1 INFO-VAX	Fri, 30 May 2003	Volume 2003 : Issue 297       Contents:% Re: advsyscon remote shadow on alpha? # Re: Alpha Upgrade sys$devices.dat ? # Re: Alpha Upgrade sys$devices.dat ?   Re: Another VMS inquirer articleD Re: Block IO question for RMS files ... Detecting EOF for empty fileD Re: Block IO question for RMS files ... Detecting EOF for empty fileD Re: Block IO question for RMS files ... Detecting EOF for empty fileP Block IO question for RMS files ... Detecting EOF for empty file with deleted reP Re: Block IO question for RMS files ... Detecting EOF for empty file with deleteP Re: Block IO question for RMS files ... Detecting EOF for empty file with deleteP Re: Block IO question for RMS files ... Detecting EOF for empty file with deleteP Re: Block IO question for RMS files ... Detecting EOF for empty file with deleteP Re: Block IO question for RMS files ... Detecting EOF for empty file with deleteP Re: Block IO question for RMS files ... Detecting EOF for empty file with deleteP Re: Block IO question for RMS files ... Detecting EOF for empty file with delete! Calculating semesters with DCL... % Re: Calculating semesters with DCL... % Re: Controller for VAXStation 4000 90 ( Re: DECUS Europe Amsterdam: Days #1 & #2( Re: DECUS Europe Amsterdam: Days #1 & #2 ES45 AGP Re: ES45 AGP Re: ES45 AGP Re: Firmware Upgrade Re: FREE TO A GOOD HOME 
 Help with VMS  Re: Help with VMS  Re: Help with VMS  Re: Help with VMS  Re: Help with VMS  Re: Help with VMS ' Re: Hobbyist seeks generic SIMM vendors  Re: Install Directory  Re: Install Directory  Re: Install Directory  Re: Install Directory  Re: Install Directory  Re: Install Directory  RE: Install Directory  Re: Invalid Disk format  Re: Invalid Disk format  JAVA appears to hang on OpenVMS # Re: JAVA appears to hang on OpenVMS , Re: Mystery Alpha CPUS, what do they fit in?, Re: Mystery Alpha CPUS, what do they fit in?, Re: Mystery Alpha CPUS, what do they fit in?  Needed, history of startup files' Needing to upgrade from AXP VMSv7.1-1h2  Re: New MiniMerge capability Re: New MiniMerge capability3 Re: NT: son of VMS? (was Re: Portents of VMS death)  Re: OSU http_server errorpage  Re: Portents of VMS death  Re: Portents of VMS death  Re: Portents of VMS death  Re: Portents of VMS death 7 Re: Reading CD-R burned on a Window system on an Alpha? 2 Re: Skil Saw? (was - Re: New MiniMerge capability)) Re: Stopping a que other then a print que ! RE:  StorageTek l700 on VMS 7.3-1 ! Re:  StorageTek l700 on VMS 7.3-1   Re: StorageTek l700 on VMS 7.3-1  Re: StorageTek l700 on VMS 7.3-1  Re: StorageTek l700 on VMS 7.3-1  Re: StorageTek l700 on VMS 7.3-1# Re: What's happened to Alan Greig ?   F ----------------------------------------------------------------------  % Date: Fri, 30 May 2003 12:47:12 +1000  From: "Pip" <pip@ti.nl0.com>. Subject: Re: advsyscon remote shadow on alpha?< Message-ID: <3ed6c626$0$16256$afc38c87@news.optusnet.com.au>  H We use the Remote Shadow Option on Alpha OpenVMS up to V7.3-1 just fine.@ Yes, I believe it does intercept start-io, because it used to beJ incompatible with raxco's perfect-cache, which did intercept start-io. TheI remote shadow device appears as a separate device, which can be added and $ removed from the shadow set at will.G Yes, we did encounter some problem with the XFC cache changes, but they  fixed them a year or more ago.H We particularly liked the out-of-sync tolerance, so that users would notK suffer a performance hit waiting for I/O completion. (We run it over a WAN,  rather than a gigabit LAN)   hth  Pip     ( "Everhart" <ge@gce.com> wrote in message% news:bb0vv6$t05$1@bob.news.rcn.net... C > If they intercept start-io and don't have a separate user visible D > shadowed device, I would treat them with great care. While I don'tE > know details, I have heard of and encountered enough driver changes E > and functional changes with the new XFC cache that I feel skeptical C > about that operation. If you have to set up a new device and have K > to point a logical at that device instead of the old name, it is a little L > harder to set up remote shadow. On the other hand you are not dependent onH > a synchronization environment which is handling numerous new functionsJ > and is increasingly hard to follow. As I wrote earlier, i tend to preferL > the Bearcomp approach. For a commercial user the issue is whether BearcompG > still sells it. Remote shadowing with a local buffer file that serves K > to hold written blocks that have not yet made it to the remote end is not H > conceptually all that hard, just takes some care in the writing of theH > buffer, but would take a little work to concoct it out of vddriver andL > some daemons, zrdriver, or lddriver. Nobody has done that in free software > AFAIK. > Glenn Everhart >  > Hal Kuff wrote:  >    ------------------------------   Date: 29 May 03 11:15:37 PST From: mckinneyj@cpva.saic.com , Subject: Re: Alpha Upgrade sys$devices.dat ?( Message-ID: <h9+1hIEWSgBn@cpva.saic.com>  / In article <uJqBa.72$oD6.3572@news.on.tac.net>, 1  "Jerry Alan Braga" <jabraga@flanagan.ca> writes: M > We are upgrading from an Alpha1200 to a DS25. The system is configured in a L > cluster with another AS1200 node and an HSZ70 controller with quorum disk. > 
 > Current: > =====   > Node REN = AS1200 (dual 5/533)% > Node STIMPY = AS1200 (single 5/400)  >  > After: > ==== > Node REN = DS25 # > Node STIMPY = AS1200 (dual 5/533) M > Other AS1200 to moved offsite for disaster and fresh standalone VMS install  >  > Here are the issues: > < > The Alpha1200's see the HSZ70 as pkb devices via the KZPBA5 > The DS25 see the HSZ70 as pka devices via the KZPBA  > G > I cannot change this and here is the issue.  The sys$devices.dat file  > contains following entries >  > 2 > ! CLUSTER_CONFIG created  3-JUL-1998 21:49:41.68 >  > [Port REN$PKA] > allocation class = 31 > ******************************** END OF PROGRAM " > ********************************2 > ! CLUSTER_CONFIG updated  3-JUL-1998 22:29:23.72 >  > [Port STIMPY$PKB]  > allocation class = 3 >  > G > According to this I have to change the [PortREN$PKB] to [PortREN$PKA] K > I have been told I cannot just change the file before shutdown to the new M > one and then boot DS25 with new file.  I have to use cluster config on boot ! > conversational.  What is this ?  >  > !! Thanks in advance !!  >  >   E I've never encountered any problems with just editing SYS$DEVICES.DAT 5 and rebooting. A conversational boot is not required.    --   - Jim    ------------------------------   Date: 29 MAY 2003 20:13:00 GMT4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher), Subject: Re: Alpha Upgrade sys$devices.dat ?6 Message-ID: <29MAY03.20130078@thuria.waisman.wisc.edu>  F In a previous article, "Jerry Alan Braga" <jabraga@flanagan.ca> wrote:M ->We are upgrading from an Alpha1200 to a DS25. The system is configured in a L ->cluster with another AS1200 node and an HSZ70 controller with quorum disk. -> ...G ->I cannot change this and here is the issue.  The sys$devices.dat file  ->contains following entries ->   ->  2 ->! CLUSTER_CONFIG created  3-JUL-1998 21:49:41.68 ->   ->[Port REN$PKA] ->allocation class = 31 ->******************************** END OF PROGRAM " ->********************************2 ->! CLUSTER_CONFIG updated  3-JUL-1998 22:29:23.72 ->   ->[Port STIMPY$PKB]  ->allocation class = 3 ->  G ->According to this I have to change the [PortREN$PKB] to [PortREN$PKA] K ->I have been told I cannot just change the file before shutdown to the new M ->one and then boot DS25 with new file.  I have to use cluster config on boot ! ->conversational.  What is this ?   I The supported way to make the change would be to do a conversational boot  and issue the SYSBOOT commands:   * 	SYSBOOT> SET/CLASS PKB		! Delete port PKB@ 	SYSBOOT> SET/CLASS PKA 3	! Add port PKA with allocation class 3  - See section 4.3 of the System Managers Manual   E You can of course edit the file yourself - just make sure it's right.    --G -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison 7 --                karcher.nomorespam@waisman.wisc.edu      ------------------------------  % Date: Thu, 29 May 2003 20:11:19 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> ) Subject: Re: Another VMS inquirer article & Message-ID: <3ED6AFB7.159E8F9@fsi.net>   John Smith wrote:  > > > "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message# > news:3ED5602F.DD0B7710@fsi.net... 
 > > [snip]E > > Folks here can attest - I cut a *LOT* of crooked furrows, but I'm  > not  > > always wrong, either.  > G > If you were an employee of 'The New hp', not only would you be wrong, B > you'd likely be fired if you didn't toe the party line. I almostH > wonder if there isn't a department inside The New hp with the initials > NKVD or KGB.  5 Kevin G. Barkes? Wonder what he's up to these days...    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------    Date: 29 May 2003 19:02:49 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) M Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file 3 Message-ID: <4GTqTUCDyFzT@eisner.encompasserve.org>   S In article <bb6016$d3g$1@news1.tilbu1.nb.home.nl>, Dirk Munk <munk@home.nl> writes:  > Dann Corbit wrote:  M >> I have searched high and low for the book "RMS Internals" but it cannot be  >> had any more. > 5 > The VMS books have been a bit reorganized it seems. K > Did you check the "OpenVMS Record Management Services Reference Manual" ?   H The "OpenVMS Record Management Services Reference Manual" is part of the VMS Documentation.  ; "RMS Internals" was a Digital Press book (by Kirby McCoy?).    ------------------------------  % Date: Thu, 29 May 2003 17:22:22 -0700 ' From: "Dann Corbit" <dcorbit@connx.com> M Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file , Message-ID: <bb687v01e5n@enews3.newsguy.com>  : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:4GTqTUCDyFzT@eisner.encompasserve.org... > > In article <bb6016$d3g$1@news1.tilbu1.nb.home.nl>, Dirk Munk <munk@home.nl> writes: > > Dann Corbit wrote: > L > >> I have searched high and low for the book "RMS Internals" but it cannot be > >> had any more. > > 7 > > The VMS books have been a bit reorganized it seems. K > > Did you check the "OpenVMS Record Management Services Reference Manual"  ?  > J > The "OpenVMS Record Management Services Reference Manual" is part of the > VMS Documentation.  A I have this document.  If my answer is in there, I can't find it.   = > "RMS Internals" was a Digital Press book (by Kirby McCoy?).   $ Yes, I know.  I can't find the book. --  0 C-FAQ: http://www.eskimo.com/~scs/C-faq/top.html$  "The C-FAQ Book" ISBN 0-201-84519-9H C.A.P. FAQ: ftp://cap.connx.com/pub/Chess%20Analysis%20Project%20FAQ.htm   ------------------------------    Date: 29 May 2003 20:16:16 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) M Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file 3 Message-ID: <WCAcmFL+sNYu@eisner.encompasserve.org>   V In article <bb687v01e5n@enews3.newsguy.com>, "Dann Corbit" <dcorbit@connx.com> writes:< > "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message/ > news:4GTqTUCDyFzT@eisner.encompasserve.org... ? >> In article <bb6016$d3g$1@news1.tilbu1.nb.home.nl>, Dirk Munk  > <munk@home.nl> writes: >> > Dann Corbit wrote:  >>M >> >> I have searched high and low for the book "RMS Internals" but it cannot  > be >> >> had any more.  >> >8 >> > The VMS books have been a bit reorganized it seems.L >> > Did you check the "OpenVMS Record Management Services Reference Manual" > ?  >>K >> The "OpenVMS Record Management Services Reference Manual" is part of the  >> VMS Documentation.  > C > I have this document.  If my answer is in there, I can't find it.  > > >> "RMS Internals" was a Digital Press book (by Kirby McCoy?). > & > Yes, I know.  I can't find the book.  2 But apparently Dirk did not (or had forgotten it).   ------------------------------  % Date: Thu, 29 May 2003 11:47:22 -0700 ' From: "Dann Corbit" <dcorbit@connx.com> Y Subject: Block IO question for RMS files ... Detecting EOF for empty file with deleted re , Message-ID: <bb5kl002fa8@enews2.newsguy.com>  E I am using Block IO.  The file has no records in it, but it has pages 4 allocated.  ANALYZE/RMS shows no errors in the file.  K After a sys$read, I get sys$read a status of 65537  and a DataSize of 32256  (non-zero). J The End Of Data is less than or equal to the Next Free Offset, and yet theI reported Key Length  is greater than the Total Key Size.  In reality, the - file is empty -- no valid records live there.   K I only get this problem sometimes.  I am sure that there is some simple way 5 to detect that the file is really empty.  What is it?    P.S.J I have searched high and low for the book "RMS Internals" but it cannot be
 had any more.  --  0 C-FAQ: http://www.eskimo.com/~scs/C-faq/top.html$  "The C-FAQ Book" ISBN 0-201-84519-9H C.A.P. FAQ: ftp://cap.connx.com/pub/Chess%20Analysis%20Project%20FAQ.htm   ------------------------------    Date: 29 May 2003 14:43:21 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) Y Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file with delete 3 Message-ID: <RBdX77W3HzOB@eisner.encompasserve.org>   V In article <bb5kl002fa8@enews2.newsguy.com>, "Dann Corbit" <dcorbit@connx.com> writes:G > I am using Block IO.  The file has no records in it, but it has pages 6 > allocated.  ANALYZE/RMS shows no errors in the file. > M > After a sys$read, I get sys$read a status of 65537  and a DataSize of 32256 
 > (non-zero). L > The End Of Data is less than or equal to the Next Free Offset, and yet theK > reported Key Length  is greater than the Total Key Size.  In reality, the / > file is empty -- no valid records live there.  > M > I only get this problem sometimes.  I am sure that there is some simple way 7 > to detect that the file is really empty.  What is it?   F Since you talk about Total Key Size, I gather this is an indexed file.  L > I have searched high and low for the book "RMS Internals" but it cannot be > had any more.   D I believe it would take more than that book to replicate all the RMS> operations required to interpret indexed files using Block IO.   ------------------------------  % Date: Thu, 29 May 2003 17:10:06 -0700 ' From: "Dann Corbit" <dcorbit@connx.com> Y Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file with delete , Message-ID: <bb67hu01d58@enews3.newsguy.com>  + "Dirk Munk" <munk@home.nl> wrote in message , news:bb6016$d3g$1@news1.tilbu1.nb.home.nl... > Dann Corbit wrote:I > > I am using Block IO.  The file has no records in it, but it has pages 8 > > allocated.  ANALYZE/RMS shows no errors in the file. > > I > > After a sys$read, I get sys$read a status of 65537  and a DataSize of  32256  > > (non-zero). J > > The End Of Data is less than or equal to the Next Free Offset, and yet the I > > reported Key Length  is greater than the Total Key Size.  In reality,  the 1 > > file is empty -- no valid records live there.  > > K > > I only get this problem sometimes.  I am sure that there is some simple  way 9 > > to detect that the file is really empty.  What is it?  > >  > > P.S.K > > I have searched high and low for the book "RMS Internals" but it cannot  be > > had any more.  > 5 > The VMS books have been a bit reorganized it seems. K > Did you check the "OpenVMS Record Management Services Reference Manual" ?   J Yes.  But those books are a bit quiet when it comes to block IO internals. I already know to check for  98938 (end of file detected) 98994 (record not found)% 99932 (invalid record's file address) . 99732 (invalid record number key or key value)  . But in this case, the seek is returning 65537. --  0 C-FAQ: http://www.eskimo.com/~scs/C-faq/top.html$  "The C-FAQ Book" ISBN 0-201-84519-9H C.A.P. FAQ: ftp://cap.connx.com/pub/Chess%20Analysis%20Project%20FAQ.htm   ------------------------------    Date: 29 May 2003 20:15:40 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) Y Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file with delete 3 Message-ID: <ysTcX7mJ7PSO@eisner.encompasserve.org>   V In article <bb67hu01d58@enews3.newsguy.com>, "Dann Corbit" <dcorbit@connx.com> writes:  0 > But in this case, the seek is returning 65537.  4 $ search sys$library:starlet.req rms/match=and,65537 literal RMS$_SUC = 65537;  literal RMS$_NORMAL = 65537; $    ------------------------------  % Date: Thu, 29 May 2003 19:13:33 -0700 ' From: "Dann Corbit" <dcorbit@connx.com> Y Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file with delete , Message-ID: <bb6epc01o6p@enews3.newsguy.com>  : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:ysTcX7mJ7PSO@eisner.encompasserve.org... < > In article <bb67hu01d58@enews3.newsguy.com>, "Dann Corbit" <dcorbit@connx.com> writes:  > 2 > > But in this case, the seek is returning 65537. > 6 > $ search sys$library:starlet.req rms/match=and,65537 > literal RMS$_SUC = 65537;  > literal RMS$_NORMAL = 65537; > $   B Yes.  That's just the problem.  The read is returning success, and' indicating thousands of bytes returned. I But there is actually no data and an attempt to decompress the index goes  *bonk*.  --  0 C-FAQ: http://www.eskimo.com/~scs/C-faq/top.html$  "The C-FAQ Book" ISBN 0-201-84519-9H C.A.P. FAQ: ftp://cap.connx.com/pub/Chess%20Analysis%20Project%20FAQ.htm   ------------------------------  + Date: Fri, 30 May 2003 02:54:29 +0000 (UTC) 7 From: moroney@world.std.spaamtrap.com (Michael Moroney) Y Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file with delete ( Message-ID: <bb6h55$rhi$2@pcls4.std.com>  ) "Dann Corbit" <dcorbit@connx.com> writes:   K >Yes.  But those books are a bit quiet when it comes to block IO internals.  >I already know to check for >98938 (end of file detected)  >98994 (record not found) & >99932 (invalid record's file address)/ >99732 (invalid record number key or key value)   / >But in this case, the seek is returning 65537.   6 That is a normal status - it did what you asked of it.  F Probably better to operate on the low bit(s) of the status code rather; than hard-coding in every response you think it can return.  --   -Mike    ------------------------------  % Date: Thu, 29 May 2003 19:57:56 -0700 ' From: "Dann Corbit" <dcorbit@connx.com> Y Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file with delete , Message-ID: <bb6hbl01s6q@enews3.newsguy.com>  D "Michael Moroney" <moroney@world.std.spaamtrap.com> wrote in message" news:bb6h55$rhi$2@pcls4.std.com...+ > "Dann Corbit" <dcorbit@connx.com> writes:  > B > >Yes.  But those books are a bit quiet when it comes to block IO
 internals. > >I already know to check for > >98938 (end of file detected)  > >98994 (record not found) ( > >99932 (invalid record's file address)1 > >99732 (invalid record number key or key value)  > 1 > >But in this case, the seek is returning 65537.  > 8 > That is a normal status - it did what you asked of it.  H I know what it means.  But it is a lie.  The function says it read a bigL block of data, but the file is empty.  Probably some field will tell me whatC is happening.  I was hoping someone might know where I should look.   H > Probably better to operate on the low bit(s) of the status code rather= > than hard-coding in every response you think it can return.   E I have done that.  The above codes are special cases I want to handle 1 separately.  They are related to EOF on a lookup.  --  0 C-FAQ: http://www.eskimo.com/~scs/C-faq/top.html$  "The C-FAQ Book" ISBN 0-201-84519-9H C.A.P. FAQ: ftp://cap.connx.com/pub/Chess%20Analysis%20Project%20FAQ.htm   ------------------------------  % Date: Thu, 29 May 2003 23:58:36 +0200  From: Dirk Munk <munk@home.nl>Y Subject: Re: Block IO question for RMS files ... Detecting EOF for empty file with delete 2 Message-ID: <bb6016$d3g$1@news1.tilbu1.nb.home.nl>   Dann Corbit wrote:G > I am using Block IO.  The file has no records in it, but it has pages 6 > allocated.  ANALYZE/RMS shows no errors in the file. > M > After a sys$read, I get sys$read a status of 65537  and a DataSize of 32256 
 > (non-zero). L > The End Of Data is less than or equal to the Next Free Offset, and yet theK > reported Key Length  is greater than the Total Key Size.  In reality, the / > file is empty -- no valid records live there.  > M > I only get this problem sometimes.  I am sure that there is some simple way 7 > to detect that the file is really empty.  What is it?  >  > P.S.L > I have searched high and low for the book "RMS Internals" but it cannot be > had any more.   3 The VMS books have been a bit reorganized it seems. I Did you check the "OpenVMS Record Management Services Reference Manual" ?    ------------------------------    Date: 29 May 2003 18:56:20 -0700- From: contracer11@uol.com.br (Shiva MahaDeva) * Subject: Calculating semesters with DCL...< Message-ID: <ddf392ea.0305291756.4f8e974@posting.google.com>   Giving two dates like this:   6   10-nov-2000 -  23-jul-2001   ->  first semester/2001  6   15-dec-2002 -  05-aug-2003   ->  first semester/2003  7   05-may-2002 -  28-jan-2003   ->  second semester/2002   7   11-jun-2000 -  01-jan-2001   ->  second semester/2000      A  How could I calculate this using a procedure ? (first or second      semester , using two dates ? )     Thanks in advance...    ------------------------------  % Date: Thu, 29 May 2003 21:40:07 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> . Subject: Re: Calculating semesters with DCL...' Message-ID: <3ED6C487.3FF47CA3@fsi.net>    Shiva MahaDeva wrote:  >  > Giving two dates like this:  > 8 >   10-nov-2000 -  23-jul-2001   ->  first semester/2001 > 8 >   15-dec-2002 -  05-aug-2003   ->  first semester/2003 > 9 >   05-may-2002 -  28-jan-2003   ->  second semester/2002  > 9 >   11-jun-2000 -  01-jan-2001   ->  second semester/2000  >  > B >  How could I calculate this using a procedure ? (first or second > ! >  semester , using two dates ? )   G Read up on the F$CVTIME() lexical function. Start with HELP Lex F$CVTI, / then check the DCL Dictionary for more details.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Thu, 29 May 2003 12:45:43 -0500 , From: Bob Blunt <robert.blunt@hp.nospam.com>. Subject: Re: Controller for VAXStation 4000 90, Message-ID: <3ed64b32$1@usenet01.boi.hp.com>   Justin McMichael wrote:  > Hi,  > I > Our large systems (mainframe) group is trying to build a duplicate of a L > VAXStation 4000 90 for use as a backup for their SMS OpenLink 21 interface > box. > K > Their vendor was able to get them a box apparently with everything except I > for the "Asynchronous serial to IBM 3745" controller card.  I put it in J > quotes because I frankly don't know if that is even technically correct.L > You see, I am not the VMS guy.  In fact I am far from it.  All I am reallyA > trying to do is help out by doing a bit of searching on my own.  > J > I have read quite a bit about the 4000 90 on the web, but nowhere have IJ > found any mention of such a controller card.  I have found references toL > synchronous controllers, but nothing specific enough to figure out if I am > barking up the right tree. > K > The card itself (as far as I can tell) is definitely plugged into a riser 1 > connector and is not attached to the mainboard.  > 8 > Does anyone here know what exactly we are looking for? >  > Justin McMichael > Riverside Health System $ > (Remove the numbers from my email) >  >  >  > @ > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----C > http://www.newsfeeds.com - The #1 Newsgroup Service in the World! @ > -----==  Over 80,000 Newsgroups - 16 Different Servers! =-----  I Justin, besides DSW21, you could search for 54-20377-01.  From Google, I   found the following:  ( http://www.workstation.net/digital.shtml  D They list the item as in stock, but I'm not sure of the date it was : posted.  An 800 number is listed, might be worth a call...   bob    ------------------------------    Date: 29 May 2003 15:52:05 -07001 From: keithparris_NOSPAM@yahoo.com (Keith Parris) 1 Subject: Re: DECUS Europe Amsterdam: Days #1 & #2 = Message-ID: <cf15391e.0305291452.6a36df48@posting.google.com>   h "Hans Vlems" <hvlems.nieuw@zonnet.nl> wrote in message news:<badu4d$se3kt$1@ID-143435.news.dfncis.de>...L > the total event had about 900 registered participants which is an all time > low for a DECUS-Europe event.   F All-time low???  I heard the attendance in Amsterdam was roughly twice that of Lyon last year.   D Also remember that the ITUG (Tandem/NonStop) folks were meeting in aE different hotel for all but a (few?) keynote session(s), so they were ) not visible at the RAI Conference Center.    ------------------------------  % Date: Thu, 29 May 2003 19:53:30 -0400 ( From: David Froble <davef@tsoft-inc.com>1 Subject: Re: DECUS Europe Amsterdam: Days #1 & #2 , Message-ID: <3ED69D7A.1030206@tsoft-inc.com>   Keith Parris wrote:   j > "Hans Vlems" <hvlems.nieuw@zonnet.nl> wrote in message news:<badu4d$se3kt$1@ID-143435.news.dfncis.de>... > L >>the total event had about 900 registered participants which is an all time >>low for a DECUS-Europe event.  >> > H > All-time low???  I heard the attendance in Amsterdam was roughly twice > that of Lyon last year.  > F > Also remember that the ITUG (Tandem/NonStop) folks were meeting in aG > different hotel for all but a (few?) keynote session(s), so they were + > not visible at the RAI Conference Center.  >   
 ITUG <> DECUS   F I think that Hans was interested in attendees with an interest in VMS.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------   Date: 29 May 2003 21:20:58 GMT4 From: Chip Coldwell <coldwell@frank.harvard.invalid> Subject: ES45 AGP / Message-ID: <bb5tjq$mu7$1@news.fas.harvard.edu>   D The Quick Specs for the ES45 mention both an AGP slot and OpenVMS asB an operating system option.  Does this imply that there is OpenVMS support for AGP video cards?   Chip   --   Charles  M. "Chip" Coldwell  "Turn on, log in, tune out"    ------------------------------  % Date: Thu, 29 May 2003 23:51:55 +0200  From: Dirk Munk <munk@home.nl> Subject: Re: ES45 AGP 2 Message-ID: <bb5vkn$aqs$1@news1.tilbu1.nb.home.nl>   Chip Coldwell wrote:F > The Quick Specs for the ES45 mention both an AGP slot and OpenVMS asD > an operating system option.  Does this imply that there is OpenVMS > support for AGP video cards? >  > Chip > P Yes, the ATI Radeon 7500 AGP is supported in VMS 7.3-1 with the latest graphics 0 patch. The PCI version is supported in the DS10.   ------------------------------  % Date: Thu, 29 May 2003 21:09:09 -0400 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: ES45 AGP L Message-ID: <rdeininger-2905032109090001@user-uinj59k.dialup.mindspring.com>  F In article <bb5vkn$aqs$1@news1.tilbu1.nb.home.nl>, munk@home.nl wrote:   >Chip Coldwell wrote: G >> The Quick Specs for the ES45 mention both an AGP slot and OpenVMS as E >> an operating system option.  Does this imply that there is OpenVMS  >> support for AGP video cards?  >>   >> Chip  >>  G >Yes, the ATI Radeon 7500 AGP is supported in VMS 7.3-1 with the latest 	 graphics  1 >patch. The PCI version is supported in the DS10.   M IIRC, there is also an AGP version of the VX1 card that is supported in ES45.    ------------------------------  % Date: Thu, 29 May 2003 21:23:23 -0400 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: Firmware Upgrade L Message-ID: <rdeininger-2905032123230001@user-uinj59k.dialup.mindspring.com>  J In article <01KWGHCQEVGYAM3M2Q@sysdev.deutsche-boerse.com>, Phillip Helbig+ <HELBPHI@sysdev.deutsche-boerse.com> wrote:   K >> >What is the latest version of the firmware available for each of these  G >> >machines?  Is there a list with such information, preferably in an  J >> >easily digestible form, on the web somewhere?  If 5.9 or later is not I >> >available, what are the chances of running 7.3-1 on these machines?    >> >Anyone done so already?  >>  $ >> V7.3-1 runs fine on both systems. > 9 >That is excellent news.  I hope that 7.3-2 will as well!  > M >> Alpha firmware version numbers vary a lot from one system to another.  The < >> minimum and recommended FW versions are system-dependent. >>  I >> You can see the FW version of a running VMS system via the SDA command L >> CLUE CONFIG.  The "Console Vers" field is the SRM console. The "PAL Code"F >> field is the VMS PALcode version.  These two numbers are completelyF >> independent of each other.  VMS generally worries about the console >> version field.  > 0 >What does F$GETSYI("CONSOLE_VERSION") indicate?  , It looks to me like the SRM Console version.  M >> On recent VMS versions, SHOW CPU/FULL gives much of the same information.  I >> There are a few other ways a well, which I won't try to get right from 
 >> memory. >>  M >> The most recent SRM version for the DEC 3000 family of systems is V7.0.  I K >> don't know the most recnet for the Alphastation 255/233.  Whatever is on & >> the FW web site is the most recent. > E >Obviously, I am confused.  For example, the "Alpha Systems Firmware  H >Update V6.2 Release Notes Overview" (this is in the CD packaging) says: > G >   Starting with the V6.1 Alpha Systems Firmware Update CD, files for  H >   systems that have not had a new firmware release for at least three J >   years will be dropped from the CD.  Firmware images for the following # >   systems are no longer included:  > $ >It then lists ALPHA255 and DEC3000. >  >This CD is from May 2002.  D The FW CD got too full, so the unchanging FW is not included after 3H years.  But the latest is still available from the web site, even if its not on the CD.    H >It also has a list of "Minimum Acceptable FW CD Versions for Recent OS H >Releases".  For VMS 7.3 it lists FW CD V5.9.  Obviously, it is talking + >about the version of the firmware CD here.  > J >Thus, apparently the last firmware release for the 255 and 3000 was 1999 H >or before.  If you say that 7.3-1 runs fine on these systems, then the A >V5.9 firmware CD must have contained firmware for these systems.   H The revision table included with the FW CD includes models for which theG FW is NOT on the CD.  But the table would have been correct when the CD  was issued.   E >Let's ask the question another way: what is the last version of VMS  H >which will run on the 3000?  The 255?  7.3-2?  8.something?  (I'm just / >looking for educated guesses here, of course.)   I The last version that will run isn't known yet.  All VMS versions to date B are still supported on these systems, as is listed in the VMS SPD.   ------------------------------   Date: 29 May 2003 17:54 CDT ' From: carl@gerg.tamu.edu (Carl Perkins)   Subject: Re: FREE TO A GOOD HOME- Message-ID: <29MAY200317544831@gerg.tamu.edu>   1 Kilgallen@SpamCop.net (Larry Kilgallen) writes... X }In article <28MAY200318270962@gerg.tamu.edu>, carl@gerg.tamu.edu (Carl Perkins) writes:4 }> Kilgallen@SpamCop.net (Larry Kilgallen) writes...u }> }In article <XXHgubKQctvR@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: ^ }> }> In article <1030527195925.2916C-100000@Ives.egh.com>, John Santos <JOHN@egh.com> writes: }> }>>  D }> }>> There are lots of farms in the area; maybe the local electricC }> }>> company is more inclined to put in 3-phase because some farm  }> }>> equipment requires it?  }> }> I }> }>    In this reguard farms are more like any small business than just K }> }>    another home.  My grandfather had lots of three phase equipment on L }> }>    his farm.  Also there was a transformer on a pole on the farm, withK }> }>    it own emergency cutoff (accessible to the fire department), just   }> }>    to serve the farm.  }> }  N }> }How did they make it accessible to the fire department but not to vandals. }>  ; }> It may have something to do with a farmer and a shotgun.  }>  L }> (How did you make your entire house accessible to the fire department but }> not to vandals?)s } H }I put a lock on my house, and the fire department may have to break in. } ? }I am forbidden to put a lock on the power cutout for my house.c  G How well does that lock on your house prevent some vandal from throwingqE a brick through your window or painting things across the front of iteA or lighting it on fire so that the fire departement needs access?t  E Vandals have access to your house, probably just as much as they havelD access to the power cutoff (unless you live in a walled compound, in+ which case the access is reduced somewhat).    --- Carl   ------------------------------    Date: 29 May 2003 17:11:33 -0700) From: machinegunkelley@hotmail.com (Mark)e Subject: Help with VMS= Message-ID: <b3d4f0be.0305291611.1312ad0f@posting.google.com>c  B We currently are running a microvax 3100/80 and decide it would beE good to move to a faster computer so we purchased a microvax 3100/98.eD We thought that we could just restore our nightly image to the driveF of the new unit and with a few minor adjustments to the systartup file we would be off and running." Well we have a few minor problems.; We are running VMS 5.5-2 unlimited users with the Y2K patche  B A. when we boot we get some errors about our license not being forB this computer.(we are keeping the old unit so I didnt really see aF license problem with using it on this machine only.) is there a way toE fix this license problem without a big hassle? I realy do not want to > have to reinstall anything as my knowledge of VMS is very very limited.  ? B. we need to fix the systartup_vms file but since this file islE causing a boot problem I have to boot to sysboot and do a set/startupaD opa0: when in this mode I cant find a text editor to use I type EDTC, but get an error like it cant find the file?  ; C. We bought this unit with three 4 gig drives only one wasSD initialized. I looked for a way to initialize them when I was at theC standalone prompt but I dont think this can be done from here, alsoi@ tried when in the opa0: mode but that didnt seem to work either.  C D. I called HP(not much help) and was told that VMS 5.5-2 would not C work on this machine, that it had to be 5.5-2H4 or 6.1 and that youMF could no longer buy either of these. I have heard of a patch for 5.5-2, to make it H4 anyone know where to get this?    #  Any help would be much appreciatedu       Mark   ------------------------------  % Date: Thu, 29 May 2003 20:38:16 -0500T1 From: "David J. Dachtera" <djesys.nospam@fsi.net>3 Subject: Re: Help with VMS' Message-ID: <3ED6B608.46D0E33F@fsi.net>1   Mark wrote:p > D > We currently are running a microvax 3100/80 and decide it would beG > good to move to a faster computer so we purchased a microvax 3100/98.PF > We thought that we could just restore our nightly image to the driveH > of the new unit and with a few minor adjustments to the systartup file > we would be off and running.$ > Well we have a few minor problems.= > We are running VMS 5.5-2 unlimited users with the Y2K patchp > D > A. when we boot we get some errors about our license not being forD > this computer.(we are keeping the old unit so I didnt really see aH > license problem with using it on this machine only.) is there a way toG > fix this license problem without a big hassle? I realy do not want toe@ > have to reinstall anything as my knowledge of VMS is very very
 > limited.  E Try SHOW LICENSE/UNITS on both machines. That'll tell you whether youa> need more license units in the VMS base license (probably do).  A > B. we need to fix the systartup_vms file but since this file iseG > causing a boot problem I have to boot to sysboot and do a set/startupdF > opa0: when in this mode I cant find a text editor to use I type EDTC. > but get an error like it cant find the file?   Try doing this, instead:   >>> b/1    SYSBOOT>  set startup_p1 "MIN"   SYSBOOT>  set writesysparams 0   SYSBOOT>  cont  D This performs a "minimal" startup. SYSTARTUP_V5 is not executed in aH minimal startup. You will likely only be able to log in from the console (OPA0:).  = > C. We bought this unit with three 4 gig drives only one wassF > initialized. I looked for a way to initialize them when I was at theE > standalone prompt but I dont think this can be done from here, alsomB > tried when in the opa0: mode but that didnt seem to work either.  G Stand-alone BACKUP provides only BACKUP commands. If you have a CD-ROM,t. boot from any newer CD, root 1: >>> B/10000000  A The displays are self-explanatory. Ignore any boot-time messages.   E > D. I called HP(not much help) and was told that VMS 5.5-2 would notvE > work on this machine, that it had to be 5.5-2H4 or 6.1 and that youfH > could no longer buy either of these. I have heard of a patch for 5.5-2. > to make it H4 anyone know where to get this?  F V5.5-2H4 was a hardware release that included support for that machineG (and I think others, also). I don't think I have it, but I do have V6.2<
 and later.   -- e David J. Dachtera" dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/r   ------------------------------  # Date: Fri, 30 May 2003 02:43:59 GMT 4 From: "Mark Buda" <buda@tabasco.zko.dec.no.spam.com> Subject: Re: Help with VMS2 Message-ID: <PzzBa.1648$m73.1190@news.cpqcorp.net>  6 "Mark" <machinegunkelley@hotmail.com> wrote in message7 news:b3d4f0be.0305291611.1312ad0f@posting.google.com...s  D > A. when we boot we get some errors about our license not being forD > this computer.(we are keeping the old unit so I didnt really see aH > license problem with using it on this machine only.) is there a way toG > fix this license problem without a big hassle? I realy do not want to @ > have to reinstall anything as my knowledge of VMS is very very
 > limited.  H The number of units for your old machine is not enough to run on the newB machine.  You need to have your new machine legally licensed (yourH system may be so or it may not be) and have enough units for the license
 OPENVMS-ALPHAt  E > D. I called HP(not much help) and was told that VMS 5.5-2 would notoE > work on this machine, that it had to be 5.5-2H4 or 6.1 and that you H > could no longer buy either of these. I have heard of a patch for 5.5-2. > to make it H4 anyone know where to get this?  G It sounds as if hardware support for the new machine is not in your oldt* version.  You will likely have to upgrade.   mark   ------------------------------  % Date: Thu, 29 May 2003 22:22:55 -0400 * From: JF Mezei <jfmezei.spamnot@istop.com> Subject: Re: Help with VMS) Message-ID: <3ED6C06B.A299FD4B@istop.com>s   Mark wrote:?= > We are running VMS 5.5-2 unlimited users with the Y2K patcha > D > A. when we boot we get some errors about our license not being forD > this computer.(we are keeping the old unit so I didnt really see a  N The old licenses were specific to machine ratings. Newer licenses are specificT to classes of machines, but are only supported on newer versions of VMS as I recall.  M If your VMS licence (LICENSE LIST VAX-VMS/FULL ) has the "MOD UNITS" quality,9N you may be able to amend the licence and give it more units (I have never done9 this, but i was told that this is what MOD_UNITS are for.*  M However, there may be legal implications with this when the time comes to get K support/service on your machine. Then again, I am not sure Digital/HP stillt support 5.5-2.    A > B. we need to fix the systartup_vms file but since this file istG > causing a boot problem I have to boot to sysboot and do a set/startupc > opa0:n   SYSBOOT>SET STARTUP_P1 = "MIN" SYSBOOT>CONT  F Then, when you are satisfied that your changes are complete, from VMS:	 MC SYSGENs SYSGEN>USE CURRENT SYSGEN>SET STARTUP_P1 = "" SYSGEN>WRITE CURRENT SYSGEN>EXIT   @ > when in this mode I cant find a text editor to use I type EDTC. > but get an error like it cant find the file?  K With a minimum startup, you get enough to edit. Do a SHOW TERM to make sureaK VMS sees the terminal type, or if not,  SET TERM/DEV=VT200 to coax VMS into % thinking you have a real VT terminal.   = > C. We bought this unit with three 4 gig drives only one was:F > initialized. I looked for a way to initialize them when I was at theE > standalone prompt but I dont think this can be done from here, also.B > tried when in the opa0: mode but that didnt seem to work either.   There are 2 things:a  D FORMAT: done at the >>> prompt  (I think it is TEST 50 if I remember correctly, but not sure)" INITIALISE: done at the $ prompt.   G format will give you a virgin drive. INIT will populate it with the VMSn8 structures to allow you to mount it and put files on it.  E > D. I called HP(not much help) and was told that VMS 5.5-2 would noteE > work on this machine, that it had to be 5.5-2H4 or 6.1 and that youe' > could no longer buy either of these.    N What is the reason while you are at 5.5-2 ? could you not upgrade to something
 more modern ?n   ------------------------------  # Date: Fri, 30 May 2003 02:42:57 GMT-' From: "Mark E. Levy" <melevy@attbi.com>5 Subject: Re: Help with VMS. Message-ID: <RyzBa.168695$rt6.50472@sccrnsc02>  ? "Mark Buda" <buda@tabasco.zko.dec.no.spam.com> wrote in message , news:PzzBa.1648$m73.1190@news.cpqcorp.net... >tJ > The number of units for your old machine is not enough to run on the newD > machine.  You need to have your new machine legally licensed (yourJ > system may be so or it may not be) and have enough units for the license > OPENVMS-ALPHAe   Um, it's a VAX, not an Alpha.h  I > It sounds as if hardware support for the new machine is not in your oldV, > version.  You will likely have to upgrade.  G Not necessarily. Most licenses of that era were shipped with MOD_UNITS. I While not necessarily *exactly* legal, just increase the number of units. K It's not like HP is being deprived of any revenue here, this is very likelyR7 a canned application and it's not going to be upgraded.e   -- l Mark E. Levy" System Management Associates, Inc. www.sysman-inc.com www.openvms.comp   ------------------------------  % Date: Fri, 30 May 2003 00:20:51 -0400n* From: "Stanley F. Quayle" <stan@stanq.com> Subject: Re: Help with VMS- Message-ID: <3ED6A3E3.1043.B017A3F@localhost>h  $ On 29 May 2003 at 17:11, Mark wrote:D > We currently are running a microvax 3100/80 and decide it would beG > good to move to a faster computer so we purchased a microvax 3100/98.e= > We are running VMS 5.5-2 unlimited users with the Y2K patchh  F You need to be at V5.5-2H4.  I have the upgrade disk; I could send it  to you.e   > is there a way to G > fix this license problem without a big hassle? I realy do not want tos@ > have to reinstall anything as my knowledge of VMS is very very
 > limited.  D You don't have to reinstall anything.  Instead, you need to upgrade D your license 60 units of "A" class, DEC part number QL-000AP-62.  I ; have some contacts at HP who can help upgrade your license.-  A > B. we need to fix the systartup_vms file but since this file iseG > causing a boot problem I have to boot to sysboot and do a set/startuptF > opa0: when in this mode I cant find a text editor to use I type EDTC. > but get an error like it cant find the file?  F Others have already suggested a minimum boot.  This would be best for  you.  = > C. We bought this unit with three 4 gig drives only one wasmF > initialized. I looked for a way to initialize them when I was at theE > standalone prompt but I dont think this can be done from here, also>B > tried when in the opa0: mode but that didnt seem to work either.  0 Get your system working first, then init away...  E > D. I called HP(not much help) and was told that VMS 5.5-2 would notpE > work on this machine, that it had to be 5.5-2H4 or 6.1 and that youpH > could no longer buy either of these. I have heard of a patch for 5.5-2. > to make it H4 anyone know where to get this?  1 As I mentioned above, I can provide this for you.M    A [shameless plug alert]  (I'm a CHARON-VAX reseller.)  Instead of k7 buying a 3100-98, you could use CHARON-VAX.  Check out:o  &   http://www.stanq.com/charon-vax.html  C HP will (for $2k) give you licenses that will work on the migrated   system.d  
 --Stan Quayle  Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671b1 8572 North Spring Ct. NW, Pickerington, OH  43147I= Preferred address:  stan@stanq.com       http://www.stanq.com.   ------------------------------  % Date: Fri, 30 May 2003 00:09:11 -0500e2 From: "Stuart Johnson" <ssj152 AT charter DOT net>0 Subject: Re: Hobbyist seeks generic SIMM vendors/ Message-ID: <vddprvjq7psfb2@corp.supernews.com>L  5 "Alder" <PGDEHMKOKIMD@spammotel.com> wrote in messageh& news:3ED5819F.2090903@spammotel.com...I > I believe you're referring to the words "multiple modules" for the 64MBoG > kit.  I've requested some info from Kahlon and will wait to hear what C > they have to say for themselves about that, and about warranties.t >n	 > Cheers,  >  > Alder- >  > Joe Heimann wrote:- > > Alder <MUNDDGNTDYTV@spammotel.com> wrote:S > >2I > >>If anyone has links to online vendors known to stock SIMMs compatible2 withG > >>"older" AlphaServers (mine is a 1000A 4/266), could you please post  linksiL > >>here.  I've contacted Island Computers, but the price is still beyond my* > >>reach.  Best would be sites in Canada. > >t > >e > >>Thanks,d	 > >>Alderi > >e > >aL > > Data Memory Systems, www.datamem.com, has listings for that model.  TheyJ > > want $50 for a 64 MB ECC memory kit if I am reading the listing right.G > > The prices for larger kits are listed as "Call".  Use their "MemoryfL > > Finder" to search for the AlphaServer listing.  Someone mentioned KahlonJ > > in this newsgroup not too long ago.  I have not used them, but a quick4 > > search of their site came up with the following: > >a9 > >         http://www.kahlon.com/result.asp?modelid=1862m > >-J > > They list the same prices for up to the 64 MB kit, and list prices forL > > larger kits.  But the description of the kits does not seem to match theG > > specifications above that kits need to be 5 matched SIMMs per bank.i > >i > >  Joe Heimann > >e > >c > >i >a  I Note: the phrase "5 MATCHED SIMMS" can be taken two ways. Think "buy 5 ofe the same part number".  K Kahlon will not know much about Alpha's and will not sell a part guaranteedxJ to work with the machine. The person you will talk to will be a sales typeJ and may not have ever heard of an Alpha. I know, I've asked. However, as IG stated in an earlier post, their memory WILL work in a AS1000A or otherhH similar machine that uses 72 pin Fast Page Parity 5volt memory.  As my 2I AS1000A's do not use the "extra" 4 chips for ECC, I can't comment on that L configuration, but other posters in this thread have said it will work. That
 convinces me!e  K Kahlon's memory is also a LOT cheaper (4 x 64 mb = 256mb,  4x$31= $124 plus 
 shipping).  I If you want to be CERTAIN the chips will work and want it in writing, pay L the hundreds or thousands of dollars for DEC memory. Think about it anyway -K how much are you risking? Less than $150. This might be the place to take a L chance. I did and I'm very happy with the results. What ever route you take,
 good luck!   Stuart Johnson   ------------------------------   Date: 29 May 2003 19:22:26 GMT( From: ka2doug@cs.commoc.sc (DL Phillips) Subject: Re: Install Directory> Message-ID: <20030529152226.15080.00000767@mb-m14.news.cs.com>   Larry Kilgallen wrote:> >In article <57ee6a43.0305290638.25812eb1@posting.google.com>,( >wsmith@smausa.com (Wendy Smith) writes:E >> What, if any, is the convention regarding the directory into whicheN >> third-party software should be loaded in preparation for an installation ofJ >> the software? We are currently installing in [000000], and a client hasL >> indicated it is "more appropriate" to install in SYS$MANAGER. I am new toH >> the Alpha VMS world, and thus have no fact-based opinion of my own... > B >Temporary directory storage during installation should be managedB >by either VMSINSTAL or PRODUCT INSTALL, the two supported methods5 >of installing software, under control of the vendor.@  N  Yes, this is the digi-paqard way, but during the  2+ decades that I've been aL TP software supplier of VMS applications I've found it unwise to rely on the whims of digi-paqard.a  O   It's been easier in our experience to use our own installation method that we N control and not spend wasted man-days learning some new and obscure "langauge"- that is liable to change in the next release.6  K  I'd say that the PRODUCT INSTALL replacement of VMSINSTAL makes for a goodaC example. The "breakage" of NCP (and DECnet) and the ERRLOG.SYS filenK (analyse/error) are two other what-the-????'s that happen to come to mind. e  y
 JMHO, YMMV   > C >If you are talking about copying the installation kits temporarilyKC >to magnetic disk to speed running one of those installation tools,mB >"wherever it fits" should do.  I tend to make a subdirectory from >my own login directory. >mA >There is a lot of rigor for where the finished product should be ? >put by the installation process, but that is up to the vendor.e? >As I understand it, that was not your question, as you are note >the vendor. >h  H Since he mentioned "a client", I got the impression that he is a vendor.  
   DL Phillips    ------------------------------    Date: 29 May 2003 14:46:34 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen)~ Subject: Re: Install Directory3 Message-ID: <A+9dxzcQYd3u@eisner.encompasserve.org>.  i In article <20030529152226.15080.00000767@mb-m14.news.cs.com>, ka2doug@cs.commoc.sc (DL Phillips) writes:4 > Larry Kilgallen wrote:? >>In article <57ee6a43.0305290638.25812eb1@posting.google.com>,o) >>wsmith@smausa.com (Wendy Smith) writes:EF >>> What, if any, is the convention regarding the directory into whichO >>> third-party software should be loaded in preparation for an installation oftK >>> the software? We are currently installing in [000000], and a client has9M >>> indicated it is "more appropriate" to install in SYS$MANAGER. I am new todI >>> the Alpha VMS world, and thus have no fact-based opinion of my own...i >>C >>Temporary directory storage during installation should be managedtC >>by either VMSINSTAL or PRODUCT INSTALL, the two supported methodsi6 >>of installing software, under control of the vendor. > P >  Yes, this is the digi-paqard way, but during the  2+ decades that I've been aN > TP software supplier of VMS applications I've found it unwise to rely on the > whims of digi-paqard.   B Then you are going so strongly against the expectations of typicalB system managers that the very notion of adhering to conventions is absurd.r  Q >   It's been easier in our experience to use our own installation method that weoP > control and not spend wasted man-days learning some new and obscure "langauge"/ > that is liable to change in the next release.y  I The last time an installation method was decommitted was about VMS 2 or 3u+ when VMSUPDATE was replaced with VMSINSTAL.)  M >  I'd say that the PRODUCT INSTALL replacement of VMSINSTAL makes for a goodeE > example. The "breakage" of NCP (and DECnet) and the ERRLOG.SYS file M > (analyse/error) are two other what-the-????'s that happen to come to mind. i  2 So stick with VMSINSTAL.  Various HP compilers do.   ------------------------------  % Date: Thu, 29 May 2003 16:31:25 -0400i* From: JF Mezei <jfmezei.spamnot@istop.com> Subject: Re: Install Directory) Message-ID: <3ED66E13.A68A5EC9@istop.com>-   Wendy Smith wrote:I > the software? We are currently installing in [000000], and a client hasiK > indicated it is "more appropriate" to install in SYS$MANAGER. I am new to G > the Alpha VMS world, and thus have no fact-based opinion of my own...k  G If using VMS install or some other procedure, you should simply let the2L customer decide where he wants the software to be installed. It also dependsG on the size of the software. (a few files, or a large number of files).u  J One way to do this is to have your startup procedure use f$environmenty toL find out what its file name is, parse it to extract device and directory andI then define the logical that points to your software. (or tell the systemN= manager he must define that logical in his startup procedure.   C Personally, I do not think that any software should be installed in)J sys$manager. The directories are cluttered enough already (especually withK TCPIP services having a whole bunch of files there that don't belong there.   F At the limit, I can tolerate an application adding its startup file inF sys$startup. But I much prefer having all of an application in its ownL directory. The trouble startst when the application is written in such a wayM as to require some shareable images be placed in sys$library. The application N should then have a file in its own directory providing a list fo its own filesK that were installed elsewhere so that years later, when you are cleaning up-0 your system, you have know what belongs to whom.   ------------------------------  % Date: Thu, 29 May 2003 16:46:01 -0400w* From: JF Mezei <jfmezei.spamnot@istop.com> Subject: Re: Install Directory) Message-ID: <3ED6717F.8337003F@istop.com>0  C > Temporary directory storage during installation should be managed0C > by either VMSINSTAL or PRODUCT INSTALL, the two supported methodsc > of installing software,j  M Note that last time I looked, Product Install had limited abilities to selecttM the destination directories/devices. It seemed to have been designed for core 0 VMS software,. not so much for layered products.   ------------------------------   Date: 29 May 2003 21:44:29 GMT( From: ka2doug@cs.commoc.sc (DL Phillips) Subject: Re: Install Directory> Message-ID: <20030529174429.21418.00000103@mb-m28.news.cs.com>   >>DL Phillips mumbled: tO >>  Yes, this is the digi-paqard way, but during the  2+ decades that I've been1 a O >> TP software supplier of VMS applications I've found it unwise to rely on the  >> whims of digi-paqard. >e >Larry Kilgallen protested:0C >Then you are going so strongly against the expectations of typicalcC >system managers that the very notion of adhering to conventions is  >absurd.  M  When I, working as a system manager as I sometimes do, install any product IVN always RTFIG and do what it says. I expect the product to install and work theK way the Installation Guide says.  What other expectations should one have?    L  Just because Digital wrote an installer application doesn't mean that's theH only way to install any product.  It means we can expect that any HP-VMSM product will probably use either VMSINTALL or maybe PRODUCT INSTALL depending4L upon what the Cover Sheet or Installation Guide says and who put it togetherN and how old the product is and whether you're installing on VAX or Alpha or...  O  I don't follow your comment about "the  very notion of adhering to conventions & is absurd". Should I feel insulted?;-)  O  Okay, I'll revise my mumble. If the installation of a TP product requires thatrM the system reboot, and/or that adjustment be made to any system parameters orhL does any other such system-critical tinker , then the best and safest way toA have the product install it via PRODUCT INSTALL (or VMSINSTALL). c  N  If the product is just a user-level application and requires no more than theM creation of some directories and maybe the installation of a library or such,fJ then just make sure the Installation Guide is clear and correct, and do itK however you like. It's your application, not HP's. If you want to use theirI installer, it's there for you.  O  I'd also like to appologize for my inconsiderate and possibly incorrect gendernL specific reference to the original poster, Wendy Smith, who I referred to as "he". Sorry, Wendy Smith.     DL Phillips   ------------------------------  # Date: Fri, 30 May 2003 00:50:29 GMTe From: Rob.Buxton@wcc.govt.nz Subject: Re: Install Directory$ Message-ID: <3ed6a8fc.17328328@news>  E On 29 May 2003 07:38:55 -0700, wsmith@smausa.com (Wendy Smith) wrote:e  C >What, if any, is the convention regarding the directory into which L >third-party software should be loaded in preparation for an installation ofH >the software? We are currently installing in [000000], and a client hasJ >indicated it is "more appropriate" to install in SYS$MANAGER. I am new toF >the Alpha VMS world, and thus have no fact-based opinion of my own... >e >I appreciate your response!  E Breaking this down a bit, are you asking where the software should bed placed prior to installation?n  ) And then where it should be installed to?s  B I've typically set up a directory, e.g. [SOFTWARE] and then createF sub-directories below that for the products I'm installing.  I tend toB do this for the software that has not been distributed on CDs e.g.D I've got it from the Web etc. So, that's where I put software before
 installation.U  E If it's a third party application and it can easily be installed on a E disk separate from my System Disk, then that's where I'll install it.e@ I like to keep the System Disk as clean and VMS Software only asF possible. I know it's not always possible, and in some cases it's moreE trouble than it's worth, so in those cases I'll install on the system0 disk. D It would depend on how the installation works, if the first thing itD does is create a sub-directory from where it is then starting at the= [000000] directory is fine. If it doesn't then I'd definatelyt# recommend creating a new directory.EC Personally I wouldn't install things into SYS$MANAGER either, I try  and reserve that for VMS.i   ------------------------------  % Date: Thu, 29 May 2003 17:56:07 -0700o# From: "Tom Linden" <tom@kednos.com>f Subject: RE: Install Directory9 Message-ID: <CIEJLCMNHNNDLLOOGNJIIEMIHEAA.tom@kednos.com>I  G The Software vendor should have figured out and embedded in the installtI process where to put it.  Possible allowing  (perhaps through dialog) you K to select other than the default where they believe it should be.  If it is5I your problem complain to the vendor till they get it right.  W2K has done $ a pretty good job with this, hint.     >-----Original Message------= >From: Rob.Buxton@wcc.govt.nz [mailto:Rob.Buxton@wcc.govt.nz]l% >Sent: Thursday, May 29, 2003 5:50 PMj >To: Info-VAX@Mvb.Saic.Com >Subject: Re: Install Directoryu >  >hF >On 29 May 2003 07:38:55 -0700, wsmith@smausa.com (Wendy Smith) wrote: >aD >>What, if any, is the convention regarding the directory into which> >>third-party software should be loaded in preparation for an  >installation ofI >>the software? We are currently installing in [000000], and a client has:K >>indicated it is "more appropriate" to install in SYS$MANAGER. I am new to-G >>the Alpha VMS world, and thus have no fact-based opinion of my own...  >> >>I appreciate your response!t >nF >Breaking this down a bit, are you asking where the software should be >placed prior to installation? >o* >And then where it should be installed to? >IC >I've typically set up a directory, e.g. [SOFTWARE] and then create G >sub-directories below that for the products I'm installing.  I tend to-C >do this for the software that has not been distributed on CDs e.g.mE >I've got it from the Web etc. So, that's where I put software beforer >installation. >9F >If it's a third party application and it can easily be installed on aF >disk separate from my System Disk, then that's where I'll install it.A >I like to keep the System Disk as clean and VMS Software only asSG >possible. I know it's not always possible, and in some cases it's moreMF >trouble than it's worth, so in those cases I'll install on the system >disk. 7E >It would depend on how the installation works, if the first thing it E >does is create a sub-directory from where it is then starting at theP> >[000000] directory is fine. If it doesn't then I'd definately$ >recommend creating a new directory.D >Personally I wouldn't install things into SYS$MANAGER either, I try >and reserve that for VMS. >  >r >---' >Incoming mail is certified Virus Free.u; >Checked by AVG anti-virus system (http://www.grisoft.com).YA >Version: 6.0.484 / Virus Database: 282 - Release Date: 5/27/2003. >t ---b& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.484 / Virus Database: 282 - Release Date: 5/27/2003   ------------------------------  # Date: Thu, 29 May 2003 17:37:21 GMTr+ From: Ryan Moore <rmoore@rmoore.dyndns.org>   Subject: Re: Invalid Disk format6 Message-ID: <Pine.LNX.4.53.0305291036380.13789@jaipur>  F Maybe the on-disk write-back cache is enabled.  I believe VMS requiresI that the on-disk write-back cache be disabled.  And I believe the defaulttI for NT is to enable that cache.  That may be why VMS won't touch the diskeI since it senses this setting.  I don't know how you turn it off.  Maybe a  jumper on the drive?  ' On Wed, 28 May 2003, Alan Boyles wrote:MN > I was trying to install VMS 7.3-1 on an AlphaStation 500/500 ( yea, I got itL > working- see power problem ).  The system has 2 disks DKA0 and DKA100.  AtN > the >>> prompt I do a show device and they both show up as RZ1BB-BS but whenI > I tried to init dka0 as the system disk ( and when I try to init at DCLrL > prompt ) I am getting an INIT-F-INVALID Invalid Media Format.  This systemK > orginally had NT on it and I am assuming that this is happening due to NT>@ > formating the disk.  How can I get this disk into ODS format ?   ------------------------------  + Date: Thu, 29 May 2003 18:36:39 +0000 (UTC) 7 From: moroney@world.std.spaamtrap.com (Michael Moroney)o  Subject: Re: Invalid Disk format( Message-ID: <bb5jvn$uas$1@pcls4.std.com>  - Ryan Moore <rmoore@rmoore.dyndns.org> writes:k  G >Maybe the on-disk write-back cache is enabled.  I believe VMS requiresCJ >that the on-disk write-back cache be disabled.  And I believe the defaultJ >for NT is to enable that cache.  That may be why VMS won't touch the diskJ >since it senses this setting.  I don't know how you turn it off.  Maybe a >jumper on the drive?T  * You can get lots of drive info as follows:   $ scsi :== $sys$etc:scsi_info  $ scsi dka0:  E The output is very cryptic (the raw SCSI mode pages) but if you know iC someone who knows SCSI maybe they can find the offending parameter.  -- r -Mikeo   ------------------------------    Date: 29 May 2003 13:12:06 -07001 From: joe.lofft@itec.mail.suny.edu (Joseph Lofft)e( Subject: JAVA appears to hang on OpenVMS= Message-ID: <de82e5e4.0305291212.3d67f4b1@posting.google.com>I  ; I am wondering if anyone else has encountered this problem..  D I am running JAVA131 V1.3-16 on OpenVMS V7.3-1.  Occasionally when ID use either the java or javac commands I am never returned to the VMSA prompt.  I have found that if I press CTRL-T that the command hasC= completed executing and I am then returned to the VMS prompt.s  D The same behavior holds true for java running in batch scripts.  TheC job will appeat to be still executing even though all commands havecC completed executing.  I verify this becasue the java app I am usingvD sends email as the last step, the email gets sent, but the job never finishes executing.-  
 Any thoughts?-   ------------------------------  # Date: Thu, 29 May 2003 20:46:16 GMTP6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER), Subject: Re: JAVA appears to hang on OpenVMS3 Message-ID: <skuBa.32875$Cx4.319763@news.chello.at>l  q In article <de82e5e4.0305291212.3d67f4b1@posting.google.com>, joe.lofft@itec.mail.suny.edu (Joseph Lofft) writes:l< >I am wondering if anyone else has encountered this problem. >.E >I am running JAVA131 V1.3-16 on OpenVMS V7.3-1.  Occasionally when I>E >use either the java or javac commands I am never returned to the VMSJB >prompt.  I have found that if I press CTRL-T that the command has> >completed executing and I am then returned to the VMS prompt. >oE >The same behavior holds true for java running in batch scripts.  The}D >job will appeat to be still executing even though all commands haveD >completed executing.  I verify this becasue the java app I am usingE >sends email as the last step, the email gets sent, but the job never  >finishes executing. >> >Any thoughts?  H I think I read about such a behaviour here or in release notes of an ECOL some months ago. I never had it happen, so I wasn't following. Maybe someoneM can jump in with the details. In the meantime, look for the VMS731_xxxx ECOs.a   -- n Peter "EPLAN" LANGSTOEGERa% Network and OpenVMS system specialistf E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Thu, 29 May 2003 19:41:48 +0100 * From: "Matt Simis" <mattsimis@hotmail.com>5 Subject: Re: Mystery Alpha CPUS, what do they fit in?o5 Message-ID: <bb5k90$61ke8$1@ID-131939.news.dfncis.de>i  . "John Smith" <a@nonymous.com> wrote in messageB news:nPqBa.85626$cK1.42100@news01.bloor.is.net.cable.rogers.com... >t7 > "Matt Simis" <mattsimis@hotmail.com> wrote in messages1 > news:bb59uk$5o3fi$1@ID-131939.news.dfncis.de...a > > F > > "David Beatty" <David.Beatty@qwertysasasdfgh.com> wrote in message0 > > news:H=jVPqnLNvIB5G4bhmS=V0YG3d+o@4ax.com...6 > > > On Thu, 29 May 2003 11:08:48 +0100, "Matt Simis"$ > > > <mattsimis@hotmail.com> wrote: > > >.C > > > >I have seen these on eBay (even bought one :(  and around one	 > variouse > > > >websites:1 > > > >http://www.dyna-comp.com/html/cpd/cpu.html8 > > > >oF > > > >What the hell are are these (21264 ones) for? I just cant get a
 > straightH > > > >answer on why there seems to be an abundance of socket based cpus	 > with nol > > > >motherboards? > > > > & > > > >Have look at the page for pics.  > > > >Does any one have a clue? > > > >g > > > >r > > > >Mattr > > > >n > > >g7 > > > I used http://www.google.com/ to search for 21264n2 > > > and found a link that answers your question: > > >n4 > > > http://www.microprocessor.sscc.ru/alpha-21264/ > > >a2 > > > The 21264B is an Alpha EV68 and the 21264 is > > > an Alpha EV6.o > > >o > > > David R. Beattyi > > >  > >  > >t. > > Thats somewhat helpful, but doesnt answer: > > H > > What motherboard, what systems came with said CPUs and why are there	 > so many , > > CPUs floating that have no motherboards? > >DG > > That page shows all the 21264 Cpus as being "PGA" packages, yet allt > theh> > > 21264 CPUs Im aware of are surface mounted to the PCB on a > Daughterboard.> > > Perhaps Im misunderstanding the use of "PGA" here however. >d > A > Not familiar with the Samsung parts, but perhaps Samsung made at@ > different packaging decision for the CPU's and boards they/API > produced.l >o >   K Now that you mention it, perhaps thats it, they are all CPUs for one of thelK Samsung boards. I did a search and found only one board that would *appear*n9 to take PGA cpus, http://www.mikerohard.de/up1100spec.pdfp  J From the pic I cant tell if its mounted to the motherboard or in a socket. Anyone know anything further?v     Matt   ------------------------------  % Date: Thu, 29 May 2003 15:21:17 -0400D( From: David Froble <davef@tsoft-inc.com>5 Subject: Re: Mystery Alpha CPUS, what do they fit in?e, Message-ID: <3ED65DAD.9030905@tsoft-inc.com>   Matt Simis wrote:e  D > "David Beatty" <David.Beatty@qwertysasasdfgh.com> wrote in message. > news:H=jVPqnLNvIB5G4bhmS=V0YG3d+o@4ax.com... > 2 >>On Thu, 29 May 2003 11:08:48 +0100, "Matt Simis"  >><mattsimis@hotmail.com> wrote: >> >>G >>>I have seen these on eBay (even bought one :(  and around on various  >>>websites:- >>>http://www.dyna-comp.com/html/cpd/cpu.htmlr >>>nK >>>What the hell are are these (21264 ones) for? I just cant get a straightlL >>>answer on why there seems to be an abundance of socket based cpus with no >>>motherboards? >>>e" >>>Have look at the page for pics. >>>Does any one have a clue? >>>t >>>n >>>Matt  >>>o >>>e3 >>I used http://www.google.com/ to search for 21264U. >>and found a link that answers your question: >>0 >>http://www.microprocessor.sscc.ru/alpha-21264/ >>. >>The 21264B is an Alpha EV68 and the 21264 is >>an Alpha EV6.e >> >>David R. Beattyn >> >> >  > , > Thats somewhat helpful, but doesnt answer: > N > What motherboard, what systems came with said CPUs and why are there so many* > CPUs floating that have no motherboards? > I > That page shows all the 21264 Cpus as being "PGA" packages, yet all the>K > 21264 CPUs Im aware of are surface mounted to the PCB on a Daughterboard..< > Perhaps Im misunderstanding the use of "PGA" here however.    Q I'm guessing here.  Chips have become commodities, and traded as such.  Possibly tL the chips you have are intended for surface mount, not a socket.  In either N case, if DEC/Compaq/HP only manufacture systems with surface mount CPUs, then K the chips you have would be useful to anyone who is building surface mount oN boards, or is building boards with sockets, if the chips are indeed built for  sockets.  Bummer.n  L It's possible some of the API boards used sockets.  Something to look into. . Don't know if they ever built a board for EV6.   Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  % Date: Thu, 29 May 2003 23:49:01 +0200  From: Dirk Munk <munk@home.nl>5 Subject: Re: Mystery Alpha CPUS, what do they fit in? 2 Message-ID: <bb5vfb$7ih$1@news1.tilbu1.nb.home.nl>  J The CPU's may have been intended for motherboards made by Alpha Processor Q Company, or however the company was called at the time. This company was started  Q by Digital and Samsung to market the Alpha Processor. They had their own line of VP motherboards. and one of them was (is) sold by Compaq in the DS20L. This system , is a Tru64 only design, it will not run VMS.  > Today this company sells network products if I'm not mistaken.   ------------------------------  % Date: Thu, 29 May 2003 21:47:14 -0500e. From: Lyndon Bartels <lbartels@pressenter.com>) Subject: Needed, history of startup files - Message-ID: <3ED67FE2.511FFAB@pressenter.com>o  C I've got a machine where all the startup files are all bulloxed up.   , The system is currently runing Alpha VMS 7.2    0 It's been upgraded at least once, probably more.    F Anyway the startup files are layers of one .com file doing nothing but= calling a second file, which does nothing but call a third...h    : If I remember correcly, sylogicals.com, systartup_vms.com,9 lat$systartup.com, etc. have been a relatively new thing.   G But I can't remember the genieology of them. When did Lat$systartup.como% become the prefered file over ltload.v  ? If I remember correctly sylogicals.com superseded setuplog.com.gD Setuplog.com used to be called from within the systartup.com. But atD some point, sylogicals, get created, and was called independently of systartup.com. -  2 systartup.com was superseded by systartup_vms.com.    ( Tell me the story of these files please?     Thanks in advance,     Lyndon   -- DG My opinions are mine and mine alone. They seldom align with those of myl	 employer.s    H The only good thing about putting the cart before the horse is you don't have to look at the horse's butt.   ------------------------------  # Date: Thu, 29 May 2003 23:34:54 GMTr2 From: "Teri Lyn Smith" <poodleskirt@sbcglobal.net>0 Subject: Needing to upgrade from AXP VMSv7.1-1h2< Message-ID: <yOwBa.8930$Hp2.6805@newssvr17.news.prodigy.com>  E Anyone with experience going from v7.1-1h2 to a current (read 'latesteL supported and least buggy') AXP VMS please email me with cavaets and advice.  / I hate to fix what isn't broken but must do it.    Thanks Teri Lyn Smith mailto:smithtl@cccta.org   ------------------------------    Date: 29 May 2003 15:50:47 -0500+ From: young_r@encompasserve.org (Rob Young) % Subject: Re: New MiniMerge capabilityt3 Message-ID: <hq21fuuDeGV+@eisner.encompasserve.org>o  a In article <oho8LMhRDCMp@eisner.encompasserve.org>, young_r@encompasserve.org (Rob Young) writes:"V > In article <3ED61A25.F1726F1F@127.0.0.1>, Nic Clews <sendspamhere@127.0.0.1> writes: >> Rob Young wrote:U >>>      > ? > 	As we know.  What happens if master node crashes?  Resort to @ > 	full copy behavior - no harm no foul.  What happens if thingsA > 	get slightly out of synch with new MINIMERGE?  Full merge.  Not > 	harm no foul. > @ > 	What I am thinking is the SCS for "write-in-progress" message@ > 	is sent prior to or synched with StartIO.  It is synchronous.D > 	If the node crashes, the SCS message that last came across is theB > 	last io that was *possibly* started.  If because of heavy writeA > 	activity one or more nodes had to go to buffered message mode, D > 	all bets are off and full merge for that volume will occur.  IdeaG > 	would be maintain synchronous at all costs - hence maybe granularity + > 	may have to change to cut down messages.  > F > 	I guess I -am- relying on SCS making it.  But if SCS can't make it,G > 	don't startio.  Surely there are some tricks here that I am missing,t > 	I'm not a systems developer.i >    	SCS sent prior to StartIO.m   	Re: how likely to work?  A 	Looking at my lock request latency chart, the SCS message shouldHB 	fall in the 100-120 microsecond range, adding .1 ms to each write@ 	in addition to more SCS traffic.  I would think the SCS messageG 	would be lighterweight than taking out a lock.  I believe just have tor; 	flip bits and not grab/create a structure.  Of course, howt< 	much would it take away from CPU, add to SCS overhead, etc.   				Rob@   ------------------------------  # Date: Thu, 29 May 2003 21:43:02 GMTs/ From: brooks@cuebid.zko.dec.nospam (Rob Brooks).% Subject: Re: New MiniMerge capabilityd- Message-ID: <wIIM1EaRYVHd@cuebid.zko.dec.com>h  - young_r@encompasserve.org (Rob Young) writes:i > 	SCS sent prior to StartIO.o >  > 	Re: how likely to work? > C > 	Looking at my lock request latency chart, the SCS message shouldaD > 	fall in the 100-120 microsecond range, adding .1 ms to each writeB > 	in addition to more SCS traffic.  I would think the SCS messageI > 	would be lighterweight than taking out a lock.  I believe just have to = > 	flip bits and not grab/create a structure.  Of course, how > > 	much would it take away from CPU, add to SCS overhead, etc.  I I don't plan to get into a public discussion as to how we're implementing-I Host-Based Minimerge, other than to say that there will be no VAX supportw? (which I did not mention in my earlier posting).  Note that for E Mini-Copy, all write bitmaps are deleted if a node enters the clusteru1 that cannot participate in writing to a bitmap.  3  G We plan to loosen that restriction for Host-Based Minimerge such that ayN non-player will not be able to mount a shadow set enabled for HBMM, and that aN shadow set mounted by a non-player cannot be enabled for HBMM, but non-playersE can coexist with HBMM-capable nodes in a cluster as long as they (the N non-players) keep their hands off HBMM-enabled shadow sets.  Note that this is> the plan, and the desired behaviour; this is not a commitment.  K HBMM will not ship with the next functional release of OpenVMS Alpha, which N is due out in the 4th quarter of this calendar year.  It will be available viaH the standard patch kit mechanism for both V7.3-1 and the next functionalL release (most likely to be called V7.3-2).  I will not attempt to guess whenG these kits will be available.  It is our hope that they'll be under theo5 Christmas tree, but, again, that is not a commitment.    -- d  M Rob Brooks    VMS Engineering -- I/O Exec Group     brooks!cuebid.zko.dec.comi   ------------------------------  % Date: Thu, 29 May 2003 21:19:02 -0700e& From: Greg Cagle <gregc@gregcagle.com>< Subject: Re: NT: son of VMS? (was Re: Portents of VMS death)/ Message-ID: <vddmvjpk8gct08@corp.supernews.com>t   Bill Todd wrote:  G > "Steve Lionel" <Steve.Lionel@not-specified-here.zyx> wrote in message 4 > news:b12adv8t25c3dqq4g31ctutv8j3paj5qdh@4ax.com... > I >>On Wed, 28 May 2003 17:23 +0100 (BST), duncan@macdonald.compulink.co.uk  >>(Duncan Macdonald) wrote:o >> >>C >>>He was the original author for much of it. And the code was goodo >  > quality - an > E >>>unusual combination of tight efficient coding and clear design andn+ >>>good commenting and a very low bug rate.d >>C >>If you're referring to Dave Cutler here, I think you're very muchC >  > mistaken.r > N > No, he's absolutely correct:  Cutler's code (at least his RSX code - I neverM > saw much of VMS at the source-code level) was high-quality according to thelJ > measures of its day:  tight, with well-designed interfaces, and correct.I > I'd have included more detailed comments, but I comment code in greater8D > detail than anyone else I've ever seen, so that doesn't mean much.  D Agree about Cutler's code. I spent a lot of time in both RSX and VMS/ source in the 80s, and it was great stuff IMHO.1  L >>Cutler's code may indeed have been tight and efficient, but it also tended >>toJ >>be fragile, highly dependent on undocumented behaviors, uncommented, and) >>obscure to the point of unmaintainable.e  A I don't believe this to be true. We wrote some incredibly complex'= device drivers that just would not have been possible withouti> clear interfaces and documented behaviors. Sorry, I just don't7 agree. And yes, we had VMS source fiche as well as RSX.b  L > All code is fragile if mishandled and obscure to those not 'skilled in theI > art'.  In the early '70s minicomputer OS code had to be a) small and b)oB > correct, each being equally important.  It was accepted that theJ > requirements of (a) implied that it would not be maintainable by trainedL > monkeys, or even average engineers - and OS people were hired accordingly. > N > What constituted being 'a good software engineer' (perhaps especially in theL > OS area, since applications could be overlaid and swapped in early systemsK > but to a large extent OS code was always resident), and more especially a B > good implementor, changed radically as the world moved to 32-bitL > environments and to physical memory sizes sometimes larger than disk sizesJ > had been earlier.  Dave may have resisted that transition in some of hisL > coding practices; I know that I certainly did, and in a few ways still do.I > But his RSX code was absolutely top-notch for its time, and of course aeN > great deal of his superb basic RSX design benefited both VMS and NT in later > years.   Absolutely.o   - Greg -- m
 Greg Cagle gregc at gregcagle dot com   ------------------------------  % Date: Thu, 29 May 2003 16:19:39 -0400 * From: JF Mezei <jfmezei.spamnot@istop.com>& Subject: Re: OSU http_server errorpage) Message-ID: <3ED66B52.30695E22@istop.com>l   Chris Sharman wrote:/ > .NEXT errorpage protfail /demo/error_403.htmlr( > .NEXT # openfail /htbin/openfail.com */ > .NEXT errorpage rulefail /demo/error_403.html * > .NEXT # cgiprotocol /demo/error_500.html1 > .NEXT errorpage  code4 /demo/error_preproc.htmlI    M protfail is when the web server process does not have provilege to access thev requested file.y Not sure about openfailtA rulefail is when you type in a URS that isn't mapped to anything.,M cgiprotocol is when you request a script that hasn't been enabled as a script < not sure about code4. "code4" is probably defined elsewhere.  = > And while I'm asking, what's this .iterate & .next anyway ?p  N There is a way to preprocess the file and generate the configuration file with: the script diretives executed. (that is what I have done).  I However, the scripting allows the web-based configuration utility to run.  (which i don't use).   ------------------------------  % Date: Thu, 29 May 2003 16:36:16 -0400-* From: JF Mezei <jfmezei.spamnot@istop.com>" Subject: Re: Portents of VMS death) Message-ID: <3ED66F36.93F7B9C4@istop.com>c   jlsue wrote:I > How do you get from a discussion about a specific cluster configurationt- > into a generic, VMS marketplace discussion?o  N Because not everyone has an application that justifies buying a dozen nodes toJ make a full fledged cluster where any node can go down without any impact.I There are many who would like to choose VMS for a small scale system that N provides production on one node, test on another with production mirrored ontoJ the test system so that the test system can be used when production fails.  K If you tell them that this isn't what VMS is for, then they will go to UnixoN and Windows. Is the goal to only keep the "crme de la crme" of customers, orF to expand the VMS marketplace and capture the HUGE potential for small  clusters in smaller businesses ?   ------------------------------  % Date: Thu, 29 May 2003 16:40:59 -0400 * From: JF Mezei <jfmezei.spamnot@istop.com>" Subject: Re: Portents of VMS death) Message-ID: <3ED67051.3260B637@istop.com>i   jlsue wrote:F > In this specific instance?  Not hardly.  They made a decision not toJ > upgrade to a release that resolves those problems, so they suffered with > them.   M No. Itis of my opinion that many shops with older versions of VMS have alredyaF made the decision to abandon VMS and are simly continuing to run theirL remaining apps on the old VMS box until they are ported to the new platform.  L And then there are some for whom upgrade is not possible becayse the ISV hasH avbandonned VMS and the application is only certified to run at whatever9 version was available at the time the ISV abandonned VMS.b  L All these case point to a unhealthy VMS marketplace where customers and ISVsF do not have confidence in the future of that platform and have stoppedL upgrading that platform. And because they lag behind in features, it becomesM even easier for them to justify getting rid of the "old" VMS because it is sopK "old" compared to more modern systems, and since they have no confidence in-8 VMS, they don't bother looking at what VMS offers today.   ------------------------------  # Date: Thu, 29 May 2003 21:47:18 GMT # From: "John Smith" <a@nonymous.com>g" Subject: Re: Portents of VMS deathJ Message-ID: <GdvBa.303776$w7k.215749@news04.bloor.is.net.cable.rogers.com>  7 "JF Mezei" <jfmezei.spamnot@istop.com> wrote in message3# news:3ED67051.3260B637@istop.com...s > jlsue wrote:E > > In this specific instance?  Not hardly.  They made a decision noth to> > > upgrade to a release that resolves those problems, so they
 suffered withr	 > > them.a >nC > No. Itis of my opinion that many shops with older versions of VMSa have alredy B > made the decision to abandon VMS and are simly continuing to run theirtD > remaining apps on the old VMS box until they are ported to the new	 platform.> >>F > And then there are some for whom upgrade is not possible becayse the ISV hasMA > avbandonned VMS and the application is only certified to run atl whatever; > version was available at the time the ISV abandonned VMS.i >qE > All these case point to a unhealthy VMS marketplace where customersp and ISVs@ > do not have confidence in the future of that platform and have stopped F > upgrading that platform. And because they lag behind in features, it becomesnF > even easier for them to justify getting rid of the "old" VMS because it is so? > "old" compared to more modern systems, and since they have not
 confidence in : > VMS, they don't bother looking at what VMS offers today.    C It may not be so much a matter of being "old" as it may be that thet customer/user,  C a) Bought into the Digital 'NT is the future' campaign in the earlyp 90's, or b) Bought into unix hype, or! c) Are buying into Linux hype, orfE d) Simply that all the people who knew VMS at that shop have left andnB the people that are there today know only enough about VMS to keepC their app limping along in status quo mode because they all went to < colleges/universities where only unix and Windows were used.   ------------------------------   Date: 30 May 2003 02:08:46 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)" Subject: Re: Portents of VMS death5 Message-ID: <bb6efe$69e7i$1@ID-135708.news.dfncis.de>a  J In article <GdvBa.303776$w7k.215749@news04.bloor.is.net.cable.rogers.com>,& 	"John Smith" <a@nonymous.com> writes: > G > d) Simply that all the people who knew VMS at that shop have left and D > the people that are there today know only enough about VMS to keepE > their app limping along in status quo mode because they all went tot> > colleges/universities where only unix and Windows were used.  oE Some of us are still trying to change this, but not getting much helptF there either.  I find it amazing that the current Hobbyist License canF be used for initial development of potentially commercial products andD yet education is still saddled with a totally unacceptable licensing
 program.  :-(h  s bill   -- uJ 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>   l   ------------------------------  % Date: Thu, 29 May 2003 20:13:26 -0500.1 From: "David J. Dachtera" <djesys.nospam@fsi.net>i@ Subject: Re: Reading CD-R burned on a Window system on an Alpha?' Message-ID: <3ED6B036.680F5C61@fsi.net>a   Larry Kilgallen wrote: > Q > In article <3ed562c0_3@newsfeed>, "Ron Milen" <milenronald@mailbag.net> writes:aN > > I understand about ISO disks.  I've been able to mount & read them before.J > > However, the term Joliet hierarchy is new to me.  Could someone please > > explain this?- > L > Microsoft made their own non-compliant derivative of the ISO-9660 standardH > to implement Unicode file and directory names.  Their format is called	 > Joliet.m   Local (Illinois) joke:  A Joliet, IL is the location of "The Big House", Stateville prison.A   I find a certain irony there...r  ) ...but you can't go by a sicko like me...o   --   David J. Dachtera  dba DJE Systemsa http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/f   ------------------------------  % Date: Thu, 29 May 2003 20:15:37 -0500-1 From: "David J. Dachtera" <djesys.nospam@fsi.net> ; Subject: Re: Skil Saw? (was - Re: New MiniMerge capability)l' Message-ID: <3ED6B0B9.3623D68D@fsi.net>1   "John E. Malmberg" wrote:o >  > Larry Kilgallen wrote: > > C > > Of course VMS itself is not exactly hardware independent.  I ameD > > sure it is headed down the tubes because VMS will not boot on my* > > totally industry standard Skil Saw :-) > ? > I think that you should be able to get the CD-ROM to spin up.l > ' > What do you plan to use as a console?e   Probably a Milwaukee Sawzall...a   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------    Date: 29 May 2003 20:05:45 -0700. From: spamsink2001@yahoo.com (Alan E. Feldman)2 Subject: Re: Stopping a que other then a print que= Message-ID: <b096a4ee.0305291905.14039560@posting.google.com>   [ JF Mezei <jfmezei.spamnot@istop.com> wrote in message news:<3EC05D98.1DA2DB89@istop.com>...  > David Froble wrote:eO > > Don't know if it's always required, but long ago I learned to use the /NEXTe& > > switch on any STOP/QUEUE commands. > - > yep. STOP/QUEUE only works on iddle queues.d > * > And if you REALLY want to stop the queue >  > STOP/QUEUE chocolate_queue" > STOP/QUEUE/ABORT chocolate_queue" > STOP/QUEUE/RESET chocolate_queue > 6 > the first one prevents any more jobs from starting.   @ It also suspends all jobs in such queue, assuming a batch queue.F Starting such a queue allows its batch jobs to change to the Executing state.  4 > The second one stops the currently executing jobs.< > The 3rd one makes sure the queue is really really stopped. >  > ; > What is really neeeded is STOP/QUEUE/NOW=I_REALLY_MEAN_ITt   Disclaimer: JMHO Alan E. Feldmanf   ------------------------------  % Date: Thu, 29 May 2003 14:07:43 -0400t From: koskaj@bender.comy* Subject: RE:  StorageTek l700 on VMS 7.3-1< Message-ID: <03052914074320.bb4f.25271181@alaxp3.bender.com>  J Since a new (to the Alpha systems) tape library/silo is involved, perhaps M the new fibre paths to the silo need to be discovered by OpenVMS, along with n discovery of the tape drives.  -  E Maybe... $MCR SYSMAN IO SCSI_PATH_VERIFY is needed, followed by $MCR  L SYSMAN IO AUTOCONFIGURE ... may allow OpenVMS to discovery and see the silo 
 tape drives.     :) jck  B >From:	SMTP%"JNixon@cfl.rr.com"  "John N." 29-MAY-2003 09:25:21.93 >To:	Info-VAX@Mvb.Saic.Com >CC:	i# >Subj:	StorageTek l700 on VMS 7.3-1p >yM >I think that we have now doubled the number of sites that have a Storage Tek?M >L700 Fibre Channel tape library hooked up to a VMS system.  Except for Davido8 >D.  I have not heard of many others.  And we need help. >AG >We added the tape drive silo (w 8 SDLT 160/320 drives)  to an existingaM >brocade switch configuration, but we cannot see the tape drives from the VMSs	 >systems.u >bM >The StorageTek engineer hooked his laptop up to the switches and can see thesK >tape drives so he figures it is a VMS problem.  The H.P. engineer (who hasiL >always been outstanding) says they have never had to do anything on the VMS' >side to make them see the tape drives.d > F >We have three Alpha systems (Two ES40s (VMS 7.2-1) and one GS140 (VMSI >7.3-1).  Each Alpha has two FC host adapters connected to two Brocade 16lF >port FC switches.  Each switch is connected to our 4 HSG80s which are( >serving two TB of data disks just fine. >eM >We added the L700 with 4 routers.  Each FC switch is connected to two of theiJ >routers, and there are two tape drives on each router. None of our AlphasI >(including the VMS 7.3-1 GS140 with all ECOs applied) can see any of theo
 >tape drives.  >s >Any suggestions?  >a >a   ------------------------------   Date: 29 MAY 2003 19:57:54 GMT4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher)* Subject: Re:  StorageTek l700 on VMS 7.3-16 Message-ID: <29MAY03.19575430@thuria.waisman.wisc.edu>  / In a previous article, koskaj@bender.com wrote:-L ->Since a new (to the Alpha systems) tape library/silo is involved, perhaps O ->the new fibre paths to the silo need to be discovered by OpenVMS, along with I! ->discovery of the tape drives.  t -> vG ->Maybe... $MCR SYSMAN IO SCSI_PATH_VERIFY is needed, followed by $MCR  N ->SYSMAN IO AUTOCONFIGURE ... may allow OpenVMS to discovery and see the silo    Actually it would be:    	$ MCR SYSMAN IO FIND_WWID 	$ MCR SYSMAN IO AUTOi  ? You only need the FIND_WWID once - it will then modify the fileoA SYS$SYSTEM:SYS$DEVICES.DAT with the necessary info. See the help.b  D Also be sure you have CMKRNL, SYSLCK and LOG_IO even though only theE first two privs are documented as being required (and you won't get a H NOPRIV error if LOG_IO is not present). You also want to use IO AUTO/LOGB to display any errors (you won't see certain errors unless you use) /LOG). I've reported these issues to CSC.a   --G -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madisone8 --                karcher.nomorepspam@waisman.wisc.edu     ------------------------------  # Date: Thu, 29 May 2003 22:07:28 GMTt# From: "John N." <JNixon@cfl.rr.com>a) Subject: Re: StorageTek l700 on VMS 7.3-1 < Message-ID: <AwvBa.15083$vL5.425129@twister.tampabay.rr.com>  L I know the SYSMAN IO AUTO command is safe to use on a running system.  Is itH also safe to use those other commands on-line.  And might they be neededK even though the systems were shut down when the F.C. routers were connected L to the FC switches.   Wouldn't (shouldn't) these commands have been executed" sometime during the boot sequence?  A "Carl Karcher" <karcher@thuria.waisman.wisc.edu> wrote in message 0 news:29MAY03.19575430@thuria.waisman.wisc.edu...1 > In a previous article, koskaj@bender.com wrote:aE > ->Since a new (to the Alpha systems) tape library/silo is involved,o perhaps K > ->the new fibre paths to the silo need to be discovered by OpenVMS, alongw with! > ->discovery of the tape drives.M > ->H > ->Maybe... $MCR SYSMAN IO SCSI_PATH_VERIFY is needed, followed by $MCRJ > ->SYSMAN IO AUTOCONFIGURE ... may allow OpenVMS to discovery and see the silo >c > Actually it would be:m >e > $ MCR SYSMAN IO FIND_WWIDP > $ MCR SYSMAN IO AUTO >nA > You only need the FIND_WWID once - it will then modify the fileeC > SYS$SYSTEM:SYS$DEVICES.DAT with the necessary info. See the help., >tF > Also be sure you have CMKRNL, SYSLCK and LOG_IO even though only theG > first two privs are documented as being required (and you won't get a)J > NOPRIV error if LOG_IO is not present). You also want to use IO AUTO/LOGD > to display any errors (you won't see certain errors unless you use+ > /LOG). I've reported these issues to CSC.6 >4 > --I > -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison-8 > --                karcher.nomorepspam@waisman.wisc.edu ><   ------------------------------  # Date: Thu, 29 May 2003 22:25:51 GMT # From: "John N." <JNixon@cfl.rr.com>i) Subject: Re: StorageTek l700 on VMS 7.3-1i< Message-ID: <PNvBa.15225$vL5.431452@twister.tampabay.rr.com>  I ok,  forget the dumb question in my last post.  I did run the command  IOcG FIND_WWID, (followed by IO AUTO) and it did find FIVE of the EIGHT tapei drives.  That is progress.   Thanks for the help.  . "John N." <JNixon@cfl.rr.com> wrote in message6 news:AwvBa.15083$vL5.425129@twister.tampabay.rr.com...K > I know the SYSMAN IO AUTO command is safe to use on a running system.  Iss itJ > also safe to use those other commands on-line.  And might they be neededC > even though the systems were shut down when the F.C. routers werey	 connected E > to the FC switches.   Wouldn't (shouldn't) these commands have beenI executed$ > sometime during the boot sequence? >aC > "Carl Karcher" <karcher@thuria.waisman.wisc.edu> wrote in messagem2 > news:29MAY03.19575430@thuria.waisman.wisc.edu...3 > > In a previous article, koskaj@bender.com wrote:,G > > ->Since a new (to the Alpha systems) tape library/silo is involved, 	 > perhapsrG > > ->the new fibre paths to the silo need to be discovered by OpenVMS,. along> > with# > > ->discovery of the tape drives.t > > ->J > > ->Maybe... $MCR SYSMAN IO SCSI_PATH_VERIFY is needed, followed by $MCRL > > ->SYSMAN IO AUTOCONFIGURE ... may allow OpenVMS to discovery and see the > silo > >b > > Actually it would be:  > >M > > $ MCR SYSMAN IO FIND_WWIDi > > $ MCR SYSMAN IO AUTO > > C > > You only need the FIND_WWID once - it will then modify the file E > > SYS$SYSTEM:SYS$DEVICES.DAT with the necessary info. See the help.  > >dH > > Also be sure you have CMKRNL, SYSLCK and LOG_IO even though only theI > > first two privs are documented as being required (and you won't get a L > > NOPRIV error if LOG_IO is not present). You also want to use IO AUTO/LOGF > > to display any errors (you won't see certain errors unless you use- > > /LOG). I've reported these issues to CSC.e > >5 > > --K > > -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison : > > --                karcher.nomorepspam@waisman.wisc.edu > >  >c >o >l   ------------------------------  % Date: Thu, 29 May 2003 20:27:00 -0500V1 From: "David J. Dachtera" <djesys.nospam@fsi.net>a) Subject: Re: StorageTek l700 on VMS 7.3-1 ' Message-ID: <3ED6B364.176A3DE7@fsi.net>    "John N." wrote: > K > ok,  forget the dumb question in my last post.  I did run the command  IOcI > FIND_WWID, (followed by IO AUTO) and it did find FIVE of the EIGHT tapee > drives.  That is progress.   O.k. Now here's a big rub...  D On the NSRs (FC-SCSI bridges, sometimes called "Crossroads" switchesH since they seem to be the only company in the country (world?) who makesH them, everyone else -including HP - just rebadges them, and maybe tweaksG the firmware a bit), if you're remapping SCSI id's, make sure that eacheG MAP starts with LUN 0. Apparently, VMS can't handle it if, for example,.C the first NSR presents LUNs 0-4 and the second presents 5-whatever.d  F I kinda wish you had elected to hold SYSMAN IO AUTOCON until after youG had resolved the visibility problem. The only way to clear the VMS dataaH structures it (and FIND_WWID) populates is to reboot the entire cluster.  F Note that if you want, before your next reboot, you can change the MGAH device units numbers to any you wish - you're not stuck with what SYSMANG arbitrated. However, if you've already configured other software to usei> the existing device units, well, you know how that stuff kinda snowballs...   -- v David J. Dachteras dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/n   ------------------------------  # Date: Fri, 30 May 2003 05:07:55 GMTm+ From: Jeff Cameron <JCam90502@jcameron.com> ) Subject: Re: StorageTek l700 on VMS 7.3-1t2 Message-ID: <BAFC353B.8FEC%JCam90502@jcameron.com>   On 5/29/03 5:47 AM, in articleL ljnBa.2503$vL5.296949@twister.tampabay.rr.com, "John N." <JNixon@cfl.rr.com> wrote:  N > I think that we have now doubled the number of sites that have a Storage TekN > L700 Fibre Channel tape library hooked up to a VMS system.  Except for David9 > D.  I have not heard of many others.  And we need help.w > H > We added the tape drive silo (w 8 SDLT 160/320 drives)  to an existingN > brocade switch configuration, but we cannot see the tape drives from the VMS
 > systems. > N > The StorageTek engineer hooked his laptop up to the switches and can see theL > tape drives so he figures it is a VMS problem.  The H.P. engineer (who hasM > always been outstanding) says they have never had to do anything on the VMS4( > side to make them see the tape drives. > G > We have three Alpha systems (Two ES40s (VMS 7.2-1) and one GS140 (VMS J > 7.3-1).  Each Alpha has two FC host adapters connected to two Brocade 16G > port FC switches.  Each switch is connected to our 4 HSG80s which arec) > serving two TB of data disks just fine.e > N > We added the L700 with 4 routers.  Each FC switch is connected to two of theK > routers, and there are two tape drives on each router. None of our AlphasaJ > (including the VMS 7.3-1 GS140 with all ECOs applied) can see any of the > tape drives. >  > Any suggestions? >  > L We had similar problems with the Storage Tech libraries (Fibre) on VMS, thenI a fellow from Quantum ATL brought in one of their 4U high M1500 librariesmI with SDLTs. Talk about Plug-and Play in VMS fibre! They came right up. We6L have since bought a P1000 library, and are considering a P3000 for our large
 data center.    G We also tried this new thing on loan from Quantum, a DX30. It is a disk F based system which emulates a tape library where you can configure theL virtual tape volume capacity, and number of virtual tape drives. When we getE more capital, we plan to buy one so we can do our backups to the DX30 I lightning fast, then replicate the savesets from the DX30 to actual tapessF for offsite disaster recovery in the background. Because we often haveK trouble keeping our SDLT's streaming when doing normal backups, the time itiL takes us to do the backups to the DX30 and then replicating to tape is a tad. less time than just backing up direct to tape.  H I must admit a bias. We are resellers for Quantum ATL as well as StorageB Tech. We specialize in storage and backup solutions for the entire Enterprise, Including VMS.   Jeff   ------------------------------   Date: 30 May 2003 06:44:08 GMT/ From: "Dave Weatherall" <djweath@attglobal.net>-, Subject: Re: What's happened to Alan Greig ?5 Message-ID: <DTiotGxQ0bj6-pn2-o5Qvw1z4nTZd@localhost>R  , On Wed, 28 May 2003 13:39:28 UTC, Roy Omond $ <Roy.Omond@BlueBubble.UK.Com> wrote:  - > Haven't seen any postings from him in ages.a > 0 > I hope nothing "untoward" has happened to him. >  > Roy Omond4 > Blue Bubble Ltd. >   4 Odd. I had exactly the same thought again yesterday.   -- t Cheers - Dave.   ------------------------------   End of INFO-VAX 2003.297 ************************