1 INFO-VAX	Fri, 01 Mar 2002	Volume 2002 : Issue 118       Contents: Alpha 2100A errors Alpha CPU Architecture question ! anyone in the UK need a VMS bod ? $ AUTOGEN Parameter Calculation Report( Re: AUTOGEN Parameter Calculation Report( Re: AUTOGEN Parameter Calculation Report+ Re: Compaq adopts microsoft approach to VMS + RE: Compaq adopts microsoft approach to VMS + Re: Compaq adopts microsoft approach to VMS + Re: Compaq adopts microsoft approach to VMS + Re: Compaq adopts microsoft approach to VMS + Re: Compaq adopts microsoft approach to VMS  Re: copying system disks Re: copying system disks Re: copying system disks Re: copying system disks Re: copying system disks Re: copying system disks Re: copying system disks Re: copying system disks Re: copying system disks RE: copying system disks Re: decnet phase IV -> phase V Re: decnet phase IV -> phase V Re: decnet phase IV -> phase V Re: decnet phase IV -> phase V Re: decnet phase IV -> phase V Re: decnet phase IV -> phase V Re: DTE Unsynchronised) Earn a dime every time you receive email!  Re: expensive procedure calls " Hewlett releases committee minutes& RE: Hewlett releases committee minutes& RE: Hewlett releases committee minutes; Re: HP & Compaq high-end systems to "stay around for years"  Re: I: PAKGEN Software for ISVs  Re: Itanium troubles Re: Itanium troubles Re: Itanium troubles Re: Itanium troubles+ Re: Microsoft Curries Favor With Undergrads  Re: No route to host? E Re: OpenVMS get together in Houston - thought you might be interested E Re: OpenVMS get together in Houston - thought you might be interested E Re: OpenVMS get together in Houston - thought you might be interested  Re: proliant 1600 not booting  QUORUM disk question Re: QUORUM disk question Re: QUORUM disk question Re: restricting access to ports  Re: restricting access to ports  Re: restricting access to ports  Re: restricting access to ports  Re: restricting access to ports  Re: Solution for the merger  Re: Solution for the merger  Re: Solution for the merger  Re: Sound on alpha/VMS?  Re: Sound on alpha/VMS? & Sun eating major helping of Linux Crow* Re: Sun eating major helping of Linux Crow Re: Timing is everything Re: Timing is everythingA uniform message format (was: RE: What return codes mean success?) % Re: vax/vms documentation - psi / x29 % Re: vax/vms documentation - psi / x29 % Re: vax/vms documentation - psi / x29  VMS / EMA agent problems# Re: What return codes mean success? # Re: What return codes mean success? # Re: What return codes mean success? # Re: What return codes mean success? # Re: What return codes mean success? # Re: What return codes mean success? # Re: What return codes mean success?  Re: [Q] internet and VMS  F ----------------------------------------------------------------------   Date: 1 Mar 2002 16:31:54 GMT 1 From: Dale.J.Martin@lerc.nasa.gov (Dale J Martin)  Subject: Alpha 2100A errors 4 Message-ID: <a5oadq$efk$1@sulawesi-fi.lerc.nasa.gov>  
 Greetings,  N I work for a service provider that maintains assorted Alpha platforms running O OpenVMS 7.1-2. Since we installed OpenVMS 7.1-2 roughly two years ago, we have  K experienced several 630 cache correctable and 660 uncorrectable CPU errors  O (either one or the other or both) on all of our AlphaServer 2100A systems. The  M frequency of these errors occuring can be anywhere from three weeks to three  L months, depending on the individual system. When we contact Compaq support, L they tell us that the 630 errors are of no great concern and that we should M monitor the system for future occurances and think about replacing memory if  J they occur frequently. Of greater concern to us are the 660 uncorrectable O errors, Compaq doesn't offer much except to say that some event on the PCI bus  N is causing them and the CPU can't correct the error. We do have an assortment 2 of third-party PCI cards installed in the 2100As.   M Has anyone had any type of experience with the cause of these 660 errors? If  H so, what have you done about them? We have tried replacing CPU, memory, L PCI/EISA daughter boards, system boards, and PCI cards to no avail, the 660 P error problem doesn't seem to follow any one piece of hardware. With the amount E of output we get from the error log files, one would think that some  P determination could be made about what specifically is happening to cause these N errors. Upgrading O/S or hardware is not an option right now, I would like to 9 know why this is happening on these particular platforms.    Thanks.    ------------------------------  % Date: Fri, 01 Mar 2002 09:51:36 -0600 ( From: David Harrold <DHarrold@wi.rr.com>( Subject: Alpha CPU Architecture question2 Message-ID: <a5o828$u38$1@newsreader.mailgate.org>  L We had a crash yesterday on one of our GS-160s and the reason came back fromN the support center as a BCache failure on one of the CPUs.  SO what exactly is the BCache?   N And more generally, is there any publicly available documentation on the Alpha) CPUs that describe these types of things?    Thanks,    Dave Harrold    N ..............................................................................N David Harrold                              E-Mail: David_Harrold at aurora.orgI Sr. Software Systems Engineer              Phone:          (414) 647-6204 I                                            Pager:          (414) 941-4634 G Aurora Health Care                         Fax:          (414) 647-4999  3031 W. Montana Street Milwaukee, WI 53215    ------------------------------   Date: 1 Mar 2002 01:16:43 -0800  From: rob@mkgm.com (rob murphy) * Subject: anyone in the UK need a VMS bod ?= Message-ID: <9e72a7b2.0203010116.28f1afaa@posting.google.com>   	 Morning !   C Its that time again, my contract has expired and I am looking for a B new one. 16 years industy experience, covering every aspect of VMSB (engineering, installation, management, programming, netwoking etcC etc). I also have a wealth of experience with NT, Exchange, Citrix, ' x25, Delphi/pascal, C++ and a lot more.   F As usual the agencies are giving me the runaround, and I know there isD not much out there, however if anyone has any positions going pleaseE feel free to drop me an email and maybe we can work something out - I E am based in Essex but have worked all over the place so I am happy to  work anywhere.  : Drop me an email if you would like to see my full details.   Cheers, 
 Rob Murphy rob@mkgm.com   ------------------------------   Date: 1 Mar 2002 01:36:07 -0800  From: sam@ratex.dk (Sam)- Subject: AUTOGEN Parameter Calculation Report < Message-ID: <d1111de.0203010136.4315fa18@posting.google.com>  	 Hi Folks.   0 Alpha OpenVMS V7.2-1 with all pathes up to date.  B Are these enormous ACP_... attempt rates anything to worry about ?    # ACP_DIRCACHE parameter information:          Feedback information. 0            Old value was 4000, New value is 4000            Hit percentage: 100% 8            Attempt rate: 4294967084 attempts per 10 sec.<         - AUTOGEN parameter calculation has been overridden.9            The calculated value was 1488.  The value 4000 F            will be used in accordance with the following requirements:.            ACP_DIRCACHE minimum value is 4000.  % ACP_DINDXCACHE parameter information:          Feedback information. 0            Old value was 4000, New value is 4000            Hit percentage: 99%8            Attempt rate: 4294966758 attempts per 10 sec.<         - AUTOGEN parameter calculation has been overridden.8            The calculated value was 372.  The value 4000F            will be used in accordance with the following requirements:0            ACP_DINDXCACHE minimum value is 4000.  # ACP_HDRCACHE parameter information:          Feedback information. 0            Old value was 4000, New value is 4000            Hit percentage: 59%8            Attempt rate: 4294966762 attempts per 10 sec.<         - AUTOGEN parameter calculation has been overridden.9            The calculated value was 1488.  The value 4000 F            will be used in accordance with the following requirements:.            ACP_HDRCACHE minimum value is 4000.   Sam    ------------------------------  % Date: Fri, 01 Mar 2002 14:19:02 +0100 ( From: Paul Sture <paul.sture@bluewin.ch>1 Subject: Re: AUTOGEN Parameter Calculation Report ) Message-ID: <3C7F7FC6.3020504@bluewin.ch>   
 Sam wrote:   > Hi Folks.  > 2 > Alpha OpenVMS V7.2-1 with all pathes up to date. > D > Are these enormous ACP_... attempt rates anything to worry about ? >  > % > ACP_DIRCACHE parameter information:  >         Feedback information. 2 >            Old value was 4000, New value is 4000! >            Hit percentage: 100% : >            Attempt rate: 4294967084 attempts per 10 sec.> >         - AUTOGEN parameter calculation has been overridden.; >            The calculated value was 1488.  The value 4000 H >            will be used in accordance with the following requirements:0 >            ACP_DIRCACHE minimum value is 4000. > ' > ACP_DINDXCACHE parameter information:  >         Feedback information. 2 >            Old value was 4000, New value is 4000  >            Hit percentage: 99%: >            Attempt rate: 4294966758 attempts per 10 sec.> >         - AUTOGEN parameter calculation has been overridden.: >            The calculated value was 372.  The value 4000H >            will be used in accordance with the following requirements:2 >            ACP_DINDXCACHE minimum value is 4000. > % > ACP_HDRCACHE parameter information:  >         Feedback information. 2 >            Old value was 4000, New value is 4000  >            Hit percentage: 59%: >            Attempt rate: 4294966762 attempts per 10 sec.> >         - AUTOGEN parameter calculation has been overridden.; >            The calculated value was 1488.  The value 4000 H >            will be used in accordance with the following requirements:0 >            ACP_HDRCACHE minimum value is 4000. > & Looks like DCL integer overflow to me.    
 Paul Sture Switzerland    ------------------------------  # Date: Fri, 01 Mar 2002 14:27:26 GMT 1 From: "Mark D. Jilson" <jilly@clarityconnect.com> 1 Subject: Re: AUTOGEN Parameter Calculation Report 2 Message-ID: <3C7F900C.A31ECF68@clarityconnect.com>  E Look at the values in AGEN$FEEDBACK.DAT.  I suspect that they be very F large and that AUTOGEN didn't take this into account and thus exceeded the limits of DCL math.   
 Sam wrote: >  > Hi Folks.  > 2 > Alpha OpenVMS V7.2-1 with all pathes up to date. > D > Are these enormous ACP_... attempt rates anything to worry about ? > % > ACP_DIRCACHE parameter information:  >         Feedback information. 2 >            Old value was 4000, New value is 4000! >            Hit percentage: 100% : >            Attempt rate: 4294967084 attempts per 10 sec.> >         - AUTOGEN parameter calculation has been overridden.; >            The calculated value was 1488.  The value 4000 H >            will be used in accordance with the following requirements:0 >            ACP_DIRCACHE minimum value is 4000. > ' > ACP_DINDXCACHE parameter information:  >         Feedback information. 2 >            Old value was 4000, New value is 4000  >            Hit percentage: 99%: >            Attempt rate: 4294966758 attempts per 10 sec.> >         - AUTOGEN parameter calculation has been overridden.: >            The calculated value was 372.  The value 4000H >            will be used in accordance with the following requirements:2 >            ACP_DINDXCACHE minimum value is 4000. > % > ACP_HDRCACHE parameter information:  >         Feedback information. 2 >            Old value was 4000, New value is 4000  >            Hit percentage: 59%: >            Attempt rate: 4294966762 attempts per 10 sec.> >         - AUTOGEN parameter calculation has been overridden.; >            The calculated value was 1488.  The value 4000 H >            will be used in accordance with the following requirements:0 >            ACP_HDRCACHE minimum value is 4000. >  > Sam    --  D Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------  % Date: Fri, 01 Mar 2002 11:53:36 +0100 ( From: Paul Sture <paul.sture@bluewin.ch>4 Subject: Re: Compaq adopts microsoft approach to VMS) Message-ID: <3C7F5DB0.9080702@bluewin.ch>    John Santos wrote:   > ) > What is 7.1-1H2????  Never heard of it.  > d I believe it contained extra hardware support for certain models, and was only delivered with those.    
 Paul Sture Switzerland    ------------------------------  $ Date: Fri, 1 Mar 2002 07:53:42 -0500+ From: "Main, Kerry" <Kerry.Main@Compaq.com> 4 Subject: RE: Compaq adopts microsoft approach to VMST Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF4016CEB1E@kaoexc01.americas.cpqcorp.net>   Paul,=20  E >>> I believe it contained extra hardware support for certain models, $ and was only delivered with those.<<  > A good url to keep handy when these types of questions arise -7 http://www.openvms.compaq.com/openvms/supportchart.html    Regards   
 Kerry Main Senior Consultant  Compaq Canada Corp.  Professional Services  Voice: 613-592-4660  Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----2 From: Paul Sture [mailto:paul.sture@bluewin.ch]=20 Sent: March 1, 2002 5:54 AM  To: Info-VAX@Mvb.Saic.Com 4 Subject: Re: Compaq adopts microsoft approach to VMS     John Santos wrote:   >=20) > What is 7.1-1H2????  Never heard of it.  >=20E I believe it contained extra hardware support for certain models, and  was only delivered with those.    
 Paul Sture Switzerland    ------------------------------  % Date: Fri, 01 Mar 2002 14:23:05 +0000 ( From: Nic Clews <sendspamhere@127.0.0.1>4 Subject: Re: Compaq adopts microsoft approach to VMS( Message-ID: <3C7F8EC9.4645837@127.0.0.1>   Paul Sture wrote:  >  > John Santos wrote: >  > > + > > What is 7.1-1H2????  Never heard of it.  > > h > I believe it contained extra hardware support for certain models, and was only delivered > with those.   Extract fromE http://www.openvms.compaq.com/openvms/os/openvms-release-history.html     E          |V7.1-1H1 |Superseded by         |  -NOV-1997 FRS | | |  for : the following:                                           |G                            |           |         |V7.1-1H2               |                |F| |    < UltraSCSI:                                                 |G                            |           |         |                      D |                | | |      - KZPBA-CA adapter on AlphaServers 4100, 4000, 2100,     | G                            |           |         |                      @ |                |Y| |        2100A, 2000, 1200, 1000, 1000A and 800                 | G                            |           |         |                      F |                | | |      - UltraSCSI disks such as RZ1BB, RZ1CB and RZ1DB         | G                            |           |         |                      G |                | | |    HSZ70 UltraSCSI controller for the Enterprise  Storage Array|G                            |           |         |                      F |                | | |      10,000 (initially in Fast SCSI mode on the KZPSA adapter | G                            |           |         |                      ) |                | | |    AlphaServer 800 , 5/500                                      |G                            |           |         |                      % |                | | |    AlphaServer 0 1200                                           |G                            |           |         |                      3 |                | | |    DIGITAL Modular Computing " Components:                      |G                            |           |         |                      / |                | | |      - Alpha 5/366 PICMG & SBC                                  |G                            |           |         |                      / |                | | |      - Alpha 5/433 PICMG & SBC                                  |G                            |           |         |                      * |                | | |    DE500-BA Network+ Adapter                                   | G                            |           |         |                     i< |                | | |    DE500-FA Network Adapter (run-time only)                   |aG                            |           |         |                     oA |                | | |                                           h  B I installed it on a Digital Modular system with two graphic heads.   -- r( Regards, Nic Clews CSC Computer Sciences nclews at csc dot comM   ------------------------------  # Date: Fri, 01 Mar 2002 16:14:10 GMTs4 From: Tim Llewellyn <tim.llewellyn@blueyonder.co.uk>4 Subject: Re: Compaq adopts microsoft approach to VMS/ Message-ID: <3C7FA79E.4C32CC1@blueyonder.co.uk>    JF Mezei wrote:d > 5 > is "supporting" older versions really that costly ?e > O > Does it really mean producing NEW patches ? How about revious version supportpK > where the product is considered mature but supported ? You have access toeH > telephone support as well as the inventory of existing patches, bit no0 > garantees that new patches would be produced ? > L > I am currious, Someone still at 5.5-2 for instance and paying for previousJ > version support. I realise that this means that Compaq must keep a 5-5-2E > machine somewhere to be able to support that customers. But from anuO > engineering point of view,  do such customers (who would be likely to be verysM > stable) ever require new patches to be written ? Or are they more likely toeN > buy support as insurance and to have someone answer questions when soemthing* > goes wrong and offer an existing patch ? > N > In other words, do customers who pay prior version support have a history ofL > finding NEW bugs, or just call because they have found an existing bug for  > which a patch already exists ?  L In my experience, if you are on a non supported version and have maintenanceK but no prior version support, support will help you diagnose the problem tooN the point where if it is a known problem they will point you to the patch, butR they will not escalate a new problem to engineering without prior version support.     -- w Tim.Llewellyn@cableinet.co.uk     C Standard disclaimer applies. My views in no way represent those of  ! my employers or service provider.n   ------------------------------  % Date: Fri, 01 Mar 2002 17:00:34 +0000 ( From: Nic Clews <sendspamhere@127.0.0.1>4 Subject: Re: Compaq adopts microsoft approach to VMS( Message-ID: <3C7FB3B2.35CE900@127.0.0.1>   "Main, Kerry" wrote: > @ > A good url to keep handy when these types of questions arise -9 > http://www.openvms.compaq.com/openvms/supportchart.htmlt   That is neat, up along withe  E http://www.openvms.compaq.com/openvms/os/openvms-release-history.html-  C Where is a link to the supportchart buried on the VMS page? I never  spotted it before.   -- m( Regards, Nic Clews CSC Computer Sciences nclews at csc dot com0   ------------------------------  % Date: Fri, 01 Mar 2002 13:12:45 -0500g- From: JF Mezei <jfmezei.spamnot@videotron.ca>i4 Subject: Re: Compaq adopts microsoft approach to VMS, Message-ID: <3C7FC49B.602D2AC2@videotron.ca>   Tim Llewellyn wrote:N > In my experience, if you are on a non supported version and have maintenanceM > but no prior version support, support will help you diagnose the problem toqP > the point where if it is a known problem they will point you to the patch, butT > they will not escalate a new problem to engineering without prior version support.    K But someone still on 5.5-2, what are the odds of them finding a *new* bug ?m  N If someone is still on 5.5-2, it is likely that they have a stabel system withL no new applications and running old versions of an application. Correct ? In+ that case, would they really find new bugs?t   ------------------------------  $ Date: Fri, 1 Mar 2002 10:11:25 +0100, From: "Bart Zorn" <B.Zorn@TrueBit.nospam.nl>! Subject: Re: copying system diskso* Message-ID: <a5ngn5$oc4$1@news1.xs4all.nl>  > "Keith Parris" <keithparris_NOSPAM@yahoo.com> wrote in message7 news:cf15391e.0202281306.5f0126cb@posting.google.com...rF > Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> wrote in message7 news:<01KET9GQMAMA8ZL57Q@sysdev.deutsche-boerse.com>...a  
     [ . . . ]   H > The biggest help I've found in maintaining multiple system disks is toE > move _off_ of the system disk, as much as possible, any files whichoF > can be placed on other disks -- especially any files that tend to be? > modified over time.  I recommend that even startup files like G > SYSTARTUP_VMS.COM on each system disk be simply a stub that calls the1D > "real" copy on a "cluster-common" disk (shadowed for reliability).H > (To do this, you do have to mount the cluster-common disk somewhere inD > startup; I like to do that in the stub SYLOGICALS.COM file on eachH > system disk, which, after mounting the cluster-common disk, then callsF > the "real" SYLOGICALS.COM from the common area.)  This way, there isF > only one copy of all the startup files for the entire cluster in one& > place, where it is easy to maintain.  
     [ . . . ].  A > --------------------------------------------------------------- A > Keith Parris | parris at encompasserve dot org | Consulting on: @ > Clusters, Disaster Tolerance, Performance, I/O, Storage & SANs  L *Shameless plug* At the Joint Conference in Lyon, I will be giving a session; about clusterwide logical names and I will give examples ofFC SYS$MANAGER:SYLOGICALS.COM and CLUSTER_COMMON:SYLOGICALS.COM, which3A implement Keith's advise above, using cluster wide logical names.   F BTW, I need a little bit of plugging, because both Stephen Hoffman and/ Yanick Pouffary are scheduled at the same time!a  % Regards, and hope to see you in Lyon!   	 Bart Zorn    ------------------------------  % Date: Fri, 01 Mar 2002 13:01:12 +0100n( From: Paul Sture <paul.sture@bluewin.ch>! Subject: Re: copying system disksa) Message-ID: <3C7F6D88.9060908@bluewin.ch>    Keith Parris wrote:   1 Nice summary Keith. I have only one thing to add.a    F > I also like to have the bare minimum in MODPARAMS.DAT (typically notB > much more than SCSNODE and SCSSYSTEMID) and use the AGEN$INCLUDED > capability to include the rest of the parameters from files on the > cluster-common disk. >  A good idea, I have separate AGEN$INCLUDE files for servers and workstations, so that SCSNODE and SCSSYSTEMID are (usually) the only entires required.    F However, VMS upgrades wreck this scheme by extracting parameters from F MODPARAMS.DAT and ALPHAVMSSYS.PAR and writing a new MODPARAMS.DAT, so I tidying them up is a standard post-upgrade task. I still have my pre and pA post V7.3 upgrade versions on disk here and see that the upgrade aB expanded MODPARAMS.DAT from 26 lines to 89, much of it duplicated.$ In particular, the new file has both   SCSSYSTEMID=55418    and later on    7 SCSSYSTEMID=(1024 * 54) + 122 ! which is what I prefer.     G Which reminds me, tidying up MODPARAMS.DAT after an upgrade is prudent tG even when not using the scheme outline above since sooner or later you rC (or one of your colleagues) are going to forget about the multiple  ? entries and only edit the first one, then be surprised why the t" modification does not take effect.    
 Paul Sture   SwitzerlandE   ------------------------------  + Date: Fri, 01 Mar 2002 15:42:33 +0100 (MET)s9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> ! Subject: Re: copying system diskst; Message-ID: <01KEUNGCTXCI8Y8HHB@sysdev.deutsche-boerse.com>a  @ > Once folks get beyond 2 or 3 system disks, this becomes a veryH > attractive option to many.  (For example, I know of someone who had anH > LAVC with 80 or so satellite nodes, each of which had their own system > disk!)  I Isn't the definition of a satellite something which doesn't have its own N system disk?    H > As another poster has pointed out, this is much easier if the "master"E > disk has a separate root for every node in the cluster (even thoughdH > you won't use all the roots on a given copy of the system disk).  ThisC > way, you don't have to change the nodename and network setup info H > every time you copy the disk; you just give each system its own uniqueF > root number, and set things up those things properly on the "master"H > disk just once: when you add a new node.  (If you were short on systemD > disk space, you _could_ delete the unused roots on each copy after> > copying the master system disk, but be careful to delete theG > SYSCOMMON.DIR file entries in those roots with $SET FILE/REMOVE first : > so you don't accidentally delete the common area, too!).  C This seems the way to go.  The only "duplicated" stuff would be in  F SYS$SPECIFIC, not SYS$COMMON, so wasted disk space won't be a problem.  E I've never used multiple roots except for satellites.  I suppose the oI thing to do is tell the machine which root to boot from, then everything   works as before?  H > The biggest help I've found in maintaining multiple system disks is toE > move _off_ of the system disk, as much as possible, any files which F > can be placed on other disks -- especially any files that tend to be? > modified over time.  I recommend that even startup files liketG > SYSTARTUP_VMS.COM on each system disk be simply a stub that calls the E > "real" copy on a "cluster-common" disk (shadowed for reliability).  H > (To do this, you do have to mount the cluster-common disk somewhere inD > startup; I like to do that in the stub SYLOGICALS.COM file on eachH > system disk, which, after mounting the cluster-common disk, then callsF > the "real" SYLOGICALS.COM from the common area.)  This way, there isF > only one copy of all the startup files for the entire cluster in one& > place, where it is easy to maintain.  E Yes, this was one of my points (4).  Multiple roots take care of the 4H more difficult problems (1 and 2 (network, node) and 5 (log files etc).  Autogen is trivial (3).   F > I also like to have the bare minimum in MODPARAMS.DAT (typically notB > much more than SCSNODE and SCSSYSTEMID) and use the AGEN$INCLUDED > capability to include the rest of the parameters from files on the > cluster-common disk.   Right, good idea.:  ? > Here's a list of files to re-direct to a cluster-common disk:F
 >  SYSUAF.DATc >  RIGHTSLIST.DATh! >  NETPROXY.DAT and NET$PROXY.DATu >  VMSMAIL_PROFILE.DATA  >  LMF$LICENSE.LDB >  NETOBJECT.DAT >  NETNODE_REMOTE.DAT = >  VMS$PASSWORD_HISTORY.DATA and VMS$PASSWORD_DICTIONARY.DATAs% >  SYLOGIN.COM (SYS$SYLOGIN: logical)  >  QMAN$MASTER: files G > and the security audit log file (see SYSECURITY.COM).  You might also C > consider OPC$LOGFILE_NAME: for OPERATOR.LOG and SYS$ERRORLOG: fornH > ERRLOG.SYS and ACCOUNTNG: for ACCOUNTNG.DAT files to move them off the > system disk.  # Are you sure this is 100% complete?   C > Here's a list of files to preserve and restore after you copy then > system disk:H >  ALPHAVMSSYS.PAR & ALPHAVMSSYS.OLD ((VAXVMSSYS.PAR & VAXVMSSYS.OLD for > VAXen) >  AGEN$FEEDBACK.DAT< >  MODPARAMS.DAT, PARAMS.DAT, SETPARAMS.DAT, AUTOGEN.PAR and > AGEN$PARAMS.REPORT >  VMSIMAGES.DAT  # Are you sure this is 100% complete?k  F I was planning to have a common disk for "personality" files anyway.  D The multiple roots take care of most of the other problems.  Thanks.   ------------------------------  + Date: Fri, 01 Mar 2002 15:46:07 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> ! Subject: Re: copying system disksa; Message-ID: <01KEUO2OIU6G8Y8HHB@sysdev.deutsche-boerse.com>A  4 > *Shameless plug* At the Joint Conference in Lyon,   B I'll be at the DECUS Symposium in Bonn.  (If any other comp.os.vmsH regulars would like to meet up with me there, send me email privately!)    > I will be giving aE > session about clusterwide logical names and I will give examples ofaE > SYS$MANAGER:SYLOGICALS.COM and CLUSTER_COMMON:SYLOGICALS.COM, whichlD > implement Keith's advise above, using cluster wide logical names.   E Interesting.  I started using cluster-wide logical names pretty soon  B after they came out, but for own stuff, not for "official" system 	 logicals.   H Now that these exist, are there plans to "support" cluster-wide logical D names for things which have traditionally been defined (to the same C thing) on all nodes or even to make this the default configuration?0   ------------------------------  % Date: Fri, 01 Mar 2002 15:35:10 +0000c( From: Nic Clews <sendspamhere@127.0.0.1>! Subject: Re: copying system disksn( Message-ID: <3C7F9FAE.5DF0404@127.0.0.1>   Phillip Helbig wrote:  > F > I've never used multiple roots except for satellites.  I suppose theJ > thing to do is tell the machine which root to boot from, then everything > works as before?  E As a point of interest I use multiple roots on my Alpha station, so Im8 can either boot it standalone or as part of the cluster.  D I have to maintain copies of usually cluster shared files for use inE standalone mode. The rest of the operating system and page / swap anduA dump files are 'shared' by each root, and they have root specific G logicals, but the startup is common, sections of it fail in one mode orw
 the other.   -- /( Regards, Nic Clews CSC Computer Sciences nclews at csc dot comu   ------------------------------   Date: 1 Mar 2002 09:23:57 -080041 From: keithparris_NOSPAM@yahoo.com (Keith Parris)q! Subject: Re: copying system disks-= Message-ID: <cf15391e.0203010923.3dac0c87@posting.google.com>c  | Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> wrote in message news:<01KEUNGCTXCI8Y8HHB@sysdev.deutsche-boerse.com>...K > Isn't the definition of a satellite something which doesn't have its own d > system disk?  , Yep.  I should have said "workstation node".  E > This seems the way to go.  The only "duplicated" stuff would be in -H > SYS$SPECIFIC, not SYS$COMMON, so wasted disk space won't be a problem.  : Except that even SYS$SPECIFIC: can contain some very largeD node-specific files like SYSDUMP.DMP, OPERATOR.LOG and ACCOUNTNG.DAT! after months of inattention, etc.   G > I've never used multiple roots except for satellites.  I suppose the aK > thing to do is tell the machine which root to boot from, then everything   > works as before?  B Right.  On Alpha, the root is the 1st argument in the BOOT_OSFLAGSD console environment variable.  On VAX, it's the high-order 4 bits of R5 as passed to VMB.EXE, IIRC.  A > > Here's a list of files to re-direct to a cluster-common disk:  ... % > Are you sure this is 100% complete?  ... E > > Here's a list of files to preserve and restore after you copy the  > > system disk  ... % > Are you sure this is 100% complete?   C The most-important files should all be there, but there may be somelA more-obscure files that aren't included.  And folks in this group < won't be shy if they notice I've missed something important.? --------------------------------------------------------------- ? Keith Parris | parris at encompasserve dot org | Consulting on: > Clusters, Disaster Tolerance, Performance, I/O, Storage & SANs   ------------------------------   Date: 1 MAR 2002 16:05:21 GMT|4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher)! Subject: Re: copying system diskso5 Message-ID: <1MAR02.16052174@thuria.waisman.wisc.edu>   Q In a previous article, Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> wrote:|   -> Keith Parris wrote:@ >> Here's a list of files to re-direct to a cluster-common disk: ->>  SYSUAF.DAT  ->>  RIGHTSLIST.DAT # ->>  NETPROXY.DAT and NET$PROXY.DATl ->>  VMSMAIL_PROFILE.DATA  ->>  LMF$LICENSE.LDB ->>  NETOBJECT.DAT ->>  NETNODE_REMOTE.DAT ? ->>  VMS$PASSWORD_HISTORY.DATA and VMS$PASSWORD_DICTIONARY.DATA ' ->>  SYLOGIN.COM (SYS$SYLOGIN: logical)  ->>  QMAN$MASTER: files I ->> and the security audit log file (see SYSECURITY.COM).  You might also E ->> consider OPC$LOGFILE_NAME: for OPERATOR.LOG and SYS$ERRORLOG: for J ->> ERRLOG.SYS and ACCOUNTNG: for ACCOUNTNG.DAT files to move them off the ->> system disk. ->  % ->Are you sure this is 100% complete?   ) Here's a more inclusive list of logicals:   E $! VMS common logicals. See sys$manager:sylogicals.template for info:  $  SYSUAF		 SYSUAFALT		/ SYSALF		 RIGHTSLIST		 LAN$NODE_DATABASE	
 LMF$LICENSE		  QMAN$MASTER 		 VMS$AUDIT_SERVER 	
 VMS$OBJECTS		  VMS$AUDIT_SERVER	  VMS$PASSWORD_HISTORY	0 VMS$PASSWORD_DICTIONARY	 VMS$PASSWORD_POLICY	 VMSMAIL_PROFILE	 $ ' $! Decnet Phase IV configuration files:  $  NET$PROXY		 
 NETPROXY		 NETOBJECT		| NETNODE_REMOTE	o NETLOGING		u NETNODE_UPDATE	  $ ) $! TCPIP configuration files/directories:  $  TCPIP$BIND_SERVER_DATA   TCPIP$DHCP_CONFIG	
 TCPIP$BOOTP		| TCPIP$CONFIGURATION	 TCPIP$EXPORT		 TCPIP$HOST		 TCPIP$NETWORK	
 TCPIP$PROXY		 
 TCPIP$ROUTE		  TCPIP$SERVICE	   --G -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison-2 --                      karcher@waisman.wisc.edu     ------------------------------  + Date: Fri, 01 Mar 2002 18:29:14 +0100 (MET):9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>A! Subject: Re: copying system disksF; Message-ID: <01KEUTRY8V1U8ZL57Q@sysdev.deutsche-boerse.com>h  G > > This seems the way to go.  The only "duplicated" stuff would be in eJ > > SYS$SPECIFIC, not SYS$COMMON, so wasted disk space won't be a problem. > < > Except that even SYS$SPECIFIC: can contain some very largeF > node-specific files like SYSDUMP.DMP, OPERATOR.LOG and ACCOUNTNG.DAT# > after months of inattention, etc.o  G Large, yes, but node-specific and thus worth keeping---or am I missing I
 something?   ------------------------------  $ Date: Fri, 1 Mar 2002 09:38:54 -0800, From: "James Gessling" <jgessling@yahoo.com>! Subject: Re: copying system disksu4 Message-ID: <a5oebg$8v9s4$1@ID-46415.news.dfncis.de>  > "Keith Parris" <keithparris_NOSPAM@yahoo.com> wrote in message7 news:cf15391e.0202281306.5f0126cb@posting.google.com...uF > Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> wrote in message7 news:<01KET9GQMAMA8ZL57Q@sysdev.deutsche-boerse.com>...o  . >.  (For example, I know of someone who had anH > LAVC with 80 or so satellite nodes, each of which had their own system > disk!) >n  J That was me!  And it worked (mostly) great.  These were vaxstation 4000's, soJ to upgrade, I made up a standard disk, in an external scsi enclosure.  The	 procedure K was to shutdown the workstation, cable up the standard disk to the external I scsi connector then boot off that disk.  Then login, and the script would- promptJ for nodename and decnet address.  The script would then do an image backupJ of the external disk to the internal one, and set the nodename, scsid etc. ShutdownJ and uncable the external disk and boot back off internal disk to complete.  K The one problem was this:  I had the operators doing this during the night,- I had7G a written procedure and had shown them how to do it.  I attached to thep	 procedure J a list of nodenames and decnet addresses for their reference. They ignored	 that listhL and just used the nodename and address given as an example in the procedure.  F You can image the cluster chaos that resulted as they worked their way throughhF the satellite nodes giving every one the same name and address!!  Even betterJ was the fact that when a node with a duplicate name is added to a cluster, the,L _other_ node with the same name crashes with a cluexit.  So they had no idea there:7 was any problem as each one they completed looked fine.   I Eventually, they realized somthing was wrong and called me.  Fortunately,  this wasG over a weekend, so I was able to go in and get things straightened out.s   Jim    ------------------------------  $ Date: Fri, 1 Mar 2002 09:41:29 -0800# From: "Tom Linden" <tom@kednos.com>t! Subject: RE: copying system diskss9 Message-ID: <CIEJLCMNHNNDLLOOGNJIOECFEEAA.tom@kednos.com>u  F Well, Jim, that is certainly not my idea of how to spend a weekend :->   > -----Original Message-----3 > From: James Gessling [mailto:jgessling@yahoo.com]s& > Sent: Friday, March 01, 2002 9:39 AM > To: Info-VAX@Mvb.Saic.Coma# > Subject: Re: copying system diskst >  >l >f@ > "Keith Parris" <keithparris_NOSPAM@yahoo.com> wrote in message9 > news:cf15391e.0202281306.5f0126cb@posting.google.com...oH > > Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> wrote in message9 > news:<01KET9GQMAMA8ZL57Q@sysdev.deutsche-boerse.com>...c > 0 > >.  (For example, I know of someone who had anJ > > LAVC with 80 or so satellite nodes, each of which had their own system
 > > disk!) > >a > L > That was me!  And it worked (mostly) great.  These were vaxstation 4000's, > soL > to upgrade, I made up a standard disk, in an external scsi enclosure.  The > proceduret@ > was to shutdown the workstation, cable up the standard disk to > the externalK > scsi connector then boot off that disk.  Then login, and the script would  > promptL > for nodename and decnet address.  The script would then do an image backupL > of the external disk to the internal one, and set the nodename, scsid etc.
 > ShutdownL > and uncable the external disk and boot back off internal disk to complete. >kB > The one problem was this:  I had the operators doing this during > the night, > I hadtI > a written procedure and had shown them how to do it.  I attached to them > procedurehL > a list of nodenames and decnet addresses for their reference. They ignored > that list C > and just used the nodename and address given as an example in the- > procedure. >-H > You can image the cluster chaos that resulted as they worked their way	 > throughgH > the satellite nodes giving every one the same name and address!!  Even > betterL > was the fact that when a node with a duplicate name is added to a cluster, > theuB > _other_ node with the same name crashes with a cluexit.  So they
 > had no ideaM > thereT9 > was any problem as each one they completed looked fine.a >eK > Eventually, they realized somthing was wrong and called me.  Fortunately, 
 > this wasI > over a weekend, so I was able to go in and get things straightened out.e >d > Jimh >  >s >y   ------------------------------  % Date: Fri, 01 Mar 2002 09:57:38 +00000% From: Alan Greig <a.greig@virgin.net>S' Subject: Re: decnet phase IV -> phase V:8 Message-ID: <qviu7ukk09skkd3tmaiigcsfro2gk37isf@4ax.com>  1 On Thu, 28 Feb 2002 13:45:27 -0800, Mark Berrymanh# <Mark.Berryman@Mvb.Saic.Com> wrote:     C >Part of the problem with this particular forum is that there are a F >handful of posters who appear to have a tremendous amount of time forI >posting here and they let their biases show through when doing so.  MostoD >of them do not like, or see no reason for, DECnet phase V and speak> >against it given any opportunity to do so.  So let me give an >alternative point of view:e   > H >Take the nay-sayers with a grain of salt.  It simply isn't as difficult >as they make it out to be..  D By all accounts DECNET Phase V is much more user friendly these daysD but some of us (and this is the case for me) first got involved withA DECNET Phase V way back in the days when it was called DECNET VAXfF Extensions. Experience with early Phase V implementation has certainlyA left me with a "don't touch with a barge pole" point of view as I22 dislike spending 48 hours on the phone to the CSC.  F That said, I have briefly played with current Phase V and it does seem7 so much more automated and straight forward these days.t  D Here's what Pete Carson of Phase V Engineering said (commenting on a" post of mine) back in January 1995  = From: carson@bulean.enet.dec.com (carson@bulean.enet.dec.com)e* Subject: Re: DECnet Phase IV vs DECnet OSI Newsgroups: comp.os.vms- View this article only Date: 1995-01-31 14:32:56 PSTm  * Alan Greig (ccdarg@zippy.dct.ac.uk) wrote:E >It was  this product, I think, which  severely damaged many people's8 >perceptions of DECnet OSI.c  @ You are not alone in your accessment of DECnet Extensions.  ThisC         supposedly limited release whose original intent to supporth new D         routers and allow customers begin populating DECdns names as partB         of their PhaseV migration has taken on a life of it's own. The B         evidence is in the fact that for the majority of the the 2 years =         you've been using this, the product has been retired.e  B         The good news for you is that the feedback you've given in yourC         note is the feedback we received from most of our customers 	 and whereeC         we have invested the majority of our efforts.  The NCL helpv that youD         dislike was discarded and redone.  The lengthy configuration wasoB         reduced to as little as five questions.  (A BASIC mode was addedoA         that defaults 95% of the questions that most people don'te         care about.)  F         As for the effort involved in 'relearning' DECnet from PhaseIV<         to PhaseV, we've also spent some effort here.   V6.0
 introducedB         the graphical Network Management tool.  This allows you toA         utilize point click technology to navigate the manageableY entities5         on your system without learning new commands.u  F         When investigating what people missed about NCP when migrating@         to NCL was the fact that NCP was very good at performingE         network tasks, which in fact may change or display attributesyD         across multiple layers.  For example, SHOW KNOWN LINKS shows?         information from both the Session Control and Transporta layers.tB         In response to this, we've begun adding Network Management TaskslB         to our Network Management tool, (for now this is available onlyC         for DecWindows users).  The first task added was SHOW KNOWNi LINKS C         and we've also added SHOW KNOWN NODE COUNTERS and SHOW KNOW  TRANSPORTS.;B         We have other tasks in the works and on the drawing board.  C         Just to clear up some of the licensing issues, there are no C         plans to remove the support for the PhaseIV code in V6.2 ofn OpenVMS.C         The routing function has never been officially supported one the C         AXP platform, but will still be supported in 6.2 of the VAX 	 platform.cF         DECnet/OSI, (which requires the same DECnet license), operates withE         PhaseIV routers and does not require setting up a DECdns namen space. -- R   Pete Carsonl" DECnet/OSI for OpenVMS Engineering Digital Equipment Corportation carson@bulean.enet.dec.com         >Mark Berryman >Mark.Berryman@Mvb.Saic.Coml   -- Alan   ------------------------------  % Date: Fri, 01 Mar 2002 11:47:11 +0100c( From: Paul Sture <paul.sture@bluewin.ch>' Subject: Re: decnet phase IV -> phase VR) Message-ID: <3C7F5C2F.3080704@bluewin.ch>L   John N. wrote:  7 > "Paul Sture" <paul.sture@bluewin.ch> wrote in message.% > news:3C7E04A3.6030203@bluewin.ch...  >  >>Jim Strehlow wrote:: >> >> >  > > H >>You will find various folks trying to persuade you not to use Phase V, >> > baseds > K >>on their initial experiences with it. It really isn't so bad once you getG >>
 >>used to it.  >>  C Apologies for the double spacing. Time to scan the bug Mozilla bug e- reports and add mine if not already there :-(f     >>K > The same can be said for creamed spinach or Unix or rape.  But why should&M > one go through the pain and agony of "getting used to it" unless there is aKH > pressing need.  For most people, phase IV will do the job reliably and	 > easily.O >   I Back in 1996 I would have agreed with you, and did indeed complain about  F it in that timeframe. Since then I believe it has improved greatly in A usability, although part of that sentiment is definitely down to - increased familiarity.  D The "pressing need" you refer to, was for some the possibility that C support for, and certainly enhancements to, Phase IV had a limited sH future. That and the possible need to run DECnet over TCP/IP were major   factors for my current employer.  E The transition went extremely smoothly, in total contrast to my 1996 s experiences with the product.p  
 Paul Sture Switzerlandi   ------------------------------  % Date: Fri, 01 Mar 2002 11:50:15 +0100 ( From: Paul Sture <paul.sture@bluewin.ch>' Subject: Re: decnet phase IV -> phase V:) Message-ID: <3C7F5CE7.1040506@bluewin.ch>    Bob Ceculski wrote:s   > > > big mistake to migrate to phase v ... big learning curve ... >   C Big learning curve for TCP/IP too, but you did that, didn't you :-)o  
 Paul Sture Switzerlanda   ------------------------------  % Date: Fri, 01 Mar 2002 12:30:44 +0100i( From: Paul Sture <paul.sture@bluewin.ch>' Subject: Re: decnet phase IV -> phase Vo) Message-ID: <3C7F6664.5040104@bluewin.ch>t   Dirk Munk wrote:   >  >  >  > Hear Hear !! > G > Very true. I've been using Phase V for some 10 years now., and it is .J > realy not so difficult. It follows the OSI  7-layer model, and that can H > be a blessing when you're searching for errors / problems. It is also I > faster, at least when I had the opportunity to test the speed of Phase c > IV and V a long time ago.r >i     Hear, hear too!?    D > And it is also easy to use DECnet over IP with Phase V, making it A > possible to use Copy to download freeware, instead of FTP.  ;-)e > & I've never tried that. How is it done?    
 Paul Sture Switzerlande   ------------------------------  % Date: Fri, 01 Mar 2002 12:51:18 -0500e- From: JF Mezei <jfmezei.spamnot@videotron.ca>i' Subject: Re: decnet phase IV -> phase V,, Message-ID: <3C7FBF95.E9B447FC@videotron.ca>   Alan Greig wrote:NF > By all accounts DECNET Phase V is much more user friendly these daysF > but some of us (and this is the case for me) first got involved withC > DECNET Phase V way back in the days when it was called DECNET VAX 
 > Extensions.1  L If had had seen a clear explanation of what files are executed in what orderI and where I was expected to add my commands to defeat some of the phase 5sJ defaults (for instance the commands to kill the messages about the missing< time servers), perhaps my experience might have been better.  I I dislike systems where you have to run a utility to figure out the exactsN syntax, and once you've done the command, you then go edit a file to enter the
 same command.    ------------------------------  % Date: Fri, 01 Mar 2002 13:03:57 -0500i- From: JF Mezei <jfmezei.spamnot@videotron.ca>G' Subject: Re: decnet phase IV -> phase V , Message-ID: <3C7FC28C.769B0D4A@videotron.ca>   Paul Sture wrote:eE > Big learning curve for TCP/IP too, but you did that, didn't you :-)   K TCPIP is not as easy as the single panel config on a MAC, granted.  But theeN experience of setting it to gives one marketable skills, whereas piddling with decnet-5 doesn't.   G But I have found that the TCPIP setup and the documentation make it faruI easier.  The help in TCPIP is more "natural" than in NCL, (perhaps due to L TCPIP having more familiar terminology).  And the printed documentation alsoE shows you the various options (mostly logical names you can define ina- systartup_VMS after having stated the stack).s  L I didn't "need" 5 but installed it to learn it. But it turned out to be moreM trouble that it was worth, especially the pesky DTSS messages I couldn't seem-L to permanently get to go away. I tried to install it also in my microvaxx IIL but then realised the darned thing needed 80,000 blocks to give me set host,J copy and decnet objects, all of which were far simpler with decnet 4 which took far fewer resources.a  L If this had been a requirement, I would have then spent the time to read theM books cover to cover a few times and played around on a test system to find aHI working configuration and then put that in production. But without such a:M need, spending time to fiddle with decnet-5 yeiels far less marketable skills.& than spending time working with TCPIP.   ------------------------------   Date: 1 Mar 2002 10:19:50 -0500E/ From: brooks@cuebid.zko.dec.nospam (Rob Brooks)  Subject: Re: DTE Unsynchroniseda- Message-ID: <hR$fzfkAKu3q@cuebid.zko.dec.com>C  7 pat.saunders@sis.securicor.co.uk (pat saunders) writes:n > Hi,e( >   I am using DECNET/OSI on a MicroVax,H 	I'm sorry to hear that :-)  (I like DECnet/OSI, but it tends to consume% most of the cycles on a MicroVAX II).C  & >   I am using a LAPB circuit on DTE-0F >   When I look at state of DTE , I find it is "Unsynchronised" , What2 > is the cause of this message and how do I fix it  I What kind of hardware are you using for the synchronous connection?  BackYH in the late 80's with the old VAX PSI product, I frequently had to "kickJ start" the KMV-11 by having it reload its microcode.  I don't remember theB syntax in NCP; if you have similar hardware, perhaps Antonio could chime in . . .  O As a previous reply stated, this message means that you don't have a connection	& between your system and the other end.   --  M Rob Brooks    VMS Engineering -- I/O Exec Group     brooks!cuebid.zko.dec.comD   ------------------------------  $ Date: Fri, 1 Mar 2002 18:20:14 +0800 From: elist365@sohu.comT2 Subject: Earn a dime every time you receive email!" Message-ID: <5047560@MVB.SAIC.COM>   <html>   <head>   </head>W   <body>   <p><a href="http://www.MintMail.com/?m=2262141" target="_blank"><img border="0" src="https://www.mintmail.com/Banners/Banner33.gif" width="218" height="70"></a></p>  M <p><font face="Arial,Helvetica,Geneva,Swiss,SunSans-Regular" size="3">Earn a e& dime every time you receive email!<br>h Sign up FREE at: <b><a href="http://www.MintMail.com/?m=2262141" target="_blank">Here</a></b></font></p>   </body>    </html> %<p></p><p align="center">===============================================================<br>ʼʹ ʼȺ ,ʼ޹<br> <a href="http://www.caretop.com"> http://www.caretop.com</a><br>===============================================================</p>o   ------------------------------  " Date: Fri, 1 Mar 2002 15:23:14 GMT' From: alexc@world.std.com (Alex Colvin)l& Subject: Re: expensive procedure calls' Message-ID: <GsAw2q.z2s9@world.std.com>D  E >The difference between SSA-form and continuation-passing-style (i.e.rD >using tail-calls only) is mostly limited to notational differences,  6 I thought SSA was all about intra-procedure data flow, not inter-procedural.<     -- A
 	mac the naf.   ------------------------------  # Date: Fri, 01 Mar 2002 16:32:06 GMTn# From: "John Smith" <a@nonymous.com>s+ Subject: Hewlett releases committee minutes)/ Message-ID: <a2Of8.3132$635.563@news1.bloor.is>t  " Hewlett releases committee minutes 338g 02/28/02 06:05 PMt Source: News.com URL:J http://investor.cnet.com/investor/news/newsitem/0-9900-1028-8944581-0.html  K Walter Hewlett, in his latest salvo, on Thursday released copies of minutes H from a Hewlett-Packard board committee meeting to prove that his earlierE comments about compensation packages for HP and Compaq Computer chiefh' executives were not misrepresentations.iL Hewlett, an HP director who opposes the $22 billion mega-merger with Compaq,E released copies of minutes from a September meeting of the HP board'stA compensation committee. Hewlett sits on the committee, along withh< co-directors and committee members Sam Ginn and Phil Condit.  H With the stakes for wooing shareholders increasing with each passing dayG leading up to the March 19 vote for HP investors, both camps are takingrK greater measures to make their cases clear. Hewlett, in releasing copies of B board-related minutes, may be pushing the envelope, some corporate governance experts say.   F "It's highly inappropriate and I would assume the information would beH proprietary," said David Vogel, professor of business ethics at the Haas? School of Business at the University of California at Berkeley.   E Hewlett, however, believes he is defending his honor by providing ther
 documents.  D Hewlett is referring to comments he and his advisers made Wednesday,I regarding a combined $115 million compensation package that initially was0L supported by the compensation committee for HP Chief Executive Carly FiorinaJ and Compaq CEO Michael Capellas. The issue centered on shareholders havingK this information before the vote and the potential conflict of interest the-G CEOs may encounter in wanting to pass the deal to collect lucrative payc	 packages.t  L Hewlett's contention was that the executives' declining a combined retentionJ bonus of $22.4 million was a drop in the bucket compared with the packages they could reap.  L "HP has recently made statements that we are 'fabricating information solelyH in an effort to gain votes,'" Hewlett said in a statement. "HP's outsideJ legal counsel has said that Capellas and Fiorina have merely 'floated some( general terms for future pay packages.'"  L Hewlett noted in his earlier statement and in copies of the minutes that theG compensation committee--including Hewlett--had supported the employment') agreements for both Fiorina and Capellas.d  F During a Sept. 20 compensation committee meeting to consider Fiorina'sI package, the minutes stated: "The committee reviewed possible performancenJ metrics for the stock options. It was generally agreed that vesting shouldL be tied to stock price growth in defined time periods and that value driversB associated with the deal would be an appropriate secondary metric.K Discussion ensued regarding what share price growth should trigger vesting.e  J "To provide context for the discussion, Ginn recapped discussions over theD last several weeks regarding the structure of the options, which areJ expected to be granted at the close of the merger," the minutes continued.L "Following extensive discussion, the committee developed a framework for the# (vesting schedule of the) options."e  G According to the minutes, as well as to previous comments from Hewlett,eJ after the compensation committee meeting adjourned, the committee had "notF agreed on the exercise price for the options, specifically whether theJ performance-based blocks would be priced at (fair market value) or premiumL prices. It was subsequently determined that the committee had not reached anF agreement on the pricing terms of the option component of the package.K Accordingly, all components of the package, which are interrelated, will beF" reconsidered at a future meeting."  K Hewlett, however, previously said he was not aware the committee had tabled I the issue until receiving a copy of the Sept. 20 minutes. He indicated he3F initially thought the matter had been resolved, which would then allowE shareholders to receive the information when HP had issued its proxy..  J HP's compensation committee directors were fuming with the latest round of attacks and counterattacks.   K In a letter sent to Hewlett, Ginn and Condit wrote: "We are stunned by yourtJ blatant mischaracterizations of the actions of the committee. As you know,G Walter, the three of us all unanimously agreed at our last compensationiK committee meeting that the executive employment terms previously discussed,oK including discussions at our prior meetings in September, were specificallykK rejected and that these terms would not serve as benchmark or minimum termsy= for any future employment arrangements following the merger."m  H They further added that the three-member committee concluded it would beK best to have the board of the newly combined company decide the appropriated? compensation terms for the executive officers after the merger.a  I And in a parting shot, Ginn and Condit noted: "You know that in order foriG our committee and the board to function properly, we must freely debate,D proposed strategies and ideas in our meetings. Yet you have put yourF personal agenda in front of the interests of HP and our shareholders."   ------------------------------  $ Date: Fri, 1 Mar 2002 08:39:22 -0800# From: "Tom Linden" <tom@kednos.com>t/ Subject: RE: Hewlett releases committee minutesR9 Message-ID: <CIEJLCMNHNNDLLOOGNJIGECDEEAA.tom@kednos.com>   + I wonder what is in it for Condit and Ginn.5   > -----Original Message-----* > From: John Smith [mailto:a@nonymous.com]& > Sent: Friday, March 01, 2002 8:32 AM > To: Info-VAX@Mvb.Saic.Comn- > Subject: Hewlett releases committee minutest >  >n$ > Hewlett releases committee minutes > 338t > 02/28/02 06:05 PMi > Source: News.com > URL:L > http://investor.cnet.com/investor/news/newsitem/0-9900-1028-8944581-0.html > B > Walter Hewlett, in his latest salvo, on Thursday released copies > of minutesJ > from a Hewlett-Packard board committee meeting to prove that his earlierG > comments about compensation packages for HP and Compaq Computer chiefw) > executives were not misrepresentations. A > Hewlett, an HP director who opposes the $22 billion mega-merger  > with Compaq,G > released copies of minutes from a September meeting of the HP board'slC > compensation committee. Hewlett sits on the committee, along withc> > co-directors and committee members Sam Ginn and Phil Condit. > J > With the stakes for wooing shareholders increasing with each passing dayI > leading up to the March 19 vote for HP investors, both camps are takingvC > greater measures to make their cases clear. Hewlett, in releasing  > copies offD > board-related minutes, may be pushing the envelope, some corporate > governance experts say.  > H > "It's highly inappropriate and I would assume the information would beJ > proprietary," said David Vogel, professor of business ethics at the HaasA > School of Business at the University of California at Berkeley.L >sG > Hewlett, however, believes he is defending his honor by providing thei > documents. >aF > Hewlett is referring to comments he and his advisers made Wednesday,K > regarding a combined $115 million compensation package that initially wasn@ > supported by the compensation committee for HP Chief Executive > Carly FiorinaaL > and Compaq CEO Michael Capellas. The issue centered on shareholders having@ > this information before the vote and the potential conflict of > interest theI > CEOs may encounter in wanting to pass the deal to collect lucrative pay  > packages.; > ; > Hewlett's contention was that the executives' declining ar > combined retentionL > bonus of $22.4 million was a drop in the bucket compared with the packages > they could reap. >s; > "HP has recently made statements that we are 'fabricatingh > information solelyJ > in an effort to gain votes,'" Hewlett said in a statement. "HP's outsideL > legal counsel has said that Capellas and Fiorina have merely 'floated some* > general terms for future pay packages.'" >o= > Hewlett noted in his earlier statement and in copies of the- > minutes that theI > compensation committee--including Hewlett--had supported the employmentb+ > agreements for both Fiorina and Capellas.M >.H > During a Sept. 20 compensation committee meeting to consider Fiorina'sK > package, the minutes stated: "The committee reviewed possible performance>L > metrics for the stock options. It was generally agreed that vesting should@ > be tied to stock price growth in defined time periods and that > value driversgD > associated with the deal would be an appropriate secondary metric.< > Discussion ensued regarding what share price growth should > trigger vesting. >hL > "To provide context for the discussion, Ginn recapped discussions over theF > last several weeks regarding the structure of the options, which areL > expected to be granted at the close of the merger," the minutes continued.< > "Following extensive discussion, the committee developed a > framework for thea% > (vesting schedule of the) options."t >pI > According to the minutes, as well as to previous comments from Hewlett, L > after the compensation committee meeting adjourned, the committee had "notH > agreed on the exercise price for the options, specifically whether theL > performance-based blocks would be priced at (fair market value) or premiumC > prices. It was subsequently determined that the committee had not  > reached anH > agreement on the pricing terms of the option component of the package.7 > Accordingly, all components of the package, which arel > interrelated, will bed$ > reconsidered at a future meeting." >/B > Hewlett, however, previously said he was not aware the committee > had tabledK > the issue until receiving a copy of the Sept. 20 minutes. He indicated heaH > initially thought the matter had been resolved, which would then allowG > shareholders to receive the information when HP had issued its proxy.c >RL > HP's compensation committee directors were fuming with the latest round of > attacks and counterattacks.i >i= > In a letter sent to Hewlett, Ginn and Condit wrote: "We arei > stunned by yourrL > blatant mischaracterizations of the actions of the committee. As you know,I > Walter, the three of us all unanimously agreed at our last compensationrB > committee meeting that the executive employment terms previously > discussed,@ > including discussions at our prior meetings in September, were > specifically? > rejected and that these terms would not serve as benchmark ory > minimum terms ? > for any future employment arrangements following the merger.", >dJ > They further added that the three-member committee concluded it would beA > best to have the board of the newly combined company decide the 
 > appropriatecA > compensation terms for the executive officers after the merger.  >iK > And in a parting shot, Ginn and Condit noted: "You know that in order for I > our committee and the board to function properly, we must freely debate.F > proposed strategies and ideas in our meetings. Yet you have put yourH > personal agenda in front of the interests of HP and our shareholders." >p >o >i >t >. >i   ------------------------------   Date: 1 Mar 2002 11:59:22 -06004+ From: young_r@encompasserve.org (Rob Young)y/ Subject: RE: Hewlett releases committee minutesi3 Message-ID: <Yp5v+J862KJf@eisner.encompasserve.org>a  _ In article <CIEJLCMNHNNDLLOOGNJIGECDEEAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes: - > I wonder what is in it for Condit and Ginn.  >   # 	Brand new shiny black helicopters.h   			Rob   ------------------------------  % Date: Fri, 01 Mar 2002 10:24:51 +0000 % From: Alan Greig <a.greig@virgin.net>kD Subject: Re: HP & Compaq high-end systems to "stay around for years"8 Message-ID: <oklu7uo29utoo1r6t29khr8hgni72jqk83@4ax.com>  B On 28 Feb 2002 19:22:27 -0800, VMSfan@hotmail.com (VMS Fan) wrote:   t theeE >company will continue to make both Compaq and HP high-end enterprise-G >systems that are already in customer use available for some time. "The 5 >big equipment will stay around for years," he said.'d  ? I think I'm more worried after reading that than I was before. n   >---. >"Rumors of my death are greatly exacerbated."" >                           -- VMS   -- Alan   ------------------------------  % Date: Fri, 01 Mar 2002 10:47:59 +0100 ( From: Paul Sture <paul.sture@bluewin.ch>( Subject: Re: I: PAKGEN Software for ISVs) Message-ID: <3C7F4E4F.1040900@bluewin.ch>   / In article <cVzC8K+49bsV@tachxxsoftxxconsult>, i? wayne@tachysoft.xxx.120519.killspam.00c7 (Wayne Sewell) writes:e  ?  > In article <3C7DA1D7.B9A63756@fsi.net>, "David J. Dachtera" u <djesys.nospam@fsi.net> writes:i    L  >> I've worked in shops where non-LMF software (other license methods) were
  >> verboten.)  >>     >I  > Really?  What's the reasoning on that?  Too much trouble dealing with u	 alternate   > key formats?a  E It makes sense given the weird variety of protection mechanisms I've aF seen over the years. One company I used to deal with deliberately set H out to crack competititors' licensing mechanisms to learn how NOT to do G it, and usually a simple PATCH was all that was required.The mechanism rD they devised for their own products was sophisticated, but could be 2 circumvented if you knew how the designer thought.  B One of the more devious licensing mechanisms I have seen involved @ something hidden in a file header, which caused immense pain on G occasions by announcing the license dead when it should not have been, nG forcing me to reach for my backup tapes. Certain changes in the TCP/IP aD configuration required the issue of a new license, somewhat (cough) C inconvenient when you are doing reconfiguration in holiday periods.3  C I am putting forward a request to use PAKGEN to the software house s* responsible for this product forthwith :-)  
 Paul Sture Switzerlandy   ------------------------------   Date: 1 Mar 2002 09:19:25 GMTt( From: nmm1@cus.cam.ac.uk (Nick Maclaren) Subject: Re: Itanium troublesE0 Message-ID: <a5nh2t$5v6$1@pegasus.csx.cam.ac.uk>  / In article <3C7F0AE5.6090309@brussels.sgi.com>,s, Alexis Cousein  <al@brussels.sgi.com> wrote: >JF Mezei wrote:P >> Why would someone buy SGI ? becayuse the software they need only runs on SGI. >,E >The vast majority of *new* customers for SGI servers (last I looked,iF >50%+ of revenue) are running applications that run on other platforms* >too, so that can't be the only reason ;).  E It isn't.  Speaking from experience, the Origin/MIPS/IRIX solution isnE a pretty good one, and far more competitive than appears if you just  D look at Specmarks (when it isn't).  For example, it needs a lot less+ support effort than many other competitors.M  ? And a lot of this is that the architecture does not stop at theiB performance of the chip.  I would not say that I regard everythingB as either fully integrated or well designed, but it is pretty good> by the standards of the competition.  Whether you regard it as- better or worse will depend on your criteria.i   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: Fri, 1 Mar 2002 10:54:41 +01005 From: "Tarjei T. Jensen" <tarjei.jensen@kvaerner.com>= Subject: Re: Itanium troubles=+ Message-ID: <a5nj59$8r29@news.kvaerner.com>   "Nick Maclaren"G > It isn't.  Speaking from experience, the Origin/MIPS/IRIX solution is=F > a pretty good one, and far more competitive than appears if you justF > look at Specmarks (when it isn't).  For example, it needs a lot less- > support effort than many other competitors.R  I We are very pleased with SGI and Irix and the Origin 300 is our preferrede Unix server for the time being.c  F Two items stand out: the point release system of patching and xlv/xfs.  L If I ever have to do a disaster recovery I desperately wish it would be on aH SGI machine. All the other I have seen to date suck big time compared to Irix with xlv.  
 Greetings,   ------------------------------  # Date: Fri, 01 Mar 2002 13:58:08 GMT:2 From: "George N. White III" <WhiteG@dfo-mpo.gc.ca> Subject: Re: Itanium troublessJ Message-ID: <Pine.SGI.4.44.0203010955190.246107-100000@wendigo.bio.dfo.ca>  ) On Fri, 1 Mar 2002, Alexis Cousein wrote:s   > JF Mezei wrote:9Q > > Why would someone buy SGI ? becayuse the software they need only runs on SGI.  >iF > The vast majority of *new* customers for SGI servers (last I looked,G > 50%+ of revenue) are running applications that run on other platformsC+ > too, so that can't be the only reason ;).e  A How many of these SGI customers had Sun as their first choice butmD bought SGI because they could get earlier delivery or better prices?   --D George N. White III <gnw3@acm.org> Bedford Institute of Oceanography   ------------------------------  # Date: Fri, 01 Mar 2002 16:17:36 GMT.4 From: Tim Llewellyn <tim.llewellyn@blueyonder.co.uk> Subject: Re: Itanium troubles 0 Message-ID: <3C7FA870.13280E96@blueyonder.co.uk>   JF Mezei wrote:a >  > Christopher Smith wrote:M > > something that supported it already.  The average idiot will not know the L > > difference between 64 bit windows on a 64 bit cpu, and 32 bit windows on > > a 64 bit cpu > N > Ever seen what the current games are like on PCs ? Guess who drives the home > computer market ?s > H > Young boys who absolutely need that new game and a high speed internetN > connection to be able to play "live" against friends, and who complain about* > slow pings that make the game go slower. > O > If a 64 bit machine with a 64 bit 3d video rendering card makes new much morenN > sophisticated games possible, it will take just a year or two before parentsL > crumble under pressure from their teenage mutant boys and buy a 64 bit PC.  N are games stressing the limitations of a 32 bit processor at present of in the forseeable future?   --   Tim.Llewellyn@cableinet.co.uk  c  C Standard disclaimer applies. My views in no way represent those of t! my employers or service provider.n   ------------------------------  $ Date: Fri, 1 Mar 2002 12:48:23 -0500; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com> 4 Subject: Re: Microsoft Curries Favor With Undergrads$ Message-ID: <3c7fbf31$1@news.si.com>  F >   Microsoft on Thursday released software development tools aimed atE >   college-level computer science students, hoping it will produce alD >   fresh crop of software programmers loyal to its Windows and .Net >   technology.c  9 At one time, Digital knew this.  Compaq just says, "Huh?"g -- nA Brian Tillman                   Internet: tillman_brian at si.comnA Smiths Aerospace                          tillman at swdev.si.come= 3290 Patterson Ave. SE, MS      Addresses modified to preventh< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  # Date: Fri, 01 Mar 2002 17:45:44 GMTn4 From: Tim Llewellyn <tim.llewellyn@blueyonder.co.uk> Subject: Re: No route to host?0 Message-ID: <3C7FBD1A.4FF97C59@blueyonder.co.uk>   JF Mezei wrote:i >  > Michael Austin wrote:e > >gL > > The default gateway needs to be the IP of the box itself. Since there is > > no router... > N > Nop. the default gateway is the router that gets you off your subnet. If youG > do not have a router in house, then you have to tell VMS to route anyoZ > connectiosn not destined for your house to the router supplied by the ISP (eg: gateway). > ; > SET ROUTE/DEFAULT/GATEWAY=isp.supplied.ip.address 0.0.0.0i > O > I do not kow how they implemented the VMS DHCP client, but normally, the DHCP P > client should handle not only the IP address, but also default gateway and DNS > server adresses. > P > I bought a router that does all that for me and allows my lan to remain staticM > and not be bothered by my ISP. The only dependancy I have on the ISP is theFI > definition in my local bind server to forward non local requests to thee4 > specific IP adresses of DNS servers my ISP offers. > : > My default gateway is the local ip address of my router.  B Yup, thats the way it works for me with my Linksys router and DSL.B Router gets DNS and DSL gateway info from DHCP, and passes the DNS info onto its own DHCP clients.e  E Of course, I only have windows boxes connected right now but there iscB hope, I have a MicroVAX 2000 of unknown operability in the house!    --   Tim.Llewellyn@cableinet.co.uk  t  C Standard disclaimer applies. My views in no way represent those of f! my employers or service provider.a   ------------------------------  % Date: Fri, 01 Mar 2002 10:07:12 +0000v% From: Alan Greig <a.greig@virgin.net>nN Subject: Re: OpenVMS get together in Houston - thought you might be interested8 Message-ID: <4cku7ug489cil7dkek369u0u2mh54hg99h@4ax.com>  3 On Thu, 28 Feb 2002 10:29:41 -0500, "Sue Skonetski"e# <susan.skonetski@compaq.com> wrote:h  ) >Compaq, PointSecure and Pioneer Standarde. >invite you to join us for a reintroduction to >the Houston OpenVMS community.n >i >When: Wednesday March 13thf >From 5:30 PM - 7:30 PM   C Hey, I'm over from the UK in Dallas that week. Never having been to B Texas before can anyone tell me if it would be feasible to catch aE flight if I'm free in Dallas by about 4? How far apart are Dallas and  Houston?    , >Where: Benjy's Restaurant - in Rice Village >(713) 522-7602s >2424 Dunstan Rd.-    ! How close to the airport is this?0 >8; >Why: Informal event to meet other local VMS users, discussR6 >VMS and Compaq's plans, hear a presentation from John= >Wisniewski and, of course, enjoy free drinks and appetizers.i >t >Agenda: 5:30 PM - 6: 15 PM- >Arrival and greetings >  >6: 15 PM - 6: 45 PM" >Presentation from Leland Bolleter >and John Wisniewski of Compaq >-Discuss plans for OpenVMSc >-Security and OpenVMS >e >6: 45 PM - 7:30 PM  >Mingle with community members >Wrap up >  >Please RSVP by March 8the >e= >To RSVP please send an email to mike.umansky@pointsecure.comeL ><mailto:%20mike.umansky@pointsecure.com> and write in the subject line will >attend or will not attend.m >t0 >We look forward to seeing you all on March 13th >t >r   -- Alan   ------------------------------   Date: 1 Mar 2002 06:23:56 -0800m; From: jnchambl@texaschildrenshospital.org (Jesse Chambless)eN Subject: Re: OpenVMS get together in Houston - thought you might be interested= Message-ID: <d92c63cc.0203010623.1a2f28a5@posting.google.com>   E Dallas to Houston...199 miles ( sorry don't know how many Km )  Aboutw? 1 hr in an airplane and about 1 hour from Bush Intercontential.i  D You would want to leave Dallas by about 3 PM to give yourself plenty of time.  B The other option is to fly into Hobby airport.  From there to Rice! village is about 30 - 40 minutes.t  e Alan Greig <a.greig@virgin.net> wrote in message news:<4cku7ug489cil7dkek369u0u2mh54hg99h@4ax.com>...o5 > On Thu, 28 Feb 2002 10:29:41 -0500, "Sue Skonetski"I% > <susan.skonetski@compaq.com> wrote:s > + > >Compaq, PointSecure and Pioneer Standardd0 > >invite you to join us for a reintroduction to! > >the Houston OpenVMS community.n > >i > >When: Wednesday March 13th  > >From 5:30 PM - 7:30 PMi > E > Hey, I'm over from the UK in Dallas that week. Never having been totD > Texas before can anyone tell me if it would be feasible to catch aG > flight if I'm free in Dallas by about 4? How far apart are Dallas and 
 > Houston? >  > . > >Where: Benjy's Restaurant - in Rice Village > >(713) 522-7602  > >2424 Dunstan Rd.p >  > # > How close to the airport is this?i > > = > >Why: Informal event to meet other local VMS users, discuss 8 > >VMS and Compaq's plans, hear a presentation from John? > >Wisniewski and, of course, enjoy free drinks and appetizers.o > >i > >Agenda: 5:30 PM - 6: 15 PMl > >Arrival and greetings > >  > >6: 15 PM - 6: 45 PM$ > >Presentation from Leland Bolleter  > >and John Wisniewski of Compaq > >-Discuss plans for OpenVMSt > >-Security and OpenVMS > >n > >6: 45 PM - 7:30 PMy  > >Mingle with community members
 > >Wrap up > >  > >Please RSVP by March 8the > >o? > >To RSVP please send an email to mike.umansky@pointsecure.comeN > ><mailto:%20mike.umansky@pointsecure.com> and write in the subject line will > >attend or will not attend.- > >i2 > >We look forward to seeing you all on March 13th > >t > >d   ------------------------------  % Date: Fri, 01 Mar 2002 15:04:57 +0000.% From: Alan Greig <a.greig@virgin.net>iN Subject: Re: OpenVMS get together in Houston - thought you might be interested8 Message-ID: <6r4v7usjrq8ke06joqobpuqg19gteatuf6@4ax.com>  A On 1 Mar 2002 06:23:56 -0800, jnchambl@texaschildrenshospital.orgo (Jesse Chambless) wrote:  F >Dallas to Houston...199 miles ( sorry don't know how many Km )  About@ >1 hr in an airplane and about 1 hour from Bush Intercontential. >hE >You would want to leave Dallas by about 3 PM to give yourself plentyt	 >of time.  >cC >The other option is to fly into Hobby airport.  From there to Ricer" >village is about 30 - 40 minutes.  E Thanks to yourself and others via email. I am in Dallas for two weekse> (work not vacation) but may be able to free up that afternoon.  C >20mike.umansky@pointsecure.com> and write in the subject line willt >> >attend or will not attend. >> >3 >> >We look forward to seeing you all on March 13thh >> > >> >   -- Alan   ------------------------------  % Date: Fri, 01 Mar 2002 14:14:28 +0100f( From: Paul Sture <paul.sture@bluewin.ch>& Subject: Re: proliant 1600 not booting) Message-ID: <3C7F7EB4.7040908@bluewin.ch>c   Mart wrote:e  G > I have a compaq proliant 1600 and when the server powers up but, getsnF > to the bios, then quits when it goes to recognize the PIII, it says,* > "Unsupported Processor detected. Systems8 > halted". From then nothing happen, I can`t do anything > > > I need to boot the system, any help would be appreciated.... > 7 Wrong newsgroup. Try alt.sys.pc-clone.compaq for adviceo   ------------------------------   Date: 1 Mar 2002 03:10:15 -0800t From: sam@ratex.dk (Sam) Subject: QUORUM disk questione; Message-ID: <d1111de.0203010310.8d70f78@posting.google.com>   	 Hi Folks.m  ? Is it possible to use the HSG80 $1$GGAxxx device as QUORUM disk * or must the QUOrum disk really be a disk ?     Samt   ------------------------------  # Date: Fri, 01 Mar 2002 12:33:42 GMTn1 From: "Kari Keronen" <kari.keronen@radiolinja.fi>t! Subject: Re: QUORUM disk questione5 Message-ID: <GyKf8.11125$zZ5.230491@news.kpnqwest.fi>r  F $1$GGAxxx device is only for connect to HSG80 via Command Console LUN.: Quorum disk must be a system disk or some other real disk.   -Kari-  % "Sam" <sam@ratex.dk> wrote in message 5 news:d1111de.0203010310.8d70f78@posting.google.com...  > Hi Folks.  > A > Is it possible to use the HSG80 $1$GGAxxx device as QUORUM diskf, > or must the QUOrum disk really be a disk ? >l >d > Saml   ------------------------------  # Date: Fri, 01 Mar 2002 14:33:34 GMT 1 From: "Mark D. Jilson" <jilly@clarityconnect.com>i! Subject: Re: QUORUM disk question 2 Message-ID: <3C7F917D.C94479B2@clarityconnect.com>  H To further expand, the quorum disk may be any disk that is not part of aB host-based set like host-based shadowing or striping or RAID.  The* quorum disk may be a controller-based set.   Kari Keronen wrote:e > H > $1$GGAxxx device is only for connect to HSG80 via Command Console LUN.< > Quorum disk must be a system disk or some other real disk. >  > -Kari- > ' > "Sam" <sam@ratex.dk> wrote in messagel7 > news:d1111de.0203010310.8d70f78@posting.google.com...r
 > > Hi Folks.o > > C > > Is it possible to use the HSG80 $1$GGAxxx device as QUORUM diske. > > or must the QUOrum disk really be a disk ? > >t > >C > > Sam    --  D Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------  + Date: Fri, 01 Mar 2002 15:22:52 +0100 (MET)>9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>F( Subject: Re: restricting access to ports; Message-ID: <01KEUN12O6P28Y8HHB@sysdev.deutsche-boerse.com>t  H > This shouldn't be necessary.  When the ISP blocks incoming connectionsF > on all ports except some very limited subset that you have chosen toH > allow, they are not filtering out *ALL* packets to those ports on yourG > system, only those that have (or don't have) a certain bit set in the-D > packet header that says "this is a new connect request".  When youG > initiate a connection to a specific port on a remote host, the TCP/IPrF > stack assigns you a random available port number for your end of theG > connection.  (The port number is how it keeps track of connections so0E > it knows which application, i.e. which BG: or TCP: device gets this,B > particular packet.)  The ISP should *NOT* be filtering out theseI > packets on the established connections, only the packets for externally  > initiated new connections.  H Unfortunately, I think the ISP IS filtering out everything.  Never mind H FTP and SMTP, which are a bit trickier; I couldn't even TELNET out when G this filter was in place, but could as soon as he took the filter down i again.  F If it's any help, here's the filter the ISP had (which is now removed 4 until I can tell him EXACTLY what he should filter):   echo "     helbig_filter"m* iptables -N helbig_filter > /dev/null 2>&1 iptables -F helbig_filter 9 iptables -A helbig_filter -p tcp --dport 8000   -j ACCEPT 9 iptables -A helbig_filter -p tcp --dport 20:21  -j ACCEPTe9 iptables -A helbig_filter -p tcp --dport 23     -j ACCEPT 9 iptables -A helbig_filter -p tcp --dport 443    -j ACCEPTs9 iptables -A helbig_filter -p tcp --dport 25     -j ACCEPTa9 iptables -A helbig_filter -p tcp --dport 110    -j ACCEPTd7 iptables -A helbig_filter -p ICMP               -j DROPe! iptables -A helbig_filter -j DROPo  H > So sending from a random port to a remote SMTP server (and getting itsH > responses) or reading mail from a remote POP3 server should work fine.  B I receive mail locally with VMS mail.  Telnet, FTP, SMTP (sending G something with VMS MAIL), HTTP connections couldn't get out.  (Well, I aE suppose technically they got out, but I got no response.  :-(  )  As a6 soon as he took down the filter, all worked as before.  I Unfortunately, I can't really demand too much of the ISP (and don't have yF any alternative, so I am stuck with him for now).  All the evidence I A have is that his filter is not intelligent, so for now I have no  E alternative but to continue on that assumption, which means the best  D strategy would be to block certain ports and allow everything else,  rather than vice versa.I  B > As far as totally restricting all but a small set of ports, thisA > would only work if you can tell your TCP/IP stack to only issueiA > ports in that range.  I don't think you can do that with either @ > TCPWare (which I use a lot) or UCX/Compaq TCP/IP, which I have; > on a couple of systems, but am much less familiar with.  t  H As far as I know, there is no way one can tell the stack which ports to H use, so I need to do it at the ISP.  Actually, I would need to do it at G the ISP anyway, since I want to avoid connections over ISDN being made y when I don't want them.e  C > I don't know if the filter at your ISP tracks connections.  (Most  > true firewalls do this.)    D I suspect it's just a simple filter and not an intelligent firewall.   ------------------------------  + Date: Fri, 01 Mar 2002 15:25:21 +0100 (MET)n9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>-( Subject: Re: restricting access to ports; Message-ID: <01KEUNCHBAD88Y8HHB@sysdev.deutsche-boerse.com>i  F > With this type of configuration, no matter what you do, someone willI > attempt to access your system via it's (I'm assuming here...) static IP,I > address.  The router does not know that if it is wanted or unwanted andaH > since you said yourself that if it gets to the router, you are billed.I > ISDN in this configuration is a lose-lose situation.  Especially if yous > want to have access at all.  f  G Right.  However, if it's some Windows virus going for port 80 (which I  H suspect a lot of the unwanted connections are), if the ISP blocks it, I  don't have to pay.  J > You can set up any service on any port you want.  However, if someone isI > port-scanning and you have set up access for that port, you are billed.i  A Right, which is why I would like at least commonly scanned ports w blocked.   ------------------------------  % Date: Fri, 01 Mar 2002 13:07:26 -05009- From: JF Mezei <jfmezei.spamnot@videotron.ca>s( Subject: Re: restricting access to ports, Message-ID: <3C7FC35C.9A8BC2ED@videotron.ca>   Phillip Helbig wrote: ; > iptables -A helbig_filter -p tcp --dport 8000   -j ACCEPT ; > iptables -A helbig_filter -p tcp --dport 20:21  -j ACCEPTo; > iptables -A helbig_filter -p tcp --dport 23     -j ACCEPTu; > iptables -A helbig_filter -p tcp --dport 443    -j ACCEPTt; > iptables -A helbig_filter -p tcp --dport 25     -j ACCEPTI; > iptables -A helbig_filter -p tcp --dport 110    -j ACCEPT 9 > iptables -A helbig_filter -p ICMP               -j DROPt  A What is wrong with accepting call requests for ports above 1024 ?g   ------------------------------  % Date: Fri, 01 Mar 2002 13:09:40 -0500t- From: JF Mezei <jfmezei.spamnot@videotron.ca>d( Subject: Re: restricting access to ports, Message-ID: <3C7FC3E2.AA613A1E@videotron.ca>   Phillip Helbig wrote: H > Right.  However, if it's some Windows virus going for port 80 (which II > suspect a lot of the unwanted connections are), if the ISP blocks it, In > don't have to pay.  G My ISP blocked 80 for any connection coming from outside its network toaH someone on their network, as a result of nimda and code red. So the onlyL connections I hacve for port 80 are from infected customers on the same ISP,H and I reported some of their IPs to the ISP and they would then call the, customer to tell him he is infected etc etc.  . Port 80 requests have gone down significantly.   ------------------------------  + Date: Fri, 01 Mar 2002 19:25:33 +0100 (MET)e9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>a( Subject: Re: restricting access to ports; Message-ID: <01KEUVKN0NLK8ZL57Q@sysdev.deutsche-boerse.com>o  C > What is wrong with accepting call requests for ports above 1024 ?M  I The original idea was to reject anything I don't know I need, so the ISP wF only allowed the server ports for telnet, smtp etc (all below 1024).  E The reason for this was to avoid unwanted costs due to viruses, port r
 scans etc.  E It now seems that this scheme doesn't work, since when I generate an wD outgoing request, some random port above 1023 is used for returning G traffic.  By blocking it, technically I could get out, but did not get aF any response (which of course kept the connection from doing anything F beyond the initial request to the server at the other end and made it  completely useless).  H As soon as the ISP removed the filter, things worked as before (i.e. no  restrictions).  G I understand that an intelligent firewall would not what incoming port oI number is associated with an outgoing request and not block it (at least :D not from the target of the outgoing request), but apparently my ISP % doesn't have an intelligent firewall.   H It seems that---except for a flat rate---my only option is not to allow H specific ports but rather to block specific ports.  My idea is to block I all below 1024 except those I know I need (server ports for SMTP and the hH like); the ports used for my outgoing connections and for listening for I return traffic associated with outgoing connections are all greater than f 1023.   + I want to allow the following < 1024 ports:t      20     21     22E    23A    25s    42i    53d    69.    79    443    989k   990t   992l  . Are there any others I might conceivably need?   ------------------------------  % Date: Fri, 01 Mar 2002 09:35:23 +0000y% From: Alan Greig <a.greig@virgin.net>o$ Subject: Re: Solution for the merger8 Message-ID: <tkiu7u0e57ctvq5b2bsqt0h1tlo6t75qu6@4ax.com>  5 On Fri, 01 Mar 2002 02:03:18 GMT, "David J. Dachtera"F <djesys.nospam@fsi.net> wrote:   >Brian Tillman wrote:a >> u+ >> >Sorry, but aren't we allowed to dream ?e >>  % >> Sounds more like an hallucination!y >  ><music>0 >...and you've just had some kind of mushroom...	 ></music>e  % The White Knight is talking backwardsg! And the Red Queen's off her head.H  E Guess Carly's the Red Queen. Not sure I see Curly as the White Knighto! but he certainly talks backwards,g -- Alan   ------------------------------   Date: 1 Mar 2002 08:44:12 -0600e+ From: young_r@encompasserve.org (Rob Young)u$ Subject: Re: Solution for the merger3 Message-ID: <ck5UxnA0WVsl@eisner.encompasserve.org>o  ` In article <tkiu7u0e57ctvq5b2bsqt0h1tlo6t75qu6@4ax.com>, Alan Greig <a.greig@virgin.net> writes:7 > On Fri, 01 Mar 2002 02:03:18 GMT, "David J. Dachtera"S  > <djesys.nospam@fsi.net> wrote: >  >>Brian Tillman wrote: >>> , >>> >Sorry, but aren't we allowed to dream ? >>> & >>> Sounds more like an hallucination! >>	 >><music>s1 >>...and you've just had some kind of mushroom...t
 >></music> > ' > The White Knight is talking backwardsa# > And the Red Queen's off her head.V > G > Guess Carly's the Red Queen. Not sure I see Curly as the White Knight # > but he certainly talks backwards,h     	Actually...  < 	"one pill makes you larger and one pill makes you small..."  A 	And you can't blame them for taking both pills at the same time!a  D 	One of the underlying arguments against the merger from Mr. HewlettE 	is there will be too much exposure to PCs.  Of course the idea thereoF 	is obvious, merge both PC divisions and ax half the employees betweenC 	the two corporations.  Walter is off base on that one.  One of theiE 	underlying incentives in this entire merger is to do something about59 	the "PC problem."  For sure!   That is the "small pill."   = 	The "large pill" of course is servers, services and storage!i  ? 	"and the one's that mother gives you don't do anything at all,e+ 	Go ask Carly... when she's ten feet tall!"y   				RobW   ------------------------------  % Date: Fri, 01 Mar 2002 15:12:57 +0000o% From: Alan Greig <a.greig@virgin.net>o$ Subject: Re: Solution for the merger8 Message-ID: <kd6v7ugqa80o8edc926i7aefmmgjq072f8@4ax.com>  C On 1 Mar 2002 08:44:12 -0600, young_r@encompasserve.org (Rob Young)  wrote:   >In- >> -( >> The White Knight is talking backwards$ >> And the Red Queen's off her head. >> sH >> Guess Carly's the Red Queen. Not sure I see Curly as the White Knight$ >> but he certainly talks backwards, >g >D
 >	Actually...3 >6= >	"one pill makes you larger and one pill makes you small..."e > B >	And you can't blame them for taking both pills at the same time!  6 Certainly Logic and proportion have fallen sloppy dead  D  Anyway must go as I believe I can hear a hookah smoking caterpillar calling.   Feed your VAX!     -- Alan   ------------------------------  * Date: Fri, 1 Mar 2002 16:54:06 +0000 (UTC)4 From: lewis@luminaforspam.mitre.org (Keith A. Lewis)  Subject: Re: Sound on alpha/VMS?. Message-ID: <a5obne$81d$1@newslocal.mitre.org>   pmoreau@dev.ath.cena.fr (Patrick MOREAU, CENA Athis, Tel: 01.69.57.64.40) writes in article <rasNhsB7kq0g@sable> dated 28 Feb 2002 17:37:33 +0100:0 >In article <a5j9qi$87l$1@newslocal.mitre.org>, ; >lewis@lumina.removethis.mitre.org (Keith A. Lewis) writes: J >> I see some audio ports in the back of my Alphastation 500au.  Are these >> usuable under VMS at all?  G >You need MMOV (Multimedia Services for OpenVMS, the pack was generallytI >available with VMS on a workstation). MMOV supports the olders MicrosofteJ >Compatible sound cards found on alphastations and also new Compaq Ensoniq7 >AudioPCI available for recent hardware (DS10 etc ...).t >hO >MMOV gives you a basic sound player - recorder (WAV format or 8bit sun format) P >but some interesting ports of Unix sound applications are available at the DECWE >archive (mp3 player, midi player, midi sequenncer and score editor):  >:# >http://decwarch.free.fr/audio.htmlo  9 Thanks for the link, Patrick!  I'll check that stuff out.o  G But I wonder if support has been yanked.  I'm checking it out on my oldlH Alphastation 600 5/233 first.  It came with a Microsoft sound card and aK MMOV-RT license.  I'm running VMS 7.3 and DW-MOTIF 1.2-5.  I just installeda MMOV 2.2 and rebooted.  G Now when I run DECsound from the CDE it doesn't seem to find the card. e= DECsound: %DIVA-E_ASSNFAIL, unpecified error from diva_assign    Also,d* $ run SYS$SYSTEM:MMOV$AUDIOSELECTPORTS.EXE <error> No audio devices found  H What do sound devices look like?  Here's what I have on the 600.  I knowJ what most of these are.  At one point I tried to put this card in a 4100. 3 Maybe I put it back in the wrong slot or something.-  	 $ sho devl  P Device                  Device           Error    Volume         Free  Trans MntP  Name                   Status           Count     Label        Blocks Count CntP VIPER$DKA0:             Mounted              0  VIPERSYS        132768   385   1P VIPER$DKA100:           Mounted              0  VSCRATCH       6408801     1   1P VIPER$DKA200:           Mounted              0  VUSER          1763136     7   1. VIPER$DKA500:           Online wrtlck        0. VIPER$DVA0:             Online               0  . Device                  Device           Error.  Name                   Status           Count. ASN0:                   Online               0. FTA0:                   Offline              0. FTA1:                   Online               0. OPA0:                   Online               0. RTA0:                   Offline              0. RTB0:                   Offline              0. TNA0:                   Offline              0. TTA0:                   Online               0. TTB0:                   Online               0  . Device                  Device           Error.  Name                   Status           Count. EWA0:                   Online               0. EWA2:                   Online               0. EWB0:                   Online               0. EWB2:                   Online               0. EWB3:                   Online               0. EWB4:                   Online               0. EWB5:                   Online               0. EWB6:                   Online               0. EWB7:                   Online               0. EWC0:                   Online               0. EWC2:                   Online               0. GYA0:                   Online               0. IKA0:                   Offline              0. IMA0:                   Offline              0. INA0:                   Offline              0. MPA0:                   Online               0. OPA2:                   Online               0. OPA3:                   Online               0. PKA0:                   Online               0. PKB0:                   Online               0. PPP0:                   Online               0. WSA0:                   Offline              0. WSA1:                   Online               0  F I just checked the Hobbyist FAQ and it said MMOV-DV is available, so IH should be able to build applications, which is what I really want to do.  + --Keith Lewis              klewis$mitre.org.> The above may not (yet) represent the opinions of my employer.   ------------------------------  # Date: Fri, 01 Mar 2002 17:27:43 GMTs- From: "John E. Malmberg" <wb8tyw@qsl.network>   Subject: Re: Sound on alpha/VMS?* Message-ID: <3C7FBC77.2010205@qsl.network>   Keith A. Lewis wrote:S  >F  > But I wonder if support has been yanked.  I'm checking it out on myD  > old Alphastation 600 5/233 first.  It came with a Microsoft sound@  > card and a MMOV-RT license.  I'm running VMS 7.3 and DW-MOTIF2  > 1.2-5.  I just installed MMOV 2.2 and rebooted.  E Did you add @SYS$STARTUP:MMOV$STARTUP to your SYSTARTUP_VMS.COM file?b  E Disk AUA0:, device type Ensoniq AudioPCI, is online, record-oriented e device, carriage control.k  G   Error count                   0    Operations completed          2115CG   Owner process     "MMOV$SERVER"    Owner UIC             [VMS,SYSTEM] G   Owner process ID       000000BF    Dev Prot       S:RWPL,O:RWPL,G:R,W0G   Reference count               1    Default buffer size              0u   -John: wb8tyw@qsl.network Personal Opinion Only0   ------------------------------   Date: 1 Mar 2002 11:55:01 -0600 + From: young_r@encompasserve.org (Rob Young)e/ Subject: Sun eating major helping of Linux Crowu3 Message-ID: <J9Uv6b4tuD8K@eisner.encompasserve.org>i  > 	Gotta love revisionist historians!  Remember kids, it is your= 	"perception" of history.  We all have our own "perceptions!"k  F http://www.nytimes.com/library/tech/00/03/biztech/articles/20soft.html     March 20, 2000  J "Linux on non-PC platforms is a nonstarter," said Greg Papadopoulos, chiefI technology officer for Sun Microsystems. "The ecosystem of open source isw4 not going to be working for IBM on other platforms."    - http://biz.yahoo.com/fo/020207/0207sun_1.html,   Thursday February 7, 2002I  I Sun's president and chief operating officer, Ed Zander, tried to convinceoG listeners on a conference call that his company has long been a stauncho' supporter of Linux. [Cough cough cough]u   ...t  O Curiously, he said the media, analysts and even customers didn't understand howoK committed his company is to Linux. Perhaps that's because Sun has until nowoO only dipped its big toe in Linux waters. Previous reluctance about Linux can beoJ seen as an effort to protect its flagship Solaris franchise, but Sun's new! strategy resembles a cannonball. l  F Sun's Linux initiatives include general-purpose servers running Linux,J development of an entire suite of infrastructure software called SunOne onN Linux, compatibility tools so that Linux applications can run on Sun's SolarisA operating system and a range of professional services for Linux. s    = 	Perhaps it has a lot to do with IBM's noted Linux success asb- 	later in that biz.yahoo.com article we read:a  N It may also be about competing on more fronts against IBM , which was an earlyI and prominent supporter of Linux. In fact, IBM last week said that it hasiL already recouped most of its $1 billion investment in Linux through sales of  hardware, software and services.   				RobT   ------------------------------  # Date: Fri, 01 Mar 2002 19:00:24 GMTu* From: "Bill Todd" <billtodd@metrocast.net>3 Subject: Re: Sun eating major helping of Linux Crowa= Message-ID: <cdQf8.159$pN4.15502@bin8.nnrp.aus1.giganews.com>o  8 "Rob Young" <young_r@encompasserve.org> wrote in message- news:J9Uv6b4tuD8K@eisner.encompasserve.org...  > ? > Gotta love revisionist historians!  Remember kids, it is yourt> > "perception" of history.  We all have our own "perceptions!"  L I'm afraid so, Rob.  The statement below appears in no way inconsistent withG Sun's current interest in Linux *on* PC platforms, and AFAIK Sun is notoG doing anything to encourage Linux on SPARC (though is making efforts tofI allow Linux *applications* to run on Solaris, which again seems in no wayoL inconsistent with the statement, which referred to IBM's support of complete, Linux environments on its non-PC platforms).  L This is not to say that Sun's interest in Linux has not increased, just thatK your purported inconsistency doesn't seem to be supported by the referencesA	 you cite.w   - bill   > H > http://www.nytimes.com/library/tech/00/03/biztech/articles/20soft.html >e >  > March 20, 2000 >mL > "Linux on non-PC platforms is a nonstarter," said Greg Papadopoulos, chiefK > technology officer for Sun Microsystems. "The ecosystem of open source isi6 > not going to be working for IBM on other platforms." >a > / > http://biz.yahoo.com/fo/020207/0207sun_1.htmll >  > Thursday February 7, 2002h >oK > Sun's president and chief operating officer, Ed Zander, tried to convinceDI > listeners on a conference call that his company has long been a staunchn) > supporter of Linux. [Cough cough cough]p >o > ...  >rB > Curiously, he said the media, analysts and even customers didn't understand howI > committed his company is to Linux. Perhaps that's because Sun has untili nowgJ > only dipped its big toe in Linux waters. Previous reluctance about Linux can beL > seen as an effort to protect its flagship Solaris franchise, but Sun's new" > strategy resembles a cannonball. > H > Sun's Linux initiatives include general-purpose servers running Linux,L > development of an entire suite of infrastructure software called SunOne onH > Linux, compatibility tools so that Linux applications can run on Sun's SolarisfB > operating system and a range of professional services for Linux. >e > > > Perhaps it has a lot to do with IBM's noted Linux success as. > later in that biz.yahoo.com article we read: >mJ > It may also be about competing on more fronts against IBM , which was an earlysK > and prominent supporter of Linux. In fact, IBM last week said that it haspK > already recouped most of its $1 billion investment in Linux through salesg of" > hardware, software and services. >  > Robs >  >b   ------------------------------  # Date: Fri, 01 Mar 2002 07:25:00 GMTp* From: "Bill Todd" <billtodd@metrocast.net>! Subject: Re: Timing is everything C Message-ID: <g1Gf8.243346$Re2.18542452@bin6.nnrp.aus1.giganews.com>C  8 "Rob Young" <young_r@encompasserve.org> wrote in message- news:h7d9jg7BPJlu@eisner.encompasserve.org...sK > In article <8Lxf8.239707$Re2.18149826@bin6.nnrp.aus1.giganews.com>, "Bill & Todd" <billtodd@metrocast.net> writes: > >eE > > In this context, Paul DeMone's numbers from his realworldtech.come 'SiliconC > > Insider' articles are interesting.  Last June, his estimates of 
 McKinley'sH > > performance *at 1.2 GHz and with an assumed 7-stage pipeline* were aL > > SPECint_base2k of 700 and a SPECfp_base2k of 1500 (by way of comparison, hisPG > > EV7 estimates at 1.2 GHz were 1000 and 1600, respectively, and theyn aren'tH > > much different today).  I believe his most-recent McKinley estimates (though F > > I can't find them at the moment) are 800 SPECint and 1400 SPECfp -	 *despite*IJ > > a lower clock frequency (1 GHz) and longer pipeline (8 stages) than he >  >  >.L http://www.realworldtech.com/forums/index.cfm?action=detail&PostNum=584&Thre ad=1&entryID=5291&roomID=130 >16 > Topic: EV7, McKinley SPECint perf: works in progress >d- > Name: Paul DeMone (pdemone@igs.net) 2/26/02a >s >oK > "Intel and Compaq people are busy fine tuning the performance of McKinleyt andrI > EV7 running standard benchmarks in time for official release later thise year.oH > After talking with sources with better perspective of the difficulties involvedC > in maximizing integer performance of high ILP, moderate clockrateo processors IK > now think the SPECint_base2k estimates for EV7 and McKinley in my "Spider' andkJ > the Mountain article" are too optimistic, especially for the McKinley. I don't D > like revising predictions made in my articles so I thought I would disclose mygJ > misgivings about those estimates here. My new estimates for McKinley and EV7oL > SPECint_base2k scores are 700 at 1.0 GHz and 1000 and 1.2 GHz respectivelyL > (down from 800 and 1050 in the article). Ironically that brings me back to thenE > same score estimates I had in my last year's "Battle in 64 bit Lando
 Revisited"> > article although the 700 figure was for a 1.2 GHz McKinley."  J Thanks - that brings the McKinley estimate at least back into the realm ofL believability, though it still seems a tad high given the reduction in clockK rate and increase in pipeline length.  In last year's article Paul seems toeF have overestimated McKinley's cache latency, but while faster cache isI certainly A Good Thing I have a vague recollection that SPECint has to be K configured such that it can't run essentially cache-resident, in which case I that wouldn't necessarily explain his newer SPECint projections.  He also E may have underestimated the potential increase in ILP from McKinley's F additional two integer FUs (which he talked about at length in anotherG article last July), so perhaps that's the reason for his later optimism-J (though I have no idea whether SPECint-type code has sufficient additionalG potential parallelism over what Merced can already exploit to make this5
 significant).5  F In this context one should remember the reference in the same materialI behind the current estimates to Merced's estimated 0.5 SPECint/MHz.  ThattL would yield a predicted Merced SPECint value of 400, whereas IIRC it debutedE at 314 (in a Dell box) and has yet to hit 380 in *any* configuration.c  F Oh, well.  As I said before, we'll know soon - just not soon enough to influence the merger voting.   - bill   ------------------------------  % Date: Fri, 01 Mar 2002 10:18:02 +0000g% From: Alan Greig <a.greig@virgin.net>-! Subject: Re: Timing is everything08 Message-ID: <gvku7usb8bfrh9a4ogpd1lc7ohggbdtd10@4ax.com>  F On Thu, 28 Feb 2002 21:59:32 GMT, "Bill Todd" <billtodd@metrocast.net> wrote:    J >If it weren't for the clear overlap in the timing of the Intel/Alpha dealK >and the merger discussions I'd still be reluctant to bring up such issues.aI >But the merger itself is enough of a soap opera that it makes such added M >speculations in this vein seem pretty consistent, even if I still feel a bitn >sheepish in presenting them.d   Bill,u  D Just as we were not told of the secret HP/ Compaq merger discussionsD during the (up to) two year period prior to the announcement, we are6 not being told about the secret HP/Intel merger ideas.   There's my conspiracy theory.s  F And Carly has already blurted out that Walter risks derailing a future' plan if he blocks the Compaq merger....a  ? All the big players have said we should expect to see more megaeE mergers in the future. We should assume they already have partners in  mind.h   >s >- bills >O >o   -- Alan   ------------------------------  + Date: Fri, 01 Mar 2002 15:56:37 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>eJ Subject: uniform message format (was: RE: What return codes mean success?); Message-ID: <01KEUOCFLR2A8Y8HHB@sysdev.deutsche-boerse.com>.  5 Naively, I would expect the message to be returned byd      o  the application itself  0    o  EXIT with the appropriate value of $STATUS  (    o  HELP/MESSAGE after an error occurs      o  F$MESSAGE($STATUS)  H to be the same.  They are not, at least not always.  Is there any rhyme  or reason behind this?   Example:   $ DIR fjwiefjwio! %DIRECT-W-NOFILES, no files found6 $ status = $status $ exit $status .AND. %XEFFFFFFF6 %RMS-W-FNF, file not found $ help/message  FNF,  file not found>$ $ write sys$output f$message(status) %RMS-W-FNF, file not found  G Here, DCL is different than the others.  However, with other commands, h other patterns occur.h   ------------------------------  $ Date: Fri, 1 Mar 2002 08:37:07 -0000, From: "Bob Knowles" <bob.knowles@compaq.com>. Subject: Re: vax/vms documentation - psi / x291 Message-ID: <15Hf8.390$fL6.6066@news.cpqcorp.net>p  H Sorry Pat - I can't be of much help. While I was in the relevant writingL group, I was working on other things at the time - although by chance a bookK I did work on more than 10 yrs ago turns out now to have got into the Alpha E PSI docset - the WANDD book (on which my expertise now is vanishinglyl small!)   G I sent your question to a one-time VAX PSI engineer (now no longer withPF Compaq) , who told me that Antonio was on the right track. I think theK 'Unsynchronised' message confirms his suspicion that your DTEs are just noteI working. He also confirmed that the docs were on the ConOLD disc 10 yearsr= ago, so as I said it'd be worth trying to find an early copy.n  	 Good luckt   b     B "pat saunders" <pat.saunders@sis.securicor.co.uk> wrote in message6 news:bc0e3bd8.0202280819.af7766a@posting.google.com...9 > "Bob Knowles" <bob.knowles@compaq.com> wrote in messagea- news:<pV7f8.259$fL6.5523@news.cpqcorp.net>...s6 > > "Alan Greig" <a.greig@virgin.net> wrote in message6 > > news:0epp7ucgiq9hds4emoqigm275ubesp3bi9@4ax.com...7 > > > On Wed, 27 Feb 2002 09:29:18 -0000, "Bob Knowles"t% > > > <bob.knowles@compaq.com> wrote:p > > >o > > >aG > > > >As Pat specified VAX, and the VAX PSI product was retired beforea Phase V,I > > > >sure as eggs is eggs the Phase V info won't be much (if any) help.P Andk > > >  > > > Is that strictly true? > >dL > > Nope. I checked the dates on the Alpha docs, and there was an overlap of 25 > > or 3 yearsL > > between the end of Reading's development of VAX PSI and the availability ofL > > the Alpha product, so Pat may well be running the old product over Phase V. > >r > > bC >i >o >' > Hi,t5 >   Yes I am using phase v , DECNET/OSI and VMS 5.5-2iG >   We have a number of VAX's that work with X.25 but we did not make aRD > backup, so when a particular VAX failed we had to reconfigure from
 > stratch.? >   I still get PAD-F-NOLINES but have found out more details : - >   I have a LAPB link to a x.25 mini switch.b/ >   Every ten secs I get the following errors :  > & >   Message from user SYSTEM on KEWG99D > Event: Link Setup Failed from: Node LOCAL:.KEWG99 LAPB Link DTE-0,/ >         at: 2002-02-28-17:16:00.693+00:00Iinfl9 >         eventUid   D645CF84-2C6E-11D6-8008-AA0004009E2A 9 >         entityUid  3718B880-2C6E-11D6-8007-AA0004009E2A 9 >         streamUid  61C47CE0-2C6E-11D6-8008-AA0004009E2A  >E >K > NCL>: > %%%%%%%%%%%  OPCOM  28-FEB-2002 17:16:00.75  %%%%%%%%%%%$ > Message from user SYSTEM on KEWG99D > Event: Link Initialising from: Node LOCAL:.KEWG99 LAPB Link DTE-0,/ >         at: 2002-02-28-17:16:00.693+00:00Iinf 0 >         Link Initialising Reason=Maximum Retry9 >         eventUid   D645CF85-2C6E-11D6-8008-AA0004009E2A 9 >         entityUid  3718B880-2C6E-11D6-8007-AA0004009E2A 9 >         streamUid  61C47CE0-2C6E-11D6-8008-AA0004009E2A  > G > when I look at the DTE state, I find it is "Unsynchronised", I am notf* > sure what this means or how to fix it ?? >f > Any help appreciated.0 >  > ta > pat    ------------------------------  % Date: Fri, 01 Mar 2002 08:54:40 +0000 % From: Alan Greig <a.greig@virgin.net> . Subject: Re: vax/vms documentation - psi / x298 Message-ID: <cagu7ugs03bdq13ml4rf20lst8k1l60hv0@4ax.com>  D On 28 Feb 2002 08:19:15 -0800, pat.saunders@sis.securicor.co.uk (pat saunders) wrote:   >WF >when I look at the DTE state, I find it is "Unsynchronised", I am not) >sure what this means or how to fix it ??   8  think it means exactly as it says: The physical line is= "unsynchronized" - ie no signal on the line. Suspect a modem,W0 line-driver, physical wiring or carrier problem.   >  >Any help appreciated. >  >ta  >pat   -- Alan   ------------------------------   Date: 1 Mar 2002 06:48:25 -0800 5 From: pat.saunders@sis.securicor.co.uk (pat saunders) . Subject: Re: vax/vms documentation - psi / x29= Message-ID: <bc0e3bd8.0203010648.7c4b2d14@posting.google.com>   e Alan Greig <a.greig@virgin.net> wrote in message news:<cagu7ugs03bdq13ml4rf20lst8k1l60hv0@4ax.com>... F > On 28 Feb 2002 08:19:15 -0800, pat.saunders@sis.securicor.co.uk (pat > saunders) wrote: >  > >iH > >when I look at the DTE state, I find it is "Unsynchronised", I am not+ > >sure what this means or how to fix it ??1 > : >  think it means exactly as it says: The physical line is? > "unsynchronized" - ie no signal on the line. Suspect a modem,b2 > line-driver, physical wiring or carrier problem. >  > >  > >Any help appreciated. > >e > >tar > >pat           Hi,oE   I include more info regarding the problem that "might" be a soluion-F to why it is unsynchronised. I get the same NCL/CML errors as the chapF below but the solution proposed only works on an alpha station. I need to find the equiv for the vax.  >    -----------------------------------------------------------  ,    A problem and a solution (as a reminder):   Environment:. Digital AlphaStation 500/ running OpenVMS V7.1  9 DEC AXPVMS DECNET_OSI V7.1          Full LP     Available>9 DEC AXPVMS VMS V7.1                 Oper System Available 9 DEC AXPVMS WANDD V1.1-B             Full LP     Availablee9 DEC AXPVMS X25 V1.1-B               Full LP     Availabler  8 During the boot, the system showed the following errors:  6    %NCL-E-CMLSENDFAILED, error sending command request5    -CML-E-EMAAPROB, error returned from VMS EMA agent 3    -NCL-E-ENTCLSNOTSUPP, entity class not supportedB  E while it was starting X.25, and executing sys$startup:x25$config.ncl.   > It turned out that @sys$startup:x25$configure.com setting was:+   1.  Autoconfigure device drivers   :   NO-   While it should be:e,   1.  Autoconfigure device drivers   :   YES   ------------------------------   Date: 1 Mar 2002 06:51:46 -0800n5 From: pat.saunders@sis.securicor.co.uk (pat saunders)e! Subject: VMS / EMA agent problemsi= Message-ID: <bc0e3bd8.0203010651.3b799a08@posting.google.com>    Hi, E   I include more info regarding the problem that "might" be a soluion0F to why a DTE unsynchronised. I get the same NCL/CML errors as the chapF below but the solution proposed only works on an alpha station. I needB to find the equiv for the vax. I use DECNET/OSI and Vax VMS V5.5-2  >    -----------------------------------------------------------  ,    A problem and a solution (as a reminder):   Environment:. Digital AlphaStation 500/ running OpenVMS V7.1  9 DEC AXPVMS DECNET_OSI V7.1          Full LP     Availablet9 DEC AXPVMS VMS V7.1                 Oper System Availablex9 DEC AXPVMS WANDD V1.1-B             Full LP     Availabled9 DEC AXPVMS X25 V1.1-B               Full LP     Availablem  8 During the boot, the system showed the following errors:  6    %NCL-E-CMLSENDFAILED, error sending command request5    -CML-E-EMAAPROB, error returned from VMS EMA agent 3    -NCL-E-ENTCLSNOTSUPP, entity class not supportedn  E while it was starting X.25, and executing sys$startup:x25$config.ncl.   > It turned out that @sys$startup:x25$configure.com setting was:+   1.  Autoconfigure device drivers   :   NO    While it should be:y,   1.  Autoconfigure device drivers   :   YES   ------------------------------  % Date: Fri, 01 Mar 2002 08:48:39 +0100u9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com>x, Subject: Re: What return codes mean success?' Message-ID: <3C7F3257.480DFD79@aaa.com>m  ? That's not 100% as described in "Writing real programs in DCL".n   0-2    cond code.  3-14   msg numbere 15     fac spec ?i 16-26  facility number 27     customer specific ? 28     inhibit display 29-31  reserved/unused.d   Jan-Erik Sderholm.    Paul Winalski wrote: > " > bits 0-2 are the condition code: >     0 = warningl >     1 = successe >     2 = errorj >     3 = informational  >     4 = fatal error  >     other values are reservedb >   > bits 3-14 are the message codeG > bit 15 is 0 if the message code in bits 3-14 is one of the OS-definednB >     shared messages, or 1 if the message code is specific to the+ >     particular facility (see bits 16-31). C > bits 16-30 are the facility code of the generator of the message.T3 >     For example the DCL CLI's facility code is 3.h? > bit 31 is 0 for system-defined facilities registered with VMSn4 >     Engineering, 1 for customer-defined facilities >u   ------------------------------   Date: 1 Mar 2002 07:03:38 -0600s From: briggs@encompasserve.org, Subject: Re: What return codes mean success?3 Message-ID: <5Ry1sOoGQkSs@eisner.encompasserve.org>   c In article <3C7F3257.480DFD79@aaa.com>, Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> writes: A > That's not 100% as described in "Writing real programs in DCL".f >  > 0-2    cond code.  > 3-14   msg numberw > 15     fac spec ?y > 16-26  facility number > 27     customer specific ? > 28     inhibit display > 29-31  reserved/unused.s  B As long as we're nit picking, facility number is in bits 16-27 andD includes the customer specific bit 27.  And the message number is in4 bits 3-15 and includes the facility specific bit 15.  D One can get the "official" definitions out of $STSDEF in STARLET.MLB  
 SEVERITY: 0-2d COND_ID:  3-27 CONTROL:  28-31E
 SUCCESS:  0-0  MSG_NO:	  3-15 CODE:	  3-14 FAC_SP:	  15-15t CUST_DEF: 27-27a INHIB_MSG: 28-28 FAC_NO:	  12-27    ------------------------------   Date: 1 Mar 2002 07:33:02 -0600t- From: Kilgallen@SpamCop.net (Larry Kilgallen)n, Subject: Re: What return codes mean success?3 Message-ID: <j4f19IS$Ul9d@eisner.encompasserve.org>n  T In article <5Ry1sOoGQkSs@eisner.encompasserve.org>, briggs@encompasserve.org writes:e > In article <3C7F3257.480DFD79@aaa.com>, Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> writes:.B >> That's not 100% as described in "Writing real programs in DCL".   >> 16-26  facility numbera  D > As long as we're nit picking, facility number is in bits 16-27 andF > includes the customer specific bit 27.  And the message number is in6 > bits 3-15 and includes the facility specific bit 15. > F > One can get the "official" definitions out of $STSDEF in STARLET.MLB >  > FAC_NO:	  12-27   E All in all, it would seem a more accurate "official" definition wouldo# be that in SYS$LIBRARY:STARLET.REQ:   % $ sear sys$Library:starlet.req fac_nox# literal STS$M_FAC_NO = %X'FFF0000'; ! macro STS$V_FAC_NO = 0,16,12,0 %;s? literal STS$S_FAC_NO = 12;              !  Facility is 12 bits o $    ------------------------------   Date: 1 Mar 2002 10:44:32 -0600- From: briggs@encompasserve.org, Subject: Re: What return codes mean success?3 Message-ID: <u+iBaqOeNavP@eisner.encompasserve.org>D  c In article <j4f19IS$Ul9d@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:rV > In article <5Ry1sOoGQkSs@eisner.encompasserve.org>, briggs@encompasserve.org writes:f >> In article <3C7F3257.480DFD79@aaa.com>, Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> writes:C >>> That's not 100% as described in "Writing real programs in DCL".S >  >>> 16-26  facility number > E >> As long as we're nit picking, facility number is in bits 16-27 andaG >> includes the customer specific bit 27.  And the message number is ink7 >> bits 3-15 and includes the facility specific bit 15., >> PG >> One can get the "official" definitions out of $STSDEF in STARLET.MLBn >> n >> FAC_NO:	  12-27  + Larry points out correctly that is's 16-27.e  < Drat.  That's what I get for looking at STS$S_FAC_NO instead of STS$V_FAC_NO    ------------------------------  # Date: Fri, 01 Mar 2002 17:31:33 GMTl From: system@SendSpamHere.ORG , Subject: Re: What return codes mean success?0 Message-ID: <00A0A4A5.7308A15C@SendSpamHere.ORG>  c In article <j4f19IS$Ul9d@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:eU >In article <5Ry1sOoGQkSs@eisner.encompasserve.org>, briggs@encompasserve.org writes:ff >> In article <3C7F3257.480DFD79@aaa.com>, Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> writes:C >>> That's not 100% as described in "Writing real programs in DCL".i >c >>> 16-26  facility number >nE >> As long as we're nit picking, facility number is in bits 16-27 and G >> includes the customer specific bit 27.  And the message number is in'7 >> bits 3-15 and includes the facility specific bit 15.i >> fG >> One can get the "official" definitions out of $STSDEF in STARLET.MLBe >> I >> FAC_NO:	  12-27 >oF >All in all, it would seem a more accurate "official" definition would$ >be that in SYS$LIBRARY:STARLET.REQ: > & >$ sear sys$Library:starlet.req fac_no$ >literal STS$M_FAC_NO = %X'FFF0000';" >macro STS$V_FAC_NO = 0,16,12,0 %;@ >literal STS$S_FAC_NO = 12;              !  Facility is 12 bits  >$ "  F Wouldn't the official definition be in the .SDL file in the source? :  --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMi             J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbese   ------------------------------  $ Date: Fri, 1 Mar 2002 12:37:34 -0500; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com> , Subject: Re: What return codes mean success?$ Message-ID: <3c7fbca8$1@news.si.com>  @ >I think I'v seen someware that you can (or could) register yourH >own application at DEC/Compaq, so you could have your own status codes.  K Only if you wanted that facility reserved.  You can create any facility you H want without registering the number, if you keep it internal to your own& business (or home, for the hobbyists). --A Brian Tillman                   Internet: tillman_brian at si.comvA Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to preventa< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------   Date: 1 Mar 2002 12:20:30 -0600h- From: Kilgallen@SpamCop.net (Larry Kilgallen)h, Subject: Re: What return codes mean success?3 Message-ID: <1+xtFuRhyXxb@eisner.encompasserve.org>   b In article <3c7fbca8$1@news.si.com>, "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:A >>I think I'v seen someware that you can (or could) register your-I >>own application at DEC/Compaq, so you could have your own status codes.5 > M > Only if you wanted that facility reserved.  You can create any facility youcJ > want without registering the number, if you keep it internal to your own( > business (or home, for the hobbyists).  A But if you want to avoid conflict with vendor products that use amE registered facility code, make sure your code is in the site-specifice8 range (has the site-specific bit with the proper value).   ------------------------------   Date: 1 Mar 2002 08:21:40 -0800d( From: bob@instantwhip.com (Bob Ceculski)! Subject: Re: [Q] internet and VMSa= Message-ID: <d7791aa1.0203010821.1fc80acf@posting.google.com>h  u martin@radiogaga.harz.de (Martin Vorlaender) wrote in message news:<3c7ed2bd.524144494f47414741@radiogaga.harz.de>... + > Bob Ceculski (bob@instantwhip.com) wrote: 9 > > martin@radiogaga.harz.de (Martin Vorlaender) wrote...e/ > > > Bob Ceculski (bob@instantwhip.com) wrote:e< > > > > "David J. Dachtera" <djesys.nospam@fsi.net> wrote...L > > > > > TCPware for OpenVMS from Process Software, http://www.process.com/O > > > > > TCPware was written from the ground up on VMS. It's kind of a pain tor@ > > > > > manage, but is very fast for some important functions. > > > >8O > > > > what are you talking about a pain to manage?  it is far easier than ucxuP > > > > or multinet, and once you understand the tcpware_configure.com file, you( > > > > don't even need $ NETCU anymore, > > > K > > > TCPWARE_CONFIGURE.COM doesn't carry an NETCU settings. It's all abouto > > > CNFNET.COM.  > > > N > > > I thought you violently opposed having to edit ASCII configuration filesO > > > at some time? Once you understand HTTPD.CONF, configuring Apache is easy.  > >nK > > wrong!  tcpware_configure.com carries netcu settings ... one example ise > >         $ NETCU SET GATEWAYu > C > Oops, you're right. The first few lines of the file deal with thedE > interface(s), host and domain name, etc. Which of course have NETCU  > equivalents. > G > But the remaining statements (those which deal with enabling servicesxL > and setting up LPD queues) are used to control execution of *_CONTROL.COM,) > and thus have nothing to do with NETCU.. > B > > this can be done by edt on the above con ... there are severalI > > others I can do also ... when I say eliminate netcu almost completelyaH > > I also mean cnfnet ... and editing tcpware_configure is a lot easier3 > > than editing 8 million conf files in apache ...  > H > Oh come on. You don't have to use Apache's INCLUDE statement - you canI > have it all in one file (in fact, using HTTDP.CONF/SRM.CONF/ACCESS.CONFnF > is deprecated). As the task at hand is a little more complicated, of6 > course you do have to remember some more statements. >  > cu, 
 >   Martin  E with purveyor, I just use the rsm html interface for everything, or I ; can edit a single configuration file ... it's a lot easier!r   ------------------------------   End of INFO-VAX 2002.118 ************************