0 INFO-VAX	Sun, 14 Jan 2001	Volume 2001 : Issue 27      Contents:
 CHARON-VAX Re: CHARON-VAX Re: CHARON-VAX4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution Re: dec 3000 300 crashing  Re: dec 3000 300 crashing # Re: Ebay dead as a post - yet again # Re: Ebay dead as a post - yet again # Re: Ebay dead as a post - yet again G Re: Hobby VMS - was Re: eBay extended downtime (was Re: eBay SPAMARAMA) ! Re: NTP can be primary on OpenVMS % Re: powerchute for VMS AXP don't work % Re: powerchute for VMS AXP don't work  Re: RMS options  Re: RMS options $ Setup OPCOM console under DecWindows( Re: Setup OPCOM console under DecWindows( Re: Setup OPCOM console under DecWindows( Re: Setup OPCOM console under DecWindowsP Re: TTDRIVER multi-line editing (was Re: VMS wishlist [was Re: Identify que entrP Re: TTDRIVER multi-line editing (was Re: VMS wishlist [was Re:Identify que entryP Re: TTDRIVER multi-line editing (was Re: VMS wishlist [was Re:Identifyque entry * VAXSHAD07_071 ECO problem with Show Device. Re: VAXSHAD07_071 ECO problem with Show Device. Re: VAXSHAD07_071 ECO problem with Show Device  F ----------------------------------------------------------------------  % Date: Sun, 14 Jan 2001 01:28:16 +0100 % From: "IdrEASY" <IdrEASY@bigfoot.com>  Subject: CHARON-VAX ( Message-ID: <93qs6b$393d$1@as121.tel.hr>  " Was anybody try this VAX emulator?   I can't boot it.   ------------------------------  # Date: Sun, 14 Jan 2001 01:06:45 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net> Subject: Re: CHARON-VAX < Message-ID: <FY686.59681$1t.2926997@typhoon.ne.mediaone.net>  0 "IdrEASY" <IdrEASY@bigfoot.com> wrote in message" news:93qs6b$393d$1@as121.tel.hr...$ > Was anybody try this VAX emulator? >  > I can't boot it.  F OK, what version do you have? If it's the full-blown distribution on aI CDROM, it should install and work like a charm on your Windoze PC. If you K have the demo version that you downloaded from the website, you'll need the I OpenVMS Hobbyist distribution (the CHARON-VAX people cannot give away the  VMS OS).   ------------------------------  % Date: Sat, 13 Jan 2001 22:17:43 -0500  From: stan@stanq.com Subject: Re: CHARON-VAX . Message-ID: <3A60D407.16114.1DF6E72@localhost>  ' On 14 Jan 2001, at 1:28, IdrEASY wrote: $ > Was anybody try this VAX emulator? > I can't boot it.  C It took a little doing.  I bought a new system with lots of memory  F and Windows 2000 on it (256 MB RAM, 733 MHz Pentium III).  It's about # the same speed as my VAX 4000-60's.   A The version I used was the full evaluation version, to see if my  F client's product would work on it.  They had to make some tweaks, but 
 it does work.   / It's a really neat concept -- I wish them luck.      --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  % Date: Sat, 13 Jan 2001 14:55:10 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> = Subject: Re: Compaq: A simple, affordable clustering solution , Message-ID: <3A60B294.D0C4DDE1@videotron.ca>   "Main, Kerry" wrote:G > So, do you think a Customer is going to risk their career (and server G > consolidation projects are career make/break projects) on a brand new M > platform that requires an active directory design to be implemented company I > wide (which includes getting UNIX and security dept's agreement) before  > hand?   L It used to be: Nobody's ever been fired for buying IBM. And right now, it isL "nobidy's ever been fired for chosing Microsoft". In many ways you can argueK that you have no choice but to buy Microsoft because you require a platform N for which the applications your company needs are available, and you require aK platform for which it is not hard to find employees. You can hire anyone to P manage a wintel thingny, but you need a qualified person to manage a VMS system.  O To manage a wintel thingny, you only need to know about [START] [RUN] setup.exe   I > So the quote from Gartner in this review should be a good sign - right?   J One article doesn't make a trend. Granted, it is refreshing to see GartnerK allow such an article to be published. But For as long as Compaq refuses to J market VMS, the general public cannot have any confidence that VMS will beM targetted as a competitive server/workstation system. Right now, that DII-COE H thingy, according to Compaq's own Inform magazine is a commitment to the defence industry. I So, to me, that DII-COE is actually a negative because I see it as Compaq 9 further restricting VMS's niches to the defence industry.   N For as long as Compaq allows its own True64 group to make the claim that it isI the first clustering solution, then I have no confidence that Compaq will 3 allow VMS to go out in the real world and compete.    K That Inform Article should/could have been worded to focus much more on the I project to make VMS more "unix" compatible than some USA government paper N requirement to be able to sell to the defense industry (unless you'.re in that: industry, that requirement/commitment means zilch to you).   N > Granted, mistakes have been made in the past. Thats history. I lived it, andM > readers of this list have heard it hundreds of times about the past issues.   L The problem is exactly because we have lived through it, we are not so naiveN to beleive Compaq's vague promises. Actions speak louder than words. PromisingE to make Compaq into an enterprise company and then turning around and M advertise their wintel boxes only is a perfect example of why I don't beleive < what Compaq says just as I didn't beleive what Digital said.  N Everyone may want the Palmer years to be forgotten. But to do that Compaq mustM signifiy some real change from those years. And while I agree that there have I been some positive signs, there is still a lot of baggage left and Compaq K still seems to be doing many (but not all) of the bad things that date from  that previous era.    H > I guess the 40 ISV partners that showed up for one evening at our lastN > internal Ambassador meeting in Nov '00 were a figment of my imagination then > ???   L Woopty doo. 40 ISV. How many ISVs does Linux or NT have ? How many ISVs does
 Sun have ?  L All that tells me is that VMS isn't dead. It doesn't mean that it is healthyR nor that Compaq intends to push VMS as a competitive solution against NT and UNIX.  L > I guess the recent wins by major Customers (including some very well knownI > names in Canada as well as some big chip companies :-)) who have chosen J > Alpha OpenVMS as their strategic OS for their future are a figment of my > imagination ?   M Of course, you're not mentioning the National Film Board's current project to  migrate off of VMS.   M You can mention your individual wins, but can you mention all the losses that & continue and will continue to happen ?  G > I guess the recent VAX Customers choosing to migrate to OpenVMS are a L > figment of my imagination? (5 in Southern Ontario alone that I know of are > cooking right now)  M Woopty doo ! So 5 customers have realised that it may cost less to move their M legacy application to a newer box due to lower mainteance costs.  But I could J give you examples of people upgrading their machines even though they know= that inside of 2 years, they will be off of VMS and on to NT.   K > Is it a perfect world ? Nope. There is always room for improvement, and I - > suspect you will start to see some of this.   I We've were told this when Compaq got Digital. Then we were told this when G Compaq started to integrate Digital, then we were told this when Compaq N annoucned it would transform itself into an enterprise company etc etc. Sorry,A but Compaq has no credibility with its promises of fixing things.    ------------------------------  % Date: Sat, 13 Jan 2001 19:50:54 +0000 % From: Alan Greig <a.greig@virgin.net> = Subject: Re: Compaq: A simple, affordable clustering solution * Message-ID: <3A60B19E.824DDC21@virgin.net>  ! steven.reece@quintiles.com wrote:    > Kerry Main replied to Fabio :  > >>> F > >8 -  The net companies dont develop decnet routers anymore. What is
 > >decnet ???  > I > While I agree DECnet is an excellent protocol, the industry has adopted J > TCPIP as the standard internetworking protocol. Compaq OpenVMS is movingG > towards TCPIP as well. However, that does not mean DECnet will not be ) > supported for a long time ..it will be.  > <<<  > M > But Fabio - there's DECnet over TCP/IP if you make the move to DECnet-Plus. K > It solves your problems of not being able to run DECnet over your network M > because the PHNM (pointy haired network managers) want only TCP/IP on their ! > network and it works very well.  >   J And  I must be hallucinating the Cisco DECNET area routers on our WAN. HmmF think we still have DECNET routing to Brasil (if that's where Fabio isN located). Current CISCO routers are perfectly happy with DECNET Phase IV or V.N Not sure exactly what Fabio means when he says "net companies". Cisco is stillA the biggest net company and they'll happily sell you DECNET. See: C http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/decnet.htm    --
 Alan Greig   ------------------------------  % Date: Sat, 13 Jan 2001 15:29:45 -0500 ' From: "Bill Todd" <billtodd@foo.mv.com> = Subject: Re: Compaq: A simple, affordable clustering solution ( Message-ID: <93qdkp$lfb$1@pyrite.mv.net>  4 Main, Kerry <Kerry.Main@compaq.com> wrote in messageH news:910612C07BCAD1119AF40000F86AF0D805284C00@kaoexc3.kao.cpqcorp.net... > JF,  > / > Hey - what are you doing email on a Sat for ?  >  > :-)  > I > >>> But they consolidate of Compaq's premier product, that 32 processor > > wintel box made by someone else or with Proliant clusters.>> > G > So, do you think a Customer is going to risk their career (and server G > consolidation projects are career make/break projects) on a brand new E > platform that requires an active directory design to be implemented  company I > wide (which includes getting UNIX and security dept's agreement) before  > hand?   D This is yet one more assertion you keep making to the point of beingJ tiresome.  At least you don't capitalize it, as you're prone to with some.  B It's clearly FUD at least in the sense that a company can deploy a= 32-processor box and choose *not* to tie it into its existing E domain-structured NT company directory structure but just allow it to F communicate as an outsider and manage it separately.  And it would notF surprise me if it were possible to include it in an existing NT domainL structure as a non-directory-server node (i.e., like a Win2K workstation canK be) - at least I'm not ready to take your unsupported and distinctly biased I word that it isn't, given the unreliability of some of your past slams at  the competition.  L JF has adequately addressed the rest, so I won't.  If you and your ilk spentL anywhere nearly as much energy trying to change the way Compaq treats VMS asJ you do perpetually trying to convince us that better times are just around4 the corner, there might be more reason for optimism.   - bill   ------------------------------    Date: 13 Jan 2001 22:23:17 -0500/ From: jordan@lisa.gemair.com (Jordan Henderson) = Subject: Re: Compaq: A simple, affordable clustering solution * Message-ID: <93r635$glg$1@lisa.gemair.com>  O In article <93qdkp$lfb$1@pyrite.mv.net>, Bill Todd <billtodd@foo.mv.com> wrote:  >  > [snip] > M >JF has adequately addressed the rest, so I won't.  If you and your ilk spent M >anywhere nearly as much energy trying to change the way Compaq treats VMS as K >you do perpetually trying to convince us that better times are just around 5 >the corner, there might be more reason for optimism.  >   @ OpenVMS continues to outperform every industry "experts" opinion= both in terms of development and markets.  And, now, finally, @ Gartner is saying very good things about OpenVMS.  It's clear to= me that the tide has turned.  There is definitely reason for  	 optimism.   B A lot more could be done.  It's seems to me to be an open questionA as to whether any more could be done that would be cost effective C both in the short-term and the long-term, and make no mistake about = it, Compaq's shareholders and Wall Street are holding Compaq  , management responsible for short-term gains.  D The biggest problems with OpenVMS I see, day in and day out, is the E drain of IT personnel, like JF, who have been convinced that OpenVMS  B has no future.  These people may openly blame Compaq, but I think = that the various negative sentiments expressed by people like I yourself and others has not helped this problem at all.  I think Kerry's  J pep talks are important to help battle this.  You have no idea what Kerry I does inside Compaq to help change the way Compaq treats VMS, but if it's  > anything, it could only be complementary to what he does here.   >- bill  >  >  >    -Jordan Henderson  jordan@greenapple.com    ------------------------------  % Date: Sat, 13 Jan 2001 23:07:47 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> = Subject: Re: Compaq: A simple, affordable clustering solution , Message-ID: <3A6125FD.947910DE@videotron.ca>   Jordan Henderson wrote: B > OpenVMS continues to outperform every industry "experts" opinion, > both in terms of development and markets.   M That is not hard to do when VMS is eother declared dead, or barely mentioned. 8 So it is easy to outperform these very low expectations.  B > Gartner is saying very good things about OpenVMS.  It's clear to> > me that the tide has turned.  There is definitely reason for > optimism.   D I don't see that the tide has turned. I see perhaps that a window ofK opportunity has opened. But I do not have confidence that Compaq will seize G this opportunity to turn the tide.  For as long as VMS isn't pitched to A customers against UNIX and NT, then Compaq won't turn  the tide.    N Microsoft and Sun are very happy with VMS because they can count on Compaq not using that secret weapon.   > > it, Compaq's shareholders and Wall Street are holding Compaq. > management responsible for short-term gains.  M But they are clueless on the existence of VMS and potential of VMS. They just K see an invisible installed base that provides some revenus and don't bother L anyone. They are focused on Compaq's wintel sales because that is how Compaq allows itself to be measured.     E > The biggest problems with OpenVMS I see, day in and day out, is the F > drain of IT personnel, like JF, who have been convinced that OpenVMS > has no future.  J And why do you suspect people get the impression that VMS has no future ? L Funny that you mention the drain of IT personnel.  I see a drain of VMS jobsF because shops are migrating away from VMS or are just keeping existing! applications in maintenance mode.   K Of course, it doesn't help when a local sales office talks about VMS in the H past during presentations such as the launch of Wildfire and pushes onlyN True64. This is backed by the Inform magazine spinning its True64 as the first2 OS with all the fancy clustering features etc etc.    3 > These people may openly blame Compaq, but I think ? > that the various negative sentiments expressed by people like 9 > yourself and others has not helped this problem at all.   L I was patient for some 8 years and stayed loyal to VMS even as work dried upH and Palmer was calling for folks to migrate away from VMS. I should have7 listened because every one else seems to have listened.        > I think Kerry's K > pep talks are important to help battle this.  You have no idea what Kerry J > does inside Compaq to help change the way Compaq treats VMS, but if it's@ > anything, it could only be complementary to what he does here.    J Kerry is in a very privileged position because he *might* be Compaq's soleK remaining VMS expert in Canada (many were laid off during the palmer years) H and he gets to see the few remaining VMS customers all across Canada andN abroad. I envy him and wish Compaq would hire more folks in his position.  ButM when you send an email to the director of professional services of your localdK office offering your VMS services and don't even get a reply, it is easy ton8 lose any hope that VMS will see a comeback where I live.   ------------------------------  % Date: Sat, 13 Jan 2001 22:11:10 -0600f7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> = Subject: Re: Compaq: A simple, affordable clustering solution - Message-ID: <3A6126DE.604DDC97@earthlink.net>y   Jordan Henderson wrote:  > Q > In article <93qdkp$lfb$1@pyrite.mv.net>, Bill Todd <billtodd@foo.mv.com> wrote:  > >i
 > > [snip] > > O > >JF has adequately addressed the rest, so I won't.  If you and your ilk spenteO > >anywhere nearly as much energy trying to change the way Compaq treats VMS as M > >you do perpetually trying to convince us that better times are just arounde7 > >the corner, there might be more reason for optimism.n > >t > B > OpenVMS continues to outperform every industry "experts" opinion? > both in terms of development and markets.  And, now, finally,eB > Gartner is saying very good things about OpenVMS.  It's clear to> > me that the tide has turned.  There is definitely reason for > optimism.   G Rich Marcello informed me that action was being taken to get Gartner to G stop black-balling OpenVMS, even before I suggested to him that someone C should do exactly that. The effort appears to have been successful.o  cD > A lot more could be done.  It's seems to me to be an open questionC > as to whether any more could be done that would be cost effective-E > both in the short-term and the long-term, and make no mistake aboutr> > it, Compaq's shareholders and Wall Street are holding Compaq. > management responsible for short-term gains.  H If Wall Street and the investors knew what the all-term gains are in theD OpenVMS profit department, they'd be all over Compaq "like hair on aB gorilla" about why OpenVMS is not advertised or actively marketed.  lE > The biggest problems with OpenVMS I see, day in and day out, is themF > drain of IT personnel, like JF, who have been convinced that OpenVMSC > has no future.  These people may openly blame Compaq, but I thinke? > that the various negative sentiments expressed by people like-J > yourself and others has not helped this problem at all.  I think Kerry'sK > pep talks are important to help battle this.  You have no idea what KerrysJ > does inside Compaq to help change the way Compaq treats VMS, but if it's@ > anything, it could only be complementary to what he does here.  E Whole-hearted agreement. OpenVMS Advocacy. Dave Gudewicz of CARTS Lug3D fame is trying to carry that banner. I recommend we *ALL* get behind  him, whatever each of us can do!  H The positive Gartner output finally gives us some live ammunition to useC in presentations to prospective customers! Now if Compaq themselvestA would come on board with *ANY*thing that would help us along even.
 further...   -- Q David J. Dachtera  dba DJE Systems1 http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Sun, 14 Jan 2001 08:13:20 +1300 9 From: "Antony Wardle" <antony.wardle@noospammm.met.co.nz> " Subject: Re: dec 3000 300 crashing0 Message-ID: <mI186.693$FC1.28273@ozemail.com.au>   You are probably right.s  ; Just turned it back on again to go through your suggestions  and beside mem it has'   ?? 800 0020 64mb   a test mem celli has T-STS-MEM - OK     Test mem  4 T-STS-MEM - LLSC Test : Addr 00200000 FWD Wr 0000000* MCHK ID: 14 Logout Frame address: 00108060: exc_addr: 000ED784  bui_stat: 00000050  bui_addr: 001081A0< fill_addr:  00054EF0    hi_synd: 00000000  lo_synd : 0000000> mm_csr:  00005931     dc_stat: 00000007          va:  001081E8  = ? T-ERR-MEM   - ldl_l bcache miss no victim at Addr: 00200044n& T-STS-MEM - Uncorredted Error cont = 1: ? T-ERR-MEM _ FAILED status = 20 test Init addr - 00200044 ?? 800      MEM 0x0020     PAL code is V5.56 	 64 mb MEMl  > So if the memory is faulty, can I take some from out of 1000a? or a VLC, or a 3100, or a PC?G   Antony      9 "Paul Repacholi" <prep@prep.synonet.com> wrote in messagef* news:87g0ina01q.fsf@k9.prep.synonet.com...0 > Paul Repacholi <prep@prep.synonet.com> writes: >sE > > Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>n writes:d > >oK > > > A double machine check usually indicates severe hardware trouble - it  meanstH > > > that the processor got a machine check (something's wrong with the	 hardware-M2 > > > indication) while it was handling the first. > >mK > > If you can get that far, it is generally memory. The POST is real smarteE >                                                               ^ NOTo > > at finding memory errors.o >t > I must get more sleep... >uE > Do a TEST MEM CELL, and I'll bet it finds an error at a high memoryM
 > address. >oF > The DBL ERR is a memory error while trying to handle the MC from the > original error.u >y > --> > Paul Repacholi                               1 Crescent Rd.,9 > +61 (08) 9257-1001                           Kalamunda.hB >                                              West Australia 60760 > Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Sat, 13 Jan 2001 15:48:57 -0500n2 From: rdeininger@mindspring.com (Robert Deininger)" Subject: Re: dec 3000 300 crashingL Message-ID: <rdeininger-1301011548570001@user-2ive7eo.dialup.mindspring.com>  k In article <mI186.693$FC1.28273@ozemail.com.au>, "Antony Wardle" <antony.wardle@noospammm.met.co.nz> wrote:v    t= > Just turned it back on again to go through your suggestionso > and beside mem it hasa >  > ?? 800 0020 64mb >  > a test mem cella > has T-STS-MEM - OK  4 Not much point trying to boot an OS in this state...    
 > Test mem > 6 > T-STS-MEM - LLSC Test : Addr 00200000 FWD Wr 0000000, > MCHK ID: 14 Logout Frame address: 00108060< > exc_addr: 000ED784  bui_stat: 00000050  bui_addr: 001081A0> > fill_addr:  00054EF0    hi_synd: 00000000  lo_synd : 0000000@ > mm_csr:  00005931     dc_stat: 00000007          va:  001081E8 > ? > ? T-ERR-MEM   - ldl_l bcache miss no victim at Addr: 00200044u( > T-STS-MEM - Uncorredted Error cont = 1< > ? T-ERR-MEM _ FAILED status = 20 test Init addr - 00200044 > ?? 800      MEM 0x0020  | Alas, I don't have service docs so I can't interpret all of this.  The MCHK ID in the middle of the memory test looks weird.  M Maybe the problem is not the memory, but rather some external memory circuit.p  " From the hardware reference guide: Memory subtests areo-   test mem cell   detecs data stuck at faults 3   t mem addr      detects addresses stuck at faultst/   t mem llsc      load-locked/store conditionali)   t mem bctp      bcache tag parity logic    t mem ecc       ECC logicl+   t mem init      inits all memory to zerost"   t mem all       all of the above   t mem ?         help   > ?? 800 0020 64mb  $ This indicates a memory error (duh!)+ The 800 is the FRU code, in the format 8xy.!    x = bank 0 to 7E    y = 0 for SIMM 0, 1 for SIMM 1, 8 for both SIMMS, F for can't tell j (A "bank" of memory is 1 side of a pair of SIMMs.  The other side of both SIMMs forms another bank. IIRC.)  L So 800 is supposed to mean SIMM 0 is sick.  Swap the SIMMs, the error should change to 801.  M The "action" listed for this error is "Be sure all SIMMs are installed in the < correct postions and are secure.  Rerun the test to verify."     > PAL code is V5.56h > 64 mb MEMl  * The firmware that came with VMS 7.1-2 was:: Console version: V7.0                PALcode version: 5.56  	 From VMS:s f$getsyi("console_version")y f$getsyi("palcode_version")h  9 But I would NOT try to upgrade firmware with sick memory!-  @ > So if the memory is faulty, can I take some from out of 1000a? > or a VLC, or a 3100, or a PC?n >  > Antony  g Make sure you have the memory configured right.  And it can't hurt to remove and re-seat all the SIMMS.v  z As far as I know, only the DEC 3000 300 family used this memory.  It isn't too hard to find used if you aren't in a hurry.   There were two DEC memory kits: ( MS16-BA   16 MB kit (2 SIMMs)     $1,200( MS16-DA   64 MB kit (2 SIMMs)     $8,000  1 (The prices are from the 1994 DECdirect catalog.)q   The catalog description is:C3 Industry-standard, double-sided 8 MB or 32 MB SIMM.n 4 Mbit/16 Mbit DRAM technology Access time of 70 ns parity memory technology    Q Clearpoint and Camminton also made compatible kits, and probably other vendors.  mm We just bought the last set from clearpoint (used) at work, but Jeff Sullivan said he thinks he can get more.o   The systems can hold up to 4 kits.  Each set of 2 SIMMs goes in 2 adjacent slots.  You have to load the slots starting with the one farthest from the drive bay, and don't skip any slots.  If you mix 16 and 64 MB kits, you have to put the big ones in first.   -- h Robert Deininger rdeininger@mindspring.com    ------------------------------  # Date: Sat, 13 Jan 2001 23:59:38 GMT 3 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk>t, Subject: Re: Ebay dead as a post - yet again/ Message-ID: <3A60EB3C.7E96C652@cableinet.co.uk>-   "Terry C. Shannon" wrote:e > / > "Paul Sture" <paul@sture.ch> wrote in message ' > news:VA.00000225.5eb1105d@sture.ch...aB > > In article <3A59E8F5.FAFA9B75@bbc.co.uk>, Tim Llewellyn wrote: > <snip>S > > > > And coincidentally I came across another example yesterday. The UK National1V > > > > Westminster bank had committed itself to NT big time about 3-4 years ago and IU > > > > did an AltaVista search on +"National Westminster" +NT. Quite a lot of links,iP > > > > but so many resulting in a 404 error that I gave up. Whilst I am used toJ > > > > seeing a few broken links here and there, I've never seen so many!L > > >  They really should be forced to publicly state why they "gave up" and > howeQ > > > much the failed NT implementation cost. After all, as VMS people, it is our S > > > livelihoods they have been "attacking" with their tin-pot "IT is cheap if its  > > > Micro$" attitude.a > >i  @ Actually, on second thought, maybe they just pulled all external
 references to their IT strategy.   , Gotta stop posting during PM cafeine frenzy.  0 > > I agree, but doubt that it will ever happen. > N > I doubt it, too. It would not be politically astute for a BANK to admit thatI > it relied on a flawed and squatulent solution to protect its customers't' > dollars, francs, Euros, and drachmas.m  0 Agreed, isn't "flawed and squatulent" a bit OTT?   ------------------------------  # Date: Sun, 14 Jan 2001 01:04:56 GMTr4 From: "Terry C. Shannon" <terryshannon@mediaone.net>, Subject: Re: Ebay dead as a post - yet again< Message-ID: <YW686.59674$1t.2926658@typhoon.ne.mediaone.net>  @ "Tim Llewellyn" <tim.llewellyn@cableinet.co.uk> wrote in message) news:3A60EB3C.7E96C652@cableinet.co.uk...e >a >  > "Terry C. Shannon" wrote:g > > 1 > > "Paul Sture" <paul@sture.ch> wrote in message ) > > news:VA.00000225.5eb1105d@sture.ch...rD > > > In article <3A59E8F5.FAFA9B75@bbc.co.uk>, Tim Llewellyn wrote:
 > > <snip>L > > > > > And coincidentally I came across another example yesterday. The UK NationalH > > > > > Westminster bank had committed itself to NT big time about 3-4 years ago and I-I > > > > > did an AltaVista search on +"National Westminster" +NT. Quite at
 lot of links,iJ > > > > > but so many resulting in a 404 error that I gave up. Whilst I am used tosL > > > > > seeing a few broken links here and there, I've never seen so many!J > > > >  They really should be forced to publicly state why they "gave up" andu > > howtL > > > > much the failed NT implementation cost. After all, as VMS people, it is ourH > > > > livelihoods they have been "attacking" with their tin-pot "IT is cheap if its > > > > Micro$" attitude.d > > >f >lB > Actually, on second thought, maybe they just pulled all external > references > to their IT strategy.  >d. > Gotta stop posting during PM cafeine frenzy. >u2 > > > I agree, but doubt that it will ever happen. > >tK > > I doubt it, too. It would not be politically astute for a BANK to admith thatK > > it relied on a flawed and squatulent solution to protect its customers'n) > > dollars, francs, Euros, and drachmas.e >r2 > Agreed, isn't "flawed and squatulent" a bit OTT?  L It all depends on whether it's YOUR dollars, francs, Euros, or drachmas thatI are at risk. And correct me if I'm wrong, but isn't Micro$oft running adsmK featuring the BSOD... ads telling customers that they'd better upgrade fromp6 WinNT to Win2K 'cuz it's 13 times more reliable?   ;-}   ------------------------------  % Date: Sat, 13 Jan 2001 22:02:35 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>o, Subject: Re: Ebay dead as a post - yet again- Message-ID: <3A6124DB.17A1BD02@earthlink.net>l   "Terry C. Shannon" wrote:. > B > "Tim Llewellyn" <tim.llewellyn@cableinet.co.uk> wrote in message+ > news:3A60EB3C.7E96C652@cableinet.co.uk..., > >a > >1 > > "Terry C. Shannon" wrote:i > > >e3 > > > "Paul Sture" <paul@sture.ch> wrote in messagel+ > > > news:VA.00000225.5eb1105d@sture.ch...DF > > > > In article <3A59E8F5.FAFA9B75@bbc.co.uk>, Tim Llewellyn wrote: > > > <snip>N > > > > > > And coincidentally I came across another example yesterday. The UK
 > NationalJ > > > > > > Westminster bank had committed itself to NT big time about 3-4 > years ago and I K > > > > > > did an AltaVista search on +"National Westminster" +NT. Quite ah > lot of links,SL > > > > > > but so many resulting in a 404 error that I gave up. Whilst I am	 > used toiN > > > > > > seeing a few broken links here and there, I've never seen so many!L > > > > >  They really should be forced to publicly state why they "gave up" > andr	 > > > howuN > > > > > much the failed NT implementation cost. After all, as VMS people, it > is ourJ > > > > > livelihoods they have been "attacking" with their tin-pot "IT is > cheap if its > > > > > Micro$" attitude.t > > > >e > > D > > Actually, on second thought, maybe they just pulled all external > > references > > to their IT strategy.. > >u0 > > Gotta stop posting during PM cafeine frenzy. > >a4 > > > > I agree, but doubt that it will ever happen. > > >oM > > > I doubt it, too. It would not be politically astute for a BANK to admite > thatM > > > it relied on a flawed and squatulent solution to protect its customers'r+ > > > dollars, francs, Euros, and drachmas., > >h4 > > Agreed, isn't "flawed and squatulent" a bit OTT? > N > It all depends on whether it's YOUR dollars, francs, Euros, or drachmas thatK > are at risk. And correct me if I'm wrong, but isn't Micro$oft running adsoM > featuring the BSOD... ads telling customers that they'd better upgrade froma8 > WinNT to Win2K 'cuz it's 13 times more reliable?   ;-}   Winking Smiley indeed!  2 I'm sure everyone here knows what 13 * 0 equals...   -- t David J. Dachteran dba DJE Systemsn http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.s   ------------------------------  % Date: Sat, 13 Jan 2001 12:06:05 -0800f+ From: "Wayne Holland" <wholland@tscnet.com> P Subject: Re: Hobby VMS - was Re: eBay extended downtime (was Re: eBay SPAMARAMA)O Message-ID: <B8A66D3F881E6F98.599D11C0A37336BE.21BA2D7D74DAD425@lp.airnews.net>   6 "Jerry Leslie" <leslie@clio.rice.edu> wrote in message! news:93pqre$irs$1@joe.rice.edu...d, > Wayne Holland (wholland@tscnet.com) wrote: > :eH > : Thank you!  Can you give me a web site that has the intel emulation? > :n >  > http://www.charon-vax.com/ >aB > I also emailed you some of the comp.os.vms articles about Charon >V6 > --Jerry Leslie     (my opinions are strictly my own)   Thanks, I'll look into these!l   ------------------------------    Date: 13 Jan 2001 22:50:37 -05002 From: malmberg@eisner.decus.org (John E. Malmberg)* Subject: Re: NTP can be primary on OpenVMS+ Message-ID: <7p88uWt8$WBi@eisner.decus.org>   0 In article <87k87za0dm.fsf@k9.prep.synonet.com>,2 Paul Repacholi <prep@prep.synonet.company> writes: >> ..  >> :See N http://www.openvms.compaq.com:8000/72final/6526/6526profile_015.html#ntp_intro >> :8 >> :NTP can be run as a primary with TCPIP 5.0 or later. >nH > Primary, as in serve a primary time reference. IE GPS or Atomic clock./ > Normally this will be a stratum 1 NTP sustem.   C I was refering to primary as in the sense that all other devices on'. the local network would get it's time from it.  ? An atomic clock option for OpenVMS is still not available after = the Compaq merger.  I am unaware of any other computer system 9 platform that offers an atomic clock as an option either.   D > So no, it can only run as a peer or client. There is NO way to getD > it to serve a primary reference, except by tranfering from DTSS. ID > can not use the PPS output from my GPS, nor use the serial outputs > to provide a time source.e  A The DTSS time server, a part of DECNET-Plus, has documentation onr? using radio receivers and other types of links for it to obtain  a master reference time.  B The manual is titled "DECnet-Plus DECdts Programming" and while it= does not appear to be on the web, I did find it in bookreadere? format on some of the older Consolidated Documentation CD-ROMs. ? The information to get DTSS to use a third party time source iso documented there.m  B If you chose to install them when you installed DECNet-Plus, thereF will be sample programs for use with sys$common:[syshlp.examples.dtss]A that may be of use.  If one of them does not match the PPS outputa@ from your GPS, then it will show you what it takes to write one.  > But DTSS is not needed to synchonize VMS time with an externalC time provider.  If you make sure that the DTSS clerk is not runningMD any program that knows how to connect to that time source and decode< it's time, if it has privilege can set the OpenVMS time with) the documented SYS$SETIME system service.n  C If the protocol to the time providing device is simple enough, then  DCL can be used.  G So yes, OpenVMS can be a primary NTP provider to a network, and DTSS iso
 not required.a  G Some programming may be required if the external time source is not onegD that is directly supported by DTSS, or that vendor does not supply a6 program that runs on OpenVMS directly to set the time.  ? > So, I am going to have to conect the GPS to the Linux box. Ati> > least that is a Prioris. But no way I can use a DRV, or plug@ > the PPS pulse into the CPU console. BTW, if the support was inA > SRM, that would be ideal for this. If you don't mind connectingv > direct to the chip.p  C I have no idea what a DRV is, or why you would be able to connect aaC GPS (Global Positioning Service receiver) to a PC running LINUX and G not to a OpenVMS system.  If it has a serial interface at standard baudsE rates, then an OpenVMS program should be able to communicate with it.l  C I do not personally have a GPS device, so I have not looked at whateF it would take to get a time referece from it.  I suspect that if thereC is a LINUX program to do so, and it's source is provided as per theoE usual custom, then it should be possible to obtain the information toa implement it on OpenVMS.   >AI > I will say, that the bounded time error in DTSS is IMO a near essential0 > part of any time protocol.  2 Yes, trust your time provider, but no too much :-)   -Johnu wb8tyw@qsl.net Personal opinion only.   ------------------------------  # Date: Sat, 13 Jan 2001 19:49:33 GMTm$ From: Gary Morin <gmm35@my-deja.com>. Subject: Re: powerchute for VMS AXP don't work) Message-ID: <93qbgb$v16$1@nnrp1.deja.com>e  D You might look at the APC Linux code.  At one time I began to try toG hack a VMS version out of that but gave up because it got just to busy.0  E I collected a number of different documents to this end including thedE pinout which was posted on DECUServe back in 98.  I still have all ofr$ that stuff somewhere if you want it.  	   -- Gary      Sent via Deja.com? http://www.deja.com/   ------------------------------  # Date: Sat, 13 Jan 2001 23:10:55 GMTa! From: larryrblackwell@my-deja.comC. Subject: Re: powerchute for VMS AXP don't work) Message-ID: <93qn9r$859$1@nnrp1.deja.com>e  5 Yes I would appreciate the pinouts if you can find itl Thanks ><     Sent via Deja.comw http://www.deja.com/   ------------------------------  % Date: Sat, 13 Jan 2001 15:34:40 -0500o' From: "Bill Todd" <billtodd@foo.mv.com>d Subject: Re: RMS options( Message-ID: <93qdtt$ln6$1@pyrite.mv.net>  L Though I have a vague and quite possibly incorrect recollection that you canL use it only for GETs, not PUTs (if true, that's likely because RMS-32 valuesJ the integrity of its internal buffers and has the means, unlike RMS-11, to protect them).  J IIRC, you can find the facilities described somewhere in the down-loadable .pdf manuals for RMS.    - bill  J Jim Johnson <Jim.Johnson@software-exploration.nospam.com> wrote in message( news:3a60760f.613432@news.demon.co.uk...B > Yes, it does.  It's still in the same place, and still acts as aG > 'hint' allowing RMS to return a pointer to its buffer rather than the 	 > user's.  >  > Jim. >h > G > On 13 Jan 2001 13:09:30 +0800, Paul Repacholi <prep@prep.synonet.com>C > wrote: >- > > ! > >This is possible one for Hein.- > >-@ > >On RSX, and maybe early VMS, you could use RMS in 'move mode'? > >or 'locate mode'. Locate mode passed back a pointer into the0@ > >RMS buffer for the record you wanted. It did not copy it into7 > >a user buffer. Yes, plenty of chance to FU big time!@ > >iB > >Does RMS still have locate mode? Is it Doced, and if so, where? > >  > >--u? > >Paul Repacholi                               1 Crescent Rd., : > >+61 (08) 9257-1001                           Kalamunda.C > >                                             West Australia 6076n1 > >Raw, Cooked or Well-done, it's all half baked.L >T
 > Jim Johnson0 > Software Exploration, Ltd.) > Software Navigation and Discovery Toolsd   ------------------------------  % Date: Sat, 13 Jan 2001 19:14:11 -060007 From: "David J. Dachtera" <djesys.nospam@earthlink.net>5 Subject: Re: RMS options- Message-ID: <3A60FD63.F1A18C9D@earthlink.net>d   Bill Todd wrote: > N > Though I have a vague and quite possibly incorrect recollection that you canN > use it only for GETs, not PUTs (if true, that's likely because RMS-32 valuesL > the integrity of its internal buffers and has the means, unlike RMS-11, to > protect them). > L > IIRC, you can find the facilities described somewhere in the down-loadable > .pdf manuals for RMS.   , There are some older doc.'s in .PDF form at:  / http://www.djesys.com/vms/freevms/document.htmlu  G Don't know if there's anything there that will help, but may be worth a  look.l   -- t David J. Dachtera  dba DJE Systemsc http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/l  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Sat, 13 Jan 2001 23:03:37 +0100a: From: "Michael Holmes" <NOSPAM.raider@NOSPAM.mindless.com>- Subject: Setup OPCOM console under DecWindows , Message-ID: <93qjfn01ps6@enews3.newsguy.com>  % I'm running VMS 7.2 on Dec 3000-300L.c? I recently got a monitor for it and have it boot to DecWindows.   K I don't have any manuals.  I was wondering what logical or  xxx$startup.comsI file I need to change to have the opcom console come up on the DecWindowss	 terminal._  8 thanks for the help, first time messing with Decwindows.G If you know of any good URLs for DecWindows please share them as well..y   Michaele   ------------------------------  % Date: Sat, 13 Jan 2001 21:52:54 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> 1 Subject: Re: Setup OPCOM console under DecWindowsM, Message-ID: <3A611475.7B18022C@videotron.ca>   Michael Holmes wrote:.M > I don't have any manuals.  I was wondering what logical or  xxx$startup.comCK > file I need to change to have the opcom console come up on the DecWindows  > terminal.   I SHIFT-F2 (print screen button, top left of keyboard) will shift the wholee/ screen down to let you see some OPCOM messages.   M However, once decwindows takes control of the screen, there is no real way tomM display the messages onn that monitor. (that I know of). Perhaps you can justrK open a decterm or DCL window and use the REPLY/ENABLE command to have OPCOMa" messages displayed in that window.   ------------------------------    Date: 13 Jan 2001 23:10:13 -05002 From: malmberg@eisner.decus.org (John E. Malmberg)1 Subject: Re: Setup OPCOM console under DecWindowsh+ Message-ID: <WXgPyo3cS$4D@eisner.decus.org>u  , In article <93qjfn01ps6@enews3.newsguy.com>,< "Michael Holmes" <NOSPAM.raider@NOSPAM.mindless.com> writes:' > I'm running VMS 7.2 on Dec 3000-300L. A > I recently got a monitor for it and have it boot to DecWindows.e >lM > I don't have any manuals.  I was wondering what logical or  xxx$startup.com K > file I need to change to have the opcom console come up on the DecWindowsu > terminal.l >u: > thanks for the help, first time messing with Decwindows.I > If you know of any good URLs for DecWindows please share them as well..   0 OpenVMS home page 	http://www.openvms.compaq.com" On that page is a link to the FAQ.  7 Online Documentation	http://www.openvms.compaq.com:8000   K The DECWindows Motif manual and possibly the sys$help:*motif*.release_notesa file can help you.  H Also see the comments in SYS$MANAGER:SYLOGICALS.TEMPLATE for controlling the startup of OPCOM.e   -John  wb8tyw@qsl.network Personal Opinion Only.   ------------------------------    Date: 13 Jan 2001 23:20:53 -05002 From: malmberg@eisner.decus.org (John E. Malmberg)1 Subject: Re: Setup OPCOM console under DecWindows + Message-ID: <miA605gAmP1l@eisner.decus.org>y  , In article <3A611475.7B18022C@videotron.ca>,/ JF Mezei <jfmezei.spamnot@videotron.ca> writes:  > Michael Holmes wrote:h= >> I don't have any manuals.  I was wondering what logical or B >> xxx$startup.com file I need to change to have the opcom console& >> come up on the DecWindows terminal. > K > SHIFT-F2 (print screen button, top left of keyboard) will shift the whole 1 > screen down to let you see some OPCOM messages.o >oO > However, once decwindows takes control of the screen, there is no real way to'O > display the messages onn that monitor. (that I know of). Perhaps you can justuM > open a decterm or DCL window and use the REPLY/ENABLE command to have OPCOMe$ > messages displayed in that window.  D It is a feature that showed up in the DecWindows-MOTIF product a fewH revisions back.  By default it is off, but when it is enabled, it places1 an operator message display window on the screen.T  0 It will be displayed even if noone is logged in.   -Johnc wb8tyw@qsl.network Personal Opinion Only.   ------------------------------  # Date: Sat, 13 Jan 2001 22:12:09 GMT ( From: Terry Kennedy <terry@gate.tmk.com>Y Subject: Re: TTDRIVER multi-line editing (was Re: VMS wishlist [was Re: Identify que entri' Message-ID: <G74GC9.JHM@spcuna.spc.edu>   4 Hoff Hoffman <hoffman@xdelta.zko.dec.nospam> writes:H >   Without extensive work in the terminal driver, this is not feasible.K >   The terminal driver keeps one line, depending on DCL or the applicationt. >   to keep track of additional command lines.  K   You're thinking of something else, I think. I believe the original posteriL is talking about single logical command lines which have wrapped on the ter-M minal. If the length of the prompt + typed command characters is greater thanhM the terminal width, VMS won't let you edit the un-wrapped portion of the linetJ without deleting the wrapped portion of the line (or changing the terminal
 width first).   M   Many Unix shells support this feature, with additional complications (sincefK they support a variety of terminals, some of which do auto-newline and someo of which don't).  4         Terry Kennedy             http://www.tmk.com5         terry@tmk.com             Jersey City, NJ USAp   ------------------------------  % Date: Sat, 13 Jan 2001 22:15:05 -0500g From: stan@stanq.comY Subject: Re: TTDRIVER multi-line editing (was Re: VMS wishlist [was Re:Identify que entryd. Message-ID: <3A60D369.23683.1DD04D1@localhost>  . On 13 Jan 2001, at 22:12, Terry Kennedy wrote:M >   You're thinking of something else, I think. I believe the original posterWN > is talking about single logical command lines which have wrapped on the ter-O > minal. If the length of the prompt + typed command characters is greater thanmO > the terminal width, VMS won't let you edit the un-wrapped portion of the line2L > without deleting the wrapped portion of the line (or changing the terminal > width first).n  C Yup, that was my point.  I did get a suggestion to set my terminal cF width to 132, but that's only somewhat helpful.  And it's too late to 6 do that *after* you've entered >80 characters of text.     --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671r1 8572 North Spring Ct. NW, Pickerington, OH  43147I= Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  % Date: Sat, 13 Jan 2001 23:42:16 -0500e* From: Chuck Chopp <ChuckChopp@rtfmcsi.com>Y Subject: Re: TTDRIVER multi-line editing (was Re: VMS wishlist [was Re:Identifyque entry  + Message-ID: <3A612E28.25FF73BB@rtfmcsi.com>s   stan@stanq.com wrote:   0 > On 13 Jan 2001, at 22:12, Terry Kennedy wrote:O > >   You're thinking of something else, I think. I believe the original posterhP > > is talking about single logical command lines which have wrapped on the ter-Q > > minal. If the length of the prompt + typed command characters is greater than"Q > > the terminal width, VMS won't let you edit the un-wrapped portion of the line N > > without deleting the wrapped portion of the line (or changing the terminal > > width first).s > D > Yup, that was my point.  I did get a suggestion to set my terminalG > width to 132, but that's only somewhat helpful.  And it's too late to 8 > do that *after* you've entered >80 characters of text. >t > --Stan >t > ----------I > Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671o3 > 8572 North Spring Ct. NW, Pickerington, OH  43147 ? > Preferred address:  stan@stanq.com       http://www.stanq.com   S Well, technically speaking, if you've entered > 80 characters but < 131 characters,rR you can put a hyphen at the end of the line, hit return and then CTRL_Y.  When youP get a command prompt back, type in SET TERM/WIDTH=132, hit return again and thenL hit the UP ARROW key twice.  This will recall the line that you attempted toS continue with the hyphen character but then aborted with the CTRL_Y keystroke.  YounG can then edit the entire line if it was up to 131 characters in length.e  Q I know, this is small consolation and does note remedy the entire problem, but ito helps a little bit...i     -- Chuck Choppe  8 ChuckChopp@rtfmcsi.com            http://www.rtfmcsi.com0                                   ICQ # 22321532@ RTFM Consulting Services Inc.     864 801 2795 voice & voicemail2 103 Autumn Hill Road              864 801 2774 fax4 Greer, SC  29651                  800 774 0718 pager7                                   8007740718@skytel.come   ------------------------------  % Date: Sat, 13 Jan 2001 14:07:54 -05001' From: "Dale A. Marcy" <dqm@y12.doe.gov>t3 Subject: VAXSHAD07_071 ECO problem with Show Devicem+ Message-ID: <3A60A78A.D48F6D54@y12.doe.gov>    Group,  L      I have tried to apply the VAXSHAD07_071 patch to a VAX 4000-500A systemE running VMS V7.1.  The application of the ECO runs without error from/L VMSINSTAL, but after rebooting, Pathworks will not start correctly (it hangsM up) and the Show Device and Show Memory commands produce stack dumps as showno below:    ? $ show dev d                                                   0P                                                                                 "     Allocation class              - 0                                            0#     Host name      ""    Host type,p, avail,                                      M %SYSTEM-F-ACCVIO, access violation, reason mask=6F, virtual address=03C00000,. PC
 =00000000,E PSL=00000000                                                         rP                                                                                 *   Improperly handled condition, image exit% forced.                              hP                                                                                 +         Signal arguments              Stacki$ contents                            P                                                                                 (         Number = 00000003               ' 00000000                               o(         Name   = 0000000C               ' 00000000                               o(                  0001306F               ' 7FDEB148                               o(                  03C00000               ' 20202020                                (                                         ' 6F737341                               .(                                         ' 74616963                               p(                                         ' 71206465                               s(                                         ' 65756575                               t(                                         ' 2020203A                               e(                                         ' 202C6520                               lP                                                                                          Register? dump                                                           dP                                                                                 9         R0 = 0000000C  R1 = 905B7021  R2 = 00000001  R3 =t 0000000C              9         R4 = 00000001  R5 = 00010C90  R6 = 00020C88  R7 =e 00010C04              9         R8 = 00020C8E  R9 = 0000BA29  R10= 000460F8  R11=o 000460FC              9         AP = 7FDEB108  FP = 7FDEB0C8  SP = 7FDEB13C  PC =n 0001306F                       PSL=C 03C00000                                                           u       ? $ show mem                                                     bP                                                                                 E   Bad Pages                        Total     Dynamic  I/O Errors     u
 Static    J                                    71724           0       71788           0    oP                                                                                 C Granularity Hint Regions (pages):  Total        Free      In Use   d Released    E   Execlet code region                320       71788      655360     v
 485315    M %SYSTEM-F-ACCVIO, access violation, reason mask=6F, virtual address=03C00000,r PC
 =00000000,E PSL=00000000                                                         tP                                                                                 *   Improperly handled condition, image exit% forced.                              oP                                                                                 +         Signal arguments              Stack $ contents                            P                                                                                 (         Number = 00000003               ' 00000000                               b(         Name   = 0000000C               ' 00000000                               ,(                  0001306F               ' 7FDEB820                               r(                  03C00000               ' 20202020                               h(                                         ' 65657246                               t(                                         ' 79624B20                               r(                                         ' 20736574                                (                                         ' 20202020                                (                                         ' 20202020                               e(                                         ' 20202020                               pP                                                                                          Register? dump                                                           .P                                                                                 9         R0 = 0000000C  R1 = 00000002  R2 = 00000001  R3 =m 0000000C              9         R4 = 00000001  R5 = 00010C90  R6 = 00020C88  R7 =h 00010C04              9         R8 = 7FFECA48  R9 = 7FFECC50  R10= 7FFED7D4  R11=  7FFE2BDC              9         AP = 7FDEB7E0  FP = 7FDEB7A0  SP = 7FDEB814  PC =i 0001306F                       PSL=C 03C00000                                                           e  F      Has anybody else had a problem with this ECO?  In case it makes aI difference, this system is clustered with an Alphaserver 4100 running VMSeH V7.1.  I have restored the system disk to a point prior to the ECO beingB applied and will be off until Tuesday, so if I need to supply moreN information, it will be after then.  Unfortunately, this system is not covered0 by phone support like many of our other systems.   Thanks,t  
 Dale A. Marcy . Science Applications International Corporation   ------------------------------  % Date: Sat, 13 Jan 2001 16:07:53 -0500 2 From: rdeininger@mindspring.com (Robert Deininger)7 Subject: Re: VAXSHAD07_071 ECO problem with Show DeviceoL Message-ID: <rdeininger-1301011607530001@user-2ive7eo.dialup.mindspring.com>  T In article <3A60A78A.D48F6D54@y12.doe.gov>, "Dale A. Marcy" <dqm@y12.doe.gov> wrote:   > Group, > N >      I have tried to apply the VAXSHAD07_071 patch to a VAX 4000-500A systemG > running VMS V7.1.  The application of the ECO runs without error from N > VMSINSTAL, but after rebooting, Pathworks will not start correctly (it hangsO > up) and the Show Device and Show Memory commands produce stack dumps as showno > below:  # From the file vaxshad07_071.README:a   Modification Date: 14-Dec-2000< Modification Type:  Added warning regarding access violation  4 ********************  WARNING  *********************4 *                                                  *4 *  After installation of this kit, the SHOW DEVICE *4 *  command causes an access violation. Engineering *4 *  is aware of this problem and is working on a    *4 *  new kit to replace this one.                    *4 *                                                  *4 *  WORKAROUND:                                     *4 *                                                  *4 *  Replace the SHOW.EXE on the system with the     *4 *  version of SHOW.EXE from the VAXSHAD06_071      *4 *  remedial kit.  The older image can be renamed   *4 *  to a later version or the image can be pulled   *4 *  from the VAXSHAD06_71 kit and copied to the     *4 *  directory.                                      *4 *                                                  *4 *  If SHOW.EXE is installed, INSTALL/REPLACE       *4 *  should be performed after the image is renamed  *4 *  or copied from the previous kit.                *4 *                                                  *4 ****************************************************     Hoff, if you're listening...  1 Evidently the SHOW MEMORY command is a problem asc well as SHOW DEVICE.  9 Also, could you persuade the patch folks to reinstate then" VAXSHAD06_071 kit on the ftp site?   -- t Robert Deininger rdeininger@mindspring.como   ------------------------------  # Date: Sat, 13 Jan 2001 21:45:24 GMTt+ From: John Santos <john.santos@verizon.net> 7 Subject: Re: VAXSHAD07_071 ECO problem with Show Deviceh> Message-ID: <MPG.14ca96e6537d10fb9896b3@news.bellatlantic.net>  C In article <3A60A78A.D48F6D54@y12.doe.gov>, dqm@y12.doe.gov says...h > Group, > N >      I have tried to apply the VAXSHAD07_071 patch to a VAX 4000-500A systemG > running VMS V7.1.  The application of the ECO runs without error fromrN > VMSINSTAL, but after rebooting, Pathworks will not start correctly (it hangsO > up) and the Show Device and Show Memory commands produce stack dumps as showno > below: >  > A > $ show dev d                                                   eR >                                                                                 $ >     Allocation class              / > 0                                            c% >     Host name      ""    Host type,w. > avail,                                      O > %SYSTEM-F-ACCVIO, access violation, reason mask=6F, virtual address=03C00000,R > PC > =00000000,G > PSL=00000000                                                         - [...]-  R >                                                                                 H >      Has anybody else had a problem with this ECO?  In case it makes aK > difference, this system is clustered with an Alphaserver 4100 running VMS J > V7.1.  I have restored the system disk to a point prior to the ECO beingD > applied and will be off until Tuesday, so if I need to supply moreP > information, it will be after then.  Unfortunately, this system is not covered2 > by phone support like many of our other systems. >   G I experienced the same problem.  Reported to Compaq.  They told me theysI couldn't replicate it and I must have a bad kit or failed to reboot afteroH installation.  I reloaded the kit; it was identical.  Extracted SHOW.EXEI from the kit; it was identical to the one installed previously.  RepeatedDD renames and install replaces of show.exe to swap in the old and new E versions of SHOW.EXE always gave errors with the new version, whereaslI the old version always seemed to work fine.  I re-installed the ECO, justrI in case something else (DCLTABLES?) was actually causing the problem, butiC it persisted.  Ended up renaming the latest version of show.exe to :. show.exe_bad and installing the older version.  ? I am also running a cluster (1 VAX 4000-200, 1 DEC 3000-300, 1 e@ AlphaServer 1200, NI interconnect), though I don't know if it is% relevant.  The two Alphas are V7.2-1.e  F Compaq never gave me a reasonable response, but a few days later a newG article appeared on DIA saying VAXSHAD07_071 was broken and caused SHOWlH command problems, and that a new ECO would be out soon.  They didn't putH the ECO on HOLD, but instead recommended replacing SHOW.EXE with the one from the VAXSHAD06_071 kit.d  E I wonder if they messed up and included the SHOW.EXE from another VMStG version (7.2 or FT7.3?) because none of the problem descriptions in theg? ECO 7 release notes say they affected SHOW.EXE, but one of the pI corrections in ECO 6 does.  Maybe the image on the ECO 7 kit was supposed I to be exactly the same as the ECO 6 kit, so this replacement does exactlyh  what ECO 7 kit should have done.   -- n John Santose   ------------------------------   End of INFO-VAX 2001.027 ************************