1 INFO-VAX	Sun, 22 Aug 2004	Volume 2004 : Issue 465       Contents:! Re: A whopping 50 percent...  ??? ! RE: A whopping 50 percent...  ??? + ANN: BOSS for IA64 (and other freeware too) / Re: Anybody got a version of the VAXELN toolkit  RE: charon vax emulator??? Re: charon vax emulator??? RE: charon vax emulator??? cobol 	 Re: cobol D Re: Figures on Itanic migration plans by HP-UX, VMS, and Tru64 usersD RE: Figures on Itanic migration plans by HP-UX, VMS, and Tru64 users Re: HPworld - I Survived RE: HPworld - I Survived8 Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM8 Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM8 Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM8 Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM8 Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM Re: Missing Display & need help with strange cluster problem Re: Re, Re : set prompt  Re: Re, Re : set prompt / Unix clusters? Was: If OVMS is killed by HP.... : Re: [OpenVMS Alpha V7.3-2] Known Problems with last ECOs ?: Re: [OpenVMS Alpha V7.3-2] Known Problems with last ECOs ?: Re: [OpenVMS Alpha V7.3-2] Known Problems with last ECOs ?: Re: [OpenVMS Alpha V7.3-2] Known Problems with last ECOs ?  F ----------------------------------------------------------------------  % Date: Sun, 22 Aug 2004 09:08:12 -0400 # From: "John Smith" <a@nonymous.com> * Subject: Re: A whopping 50 percent...  ???, Message-ID: <f5OdnfGD0pAgB7XcRVn-gw@igs.net>   David Froble wrote:  > Ray wrote: > G >> Back in the Digital days, when the Digital UNIX boys went calling on A >> the VMS customers telling them that VMS was dead, UNIX was the @ >> future, and you need to get off VMS and onto UNIX, I rememberD >> hearing a statistic that said out of every six VMS customers thatG >> switched, only *one* switched to Digital UNIX. As UNIX's go, Digital C >> UNIX wasn't bad, <sarcasm>so perhaps there were other factors at  >> work?</sarcasm> >>B >> Given this past behavior, 50% retention seems quite optimistic. >> >> >> > F > I've never understood expanding your customer base at the expense ofC > another segment of YOUR OWN COMPANY.  Then again, I've read about < > significant antagonism between VMS and Unix people at DEC.E > Regardless, at some level management should have realized that they > > were falling on their own sword and put a firm stop to such. > E > Not quite the same as the HP issue.  It's not a different OS on the 
 > same HW,# > it's the same OS on different HW.     H Cannibalizing your own customer base makes some sense rather than losing# your customer base to a competitor.   D The problem with Digital/Compaq/HP's approach in suggesting that VMSG customers move to unix, Windows, or Linux is that none of these options K provide as high a profit margin to the vendor nor do they necessarily offer J a better overall value proposition (security, stability, scalability, ease9 of programming, operating costs, etc...) to the customer.   H I have never seen IBM go out of its way to try and convince one of theirK MVS/OS390/ZoS customers that unix/windows/linux is what the customer should G move to. IBM simply states that they can offer these options and if the I customer so decides to lean that way IBM can help - Period. Now if Sun or J some other vendor comes along to try and poach that IBM customer to a unixB or other non-IBM environment, IBM fights tooth-and-nail to either:D a) keep the mainframe customer a mainframe customer (preferably), orH b) if a) is a lost cause, IBM will offer an IBM-based unix/Windows/linux solution  G But IBM does not go out of the way to slag its own flagship product has  Digital/Compaq/HP .    ------------------------------  % Date: Sun, 22 Aug 2004 06:49:29 -0700 # From: "Tom Linden" <tom@kednos.com> * Subject: RE: A whopping 50 percent...  ???9 Message-ID: <NDEMLKKEBOIFBMJLCECIEEANDLAA.tom@kednos.com>    < -----Original Message-----* < From: John Smith [mailto:a@nonymous.com]' < Sent: Sunday, August 22, 2004 6:08 AM  < To: Info-VAX@Mvb.Saic.Com + < Subject: Re: A whopping 50 percent... ???  <  <  < David Froble wrote:  < > Ray wrote: < > I < >> Back in the Digital days, when the Digital UNIX boys went calling on C < >> the VMS customers telling them that VMS was dead, UNIX was the B < >> future, and you need to get off VMS and onto UNIX, I rememberF < >> hearing a statistic that said out of every six VMS customers thatI < >> switched, only *one* switched to Digital UNIX. As UNIX's go, Digital E < >> UNIX wasn't bad, <sarcasm>so perhaps there were other factors at  < >> work?</sarcasm> < >>D < >> Given this past behavior, 50% retention seems quite optimistic. < >> < >> < >> < > H < > I've never understood expanding your customer base at the expense ofE < > another segment of YOUR OWN COMPANY.  Then again, I've read about > < > significant antagonism between VMS and Unix people at DEC.G < > Regardless, at some level management should have realized that they @ < > were falling on their own sword and put a firm stop to such. < > G < > Not quite the same as the HP issue.  It's not a different OS on the  < > same HW,% < > it's the same OS on different HW.  <  < J < Cannibalizing your own customer base makes some sense rather than losing% < your customer base to a competitor.  < F < The problem with Digital/Compaq/HP's approach in suggesting that VMSI < customers move to unix, Windows, or Linux is that none of these options ; < provide as high a profit margin to the vendor nor do they  < necessarily offer L < a better overall value proposition (security, stability, scalability, ease; < of programming, operating costs, etc...) to the customer.  < J < I have never seen IBM go out of its way to try and convince one of their= < MVS/OS390/ZoS customers that unix/windows/linux is what the  < customer should I < move to. IBM simply states that they can offer these options and if the K < customer so decides to lean that way IBM can help - Period. Now if Sun or L < some other vendor comes along to try and poach that IBM customer to a unixD < or other non-IBM environment, IBM fights tooth-and-nail to either:F < a) keep the mainframe customer a mainframe customer (preferably), orJ < b) if a) is a lost cause, IBM will offer an IBM-based unix/Windows/linux
 < solution  D The difference between HP and IBM, is that HP is driven by strategic thinkingL whereas IBM is market driven.  The problem is you can't outguess the market.   < I < But IBM does not go out of the way to slag its own flagship product has  < Digital/Compaq/HP .  <  <  < --- ( < Incoming mail is certified Virus Free.< < Checked by AVG anti-virus system (http://www.grisoft.com).A < Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004  <  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).? Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004    ------------------------------  % Date: Sun, 22 Aug 2004 00:49:02 -0500 - From: Hunter Goatley <goathunter@goatley.com> 4 Subject: ANN: BOSS for IA64 (and other freeware too)6 Message-ID: <MsWVc.7564$_h.615@bignews3.bellsouth.net>  8 BOSS, the old multi-session manager that lets you log in> to multiple sessions from one terminal using pseudo-terminals,9 is now available for OpenVMS IA64, in addition to VAX and < Alpha.  I only had to make a minor edit to get it to compile> and run.  I still occasionally find BOSS useful, even in these) days of multiple TELNET and SSH sessions.   < If you're looking for OpenVMS IA64 freeware for VMS, you can@ use my FILESERV search engine to see what packages are available= for IA64 now.  Among the packages there that have been ported < are: ZIP, UNZIP, FLIST, HGSD, MMK, HGFTP, BOSS, BAT, the DBS utilities, and more.   http://www.process.com/openvms/   4 ftp://ftp.process.com/vms-freeware/fileserv/boss.zip  ) And on the usual mirrors within 24 hours.      Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/ ; <goathunter@GOATLEY.COM>     http://www.goatley.com/hunter/    ------------------------------  % Date: Sun, 22 Aug 2004 19:18:05 +0800 , From: Paul Repacholi <prep@prep.synonet.com>8 Subject: Re: Anybody got a version of the VAXELN toolkit0 Message-ID: <87smafh15e.fsf@k9.prep.synonet.com>  # nyce3000@hotmail.com (Dave) writes:   H > I am currently testing a real-time version of a VAX emulator and wouldC > very much like to get hold of a version of the VAXELN toolkit. Is ( > there anybody out there with a copy???  E Any old Vax condist will do the job. It is not the hotest item in the  update stakes recently.   3 Be a good candidate for the freeware disk though :)    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sun, 22 Aug 2004 11:07:31 -0400 ' From: "Main, Kerry" <kerry.main@hp.com> # Subject: RE: charon vax emulator??? R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB3DFC15@tayexc19.americas.cpqcorp.net>   > -----Original Message-----4 > From: David Froble [mailto:davef@tsoft-inc.com]=20 > Sent: August 20, 2004 2:09 PM  > To: Info-VAX@Mvb.Saic.Com % > Subject: Re: charon vax emulator???  >=20  
 [..snip..]  A > My understanding is that when running CHARON-VAX on an Intel=20  > box it is=20= > recommended to be the sole user.  Seems that there are a=20  > bunch of OS things that=20! > aren't required in such a case.  >=20   Dave -  F My biggest concern when I hear Cust's considering Charon-VAX (or otherF emulators) on x86 boxes for even semi-mission critical environments is? the monthly security/virus patches as recommended by Microsoft.   F While these typically require system reboots, the biggest issue is notD the reboot time (bad enough though), but rather the time required toD qualify these monthly (and some semi-monthly) patches before loadingG them into production i.e. most companies with semi-mission critical and F higher type stuff need to certify/test any patches before loading them into production.  B Customers running on VAX have not had to worry about this and theyF should fully understand what it is they are getting into before making	 the jump.   F Note - this has nothing to do with CHARON-VAX or any other emulator on$ x86, but rather the entire solution.   Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  Email: kerryDOTmainAThpDOTcom . (remove the DOT's and AT for email address)=20  $ "OpenVMS has always had integrity .. Now, Integrity has OpenVMS .."   ------------------------------  % Date: Sun, 22 Aug 2004 11:39:32 -0400 ) From: Andrew Robert <arobert@townisp.com> # Subject: Re: charon vax emulator??? 0 Message-ID: <10ihffskejh6713@corp.supernews.com>   Main, Kerry wrote: >>-----Original Message-----2 >>From: David Froble [mailto:davef@tsoft-inc.com]  >>Sent: August 20, 2004 2:09 PM  >>To: Info-VAX@Mvb.Saic.Com % >>Subject: Re: charon vax emulator???  >> >  >  > [..snip..] >  > ? >>My understanding is that when running CHARON-VAX on an Intel   >>box it is ; >>recommended to be the sole user.  Seems that there are a   >>bunch of OS things that ! >>aren't required in such a case.  >> >  >  > Dave - > H > My biggest concern when I hear Cust's considering Charon-VAX (or otherH > emulators) on x86 boxes for even semi-mission critical environments isA > the monthly security/virus patches as recommended by Microsoft.  > H > While these typically require system reboots, the biggest issue is notF > the reboot time (bad enough though), but rather the time required toF > qualify these monthly (and some semi-monthly) patches before loadingI > them into production i.e. most companies with semi-mission critical and H > higher type stuff need to certify/test any patches before loading them > into production. > D > Customers running on VAX have not had to worry about this and theyH > should fully understand what it is they are getting into before making > the jump.  > H > Note - this has nothing to do with CHARON-VAX or any other emulator on& > x86, but rather the entire solution. > 	 > Regards  >  > Kerry Main > Senior Consultant  > HP Services Canada > Voice: 613-592-4660  > Fax: 613-591-4477  > Email: kerryDOTmainAThpDOTcom . > (remove the DOT's and AT for email address)  > & > "OpenVMS has always had integrity ..  > Now, Integrity has OpenVMS .." >   G I agree that running a VAX emulator on a Microsoft box is risky due to  % trojans, virii, security issues, etc.   ( That is why I would recommend you don't.  9 Instead, I would run an emulator running on top of Linux.   F I've run the Simh VAX emulator on Fedora CORE1 and Fedora CORE2 linux  for some time without issue.   ------------------------------  % Date: Sun, 22 Aug 2004 09:17:42 -0700 # From: "Tom Linden" <tom@kednos.com> # Subject: RE: charon vax emulator??? 9 Message-ID: <NDEMLKKEBOIFBMJLCECIMEBDDLAA.tom@kednos.com>    < -----Original Message-----2 < From: Andrew Robert [mailto:arobert@townisp.com]' < Sent: Sunday, August 22, 2004 8:40 AM  < To: Info-VAX@Mvb.Saic.Com % < Subject: Re: charon vax emulator???  <  <  < Main, Kerry wrote: < >>-----Original Message-----3 < >>From: David Froble [mailto:davef@tsoft-inc.com] ! < >>Sent: August 20, 2004 2:09 PM  < >>To: Info-VAX@Mvb.Saic.Com ' < >>Subject: Re: charon vax emulator???  < >> < >  < >  < > [..snip..] < >  < > @ < >>My understanding is that when running CHARON-VAX on an Intel
 < >>box it is < < >>recommended to be the sole user.  Seems that there are a < >>bunch of OS things that # < >>aren't required in such a case.  < >> < >  < > 
 < > Dave - < > J < > My biggest concern when I hear Cust's considering Charon-VAX (or otherJ < > emulators) on x86 boxes for even semi-mission critical environments isC < > the monthly security/virus patches as recommended by Microsoft.  < > J < > While these typically require system reboots, the biggest issue is notH < > the reboot time (bad enough though), but rather the time required toH < > qualify these monthly (and some semi-monthly) patches before loadingK < > them into production i.e. most companies with semi-mission critical and J < > higher type stuff need to certify/test any patches before loading them < > into production. < > F < > Customers running on VAX have not had to worry about this and theyJ < > should fully understand what it is they are getting into before making
 < > the jump.  < > J < > Note - this has nothing to do with CHARON-VAX or any other emulator on( < > x86, but rather the entire solution. < >  < > Regards  < >  < > Kerry Main < > Senior Consultant  < > HP Services Canada < > Voice: 613-592-4660  < > Fax: 613-591-4477 ! < > Email: kerryDOTmainAThpDOTcom / < > (remove the DOT's and AT for email address)  < > ( < > "OpenVMS has always had integrity .." < > Now, Integrity has OpenVMS .." < >  < H < I agree that running a VAX emulator on a Microsoft box is risky due to' < trojans, virii, security issues, etc.  < * < That is why I would recommend you don't. < ; < Instead, I would run an emulator running on top of Linux.  < G < I've run the Simh VAX emulator on Fedora CORE1 and Fedora CORE2 linux  < for some time without issue.  G Now what would be interesting is to use Linux to cobble together an SRM G emulator.  When Linux boots it inspects the hardware to determine which F drivers to load.  Once that is known you could then bind an executableF with these drivers loaded, to emulate the SRM console in the form of a monitor C and then to boot this stand alone, possibly using milo and linload.    <  < --- ( < Incoming mail is certified Virus Free.< < Checked by AVG anti-virus system (http://www.grisoft.com).A < Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004  <  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).? Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004    ------------------------------  # Date: Sun, 22 Aug 2004 07:10:22 GMT 3 From: Michael Grunditz <michael.grunditz@telia.com>  Subject: cobol1 Message-ID: <1a3860e24c.michael@privat.utfors.se>    Hi  > I am looking for a cobol compiler for my vms vax. I have found? a kit , but unfortunaly it was a japanese one. On the same site B I found decwriter and other stuff , but I think that they are also unsable to me.   Michael Grunditz   ------------------------------  % Date: Sun, 22 Aug 2004 14:28:07 +0200 . From: Frank Themann <frankthemann@T-Online.de> Subject: Re: cobol+ Message-ID: <41289157.FA963E52@T-Online.de>    Michael Grunditz wrote:  >  > Hi > @ > I am looking for a cobol compiler for my vms vax. I have foundA > a kit , but unfortunaly it was a japanese one. On the same site D > I found decwriter and other stuff , but I think that they are also > unsable to me.  G Im not sure, but isnt the cobol compiler, besides others, included in E the OpenVMS Hobbyist CD? The license is part of the hobbyists layered F products license kit. If you use your VAX as a hobbyist, this would be an approach.  
 Frank Themann    ------------------------------  % Date: Sun, 22 Aug 2004 09:19:27 -0400 # From: "John Smith" <a@nonymous.com> M Subject: Re: Figures on Itanic migration plans by HP-UX, VMS, and Tru64 users , Message-ID: <DJSdnW1Xnrn9ALXcRVn-og@igs.net>   David Froble wrote:  > Tom Linden wrote:  >  >> >> < -----Original Message----- 4 >> < From: David Froble [mailto:davef@tsoft-inc.com] >  >  > <snip a bunch of stuff>  >  > F >> < The only reason itanic will get faster than Alphas is the lack of >> < newer faster  >> < Alphas. >>, >> Which mirrors the VAX to Alpha transition > F > Oh yes, definitely.  The N-VAX was quite successful, technically forB > sure, and I'd have to say financally also.  I seem to remember aE > MicroVAX 3100 model 96 (the last N-VAX chip) selling for about $37K C > with VMS, while a much faster AlphaServer 1000 (I think) sold for D > $18K with VMS.  DEC was milking the VAX cow, and unfairly I think.E > Customers don't like to feel screwed.  Through-out most of the life < > of the VAX, DEC milked the customers, and drove many away.  F This is EXACTLY the reason why Sun and other unix vendors were able toK extablish a beachhead. Digital OWNED the mid-range market (aside from IBM's J S38 and AS400) and could have made unix a stillborn commercial exercise by lowering prices on VMS.   G I suppose the real problem was DEC management's inability to 'adapt and E embrace change' (is there an echo here?) and at the same time adopt a I different management culture which would have allowed them to lower their L internal expenses at the same time as lowering prices to customers - thereby? permitting DEC to keep similar gross margins and profitability.   L Note to HP: Most of the "world's great companies" value staying in business.8 Reliable computing is one of those ways...Windows isn't.   ------------------------------  % Date: Sun, 22 Aug 2004 07:57:33 -0700 # From: "Tom Linden" <tom@kednos.com> M Subject: RE: Figures on Itanic migration plans by HP-UX, VMS, and Tru64 users 9 Message-ID: <NDEMLKKEBOIFBMJLCECIIEAPDLAA.tom@kednos.com>    < -----Original Message-----1 < From: David Froble [mailto:davef@tsoft-inc.com] ) < Sent: Saturday, August 21, 2004 8:28 PM  < To: Info-VAX@Mvb.Saic.Com I < Subject: Re: Figures on Itanic migration plans by HP-UX, VMS, and Tru64  < users  <  <  < Tom Linden wrote:  <  < >   < > < -----Original Message-----5 < > < From: David Froble [mailto:davef@tsoft-inc.com]  <  <  < <snip a bunch of stuff>  <  < G < > < The only reason itanic will get faster than Alphas is the lack of  < > < newer faster
 < > < Alphas.  < > - < > Which mirrors the VAX to Alpha transition  < B < Oh yes, definitely.  The N-VAX was quite successful, technically < for sure, and A < I'd have to say financally also.  I seem to remember a MicroVAX  < 3100 model 96 @ < (the last N-VAX chip) selling for about $37K with VMS, while a
 < much faster = < AlphaServer 1000 (I think) sold for $18K with VMS.  DEC was  < milking the VAX cow,> < and unfairly I think.  Customers don't like to feel screwed. < Through-out mostH < of the life of the VAX, DEC milked the customers, and drove many away. < @ < The Alpha was/is 64 bit, while the VAX was 32 bit, but at that < time there just ? < weren't many 64 bit apps.  Don't know what type of gain there  < would be with a 64? < bit VAX.  Don't know how far the architechure could have been  < pushed.  I don'tA < think that any VAX could have allowed pushing the clock rate as  < much as Alpha,K < as that was one of the prime design goals with Alpha.  But, while AMD has < < recently been making chips with clock rates well below the < Pentium 4, theirJ < performance is right up there with the Pentium.  Clock isn't everything. <   K Of course the clock rate on VAX could have been increased as much as Alpha, L they just gave up on it, and yes it could also have been extended to 64 bit.F A VAX clock rate of half as much as Alpha would probably give the same performance.     < Dave <  < --6 < David Froble                       Tel: 724-529-04506 < Dave Froble Enterprises, Inc.      Fax: 724-529-0596@ < DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com < 170 Grimplin Road  < Vanderbilt, PA  15486  <  < --- ( < Incoming mail is certified Virus Free.< < Checked by AVG anti-virus system (http://www.grisoft.com).A < Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004  <  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).? Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004    ------------------------------    Date: 22 Aug 2004 07:16:28 -0700! From: wilmesr@hotmail.com (Rusty) ! Subject: Re: HPworld - I Survived = Message-ID: <f0d7bf28.0408220616.36fc8928@posting.google.com>   C At one of the VMS sessions they mentioned a promotion for an RX2600  series w/ VMS for $900.   % I can't find any mention at hp.com.      Anyone have any info on this?    ------------------------------  % Date: Sun, 22 Aug 2004 13:29:55 -0400 ' From: "Main, Kerry" <kerry.main@hp.com> ! Subject: RE: HPworld - I Survived R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB3DFC18@tayexc19.americas.cpqcorp.net>   > -----Original Message------ > From: Rusty [mailto:wilmesr@hotmail.com]=20   > Sent: August 22, 2004 10:16 AM > To: Info-VAX@Mvb.Saic.Com # > Subject: Re: HPworld - I Survived  >=20E > At one of the VMS sessions they mentioned a promotion for an RX2600  > series w/ VMS for $900.  >=20) > I can't find any mention at hp.com. =20  >=20 > Anyone have any info on this?  >=20   Rusty,  D I suspect that you may have heard about the following somewhat dated
 promotion:J http://h30046.www3.hp.com/promofile_oov.php?promo=3D1-27LB&portal=3DPRODU= CTS   E Note that the fine print says you get the rx2600 for USD$990 with the 7 purchase of an OpenVMS based ES/GS Series Alpha system.   E However, there are other alternatives as well for getting rx2600's as F well. A recent post on this newsgroup indicated that there were 2600's to be had for less than USD$2K.   D Keep in mind that in addition to OpenVMS, these 2600's will also runB Linux, Windows64 and HP-UX on the same server as well, so they are pretty flexible dev boxes.   Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  Email: kerryDOTmainAThpDOTcom . (remove the DOT's and AT for email address)=20  $ "OpenVMS has always had integrity .. Now, Integrity has OpenVMS .."   ------------------------------  % Date: Sun, 22 Aug 2004 03:38:35 -0400   From: John Santos <JOHN@egh.com>A Subject: Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM 6 Message-ID: <1040822032548.19425R-100000@Ives.egh.com>  ( On Sat, 21 Aug 2004, David Froble wrote:   > Starlet731 wrote:  > 
 > > Hello, > > ( > > I have a problem with the following: > > J > > PWS 600au has no supported CD-ROM drive for OpenVMS (i.e. not 512 byte > > sectored)!O > > So I can not boot the installation CD-ROM on the PWS. I have OpenVMS V7.3-1 K > > and an AlphaServer 1000 4/200 with a supported CD-ROM drive and OpenVMS  > > installed on it.I > > Now I have read that I can install OpenVMS on the PWS via the network O > > (ethernet) form the AlphaServer with a cluster configuration. By the way: I  > > use the hobbyist licenses.P > > How must I accomplish this to get OpenVMS installed on the local disk on theO > > PWS? Can I do that directly from the mounted OpenVMS installation CD-ROM on A > > the AlphaServer (via the net), or must I do this another way? K > > Is there a link on the net with a more detailed explanation to do this?  > >  > > Thank you for your help! > >  > >  > >  > R > 1) take the PWS disk, put it in the AlphaServer 1000, build VMS, move disk back  > to PWS, autogen. > 7 > 2) take CD drive from AS 1000, put in PWS, build VMS.  > R > 3) (best option) get another CD drive for PWS.  You can find one for well under  > $20.  Maybe under $10. >  > Dave  G If PWS will boot over the network, you can add a 2nd node for it on the E AS1000 ($ @sys$manager:cluster_config_lan), boot it into the cluster, F enable MSCP disk serving on it, mount the PWS disk /foriegn (on eitherM the AS1000 or the PWS), backup/image/ignore=interlock AS1000_disk: PWS_disk:, G dismount the PWS_DISK:, remount it file-structured, change its label to F avoid conflicts, ana/disk/repair it to fix the broken stuff due to theE online backup, shutdown and reboot the PWS from its local disk, using H the root directory you made for it.  If the two systems are not going toF permanenly live in a cluster, change VAXCLUSTER to 0 in MODPARAMS.DAT, autogen and reboot.   C Remember you'll still have to use the PWS's root directory when you H boot it, either from its local disk or via the network, or it will think/ it is the AS1000, leading to network conflicts.   D Deleting the extra roots and renaming the remaining on to [sys0.] is# left as an exercise for the reader.    --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Sun, 22 Aug 2004 16:57:42 +0200 - From: "Starlet731" <starlet731@attglobal.net> A Subject: Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM 0 Message-ID: <YpKdnd9sict6LrXcRVnyjw@scarlet.biz>  I Does this explanation assume that there is something installed yet on the L PWS. I want to start from the situation with totally blanc disks on the PWS.J How is it booted into the cluster formed with the AS1000. How must this be% done from the SRM console on the PWS?    Thanks!   / "John Santos" <JOHN@egh.com> schreef in bericht 0 news:1040822032548.19425R-100000@Ives.egh.com...* > On Sat, 21 Aug 2004, David Froble wrote: >  > > Starlet731 wrote:  > >  > > > Hello, > > > * > > > I have a problem with the following: > > > L > > > PWS 600au has no supported CD-ROM drive for OpenVMS (i.e. not 512 byte > > > sectored)!J > > > So I can not boot the installation CD-ROM on the PWS. I have OpenVMS V7.3-1E > > > and an AlphaServer 1000 4/200 with a supported CD-ROM drive and  OpenVMS  > > > installed on it.K > > > Now I have read that I can install OpenVMS on the PWS via the network J > > > (ethernet) form the AlphaServer with a cluster configuration. By the way: I  > > > use the hobbyist licenses.K > > > How must I accomplish this to get OpenVMS installed on the local disk  on theG > > > PWS? Can I do that directly from the mounted OpenVMS installation 	 CD-ROM on C > > > the AlphaServer (via the net), or must I do this another way? G > > > Is there a link on the net with a more detailed explanation to do  this?  > > >  > > > Thank you for your help! > > >  > > >  > > >  > > I > > 1) take the PWS disk, put it in the AlphaServer 1000, build VMS, move 	 disk back  > > to PWS, autogen. > > 9 > > 2) take CD drive from AS 1000, put in PWS, build VMS.  > > H > > 3) (best option) get another CD drive for PWS.  You can find one for
 well under > > $20.  Maybe under $10. > >  > > Dave > I > If PWS will boot over the network, you can add a 2nd node for it on the G > AS1000 ($ @sys$manager:cluster_config_lan), boot it into the cluster, H > enable MSCP disk serving on it, mount the PWS disk /foriegn (on eitherD > the AS1000 or the PWS), backup/image/ignore=interlock AS1000_disk:
 PWS_disk:,I > dismount the PWS_DISK:, remount it file-structured, change its label to H > avoid conflicts, ana/disk/repair it to fix the broken stuff due to theG > online backup, shutdown and reboot the PWS from its local disk, using J > the root directory you made for it.  If the two systems are not going toH > permanenly live in a cluster, change VAXCLUSTER to 0 in MODPARAMS.DAT, > autogen and reboot.  > E > Remember you'll still have to use the PWS's root directory when you J > boot it, either from its local disk or via the network, or it will think1 > it is the AS1000, leading to network conflicts.  > F > Deleting the extra roots and renaming the remaining on to [sys0.] is% > left as an exercise for the reader.  >  > --  
 > John Santos  > Evans Griffiths & Hart, Inc. > 781-861-0670 ext 539 >    ------------------------------  % Date: Sun, 22 Aug 2004 16:49:19 +0200 - From: "Starlet731" <starlet731@attglobal.net> A Subject: Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM 0 Message-ID: <f5CdndR-ptlyLLXcRVnyjQ@scarlet.biz>  I Can't it be done in a less labor intensive way (not swapping the physical K disks or CD-ROM's) because I hate messing with the computer hardware. Can I D do this with a cluster configuration between the PWS and the AS1000?J How do I configure the AS1000 to serve the installation CD-ROM to the PWS.L How do I boot then the PWS from the SRM console (via network interface EWA0)4 with the installation CD in the AS1000 CD-ROM drive?   Thanks7 "David Froble" <davef@tsoft-inc.com> schreef in bericht & news:412814DD.9060003@tsoft-inc.com... > Starlet731 wrote:  > 
 > > Hello, > > ( > > I have a problem with the following: > > J > > PWS 600au has no supported CD-ROM drive for OpenVMS (i.e. not 512 byte > > sectored)!H > > So I can not boot the installation CD-ROM on the PWS. I have OpenVMS V7.3-1K > > and an AlphaServer 1000 4/200 with a supported CD-ROM drive and OpenVMS  > > installed on it.I > > Now I have read that I can install OpenVMS on the PWS via the network H > > (ethernet) form the AlphaServer with a cluster configuration. By the way: I > > use the hobbyist licenses.L > > How must I accomplish this to get OpenVMS installed on the local disk on the L > > PWS? Can I do that directly from the mounted OpenVMS installation CD-ROM onA > > the AlphaServer (via the net), or must I do this another way? K > > Is there a link on the net with a more detailed explanation to do this?  > >  > > Thank you for your help! > >  > >  > >  > L > 1) take the PWS disk, put it in the AlphaServer 1000, build VMS, move disk back > to PWS, autogen. > 7 > 2) take CD drive from AS 1000, put in PWS, build VMS.  > K > 3) (best option) get another CD drive for PWS.  You can find one for well  under  > $20.  Maybe under $10. >  > Dave >  > --  6 > David Froble                       Tel: 724-529-04506 > 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, 22 Aug 2004 14:59:01 +0000 (UTC) 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)A Subject: Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM 1 Message-ID: <newscache$a2su2i$vdx1$1@news.sil.at>   ` In article <f5CdndR-ptlyLLXcRVnyjQ@scarlet.biz>, "Starlet731" <starlet731@attglobal.net> writes:J >Can't it be done in a less labor intensive way (not swapping the physicalL >disks or CD-ROM's) because I hate messing with the computer hardware. Can IE >do this with a cluster configuration between the PWS and the AS1000?   K Yes. Use the AS1000 as a bootserver for the PWS. Use the PWS as a satellite D to backup the VMS CD to a local SCSI disk, then boot the PWS locallyH from this (installation) disk and install VMS on another local PWS disk.  K >How do I configure the AS1000 to serve the installation CD-ROM to the PWS.    No problem with serving the CD, 8 but a problem installing OpenVMS from an MSCP served CD.  M >How do I boot then the PWS from the SRM console (via network interface EWA0) 5 >with the installation CD in the AS1000 CD-ROM drive?o   Not at all.   D OTOH, you can use the undocumented/unsupported infoserver feature ofH OpenVMS Alpha V8 to serve the AS1000 CD via a LAST service to the PWS...   -- y Peter "EPLAN" LANGSTOEGERs% Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Sun, 22 Aug 2004 17:42:14 +0200 - From: "Starlet731" <starlet731@attglobal.net>pA Subject: Re: Installing OpenVMS Alpha on PWS 600au without CD-ROM 0 Message-ID: <noSdnQ6AabrII7XcRVnyuA@scarlet.biz>  I I have 2 local disks in the PWS, so your proposed configuration procedureuL would work, but how do I boot the PWS into the cluster via the EWA0 ethernet  interface from it's SRM console?  K Is this with BOOT EWA0? When I do this it continuously retries and will notpJ boot into the cluster. Do have have to give other options to this command?   Thanks!i  E "Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> schreef in bericht?+ news:newscache$a2su2i$vdx1$1@news.sil.at...-? > In article <f5CdndR-ptlyLLXcRVnyjQ@scarlet.biz>, "Starlet731"0" <starlet731@attglobal.net> writes:L > >Can't it be done in a less labor intensive way (not swapping the physicalL > >disks or CD-ROM's) because I hate messing with the computer hardware. Can ItG > >do this with a cluster configuration between the PWS and the AS1000?s >lC > Yes. Use the AS1000 as a bootserver for the PWS. Use the PWS as ao	 satelliteSF > to backup the VMS CD to a local SCSI disk, then boot the PWS locallyJ > from this (installation) disk and install VMS on another local PWS disk. >UH > >How do I configure the AS1000 to serve the installation CD-ROM to the PWS. >s! > No problem with serving the CD,v: > but a problem installing OpenVMS from an MSCP served CD. >>I > >How do I boot then the PWS from the SRM console (via network interfacex EWA0)f7 > >with the installation CD in the AS1000 CD-ROM drive?e >a
 > Not at all.n >cF > OTOH, you can use the undocumented/unsupported infoserver feature ofJ > OpenVMS Alpha V8 to serve the AS1000 CD via a LAST service to the PWS... >  > -- n > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialistI > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   Date: 22 Aug 2004 13:34:53 GMT/ From: Thierry Dussuet <thierry@dussuet.lugs.ch>l Subject: Re: Missing Display1 Message-ID: <slrncih87t.1mq3.thierry@MARS.Family>   
 Good morning!e  3 On 2004-08-20, Hoff Hoffman <hoff@hp.nospam> wrote:te > In article <slrncicdaj.1mq3.thierry@MARS.Family>, Thierry Dussuet <thierry@dussuet.lugs.ch> writes:a >iN >:I have a VAXstation 3100/38 at home which has the switch set as a VAXserver.N >:Since some time I see such messages every 5 minutes, which fill up the audit. >:log, and I'm wondering where they come from. >:* >:Message from user AUDIT$SERVER on MERKURO >:Security alarm (SECURITY) and security audit (SECURITY) on MERKUR, system id:M >:26825 : >:Auditable event:          Detached process login failure > ..< >:The message number means "No display found", but I have no3 >:keyboard/mouse/monitor hooked up to the computer.  >nC >   Enable security alarms for process creations.  That should say.o  ; It did!  Learning new wonderful things about VMS every day.i  A >   I'd also ensure that DECwindows was properly disabled for thedD >   particular OpenVMS VAX version -- the current mechanism involves5 >   DECW$IGNORE_WORKSTATION, as discussed in the FAQ."  N DECW$IGNORE_WORKSTATION was set to TRUE already, although I hadn't seen it was in the FAQ.C  A >   When posting, the OpenVMS VAX and DECwindows versions and ECOoB >   level -- if not current on at least the available ECOs, please' >   get there -- can be useful details.u  O Excuse me I didn't think about this - This is OpenVMS 7.3 with DECwindows 1.2-5r and all the ECOs I could find.  M The problem was an XDM server I had tried to setup when going to headless andl9 forgotten to disable after seeing that it did not work...d   Thank you for your help!   Thierry    ------------------------------  + Date: Sun, 22 Aug 2004 08:38:15 +0000 (UTC)tP From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)/ Subject: need help with strange cluster problemo- Message-ID: <cg9m1n$1u6q$1@godfrey.mcc.ac.uk>   I My hobbyist cluster consists of three nodes, each with one vote: GLADIA, >H DANEEL and ELIJAH.  GLADIA is an ALPHA, the other two nodes are VAXes.  F Almost all disks are shadow sets with members mounted two nodes.  All E disks are MSCP served to all nodes, and all disks are mounted by all  F nodes.  SYSUAF.DAT etc are on the DISK$USER shadow set.  This disk is I mounted by each node in SYLOGICALS.COM and logicals are defined to point   to SYSUAF.DAT etc.  I Returning after a few weeks holiday, during which no member rebooted and tH there were apparently no serious problems, I noticed that the member of E DISK$USER on DANEEL was "Online" "ShadowSetMember".  I didn't try to oH MOUNT it again into the shadow set, since I had just rebooted GLADIA in I order to bring it back up with just one member of the system-disk shadow hD set, since I planned to install 9 patches (leaving the disconnected G member as a clean backup should something go wrong with the patches).  yD When GLADIA came back up, it tried and failed to mount the "Online" G member into DISK$USER.  I then waited for the shadow copy of DISK$SOFT tH to complete, since this is distributed across DANEEL and GLADIA, then I  shut down DANEEL.   I Note that I didn't install any patches on any machines since last June.  tG In particular, I haven't yet installed the 9 patches I need to install e
 on GLADIA.  I From the console prompt, DANEEL could see its half of DISK$USER fine.  I tD rebooted, and apparently all went well: the member was added to the 3 shadow set with a copy operation.  So far, so good.e   I then went to sleep.r  F In the morning, I found the following situation: the member on DANEEL H was still in the "ShadowCopying" state, but the member on ELIJAH was no I longer in the state "ShadowSetMember", but rather "ShadowMergeMbr".  All aI other shadow sets look fine.  The copying was 76% complete (now 88%) and g
 0% merged.  D I then discovered that ELIJAH had spontaneously rebooted during the D night, while I was sleeping.  ANALYZE shows "inconsistent shadowing  state" as the reason.   5 That would explain things, but why did ELIJAH reboot?6  G DISK$USER had the member on DANEEL in the "ShadowCopying" state before tH the reboot of ELIJAH, which was of course correct.  It has it now after I the reboot of ELIJAH as well.  Presumably that is correct and the shadow   copy started again.9  A There are problems on node GLADIA, however, since DISK$USER is inAI mount-verify timeout (there was no problem when I went to sleep).  Since bG SYSUAF.DAT etc are on this disk, lots of things are failing which need o to access these files.  H So, my plans are to wait until the shadow copy of DISK$USER is complete E (not necessary, but since rebooting GLADIA will cause another shadow iF copy to start, and bandwidth (10BaseT) is low, I just want one shadow # copy at a time) then reboot GLADIA.E  I The console on GLADIA tells me to run SYS$SYSTEM:IMGDMP_RIGHTS, but that y2 fails since the necessary files can't be accessed!  I So: missing disk on DANEEL apparently corrected OK.  Strange spontaneous p= reboot of ELIJAH.  Strange problem on GLADIA.  All unrelated?e   ------------------------------  % Date: Sun, 22 Aug 2004 19:05:00 +0800., From: Paul Repacholi <prep@prep.synonet.com>  Subject: Re: Re, Re : set prompt0 Message-ID: <871xhzigbn.fsf@k9.prep.synonet.com>  0 spamsink2001@yahoo.com (Alan E. Feldman) writes:  Z > VAXman-  @SendSpamHere.ORG wrote in message news:<00A36A14.C8ACC269@SendSpamHere.ORG>...q >> In article <b096a4ee.0408191753.20cf9fc4@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes: \ >> >VAXman-  @SendSpamHere.ORG wrote in message news:<00A3695E.CC43E1CF@SendSpamHere.ORG>...s >> >> In article <b096a4ee.0408190543.722e672@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes:o > [...]e > [...]t >> >> >VAXMAN: default = DEC >> >> >  >> >> > & >> >> >So unless you say otherwise...! >> >>  >> >> I say! >> > >> >  O-kay! >>    >> Typical confrontational NYer. >o > O-kay is confrontational?d > L >> *You* said you wanted a "time" in your prompt.  If it's not on a terminal7 >> and it's not on a DECterm then where the hell is it?a >  > On a SmarTerm window.   : So if it's so smart, why doesn't it know what day it is ;)     -- e< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.y@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sun, 22 Aug 2004 12:34:57 -0500[2 From: David J Dachtera <djesys.nospam@comcast.net>  Subject: Re: Re, Re : set prompt+ Message-ID: <4128D941.1AD7AC89@comcast.net>?   David Froble wrote:  >  > VAXman- wrote: > r > > In article <b096a4ee.0408201824.1701176e@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes: > > \ > >>VAXman-  @SendSpamHere.ORG wrote in message news:<00A36A14.C8ACC269@SendSpamHere.ORG>... > >>s > >>>In article <b096a4ee.0408191753.20cf9fc4@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes:r > >>> ^ > >>>>VAXman-  @SendSpamHere.ORG wrote in message news:<00A3695E.CC43E1CF@SendSpamHere.ORG>... > >>>>t > >>>>>In article <b096a4ee.0408190543.722e672@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes: > >>>>>t	 > >>[...]m	 > >>[...]h > >> > >>>>>>VAXMAN: default = DEC  > >>>>>> > >>>>>>' > >>>>>>So unless you say otherwise...!  > >>>>>>
 > >>>>>I say!t > >>>>>/
 > >>>> O-kay!s > >>>>" > >>>Typical confrontational NYer. > >>>  > >>O-kay is confrontational?w > >> > >>N > >>>*You* said you wanted a "time" in your prompt.  If it's not on a terminal9 > >>>and it's not on a DECterm then where the hell is it?O > >>>r > >>On a SmarTerm window., > >> > >   > > What the hell is a SmarTerm? > >r > >n > O > Among other things, it is a VT terminal emulator that runs on windoz.  RathermS > good emulator.  You may read about Reflections, but I personally prefer SmarTerm.V  E There was a time when R/2 and R/4 were the *ONLY* commercial terminal-G programs for WhineBloze that actually did smooth-scroll (it was lackingnG in R/1 and R/3 circa. 1995 or so, IIRC). Does SmarTerm do smooth-scroll  now?   D.J.D.   ------------------------------  % Date: Sun, 22 Aug 2004 19:12:44 +0800s, From: Paul Repacholi <prep@prep.synonet.com>8 Subject: Unix clusters? Was: If OVMS is killed by HP....3 Message-ID: <87wtzrh1eb.fsf_-_@k9.prep.synonet.com>t  % "John Smith" <a@nonymous.com> writes:   F > Unix clustering first saw the light of day about 25 years after unix@ > was first released and it still isn't in the same class as VMS
 > clustering.   C So to wander into a side path a little :) Who was first in the unix . world with `clustering'? and what sould it do?   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.v@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  + Date: Sun, 22 Aug 2004 06:40:27 +0000 (UTC)t6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)C Subject: Re: [OpenVMS Alpha V7.3-2] Known Problems with last ECOs ? 1 Message-ID: <newscache$dz4u2i$bow1$1@news.sil.at>a  ] In article <4124f71e@usenet01.boi.hp.com>, "Guy Peleg" <guy.peleg@remove_this_hp.com> writes:h6 >If possible, please post the output of CLUE CRASH....   OpenVMS (TM) Operating System, Version V7.3-2   -- System Dump Analysis    1-JAN-2004 00:00:03.38                         Page     1              J                                                          Table of ContentsJ                                                          -----------------    h                              Crashdump Summary Information:                                   ....    2 h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                         h                                                                                                          - OpenVMS (TM) Operating System, Version V7.3-2   -- System Dump Analysis    1-JAN-2004 00:00:03.38                         Page     2 Crashdump Summary Information:      * Crash Time:         1-JAN-2004 00:00:03.38; Bugcheck Type:     INVEXCEPTN, Exception while above ASTDELe$ Node:              LUNA    (Cluster) CPU Type:          v VMS Version:       V7.3-2  - Current Process:   SWAPPER" Current Image:     <not available>4 Failing PC:        FFFFFFFF.80178E00    SYS$VM+16E00$ Failing PS:        10000000.00000800F Module:            SYS$VM    (Link Date/Time:  7-JUL-2004 16:54:51.71) Offset:            00016E00s  * Boot Time:         17-NOV-1858 00:00:00.00* System Uptime:               0 00:00:00.00 Crash/Primary CPU: 00/00 System/CPU Type:   1E05)' Pagesize:          8 KByte (8192 bytes)l< Physical Memory:   640 MByte (81920 PFNs, contiguous memory) Dumpfile Pagelets: 15815 blocks ' Dump Flags:        writecomp,errlogcompo2 Dump Type:         compressed,selective,shared_mem$ EXE$GL_FLAGS:      poolpging,bugdump8 Paging Files:      0 Pagefiles and 0 Swapfiles installed   Stack Pointers:uK KSP = FFFFFFFF.83979C18   ESP = 00000000.00000000   SSP = 00000000.00000000m USP = 00000000.00000000    General Registers:K R0  = 00000000.00000000   R1  = 00000000.0000000C   R2  = FFFFFFFF.83979E10 K R3  = FFFFFFFF.82CC45A0   R4  = FFFFFFFF.83979C80   R5  = FFFFFFFF.83979DF8 K R6  = FFFFFFFF.83979E40   R7  = 10000000.00000800   R8  = 00000000.00000000rK R9  = 00000000.00000009   R10 = 00000000.00000009   R11 = FFFFFFFF.833A8004lK R12 = 00000000.00000000   R13 = FFFFFFFF.82CE6D28   R14 = FFFFFFFF.815278C0iK R15 = FFFFFEFE.00033388   R16 = 00000000.000001CC   R17 = FFFFFFFF.83979C80oK R18 = FFFFFFFF.83979E40   R19 = FFFFFFFF.83979F08   R20 = 00000000.00000180gK R21 = 00000000.0000012A   R22 = 00000000.00000000   R23 = FFFFFFFF.82C08000aK R24 = FFFFFFFF.82CE46C0   AI  = FFFFFFFF.82CE46C0   RA  = FFFFFFFF.80178D44uK PV  = FFFFFFFF.82CE6D90   R28 = 00000000.00000000   FP  = FFFFFFFF.83979FA0 1 PC  = FFFFFFFF.800951E8   PS  = 18000000.00000800s   Exception Frame:K R2  = FFFFFFFF.815279B0   R3  = FFFFFFFF.82C091C8   R4  = FFFFFFFF.815278C0tK R5  = 00000000.00000000   R6  = 00000000.00000000   R7  = 00000000.00000000:1 PC  = FFFFFFFF.80178E00   PS  = 10000000.00000800S  = Signal Array:                            64-bit Signal Array: K Arg Count    = 00000005                  Arg Count      =          00000005iK Condition    = 0000000C                  Condition      = 00000000.0000000CtK Argument #2  = 00000004                  Argument #2    = 00000000.00000004lK Argument #3  = 000021A0                  Argument #3    = 00000000.000021A0eK Argument #4  = 80178E00                  Argument #4    = FFFFFFFF.80178E00'K Argument #5  = 00000800                  Argument #5    = 10000000.000008009     OpenVMS (TM) Operating System, Version V7.3-2   -- System Dump Analysis    1-JAN-2004 00:00:03.38                         Page     3 Crashdump Summary Information:       Mechanism Array:K Arguments    = 0000002C                  Establisher FP = FFFFFFFF.83979FA0fK Flags        = 00000000                  Exception FP   = FFFFFFFF.83979E40/K Depth        = FFFFFFFD                  Signal Array   = FFFFFFFF.83979DF8'K Handler Data = FFFFFFFF.82CDC040         Signal64 Array = FFFFFFFF.83979E104K R0  = 00000000.00000001   R1  = 00000000.0000147E   R16 = FFFFFFFF.FFFFFFFF K R17 = FFFFFFFF.FFFFFFF9   R18 = FFFFFFFF.82C08040   R19 = FFFFFFFF.83979F08 K R20 = 00000000.00000180   R21 = 00000000.0000012A   R22 = 00000000.00000000tK R23 = FFFFFFFF.82C08000   R24 = FFFFFFFF.82CE46C0   R25 = FFFFFFFF.82CE46C0eK R26 = FFFFFFFF.80178D44   R27 = FFFFFFFF.82CE6D90   R28 = 00000000.00000000k   System Registers: K Page Table Base Register (PTBR)                           00000000.00000127aK Processor Base Register (PRBR)                            FFFFFFFF.81412000iK Privileged Context Block Base (PCBB)                      00000000.010D8080eK System Control Block Base (SCBB)                          00000000.000009882K Software Interrupt Summary Register (SISR)                00000000.00000000rK Address Space Number (ASN)                                00000000.0000007F K AST Summary / AST Enable (ASTSR_ASTEN)                    00000000.0000000F.K Floating-Point Enable (FEN)                               00000000.000000000K Interrupt Priority Level (IPL)                            00000000.00000008 K Machine Check Error Summary (MCES)                        00000000.00000000tK Virtual Page Table Base Register (VPTB)                   FFFFFEFC.00000000- - OpenVMS (TM) Operating System, Version V7.3-2   -- System Dump Analysis    1-JAN-2004 00:00:03.38                         Page     4 Crashdump Summary Information:       Failing Instruction:$ SYS$VM+16E00:  	STW		R13,#X2020(R20)  * Instruction Stream (last 20 instructions):$ SYS$VM+16DB0:  	LDL		R25,#X0040(R25)" SYS$VM+16DB4:  	S8ADDQ		R9,R25,R25 SYS$VM+16DB8:  	STQ		R0,(R25)- SYS$VM+16DBC:  	RET		R31,(R26)  SYS$VM+16DC0:  	SUBQ		SP,#X80,SP# SYS$VM+16DC4:  	STQ		R26,#X0008(SP) " SYS$VM+16DC8:  	STQ		R2,#X0010(SP)" SYS$VM+16DCC:  	STQ		R3,#X0018(SP)" SYS$VM+16DD0:  	STQ		R4,#X0020(SP)" SYS$VM+16DD4:  	STQ		R5,#X0028(SP)" SYS$VM+16DD8:  	STQ		R6,#X0030(SP)" SYS$VM+16DDC:  	STQ		R7,#X0038(SP)" SYS$VM+16DE0:  	STQ		R8,#X0040(SP)" SYS$VM+16DE4:  	STQ		R9,#X0048(SP)# SYS$VM+16DE8:  	STQ		R10,#X0050(SP) # SYS$VM+16DEC:  	STQ		R11,#X0058(SP)o# SYS$VM+16DF0:  	STQ		R12,#X0060(SP) # SYS$VM+16DF4:  	STQ		R13,#X0068(SP)i# SYS$VM+16DF8:  	STQ		R14,#X0070(SP)v# SYS$VM+16DFC:  	STQ		R15,#X0078(SP) $ SYS$VM+16E00:  	STW		R13,#X2020(R20), SYS$VM+16E04:  	cannot translate instruction$ SYS$VM+16E08:  	STW		R13,#X2020(R20), SYS$VM+16E0C:  	cannot translate instruction  SYS$VM+16E10:  	BR		R28,#X08D000  < It seems, the trace to VMS732_SYS-V0400 is getting warmer...   -- S Peter "EPLAN" LANGSTOEGERo% Network and OpenVMS system specialistw E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  + Date: Sun, 22 Aug 2004 06:43:31 +0000 (UTC)s6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)C Subject: Re: [OpenVMS Alpha V7.3-2] Known Problems with last ECOs ?a1 Message-ID: <newscache$y35u2i$mow1$1@news.sil.at>   X In article <R8QUc.8313$2B3.7064@news.cpqcorp.net>, hoff@hp.nospam (Hoff Hoffman) writes:H >  Check the disk and file fragementation levels.  If it is excessive orH >  if core files are heavily fragmented, try a BACKUP/IMAGE and restore.G >  I've seen problems after ECO installations that have tracked back tou> >  severe disk fragementation; I've learned to check for this.  G I did a defrag to level 1 (on another system) and the crashes are still2F there. It was unlikely but now its out. But thanks for reminding me...   -- a Peter "EPLAN" LANGSTOEGERw% Network and OpenVMS system specialistt E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  + Date: Sun, 22 Aug 2004 15:11:51 +0000 (UTC)h6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)C Subject: Re: [OpenVMS Alpha V7.3-2] Known Problems with last ECOs ?h1 Message-ID: <newscache$4nsu2i$hex1$1@news.sil.at>h  j In article <newscache$8zbn2i$jfl1$1@news.sil.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:H >In the meantime I'll try to remove the ECOs (btw: does anyone know if aI >UNDO can be done while booted from the 7.3-2 CD - which I must boot fromvI >an Infoserver and promises funny evenings this week) and upgrade anothert >PWS and XP1000...   Has anyone already tried  $ 	$ PRODUCT UNDO PATCHES/REMOTE/ALL ?  H I did specify the locicals PCSI$SYSDEVICE and PCSI$SPECIFIC (as in help) andM   	$ PRODUCT SHOW HISTORY/REMOTE 	$ PRODUCT SHOW PRODUCT/REMOTE) 	$ PRODUCT SHOW RECOVERY_DATA/REMOTE/FULL)  D all do work, but UNDO claims it can't find PCSI$UNDO_OBJECT_DATA.DAT* but they are both there (from the 2 ECOs).  ' Do you perhaps know, what I did wrong ?c   TIAa   -- d Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialisti E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  + Date: Sun, 22 Aug 2004 15:34:36 +0000 (UTC)t6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)C Subject: Re: [OpenVMS Alpha V7.3-2] Known Problems with last ECOs ?u1 Message-ID: <newscache$kptu2i$2fx1$1@news.sil.at>S  j In article <newscache$4nsu2i$hex1$1@news.sil.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:k >In article <newscache$8zbn2i$jfl1$1@news.sil.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:lI >>In the meantime I'll try to remove the ECOs (btw: does anyone know if alJ >>UNDO can be done while booted from the 7.3-2 CD - which I must boot fromJ >>an Infoserver and promises funny evenings this week) and upgrade another >>PWS and XP1000...t >  >Has anyone already tried  > % >	$ PRODUCT UNDO PATCHES/REMOTE/ALL ?a > I >I did specify the locicals PCSI$SYSDEVICE and PCSI$SPECIFIC (as in help)2 >and >4 >	$ PRODUCT SHOW HISTORY/REMOTE3 >	$ PRODUCT SHOW PRODUCT/REMOTEu* >	$ PRODUCT SHOW RECOVERY_DATA/REMOTE/FULL >uE >all do work, but UNDO claims it can't find PCSI$UNDO_OBJECT_DATA.DATo+ >but they are both there (from the 2 ECOs).t >g( >Do you perhaps know, what I did wrong ?  E Ok. Found the bug myself. I forgot the PCSI ECO. After installing it,tE I was able to UNDO both PATCHES - RMS and MOUNT96 - with /REMOTE/ALL.   C But unfortunately it didn't help. The same crashes are still there.>  E So, the culprit could well be the SYS V0400, but why did the PWS work B with it for 3 weeks before the install of RMS/MOUNT96 stopped it ?  7 OTOH, it could also be a problem of the PWS hardware...h   -- w Peter "EPLAN" LANGSTOEGERa% Network and OpenVMS system specialistn E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   End of INFO-VAX 2004.465 ************************