1 INFO-VAX	Tue, 26 Feb 2002	Volume 2002 : Issue 111       Contents: Re: A problem with a patch Re: Abbreviation dictionary  Re: Abbreviation dictionary 1 Re: BZIP2 for OpenVMS (was: Re: PGP for OpenVMS?) 1 RE: BZIP2 for OpenVMS (was: Re: PGP for OpenVMS?)  Edit/TPU question... Re: Edit/TPU question... Re: Edit/TPU question... Re: Edit/TPU question... Re: Edit/TPU question... Re: Edit/TPU question... Re: Edit/TPU question... Re: Edit/TPU question... Re: Edit/TPU question... expensive procedure calls 0 Re: F$EXTRACT does parsing before giving result? Ftp/copy problem Re: Ftp/copy problem Re: Ftp/copy problem Re: Ftp/copy problem FW: Powerpoint competition Re: FW: Powerpoint competitionJ Re: Getting VMS running on alphapc 150 - any help or pointers appreciated. I: PAKGEN Software for ISVs  Re: I: PAKGEN Software for ISVs  Re: I: PAKGEN Software for ISVs  Re: I: PAKGEN Software for ISVs  Re: I: PAKGEN Software for ISVs  Re: I: PAKGEN Software for ISVs  Re: I: PAKGEN Software for ISVs  Re: I: PAKGEN Software for ISVs = Re: IBM says they have best real time mainframe, where's VMS? = Re: IBM says they have best real time mainframe, where's VMS? = Re: IBM says they have best real time mainframe, where's VMS?  If you need PI.... interesting INQUIRER article  Re: interesting INQUIRER article Re: Itanium troubles Re: Itanium troubles Re: Itanium troubles Re: Itanium troubles Re: Itanium troubles  Modular data Router - Fibre Tape$ RE: Modular data Router - Fibre Tape$ Re: Modular data Router - Fibre Tape Re: mysterious system reboot Re: OpenVMS IPF presentation Powerpoint competition Re: Powerpoint competition Re: PrintServer software Re: PrintServer software) Re: Profitability and the survival of VMS ) Re: Profitability and the survival of VMS ) Re: Profitability and the survival of VMS  Re: Proposal - Hobbyist FAQ  Remote Password changes  Re: Remote Password changes  Re: Setting Time and Date  Re: Shannon on the merger  Re: Shannon on the merger # SHOW ENTRY /FULL doesn't show /PARA ' Re: SHOW ENTRY /FULL doesn't show /PARA ' Re: SHOW ENTRY /FULL doesn't show /PARA ' Re: SHOW ENTRY /FULL doesn't show /PARA L Re: Singular they was Re: Sv: Younger recruits versus experienced veterans (P Re: Sv: Younger recruits versus experienced veterans ( was The demise       of  ! Re: The portability of Windows NT & Re: tool to calc recursive dir sises ?& Re: tool to calc recursive dir sises ? Users logged out with TCPIP$XDM  Re: vax h/w type.  Re: VAX SCAN Re: VAX SCAN Re: VAX SCAN Re: VAX SCAN Re: VAX SCAN! vax/vms documentation - psi / x29   F ----------------------------------------------------------------------  # Date: Tue, 26 Feb 2002 01:04:42 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)# Subject: Re: A problem with a patch 1 Message-ID: <KaBe8.165$fL6.4101@news.cpqcorp.net>   b In article <a52r9s$296d$1@news2.ipartners.pl>, "Tomasz Dryjanski" <tdryjanski@hotmail.com> writes:D :I have installed VMS 7.2-1H1, then the VMS721H1_UPDATE-V0400 patch. ..L :The server is Alpha 1000A server with the newest console firmware designed.H :I installed VMS using [INITIALIZE], with more or less standard options,M :without DECW and DECNet Plus (we use Phase IV). The system booted correctly, I :and let me log on with the nice "Welcome to OpenVMS (TM) Alpha Operating # :System, Version V7.2-1H1" message.  ..H :Then I installed the mandatory patch, VMS721H1_UPDATE-V0400. During the' :installation I received the following: L :%PCSI-I-OBJSKP, directory [DECW$INCLUDE] pertains to an option that was not$ :selected; directory update skipped,J :repeated several times, with different DECW directories listed. I thought6 :that it was obvious, and I let installation continue.6 :And the subsequent message, after 80% done, was ugly: :%PCSI-E-READERR, error reading < :DKA400:[PATCH.V721H1]DEC-AXPVMS721H1_UPDATE-V0400--4.PCSI;12 :-DDIS-E-INCSEQCAL, inconsistent sequence of calls$ :%PCSI-E-OPFAILED,  operation failed8 :I terminated the operation and rebooted. And now I have= :"OpenVMS (TM) Alpha Operating System, Version X71Z-P2E" (?!)  :"%INSTALL-E-OPENIN, errorG :opening -DISK$ALPHASYS:<SYS0.SYSCOMMON.SYSLIB>DISMNTSHR.EXE; as input"  :during the boot process, & :and the system is not even able to do :$ sh dev d I :causing access violation (reason mask AC, "Improperly handled condition,  :image exit forced.")  ..  L   Your system disk is apparently corrupted.  Since you didn't make a BACKUP K   of your system disk before you applied the (now failed) ECO (who among us K   really reads and follows the directions, after all? :-), please start by  N   applying the OpenVMS Alpha V7.2-1H1 kit (or better, apply V7.2-2 or later), (   and then roll on the appropriate ECOs.  M   [This is effectively the ECO back-out procedure listed in the OpenVMS FAQ.]   H   I have seen a few DDIS errors reported within PCSI installations, and K   these are almost always triggered by a PCSI file that was not downloaded  J   using correct FTP file transfer semantics -- webbrowser implementations I   seemingly choose to use the binary or the text transfer mode at random. 8   I've *not* seen a -DDIS-E-INCSEQCAL error within PCSI.  H   I'd also determine if there is a file lurking here somewhere that has G   DDIF semantics assigned.  But that does not appear entirely likely to F   have occured, given this is reportedly a fresh OpenVMS installation.  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 25 Feb 2002 22:25:41 -0600 , From: "Rich Jordan" <rjordan@mindspring.com>$ Subject: Re: Abbreviation dictionary2 Message-ID: <a5f2ic$of1$1@slb6.atl.mindspring.net>   JF, F      a real shot in the dark.  Sometime in the last few weeks SlashdotI (slashdot.org) had a pointer to an article about linguists using ZIP (and L specifically one of the tokenizing/dictionary building methods) as a tool inD linguistic analysis; it can supposedly help identify common roots inG languages, or help ID if unacknowledged pieces were written by the same L author.  They were also quite excited about the prospects for use in geneticI research, locating and identifying common sections of code sequence, etc. J It should not be hard to locate the slashdot entry, and it had pointers toK the actual journal site (which as I recall wanted a couple dollars, which I  didn't pay).  K      Like I said, a shot in the dark, but if you have access to information H on the algorithms used for this type of compression, is it possible that, something useful might be developed from it?   Rich Jordan   = JF Mezei wrote in message <3C7A7FEC.17B10DDA@videotron.ca>...  >"Farrell, Michael" wrote: >> >> JF, >>L >> Have you received any answer to this request?  I have a similar interest. > E >Nop, what I will end up doing is a $FIND of the first word, and then F >sequential reads comparing the whole strings until the read string is greater D >than the expression. The previous record will contain the "closest"
 expression1 >that matches as many words as possible  ........    ------------------------------  % Date: Tue, 26 Feb 2002 00:13:24 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> $ Subject: Re: Abbreviation dictionary, Message-ID: <3C7B1972.CDA0F658@videotron.ca>   Rich Jordan wrote:K > (slashdot.org) had a pointer to an article about linguists using ZIP (and N > specifically one of the tokenizing/dictionary building methods) as a tool in > linguistic analysis;  < Thanks, will look for it (didn't find it first time around).   ------------------------------  # Date: Tue, 26 Feb 2002 01:42:37 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman): Subject: Re: BZIP2 for OpenVMS (was: Re: PGP for OpenVMS?)1 Message-ID: <hKBe8.167$fL6.4426@news.cpqcorp.net>   L In article <a55vmf$2nn$1@aquila.mdx.ac.uk>, david20@alpha1.mdx.ac.uk writes:X :In article <C2256B68.005F2099.00@jklh21.valmet.com>, norm.raphael@jamesbury.com writes: :> :>; :>Can anyone confirm or deny or elaborate on the following:  :>P :>"The latest mention of it on comp.os.vms from Glenn and Mary Everhart suggestsO :>it's on the Fall 2001 Sig Tapes in the [NET] directory. I haven't looked so I C :>don't know whether this is still GNUPG 1.0.4 or a later version."  :> :>-Norm  :> : 4 :I've now looked on ftp://mvb.saic.com/vmslt01b/net/! :and it appears to be GNUPG 1.0.6  : ( :However the file is in .TAR-BZ2 format.N :I seem to recall seeing a decompression program which could handle .BZ2 filesM :some time ago on VMS but haven't got it on my system. I'd expect to find the L :decompression tools on the same system as the ftp archive but can't seem toK :spot them. Anyone know where I can pick up a tool to decompress this file.     +   I ported a version of bzip2 a while back.   <     http://www.openvms.compaq.com/freeware/freeware50/bzip2/  F   If y'all get a decent/recent PGP port, please pass along a kit (for >   the next Freeware) or a pointer (for the next FAQ).  Thanks!  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 25 Feb 2002 18:05:28 -0800 # From: "Tom Linden" <tom@kednos.com> : Subject: RE: BZIP2 for OpenVMS (was: Re: PGP for OpenVMS?)9 Message-ID: <CIEJLCMNHNNDLLOOGNJIIEKAEDAA.tom@kednos.com>   I This is used to unpack the bash kit and you can get it on sourceforge.com    > -----Original Message-----; > From: Hoff Hoffman [mailto:hoffman@xdelta.zko.dec.nospam] ) > Sent: Monday, February 25, 2002 5:43 PM  > To: Info-VAX@Mvb.Saic.Com < > Subject: Re: BZIP2 for OpenVMS (was: Re: PGP for OpenVMS?) >  > . > In article <a55vmf$2nn$1@aquila.mdx.ac.uk>, " > david20@alpha1.mdx.ac.uk writes:8 > :In article <C2256B68.005F2099.00@jklh21.valmet.com>, $ > norm.raphael@jamesbury.com writes: > :> > :>= > :>Can anyone confirm or deny or elaborate on the following:  > :>A > :>"The latest mention of it on comp.os.vms from Glenn and Mary   > Everhart suggests > > :>it's on the Fall 2001 Sig Tapes in the [NET] directory. I  > haven't looked so I E > :>don't know whether this is still GNUPG 1.0.4 or a later version."  > :>	 > :>-Norm  > :> > : 6 > :I've now looked on ftp://mvb.saic.com/vmslt01b/net/# > :and it appears to be GNUPG 1.0.6  > : * > :However the file is in .TAR-BZ2 format.? > :I seem to recall seeing a decompression program which could   > handle .BZ2 files D > :some time ago on VMS but haven't got it on my system. I'd expect 
 > to find the A > :decompression tools on the same system as the ftp archive but   > can't seem to C > :spot them. Anyone know where I can pick up a tool to decompress   > this file. >  > - >   I ported a version of bzip2 a while back.  > > >     http://www.openvms.compaq.com/freeware/freeware50/bzip2/ > H >   If y'all get a decent/recent PGP port, please pass along a kit (for @ >   the next Freeware) or a pointer (for the next FAQ).  Thanks! > 3 >  ---------------------------- #include <rtfaq.h>   > ----------------------------- 6 >       For additional, please see the OpenVMS FAQ --  > www.openvms.compaq.com    5 >  --------------------------- pure personal opinion   > --------------------------- 4 >    Hoff (Stephen) Hoffman   OpenVMS Engineering    > hoffman#xdelta.zko.dec.com >    ------------------------------  + Date: Mon, 25 Feb 2002 21:35:53 -0300 (BRT)  From: valdemir-@uol.com.br Subject: Edit/TPU question... 5 Message-ID: <200202260035.VAA27924@wright.uol.com.br>    Hello all VMS Users:  @   I=B4d like know when I=B4m using Edit/tpu, which keys sequence:   I need press to go to the end of file ( like PF1-4 in=20   Edit/EDT...).      Thanks...    ------------------------------  # Date: Tue, 26 Feb 2002 01:01:58 GMT ' From: Don Sykes <anonymous@pacbell.net> ! Subject: Re: Edit/TPU question... + Message-ID: <3C7ADF6C.E06A7C97@pacbell.net>   B Just enter, "set key edt" first, then you can use EDT keypad keys.   valdemir-@uol.com.br wrote:  >  > Hello all VMS Users: > > >   Id like know when Im using Edit/tpu, which keys sequence9 >   I need press to go to the end of file ( like PF1-4 in  >   Edit/EDT...).  > 
 >   Thanks...    --     Have VMS. Will Travel. Wire Paladin @alphase.com 
 San Francisco    ------------------------------  % Date: Tue, 26 Feb 2002 12:23:43 +1100 / From: "Phil Howell" <phowell@snowyhydro.com.au> ! Subject: Re: Edit/TPU question... 1 Message-ID: <CtBe8.1403$936.56709@ozemail.com.au>   ' <valdemir-@uol.com.br> wrote in message / news:200202260035.VAA27924@wright.uol.com.br...  Hello all VMS Users:  <   Id like know when Im using Edit/tpu, which keys sequence7   I need press to go to the end of file ( like PF1-4 in    Edit/EDT...).      Thanks... " Use the PF4 key to "enter command"3 If you know EDT then the easy way is SET KEYPAD EDT ? otherwise SET GOLD PF1 then GOLD+downarrow takes you to the end  Phil   ------------------------------  % Date: Mon, 25 Feb 2002 21:18:15 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> ! Subject: Re: Edit/TPU question... , Message-ID: <3C7AF066.ED787A38@videotron.ca>   valdemir-@uol.com.br wrote: > >   Id like know when Im using Edit/tpu, which keys sequence9 >   I need press to go to the end of file ( like PF1-4 in  >   Edit/EDT...).   3 I don't think that there is one defined by default.    [DO] define  command: BOTTOM 4 key: any key you want (numeric keypad or PFkey etc).   other command: TOP  N (if you don't have the [DO] KEY (F16), you can use PF4 (upper rightmost key on numeric keypad)    ------------------------------  # Date: Tue, 26 Feb 2002 04:35:53 GMT ! From: Andy <acs@fcgnet.works.net> ! Subject: Re: Edit/TPU question... > Message-ID: <Xns91C0EFA964EE9acsfcgnetworksnet@216.166.71.232>  ; JF Mezei <jfmezei.spamnot@videotron.ca> enlightened us with % news:3C7AF066.ED787A38@videotron.ca:     > valdemir-@uol.com.br wrote: ? >>   Id like know when Im using Edit/tpu, which keys sequence : >>   I need press to go to the end of file ( like PF1-4 in >>   Edit/EDT...). > 5 > I don't think that there is one defined by default.    Can I play too/also ? :-).  < Two more choices (besides going for the EDT keypad route...)  = $ DEFINE SYS$LOGIN:EVE.INIT ! If not already defined in your  9 $                           ! login.com or somewhere else  $ EDIT EVE$INIT    SET KEYPAD WPS   <CTRL-Z>   [Mine actually looks like: !  SET KEYPAD WPS DEFINE KEY=GOLD/1 ONE WINDOW DEFINE KEY=GOLD/2 TWO WINDOW DEFINE KEY=GOLD/G GET FILE DEFINE KEY=GOLD/I INCLUDE FILE DEFINE KEY=GOLD/M SPAWN MAIL DEFINE KEY=GOLD/O OTHER WINDOW DEFINE KEY=GOLD/S SPELL  DEFINE KEY=GOLD/Z WHAT LINE  !   = and dates from back 10 years ago when I lived inside ALL-IN-1 @ and used WPS-Plus. Now-a-days I [mostly] use the DO key instead.    Then PF1-B = bottom/ PF1-T = top    ; Or.... why bother going for a shortcut when the real thing   works just as well     Bottom:    <DO> Command: bot   Top:   <DO> Command: Top   Hope that helps....    -Andy- --     ------------------------------  # Date: Tue, 26 Feb 2002 05:36:22 GMT ! From: Andy <acs@fcgnet.works.net> ! Subject: Re: Edit/TPU question... = Message-ID: <Xns91C15B7AD303acsfcgnetworksnet@216.166.71.232>   0 Andy <acs@fcgnet.works.net> enlightened us with 6 news:Xns91C0EFA964EE9acsfcgnetworksnet@216.166.71.232:   Oops...   ? > $ DEFINE SYS$LOGIN:EVE.INIT ! If not already defined in your  ; > $                           ! login.com or somewhere else    I meant something like:   $ $ DEFINE EVE$INIT SYS$LOGIN:EVE.INIT       -Andy-   ------------------------------  % Date: Tue, 26 Feb 2002 00:42:31 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> ! Subject: Re: Edit/TPU question... , Message-ID: <3C7B2043.6891E211@videotron.ca>   Andy wrote:  > SET KEYPAD WPS  K Tisk tisk ! This is like a male admitting to eating quiche :-) :-) :-) :-)    D I don't have the keypad set to WPS, but I have key mappings such as * <gold><left arrow> to get to start of line) <gold><right arrow> to get to end of linen  G But I still use WPSPLUS for emails. (much better for word wrapping etc,pI besides, my SMTP and POP gateways runs under message router). What I findtN myself though is trying to use the mouse while inside wpsplus and realising it
 isn't TPU ...T  ? > and dates from back 10 years ago when I lived inside ALL-IN-1   N Oh oh... you have a clone running on my all mighty Microvax II :-) :-) :-) :-) :-) Which module are you in ?l  G You wouldn't happen to have the documentation on how to access built-in K functions by any chance, would you ? (I have the doc on how to add externalhM functions (install/execute), but not how to make built-in functions that havea access to symbols etc).E   ------------------------------  # Date: Tue, 26 Feb 2002 05:56:46 GMTt! From: Andy <acs@fcgnet.works.net>a! Subject: Re: Edit/TPU question...e= Message-ID: <Xns91C192D23336acsfcgnetworksnet@216.166.71.232>   ; JF Mezei <jfmezei.spamnot@videotron.ca> enlightened us with % news:3C7B2043.6891E211@videotron.ca: V  @ >> and dates from back 10 years ago when I lived inside ALL-IN-1      @ > You wouldn't happen to have the documentation on how to accessB > built-in functions by any chance, would you ? (I have the doc onA > how to add external functions (install/execute), but not how toa; > make built-in functions that have access to symbols etc).e  @ Notice the "10 years ago"... not something I ever tried to do...B though it was probably mentioned in one of the Tony Redmond books.@ The only ALL-IN-1 documentation I have now is whatever is on the current CD set.n   -Andy-   ------------------------------  % Date: Tue, 26 Feb 2002 07:44:36 +0100 ( From: Paul Sture <paul.sture@bluewin.ch>! Subject: Re: Edit/TPU question...e) Message-ID: <3C7B2ED4.3080304@bluewin.ch>n   Andy wrote:   2 > Andy <acs@fcgnet.works.net> enlightened us with 8 > news:Xns91C0EFA964EE9acsfcgnetworksnet@216.166.71.232: > 	 > Oops...o >  > ? >>$ DEFINE SYS$LOGIN:EVE.INIT ! If not already defined in your d; >>$                           ! login.com or somewhere elser >> >  > I meant something like:  > & > $ DEFINE EVE$INIT SYS$LOGIN:EVE.INIT >      Another one, much simpler:     $ DEFINE EVE$KEYPAD EDTo __  
 Paul Sture Switzerlandi   ------------------------------  % Date: Tue, 26 Feb 2002 14:04:30 +1300t# From: Bruce Hoult <bruce@hoult.org> " Subject: expensive procedure calls> Message-ID: <bruce-C81EAF.14043026022002@news.paradise.net.nz>  G In article <name99-2502021512250001@handma2.apple.com>, name99@mac.com   (Maynard Handley) wrote:  K > Ah, once again the "blindingly fast because of no function call overhead"AH > claim. If you look at any decent RISC machine (like a PPC) there IS noI > function call "overhead". The set of things that are done on a functionjI > call is exactly the same as the set of things that are done in a set of1  > goto's faking a function call.  H This is even more true when you have a compiler that supports tail-call  elimination.  G See Guy Steele's 1977 paper: "Debunking the 'Expensive Procedure Call' NI Myth, or, Procedure Call Implementations Considered Harmful, or, Lambda: nB The Ultimate GOTO". MIT AI Lab. AI Lab Memo AIM-443. October 1977.  +    http://library.readscheme.org/page1.htmle@    ftp://publications.ai.mit.edu/ai-publications/pdf/AIM-443.pdf  E It's about the PDP-10, but the same things apply to modern RISCs too.E   -- Bruce   ------------------------------  % Date: Mon, 25 Feb 2002 20:58:10 +0100e- From: Didier Morandi <Didier.Morandi@Free.fr>s9 Subject: Re: F$EXTRACT does parsing before giving result?n' Message-ID: <3C7A9753.61BEE197@Free.fr>a   I agree.   "Alan E. Feldman" wrote: > + > But ***in your original post*** you wroteV >  >     (today = f$time()) >  > which is clearly not >  >     today = "f$time()" > H > as you wrote in the post quoted at the top of this post. That's why he" > wrote what he did. He was right.   ------------------------------  # Date: Tue, 26 Feb 2002 00:20:03 GMTe" From: "jleonard" <jleonard@iol.ie> Subject: Ftp/copy problemp- Message-ID: <TwAe8.5432$D6.15424@news.iol.ie>e  E Large text file, created by a datatrieve procedure is tranferred to a L machine running NT4 Server using a ftp/copy command. The File is large circaJ 200MB. Attempting to import the text file into an access 97 database failsH if attempted before nearly 70 minutes have elapsed from when transfer isK complete. The error indicates either a permission issue or that the file is D already in use. Once sufficient time has elapsed, the importation isI allowed. This outcome is reproducible on this machine. Any views would beyJ appreciated, especially with a solution. The transfer is by anonymous ftp,C and the sharing of the windows side folder should allow access. The E importation is run either interactively or from a batch file run as an0 scheduled service under Administrator privilege. Thanks for your attention, John   ------------------------------  % Date: Mon, 25 Feb 2002 21:11:12 -0500s- From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Re: Ftp/copy problema, Message-ID: <3C7AEEBF.ED5A614F@videotron.ca>   jleonard wrote:.L > 200MB. Attempting to import the text file into an access 97 database failsJ > if attempted before nearly 70 minutes have elapsed from when transfer is > complete.   K On NT, does a process get created by the FTP transfer ? Is it possible thatF= the process on NT remains active with some lock on the file ?p  L (is there the equivalent of SHOW DEV/FILES/NOSYS on NT ? that would give you2 information on who has got the file still locked).  @ The 70 minutes sounds like some idle timeout for the FTP server.   ------------------------------  # Date: Tue, 26 Feb 2002 03:12:20 GMTo2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Ftp/copy problema1 Message-ID: <o2De8.173$fL6.4384@news.cpqcorp.net>   R In article <TwAe8.5432$D6.15424@news.iol.ie>, "jleonard" <jleonard@iol.ie> writes:F :Large text file, created by a datatrieve procedure is tranferred to aM :machine running NT4 Server using a ftp/copy command. The File is large circagK :200MB. Attempting to import the text file into an access 97 database fails I :if attempted before nearly 70 minutes have elapsed from when transfer isrL :complete. The error indicates either a permission issue or that the file isE :already in use. Once sufficient time has elapsed, the importation is J :allowed. This outcome is reproducible on this machine. Any views would beK :appreciated, especially with a solution. The transfer is by anonymous ftp, D :and the sharing of the windows side folder should allow access. TheF :importation is run either interactively or from a batch file run as a1 :scheduled service under Administrator privilege.D  H   Check for an active network connection from the (unspecified) OpenVMS B   TCP/IP client to the (unspecified) Windows FTP client or server.  F   If there is no connection, this would appear to be an odd newsgroup G   for what would then appear to be a Microsoft Access question.  Sure,  H   the data came over from Compaq OpenVMS (hopefully via COPY/FTP).  But H   it transfers to and loads into Access correctly after some delay, and C   thus your question is centrally on the cause of the delay on the  H   Microsoft Windows system.  This oddity would thus certainly appear to C   be specific to the Microsoft Windows platform, and to how Access rE   decides what (and when) it can import, or (potentially) on how the sE   Windows FTP client (or server, depending on the direction) decides i   to release the file.  G   When posting, please consider providing the information encouraged bytH   the "how to ask questions" section of the OpenVMS FAQ.  Specifically, G   the platform, product, version, and ECO information that is requested:H   by the FAQ.  In cases such as this, the exact command used can also beH   of use.  Without these (and potentially other) details, we can really    only guess at the cause.  I   Check for and apply OpenVMS ECOs and any ECO(s) that might be availablemG   for the particular IP stack installed on OpenVMS.  Also check for anyt@   hotfixes or service packs for Microsoft Windows and/or Access.    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 25 Feb 2002 21:28:08 -0600iC From: "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com>o Subject: Re: Ftp/copy problem H Message-ID: <craig.berry-B84671.21280825022002@news.directvinternet.com>  G I have heard of similar things before, i.e., something hanging because tE a file long since uploaded from VMS to NT is still open for write or pA locked in some way.  The best NT guy I ever knew told me, when I gC offered to help analyze the situation, "Don't worry about it, it's tA always on the NT side."  Dunno whether he was right, but it says -H something about where to check first.  I believe there are utilities on G the NT resource kit that would allow you to check whether anything has   the file open, etc.  -  B The situation could be highly dependent on your TCP/IP vendor and H assorted software versions, ECOs, service packs, and so on.  Also, your G FTP client and server may or may not be the default ones; if they are, TF try something different.  In particular, on the VMS side, try MadGoat  FTP (now simply HGFTP) from = <http://vms.process.com/scripts/fileserv/fileserv.com?HGFTP>.t    - In article <TwAe8.5432$D6.15424@news.iol.ie>,o$  "jleonard" <jleonard@iol.ie> wrote:  G > Large text file, created by a datatrieve procedure is tranferred to aoN > machine running NT4 Server using a ftp/copy command. The File is large circaL > 200MB. Attempting to import the text file into an access 97 database failsJ > if attempted before nearly 70 minutes have elapsed from when transfer isM > complete. The error indicates either a permission issue or that the file is F > already in use. Once sufficient time has elapsed, the importation isK > allowed. This outcome is reproducible on this machine. Any views would be L > appreciated, especially with a solution. The transfer is by anonymous ftp,E > and the sharing of the windows side folder should allow access. TheUG > importation is run either interactively or from a batch file run as a 2 > scheduled service under Administrator privilege. > Thanks for your attention, > John >  >r   ------------------------------  % Date: Tue, 26 Feb 2002 10:49:56 +0530n, From: "Rai, Amlesh" <amlesh.rai@digital.com># Subject: FW: Powerpoint competitionoP Message-ID: <7A98AEDB54C13647BBCB33E3FFEF4942227B04@DPEXCH01.digitalindiasw.net>   -----Original Message-----4 From: JF Mezei [mailto:jfmezei.spamnot@videotron.ca]) Sent: Tuesday, February 26, 2002 10:45 AMs To: Info-VAX@Mvb.Saic.Comd Subject: Powerpoint competition      http://www.Mew.org/mgp/s  @ Has a downloadable product for x-windows (linux) that supposedly competes) against Powerpoint to make presentations.   E However, to download it, one needs "cvs" to the host toget the files.- What is- "CVS " ?????   ------------------------------  % Date: Tue, 26 Feb 2002 07:25:25 +0100n/ From: Frederik Meerwaldt <frederik@freddym.org>.' Subject: Re: FW: Powerpoint competition-/ Message-ID: <a5f9o1$99a$04$1@news.t-online.com>-   Hi,-  D this doesn't really belong in a VMS Newsgroup, but CVS does as it is ported to VMS, too   > http://www.Mew.org/mgp/- > B > Has a downloadable product for x-windows (linux) that supposedly
 > competes+ > against Powerpoint to make presentations.0 > G > However, to download it, one needs "cvs" to the host toget the files.k	 > What isB > "CVS " ?????  B CVS is Concurrent Versions System see www.cvshome.org for details.   ------------------------------  # Date: Tue, 26 Feb 2002 02:05:39 GMT-2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)S Subject: Re: Getting VMS running on alphapc 150 - any help or pointers appreciated. 1 Message-ID: <T3Ce8.168$fL6.4381@news.cpqcorp.net>t  b In article <FjEd8.5$Cz3.130@read2.inet.fi>, "PLZI" <janne.peltola@eisikanautaa.sonera.com> writes:  K   Since this box reportedly worked before, the problem here probably isn't  J   with the firmware of the SCSI controller nor the graphics controller, itH   is probably a problem or an incompatibility somewhere within the SCSI D   chain.  But I will mention these other possibilities below, too...  H :I have Alpha AXP 150 minitower, complete with loads of RAM (80MB), scsi$ :controller, cd-rom and whatnot. ...  F   Whatnot here -- such as the particular graphics controller installedK   in the system -- is exceedingly important.   OpenVMS supports relatively e1   few graphics controllers in this configuration.g  G   I will assume you have switched over to or are otherwise running the i-   SRM console, of course.  Not ARC/AlphaBIOS.   K :Originally it had DEC-made hard disks, a 3gig and a 5gig drives, if memoryY? :serves. I distinctly remember installing OpenVMS 7.2 or 7.3...   H   The DEC 2000 -- this is the name of the DECpc 150 AXP when running SRMH   and OpenVMS and such -- is one of the few Alpha systems that have beenK   retired by OpenVMS Engineering; this is one of the few that is no longer d   officially supported.   . ..and it booted happily. I had no PAK's at theK :time, so it merely booted to DCL, and complained about the missing product K :keys. Then one of the HD's gave finally in, and I stored the thing away. A]8 :year and a half later, I decided to give it another go. :yJ :Now, I have quite a large selection of miscellaneous scsi drives,  but itJ :seems the machine is *very* picky. Most of the larger (say, 8 gig) drivesL :get recognized wrong by the firmware. Put an 8 gig drive in, it claims it'sH :a 500MB or so. Put a 4 gig drive in, it says it's a 100MB drive. I haveK :exactly one drive, a fujitsu 2 gig, which seems to get reported correctly.iE :Why does this happen, any ideas? The firmware is the latest version, K :installed by compaq's firmware utility (it claimed that no OpenVMS 7.3 foru :me if I do not upgrade it).  I   This system has a SCSI implementation that is exceedingly sensitive to  H   the length of the SCSI, and to the particular SCSI devices.  You must F   keep the entire (internal) 1742A cable inside the box, use a second G   1740A to get outside the box -- this 1740A is the same as the 1742A,  G   sans the floppy.  Both the 1742A and the 1740A firmware ROMs must be  H   at revision "G.1".  (The DEC 2000 series console should display "G.1" @   -- if that is what you have, of course.  Not "G".  Not "H".)    G   Also see the FAQ for the required SCSI ECOs, depending on the OpenVMS/G   release in use here -- there are some configurations and combinationsEE   of versions that can encounter drive- or capacity-related problems.   E :Oh, one more thing. How do I really, really low-level format a scsi e: :drive on this box? Without a hammer and a chisel, I mean.  C   Ignoring the truely rich set of possible humorous answers here...aG   With OpenVMS Alpha running, you can use the INITIALIZE/ERASE command.      N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 25 Feb 2002 14:01:39 -0500I, From: Mark Schafer <mark.schafer@compaq.com>$ Subject: I: PAKGEN Software for ISVs) Message-ID: <3C7A8A13.6050207@compaq.com>    PAKGEN Software for ISVs  F PAKGEN (which produces LMF PAKs for software) is now available to CSA  members upon request.0  B Members may request this offering at no charge by filling out the H Request for Technical Support form <http://csa.compaq.com/csa.asp>.  In H your request, put "PAKGEN" in the Subject field and the requested TOKEN > string in the text box called 'Your Request or Concern'.  CSA C TechSupport will open a case for the request and forward it to the aC License Key manager.  The manager will issue a PAKGEN key with the  @ requested TOKEN string and e-mail the key file to the requester.  D Download these documents from the CSA Members Only website: "PAKGEN B Software for ISVs" (MS WORD) and the "DEC VMS/LMF System Services  Reference Manual" (PDF).   ------------------------------  # Date: Mon, 25 Feb 2002 19:42:14 GMTh From: system@SendSpamHere.ORG ( Subject: Re: I: PAKGEN Software for ISVs0 Message-ID: <00A0A193.1436C784@SendSpamHere.ORG>  X In article <3C7A8A13.6050207@compaq.com>, Mark Schafer <mark.schafer@compaq.com> writes: >u >( >PAKGEN Software for ISVsd >tG >PAKGEN (which produces LMF PAKs for software) is now available to CSA n >members upon request. >bC >Members may request this offering at no charge by filling out the 2I >Request for Technical Support form <http://csa.compaq.com/csa.asp>.  In uI >your request, put "PAKGEN" in the Subject field and the requested TOKEN  ? >string in the text box called 'Your Request or Concern'.  CSA eD >TechSupport will open a case for the request and forward it to the D >License Key manager.  The manager will issue a PAKGEN key with the A >requested TOKEN string and e-mail the key file to the requester.h   Done...     E >Download these documents from the CSA Members Only website: "PAKGEN ,C >Software for ISVs" (MS WORD) and the "DEC VMS/LMF System Services l >Reference Manual" (PDF).y >s   URL???   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             .J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbes0   ------------------------------  % Date: Mon, 25 Feb 2002 15:27:35 -0500E, From: Mark Schafer <mark.schafer@compaq.com>( Subject: Re: I: PAKGEN Software for ISVs) Message-ID: <3C7A9E37.4090005@compaq.com>t   system@SendSpamHere.ORG wrote:  Z > In article <3C7A8A13.6050207@compaq.com>, Mark Schafer <mark.schafer@compaq.com> writes: >  >> >>PAKGEN Software for ISVs >>H >>PAKGEN (which produces LMF PAKs for software) is now available to CSA  >>members upon request.E >>D >>Members may request this offering at no charge by filling out the J >>Request for Technical Support form <http://csa.compaq.com/csa.asp>.  In J >>your request, put "PAKGEN" in the Subject field and the requested TOKEN @ >>string in the text box called 'Your Request or Concern'.  CSA E >>TechSupport will open a case for the request and forward it to the 0E >>License Key manager.  The manager will issue a PAKGEN key with the tB >>requested TOKEN string and e-mail the key file to the requester. >> > 	 > Done...l >  >  > F >>Download these documents from the CSA Members Only website: "PAKGEN D >>Software for ISVs" (MS WORD) and the "DEC VMS/LMF System Services  >>Reference Manual" (PDF). >> >> >  > URL???    - http://csa.compaq.com/CSA_Members_Login.shtml    ------------------------------  # Date: Mon, 25 Feb 2002 23:11:19 GMT  From: system@SendSpamHere.ORGe( Subject: Re: I: PAKGEN Software for ISVs0 Message-ID: <00A0A1B0.49B9DD0A@SendSpamHere.ORG>  X In article <3C7A9E37.4090005@compaq.com>, Mark Schafer <mark.schafer@compaq.com> writes: >system@SendSpamHere.ORG wrote:i >r[ >> In article <3C7A8A13.6050207@compaq.com>, Mark Schafer <mark.schafer@compaq.com> writes:f >> t >>>o >>>PAKGEN Software for ISVsh >>>aI >>>PAKGEN (which produces LMF PAKs for software) is now available to CSA   >>>members upon request. >>> E >>>Members may request this offering at no charge by filling out the EK >>>Request for Technical Support form <http://csa.compaq.com/csa.asp>.  In eK >>>your request, put "PAKGEN" in the Subject field and the requested TOKEN  A >>>string in the text box called 'Your Request or Concern'.  CSA eF >>>TechSupport will open a case for the request and forward it to the F >>>License Key manager.  The manager will issue a PAKGEN key with the C >>>requested TOKEN string and e-mail the key file to the requester.0 >>>0 >> e
 >> Done... >> " >> o >> iG >>>Download these documents from the CSA Members Only website: "PAKGEN .E >>>Software for ISVs" (MS WORD) and the "DEC VMS/LMF System Services e >>>Reference Manual" (PDF).T >>>v >>>i >> f	 >> URL???m >. >e. >http://csa.compaq.com/CSA_Members_Login.shtml >h >e  I Takes me to a BIG GRAY SCREEN.  Seeing as how Compaq's CSA site has nevereI supported Netscape on VMS, I have never known my username/password to ac-a" cess the CSA site even if I could.  I My FAX machine is in possession of the license key to run PAKGEN but aloto@ of good it will do me because I can't access it on the CSA site. --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             fJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesi   ------------------------------    Date: 25 Feb 2002 19:10:06 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen):( Subject: Re: I: PAKGEN Software for ISVs3 Message-ID: <jx45EQhl1vqA@eisner.encompasserve.org>e  X In article <3C7A8A13.6050207@compaq.com>, Mark Schafer <mark.schafer@compaq.com> writes: >  >  > PAKGEN Software for ISVs > H > PAKGEN (which produces LMF PAKs for software) is now available to CSA  > members upon request.   B Is this software available on physical media ?  Your post seems to@ discuss only transfer of the license key and the documentation ?  > Does this software run on Alpha VMS, or is it still VAX-only ?  D > Members may request this offering at no charge by filling out the J > Request for Technical Support form <http://csa.compaq.com/csa.asp>.  In J > your request, put "PAKGEN" in the Subject field and the requested TOKEN @ > string in the text box called 'Your Request or Concern'.  CSA E > TechSupport will open a case for the request and forward it to the cE > License Key manager.  The manager will issue a PAKGEN key with the eB > requested TOKEN string and e-mail the key file to the requester. > F > Download these documents from the CSA Members Only website: "PAKGEN D > Software for ISVs" (MS WORD) and the "DEC VMS/LMF System Services  > Reference Manual" (PDF).   ------------------------------    Date: 25 Feb 2002 20:38:30 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)n( Subject: Re: I: PAKGEN Software for ISVs3 Message-ID: <Y9gaxqDoyxkf@eisner.encompasserve.org>i  c In article <jx45EQhl1vqA@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:yZ > In article <3C7A8A13.6050207@compaq.com>, Mark Schafer <mark.schafer@compaq.com> writes: >>   >> d >> PAKGEN Software for ISVsi >>  I >> PAKGEN (which produces LMF PAKs for software) is now available to CSA u >> members upon request. > D > Is this software available on physical media ?  Your post seems toB > discuss only transfer of the license key and the documentation ? > @ > Does this software run on Alpha VMS, or is it still VAX-only ?  = And if the former, will it generate Type-1 PAKS (required for  VMS V5.0 and VMS V5.1) ?  E >> Members may request this offering at no charge by filling out the tK >> Request for Technical Support form <http://csa.compaq.com/csa.asp>.  In uK >> your request, put "PAKGEN" in the Subject field and the requested TOKEN wA >> string in the text box called 'Your Request or Concern'.  CSA iF >> TechSupport will open a case for the request and forward it to the F >> License Key manager.  The manager will issue a PAKGEN key with the C >> requested TOKEN string and e-mail the key file to the requester.e >> fG >> Download these documents from the CSA Members Only website: "PAKGEN gE >> Software for ISVs" (MS WORD) and the "DEC VMS/LMF System Services f >> Reference Manual" (PDF).d   ------------------------------  # Date: Tue, 26 Feb 2002 02:56:59 GMTa2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)( Subject: Re: I: PAKGEN Software for ISVs1 Message-ID: <%PCe8.172$fL6.4227@news.cpqcorp.net>h  X In article <3C7A8A13.6050207@compaq.com>, Mark Schafer <mark.schafer@compaq.com> writes: :h :PAKGEN Software for ISVsl : G :PAKGEN (which produces LMF PAKs for software) is now available to CSA f :members upon request.    @   Available on OpenVMS VAX and OpenVMS Alpha, on V7.2 and later.      N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 26 Feb 2002 03:36:45 GMTo1 From: "David J. Dachtera" <djesys.nospam@fsi.net>g( Subject: Re: I: PAKGEN Software for ISVs' Message-ID: <3C7B0434.A86773C8@fsi.net>h   Mark Schafer wrote:t >  > PAKGEN Software for ISVs > G > PAKGEN (which produces LMF PAKs for software) is now available to CSAe > members upon request.e > C > Members may request this offering at no charge by filling out the I > Request for Technical Support form <http://csa.compaq.com/csa.asp>.  In,I > your request, put "PAKGEN" in the Subject field and the requested TOKENu? > string in the text box called 'Your Request or Concern'.  CSAhD > TechSupport will open a case for the request and forward it to theD > License Key manager.  The manager will issue a PAKGEN key with theB > requested TOKEN string and e-mail the key file to the requester. > E > Download these documents from the CSA Members Only website: "PAKGENrC > Software for ISVs" (MS WORD) and the "DEC VMS/LMF System ServicesG > Reference Manual" (PDF).  
 Gentlemen,  A My congratulations on a significant step forward! Wonderful news!@  B Many of us hope that this bit of momentum will propagate into even greater momentum.   F In any journey, every step is important. This one is *VERY* important.= It brings the ISVs much closer the OpenVMS market by reducingn  development costs significantly.  @ Now: what can be done to bring the end-users closer to the ISVs?   -- s David J. Dachterae dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Mon, 25 Feb 2002 23:44:46 +0100l' From: Brass Christof <welcome@spam.net> F Subject: Re: IBM says they have best real time mainframe, where's VMS?( Message-ID: <3C7ABE5E.9C4A70C9@spam.net>   Phillip Helbig wrote:s > 7 > > Interesting use of words. Banks aren't "real time".a > J > Based on my own experience, the processing of transactions involving theJ > transfer of money into my account is done in batch mode, at the quickestJ > overnight but sometimes it takes several days.  However, when I withdrawJ > funds from my account, the debit is noted in real time.  If you have twoH > ATM cards, synchronise watches before giving one to someone travellingI > half-way around the world.  Arrange that one of you will withdraw funds,E > up to the withdrawal limit at a given time and the other should tryrH > again a few seconds later.  That's real-time processing (or, at least, > almost real-time).  F I know that you know that the two watches will not be synchronised ...	 Remember?,   -- n6 moc dot slupofni at ssarb - please revert the sequence   ------------------------------  # Date: Mon, 25 Feb 2002 23:13:16 GMT 4 From: Tim Llewellyn <tim.llewellyn@blueyonder.co.uk>F Subject: Re: IBM says they have best real time mainframe, where's VMS?/ Message-ID: <3C7AC3EE.E0F5A65@blueyonder.co.uk>    Brass Christof wrote:o >  > Phillip Helbig wrote:S > > 9 > > > Interesting use of words. Banks aren't "real time".  > > L > > Based on my own experience, the processing of transactions involving theL > > transfer of money into my account is done in batch mode, at the quickestL > > overnight but sometimes it takes several days.  However, when I withdrawL > > funds from my account, the debit is noted in real time.  If you have twoJ > > ATM cards, synchronise watches before giving one to someone travellingK > > half-way around the world.  Arrange that one of you will withdraw fundshG > > up to the withdrawal limit at a given time and the other should try4J > > again a few seconds later.  That's real-time processing (or, at least, > > almost real-time). > H > I know that you know that the two watches will not be synchronised ... > Remember?b >   3 who needs watches if you've both got mobile phones?r  G You could even issue the request simultaneously (give or take the speed  of light factors).  O I'd definitely recommed setting up a test account specifically for this purposeh% if you wanted to try it (I don't) :-)i   regards  -- 8 Tim.Llewellyn@cableinet.co.uk  n  C Standard disclaimer applies. My views in no way represent those of t! my employers or service provider.-   ------------------------------  % Date: Mon, 25 Feb 2002 18:22:01 -0500c- From: JF Mezei <jfmezei.spamnot@videotron.ca>aF Subject: Re: IBM says they have best real time mainframe, where's VMS?, Message-ID: <3C7AC716.58830D5D@videotron.ca>   Tim Llewellyn wrote:5 > who needs watches if you've both got mobile phones?e > I > You could even issue the request simultaneously (give or take the speed  > of light factors).  L But bank transactions are not real time. If you both press at the same time,H one of them will go first, but you can't predict which one. And the bank. doesn't garantee a response time for its ATMs.  M If your transaction takes an extra second to execute, you don't notice. But aoL true real-time system, a random delay of up to one second could kill people.  & real time != interactive/transactional   ------------------------------  % Date: Tue, 26 Feb 2002 00:51:04 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca>a Subject: If you need PI....s, Message-ID: <3C7B2244.22B3AB18@videotron.ca>  L http://3.141592653589793238462643383279502884197169399375105820974944592.jp/  N I am not sure if the page ever finishes, but it definitely will give you PI to> far more precision that even 64 bit Alpha can take :-) :-) :-)  N Note that on my MAC, that URL is too long and gets truncated to 65 characters. in that case, you cani http://202.224.192.18r    G nslookup on VMS is able to translate the domain name to the IP address.t   ------------------------------  + Date: Mon, 25 Feb 2002 20:21:41 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>s% Subject: interesting INQUIRER articlea; Message-ID: <01KEPCJWWT9Y8ZLH6V@sysdev.deutsche-boerse.com>o  F I rarely post URL's to "trade rag" articles, but this one seems worth - it.  (Perhaps someone has already posted it.)m  *    http://www.theinquirer.net/22020211.htm  1 What did this guy do to earn a $26 million bonus?   F ANY objective reading of the situation would say that the guy was not > good for the company, regardless of what one thinks about VMS.   ------------------------------  % Date: Mon, 25 Feb 2002 14:54:58 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca>r) Subject: Re: interesting INQUIRER articlee, Message-ID: <3C7A968B.B5395ED0@videotron.ca>   Phillip Helbig wrote:a, >    http://www.theinquirer.net/22020211.htm > 3 > What did this guy do to earn a $26 million bonus?i > G > ANY objective reading of the situation would say that the guy was not-@ > good for the company, regardless of what one thinks about VMS.  M What the article failed to mention is what happened between the time Pfeifferq6 was sacked and Capellas was put in charge permanently.  L Capellas had been put in charge as a lame duck place holder while they wouldH be seeking a permanent big cheese for Compaq. The problem is that nobodyK wanted the job so after a lengthy unsuccesful search with many refusals for>L job offers, Compaq turned to the stand-by place holder and gave him the job.  J The failure was at the board/Rosen level for failing to find a replacement prior to sacking Pfeiffer.  M While Bill Gates continues to brag that he forters innovation etc etc, it haslL become clear that all the wintel business from intel/microsoft to compaq andJ dell are stuck in time, forced to support a glorified version of DOS on anK 8086 and cannot innovate because the minute one manufacturer does somethinguQ different from the others, they get labeled "proprietary, not industry standard"..  N Compaq is no different than the various landline telephone set makers. You canM vary the shape a bit, but in the end, all phones are the same, unless you arerG willing to build a proprietary telephone system with all sorts of fancyMM features internally but that presents the "standard" interface to the rest of 
 the world.  K Compaq cannot innovate in the wintel business because that is the nature ofGK the business. But Compaq could have innovated in its proprietary businessesaL where it controlled everything from the chip to the applications. All it did' was continue projects begun by Digital.d    N Compaq's role model should have been Apple instead of a dual love for Dell andM IBM. And when you look at the few "innovations" from Compaq, guess where theyiS came from ? Can you say iPAQ (the original ones, that looked exactly like an iMAC).n   ------------------------------  % Date: Mon, 25 Feb 2002 21:42:28 +0100N* From: Alexis Cousein <al@brussels.sgi.com> Subject: Re: Itanium troublesS/ Message-ID: <3C7AA1B4.5040708@brussels.sgi.com>r   Nick Maclaren wrote:C > The Itanic sank.  Intel did not expect that.  Not even I expecteddD > quite such a spectacular failure.  Note that I am NOT just talkingE > about performance and delay, but the fact that it plain didn't workNE > and (despite being reengineered AFTER tape-out) couldn't be made tol > work.n  B "Can't be made to work" is an overstatement. There are a number ofF working IA64 boxes around (SGI sells one), and there are even a number? of working *large* IA64 boxes (though not all of them have beenr
 productized)..   --  ? <these messages express my own views, not those of my employer>-) Alexis Cousein				Senior Systems Engineer . SGI Belgium and Luxemburg		al@brussels.sgi.com   ------------------------------  % Date: Mon, 25 Feb 2002 21:49:34 +01003* From: Alexis Cousein <al@brussels.sgi.com> Subject: Re: Itanium troublesc/ Message-ID: <3C7AA35E.5020402@brussels.sgi.com>a   Nick Maclaren wrote: > G > Eh?  I am not talking about performance.  I am talking about the factPF > that the Itanic DID NOT AND DOES NOT WORK.  Even Dell gave up on it. > J The boxes Dell was selling weren't plagued by the incident that Compaq wasD seeing. It's just that Dell doesn't sell in any of the markets where( the first incarnation of IA64 is useful.  E Remember Dell's business model requires volume. The reason Dell isn'tu: selling the boxes has little to do with technical reasons.       -- a? <these messages express my own views, not those of my employer>i) Alexis Cousein				Senior Systems EngineerO. SGI Belgium and Luxemburg		al@brussels.sgi.com   ------------------------------   Date: 25 Feb 2002 22:24:49 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren) Subject: Re: Itanium troublesa0 Message-ID: <a5edjh$ih7$1@pegasus.csx.cam.ac.uk>  / In article <3C7AA1B4.5040708@brussels.sgi.com>,a, Alexis Cousein  <al@brussels.sgi.com> wrote: >Nick Maclaren wrote:-D >> The Itanic sank.  Intel did not expect that.  Not even I expectedE >> quite such a spectacular failure.  Note that I am NOT just talking9F >> about performance and delay, but the fact that it plain didn't workF >> and (despite being reengineered AFTER tape-out) couldn't be made to >> work. >IC >"Can't be made to work" is an overstatement. There are a number ofoG >working IA64 boxes around (SGI sells one), and there are even a numberK@ >of working *large* IA64 boxes (though not all of them have been >productized).  B Given the number of systems that have worked perfectly in test andA demonstration and have been withdrawn as unusable when real users/@ attempt to use them, please permit me my doubts.  I have reasons for my statements.  D For 6 months now, since the official 'down the slipway', I have beenE trying to find any reference sites or evidence of reliability of such ! systems.  So far with no success.m     Regards, Nick Maclaren,* University of Cambridge Computing Service,> New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. Email:  nmm1@cam.ac.uk/ Tel.:  +44 1223 334761    Fax:  +44 1223 334679m   ------------------------------  % Date: Mon, 25 Feb 2002 17:42:42 -0500V- From: JF Mezei <jfmezei.spamnot@videotron.ca>( Subject: Re: Itanium troublesL, Message-ID: <3C7ABDE2.E0C5153B@videotron.ca>   Nick Maclaren wrote:D > Given the number of systems that have worked perfectly in test andC > demonstration and have been withdrawn as unusable when real userssB > attempt to use them, please permit me my doubts.  I have reasons > for my statements.  M But could these problems be due to the microsoft software instead of the chips? ? Or perhaps customers were  unimpressed with the performance ?r  	 Question:   M Would HP-UX which is closely allied to PA-Risc have any performance advantagel- or disadvantage compered to Windows on IA64 ?.  K Is Windows on IA64 fully native, or does it rely on some of the IA64's 8086- emulation ?-   ------------------------------   Date: 25 Feb 2002 22:52:59 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren) Subject: Re: Itanium troubles 0 Message-ID: <a5ef8b$kcf$1@pegasus.csx.cam.ac.uk>  , In article <3C7ABDE2.E0C5153B@videotron.ca>,/ JF Mezei  <jfmezei.spamnot@videotron.ca> wrote:G >Nick Maclaren wrote: E >> Given the number of systems that have worked perfectly in test andSD >> demonstration and have been withdrawn as unusable when real usersC >> attempt to use them, please permit me my doubts.  I have reasonsy >> for my statements.? > N >But could these problems be due to the microsoft software instead of the chip@ >? Or perhaps customers were  unimpressed with the performance ?  B They could.  The little birds that cheeped to me indicated that it0 wasn't the latter problem - bad though that was.  D However, let me give you a very Bowlerized version of an interchange with a major vendor:  D Me:  Is there a specification of XXX?  It is perverse and bug-ridden( and I am going bonkers trying to use it.  A Them:  There are no known bugs in it, but we will help you if youi have problems using it.   0 Me:  !!!!!  I am trying to find a SPECIFICATION.  D Them:  The documentation is what you get, and any conflict with that may be reported as a bug.c  0 Me:  The following is a flagrant conflict - ....  @ Them:  You can resolve your problem by changing your use to ....  6 Me:  !!!!!  I am reporting a BUG in the damn facility!  = Them:  I have spoken to the developers and they say it is note4 supposed to work.  We will change the documentation.  * Me:  I need the bug FIXED, not documented.  > Them:  As it is not supposed to work, there is no bug.  File a request for enhancement.  0 Now, whose fault is it that my code didn't work?     Regards, Nick Maclaren,* University of Cambridge Computing Service,> New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. Email:  nmm1@cam.ac.uk/ Tel.:  +44 1223 334761    Fax:  +44 1223 334679t   ------------------------------  % Date: Mon, 25 Feb 2002 19:14:55 -0500l  From: Kuff@Tessco.Com (Hal Kuff)) Subject: Modular data Router - Fibre Tape O Message-ID: <9F2449AF4657C6B5.5D8DF61A36F4CBF7.8DE3DCFCB8FEC1AD@lp.airnews.net>y  D    Is anyone using a Modular Data Router (I or II) on a Compaq FibreI Channel SAN? I'm looking for the feature/compatibility matrix for the MDRdJ I & II on OpenVMS... It is not clear what exactly is supported and in what9 version... I logged a case with the Storage group and the D Vms-Internales-Drivers DSN list and they are not sure or do not have access to the info.y  @    What version are you running and what success are you having?   ------------------------------  % Date: Tue, 26 Feb 2002 07:46:59 +0100e From: zessin@decus.def- Subject: RE: Modular data Router - Fibre TapeS* Message-ID: <00A0A222.3C453FC0.7@decus.de>   Hal Kuff wrote:-E >   Is anyone using a Modular Data Router (I or II) on a Compaq Fibre@ > Channel SAN?  ; There is not 'I' or 'II', it is just 'Modular Data Router'. @ Are you talking about the Fibre Channel Tape Controllers (FCTC)?D They were numbered I and II, but these are not supported by OpenVMS.   The quickspecs are at:: http://www.compaq.com/products/storageworks/mdr/index.html  ? > What version are you running and what success are you having?a  A Just MDR. It's been some time that I've played with both, OpenVMS-? and the MDR. I couldn't get a tape configured while booted from-? the VMS 7.3 CD. When I had booted from a system disk I couldn'tp@ get the tape configured either by just running SYSMAN - I had to> do a reboot. Might have been fixed with some ECO - I don't run" VMS in production so I don't care.   -- c
 Uwe Zessin   ------------------------------  % Date: Tue, 26 Feb 2002 07:46:12 +0100D From: Dirk Munk <munk@home.nl>- Subject: Re: Modular data Router - Fibre Tape & Message-ID: <3C7B2F34.5050201@home.nl>  G We are planning to use them. You need VMS 7.3 as a minimum I have been N) told by our storage salesman with Compaq.n   Hal Kuff wrote:e  E >   Is anyone using a Modular Data Router (I or II) on a Compaq Fibre J >Channel SAN? I'm looking for the feature/compatibility matrix for the MDRK >I & II on OpenVMS... It is not clear what exactly is supported and in what : >version... I logged a case with the Storage group and theE >Vms-Internales-Drivers DSN list and they are not sure or do not haver >access to the info. >tA >   What version are you running and what success are you having?h >e   ------------------------------  # Date: Tue, 26 Feb 2002 02:51:46 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)% Subject: Re: mysterious system reboot"1 Message-ID: <6LCe8.171$fL6.4426@news.cpqcorp.net>   W In article <a5ch75$25k$1@newshost.mot.com>, "Steven Xie" <r33300@email.mot.com> writes: / :Forget to tell, The system info. as following,  :m :OS OpenVMS 7.2-1a :HW Alpha ES40.a : @ :I have done a ana/crash and it turn out something as following. :E :Crashdump Summary Information:s :------------------------------y+ :Crash Time:        25-FEB-2002 08:53:14.58 = :Bugcheck Type:     INSF_NONPAGED, Insufficient nonpaged poolV     Hmmm.  Interesting.t  * :Looks like I need a new patch for this???  C   I'd encourage picking up the mandatory ECOs for OpenVMS and other/   products in use.  D   After getting the current ECOs, I'd also look at configuring more D   non-paged pool and/or more physical memory, and at offloading the E   contents of non-paged pool as appropriate, and I'd look around for .D   something that is leaking non-paged pool.  (The SDA SHOW commands 2   can be useful in tracking the contents of pool.)      N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 26 Feb 2002 02:22:01 GMTo2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)% Subject: Re: OpenVMS IPF presentations1 Message-ID: <djCe8.169$fL6.4459@news.cpqcorp.net>a  q In article <5NEd8.11546$ro5.4152153@typhoon.ne.ipsvc.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes:rK :Better yet, ask why the enlightened graphics designers in Houston placed a 7 :picture of a Sun monitor on the VMS V7.3 distribution.2  C   The folks in Houston were not involved in the choice of the image.   used for the OpenVMS manuals.y  G   I was one of the folks that helped pick that particular image out of @E   the images that were made available for use on the OpenVMS manuals.e    D :Hint: It's either Black Helicopters, Ken Lay, Bob Palmer, or Elvis,4 :depending on what Conspiracy Theory you ascribe to.  H   Hint: difference in the resolutions of the proof copies of the images J   and of the printer used to print the manual covers can sometimes matter.   	--e  K   Conspiracists rejoice: unless the other provided images are also checked eG   at higher resolutions than the proofs, the "truth" of this particulart.   error will never truely be known.  Good, eh?    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 26 Feb 2002 00:14:30 -0500s- From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Powerpoint competition , Message-ID: <3C7B19B3.72B12732@videotron.ca>   http://www.Mew.org/mgp/s  I Has a downloadable product for x-windows (linux) that supposedly competesa) against Powerpoint to make presentations.l  M However, to download it, one needs "cvs" to the host toget the files. What is  "CVS " ?????   ------------------------------  # Date: Tue, 26 Feb 2002 05:46:49 GMTz! From: Andy <acs@fcgnet.works.net> # Subject: Re: Powerpoint competitionr= Message-ID: <Xns91C17784BF61acsfcgnetworksnet@216.166.71.232>D  ; JF Mezei <jfmezei.spamnot@videotron.ca> enlightened us withy% news:3C7B19B3.72B12732@videotron.ca: o   > http://www.Mew.org/mgp/t > B > Has a downloadable product for x-windows (linux) that supposedly4 > competes against Powerpoint to make presentations. > @ > However, to download it, one needs "cvs" to the host toget the	 > files.    F Really ? There seems to be a link to the following ftp server on this  page.a  % Try ftp://ftp.mew.org/pub/MagicPoint/    > What is "CVS " ?????  F ? client/server based revision control software ? Seems to be popular  :-) at SourceForge.t   -Andy-   ------------------------------  % Date: Mon, 25 Feb 2002 15:13:19 -050000 From: Paul Anderson <paul.r.anderson@compaq.com>! Subject: Re: PrintServer softwares; Message-ID: <250220021513191843%paul.r.anderson@compaq.com>3  
 In articleD <18560B9BCCE902439194CA5C0AA9963F55F930@SGSINSMAPXMS10.SONYE2K.COM>,6 Quek, Hong Cheang <Hongcheang.Quek@ap.sony.com> wrote:  L > I need to get the printserver software for my DEC print server 17. Saw oneL > of the mails on DEC print server 17 that points to www.digital.com for theA > software download. But that site has already been transfered tooB > www.compaq.com and I can't find any download at the compaq site.  @ For what operating system do you want PrintServer Software?  TheE OpenVMS version is available on the quarterly layered product CDs andiF has never been available on the web.  The other versions are available at  H <http://www.compaq.com/products/printers/software/prt_swdrv_printserver. html>t   Paul   -- e  Paul Anderson   OpenVMS Engineering:   Compaq Computer Corporationh   ------------------------------  % Date: Tue, 26 Feb 2002 11:16:03 +0800e7 From: "Quek, Hong Cheang" <Hongcheang.Quek@ap.sony.com>o! Subject: Re: PrintServer softwarehO Message-ID: <18560B9BCCE902439194CA5C0AA9963F55F931@SGSINSMAPXMS10.SONYE2K.COM>0   Hi Paul   J I need the printserver for solaris 7. I went to the link that you gave butL it turned out to be a broken link. Searched the internet and found this site :b   ftp.digital.com   J It does have the binaries for Solaris, but somehow cannot seem to download the files. Advice please. :)   Thanks d Quek  C ------------------------------------------------------------------- J This email is confidential and intended only for the use of the individualL or entity named above and may contain information that is privileged. If youH are not the intended recipient, you are notified that any dissemination,I distribution or copying of this email is strictly prohibited. If you haveqJ received this email in error, please notify us immediately by return emailH or telephone and destroy the original message. Thank you. - This mail is) sent via Sony Asia Pacific Mail Gateway. aC -------------------------------------------------------------------    ------------------------------  % Date: Mon, 25 Feb 2002 13:10:38 -0500r5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> 2 Subject: Re: Profitability and the survival of VMS1 Message-ID: <2bve8.146$fL6.2779@news.cpqcorp.net>r  L I saw your name a few minutes ago in an earlier thread... I wondered if that was you.  J For those who don't know John, he implemented ISO 9660 support eons ago...J hope you've gotten JPL to start putting the record attributes onto the CDsI ;-)   I had hacked up something to test the ISO 9660 using some CD's JohnsL had from the Voyager mission.  The data on the CD's was actually from a VAX,H but when they burned the CDs, they left out some "optional" information,6 which caused me to have to unblock the records myself.  G In any case... yup.  I'm still here.  At least until someone in Floridau$ makes me a job offer I can't refuse.        W. John Guineau wrote in message. <04Ed8.479$1d4.709649@twister.socal.rr.com>... >cL >Having worked in the VMS Development group for several years (circa OpenVMSJ >5.x and the first releases of OpenVMS Alpha 1.0, when it was still calledL >DEC) - I can vouch for people like Fred Kleinsorge and Andy Goldstein. TheyI >are world class developers and have NO NEED to lie. They believe in VMS,)L >obviously, because they have stood behind it for more years than anyone can' >count. Andy was a VMS V1.0 designer...o > F >While I'm at it - Hey Fred, Andy! You guys are still there! Wow! Very coool. >  >johnc >e >r? >"Sue Skonetski" <susan_skonetski@hotmail.com> wrote in messagee8 >news:857e9e41.0202221910.753103c5@posting.google.com... >> Newsgroup folks,  >>F >> What Fred has said is true.  It is your choice to belive us or not.G >> But please keep in mind what Fred has said in this note.  None of uskF >> at Compaq are commended by management for any participation on thisI >> newsgroup.  We participate because we care about VMS and what you havef
 >> to say. >>I >> JF what bonus? you must obviously know something we do not, because wee >> sure have not gotten them.s >>> >> Its funny to me, but all the people from the VMS group thatG >> participate in this newsgroup are known for being straight shooters.-H >> Why would we take the time to lie, we are very busy?  And if you knewF >> Fred or Hoff or Robert or John or Clair or Andy you would know that >> they do NOT lie.e >>E >> And if you think that makes me a prostitute too, so be it.  I havef? >> been called worse for saying what I think. And I will not be @ >> intimidated or scared away from stating my opinion by anyone. >>F >> There are many people from this newsgroup who really value what theI >> engineers opinion.  And if you doubt the integrity of Compaq employees D >> in the VMS Group.  Please feel free to contact our group manager. >> Mark.Gorham@compaq.coml >> >> Sue >> >> >>C >> "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in messagey- >news:<Ymwd8.91$fL6.1195@news.cpqcorp.net>...CL >> > In the course of a career, there are sometimes that you are called upon >to K >> > paint the best picture you can.  And yes, my career has included being1 as= >> > software services specialist, and I had to do pre-sales.s >> >/ >> > I can say that I never lied to a customer.c >> >H >> > I am not paid to read or write in this forum.  In fact, there is no >careerNH >> > benefit to me personally for doing so.  Nobody has asked me to.  It >doesn'tL >> > show up on my review.  My boss, and his boss, and his boss don't pat me >onaI >> > the back and say "good job".  In fact there is more risk that I will( saytI >> > something to piss someone off externally or internally than anythinga >else. >> >? >> > Are there things I can't say?  Of course.  Some are Compaq 
 confidential,G >and? >> > some are just my opinons at times that may differ with thex
 corporations.a >> >J >> > I may choose to be optomistic about a particular outcome, but I don'tI >> > believe that I would write something that I patently believed has no L >> > realistic chance of happening.  For all the doomsayers that have talkedH >> > about the imminent demise of VMS for the last decade... we're still >here. >> > >> > >> >5 >> > paddy.o'brien@zzz.tg.nsw.gov.au wrote in messagel1 >> > <01KEIAW3FDQA005D2B@tgmail.tg.nsw.gov.au>...  >> > >Bill Todd wrote:A >> > >>"JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in messagee- >> > >>news:3C732F7D.CCB78621@videotron.ca...i >> > >>c
 >> > >>... >> > >>1J >> > >>> HP gains access to the clustering and TCP technologies and access to >theF >> > >>> experienced employees who would make a difference. Those have	 >probably:
 >> >  beenC >> > >>> given hefty bonuses to not only stay at Compaq/HP but alsoa >prortitute 3 >> > >>> themselves to defend the companies' plans.y >> > >>aK >> > >>That last comment was *way* out of line (if it referred to technicalt
 >> >  people,e >> > >>as it appeared to). >> > >K >> > >Not true, Bill (that J-F's comment was out of line).  In another lifec >int	 >> >  thenF >> > >UK (one of several reasons that I ended up here -- .au not c.o.v :-) ), >as  >> >  anL >> > >technical programmer I had to prostitute myself.  Hmm, no hefty bonus, >I
 >> >  just7 >> > >had to support a wife and young son and daughter.A >> > >F >> > >From my experience, my sympathy goes to our VMS engineers.  They might,J >> > >however, be right in their expectations and we wrong.  Regardless, I >wouldK >> > >expect them to be primarily interested in keeping the bank account inu >the >> > >black. >> > > >> > >Regards, Paddy >> > > >a >    ------------------------------  % Date: Mon, 25 Feb 2002 23:37:36 +0100>' From: Brass Christof <welcome@spam.net>r2 Subject: Re: Profitability and the survival of VMS( Message-ID: <3C7ABCB0.5D885E70@spam.net>   David Katelansky wrote:  > F > This sounds weird to most people.  Companies are in business to makeD > money, so you'd think they'd be more then happy to get calls aboutB > their products.  Back in 1999 I found out that most employees ofD > Compaq didn't even know what DEC compters were called, or at leastE > they acted that way.  I wanted to buy a used VAX so I called up themH > sales department at Compaq to see if they did that or could lead me inF > the right direction; nobody in their sales department had ever heardE > of a VAX!  I called their support department; nobody there had everwG > heard of a VAX either, so they put me through to technical support toeA > see if somebody there could help me - same negative results!  InH > finally found a company in New York, the Computer Clearing House, thatB > had just what I wanted; a VAXStation 3100 M38.  You can find VAX? > systems on e-bay nowadays, but that was a really exasperating!D > experience I had with Compaq.  It also shows you that there was noG > initiative at Compaq to even make their employees aware about the DECc? > line of computers.  Back in 1999 Compaq was still producing anE > VAXStation 3100 (M95 I think); you'd think somebody in sales should F > have been told that.  This showed a complete lack of interest in theG > DEC line of computers at Compaq, and I agree with Brass Christof; thevH > people I spoke to didn't want to be bothered with these systems they'd > never even heard of.  B In Switzerland the situation was very different as the DEC people > stayed in business. DEC was much stronger in Switzerland than ? Compaq and the buildings of DEC were much better and at better  ? places. In fact Compaq recently moved even their European head p> quater from Munich (Germany) to Zurich (Switzerland) into the A very same buildings that were DEC once. The area is still called m9 DECpark by most people I know although they replaced the n> d|i|g|i|t|a|l logos all over the place by some Compaq writing.: The DEC call centre continued to exist and it is still no 0 problem to get in contact with the right people.  ? But honestly I regard this as the exception. As another poster t= pointed out: every merger of that magnitude needs some years a; to be digested until the positive effects will be visible.  ? And it might well be the case that the same effect will happen A@ wrt current Compaq and HP products. It needs time and effort to ? tell the people in the united company what their products are. ?: And it needs hard training to make this work because only B knowing the names isn't enough to sell, to consult and to support.  = I'm not familiar with the business aspect enough but I think p= without merger Compaq management would have less excuses and s? this might be better for the enterprise systems if they really d are the cash cows.   -- g6 moc dot slupofni at ssarb - please revert the sequence   ------------------------------  # Date: Tue, 26 Feb 2002 00:44:38 GMTt/ From: "W. John Guineau" <guineau@earthlink.net>a2 Subject: Re: Profitability and the survival of VMS9 Message-ID: <WTAe8.7359$1d4.2792185@twister.socal.rr.com>h  	 Hey Fred,d  I Yup, that's me. Don't forget I was also the one who implemented the first G SCSI-2 tagged command queueing support in VAX/VMS. I think I still have19 dozens of neurons still dedicated to good old PKDRIVER :)l  H You know, at one point during a side-job I did at JPL, I actually workedJ along side the folks who put out the Voyager CD's, and countless others. IL never even thought to harass them about the ISO 9660 issues. But then, I wasC too busy eyeing the piles of server machines they were readying for'> processing/archiving the data from the JASON-1 satellite I wasJ designing/implementing the ground system for (my real job at JPL.) JASON-1F just launched this past December so now I'm looking for a job again :(  L It's good to hear from you Fred! When you get to Florida, call me with a job	 offer! :)t   john      @ "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in message+ news:2bve8.146$fL6.2779@news.cpqcorp.net...:I > I saw your name a few minutes ago in an earlier thread... I wondered if: that
 > was you. >bL > For those who don't know John, he implemented ISO 9660 support eons ago...L > hope you've gotten JPL to start putting the record attributes onto the CDsK > ;-)   I had hacked up something to test the ISO 9660 using some CD's John I > had from the Voyager mission.  The data on the CD's was actually from a. VAX,J > but when they burned the CDs, they left out some "optional" information,8 > which caused me to have to unblock the records myself. >FI > In any case... yup.  I'm still here.  At least until someone in Floridal& > makes me a job offer I can't refuse. >  >o >g" > W. John Guineau wrote in message0 > <04Ed8.479$1d4.709649@twister.socal.rr.com>... > >nF > >Having worked in the VMS Development group for several years (circa OpenVMSoL > >5.x and the first releases of OpenVMS Alpha 1.0, when it was still calledI > >DEC) - I can vouch for people like Fred Kleinsorge and Andy Goldstein.  TheyK > >are world class developers and have NO NEED to lie. They believe in VMS, J > >obviously, because they have stood behind it for more years than anyone can-) > >count. Andy was a VMS V1.0 designer...e > >FH > >While I'm at it - Hey Fred, Andy! You guys are still there! Wow! Very > coool. > >- > >john- > >- > >-A > >"Sue Skonetski" <susan_skonetski@hotmail.com> wrote in messagez: > >news:857e9e41.0202221910.753103c5@posting.google.com... > >> Newsgroup folks,o > >>H > >> What Fred has said is true.  It is your choice to belive us or not.I > >> But please keep in mind what Fred has said in this note.  None of uscH > >> at Compaq are commended by management for any participation on thisK > >> newsgroup.  We participate because we care about VMS and what you havec > >> to say. > >>K > >> JF what bonus? you must obviously know something we do not, because weh > >> sure have not gotten them.v > >>@ > >> Its funny to me, but all the people from the VMS group thatI > >> participate in this newsgroup are known for being straight shooters. J > >> Why would we take the time to lie, we are very busy?  And if you knewH > >> Fred or Hoff or Robert or John or Clair or Andy you would know that > >> they do NOT lie.o > >>G > >> And if you think that makes me a prostitute too, so be it.  I have A > >> been called worse for saying what I think. And I will not besB > >> intimidated or scared away from stating my opinion by anyone. > >>H > >> There are many people from this newsgroup who really value what theK > >> engineers opinion.  And if you doubt the integrity of Compaq employeesoF > >> in the VMS Group.  Please feel free to contact our group manager. > >> Mark.Gorham@compaq.com  > >> > >> Sue > >> > >> > >>E > >> "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in messagee/ > >news:<Ymwd8.91$fL6.1195@news.cpqcorp.net>...fI > >> > In the course of a career, there are sometimes that you are called- upon > >to-G > >> > paint the best picture you can.  And yes, my career has included< being. > ao? > >> > software services specialist, and I had to do pre-sales.3 > >> >1 > >> > I can say that I never lied to a customer.  > >> >J > >> > I am not paid to read or write in this forum.  In fact, there is no	 > >careertJ > >> > benefit to me personally for doing so.  Nobody has asked me to.  It
 > >doesn'tK > >> > show up on my review.  My boss, and his boss, and his boss don't patu me > >on0K > >> > the back and say "good job".  In fact there is more risk that I will  > saytK > >> > something to piss someone off externally or internally than anythingz > >else. > >> >A > >> > Are there things I can't say?  Of course.  Some are Compaqr > confidential,p > >andA > >> > some are just my opinons at times that may differ with the) > corporations.  > >> >L > >> > I may choose to be optomistic about a particular outcome, but I don'tK > >> > believe that I would write something that I patently believed has noeG > >> > realistic chance of happening.  For all the doomsayers that have. talkedJ > >> > about the imminent demise of VMS for the last decade... we're still > >here. > >> > > >> > > >> >7 > >> > paddy.o'brien@zzz.tg.nsw.gov.au wrote in message-3 > >> > <01KEIAW3FDQA005D2B@tgmail.tg.nsw.gov.au>...  > >> > >Bill Todd wrote:C > >> > >>"JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in messageD/ > >> > >>news:3C732F7D.CCB78621@videotron.ca...3	 > >> > >>c > >> > >>...	 > >> > >>CL > >> > >>> HP gains access to the clustering and TCP technologies and access > to > >theH > >> > >>> experienced employees who would make a difference. Those have > >probablyo > >> >  beenE > >> > >>> given hefty bonuses to not only stay at Compaq/HP but alsoo
 > >prortitute.5 > >> > >>> themselves to defend the companies' plans.o	 > >> > >>dC > >> > >>That last comment was *way* out of line (if it referred tos	 technicalu > >> >  people,  > >> > >>as it appeared to). > >> > >H > >> > >Not true, Bill (that J-F's comment was out of line).  In another life > >inh > >> >  theoH > >> > >UK (one of several reasons that I ended up here -- .au not c.o.v > :-) ), > >asr	 > >> >  atG > >> > >technical programmer I had to prostitute myself.  Hmm, no heftye bonus, > >I > >> >  just9 > >> > >had to support a wife and young son and daughter.0 > >> > >H > >> > >From my experience, my sympathy goes to our VMS engineers.  They > might,L > >> > >however, be right in their expectations and we wrong.  Regardless, I > >wouldJ > >> > >expect them to be primarily interested in keeping the bank account in > >the > >> > >black. > >> > > > >> > >Regards, Paddy > >> > > > >d > >  >e >b   ------------------------------   Date: 26 Feb 2002 03:56:04 GMT2 From: "Zane H. Healy" <healyzh@shell1.aracnet.com>$ Subject: Re: Proposal - Hobbyist FAQ, Message-ID: <a5f10k01eu4@enews3.newsguy.com>  1 William Barnett-Lewis <wlewis@mailbag.com> wrote:eC > Reading Mark Reddings experiences and pondering my own trials andoE > tribulations as a Vax and VMS hobbyist/newby, I got to wondering ifpJ > maybe the time isn't ripe for a Hobbyist specific FAQ. While much of the  I I actually started writing one about a year and a half ago...  It's still H got some rough spots and holes, but if someone wants to fill those in I  wouldn't object :^)a  / As of right now it's available for download at:MK http://www.aracnet.com/~healyzh/vms_hobbyist_faq.txt and I've also included-	 it below.-   		Zane     OpenVMS Hobbyist FAQ Last Revised: 09OCT200034 Maintained By: Zane H. Healy     healyzh@aracnet.com   Related FAQ's: VMS FAQo5 http://www.openvms.compaq.com/wizard/openvms_faq.html1# http://eisner.decus.org/vms/faq.htma   MicroVAX/VAXstation FAQg1 http://anacin.nsc.vcu.edu/~jim/mvax/mvax_faq.htmlo     Section 0: Why?oA 1. Why does this FAQ exist, when there is already an OpenVMS FAQ?u0 2. Why would anyone want to run OpenVMS at home?     Section 1: Hardware ! 1. What Hardware can run OpenVMS? . 2. Where can I get Hardware to run OpenVMS on? 3. Choosing a Hobbyist system.4 4. What DEC/Compaq Video Cards does OpenVMS Support?J 4a. What DEC/Compaq video cards for the Alpha aren't supported by OpenVMS?9 5. What 3rd Party PCI Video cards will work with OpenVMS?i8 6. What 3rd Party PCI SCSI cards will work with OpenVMS?6 7. What 3rd Party Motherboards will work with OpenVMS?- 8. Converting a NT PWS system to run OpenVMS.r& 9. Installing OpenVMS on a DEC Multia.F 10. I don't have a Monitor for my system can I use a terminal instead?+ 11. What Monitors can I use with my system?l 12. Using 3rd Party disks." 13. Using 3rd Party CD-ROM Drives.+ 14. What is a VAX Console (PC350 or PC380)?l' 15. Can I run OpenVMS on my DECstation?v 16. Moving a System., 17. How can I add SCSI support to my system? 18. What is this DEC drive?    Section 2: Softwarei> 1. I've got the hardware, where do I get the Operating System?@ 2. I've got a OpenVMS system, where can I get some applications?/ 3. Is there a database available for Hobbyists? & 4. Where is the License PAK for TCPIP?# 5. What Web Browsers are available? % 6. What E-Mail Clients are available?t% 7. What USENET Readers are available?>$ 8. What TCP/IP Stacks are available?M 9. I installed the Tru64 Hobbyist software on another hard drive, now I can'ta    boot OpenVMS.2 10. Switching between different Operating Systems.   Section 3: Information) 1. Where can I get OpenVMS documentation? 1 2. Where can I get Documentation on the Hardware?e4 3. What books do you recommend for a beginning user?5 4. What books do you recommend for a Systems Manager?i? 5. What books do you recommend for getting started programming? ( 6. What USENET newsgroups are available?? 7. Where can I get information on porting UNIX apps to OpenVMS?        Section 0: Why?uA 1. Why does this FAQ exist, when there is already an OpenVMS FAQ?k  O    The OpenVMS FAQ is a fantastic source of information, and any Hobbyist will tL    undoubtably find themselves regularly refering to it.  However, the fact K    remains that there are many questions that a Hobbyist will have that theuE    OpenVMS FAQ does not answer.  This FAQ will strive to answer thosem    questions.  >  K    If you can clarify any of the questions in this FAQ, or if you have any hI    questions that you think belong in it, please let the maintainer know.a  0 2. Why would anyone want to run OpenVMS at home?  O    There are several reasons a person might wish to run OpenVMS at home.  AmonghL    those reasons are the fact that the Operating System is extremelly stable    and well documented.  1   Section 1: Hardwarev! 1. What Hardware can run OpenVMS?e  O    Any VAX-based, and most Alpha-based systems are capable of running OpenVMS. oF    The following lists the specific models listed in the SPD as being N    supported, and where possible lists the first version of OpenVMS to supportI    the system.  Where support has been dropped in OpenVMS for a specific a    system, that is also listed.    System					First		Last 					Version		Versionl 					Supported   	SupportediA -----------------------                 ---------       --------->   VAX Systems Supported  --------------------- $                                    	 Unibus Based Systems o  VAX-11/725						5.1-1 o  VAX-11/725         					5.15 o  VAX-11/730                                    	6.2r o  VAX-11/750						6.2; o  VAX-11/751                                           6.2l; o  VAX-11/780                                           6.2a; o  VAX-11/782                                           6.2e; o  VAX-11/785                                           6.2 ; o  VAXft 110                                            6.2s; o  VAXft 310                                            6.2>; o  VAXft 410                                            6.2r; o  VAXft 610                                            6.2t; o  VAXft 810                                            6.2     8 Q-bus Based Systems                                     ; o  MicroVAX I                                           6.2n; o  VAXstation I                                         6.2b; o  MicroVAX II                                          7.2 ; o  VAXstation II                                        7.2a; o  VAXstation II/RC                                     7.2r; o  VAXstation II/GPX                                    7.2  o  VAXstation II/QVSS					7.2h  o  MicroVAX 3300, VAXserver 3300  o  MicroVAX 3400, VAXserver 3400  o  MicroVAX 3500, VAXserver 3500 o  VAXstation 3500 o  VAXstation 3520 o  VAXstation 3540  o  MicroVAX 3600, VAXserver 3600  o  MicroVAX 3800, VAXserver 3800  o  MicroVAX 3900, VAXserver 3900 o  VAX 4000 Model 100f o  VAX 4000 Model 200g o  VAX 4000 Model 300r o  VAX 4000 Model 400m o  VAX 4000 Model 500n o  VAX 4000 Model 600  o  VAX 4000 Model 50 o  VAX 4000 Model 100A o  VAX 4000 Model 105A o  VAX 4000 Model 106A o  VAX 4000 Model 108  o  VAX 4000 Model 500A o  VAX 4000 Model 505A o  VAX 4000 Model 600A o  VAX 4000 Model 700A o  VAX 4000 Model 705A o  VAXserver 4000 Model 200e o  VAXserver 4000 Model 3000 o  VAXserver 4000 Model 400e o  VAXserver 4000 Model 500: o  VAXserver 4000 Model 600a   NMI Bus-Based Systems7 o  VAX 85300 o  VAXserver 8530  o  VAX 8550o    VAXserver 8550u o  VAX 8700m o  VAXserver 8700i o  VAX 8800i o  VAX 8810  o  VAX 8820o o  VAX 8830y o  VAX 8840e o  VAXserver 8800s o  VAXserver 8810d o  VAXserver 8820  o  VAXserver 8830s o  VAXserver 8840o   XMI Bus-Based Systemst o  VAX 6000 Model 210, 220,     230, 240h o  VAX 6000 Model 310, 320,     330, 340, 350, 360a o  VAX 6000 Model 410, 420,     430, 440, 450, 460t o  VAX 6000 Model 510, 520,     530, 540, 550, 560o o  VAX 6000 Model 610, 620,     630, 640, 650, 660  o  VAXserver 6000 Model 210, r    220, 310, 320, 410, 420,     510, 520, 610, 620, 630 o  VAX 8530, VAX 8550, g!    VAXserver 8530, VAXserver 8550f o  VAX 8700, VAXserver 8700  o  VAX 8800, VAX 8810,      VAX 8820, VAX 8830, p    VAX 8840r o  VAXserver 8800, i    VAXserver 8810,      VAXserver 8820,      VAXserver 8830,    VAXserver 8840,  
    VAX 8842, y
    VAX 8974, t    VAX 8978l o  VAX 7000 Model 610, 620,     630, 640, 650, 660, 710,     720, 730, 740, 750, 760,     810, 820, 830, 840, 850,     860 o  VAX 10000 Model 610, 620, c    630, 640, 650, 660    VAXBI Bus-Based Systemsl o  VAX 8200n o  VAX 8250n o  VAXserver 8200; o  VAXserver 8250d o  VAX 8300o o  VAX 8350b o  VAXserver 8300s o  VAXserver 8350l   SBI Bus-Based Systems  o  VAX 8600o o  VAX 8650m o  VAXserver 8600t o  VAXserver 8650h  $ Special System-Specific Internal Bus; o  MicroVAX 2000                                        7.2  o  VAXstation 2000    					7.2; o  VAXstation 2000/GPX                                  7.2 ; o  VAXstation 2000/MFB                                  7.2n o  MicroVAX 3100 Model 10  o  MicroVAX 3100 Model 10E o  MicroVAX 3100 Model 20v o  MicroVAX 3100 Model 20E o  MicroVAX 3100 Model 30t o  MicroVAX 3100 Model 40  o  MicroVAX 3100 Model 80h o  MicroVAX 3100 Model 85i o  MicroVAX 3100 Model 88y o  MicroVAX 3100 Model 90h o  MicroVAX 3100 Model 95| o  MicroVAX 3100 Model 96p o  MicroVAX 3100 Model 98. o  VAXserver 3100 Model 10 o  VAXserver 3100 Model 10En o  VAXserver 3100 Model 20 o  VAXserver 3100 Model 20Eu o  VAXstation 4000 Model 60h o  VAXstation 4000 Model 90r o  VAXstation 4000 Model 95  o  VAXstation 4000 Model 96y o  VAXstation 4000-VLC o  VAX 9000 Model 110t o  VAX 9000 Model 110VP[5] o  VAX 9000 Model 210  o  VAX 9000 Model 210VP  o  VAX 9000 Model 310o o  VAX 9000 Model 310VPn o  VAX 9000 Model 320  o  VAX 9000 Model 320VPu o  VAX 9000 Model 330r o  VAX 9000 Model 330VPn o  VAX 9000 Model 340a o  VAX 9000 Model 340VP  o  VAX 9000 Model 410' o  VAX 9000 Model 410VPu o  VAX 9000 Model 420' o  VAX 9000 Model 420VPu o  VAX 9000 Model 430t o  VAX 9000 Model 430VPr o  VAX 9000 Model 440d o  VAX 9000 Model 440VP    [5] Vector processor (VP)e   Alpha Systems Supportede -----------------------.   EISA Bus-Based Systems o  DEC 2000 Models 300/500   TURBOchannel Bus-Based Systems& o  DEC 3000 Models 300/300L/300LX/300X o  DEC 3000 Models 400/400Si  o  DEC 3000 Models 500/500S/500X8 o  DEC 3000 Models 600/600S             V1.5-1H1 or V6.0" o  DEC 3000 Models 700/700LX		V6.1 o  DEC 3000 Models 800/800S , o  DEC 3000 Models 900/900LX            V6.1   DSSI Bus-Based Systems o  DEC 4000 Model 600m o  DEC 4000 Model 700    XMI Bus-Based Systemsh% o  AlphaServer 8400 (All chip speeds)  o  DEC 7000 Model 600l o  DEC 10000 Model 600   PCI Bus-Based Systemsd$ o  AlphaServer 300 (All chip speeds)$ o  AlphaServer 400 (All chip speeds)$ o  AlphaServer 800 (All chip speeds)% o  AlphaServer 1000 (All chip speeds)6& o  AlphaServer 1000A (All chip speeds)% o  AlphaServer 1200 (All chip speeds)e% o  AlphaServer 2000 (All chip speeds)t% o  AlphaServer 2100 (All chip speeds)s& o  AlphaServer 2100A (All chip speeds)) o  AlphaServer 2100A LP (All chip speeds)l% o  AlphaServer 4000 (All chip speeds)o% o  AlphaServer 4100 (All chip speeds)o% o  AlphaServer 8200 (All chip speeds)o% o  AlphaServer 8400 (All chip speeds) * o  Compaq AlphaServer DS10 (Version 7.2-1)+ o  Compaq AlphaServer DS10L (Version 7.2-1)1 o  Compaq AlphaServer DS20+ o  Compaq AlphaServer DS20E (Version 7.2-1)a* o  Compaq AlphaServer ES40 (Version 7.2-1) o  Compaq AlphaServer GS60+ o  Compaq AlphaServer GS60E (Version 7.2-1)p o  Compaq AlphaServer GS140v- o  Compaq AlphaServer GS160 (Version 7.2-1H1)u+ o  DIGITAL 2100 Server Model A500MP, A600MPe% o  AlphaStation 200 (All chip speeds)D% o  AlphaStation 250 (All chip speeds)n  o  AlphaStation 255/233, 255/300% o  AlphaStation 400 (All chip speeds)d2 o  AlphaStation 500/266, 500/333, 500/400, 500/500% o  AlphaStation 600 (All chip speeds)t& o  AlphaStation 600A (All chip speeds) o  DPWau 433au, 500au, 600au, o  Compaq AlphaStation DS20e (Version 7.2-1)+ o  Compaq AlphaStation ES40 (Version 7.2-1) , o  Compaq AlphaStation XP900 (Version 7.2-1)- o  Compaq AlphaStation XP1000 (Version 7.2-1)o  B The following are the Compaq semiconductor microprocessor develop-1 ment reference boards supported by OpenVMS Alpha. 1 o  Alpha 21064/21064A PCI reference board (EB64+) * o  Alpha 21164 PCI reference board (EB164)% o  Alpha PC64 reference board (APC64)r   Laptop Systems o  Tadpole ALPHAbook 1  " Compaq Modular Computing Component o  Alpha 4/233 PICMG SBC o  Alpha 4/266 PICMG SBC o  Alpha 5/366 PICMG SBC o  Alpha 5/500 PICMG SBC o  CompactPCI CS-1000F    . 2. Where can I get Hardware to run OpenVMS on?  N    The first problem someone wanting to run OpenVMS as a Hobbyist is likely toN    face is obtaining hardware to run it on.  Locally you can check Colleges inN    your area, and anyone that scraps computers.  Sometimes you will be able toO    find systems listed as being available in USENET newsgroups, and you can tryoJ    Resellers.  In the last couple years one of the best places to look forN    Hobbyists has been eBay (beware you are likely to find resellers bidding on    the items as well).      http://www.ebay.com   3. Choosing a Hobbyist system.    4 4. What DEC/Compaq Video Cards does OpenVMS Support?      Q-Bus    -------------K    M7602       VCB01, QVSS Q   Qbus Video Sub System module for Q22 systemso+    M7602                       (uVAX I, II)   L    M7602-YA    VCB01, QVSS Q   Qbus Video Sub System module, bitmap graphics3    M7602-YA                    option. (uVAX I, II)u    ;    M7168       VCB02       Q   4-plane colour bitmap module     M7168       QDSSi  >    M7169       VCB02       Q   4-plane video controller module    M7169       QDSSl            TURBOchanneld    ------------r    PMAGB-BA	HX (aka SFB)J If you find an SOC for a DEC 3000-400, you might find something about this card.t  5    PMAG-D/PGX	(Not Supported, last supported in V7.1)t   [Robert Deininger]N > There is also a PMAG-F, sometimes seen at ebay.  I think it might be "PGX+".M > The VMS 7.1 release notes have an end-of-support notice for PGX graphics, I"J > assume that applies to PGX+ as well.  I think the note I saw in the 7.1 N > manual took effect at 7.0.  So 6.2-xxx was the last support.  But I've neverA > seen a 7.0 doc set, so I referenced the one I've actually seen.   L > I don't know if "not supported" means "won't work anymore", or "we didn't % > test it, so we won't support it".         ! http://www.islandco.com/video.htmd4 http://moon.hanya-n.org/comp/alpha/hct/graphics.html    7    PMAGD-AA	HX+ ZLX-E1, 8-Plane 2D/3D, 1280x1024, 72Hz,  		2 Mpixels graphics memory   <    PMAGD-BA     HX+ ZLX-E2, 24-Plane 2D/3D, 1280x1024, 72Hz,)                 2 Mpixels graphics memory,  8    PMAGD-CA	HX+ ZLX-E3, 24-Plane 2D/3D, 24-bit Z-Buffer,, 		1280x1024, 72Hz, 4 Mpixels graphics memory  ;    PMAGC-AA	ZLX-M1, 24-Plane 3D, Double buffered, Z-Buffer,l2 		1 rendering processor, 4 Mpixels graphics memory  1    PMAGC-BA	ZLX-M2, 24-Plane 3D, 24-bit Z-Buffer,a- 		1280x1024, 72Hz, 8 Mpixels graphics memory,m( 		2 rendering processor, double buffered  B    PMAGC-DA	ZLX-L1, 24-Plane 3D, 24-bit image, 24-bit Z buffering,7 		24-bit double buffer, 4-Mpixels total graphics memoryb  B    PMAGC-EA	ZLX-L2, 24-Plane 3D, 24-bit image, 24-bit Z buffering,/ 		24-bit double buffer, 4-Mpixels accumulation e, 		buffering, 8-Mpixels total graphics memory    m    ISA    -------------@    PB2GA-FA     ATI Mach 64 WinTurbo "CX", entry level graphics,:                 with 2-Mbyte DRAM, 1280x1024 x 256 colors $    any S3 Trio64 option up to the V+   		ATI Mach 64 WinTurbo "GX"r( 		S3 Trio64 1MB and 2MB, 8-Plane (4D10T)  ! 		S3 Trio64V 1MB and 2MB, 8-Plane>      PB2GA-AA     QVision@      PCI    -------------@    PB2GA-FA     ATI Mach 64 WinTurbo "CX", entry level graphics,:                 with 2-Mbyte DRAM, 1280x1024 x 256 colors   8    PBXGA-AA     ZLXp-E1 8-Plane 2D graphics accelerator,:                 2 Mpixels, 1280x1024 x 256 colors, 72Hz     9    PBXGA-BA     ZLXp-E2 24-Plane 2D graphics accelerator,.:                 4 Mpixels, 1280x1024, true color, 72Hz      9    PBXGA-CA     ZLXp-E3 24-Plane 2D graphics accelerator,f6                 24-bit Z-buffer, 4 Mpixels, 1280x1024,9                 true color, 72Hz                         t  8    PBXGC-AA     ZLXp-L1 24-Plane (fully double buffered)9                 3D graphics accelerator, 24-bit Z-buffer,e:                 16 Mpixels, 1280x1024, true color, 72Hz     8    PBXGC-BA     ZLXp-L2 24-Plane (fully double buffered)9                 3D graphics accelerator, 24-bit Z-buffer,o9                 32 Mpixels, 1280x1024, true color, 72Hz  r   		PowerStorm 3D10, 8-Plane   		PowerStorm 3D30e  % 		PowerStorm 4D20, 24-Plane, Z-buffer  		 		PowerStorm 4D20T       PBXGK-BB     PowerStorm 4D10T, 		ELSA GLoria Synergy 8mb PCI with Permedia /                 II chipset, 24-Plane, 1280x1024    		PowerStorm 300   		PowerStorm 350   [Stephen Hoffman] K   The following *should* be the list of PCI graphics controllers presently :I   supported on various OpenVMS releases, some will require Open3D and/or o@   ECO kits, and the minimum supported OpenVMS version will vary:       PBXGA-A* (ZLXp-E1)     PBXGA-B* (ZLXp-E2)     PBXGA-C* (ZLXp-E3)     PBXGC-A* (ZLXp-L1)     PBXGC-B* (ZLXp-L2)$     PB2GA-A* (Compaq QVision 1024/E)$     PB2GA-HA (Compaq QVision 1280/P)     PB2GA-FA (ATI Mach64 CX)     PB2GA-FB (ATI Mach64 GX)     PB2GA-JA (S3 Trio64 2MB)     PB2GA-JB (S3 Trio64 1MB)     PB2GA-JC (S3 Trio64V+ 1MB)     PB2GA-JD (S3 Trio64V+ 2MB)     PX2GA-JA (PowerStorm 3D10)     PBXGB-AA (PowerStorm 3D30)     PBXGB-CA (PowerStorm 4D20)  %    VAXstation 4000/VLC Built-in Videoc%    ----------------------------------v    [Richard B. Gilbert]wM  VS48K-AA - 1024x768, 66(72?)Hz - RGB  (unknown connector, possibly 15-pin D):>  VS48K-BA - 1024x768, 60Hz      - SVGA (miniature D, PC-style)B  VS48K-CA - 1280x1024, 72Hz    - RGB  (DEC-special, 3 mini-coax)<    C  I have the VS48K-AA.  It takes a DEC BC29H cable.  It's a "D shells*  coax" to three BNC connectors type cable.     J 4a. What DEC/Compaq video cards for the Alpha aren't supported by OpenVMS?       PBXGA-JA    DEC864     PBXGI-AA	PowerStorm 4D40Tt     PBXGI-AB	PowerStorm 4D50Ta     PBXGI-AD	PowerStorm 4D51Tc     PBXGI-AC	PowerStorm 4D60TS  9 5. What 3rd Party PCI Video cards will work with OpenVMS?o  B    At least some success has been had using S3 Trio64 based cards.  3 6. What DEC/Compaq SCSI Cards does OpenVMS Support?C   Q-Busa
 -------------i? KZQSA         Q-bus to SCSI bus adapter. This adapter allows upnA               to seven SCSI storage devices to attach to the SCSIn>               bus. Supported only for CD-ROM and specific tape               devices.     TURBOchannel
 -------------m@ KZTSA         Mass-storage adapter for TURBOchannel systems with/               one SCSI-2 FWD port. (Alpha only)    [Robert Deininger]F > This is also the only supported turbochannel SCSI device that can doM > multi-host SCSI busses in VMS.  (Though I noted somewhere that Digital UnixsL > "clusters" can use either of the two following adapters in multi-host SCSIK > configurations.) So if you want to hobby with a SCSI cluster of DEC 3000  3 > systems, you need this (rare, expensive) adapter.a      @ PMAZB         Mass-storage adapter for TURBOchannel systems with0               two SCSI-2 FSE ports. (Alpha only)  @ PMAZC         Mass-storage adapter for TURBOchannel systems with5               two fast SCSI-2 FSE ports. (Alpha only)e     EISA
 -------------oA KZESC-AA      Backplane RAID controller for EISA systems with one +               SCSI-2 FSE port. (Alpha only)o  = KZESC-BA      Backplane RAID controller for EISA systems withW2               three SCSI-2 FSE ports. (Alpha only)  ? PB2HA-SA      Mass-storage controller for EISA systems with oney?               SCSI port. (Limited SCSI-2 support. Alpha only one:               systems with no greater than 1GB of memory.)     PCIv
 -------------eB KZPAA         Mass-storage adapter for PCI systems with one SCSI-2$               FSE port. (Alpha only)  A KZPBA-CA      Mass-storage adapter for PCI based servers with one B               UltraSCSI port. Single host support in V6.2-1H3, and/               V7.1-1H1 and higher. (Alpha only)   = KZPBA-CB      Mass-storage adapter for PCI based servers with ?               two UltraSCSI ports. Single host support in V6.2-TA               1H3, and multi-host support in V7.1-1H1 and higher.                (Alpha only)  B KZPDA         Mass-storage adapter for PCI systems with one SCSI-2%               FWSE port. (Alpha only)n  B KZPSA         Mass-storage adapter for PCI systems with one SCSI-2@               FWD port. (Alpha only - 26 per system maximum with.               Version 6.2-1H3 and Version 7.1)  @ KZPSC-AA      Backplane RAID controller for PCI systems with one+               SCSI-2 FSE port. (Alpha only)O  B KZPSC-BA      Backplane RAID controller for PCI systems with three,               SCSI-2 FSE ports. (Alpha only)  ? KZPCM         Mass-storage/network adapter for PCI systems with >               one SCSI-2 FSE port, an Ethernet port to connect>               to IEEE 802.3 local area networks. (Alpha only -.               Version 6.2-1H1 minimum support)  A KGPSA-BC      Mass-storage adapter for PCI-based servers with onerA               Fibre Channel port. (Alpha only - Version 7.2-1 and-               higher)p      9 6a. What 3rd Party PCI SCSI cards will work with OpenVMS?     ( 	http://www.swt.com/deals.html#scsicards  	 		NCR 8101 		NCR53C810 M    Tekram 390F	Symbios 53C875 (openvms offlines the card Tru64 runs as a 810)	
 		isp-1220    Qlogic 1041 		Qlogic QLA1040 		Qlogic ISP1020  + 	KZPBA family is Qlogic QLA104x controllers   6 7. What 3rd Party Motherboards will work with OpenVMS?      264DP  - 8. Converting a NT PWS system to run OpenVMS.   O    As I understand it the official conversion kit included the following items:.  .   	KZPBA-CA -- Q-Logic QLA1040 SCSI Controller$ 	RRD46-AB -- Toshiba 12x SCSI CD-ROMD 	PBXGB-AA or now a PDXGK-BB -- ELSA Synergy PCI 8mb non-Video In/Out7 	A badge to change the designation from a 'a' to a 'au'   K    First make sure you've got the needed SCSI Controller, drives, and video     board.  Then obtain and      & 9. Installing OpenVMS on a DEC Multia.  +    The DEC Multia is not a supported system   1    http://www.openvms.compaq.com/freeware/multia/   F 10. I don't have a Monitor for my system can I use a terminal instead?   [Robert Deininger]K > I little guide to the large collection of bizzare part numbers related to M > MMJ connectors and adapters would be kind of nice.  Alas, I don't have mucho > to > go on at this point.    + 11. What Monitors can I use with my system?A 12. Using 3rd Party disks." 13. Using 3rd Party CD-ROM Drives.+ 14. What is a VAX Console (PC350 or PC380)? ' 15. Can I run OpenVMS on my DECstation?A 16. Moving a System., 17. How can I add SCSI support to my system? 18. What is this DEC drive?    	RD51  	RD520 	RD53V 	RD54    Section 2: Software > 1. I've got the hardware, where do I get the Operating System?@ 2. I've got a OpenVMS system, where can I get some applications?/ 3. Is there a database available for Hobbyists? & 4. Where is the License PAK for TCPIP?  I    Prior to V5.0 TCPIP was known as UCX.  Simply use the UCX License PAK.   # 5. What Web Browsers are available?e      Netscape V3.03o    Mozilla M18	eO       http://www.openvms.compaq.com/openvms/products/ips/register_mozilla.html	     Mosaic V3.6-2    lynx V7.2 (VT based)0>       http://www.openvms.compaq.com/openvms/products/ips/lynx/  % 6. What E-Mail Clients are available?r% 7. What USENET Readers are available?r$ 8. What TCP/IP Stacks are available?  O    In addition to TCPIP which is available on the Hobbyist CD-ROM, you can alsoVO    obtain Multinet and TCPware from Process Software.  Plus for the VAX you can     get the old CMU-IP stack.  M 9. I installed the Tru64 Hobbyist software on another hard drive, now I can't0    boot OpenVMS.2 10. Switching between different Operating Systems.N 11. I've gotten the Hobbyist Layered PAKs, but what do they all mean and where     do I get the software?  
  Hobbyist PAK0N SOFTWARE PRODUCT NAME                           UPI     SPD #         PAK NAME    ACMS                       L ACMS Development OpenVMS VAX                    079     25.50.xx        ACMSL ACMS Development OpenVMS AXP                    2PZ     25.50.xx        ACMS     ACMS-REM                 O ACMS Remote OpenVMS VAX                         Y30     25.50.xx       ACMS-REMcO ACMS Remote OpenVMS AXP                         2Q0     25.50.xx       ACMS-REM     ACMS-RTN ACMS Runtime OpenVMS VAX                        076     25.50.xx       ACMS-RTN ACMS Runtime OpenVMS AXP                        2Q1     25.50.xx       ACMS-RT  8  ACMSXP-DEV                pO ACMSxp for OpenVMS Alpha App Con(Dev)           4WR     60.53.xx     ACMSXP-DEV     ACMSXP-RT                N ACMSxp for OpenVMS Alpha App Con(Run)           4WS     60.53.xx     ACMSXP-RT    ADAI DEC ADA OpenVMS VAX                             056     26.60.xx      ADAlI DEC ADA OpenVMS AXP                             09P     45.00.xx      ADA1  M  ADA-PDO                   dN DEC ADA PDO OpenVMS VAX                         0VQ     26.60.xx      ADA-PDO M DEC ADA PDO OpenVMS AXP                         0VR     45.00.xx      ADA-PDO   0  ALLIN1-MAIL-DW-CLIENT    N DEC MAILworks DECwindows Cl OVMS VAX    VZ7   31.51.xx   ALLIN1-MAIL-DW-CLIENT    ALLIN1-MAIL-SERVERXK DEC MAILworks Server OpenVMS VAX        YCZ   31.51.xx   ALLIN1-MAIL-SERVER6K DEC MAILworks Server OpenVMS AXP        3NG   63.91.xx   ALLIN1-MAIL-SERVER     ALLIN1-MAIL-SERVER-USER   0    ALLIN1-MAIL-VT-CLIENT    N DEC MAILworks Video Term Cli OVMS VAX   YHS   31.51.xx   ALLIN1-MAIL-VT-CLIENTN DEC MAILworks Video Term Cli OVMS AXP   3P9   63.91.xx   ALLIN1-MAIL-VT-CLIENT    ALLIN1-MAIL-VT-USER    ALLIN1-MAIL-WAN-SERVER     O DEC MAILworks WAN Svr OpenVMS VAX       YFU   31.51.xx   ALLIN1-MAIL-WAN-SERVER   
 [JF Mezei]K None of these provide all-in-1 office server. Those are for the old/retired0H product that had absolutely nothing to do with all-in-1. (character cell glorified VMSmail).       BASIC                    M DEC BASIC OpenVMS VAX                           095     25.36.xx        BASIC2M DEC BASIC OpenVMS AXP                           0Y7     25.36.xx        BASIC0     C/I DEC C OpenVMS VAX                               015     25.38.xx        CCI DEC C OpenVMS AXP                               MU7     42.26.xx        C7  X  CMS                       0K DEC CMS OpenVMS AXP                             0W1     42.29.xx        CMSsK DEC CMS OpenVMS VAX                             007     25.52.xx        CMS   p  COBOL                    M DEC COBOL OpenVMS AXP                           0JU     45.92.xx        COBOL M DEC COBOL OpenVMS VAX                           099     25.04.xx        COBOLA  a  CXX-VM DEC C++ OpenVMS AXP                             0HQ     45.95.xx        CXX-V0M DEC C++ OpenVMS VAX                             MJ1     37.39.xx        CXX-V0  A  DCE-APP-DEV               vO DCE Application Dev Kit OpenVMS VAX             01S     43.05.xx    DCE-APP-DEVrO DCE Application Developers' Kit AXP             24C     43.05.xx    DCE-APP-DEVv  4  DCE-CDS                  N DCE Cell Directory Server OpenVMS VAX           24D     43.05.xx       DCE-CDSN DCE Cell Directory Server OpenVMS AXP           24E     43.05.xx       DCE-CDS  1
  DCE-SECURITYh    DCPS-OPEN                 rN DECprint Supervisor OpenVMS AXP                 09K     44.15.xx     DCPS-OPENN DECprint Supervisor OpenVMS VAX                 09F     44.15.xx     DCPS-OPEN  r  DCPS-PLUS                N DECprint Supervisor Plus OpenVMS VAX            09L     44.15.xx     DCPS-PLUSN DECprint Supervisor Plus OpenVMS AXP            09M     44.15.xx     DCPS-PLUS  p  DECDCS-SRV-VA7 DEC DISTRIBUTED COMPUTING SERVICES(DECDCS) OPENVMS AXP p    DECMIGRATE                /O DECmigrate OpenVMS AXP                          MWM     39.44.xx     DECMIGRATEh    DECRAM                   N DECram OpenVMS AXP                              MV3     34.26.xx        DECRAMN DECram OpenVMS VAX                              GJ9     34.26.xx        DECRAM  h	  DECWRITE1N DECWRITE OpenVMS VAX                            VVF     25.F7.xx      DECWRITEN DECWRITE OpenVMS AXP                            2FN     55.58.xx      DECWRITE  4  DECWRITE-USER              O DECwrite for OpenVMS Alpha                      2FN     55.58.xx  DECWRITE-USER4O DECwrite OpenVMS VAX                            VVF     25.F7.xx  DECWRITE-USERt    DESKTOP-ACMS             O DECtp Desktop ACMS OpenVMS VAX                  GZG     34.81.xx   DESKTOP-ACMSm    DFSK DECdfs OpenVMS VAX                              VEQ     28.78.xx        DFSpK DECdfs OpenVMS AXP                              37Y     28.78.xx        DFSo  i  DQS                       LK DEC DQS OpenVMS AXP                             0HP     28.80.xx        DQSeK DEC DQS OpenVMS VAX                             VEN     28.80.xx        DQS   U  DTM                      K DEC Test Manager OpenVMS VAX                    927     26.68.xx        DTMkK DEC Test Manager OpenVMS AXP                    0W4     42.29.xx        DTMd     DTRK DEC Datatrieve OpenVMS AXP                      0JK     25.44.xx        DTReK DEC Datatrieve OpenVMS VAX                      898     25.44.xx        DTR-  -  DTR-UI-JAPANESE           1    DVNETEND                 N DECnet/OSI End-Node OpenVMS AXP                 MTF     42.25.xx      DVNETENDN DECnet/OSI End-Node OpenVMS VAX                 D04     25.03.xx      DVNETENDC Basic function license (DVNETEND) --- provides end system support. B   	  DVNETEXTpN DECnet/OSI EF OpenVMS AXP                       MTG     42.25.xx      DVNETEXTN DECnet/OSI EF OpenVMS AXP                       MTH     25.03.xx      DVNETEXTN Extended function license (DVNETEXT) for Alpha systems --- provides end systemF support, DECdts server, cluster alias, and OSI applications gateways.   N A DVNETRTG license which isn't supplied would be needed to run a DECdns server     DW-MOTIF         DECWINDOWS MOTIF FOR OPENVMS AXP            .  DW-MOTIF-UI-CESKY          DW-MOTIF-UI-DEUTSC   DW-MOTIF-UI-ESPANO        a  DW-MOTIF-UI-FRANCA         DW-MOTIF-UI-HANGULw  DW-MOTIF-UI-HANYU         f  DW-MOTIF-UI-HANZI          DW-MOTIF-UI-HEBREWu  DW-MOTIF-UI-ITALIA        c  DW-MOTIF-UI-JAPANE         DW-MOTIF-UI-MAGYAR   DW-MOTIF-UI-POLSKI        p  DW-MOTIF-UI-RUSSKI         DW-MOTIF-UI-SLOVEN   DW-MOTIF-UI-SVENSK        o    DW-SNA-3270-TE-VMS       M DECwind DECnet/SNA 3270 Term Em VAX          VXB  31.58.xx DW-SNA-3270-TE-VMS   
  EXT-MATH-LIB O Digital Ext Math Lib Dev OpenVMS AXP            MUV     41.84.xx   EXT-MATH-LIBDO Digital Ext Math Lib Dev OpenVMS VAX            YEZ     31.67.xx   EXT-MATH-LIBr  i  EXT-MATH-LIB-RT            P Digital Ext Math Lib RT OpenVMS AXP             MUW     41.84.xx EXT-MATH-LIB-RTP Digital Ext Math Lib RT OpenVMS VAX             MUS     31.67.xx EXT-MATH-LIB-RT  r  FMS                      K DEC FMS Development OpenVMS AXP                 MVS     45.06.xx        FMSHK DEC FMS Development OpenVMS VAX                 VD7     26.10.xx        FMS     FMS-RT-UI-JAPANESEa  FMS-UI-HANGUL                FMS-UI-JAPANESE              FORMSM DECforms Develop OpenVMS VAX                    VCH     29.90.xx        FORMS,M DECforms Develop OpenVMS AXP                    0J8     29.90.xx        FORMSr  ,  FORMS-RT                  oN DECforms Runtime OpenVMS VAX                    VNS     29.90.xx      FORMS-RTN DECforms Runtime OpenVMS AXP                    0J9     29.90.xx      FORMS-RT     FORMS-RT-UI-HANGUL         FORMS-RT-UI-HANYU    FORTRAN                    N Digital Fortran 77 OpenVMS VAX                  100     25.16.xx       FORTRANO Digital Fortran OpenVMS Alpha                   MV1     42.38.xx       FORTRAN "  ,  GKS                      K DEC GKS Development OpenVMS VAX                 810     26.20.xx        GKSpK DEC GKS Development OpenVMS AXP                 02U     42.60.xx        GKS2    GKS-RT7N DEC GKS Runtime OpenVMS VAX                     811     26.20.xx        GKS-RTN DEC GKS Runtime OpenVMS AXP                     02V     42.60.xx        GKS-RT    GKS-RT-UI-JAPANESE           GKS-UI-JAPANESE              GKS3DM DEC GKS-3D Development OpenVMS VAX              VFX     25.D2.xx        GKS3D     GKS3D-RT                  eO DEC GKS-3D Runtime OpenVMS VAX                  VFY     25.D2.xx       GKS3D-RTr    LSE                      K DEC LSE/Source Code Anal OpenVMS VAX            057     26.59.xx        LSEoK DEC LSE/Source Code Anal OpenVMS AXP            0W2     42.29.xx        LSE      MACRO64O Macro-64 Assembler OpenVMS AXP                  MWP     42.66.xx        MACRO64e    MAILBUS-400-API           2P MAILbus 400 App Prog Interf OVMS VAX            04R     42.83.xx MAILBUS-400-APIP MAILbus 400 App Prog Interf OVMS AXP            3L4     54.69.xx MAILBUS-400-API     MAILBUS-400-MTA          . MAILBUS 400 MESSAGE TRANSFER AGENT FOR OPENVMS    MMOV-DVO MULTIMEDIA Services Dev OpenVMS AXP             4G8     64.24.xx        MMOV-DVr    MMOV-RT                   lO MULTIMEDIA Services RT OpenVMS AXP              4G9     64.24.xx        MMOV-RTi    MMS                      K DEC MMS OpenVMS VAX                             VAD     26.03.xx        MMS K DEC MMS OpenVMS AXP                             0W5     42.29.xx        MMSo  q  NOTESM DEC Notes OpenVMS AXP                           0PG     47.19.xx        NOTES-M DEC Notes OpenVMS VAX                           960     27.06.xx        NOTES)     OPENVMS-ALPHA-USER         N OpenVMS AXP 1-unlim interactive users        MT2  25.01.xx  OPENVMS-ALPHA-USER    OPS5                     L DEC OPS5 Dev OpenVMS VAX                        913     27.04.xx        OPS5L DEC OPS5 Dev OpenVMS AXP                        0JJ     27.04.xx        OPS5    PASCALnN DEC PASCAL OpenVMS AXP                          098     25.11.xx        PASCALN DEC PASCAL OpenVMS VAX                          126     25.11.xx        PASCAL     PCA                        M DIGITAL Performance and Coverage Analyzer (Alpha)       0W3   42.29.xx   PCA CM DIGITAL Performance and Coverage Analyzer (VAX)         119   26.76.xx   PCA    E  PHIGS                    M DEC PHIGS Development OpenVMS VAX               0KB     29.38.xx        PHIGSBM DEC PHIGS Development OpenVMS AXP               0A6     44.45.XX        PHIGSe    PHIGS-RUNTIMEO DEC PHIGS Runtime OpenVMS VAX                   VK1     29.38.xx  PHIGS-RUNTIMESO DEC PHIGS Runtime OpenVMS AXP                   0A7     44.45.xx  PHIGS-RUNTIMEo    PHIGS-RUNTIME-UI-JAPAN       PHIGS-UI-JAPANESE            RMSJNL N RMS Journaling OpenVMS AXP                      0VH     47.03.xx        RMSJNLN RMS Journaling OpenVMS VAX                      VDV     27.58.xx        RMSJNL  Z  RTR-CL                    tN DEC Reliable Trans Rtr Clnt OpenVMS VAX         XNL     34.30.xx        RTR-CLN DEC Reliable Trans Rtr Clnt OpenVMS AXP         2AR     51.04.xx        RTR-CL  e  RTR-SVR                  N DEC Reliable Ttans Svr OpenVMS VAX              XNK     34.30.XX       RTR-SVRO DEC Reliable Trans Rtr Svr OpenVMS AXP          2AQ     51.04.XX       RTR-SVR )     SLSI Storage Library System for OpenVMS Alpha (Server)0YP    29.67.xx     SLS (H Storage Library System for OpenVMS VAX (Server)  0L7    29.67.xx     SLS    SLS-ACS                    L Storage Library Sys ACS OpenVMS AXP             0YR     29.67.xx     SLS-ACSL Storage Library Sys ACS OpenVMS VAX             MW1     29.67.xx     SLS-ACS     SLS-REMOTE               O Storage Library System for OpenVMS Alpha (Remote)0YQ    29.67.xx     SLS-REMOTE O Storage Library System for OpenVMS VAX (Remote)  YE8    29.67.xx     SLS-REMOTEo    SQL-DEVL DEC SQL Development for OpenVMS AXP             2PV     52.91.xx     SQL-DEV    SSU                       AK Session Support Utility OpenVMS AXP             2T7     27.79.xx        SSUnK Session Support Utility OpenVMS VAX             VE3     27.79.xx        SSU     UCX                      K DEC TCP/IP Client Upgrade OVMS VAX              0PJ     46.46.xx        UCX K DEC TCP/IP Client Upgrade OVMS AXP              0PH     46.46.xx        UCX K DEC TCP/IP Services OpenVMS AXP                 0LX     46.46.xx        UCX K DEC TCP/IP Services OpenVMS VAX                 VHR     25.A4.xx        UCXa  r  VAXSETbN DECset OpenVMS VAX                              965     27.07.xx        VAXSETN DECset OpenVMS AXP                              MUP     42.29.xx        VAXSET     VMS-UI-JAPANESE                VMSCLUSTER               N VMS Cluster Software for OpenVMS AXP            MUZ     41.68.xx    VMSCLUSTER    VOLSHADN Volume Shadowing OpenVMS VAX                    AB2     27.29.xx       VOLSHADN Volume Shadowing OpenVMS AXP                    2A1     47.04.xx       VOLSHAD  Z  X25                       nK X.25 OpenVMS AXP                                0TH     47.37.xx        X25O    X25-CLIENT              AO DEC X.25 Client OpenVMS AXP                     0TW     46.37.xx     X25-CLIENTo    X500-ADMIN-FACILITYM DEC x.500 Admin Facility OVMS VAX        0P5     40.77.xx X500-ADMIN-FACILITYpM DEC x.500 Admin Facility OVMS AXP        2P0     40.77.xx X500-ADMIN-FACILITYk  (  X500-DIRECTORY-SERVERO DEC x.500 Directory Svc OVMS VAX         0P4     40.77.xx X500-DIRECTORY-SERVERIO DEC x.500 Directory Svc OVMS AXP         2NZ     40.77.xx X500-DIRECTORY-SERVER   -     Section 3: Information) 1. Where can I get OpenVMS documentation?   O    The first place to start in your search for documentation should most likely1-    be the "OpenVMS documentation website" at:o$ 	http://www.openvms.compaq.com:8000/    1 2. Where can I get Documentation on the Hardware? 4 3. What books do you recommend for a beginning user?5 4. What books do you recommend for a Systems Manager?w? 5. What books do you recommend for getting started programming?O( 6. What USENET newsgroups are available?  N    The best Newsgroup to ask general OpenVMS questions is comp.os.vms, however/    a near complete list includes the following:   5 	comp.os.vms		DEC's VAX* line of computers & VMS.    m=   	comp.org.decus 		Digital Equipment Computer Users' Societya
 				newsgroup =         comp.sys.dec		Discussions about DEC computer systems.s? 	comp.sys.dec.micro	DEC Micros (Rainbow, Professional 350/380).n= 	vmsnet.alpha		Alpha AXP architecture, systems, porting, etc.s? 	vmsnet.mail.pmdf	PMDF email system, gatewayed to ipmdf mailing 	 				list.e= 	vmsnet.internals	VMS internals, MACRO-32, Bliss, &c; gatewayr 				w/MACRO32.1 	vmsnet.mail.misc	Other electronic mail software.a? 	vmsnet.mail.mx		MX email system, gatewayed to MX mailing list.n7 	vmsnet.misc		General VMS topics not covered elsewhere.i9 	vmsnet.networks.desktop.misc		Other desktop integration   						software.t7 	vmsnet.networks.desktop.pathwork	DEC Pathworks desktop  						integration.> 	vmsnet.networks.management.decmc	DECmcc and related software.: 	vmsnet.networks.management.misc		Other network management 						solutions.5 	vmsnet.networks.misc			General networking topics not  						covered elsewhere.@ 	vmsnet.networks.tcp-ip.cmu-tek		CMU-TEK TCP/IP package; gateway 						cmu-openvms-ip.a= 	vmsnet.networks.tcp-ip.misc		Other TCP/IP solutions for VMS.r; 	vmsnet.networks.tcp-ip.tcpware		Process Software's TCPWAREi 						TCP/IP software.8 	vmsnet.networks.tcp-ip.ucx		DEC's VMS/Ultrix Connection 						(TCP/IP for VMS).e> 	vmsnet.networks.tcp-ip.wintcp		The Wollongong Group's WIN-TCP 						TCP/IP software. 	vmsnet.sdk.openvms.fieldtestl( 	vmsnet.sysmgt				VMS system management.  O    Do not be surprised if your ISP does not carry all the groups on this list. aG    In my case I had to specifically request that they add the vmsnet.* aK    hierarchy, and a few other groups that I needed access to.  Obviously itoF    helps if you have a good ISP that is willing to listen to requests.    ? 7. Where can I get information on porting UNIX apps to OpenVMS?    ------------------------------  % Date: Mon, 25 Feb 2002 22:36:58 -0600 + From: Shael Richmond <ksrich@bellsouth.net>   Subject: Remote Password changes- Message-ID: <3C7B10EA.5F48CF03@bellsouth.net>b  @ We are restructuring our security.  I'm looking for a way for myC users to be able to change their password on our development system = and then migrate that password change to our 30 remote sites.v  G I've been playing around with RSH and Rlogin but haven't had much luck.DF I want to use the standard "SET PASSWORD" facility and not go through 
 authorize.  - I am running AXP/VMS 7.2-1 and UCX 5.1 eco 3.    Any suggestions?   Thanks,.   ShaelA   ------------------------------    Date: 25 Feb 2002 23:05:03 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)O$ Subject: Re: Remote Password changes3 Message-ID: <r6aTl77yXw3N@eisner.encompasserve.org>   [ In article <3C7B10EA.5F48CF03@bellsouth.net>, Shael Richmond <ksrich@bellsouth.net> writes:fB > We are restructuring our security.  I'm looking for a way for myE > users to be able to change their password on our development systemn? > and then migrate that password change to our 30 remote sites.M   > Any suggestions?  A Propagating reusable passwords means propagating vulnerabilities.    ------------------------------   Date: 25 Feb 2002 23:56:41 GMT+ From: "Joe Heimann" <heimann@ecs.umass.edu> " Subject: Re: Setting Time and Date, Message-ID: <a5eivp$lqt$1@odo.ecs.umass.edu>  - Ozone Radical <ozoneradical@yahoo.com> wrote:A^ > Didier Morandi <Didier.Morandi@Free.fr> wrote in message news:<3C775A35.950ECD2A@Free.fr>...@ >> Buy the appropriate license. This forum is not a WAREZ forum. >>    E > The computers, and the software on them, were given to us by the US H > government. We are supposed to get them working. Thanks for the advise	 > anyway.-  J Did the US Government also transfer the licenses to you?  If not, you willH need to use licenses obtained through the educational license program toJ use the software on the systems.  Most are free for single user usage, theH licensing through the ESLUG and CSL programs do have a cost for multipleJ users.  If the HELP files are no longer on the systems, you will also wantF to get OS and Layered Products media to reload them.  There is a mediaI subscription available through the two mentioned programs.  There is also I a hobbyist license program with similar terms to the single user licensesxE for education.  You can find out more about that program at this URL:   3         http://www.montagar.com/hobbyist/index.html    Joe Heimann    heimann@ecs.umass.edu    ------------------------------   Date: 25 Feb 2002 19:24:22 GMT& From: peter@abbnm.com (Peter da Silva)" Subject: Re: Shannon on the merger% Message-ID: <a5e316$evh@web.nmti.com>x  , In article <3C793862.B6B23144@videotron.ca>,/ JF Mezei  <jfmezei.spamnot@videotron.ca> wrote:C > "Terry C. Shannon" wrote: D > > CPQ currently spends close to $300M USD per year on "marketing."  N > But that $300 has the punch of $600 million because by advertising Intel and4 > MS crap, they get "help" from Intel and Microsoft.  J But so does Dell. In fact Dell benefits from any Wintel advertising CompaqI does, indirectly. The only advertising Compaq can do that won't help DellvI in some way is advertising on their big iron... Dell has nothing to equalP that.    -- l+  `-_-'   In hoc signo hack, Peter da Silva. E   'U`    "A well-rounded geek should be able to geek about anything."rL                                                        -- nicolai@esperi.org          Disclaimer: WWFD?   ------------------------------   Date: 25 Feb 2002 18:56:29 CDT= From: wayne@tachysoft.xxx.120519.killspam.00c7 (Wayne Sewell) " Subject: Re: Shannon on the merger. Message-ID: <XgdE$1Pr04vc@tachxxsoftxxconsult>  [ In article <3C79AB7D.781F4CC2@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:O > "Terry C. Shannon" wrote:  >> .1 >> "John Smith" <a@nonymous.com> wrote in messageA+ >> news:hd6e8.407$1h5.386@news2.bloor.is... N >> > If the merger is voted down, it's important that HP shareholders vote NO,M >> > and Comapq shareholders vote yes. In this way, the deal 'breakup fee' ofWJ >> > $675 million gets paid to Compaq by HP, and not the other way around. >> >H >> > Now if they'd only use that $675 million to properly market OpenVMS
 >> instead2 >> > of paying themselves fat bonuses for nothing. >> > >> R >> NOW *THAT'S* A CONCEPT!!! >>  N >> CPQ currently spends close to $300M USD per year on "marketing." Maybe they, >> should outsource the whole wretched mess. > J > Of course, the outsource provider would have to be some entity the Q canI > control. Otherwise, they might end up getting effective exposure, might H > end up selling a good bit more VMS, and might end up making more money > off of VMS there for.V >  > Can't have that, now, can we?. >   >> Of course, the outsourcing ofM >> Accounts Payable and Accounts Receivable has been an utter disaster. TrustV >> me on this one! > / > I trust no one *REALLY* expected otherwise...S > O >> What CPQ really needs is some new blood on the Board, not just the same-old,8L >> same-old candidates selected by the Houston Politburo. The Politburo that" >> brought you Director Ken Lay... > I > I'd be tempted to go run "Blazing Saddles" so I could quote a good line G > from Hedly LaMarr... (ala "My mind is raging torrent overflowing with.H > swirling nords of thought, an avalanche of creative alternatives.", or > something like that...)e >   N Then I can play the Taggert (Slim Pickens) part and say "Ditto!"  (Or was the 1 reponse to that the "20-dollar whore" line?)  :-)    -- EO ===============================================================================nM Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxxi: http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-) O ===============================================================================5= Society Lady:  Are you familiar with the Great Wall of China?A5        Curly:  No, but I know a big fence in Chicago!e   ------------------------------  % Date: Mon, 25 Feb 2002 17:48:41 -0500w- From: JF Mezei <jfmezei.spamnot@videotron.ca>C, Subject: SHOW ENTRY /FULL doesn't show /PARA, Message-ID: <3C7ABF49.7ADD8A96@videotron.ca>  N Is it me, or does SHOW ENTRY/FULL not reveal the /PARAMETERS for a print job ?  M I was trying to figure out why MOSAIC was sending jobs to print as postscriptHN text instead of postscript program. In the trailer page after I DELETE/ENTRY ,L it was writted /PARA=DATA_TYPE=ANSI, but when I was doing SHOW ENTRY/FULL on- VMS, the /PARA information was not displayed.-   (VAX, VMS 7.2)  M Is this a known "feature" ? Is there a way to see a print job's full pedigree 
 from DCL ?  N I have a generic postscript print queue that has /PARA=DATA_TYPE=POSTSCRIPT asG default and it is then sent to the execution queue. When I print to the K postscript queue, by the time the job gets to the execution queue, the SHOW J ENTRY doesn't display the parameters that were added by the generic queue.   ------------------------------  # Date: Tue, 26 Feb 2002 03:42:52 GMTT1 From: "David J. Dachtera" <djesys.nospam@fsi.net>M0 Subject: Re: SHOW ENTRY /FULL doesn't show /PARA' Message-ID: <3C7B05A4.59E3FF0A@fsi.net>    JF Mezei wrote:  > P > Is it me, or does SHOW ENTRY/FULL not reveal the /PARAMETERS for a print job ? > O > I was trying to figure out why MOSAIC was sending jobs to print as postscript P > text instead of postscript program. In the trailer page after I DELETE/ENTRY ,N > it was writted /PARA=DATA_TYPE=ANSI, but when I was doing SHOW ENTRY/FULL on/ > VMS, the /PARA information was not displayed.9 >  > (VAX, VMS 7.2) > O > Is this a known "feature" ? Is there a way to see a print job's full pedigreeR > from DCL ?  A I've never seen if fail completely, but it's possible that a long . parameter list results in a truncated display.  P > I have a generic postscript print queue that has /PARA=DATA_TYPE=POSTSCRIPT as5 > default and it is then sent to the execution queue.E  H How did you accomplish that? I've only ever seen it done via system-wide@ logical names. How do you assign default /PARAMETERS to a queue?   > When I print to theEM > postscript queue, by the time the job gets to the execution queue, the SHOWEL > ENTRY doesn't display the parameters that were added by the generic queue.  9 I think Paul needs to step in here and comment on that...    --   David J. Dachterae dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/V   ------------------------------  % Date: Mon, 25 Feb 2002 23:58:49 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> 0 Subject: Re: SHOW ENTRY /FULL doesn't show /PARA, Message-ID: <3C7B1608.45E8308E@videotron.ca>   "David J. Dachtera" wrote:J > How did you accomplish that? I've only ever seen it done via system-wideB > logical names. How do you assign default /PARAMETERS to a queue?  N I stand corrected. Checked the DCPS procedures and indeed the magic is done byK logical names. So I guess that if there is no "DATA=" in the parameters for L the job, the DCPS print symbiont will look at the logical name for the queue% the job was submitted to. (Correct ?)   N That would explain why the /PARA doesn't appear on the entry. When things work8 one easily forgets how they had been setup initially :-)   ------------------------------   Date: 25 Feb 2002 23:44 CST ' From: carl@gerg.tamu.edu (Carl Perkins) 0 Subject: Re: SHOW ENTRY /FULL doesn't show /PARA- Message-ID: <25FEB200223442139@gerg.tamu.edu>   5 "David J. Dachtera" <djesys.nospam@fsi.net> writes...7Q }> I have a generic postscript print queue that has /PARA=DATA_TYPE=POSTSCRIPT as.6 }> default and it is then sent to the execution queue. } I }How did you accomplish that? I've only ever seen it done via system-wideOA }logical names. How do you assign default /PARAMETERS to a queue?  }--  }David J. Dachtera  E You can use DCPS and specify the desired parameters in the setup .COMxF file. DCPS sets them up as logical names like DCPS$queuename_PARAMETER( which the DCPS symbiont checks and uses.  D This allows you to make, for example, a queue that prints everything in duplex mode:    In DCPS$STARTUP.COM:  % $ @sys$startup:dcps$execution_queue - C         main$q -                        ! P1 - Execution queue nameeD         gergx::"serial/lta15:" -        ! P2 - Serial Device name orE         -                               !       PrintServer node name L         dcps_lib -                      ! P3 - Logical name for library(ies)G         "" -                            ! P4 - Default queue parameters O         "/SEPARATE=(NOBURST,NOTRAILER)" -       ! P5 - Default queue qualifiers I         "" -                            ! P6 - Communication speed(serialS<         -                               !      devices only)E         "/SPOOL=(MAIN$Q,GERGX$DKA0)" -  ! P7 - Device characteristicsV<         ""                              ! P8 - Verify on/off) $ @sys$startup:dcps$generic_queue -     !eA         sysduplex -                     ! P1 - Generic queue name F         main$q -                        ! P2 - Execution queue name(s)G         "sides=2" -                     ! P3 - Default queue parametersXG         "" -                            ! p4 - Default queue qualifiersO<         ""                              ! P5 - Verify on/off   After this setup runs you have:S   $ sh log *duplex*/sys6   (LNM$SYSTEM_TABLE)  (   "DCPS$SYSDUPLEX_PARAMETER" = "sides=2"  C Everything that goes through the SYSDUPLEX queue comes out duplex - C except, perhaps, if you specify /PAREMTERS=sides=1 (or perhaps just D any paremeters, I havn't tried it and don't know if the defaults areF only applied if none are given or if they are merged with any that are@ given with precidence to any explicitly specified with the job).   --- Carl   ------------------------------   Date: 25 Feb 2002 22:52 CST ' From: carl@gerg.tamu.edu (Carl Perkins)PU Subject: Re: Singular they was Re: Sv: Younger recruits versus experienced veterans (n- Message-ID: <25FEB200222520615@gerg.tamu.edu>n  e In article <Jbl6KmZJoCQV@eisner.encompasserve.org>, koehler@encompasserve.org (Bob Koehler) writes... ^ }In article <01KEMGOK42CI0058C8@tgmail.tg.nsw.gov.au>, paddy.o'brien@zzz.tg.nsw.gov.au writes: }> Bob,d- }>>      Fish is only singular in New Jersey.  }>  - }> Is this some strange US attempt at humour?  } D }   Everything in the state of New Jersey is strange.  Even the good }   things.5 } J }   As we moved around the country when I was a child, I was treated to a C }   great many variations on what was condidered education.  But it E }   wasn't until we moved to NJ that someone tried to teach my sister ! }   fishes as the plural of fish.   A If it wasn't, it wouldn't be possible to have someone "sleep withM the fishes". This, it must be.   --- Carl   ------------------------------  % Date: Mon, 25 Feb 2002 15:12:25 -0800O& From: name99@mac.com (Maynard Handley)Y Subject: Re: Sv: Younger recruits versus experienced veterans ( was The demise       of   7 Message-ID: <name99-2502021512250001@handma2.apple.com>   ? In article <3C72FD44.2058A1ED@ev1.net>, richmond@ev1.net wrote:    > Bob Koehler wrote: > >  > > In articleE <yKxb8.25353$Nv5.721800@bgtnsc05-news.ops.worldnet.att.net>, "StephenM+ Fuld" <s.fuld.pleaseremove@att.net> writes:X > > M > > > As an example, I used to teach Fortran to people who already knew COBOL I > > > (Yes, it was a long time ago).  In COBOL, there is a "Perform" verb  which isH > > > sort of like an internal procedure call but with all the variables visible.O > > > It essentially transfers control to code at some label, executes the codetL > > > until the next label then returns.  This encouraged a style that said,P > > > essentially "If something is true, go perform code to handle that." So theH > > > code to handle the situation had to be physically removed from the	 mainline.n > > >eO > > > In contrast, most Fortrans of the time, didn't have such a construct, butrO > > > had conditional if statements where the conditionally performed statementlO > > > could be a goto.  This encouraged a style like "if something is NOT true,vO > > > goto around the code that handled it", followed immediately by that code.l > > >c > > I > >    Thus invented: the COME FROM construct.  Old FORTRAN-IV code, withtF > >    very large subroutines.  Instead of writing a new subroutine toH > >    handle common code, the programmers were in the habit of labelingL > >    it and jumping there with a GOTO.  Then a variable (often an ASSIGNEDK > >    GOTO variable) was used to tell where to GOTO to get back (where didnH > >    I come from?).  Somewhat like a BASIC GOSUB, but more painfull to > >    maintain. > >cC > This "come from" constuct that uses the ASSIGNED GOTO variable isoD > useful to create a "simulated" recursive routine. I once wrote oneB > to traverse an AVL tree and print the nodes out in alphabetical A > order. It is blindingly *fast*...because there is *no* functioneC > call overhead. You have to stack and unstack the local variables a > yourself.f  I Ah, once again the "blindingly fast because of no function call overhead"uF claim. If you look at any decent RISC machine (like a PPC) there IS noG function call "overhead". The set of things that are done on a function;G call is exactly the same as the set of things that are done in a set of/ goto's faking a function call.   Maynardp   ------------------------------  % Date: Mon, 25 Feb 2002 17:32:56 +0100e2 From: martin@radiogaga.harz.de (Martin Vorlaender)* Subject: Re: The portability of Windows NT; Message-ID: <3c7a6738.524144494f47414741@radiogaga.harz.de>r  . JF Mezei (jfmezei.spamnot@videotron.ca) wrote:> > I keep hearing about the dangers of null terminated strings. >e2 > I frankly don't see what the fuss is all about.  >sN > If you design your subroutines properly, you require that the caller provideA > the maximum size of a buffer you are expected to write data to.s  H Problem is, this isn't done (largely). Look at the ANSI or POSIX C RTLs.< Okay, there is strncpy(), but many programmers use strcpy().  J > If at all, null terminated strings force you to be more conscious of the > buffer overflow potential.  E Problem is, the *ix world never has been too concious (until lately).3  E > The problem is not the null terminated strings, it is the hiring of H > nintendo-playing microsoft weenies without experience to write serious > code.n  B Without being a M$ advocate: this dates back to the advent of *ix.9 M$ only copies the bad code, as they have always done :-)    cu,    Martin -- hA                      | Martin Vorlaender  |  VMS & WNT programmer . Microsoft's answer   | work: mv@pdv-systeme.deA to OpenVMS is        |   http://www.pdv-systeme.de/users/martinv/-5 Windows NT 10.0.     | home: martin@radiogaga.harz.deg   ------------------------------  # Date: Mon, 25 Feb 2002 19:12:52 GMTs' From: Don Sykes <anonymous@pacbell.net>a/ Subject: Re: tool to calc recursive dir sises ?l+ Message-ID: <3C7A8DC4.9991E97D@pacbell.net>n   You mean like :a 	$ LOOP:) 	$ check = f$search("DISK:[000000]*.dir")  	$ if check.eqs.""  then exith- 	$ check = check -"000000]" -".DIR;1" +"...]"  	$ dir/siz/grand 'CHECK' 	$ goto LOOP   Jan-Erik Sderholm wrote:  >  > Hi.i< > I'd like a tool that displays the total size and number of; > the files i each dir on a disk. Each dir should display abB > total *incl* all sub-dirs from that level. A "dir /tot" displaysB > the actual number of files and size in each dir *excl* sub-dirs. > % > Anyone having samething like this ?a > - > I once wrote a tool to do this in DCL usingF  > F$SEARCH("device:[000000...]")H > and then using F$FILE_ATTRIBUTES to calculate eof-size, alloc-size forJ > each dir and then write a report. It included a "level:n" label for eachE > directory, so I could do "SEA <report> "level:2"" to get the totalsnF > for a specific directory level. It worked fine, it just took so long > time	 > to run.  > 	 > Regardso > Jan-Erik Sderholm.e   -- t   Have VMS. Will Travel. Wire Paladin @alphase.com 
 San Francisco    ------------------------------  % Date: Mon, 25 Feb 2002 21:01:27 +0100h- From: Didier Morandi <Didier.Morandi@Free.fr>t/ Subject: Re: tool to calc recursive dir sises ?t' Message-ID: <3C7A9817.C3CD345F@Free.fr>   ? No. You just create your temp dir with a maximum version limit!r   D.   Jan-Erik Sderholm wrote:n   ../..o2 > What I'd like to "find" is, e.g., some directory4 > where I'v forgotten to clean out tmp files or some2 > batch job where I'v forgotten to purge the logs. > @ > Right now, I think I'll just run a "DIR/SIZE/TOT/OUT=somefile"' > and then write some DCL to sum it up.  >  > Jan-Erik.-   -- -H   ----------------------------------------------------------------------H MORANDI Consultants  -  WEB: http://Didier.Morandi.Free.fr/index_us.htmlH Pflanzschulstrasse 53, 8004 Zurich, Switzerland. GSM: +41 (0)79 705 4670H 19, chemin de la Butte, 31400 Toulouse, France.  GSM: +33 (0)6 7983 6418  H Disaster Recovery Plans, Computer Security Audits, DEC OpenVMS ExpertiseH On parle franais Man spricht Deutsch se habla Castellano English spoken   ------------------------------    Date: 25 Feb 2002 22:57:07 -0800( From: giese@volkswerft.de (Rainer Giese)( Subject: Users logged out with TCPIP$XDM= Message-ID: <2f256f8d.0202252257.21cbcc4c@posting.google.com>v  ? Because I got no answer in vmsnet.networks.tcp-ip.ucx, but very / interested in the problem, I try it again here.   D I changed our X-Terminals of several producers to using XDMCP_DIRECTA instead of DECnet (with TCPIP 5.1 ECO 3 on the VMS hosts). In the@F morning it works, but in the afternoon I got the following situation :  D If a user logs off, almost reproducable some other users were kicked out.  @ With a TCPIP$XDM_DEBUG_W-logical I found some similar in several0 [TCPIP$XMD.WORK]*.OUT-files (my comments in <>):  % sys$crembx: status = 1 , number = 400a' sys$getdviw: status = 1 , number = 6621 	 =========  user     giese  8 pass     ********                <password was readable> proc     _xdm_00019 2 script   SYS$SPECIFIC:[TCPIP$XDM.WORK]tek07_0.COM  mbx      6621 	 =========P	 =========r3 pid     677387556 / 28601D24      <this was my PID>  status  1 / 1 	 =========  mailbox ASYNC read: status = 1 p@ mailbox read: status = 1 , pid = 28601C85 <this PID belongs to a different user>s sys$delmbx( 400 ) status = 1   sys$dassgn( 400 ) status = 1 >  ( Is there anyone using XDM successfully ?   Regards> Rainer Giese   ------------------------------  # Date: Tue, 26 Feb 2002 01:27:27 GMTy2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: vax h/w type.1 Message-ID: <3wBe8.166$fL6.4277@news.cpqcorp.net>   W In article <21FEB200209351223@gerg.tamu.edu>, carl@gerg.tamu.edu (Carl Perkins) writes:e :"Admirably" is debateable - a' :$ Write SYS$Output F$GetSYI("HW_NAME")o6 :may not tell you the model number - for example on my8 :VAXstation 3100 model 48, also running V5.5-2, it gives9 :the "VAXstation 3100" part, but not the "model 48" part.   A   There's no electronic difference between various members of thexA   VAXstation 3100 series.  The VAXstation 3100 models 38 and 48, dC   for instance, are entirely identical -- save for the size of and eB   the number of available storage slots in the physical enclosure.9   This difference is not something OpenVMS VAX can "see".d  @   Further, some of these fields have rather constrained lengths.  H   Also (though not the case here), some of the VAX systems will emulate I   others -- this was quite common when newer VAX systems were to be used hF   on older releases of OpenVMS VAX.  OpenVMS VAX V5.5-2H4 has no idea F   what a VAX 7000 model 800 might be, and reports the system as a VAX D   7000 model 600.  The folks then do see the system bootstrap on theH   older OpenVMS VAX release, but don't see the correct system name, and 2   some degree of consternation regularly ensues...   :$ show lic/charge. :gives the somewhat odd information indicating5 :"This is a VAXstation 3100, hardware model type 148"=5 :which is somewhat better, but not an exact match foro" :the actual model number of [1]48.       Here is a local example:   $ sho lic/char* VMS/LMF Charge Information for node [name]/ This is a VAX 6000-540, hardware model type 188: .. $ x=f$getsyi("hw_model") $ sho sym xo/   X = 188   Hex = 000000BC  Octal = 00000000274'< $ lib/extr=$vaxdef/out=sys$scratch:x.x sys$share:starlet.mlb $ sear sys$scratch:x.x 188 $EQU    VAX$K_V1202_4T  188E $EQU    VAX$C_V1202_4T  188  $ x=f$getsyi("HW_NAME")M $ sho sym xd   X = "VAX 6000-540" $s  J   Probably the biggest problem is a lack of (visible) comments in $VAXDEF.H   Unless you know that the V1202 means processor family 12 and member 2,I   and the 4T means this is a four-processor Timesharing system, and more .L   importantly, which VAX CPU is assigned 1202, you're kinda "stuck".  Older I   type codes are more obscure, such as the VPVWS type code below -- that AI   symbol is largely derived from other symbols and from the project name e   for that VAX system.  J   The Alpha systems -- those with Dynamic System Recognition (DSR) supportJ   in the console -- are far better at this, as OpenVMS learns the details F   of the system from the console.  (That said, $ALPHADEF does not see H   particularly frequent updates on OpenVMS Alpha -- a couple of us spentD   several weeks overhauling the $ALPHADEF file contents circa V7.1.)  H   As for the VAX hardware type code for that VAXstation 3100 series that   was referenced above:j   $ sear sys$scratch:x.x 148 $EQU    VAX$K_VPVWS     148n $EQU    VAX$C_VPVWS     148  $   G   This is a PVAX1-series single-user workstation, and particularly one YE   that lacks the Dragon (GPX) graphics support.  Which particular VAXT8   "consumer" of the PVAX1-series motherboard, I donno...    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 25 Feb 2002 15:01:13 -0500 % From: "John Vottero" <John@mvpsi.com>  Subject: Re: VAX SCANo/ Message-ID: <u7l60tfgivo6c5@news.supernews.com>S  ? "Ruslan R. Laishev" <laishev@smtp.deltatel.ru> wrote in messaget* news:3C7A8AE1.6083EE81@smtp.deltatel.ru... >O > John Reagan wrote: > >  > > Tom Linden wrote:eE > > > I couldn't locate a license pak for subject on the freeware 4.0c > > > distribution. J > > > Did I miss it?  If not, does someone have a pak they couls email me? > > >fE > > > Rebuilding the kit does not seem like a productive use of time.- > > >-1 > > > Was this ever ported to Alpha in some form?0 > > >r > > >M > ><! > > It was never ported to Alpha.j > Is there a plan to do this ?  K I think Compaq's plan is to put the source code on the freeware CD and hopeaG that someone ports it in their spare time.  Getting it running on AlphasK should be fairly easy.  Getting it to produce Alpha object code is the hard? part.t   ------------------------------  % Date: Mon, 25 Feb 2002 15:09:44 -0500 * From: John Reagan <john.reagan@compaq.com> Subject: Re: VAX SCANt) Message-ID: <3C7A9A08.5060506@compaq.com>w   Ruslan R. Laishev wrote:   > 	Is there a plan to do this ?e >  Absolutely not.   I As John mentioned, the sources for VAX SCAN have been submitted to DECUS k@ (they've been there a while).  But as John also mentioned, just D recompiling it on Alpha gives you an Alpha image that generates VAX 
 instructions.(  H And to answer the question before it comes up, "No, we won't be porting  VAX SCAN to Itanium either."   --   John Reagana' Compaq Pascal/{A|I}MACRO Project Leader7   ------------------------------  % Date: Mon, 25 Feb 2002 13:55:37 -0700C+ From: "Barry Treahy, Jr." <Treahy@mmaz.com>h Subject: Re: VAX SCAN % Message-ID: <3C7AA4C9.40509@mmaz.com>    John Reagan wrote:   > Ruslan R. Laishev wrote: > # >>     Is there a plan to do this ?a >> > Absolutely not.J >aE > As John mentioned, the sources for VAX SCAN have been submitted to tH > DECUS (they've been there a while).  But as John also mentioned, just F > recompiling it on Alpha gives you an Alpha image that generates VAX  > instructions.  >uB > And to answer the question before it comes up, "No, we won't be & > porting VAX SCAN to Itanium either." > C What about TDMS.  This didn't make the Alpha port, and what of the  G prospects of it making the IPF port?  If not, since Compaq hasn't done  G anything with it for a long time and would obviously consider it dead,  % what about releasing it too to DECUS?-   Barryn   --    @ Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO   A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028    ------------------------------  % Date: Mon, 25 Feb 2002 16:16:43 -05006- From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Re: VAX SCAN , Message-ID: <3C7AA9AE.28C6A1E7@videotron.ca>   "Barry Treahy, Jr." wrote:D > What about TDMS.  This didn't make the Alpha port, and what of theH > prospects of it making the IPF port?  If not, since Compaq hasn't doneH > anything with it for a long time and would obviously consider it dead,' > what about releasing it too to DECUS?(  M Wasn't there a statement made somwhere about Compaq committing to port to IPF G only products which are still "alive" at a certain point in time (don't M remember when that cut off time was), with a few exceptions such as FMS whichn3 would be ported to IPF even though they are mature._   ------------------------------  # Date: Tue, 26 Feb 2002 02:36:57 GMTs2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: VAX SCANp1 Message-ID: <dxCe8.170$fL6.4336@news.cpqcorp.net>e  g In article <3C77B4DD.162F0BD1@smtp.deltatel.ru>, "Ruslan R. Laishev" <laishev@smtp.deltatel.ru> writes:  :g :Tom Linden wrote: :> eB :> I couldn't locate a license pak for subject on the freeware 4.0 :> distribution.  F   Is there even a PAK?  VAXscan is pretty old, and might predate PAKs.*   Did you look in one of the zip archives?  G :> Did I miss it?  If not, does someone have a pak they couls email me?D  $   If there even is a PAK, of course.  6   If there is a PAK required, I can likely provide it.  B :> Rebuilding the kit does not seem like a productive use of time. :> C. :> Was this ever ported to Alpha in some form?   :	Add my vote too!!!!d  -   There is no Alpha port of the VAXscan tool.   G   There are no plans to port the VAXscan tool to a native application,  G   though there are some bits involving DECmigrate that appear possible.   F   There have been a number of folks that have looked at this port, as F   this is not the first request for an Alpha port of the VAXscan tool.E   I and others have looked into this on various occasions -- VAXscan  D   is based on an old version of the VCG code generator for VAX, and C   would have to be heavily modified to get it to work with the GEM     code generator used on Alpha.-  G   As I have indicated during these previous research projects into the rD   status of VAXscan, I would encourage the use of Perl or Python or    other approach.e  C   No, I know of no particular tools to port VAXscan code into Perl     or Python or other language.  E   Since Tom Linden has the source code for VAXscan from the Freeware aD   and likely also has a version of the GEM object libraries as part B   of his work supporting PL/I, Tom is probably in the best spot to?   look into the GEM licensing and for an Alpha port of VAXscan.         N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------    Date: 25 Feb 2002 11:15:49 -08005 From: pat.saunders@sis.securicor.co.uk (pat saunders)i* Subject: vax/vms documentation - psi / x29= Message-ID: <bc0e3bd8.0202251115.57c3b308@posting.google.com>    Hi,hE   Does anyone know where to find online documentation about PSI / x29h configuration E.Gf   VAX PSI MANAGEMENT GUIDE, @   I am trying to find why i get PAD-F_NOLINES error when using :   set host /x29 dte-0%<xxxxx>t ta pate   ------------------------------   End of INFO-VAX 2002.111 ************************