1 INFO-VAX	Tue, 15 Aug 2006	Volume 2006 : Issue 453       Contents: Re: Alpha remembrance day  Build procedure for WGET Re: Build procedure for WGET% Re: Clients using a GUI to access FTP % Re: Clients using a GUI to access FTP % Re: Clients using a GUI to access FTP % Re: Clients using a GUI to access FTP % Re: Clients using a GUI to access FTP % Re: Clients using a GUI to access FTP  CPU Speed on ALpha ES40  Re: CPU Speed on ALpha ES40  Re: CPU Speed on ALpha ES40  Re: CPU Speed on ALpha ES40  Re: CPU Speed on ALpha ES40  Re: CPU Speed on ALpha ES40  Re: I should'a known better!P Missing freeware submission (was Freeware V8.0 and July 2006 OpenVMS FAQ Availab9 OpenVMS Integrity install CD's and layered products media   Re: Products in Operating SystemI The Future of VMS development! (Was Re: Multinet's _BG: Driver and IPsec) M Re: The Future of VMS development! (Was Re: Multinet's _BG: Driver and IPsec) & Re: [VMS] Products in Operating System  F ----------------------------------------------------------------------    Date: 15 Aug 2006 04:11:02 -0700- From: "Andrew" <andrew_harrison@symantec.com> " Subject: Re: Alpha remembrance dayC Message-ID: <1155640262.501829.111910@h48g2000cwc.googlegroups.com>    Bill Todd wrote: > Andrew wrote:  > > Bill Todd wrote: > >> Andrew wrote: > >> > >> ... > >>6 > >>> Why keep repeating the same sorry tired mantra ?K > >> I'm sorry that you seem to find the truth tiresome, moron - but as you G > >> ought to be able to divulge from some of the material to which you 9 > >> responded, you're not an audience that I care about.  > > ? > > Which truth are you refering to exactly, yours or reality ?  > H > They are pretty much the same - and you *really* need a spell-checker. >   G Resorting to abuse and complaining about grammar and spelling is always @ a sign that the poster has run out of intellectual capital. KeepA digging its amusing to watch the top of your head disappear below  ground level again.   K > >>> Alpha grew initially because it was new, it was quick and with things L > >>> like the VEST program it was relatively easy to move apps from VAX/VMSI > >>> to Alpha/OpenVMS. It died because the mistakes made by DEC prior to J > >>> Alpha's introduction created a climate in which it could not attractJ > >>> enough software or market share to sustain it after the honeymoon of > >>> the initial introduction. J > >> Sure, Andrew - the honeymoon period explains it all, just like it didI > >> with Itanic's initial acceptance (not) - despite the ease with which I > >> IA32 software could run there without even something like VEST being  > >> necessary.  > >>D > > Ohh come on Bill even you must grasp the weakness of this point. > > H > > When Alpha was introduced it clearly led VAX in terms of performanceI > > and price so there was a real incentive to move.  It also led all the H > > other CPU architectures in terms of per CPU performance so there wasC > > also an incentive to move onto the Alpha platform from outside.  > G > Gee, Andrew, why am I surprised that at least some of your incoherent + > drivel actually makes my own case for me?  >   G Well if you can part of my argument that supports you case such that it  is then please quote it.  G > If DEC's *prior* activities had indeed fatally sabotaged Alpha as you E > would have us believe, then that effect would have been apparent at I > Alpha's launch (a transition which, no matter how manageable, was *not* E > a negligible one) and *that* transitional point would have been the G > natural time for people dissatisfied with DEC or with the surrounding H > 'ecosystem' in which you appear to place somewhat excessive importance3 > given Alpha's actual history to have jumped ship.  >   F So where exactly would the VMS?VAX customer base have gone in your oddA little world. VAX 9000 series ! that was a dud. No most customers F upgraded to Alpha and OpenVMS often because it was the only option and@ then found at the end of the decade that they had no where to go( because all their ISV's had jumped ship.  C How may times do I have to repeat what others have also observed as F customers and Digital employes. The market changed, commercial systemsF customers moved from make to buy. The mid to late 90's saw the rise ofD the packaged software solution, the rise of the middleware market inF almost all markets with the possible exception of HPC. Digital becauseD of its mistakes leading up to the Alpha launch was singularly poorly) placed to thrive in this new environment.   C In 1993 SAP generated annual revenues of $718 million, by 2002 less E than a decade later SAP generated annual revenues of $9.5 billion. In F 1993 some of that 718 million dollar market was addressable by VMS, in 2002 none was addressable.  > Siebel generated annual revenues of $8 million in 1995, by theF beginning of 2002 less than a decade later Siebel had revenues of just= over $2 billion. A market that Alpha was not able to address.   G This picture is repeated for almost every major applications vendor, it F also extends to crucial middleware components. Even the brighter spotsC like Oracle made life difficult in practice by not providing timely < support for DBMS or Appplications Suites on Alpha platforms.      F > And yet they - and even outsiders, as you note - happily signed ontoJ > Alpha, and only *later* (after the additional depredations of the Palmer > era) got cold feet.  > G Of course some new customers bought into Alpha, it was fast and in 1992 B many IT organisations still developed big chunks of their softwareF infrastructure themselves so lack of apps and middleware was much less of an issue.  D But name a significant outsider in the commercial systems space thatG signed for Alpha. Name a significant outsider in the desktop space that  signed for AlphaPC.   E Of course Cray signed for Alpha, but then they operated in the market C least dependant on having a viable ISV and partner ecosystem from a  platform perspective.   C Given Alpha's origional goals the lack of serious commercial design 4 wins had a major impact on Alpha's long term future.  J > > Roll forward a decade and Itanium had none of the speed advantage thatJ > > Alpha had in fact you could buy a faster system running Alpha from theG > > same vendor HP and if you wanted IA32 compatibility you could buy a  > > faster system from anyone. > H > Well, at least you're consistent in your inconsistency.  The point youH > raised regarding Alpha was the ease of running native VAX applicationsF > (though at interpretive rather than native speed), and precisely theF > same point applies to (post-Merced, obviously) Itanics (save that noJ > interpretation was required, hence even greater compatibility obtained). >   G Still irrelevant, except for some edge conditions running emulated code D on Alpha was generally faster than running the same code on VAX. The reverse was true for Itanium.   A In addtion there was no viable alternative, VAX 9000 was a failed F project.  On the other hand prospective Merced customers had plenty ofF options. x86 for Windows, faster and cheaper. Alpha for Tru64 and VMS, faster and cheaper.   J > And McKinley's lack of any substantive speed advantage (though it was atC > least somewhat faster than the PA-RISC CPUs that it was primarily G > replacing) was more than offset by the fact that unlike VAX (where no J > imminent demise loomed and where in fact production continued for a fullH > 8 years after Alpha's introduction) PA-RISC was already slated for theF > glue factory (and rather sooner than eventually turned out to be theK > case), hence providing significantly more impetus for an early migration.  >   C So you have very conveniently forgotten Merced ! how unsuprising. A F puff of smoke appears from one of the Todd airlines DC9 engines and it@ is forced to taxi back to the jetway. Or put it another way your+ ommision means that your point doesn't fly.   A McKinley was the relaunch of Itanium after Merced flopped Can you ; dredge up a similar situation from the Alpha history books?    > ...  > H > >>> Alpha sales initially went up to a pretty reasonable 10-12% market> > >>> share, fell in the latter half of the 1990's to below 5%L > >> For the reasons I suggested, of course - reasons based on actual events- > >> rather than on your 'honeymoon' fantasy.  > >> > > B > > So what are the actual events you would like to introduce ???? > J > Ah - reading-disabled as well as learning-disabled, I see.  You can findF > them (as should have been evident from the above wording, nitwit) byH > revisiting the existing material in this thread which you so obviously. > failed to assimilate the first time through. >    So refresh my memory.    Regards  Andrew Harrison    ------------------------------  % Date: Tue, 15 Aug 2006 17:25:11 +0930 % From: Jeremy Begg <nospam@vsm.com.au> ! Subject: Build procedure for WGET ) Message-ID: <44E17DDF.2010607@vsm.com.au>    Hi,   H This message is for StevenSchweda, whose mail server is blocking mine. L (The error message is 'Your IP address or subnet is in my list of bad ones' E which seems a little odd as none of my systems are listed in any RBL   database that I know of.)   H Anyway, today I downloaded WGET 1.10.2b and attempted to build it on my K OpenVMS Alpha V7.3-2 system.  It failed during the LINK command because it  > tried to access MULTINET_SOCKET_LIBRARY, which does not exist.  J On this system we are running Process Software's "SSH for OpenVMS" productK (a better SSH than the one provided with TCP/IP services).  This product is I derived from MultiNet and so the logical name MULTINET_ROOT is present on 1 the system -- but MULTINET_SOCKET_LIBRARY is not.   B I got the build procuedure to work by making a very simple change:       $ diff vms-wget.com      ************<     File DKA100:[SOURCES.WGET-1_10_2B_VMS.VMS]VMS-WGET.COM;2H        88   $ if (f$edit( f$trnlnm( "MULTINET_SOCKET_LIBRARY"), "TRIM")  .nes. "") then -        89      IP = "MULTINET"
     ******<     File DKA100:[SOURCES.WGET-1_10_2B_VMS.VMS]VMS-WGET.COM;1N        88   $ if (f$edit( f$trnlnm( "MULTINET_ROOT"), "TRIM") .nes. "") then -        89      IP = "MULTINET"     ************  *     Number of difference sections found: 1)     Number of difference records found: 1   $     DIFFERENCES /IGNORE=()/MERGED=1-<         DKA100:[SOURCES.WGET-1_10_2B_VMS.VMS]VMS-WGET.COM;2-;         DKA100:[SOURCES.WGET-1_10_2B_VMS.VMS]VMS-WGET.COM;1   L As you can see, I changed the procedure to check for MULTINET_SOCKET_LIBRARY rather than MULTINET_ROOT.  H Incidentally, Process Software tries very hard to make sure that the UCXL emulation in MultiNet and TCPware is as accurate as possible -- meaning thatG there's no reason to have a special build configuration on systems with F MultiNet or TCPware.  I suppose this might not be the case for systemsK running very old versions of OpenVMS or MultiNet or TCPware.   Perhaps the  J build procedure should only link against MultiNet or TCPware if explicitlyJ requested by a command-line parameter.  I think it would be safe to ignore5 them completely if it's running on VMS V7.x or later.    Regards,            Jeremy Begg  >    +---------------------------------------------------------+>    |            VSM Software Services Pty. Ltd.              |>    |                 http://www.vsm.com.au/                  |>    |       "OpenVMS Systems Management & Programming"        |>    |---------------------------------------------------------|>    | P.O.Box 402, Walkerville, |  E-Mail:  jeremy@vsm.com.au |>    | South Australia 5081      |   Phone:  +61 8 8221 5188   |>    |---------------------------|  Mobile:  0414 422 947      |>    |  A.C.N. 068 409 156       |     FAX:  +61 8 8221 7199   |>    +---------------------------------------------------------+   ------------------------------  + Date: Tue, 15 Aug 2006 08:02:41 -0500 (CDT) * From: sms@antinode.org (Steven M. Schweda)% Subject: Re: Build procedure for WGET 2 Message-ID: <06081508024175_2027FAC5@antinode.org>  % From: Jeremy Begg <nospam@vsm.com.au>   J > This message is for StevenSchweda, whose mail server is blocking mine. N > (The error message is 'Your IP address or subnet is in my list of bad ones' G > which seems a little odd as none of my systems are listed in any RBL   > database that I know of.)   F    I tend to add whole IP address blocks to my Bad-Clients list when IH get junk e-mail from somewhere.  If I knew your server's address, I'd beH happy to accomodate it.  (In a pinch, there's also a message form on the Web server.)  J > Anyway, today I downloaded WGET 1.10.2b and attempted to build it on my M > OpenVMS Alpha V7.3-2 system.  It failed during the LINK command because it  @ > tried to access MULTINET_SOCKET_LIBRARY, which does not exist. > [...]   F    Yes, the explicit Multinet references are old and probably obsoleteG (VMS V6.x?), and I've suspected this for a while, but I was waiting for E a complaint from someone who had actual Multinet experience, as I run  the HP product here.  =    I think that an explicit command-line request for Multinet E specificity would be best nowadays.  I should be able to arrange that  pretty soon.      Thanks for the complaint.  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------    Date: 15 Aug 2006 07:37:48 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) . Subject: Re: Clients using a GUI to access FTP3 Message-ID: <6nfpEH2LHKic@eisner.encompasserve.org>   _ In article <06081416462199_20200290@antinode.org>, sms@antinode.org (Steven M. Schweda) writes: = > From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  > l >> In article <1155406680.531728.59140@m79g2000cwm.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes: >> >  L >> > Ah, with the year at the end with everything else in order! What system >> > offers this T option? >>  K >>    I routinely use "ls -lrt" on every UNIX, Linux, or cygwin box I have.  > H >    Then, as a big-tine Linux/UNIX user, you should know the difference > between "t" and "T".  F    Oops, I was reading usenet viaa VMS system, and therefor reading in    case-insensitive mode.   A    And accdientally demonstrating in a practical manner that case -    sensitivity is not a good human interface.    ------------------------------  % Date: Tue, 15 Aug 2006 15:53:29 +0100 * From: "Richard Brodie" <R.Brodie@rl.ac.uk>. Subject: Re: Clients using a GUI to access FTP, Message-ID: <ebsn5a$h09$1@south.jnrs.ja.net>  ? "Malcolm Dunnett" <nothome@spammers.are.scum> wrote in message  & news:vMUOshXa4Y0D@malvm9.mala.bc.ca...  M >  True, but most words don't change their meaning if you capitalize them :-)   & Unless you speak German, for example.    ------------------------------  % Date: Tue, 15 Aug 2006 23:09:49 +0930 * From: Mark Daniel <mark.daniel@vsm.com.au>. Subject: Re: Clients using a GUI to access FTP0 Message-ID: <12e3n6uk65hou3a@corp.supernews.com>   Bill Gunshannon wrote:5 > In article <6nfpEH2LHKic@eisner.encompasserve.org>, @ > 	koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: > a >>In article <06081416462199_20200290@antinode.org>, sms@antinode.org (Steven M. Schweda) writes:  >>> >>>From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) >>>  >>> m >>>>In article <1155406680.531728.59140@m79g2000cwm.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes:  >>>>L >>>>>Ah, with the year at the end with everything else in order! What system >>>>>offers this T option? >>>>L >>>>   I routinely use "ls -lrt" on every UNIX, Linux, or cygwin box I have. >>> I >>>   Then, as a big-tine Linux/UNIX user, you should know the difference  >>>between "t" and "T".  >>H >>   Oops, I was reading usenet viaa VMS system, and therefor reading in >>   case-insensitive mode.  >>C >>   And accdientally demonstrating in a practical manner that case / >>   sensitivity is not a good human interface.  >  > L > Tell that to all the newspapers and book publishers and schools and.......K > Humans use mixed case pretty much for everything they do everyday.  Seems , > like a pretty good human interface to me!! >  > bill  C I've always felt case-sensitivity, as contrasted to the use of case F essentially as decoration, to be counter-intuitive.  Mark Daniel, markF daniel, MARK DANIEL, mARK dANIEL and MaRk DaNiEl all refer to the same@ object.  So do PARIS, Paris; Boston, boston; vms and OpenVMS :-)   ------------------------------    Date: 15 Aug 2006 07:40:54 -07001 From: nothome@spammers.are.scum (Malcolm Dunnett) . Subject: Re: Clients using a GUI to access FTP, Message-ID: <vMUOshXa4Y0D@malvm9.mala.bc.ca>  , In article <4ke3p5Fbk6ueU1@individual.net>, -    bill@cs.uofs.edu (Bill Gunshannon) writes:    >>> between "t" and "T". >>  I >>    Oops, I was reading usenet viaa VMS system, and therefor reading in  >>    case-insensitive mode. >>  D >>    And accdientally demonstrating in a practical manner that case0 >>    sensitivity is not a good human interface. > L > Tell that to all the newspapers and book publishers and schools and.......K > Humans use mixed case pretty much for everything they do everyday.  Seems , > like a pretty good human interface to me!! >   L   True, but most words don't change their meaning if you capitalize them :-)   ------------------------------   Date: 15 Aug 2006 16:51:29 GMT( From: bill@cs.uofs.edu (Bill Gunshannon). Subject: Re: Clients using a GUI to access FTP+ Message-ID: <4keccgFbmob8U1@individual.net>   , In article <vMUOshXa4Y0D@malvm9.mala.bc.ca>,4 	nothome@spammers.are.scum (Malcolm Dunnett) writes:. > In article <4ke3p5Fbk6ueU1@individual.net>, / >    bill@cs.uofs.edu (Bill Gunshannon) writes:  >  >>>> between "t" and "T".  >>> J >>>    Oops, I was reading usenet viaa VMS system, and therefor reading in >>>    case-insensitive mode.  >>> E >>>    And accdientally demonstrating in a practical manner that case 1 >>>    sensitivity is not a good human interface.  >>  M >> Tell that to all the newspapers and book publishers and schools and....... L >> Humans use mixed case pretty much for everything they do everyday.  Seems- >> like a pretty good human interface to me!!  >>   > N >   True, but most words don't change their meaning if you capitalize them :-)   Not actually true.   Smith - a name smith - an occupation     bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------    Date: 15 Aug 2006 10:45:39 -0700$ From: "AEF" <spamsink2001@yahoo.com>. Subject: Re: Clients using a GUI to access FTPC Message-ID: <1155663939.208627.228170@i42g2000cwa.googlegroups.com>    Bill Gunshannon wrote:. > In article <vMUOshXa4Y0D@malvm9.mala.bc.ca>,6 > 	nothome@spammers.are.scum (Malcolm Dunnett) writes:/ > > In article <4ke3p5Fbk6ueU1@individual.net>, 1 > >    bill@cs.uofs.edu (Bill Gunshannon) writes:  > >  > >>>> between "t" and "T".  > >>> L > >>>    Oops, I was reading usenet viaa VMS system, and therefor reading in > >>>    case-insensitive mode.  > >>> G > >>>    And accdientally demonstrating in a practical manner that case 3 > >>>    sensitivity is not a good human interface.  > >>O > >> Tell that to all the newspapers and book publishers and schools and....... N > >> Humans use mixed case pretty much for everything they do everyday.  Seems/ > >> like a pretty good human interface to me!!  > >> > > P > >   True, but most words don't change their meaning if you capitalize them :-) >  > Not actually true. >  > Smith - a name > smith - an occupation  >  [...]    First of all, he said *most*.    Second,    Smith went home. smith went home. SMITH WENT HOME.   He works as a smith. he works as a smith. HE WORKS AS A SMITH.  
 He's a smith. 
 He's a Smith. 
 he's a smith. 
 HE'S A SMITH.   C Context! Of course that's not always enough to make it unambiguous.   @ Whether mixed case commands and file-specs are preferable to theD case-blind version is subject to debate, but I think most people whoA started with the latter are definitely not going to like suddenly C having to be constantly aware of case when they use the former! And > that group includes me. I hear that Unix users, when the firstE encounter VMS, have a sudden fear of uppercase letters. Is that true?    ------------------------------  % Date: Tue, 15 Aug 2006 12:50:36 +0100 - From: "chris" <christian.rothwell@baesystems>   Subject: CPU Speed on ALpha ES401 Message-ID: <44e1b242$1_1@glkas0286.greenlnk.net>   J Is there any way of determining the CPU speeds (CPU0 / CPU1)  of an alpha L es40 when someone is logged on and using it. The normal way is putting in a E console and rebooting it , to see the speeds at the start of boot up.    ------------------------------    Date: 15 Aug 2006 05:07:18 -07000 From: "Steve B" <stephen_bainbridge@yahoo.co.uk>$ Subject: Re: CPU Speed on ALpha ES40C Message-ID: <1155643638.260999.170200@i42g2000cwa.googlegroups.com>    chris wrote:K > Is there any way of determining the CPU speeds (CPU0 / CPU1)  of an alpha M > es40 when someone is logged on and using it. The normal way is putting in a G > console and rebooting it , to see the speeds at the start of boot up.    Chris, use SDA:    $ ANAL /SYS  SDA> CLUE CONFIG  / This will show you the cycle time (and the MHz)    Steve    ------------------------------    Date: 15 Aug 2006 05:13:14 -0700 From: etmsreec@yahoo.co.uk$ Subject: Re: CPU Speed on ALpha ES40B Message-ID: <1155643994.872967.247010@i3g2000cwc.googlegroups.com>  # or SHOW CPU/FULL from a DCL prompt.    Steve    Steve B wrote: > chris wrote:M > > Is there any way of determining the CPU speeds (CPU0 / CPU1)  of an alpha O > > es40 when someone is logged on and using it. The normal way is putting in a I > > console and rebooting it , to see the speeds at the start of boot up.  >  > Chris, use SDA:  > 
 > $ ANAL /SYS  > SDA> CLUE CONFIG > 1 > This will show you the cycle time (and the MHz)  >  > Steve    ------------------------------  % Date: Tue, 15 Aug 2006 14:06:23 +0100 - From: "chris" <christian.rothwell@baesystems> $ Subject: Re: CPU Speed on ALpha ES40/ Message-ID: <44e1c402_1@glkas0286.greenlnk.net>    Cheers for that    Chris ( <etmsreec@yahoo.co.uk> wrote in message < news:1155643994.872967.247010@i3g2000cwc.googlegroups.com...% > or SHOW CPU/FULL from a DCL prompt.  >  > Steve  >  > Steve B wrote: >> chris wrote: I >> > Is there any way of determining the CPU speeds (CPU0 / CPU1)  of an  
 >> > alphaL >> > es40 when someone is logged on and using it. The normal way is putting 	 >> > in a J >> > console and rebooting it , to see the speeds at the start of boot up. >> >> Chris, use SDA: >> >> $ ANAL /SYS >> SDA> CLUE CONFIG  >>2 >> This will show you the cycle time (and the MHz) >> >> Steve >    ------------------------------    Date: 15 Aug 2006 07:38:42 -07000 From: "Steve B" <stephen_bainbridge@yahoo.co.uk>$ Subject: Re: CPU Speed on ALpha ES40C Message-ID: <1155652721.981923.175660@m73g2000cwd.googlegroups.com>    etmsreec@yahoo.co.uk wrote: % > or SHOW CPU/FULL from a DCL prompt.  >  > Steve  >  > Steve B wrote: > > chris wrote:O > > > Is there any way of determining the CPU speeds (CPU0 / CPU1)  of an alpha Q > > > es40 when someone is logged on and using it. The normal way is putting in a K > > > console and rebooting it , to see the speeds at the start of boot up.  > >  > > Chris, use SDA:  > >  > > $ ANAL /SYS  > > SDA> CLUE CONFIG > > 3 > > This will show you the cycle time (and the MHz)  > > 	 > > Steve   F Not if your running OpenVMS v7.3, which is what we are running on some- machines. I think it was introduced in v7.3-1    ------------------------------  # Date: Tue, 15 Aug 2006 15:28:32 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>$ Subject: Re: CPU Speed on ALpha ES40. Message-ID: <AKlEg.97$7K3.43@news.cpqcorp.net>   chris wrote:L > Is there any way of determining the CPU speeds (CPU0 / CPU1)  of an alpha N > es40 when someone is logged on and using it. The normal way is putting in a G > console and rebooting it , to see the speeds at the start of boot up.   F    If you have access to a relatively recent OpenVMS release (for the E definitions, and not for the retrieval path), you can use the system  C marketing model (SMM) as an index into the information in ALPHADEF  D include file.   The SMM is available on any Alpha system via, among " other paths, f$getsyi("hw_model").  B    I kinda went gonzo in one of the include files a while back... 7 Here's what you'll see on an OpenVMS I64 V8.2-1 system:   2 $ sear sys$share:*.req alpha$k,es40/wind=1/mat=and   ******************************  SYS$COMMON:[SYSLIB]STARLET.REQ;1  I literal ALPHA$K_AS2208050001 = 1813;    !  AlphaServer ES40 6/500 (1cpu,   10-slot PCI, 8-slot MMB)H literal ALPHA$K_AS2208050002 = 1814;    !  AlphaServer ES40 6/500 (2cpu)H literal ALPHA$K_AS2208050003 = 1815;    !  AlphaServer ES40 6/500 (3cpu)H literal ALPHA$K_AS2208050004 = 1816;    !  AlphaServer ES40 6/500 (4cpu)I literal ALPHA$K_AS2208050101 = 1817;    !  AlphaServer ES40 6/667 (1cpu,   10-slot PCI, 8-slot MMB)H literal ALPHA$K_AS2208050102 = 1818;    !  AlphaServer ES40 6/667 (2cpu)H literal ALPHA$K_AS2208050103 = 1819;    !  AlphaServer ES40 6/667 (3cpu)H literal ALPHA$K_AS2208050104 = 1820;    !  AlphaServer ES40 6/667 (4cpu)I literal ALPHA$K_AS2208050301 = 1861;    !  AlphaServer ES40 6/500 (1cpu,   6-slot PCI, 8-slot MMB) H literal ALPHA$K_AS2208050302 = 1862;    !  AlphaServer ES40 6/500 (2cpu)H literal ALPHA$K_AS2208050303 = 1863;    !  AlphaServer ES40 6/500 (3cpu)H literal ALPHA$K_AS2208050304 = 1864;    !  AlphaServer ES40 6/500 (4cpu)I literal ALPHA$K_AS2208050401 = 1865;    !  AlphaServer ES40 6/667 (1cpu,   6-slot PCI, 8-slot MMB) H literal ALPHA$K_AS2208050402 = 1866;    !  AlphaServer ES40 6/667 (2cpu)H literal ALPHA$K_AS2208050403 = 1867;    !  AlphaServer ES40 6/667 (3cpu)H literal ALPHA$K_AS2208050404 = 1868;    !  AlphaServer ES40 6/667 (4cpu)I literal ALPHA$K_AS2208050501 = 1869;    !  AlphaServer ES40 6/500 (1cpu,   6-slot PCI, 4-slot MMB) H literal ALPHA$K_AS2208050502 = 1870;    !  AlphaServer ES40 6/500 (2cpu)H literal ALPHA$K_AS2208050503 = 1871;    !  AlphaServer ES40 6/500 (3cpu)H literal ALPHA$K_AS2208050504 = 1872;    !  AlphaServer ES40 6/500 (4cpu)I literal ALPHA$K_AS2208050601 = 1873;    !  AlphaServer ES40 6/667 (1cpu,   6-slot PCI, 4-slot MMB) H literal ALPHA$K_AS2208050602 = 1874;    !  AlphaServer ES40 6/667 (2cpu)H literal ALPHA$K_AS2208050603 = 1875;    !  AlphaServer ES40 6/667 (3cpu)H literal ALPHA$K_AS2208050604 = 1876;    !  AlphaServer ES40 6/667 (4cpu)I literal ALPHA$K_AS2208050701 = 1923;    !  AlphaServer ES40 6/500 (1cpu,   10-slot PCI, 4-slot MMB)H literal ALPHA$K_AS2208050702 = 1924;    !  AlphaServer ES40 6/500 (2cpu)H literal ALPHA$K_AS2208050703 = 1925;    !  AlphaServer ES40 6/500 (3cpu)H literal ALPHA$K_AS2208050704 = 1926;    !  AlphaServer ES40 6/500 (4cpu)I literal ALPHA$K_AS2208050801 = 1927;    !  AlphaServer ES40 6/667 (1cpu,   10-slot PCI, 4-slot MMB)H literal ALPHA$K_AS2208050802 = 1928;    !  AlphaServer ES40 6/667 (2cpu)H literal ALPHA$K_AS2208050803 = 1929;    !  AlphaServer ES40 6/667 (3cpu)H literal ALPHA$K_AS2208050804 = 1930;    !  AlphaServer ES40 6/667 (4cpu)I literal ALPHA$K_AS2208050901 = 1931;    !  AlphaServer ES40 6/500 (1cpu,   10-slot PCI, 4-slot MMB)H literal ALPHA$K_AS2208050902 = 1932;    !  AlphaServer ES40 6/500 (2cpu)H literal ALPHA$K_AS2208050903 = 1933;    !  AlphaServer ES40 6/500 (3cpu)H literal ALPHA$K_AS2208050904 = 1934;    !  AlphaServer ES40 6/500 (4cpu)I literal ALPHA$K_AS2208050A01 = 1935;    !  AlphaServer ES40 6/667 (1cpu,   10-slot PCI, 4-slot MMB)H literal ALPHA$K_AS2208050A02 = 1936;    !  AlphaServer ES40 6/667 (2cpu)H literal ALPHA$K_AS2208050A03 = 1937;    !  AlphaServer ES40 6/667 (3cpu)H literal ALPHA$K_AS2208050A04 = 1938;    !  AlphaServer ES40 6/667 (4cpu)D literal ALPHA$K_AS220B050101 = 1949;    !  AlphaStation ES40 67/667  (1cpu) (6-slot PCI, 4-slot MMB) J literal ALPHA$K_AS220B050102 = 1950;    !  AlphaStation ES40 67/667 (2cpu)J literal ALPHA$K_AS220B050103 = 1951;    !  AlphaStation ES40 67/667 (3cpu)J literal ALPHA$K_AS220B050104 = 1952;    !  AlphaStation ES40 67/667 (4cpu)D literal ALPHA$K_AS220B050201 = 1957;    !  AlphaStation ES40 67/667   (1cpu) (10-slot PCI, 8-slot MMB)J literal ALPHA$K_AS220B050202 = 1958;    !  AlphaStation ES40 67/667 (2cpu)J literal ALPHA$K_AS220B050203 = 1959;    !  AlphaStation ES40 67/667 (3cpu)J literal ALPHA$K_AS220B050204 = 1960;    !  AlphaStation ES40 67/667 (4cpu)D literal ALPHA$K_AS220C050001 = 1984;    !  AlphaStation ES40 68/833  (1cpu) (10-slot PCI)J literal ALPHA$K_AS220C050002 = 1985;    !  AlphaStation ES40 68/833 (2cpu)J literal ALPHA$K_AS220C050003 = 1986;    !  AlphaStation ES40 68/833 (3cpu)J literal ALPHA$K_AS220C050004 = 1987;    !  AlphaStation ES40 68/833 (4cpu)D literal ALPHA$K_AS220C050101 = 1988;    !  AlphaStation ES40 68/833  (1cpu) (6-slot PCI) J literal ALPHA$K_AS220C050102 = 1989;    !  AlphaStation ES40 68/833 (2cpu)J literal ALPHA$K_AS220C050103 = 1990;    !  AlphaStation ES40 68/833 (3cpu)J literal ALPHA$K_AS220C050104 = 1991;    !  AlphaStation ES40 68/833 (4cpu) $    ------------------------------  % Date: Tue, 15 Aug 2006 09:25:24 -0700 % From: DeanW <dean.woodward@gmail.com> % Subject: Re: I should'a known better! I Message-ID: <3f119ada0608150925v2c3ab034u3acf135867ae7a0e@mail.gmail.com>   : On 8/12/06, JF Mezei <jfmezei.spamnot@teksavvy.com> wrote:G > I really do not understand why corporations are paying for such voice 9 > response software/hardware when customers despise them.    a) it's cheaper than liveware. b) the customers tolerate it. E c) nobody complains. (The fact that there's no channel to do so might " have something to do with that...)   --   Dean Woodward    =o&o  dean.woodward@gmail.com    ------------------------------  % Date: Tue, 15 Aug 2006 10:31:14 -0600 + From: Mark Berryman <mark@theberrymans.com> Y Subject: Missing freeware submission (was Freeware V8.0 and July 2006 OpenVMS FAQ Availab % Message-ID: <44e19483$1@mvb.saic.com>    Hoff Hoffman wrote:  > D > The contents of the HP OpenVMS Freeware V8.0 distribution are now : > available for downloads at the OpenVMS Freeware website: > , >   <http://www.hp.com/go/openvms/freeware/> > K > A listing of all packages is available via the main Freeware page, as is  4 > a file containing all of the submission abstracts.  N Well, it looks like I was one of the ones whose submission was lost by the HP B web page since I never got any response and it is not listed here.  N So, for anyone who is interested, you can get a PCSI kit of Ghostscript V8.54 < at http://mvb.saic.com/freeware/pcsi_kits/ghostscript-v0854/  P Alpha and IA64 kits are available.  No VAX kit was produced since this code now  depends upon 64-bit integers.   
 Mark Berryman    ------------------------------    Date: 14 Aug 2006 22:40:54 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> B Subject: OpenVMS Integrity install CD's and layered products mediaB Message-ID: <1155620454.158056.85550@b28g2000cwb.googlegroups.com>  D I'm not sure exactly how they are structured - my only experience isF with the VAX/Alpha distribution.  I have a need now to borrow a set ofA the Integrity OpenVMS V8.2-1 (and/or V8.2 or 8.3 for that matter) F installation media and any available layered products.  Geography wise@ I am near Cincinnati, Ohio, USA.  Any help would be appreciated. Thanks.      John H. Reinhardt    ------------------------------  % Date: Tue, 15 Aug 2006 12:57:43 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> ) Subject: Re: Products in Operating System : Message-ID: <IvidnfqtBOOYYHzZnZ2dnUVZ_oidnZ2d@comcast.com>   H Vlems wrote: > etmsreec@yahoo.co.uk schreef:  >  > I >>As a slightly different issue but along the same lines, how come DECnet E >>Phase IV is considered to be a system-integrated product yet DECnet  >>Phase V is a layered product?  >> >>Steve  >  > G > Possibly historical reasons  for that. Once DECnet was a prerequisite < > for clustering and that functionality was embedded in VMS.E > IIRC DECnet before VMS V5.0 was a real layered product in the sense H > that it came on its own TK50 tape. Or is this my memory playing tricks3 > again and did that only happen to microVMS users?  >  > Hans >   H Not quite correct.  DECnet was installed as part of the O/S.  The DECnetC LICENSE KEY came on a separate TK50!  It wouldn't work without the   license key.   ------------------------------  % Date: Tue, 15 Aug 2006 20:03:21 +0800 3 From: "Richard Maher" <maher_rj@hotspamnotmail.com> R Subject: The Future of VMS development! (Was Re: Multinet's _BG: Driver and IPsec)1 Message-ID: <ebsd12$omi$1@news-02.connect.com.au>    Hi Richard,   6 Really appreciate the detailed reply! Thanks for that.  K > One of the things that makes IPSEC in MultiNet 5.0 difficult is that only  > static keys are 6 > supported.  Windows/IPsec requires automatic keying.  E Are your "static keys" equivalent to their "pre-shared secrets"? (The J terminology drives me nuts over there. Although, I'm actually in love withG the idea of an "ambient transaction". The "Default transaction" is like 
 soooo 90s :-)   E > We have done some work on automatic key exchange, but there was not K > sufficient time to get it tested and documented for MultiNet 5.1; it will  be > part of MultiNet 5.2.   J Do you have a "Road Map" or ETA for 5.2? Admittedly, the pressure's off asJ UCX IPsec will be held up indefinitely while Nurse Ratched and her croniesC have had a chance to vet it for C conformity and a total absence of F inner-mode interfaces, but it always helps be first-to-market in theseK situations. (Then they'll have to kiss BEA's and IBM's collective arses and G decide it's prudent to cancel the whole thing, so you should be OK this 	 century!)   G Look, I know it's been said (more than once) that I'm slightly prone to J superlative (Pig's arse :-), but IPsec *is* the mut's nuts! It's what realL infrastructure is all about. IMHO "Connection-Oriented IPsec" has a big partD to play in the future of application development and the internet inI general. Bending over backwards trying to shoe horn some contextless "Web H Page Browser" into the guise of a middleware backbone is always going to stumble.  G > security policies and how to do manual keying.  See chapter 31 of the  > Installation and > Administrator's Guide.@ > http://www.process.com/tcpip/mndocs51/multinet_admin_guide.pdf  J A couple of quick observations/questions (I didn't look through the manual
 in detail): -   > Do you provide "From any port" - "To this port" functionality?  J "At the moment IPsec can't be invoked with setsockopt()" Will this be done> anytime soon? You still support per-port configuration, right?   Cheers Richard Maher  7 "Richard Whalen" <WhalenR@process.com> wrote in message % news:ebpu23$fp7$1@news.process.com... @ > "Richard Maher" <maher_rj@hotspamnotmail.com> wrote in message- > news:ebpkl6$lsi$1@news-02.connect.com.au...  > > Hi,  > > J > > I just had a disappointing glance through the latest VMS road map, and > once= > > again found UCX's IPsec capability still some way off :-(  > > H > > Having said that, I've just (today) realized that Process Software's; > > Multinet already advertises this functionality for VMS.  > >  > > When was the release date? > I > IPSEC was included as part of MultiNet 5.0; the release notes are dated 
 > June, 2004.  >  > > ! > > Is anyone out there using it?  > H > I believe that some customers may be using it because we have had some > questions about it.  >  > > J > > Does anyone have VMS/Multinet/IPsec applications talking transparently > over$ > > TCP/IP sockets to Windows/IPsec? > K > One of the things that makes IPSEC in MultiNet 5.0 difficult is that only  > static keys are 6 > supported.  Windows/IPsec requires automatic keying. > E > We have done some work on automatic key exchange, but there was not K > sufficient time to get it tested and documented for MultiNet 5.1; it will  be > part of MultiNet 5.2.  >  > > H > > Is it truly transparent to the application/socket programmer? (these > ports, > > these addresses, GO!)? > I > Yes, it is transparent to the application/socket programmer, especially  with > the automatic J > key exchange program in place.  An administrator still has to set up the > security policies E > (which systems require which types of security), and set up the key  exchange > program, butH > once that is done the key exchange program will securely negotiate and > exchange keys J > with the remote system when a connection is opened, then the key will be > used for theJ > communication for that connection.   The only thing that the application may 
 > notice is a % > delay at connection initation time.  > > / > > Is a simple configuration script available?  > H > The documentation and examples for MultiNet V5.2 will include a simple > configuration I > script for the key exchange program (racoon) that will work between any  two  > systems thatJ > have had security policies defined.  The current documentation shows how to > set upG > security policies and how to do manual keying.  See chapter 31 of the  > Installation and > Administrator's Guide.@ > http://www.process.com/tcpip/mndocs51/multinet_admin_guide.pdf >  > > 3 > > Why didn't they do the same thing with TCPware?  > > J > > I've tested my software with UCX and TCPWare but not Multinet, but I'm > sureL > > Process Software would rather die then allow a behavioural inconsistency/ > > between their various BG: offerings on VMS?  > L > Process Software tries to keep the BG: device offered in both MulitNet and> > TCPware compatible with what is in TCP/IP Services.  When an incompatibility  > is9 > discovered we work to fix the problem in both products.  >  > > % > > Is anyone else as ignorant as me?  > >  > > Cheers Richard Maher > > L > > PS. Is some smart arse would like to chime in with "The documentation isJ > > quite clear on the subject" or "I found it with only one finger" or "I > justL > > wait for posts like yours so I can, once more, sing 'I'm too sexy for myI > > shirt!'" then if you could take the time to mention chpt and verse of 5 > > provide a pointer then that would be just peachy.  > >  > >  >  > Richard Whalen > Process Software >  >    ------------------------------  % Date: Tue, 15 Aug 2006 11:37:57 -0400 , From: "Richard Whalen" <WhalenR@process.com>V Subject: Re: The Future of VMS development! (Was Re: Multinet's _BG: Driver and IPsec)+ Message-ID: <ebspoo$frr$1@news.process.com>   > "Richard Maher" <maher_rj@hotspamnotmail.com> wrote in message+ news:ebsd12$omi$1@news-02.connect.com.au... 
 > Hi Richard,  > 8 > Really appreciate the detailed reply! Thanks for that. > H > > One of the things that makes IPSEC in MultiNet 5.0 difficult is that only > > static keys are 8 > > supported.  Windows/IPsec requires automatic keying. > G > Are your "static keys" equivalent to their "pre-shared secrets"? (The L > terminology drives me nuts over there. Although, I'm actually in love withI > the idea of an "ambient transaction". The "Default transaction" is like  > soooo 90s :-)   G Yes, "static keys" can be considered to be "pre-shared secrets".   With G static keying system management needs to administer the distribution of G keys, keep them secure, and coordinate which keys are used when if keys ) are changed on any sort of regular basis.   E Even when the key exchange program is in place systems need to have a L method of proving that they are who they say they are during the negotiationK process.  This may also be done with a "pre-shared secret", but since it is H used in a more limited manner keeping it secure is an easier task.  WhenK the key exchange program is in use the actual keys that are used to encrypt B or authenticate packets are changed more frequently which provides better security.   > G > > We have done some work on automatic key exchange, but there was not H > > sufficient time to get it tested and documented for MultiNet 5.1; it will > be > > part of MultiNet 5.2.  > * > Do you have a "Road Map" or ETA for 5.2?  I We have some estimates, but I don't know what is being told to customers. G I would recommend talking with sales or marketing for this information.    > L > A couple of quick observations/questions (I didn't look through the manual > in detail): -  > @ > Do you provide "From any port" - "To this port" functionality? > L > "At the moment IPsec can't be invoked with setsockopt()" Will this be done@ > anytime soon? You still support per-port configuration, right? >   5 Yes, a security policy can specify a particular port:  spdadd src-ip dst-ip[port] ...L will provide security between the specified source to the particular port onI the specified destination.  The ip addresses can include a prefix length, ? so you can get large groups of addresses with a few rules.  The 
 documentation K is primarily a specification of the syntax and hence it can be easy to miss  some of the functionality.  < We have not documented the programming mechanism for settingG security policy.  If customers need access to security policies from an E application, then they should contact Process Software so that we can B work with them and we can iron out some of the rough points in the+ programming interface before we publish it.    ------------------------------  # Date: Tue, 15 Aug 2006 15:37:35 GMT 3 From: Wayne Morrison <Wayne.Morrison_NOSPAM@hp.com> / Subject: Re: [VMS] Products in Operating System . Message-ID: <3TlEg.99$QN3.78@news.cpqcorp.net>    Peter 'EPLAN' LANGSTOEGER wrote:     ... J > 3) I assume that products like CDSA and KERBEROS (packaged into OPENVMS)L > can be upgraded to a newer version (eg. install CDSA V2.1 onto VMS V7.3-2)J > But as they are not contained in the VMS systems Software Rollout ReportK > http://www.openvms.digital.com/openvms/os/swroll/VAROL.HTML I'm not sure. N > (I think, KERBEROS V2.1 runs perfect on V7.3-2) Has anyone tried it already? ...   F Yes, CDSA and Kerberos can be upgraded to newer versions - as long as G the newer version supports the older operating system version.  If you  I try to install the new version, it will either install, or tell you that  H   it doesn't support the version of OpenVMS you're trying to install it < on.  Both are installed via PCSI kits, whether during a VMS + install/upgrade or as a separate kit later.   E Kerberos V2.1 was build against OpenVMS V7.3-2, and will run on that  G version with no problems.  It's supported on V7.3-2 to V8.2.  Kerberos  E V3.0 will be shipping with V8.3, and is a much newer version that is  G also supported back to V7.3-2.  Kerberos V3.0 is based on MIT Kerberos   1.4.1.   	Wayne Morrison, CISSP  	Project Leader, CDSA & Kerberos 	OpenVMS Engineering   ------------------------------   End of INFO-VAX 2006.453 ************************