0 INFO-VAX	Fri, 18 Feb 2005	Volume 2005 : Issue 97      Contents: 7.32 patching questions  Re: 7.32 patching questions  Re: 7.32 patching questions  Re: 7.32 patching questions  Re: 7.32 patching questions  Re: 7.32 patching questions  Re: 7.32 patching questions  Re: 7.32 patching questions  Re: 7.32 patching questions + Dallas-Fort Worth LUG Meeting - February 25 3 Re: DCL command to show number of interactive users  Dvorak on IA64 & Opteron & Cell # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down # Re: HP financials: Alpha sales down ( Re: I'd heard about this a while back...- Re: linux kernel has major security flaws ... - Re: linux kernel has major security flaws ... 1 Re: Looking for suggestions for bootcamp sessions 1 Re: mandatory 7.32 update (in 8.2 ship) questions ! Re: Mounting disks during STARTUP  Re: Need performance help  OpenVMS 8.2 docs and freeware ! Re: OpenVMS 8.2 docs and freeware 4 Re: OpenVMS Cluster to Replace News.Individual.NET ?4 Re: OpenVMS Cluster to Replace News.Individual.NET ?4 Re: OpenVMS Cluster to Replace News.Individual.NET ?P OpenVMS Pearl - Datamation Article Names HP OpenVMS servers in top 5 best of 04 P Re: OpenVMS Pearl - Datamation Article Names HP OpenVMS servers in top 5 best ofP Re: OpenVMS Pearl - Datamation Article Names HP OpenVMS servers in top 5 best of OpenVMS Small Partner Strategy" Re: OpenVMS Small Partner Strategy" Re: OpenVMS Small Partner Strategy( OT: Message to Peter "EPLAN" LANGSTOEGER" Port Print facility Update for I64 Re: Queue Length on shadow disk  Re: Queue Length on shadow disk  Rdb - monitor home directory  Re: Rdb - monitor home directory Re: SLS dead Re: SLS dead Re: SLS dead! Re: Speed of light as speed limit  Re: Status of devices # Re: TCPIP automatic route additions  Re: [OT:] BiometricsP Re: [OT] Speed of light as speed limit (was Re: DECW$CLOCK design flaw   flaw   P Re: [OT] Speed of light as speed limit (was Re: DECW$CLOCK design flaw   flaw     F ----------------------------------------------------------------------    Date: 17 Feb 2005 11:44:48 -0800 From: tadamsmar@yahoo.com   Subject: 7.32 patching questionsB Message-ID: <1108669488.832525.99610@z14g2000cwz.googlegroups.com>   Looking at:   2 ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2  , What the heck is MASTER_V732_MASTER_ECOLIST?  4 It seems to be a kit, but it is too small to contain4 everything mentioned in the description .TXT file of> the same name. The text seems to describe VMS732_UPDATE-V0300.  7 Anyway I just loaded 7.32 from the Oct 03 distribution.   ) To patch it, I think that I should apply:    1. VMS732_PCSI-V0100 2. VMS732_UPDATE-V0300> 3. VMS732_VMSUPD-V0100 (from the mandatory update CD that came?    with the recent 8.2 shipment. It is not on the patch site!?) 6 4. Any other INSTALL_1 or applicable patches that have&    come out since VMS732_UPDATE-V0300.  ? Is this a good way to proceed?  I am assuming that UPDATE-V0300 3 rolls up all the important patches that preceed it.   % Could they make this more confusing??    ------------------------------  % Date: Thu, 17 Feb 2005 15:04:13 -0500 6 From: Brad Hamilton <brMadAhaPmiSlton@coMmcAasPt.Snet>$ Subject: Re: 7.32 patching questions0 Message-ID: <-9Kdna-ff-YgZYnfRVn-gg@comcast.com>   tadamsmar@yahoo.com wrote: <snip>9 > Anyway I just loaded 7.32 from the Oct 03 distribution.  > + > To patch it, I think that I should apply:  >  > 1. VMS732_PCSI-V0100 > 2. VMS732_UPDATE-V0300@ > 3. VMS732_VMSUPD-V0100 (from the mandatory update CD that cameA >    with the recent 8.2 shipment. It is not on the patch site!?) 8 > 4. Any other INSTALL_1 or applicable patches that have( >    come out since VMS732_UPDATE-V0300. > A > Is this a good way to proceed?  I am assuming that UPDATE-V0300 5 > rolls up all the important patches that preceed it.  > ' > Could they make this more confusing??  >   F I do not know what is contained in number 2.  Do numbers 1, 3, and 4, D and then look at the CD, to see if there is anything on the CD that , supersedes anything you have just installed.  B It has been my experience that MUP CD's usually duplicate patches C appearing on the ECO website.  It is always good practice to check.   : While we are on the subject of "best practice" for ECO's -  I If you are patching for a production system, then you might want to find  @ a "test" system to load the patches on first, and then run your F "production" load/data on your test box, to uncover any problems.  If I you have no "test" system, you might want to wait a month before loading  G patches.  Occasionally, updates to the patches will appear for various  I reasons (problems not uncovered in regression testing, or missing images   (EXEs)).  H If you are "just" a hobbyist, you probably don't need to be so careful. E   In any case, a backup of the system disk before patching is always   good practice.   ------------------------------  % Date: Thu, 17 Feb 2005 15:23:01 -0500  From: norm.raphael@metso.com$ Subject: Re: 7.32 patching questionsQ Message-ID: <OF93B9ED10.2135E221-ON85256FAB.006F1ED6-85256FAB.00704548@metso.com>   4 tadamsmar@yahoo.com wrote on 02/17/2005 02:44:48 PM:  
 > Looking at:  > 4 > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2 > . > What the heck is MASTER_V732_MASTER_ECOLIST? > 6 > It seems to be a kit, but it is too small to contain6 > everything mentioned in the description .TXT file of@ > the same name. The text seems to describe VMS732_UPDATE-V0300. > 9 > Anyway I just loaded 7.32 from the Oct 03 distribution.  > + > To patch it, I think that I should apply:  >  > 1. VMS732_PCSI-V0100 > 2. VMS732_UPDATE-V0300@ > 3. VMS732_VMSUPD-V0100 (from the mandatory update CD that cameA >    with the recent 8.2 shipment. It is not on the patch site!?) 8 > 4. Any other INSTALL_1 or applicable patches that have( >    come out since VMS732_UPDATE-V0300. > A > Is this a good way to proceed?  I am assuming that UPDATE-V0300 5 > rolls up all the important patches that preceed it.  > ' > Could they make this more confusing??  > 8 That's about correct.  the master list is documentation:  < CURRENT UPDATE KIT                              RELEASE DATE< ------------------                              ------------< VMS732_UPDATE-V0300                              28-OCT-2004     KITS INCLUDED IN UPDATE KIT: ===========================   ; KIT NAME                          RELEASE DATE   SUPERSEDED ; -----------------------------     ------------   ---------- - VMS732_AUDSRV-V0100               31-AUG-2004 5 VMS732_BACKUP-V0200                4-OCT-2004     Yes - VMS732_DCL-V0200                   4-FEB-2004 - VMS732_F11X-V0300                 18-OCT-2004 5 VMS732_FIBRE_SCSI-V0300            4-MAY-2004     Yes - VMS732_GRAPHICS-V0200             26-JAN-2004 - VMS732_HBMM-V0200                 23-SEP-2004 - VMS732_IPC-V0100                   7-SEP-2004 - VMS732_LAN-V0200                  13-APR-2004 - VMS732_LIBRTL-V0100               15-JUL-2004 - VMS732_LMF-V0100                  24-MAY-2004 - VMS732_MANAGE-V0200               10-MAR-2004 - VMS732_MOUNT96-V0100              11-AUG-2004 4 VMS732_PTHREAD-V0100              18-JUL-2004    Yes4 VMS732_RMS-V0100                  11-AUG-2004    Yes- VMS732_RPC-V0300                  20-FEB-2004 - VMS732_SHADOWING-V0200            15-OCT-2004 4 VMS732_SYS-V0500                  24-AUG-2004    Yes- VMS732_SYSLOA-V0200               21-JUL-2004 - VMS732_TDF-V0200                   1-JUN-2004 - VMS732_UPDATE-V0200                1-MAR-2003 - VMS732_XFC-V0100                  22-JUL-2004     < ECO KITS NOT INCLUDED IN UPDATE KIT:   RELEASE DATE COMMENTSH ------------------------------------   ------------ --------------------2 VMS732_SYSINI-V0100                    25-JAN-20052 VMS732_MQ-V0100                        12-JAN-20052 VMS732_BACKUP-V0300                     6-JAN-20052 VMS732_CPU270F-V0100                    4-JAN-20052 VMS732_RMS-V0200                        4-JAN-20052 VMS732_PTHREAD-V0200                    7-DEC-2004J VMS732_FIBRE_SCSI-V0400                 6-DEC-2004  Documentation Modified2 VMS732_SYS-V0600                        6-DEC-20042 VMS732_TRACE-V0200                      1-NOV-20042 VMS732_PCSI-V0100                       3-MAR-2004    7 One patch has been published that is not on here due to  download issues   2 VMS732_DRIVER-V0100                    15-FEB-2005  ; You'll have to check for INSTALL_level and prerequisites to % see if you need all of the last ones.     * The PCSI patch has to go in first and then  ,      7.3  Special Installation Instructions:    ?       o  No reboot is necessary after installation of this kit. G          However, after installation of the kit users will need to take E          one of the following steps to ensure that the new PCSI files           are used:  @           -  Execute the command SET COMMAND SYS$UPDATE:PCSI.CLD  %           -  Log out and log back in.    ------------------------------    Date: 17 Feb 2005 13:00:09 -0800 From: tadamsmar@yahoo.com $ Subject: Re: 7.32 patching questionsB Message-ID: <1108674009.230881.59730@o13g2000cwo.googlegroups.com>   Brad Hamilton wrote: > tadamsmar@yahoo.com wrote: > <snip>; > > Anyway I just loaded 7.32 from the Oct 03 distribution.  > > - > > To patch it, I think that I should apply:  > >  > > 1. VMS732_PCSI-V0100 > > 2. VMS732_UPDATE-V0300B > > 3. VMS732_VMSUPD-V0100 (from the mandatory update CD that cameC > >    with the recent 8.2 shipment. It is not on the patch site!?) : > > 4. Any other INSTALL_1 or applicable patches that have* > >    come out since VMS732_UPDATE-V0300. > > C > > Is this a good way to proceed?  I am assuming that UPDATE-V0300 7 > > rolls up all the important patches that preceed it.  > > ) > > Could they make this more confusing??  > >  > . > I do not know what is contained in number 2.  4 Number 2 is marked INSTALL_1, so that is an argument4 for applying it.  One could argue that the advantage2 of waiting for over a year to install an update is/ so you can get the patches.  On the other hand, / I have only had one minor problem with 7.32 and / no show stoppers so far (1.5 days of operation) / so one could argue that I don't need to fix it.   4 However, I don't see why I would want to do number 4- and not do number 2.  I think I should either 2 (1) apply all the INSTALL_1 patches or (2) install2 only the mandatory security patch and its required4 pre-patches and apply other patches only when I find I need them.  8 Number 2 seems to contain all the INSTALL_1 patches that7 predate it, plus some INSTALL_2 patches that are of the 6 sort that almost everyone would need.  So, number 2 is. pretty much a generic one-step update of 7.32.  9 Number 2 is a big kit that contains all these other kits:   ; KIT NAME                          RELEASE DATE   SUPERSEDED ; -----------------------------     ------------   ---------- - VMS732_AUDSRV-V0100               31-AUG-2004 5 VMS732_BACKUP-V0200                4-OCT-2004     Yes - VMS732_DCL-V0200                   4-FEB-2004 - VMS732_F11X-V0300                 18-OCT-2004 5 VMS732_FIBRE_SCSI-V0300            4-MAY-2004     Yes - VMS732_GRAPHICS-V0200             26-JAN-2004 - VMS732_HBMM-V0200                 23-SEP-2004 - VMS732_IPC-V0100                   7-SEP-2004 - VMS732_LAN-V0200                  13-APR-2004 - VMS732_LIBRTL-V0100               15-JUL-2004 - VMS732_LMF-V0100                  24-MAY-2004 - VMS732_MANAGE-V0200               10-MAR-2004 - VMS732_MOUNT96-V0100              11-AUG-2004 4 VMS732_PTHREAD-V0100              18-JUL-2004    Yes4 VMS732_RMS-V0100                  11-AUG-2004    Yes- VMS732_RPC-V0300                  20-FEB-2004 - VMS732_SHADOWING-V0200            15-OCT-2004 4 VMS732_SYS-V0500                  24-AUG-2004    Yes- VMS732_SYSLOA-V0200               21-JUL-2004 - VMS732_TDF-V0200                   1-JUN-2004 - VMS732_UPDATE-V0200                1-MAR-2003 - VMS732_XFC-V0100                  22-JUL-2004      > Do numbers 1, 3, and 4, E > and then look at the CD, to see if there is anything on the CD that . > supersedes anything you have just installed.   Why 1,3 and 4?  9 3 *is* the only thing on the CD that is applicable. There > are two patches on the CD for 73.2 and one if for DECnet-plus.  ; 3 is only 715 blocks so it can't be covering much territory = in terms of existing patches on the web site.  2 is a whopper  of a patch.    I think maybe you made a typo?   > C > It has been my experience that MUP CD's usually duplicate patches E > appearing on the ECO website.  It is always good practice to check.  > < > While we are on the subject of "best practice" for ECO's - > E > If you are patching for a production system, then you might want to  findA > a "test" system to load the patches on first, and then run your C > "production" load/data on your test box, to uncover any problems.   @ I am upgrading my development system and one "production" system. that is not really in production at this time.  ? I think I am probably OK with the load test of the systems that 9 I am upgrading.  I recognize that the autogen might screw < up the performance of a production system, but our MODPARAMS5 is has stuff that prevented that in the past.  In our 7 environment, we are not working near capacity limits on 8 most parameters, and I think MODPARMS may cover the ones that are important to us.    > IfB > you have no "test" system, you might want to wait a month before loading @ > patches.  Occasionally, updates to the patches will appear for various C > reasons (problems not uncovered in regression testing, or missing  images
 > (EXEs)). > @ > If you are "just" a hobbyist, you probably don't need to be so careful.F >   In any case, a backup of the system disk before patching is always > good practice.   I am not a hobbyist.   ------------------------------  % Date: Thu, 17 Feb 2005 16:08:51 -0500 6 From: Brad Hamilton <brMadAhaPmiSlton@coMmcAasPt.Snet>$ Subject: Re: 7.32 patching questions0 Message-ID: <3YydnV_OttF-mojfRVn-hA@comcast.com>   tadamsmar@yahoo.com wrote: > Brad Hamilton wrote: >  <snip> > Why 1,3 and 4? > ; > 3 *is* the only thing on the CD that is applicable. There @ > are two patches on the CD for 73.2 and one if for DECnet-plus. > = > 3 is only 715 blocks so it can't be covering much territory ? > in terms of existing patches on the web site.  2 is a whopper 
 > of a patch.  >   > I think maybe you made a typo? >     Correct - I  _meant_ to say 2...   <snip>   ------------------------------    Date: 17 Feb 2005 13:15:58 -0800 From: tadamsmar@yahoo.com $ Subject: Re: 7.32 patching questionsC Message-ID: <1108674958.848777.285500@c13g2000cwb.googlegroups.com>    norm.raphael@metso.com wrote: 6 > tadamsmar@yahoo.com wrote on 02/17/2005 02:44:48 PM: >  > > Looking at:  > > 6 > > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2 > > 0 > > What the heck is MASTER_V732_MASTER_ECOLIST? > > 8 > > It seems to be a kit, but it is too small to contain8 > > everything mentioned in the description .TXT file ofB > > the same name. The text seems to describe VMS732_UPDATE-V0300. > > ; > > Anyway I just loaded 7.32 from the Oct 03 distribution.  > > - > > To patch it, I think that I should apply:  > >  > > 1. VMS732_PCSI-V0100 > > 2. VMS732_UPDATE-V0300B > > 3. VMS732_VMSUPD-V0100 (from the mandatory update CD that cameC > >    with the recent 8.2 shipment. It is not on the patch site!?) : > > 4. Any other INSTALL_1 or applicable patches that have* > >    come out since VMS732_UPDATE-V0300. > > C > > Is this a good way to proceed?  I am assuming that UPDATE-V0300 7 > > rolls up all the important patches that preceed it.  > > ) > > Could they make this more confusing??  > > : > That's about correct.  the master list is documentation: > > > CURRENT UPDATE KIT                              RELEASE DATE> > ------------------                              ------------> > VMS732_UPDATE-V0300                              28-OCT-2004 >  >  > KITS INCLUDED IN UPDATE KIT: > ===========================  > = > KIT NAME                          RELEASE DATE   SUPERSEDED = > -----------------------------     ------------   ---------- / > VMS732_AUDSRV-V0100               31-AUG-2004 7 > VMS732_BACKUP-V0200                4-OCT-2004     Yes / > VMS732_DCL-V0200                   4-FEB-2004 / > VMS732_F11X-V0300                 18-OCT-2004 7 > VMS732_FIBRE_SCSI-V0300            4-MAY-2004     Yes / > VMS732_GRAPHICS-V0200             26-JAN-2004 / > VMS732_HBMM-V0200                 23-SEP-2004 / > VMS732_IPC-V0100                   7-SEP-2004 / > VMS732_LAN-V0200                  13-APR-2004 / > VMS732_LIBRTL-V0100               15-JUL-2004 / > VMS732_LMF-V0100                  24-MAY-2004 / > VMS732_MANAGE-V0200               10-MAR-2004 / > VMS732_MOUNT96-V0100              11-AUG-2004 6 > VMS732_PTHREAD-V0100              18-JUL-2004    Yes6 > VMS732_RMS-V0100                  11-AUG-2004    Yes/ > VMS732_RPC-V0300                  20-FEB-2004 / > VMS732_SHADOWING-V0200            15-OCT-2004 6 > VMS732_SYS-V0500                  24-AUG-2004    Yes/ > VMS732_SYSLOA-V0200               21-JUL-2004 / > VMS732_TDF-V0200                   1-JUN-2004 / > VMS732_UPDATE-V0200                1-MAR-2003 / > VMS732_XFC-V0100                  22-JUL-2004  >  > > > ECO KITS NOT INCLUDED IN UPDATE KIT:   RELEASE DATE COMMENTS5 > ------------------------------------   ------------  --------------------4 > VMS732_SYSINI-V0100                    25-JAN-20054 > VMS732_MQ-V0100                        12-JAN-20054 > VMS732_BACKUP-V0300                     6-JAN-20054 > VMS732_CPU270F-V0100                    4-JAN-20054 > VMS732_RMS-V0200                        4-JAN-20054 > VMS732_PTHREAD-V0200                    7-DEC-2004C > VMS732_FIBRE_SCSI-V0400                 6-DEC-2004  Documentation  Modified4 > VMS732_SYS-V0600                        6-DEC-20044 > VMS732_TRACE-V0200                      1-NOV-20044 > VMS732_PCSI-V0100                       3-MAR-2004 >  > 9 > One patch has been published that is not on here due to  > download issues  > 4 > VMS732_DRIVER-V0100                    15-FEB-2005 > = > You'll have to check for INSTALL_level and prerequisites to ' > see if you need all of the last ones.  >  > , > The PCSI patch has to go in first and then > . >      7.3  Special Installation Instructions: >  > A >       o  No reboot is necessary after installation of this kit. D >          However, after installation of the kit users will need to takeG >          one of the following steps to ensure that the new PCSI files  >          are used: > B >           -  Execute the command SET COMMAND SYS$UPDATE:PCSI.CLD > ' >           -  Log out and log back in.     1 So, you think this process would probably be OK?:    1.  apply PCSI-V0100 patch# 2.  SET COMMAND SYS$UPDATE:PCSI.CLD  3.  Log out/in' 4.  apply UPDATE-V0300 mega-patch patch > 5.  apply mandatory security patch from the CD that came w/8.21 6.  review all the patches since UPDATE-V0300 and .     apply any patches that are recommended for'     my configuration of software usage.    ------------------------------  % Date: Thu, 17 Feb 2005 17:14:43 -0500  From: norm.raphael@metso.com$ Subject: Re: 7.32 patching questionsQ Message-ID: <OF33C5BD19.69E72FFA-ON85256FAB.007A04B1-85256FAB.007A7F1C@metso.com>   	 see below   4 tadamsmar@yahoo.com wrote on 02/17/2005 04:15:58 PM:   >  > norm.raphael@metso.com wrote: 8 > > tadamsmar@yahoo.com wrote on 02/17/2005 02:44:48 PM: > >  > > > Looking at:  > > > 8 > > > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2 > > > 2 > > > What the heck is MASTER_V732_MASTER_ECOLIST? > > > : > > > It seems to be a kit, but it is too small to contain: > > > everything mentioned in the description .TXT file ofD > > > the same name. The text seems to describe VMS732_UPDATE-V0300. > > > = > > > Anyway I just loaded 7.32 from the Oct 03 distribution.  > > > / > > > To patch it, I think that I should apply:  > > >  > > > 1. VMS732_PCSI-V0100 > > > 2. VMS732_UPDATE-V0300D > > > 3. VMS732_VMSUPD-V0100 (from the mandatory update CD that cameE > > >    with the recent 8.2 shipment. It is not on the patch site!?) < > > > 4. Any other INSTALL_1 or applicable patches that have, > > >    come out since VMS732_UPDATE-V0300. > > > E > > > Is this a good way to proceed?  I am assuming that UPDATE-V0300 9 > > > rolls up all the important patches that preceed it.  > > > + > > > Could they make this more confusing??  > > > < > > That's about correct.  the master list is documentation: > > @ > > CURRENT UPDATE KIT                              RELEASE DATE@ > > ------------------                              ------------@ > > VMS732_UPDATE-V0300                              28-OCT-2004 > >  > >   > > KITS INCLUDED IN UPDATE KIT: > > ===========================  > > ? > > KIT NAME                          RELEASE DATE   SUPERSEDED ? > > -----------------------------     ------------   ---------- 1 > > VMS732_AUDSRV-V0100               31-AUG-2004 9 > > VMS732_BACKUP-V0200                4-OCT-2004     Yes 1 > > VMS732_DCL-V0200                   4-FEB-2004 1 > > VMS732_F11X-V0300                 18-OCT-2004 9 > > VMS732_FIBRE_SCSI-V0300            4-MAY-2004     Yes 1 > > VMS732_GRAPHICS-V0200             26-JAN-2004 1 > > VMS732_HBMM-V0200                 23-SEP-2004 1 > > VMS732_IPC-V0100                   7-SEP-2004 1 > > VMS732_LAN-V0200                  13-APR-2004 1 > > VMS732_LIBRTL-V0100               15-JUL-2004 1 > > VMS732_LMF-V0100                  24-MAY-2004 1 > > VMS732_MANAGE-V0200               10-MAR-2004 1 > > VMS732_MOUNT96-V0100              11-AUG-2004 8 > > VMS732_PTHREAD-V0100              18-JUL-2004    Yes8 > > VMS732_RMS-V0100                  11-AUG-2004    Yes1 > > VMS732_RPC-V0300                  20-FEB-2004 1 > > VMS732_SHADOWING-V0200            15-OCT-2004 8 > > VMS732_SYS-V0500                  24-AUG-2004    Yes1 > > VMS732_SYSLOA-V0200               21-JUL-2004 1 > > VMS732_TDF-V0200                   1-JUN-2004 1 > > VMS732_UPDATE-V0200                1-MAR-2003 1 > > VMS732_XFC-V0100                  22-JUL-2004  > >  > > @ > > ECO KITS NOT INCLUDED IN UPDATE KIT:   RELEASE DATE COMMENTS7 > > ------------------------------------   ------------  > --------------------6 > > VMS732_SYSINI-V0100                    25-JAN-20056 > > VMS732_MQ-V0100                        12-JAN-20056 > > VMS732_BACKUP-V0300                     6-JAN-20056 > > VMS732_CPU270F-V0100                    4-JAN-20056 > > VMS732_RMS-V0200                        4-JAN-20056 > > VMS732_PTHREAD-V0200                    7-DEC-2004E > > VMS732_FIBRE_SCSI-V0400                 6-DEC-2004  Documentation 
 > Modified6 > > VMS732_SYS-V0600                        6-DEC-20046 > > VMS732_TRACE-V0200                      1-NOV-20046 > > VMS732_PCSI-V0100                       3-MAR-2004 > >  > > ; > > One patch has been published that is not on here due to  > > download issues  > > 6 > > VMS732_DRIVER-V0100                    15-FEB-2005 > > ? > > You'll have to check for INSTALL_level and prerequisites to ) > > see if you need all of the last ones.  > >  > > . > > The PCSI patch has to go in first and then > > 0 > >      7.3  Special Installation Instructions: > >  > > C > >       o  No reboot is necessary after installation of this kit. F > >          However, after installation of the kit users will need to > take  I > >          one of the following steps to ensure that the new PCSI files    Note:  one of the following....    > >          are used: > > D > >           -  Execute the command SET COMMAND SYS$UPDATE:PCSI.CLD > > ) > >           -  Log out and log back in.  >  > 3 > So, you think this process would probably be OK?:  >  > 1.  apply PCSI-V0100 patch  0 Step 2 or step 3, although both wouldn't hurt ;)  % > 2.  SET COMMAND SYS$UPDATE:PCSI.CLD  > 3.  Log out/in  ) > 4.  apply UPDATE-V0300 mega-patch patch @ > 5.  apply mandatory security patch from the CD that came w/8.23 > 6.  review all the patches since UPDATE-V0300 and 0 >     apply any patches that are recommended for) >     my configuration of software usage.  >  That will "probably be OK."    ------------------------------  # Date: Thu, 17 Feb 2005 22:24:50 GMT # From: Beach Runner <bob@nospam.com> $ Subject: Re: 7.32 patching questions; Message-ID: <SQ8Rd.90040$qB6.36748@tornado.tampabay.rr.com>   F Excuse the top posting, but if you have update 3 installed, you really# should install VMS732_SYSINI-V0100.    tadamsmar@yahoo.com wrote:   > norm.raphael@metso.com wrote:  > 6 >>tadamsmar@yahoo.com wrote on 02/17/2005 02:44:48 PM: >> >> >>>Looking at: >>> 5 >>>ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2  >>> / >>>What the heck is MASTER_V732_MASTER_ECOLIST?  >>> 7 >>>It seems to be a kit, but it is too small to contain 7 >>>everything mentioned in the description .TXT file of A >>>the same name. The text seems to describe VMS732_UPDATE-V0300.  >>> : >>>Anyway I just loaded 7.32 from the Oct 03 distribution. >>> , >>>To patch it, I think that I should apply: >>>  >>>1. VMS732_PCSI-V0100  >>>2. VMS732_UPDATE-V0300 A >>>3. VMS732_VMSUPD-V0100 (from the mandatory update CD that came B >>>   with the recent 8.2 shipment. It is not on the patch site!?)9 >>>4. Any other INSTALL_1 or applicable patches that have ) >>>   come out since VMS732_UPDATE-V0300.  >>> B >>>Is this a good way to proceed?  I am assuming that UPDATE-V03006 >>>rolls up all the important patches that preceed it. >>> ( >>>Could they make this more confusing?? >>>  >>: >>That's about correct.  the master list is documentation: >>> >>CURRENT UPDATE KIT                              RELEASE DATE> >>------------------                              ------------> >>VMS732_UPDATE-V0300                              28-OCT-2004 >> >> >>KITS INCLUDED IN UPDATE KIT: >>===========================  >>= >>KIT NAME                          RELEASE DATE   SUPERSEDED = >>-----------------------------     ------------   ---------- / >>VMS732_AUDSRV-V0100               31-AUG-2004 7 >>VMS732_BACKUP-V0200                4-OCT-2004     Yes / >>VMS732_DCL-V0200                   4-FEB-2004 / >>VMS732_F11X-V0300                 18-OCT-2004 7 >>VMS732_FIBRE_SCSI-V0300            4-MAY-2004     Yes / >>VMS732_GRAPHICS-V0200             26-JAN-2004 / >>VMS732_HBMM-V0200                 23-SEP-2004 / >>VMS732_IPC-V0100                   7-SEP-2004 / >>VMS732_LAN-V0200                  13-APR-2004 / >>VMS732_LIBRTL-V0100               15-JUL-2004 / >>VMS732_LMF-V0100                  24-MAY-2004 / >>VMS732_MANAGE-V0200               10-MAR-2004 / >>VMS732_MOUNT96-V0100              11-AUG-2004 6 >>VMS732_PTHREAD-V0100              18-JUL-2004    Yes6 >>VMS732_RMS-V0100                  11-AUG-2004    Yes/ >>VMS732_RPC-V0300                  20-FEB-2004 / >>VMS732_SHADOWING-V0200            15-OCT-2004 6 >>VMS732_SYS-V0500                  24-AUG-2004    Yes/ >>VMS732_SYSLOA-V0200               21-JUL-2004 / >>VMS732_TDF-V0200                   1-JUN-2004 / >>VMS732_UPDATE-V0200                1-MAR-2003 / >>VMS732_XFC-V0100                  22-JUL-2004  >> >>> >>ECO KITS NOT INCLUDED IN UPDATE KIT:   RELEASE DATE COMMENTS5 >>------------------------------------   ------------  >  > -------------------- > 4 >>VMS732_SYSINI-V0100                    25-JAN-20054 >>VMS732_MQ-V0100                        12-JAN-20054 >>VMS732_BACKUP-V0300                     6-JAN-20054 >>VMS732_CPU270F-V0100                    4-JAN-20054 >>VMS732_RMS-V0200                        4-JAN-20054 >>VMS732_PTHREAD-V0200                    7-DEC-2004C >>VMS732_FIBRE_SCSI-V0400                 6-DEC-2004  Documentation  > 
 > Modified > 4 >>VMS732_SYS-V0600                        6-DEC-20044 >>VMS732_TRACE-V0200                      1-NOV-20044 >>VMS732_PCSI-V0100                       3-MAR-2004 >> >>9 >>One patch has been published that is not on here due to  >>download issues  >>4 >>VMS732_DRIVER-V0100                    15-FEB-2005 >>= >>You'll have to check for INSTALL_level and prerequisites to ' >>see if you need all of the last ones.  >> >>, >>The PCSI patch has to go in first and then >>. >>     7.3  Special Installation Instructions: >> >>A >>      o  No reboot is necessary after installation of this kit. D >>         However, after installation of the kit users will need to >  > take > G >>         one of the following steps to ensure that the new PCSI files  >>         are used: >>B >>          -  Execute the command SET COMMAND SYS$UPDATE:PCSI.CLD >>' >>          -  Log out and log back in.  >  >  > 3 > So, you think this process would probably be OK?:  >  > 1.  apply PCSI-V0100 patch% > 2.  SET COMMAND SYS$UPDATE:PCSI.CLD  > 3.  Log out/in) > 4.  apply UPDATE-V0300 mega-patch patch @ > 5.  apply mandatory security patch from the CD that came w/8.23 > 6.  review all the patches since UPDATE-V0300 and 0 >     apply any patches that are recommended for) >     my configuration of software usage.  >    ------------------------------  # Date: Fri, 18 Feb 2005 03:58:05 GMT   From: John Santos <john@egh.com>$ Subject: Re: 7.32 patching questions+ Message-ID: <hJdRd.37536$Dc.26545@trnddc06>    tadamsmar@yahoo.com wrote: > norm.raphael@metso.com wrote:  > 6 >>tadamsmar@yahoo.com wrote on 02/17/2005 02:44:48 PM: >> >> >>>Looking at: >>> 5 >>>ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2  >>> / >>>What the heck is MASTER_V732_MASTER_ECOLIST?  >>> 7 >>>It seems to be a kit, but it is too small to contain 7 >>>everything mentioned in the description .TXT file of A >>>the same name. The text seems to describe VMS732_UPDATE-V0300.   > All the kit contains is the text file.  It is the current list> of released ECO's.  The version you are looking at seems to be> the one published immediately after UPDATE-V0300 was released,= which superseded all the earlier ECO's (except PCSI-V0100, so 7 that should have been listed in the text file as well.)          >>> : >>>Anyway I just loaded 7.32 from the Oct 03 distribution. >>> , >>>To patch it, I think that I should apply: >>>  >>>1. VMS732_PCSI-V0100  >>>2. VMS732_UPDATE-V0300 A >>>3. VMS732_VMSUPD-V0100 (from the mandatory update CD that came B >>>   with the recent 8.2 shipment. It is not on the patch site!?)9 >>>4. Any other INSTALL_1 or applicable patches that have ) >>>   come out since VMS732_UPDATE-V0300.  >>> B >>>Is this a good way to proceed?  I am assuming that UPDATE-V03006 >>>rolls up all the important patches that preceed it. >>> ( >>>Could they make this more confusing?? >>>  >>: >>That's about correct.  the master list is documentation: >>> >>CURRENT UPDATE KIT                              RELEASE DATE> >>------------------                              ------------> >>VMS732_UPDATE-V0300                              28-OCT-2004 >> >> >>KITS INCLUDED IN UPDATE KIT: >>===========================  >>= >>KIT NAME                          RELEASE DATE   SUPERSEDED = >>-----------------------------     ------------   ---------- / >>VMS732_AUDSRV-V0100               31-AUG-2004 7 >>VMS732_BACKUP-V0200                4-OCT-2004     Yes / >>VMS732_DCL-V0200                   4-FEB-2004 / >>VMS732_F11X-V0300                 18-OCT-2004 7 >>VMS732_FIBRE_SCSI-V0300            4-MAY-2004     Yes / >>VMS732_GRAPHICS-V0200             26-JAN-2004 / >>VMS732_HBMM-V0200                 23-SEP-2004 / >>VMS732_IPC-V0100                   7-SEP-2004 / >>VMS732_LAN-V0200                  13-APR-2004 / >>VMS732_LIBRTL-V0100               15-JUL-2004 / >>VMS732_LMF-V0100                  24-MAY-2004 / >>VMS732_MANAGE-V0200               10-MAR-2004 / >>VMS732_MOUNT96-V0100              11-AUG-2004 6 >>VMS732_PTHREAD-V0100              18-JUL-2004    Yes6 >>VMS732_RMS-V0100                  11-AUG-2004    Yes/ >>VMS732_RPC-V0300                  20-FEB-2004 / >>VMS732_SHADOWING-V0200            15-OCT-2004 6 >>VMS732_SYS-V0500                  24-AUG-2004    Yes/ >>VMS732_SYSLOA-V0200               21-JUL-2004 / >>VMS732_TDF-V0200                   1-JUN-2004 / >>VMS732_UPDATE-V0200                1-MAR-2003 / >>VMS732_XFC-V0100                  22-JUL-2004  >> >>> >>ECO KITS NOT INCLUDED IN UPDATE KIT:   RELEASE DATE COMMENTS5 >>------------------------------------   ------------u >  > -------------------- > 4 >>VMS732_SYSINI-V0100                    25-JAN-20054 >>VMS732_MQ-V0100                        12-JAN-20054 >>VMS732_BACKUP-V0300                     6-JAN-20054 >>VMS732_CPU270F-V0100                    4-JAN-20054 >>VMS732_RMS-V0200                        4-JAN-20054 >>VMS732_PTHREAD-V0200                    7-DEC-2004C >>VMS732_FIBRE_SCSI-V0400                 6-DEC-2004  Documentation  > 
 > Modified > 4 >>VMS732_SYS-V0600                        6-DEC-20044 >>VMS732_TRACE-V0200                      1-NOV-20044 >>VMS732_PCSI-V0100                       3-MAR-2004 >> >>9 >>One patch has been published that is not on here due tos >>download issuesf >>4 >>VMS732_DRIVER-V0100                    15-FEB-2005 >>= >>You'll have to check for INSTALL_level and prerequisites to ' >>see if you need all of the last ones.s >> >>, >>The PCSI patch has to go in first and then >>. >>     7.3  Special Installation Instructions: >> >>A >>      o  No reboot is necessary after installation of this kit.eD >>         However, after installation of the kit users will need to >  > take > G >>         one of the following steps to ensure that the new PCSI filese >>         are used: >>B >>          -  Execute the command SET COMMAND SYS$UPDATE:PCSI.CLD >>' >>          -  Log out and log back in.  >  >  > 3 > So, you think this process would probably be OK?:  >  > 1.  apply PCSI-V0100 patch% > 2.  SET COMMAND SYS$UPDATE:PCSI.CLDn > 3.  Log out/in  E Do one of 2 or 3.  There is no need to do both.  (As the instructionss above clearly say.)a    ) > 4.  apply UPDATE-V0300 mega-patch patche@ > 5.  apply mandatory security patch from the CD that came w/8.23 > 6.  review all the patches since UPDATE-V0300 ande0 >     apply any patches that are recommended for) >     my configuration of software usage.y   -- d John Santoso Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------    Date: 17 Feb 2005 14:59:44 -0800! From: susan_skonetski@hotmail.com 4 Subject: Dallas-Fort Worth LUG Meeting - February 25C Message-ID: <1108681184.794958.136840@z14g2000cwz.googlegroups.com>   E Please Save the Date - The Encompass Board of Directors wants to meet-
 the DFWLUG  G The Encompass Board of Directors will be in Dallas-Fort Worth on Friday-E evening, February 25, and would like the opportunity to meet with thes? members of the DFWLUG and Dallas-Fort Worth Encompass community G members. This informal networking event will take place at the SheratontG Grand Hotel near DFW airport from 6 p.m. - 7:30 p.m. and is open to theiC Encompass community.  Please feel free to stop by for complimentaryfF appetizers and beverages.  The Board and Hewlett-Packard are committedD to the support of the Local User Groups, so take this opportunity toF talk to your Board and HP about future support of the DFWLUG and other@ issues important to you, while catching up with old friends.  In1 addition, future DFWLUG events will be announced.t   When:a Friday, February 25, 2005I 6:00 p.m. - 7:30 p.m.p   Where:' Sheraton Grand Hotel (near DFW airport)0 4440 W. John Carpenter Freeway Irving, Texas 75063 G (Southeast corner of Hwy. 114 and Esters Blvd. on the North side of the  airport)  / Please RSVP or forward questions to Dena Wright-2 (dena.wright@encompassUS.org) or Katie Diestelkamp= (katie.diestelkamp@encompassUS.org) at Encompass Headquartersj  . We're looking forward to seeing you in Dallas!  # Encompass director & DFWLUG member,a Dena Wrighto dena.wright@encompassUS.orgj   ------------------------------  % Date: Thu, 17 Feb 2005 12:34:35 -0500t& From: Jilly <jilly@clarityconnect.com>< Subject: Re: DCL command to show number of interactive usersB Message-ID: <1108667699.f8f0a0c802bbb047774932f92abbc079@teranews>   bob@instantwhip.com wrote:   > anyone know any? >  > $ ?1  I There may be multiple ways to report this based on what you believe is an K interactive user and how a system is managed.  This is the reason why there J is no single item for this.  For example, do you have all users log in viaI the same username?  do you have users that log in multiple times?  do youmI have users that share usernames?  do you have users that startup detached G DECTerms?  etc. etc.  Figuring out how your system is used and defining J what an interactive user is for your environment will then lead you to the proper way to report this item.t   -- cB Jilly - Working from Home in the Chemung River Valley, Waverly, NYF       - jilly@stny.rr.com                http://home.stny.rr.com/jillyE       - mark.jilson@hp.com               http://www.hp.com/go/openvms ;       - http://www.jilsonracing.com      Go Fast, Turn LeftbC       - http://www.chemungspeedrome.com  Door Handle to Door Handle    ------------------------------  % Date: Thu, 17 Feb 2005 16:56:20 -0500r# From: "John Smith" <a@nonymous.com> ( Subject: Dvorak on IA64 & Opteron & Cell, Message-ID: <Ppydndp0aJabjojfRVn-qQ@igs.net>  3 http://www.pcmag.com/article2/0,1759,1760523,00.aspn   --- OpenVMS - The classics never go out of style.g   ------------------------------  % Date: Thu, 17 Feb 2005 15:21:47 -0500,# From: "John Smith" <a@nonymous.com>o, Subject: Re: HP financials: Alpha sales down, Message-ID: <DIKdnW5h94NBYYnfRVn-qw@igs.net>   From the 8-K filing2       Technology Solutions Group  G The Technology Solutions Group (TSG) consists of Enterprise Storage andtE Servers, Software and HP Services. The group reported revenue of $8.1sL billion, up 14% from the prior-year period. Operating profit for the quarterL totaled $312 million, or 3.9% of revenue, down from $365 million, or 5.2% of revenue, year-over-year.  L "TSG posted strong top line results for the quarter, but we continue to faceH ongoing margin pressure due to pricing and product mix, as well as costsG associated with workforce reductions. We are actively managing our costmK structure to achieve improved profitability," said Ann Livermore, ExecutivenL Vice President, HP's Technology Solutions Group. "In this highly competitiveJ environment, I'm especially proud of the strong top line we achieved in HPH Services, which continues to grow faster than the market and our leading
 competitors."c   Enterprise Storage and Servers  L Enterprise Storage and Servers (ESS) reported revenue of $4.0 billion, up 9%H over the prior-year period. On a year-over-year basis, industry-standardE server revenue increased 19%, business-critical systems (BCS) revenue0H declined 2% and networked storage revenue was down 1%. Within BCS, HP-UXL revenue growth of 3% year-over-year was more than offset by NonStop declinesH of 19% and ongoing declines in AlphaServer sales. ESS reported operatingI profit of $71 million for the quarter, or 1.8% of revenue, down from $1530! million in the prior-year period.       B [what I find interesting in this is: a) no mention of Itanic salesK specifically, b) that they would report a 19% decline in NSK but NOT assign D a figure to the decline in Alpha sales - which to me could either beJ negligible - but they reported small declines in network storage (-1%) andJ in HP-UX (-3%),  - so the only conclusion I can draw from the reticence to< report Alpha sales is that they have fallen off a cliff.  NoK surprise...that's what happens when you kill a chip and you don't advertise  the OS that runs on it.]   HP Services1  K HP Services (HPS) revenue grew 20% year-over-year to a record $3.8 billion.0L On a year-over-year basis, Managed Services revenue grew 44%, Consulting andK Integration grew 20% and Technology Services grew 14%. Operating profit wasYC $281 million, or 7.4% of revenue, compared with $261 million in the  prior-year period.   Software  G Software reported quarterly revenue of $240 million, an increase of 18% D year-over-year. HP OpenView revenue increased 16% year-over-year. HPG OpenCall revenue was up 22%. Software reported an operating loss of $40-F million, compared with a loss of $49 million in the prior-year period.       --- OpenVMS - The classics never go out of style.U   ------------------------------  # Date: Thu, 17 Feb 2005 22:17:32 GMT 1 From: Keith Parris <keithparris_NOSPAM@yahoo.com> , Subject: Re: HP financials: Alpha sales down/ Message-ID: <0K8Rd.266$77.192@news.cpqcorp.net>    JF Mezei wrote:- > Robert Deininger wrote:d >>AlphaServer = VMS + Tru64. > G > I would have though that Tru64 sales would have completely stabilisedMH > (to a very low level) some time ago. Wouldn't VMS sales have accountedJ > for the vast majority of Alpha sales in the last year or two since Tru649 > was officially without any future since Sept 7th 2001 ?r >SI > The fact that HP killed the port of TruCluster to HP-UX wouldn't really ' > have affected Tru64 sales, would it ?h  D Tru64 wasn't killed outright in 2001 -- it has followed the roadmap D outlined then and has had several releases, a whole line of new EV7 B boxes, plus EV7z upgrades, and support continues into the future. C Companies with investments in and plans charted around using Tru64 eE wouldn't have been able to change course immediately, and HP's plans CH were intended to give them a gradual period for transition. But we have E certainly been seeing the numbers indicate reductions in Alpha sales uG revenues for Tru64 for a number of quarters in a row. And gains on the o? VMS side aren't enough to make up for all of the Tru64 decline.@  E There are also other factors involved. Alpha hardware costs less now  G than before, and for more-powerful machines. Itanium is the now on the  D table as competition for Alpha sales, and Itanium system prices are E lower. While this means exceptional value for the money for VMS (and eD Tru64) customers, it means lower revenue and profit numbers for HP. B Opponents may use these lower numbers to falsely say VMS is dying.  G I remember in the early '90s, when UNIX was getting a lot of hype, and h@ the price for new VMS systems was lowered so the price would be F identical whether a box ran VMS or UNIX. This immediately resulted in H lower revenue numbers for VMS, which UNIX proponents (even some Digital 9 VPs) immediately jumped on as "proof" that VMS was dying.u  G Also, the majority of VMS' sizeable contributions to HP's revenues and oC profits are found not in BCS, but in this area: "HP Services (HPS) i? revenue grew 20% year-over-year to a record $3.8 billion. On a oH year-over-year basis, Managed Services revenue grew 44%, Consulting and H Integration grew 20% and Technology Services grew 14%. Operating profit H was $281 million, or 7.4% of revenue, compared with $261 million in the F prior-year period." Based on past experience, one could estimate that F roughly 15% of the revenues and 25% of the profits here were from VMS.   ------------------------------  # Date: Thu, 17 Feb 2005 22:23:53 GMTh1 From: Keith Parris <keithparris_NOSPAM@yahoo.com>d, Subject: Re: HP financials: Alpha sales down. Message-ID: <ZP8Rd.267$H6.56@news.cpqcorp.net>   John Smith wrote:  > From the 8-K filingE  D It's nice to see "Open VMS" [sic] mentioned specifically in the 10K ( filing, albeit without specific numbers.    From HP's 10-K filing: G http://www.hp.com/hpinfo/investor/financials/annual/2004/hp2004_10k.pdfeF "Business Critical Servers. Business critical servers include Reduced F Instruction Set Computing ("RISC")-based servers running on the HP-UX G operating system, Itanium-based servers running on HP-UX, Windows and 0I Linux and the HP AlphaServer product line running on both Tru64 UNIX and 2
 Open VMS."  F Of course we'll have to change the wording for next quarter, now that ; 8.2 has shipped and VMS will also be being sold on Itanium.    ------------------------------    Date: 17 Feb 2005 14:31:41 -0800* From: "AndyB" <andrew.buss@btinternet.com>, Subject: Re: HP financials: Alpha sales downB Message-ID: <1108679501.953916.44210@g14g2000cwa.googlegroups.com>  + >From HP presentation accompanying webcast:0  B BCS was 22% ($US 880 million) of $US 4 billion Servers and storage revenue in Q1 FY05 ISS was 58% ($US 2.3 billion)2! Storage was 20% ($US 800 million)    Integrity was up 50% Y/Y; Integrity made up 18% of BCS revenues now ($US 158 million) D This is approx 7% of the value of the ISS market (starting to become significant)   Cheers         John Smith wrote:t > From the 8-K filingh >  >  >e > Technology Solutions Group >?E > The Technology Solutions Group (TSG) consists of Enterprise Storage  andeG > Servers, Software and HP Services. The group reported revenue of $8.1sF > billion, up 14% from the prior-year period. Operating profit for the quarteriF > totaled $312 million, or 3.9% of revenue, down from $365 million, or 5.2% ofh > revenue, year-over-year. >CF > "TSG posted strong top line results for the quarter, but we continue to facedD > ongoing margin pressure due to pricing and product mix, as well as costsrD > associated with workforce reductions. We are actively managing our costC > structure to achieve improved profitability," said Ann Livermore,h	 Executive B > Vice President, HP's Technology Solutions Group. "In this highly competitivegF > environment, I'm especially proud of the strong top line we achieved in HP B > Services, which continues to grow faster than the market and our leadinge > competitors."  >u  > Enterprise Storage and Servers >e? > Enterprise Storage and Servers (ESS) reported revenue of $4.0r billion, up 9%8 > over the prior-year period. On a year-over-year basis, industry-standardoG > server revenue increased 19%, business-critical systems (BCS) revenue D > declined 2% and networked storage revenue was down 1%. Within BCS, HP-UXeE > revenue growth of 3% year-over-year was more than offset by NonStopn declines@ > of 19% and ongoing declines in AlphaServer sales. ESS reported	 operatingeF > profit of $71 million for the quarter, or 1.8% of revenue, down from $153# > million in the prior-year period.e >o >  > D > [what I find interesting in this is: a) no mention of Itanic salesF > specifically, b) that they would report a 19% decline in NSK but NOT assignF > a figure to the decline in Alpha sales - which to me could either beB > negligible - but they reported small declines in network storage	 (-1%) and-? > in HP-UX (-3%),  - so the only conclusion I can draw from ther reticence to> > report Alpha sales is that they have fallen off a cliff.  NoC > surprise...that's what happens when you kill a chip and you don'tt	 advertise3 > the OS that runs on it.] > 
 > HP Services  > D > HP Services (HPS) revenue grew 20% year-over-year to a record $3.8 billion.? > On a year-over-year basis, Managed Services revenue grew 44%,a Consulting andB > Integration grew 20% and Technology Services grew 14%. Operating
 profit wasE > $281 million, or 7.4% of revenue, compared with $261 million in the  > prior-year period. >i
 > Software >eE > Software reported quarterly revenue of $240 million, an increase ofo 18%pF > year-over-year. HP OpenView revenue increased 16% year-over-year. HPE > OpenCall revenue was up 22%. Software reported an operating loss ofa $40/@ > million, compared with a loss of $49 million in the prior-year period.  >  >  >  > --/ > OpenVMS - The classics never go out of style.t   ------------------------------  % Date: Thu, 17 Feb 2005 20:34:20 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> , Subject: Re: HP financials: Alpha sales downB Message-ID: <1108689740.a2fe884f8fe5c8e76a357342819c742c@teranews>   John Smith wrote:CM > specifically, b) that they would report a 19% decline in NSK but NOT assigna) > a figure to the decline in Alpha sales e  C Note that the NSK sales vary a lot in percentage. When you have lowSE volume where each sale is big, then your sales figures can vary widlyD@ without really indicating health or sickness.  When Tandem was aF company, its financials also varied quite a bit. One need to look at aD full year,s worth of data and compare it to previous years to see if there is any trend.e  F VMS is on its way there too, with only 660 customer left that matter.   L > in HP-UX (-3%),  - so the only conclusion I can draw from the reticence to; > report Alpha sales is that they have fallen off a cliff. 2  @ Actually, I woudln't be surprised to see the opposite. HP may beD reticent to publish Alpha figures because perhaps they are doing farF better than they would have wanted Alpha to do. If VMS sales did rise,D consider why HP wouldn't want to give Wall Street some good news andG instead would focus on a drop in Alpha sales. That is the big question.   F > year-over-year. HP OpenView revenue increased 16% year-over-year. HPI > OpenCall revenue was up 22%. Software reported an operating loss of $400H > million, compared with a loss of $49 million in the prior-year period.  K So much for arguments that HP never reports individual product performance.    ------------------------------  % Date: Thu, 17 Feb 2005 20:49:33 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> , Subject: Re: HP financials: Alpha sales downB Message-ID: <1108690659.c2f011649d044f4d3401b04c25c4c092@teranews>   Keith Parris wrote:8) > Tru64 wasn't killed outright in 2001 --   A Tru64 was the first casualty announced just after Carly and CurlyF' announced their engagement on Sept 7th.   H > revenues for Tru64 for a number of quarters in a row. And gains on theA > VMS side aren't enough to make up for all of the Tru64 decline.   D Has Tru64 decline increasted recently, or has it been fairly gradual since Sept 2001 ?C  H > than before, and for more-powerful machines. Itanium is the now on theE > table as competition for Alpha sales, and Itanium system prices are- > lower.  G IA64 sales aren't really a facort in the past quarter. Alsop, Since VMSAC runs only on a small subset of IA64 boxes, what percentage of those2A remaining 660 customers can more substantial parts of their Alpha0F systems to IA64 today ? Won't they have to wait at least a year before  VMS is available on Superdomes ?   ------------------------------  % Date: Thu, 17 Feb 2005 20:41:25 -0500 ( From: Bill Todd <billtodd@metrocast.net>, Subject: Re: HP financials: Alpha sales down= Message-ID: <L6mdnX6mtJxY2ojfRVn-jA@metrocastcablevision.com>7   Keith Parris wrote:    ...   I > Also, the majority of VMS' sizeable contributions to HP's revenues and e1 > profits are found not in BCS, but in this area:   H Indeed.  And given that VMS sales aren't even close to holding up their G end, the service revenues will inevitably follow them down hill - just  F with an obvious time-lag comparable to the installed lifetimes of the  system involved.     "HP Services (HPS)A > revenue grew 20% year-over-year to a record $3.8 billion. On a  J > year-over-year basis, Managed Services revenue grew 44%, Consulting and J > Integration grew 20% and Technology Services grew 14%. Operating profit J > was $281 million, or 7.4% of revenue, compared with $261 million in the H > prior-year period." Based on past experience, one could estimate that H > roughly 15% of the revenues and 25% of the profits here were from VMS.  @ The 'past experience' you are basing this on would appear to be I pre-Alphacide experience (very much as that perpetual '411,000 installed eF systems' seems to be), unless you're asserting that the Alphacide had C very little effect in this area:  I could have believed that a few uI months or even a year or more after the event (due to the time-lag noted  D above), but it seems rather less believable coming up on its fourth  anniversary.   - bill   ------------------------------  % Date: Thu, 17 Feb 2005 22:33:35 -0500o) From: "Neil Rieck" <n.rieck@sympatico.ca>0, Subject: Re: HP financials: Alpha sales down; Message-ID: <cmdRd.24461$4I5.1121503@news20.bellglobal.com>8  ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message .< news:1108690659.c2f011649d044f4d3401b04c25c4c092@teranews...   [...snip...]    Alpha sales are only down at HP.  I In December-2004 my employer purchased two used AS-DS20e machines from a  I used equipment vendor and we quickly realized we were in the middle of a bM bidding war. The vendor told us that used Alpha sales were up 150% (whatever  K that means) since September 2004 with no end in sight coming. This started  B us to speculate: "Did this have anything to do with the announced M End-of-Life of Alpha?". Were others thinking things like "Gee, Itanium boxes hK are coming out now but I'd like to wait for the technology to mature a bit SH so I'll by myself some time by purchasing used Alphas?" If any of these L speculations are even partly true, it makes you wonder why Compaq/HP didn't E do the IBM thing and be a little more secretive when it comes to EOL   statements etc.o    
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.8 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html   ------------------------------  % Date: Thu, 17 Feb 2005 23:19:42 -0500-' From: Dave Froble <davef@tsoft-inc.com>-, Subject: Re: HP financials: Alpha sales down0 Message-ID: <111aqlvk2sd8laf@corp.supernews.com>   John Smith wrote:   D > [what I find interesting in this is: a) no mention of Itanic salesM > specifically, b) that they would report a 19% decline in NSK but NOT assign-F > a figure to the decline in Alpha sales - which to me could either beL > negligible - but they reported small declines in network storage (-1%) andL > in HP-UX (-3%),  - so the only conclusion I can draw from the reticence to> > report Alpha sales is that they have fallen off a cliff.  NoM > surprise...that's what happens when you kill a chip and you don't advertise  > the OS that runs on it.]  E Don't forget that T64 was sold on more Alphas than VMS, and not only  A wasn't it advertised, it also was killed, and the final nail was 5E reneging on moving capabilities to HP-UX.  Nobody in or out of their 73 right mind would buy a T64 box.  There's the cliff.2   Dave   ------------------------------  % Date: Fri, 18 Feb 2005 00:25:06 -0500J- From: JF Mezei <jfmezei.spamnot@teksavvy.com> , Subject: Re: HP financials: Alpha sales downB Message-ID: <1108703574.ca06a809a2325e23ac79206de0e41c16@teranews>   Dave Froble wrote:F > Don't forget that T64 was sold on more Alphas than VMS, and not onlyB > wasn't it advertised, it also was killed, and the final nail wasF > reneging on moving capabilities to HP-UX.  Nobody in or out of their5 > right mind would buy a T64 box.  There's the cliff.   B On Jun 25 2001, all Tru64 customers knew Alpha was dead and that a6 migration to a different platform was going to happen.  H On Sept 7th 2001 (or a day or two later), Vurly and Carly announced thatG Tru64 was dead and not ported to IA64, so all Tru64 customers knew thatB? in long term theymd have to migrate to another OS AND platform.1  H Now, HP may have recently announced the obvious (that they wouldn't portH Tru64 features to HP-UX) but would this really have made a difference to Tru64 customers' plans ?    F Now, in 2001, Tru64 customers were told to start to migrate to anotherE OS before HP had a viable solution to offer. I reckon many would have D begnun strategic decision of where to go and begin gradual migrationF process. This begins by adding any new application to the new platform% and slowly migrate the "legacy" ones.M    D If a "cliff" recently appeared with Alpha sales tanking big time, itG would have been as a result of the 2001 announcements taking time to gof@ from strategic decisions to final cutting of ties between formerH customer and HP.  If a legacy application on Tru64/Alpha needs increasedG capacity, it is still easier to just buy more alphas to handle the load G until the application is ported. On the other hand, as applications are C ported, it does free up some capacity. But in some cases, it may benH simpler to keep everything together and move all at once , once all apps3 that talek to each other have been migrated/tested.M   ------------------------------  % Date: Thu, 17 Feb 2005 19:39:33 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>1 Subject: Re: I'd heard about this a while back...2+ Message-ID: <42154755.4E8A685F@comcast.net>    Bob Koehler wrote: > k > In article <newscache$f5o0ci$fao$1@news.sil.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:p > >f* > > No company likes 'proprietary things'. > . >    Microsoft would be suprised to hear that.  D Micro$lop is not "proprietary" - it's "industry standard", remember?   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/t  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/a   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  # Date: Fri, 18 Feb 2005 03:29:28 GMT   From: John Santos <john@egh.com>6 Subject: Re: linux kernel has major security flaws ...+ Message-ID: <sidRd.37533$Dc.19722@trnddc06>p   bob@instantwhip.com wrote:5 > how can people even seriously consider running this   > garbage when vms is out there? > + > http://www.theinquirer.net/?article=21295p  D I'm certainly not a Linux expert, and am not trying to defend it but just to be fair...  E The 1st (of 4) security flaw described says you can access supposedly D secure data if you (as an unprivileged user) have read access to theC swap area or physical access to the machine.  I've never heard of ad@ system that encrypts the swap area (maybe there are systems thatD encrypt *everything* on the disk, and so encrypt the swap area), butC other than that, doesn't having read access to the swap area and/or = physical access to the system violate security on any system?3  4 VMS page and swap files belong to [SYSTEM] and have C (o:rwed,s:rwed,g:,w:) protection.  Non-SYSPRV users don't have reads. access to them, and shouldn't on Linux either.  2 And we all know that physical access is right out.  - Larry K (if you haven't kill-filed Bob C.)???    --   John Santos- Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------    Date: 17 Feb 2005 23:40:09 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) 6 Subject: Re: linux kernel has major security flaws ...3 Message-ID: <dv4GsPAP0zhu@eisner.encompasserve.org>>  N In article <sidRd.37533$Dc.19722@trnddc06>, John Santos <john@egh.com> writes: > bob@instantwhip.com wrote:6 >> how can people even seriously consider running this! >> garbage when vms is out there?  >> M, >> http://www.theinquirer.net/?article=21295 > F > I'm certainly not a Linux expert, and am not trying to defend it but > just to be fair... > G > The 1st (of 4) security flaw described says you can access supposedly0F > secure data if you (as an unprivileged user) have read access to theE > swap area or physical access to the machine.  I've never heard of aNB > system that encrypts the swap area (maybe there are systems thatF > encrypt *everything* on the disk, and so encrypt the swap area), butE > other than that, doesn't having read access to the swap area and/orC? > physical access to the system violate security on any system?  > 6 > VMS page and swap files belong to [SYSTEM] and have E > (o:rwed,s:rwed,g:,w:) protection.  Non-SYSPRV users don't have readM0 > access to them, and shouldn't on Linux either. > 4 > And we all know that physical access is right out. > / > Larry K (if you haven't kill-filed Bob C.)???I  3 The point is that I have not killfiled John Santos.   A The question I would ask (also not as a Linux expert) is how easy-D it is for the unprivileged user to get read access to the swap area.A If this is the installation default or similarly easy to achieve,C! then I think the hole is genuine.-  E As you point out, physical access beats all, even if it means leavingVC a hardware device to intercept the key which is used to encrypt the  page and swap file :-)   ------------------------------  # Date: Fri, 18 Feb 2005 00:40:39 GMT 5 From: rdeininger@mindspringdot.com (Robert Deininger) : Subject: Re: Looking for suggestions for bootcamp sessionsL Message-ID: <rdeininger-1702051940410001@user-uinj43q.dialup.mindspring.com>  C In article <1108657785.912704.210460@o13g2000cwo.googlegroups.com>, " kenneth.randell@verizon.net wrote:   ...    >EE >While we are at this, is it possible to change the SCSI ID's/bus fortD >the 3 internal drives on the rx26x0?  They handily come up as DKA0,F >DKA100, and DKB200 which I guess is why external drive shelves aren't8 >supported on the 68-pin plug on the back on the rx26x0?  G No, the SCSI IDs are built into the SCSI backplane.  IDs 0 and 1 on oneiB SCSI bus, ID 2 on the other bus (which is shared with the external connector).s   ------------------------------    Date: 17 Feb 2005 11:07:16 -0800 From: tadamsmar@yahoo.comM: Subject: Re: mandatory 7.32 update (in 8.2 ship) questionsC Message-ID: <1108667236.025936.297170@l41g2000cwc.googlegroups.com>e   norm.raphael@metso.com wrote:06 > tadamsmar@yahoo.com wrote on 02/17/2005 10:50:38 AM: >u > >  > > tadamsmar@yahoo.com wrote:2 > > > There is a mandatory update CD for 7.32 that) > > > comes with the recent 8.2 shipment.t > > >h8 > > > But, reading the .txt files in the 7.32 directory,8 > > > it seems that one needs to apply VMS732_PCSI_V01000 > > > patch before applying the patch on the CD.7 > > > However, this preliminary patch is not on the CD.@6 > > > And, the patch does not seem to be in any of the > > > quaterlies since 7.32. > > > 1 > > > So, I guess I have to go to the web to findc3 > > > the preliminary patch that is required before2, > > > I apply the patch available on the CD. > > >p* > > > Or did I overlook something? Was the, > > > VMS732_PCSI_V0100 patch sent in one of > > > the quarterlies? > > >m0 > > > Also, they did not ship a mentioned DECnet4 > > > phase IV patch required to get the full effect4 > > > of the upgrade, but this is a lessor sin since5 > > > not everybody is not running phase IV, I guess.. > >i1 > > Well, the DECnet phase IV patch mentioned is:  > >r$ > > DEC-AXPVMS-DNVOSIMUP01-V0703-2-4 > >  > > Is not available here: > >s6 > > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2 >P > >0/ > Well, it probably should be here, but is not:t >l? > ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/  >  > and IIRC DNVOSI is phase V.a >  > You should e-mailo >  > George PagliaruloM > ECO Release Process   > OpenVMS Sustaining Engineering > Hewlett-Packard Companyd > 110 Spit Brook Roadm > Nashua, New Hampshire 03062h > Tel# (603)884-1000" > e-mail: george.pagliarulo@hp.com  , Phase V!  I misread that.  Did not even know there was a phase V.  ! So, not a problem for my upgrade.o   ------------------------------  % Date: Thu, 17 Feb 2005 19:38:22 -0600o2 From: David J Dachtera <djesys.nospam@comcast.net>* Subject: Re: Mounting disks during STARTUP+ Message-ID: <4215470E.5182510E@comcast.net>t   Bart Zorn wrote: > H > Not really. If you find a disk which appears to be a shadowset member,C > you can mount it with the /INCLUDE qualifier and it will find its  > fellow members automatically.4  # Has anyone seen that actually work?:   -- = David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:-" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/C  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Thu, 17 Feb 2005 19:47:32 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>" Subject: Re: Need performance help+ Message-ID: <42154934.2021278F@comcast.net>    Kenneth Farmer wrote:L > : > Please email this guy directly if you're able to assist. > " > Rajat.Gupta(at)gb.vodafone.co.uk > 8 > I've also posted in OpenVMS Tech forum on OpenVMS.org: > : > http://www.openvms.org/phorum/read.php?f=1&i=1533&t=1533 > 	 > Hello ,7 > K > Thank you very much for the reponse. I want to know of any profiling tool + > avalaible for openVMS like gprof on unix.  > N > Actually I have a process that gives a performance of 20000 transactions perN > sec on linux machine but gives only 3000 transactions on an OpenVMS platformJ > with maximum CPU utilization. I want to get hold of the limiting issues.  E Look into using Extended File Cache, and make sure your disk units on 9 your storage arrays are set with writeback cache enabled.T   --   David J Dachtera dba DJE Systems- http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:-" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/V   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Thu, 17 Feb 2005 18:41:19 -0500 , From: "warren sander" <warren.sander@hp.com>& Subject: OpenVMS 8.2 docs and freeware, Message-ID: <42152be4$1@usenet01.boi.hp.com>  . The OpenVMS 8.2 docs are new up and available. http://h71000.www7.hp.com/docM  / the OpenVMS Freeware V7 is now up and available>- http://h71000.www7.hp.com/freeware/freeware70t? for ftp download of the disks that expand into backup save sets  ftp://ftp.hp.com/pub/openvms   ------------------------------    Date: 17 Feb 2005 23:35:33 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) * Subject: Re: OpenVMS 8.2 docs and freeware3 Message-ID: <uDyJyfLtgR3Z@eisner.encompasserve.org>   [ In article <42152be4$1@usenet01.boi.hp.com>, "warren sander" <warren.sander@hp.com> writes: 0 > The OpenVMS 8.2 docs are new up and available. > http://h71000.www7.hp.com/doc   E From here in Massachusetts, the 8.2 link gets me a page that says 8.2eE at the top but has only a column for 7.3-2.  The one manual I checkedC; (Guide to System Security, of course) is the 7.3-2 version.    ------------------------------   Date: 17 Feb 2005 18:53:44 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)= Subject: Re: OpenVMS Cluster to Replace News.Individual.NET ?i, Message-ID: <37k7hoF5f8r6dU1@individual.net>  , In article <Ks6dnYGcuKLgIonfRVn-rA@igs.net>,& 	"John Smith" <a@nonymous.com> writes: > M > I recall seeing the same data, probably in one of the inForm newsletters inU > the mid/late-90's. > F > It's probably worth dusting off an Alpha and loading VMS, Linux, andK > possibly Tru64 on separate boot disks and doing the tests again if for no0N > other reason that if a favorable result is found (+/- 1-2%) it could be usedJ > in closed-door discussions with the 660 accounts that HP talks about VMS > with.    @ I would suggest including FreeBSD in that test as well.  I can't@ speak for Tru64 but I wouldn't place any money on the efficiency of Linux IO either.G   bill   -- sJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   i   ------------------------------   Date: 17 Feb 05 14:55:06 EST) From: cook@wvnvms.wvnet.edu (George Cook)o= Subject: Re: OpenVMS Cluster to Replace News.Individual.NET ?f! Message-ID: <SEAwYjefU40i@wvnvms>a  U In article <cv2hah$o7a$1@naig.caltech.edu>, David Mathog <mathog@caltech.edu> writes:i > Main, Kerry wrote:F >> I would agree that the "VMS IO is slower" is one of those old wives= >> tales based on experiences with older versions of OpenVMS.d >> n > C > Note, for those of you who have forgotten just how poorly VMS did,& > in these tests google in groups for: > " >    mathog blade ds10 mybenchmark > F > and select the one with the subject: blade vs. DS10 on "mybenchmark" > H > These results are also in the download link I posted earlier, but this. > will save you the trouble of unzipping that.  A I may be misunderstanding your data, but the greatest part of thea@ slowness appears related to file create/open/close?  If so, thisA would closely match our experience with ANUNEWS vs. DNEWS as newsWC servers.  ANUNEWS is very file create/open/close intense (e.g. each-@ article is stored in a separate file) whereas DNEWS is the exact> opposite.  ANUNEWS was a total I/O dog (caused nightmares justA handling one feed) while DNEWS just purrs along handling multipleb? feeds.  I have never even had to check how much I/O DNEWS does,? nor do any type of I/O tuning.  C VMS is not automatically always slower on I/O.  It has a great deal . to do with how the application is implemented.     George Cook  WVNETi   ------------------------------  % Date: Fri, 18 Feb 2005 05:13:28 +0800e From: prep@prep.synonet.com = Subject: Re: OpenVMS Cluster to Replace News.Individual.NET ?r- Message-ID: <87r7jec2kn.fsf@prep.synonet.com>   ) David Mathog <mathog@caltech.edu> writes:    > Main, Kerry wrote:  F >> I would agree that the "VMS IO is slower" is one of those old wives= >> tales based on experiences with older versions of OpenVMS.n  F > Note, for those of you who have forgotten just how poorly VMS did in# > these tests google in groups for:.  " >    mathog blade ds10 mybenchmark  F > and select the one with the subject: blade vs. DS10 on "mybenchmark"  C > These results are also in the download link I posted earlier, but.3 > this will save you the trouble of unzipping that.-  E David, if you take a broken IO design and do a brain-dead port of it,"C what do you expect... If you do it RIGHT, vms will pound unix IO to-G pulp. That is why unix is now getting such new ideas as MMIO and Direct7 IO. ;|  D A News server is a notorious system killer. google for `i-node hack'C for an intro. The normal news implementation uses a simplistic file B design to store articles, and hammers file creation to a pulp. The 50 GB/day is also problematic.  @ There is already a reasonable News server for VMS, ANU News, and@ it has had several updates and overhauls by <some one who's name? I should be able to remember> in it's comercial supported form.T     -- r< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.l@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------    Date: 17 Feb 2005 13:09:02 -0800! From: susan_skonetski@hotmail.comeY Subject: OpenVMS Pearl - Datamation Article Names HP OpenVMS servers in top 5 best of 04 oB Message-ID: <1108674542.180942.39970@l41g2000cwc.googlegroups.com>  B This may be the best OpenVMS Pearl since we announced on IntegrityC Servers.  It is wonderful to be recognized by the industry for BOTHc Alpha and Integrity Servers.  3 http://www.cioupdate.com/trends/article.php/3469701e    G StorageTek's Streamline SL500 Modular Library System was the big winner G in the Enterprise Server category, gaining more than twice the votes of @ runner-up IBM's p5 Series. JBoss Inc.'s JBoss Application ServerC finished third, with NetManage Inc.'s RUMBA and HP's OpenVMS OS fora. Alpha, VAX and Integrity Servers close behind.  C Could you do me a favor and just this once not get negative on thist< posting even the announcment of the VTJ managed to get down.   Thanks Sue    ------------------------------    Date: 17 Feb 2005 15:50:53 -0800 From: jordan@ccs4vms.comY Subject: Re: OpenVMS Pearl - Datamation Article Names HP OpenVMS servers in top 5 best ofeB Message-ID: <1108684253.792254.28090@o13g2000cwo.googlegroups.com>  E > Could you do me a favor and just this once not get negative on thisH> > posting even the announcment of the VTJ managed to get down.  ! I'm sorry :(  Its hard sometimes.e   !!!!!l  % Go VMS!  Industry recognition = good!h& Positive industry recognition = great!   ------------------------------  % Date: Thu, 17 Feb 2005 20:37:23 -0500H- From: JF Mezei <jfmezei.spamnot@teksavvy.com> Y Subject: Re: OpenVMS Pearl - Datamation Article Names HP OpenVMS servers in top 5 best ofdB Message-ID: <1108689924.1c7152031f95cce1d4f87c7281b8fca5@teranews>  " susan_skonetski@hotmail.com wrote:E > finished third, with NetManage Inc.'s RUMBA and HP's OpenVMS OS fora0 > Alpha, VAX and Integrity Servers close behind. > E > Could you do me a favor and just this once not get negative on this > > posting even the announcment of the VTJ managed to get down.  F OK, great news !!! VAX is listed ahead of Integrity !!!!!! :-) :-) :-) :-) :-) :-) :-)-  ( (Sorry Sue, I really couldn't resist :-)   ------------------------------  % Date: Thu, 17 Feb 2005 19:59:55 -060012 From: David J Dachtera <djesys.nospam@comcast.net>' Subject: OpenVMS Small Partner Strategy + Message-ID: <42154C1A.1513A2EF@comcast.net>8  F O.k. I've got the kernel of an idea. I can usually count on this groupD to pick such things apart down to the sub-atomic level, so let's see what anyone thinks of this:e  F hp/VMS has this unrealistic thing about $1-megabuck in volume per yearG for "qualified resellers". Great for super-size VARs and resellers, badr for us "little guys".    So, here's what I was thinking:   * 1. Identify existing "qualified resellers"$ 2. Establish relationships with themH 3. Enlist their support to negotiate with hp for support of (or at leastC non-interference with) a multi-tiered distribution network with thenC "qualified resellers" near the top, and us "bottom feeders" furtherz down.e? 4. We order VMS, Alphas and I64 machines through the "qualifiedm resellers" as our sales happen.u  < Seems to me, this can be sold (to hp) because all sides win.  ' Comments? Commendations? Condemnations?    -- g David J Dachtera dba DJE Systemse http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:a" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/e  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/l   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Thu, 17 Feb 2005 22:18:39 -0500n- From: JF Mezei <jfmezei.spamnot@teksavvy.com> + Subject: Re: OpenVMS Small Partner StrategyoB Message-ID: <1108695997.47a59d765eef7c295e80206e2fd84fec@teranews>   David J Dachtera wrote: H > hp/VMS has this unrealistic thing about $1-megabuck in volume per yearI > for "qualified resellers". Great for super-size VARs and resellers, bad  > for us "little guys".   D The argument in favour of this policy is ensuring quality control ofH vendors and making sure that anyone making a pitch to a customer has had, full training by Digital/Compaq/HP/whatever.  G The problem is that ever since the Palmer years, they have used this asMC a barrier to selling VMS instead of as a facilitator to doing greato+ sales and recruiting more VMS salespersons.)    , > 1. Identify existing "qualified resellers"& > 2. Establish relationships with them> > 3. Enlist their support to negotiate with hp for support of   A One would have to know if the contracts between the vendor and HP2H require that only "employees" with full HP training/accreditation handle
 VMS sales.  H If there is no such restriction, then you could negotaite with Island orC whoever some deal where you get a cut fo sales you generate. Nut if-N there are contract restrictions, the vendors may not be able to do such deals.   (But yes, it is a good idea).:  @ The problem is that tiny vendors such as you and I cannot make aG convincing sales pitch without the support of HP and by that, I mean:  c MARKETING AND ADVERTISING.  H If I go to a bank and pitch a VMS solution, I will be laughed at. But ifA HP advertises VMS and banks become curious at VMS, then they willc welcome my presentations..   ------------------------------  % Date: Thu, 17 Feb 2005 23:54:53 -0500 ' From: Dave Froble <davef@tsoft-inc.com>d+ Subject: Re: OpenVMS Small Partner Strategyt0 Message-ID: <111asntpq6nfo36@corp.supernews.com>   David J Dachtera wrote:AH > O.k. I've got the kernel of an idea. I can usually count on this groupF > to pick such things apart down to the sub-atomic level, so let's see > what anyone thinks of this:  > H > hp/VMS has this unrealistic thing about $1-megabuck in volume per yearI > for "qualified resellers". Great for super-size VARs and resellers, bad: > for us "little guys".  > ! > So, here's what I was thinking:4 > , > 1. Identify existing "qualified resellers"& > 2. Establish relationships with themJ > 3. Enlist their support to negotiate with hp for support of (or at leastE > non-interference with) a multi-tiered distribution network with thenE > "qualified resellers" near the top, and us "bottom feeders" furthero > down.8A > 4. We order VMS, Alphas and I64 machines through the "qualifiedi! > resellers" as our sales happen.s > > > Seems to me, this can be sold (to hp) because all sides win. > ) > Comments? Commendations? Condemnations?y >   D Why not just form a combine of all the small VARs and such?  If the B total of sales through the combine exceeds the $1M then it should  qualify as a reseller.  G Ok, who's going to do all the paperwork?  Another idea shot in the ass.r   Dave   ------------------------------    Date: 17 Feb 2005 20:47:18 -0800; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com>e1 Subject: OT: Message to Peter "EPLAN" LANGSTOEGERsB Message-ID: <1108702038.711081.70250@z14g2000cwz.googlegroups.com>  G Thank you very much for the links.  Looks like they will get me started  on Alpha VMS 8.2 quite nicely.  G I've tried to send this to you several times, however, I guess your ISPuE has my Yahoo mail address blocked.  At least that is what is seems tol be from the return message.e   Message from  yahoo.com.7 Unable to deliver message to the following address(es).o     <peter@langstoeger.at>: ' 194.177.158.65 does not like recipient.eC Remote host said: 550 Programmed rejection for source host/address.i Giving up on 194.177.158.65.    F Sorry for posting here. I didn't know any other way of getting through0 and I didn't want you to think I was ungrateful.     John H. Reinhardt    ------------------------------  % Date: Thu, 17 Feb 2005 20:18:23 -0600r2 From: David J Dachtera <djesys.nospam@comcast.net>+ Subject: Port Print facility Update for I64e+ Message-ID: <4215506E.797B6A04@comcast.net>n  ' See http://www.djesys.com/freeware/vms/,  
 ppf012.zip  F The Port Print Facility provides a simple way of "queueing" text filesF for printing through the printer port of a VT terminal, or through the+ printer of a PC running a terminal program.   G Port Print Facility V1.2B has been compiled for I64. The new archive atwG the above URL now includes an object library for I64 as well as for VAXe
 and Alpha.  F Just download the archive, expand it, and invoke LINK_PPF.COM. The OLB. appropriate to your platform will be selected.  F Thanx to the maintainers of the test-drive cluster site for the use of the IA64 machine.c   --   David J Dachtera dba DJE Systemsa http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:r" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/a  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/4   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Thu, 17 Feb 2005 12:30:26 -0500a& From: Jilly <jilly@clarityconnect.com>( Subject: Re: Queue Length on shadow diskB Message-ID: <1108667698.70df3002aa27152886089349768ff670@teranews>   bill@wcschmidt.com wrote:s  @ > I have a strange problem with a queue length on a shadow drive >  > DSA1:                  WORKi > $ > Current    Ave      Min        Max) > 27218.00   27171.73 18145.33   27218.00f > G > using monitor disk/item=queue_length, I see this queue length and can  > not believe it.z > & > Any ideas as to where the issue is ? > I > When do I a show device/files nothing is open other than the index.sys.a > F > With ana/sys sho dev dsa1: nothing unusual here with no i/o requests
 > pending. > F > I'm using VMS 7.2 with all the latest patchs, I even checked to make7 > sure that the latest for shadowing has been installede > 
 > any ideas ?S >  > Thanks > Bill Schmidt  K Known issue with the upkeep of UCB$L_QLEN item.  Best you can do is to make K sure you are at the latest and greatest patches for your version of VMS and.I when there is a quiet period for the disk use SYS$SHARE:DELTA to zero outsJ the field.  If you can get this to happen under V8.2 then please report it to the CSC.o   -- tB Jilly - Working from Home in the Chemung River Valley, Waverly, NYF       - jilly@stny.rr.com                http://home.stny.rr.com/jillyE       - mark.jilson@hp.com               http://www.hp.com/go/openvmst;       - http://www.jilsonracing.com      Go Fast, Turn LeftpC       - http://www.chemungspeedrome.com  Door Handle to Door Handle    ------------------------------    Date: 17 Feb 2005 19:23:22 -0500/ From: brooks@cuebid.zko.dec.nospam (Rob Brooks)d( Subject: Re: Queue Length on shadow disk- Message-ID: <1Fc4aIj8pjzA@cuebid.zko.dec.com>n  ( Jilly <jilly@clarityconnect.com> writes: > bill@wcschmidt.com wrote:e  A >> I have a strange problem with a queue length on a shadow drive$ >> l >> DSA1:                  WORK >> m% >> Current    Ave      Min        Max * >> 27218.00   27171.73 18145.33   27218.00 >> -H >> using monitor disk/item=queue_length, I see this queue length and can >> not believe it.  G >> I'm using VMS 7.2 with all the latest patchs, I even checked to make08 >> sure that the latest for shadowing has been installed  aM > Known issue with the upkeep of UCB$L_QLEN item.  Best you can do is to make M > sure you are at the latest and greatest patches for your version of VMS andeK > when there is a quiet period for the disk use SYS$SHARE:DELTA to zero out L > the field.  If you can get this to happen under V8.2 then please report it
 > to the CSC.n  I Yes, this is to be expected IF the devices are multipath. If they're not  H multipath, then I'm pretty sure that ucb$l_qlen is correctly maintained.  E If you are using multipath devices, I STRONGLY urge you to upgrade tooF at least V7.3-1; many significant changes to multipath device handlingD were added for V7.3-1.  Of course, upgrading to V8.2 or V7.3-2 would be even better.n   ---uM Rob Brooks    VMS Engineering -- I/O Exec Group     brooks!cuebid.zko.dec.com'   ------------------------------    Date: 17 Feb 2005 21:31:59 -0800% From: andrew.rycroft@intrinsitech.com-% Subject: Rdb - monitor home directory0C Message-ID: <1108704719.406016.127950@g14g2000cwa.googlegroups.com>a   Hi,h  : SWe are running Oracle Rdb v7.0.7 in a cluste environment,   Sometime we see the message :-  9 -RDMS-F-NOMONHOMEDIR, monitor home directory is not validu: -DECEDI-I-INFO, Error from SQL when setting transaction in STARTUP_REC_RIPPLES.  3 What logical points to the monitor home directroy ?o   With regards Andrew   ------------------------------  + Date: Fri, 18 Feb 2005 06:52:23 +0000 (UTC)i3 From: "Richard Maher" <maher_rj@hotspamnotmail.com> ) Subject: Re: Rdb - monitor home directoryP/ Message-ID: <cv43b7$gg4$1@titan.btinternet.com>    try RDM$MONITOR    Regards Richard Maher   2 <andrew.rycroft@intrinsitech.com> wrote in message= news:1108704719.406016.127950@g14g2000cwa.googlegroups.com...g > Hi,  > < > SWe are running Oracle Rdb v7.0.7 in a cluste environment, >i  > Sometime we see the message :- >n; > -RDMS-F-NOMONHOMEDIR, monitor home directory is not validt< > -DECEDI-I-INFO, Error from SQL when setting transaction in > STARTUP_REC_RIPPLES. >a5 > What logical points to the monitor home directroy ?n >( > With regards > Andrew >4   ------------------------------  % Date: Thu, 17 Feb 2005 22:25:18 +0100 - From: Marc Van Dyck <marc.vandyck@brutele.be>: Subject: Re: SLS dead 0 Message-ID: <mn.8d417d52c610498a.584@brutele.be>  # denny a prsent l'nonc suivant : G > I have been told several times by HP support people that ABS "ArchiveiH > Backup System for OpenVMS" is the product to migrate to.  They make noH > excuses for SLS, and have told me several times that bugs i found will > not be fixed.s >lI > They say the SLS license will work for ABS. They say that conversion is8I > "painless" (like waking up in a tub of icewater to discover you kidneys6
 > are gone!).d >fI > We are on V2.9H. As soon as I get some free time, I'm going to copy our 9 > volume database and see what happens when I convert it.S >2 > So my questions are, >    have you looked at ABS?# >    Is ABS going to be maintained?fF >    And if SLS is really dead, why don't they let us hobbyists have a > license for it?m
 > regards, >t > denny4  D We have tried a migration to ABS 5 years ago, it took months, and we> had to revert to SLS at the end. We use SLS in a very complex  environment,G with StorageTek Silos, high performance drives, TDSystems muxes, and sokA on. ABS can't drive that stuff. At least it couldn't last time weo0 tried. Has it much changed in the last 5 years ?  A And also, I'm afraid of the future of ABS too, since it seems to / compete D a lot with this 'data protector' stuff that H.P. has ported from itsE Unix world. Can both products survive on the long term ? Can we trustn H.P. if they answer "yes" ?y  C Legato would probably work, but we've adopted Veritas for Unix and - WintelE 4 years ago. Having both in the same shop doesn't look quite right...i    So, still no clear path ahead...   --  
 Marc Van Dycks   ------------------------------  % Date: Thu, 17 Feb 2005 22:27:48 +0100a- From: Marc Van Dyck <marc.vandyck@brutele.be>o Subject: Re: SLS deadf0 Message-ID: <mn.8d437d5294d6bb41.584@brutele.be>  . David J Dachtera a prsent l'nonc suivant : > Wayne Sewell wrote:  >> u >>> From: <Usenet> >>> X-Newsgroups: comp.os.vmsl >>> Subject: SLS deado) >>> Date: Fri, 11 Feb 2005 17:03:34 +0100  >>> X-Priority: 3a >>> X-MSMail-Priority: Normal  >> t >>> E >>> From the last OpenVMS roadmap PDF document, dated february 2005 :h >>> N >>> Storage Library System V2.9J (Q1 2005) will contain support for VMS V7.3-2 >>> L >>> and V8.2 on Alpha Only. Subsequent releases will concentrate on remedial
 >>> fixes anda >>> N >>> support for new versions of OpenVMS. There will be no support for new tape >>> devicesu >>> M >>> after V2.9H timeframe, and no new features will be introduced. No port to- >>> Integrity is >>>  >>> planned. >>>  >>> M >>> This looks like a complete change of directions for this product. And for ! >>> me, it looks like a disaster,g/ >>> specially the decision to abandon the port.6 >>> O >>> I got this info from the abovementionned PDF document, distributed to me inV >>> through an unofficialiL >>> channel. The info did not appear anywhere else I know. But kindlt asked, >>> H.P. confirmed. HowNA >>> many other customers are impacted but still not aware of it ?s >>> I >>> A fellow H.P. employee urged me to write my concerns and disagreementa >>> directly to Mark Gorham,J >>> which I will do. Perhaps other impacted customers should do the same ? >>>  >>>  >>> Marc Van Dyck. >>>  >> aM >> The TAPESYS port to itanium is in progress.  The itanium builds have been a" >> done, now in the testing stage. >> 1O >> This is the closest functional equivalent to SLS, though it is a third-party6O >> product.  The original SLS actually *was* TAPESYS, taken from a snapshot of mL >> an much earlier version.  The two products have diverged since then, but   >> still have many similarities. > F > If/when Cerner gets the "warm fuzzies" for whatever Enterprise ClassF > Itanic machines, looks like I'll be talking to you and your folks atI > SP32 for on-going support of our backups using StorageTek libraries, if / > SLS on I64 is not to be. (ABS is not usable.)l  G We'll have to get in touch, then... You and me seem to be using more oro< less the same stuff (powderhorns, eagle drives, omniserves).   -- n
 Marc Van Dycke   ------------------------------  % Date: Thu, 17 Feb 2005 19:37:40 -0600c2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: SLS deadl+ Message-ID: <421546E3.8DD2CCD8@comcast.net>    Marc Van Dyck wrote: > 0 > David J Dachtera a prsent l'nonc suivant : > > Wayne Sewell wrote:  > >> > >>> From: <Usenet> > >>> X-Newsgroups: comp.os.vmsc > >>> Subject: SLS dead + > >>> Date: Fri, 11 Feb 2005 17:03:34 +0100- > >>> X-Priority: 3- > >>> X-MSMail-Priority: Normal: > >> > >>> G > >>> From the last OpenVMS roadmap PDF document, dated february 2005 :d > >>>tP > >>> Storage Library System V2.9J (Q1 2005) will contain support for VMS V7.3-2 > >>> N > >>> and V8.2 on Alpha Only. Subsequent releases will concentrate on remedial > >>> fixes andO > >>>rP > >>> support for new versions of OpenVMS. There will be no support for new tape
 > >>> devices  > >>>aO > >>> after V2.9H timeframe, and no new features will be introduced. No port to  > >>> Integrity is > >>>  > >>> planned. > >>>e > >>>/O > >>> This looks like a complete change of directions for this product. And for/# > >>> me, it looks like a disaster,e1 > >>> specially the decision to abandon the port.i > >>>VQ > >>> I got this info from the abovementionned PDF document, distributed to me ine > >>> through an unofficial-N > >>> channel. The info did not appear anywhere else I know. But kindlt asked, > >>> H.P. confirmed. HowjC > >>> many other customers are impacted but still not aware of it ?d > >>>DK > >>> A fellow H.P. employee urged me to write my concerns and disagreementu > >>> directly to Mark Gorham,L > >>> which I will do. Perhaps other impacted customers should do the same ? > >>>  > >>>l > >>> Marc Van Dyck. > >>>n > >>N > >> The TAPESYS port to itanium is in progress.  The itanium builds have been$ > >> done, now in the testing stage. > >>Q > >> This is the closest functional equivalent to SLS, though it is a third-party P > >> product.  The original SLS actually *was* TAPESYS, taken from a snapshot ofM > >> an much earlier version.  The two products have diverged since then, butt" > >> still have many similarities. > >eH > > If/when Cerner gets the "warm fuzzies" for whatever Enterprise ClassH > > Itanic machines, looks like I'll be talking to you and your folks atK > > SP32 for on-going support of our backups using StorageTek libraries, if'1 > > SLS on I64 is not to be. (ABS is not usable.)x > I > We'll have to get in touch, then... You and me seem to be using more oro> > less the same stuff (powderhorns, eagle drives, omniserves).  E Actually, L700e's, SDLT-1s. Sharing two libraries (no pass-thru - SLS-, chokes on that) with Novell and W2K servers.   -- e David J Dachtera dba DJE Systemsu http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:4" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/i  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/n   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Fri, 18 Feb 2005 04:54:55 +0800  From: prep@prep.synonet.comy* Subject: Re: Speed of light as speed limit- Message-ID: <87zmy2c3fk.fsf@prep.synonet.com>y  & "AEF" <spamsink2001@yahoo.com> writes:    F > Just as an aside, if you go to http://www.feynman.com, you can watchF > several hours worth of video of Feynman giving the QED lectures on a@ > trial basis in New Zealand! You need real player to view it. I > highly recommend it.  ( This is going to bugger the buget again!   There a real player for VMS?   -- t< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.e@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------   Date: 17 FEB 2005 19:53:33 GMT+ From: Dave Greenwood <greenwoodde@ornl.gov>k Subject: Re: Status of devices2 Message-ID: <17FEB05.19533380@feda01.fed.ornl.gov>  > In a previous article, Paul Sture <paul.sture@decus.ch> wrote: > bhushann@gmail.com wrote:C >  n* > > Thank you for your prompt reply Mezei.K > > What I am looking for is, how to obtain all the other states the devicec1 > > could be in other than mount and not mounted.  > >  >  s# > $ help lexical f$getdvi arguments- >  -7 > and look at the item list. Most are self explanatory.g  C That's true (eg: exists, avl, mnt), but there are also a few statese? (eg: MntVerify, MntVerifyTimeout) that don't have explicit item1' codes.  Here are the states I look for:      $ sts = f$getdvi(vol,"sts")19   $ if (sts .and. %x0010) .eq. %x0010 then ...   ! Onlineo<   $ if (sts .and. %x4000) .eq. %x4000 then ...   ! MntVerifyC   $ if (sts .and. %x0800) .eq. %x0800 then ...   ! MntVerifyTimeoutx   Dave --------------9 Dave Greenwood                Email: Greenwoodde@ORNL.GOVrH Oak Ridge National Lab        %STD-W-DISCLAIMER, I only speak for myself   ------------------------------  % Date: Thu, 17 Feb 2005 19:44:31 -060012 From: David J Dachtera <djesys.nospam@comcast.net>, Subject: Re: TCPIP automatic route additions+ Message-ID: <4215487F.ADF4E7FD@comcast.net>0   DeanW wrote: > G > I have a customer with a somewhat mis-configured network. Clients are)C > connecting to the VMS box via a router that normally shouldn't berD > passing that traffic- and when they do, TCPIP (5.0a) automaticallyA > adds a route back to that client's subnet through the incorrectrH > router, which then prevents all the rest of the clients on that subnet! > from connecting the proper way.  > E > It's a simple installation, with not dynamic routing enabled on theaE > VMS side (or anywhere, if they're following my suggestion- but they G > did just bring a high-priced network consultant in, which is probably@4 > how we got this mess in the first place... *sigh*) > - > Anyway, the routing table should look like:  >  > $ tcpip sho routeh > & >                              DYNAMIC > > > Type           Destination                           Gateway > 8 > DN    0.0.0.0                               172.16.1.17 > DH    127.0.0.1                             127.0.0.1l8 > AN    172.16.0.0/22                         172.16.1.4: > DN    <external_net>/24                      172.16.1.10 > $ tcpip sho route /permh > ( >                              PERMANENT > > > Type           Destination                           Gateway > 8 > PN    0.0.0.0                               172.16.1.17 > PH    127.0.0.1                             127.0.0.1/8 > PN    172.16.0.0/22                         172.16.1.48 > PN    <external_net>/28                    172.16.1.10 > $. > D > The trouble comes when something connects from 192.168.0.x via theB > firewall at 172.16.1.10 instead of coming in through the defaultG > router (172.16.1.1) Solving this issue is going to take some time, asrF > it's sporradic (usually once or twice a month) but crippling when it2 > happens, until the incorrect routes get removed. > N > Is there a way to have TCPIP not automatically add routes that I don't want? > B > If I put a permanent route in for 192.168.0/24 to go through theD > default router, will that defeat the automatic routes being added?D > (I'm dubious- note that the permenant route to the external net is7 > correct, the dynamic one has an incorrect bitmask...)   3 Look in the doc. / on-line help under STOP ROUTING.a  F Dunno if you have to do that on every boot, or if you can configure it off.   --   David J Dachtera dba DJE Systemsa http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho//  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32//   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Fri, 18 Feb 2005 05:17:26 +0800a From: prep@prep.synonet.com- Subject: Re: [OT:] Biometrics5- Message-ID: <87mzu2c2e1.fsf@prep.synonet.com>s  % "John Smith" <a@nonymous.com> writes:e  E > a recent report by IDG's News Service in London. The collected dataaD > from millions of citizens would be deposited in a massive databaseF > called the National Identification Register under a plan expected to* > cost up to 5.5-billion ($12.8-billion).  B Any one want to be in a sweepstake for how long till some unwashed; off's the data? And how much over cost and late it will be!    -- p< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.o@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  # Date: Thu, 17 Feb 2005 23:22:06 GMTeL From: winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing)Y Subject: Re: [OT] Speed of light as speed limit (was Re: DECW$CLOCK design flaw   flaw   i6 Message-ID: <00A3F88C.E76E16E0@SSRL.SLAC.STANFORD.EDU>  K In article <87vf8qc37j.fsf@prep.synonet.com>, prep@prep.synonet.com writes:a* >"Main, Kerry" <kerry.main@hp.com> writes: >i >>> -----Original Message-----8 >>> From: Ken Fairfield [mailto:my.full.name@intel.com] # >>> Sent: February 16, 2005 8:08 PMh >>> To: Info-VAX@Mvb.Saic.Comc= >>> Subject: Re: [OT] Speed of light as speed limit (was Re:  $ >>> DECW$CLOCK design flaw flaw flaw >a# >> [snip lots of physics stuff ...]  >h: >>> I don't speak for Intel, Intel doesn't speak for me... >  >>> Ken Fairfieldf% >>> D1C Automation VMS System Supportk& >>> who:   kenneth dot h dot fairfield >>> where: intel dot com > G >> Wow - it's amazing what backgrounds some folks have lurking in their # >> resumes besides techie IT stuff.n > - >Have you forgotten that Ken is an ex SLACer?s >-; >I wonder how many VMS systems still remain in the HEP labs2 >anymore :(e  J Can't speak for HEP generally.  Use of VMS systems has certainly shrunk inN peripheral functions at SLAC - the mail gateway systems are now Sun boxes, notL VMS boxes; the compute farms are Linux boxes - but VMS systems still run theJ big linac, and we're heavily invested in VMS in the synchrotron radiation L laboratory, both running beamlines and running our dedicated injector.  SSRLL (a division of SLAC) uses VMS for webserver system, proposal administration, database backend, etc.   -- Alanl   ------------------------------  % Date: Fri, 18 Feb 2005 04:59:44 +0800  From: prep@prep.synonet.comVY Subject: Re: [OT] Speed of light as speed limit (was Re: DECW$CLOCK design flaw   flaw   ,- Message-ID: <87vf8qc37j.fsf@prep.synonet.com>   ) "Main, Kerry" <kerry.main@hp.com> writes:t   >> -----Original Message-----g7 >> From: Ken Fairfield [mailto:my.full.name@intel.com]  " >> Sent: February 16, 2005 8:08 PM >> To: Info-VAX@Mvb.Saic.Com< >> Subject: Re: [OT] Speed of light as speed limit (was Re: # >> DECW$CLOCK design flaw flaw flawn  " > [snip lots of physics stuff ...]  9 >> I don't speak for Intel, Intel doesn't speak for me...I  n >> Ken Fairfield$ >> D1C Automation VMS System Support% >> who:   kenneth dot h dot fairfieldi >> where: intel dot como  F > Wow - it's amazing what backgrounds some folks have lurking in their" > resumes besides techie IT stuff.  , Have you forgotten that Ken is an ex SLACer?  : I wonder how many VMS systems still remain in the HEP labs
 anymore :(   -- -< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.C@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------   End of INFO-VAX 2005.097 ************************