INFO-VAX Thu, 21 Feb 2008 Volume 2008 : Issue 103 Contents: Alphaserver DS10L 617Mhz Re: Another Alpha turned off... Re: Another Alpha turned off... Re: Another Alpha turned off... Re: Another Alpha turned off... Re: Does dism/unload spin down a disk? Re: Emacs Re: Emacs Re: Emacs Re: Errors during shadow set merge Re: Errors during shadow set merge Re: regex within a DCL procedure Re: regex within a DCL procedure Re: Semi OT: Feedback to HP Re: TU58 cartridges Re: VAX BASIC, file specs, and command line arguments VAXstation 3100, TK50 Tape Drive and LA50 Printer Re: VMS license fees? ---------------------------------------------------------------------- Date: Wed, 20 Feb 2008 15:48:54 -0500 From: "David Turner, Island Computers" Subject: Alphaserver DS10L 617Mhz Message-ID: <13rp4hkhek4odde@news.supernews.com> If anyone here is getting rid of Alphaserver DS10L 617Mhz systems in quantity, then please call us Thanks -- David B Turner Island Computers US Corp 1207 East Highway 80 Suite D Tybee GA 31328 Toll Free: 877-6364332 x201 Intl: 912 786 8501 x201 Fax: 912 786 8505 E: dturner@islandco.com W: http://www.islandco.com The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. ------------------------------ Date: Wed, 20 Feb 2008 21:22:28 -0500 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= Subject: Re: Another Alpha turned off... Message-ID: <47bce059$0$90267$14726298@news.sunsite.dk> Neil Rieck wrote: > My employer still has lots of VAXs (8550, 3500, 4300, etc.) and older > Aphas (2100, 4100, etc) that just refuse to die and, because marketing > people now control the purse strings at most companies, will probably > never be replaced anytime soon. A 8550 !! That must be 20 years old. Arne ------------------------------ Date: Thu, 21 Feb 2008 03:20:47 GMT From: Michael Austin Subject: Re: Another Alpha turned off... Message-ID: Arne Vajhøj wrote: > Neil Rieck wrote: >> My employer still has lots of VAXs (8550, 3500, 4300, etc.) and older >> Aphas (2100, 4100, etc) that just refuse to die and, because marketing >> people now control the purse strings at most companies, will probably >> never be replaced anytime soon. > > A 8550 !! > > That must be 20 years old. > > Arne Yeah, I remember working on those things 20+ years ago :) ------------------------------ Date: Wed, 20 Feb 2008 20:03:45 -0800 (PST) From: Jerry Eckert Subject: Re: Another Alpha turned off... Message-ID: <15be227a-1f36-4b7c-bde6-a3e890374b2a@b29g2000hsa.googlegroups.com> On Feb 16, 4:17 pm, Michael Austin wrote: > It was a sad day for me today as I completed the final backup and making > sure everything I needed was removed from my trusty Alpha 2100 that has > been running firstdbasource.com and spacelots.com for the past 8-9 > years. I purchased (or traded services for systems) 2 Alpha 2100's > during 1999. Both had just been retired at 2 separate Charlotte-based > companies and had been running at those sites for 4-5 years at that > time. I lost one of them about 3 years ago - bad I/O board and it has > been sitting silent acting as storage unit for a monitor/keyboard of the > other server. During Christmas week, I found 2 inexpensive DS10L's that > have taken the place of the 2100's. The "good" 2100/275 may live yet > again as a small Samba file server for a local law firm, but that is > still being negotiated. (hey, I may even make back the $1K I paid for it > :) ). The other will be taken to a local computer recycling center for > disposal after cannibalizing any remaining boards. (The SCSI card is now > in my DS10L :)) > > DEC made the very best hardware in the business. I do not see ANY > vendor that even comes close to competing. Along with the 2 2100's, I > also have been running a |d|i|g|i|t|a|l| Starion 266MhzPentI+32Mb mem. > I purchased it in '97 from a Frye's Electronics in Phoenix and it had > been a floor demo that ran from the time they received it in 1995 until > I bought it. In 1999, I wiped Windows95 off of it and installed Caldera > Linux. It's sole purpose in life since 1999 is to keep my DSL IP > address in sync with my Dynamic DNS provider ZONEEDIT.COM In 2000 the > primary port on the IDE controller died in such a way that there was no > more "C:" drive. I created a boot-floppy that stays in the floppy drive > and boots, then turns control over to the D: drive... It has been doing > this now for 8+ years - headless. I have a feeling the Starion is dying > as the fan gets loud at times and the box reboots itself every couple > months. I have a feeling my 6 year old Dell box will replace its > functionality - but do not think it will last as long as the Starion > has... almost 13 years - almost as long as the 2100's. > > They have served me well -please pause for a moment of silence... > > Long Live Alpha. I can relate. Just this week we retired a VAX 4000-105A that had been up continuously from September 27, 2001 until July 25, 2007 -- 2127 days. Its rack-mate was shut down after a mere 1538 days. Both went down for power system maintenance in the data center. Had it not been for that, it's quite likely the first would have reached 2336 days when it was retired. OpenVMS V7.2 on node F332 25-JUL-2007 20:06:29.85 Uptime 2127 16:34:01 System last booted: 27-SEP-2001 02:44:53.84 Jerry ------------------------------ Date: Wed, 20 Feb 2008 22:35:30 -0800 (PST) From: Neil Rieck Subject: Re: Another Alpha turned off... Message-ID: <33dfa0ef-df89-49f5-9282-8982d95a9bb2@72g2000hsu.googlegroups.com> On Feb 20, 9:22=A0pm, Arne Vajh=F8j wrote: > Neil Rieck wrote: > > My employer still has lots of VAXs (8550, 3500, 4300, etc.) and older > > Aphas (2100, 4100, etc) that just refuse to die and, because marketing > > people now control the purse strings at most companies, will probably > > never be replaced anytime soon. > > A 8550 !! > > That must be 20 years old. > > Arne You are correct. I think they (two large dual-host clusters; one in Toronto and the other in Montreal) were installed in 1986. I've tried informing managment that they could save a ton of money by just reducing their power and cooling requirements but it all falls on deaf ears. Part of the foot-dragging is because operational costs come out of someone else's budget; other problems are due to multi-partner outsourcing (all party's expect to get rich on an upgrade). We all live in Dilbert land. Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/ ------------------------------ Date: Thu, 21 Feb 2008 02:27:37 +0100 From: "P. Sture" Subject: Re: Does dism/unload spin down a disk? Message-ID: In article <47B5A4EE.6030006@comcast.net>, "Richard B. Gilbert" wrote: > JF Mezei wrote: > > DSSI disks had a function to turn on the fault light manually in order > > to identify a drive. But this may not be of much help to you. > > > > Depending on the disk generation, some drives had very loud arm > > movements. With such drives, doing a DIR/FULL disk:[000000...]*.*;* > > would let you go and listen to which drive was always active. > > ISTR the HSZ series controllers had some such feature. The command was > "locate". ISTR the HSJ controllers having the locate command too. -- Paul Sture Sue's OpenVMS bookmarks: http://eisner.encompasserve.org/~sture/ovms-bookmarks.html ------------------------------ Date: 20 Feb 2008 23:06:26 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Emacs Message-ID: <47bcb272$0$25018$607ed4bc@cv.net> In article <47bc635b$0$10271$c3e8da3@news.astraweb.com>, JF Mezei writes: >VAXman- @SendSpamHere.ORG wrote: > >> "Well my son, life is like a beanstalk, isn't it?" >> >>http://tmesis.com/drat.html > >I checked out you Sanyo manufactured VAXbar at: > >http://www.tmesis.com/zymological_zealotry/ > >Out of curiosity, how long does the keg last ? Or is your consumption so >high that you never worry about it going stale ? Guinness comes in a 50L keg. That's about 13.2 USgals. The typical keg of domestic US swill comes in a 15.25 USgal keg. The Guinness keg will provide me with about 106 USpints or 84 imperial pints. It lasts me 30-40 days so it does not go south. That all depends on whether or not Mrs. VAXman joins me imbibing. >Is there an explanation for the need to mix N2 and CO2 to produce the >VAXman ingestible dark gold elixir ? ABSOLUTELY! Contrary to popular mythconception, Guinness *is* a carbonated beer. When properly carbonated, it should have about 1.2 volumes of CO2 dissolved in it. The higher the pressure, the more CO2 will dissolve. CO2 readily dis- solves into solution; N2 does not. When a pint of Guinness is poured, the Guinness is forced through a faucet with a restrictor. This restrictor is a tiny metal disk with 5 pinholes. The purpose of this is to cause the CO2 to come out of solution and create that luscious thick creamy head. However, the tiny holes require a large push to get the beer through it. If you increase the CO2 pressure to push the beer through the restrictor, too much CO2 would dissolve into the beer and all you would get is head (there's a joke in there but I'll refrain). So, to get the necessary pressure to PUSH the beer, you use N2 which will not readily dissolve into solution. At 4deg.C (proper pumping temperature for Guinness) the CO2 pressure is about 8PSI. The pressure needed to force the beer through the restrictor is about 30PSI. Hence, the N2 mix. >And does the stuff actually come from Ireland, or is there a brewery in >the USA ? Bottled Guinness, in North America, is contract brewed by Labatts in Ca. The kegs I get are imported from Ireland. They maintain the Guinness tap coupler on the kegs too. You need a special tap for Guinness kegs. They do not use the American Sankey tap! >More importantly, in the winter, do you move it indoors ? Or is the >hardware capable of heating the contents to maintain the proper >temperature ? That photo was taken when the cooler was moved out for a backyard party. It spends most of its time in my basement. This is a photo of my 200mWatt laser firing in the basement. You can see the Guinness kit in the "limelight" of the DPSS laser beam. http://www.tmesis.com/pix/200mWatt-DPSS-Laser.JPG -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Wed, 20 Feb 2008 19:40:32 -0500 From: JF Mezei Subject: Re: Emacs Message-ID: <47bcc8bf$0$25430$c3e8da3@news.astraweb.com> VAXman- @SendSpamHere.ORG wrote: >It lasts me 30-40 days so > it does not go south. That all depends on whether or not Mrs. VAXman joins > me imbibing. Do you rely on Guiness alone for nutrition ? :-) :-) :-) > for Guinness) the CO2 pressure is about 8PSI. The pressure needed to force > the beer through the restrictor is about 30PSI. Hence, the N2 mix. Thanks for explanation. Had not thought of that. And in terms of the laser in the basement, I expect you will shortly announce you have a small nuclear reactor to power all your vaxen in your basement ? :-) :-) :-) :-) :-) ------------------------------ Date: 21 Feb 2008 00:56:11 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Emacs Message-ID: <47bccc2b$0$8060$607ed4bc@cv.net> In article <47bcc8bf$0$25430$c3e8da3@news.astraweb.com>, JF Mezei writes: >VAXman- @SendSpamHere.ORG wrote: >>It lasts me 30-40 days so >> it does not go south. That all depends on whether or not Mrs. VAXman joins >> me imbibing. > >Do you rely on Guiness alone for nutrition ? :-) :-) :-) Nutritionally, Guinness isn't bad. More mythconceptions about Guinness... It's too heavy a beer... NOT. The specific gravity of Guinness makes it a lighter beer than even some 'lite' beers. It's too strong a beer... NOT. The ABV of Guinness is 4%. Most domestic swill is 5% or higher. Guinness is also 110 calories for 12 oz. Compare that to most light beers -- watered down swill lagers. >> for Guinness) the CO2 pressure is about 8PSI. The pressure needed to force >> the beer through the restrictor is about 30PSI. Hence, the N2 mix. > >Thanks for explanation. Had not thought of that. I have charts for the proper manifold gas mix based on STP altitude and storage temps. >And in terms of the laser in the basement, I expect you will shortly >announce you have a small nuclear reactor to power all your vaxen in >your basement ? :-) :-) :-) :-) :-) Just a hobby JF. A remnant of my college graduate days; albeit, DPSS lasers didn't exist then. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Wed, 20 Feb 2008 11:12:23 -0800 (PST) From: tadamsmar Subject: Re: Errors during shadow set merge Message-ID: On Feb 20, 1:10=A0pm, Tad Winters wrote: > tadamsmar wrote innews:949155f7-e92c-4368-a425-9bcf00= 96729a@e60g2000hsh.googlegroups.com: > > > On Feb 20, 10:26=A0am,tadamsmar wrote: > >> On Feb 20, 8:08=A0am, Jim wrote: > > >> > On Feb 19, 7:59=A0am,tadamsmar wrote: > > >> > > On Feb 18, 11:17=A0pm, Michael Austin > >> > > wrote: > > >> > > > tadamsmarwrote: > >> > > > > On Feb 18, 5:00 pm, "Richard B. Gilbert" > >> > > > > wrote: > >> > > > >> tadamsmarwrote: > >> > > > >>> I noticed I was getting errors when adding a member to a > >> > > > >>> shadow set. > >> > > > >>> I have been getting errors during shadow set merges since > >> > > > >>> I bought this refurb DS10. > >> > > > >>> Got 109 error today when I remerged after doing an image. > >> > > > >>> =A016 errors on DKA0 and 93 on DKA100. > >> > > > >>> What do you think is causing this? > >> > > > >>> Are these soft errors? > >> > > > >>> Here is the log for one: > >> > > > >>> **** V3.4 =A0********************* ENTRY 1667 > >> > > > >>> ******************************** > >> > > > >>> Logging OS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. = OpenVMS > >> > > > >>> System Architecture =A0 =A0 =A0 =A0 =A0 =A0 =A0 2. Alpha > >> > > > >>> OS version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 V7.3-2 > >> > > > >>> Event sequence number =A0 =A0 =A0 =A0 11474. > >> > > > >>> Timestamp of occurrence =A0 =A0 =A0 =A0 =A0 =A0 =A018-FEB-200= 8 09:52:48 > >> > > > >>> Time since reboot =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A077 D= ay(s) 1:23:46 > >> > > > >>> Host name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0EESD > >> > > > >>> System Model =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = AlphaServer DS10 617 > >> > > > >>> MHz Entry Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A01. Device Error > >> > > > >>> ---- Device Profile ---- > >> > > > >>> Unit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 $1$DKA0 > >> > > > >>> Product Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = ATLAS10K2-TY184L > >> > > > >>> Vendor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 QUANTUM > >> > > > >>> -- Driver Supplied Info - > >> > > > >>> Device Firmware Revision =A0 =A0 =A0 =A0 =A0 =A0 DA40 > >> > > > >>> VMSSCSIError Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 5. Extended Sen= se Data > >> > > > >>> from Device > >> > > > >>>SCSIID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >> > > > >>>SCSILUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > >> > > > >>>SCSISUBLUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >> > > > >>> Port Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00000001 =A0NORMAL = =A0- =A0normal > >> > > > >>> successful completion > >> > > > >>>SCSICommand Opcode =A0 =A0 =A0 =A0 =A0 =A0 x28 =A0Read (10 byt= e command) > >> > > > >>> Command Data > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x00 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x02 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x06 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x44 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x8A > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x00 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x00 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x01 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x00 > >> > > > >>>SCSIStatus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 =A0Chec= k Condition > >> > > > >>> Remaining Byte Length =A0 =A0 =A0 =A0 =A0 =A018. > >> > > > >>> --- Device Sense Data --- > >> > > > >>> Error Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0xF0 =A0= Current Error > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Information Bytes > >> > > > >>> are Valid Segment # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 x00 > >> > > > >>> Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06= > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44= > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A= =A0LBA: =A0x0206448A > >> > > > >>> Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0= Medium Error > >> > > > >>> Additional Sense Length =A0 =A0 =A0 =A0 x0A > >> > > > >>> CMD Specific Info Byte 3 =A0 =A0 =A0 =A0x21 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0x23= > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0x3E= > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0xD4= > >> > > > >>> ASC & ASCQ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x1100 =A0AS= C =A0=3D =A0 x0011 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0ASCQ =3D =A0 x0000 > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Unrecovered Read > >> > > > >>> Error FRU Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0x00 > >> > > > >>> Sense Key Specific Byte 0 =A0 =A0 =A0 x80 =A0Valid Sense Key = Data > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 x00= > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 xA0= > >> > > > >>> ----- Software Info ----- > >> > > > >>> UCB$x_ERTCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retr= ies Remaining > >> > > > >>> UCB$x_ERTMAX =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retr= ies Allowable > >> > > > >>> IRP$Q_IOSB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x0000000000000000 > >> > > > >>> UCB$x_STS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x08021810 =A0Online= > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Software Valid > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Unload At Dismount > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Volume is Valid on > >> > > > >>> the local node > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Unit supports the > >> > > > >>> Extended Function bit > >> > > > >>> IRP$L_PID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x82640450 =A0Reques= tor "PID" > >> > > > >>> IRP$x_BOFF =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4416. Byte= Page Offset > >> > > > >>> IRP$x_BCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0512. Tr= ansfer Size In > >> > > > >>> Byte(s) UCB$x_ERRCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = 32. Errors This > >> > > > >>> Unit UCB$L_OPCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022716780. QIO= 's This Unit > >> > > > >>> ORB$L_OWNER =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00010004 =A0Owners U= IC > >> > > > >>> UCB$L_DEVCHAR1 =A0 =A0 =A0 =A0 =A0 =A0x1C4D4008 =A0Directory = Structured > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0File Oriented > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Sharable > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Available > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Mounted > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Error Logging > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Capable of Input > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Capable of Output > >> > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0Random Access > >> > > > >> Is that system under service contract? =A0If so, ask to have > >> > > > >> the drive replaced! > > >> > > > >> I hope you have a recent backup that's readable. =A0 If you > >> > > > >> don't, try to make one! =A0Right now!!!! > > >> > > > >> It could be just a single bad block. =A0It could also be all > >> > > > >> the warning you are going to get that the disk is failing! > >> > > > >> =A0Once you hear that "loud scraping sound" it's all over!! > > >> > > > >> If you don't have a service contract, order a replacement > >> > > > >> disk and get a rush on the delivery! > > >> > > > >> Meanwhile, keep an eye on the disk. =A0If you get more error > >> > > > >> messages with different LBAs it means the situation is > >> > > > >> deteriorating and you may have an emergency within a few > >> > > > >> minutes or hours.- Hide quoted text - > > >> > > > >> - Show quoted text - > > >> > > > > Are these hard or soft errors? > > >> > > > These are generally HARD errors - do what he said and order a > >> > > > disk ASAP.- Hide quoted text - > > >> > > > - Show quoted text - > > >> > > I am skeptical that its the disks (In my original message, I > >> > > indicated that I get errors for both disks) > > >> > > I have had this problem for a while. =A0I have run: > > >> > > ANAL/MEDIA/EXER > > >> > > on the disks and found no errors. > > >> > > These error bursts only happen when I do a shadow set merge. > > >> > > I suspect something about the SCSI, or connections, that is > >> > > stressed by a merge.- Hide quoted text - > > >> > > Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > >> > > =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > >> > > =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > >> > > =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0LBA= : =A0x0206448A > >> > > Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Medium= Error > > >> > This is indicative of the problem - a media failure - and not one > >> > of electronics. It might be interesting to determine where that > >> > logical block address lives. I suspect that you'll find that it > >> > belongs to some file that is rarely or never accessed - until > >> > such time as a shadow copy/merge occurs - and then when it is > >> > touched the media error is noted. You might find that the > >> > integrity of said file is compromised (I presume the block is > >> > located in a file and not in free space) and requires restoration > >> > (note that this event was recorded as an unrecovered read).- Hide > >> > quoted text - > > >> > - Show quoted text - > > >> Perhaps you are on to something. =A0I checked the error log more > >> extensively and did find LBAs that appear in more than one error > >> burst.- Hide quoted text - > > >> - Show quoted text - > > > I just started a ANAL/MEDIA/EXER=3DFULL > > > I have not tried FULL before, maybe that will make a difference. > > Also, it's been months since I tried ANAL/MEDIA/EXER > > This is a bit confusing. =A0If the system is under a maintenance > contract, but you have the time to exercise the media, it would seem to > me the first thing to do is get the drives swapped. > > That bit aside, IIRC, analyzing the media may not reveal errors since > the drives generally handle their own bad block replacement. Why does that matter? What does that have to do with errors? What disk errors won't be found by: ANAL/MEDIA/EXER=3DFULL ? > There > used to be a kit called RZDISK which allowed you to send a number of > SCSI commands that weren't otherwise available. =A0I think I recently > mentioned finding RZTOOLS in SYS$ETC which also provided some > additional command options. =A0It might be useful to see if you can use > these to query the disk's bad block table before and after a media > exercise to see how it changes. =A0If the table keeps growing, don't > waste any more time, just replace the disks. ANAL/MEDIA/LOG tells you how many blocks are in the bad block table. Why not use just use this command? ------------------------------ Date: Thu, 21 Feb 2008 03:19:08 GMT From: Michael Austin Subject: Re: Errors during shadow set merge Message-ID: tadamsmar wrote: > On Feb 18, 11:17 pm, Michael Austin > wrote: >> tadamsmarwrote: >>> On Feb 18, 5:00 pm, "Richard B. Gilbert" >>> wrote: >>>> tadamsmarwrote: >>>>> I noticed I was getting errors when adding a member to a shadow >>>>> set. >>>>> I have been getting errors during shadow set merges since I bought >>>>> this refurb DS10. >>>>> Got 109 error today when I remerged after doing an image. 16 errors >>>>> on DKA0 and 93 on DKA100. >>>>> What do you think is causing this? >>>>> Are these soft errors? >>>>> Here is the log for one: >>>>> **** V3.4 ********************* ENTRY 1667 >>>>> ******************************** >>>>> Logging OS 1. OpenVMS >>>>> System Architecture 2. Alpha >>>>> OS version V7.3-2 >>>>> Event sequence number 11474. >>>>> Timestamp of occurrence 18-FEB-2008 09:52:48 >>>>> Time since reboot 77 Day(s) 1:23:46 >>>>> Host name EESD >>>>> System Model AlphaServer DS10 617 MHz >>>>> Entry Type 1. Device Error >>>>> ---- Device Profile ---- >>>>> Unit $1$DKA0 >>>>> Product Name ATLAS10K2-TY184L >>>>> Vendor QUANTUM >>>>> -- Driver Supplied Info - >>>>> Device Firmware Revision DA40 >>>>> VMSSCSIError Type 5. Extended Sense Data from Device >>>>> SCSIID x00 >>>>> SCSILUN x00 >>>>> SCSISUBLUN x00 >>>>> Port Status x00000001 NORMAL - normal successful >>>>> completion >>>>> SCSICommand Opcode x28 Read (10 byte command) >>>>> Command Data >>>>> x00 >>>>> x02 >>>>> x06 >>>>> x44 >>>>> x8A >>>>> x00 >>>>> x00 >>>>> x01 >>>>> x00 >>>>> SCSIStatus x02 Check Condition >>>>> Remaining Byte Length 18. >>>>> --- Device Sense Data --- >>>>> Error Code xF0 Current Error >>>>> Information Bytes are Valid >>>>> Segment # x00 >>>>> Information Byte 3 x02 >>>>> Byte 2 x06 >>>>> Byte 1 x44 >>>>> Byte 0 x8A LBA: x0206448A >>>>> Sense Key x03 Medium Error >>>>> Additional Sense Length x0A >>>>> CMD Specific Info Byte 3 x21 >>>>> Byte 2 x23 >>>>> Byte 1 x3E >>>>> Byte 0 xD4 >>>>> ASC & ASCQ x1100 ASC = x0011 >>>>> ASCQ = x0000 >>>>> Unrecovered Read Error >>>>> FRU Code x00 >>>>> Sense Key Specific Byte 0 x80 Valid Sense Key Data >>>>> Byte 1 x00 >>>>> Byte 2 xA0 >>>>> ----- Software Info ----- >>>>> UCB$x_ERTCNT 16. Retries Remaining >>>>> UCB$x_ERTMAX 16. Retries Allowable >>>>> IRP$Q_IOSB x0000000000000000 >>>>> UCB$x_STS x08021810 Online >>>>> Software Valid >>>>> Unload At Dismount >>>>> Volume is Valid on the local >>>>> node >>>>> Unit supports the Extended >>>>> Function bit >>>>> IRP$L_PID x82640450 Requestor "PID" >>>>> IRP$x_BOFF 4416. Byte Page Offset >>>>> IRP$x_BCNT 512. Transfer Size In Byte(s) >>>>> UCB$x_ERRCNT 32. Errors This Unit >>>>> UCB$L_OPCNT 22716780. QIO's This Unit >>>>> ORB$L_OWNER x00010004 Owners UIC >>>>> UCB$L_DEVCHAR1 x1C4D4008 Directory Structured >>>>> File Oriented >>>>> Sharable >>>>> Available >>>>> Mounted >>>>> Error Logging >>>>> Capable of Input >>>>> Capable of Output >>>>> Random Access >>>> Is that system under service contract? If so, ask to have the drive >>>> replaced! >>>> I hope you have a recent backup that's readable. If you don't, try to >>>> make one! Right now!!!! >>>> It could be just a single bad block. It could also be all the warning >>>> you are going to get that the disk is failing! Once you hear that "loud >>>> scraping sound" it's all over!! >>>> If you don't have a service contract, order a replacement disk and get a >>>> rush on the delivery! >>>> Meanwhile, keep an eye on the disk. If you get more error messages with >>>> different LBAs it means the situation is deteriorating and you may have >>>> an emergency within a few minutes or hours.- Hide quoted text - >>>> - Show quoted text - >>> Are these hard or soft errors? >> These are generally HARD errors - do what he said and order a disk ASAP.- Hide quoted text - >> >> - Show quoted text - > > I am skeptical that its the disks (In my original message, I indicated > that I get errors for both disks) > > I have had this problem for a while. I have run: > > ANAL/MEDIA/EXER > > on the disks and found no errors. > > These error bursts only happen when I do a shadow set merge. > > I suspect something about the SCSI, or connections, that is stressed > by a merge. I still suspect the media - and I can back it up with 24 years of reading error logs... can you? ------------------------------ Date: Wed, 20 Feb 2008 21:19:53 -0500 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= Subject: Re: regex within a DCL procedure Message-ID: <47bcdfbe$0$90267$14726298@news.sunsite.dk> Jean-François Piéronne wrote: > Arne Vajhøj wrote: >> Jan-Erik Söderholm wrote: >>> Pierre wrote: >>>> can perl/awk/python read/write symbols/logicals ? >>> >>> Python, yes. >>> >>> See: http://vmspython.dyndns.org/VMSRTLExample >> >> I do not have Python running on my VMS systems, but >> I would have expected os.getenv to be able to do it. > > Correct, but using os.getenv (jacket routine to the CRTL getenv routine) > you can't choose between a symbol or a logical. And if you have a > logical and a symbol with the same name getenv return the logical and > you have no access to the symbol. If you need to distinguish between symbol and logical, then you obviously need the VMS specific solution. Arne ------------------------------ Date: Wed, 20 Feb 2008 20:10:52 -0800 (PST) From: Jerry Eckert Subject: Re: regex within a DCL procedure Message-ID: <8059aba3-65aa-49f8-a5e6-7f99f984dd6c@60g2000hsy.googlegroups.com> On Feb 18, 3:29 pm, Hein RMS van den Heuvel wrote: > On Feb 18, 3:54 pm, Pierre wrote: > > > can perl/awk/python read/write symbols/logicals ? > > > Pierre > > Yes. Perl in trivially easy through the $ENV{logical/symbol} > associative array, as well as through a VMS specific extention DCLsym. > > The ENVIRON implemenation for OpenVMS AWK, at least up to 3.1.1 is > incomplete: > $ awk /comm="BEGIN{ for( item in ENVIRON) print item, ENVIRON[item]}" > nl: > AWKPATH .,/AWK_LIBRARY > USER HEIN > TERM vt102-132 > PATH /user1/hein > HOME /user1/hein > $ awk --version > GNU Awk 3.1.1 > > I have not experience with Python (shame on me), but believe it to > have good interfaces to RTL functions and SYStem services. > > Hein. If you need to translate other symbols or logical names using GAWK, the program can pass a command (e.g., SHOW SYM, SHOW LOG, or F$TRNLNM) to DCL and read back the output. ------------------------------ Date: Wed, 20 Feb 2008 20:34:28 -0800 (PST) From: Sue Subject: Re: Semi OT: Feedback to HP Message-ID: <242aad10-5b56-41c4-bbfb-690cf8c69fe1@t66g2000hsf.googlegroups.com> On Feb 16, 12:24=A0pm, JF Mezei wrote: > Michael Austin wrote: > > JF - also to be truly "fair", depending on the level of information > > provided for security vulnerabilities, most companies do not respond to > > the information. Well, they do and they don't - you may see in the near > > future a new ECO/patch for the affected application :) > > It would have been nice to just get an email stating that they had > forwarded my message to the appropriate people. > > As I recall, that form that Mr SMS had provided was VMS specific. > Perhaps there is nobody left in the VMS group to read those. Perhaps > they go to the mailbox of an employee that no longer works there. > > I know I could have sent it toSuedirectly and have high confidence > thatSuewould forward it to the appropriate person. > > However, what i could now do is hunt down the original URL I used, and > write =A0a message toSuethat perhaps messages posted using that form get > lost and not read by any humans. If the form is broken behind the > scenes,Suecould then not only make sure it is fixed and make sure it > is read by a human at regular intervals, but also retrieve my original > message and forward it to the appropriate people. > > The big difference between HP-VMS and Apple-OSX isSue. With VMS, we > haveSueto contact where we have problems. Apple is way too big to have > people who are in direct contact with individual customers. > > But with Apple, while I don't expect a response from a bug report, I > know their web form points to a group that actively =A0monitor the bug > reports. With VMS, I am not sure there is anyone left to monitor the > various forms that people can fill. So if you send me the stuff I can try and fix the problem. Sue ------------------------------ Date: Thu, 21 Feb 2008 01:24:21 +0100 From: Philipp Hachtmann Subject: Re: TU58 cartridges Message-ID: <47bcc56f$0$20775$afc38c87@news6.united-newsserver.de> Hello! > The only time I have ever even tried to resell a piece of my classic > computer stuff was when I could not find someone to take it for free. Haha! I'm just in a similar situation. I have been offering a lot of stuff (including ASR33, 9-track tape drive, PDP11/23 stuff, HP1000 system) for free (or little charge for my rescuing efforts) on de.alt.folklore.computer - nobody wants them. Next step will be eBay... Sad... Best wishes, Philipp :-) ------------------------------ Date: Wed, 20 Feb 2008 20:28:48 -0800 From: "Jeffrey H. Coffield" Subject: Re: VAX BASIC, file specs, and command line arguments Message-ID: <467vj.2345$fX7.290@nlpi061.nbdc.sbc.com> Hein RMS van den Heuvel wrote: > Jeffrey, > > I don't like the looks of the useropen. > Best I can tell on quick inspection it will reduce the default error > handler functionality by killing the ability to return a filename > there. > I would suggest to recode to leave the Basic provide nam block in > place and chase down its RSA pointer for a string copy after the SYS > $OPEN. Mind you, as Basic does not do pointers, you may need a helper > de-reference function for that and a little white lie. > > Mr Hobbs (that the name?), I can probably retrieve a workign example > of the that. Let me know here, or in an Email if that's appreciated > > Hein. I really don't understand what you are suggesting. This code has been working in numerous production application at several sites since 1996 with no problems. Why do you think this will interfere with the error handling? Jeff ------------------------------ Date: Wed, 20 Feb 2008 20:49:45 -0800 (PST) From: univms@bigfoot.com Subject: VAXstation 3100, TK50 Tape Drive and LA50 Printer Message-ID: <28c1794c-7c60-4710-a781-48518be8453b@t66g2000hsf.googlegroups.com> Selling a VAXstation 3100 with VMS 5.0 installed, TK50 tape drive, and LA50 printer, all for $100. They can be picked locally (Milwaukee, WI) or can be shipped. Shipping will probably be about $150 - $200 because of the weight. ------------------------------ Date: Thu, 21 Feb 2008 01:53:06 +0100 From: "P. Sture" Subject: Re: VMS license fees? Message-ID: In article <47b373d1$0$25029$607ed4bc@cv.net>, VAXman- @SendSpamHere.ORG wrote: > In article <47B363C7.6010706@comcast.net>, "Richard B. Gilbert" > writes: > >I think your dates are a little off Dan. In 1984 there were licenses > >but no License PAKs. You did need a software "patch" to enable DECnet > >but that was not the same thing as a PAK. > > > >Paper license PAKs came along a couple of years later! > > 1987/88 time frame when VMS V5.0 and the LMF were introduced. Which in turn came before there were Alpha, so paper license PAKs were already in use when Alphas arrived. -- Paul Sture Sue's OpenVMS bookmarks: http://eisner.encompasserve.org/~sture/ovms-bookmarks.html ------------------------------ End of INFO-VAX 2008.103 ************************