0 INFO-VAX	Thu, 06 Jan 2005	Volume 2005 : Issue 12      Contents: Re: Circumcise the circumciser Re: Comp.os.vms netiquette$ Re: DCPS and Kyocera FS-6020 printer Decent VMS served web site0 Re: Emulation of an Alpha server running OpenVMS0 Re: Emulation of an Alpha server running OpenVMS0 Re: Emulation of an Alpha server running OpenVMS0 Re: Emulation of an Alpha server running OpenVMS0 Re: Emulation of an Alpha server running OpenVMS0 Re: Emulation of an Alpha server running OpenVMS, Re: For JF: Young men kill their circumciser, Re: For JF: Young men kill their circumciser, Re: For JF: Young men kill their circumciser, Re: For JF: Young men kill their circumciserP Re: Has anyone heard if any of our customers have been hurt by the tidal wave in5 Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field 5 Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field 5 Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field 5 Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field  HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement  Re: HP/Linux Tivo replacement 4 Mark Gorham interview in Interex's HP World Magazine8 Re: Mark Gorham interview in Interex's HP World Magazine Re: More on Tru64  Re: More on Tru64 B Re: need help in decoding VAXstation 4000/60 console error message/ Re: Need help with user-written routine in SOR$  Re: Need UNIX clarification  Re: Need UNIX clarification 6 NFS volume mappings disappear/not visible after reboot> O/T               Re: For JF: Young men kill their circumciserB Re: O/T               Re: For JF: Young men kill their circumciser Shared Interrupts question Re: TCP/IP mailing problem Re: TCP/IP mailing problem Re: TCP/IP mailing problem) VAXstation 3100: supported under VMS 7.3? - Re: VAXstation 3100: supported under VMS 7.3? - Re: VAXstation 3100: supported under VMS 7.3?   F ----------------------------------------------------------------------  % Date: Thu, 06 Jan 2005 12:55:07 -0500  From: dadavoo <fa@fa.foo> ' Subject: Re: Circumcise the circumciser 8 Message-ID: <mnuqt0p5falk2g4j4gpjoqocie4gv09c7p@4ax.com>  / Semolina Pilchard <ushat@ukonline.co.uk> wrote:   C >On Thu, 06 Jan 2005 12:12:52 -0500, E Varden <jpps@vif.com> wrote:  >  >> >>> : >That's your most profound post for several years, Varden.  ? No kidding.  I still remember when he/she/it was posting with a D posting date several years in the future so his/her/its posts always+ stayed current in the group, never expired.   E Whoever circumcised him/her/it obviously chopped off the entire head.    ------------------------------  $ Date: Thu, 6 Jan 2005 11:23:10 -0500< From: "Peter Weaver" <WeaverConsultingServices@sympatico.ca># Subject: Re: Comp.os.vms netiquette , Message-ID: <3456vgF4645f4U1@individual.net>   Wayne Sewell wrote:  >...F > Just be aware that potential customers may be pissed off, especiallyE > if you go overboard with it.  For instance, I wouldn't buy anything D > from Island Computers if they were the only vendor on earth.  TheyC > have been bombarding the newsgroup with incessant advertising for  > years. >...  H At least what Island does is not as bad as Computer Clearing House, justF as I was reading this thread I received a direct e-mail from them thatE did not go into my spam box. I had hardware@computerch.net in my spam 4 rules, but today they changed the sending address toE davevl@computerch.net so the garbage ended up in my inbox. Time to go  update my rule.    --   Peter Weaver Weaver Consulting Services Inc.  Canadian VAR for CHARON-VAX  www.weaverconsulting.ca    ------------------------------  $ Date: Thu, 6 Jan 2005 12:33:16 +0100% From: "Fred Zwarts" <F.Zwarts@KVI.nl> - Subject: Re: DCPS and Kyocera FS-6020 printer . Message-ID: <crj6kj$j9i$1@info.service.rug.nl>  9 "Paul Anderson" <paul.anderson@hp.com> wrote in message = / news:050120051121538775%paul.anderson@hp.com... < > In article <crh09t$5c1$1@info.service.rug.nl>, Fred Zwarts > <F.Zwarts@KVI.nl> wrote: >=20G > > The only problem left is that when a print job has printed its last A > > page, it enters the "Stalled" state and never completes. This H > > effectively blocks the queue and also printing from other systems to > > this printer is blocked. > >=20E > > I assume that the stalled state is a result of the postprocessing $ > > that DCPS performs for each job. >=20E > Yes, it appears DCPS is waiting forever for the printer to return a F > Control-D character when it is done interpreting your job.  Often, aE > printer network timeout occurs which ends the connection, but which < > also puts the DCPS job on hold.  Neither scenario is good. >=20J > > Is there a way to change this postprocessing, e.g., by setting queue =  - > > parameters, or by defining logical names?  >=20D > No, but you could try using LPD instead of Raw TCP.  LPD is less = robustH > but might work in this situation.  LPD support was added in DCPS V2.3. >=20 > Paul >=20 > --=20  >  Paul Anderson >   OpenVMS Engineering  >   Hewlett-Packard Company   G Thanks for the tip. It works, but with the additional definition of a =  logical ! name DCPS$queuename_PRODUCT_NAME. G Without this logical name, the printer only prints an error page with =  the=20 following lines:  %     Error Name:            /undefined   -     Offending Command:     checkconfiguration          Operand Stack:      G If I specify the product name as anything the symbiont complains when = 	 the first I print job is started that it does not recognize the product name and it =  assumes ) Unrecognized, but it prints correctly.=20 E This contradicts the documentation, which says that for unsupported =  printers the=20 5 definition of the product name logical is not needed.    Again, thanks for the tip!   F.Z.   ------------------------------  % Date: Thu, 06 Jan 2005 08:19:20 -0700 + From: John Nebel <john.nebel_vms@csdco.com> # Subject: Decent VMS served web site ( Message-ID: <41DD56F8.9040801@csdco.com>  I www.cdle.org runs on VMS and about 40% of the Colorado labor force is in  H the underlying system.  Having knowledge of the labor force is a useful 6 tool for state, county, and city economic development.  D Colorado is one of the few states State which meets the complex and H ever-changing USDOL-ETA reporting requirements and VMS is essential for  this.   C We are currently adding a function so Employers and Applicants can  G choose automatic notification of applicants or job openings via e-mail.   G Something like 40% of the Job Applicants now put their own information  I via the web and the data are much more complete than that entered by the  I   the local Employment Service office. This is having an interesting and  E pretty good affect on a rather large agency - people more in need of   personal attention can get it.   John   VMS booster    ------------------------------   Date: 5 Jan 2005 23:09:55 -0800  From: dooleys@snowy.net.au9 Subject: Re: Emulation of an Alpha server running OpenVMS C Message-ID: <1104995395.826203.254540@z14g2000cwz.googlegroups.com>    > D > The reason why the budget is not there is because the applications5 > resident on the VMS systems are being migrated off.  > C > The VMS systems will not be hosting users but simply serving as a E > historical data repository while that data is also migrated off and  > validated. > G > Primarily, the issue revolves around some Oracle RDB Server databases   3 > and some vendor proprietor y database structures.  > F > Speed isn't really an issue because this is strictly for archive and an% > occassional report, not production.  > C > I looked at the Oracle side of things on a VAX but the latest VAX 9 > version does not match the version level in production.  > E > Even if it did, I still have the vendor proprietor y stuff to worry  about. > G > Management doesn't want to spend 1 cent on the hardware or associated   7 > service contracts so my choices are somewhat limited.  > @ > It isn't the Unix/Windows people that are the issue but Senior) > Management trying to consolidate space.  > F > We recently shutdown one of our data centers so they need a place to put 	 > things.  > 7 > Even with server consolidation and such, it is tight.  > B This would probably be a last resort, and I hesitate to suggest it here, G but you can run Rdb on other operating systems (unsupported, but cheap)  PhilM http://www.oracle.com/technology/software/products/rdbnt8/htdocs/winsoft.html    ------------------------------   Date: 6 Jan 2005 07:41:28 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 9 Subject: Re: Emulation of an Alpha server running OpenVMS 3 Message-ID: <pcj0vQ$ywwsu@eisner.encompasserve.org>   U In article <41DC4B52.7030000@MMaz.com>, "Barry Treahy, Jr." <Treahy@MMaz.com> writes:   + > Boy, I'd hate to see your build times :-P   F    Can't be much worse than running the vector instruction emulator on    a VAXstation 2000.    ------------------------------   Date: 6 Jan 2005 07:45:19 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 9 Subject: Re: Emulation of an Alpha server running OpenVMS 3 Message-ID: <5EUwCA7ZLmXi@eisner.encompasserve.org>   X In article <7qZCd.5167$kk7.2464@news.cpqcorp.net>, hoff@hp.nospam (Hoff Hoffman) writes: > C >   As others have mentioned, there is presently no Alpha emulator  D >   available, and a move to a smaller and speedier Alpha, or a moveE >   to a OpenVMS I64 box -- and significant cost savings within these @ >   I64 boxes could be realized here -- might well be an option. >   F    Case in point:  we recently pulled an EV5 workstation out of excess@    to replace a DEC 10000.  The space savings are major, and the"    performance increase is nice.     ------------------------------   Date: 6 Jan 2005 07:56:58 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 9 Subject: Re: Emulation of an Alpha server running OpenVMS 3 Message-ID: <Eo2RbbgAeKAO@eisner.encompasserve.org>   V In article <41DC7387.6080001@tsoft-inc.com>, Dave Froble <davef@tsoft-inc.com> writes: > R > You need an elephant to stomp on that antique!  No, I forget how they built the 2 > boxes back then.  The elephant couldn't hurt it.  G    I'm not quite an elephant, but I was always sure my MicroVAXen would      tolerate me standing on them.   ------------------------------  % Date: Thu, 06 Jan 2005 17:34:02 +0000 E From: Tim ffrench-Lynch <tim-DOT-ffrench-HYPHEN-lynch@baesystems.com> 9 Subject: Re: Emulation of an Alpha server running OpenVMS . Message-ID: <41DD768A.3F706C5F@baesystems.com>   Andrew Robert wrote: >  > Good morning,  > H > I anticipate retirement of my legacy Alpha OpenVMS systems in the near	 > future.  > G > I've reviewed the Charon-VAX and Simh VAX emulators and they are nice : > but they appear to emulate the VAX/VMS environment only. > 3 > I need to be able to emulate a full Alpha system.  > 1 > Does anyone know of a suitable emulator around?   C I'd get a pair of second hand DS10L systems, each will hopefully be @ able to take enough memory and disk space to support your legacy; requirements on it's own and allows for one system failing.   D They're only 1.75" high - just stick an 'Intel Inside' badge on them9 and tell the boss that they're PCs emulating an Alpha :-)    Tim    ------------------------------   Date: 6 Jan 2005 09:38:18 -0800 & From: "Galen" <gspamtackett@yahoo.com>9 Subject: Re: Emulation of an Alpha server running OpenVMS B Message-ID: <1105033098.223287.17140@f14g2000cwb.googlegroups.com>  : > An emulation of a 64-bit system on a 32-bit system would > be incredibly slow.   E As a Mac enthusiast, I just can't help pointing out that Apple offers B some very nice PowerMac G5 systems with 64 bit processors. I'm not= familiar enough with them to know just how fully the software > environment supports 64 bit addressing and data types, though.  B So, as soon as I have the money to buy a G5 I'll get started on anG Alpha emulator to run under OS X.  (Just kidding! :-) With all the free E time I have it would only take me 10 or 15 years to get it written. )    ------------------------------  % Date: Thu, 06 Jan 2005 08:00:17 +0000 . From: Semolina Pilchard <ushat@ukonline.co.uk>5 Subject: Re: For JF: Young men kill their circumciser 8 Message-ID: <7arpt0tol3bicungtbs15o8tlus0ftrbl0@4ax.com>  - On Wed, 05 Jan 2005 18:50:16 -0500, Dan Drake # <ddrake@comcast.notthis.net> wrote:   6 >On Wed, 05 Jan 2005 02:10:32 +0000, Semolina Pilchard ><ushat@ukonline.co.uk> wrote: > @ >>Not the same thing.  That's like stags going into rut.  It's aF >>response to oestrus in females.  "Oestrus" = "in heat" but is not so >>illiterately expressed.  > F >Argue semantics if you like, and you're probably right about heat andG >oestrus, but the fact remains that male elephants periodically go into > >must whether or not a fruity female elephant is within range.  B It's a little more than semantics.  More elementary biology.  It'sA called heat because the female's vaginal temperature rises during F oestrus.  That's why artificial insemination operatives (now there's aA good job) carry a thermometer.  Saves 'em wasting good spunk on a F female that has passed the period of optimum fertility.  Clearly, thisF phenomen cannot be replicated in the male of the species as it lacks aA vagina.  I may not have your profound and first-hand knowledge of D pachyderm's genitals, Dan, but on the other hand I don't mistake oneB discrete phenomenon for another and then dig my heels in about it. > F >And when a male elephant is in must, then he's not to be fucked with,F >unless you offer him a receptive female elephant, or you have alreadyG >scraped the crud off from behind his ears.  A bit like the SR, really.   C That may well be the case, but I fail to see how this can back your : rather peculiar assertion that male animals go into heat.  >  >Ask a mahout.   I meet them so rarely. --   Sem    ------------------------------  % Date: Thu, 06 Jan 2005 06:15:11 -0500 , From: Dan Drake <ddrake@comcast.notthis.net>5 Subject: Re: For JF: Young men kill their circumciser 8 Message-ID: <jn6qt0h1pd2426kiv5vtkd1408b7jnovkt@4ax.com>  5 On Thu, 06 Jan 2005 08:00:17 +0000, Semolina Pilchard  <ushat@ukonline.co.uk> wrote:   C >It's a little more than semantics.  More elementary biology.  It's B >called heat because the female's vaginal temperature rises during	 >oestrus.   F The OED says: "Sexual excitement or desire.  Now only, (the period of)F a female animal's readiness for mating: esp in 'on heat,' (Chiefly US) 'in heat' ME."  C I'm sure the Middle English were running around poking their highly C accurate thermometers up their she-animals' pussies all the time...   D >That may well be the case, but I fail to see how this can back your: >rather peculiar assertion that male animals go into heat.  F It seems like male animals used to get sexual heat, but they don't any+ more.  Maybe you know something about that?  --  	 Dan Drake    ------------------------------  % Date: Thu, 06 Jan 2005 12:22:31 +0000 . From: Semolina Pilchard <ushat@ukonline.co.uk>5 Subject: Re: For JF: Young men kill their circumciser 8 Message-ID: <qu9qt0h1auvfkj9vi0kv6eju3j2ikukcor@4ax.com>  - On Thu, 06 Jan 2005 06:15:11 -0500, Dan Drake # <ddrake@comcast.notthis.net> wrote:   6 >On Thu, 06 Jan 2005 08:00:17 +0000, Semolina Pilchard ><ushat@ukonline.co.uk> wrote: > D >>It's a little more than semantics.  More elementary biology.  It'sC >>called heat because the female's vaginal temperature rises during 
 >>oestrus. > G >The OED says: "Sexual excitement or desire.  Now only, (the period of) G >a female animal's readiness for mating: esp in 'on heat,' (Chiefly US)  >'in heat' ME."   > Your excursion into the arcana of the OED doesn't seem to haveC furthered your cause one jot or tittle, Dan, me boy.  I had a quick E squint in my Lloyd's Encyclopaedic Dictionary (1895) but there was no A entry for the sexual connotation of "heat", possibly because them C godly Victorians averted their eyes from dirty shit like that while 5 bungholing the manservant over the dining-room table.  > D >I'm sure the Middle English were running around poking their highlyD >accurate thermometers up their she-animals' pussies all the time...  C To get the minor technicalities out of the road, Middle English was ; what they spoke, not who they were.  Who they were, was the E predominantly rural early medieval yeomanry.  Don't decry them.  They D may not have had our technology but their powers of observation wereF pretty good.  I'm sure they could tell a cow's cunt from an elephant'sB pizzle, and lacking thermometers I expect they thrust their highlyE accurate and sensitive FINGERS up the snatch of the cow, ewe, goat or > whatever and were discerning enough to know whether the raisedE temperature indicated it was fucking time.  Being quite logical about D this, we can be sure that it was so.  Had medieval man or any of our< forebears been unable to manage this simple element of stock@ husbandry, we probably wouldn't be around as a species any more. > E >>That may well be the case, but I fail to see how this can back your ; >>rather peculiar assertion that male animals go into heat.  > G >It seems like male animals used to get sexual heat, but they don't any , >more.  Maybe you know something about that?  C Oh, dear.  How fucking persistent you are.  I admire a captain that A goes down with his ship, though.  Male animals, men included, may D imagine that they are hot (or even hawt) when aroused.  They mistakeD ardour for temperature.  It may that due to the rush of blood to the? penis during erection, that organ becomes warmer by a minuscule < proportion.  I don't know.  But it certainly isn't an easilyB measurable indicator of peak fertility, as it is in the females ofE some species.  It isn't "going in (or on) heat.  It's just a stiffie.  --   Sem    ------------------------------  % Date: Thu, 06 Jan 2005 11:35:28 -0500  From: E Varden <jpps@vif.com> 5 Subject: Re: For JF: Young men kill their circumciser + Message-ID: <1105029349.395085@www.vif.com>    Dan Drake wrote:7 > On Wed, 05 Jan 2005 02:10:32 +0000, Semolina Pilchard  > <ushat@ukonline.co.uk> wrote:  >  > / >>On Tue, 04 Jan 2005 19:59:17 -0500, Dan Drake % >><ddrake@comcast.notthis.net> wrote:  >> >>8 >>>On Tue, 04 Jan 2005 18:53:25 +0000, Semolina Pilchard  >>><ushat@ukonline.co.uk> wrote: >>>  >>>   >>>>MYou need ovaries before you >>>>can go in heat.  >>> ( >>>Tell that to a male elephant in must. >>@ >>Not the same thing.  That's like stags going into rut.  It's aF >>response to oestrus in females.  "Oestrus" = "in heat" but is not so >>illiterately expressed.  >  > G > Argue semantics if you like, and you're probably right about heat and H > oestrus, but the fact remains that male elephants periodically go into? > must whether or not a fruity female elephant is within range.    	[nix the xposting]   ? Ob pedant:  it's "musth", you ass-fat simple armchair wizards,  ( speaking of that illiterately expressed.  C "Must" is your duty to your wife.  "Musth" is the unstoppable need  B to do duty to any cunt with the whiff of elephant - and anyone in  the way becomes travel-paste.   3 ...Sometimes I think of them as Italian, I dunno...      Pe   ------------------------------  % Date: Thu, 06 Jan 2005 01:48:09 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> Y Subject: Re: Has anyone heard if any of our customers have been hurt by the tidal wave in , Message-ID: <41DCDEF8.667BA1A2@teksavvy.com>  J BBC reported that Lafarge (makers of cement/concrete) had a large plant inL Aceh province and all of the 350 employees are missing. Lafarge used to be aI big VMS shop. I think they still have a couple of VMS boxes left here and V there around the world. (But their main systems are now on a competitor's Unix (HPUX).    M Concrete plants like to be near water/port so that they can load the concrete  into ships for transport.    ------------------------------   Date: 6 Jan 2005 08:56:02 GMT 2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>> Subject: Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field? Message-ID: <DTiotGxQ0bj6-pn2-JS0LYQOPbD1J@dave2_os2.home.ours>   B On Wed, 5 Jan 2005 19:55:47 UTC, John Reagan <john.reagan@hp.com>  wrote:   > Lorin Ricker wrote:  >  > > F > > b)  Looked for asynchronous and volatile data issues/problems, andG > > I've used all available Pascal attributes and directives to be sure F > > that I'm not being tripped up by this sort of thing.  No change inI > > behavior.  I'm pretty darn sure that compiler-optimization issues are  > > not at fault here. > 
 > Thanks. :-)  >  >  > > A > > *  Do $GET/SETUAI honor the logical name "SYSUAF" to redirect F > > operations to test-copies of SYSUAF.DAT, or are these RTL routines? > > "hard-wired" to the official system instance in SYS$SYSTEM?  > J > I've certainly moved SYSUAF.DAT out of SYS$SYSTEM before.  The logicals I > have to be /SYSTEM/EXEC.  For just playing with a local SYSUAF.DAT for  E > fun, I believe the services will follow your logical.  Define your  H > SYSUAF logical and use AUTHORIZE to see if you can read/write it.  It  > uses the same interfaces.  > % > Beyond that, I have no real advice.  >  >   D Depending on how the file open is done I would have (half-)expected B that a copy of the file in the current working directory would be A opened every time. Certainly in Fortran. i.e. an open specifying  ? 'SYSUAF' would apply the the default '.DAT' extension and find  B SYSUAF.DAT and open it. Does Pascal do any different? This was my F experience (_not_ with SYSUAF but opening by logical name in general) ; many moons ago (VMS V5.nn!!). I've not checked again since.   F Mind you, I was playing with process logical names. I've never had the* need to play, explicitly, in higher modes.    --   Cheers - Dave W.   ------------------------------   Date: 6 Jan 2005 07:56:05 -0600  From: briggs@encompasserve.org> Subject: Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field3 Message-ID: <yCTU5ipS94Vz@eisner.encompasserve.org>   t In article <DTiotGxQ0bj6-pn2-JS0LYQOPbD1J@dave2_os2.home.ours>, "Dave Weatherall" <djw-nothere@nospam.nohow> writes:F > Depending on how the file open is done I would have (half-)expected D > that a copy of the file in the current working directory would be C > opened every time. Certainly in Fortran. i.e. an open specifying  A > 'SYSUAF' would apply the the default '.DAT' extension and find  D > SYSUAF.DAT and open it. Does Pascal do any different? This was my H > experience (_not_ with SYSUAF but opening by logical name in general) = > many moons ago (VMS V5.nn!!). I've not checked again since.   ' In Fortran, an open along the lines of:   2 	OPEN ( UNIT=1, FILE='SYSUAF', STATUS='OLD', ... )   together with a logical name  6 	$ DEFINE /SYSTEM /EXEC SYSUAF SHARED_FILES:SYSUAF.DAT  # will access SHARED_FILES:SYSUAF.DAT   ) and will not access SYS$DISK:[]SYSUAF.DAT     @ The file name presented in an OPEN command is subject to logical/ name translation in three cases that I know of:   : o If file name has the syntax:  nodename::rest-of-filespec  $   e.g. DONALD::SYS$SYSTEM:SYSUAF.DAT  ?   Logical name resolution is attempted on the nodename (DONALD)   > o If the file name has the syntax: devicename:rest-of-filespec     e.g. CLUSTER_FILES:SYSUAF.DAT   H   Logical name resolution is attempted on the devicename (CLUSTER_FILES)  I o If the file name has the syntax:  name   (devoid of ':', '.', ';', etc)   
   e.g. SYSUAF   ;   Logical name resolution is attempted on the name (SYSUAF)   M o Otherwise (name has multiple components, but no leading device or nodename)      e.g. SYSUAF.DAT   *   Logical name resolution is not attempted  A This is all RMS default behavior.  It is not specific to Fortran,  Pascal, BASIC or anything else.   C [This simplified description looks just at the initial logical name C resolution performed with respect to the main filespec.  It ignores A the translation that may be performed with respect to the default = file spec, related file specs and SYS$DISK:.  It also ignores @ any iterative translation that may occur if the file name syntax> resulting from one set of translations has a leading nodename,/ a leading devicename or is a one part filename]   H > Mind you, I was playing with process logical names. I've never had the, > need to play, explicitly, in higher modes.  @ Largely irrelevant.  A Fortran (or Pascal, C, Basic or whatever)E OPEN will respect logical names at all four access modes.  The gotcha > is that it will use the _outermost_ such logical name.  And it> will pay attention to logical names in the tables mentioned in the user's LNM$FILE_DEV list.   A By contrast, the services that use SYSUAF for authentication will I ignore outer mode logical names and use inner mode logical names instead. H These security services are picky about the logical name tables in which they search as well.   ------------------------------  $ Date: Thu, 6 Jan 2005 08:55:51 -0500: From: "Hein RMS van den Heuvel" <hein@Hewlett-Packard.com>> Subject: Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field, Message-ID: <41dd4388$1@usenet01.boi.hp.com>  E "Hein RMS van den Heuvel" <hein@Hewlett-Packard.com> wrote in message & news:41dccc8c$1@usenet01.boi.hp.com... > > > Here is a simple script to identify 'broken' sysuaf records:  L Sorry for re-replying to my own reply. Should have done it right immediatly.K That script was a first version which would only catch current corruptions,  but not latent corruptions. > The script that I meant to post, is included and detects both.  L If you run this on your sysuaf in the next few days/weeks and then detect (aL pattern of) corruptions that you can not explain then I'd like to hear: hein at hp_remove_this_ dot com   Hein.    $open/read/share=write uaf4 'f$parse("SYSUAF","SYS$SYSTEM:.DAT",,,"SYNTAX_ONLY") $loop:  $read/nolock/end=done uaf record $offset = f$cvsi(16,16,record) $len = f$length(record) 1 $if offset.eq.0   .and. len.eq.644 then goto loop 1 $if offset.eq.644 .and. len.ge.644 then goto loop ; $write sys$output "''f$extr(4,12,record)' ''len' ''offset'" 
 $goto loop $done:
 $close uaf   ------------------------------  % Date: Thu, 06 Jan 2005 14:46:42 +0000 - From: John Laird <nospam@laird-towers.org.uk> > Subject: Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field8 Message-ID: <nqiqt0pvaj7c7hs5ina6pde7f6t4293nvo@4ax.com>  H On 6 Jan 2005 08:56:02 GMT, "Dave Weatherall" <djw-nothere@nospam.nohow> wrote:  E >Depending on how the file open is done I would have (half-)expected  C >that a copy of the file in the current working directory would be  B >opened every time. Certainly in Fortran. i.e. an open specifying @ >'SYSUAF' would apply the the default '.DAT' extension and find C >SYSUAF.DAT and open it. Does Pascal do any different? This was my  G >experience (_not_ with SYSUAF but opening by logical name in general)  < >many moons ago (VMS V5.nn!!). I've not checked again since.  J I would imagine that the file is opened with a name-spec of 'SYSUAF' and aI default name-spec of 'SYS$SYSTEM:.DAT', as this will find the file in the G expected location in the absence of a logical name entry for SYSUAF (*) G This default name-spec is not used on a subsequent creation however ;-) L Fortran implicitly provides a DEFAULTFILE value of '.DAT', with a FILE value7 of 'FORnnn' for logical unit nnn, as you no doubt know.   L (*)  I wish ACCOUNTING had sensible default file-handling .  And ANAL/AUDIT.J And there are probably others.  I sort of expect ACCOUNTING ;-1 to examine% the previous version, and it doesn't.    --  / Our biggest problem is apathy - but who cares?     Mail john rather than nospam...    ------------------------------  $ Date: Thu, 6 Jan 2005 06:35:27 -0500# From: "John Smith" <a@nonymous.com> " Subject: HP/Linux Tivo replacement, Message-ID: <_NSdndMv_Prhv0DcRVn-sQ@igs.net>  3 http://pcworld.com/news/article/0,aid,119173,00.asp   K Do you think that with the same amount of man-hours invested in customizing F Linux for the task, HP could have made VMS do the same thing for them?   ------------------------------   Date: 6 Jan 2005 13:38:27 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)& Subject: Re: HP/Linux Tivo replacement, Message-ID: <344tajF48q7g6U1@individual.net>  , In article <_NSdndMv_Prhv0DcRVn-sQ@igs.net>,& 	"John Smith" <a@nonymous.com> writes:5 > http://pcworld.com/news/article/0,aid,119173,00.asp  > M > Do you think that with the same amount of man-hours invested in customizing H > Linux for the task, HP could have made VMS do the same thing for them? >   7 Considering that a Tivo clone running on Linux has been 8 around for more than a year, I would guess they expended< somewhere real close to 0 man-hours bringing this to market.8 Considering the current state of graphics support in VMS6 and the very high liklihood that it will never support8 things like TV Tuner Cards, how much effort do you think  it would take to do this on VMS?   bill     --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   Date: 6 Jan 2005 08:13:56 -0600 B From: clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley)& Subject: Re: HP/Linux Tivo replacement3 Message-ID: <zvq44yJKS+cK@eisner.encompasserve.org>   W In article <344tajF48q7g6U1@individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: . > In article <_NSdndMv_Prhv0DcRVn-sQ@igs.net>,( > 	"John Smith" <a@nonymous.com> writes:6 >> http://pcworld.com/news/article/0,aid,119173,00.asp >>  N >> Do you think that with the same amount of man-hours invested in customizingI >> Linux for the task, HP could have made VMS do the same thing for them?  >>   > 9 > Considering that a Tivo clone running on Linux has been : > around for more than a year, I would guess they expended> > somewhere real close to 0 man-hours bringing this to market.: > Considering the current state of graphics support in VMS8 > and the very high liklihood that it will never support: > things like TV Tuner Cards, how much effort do you think" > it would take to do this on VMS? >   G You also need to consider that Linux will run on really cheap hardware, M unlike VMS. For example, Linux is used in the Linksys WRT54G wireless router. A (And yes, I know that cheap hardware is not VMS's target market.)   I I actually stuck a TV tuner card in my home Alpha once and wrote a driver L for it. I was only interested in the teletext data stream transmitted withinK the video signal, but it was enough to make me realise just how much effort 1 would be required for general television support.   K BTW, at the time I did this, VMS did not support shared interrupts. I don't F know if there are any plans to change this, but the tuner card I used,K where the audio and video capabilities appeared as different PCI functions, ( shared an interrupt for those functions.  J The short summary is that sadly it's easier and more feasible to use Linux% for this than it would be to use VMS.    Simon.   --  B Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP       7 Microsoft: The Standard Oil Company of the 21st century    ------------------------------  % Date: Thu, 06 Jan 2005 07:55:00 -0700 + From: "Barry Treahy, Jr." <Treahy@MMaz.com> & Subject: Re: HP/Linux Tivo replacement' Message-ID: <41DD5144.8070203@MMaz.com>    John Smith wrote:   4 >http://pcworld.com/news/article/0,aid,119173,00.asp > L >Do you think that with the same amount of man-hours invested in customizingG >Linux for the task, HP could have made VMS do the same thing for them?  >    > G They don't state the architecture in the article, other than to say it  D isn't a PC, but I doubt the processor is an Alpha, Itantic, or PPC, E which most likely means it is a flavor of X86 which HP/Compaq didn't  B port VMS too...  Now, if the money and time wasted to port VMS to I Itantic had been invested into a X86 or X86-64 port, then I believe your  H question would have been valid.  Whether you like Linux, which I do, or H not, I don't know of a more hardware neutral OS - it runs on just about 
 everything...      Barryn   --    < Barry Treahy, Jr                     E-mail: Treahy@MMaz.com< Midwest Microwave, Inc.                  Phone: 480/314-1320< Vice President & CIO                      FAX:  480/661-7028  I                        ... but it's a DRY HEAT!                          g   ------------------------------   Date: 6 Jan 2005 15:55:15 GMTl( From: bill@cs.uofs.edu (Bill Gunshannon)& Subject: Re: HP/Linux Tivo replacement, Message-ID: <3455b3F48s5lcU1@individual.net>  ' In article <41DD5144.8070203@mmaz.com>,c. 	"Barry Treahy, Jr." <Treahy@MMaz.com> writes: > I > They don't state the architecture in the article, other than to say it  F > isn't a PC, but I doubt the processor is an Alpha, Itantic, or PPC, G > which most likely means it is a flavor of X86 which HP/Compaq didn't nD > port VMS too...  Now, if the money and time wasted to port VMS to K > Itantic had been invested into a X86 or X86-64 port, then I believe your vJ > question would have been valid.  Whether you like Linux, which I do, or J > not, I don't know of a more hardware neutral OS - it runs on just about  > everything...m >   B I don't mean to rain on your parade, but I think you will find BSDB runns on more different systems than Linux.  And it's a better OS.C And it has a more reasonable license.  I can not for the life of meT- figure out what is so attractive about Linux.r   bill   -- aJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   r   ------------------------------  % Date: Thu, 06 Jan 2005 09:30:06 -0700 + From: "Barry Treahy, Jr." <Treahy@MMaz.com>o& Subject: Re: HP/Linux Tivo replacement' Message-ID: <41DD678E.8050005@MMaz.com>e   Bill Gunshannon wrote:  ( >In article <41DD5144.8070203@mmaz.com>,/ >	"Barry Treahy, Jr." <Treahy@MMaz.com> writes:P >  i >pI >>They don't state the architecture in the article, other than to say it pF >>isn't a PC, but I doubt the processor is an Alpha, Itantic, or PPC, G >>which most likely means it is a flavor of X86 which HP/Compaq didn't  D >>port VMS too...  Now, if the money and time wasted to port VMS to K >>Itantic had been invested into a X86 or X86-64 port, then I believe your oJ >>question would have been valid.  Whether you like Linux, which I do, or J >>not, I don't know of a more hardware neutral OS - it runs on just about  >>everything...o >> >>     >> >s& >I don't mean to rain on your parade,  > G With all of the rain that has been hitting Phoenix, I would never have l noticed :-)    >but I think you will find BSD. >runns on more different systems than Linux.   >hG I stand corrected, but that still doesn't change the argument that VMS -F doesn't run native on much of anything in comparison to the countless  flavors of Un*x"   >And it's a better OS. >  a >oG Perhaps it is today, possibly it is just a matter of exposure and that iE when I started using Linux almost a decade ago, the 1.x Linux kernel nE just worked out better for the older 486 hardware that I had vs. BSD.h  ( >And it has a more reasonable license.   > E Eh, a debate that really doesn't impact me, so I really don't care...a   >I can not for the life of mew. >figure out what is so attractive about Linux. >  l >tG That's easy, the Penguin is cuter, at least according to my wife, than s the Demon...   Barryr   --    < Barry Treahy, Jr                     E-mail: Treahy@MMaz.com< Midwest Microwave, Inc.                  Phone: 480/314-1320< Vice President & CIO                      FAX:  480/661-7028  I                        ... but it's a DRY HEAT!                          v   ------------------------------  % Date: Thu, 06 Jan 2005 11:25:55 -0500v- From: JF Mezei <jfmezei.spamnot@teksavvy.com>-& Subject: Re: HP/Linux Tivo replacementB Message-ID: <1105028156.7b261dc45620652d3a9ebc9dee8d5626@teranews>   Bill Gunshannon wrote:: > Considering the current state of graphics support in VMS8 > and the very high liklihood that it will never support: > things like TV Tuner Cards, how much effort do you think" > it would take to do this on VMS?  8 Every excuse you make shuts VMS from yet another market.  H One shouldn't find reasons NOT to do something with VMS, one should find5 reasons to do stuff with VMS and expand its horizons.t  K Look at DECwidnows. It isn't in the VMS roadmap. Lets assume that they haverM abandonned it for the sake of discussion. Then, DEC/HP should release the lowsK level X code as open source, and thne strike a deal with OpenMotif to allowCI the open sources version of Motif to run on VMS (its the same, except thehC license requires you run openmotif only on open sources platforms).e  J Because all of X is now open source, having the proprietary bits availableN would allow the porting of modern motif and X to VMS since DEC/HP aren't going
 to do it.   J There si a lot of very good code around VMS that is being kept in a prisonL instead of being given a chance to do some good. It may or may not result inN something good, but one thing is sure: keeping that source in a vault will NOT do any good.   ------------------------------   Date: 6 Jan 2005 16:37:45 GMT-( From: bill@cs.uofs.edu (Bill Gunshannon)& Subject: Re: HP/Linux Tivo replacement, Message-ID: <3457qoF455jsqU1@individual.net>  B In article <1105028156.7b261dc45620652d3a9ebc9dee8d5626@teranews>,0 	JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > Bill Gunshannon wrote:; >> Considering the current state of graphics support in VMS 9 >> and the very high liklihood that it will never supporta; >> things like TV Tuner Cards, how much effort do you think # >> it would take to do this on VMS?  > : > Every excuse you make shuts VMS from yet another market.  + There you go, shooting the messenger again.a   > J > One shouldn't find reasons NOT to do something with VMS, one should find7 > reasons to do stuff with VMS and expand its horizons.   C Tell HP that.  They released a product on Linux instead of VMS.  Of5A course, I didn't even mention the biggest reason you'll never seej> OpenVMS Tivo.  When the Linux version was just being developed> people were arguing that considering the cost of a Tivo box it> was too expensive to do it with Linux.  So, where do you think  VMS would weigh in on this one??   > M > Look at DECwidnows. It isn't in the VMS roadmap. Lets assume that they havewO > abandonned it for the sake of discussion. Then, DEC/HP should release the lowuM > level X code as open source, and thne strike a deal with OpenMotif to allownK > the open sources version of Motif to run on VMS (its the same, except thetE > license requires you run openmotif only on open sources platforms).n  + OK.  Go ahead and convince HP of that.  :-)    > L > Because all of X is now open source, having the proprietary bits availableP > would allow the porting of modern motif and X to VMS since DEC/HP aren't going > to do it.   + OK.  Go ahead and convince HP of that.  :-)i   > L > There si a lot of very good code around VMS that is being kept in a prisonN > instead of being given a chance to do some good. It may or may not result inP > something good, but one thing is sure: keeping that source in a vault will NOT > do any good.  + OK.  Go ahead and convince HP of that.  :-)t   Do you see a pattern here?    A Going back to your original statement, one doesn't have to "find"MA reasons for not doing something with VMS.  HP, who owns it, takest good care of that.   bill   -- aJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   a   ------------------------------  % Date: Thu, 06 Jan 2005 11:51:36 -0500h3 From: Steve Lionel <Steve.Lionel@REMOVEintelME.com> & Subject: Re: HP/Linux Tivo replacement8 Message-ID: <r1rqt01er6s25uukucpqphel5bgbjhpjpq@4ax.com>  E On 6 Jan 2005 13:38:27 GMT, bill@cs.uofs.edu (Bill Gunshannon) wrote:n  8 >Considering that a Tivo clone running on Linux has been >around for more than a year,   J A hard disk video recorder, maybe.  A "TiVo clone", no - not any more than5 Windows is a "VMS clone" because it can run programs.    Stevec   ------------------------------  % Date: Thu, 06 Jan 2005 12:43:31 -0500n- From: JF Mezei <jfmezei.spamnot@teksavvy.com>s& Subject: Re: HP/Linux Tivo replacementB Message-ID: <1105032807.67b1675445395aa08bb2c1ee48b7b2d8@teranews>   Steve Lionel wrote:eL > A hard disk video recorder, maybe.  A "TiVo clone", no - not any more than7 > Windows is a "VMS clone" because it can run programs.-  M Rela Tivo boxes have been hacked by Linux geeks who were able to add programsrN and features to the standard Tivo software, enabling, for instance FTP service; so that you could copy moving to/from the Tivo and your PC.a  K Such hackjs became popular enough that Tivo is now starting to enable thosee" features in the unhacked machines.  N Had Tivo chosen a more secure OS such as VMS for an embedded box, such hackersN would not likely have been able to penetrate the box which would have remained a big black box.  H However, in the grand scheme of things, the Linux solution will turn outI better since hackers have already forced Tivo to improve their product bygG enabling features that they had purposefully disabled (due to copyrightkL issues). Had the Tivo box been secure, there wouldn't have been the pressure" for Tivo to open up such features.   ------------------------------  % Date: Thu, 06 Jan 2005 10:41:58 -0700e+ From: "Barry Treahy, Jr." <Treahy@MMaz.com>-& Subject: Re: HP/Linux Tivo replacement' Message-ID: <41DD7866.3080705@MMaz.com>e   Steve Lionel wrote:t  F >On 6 Jan 2005 13:38:27 GMT, bill@cs.uofs.edu (Bill Gunshannon) wrote: >x >    >t9 >>Considering that a Tivo clone running on Linux has beene >>around for more than a year, . >>     >> >-K >A hard disk video recorder, maybe.  A "TiVo clone", no - not any more thanr6 >Windows is a "VMS clone" because it can run programs. >  i >oH I hate to disagree, but EchoStar's DishNetwork has had TiVo like, Linux  based, DVR's for a long time...C   Barry0   -- t  < Barry Treahy, Jr                     E-mail: Treahy@MMaz.com< Midwest Microwave, Inc.                  Phone: 480/314-1320< Vice President & CIO                      FAX:  480/661-7028  I                        ... but it's a DRY HEAT!                          l   ------------------------------  $ Date: Thu, 6 Jan 2005 12:44:08 -0500# From: "John Smith" <a@nonymous.com> & Subject: Re: HP/Linux Tivo replacement, Message-ID: <TfOdnbEL1P175UDcRVn-pQ@igs.net>   Bill Gunshannon wrote:D > In article <1105028156.7b261dc45620652d3a9ebc9dee8d5626@teranews>,1 > JF Mezei <jfmezei.spamnot@teksavvy.com> writes:  >> Bill Gunshannon wrote:m< >>> Considering the current state of graphics support in VMS: >>> and the very high liklihood that it will never support< >>> things like TV Tuner Cards, how much effort do you think$ >>> it would take to do this on VMS? >>; >> Every excuse you make shuts VMS from yet another market.e >u- > There you go, shooting the messenger again.  >0 >>F >> One shouldn't find reasons NOT to do something with VMS, one should= >> find reasons to do stuff with VMS and expand its horizons.o >nE > Tell HP that.  They released a product on Linux instead of VMS.  OfsC > course, I didn't even mention the biggest reason you'll never seel@ > OpenVMS Tivo.  When the Linux version was just being developed@ > people were arguing that considering the cost of a Tivo box it@ > was too expensive to do it with Linux.  So, where do you think" > VMS would weigh in on this one?? >g >>D >> Look at DECwidnows. It isn't in the VMS roadmap. Lets assume thatC >> they have abandonned it for the sake of discussion. Then, DEC/HPpF >> should release the low level X code as open source, and thne strikeF >> a deal with OpenMotif to allow the open sources version of Motif to@ >> run on VMS (its the same, except the license requires you run- >> openmotif only on open sources platforms).  >e- > OK.  Go ahead and convince HP of that.  :-)l >r >>C >> Because all of X is now open source, having the proprietary bitstG >> available would allow the porting of modern motif and X to VMS since-  >> DEC/HP aren't going to do it. > - > OK.  Go ahead and convince HP of that.  :-)u >t >>F >> There si a lot of very good code around VMS that is being kept in aD >> prison instead of being given a chance to do some good. It may orC >> may not result in something good, but one thing is sure: keepinge/ >> that source in a vault will NOT do any good.n >i- > OK.  Go ahead and convince HP of that.  :-)o >h > Do you see a pattern here? >gC > Going back to your original statement, one doesn't have to "find"=C > reasons for not doing something with VMS.  HP, who owns it, takesn > good care of that.      K An implied point in the original proposition is that an HP-internal producthJ (VMS) could have been used (potentially), but not likely because as we all. know VMS does not run on inexpensive hardware.  K If VMS were used, would we see people 'hacking' the boxes they chose to runtJ it on just so they could get their hands on a VMS machine? Not likely. ButE again, that's not the point even though it would be waaay cool to see 2 hackers smacking their heads against VMS concrete.  K But the real point is that the HP executives would see and maybe would even L say something along the lines of "Hey, that VMS operating system is good forH a lot of things if we put our minds to it". Heck, the word "Invent" even> springs to mind. And with that would likely come more funding.  L Okay, linux didn't cost HP much....but neither does VMS if they chose to useK it for this app as an embedded os (as long as it worked on the chosen h/w).e  K I seem to recollect that there was some discussion of making VMS run on ARMyA when DEC had it, which probably isn't a bad choice of chip for ankD application like a Tivo-like clone. Now that it too is an Intel chipB (Xscale), maybe Intel can cough up some porting money for VMS  ;-)  L No offense to VMS Engineering, but I guess it's hard to 'invent' outside theK box, or even get the opportunity to do a "Google" (20% of your week devotedmJ to new ideas that could lead anywhere - an Xscale or x86 or Power5 or evenI Sparc port for example) when you are short-staffed and can barely keep upeH with all the absolutely necessary stuff you have to do as it is. And theL execs who control you are themselves like puppets on strings controlled from on high in Palo Alto.x   --John&  "I am not a number! I am a free man!"   ------------------------------  $ Date: Thu, 6 Jan 2005 10:36:44 -0800% From: DeanW <dean.woodward@gmail.com> & Subject: Re: HP/Linux Tivo replacement7 Message-ID: <3f119ada050106103674def2a0@mail.gmail.com>s  E On Thu, 6 Jan 2005 06:35:27 -0500, John Smith <a@nonymous.com> wrote: 5 > http://pcworld.com/news/article/0,aid,119173,00.aspe > A > Do you think that with the same amount of man-hours invested in ? > customizing Linux for the task, HP could have made VMS do theh > same thing for them?   Not even close.-+    a) VMS doesn't run on commodity hardware3B    b) The device drivers (capture card) don't already exist on VMS  E Other than that, what's the business model? How would you license it?9> How much would having VMS on it increase the price? What's the advantage, anyway?  	 JF wrote:oC > Had Tivo chosen a more secure OS such as VMS for an embedded box,iI > such hackers would not likely have been able to penetrate the box whicht& > would have remained a big black box.  F You're kidding, right?  Hacking a Tivo is *not* the same as cracking aF box over the internet by exploiting a buffer overrun- it's a matter ofE pulling the HD and dropping it into another system, then mounting the(C disk and poking around. Do you think The Almighty MicroVAX 3100 canhE remain secure under those conditions?  The only extra security that a,@ VMS box would have offered would have been the "security through obscurity" kind- i.e., "none".  C Backing up to the other point- if it *had* been VMS based, it wouldlF have been great for VMS publicity, as people would be flocking here in2 droves to find out how to work in the environment.   ------------------------------  # Date: Thu, 06 Jan 2005 18:03:51 GMTa1 From: Keith Parris <keithparris_NOSPAM@yahoo.com>a= Subject: Mark Gorham interview in Interex's HP World Magazinea0 Message-ID: <b4fDd.5239$1j.632@news.cpqcorp.net>  A See http://www.openvms.org/stories.php?story=05/01/04/5775466 or l3 http://www.interex.com/hpworldnews/hpw501/news3.jspd  " Some snippets I found interesting:  " "Q: Is OpenVMS growing these days?  G OpenVMS has been growing for the last year. Weve had four quarters of oH either single- or double-digit revenue growth. Its been quite exciting  for us."  I This is also the first public mention I've seen of Mark's important work tH and influence beyond just OpenVMS, making changes to HP's policies that A benefit HP as they help OpenVMS: "Gorham is also responsible for nI programs to grow HP revenue and improve customer satisfaction. He is the kD BCS (Business Critical Systems) Executive Champion for more than 70 H customers worldwide, the BCS Country Champion for the Nordic Countries, H and the BCS Government Segment Champion. Gorham is currently working in F the Enterprise Storage and Servers (ESS) War Room, helping to drive F end-to-end business models and process improvements that systemically 4 improve the worldwide business performance for ESS."   ------------------------------  $ Date: Thu, 6 Jan 2005 13:08:59 -0500# From: "John Smith" <a@nonymous.com>hA Subject: Re: Mark Gorham interview in Interex's HP World Magazine , Message-ID: <TYGdnTd5zfgk40DcRVn-gw@igs.net>   Keith Parris wrote:iB > See http://www.openvms.org/stories.php?story=05/01/04/5775466 or5 > http://www.interex.com/hpworldnews/hpw501/news3.jsp  > $ > Some snippets I found interesting: >g$ > "Q: Is OpenVMS growing these days? > H > OpenVMS has been growing for the last year. Weve had four quarters of@ > either single- or double-digit revenue growth. Its been quite > exciting for us."  >cE > This is also the first public mention I've seen of Mark's importantt@ > work and influence beyond just OpenVMS, making changes to HP's@ > policies that benefit HP as they help OpenVMS: "Gorham is alsoB > responsible for programs to grow HP revenue and improve customerC > satisfaction. He is the BCS (Business Critical Systems) Executive@@ > Champion for more than 70 customers worldwide, the BCS CountryC > Champion for the Nordic Countries, and the BCS Government SegmentsE > Champion. Gorham is currently working in the Enterprise Storage andaG > Servers (ESS) War Room, helping to drive end-to-end business models B > and process improvements that systemically improve the worldwide  > business performance for ESS."    " Some snippets I found interesting:H a) The same list of customers trotted out again - Cerner, the exchanges,> Logica.  Who are some of the new users outside of those areas?  F b) "The Swift Stock Exchange has been a great partner and customer forB years. Deutsche [Telekom] a great partner and customer for years."  H Let's see:..."The Swift Stock Exchange'????? SWIFT does diddley with VMS2 these days, and they don't run an exchange either.  @ Deutsche [Telekom] ??? in the "exchange" section of the article.  I Seems to me the article's author knows diddley about VMS, its markets and F customers, and nobody who proofread the article did either. It kind ofJ reminds me of the user manuals translated from the original Cantonese by aH person from India with barely a working knowledge of English. From thereJ it's translated into Swedish and then back to English in Taiwan (sorry for the stereotypes).g  I Other than that....I guess it's the start of some marketing effort at one  level or another.     K Back to the fault-tolerant stuff for a minute......IIRC the old FT810 Vaxen(I ran vanilla VMS. If so, does this mean that if today's VMS is run on a FTd2 Integrity box we VMS users will get FT and DT too?      ! Perhaps the author of the article0   ------------------------------  % Date: Thu, 06 Jan 2005 11:02:08 -0500c- From: JF Mezei <jfmezei.spamnot@teksavvy.com>A Subject: Re: More on Tru64B Message-ID: <1105026730.c6846ff2211d8aae46ecdc6f09b4f47a@teranews>   Bill Gunshannon wrote:& > >  05 FIRST PIC X(30) value 'Three'.+ > >  05 SECOND  PIC X(30) value 'Thousand'.r& > >  05 THIRD  PIC X(60) value spaces. > >mM > > result in THIRD having the value "Three Thousand"  in today's cobol ?????  > F > Don't know about "today's cobol", but in ANSI-74 it would have been: > > >    STRING FIRST, SPACE, SECOND DELIMITED BY SIZE INTO THIRD.  A Are you sure "string" was part of COBOL and not a VAX extension ?   I I don't recall seing this on IBM Cobol. And did STRING automatically trimt$ trailing spaces from stored values ?   ------------------------------   Date: 6 Jan 2005 16:20:21 GMTi( From: bill@cs.uofs.edu (Bill Gunshannon) Subject: Re: More on Tru64, Message-ID: <3456q5F47djs7U1@individual.net>  B In article <1105026730.c6846ff2211d8aae46ecdc6f09b4f47a@teranews>,0 	JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > Bill Gunshannon wrote:' >> >  05 FIRST PIC X(30) value 'Three'.r, >> >  05 SECOND  PIC X(30) value 'Thousand'.' >> >  05 THIRD  PIC X(60) value spaces.  >> >N >> > result in THIRD having the value "Three Thousand"  in today's cobol ????? >>  G >> Don't know about "today's cobol", but in ANSI-74 it would have been:. >> a? >>    STRING FIRST, SPACE, SECOND DELIMITED BY SIZE INTO THIRD.t > C > Are you sure "string" was part of COBOL and not a VAX extension ?P  . As stated above, STRING was added at ANSI-74.    > * > I don't recall seing this on IBM Cobol.   ? I can't imagine IBM doing a COBOL that didn't at least meet thee> standard.  Like most other vendors, they then added extensions; of their own and then lobbied to make them part of the next 	 standard.s  L >                                          And did STRING automatically trim& > trailing spaces from stored values ?  E Well, not meaning to be pedantic, but you didn't include the trailingTE spaces in your strings and I don't remember if COBOL would space fill0F or fill with LOW-VALUES.  In any case, I can do the same thing without the extra Working-Storage with:tC     STRING "Three", SPACE, "Thousand" DELIMITED BY SIZE INTO THIRD.t/ Does what you wanted and saves Working-Storage.   D There is another way using an index to specify the starting position> of an item in the created string that could also eliminate the@ trailing blanks if they are there, but I don't have my referenceC with me and I am unsure of the syntax, but I will provide it toniten) when I get home I it is really necessary.     B COBOL is more powerful than many give it credit for.  At least one@ of the current commercial COBOL vendors claims their compiler isB actually written in COBOL (not something I would brag about, right tool for the job and all that.)D   bill   -- AJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   D   ------------------------------  ! Date: Thu, 06 Jan 05 11:45:25 GMTo From: jmfbahciv@aol.com K Subject: Re: need help in decoding VAXstation 4000/60 console error messageU, Message-ID: <_u2dnY8ENPsys0DcRVn-rA@rcn.net>  $ In article <crhnj4$akl$1@online.de>,G    helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to ,
 reply) wrote: : >In article <oc6dnWpqaJwqnkbcRVn-oQ@igs.net>, "John Smith" ><a@nonymous.com> writes:  >e/ >> >> it seems that (at least) disk 3 is brokenn >> >J >> > Thanks.  After a few power cycles (always leaving the power off for aE >> > couple of minutes), the VAXstation booted (which it is set to dorK >> > automatically if it can) and the disk is now mounted on all 3 nodes ins% >> > the cluster and is working fine.o >> n >> oF >> May be a thermal fault.  Have you opened the case and blown all the >> accumulated dust away?s >t: >Good idea.  I suppose I should do that from time to time.  < Heh.  Folklore had it that a PDP-10 wouldn't work until dust
 was added.   /BAH    ' Subtract a hundred and four for e-mail.s   ------------------------------   Date: 6 Jan 2005 08:23:07 GMTe2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>8 Subject: Re: Need help with user-written routine in SOR$? Message-ID: <DTiotGxQ0bj6-pn2-R7QzXxcMEd1e@dave2_os2.home.ours>a  ? On Tue, 4 Jan 2005 19:46:30 UTC, hoefelmeyer@hotmail.com wrote:s  D > Cool! The structure wrapper must be needed by VMS for some reason,E > then. I was just worried that it was something significant that waseI > glossed over in the docs. Well, that makes it a lot easier for me!  I'mSG > very pleased to have my fears proved groundless. Thank you very much!n > C > A couple of other questions come to mind, with passing pointers - ? > first, since ADRS1 and ADRS2 are pointers to my records, if I-E > dereference them and modify non-key fields in them in my user_equalHH > routine, it would indeed change the actual record, correct? I know theI > answer in C, but am not sure in BASIC, i.e., is my function accessing abH > pointer to the actual record, as does C, or is it a pointer to a local5 > copy of the record? The latter doesn't seem likely.  > D > And if I can, would doing so make the sort choke? I don't see why,H > because I'm not changing keys, but you never know. I'll check this out > empirically. >   F I've no access to my grey wall but IIRC the point to be remembered is F that the user routines are called by SORT/MERGE and the arguments and F the memory holding them belong to it and _not_ the caller of the SOR$ @ routines. I would not meddle with their content in the User_xxx 	 routines.e  F Consider John's example. He used the the 'sort file' interface, he has< no idea about how SORT/MERGE manages the individual records  internally.o  F That said, changing the content of the record(s) might work but don't  change the length.   -- a Cheers - Dave W.   ------------------------------   Date: 6 Jan 2005 08:23:04 GMTw2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>$ Subject: Re: Need UNIX clarification? Message-ID: <DTiotGxQ0bj6-pn2-498EmMzD1XqK@dave2_os2.home.ours>6  > On Tue, 4 Jan 2005 14:30:47 UTC, Kilgallen@SpamCop.net (Larry  Kilgallen) wrote:F   <SNIP>   > D > ASTs have made individual VMS processes multi-threaded from day 1,= > but not with the familiar (to some) Unix programming model.n > D > Only after the addition of that Unix programming model was supportC > added for a single process actually executing on multiple CPUs at B > the same time, but that is not the definition of multi-threaded.  F Indeed, it appears to be one of the reasons why Unix  'fork's so much.   -- i Cheers - Dave W.   ------------------------------   Date: 6 Jan 2005 09:03:04 GMTe2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>$ Subject: Re: Need UNIX clarification? Message-ID: <DTiotGxQ0bj6-pn2-NdRrJGw9Jmg4@dave2_os2.home.ours>t  3 On Thu, 6 Jan 2005 08:23:04 UTC, "Dave Weatherall"  ! <djw-nothere@nospam.nohow> wrote:A  @ > On Tue, 4 Jan 2005 14:30:47 UTC, Kilgallen@SpamCop.net (Larry  > Kilgallen) wrote:e >  > <SNIP> >  > > F > > ASTs have made individual VMS processes multi-threaded from day 1,? > > but not with the familiar (to some) Unix programming model.  > > F > > Only after the addition of that Unix programming model was supportE > > added for a single process actually executing on multiple CPUs at.D > > the same time, but that is not the definition of multi-threaded. > H > Indeed, it appears to be one of the reasons why Unix  'fork's so much. >   C Oops - I thought I'd killed this - sorry for the pollution with an - incomplete thought.    --   Cheers - Dave W.   ------------------------------   Date: 6 Jan 2005 10:24:51 -0800 ( From: "yuccadave" <yuccadave@excite.com>? Subject: NFS volume mappings disappear/not visible after reboot1C Message-ID: <1105035891.131884.215200@f14g2000cwb.googlegroups.com>e  D I just worked out this issue with HP Customer Support, and thought ID would contribute it to the general VMS folklore. (And in case I ever need to find it again.)    ---------------------nD OpenVMS V7.3-2, TCPIP V5.4 (but also true of earlier versions of VMS and TCPIP).v  G NFS volume mappings disappear after reboot. They exist in the permanenta: database, but don't get loaded into the volatile database.  D The problem occurs when NFS is started BEFORE the disks are mounted.; The solution is to mount the disks PRIOR to starting TCPIP.d@ A quick kludge is to issue $ TCPIP GENERATE MAP to load the mapsD manually. This is undocumented, but is the way TCPIP$NFS_STARTUP.COM loads the maps.e  E This is alluded to in SYS$SYSDEVICE:[TCPIP$NFS]TCPIP$MOUNTD_node.LOG,  with entries that look like:G "<timestamp> ERROR: stat: no such file or directory, Cannot stat <map>"rG This can indicate that the disk associated with the map is not mounted.u& Hope this helps someone in the future.   ------------------------------  % Date: Thu, 06 Jan 2005 12:12:52 -0500o From: E Varden <jpps@vif.com>|G Subject: O/T               Re: For JF: Young men kill their circumciserc+ Message-ID: <1105031594.429890@www.vif.com>d   >l   ------------------------------  % Date: Thu, 06 Jan 2005 17:51:55 +0000 . From: Semolina Pilchard <ushat@ukonline.co.uk>K Subject: Re: O/T               Re: For JF: Young men kill their circumciserD8 Message-ID: <qkuqt0lgo0r0d52127ld3vqd8tcgvbe2tv@4ax.com>  B On Thu, 06 Jan 2005 12:12:52 -0500, E Varden <jpps@vif.com> wrote:   >  >>9 That's your most profound post for several years, Varden.h -- n Semu   ------------------------------  % Date: Thu, 06 Jan 2005 09:36:25 -0500 4 From: Forrest Kenney <forrest_dot_kenney@hp_dot.com># Subject: Shared Interrupts questionf* Message-ID: <41DD4CE9.CF44BC31@hp_dot.com>  D     In V8.2 shared interrupts will be supported on the IA64 systems. Sorry, there are% no plans to port the support to Alphad     Forrest Kenney OpenVMSh   ------------------------------  * Date: Thu, 6 Jan 2005 09:32:08 +0000 (UTC)6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)# Subject: Re: TCP/IP mailing problem 0 Message-ID: <newscache$kh2w9i$d04$1@news.sil.at>  q In article <fhoot0dde7m4h70ds0eel04d3260dbh3kj@4ax.com>, Martin Hunt <martin.hunt@fairfaxnz.REMOVE.co.nz> writes:dE >What do you mean by the latest ECO? I can't find anything later thanr >ECO 2.t   Look again. ECO 4 is current.   0 	ftp://ftp.itrc.hp.com/openvms_patches/vax/V7.3/   -- a Peter "EPLAN" LANGSTOEGERl% Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  $ Date: Thu, 6 Jan 2005 10:36:37 -0000* From: "Richard Brodie" <R.Brodie@rl.ac.uk># Subject: Re: TCP/IP mailing problemn2 Message-ID: <crj4bl$h7j$1@blackmamba.itd.rl.ac.uk>  ] "Phillip Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de> wrote in messagee news:crhnti$akl$2@online.de...  I > > When it gets to the recipient, the address appears as ABC@x.y.z (onlyn0 > > the first part is translated to upper case). >bI > They should not object, since according to the RFC it shouldn't matter.e   Not on my reading of it:  
 (RFC 2821)K "The local-part of a mailbox MUST BE treated as case sensitive.  Therefore, Q SMTP implementations MUST take care to preserve the case of mailbox local-parts."    ------------------------------  % Date: Thu, 06 Jan 2005 11:18:32 -0500z- From: JF Mezei <jfmezei.spamnot@teksavvy.com>.# Subject: Re: TCP/IP mailing problem B Message-ID: <1105027716.fe97f28bc13c77ffac688c57fdbb865b@teranews>    Peter 'EPLAN' LANGSTOEGER wrote: > Look again. ECO 4 is current.  > 9 >         ftp://ftp.itrc.hp.com/openvms_patches/vax/V7.3/n  N ECO 4 mentions nothing about fixing the DHCP_GUI which crashes when you try toG edit fields with multiple values (such as DNS servers). And it mentionshG nothing about the IMAP server which was rendered unusable (crashes upondL startup) when ECO 2 was introduced. It also mentions nothing about the wholeJ system crashing when you attempt to start a SLIP interface since TCPIP 5.3 (worked for TCPIP 5.0)   ------------------------------  * Date: Thu, 6 Jan 2005 07:36:21 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)2 Subject: VAXstation 3100: supported under VMS 7.3?$ Message-ID: <crippk$bgo$1@online.de>  E I had a look at the SPD for 7.3-2 ALPHA and 7.3 VAX.  In the list of  H supported systems, I didn't find the VAXstation 3100.  I don't think it H was already retired in a previous version of VMS.  Is this an oversight E in the SPD?  Is the VAXstation 3100 still supported under 7.3?  What i
 about 8.2?   ------------------------------   Date: 6 Jan 2005 09:00:31 -0600<- From: Kilgallen@SpamCop.net (Larry Kilgallen)e6 Subject: Re: VAXstation 3100: supported under VMS 7.3?3 Message-ID: <6KkV15yd9JNs@eisner.encompasserve.org>,  w In article <crippk$bgo$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:eG > I had a look at the SPD for 7.3-2 ALPHA and 7.3 VAX.  In the list of aJ > supported systems, I didn't find the VAXstation 3100.  I don't think it J > was already retired in a previous version of VMS.  Is this an oversight @ > in the SPD?  Is the VAXstation 3100 still supported under 7.3?  - If it is not in the SPD, it is not supported.k  B You have been in this newsgroup long enough that I presume you areG quite familiar with the difference between "supported" and "will work".e   > What about 8.2?o  D If an older system is not supported in some version, it is extremely- unlikely* to be supported in a newer version.h  B Dropping support for a given system allows VMS Development to dropD that system out of the Quality Test and Verification processing thatH must happen before each VMS Version is released.  That is a considerableJ time saving, to the advantage of all those customers running later systems4 who want the new version to be release more quickly.  ? The only people running systems as old as the ones you describeI@ are likely to be VMS hobbyists, who do not buy support contractsA anyway, so whether a given box is supported or not is immaterial.r  F * If there is some customer who wants to buy lots of support contractsL   for a particular older system, I suppose the management at VMS DevelopmentG   might be influenced.  But it is more expensive for VMS Development toaF   support older systems than newer systems, since running a particularI   test suite is going to take longer on an older system.  So the contracteG   you are willing to sign for support should be for a _large_ number ofa   that older system model.   ------------------------------  $ Date: Thu, 6 Jan 2005 17:14:17 -0000* From: "Richard Brodie" <R.Brodie@rl.ac.uk>6 Subject: Re: VAXstation 3100: supported under VMS 7.3?2 Message-ID: <crjrl9$r1s$1@blackmamba.itd.rl.ac.uk>  : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:6KkV15yd9JNs@eisner.encompasserve.org...V_ > In article <crippk$bgo$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove  CLOTHES to reply) writes:aH > > I had a look at the SPD for 7.3-2 ALPHA and 7.3 VAX.  In the list ofK > > supported systems, I didn't find the VAXstation 3100.  I don't think it K > > was already retired in a previous version of VMS.  Is this an oversightdB > > in the SPD?  Is the VAXstation 3100 still supported under 7.3? >n/ > If it is not in the SPD, it is not supported.n  E Normally one would have to assume this was true. However, the VMS SPD M lists discontinued machines as well (and the last version supported, althoughnE not always correctly). The VAXstation 3100 isn't in that list either.    ------------------------------   End of INFO-VAX 2005.012 ************************