1 INFO-VAX	Thu, 09 Aug 2001	Volume 2001 : Issue 439       Contents:& ACCVIO problem - any help appreciated. Re: Alpha-IA64 FAQ Re: Alpha-IA64 FAQ Re: Alpha-IA64 FAQ+ Re: Any way to get a BA350 to work with NT? , Re: Apache on VMS - httpd.conf and .htaccessE Re: Automating MS Access with DCL code for a report run once a month.  Re: AW: SYBASE on VMS 6 Re: Backup disk on one system to tape drive on another2 Backup disk on one system to tape drive on another6 Re: Backup disk on one system to tape drive on another6 Re: Backup disk on one system to tape drive on another6 Re: Backup disk on one system to tape drive on another! Re: benchmarking disk performance  Re: Business LInk  Re: Business LInk  Re: Business LInk . Re: Can queue manager handle 100.000 entries ?. Re: Can queue manager handle 100.000 entries ?. Re: Can queue manager handle 100.000 entries ?. Re: Can queue manager handle 100.000 entries ?1 DECwindows keyboard problem: < > keys do not work 5 Re: DECwindows keyboard problem: < > keys do not work  Re: free software available  GEMBASE x OpenVMS 7.3  Re: HELP..VMSer in UNIX land Re: HELP..VMSer in UNIX land Re: HELP..VMSer in UNIX land Re: HELP..VMSer in UNIX land Re: HELP..VMSer in UNIX land/ Re: How to build a bootable media for a 11/780? / Re: How to build a bootable media for a 11/780?  RE: IA64 Rocks My World - Installing V7.3 on Personal Workstation 500au 1 Re: Installing V7.3 on Personal Workstation 500au 1 Re: Installing V7.3 on Personal Workstation 500au 1 Re: Installing V7.3 on Personal Workstation 500au 1 Re: Installing V7.3 on Personal Workstation 500au 6 Re: IPF Console Bootstrap (was: No chance for OpenVMS)! Re: Lemmings, was Re: Move to Sun ! Re: Lemmings, was Re: Move to Sun  Re: LPs on the Web Re: LPs on the Web" Re: LPs on the Web (Was: Re: DCPS) Re: Microsoft and Code red Re: Microsoft and Code red Re: Microsoft and Code red* Re: Microsoft and Code red (Cisco as well)* Re: Microsoft and Code red (Cisco as well)* Re: Microsoft and Code red (Cisco as well)) RE: Modems, Keyboard & Mouse Ports on VLC % Modems, Keyboard & Mouse Ports on VLC  Re: Move to Sun  Re: Move to Sun ) Mozilla M0.9.3, August 3rd release; Java?  NFS network protocol error Re: NFS network protocol error Re: OpenVMS (Itanium) wishes Re: OpenVMS and IA642 Premier Issue of Encompass Membership E-Newsletter( Qume QTV-202 keyboard and Dec 3000/300LX Red Code: where are we going? ! Re: Red Code: where are we going? % Re: REQ: VMS Baseball Cap (Help Sue?) % Re: REQ: VMS Baseball Cap (Help Sue?) 3 Re: Source for non-standard DEC 15 Amp power cords? 4 Re: Suggested DCPS features (was OpenVMS  + Itanium)< Re: suggested reading: "Making a Mountain Out of a Molehill"" Re: Sun goes after Alpha user base Re: Sun keep 'em coming  Re: SYBASE on VMS 9 Re: TCPware v5.5-3: file size change during FTP transfer? $ Re: Terry Shannon Tech Talk on Tru64$ Re: Terry Shannon Tech Talk on Tru64 Re: Third postcard from Sun  Re: Third postcard from Sun  Re: Third postcard from Sun  Re: Third postcard from Sun & uVAX 3100 M38 hardware troubleshooting= Re: very nice message also room for feedback on this web site  Re: VMS 7.3 experiences? Re: VMS 7.3 experiences?
 VMS Manual Re: VMS Manual Re: vmstar questions Re: vmstar questions Re: vmstar questions Re: vmstar questions Re: vmstar questions Re: vmstar questions
 Vortex Server ; Re: You Get What You Pay For, a.k.a., There's No Free Lunch < Re: [OT] Market corrections (was Re: Alpha: an invitation to  F ----------------------------------------------------------------------  # Date: Wed, 08 Aug 2001 21:52:47 GMT ) From: rob.buxton@wcc.govt.nz (Rob Buxton) / Subject: ACCVIO problem - any help appreciated. / Message-ID: <3b71a6c3.3428820@news.wcc.govt.nz>   	 Hi Folks,   7 Spent a while on this and I'm getting a tad frustrated. E We have a program that was working okay until I put a raft of patches  onto our Production Alpha.
 Patches were: 7 DEC VMS AVAIL_MAN V2.0              Full LP     Install  05-AUG-2001 12:14:557 DEC AXPVMS TCPIP_ECO V5.1-151       Patch       Install  05-AUG-2001 12:10:027 DEC AXPVMS DNVOSIECO03 V7.2         Patch       Install  05-AUG-2001 12:03:467 DEC AXPVMS VMS721_SHADOWING V6.0    Patch       Install  05-AUG-2001 12:00:507 DEC AXPVMS VMS721_RENAME_OLD V1.0   Patch       Install  05-AUG-2001 11:59:377 DEC AXPVMS VMS721_F11X V3.0         Patch       Install  05-AUG-2001 11:55:277 DEC AXPVMS VMS721_RMS V2.0          Patch       Install  05-AUG-2001 11:48:577 DEC AXPVMS VMS721_MANAGE V2.0       Patch       Install  05-AUG-2001 11:47:027 DEC AXPVMS VMS721_AUDSRV V1.0       Patch       Install  05-AUG-2001 11:45:317 DEC AXPVMS VMS721_SYS V10.0         Patch       Install  05-AUG-2001 11:34:407 DEC AXPVMS VMS721_UPDATE V3.0       Patch       Install  05-AUG-2001 11:28:19  ? These Patches were applied to our Development Alpha a few weeks  before. D So, on both Production and Development Alphas we're running the same# version of VMS (7.2-1) and Patches. A On Development the job runs fine, on Production it fails with the 
 ACCVIO below.    Print Date = 08-Aug-2001; %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual : address=000000000057E000, PC=000000000011EB20, PS=0000001B/ %TRACE-F-TRACEBACK, symbolic stack dump follows 9   image    module    routine             line      rel PC  abs PC  E I've copied all of the data files it uses to a separate directory and = used local assigns to reference the data to ensure there's no F different data. Still it fails on Production and works on Development.  : The User Quotas are higher on Production than Development.  D The run time also varies, the job should take about 7-8 minutes, but@ sometimes it fails immediately and other times after running for1 several minutes (almost to the end but not quite)   D It also works on the VAX variant of the image against the same data.  D Are there any SYSGEN Parameters that might influence this behaviour?  A The main difference I can see is that on Production we use Volume F shadowing and on Development we do not. I've tried moving all the dataF to a non-shadowed disk but that still failed. Also moved it to a local disk to rule out mscp serving.  ! Further tests & checks I've done. = Checked the link dates of the image being run on Production &  Development - it's the same @ Checked the dates on files in sys$library:, sys$loadable_images,F sys$system to ensure that the order of patches hasn't left a different image in place. B Used SDA and Availability Manager to watch for quotas and to watchB what files are held open and specifically ensure they're the same.  D On Production, we have two similary configured Alphas, the job failsE on both. On Development we have two Alphas, the second is on 7.3, the  job works on both of these.    Bewildered again!    Rob.   ------------------------------  $ Date: Wed, 8 Aug 2001 14:52:10 -0400' From: "Bill Todd" <billtodd@foo.mv.com>  Subject: Re: Alpha-IA64 FAQ ( Message-ID: <9ks1p6$jat$1@pyrite.mv.net>  3 "Peter da Silva" <peter@abbnm.com> wrote in message  news:9krkos$ctm@web.nmti.com... > > In article <q7wb7.9210$xj.1504287@typhoon.southeast.rr.com>,' > Ken Farmer <kfarmer@tru64.org> wrote: 7 > > http://www2.tru64.org/pages.php?page=Alpha-IA64-FAQ  >  > Alpha 4 -- Is Alpha dead?  > C >     Alpha will live on in IPF (Intel Processor Family). Intel and F >     Compaq have agreed to use Alpha EV8 technology to enhance futureH >     IPF technology. This allows Compaq to stop competing with industry? >     standards and focus on the higher level of the stack, OS, H >     compilers, and so forth. With the Alpha technology integrated intoD >     IPF, the performance curve will leave other RISC at the end of >     life.  > C > While I understand what you're trying to say, there is an obvious E > confusion here between implementation and architecture. Alpha is an C > architecture. What you mean is that technologies developed in the ? > implementation of the Alpha architecture will be used in IPF.   L Indeed, but the words sound a lot more like Compaq PR crap than like Ken.  IL hadn't realized the degree to which Tru64.org had, like SKC, become a CompaqJ PR arm since the Alpha debacle, but you'll find only Good News there theseI days, including uniformly-glowing customer comments on the decision.  The K statement about IPF incorporation of Alpha technology leaving other RISC at H EOL is an especially egregious marketing flatulence to find in something masquerading as a 'FAQ'.  H Of course, the desire to 'stop competing with industry standards' hardlyK stops at the hardware interface:  expect VMS and Tru64 to follow as soon as J Compaq deems it convenient, regardless of how its customers may feel aboutH the matter.  And as for compilers, I think the soi-disant 'FAQ' may haveL missed the major transfer of compiler technology, ownership, and development3 staff to Intel that accompanied the Alpha decision.    - bill   >  > --- >  `-_-'   In hoc signo hack, Peter da Silva. G >   'U`    "A well-rounded geek should be able to geek about anything." ; >                                                        --  nicolai@esperi.org >          Disclaimer: WWFD?   ------------------------------   Date: 8 Aug 2001 15:10:20 GMT & From: peter@abbnm.com (Peter da Silva) Subject: Re: Alpha-IA64 FAQ % Message-ID: <9krkos$ctm@web.nmti.com>   < In article <q7wb7.9210$xj.1504287@typhoon.southeast.rr.com>,% Ken Farmer <kfarmer@tru64.org> wrote: 5 > http://www2.tru64.org/pages.php?page=Alpha-IA64-FAQ    Alpha 4 -- Is Alpha dead?   A     Alpha will live on in IPF (Intel Processor Family). Intel and D     Compaq have agreed to use Alpha EV8 technology to enhance futureF     IPF technology. This allows Compaq to stop competing with industry=     standards and focus on the higher level of the stack, OS, F     compilers, and so forth. With the Alpha technology integrated intoB     IPF, the performance curve will leave other RISC at the end of	     life.   A While I understand what you're trying to say, there is an obvious C confusion here between implementation and architecture. Alpha is an A architecture. What you mean is that technologies developed in the = implementation of the Alpha architecture will be used in IPF.    --  +  `-_-'   In hoc signo hack, Peter da Silva. E   'U`    "A well-rounded geek should be able to geek about anything." L                                                        -- nicolai@esperi.org          Disclaimer: WWFD?   ------------------------------  # Date: Wed, 08 Aug 2001 23:40:02 GMT & From: "Ken Farmer" <kfarmer@tru64.org> Subject: Re: Alpha-IA64 FAQ ? Message-ID: <m5kc7.90097$J37.21085447@typhoon.southeast.rr.com>   2 "Bill Todd" <billtodd@foo.mv.com> wrote in message" news:9ks1p6$jat$1@pyrite.mv.net... > 5 > "Peter da Silva" <peter@abbnm.com> wrote in message ! > news:9krkos$ctm@web.nmti.com... @ > > In article <q7wb7.9210$xj.1504287@typhoon.southeast.rr.com>,) > > Ken Farmer <kfarmer@tru64.org> wrote: 9 > > > http://www2.tru64.org/pages.php?page=Alpha-IA64-FAQ  > >  > > Alpha 4 -- Is Alpha dead?  > > E > >     Alpha will live on in IPF (Intel Processor Family). Intel and H > >     Compaq have agreed to use Alpha EV8 technology to enhance futureJ > >     IPF technology. This allows Compaq to stop competing with industryA > >     standards and focus on the higher level of the stack, OS, J > >     compilers, and so forth. With the Alpha technology integrated intoF > >     IPF, the performance curve will leave other RISC at the end of
 > >     life.  > > E > > While I understand what you're trying to say, there is an obvious G > > confusion here between implementation and architecture. Alpha is an E > > architecture. What you mean is that technologies developed in the A > > implementation of the Alpha architecture will be used in IPF.     K Your right, that does sound like marketing material.  That's exactly what I I started it from.  It was the only info I had at the time that I could get K up.  Hey, it's a start, not something written in stone.  And like all FAQ's L it needs participation from the community.  I have limited time so I can use all the help I can get.     K > Indeed, but the words sound a lot more like Compaq PR crap than like Ken.  I G > hadn't realized the degree to which Tru64.org had, like SKC, become a  CompaqL > PR arm since the Alpha debacle, but you'll find only Good News there theseK > days, including uniformly-glowing customer comments on the decision.  The J > statement about IPF incorporation of Alpha technology leaving other RISC atJ > EOL is an especially egregious marketing flatulence to find in something > masquerading as a 'FAQ'.    E First of all I like to thank you Bill.  Your commentary has been both F entertaining and informative regarding this issue over the last month.  K PR arm?  I consider that a compliment.  What exactly did you think the site I was supposed to be about?  The purpose of the site is to offer assistance L and industry news to sysadmins/developers/tech managers, etc.  I'm trying toD spread positive information about Tru64, not kick it in the teeth orI alienate Compaq.  Alpha decision or no Alpha decision the material on the F site would be the same (more or less).  Don't confuse my enthusiam for/ Alpha/Tru64 with approval of Compaq's decision.   F I too have been shocked by the decision.  Terry Shannon and myself putH together the Alpha Transition Survey, recently available, to try and getJ some kind of an idea of how the technical end of the spectrum was feeling.F The results will be summarized soon.  I can promise you Compaq will beE reading it.  To me, that is doing something constructive to voice the J opinions of others.  I can even go as far as putting up a forum to discussL this issue.  I recently even emailed you asking if you wanted to participateH with a constructive article on the site, giving you opportunity to voiceJ your opinion, I even offered you cash  You stated you didn't think you hadK anything to offer the Tru64 community.  What more can I do, set you up your ' own website, bitchin-at-compaq.com?  :)     J > Of course, the desire to 'stop competing with industry standards' hardlyJ > stops at the hardware interface:  expect VMS and Tru64 to follow as soon asL > Compaq deems it convenient, regardless of how its customers may feel aboutJ > the matter.  And as for compilers, I think the soi-disant 'FAQ' may haveB > missed the major transfer of compiler technology, ownership, and development 5 > staff to Intel that accompanied the Alpha decision.     H Help me out here Bill.  Give me some questions and answers on compilers,J ownership or development and whatever else you think can offer information about the transition.    Ken      -- Ken Farmer, kfarmer@tru64.org  Tru64.org, http://www.tru64.org  Tru64.org Newsletter: < http://www2.tru64.org/pages.php?page=Newsletter-Registration   ------------------------------  % Date: Mon, 06 Aug 2001 20:38:42 -0500 / From: Chris Scheers <chris@applied-synergy.com> 4 Subject: Re: Any way to get a BA350 to work with NT?3 Message-ID: <3B6F46A2.EB35DCD7@applied-synergy.com>    Bill Bradley wrote:  > / > OT, but, I need this working for a project...  > I > We're running into a problem trying to get a StorageWorks array cabinet K > working.  I'm setting up NT4 Enterprise Sever w/SP6a, and have a BA350-SB F > cabinet with four SWXD3-WE 4.3 GB drives that I would setup in an NTM > software RAID 5 array as drive D.  The PC is a standard Dell GX200 with PCI G > slots, so, I cannot use the existing SCSI (DSSI?) cards from an Alpha  > server, which are EISA.  > N >  I've tried the following Adaptec SCSI adapters, but, none of them can "see" > the drives at the BIOS level:  >  > 3940 >  > 2930 > N > 2944 (this is a HV Differential SCSI, but, wasn't sure WHAT kind the cabinet > supports).  C While a BA350 works fine with NT, your configuration will not work.   G The BA350-SB is a narrow (8 bit) cabinet.  SWXD3-WE drives are wide (16 % bit).  They will not work in a BA350.   F You can either use your wide drives in a wide cabinet like a BA356, or( you can get narrow drives for the BA350.  
 Good luck!  G ----------------------------------------------------------------------- $ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com C   Fax: 817-237-3074l   ------------------------------  # Date: Wed, 08 Aug 2001 01:20:51 GMTQL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")5 Subject: Re: Apache on VMS - httpd.conf and .htaccessf8 Message-ID: <00A002F6.26DD46FD@SSRL04.SLAC.STANFORD.EDU>  ` In article <31ff7ddd.0108070652.456fcfa8@posting.google.com>, theop@itex.je (Theo Platt) writes:i >paszty@xoma.com (Nick Paszty) wrote in message news:<14ce1c21.0108021437.6c2d6c86@posting.google.com>...n
 >> hello all.a >> d7 >> thanks for the pointers.  i've got all this working.i >> sI >> now on to getting the .htaccess file to accept the password and figure ( >> out why my cgi scripts are dumping in >>   >> can't start child process >> 0
 >> errors. >> a
 >> cheers, >> a >> nick0 >> t >s >Nick, > D >We've just installed CSWS 1.0-1 (Open VMS 7.2-1, TCPware 5.4-3) and >are having cgi problems too.n >sE >We get a 500 Internal server error on the browser and these messages  >in the ERROR_LOG: > E >07-Aug-2001 15:21:13 [20407E96] GENERIC_SOCKETPAIR_inet: bind() - 49MB >[Tue Aug  7 15:21:13 2001] [error] [client 189.1.8.110] (49)can't9 >assign requested address : couldn't spawn child process: & >/apache$root/cgi-bin/test-cgi-vms.com >7' >Looking back in the archive if you do g >.* >DEFINE/SYSTEM/EXE TCPIP$DEVICE UCX$DEVICE >g >it should fix it. k >t >It didn't in our case.g >. >Any suggestions anyone ?0  L There wre patches for Multinet to make it run right with Apache/CSWS.  Check) with process to see if TCPware needs any.l   -- Alan       O =============================================================================== 0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056fM  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210sO ===============================================================================i   ------------------------------  % Date: Wed, 08 Aug 2001 00:02:17 -0500&C From: "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com>9N Subject: Re: Automating MS Access with DCL code for a report run once a month.I Message-ID: <craig.berry-C4D784.00021708082001@newsrump.sjc.telocity.net>u  5 In article <000201c11f60$9c133330$c408040a@lcms.org>,o(  Sue Pedersen <pedersen@lcms.org> wrote:  M > I'm not sure where to start with this project.  A colleage is taking a file N > from our VAX system and making a report with Access once a month.  A requestL > has been made to automate this process to happen on the 3rd of each month.L > I'm assuming I need to put this into the scheduler but I'm not sure how toK > get a report to run in Access from a DCL program.  Could you give me some5 > pointers??  E Well, there are lots of things you *could* do, though I doubt if you  H *want* to do most of them.  I assume "the scheduler" is on the VMS side H and that it is possible and appropriate for a machine running Access to A stay in some sort of "listening" mode permanently.  What kind of  F listening it does depends on what you give it to listen to on the VMS A side.  DCOM and/or CORBA and/or various messaging and middleware o> products could potentially give you the ability to initiate a D conversation from the VMS machine that would kick off the report in ? Access.  Some of the products and technologies are listed here:]  : <http://www.openvms.compaq.com/ebusiness/Integration.html>  F But that's all most likely overkill, and I think quite a few of these H only run on Alpha, not VAX.  A somewhat cruder version of the same idea B would be to transfer a file containing the data from the VAX to a F location where the Access database can get to it (via ftp or any of a E number of other methods).  You can periodically scan for a new file, oG then import it and run a report from it when it turns up.  If you want eE to get fancy, there is some Win32 system call (that I don't remember 2D the name of) that essentially posts a watchpoint on a directory and H returns control to your program whenever the directory has been written / to; that way you'd know a new file has arrived.H  H The crudest, simplest, and probably best and most robust solution would F be to scrap the Access report altogether and rewrite it to run on the F VAX; there are myriad ways to spit out HTML, XML, Postcript, PDF, and G other flavors of formatted or encoded text on VMS without resorting to 4> less reliable environments and precarious automated transfers.   ------------------------------  % Date: Wed, 08 Aug 2001 22:47:05 +0100l. From: Graham Burley <100625.30@compuserve.com> Subject: Re: AW: SYBASE on VMS. Message-ID: <3B71C169.29780B73@compuserve.com>  F Department of Justice State of Bern (Switzerland) Replaces Sybase With, InterSystems' Cach Post-Relational Database  - http://www.e-dbms.com/analysts/1998/bern.htmlp  	 Cach Q&Ae  ( http://www.e-dbms.com/cache/cacheqa.html    * fabio_compaq@ep-bc.petrobras.com.br wrote: >  > Jakobo > ! > Let's open this discussion ok ?  > H > Is there a way to port from Oracle RDB, Ingres, Sybase, Progress under	 > OpenVMSd  >  to Intersystems's Cach ????? > 	 > Regards0   ------------------------------  # Date: Wed, 08 Aug 2001 21:15:13 GMTl. From: Burnie M <burniem.NOSPAM@ozemail.com.au>? Subject: Re: Backup disk on one system to tape drive on anothere8 Message-ID: <70b3ntomn1c8n4ks6tdjemgt6gn3o36ndd@4ax.com>  % Use ABS/SLS. It is designed for this.t    0 On Wed, 08 Aug 2001 11:51:13 GMT, "Kari Keronen"# <kari.keronen@radiolinja.fi> wrote:t  L >How about to NFS mount the disks you want to backup to a system with a tape >drive and then do the backup ?d >eL >I have never tried how this works, because we use ABS to do our backups andJ >with that comes RDF (Remote Device Facility) that can do exactly what you& >want over the DECNET and we use that. >h >-Kari-i >u/ >Mark Hemker <hemker@home.com> wrote in article 0 ><0a51ntomma024eopujfq7mq8did1ig10in@4ax.com>...G >> I am trying to figure out a way to backup the disks on one system tosG >> the tape drive on another system.  Both system are running VMS 7.2-1eG >> and TCP/IP Services 5.0a.  The system with the tape drive has DECNETkG >> Phase IV installed and configured but the system with the disks doesmG >> not.  If necessary, I could install DECNET on the other system.  The$H >> systems cannot be clustered so I can't use TMSCP.  I am wanting to beF >> able to perform image backups as if the tape drive were attached to >> the system. >> e >> Thanks for any help,l >> Mark Hemker >> hemker@home.com >> o   ------------------------------  # Date: Wed, 08 Aug 2001 01:25:45 GMTe# From: Mark Hemker <hemker@home.com>d; Subject: Backup disk on one system to tape drive on anothera8 Message-ID: <0a51ntomma024eopujfq7mq8did1ig10in@4ax.com>  D I am trying to figure out a way to backup the disks on one system toD the tape drive on another system.  Both system are running VMS 7.2-1D and TCP/IP Services 5.0a.  The system with the tape drive has DECNETD Phase IV installed and configured but the system with the disks doesD not.  If necessary, I could install DECNET on the other system.  TheE systems cannot be clustered so I can't use TMSCP.  I am wanting to behC able to perform image backups as if the tape drive were attached to) the system.    Thanks for any help, Mark Hemker  hemker@home.com    ------------------------------  # Date: Wed, 08 Aug 2001 04:38:28 GMTg* From: "Jack Peacock" <peacock@simconv.com>? Subject: Re: Backup disk on one system to tape drive on anothertD Message-ID: <8n3c7.4694$nb4.429782@newsread1.prod.itd.earthlink.net>  0 "Mark Hemker" <hemker@home.com> wrote in message2 news:0a51ntomma024eopujfq7mq8did1ig10in@4ax.com...F > I am trying to figure out a way to backup the disks on one system to" > the tape drive on another system >cK One method, if you have enough disk, is to back up the non-tape system to aoE (large) file, then COPY/FTP that file to the tape system, and finally L transfer the backup image file to tape.  Cumbersome but you can automate it. The catch will be disk space.k    Jack Peacocko   ------------------------------   Date: 8 Aug 2001 13:42:46 GMTs5 From: koehler@bessta.gsfc.nasa.aspm.gov (Bob Koehler)r? Subject: Re: Backup disk on one system to tape drive on anothero/ Message-ID: <9krfkm$8mi$2@skates.gsfc.nasa.gov>   ^ In article <0a51ntomma024eopujfq7mq8did1ig10in@4ax.com>, Mark Hemker <hemker@home.com> writes:E >I am trying to figure out a way to backup the disks on one system toyE >the tape drive on another system.  Both system are running VMS 7.2-1oE >and TCP/IP Services 5.0a.  The system with the tape drive has DECNET E >Phase IV installed and configured but the system with the disks doesFE >not.  If necessary, I could install DECNET on the other system.  TheiF >systems cannot be clustered so I can't use TMSCP.  I am wanting to beD >able to perform image backups as if the tape drive were attached to >the system. >e  B Any possibility of switching to Multinet?  There's a remote deviceD utility that runs over Multinet, we use it for exactly this purpose.  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences Corporationu= GSFC Code 582 Flight Software   | Federal Sector, Civil GroupmI                                 | please remove any ".aspm" when replyingm   ------------------------------  % Date: Wed, 08 Aug 2001 11:14:20 -0400a2 From: rdeininger@mindspring.com (Robert Deininger)? Subject: Re: Backup disk on one system to tape drive on anotheroL Message-ID: <rdeininger-0808011114210001@user-2ive73a.dialup.mindspring.com>  D In article <0a51ntomma024eopujfq7mq8did1ig10in@4ax.com>, Mark Hemker <hemker@home.com> wrote:  F > I am trying to figure out a way to backup the disks on one system toF > the tape drive on another system.  Both system are running VMS 7.2-1F > and TCP/IP Services 5.0a.  The system with the tape drive has DECNETF > Phase IV installed and configured but the system with the disks doesF > not.  If necessary, I could install DECNET on the other system.  TheG > systems cannot be clustered so I can't use TMSCP.  I am wanting to beeE > able to perform image backups as if the tape drive were attached to 
 > the system.d   Possibilities:  D 1. Install and configure DECnet on the second node.  If you have the5 licenses, this is likely the fastest and easiest way.e  J 2. Configure an NFS server on the node with the disks, NFS mount the disks on the node with the tape.  I 3. Temporarily cluster the systems, just for the duration of the backup. 2I (The node with disks you want to back up could be a satellite of the nodet$ with the tape drive, or vice-versa.)  F 4. Software Partners has/had a remote tape product called Thruway if IJ remember correctly.  It made remote tape drives appear local.  When I lastF used it, it needed DECnet, but I suspect it can also use tcpip by now.  = BTW, you should seriously consider upgrading TCP/IP to V 5.1.    --   Robert Deininger rdeininger@mindspring.coml   ------------------------------   Date: 8 Aug 2001 22:35:40 -0700v1 From: keithparris_nospam@yahoo.com (Keith Parris)u* Subject: Re: benchmarking disk performance= Message-ID: <dba3451e.0108082135.3f7d0932@posting.google.com>   O Another VMS Freeware tool for this purpose is DISKBLOCK, with its TEST command.lC -------------------------------------------------------------------lC Keith Parris | parris at encompasserve dot org | VMS consulting on:nC Clusters, Disaster Tolerance, Internals, Performance, Storage & I/Oo   ------------------------------   Date: 7 Aug 2001 18:32:39 -0700h1 From: nothome@spammers.are.scum (Malcolm Dunnett)p Subject: Re: Business LInk, Message-ID: <6WMgq3eFe6F9@malvm6.mala.bc.ca>  ( In article <GHpztF.2H6@spcuna.spc.edu>, .     Terry Kennedy <terry@gate.tmk.com> writes:  ( > john nixon <jnixon@cfl.rr.com> writes:( >> It appears that they have killed DBL. > I >   For what it's worth, my DBL login still works and Compaq have assurediI > me that it won't go away until a workable replacement is available (forI
 > end users).  > F     Mine don't. They stopped working sometime in the last month. I got? an email from Compaq saying I should call a sales rep if I wantK information.  C     Surely they aren't stupid enough to think this is an equivalentsE option are they? How much "shopping around" is the sales rep going tot$ tolerate? Are they available 24 x 7?  E     I presume the problem is that the old businesslink doesn't run on > Windows and they haven't found a replacement that does yet :-)   ------------------------------  # Date: Wed, 08 Aug 2001 02:54:55 GMTo From: dittman@dittman.net  Subject: Re: Business LInkA Message-ID: <3S1c7.20613$5j7.1748060@e420r-atl1.usenetserver.com>   2 Malcolm Dunnett <nothome@spammers.are.scum> wrote:* : In article <GHpztF.2H6@spcuna.spc.edu>, 0 :     Terry Kennedy <terry@gate.tmk.com> writes:  ) :> john nixon <jnixon@cfl.rr.com> writes:c) :>> It appears that they have killed DBL.o :> uJ :>   For what it's worth, my DBL login still works and Compaq have assuredJ :> me that it won't go away until a workable replacement is available (for :> end users). :> tH :     Mine don't. They stopped working sometime in the last month. I gotA : an email from Compaq saying I should call a sales rep if I wanth : information.  H I had the same thing happen.  When I complained I was told I could applyG for some kind of reseller's account on some other system, but that's nouF use for me.  When I replied that the site said the system would remainH available for users in the US I was told that someone would take care ofJ the problem.  I've even sent a follow-up email, but still have no account. -- e Eric Dittman dittman@dittman.netp   ------------------------------  % Date: Wed, 08 Aug 2001 17:19:22 -0500 / From: Chris Scheers <chris@applied-synergy.com>Y Subject: Re: Business LInk3 Message-ID: <3B71BAEA.1D444B42@applied-synergy.com>m   Terry Kennedy wrote: > ( > john nixon <jnixon@cfl.rr.com> writes:) > > It appears that they have killed DBL.m > I >   For what it's worth, my DBL login still works and Compaq have assuredeI > me that it won't go away until a workable replacement is available (ford
 > end users).  > H >   Note that even when they "kill" stuff, it's still around - for a funH > time, telnet to "orders.sales.digital.com" - that's the old "Digital'sI > Electronic Connection", and it is lonely and would like some of its old H > friends to visit it every now and again. Your old e-store account num-F > ber and password should still work (I just tried mine to make sure).  = Interesting.  I thought they had turned that off a while ago.a  G Unfortunately, my login no longer works.  It lets me log in, but then IeE get various errors such as "The menu entry point can not be found..." G and "Temporary header file cannot be REwritten...", then it disconnects  me.  <sigh>c  : Fortunately, my Busnesslink login still works.  (For now.)  G -----------------------------------------------------------------------c$ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com a   Fax: 817-237-3074t   ------------------------------  # Date: Wed, 08 Aug 2001 19:30:51 GMT 3 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk>u7 Subject: Re: Can queue manager handle 100.000 entries ?o/ Message-ID: <3B7191BE.3BF7AE6F@cableinet.co.uk>d   Jan-Erik Sderholm wrote:l > B > Yes, probably in most cases, but I'd prefer to *know* that I can? > run my BATCH *even* if the smtp gateway isn't available until B > later. Or add some check to the BATCH routine to "hold" when theF > smtp queue length goes over some value, let's say 1000 queued mails.H > That is, *if* there is a problem with VLEC (Very Large Entry Count :-) > ). >  > Jan-Erik Sderholm.u >   G Sounds to me like you really need to run some real tests. You do have ar development @ environment, don't you? Won't take long to write a .COM to send @ emails in a loop. Choose your target email addresses for testing
 carefully,H make sure the people running your SMTP gateway are aware of what you are	 planning.-   regards-   > JF Mezei wrote:r > >p< > > By the time you've finished writing the emails, the vast( > > majority might already be sent away.  < Pure speculation. My take is let VMS take the load unless itB explicitly does break (you may need to tune) rather than inventing: ad hoc strategies to deal with a problem that may not even8 exist. Only testing will reveal if there is any problem.   regards    -- . Tim.Llewellyn@cableinet.co.uk  0  C Standard disclaimer applies. My views in no way represent those of  ! my employers or service provider.e   ------------------------------  % Date: Wed, 08 Aug 2001 21:53:52 +0200h< From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>7 Subject: Re: Can queue manager handle 100.000 entries ?l( Message-ID: <3B7198D0.765D1726@home.com>   Just 2 things...: 1. It wasn't me that asked in the first place, but anyway.4 2. The question was if the VMS queue subsystem could;    "store" 100.000 entries, not it they could be mailed out1G    of the system. So you could just as well $PRINT a file 100.000 timesnB    to a stopped temporary queue and then just delete the queue, or@    perhaps print a few files just to verify the the QUEMGR still    does what it should.u>    You will not upset anyone, besides perhaps if you have someA    "intelligent" tool that are monitoring your queues for pendingo    entries :-)  	 Jan-Erik.7   Tim Llewellyn wrote: > I > Sounds to me like you really need to run some real tests. You do have au
 > developmenttA > environment, don't you? Won't take long to write a .COM to send B > emails in a loop. Choose your target email addresses for testing > carefully,J > make sure the people running your SMTP gateway are aware of what you are > planning.= > 	 > regards=   ------------------------------  # Date: Wed, 08 Aug 2001 21:28:38 GMTE3 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk> 7 Subject: Re: Can queue manager handle 100.000 entries ?S/ Message-ID: <3B71AD52.494F54CA@cableinet.co.uk>s   Jan-Erik Sderholm wrote:= >  > Just 2 things...< > 1. It wasn't me that asked in the first place, but anyway.  ? yup, usenet can be like that. Sorry if you didn't like my tone.<  6 > 2. The question was if the VMS queue subsystem could= >    "store" 100.000 entries, not it they could be mailed outtI >    of the system. So you could just as well $PRINT a file 100.000 timestD >    to a stopped temporary queue and then just delete the queue, orB >    perhaps print a few files just to verify the the QUEMGR still >    does what it should.e  D OK, in that case why not just submit some tiny job that does nothingD to a temporary, stopped queue? I don't have priv'd VMS access to try myself,o sorry.  f@ >    You will not upset anyone, besides perhaps if you have someC >    "intelligent" tool that are monitoring your queues for pendingp >    entries :-)  9 Their logfiles might get a little large I suppose, and ofsA course make sure the queue manager has plenty of free disk space..   regards"    -- u Tim.Llewellyn@cableinet.co.uk  t  C Standard disclaimer applies. My views in no way represent those of i! my employers or service provider.m   ------------------------------  % Date: Tue, 07 Aug 2001 21:36:14 -0400l- From: JF Mezei <jfmezei.spamnot@videotron.ca>a7 Subject: Re: Can queue manager handle 100.000 entries ?p+ Message-ID: <3B70978E.346793A@videotron.ca>    Jan-Erik Sderholm wrote:aB > Yes, probably in most cases, but I'd prefer to *know* that I can: > run my BATCH *even* if the smtp gateway isn't available   J There was a thread some time ago about what happens if there are more thanM 1000 queue entries and the message from the all mighty VMS engineers was thatrN the queue system could handle more than 1000 entries but that the behaviour inK terms of numbering the entries was not documented (eg: the engineers didn't K want to reveal the trick because this was something which could change fromf version to version).   ------------------------------   Date: 08 Aug 2001 19:28:18 GMT' From: "Jim Strehlow" <jims@data911.com>a: Subject: DECwindows keyboard problem: < > keys do not work0 Message-ID: <9ks3si$3b7@dispatch.concentric.net>  A I have seen several postings regarding keyboard keys not working;y- but not regarding the following specifically.s  @ I had the following problem and I have noted the solution below.   Problem:D The  <  >  keys do not work within the DECterm (DCL) terminal window at monitors running DECwindows.L  B On the standard Digital/Compaq keyboards for a DECwindows monitor,L the [< , ] key, the [> . ] key, and the special [< >] key to the left of the [Z] keyr" all work at the username text box.@ That demonstrates that the keys physically work on the keyboard.  G When I click on the DECWindows DECterm icon and enter DCL commands, theCC  <  and  >  characters above the comma and period keys do not work.S  	 Solution:e  On the DECterm window,S1    - click on the menu bar: [Options], [Keyboard]w2    - click the radio button: (*)comma key sends <,4    - click on the menu bar: [Options] [Save Options]    * Does anyone know why the DECterm option of      comma key sends " is the default?    Jim Strehlow, Data911  Alameda, CAc jimS@data911.com   ------------------------------  % Date: Wed, 08 Aug 2001 22:19:07 +0200e, From: Didier Morandi <Didier.Morandi@gmx.ch>> Subject: Re: DECwindows keyboard problem: < > keys do not work& Message-ID: <3B719EBB.CC1129DB@gmx.ch>   Jim Strehlow wrote:a  I > When I click on the DECWindows DECterm icon and enter DCL commands, the>E >  <  and  >  characters above the comma and period keys do not work.5  G I have the same behaviour and probably all of us. Only the < and > keyst/ which are on the left of the space bar do work.y   D.   ------------------------------  # Date: Wed, 08 Aug 2001 17:58:49 GMT - From: goathunter@goatley.com (Hunter Goatley)s$ Subject: Re: free software available1 Message-ID: <3b717d63.139449477@news.process.com>v  D On Wed, 8 Aug 2001 10:51:54 -0500, norm.raphael@jamesbury.com wrote:   >o >w
 >Dear Sue, >  I'm not Sue, but.....q  + >While I am pleased by this generous offer,iC >I am confused by this message.  Is this available at the events orv3 >by download at the url provided or either or both.- >  >How should one proceed? > > They regularly post this URL to comp.os.vms, so have at it, if	 you want.g  ? They wanted me to include the software in my freeware archives,c> but I declined to do so because it's not really freeware (it's= one free license, but there's a cost for more).  That's not alA criticism of they're giving it away---I think that's great.  It's>C just not something that I felt I could put in my freeware archives.e  * Same with the txt2pdf shareware people....   Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/c9 goathunter@goatley.com     http://www.goatley.com/hunter/n   ------------------------------  $ Date: Wed, 8 Aug 2001 15:19:52 -0300+ From: <fabio_compaq@ep-bc.petrobras.com.br>  Subject: GEMBASE x OpenVMS 7.3L Message-ID: <OFD95F2C57.A982DA36-ON03256AA2.00644999@ep-bc.petrobras.com.br>  H Who is using  GEMBASE ? I am planning to upgrade my systems to OpenVMS = 7.3. when I have window time.  H I would like to know what GEMBASE version is compatible wih OVMS 7.3 an= d if you  have considerations.  , Actually I have GEMBASE 6.0 running OVMS 7.2   Regardsm   F=E1bio Cardosoh        H                                                                        =            =20H                     <danco@pebble                                      =            =20H                     .org>                Para:                         =            =20H                                          fabio_compaq@ep-bc.petrobras.c= om.br      =20H                     27/04/2001           cc:                           =            =20H                     01:00                Assunto:     Re: passwords    =            =20H                                                                        =            =20H                                                                        =            =20         In comp.os.vms, you wrote:  H >There is an procedure (application) developed in GEMBASE with the list=  ofc >users in Oracle RDB database.H >All the "end users", except SYSTEM, FIELD, etc .. are in this database= , so' >the help desk can change the passwordso@ >without performing a password change in the priviliged account.  F Note that GEMBASE V6.1.6 (not out yet) has a password change dialog inE both the fat and thin clients that allows users to change server-sideoB passwords via the broker.  This works with every GEMBASE supportedH server platform.  Password and account expirations (for those platforms=  F that support them) are also checked (and give advance warnings to thin	 clients).b   - Dans     =h   ------------------------------   Date: 8 Aug 2001 12:31:23 GMTe1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)s% Subject: Re: HELP..VMSer in UNIX lande, Message-ID: <9krber$13b6$1@info.cs.uofs.edu>  + In article <3B7048A3.96D63AED@softapp.com>,n-  Fletcher Hearns <hearns@softapp.com> writes:s
 |> Hello all,e |> l> |> I have a question for all you VMSers now working with UNIX. |> -; |> I have a text file that I need to modify.  I need to add- |> something toe7 |> the beginning and something to the end of each line.S
 |> Basically:g |> f |> "This is line 1"  becomes |> "ABC This is line 1 XYZ"  |>  5 |> I can think of several way to do this on VMS using-> |> either a DCL command procedure or and editor invoked with a? |> command procedure.  But I am having trouble figuring out how:< |> to do this on UNIX (Tru64). I have looked at both SED and8 |> AWK and made some headway. Using SED I can figure out3 |> how to add the ABC to each line but not the XYZ.8 |> g! |> Any help would be appreciated.@ |> cH I will assume you want the output file to be the same as the input file." sed was the best tool for the job.  H Create a file called sed.script (or something of your choice) containing
     s/^/ABC /h
     s/$/ XYZ/   J Create another file called do_sed (or something of your choice) containing     sed -f sed.script $1 >tmpfile    rm $1;mv tmpfile $1  % Make it executable (chmod u+x do_sed)l0 Invoke with:  do_sed name_of_file_to_be_modified  < This is only one of many possible ways, but it is simple and
 re-usable.   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   e   ------------------------------   Date: 8 Aug 2001 12:34:17 GMT 1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)b% Subject: Re: HELP..VMSer in UNIX landt, Message-ID: <9krbk9$13b6$2@info.cs.uofs.edu>  ) In article <3B71126D.930A8CD8@gtech.com>,t@  Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> writes: |> Fletcher Hearns wrote:a@ |> > I have a question for all you VMSers now working with UNIX. |> > .= |> > I have a text file that I need to modify.  I need to add1 |> > something toD9 |> > the beginning and something to the end of each line.- |> > Basically:e |> >   |> > "This is line 1"  becomes |> > "ABC This is line 1 XYZ"  |> > u7 |> > I can think of several way to do this on VMS using @ |> > either a DCL command procedure or and editor invoked with aA |> > command procedure.  But I am having trouble figuring out howl> |> > to do this on UNIX (Tru64). I have looked at both SED and: |> > AWK and made some headway. Using SED I can figure out5 |> > how to add the ABC to each line but not the XYZ.l |> r3 |> I think you should spend the time to learn Perl.- |>  / |> I will solve a lot of this kind of problems.@  , Using a sledgehammer to put in thumbtacks!!!   bill   -- kJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   t   ------------------------------  % Date: Tue, 07 Aug 2001 19:42:34 -0500t- From: "David L. Nicol" <david@kasey.umkc.edu>a% Subject: Re: HELP..VMSer in UNIX land . Message-ID: <3B708AFA.2DFC54FE@kasey.umkc.edu>   Fletcher Hearns wrote:   > "This is line 1"  becomesc > "ABC This is line 1 XYZ" > 4 > I can think of several way to do this on VMS using= > either a DCL command procedure or and editor invoked with a > > command procedure.  But I am having trouble figuring out how; > to do this on UNIX (Tru64). I have looked at both SED ands7 > AWK and made some headway. Using SED I can figure outp2 > how to add the ABC to each line but not the XYZ. >   > Any help would be appreciated.  7 I guess you want to do this as part of a script, rathers8 than with an editor.  The following perl one-liner will  work with a stream:a  - cat Old | perl -ple'$_ = "ABC $_ XYZ"' | more   : And here's how to apply it to all the files in the current' directory whose names start with "This"   % perl -i -ple'$_ = "ABC $_ XYZ"' This*t      , perl for VMS exists.  Is it widely deployed?     -- sC                                            David Nicol 816.235.1187i free Dmitry Skylarov   ------------------------------  % Date: Wed, 08 Aug 2001 13:56:36 +0100d0 From: andrew harrison <andrew.nospam@uk.sun.com>% Subject: Re: HELP..VMSer in UNIX landn* Message-ID: <3B713704.167BDAFF@uk.sun.com>   Pat Rankin wrote:h > . > In article <3B7048A3.96D63AED@softapp.com>,\1 >  Fletcher Hearns <hearns@softapp.com> writes...n > [...]e > > "This is line 1"  becomeso > > "ABC This is line 1 XYZ" > [...]d >  > With awk, either3 >   awk '{print "ABC " $0 " XYZ"}' <infile >outfilen > or3 >   awk '{print "ABC", $0, "XYZ"}' <infile >outfile-@ > would do it.  The solution with sed should be equally trivial,< > and it is probably the most appropriate Unix tool for this= > simple job, but I'd have to look at its man page to get thes > right syntax.... > 4 >                 Pat Rankin, rankin@eql.caltech.edu  + You can also do this with the shell itself.   	 #!/bin/shn
 initial="ABC">	 end="XYZ"   echo "Enter file to convert :\c" read a
 case $a in "")i          echo "Invalid file name"         exit;; *)         rm -f $a.convn         cat $a | while read Al
         do)         echo "$initial $A $end" >>$a.conve         done
         ;; esac     -- t Andrew Harrisona Enterprise IT Architecto   ------------------------------  % Date: Wed, 08 Aug 2001 09:29:17 -0400o+ From: Brendan Welch <brendan_welch@uml.edu>t% Subject: Re: HELP..VMSer in UNIX land ' Message-ID: <3B713EAD.6C432FE8@uml.edu>    Fletcher Hearns wrote: >  > Hello all, > = > I have a question for all you VMSers now working with UNIX.e > : > I have a text file that I need to modify.  I need to add > something to6 > the beginning and something to the end of each line. > Basically: >  > "This is line 1"  becomeso > "ABC This is line 1 XYZ" > 4 > I can think of several way to do this on VMS using= > either a DCL command procedure or and editor invoked with a-> > command procedure.  But I am having trouble figuring out how; > to do this on UNIX (Tru64). I have looked at both SED and 7 > AWK and made some headway. Using SED I can figure out82 > how to add the ABC to each line but not the XYZ. >   > Any help would be appreciated. >  > -- > Fletcher Hearnsl > President/Consultant	 > S*A*I*LC > 2828 Brian Ct. > Ellicott City MD 21043 > 410-465-2391 > hearns@softapp.com  B I think I learned this from the book "UNIX for VMS Users", Bourne, Digital Press.  % Use the editor "ex" on filename "xyz"H   ex xyzA 1,$  sub/"This"/"ABC This/     !takes care of the beginning;  1,$k means for lines /                                !1 through last.oF                                !for the end of each line, if each line
 has differentLF                                !text at the end, offhand I don't think ex is ,                                !appropriate.4 wq         !write out the file xyz and quit normally   --E Brendan Welch, system analyst, Univ. of Massachusetts - Lowell, W1LPGa   ------------------------------  # Date: Wed, 08 Aug 2001 03:13:13 GMTg# From: ualski <ualski@earthlink.net>y8 Subject: Re: How to build a bootable media for a 11/780?- Message-ID: <3B70AE32.67180361@earthlink.net>m   John Santos wrote: > ) > On Tue, 7 Aug 2001, Hoff Hoffman wrote:u > f > > In article <3b704888$1@news.si.com>, "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:H > > :>Do a 11/780 read CD drive or so for installing OpenVMS v7.2 from a > > :>scratch? > >l# > >   System configuration, please?eF > >   You will need an RX01 (8 inch floppy disk) containing standaloneF > >   BACKUP for OpenVMS VAX, or you will need standalone BACKUP on anI > >   RL02 or similar removable disk media.  IIRC, you can also bootstrap:H > >   this system from tape media, so if you have a supported TMSCP tapeH > >   drive (TU78, TA78, etc), you could boot off that.  If you can swapI > >   a DSA-class (RA) disk over to another system via UDA50/KDA50/BDA50,iE > >   you could load the kit contents onto the disk and swap it back.b > A > I'm not sure if you could boot the 780 from tape.  The standarduH > install procedure was to boot from S/A backup floppies (required aboutE > 5-6 floppies as of the latest version), restore the .B saveset from F > 9-track tape to a disk, boot that disk and proceed with the install.H > (At one time, you could also get VMS kits on various removeable disks,G > such as RA60's, and maybe RM03's and RL02's, but that was a long timen > ago.)t  G I'm pretty sure VMS would boot from tape.  I remember running essaa (or J whatever the diag supervisor was called) from a TE16. (which was on a TM03J hanging off a Massbus adapter).  I can't recall if that was a special caseJ but it could be done.  I do remember it was slow, but quite as bad as xxdpI starting from a TU58.  Too bad you don't have those 785's any more.  TheygF were fun machines to play around with and you could fix them yourself.   -- Aaron Sliwinski   ------------------------------  % Date: Tue, 07 Aug 2001 23:59:14 -0400e' From: Howard S Shubs <howard@shubs.net>g8 Subject: Re: How to build a bootable media for a 11/780?< Message-ID: <howard-0F488A.23591407082001@enews.newsguy.com>  6 In article <1010807175220.44635A-100000@Ives.egh.com>,"  John Santos <JOHN@egh.com> wrote:  H > I don't know if it was supported, but I had two customer systems usingD > 11/785's on VMS V7.1.  They both worked fine.  (Booting took aboutI > 15 minutes, after I tried every trick I could think of to speed it up.)   K Given that the VAX-11/780 and the VAX-11/785 are two different boxes, that aM doesn't mean much.  I can tell you from experience that if they say it won't KK work, it won't work.  The final version, IIRC, of STABACKUP that you could oN build for an 11/780 was the one which came with VAX/VMS 5.1, which dates from N around 1989 or 1990, did not come on CD-ROM, and which might not work even if O you can find media which at one time contained that version.  I tried building iL a STABACKUP from VAX/VMS 6.1 even though they said it wouldn't work, and it  didn't.g  M I'm not saying you can't run a VAX-11/780, but you're going to have to go on .O an archalogical dig in some one's files to find appropriate versions of system  	 software.s -- e Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"   ------------------------------  $ Date: Wed, 8 Aug 2001 14:28:40 -0400+ From: "Main, Kerry" <Kerry.Main@compaq.com>g  Subject: RE: IA64 Rocks My WorldR Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF4D4956D@kaoexc01.americas.cpqcorp.net>   Andrew,t  G >> it failed abjectly because most of the references arn't customers <<   I Yep, you are right. These ISV's must promote their app's running on theseeG servers because they like to use them for their own use. They could noth2 possibly have end user Customers for them. Right ?   sigh ..   
 Over and out.m    
 Kerry Main Senior Consultantd Compaq Canada Corp.g Professional Services  Voice: 613-592-4660u Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----7 From: andrew harrison [mailto:andrew.nospam@uk.sun.com]m Sent: August 8, 2001 1:19 PM To: Info-VAX@Mvb.Saic.Com   Subject: Re: IA64 Rocks My World       "Main, Kerry" wrote: > 	 > Andrew,e > D > >> So stop marketing your TPC-C result as being an indication that	 WildFires 0 > are suitable boxes for high end OLTP apps. <<< > K > Go bother the TPC Council .. this issue has been beaten to death already.  > I > As for the Wildfire suitability in high end apps, check these folks outn forwH > recent examples of mission critical Alpha GS Series / VMS  OLTP usage: (and# > they are not using Oracle Server)hH > http://www.openvms.compaq.com/openvms/brochures/Bank-Austria/ (Bank of
 > Austria) > Others can be found at:k4 > http://www.openvms.compaq.com/gsseries/quotes.html  3 This apparently contains customer references but !!h   Bank of Austriar- 	Customer but not a GS320 user (treasury appso' 	are generally report/batch intensive).w BEA * 	Not a customer its an ISV endorsment and 0 	commitment to OpenVMS now lags other platforms 
 	(WLS etc) BCDk& 	Not a customer its an ISV endorsement Cerner+ 	Not a customer its another ISV endorsement  Cognos0 	Not a customer its another ISV endorsement and 5 	Cognos are also actively offering "Legacy (OpenVMS)"-) 	migration tools to non legacy platforms.2 CA- 	ISV endorsment and advert for Unicenter TNG.i	 Inovawareu 	ISV endorsement Kenanb 	ISV endorsement KCSL 	ISV endorsement Memorial HermanC< 	At last another customer (this was supposed to be a list of* 	customers so its nice that one popped up) Northern Lights  	Ohhh another Customer Oracle6 	ISV endorsement from a vendor that has been gradually2 	dropping support for OpenVMS for all but its core 	DBMS products.e Parexcel	 	Customerr SASo 	ISV endorsement Southeastern Freight -	 	Customer   8 So you publish a list of 15 customer endorsements which 6 actually consists of 5 customers and 10 ISV's. None of4 the customers except the Bank of Austria go into any3 detail on what they are actually using, the Bank ofe2 Austria is using a GS160 and a GS140 in a cluster.  0 Very few of these appear to be OLTP references !  " So what was your point exactly ???  4 If it was to convince people that there are glowing < OLTP GS references from customers it failed abjectly because7 most of the references arn't customers and most of the , references arn't OLTP either.    Regardse Andrew Harrisonh Enterprise IT Architect    ------------------------------  $ Date: Wed, 8 Aug 2001 14:40:55 -04003 From: "Pohl, Kathy" <Kathy.Pohl@itec.mail.suny.edu>a6 Subject: Installing V7.3 on Personal Workstation 500auG Message-ID: <0B41ACBECF83734D98ABC83DD8E097E1C4A7@cipher.itec.suny.edu>f  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01C12039.A885A4C0o Content-Type: text/plain;- 	charset="iso-8859-1"-     	Hi,  A 	I am trying to install OpenVMS Alpha V7.3 on my Digital personalo workstation 500au.E 	I boot it using the command >>> boot dkb0 .  It starts to boot and I9 get the message:E 	"OpenVMS Alpha Operating System, Version V7.3" and then it hangs.  Io have updated@ 	the firmware already.  I have read all the installation doc and can't seem to get beyond this. 	What next?    	Thanks, 	Kathy  ' ------_=_NextPart_001_01C12039.A885A4C0n Content-Type: text/html; 	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">  <HTML> <HEAD>9 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =  charset=3Diso-8859-1">@ <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 5.5.2653.12"> = <TITLE>Installing V7.3 on Personal Workstation 500au </TITLE>  </HEAD>  <BODY> <BR>  > <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 = FACE=3D"Arial">Hi,</FONT>  </P>  > <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =H FACE=3D"Arial">I am trying to install OpenVMS Alpha V7.3 on my Digital =" personal workstation 500au.</FONT>? <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 = C FACE=3D"Arial">I boot it using the command &gt;&gt;&gt; boot dkb0 =e6 &nbsp; It starts to boot and I get the message:</FONT>? <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =SI FACE=3D"Arial">&quot;OpenVMS Alpha Operating System, Version V7.3&quot; =h. and then it hangs.&nbsp; I have updated</FONT>? <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =u@ FACE=3D"Arial">the firmware already.&nbsp; I have read all the =: installation doc and can't seem to get beyond this.</FONT>? <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =f  FACE=3D"Arial">What next?</FONT> </P>  > <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 = FACE=3D"Arial">Thanks,</FONT>l? <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =a FACE=3D"Arial">Kathy</FONT>  </P>   </BODY>l </HTML>.) ------_=_NextPart_001_01C12039.A885A4C0--V   ------------------------------   Date: 8 Aug 2001 13:34:24 -0700n& From: robyoung@my-deja.com (Rob Young): Subject: Re: Installing V7.3 on Personal Workstation 500au= Message-ID: <9c40b5bf.0108081234.30d00fa5@posting.google.com>n   "Pohl, Kathy" <Kathy.Pohl@itec.mail.suny.edu> wrote in message news:<0B41ACBECF83734D98ABC83DD8E097E1C4A7@cipher.itec.suny.edu>... > Hi,  > C > 	I am trying to install OpenVMS Alpha V7.3 on my Digital personalB > workstation 500au.G > 	I boot it using the command >>> boot dkb0 .  It starts to boot and I  > get the message:G > 	"OpenVMS Alpha Operating System, Version V7.3" and then it hangs.  It > have updatedB > 	the firmware already.  I have read all the installation doc and  > can't seem to get beyond this.
 > 	What next?  >   A The upgrade went smoothly?  Assuming that... try booting SYSBOOT:>  " >>> boot -fl root,flags  boot_dev:   by example:    >>> boot -fl 0,1 dkb0:   SYSBOOT> SET WRITESYSPARAMS 0  SYSBOOT> SET STARTUP_P1 "MIN"o SYSBOOT> CONTINUE   D When you get in, comment out your TCP/IP startup and go back and tryI a complete boot.  If using Multinet, you have to get to 4.3 , can't speaku for the other packages.s   Robe   ------------------------------  $ Date: Wed, 8 Aug 2001 18:07:53 -0400  From: John Santos <JOHN@egh.com>: Subject: Re: Installing V7.3 on Personal Workstation 500au6 Message-ID: <1010808180505.44635E-100000@Ives.egh.com>   On 8 Aug 2001, Rob Young wrote:e   > "Pohl, Kathy" <Kathy.Pohl@itec.mail.suny.edu> wrote in message news:<0B41ACBECF83734D98ABC83DD8E097E1C4A7@cipher.itec.suny.edu>... > > Hi,c > > E > > 	I am trying to install OpenVMS Alpha V7.3 on my Digital personal- > > workstation 500au.I > > 	I boot it using the command >>> boot dkb0 .  It starts to boot and Ia > > get the message:I > > 	"OpenVMS Alpha Operating System, Version V7.3" and then it hangs.  In > > have updatedD > > 	the firmware already.  I have read all the installation doc and" > > can't seem to get beyond this. > > 	What next?I > >  > C > The upgrade went smoothly?  Assuming that... try booting SYSBOOT:  > $ > >>> boot -fl root,flags  boot_dev: > 
 > by example:t >  > >>> boot -fl 0,1 dkb0: >  > SYSBOOT> SET WRITESYSPARAMS 0- > SYSBOOT> SET STARTUP_P1 "MIN"" > SYSBOOT> CONTINUEm > F > When you get in, comment out your TCP/IP startup and go back and tryK > a complete boot.  If using Multinet, you have to get to 4.3 , can't speakn > for the other packages.p >  > RobB  E Can you clarify: Are you booting the VMS installation CD (i.e. at the.F start of the installation process) or have you done that and installedF VMS on a target disk (presumably DKB0:) and are now trying to boot theE target disk for the 1st time?  In other words, is DKB0: your CD drive> or your new system disk?  B If you are booting the CD, then it is probably a CD drive problem.E Is it a DEC/Compaq CD drive or 3rd party?  (What does >>> show deviceeA show for it?)  If 3rd-party, is it a drive that is known to work?o? See the FAQ and search the history of this newsgroup and/or askyD here for requirements and other peoples experiences with this drive.A If 3rd-party, is it configured correctly?  (VMS requires it to bevF set to 512-byte block size.  Some drives can't be set this way, others< have a jumper.  There are probably other requirements, too.)  @ If the CD is known to be a supported model, is it an IDE or SCSI? drive?  Some (all?) IDE drives require an auxiliary boot floppygB containing the drivers to boot from CD for some or all versions of VMS.  ? If all the above checks out, boot into SYSBOOT as Rob suggesteds and see what happens.e  ; If the problem is booting your target system disk after theD= install, then also try booting into SYSBOOT as Rob suggested.h   HTH    -- n John Santosb Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------   Date: 8 Aug 2001 17:59:50 -0500l9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)=: Subject: Re: Installing V7.3 on Personal Workstation 500au3 Message-ID: <qnxNe+6Xmimg@eisner.encompasserve.org>   } In article <0B41ACBECF83734D98ABC83DD8E097E1C4A7@cipher.itec.suny.edu>, "Pohl, Kathy" <Kathy.Pohl@itec.mail.suny.edu> writes: L > This message is in MIME format. Since your mail reader does not understand> > this format, some or all of this message may not be legible.  $ So I won't bother reading any of it.  ' Please do not send MIME to comp.os.vms.V   ------------------------------   Date: 8 Aug 2001 18:20:40 -0700 & From: robyoung@my-deja.com (Rob Young): Subject: Re: Installing V7.3 on Personal Workstation 500au= Message-ID: <9c40b5bf.0108081720.61cb1838@posting.google.com>   ^ John Santos <JOHN@egh.com> wrote in message news:<1010808180505.44635E-100000@Ives.egh.com>...! > On 8 Aug 2001, Rob Young wrote:r >  > > "Pohl, Kathy" <Kathy.Pohl@itec.mail.suny.edu> wrote in message news:<0B41ACBECF83734D98ABC83DD8E097E1C4A7@cipher.itec.suny.edu>...	 > > > Hi,n > > > G > > > 	I am trying to install OpenVMS Alpha V7.3 on my Digital personal  > > > workstation 500au.K > > > 	I boot it using the command >>> boot dkb0 .  It starts to boot and It > > > get the message:K > > > 	"OpenVMS Alpha Operating System, Version V7.3" and then it hangs.  Id > > > have updatedF > > > 	the firmware already.  I have read all the installation doc and$ > > > can't seem to get beyond this. > > > 	What next?  > > >  > > E > > The upgrade went smoothly?  Assuming that... try booting SYSBOOT:w > > & > > >>> boot -fl root,flags  boot_dev: > >  > > by example:- > >  > > >>> boot -fl 0,1 dkb0: > > ! > > SYSBOOT> SET WRITESYSPARAMS 0l! > > SYSBOOT> SET STARTUP_P1 "MIN"S > > SYSBOOT> CONTINUEg > > H > > When you get in, comment out your TCP/IP startup and go back and tryM > > a complete boot.  If using Multinet, you have to get to 4.3 , can't speake > > for the other packages.o > >  > > Robo > G > Can you clarify: Are you booting the VMS installation CD (i.e. at the H > start of the installation process) or have you done that and installedH > VMS on a target disk (presumably DKB0:) and are now trying to boot theG > target disk for the 1st time?  In other words, is DKB0: your CD driveu > or your new system disk? > D > If you are booting the CD, then it is probably a CD drive problem.G > Is it a DEC/Compaq CD drive or 3rd party?  (What does >>> show deviceeC > show for it?)  If 3rd-party, is it a drive that is known to work?eA > See the FAQ and search the history of this newsgroup and/or askCF > here for requirements and other peoples experiences with this drive.C > If 3rd-party, is it configured correctly?  (VMS requires it to besH > set to 512-byte block size.  Some drives can't be set this way, others> > have a jumper.  There are probably other requirements, too.) > B > If the CD is known to be a supported model, is it an IDE or SCSIA > drive?  Some (all?) IDE drives require an auxiliary boot floppyeD > containing the drivers to boot from CD for some or all versions of > VMS. > A > If all the above checks out, boot into SYSBOOT as Rob suggested. > and see what happens.h > = > If the problem is booting your target system disk after theU? > install, then also try booting into SYSBOOT as Rob suggested.- >     D       The CD will have a jumper and 95%+ of the time (from the 3 or C       so 500s I am in - 100% of the time) the CD shows up as dka400sE       .  So unless someone removed the jumper and it is showing up as H       0, meaning the system disk won't be showing up if that's the case.  D       I also suspect she is working with a vanilla Alphastation 500.   Rob    ------------------------------  % Date: Fri, 03 Aug 2001 11:02:16 -0500>/ From: Chris Scheers <chris@applied-synergy.com>e? Subject: Re: IPF Console Bootstrap (was: No chance for OpenVMS)t3 Message-ID: <3B6ACB08.B3434752@applied-synergy.com>e   "Mark D. Jilson" wrote:  > A > Could Chris be think about (admittedly flimsy) the case where aaF > development group wants to get an IPF machine but the cost of the CDH > drive in it busts their budget thus they want a CD-less IPF system and@ > have it be able to somehow boot via their existing Alpha based > development systems??   E OK, OK!  I was suffering from dain bramage.  I was posting when I waso too tired.  Sorry!  <grin>  B For some reason, I was reading Fred's post as saying that the diskE management utilities had to be booted from a disk (hard disk, not CD)s? partition.  If no local disks had been properly preped with thet; utilities, you could network boot them from another system.   G My question was how to set up the IPF management partition on the first A system so that you can network boot the others.  (And no, network H booting from an Alpha is not acceptable.  If the intent is to expand theH market, there will be customers who are getting their first and only (so far) VMS system.)   F Booting from the CD is a perfectly reasonable and acceptable solution.   Sorry for all the confusion.       > Larry Kilgallen wrote: > > n > > In article <Zifa7.544$Yx2.10075@news.cpqcorp.net>, "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes:* > > > Jan Vorbrueggen wrote in message ...7 > > >>Chris Scheers <chris@applied-synergy.com> writes:1 > > >>> > > >>> What do you do for the first machine you get in house? > > >>> > > >>Pop the OS distribution CD into its drive and boot that. > > >> > > >@ > > >eP > > > Maybe what he meant was "what if this is the first IPF machine you have inR > > > house".  The answer then is, I would expect PXE booting to be added to Alpha > > > as well. > >7E > > If it is the first IPF machine in house, you still have no reasonnF > > not to put the distribution CD directly into it.  Nobody ever saidD > > that Alpha and IPF versions of VMS would come on the same CDROM.  G -----------------------------------------------------------------------t$ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com a   Fax: 817-237-3074w   ------------------------------  % Date: Wed, 08 Aug 2001 14:32:50 -0400-- From: JF Mezei <jfmezei.spamnot@videotron.ca> * Subject: Re: Lemmings, was Re: Move to Sun, Message-ID: <3B7185C7.9303BA1D@videotron.ca>   Jan Vorbrueggen wrote:M > As long as Compaq was supporting and further developing Alpha, you could beVJ > sure they would also be supporting and further developing Tru64 and VMS,; > because without them Alpha would loose its raison d'etre.e   Agreed.o  P > indeed takes that long) "VMS and Tru64 sales have subsided to just 5% of theirH > former glory [surprise, surprise!], we will therefore now move them to9 > maintenance mode and desupport them in a year's time." I  L I disagree.  Consider that Compaq did not give away EV7 team right away.  AsK long as EV7 team is working for Compaq on the last Alpha, then it is a fairhL bet that Compaq won't go out and put VMS in maintenance mode. If Compaq wereJ to kill EV7 and let the employees go to Intel as the deal stipulates, then' yeah, what you say would likely happen.h  J What I do find quite odd though is that Compaq would supposedly wait untilN 2004 before making VMS on IA64 commercially available even though it might runL on IA64 beforehand. A conspiracy theorist might see this as a way for CompaqL to delay any support commitment on VMS-IA64 as long as possible and keep the+ VMS customers on Alpha as long as possible.X  J If nobody is using VMS on IA64 in early 2004, then Compaq would be able toJ pull the plug on the commercial availability of VMS on IA64. (a bit in theI same way that versions of NT were built on Alpha but not commercialised).   L If VMS is made available on IA64 as soon as it is ready, then not only wouldM Compaq have to commit to supporting that platform , but would customers stilln buy EV7 Alphas ?  I In the end, Compaq probably didn't want to appear to be killing Alpha tooaM quickly, so it decided to kill it only after EV7 is done. But in doing so, it/G probably cannot cannabalise Alpha sales until that time so VMS won't bewH available on IA64 until after EV7. This way, those customers who need toL upgrade will continue to be forced to upgrade on Alpha because IA64 won't beJ available for VMS yet. If VMS were to become availagle on IA64 next month,V then Alpha would no longer sell and the money spend on completing EV7 would be wasted.   ------------------------------  $ Date: Wed, 8 Aug 2001 13:16:04 -0400' From: "Bill Todd" <billtodd@foo.mv.com>N* Subject: Re: Lemmings, was Re: Move to Sun( Message-ID: <9krs50$c25$1@pyrite.mv.net>  5 "Nic Clews" <sendspamhere@127.0.0.1> wrote in messages" news:3B71528C.FDF0283@127.0.0.1... > Bill Todd wrote: > >wI > > Not if Compaq and its apologists stop spewing bullshit about how IA64e haslJ > > comparable (or better) performance potential than Alpha had, how AlphaL > > wasn't profitable, how IA64 will be a better platform for VMS than AlphaI > > would have been (the real question being whether VMS will survive thenE > > intermediate-term loss of Alpha customers in anything more than a F > > permanently-stagnant state), and how 'committed' they are to VMS's futureG > > (without explaining why the even more explicit commitments to Alpha5 weren'ts) > > worth the HTML they were written in).t >e > How important is performance?a  L One area in which it is central to the current discussion is in establishingK the fact that Compaq was willing to lie about it in an attempt to justify aoH decision that in fact had nothing to do with performance.  In fact, thisH reflection on Compaq's (lack of) integrity may be the dominant aspect ofH performance in at least the current context:  the world doesn't *really*L need to get where it's going at the highest possible speed, though (as notedL below) often seems to be willing to pay for the privilege if it's available.   >,A > Your aguments against Itainium as a technology are very strong,o > and probably right.5 >u= > However I've failed to see any real evidence that Alpha was.1 > sold on the basis of its [superior] technology.   J To a large degree Alpha was indeed not *sold* on the basis of its superiorG technology (save for exceptions such as the Alpha/IA64 comparison white-J paper).  But it was often *bought* on the basis of its superior technology6 (that's where the term 'stealth marketing' came from).   >0: > It sold because people wanted VMS, and Alpha was what it
 > runs on.  G IIRC Terry mentioned a while ago that Tru64 sold more higher-end server I systems than VMS did.  Now, Tru64 does offer a few unique advantages overhI other Unixes, but certainly not to the same degree that VMS does, so thisaI tends to call your assertion that Alpha's hardware superiority had littlet impact on sales into question.   >nH > It wasn't sold because people wanted the fastest chip, then found some) > operating system or other to run on it.T  F In at least some cases, it was sold for precisely this reason.  CeleraJ Genomics comes immediately to mind, and of course the recent supercomputer sales wins.E   >a= > If performance really was the issue, then there would be NOB8 > VAX's. We're not all speed freaks, driving the fastest; > production car just gets you into the traffic jam sooner!b  L If you look at the commercial PC market, you'll find that performance (or atJ least perceived performance) shares first place with price as the dominantI user purchase criterion.  For most PC use it's just about as important as K tail fins were on cars in the late '50s, but that doesn't seem to matter to;
 customers.  L There's certainly *some* similar effect as one moves up-market:  size reallyK does seem to matter to people.  And of course in the server space, it oftenVI really *is* useful in maximizing the load a given installation can handlen with acceptable performance.   >nG > Similarly, no-one would want the DS10s or the other 'low end' Alphas, + > we'd all be craving the GS and ES series.e  K It would be interesting to see a use breakdown for low-end Alphas.  ClearlyOH some are used simply as cost-effective compatible adjuncts to higher-endI machines (hence get 'pulled along' by high-end sales that may be based onTE performance), and some others may be used in workstation applicationsA! requiring a 64-bit address space.    ...l  : > In 2005 or thereabouts, people will have a choice, Alpha: > or Itanium. The pen pusher isn't going to _want_ to knowG > the technical differences - they don't care. It'll be bottom line ando > TCO.  J Unfortunately, they won't have an *equal* choice, because Alpha technologyK will have hit its Compaq-declared dead-end at that point in time.  So those:F Alpha platform users who haven't already bailed out by then will startI feeling terminal pressure to do so - and unless VMS looks a hell of a lot G more viable by that time than it does today (and exactly what basis hasaJ Compaq given anyone to expect that to happen?) will likely not look kindly) on Compaq for having forced this on them.e  H In the meantime, of course, there's a major DISincentive to purchase anyJ Alpha system, since the need for *some* kind of migration a few years down the road is already guaranteed.o  I Oh, by the way, if TCO dominated purchase decisions, VMS (on Alpha) wouldo% already dominate the entire market...Y   >MH > > The major issues here are Compaq's competence and credibility, which manyH > > feel are both in the negative range.  But since the reasons for this includeeG > > questions of the technical merits of Alpha vs. IA64 (since Compaq'seJ > > statements *made* these issues), discussing them is entirely relevant. >mH > But the statements also stated (from the press release HTML, quoted of > the Intel CEO: >gG > " Our agreement will bring higher levels of performance, availabilityu > andeI >                             scalability to systems based on the Itanium: > processor family." >DI > There's no such statement that the Itanium releases of VMS are going tonH > be faster. It is saying that the Itanium will get faster, but it would: > anyway, with or without the help of the Alpha engineers.  L The Compaq statements I referred to (offered as supporting arguments for theD Alphacide, but not in the announcement press releases) were the onesG claiming that Compaq's own Alpha engineers had warned Compaq that Alpha B would have problems keeping up with IA64 performance improvements.   ...u  E > As to competance, I believe Compaq are doing a much better job thane > Digital every did.  L I assume you mean 'ever did' above, and that's poppycock, unless you confineE 'ever' to the Palmer years (which are a ridiculously easy standard tom exceed).  3  It does not mean I agree with all their decisions,o. > but they cannot be all things to all people.  K Too bad the things they seem to want to be are the things they're the worstu at.i  I Customers may not have a right to expect Compaq to be responsive to theiroE wishes, but they have a right to call Compaq incompetent if it isn't:B% that's what competition is all about.g   ...   G > One further point if I may, with all those Intel ads with their funnytE > costumed people dancing around to an annoying jangling ditty duringrH > primetime TV, in a few short years time, those same adverts will in my- > mind promoting the [a] platform of OpenVMS.e >aG > I could never see a future, even if Alpha continued thru EV8 and EV9,pH > similar messages from our mutual friends extolling the wonders of OOOP > and predication, could you?o  J Funny, I read somewhere recently that a lot of industry professionals findK those ads insulting to their intelligence.  So I'm not sure that the futurehL you envision (even if it should come to pass) is a desirable one for the VMS space.   - bill   >o > --* > Regards, Nic Clews CSC Computer Sciences > nclews at csc dot come   ------------------------------  + Date: Wed, 08 Aug 2001 12:24:42 -0500 (CDT)u From: sms@antinode.org Subject: Re: LPs on the Webh) Message-ID: <01080812244207@antinode.org>t  1 From: keithparris_nospam@yahoo.com (Keith Parris)bw > John Santos <john.santos@post.harvard.edu> wrote in message news:<MPG.15c951f3234e9cb98968d@news.bellatlantic.net>... K > > Hmmm.  If you are eligible and can join CSA (~$100-$150/year), then youiI > > can get the VMS and/or Tru64 CD distributions (LP+DOCs 4 times a year E > > plus current O/S kit + any new O/S releases) for about $500/year.c > @ > CSA membership is $600 in the US.  The Digital ASAP program it# > repalced was $200 per year, IIRC.K  E    The corresponding IBM program, like the corresponding Sun Program, D costs $0/year.  I recently received my CD-ROM kit for AIX 5L version 5.1, also at a cost of $0.  A    You tell me: Who wants to attract application developers more?d  5    Included in the AIX release notes was this tidbit:   C       The Expansion Pack includes the Netscape web browser product,nH       Communicator, Version 4.7.6.1.  The ~i~ in the title "Netscape (R)G       Communicator 4.76i" on the About page indicates that the code was@       compiled by IBM.  G When I saw this, I tried (wistfully) to imagine a comparable notice forY= a comparable version of Netscape Communicator for VMS, but mye# imagination was not up to the task.8  H    (_I_ think it's worth having an AIX system around just for the little' SMIT dude, but I'm easily entertained.)7  H    On an unrelated topic, I recently noticed a link on a Sun Web page toF "http://soldc.sun.com/ntmigration".  Unlike Digital/Compaq, Sun's ideaF of NT migration involves migrating _from_ NT (to Solaris, of course).  Whoa.  There's a novel concept.   H ------------------------------------------------------------------------  C    Steven M. Schweda               (+1) 651-699-9818  (voice, home) C    382 South Warwick Street        (+1) 763-781-0308  (voice, work) G    Saint Paul  MN  55105-2547      (+1) 763-781-0309  (facsimile, work) 9    sms@antinode.org                sms@provis.com  (work)P   ------------------------------   Date: 8 Aug 2001 17:47:51 -0500 9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)a Subject: Re: LPs on the Webp3 Message-ID: <kFxicZ7V0OB8@eisner.encompasserve.org>   B In article <01080812244207@antinode.org>, sms@antinode.org writes:3 > From: keithparris_nospam@yahoo.com (Keith Parris)Dx >> John Santos <john.santos@post.harvard.edu> wrote in message news:<MPG.15c951f3234e9cb98968d@news.bellatlantic.net>...L >> > Hmmm.  If you are eligible and can join CSA (~$100-$150/year), then youJ >> > can get the VMS and/or Tru64 CD distributions (LP+DOCs 4 times a yearF >> > plus current O/S kit + any new O/S releases) for about $500/year. >> /A >> CSA membership is $600 in the US.  The Digital ASAP program itf$ >> repalced was $200 per year, IIRC. > G >    The corresponding IBM program, like the corresponding Sun Program,pF > costs $0/year.  I recently received my CD-ROM kit for AIX 5L version > 5.1, also at a cost of $0. > C >    You tell me: Who wants to attract application developers more?l  H The Compaq/DEC program always takes a long time to respond to inquiries.D The IBM program responds quickly.  After 4 years of letters back andD forth, I gave up on the Sun program.  (All this is for non-technical inquiries.)e   ------------------------------  % Date: Tue, 07 Aug 2001 21:10:06 -0500m1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e+ Subject: Re: LPs on the Web (Was: Re: DCPS)e' Message-ID: <3B709F7E.722D453D@fsi.net>e   Keith Parris wrote:r > G > One way to get the CDs inexpensively is to become a Compaq Accredited C > Professional (see http://www.compaq.com/certification/).  The VMSoE > certification "track" at this point consists of only a single exam,hF > and once you pass that you can apply for certification.  Once you'reC > certified, you can apply for a free(!) 1-year subscription to theh% > CONOLD/CONDIST/OS distribution CDs.  > G > I'm told the tests cost $100 -- but Compaq was picking up the tab for-G > the tests I took as an attendee at European DECUS/ITUG in Lisbon, and @ > I was told they plan to do the same for attendees at CETS2001.  G That's just *TOO* excellent! I *GOTTA* put that up in the next issue ofa my Hobbyist page(s).  * One more baby step toward affordability...   -- k David J. Dachteraf dba DJE Systemsh http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/h   ------------------------------  $ Date: Tue, 7 Aug 2001 19:41:29 -0400+ From: "John Saunders" <jws@ma.ultranet.com> # Subject: Re: Microsoft and Code redw+ Message-ID: <9kpuc6$k69$1@bob.news.rcn.net>g  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3B705751.B9BD918D@videotron.ca...: > Some most interesting reading^about how the virus works: >r/ > http://www.incidents.org/react/code_redII.phpa >e > The best one is:@ > First, the trojan program adds the value SFCDisable=0xFFFFFF9D >                            tot: HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogin.J >                            This registry setting completely disables the > Windows File8 >                            Protection (WFP) mechanism. >uI > So, on windows, adding just some registry entry disables file security.t GreatmL > stuff. Who is the complete do-do at Microsoft who implemented that feature ?o >sF Windows File Protection is not File Security. That registry entry does' nothing to affect file system security.g  J Windows File Protection is a mechanism which watches certain system files,B and if they're modified, replaces them with the original versions. --
 John Saundersd jws@ma.ultranet.comt   ------------------------------  # Date: Wed, 08 Aug 2001 12:59:53 GMT ? From: "Mark \(un-MASK\) Forsyth" <forsyMhm@optusAhome.coSm.aKu>t# Subject: Re: Microsoft and Code redr" Message-ID: <2scrk9.544.ln@really>  6 "John Saunders" <jws@ma.ultranet.com> wrote in message% news:9kr4m1$5el$1@bob.news.rcn.net... J > "Mark (un-MASK) Forsyth" <forsyMhm@optusAhome.coSm.aKu> wrote in message > news:ej1rk9.no3.ln@really... > >l  	 [deletia]o  ? > > Yes. You can also get well and truly stuck into 'em about an
 vulnerability.J > > that allows complete access that they were told about in June 1999 and yeti4 > > did nothing about until about a month or so ago. > J > Mark, do you mean that Microsoft were told about the Index Server bufferB > overrun in June 1999? If so, do you have  documentation of that?  E The vulnerability is the same. ie. Buffer overrun when processing IISwF filtered extensions. The actual exploit was different to the "proof ofA concept' that eEye published. Still should've woken MS up though.d  K Have a look at http://www.eeye.com/html/Research/Advisories/AD19990608.htmlr andl> http://www.eeye.com/html/Research/Advisories/AD19990608-3.html   Ooroo 	 Mark F...          > -- > John Saunders  > jws@ma.ultranet.coml >h >  >s   ------------------------------  % Date: Wed, 08 Aug 2001 11:29:24 -0400r2 From: rdeininger@mindspring.com (Robert Deininger)# Subject: Re: Microsoft and Code rediL Message-ID: <rdeininger-0808011129250001@user-2ive73a.dialup.mindspring.com>  ; In article <9kr4m1$5el$1@bob.news.rcn.net>, "John Saunders"s <jws@ma.ultranet.com> wrote:    J > Mark, do you mean that Microsoft were told about the Index Server bufferB > overrun in June 1999? If so, do you have  documentation of that?  B Is that an Armani-clad dorsal fin I see circling around Mr. Gates?   (I hope so.)   --   Robert Deininger rdeininger@mindspring.comm   ------------------------------  $ Date: Wed, 8 Aug 2001 12:06:40 -06004 From: "Michael D. Ober" <mdo.@.wakeassoc.com.nospam>3 Subject: Re: Microsoft and Code red (Cisco as well)s1 Message-ID: <Ucfc7.175$2I.139484@news.uswest.net>a  K I applied the patch according to the MS Security email I received and still F had problems; not with my MS Servers, but with my Cisco 675 DSL modem.K There is a similar bug in the Cisco DSL modems.  I have yet to see anythingeL from Cisco on fixing their bug.  USWest/Qwest finally found and provided the fix.   Here's the Cisco Bug:c  K When the cisco CBOS receives a packet tagged for a port it is configured to?H watch, it attempts to parse this packet, even when the service that usesK this port has been disabled.  This means that simply disabling the CBOS websL configuration service won't prevent the Code Red worm from causing the CiscoG modems to stop routing.  The solution is to change the HTTP port on the K modem to a random number above 1024.  Like I said, Qwest found and provided  this information, not Cisco.  6 The problem of unchecked buffers is far wider than MS. --
 Mike Ober.  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message% news:3B6ECE73.C5851A6@videotron.ca...aK > As you may be aware, there is a new more virulent worm making the circles F > which enables the ISS server as a glorified TELNET server goving you	 access to> > the NT command prompt. >@I > For the past 4-5 days, my ISP has been swamped by the virus which makesdL > connection attempts to every possible IP. As a result, for almost every IPD > request, the routers generate an ARP request to try to learn which ethernetE > interface on the cable modem network has that IP since for the vastr majorityF > of cases, the IP address is unkown to the ARP table.  The lights are flashingK > constantly on the cable modem. I don't run any MS operating systems, so I  amJ > not affraid, however, it is anoying because of the significant amount ofG > traffic on the lan this adds (I am trying to isolate a problem with a  hub).s > I > Could this be the achile's heel that starts to bring down Microsoft, ore willG > corporations ignore this major flaw and continue to blindly bet theiri business > on Microsoft stuff ? >tD > What will it take for corporations to wake up from their MicrosoftE > trans/brainwashing and realise that they shouldn't be betting their( business > on MS software ?   ------------------------------  + Date: Wed, 08 Aug 2001 13:45:51 -0500 (CDT)' From: sms@antinode.org3 Subject: Re: Microsoft and Code red (Cisco as well)h) Message-ID: <01080813455122@antinode.org>g  4 From: "Michael D. Ober" <mdo.@.wakeassoc.com.nospam>  M > I applied the patch according to the MS Security email I received and stillgH > had problems; not with my MS Servers, but with my Cisco 675 DSL modem.M > There is a similar bug in the Cisco DSL modems.  I have yet to see anythingaN > from Cisco on fixing their bug.  USWest/Qwest finally found and provided the > fix.  C    Cisco does not deal with peons like us on CPE (Customer PremisesoE Equipment).  They deal with higher level entities, like Qwest.  Qwest H supplies instructions for a work-around for the problem, not a fix.  TheG fix is in a later version (2.4.x) of the CBOS, which I got (months ago) ? from my ISP, because until very recently, Qwest was too lame too0 distribute anything newer than 2.2.x themselves.  5 > [...]The solution is to change the HTTP port on theoD > modem to a random number above 1024.  Like I said, Qwest found and' > provided this information, not Cisco.o  G   "Solution", right.  Why a port above 1024?  No good reason.  Anythingn  other than 80 evades the attack.  8 > The problem of unchecked buffers is far wider than MS.  H    No argument there, but if you think Qwest is so good, try calling DSLF support (800-247-7285) and checking the current wait time.  (I've beenA on hold for almost a half-hour so far (on an unrelated problem).)s  H ------------------------------------------------------------------------  C    Steven M. Schweda               (+1) 651-699-9818  (voice, home)iC    382 South Warwick Street        (+1) 763-781-0308  (voice, work) G    Saint Paul  MN  55105-2547      (+1) 763-781-0309  (facsimile, work)s9    sms@antinode.org                sms@provis.com  (work)i   ------------------------------  $ Date: Wed, 8 Aug 2001 15:17:16 -06004 From: "Michael D. Ober" <mdo.@.wakeassoc.com.nospam>3 Subject: Re: Microsoft and Code red (Cisco as well) 2 Message-ID: <z%hc7.1115$1u.342298@news.uswest.net>  G Actually, I just got an email from Windows 2000 Magazine Security folkspA reporting that Cisco 600 series modems with CBOS v2.4.2 are stilloI experiencing the problem with the port.  And yes, I sat for 90 minutes oneJ hold with Qwest, but the fact that Cisco hasn't been assisting modem usersL via their web-site reflects poorly on them as well.  As for the "solution" -I it stinks.  Unfortunately, a permanent solution can only come from Cisco.TL Picking a port above 1024 avoid the possibility of another "well-known" port attack.4 --
 Mike Ober.  G <sms@antinode.org> wrote in message news:01080813455122@antinode.org... 6 > From: "Michael D. Ober" <mdo.@.wakeassoc.com.nospam> > I > > I applied the patch according to the MS Security email I received and  still J > > had problems; not with my MS Servers, but with my Cisco 675 DSL modem.F > > There is a similar bug in the Cisco DSL modems.  I have yet to see anythingL > > from Cisco on fixing their bug.  USWest/Qwest finally found and provided thel > > fix. >dE >    Cisco does not deal with peons like us on CPE (Customer PremisestG > Equipment).  They deal with higher level entities, like Qwest.  QwestpJ > supplies instructions for a work-around for the problem, not a fix.  TheI > fix is in a later version (2.4.x) of the CBOS, which I got (months ago)eA > from my ISP, because until very recently, Qwest was too lame toi2 > distribute anything newer than 2.2.x themselves. >d7 > > [...]The solution is to change the HTTP port on the,F > > modem to a random number above 1024.  Like I said, Qwest found and) > > provided this information, not Cisco.e > I >   "Solution", right.  Why a port above 1024?  No good reason.  Anything " > other than 80 evades the attack. > : > > The problem of unchecked buffers is far wider than MS. >mJ >    No argument there, but if you think Qwest is so good, try calling DSLH > support (800-247-7285) and checking the current wait time.  (I've beenC > on hold for almost a half-hour so far (on an unrelated problem).)  >eJ > ------------------------------------------------------------------------ >lE >    Steven M. Schweda               (+1) 651-699-9818  (voice, home)'E >    382 South Warwick Street        (+1) 763-781-0308  (voice, work)eI >    Saint Paul  MN  55105-2547      (+1) 763-781-0309  (facsimile, work)w; >    sms@antinode.org                sms@provis.com  (work)o   ------------------------------  $ Date: Wed, 8 Aug 2001 16:24:20 -0500* From: WILLIAM WEBB <WWEBB1@email.usps.gov>2 Subject: RE: Modems, Keyboard & Mouse Ports on VLC- Message-ID: <0033000031715814000002L042*@MHS>o  7 =0AYou won't get full modem control with TTA3, however.e   WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNETi* > Sent: Wednesday, August 08, 2001 1:42 PMF > To: Webb, William W - Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET4 > Subject: RE: Modems, Keyboard & Mouse Ports on VLC >d >  > New VLC User wrote:g= > > Unless I'm mistaken (and please correct me if I'm wrong),  > the keyboard; > > and mouse ports on my VAXstation 4000 VLC are TTA0: andh > TTA1:.  Can I 4 > > use either of these ports for an external modem? >o5 > Seems doubtful.  Mine are being used by DECwindows.  >cE > > the pinouts?  NOTE: I'm already using the DB25 port (TTA2:) for ao' > > serial printer.  Thanks in advance.m > > > You're in luck because there is also an MMJ port next to the > DB25 port.< > VMS sees this device as TTA3.  The pinout according to the > users's manual > page B-1 is as follows:  >  > Pin     Meaninge > _______________e
 > 1       DTR  > 2       Transmit > 3       Ground > 4       Ground > 5       Receivei
 > 6       DSRo >=   ------------------------------  # Date: Wed, 08 Aug 2001 05:55:49 GMTy$ From: info@adroso.com (New VLC User). Subject: Modems, Keyboard & Mouse Ports on VLC: Message-ID: <3b70d2e0.286773142@news.jamison1.pa.home.com>  F Unless I'm mistaken (and please correct me if I'm wrong), the keyboardE and mouse ports on my VAXstation 4000 VLC are TTA0: and TTA1:.  Can ICE use either of these ports for an external modem?  And if so, what are-A the pinouts?  NOTE: I'm already using the DB25 port (TTA2:) for a@# serial printer.  Thanks in advance.    ------------------------------  % Date: Wed, 08 Aug 2001 20:46:04 +0200m= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>v Subject: Re: Move to Sun) Message-ID: <3B7188EC.EF3B1B7E@gtech.com>l   andrew harrison wrote:I > > "Thus far, Sun is the only vendor that does not plan to include Intel K > > chip support in its product line. Instead, Sun is going the proprietaryc@ > > route with its SPARC and 64-bit UltraSPARC microprocessors."  8 > You post also totally ignores that fact that there are8 > other vendors who have no intention of including IA-64 > in their product lines.t > < > The IBM S390 division, the AS400 and the RS/6000 divisions< > have no intention of including any IA-64 products in their > product lines.   ????  > It is already some time since IBM renamed their hardware boxes: to foobarSeries (specifically I think a RS/6000 are called
 a pSeries.  B But your statement does not make any sense ! Compaq Alpha divisionB are not including IA-64. VMS (and Tru64) will support IA-64. It is@ the same for IBM. Their pSeries will not use IA-64. But AIX willF support IA-64 (I think the beta version of AIX 5 for IA-64 are already out there).o   Arne   ------------------------------  % Date: Wed, 08 Aug 2001 13:37:09 +0100t0 From: andrew harrison <andrew.nospam@uk.sun.com> Subject: Re: Move to Sun* Message-ID: <3B713275.59D65FBE@uk.sun.com>   Nic Clews wrote: >  > Jack Peacock wrote:t > >tI > > The customer, one of our largest (very large european multinational),kH > > has told us they want to keep our applications but do not want it onD > > VMS.  They have an IT policy, in place for several years now, toL > > eliminate all VMS based machines and applications.  Replacements are SunI > > for critical servers and NT for web servers (non-critical informationWL > > kiosk type apps).  They are willing to pay substantial sums to implement > > their policy.6 > I > Obviously your client has not read the July Gartner report which placesoH > Sun in a weak position with respect to Compaq recent announcement withD > server consolidation to Itanium. Competitional analysis says this: > G > "Thus far, Sun is the only vendor that does not plan to include IntelgI > chip support in its product line. Instead, Sun is going the proprietary > > route with its SPARC and 64-bit UltraSPARC microprocessors." > + > The phrase "out on a limb" comes to mind.e >   D Interesting definition of proprietary, SPARC is actually one of the B most open processor architectures there is. AMD and Transmeta haveE had to very carefully clone the Intel x86 processor, on the otherhand>D the information required to develop and build SPARC CPU's is in the  public domain.  C This is why for example Fujitsu are able to develop and manufactureaB their own SPARC CPU's, and then build them into their own servers  that run Solaris.S  9 If your definition is non-proprietary Intel, proprietary  6 anthing that isn't Intel then you should have said so.  7 You post also totally ignores that fact that there are p7 other vendors who have no intention of including IA-64 t in their product lines.e  : The IBM S390 division, the AS400 and the RS/6000 divisions: have no intention of including any IA-64 products in their product lines.  B And those vendors that have decided to drop their own architectureB in favour of IA-64 have done it with a great deal more thought and5 planning that Compaq have. HP being the best example.   B So if you think that a hastily conceived decision by Compaq which > has apparently had no technical due dilligence and which will > not deliver actual products until 2005 puts Compaq in a better, possition than Sun you are probably deluded.   Regardss Andrew Harrisonn Enterprise IT Architectu   ------------------------------   Date: 8 Aug 2001 14:26:25 -0700,& From: jordan@ccs4vms.com (Rich Jordan)2 Subject: Mozilla M0.9.3, August 3rd release; Java?= Message-ID: <cc5619f2.0108081326.7a812469@posting.google.com>i  ? Noted that M0.9.3 was released on 8/3, apparently still with noEE working Java accompaniment.  Unfortunately that still severely limitse@ its usability here (very unfortunately, java is a slow and buggyD beast, and I wish we didn't need it).  Is there any release scheduleD for the Java Version 1.3.0_01 with 'OJI' that is supposed to be what Mozilla needs to work?   Rich Jordanl   ------------------------------   Date: 8 Aug 2001 05:34:09 -0700- From: vms@trymech.co.uk (Paul)# Subject: NFS network protocol error = Message-ID: <6f04997e.0108080434.1eb18a2b@posting.google.com>o  K I have an NFS export from a HP server successfully mounted on an VMS client<Q and I am able to create and edit files on it successfully - the problem is this :.  K Using the BACKUP utility to restore files from the OpenVMS box to any HP UXwL system, either from tape or disk and regardless of whether it's for multipleH or single files, results in the following error and no files are copied:  ( VMSSERVER> backup a.a ONE:[000000]*.*/lo< %BACKUP-E-OPENOUT, error opening ONE:[000000]A.A;1 as output" -RMS-E-CRE, ACP file create failed* -SYSTEM-F-PROTOCOL, network protocol error   The configuration    OpenVMS NFS Client (VMSSERVER):d  
 HP UX mount:-g   $ TCPIP mount ONE:[000000] - /HOST="hostname"-f /PATH="/tmp" -
 /OWNER=[1,4]- 
 /SUPERUSER=0-m /PROT=(O:R)- /NOADF- 5 /ACP_PARAMS=(PRIO=1,WORKSET=8000,MAX_WORKSET=12000) -h hostname_tmp   ------------------------------  # Date: Wed, 08 Aug 2001 15:16:56 GMTt1 From: "Kari Keronen" <kari.keronen@radiolinja.fi>e' Subject: Re: NFS network protocol errorm2 Message-ID: <01c1201d$1e58efd0$9b0ba8c0@rlhkikker>  I Depending of file attributes of file A.A BACKUP may have problems to copy1? the file to NFS mounted disk on UNIX box. Look for restrictionsh   $ TCPIP HELP MOUNT/CONVERT  J The /NOADF qualifier that you used makes of course it impossible to create3 nothing else than STREAM_LF type files to the disk.e   -Kari-  ) Paul <vms@trymech.co.uk> wrote in articleo4 <6f04997e.0108080434.1eb18a2b@posting.google.com>...F > I have an NFS export from a HP server successfully mounted on an VMS clientI > and I am able to create and edit files on it successfully - the problemc	 is this :e > J > Using the BACKUP utility to restore files from the OpenVMS box to any HP UXE > system, either from tape or disk and regardless of whether it's forI multipleJ > or single files, results in the following error and no files are copied: > * > VMSSERVER> backup a.a ONE:[000000]*.*/lo> > %BACKUP-E-OPENOUT, error opening ONE:[000000]A.A;1 as output$ > -RMS-E-CRE, ACP file create failed, > -SYSTEM-F-PROTOCOL, network protocol error >  > The configuratione > ! > OpenVMS NFS Client (VMSSERVER):e >  > HP UX mount:-9 >  > $ TCPIP mount ONE:[000000] - > /HOST="hostname"-o > /PATH="/tmp" - > /OWNER=[1,4]-a > /SUPERUSER=0-  > /PROT=(O:R)-	 > /NOADF-w7 > /ACP_PARAMS=(PRIO=1,WORKSET=8000,MAX_WORKSET=12000) -- > hostname_tmp >    ------------------------------  % Date: Wed, 08 Aug 2001 14:43:43 -0400n- From: JF Mezei <jfmezei.spamnot@videotron.ca>s% Subject: Re: OpenVMS (Itanium) wishese, Message-ID: <3B718854.A65249AC@videotron.ca>  * fabio_compaq@ep-bc.petrobras.com.br wrote:; > b) I will insist in the LAN Console for Itanium servers. h  N I would much rather have a very simple yet bulletproof serial console. You canK always hook it up to a small terminal server so you can access your console  though the lan.n  M I would not want to see the support of multiple console paradigms to make them console less usable.  L Consider that the console on my vaxstation 3100 cannot display multinationalM characters when sent to the video monitor during the boot sequence, while thesA simpler console of my all mighty microvax II has no problems withh& multinational characters sent to OPA0.  J While the display of multinational characters is not that important in theK grand scheme of things, it does make one wornder what else was omitted fromeL the fancier console medium compared to the simpler more complete serial one.   ------------------------------  % Date: Wed, 08 Aug 2001 11:26:10 -0400e2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: OpenVMS and IA64 L Message-ID: <rdeininger-0808011126110001@user-2ive73a.dialup.mindspring.com>  B In article <tn2hkh3pfhs944@news.supernews.com>, "www.islandco.com" <dbturner@islandco.com> wrote:    G > Let's keep backing up to 30 year old technology  floppies and tapes !H  G Your tape drives may be 30 years old, but ours are quite a bit newer...f  H Seriously, modern tape drives are pretty good for backups.  They haven'tI improved quite as fast as disks, but every year or two there are improvedo models available.t  D > What is the average age of the VMS development engineers, anyway ?  E That's easy to figure out.  Just add up their ages, and divide by 11.e   :-)S   -- r Robert Deininger rdeininger@mindspring.come   ------------------------------  % Date: Thu, 09 Aug 2001 00:57:03 -0400e' From: Jim Becker <jbecker@ui.urban.org>o; Subject: Premier Issue of Encompass Membership E-Newsletters+ Message-ID: <3B72181F.7376044@ui.urban.org>n  F The following was mailed to Encompass members for whom we have current e-mail addresses.     E Welcome to the premier edition of Encompass Points! Encompass Points hB is a bi-monthly, e-mail newsletter for Encompass, an independent, : volunteer-driven organization providing Compaq users with F opportunities for education, peer networking, and vendor advocacy. If F you would like to be removed from this list, please send an e-mail to  information@encompassus.org    ISSUE CONTENTS:  ** PRESIDENT'S MESSAGE r* ** CALL FOR BOARD OF DIRECTOR NOMINATIONS - ** CETS PRE-CONFERENCE PROGRAM AND BOOTCAMPS  6 ** ENCOMPASS, COMPAQ LAUNCH LOCAL PARTNERSHIP PROGRAM " ** TRU64 USERS, COMPAQ PARTNER UP 0 ** LUGS: LOCAL TOUCHSTONES IN GLOBAL PROFESSION B ** COMPAQ & INTEL: CHANGING THE LANDSCAPE OF ENTERPRISE COMPUTING ! ** SUPPORT QUESTIONS FOR COMPAQ?   ** COMPAQ SERVERS  ** 2001 CALENDAR C       PRESIDENT'S MESSAGE E Welcome to the first edition of Encompass Points, the Encompass U.S. 0E electronic newsletter. We plan on publishing this newsletter several c= times throughout the year to keep you informed of the plans, yE activities, and general information about your association and about u Compaq.   E The first half of this year has certainly lived up to that prophetic IE saying, "may you live in interesting times." We have experienced the wE great bubble burst of the "dot-coms." We have seen our own high-tech tG industry take steep hits and have all come to know at least one or two iD associates (if not being one ourselves) that are no longer at their G old positions. Closer to home, many within our own society are reeling 2C from how to leverage, recover from, or otherwise simply fathom the tG significant announcement from Compaq that will see the transition from 2E the Alpha technology to Intel's Itanium line. With all these changes hG and concerns affecting so many of us, it is not trite to say, "You are  C not alone." Encompass understands, and as your society, is working  A hard to pull together sources of information and forums for your s  discussions about these issues.   A Foremost among these is the upcoming Compaq Enterprise Technical fE Symposium (CETS) 2001 being held in Anaheim, September 8 through 14. dA While many other high-tech firms have canceled or deferred their hE technical conferences, Compaq, partnering with Encompass and others, -A continues to offer CETS. And never has this conference been more hE timely. Encompass is working closely with Compaq to provide a number iE of sessions and opportunities for you to really understand and probe 5E Compaq's directions with Alpha and the implications for you and your rE business. More than discussing the future, CETS is the place to come -C to understand the "Here and Now" of the technologies, products and mC services you use today as well as tomorrow. Please see the article o$ below on CETS for more information.       F Speaking of CETS, I also wanted to remind you that we will be holding @ the first annual Encompass member meeting at the conference. As F members of the association, this is your meeting and your opportunity B to meet other members of Board and me. Further details about this & meeting will be e-mailed to you soon.   F I've already exceeded my line budget and there is still more to tell, B but I'd better stop here. I look forward to seeing many of you at  CETS. Have a safe journey. e  
 Joe Pollizzi o President, Encompass, US k      ' CALL FOR BOARD OF DIRECTOR NOMINATIONS tA Encompass is accepting self-nominations for four Encompass board  E member positions for terms spanning 2002-2004. Interested candidates  E should e-mail contact information along with a statement of interest  - to information@encompassus.org by August 31. h  F As part of our transition from our DECUS heritage to Encompass, three F of the candidates will be elected to three-year terms, and the fourth A to a one-year term. Newly elected board members will take office sF January 2002. Thereafter, Encompass will be electing three candidates  each year. e  < Members will vote on the new slate of candidates this fall.       * CETS PRE-CONFERENCE PROGRAM AND BOOTCAMPS F Register by August 10 to save $100 on one-day Pre-conference Seminars + or $200 on the two-day TechWorks Bootcamp. l  ? The Pre-Conference program continues as strong as ever and now  C includes the TechWorks Bootcamps. These are special pre-conference T< seminars specifically designed for the experienced computer E professional who needs to learn a new technology. Even the bootcamps  C listed as "introductory" assume some level of technological savvy, yG such as the bootcamp for Windows NT or UNIX systems administrators who kF would like to learn OpenVMS systems management. Attendees are assumed F to already know the "what" and "why" of managing a networked computer E system from experience, so bootcamp trainers can jump right into the -@ "how" of managing an OpenVMS system. At CETS2001, six excellent D bootcamp topics are being presented by speaker teams of experienced 
 trainers.   D Who should sign up for a TechWorks Bootcamp? Computer professionals D who are looking to add a new technology to their site but who don't D want to sit through "computer basics" before getting to the core of D the new technology. Sign up for a seminar that gives you credit for 4 your experience - sign up for a TechWorks Bootcamp!   E The registration information for the Bootcamps, as well as all other  A Pre-Conference Seminars, are found on the Seminar tab during the  G registration process (note: if you have already registered you can use  E the "Update Registration" feature on www.CETS2001.com to add these). TF We believe these intense Bootcamps will be the fast track to learning ? a "new to you" platform. For more information please download: :4 http://www.cets2001.com/privatedocs/Seminars.pdf or 1 http://www.cets2001.com/privatedocs/Seminars.txt s      3 ENCOMPASS, COMPAQ LAUNCH LOCAL PARTNERSHIP PROGRAM  G A new Encompass and Compaq initiative to deliver technical information  D at the local level drew 109 members and Compaq customers July 31 in E Washington, DC for the premier event, co-sponsored by the Enterprise e Server Local User Group. A  G Local Partnership Program events are planned to strengthen avenues for bE knowledge exchange and advocacy through face-to-face educational and t? networking opportunities in local communities throughout North l	 America. 1  E Come see the latest Compaq technologies in action and hear about the TE unfolding future of Compaq at the next event slated for August 16 in eE Blue Bell, Penn. This event will enable you to personally visit with e@ Compaq executives, systems engineers as well as Encompass board D members, volunteers and other IT professionals. To view the agenda, 0 click to http://www.encompassus.org/events/LPP/   ? Watch for more Local Partnership Programs this Fall in Boston,    Cupertino, Houston and Toronto.   E To volunteer for the LPP, contact the program manager, Jenny Butler, a at Jbutler@utmem.edu.        TRU64 USERS, COMPAQ PARTNER UP  G The TRU64 UNIX Technical Advisory Group (TAG) connects Encompass Tru64  C customers with Compaq in order primarily to provide customers with 0G technical information on Tru64 UNIX and Compaq with customer feedback. jF TAG meetings include presentations by Compaq Engineers followed by an F opportunity for customer feedback. The first three meetings presented A previews of Operating System features including Security, Aurema a@ ARMtech, and Cluster Interconnects. A summary of the latest TAG $ meeting (June 2001) is available at 0 http://www.encompassus.org/whatsnew/TAGMtg.html 1 Information on the TAG and Tru64 is available at u: http://www.iscnet.upenn.edu/~magill/encompass/index.html.   G The Tru64 UNIX TAG is expanding its efforts beyond meetings to provide iE technical information to the Encompass Tru64 community. TAG plans to dE include IA64/Alpha integration status information from Intel as well e> as tracking the IA64 port of Tru64. In addition, look for TAG > sponsored sessions at CETS2001 (http://www.cets2001.com). For < information on becoming part of the TAG, contact Anne Foley  (anne.foley@compaq.com). r      - LUGS: LOCAL TOUCHSTONES IN GLOBAL PROFESSION IE Encompass' geographically based local user groups (LUGs) connect you  E with Compaq users and Encompass members on a local and more personal 0F level. Originally established to expand and improve Encompass' member D services, LUGS are now a beneficial source of technical information ? and provide activities throughout the United States to connect fE members with other IT professionals near home. To find a LUG in your y& area, or to start a new LUG, click to ! http://www.encompassus.org/lugs/ n  A LUG Chairpersons should send submissions to LUG Plan Manager Pam    Campbell at pcampb456@iwon.com.       ? COMPAQ & INTEL: CHANGING THE LANDSCAPE OF ENTERPRISE COMPUTING n? By adopting the Itanium architecture for its 64-bit enterprise  ? servers, Compaq will enhance customers' current investments by bF providing advanced systems design and capabilities - from web servers ; to supercomputers - at the lowest possible price. For more c; information on this timely announcement, bookmark this URL a* http://www.compaq.com/hps/ipf-enterprise/       + COMPAQ ON CALL TO ANSWER SUPPORT QUESTIONS gB Visit "Ask Compaq" at http://askq.compaq.com/ if you need a quick  answer to a support question.        COMPAQ SERVERS mF For information on Compaq's array of servers - Single Purpose Systems ( to Supercomputers, be sure to check out > http://www.compaq.com/products/servers/ for the latest deals,  upgrades, and enhancements.   5 Send e-newsletter submissions to andrea_may@sba.com. o      	 CALENDAR   August through October 2001    AUGUST 14-15    ) Compaq National Storage Days             i1 Colorado Springs, CO                             a7 http://storage.inet.cpqcorp.net/events/nsd/tstords.asp t& Questions? nastorageevents@compaq.com    AUGUST 14       9 Compaq Technology Update -- Southeast                    n8 Atlanta, GA                                             ' http://www.compaq-signup.com/southeast  " Questions? Mickey.Pugh@Compaq.com   
 AUGUST 16 0 Local Partnership Program                       0 Hosted by Encompass & Compaq Computer Corp       Blue Bell, PA 8 http://www.encompassus.org/events/LPP/philadelphia.html ' Questions: Information@EncompassUS.org o(                                          SEPTEMBER 8-9   9 Compaq Enterprise Technical Symposium 2001 Pre-Conference. Seminars        Anaheim, California              http://www.cets2001.com $ Questions? information@cets2001.com                           SEPTEMBER 9-14  0 Compaq Enterprise Technical Symposium 2001        Anaheim, California               http://www.cets2001.com         $ Questions? information@cets2001.com   
 SEPTEMBER 25  , Enterprise Server Local Users Group Meeting  Washington, DC 0& http://encompasserve.org/lugs/esilug/    OCTOBER 9               ( Compaq Technology Update -- Southeast    Atlanta, Georgia        ' http://www.compaq-signup.com/southeast ." Questions? Mickey.Pugh@Compaq.com 0                                                  OCTOBER 25 t Local Partnership Program  Hosted by Encompass 0 Lexington, Massachusetts                        @ Questions? Information@EncompassUS.org or Anne.Foley@Compaq.com   0                                                 B To submit a calendar listing, please contact: andrea_may@sba.com.   A Encompass headquarters is at 401 N. Michigan Avenue, Chicago, IL .1 60611. To reach headquarters, call 877.354.9887.         BOARD OF DIRECTORS 8  Joe Pollizzi - President         Compaq Relations x   Clay Denton - Vice President y CETS d    Jim Becker- Secretary/Treasurer  Communications f   Rochelle Lauer - Director  Volunteer Recruitment/Support    Patrick McMichael - Director r Local User Groups    Barbara Nicholson - Director   Regional Events    Jean Norton - Director   Membership Services    Clyde Poole - Director w& Business Practices/Strategic Planning     Terry Shannon - Director         Advocacy                  o   --
 Jim Becker+ The Urban Institute (http://www.urban.org/) ' Encompass (http://www.encompassus.org/)c. ESILUG (http://encompasserve.org/lugs/esilug/)   ------------------------------  % Date: Wed, 08 Aug 2001 18:33:14 -0400=" From: Mark <espexplorer@iname.com>1 Subject: Qume QTV-202 keyboard and Dec 3000/300LXA) Message-ID: <3B71BE2A.2184B53E@iname.com>1  H Does anyone happen to know if the Qume QVT-202 keyboard can be used withC the DCE 3000/300LX?  I guess my real question is whether or not theiA QVT-202 is compatable with the Digital LK201 and LK401 keyboards.$   Thanks for any information,    Mark   ------------------------------  % Date: Wed, 08 Aug 2001 22:28:44 +0200e, From: Didier Morandi <Didier.Morandi@gmx.ch>& Subject: Red Code: where are we going?& Message-ID: <3B71A0FC.E363BD97@gmx.ch>   (from my Mac PWS logfile)t   ../.. ? [06/AUG/2001:20:22:39 +0200] ""GET /default.ida?62.2.50.88 - -  @ [06/AUG/2001:20:22:40 +0200] ""GET /default.ida?62.2.41.232 - - C [06/AUG/2001:20:22:47 +0200] ""GET /default.ida?217.162.136.38 - - eA [06/AUG/2001:20:23:45 +0200] ""GET /default.ida?62.2.111.166 - -  @ [06/AUG/2001:20:23:56 +0200] ""GET /default.ida?62.5.41.200 - - A [06/AUG/2001:20:24:05 +0200] ""GET /default.ida?62.2.139.125 - -  B [06/AUG/2001:20:24:15 +0200] ""GET /default.ida?217.162.98.14 - - C [06/AUG/2001:20:24:19 +0200] ""GET /default.ida?217.162.65.195 - -  @ [06/AUG/2001:20:28:57 +0200] ""GET /default.ida?62.2.73.140 - - A [06/AUG/2001:20:29:10 +0200] ""GET /default.ida?62.2.148.115 - - aC [06/AUG/2001:20:29:28 +0200] ""GET /default.ida?217.162.136.38 - -  D [06/AUG/2001:20:30:41 +0200] ""GET /default.ida?217.162.176.136 - - ? [06/AUG/2001:20:32:02 +0200] ""GET /default.ida?62.2.80.37 - - :D [06/AUG/2001:20:32:16 +0200] ""GET /default.ida?217.162.120.242 - - D [06/AUG/2001:20:33:48 +0200] ""GET /default.ida?217.162.112.134 - - C [06/AUG/2001:20:34:16 +0200] ""GET /default.ida?217.162.110.21 - - -@ [06/AUG/2001:20:35:10 +0200] ""GET /default.ida?62.2.43.127 - - @ [06/AUG/2001:20:42:19 +0200] ""GET /default.ida?62.2.108.60 - -  ../..w (X and N letters suppressed)  L in two days, 202 794 X and 6 802 N (how many repeated characters by attack?)  H Does this mean that all these poor PC users were infected and that theirD IIS is trying to infect my iMac? (217.162.x.x and 62.2.x.x are Swiss Cablecom networks)  H If this is the case, this RED CODE apocalypse is a genuine apocalypse...   D.   ------------------------------  % Date: Wed, 08 Aug 2001 16:37:56 -0400s- From: JF Mezei <jfmezei.spamnot@videotron.ca>s* Subject: Re: Red Code: where are we going?+ Message-ID: <3B71A30F.463E171@videotron.ca>g   Didier Morandi wrote: J > Does this mean that all these poor PC users were infected and that their# > IIS is trying to infect my iMac?    N Yes. They send an HTTP request to anyone and everyone, and if there is a replyL that shows that the server is a microsoft IIS of the right version, then theN infected machine will infect the host which will in turn try to infect as many machines as it wants.-  M They can't infect your mac, but they will still knock at its door to find outb# if you are on a MS software or not.a   ------------------------------  % Date: Tue, 07 Aug 2001 21:21:43 -0500s1 From: "David J. Dachtera" <djesys.nospam@fsi.net>n. Subject: Re: REQ: VMS Baseball Cap (Help Sue?)' Message-ID: <3B70A237.B60F757C@fsi.net>    Jan-Erik Sderholm wrote:o >  > Hm...e8 > I keep getting "Zip/Postal Code or State invalid", but  > we don't have those in Sweden. >  > What to do ? > 	 > Regardso > Jan-Erik Sderholm >  > Hoff Hoffman wrote:a > > H > >   Connect to www.openvms.compaq.com, select the "portal" link on theH > >   upper left of the page, then select the estore link (bottom right,J > >   IIRC).  Yes, you do need to access the store via the Compaq website.  4 Ah! The wonders of being an international company...   -- - David J. Dachtera- dba DJE Systems0 http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/p   ------------------------------  # Date: Wed, 08 Aug 2001 05:46:28 GMTn From: Dirk Munk <munk@home.nl>. Subject: Re: REQ: VMS Baseball Cap (Help Sue?)' Message-ID: <3B70D233.CF4B8875@home.nl>r  & --------------81009F64B1F3D59B30399082* Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bito  _ I noticed the cap has a real Digital-style order number (QA-6MDAE-G9). Does this mean we need ai1 license too if we want to wear it (QL-6MDAE-2B) ?r       Hoff Hoffman wrote:s  d > In article <3b70479f$1@news.si.com>, "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:K > :>>    I have (had) one of those great VMS caps and it self-destructed inCK > :>> a coin-op washing machine.  Can someone give me a pointer as to whereSL > :>> to get another? (Sue?)  I got the original from a Compaq VMS team that$ > :>> came to our company.   Thanks! > :>O > :>http://www.e-softwarefactory.com/acb/showdetl.cfm?&DID=30&Product_ID=215810 
 > :&CATID=194  > :S- > :So, I tried this URL.  This is what I get:o? > :This site is only accessible through the link pages found atW: > :WWW.OPENVMS.COMPAQ.COM or WWW.OPENVMS.DIGITAL.COM (app) >tF >   Connect to www.openvms.compaq.com, select the "portal" link on theF >   upper left of the page, then select the estore link (bottom right,H >   IIRC).  Yes, you do need to access the store via the Compaq website. >lP >  ---------------------------- #include <rtfaq.h> -----------------------------L >       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.comP >  --------------------------- pure personal opinion ---------------------------N >    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com  & --------------81009F64B1F3D59B30399082) Content-Type: text/html; charset=us-asciit Content-Transfer-Encoding: 7bito  > <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html>F I noticed the cap has a real Digital-style order number (QA-6MDAE-G9).H Does this mean we need a license too if we want to wear it (QL-6MDAE-2B) ?d
 <br>&nbsp;
 <br>&nbsp; <p>Hoff Hoffman wrote:M <blockquote TYPE=CITE>In article &lt;3b70479f$1@news.si.com>, "Brian Tillman"s0 &lt;tillman_brian@notnoone.notnohow.com> writes:F <br>:>>&nbsp;&nbsp;&nbsp; I have (had) one of those great VMS caps and it self-destructed inhF <br>:>> a coin-op washing machine.&nbsp; Can someone give me a pointer as to where I <br>:>> to get another? (Sue?)&nbsp; I got the original from a Compaq VMSo	 team thatA0 <br>:>> came to our company.&nbsp;&nbsp; Thanks! <br>:> <br>:><a href="http://www.e-softwarefactory.com/acb/showdetl.cfm?&DID=30&Product_ID=215810">http://www.e-softwarefactory.com/acb/showdetl.cfm?&amp;DID=30&amp;Product_ID=215810</a>o <br>:&amp;CATID=194i <br>:o4 <br>:So, I tried this URL.&nbsp; This is what I get:A <br>:This site is only accessible through the link pages found ats< <br>:WWW.OPENVMS.COMPAQ.COM or WWW.OPENVMS.DIGITAL.COM (app)H <p>&nbsp; Connect to www.openvms.compaq.com, select the "portal" link on the F <br>&nbsp; upper left of the page, then select the estore link (bottom right,K <br>&nbsp; IIRC).&nbsp; Yes, you do need to access the store via the Compaqr website.Y <p>&nbsp;---------------------------- #include &lt;rtfaq.h> -----------------------------eI <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For additional, please see the OpenVMSt FAQ -- www.openvms.compaq.comlW <br>&nbsp;--------------------------- pure personal opinion --------------------------- S <br>&nbsp;&nbsp; Hoff (Stephen) Hoffman&nbsp;&nbsp; OpenVMS Engineering&nbsp;&nbsp;E' hoffman#xdelta.zko.dec.com</blockquote>g </html>i  ( --------------81009F64B1F3D59B30399082--   ------------------------------  # Date: Wed, 08 Aug 2001 20:34:45 GMTm' From: ben_myers@charter.net (Ben Myers)e< Subject: Re: Source for non-standard DEC 15 Amp power cords?0 Message-ID: <3b71a23f.29926093@news.charter.net>  E Heat up your VAX enough and maybe it could boil water.  :)   Not goody for the VAX, tho... Ben Myersa  B On Wed, 08 Aug 2001 18:18:04 +0100, ChrisQ <quattro@aerosys.co.uk> wrote:   >Robert DiRosario wrote: >> cI >> Where can I get the non-standard 15 Amp 120V power cords that DEC usedoI >> on things like the VAX 4000 systems in the BA-440 enclosure or the DEC  >> Alpha 3000/900? >o >Robert, > S >I think what you want is the IEC "hot condition" plug lead set. These are like the X >standard IEC plugs, but have a notch along the length of the flat side and are rated at5 >10a, not 5 as per the standard un-notched cord set. i >aQ >Here in europe they are fitted to electric kettles etc, which is probably no usee' >whatsoever if you are in the US ;-)...  >t >Chris  	 Ben Myerse Spirit of Performance, Inc., 73 Westcott Road Harvard, MA 01451N tel: 978-456-3889d eFax: 810-963-0412 o  PayPal, MC, VISA, AMEX accepted.   ------------------------------  # Date: Wed, 08 Aug 2001 01:27:36 GMToL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")= Subject: Re: Suggested DCPS features (was OpenVMS  + Itanium).8 Message-ID: <00A002F7.18CC8159@SSRL04.SLAC.STANFORD.EDU>  b In article <3b704c8c$1@news.si.com>, "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:M >>It should be possible to use the printer feature in the normal way via DCPSuL >>for the Guru's or people who knows all the printer features. For all other= >>(normal users), there should be a GUI like the windows GUI.c >iI >That's been available since DECwindows first came out.  It's the "print"aJ >widget.  Just click on any DECwindows "File" menu and you'll see it.  YouM >can specify anything there that the PRINT command supports, including any of 5 >the /PARAMETERS that any specific symbiont supports.t  I Kinda.  You have to know what the options are.  And if the printer has a eI funny set of trays (say, tray_1, tray_2, tray_3, tray_4 instead of upper,fI middle, lower) that's not reflected in what the print widget offers, and tM if you try to select a tray that doesn't exist by that name on that printer,  L DCPS will drop your job on the floor, rather than, say, guessing which tray ; you want or printing from the default tray on that printer.c  ) (Been there, done that, pretty recently.)s   -- Alan   O ===============================================================================c0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056oM  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210eO ===============================================================================t   ------------------------------   Date: 8 Aug 2001 16:23:39 -0700t1 From: keithparris_nospam@yahoo.com (Keith Parris)vE Subject: Re: suggested reading: "Making a Mountain Out of a Molehill"e= Message-ID: <dba3451e.0108081523.55a36b37@posting.google.com>n  f "Bill" <billmuy@home.com> wrote in message news:<8AP77.409232$p33.8364805@news1.sttls1.wa.home.com>...N > 1. Speculating that McKinley rumoured performance may be "close to the sweetJ > spot for IA64", suggesting that further performance gains would be hard.N > Surely a person with Mr DeMone's apparent experience should know better than > that!X  F The "sweet spot" he was talking about was with regard to the amount of7 parallelism within the chip compared with the amount ofe7 instruction-level parallelism to be found in most code.r  @ The terminology uses an analogy with an engine and the number ofD cylinders it has.  Since 3 instructions fit into one IA64 code word,> an implementation that can issue 3 instructions in parallel isE referred to a "one-banger".  An implementation which can issue 2 codefE words (6 instructions) in parallel is referred to as a "two-banger". mC Merced and McKinley are both "two-bangers", but Paul points out how @ Merced has insufficient execution units to really handle all theF likely instruction combinations, and speculates that McKinley has more execution units.  D One could conceivably implement a "four-banger" but Paul feels thereD is not enough instruction-level parallelism in the real world to getE much performance benefit from that.  So a "two-banger" implementation C is probably optimal.  That's the "sweet spot" he was talking about.b  A This doesn't preclude optimizations in other areas of the design..C -------------------------------------------------------------------gC Keith Parris | parris at encompasserve dot org | VMS consulting on:aC Clusters, Disaster Tolerance, Internals, Performance, Storage & I/OO   ------------------------------  % Date: Wed, 08 Aug 2001 14:29:31 +0100U0 From: andrew harrison <andrew.nospam@uk.sun.com>+ Subject: Re: Sun goes after Alpha user base * Message-ID: <3B713EBB.CDA83D5E@uk.sun.com>  " "Scandora, Anthony (35048)" wrote: > N > I'm trying to remember a significant processor delivery that beat or met itsC > original announced date.  I can't, and I don't really care.  It'sgN > interesting to learn about what's being developed, but only a fool would betF > real money on any major new technology's first working release date. >   D I would be the first to agree with you, particularly if the vendors B of the processors don't make vast performance claims for their yet@ to be delivered systems in the hope that people will stop buying someone elses systems.  A Sadly that hasn't been the case particularly in this group where cA we were getting performance estimates for TPC-C on WildFires withOE an assertion that this would trash Sun/HP/IBM boxes arround 18 monthse! before WildFire actually shipped.s  C This is only one of a number of similar incidents in the same vein.r      J > I'm far more concerned with what works.  As far as I know, EV6 does, andL > some time next year or early 2003, EV7 is likely to.  When will Sun figure% > out how to make a cache that works?  >   6 We did some time ago. The ecache on E10Ks and smaller 7 UltraII based machiens has been modified. This happeneda late last year.    Regardsr Andrew Harrison  Enterprise IT Architectp   ------------------------------  # Date: Wed, 08 Aug 2001 00:02:29 GMTe' From: bad bob <sfmc68@bellatlantic.net>o  Subject: Re: Sun keep 'em coming0 Message-ID: <3B708511.66DCC4EB@bellatlantic.net>   Arne Vajh=F8j wrote: > =    > andrew harrison wrote: > > Arne Vajh=F8j wrote: > > > wanderer wrote: J > > > > Just a thought, what if an independent company would buy the righ= ts tosJ > > > > VMS and the layered products and port the stuff over to Sun hardw= are?J > > > > Mentec afterall bought the rights from Dec for the PDP based OS's= =2E  > > >  > > > What is the point ?  > > > G > > > SPARC systems have a cache problem. Intel systems can not divide.  > >hJ > > SPARC systems had a cache problem, Intel used not to be able to divid= ecF > > and Alphas used to overheat and brew up in a sometimes spectacularB > > way as one of the insurance companies in the UK found to their	 > > cost.w > >2 > > No big difference IMHO.i > =a  	 > Oh yes.. > =    > Big difference.e > =e  = > SPARC and Intel were lots of systems. The problems has beenm+ > public acknowledged from very high level.  > =   B > The Alpha story you bring up is an unsubstantiated story brougth > up by a SUN emploeyee. > =s   > That is a big difference ! > =m   > Arne	 Hey Arne! D YOur original response to the question was on the money, why bother?E One of the things that customers have been taught by various vendors, C in an attempt to manage their expectations, is that all you have to.C do is reboot every once in a while, say once a week. With customers  trained this way, why bother?t  C In days of old we had this theory of flogiston, that is tied to theA@ concept of flooby dust.  Flooby dust fills up the cache in suns,@ so the cache needs to be recycled.  In MS boxes, it fills up theC bit bucket and the memory starts to leak. So, you shut it off and =i  @ let the flooby dust settle to the bottom of the bit bucket, then? restart.  Real systems run a bit longer than MS or E10Ks.  I do - like the ultrasparc boxes, not bad terminals.l   bobi   ------------------------------   Date: 08 Aug 2001 19:45:06 GMT' From: "Jim Strehlow" <jims@data911.com>i Subject: Re: SYBASE on VMS0 Message-ID: <9ks4s2$3at@dispatch.concentric.net>  E We still have some client customers running our software with Sybase..3 Most client customers run our software with Oracle.c   Jim Strehlow, Data911s Alameda, CA, USA JimS@Data911.com  = Arne Vajhj wrote in message <3B6FE8AC.56490B82@gtech.com>...r >Jakob Erber wrote:@L >> Sybase will soon stop its support for its DB product on OpenVMS. Is there8 >> anybody out there, who is also effected by this step? > 	 >Oh yes !T >2 >Arner   ------------------------------   Date: 8 Aug 2001 13:03:21 GMTs1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)eB Subject: Re: TCPware v5.5-3: file size change during FTP transfer?, Message-ID: <9krdap$14h0$1@info.cs.uofs.edu>  = In article <9f261edc.0108071241.56448493@posting.google.com>,i0  tessier-ashpool@usa.net (Chris Bardell) writes:) |> Yeah, I know this sounds a little odd.x |>  G |> Here's an extract from an FTP logfile. The server is running OpenVMSTH |> Alpha v7.2-1, with TCPware v5.5-3. The client is a PC running CuteFTP; |> (although this seems to happen across multiple clients).e |> .E |> <<<150 Opening data connection for DISKnn:[BLAH]FILE.DAT;123 (3200d
 |> bytes).>>>- |>  G |> The transfer then takes place, but appears to send fewer characters,/ |> eg: |>  A |> <<<226 Closing data connection. 2992 (8) bytes transferred.>>>  |> ]H |> Why the discrepancy in the original file size (3200 bytes) versus the |> amount transferred (2992)?- |> 01 |> The file is ASCII data, with these attributes:74 |> Record format:      Fixed length 128 byte records7 |> Record attributes:  Carriage return carriage controlG |> eF |> NB: this is NOT a pedantic question; this has caused some difficult, |> problems for an organisation I deal with. |>  B |> Sounds like some sort of optimisation or compression (?), but IF |> basically wanna switch it off! AFAIK, the previous version (v5.4-3)E |> did not do this. I've checked the manuals, website, Usenet - still]1 |> can't find an answer. I'm aware of the logical0A |> TCPWARE_FTP_DONT_REPORT_FILESIZE but this doesn't appear to be1 |> directly relevant./ |> l@ |> If anyone can offer any help or suggestions, I'd be extremelyF |> grateful. Also please forgive is this is a dumb-ass question or I'm% |> missing something obvious. Thanks.r |> s  E If I had to guess, I would say the count reflects characters actually6C sent.  As you likely know, the format of an ASCII file differs fromsC OS to OS.  In order to maintain the proper format for ASCII on both-E ends the transfer is actually done by converting the file to NETASCIImI and then converting it to native ASCII when it arrives on the destinationeE end.  NETASCII uses a single character (LF, 10, 012, 0A, '\n') as thenD end of line marker.  Because many other machines (DOS, VMS) use more@ than one character as a record separator the count of transferedB characters will be different than the size of either the source or destination file.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   e   ------------------------------   Date: 8 Aug 2001 16:02:44 -0700 3 From: utlonghornsrule@yahoo.com (Newbie JrSysAdmin)h- Subject: Re: Terry Shannon Tech Talk on Tru64Q= Message-ID: <2de05464.0108081502.56624985@posting.google.com>f   ">  ! > Copyright 2001 Terry C. Shannon 6 > Not affiliated with ... Compaq Computer Corporation.  D lackey, do you even know what a good hotel room in anaheim costs, or1 did your "non-affiliate" take care of it for you?w   ------------------------------  % Date: Thu, 09 Aug 2001 00:47:12 -0400l' From: Jim Becker <jbecker@ui.urban.org> - Subject: Re: Terry Shannon Tech Talk on Tru64 , Message-ID: <3B7215D0.39839B17@ui.urban.org>   Robert Deininger wrote:  > ? > In article <2de05464.0108081502.56624985@posting.google.com>,.6 > utlonghornsrule@yahoo.com (Newbie JrSysAdmin) wrote: >  > > ">% > > > Copyright 2001 Terry C. Shannonw: > > > Not affiliated with ... Compaq Computer Corporation. > > H > > lackey, do you even know what a good hotel room in anaheim costs, or5 > > did your "non-affiliate" take care of it for you?D > 8 > What's happened to people's manners in this newsgroup? >  > -- > Robert Deininger > rdeininger@mindspring.comn  A And what happened to checking facts instead of spreading baselessdD innuendo? Fact: Compaq is not "taking care of" Terry Shannon's hotel arrangements at CETS.A   --
 Jim Becker+ The Urban Institute (http://www.urban.org/)1' Encompass (http://www.encompassus.org/)r. ESILUG (http://encompasserve.org/lugs/esilug/)   ------------------------------  $ Date: Wed, 8 Aug 2001 14:41:58 -0400' From: "Bill Todd" <billtodd@foo.mv.com>e$ Subject: Re: Third postcard from Sun( Message-ID: <9ks166$ijf$1@pyrite.mv.net>  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3B716EA4.40382F33@videotron.ca... > Bill Todd wrote:J > > Given what dropping Alpha is likely to cost Compaq over the 3 years or soI > > before the port generates a single penny of compensating revenue (notf thatD > > even at that point the compensation will likely be anything like
 complete),K > > the course upon which Compaq has embarked just about has to be the mosth2 > > expensive course it possibly could have chosen > H > I disagree completely. Put yourself in Compaq's shoes. The cost of the port is-F > probably paid for by the large wad of cash that Intel gave Compaq in excahnge< > for Compaq killing Alpha and sending its remains to Intel.  I You misunderstand completely.  The cost of the port is peanuts.  The real-J expense is in lost market-share and profit opportunities during the periodH when VMS and Tru64 are available only on a declared-dying platform, plusF thereafter if indeed this causes a loss in market share, plus the lostI opportunity to leverage Alpha's ability to be a long-term major player in ! mid-range-and-up market segments.n  G That one-time 'wad of cash' would have to be at least in the $5 billionaI range to be anywhere nearly large enough to compensate for taking a majoroK hit in the well over $1 billion in lost annual Alpha-related *profit* (evenlJ with the current anemic marketing efforts - and a good deal more if CompaqD had decided to try to make Alpha the centerpiece it deserved to be).   ...   L > The killing of Alpha was just a strategic decision that will enable Compaq toC > go where it wants to go today. It has nothing to do about Alpha'se) > technological superiority or costs etc.;  L That I can agree with whole-heartedly.  Aside from integrity-related issues,B however, the big question is WHY Compaq wanted to abandon its mostB profitable and most promising business segments (Alpha and to someG appearances now Storage as well) to go in other directions which it has I already demonstrated less than stellar competence to pursue (e.g., havingWI run DEC's service business into the ground, it's now talking about buyingwL others to destroy, and after 3 years of major effort its PC business has yet7 to do more than break even against Dell's competition).,   - bill   ------------------------------  % Date: Wed, 08 Aug 2001 15:06:27 -0400t- From: JF Mezei <jfmezei.spamnot@videotron.ca>u$ Subject: Re: Third postcard from Sun, Message-ID: <3B718DA6.44CF35BC@videotron.ca>   Bill Todd wrote:K > You misunderstand completely.  The cost of the port is peanuts.  The real-L > expense is in lost market-share and profit opportunities during the periodE > when VMS and Tru64 are available only on a declared-dying platform,   M Calculated decision. Cannabalise VMS sales in favour of getting all that cash5> from Intel that allows you to build more profitable businesses6 (software/support/solutions/service) in the long term.  I If Compaq that VMS's days were numbered anyways (whether in a few or manygM years), then it is normal for Compaq to seek to replace the VMS business with 7 something that has much longer term lifetime potential.   N The fact that Compaq has taken the decisions it has taken so fart with regardsN to VMS indicates to me that Compaq does not beleive that VMS has a bright longL term future, but beleives that it is worth continuing to support VMS for nowM because it is not only profitable, but also give Compaq a foot in the door ofi some very rich customers.   H > thereafter if indeed this causes a loss in market share, plus the lostK > opportunity to leverage Alpha's ability to be a long-term major player in # > mid-range-and-up market segments.e  G If Compaq beleives that NT will rule the enterprise market, then Compaq L should/needs to develop its NT based enterprise solutions and systems. If itE is smart, it will be able to leverage some of its "legacy enterprise"5D expertise (VMS/Unix) to build better NT based systems and solutions.  N The minute you start to beleive that Compaq truly intends to be the world's #1M NT enterprise company, then all of Compaq's actions (or inactions) make a lot 	 of sense.:  I > That one-time 'wad of cash' would have to be at least in the $5 billionCK > range to be anywhere nearly large enough to compensate for taking a major H > hit in the well over $1 billion in lost annual Alpha-related *profit*   N You are assuming that Compaq will instantly lose VMS related revenus. AirlinesL claim that the vast majority of their profits come from a few business classL passengers. I have to assume that Compaq did the same math and realised thatN it can ditch a large number of VMS customers and keep the few truly profitable, ones with minimal impact on the bottom line.  J And the fact that compaq seems to have bothered to visit some of its trulyJ profitable customers on the day the alpha was killed is an indication that6 Compaq does intend to pamper and keep those customers.  D > however, the big question is WHY Compaq wanted to abandon its most2 > profitable and most promising business segments   M Even while it was  taking on water, the Titanic was still the world's largesttN and most luxurious ship, with the alchool and violins still going, power stillM being supplied to light/heat the ship etc. But the captain knew that it wouldtL sink, it was just a matter of time. Strategically, it made sense to take theJ steps that would eventually lead you off that ship in a controller/orderly fashion without any major rush.N  L This is especially true if you know that they have just finished a brand newM ship that promises to be even bigger and more comfortable and faster and that3M it will come to rescue you just in time, with just a small migration from one=$ to the other by using the lifeboats.   ------------------------------  $ Date: Wed, 8 Aug 2001 16:30:13 -0400' From: "Bill Todd" <billtodd@foo.mv.com>t$ Subject: Re: Third postcard from Sun( Message-ID: <9ks7h0$p4g$1@pyrite.mv.net>  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3B718DA6.44CF35BC@videotron.ca...   ...0  E > The minute you start to beleive that Compaq truly intends to be thee
 world's #1K > NT enterprise company, then all of Compaq's actions (or inactions) make ac lotn > of sense.r  D Under the same premise, so did DEC's actions 5 or 6 years ago.  ThatL premise, however, doesn't appear all that much solider now than it did then,9 and Compaq may reap the same rewards for it that DEC did.    >mK > > That one-time 'wad of cash' would have to be at least in the $5 billionmG > > range to be anywhere nearly large enough to compensate for taking as majoreI > > hit in the well over $1 billion in lost annual Alpha-related *profit*s >3G > You are assuming that Compaq will instantly lose VMS related revenus.i  G I am only assuming that Compaq will lose perhaps 30% of current VMS andtJ Tru64 revenues.  Given that some costs are fixed, the relationship betweenI revenue and profit tends to be supra-linear:  losing 30% of revenue couldaH easily result in loss of 50% of profit (which was what I was SWAGging it9 would take around $5 billion up-front to compensate for).   J Of course, by the same token doubling VMS revenues might well have tripled
 VMS profit...o   - bill   ------------------------------  $ Date: Wed, 8 Aug 2001 08:36:40 -0400' From: "Bill Todd" <billtodd@foo.mv.com>p$ Subject: Re: Third postcard from Sun( Message-ID: <9krbp2$oll$1@pyrite.mv.net>  F "Larry Kilgallen" <Kilgallen@eisner.decus.org.nospam> wrote in message- news:xI3TUzd2W+hp@eisner.encompasserve.org...sI > In article <3B710FB0.86713E3@gtech.com>, Arne =?iso-8859-1?Q?Vajh=F8j?=,  <arne.vajhoej@gtech.com> writes: > > Bill Todd wrote:7 > >> "Dan O'Reilly" <dano@process.com> wrote in messagenA > >> news:5.1.0.14.2.20010806144824.02c4cba8@ntbsod.psccos.com...eF > >> > Or maybe, just MAYBE, the customers have been wanting VMS on an	 industry-yE > >> > standard platform all along (like many in this forum have beend bitching > >> > about). > >>J > >> People like you keep trying to foist this myth upon the world, but it simplyJ > >> doesn't wash.  I defy you to find a single post, ever, in c.o.v. thatE > >> suggested that VMS should be *moved* to another platform (at thel
 expense ofI > >> support of the Alpha platform):  every suggestion I've ever seen has  been to E > >> *expand* the availability of VMS to *include* a second platform.h > >oF > > My guess would be that most posters has not explicit stated any of > > theese.c > >yK > > If someone says "I would like to see VMS on Intel" it is pretty open tolE > > be interpreted as "add" or "replace" depending on what the readern
 > > wants. >e > Or what Compaq can afford.  I Given what dropping Alpha is likely to cost Compaq over the 3 years or so J before the port generates a single penny of compensating revenue (not thatK even at that point the compensation will likely be anything like complete),uG the course upon which Compaq has embarked just about has to be the mosthF expensive course it possibly could have chosen (at least compared withE alternatives such as maintaining the status quo and its stable profitpF stream, or doing that plus really starting to market and develop AlphaC products, especially VMS, so as to grow that profit stream - which,cJ incidentally, would have made *adding* IA64 support to VMS fit right in as part of that growth strategy).   - bill   ------------------------------   Date: 8 Aug 2001 19:29:20 -0700 + From: mend0070@tc.umn.edu (Phil Mendelsohn)c/ Subject: uVAX 3100 M38 hardware troubleshootingn< Message-ID: <9fffd0d8.0108081829.9f2a6bd@posting.google.com>  - Hi,  setup follows, with question at the end:r  F I'm salvaging a pallet of surplus uVAXen 3100's, Storage Expansion, anD InfoServer, some DECstations (now mostly parts, where applicable  --F i.e. drives), and some VT1300s.  This is hobbyist; it happened largelyC due to a little creativity in rearranging a crowded basement and an  understanding wife.c  A Had pretty good luck -- I've got 3 or 4 working so far.  Today, IeF tried to salvage an ex-NASA VAXstation 3100 M38.  Pretty clean, only a= little corrosion around the battery (leaked), but cleaned up.   > First boot got to the dead sargeant ">>>", and SHOW DEV workedF alright, but failed to boot.  ("Darn, no interesting NASA data on thatD one...")  Powered off.  Attached CD-ROM (untested RRD-42) to try andD boot Hobbyist VMS CD-ROM.  Funny power-up test (below.)  Tried known@ good Toshiba CD-ROM drive.  Tried no SCSI drive.  Tried with andF without 4MB memory expansion (suspected that it might have experiencedC ESD death when removed for cleaning.)  Dead backup battery on/off.  D Visual inspection -- everything seems OK, but now boot sequence goes
 like this:  > F..E..D..C..B..{insert 3-5 minute pause here but not new line}+ F..E..D..C..B..A..9..8..7..6..5..4..3..2..1u   ? F 	0101  0101.0101 ? E	0101  0101.0101eB <snip, but run through all 15 power power up tests with same code> ? 1     0101  0101.0101h   **QUESTION**E Is anyone able to pass along the significance of this error code, andeD if so, please do.  This machine acts like all the good uVAXen I haveF until it gets to ..B {long pause}.  I know this is the MEMory test, soE I suspect that's the culprit.  No, I haven't tested with other memorys? yet; I'm not willing to give up the good (scarce) memory in theaB working machines in case something here might be bringing it down.  D My suspicion is that this is a "global" hardware error of some sort,A 'cause it's a little too orderly to be random and the serial portt# bothers to tell it to the terminal.a  @ Can anyone confirm or deny, and any information is appreaciated.   Thanks in advance.   Phil Mendelsohnr   ------------------------------   Date: 7 Aug 2001 17:32:15 -0700d0 From: 75176.2451@compuserve.com (Scott Campbell)F Subject: Re: very nice message also room for feedback on this web site= Message-ID: <2c127902.0108071632.381f5ad7@posting.google.com>v  a JF Mezei <jfmezei.spamnot@videotron.ca> wrote in message news:<3B6EF841.6388EBA4@videotron.ca>...c > Sue Skonetski wrote:I > > Off-the-Shelf Compaq AlphaServer Systems Power Sophisticated Militaryi  > > Airborne Surveillance System >  tN > > airborne surveillance and target acquisition. Northrop Grumman CorporationP > > (NYSE: NOC) partnered with Compaq Computer Corporation (NYSE: CPQ) to outfitI > > its latest super-sophisticated battlefield surveillance aircraft with<( > > commercial, off-the-shelf computers. >  LP > > Known as Block 20 E-8C Joint Strategic Target Attack Radar System (J-STARS),O > > the plane uses 20 Compaq AlphaServer(TM) ES40CV systems running the OpenVMS2 > > operating system.  >  > P > Dear Sue, tell your managers that while it is great news to announce a win forM > VMS,  they should have just omitted any mention of the word "Alpha" in thatbN > announcement. It makes the military look silly for purchasing dead hardware. > P > Secondly, the use of "commercial off the shelf hardware" goes against Compaq'sP > whole "public" decision to dump proprietary Alpha in favour of "off the shelf" > industry standard Intel crap.i > M > Is Alpha industry standard commercial off-the shelf or not ? If it is, theneN > why kill it ? And if it isn't, then stop describing Alpha as such because it@ > makes Compaq look very silly to flip flop on its own products.  E Having worked on Joint STARS for more than 10 years, lately as one ofdB the lead VMS programmers, I can tell you there is a big differenceD between the special militarized equipment that is currently deployedA and the ES40 systems we are migrating to. The primary emphasis in>C using COTS is to reduce overall life cycle costs. By using standardt> commercial hardware, we are saving several million dollars perE aircraft for our customer (and the taxpayers). The entire suite of 20IF ES40 systems costs about the same as just one of the older militarized; VAX systems (and there are five of those per aircraft), andr" outperforms them by a wide margin.  A And COTS does not apply just to hardware; we are integrating morelD off-the-shelf software, too. Most software for military applicationsA is highly customized, with commensurately high maintenance costs.sB Using VMS is just one part of the equation, although certainly theE operating system is one of the most important considerations. We havemE encountered very few problems using VMS on both VAX and Alpha systemso= over the past 12 years. We have come close to the edge of itsnE real-time capability, especially on the older VAX, but it handles our- application very well.  E Using Alpha systems is not silly; we need the extreme performance and B reliability that this platform affords us. Compaq support has beenC superb during our entire development program, despite our sometimeso< extreme demands on them. Even though our next upgrade may beF IA64-based, I see nothing in that to be overly concerned about, and weF should be able to continue to provide our customer with a leading edge system at reasonable cost.  F This is a purely personal opinion and does not reflect the policies of3 Northrop Grumman Corporation or the U.S. Air Force.       -- Scott Campbell   ------------------------------  % Date: Tue, 07 Aug 2001 21:05:39 -0500a1 From: "David J. Dachtera" <djesys.nospam@fsi.net>.! Subject: Re: VMS 7.3 experiences? ' Message-ID: <3B709E73.E3E8326A@fsi.net>    Mark Daniel wrote: > D > "Beware the Ides of XFC" lest your RMS integrity die an unpleasant > death. > [snip]: > Moral of the story; at least wait for Service Pack 1 ;^)  C Now you know why I refer to "General Availability" as "Gamma Test".h   --   David J. Dachtera  dba DJE Systems? http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/n   ------------------------------  $ Date: Wed, 8 Aug 2001 10:23:34 -0400. From: "Kenneth Randell" <kenr@datametrics.com>! Subject: Re: VMS 7.3 experiences?t+ Message-ID: <9kri0a$sou$1@bob.news.rcn.net>:  F Not to add fuel to this fire, but my experience has been that under NOL circumstances should you use $IO_PERFORM while running XFC with VMS 7.3.  If you try it, you'll see why.v  L CSC has a patch for this...although I would have expected to see an official( patch kit by now appear on the web site.   Ken Randell   : Mark Daniel <Mark.Daniel@wasd.vsm.com.au> wrote in message) news:3B6F86E7.BDBAC4E3@wasd.vsm.com.au...lD > "Beware the Ides of XFC" lest your RMS integrity die an unpleasant > death. >eH > We recently upgraded to 7.3 on two Alpha clusters (7 and 4 systems) asH > well as a miscellany of stand-alone systems.  This was in part to reapF > the benfits of XFC (which looked promising on the two standalones we5 > experimented on - obviously not thoroughly enough).m >tE > From the outset we noticed (and reported) %XFCACHE-W-DATALOSS OPCOMbF > messages.  This (seems) to have resulted in at least one applicationI > ACCVIOing.  More recently we noticed RMS index file corruption (ANA/RMSdH > reporting "Unrecoverable error encountered in structure of file") withC > XFC (VIOC) turned on and none with it turned off (same data, samehC > application, 2 cycles of investigation).  Without reproducing thesF > contents of some two dozen or so emails back and forth with CSC it's8 > difficult to be more specific with these descriptions. >aF > CSC and VMS Engineering are working (feverishly I should imagine) on > this.  Expect ECOs shortly.e > F > My recommendation would be DO NOT PROCEDE WITH ANY 7.3 UPGRADE until' > these issues (at least) are resolved.v >$: > Moral of the story; at least wait for Service Pack 1 ;^) >e > Rob Young wrote: > > % > > cmcgav@ionet.net wrote in messageq4 news:<bbltmt44uv2t2njmqmch61b59d457lnnqm@4ax.com>...I > > > On 2 Jul 2001 12:08:23 -0500, young_r@encompasserve.org (Rob Young)i > > > wrote: > > > ; > > > >In article <C2256A7D.004AA3C1.00@jklh21.valmet.com>,o" norm.raphael@jamesbury.com writes: > > > >> > > > >>
 > > > >> Tom,I > > > >>K > > > >> According to the cover letter for V7.3, V6.2 is _not_ supported ing ae > > > >> migration-modedJ > > > >> (or any other mode) with V7.3.  I have been told this is at least partly because > > > >> of C > > > >> mount hangs with volume shadowing on one of the Field Testo	 releases.s > > > >>D > > > >> Do you have any experience with this, positive or negative. > > > >> > > > >sF > > > >     Last week I booted an Alpha into a VAX 6.2 cluster.  Alpha runningiI > > > >     7.2-1 with latest SYS patch (but not the very latest, the oneoG > > > >     updated Thursday or so?).  Mounted disks not in use, copied1H > > > >     those files, that's easy.  But I also mounted and copied all	 files offpL > > > >     a VAX based shadowset.  Worked like a charm.  One datapoint does not a I > > > >     case make.  Your mileage may vary.  And the Alpha was removed  from the) > > > >     cluster after this operation.i > > > >n' > > > >                             Roba > > >o > > >aJ > > > Well, we are installing a new DS20E system, and did some simple timeG > > > trials with a batch application that does a good mix of reads ande
 > > > writes.i > > > ? > > > The disks were served by an HSG80 dual controller system.a > > >V > > > HSG caching turned off > > >h" > > > 7.2-1    No VIOC        6min  > > > 7.2-1    VIOC cache   4min' > > > 7.3      New XFC cache   9min!!!!  > > >s > > > HSG caching turned ont > > > B > > > 7.2-1   VIOC cache, HSG cache                      2min 1secA > > > 7.3      New XFC cache, HSG cache               2min 20 sec  > > >SI > > > Needless to say we were surprised and disappointed by the results..o > > >tK > > > Plus the IO's reported by the 7.3 runs were much higher than the IO'siG > > > from the 7.2-1 runs. CPU time and buffered were nearly identical.  > > >aD > > > Also all drives would only mount under VIOC compatibilty mode. > > >tG > > > Any ideas? I used the same settings for the 7.3 test as it was ane- > > > upgraded copy of the 7.2-1 system disk.t > >s= > > There is so much here... first, XFC will do pre-fetching:t > >sD > > http://www.openvms.compaq.com:8000/73final/6017/6017pro_077.html > >oI > > In an OpenVMS Cluster, different nodes can use different data caches.yH > > This allows mixed architecture clusters to benefit from XFC. OpenVMSJ > > Alpha nodes can use either XFC or VIOC. OpenVMS VAX nodes can use only) > > VIOC, as described in Section 18.5.6.: > > I > > XFC improves I/O performance and contains the following features that   > > are not available with VIOC: > >h > > Read-ahead caching# > > Automatic resizing of the cache  > > Larger maximum cache sizel= > > No limit on the number of closed files that can be cachedo; > > Control over the maximum size of I/O that can be cachedy: > > Control over whether cache memory is static or dynamic > >a > > ---u > >aE > > So this tells us all your I/O is random.  Or is it?  When you saye
 > > "cacheJ > > turned off on the HSG80s", you mean write-back cache?  You didn't turn > > off.+ > > read cache?  When using XFC, what does:t > >  > > $ analyze/system > > SDA> XFC SHOW SUMMARYo > >  > > reveal?  > >i > > I am peeling through:  > >q< > > http://www.decus.gr.jp/decus99/sessioncd/NOTES/OV166.PDF > >bI > > Slide seventeen shows how you can zoom in on individual files, locate  > > the - > > file id on a directory/full filename.ext;  > >t > > then in SDA: > >lH > > SDA> XFC SHOW FILE/ID=xxx  ! Converted to hex, see slide for details > >tI > > With both VIOC and XFC, what are your hit rates:  show memory/cache ?c > >n > > To a another PDF of Ian's: > >s< > > http://www.decus.gr.jp/decus99/sessioncd/NOTES/OV167.PDF > > F > > look at individual files with less detail, but mostly good enough: > > : > > $ show mem/cache/file=(device:[directory]filename.ext) > >h3 > > Slide 32 shows that IO latency is less for XFC.m > >tJ > > However, on slide 33, we see VIOC outperforming XFC for reads to smallD > > files, 1000 block file , 100000 I/Os and VIOC takes 3 minutes 54 > > seconds,# > > XFC takes 4 minutes 14 seconds.- > >-E > > The tables are turned drastically in slide 34.  1.5 million blockt	 > > file,cE > > 300000 I/Os and XFC takes 17 minutes, 36 seconds... VIOC takes 50y > > minutes  > > 24 seconds.e > >pJ > > So what is going on?  You have small files, guess #1.  Second guess is > > thatI > > you somehow aren't doing the same thing.  To report that you had mucho
 > > higher> > > I/Os on the 7.3 runs on the face of it doesn't make sense. > >kJ > > Outline what you are doing, how you are doing it , size of files , XFC	 > > statsg > > before and after, etc. etc.' > >eJ > > Basically, not enough to go on.  By the time there is, you may have it > > figuredi > > out :-)d > >  > > Robh >o > -- > Illegitimis nil carborundum.   ------------------------------   Date: 08 Aug 2001 11:23:19 GMT From: Ruman <ruman@hotmail.com>s Subject: VMS Manualt- Message-ID: <200188-132319-749197@foorum.com>l    Where can I download a good one?   ------D User of http://www.foorum.com/. The best tools for usenet searching.   ------------------------------  % Date: Wed, 08 Aug 2001 16:55:29 +0200n< From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com> Subject: Re: VMS Manualp( Message-ID: <3B7152E1.72CAF12D@home.com>  2 Goto http://www.openvms.compaq.com:8000/index.html   Jan-Erik Sderholm   Ruman wrote: > " > Where can I download a good one?   ------------------------------  $ Date: Wed, 8 Aug 2001 14:18:46 -0400  From: jamese@beast.dtsw.army.mil Subject: Re: vmstar questions 0 Message-ID: <01080814184641@beast.dtsw.army.mil>  C "John McDen" <jj@jj.moc> wrote on Wed, 8 Aug 2001 11:52:58 -0400 ine  <9krnl9$nge$1@bob.news.rcn.net>:  9 > Could somebody tell me what does this errors in vmstar   > means, I really don't3 > understand what this means.o >  > 1. tar: error in SYS$PARSE.3 > 2. *** skipped  $2$DUA8: 9# > [ARCHIVE.ACADDBA.ABFS]10056.OBJ;1. >     *** unsupported format.t  % From the VMS TAR 3.3-9 AAAREADME.TXT:>       Restrictions     ------------  I     Because of diffrences in the Un*x and VMS filesystems, some files may,E     fail to be correctly transferred to/from the tarfile. This can be      caused by:  L     - VMS strong file typing: VMSTAR can only safely tranfer back and forth I     VMS "text" files (rfm=vfc or stream_lf with rat=cr) or VMS fixed size E     record, 512 bytes/record, rat=none files (e.g. .EXE image files).hJ     VMSTAR will skip other file types (this includes .OBJ, they *can't* beB     archived.  Library files may work, but be cautious with them).  : Ed James                           ed.james@telecomsys.com5 TeleCommunications Systems, Inc.   voice 410-295-1919e; 2024 West Street, Suite 300              800-810-0827 x1919 5 Annapolis, MD 21401-3556           fax   410-280-1094o   ------------------------------  % Date: Wed, 08 Aug 2001 20:56:12 +0200e, From: Didier Morandi <Didier.Morandi@gmx.ch> Subject: Re: vmstar questionsf& Message-ID: <3B718B4B.4D0D3C20@gmx.ch>   Jan-Erik Sderholm wrote:  >  > Hi. 3 > (VMSTAR is a port of the "tar" utility from UNIX)a   What is the "tar" utility?   D.   ------------------------------  % Date: Wed, 08 Aug 2001 15:08:59 -0400e- From: JF Mezei <jfmezei.spamnot@videotron.ca>t Subject: Re: vmstar questionse, Message-ID: <3B718E3E.F7C34976@videotron.ca>   Didier Morandi wrote:c5 > > (VMSTAR is a port of the "tar" utility from UNIX)  >  > What is the "tar" utility?   UNIX's equivalent of $BACKUP.p  < (Isn't it also some Klingon dog in the star trek universe ?)   ------------------------------  % Date: Wed, 08 Aug 2001 21:30:57 +0200g, From: Didier Morandi <Didier.Morandi@gmx.ch> Subject: Re: vmstar questions-& Message-ID: <3B719371.9860D8F9@gmx.ch>   JF Mezei wrote:t >  > Didier Morandi wrote: 7 > > > (VMSTAR is a port of the "tar" utility from UNIX)- > >9 > > What is the "tar" utility? >  > UNIX's equivalent of $BACKUP.  > > > (Isn't it also some Klingon dog in the star trek universe ?)  ; Jean-Franois, je ne sais pas ce que je ferais sans toi :^)(   D.   ------------------------------   Date: 8 Aug 2001 19:47:46 GMTT5 From: koehler@bessta.gsfc.nasa.aspm.gov (Bob Koehler)r Subject: Re: vmstar questionse/ Message-ID: <9ks512$nbb$1@skates.gsfc.nasa.gov>r   >g >What is the "tar" utility?o >n  @ It's what you use to keep you're UNIX system from falling apart.  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences CorporationS= GSFC Code 582 Flight Software   | Federal Sector, Civil GroupsI                                 | please remove any ".aspm" when replyingR   ------------------------------   Date: 8 Aug 2001 18:41 CDT' From: carl@gerg.tamu.edu (Carl Perkins)O Subject: Re: vmstar questions , Message-ID: <8AUG200118411058@gerg.tamu.edu>  0 Didier Morandi <Didier.Morandi@gmx.ch> writes... }Jan-Erik Sderholm wrote: }>   }> Hi.4 }> (VMSTAR is a port of the "tar" utility from UNIX) }  }What is the "tar" utility?  }  }D.:    The same thing it's always been.  C If you don't know what it is you won't be able to help the original2G poster, so what difference does it make? (It comes up here often enoughh$ that I am surprised you don't know.)  E To the original poster: As has been pointed out, you can't tar all ofaG the file types that VMS uses. On the other hand, the only reason to taraF files on a VMS system is to transfer them to a Unix system (especiallyI one that doesn't have zip available). Since you can't use a VMS .OBJ fileNK on a Unix system, it doesn't really matter that you can't tar an .OBJ file.o  D If you are not trying to transfer data to a Unix system, then tar is the wrong tool for the job.s   --- Carl   ------------------------------  $ Date: Thu, 9 Aug 2001 09:21:39 +1200& From: A Bonaveidogo <Asena@fsc.com.fj> Subject: Vortex Server? Message-ID: <000001c12050$1e0c9c60$100a640a@Patrick.fsc.com.fj>m  , This is a multi-part message in MIME format.  + ------=_NextPart_000_0001_01C120B4.B3417C60- Content-Type: text/plain;2 	charset="iso-8859-1". Content-Transfer-Encoding: 7bitl  H We're using Vortex Server to get data from VMS to Linux.  Can it be used for Windows?  7) Any idea/suggestions will be appreciated.v    Thanks  f AB  + ------=_NextPart_000_0001_01C120B4.B3417C603 Content-Type: text/html; 	charset="iso-8859-1"k+ Content-Transfer-Encoding: quoted-printabler  > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>      @ <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR></HEAD> <BODY bgColor=3D#ffffff>5 <DIV align=3Dleft><FONT face=3DArial size=3D2><SPAN = " class=3D40581621-08082001>We're=20I using Vortex Server to&nbsp;get data from VMS to Linux.&nbsp; Can it be =l used for=20  Windows?</SPAN></FONT></DIV>6 <DIV align=3Dleft><FONT face=3DArial size=3D2><SPAN=204 class=3D40581621-08082001></SPAN></FONT>&nbsp;</DIV>5 <DIV align=3Dleft><FONT face=3DArial size=3D2><SPAN =   class=3D40581621-08082001>Any=209 idea/suggestions will be appreciated.</SPAN></FONT></DIV>,6 <DIV align=3Dleft><FONT face=3DArial size=3D2><SPAN=204 class=3D40581621-08082001></SPAN></FONT>&nbsp;</DIV>6 <DIV align=3Dleft><FONT face=3DArial size=3D2><SPAN=204 class=3D40581621-08082001>Thanks</SPAN></FONT></DIV>6 <DIV align=3Dleft><FONT face=3DArial size=3D2><SPAN=204 class=3D40581621-08082001></SPAN></FONT>&nbsp;</DIV>6 <DIV align=3Dleft><FONT face=3DArial size=3D2><SPAN=20> class=3D40581621-08082001>AB</SPAN></FONT></DIV></BODY></HTML>  - ------=_NextPart_000_0001_01C120B4.B3417C60--    ------------------------------  % Date: Tue, 07 Aug 2001 21:15:25 -0500p1 From: "David J. Dachtera" <djesys.nospam@fsi.net>hD Subject: Re: You Get What You Pay For, a.k.a., There's No Free Lunch' Message-ID: <3B70A0BD.788EFC45@fsi.net>    Jerry Leslie wrote:i > 2 > David J. Dachtera (djesys.nospam@fsi.net) wrote:K > : I get that here on OSR2. I'll leave come back in a couple of hours, try J > : open Eudora, Netscape or whatever, and it'll just hang. When I finallyK > : do get a response to the three-fingered-salute, it says that the systemeE > : is dangerously low on resources (whatever TF *THAT*'s supposed toe > : mean!).r >  > : Micro$hit - Gotta love it! > @ > "You're riding with Microsoft, the Firestone of the Internet!"  H Bill T. makes a good point - the jury's still out on what combination ofB factors led to the tread separation failures that made the news so prominently...   -- m David J. Dachterai dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/s   ------------------------------   Date: 8 Aug 2001 05:06:21 GMT - From: djweath@attglobal.net (Dave Weatherall)tE Subject: Re: [OT] Market corrections (was Re: Alpha: an invitation toa5 Message-ID: <DTiotGxQ0bj6-pn2-ORdcLSGmLzI5@localhost>-  F On Mon, 6 Aug 2001 21:10:26, "Stephen Fuld" <s.fuld@worldnet.att.net>  wrote:   Very big snip...  I > > One of my first experiences of purchasing in a large company was overnD > > 20 years ago when I needed 2 10M resistors. I can't remember theB > > numbers but by the time it had gone thro' the system, each 25pF > > resistor cost something like 25 quid... Would the company be doingC > > that now? Probably not in the same area, the area requiring 10Mn3 > > resistors would have been out-sourced by now...o >  > N > Anyone can be stupid. The hope is that the stupid things in private industryE > get weeded out by the competition.  That force doesn't exist in the M > government.  Of course, if I needed two 25P resistors, I would pay for themuI > out of my pocket rather than put up with the hassle of dealing with the  > purchasing people :-).  > Indeed, and I have done so a couple of times since. I've been  recompensed in biros :-)  	 Enough OTs   -- t Cheers - Dave.   ------------------------------   End of INFO-VAX 2001.439 ************************