1 INFO-VAX	Mon, 24 Apr 2006	Volume 2006 : Issue 226       Contents:) Re: FA: MicroVAX 3100-30 Parts Machine NR ) Re: FA: MicroVAX 3100-30 Parts Machine NR ) Re: FA: MicroVAX 3100-30 Parts Machine NR ) Re: FA: MicroVAX 3100-30 Parts Machine NR A Heads UP BRUDEN Announces the OpenVMS Bootcamp Uptime Scholarship E Re: Heads UP BRUDEN Announces the OpenVMS Bootcamp Uptime Scholarship * Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof% Need Help Finding Memory Part Numbers ) Re: Need Help Finding Memory Part Numbers : Re: Overland Data neo 2000/MSL series drive + OpenVMS 8.2> Re: Replacing drives in bricks& Re: required patches for other patches4 Re: shadow sets, cluster, merge, MVTIMEOUT, dismount4 Re: shadow sets, cluster, merge, MVTIMEOUT, dismount4 Re: shadow sets, cluster, merge, MVTIMEOUT, dismount4 Re: shadow sets, cluster, merge, MVTIMEOUT, dismount4 Re: shadow sets, cluster, merge, MVTIMEOUT, dismount Re: Strange disk device state 6 VAX/VMS 5.5-2, Disk to Disk backup / Disk name problem: Re: VAX/VMS 5.5-2, Disk to Disk backup / Disk name problem: Re: VAX/VMS 5.5-2, Disk to Disk backup / Disk name problem: Re: VAX/VMS 5.5-2, Disk to Disk backup / Disk name problem Re: vws  Re: vws  Re: vws   F ----------------------------------------------------------------------    Date: 23 Apr 2006 13:38:09 -0700 From: tomarsin2015@comcast.net2 Subject: Re: FA: MicroVAX 3100-30 Parts Machine NRB Message-ID: <1145824689.761638.40630@u72g2000cwu.googlegroups.com>  D If you have one that works and has memory (dont need drives) contact me.  thanks phil   ------------------------------  % Date: Sun, 23 Apr 2006 16:20:00 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>2 Subject: Re: FA: MicroVAX 3100-30 Parts Machine NR6 Message-ID: <444BEF80.7D20BC71@NeOaSrPtAhMlNiOnWk.net>    Peter 'EPLAN' LANGSTOEGER wrote: > { > In article <444ADAC5.9FB1104A@NeOaSrPtAhMlNiOnWk.net>, "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> writes: K > >I just posted my first auction on eBay. Search for "Microvax" - not many H > >hits these days. The URL is too long to post here. This box complainsK > >about an unexpected interrupt during the POST and then won't boot. Maybe 5 > >someone can fix it, I'm not going to mess with it.  > . > At which length is the URL too long for you? > G >         http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=8800568552   B Whence did you acquire that URL? It was not presented to me in the  course of yesterday's activites.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  % Date: Sun, 23 Apr 2006 16:24:23 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>2 Subject: Re: FA: MicroVAX 3100-30 Parts Machine NR6 Message-ID: <444BF087.147C0B73@NeOaSrPtAhMlNiOnWk.net>   tomarsin2015@comcast.net wrote:  > F > If you have one that works and has memory (dont need drives) contact > me.  > thanks  D So far I have four of them. One with 4MB, three with 8MB. Still have1 two(2) more units to check out, and one more DOA.   F BTW: I also have an InfoServer-100 with two RRD42s in it. Dunno how toD go about testing that, but I'll do what I can and see what I come up" with. Any advice would be welcome.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------    Date: 23 Apr 2006 20:19:06 -0700 From: tomarsin2015@comcast.net2 Subject: Re: FA: MicroVAX 3100-30 Parts Machine NRB Message-ID: <1145848746.553742.92620@j33g2000cwa.googlegroups.com>    To test a InfoServer 100 do thisE Just like the VAX plug the cable into the MMJ port next to the serial  portE Just like the VAX it will count down. Since its not connected to your  network ' you will get the >>>. Do a show device. 5 More then likely you will have either a RZ23/24 drive  check for this
 BFLG D0000000  Halt 2' boot device dka100,dka200 (the 2 RDD42)  the RZ2X will be DKA0 $ If everything is okay then just type	 >>>B dka0 E If the drive has the Infoserver software installed it will come up.If  the Infoserver ask for a6 password the default password is ESS (uppper or lower) hope this helps  ps I still use 5 InfoServers  phil   ------------------------------    Date: 23 Apr 2006 13:51:57 -0700) From: "Sue" <susan_skonetski@hotmail.com> J Subject: Heads UP BRUDEN Announces the OpenVMS Bootcamp Uptime ScholarshipB Message-ID: <1145825517.883716.26120@g10g2000cwb.googlegroups.com>  8 BRUDEN Announces the OpenVMS Bootcamp Uptime Scholarship  A This scholarship recognizes the fact that, although we are always E looking for youth, what has kept OpenVMS alive is the dedication to a > quality O/S from the user community. Criteria for scholarship:0 1) Must have worked on OpenVMS, when it was VMS.2 2) Must be older than Bruce Ellis (Born 6/2/1956).5 3) Must not have won a previous "Uptime Scholarship". + 4) The oldest applying individual will win. < 5) Employees of BRUDEN and Hewlett-Packard are not eligible.B 6) Application must be submitted by 11:59PM Eastern Time on May 3, 2006.   F BRUDEN will pay for the registration fee to the May 2006 Bootcamp (allC travel and incidental expense are the responsibility of the winning  candidate).   3 Send applications with the following information to  Bruce.Ellis@BRUDEN.com   First name: 
 Last name: Student Country of Citizenship: 
 Company name:  Student Mailing Address:
 Telephone: E-mail address:  Date of birth: Lowest version of VMS used:   E For details on the OpenVMS Advanced Technical Boot Camp please visit: . http://h71000.www7.hp.com/symposium/index.html   ------------------------------  % Date: Sun, 23 Apr 2006 21:29:30 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> N Subject: Re: Heads UP BRUDEN Announces the OpenVMS Bootcamp Uptime Scholarship, Message-ID: <444C29DD.51CEBE37@teksavvy.com>  
 Sue wrote:2 > 1) Must have worked on OpenVMS, when it was VMS.  F Only way for this to happen is a DEC engineer working on a new releaseH of VMS that would be later be named "OpenVMS". So officially, the OS wasH still called VMS, even though the engineer was working on the unreleased version og OpenVMS.   F (I think that perhaps the intend was to have someone who worked on VMS before it was named OpenVMS.      D Plenty of people worked on VMS while it was named OpenVMS though :-)  4 > 2) Must be older than Bruce Ellis (Born 6/2/1956).  H Glad to see I still have a number of years to go before I qualify :-) So, Mr ellis's birthay is 6th or february then ?      E But this is a neat promotion though ;-)  So Bruce Ellis just wants to 1 make sure he's not the older person in the room ?   ; Is he still married to the ex Decus Canada office manager ?    ------------------------------  # Date: Sun, 23 Apr 2006 17:38:03 GMT ( From: Alan Greig <greigaln@netscape.net>3 Subject: Re: HP Storageworks Arrays are Bulletproof = Message-ID: <%XO2g.157689$zI1.2239@fe2.news.blueyonder.co.uk>    Neil Rieck wrote:   F > You are correct. But prefixing the product name with XP provides an L > automatic association with Windows-XP. It's not a bad thing but it is how  > marketing people think.   F About the only operating system you wouldn't use this product with is H XP. The flavour of Windows would be Server 2003 for something like this.   > O > BTW, my previous post was a response to a complaint about the video being in  O > WMV format which I don't see as a big deal. If HP is selling a product which    G Not what the big movie companies tend to use for their trailers. Maybe   they know something HP doesn't.      --  
 Alan Greig   ------------------------------  % Date: Sun, 23 Apr 2006 15:12:02 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 3 Subject: Re: HP Storageworks Arrays are Bulletproof , Message-ID: <444BD17C.BC6BF0F5@teksavvy.com>   Dave Froble wrote:G > To some people, WMV is a universal format usable to everyone.  If you H > cannot use it, you're not using 'appropriate' tools.  Some comparisonsF > might be 'a bus built only for white people', or 'stores with access" > only for non-handicaped people'.  @ I resent the implication that those who cannot view WMV might be considered "handicapped".   D I see it more as: "we only let people of a certain religion into our" restaurant/club" type of decision.  E MPEG is the real cross platform standard.  And there is no need for a G proprietary format. And unless HP wishes to have DRM to prevent its VMS @ marketing from being distributed as widely as possible, there is/ absolutely no need to use a proprietary format.     I > not use VMS on the desktop.  Other products are better oriented to this J > task.  Just today's reality.  Those who dispute this just aren't willing > to face reality.  ? The reality is that every smart person MUST fight the Microsoft E monopoly. If you accept that everyone MUST have a windows platform to < function, then you have given up and have joined the enemy.   C I recently struck a chrord with my bank (a small local bank). I had H problems with their login page. They told me it was because I had an oldH browser. I pointed them to validator.w3.org and showed that their simpleG login page had over 80 html erors on it, and asked them: "how would you F like it if the press started to report that your web site that handlesD secure financial transctions was full of errors and question whetherG this poor quality control was also affecting their core banking apps on  their mainframes ?".    G The more people complain about the use of proprietary formats where not H necessary, the more businesses will realise that there is no need to useB those and that sticking to open standards aloows you to reach moreE people and protect your own butt because your web sites adhere to the  real standards.   G And the more businesses do that, the more Microsoft will have to listen @ and stop fucking world standards by adding its own variations to everything it does.    ------------------------------  % Date: Sun, 23 Apr 2006 16:13:06 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>3 Subject: Re: HP Storageworks Arrays are Bulletproof 6 Message-ID: <444BEDE2.2844ACDC@NeOaSrPtAhMlNiOnWk.net>   Neil Rieck wrote:  > F > For some reason this video has touched a raw nerve with some people.  B I think it would be safe to say that it is not the video that "hasB touched a raw nerve with some people", but rather the fact that itE cannot be viewed on any platform not supporting Windows Media Player, C including - but not limited to - MAC/OS-X or an OpenVMS system with F DECwindows and Secure Web Browser regardless of whether Javascript has# been disabled for maximum security.   @ ...and I feel confident saying that the "XP" in "XP12000" has noF relationship to Micro$lop. Remember: this is rebadged Hitachi kit, the successor to EVA.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  % Date: Sun, 23 Apr 2006 17:40:32 -0400 / From: "William Webb" <william.w.webb@gmail.com> 3 Subject: Re: HP Storageworks Arrays are Bulletproof I Message-ID: <8660a3a10604231440i3218ec30m5357779163443239@mail.gmail.com>   : On 4/23/06, JF Mezei <jfmezei.spamnot@teksavvy.com> wrote: > Dave Froble wrote:I > > To some people, WMV is a universal format usable to everyone.  If you J > > cannot use it, you're not using 'appropriate' tools.  Some comparisonsH > > might be 'a bus built only for white people', or 'stores with access$ > > only for non-handicaped people'. > B > I resent the implication that those who cannot view WMV might be > considered "handicapped".  > F > I see it more as: "we only let people of a certain religion into our$ > restaurant/club" type of decision. > G > MPEG is the real cross platform standard.  And there is no need for a I > proprietary format. And unless HP wishes to have DRM to prevent its VMS B > marketing from being distributed as widely as possible, there is1 > absolutely no need to use a proprietary format.  >  > K > > not use VMS on the desktop.  Other products are better oriented to this L > > task.  Just today's reality.  Those who dispute this just aren't willin= g  > > to face reality. > A > The reality is that every smart person MUST fight the Microsoft G > monopoly. If you accept that everyone MUST have a windows platform to = > function, then you have given up and have joined the enemy.  > E > I recently struck a chrord with my bank (a small local bank). I had J > problems with their login page. They told me it was because I had an oldJ > browser. I pointed them to validator.w3.org and showed that their simpleI > login page had over 80 html erors on it, and asked them: "how would you H > like it if the press started to report that your web site that handlesF > secure financial transctions was full of errors and question whetherI > this poor quality control was also affecting their core banking apps on  > their mainframes ?". > I > The more people complain about the use of proprietary formats where not J > necessary, the more businesses will realise that there is no need to useD > those and that sticking to open standards aloows you to reach moreG > people and protect your own butt because your web sites adhere to the  > real standards.  > I > And the more businesses do that, the more Microsoft will have to listen B > and stop f***ing world standards by adding its own variations to > everything it does.  >   J jf, haven't you heard the old saw about Microsoft's approach to standards?   It's called E3:    Embrace  Extend Extinguish.    WWWebb   --C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Sun, 23 Apr 2006 22:22:09 -0400 ' From: Dave Froble <davef@tsoft-inc.com> 3 Subject: Re: HP Storageworks Arrays are Bulletproof 9 Message-ID: <0eidnVkUx7IPqNHZnZ2dneKdnZydnZ2d@libcom.com>    JF Mezei wrote:  > Dave Froble wrote: > G >>To some people, WMV is a universal format usable to everyone.  If you H >>cannot use it, you're not using 'appropriate' tools.  Some comparisonsF >>might be 'a bus built only for white people', or 'stores with access" >>only for non-handicaped people'. >  > B > I resent the implication that those who cannot view WMV might be > considered "handicapped".   H That wasn't my point.  I was attempting to say that they blatantly used H a format not viewable by everybody, and comparing that to lessons we as ? a society have learned.  HP apparently hasn't yet learned this   particular lesson.  D Then again, is it HP, or some company they hired?  Remember the VMS G media kit, or whatever, with the Sun workstation/terminal on the cover?    --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Sun, 23 Apr 2006 22:35:49 -0400 ) From: "Neil Rieck" <n.rieck@sympatico.ca> 3 Subject: Re: HP Storageworks Arrays are Bulletproof 6 Message-ID: <9QW2g.442$fx.78164@news20.bellglobal.com>  G "AlexNOSPAMDaniels@themail.co.uk" <alexdaniels@themail.co.uk> wrote in   message  >  [snip] > E > The "Storageworks XP" array is a blue HP, pre-merger product. It is ) > also a rebranded HDS (Hitachi) product.  > 0 >>You've got to give credit where credit is due. > I > Well done to the "Storageworks Engineers" in the video who stuck the HP  > badge on the front.  > G > I should also note, technically is doesn't offer the same support for H > VMS, that HSGs/EVAs and other DEC/Compaq lineage Storageworks products > do.  > G > It doesn't support SCSI READL/WRITEL and the forced error flag. It is < > argueable therefore not suitable for all VMS environments. > D > Personally I'm quite happy with EVA8000's, but if I did need to go> > beyond that, it wouldn't be to  the "Storageworks" XP array. >  > Alex > $ Thanks for this info. I had no idea.  
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.8 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html9 http://www3.sympatico.ca/n.rieck/links/openvms_demos.html    ------------------------------  % Date: Sun, 23 Apr 2006 19:59:14 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>. Subject: Need Help Finding Memory Part Numbers6 Message-ID: <444C22E2.AE2FF941@NeOaSrPtAhMlNiOnWk.net>  E Wondering if someone would be so kind as to help me find part numbers  for a couple of memory items:   : o Memory for MicroVAX 3100, model DV-31ETA-A or DV-31DTA-A  % o Memory SIMMs for HSJ50 cache module   D Does anyone know where to find quick spec.'s or something that would give me a clue here?   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  % Date: Sun, 23 Apr 2006 21:07:43 -0500 % From: JORDAN <rjordan@mindspring.com> 2 Subject: Re: Need Help Finding Memory Part Numbers1 Message-ID: <l7CdnQkYwORtr9HZ4p2dnA@megapath.net>    David J. Dachtera wrote:G > Wondering if someone would be so kind as to help me find part numbers  > for a couple of memory items:  > < > o Memory for MicroVAX 3100, model DV-31ETA-A or DV-31DTA-A > 9 DV-31ETA-Ax, MicroVAX 3100-20e Multiuser Base System, VMS 9 DV-31DTA-Ax, MicroVAX 3100-10e Multiuser Base System, VMS   C Same memory as MV3100-10, MV3100-20, VAXstation 3100-30, 38, 40, 48 4 (MV3100-30, 40, and 80 and on are totally different)) (VAXstation 3100-76 is totally different)     8 4MB built in on main logic board on all system versions.    = Up to 2 memory modules can be installed; only the 8 and 16 MB = models have the connector to allow installation of the single ? port 4 and 12MB cards, but the 4 and 12 can install directly to  the MLB.    $ MS42-AB, 4MB, no secondary connector  : MS42-KA, 8MB, secondary connector for second memory option  % MS42-BA, 12MB, no secondary connector   < MS42-CA, 16MB, secondary connector for second memory option.   Supported configurations:   + Desired memory (MB)     module part numbers      8                   MS42-AB     12                   MS42-KA 2    16                   MS42-KA+MS42-AB OR MS42-BA    20                   MS42-CA :    24                   MS42-KA+MS42-BA OR MS42-CA+MS42-AB    28                      N/A)    32                   MS42-CA + MS42-BA   ' > o Memory SIMMs for HSJ50 cache module  >   = Sorry, my SOC collection poops out in the HSJ30/40 timeframe.    Rich   ------------------------------  % Date: Sun, 23 Apr 2006 21:38:59 -0400 3 From: "Peter Weaver" <newsonly@weaverconsulting.ca> C Subject: Re: Overland Data neo 2000/MSL series drive + OpenVMS 8.2> 7 Message-ID: <W_V2g.321$1V4.33471@news20.bellglobal.com>   ' <bob.birch@gmail.com> wrote in message  < news:1145769788.888196.51390@u72g2000cwu.googlegroups.com...= > Isn't the TZ88 SCSI 2, 8 bit with 50 pin SE configuration ? 8 > Whereas the Neo 2000/DLT8000 is SCSI 3 16 bit, 68 pin?  F Probably right, I never saw a DLT8000 myself, but I was responding to D "One HP tech said that support in VMS for 'older' tape drives is no 8 longer there and customer should have something newer."    ------------------------------  % Date: Sun, 23 Apr 2006 19:09:30 -0400 * From: "d b turner" <dbturner@islandco.com>' Subject: Re: Replacing drives in bricks 9 Message-ID: <NLT2g.14132$iB2.8625@bignews4.bellsouth.net>   H That's why you buy from a reputable dealer that has a little clout with  distributors  L we go through a hell of a lot of drives, mark up the price by about 20% and  resell  J Deal is we ALWAYS give YOU 12 months warranty whether the Manufacturer or  OEM gives it or not    That's why we are here. 8 Yeah yeah yeah it's all down to marketing but ask around. We don't have many, if even one, po'd customer  K Ultimately, those Ebay resellers and "cheap drive houses" will get you ...  I don't forget to ask for the free 1KG tub of vaseline when you place your   order   C Would you ever buy a TV or PC for home with 30 days warranty???????      OK then....    David     / "Tom Linden" <tom@kednos.com> wrote in message  # news:op.s8e00bsxzgicya@hyrrokkin... L > On Sat, 22 Apr 2006 07:01:04 -0700, BRAD <bradhamilton@comcast.net> wrote: >  >> BRAD wrote: >> [...]A >>> Keeping in mind that these Seagate drives are meant for blue  J >>> bricks/blue shelves only, I use SX336704LC (36G) and SX173404LC (72G)  >>> drives.  They  >>K >> Did a bit more thorough searching on eBay - ST173404LCV is the 72G part  J >> number, and ST336704LCV is the 36G part.  Both available on eBay, with L >> the 72's going for $35.00USD + $15.00 shipping ("buy it now" price). The 8 >> 36's don't seem to be available at comparable prices. > H > The problem with buying used drives is the warranty issue.  I bought aE > dozen ST373405LC  from globalmicros and two of them failed within a J > couple of months, but I only needed 10, 6 in the BA356 and 4 in the DellJ > Poweredge, so I had spares.  If you check the manufacturers site for theJ > warranty information by supplying your serial number, you will find thatD > some are returned to the manufacturer and others to the reseller,  > typically L > OEM drives.  In my case, it was one of each and they were very good about  > itJ > I just checked their site and these drives and the price depends on the  > lengthJ > of the warranty.  BTW, these are the 1" drives which I wanted for betterJ > cooling in the bricks, but also necessary for the Poweredge.  I had goodM > experience with these guys, but your mileage may vary. The new 15K Hitachi   > drivesL > are supposed to be outstanding, employing a new type of bearing, but that  > isM > all I know about it.  Of course that would be overkill for BA356.  I might  
 > get some > for our HSG80. >  > I see a lot of 5 on ebay at  > http://computers.search.ebay.com/seagate-st373405lc_Computers-Networking_W0QQbsZSearchQQcatrefZC6QQfposZ93953QQfromZR10QQfsooZ1QQfsopZ1QQftrtZ1QQftrvZ1QQsacatZ58058QQsadisZ200QQsargnZQ2d1QQsaslcZ2QQsbrftogZ1QQsofocusZbs  > ; > http://www.globalmicro.com/index.asp?t=1&s=101&b=SEAGATE     ------------------------------  % Date: Sun, 23 Apr 2006 15:00:32 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> / Subject: Re: required patches for other patches + Message-ID: <444BCECA.32A3BD3@teksavvy.com>     Peter 'EPLAN' LANGSTOEGER wrote:3 > I always install UPDATE ECOs as soon as possible.    This used to be the case.   F I don't do it anymore. I got bitten by the 5.3 to 5.3-2 ECO on VAX forF TCPIP Services which broke many things. And going from 5.0 to 5.3 alsoC "broke" traceroute which now gives meaningless numbers. (traceroute G tells me it takes 100ms to get to my router, ping on the same node says I 10ms, and a traceroute or ping from a MAC next to that machine says 1ms.)   H Seems that the student they hired to maintain ping and traceroute on VMSG didn't read the manuals properly in terms of timers and the limitations G of various timers. (using timing facilities with 10ms resolution is not ! bright for pings or traceroutes).     G What this says is that the overall quality assurance has gone down. But A in the end, since engineers only care about a few large remaining G customers, I suspect that QA is still great for the features that those  few customers actually use.   9 Note that traceroute on 5.0 of TCPIP Services was usable.    ------------------------------  + Date: Sun, 23 Apr 2006 18:30:10 +0000 (UTC) 7 From: moroney@world.std.spaamtrap.com (Michael Moroney) = Subject: Re: shadow sets, cluster, merge, MVTIMEOUT, dismount ( Message-ID: <e2gh3i$915$1@pcls4.std.com>  F Regardless of where the physical disks are hosted, any shadowset still@ mounted by a node when it is shutdown will require a merge.  As D SHUTDOWN.COM dismounts everything, the only issue is when files likeE SYSUAF are on a non system shadowset, which is a bug of sorts.  There J was recent discussion here how to take care of that, shutting down certainH system processes.  This should be the only issue regarding mounted sets.  H Other than that, the only problem is disks hosted by the departing node.@ Other nodes will stall I/O on the sets for up to SHADOW_MBR_TMO,J SHADOW_SYS_TMO or MVTIMEOUT seconds as appropiate.  If the node comes backI within that time and begins serving the drive again, the system will pick I up where it left off.  Otherwise shadowing will remove the missing member B if there is another good one, or place the set in MVTIMEOUT state.  H If the member was removed, a copy will be needed when adding it back in.   ------------------------------  % Date: Sun, 23 Apr 2006 14:49:21 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> = Subject: Re: shadow sets, cluster, merge, MVTIMEOUT, dismount , Message-ID: <444BCC2C.FCB86919@teksavvy.com>  C When I last looked at Shutdown.COM, it lacked the ability to call a 5 user-written "dismount" procedure at the right time.    D And SYSSHUTDWN.COM (the user witten procedure) is called well before! disks are ready to be dismounted.   C >In case 1), it will be dismounted on A but not on B and C.  Is it  ? >necessary to dismount it on B and C in order to avoid a merge?    Think about it:   C At the time node A dismounts a drive, node A's MSCP server is still H active, so while it may be dismounted locally, the other nodes are stillH accessing it right up until the end when it abruptly becomes unavailable! and goes into mount verification.   F But the shadowset itself can continue since it would have at least oneF other member that is usable. So by the time A's disk becomes available9 again, there is no choice but to run some form of process / (merge/copy/etc) to bring that disk up to date.   7 I think that to do a clean dismount, you would have to    F SHOW DEV/FILES to a file. Then STOP/ID any process accessing a file onE that drive. And then run INSTALL to delete any installed files (PID = F 000000 in SHOW DEV/FILES), AND then check for any page/swap files thatH may be on that drive and get a list of processes that have memory mapped+ to that file and kill those processes too.    8 Run the above on every node that has that drive mounted.  F I am somewhat surprised that the VMS engineers haven't made the systemD shutdown more "dismount smart" since shadowing appeared in 1990/1991H time  frame. Being about to do clean dismounts isn't easy. I is probablyD hard to justify spending money on updating a procedure people say isH nevert used because VMS is never shutdown :-) But in reality, especiallyH in a cluster, one is able to shutdown to do maintenance/upgrades etc andC this is where a proper dismount of drives becomes really important.    ------------------------------  + Date: Sun, 23 Apr 2006 19:13:44 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)= Subject: Re: shadow sets, cluster, merge, MVTIMEOUT, dismount $ Message-ID: <e2gjl8$1tq$1@online.de>  H In article <e2gh3i$915$1@pcls4.std.com>, moroney@world.std.spaamtrap.com (Michael Moroney) writes:   H > Regardless of where the physical disks are hosted, any shadowset stillB > mounted by a node when it is shutdown will require a merge.  As F > SHUTDOWN.COM dismounts everything, the only issue is when files likeG > SYSUAF are on a non system shadowset, which is a bug of sorts.  There L > was recent discussion here how to take care of that, shutting down certainJ > system processes.  This should be the only issue regarding mounted sets.  B Actually, SHUTDOWN.COM takes care of the audit server and securityC server.  I still kill the DECwindows server by hand (or, rather, in H SYSSHUTDWN.COM) since I'm not sure if it is killed otherwise (it doesn'tH seem to occur in SHUTDOWN.COM, but the code is rather cryptic).  Since aH merge of the shadow set in question takes about 8 hours, I don't want toB experiment too much.  The open file in question is RIGHTSLIST.DAT;D perhaps someone with a small and/or fast non--system-disk shadow setG with RIGHTSLIST.DAT on it can experiment.  (There doesn't seem to be a  @ DECW$SHUTDOWN.COM, which would be the obvious place to do this.)  J > Other than that, the only problem is disks hosted by the departing node.B > Other nodes will stall I/O on the sets for up to SHADOW_MBR_TMO,L > SHADOW_SYS_TMO or MVTIMEOUT seconds as appropiate.  If the node comes backK > within that time and begins serving the drive again, the system will pick K > up where it left off.  Otherwise shadowing will remove the missing member D > if there is another good one, or place the set in MVTIMEOUT state.  F So it would make sense, at least if REMOVE_NODE is specified, to do a E DISMOUNT/CLUSTER in SHUTDOWN.COM on shadow-set members with a direct  H connection only to the node shutting down and also to shadow sets whose F members have a direct connection only to the node shutting down.  Or, F equivalently, dismount them from other nodes in the cluster.  (Once a I member is dismounted from one node, it will be dismounted from all nodes  H since shadow-set consistency is automatically maintained; a full shadow I set will be dismounted from the node being shut down by SHUTDOWN.COM, so  5 it's enough to dismount it on the other nodes first.)   D Here's some code to do this which I wrote today (and have NOT fully  tested):  H ---------8<-------------------------------------------------------------  ( $! CLUSTER_MANAGER:SHUTDOWN_DISMOUNT.COM $! $! $  WSO := WRITE SYS$OUTPUT $! $!! $  IF P1 .EQS. "" THEN GOTO USAGE  $! $!9 $! get a list of nodes other than the one being shut down  $!) $  @ CLUSTER_MANAGER:DEFINE_NODE_LIST.COM  $  NON_SHUTDOWN_NODES = "" $  I = 0 $NODE_LOOP: 1 $  NODE = F$TRNLNM("NODES","SYSMAN$NODE_TABLE",I) + $  IF NODE .EQS. "" THEN GOTO GOT_ALL_NODES , $  IF NODE .NES. F$GETSYI("NODENAME") THEN -8     NON_SHUTDOWN_NODES = NON_SHUTDOWN_NODES + "," + NODE $  I = I + 1 $GOTO NODE_LOOP  $GOT_ALL_NODES: 0 $  NON_SHUTDOWN_NODES = NON_SHUTDOWN_NODES - ","O $  DEFINE/NOLOG/TABLE=SYSMAN$NODE_TABLE NON_SHUTDOWN_NODES 'NON_SHUTDOWN_NODES'  $! $! $! get a list of disks $! $  DISMOUNT_LIST = ""  $DISK_LOOP:  $  DISK = F$DEVICE("*","DISK")+ $  IF DISK .EQS. "" THEN GOTO GOT_ALL_DISKS 7 $  IF .NOT. F$GETDVI(DISK,"EXISTS") THEN GOTO DISK_LOOP 4 $  IF .NOT. F$GETDVI(DISK,"MNT") THEN GOTO DISK_LOOP" $  IF F$GETDVI(DISK,"SHDW_MASTER") $  THEN  $!   we have a shadow set = $!   check if all members are directly connected to this node  $    AC = F$GETSYI("ALLOCLASS")  $    REF_DISK = DISK $    ALL := TRUE
 $    I = 0
 $MEMBER_LOOP:  $    I = I + 15 $    MEMBER = F$GETDVI(REF_DISK,"SHDW_NEXT_MBR_NAME") 1 $    IF MEMBER .EQS. "" THEN GOTO GOT_ALL_MEMBERS 8 $    IF F$LOCATE("$''AC'$",MEMBER) .LT. F$LENGTH(MEMBER)	 $    THEN  $      MEMBER_'I' = MEMBER	 $    ELSE  $      MEMBER_'I' = "" $      ALL := FALSE 
 $    ENDIF $    REF_DISK = MEMBER $GOTO MEMBER_LOOP  $GOT_ALL_MEMBERS:  $    IF ALL 	 $    THEN 1 $      DISMOUNT_LIST = DISMOUNT_LIST + "," + DISK 	 $    ELSE  $MEMBER_LIST_LOOP: $      I = I - 1- $      IF I .EQS. 0 THEN GOTO GOT_MEMBER_LIST $ $      IF MEMBER_'I' .NES. "" THEN -8         DISMOUNT_LIST = DISMOUNT_LIST + "," + MEMBER_'I' $GOTO MEMBER_LIST_LOOP $GOT_MEMBER_LIST: 
 $    ENDIF $  ELSE 2 $!   not really needed if REMOVE_NODE is specified, $    IF .NOT. F$GETDVI(DISK,"SHDW_MEMBER") -H       .AND. F$GETDVI(DISK,"HOST_NAME") .EQS. F$GETSYI("NODENAME") THEN -0       DISMOUNT_LIST = DISMOUNT_LIST + "," + DISK $  ENDIF $GOTO DISK_LOOP  $GOT_ALL_DISKS: & $  DISMOUNT_LIST = DISMOUNT_LIST - "," $  IF P1 .EQS. "SHOW"  $  THEN  $     WSO ""1 $     WSO "Other nodes are: ", NON_SHUTDOWN_NODES 9 $     WSO "Devices to be dismounted are: ", DISMOUNT_LIST  $  ELSE  $    IF P1 .NES. "DISMOUNT" 	 $    THEN  $      GOTO USAGE 	 $    ELSE  $      CLOSE/NOLOG FILE ? $      OPEN/WRITE FILE SYS$SCRATCH:SHUTDOWN_DISMOUNT_SYSMAN.COM  $      I = 0
 $SYSMAN_LOOP: , $      DISK = F$ELEMENT(I,",",DISMOUNT_LIST)2 $      IF DISK .EQS. "," THEN GOTO GOT_SYSMAN_LOOP $      WRITE FILE "$  SET NOON" < $      WRITE FILE "$  DMO := DISMOUNT/ABORT/OVERRIDE=CHECKS"" $      WRITE FILE "$  DMO ''DISK'" $      I = I + 1 $GOTO SYSMAN_LOOP  $GOT_SYSMAN_LOOP:  $      WRITE FILE "$  EXIT"  $      CLOSE FILE  $      MC SYSMAN2          SET ENVIRONMENT/NODE=(NON_SHUTDOWN_NODES)6          DO @ SYS$SCRATCH:SHUTDOWN_DISMOUNT_SYSMAN.COM        EXIT 6 $    DELETE SYS$SCRATCH:SHUTDOWN_DISMOUNT_SYSMAN.COM;*
 $    ENDIF $  ENDIF $  EXIT  $USAGE:  $  TYPE SYS$INPUT    P1: { SHOW | DISMOUNT }   H ---------8<-------------------------------------------------------------  ' $! CLUSTER_MANAGER:DEFINE_NODE_LIST.COM  $! $! $  NODES  = ""
 $  VAX   = "" 
 $  ALPHA = ""  $  CONTEXT    = "" $GNL_START:  $  ID = F$CSID(CONTEXT) & $  NODENAME = F$GETSYI("NODENAME",,ID) $  IF ID .NES. ""  $  THEN # $    NODES = NODES + NODENAME + "," 2 $    IF F$GETSYI("ARCH_NAME",NODENAME) .EQS. "VAX"	 $    THEN ! $      VAX = VAX + NODENAME + "," 	 $    ELSE 6 $      IF F$GETSYI("ARCH_NAME",NODENAME) .EQS. "Alpha" $      THEN ' $        ALPHA = ALPHA + NODENAME + ","  $      ELSE ( $!       add Itanium code here if needed $      ENDIF
 $    ENDIF $  ELSE 2 $    NODES  = F$EXTRACT(0,F$LENGTH(NODES)-1,NODES)- $    VAX   = F$EXTRACT(0,F$LENGTH(VAX)-1,VAX) 1 $    ALPHA = F$EXTRACT(0,F$LENGTH(ALPHA)-1,ALPHA)  $    GOTO GNL_DONE $  ENDIF $GOTO GNL_START 
 $GNL_DONE:4 $  DEFINE_IT := DEFINE/NOLOG/TABLE=SYSMAN$NODE_TABLE1 $  IF NODES .NES. "" THEN DEFINE_IT NODES 'NODES' / $  IF VAX   .NES. "" THEN DEFINE_IT VAX   'VAX' 1 $  IF ALPHA .NES. "" THEN DEFINE_IT ALPHA 'ALPHA'  $! $! $  EXIT   H ---------8<-------------------------------------------------------------   ------------------------------  + Date: Sun, 23 Apr 2006 21:26:36 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)= Subject: Re: shadow sets, cluster, merge, MVTIMEOUT, dismount $ Message-ID: <e2grec$eug$1@online.de>  5 In article <444BCC2C.FCB86919@teksavvy.com>, JF Mezei ' <jfmezei.spamnot@teksavvy.com> writes:    E > >In case 1), it will be dismounted on A but not on B and C.  Is it  A > >necessary to dismount it on B and C in order to avoid a merge?   2 This was with both members on the node to go down.   > Think about it:  > E > At the time node A dismounts a drive, node A's MSCP server is still J > active, so while it may be dismounted locally, the other nodes are stillJ > accessing it right up until the end when it abruptly becomes unavailable# > and goes into mount verification.    Right.  H > But the shadowset itself can continue since it would have at least one > other member that is usable.    C Not if all are connected directly only to the node which went down.   + > So by the time A's disk becomes available ; > again, there is no choice but to run some form of process 1 > (merge/copy/etc) to bring that disk up to date.   E This would apply in the case that only one member went down with the  I node being shut down.  Of course, if it comes back after a while, a copy  F will be needed.  (Of course, once a member is dismounted on any node, I all of the "same" shadow sets on all nodes immediately expel the disk as   well.)   ------------------------------  % Date: Sun, 23 Apr 2006 21:19:14 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> = Subject: Re: shadow sets, cluster, merge, MVTIMEOUT, dismount , Message-ID: <444C2775.92936B08@teksavvy.com>  / Phillip Helbig---remove CLOTHES to reply wrote: J > I'm not sure.  If you are already shutting down the system, then I thinkA > you can go ahead and dismount disks which SHUTDOWN.COM will not  > dismount.   C Then you basically have to perform all the tasks in shutdown.com in ' syshutdwn.com ... re-invernt the wheel.   G For instance, the INSTALL PURGE is done very late in the shutdown code. E You would have to do it yourself in syshutdwn.com to make sure you've E cleared all your disks of installed images.  And you need to stop the  queues as well etc etc etc.   H > In general, yes.  In practice, installed files and page and swap filesG > are taken care of by SHUTDOWN.COM, at least if they are on the system , > disk, maybe if they are elsewhere as well.  D This is done much later in the shutdown once all processes have beenE killed. But even then, you have no assurance that the process running D shutdown.com is mapped to a page file on the system disk.  You wouldD have to do a shutdown by first using sysgen to remove any additionalC pagefiles, and then spawn a detached process that runs the shutdown E procedure (this one would be mapped to a page file on teh system disk . since all others have been marked for delete).  E Then, you could kill all other processes except yours, and this would D give you reasonable assurance that the pagefiles on non-system disks; would be closed and you could then succesfully dismount it.   H > My concern is with shadow sets with members directly connected only toG > the node shutting down, and with members of shadow sets one member of % > which is on the node shutting down.   F The concern is the ability to have a disk that *can* be dismounted, asG opposed to being marked for dismount. To avoid any merge/copy, you need E to cleanly dismount the shadow set istead of removing a member from a B surviving shadow set. And that means that you need to shutdown allB applications that use that shadow set on ALL nodes in the cluster.  F It also needs good design in terms of page/swap file locations so thatH you can cleanly dismount disks without having to cull processes all over the cluster.  G > Indeed.  On the other hand, most of the work is cleanly shutting down J > the applications.  After that's done, I hope the code I just posted will > do the trick.  :-)  H Suppose two applications require a shareable image to be installed. BothF startup procedures can do an INSTALL of it (first testing to see if itE is installed), but when you shutdown, one cannot remove the installed D image because it might sill be needed by the other application so it isn't as obvious.    ------------------------------  % Date: Sun, 23 Apr 2006 13:28:23 -0700 ' From: glenn everhart <everhart@gce.com> & Subject: Re: Strange disk device state& Message-ID: <444BE367.4070908@gce.com>   Albrecht Schlosser wrote:  > Problem summary: > F > There is a disk that can't be accessed because the system gives the  > error message: > > > %SYSTEM-W-DEVALLOC, device already allocated to another user > I > although it has been dismounted successfully. Device state is "online"  3 > (not allocated). However, show device/full shows:  > " > Reference count       4294967295 >  > which is hex FFFFFFFF, see:  >  > $ x = 4294967295
 > $ sho sym x 0 >   X = -1   Hex = FFFFFFFF  Octal = 37777777777 > H > History: The device has had lots of errors ( > 35000 ), and the error I > count has been reset. There was a process running (BADBLOCKSCAN), that  K > has been terminated with STOP/ID. The local system manager said, that he  $ > did an ANA/DISK, but no ANA/MEDIA. > I > There is a replacement disk that should be inserted and mounted (in an  H > Itanium RX2620 box, hot swappable), but obviously, this can't be done. > J > Does anybody have an idea, what to do without a reboot? What else can I E > look for? (BTW: SDA> sho dev /chan doesn't work, though I think it  F > should, as can be seen in the included help output. It doesn't work ? > under OpenVMS Alpha 7.3-2 either. So, what am I doing wrong?)  >  > Thanks for all help  > 
 > Albrecht >  > H > The following output is what I found out so far (sorry, if some lines  > wrap and for the long text)  >  > $ sho time >   21-APR-2006 16:32:34 >  > $ tcpip sho vers > L >   HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.5 - ECO 1; >   on an HP rx2620  (1.30GHz/3.0MB) running OpenVMS V8.2-1  >  > $ sho dev dka100 > H > Device                  Device           Error    Volume         Free  > Trans Mnt I >  Name                   Status           Count     Label        Blocks   > Count Cnt 0 > $1$DKA100:     (KKP1H)  Online               0 >  > $ sho dev dka100 /full > K > Disk $1$DKA100: (KKP1H), device type HP 146 G MAW3147NC, is online, file- I >     oriented device, shareable, available to cluster, error logging is  
 > enabled. > G >     Error count                    0    Operations completed   389095 < >     Owner process                 ""    Owner UIC [SYSTEM]F >     Owner process ID        00000000    Dev Prot S:RWPL,O:RWPL,G:R,WF >     Reference count       4294967295    Default buffer size      512; >     Current preferred CPU Id       0    Fastpath        1 D >     Total blocks           286749488    Sectors per track       96F >     Total cylinders            31115    Tracks per cylinder       96& >     Allocation class               1 > A >   Device error count was last reset on: 21-APR-2006 16:21:32.86  >  >  > $ allo dka100:> > %SYSTEM-W-DEVALLOC, device already allocated to another user >  > $ mount/for/noassi dka100:= > %MOUNT-F-DEVALLOC, device already allocated to another user  >  > $ ana/sys  >  > OpenVMS system analyzer  >  > SDA> sho dev /chan% > %CLI-W-SYNTAX, error parsing 'CHAN'  > SDA> help sho dev  >  > SHOW > 
 >   DEVICE > J >        Displays a list of all devices in the system and their associatedI >        data structures, or displays the data structures associated with # >        a given device or devices.  >  >        Format  > F >          SHOW DEVICE  [device-name[:] |/ADDRESS=ucb-address|/BITMAP| > 3 >                       /CDT=cdt_address|/CHANNELS|  > 8 >                       /HOMEPAGE|/PDT|/UCB=ucb-address] >  >  >  > ' >     Additional information available:  >  >     Parameter  Qualifiers L >     /ADDRESS   /CDT       /BITMAP    /CHANNELS  /HOMEPAGE  /PDT       /UCB >  > SDA> sho dev dka100: > J > $1$DKA100 [KKP1H$DKA100]                       HP 146 G MAW3147NC  UCB: 
 > 8955BB40 > 8 > Device status:   18000010 online,exfunc_supp,fast_path; > Characteristics: 1C454008 dir,fod,shr,avl,elg,idv,odv,rnd 0 >                  21010201 clu,nnm,nlt,scsi,dtn* > SUD Status       00000001 path_available > G > Owner UIC [000001,000004]   Operation count     389095   ORB address  
 > 8955BAC0G >       PID        00000000   Error count              0   DDB address   >  894B32C0 G > Alloc. lock ID   00000000   Reference count   ********   DDT address  
 > 883737A0G > Alloc. class            1   Online count             0   SUD address  
 > 894EBE40G > Class/Type          01/36   Retry cnt/max        16/16   CRB address  
 > 89488980J > Def. buf. size        512   BOFF              00000000   I/O wait queue 
 > 8955BC708 > DEVDEPEND        798B6060   Byte count        000000008 > DEVDEPND2        00000000   SVAPTE            000000008 > DEVDEPND3        01000001   DEVSTS            00000004 > FLCK index             3A  > DLCK address     894B3340  > Preferred CPUDB  8941A000  > Preferred CPUID        00  > 1 >                  --  Device Path Information --  >  >  UCB: 8955BB40 Path: PKA0.1  >     Press RETURN for more. > SDA> >  > I/O data structures  > -------------------  > I >                 --- Primary Class Driver Data Block (CDDB) 894AB400 ---  >  > Status:              00000000  > Controller Flags:    0000  > F > Allocation class       1    CDRP Queue      00000000    DDB address 
 > 894B32C0F > System ID       00000000    Restart Queue   00000000    CRB address 
 > 89488980M >                 00000000    DAP Count              0    CDDB link  00000000 F > Contrl. ID      00000000    Contr. timeout         0    PDT address 
 > 00000000G >                 00000000    Reinit Count           0    Original UCB   >  00000000 L > Response ID     00000000    Wait UCB Count         0    UCB chain 00000000 > MSCP Cmd status 00000000 > ) >         *** PORT I/O queue is empty ***  > + >         *** DEVICE I/O queue is empty ***  >  > , >         *** I/O request queue is empty *** > SDA>  E This looks like something decremented reference count without having  H incremented it. Note that this may have happened long before the problemC became apparent; if another process had incremented refcount first, E or extra files were opened (bumping refcount more), the rogue process E might have fiddled refcount long before without apparent consequence.   D Thus anything that could have dropped into kernel mode and that was E aborted would be a place to look for misbehavior. Ditto anything that B might have had ability to alter kernel structures and was unusual.  D If there's no longer a device lock on the device, I would guess thatH zeroing the refcount in the UCB would be safe. If a device lock is stillF around for the device, that will need to be removed, a not easy thing.C The error messages would cause me to go looking for a device lock;  H suspect one is in there. (Assign channel locks disks; deassign unlocks.)G However it would seem simplest to reboot and replace the bad drive ASAP  (not knowing your constraints.)    Glenn Everhart   ------------------------------    Date: 23 Apr 2006 10:45:22 -0700 From: mark_doherty@yahoo.co.uk? Subject: VAX/VMS 5.5-2, Disk to Disk backup / Disk name problem B Message-ID: <1145814322.246613.97770@v46g2000cwv.googlegroups.com>  E We have bought some RF36 disks and proceeded to do standalone disk to  disk backup with ...C $ BACKUP/IGNORE=(LABEL,INTERLOCK) /REC/IMAGE/VERI $1$DIA0: $1$DIA1: G but it did not like the name of the target disk. The disk available was F W0VDI5$DIA1. Using this name it was possible to do the backup but whenG it booted from the new disk there were dependancies on the name in some  scripts.   I tried at the boot prompt| >>> SET HOST /DUP/UQSSP/DISK 0 PARAMS and it responds with "Starting DUP Server" and then immediately  "Stopping DUP Server"   How do you change the name?    ------------------------------  % Date: Sun, 23 Apr 2006 21:05:15 +0200 3 From: Wilm Boerhout <w4OLD.boerhout@PAINTplanet.nl> C Subject: Re: VAX/VMS 5.5-2, Disk to Disk backup / Disk name problem 6 Message-ID: <444bcff9$0$18283$ba620dc5@nova.planet.nl>  5 mark_doherty@yahoo.co.uk mailde op 23-4-2006 19:45... G > We have bought some RF36 disks and proceeded to do standalone disk to  > disk backup with ...E > $ BACKUP/IGNORE=(LABEL,INTERLOCK) /REC/IMAGE/VERI $1$DIA0: $1$DIA1: I > but it did not like the name of the target disk. The disk available was H > W0VDI5$DIA1. Using this name it was possible to do the backup but whenI > it booted from the new disk there were dependancies on the name in some 
 > scripts. >  > I tried at the boot prompt > | >>>>SET HOST /DUP/UQSSP/DISK 0 PARAMS and it responds with "Starting DUP Server" and then immediately  "Stopping DUP Server" >  >  > How do you change the name?    You don't have to.  H Boot the system without running the startup script (a minimal boot), by H setting boot register R5 to 1. The method for this depends on your host L system, which you did not specify. Then in SYSBOOT>, set STARTUP_P1 to "MIN"  H After the system finishes the minimal startup, log on and edit away any  dependencies in the scripts.  I Reboot and clear the STARTUP_P1 parameter. The system should now startup  
 correctly.   /Wilm    ------------------------------  % Date: Sun, 23 Apr 2006 15:49:20 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> C Subject: Re: VAX/VMS 5.5-2, Disk to Disk backup / Disk name problem , Message-ID: <444BDA38.C575E23F@teksavvy.com>   mark_doherty@yahoo.co.uk wrote:  > I tried at the boot prompt~ > >>> SET HOST /DUP/UQSSP/DISK 0 PARAMS and it responds with "Starting DUP Server" and then immediately  "Stopping DUP Server"  = the UQSSP is only for KFQSA controllers that are Q-BUS based.   K If you have a built-in DSSI controllers (VAX 4000 series and up): from VMS:    $MC SYSGEN  * SYSGEN> LOAD SYS$LOADABLE_IMAGES:FYDRIVER  SYSGEN> CONNECT FYA0 /NOADAP    3 $SET HOST/DUP/SERVER=MSCP$DUP/TASK=PARAMS diskname    G where "diskname" is the node name shows between parentheses in SHOW DEV 	 D output.   E Inside PARAMS, it is fairly straightforward on how to change the node E name (there is on board help). But you must remember to use the WRITE E command when done to save the changes and add a space between command  and parameter   $ (eg: SHOW /SCS instead of SHOW/SCS )     From the console: : >>>  SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number PARAMS    H In terms of a BACKUP/IMAGE,  the DSSI nodename doesn't have to match theE volume name. (for instance, my system disk has node namd DISK45 but a I volume name of MICHELIN and the logical created for it is DISK$MICHELIN )    What you may need to do is to  INIT DIA1 TEMP MOUNT/FOREIGN DIA11 BACKUP/IMAGE DIA0 DIA1 (with all the parameters).  DISMOUNT DIA1:  4 SET VOLUME DIA0: /LABEL=TEMP2    (old system disk)    ( MOUNT DIA1: TEMP   (mounts it privately) SET VOLUME DIA1/LABEL=goodlabel   D You should then be able to reboot from the DIA1: drive and it shouldG appear with the good label and be mounted with DISK$volumename logical.   E (you can't really have tow disks with same volume name mounted at the C same time, so you need to rename the old drive to free up the name.   G After you've renamed the volumes with SET VOLUME, you'lkl have logicals H such as DISK$volume still pointing to the old drive, so you may not wish7 to stay in that status for very long before you reboot.    ------------------------------  % Date: Sun, 23 Apr 2006 16:33:50 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>C Subject: Re: VAX/VMS 5.5-2, Disk to Disk backup / Disk name problem 6 Message-ID: <444BF2BE.EFACBB63@NeOaSrPtAhMlNiOnWk.net>   mark_doherty@yahoo.co.uk wrote:  > G > We have bought some RF36 disks and proceeded to do standalone disk to  > disk backup with ...E > $ BACKUP/IGNORE=(LABEL,INTERLOCK) /REC/IMAGE/VERI $1$DIA0: $1$DIA1: I > but it did not like the name of the target disk. The disk available was H > W0VDI5$DIA1. Using this name it was possible to do the backup but whenI > it booted from the new disk there were dependancies on the name in some 
 > scripts.  F As you have just witnessed, this is bad practice. The only place disksB should be referred to by explicit device name is in the disk-mountH procedure that runs during - or is invoked by - SYSTARTUP_V5.COM. In allH other places except the queue database, these should be referened by the8 logical volume name assigned as P3 of the MOUNT command:  7 $ MOUNT[/SYSTEM] ddcu: volume_label logical_volume_name   D If not specified, logical volume name defaults to DISK$volume_label.   > I tried at the boot prompt~ > >>> SET HOST /DUP/UQSSP/DISK 0 PARAMS and it responds with "Starting DUP Server" and then immediately  "Stopping DUP Server" >  > How do you change the name?   
 You don't.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  % Date: Sun, 23 Apr 2006 15:17:01 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: vws, Message-ID: <444BD2A6.376E6DF3@teksavvy.com>   nierveze wrote: 9 > I have never found any information of the status of vws : > regarding hobby program,and especially uisx as there areH > applications running under vws ,and with this 'emulator' they could be > run under decwindow.  C vws is included in the hobbyisty programme and in fact was from the B start (whereas Motif came later once Motif went to open source forE platforms that don't charge for it, and DEC was able to get Motif for 0 free for Bobbyists since they don't pay for it).  G The vws emulator under Motif exists but is hidden in the attic at ZKO.  9 Personally, I'd love to run the moon landing game again.    F vws should be in the older versions of the bobbyist. If you can't findA it, I can probably get it from my old CDs and let you download it 9 (contact me privately at jfmezei  vaxination period ca .    ------------------------------  % Date: Sun, 23 Apr 2006 21:21:29 -0400 * From: "FredK" <fred.nospam@nospam.dec.com> Subject: Re: vws, Message-ID: <444c2818$1@usenet01.boi.hp.com>  J VWS and UISX was sold to Touch Technologies years ago, as such - it is not* ours to make part of the hobbyist program.    : "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message& news:444BD2A6.376E6DF3@teksavvy.com... > nierveze wrote: ; > > I have never found any information of the status of vws < > > regarding hobby program,and especially uisx as there areJ > > applications running under vws ,and with this 'emulator' they could be > > run under decwindow. > E > vws is included in the hobbyisty programme and in fact was from the D > start (whereas Motif came later once Motif went to open source forG > platforms that don't charge for it, and DEC was able to get Motif for 2 > free for Bobbyists since they don't pay for it). > H > The vws emulator under Motif exists but is hidden in the attic at ZKO.: > Personally, I'd love to run the moon landing game again. > H > vws should be in the older versions of the bobbyist. If you can't findC > it, I can probably get it from my old CDs and let you download it ; > (contact me privately at jfmezei  vaxination period ca .    ------------------------------  % Date: Sun, 23 Apr 2006 21:42:26 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: vws, Message-ID: <444C2CE4.BC4FD663@teksavvy.com>   FredK wrote: > L > VWS and UISX was sold to Touch Technologies years ago, as such - it is not, > ours to make part of the hobbyist program.  ' How many "years ago" was "years ago". ?   F I think I got my first batch of hobbyists licences for my 3100 back inE 1997, and at the time, it didn't include Motif, but I was able to run  VWS on it.    ? So either I had VWS licences from the place I got my 3100 from, )  or they came with the Hobbyist programme  or VWS ran on a VMS licence.   ------------------------------   End of INFO-VAX 2006.226 ************************