0 INFO-VAX	Fri, 18 Feb 2005	Volume 2005 : Issue 98      Contents: 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 P Re: Does anyone know of an object compatible (non static) way of setting timeout Re: How to get a free iPod?  Re: How to get a free iPod?  Re: How to get a free iPod? # 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: linux kernel has major security flaws ... - Re: linux kernel has major security flaws ... - Re: linux kernel has major security flaws ...  looking for a new job  Re: looking for a new job 1 Re: Looking for suggestions for bootcamp sessions 1 Re: Looking for suggestions for bootcamp sessions 9 Micro$oft warns of undetectable spyware security risk ... ! Re: Mounting disks during STARTUP ! Re: Mounting disks during STARTUP ! Re: Mounting disks during STARTUP ! Re: Mounting disks during STARTUP  RE: Need performance help ! Re: OpenVMS 8.2 docs and freeware ! Re: OpenVMS 8.2 docs and freeware ! Re: 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 ?" Re: OpenVMS Small Partner Strategy" Re: OpenVMS Small Partner Strategy" Re: OpenVMS Small Partner Strategy, Re: OT: Message to Peter "EPLAN" LANGSTOEGER& Re: Port Print facility Update for I64/ Re: read monitor (>>>) variables from OpenVMS ? / Re: read monitor (>>>) variables from OpenVMS ?  Shark Tank mentions VMS  RE: Shark Tank mentions VMS  RE: Shark Tank mentions VMS # Re: TCPIP automatic route additions  TCPIP name cache TCPIP name cache Re: TCPIP name cache Re: TCPIP name cache Terminal connection   Re: VMS 8.2 Itanium Distribution  Re: VMS 8.2 Itanium Distribution  F ----------------------------------------------------------------------  % Date: Fri, 18 Feb 2005 10:28:55 +0100 & From: Paul Sture <paul.sture@decus.ch>$ Subject: Re: 7.32 patching questions, Message-ID: <37lqqmF5dll75U1@individual.net>   norm.raphael@metso.com wrote:   3 >>So, you think this process would probably be OK?:  >> >>1.  apply PCSI-V0100 patch >  > 2 > Step 2 or step 3, although both wouldn't hurt ;) >  > % >>2.  SET COMMAND SYS$UPDATE:PCSI.CLD  >>3.  Log out/in >   C But don't do what I once did. I faithfully did either 2 or 3, then  = accidentally picked another DECterm session to do the update.    ------------------------------  + Date: Fri, 18 Feb 2005 12:18:53 +0000 (UTC) 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)$ Subject: Re: 7.32 patching questions0 Message-ID: <newscache$hvw3ci$wow$1@news.sil.at>  U In article <37lqqmF5dll75U1@individual.net>, Paul Sture <paul.sture@decus.ch> writes: D >But don't do what I once did. I faithfully did either 2 or 3, then > >accidentally picked another DECterm session to do the update.  H This (I mean, getting the most current DCLTABLES) is not the only reasonF why I strongly recommend doing installations via a SET HOST[/LAT]/LOG=F every time. And having some PCSI logicals defined helps a lot to get a  meaningful installation logfile.  4 (LNM$SYSTEM_TABLE)      [kernel]  [shareable,system]D                         [Protection=(RWC,RWC,R,R)]  [Owner=[SYSTEM]]  -   "AXPVMS$PCSI_EXECUTE_VERIFY" [exec] = "YES" )   "AXPVMS$PCSI_LOG_TRACE" [exec] = "BOTH" +   "PCSI$$SAVE_RECOVERY_DATA" [exec] = "YES"    "PCSI$LOG" [exec] = "TRUE"7   "PCSI$SOURCE" [exec] = "SYS$SYSDEVICE:[INSTALL_KITS]"    "PCSI$TRACE" [exec] = "TRUE"    J If you consider installing new layered products (DCPS V2.4, DFG V2.9, ...)E as well, and you want to eventually back out ECOs (PRODUCT UNDO) then D install all the LPs before all ECOs (or at least before all the ECOsB you eventually want to UNDO). Every full product install/deinstallH deletes all ECO recovery data and then you can no longer UNDO any patch.    A And finally let me list my current recommendation for V7.3-2 ECOs    VMS732_PCSI		V1.0  VMS732_UPDATE 		V3.0 VMS732_TRACE		V2.0 VMS732_SYS		V6.0 VMS732_FIBRE_SCSI	V4.0 VMS732_PTHREAD		V2.0 VMS732_RMS		V2.0 VMS732_CPU270F		V1.0 VMS732_BACKUP		V3.0  VMS732_MQ		V1.0  VMS732_SYSINI		V1.0  VMS732_DRIVER		V1.0    DNVOSIECO01		V7.3-2  TCPIP_ECO		V5.4-154   M which means all of the current ECOs. YMMV of course (no MARVEL/MQ/APACHE/...) M NOTE: So far, I don't know the VMS732_VMSUPD V1.0 that this thread mentioned.    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 18 Feb 2005 05:06:53 -0800 From: tadamsmar@yahoo.com $ Subject: Re: 7.32 patching questionsC Message-ID: <1108732013.450021.325440@g14g2000cwa.googlegroups.com>    norm.raphael@metso.com wrote:  > see below  > 6 > tadamsmar@yahoo.com wrote on 02/17/2005 04:15:58 PM: >  > > ! > > norm.raphael@metso.com wrote: : > > > tadamsmar@yahoo.com wrote on 02/17/2005 02:44:48 PM: > > >  > > > > Looking at:  > > > > : > > > > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2 > > > > 4 > > > > 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 ofF > > > > the same name. The text seems to describe VMS732_UPDATE-V0300. > > > > ? > > > > Anyway I just loaded 7.32 from the Oct 03 distribution.  > > > > 1 > > > > To patch it, I think that I should apply:  > > > >  > > > > 1. VMS732_PCSI-V0100 > > > > 2. VMS732_UPDATE-V0300F > > > > 3. VMS732_VMSUPD-V0100 (from the mandatory update CD that cameG > > > >    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. > > > > G > > > > Is this a good way to proceed?  I am assuming that UPDATE-V0300 ; > > > > rolls up all the important patches that preceed it.  > > > > - > > > > Could they make this more confusing??  > > > > > > > > That's about correct.  the master list is documentation: > > > B > > > CURRENT UPDATE KIT                              RELEASE DATEB > > > ------------------                              ------------B > > > VMS732_UPDATE-V0300                              28-OCT-2004 > > >  > > > " > > > KITS INCLUDED IN UPDATE KIT:! > > > ===========================  > > > A > > > KIT NAME                          RELEASE DATE   SUPERSEDED A > > > -----------------------------     ------------   ---------- 3 > > > VMS732_AUDSRV-V0100               31-AUG-2004 ; > > > VMS732_BACKUP-V0200                4-OCT-2004     Yes 3 > > > VMS732_DCL-V0200                   4-FEB-2004 3 > > > VMS732_F11X-V0300                 18-OCT-2004 ; > > > VMS732_FIBRE_SCSI-V0300            4-MAY-2004     Yes 3 > > > VMS732_GRAPHICS-V0200             26-JAN-2004 3 > > > VMS732_HBMM-V0200                 23-SEP-2004 3 > > > VMS732_IPC-V0100                   7-SEP-2004 3 > > > VMS732_LAN-V0200                  13-APR-2004 3 > > > VMS732_LIBRTL-V0100               15-JUL-2004 3 > > > VMS732_LMF-V0100                  24-MAY-2004 3 > > > VMS732_MANAGE-V0200               10-MAR-2004 3 > > > VMS732_MOUNT96-V0100              11-AUG-2004 : > > > VMS732_PTHREAD-V0100              18-JUL-2004    Yes: > > > VMS732_RMS-V0100                  11-AUG-2004    Yes3 > > > VMS732_RPC-V0300                  20-FEB-2004 3 > > > VMS732_SHADOWING-V0200            15-OCT-2004 : > > > VMS732_SYS-V0500                  24-AUG-2004    Yes3 > > > VMS732_SYSLOA-V0200               21-JUL-2004 3 > > > VMS732_TDF-V0200                   1-JUN-2004 3 > > > VMS732_UPDATE-V0200                1-MAR-2003 3 > > > VMS732_XFC-V0100                  22-JUL-2004  > > >  > > > B > > > ECO KITS NOT INCLUDED IN UPDATE KIT:   RELEASE DATE COMMENTS9 > > > ------------------------------------   ------------  > > --------------------8 > > > VMS732_SYSINI-V0100                    25-JAN-20058 > > > VMS732_MQ-V0100                        12-JAN-20058 > > > VMS732_BACKUP-V0300                     6-JAN-20058 > > > VMS732_CPU270F-V0100                    4-JAN-20058 > > > VMS732_RMS-V0200                        4-JAN-20058 > > > VMS732_PTHREAD-V0200                    7-DEC-2004G > > > VMS732_FIBRE_SCSI-V0400                 6-DEC-2004  Documentation  > > Modified8 > > > VMS732_SYS-V0600                        6-DEC-20048 > > > VMS732_TRACE-V0200                      1-NOV-20048 > > > VMS732_PCSI-V0100                       3-MAR-2004 > > >  > > > = > > > One patch has been published that is not on here due to  > > > download issues  > > > 8 > > > VMS732_DRIVER-V0100                    15-FEB-2005 > > > A > > > You'll have to check for INSTALL_level and prerequisites to + > > > see if you need all of the last ones.  > > >  > > > 0 > > > The PCSI patch has to go in first and then > > > 2 > > >      7.3  Special Installation Instructions: > > >  > > > E > > >       o  No reboot is necessary after installation of this kit. E > > >          However, after installation of the kit users will need  to > > take > E > > >          one of the following steps to ensure that the new PCSI  files  > ! > Note:  one of the following....  >  > > >          are used: > > > F > > >           -  Execute the command SET COMMAND SYS$UPDATE:PCSI.CLD > > > + > > >           -  Log out and log back in.  > >  > > 5 > > So, you think this process would probably be OK?:  > >  > > 1.  apply PCSI-V0100 patch > 2 > 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 B > > 5.  apply mandatory security patch from the CD that came w/8.25 > > 6.  review all the patches since UPDATE-V0300 and 2 > >     apply any patches that are recommended for+ > >     my configuration of software usage.  > >  > That will "probably be OK."   = I phrased it that way because I'm not planning to sue you :).   = And, I have 3 stages of backups since I had to do pre-upgrade ; and post-upgrade patches, and you never know when a corrupt > patch/upgrade file will tell you to go back to your backup and8 start over!  If you stage it, you avoid some repetition.  @ After I have proven all my patch/upgrade files work, I will just4 do one stage of backup tapes for the other machines.   Thanks for your help!    ------------------------------    Date: 18 Feb 2005 05:20:26 -0800 From: tadamsmar@yahoo.com $ Subject: Re: 7.32 patching questionsC Message-ID: <1108732826.693604.296180@z14g2000cwz.googlegroups.com>     Peter 'EPLAN' LANGSTOEGER wrote:9 > In article <37lqqmF5dll75U1@individual.net>, Paul Sture  <paul.sture@decus.ch> writes: E > >But don't do what I once did. I faithfully did either 2 or 3, then @ > >accidentally picked another DECterm session to do the update. > C > This (I mean, getting the most current DCLTABLES) is not the only  reason8 > why I strongly recommend doing installations via a SET HOST[/LAT]/LOG= F > every time. And having some PCSI logicals defined helps a lot to get a " > meaningful installation logfile. > 6 > (LNM$SYSTEM_TABLE)      [kernel]  [shareable,system]F >                         [Protection=(RWC,RWC,R,R)]  [Owner=[SYSTEM]] > / >   "AXPVMS$PCSI_EXECUTE_VERIFY" [exec] = "YES" + >   "AXPVMS$PCSI_LOG_TRACE" [exec] = "BOTH" - >   "PCSI$$SAVE_RECOVERY_DATA" [exec] = "YES"  >   "PCSI$LOG" [exec] = "TRUE"9 >   "PCSI$SOURCE" [exec] = "SYS$SYSDEVICE:[INSTALL_KITS]"   >   "PCSI$TRACE" [exec] = "TRUE" >  > G > If you consider installing new layered products (DCPS V2.4, DFG V2.9,  ...)G > as well, and you want to eventually back out ECOs (PRODUCT UNDO) then F > install all the LPs before all ECOs (or at least before all the ECOsD > you eventually want to UNDO). Every full product install/deinstallC > deletes all ECO recovery data and then you can no longer UNDO any  patch. >  > C > And finally let me list my current recommendation for V7.3-2 ECOs  >  > VMS732_PCSI		V1.0  > VMS732_UPDATE 		V3.0 > VMS732_TRACE		V2.0 > VMS732_SYS		V6.0 > VMS732_FIBRE_SCSI	V4.0 > VMS732_PTHREAD		V2.0 > VMS732_RMS		V2.0 > VMS732_CPU270F		V1.0 > VMS732_BACKUP		V3.0  > VMS732_MQ		V1.0  > VMS732_SYSINI		V1.0  > VMS732_DRIVER		V1.0  >  > DNVOSIECO01		V7.3-2  > TCPIP_ECO		V5.4-154  > 9 > which means all of the current ECOs. YMMV of course (no  MARVEL/MQ/APACHE/...) D > NOTE: So far, I don't know the VMS732_VMSUPD V1.0 that this thread
 mentioned.  F VMSUPD 1 is part of the VMS 8.2 media distribution. Its on a mandatory security patch@ CD for earlier versions of VMS that comes with the distribution.  C I know some of those patches (BACKUP 3, for instance) are marked as 1 "upgrade if you are having problems" (INSTALL_3).      >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.at@ > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist    ------------------------------    Date: 18 Feb 2005 05:50:11 -0800 From: tadamsmar@yahoo.com $ Subject: Re: 7.32 patching questionsC Message-ID: <1108734611.310614.132050@l41g2000cwc.googlegroups.com>     Peter 'EPLAN' LANGSTOEGER wrote:9 > In article <37lqqmF5dll75U1@individual.net>, Paul Sture  <paul.sture@decus.ch> writes: E > >But don't do what I once did. I faithfully did either 2 or 3, then @ > >accidentally picked another DECterm session to do the update. > C > This (I mean, getting the most current DCLTABLES) is not the only  reason8 > why I strongly recommend doing installations via a SET HOST[/LAT]/LOG= F > every time. And having some PCSI logicals defined helps a lot to get a " > meaningful installation logfile. > 6 > (LNM$SYSTEM_TABLE)      [kernel]  [shareable,system]F >                         [Protection=(RWC,RWC,R,R)]  [Owner=[SYSTEM]] > / >   "AXPVMS$PCSI_EXECUTE_VERIFY" [exec] = "YES" + >   "AXPVMS$PCSI_LOG_TRACE" [exec] = "BOTH" - >   "PCSI$$SAVE_RECOVERY_DATA" [exec] = "YES"  >   "PCSI$LOG" [exec] = "TRUE"9 >   "PCSI$SOURCE" [exec] = "SYS$SYSDEVICE:[INSTALL_KITS]"   >   "PCSI$TRACE" [exec] = "TRUE" >  > G > If you consider installing new layered products (DCPS V2.4, DFG V2.9,  ...)G > as well, and you want to eventually back out ECOs (PRODUCT UNDO) then F > install all the LPs before all ECOs (or at least before all the ECOsD > you eventually want to UNDO). Every full product install/deinstallC > deletes all ECO recovery data and then you can no longer UNDO any  patch. >  > C > And finally let me list my current recommendation for V7.3-2 ECOs  >  > VMS732_PCSI		V1.0  > VMS732_UPDATE 		V3.0 > VMS732_TRACE		V2.0 > VMS732_SYS		V6.0 > VMS732_FIBRE_SCSI	V4.0 > VMS732_PTHREAD		V2.0 > VMS732_RMS		V2.0 > VMS732_CPU270F		V1.0 > VMS732_BACKUP		V3.0  > VMS732_MQ		V1.0  > VMS732_SYSINI		V1.0  > VMS732_DRIVER		V1.0  >  > DNVOSIECO01		V7.3-2   B DNVOSIECO01 is for DECNET-PLUS users only.  I am running phase IV.   > TCPIP_ECO		V5.4-154  > 9 > which means all of the current ECOs. YMMV of course (no  MARVEL/MQ/APACHE/...) D > NOTE: So far, I don't know the VMS732_VMSUPD V1.0 that this thread
 mentioned. >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.at@ > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist    ------------------------------    Date: 18 Feb 2005 05:59:45 -0800 From: tadamsmar@yahoo.com $ Subject: Re: 7.32 patching questionsC Message-ID: <1108735185.289975.233640@o13g2000cwo.googlegroups.com>     Peter 'EPLAN' LANGSTOEGER wrote: > TCPIP_ECO		V5.4-154   # First, I don't see that patch here:   = ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/   9 Second, I am running TCPIP V5.0-10 fresh off the VMS 7.32 
 distribution.   8 So, I guess I would need to upgrade from the quarterlies  to get to that version of TCPIP.   ------------------------------    Date: 18 Feb 2005 06:06:33 -0800 From: tadamsmar@yahoo.com $ Subject: Re: 7.32 patching questionsB Message-ID: <1108735593.268598.45490@z14g2000cwz.googlegroups.com>   tadams...@yahoo.com wrote:" > Peter 'EPLAN' LANGSTOEGER wrote: > > TCPIP_ECO		V5.4-154  > % > First, I don't see that patch here:  > ? > ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/  > ; > Second, I am running TCPIP V5.0-10 fresh off the VMS 7.32  > distribution.  > : > So, I guess I would need to upgrade from the quarterlies" > to get to that version of TCPIP.  4 Opps! I was running PROD SHOW PROD on the wrong box!   I'm at TCPIP V5.4-15  5 but the ECO is still not on the ftp site, so where do 
 I find it?   ------------------------------  + Date: Fri, 18 Feb 2005 08:56:10 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)$ Subject: Re: 7.32 patching questions2 Message-ID: <05021808561037_27800279@antinode.org>   From: tadamsmar@yahoo.com   $ > > Peter 'EPLAN' LANGSTOEGER wrote: > > > TCPIP_ECO		V5.4-154  > > ' > > First, I don't see that patch here:  > > A > > ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/  > [...] 6 > Opps! I was running PROD SHOW PROD on the wrong box! >  > I'm at TCPIP V5.4-15      That makes more sense.   7 > but the ECO is still not on the ftp site, so where do  > I find it?  E    I had the same problem.  The key is not to be distracted by these:   -       ALP_TCPIP_ECO-V0501-155.PCSI-DCX_AXPEXE !       ALP_TCPIP_ECO-V0501-155.txt .       ALP_TCPIP_ECO-V0503-182.PCSI-DCX_AXPEXE !       ALP_TCPIP_ECO-V0503-182.txt    but to continue down to these:  7       DEC-AXPVMS-TCPIP_ECO-V0504-151-4.PCSI-DCX_AXPEXE  *       DEC-AXPVMS-TCPIP_ECO-V0504-151-4.txt6       DEC-AXPVMS-TCPIP_ECO-V0504-152-4.PCSI-DCX_AXPEXE*       DEC-AXPVMS-TCPIP_ECO-V0504-152-4.txt=       DEC-AXPVMS-TCPIP_ECO-V0504-154-4.PCSI-DCX_AXPEXE   <--- =       DEC-AXPVMS-TCPIP_ECO-V0504-154-4.txt               <---   #    It's a clever naming convention.   H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------  % Date: Fri, 18 Feb 2005 08:53:09 -0000 # From: "Robin" <robin@yeahright.com> Y Subject: Re: Does anyone know of an object compatible (non static) way of setting timeout % Message-ID: <cv4ao4$kr8$1@rdel.co.uk>   H "Bob Koehler" <koehler@eisner.nospam.encompasserve.org> wrote in message- news:9kg$pgK$caLa@eisner.encompasserve.org... L > In article <cuv4vb$fn$1@rdel.co.uk>, "Robin" <robin@yeahright.com> writes: > > Hi all,  > > J > >     I hope someone can help. I need a way of setting object compatibleI > > timeouts within VMS. Both the system command 'sys$setimr()' and the X K > > toolkit command 'XtAppAddTimeOut()' call static functions on completion J > > rendering my object code useless. (There will be multiple instances of the 0 > > object but only one of the timeout routine!) > > H > > If anyone knows any other way of achieving this I would be grateful. > I >    The general way of telling things apart in the AST called by $SETIMR G >    is by the request id, which is basically an argument passed to the F >    AST that you can use as you wish.  You need to map the request idI >    to the specific object instance.  For example, in Java you could use F >    Object.hash() (inheritted by all objects) as a unique request id.F >    There should be something similar in C++, perhaps &object.  ThereH >    should then be a hook to allow your static routine to access objectH >    instance specific data and functions, but you may have to make sure/ >    you write them in an AST reentrant manner.  >   F Within C++ you supply the 'this' pointer from which you can access any members of the object.   Ta   Robin    ------------------------------    Date: 18 Feb 2005 06:59:11 -0800 From: DeathbySuicide@gmail.com$ Subject: Re: How to get a free iPod?B Message-ID: <1108738751.155524.53630@f14g2000cwb.googlegroups.com>  3 here is a link, just in case that person got theres # http://www.freeiPods.com/?r=8123756    ------------------------------    Date: 18 Feb 2005 06:59:08 -0800 From: DeathbySuicide@gmail.com$ Subject: Re: How to get a free iPod?B Message-ID: <1108738748.413214.62670@z14g2000cwz.googlegroups.com>  3 here is a link, just in case that person got theres # http://www.freeiPods.com/?r=8123756    ------------------------------  + Date: Fri, 18 Feb 2005 18:21:01 +0000 (UTC)  From: DeathbySuicide@gmail.com$ Subject: Re: How to get a free iPod?$ Message-ID: <cv5bmd$vcs$1@online.de>   illegal message cancelled    ------------------------------  % Date: Fri, 18 Feb 2005 05:03:00 -0800 # From: "Tom Linden" <tom@kednos.com> , Subject: Re: HP financials: Alpha sales down( Message-ID: <opsmd87aa5zgicya@hyrrokkin>  G On Thu, 17 Feb 2005 22:33:35 -0500, Neil Rieck <n.rieck@sympatico.ca>    wrote:  J > In December-2004 my employer purchased two used AS-DS20e machines from aJ > used equipment vendor and we quickly realized we were in the middle of aF > bidding war. The vendor told us that used Alpha sales were up 150%   > (whatever F > that means) since September 2004 with no end in sight coming. This  	 > started C > us to speculate: "Did this have anything to do with the announced J > End-of-Life of Alpha?". Were others thinking things like "Gee, Itanium   > boxes J > are coming out now but I'd like to wait for the technology to mature a   > bit I > so I'll by myself some time by purchasing used Alphas?" If any of these H > speculations are even partly true, it makes you wonder why Compaq/HP   > didn'tF > do the IBM thing and be a little more secretive when it comes to EOL > statements etc.   # Which computer systems did IBM EOL?    --  C Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------  % Date: Fri, 18 Feb 2005 08:33:55 -0500 # From: "John Smith" <a@nonymous.com> , Subject: Re: HP financials: Alpha sales down, Message-ID: <oNudnVGYye9Yc4jfRVn-rw@igs.net>   Tom Linden wrote: G > On Thu, 17 Feb 2005 22:33:35 -0500, Neil Rieck <n.rieck@sympatico.ca>  > wrote: > D >> In December-2004 my employer purchased two used AS-DS20e machinesF >> from a used equipment vendor and we quickly realized we were in theD >> middle of a bidding war. The vendor told us that used Alpha sales >> were up 150% (whatever E >> that means) since September 2004 with no end in sight coming. This 
 >> startedD >> us to speculate: "Did this have anything to do with the announcedA >> End-of-Life of Alpha?". Were others thinking things like "Gee,  >> Itanium boxesG >> are coming out now but I'd like to wait for the technology to mature  >> a bitD >> so I'll by myself some time by purchasing used Alphas?" If any ofC >> these speculations are even partly true, it makes you wonder why  >> Compaq/HP didn't G >> do the IBM thing and be a little more secretive when it comes to EOL  >> statements etc. > % > Which computer systems did IBM EOL?     H 709 -  sometime long ago, but I bet if you called and asked IBM for helpA with one you still had around, they'd find a way to help you out.    --- OpenVMS - The classics never go out of style.    ------------------------------  % Date: Fri, 18 Feb 2005 08:55:48 -0500 ' From: "Main, Kerry" <kerry.main@hp.com> , Subject: RE: HP financials: Alpha sales downR Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB53F592@tayexc19.americas.cpqcorp.net>   > -----Original Message-----4 > From: Bill Todd [mailto:billtodd@metrocast.net]=20! > Sent: February 17, 2005 8:41 PM  > To: Info-VAX@Mvb.Saic.Com . > Subject: Re: HP financials: Alpha sales down >=20 > Keith Parris wrote:  >=20 > ...  >=20@ > > Also, the majority of VMS' sizeable contributions to HP's=20 > revenues and=20 3 > > profits are found not in BCS, but in this area:  >=20; > Indeed.  And given that VMS sales aren't even close to=20  > holding up their=20 ? > end, the service revenues will inevitably follow them down=20  > hill - just=20J > with an obvious time-lag comparable to the installed lifetimes of the=20 > system involved. >=20 >   "HP Services (HPS)E > > revenue grew 20% year-over-year to a record $3.8 billion. On a=20 ? > > year-over-year basis, Managed Services revenue grew 44%,=20  > Consulting and=20 = > > Integration grew 20% and Technology Services grew 14%.=20  > Operating profit=20 ? > > was $281 million, or 7.4% of revenue, compared with $261=20  > million in the=20 > > > prior-year period." Based on past experience, one could=20 > estimate that=20> > > roughly 15% of the revenues and 25% of the profits here=20 > were from VMS. >=20D > The 'past experience' you are basing this on would appear to be=20: > pre-Alphacide experience (very much as that perpetual=20 > '411,000 installed=20 J > systems' seems to be), unless you're asserting that the Alphacide had=20G > very little effect in this area:  I could have believed that a few=20 > > months or even a year or more after the event (due to the=20 > time-lag noted=20 H > above), but it seems rather less believable coming up on its fourth=20 > anniversary. >=20 > - bill >=20   Bill,   @ The services revenue is very significant and if you believe some= analysts, is where the future is wrt to solutions selling.=20   C As an example, pointer to OpenVMS USD $750M services win last year: 9 http://www.hp.com/hpinfo/newsroom/press/2004/040324a.html C "HP awarded $784 Million Services Contract by Department of Veteran  Affairs"  F "...HP has been an infrastructure, consulting and services provider to@ the VA since 1983 through its work on the Decentralized HospitalD Computer Program (DHCP) and Enhanced Decentralized Hospital ComputerE Program (EDHCP) contracts. Over time, HP and the VA have collaborated > closely to continually evolve the VA's IT environment and haveE successfully deployed HP's OpenVMS clusters on AlphaServer systems to F build an adaptive environment that has increased performance, utilizesH 64-bit architecture and has enhanced reliability and up-time. As part ofB this latest agreement, HP takes responsibility for maintenance andF support for all hardware and software products that comprise the VistA
 solution."  B Hey - that's what Linux is all about right? Sell cheap and get the service contract.    :-)    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  $ "OpenVMS has always had integrity .. Now, Integrity has OpenVMS .."   ------------------------------  % Date: Fri, 18 Feb 2005 09:23:21 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> , Subject: Re: HP financials: Alpha sales downB Message-ID: <1108735844.85b4ffa0222c77cf4d82e22a759c8f8a@teranews>   Tom Linden wrote:    % > Which computer systems did IBM EOL?   G System 34, System 36, System 38. (replaced by the AS400). The old AS400 H was then ported to Power based systems. IBM redid all the OS names and I lost track.   C The lack of upgradibilkity from the incompatible 34, 36, 38 and MVS F systems was one of the big reasons that VMS took off since it was ableH to offer from desktop to data centre on the same OS and in that time, on the same hardware architecture.   H The 34/36/28/MVS mess was purposefully done so that should IBM have beenD forced to divest, the companies buying the smaller systems would notG inherit any of the valuable MVS and 370 architecture stuff. This is one 5 of the big reasons VMS got such a boost in the 1980s.   E When IBM combined the midrange systems into the AS400, the AS400 then F became the "VAX Killer". It was still different from MVS machines, butB it greatly reduced the disparity and incompatibility within IBM byJ simplifying the product offering between the PC, AS400 and MVS mainframes.   ------------------------------  % Date: Fri, 18 Feb 2005 09:48:28 -0500 # From: "John Smith" <a@nonymous.com> , Subject: Re: HP financials: Alpha sales down, Message-ID: <0ZWdneJAmrKinYvfRVn-uQ@igs.net>   Main, Kerry wrote: >> -----Original Message----- 2 >> From: Bill Todd [mailto:billtodd@metrocast.net]" >> Sent: February 17, 2005 8:41 PM >> To: Info-VAX@Mvb.Saic.Com/ >> Subject: Re: HP financials: Alpha sales down  >> >> Keith Parris wrote: >> >> ... >>= >>> Also, the majority of VMS' sizeable contributions to HP's  >> revenues and 3 >>> profits are found not in BCS, but in this area:  >>9 >> Indeed.  And given that VMS sales aren't even close to  >> holding up their = >> end, the service revenues will inevitably follow them down  >> hill - justH >> with an obvious time-lag comparable to the installed lifetimes of the >> system involved.  >> >>   "HP Services (HPS) B >>> revenue grew 20% year-over-year to a record $3.8 billion. On a< >>> year-over-year basis, Managed Services revenue grew 44%, >> Consulting and : >>> Integration grew 20% and Technology Services grew 14%. >> Operating profit < >>> was $281 million, or 7.4% of revenue, compared with $261 >> million in the ; >>> prior-year period." Based on past experience, one could  >> estimate that; >>> roughly 15% of the revenues and 25% of the profits here  >> were from VMS.  >>B >> The 'past experience' you are basing this on would appear to be8 >> pre-Alphacide experience (very much as that perpetual >> '411,000 installed H >> systems' seems to be), unless you're asserting that the Alphacide hadE >> very little effect in this area:  I could have believed that a few < >> months or even a year or more after the event (due to the >> time-lag noted F >> above), but it seems rather less believable coming up on its fourth >> anniversary.  >>	 >> - bill  >> >  > Bill,  > B > The services revenue is very significant and if you believe some< > analysts, is where the future is wrt to solutions selling. > E > As an example, pointer to OpenVMS USD $750M services win last year: ; > http://www.hp.com/hpinfo/newsroom/press/2004/040324a.html E > "HP awarded $784 Million Services Contract by Department of Veteran 
 > Affairs" > H > "...HP has been an infrastructure, consulting and services provider toB > the VA since 1983 through its work on the Decentralized HospitalF > Computer Program (DHCP) and Enhanced Decentralized Hospital ComputerG > Program (EDHCP) contracts. Over time, HP and the VA have collaborated @ > closely to continually evolve the VA's IT environment and haveG > successfully deployed HP's OpenVMS clusters on AlphaServer systems to H > build an adaptive environment that has increased performance, utilizesG > 64-bit architecture and has enhanced reliability and up-time. As part G > of this latest agreement, HP takes responsibility for maintenance and H > support for all hardware and software products that comprise the VistA > solution." > D > Hey - that's what Linux is all about right? Sell cheap and get the > service contract.     B Spin, spin, spin.   VA was an *existing* VMS customer outsourcing.  L How many sales of VMS >$25 million (hardware / os / layered products) in oneK deal have there been in the time since the VA outsourcing deal? How many of A these sales were to *new* customers? How many of these included a A significant Services component?   My money says Zero, Zero, Zero.   I How many VMS services deals with exisiting VMS customers for VMS services / >$50 million have been done since that VA deal?      --- OpenVMS - The classics never go out of style.    ------------------------------  % Date: Fri, 18 Feb 2005 07:14:57 -0800 # From: "Tom Linden" <tom@kednos.com> , Subject: Re: HP financials: Alpha sales down( Message-ID: <opsmefa7fxzgicya@hyrrokkin>  . On Fri, 18 Feb 2005 09:23:21 -0500, JF Mezei  % <jfmezei.spamnot@teksavvy.com> wrote:    > Tom Linden wrote:  > & >> Which computer systems did IBM EOL? > I > System 34, System 36, System 38. (replaced by the AS400). The old AS400 J > was then ported to Power based systems. IBM redid all the OS names and I
 > lost track.   E You need to check your facts.  AS400, e.g. runs on a Power core using I emulation.  It is compatible.  The point I was trying to make is that IBM ? endeavoured to not endanger its installed base by introducing    non-compatibleI architecture.  You can run an object module compiled 30 years ago on z-ost contrast that with  
 VAX->AXP->IPF   < In fact, you could run the old System 3 code on the 34, etc. >tE > The lack of upgradibilkity from the incompatible 34, 36, 38 and MVSiH > systems was one of the big reasons that VMS took off since it was ableJ > to offer from desktop to data centre on the same OS and in that time, on! > the same hardware architecture.  >gJ > The 34/36/28/MVS mess was purposefully done so that should IBM have beenF > forced to divest, the companies buying the smaller systems would notI > inherit any of the valuable MVS and 370 architecture stuff. This is onea7 > of the big reasons VMS got such a boost in the 1980s.P >nG Pure speculation on your part.  I have never heard such a story before.f  G > When IBM combined the midrange systems into the AS400, the AS400 thenuH > became the "VAX Killer". It was still different from MVS machines, butD > it greatly reduced the disparity and incompatibility within IBM byB > simplifying the product offering between the PC, AS400 and MVS  
 > mainframes.pD Huh?  What are you talking about?  Those are different product linesA and there has never been any claim of compatibility amongst them.d     -- nC Using Opera's revolutionary e-mail client: http://www.opera.com/m2/r   ------------------------------  % Date: Fri, 18 Feb 2005 07:16:18 -0800 # From: "Tom Linden" <tom@kednos.com> , Subject: Re: HP financials: Alpha sales down( Message-ID: <opsmefdgbkzgicya@hyrrokkin>  F On Fri, 18 Feb 2005 08:33:55 -0500, John Smith <a@nonymous.com> wrote:   > Tom Linden wrote:RH >> On Thu, 17 Feb 2005 22:33:35 -0500, Neil Rieck <n.rieck@sympatico.ca>	 >> wrote:a >>E >>> In December-2004 my employer purchased two used AS-DS20e machinesrG >>> from a used equipment vendor and we quickly realized we were in thenE >>> middle of a bidding war. The vendor told us that used Alpha salesf >>> were up 150% (whateverF >>> that means) since September 2004 with no end in sight coming. This >>> starteduE >>> us to speculate: "Did this have anything to do with the announced B >>> End-of-Life of Alpha?". Were others thinking things like "Gee, >>> Itanium boxesnH >>> are coming out now but I'd like to wait for the technology to mature	 >>> a bit-E >>> so I'll by myself some time by purchasing used Alphas?" If any of D >>> these speculations are even partly true, it makes you wonder why >>> Compaq/HP didn'tH >>> do the IBM thing and be a little more secretive when it comes to EOL >>> statements etc.d >>& >> Which computer systems did IBM EOL? >pH Quite right, forgot about that one, maybe I should have said in the last 40 years:-)M > J > 709 -  sometime long ago, but I bet if you called and asked IBM for helpC > with one you still had around, they'd find a way to help you out.E >r > --/ > OpenVMS - The classics never go out of style.- >- >        -- ,C Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------   Date: 18 Feb 2005 15:28:35 GMT( From: bill@cs.uofs.edu (Bill Gunshannon), Subject: Re: HP financials: Alpha sales down, Message-ID: <37mft3F5f2qc1U1@individual.net>  ( In article <opsmefa7fxzgicya@hyrrokkin>,& 	"Tom Linden" <tom@kednos.com> writes:0 > On Fri, 18 Feb 2005 09:23:21 -0500, JF Mezei  ' > <jfmezei.spamnot@teksavvy.com> wrote:L > E >> it greatly reduced the disparity and incompatibility within IBM bysC >> simplifying the product offering between the PC, AS400 and MVS    >> mainframes.F > Huh?  What are you talking about?  Those are different product linesC > and there has never been any claim of compatibility amongst them.R  R& Well, there was that PC370 thing.  :-)   bill  E   -- "J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   n   ------------------------------  # Date: Fri, 18 Feb 2005 16:44:15 GMT,! From: Nigel Barker <nigel@hp.com>t, Subject: Re: HP financials: Alpha sales down8 Message-ID: <965c111jgou80bs67jk4tu3p7ja92o89n4@4ax.com>  K On Thu, 17 Feb 2005 20:49:33 -0500, JF Mezei <jfmezei.spamnot@teksavvy.com>e wrote:  3 >Since VMS runs only on a small subset of IA64 boxe   # I wouldn't call 50% a small subset.d   -- Nigel Barker Live from the sunny Cote d'AzurU   ------------------------------  % Date: Fri, 18 Feb 2005 13:44:59 -0500 ( From: Bill Todd <billtodd@metrocast.net>, Subject: Re: HP financials: Alpha sales down= Message-ID: <MLGdnRrLrJQwqovfRVn-ug@metrocastcablevision.com>O   Main, Kerry wrote: >>-----Original Message-----2 >>From: Bill Todd [mailto:billtodd@metrocast.net] ! >>Sent: February 17, 2005 8:41 PMo >>To: Info-VAX@Mvb.Saic.Com.. >>Subject: Re: HP financials: Alpha sales down >> >>Keith Parris wrote:    ...n   >>  "HP Services (HPS) >>B >>>revenue grew 20% year-over-year to a record $3.8 billion. On a < >>>year-over-year basis, Managed Services revenue grew 44%,  >> >>Consulting and 0 >>: >>>Integration grew 20% and Technology Services grew 14%.  >> >>Operating profit   >>< >>>was $281 million, or 7.4% of revenue, compared with $261  >> >>million in the   >>; >>>prior-year period." Based on past experience, one could 1 >> >>estimate that  >>; >>>roughly 15% of the revenues and 25% of the profits here   >> >>were from VMS. >>B >>The 'past experience' you are basing this on would appear to be 8 >>pre-Alphacide experience (very much as that perpetual  >>'411,000 installed MH >>systems' seems to be), unless you're asserting that the Alphacide had E >>very little effect in this area:  I could have believed that a few  < >>months or even a year or more after the event (due to the  >>time-lag noted  F >>above), but it seems rather less believable coming up on its fourth  >>anniversary. >> >>- bill >> >  >  > Bill,a > * > The services revenue is very significant  H You are, as usual, side-stepping the specific issue raised, Kerry.  VMS G services revenue could qualify as 'very significant' even if were only s 1/4 what it was 4 years ago.  G If you're not willing to go on record with actual numbers, you're just mC (again as usual) spewing spin.  By the way, the value of that $784 yG million service contract you cited was not only spread out over a full iH decade (i.e, less than $80 million annually) but, as John noted, merely I reflects the extension of *existing* VMS service revenue rather than new i	 business.t   - bill   ------------------------------  % Date: Fri, 18 Feb 2005 00:46:00 -0800  From: Z <Z@no.spam> 6 Subject: Re: linux kernel has major security flaws ...) Message-ID: <j1iRd.2456$h8.2101@fe07.lga>-   John Santos wrote:G > The 1st (of 4) security flaw described says you can access supposedly F > 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 a B > 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/or ? > physical access to the system violate security on any system?   F Yes, it does.  The only real and unfixed flaw in that list is #2, the 
 setsid() bug.    ------------------------------    Date: 18 Feb 2005 05:24:35 -0800 From: bob@instantwhip.comN6 Subject: Re: linux kernel has major security flaws ...C Message-ID: <1108733074.901509.270530@l41g2000cwc.googlegroups.com>   1 and how many more lists will there be after that?    ------------------------------   Date: 18 Feb 2005 13:51:38 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)6 Subject: Re: linux kernel has major security flaws ..., Message-ID: <37ma79F5c8371U1@individual.net>  ) In article <j1iRd.2456$h8.2101@fe07.lga>,7 	Z <Z@no.spam> writes: > John Santos wrote:H >> The 1st (of 4) security flaw described says you can access supposedlyG >> secure data if you (as an unprivileged user) have read access to the F >> swap area or physical access to the machine.  I've never heard of aC >> system that encrypts the swap area (maybe there are systems that G >> encrypt *everything* on the disk, and so encrypt the swap area), but F >> other than that, doesn't having read access to the swap area and/or@ >> physical access to the system violate security on any system? > H > Yes, it does.  The only real and unfixed flaw in that list is #2, the  > setsid() bug.   F I would also wonder if any of this applies to the SE version of RedHatF which has (finally) incorporated the work done by NSA into the kernel.   bill   -- 0J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  + Date: Fri, 18 Feb 2005 12:37:35 +0000 (UTC)c  From: Heinz <heinzmeyer@msn.com> Subject: looking for a new job< Message-ID: <Xns960157B43829Aheinzmeyermsncom@213.51.129.36>   Hi everybody  J After the company I use to work for closed the doors I was left without a  job.L At this time it is very hard to find a job as vax/vms system manager in the  netherlands.M so if there is somebody out there in the world who can use a vax/vms - NT -   C system manager please let me know and I be happy to send you my cv.k   Thankz.    ------------------------------    Date: 18 Feb 2005 10:07:23 -0800  From: "Barry" <dysert@gmail.com>" Subject: Re: looking for a new jobC Message-ID: <1108750043.820260.318020@o13g2000cwo.googlegroups.com>   C If you get yourself an account at decuserve.org, there's a DECNotesSD conference for employment.  It doesn't get a lot of activity, but at7 least it's another place to post your need.  Good luck.s   ------------------------------  # Date: Fri, 18 Feb 2005 11:05:47 GMTp! From: Nigel Barker <nigel@hp.com>t: Subject: Re: Looking for suggestions for bootcamp sessions8 Message-ID: <avfb119bmu4vl9pt0umdvc0ejub86ii8cj@4ax.com>  A On 16 Feb 2005 19:16:02 -0800, kenneth.randell@verizon.net wrote:w  G >On an Alpha, I simply type B DKA0 and I'm all set -- this is very easy E >for my users to remember.  My experience on Itanium is that the bootaG >information has some kind of disk-partition/other-magic-code stored in E >the NVRAM, so even if the disk is in the same slot and bootable, thekB >saved boot information is different so the system won't boot.  MyF >remote users are not the kind to use BCFG commands in order to changeF >things.  This part can likely be done via a script, but it seems more >hackerly to write a program.l  P It's true that boot will fail if you swap out one system disk for another set upL to autoboot from a disk with a particular Globally Unique Identifier (GUID).N However it is still possible to do the equivalent of >>> b dka0 it's just that. you have to type in a few more characters e.g.  # shell>  fs0:\efi\vms\vms_loader.efi   N Creating a new entry in the boot menu is just a question of selecting a couple of menu items.   -- Nigel Barker Live from the sunny Cote d'Azuro   ------------------------------  # Date: Fri, 18 Feb 2005 16:51:16 GMTo& From: John Reagan <john.reagan@hp.com>: Subject: Re: Looking for suggestions for bootcamp sessions/ Message-ID: <82pRd.303$ZA.292@news.cpqcorp.net>d   Nigel Barker wrote:aP > However it is still possible to do the equivalent of >>> b dka0 it's just that0 > you have to type in a few more characters e.g. > % > shell>  fs0:\efi\vms\vms_loader.efi  > P > Creating a new entry in the boot menu is just a question of selecting a couple > of menu items.  G The shell does invoke some ini/login file if present (I don't remember ]G the name right off hand).  You can put an alias in there for the above " command.     --   John ReaganE/ HP Pascal/{A|I}MACRO for OpenVMS Project LeaderP Hewlett-Packard Company"   ------------------------------    Date: 18 Feb 2005 05:28:30 -0800 From: bob@instantwhip.comlB Subject: Micro$oft warns of undetectable spyware security risk ...B Message-ID: <1108733310.343931.80970@g14g2000cwa.googlegroups.com>  : so you think everything can be patched in windoze land ...  ) http://www.theinquirer.net/?article=21326    ------------------------------    Date: 18 Feb 2005 00:10:26 -0800% From: Bart.Zorn@xs4all.nl (Bart Zorn)3* Subject: Re: Mounting disks during STARTUP= Message-ID: <a98cd882.0502180010.38ff0be4@posting.google.com>7  F There is one example which demonstrates that it works: when you have aF shadowed system disk with more than one member, the second (and third)> member get automatically added to the shadow set at boot time.  = But yes, I have seen it work and we use it here in a separateY4 MOUNT_DISKS.COM which is called frol SYLOGICALS.COM.  	 Bart Zorn   e David J Dachtera <djesys.nospam@comcast.net> wrote in message news:<4215470E.5182510E@comcast.net>...u > Bart Zorn wrote: > > J > > Not really. If you find a disk which appears to be a shadowset member,E > > you can mount it with the /INCLUDE qualifier and it will find itsd! > > fellow members automatically.o > % > Has anyone seen that actually work?  >  > -- G > David J Dachtera > dba DJE Systemss > 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/a > $ > Unofficial OpenVMS-IA32 Home Page:! > http://www.djesys.com/vms/ia32/4 >  > Coming soon:( > Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Fri, 18 Feb 2005 03:32:17 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>d* Subject: Re: Mounting disks during STARTUPB Message-ID: <1108714795.7463671c9faa315adbd1d78d697c6012@teranews>   Bart Zorn wrote: > H > There is one example which demonstrates that it works: when you have aH > shadowed system disk with more than one member, the second (and third)@ > member get automatically added to the shadow set at boot time.  B Yes because system disks are mounted REALLY early into the booting2 process, way before any of your DCL gets executed.  F But do data shadow sets now automount any members that were there whenB the shadow set was dismounted ? Or must one still do a /INCLUDE to0 specify which actual drives are to be included ?  F Back when I did this ( along time ago), I had code that waited up to aF few minutes for other disks in a shadow set to become available beforeH proceeding with the mount. If you mounted the shadow set alltogether andC it was properly dismounted before, the mount would be quick. If youT? added a member afterwards, then it could result in a copy/mergeb? operation. (I know that this has changed since I last used it).o  G Waiting a couple minutes during boot saved a lot of processing time. It G also gave VMS a much better opportunity at deciding which drive was thecG most current in case there was a difference in the set.  The problem is	< when not all nodes were being booted at the exact same time.   ------------------------------    Date: 18 Feb 2005 07:57:31 -0800% From: Bart.Zorn@xs4all.nl (Bart Zorn)7* Subject: Re: Mounting disks during STARTUP= Message-ID: <a98cd882.0502180757.6ab388e2@posting.google.com>f  w JF Mezei <jfmezei.spamnot@teksavvy.com> wrote in message news:<1108714795.7463671c9faa315adbd1d78d697c6012@teranews>...M > Bart Zorn wrote: > > J > > There is one example which demonstrates that it works: when you have aJ > > shadowed system disk with more than one member, the second (and third)B > > member get automatically added to the shadow set at boot time. > D > Yes because system disks are mounted REALLY early into the booting4 > process, way before any of your DCL gets executed. > H > But do data shadow sets now automount any members that were there whenD > the shadow set was dismounted ? Or must one still do a /INCLUDE to2 > specify which actual drives are to be included ? > H > Back when I did this ( along time ago), I had code that waited up to aH > few minutes for other disks in a shadow set to become available beforeJ > proceeding with the mount. If you mounted the shadow set alltogether andE > it was properly dismounted before, the mount would be quick. If you-A > added a member afterwards, then it could result in a copy/mergeaA > operation. (I know that this has changed since I last used it).0 > I > Waiting a couple minutes during boot saved a lot of processing time. It:I > also gave VMS a much better opportunity at deciding which drive was the,I > most current in case there was a difference in the set.  The problem is/> > when not all nodes were being booted at the exact same time.  F The fact that the boot process is able to find the original members ofB the shadowset indicates to me that the chance that MOUNT can do it& later on for other disks is very good.  E I started using /INCLUDE just because I found it in the documentation = and until now I have had no reason to distrust it. I call the-B MOUNT_DISKS.COM, which uses /INCLUDE, from SYLOGICALS.COM and that/ works OK! I do not use WAITs in MOUNT_DISKS.COM3   Regards,  	 Bart Zorns   ------------------------------  + Date: Fri, 18 Feb 2005 17:35:32 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)* Subject: Re: Mounting disks during STARTUP$ Message-ID: <cv5914$p98$1@online.de>  = In article <a98cd882.0502180757.6ab388e2@posting.google.com>,R( Bart.Zorn@xs4all.nl (Bart Zorn) writes:   G > I started using /INCLUDE just because I found it in the documentationt? > and until now I have had no reason to distrust it. I call the D > MOUNT_DISKS.COM, which uses /INCLUDE, from SYLOGICALS.COM and that1 > works OK! I do not use WAITs in MOUNT_DISKS.COM5  @ I haven't used it since I don't understand it.  :-)  What's the C advantage, apart from being able to specify only one member of the -C shadow set?  (Actually, for documentaton purposes, I would like to P specify all of them.)   H If all aren't available when using MOUNT/INCLUDE, will the mount fail?  5 If so, this MIGHT be what you want, but might not be.1   ------------------------------  % Date: Fri, 18 Feb 2005 09:18:43 -0500 ' From: "Main, Kerry" <kerry.main@hp.com>n" Subject: RE: Need performance helpR Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB53F598@tayexc19.americas.cpqcorp.net>   > -----Original Message-----> > From: David J Dachtera [mailto:djesys.nospam@comcast.net]=20! > Sent: February 17, 2005 8:48 PM- > To: Info-VAX@Mvb.Saic.Com1$ > Subject: Re: Need performance help >=20 > Kenneth Farmer wrote:j > >=20< > > Please email this guy directly if you're able to assist. > >=20$ > > Rajat.Gupta(at)gb.vodafone.co.uk > >=20: > > I've also posted in OpenVMS Tech forum on OpenVMS.org: > >=20B > > http://www.openvms.org/phorum/read.php?f=3D1&i=3D1533&t=3D1533 > >=20 > > Hello ,l > >=20A > > Thank you very much for the reponse. I want to know of any=20  > profiling tool- > > avalaible for openVMS like gprof on unix.e > >=20B > > Actually I have a process that gives a performance of 20000=20 > transactions perB > > sec on linux machine but gives only 3000 transactions on an=20 > OpenVMS platform> > > with maximum CPU utilization. I want to get hold of the=20 > limiting issues. >=20G > Look into using Extended File Cache, and make sure your disk units on ; > your storage arrays are set with writeback cache enabled.s >=20    / Also, have not used this myself, but check out:t0 http://h71000.www7.hp.com/openvms/products/dcpi/F "The HP Digital Continuous Profiling Infrastructure (HP DCPI) AdvancedG Development Kit for AlphaServer systems permits continuous low-overheadsA profiling of entire systems, including the kernel, user programs,eE drivers, and shared libraries. The system is efficient enough that it H can be left running all the time, allowing it to be used to drive online6 profile-based optimizations for production systems.=20  ; HP DCPI maintains a database of profile information that isnF incrementally updated for every executable image that runs. A suite ofB profile analysis tools analyzes the profile information at variousG levels. At one extreme, the tools show what fraction of CPU cycles wereSG spent executing the kernel and each user program. At the other extreme,7G the tools show how long a particular instruction stalls on average, fori& example, because of a D-cache miss.=20  E HP DCPI documentation contains an overview of DCPI for OpenVMS, along8/ with detailed descriptions of DCPI commands.=20a  F To download and install DCPI, you must first agree to the terms of theE license and register with HP. You will then receive an e-mail messaget) with the location of the download kit.=20s  F To be notified of new releases and other developments, sign up for ourG HP DCPI mailing list by sending us your full name, affiliation, mailingw' address, and preferred e-mail address."$     Regardsd   ------------------------------    Date: 18 Feb 2005 02:35:29 -0800/ From: "issinoho@gmail.com" <issinoho@gmail.com>m* Subject: Re: OpenVMS 8.2 docs and freewareB Message-ID: <1108722929.675096.60340@l41g2000cwc.googlegroups.com>  G Has the version of ImageMagick on here been tested and verified to work  with JPEG images?DD My initial attempt at building it didn't work - I'd be interested in/ hearing from anyone with more fruitful results.e   ------------------------------  % Date: Fri, 18 Feb 2005 12:05:14 -0500 , From: "warren sander" <warren.sander@hp.com>* Subject: Re: OpenVMS 8.2 docs and freeware, Message-ID: <42162094$1@usenet01.boi.hp.com>   fixedh: "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:uDyJyfLtgR3Z@eisner.encompasserve.org...,> > In article <42152be4$1@usenet01.boi.hp.com>, "warren sander" <warren.sander@hp.com> writes:2 > > The OpenVMS 8.2 docs are new up and available.! > > http://h71000.www7.hp.com/doc  >cG > From here in Massachusetts, the 8.2 link gets me a page that says 8.2nG > at the top but has only a column for 7.3-2.  The one manual I checkedL= > (Guide to System Security, of course) is the 7.3-2 version.    ------------------------------  % Date: Fri, 18 Feb 2005 12:05:59 -0500 , From: "warren sander" <warren.sander@hp.com>* Subject: Re: OpenVMS 8.2 docs and freeware* Message-ID: <421620c1@usenet01.boi.hp.com>  G some of the manuals haven't been updated or they hadn't created new 8.2o versions for me.  & send your emails to openvmsdocs@hp.com    : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:uDyJyfLtgR3Z@eisner.encompasserve.org...n> > In article <42152be4$1@usenet01.boi.hp.com>, "warren sander" <warren.sander@hp.com> writes:2 > > The OpenVMS 8.2 docs are new up and available.! > > http://h71000.www7.hp.com/doce >)G > From here in Massachusetts, the 8.2 link gets me a page that says 8.2uG > at the top but has only a column for 7.3-2.  The one manual I checkedo= > (Guide to System Security, of course) is the 7.3-2 version.I   ------------------------------  % Date: Fri, 18 Feb 2005 13:08:37 -0500 , From: "warren sander" <warren.sander@hp.com>* Subject: Re: OpenVMS 8.2 docs and freeware, Message-ID: <42162f6f$1@usenet01.boi.hp.com>  J the 7.3-2 version of the guide to security is the most recent copy. it was not updated for 8.2w  according to the doc group folks  : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:uDyJyfLtgR3Z@eisner.encompasserve.org... > > In article <42152be4$1@usenet01.boi.hp.com>, "warren sander" <warren.sander@hp.com> writes:2 > > The OpenVMS 8.2 docs are new up and available.! > > http://h71000.www7.hp.com/doc  >,G > From here in Massachusetts, the 8.2 link gets me a page that says 8.2uG > at the top but has only a column for 7.3-2.  The one manual I checked9= > (Guide to System Security, of course) is the 7.3-2 version.O   ------------------------------  % Date: Fri, 18 Feb 2005 09:41:14 +0100 & From: Paul Sture <paul.sture@decus.ch>= Subject: Re: OpenVMS Cluster to Replace News.Individual.NET ?a, Message-ID: <37lo19F5fb8j4U1@individual.net>   Bill Gunshannon wrote:  D > In article <1108624898.4b72846fc2fcfeae325e3f1dfb4fadf8@teranews>,2 > 	JF Mezei <jfmezei.spamnot@teksavvy.com> writes: >  >>leslie wrote:A >>G >>>One way to give OpenVMS some much-needed publicity would be to offernC >>>the internet a multi-site OpenVMS cluster as a free news server.- >>C >>Is there a NNTP server on VMS that supports user authentication ?s >>H >>Such a service would be a neat technology demonstration, especially ifH >>it were setup for free by hobbyists, a showcase of how simple it wouldH >>be compared to the complex and expensive distributed solution sused byL >>services such as akamai and the large commercial distributed news servers. >  > E > I can't imagine whatr solution they use but I ran a News Server foroC > a long time and it was one of the systems that required the leasto
 > of my time.a >   G I too ran a News Server on a SuSE system. and once set up, it just ran.e  F The documentation claimed it had been designed for reliability rather D than a high number of users, but it ran fine for me on a 300 MHz el 
 cheapo PC.    H On a bigger scale there were continual threats to scrap the News Server I at work a few years ago, simply because noone wanted it on their budget.  H The sum involved was peanuts in the grand scheme of things - about half E the budget for one person per year, so with maintenance, capital and l: floorspace costs probably didn't take much time to manage.   ------------------------------  % Date: Fri, 18 Feb 2005 09:12:54 -0800i' From: David Mathog <mathog@caltech.edu>s= Subject: Re: OpenVMS Cluster to Replace News.Individual.NET ?n+ Message-ID: <cv57mm$j4s$1@naig.caltech.edu>/   George Cook wrote:D  > I may be misunderstanding your data, but the greatest part of the6  > slowness appears related to file create/open/close?  ; In some cases that was true, but not for the examples given  in the benchmark.g  % I've occasionally seen Unix code that 6 opens a file for append, writes to it, then closes it,; then does it all over again.  This causes only a very minore; performance hit on Unix/linux (at least the ones I've used)s= but is horrifically slow on VMS.  You note that DNEWS is muchuA faster than ANUNEWS.  I'm not familiar with either one.  However,t4 since you state that the latter keeps each post in a2 separate file by definition it must be doing a lot; of open/close, and it's almost axiomatic from that point ont- that it must be very slow.  I'm also going tor= guess that it started as a port from some Unix program, wherewB all of those and opens and closes wouldn't have been as much of a > problem.  One can pretty much guess that DNEWS stores posts in> a more efficient manner, in some sort of container or database= file, so that it doesn't need to open/close zillions of filesa7 all the time. Perhaps it uses RMS indexed files, and if C not, reimplements something fairly similar at the disk block level.0  D Bypass RMS and then VMS can write data onto disk at a sustained rateH as fast as the hardware will go.  On the other hand, use RMS, especially8 through C, and typical smallish read/write programs are,6 or at least were, much slower on VMS than on identicalE hardware running linux.  This was a real problem for me since roughlyr, 100% of the software we use is written in C!   prep@prep.synonet.com wrote:+ > David Mathog <mathog@caltech.edu> writes:3 > G > David, if you take a broken IO design and do a brain-dead port of it, E > what do you expect... If you do it RIGHT, vms will pound unix IO toiI > pulp. That is why unix is now getting such new ideas as MMIO and Directs > IO. ;|  F Well, take a look at the benchmarks and tell me in which way they are C broken.  Most of them do nothing more than open an input file, openr? an output file (or files) and copy from one to the other.  They I represent a pretty typical IO load for the sorts of programs I encounter.0   > F > A News server is a notorious system killer. google for `i-node hack'E > for an intro. The normal news implementation uses a simplistic fileiD > design to store articles, and hammers file creation to a pulp. The  > 50 GB/day is also problematic. > B > There is already a reasonable News server for VMS, ANU News, andB > it has had several updates and overhauls by <some one who's nameA > I should be able to remember> in it's comercial supported form.:  6 George said that ANUNEWS "was a total I/O dog" whereas? DNEWS isn't.  You guys must be grabbing different parts of that>* elephant.  Is ANUNEWS an I/O dog or not???   Regards,   David Mathog mathog@caltech.edu   ------------------------------    Date: 18 Feb 2005 08:26:50 -0800 From: jordan@ccs4vms.com+ Subject: Re: OpenVMS Small Partner StrategyBB Message-ID: <1108744009.975338.57300@g14g2000cwa.googlegroups.com>  C Compaq added requirements for certification for a certain number ofwG employees; I got both the Alphaserver and VMS certifications, one other-= person got the VMS cert, and a third got just the AlphaserveroG certification.  That was sufficient, and we were set to renew that when / HP dropped its million dollar doggy bomb on us.r  F However, we used to be a direct VAR under Digital.  Under GQ Palmer we@ were relegated to 'tiered VAR' status, which meant we had to buyF through a distributor (in our case Wyle) at lower margins.  At the endF we were still purchasing through Wyle/Arrow, but as a result of the HP@ doggy bomb, we were informed that we were no longer qualified to> purchase enterprise equipment or software, even through a tier@ distributor.  That means the officially authorized new equipmentF distributors are prohibited by HP from selling equipment to folks like us for resale.  G We do still have the ability to 'resell' Alphas and OpenVMS, but now wetG have to do it through an end reseller (like we used to be); margins are > squeaky and order versatility is not what we used to have,  InD addition, credit for, paperwork for, and HP recognition for the saleA goes to the end reseller we 'facilitated' through, not to us.  HPn, support contracts have their name, not ours.  G So in a way we can do what you described now, though with major caveats F and very little margin (and considering you're competing against otherE end resellers who get a better deal than you on hardware and software4B cost, you can't count on winning many sales... at least on price).  F I don't see HP even bothering to pay attention to any such suggestion.B They are just flat NOT INTERESTED in selling VMS into small/mediumE business, and so have no interest in vendors that specialized in thatrF area.  Thats why we may well have sold our very last VMS system into aF site last year, the end of a ~30 year run that started with PDP-8s andF -11s and ended with Dells (because they are cheaper and better wintelsF and we get a better deal retail from them than we can get from HP as aF reseller of their wintel products, and Dell will sell _ANYTHING_ to us9 without imposing a million dollar minimum requirement...)    Rich   ------------------------------  % Date: Fri, 18 Feb 2005 12:15:07 -0500e# From: "John Smith" <a@nonymous.com>t+ Subject: Re: OpenVMS Small Partner Strategya, Message-ID: <_JGdnXIliNoAv4vfRVn-hg@igs.net>   jordan@ccs4vms.com wrote:nE > Compaq added requirements for certification for a certain number ofdC > employees; I got both the Alphaserver and VMS certifications, oneeE > other person got the VMS cert, and a third got just the Alphaserver D > certification.  That was sufficient, and we were set to renew that6 > when HP dropped its million dollar doggy bomb on us. >iH > However, we used to be a direct VAR under Digital.  Under GQ Palmer weB > were relegated to 'tiered VAR' status, which meant we had to buyH > through a distributor (in our case Wyle) at lower margins.  At the endH > we were still purchasing through Wyle/Arrow, but as a result of the HPB > doggy bomb, we were informed that we were no longer qualified to@ > purchase enterprise equipment or software, even through a tierB > distributor.  That means the officially authorized new equipmentH > distributors are prohibited by HP from selling equipment to folks like > us for resale. > F > We do still have the ability to 'resell' Alphas and OpenVMS, but now@ > we have to do it through an end reseller (like we used to be);B > margins are squeaky and order versatility is not what we used toG > have,  In addition, credit for, paperwork for, and HP recognition fordD > the sale goes to the end reseller we 'facilitated' through, not to6 > us.  HP support contracts have their name, not ours. >zA > So in a way we can do what you described now, though with majornB > caveats and very little margin (and considering you're competing? > against other end resellers who get a better deal than you on F > hardware and software cost, you can't count on winning many sales... > at least on price).o >hH > I don't see HP even bothering to pay attention to any such suggestion.D > They are just flat NOT INTERESTED in selling VMS into small/mediumG > business, and so have no interest in vendors that specialized in thattH > area.  Thats why we may well have sold our very last VMS system into aH > site last year, the end of a ~30 year run that started with PDP-8s andH > -11s and ended with Dells (because they are cheaper and better wintelsH > and we get a better deal retail from them than we can get from HP as aH > reseller of their wintel products, and Dell will sell _ANYTHING_ to us; > without imposing a million dollar minimum requirement...)y  H Not that you don't have better things to do with your time, but have you written to Ann Livermore?u   --- OpenVMS - The classics never go out of style.n   ------------------------------    Date: 18 Feb 2005 10:17:08 -0800 From: bob@instantwhip.comi+ Subject: Re: OpenVMS Small Partner StrategyrC Message-ID: <1108750628.738920.322920@g14g2000cwa.googlegroups.com>   E they are not cheaper ... there is the big lie ... total tco is higher # with any other non vms solution ...d   ------------------------------  + Date: Fri, 18 Feb 2005 12:39:55 +0000 (UTC)s6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)5 Subject: Re: OT: Message to Peter "EPLAN" LANGSTOEGER 0 Message-ID: <newscache$iux3ci$nqw$1@news.sil.at>   In article <1108702038.711081.70250@z14g2000cwz.googlegroups.com>, "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> writes:H >I've tried to send this to you several times, however, I guess your ISPF >has my Yahoo mail address blocked.  At least that is what is seems to >be from the return message.  ? Sorry, no. I'm the ISP in this case. I forgot to whitelist you,n@ because I've blacklisted YAHOO (besides a bunch of others, too).  G >Sorry for posting here. I didn't know any other way of getting througho1 >and I didn't want you to think I was ungrateful.e  B A text-only message should always come through if it's not from anJ RBLed mailer or with an yahoo, msn, netscape and similar sender addresses.0 So your company mail address may have worked ;-)  N Normally, I check my OPERATOR.LOG for unwanted rejections, but I was/am ill...  $ You're whitelisted now and Good Luck   --   Peter "EPLAN" LANGSTOEGERt% Network and OpenVMS system specialisto E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  # Date: Fri, 18 Feb 2005 16:52:36 GMTf& From: John Reagan <john.reagan@hp.com>/ Subject: Re: Port Print facility Update for I64./ Message-ID: <o3pRd.304$ZA.146@news.cpqcorp.net>e   David J Dachtera wrote:   H > Thanx to the maintainers of the test-drive cluster site for the use of > the IA64 machine.D >   D Just curious...  How long did it take you to port?  Any interesting  problems you ran into?     -- > John Reagann/ HP Pascal/{A|I}MACRO for OpenVMS Project Leaderj Hewlett-Packard Companyo   ------------------------------  % Date: Fri, 18 Feb 2005 14:55:05 +0100h, From: "Ferry Bolhar" <bol@adv.magwien.gv.at>8 Subject: Re: read monitor (>>>) variables from OpenVMS ?5 Message-ID: <1108734909.382005@proxy.dienste.wien.at>u  0 <JimStrehlow@data911.com> schrieb im Newsbeitrag= news:1108571853.458156.104310@z14g2000cwz.googlegroups.com...g@ > What version of OpenVMS allows you to use a f$setenv function?9 > v7.3-1 returns an -IVFAM invalid lexical function name.   7 Perhaps you're on a VAX? F$GETENV exists on Alpha only.o   Greetings, Ferry --   Ing. Ferry Bolhar % Municipality of Vienna, Department 14  A-1010 Vienna / AUSTRIA- E-mail: bol@adv.magwien.gv.at1   ------------------------------    Date: 18 Feb 2005 12:08:31 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)g8 Subject: Re: read monitor (>>>) variables from OpenVMS ?3 Message-ID: <ra7GIW+HmA1F@eisner.encompasserve.org>m  d In article <1108734909.382005@proxy.dienste.wien.at>, "Ferry Bolhar" <bol@adv.magwien.gv.at> writes: > 2 > <JimStrehlow@data911.com> schrieb im Newsbeitrag? > news:1108571853.458156.104310@z14g2000cwz.googlegroups.com...4A >> What version of OpenVMS allows you to use a f$setenv function?H: >> v7.3-1 returns an -IVFAM invalid lexical function name. > 9 > Perhaps you're on a VAX? F$GETENV exists on Alpha only.-   The same is true of V7.3-1 :-)   ------------------------------  % Date: Fri, 18 Feb 2005 11:38:43 -0500o2 From: "Stanley F. Quayle" <squayle@insight.rr.com>  Subject: Shark Tank mentions VMS. Message-ID: <4215D3C3.27182.2FD3584@localhost>  F http://www.computerworld.com/departments/opinions/sharktank/0,4885,998" 78,00.html?source=NLT_SH&nid=99878   Beware abbreviations!4  
 --Stan Quaylel Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363r3 8572 North Spring Ct., Pickerington, OH  43147  USAe0 stan-at-stanq-dot-com       http://www.stanq.com   ------------------------------  % Date: Fri, 18 Feb 2005 12:07:18 -0500s' From: "Main, Kerry" <kerry.main@hp.com>e$ Subject: RE: Shark Tank mentions VMSR Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB53F5C9@tayexc19.americas.cpqcorp.net>   > -----Original Message-----< > From: Stanley F. Quayle [mailto:squayle@insight.rr.com]=20" > Sent: February 18, 2005 11:39 AM > To: Info-VAX@Mvb.Saic.Com " > Subject: Shark Tank mentions VMS >=20H > http://www.computerworld.com/departments/opinions/sharktank/0,4885,998( > 78,00.html?source=3DNLT_SH&nid=3D99878 >=20 > Beware abbreviations!  >=20 > --Stan Quayleu > Quayle Consulting Inc. >=20 > ----------/ > Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363e5 > 8572 North Spring Ct., Pickerington, OH  43147  USAg2 > stan-at-stanq-dot-com       http://www.stanq.com >=20 >=20   Stan,a  D Reminds me of some older VAX console commands that used to interpret& ">>>H" as short for "halt" the system.  C That is until a few incidents were reported whereby operaters wouldt@ enter ^P to get to the console and then type "H" for "help" ....   :-)n  H As I recall, subsequent versions required one to enter at least HA or HE to be recognized.e   Regards   
 Kerry Main Senior Consultantn HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477l kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  $ "OpenVMS has always had integrity .. Now, Integrity has OpenVMS .."   ------------------------------  % Date: Fri, 18 Feb 2005 13:33:41 -0500 5 From: "Bochnik, William J" <William_Bochnik@acml.com>r$ Subject: RE: Shark Tank mentions VMSQ Message-ID: <2D75787AAF09C64481BDFD89113BE6D507CBCCB3@ac2kama0102.ac.lp.acml.com>   F Had a similar incident at my old job.  The "esc" key on the Microvax 2H would take you to the >>> prompt.  We used terminal servers there, whereH hitting the esc key would allow you to switch sessions.  Well, one day aE programmer was in the datacenter and walked over to the MII.  He seestG that someone's logged in, so hits the esc key, and gets the >>> prompt.lF Needless to say 30 seconds later we had a cluster state transition....   -----Original Message-----/ From: Main, Kerry [mailto:kerry.main@hp.com]=20.( Sent: Friday, February 18, 2005 12:07 PM To: Info-VAX@Mvb.Saic.Com-$ Subject: RE: Shark Tank mentions VMS         > -----Original Message-----9 > From: Stanley F. Quayle [mailto:squayle@insight.rr.com]-" > Sent: February 18, 2005 11:39 AM > To: Info-VAX@Mvb.Saic.Coms" > Subject: Shark Tank mentions VMS >=20H > http://www.computerworld.com/departments/opinions/sharktank/0,4885,998( > 78,00.html?source=3DNLT_SH&nid=3D99878 >=20 > Beware abbreviations!i >=20 > --Stan Quaylet > Quayle Consulting Inc. >=20 > ----------/ > Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 5 > 8572 North Spring Ct., Pickerington, OH  43147  USA 2 > stan-at-stanq-dot-com       http://www.stanq.com >=20 >=20   Stan,>  D Reminds me of some older VAX console commands that used to interpret& ">>>H" as short for "halt" the system.  C That is until a few incidents were reported whereby operaters wouldc@ enter ^P to get to the console and then type "H" for "help" ....   :-)c  H As I recall, subsequent versions required one to enter at least HA or HE to be recognized.h   Regardsd  
 Kerry Main Senior Consultantf HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477f kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  $ "OpenVMS has always had integrity .. Now, Integrity has OpenVMS .."    ) ----------------------------------------- L The information contained in this transmission may contain privileged and c=L onfidential information and is intended only for the use of the person(s) n=L amed above. If you are not the intended recipient, or an employee or agent =L responsible for delivering this message to the intended recipient, any revi=L ew, dissemination, distribution or duplication of this communication is str=L ictly prohibited. If you are not the intended recipient, please contact the=L  sender immediately by reply e-mail and destroy all copies of the original =L message. Please note that we do not accept account orders and/or instructio=L ns by e-mail, and therefore will not be responsible for carrying out such o= rders and/or instructions.L If you, as the intended recipient of this message, the purpose of which is =L to inform and update our clients, prospects and consultants of developments=L  relating to our services and products, would not like to receive further e=L -mail correspondence from the sender, please "reply" to the sender indicati=L ng your wishes.  In the U.S.: 1345 Avenue of the Americas, New York, NY 101= 05.-   ------------------------------  % Date: Fri, 18 Feb 2005 10:15:18 +0000e- From: Roy Omond <Roy.Omond@BlueBubble.UK.Com>f, Subject: Re: TCPIP automatic route additions, Message-ID: <37ltm5F5g3l08U1@individual.net>   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 incorrecteH >>router, which then prevents all the rest of the clients on that subnet! >>from connecting the proper way.h >>E >>It's a simple installation, with not dynamic routing enabled on thedE >>VMS side (or anywhere, if they're following my suggestion- but theypG >>did just bring a high-priced network consultant in, which is probablyo4 >>how we got this mess in the first place... *sigh*) >>- >>Anyway, the routing table should look like:  >> >>$ tcpip sho router >>& >>                             DYNAMIC >>> >>Type           Destination                           Gateway >>8 >>DN    0.0.0.0                               172.16.1.17 >>DH    127.0.0.1                             127.0.0.1s8 >>AN    172.16.0.0/22                         172.16.1.4: >>DN    <external_net>/24                      172.16.1.10 >>$ tcpip sho route /perm1 >>( >>                             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 >>$v >>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, asoF >>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 is8 >>correct, the dynamic one has an incorrect bitmask...)   G Sorry for the late addition, but this has been discussed before on cov.8  @ The solution is to disable ICMP redirects in the inet subsystem.   I.e.   	$ tcpip0 	TCPIP> sysconfig -r inet icmp_rejectcodemask=32  	 Roy Omond@ Blue Bubble Ltd.   ------------------------------  % Date: Fri, 18 Feb 2005 12:07:47 +0100a) From: "Usenet" <bruno.seghers@banksys.be>e Subject: TCPIP name cache)6 Message-ID: <4215cc9f$0$23944$ba620e4c@news.skynet.be>   Hi,.  J Is somebody could tell me how I can see the naming cache in TCPIP point of view and how I can flush it.   Thus the same as   $ mc cdi_cache_dumpe5 $ mc ncl flush session control naming cache entry "*"2   but for tcpip.  " We have a DNS based configuration.   My problem is the following :   0 A client has token a telnet session on a server.G As there is no reverse dns on the ip address of the client, the logicall( SYS$REM_NODE is equal to the ip address.I Thus SET DISPLAY/CREATE/NODE='f$trnlnm("SYS$REM_NODE")/TRANS=TCPIP  workst well  L For a management reason, the reverse resolution of the client ip address was1 activated but to an other name that the dns name.AK Thus SYS$REM_NODE was defined to a NONE_DNS_NAME , thus SET DIPLAYS no morei working.  E The reverse resolution was disabled but the NONE_DNS_NAME seems to be:6 associated in a cache to the ip address of the client.  H TTL of the reverse record : 3 hours, NONE_DNS_NAME still present after 2 days.e   Thanks for your help  
 Seghers BrunoM Belgiumi   ------------------------------  % Date: Fri, 18 Feb 2005 12:08:15 +01002) From: "Usenet" <bruno.seghers@banksys.be>  Subject: TCPIP name cachet6 Message-ID: <4215cca0$0$23944$ba620e4c@news.skynet.be>   Hi,t  J Is somebody could tell me how I can see the naming cache in TCPIP point of view and how I can flush it.   Thus the same as   $ mc cdi_cache_dumpd5 $ mc ncl flush session control naming cache entry "*"    but for tcpip.  " We have a DNS based configuration.   My problem is the following :   0 A client has token a telnet session on a server.G As there is no reverse dns on the ip address of the client, the logicald( SYS$REM_NODE is equal to the ip address.I Thus SET DISPLAY/CREATE/NODE='f$trnlnm("SYS$REM_NODE")/TRANS=TCPIP  works  well  L For a management reason, the reverse resolution of the client ip address was1 activated but to an other name that the dns name.rK Thus SYS$REM_NODE was defined to a NONE_DNS_NAME , thus SET DIPLAYS no mored working.  E The reverse resolution was disabled but the NONE_DNS_NAME seems to bed6 associated in a cache to the ip address of the client.  H TTL of the reverse record : 3 hours, NONE_DNS_NAME still present after 2 days.c   Thanks for your help  
 Seghers Brunoe Belgiumd   ------------------------------  % Date: Fri, 18 Feb 2005 06:37:36 -0500d- From: JF Mezei <jfmezei.spamnot@teksavvy.com>- Subject: Re: TCPIP name cache B Message-ID: <1108725911.f600f61a9cb72f0e240206e3e64907ae@teranews>  
 Usenet wrote:uL > Is somebody could tell me how I can see the naming cache in TCPIP point of > view and how I can flush it.  # @sys$manager:tcpip$define_commands 4 or3 ncd :== "$sys$system:tcpip$bind_server_control.exe"t   then:t   $ndc dumpdbh   This creates  0 [sys0.tcpip$bind]tcpip$bind_server_zones_dump.DB  J It includes all the stuff in its cache in what seems to be a random order.  F I *assume* that restarting the name server (there is an option in NDC,F but you can also user TCPIP SET NAME_SERVICE/INITIALIZE) would zap theG cache and reload your own zone files from scratch. But I haven't testedwF this. (only hat the set name/init does reload the local zone file, not sure about cache)m   ------------------------------  % Date: Fri, 18 Feb 2005 07:03:05 -0500l- From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: TCPIP name cache B Message-ID: <1108727435.a567f99a19b860767f6a248a3d6e7adb@teranews>  
 Usenet wrote:cK > Thus SET DISPLAY/CREATE/NODE='f$trnlnm("SYS$REM_NODE")/TRANS=TCPIP  workss > well > N > For a management reason, the reverse resolution of the client ip address was3 > activated but to an other name that the dns name.(  1 You can try instead of f$trnlnm("SYS$REM_NODE") :   " 'F$GETDVI ( "TT", "TT_ACCPORNAM" )  B However, this may yeield the same information (eg: translated name instead of IP address).   H If you have access to your own DNS server, you might be able to overrideG what the corporate server gives you. It is VERY wrong for a coprate DNS B scheme to assign a wrong name to an IP, especially if that name isG shared between many IPs since this means that you can't really tell whoT is coming into your system.r  . Right now, about the only way I have found is:  1 SHOW TERM, this gives you the remote port number.i then TCPIP SHOW DEV sG and then hnt for the line that has that remote port number, and you getm/ the IP address instead of translated host name.W  C Is there a better way to corrolate the TNAxxx: device to the BGxxx:- device ????    ------------------------------  % Date: Fri, 18 Feb 2005 08:51:07 -0800T# From: "Tom Linden" <tom@kednos.com>O Subject: Terminal connection( Message-ID: <opsmejrh0bzgicya@hyrrokkin>  F I use PuTTY from W2k to connect using SSH2 to a 7.3-2 machine and then1 DECnet to a 7.3-1 machine where I run emacs 19.28r   When I try to run emacs I getU       NORNS> emacs -nw FOO.TXT [Spawning a new Kept EMACS] - emacs: Terminal type vt102-80 is not defined. 4 If that is not the actual type of terminal you have,= use the Bourne shell command `TERM=... export TERM' (C-shell:ID `setenv TERM ...') to specify the correct type.  It may be necessary< to do `unset TERMCAP' (C-shell: `unsetenv TERMCAP') as well., [Attached to DCL in directory $7$DKA0:[TOM]]     Now in the TERM dir there is  F VT100.ELC;1         VT102.EL;1          VT125.EL;1          VT200.EL;1F VT200.ELC;1         VT201.EL;1          VT220.EL;1          VT240.EL;1   NORNS> type VT102.EL (load "term/vt100" nil t)   = Is the problem that the above lisp file is not byte compiled?y, Who is claiming that it is VT102-80,  PuTTY?  6 SHO TERM/FULL doesn't supply that form of designation.   ------------------------------  # Date: Fri, 18 Feb 2005 16:40:21 GMTa! From: Nigel Barker <nigel@hp.com>m) Subject: Re: VMS 8.2 Itanium Distribution 8 Message-ID: <2v4c1158obfjco5laa6896902hqov4q5ri@4ax.com>  F On Thu, 17 Feb 2005 03:47:34 GMT, rdeininger@mindspringdot.com (Robert Deininger) wrote:y  ? >(Yes, the VMS installation kit for Itanium is on DVD, not CD.)c  P It's on DVD for the very good reason that it doesn't fit on a CD. In fact AFAICR it wouldn't even fit on 2 CDs.   -- Nigel Barker Live from the sunny Cote d'Azurl   ------------------------------  % Date: Fri, 18 Feb 2005 11:35:17 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>i) Subject: Re: VMS 8.2 Itanium DistributionhB Message-ID: <1108743749.8025c9a5c7b2d36a5aaf6f3b13db15a0@teranews>   Nigel Barker wrote:c  eR > It's on DVD for the very good reason that it doesn't fit on a CD. In fact AFAICR  > it wouldn't even fit on 2 CDs.  A I can understand executables bloating from VAX to Alpha since allaD pointers/adresses double in size from 32 to 64 bits, and if you haveC instructions containing 2 adddresses, that makes things even worse.s  G But from Alpha to IA64, since both are 64 bits, how come there would bee= so much difference in size between 600meg and over 1200 meg ?c  @ Is the bloat due to truly bigger .exe files ? Or are there extra0 components bundled into the OS installtion CDs ?   ------------------------------   End of INFO-VAX 2005.098 ************************