1 INFO-VAX	Sat, 23 Dec 2000	Volume 2000 : Issue 714       Contents: Re: "New" BA350  Re: "New" BA350 / Re: Any tips and/or tricks for VMS with HSG80s? / Re: Any tips and/or tricks for VMS with HSG80s? / RE: Any tips and/or tricks for VMS with HSG80s?  Re: DSNlink for OpenVMS v3.0 Re: DSNlink for OpenVMS v3.0 Re: DSNlink for OpenVMS v3.0 Re: DSNlink for OpenVMS v3.0 Re: DSNlink for OpenVMS v3.0 Re: DSNlink for OpenVMS v3.0 Duplicate messages' RE: Error After Adding New Network Card ( Re: Happy Holidays - From Rich Marcelllo( Re: Happy Holidays - From Rich Marcelllo( Re: Happy Holidays - From Rich Marcelllo( RE: Happy Holidays - From Rich Marcelllo( Re: Happy Holidays - From Rich Marcelllo( Re: Happy Holidays - From Rich Marcelllo& Re: How to Invoke Conversational Boot?0 Re: INFO-VAX complaints about duplicate postings0 Re: INFO-VAX complaints about duplicate postings0 Re: INFO-VAX complaints about duplicate postings0 Re: INFO-VAX complaints about duplicate postings INFO-VAX problems 
 Invitation
 mail bombing? & Re: Monitor on a AXP running VMS 7.2-1) Re: Netscape 3.03/Elsa and window crashes ) Re: Netscape 3.03/Elsa and window crashes = Re: NLA0: the null device - can VMS have other default names? = Re: NLA0: the null device - can VMS have other default names? = Re: NLA0: the null device - can VMS have other default names? ! Re: Problem with linking C++ code ! Re: Problem with linking C++ code ! Re: Problem with linking C++ code  remove3 Re: Rules of Flight -- was DSNlink for OpenVMS v3.0  Re: Segmented keys in RMS = Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster 9 Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster = Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster = Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster = Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster = Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster = Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster = Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster  Re: SLS Question" Static DHCP leases for Macintoshes Re: system disk space  Re: system disk space  Re: system disk space ) Re: System halts when console is shut off ) Re: System halts when console is shut off ) Re: System halts when console is shut off   The Listserver here has gone mad  F ----------------------------------------------------------------------    Date: 22 Dec 2000 15:45:39 -0500* From: kuhrt@eisner.decus.org (Marty Kuhrt) Subject: Re: "New" BA350+ Message-ID: <+lr4ElXhTNSH@eisner.decus.org>   C In article <91u6kh$3t9$1@nnrp1.deja.com>, gmm35@my-deja.com writes: 2 > Well I have been of ebaying and got a used BA3502 > and some SBB's with an eye to arraching it to my2 > VAXserver 3100.  No manual (of course). I attach0 > my miniscsi end inside the shelf (on the right0 > side) plug the 50 pin standard scsi on my VAX.3 > Install a drive in an open address slot (0 at the 2 > top right?) power it up and do a show dev on the/ > VAX console... no drive shows up on the list.  > 
 > I tried: >  diferent drive  >  all "Open" slots % >  moving the cable to the left side.  >   > THe VAX is addressed at SCSI 7 > 1 > I sure would appreciate any ideas you all might  > have.   6 The SBBs should be -VA types to work in a BA350, IIRC.   ------------------------------  % Date: Fri, 22 Dec 2000 08:27:38 -0700 + From: "Barry Treahy, Jr." <treahy@mmaz.com>  Subject: Re: "New" BA350( Message-ID: <3A4372EA.B16CAC36@mmaz.com>  C My first guess is that the BA350 you purchased may have been in the ? middle of a SCSI chain and it is no longer terminated properly.   H Pull the top rear fan out and confirm that the termination plug is still	 inserted.    Barry    gmm35@my-deja.com wrote:  2 > Well I have been of ebaying and got a used BA3502 > and some SBB's with an eye to arraching it to my2 > VAXserver 3100.  No manual (of course). I attach0 > my miniscsi end inside the shelf (on the right0 > side) plug the 50 pin standard scsi on my VAX.3 > Install a drive in an open address slot (0 at the 2 > top right?) power it up and do a show dev on the/ > VAX console... no drive shows up on the list.  > 
 > I tried: >  diferent drive  >  all "Open" slots % >  moving the cable to the left side.  >   > THe VAX is addressed at SCSI 7 > 1 > I sure would appreciate any ideas you all might  > have.  >  >   -- Gary  >  > Sent via Deja.com  > http://www.deja.com/   --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO   A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028    ------------------------------  # Date: Fri, 22 Dec 2000 21:42:52 GMT % From: Uwe Zessin <zessin@my-deja.com> 8 Subject: Re: Any tips and/or tricks for VMS with HSG80s?) Message-ID: <920hsr$tnt$1@nnrp1.deja.com>   + In article <PFBvXZrZlrsI@eisner.decus.org>, -   young_r@eisner.decus.org (Rob Young) wrote: 7 > In article <3A42BB40.4737CBB0@wi.rr.com>, Scott Vieth  <svieth@wi.rr.com> writes: > > Hi:  > > D > > I've connected NT servers to our ESA12000s and even got a NovellC > > server to talk to one of our Big StorageToys just to prove that ? > > it would work but have not yet connected a VMS system to an 
 > > ESA12000.  > > E > > Does anyone have any tips or tricks that they can pass along when 7 > > it comes to connecting a VMS system to an ESA12000?   B The current version of the manual should be sufficient - the first# one I found a little bit confusing. 1 See: http://www.openvms.compaq.com/openvms/fibre/   D > > Has anyone done any dual-path stuff similar to SecurePath on NT?D > > (Which is also similar to the dual-path setup I have with my CI- > > based storage networks.)  E Secure path is extra software for NT + Sun Solaris. OpenVMS V7.2+ and C Tru64 Unix V5.0A+ have multi-path features built into the operating  system.   G I am not responsible for any OpenVMS systems that use FC in production, F however I am involved in a sale of a 4 node cluster and two EMA-12000sF configuration that was handed to the customer some time ago. I've heldE some training there and they are now trying to familiarize themselves  with the hard- and software.    > > Many thanks in advance.  :^) > @ > I'm going to get to do this someday soon, maybe ;-).  I sat inA > on the one day ESA12000 pre-seminar at CETS2000 (Monday session @ > in Oct 2000).  I repeated a story yesterday from that session.G > One of the CETS fellows told a sad story about a customer that didn't = > quite have their HSG80s configured correctly (sorry, detail ? > is sparse ;-) and when an NT server booted it was quite happy A > to say hello to all the storage it saw including the production C > databases that were being served up to Sun servers.  Very painful @ > restore of those databases resulted.  The key I came away from@ > there was to use zoning on the Brocade/Compaq switches.  It isB > hardware based and so the NT or Novell or VMS , etc. servers can > only see their storage.   C Ahem. Switch zoning only helps when the servers talk to _different_ C storage systems, although it is useful to prevent HBAs from talking C to each other, too. As the HSG80's connection table (with ACS V8.5) C is only 64 entries big - zoning can/must also be used to reduce the  number of connections.  A On a storage system that is accessed by multiple systems which do D not form a single cluster you need to set up SSP - selective storage$ presentation (a.k.a. 'LUN masking').   >  Here is a bit about it: > ? > http://www.nwfusion.com/archive/1999/69463_07-05-1999.html?nf  > 5 >  The 2400 and 2800 switches support hardware zoning 4 >  and IP addressing. Hardware zoning allows the SAN9 >  fabric to be partitioned securely into several virtual 9 >               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7 >  private SANs to isolate different operating systems, 6 >  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >  departments or policies.  >  ^^^^^^^^^^^^^^^^^^^^^^^  < It is sometimes also necessary when using one OS, as I wrote> above, to prevent the HBAs from talking to each other. In that= case a storage subsystem can be in multiple zones at the same  time (zones can overlap).   < >      "Zoning is an issue that is becoming important in the+                                    ======== 9 >      SAN environment. With hardware zoning, you have an 7 >      absolute lock on security. No one can change the < >      security unless they know how the switch works," says< >      Farid Neema, president of Strategic Research in Santa >      Barbara, Calif.  ; Well, the article is old, now. Zoning _is_ important today!                               ---  : Oh, and for those of you who have no experience with this:> Zoning and SSP are _not_ mutual exclusive. They have different  purposes and you will need both.   >  [...]    --
 Uwe Zessin3 (If you want to send mail, please use user "zessin" / who lives at "decus.decus.de", not my-deja.com)      Sent via Deja.com  http://www.deja.com/   ------------------------------  # Date: Sat, 23 Dec 2000 01:08:58 GMT $ From: Scott Vieth <svieth@wi.rr.com>8 Subject: Re: Any tips and/or tricks for VMS with HSG80s?) Message-ID: <3A43FB4F.87FBF540@wi.rr.com>    Rob:  R That's easy to avoid if you configure your Units on the HSG80s correctly and allowT only the servers who are supposed to see those units to access them.  I believe that CompaqS called it "Selective Storage Presentation" (I could be mistaken).  It's done within  the HSG80s.   A I haven't had to invoke switch-level security on our SANs yet....   
 -Scott ;^)   Rob Young wrote:  R > In article <3A42BB40.4737CBB0@wi.rr.com>, Scott Vieth <svieth@wi.rr.com> writes: > > Hi:  > > K > > I've connected NT servers to our ESA12000s and even got a Novell server  > > to talk K > > to one of our Big StorageToys just to prove that it would work but have  > > not yet connected   > > a VMS system to an ESA12000. > > H > > Does anyone have any tips or tricks that they can pass along when itI > > comes to connecting a VMS system to an ESA12000?  Has anyone done any K > > dual-path stuff similar to SecurePath on NT?  (Which is also similar to B > > the dual-path setup I have with my CI-based storage networks.) > >   > > Many thanks in advance.  :^) > >  > H >         I'm going to get to do this someday soon, maybe ;-).  I sat inI >         on the one day ESA12000 pre-seminar at CETS2000 (Monday session H >         in Oct 2000).  I repeated a story yesterday from that session.O >         One of the CETS fellows told a sad story about a customer that didn't E >         quite have their HSG80s configured correctly (sorry, detail G >         is sparse ;-) and when an NT server booted it was quite happy I >         to say hello to all the storage it saw including the production K >         databases that were being served up to Sun servers.  Very painful H >         restore of those databases resulted.  The key I came away fromH >         there was to use zoning on the Brocade/Compaq switches.  It isJ >         hardware based and so the NT or Novell or VMS , etc. servers can: >         only see their storage.  Here is a bit about it: > ? > http://www.nwfusion.com/archive/1999/69463_07-05-1999.html?nf  > F >                   The 2400 and 2800 switches support hardware zoningE >                   and IP addressing. Hardware zoning allows the SAN J >                   fabric to be partitioned securely into several virtualJ >                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^H >                   private SANs to isolate different operating systems,G >                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ , >                   departments or policies.+ >                   ^^^^^^^^^^^^^^^^^^^^^^^  > I >                   "Zoning is an issue that is becoming important in the F >                   SAN environment. With hardware zoning, you have anD >                   absolute lock on security. No one can change theI >                   security unless they know how the switch works," says I >                   Farid Neema, president of Strategic Research in Santa # >                   Barbara, Calif.  > G >                   Software zoning is not as robust as hardware zoning 7 >                   and can be more easily compromised.  > E >         Here is where I admit my weakness... but then again I'm not D >         an all knowing Enterprise IT Architect... I am working offG >         3 month old memory and the backing store is over 40 years old N >         and is getting flakier by the day with 3 kids chattering constantly,F >         etc.  plus with no hands on knowledge I can blather on quiteE >         a bit but acknowledge I could do a better job explaining it I >         (maybe ;) if I had the manuals from that session in front of me ) >         and a few months of experience.  > F >         Hope this helps and maybe we get a few hands-on folks to pop
 >         in.  > % >                                 Rob    ------------------------------  % Date: Fri, 22 Dec 2000 09:58:32 -0600 + From: "Main, Kerry" <Kerry.Main@compaq.com> 8 Subject: RE: Any tips and/or tricks for VMS with HSG80s?N Message-ID: <910612C07BCAD1119AF40000F86AF0D805284B31@kaoexc3.kao.cpqcorp.net>   Hello Scott,  3 You may already be aware of this, but just in case:   F The web site which has all the latest info on OpenVMS/SAN planning and' design,SW versions etc can be found at: 8 <http://www.openvms.compaq.com/openvms/fibre/index.html>  L The detailed info can be found in documents in Table 1 at the end of the web page.    Regards,  
 Kerry Main Senior Consultant  Compaq Canada Inc. Professional Services  Voice: 613-592-4660  Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----+ From: Scott Vieth [mailto:svieth@wi.rr.com]  Sent: December 21, 2000 9:23 PM  To: Info-VAX@Mvb.Saic.Com 4 Subject: Any tips and/or tricks for VMS with HSG80s?     Hi:   G I've connected NT servers to our ESA12000s and even got a Novell server  to talk G to one of our Big StorageToys just to prove that it would work but have  not yet connected  a VMS system to an ESA12000.  D Does anyone have any tips or tricks that they can pass along when itE comes to connecting a VMS system to an ESA12000?  Has anyone done any G dual-path stuff similar to SecurePath on NT?  (Which is also similar to > the dual-path setup I have with my CI-based storage networks.)   Many thanks in advance.  :^)   -Scott Vieth& CI Plumber, Fibre Channel Plumber  ;^)   ------------------------------  % Date: Fri, 22 Dec 2000 14:37:34 -0500   From: John Santos <JOHN@egh.com>% Subject: Re: DSNlink for OpenVMS v3.0 6 Message-ID: <1001222141534.17250A-100000@Ives.egh.com>    Are we officially off topic yet?  " On 22 Dec 2000, Bob Koehler wrote:  n > In article <MPG.14ad57dbc709ad4e9896aa@news.bellatlantic.net>, John Santos <john.santos@verizon.net> writes: > L > > I was thinking of Aquarius.  Spider (and Snoopy) were never intended to 	 > > land.  > > E > > I'm not sure if any LM's are still in orbit.  The later ones were E > > crashed deliberately to test the seismic detectors.  I don't know  > > about Spider or Eagle. > E > 10 were flown (Apollo 5, 9, 10, 11, 12, 13, 14, 15, 16, 17), 9 were  > manned (not Apollo 5).   > I > Aquarius reentered Earth's atmosphere.  At least Intrepid, Antares, and J > Challenger were were intentionally crashed into the moon.  So at least 4I > landed.  Spider is the only one I'm fairly sure was left in Earth orbit I > (the unnamed Apollo 5 LM may have been, but we're not counting unmanned J > vehicles; both may have been de-orbitted by ground command).  Falcon andH > Orion may have also been run into the moon.  I think Eagle is in solar > orbit, Snoopy may be, too. > I > So anywhere from one to five manned flying craft were abandon in flight F > with no landing plans.  (I'm sure NORAD knows the correct number andJ > where they are.)  Seven are distinct in having first been landed manned,F > then taken off manned, which is not the usual order for a single useE > vehicle.  But all seven performed exactly the same number of manned D > landings as manned take-offs, which matches norm, unless you count+ > leaving Earth attached to a manned craft.  >   F I was thinking of the LM's, but this isn't exactly what I had in mind.  I My original thought was just reversing the sense of "Takeoff is optional,sA but landing is mandatory" to "Landing is optional, but takeoff isrC mandatory", which I thought applied to the 7 planned moon landings. C In a normal airplane scenario, if you don't take off, then there isnD no need to land.  In Apollo 13's case, since they didn't land, there was no need to take off.  A I wonder if there were ever airplane flights to distant locationsC? (e.g. Antarctica), where the crew's plan was only to land if its@ looked like they would be able to take off again, because rescueB would be impossible if they couldn't take off.  If landing/takeoff: didn't look good, they would just turn around and go home.  ; As for flying craft abandoned in flight...  I wonder if anybB barn-stormers may have done this (by transfering to another plane,B leavine the plane they took off in to crash on its own).  Or maybe? movie stunt pilots.  I don't think the FAA would look kindly oni@ this though.  Without a pilot, the plane would be out of control and might crash anywhere.   J > I think Challenger is the only manned spacecraft name ever re-used.  For= > the near future such action might now be taken as bad luck.c  @ The shuttle Enterprise was named after the Star Trek Enterprise,D which was probably named after the long line of US Navy Enterprises.> But the shuttle Enterprise never flew in space, just unpoweredD test landings, and the original spacecraft Enterprise was fictional.  ? Lots of spacecraft have been named after ships.  Vostok was the G 1st Russian ship to circumnavigate the world, and Columbia, Challenger,uB Discovery, Atlantis and Endeavor were all important in the historyC of oceanic exploration.  I think they should have named one of them B Beagle, but maybe they thought it didn't sound impressive like theD others.  (My mom had a half-beagle/half-bassett who was a very silly dog.)e  sH > ----------------------------------------------------------------------A > Bob Koehler                     | Computer Sciences Corporations? > NASA GSFC Flight Software       | Federal Sector, Civil Group    -- y John Santosc Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Fri, 22 Dec 2000 14:45:29 -0500u- From: "Peter Weaver" <peter.weaver@stelco.ca>-% Subject: Re: DSNlink for OpenVMS v3.0-4 Message-ID: <AbO06.102244$Z2.1217213@nnrp1.uunet.ca>  - "John Santos" <JOHN@egh.com> wrote in messager0 news:1001222141534.17250A-100000@Ives.egh.com..." > Are we officially off topic yet?  9 Yes, and I'm sorry, but thanks for the pre-christmas fun.   = > As for flying craft abandoned in flight...  I wonder if anyBD > barn-stormers may have done this (by transfering to another plane,D > leavine the plane they took off in to crash on its own).  Or maybeA > movie stunt pilots.  I don't think the FAA would look kindly on   C Do ejector seats count? Or how about Crusty in the Simpsons when hes faked his own death?       RULES OF THE AIR   ----------------- <   #5. The ONLY time you have too much fuel is when you're on       fire.    ------------------------------  % Date: Fri, 22 Dec 2000 15:04:10 -0500d  From: John Santos <JOHN@egh.com>% Subject: Re: DSNlink for OpenVMS v3.0t6 Message-ID: <1001222145731.17250A-100000@Ives.egh.com>  ( On Fri, 22 Dec 2000, Peter Weaver wrote:  / > "John Santos" <JOHN@egh.com> wrote in message 2 > news:1001222141534.17250A-100000@Ives.egh.com...$ > > Are we officially off topic yet? > ; > Yes, and I'm sorry, but thanks for the pre-christmas fun.C  7 I'm the one responsible.  You just used an amusing .sigt  ? > > As for flying craft abandoned in flight...  I wonder if any F > > barn-stormers may have done this (by transfering to another plane,F > > leavine the plane they took off in to crash on its own).  Or maybeC > > movie stunt pilots.  I don't think the FAA would look kindly onm > E > Do ejector seats count? Or how about Crusty in the Simpsons when hed > faked his own death?  C Shane Smith asked about parachuting.  My view was, he still landed,u@ just not in the plane.  As for ejector seats, I don't think many2 planes take of with the pilot intending to use it.  < I don't remember the details of Crusty's death.  I assume he faked a plane crash.  A P.S. Paul Sture also got what I was thinking of (private e-mail.)a   --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Fri, 22 Dec 2000 15:08:51 -0500 - From: "Richard D. Piccard" <piccard@ohio.edu> % Subject: Re: DSNlink for OpenVMS v3.0-( Message-ID: <3A43B4C4.12B51955@ohio.edu>  E Are the "rules of the air" collected in one place, or are we going to < have to wait for them to emerge, one at a time, in your sig?                   RDPa     Peter Weaver wrote:e  / > "John Santos" <JOHN@egh.com> wrote in messagen2 > news:1001222141534.17250A-100000@Ives.egh.com...$ > > Are we officially off topic yet? >e; > Yes, and I'm sorry, but thanks for the pre-christmas fun.2 >s? > > As for flying craft abandoned in flight...  I wonder if anyaF > > barn-stormers may have done this (by transfering to another plane,F > > leavine the plane they took off in to crash on its own).  Or maybeC > > movie stunt pilots.  I don't think the FAA would look kindly ong >VE > Do ejector seats count? Or how about Crusty in the Simpsons when heb > faked his own death? >n >   RULES OF THE AIR >   -----------------:> >   #5. The ONLY time you have too much fuel is when you're on
 >       fire.t   --B ==================================================================B Dick Piccard                           Academic Technology ManagerB piccard@ohio.edu                                 Computer ServicesB http://oak.cats.ohiou.edu/~piccard/                Ohio University   ------------------------------  % Date: Fri, 22 Dec 2000 15:44:42 -0500d- From: "Peter Weaver" <peter.weaver@stelco.ca>4% Subject: Re: DSNlink for OpenVMS v3.0g4 Message-ID: <b3P06.102247$Z2.1217752@nnrp1.uunet.ca>  8 "Richard D. Piccard" <piccard@ohio.edu> wrote in message" news:3A43B4C4.12B51955@ohio.edu...D > Are the "rules of the air" collected in one place, or are we going to> > have to wait for them to emerge, one at a time, in your sig? >E  D I have 24 that were sent to me the other week that I plan on postingB with each message. But I just took a look with AltaVista and foundC this list - http://users2.50megs.com/ransompark/page11.html. So youH= haev your choice; wait for my postings or check out the site.   B I just also found it at http://www.gcfl.net/archive/20000627.html,E there they say that this list was published in the June 2000 issue of C Australian Aviation Magazine but I have seen most of these rules insA one form or another in various magazines before. One missing fromtD these lists that is usually there is "The FAA believes that when the@ aircraft paperwork equals the weight of the aircraft ... it willE fly." I guess the Australian Aviation group is not as bureaucratic asr the FAA.  4 If anyone cares I found the Annotated High Flight at. http://idt.net/~rwbutler/Visions/HighFly2.htm.     --   RULES OF THE AIR   -----------------n;   #6. The propeller is just a big fan in front of the planen9       used to keep the pilot cool. When it stops, you cane.       actually watch the pilot start sweating.   ------------------------------  % Date: Fri, 22 Dec 2000 10:24:17 -0800 ! From: Shane.F.Smith@Healthnet.comt% Subject: Re: DSNlink for OpenVMS v3.03D Message-ID: <OF673EF08D.45D7512E-ON882569BD.0064FF89@foundation.com>  K It occurs to me that various space probes were fired off into space with nobI expectation of landfall anywhere. Isn't one of the Voyager series getting^" close to leaving the solar system?  	 Do I win?i   Shanef          ? John Santos <john.santos@verizon.net> on 12/21/2000 11:56:30 PM^   To:   Info-VAX@Mvb.Saic.Comi cc:   & Subject:  Re: DSNlink for OpenVMS v3.0    I In article <91ucuu$dd0$1@lisa.gemair.com>, jordan@lisa.gemair.com says...o- > In article <Al3iAx2noIxw@eisner.decus.org>,e/ > Bob Koehler <koehler@eisner.decus.org> wrote: F > >In article <93q06.101244$Z2.1206232@nnrp1.uunet.ca>, "Peter Weaver"  <peter.weaver@stelco.ca> writes: > >>K > >> What happened 7 times where the takeoff was mandatory and the landingsaD > >> optional? And how did Air Force One take off more times that it > >> landed? > >t   Wrong track ;-)i  I > >   It's only Air Force One as long as the President is on it.  RichardaI > >   Nixon was still President when he got on it and it departed AndrewsrI > >   but it became simply Air Force N26000 (or was it N27000) when Gerryw6 > >   Ford was sworn in while it was still in the air. > >t > E > Yes, but isn't that incident couterbalanced by Lyndon Johnson being H > sworn in as President after Kennedy's assassination while on Air Force+ > 2 (which immediately became Air Force 1)?e  H I'm not sure, but I think Johnson was sworn in while the plane was still* on the ground in Dallas, by a local judge.  C Beside, wasn't Kennedy's body transported back to Washington on thenC same plane, which would have made this Air Force One if it took offr' before Johnson took the oath of office?   G > >   Usually the aircraft is loaned to the departing president, but hesE > >   doesn't actually leave until after the Inauguration so it's noto+ > >   Air Force One while he's flying away.o > > 4 > >   I wonder if Bill is going to NY or Georgetown? > >aI > >----------------------------------------------------------------------)B > >Bob Koehler                     | Computer Sciences Corporation@ > >NASA GSFC Flight Software       | Federal Sector, Civil GroupH > >                                | please remove ".aspm" when replying  4 Bob, you of all people on the group should get it... >t > -Jordan Hendersonv > jordan@greenapple.com  >    -- John Santosn   ------------------------------  % Date: Fri, 22 Dec 2000 08:20:10 -0700s+ From: "Barry Treahy, Jr." <treahy@mmaz.com>  Subject: Duplicate messagesn( Message-ID: <3A43712A.EA34251C@mmaz.com>  F Not to whine too loudly, but I have almost 300 messages just from 11pmG last night until 8am this morning and this is a result of the SAIC listvH duplicating every post as many as six times.  Is any progress being made to cease this?   Barry    --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO   A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028.   ------------------------------   Date: 22 Dec 2000 15:05:48 PSTT From: Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515)0 Subject: RE: Error After Adding New Network Card3 Message-ID: <taAgQryHrnop@mccdev.slac.stanford.edu>l   In article tL     <6FACDDDFBD7BD411B38100D0B7B0CDCC40B5FC@ohms.electric.ci.austin.tx.us>, 6     	"Stuart, Ed" <Ed.Stuart@austinenergy.com> writes:M > Yep, I just got off the phone with the CSC an learned that the EWB-0 devicenN > is referenced as EWA-1 when used in network configurations such as DECnet orD > TCP/IP.  What I didn't ask them was where this is mentioned in theF > documentation.  Thanks for your response, but did you learn about byF > accident as we just did or is it explained in the doc set somewhere?  H         It's in the DECNET documentation.  I  can't say where since it'sH     been  about  5  years  since  i looked  it  up,  but  it's  there...H     Confuing, yes, but it's been this way for all of  DECNET  IV's  life     (if not longer).           -Ken --  M  Kenneth H. Fairfield            |  Internet: Fairfield@SLC.Slac.Stanford.Edu :  SLAC, 2575 Sand Hill Rd, MS 46  |  Voice:    650-926-2924:  Menlo Park, CA  94025           |  FAX:      650-926-3515N  -----------------------------------------------------------------------------B  These opinions are mine, not SLAC's, Stanford's, nor the DOE's...   ------------------------------   Date: 22 Dec 2000 20:29:22 GMT2 From: mathog@seqaxp.bio.caltech.edu (David Mathog)1 Subject: Re: Happy Holidays - From Rich Marcelllos, Message-ID: <920dj2$1mp@gap.cco.caltech.edu>  r In article <iev06.21413$1t.702698@typhoon.ne.mediaone.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes: >a >oK >> I suggest that the VMS engineers arrange for RM to be stripped of his PCsN >> and forced to use a DS10, and nothing but a DS10, for all of 2001.   (Or atJ >> least for a couple of weeks.)  Perhaps the VP in charge of OpenVMS willN >> understand our viewpoint a little better after he actually USES some of the" >> products his division produces! >3M >Which no doubt will allow him to wave a magic wand and get Shockwave and all 4 >those personal productivity apps ported to OpenVMS. >o  I All?  Any would be good.  Heck, it would be nice to see even one! I don'tfK expect to see that magic wand but it would be nice to see a small amount of G cash go towards actually delivering a modern browser.  Let RM live withpJ Navigator 3.03 for a while and maybe he'll feel a bit more inclined to put the resources behind it.   r  D I never understood Digital's alpha strategy - it seemed designed to J perpetually marginalize the alpha.  And boy did it achieve that.  This letB Intel make hundreds of billions of dollars selling chips that wereF nowhere near as fast.  Now Compaq's in charge of the alpha and they'reE every bit as muddled. Compaq's got a great alpha strategy for sellingdB lots of other people's x86 based machines. They seem to think thatG workstation class machines are worth the money when they not only don'tuK ship with any productivity applications, but when none are even available. iH That's just ridiculous and by holding to that they pretty well lock VMS,F Tru64, and even Linux/Alpha out of huge swaths of the market.  BecauseB while there are times where you grit your teeth and buy the numberF cruncher, knowing that you're going to have to get a second machine toJ write up your results, it's a whole lot easier to just buy the one machineK that does it all.  And if you can only get one machine, you generally have iF to get the one with the word processor and supported browser, because D most people cannot live without those, and they'll give up speed andB reliability to get them.   (Which is why SKC is not composed on an+ Alpha, let alone a VMS alpha, right Terry?)l  H The end result is that a lot of people who could buy an Alpha don't as aI direct result of the lack of key bits of software.   That keeps the alphaaI market tiny, it keeps developers off the platform(s), and round and round-J it goes.  Lots of hardware potential, no strategy to capitalize on it. AndG Compaq, like Digital, just muddles along, feeling really good about thegD couple of billion of income they pull in on the high margin systems,H without giving any weight at all to the mass market they have completelyI missed out on.   The transitions too hard, too much risk.  "We can't get i there from here."    Sigh.     K At least AMD's rise has made the x86 market much more competitive.  So that I when we do buy those x86 based machines (instead of Alphas) we don't have 2 to take as large a performance hit as we used to.    Regards,   David Mathog mathog@seqaxp.bio.caltech.eduw? Manager, sequence analysis facility, biology division, Caltech     ------------------------------  # Date: Fri, 22 Dec 2000 20:29:46 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)i1 Subject: Re: Happy Holidays - From Rich Marcelllod0 Message-ID: <009F4FB4.7A9223BA@SendSpamHere.ORG>  k In article <92070v$irr$1@mailint03.im.hou.compaq.com>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:h >yq >In article <009F4EB8.2FEF6B79@SendSpamHere.ORG>, system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) writes:e > K >:... and a greeting .EXE message from Rich too.  Can we take him or CompaqnK >:seriously when the .EXE is a monopoly$chlock image and not one which will L >:run on VMS?  When they do things like this, it is so difficult to keep the
 >:faith... >eH >  As I and as various other folks do not accept and do not run emailed K >  executable code as a general rule, and as unpacking the Microsoft-based fJ >  executables in question (and run them on OpenVMS) will clearly fail, I 9 >  won't happen see these particular marketing materials.a  H Well having veiwed this page with a PeeCee browser (Netscape) to see theG Flash message, I don't see why it couldn't have been a more universally H accepted animated GIF.  Considering the size and the slow speed at whichH it rendered on a 233MHz "inthell inside" box, an animated GIF would have been faster.  G >  Hmmm...  Refresh my memory...  Why is this is a problem for me?  :-)c  F It's the perception that upper management still insists on alientatingG the VMS audience.  I'd think you'd find that a problem as it erodes theaF confidence of the loyal VMS user/buyer -- the same folks that do keep G you employed and your family housed and fed.  I gather from speaking tooG you folks in VMS engineering that you'd prefer to stay there.  If you'duG prefer to spend your remaining working years reinstalling Windblows so oH be it; however, I'd like to pass my remaining years working on/with VMS.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             nO city, n., 1. a place where trees are cut down and streets are named after them.w   ------------------------------  # Date: Fri, 22 Dec 2000 21:24:48 GMTr4 From: "Terry C. Shannon" <terryshannon@mediaone.net>1 Subject: Re: Happy Holidays - From Rich Marcellloa; Message-ID: <AEP06.24110$1t.820298@typhoon.ne.mediaone.net>a  ? "David Mathog" <mathog@seqaxp.bio.caltech.edu> wrote in message & news:920dj2$1mp@gap.cco.caltech.edu...G > In article <iev06.21413$1t.702698@typhoon.ne.mediaone.net>, "Terry C.i, Shannon" <terryshannon@mediaone.net> writes: > >  > >cJ > >> I suggest that the VMS engineers arrange for RM to be stripped of his PCG > >> and forced to use a DS10, and nothing but a DS10, for all of 2001.e (Or atL > >> least for a couple of weeks.)  Perhaps the VP in charge of OpenVMS willL > >> understand our viewpoint a little better after he actually USES some of thei$ > >> products his division produces! > >hK > >Which no doubt will allow him to wave a magic wand and get Shockwave and- all-6 > >those personal productivity apps ported to OpenVMS. > >  > K > All?  Any would be good.  Heck, it would be nice to see even one! I don'teJ > expect to see that magic wand but it would be nice to see a small amount ofI > cash go towards actually delivering a modern browser.  Let RM live with0L > Navigator 3.03 for a while and maybe he'll feel a bit more inclined to put > the resources behind it.  J Would that the MS-Orifice suite and Exploder ran on OpenVMS. Apache is theJ chosen direction for OpenVMS web stuff, but that doesn't do much good from the browser standpoint.   ( The StarOffice port is underway, though.   >tE > I never understood Digital's alpha strategy - it seemed designed to L > perpetually marginalize the alpha.  And boy did it achieve that.  This letD > Intel make hundreds of billions of dollars selling chips that wereH > nowhere near as fast.  Now Compaq's in charge of the alpha and they'reG > every bit as muddled. Compaq's got a great alpha strategy for sellingsD > lots of other people's x86 based machines. They seem to think thatI > workstation class machines are worth the money when they not only don't L > ship with any productivity applications, but when none are even available.J > That's just ridiculous and by holding to that they pretty well lock VMS,H > Tru64, and even Linux/Alpha out of huge swaths of the market.  BecauseD > while there are times where you grit your teeth and buy the numberH > cruncher, knowing that you're going to have to get a second machine toL > write up your results, it's a whole lot easier to just buy the one machineL > that does it all.  And if you can only get one machine, you generally haveG > to get the one with the word processor and supported browser, becauserF > most people cannot live without those, and they'll give up speed andD > reliability to get them.   (Which is why SKC is not composed on an- > Alpha, let alone a VMS alpha, right Terry?)d  L Oh, I *could* FX!32-ize ClarisWorks and run it on my NT-based 433a (in fact,K I have done so, but it's, well, kinda slow) or make the Big Leap to WindowsaK 2000 on the same box (with Windows 2000 Alpha Professional) and perhaps gethD a tad more speed, but I fear such a tactic would merely increase the+ cruftiness of the word processing software.a   > J > The end result is that a lot of people who could buy an Alpha don't as aK > direct result of the lack of key bits of software.   That keeps the alpha6K > market tiny, it keeps developers off the platform(s), and round and round:L > it goes.  Lots of hardware potential, no strategy to capitalize on it. AndI > Compaq, like Digital, just muddles along, feeling really good about the F > couple of billion of income they pull in on the high margin systems,J > without giving any weight at all to the mass market they have completelyJ > missed out on.   The transitions too hard, too much risk.  "We can't get > there from here."5 >1  J I have no idea what it would cost to achieve applications critical mass onL OpenVMS Alpha, but I daresay it would be up there in the billions (single orF double-digit, I dunno). Had a certain very senior Digital manager (notJ Palmer, t'was in fact the CTO) not capitulated to Microsoft's terms duringJ the Alliance for Enterprise Computing talks of late 94-early 95, we'd haveL client-side parity with Intel on AlphaNT. And AlphaNT would still be around.  K The cancellation of the Mica OS and the Emerald project in conjunction withEI the scuttling of the PRISM microprocessor in late March 1988 is what shutiI the door on OpenVMS portability. Attempting to achieve apps critical mass=A today would be roughly equivalent to doing the same thing on MVS.    ------------------------------  % Date: Fri, 22 Dec 2000 11:36:05 +0000 8 From: John Macallister <J.Macallister1@physics.ox.ac.uk>1 Subject: RE: Happy Holidays - From Rich Marcelllo-L Message-ID: <35666012DF4CD411BE940090279FA240112017@ppnt41.physics.ox.ac.uk>  D The "Happy Holidays" (Ugh!) message was aimed at people with desktop1 systems. VMS is not marketed as a desktop system.   K Even if the message had somehow been adapted to run through a "VMS browser"5L I wonder how many of us have VMS hardware configured to reproduce the audio.I I suspect the percentage would be low. On the other hand the number of usEG with PCs available, and used, on our desktops must be high. The message  reaches its target audience.   John  B Name: John B. Macallister  E-mail: j.macallister1@physics.ox.ac.ukH Post: Nuclear and Astrophysics Laboratory, Keble Road, Oxford OX1 3RH,UKA Phone: +44-1865-273388 (direct)  273333 (reception)  273418 (Fax)r   ------------------------------  % Date: Fri, 22 Dec 2000 10:14:31 -0800n! From: Shane.F.Smith@Healthnet.como1 Subject: Re: Happy Holidays - From Rich Marcelllo D Message-ID: <OF31A66B16.99FE86D8-ON882569BD.00642358@foundation.com>  C Sales should be addressed to the rest of the world, it's true. ThatcE postcard was a merry Christmas to the userbase, ie the VMS people, sou should be available on VMS.r   Shanet          2 martin@radiogaga.harz.de on 12/21/2000 07:04:11 PM  * Please respond to martin@radiogaga.harz.de   To:   Info-VAX@Mvb.Saic.Com  cc:   2 Subject:  Re: Happy Holidays - From Rich Marcelllo    F Sorry, but I don't really understand all the fuzz. If Compaq addressesA VMS users, they're accused of preaching to the choir. And if theytF address the rest of the world (or most of it, i.e. WinDoze users), the< VMS users mourn that they can't view it on their machines...  B IMHO, NT really is a nice OS - for a client machine. With a decentG terminal emulator (KEA!, Reflection, or CKermit), an X server (eXceed), F Opera, and perhaps an NFS client or Samba on the VMS side, you're set.   cu,    Martin --J One OS to rule them all       | Martin Vorlaender  |  VMS & WNT programmer7 One OS to find them           | work: mv@pdv-systeme.de1 One OS to bring them all      |V( http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------  % Date: Sat, 23 Dec 2000 01:13:21 -0500e' From: "Bill Todd" <billtodd@foo.mv.com>.1 Subject: Re: Happy Holidays - From Rich Marcelllo1( Message-ID: <921fl3$pdv$1@pyrite.mv.net>  @ David J. Dachtera <djesys.nospam@earthlink.net> wrote in message& news:3A442169.E1567FE@earthlink.net... > Bill Todd wrote: > >d> > > Dave Gudewicz <david.gudewicz@abbott.com> wrote in message6 > > news:91vpgd$nb6$1@fizban.fizban.pprd.abbott.com...J > > > We should put this thread in a time capsule and have someone open it in aJ > > > decade or 3 and observe their reaction to it.  If it were me reading these6L > > > words then, I would use the term BAH, HUMBUG to describe its contents. > > Howi > > > about you? > >tJ > > Very likely - because by then, with high probability, the putative VMSL > > renaissance will have been seen to be as inconsequential as this thread, andbK > > no one will care about VMS any more (save for those people happy to runt it? > > pretty much as-is forever, assuming Compaq holds to its COEi
 commitments).eG > > So this thread will simply be seen, correctly, as just so much more  bleatingF > > by sheep unwilling or unable to summon up the courage to take more directI > > action to make Compaq take an unequivocal position (the same position  bothK > > inside and outside the VMS coterie) on its commitment (or lack thereof)c to > > VMS's future.  >yH > Hi, Bill!! Long time, no see!! How are you doing? The Season's Best to > you!!-  H Happily busy, thanks.  But still able to get frustrated at the same old,' same old w.r.t. VMS, Compaq, and c.o.v.C   >aE > Now, since we've already beaten Compaq bloody both privately and in H > public, what else would you recommend we do? We've shown them both theJ > error of their ways and where the profit potential *REALLY* is. However,F > as the wise man said, "There are none so blind as those who will not* > see" and Compaq is epitome of blindness.  . As you point out, likely deliberate blindness.   >cH > So, short of criminal action, violence and/or civil disobedience, what > do you recommend?o  I Well, about 10 months ago over a dozen people got together and decided totJ present a competent analysis of the situation that Compaq seemed so unableI to assimilate.  After 3 months or so of lively discussion and significant K work, we sent a letter to Capellas, since the problems Compaq had admitting-H that VMS existed seemed pretty clearly structural at the corporate level= rather than simple ineptitude within Marcello's organization.m  L However, Capellas just passed us on to Marcello.  While some of us suspectedI this was a brush-off indicating no hope for any corporate-level change inoJ perspective w.r.t. VMS, we gamely met with Marcello's team, which was moreE than happy to talk with us and receptive to ideas but powerless to dotK anything significant (due to a laughably miniscule ad budget for the FY andaL no real promise of improvement in the future, though they hope that signs ofL life in VMS sales might leave the funding subject to increase at some future time).  K Since then, we've been farting around trying to get Compaq's blessing to gorK public so that more people might become involved and perhaps swing a littlehH more weight at the CEO level.  Exactly why anyone feels we need Compaq'sI blessing has never been clear to me, but the more optimistic among us mayrJ have felt that it demonstrated good faith and a partner-like attitude thatJ would be appreciated and perhaps reciprocated.  The upshot has been that 7K months have passed and Marcello's organization is still dithering about it.   G I'm not going to take it upon myself to 'out' the group - they can keep A waiting if that's what they feel is best.  However, since I had a-K significant hand in beating the letter to Capellas into shape, and since mysJ patience has run out, I'll just include it below:  I don't take credit forG anything like all the ideas in it, but, as I said, enough of the actualR? words are mine (and I put enough effort into them) that I'm not@ uncomfortable releasing it.t  K So my suggestion is that people read it and see what parts they agree with,sK then band together into a group that represents some significant percentageaE of the purchasing power behind the $4B/year or so that VMS reportedlynK generates and get Capellas' attention (since our group's experience is that)H logic doesn't necessarily carry much weight, but money well might).  Or,I come up with some other scenario that better fits the long-term needs andp2 desires of the VMS customer base and present that.  G A small percentage of what we advocated seems to be happening (no clear J reason to think our letter caused much of it, but that's OK with us).  But< none of the major elements seem likely, from what I can see.  J Anyway, have at it.  I hope it generates more activity here than it did atH Compaq.  It's a final draft with perhaps a couple of wording differencesH from what Capellas actually received, but it's *very* close to verbatim.   - bill     May 14, 2000     Michael Capellas Chief Executive Officera Compaq Computer Corporationn   cc:  Richard Marcello.     Dear Mr. Capellas:    E We are an international group of computer industry professionals withtI diverse backgrounds who have recently banded together to discuss concernsoJ about Compaq's relative neglect of its OpenVMS operating system.  Our hopeJ is that a coherent presentation at the highest level may be more effectiveJ in communicating the adverse effects of such neglect than the constant but9 muted customer rumbling that has occurred over the years.o  K We appreciate your time and attention and will try to be concise.  In turn,hI we hope you will be tolerant of the level of occasionally-blunt detail weoL deem necessary to break through long-standing barriers to changes in the wayJ OpenVMS has been handled.  It appears that some such changes may be takingG place even as we speak:  please do not mistake our attempt to present atK complete picture for any lack of appreciation for the efforts already underd way.  J Our own discussions have ranged more widely and deeply than can reasonablyJ be presented here.  Should you find the following material useful and haveH interest in further contact, we would be happy to talk with you or other appropriate parties.     Sincerely yours,  F [we signed most of our names for Capellas, but they're omitted here to protect the shy]       Part I:  Why OpenVMS?  Why Now?a     OpenVMS's Role Within Compaq  D There may be a natural tendency to concentrate on the intense directG competition that the rest of Compaq's products face with their externalgI look-alikes and an understandable reluctance to risk disrupting OpenVMS'shK significant and at least relatively uncontested revenue stream.  If so, theoI view inherited from Digital that OpenVMS is a 'legacy' system nearing itsrL twilight years likely reinforces any inclination to leave well enough alone.> However, such treatment ignores the role OpenVMS could play inD differentiating Compaq from vendors such as Dell, Sun, and HP, whoseJ offerings consist primarily of commodity Windows and Unix products, and inK placing Compaq on equal footing with IBM, which currently does a far better-2 job of leveraging the full breadth of its systems.  E OS/360-370-390 is a respected 36-year-old architecture that remains a-K leader, despite running on limiting 32-bit hardware, and IBM has taken full.K advantage of it over the years as it explored additional markets with newerqK products.  OpenVMS was once a similarly respected system but is now largely I ignored, despite running on arguably the fastest and most scalable 64-biteG commercial hardware in the world, because Digital decided long ago thatcI 'non-proprietary' systems were its future and did its best to convert its$$ existing customer base to their use.  F Since it remains impossible to forecast when, if ever, Unix (let aloneF Windows) will be able to adequately replace OpenVMS (or OS/390), IBM'sH strategy of integrating its proprietary crown jewel seems to have provenH superior to Digital's strategy of replacement.  Unfortunately, corporateF decisions of such a fundamental nature carry with them a great deal ofF inertia, not least because admitting failure can compromise high-levelI careers, and that inherited inertia apparently continues to influence them. attitude of Compaq toward OpenVMS to this day.     But OpenVMS is so Proprietaryt  D So are OS/390 and OS/400 - perhaps more so, if one includes hardwareK multi-sourcing considerations.  And while customers and third-party vendorspE do gravitate toward the familiarity and increased vendor-independence L offered by Unix or Windows solutions when such solutions satisfy their needsF cost-effectively, when this is not the case they still readily turn toE full-service vendors for 'proprietary' solutions as long as they havehI confidence that the vendor, and the solution, will continue to meet theiry requirements over time.r  F Despite over a decade of marketing neglect, OpenVMS has maintained itsJ technological leadership and remains superbly qualified for this role.  ItJ is significantly superior to any commonly-used Unix (let alone Windows) inH the areas of reliability, availability, scalability, disaster-tolerance,J security, near-real-time activities (e.g., process control), I/O-intensiveG workloads, record-oriented processing, and mixed-language applications.eC Other notable strengths include ease of administration, support forA> application development, and performance/operating efficiency.  J Given the degree to which expectations have been lowered over the years byL Windows and Unix and their associated hype, we feel a need to emphasize thatG these distinctions are real.  OpenVMS can credibly claim to be the mostIH scalable system on the planet:  it is suitable for the smallest start-upL operation, yet can never be outgrown.  It has levels of security found in noK other commercial operating system, clustering technology that remains yearsiK ahead of any competition, and a degree of fault-tolerance and resistance to J error that allows OpenVMS to be used in mission-critical systems that mustI stay up for years at a time (the longest we know of is 17 years without ao5 reboot in the service of the Irish National Railway).l    $ OpenVMS as The Compaq Differentiator  J Sole ownership of OpenVMS gives Compaq the ability to react quickly to newF customer needs and attract business by offering features that Unix andH Windows environments cannot match (see above).  Customers dependent upon> unique OpenVMS features become tied to Compaq to a degree thatG 'non-proprietary' customers are not - a healthy relationship as long ashL Compaq views it as symbiotic rather than exploitative.  Combine this lock-inH with the common desire, especially among large customers, to deal with aJ single vendor, and other vendors who lack such soup-to-nuts range in theirJ product sets become second-class contenders in a significant percentage of sales situations.e  K IBM has long used its OS/360-370-390 architecture to anchor the high end intJ such situations and the niche solutions supported by its OS/400 systems toE anchor its presence in other environments.  If Compaq can demonstrateeG effectively that it now views OpenVMS as a core asset rather than as annL aberration in its product line-up, OpenVMS can once again become the kind ofL keystone that clinches corporate-wide standardization on a single vendor and5 stabilizes, rather than frustrates, customer loyalty.,  I Ideally, all of Compaq's systems should be able to win sales on their ownr@ merits.  However, the intense competition for advantage in IntelJ Architecture hardware platforms (including IBM's OnForever robust hardwareH and X Architecture heterogeneous clustering initiatives), the continuingL apathy toward Tru64 in the Unix market, and the partnerships Dell has formedL to sell servers and server-appliances and to counter its weakness in serviceI and support are only a few of the factors conspiring to make it difficult G for Compaq to hold the Windows and Unix ground it already occupies, leteF alone gain any.  Linux may change the nature of the Unix playing fieldC somewhat, but here again competitive pressures are strong, with IBM G committing to support Linux environments on all its systems - includingWK OS/390 and OS/400 - as well as positioning S/390 systems as general-purposer2 servers (an important AlphaServer market segment).  H A highly-visible renewed commitment to OpenVMS is one of the few ways inL which Compaq can differentiate itself to gain entry into and/or advantage inK corporate sales situations for all its products.  It is also an opportunityoL to break the long-standing stranglehold that industry doubts about OpenVMS'sC future have held on one of Compaq's highest-margin revenue streams.t  @ The sections below outline some of the current obstacles to suchH revitalization and suggested remedies for them.  Since we recognize thatG Compaq has a great deal of experience in how to market products that itTJ wants to market, most of this discussion is presented in abbreviated form,2 which we would be happy to expand upon if desired.       Part II:  Problems/Remediesn     Advertisingd  K Unless Compaq puts its money where its mouth is, no one is going to believe C that a renewed commitment to OpenVMS is any more real than previous E temporary blips on the otherwise blank radar screen.  How much money?EI Compare the net profit generated by PC and Industry-Standard Server salesyH and service to that generated by OpenVMS sales and service.  Now compareI their respective ad budgets, in all media (not including AlphaServer ads:lL they almost never mention OpenVMS save as an afterthought to a Tru64 pitch).  J While that provides a first approximation of the degree of change requiredK for credibility, OpenVMS may not need nearly as much general advertising as-L long as it has industry advertising comparable to Windows'.  For a start, itA needs something like two-page "OpenVMS Advantage" ads in the sameRJ publications (and with the same frequency) as the "Windows 2000 Advantage"H ads so that not only the OpenVMS name but detailed information about itsK capabilities will reach the people who approve corporate purchases, as well L as those who recommend them.  (We understand that the Windows 2000 AdvantageI ads are shared with Microsoft, but many of Compaq's other Wintel platformp
 ads are not.)a  I OpenVMS advertising needs to emphasize the OpenVMS strengths (see earlier K list) that other systems, including Compaq's, lack, just as advertising for.J other Compaq systems emphasizes their own perceived strengths (such as theE recent UK ad headlined "Nothing integrates better with NT than TRU-64RK UNIX" - ahem).  This is difficult to do tactfully when an ad is shared with-L other Compaq systems, though ancillary, less specific shared advertising canK be effective too as long as the systems are featured equally.  OpenVMS alsolL needs to be advertised to the rest of Compaq's current customers in the same? manner other Compaq systems are advertised to the OpenVMS base.c  I Additional specialized OpenVMS advertising is warranted in markets deemeduK especially receptive to OpenVMS - certainly the current 'target market' set2B plus any environment (e.g., Web services of all kinds) requiring aK highly-available, highly-scalable, and/or highly-secure platform.  However,hK it is important not to perpetuate the impression that those markets are theaL only areas in which OpenVMS is actively competing:  a system perceived to beK holed up in a few remaining strongholds is not one corporations will choosesH to commit to for the next decade or more.  Less concentrated but visibleK specialized advertising in any market segment where OpenVMS can effectivelyRF compete will provide important reassurance of Compaq's dedication to a* strategy of broad-based, long-term growth.  J All the above won't begin to use up the amount of money suggested above asK necessary for credibility, but it will at least be a good start.  It likelydJ has more directly-measurable benefits than generic 'brand awareness' printG and television advertising (though the competition does not shrink from-I funding this).  And it should provide initial evidence suggesting whether ) further increases would prove profitable.:     Web Informationi  L Once people are made aware of OpenVMS, it is imperative that they be able toG find out virtually anything they may want to about it easily, including.E information about purchasing and pricing, available applications, andaI up-to-date benchmark results (a critical factor in some sales).  While wehJ recognize that Compaq has been working hard to improve OpenVMS informationH accessibility via the corporate Web site, we have yet to see anything toF suggest that the desired result will appear in the foreseeable future.  H There are too many examples of Web-site problems even just to list here,G which leads us to suspect that the underlying issue may be structural -oF perhaps a result of over-centralization of content-control rather thanA leaving it in the hands of the people best equipped to present iteC effectively (under suitable overall corporate look, feel, and taste I guidelines), un-muddled by frequent inter-mixing of references to Windows J and Tru64.  Whatever the cause, prompt action is important, and once again< we would be happy to offer detailed suggestions if asked to.    ( Corporate Publications and Presentations  L While the decidedly inadequate OpenVMS Web presence may merely be the resultG of corporate ineptitude, the consistent disregard for OpenVMS in CompaqeK publications and presentations that glowingly showcase Windows, Tandem NSK,wG and Tru64 presents the disturbing appearance of an active conspiracy ofe silence.  When  E Compaq's Annual Report fails even to mention OpenVMS in its corporateeF narrative despite an 'unstoppable' theme that OpenVMS fits better than anything else save NSK,y  K the January Investor Relations presentation by Enrico Pesatori is similarlyi silent,i  I the Inform corporate newsletter presents a 'success story' without notingn# that the platform used was OpenVMS,   K the Compaq Non-Stop eBusiness Strategy white paper treats OpenVMS more likes@ SCO Unix and NetWare than like Compaq's other main-line systems,  A the set of AlphaServer Web links is overwhelmingly Tru64-related,l  K it conveys a definite message to both existing and potential customers thatiF OpenVMS is not a priority for Compaq.  No competitor could instill theH degree of 'Fear, Uncertainty, and Doubt' about OpenVMS that Compaq's ownL actions (and Digital's before it) have:  pervasive, long-term change will be necessary to erase it.     Salesn  J Similar FUD regarding OpenVMS has been generated by the persistent effortsJ of the sales force to encourage happy OpenVMS customers to migrate to someI other Compaq platform.  We hope that recent rumors of change in this areaeI are true:  not only does it tend to lose Compaq entire corporate accountscI (if they migrate, it is often to a competitor), but it's really annoying.   K We also have anecdotal evidence that when OpenVMS is being considered for a L new installation, along with some other Compaq system, failure to pursue theL OpenVMS option often results in loss of the entire sale to some other vendorL (e.g., OpenVMS was competitive due to its unique qualities whereas Tru64 was not).a     Press Relationsi  G Compaq does a commendable job of releasing information about its PC andrH Industry-Standard Server offerings and a more modest but adequate job ofE releasing information about AlphaServer hardware and Tru64 Unix.  ButoI (again) there is only silence where OpenVMS is concerned, and as a resulttE media coverage routinely categorizes OpenVMS as 'aging', 'legacy', orgC 'defunct' (all have appeared recently).  A bit of targeted personalu= schmoozing might also help:  the return could be substantial.e     Application Availability  J The fact that customers often choose an application and only then choose aG hardware platform means that system sales can often be dependent on thegE range of available applications - an area in which OpenVMS has becomeiK seriously deficient.  Visible renewed commitment by Compaq to OpenVMS sales L across the full market spectrum will start to encourage Independent SoftwareL Vendors and Value-Added Resellers to make applications available on OpenVMS.I Even minor additional effort specifically aimed at courting and educating-E ISVs and VARs could achieve disproportionate results.  For especiallyyH strategic applications, consider providing hardware, consulting, or even financial aid.  K Examples of enterprise applications not available in their current versionssF on OpenVMS include SAP, Oracle Applications, Baan, Peoplesoft, Sybase,C Informix, DB2, MS SQLserver, Netscape Server Suite, Lotus Notes, MS L Exchange, MS IIS, Squid, MS Office, Corel Office, Lotus Smartsuite, and StarH Office.  The much shorter list of such applications that are available -F Oracle, Oracle RDB, PMDF, and Apache - does not compare favorably with competing platforms.     New Product Features  I Published road maps for OpenVMS development do not present a picture of a K system committed to continued leadership of the kind it enjoys today.  ThisRK makes knowledgeable customers hesitant to commit their own operations to it,G for the long term.  Targeted new development can also be a real bargain I compared with other promotional mechanisms, and we offer two examples fore consideration:  K The currently-defunct OpenVMS POSIX environment originally gave rise to theyL 'Open' in OpenVMS.  We have heard that efforts are under way to resurrect itE in a more usable form, with better performance and one hopes improvedlK integration with the native environment (i.e., much more than just a 'check.G the box' facility).  Extension to allow it to run many/most Alpha LinuxuG binaries on OpenVMS would not only help make a large library (1200+) ofiK sorely-needed applications instantly available but would match IBM's 'Linuxs everywhere' strategy (seeiL http://www10.nytimes.com/library/tech/00/03/biztech/articles/20soft.html andF http://www.redherring.com/insider/2000/0503/tech-ibmlinux050300.html -G interesting reading in multiple respects).  An efficient and integrated K Linux persona coupled with the existing strengths of OpenVMS would create at# platform unequaled in the industry.   F A second initiative which would mesh nicely with such Linux support isB development of a heterogeneous SAN file system to allow concurrentK data-sharing across OpenVMS, Windows 2000, and Unix/Linux.  Though IBM, HP,nK Veritas, EMC, Adic, Avid, and likely others have products in this space, ithJ remains an area where no one yet appears willing to make the commitment toH do the job right.  This represents a leadership opportunity that Compaq,K with its expertise across OpenVMS, Tru64, and NT environments, is unusuallyaK well-positioned to avail itself of.  It also offers improved integration oftG heterogeneous systems within single Wildfire boxes, dovetails well witheL Compaq's strengths in lower-level storage architecture, and protects againstI industry standardization on some competitive implementation that does noti include OpenVMS and Tru64.     OpenVMS in Academiai  H We applaud rumors of a recent decision to offer free OpenVMS licenses toK academia.  In combination with existing free academic cluster licensing, itsH should help stimulate use of OpenVMS in areas long ago lost to free Sun, *BSD, and Linux configurations.h  G While we cannot prove it, we suspect that the decline of OpenVMS in the L marketplace is at least in some small part attributable to its disappearance? from academia (where it once reigned supreme) and its resulting I unfamiliarity to the current generation of purchasers, users, and supportnC personnel.  If so, additional efforts in this area (e.g., strategicsL applications and video and/or on-line tutorials that could be used as course adjuncts) could prove fruitful.u     Entry-Level System Pricing  G Aggressive pursuit of entry-level sales (like attention to academia andrJ serious on-going development) tends to reassure customers about a vendor'sI long-term commitment to a system, since there is little immediate, direct C payoff for the effort expended.  One of our members stated it thus:s  J "Without seeds, you don't get seedlings.  Without seedlings, you don't getK new trees.  A huge, elegant, mature tree surrounded by asphalt and concrete L and maintained lawn and pretty little flowerbeds in a city square is a dyingL tree.  In contrast, a patch of fertile land covered in nondescript scrub can( be a forest of such trees in the making.  K "I think people may appreciate this at an instinctive level.  No OpenVMS in H colleges, no small OpenVMS sites, no affordable low-end OpenVMS, means aG dying operating system, and the only question is how long the remainingh trees will stand for."  F We will not presume to suggest what Compaq's trade-off between low-end@ profit and market penetration should be, but offer the following observations for consideration:v  F The low-end market is especially sensitive to the relationship betweenF hardware and system software price.  This suggests making at least theG system software price platform-specific rather than shared across, say,)G DS10s, DS20s, and ES40s (or a new sub-DS10 platform should one appear).rL Pre-packaged 'cluster in a box' configurations and volume discounts starting@ at quantity 2 for multi-box sales might also stimulate interest.  K The price of an entry-level OpenVMS system will inevitably be compared withcI Windows 2000 Server or Windows 2000 Advanced Server (the latter including J primitive clustering support).  Given the superior capabilities of OpenVMSH and the fact that entry-level DS10 hardware costs about twice as much asL good-quality Intel hardware, one can justify pricing a DS10 OpenVMS softwareD configuration at about twice the level of a similar Windows software configuration.  G Price it much higher than that level, and even OpenVMS enthusiasts will*K start to question its value; price it noticeably lower, and the market willsJ perceive it as aggressive.  In this context, note that Windows 2000 ServerH and Advanced Server include features such as TCP/IP and other networkingG support, disk defragmentation, and volume shadowing that are extra-costuE options in OpenVMS and should thus be added before comparing pricing.nH Furthermore, Windows system prices are typically discounted when bundled with a hardware sale.t      
 Conclusion  I Because OpenVMS has suffered years of neglect compared with other DigitalrI and competing systems, temporary compensatory efforts may be necessary touG let the world know in no uncertain terms that OpenVMS is not only still'K alive but hunting for bear.  We otherwise suggest that all Compaq platformsoI will have the best chance of realizing their potential if they attempt totJ exploit their mutual synergy (a strategy that IBM embraces whole-heartedlyL within its own product set) rather than partition themselves into boxes thatG at least some customers will not find to their liking.  In the process,tF Compaq will return to a business model that served Digital well at theJ height of its success - and be seen as more responsive to its customers as well.s   ------------------------------   Date: 22 Dec 2000 19:11:11 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)/ Subject: Re: How to Invoke Conversational Boot?i6 Message-ID: <92090f$j3t$2@mailint03.im.hou.compaq.com>  ] In article <3a4294f9.79257534@news.iquest.net>, bskidmore@iquest.net (Barry Skidmore) writes:gE :I need to invoke a conversational boot on a MicroVAX 3100-40 runningaC :OpenVMS 7.2, so that I can bypass SYSTARTUP_VMS.COM.  The manual IhB :have, unfortunately, does not tell me how to invoke SYSBOOT on my :system.  (   Please see the OpenVMS FAQ for this...  A   Alternatively, check the manuals on the OpenVMS website -- the  #   OpenVMS FAQ has pointers to them.c  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Fri, 22 Dec 2000 17:02:51 -0500a, From: "Glenn C. Everhart" <Everhart@GCE.com>9 Subject: Re: INFO-VAX complaints about duplicate postingsm' Message-ID: <3A43893B.31135DD1@GCE.com>e  C The info-vax list side has massive duplication going on; most postsp@ seemed to have around 8-10 duplicates this AM. Strangely it only! hits info-vax, not the newsgroup.r   John Santos wrote: > H > The last several posts I've made are causing me to get multiple e-mailH > messages about duplicate posts from "L-Soft list server at UGA (1.8d)" > <LISTSERV@LISTSERV.UGA.EDU>f > F > So far I've received anywhere from 3 to 10 of these messages quoting  > the 3 posts I made last night. > B > At first I attributed it to real duplicate postings from my newsE > server, which has been acting extremely flaky all month.  (Verizon,lE > see comp.dcom.xdsl for all the gory speculation, though no official ? > explanation from Verizon has ever appeared.  Really makes youiC > appreciate being a customer of the DEC/Compaq VMS group.  Thanks,e > Hoff and crew.)v > C > Several times it refused to accept posts until I disconnected andiD > tried again.  One of them appeared to fail posting, but the secondB > time it gave me a "duplicate post" error (directly from the newsB > server, not from INFO-VAX), and a few minutes later the "failed" > post appeared on comp.os.vms.d > E > However, today the news server seems to acting okay, so maybe theree. > is some kind of forwarding loop in INFO-VAX. > D > If it is really my news server (or my news reader, Gravity 2.30 onC > Win98 SE) causing this, any idea how to make it stop?  Are people F > seeing duplicate posts from me?  (They aren't showing up in Gravity,@ > but maybe it or the Verizon news server are suppressing them.) >  > --
 > John Santoso   ------------------------------  % Date: Fri, 22 Dec 2000 13:18:40 -0500g& From: Ken Robinson <ksrobin@erenj.com>9 Subject: Re: INFO-VAX complaints about duplicate postingsh7 Message-ID: <5.0.0.25.2.20001222131729.01c1a350@clmail>o  0 At 05:18 PM 12/22/2000 +0000, John Santos wrote:G >The last several posts I've made are causing me to get multiple e-mail G >messages about duplicate posts from "L-Soft list server at UGA (1.8d)"y ><LISTSERV@LISTSERV.UGA.EDU> >fE >So far I've received anywhere from 3 to 10 of these messages quoting, >the 3 posts I made last night.o  I It looks like a problem on the list, not with the newsgroup. So far I've o= deleted at least 300 to 400 duplicate posts since last night.    Ken Robinson   ------------------------------  % Date: Fri, 22 Dec 2000 15:22:54 -0700 + From: "Barry Treahy, Jr." <treahy@mmaz.com>n9 Subject: Re: INFO-VAX complaints about duplicate postingss( Message-ID: <3A43D43E.4B7435D8@mmaz.com>  J It seems to be coming from a portal node at IP 198.151.13.15, I've startedL blocking that address for the time being.  I've been receiving dozens of theH same message duplicated not only through out the night but also repeated/ during the entire day with the same time stamp.e   Barryn   "Glenn C. Everhart" wrote:  E > The info-vax list side has massive duplication going on; most posts B > seemed to have around 8-10 duplicates this AM. Strangely it only# > hits info-vax, not the newsgroup.  >  > John Santos wrote: > >tJ > > The last several posts I've made are causing me to get multiple e-mailJ > > messages about duplicate posts from "L-Soft list server at UGA (1.8d)" > > <LISTSERV@LISTSERV.UGA.EDU>e > > H > > So far I've received anywhere from 3 to 10 of these messages quoting" > > the 3 posts I made last night. > >nD > > At first I attributed it to real duplicate postings from my newsG > > server, which has been acting extremely flaky all month.  (Verizon,fG > > see comp.dcom.xdsl for all the gory speculation, though no officialsA > > explanation from Verizon has ever appeared.  Really makes yousE > > appreciate being a customer of the DEC/Compaq VMS group.  Thanks,i > > Hoff and crew.)m > >iE > > Several times it refused to accept posts until I disconnected andaF > > tried again.  One of them appeared to fail posting, but the secondD > > time it gave me a "duplicate post" error (directly from the newsD > > server, not from INFO-VAX), and a few minutes later the "failed"! > > post appeared on comp.os.vms.w > >hG > > However, today the news server seems to acting okay, so maybe therel0 > > is some kind of forwarding loop in INFO-VAX. > > F > > If it is really my news server (or my news reader, Gravity 2.30 onE > > Win98 SE) causing this, any idea how to make it stop?  Are peoplecH > > seeing duplicate posts from me?  (They aren't showing up in Gravity,B > > but maybe it or the Verizon news server are suppressing them.) > >e > > -- > > John Santosb   --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO   A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028r   ------------------------------  % Date: Fri, 22 Dec 2000 20:38:38 -0700 + From: "Barry Treahy, Jr." <treahy@mmaz.com> 9 Subject: Re: INFO-VAX complaints about duplicate postingso( Message-ID: <3A441E3E.E74C93C9@mmaz.com>  P I know its SAIC, but I've been looking at the headers and it appears that all ofQ the junk messages are coming from this IP address where as the originals are fromnK the mvb node.  I suspect that the folks at SAIC have long been gone for theaQ holidays, but I haven't had any problems since the block yet single-copies of the # messages posted are being received.o   Barrye   Glenn and Mary Everhart wrote:  I > Feh. That's at SAIC, which is where the official info-vax site is (sametK > company; mvb.saic.com is 139.121.16.104 but this could be - probably is -t6 > on their internal net.). Lord knows what's going on. >r > "Barry Treahy, Jr." wrote: > >nN > > It seems to be coming from a portal node at IP 198.151.13.15, I've startedP > > blocking that address for the time being.  I've been receiving dozens of theN > > same message duplicated not only through out the night but also repeated1y3 > > during the entire day with the same time stamp.l > >i	 > > Barryh > >o > > "Glenn C. Everhart" wrote: > >uI > > > The info-vax list side has massive duplication going on; most postsoF > > > seemed to have around 8-10 duplicates this AM. Strangely it only' > > > hits info-vax, not the newsgroup.t > > >n > > > John Santos wrote: > > > >eN > > > > The last several posts I've made are causing me to get multiple e-mailN > > > > messages about duplicate posts from "L-Soft list server at UGA (1.8d)"# > > > > <LISTSERV@LISTSERV.UGA.EDU>t > > > >eL > > > > So far I've received anywhere from 3 to 10 of these messages quoting& > > > > the 3 posts I made last night. > > > >rH > > > > At first I attributed it to real duplicate postings from my newsK > > > > server, which has been acting extremely flaky all month.  (Verizon,tK > > > > see comp.dcom.xdsl for all the gory speculation, though no official.E > > > > explanation from Verizon has ever appeared.  Really makes youlI > > > > appreciate being a customer of the DEC/Compaq VMS group.  Thanks,  > > > > Hoff and crew.)o > > > >tI > > > > Several times it refused to accept posts until I disconnected andsJ > > > > tried again.  One of them appeared to fail posting, but the secondH > > > > time it gave me a "duplicate post" error (directly from the newsH > > > > server, not from INFO-VAX), and a few minutes later the "failed"% > > > > post appeared on comp.os.vms.) > > > >rK > > > > However, today the news server seems to acting okay, so maybe theret4 > > > > is some kind of forwarding loop in INFO-VAX. > > > >eJ > > > > If it is really my news server (or my news reader, Gravity 2.30 onI > > > > Win98 SE) causing this, any idea how to make it stop?  Are peopledL > > > > seeing duplicate posts from me?  (They aren't showing up in Gravity,F > > > > but maybe it or the Verizon news server are suppressing them.) > > > >u
 > > > > -- > > > > John Santose > >r > > -- > >bC > > Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIOf > >hE > > E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028t   --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIOi  A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028i   ------------------------------  % Date: Fri, 22 Dec 2000 10:49:16 +0000s$ From: Steve.Spires@yellowpages.co.uk Subject: INFO-VAX problems/ Message-ID: <002569BD.003B7310.00@quegw01.btyp>b   cc:p bcc:L Contact:   Tel: 3063  -  IS - Infrastructure, 1st Floor, Bridge Street Plaza   INFO-VAX problemsc    P I thought this had been fixed - the multiple postings I mean - but it appears toP be worse now than it was before. It looks like I'm getting over 6 copies of each% message which is causing a problem...t   Any news on this?S  K I'm not looking forward to how many messages might be waiting for me when I * return to work in the middle of next week!   Steve Spires VMS System Manager BT/Yellow Pagesi     [Information] -- PostMaster:D This transmission is intended solely for the addressee(s) and may beL confidential. If you are not the named addressee, or if the message has beenP addressed to you in error, you must not read, disclose, reproduce, distribute or use this transmission.  L Delivery of this message to any person other than the named addressee is notH intended in any way to waive confidentiality.  If you have received thisF transmission in error please contact the sender or delete the message.  
 Thank you.   ------------------------------  % Date: Fri, 22 Dec 2000 14:24:47 +0001 ( From: Andree <andree_clairs@ciaoweb.com> Subject: Invitationi- Message-ID: <0G5Z00MM8HWP3O@mx.west.saic.com>    <BODY bgColor=#ffffff>0 <DIV><FONT face=Arial size=2>Hello!</FONT></DIV><DIV><FONT face=Arial size=2>We are looking for professional singles who would like to register for FREE at the Soulmate Zone, the leading site for quality singles from around the world. If interested, join us at www.soulmatezone.com and take a quick tour before registering. Thanks for your time and attention. We apologize for any inconvenience we may have casued you.</FONT></DIV>e0 <DIV><FONT face=Arial size=2>&nbsp;</FONT></DIV>0 <DIV><FONT face=Arial size=2>&nbsp;</FONT></DIV>6 <DIV><FONT face=Arial size=2>Best Wishes,</FONT></DIV>0 <DIV><FONT face=Arial size=2>&nbsp;</FONT></DIV>0 <DIV><FONT face=Arial size=2>Andree</FONT></DIV>E <DIV><FONT face=Arial size=2>http://www.soulmatezone.com</FONT></DIV>l   ------------------------------  % Date: Fri, 22 Dec 2000 20:03:16 +0200c From: mauf@uhu.unizar.es Subject: mail bombing?* Message-ID: <00122220031655@uhu.unizar.es>  B From:	SMTP%"hoffman@xdelta.zko.dec.nospam" 22-DEC-2000 19:58:18.26 To:	Info-VAX@Mvb.Saic.Com  CC:	. Subj:	Re: Happy Holidays - From Rich Marcelllo    p In article <009F4EB8.2FEF6B79@SendSpamHere.ORG>, system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) writes:  J :... and a greeting .EXE message from Rich too.  Can we take him or CompaqJ :seriously when the .EXE is a monopoly$chlock image and not one which willK :run on VMS?  When they do things like this, it is so difficult to keep theb	 :faith...a  G   As I and as various other folks do not accept and do not run emailed  J   executable code as a general rule, and as unpacking the Microsoft-based I   executables in question (and run them on OpenVMS) will clearly fail, I e8   won't happen see these particular marketing materials.  F   Hmmm...  Refresh my memory...  Why is this is a problem for me?  :-)  F   Seriously, there are folks that do accept and do run these marketingF   widgets, and do find them interesting.  I will suggest an "opt-out" F   mechanism for those folks on the email distribution list that do notF   accept these or cannot process these...  Or would you prefer to haveH   these duplicated, so that you can receive a parallel set of X Windows >   marketing distributions for execution directly on OpenVMS?    G   All that said, and as should be clear from my earlier statements of, sK   um, paranoia, I'd personally be no more likely to run emailed executable oG   images on my OpenVMS system than run emailed Microsoft executables...t  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com    N Just before the preciding message, I have received the (huge) e-mail referred.L A few weeks ago (*and due to an error of mine*) my quota was exceeded and myK account bounced back many Info-Vax communications, for which I have alreadyr! apologized to the List mantainer.n  M For the last 2-3 days, I have received *every* message 5-? times. I am afraid K this time my quota will be exceeded due to the mailing list, unless I spendf my three free days deleting.   What should I do?l     Merry Christmas to all     Miguel A. Uson Zaragoza   ------------------------------   Date: 22 Dec 2000 20:14:11 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)/ Subject: Re: Monitor on a AXP running VMS 7.2-1d6 Message-ID: <920cmj$jil$1@mailint03.im.hou.compaq.com>  \ In article <3a436082.76217725@news.starnet.net>, sfm1115@bjcmail.carenet.org (Shawn) writes:E :I know how to run Monitor System and Monitor System/all.  Is there aiA :way I can re-direct the output to a file rather than the system.  ..A :I looked through my manuals and was unable to locate the correcti :parameter to set..., :I am running OpenVMS 7.2-1 on an Alpha 2100  =   The MONITOR utility can record and play back information...      $ MONITORg   MONITOR> HELP MONITOR /RECORDr   ...t   Topic? MONITOR /INPUT    ...i  F   For additional details, please see the MONITOR utility documentation@   in the OpenVMS manual set.  An online version is available at:  &     http://www.openvms.compaq.com:8000<       /72final/6258/6048pro_contents_002.html#toc_chapter_15    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 22 Dec 2000 22:04:50 GMTa7 From: moroney@world.std.spaamtrap.com (Michael Moroney)l2 Subject: Re: Netscape 3.03/Elsa and window crashes& Message-ID: <G5zpC3.9tB@world.std.com>  4 mathog@seqaxp.bio.caltech.edu (David Mathog) writes:  L >If I leave Netscape running too long on my VMS 7.2-1 DS10 with an Elsa cardL >it has a tendency to crash and take the rest of my X11 session with it. TheJ >symptom is that I click on a link and BOOM - the entire session goes downG >and the screen blanks.  About 2 seconds later I'm looking at the logincI >screen.  That indicates that the server stayed up, but the session went e >down. n  G I had this happen all the time on a VS4000/VLC.  I finally solved it bynG greatly increasing a quota of the DECW$SERVER process in the appropiateoI startup .com file (I forget which)  I think it was the pagefile quota, itu9 was definitely a virtual page related quota of some sort.o  D Problem is Netscape leaks memory and other resources like a sieve...   -Mike    ------------------------------  + Date: Fri, 22 Dec 2000 16:32:55 -0600 (CST)n2 From: Carol Lee Poush <cpoush@brazosport.cc.tx.us>2 Subject: Re: Netscape 3.03/Elsa and window crashesR Message-ID: <Pine.OSF.4.10.10012221630390.20456-100000@gator1.brazosport.cc.tx.us>   Please help.I Please unsubscibe me.  I have sent many requests to Info-VAX@Mvb.Saic.Com J with this request and have not been successful. I will be gone for severalE weeks and there will be too many messages to deal with when I return.c   ------------------------------  # Date: Fri, 22 Dec 2000 19:56:40 GMTl* From: Alan E. Feldman <alan48@my-deja.com>F Subject: Re: NLA0: the null device - can VMS have other default names?) Message-ID: <920blm$oln$1@nnrp1.deja.com>b  ' In article <3a431bcb$1@cpns1.saic.com>,S0   "Scott Stark" <hayden.s.stark@saic.com> wrote: > > David J. Dachtera wrote:! > >> AH! I see the confusion now.S > >>A > >> In most cases, "NL:" is taken as being identical to "NLA0:".l >n= > Thank you for the abundant replies, the questions have beenp answered.  TheF > solution is to have the code look for NLA0 and not just "NL" as that would-* > bypass the intended NLPx (print) action.  = So, you're searching code for occurrences of the null device?-  D You need to search for NL, NLA, NL0, NLA0, and all four with a colonE attached. This is because the default controller is A and the defaultaE number is 0, so either or both can be missing and it's still the sameh device.x   > H > BTW, VMS on-line help usually has the answers but I could not find anyF > references to the null device (NLA0:) in there (did find in VMS FAQs andrH > didn't look in documentation).  Thought I'd solicit here and got ample  < It's mentioned in the documentation as SPAWN/INPUT=NL: underE SPAWN/NOWAIT in the DCL Dictionary and described more fully somewhere   in the user's manual, I believe.  
 > replies. > Problem resolved.i   OK.h   [...]    --F NOTE: If you wish to e-mail me, please do NOT use the deja address. ItE is broken. Instead, use one of the addresses below, removing the long. wrong part first. Thanks.o   Disclaimer: JMHO Alan E. Feldman  &-)+ w: afeldman@gfigroup.ButItSaidItPrinted.coms5 h: alan48@dellnet.YouCantBelieveEverythingYouRead.coma     Sent via Deja.comm http://www.deja.com/   ------------------------------  # Date: Fri, 22 Dec 2000 22:00:08 GMTt7 From: moroney@world.std.spaamtrap.com (Michael Moroney)rF Subject: Re: NLA0: the null device - can VMS have other default names?& Message-ID: <G5zp48.79y@world.std.com>  * Terry Kennedy <terry@gate.tmk.com> writes:  I >  2) Nothing would prevent someone from doing a SYSGEN CONNECT / etc. to > >     make a new device called NLB0:, NLQ1234:, or even FOO99:  > I _vaguely_ remember playing around on a vax and configuring aF NLB0: device.  If I remember correctly the system crashed when I tried" accessing it.  This was years ago.   -Miked   ------------------------------  % Date: Fri, 22 Dec 2000 23:44:57 -0500t, From: Howard S Shubs <hshubs@mindspring.com>F Subject: Re: NLA0: the null device - can VMS have other default names?> Message-ID: <hshubs-717FC9.23445722122000@news.mindspring.com>  B In article <3A442BD1.E3A2F432@earthlink.net>, "David J. Dachtera" $ <djesys.nospam@earthlink.net> wrote:  F >Also in Multinet, NTY devices are terminal class devices, although byG >the more parochial definition they should be "NT" class devices on the F >25th ("Y") controller having unit numbers between 0 and 9999 (0 being! >the template device, naturally).   4 Naturally.  Who gets the check?  Naturally.  (sorry)    F >You'll probably find UCX/TCPware TNAxxxx: devices more platable: "TN"@ >(Telnet? "Terminal, Network"?) class devices on the first ("A")A >controller with unit numbers between 0 and 9999. Unit zero(0) is A >typically the template device. These are terminal-class devices.0  O -That- is what I'm familiar with.  I've used Wollongong too, but that's waaaay s back.d  O Waitaminut... Multinet is from Process Software, yes?   Maybe I -did- use them nP several years ago... and found their usage broken, though the software worked.   It's been a long time. -- c Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"   ------------------------------  % Date: Fri, 22 Dec 2000 20:17:39 -0000e- From: wspencer@ap.nospam.org (Warren Spencer)i* Subject: Re: Problem with linking C++ code/ Message-ID: <t47dn3hl23ka3b@news.supernews.com>s  * seibel_r@ociweb.com (Rich Seibel) wrote in1 <slrn93vca2.pep.seibel_r@localhost.localdomain>:     >aI >I am trying to port a rather large open source middleware package calledg: >ACE/TAO to VMS and I am having a problem with the linker. >"  
 << snip >>  I Sorry you got delayed responses.  The holidays might be interfering with  F the usual "snappy" response times most people experience on this list.  I I'm not a C++ specialist, but I can ask some of the basic questions that hJ seem to jump out.  Not knowing how signficant your OpenVMS experience is, , please forgive it these items are too basic.  # - The linker is whining about this:n    9 %LINK-I-DATMISMCH, creation date of  7-FEB-2000 17:40 in c, >shareable image GNU:[LIB]DECC$SHR_V71.EXE;1C >        differs from date of 29-JUL-1999 00:17 in shareable image p* >library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1  I Any chance you have a broken installation of C++ or C?  Might want to re-mJ run the Installation Verification Procedure (IVP) for the products to see  if they identify any issues.   Another item on your list is:   + > I know that the module is in the library nC >because LIBRARY tells me so and will show me the symbols.  Is this ! >a known problem with the linker?   A Don't know if it's a problem with the linker.  Have you done a $ nL LIBRARY/REPLACE to ensure the module in the library is up to date?  Also, a I $ LIBRARY/LIST/NAMES on the library should show you all symbols that the u$ linker can resolve from the library.  H There's also /PREFIX qualifier on the C compiler (don't know about c++) G that controls symbol prefixing of system-related global names.  Just a a
 thought...   ws   -- 23 << What if there were no hypothetical questions? >>-   Warren Spencer Senior Software Engineer The Associated Press  ? ** My employer does not necessarily agree with my statements **p   ------------------------------  # Date: Fri, 22 Dec 2000 20:51:44 GMTS2 From: seibel_r@localhost.localdomain (Rich Seibel)* Subject: Re: Problem with linking C++ code; Message-ID: <slrn947fms.vgn.seibel_r@localhost.localdomain>   = On Fri, 22 Dec 2000 11:53:08 GMT, xx <xxx@hotmail.com> wrote:oM >If using cxxlink does not solve the problem *and* you have a reasonable sizeiM >reproducer, feel free to send email to compaq_cxx.bug@compaq.com and we wille >get your question answered. >S >Duane Smith >Compaq C++ Engineering Manageri >s >tJ My current working hypothesis is that the program I am building referencesH something in a library.  One or more of the objects files in the libraryF reference templates in the template repository.  The templates need an5 object file in the library, but this does not happen.r  9 I've included a small extract from my original post here:   I I am using the GNV tools, bash, gmake, and wrappers for the CXX, CXXLINK, D and LIBRARY programs.  These are working successfully to allow me to start to compile the system.  B The platform is and Alpha runing OpenVMS.  The compiler identifies7 itself as Compaq C++ V6.2-035 for OpenVMS Alpha V7.1-2.p  a
 Details -- The link step is: 
 $cxxlink -  /repository=([.cxx_repository] -6 ,SYS$SYSDEVICE:[TAO.ACE_WRAPPERS.ACE.CXX_REPOSITORY] - ,[.CXX_REPOSITORY] - ) -e /exec=ARGV_TEST. - link00ea30.opt/opt where the opt file is: [.VMS_OBJ]ARGV_TEST.O 0 SYS$SYSDEVICE:[TAO.ACE_WRAPPERS.ACE]LIBACE.A/lib< The oupput from the linker is long, only an exerpt is shown:$ %LINK-W-WRNERS, compilation warningsB         in module SV_SEMAPHORE_SIMPLE file SYS$SYSDEVICE:[TAO.ACE_ WRAPPERS.ACE]LIBACE.A;1lB %LINK-I-DATMISMCH, creation date of  7-FEB-2000 17:40 in shareable! image GNU:[LIB]DECC$SHR_V71.EXE;1rA         differs from date of 29-JUL-1999 00:17 in shareable imageo) library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1VB %LINK-I-DATMISMCH, creation date of 26-JUL-1999 16:17 in shareable* image SYS$COMMON:[SYSLIB]PTHREAD$RTL.EXE;1A         differs from date of  7-DEC-1998 15:24 in shareable image ) library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1c' %LINK-W-NUDFSYMS, 13 undefined symbols:e= %LINK-I-UDFSYM,         char *ACE_NS_String::char_rep() consteI %LINK-I-UDFSYM,         ACE_NS_String::ACE_NS_String(const ACE_WString &)rI %LINK-I-UDFSYM,         ACE_NS_Internal::ACE_NS_Internal(ACE_NS_String &,n constchar *) [snip]F %LINK-W-USEUNDEF, undefined symbol const char *ACE_NS_Internal::type()
 referenced)         in psect $LINK$ offset %X00000190FJ         in module CXX$LSTNMENTRES67ACLCLNM273SJTL file SYS$SYSDEVICE:[TAO.E ACE_WRAPPERS.ACE.CXX_REPOSITORY]CXX$LSTNMENTRES67ACLCLNM273SJTL.OBJ;2iE %LINK-W-USEUNDEF, undefined symbol ACE_NS_String::ACE_NS_String(conste ACE_WString &) referenced )         in psect $LINK$ offset %X000001B0rJ         in module CXX$LSTNMENTRES67ACLCLNM273SJTL file SYS$SYSDEVICE:[TAO.E ACE_WRAPPERS.ACE.CXX_REPOSITORY]CXX$LSTNMENTRES67ACLCLNM273SJTL.OBJ;2s [snip]F The original object module does not reference the repository above, itC did reference the repository in the current directory, but this didrC not result in undefined symbols.  The repository objects above were:G referenced in the library (there is only one) which also has the object0I file which contains the missing symbols.  I did try repeating the libraryr% but that did not make any difference.0  K Is it not possible to have a lib reference templates that use the same lib?s     -- BD --------------------------------------------------------------------D Rich Seibel, Software Engineer                 (314)579-0066 ext 220D Object Computing, Inc.                           seibel_r@ociweb.comD Need ACE training?                      See http://www.theaceorb.comD --------------------------------------------------------------------   ------------------------------  # Date: Fri, 22 Dec 2000 22:43:59 GMTM2 From: seibel_r@localhost.localdomain (Rich Seibel)* Subject: Re: Problem with linking C++ code; Message-ID: <slrn947m99.vt9.seibel_r@localhost.localdomain>t  L On Fri, 22 Dec 2000 20:17:39 -0000, Warren Spencer <wspencer@ap.nospam.org>  wrote:+ >seibel_r@ociweb.com (Rich Seibel) wrote ins2 ><slrn93vca2.pep.seibel_r@localhost.localdomain>:  >  >>J >>I am trying to port a rather large open source middleware package called; >>ACE/TAO to VMS and I am having a problem with the linker.  >> >c ><< snip >>n > J >Sorry you got delayed responses.  The holidays might be interfering with G >the usual "snappy" response times most people experience on this list.. >>J >I'm not a C++ specialist, but I can ask some of the basic questions that K >seem to jump out.  Not knowing how signficant your OpenVMS experience is, <- >please forgive it these items are too basic.s >n$ >- The linker is whining about this: >  >E: >%LINK-I-DATMISMCH, creation date of  7-FEB-2000 17:40 in - >>shareable image GNU:[LIB]DECC$SHR_V71.EXE;1tD >>        differs from date of 29-JUL-1999 00:17 in shareable image + >>library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1r >yJ >Any chance you have a broken installation of C++ or C?  Might want to re-K >run the Installation Verification Procedure (IVP) for the products to see   >if they identify any issues.s >iF I'll need see about this one.  So far it hasn't seems to be a problem.F I can create usable, executable programs.  In fact, even this one willE work if I specifically include the missing object module in the link.-   >Another item on your list is: >:, >> I know that the module is in the library D >>because LIBRARY tells me so and will show me the symbols.  Is this" >>a known problem with the linker? >-B >Don't know if it's a problem with the linker.  Have you done a $ M >LIBRARY/REPLACE to ensure the module in the library is up to date?  Also, a e YesGJ >$ LIBRARY/LIST/NAMES on the library should show you all symbols that the % >linker can resolve from the library.o9 It does show that the missing symbols are in the library.  >oI >There's also /PREFIX qualifier on the C compiler (don't know about c++)  H >that controls symbol prefixing of system-related global names.  Just a  >thought...oI Looked at this one, it seems to only apply to system-related symbols, therG ones in question are in my library.  I don't have any issue with systemd( related symbols.  They are all resolved. >  >ws' >a Thanks for your response.a     -- aD --------------------------------------------------------------------D Rich Seibel, Software Engineer                 (314)579-0066 ext 220D Object Computing, Inc.                           seibel_r@ociweb.comD Need ACE training?                      See http://www.theaceorb.comD --------------------------------------------------------------------   ------------------------------  + Date: Fri, 22 Dec 2000 10:34:59 -0600 (CST)t2 From: Carol Lee Poush <cpoush@brazosport.cc.tx.us> Subject: removepR Message-ID: <Pine.OSF.4.10.10012221034440.20227-100000@gator1.brazosport.cc.tx.us>   remove   ------------------------------  % Date: Fri, 22 Dec 2000 16:04:46 -0500g- From: "Richard D. Piccard" <piccard@ohio.edu>o< Subject: Re: Rules of Flight -- was DSNlink for OpenVMS v3.0( Message-ID: <3A43C1DD.9BC59DF1@ohio.edu>  B Thank you.  Off-topic, but a nice way to start Christmas vacation.                           RDPd     Peter Weaver wrote:v  : > "Richard D. Piccard" <piccard@ohio.edu> wrote in message$ > news:3A43B4C4.12B51955@ohio.edu...F > > Are the "rules of the air" collected in one place, or are we going > to@ > > have to wait for them to emerge, one at a time, in your sig? > >I >vF > I have 24 that were sent to me the other week that I plan on postingD > with each message. But I just took a look with AltaVista and foundE > this list - http://users2.50megs.com/ransompark/page11.html. So you ? > haev your choice; wait for my postings or check out the site.e >2D > I just also found it at http://www.gcfl.net/archive/20000627.html,G > there they say that this list was published in the June 2000 issue ofmE > Australian Aviation Magazine but I have seen most of these rules ineC > one form or another in various magazines before. One missing from F > these lists that is usually there is "The FAA believes that when theB > aircraft paperwork equals the weight of the aircraft ... it willG > fly." I guess the Australian Aviation group is not as bureaucratic asr
 > the FAA. >a6 > If anyone cares I found the Annotated High Flight at0 > http://idt.net/~rwbutler/Visions/HighFly2.htm. >  > -- >   RULES OF THE AIR >   -----------------.= >   #6. The propeller is just a big fan in front of the planes; >       used to keep the pilot cool. When it stops, you canV0 >       actually watch the pilot start sweating.   --B ==================================================================B Dick Piccard                           Academic Technology ManagerB piccard@ohio.edu                                 Computer ServicesB http://oak.cats.ohiou.edu/~piccard/                Ohio University   ------------------------------   Date: 22 Dec 2000 19:09:31 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)" Subject: Re: Segmented keys in RMS6 Message-ID: <9208tb$j3t$1@mailint03.im.hou.compaq.com>  { In article <99CDEDA1726CD4118F4A00D0B788429703617D@pdns.sema.co.in>, Bhaskar Sengupta <Bhaskar.Sengupta@sema.co.in> writes:E  B :	I have an indexed file with a primary key of 39 bytes which is aM :structure of 9 members. The rest of the record is filler. I want to retreiveiK :data based on one member of the primary key. Which means that I might haveh* :duplicate key ( because it is a member ).  I   There is no "member" of the primary key, there is only the primary key.hG   The primary key might have one or more segments, but segmentation is oE   not particularly relevent an indexed file access via key.  You can fI   partial-match based on the primary key, or you can declare one or more u:   additional (and potentially overlapping) secondary keys.  C :	I have in my user program declared a segmented primary key and am-L :opening the file with the necessary segment of the key. While reading, I amH :again using the segmented key to do random sys$find and then sequentialI :sys$get with the RAB$V_LIM option set. I am supposed to get a RMS_OK_LIM02 :once the duplication of the segmentd part stops.   A   Please ensure that the correct syntax to use in your particular C   program is RAB$V_LIM (the bit offset) and not RAB$M_LIM (the bit v   mask).  B   Can you post a reproducer (example) that demonstrates the error?  @   When posting, a small source code reproducer of these sorts ofC   problems can be very useful.  In this case, we probably also needeB   something that creates the data file.  It need not be as complex>   as your segmented key, as I expect you could demonstrate the@   problem using a non-segmented string key.  (The inclusion of a@   concise reproducer is also a sequence that typically forces a B   systematically approach and review of the problem -- I've found B   more than a few errors in my own code over the years using this    particular technique.)  A   The OpenVMS version, platform, and ECO level are also regularlyy3   useful details to include when posting questions.s  C   Attached is an example of a concise reproducer -- this reproducerhC   was created in response to a report of a problem with privileges  @   and privilege handling with executable and shareable images...A   If you can demonstrate a problem with something like this, thenxD   it is far easier and far quicker for folks to find and to help youD   address the cause.  (Or -- if it is a bug in OpenVMS -- to report "   it to Compaq, and get it fixed.)  G   The attached example is probably more involved than you really want, iE   but this example did (does) clearly demonstrate the particular (andi@   expected) operation of OpenVMS in the reported problem area...8   (nb: The example code largely lacks error handling...)  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com      
 $ set noon. $ if f$search("sys$share:zzzshr.exe") .nes. "" $ then6 $   known = f$file_att("sys$share:zzzshr.exe","known") $   if known $   then) $     install delete sys$share:zzzshr.exet	 $   endifj! $   delete sys$share:zzzshr.exe;*- $ endifa- $ if f$search("sys$scratch:zzz.exe") .nes. ""e $ then5 $   known = f$file_att("sys$scratch:zzz.exe","known"): $   if known $   then( $     install delete sys$scratch:zzz.exe	 $   endif@  $   delete sys$scratch:zzz.exe;* $ endif.( $ cc zzz/def=ZZZ/obj=sys$scratch:zzz.obj. $ cc zzz/def=ZZZSHR/obj=sys$scratch:zzzshr.obj $ goto 'f$getsyi("ARCH_NAME")' $Alpha:: $ link/notrace/nodebug -; sys$scratch:zzzshr/share=sys$share:zzzshr.exe,sys$input/opti  symbol_vector=(ChkPrv=procedure) gsmatch=lequal,1,0 identification="zzzshr v1.0"
 $ goto commona $VAX: / $ macro sys$input/object=sys$scratch:zzzxfr.obj %   .title $$$xfrvec transfer vector(s)t   .ident /zzzxfr v1.0/,   .psect $$$xfrvec,exe,shr,nowrt,rd,pic,quad   .macro xfrvec entrypoint
   .align quada   .transfer entrypoint   .external entrypoint   .mask entrypoint   jmp l^entrypoint+2   .endm3   xfrvec ChkPrv    .end $ link/notrace/nodebug -N sys$scratch:zzzshr,sys$scratch:zzzxfr/share=sys$share:zzzshr.exe,sys$input/opt cluster=$$$xfrvec  collect=$$$xfrvec,$$$xfrvecn gsmatch=lequal,1,0 identification="zzzshr v1.0"
 $ goto commonr $Common: $ link/notrace/nodebug -8 /execu=sys$scratch:zzz.exe sys$scratch:zzz,sys$input/opt sys$share:zzzshr/share $N $rF $! SYSLCK disabled, not installed, not installed with SYSLCK privilege $   $ set process/privilege=nosyslck $ run sys$scratch:zzzi $ E $! SYSLCK enabled, not installed, not installed with SYSLCK privilegen $z $ set process/privilege=syslck $ run sys$scratch:zzze  $ set process/privilege=nosyslck! $ install create sys$share:zzzshrd $lB $! SYSLCK disabled, installed, not installed with SYSLCK privilege $r $ run sys$scratch:zzzs  $ install create sys$scratch:zzz $ run sys$scratch:zzzu $t> $! SYSLCK disabled, installed, installed with SYSLCK privilege $t- $ install replace sys$scratch:zzz/priv=syslckr $ run sys$scratch:zzze $u $! clean up... $"  $ install delete sys$scratch:zzz! $ install delete sys$share:zzzshr  $ delete sys$scratch:zzz.exe;* $ delete sys$share:zzzshr.exe;*R $P $ exit  
         --   /*	 //  zzz.cD */ #include <prvdef.h>p #include <ssdef.h> #include <starlet.h> #include <stdio.h> #include <stdlib.h>r
 #ifdef ZZZ main()   {    int RetStat, ChkPrv();   RetStat = ChkPrv();s   return 1;a   }c #endif
 #ifdef ZZZSHRt int ChkPrv()   {n   int RetStat;-   int PrvQWIn[2] = {0,0}, PrvQWOut[2]= {0,0}; 2   RetStat = sys$setprv( 0, PrvQWIn, 0, PrvQWOut );#   if ( PrvQWOut[0] & PRV$M_SYSLCK )      printf("SYSLCK enabled\n");h   else      printf("SYSLCK disabled\n");   return RetStat;h   }i #endif   ------------------------------    Date: 22 Dec 2000 15:01:35 -0500* From: young_r@eisner.decus.org (Rob Young)F Subject: Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster+ Message-ID: <Zc+N6rk2IiBy@eisner.decus.org>   r In article <WfO06.23625$1t.810026@typhoon.ne.mediaone.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes:   > E > That cabinet might be, ummm, an inch or two taller than the currentnH > GS-cabinet. And if it were me, why, I'd consider a color change. Let'sN > see... pink? Nope. Purple? No way, that's Pauline Nist's color of choice andJ > she's the Himalaya maven. Black... carbon black, as in iPAQ Black? Yeah, > THAT's the ticket... >  	 ; 	That stinks.  Looks like an SP frame then.  If it were me,w> 	I would make 'em candy apple red and add bright yellow flames9 	along the bottom.  It would communicate speed to the CIOe= 	and CEO and that is the message you would want them to leaveo< 	the datacenter tour with.  Of course half the CIOs and CEOs? 	would turn their noses up and remark: "they can't be serious." ; 	I'd tell them to come back when they get a sense of humor.p   				Rob    ------------------------------  # Date: Fri, 22 Dec 2000 19:50:14 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>B Subject: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster; Message-ID: <WfO06.23625$1t.810026@typhoon.ne.mediaone.net>-  7 "Rob Young" <young_r@eisner.decus.org> wrote in message1% news:+BUX$wreIwRY@eisner.decus.org...l   <snip> >S< > You bet.  But maybe if EV69 is real, there is a multi-year< > upgrade path for current Wildfire owners and they actually3 > get cheaper boards and memory than Marvel owners?o  I Sure, there's a multi-year upgrade path for the current GS-Series. May bez some EV69-EV7 overlap.  G If I was responsible for a large data center running GS-boxen, I'd justiH cluster my incumbent GS machines with Marvels anyhow. I suspect a fairly7 high percentage of the GS base is clustered as it is...i  	 > Perhapsc8 > this keeps the lawyers at bay if they extend them out?  / I meant lawyers only in regard to the WildName.l  
 > Speaking? > of lawyers... is there anyone in the world actually expectingeC > to make revenues off Itanium before the end of next year?  If so, @ > were they promised any revs this year?  Perhaps with all these? > smart lawyers current Wildfire owners have some nice slipperye4 > timelines and promises as Itanium wanna-be owners? >h  F CPQ generally is pretty careful when it comes to making promises aboutG future deliverables. I haven't bought any GS-boxen, but I haven't heardkK anything from owners which would lead me to believe they're being BSed. The.L CPQ PIDs on AlphaServer futures doubtlessly explain things pretty well. NoteG that in the public GS-Series presentations the next CPU increment is 48 K whilst Marvel is, ahem, "rumoured" to be a 64-CPU system. Well, an EV7-izediL GS320 cabinet will be able to hold 48 CPUs. This would lead one to speculateF that a brand spanking new EV7 GS640 Marvel will come in a new cabinet.  C That cabinet might be, ummm, an inch or two taller than the currentnF GS-cabinet. And if it were me, why, I'd consider a color change. Let'sL see... pink? Nope. Purple? No way, that's Pauline Nist's color of choice andH she's the Himalaya maven. Black... carbon black, as in iPAQ Black? Yeah, THAT's the ticket...   matcoH   ------------------------------    Date: 22 Dec 2000 14:56:17 -0500* From: young_r@eisner.decus.org (Rob Young)F Subject: Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster+ Message-ID: <uwrJIf7VRJoH@eisner.decus.org>e  r In article <WfO06.23625$1t.810026@typhoon.ne.mediaone.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes: > 9 > "Rob Young" <young_r@eisner.decus.org> wrote in message-' > news:+BUX$wreIwRY@eisner.decus.org...A >  > <snip> >>= >> You bet.  But maybe if EV69 is real, there is a multi-year = >> upgrade path for current Wildfire owners and they actuallyI4 >> get cheaper boards and memory than Marvel owners? > K > Sure, there's a multi-year upgrade path for the current GS-Series. May be_ > some EV69-EV7 overlap. > I > If I was responsible for a large data center running GS-boxen, I'd justlJ > cluster my incumbent GS machines with Marvels anyhow. I suspect a fairly9 > high percentage of the GS base is clustered as it is...i > 
 >> Perhaps9 >> this keeps the lawyers at bay if they extend them out?  > 1 > I meant lawyers only in regard to the WildName.b  ( 	Ooops.. way out of context on my end :(   				Robo   ------------------------------  % Date: Fri, 22 Dec 2000 16:28:40 -0500h+ From: "John Gemignani, Jr." <john@ossc.net> F Subject: Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster+ Message-ID: <3a43c773$1@newsfeed.vitts.com>t  K Ship them in traditional colors but put the red and yellow flameware on the-. packaging.  You'll be able to see them coming.   -John     7 "Rob Young" <young_r@eisner.decus.org> wrote in messagee% news:Zc+N6rk2IiBy@eisner.decus.org... G > In article <WfO06.23625$1t.810026@typhoon.ne.mediaone.net>, "Terry C. , Shannon" <terryshannon@mediaone.net> writes: >- > >-G > > That cabinet might be, ummm, an inch or two taller than the current-J > > GS-cabinet. And if it were me, why, I'd consider a color change. Let'sL > > see... pink? Nope. Purple? No way, that's Pauline Nist's color of choice andrL > > she's the Himalaya maven. Black... carbon black, as in iPAQ Black? Yeah, > > THAT's the ticket... > >a >o< > That stinks.  Looks like an SP frame then.  If it were me,? > I would make 'em candy apple red and add bright yellow flames>: > along the bottom.  It would communicate speed to the CIO> > and CEO and that is the message you would want them to leave= > the datacenter tour with.  Of course half the CIOs and CEOss@ > would turn their noses up and remark: "they can't be serious."< > I'd tell them to come back when they get a sense of humor. >m > RobC >s   ------------------------------  % Date: Fri, 22 Dec 2000 22:44:58 -0000u4 From: "John D. Peedle" <john@peedle.freeserve.co.uk>F Subject: Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster. Message-ID: <920lgf$63t$1@news6.svr.pol.co.uk>  F And add a whole range of flashing lights - that *really* impresses the technically challenged   John D. Peedle  6 "John Gemignani, Jr." <john@ossc.net> wrote in message% news:3a43c773$1@newsfeed.vitts.com... I > Ship them in traditional colors but put the red and yellow flameware on  thet0 > packaging.  You'll be able to see them coming. >p > -Johno >e > 9 > "Rob Young" <young_r@eisner.decus.org> wrote in messages' > news:Zc+N6rk2IiBy@eisner.decus.org...bI > > In article <WfO06.23625$1t.810026@typhoon.ne.mediaone.net>, "Terry C.l. > Shannon" <terryshannon@mediaone.net> writes: > >o > > > I > > > That cabinet might be, ummm, an inch or two taller than the current L > > > GS-cabinet. And if it were me, why, I'd consider a color change. Let'sG > > > see... pink? Nope. Purple? No way, that's Pauline Nist's color of  choice > andeH > > > she's the Himalaya maven. Black... carbon black, as in iPAQ Black? Yeah,y > > > THAT's the ticket... > > >$ > >A> > > That stinks.  Looks like an SP frame then.  If it were me,A > > I would make 'em candy apple red and add bright yellow flamesi< > > along the bottom.  It would communicate speed to the CIO@ > > and CEO and that is the message you would want them to leave? > > the datacenter tour with.  Of course half the CIOs and CEOsoB > > would turn their noses up and remark: "they can't be serious."> > > I'd tell them to come back when they get a sense of humor. > >n > > Robi > >s >d >e   ------------------------------  % Date: Fri, 22 Dec 2000 19:37:00 -0500n# From: Paul DeMone <pdemone@igs.net>-F Subject: Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster' Message-ID: <3A43F3AC.CA804BA9@igs.net>2   "John D. Peedle" wrote:  > H > And add a whole range of flashing lights - that *really* impresses the > technically challenged  A No you need a 1/2" reel to reel upright tape drive to do that :-)-   --D Paul W. DeMone       The 801 experiment SPARCed an ARMs race of EPICE Kanata, Ontario      proportions to put more PRECISION and POWER intouG demone@mosaid.com    architectures with MIPSed results but ALPHA's wellt$ pdemone@igs.net      that ends well.   ------------------------------  % Date: Fri, 22 Dec 2000 12:27:18 -0800r! From: Shane.F.Smith@Healthnet.comhF Subject: Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun ClusterD Message-ID: <OFB949A428.80B417EC-ON882569BD.006F2499@foundation.com>  # I know I'm going to regret this.....  4 http://www.virtualhideout.net/cool_case/page24.shtml  H This is a gallery of customised computer cases, mostly PCs. Some of themJ look really good. Second from the bottom on that particular page, you willI find one of mine. It's a small, bright red LANparty box. If you're wonder K about the nickname, it's one of my Quake handles. (This is the only place I  post using my real name.)i   Shanee          > young_r@eisner.decus.org (Rob Young) on 12/22/2000 12:01:35 PM   To:   Info-VAX@Mvb.Saic.Com/ cc:1  G Subject:  Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Clusteri    E In article <WfO06.23625$1t.810026@typhoon.ne.mediaone.net>, "Terry C.m, Shannon" <terryshannon@mediaone.net> writes:   >nE > That cabinet might be, ummm, an inch or two taller than the currentnH > GS-cabinet. And if it were me, why, I'd consider a color change. Let'sJ > see... pink? Nope. Purple? No way, that's Pauline Nist's color of choice andaJ > she's the Himalaya maven. Black... carbon black, as in iPAQ Black? Yeah, > THAT's the ticket... >t  ?      That stinks.  Looks like an SP frame then.  If it were me, B      I would make 'em candy apple red and add bright yellow flames=      along the bottom.  It would communicate speed to the CIOAA      and CEO and that is the message you would want them to leave @      the datacenter tour with.  Of course half the CIOs and CEOsC      would turn their noses up and remark: "they can't be serious." ?      I'd tell them to come back when they get a sense of humor.=                       Rob    ------------------------------  # Date: Sat, 23 Dec 2000 01:04:43 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>F Subject: Re: Simply Marvelous (was Re: DS20 vs DS20E. Was: Sun Cluster; Message-ID: <LSS06.25243$1t.839399@typhoon.ne.mediaone.net>f  0 "Paul DeMone" <pdemone@igs.net> wrote in message! news:3A43F3AC.CA804BA9@igs.net...D >9 >t > "John D. Peedle" wrote:m > >oJ > > And add a whole range of flashing lights - that *really* impresses the > > technically challenged >tC > No you need a 1/2" reel to reel upright tape drive to do that :-)  >3  L Yeah, well, a TS-11 running the UETP program does, er, did a pretty good jobC with the lights. Trouble is, you need to go back to the days of thecL PDP/11-50 or one o' the IBM 360s to get a decent set of front panel lites...   ------------------------------  % Date: Fri, 22 Dec 2000 22:24:44 +0100h# From: "Dick" <d.vd.vlugt@hccnet.nl>s Subject: Re: SLS Questions) Message-ID: <920gqo$6c1$1@news.hccnet.nl>f  L At our site we redefined 'a 24 hour day' for SLS to be from 17:00 till 16:59
 the next day.eJ I do not know (at this moment) how that is done, but after Christmas I can easely find it out.gJ Hope this will give you a hint, otherwise mail me and I will reply (in due time) with an answer.e     --	 ... Di-)k     http://home.hccnet.nl/d.vd.vlugt http://join.at/gor.alkmaar http://come.to/troubadour   0 <bawilhelm@my-deja.com> schreef in berichtnieuws 92001d$ekc$1@nnrp1.deja.com...F > We are using SLS for our system backups.  We run a series of backupsJ > each night with a final incremental or image depending on the night.  InF > SLS if you run the same backup on the same day it will send an OPCOM? > message and ask if you want to REDO, QUIT or SKIP the backup.d >eH > The problem that has been occasionally occurring is if for some reasonG > the last backup of the previous night occurred after midnight and thenJ > last backup of the current day starts before midnight, you have to reply% > to redo each saveset in the backup.t >gI > There is a parameter UNATTENDED_BACKUPS that can be set that will forcepI > the backup to proceed without operator intervention, but it has a nastyvI > side effect over automatically overwriting the label of the tape.  This H > is a problem if you accidentally put in the wrong tape. (This seems to > happen fairly frequently). >dF > Does anyone have any suggestions on how to get around this?  We have@ > tried creating multiple tape pools for some of the backups but& > inevitably the problem still occurs. >s > Thanks >v > Brent Wilhelmt > Salisbury State University >. >  > Sent via Deja.coma > http://www.deja.com/   ------------------------------   Date: 22 DEC 2000 19:14:43 GMT4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher)+ Subject: Static DHCP leases for Macintoshest6 Message-ID: <22DEC00.19144300@thuria.waisman.wisc.edu>  D We've successfully used the TCPIP V5.0A DHCP server to assign staticC leases to Windows PC's. We've never been able to have this work foro Macintosh clients however.   Detail:e  O To setup a static lease (as opposed to obtaining a dynamic lease from a pool of-L IP numbers) the MAC address of the client needs to be entered as per section9 7.2.4.3 of "TCP/IP Services for OpenVMS Management" (see:mX http://www.openvms.compaq.com:8000/72final/6526/6526profile_010.html#_stc_ip_addr_dhcp).N For Windows PC's we prefix the MAC address with "01" and set the type to 0 andM length to 7. This works as stated. For Macintosh clients we've been unable to N choose a MAC address that works. Does anyone know the correct format, type and0 length of the MAC address for Macintosh clients?  J We also have the server parameter "Restrict to Known MAC Addresses" set toJ "true". This requires MAC address to be "Preloaded" before the server willO respond to the client. For PC's we set this to the raw MAC address (no prefix).A   ------------------------------   Date: 22 Dec 2000 19:25:00 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: system disk space6 Message-ID: <9209qc$j96$1@mailint03.im.hou.compaq.com>  [ In article <3A42A823.A34E5A44@boeing.com>, Jim Binder <james.binder@pss.boeing.com> writes:/E :I've inherited an Alpha 4100 w/openVMS 7.2 installed.  We do not addrJ :software yet, the system disk is getting smaller.  Is there any location > :I should look for logs or temp files which should be deleted?  
   Start with:   K http://www.openvms.compaq.com:8000/72final/6017/6017pro_043.html#6017backup:  4   ...in case you make a mistake with the deletion...  H   Periodically recreating and then purging the accounting database, the I   security audit database, the operator log, and various other log files sJ   can be the most common techniques -- most folks configure the system to J   reset and purge these files automatically.  (For detailed suggestions onF   how to achieve this, please see SYS$STARTUP:SYSTARTUP_VMS.TEMPLATE.)  !   Also see some of the following:v  M http://www.openvms.compaq.com:8000/72final/6017/6017pro_073.html#index_x_4320/N http://www.openvms.compaq.com:8000/72final/6017/6017pro_036.html#disk_mgmt_secL http://www.openvms.compaq.com:8000/72final/6017/6017pro_037.html#purging_secM http://www.openvms.compaq.com:8000/72final/6017/6017pro_069.html#index_x_3979   J   Most likely, your application and your users are building up cruft, too.K   As to how to clean that up, well, that needs to be determined and handlede?   locally, or with the assistance of the application vendor(s).e  I   Most importantly, make sure you have a good and restorable BACKUP here. G   This because you plan to delete files, and because you may or may notcG   know if you have a current BACKUP -- one that you can restore in the a.   event of an application or system failure...  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 22 Dec 2000 16:35:44 GMT 2 From: robert_jm_barron@hotmail.com (Robert Barron) Subject: Re: system disk space4 Message-ID: <3a43823a.8911969@news.netvision.net.il>  , On Fri, 22 Dec 2000 01:02:27 GMT, Jim Binder$ <james.binder@pss.boeing.com> wrote:  E >I've inherited an Alpha 4100 w/openVMS 7.2 installed.  We do not adds	 >software+I >yet, the system disk is getting smaller.  Is there any location I shoulde >lookn0 >for logs or temp files which should be deleted? >> >Thanks a lot.   I like using this one.... $ DIR [000000...]*.* /SIN /DATE=MODIF /SIZ=ALL  ? This will show you all the files which have been changed  sinces
 yesterday.7 This finds new files and files which have been growing. B The /SIZ=ALL will show you files which are growing even if they're0 still open DIR/SIZ won't show their "true" size.   bye, Robert   ------------------------------  # Date: Fri, 22 Dec 2000 21:32:53 GMTp+ From: Chris Doran <chris_doran@my-deja.com>t Subject: Re: system disk space) Message-ID: <920ha5$t95$1@nnrp1.deja.com>e  6 In article <9209qc$j96$1@mailint03.im.hou.compaq.com>,&   hoffman@xdelta.zko.dec.nospam wrote: > 7 > In article <3A42A823.A34E5A44@boeing.com>, Jim Binderi% <james.binder@pss.boeing.com> writes:nG > :I've inherited an Alpha 4100 w/openVMS 7.2 installed.  We do not add-B > :software yet, the system disk is getting smaller.  Is there any location@ > :I should look for logs or temp files which should be deleted? >a <snip>E >   Periodically recreating and then purging the accounting database,  theYD >   security audit database, the operator log, and various other log filesdA >   can be the most common techniques -- most folks configure thet	 system tou= >   reset and purge these files automatically.  (For detailedc suggestions onH >   how to achieve this, please see SYS$STARTUP:SYSTARTUP_VMS.TEMPLATE.) >...  A For some "VMS weeds" and how to keep them growing, see my post at . http://x53.deja.com/=vz/getdoc.xp?AN=627210543   Chriso         Sent via Deja.comi http://www.deja.com/   ------------------------------    Date: 22 Dec 2000 15:51:39 -0500* From: kuhrt@eisner.decus.org (Marty Kuhrt)2 Subject: Re: System halts when console is shut off+ Message-ID: <yVk$KJGe9rc8@eisner.decus.org>i  f In article <91ts35$lkv$1@newsg3.svr.pol.co.uk>, "John D. Peedle" <john@peedle.freeserve.co.uk> writes:9 > "Marty Kuhrt" <kuhrt@eisner.decus.org> wrote in messagee' > news:JK8dKY$$6CUA@eisner.decus.org...pL >> In article <91rts7$e7s$1@slb2.atl.mindspring.net>, "Steven Shamlian" <not& > dot an at earthling dot net> writes:G >> > This post is in regards to a VAXstation 4000 VLC.  The machine ranoM >> > wonderfully before my graphics monitor randomly died and I had to hit s3  > and'H >> > use a terminal as the system console.  To save power on the machine > (it'shI >> > only a fileserver, so I don't care all that much about what messages  > scrollG >> > across its screen), I turn the console on only when necessary (forlI >> > [re]booting it and the like).  However, with the terminal-as-consoleS > setup,H >> > the VAX halts itself whenever I shut the terminal off (shutting the
 > graphicsJ >> > monitor off before didn't do this, most probably because monitors are > outputM >> > devices and so the VAX doesn't give a damn whether it's doing its job oroJ >> > not).  How do I tell the VAX that it's really OK to keep running when > thetJ >> > terminal shuts off?  Or is there a setting that needs modification on > the  >> > terminal? >>I >> Chances are that the terminal is tossing a Break or Ctrl-P or the like2M >> on the line when you shut it off.  This will cause the VAX to halt becausemE >> the terminal told it to.  If you disconnect the serial line beforer) >> turning it off, this might not happen.< > N > Are you sure about this? In the Unix world, there is a getty process runningG > against the serial port which monitors the port. When the terminal is J > switched off, the (?)DTR line is no longer high so the process dies. SunM > Systems drop out to the the OK prompt if you turn off a serial console too.uI > I'm not sure about Alphas as I have never run one with a serial consolet  H I run most of my Alphas with serial consoles.  I rarely have all of themG connected, since I have only a couple of VTs, and am too lazy to buy a sC switch box.  If I disconnect the console the system doesn't notice.y   ------------------------------  % Date: Fri, 22 Dec 2000 22:40:25 -0000e4 From: "John D. Peedle" <john@peedle.freeserve.co.uk>2 Subject: Re: System halts when console is shut off. Message-ID: <920l7u$5s5$1@news6.svr.pol.co.uk>  7 "Marty Kuhrt" <kuhrt@eisner.decus.org> wrote in messagem% news:yVk$KJGe9rc8@eisner.decus.org...-B > In article <91ts35$lkv$1@newsg3.svr.pol.co.uk>, "John D. Peedle"% <john@peedle.freeserve.co.uk> writes:j; > > "Marty Kuhrt" <kuhrt@eisner.decus.org> wrote in messageu) > > news:JK8dKY$$6CUA@eisner.decus.org...sI > >> In article <91rts7$e7s$1@slb2.atl.mindspring.net>, "Steven Shamlian"a <not( > > dot an at earthling dot net> writes:I > >> > This post is in regards to a VAXstation 4000 VLC.  The machine raneL > >> > wonderfully before my graphics monitor randomly died and I had to hit s3 > > and.J > >> > use a terminal as the system console.  To save power on the machine	 > > (it's K > >> > only a fileserver, so I don't care all that much about what messagesS
 > > scrollI > >> > across its screen), I turn the console on only when necessary (forNK > >> > [re]booting it and the like).  However, with the terminal-as-consoleh
 > > setup,J > >> > the VAX halts itself whenever I shut the terminal off (shutting the > > graphicsL > >> > monitor off before didn't do this, most probably because monitors are
 > > outputL > >> > devices and so the VAX doesn't give a damn whether it's doing its job orL > >> > not).  How do I tell the VAX that it's really OK to keep running when > > theaL > >> > terminal shuts off?  Or is there a setting that needs modification on > > the  > >> > terminal? > >>K > >> Chances are that the terminal is tossing a Break or Ctrl-P or the like G > >> on the line when you shut it off.  This will cause the VAX to halt4 becauseuG > >> the terminal told it to.  If you disconnect the serial line beforel+ > >> turning it off, this might not happen.C > >rH > > Are you sure about this? In the Unix world, there is a getty process runningnI > > against the serial port which monitors the port. When the terminal iseL > > switched off, the (?)DTR line is no longer high so the process dies. SunJ > > Systems drop out to the the OK prompt if you turn off a serial console too.K > > I'm not sure about Alphas as I have never run one with a serial consolep > J > I run most of my Alphas with serial consoles.  I rarely have all of themH > connected, since I have only a couple of VTs, and am too lazy to buy aE > switch box.  If I disconnect the console the system doesn't notice.d  I That's usefule to know since I am about to deploy an increasing number ofo( Alpha with (potentially) serial consoles   ------------------------------  + Date: Fri, 22 Dec 2000 17:18:13 +0100 (CET)p: From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>2 Subject: Re: System halts when console is shut offJ Message-ID: <Pine.LNX.4.21.0012221711340.25656-100000@irys.stanpol.com.pl>  * On Thu, 21 Dec 2000, John D. Peedle wrote:  8 +"Marty Kuhrt" <kuhrt@eisner.decus.org> wrote in message [...]aI +> Chances are that the terminal is tossing a Break or Ctrl-P or the likepM +> on the line when you shut it off.  This will cause the VAX to halt becauseeE +> the terminal told it to.  If you disconnect the serial line before ) +> turning it off, this might not happen.  +'M +Are you sure about this? In the Unix world, there is a getty process running   B  The control is "allowed by the OS" but is a feature - the consoleC port is controlled out_of_control of the OS; communication with thet@ port is done thru console (the code, where starts computer, from ROM/EPROM/flash) driver !F  F +against the serial port which monitors the port. When the terminal isE +switched off, the (?)DTR line is no longer high so the process dies.h  B  But here the *OS* (not process in the OS) is stopped, the control@ goes to console and you can do some work (without pressing RESET= or poer off, of course -:)!) when get expected (b.ex. clustere= quorum loss) or unexpected (loop in code with raised IPL etc)w hang of the system.t  C +                                                               Sun-L +Systems drop out to the the OK prompt if you turn off a serial console too.H +I'm not sure about Alphas as I have never run one with a serial console  >  For sure - you can control the computer out_of the loaded OS.9  And the control is allowed by the console+OS code (b.ex. B DU and VMS allow it, NT doesn't allow, not sure for Linux and BSD)    Regards - Gotfryd   -- cE =====================================================================mF $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=MEo. $!                        GS@stanpol.zabrze.plE =====================================================================    ------------------------------  % Date: Fri, 22 Dec 2000 23:20:35 +010012 From: "Helge Krambeck" <helgekrambeck@t-online.de>) Subject: The Listserver here has gone mad / Message-ID: <920k0m$rgf$05$1@news.t-online.com>3   Hi,8  < I just replied to my own Post (SMTP Server under OpenVMS...)5 Now the Listserver has gone mad and keeps telling me,,3 that i am not allowed to post the same thing again,c0 which I DIDNT DO. Can anybody who is responsible7 for the Listserver please stop this stupid machine ????a  7 Here is the Email that keeps coming every half an hour:a  J Your message  is being returned to  you unprocessed because it  appears to haveI already  been  distributed to  the  INFO-VAX  list.  That  is, a  messageI withL identical text  (but possibly with different  mail headers) has been  posted toH the list recently, either by you or by  someone else. If you have a good reasonF to resend this message to the list (for instance because you have been notifiedG of a hardware failure with loss of  data), please alter the text of the. messageIJ in some way and  resend it to the list. Note that  altering the "Subject:" lineC or adding blank  lines at the top  or bottom of the message  is not4 sufficient;mK you should  instead add a  sentence or  two at the  top explaining why  youu aresK resending the  message, so that the  other subscribers understand why  theyo are.' getting two copies of the same message.i  - ------------------------ Rejected message (71i! lines) --------------------------lJ Received: from portal.east.saic.com (portal.east.saic.com [198.151.13.15])@ by listserv.cc.uga.edu (8.11.0/8.11.0) with SMTP id eBMDoQK39642@ for <info-vax@listserv.uga.edu>; Fri, 22 Dec 2000 08:50:26 -05005 Received: from mclmx.saic.com by portal.east.saic.compL           via smtpd (for listserv.cc.uga.edu [128.192.253.10]) with SMTP; 22 Dec 2000 13:50:26 UTJ Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com; Fri, 22 Dec 2000 05:46:57 -0500a4 Received: from cphub.mail.saic.com ([139.121.95.10])@  by mcl-its-ieg01.mail.saic.com (NAVIEG 2.1 bld 63) with SMTP id M2000122203585600559"  ; Fri, 22 Dec 2000 03:59:21 -0500C Received: from MVB.SAIC.COM by cpmx.mail.saic.com; Thu, 21 Dec 2000o 23:57:40 -08002 From: "Helge Krambeck" <helgekrambeck@t-online.de> X-Newsgroups: comp.os.vmsoL Subject: Re: SMTP Server under OpenVMS AXP V6.2/UCX V4 Character Set Problem% Date: Fri, 22 Dec 2000 01:03:23 +0100  Organization: T-Online	 Lines: 41 / Message-Id: <91u5le$rnq$04$1@news.t-online.com>d Mime-Version: 1.0m, Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bituK X-Trace: news.t-online.com 977443311 04 28410 i7UeM7GSCaGsm 001222 00:01:51t# X-Complaints-To: abuse@t-online.comi( X-Sender: 520097759765-0001@t-dialin.net
 X-Priority: 3  X-MSMail-Priority: Normaln6 X-Newsreader: Microsoft Outlook Express 5.50.4133.24008 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 To: Info-VAX@Mvb.Saic.Comm X-Gateway-Source-Info: USENETt   Hi Jean-Francois,u   Thank you, I restarted smtp  and now it works.c  
 Best regards,    Helge Krambeck    C "Jean-Franois Marchal" <jean-francois.marchal@x9000.fr> schrieb ima4 Newsbeitrag news:91tek9$hd7$1@reader1.imaginet.fr...# > Did you restart smtp after that ?h >  > Jean-Franois Marchalt > X9000 - LYON (FR)i >e >c? > "Helge Krambeck" <helgekrambeck@t-online.de> wrote in message + > news:91td9l$ad9$07$1@news.t-online.com...r > > Hi,  > > . > > I want to configure an Alpha Station/ Open$ > > VMS AXP V6.2 SMTP Server running$ > > under UCX Version 4 to use 8 Bit) > > encoding for Emails sent through thise) > > server. The Problem is, that the SMTPl+ > > Server running on this machine converts % > > all Emails to 7-Bit US-ASCII. How ' > > can I activate 8-Bit transmission ?/* > > Somebody suggested using this command:% > > $ UCX SET CONF SMTP/OPT=EIGHT_BIT@ > > but it doesnt work.C > >a. > > Helge Krambeck (helgekrambeck@t-online.de) > >  > >g >D >2   ------------------------------   End of INFO-VAX 2000.714 ************************