0 INFO-VAX	Tue, 14 Jan 2003	Volume 2003 : Issue 28      Contents:0 Access linux and/or windows directories with vms4 Re: Access linux and/or windows directories with vms4 Re: Access linux and/or windows directories with vms4 Re: Access linux and/or windows directories with vms4 RE: Access linux and/or windows directories with vms, ANN: DCL-EXPAND added to HG/Process archives Re: Boot Contest change  Re: Boot Contest change  Re: Boot Contest change  Re: CSWS PHP 1.1 php.ini bug? & decnet  - mailbox programming question Re: DECnet Problem Re: DECnet Problem Re: DECnet Problem Re: Freeware VDD64 Re: GE HCT Tool Kit  Re: Help with VAX Basic  Re: Help with VAX Basic  RE: Help with VAX Basic J Re: How much disk I/O can I do with a sys$QIOW IO$_WRITEVBLK/IO$_READVBLK?J Re: How much disk I/O can I do with a sys$QIOW IO$_WRITEVBLK/IO$_READVBLK?J Re: How much disk I/O can I do with a sys$QIOW IO$_WRITEVBLK/IO$_READVBLK?) HP Sets the Stage for Alpha's Last Hurrah - Re: HP Sets the Stage for Alpha's Last Hurrah - Re: HP Sets the Stage for Alpha's Last Hurrah - Re: HP Sets the Stage for Alpha's Last Hurrah # Re: Marvel talks at The Inquirer... # Re: Marvel talks at The Inquirer... # Re: Marvel talks at The Inquirer...  Re: Microvax Floating point  Re: MOP with Multiple NICs Re: MOP with Multiple NICs MOP with Multiple NICs. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today?. Re: Most common OpenVMS versions in use today? Re: Network troubleshooters  Re: Newbie to OpenVMS. OpenVMS license question Re: OpenVMS license question Re: Reading file in DCL  Re: Reading file in DCL ; Re: Retrieve RMS Key information at runtime (using Fortran)  Re: SMTP mail: TFF facility  Re: Suppressing SMTP headers Surplus Kit 8 The Inquirer: How Mike Capellas was "castrated" by CarlyP The manual says "Do not use QIO for reading from a file" has anyone heard of thi" Re: The need for reliable desktops Re: vax6k.openecs.org rebirth  Re: vax6k.openecs.org rebirth ! VMS on Itanic boot report sighted % Re: VMS on Itanic boot report sighted % Re: VMS on Itanic boot report sighted % RE: VMS on Itanic boot report sighted % Re: VMS on Itanic boot report sighted % Re: VMS on Itanic boot report sighted % RE: VMS on Itanic boot report sighted  Re: What does RWCLU mean? / Re: Why doesn't SET BREAK %LABEL work any more? / Re: Why doesn't SET BREAK %LABEL work any more?  Re: Wireless Ethernet  Re: Wireless Ethernet   F ----------------------------------------------------------------------  % Date: Tue, 14 Jan 2003 13:29:59 +0100 = From: "Franz-Jrgen Tollmann" <tollmann@vim.uni-wuerzburg.de> 9 Subject: Access linux and/or windows directories with vms ' Message-ID: <3e2402cc@uni-wuerzburg.de>    Hi,   H we are looking for a solution to access windows or linux directories via network with a vms system.G The operater of the vms-system doesnt want to install software such as D samba on the VMS Alpha. It would be ok for him if we would install aG software that makes him able to access the directories on or windows or  linux machine.	 Any idea?    Thanks a lot Franz    ------------------------------  % Date: Tue, 14 Jan 2003 08:25:03 -0500 & From: Ken Robinson <kenrbnsn1@rcn.com>= Subject: Re: Access linux and/or windows directories with vms < Message-ID: <5.1.0.14.2.20030114082150.030664d0@pop.rcn.com>  ; At 01:29 PM 1/14/2003 +0100, Franz-J=FCrgen Tollmann wrote: I >we are looking for a solution to access windows or linux directories via  >network with a vms system. J >The operater of the vms-system doesn=B4t want to install software such asE >samba on the VMS Alpha. It would be ok for him if we would install a H >software that makes him able to access the directories on or windows or >linux machine. 
 >Any idea?  G Take a look at the NFS package that comes with TCP/IP. You don't say=20 . whether the Alpha is running a TCP/IP package.   Ken Robinson   ------------------------------  % Date: Tue, 14 Jan 2003 08:32:25 -0500 * From: "Stanley F. Quayle" <stan@stanq.com>= Subject: Re: Access linux and/or windows directories with vms . Message-ID: <3E23CB19.27177.9E82A3B@localhost>  7 On 14 Jan 2003 at 13:29, Franz-J=FCrgen Tollmann wrote: J > we are looking for a solution to access windows or linux directories via > network with a vms system.K > The operater of the vms-system doesn=B4t want to install software such a=  s F > samba on the VMS Alpha. It would be ok for him if we would install aI > software that makes him able to access the directories on or windows or  > linux machine.  A The Linux machines can export directories to VMS using NFS.  The  D exported piece of Linux filesystem appears as a disk device.  I use   this all the time on my systems.  C There's also DECnet for Linux, but it's not quite as stable as NFS.   F There might be a NFS implementation for Windows (you didn't say which 	 version).   A If you don't need "directories", but just "files", there are FTP  ; servers available for Windows.  Some of them are shareware.   
 --Stan Quayle  Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------    Date: 14 Jan 2003 07:55:34 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) = Subject: Re: Access linux and/or windows directories with vms 3 Message-ID: <PbPVke6ama+o@eisner.encompasserve.org>   g In article <3e2402cc@uni-wuerzburg.de>, "Franz-Jrgen Tollmann" <tollmann@vim.uni-wuerzburg.de> writes:  > Hi,  > J > we are looking for a solution to access windows or linux directories via > network with a vms system.I > The operater of the vms-system doesnt want to install software such as F > samba on the VMS Alpha. It would be ok for him if we would install aI > software that makes him able to access the directories on or windows or  > linux machine. > Any idea?   G    Both TCP/IP and DECnet come to mind since both are available for all 8    three machines.  What does he have on his VMS system?   ------------------------------  % Date: Tue, 14 Jan 2003 06:39:13 -0800 # From: "Tom Linden" <tom@kednos.com> = Subject: RE: Access linux and/or windows directories with vms 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIMEJJGGAA.tom@kednos.com>    >-----Original Message----- 0 >From: Stanley F. Quayle [mailto:stan@stanq.com]( >Sent: Tuesday, January 14, 2003 5:32 AM >To: Info-VAX@Mvb.Saic.Com> >Subject: Re: Access linux and/or windows directories with vms >  > 6 >On 14 Jan 2003 at 13:29, Franz-Jrgen Tollmann wrote:K >> we are looking for a solution to access windows or linux directories via  >> network with a vms system. J >> The operater of the vms-system doesnt want to install software such asG >> samba on the VMS Alpha. It would be ok for him if we would install a J >> software that makes him able to access the directories on or windows or >> linux machine.  > A >The Linux machines can export directories to VMS using NFS.  The D >exported piece of Linux filesystem appears as a disk device.  I use! >this all the time on my systems.  > D >There's also DECnet for Linux, but it's not quite as stable as NFS. > F >There might be a NFS implementation for Windows (you didn't say which
 >version). > A >If you don't need "directories", but just "files", there are FTP < >servers available for Windows.  Some of them are shareware.  G And if you don't need to process those files in Lin or Win then can use $ Putty, which only displays a window.   >  >--Stan Quayle >Quayle Consulting Inc.  >  >---------- D >Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-16712 >8572 North Spring Ct. NW, Pickerington, OH  43147> >Preferred address:  stan@stanq.com       http://www.stanq.com >  >  >---' >Incoming mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com). B >Version: 6.0.435 / Virus Database: 244 - Release Date: 12/30/2002 >  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).A Version: 6.0.435 / Virus Database: 244 - Release Date: 12/30/2002    ------------------------------  # Date: Tue, 14 Jan 2003 16:58:21 GMT - From: goathunter@goatley.com (Hunter Goatley) 5 Subject: ANN: DCL-EXPAND added to HG/Process archives 0 Message-ID: <3e243d02.84352071@news.process.com>  F A new package, DCL-EXPAND, has been added to my VMS freeware archives.  J EXPAND is a utility for generating repetitive scripts,  called expansions.K EXPAND generates an expansion by applying a list to a template.  This works L much the same way as a mail merge facility generates a mailing by applying a mailing list to a form letter.  H EXPAND is written entirely in DCL by David Cressey.  Thanks to David for contributing the package.   K You can download the files from the Process Software OpenVMS Resource Page:    http://www.process.com/openvms/   " Or by using one of the URLs below:  : ftp://ftp.process.com/vms-freeware/fileserv/dcl-expand.zip? http://vms.process.com/ftp/vms-freeware/fileserv/dcl-expand.zip 6 ftp://ftp.tmk.com/vms-freeware/fileserv/dcl-expand.zip; http://www.tmk.com/ftp/vms-freeware/fileserv/dcl-expand.zip   % Or from your favorite mirror archive.    Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/ 8 goathunter@goatley.com    http://www.goatley.com/hunter/< New Robert R. McCammon site: http://www.RobertRMcCammon.com/   ------------------------------  % Date: Tue, 14 Jan 2003 14:55:05 +0000 % From: Alan Greig <a.greig@virgin.net>   Subject: Re: Boot Contest change8 Message-ID: <9n882v0d8liral545v1irfpfsu5me4ih1k@4ax.com>  E On Thu, 09 Jan 2003 15:37:49 +0000, Andrew Harrison SUNUK Consultancy . <Andrew_No.Harrison_No@nospamn.sun.com> wrote:  * >I also don't know what I would do with an >OpenVMS shirt.   E Walk into a "Linux Powered" Internet Cafe wearing it. Doesn't work in F a Gatespowered establishment as they have no idea what it is. Me and aE colleague did this once at a specific event full of Linuxoids. Amused 9 the hell out of one well known UK trade press journalist.    > . >So you guys can share the 5 among yourselves. > / >Incedentally JF arn't you a resident of Canada 
 >not the US ?  >  >Regards >Andrew Harrison >    -- Alan   ------------------------------  + Date: Tue, 14 Jan 2003 16:44:41 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>   Subject: Re: Boot Contest change; Message-ID: <01KR8D3TUAYE96VN71@sysdev.deutsche-boerse.com>   - > > I also don't know what I would do with an  > > OpenVMS shirt. > G > Walk into a "Linux Powered" Internet Cafe wearing it. Doesn't work in H > a Gatespowered establishment as they have no idea what it is. Me and aG > colleague did this once at a specific event full of Linuxoids. Amused ; > the hell out of one well known UK trade press journalist.   H Does anyone still have the DEC shoelaces?  In my opinion, that's what a D VMS boot should be laced with.  [Dons asbestos pun suit for fear of  groans]    ------------------------------  + Date: Tue, 14 Jan 2003 16:49:50 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>   Subject: Re: Boot Contest change; Message-ID: <01KR8DB9UNUK96VN71@sysdev.deutsche-boerse.com>   - > > I also don't know what I would do with an  > > OpenVMS shirt. > G > Walk into a "Linux Powered" Internet Cafe wearing it. Doesn't work in H > a Gatespowered establishment as they have no idea what it is. Me and aG > colleague did this once at a specific event full of Linuxoids. Amused ; > the hell out of one well known UK trade press journalist.   ? I'm reminded of the scene in Quadrophenia where Jimmy puts "My  , Generation" on the record player at a party.   ------------------------------  % Date: Wed, 15 Jan 2003 00:42:46 +1030 / From: Mark Daniel <Mark.Daniel@wasd.vsm.com.au> & Subject: Re: CSWS PHP 1.1 php.ini bug?, Message-ID: <3e241ad7_4@news.chariot.net.au>   Mark Daniel wrote:K > I am finding it difficult to change configuration parameters via PHP.INI.  > I > To demonstrate (this uses the PHP.EXE that is delivered with CSWS PHP):  > $ >   $ PHP = "$PHP_ROOT:[BIN]PHP.EXE", >   $ PIPE PHP -i | SEARCH SYS$INPUT: EXPOSE > H > Note that the displayed value (amongst all the HTML markup) is 'on'.  A > Now EDIT the file PHP_ROOT:[000000]PHP.INI and change the line  J > "php_expose = on" to php_expose = off".  Do the above pipe|search again J > and see if the reported value of php_expose has changed to "off".  I'll K > bet it hasn't, and neither can most (all?) non-'extension' directives in   > the file be changed. > E > I am not using this with CSWS and MOD_PHP and so cannot comment on  K > whether PHP.INI can be used in that configuration.  It should work using   > the above in any case. > 1 > Can anyone confirm or dispute this observation?  >   * OK.  It doesn't work with CSWS 1.3 either!  "    $ type APACHE$ROOT:[PHP]PHP.INI    ;C    ; Uncomment any of the extension below to have them automaticly  
 loaded by PHP     ;    expose_php=off     extension=php_bcmath.exe     extension=php_calendar.exe     extension=php_ctype.exe
    8< snip 8<    php_info() ...  
    8< snip 8< 5    error_reporting    no value               no value /    expose_php         On                     On A    extension_dir      /php_root/extensions   /php_root/extensions 
    8< snip 8< ?    _SERVER["SERVER_SOFTWARE"] Apache/1.3.26 (OpenVMS) PHP/4.1.1 
    8< snip 8<    Log a software call?  F +--------------------------------------------------------------------+E   Mark Daniel                         http://wasd.vsm.com.au/adelaide F   mailto:Mark.Daniel@wasd.vsm.com.au (Mark.Daniel@dsto.defence.gov.au)F +--------------------------------------------------------------------+   ------------------------------    Date: 14 Jan 2003 07:26:23 -0800# From: jiannisf@yahoo.com (Jiannisf) / Subject: decnet  - mailbox programming question = Message-ID: <fbc2930d.0301140726.7a2b86ff@posting.google.com>   E I want to create a process in OVMS, which will communicate via Decnet 6 at one side and from an AST mailbox at the other side.  2 How can I create an AST for the Network messages ?  F Since now I'm using an infinite loop which reads network (sys$waitfr (D sys$get(RAB) ), but that approach doesnt work with AST mailboxes (?)   Thanx in advance   ------------------------------  % Date: Tue, 14 Jan 2003 09:07:11 +0100 , From: "Ferry Bolhar" <bol@adv.magwien.gv.at> Subject: Re: DECnet Problem 7 Message-ID: <1042531475.49162@mozart.adv.magwien.gv.at>   	 Hi folks,   H our news server was down the last days - so I just wanted to ask whetherB there are new postings to my question concerning the problems withK DECnet-Plus (see below). I can see just 2 answers to this - one from Grard I Labadie and the second from myself. Please, if any other has responded to = this thread, do it again - I have not received these answers.    MTIA and kind greetings,   Ferry    > Hi folks,  > * > here are the answers to Grards posting: > 7 > > $ Mc ncl SHOW OSI TRANSPORT TEMPLATE OSIT$RFC* NAME 
 > > does show  >  > > Identifiers  > > Name = osit$rfc1006  > 2 > > Node 0 OSI Transport Template osit$rfc1006plus* > > at 1997-02-20-10:54:23.502-07:00I0.909 > >  > > Identifiers  > >  > > Name = osit$rfc1006plus  > > or not ? >  > Yes, shows the above.  >  > > Does > > $ ucx sh dev > > show the ports 102 and 399 > J > No, doesn't (at least not as local ports). I should mention that I _can_J > connect to a remote node over RFC1006 _from_ MVIE63. But I can't connect > _to_ MVIE63 this way.  > $ > > If MVIE63 has an IP @ of 1.2.3.4
 > > What does  > > $ telnet 1.2.3.4 102 > > $ telnet 1.2.3.4 399 > > 
 > > show ? > > ( > > %TELNET-I-TRYING, Trying ... 1.2.3.48 > > %TELNET-E-CONNFAIL, Failed to connect to remote host8 > > -SYSTEM-F-REJECT, connect to network object rejected > > or > > ( > > %TELNET-I-TRYING, Trying ... 1.2.3.49 > > %TELNET-I-SESSION, Session 01, host 1.2.3.4, port 102  > > TELNET> EXIT > % > Connect to network object rejected.  >  > > What gives > > $ set host ip$1.2.3.4  > ? > %SYSTEM-F-UNREACHABLE, remote node is not currently reachable  > E > > Check if your node is configured to allow DECnet/OSI to perform a 3 > > BIND operation, with the following NCL command: 0 > > NCL> SHOW SESSION CONTROL NAMING SEARCH PATH > / > Yes, it is. Contains this naming search path:  >  > Naming Search Path = > {  > [  > Directory Service = Local ,  > Template = "*" > ] ,  > [  > Directory Service = Local ,  > Template = "local:*" > ] ,  > [  > Directory Service = Domain , > Template = "*" > ] ,  > [  > Directory Service = Domain ," > Template = "*.adv.magwien.gv.at" > ] ,  > [  > Directory Service = Domain ,# > Template = "*.host.magwien.gv.at"  > ]  > }  > % > and this backtranslation sear path:  >  > Backtranslation Search Path =  > {  > [  > Directory Service = Local ,  > Template = ""  > ] ,  > [  > Directory Service = Domain , > Template = ""  > ]  > }  > L > As mentioned in my first posting, i have a _similar_ configuration on many/ > other systems where it runs without problems.  >  > Any ideas? >  > MTIA and kind greetings, >  > Ferry  > ---  > Ing. Ferry Bolhar-Nordenkampf ' > Municipality of Vienna, Department 14  > A-1010 Vienna / AUSTRIA  > E-mail: bol@adv.magwien.gv.at < > "Wenn hier einer schuld ist, dann immer nur der Computer." >  >  >  >    ------------------------------  % Date: Tue, 14 Jan 2003 04:25:37 -0500   From: John Santos <JOHN@egh.com> Subject: Re: DECnet Problem 4 Message-ID: <1030114034345.631B-100000@Ives.egh.com>  ( On Tue, 14 Jan 2003, Ferry Bolhar wrote:   > Hi folks,  >=20J > our news server was down the last days - so I just wanted to ask whetherD > there are new postings to my question concerning the problems withL > DECnet-Plus (see below). I can see just 2 answers to this - one from G=E9= rardK > Labadie and the second from myself. Please, if any other has responded to ? > this thread, do it again - I have not received these answers.  >=20 > MTIA and kind greetings,  E I don't know if anyone else has responded...  I have had intermittent C problems with DECnet-Plus not working over TCP/IP.  Rebooting cured C it (all but one time, when rebooting twice cured it.)  We are using @ TCPWare on most of our systems, but UCX/TCPIP on a few.  I can'tB remember if it was restricted to TCPWare; I think it happened with> TCPIP Services as well.  It happened on both VAXes and Alphas.  D The symptoms (aside from it not working!) were 1) you didn't see the normal OPCOM messages, i.e.:  8 %%%%%%%%%%%  OPCOM  13-JAN-2003 14:17:11.55  %%%%%%%%%%%  Message from user TPCONS on IVES -- TPCONS: Listen to PWIP Done  8 %%%%%%%%%%%  OPCOM  13-JAN-2003 14:17:11.55  %%%%%%%%%%%  Message from user TPCONS on IVES -- TPCONS: Listen to PWIP Done  A (These messages usually appear when you boot.)  And 2) The TCP/IP : stack didn't show anything listening on ports 102 and 399.    ? I reported it to DEC years ago, but it wasn't reproducible, and ? they always blamed TCPWARE... :-)  (I'm pretty sure it broke on ; a system running UCX/TCPIP at least once, so TCPWARE really < couldn't be to blame...)  (Actually, they suggested it might: be a quota problem with NET$ACP, and to try increasing its7 BYTLM quota to 50000 by defining an appropriate logical @ name in SYS$MANAGER:NET$LOGICALS.COM and rebooting.  This didn't> help.  Rebooting cured the problem, as it had in the past, but7 it happened again later with the increased BYTLM.  They / also mentioned similar problems with Multinet.)     = Something in the fine print of a recent ECO (or may a comment : in c.o.v by someone in the know) led me to believe that it: might be fixed.  I can't find my notes about this, though,> and nothing in the various DNV ECO release notes rings a bell.  8 I think it was 6-8 months ago, which would correspond to7 ECO 5 for Alpha V7.2-1 (there has since been an ECO 6), 6 and probably ECO 2 for Alpha V7.3, and maybe ECO 2 for6 VAX V7.3.  Or maybe it was a SYS or LAN or DRIVER ECO?; OTOH, I also installed TCPWARE V5.6 at about the same time.   : At any rate, it hasn't happened since I installed whatever ECO's I suspected might fix it.   9 I'm sorry this is so vague...  The little gray cells must 9 be getting full.  I hope a vague answer is better than no  answer!   
 Good Luck!   >=20 > Ferry  >=20
 > > Hi folks,  > > . > > here are the answers to G=E9rards posting: > > 9 > > > $ Mc ncl SHOW OSI TRANSPORT TEMPLATE OSIT$RFC* NAME  > > > does show  > >  > > > Identifiers  > > > Name =3D osit$rfc1006  > > 4 > > > Node 0 OSI Transport Template osit$rfc1006plus, > > > at 1997-02-20-10:54:23.502-07:00I0.909 > > >  > > > Identifiers  > > >  > > > Name =3D osit$rfc1006plus  > > > or not ? > >  > > Yes, shows the above.  > > 
 > > > Does > > > $ ucx sh dev  > > > show the ports 102 and 399 > > L > > No, doesn't (at least not as local ports). I should mention that I _can= _ L > > connect to a remote node over RFC1006 _from_ MVIE63. But I can't connec= t  > > _to_ MVIE63 this way.  > > & > > > If MVIE63 has an IP @ of 1.2.3.4 > > > What does  > > > $ telnet 1.2.3.4 102 > > > $ telnet 1.2.3.4 399 > > >  > > > show ? > > > * > > > %TELNET-I-TRYING, Trying ... 1.2.3.4: > > > %TELNET-E-CONNFAIL, Failed to connect to remote host: > > > -SYSTEM-F-REJECT, connect to network object rejected > > > or > > > * > > > %TELNET-I-TRYING, Trying ... 1.2.3.4; > > > %TELNET-I-SESSION, Session 01, host 1.2.3.4, port 102  > > > TELNET> EXIT > > ' > > Connect to network object rejected.  > >  > > > What gives > > > $ set host ip$1.2.3.4  > > A > > %SYSTEM-F-UNREACHABLE, remote node is not currently reachable  > > G > > > Check if your node is configured to allow DECnet/OSI to perform a 5 > > > BIND operation, with the following NCL command: 2 > > > NCL> SHOW SESSION CONTROL NAMING SEARCH PATH > > 1 > > Yes, it is. Contains this naming search path:  > >  > > Naming Search Path =3D > > {  > > [ ! > > Directory Service =3D Local ,  > > Template =3D "*" > > ] ,  > > [ ! > > Directory Service =3D Local ,  > > Template =3D "local:*" > > ] ,  > > [ " > > Directory Service =3D Domain , > > Template =3D "*" > > ] ,  > > [ " > > Directory Service =3D Domain ,& > > Template =3D "*.adv.magwien.gv.at" > > ] ,  > > [ " > > Directory Service =3D Domain ,' > > Template =3D "*.host.magwien.gv.at"  > > ]  > > }  > > ' > > and this backtranslation sear path:  > > # > > Backtranslation Search Path =3D  > > {  > > [ ! > > Directory Service =3D Local ,  > > Template =3D ""  > > ] ,  > > [ " > > Directory Service =3D Domain , > > Template =3D ""  > > ]  > > }  > > L > > As mentioned in my first posting, i have a _similar_ configuration on m= any 1 > > other systems where it runs without problems.  > >  > > Any ideas? > >  > > MTIA and kind greetings, > > 	 > > Ferry  > > --- ! > > Ing. Ferry Bolhar-Nordenkampf ) > > Municipality of Vienna, Department 14  > > A-1010 Vienna / AUSTRIA ! > > E-mail: bol@adv.magwien.gv.at > > > "Wenn hier einer schuld ist, dann immer nur der Computer." > >  > >  > >  > >  >=20 >=20 >=20 >=20   --=20  John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------    Date: 14 Jan 2003 11:55:27 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: Re: DECnet Problem 3 Message-ID: <2w6dxhFX1yiz@eisner.encompasserve.org>   f In article <1042531475.49162@mozart.adv.magwien.gv.at>, "Ferry Bolhar" <bol@adv.magwien.gv.at> writes: > Hi folks,  > J > our news server was down the last days - so I just wanted to ask whetherD > there are new postings to my question concerning the problems with
 > DECnet-Plus    http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&frame=right&th=12849d2c07fde654&seekm=3C5FEDA3.A9FB6E3B%40contrastmediagroep.nl#link19    ------------------------------  % Date: Tue, 14 Jan 2003 10:05:08 +0100 2 From: "Ren Schelbaum" <rene.schelbaum@datakom.at> Subject: Re: Freeware VDD64 G Message-ID: <3e23d2a2$0$20518$91cee783@newsreader01.highway.telekom.at>   6 "Hoff Hoffman" <hoff@hp.nospam> schrieb im Newsbeitrag$ news:avvo0n$nob$2@web1.cup.hp.com... > > > In article <3E1EDEC2.8000109@maury-imprimeur.fr>, Tim Oakley$ <toakley@maury-imprimeur.fr> writes: > H > :Have just updated to v7.3 and our optical disks which used to use theK > :PERCPETICS supplied 'WDD' drivers (OSMS i think) no longer work (in fact 4 > :the system crashes when we load the WDD drivers). > :  > :HP France told me that...	 > :either K > :purchase new drivers from a company named USDESIGN who tookover the OSMS K > :software from Compaq (this seems fair, but USDESIGN tell me that the new F > :drivers will allow me to read data from my optical drives but *not*7 > :write to them (sounds like a Microsoft enhancement))  > L >   This compatability model is fairly common in the storage hardware space.I >   The ability to read the media from older drives permits you to access K >   older archives, while the removal of the write-related hardware and the J >   associated logic for the older widget simplifies (and reduces the costK >   and the risks to) the write-path of the device.  Various generations of I >   DLT tape drives have had similar upward read media compatability, for I >   instance, and the new Iomega Zip750 drives (are both read- and write- K >   compatible with the previous-generation Zip250 drives and) can read but , >   cannot write to the oldest Zip100 media. >  > :or K > :try using the freeware VDD64 package which should allow me to access the $ > :optical disks as i did with OSMS. > : K > :Having downloaded the VDD package and read the help/user doc i don't see  > :how VDD is going to help me.  > : J > :Has anyone used the freeware 'VDD64' (virtual device drivers) for theirH > :optical drives or has anyone got a different solution to my problem ? >  >  > I >   AFAIK, HP France is either confused, or some amount of information in E >   the discussion was lost in the transition and/or the translation.  > I >   As you expect, VD64 and LD implement virtual disks, and these are not H >   particularly useful for accessing foreign devices.  These mechanismsG >   are usful for creating the master data copies that are then used as E >   the source for block-oriented write operations to recordable disk K >   media, particularly to CD disks -- this may have been either the source B >   of the confusion, or potentially the intent of the suggestion. > I >   If you can write to the RWZ-series devices using a block-oriented I/O K >   sequential write mode (implemented with, for instance, a series of $qio K >   or $qiow IO$_WRITELBLK calls), this suggestion from HP France does make H >   good sense and will (probably) work.  (I'm not familiar with the RWZF >   series device control interface, nor with the WDD device drivers.) > K >   Current media for this task would be DVD-R, DVD+R, DVD-RW, DVD+RW, etc.  > G >   I have passed a reference to to the comments on the contents of the F >   OpenVMS SPD (located elsewhere in the thread) along to the OpenVMS >   Business Manager.  > ( >  ---------------------------- #include' <rtfaq.h> ----------------------------- L >       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com, >  --------------------------- pure personal# opinion --------------------------- G >         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com  >     Hello !  L ... agreed, but I didn't have to buy a new license to be able to read a TK50 Tape on a TK70 drive!    Ren   ------------------------------  % Date: Tue, 14 Jan 2003 10:18:07 -0500 * From: "Stanley F. Quayle" <stan@stanq.com> Subject: Re: GE HCT Tool Kit. Message-ID: <3E23E3DF.15346.A48EF8C@localhost>  + On 14 Jan 2003 at 1:41, Hoff Hoffman wrote: % > :However, the toolkit ends up doing 0 > :4000 buffered I/O/second at one site and 6000$ > :buffered I/O/second at the other.  E >   This does imply the software has either lost its place; that the  H >   host software has effectively become unsynchronized with the current4 >   PLC communications and with the PLC data stream.  E It's a "huh? what?" loop.  Both sides keep responding to the other's  C unsynchronized stuff.  The only way out (usually) is to reset both   sides at the same time.   I >   [,,,] at least the older PLCs have traditionally had some of the most E >   bizarre serial communications interfaces I can recall having ever G >   seen -- schemes based on single-character I/O and home-grown serial  >   protocols are not unusual.  D When you're controlling things at 9600 baud or below, one character  can take a lifetime.  F >   I do hope and do expect that the newer PLCs and newer PLC software >   has improved.   @ Yes.  I just completed an interface API for a client to control B Rockwell ControlLogix PLC's using "EtherNet/IP".  It's all TCP/IP  based.  D It's industry standard, based on an earlier "ControlNet" standard.  F Unfortunately, the documentation is written for a PLC manufacturer to C get his machine in compliance -- they expect that most people will   use NT client software.   = My client's committed to VMS.  I had to reverse-engineer the  ! standard, but I was glad to help.   8 >  (Factories tend to invest in a pile of similar PLCs, J >   and will then keep the PLCs in operation for as long as the particularG >   operation the PLCs are controlling is itself running -- and worse,  H >   short of a direct lightning hit, some of the oldest and the worst of >   the PLCs just don't die.  F Yep.  I have clients using I/O hardware that predates PLC's -- it was @ directly-connected to serial cards on PDP-11's.  We developed a > special-purpose box with an Ethernet interface so it could be D controlled by VMS.  Now I have a request for proposal to control it D from Linux or Windows.  My recommendation is Linux -- 10 years from C now, no one will be able to develop software for Windows 2000, but    Linux will still be available...  J >   If I were in your situation, I would check with the GE Fanuc folks andH >   see if this is a known problem.  [...]  I do not know if GE Fanuc is8 >   presently supporting this PLC or this HCT, as well.)  / It would seem unlikely, but it's worth a try...   
 --Stan Quayle  Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  % Date: Tue, 14 Jan 2003 07:36:19 -0500 2 From: rdeininger@mindspring.com (Robert Deininger)  Subject: Re: Help with VAX BasicL Message-ID: <rdeininger-1401030736190001@user-2ive235.dialup.mindspring.com>  < In article <01C2BB0E.2E1C5460@sulfer.icius.com>, Shane Smith <ssmith@icius.com> wrote:   I >Believe me, there's a lot more than one BASIC app put there. What you're H >experiencing isn't a BASIC issue, it's how DCL works. When your commandF >file runs, it's accepting input from its command stream, SYS$COMMAND,G >which is taking input from the command file itself. You need to divert & >that to take input from the keyboard: > * >$ DEFINE/NOLOG/USER SYS$COMMAND SYS$INPUT >$ RUN whatever_you_want_to_run  >  ...   F >Incidentally, if anyone can explain to me why the qualifier is /USER,G >I'd love to know. DCL commands and qualifiers are usually descriptive,  >and this doesn't seem to be.   F The name is /USER_MODE, and it comes from the 4 protection modes builtC into the VAX hardware and used throughout VMS.  The modes are USER, J SUPERVISOR, EXECUTIVE, and KERNEL.  Logical names can be created in all of9 these modes (kernel-mode names can't be created via DCL).   G See the logical name documentation in the OpenVMS User's Guide for more 5 info on the meaning of the modes for logical names.     G User mode is least privileged.  User mode tends to be associated with a G single executable image.  So we have user-mode exit handlers, user-mode F ASTs, user-mode logical names, and so on.  When a image runs down, theA user-mode stuff, including logical names, gets deleted.  The nextO+ executable image starts with a clean slate.   E DCL itself mostly inhabits Supervisor mode.  It doesn't trust much ofeI anything defined in user mode, so it is protected against bad behavior inw a user's program.v  P RMS lives in Executive mode, along with various other less-visible parts of VMS.  = The core of the OS lives in Kernel mode, the most privileged.r  G The boundaries between the inner modes are somewhat ill-defined, and ittD isn't always easy to predict what mode a certain operation requires.  J The 4 modes are enforced by hardware on VAX, by PALcode on Alpha, and will$ be mostly in OS software on Itanium.   ------------------------------    Date: 14 Jan 2003 05:49:23 -08002 From: vibroplex@mindspring.com (Derek Cohn/WB0TUA)  Subject: Re: Help with VAX Basic= Message-ID: <d7d0c297.0301140549.22d21c60@posting.google.com>A  / Good morning Jan-Erik and Shane (and the rest),I  A Thank you very, very much for the information you posted here.  Ir< implemented your recommended change in the DCL and it worked2 perfectly.  My program is now running as intended.  C Also, thanks for letting me know I'm not the only soul working with E VAX BASIC these days.  It was getting to be a little lonely here. :-)r  C This is my 10th year using VMS and I just love it.  What a fabulous  operating system!   2 I am very grateful for your invaluable assistance!   Derek    ------------------------------    Date: 14 Jan 2003 08:31:29 -0600 From: briggs@encompasserve.org  Subject: RE: Help with VAX Basic3 Message-ID: <XHkqJuQXaq3o@eisner.encompasserve.org>s  W In article <01C2BB0E.2E1C5460@sulfer.icius.com>, Shane Smith <ssmith@icius.com> writes:iG > Incidentally, if anyone can explain to me why the qualifier is /USER,mH > I'd love to know. DCL commands and qualifiers are usually descriptive, > and this doesn't seem to be.  A As has been explained elsewhere, the /USER is an abbreviation for B the full qualifier:  /USER_MODE.  And this, in turn means that the1 logical name in question is defined in user mode.g  = This has several effects, some useful and some not so useful.a  E 1.  The logical name is automatically deassigned at image exit.  ThisrE is the effect that is usually desired.  So you can assign the logical D name, use it in one image and not worry about cleaning up afterward.  @     Note that because the name is only deassigned at image exit,E it will not be automatically deassigned after the next DCL command ino= the command file, but only after the next DCL command that is @ implemented by performing an image activation.  I recall one bugG in SYS$SYSTEM:STARTUP.COM that resulted from a DEC engineer overlookingn= this small detail.  A user mode assignment there outlived itso> usefulness in some circumstances.  Command procedure exit alsoD counts as image rundown and triggers user mode logical deassignment.  E     Technically, it's only user mode logical names in certain logicalm@ name tables that are automatically deassigned at image exit.  IfC you $ DEFINE /JOB /USER, the resulting name will persist even after2I image exit.  If I recall correctly, LNM$PROCESS and LNM$PROCESS_DIRECTORY > are the two tables within which user mode names are deassigned at image exit.  D 2.  If the logical name is SYS$INPUT, SYS$OUTPUT or SYS$ERROR, it is5 not automatically opened as a process permanent file.o  A     This piece of arcana is of limited usefulness.  But it means, @ for instance, that if you define SYS$INPUT in user mode and thenB try to $ READ SYS$INPUT foo you'll get an error message about fileB not open.  Its most visible impact is on file versioning when usedA on SYS$OUTPUT.  With a supervisor mode assignment, you get shared1B access to one PPF, no matter how many times your application opensC SYS$OUTPUT.  With a user mode assignment, each time the applications6 opens SYS$OUTPUT it is likely to create a new version.  A 3.  The user mode assignment does not affect competing inner modes assignments.  H     So if you have SYS$INPUT defined in supervisor mode pointing to some> data file (and, perhaps, opened as a PPF with a stream context@ pointing to some record in the middle of that data file) you canD define SYS$INPUT in user mode, activate an image, run down the imageF and the original SYS$INPUT will still be intact.  And the PPF context, if any, will be intact as well.0  C 4.  Note that if you spawn a subprocess and propagate logical namesuA into the subprocess, the user mode assignment will be copied into./ the subprocess as a supervisor mode assignment.a   	John Briggs   ------------------------------    Date: 14 Jan 2003 11:43:24 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen).S Subject: Re: How much disk I/O can I do with a sys$QIOW IO$_WRITEVBLK/IO$_READVBLK? 3 Message-ID: <5On1NA3vKOek@eisner.encompasserve.org>w  W In article <3E23934A.5090902@tsoft-inc.com>, David Froble <davef@tsoft-inc.com> writes:  > RC Bryan wrote:  > G >> We have an existing application that uses QIOW to write data to diskp >> as follows: >> t >>    vmsCondCode = sys$qiow ( s5 >>                     0,                   // no EFNC@ >>                     nChannel,            // Channel to deviceB >>                     IO$_WRITEVBLK,       // write function code? >>                     Iosb,                // I/O status blockaH >>                     0,                   // no AST completion routine@ >>                     0,                   // no AST parameters? >>                     bufferAddr,          // P1 user's bufferrB >>                     length,              // P2 length of bufferA >>                     StartPage,           // P3 = Record number-7 >>                     0,0,0);              // No P4-P6i >  > P > I think the 'length' is an unsigned 16 bit integer, thus 65535 bytes.  I know L > that when writing disk blocks, the limit is 127 blocks to a write or read.  @ 	That should be true only for really old (i.e., pre-SCSI) disks.  # 	Looking at the V7.3 documentation:i  < 	file:///VMSDOC073/v73/6136/6136pro_008.html#disk_func_codes  A > "Non-DSA disk devices can read or write up to 65,535 bytes in ahA >  single request. DSA devices connected to an HSC50 can transfert? >  up to 4 billion bytes in a single request. In all cases, thetA >  maximum size of the transfer is limited by the number of pages ? >  that can be faulted into the process's working set, and thene? >  locked into physical memory. (The disk driver is responsiblehA >  for any memory management functions of this type.) The size of-A >  the transfer does not affect the applicable quotas (direct I/O@@ >  count, buffered I/O count, and asynchronous system trap (AST)@ >  count limit). These quotas refer to the number of outstandingA >  I/O operations of each type, not the size of the I/O operationl >  being performed."   ------------------------------    Date: 14 Jan 2003 10:16:25 -0800$ From: rcbryan@hotmail.com (RC Bryan)S Subject: Re: How much disk I/O can I do with a sys$QIOW IO$_WRITEVBLK/IO$_READVBLK?:= Message-ID: <fbcf38dc.0301141016.5b43bd6a@posting.google.com>i  \ David Froble <davef@tsoft-inc.com> wrote in message news:<3E23934A.5090902@tsoft-inc.com>... >nP > I think the 'length' is an unsigned 16 bit integer, thus 65535 bytes.  I know L > that when writing disk blocks, the limit is 127 blocks to a write or read.  _ Stuart Fuller <stufuller@usa.net> wrote in message news:<ur100b.i6f.ln@dadsys2.fuller.local>...  > N > The I/O User's Guide documents the max I/O sizes for a variety of devices.  * > See section 2: the disk drivers section.     Thanks guys.  ; In the I/O User's Guide in section 2.4: Disk Function CodesF
 (available atnQ http://www.openvms.compaq.com/doc/731FINAL/6136/6136pro_008.html#disk_func_codes)"D they say: "Non-DSA disk devices can read or write up to 65,535 bytesF in a single request. DSA devices connected to an HSC50 can transfer upD to 4 billion bytes in a single request."  While I am not sure what aF DSA disk is I feel confident that if I limit transfers to 65K, it will> work on any customer's machines.  It kind of galls me to limit@ performance like that but the last thing I need is problems on a@ customer system (with old disks) that I can't reproduce (with my new(er) disks).e  6 Do you supposed all Alphas can do the 4 gig transfers?  
 Thanks again..	 /RC Bryanr   ------------------------------  + Date: Tue, 14 Jan 2003 18:25:39 +0000 (UTC)g3 From: "Richard Maher" <maher_rj@hotspamnotmail.com>iS Subject: Re: How much disk I/O can I do with a sys$QIOW IO$_WRITEVBLK/IO$_READVBLK?e0 Message-ID: <b01kn2$cav$1@sparta.btinternet.com>   Hi,a  K Does Fast I/O (and whatever device restrictions go with it) interest you aty. all? "buflen" says it can be the full 64-bits.  I Although the documentation says Alpha only, somewhere I saw that, on VAX,,G the single $io call was translated automagically into multiple $qios. It don't know if it's true.  * I'll post an example if you're interested.   Regards Richard Maher.  / RC Bryan <rcbryan@hotmail.com> wrote in messages6 news:fbcf38dc.0301131705.b838357@posting.google.com...F > We have an existing application that uses QIOW to write data to disk
 > as follows:d >e >    vmsCondCode = sys$qiowo  4 >                     0,                   // no EFN? >                     nChannel,            // Channel to deviceoA >                     IO$_WRITEVBLK,       // write function codet> >                     Iosb,                // I/O status blockG >                     0,                   // no AST completion routinem? >                     0,                   // no AST parameterse> >                     bufferAddr,          // P1 user's bufferA >                     length,              // P2 length of buffer/@ >                     StartPage,           // P3 = Record number6 >                     0,0,0);              // No P4-P6 >MG > I cannot find a hard number anywhere that says what the max value can1D > be for length.  The program originally limited the I/O to size 32K9 > chunks but I discovered that I can write bigger pieces.5 >i+ > Is a limit of 64K reasonable for V7.1 on?+% > Can I go with a much greater limit? 8 > Is this documented anywhere that I have not found yet?E > Am I going to discover that my new SCSI disks can run fine with bigL4 > blocks but some old disk is going to have trouble? >  > Thanks in advance, > /RC Bryany   ------------------------------  % Date: Tue, 14 Jan 2003 09:47:25 -0500v From: norm.raphael@metso.com2 Subject: HP Sets the Stage for Alpha's Last Hurrah? Message-ID: <OF3A3EC4F4.B27764E2-ON85256CAE.0050704D@metso.com>   W http://www.computerworld.com/hardwaretopics/hardware/server/story/0,10801,77476,00.htmla      ) HP Sets the Stage for Alpha's Last Hurrah-   By JAIKUMAR VIJAYAN         JANUARY 13, 2003M    J Hewlett-Packard Co. is gearing up for the Jan. 21 launch of a long-awaitedK line of AlphaServers that promises to deliver substantial price/performancem gains over existing technology.I    H But HP's previously announced plans to eventually standardize all of itsI servers on Intel Itanium processors may temper some of the enthusiasm theh; announcement would otherwise have generated, analysts said.c    F HP gained the Alpha technology through its purchase of Compaq ComputerF Corp. last year. AlphaServers run the OpenVMS and Tru64 Unix operatingJ systems and were scheduled to be phased out of production even before HP'sI merger with Compaq. The company's AlphaServer business is deep in the red-B and is expected to lose about $200 million this fiscal year alone.     [Is that true?]u    E HP's Marvel family of AlphaServers is based on the company's recentlyUH released EV7 processors, with models ranging from a two-CPU departmentalF server to a 64-processor enterprise server. HP last week confirmed theJ planned Marvel announcement but declined to provide details on the systemsG or migration strategy in advance. However, much of that information haseG been freely available to the Alpha faithful, most recently from HP, andU from Compaq before that.    E Apart from the faster EV7 processors, the new Marvel departmental andaC enterprise servers will feature a technology called switchless mesh-I architecture that allows users to add processors, memory and I/O capacitylF "almost like Lego blocks," according to information posted on HP's Web site.d    D The servers will support multipath I/O technology for greater systemI availability and dynamic partitioning capabilities. The servers also comeh= with a new system management console designed for centralized  administration.T    H HP's Marvel plan says a lot about the company's intent to stick with itsF postmerger product commitments, said Fernando Yson, systems manager atH Unicare/Cost Care. The Huntington Beach, Calif.-based health insurer hasE several small to midsize AlphaServers running homegrown applications.f    E When the time comes for an upgrade, it will most likely be to ItaniumsJ instead of Alpha because of HP's road map, Yson said. "But we are going to8 wait for other users to test it first before migrating."    I The Pittsburgh Supercomputing Center, which has beta-tested the EV7-basedtI servers, has ordered a "fair amount" of the systems, said Michael Levine,n6 scientific director at the federally supported center.    F The new servers will supplement the organization's existing 3,000-nodeI AlphaServer cluster, the largest nondefense supercomputer in the country,bE according to Levine. The servers' very high bandwidth performance andnD interconnect technologies are what make them appealing, Levine said.    F HP's decision to switch its server technology to Itanium in the futureK "doesn't make things any easier," said Levine. "But it is the sort of thingd; people are used to and should in most cases be manageable."n    H The new capabilities make for "faster, better, cheaper systems with muchC higher performance and much lower latency" than previous-generation-F Wildfire AlphaServers, said Terry Shannon, publisher of "Shannon KnowsJ HPC," an Albuquerque, N.M.-based newsletter. The new servers should appealH to many larger users that would need years to migrate off Alpha, Shannon said.-    + Still, the migration issue is a thorny one.-    J "Last year, I would have said that this was some really great and excitingJ technology," said Rich Partridge, an analyst at D.H. Brown Associates Inc.J in Port Chester, N.Y. But with Marvel likely to be the Alpha family's lastD hurrah, users must get commitments from HP that guarantee investment9 protection when they move to Itanium processors, he said.      [What about EV79?]    C HP has said it will support the Alpha installed base for as long as$G necessary. Its AlphaServer customer assurance program offers money-back I guarantees, technology-refresh incentives, guaranteed trade-in values and7F transition lease programs for systems purchased through December 2003.   ------------------------------    Date: 14 Jan 2003 09:23:57 -0600+ From: young_r@encompasserve.org (Rob Young)t6 Subject: Re: HP Sets the Stage for Alpha's Last Hurrah3 Message-ID: <2jhv5O8PYazj@eisner.encompasserve.org>   ^ In article <OF3A3EC4F4.B27764E2-ON85256CAE.0050704D@metso.com>, norm.raphael@metso.com writes: >  > - > Still, the migration issue is a thorny one.d >   < 	You read that and come away disappointed.  It is true that C 	Alpha and Itanium won't be binary compatable.  But they will shareeC 	code.  The hope is compiler issues are not substantial.  But won't @ 	there be a great deal of compiler synergy in that you will haveD 	a common back-end?  Intel wants Itanium to succeed and are spending 	money, this too is good.-   > L > "Last year, I would have said that this was some really great and excitingL > technology," said Rich Partridge, an analyst at D.H. Brown Associates Inc.L > in Port Chester, N.Y. But with Marvel likely to be the Alpha family's lastF > hurrah, users must get commitments from HP that guarantee investment; > protection when they move to Itanium processors, he said.  >   B 	That is funny isn't it?  With the average shelf life of a WindowsA 	server in the neighborhood of 3-4 years, what does he expect?  8TG 	years of longevity?  If after 4 years, you are ready to upgrade anyhownH 	(many of us are, run out of horsepower, servers have depreciated, etc.)B 	You will be ready to limp along another year or two in 4 years as 	you introduce Itaniums.  , 	Secondly, how fast is anyone going to move?A 	Won't it be a gradual introduction?  Of course it will, and moste= 	likely over the next 4-6 years, a lifetime in this industry.   > 	What is investment protection?  Is there a legitimate fear orA 	concern?  If so, how is it manifested?  I see it as analyst FUD.l; 	Counter-vailing opinions welcome.  I am interested in whatA 	investment protection is.   >  > [What about EV79?] >   , 	What about it?  Still on roadmaps isn't it?  ? 	Look, at least it is shipping.  Go back and read some opinionstE 	a year or two ago.  Several thought it wouldn't ship.  What a crock.r   > E > HP has said it will support the Alpha installed base for as long asoI > necessary. Its AlphaServer customer assurance program offers money-backcK > guarantees, technology-refresh incentives, guaranteed trade-in values andsH > transition lease programs for systems purchased through December 2003. >   E 	Just like they are supporting VAXes.  HP will reap a bit of a bittertE 	harvest with MPE/ix, no migration path.  The VAX base is still big, dG 	to drop VAX/VMS support would not be a good thing.  When did the last y/ 	VAX get ordered?  If I recall, September 1999.    					Rob   ------------------------------  # Date: Tue, 14 Jan 2003 16:17:55 GMTd# From: "John Smith" <a@nonymous.com>e6 Subject: Re: HP Sets the Stage for Alpha's Last HurrahK Message-ID: <TKWU9.337705$F2h1.155964@news01.bloor.is.net.cable.rogers.com>r  ) <norm.raphael@metso.com> wrote in message-9 news:OF3A3EC4F4.B27764E2-ON85256CAE.0050704D@metso.com...n >n >  >H >gF http://www.computerworld.com/hardwaretopics/hardware/server/story/0,10 801,77476,00.html  >n >e >4+ > HP Sets the Stage for Alpha's Last Hurrah  >= > By JAIKUMAR VIJAYANa >        JANUARY 13, 2003  >t >n? > Hewlett-Packard Co. is gearing up for the Jan. 21 launch of ar long-awaited; > line of AlphaServers that promises to deliver substantial  price/performanceG! > gains over existing technology.d >o >yF > But HP's previously announced plans to eventually standardize all of itsh< > servers on Intel Itanium processors may temper some of the enthusiasm the= > announcement would otherwise have generated, analysts said.  >b >s? > HP gained the Alpha technology through its purchase of Compaq( Computer> > Corp. last year. AlphaServers run the OpenVMS and Tru64 Unix	 operatingo@ > systems and were scheduled to be phased out of production even before HP'sTC > merger with Compaq. The company's AlphaServer business is deep ind the redVD > and is expected to lose about $200 million this fiscal year alone. >  >n > [Is that true?]O    C If it's true, then the principal reasons for it are numerous and go%A back from the present day to about 5 years ago (as a rough date):   D 1) The delays introduced by Compaq management in getting EV7 out the9 door due to their waffling committment to the technology.   = 2) The announcement that Alpha was dead - which only hastenedIC migration plans from VMS by many organizations, and killed purchase  plans by other organizations.u  D 3) Profound lack of marketing by both Comapq and HP of Alpha systems& in general, and OpenVMS in particular.  F 4) A huge doubt overhanging the market as to the viability of IA-64 as+ an ultimate migration path for Alpha users.a  C 5) HP's desire to pad the Alpha divisions books with every possibleb@ expense in order to make it look bad and provide 'rationale' for' continued de-emphasis of VMS and Alpha.   B 6) General downturn in the IT marketplace over the past 18 months.   ------------------------------  % Date: Tue, 14 Jan 2003 13:26:20 -0500m* From: "Bill Todd" <billtodd@metrocast.net>6 Subject: Re: HP Sets the Stage for Alpha's Last Hurrah2 Message-ID: <A86cnauXEu3By7mjXTWcqg@metrocast.net>  8 "Rob Young" <young_r@encompasserve.org> wrote in message- news:2jhv5O8PYazj@eisner.encompasserve.org...n   ...l    > Look, at least it is shipping.  + Always one to look on the bright side, Rob.2      Go back and read some opinions > a year or two ago.  L You should go back and do so yourself, since you clearly don't remember them
 correctly.  3 >  Several thought it wouldn't ship.  What a crock.i  K Wrong, Rob:  several people thought *that there was a non-negligible chancepJ that EV7 wouldn't ship*, and the recent Inquirer article purports to quoteE an internal cHumPaq source as saying that indeed EV7 would *not* havewH shipped save for some government commitments with teeth in them.  Now, IE don't presume to vouch for that source, but the manner in which HP isRK handling the debut (for a laugh, contrast it with the nominal Itanic2 debut = and accompanying fanfare last July, especially in the area ofTL benchmarketing) certainly suggests that they would have cancelled it if they) felt they could have gotten away with it.D   - bill   ------------------------------   Date: 14 Jan 2003 09:35:32 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren), Subject: Re: Marvel talks at The Inquirer...0 Message-ID: <b00ll4$llk$1@pegasus.csx.cam.ac.uk>  H In article <RmiS9.180572$yW.40570@news04.bloor.is.net.cable.rogers.com>,% "John Smith" <a@nonymous.com> writes:s |>   |> > SPARC is from 1989 !  |> >@ |> > Ofcourse there were Motorola based workstations before, but@ |> > I think it was first with SPARC that price/performance went |> > real bad for DEC. |>  I |> Sun, in their first generation gear, which was available before SPARC,-F |> was a price/performance leader if you overlooked the fact that unix5 |> wasn't worth a pitcher of warm spit in those days.O  A The reason that Sun and Apollo established themselves was because A they were the first two vendors to deliver Unix workstations with @ half-working software (including compilers).  By the late 1980s,E there were several such vendors (almost all using Motorola 68K chips)g" and the quality wasn't bad at all.  > The first Sun 3 (SPARC) systems were slower than the ones theyB replaced on many or most workloads, and it wasn't until the second< production that they started to pull ahead.  As you say, the@ MicroVAX was no longer a price/performance leader by the time of
 the 68020.  B As servers, the software was usually pretty dire but, for example,A HP-UX 7 was good enough to use for that purpose.  I wouldn't have,= wanted to use any Sun system of that era for a server, though  dozens of academic sites did."  = As people point out, DEC's mistake was in failing to turn the ' MicroVAX lead into a dominant position.n     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 334679    ------------------------------  % Date: Tue, 14 Jan 2003 12:06:06 +0000 ' From: Andrew Harrison SUNUK Consultancy , Subject: Re: Marvel talks at The Inquirer.... Message-ID: <3E23FD2E.9070302@nospamn.sun.com>   Nick Maclaren wrote:J > In article <RmiS9.180572$yW.40570@news04.bloor.is.net.cable.rogers.com>,' > "John Smith" <a@nonymous.com> writes:o > |> a > |> > SPARC is from 1989 !V > |> >B > |> > Ofcourse there were Motorola based workstations before, butB > |> > I think it was first with SPARC that price/performance went > |> > real bad for DEC. > |> oK > |> Sun, in their first generation gear, which was available before SPARC,-H > |> was a price/performance leader if you overlooked the fact that unix7 > |> wasn't worth a pitcher of warm spit in those days.  > C > The reason that Sun and Apollo established themselves was because2C > they were the first two vendors to deliver Unix workstations witheB > half-working software (including compilers).  By the late 1980s,G > there were several such vendors (almost all using Motorola 68K chips)y$ > and the quality wasn't bad at all. > @ > The first Sun 3 (SPARC) systems were slower than the ones theyD > replaced on many or most workloads, and it wasn't until the second> > production that they started to pull ahead.  As you say, theB > MicroVAX was no longer a price/performance leader by the time of > the 68020. >   9 The Sun 3 range were 68010/68020 and 68030 based systems.e- The Sun 4 range were the SPARC based systems.   5 The Sun 3 and Sun 4 range overlapped with 68030 basedv1 systems coming out at the same time as the secondE( generation of Sun 4 SPARC based systems.  1 The SPARCstation 1 used the same packaging as the  68030 based 3/80  D > As servers, the software was usually pretty dire but, for example,C > HP-UX 7 was good enough to use for that purpose.  I wouldn't haver? > wanted to use any Sun system of that era for a server, thought > dozens of academic sites did.e >   : At the time Sun's servers 3/280 and 4/280 were simply rack; mounted versions of the deskside workstations the 3/260 andt' 4/260. Same VME cards larger card cage.   : You could use larger SMD and IPI drives in the 19inch cabs8 but that appart from having more VME slots was about it.  ;  From an OS standpoint at the time SunOS lacked things like < a logical volume manager, log based filesystems etc reducing8 its efficacy as a server OS. LVMs came in later releases: of SunOS and there was no HA clustering software for SunOS5 until I wrote it but that was for the SPARCserver 600n which was introduced in 1991.o    ? > As people point out, DEC's mistake was in failing to turn thes) > MicroVAX lead into a dominant position.  >  > 
 > Regards, > Nick Maclaren,, > University of Cambridge Computing Service,@ > New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. > Email:  nmm1@cam.ac.uk1 > Tel.:  +44 1223 334761    Fax:  +44 1223 334679t   ------------------------------   Date: 14 Jan 2003 16:42:54 GMT( From: bill@cs.uofs.edu (Bill Gunshannon), Subject: Re: Marvel talks at The Inquirer...5 Message-ID: <b01emd$kiaud$1@ID-135708.news.dfncis.de>l  0 In article <b00ll4$llk$1@pegasus.csx.cam.ac.uk>,+ 	nmm1@cus.cam.ac.uk (Nick Maclaren) writes:c > D > As servers, the software was usually pretty dire but, for example,C > HP-UX 7 was good enough to use for that purpose.  I wouldn't havea? > wanted to use any Sun system of that era for a server, thoughe > dozens of academic sites did.p  C I had HP-UX, Sun3's and Sparcs all runing simultaneously here and IcA can assure you my experience was quite different than yours.  The B worst performer was the HP and I was glad to finally dump it.  TheD Suns lasted a while longer and, surprisingly, the only ones still inC regular use are the Sun3's.  Two servers and 3 workstations runningtG strictly as X-terminals for those servers.  The engineering applicationtG they run was never ported anywhere else, and other than maintenance thei: Sun3's are more than adequate for this single application.   > ? > As people point out, DEC's mistake was in failing to turn theu) > MicroVAX lead into a dominant position.d  " This I can definitely agree with.    bill   -- iJ 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: Tue, 14 Jan 2003 13:29:55 -0500 ! From: Jim Agnew <jpagnew@vcu.edu>-$ Subject: Re: Microvax Floating point' Message-ID: <3E245723.BB387A54@vcu.edu>   > I only know from said experience that the CRC-32??? polynomialF instruction is done in microcode on the Microvax 3900, and in firmware% (faster) on a vaxstation 3100model38,eF making the vaxstation the faster vms backup machine...  details may be, wrong, but that's what was explained to us..   jime   JF Mezei wrote:0 >  > Theroretical question. > J > Floating point operations on Microvax machines are emulated by software, > correct ?y > K > *conceptually* and forgetting any need to be compatible with other vaxes,.N > wouldn't it be possible to just change the shareable images (it is uvmrtl orL > something like that ?) so that they would use IEEE format floating point ? > O > Are are there still hardware limitations that truly tie the microvaxen to thet > vax floating point format ?    ------------------------------  % Date: Tue, 14 Jan 2003 16:39:31 -0000 * From: "Richard Brodie" <R.Brodie@rl.ac.uk># Subject: Re: MOP with Multiple NICsB, Message-ID: <b01eg4$14ka@newton.cc.rl.ac.uk>  Q "Dan Moore" <dmoore@sosu.edu> wrote in message news:3E24354A.F14CC6D7@sosu.edu...   8  > How do you bind MOPDL to an additional ethernet card?  > If you are using the Decnet MOP rather  than LANCP: DEFINE and' SET the circuit service enabled in NCP.-  & ncp> def circuit eia-0 service enabled& ncp> set circuit eia-0 service enabled  N >We have just installed a DS25 and had to move LAT  (using LAT$DEVICE logical)K >to another ethernet card because network performance was terrible comparednQ >to the system we replaced. I think we essentially had go-carts (old lat devices) 0 >getting creamed on the freeway (by 100mbit ip).  U LAT is fairly intolerant of packet losses; it may be just a speed mismatch as you say T but it's worth checking that the ports haven't autoconfigured wrong or there is some other network problem.   ------------------------------  % Date: Tue, 14 Jan 2003 18:31:28 +0100i9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com>e# Subject: Re: MOP with Multiple NICs ' Message-ID: <3E244970.CFCD926B@aaa.com>t   Hi.tH The only speed that matters is that the closest port (hub or switch) to D the LAT device (DECserver?) is using the right speed, probably 10Mb.D the speed on the rest of the network does not matter. I'd check that9 the LAT device connection is set hard to the right speed.o  E The same for the DS25 connection, even if the DS25 have a 10/100 card-E and everything "should" just auto-negotiate correctly. I'v seen cases F where the boxes got the speed right, but one side selected half-duplexG and the other full-duplex with "interesting" results. All can very wellnG look OK for a while, but with a higher level of traffic, package losses  are getting worse.       Dan Moore wrote: >  > Greetings, > 4 > We have just installed a DS25 and had to move LAT 6 > (using LAT$DEVICE> logical) to another ethernet card6 > because network performance was terrible compared to > the system we replaced.u   ------------------------------  % Date: Tue, 14 Jan 2003 10:05:30 -0600s! From: Dan Moore <dmoore@sosu.edu>  Subject: MOP with Multiple NICs-( Message-ID: <3E24354A.F14CC6D7@sosu.edu>  & --------------51921EDAE2334E677DEBDD56* Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit   
 Greetings,  8    How do you bind MOPDL to an additional ethernet card?  O   We have just installed a DS25 and had to move LAT  (using LAT$DEVICE logical)uJ to another ethernet card because network performance was terrible comparedP to the system we replaced. I think we essentially had go-carts (old lat devices)G getting creamed on the freeway (by 100mbit ip). There may still be somemT residual issues, but for now, I need to know how to bind mopdl to the EIA0 interface= so our dec servers will boot if for some reason they go down.i   Here is our current lan config:O	 analy/sysi  " OpenVMS (TM) Alpha system analyzer    
 SDA> show lan    LAN Data Structuresk -------------------o>                  -- LAN Device Summary 14-JAN-2003 09:35:32 --  * LAN block address = 8157D640  (3 stations)% LAN block flags   = 00000004 LAN_INITe           Press RETURN for more.   SDA>   LAN Data Structurese -------------------p  >                  -- EIA Device Summary 14-JAN-2003 09:35:32 --   LSB address  = 82CC8000t" Device state = 00000003 RUN,INITED  9 UCB      UCB Addr  Fmt   Value           Client     StateS< ---      --------  ---   -----           ------  ----------- EIA0     8157D180kJ EIA2     81650D00  Eth   60-07           SCA     0017 STRTN,LEN,UNIQ,STRTDF EIA5     816FB940  Eth   60-04           LAT     0015 STRTN,UNIQ,STRTDJ EIA6     81890EC0  Eth   60-03           DECNET  0017 STRTN,LEN,UNIQ,STRTD           Press RETURN for more.   SDA>   LAN Data Structurese -------------------e  >                  -- EWA Device Summary 14-JAN-2003 09:35:32 --   LSB address  = 8C0A8000m- Device state = 00000103 RUN,INITED,RING_AVAILd  9 UCB      UCB Addr  Fmt   Value           Client     State < ---      --------  ---   -----           ------  ----------- EWA0     8157E900dJ EWA2     81651A00  Eth   60-07           SCA     0017 STRTN,LEN,UNIQ,STRTDF EWA22    816FB600  Eth   08-00           IP      0015 STRTN,UNIQ,STRTDF EWA24    817CDB40  Eth   08-06           ARP     0015 STRTN,UNIQ,STRTDJ EWA137   818A6800  Eth   60-03           DECNET  0017 STRTN,LEN,UNIQ,STRTDP EWA138   81881A00  Eth   60-01           MOPDL   009F STRTN,LEN,UNIQ,SHARE,STRTD ,SHRDEF P EWA139   81881480  Eth   90-00           LOOP    009D STRTN,UNIQ,SHARE,STRTD,SHR DEF            Press RETURN for more.   SDA>   LAN Data Structures4 -------------------8  >                  -- EWB Device Summary 14-JAN-2003 09:35:33 --   LSB address  = 8C0D2000s" Device state = 00000003 RUN,INITED  9 UCB      UCB Addr  Fmt   Value           Client     Stated< ---      --------  ---   -----           ------  ----------- EWB0     8163C880rJ EWB2     81653A40  Eth   60-07           SCA     0017 STRTN,LEN,UNIQ,STRTDF EWB6     817BD880  Eth   08-00           IP      0015 STRTN,UNIQ,STRTDF EWB8     817CE9C0  Eth   08-06           ARP     0015 STRTN,UNIQ,STRTDD EWB9     81946500  Eth   60-03           DECNET  0007 STRTN,LEN,UNIQ       --	 Dan Moore.$ Director of Administrative Computing& Southeastern Oklahoma State University" 1405 North Fourth Avenue  PMB 4230 Durant, Oklahoma   74701-0609 + Phone: (580) 745-2006   Fax: (580) 745-2007m    & --------------51921EDAE2334E677DEBDD56) Content-Type: text/html; charset=us-asciia Content-Transfer-Encoding: 7bitB  > <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html>
 Greetings,E <p>&nbsp;&nbsp; How do you bind MOPDL to an additional ethernet card?tH <p>&nbsp; We have just installed a DS25 and had to move LAT&nbsp; (using LAT$DEVICE logical) N <br>to another ethernet card because network performance was terrible comparedG <br>to the system we replaced. I think we essentially had go-carts (oldu lat devices)F <br>getting creamed on the freeway (by 100mbit ip). There may still be someI <br>residual issues, but for now, I need to know how to bind mopdl to theT EIA0 interfaceA <br>so our dec servers will boot if for some reason they go down. " <p>Here is our current lan config:
 <br>analy/sys . <p><tt>OpenVMS (TM) Alpha system analyzer</tt> <br><tt></tt>&nbsp;<tt></tt>" <p><tt>SDA> show lan</tt><tt></tt> <p><tt>LAN Data Structures</tt>i  <br><tt>-------------------</tt>h <br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;; -- LAN Device Summary 14-JAN-2003 09:35:32 --</tt><tt></tt>k; <p><tt>LAN block address = 8157D640&nbsp; (3 stations)</tt>e< <br><tt>LAN block flags&nbsp;&nbsp; = 00000004 LAN_INIT</tt> <br><tt></tt>&nbsp;m <br><tt></tt>&nbsp;<tt></tt>> <p><tt>&nbsp;&nbsp;&nbsp; Press RETURN for more.</tt><tt></tt> <p><tt>SDA></tt><tt></tt>  <p><tt>LAN Data Structures</tt>t) <br><tt>-------------------</tt><tt></tt>og <p><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;N; -- EIA Device Summary 14-JAN-2003 09:35:32 --</tt><tt></tt>i( <p><tt>LSB address&nbsp; = 82CC8000</tt>8 <br><tt>Device state = 00000003 RUN,INITED</tt><tt></tt>G <p><tt>UCB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UCB Addr&nbsp; Fmt&nbsp;&nbsp;n` Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client&nbsp;&nbsp;&nbsp;&nbsp;
 State</tt>H <br><tt>---&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------&nbsp; ---&nbsp;&nbsp;N -----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ------&nbsp; -----------</tt>2 <br><tt>EIA0&nbsp;&nbsp;&nbsp;&nbsp; 8157D180</tt> <br><tt>EIA2&nbsp;&nbsp;&nbsp;&nbsp; 81650D00&nbsp; Eth&nbsp;&nbsp; 60-07&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : SCA&nbsp;&nbsp;&nbsp;&nbsp; 0017 STRTN,LEN,UNIQ,STRTD</tt> <br><tt>EIA5&nbsp;&nbsp;&nbsp;&nbsp; 816FB940&nbsp; Eth&nbsp;&nbsp; 60-04&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;d6 LAT&nbsp;&nbsp;&nbsp;&nbsp; 0015 STRTN,UNIQ,STRTD</tt> <br><tt>EIA6&nbsp;&nbsp;&nbsp;&nbsp; 81890EC0&nbsp; Eth&nbsp;&nbsp; 60-03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;r+ DECNET&nbsp; 0017 STRTN,LEN,UNIQ,STRTD</tt>  <br><tt></tt>&nbsp;I <br><tt></tt>&nbsp;<tt></tt>> <p><tt>&nbsp;&nbsp;&nbsp; Press RETURN for more.</tt><tt></tt> <p><tt>SDA></tt><tt></tt>c <p><tt>LAN Data Structures</tt> ) <br><tt>-------------------</tt><tt></tt>ng <p><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-; -- EWA Device Summary 14-JAN-2003 09:35:32 --</tt><tt></tt>i( <p><tt>LSB address&nbsp; = 8C0A8000</tt>C <br><tt>Device state = 00000103 RUN,INITED,RING_AVAIL</tt><tt></tt>OG <p><tt>UCB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UCB Addr&nbsp; Fmt&nbsp;&nbsp;a` Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client&nbsp;&nbsp;&nbsp;&nbsp;
 State</tt>H <br><tt>---&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------&nbsp; ---&nbsp;&nbsp;N -----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ------&nbsp; -----------</tt>2 <br><tt>EWA0&nbsp;&nbsp;&nbsp;&nbsp; 8157E900</tt> <br><tt>EWA2&nbsp;&nbsp;&nbsp;&nbsp; 81651A00&nbsp; Eth&nbsp;&nbsp; 60-07&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : SCA&nbsp;&nbsp;&nbsp;&nbsp; 0017 STRTN,LEN,UNIQ,STRTD</tt> <br><tt>EWA22&nbsp;&nbsp;&nbsp; 816FB600&nbsp; Eth&nbsp;&nbsp; 08-00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;; IP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0015 STRTN,UNIQ,STRTD</tt>  <br><tt>EWA24&nbsp;&nbsp;&nbsp; 817CDB40&nbsp; Eth&nbsp;&nbsp; 08-06&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6 ARP&nbsp;&nbsp;&nbsp;&nbsp; 0015 STRTN,UNIQ,STRTD</tt>{ <br><tt>EWA137&nbsp;&nbsp; 818A6800&nbsp; Eth&nbsp;&nbsp; 60-03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2+ DECNET&nbsp; 0017 STRTN,LEN,UNIQ,STRTD</tt>b{ <br><tt>EWA138&nbsp;&nbsp; 81881A00&nbsp; Eth&nbsp;&nbsp; 60-01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;66 MOPDL&nbsp;&nbsp; 009F STRTN,LEN,UNIQ,SHARE,STRTD</tt> <br><tt>,SHRDEF</tt>{ <br><tt>EWA139&nbsp;&nbsp; 81881480&nbsp; Eth&nbsp;&nbsp; 90-00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;e; LOOP&nbsp;&nbsp;&nbsp; 009D STRTN,UNIQ,SHARE,STRTD,SHR</tt>  <br><tt>DEF</tt> <br><tt></tt>&nbsp;t <br><tt></tt>&nbsp;<tt></tt>> <p><tt>&nbsp;&nbsp;&nbsp; Press RETURN for more.</tt><tt></tt> <p><tt>SDA></tt><tt></tt>i <p><tt>LAN Data Structures</tt>t) <br><tt>-------------------</tt><tt></tt>tg <p><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;o; -- EWB Device Summary 14-JAN-2003 09:35:33 --</tt><tt></tt>o( <p><tt>LSB address&nbsp; = 8C0D2000</tt>8 <br><tt>Device state = 00000003 RUN,INITED</tt><tt></tt>G <p><tt>UCB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UCB Addr&nbsp; Fmt&nbsp;&nbsp;0` Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client&nbsp;&nbsp;&nbsp;&nbsp;
 State</tt>H <br><tt>---&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------&nbsp; ---&nbsp;&nbsp;N -----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ------&nbsp; -----------</tt>2 <br><tt>EWB0&nbsp;&nbsp;&nbsp;&nbsp; 8163C880</tt> <br><tt>EWB2&nbsp;&nbsp;&nbsp;&nbsp; 81653A40&nbsp; Eth&nbsp;&nbsp; 60-07&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t: SCA&nbsp;&nbsp;&nbsp;&nbsp; 0017 STRTN,LEN,UNIQ,STRTD</tt> <br><tt>EWB6&nbsp;&nbsp;&nbsp;&nbsp; 817BD880&nbsp; Eth&nbsp;&nbsp; 08-00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;e; IP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0015 STRTN,UNIQ,STRTD</tt>  <br><tt>EWB8&nbsp;&nbsp;&nbsp;&nbsp; 817CE9C0&nbsp; Eth&nbsp;&nbsp; 08-06&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;c6 ARP&nbsp;&nbsp;&nbsp;&nbsp; 0015 STRTN,UNIQ,STRTD</tt> <br><tt>EWB9&nbsp;&nbsp;&nbsp;&nbsp; 81946500&nbsp; Eth&nbsp;&nbsp; 60-03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; % DECNET&nbsp; 0007 STRTN,LEN,UNIQ</tt>  <br><tt></tt>&nbsp; 
 <br>&nbsp; <p>--s
 <br>Dan Moorel( <br>Director of Administrative Computing* <br>Southeastern Oklahoma State University+ <br>1405 North Fourth Avenue&nbsp; PMB 4230 + <br>Durant, Oklahoma&nbsp;&nbsp; 74701-0609 9 <br>Phone: (580) 745-2006&nbsp;&nbsp; Fax: (580) 745-2007  <br>&nbsp;</html>   ( --------------51921EDAE2334E677DEBDD56--   ------------------------------   Date: 14 Jan 2003 07:07:21 GMT- From: djweath@attglobal.net (Dave Weatherall)@7 Subject: Re: Most common OpenVMS versions in use today?I5 Message-ID: <DTiotGxQ0bj6-pn2-vnCjRSVs41Iy@localhost>g  C On Mon, 13 Jan 2003 10:26:17 UTC, otto@programmer.net (Otto) wrote:d   > Hello! > > > Could anybody please tell us which OpenVMS versions that are2 > commonly used in production environments today?  > Both VAX and Alpha?o > OpenVMS 5.x, 6.x, 7.x. >  > Thanks in advance. >  > //Otto  @ We dropped 5.5.4 as a supported environment only last year. Our F Cluster, Vax and Alpha, is at VMS 6.2 and ready to move forward to at 5 7.2 via 7.1, which should join the cluster this week.c  C 6.2 is our lowest common denominator still but not for much longer.p   -- o Cheers - Dave.   ------------------------------  % Date: Tue, 14 Jan 2003 02:41:07 -0400 0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>7 Subject: Re: Most common OpenVMS versions in use today? . Message-ID: <3E23B0F7.A0D6F18@vl.videotron.ca>   Phillip Helbig wrote:c > - > > in MY opinion. 7.3 removes functionality,  > , > Please elabourate and/or add smileys.  :-)  J Display postscipt has been removed, crippling DECwrite, as well as the CDA4 viewer's ability to display simple postscript files.   ------------------------------  + Date: Tue, 14 Jan 2003 09:34:49 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> 7 Subject: Re: Most common OpenVMS versions in use today?,; Message-ID: <01KR7Y1SJUS496VN71@sysdev.deutsche-boerse.com>e  H > Display postscipt has been removed, crippling DECwrite, as well as the; > CDA viewer's ability to display simple postscript files. e  = Right.  I suspected that that was what you were referring to.s  B IIRC, this was a decision by Adobe which VMS engineering could do  nothing about.  A I've never used DECwrite and never used the CDA viewer.  I have, wE however, produced PostScript files on VMS machines for years, either  A with my own Fortran code or via DVIPS from LaTeX.  I've found GV -C (GhostView, which has a common ancestor with GhostScript) to be an mG acceptable viewer.  No idea, though, to what extent that could replace r the lost functionality.F   ------------------------------  % Date: Tue, 14 Jan 2003 10:06:25 +0100h9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> 7 Subject: Re: Most common OpenVMS versions in use today?I' Message-ID: <3E23D311.E0914751@aaa.com>   6 I can't see that the lack of a PS viewer can be of any2 importance what so ever at *commersial* VMS sites.  1 Maybe for a few hobbyists, but I can't see why HP < should take *any* notice of what *non-paying* users think...  = For *real* use, 7.3 is the *best* VMS release this far, IMHO.i   Jan-Erik Sderholm.r     Phillip Helbig (and JF) wrote: > N > >(JF) Display postscipt has been removed, crippling DECwrite, as well as the@ > >(JF) CDA viewer's ability to display simple postscript files. > ? > Right.  I suspected that that was what you were referring to.e > C > IIRC, this was a decision by Adobe which VMS engineering could doo > nothing about.   ------------------------------  + Date: Tue, 14 Jan 2003 10:20:54 +0100 (MET)l9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>s7 Subject: Re: Most common OpenVMS versions in use today?r; Message-ID: <01KR7ZPQFN6I96VN71@sysdev.deutsche-boerse.com>   8 > I can't see that the lack of a PS viewer can be of any4 > importance what so ever at *commersial* VMS sites.  I Are there no commercial sites using DECwrite and needing full PostScript   support?   ------------------------------    Date: 14 Jan 2003 14:26:22 +0100( From: Andreas Davour <ante@update.uu.se>7 Subject: Re: Most common OpenVMS versions in use today?V0 Message-ID: <cs9smvv50ch.fsf@Tempo.Update.UU.SE>  ( Jan-Erik Sderholm <aaa@aaa.com> writes:  8 > I can't see that the lack of a PS viewer can be of any4 > importance what so ever at *commersial* VMS sites. > 3 > Maybe for a few hobbyists, but I can't see why HP > > should take *any* notice of what *non-paying* users think...  8 Ever heard of generating good will? It's worth more than many suits think.r  3 But I won't argue that VMS 7.3 is the best version,g( I haven't used any else so I don't know.   /Andreas   ------------------------------  % Date: Tue, 14 Jan 2003 15:47:56 +0100p$ From: "Peter Flunger" <p-i-b@gmx.at>7 Subject: Re: Most common OpenVMS versions in use today?e0 Message-ID: <b017ut$1pi$1@newsreader1.netway.at>  " "Otto" <otto@programmer.net> wrote >w> > Could anybody please tell us which OpenVMS versions that are1 > commonly used in production environments today?u > Both VAX and Alpha?o > OpenVMS 5.x, 6.x, 7.x.   No more (production VAXen) several sites runninga7 about 25 clusters with a total of 100 Alphas with 7.2-1a one site with 7.1-2-@ one site with 7.3-1 ( 5 clusters = 18 nodes + a few standalone ) a few sites with 7.2-2 one system left with 6.2-1H3  . and of course hundreds of test systems running all Versions staring with 7.1n  8 Hope to migrate all or most systems to 7.3-1 in the near future.e  0 The first versions of 7.1 were - in my opinion -7 quite unstable, took a while to get and install all then ECOs, but was OK in the end.  
 7.3-1 rocks !i  
 long live VMSs   Peteri   ------------------------------    Date: 14 Jan 2003 11:48:00 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)t7 Subject: Re: Most common OpenVMS versions in use today?e3 Message-ID: <BLbvcaL$jHHB@eisner.encompasserve.org>s  w In article <01KR7Y1SJUS496VN71@sysdev.deutsche-boerse.com>, Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> writes:aI >> Display postscipt has been removed, crippling DECwrite, as well as theq< >> CDA viewer's ability to display simple postscript files.  > ? > Right.  I suspected that that was what you were referring to.   : It also prevents used of the DEC Document graphics editor.  D > IIRC, this was a decision by Adobe which VMS engineering could do  > nothing about.  H They could have licensed a competing implementation, and were informally3 offered one.  Integration would have taken a while.'   ------------------------------    Date: 14 Jan 2003 11:48:49 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)o7 Subject: Re: Most common OpenVMS versions in use today?i3 Message-ID: <I8mmQCglebJU@eisner.encompasserve.org>g  c In article <3E23D311.E0914751@aaa.com>, Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> writes:r8 > I can't see that the lack of a PS viewer can be of any4 > importance what so ever at *commersial* VMS sites. > 3 > Maybe for a few hobbyists, but I can't see why HPJ> > should take *any* notice of what *non-paying* users think...  1 But for ISVs who want to create documentation ???    ------------------------------  % Date: Tue, 14 Jan 2003 19:20:12 +0100<9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com>p7 Subject: Re: Most common OpenVMS versions in use today?s' Message-ID: <3E2454DC.5EB6CDAE@aaa.com>t  ? I'm a DECdoc user myself, but always convert the PS output fromw< DECdoc into PDF on-the-fly, and reads the PDF on a PC. After< all, a PC is where this documentation will be read anyway...  	 Jan-Erik.    Larry Kilgallen wrote: > e > In article <3E23D311.E0914751@aaa.com>, Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> writes:o: > > I can't see that the lack of a PS viewer can be of any6 > > importance what so ever at *commersial* VMS sites. > >P5 > > Maybe for a few hobbyists, but I can't see why HPn@ > > should take *any* notice of what *non-paying* users think... > 3 > But for ISVs who want to create documentation ???    ------------------------------  % Date: Tue, 14 Jan 2003 15:17:05 +0000 % From: Alan Greig <a.greig@virgin.net> $ Subject: Re: Network troubleshooters8 Message-ID: <iaa82vcm0o24s3odpj0ld4rpoo7ip5ap06@4ax.com>  F On Thu, 09 Jan 2003 13:03:06 GMT, "John N." <JNixon@cfl.rr.com> wrote:  L >Can someone recommend a really good network troubleshooter?  I would prefer@ >to have 2nd hand referrals instead of someone looking for work. >rH >Our Local network has a lot of Cisco Gear (but not exclusively) , Unix,I >Windows, VAX and Alpha VMS, TCP/IP,  Decnet (Phase IV an phase V),  LAT,lM >varous flavors of SNA, firewalls and lots of other stuff I don't know about.mM >We are having frequent, intermittent, short-duration slowdowns and timeouts.i  A The first thing I'd check for is duplex mismatch. Check for large.7 numbers of "late collisions" in Cisco "show interface".   L >While it usually works well, and our network guys usually do a good job, weK >are having difficulty finding this problem.   And  generally, we  probablyt# >have lots of room for improvement.s >.   -- Alan   ------------------------------   Date: 14 Jan 2003 07:07:23 GMT- From: djweath@attglobal.net (Dave Weatherall)s Subject: Re: Newbie to OpenVMS.n5 Message-ID: <DTiotGxQ0bj6-pn2-o1jxYF6d9ddI@localhost>g  6 On Tue, 14 Jan 2003 03:31:03 UTC, "David J. Dachtera" - <djesys.nospam@earthlink.spamfree.net> wrote:    > Amarendra GODBOLE wrote:
 > > [snip]" > > But I don't know ... why there- > > is $ embedded in many if the names, etc..A >  > Oh, yeah. Good point.r > J > It's generally considered that file names, logical names, routine names,E > etc. containing a "$" are reserved to OpenVMS Engineering, and that-/ > users should avoid using "$" in such places. d > D > Generally, it is considered good form for users, ISVs, etc. to useF > underscore ("_") instead of "$" in file/logical/symbol/object(/etc.)
 > names...  = How many of us break the rule? I'm sure I'm not the only one.s  F It was a long time before I saw and read the statement w.r.t. $ being F reserved for Digital use. I'd already adopted the convention that the C $ indicated a logical name. At the time I believed I was following r DEC's=! convention. Naughty of me really.J   -- 1 Cheers - Dave.   ------------------------------    Date: 14 Jan 2003 03:45:56 -0800  From: otto@programmer.net (Otto)! Subject: OpenVMS license questiona= Message-ID: <c0b935a5.0301140345.5fb7ba32@posting.google.com>   P Can I use an OpenVMS 7.3 license with an older release, for instance 7.0 or 6.2?   ------------------------------    Date: 14 Jan 2003 12:01:48 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)a% Subject: Re: OpenVMS license questione3 Message-ID: <QCpDYM$SOVpQ@eisner.encompasserve.org>(  ` In article <c0b935a5.0301140345.5fb7ba32@posting.google.com>, otto@programmer.net (Otto) writes:R > Can I use an OpenVMS 7.3 license with an older release, for instance 7.0 or 6.2?  " Yes, both technically and legally.  K What you can _not_ do is get _support_ for older versions at the same pricecJ as for current versions.  If you are not on support, that does not matter.   ------------------------------    Date: 14 Jan 2003 07:51:54 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)d  Subject: Re: Reading file in DCL3 Message-ID: <C152GkNR19QR@eisner.encompasserve.org>t  e In article <slrnb26a5d.7gp.WADE@DAX.ASUB.ARKNET.EDU>, WADE@DAX.ASUB.ARKNET.EDU (Wade Fincher) writes:rE > Does anyone have any ideas on how I might go about reading the lastn@ > 30 bytes of a binary file and assigning the data to a logical?  %    Yes.  Now go do your own homework.    ------------------------------    Date: 14 Jan 2003 06:41:57 -0800. From: spamsink2001@yahoo.com (Alan E. Feldman)  Subject: Re: Reading file in DCL= Message-ID: <b096a4ee.0301140641.5e4cb46a@posting.google.com>   g JF Mezei <jfmezei.spamnot@vl.videotron.ca> wrote in message news:<3E2390B7.12517023@vl.videotron.ca>...n [...]w > M > This may sound silly, but is there a way to define a logical whose value is-P > that of a symbol without symbol substitution happening at thd DCL level ?  (soF > that any quotes in the symbol wouldn't mess things up for instance).  L Well, here's one way to do it. If anyone knows a better way, please post it.   Edited slightly for clarity:   $ A = """hi """"alan"""" hi"""  $ @XX-DOUBLE-ALL-QUOTES.COM A AB
 $ SH SYM A   A = ""hi ""alan"" hi"" $ SH SYM ABs    AB == """hi """"alan"""" hi""" $ DEFINE AB "''AB'"r $ SH LOG AB 0    "AB" = ""hi ""alan"" hi"" (LNM$PROCESS_TABLE)
 $ SH SYM A       A = ""hi ""alan"" hi""    ? $    SAVED_VERIFY = 'F$VERIFY(0)'  !+  XX_DOUBLE_ALL_QUOTES.COM  $vE $!+  PURPOSE: Doubles all quotes within the string value of a symbol wE $!            so that it can be used in the form "''symbol'" and the t- $!            quotes will come out all right.w $!H $!   PARAMETERS: p1 - the name of the symbol containing the input stringI $!               p2 - the name of the symbol to receive the output stringc $!+ $!   Written by Alan E. Feldman, 2003-01-03s3 $!   (Based on a similar routine by Jerry Leichter)g $!- $    SET SYMBOL/SCOPE=(NOLOCAL,NOGLOBAL)/VERBc $    STATUS = %X18008001& $    ON CONTROL_Y THEN EXIT %X1800800C $    ON WARNING THEN EXITe $    WSO := WRITE SYS$OUTPUT $    IF (F$TYPE('P1').EQS."")-	 $    THENe' $        WSO "P1 must be a symbol name"s $        RETURN %X18008004
 $    ENDIF $    PARAM = 'P1'e $    QUOTE = """"g $    DOUBLED = ""@
 $    I = 0 $_LOOP:>$ $    ELEM = F$ELEMENT(I,QUOTE,PARAM)( $    IF (ELEM.EQS.QUOTE) THEN GOTO _DONE- $    DOUBLED = DOUBLED + QUOTE + QUOTE + ELEM> $    I = I + 1 $    GOTO _LOOP> $_DONE: & $    DOUBLED = DOUBLED - QUOTE - QUOTE $    'P2' == DOUBLED8 $    EXIT $STATUS+0*F$VERIFY(SAVED_VERIFY).OR.%X10000000   Disclaimer: JMHO Alan E. Feldmann   ------------------------------    Date: 14 Jan 2003 04:51:18 -0800+ From: usenet_ihc@hotmail.com (Gert de Boom)eD Subject: Re: Retrieve RMS Key information at runtime (using Fortran)= Message-ID: <12ce5972.0301140451.599b5474@posting.google.com>    Hein wrote:h  D > Use the XABs you find, add those you need, then $DISPLAY and save F > desired data. When done you must remove any XABs from the xab chain  > that you have added.  B I'll take a better look at traversing the XABs in combination with	 $DISPLAY.s  J > > Another solution could be to use LIB$SPAWN and then create an FDL fileH > > using something like this: $analyze/rms_file /fdl myindexedfile.ind. > I > Yuck, don't spawn. Call FDL$GENERATE directly if you must, but then youa, > have to parse the result as you point out.  > I did already call FDL$GENERATE but it fails to return the key information.C Most likely once my routine for traversing XABs looking for the keyt? info works, FDL$GENERATE works too (I didn't use $DISPLAY yet).d   > (stuur me een mailtje, C   <dutch>wB Mocht ik er niet uit komen, dan doe ik dat zeker. Bedankt voor het aanbod.a </dutch>  , Thanks (also to Larry, Daryl, Randy and JF), Gert   ------------------------------  % Date: Tue, 14 Jan 2003 19:40:19 +0100m6 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>$ Subject: Re: SMTP mail: TFF facility) Message-ID: <3E245993.3030205@vajhoej.dk>    JF Mezei wrote:iO > OK, TFF is now documented. However, in the documentation,  it states that one E > simply creates an RFC822 message in a file, and submit this to TFF.e > L > Does this mean that  TFF will parse the RFC822 header to determine who the2 > message should be going to ? (not quite kosher). > K > For instance, if I wants to send to 5 people, but have a TO: <undisclosedb/ > recipients> line, is that possible with TFF ?r > L > Or must I go and reverser engineer the control file formats and submit the/ > files myself to the appropriate SMTP queues ?- > M > I would have prefered if one would provide TFF with 2 files, one containingsP > the destination and one containing the message.  In SMTP parlance, the MAIL TON > commands in the SMTP dialogue are quite difference from the DATA phase which> > contains teh message (the RFC822 header  is part of message)   Have you tried NBL ?   Arne   ------------------------------  % Date: Tue, 14 Jan 2003 02:40:12 -0400y0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>% Subject: Re: Suppressing SMTP headers / Message-ID: <3E23B0C0.5F4E07A5@vl.videotron.ca>r   Curtis Justus wrote: >  > Hello, > H > I am trying to suppress the SMTP header information from incoming SMTPN > e-mail messages.  I have configured my options on my SMTP service so that it, > reads "NOHEADERS," yet they still show up.  % TCPIP> SET CONF SMTP/OPTION=NOHEADERSb TCPIP> DISABLE SERVICE SMTPn  I (with UCX, you may need to get out of the utility and kill the processes)m   then TCPIP START SERVICE SMTPu  M In other words, the changes you make don't come into effect until you restart8
 the software.    ------------------------------  % Date: Tue, 14 Jan 2003 13:38:42 +0000P  From: grayd@turpinltd.com_nospam Subject: Surplus Kit8 Message-ID: <pa482vomai05mjcggv1dc1n5har9lsaagh@4ax.com>   Greetings, t  A The following suplus kit will be available within approx 1 month./E Contact me via email if you require further info or to make an offer.a   Will split!   6 Items located in North Hertfordshire, United Kingdom.    DEC Alpha 1    4000 Alpha Servere 2 x 5/600 CPU  2 x 512 mb Memoryh 11 x 4.3gb Disko 3 x 9.1gb Disk 2 x 18.2gb Diskt  1 x SW500 Storageworks Enclosure 1 x HSZ50 Cache Raid Controllern! 1 x TZ88 20/40 GB SCSI Tape Driveu* 1 x 1600/6250 BPI SCSI Table Top Tape Unit   DEC Alpha 2s   4000 Alpha Servere 2 x 5/400 CPU  2 x 512 mb MemoryS   7 x 4.3 gb Disk  2 x 18.2 gb Disk  0 Firmware of CPU boards in Alpha 2 do not match.   	 Regards, p 	David.    David.Gray@turpin.com.nospam       ------------------------------  % Date: Tue, 14 Jan 2003 15:32:27 +0000,% From: Alan Greig <a.greig@virgin.net>bA Subject: The Inquirer: How Mike Capellas was "castrated" by Carlyr8 Message-ID: <dab82voe4g0ekl3n2thk8kosrdrelfpkg1@4ax.com>  ( http://www.theinquirer.net/?article=7186  * How Mike Capellas was "castrated" by Carly   Ouch! Ouch! Ouch!   . By Esther Tigre: Monday 13 January 2003, 16:07  E AN ARTICLE in today's Wall Street Journal has extracts from a book by0D one of its reporters who tracked the merger of HP and Compaq. And in= it, he said that Carly Fiorina codenamed her firm Heloise ands Capellas' firm Abelard.y  D The article continues, Carly did not tell Capellas that the sad loveF affair between Heloise and Abelard ended up with the man in the affair being castrated.  F That, according to extracts published in the WSJ today, was not a factD that was known to Capellas until Autumn 2002. The author of the bookD said that when Capellas found out he shuddered and said: "I'm glad I
 didn't know".l  ? Which just goes to show that if you're a CEO of a multinational ; corporation it pays to be well read as well as filthy rich.a  C The article goes on to say that Capellas thought he would be CEO of D the joint company, but behind his back HP staff were laughing at the possibility.  B Presumably Carly did know about the mediaeval story of Heloise and
 Abelard...  D If she is Heloise, then she is in a virtual convent at Arguentil and? they will meet again in nine years time. But there won't be any $ champagne next time round, we guess.  D The book is called Perfect Enough: Carly Fiorina and the Reinvention& of Hewlett-Packard by George Anders.  -- Alan   ------------------------------    Date: 14 Jan 2003 10:45:46 -0800$ From: rcbryan@hotmail.com (RC Bryan)Y Subject: The manual says "Do not use QIO for reading from a file" has anyone heard of thig= Message-ID: <fbcf38dc.0301141045.25fd47be@posting.google.com>e  E In the "OpenVMS Programming Concepts Manual" (which can be referencede at: A http://www.openvms.compaq.com/doc/731FINAL/5841/5841pro_061.html)iE in section 23.9.1: it says "Note  Do not use the SYS$QIO and SYS$QIOWa= system services for input from a file or nonterminal device."a  C I admit I did not read every last bit of the surrounding text but IwB have to ask, "What does the system use for reading?"  Am I missingB something here?  What are we supposed to use to read non-RMS data?   Comment anybody?   Regards,	 /RC Bryan    ------------------------------   Date: 14 Jan 2003 07:07:22 GMT- From: djweath@attglobal.net (Dave Weatherall) + Subject: Re: The need for reliable desktops 5 Message-ID: <DTiotGxQ0bj6-pn2-fbx0PdphDStm@localhost>   " On Mon, 13 Jan 2003 14:03:03 UTC, < koehler@eisner.nospam.encompasserve.org (Bob Koehler) wrote:  g > In article <DTiotGxQ0bj6-pn2-SbC3ZdimF222@localhost>, djweath@attglobal.net (Dave Weatherall) writes:u > C > > Well in a space-station I would have thought you sell the heat .E > > generation from VMS/Alpha notebooks as  a method of recycling or 4I > > overall energy efficiency :-) The tadpole salesmen definitely missed e > > an opportunity there.i > G >    Inside the space station a 75W eater is a problem.  Heat builds upbJ >    and you have to get rid of it.  Outside you are either too hot or tooI >    cold depending an whether your on the dark or lit side, so their areu* >    radiators and heaters to handle both.   <snip>  0 Exactly, Alpha notebooks - for the dark side :-)  F Seriously though, thanks for the info Bob. It is all to easy to forgetE that space isn't  just cold, or rather, a body in space won't always l be cold.   -- a Cheers - Dave.   ------------------------------  % Date: Tue, 14 Jan 2003 11:35:14 +0000p% From: Alan Greig <a.greig@virgin.net>e& Subject: Re: vax6k.openecs.org rebirth8 Message-ID: <iss72v0n5vk89kh8rdsla7djhiq9ckmn9r@4ax.com>  E On 3 Jan 2003 07:27:24 -0600, koehler@eisner.nospam.encompasserve.org  (Bob Koehler) wrote:  W >In article <2JAN200322230368@gerg.tamu.edu>, carl@gerg.tamu.edu (Carl Perkins) writes:rI >> Way back when, roughly 1983, I got cought calling the phsyical memory, J >> e.g. RAM, of an 11/780 "core" by someone who thought it odd. Why did I?F >> I picked it up from the people I worked for and with. Why did they?G >> Because that's what they had always called that sort of thing - theySE >> didn't care if it was real "core" type memory, it was the physicalrG >> memory and they always called it "core". At that point I didn't care H >> what the difference was (and was barely aware of the difference), andG >> neither did they. The expression was apparently pretty commonly usedf >> that way back then. >eE >   Once upon a time we had a facility with 3 PDP-11, 2 PDP-10, and 8uC >   11/780.  One of the engineers came by and said we were going tolE >   replace the 1MB core in the 2050, I thought he was talking out ofc
 >   habit.  E When you replaced the core memory with IC based memory in a DEC20 the,B entire cabinet could become unstable if certain access panels wereF swung out due to  the absence of the heavy core memory.. Field ServiceE engineers told me they had actually heard of machines tipping over inhE the early upgrade days before the problem was fixed. I *think* we hadwA counterweights fitted but it might have just been a large warningt sticker. Can't recall now.  	 >   Nope.s   -- Alan   ------------------------------  # Date: Tue, 14 Jan 2003 15:24:54 GMTr4 From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>& Subject: Re: vax6k.openecs.org rebirth8 Message-ID: <5oa82vo7j2lqn8acqisbl5i1i67n5h3q6t@4ax.com>  . On Tue, 14 Jan 2003 11:35:14 +0000, Alan Greig <a.greig@virgin.net> wrote:p  F >On 3 Jan 2003 07:27:24 -0600, koehler@eisner.nospam.encompasserve.org >(Bob Koehler) wrote:i >uX >>In article <2JAN200322230368@gerg.tamu.edu>, carl@gerg.tamu.edu (Carl Perkins) writes:J >>> Way back when, roughly 1983, I got cought calling the phsyical memory,K >>> e.g. RAM, of an 11/780 "core" by someone who thought it odd. Why did I?iG >>> I picked it up from the people I worked for and with. Why did they?mH >>> Because that's what they had always called that sort of thing - theyF >>> didn't care if it was real "core" type memory, it was the physicalH >>> memory and they always called it "core". At that point I didn't careI >>> what the difference was (and was barely aware of the difference), and-H >>> neither did they. The expression was apparently pretty commonly used >>> that way back then.E >>F >>   Once upon a time we had a facility with 3 PDP-11, 2 PDP-10, and 8D >>   11/780.  One of the engineers came by and said we were going toF >>   replace the 1MB core in the 2050, I thought he was talking out of >>   habit.- >-F >When you replaced the core memory with IC based memory in a DEC20 theC >entire cabinet could become unstable if certain access panels wereDG >swung out due to  the absence of the heavy core memory.. Field Service F >engineers told me they had actually heard of machines tipping over inF >the early upgrade days before the problem was fixed. I *think* we hadB >counterweights fitted but it might have just been a large warning >sticker. Can't recall now.8 >D
 >>   Nope.  ? Was often a little foot extended on a sliding piece of frame onhA each side: was actually more of a problem when you had drawers of1@ core in a rack -- like horizontal files: no more than one drawer could be extended at a time. E  9 Thanks. Take care, Brian Inglis 	Calgary, Alberta, Canada  --  F Brian.Inglis@CSi.com 	(Brian dot Inglis at SystematicSw dot ab dot ca),     fake address		use address above to reply@ abuse@aol.com tosspam@aol.com abuse@att.com abuse@earthlink.com ? abuse@hotmail.com abuse@mci.com abuse@msn.com abuse@sprint.com eB abuse@yahoo.com abuse@cadvision.com abuse@shaw.ca abuse@telus.com - abuse@ibsystems.com uce@ftc.gov				spam traps2   ------------------------------   Date: 14 Jan 2003 09:36:29 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren)* Subject: VMS on Itanic boot report sighted0 Message-ID: <b00lmt$lma$1@pegasus.csx.cam.ac.uk>  G As reports of VMS being about to boot on the Itanic have been appearing,' for over a year now, I make no comment.d  ( http://www.theinquirer.net/?article=7191     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 334679u   ------------------------------  % Date: Tue, 14 Jan 2003 09:51:58 -0500/ From: norm.raphael@metso.com. Subject: Re: VMS on Itanic boot report sighted? Message-ID: <OF6781CABB.B60B066D-ON85256CAE.00518082@metso.com>   5 If only you had actually said, "No comment," instead.A5 Knowledgeable readers here know what's what, eh what.e  @ From:  nmm1@cus.cam.ac.uk (Nick Maclaren) on 01/14/2003 04:36 AM  4 Please respond to nmm1@cus.cam.ac.uk (Nick Maclaren)   To:    Info-VAX@Mvb.Saic.Com cc:e  - Subject:    VMS on Itanic boot report sightedb      G As reports of VMS being about to boot on the Itanic have been appearingi' for over a year now, I make no comment.t  ( http://www.theinquirer.net/?article=7191     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 334679-   ------------------------------  % Date: Tue, 14 Jan 2003 10:12:58 -0500;A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com>4. Subject: Re: VMS on Itanic boot report sighted. Message-ID: <3e2428fb$1_3@hpb10302.boi.hp.com>  5 "Nick Maclaren" <nmm1@cus.cam.ac.uk> wrote in messageI* news:b00lmt$lma$1@pegasus.csx.cam.ac.uk... >pI > As reports of VMS being about to boot on the Itanic have been appearing ) > for over a year now, I make no comment.  >u  E Getting new compilers complete (Bliss, Macro-32, C), dealing with thebG complexities of different calling standards and the need to continue topK support all that non-standard VAX code, a new linker, new tools, new object F format, new image format, new firmware standard (and ACPI) has taken aL while.  Unlike a new UNIX platform, it's a bit more than just getting GCC to compile and link.p  @ But the reports are fairly accurate as to just how close we are.   ------------------------------  % Date: Tue, 14 Jan 2003 07:15:18 -0800&# From: "Tom Linden" <tom@kednos.com>n. Subject: RE: VMS on Itanic boot report sighted9 Message-ID: <CIEJLCMNHNNDLLOOGNJIMEJLGGAA.tom@kednos.com>>  A The transition to Itanium might have been easier had it been froms@ VAX rather than Alpha.  It looks to me that it would have been a? lot easier porting VCG rather than GEM, but then, I am probablyb wrong.   >-----Original Message----->G >From: Fred Kleinsorge [mailto:kleinsorge@star-dot-zko-dot-dec-dot-com]0( >Sent: Tuesday, January 14, 2003 7:13 AM >To: Info-VAX@Mvb.Saic.Com/ >Subject: Re: VMS on Itanic boot report sighted  >> >>6 >"Nick Maclaren" <nmm1@cus.cam.ac.uk> wrote in message+ >news:b00lmt$lma$1@pegasus.csx.cam.ac.uk...& >>J >> As reports of VMS being about to boot on the Itanic have been appearing* >> for over a year now, I make no comment. >> >&F >Getting new compilers complete (Bliss, Macro-32, C), dealing with theH >complexities of different calling standards and the need to continue toL >support all that non-standard VAX code, a new linker, new tools, new objectG >format, new image format, new firmware standard (and ACPI) has taken a2> >while.  Unlike a new UNIX platform, it's a bit more than just >getting GCC to> >compile and link. > A >But the reports are fairly accurate as to just how close we are.n >; >s >U >A >---' >Incoming mail is certified Virus Free.b; >Checked by AVG anti-virus system (http://www.grisoft.com).sB >Version: 6.0.435 / Virus Database: 244 - Release Date: 12/30/2002 >- ----& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).A Version: 6.0.435 / Virus Database: 244 - Release Date: 12/30/2002<   ------------------------------  % Date: Tue, 14 Jan 2003 16:14:07 -00000* From: "Richard Brodie" <R.Brodie@rl.ac.uk>. Subject: Re: VMS on Itanic boot report sighted+ Message-ID: <b01d0g$q28@newton.cc.rl.ac.uk>2  b "Tom Linden" <tom@kednos.com> wrote in message news:CIEJLCMNHNNDLLOOGNJIMEJLGGAA.tom@kednos.com...C > The transition to Itanium might have been easier had it been fromDB > VAX rather than Alpha.  It looks to me that it would have been aA > lot easier porting VCG rather than GEM, but then, I am probably; > wrong.  A I would imagine that just about any second platform port would benH significantly easier than the first, almost regardless of the specifics.   ------------------------------  % Date: Tue, 14 Jan 2003 11:17:55 -0500 + From: Steve Lionel <Steve.Lionel@intel.com>&. Subject: Re: VMS on Itanic boot report sighted8 Message-ID: <nld82v0mlkv7smc2jprblk2j7vk6bvt99f@4ax.com>  A On Tue, 14 Jan 2003 07:15:18 -0800, "Tom Linden" <tom@kednos.com>s wrote:  B >The transition to Itanium might have been easier had it been fromA >VAX rather than Alpha.  It looks to me that it would have been aQ@ >lot easier porting VCG rather than GEM, but then, I am probably >wrong.t   Yes, you probably are.  F GEM in fact already had Itanium support, albeit for Linux and Windows,> not VMS.  It wasn't well tested, but it was there.  But simplyA supporting the processor in the code generator is only 10% of the&! overall porting effort - if that.&  A Furthermore, all of the "interesting" compilers use GEM, not VCG.-    D Please send Visual Fortran support requests to vf-support@compaq.com   Steve Lionel Software Products Division Intel Corporations
 Nashua, NH  = User communities for Intel Fortran and Compaq Visual Fortran:&    http://intel.com/IDS/community   ------------------------------    Date: 14 Jan 2003 11:58:49 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen);. Subject: RE: VMS on Itanic boot report sighted3 Message-ID: <UMwucZOY6gKk@eisner.encompasserve.org>t  _ In article <CIEJLCMNHNNDLLOOGNJIMEJLGGAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes:4C > The transition to Itanium might have been easier had it been frompB > VAX rather than Alpha.  It looks to me that it would have been aA > lot easier porting VCG rather than GEM, but then, I am probablyt > wrong.  $ Compilation is not the _only_ issue.  ; There is also the business of supporting 64-bit addressing.;   ------------------------------  % Date: Tue, 14 Jan 2003 10:55:54 +0000&( From: Nic Clews <sendspamhere@127.0.0.1>" Subject: Re: What does RWCLU mean?) Message-ID: <3E23ECBA.1EA681AF@127.0.0.1>5   Daryl Jones wrote: > S > Saminda C F Lam <ccminda@ust.hk> wrote in message news:<3E1E9FE6.60809@ust.hk>...bE > > What does RWCLU mean?  The manual says "Resource Wait for Cluster,K > > Transition".  I found processes in RWCLU state on an Alpha cluster.  Is>C > > it indicative of some resource problem?  If so, what resources?   vC > The lock manager uses RWSCS to stall executions of a process on aaG > VMScluster node when the lock manager must wait for a response from a(H > remote system that has information about the particular lock resource.  D Yes, typically this would occur for lock directory lookups, and lockF requests to the node mastering the lock in question. Ideally you don'tC want to see processes in this state (maybe only briefly) as it doesjH infer that the cluster protocol is holding up a process. However this is a different state from...l  H > A process that issues any lock requests on any node of a VMScluster inH > transition (that is, while a node is being added or removed) is placed; > into RWCLU wait until the cluster memebership stabilizes.o  C And this is the difference, but only part of the story. DistributedlC locking needs co-operation from all systems, because the locking is A shared between those with a LOCKDIRWT, and the interests of thoserG systems without, are represented. In transition, when the membership ofsE a system which has remote responsibilities to the cluster is put into:D question, locks dependent on that system hold until the situation is7 resolved one way or another. RWSCS can turn into RWCLU.g  H In the case of a failing system where the lock in question is local, theH process will continue either until it becomes dependent on a remote lockF resource, or the system fails. (It could recover of course and nothing would be any different).  G The RWCLU happens when the lock information of which a request is being-F made, because some other system is either the directory manager or theE current (remote) master, and the wait state is maintained because then< system is the subject of a transition in the current clusterC incarnation, or this system is irrevocably removed from the currentvF incarnation, and the lock information is remastered (this node will ofF course have a local copy of the information from which the information can be rebuilt).  ? A transition is also triggered when interconnects change state.u  E There is another case for RWCLU, this is for lock remastering. If the G locking activity against a distributed lock is of a rate high enough torH determine it would most likely be more efficiently handled by some otherF node, then the lock processing on that lock tree (but not all locks inC all trees) is frozen while it is moved. This additional meaning foruG RWCLU was inherited when the V5.5 remastering algorithm was introduced.   F In my previous response to this, I started to talk about this. ImagineG that this is a two node cluster with two co-operating processes, one onuE each node, each active in a particular tree of locks. Say one processtE does a burst of processing (and locking) against this tree, then thismG node is the obvious best master for this tree, and the lock manager may H decide to remaster the locks from the remote master, and there's a RWCLUH while this happens. Then, the burst of activity moves to the other node,F and then the other node becomes a more logical candidate as the masterA for the lock, and it gets remastered back again. In this there isw: absolutely no hint of either a cluster member failure or a reconfiguration.  D This behaviour is either as expected, or down to application design.G While it is possible to address this behaviour using SYSGEN parameters,-H I would advise against it unless you really know what you are doing, and? can explain from a system and application point of view why theR conditions are being observed.  > We're speculating here, we don't know how many nodes, what any underlying conditions are.  F An article "Discussion of processes in the RWXXX scheduling states" isA enlightening. Now they've replaced askopenvms with the HP naturaliE language thing, it seems to be more difficult (or the information has-G now become restricted) to get to the articles. Also, VAXcluster systemstG Quorum from May 1992  and "VAXcluster Principles" as well as a plethoragG of internals books are useful in understanding this (not forgetting the. documentation).   5 (I'm also trying not to make this sound complicated).    -- n? Regards, Nic Clews a.k.a. Mr. CP Charges, CSC Computer Sciences  nclews at csc dot coms   ------------------------------    Date: 14 Jan 2003 07:48:00 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)h8 Subject: Re: Why doesn't SET BREAK %LABEL work any more?3 Message-ID: <qvmVlCS8XOkk@eisner.encompasserve.org>n  k In article <Pine.LNX.4.50.0301131549550.22253-100000@jaipur>, Ryan Moore <rmoore@rmoore.dyndns.org> writes:FE > I don't know how this works in Fortran, but in C, I always have theeG > compiler create a .LIS file that contains line numbers of the code inoK > question and then do a SET BREAK %LINE command.  Can Fortran do somethingi
 > similar?  ?    DEBUG can set breakpoints on a line number for all supporteddH    languages.  You don't have to make a list file, you can just find the-    line via the SRC window or examine/source.o   ------------------------------  % Date: Tue, 14 Jan 2003 11:10:49 -0500s+ From: Steve Lionel <Steve.Lionel@intel.com>i8 Subject: Re: Why doesn't SET BREAK %LABEL work any more?8 Message-ID: <4gd82v8d1jfgalmoi6qqlmih9q0nm4f1vp@4ax.com>  . On Mon, 13 Jan 2003 23:28:50 +0000, John Laird! <john@laird-towers.org.uk> wrote:h  I >One for the compiler group, then.  (I don't think Steve Lionel reads covtM >regularly.)  My experience is they've usually seen and fixed any bug we everoF >reported, so it's a question of finding or waiting on the appropriate >update.  3 I do, but not every message.  Saw this one, though.n  = As others have noted, we fixed this bug in version 7.4 of thes' compiler.  That was, um, two years ago?e    D Please send Visual Fortran support requests to vf-support@compaq.com   Steve Lionel Software Products Division Intel Corporations
 Nashua, NH  = User communities for Intel Fortran and Compaq Visual Fortran:v    http://intel.com/IDS/community   ------------------------------  % Date: Tue, 14 Jan 2003 11:34:48 -0000e* From: "Richard Brodie" <R.Brodie@rl.ac.uk> Subject: Re: Wireless Ethernet+ Message-ID: <b00skp$o8m@newton.cc.rl.ac.uk>V  \ "Shane Smith" <ssmith@icius.com> wrote in message news:01C2BB27.A134B5A0@sulfer.icius.com...  I > OK, now this is the part I'm curious about, especially since I'm in the A > process of installing some wireless gear. How is this key used?0  E Badly by most accounts: best advice seems to be to not to rely on WEPnN to protect your data. As with a number of other similar designs, it's not goodJ enough to use a cryptographically strong cipher, you have to use it right.  3 http://www.isaac.cs.berkeley.edu/isaac/wep-faq.htmlt   ------------------------------  + Date: Tue, 14 Jan 2003 14:30:19 +0000 (UTC)M+ From: david20@alpha2.mdx.ac.uk (David Webb)t Subject: Re: Wireless Ethernet+ Message-ID: <b016tr$blh$1@aquila.mdx.ac.uk>h  j In article <5.1.0.14.2.20030113181744.00bb3ca0@raptor.psccos.com>, Dan O'Reilly <dano@process.com> writes:- >At 06:13 PM 1/13/2003, Michael Austin wrote:oH >>If you do not provide a WEP key in your router/WAP device, then anyoneI >>with a Wireless card can access the internet through your connection --E9 >>and it would look like the data was transferred to you.E >cK >Not strictly true.  Some WAP's, such as the Linksys I use, can also filteri >on allowable MAC addresses. >aD Which adds little security since MAC addresses can be easily forged.  M There are many articles on the web on the woeful security of current wirelesso protocols and products.    See for instance :-n  A http://www.oreillynet.com/pub/a/wireless/2002/04/19/security.html   
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------   End of INFO-VAX 2003.028 ************************reate documentation ???    ------------------------------  % Date: Tue, 14 Jan 2003 15:17:05 +0000 % From: Alan Greig <a.greig@virgin.net> $ Subject: Re: Network troubleshooters8 Message-ID: <iaa82vcm0o24s3odpj0ld4rpoo7ip5ap06@4ax.com>  F On Thu, 09 Jan 2003 13:03:06 GMT, "John N." <JNixon@cfl.rr.com> wrote:  L >Can someone recommend a really good network troubleshooter?  I would prefer@ >to have 2nd h