1 INFO-VAX	Wed, 09 May 2001	Volume 2001 : Issue 259       Contents: Re: 7.2-2 availability Re: 7.2-2 availability Re: 7.2-2 availability Re: 7.2-2 availability, ??== Limiting a DCL $SEARCH to newest files.0 Re: ??== Limiting a DCL $SEARCH to newest files.. Re: ABS - backup service from NT to VMS device. Re: ABS - backup service from NT to VMS device. Re: ABS - backup service from NT to VMS device Re: Bisynch  Re: Bisynch  Re: Bisynch  Re: Bisynch  Re: Bisynch  Re: Bisynch  Re: Bisynch  Re: Bisynch ) Re: Conference: CETS-2001 - Conference CD ) Re: Conference: CETS-2001 - Conference CD ) Re: Conference: CETS-2001 - Conference CD ) Re: Conference: CETS-2001 - Conference CD ) Re: Conference: CETS-2001 - Conference CD ) Re: Conference: CETS-2001 - Conference CD = Re: Conference: CETS-2001 - Conference CD - the Microsoft Way = Re: Conference: CETS-2001 - Conference CD - the Microsoft Way  Re: DCL "library"  Re: DCL "library" ; Digital Networks changed the D - I - G - I - T - A - L logo  Digital Networks Press Release Re: Disk re-organisation re: Disk re-organisation5 Re: Effecient I/O  was Re: Pentium 4 Prefetch engine? ) email lists interesting to OpenVMS users?  FYI: Bug in VMS indent Re: FYI: Bug in VMS indent* Re: How to repair corrupted ACCOUNTNG.DAT?- IBM announces MQSeries V5.1 for OpenVMS/Alpha 1 Re: IBM announces MQSeries V5.1 for OpenVMS/Alpha 1 Re: IBM announces MQSeries V5.1 for OpenVMS/Alpha & Re: Microsoft web sites hacked (again)2 Re: mounting 2 disk with the same label in cluster2 Re: mounting 2 disk with the same label in cluster2 Re: mounting 2 disk with the same label in cluster2 Re: mounting 2 disk with the same label in cluster2 Re: mounting 2 disk with the same label in cluster( Mystery of the misreported graphics card& Re: Oracle Parallel Server on OpenVMS?& Re: Oracle Parallel Server on OpenVMS?& Re: Oracle Parallel Server on OpenVMS?& Re: Oracle Parallel Server on OpenVMS?& Re: Oracle Parallel Server on OpenVMS?& Re: Oracle Parallel Server on OpenVMS? Processor Affinity Re: Processor Affinity Re: Processor Affinity+ Programming language usage on VMS systems ? / Re: Programming language usage on VMS systems ? / Re: Programming language usage on VMS systems ? / Re: Programming language usage on VMS systems ? / Re: Programming language usage on VMS systems ? / Re: Programming language usage on VMS systems ?  Re: SYSMAN and SMISERVER Re: SYSMAN and SMISERVER Re: SYSMAN and SMISERVER Re: TCP/IP printing on vms 7.1/ Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / RE: The Internet, Tru64 and other unix variants 7 Re: VAX Just Stops - Not the Usual Suspects - follow up 7 Re: VAX Just Stops - Not the Usual Suspects - follow up 7 Re: VAX Just Stops - Not the Usual Suspects - follow up 7 Re: VAX Just Stops - Not the Usual Suspects - follow up  Re: VAX vs AXP executable  Re: VAX vs AXP executable  Virus Attack' Re: VMS 7.2 BACKUP damaging system disk ' Re: VMS 7.2 BACKUP damaging system disk ' Re: VMS 7.2 BACKUP damaging system disk ' Re: VMS 7.2 BACKUP damaging system disk ' Re: VMS 7.2 BACKUP damaging system disk ' Re: VMS 7.2 BACKUP damaging system disk ' Re: VMS 7.2 BACKUP damaging system disk # Re: VMS 7.3 docs on OpenVMS webite? - Re: What is the best way to erase SCSI disks? - Re: What is the best way to erase SCSI disks? E Re: www.openvms.compaq.com doesn't display correctly in VMS Navigator E Re: www.openvms.compaq.com doesn't display correctly in VMS Navigator E Re: www.openvms.compaq.com doesn't display correctly in VMS Navigator E Re: www.openvms.compaq.com doesn't display correctly in VMS Navigator  Re: Xserver NodeNameE Re: [EVENT] Post =?iso-8859-1?Q?Z=FCrich?= seminar event registration  Re: [OT] Religion   F ----------------------------------------------------------------------  $ Date: Wed, 9 May 2001 09:55:11 +0100* From: "Richard Brodie" <R.Brodie@rl.ac.uk> Subject: Re: 7.2-2 availability , Message-ID: <9db0mo$4mro@newton.cc.rl.ac.uk>  1 "Ed Wilts" <ewilts@mediaone.net> wrote in message 6 news:gg2K6.30009$V6.1255695@typhoon.mn.mediaone.net...  A > Anybody here know when I can expect 7.2-2 to actually roll out?    It says Q3 on the roadmap.   ------------------------------   Date: 9 May 2001 07:33:26 -0500 9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)  Subject: Re: 7.2-2 availability 3 Message-ID: <8Jy1xfNB7CGw@eisner.encompasserve.org>   c In article <gg2K6.30009$V6.1255695@typhoon.mn.mediaone.net>, Ed Wilts <ewilts@mediaone.net> writes: N > I've heard lots of rumors about the availability of 7.2-2, but can't recall J > hearing when it would actually ship or how we can get our hands on it.  K > Alas, the OpenVMS web site is quite silent on the subject...  I've got a  N > bunch of systems to upgrade from 7.2 and 7.1-2, and going straight to 7.2-2 # > would save me a lot of headaches.  > A > Anybody here know when I can expect 7.2-2 to actually roll out?   G Lots of people here will recommend 7.2-1 as being much better than 7.2. G There are no such reports of field experience with 7.2-2.  If I were in ( your position, I would upgrade to 7.2-1.  F Of course, I am _not_ in your position.  In my own position I will tryL the latest with very little hesitation but still have one VAX running 5.3-1.   ------------------------------    Date: 09 May 2001 16:07:54 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>  Subject: Re: 7.2-2 availability H Message-ID: <y4itjawr7p.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  , "Richard Brodie" <R.Brodie@rl.ac.uk> writes:  C > > Anybody here know when I can expect 7.2-2 to actually roll out?  > It says Q3 on the roadmap.  J The ECO to TCPIP 5.1, just out, says it applies to 7.2-2 as well. You make your own conclusions...    	Jan   ------------------------------  # Date: Wed, 09 May 2001 16:00:14 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: 7.2-2 availability 0 Message-ID: <iQdK6.53$fi2.1859@news.cpqcorp.net>  c In article <gg2K6.30009$V6.1255695@typhoon.mn.mediaone.net>, Ed Wilts <ewilts@mediaone.net> writes:   @ :Anybody here know when I can expect 7.2-2 to actually roll out?  J   The current schedule estimate for the OpenVMS Alpha V7.2-2 work targets I   a release from engineering circa Q3CY2001.  Empirical evidence derived  F   from earlier releases indicates an additional four to six weeks for J   replication and distribution will be required after engineering release.  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 09 May 2001 14:29:03 +0200 , From: aus@vim.uni-wuerzburg.de (Hans M. Aus)5 Subject: ??== Limiting a DCL $SEARCH to newest files. D Message-ID: <aus-0905011429030001@wvia48.virologie.uni-wuerzburg.de>  H Is there an easy way to limit the DCL $SEARCH filename.dat;* to only the newest N files?    --  B Cheers, Hans M. Aus, Wuerzburg, Germany,  aus@vim.uni-wuerzburg.de   ------------------------------  # Date: Wed, 09 May 2001 12:46:58 GMT & From: "john nixon" <jnixon@cfl.rr.com>9 Subject: Re: ??== Limiting a DCL $SEARCH to newest files. ? Message-ID: <6%aK6.182141$fs3.30764121@typhoon.tampabay.rr.com>    You can use dates,  L SEARCH/SINCE=date   (you can specify /created or /modified etc... to specify  which date you prefer to key on,   Or you can use version numbers  . Search      file1.tmp;0,;-1,;-2,;-3     string   See:  $Help Search  9 "Hans M. Aus" <aus@vim.uni-wuerzburg.de> wrote in message > news:aus-0905011429030001@wvia48.virologie.uni-wuerzburg.de... > J > Is there an easy way to limit the DCL $SEARCH filename.dat;* to only the > newest N files?  >  > --D > Cheers, Hans M. Aus, Wuerzburg, Germany,  aus@vim.uni-wuerzburg.de >    ------------------------------  $ Date: Wed, 9 May 2001 08:37:33 -05001 From: "Dave Gudewicz" <david.gudewicz@abbott.com> 7 Subject: Re: ABS - backup service from NT to VMS device 8 Message-ID: <9dbh7n$rf9$1@fizban.fizban.pprd.abbott.com>  J We have spent some time with ABS, v3.newest, with VMS as the backup targetK only.  Seems OK but I have to agree with spotty support.  We also looked at K VMS roadmaps and ABS *is* Compaq's solution with new stuff coming, etc.  It L would be nice if other GUIs were supported.  Don't mean to start a war here,H but Motif is not "well known" and on the decline from what I understand.  J We also looked at Veritas, and when we asked questions like "can it backupI and restore a VMS system disk such that the restored disk is bootable" we L got a blank stare as an answer.  Maybe we asked the wrong person.  Donno for sure.   I I believe TAR is the only backup format supported by Veritas.  Not saying 8 thats bad, but that sure isn't native VMS backup format.  J Now this thread has started me thinking if ABS is/was the right way to go.  " Anybody else have comments on ABS?   Dave...   8 "Peter Weaver" <peter.weaver@stelco.ca> wrote in message. news:5YyJ6.235271$Z2.2516384@nnrp1.uunet.ca...H > "Curtis Rempel" <vmsguy.no.spam.here.please@home.com> wrote in message4 > news:etKI6.164$Hk4.13289@news1.rdc1.ab.home.com... > >...= > > We have since killed ABS since Digital and now Compaq has  > consistentlyH > > demonstrated that they cannot get their act together.  We have moved	 > forward E > > with Veritas NetBackup running on a Tru64 AlphaServer.  We tested 	 > the VMS H > > client support extremely rigorously and found no major deficiencies. > G > How do you handle your system drives? Aliases and Contiguous files on  > non-system drives? > F > > Veritas support for the VMS client is out of the UK (Chertsey) and
 > Alan FayF > > is 110% top notch (thanks for all your extremely helpful and quick > responses  > > Alan!).  > E > Seconded, he is very quick to fix problems. I did get a bit nervous G > when I recieved a new image at 9:40 and noticed that the link time on C > it was 9:30 (after converting for time zones) - but the new image  > fixed the problem. >  >  > >...G > > the software and ask for your money back - ALL of it.  Having grown 	 > up with D > > Digital and become accustomed to the stellar engineering efforts	 > made by H > > various product groups, it was an absolute nightmare to believe thatF > > something like ABS was actually released in public as a product by
 > Digital.? > > I would have been personally embarrassed myself to have let  > something like > > ABS see the light of day.  > F > Compaq Analyze, DSN 2.2, DSN 3.0, ABS... How is this garbage gettingF > through the door at Compaq? How do we get Compaq's attention so theyD > know that we expect all the products on our VMS systems to work as > well as the base OS itself?  >  >    ------------------------------  $ Date: Wed, 9 May 2001 09:26:04 -05001 From: "Dave Gudewicz" <david.gudewicz@abbott.com> 7 Subject: Re: ABS - backup service from NT to VMS device 8 Message-ID: <9dbk39$rsh$1@fizban.fizban.pprd.abbott.com>  G Just noticed that v3.2 of ABS was released 30-Apr-2001.  From the cover  letter:   + Changes to the scope of support for ABS 3.2   J In a future release, ABS will discontinue to utilize Windows NT Alpha as aE client.  As of 3.2, the ABS UNIX client will only utilize Tru64 UNIX.   - More at:  www.support.compaq.com/sms/abs/ and 3 www.openvms.compaq.com/openvms/storage/abspage.html    Dave...   < "Dave Gudewicz" <david.gudewicz@abbott.com> wrote in message2 news:9dbh7n$rf9$1@fizban.fizban.pprd.abbott.com...L > We have spent some time with ABS, v3.newest, with VMS as the backup targetJ > only.  Seems OK but I have to agree with spotty support.  We also looked atI > VMS roadmaps and ABS *is* Compaq's solution with new stuff coming, etc.  ItH > would be nice if other GUIs were supported.  Don't mean to start a war here, J > but Motif is not "well known" and on the decline from what I understand. > L > We also looked at Veritas, and when we asked questions like "can it backupK > and restore a VMS system disk such that the restored disk is bootable" we J > got a blank stare as an answer.  Maybe we asked the wrong person.  Donno for  > sure.  > K > I believe TAR is the only backup format supported by Veritas.  Not saying : > thats bad, but that sure isn't native VMS backup format. > L > Now this thread has started me thinking if ABS is/was the right way to go. > $ > Anybody else have comments on ABS? > 	 > Dave...  > : > "Peter Weaver" <peter.weaver@stelco.ca> wrote in message0 > news:5YyJ6.235271$Z2.2516384@nnrp1.uunet.ca...J > > "Curtis Rempel" <vmsguy.no.spam.here.please@home.com> wrote in message6 > > news:etKI6.164$Hk4.13289@news1.rdc1.ab.home.com... > > >...? > > > We have since killed ABS since Digital and now Compaq has  > > consistentlyJ > > > demonstrated that they cannot get their act together.  We have moved > > forward G > > > with Veritas NetBackup running on a Tru64 AlphaServer.  We tested  > > the VMS J > > > client support extremely rigorously and found no major deficiencies. > > I > > How do you handle your system drives? Aliases and Contiguous files on  > > non-system drives? > > H > > > Veritas support for the VMS client is out of the UK (Chertsey) and > > Alan FayH > > > is 110% top notch (thanks for all your extremely helpful and quick
 > > responses 
 > > > Alan!).  > > G > > Seconded, he is very quick to fix problems. I did get a bit nervous I > > when I recieved a new image at 9:40 and noticed that the link time on E > > it was 9:30 (after converting for time zones) - but the new image  > > fixed the problem. > >  > >  > > >...I > > > the software and ask for your money back - ALL of it.  Having grown  > > up with F > > > Digital and become accustomed to the stellar engineering efforts > > made by J > > > various product groups, it was an absolute nightmare to believe thatH > > > something like ABS was actually released in public as a product by > > Digital.A > > > I would have been personally embarrassed myself to have let  > > something like > > > ABS see the light of day.  > > H > > Compaq Analyze, DSN 2.2, DSN 3.0, ABS... How is this garbage gettingH > > through the door at Compaq? How do we get Compaq's attention so theyF > > know that we expect all the products on our VMS systems to work as > > well as the base OS itself?  > >  > >  >  >    ------------------------------  $ Date: Wed, 9 May 2001 10:29:25 -0400- From: "Peter Weaver" <peter.weaver@stelco.ca> 7 Subject: Re: ABS - backup service from NT to VMS device 4 Message-ID: <ovcK6.235844$Z2.2537365@nnrp1.uunet.ca>  < "Dave Gudewicz" <david.gudewicz@abbott.com> wrote in message2 news:9dbh7n$rf9$1@fizban.fizban.pprd.abbott.com... >...E > We also looked at Veritas, and when we asked questions like "can it  backup> > and restore a VMS system disk such that the restored disk is bootable" weC > got a blank stare as an answer.  Maybe we asked the wrong person. 	 Donno for  > sure.  >...  8 You asked the right person and got the correct response.  E Unfortunately the NetBackup documentation said "restored system disks F have been successfully made bootable by some knowledgeable customers."D When we told the people who bought NetBackup (without any input fromC any VMS person) that we could not backup the system drive we had to D prove it. I actually had one person look me in the eye and say "does. that mean you're not knowledgeable about VMS?"  F I sent a note to Alan Fay about this and he removed that line from the manual. (thanks Alan)    ------------------------------    Date: 09 May 2001 10:25:27 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>: Subject: Re: BisynchH Message-ID: <y4eltzkjyg.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  - "antonio.carlini" <arcarlini@iee.org> writes:   D > > I do not think that hacking VMSINSTAL to force it is the answer.K > I recall that there is some way of forcing PCSI to install regardless of  H > its opinion regarding the wisdom of so doing, but I don't recall how.   J AFAIR, VMSINSTAL does not give you the option if the callback is so coded.   	Jan   ------------------------------    Date: 09 May 2001 10:31:10 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>A Subject: Re: BisynchH Message-ID: <y4bsp2ly9d.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  ( "john nixon" <jnixon@cfl.rr.com> writes:  M > Thanks for your offer of assistance.  So far, you and Scot are the only onehK > that have replied, but no one from an official capacity.  I am paying foreK > Compaq support for 2780/3780, but so far no one else, including our salesiK > rep or DSN has stepped up to the plate.  I have even e-mailed the productm
 > manager.  9 That lack of response, of course, is always unacceptable.a  M > I do not think that hacking VMSINSTAL to force it is the answer.  Even if IsN > could make it work for now, I am going to have to buy several DS10s or otherN > Alphas (along with all the software, including cluster and vol-shadowing) to > accommodate one board each.   M What if modifying KITINSTAL.COM (_not_ VMSINSTAL.COM, that was not suggested)vJ were the officially sanctioned workaround? Once you have re-packackged theF save set with the modified KITINSTAL, you no longer have a (technical)G problem, provided the software actually functions on the VMS version ineC question, which you have not said explicitly, but I gather it does.t  H > I can't see spending that kind of money on a cludged prouduct that is  > not supported.   Of course not, but...n  N > The SPD says it should work on VMS 7.2 and DECnet OSI 7.2 and later, but the > product won't install.  N The SPD (you have saved and printed a copy?) is DEC^H^H^HCPQ's legally bindingG statement that the product is supported on that platform. Reality might L intervene, as with every component of a system, but the SPD's statement (andK your support contract) is your basis for lighting a fire under CPQ's bottom  if required.   	Jan   ------------------------------    Date: 09 May 2001 19:43:51 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: Bisynch- Message-ID: <87itjaycg8.fsf@prep.synonet.com>   I Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> writes:u  @ > The SPD (you have saved and printed a copy?) is DEC^H^H^HCPQ'sA > legally binding statement that the product is supported on that A > platform. Reality might intervene, as with every component of a E > system, but the SPD's statement (and your support contract) is yourc; > basis for lighting a fire under CPQ's bottom if required.d  D The way to solve it is to ring Texas and ask when <name> of <office> will return your call.   -- D< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.n@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov c   ------------------------------  # Date: Wed, 09 May 2001 12:54:31 GMTD& From: "john nixon" <jnixon@cfl.rr.com> Subject: Re: Bisynch? Message-ID: <b6bK6.182204$fs3.30767992@typhoon.tampabay.rr.com>t  A The product is 2780/3780 pe (protocol emulator).  The kit name iseH AXPBSCPTP020 and it is a VMSINSTAL kit.  The install procedure gives theK error messages about BADVMS and Product expired after VMS 7.1  (even thoughuI the SPD claims support for VMS7.2), then the install procedure exits.  ITaF doesn't crash and it doesn't give an option to continue.  it just says@ "%VMS-E-INSFAIL, the installation of AXPBSCPTP v2.0 HAS FAILED",   Then it returns you to the $.S  6 "antonio.carlini" <arcarlini@iee.org> wrote in message! news:3AF8124D.8518F4B7@iee.org...  > john nixon wrote:kJ > > I do not think that hacking VMSINSTAL to force it is the answer.  Even if IJ > > could make it work for now, I am going to have to buy several DS10s or othere> > > Alphas (along with all the software, including cluster and vol-shadowing) to K > > accommodate one board each.  I can't see spending that kind of money on  an+ > > cludged prouduct that is not supported.t >d3 > Is this the SNA software that will not install orw3 > the X.25 software? If it's X.25 then I'm a little ' > surprised since I use to have to jumpa) > through hoops to build PCSI kits so I'mn2 > guessing that noone would have built a VMSINSTAL > kit in a looong time!s >r2 > I don't recall ever playing with SNA on Alpha so > I cannot comment on that.e >vL > > The SPD says it should work on VMS 7.2 and DECnet OSI 7.2 and later, but therG > > product won't install.  I am really stuck with no help forthcoming.r > , > I recall that there is some way of forcing+ > PCSI to install regardless of its opinion9) > regarding the wisdom of so doing, but I * > don't recall how. Maybe someone else can > dive in here.  >o- > I assume that it just bombs out rather than 1 > asking whether you wish to continue even though / > it may be a terminally bad idea (which, IIRC,  > is how the DECnet kit works).  > 	 > Antonioe >s > -- >t > ---------------n/ > Antonio Carlini             arcarlini@iee.orgy >h   ------------------------------  # Date: Wed, 09 May 2001 13:00:46 GMTm& From: "john nixon" <jnixon@cfl.rr.com> Subject: Re: Bisynch? Message-ID: <2cbK6.182254$fs3.30771668@typhoon.tampabay.rr.com>   L Shortly after posting, I received a response from the product manager (SusanH Dugdale).  (In her defense, I don't think hter reply to me was due to myK posting on COV.   She is looking into this for me, and also looking into aneK alternative, but I still have no answer yet as to why the kitinstal and the  SPD differ.   J As for the lack of response from DSN or Colorado, the problem is more withF contract administration than with the product support group.  For someH reason, they think we don't have support for the product.  I wonder whatJ they are doing with the $2,112 we send them every year to maintain this on
 four systems.t  L "Jan Vorbrueggen" <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> wrote inJ message news:y4bsp2ly9d.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de...* > "john nixon" <jnixon@cfl.rr.com> writes: > K > > Thanks for your offer of assistance.  So far, you and Scot are the only  oneqI > > that have replied, but no one from an official capacity.  I am paying  forcG > > Compaq support for 2780/3780, but so far no one else, including our  sales E > > rep or DSN has stepped up to the plate.  I have even e-mailed the5 productr > > manager. >"; > That lack of response, of course, is always unacceptable.  >m   ------------------------------  % Date: Wed, 09 May 2001 14:26:06 +0100   From: steven.reece@quintiles.com Subject: Re: BisynchH Message-ID: <OF3F27EA95.7E2006EE-ON80256A47.0048D973@qedi.quintiles.com>  I This would be along the same lines as using DECnet over TCP/IP for DQS ise: unsupported, despite the view of the DQS SPD that states :I "The DQS software can be used in any DECnet networking environment.  BothnG Local Area Networks and Wide Area Networks are supported.  DQS supportsc' DECnet Phase V fullname functionality."B# It's a strange world we live in....s Steve.   John Nixon commented := >>>I still have no answer yet as to why the kitinstal and thet SPD differ.<<<   ------------------------------  $ Date: Wed, 9 May 2001 09:35:31 -04002 From: "Sue Skonetski" <susan.skonetski@compaq.com> Subject: Re: Bisynch0 Message-ID: <0JbK6.45$fi2.1814@news.cpqcorp.net>   Just a question." Did you log a call for this issue?  F For folks that may be new to the process.  My apoligies if everyone is already aware of this.  J You are much better off contacting your local service rep vs the sales rep (Digital or otherwise).:  9 How the problem reporting structure works with-in Compaq.v  I Customer with a services contract logs a call. Once the problem report iseI logged and if the field can not answer it the problem will end up back ati4 VMS engineering in the Sustaining Engineering group.  G One of the good things about this procedure is that once the sustainingyK engineering group fixes the bug it is then put into future releases of VMS.e# So the procedure helps VMS quality.n   SueS    1 "john nixon" <jnixon@cfl.rr.com> wrote in messagef9 news:afDJ6.170899$fs3.28745768@typhoon.tampabay.rr.com... 8 > If you remember the Bisynch thread a little while ago, >2L > Well, we bought the PBXDB for our Alphaserver.  We have a license.  I haveJ > even lined up a source for some of the 8 port cards so that we only have toL > buy 4 Alphas to get my 26 ports instead of seven Alphas.  Now, we load the? > software, and it rather rudely tells us that we have "BADVMS"aH > (%AXPBSCPTP-E-BADVMS,  this kit can only be installed on OpenVMS Alpha V6.2
 > or V7.1) > I > It says to contact your local Digital sales representative  (not CompaqeF > sales rep,but "Digital".   It was probably Bob Palmer that wrote the BADVMS > part). >NH > I wonder what I do now.  This was a big part of our VAX to Alpha port. NowiH > that we have spent a rather large sum of money, I have to go tell them thatG > I did not research this well enough.   I sure hope I like living in a  > Sun/Solaris+Microsoft world. >s >i >t >s   ------------------------------  # Date: Wed, 09 May 2001 14:04:52 GMT & From: "john nixon" <jnixon@cfl.rr.com> Subject: Re: Bisynch? Message-ID: <88cK6.183156$fs3.30811398@typhoon.tampabay.rr.com>t  H I have tried to log a call over DSN, but they claim I don't have suport.K When I pointed out my contract number and the four line item numbers, wherelI I am paying over $2,000 /year, they said they (DSN%DSNLINK) was the wrongP group.   DSN%MOD never answered.o  J I am still waiting to hear back from DSN%CAD.  (I just sent them a message today)  0 Our contract administrator is "looking into it".  K I have heard back from my Compaq Sales Rep(but it was an automated, "out ofmI office" message) and his tech guy, and from my Compaq Authorized Reseller / and his tech guy.  They all said to log a call.   C By the "local service rep",  are you referring to our Field ServiceMJ Engineer?  I hadn't thouht of that because this is a software problem.  He% is pretty sharp.  I will contact him.t  = "Sue Skonetski" <susan.skonetski@compaq.com> wrote in messagee* news:0JbK6.45$fi2.1814@news.cpqcorp.net... >t >  > Just a question.$ > Did you log a call for this issue? >tH > For folks that may be new to the process.  My apoligies if everyone is > already aware of this. > L > You are much better off contacting your local service rep vs the sales rep > (Digital or otherwise).h >n; > How the problem reporting structure works with-in Compaq.6 >nK > Customer with a services contract logs a call. Once the problem report is K > logged and if the field can not answer it the problem will end up back ate6 > VMS engineering in the Sustaining Engineering group. >tI > One of the good things about this procedure is that once the sustainingeH > engineering group fixes the bug it is then put into future releases of VMS.% > So the procedure helps VMS quality.A >s > Suee >a > 3 > "john nixon" <jnixon@cfl.rr.com> wrote in message.; > news:afDJ6.170899$fs3.28745768@typhoon.tampabay.rr.com...y: > > If you remember the Bisynch thread a little while ago, > > I > > Well, we bought the PBXDB for our Alphaserver.  We have a license.  I  haveL > > even lined up a source for some of the 8 port cards so that we only have > toJ > > buy 4 Alphas to get my 26 ports instead of seven Alphas.  Now, we load thehA > > software, and it rather rudely tells us that we have "BADVMS"mJ > > (%AXPBSCPTP-E-BADVMS,  this kit can only be installed on OpenVMS Alpha > V6.2 > > or V7.1) > >MK > > It says to contact your local Digital sales representative  (not CompaqiH > > sales rep,but "Digital".   It was probably Bob Palmer that wrote the > BADVMS
 > > part). > > J > > I wonder what I do now.  This was a big part of our VAX to Alpha port. > NowlJ > > that we have spent a rather large sum of money, I have to go tell them > thatI > > I did not research this well enough.   I sure hope I like living in ac  > > Sun/Solaris+Microsoft world. > >  > >g > >  > >m >m >n >o   ------------------------------  # Date: Wed, 09 May 2001 11:32:46 GMTs& From: "Jeff Killeen" <Jeff@IDM-IO.com>2 Subject: Re: Conference: CETS-2001 - Conference CD6 Message-ID: <yV9K6.311$372.382868@typhoon2.ba-dsg.net>  + This is an FYI to all potential speakers...   D This year the conference CD with the session notes will be publishedL >>>BEFORE<<< the conference.  That means there will be a requirement to haveL your session materials submitted about mid August if you want them publishedH on the CD.  Any materials supplied after that point in time will only be available via the web site.   B The primary goal here is to insure attendees with laptops have theE presentations.  The secondary goal is to insure all presentations areiH available to attendees via the web right after the session is presented.  L We are developing a new web portal at www.CETS2001.com.  One of its featuresH will be a session index tool that will allow you to download the session@ presentation (if available) when you display a session abstract.  I Due to resource constraints the presentations material will be limited toeF PowerPoint format.  We are aware that for some that is not a preferredL format.  We will review this issue again for CETS-2002.  Developing this newJ portal has been a very resource intensive project and we have had to limit; its scope to insure timelines are achieved within budget...g     --        . Jeff Killeen - Encompass CETS Business ManagerE =====================================================================o  1 "Jeff Killeen" <Jeff@IDM-IO.com> wrote in messaged3 news:3ZwI6.15057$Aj1.5764537@typhoon2.ba-dsg.net...cI > This initial message is for anyone who may be interested in speaking at H > CETS-2001 (Compaq Enterprise Technical Symposium) www.CETS2001.com.  AG > representative group of 40+ likely attendees recently met as teams to  adviseJ > what _new_ content is desired at the CETS fall Symposium this September. > The report is available at...  >sA > http://www.cets2001.com/privatedocs/CETS2001PhaseICATReport.doc0 >$
 > ...or... >oA > http://www.cets2001.com/privatedocs/CETS2001PhaseICATReport.pdfy >yH > ...a more detail message will follow next week.  Session speakers have theireH > conference fee waived.  Weekend Seminar or Techworks Bootcamp speakers alsoG > have their fee waived plus receive airfare and weekend hotel.  Please  stayedH > tuned for a detailed message regarding speaking at CETS-2001 that willJ > follow on 5/8/2001 or 5/9/2001.  However it would be useful to read this$ > report in advance of this message. >-/ > End User session are highly valued at CETS...S >Q >  > -- >m >o >q >m2 > Jeff Killeen - www.Killeen.cc (All contact info)G > =====================================================================i >r >  >o >a >d   ------------------------------  $ Date: Wed, 9 May 2001 08:10:50 -05001 From: "Dave Gudewicz" <david.gudewicz@abbott.com>(2 Subject: Re: Conference: CETS-2001 - Conference CD8 Message-ID: <9dbfku$r7a$1@fizban.fizban.pprd.abbott.com>  H Thanks Jeff.  I think having the CD created *before* the conference is a great idea.t   Dave...t  1 "Jeff Killeen" <Jeff@IDM-IO.com> wrote in messagee0 news:yV9K6.311$372.382868@typhoon2.ba-dsg.net...- > This is an FYI to all potential speakers...  >1F > This year the conference CD with the session notes will be publishedI > >>>BEFORE<<< the conference.  That means there will be a requirement to0 haveD > your session materials submitted about mid August if you want them	 publishedsJ > on the CD.  Any materials supplied after that point in time will only be > available via the web site.a >oD > The primary goal here is to insure attendees with laptops have theG > presentations.  The secondary goal is to insure all presentations arenJ > available to attendees via the web right after the session is presented. >tE > We are developing a new web portal at www.CETS2001.com.  One of its  featuresJ > will be a session index tool that will allow you to download the sessionB > presentation (if available) when you display a session abstract. >eK > Due to resource constraints the presentations material will be limited to-H > PowerPoint format.  We are aware that for some that is not a preferredJ > format.  We will review this issue again for CETS-2002.  Developing this newsL > portal has been a very resource intensive project and we have had to limit= > its scope to insure timelines are achieved within budget...f >s >a > -- >f >  >  > 0 > Jeff Killeen - Encompass CETS Business ManagerG > =====================================================================2 >/3 > "Jeff Killeen" <Jeff@IDM-IO.com> wrote in message 5 > news:3ZwI6.15057$Aj1.5764537@typhoon2.ba-dsg.net...mK > > This initial message is for anyone who may be interested in speaking at J > > CETS-2001 (Compaq Enterprise Technical Symposium) www.CETS2001.com.  AI > > representative group of 40+ likely attendees recently met as teams tou > adviseL > > what _new_ content is desired at the CETS fall Symposium this September.! > > The report is available at...  > > C > > http://www.cets2001.com/privatedocs/CETS2001PhaseICATReport.docw > >t > > ...or... > >tC > > http://www.cets2001.com/privatedocs/CETS2001PhaseICATReport.pdf  > >sJ > > ...a more detail message will follow next week.  Session speakers have > theirhJ > > conference fee waived.  Weekend Seminar or Techworks Bootcamp speakers > alsoI > > have their fee waived plus receive airfare and weekend hotel.  Pleaseo > stayedJ > > tuned for a detailed message regarding speaking at CETS-2001 that willL > > follow on 5/8/2001 or 5/9/2001.  However it would be useful to read this& > > report in advance of this message. > >v1 > > End User session are highly valued at CETS...l > >n > >  > > -- > >t > >p > >t > >u4 > > Jeff Killeen - www.Killeen.cc (All contact info)I > > =====================================================================o > >n > >) > >o > >s > >r >g >n   ------------------------------    Date: 09 May 2001 16:21:26 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de><2 Subject: Re: Conference: CETS-2001 - Conference CDH Message-ID: <y466fawql5.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  ( "Jeff Killeen" <Jeff@IDM-IO.com> writes:  K > Due to resource constraints the presentations material will be limited to  > PowerPoint format.  L It is so difficult to accept, either alternatively or in addition, PDF filesM (which can be generated from PPT, BTW, and I as a company employee usually dotN not consider it a good idea to give away all the company-specific PPT template stuff with every presentation)?x   	Jan   ------------------------------  # Date: Wed, 09 May 2001 16:24:06 GMTi2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)2 Subject: Re: Conference: CETS-2001 - Conference CD0 Message-ID: <GaeK6.57$fi2.1893@news.cpqcorp.net>  l In article <9dbfku$r7a$1@fizban.fizban.pprd.abbott.com>, "Dave Gudewicz" <david.gudewicz@abbott.com> writes:I :Thanks Jeff.  I think having the CD created *before* the conference is a- :great idea.  J   Now for the downside of a mid-August deadline for a mid-September event.  C   Please do not expect to see current versions of my presentations 2G   included on the conference CD, nor the sessions of a number of other tG   folks in OpenVMS Engineering.  While having the CD media immediately aJ   available to the conference attendees is a certainly and clearly useful F   -- and while I will certainly work to see the latest versions of my F   presentation materials included, the lead time can run afoul of the    nature of the business.s  F   Why?  Well, I am perpetually updating my slides.  For example, threeE   of the technical presentations I usually perpetrate are being used tE   this week in Lisbon and will be used again next week in London and  G   Zurich, and the presentation that I expect most folks are interested nH   in -- the technical update -- was updated twice in the past two weeks.F   It may well be updated again later this week or early next.  (I haveG   been known to update the presentation immediately prior to presentinge<   it -- to incorporate important information just received.)  D   For more the static presentations, this pre-emptive approach will A   clearly work just fine, and several of my presentations and thep@   presentations of other engineers would obviously qualify here.  D   As an obviously more costly alternative, I do know of conferences A   that create the media at the end of the week of the conference.l  H   This distribution decision might provide the impetus to serve various I   of the Compaq OpenVMS CETS2001 technical presentations via the website..H   (Or to bring along the hardware necessary to replicate CD-R media. :-)  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 09 May 2001 17:43:39 +0100g  From: steven.reece@quintiles.com2 Subject: Re: Conference: CETS-2001 - Conference CDH Message-ID: <OFDCE6B449.92DDE5CA-ON80256A47.005BA58E@qedi.quintiles.com>  J If only it was a VMS CD.  Then someone might be able to justify a GS320 orK GS160 (for expandability) with lots of PCI cages with SCSI adapter cards inh+ them connected to (unsupported) CD writers.s* Sledgehammers and nuts spring to mind..... :-)o   Hoff commented : >>>hG   This distribution decision might provide the impetus to serve variousnI   of the Compaq OpenVMS CETS2001 technical presentations via the website. H   (Or to bring along the hardware necessary to replicate CD-R media. :-) <<<l   ------------------------------  % Date: Wed, 09 May 2001 11:58:11 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>N2 Subject: Re: Conference: CETS-2001 - Conference CD& Message-ID: <3AF97723.B1A9496@fsi.net>   Jeff Killeen wrote:s > - > This is an FYI to all potential speakers...t > F > This year the conference CD with the session notes will be publishedN > >>>BEFORE<<< the conference.  That means there will be a requirement to haveN > your session materials submitted about mid August if you want them publishedJ > on the CD.  Any materials supplied after that point in time will only be > available via the web site.a  D I would suggest, then, that the pre-conference CD be cleary labelledA "PRELIMINARY - SUBJECT TO CHANGE WITHOUT NOTICE" with that notice H repeated copiously throughout the material and that a complete, updated,H comprehensive post-conference CD be made available either free of charge( or for the cost of postage and handling.  H I do, also, second David G.'s comment that this is a good idea, with the* caveat of the limitations mentioned above.  D > The primary goal here is to insure attendees with laptops have theG > presentations.  The secondary goal is to insure all presentations aresJ > available to attendees via the web right after the session is presented.  F To accomodate attendees with laptops, perhaps a better option might beD to facilitate (by some magic) downloading of the presentation(s) forC those session(s) one wishes to attend. This eliminates the cost andPH lead-time of producing a static medium, and provides the latest and most) up-to-date presentation to the attendees.h  G Of course, hardcopy hand-outs will still need to be available since not-G everyone is sufficiently affluent to have the luxury of travelling withSE a laptop (much less even having one). I see many attendees with them,g= but I also see the majority of attendees without them. So, it D (pre-conference CD) seems an inordinately large effort/expense to go- through to serve a somewhat limited audience.   N > We are developing a new web portal at www.CETS2001.com.  One of its featuresJ > will be a session index tool that will allow you to download the sessionB > presentation (if available) when you display a session abstract. > K > Due to resource constraints the presentations material will be limited torH > PowerPoint format.  We are aware that for some that is not a preferredN > format.  We will review this issue again for CETS-2002.  Developing this newL > portal has been a very resource intensive project and we have had to limit= > its scope to insure timelines are achieved within budget...o  ) I second Larry K.'s comments, and expand:s  F PowerPoint itself provides for HTML output (well, HTML and either .GIFG or .JPG). Extra effort required to accomodate this should be minimal oroE non-existant. All servers and browsers (except Lynx) on all platformse( support both HTML and .GIF/.JPG, AFAIK.   F PPT is M$-proprietary with limited support in Linux and *BSD (Koffice, StarOffice, etc.).  B Users having PPT should be able to download the .PPT file (Zipped,G preferably, of course! - NO SELF-EXTRACTS!!! (security consideration)). F Other users should be able to download the HTML version (again, ZippedE to preserve the directory structure as well as to reduce the downloadl bandwidth consumption).S   -- t David J. Dachteraw dba DJE Systemsi http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/h  H This may have been posted to an OpenVMS-related newsgroup. So, a certain# bias in postings is to be expected..  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  # Date: Wed, 09 May 2001 13:39:53 GMTo& From: "Jeff Killeen" <Jeff@IDM-IO.com>F Subject: Re: Conference: CETS-2001 - Conference CD - the Microsoft Way7 Message-ID: <JMbK6.1547$v66.477593@typhoon1.ba-dsg.net>   / > Limiting scope is an understandable approach.S >O8 > But why not choose a more universal scope, like HTML ?  I This wasn't a clean sheet of paper design.  It turns out that the companyiJ that developed the Portal for Novell's Brainshare conference had some goodI off-the-shelf application chunks we could use.  If we hadn't found them Im9 doubt we would have had a working Portal for CETS-2001...t     --        . Jeff Killeen - Encompass CETS Business ManagerE =====================================================================   F "Larry Kilgallen" <Kilgallen@eisner.decus.org.nospam> wrote in message- news:OLAbC0DlDfEQ@eisner.encompasserve.org...iG > In article <yV9K6.311$372.382868@typhoon2.ba-dsg.net>, "Jeff Killeen"q <Jeff@IDM-IO.com> writes:a >fJ > > Due to resource constraints the presentations material will be limited toJ > > PowerPoint format.  We are aware that for some that is not a preferredL > > format.  We will review this issue again for CETS-2002.  Developing this new H > > portal has been a very resource intensive project and we have had to limitv? > > its scope to insure timelines are achieved within budget...a >i/ > Limiting scope is an understandable approach.d > 8 > But why not choose a more universal scope, like HTML ?   ------------------------------   Date: 9 May 2001 08:42:43 -0500e9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)hF Subject: Re: Conference: CETS-2001 - Conference CD - the Microsoft Way3 Message-ID: <OLAbC0DlDfEQ@eisner.encompasserve.org>r  _ In article <yV9K6.311$372.382868@typhoon2.ba-dsg.net>, "Jeff Killeen" <Jeff@IDM-IO.com> writes:r  K > Due to resource constraints the presentations material will be limited toBH > PowerPoint format.  We are aware that for some that is not a preferredN > format.  We will review this issue again for CETS-2002.  Developing this newL > portal has been a very resource intensive project and we have had to limit= > its scope to insure timelines are achieved within budget...%  - Limiting scope is an understandable approach.e  6 But why not choose a more universal scope, like HTML ?   ------------------------------  % Date: Wed, 09 May 2001 13:19:02 +0100e- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>e Subject: Re: DCL "library") Message-ID: <3AF935B6.FD035CE1@bbc.co.uk>w  ! terry.polar@eudoramail.com wrote:A   >p >.K > Why don't try MenuFinder utility ? It's seems perfect for integrating DCLlN > procedures on a menu system - you can easily maintain your procedure withoutC > exiting the menu and your procedures or programs can be anywhere.  >  > Visit: www.itre.com/mf/- >- > Terry   O thanks for the pointer Terry, it is free for the first machine so I may try it.j   regardsn     --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uks  A I speak for myself only and my views in no way represent those ofs MedAS or the BBC.q   ------------------------------  % Date: Wed, 09 May 2001 13:30:27 +0100w- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>u Subject: Re: DCL "library"' Message-ID: <3AF93863.B48E23@bbc.co.uk>i   John Santos wrote:  F > In the interests of safety, I would propose a modification to eitherB > of these procedures.  If you have internal labels that are *not*> > intended to be entry points, people can call them anyway, by? > mistake or on purpose.  (Security shouldn't be an issue here,e? > since I don't think anyone could do anything by calling a DCLoA > "library" procedure that they couldn't do directly by executingi= > the appropriate DCL commands interactively, unless you wereaA > calling the library as a captive user, but accidents happen...)o >o? > The most obvious fix (to me) is to prefix the labels that area? > intended to be externally visible with a string, such as "X_"s= > (for eXternal), and then prefix the target of the "call" ori> > "goto" with it.  Labels that do *not* begin with "X_" can be> > used as necessary with no risk of someone accidently jumping
 > to them. >= > See below: >=    John=   I'll bear that in mind."   regardsI --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.ukn  A I speak for myself only and my views in no way represent those ofg MedAS or the BBC.a   ------------------------------  % Date: Wed, 09 May 2001 10:46:43 -0300 ) From: fabio_compaq@ep-bc.petrobras.com.br D Subject: Digital Networks changed the D - I - G - I - T - A - L logoL Message-ID: <OFA3286625.532D4B95-ON03256A47.004B9A04@ep-bc.petrobras.com.br>   Clickt   http://www.dnpg.comR   Regards    FC   ------------------------------  $ Date: Wed, 9 May 2001 13:04:49 -04002 From: "Sue Skonetski" <susan.skonetski@compaq.com>' Subject: Digital Networks Press Releaset0 Message-ID: <AMeK6.61$fi2.1700@news.cpqcorp.net>   Logo removed by Sue Skonetskio         FOR IMMEDIATE RELEASEs    D PR Contacts:            Dawn Rohrbacher               Karen Blondell  -                              Digital Networksa D|K|Communications  I                              978-474-8340                    310-791-5838   K                              rohrbach@dnpg.com           k.blondell@gte.net=          $ DIGITAL NETWORKS INTRODUCES FOUR NEW  / PRODUCTS FOR ENTERPRISE NETWORKING APPLICATIONS-      . Experienced Networking Leader Offers Unrivaled  E Investment Protection and Worldwide Service and Support at a Low CostT      K Andover, Mass (April 23, 2001) - Digital Networks, the leader in networking L products for the enterprise and workgroup environments, today announced fourF new products along with an enhanced service and support offering.  TheF DNmultilayer 1000, DNswitch, DECserver 732 and DECswitch 90 FE are allK immediately available and shipping to customers through a worldwide channeli& of distribution and reseller partners.      G Digital Networks is the former networking division of Digital EquipmentsH Corporation (DEC), and has been in operation for less than one year. TheL company is delivering reliable and scalable networking solutions to over oneK million end users worldwide including Blockbuster Video, Compaq, Fingerhut,s WorldCom and the VA Hospital.n      E Digital Networks supports the worldwide installed base of DEC network F equipment users with products and services to extend the life of theirL network infrastructure. With over one million DECservers, 100,000 DEChub 90sL and 50,000 MultiSwitch 900 chassis' installed today, Digital Networks serves! a large, loyal base of customers.u              G "Today's economic climate presents an excellent opportunity for DigitaliL Networks' value-oriented networking products; which are reliable, long-livedJ and easily adapt to changes in technology and business requirements," saidK Lee Knoch, executive vice president at Digital Networks.  "IS professionals E are searching for ways to make the best technology investments movingwI forward. Our existing customers can draw more value out of their networksCH through upgrades and expansion with our products, rather than completelyJ replacing their existing equipment; and new enterprise customers get peace< of mind knowing that our products will not become obsolete."     New Product OfferingsoI Among the new product families introduced today are the DNmultilayer 1000pG family of switch routers for the enterprise and the DNswitch family foroI workgroup environments. Individual products also introduced today includecG the DNswitch 800, the DECserver 732, and the DECswitch 90 Fast EthernetoG Switch. All Digital Network products are ideal solutions for enterpriseS organizations.      I The new DNmultilayer 1000  switch router family consists of products that0C provide high-speed network connectivity in enterprise, LAN, WAN andwH metropolitan area (MAN) networks. The DNmultilayer 1800 and 1400 modularI expandable chassis-based products support up to 48 Gigabit Ethernet portswI and 128 10/100 ports, while the fixed configuration DNmultilayer 1200 and J 1100 offer high density 10/100 layer 2/3/4 switching with multiple GigabitH Ethernet uplinks. Using Ethernet over OC-48 technology, the DNmultilayerI 1000 family provides continued support for disaster tolerant data centersu* and high performance cluster environments.  G  The new DNswitch family of stackable and standalone 10/100 and Gigabit=H Ethernet switches are ideal for the broadest workgroup environments. The DNswitch 800 is an  F 8-port high-performance gigabit Ethernet workgroup switch suitable forI supporting network-intensive applications and high volume file transfers.u  E The new DECserver 732 is the high performance member of the DECserveryH family - the most reliable access and device-server family on the marketH today with more than one million units installed worldwide. This 32-portC device server is ideal for mission-critical applications in retail,dG manufacturing, telecommuting and office/building automation; connectinghD devices such as security cameras, terminals, modems, cash registers,D laboratory instruments and factory equipment to an Ethernet network.  H  Digital Networks is also introducing the new DECswitch 90 Fast EthernetF switch - available for customers with the DEChub90 and MultiSwitch 900B platforms, as well as standalone and stacked configurations in theH Multistack System.  The addition of the DECswitch 90 allows customers toK incrementally grow the number of ports and the speed of their network (fromuJ 10Mbps to 100 Mbps), and maximize the value of their current investment inC Digital-branded technology. This new product eliminates the risk of : bottleneck that often results from normal business growth.      
 DNservices  H In addition to its impressive array of new products, Digital Networks isL expanding its offering to include a comprehensive portfolio of services thatG can be modified to meet customers' precise operational requirements anddE business objectives.  Digital Networks now provides its customers and E resellers with customized installation, on-site maintenance, softwaree7 maintenance, technical assistance and warranty support.u      @ Many of the new services available are due in part to a businessF relationship with VITAL Network Services, a leading global provider ofI network support for converging networks. Through VITAL's Rapid TechnologynH Introduction Process, services have been introduced worldwide to DigitalJ Networks' entire portfolio of multi-technology network switches, workgroupH switches, access servers, routers, and network management product lines.       Dedication to the ChanneleA Digital Networks sells its products exclusively through a channeli@ distribution model. Selling partners include the world's leadingF distributors of network solutions - including AVNET and Pioneer in theH United States; Azlan, Anixter and Raab-Karcher in Europe; and Duxbury inA South Africa - and more than 200 value-added resellers worldwide.e      F "Digital Networks offers a real value-add to our customers with betterJ pricing, low cost of ownership, a history of reliability, and innovation -L as well as a strong new product portfolio for the future," said Andy Bryant,J president, Avnet Computer Marketing.  "The Digital-branded products are anL integral part of our customers' network infrastructure, and we will continue= to be a value-added supplier of Digital Networks' solutions."n      F "Our distribution model is what makes us unique," said Dana Lariviere,I executive vice president at Digital Networks. "We do not compete with ourjF partners - period! Few companies in the market can claim this level ofJ dedication.  Digital Networks will continue to uphold our reputation as an@ excellent channel partner and we will only partner with the best' distributors and VARs in the industry."C       Pricing and AvailabilityF The DNmultilayer 1000 family of switch routers offers the best GigabitG pricing in the industry at less than $1500 per Gigabit port. Individualt6 product pricing (minimum configuration) is as follows:  G -          DNmultilayer 1800 (twelve-slot chassis with 8 payload slots)a starts at under $29,000r  F -          DNmultilayer 1400 (eight-slot chassis with 4 payload slots) starts at under $21,000:  G -          DNmultilayer 1200 (two-slot chassis) starts at under $11,000R  G -          DNmultilayer 1100 (one-slot chassis) starts at under $10,000.      I The DNswitch family offers the lowest cost per port ($58 per 10/100 port) F and highest performance in the industry. Products come with a lifetimeL warranty and free clearVISN network management software, making this product family an incredible value. Theb  5 DN Switch 800 pre-configured box is priced at $5,995.t  I The DECserver 732 asynchronous device server is now available for $3,095.a Thei  L DECswitch 90 is priced at $845 and is now available as a DEChub 90 module, aL MultiSwitch 900 module, or with the purchase of a DETRX as a standalone unitK in the Multistack System.  The DECswitch 90 comes with a one-year warranty,pI which includes telephone support during normal business hours and a 5-dayr advance replacement.       About Digital NetworksK Based in Andover, Mass., Digital Networks was established in September 2000iK as a privately held company committed to providing high performance networktE solutions for mission-critical enterprise and workgroup applications.lF Formerly the networking product group of Digital Equipment CorporationK (DEC), the company has an installed base of more than one million end userseI worldwide and continues to sell its products exclusively through a globaleG channel of distributors and resellers. For additional information visiteK www.digitalnetworks.net or call 978.474.8300 in the U.S. and Canada, or +44n (0) 1635.810.432 in Europe.o  
 #  #  #  #   ------------------------------  % Date: Wed, 09 May 2001 16:35:45 +1000c( From: Patrick Keogh <pkeogh@au1.ibm.com>! Subject: Re: Disk re-organisationt+ Message-ID: <3AF8E541.E989E5E5@au1.ibm.com>e   Martin Vorlaender wrote:   > G > The question that went unanswered then was how to merge the QUOTA.SYSc	 > files?!   , Merging QUOTA.SYS is fairly straightforward.M The file format is a standard indexed file (ANALYZE will reveal all), and yout can 2 read and write two QUOTA.SYS files, even from DCL.   An algorithm likea  '     Read one file (master) sequentially 8     Indexed read record with same UIC in secondary file.L     If it exists, add permquotas, select larger of two overdrafts and update record.r  N     Then a sequential pass through the secondary file to find any record which doesN     not have a corresponding entry in the master, writing them to the primary.       Then rebuild the quotas.  M Sorry I don't have access to a VMS system, so I can't give you a tested piecetL of code, but it is straightforward, or at least I thought so at the time :-)  
 Patrick KeoghH IBM Global Services Australiae   ------------------------------  % Date: Wed, 09 May 2001 11:36:38 +0100l/ From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>e! Subject: re: Disk re-organisation 6 Message-ID: <009FBC04.C5C582F5.4@maxwell.ph.kcl.ac.uk>   > B > I've thrown together a few disks myself, and had good success byF > DEFINEing (/SYSTEM/EXECUTIVE/TRANSLATION=CONCEAL, of course) the old > device names to the new disk.A > L > Do not forget to use the output qualifier /BY_OWNER=ORIGINAL if you BACKUP > the data.a > G > The question that went unanswered then was how to merge the QUOTA.SYSl	 > files?!i > E The way I once did that was to dump the information as ASCII text forw each of the old disks:  " $ ASSIGN/USER DISC1.LIS SYS$OUTPUT $ MCR DISKQUOTAp
 DISKQ> SHOW *o	 DISKQ> ^Zh   etcs  N then concatenated the files and used VMS GAWK to consolidate duplicate entriesJ and write out a command procedure that when run would recreate appropriate9 quotas. Was throwaway code but basics were something liket  , //  {   quota[$1] += $3 ; limit[$1] += $4; }  E END { for user in quota printf( "ADD %s /PERM=%s /OVER=%s\n", user, \5D                                           quota[user], limit[user] )     }-     Then after big disk populated,   $ MCR DISKQUOTAJ
 DISKQ> ENABLE7 DISKQ> REBUILDM  and run the procedure created above. I also seem to remember I added a fudgeoO factor to allow for the rather bigger cluster size on the new disk compared to rG the old ones. without this, someone with a lot of one-block files wouldoH no longer have had enough space. DIR/TOTAL [*...] provided the necessary data for the fudging.     	Yours,
 		Nigel Arnot - 		NRA@MAXWELL.PH.KCL.AC.UK                   1  7 		"In the beginning there was nothing, which exploded."s   ------------------------------    Date: 09 May 2001 09:47:41 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> > Subject: Re: Effecient I/O  was Re: Pentium 4 Prefetch engine?H Message-ID: <y4n18nklpe.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  ) "Bill Todd" <billtodd@foo.mv.com> writes:c  M > To respond directly to your comment, 'real memory' is *not* 'required', butaL > it's desirable to make use of it in such circumstances if it happens to beJ > available.  The application has no clue how tight physical memory may beI > such that it can choose between accumulating data in virtual memory and < > flushing it out to disk - but the system knows very well.   J An interesting variant is VMS BACKUP. It turns VMS's resource quota systemE around: instead of having the quotas limit its activity when they areaH exhausted, BACKUP will use them as guarantees (for physical memory, fileI handles, kernel memory for various data structures and threading) that itMK can call for, and will adapt its highly parallel I/O activity to the amountcI thus specified. This has two problems: once you start a BACKUP job with acJ certain quota profile (which is not easy to adapt on the fly - but that isG a seperate issue that could be handled much more gracefully) it _will_ sI consume those resources, whatever the state of the system at that moment; E conversely, should more resources be at that moment available withoutcK impacting the rest of the system, BACKUP will not make use of them to avoidiH possibly detrimental effects (e.g., paging an I/O buffer out). Thus, youM are forced to have a general user BACKUP (yes, that is done quite frequently,-N for instance for data interchange) run very much below optimum on an otherwiseL idle system, while a heavily tuned system BACKUP will always strongly impact the system..   	Jan   ------------------------------  # Date: Wed, 09 May 2001 17:01:07 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)2 Subject: email lists interesting to OpenVMS users?0 Message-ID: <nJeK6.60$fi2.2026@news.cpqcorp.net>  I   I am looking to add a section containing various available email lists  H   that may be of interest to OpenVMS users into the next edition of the    OpenVMS FAQ.  K   I have addresses of some email lists (list servers) for various interest tG   areas of OpenVMS users (eg: OSU webserver, vmsperl, purveyor, OpenVMSmB   ECO kit notifications), and have heard of other lists (eg: Rdb).  G   Please post or email pointers to lists, and I will add them.  Thanks!-  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 9 May 2001 12:33:31 GMTe- From: "Phil Tregoning" <ptregoni@esoc.esa.de>t Subject: FYI: Bug in VMS indent A Message-ID: <01c0d881$cba14ae0$4b53b083@ptregoni.dev.esoc.esa.de>l   Hi,   6 I've been playing with Indent, a C and C++ source code5 formatter that's on the freeware disk and come acrossw
 a feature.  5 Indent will sometimes insert extra blank lines in and.6 after comments in C source files, for example changing this source:     /*    * A comment    */    To this:     /*      * A comment      */t  2 The culprit is the following line of code in io.c:  -   fwrite (com_st, e_com - com_st, 1, output);h  ) Changing it to an fprintf() fixes things:k  3   fprintf (output, "%.*s", e_com - com_st, com_st);e  3 The root of the problem is the sometimes surprisingd/ way Compaq C treats fwrite()s to a text stream.m  ( I have reported this to Indent's author.   Regards,   	Phil Ti   ------------------------------  # Date: Wed, 09 May 2001 16:02:06 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)# Subject: Re: FYI: Bug in VMS indent-0 Message-ID: <2SdK6.54$fi2.1954@news.cpqcorp.net>  q In article <01c0d881$cba14ae0$4b53b083@ptregoni.dev.esoc.esa.de>, "Phil Tregoning" <ptregoni@esoc.esa.de> writes:   7 :I've been playing with Indent, a C and C++ source codeB6 :formatter that's on the freeware disk and come across :a feature.a  +   The freeware V5 version, I will assume.     J   Please send along an updated kit, and I will add it to the next release.    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  * Date: Wed, 9 May 2001 13:59:03 +0000 (UTC)' From: david20@alpha1.mdx.ac.uk (D.Webb) 3 Subject: Re: How to repair corrupted ACCOUNTNG.DAT?S+ Message-ID: <9dbif7$bqp$1@aquila.mdx.ac.uk>S  V In article <3AF8D628.778D2512@ui.urban.org>, Jim Becker <jbecker@ui.urban.org> writes:E >A crude hack that has worked for me before went something like this:  >o >$ open /read bad accountng.badt" >$ open /write good accountng.good	 >$ again:s% >$ read /error=again /end=eof bad reco >$ write good recn
 >$ goto againr >$ eof:o >$ close bad
 >$ close goodn >uD >You lose data right around the corrupted spot, but at least you get >records after it. >    Why not   2 ACCOUNT/BINARY/OUT=NEWACCOUNTNG.DAT  ACCOUNTNG.DAT  
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------  $ Date: Wed, 9 May 2001 09:10:30 -04002 From: "Sue Skonetski" <susan.skonetski@compaq.com>6 Subject: IBM announces MQSeries V5.1 for OpenVMS/Alpha0 Message-ID: <zlbK6.43$fi2.1807@news.cpqcorp.net>   Dear Newsgroup  L Over the last months I've seen a number of questions on this list concerning& IBM's support for MQSeries on OpenVMS.  K IBM has just announced the availability of MQSeries V5.1 for OpenVMS/Alpha, B V7.2 -1 or V7.3. Full details of the announcement can be found at:C <http://www.ibm.com/software/ts/mqseries/messaging/openvmsv51/> andsL <http://www.ibm.com/software/ts/mqseries/messaging/openvmsv51/factsheet.html >.  
 Warm Regards,y       Sue    ------------------------------   Date: 9 May 2001 15:14:28 GMTa2 From: mathog@seqaxp.bio.caltech.edu (David Mathog): Subject: Re: IBM announces MQSeries V5.1 for OpenVMS/Alpha, Message-ID: <9dbmsk$luf@gap.cco.caltech.edu>  e In article <zlbK6.43$fi2.1807@news.cpqcorp.net>, "Sue Skonetski" <susan.skonetski@compaq.com> writes:h >oM >Over the last months I've seen a number of questions on this list concerning ' >IBM's support for MQSeries on OpenVMS.e >nL >IBM has just announced the availability of MQSeries V5.1 for OpenVMS/Alpha, >V7.2 -1 or V7.3.   K Oddly, starting from the top of the MQSERIES pages I could not find a link o to the page you cited:  ?   http://www.ibm.com/software/ts/mqseries/messaging/openvmsv51/   = although the page clearly does exist.  There _was_ a link to n  =   http://www-4.ibm.com/software/ts/mqseries/platforms/vmsaxp/o   from the list of platforms  6   http://www-4.ibm.com/software/ts/mqseries/platforms/  J which is on the main mqseries page, but that VMS link is for older versionI (V2.1) of the software.  In fact, every link on that page seems to be for ? older versions.  The current version seems to be 5.2 or 5.2.1. o  J Ah, I just found a link to the new VMS page from the "MQSeries Family May  Announce" page:r  8   http://www-4.ibm.com/software/ts/mqseries/mayannounce/  E The VMS Alpha 5.1 version is listed as being available May 25,2001.  i? Unclear if the older version for VAX is still available or not.    Regards,   David Mathog mathog@caltech.edu? Manager, sequence analysis facility, biology division, Caltech NJ **************************************************************************J *                                RIP VMS                                 *J **************************************************************************   ------------------------------  $ Date: Wed, 9 May 2001 11:21:30 -0400- From: "Peter Weaver" <peter.weaver@stelco.ca>g: Subject: Re: IBM announces MQSeries V5.1 for OpenVMS/Alpha4 Message-ID: <dgdK6.235861$Z2.2537854@nnrp1.uunet.ca>  = "Sue Skonetski" <susan.skonetski@compaq.com> wrote in messagei* news:zlbK6.43$fi2.1807@news.cpqcorp.net... > ...i> > IBM has just announced the availability of MQSeries V5.1 for OpenVMS/Alpha,D > V7.2 -1 or V7.3. Full details of the announcement can be found at: >...     Also note item Q1 atF http://www-4.ibm.com/software/ts/mqseries/messaging/openvmsv51/faq.htm l;   ============ Start Quote@ Q1. Previous MQSeries level for OpenVMS included support for VAXD hardware systems. Why has that not been continued for MQSeries V5.1?B A1. The MQSeries V2.2.1.1 for OpenVMS on VAX hardware systems willD continue to be a marketed offering MQSeries option for that specific? platform combination. Compaq have announced end of life for VAXoF hardware, and end of sales as Sept2000, indicating no new developmentsC would be done for the OpenVMS operating system on the VAX platform,dD except those vital to interoperability issues with Alpha. Compaq areC encouraging their own customer base to move onto the newer and moref efficient Alpha hardware base. ============ End Quote  F Anybody know of good replacements for MQSeries that still runs on VAX?   ------------------------------    Date: 09 May 2001 19:15:03 +0800, From: Paul Repacholi <prep@prep.synonet.com>/ Subject: Re: Microsoft web sites hacked (again)s- Message-ID: <87vgnayds8.fsf@prep.synonet.com>   / JF Mezei <jfmezei.spamnot@videotron.ca> writes:i  B > For those who want more ammunition that MS software isn't quirte > ready for prime time.   6 > http://public.wsj.com/sn/y/SB988994781918090944.html  C > Computer intruders managed to gain control of three internationalpF > Microsoft Corp. home pages on Thursday, replacing the company's dataF > with a simple message taunting the software giant. Microsoft's U.K.,D > Mexico and Saudi Arabia sites were replaced with messages from the > hacker group Prime Suspectz.  F >  The defacements come two days after Microsoft revealed its flagshipE > Web server software had a serious vulnerability, but it's not knownlB > if the intruders used that vulnerability to attack the MicrosoftC > sites. In a related development, a computer hacker published codeEB > Wednesday night that makes taking advantage of the new Microsoft8 > flaw easy for any ill-intentioned computer programmer.  @ It is worse than that. (OK, worse and M$ is kind of stupid, but)  > There is currently a worm doing the tour of IIS on Windows andC Solaris.  Well, the stupid Solaris sites anyway. It is a variant ofaB the IIS buffer overflow. See TheRegister for the horrid details.... e-mail if you want a copy of the doze smasher.   -- d< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.p@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov s   ------------------------------  % Date: Wed, 09 May 2001 08:45:59 +0200c- From: Jouk Jansen <joukj@hrem.stm.tudelft.nl>n; Subject: Re: mounting 2 disk with the same label in clustert3 Message-ID: <3AF903C7.38719043@hrem.stm.tudelft.nl>n    Gotfryd Smolik, VMS lists wrote: > % > On Tue, 8 May 2001, JF Mezei wrote:G > I > >+> >  %MOUNT-F-VOLALRMNT, another volume of same label already mountedtP > >+> > Is there any possibility to overcome this problem on OpenVMS-alpha 7.2-1$ > >+> > without changing the labels? > >+Q > >+I have not tried this, but have you considered playing with the logical namess% > >+created when a drive is mounted ?  > >+  > >+for instance DISK$volumename > >+Q > >+If you were to delete that logical and create a new one such as DISK$volname1aR > >+then *perhaps* when you mount the second drive with the same volume label, VMS > >+might not see a conflict.n > ? >  Perhaps ;) VMS will use the label as the filesystem name, to - > be precise as the cluster-wide lock name :)s >  Check with ANAL/SYS :)tE With a quick check I could not find this. What command of SDA did youi
 have in mind?9   > 5 > >+ You'll have to create the logical with teh exactv' > >+same attriutes as the original one.0 > @ >  Be aware the fact that the logname *must not* be the problem,8 > because if the device is not /CLUSTER mounted the name= > is only local (/SYSTEM on the nodes, where is mounted - note > on whole cluster)r > '  Right, the logical is NOT the problem.n     What I actually try to do:D    -I have a NFS mounted disk on some Unix System mounted on all the%      nodes on the cluster ( NFS$DISK)lH    -On this disk I created with LD063 (freeware CD5.0) a file containing      a VMS file system        i.e.n;           LD CREATE /size=1300000 NFS$DISK:[vms]vmsdisk.dskl4           LD CONNECT NFS$DISK:[vms]vmsdisk.dsk lda1:           init lda1: label1e(    -I repeat on each node of the cluster4           LD CONNECT NFS$DISK:[vms]vmsdisk.dsk lda1:@       Note that the /SHARE qualifier does not work in this case.@    -I can mount the filesystem on only one member of the cluster:      with /SYSTEM. I would like to do this on all members.B      /CLUSTER does not work since the LDxx devices are not cluster>      transparent. (or can LD been such configured that this is      the case?)p                          Jouk:   ------------------------------    Date: 09 May 2001 10:22:08 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>n; Subject: Re: mounting 2 disk with the same label in cluster.H Message-ID: <y4heyvkk3z.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  / JF Mezei <jfmezei.spamnot@videotron.ca> writes:d  O > If you were to delete that logical and create a new one such as DISK$volname1lM > then *perhaps* when you mount the second drive with the same volume label, l  > VMS might not see a conflict.   K No, that doesn't help. MOUNT creates a system-wide - and in a cluster, thataN means cluster-wide - lock on a resource that is formed from the label name forK any volume (this includes tapes, of course) that is accessible to more thanrH one job tree - i.e., any volume mounted /GROUP, /SYSTEM or /CLUSTER (theI latter just being a shorthand for saying "please ask all CLUSTER_SERVERs  N in the cluster to perform the same MOUNT command for me"). (In fact, dependingM on the file system on the disk, MOUNT creates multiple such locks on multiplem: such resources, but one is enough to trigger the problem.)  K It would be a very complex redesign of the resources used to control access H to shared volumes if this behaviour were to be changed. I can't see that happening any time soon...   	Jan   ------------------------------    Date: 09 May 2001 18:39:39 +0800, From: Paul Repacholi <prep@prep.synonet.com>; Subject: Re: mounting 2 disk with the same label in clusters- Message-ID: <874ruuztzo.fsf@prep.synonet.com>   / Jouk Jansen <joukj@hrem.stm.tudelft.nl> writes:t  C > I would like to mount on two members of my cluster two disks withkC > the same label, one on each member. However if I try to mount theOD > second one I get the message %MOUNT-F-VOLALRMNT, another volume ofF > same label already mounted Is there any possibility to overcome this= > problem on OpenVMS-alpha 7.2-1 without changing the labels?    NO!t  D No amount of fideling with logicals etc will touch the real problem.A The file-system code uses the label in the home block to create a"+ RSB for the volume. These *MUST* be unique.   A The only way to mount the two volumes with the same label clustero wide is to re-write the XQP.   Or change one label.   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.l@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov     ------------------------------  % Date: Wed, 09 May 2001 10:12:46 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> ; Subject: Re: mounting 2 disk with the same label in cluster1, Message-ID: <3AF9505D.ACD6742F@videotron.ca>   Alphaman wrote:uN > I like the DISK$label logicals as I know that they will be there if the diskC > drive is accessible.  The third parameter in the Mount command isdG > optional -- you can leave it off, but DISK$label will still be there.   I I use the logical created with the optional parameter of MOUNT because it I provides a level of independance from the hardware and makes it easier to * combine drives or move a drive around etc.  K The volume label is a nice security feature to ensure that you are mountingmB the right drive, but apart from that, I have never made use of it.   ------------------------------   Date: 9 May 2001 11:17:38 -0500u From: briggs@encompasserve.org; Subject: Re: mounting 2 disk with the same label in cluster,3 Message-ID: <NRHZxa0QXQTS@eisner.encompasserve.org>o  \ In article <3AF81154.E4B9E418@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: > john nixon wrote:s >> lO >> You cannot do what you are asking.  Perhaps if you described the problem youcJ >> are trying to overcome someone could offer you an alternative solution. > P > If you do a SET VOLUME/LABEL="newlabel", it doesn't seem to change the logicalW > names that are created when the drive was mounted, so the conflict woult still exist.o  ( You are proceeding from a false premise.  O Logical names have nothing to do with this.  The distributed lock manager does.oG When a disk is mounted, a lock is taken out on a resource name that is aN constructed from the volume label.  Any attempt to mount a disk with the same  label will encounter the lock.  N If you mount the new disk privately, SET VOLUME /LABEL on it, dismount it and . then mount it again /SYSTEM, all will be well.   (System A):l  # $ MOUNT /SYSTEM DKA1: MYDISK MYDISK- 	- (System B):-   $ MOUNT DKB2: MYDISK MYDISK1# $ SET VOLUME MYDISK /LABEL=MYDISK_Xz $ DISMOUNT /NOUNLOAD DKB2)% $ MOUNT /SYSTEM DKB2: MYDISK_X MYDISKp       John Briggsg   ------------------------------   Date: 9 May 2001 10:00 CST' From: carl@gerg.tamu.edu (Carl Perkins)e1 Subject: Mystery of the misreported graphics cardS, Message-ID: <9MAY200110005881@gerg.tamu.edu>  A So here I am switching some DEC 3000m600 systems from VMS V6.1 toa> V7.2-1. Naturally, I need to update the firmware (they had the? firmware version they shipped with in 1994). I did that on one.a@ Then DECwindows fails to operate properly on it when booted withD V6.1 - the processes run, but the console display keeps being shown,? except for the bottom 1/2" or so of the screen. It is unuseableiE as either DECwindows or as the console (and control-F2 does nothing).-A Everything else on the system is running fine. On the other hand,-" it all works fine with VMS V7.2-1.  ' Then I discovered something really odd.c  A I went to check the graphc card firmware to see if also it neededeB updating, assuming that it did and that the problem under V6.1 was1 a system firmware/card firmware mismatch problem.b  > My DEC 3000m600 systems claim that they have PMAGB-BA graphics= cards in them with the "show config" at the console prompt. Ie+ always thought that that was what they had.w  @ The Turbochannel device firmware updater thingy, when booted up,= thinks that they are PMAGB-BA cards. Except that the checksumA@ doesn't match, even though it claims they have the same firmware< version (V1.1 - the version on the Firmware Update V5.8 CD).  * I figured something strange had happened.   A So I open it up (initially just with the intention of setting the,; firmware update jumper so I could "update" or "repair" it).s  E I'm not absolutely certain what the card is, but it definately is not C a PMAGB-BA. It is presumably some variety of PMAGB-B, since it says-C as much on it (even before you pop the box open - it's printed next  to the video connector).  @ It has two oscilators labeled as being 130.808MHz and 74.369MHz.A Based on that, I am assuming that it is a PMAGB-BC. It has a part1A number of "50-21142-01 D1" on it, which I can not locate anywhereeD useful, just some archived SPAM that list for sale a DEC 3000 system@ with a "50-21142-01" graphics card (but doesn't identify it withB a PMAGB-Bx type name). On the exterior, near the "PMAGB-B" text isB some fine print that says "36-36966-01.A01", which does not appear" in any usefull context on the web.  . Which brings us to the question and a comment:  B Why is it that this card, probably a PMAGB-BC, is being identifiedA by both the system's console and the TC_V2_2.SYS firwmare updateri code as being a PMAGB-BA?-  F At any rate, there is no firmware update for it on the Firmware UpdateC V5.8 CD. Unless the system's firmware can be downgraded to whatever5A the original version was (via the firmware CD that came with it),:F this VMS upgrade is one-way as far as the capacity to use the graphicsB display is concerned.  Also, had I blindly believed that it reallyB was a PMAGB-BA, I would have just hit it with the wrong firmware -D which may very well make it completely non-functional (and, at leastF on the newer CD there is no firmware for it to resotre it to anys sortE of functional condition - I havn't checked the old 1994 vintage CD tof see if it has any on there).  G The moral of the story: Don't beleive everything you read. Just becausetE your system says it has some specific type of hardware attached to it. doesn't mean that it does.   --- Carl   ------------------------------  % Date: Wed, 09 May 2001 12:20:13 +0100-  From: steven.reece@quintiles.com/ Subject: Re: Oracle Parallel Server on OpenVMS?iH Message-ID: <OF008E7C6C.515C6720-ON80256A47.003DFD2A@qedi.quintiles.com>  F I take it that screams is screaming positively rather than negatively?C If so, is it really that different that "classic" Oracle on VMS (my G experience suggests that it might be) and if, in trun, this is the caselK then why the difference?  Parentage?  Preference on Oracle's part?  Lack off, functionality in one product over the other?   Steve.   Hoff quoted/commented: >>>o? :We are currently evaluating a solution for a high availabilityi6 :database solution which should run on a GS80 cluster. .u :-RDB on OpenVMS...-  #   Oracle Rdb performance screams...4 <<<M   ------------------------------   Date: 9 May 2001 07:40:52 -0500I9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)9/ Subject: Re: Oracle Parallel Server on OpenVMS?K3 Message-ID: <DRzDpinLCofR@eisner.encompasserve.org>a  k In article <OF008E7C6C.515C6720-ON80256A47.003DFD2A@qedi.quintiles.com>, steven.reece@quintiles.com writes:n > H > I take it that screams is screaming positively rather than negatively?E > If so, is it really that different that "classic" Oracle on VMS (my I > experience suggests that it might be) and if, in trun, this is the casekM > then why the difference?  Parentage?  Preference on Oracle's part?  Lack ofn. > functionality in one product over the other? >  > Steve. >  > Hoff quoted/commented: >>>>A > :We are currently evaluating a solution for a high availabilityf8 > :database solution which should run on a GS80 cluster. > .o > :-RDB on OpenVMS...  > % >   Oracle Rdb performance screams...r > <<<v  F "Classic" Oracle is portable between operating systems, which _always_G slows down performance compared to something well-written for VMS.  Ando9 I rarely use the term "always" when discussing computers.Q   ------------------------------    Date: 09 May 2001 21:41:41 +0800, From: Paul Repacholi <prep@prep.synonet.com>/ Subject: Re: Oracle Parallel Server on OpenVMS?1- Message-ID: <87eltyy6zu.fsf@prep.synonet.com>t  " steven.reece@quintiles.com writes:  < > I take it that screams is screaming positively rather than@ > negatively?  If so, is it really that different that "classic"D > Oracle on VMS (my experience suggests that it might be) and if, in1 > trun, this is the case then why the difference?   9 8i is a unix port. How fast can you say 'context switch'.*  E >  Parentage?  Preference on Oracle's part?  Lack of functionality in1 > one product over the other?e  ( RDB include GEM for compiling the query.  B Look at the Oracle RDB stuff on Oracles site from their roadshows.   -- 3< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.c@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov f   ------------------------------  % Date: Wed, 09 May 2001 11:15:21 -0400o- From: Michael Austin <miaustin@bellsouth.net>l/ Subject: Re: Oracle Parallel Server on OpenVMS?h- Message-ID: <3AF95F09.FB63997E@bellsouth.net>h   Larry Kilgallen wrote:  i > In article <3af86554$0$21056$62ce1842@SSP1NO55>, "Robert Schmoelzer" <robert.schmoelzer@aon.at> writes:t >m > > -RDB on OpenVMSh< > >     seems technically great but limited support by local! > >     Compaq and Oracle people;e >m  b Obviously Rdb's technical support is still in Colorado Springs,  There may not be very many Oraclef (employee) consultants available for Rdb work , but there are quite a few of us who make our living ink Rdb.  I will actually be available within the next few weeks.  Most of the consultants who are independentseb actually have more experience than those in local offices for Oracle or Rdb and a number of us are ex-DECCIEs.p  f IMHO, OPS cannot hold a candle to Rdb in a cluster.  As far as features go, it depends on what you aref looking for.  Developer/Designer works with Rdb, SQL*Net transport works with Rdb 7.0.2+.  I  have web` enabled databases using the Rdb Web Cartridge on Apache and OSU web servers.  It also works withh OA[pplication]Server, but this requires a 3 tier solution with WNT or u**x for the OAS piece. OpenVMS isi much more stable, Rdb is extremely stable.  If you absolutely gotta have 24x7x365, Rdb on OpenVMS is yourwg only bet. ..and scalable... I know of a system where the database was ~5TB a year or so ago, and BTW isk, managed by Compaq Services in Colo. Springs.  i It is amazing to me how customers wanted Highly available systems yet put up with the constant reboots ofie WNT and u**x systems on a sometimes daily basis.  Not to mention the downtime associated with Oracle.eg (upgrades take many  hours compared to the simple upgrade of Rdb  - usually done in minutes. and not asw frequently.)   >e: > It seems to me there is great support via the Oracle Rdb6 > mailing list maintained by JCC Systems, with lots of, > participation from savvy Oracle employees.  g not to mention the *available* consultants who specialize in Rdb and some of us can do ANY dba functionoj sitting right here in our comfortable HOME office.  All that is required is a VPN connection to your site.i (BTW, I have been working at an extremely large pharmaceutical company working from home every other weekK/ providing mission-critical production support.)    Michael Austin First DBA Source, Inc. 704-947-1089   ------------------------------   Date: 9 May 2001 12:26:01 -0500c9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)s/ Subject: Re: Oracle Parallel Server on OpenVMS?03 Message-ID: <WaToHYA6SFRa@eisner.encompasserve.org>h  ] In article <3AF95F09.FB63997E@bellsouth.net>, Michael Austin <miaustin@bellsouth.net> writes:3 > Larry Kilgallen wrote: > j >> In article <3af86554$0$21056$62ce1842@SSP1NO55>, "Robert Schmoelzer" <robert.schmoelzer@aon.at> writes: >> >> > -RDB on OpenVMS= >> >     seems technically great but limited support by locali" >> >     Compaq and Oracle people;  ; >> It seems to me there is great support via the Oracle Rdb 7 >> mailing list maintained by JCC Systems, with lots ofw- >> participation from savvy Oracle employees.e > i > not to mention the *available* consultants who specialize in Rdb and some of us can do ANY dba function 4 > sitting right here in our comfortable HOME office.  G Far be it from me to downplay the usefulness of independent consultantsoI (who can probably be more honest about the differences between Oracle RdbtH and Oracle Classic).  The concern in the original post seemed to be thatJ nobody who worked for Oracle knew about Rdb.  With that concern addressed,I it may very well be that assistance other than from Oracle might be quitetH appropriate.  But I can understand how a question about support from theC vendor might be the first question from someone (or their manager).d   Larry KilgallenE   ------------------------------  % Date: Wed, 09 May 2001 13:46:31 -0400 - From: Michael Austin <miaustin@bellsouth.net>o/ Subject: Re: Oracle Parallel Server on OpenVMS?r- Message-ID: <3AF98277.6E525C3E@bellsouth.net>    Paul Repacholi wrote:l  $ > steven.reece@quintiles.com writes: >l> > > I take it that screams is screaming positively rather thanB > > negatively?  If so, is it really that different that "classic"F > > Oracle on VMS (my experience suggests that it might be) and if, in3 > > trun, this is the case then why the difference?e > ; > 8i is a unix port. How fast can you say 'context switch'.N >D  J Actually, there is an 8i version for OpenVMS or should be out shortly.  8iJ is a unix port of Oracle Oracle (6,7,8,8i,9,9i) ... has nothing to do withJ Rdb.  Prior to about Oracle6.0 the primary development platform for OracleL was OpenVMS.   Then it was ported to all of the Unix flavors.  After 6.0 ( IL think this is correct) the primary development platform was Sun Solaris. And then ported back to OpenVMS.  J Rdb on the other hand only had one unix port and it was OSF1.  Once OracleJ bought Rdb from Digital, the OSF1 version of Oracle effectively died.  Rdb4 development still continues on the OpenVMS platform.  H In terms of features, they are very close.  In terms of maintenance, RdbL still wins hands down.  For example: to do a true online backup on an OracleI database requires a huge script (last one I wrote was some 300 lines long J for a relatively small database).  For Rdb you just add one more qualifierJ to the rmu/backup command:  "/online".  In some unix flavors you are stillJ limited to a 2G or 4G file size.  How many of these do you need to build aJ 5Tb database?  Rdb can also restore a SINGLE page to the database and makeI it consistent.  With traditional Oracle, you restore the entire data fileSJ and or tablespace and hope all of your redo log files are still around andE functional.  Have you ever tried to get "real-time" statistics out ofnI Oracle. Nothing but a bunch of scripts that run at a given point in time,c2 not in real-time.  Although OEM is getting better.  L Again, IMHO.... STAY WITH RDB, YOU WILL HAVE MANY FEWER HEADACHES.  The costG is about the same for the large class systems so it is  a moot point to I change.  Unless you no longer want the stability and uptime of an OpenVMS- cluster.   Michael Austin First DBA Source, Inc.. Senior DBA Consultant (Rdb and classic Oracle) 704-947-1089  (Office)     >iG > >  Parentage?  Preference on Oracle's part?  Lack of functionality inn > > one product over the other?e >t* > RDB include GEM for compiling the query. >nD > Look at the Oracle RDB stuff on Oracles site from their roadshows. >e > --> > Paul Repacholi                               1 Crescent Rd.,9 > +61 (08) 9257-1001                           Kalamunda.rB >                                              West Australia 60760 > Raw, Cooked or Well-done, it's all half baked.J > Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,$ >   mpowell@fcc.gov,gtristan@fcc.gov   ------------------------------  $ Date: Wed, 9 May 2001 09:18:21 -06004 From: "Michael D. Ober" <mdo.@.wakeassoc.com.nospam> Subject: Processor Affinityi2 Message-ID: <4ddK6.1911$VX.126461@news.uswest.net>  D Under WinNT, a process can be switched between processors while it'sL running.  Is this true under VMS 7.2-1?  If so, I need a source reference to
 show my boss.  -- Thanks,a
 Mike Ober.   ------------------------------  % Date: Wed, 09 May 2001 16:31:31 +0100e  From: steven.reece@quintiles.com Subject: Re: Processor AffinitytH Message-ID: <OF33351634.B52AD255-ON80256A47.00550C26@qedi.quintiles.com>  J Do you mean whilst the process is in existance or do you mean when the cpuK is actually working on it?  If the former then of course - it's part of theFJ scheduling.  If the latter then I'd guess no, unless the cpu needs to deal with an interrupt. Steve.   Michael D, Ober wrote: >>>lD Under WinNT, a process can be switched between processors while it'sI running.  Is this true under VMS 7.2-1?  If so, I need a source referencer to
 show my boss.o <<<a   ------------------------------   Date: 9 May 2001 12:35:40 -0500h9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)a Subject: Re: Processor Affinityl3 Message-ID: <EdsNnP59WHmV@eisner.encompasserve.org>e  k In article <OF33351634.B52AD255-ON80256A47.00550C26@qedi.quintiles.com>, steven.reece@quintiles.com writes:- > L > Do you mean whilst the process is in existance or do you mean when the cpuM > is actually working on it?  If the former then of course - it's part of thenL > scheduling.  If the latter then I'd guess no, unless the cpu needs to deal > with an interrupt. > Steve. >  > Michael D, Ober wrote: >>>>F > Under WinNT, a process can be switched between processors while it'sK > running.  Is this true under VMS 7.2-1?  If so, I need a source references > to > show my boss.d > <<<   E When the CPU is working on it there will be periodic clock interruptshE for quantum end, and at that point a change in CPU might be possible.eB It would be a Bad Idea(tm) in most cases, however, because the CPUD cache and translation buffers are already set up for that process onE the current CPU.  That is why in most cases you are better off to let A VMS move the process back and forth between CPUs based on what ithE knows about the situation, rather than attempting to manually control E it.  If you are concerned about "fairness" of a non-technical nature,i@ such as which department paid for the hardware, there has been aB Class Scheduler system service available for years.  V7.3 promises- a more friendly interface to that capability.U  ? The only case where concern about which processor is used mightoA be when using a Wildfire GS(80*n) system and concerned about NUMA:? effects.  Presumably that is not your concern if you are makingy comparison to Windows NT.s  B And of course if you are using DECthreads on that Alpha (includingA either Compaq Ada or GNAT tasking), your process could be runninga" on multiple CPUs at the same time.   ------------------------------  # Date: Wed, 09 May 2001 12:31:44 GMToB From: Simon Clubley <simon_clubley@remove_me.excite.com-Earth.UFP>4 Subject: Programming language usage on VMS systems ?6 Message-ID: <QMaK6.7475$vg1.610094@www.newsranger.com>  G I have been curious for a while about which languages are in use on VMSoC systems and what percentage of systems these languages run on. Doesn9 anybody have an idea of what this distribution might be ?   C It would be interesting to know as well what the distribution is inc@ the installed base (VAX and/or Alpha) as well as in new systems.  F [I have no specific reason for the information, I am just interested.]   Thanks for any information,3   Simon.   -- l; Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFP"J 'The statement that "it can never happen" is not an acceptable programmingH approach. You must assume it can happen and be in control when it does.'=           -- Ada 95 Quality and Style Guidelines, US DoD AJPOu   ------------------------------  % Date: Wed, 09 May 2001 09:25:12 -0400o# From: Jim Agnew <Agnew@hsc.vcu.edu> 8 Subject: Re: Programming language usage on VMS systems ?+ Message-ID: <3AF94538.F5CE3340@hsc.vcu.edu>t  j we use Fortran, Ingres Quel, Ingres SQL, Perl, C, dcl, and oh, yeah, odbc to frontend ingres with access..   Simon Clubley wrote: > I > I have been curious for a while about which languages are in use on VMSAE > systems and what percentage of systems these languages run on. Does ; > anybody have an idea of what this distribution might be ?c > E > It would be interesting to know as well what the distribution is inuB > the installed base (VAX and/or Alpha) as well as in new systems. > H > [I have no specific reason for the information, I am just interested.] >  > Thanks for any information,  >  > Simon. >  > --= > Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFP.L > 'The statement that "it can never happen" is not an acceptable programmingJ > approach. You must assume it can happen and be in control when it does.'? >           -- Ada 95 Quality and Style Guidelines, US DoD AJPOi   ------------------------------  % Date: Wed, 09 May 2001 09:25:37 -0400o# From: Jim Agnew <Agnew@hsc.vcu.edu>e8 Subject: Re: Programming language usage on VMS systems ?+ Message-ID: <3AF94551.4A4BFD38@hsc.vcu.edu>e  < i forgot, TECO code is in use also, as well as vax-11 macro.   jim    Jim Agnew wrote: > l > we use Fortran, Ingres Quel, Ingres SQL, Perl, C, dcl, and oh, yeah, odbc to frontend ingres with access.. >  > Simon Clubley wrote: > >,K > > I have been curious for a while about which languages are in use on VMS G > > systems and what percentage of systems these languages run on. Doesf= > > anybody have an idea of what this distribution might be ?f > > G > > It would be interesting to know as well what the distribution is ineD > > the installed base (VAX and/or Alpha) as well as in new systems. > >sJ > > [I have no specific reason for the information, I am just interested.] > >o > > Thanks for any information,c > >o
 > > Simon. > >n > > --? > > Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFP,N > > 'The statement that "it can never happen" is not an acceptable programmingL > > approach. You must assume it can happen and be in control when it does.'A > >           -- Ada 95 Quality and Style Guidelines, US DoD AJPO    ------------------------------   Date: 9 May 2001 08:51:26 -0500t9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)t8 Subject: Re: Programming language usage on VMS systems ?3 Message-ID: <sgL4hxQtUL3v@eisner.encompasserve.org>p  { In article <QMaK6.7475$vg1.610094@www.newsranger.com>, Simon Clubley <simon_clubley@remove_me.excite.com-Earth.UFP> writes:aI > I have been curious for a while about which languages are in use on VMSuE > systems and what percentage of systems these languages run on. Doesn; > anybody have an idea of what this distribution might be ?e > E > It would be interesting to know as well what the distribution is inyB > the installed base (VAX and/or Alpha) as well as in new systems. > H > [I have no specific reason for the information, I am just interested.] >  > Thanks for any information,t >  > Simon. >  > -- u= > Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFP L > 'The statement that "it can never happen" is not an acceptable programmingJ > approach. You must assume it can happen and be in control when it does.'? >           -- Ada 95 Quality and Style Guidelines, US DoD AJPOg  . I would expect more precision from an Ada fan.  B By "language use", do you mean execution or compilation machines ?; If execution, do you want to include third party products ?o How about layered products ?> Do you want a raw count of machines, or hours per language per machine per year ?; Would that be absolute hours or percentage of total hours ?s  ? Presumably you don't want to count languages that are installedl= but never used (if it is only compilation that concerns you)..   =======a  @ I hope the above can be of help in formatting your actual survey? questions.  Figuring out how to get back a scientific sample isa well beyond my capabilities.   ------------------------------  % Date: Wed, 09 May 2001 15:02:37 +0200t= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>e8 Subject: Re: Programming language usage on VMS systems ?) Message-ID: <3AF93FED.E76F5FF6@gtech.com>y   Simon Clubley wrote:I > I have been curious for a while about which languages are in use on VMSnE > systems and what percentage of systems these languages run on. Doesr; > anybody have an idea of what this distribution might be ?P > E > It would be interesting to know as well what the distribution is intB > the installed base (VAX and/or Alpha) as well as in new systems. > H > [I have no specific reason for the information, I am just interested.]  ; It is very difficult to estimate. Based on questions posted-: here and my guesses, then I would estimate something like:  )              existing code       new code0& Macro-32          10%               0%& Fortran           20%              10%& Pascal            10%               0%& C                 30%              60%& C++                5%              20%& other             25%              10%  3 (other = Cobol, Basic, PL/I, RPG, Ada, Bliss, Java):  > There were written a lot of Macro-32 in the good old VAX days.  / Fortran has always been a huge language on VMS.   8 VMS Pascal is actually a very nice Pascal, but has never been very widely used.  0 C started late on VMS, but it is dominant today.  - C++ has not really had its break-through yet.   5 There are ofcourse a lot of old Cobol code out there.u   Ada has its standard DoD niche.l  2 VMS Basic actually have quite a big niche with its loyal followers.  5 Bliss was/is big within Digital/Compaq, but has nevere
 spread a lot.e  ; Java is availabel on VMS, but has not really taken off yet.e   Arne   ------------------------------  % Date: Wed, 09 May 2001 16:09:31 +0200p+ From: Jimmi Aakjaer <aakjaer@post7.tele.dk>e8 Subject: Re: Programming language usage on VMS systems ?8 Message-ID: <kpjiftsn0qndci09glg05ha9998bd55ct0@4ax.com>   Hi  A We are using Pascal(25%) ,Cobol (25%) and Cognos Powerhouse (4GL)w/ (50%) and are still developing in all languages    /Jimmi  / On Wed, 09 May 2001 12:31:44 GMT, Simon Clubleyn5 <simon_clubley@remove_me.excite.com-Earth.UFP> wrote:l  H >I have been curious for a while about which languages are in use on VMSD >systems and what percentage of systems these languages run on. Does: >anybody have an idea of what this distribution might be ? >nD >It would be interesting to know as well what the distribution is inA >the installed base (VAX and/or Alpha) as well as in new systems.o >pG >[I have no specific reason for the information, I am just interested.]m >e >Thanks for any information, >s >Simon.    ------------------------------  # Date: Wed, 09 May 2001 11:01:39 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)o! Subject: Re: SYSMAN and SMISERVERl0 Message-ID: <009FBBDE.5BA7BB2D@SendSpamHere.ORG>  d In article <9dakrg$3i2$1@gossamer.itmel.bhp.com.au>, "Dick Adams" <adams.dick.rc@bhp.com.au> writes:J >Thanks Brian but I'm afraid the online docs are not able to enlighten me. >e" >To rephrase my original question.J >I don't understand why SYSMAN commands work to all the nodes which do not; >have SMISERVER running (and aren't in cluster) except one?n >i >Some more information. K >When I SET ENVIRONMENT /NODE=(node1,...) it prompts me for the password tooJ >use on remote nodes, I can sign on to all the nodes using the same useridJ >and password. When I issue a command such as DO SHOW TIME, it executes onB >all nodes until it get to the one in question, it then fails with >c> >"SYSTEM-F-INVLOGIN, login information invalid at remote node" >eM >On the target node the accounting records show a login failure with a useridcH >of ILLEGAL and final status text of "%LOGIN-F-NOSUCHUSER, no such user" > J >This is not actually causing me a problem as I can start up SMISERVER andH >everything works as expected, but, why is one node different to all the >others?  7 DECnet phase IV or V running on the problematic target?s  ( Look at the SMISERVER object definition:  	 Phase IV:>/ $ MCR NCP SHOW OBJECT SMISERVER CHARACTERISTICSa   Phase V:O $ MCR NCL SHOW NODE 0 SESSION CONTROL APPLICATION SMISERVER ALL CHARACTERISTICSv   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMn             O city, n., 1. a place where trees are cut down and streets are named after them.c   ------------------------------  % Date: Wed, 09 May 2001 10:14:44 -0400t- From: JF Mezei <jfmezei.spamnot@videotron.ca>d! Subject: Re: SYSMAN and SMISERVER , Message-ID: <3AF950D3.71C5B8BC@videotron.ca>   Dick Adams wrote:tK > I don't understand why SYSMAN commands work to all the nodes which do not < > have SMISERVER running (and aren't in cluster) except one? >  > Some more information.L > When I SET ENVIRONMENT /NODE=(node1,...) it prompts me for the password toK > use on remote nodes, I can sign on to all the nodes using the same userid- > and password  ? > "SYSTEM-F-INVLOGIN, login information invalid at remote node"u  1 Have you tried SET ENV/NODE=node/USER=username  ?a   ------------------------------  % Date: Wed, 09 May 2001 12:37:10 -0400 5 From: David Beatty <David.Beatty@qwertysasasdfgh.com>m! Subject: Re: SYSMAN and SMISERVERr2 Message-ID: <43H5OokW4FPYsV0UmUWzLhRWphLG@4ax.com>  ? Do you by any chance have Decnet proxies setup for your accounteA across the cluster?  That will allow you to use SYSMAN across ther& cluster without the use of a password.   David R. Beatty   / On Wed, 9 May 2001 15:31:30 +1000, "Dick Adams"N! <adams.dick.rc@bhp.com.au> wrote:r  J >Thanks Brian but I'm afraid the online docs are not able to enlighten me. >6" >To rephrase my original question.J >I don't understand why SYSMAN commands work to all the nodes which do not; >have SMISERVER running (and aren't in cluster) except one?a >s >Some more information.hK >When I SET ENVIRONMENT /NODE=(node1,...) it prompts me for the password torJ >use on remote nodes, I can sign on to all the nodes using the same useridJ >and password. When I issue a command such as DO SHOW TIME, it executes onB >all nodes until it get to the one in question, it then fails with >f> >"SYSTEM-F-INVLOGIN, login information invalid at remote node" >nM >On the target node the accounting records show a login failure with a useridnH >of ILLEGAL and final status text of "%LOGIN-F-NOSUCHUSER, no such user" >nJ >This is not actually causing me a problem as I can start up SMISERVER andH >everything works as expected, but, why is one node different to all the >others? >i >Dicko >2 >rI >Brian Schenkenberger, VAXman- <system@SendSpamHere.ORG> wrote in messageb+ >news:009FBB15.9C16F2C3@SendSpamHere.ORG...sD >> In article <9d81k9$bp4$1@gossamer.itmel.bhp.com.au>, "Dick Adams"# ><adams.dick.rc@bhp.com.au> writes:n >> >Hi all, L >> >        I look after several Alphas running OpenVMS 6.2, they are not in >aI >> >cluster. When I use SYSMAN to manage them all at once I have one node  >thataK >> >requires SMISERVER to be running but the others do not? When I read the D >> >documentation (7.21 doco) it says that to use SYSMAN you require
 >SMISERVER7 >> >yet it's works without it on all nodes except one??t >> >> >> >Can anyone shed some light on this apparent contradiction? >> > >> >TIA- >> >    Dick >>K >> In a cluster, the SMISERVER is started automatically and SYSMAN commandsaK >> referencing other nodes in the cluster are effected via cluster communi- J >> cations and the SMISERVER.  SYSMAN can also target nodes outside of the@ >> cluster.  In this case, the comminication is done via DECnet. >>H >> Read the SYSTEM HELP text for SET ENVIRONMENT for a few more details. >> >> -- 5 >> VAXman- OpenVMS APE certification number: AAA-0001  >VAXman(at)TMESIS(dot)COMm >>L >> city, n., 1. a place where trees are cut down and streets are named after >them. >W   ------------------------------  % Date: Wed, 09 May 2001 12:40:00 +0100s  From: steven.reece@quintiles.com' Subject: Re: TCP/IP printing on vms 7.1-H Message-ID: <OF0F25E299.48B4A06E-ON80256A47.003F91EE@qedi.quintiles.com>  I Depends what you are seeking to achieve and which IP stack you are using. I If you are running Compaq's TCP/IP Services for OpenVMS (a.k.a. UCX) thensD you can use lpr or you can use the telnet symbiont (TCP$TELNETSYM orC UCX$TELNETSYM depending on the product version that you are using).   G See MGMT6 in the OpenVMS FAQ "How do I connect a PostScript printer via0F TCP/IP" and bear in mind that the telnet symbiont need not be printingJ postscript - it just throws what it gets at the printer and hopes that the) printer will understand what it receives.t  H In my opinion, it's easier than trying to understand LPR but then that's
 just me.  :-)f Steve.   Graham Van Epps asked:7 >>>after skimming this ng and reading the faq, i gathere2 that i am supposed to use lprsetup to configure my/ alpha to print over tcp/ip to an hp laserjet 4.p   two questions/problems:eA 1. when logged in as system, there is no lprsetup in the ucx dir.I5    running lprsetup returns a command not found error<D 2. i ran it on a tru64 box to see what to expect and it had no optioD    for the laserjet 4.  should i just choose remote or postscript...  E also, could i just copy a bsd printcap file over and install it on mye> vms system?  docs seem to imply that they use the same syntax.   any help would be awesome. thanks.e <<<    ------------------------------  % Date: Wed, 09 May 2001 12:43:46 +0200a) From: Christof Brass <brass@infopuls.com>?8 Subject: Re: The Internet, Tru64 and other unix variants, Message-ID: <3AF91F62.5303E409@infopuls.com>   CSABA HARANGOZO wrote: > , > Christof Brass <brass@infopuls.com> wrote: [SNIP] > > Nobody needs another UNIX. > N >         Unfortunately, the "bastardisation" of VMS continues unabated... :-(H >         See:   http://www.openvms.compaq.com/solutions/government/coe/ > G >         Here you can read ( among others ) the DII COE Faq, and weep.oL >         If the stupid DoD wants Unix, there is Tru64, no need to ruin VMS.M >         But of course, one can not expect common sense from these places...o > 7 >                                                 Csaba  > K >    ----------------------------------------------------------------------bG >    * Csaba I. Harangozo     |    'To err is human', said the hedgehogrG >    * csabah@zipworld.com.au |           as he dismounted a wirebrush.uK >    ----------------------------------------------------------------------h= >    EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]:a   Thanks!y< I agree completely: why should the DoD people choose VMS for their UNIX wishes?   ------------------------------  % Date: Wed, 09 May 2001 12:58:13 +0200d) From: Christof Brass <brass@infopuls.com>M8 Subject: Re: The Internet, Tru64 and other unix variants+ Message-ID: <3AF922C5.FE1658D@infopuls.com>    Jouk Jansen wrote: >  > D.Webb wrote:a > >hN > > Paradoxically the only time that the death of Tru64 might actually benefitO > > VMS is if the COE work was so good that all Tru64 applications could be runeQ > > (with good performance) on VMS !! Then Compaq might be able to retain some ofoQ > > the Tru64 user base. (Though probably the only way to do this without adverseaQ > > customer reaction would probably be to present it as merging Tru64 into VMS).c > >gI > Not that bad if Tru64 is an optional user shell on the full VMS-kernel.uF > This combination will give the most secure Unix (gettinmg rid of theI > suid problems). Even from the point of marketing this is a good option:iH > the name Tru64 has to be dropped when in future processors will appearD > with more than 64 bits and what is a nice  name than "SecureUNIX"? >  >                       Jouk   64 Bit is enough.    ------------------------------  % Date: Wed, 09 May 2001 12:57:22 +0200 ) From: Christof Brass <brass@infopuls.com>p8 Subject: Re: The Internet, Tru64 and other unix variants, Message-ID: <3AF92292.F098DFD4@infopuls.com>   "D.Webb" wrote:  > ^ > In article <3AF6CB4A.3BC5B0F9@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: > >"D.Webb" wrote:P > >> The death of Tru64 would almost certainly mean that Compaq would reconsiderN > >> whether it should continue to invest in developing new versions of Alpha. > >PK > >Don't forget the efforts to port Tandem's NSK/Gardian to Alpha. And as Ib' > >recall, Linuc runs on alpha as well.  > >l > M > I hadn't forgotten NSK but until they actually start shipping on Alpha thatsK > effort is subject to the possibility of reconsideration and cancellation.i > 	 > Linuc ?  > P > Linux runs on Alpha but although some Tru64 users might move to Linux on AlphaJ > (If - big if - Tru64 were to die) most would probably go to a Commercial > Unix - most probably Solaris.nK > Some might move to Linux and recoup their investment in Alpha Hardware by I > running Linux on Alpha. However future purchases for linux would almostT7 > inevitably be on "the standard Linux platform" Intel.bE > There would also of course be the customer reaction against Compaq.t > . > Losing one OS (WNT on Alpha) is unfortunate., > Losing Two (Tru64) smacks of Carelessness.  > SUN will sooner or later replace Solaris by Linux. You can see signs of this already.; Compaq could (and should from my point of view - sorry if Is> insult Tru64 fans - I don't have a clue about the real quality8 compared to other UNIX flavours) do the same. This would> probably enforce the Alpha because there would be a decent and> serious Alpha Linux distribution without delay compared to the Intel Linux distributions.  L > Paradoxically the only time that the death of Tru64 might actually benefitM > VMS is if the COE work was so good that all Tru64 applications could be run.O > (with good performance) on VMS !! Then Compaq might be able to retain some of O > the Tru64 user base. (Though probably the only way to do this without adversetO > customer reaction would probably be to present it as merging Tru64 into VMS).e  : Exactly this is one of my fears. The resulting elephant OS@ wouldn't be managable with many respects: development of the OS,# administration and app development.m? Again: I really don't see any point in having UNIX apps runninge< on top of VMS. Why should this be better than having them on Tru64?  P > >What I find interesting is the timing aspect of this versus the fact that theP > >most recent game of musical chairs at Compaq has Marcello heading both True64 > >and VMS.2 >  > David Webb > VMS and Unix team leader > CCSS > Middlesex University   ------------------------------  % Date: Wed, 09 May 2001 12:50:47 +0200@) From: Christof Brass <brass@infopuls.com>M8 Subject: Re: The Internet, Tru64 and other unix variants, Message-ID: <3AF92107.E79434FA@infopuls.com>   "D.Webb" wrote:e > o > In article <QvtJ6.1712$CN.321365@nostril.pacific.net.au>, CSABA  HARANGOZO   <csabah@zipworld.com.au> writes:g- > >Christof Brass <brass@infopuls.com> wrote:t > >> Dirk Munk wrote:t > >e > >> [SNIP]u > >  > >> Brillant.C > >> And not to mix UNIX features into VMS because this would offernD > >> the pure VMS apps to step by step be re-written to be more UNIX; > >> like and to end up on UNIX finally. Moreover will thisfA > >> UNIXication of VMS introduce subtle and heavy problems whichm# > >> will raise the platform costs..: > >> Branding is the art to remain sufficiently different. > >> Nobody needs another UNIX.h > > N > >       Unfortunately, the "bastardisation" of VMS continues unabated... :-(H > >       See:   http://www.openvms.compaq.com/solutions/government/coe/ > >rG > >       Here you can read ( among others ) the DII COE Faq, and weep. L > >       If the stupid DoD wants Unix, there is Tru64, no need to ruin VMS.M > >       But of course, one can not expect common sense from these places...g > >p7 > >                                               Csabae > >a >  > Sorry have to disagree.bM > So long as it doesn't interfere with VMS's strengths ie Security, Stability I > and clustering then anything which increases the number of applicationsnN > (either by easing the porting efforts of Volunteers or persuading commercialD > companies that a VMS port is not too difficult) is to be welcomed.  : Intermixing architecture foreign things endangers quality,7 stability, easy of use which increases TOC, complexity.g  @ There is no point in having UNIX apps on VMS. Either we get best= of breed apps (like on the Mac vs Wintel or Walpha) on VMS orr< implement something like VMware for Alpha and run them under; Tru64 or Linux or have a separate box to run it on Tru64 ort Linux.= Again: there is not the smallest point in having UNIX apps oni: VMS. Moreover it could lead to let current VMS app vendors@ change theirs apps to be more UNIX like and to be easier to port( to UNIX and perhaps abandon them on VMS. Is this what we really want?  N > All operating systems pinch from each other. VMS has pinched from Unix, UnixO > has pinched from VMS. (Hell the Core of NT was allegedly pinched almost wholek > from VMS).  > VMS was designed to avoid all the UNIX pitfalls. From my point? of view VMS learned from other OSs how it shouldn't be done. If   this fits into your description?  > Basically what do you want to learn VMS from which other OSs?    Is pipeing that important? ;-)  N > This is normal. It's happened ever since VMS was concieved (and before since7 > VMS was designed based on earlier operating systems).aE > I want a growing evolving VMS not a dead preserved museum specimen.v >  > David Webb > VMS and Unix team leader > CCSS > Middlesex University >  > PS.s > Q > If Tru64 really were in trouble then far from being a reason to celebrate it iseQ > bad news for VMS. Tru64 sells Alpha chips. Those using Tru64 would be forced toiP > move to other vendor's Unix systems (Since their applications won't run on VMSP > !!). Sun would probably be the big winner. Linux would take some (and a few of6 > them - probably a very few would be Linux on Alpha).M > The death of Tru64 would almost certainly mean that Compaq would reconsiderjK > whether it should continue to invest in developing new versions of Alpha.s   ------------------------------  % Date: Wed, 09 May 2001 13:04:38 +0200 ) From: Christof Brass <brass@infopuls.com>o8 Subject: Re: The Internet, Tru64 and other unix variants, Message-ID: <3AF92446.400DC156@infopuls.com>   David Mathog wrote:l > d > In article <3AF7EEC6.338A954@hrem.stm.tudelft.nl>, Jouk Jansen <joukj@hrem.stm.tudelft.nl> writes: > >D.Webb wrote: > >>O > >> Paradoxically the only time that the death of Tru64 might actually benefitaP > >> VMS is if the COE work was so good that all Tru64 applications could be runR > >> (with good performance) on VMS !! Then Compaq might be able to retain some ofR > >> the Tru64 user base. (Though probably the only way to do this without adverseR > >> customer reaction would probably be to present it as merging Tru64 into VMS). > >>J > >Not that bad if Tru64 is an optional user shell on the full VMS-kernel.G > >This combination will give the most secure Unix (gettinmg rid of theM > >suid problems). > M > I'm not sure that you can have sufficient compatibility without introducingh > the suid problem.s > J > It doesn't surprise me at all that Tru64 is being replaced by Linux.  WeL > use Linux on our DS10 beowulf and there's nothing in Tru64 that would haveH > justified the very high price of putting that OS on those boxes.  (But2 > then, I'm not running a bank or a national lab.) > J > I've argued D.Webb's point here several times before - that is, if thereK > were a common run time environment for all Alphas it would be a very goodlJ > thing for the Alpha platform.  It would let a single porting effort ("toJ > alpha") produce code that could be sold/distributed for Linux,Tru64, andL > OpenVMS ( albeit within a Unixy environment on VMS).   It's hard enough toQ > convince people to develop software for Alpha, but Compaq could sweeten the pot > > by offering 3 platforms for the price of one porting effort. > H > If the DII/COE initiative does not in the end allow Tru64 and/or LinuxG > binaries to run on OpenVMS then the folks who are running the show ate: > Compaq are truly a half dozen drinks short of a sixpack. > 
 > Regards, >  > David Mathog > mathog@caltech.edu@ > Manager, sequence analysis facility, biology division, CaltechL > **************************************************************************L > *                                RIP VMS                                 *L > **************************************************************************  ; Running Tru64 and/or Linux apps on VMS won't happen. Do youc; realise the problems some UNIX flavours have in running WNT1@ apps? What could and should be accomplished is to have something> like an aBCS (analog to iBCS) which would help in running UNIX/ flavoured Alpha apps on all UNIX flavoured OSs.n  = To run VMS apps on UNIX or vice versa wouldn't be a good idea @ because it's simply not necessary. There are much better ways to have the same effect..  ? Dropping Tru64 is not a problem for the Alpha. Because VMS onlyp< runs on Alpha, dropping Alpha means dropping VMS. This won't7 happen in the foreseeable future (if something like the-? foreseeable future exists at all). Or VMS has to be ported to at different HW than Alpha.   ------------------------------  % Date: Wed, 09 May 2001 13:11:50 +02001) From: Christof Brass <brass@infopuls.com>e8 Subject: Re: The Internet, Tru64 and other unix variants, Message-ID: <3AF925F6.B6420AA1@infopuls.com>   "D.Webb" wrote:u > q > In article <bO3ofuYMAFbe@eisner.encompasserve.org>, Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:sX > >In article <9d8gqm$bes$1@aquila.mdx.ac.uk>, david20@alpha2.mdx.ac.uk (D.Webb) writes: > >31 > >> Losing one OS (WNT on Alpha) is unfortunate.w > >rE > >That might be true if Windows NT had ever been on Alpha, but sincetD > >Microsoft did not support their own office applications on Alpha,E > >reasons for using their operating system were irrelevant to Alpha.u > N > Quite a number of companies were using NT on Alpha. DEC/Compaq even produced. > Alpha boxes specifically to run NT on Alpha.P > Hence a large number of customers were upset by the fairly sudden demise of NTH > on Alpha. It is irrelevent to those users whose fault that demise was.K > I would suspect that those customers took a fair bit of persuading to buy  > anything from Compaq again.l >  > David Webb > VMS and Unix team leader > CCSS > Middlesex University  > The burned customers wouldn't probably by anything from Compaq= and they probably woulnd't buy any Alpha products. Instead ofi> dropping NT on Alpha C should have sued Micro$hit like Digital< did with Intel. If the contracts didn't allow this shoot the people who signed them.r  = I think it makes a difference whose fault the end of Alpha NTn? was. You could explain it to customers and blame the guilty. Ifm@ it wasn't Compaq's fault entirely (including the contract stuff)? they might have been able to convince some customers not to buyl> Micro$hit products (although I doubt that this would have been very effective).  = Do you know any serious numbers of used Alpha NT licences anda apps and companies?    ------------------------------  % Date: Wed, 09 May 2001 13:06:53 +0200 ) From: Christof Brass <brass@infopuls.com>t8 Subject: Re: The Internet, Tru64 and other unix variants, Message-ID: <3AF924CD.78E54207@infopuls.com>   Larry Kilgallen wrote: > W > In article <9d8gqm$bes$1@aquila.mdx.ac.uk>, david20@alpha2.mdx.ac.uk (D.Webb) writes:S > 0 > > Losing one OS (WNT on Alpha) is unfortunate. > D > That might be true if Windows NT had ever been on Alpha, but sinceC > Microsoft did not support their own office applications on Alpha,sD > reasons for using their operating system were irrelevant to Alpha.  < As Terry Shannon pointed out several times: any co-operation= with Micro$hit is organ donatorship. I don't know anybody whoi= thinks that Micro$hit did their job for AlphaNT right or thatt8 Micro$hit had a real interest in supporting NT on Alpha.   ------------------------------  % Date: Wed, 09 May 2001 12:40:46 +0000   From: Steve.Spires@yellgroup.com8 Subject: Re: The Internet, Tru64 and other unix variants/ Message-ID: <00256A47.0045AA10.00@quegw01.btyp>6  L Contact:   Tel: 3063  -  IS - Infrastructure, 1st Floor, Bridge Street Plaza    O Well, one lost account was Yellow Pages [now Yell Group] in the UK, who were onMP the Alpha/NT route, quite heavy investment and long term commitment, and a totalL Compaq house [ VMS , Tru64 and Alpha/NT, along with Compaq Wintel boxes from desktop to servers].  O Since Compaq turned round and blew the Alpha/NT platform, which meant a radicalaI rethink for the organisation and accepting some heavy losses in hardware,tM software and development costs, all the Tru64 boxes [23 in number ranging alleK the way up to 8400s] have been or are being replaced by Sun and HP, the VMShN boxes [Vax and Alpha, 30 in number from 2100 to 8400 with 6000 and 7000 Vaxes]M are being phased out as the company made a decision to move away from Compaq,rM and the desktop machines [about 4500] and Wintel servers [about 70] have beens lost to HP.o  P So, they DID have an account which would have been worth a substantial amount inM total, which they lost [or are losing] completely because they pissed off theaI management with false promises and almost no warning of a change of plan.p  H Added to which, as Yell regard me as a Compaq employee, they put me in aE position which I feel isn't compensated enough for in monetary terms,aA considering the amount of flak I got [and still get] over this...-   Steve Spires        = Christof Brass <brass@infopuls.com> on 09/05/2001 11:11:50 AMn    To:        Info-VAX@Mvb.Saic.Com+ cc:         (bcc: Steve Spires/YellowPages)DF From:      Christof Brass <brass@infopuls.com>, 9 May 2001, 11:11 a.m.  / Re: The Internet, Tru64 and other unix variants          "D.Webb" wrote:. > 5 > In article <bO3ofuYMAFbe@eisner.encompasserve.org>,c; Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:.P > >In article <9d8gqm$bes$1@aquila.mdx.ac.uk>, david20@alpha2.mdx.ac.uk (D.Webb) writes:D > >E1 > >> Losing one OS (WNT on Alpha) is unfortunate.  > > E > >That might be true if Windows NT had ever been on Alpha, but sincenD > >Microsoft did not support their own office applications on Alpha,E > >reasons for using their operating system were irrelevant to Alpha.- >-N > Quite a number of companies were using NT on Alpha. DEC/Compaq even produced. > Alpha boxes specifically to run NT on Alpha.P > Hence a large number of customers were upset by the fairly sudden demise of NTH > on Alpha. It is irrelevent to those users whose fault that demise was.K > I would suspect that those customers took a fair bit of persuading to buye > anything from Compaq again.h >e > David Webb > VMS and Unix team leader > CCSS > Middlesex University  > The burned customers wouldn't probably by anything from Compaq= and they probably woulnd't buy any Alpha products. Instead ofn> dropping NT on Alpha C should have sued Micro$hit like Digital< did with Intel. If the contracts didn't allow this shoot the people who signed them.r  = I think it makes a difference whose fault the end of Alpha NTd? was. You could explain it to customers and blame the guilty. Ifm@ it wasn't Compaq's fault entirely (including the contract stuff)? they might have been able to convince some customers not to buyh> Micro$hit products (although I doubt that this would have been very effective).  = Do you know any serious numbers of used Alpha NT licences and  apps and companies?-   ------------------------------    Date: 09 May 2001 16:11:08 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>g8 Subject: Re: The Internet, Tru64 and other unix variantsH Message-ID: <y4d79iwr2b.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  + Christof Brass <brass@infopuls.com> writes:   @ > SUN will sooner or later replace Solaris by Linux. You can see > signs of this already.  F You can? I cannot. It would imply a singular loss of control by Sun to; do that, and not least a significant investment write-off. 2   	Jan   ------------------------------    Date: 09 May 2001 16:09:36 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>"8 Subject: Re: The Internet, Tru64 and other unix variantsH Message-ID: <y4g0eewr4v.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  + Christof Brass <brass@infopuls.com> writes:   / > There is no point in having UNIX apps on VMS.K  I I suggest you first define what a "UNIX app" is - possibly in contrast to = a "VMS app" - and then we might have a basis for discussion. p   	Jan   ------------------------------    Date: 09 May 2001 16:15:27 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>h8 Subject: Re: The Internet, Tru64 and other unix variantsH Message-ID: <y4ae4mwqv4.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  " Steve.Spires@yellgroup.com writes:  J > Since Compaq turned round and blew the Alpha/NT platform, which meant a I > radical rethink for the organisation and accepting some heavy losses inyM > hardware software and development costs, all the Tru64 boxes [23 in number hJ > ranging all the way up to 8400s] have been or are being replaced by Sun L > and HP, the VMS boxes [Vax and Alpha, 30 in number from 2100 to 8400 with K > 6000 and 7000 Vaxes] are being phased out as the company made a decision qM > to move away from Compaq, and the desktop machines [about 4500] and Wintel o* > servers [about 70] have been lost to HP.  H So they made that other type of irrational decision well-known in the ITB sector and cut off their nose and their eyes to spite their face.   6 Whatever has become of "never touch a running system"?   	Jan   ------------------------------  % Date: Wed, 09 May 2001 15:49:49 +0100f  From: steven.reece@quintiles.com8 Subject: Re: The Internet, Tru64 and other unix variantsH Message-ID: <OF043E46F8.9250E1B5-ON80256A47.00515598@qedi.quintiles.com>   Jan Vorbrueggen wrote: >>>p6 Whatever has become of "never touch a running system"? <<<r  K The text got rubbed off as people grappled for the "Off" switch on their NT  systems.....   Steve.   ------------------------------  % Date: Wed, 09 May 2001 16:04:05 +0100o0 From: andrew harrison <andrew.nospam@uk.sun.com>8 Subject: Re: The Internet, Tru64 and other unix variants* Message-ID: <3AF95C64.E054A6CD@uk.sun.com>   Christof Brass wrote:e > = > Running Tru64 and/or Linux apps on VMS won't happen. Do yout= > realise the problems some UNIX flavours have in running WNTaB > apps? What could and should be accomplished is to have something@ > like an aBCS (analog to iBCS) which would help in running UNIX1 > flavoured Alpha apps on all UNIX flavoured OSs., >   8 Rubbish its already happening. What do you think Oracle 8 use as their development platform ?? it isn't Windows NT: or OpenVMS. How about all the GNU utilities that have been ported to OpenVMS ??  = You windows point is also rubbish, there is a huge differenceH: between say Tru64/Solaris/Linux which have well documented8 API's with easy access to source code for more detailed 8 scrutiny and Windows, which is not as well documented as8 it should be, which changes rapidly and which has major : apps that use the undocumented/poorly documented features.  9 Incedentally you seem to missunderstand what Linux is, itt> isn't a new OS it is simply a new UNIX like kernel that makes : extensive use of the the GNU and other freeware utilities = to provide a UNIX like environment. Almost all of what peopled- think of as being Linux existed before Linux.,  ? > To run VMS apps on UNIX or vice versa wouldn't be a good ideaeB > because it's simply not necessary. There are much better ways to > have the same effect.a > A > Dropping Tru64 is not a problem for the Alpha. Because VMS only > > runs on Alpha, dropping Alpha means dropping VMS. This won't9 > happen in the foreseeable future (if something like thelA > foreseeable future exists at all). Or VMS has to be ported to as > different HW than Alpha.  2 I don't think that Compaq will drop tru64 anytime 5 soon, but if they did then it would be the beginning i6 of the end for VMS because it would no longer benefit 4 from the economies of scale that it does by sharing   the same HW platform with Tru64.   Regardsh Andrew Harrisonn Enterprise IT Architecte   ------------------------------  % Date: Wed, 09 May 2001 09:03:04 -0700t! From: Tom Linden <tom@kednos.com>s8 Subject: RE: The Internet, Tru64 and other unix variants9 Message-ID: <CIEJLCMNHNNDLLOOGNJICEGNCIAA.tom@kednos.com>c   > -----Original Message-----9 > From: andrew harrison [mailto:andrew.nospam@uk.sun.com]d' > Sent: Wednesday, May 09, 2001 8:04 AM  > To: Info-VAX@Mvb.Saic.Com.: > Subject: Re: The Internet, Tru64 and other unix variants >i >M > Christof Brass wrote:  > >t? > > Running Tru64 and/or Linux apps on VMS won't happen. Do you ? > > realise the problems some UNIX flavours have in running WNT.D > > apps? What could and should be accomplished is to have somethingB > > like an aBCS (analog to iBCS) which would help in running UNIX3 > > flavoured Alpha apps on all UNIX flavoured OSs.l > >  >m9 > Rubbish its already happening. What do you think OracleF: > use as their development platform ?? it isn't Windows NT< > or OpenVMS. How about all the GNU utilities that have been > ported to OpenVMS ?? >r? > You windows point is also rubbish, there is a huge difference < > between say Tru64/Solaris/Linux which have well documented9 > API's with easy access to source code for more detailedt: > scrutiny and Windows, which is not as well documented as9 > it should be, which changes rapidly and which has majorx< > apps that use the undocumented/poorly documented features. >f; > Incedentally you seem to missunderstand what Linux is, it ? > isn't a new OS it is simply a new UNIX like kernel that makeso; > extensive use of the the GNU and other freeware utilitiesU? > to provide a UNIX like environment. Almost all of what peoplen/ > think of as being Linux existed before Linux.k >oA > > To run VMS apps on UNIX or vice versa wouldn't be a good ideapD > > because it's simply not necessary. There are much better ways to > > have the same effect.t > >lC > > Dropping Tru64 is not a problem for the Alpha. Because VMS only-@ > > runs on Alpha, dropping Alpha means dropping VMS. This won't; > > happen in the foreseeable future (if something like theIC > > foreseeable future exists at all). Or VMS has to be ported to a6 > > different HW than Alpha. >o3 > I don't think that Compaq will drop tru64 anytimee6 > soon, but if they did then it would be the beginning7 > of the end for VMS because it would no longer benefite5 > from the economies of scale that it does by sharingV" > the same HW platform with Tru64.  K VMS and Alpha aren't exactly synonymous.  In theory VMS could run on Intel,T e.g.   >m	 > Regardse > Andrew Harrison  > Enterprise IT ArchitectT >g   ------------------------------    Date: 09 May 2001 10:50:22 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> @ Subject: Re: VAX Just Stops - Not the Usual Suspects - follow upH Message-ID: <y41ypylxdd.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  + rob.buxton@wcc.govt.nz (Rob Buxton) writes:t   > Here's the update. [snip]  M Sounds very much like a multicast packet ((R)ARP?) causing a HALT instructioneL to be executed in kernel mode. The console(s) should say/have said so, BTW -	 did they?h   	Jan   ------------------------------    Date: 09 May 2001 18:23:43 +0800, From: Paul Repacholi <prep@prep.synonet.com>@ Subject: Re: VAX Just Stops - Not the Usual Suspects - follow up- Message-ID: <878zk6zuq8.fsf@prep.synonet.com>f  + rob.buxton@wcc.govt.nz (Rob Buxton) writes:r   > Thanks for all the responses.l  @ > Alas, my News Server connection has been a bit wayward so I've > missed a few days.  6 Oh, nice to know I'm not the only one... bloody BGP...  E > Again, I'll post an update as this might deter people from going toeE > TCPIP 5.1 on aging VAXes. If it is a quota problem it's odd that itoE > hits three systems at the same time. So, I can only think it's somerE > kind of Network Event that's triggering some odd behaviour. The VAX C > 4000s are also on the same Network. Main differenced is that theyr4 > have FDDI and Ethernet, MV3100s are just Ethernet.  E It seems your ethernet controllers are being shot by TCP (But not thegB FDDIs) and the cluster vanishes so they hang. It is odd they don't
 cluexit...   -- *< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov     ------------------------------  % Date: Wed, 09 May 2001 10:09:09 -0400e- From: JF Mezei <jfmezei.spamnot@videotron.ca>u@ Subject: Re: VAX Just Stops - Not the Usual Suspects - follow up, Message-ID: <3AF94F84.4B539A95@videotron.ca>   Rob Buxton wrote:sC > Okay... found that the one that was not stopping was not startingsE > TCPIP, had 5.1 installed but INTSTKPAGES was too low. Sysgenned andV > started TCPIP.3 > At the next "stoppage" all three MV3100s stopped.   J For what its worth, My 3100-30 with only 16 megs of memory would sometimesJ crash during the boot sequence  if I tried to log in while TCPIP (5.0) wasJ starting. So I had learned to let it boot to the end and then log in. (TCP startup runs as a batch job).s  K This was a real crash though, so not quite the same symptoms as you. I have3L not played enough with the boot sequence since I upped the SPTEREQ parameter5 (which was preventing me at some pint from spawning).o  F I am starting to get a feeling that AUTOGEN on VAX miscalculates a few: parameters. (I know that SPTEREQ was way undercalculated).   ------------------------------  % Date: Wed, 09 May 2001 10:39:59 -0700t+ From: "Barry Treahy, Jr." <treahy@mmaz.com> @ Subject: Re: VAX Just Stops - Not the Usual Suspects - follow up( Message-ID: <3AF980EF.F93D0CC0@mmaz.com>   Rob Buxton wrote:r  E > I have forced a Crash Dump, not enough of an expert to diagnose it,p' > but I have logged a call with Compaq.e >p  I If you use ANA/CRASH on the dumps, do a SHOW SUMAMRY and locate the TCPIPtG related processes.  Using the index column (the second column), you can J issue a SHOW PROCESS/ID= on those processes to evalute their process level5 quotes and look for any that might have expired them.o  
 Good luck.   Barryi --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIOh  A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028y   ------------------------------   Date: 9 May 2001 07:13:19 CDT = From: wayne@tachysoft.xxx.310887.killspam.0162 (Wayne Sewell)t" Subject: Re: VAX vs AXP executable. Message-ID: <bK2EbLk5sP5Z@tachxxsoftxxconsult>  \ In article <3AF801E2.2DA3F603@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: > Wayne Sewell wrote:IQ >> Well, this is a nice addition to the command and I plan to start using it, butvR >> how does it help with the stated problem?  Having just tried the command, I seeL >> that the information is still written to sys$output, so you still have to5 >> redirect it to a file, read it back, and parse it.s > E > $PIPE ANA/IMAGE/SELECT=ARCH myexecutable.exe | search sys$input VAX0D > $IF $STATUS .eq. %X10000001 then arch = "VAX" else arch = "ALPHA".  O Well, okay, but you could do exactly the same thing with the original technique O of using /out, and I think a couple of earlier posts in this thread illustrated@O exactly that.  My point was that the new qualifier doesn't really gain you muchtL over what was already there, at least for the stated problem.  True, there'sN less overhead this way, but my /symbol suggestion would have taken almost *no*	 overhead.n  K In fact, adding a /symbol qualifier wouldn't even be required.  The analyzeoK program could simply create a symbol automatically, as the checksum commandn does.   = Brian's return code idea would have taken even less overhead.h   -- aO ===============================================================================-M Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxxg: http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-)0O ===============================================================================cB Jed Clampett, checking into hotel: "This place got a cement pond?"+ Ellie May: "And do yuh let critters in it?"n   ------------------------------  # Date: Wed, 09 May 2001 15:27:53 GMTa= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)c" Subject: Re: VAX vs AXP executable0 Message-ID: <009FBC03.8CE62EA4@SendSpamHere.ORG>  n In article <bK2EbLk5sP5Z@tachxxsoftxxconsult>, wayne@tachysoft.xxx.310887.killspam.0162 (Wayne Sewell) writes:] >In article <3AF801E2.2DA3F603@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:n >> Wayne Sewell wrote:R >>> Well, this is a nice addition to the command and I plan to start using it, butS >>> how does it help with the stated problem?  Having just tried the command, I seeaM >>> that the information is still written to sys$output, so you still have too6 >>> redirect it to a file, read it back, and parse it. >> tF >> $PIPE ANA/IMAGE/SELECT=ARCH myexecutable.exe | search sys$input VAXE >> $IF $STATUS .eq. %X10000001 then arch = "VAX" else arch = "ALPHA".w >iP >Well, okay, but you could do exactly the same thing with the original techniqueP >of using /out, and I think a couple of earlier posts in this thread illustratedP >exactly that.  My point was that the new qualifier doesn't really gain you muchM >over what was already there, at least for the stated problem.  True, there'sAO >less overhead this way, but my /symbol suggestion would have taken almost *no*s
 >overhead. >CL >In fact, adding a /symbol qualifier wouldn't even be required.  The analyzeL >program could simply create a symbol automatically, as the checksum command >does. >e> >Brian's return code idea would have taken even less overhead.  L ...but perhaps a little more in the head.  This /SELECT seems like a rather / poorly thought out new addition to the utility.>   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMN            eO city, n., 1. a place where trees are cut down and streets are named after them.s   ------------------------------  % Date: Wed, 09 May 2001 12:13:39 -0400A/ From: "Howard E. Arnold" <arnoldh@celerent.com>i Subject: Virus Attackp? Message-ID: <NEBBKBPAMLAEPFNHOPFBGEODCOAA.arnoldh@celerent.com>   H My E-mail distribution list was infected with a virus this morning and a5 message should have been sent to everyone on my list.   L I'm sending this message to warn you that you may have this virus and not to/ open it. The title of the message was HOMEPAGE.n  : I apologize for any inconvenience this may have cause you.   Howard   ------------------------------    Date: 09 May 2001 10:46:17 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>p0 Subject: Re: VMS 7.2 BACKUP damaging system diskH Message-ID: <y44ruulxk6.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  - "Barry Treahy, Jr." <treahy@mmaz.com> writes:e  J > I've tested backing up on-line disk to disk (with and without the /ALIAS< > and with the /NOALIAS) and the target disk is not bootable  5 What, in detail, is the prolem behind "not bootable"?    	Jan   ------------------------------  % Date: Wed, 09 May 2001 06:35:44 -0700h+ From: "Barry Treahy, Jr." <treahy@mmaz.com>u0 Subject: Re: VMS 7.2 BACKUP damaging system disk( Message-ID: <3AF947B0.E1FB0194@mmaz.com>   Robert Deininger wrote:e  ! > Questions about your situation:a >oE > Are you backing up a live system disk?  I wouldn't expect a perfectRF > backup, and a restored "live" backup might need some manual labor to > render it bootable.m  N I've been using VMS for 20 year and though DEC advises against on-line backupsK of the system disk, I have never had a back not be bootable not have I everlL had one where the main root aliases are messed up.  The problem is that in aK 7x24 operation, you cannot take down a system to backup the system disk and-C yes I know that you'll always get the cleanest backup in SA mode...m    I > Are you certain your system disk directory/alias structures are correctR > before the backup?  M Yes, I've ran a full ana/disk/rep with full read check on the original systemhK disk and it is clean.  The on-line results of a disk to disk image, howeversK start by loosing the entire VMS$COMMON directory in the MFD and a resultingUJ ana/disk/rep places it into [SYSLOST].  Now running on-line backups of any< disk, let alone a system volume, should not be doing this...  ' > Are you up to date with your patches?   N I do not see any new patches that might have been missed, but that would implyJ a difference in the SA backup image and the running VMS image of backup...   Regards,   Barrym   --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO   A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028    ------------------------------  % Date: Wed, 09 May 2001 14:45:33 +0100   From: steven.reece@quintiles.com0 Subject: Re: VMS 7.2 BACKUP damaging system diskH Message-ID: <OF8DE810A1.A69FA044-ON80256A47.004B5601@qedi.quintiles.com>  D What's the command line that you're using for the backup and for the restore?I Whilst I appreciate your experience and knowledge, it's easy to trip overmH things and be so deep into a problem that you can't see the wood for the trees.   Steve.    Barry Treahy, Jr. wrote/quoted :I >>>I've been using VMS for 20 year and though DEC advises against on-lined backupstK of the system disk, I have never had a back not be bootable not have I evereJ had one where the main root aliases are messed up.  The problem is that in aeK 7x24 operation, you cannot take down a system to backup the system disk and:C yes I know that you'll always get the cleanest backup in SA mode....    I > Are you certain your system disk directory/alias structures are correctp > before the backup?  F Yes, I've ran a full ana/disk/rep with full read check on the original systemK disk and it is clean.  The on-line results of a disk to disk image, however-K start by loosing the entire VMS$COMMON directory in the MFD and a resultingrJ ana/disk/rep places it into [SYSLOST].  Now running on-line backups of any< disk, let alone a system volume, should not be doing this... <<<t   ------------------------------  % Date: Wed, 09 May 2001 09:58:35 -0400.2 From: rdeininger@mindspring.com (Robert Deininger)0 Subject: Re: VMS 7.2 BACKUP damaging system diskL Message-ID: <rdeininger-0905010958350001@user-2iveblu.dialup.mindspring.com>  < In article <3AF947B0.E1FB0194@mmaz.com>, "Barry Treahy, Jr." <treahy@mmaz.com> wrote:   > Robert Deininger wrote:a > # > > Questions about your situation:l > >tG > > Are you backing up a live system disk?  I wouldn't expect a perfecttH > > backup, and a restored "live" backup might need some manual labor to > > render it bootable.e > P > I've been using VMS for 20 year and though DEC advises against on-line backupsM > of the system disk, I have never had a back not be bootable not have I evereN > had one where the main root aliases are messed up.  The problem is that in aM > 7x24 operation, you cannot take down a system to backup the system disk and E > yes I know that you'll always get the cleanest backup in SA mode...   E Ok.  I was speculating, since I didn't know exactly what you meant byw
 "unbootable".   pK > > Are you certain your system disk directory/alias structures are correct  > > before the backup? > O > Yes, I've ran a full ana/disk/rep with full read check on the original systemt > disk and it is clean.  e  I This would not find the sort of problem caused by the old backup bug with J aliases.  You could get a disk that was perfectly valid from a file system: point of view, but did not have the structure VMS expects.  6 > The on-line results of a disk to disk image, howeverM > start by loosing the entire VMS$COMMON directory in the MFD and a resultingoL > ana/disk/rep places it into [SYSLOST].  Now running on-line backups of any> > disk, let alone a system volume, should not be doing this...  L Please post the output of DUMP/HEADER/BLOCK=COUNT:0 [000000]VMS$COMMON.DIR , from your original disk.  H If VMS$COMMON.DIR is an alias (a common symptom of the old problem), andE the real directory has gone away somehow, then a BACKUP/NOALIAS wouldn* likely not copy this vital directory tree.  5 What messages does backup give around VMS$COMMON.DIR?N   -- J Robert Deininger rdeininger@mindspring.com    ------------------------------   Date: 09 May 2001 16:19:41 GMT From: ka2doug@cs.com (KA2DOUG)0 Subject: Re: VMS 7.2 BACKUP damaging system disk> Message-ID: <20010509121941.01796.00001684@ng-fn1.news.cs.com>  5 >    BACKUP/IMAGE/IGNORE=NOBACK $45$DKA400 $145$DIA0:L  K Pardon me, but I think you need to add INTERLOCK to your IGNORE= statement,oK don't you? There are many open files on a live system, and you are not event. getting a *cludged* copy of them without it.    K And, do you really want to make a copy of the garbage in your page and swapo files?  M I often must do VMS /image backups on live systems and if the media is good IsK have never had an unbootable restore. I've had some unusable files, but thel system has always booted.v   ------------------------------  % Date: Wed, 09 May 2001 10:03:45 -0700e+ From: "Barry Treahy, Jr." <treahy@mmaz.com>/0 Subject: Re: VMS 7.2 BACKUP damaging system disk( Message-ID: <3AF97871.AF481058@mmaz.com>   Robert Deininger wrote:n  Q > > Yes, I've ran a full ana/disk/rep with full read check on the original systemh > > disk and it is clean.  > K > This would not find the sort of problem caused by the old backup bug withmL > aliases.  You could get a disk that was perfectly valid from a file system< > point of view, but did not have the structure VMS expects.  R This tests the validity of the ODS-2 file system, but you are correct, it does notN determine if the proper aliases  from VMS$COMMON to the site specific roots ofR [sysX.syscommon] exist or are correct.  As for proper linking, you'll see that the file ids are good:  H V4500$ dir/file dka400:[000000]vms$common.dir,dka400:[sys0]syscommon.dir   Directory DKA400:[000000]S   VMS$COMMON.DIR;1     (11,1,0)n   Total of 1 file.   Directory DKA400:[SYS0]p   SYSCOMMON.DIR;1      (11,1,0)s   Total of 1 file.  & Grand total of 2 directories, 2 files.     >  >b8 > > The on-line results of a disk to disk image, howeverO > > start by loosing the entire VMS$COMMON directory in the MFD and a resultinglN > > ana/disk/rep places it into [SYSLOST].  Now running on-line backups of any@ > > disk, let alone a system volume, should not be doing this... >lN > Please post the output of DUMP/HEADER/BLOCK=COUNT:0 [000000]VMS$COMMON.DIR , > from your original disk.  Q Here are the dumps for both the VMS$COMMON and the related SYSCOMMON for the main-
 SYS0 root:  > V4500$ DUMP/HEADER/BLOCK=COUNT:0 dka400:[000000]VMS$COMMON.DIRG Dump of file DKA400:[000000]VMS$COMMON.DIR;1 on  9-MAY-2001 09:57:36.57p4 File ID (11,1,0)   End of file block 4 / Allocated 9  (                              File Header   Header area ,     Identification area offset:           40-     Map area offset:                      100 -     Access control area offset:           255a-     Reserved area offset:                 255d+     Extension segment number:             0W.     Structure level and version:          2, 12     File identification:                  (11,1,0)1     Extension file identification:        (0,0,0):     VAX-11 RMS attributess2         Record type:                      Variable4         File organization:                Sequential5         Record attributes:                Non-spanned -         Record size:                      512w+         Highest block:                    9i+         End of file block:                5.+         End of file byte:                 0g+         Bucket size:                      0n+         Fixed control area size:          0d-         Maximum record size:              512m+         Default extension size:           0 +         Global buffer count:              0v+         Directory version limit:          0N@     File characteristics:                 Contiguous, Directory,;                                           MoveFile disablede6     Caching attribute:                    Writethrough+     Map area words in use:                2d+     Access mode:                          0 2     File owner UIC:                       [SYSTEM]B     File protection:                      S:RWE, O:RWE, G:RE, W:RE1     Back link file identification:        (4,4,0)C:     Journal control flags:                <none specified>.     Active recovery units:                None+     Highest block written:                9 .     Client attributes:                    None   Identification area0:     File name:                            VMS$COMMON.DIR;1+     Revision number:                      4-A     Creation date:                        16-DEC-1998 13:47:36.73tA     Revision date:                        16-DEC-1998 13:55:34.22n:     Expiration date:                      <none specified>:     Backup date:                          <none specified>   Map area     Retrieval pointers0         Count:          9        LBN:        261  / Checksum:                                 38254 ; V4500$ DUMP/HEADER/BLOCK=COUNT:0 dka400:[SYS0]SYSCOMMON.DIRgD Dump of file DKA400:[SYS0]SYSCOMMON.DIR;1 on  9-MAY-2001 09:57:57.214 File ID (11,1,0)   End of file block 4 / Allocated 9  (                              File Header   Header area ,     Identification area offset:           40-     Map area offset:                      100n-     Access control area offset:           255t-     Reserved area offset:                 255c+     Extension segment number:             0Q.     Structure level and version:          2, 12     File identification:                  (11,1,0)1     Extension file identification:        (0,0,0)u     VAX-11 RMS attributes 2         Record type:                      Variable4         File organization:                Sequential5         Record attributes:                Non-spanneda-         Record size:                      512p+         Highest block:                    9,+         End of file block:                5a+         End of file byte:                 0e+         Bucket size:                      0I+         Fixed control area size:          0s-         Maximum record size:              512 +         Default extension size:           0 +         Global buffer count:              0c+         Directory version limit:          0 @     File characteristics:                 Contiguous, Directory,;                                           MoveFile disabledh6     Caching attribute:                    Writethrough+     Map area words in use:                2b+     Access mode:                          0A2     File owner UIC:                       [SYSTEM]B     File protection:                      S:RWE, O:RWE, G:RE, W:RE1     Back link file identification:        (4,4,0) :     Journal control flags:                <none specified>.     Active recovery units:                None+     Highest block written:                9t.     Client attributes:                    None   Identification areas:     File name:                            VMS$COMMON.DIR;1+     Revision number:                      41A     Creation date:                        16-DEC-1998 13:47:36.73oA     Revision date:                        16-DEC-1998 13:55:34.22u:     Expiration date:                      <none specified>:     Backup date:                          <none specified>   Map area     Retrieval pointers0         Count:          9        LBN:        261  / Checksum:                                 38254w   >u >yJ > If VMS$COMMON.DIR is an alias (a common symptom of the old problem), andG > the real directory has gone away somehow, then a BACKUP/NOALIAS would , > likely not copy this vital directory tree. >e7 > What messages does backup give around VMS$COMMON.DIR?u  S No errors during the backup process, sans the interlock warnings that are overriden= with the /IGNORE=INTERLOCK.=   Regards,   Barry  --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO/  A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028.   ------------------------------  % Date: Wed, 09 May 2001 18:03:23 +0100=  From: steven.reece@quintiles.com0 Subject: Re: VMS 7.2 BACKUP damaging system diskH Message-ID: <OF3EC5D6FE.92B98623-ON80256A47.005CE7C2@qedi.quintiles.com>  K I haven't yet seen the full message with the backup command line in it, but0K as of around v6.2 the backup of a VMS system disk must have /NOALIAS on it.-B Otherwise the corruption of the SYS$COMMON tree is bound to occur.( Note that /NOALIAS is _not_ the default.  ? I would suggest that a more appropriate command line might be :6  @ $ BACKUP/IMAGE/NOALIAS/IGNORE=(INTERLOCK) $45$DKA400: $145$DIA0:  C I believe that the colons are required on the input and output diskr specifications.h  1 An interesting aside from a couple of weeks ago :a  J An image backup on an OpenVMS Alpha v7.1-1H2 system that I know of failed.K It didn't produce an error, it didn't ACCVIO (apparently) it just seemed tot? not do anything.  The system has ALPBACK04_071 installed on it.cH Looking at the status which was returned, this indicated that backup hadJ ACCVIOed.  A colleague that was investigating it could not see the problemJ and was looking for databases that were still open and all manner of other stuff.= It turned out that he had missed the colon off the input disklE specification.  Correcting the command cured the problem.  Installing D ALPBACK05_071 cured the problem of backup not indicating that it had failed.t   Steve.   KA2DOUG wrote/quoted :8 >>>>    BACKUP/IMAGE/IGNORE=NOBACK $45$DKA400 $145$DIA0:  K Pardon me, but I think you need to add INTERLOCK to your IGNORE= statement,qK don't you? There are many open files on a live system, and you are not evene, getting a *cludged* copy of them without it.  K And, do you really want to make a copy of the garbage in your page and swap  files? <<<a   ------------------------------  % Date: Wed, 09 May 2001 08:44:58 +0200o- From: Didier Morandi <didier.morandi@ubs.com>A, Subject: Re: VMS 7.3 docs on OpenVMS webite?' Message-ID: <3AF8E76A.6B157788@ubs.com>    Ryan Moore wrote:p > I > When are the VMS 7.3 docs going to show up on the OpenVMS documentation-L > website (http://www.openvms.compaq.com:8000/index.html)?  It would be niceK > to start reading the Release Notes and New Features manuals before we getP > our hardcopies.A >  > -Ryane  D We got our hardcopy set last week here in Switzerland, but no CD :-(   D.   ------------------------------    Date: 09 May 2001 10:13:39 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>o6 Subject: Re: What is the best way to erase SCSI disks?H Message-ID: <y4k83rkki4.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  4 hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:  K > :>   There isn't a completely reliable means, short of bulk degausing thep> > :>   media, and then grinding and slagging the platter(s).  G > :Heating above the Curie point of the platter's coating is completelye3 > :reliable. No need to guard the resulting liquid. , >   Actually, no.  There can still be value.  $ But none associated with the data...   	Jan   ------------------------------    Date: 09 May 2001 19:31:34 +0800, From: Paul Repacholi <prep@prep.synonet.com>6 Subject: Re: What is the best way to erase SCSI disks?- Message-ID: <87n18myd0p.fsf@prep.synonet.com>u  4 mathog@seqaxp.bio.caltech.edu (David Mathog) writes:  R > In article <3AF74AF7.F2A2CA16@wi.rr.com>, Scott Vieth <svieth@wi.rr.com> writes:  C > >That gives me an idea: I *do* live in the same city as the worldeF > >headquarters for GE Medical.  I could drop the drives off at GE andC > >ask the guys that build the MRI units to "cook" the drives for a0: > >half-hour in one of their "30-second MRI" systems.  ;^)  H Just pass them through. It may be 'interesting geting them out though :)  5 > That's a really, really, really, REALLY bad idea.  e  D > Think about what's going to happen when the iron in the drive getsE > into a field of that magnitude.  Even bolting the drives down mightcD > not do it as the forces may be high enough to tear individual ironC > based components loose and possibly right through a plastic case. F > There's a reason they don't MRI people who have, or are suspected to> > have, bits of iron stuck in their bodies.  For instance, see0 > http://text.nlm.nih.gov/nih/cdc/www/66txt.html  D They will jump to attention in the middle of the cavity. Seen a phot- of an Oxy bottle thte was forgten on day one!    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.t@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov -   ------------------------------    Date: 09 May 2001 10:36:18 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>rN Subject: Re: www.openvms.compaq.com doesn't display correctly in VMS NavigatorH Message-ID: <y47kzqly0t.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  2 sander@vmsbiz.enet.dec.com (Warren Sander) writes:  O > And also fyi.. On a monthly average the web site gets around 4.5 million hits'L > per month. Of those hits, more than 3 million come from IE type browsers, L > and 800,000 from netscape type browers (the rest are various other browers > including Opera, Mosaic etc.  9 Opera, by default, is set up to lie and impersonate IE 5.    	Jan   ------------------------------  % Date: Wed, 09 May 2001 10:01:03 +0200a= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>4N Subject: Re: www.openvms.compaq.com doesn't display correctly in VMS Navigator) Message-ID: <3AF8F93F.9A1AA91A@gtech.com>c   JF Mezei wrote:   A [comments about using correct MIME labels which I agree 100% with  removed]  D > Web servers should be programmed to warn the web master whenever aJ > "application/octet-stream" document is being served since very little of, > internet documents require that mime type.  @ I do not agree on this. "application/octet-stream" is the way ofA saying "download binary file and do not even think about startingfA an application to view it". Quite usefull in my opinion. I do not C see the point in having a zillion MIME types defined for stuff that8- will never have a viewer application defined.b   Arne   ------------------------------  % Date: Wed, 09 May 2001 10:06:23 +0200n= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>nN Subject: Re: www.openvms.compaq.com doesn't display correctly in VMS Navigator) Message-ID: <3AF8FA7F.D2F24FEC@gtech.com>    Warren Sander wrote:^ > In article <3AF82191.373BD9AC@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:R > |>Their web server is not configured properly. It serves javascript files as theM > |>microsoft "catch all meaningless" mime type of "application/octet-stream"oQ > |>which means that internet compliant browsers who rely on the mime type do nota" > |>know what to do that that URL.  L > The web server is configured correctly. I didn't get the mime type updated > on the external server.b  D One could argue that the difference between "the external server not beingcE configured properly" and "a configuration file on the external serverl' not being updated" is very very small !   M > |>So, another example of a web site where the web master only has access to Q > |>microsoft junk and therefore cannot veryfy compliant with internet standards.   7 > I don't know where the 'microsoft' comment came from.u  F This problem will not be seen in MSIE - only in browsers following theE internet standards (using MIME labels). MSIE does not use MIME labelso! but uses file-extensions instead.t  3 So the MicroSoft junk mentioned is the web-browser.   J >              I did get it on my internal copy and I DO TEST EVERY SINGLEG > PAGE ON THE SERVER WITH NETSCAPE 3.03B with Java. I don't use the vaxu > version anymore.  F And we now know that the problem is not that you tested with MSIE, but9 that the internal and external servers were out of synch.0  + Not good ofcourse, but such things happend.    Arne   ------------------------------    Date: 09 May 2001 18:57:28 +0800, From: Paul Repacholi <prep@prep.synonet.com>N Subject: Re: www.openvms.compaq.com doesn't display correctly in VMS Navigator- Message-ID: <87zocmyelj.fsf@prep.synonet.com>-  2 sander@vmsbiz.enet.dec.com (Warren Sander) writes:  D > The web server is configured correctly. I didn't get the mime typeF > updated on the external server. I did get it on my internal copy andD > I DO TEST EVERY SINGLE PAGE ON THE SERVER WITH NETSCAPE 3.03B with, > Java. I don't use the vax version anymore.  C The VMS server is a lot better than the idiots across at the Q. AndR; thank you for checking, there are just so many who don't...e  E > I don't know where the 'microsoft' comment came from. The server isiF > and has been Purveyor for OpenVMS for over 5 years. It is running on > an OpenVMS system.  C > In fact there is NO 'microsoft' type product being used by me fors, > web management, creation or anything else.  D Oh? so who is the tooth fairy who drops all the PPT files under yourD pillow? Or the COE presentations? I suspect you have missed a few...  E > I use EDT and/or TPU to edit my pages. I have for 5 years and whileCE > I might be moving to newer technology over the summer I still plaino4 > to make sure everything works with Netscape 3.03b.  D Yeah, nice to know that there is one person that deals with compaq'sE web pages who has a clue... I think you must be about the old one who  does though.  B > And also fyi.. On a monthly average the web site gets around 4.5F > million hits per month. Of those hits, more than 3 million come fromD > IE type browsers, and 800,000 from netscape type browers (the rest8 > are various other browers including Opera, Mosaic etc.  A > Of the 800,000 hits from netscape 3.x versions are about 60,000  > hits.c  C So how many of these non NS3 hits are from VMS systems? Perhaps VMS4D might be a metric of some small value on a VMS web site. We allready? know it counts for nothing to the idiots at the compaq main web  server.f    F > That's less than 10% of the Netscape hits and 1.5% of the total hits > for the month.  F > There's lots of things that we can't do on the site in order to makeF > sure that 3.03b continues to work. This is for the OpenVMS site only > not all of compaq.com.  ? > I added in the new survey in order to try to get some OpenVMS A > customer voices into the folks in Houston. I didn't make up the,D > survey and have very little input into it but I felt it was betterF > to have you all have the ability to give some feedback and representF > the OpenVMS customer base to the compaq.com folks rather than not do > anything at all.  E Simple. Give them a Vax, current VMS and the *STANDARD* browser. HookuI it up to a 28K serial line. Turn off Jave and JS, or implement a completee$ protected subsystem for the browser.  / And send the bugs to the web page black hole :(d   -- e< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.n@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov )   ------------------------------    Date: 09 May 2001 19:19:03 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: Xserver NodeNameo- Message-ID: <87r8xyydlk.fsf@prep.synonet.com>   = "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:z  ? > >How can I determine the nodename of the Xserver during login B > >Running VMS 6.2 on VAX 7000.  Xclients include VAXstation 4000,# > >unix machines, and NT computers.   F > Since the servers themselves know their own IP address, why not haveB > them send it as a parameter to a command procedure on the client: > system?  That's what we do.  The procedure then uses SETC > DISPLAY/CREATE/NODE='ip', where "ip" is the IP address the server  > sent.c  A And if you have multiple interfaces? Remember that machines don't % 'have' an IP address, interfaces do. s   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov :   ------------------------------  % Date: Wed, 09 May 2001 08:39:04 +0200 - From: Didier Morandi <didier.morandi@ubs.com> N Subject: Re: [EVENT] Post =?iso-8859-1?Q?Z=FCrich?= seminar event registration' Message-ID: <3AF8E608.3E447665@ubs.com>$   Sue Skonetski wrote: > 	 > Didier,  > : > I have sent this to all the OSSG folks  going to Zurich.  H Thanks. We are already 6 for the dinner and zero for the post-dinner :-)   D.   ------------------------------  % Date: Wed, 09 May 2001 13:27:28 +0100a- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>f Subject: Re: [OT] Religion) Message-ID: <3AF937B0.42839F79@bbc.co.uk>   $ system@niuhep.physics.niu.edu wrote:  J >  or are you just being sloppy in your failure to edit attribution lines? >C >O   i guess so.      --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.ukd  A I speak for myself only and my views in no way represent those of  MedAS or the BBC.    ------------------------------   End of INFO-VAX 2001.259 ************************