1 INFO-VAX	Fri, 19 May 2006	Volume 2006 : Issue 277       Contents: Fixing a Corrupt PCSI Database Re: FreeVMS New release 0.2.10 FreeVMS New release 0.2.10 Incredible! , Openvms system manager - newbie or mid level& Re: Oracle 10G Client Tools on OpenVMS& Re: Oracle 10G Client Tools on OpenVMS& Re: Oracle 10G Client Tools on OpenVMS& Re: Oracle 10G Client Tools on OpenVMS& Re: Oracle 10G Client Tools on OpenVMS# Re: Ping in web server command file  Re: Results of my straw poll.  Re: Results of my straw poll.  Re: Results of my straw poll.  Re: Results of my straw poll.  RE: Results of my straw poll.  Re: Results of my straw poll.  Re: Results of my straw poll.  Re: Results of my straw poll.  Re: Results of my straw poll.  Re: Results of my straw poll. P Re: TCPIP Configuration -TCPIP-E-BIND_NO_ZONEXFR, zone transfer was  unsuccessfu Re: VPM_SERVER strangenessB Re: XP1000 SRM Firmware (was: Re: Digital PWS 500au Firmware V6.9)B Re: XP1000 SRM Firmware (was: Re: Digital PWS 500au Firmware V6.9)B Re: XP1000 SRM Firmware (was: Re: Digital PWS 500au Firmware V6.9)B Re: XP1000 SRM Firmware (was: Re: Digital PWS 500au Firmware V6.9)  F ----------------------------------------------------------------------  % Date: Fri, 19 May 2006 13:32:43 -0400 + From: Steve Matzura <number6@speakeasy.net> ' Subject: Fixing a Corrupt PCSI Database 8 Message-ID: <n50s621c7j71cca86a94rcmq1hvk9fmhls@4ax.com>  E Recently, a former coworker reported to me that during a PRODUCT SHOW B PRODUCT on a VMS 7.32 system, he encountered an error indicating aF missing .PCSI database file for one of the products known to have beenE installed--namely, the latest PTHREADS patch.  HP told him there's no F way to actually repair the PCSI database, but I recommended he attemptF to remove the patch, then re-apply it.  Does anyone have experience in
 this area?   ------------------------------    Date: 19 May 2006 04:32:23 -0700! From: "mariuz" <mapopa@gmail.com> ' Subject: Re: FreeVMS New release 0.2.10 B Message-ID: <1148038343.462303.18070@j33g2000cwa.googlegroups.com>   The main project's page 5 http://www.systella.fr/~bertrand/FreeVMS/indexGB.html   G Disk Images (mentioned in previous post) are created for bochs emulator   http://bochs.sourceforge.net/  % a.img is to boot from floppy in bochs   c.img is disk image to boot from  5 Here is an older how i managed to boot it under bochs ( http://osnews.com/story.php?news_id=8769   ------------------------------    Date: 19 May 2006 04:19:25 -0700! From: "mariuz" <mapopa@gmail.com> # Subject: FreeVMS New release 0.2.10 B Message-ID: <1148037565.159301.37480@j73g2000cwa.googlegroups.com>   New release 0.2.10 at F ftp.nvg.ntnu.no:/pub/vms/freevms (freevms-0_2_10.tgz and linker-0_2_6)  , Disk images are named a.img.gz and c.img.gz.; The USE file or reference to it should accompany downloads. ? (For x86_64 they are named a.img.x86_64.gz and c.img.x86_64.gz) % The README file should be read first.    News:  x86_64:  Better PAL.  PAL SMP support.3 PAL support for 4 modes (but no CLI in supervisor).  All 4 modes used.  i386: 1 PAL support for 4 modes (with CLI in supervisor).  Only 3 modes used.   Bugs/features fixed: x86_64: % Critical kernel stack overflow (PAL). ! Killed off interrupt stack (PAL).  Misc other PAL fixes.  i386: & Killed off Linux semaphores here, too.5 Linux spinlock semantics with pte alloc in syscredel.  Both: # Zero check for image routine start.    ------------------------------  % Date: Fri, 19 May 2006 03:57:49 +0100 ' From: "Knowledge" <knowledge@world.net>  Subject: Incredible!; Message-ID: <newscache$v9sizi$gf9$1@newsfront4.netvisao.pt>                   100% Reliable!    http://theproofonline.com/?8a4y      We Ship WorldWide!) Gurantee 100% Top Quality of All Products  Discreet Packaging & Shipping  Verisign Secure Site!      http://theproofonline.com/?8a4y    ------------------------------  % Date: Fri, 19 May 2006 10:50:42 -0400 " From: "Hal Kuff" <kuff@tessco.com>5 Subject: Openvms system manager - newbie or mid level 0 Message-ID: <126rmq3csaibo80@corp.supernews.com>  K We have an opening for an OpenVMS manager on several Alpha (to be Itanium)  M platforms... good oppurtunity for a newbie or a mid level person.. very open  D to varied levels of experience - however this is not a senior level K position... lots of toys. Position is in Baltimore area...  we have a Reno  A facility and we are open to the right candidate for Reno as well.      Kuff at tessco dot com www.tessco.com     ------------------------------  % Date: Fri, 19 May 2006 09:39:41 -0400 * From: "Syltrem" <syltremzulu@videotron.ca>/ Subject: Re: Oracle 10G Client Tools on OpenVMS / Message-ID: <126rii51fclf24@corp.supernews.com>   ( <ksrich@bellsouth.net> wrote in message 4 news:Yqtag.73031$Jk3.45184@bignews5.bellsouth.net... > 5 > "Earl Lakia" <elakia@hotmail.com> wrote in message  6 > news:qYmdnZbpN8HHt_fZnZ2dnUVZ_tudnZ2d@comcast.com...J >> Anyone tried Oracle 10G client tools (ProFORTRAN and ProC) and SQL PlusG >> on OpenVMS 7.2 or later (Alpha).  In particular is the new TIMESTAMP  >> data type supportted? >> > E > We are testing 10G on OpenVMS 8.2.  We use ProFortran but not ProC. C > I don't remember about the TIMESTAMP data type but there is a big K > gotcha now.  Oracle only supports IEEE for Float data types.  If you have K > isolated code you can use the /float=ieee switch on Fortran.  We weren't   > soH > lucky and are changing our code to convert every floating point number, > back and forth during selects and updates. >  >  > Shael  >    Hi  ( If you are testing, are you a beta site?> Havent's heard OpenVMS 10gR2 is ready yet (Alpha or Integrity)   I'm eagerly waiting for it.    Thanks     ------------------------------    Date: 19 May 2006 16:40:15 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)/ Subject: Re: Oracle 10G Client Tools on OpenVMS , Message-ID: <446df4ef$1@news.langstoeger.at>  \ In article <126rii51fclf24@corp.supernews.com>, "Syltrem" <syltremzulu@videotron.ca> writes:? >Havent's heard OpenVMS 10gR2 is ready yet (Alpha or Integrity)    But 10gR1 is there (for Alpha)   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 19 May 2006 07:51:39 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> / Subject: Re: Oracle 10G Client Tools on OpenVMS C Message-ID: <1148050299.713264.127140@j33g2000cwa.googlegroups.com>    Syltrem wrote:) > <ksrich@bellsouth.net> wrote in message 6 > news:Yqtag.73031$Jk3.45184@bignews5.bellsouth.net... > > 6 > > "Earl Lakia" <elakia@hotmail.com> wrote in message8 > > news:qYmdnZbpN8HHt_fZnZ2dnUVZ_tudnZ2d@comcast.com...L > >> Anyone tried Oracle 10G client tools (ProFORTRAN and ProC) and SQL PlusI > >> on OpenVMS 7.2 or later (Alpha).  In particular is the new TIMESTAMP  > >> data type supportted? > >> > > G > > We are testing 10G on OpenVMS 8.2.  We use ProFortran but not ProC. E > > I don't remember about the TIMESTAMP data type but there is a big M > > gotcha now.  Oracle only supports IEEE for Float data types.  If you have L > > isolated code you can use the /float=ieee switch on Fortran.  We weren't > > soJ > > lucky and are changing our code to convert every floating point number. > > back and forth during selects and updates. > >  > > 	 > > Shael  > >  >  > Hi > * > If you are testing, are you a beta site?@ > Havent's heard OpenVMS 10gR2 is ready yet (Alpha or Integrity) >  > I'm eagerly waiting for it.  >  > Thanks  C The OP didn't specify 10gR1 or 10gR2.  10gR1 has been available for D Alpha VMS V7.3-2 since June 2005.  It was also certified for V8.2 inF March 2006.  Current projected release of 10gR2 (10.2.0.2)  for VMS is- September 2006 according to Oracle's Metalink    ------------------------------    Date: 19 May 2006 18:12:23 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)/ Subject: Re: Oracle 10G Client Tools on OpenVMS , Message-ID: <446e0a87$1@news.langstoeger.at>   In article <1148050299.713264.127140@j33g2000cwa.googlegroups.com>, "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> writes: D >The OP didn't specify 10gR1 or 10gR2.  10gR1 has been available forE >Alpha VMS V7.3-2 since June 2005.  It was also certified for V8.2 in G >March 2006.  Current projected release of 10gR2 (10.2.0.2)  for VMS is . >September 2006 according to Oracle's Metalink  I Assume this shifts to Oct2006 and then we are already one year later than I what the last plan told (Q4CY05). And I thought, every new Oracle version A will be published on every supported platform within 3 months ;-)    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Fri, 19 May 2006 13:18:17 -0400 * From: "Syltrem" <syltremzulu@videotron.ca>/ Subject: Re: Oracle 10G Client Tools on OpenVMS 0 Message-ID: <126rvc1kisbjd16@corp.supernews.com>  , <johnhreinhardt@yahoo.com> wrote in message = news:1148050299.713264.127140@j33g2000cwa.googlegroups.com...  >  > Syltrem wrote:* >> <ksrich@bellsouth.net> wrote in message7 >> news:Yqtag.73031$Jk3.45184@bignews5.bellsouth.net...  >> >7 >> > "Earl Lakia" <elakia@hotmail.com> wrote in message 9 >> > news:qYmdnZbpN8HHt_fZnZ2dnUVZ_tudnZ2d@comcast.com... I >> >> Anyone tried Oracle 10G client tools (ProFORTRAN and ProC) and SQL  
 >> >> PlusJ >> >> on OpenVMS 7.2 or later (Alpha).  In particular is the new TIMESTAMP >> >> data type supportted?  >> >>  >> >H >> > We are testing 10G on OpenVMS 8.2.  We use ProFortran but not ProC.F >> > I don't remember about the TIMESTAMP data type but there is a bigJ >> > gotcha now.  Oracle only supports IEEE for Float data types.  If you 	 >> > have F >> > isolated code you can use the /float=ieee switch on Fortran.  We  >> > weren't >> > so K >> > lucky and are changing our code to convert every floating point number / >> > back and forth during selects and updates.  >> > >> >
 >> > Shael >> > >> >> Hi  >>+ >> If you are testing, are you a beta site? A >> Havent's heard OpenVMS 10gR2 is ready yet (Alpha or Integrity)  >> >> I'm eagerly waiting for it. >>	 >> Thanks  > E > The OP didn't specify 10gR1 or 10gR2.  10gR1 has been available for F > Alpha VMS V7.3-2 since June 2005.  It was also certified for V8.2 inH > March 2006.  Current projected release of 10gR2 (10.2.0.2)  for VMS is/ > September 2006 according to Oracle's Metalink  >   E Right. I was too quick. I think my eyes saw 10g and 8.2 and my brain   registered 10g2  Wishful thinking maybe   Syltrem    ------------------------------    Date: 19 May 2006 08:15:28 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) , Subject: Re: Ping in web server command file3 Message-ID: <iGk9D4mmF$ZL@eisner.encompasserve.org>   b In article <Fk4bg.39092$Hk1.27385@read1.cgocable.net>, "Mike Robinson" <onthost@gmail.com> writes: > < > "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message( > news:446B94B8.552351F8@teksavvy.com...   >>8 >> PLEASE DO NOT POST IN HTML. THIS IS A TEXT NEWSGROUP. > Technically HTML is TEXT.   D    Technically it's all binary.  But how would you say non-HTML text*    without the clumsy phrase I just wrote?   ------------------------------   Date: 19 May 2006 06:22:12 GMT From: healyzh@aracnet.com & Subject: Re: Results of my straw poll., Message-ID: <e4jo6k01hvj@enews1.newsguy.com>  " Tom Linden <tom@kednos.com> wrote:J > On Thu, 18 May 2006 18:48:41 -0700, Bill Gunshannon <bill@cs.uofs.edu>   > G > > What did any of that have to do with the fact that I don't have the I > > hardware to waste (and wouldn't waste it if I did) on a piddling task F > > like serving up documentation?  When you spend as much effort as IE > > have to doing so much with so little you tend to get very frugal.   L I sort of agree in this case (even though I do serve up multiple sets of theJ doc's on my VMS server).  At the same time, other than disk space would itJ really be a problem, it wouldn't put much of a load on the server, and it K would save electricity.  The real advantage to serving it up on VMS is you  % can serve up Bookreader format doc's.   ; OTOH, I think the suggestion that you point the students at G http://www.hp.com/go/vms/docs makes more sense than setting up your own I server to do it.  I'm have the doc's on my server so I can quickly access ? them, plus they're older, and a bunch are in bookreader format.   L > I have a bunch of 4 and 9 GB drives you are welcome to and will be freeingI > up as many as 24 18 GB soon, to which you are welcome.  They are 80 pin  > scsi.   I I would think old decommishioned Unix hardware, or even decommisioned PC  D servers might be a good source of drives.  The hardware is viewed asG garbage, but can be a good source of parts for Alpha's running OpenVMS.   2 > FWIW, I have used 80->68 and 68->50 pin adapters  J I ran for quite a while using an 18GB SCA drive in my PWS433au this way.    J Actually can't the XP1000's use IDE HD's?  Alternately there are the AcardH IDE-to-SCSI converters though they cost money (which is why I don't have any).    			Zane    ------------------------------  % Date: Fri, 19 May 2006 04:08:23 -0400 ' From: Dave Froble <davef@tsoft-inc.com> & Subject: Re: Results of my straw poll./ Message-ID: <o7idnTCRDdqR4fDZRVn-pQ@libcom.com>    Bill Gunshannon wrote:+ > In article <op.s9rqfziyzgicya@hyrrokkin>, ( > 	"Tom Linden" <tom@kednos.com> writes:K >> On Thu, 18 May 2006 15:17:18 -0700, Bill Gunshannon <bill@cs.uofs.edu>   	 >> wrote:  >>L >>> You must have missed the part where I said "no budget, so I use existingI >>> hardware".   Sometimes life isn't as rosy as some would paint it here  >>> in "the ivory tower". C >> I thought you said you were going to pick up a couple of XP1000s  > 8 > Those kinds of deals are never a sure thing until they9 > happen.  But, if I did, first priority would be setting & > up a system for student/faculty use. > > > I just couldn't see wasting hardware like that on a piddling% > task like serving up documentation.  >  > bill >   B You're thinking PC type mentality again.  The Alpha just might do G everything you want, including the documentation, and be loafing while  	 doing so.    --  4 David Froble                       Tel: 724-529-0450> Dave Froble Enterprises, Inc.      E-Mail: davef@tsoft-inc.com DFE Ultralights, Inc.  170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------   Date: 19 May 2006 11:57:25 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)& Subject: Re: Results of my straw poll., Message-ID: <4d5q54F18v9k9U1@individual.net>  , In article <e4jo6k01hvj@enews1.newsguy.com>, 	healyzh@aracnet.com writes:$ > Tom Linden <tom@kednos.com> wrote:K >> On Thu, 18 May 2006 18:48:41 -0700, Bill Gunshannon <bill@cs.uofs.edu>    >>H >> > What did any of that have to do with the fact that I don't have theJ >> > hardware to waste (and wouldn't waste it if I did) on a piddling taskG >> > like serving up documentation?  When you spend as much effort as I F >> > have to doing so much with so little you tend to get very frugal. > N > I sort of agree in this case (even though I do serve up multiple sets of theL > doc's on my VMS server).  At the same time, other than disk space would itL > really be a problem, it wouldn't put much of a load on the server, and it  > would save electricity.     H Do you really thin the 70-100 watts the PC draws would even be a blip onF the radar in a computer room with VAX 7000 and PDP-11.44's in it?  Not0 to mention the rest of the stuff here on campus.  L >                         The real advantage to serving it up on VMS is you ' > can serve up Bookreader format doc's.   H The last Docset I got had two sets. One was bookreader and the other wasI HTML.  My students can read the HTML with any web browser. The bookreader F format would only be accessible from a (very) small subset of machinesH here on campus.  Plus, remember my saying I was going to put 7 CD drives= on the box?  It's not just VMS documentation I need to serve.    > = > OTOH, I think the suggestion that you point the students at I > http://www.hp.com/go/vms/docs makes more sense than setting up your own K > server to do it.  I'm have the doc's on my server so I can quickly access A > them, plus they're older, and a bunch are in bookreader format.   G Network traffic, network outages, network latency.  And that's just the E disadvantages that come immediately to mind.  Because I have to serve F other docs as well, it doesn't make much sense to make them go all the? way to hp.com for some of them when I have them all right here.    > M >> I have a bunch of 4 and 9 GB drives you are welcome to and will be freeing J >> up as many as 24 18 GB soon, to which you are welcome.  They are 80 pin >> scsi. > K > I would think old decommishioned Unix hardware, or even decommisioned PC  - > servers might be a good source of drives.     E Not SCSI.  We haven't used SCSI here for a long time.  Too expensive. G And contrary to popular belief, IDE is just as reliable.  In most cases E the only difference between SCSI and IDE is the controller mounted on 8 the drive.  The actual drive works are exactly the same.  E >                                           The hardware is viewed as I > garbage, but can be a good source of parts for Alpha's running OpenVMS.   H Except that only certain PC grade parts will work with VMS and they tendD to be at the high-end pricewise which is not the end where we do our
 fishing.  :-)    > 3 >> FWIW, I have used 80->68 and 68->50 pin adapters  > L > I ran for quite a while using an 18GB SCA drive in my PWS433au this way.   > L > Actually can't the XP1000's use IDE HD's?  Alternately there are the AcardJ > IDE-to-SCSI converters though they cost money (which is why I don't have > any).   I WHile I appreciate everyone's attempts to help, you always seem to ignore I the place where I keep saying I have $0.00 budget for anything related to D VMS.  I do it because I think it is worthwhile and important for theG students.  That opinion is not shared by anyone here.  That's why I beg H and borrow (I haven't yet resorted to stealing :-) what I can to keep it< going.  I see no likelihood of this changing on the horizon.   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: 19 May 2006 12:04:10 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)& Subject: Re: Results of my straw poll., Message-ID: <4d5qhqF18v9k9U2@individual.net>  / In article <o7idnTCRDdqR4fDZRVn-pQ@libcom.com>, * 	Dave Froble <davef@tsoft-inc.com> writes: > Bill Gunshannon wrote:, >> In article <op.s9rqfziyzgicya@hyrrokkin>,) >> 	"Tom Linden" <tom@kednos.com> writes: L >>> On Thu, 18 May 2006 15:17:18 -0700, Bill Gunshannon <bill@cs.uofs.edu>  
 >>> wrote: >>> M >>>> You must have missed the part where I said "no budget, so I use existing J >>>> hardware".   Sometimes life isn't as rosy as some would paint it here >>>> in "the ivory tower".D >>> I thought you said you were going to pick up a couple of XP1000s >>  9 >> Those kinds of deals are never a sure thing until they : >> happen.  But, if I did, first priority would be setting' >> up a system for student/faculty use.  >>  ? >> I just couldn't see wasting hardware like that on a piddling & >> task like serving up documentation. >>   >> bill  >>   > , > You're thinking PC type mentality again.    H No, I'm thinking $0.00 budget mentality.  After all these years, it just comes naturaly.   C >                                          The Alpha just might do  I > everything you want, including the documentation, and be loafing while   > doing so.   C 1. At this point I do not have an Alpha, so planning on using it is     destined for failure.D 2. Just where in that Alpha box am I supposed to put the additionl 7A    IDE CDROM drives?  Assuming it would even support them.  I can B    pretty much assure you that none of the add-on IDE cards I haveB    is likely to be supported by VMS so that means I can't add them%    even if there was room in the box. D 3. Not so sure it will be loafing as the first thing anyone is goingA    to want run is Java and Eclipse.  I am not sure any Alpha I am B    likely to get at my usual price is going to have the horsepowerD    for that, much less other tasks that are better handled with muchC    lower tech hardware.  If you need to run to the end of the block B    to get the newspaper, do you take the SUV or the bicycle?  Both    CAN do the job.   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: 19 May 2006 08:06:19 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) & Subject: RE: Results of my straw poll.3 Message-ID: <SH+ydvNjGpSV@eisner.encompasserve.org>   ` In article <JFEPKAPBPMDFDBOIANGDOEJEHIAA.dallen@nist.gov>, "Dan Allen" <dallen@nist.gov> writes: > R > Amen brother! Sections M, U, and P of the docset. I've been around both Unix andQ > VMS pretty much from the git-go and I've always listed the VMS documentation as + > one of VMS's bigger advantages over Unix.   H    The worst documentation I had to deal with was the HP-UX man page forH    the magnetic tape interface.  It told me that the minor number of theC    special device file contained bit fields to control auto rewind, H    density, compression, and such but didn't show the layout of the bit J    fields.  I had to experiment with a variety of files in /dev to reverse"    engineer the controls I needed.  H    I think the author assumed if I was looking at minor device numbers I    must have the source.   ------------------------------    Date: 19 May 2006 08:10:27 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) & Subject: Re: Results of my straw poll.3 Message-ID: <n5R95t8gmUiU@eisner.encompasserve.org>   p In article <UOudnUJK2ZH-SfHZnZ2dnUVZ_smdnZ2d@comcast.com>, "Richard B. Gilbert" <rgilbert88@comcast.net> writes: > K > Speaking of information overload, how about "man".  If you need what awk  / > does, you'll never guess what they called it.   J    We all know that.  Late 1960's human interface technology, using names     like grep, awk, and biff.  E    The problem I have is imitation.  I get programmers who grew up on D    UNIX and they want to write C programs with meaningless names andE    undecipherable option letters because that's what they're used to.    ------------------------------    Date: 19 May 2006 08:11:41 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) & Subject: Re: Results of my straw poll.3 Message-ID: <wLCEMFqhJGlG@eisner.encompasserve.org>   W In article <4d49dvF18j815U1@individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes:  > I > As for finding it, if you can describe what you want to do, you can use I > "man -k" or apropos to find the appropriate command and then look it up   > with the standard man command.  F    You can use man -k if the admin has set up that data base.  You canD    set it up if you're the admin.  You're SOL if the admin never had    a use for man -k.   ------------------------------    Date: 19 May 2006 08:07:24 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) & Subject: Re: Results of my straw poll.3 Message-ID: <D+pYqApAhyiu@eisner.encompasserve.org>   f In article <G5ydnY6eFowtW_HZ4p2dnA@comcast.com>, "Richard B. Gilbert" <rgilbert88@comcast.net> writes: > J > It also creates jobs for support people.  How many PC support people do D > you suppose there are for every VMS person?  Is there any company K > employing ten or more persons without a help desk or a PC support person?   ;    One of my close friends made a career out of PC support.    ------------------------------   Date: 19 May 2006 13:49:51 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)& Subject: Re: Results of my straw poll., Message-ID: <4d60nvF18ts8cU1@individual.net>  3 In article <SH+ydvNjGpSV@eisner.encompasserve.org>, > 	koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes:b > In article <JFEPKAPBPMDFDBOIANGDOEJEHIAA.dallen@nist.gov>, "Dan Allen" <dallen@nist.gov> writes: >>  S >> Amen brother! Sections M, U, and P of the docset. I've been around both Unix and R >> VMS pretty much from the git-go and I've always listed the VMS documentation as, >> one of VMS's bigger advantages over Unix. > J >    The worst documentation I had to deal with was the HP-UX man page forJ >    the magnetic tape interface.  It told me that the minor number of theE >    special device file contained bit fields to control auto rewind, J >    density, compression, and such but didn't show the layout of the bit L >    fields.  I had to experiment with a variety of files in /dev to reverse$ >    engineer the controls I needed. > J >    I think the author assumed if I was looking at minor device numbers I >    must have the source.  F Unless HP-UX became even worse over the years than it was the one time; I was forced to use it, that should not have been an issue.   G There are separae device names that allow access to all of the features F supported by a particular tape interface.  And that goes back at least as far as Ultrix-11.& Extracted from the Ultrix-11 man page:<       The files /dev/mt?  are 800bpi; /dev/ht?  are 1600bpi;        /dev/gt?  are 6250bpi. ?       The files /dev/ht?, /dev/tk?, /dev/tm?, and /dev/gt?  are @       normally rewound when closed, files beginning with the 'n'6       prefix are not rewound when closed (for example,       /dev/nrht0).    J Looking at FreeBSD this convention is still in use with additional entriesI for things like compression and even wether or not to auto eject the tape  after rewind on close.   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: Fri, 19 May 2006 10:27:34 -0400 # From: sol gongola <sol@adldata.com> & Subject: Re: Results of my straw poll.0 Message-ID: <1148048883.804084@nntp.acecape.com>   Bill Gunshannon wrote:, > In article <446D00A5.6060503@comcast.net>,2 > 	bradhamilton <bradhamilton@comcast.net> writes: >> Bill Gunshannon wrote: > >>> In article <UOudnUJK2ZH-SfHZnZ2dnUVZ_smdnZ2d@comcast.com>,: >>> 	"Richard B. Gilbert" <rgilbert88@comcast.net> writes: >> [...]N >>>> Speaking of information overload, how about "man".  If you need what awk 2 >>>> does, you'll never guess what they called it.M >>> Ummm....  that's not information overload.  Information overload would be L >>> if asking for a particular man page just sent all of them to your screen >>> every time.  >>> K >>> As for finding it, if you can describe what you want to do, you can use K >>> "man -k" or apropos to find the appropriate command and then look it up " >>> with the standard man command.G >> In the context of this thread, (using as few "outside" resources as  I >> possible to get "help") awk may not be the best example; in the first  J >> few paragraphs of "man awk", there is a reference to an "outside" book I >> which supposedly provides complete information on using this language.  >>! >> "Complete" docs, indeed...	:-)  > E > So, if I type "HELP COBOL" it's going to give me the whole language  > reference, too?  >    > bill > 4 Don't know about cobol but "help fortran statements"5 gives you an awful lot of the fortran language manual  and there is a lot more.  " I presume that cobol has likewise.   ------------------------------  + Date: Fri, 19 May 2006 11:06:25 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)Y Subject: Re: TCPIP Configuration -TCPIP-E-BIND_NO_ZONEXFR, zone transfer was  unsuccessfu $ Message-ID: <e4k8rh$oo1$2@online.de>  E In article <otSdnfjoeNQnevHZRVn-qA@comcast.com>, "Richard B. Gilbert" ! <rgilbert88@comcast.net> writes:    % > My Linksys BEFSR81 router does not  H > implement the full DHCP protocol so I can't query it for just the DNS D > servers.  I'm hoping to find a Cisco SOHO router at a price I can  > afford. . . .   I I have a similar router I use for other reasons (primarily because I can  = extract the WAN address from it via LYNX).  However, the big  D disadvantage, which I don't have with other DSL routers, is that it H cannot itself be a nameserver for VMS.  (With other routers, I can just I set up the router as a nameserver in VMS and it will forward requests to  E whatever nameservers it gets over DHCP.  With the LINKSYS, I can see  G what nameservers it gets from the WAN (these change from time to time)  ( and I enter these as nameservers on VMS.   ------------------------------  # Date: Fri, 19 May 2006 14:17:06 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com># Subject: Re: VPM_SERVER strangeness 0 Message-ID: <Crkbg.808$7u2.460@news.cpqcorp.net>  / Phillip Helbig---remove CLOTHES to reply wrote: ) > ...VPM server was showing a few hundred ) > thousand page faults and 0 CPU usage... F > Another cluster, same VMS and patch level, shows no problems at all.I > I restarted the VPM server on the system with problems.  No change: it  * > immediately starts throwing page faults.  H    That two OpenVMS systems are at the same revision level is certainly F interesting and useful, but knowing that both are at the most current F level is arguably more interesting.  (The former implies a difference H between the box that doesn't involve ECO kits, while the latter implies F the potential for a new and as-yet unresolved problem within OpenVMS.)      VPM via DECnet or IP?  $    OpenVMS version and architecture?      How was VPM started?   G    Different system default quotas?  (That case shouldn't hit VPM, but  H I've seen that trip various applications over the years -- depending on B the system default quotas can lead to odd application differences 7 between two otherwise identical systems, for instance.)   B    There are ECOs available for VPM-related problems for specific  OpenVMS releases.   G    I'd start here by getting the boxes current on ECO kits, but that's  H obviously also a "boilerplate" answer.  There has been various cases of A odd manifestations of problems over the years, and cases where a  H mandatory ECO kit can fix a low-level problem that triggered all matter E of oddness across disparate higher-level components.  The TCP/IP NFS  E server corruption bug of a couple of years back was one such classic  I example.  You might not assume that an NFS bug could clobber an entirely  I distinct application calculation, in a process environment that makes no  G use of IP or of NFS.  This, however, is one of the reasons why we have   mandatory ECO kits.    ------------------------------  # Date: Fri, 19 May 2006 11:38:12 GMT 5 From: rdeininger@mindspringdot.com (Robert Deininger) K Subject: Re: XP1000 SRM Firmware (was: Re: Digital PWS 500au Firmware V6.9) Z Message-ID: <rdeininger-1905060738080001@dialup-4.233.173.37.dial1.manchester1.level3.net>  N In article <op.s9rdgyt8zgicya@hyrrokkin>, "Tom Linden" <tom@kednos.com> wrote:  K >On Thu, 18 May 2006 10:16:11 -0700, Steven M. Schweda <sms@antinode.org>    >wrote:  > K >>    I had no trouble upgrading the firmware on my XP1000 (500MHz) systems H >> when I got them.  As I recall, I used an Alpha Firmware Update CD-ROMH >> (probably one from a Non-Commercial Tru64 UNIX kit).  (When I got theJ >> systems, the firmware couldn't identify an ELSA GLoria graphics card byH >> name, for example.  Now, it just can't identify an Ati Radeon 7500 byK >> name.)  I get firmware-related complaints only when booting VMS versions  >> after V7.3-2.6 >> alp $ write sys$output f$getsyi( "CONSOLE_VERSION")	 >> V5.9-1  > K >No, you wouldn't.  The point was to get something later, 6.x or 7.x, which F >had additional features to which I referred.    I wonder if the majorJ >firmware version was originally intended to corresponfd to the chip, e.g.L >EV5, etc.  BTW, saw somewhere, don't remember where now, but reference to   >an L >XP1000 at 750MHz with EV67, wonder if that ever got past a powerpoint slide
 >or whatever.   E There seems to be a great deal of confusion and misinformation flying D around here.  I think folks may be mixing together several different7 issues which are really only slightly related, at best.   A 1. Firmware version numbering in TOTALLY unrelated for systems in F different hardware families.  Lamenting the lack of V7.something for aI Digital Personal Workstation, for example, is silly.  Version number does / NOT relate to functionality or feature content.   B 2. The version number of the SRM firmware is unrelated, except forJ occasional coincidences, to the version number of the "quarterly" firmwareH CD.  The version number of the CD is irrelevant, except for figuring out which CD you have.  H 3. VMS checks the SRM version against a look-up table at boot time.  YouH might see a warning, (if you don't have the recommended minimum version)E or in extreme cases a refusal to boot (if you don't have the required J minimum version).  (An undocumented boot flag will bypass the check.)  TheB look-up table only has granularity down to the "sub-family" level.  E 4. There is one case among all the alpha systems VMS supports where a F system's FW doesn't match at the sub-family level.  That is the CompaqH Professional Workstation XP1000.  The last version available is V5.9-1. C VMS has an entry in the look-up table that is correct for the other F members of the sub-family, but not the XP1000.  Thus the "recommended"I minimum for the XP1000 is higher than the installed firmware, and you get G a warning.  The "required" minimum for this family will likely never be F raised past V5.9-1, so the warning is the worst that will ever happen.  I 5. The XP1000 firmware situation, and the VMS warning, are known and have I been documented in the VMS release notes for a while now.  RTFM is always  a good idea.  E Customizing the firmware check for XP1000 to eliminate the warning is J fairly low priority, so it may not happen anytime soon.  (Fixing the checkJ is surprisingly non-trivial because of the way the alpha- and I64-specificI pieces of this module interact.  And the module is/was changed frequently G for I64.  The alpha fix has been done, twice that I know of, only to be D rendered irrelevant before it could be checked in by fast-moving I64@ changes.  The module is overdue for a swamp-draining, it seems.)  J 6. The XP1000 systems were the only members of their family to come from aC different design group (the old workstation group).  That group was F re-organized out of existence around the time the XP1000 shipped.  TheI AlphaServer group inherited the XP1000. The firmware source code pool and J build environment were archane, unique, and like much of the XP1000 stuff,< the documentation did not survive the reorganization intact.  E The last I heard, the XP1000 firmware is buildable, but there was low J confidence that the build would exactly match V5.9-1 as a starting point. C So the short list of "annoyance" problems could be removed, but the I firmware would need a full-on requalification because of the re-invention F of the build environment.  Little demand, little benefit to customers,F high risk for customers, no revenue for HP, thus no new firmware build	 expected.   I 6. Hardware support, and more specifically boot support, for a particular H I/O card depends on a lot of things.  One of those is support in the SRMB firmware.  Another is basic compatibility of the card with the PCIF environment of the system.  Last, of course, is qualification testing.  D The I/O implementation in the XP1000 differs from the other "normal"H family members in weird ways.  To support new I/O cards, the alphaserverH folks would have had to sort out the problems on a system they inheritedG and did not have much experience with.  I think that would have knocked ? most new cards out of consideration, EVEN IF the firmware build I environment had been "easy".  There may be thermal and mechanical worries  for some newer cards as well.    ------------------------------  % Date: Fri, 19 May 2006 07:48:43 -0700 # From: "Tom Linden" <tom@kednos.com> K Subject: Re: XP1000 SRM Firmware (was: Re: Digital PWS 500au Firmware V6.9) ) Message-ID: <op.s9szfhtdzgicya@hyrrokkin>   6 On Fri, 19 May 2006 04:38:12 -0700, Robert Deininger  % <rdeininger@mindspringdot.com> wrote:   K > In article <op.s9rdgyt8zgicya@hyrrokkin>, "Tom Linden" <tom@kednos.com>    > wrote: > K >> On Thu, 18 May 2006 10:16:11 -0700, Steven M. Schweda <sms@antinode.org> 	 >> wrote:  >>F >>>    I had no trouble upgrading the firmware on my XP1000 (500MHz)   >>> systems I >>> when I got them.  As I recall, I used an Alpha Firmware Update CD-ROM I >>> (probably one from a Non-Commercial Tru64 UNIX kit).  (When I got the K >>> systems, the firmware couldn't identify an ELSA GLoria graphics card by I >>> name, for example.  Now, it just can't identify an Ati Radeon 7500 by E >>> name.)  I get firmware-related complaints only when booting VMS    >>> versions >>> after V7.3-2. 7 >>> alp $ write sys$output f$getsyi( "CONSOLE_VERSION") 
 >>> V5.9-1 >>I >> No, you wouldn't.  The point was to get something later, 6.x or 7.x,    >> whichH >> had additional features to which I referred.    I wonder if the majorI >> firmware version was originally intended to corresponfd to the chip,    >> e.g. K >> EV5, etc.  BTW, saw somewhere, don't remember where now, but reference    >> to  >> an J >> XP1000 at 750MHz with EV67, wonder if that ever got past a powerpoint   >> slide >> or whatever.  > G > There seems to be a great deal of confusion and misinformation flying F > around here.  I think folks may be mixing together several different9 > issues which are really only slightly related, at best.  > C > 1. Firmware version numbering in TOTALLY unrelated for systems in H > different hardware families.  Lamenting the lack of V7.something for aK > Digital Personal Workstation, for example, is silly.  Version number does 1 > NOT relate to functionality or feature content.  > D > 2. The version number of the SRM firmware is unrelated, except forE > occasional coincidences, to the version number of the "quarterly"   
 > firmwareJ > CD.  The version number of the CD is irrelevant, except for figuring out > which CD you have. > J > 3. VMS checks the SRM version against a look-up table at boot time.  YouJ > might see a warning, (if you don't have the recommended minimum version)G > or in extreme cases a refusal to boot (if you don't have the required J > minimum version).  (An undocumented boot flag will bypass the check.)    > The D > look-up table only has granularity down to the "sub-family" level. > G > 4. There is one case among all the alpha systems VMS supports where a H > system's FW doesn't match at the sub-family level.  That is the CompaqI > Professional Workstation XP1000.  The last version available is V5.9-1. E > VMS has an entry in the look-up table that is correct for the other H > members of the sub-family, but not the XP1000.  Thus the "recommended"K > minimum for the XP1000 is higher than the installed firmware, and you get I > a warning.  The "required" minimum for this family will likely never be H > raised past V5.9-1, so the warning is the worst that will ever happen. > K > 5. The XP1000 firmware situation, and the VMS warning, are known and have K > been documented in the VMS release notes for a while now.  RTFM is always  > a good idea. > G > Customizing the firmware check for XP1000 to eliminate the warning is H > fairly low priority, so it may not happen anytime soon.  (Fixing the   > check A > is surprisingly non-trivial because of the way the alpha- and    > I64-specificK > pieces of this module interact.  And the module is/was changed frequently I > for I64.  The alpha fix has been done, twice that I know of, only to be F > rendered irrelevant before it could be checked in by fast-moving I64B > changes.  The module is overdue for a swamp-draining, it seems.) > L > 6. The XP1000 systems were the only members of their family to come from   > a E > different design group (the old workstation group).  That group was H > re-organized out of existence around the time the XP1000 shipped.  TheK > AlphaServer group inherited the XP1000. The firmware source code pool and G > build environment were archane, unique, and like much of the XP1000    > stuff,> > the documentation did not survive the reorganization intact. > G > The last I heard, the XP1000 firmware is buildable, but there was low K > confidence that the build would exactly match V5.9-1 as a starting point. E > So the short list of "annoyance" problems could be removed, but the K > firmware would need a full-on requalification because of the re-invention H > of the build environment.  Little demand, little benefit to customers,H > high risk for customers, no revenue for HP, thus no new firmware build > expected.  > K > 6. Hardware support, and more specifically boot support, for a particular J > I/O card depends on a lot of things.  One of those is support in the SRMD > firmware.  Another is basic compatibility of the card with the PCIH > environment of the system.  Last, of course, is qualification testing. > F > The I/O implementation in the XP1000 differs from the other "normal"J > family members in weird ways.  To support new I/O cards, the alphaserverJ > folks would have had to sort out the problems on a system they inheritedI > and did not have much experience with.  I think that would have knocked A > most new cards out of consideration, EVEN IF the firmware build K > environment had been "easy".  There may be thermal and mechanical worries  > for some newer cards as well.   I Well that pretty well sums it up.  The msg never really bothered me.  All I I wanted was WWIDMGR support.  Oh well.  BTW was there another system a    server, ? 900 or such, that used some of the same hardware as the XP1000?    ------------------------------  % Date: Fri, 19 May 2006 18:44:14 +0200 / From: Paul Sture <paul.sture.nospam@hispeed.ch> K Subject: Re: XP1000 SRM Firmware (was: Re: Digital PWS 500au Firmware V6.9) ; Message-ID: <47da8$446df5df$50db5015$25581@news.hispeed.ch>    Tom Linden wrote:     ) > BTW was there another system a  server, A > 900 or such, that used some of the same hardware as the XP1000?   H There was a workstation known as XP900. I had one at work at one point, 7 though I don't think it actually _said_ XP900 anywhere.    ------------------------------  # Date: Fri, 19 May 2006 16:51:04 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>K Subject: Re: XP1000 SRM Firmware (was: Re: Digital PWS 500au Firmware V6.9) 0 Message-ID: <YHmbg.827$tJ2.474@news.cpqcorp.net>   Tom Linden wrote:   % > All I wanted was WWIDMGR support.     %    That's not likely going to happen.   H    In the Alpha product line, members of the DS, ES and GS series boxes F are the targets for most (all?) new work and most (all?) new testing. 5 Older boxes are not seeing the same sorts of updates.   ! > BTW was there another system a  I > server, 900 or such, that used some of the same hardware as the XP1000?   G    Still digging for a way to get this, eh?  :-)  At a platform level,  F I'm not aware of any such sharing with the AlphaStation XP1000 series F with any other boxes.  (As was the case of several of the workstation G products, they could be entirely unique and shared no commonality with  5 any of the contemporary products in the server line.)   H    Here, I expect you are confusing the AlphaStation XP1000 workstation B box with the server platform that has variously been known as the > AlphaStation VS10, AlphaStation XP900, AlphaStation DS10, and I AlphaServer DS10 series, depending on various options configured, and on  - the particular marketeering efforts underway.   I    One of the other workstations, the Ultimate Personal Workstation, was  H a close platform relative to the AlphaServer 1200 series.  (Personally, H I like to think of the AlphaStation GS1280 as the ultimate workstation, < but I'd first need sufficient cribbing to shore up my desk.)   ------------------------------   End of INFO-VAX 2006.277 ************************                                                                                                                                                                                                                                                                                                                                                                                                                                                            kX;1J4ݝ(
n49]}NՅǡ䰁w<2GiEhȟ&ṕBIqڤ)@-w}`q}	dJeMu:	oxk#}PIG JvE~EA A%FU{Ħ~ݭmͯq8)kcA8HD4@z >Gp$iOynݒ45a6N0Xibx(FEz9nKQKx%ȕTE` Ms}28>3^W.Y#U]5*D4ϻe~TsFyzys_ӿ{S
c.I\?90 މzמ<a_yͫ@Ip>$k11ֶm JwFCwOr7y@~pW0>m~4U
РЉ
/),Um6-.ЋS]@Tq8{ Mz_I (86opB۔0Rʕ!{dP/yH(0"mwsԄy_E;飪_~ݩ~(j {i\TT=C
炫tXt~Nxz0C.@7xs7	N:eHjRr.)F^ky~Beg}|&QO݋/-?h8mhY(I]"R P^Ua8ݭu[\hޖ{م@)܊WrcGUcFw[ýZiZiJA.FՃ2xDk*
\ARzס~ͩSG{2B[(4)óN{Gh8
M>숔w]2=$2PwQNbi";bXKm^S~٪\@DaCtvwzeyy(<D\+cP1dր^?VCԽaW {|	.ڲ5S-Z5FzRj)CCYaa)U{ܟՠiP<,Z5kqPHF$"mRd_F3A'Pw.ς+Yq!>d_f
Xr{Lz_nV~C1hg(ZQ:01kM2v|>r2|mmup?˖a?E~>ܾ4}TƧsI:.kid~2'OAڋ"&d=%Ͼsld[wpƃdFW76%9Iy e(tꪧ
$|
rSI@
P( t2x6|2z_xŵ򲿇jWL*w|qD!
}·țr$)fk !]#
ROio0ם`h<VI؟ p)ᩰh`:ߣ("T7_zgU
bY	Vi)8KvDY;/Gi5NVp)LhEQ
Ê"EWǶaǣT@ʰAagm}'oe[$C(kQ7csm+ctw𽇨Ǟw]Qpdlrd-9/+j {Q<<DRWIQ	1RƂg4 `JAH(Ht]'(Nb%ftKTJvChF/
w*XyӘV<NaJ8UA[ۊq
\76Ja
XYJǔxX^Ay	h^+-F,!EJ	ĝkR[n++Ny	xcPW,H1Z1wKU
ljcz]USJiKFe"u%ЍZj 2 3 v9ȵE ߘS!6UEޠ39ڼ20uW敁)eJ5G3jn!\
!-6еE
!͹>,ʍy61Л"rR0睕p:N	]ϟ2Wy`"+7
G]p]!GTWj*Sww5Ud;5Rs]mn?Ӄ|0(C>uC'x/+B
{/UFoBW
9UFoBZ*2
CfY8*2w"q\]PgynCig_f\KU'
P``37Ԃ$LF6惯4E-G
pGF{8'6=
`yO+1\E lugZ)VrDg3r¯,
L_~O/zFw~XwfV7=bʓ<r͢:YiUnqTagu峤_7l>6o}oX=Еy)@aJwVy@a0yƔ%iʕOY[7-tjb`xVx<\VǸkHaYn̅jHOYB5+_,1re[YhVZo|:,ue.`k<OxO HJ =5K7Y<KM{йK@V+!,-FOHՐni%Lr}0])g	rnbsq_w`70Lv,=e蚄GIW
f:'a4mrXeipcvrau#_Vܜ阮
ir5gQ׏3fY]mrQ(\:Uζzoܧl̶2!Vө^IH-fyI#ֆJ1]f/ ߠɜ_K^[E~V=S-ѥ7L ҵ7t3.6w\a
7!4ESTB{1KwNUz9]%93fx,ϝiK)rPߵ2/BԯQ{6XЩhA,ҝS^ymƂY3<gOrr[<Poe7c܋ժ)p%WCùؗK1A5%|q9BxEWKj˕/B	1R+ٺj5GN{gf7b-/WʐۼX Z*?u1_Uf_7_ooص[2Zq-0<Q349qZ95Y&drw3"%Souxas
iUQ)ڹA׮T)|4~7NSy=[)B7V,
~,](duBBQ4WZ%W
%;djeh+3z6cW)W;6jΓݻڦ2 T{2tF_hgW/zuNQ5gQa:E)^9E