1 INFO-VAX	Tue, 01 Mar 2005	Volume 2005 : Issue 120       Contents: Re: Backup /ALIAS question Re: Backup /ALIAS question Re: Backup /ALIAS question Re: Backup /ALIAS question Build problems - Freetype  Re: Build problems - Freetype  Re: CDRECORD v. RMS defaults# Re: Changing Tape Device protection ' Re: Checking for "file open for write". " DECC : toupper/tolower performance& Re: DECC : toupper/tolower performance& Re: DECC : toupper/tolower performance& Re: DECC : toupper/tolower performance* Re: Has anyone had any bad T4 experiences?) Identify the process locking a RMS record - Re: Identify the process locking a RMS record - RE: Identify the process locking a RMS record - Re: Identify the process locking a RMS record - Re: Identify the process locking a RMS record K RE: Interesting error message I just got trying to access accuwea		ther.com K Re: Interesting error message I just got trying to access accuwea	 ther.com J RE: Interesting error message I just got trying to access accuwea	ther.comJ Re: Interesting error message I just got trying to access accuwea	ther.comJ RE: Interesting error message I just got trying to access accuwea	ther.comJ Re: Interesting error message I just got trying to access accuwea	ther.comJ Re: Interesting error message I just got trying to access accuwea	ther.comJ Re: Interesting error message I just got trying to access accuwea ther.comJ Re: Interesting error message I just got trying to access accuwea ther.comP Re: Interesting error message I just got trying to access accuwea ther.com ther.P Re: Interesting error message I just got trying to access accuwea ther.com ther.& Re: new Itanium after Tukwila: Poulson& Re: new Itanium after Tukwila: Poulson NTP and timezones  Re: NTP and timezones  Re: NTP and timezones 8 Re: OpenVMS Seminar in Toronto (2005-02-24) a few points Re: Ouch! a *MAJOR* bug in TPU. & Re: Problem with a DEC terminal server& Re: Problem with a DEC terminal server& Re: Problem with a DEC terminal server Re: Sayonara Tukwilla  Re: Sayonara Tukwilla 1 RE: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End... 1 Re: This is the End... My Only Friend, The End...  Re: VMS Alpha 8.2 with CSWS 2.0  Re: VMS Alpha 8.2 with CSWS 2.0  Re: VMS Alpha 8.2 with CSWS 2.0  Re: VMS Alpha 8.2 with CSWS 2.0  Re: VMS Alpha 8.2 with CSWS 2.0  RE: VMS Alpha 8.2 with CSWS 2.0 0 VMS V8.2 Source Listings (Shipping Confirmation)4 Re: VMS V8.2 Source Listings (Shipping Confirmation)4 Re: VMS V8.2 Source Listings (Shipping Confirmation)< Re: What is the Difference between Shadow and Mirrored disk?< Re: What is the Difference between Shadow and Mirrored disk?< Re: What is the Difference between Shadow and Mirrored disk?  F ----------------------------------------------------------------------  $ Date: Tue, 1 Mar 2005 09:20:24 -0500* From: "Syltrem" <syltremzulu@videotron.ca># Subject: Re: Backup /ALIAS question 1 Message-ID: <LR_Ud.140$g4.2465@tor-nn1.netcom.ca>   9 "AEF" <spamsink2001@yahoo.com> a crit dans le message de = news:1109648336.332378.165940@f14g2000cwb.googlegroups.com...  >  > Syltrem wrote:) > > I use /NOALIAS whenever I do a /IMAGE  > > 0 > > But the problem is on the restore operation.F > > When restoring directories with aliases, I have to manually do SET! > > FILE/ENTER after the restore.  > > / > > $ back sys$sysdevice:[sys*...]*.*.*/noalias % > > $1$dga64:[temp]s.bck/sav/igno=int  > > erl ) > > %BACKUP-W-ADNOTSAVED, alias directory % > SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR;1 
 > > and it > > s directory tree not saved) > > %BACKUP-W-ADNOTSAVED, alias directory % > SYS$SYSDEVICE:[SYS1]SYSCOMMON.DIR;1 
 > > and it > > s directory tree not savedH > > %BACKUP-W-AFNOTSAVED, alias file SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR;1	 > was not  > > sav  > > edH > > %BACKUP-W-AFNOTSAVED, alias file SYS$SYSDEVICE:[SYS1]SYSCOMMON.DIR;1	 > was not  > > sav  > > ed > > $ A > > $ back $1$dga64:[temp]s.bck/sav $1$dga64:[temp...]*.*.*/alias + > > $ dir $1$dga64:[temp.sys0]SYSCOMMON.dir % > > %DIRECT-W-NOFILES, no files found  > >  > > This is very cumbersome. > > H > > If, otoh, I use the /ALIAS qualifier in the backup, the restore will > create: > > multiple copies of the files, which is somewhat worse. > > B > > Anyone knows how to do a good restore with file aliases? I can > recreate them I > > manually because I know what they are on my system, but it's far from  > being 
 > > ideal. > H > Why would you want to do this? If you are restoring a system disk, youD > need to use /IMAGE and then the aliases are restored properly. TheH > BACKUP utility was not designed with what you want to do here in mind. > H > IOW: Why would you want [temp.sys0...], [temp.sys1...], etc., with allG > the "common directories" aliased as they would be on a regular system  > disk?    This was just an example. F Usually I do this to restore to the original directory in its original/ location (albeit on a different disk) of course  But the end result is the same  H I believe David and John are right that there is a difference in the wayH directory files (.DIR) are backed up/restored with the /IMAGE qualifier.  B Thing is, for instance, that I recently wanted to move my MultinetA installation to a test machine. Didn't want the entire disk, just K [MULTINET...] so I could not use /IMAGE. And I had to manually recreate the  aliases after the restore.  > Normally you want to do this for a system disk, and you do use, /IMAGE/NOALIAS, and I believe it would work.
 Let's see: $ mount dka100: /for" $ back/image/noalias dka0: dka100:! $ mount dka100 /over=id popo popo $ $ dir/fil dka100:[sys%]syscommon.dir   Directory DKA100:[SYS0]  SYSCOMMON.DIR;1      (12,1,0)  Total of 1 file. Directory DKA100:[SYSE]  SYSCOMMON.DIR;1      (12,1,0)  Total of 1 file.  & Grand total of 2 directories, 2 files.   With /IMAGE all is fine.  F So it appears we have to keep track of aliases if not using the /IMAGE1 qualifier (as per first example above). Not good.        --   Syltrem   H http://pages.infinit.net/syltrem (OpenVMS related web site, en franais) >    ------------------------------   Date: 1 Mar 2005 07:54:17 -0800 $ From: "AEF" <spamsink2001@yahoo.com># Subject: Re: Backup /ALIAS question B Message-ID: <1109692457.758073.14910@f14g2000cwb.googlegroups.com>   John Santos wrote: > JF Mezei wrote: 
 > > Question:  > > 0 > > when I am in the directory:  $DISK:[RECIPES] > > G > > and I do SET FILE/ENTER=[CHOCOLATE]MOUSSE.TXT  CHOCOLATE_MOUSSE.TXT  > > ? > > Is it correct to state that all it does is update the file:  > > % > >  $DISK:[000000]RECIPES.DIR   ????  > 8 > No, but almost. It updates $disk:[000000]chocolate.dir > D > > adding name chocolate_mousse.txt and pointing the the file-ID of the  > > [chocolate]mousse.txt ?  > + > You have the file and the alias reversed.  > 0 > $ set file/enter=ALIAS-SPEC EXISTING-FILE-SPEC > ? > Your command creates an entry in CHOCOLATE.DIR using the name B > MOUSSE.TXT pointing to the existing CHOCOLATE_MOUSSE.TXT located > in the current directory.      Correct.    2 > (I wasn't sure about the order, so I tested it.) >  > > G > > As such, when you do a backup/image/noalias, is it correct to state  thatC > > the contents of $disk:[000000]recipes.dir will be saved to disk 2 > > including the info on the aliased file entry ? >  > I think this is how it works.     B Yes. BACKUP/IMAGE/NOALIAS walks the directory structure in "BACKUPB order". During this it saves all primary files, including the .DIRC files *and their contents*. It is these .DIR files that contain the 5 alias information (in the form of directory entries).     G > > Or does BACKUP/IMAGE treat .DIR files as /NOBACKUP ,saving only the , > > file's attributes and not its contents ?    7 No. Image backups save also the data in the .DIR files.     F > I think an image backup preserves file-ids, just so the above method    F Yes, FID's are preserved and the .DIR files are saved and restored "as& is" (or should that be "as are"? :-) .    G > of preserving aliases will work, (though it releases unused extension E > headers, so you might end up with a sparesly-populated INDEXF.SYS.)  > A > We need a backup expert to answer this authoritatively, though.  >  > --
 > John Santos  > Evans Griffiths & Hart, Inc. > 781-861-0670 ext 539   ------------------------------  % Date: Tue, 01 Mar 2005 11:32:07 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> # Subject: Re: Backup /ALIAS question B Message-ID: <1109693979.44f46fc5ae47184dd22f7b3e294301bd@teranews>  
 AEF wrote:D > Yes. BACKUP/IMAGE/NOALIAS walks the directory structure in "BACKUPD > order". During this it saves all primary files, including the .DIRE > files *and their contents*. It is these .DIR files that contain the 7 > alias information (in the form of directory entries).   G Is it correct then to state that /ALIAS or /NOALIAS makes no difference  to an image restore operation ?    ------------------------------   Date: 1 Mar 2005 08:22:41 -0800 $ From: "AEF" <spamsink2001@yahoo.com># Subject: Re: Backup /ALIAS question B Message-ID: <1109694161.228396.69050@l41g2000cwc.googlegroups.com>   Syltrem wrote:= > "AEF" <spamsink2001@yahoo.com> a =E9crit dans le message de ? > news:1109648336.332378.165940@f14g2000cwb.googlegroups.com...  > >  > > Syltrem wrote:+ > > > I use /NOALIAS whenever I do a /IMAGE  > > > 2 > > > But the problem is on the restore operation.D > > > When restoring directories with aliases, I have to manually do SET # > > > FILE/ENTER after the restore.  > > > 1 > > > $ back sys$sysdevice:[sys*...]*.*.*/noalias ) > > > $1$dga64:[temp]s.bck/sav/igno=3Dint 	 > > > erl + > > > %BACKUP-W-ADNOTSAVED, alias directory ' > > SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR;1  > > > and it  > > > s directory tree not saved+ > > > %BACKUP-W-ADNOTSAVED, alias directory ' > > SYS$SYSDEVICE:[SYS1]SYSCOMMON.DIR;1  > > > and it  > > > s directory tree not saved& > > > %BACKUP-W-AFNOTSAVED, alias file# SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR;1  > > was not 	 > > > sav  > > > ed& > > > %BACKUP-W-AFNOTSAVED, alias file# SYS$SYSDEVICE:[SYS1]SYSCOMMON.DIR;1  > > was not 	 > > > sav  > > > ed > > > $ C > > > $ back $1$dga64:[temp]s.bck/sav $1$dga64:[temp...]*.*.*/alias - > > > $ dir $1$dga64:[temp.sys0]SYSCOMMON.dir ' > > > %DIRECT-W-NOFILES, no files found  > > >  > > > This is very cumbersome. > > > E > > > If, otoh, I use the /ALIAS qualifier in the backup, the restore  will
 > > create< > > > multiple copies of the files, which is somewhat worse. > > > D > > > Anyone knows how to do a good restore with file aliases? I can > > recreate them F > > > manually because I know what they are on my system, but it's far from	 > > being  > > > ideal. > > F > > Why would you want to do this? If you are restoring a system disk, you F > > need to use /IMAGE and then the aliases are restored properly. TheD > > BACKUP utility was not designed with what you want to do here in mind.  > > F > > IOW: Why would you want [temp.sys0...], [temp.sys1...], etc., with all B > > the "common directories" aliased as they would be on a regular system	 > > disk?  >  > This was just an example. ? > Usually I do this to restore to the original directory in its  original1 > location (albeit on a different disk) of course   > But the end result is the same > F > I believe David and John are right that there is a difference in the way ? > directory files (.DIR) are backed up/restored with the /IMAGE 
 qualifier.  E They are correct. The restoration of .DIR files is very different. In B /IMAGE restores, the .DIR files are restored "as is". In non-imageF restores the .DIR files are created only if they don't exist. It is as= if you were creating the entire directory path for each file.   : So if you are restoring a non-image save set that contains   [AAA]BBB.DIR [AAA.BBB]FILE.TXT  [AAA.BBB]FILE2.TXT   then the following happens:   A BBB.DIR is created empty if it does not already exist. If it does G already exist, then nothing is done. FILE.TXT is added to [AAA.BBB] and G given a new FID on the fly. FILE2.TXT is added to [AAA.BBB] and given a F new FID on the fly. Since data from the .DIR file is not copied to the disk, any aliases are lost.   A (If /INCREMENTAL is specified, then the .DIR files are updated as C needed for incremental restorations. For example, directory entries F must be created for files that existed at the save-time of the currentE save set, but were saved to a previous save set. This would mean that ? the data in the .DIR files is saved even in non-image save sets  (perhaps sans FID's).)   > D > Thing is, for instance, that I recently wanted to move my MultinetC > installation to a test machine. Didn't want the entire disk, just @ > [MULTINET...] so I could not use /IMAGE. And I had to manually recreate the > aliases after the restore.    B That is correct. BACKUP is not designed to do that as I said in my previous post.    @ > Normally you want to do this for a system disk, and you do use. > /IMAGE/NOALIAS, and I believe it would work. > Let's see: > $ mount dka100: /for$ > $ back/image/noalias dka0: dka100:% > $ mount dka100 /over=3Did popo popo & > $ dir/fil dka100:[sys%]syscommon.dir >  > Directory DKA100:[SYS0]  > SYSCOMMON.DIR;1      (12,1,0)  > Total of 1 file. > Directory DKA100:[SYSE]  > SYSCOMMON.DIR;1      (12,1,0)  > Total of 1 file. > ( > Grand total of 2 directories, 2 files. >  > With /IMAGE all is fine. > A > So it appears we have to keep track of aliases if not using the  /IMAGE3 > qualifier (as per first example above). Not good.     G Correct. Only /IMAGE will preserve aliases. (Would /INCREMENTAL restore 0 any new aliases? I'll have to try that one day.)  B It seems to me that aliases in VMS were made primarly (and perhapsF only) to support the SYSCOMMON structure and BACKUP/IMAGE was designed> to handle it properly. For other (non-documented) uses you are basically on your own.   ------------------------------    Date: 28 Feb 2005 23:54:13 -0800 From: mcbill20@yahoo.com" Subject: Build problems - FreetypeC Message-ID: <1109663653.645952.190550@l41g2000cwc.googlegroups.com>   F I am still trying to get GDCHART to work. After many aborted attempts,? I deleted everything (multiple times) and decided to start from D scratch. I have tried some older versions form the VMS freeware CD'sF after all my problems with stuff I got from the freeware pointers from this group--I specifically:(http://www.quadratrix.be/products/open_source_material.html  ).  E I downloaded the original tarballs form the pointers at the above URL D and then the zip files containing the fixes. The zip files generallyE contained two files: a "qport.com" and a "[.contrib.vms]descrip.vms]. 6 When I tried to run the qport.com I got the following:  0 Building FreeType 2.1.7 for OpenVMS Alpha V7.3-1  D %MMK-F-MACFILSYNTAX, syntax error at line 1 in macro definition file BUILD_DEV:[ , FREETYPE-2_1_7.CONTRIB.VMS]MFILE.MMS_ALPHA;8    G Right now I am trying to get Freetype version 2-1-9 to work. The source E already included a vms_make.com. Unfortunately, it chokes when trying B to compile truetype.c. Apparently it has a problem with a macro inC FTMEMORY.H.  I don't know if it's sloppy code or a problem with the E behavior in the VMS compiler but I can't seem to get it to work. Here 2 is the output. I would appreciate any suggestions.   Thanks.  Bill  	 VMS 7.3-1 	 DEC C 6.5 	 MMK 3.9-6    $ @vms_make  Creating descrip.mms files ... ... Main directory ... [.builds.vms] directory  ... [.src.autohint] directory  ... [.src.gzip] directory  ... [.src.lzw] directory ... [.src.type1] directory% define freetype [--.include.freetype] @ %DCL-I-SUPERSEDE, previous value of FREETYPE has been superseded define psaux [-.psaux]= %DCL-I-SUPERSEDE, previous value of PSAUX has been superseded  define autohint [-.autohint]@ %DCL-I-SUPERSEDE, previous value of AUTOHINT has been superseded define base [-.base]< %DCL-I-SUPERSEDE, previous value of BASE has been superseded define cache [-.cache]= %DCL-I-SUPERSEDE, previous value of CACHE has been superseded  define cff [-.cff]; %DCL-I-SUPERSEDE, previous value of CFF has been superseded  define cid [-.cid]; %DCL-I-SUPERSEDE, previous value of CID has been superseded  define pcf [-.pcf]; %DCL-I-SUPERSEDE, previous value of PCF has been superseded  define psnames [-.psnames]? %DCL-I-SUPERSEDE, previous value of PSNAMES has been superseded  define raster [-.raster]> %DCL-I-SUPERSEDE, previous value of RASTER has been superseded define sfnt [-.sfnt]< %DCL-I-SUPERSEDE, previous value of SFNT has been superseded define smooth [-.smooth]> %DCL-I-SUPERSEDE, previous value of SMOOTH has been superseded define truetype [-.truetype]@ %DCL-I-SUPERSEDE, previous value of TRUETYPE has been superseded define type1 [-.type1]= %DCL-I-SUPERSEDE, previous value of TYPE1 has been superseded  define winfonts [-.winfonts]@ %DCL-I-SUPERSEDE, previous value of WINFONTS has been superseded< if f$search("lib.dir") .eqs. "" then create/directory [.lib] set default [.builds.vms]  MMK/MACRO=(COMP_FLAGS="") 5 CC/include=([],[--.include],[--.src.base]) FTSYSTEM.C 0 library/create [--.lib]freetype.olb ftsystem.obj set default [--.src.autohint]  MMK/MACRO=(COMP_FLAGS="") 3 CC/incl=([--.include],[--.src.autohint]) AUTOHINT.C ) library [--.lib]freetype.olb autohint.obj  set default [-.base] MMK/MACRO=(COMP_FLAGS="") @ CC/include=([--.builds.vms],[--.include],[--.src.base]) FTBASE.C@ CC/include=([--.builds.vms],[--.include],[--.src.base]) FTINIT.CA CC/include=([--.builds.vms],[--.include],[--.src.base]) FTGLYPH.C A CC/include=([--.builds.vms],[--.include],[--.src.base]) FTDEBUG.C ? CC/include=([--.builds.vms],[--.include],[--.src.base]) FTBDF.C > CC/include=([--.builds.vms],[--.include],[--.src.base]) FTMM.CA CC/include=([--.builds.vms],[--.include],[--.src.base]) FTTYPE1.C @ CC/include=([--.builds.vms],[--.include],[--.src.base]) FTXF86.C? CC/include=([--.builds.vms],[--.include],[--.src.base]) FTPFR.C B CC/include=([--.builds.vms],[--.include],[--.src.base]) FTSTROKE.CB CC/include=([--.builds.vms],[--.include],[--.src.base]) FTWINFNT.C@ CC/include=([--.builds.vms],[--.include],[--.src.base]) FTBBOX.C library [--.lib]freetype.olb3 ftbase.obj,ftinit.obj,ftglyph.obj,ftdebug.obj,ftbdf P .obj,ftmm.obj,fttype1.obj,ftxf86.obj,ftpfr.obj,ftstroke.obj,ftwinfnt.obj,ftbbox. obj  set default [-.bdf]  MMK/MACRO=(COMP_FLAGS="") , CC/include=([--.include],[--.src.bdf]) BDF.C$ library [--.lib]freetype.olb bdf.obj set default [-.cache]  MMK/MACRO=(COMP_FLAGS="") 2 CC/include=([--.include],[--.src.cache]) FTCACHE.C  -     if ( family && --family->num_nodes <= 0 )  ...................^> %CC-I-QUESTCOMPARE, In this statement, the unsigned expression "--family->num_no E des" is being compared with a relational operator to a constant whose 
 value is n; ot greater than zero.  This might not be what you intended.  at line number 50 in file 0 BUILD_DEV:[FREETYPE-2_1_9.SRC.CACHE]ftcglyph.c;2( library [--.lib]freetype.olb ftcache.obj set default [-.cff]  MMK/MACRO=(COMP_FLAGS="") , CC/include=([--.include],[--.src.cff]) CFF.C$ library [--.lib]freetype.olb cff.obj set default [-.cid]  MMK/MACRO=(COMP_FLAGS="") 1 CC/include=([--.include],[--.src.cid]) TYPE1CID.C ) library [--.lib]freetype.olb type1cid.obj  set default [-.gzip] MMK/MACRO=(COMP_FLAGS="") 0 CC/include=([--.include],[--.src.gzip]) FTGZIP.C' library [--.lib]freetype.olb ftgzip.obj  set default [-.lzw]  MMK/MACRO=(COMP_FLAGS="") . CC/include=([--.include],[--.src.lzw]) FTLZW.C& library [--.lib]freetype.olb ftlzw.obj set default [-.pcf]  MMK/MACRO=(COMP_FLAGS="") , CC/include=([--.include],[--.src.pcf]) PCF.C$ library [--.lib]freetype.olb pcf.obj set default [-.pfr]  MMK/MACRO=(COMP_FLAGS="") , CC/include=([--.include],[--.src.pfr]) PFR.C$ library [--.lib]freetype.olb pfr.obj set default [-.psaux]  MMK/MACRO=(COMP_FLAGS="") 0 CC/include=([--.include],[--.src.psaux]) PSAUX.C& library [--.lib]freetype.olb psaux.obj set default [-.pshinter] MMK/MACRO=(COMP_FLAGS="") 5 CC/include=([--.include],[--.src.psnames]) PSHINTER.C ) library [--.lib]freetype.olb pshinter.obj  set default [-.psnames]  MMK/MACRO=(COMP_FLAGS="") 4 CC/include=([--.include],[--.src.psnames]) PSNAMES.C( library [--.lib]freetype.olb psnames.obj set default [-.raster] MMK/MACRO=(COMP_FLAGS="") 2 CC/include=([--.include],[--.src.raster]) RASTER.C' library [--.lib]freetype.olb raster.obj  set default [-.sfnt] MMK/MACRO=(COMP_FLAGS="") . CC/include=([--.include],[--.src.sfnt]) SFNT.C% library [--.lib]freetype.olb sfnt.obj  set default [-.smooth] MMK/MACRO=(COMP_FLAGS="") 2 CC/include=([--.include],[--.src.smooth]) SMOOTH.C' library [--.lib]freetype.olb smooth.obj  set default [-.truetype] MMK/MACRO=(COMP_FLAGS="") 6 CC/include=([--.include],[--.src.truetype]) TRUETYPE.C  9     if ( ( error = FT_NEW_ARRAY( delta_xy, n_points ) ) ) 
 .........^4 %CC-W-UNDEFVARMOD, In this statement, the expressionD "(error=((error=(FT_Alloc(...)))!=0))" modifies the variable "error"G more than once without an intervening sequence point.  This behavior is 
 undefined. at line number 1322 in file 2 BUILD_DEV:[FREETYPE-2_1_9.SRC.TRUETYPE]ttgxvar.c;2D %MMK-F-ERRUPD, error status %X10B91260 occurred when updating target TRUETYPE.OBJD %MMK-F-ERRUPD, error status %X1C14803C occurred when updating target ALL  $    ------------------------------   Date: 1 Mar 2005 07:21:29 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) & Subject: Re: Build problems - Freetype3 Message-ID: <8sd3UZBsNJJ2@eisner.encompasserve.org>   ^ In article <1109663653.645952.190550@l41g2000cwc.googlegroups.com>, mcbill20@yahoo.com writes:  ; >     if ( ( error = FT_NEW_ARRAY( delta_xy, n_points ) ) )  > .........^6 > %CC-W-UNDEFVARMOD, In this statement, the expressionF > "(error=((error=(FT_Alloc(...)))!=0))" modifies the variable "error"  7    It looks like FT_NEW_ARRAY expands to something like C    error=(FT_Alloc(...).  If so it's a genuine undefined behaviour, C    although in this case the compiler is most likely to do what the 3    programmer expected.  The correct code would be:   ,    if ( FT_NEW_ARRAY( delta_xy, n_points ) )   ------------------------------   Date: 1 Mar 2005 09:57:26 +0100 C From: vaxinf@chclu.chemie.uni-konstanz.de (Eberhard Heuser-Hofmann) % Subject: Re: CDRECORD v. RMS defaults 2 Message-ID: <42242e76$1@merkur.rz.uni-konstanz.de>  < In article <4223E199.74ED4D5F@comcast.net>, David J Dachtera# <djesys.nospam@comcast.net> writes:  >Eberhard Heuser-Hofmann wrote:  >>  F >> In article <05022716211763_27800279@antinode.org>, sms@antinode.org
 >> (Steven >> M. Schweda) writes:G >> >From: vaxinf@chclu.chemie.uni-konstanz.de (Eberhard Heuser-Hofmann)  >> >I >> >> >   It's possible that mkisofs could be made to write an image file  >a8 >> >> >little faster, too, but I haven't looked at that. >> >> * >> >> I assume a huge speedup for mkisofs. >> >J >> >   On a small test (22MB), just "SET RMS /BLOCK = 127 /EXTEND = 16384"G >> >cut the time from about 50s to about 15s.  Perhaps two buffers with J >> >read-ahead/write-behind would help a bit more.  Clearly, there's a lot/ >> >of potential for improvement in this stuff.  >> >E >> >> >   I haven't looked elsewhere lately, either.  How obsolete is  >1.8.1?  >> >> C >> >> V1.8.1 of cdrecord  is a stone age version. V2.x ist the most  >recent. >> >H >> >   Well, it's all newer than my hardware.  I see that the version ofF >> >CDRECORD supplied by HP is 1.10.  Does anyone know if any work was >done 0 >> >on it, or was it just captured and packaged? >>  I >> ftp://v36.chemie.uni-konstanz.de/CDRECORD_VMS/CDRTOOLS-2_01A24_VMS.ZIP  >>  J >> If you are a little bit patient, a newer version is online for download >> soon. >>  J >> BTW: Something seems be wrong with the newest dqdriver, that comes withJ >> VMS732_DRIVER-V0100. If the is no disk inserted in my DVD-burner during< >> startup the drive goes offline and remains in that state. > G >Hhmmm... sounds like what we see on our GS160s, now that we're running @ >V7.3-2. Nothing in the drives at boot time means the drives areB >inaccessible. It's a development cluster, so can't bounce it like% >dribbling a basketball to test that.  >    This is a great idea:   ? OpenVMS only comes up, if a special CD/DVD is plugged in during 9 the boot process. The SIMS2 provides similar features ...    eberhard   ------------------------------   Date: 1 Mar 2005 06:36:58 -0600 - From: Kilgallen@SpamCop.net (Larry Kilgallen) , Subject: Re: Changing Tape Device protection3 Message-ID: <9$+GkXu5k6QA@eisner.encompasserve.org>   ` In article <4223E200.EC0FFF7A@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes:  D > I have to do something similar at startup time, or even SLS cannot' > access the fibre-channel tape drives.   F There is supposed to be a way to make protections persist across boots& by using the device security database.   ------------------------------   Date: 1 Mar 2005 04:48:02 -0800 * From: "Alan Greig" <greigaln@netscape.net>0 Subject: Re: Checking for "file open for write".C Message-ID: <1109681282.873242.140460@f14g2000cwb.googlegroups.com>    Bob Koehler wrote:9 > In article <cbfUd.57928$uc.15795@trnddc04>, John Santos  <john@egh.com> writes: > >  > F >    In order to allow for broken connections, FTP saves as much as itC >    gets and implements a restart capability.  I've never seen the & >    latter used, but it's in the RFC.  @ Web browsers, download managers etc all implement this. Most ftpD servers support it including most (all?) of the VMS ones these days.8 Mosaic, Mozilla, Netscape all implemented it under VMS.    --
 Alan Greig   ------------------------------  % Date: Tue, 01 Mar 2005 12:38:38 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> + Subject: DECC : toupper/tolower performance B Message-ID: <1109697967.846299e2b11a48e9742a810baa402624@teranews>  C I need to do a case insensitive comparison. I looked at the toupper H macro and while it works, i was wondering about peformance ( it seems to do a lot of checking).  E Would it be faster to just have an array of 256 bytes and just lookup ? the translated character based on the value of the untranslated  character ?   # newchar = uppercase[oldchar] ;  ???   D or does DECC end up taking mroe juice out of the VAX CPU for such an operation compared to:   newchar = toupper(oldchar) ;  5 (I can setup my own translation table fairly easily).    ------------------------------   Date: 1 Mar 2005 12:23:22 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) / Subject: Re: DECC : toupper/tolower performance 3 Message-ID: <GPs3YCPQQNF1@eisner.encompasserve.org>   r In article <1109697967.846299e2b11a48e9742a810baa402624@teranews>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > E > I need to do a case insensitive comparison. I looked at the toupper J > macro and while it works, i was wondering about peformance ( it seems to > do a lot of checking). > G > Would it be faster to just have an array of 256 bytes and just lookup A > the translated character based on the value of the untranslated 
 > character ?  > % > newchar = uppercase[oldchar] ;  ???  > F > or does DECC end up taking mroe juice out of the VAX CPU for such an > operation compared to: >  > newchar = toupper(oldchar) ;  G    I suspect you may see some small performance gain using str$upcase()     over looping on toupper().   G    If you want to do the translation via table lookup, consider feeding     the table to lib$movtc.   ------------------------------  # Date: Tue, 01 Mar 2005 18:59:13 GMT * From: "FredK" <fred.nospam@nospam.dec.com>/ Subject: Re: DECC : toupper/tolower performance . Message-ID: <5Y2Vd.784$m04.7@news.cpqcorp.net>  D Note: Doing case blind conversions by upcasing generally speaking is only valid for ASCII.   A In any case, upcase is a range check and a bit clear, fairly fast B register operations.  A lookup would not need to do this, but does# require an additional memory fetch.     : "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message< news:1109697967.846299e2b11a48e9742a810baa402624@teranews... > E > I need to do a case insensitive comparison. I looked at the toupper J > macro and while it works, i was wondering about peformance ( it seems to > do a lot of checking). > G > Would it be faster to just have an array of 256 bytes and just lookup A > the translated character based on the value of the untranslated 
 > character ?  > % > newchar = uppercase[oldchar] ;  ???  > F > or does DECC end up taking mroe juice out of the VAX CPU for such an > operation compared to: >  > newchar = toupper(oldchar) ; > 7 > (I can setup my own translation table fairly easily).    ------------------------------  % Date: Tue, 01 Mar 2005 10:38:01 -0800  From: Z <Z@no.spam> / Subject: Re: DECC : toupper/tolower performance * Message-ID: <oE2Vd.2682$R_6.1710@fe04.lga>   JF Mezei wrote: E > I need to do a case insensitive comparison. I looked at the toupper J > macro and while it works, i was wondering about peformance ( it seems to > do a lot of checking). > G > Would it be faster to just have an array of 256 bytes and just lookup A > the translated character based on the value of the untranslated 
 > character ?   ' have you looked at  _toupper/_tolower ?    ------------------------------  $ Date: Tue, 1 Mar 2005 09:58:50 -0500# From: "John Smith" <a@nonymous.com> 3 Subject: Re: Has anyone had any bad T4 experiences? , Message-ID: <m_ydnfITVfW3HrnfRVn-1A@igs.net>   David J Dachtera wrote:  > Thomas Wirt wrote: >>C >> I am preparing to install T4 on my AS 4100's (VMS 7.3-1) and was @ >> wondering what experiences anyone else had had.  Does it workG >> seamlessly?  Any crashes or performance hits?  Is it as useful as it 	 >> looks?  > H > Trouble with T4 is, its a collector - ONLY. The truly useful bit - theF > reporting and analysis pieces - remain MIA (ever since the demise of > PSPA and SPM). > H > T4 outputs CSV data that will easily choke Excel. TLViz is intended toH > deal with it, that's all TLViz provides: "Time Line Visualization". No > ASCII histograms, etc.    B Stuff it into a RDBMS and analyze it with el cheapo (relative to aK VMS-available app) copy of a PC (gag) stats package (SPSS, PC-STAT, etc...) J or SAS if you've got it. Even tools like MathCAD and Mathematica should be able to do a credible job.   --- OpenVMS - The classics never go out of style.    ------------------------------   Date: 1 Mar 2005 07:44:05 -0800 & From: tlywong@gmail.com (Terence Wong)2 Subject: Identify the process locking a RMS record= Message-ID: <87af9e83.0503010744.618ca5b8@posting.google.com>   @ We had problem to identify application process locking a record.  D Before any program change, is there any VMS utility show the process locking the record ?  C Also how to identify the process locking the record through ANALYZE 	 /SYSTEM ?     Thanks for any input in advance,   Terence.   ------------------------------  % Date: Tue, 01 Mar 2005 17:36:18 +0100 5 From: Philippe Marmillod <philippe.marmillod@epfl.ch> 6 Subject: Re: Identify the process locking a RMS record) Message-ID: <422499f3$1@epflnews.epfl.ch>   ) AMDS is nice to display interprocess lock    Terence Wong wrote: B > We had problem to identify application process locking a record. > F > Before any program change, is there any VMS utility show the process > locking the record ? > E > Also how to identify the process locking the record through ANALYZE  > /SYSTEM ?  > " > Thanks for any input in advance, > 
 > Terence.   ------------------------------  $ Date: Tue, 1 Mar 2005 11:49:49 -0500' From: "Main, Kerry" <kerry.main@hp.com> 6 Subject: RE: Identify the process locking a RMS recordR Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB53F928@tayexc19.americas.cpqcorp.net>   Hello Terry,  G As a suggestion, you may want to consider the Availability Manager that 9 is available for free download at the following location:   > http://h71000.www7.hp.com/openvms/products/availman/index.html  + Client piece can run on OpenVMS or Windows.2   Regards2  
 Kerry Main Solutions Architecte Hewlett-Packard (Canada) Co.! Consulting & Integration Services/ Voice: 613-592-4660a Fax   : 613-591-4477 Email: Kerry.Main@hp.com =20    > -----Original Message-----2 > From: Terence Wong [mailto:tlywong@gmail.com]=20 > Sent: March 1, 2005 10:44 AM > To: Info-VAX@Mvb.Saic.Comt4 > Subject: Identify the process locking a RMS record >=20B > We had problem to identify application process locking a record. >=20F > Before any program change, is there any VMS utility show the process > locking the record ? >=20E > Also how to identify the process locking the record through ANALYZEs > /SYSTEM ?S >=20" > Thanks for any input in advance, >=20
 > Terence. >=20   ------------------------------  # Date: Tue, 01 Mar 2005 17:31:33 GMTu# From: hoff@hp.nospam (Hoff Hoffman).6 Subject: Re: Identify the process locking a RMS record0 Message-ID: <VF1Vd.775$_X3.351@news.cpqcorp.net>  f In article <87af9e83.0503010744.618ca5b8@posting.google.com>, tlywong@gmail.com (Terence Wong) writes:A :We had problem to identify application process locking a record.y     OpenVMS version?  E :Before any program change, is there any VMS utility show the processe :locking the record ?t  D   AMDS or its more current version, Availability Manager, make this @   easy -- current versions are licensed with OpenVMS, are easily>   installed, and make finding a blocking lock blindingly easy.  E   When I have this situation, I tend to code the applications to playcD   more nicely with the record locks, where the application detects aD   long hold time for itself, and backs off the lock.  Where I do notB   need the record lock, I do not acquire it.  Both are obvious, of@   course, and are certainly not the only way to go after what isE   usually a coding or design problem within the application -- I haveeA   had my share of these errors over the years; errors I've eithera/   committed, or that I have found and resolved.   D :Also how to identify the process locking the record through ANALYZE
 :/SYSTEM ?  G   Current SDA versions are better at this.  Older releases are somewhatsE   of an "adventure" when tracing the lock trees around a cluster.  OnnE   the current versions, SHOW LOCK is pretty easy to use and to follow.G   around.  On older releases, again, it'll be more of an "adventure" --nG   you will want to look at the lock resource name documentation, if youTE   take this SDA tactic, too -- you'll need to know what the RMS lock sF   names look like, and how the locks are structured.  IIRC, this is in+   the internals and data structures manual..  C   Me?  I'd install Avaibility Manager or AMDS, and be done with it. C   Look for which process is holding a lock that is blocking others,lD   and work out from there -- the IDSM can still be useful here, too,G   though simpler cluster configurations and stand-along can potentiallyeF   be easy to resolve without knowledge of the specific resource names.    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com2   ------------------------------  % Date: Tue, 01 Mar 2005 12:18:10 -0500:- From: JF Mezei <jfmezei.spamnot@teksavvy.com>06 Subject: Re: Identify the process locking a RMS recordB Message-ID: <1109696740.f973f58f48044784d92943851537f965@teranews>   Hoff Hoffman wrote:cE >   Me?  I'd install Avaibility Manager or AMDS, and be done with it.    Is there a solution for VAX ?    ------------------------------  $ Date: Tue, 1 Mar 2005 09:03:37 -0600/ From: "Stuart, Ed" <Ed.Stuart@austinenergy.com>sT Subject: RE: Interesting error message I just got trying to access accuwea		ther.comT Message-ID: <DA4AD590CAF06845B671C398333A89C6082E26EF@ohms.electric.ci.austin.tx.us>  E  You're usually on the downside of everything, but please do not post " without checking your facts first.  : OS, Web Server and Hosting History for encompasserve.org  H http://encompasserve.org was running OSU on OpenVMS when last queried at2 1-Mar-2005 15:03:30 GMT - refresh now Site Report # Try out the Netcraft Toolbar!  FAQ i  S2 OS  Server Last changed IP address Netblock Owner I OpenVMS  OSU/3.7;Multinet  6-Mar-2002  192.135.80.34   Arnold Consulting,] Inc. l        > -----Original Message-----+ > From: John Smith [mailto:a@nonymous.com]  ' > Sent: Tuesday, March 01, 2005 8:38 AM. > To: Info-VAX@Mvb.Saic.Comh> > Subject: Re: Interesting error message I just got trying to  > access accuwea ther.coml > = > I don't believe I've ever seen a Netcraft entry that knows o? > about OpenVMS......either due to a paucity of sites actually y= > using VMS as their web server OS, or that Netcraft doesn't   > know what OpenVMS is.  >  >  >  > Stuart, Ed wrote:I: > > Interestingly enough, the accuweather servers are not  > reporting what e. > > OS they are running according to Netcraft. > >t5 > > OS  Server Last changed IP address Netblock Owner B > > unknown  OSU/3.9c;UCX  9-Nov-2003  207.242.93.24   Accuweather= > > unknown  unknown  8-Nov-2003  207.242.93.24   AccuweathergC > > unknown  OSU/3.9c;UCX  28-Mar-2002  207.242.93.24   AccuweatheriE > > unknown  OSU/3.8aw2;UCX  26-Feb-2002  207.242.93.24   AccuweathertC > > unknown  OSU/3.9c;UCX  25-Feb-2002  207.242.93.24   Accuweather E > > unknown  OSU/3.8aw2;UCX  24-Feb-2002  207.242.93.24   Accuweather C > > unknown  OSU/3.9c;UCX  22-Feb-2002  207.242.93.24   Accuweathere> > > Compaq Tru64  OSU/3.8aw2;UCX  6-Mar-2001  207.242.93.24   
 > Accuweatherl? > > Compaq Tru64  Microsoft-IIS/5.0  5-Mar-2001  207.242.93.24 L > Accuweather G > > Compaq Tru64  OSU/3.8aw2;UCX  3-Mar-2001  207.242.93.24 Accuweatherh > >t > >> -----Original Message-----h? > >> From: Kilgallen@SpamCop.net [mailto:Kilgallen@SpamCop.net]v, > >> Sent: Monday, February 28, 2005 4:55 PM > >> To: Info-VAX@Mvb.Saic.ComH > >> Subject: Re: Interesting error message I just got trying to access  > >> accuweather.com > >> > >> In articleOC > >> <1109606335.721844.142510@g14g2000cwa.googlegroups.com>, "Ken Y+ > >> Robinson" <kenrbnsn@rbnsn.com> writes:.C > >>> I just tried to access accuweather.com and got the following:. > >>>i< > >>> -ERROR-(500):  %SYSTEM-F-REMRSRC, insufficient system  > resources at a' > >>> remote node Requested method: GET  > >>> Requested URL:    //  > >>> HTTP protocol:    HTTP/1.1 > >>>e; > >>> Looks like someone's VMS box isn't configured well...- > >>F > >> Or a lot of people in the Northeast have heard about an oncoming - > >> storm but have not yet lost power to it.  >  > -- > / > OpenVMS - The classics never go out of style.S >  >    ------------------------------  # Date: Tue, 01 Mar 2005 17:59:42 GMTc! From: Nigel Barker <nigel@hp.com>nT Subject: Re: Interesting error message I just got trying to access accuwea	 ther.com8 Message-ID: <gc9921prcannc22umt48jrunb5c66f54a5@4ax.com>  K On Tue, 01 Mar 2005 11:19:08 -0500, JF Mezei <jfmezei.spamnot@teksavvy.com>k wrote:   >John Smith wrote: >> iC >> I don't believe I've ever seen a Netcraft entry that knows about L >> OpenVMS......either due to a paucity of sites actually using VMS as their@ >> web server OS, or that Netcraft doesn't know what OpenVMS is. >aF >Unfortunatly, the server ideintification doesn'T report "VMS" (or its  P Yes it does & has done for several years. For example I just checked the OpenVMSK home page h71000.www7.hp.com & Netcraft reports the OS as OpenVMS & the web / server as Apache/1.3.20 (OpenVMS) mod_perl/1.21   I See http://toolbar.netcraft.com/site_report?url=http://h71000.www7.hp.coml   -- Nigel Barker Live from the sunny Cote d'Azura   ------------------------------  $ Date: Tue, 1 Mar 2005 07:48:07 -0600/ From: "Stuart, Ed" <Ed.Stuart@austinenergy.com>KS Subject: RE: Interesting error message I just got trying to access accuwea	ther.comeT Message-ID: <DA4AD590CAF06845B671C398333A89C6082E2662@ohms.electric.ci.austin.tx.us>  H  Interestingly enough, the accuweather servers are not reporting what OS' they are running according to Netcraft.t  2 OS  Server Last changed IP address Netblock Owner A unknown  OSU/3.9c;UCX  9-Nov-2003  207.242.93.24   Accuweather   u< unknown  unknown  8-Nov-2003  207.242.93.24   Accuweather   B unknown  OSU/3.9c;UCX  28-Mar-2002  207.242.93.24   Accuweather   D unknown  OSU/3.8aw2;UCX  26-Feb-2002  207.242.93.24   Accuweather   B unknown  OSU/3.9c;UCX  25-Feb-2002  207.242.93.24   Accuweather   D unknown  OSU/3.8aw2;UCX  24-Feb-2002  207.242.93.24   Accuweather   B unknown  OSU/3.9c;UCX  22-Feb-2002  207.242.93.24   Accuweather   H Compaq Tru64  OSU/3.8aw2;UCX  6-Mar-2001  207.242.93.24   Accuweather   K Compaq Tru64  Microsoft-IIS/5.0  5-Mar-2001  207.242.93.24   Accuweather   iF Compaq Tru64  OSU/3.8aw2;UCX  3-Mar-2001  207.242.93.24   Accuweather    > -----Original Message-----= > From: Kilgallen@SpamCop.net [mailto:Kilgallen@SpamCop.net] /) > Sent: Monday, February 28, 2005 4:55 PM  > To: Info-VAX@Mvb.Saic.Comt> > Subject: Re: Interesting error message I just got trying to  > access accuweather.com > 
 > In article  @ > <1109606335.721844.142510@g14g2000cwa.googlegroups.com>, "Ken ( > Robinson" <kenrbnsn@rbnsn.com> writes:A > > I just tried to access accuweather.com and got the following:o > > G > > -ERROR-(500):  %SYSTEM-F-REMRSRC, insufficient system resources at m% > > remote node Requested method: GETc > > Requested URL:    /t > > HTTP protocol:    HTTP/1.1 > > 9 > > Looks like someone's VMS box isn't configured well...F > : > Or a lot of people in the Northeast have heard about an 3 > oncoming storm but have not yet lost power to it.m >    ------------------------------  $ Date: Tue, 1 Mar 2005 09:38:15 -0500# From: "John Smith" <a@nonymous.com>hS Subject: Re: Interesting error message I just got trying to access accuwea	ther.coml, Message-ID: <e_ydnRDdc89EHbnfRVn-sw@igs.net>  @ I don't believe I've ever seen a Netcraft entry that knows aboutI OpenVMS......either due to a paucity of sites actually using VMS as theirV= web server OS, or that Netcraft doesn't know what OpenVMS is.        Stuart, Ed wrote:eF > Interestingly enough, the accuweather servers are not reporting what, > OS they are running according to Netcraft. >t3 > OS  Server Last changed IP address Netblock OwnerF@ > unknown  OSU/3.9c;UCX  9-Nov-2003  207.242.93.24   Accuweather; > unknown  unknown  8-Nov-2003  207.242.93.24   AccuweatheraA > unknown  OSU/3.9c;UCX  28-Mar-2002  207.242.93.24   AccuweatheraC > unknown  OSU/3.8aw2;UCX  26-Feb-2002  207.242.93.24   Accuweather4A > unknown  OSU/3.9c;UCX  25-Feb-2002  207.242.93.24   AccuweatheriC > unknown  OSU/3.8aw2;UCX  24-Feb-2002  207.242.93.24   AccuweathereA > unknown  OSU/3.9c;UCX  22-Feb-2002  207.242.93.24   AccuweatheriG > Compaq Tru64  OSU/3.8aw2;UCX  6-Mar-2001  207.242.93.24   Accuweathere< > Compaq Tru64  Microsoft-IIS/5.0  5-Mar-2001  207.242.93.24E > Accuweather Compaq Tru64  OSU/3.8aw2;UCX  3-Mar-2001  207.242.93.24 
 > Accuweatherc >e >> -----Original Message-----t= >> From: Kilgallen@SpamCop.net [mailto:Kilgallen@SpamCop.net] * >> Sent: Monday, February 28, 2005 4:55 PM >> To: Info-VAX@Mvb.Saic.Com> >> Subject: Re: Interesting error message I just got trying to >> access accuweather.comn >>
 >> In articlea@ >> <1109606335.721844.142510@g14g2000cwa.googlegroups.com>, "Ken) >> Robinson" <kenrbnsn@rbnsn.com> writes:hA >>> I just tried to access accuweather.com and got the following:r >>>rF >>> -ERROR-(500):  %SYSTEM-F-REMRSRC, insufficient system resources at% >>> remote node Requested method: GETy >>> Requested URL:    /a >>> HTTP protocol:    HTTP/1.1 >>>c9 >>> Looks like someone's VMS box isn't configured well...a >>: >> Or a lot of people in the Northeast have heard about an4 >> oncoming storm but have not yet lost power to it.   --  - OpenVMS - The classics never go out of style.t   ------------------------------  * Date: Tue, 1 Mar 2005 16:33:12 +0000 (UTC) From: david20@alpha2.mdx.ac.ukS Subject: RE: Interesting error message I just got trying to access accuwea	ther.coma) Message-ID: <d025g8$dnu$1@news.mdx.ac.uk>e   In article <DA4AD590CAF06845B671C398333A89C6082E2662@ohms.electric.ci.austin.tx.us>, "Stuart, Ed" <Ed.Stuart@austinenergy.com> writes:I > Interestingly enough, the accuweather servers are not reporting what OS ( >they are running according to Netcraft. >.3 >OS  Server Last changed IP address Netblock Owner  B >unknown  OSU/3.9c;UCX  9-Nov-2003  207.242.93.24   Accuweather   = >unknown  unknown  8-Nov-2003  207.242.93.24   Accuweather   iC >unknown  OSU/3.9c;UCX  28-Mar-2002  207.242.93.24   Accuweather    E >unknown  OSU/3.8aw2;UCX  26-Feb-2002  207.242.93.24   Accuweather   aC >unknown  OSU/3.9c;UCX  25-Feb-2002  207.242.93.24   Accuweather   hE >unknown  OSU/3.8aw2;UCX  24-Feb-2002  207.242.93.24   Accuweather    C >unknown  OSU/3.9c;UCX  22-Feb-2002  207.242.93.24   Accuweather   iI >Compaq Tru64  OSU/3.8aw2;UCX  6-Mar-2001  207.242.93.24   Accuweather   nL >Compaq Tru64  Microsoft-IIS/5.0  5-Mar-2001  207.242.93.24   Accuweather   G >Compaq Tru64  OSU/3.8aw2;UCX  3-Mar-2001  207.242.93.24   Accuweather e >M    1 Well the earlier entries are interesting as well.e  + OSU running on Tru64 with UCX tcpip stack ?nI I think I recall you could build OSU for Tru64 but I didn't think anybodyw had really used it.s3 And what about running Microsoft-IIS/5.0  on Tru64.e    
 David Webb Security team leader CCSS Middlesex University           >> -----Original Message----- > >> From: Kilgallen@SpamCop.net [mailto:Kilgallen@SpamCop.net] * >> Sent: Monday, February 28, 2005 4:55 PM >> To: Info-VAX@Mvb.Saic.Com? >> Subject: Re: Interesting error message I just got trying to   >> access accuweather.comf >>   >> In article A >> <1109606335.721844.142510@g14g2000cwa.googlegroups.com>, "Ken  ) >> Robinson" <kenrbnsn@rbnsn.com> writes:sB >> > I just tried to access accuweather.com and got the following: >> >  H >> > -ERROR-(500):  %SYSTEM-F-REMRSRC, insufficient system resources at & >> > remote node Requested method: GET >> > Requested URL:    / >> > HTTP protocol:    HTTP/1.1w >> > e: >> > Looks like someone's VMS box isn't configured well... >> a; >> Or a lot of people in the Northeast have heard about an r4 >> oncoming storm but have not yet lost power to it. >> -   ------------------------------   Date: 01 Mar 2005 16:50:27 GMT+ From: "Doc." <doc.cypher@openvms-rocks.com>mS Subject: Re: Interesting error message I just got trying to access accuwea	ther.com 7 Message-ID: <Xns960CB5AE6A0D6dcovmsrox@212.100.160.126>t  G %NEWS-I-NEWMSG, John Smith wrote in news:e_ydnRDdc89EHbnfRVn-sw@igs.neto  B > I don't believe I've ever seen a Netcraft entry that knows aboutF > OpenVMS......either due to a paucity of sites actually using VMS as E > their web server OS, or that Netcraft doesn't know what OpenVMS is.s   They do if you run WASD.  ? http://uptime.netcraft.com/up/graph/?host=www.openvms-rocks.comR     Doc. -- eG OpenVMS:     Eight out of ten hackers prefer *other* operating systems.iG http://www.openvms-rocks.com    Deathrow Public-Access OpenVMS Cluster.u   ------------------------------  $ Date: Tue, 1 Mar 2005 11:55:17 -0500# From: "John Smith" <a@nonymous.com>,S Subject: Re: Interesting error message I just got trying to access accuwea	ther.comB, Message-ID: <ipGdnSkGhNjrA7nfRVn-2Q@igs.net>   Doc. wrote:t% > %NEWS-I-NEWMSG, John Smith wrote in % > news:e_ydnRDdc89EHbnfRVn-sw@igs.netu >eC >> I don't believe I've ever seen a Netcraft entry that knows aboutaF >> OpenVMS......either due to a paucity of sites actually using VMS asF >> their web server OS, or that Netcraft doesn't know what OpenVMS is. >t > They do if you run WASD. >uA > http://uptime.netcraft.com/up/graph/?host=www.openvms-rocks.com-     I stand corrected.   --B OpenVMS - The classics never go out of style..... they just aren't advertised.s   ------------------------------  * Date: Tue, 1 Mar 2005 17:10:00 +0000 (UTC) From: david20@alpha2.mdx.ac.ukS Subject: Re: Interesting error message I just got trying to access accuwea ther.coml) Message-ID: <d027l8$ejr$1@news.mdx.ac.uk>p  r In article <1109696478.8588e5226aa1bea8b419680b635b3b7b@teranews>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: >"Doc." wrote: >  >> They do if you run WASD.e >> dB >> http://uptime.netcraft.com/up/graph/?host=www.openvms-rocks.com >eI >In your case, the "openvms" string in included in the Server header. ButAE >for OSU, it isn't. Yet netcraft knows I am running VMS. So they musts/ >have a table of web servers and associated OS..  . They know that your running VMS if you run OSU   seep  : http://uptime.netcraft.com/up/graph/?host=alpha2.mdx.ac.uk    
 David Webb Security team leader CCSS Middlesex University   ------------------------------  $ Date: Tue, 1 Mar 2005 10:22:49 -0800% From: DeanW <dean.woodward@gmail.com>lS Subject: Re: Interesting error message I just got trying to access accuwea ther.coml6 Message-ID: <3f119ada050301102286fb50d@mail.gmail.com>  - On Tue, 1 Mar 2005 07:48:07 -0600, Stuart, Edb# <Ed.Stuart@austinenergy.com> wrote:uJ >  Interestingly enough, the accuweather servers are not reporting what OS) > they are running according to Netcraft.v > 3 > OS  Server Last changed IP address Netblock Owner @ > unknown  OSU/3.9c;UCX  9-Nov-2003  207.242.93.24   Accuweather; > unknown  unknown  8-Nov-2003  207.242.93.24   AccuweathereA > unknown  OSU/3.9c;UCX  28-Mar-2002  207.242.93.24   Accuweather C > unknown  OSU/3.8aw2;UCX  26-Feb-2002  207.242.93.24   AccuweatheraA > unknown  OSU/3.9c;UCX  25-Feb-2002  207.242.93.24   Accuweather C > unknown  OSU/3.8aw2;UCX  24-Feb-2002  207.242.93.24   Accuweather)A > unknown  OSU/3.9c;UCX  22-Feb-2002  207.242.93.24   AccuweatherlG > Compaq Tru64  OSU/3.8aw2;UCX  6-Mar-2001  207.242.93.24   AccuweathernJ > Compaq Tru64  Microsoft-IIS/5.0  5-Mar-2001  207.242.93.24   AccuweatherG > Compaq Tru64  OSU/3.8aw2;UCX  3-Mar-2001  207.242.93.24   Accuweathers  E Hey- IIS running on Tru64. Nice. NetCraft thinks my WASD installationT is running on NT4 or Win98...s   ------------------------------  % Date: Tue, 01 Mar 2005 11:19:08 -0500.- From: JF Mezei <jfmezei.spamnot@teksavvy.com>.Y Subject: Re: Interesting error message I just got trying to access accuwea ther.com ther.]B Message-ID: <1109693201.15a48b686ae648fb5bcb68ab1961b9c0@teranews>   John Smith wrote:  > B > I don't believe I've ever seen a Netcraft entry that knows aboutK > OpenVMS......either due to a paucity of sites actually using VMS as their(? > web server OS, or that Netcraft doesn't know what OpenVMS is..  E Unfortunatly, the server ideintification doesn'T report "VMS" (or itso open variation). .  H Note that in manu cases, you only see "Apache" and not any indication ofD the underlyting OS either. Netcraft may have been more useful in the/ past when Server: strings were more meaningful.o  D The only one where you know the OS is when you see sites served with! IIS, you know it runs on Widnows.    ------------------------------  % Date: Tue, 01 Mar 2005 12:13:46 -0500-- From: JF Mezei <jfmezei.spamnot@teksavvy.com> Y Subject: Re: Interesting error message I just got trying to access accuwea ther.com ther.tB Message-ID: <1109696478.8588e5226aa1bea8b419680b635b3b7b@teranews>  
 "Doc." wrote:   l > They do if you run WASD. > A > http://uptime.netcraft.com/up/graph/?host=www.openvms-rocks.como  H In your case, the "openvms" string in included in the Server header. ButD for OSU, it isn't. Yet netcraft knows I am running VMS. So they must. have a table of web servers and associated OS.   ------------------------------    Date: 28 Feb 2005 22:47:48 -0800 From: icerq4a@spray.se/ Subject: Re: new Itanium after Tukwila: PoulsonGC Message-ID: <1109659668.323757.258880@l41g2000cwc.googlegroups.com>.   JF Mezei wrote:g > icerq4a@spray.se wrote:w > >M3 > > http://news.zdnet.com/2100-9584_22-5593047.html- >cG > Intel would have been much better off announcing this last year whichfF > would have help counter all the bad news that gave much steam to the) > rumours that IA64 wasn't going to last.   ) I think Tukwila was sufficient last year."  C > It will be interesting to see how many details Intel will releasey today.G > IA64 is still one generation behind (Power has had dual core for some- > time).  / Yes, being late on dual-core has not been good.o  B > But that still doesn't give much trust in IA64's future. EV8 was# > announced but never materialised.s  G You have in the past said that there was nothing beyond 2007, now therepF is, but as expected there is always a negative side on everything from
 your side.   ------------------------------  % Date: Tue, 01 Mar 2005 12:42:50 -0500M( From: Bill Todd <billtodd@metrocast.net>/ Subject: Re: new Itanium after Tukwila: Poulsoni= Message-ID: <TZudnZXOeIYBNLnfRVn-3Q@metrocastcablevision.com>M   icerq4a@spray.se wrote:- > JF Mezei wrote:s >  >>icerq4a@spray.se wrote:r >>2 >>>http://news.zdnet.com/2100-9584_22-5593047.html >>G >>Intel would have been much better off announcing this last year which F >>would have help counter all the bad news that gave much steam to the) >>rumours that IA64 wasn't going to last.- >  > + > I think Tukwila was sufficient last year.E  A I tend to agree.  But the suggestion that this is no longer true  I reflects more than the simple passage of time (though that's significant fH as well):  it reflects the fact that Tukwila changed from being a major I core-design upgrade to yet another ho-hum re-spin (Montecito itself is a E7 re-spin, but at least a somewhat more interesting one).,  I McKinley's basic core design now looks like all Itanic will have through EI at least 2008 (the recent Tukwila change makes its 2007 target date much -D more of a challenge - they reportedly haven't firmly settled on the C final design yet - and even if Poulson leverages some of the Alpha :D team's core work expecting product before 2009 would be, let's say, H optimistic), which is starting to challenge EV6's longevity but without G the excuse that the Alpha architecture was abandoned less than 3 years d? after EV6 debuted.  And unlike EV6, the McKinley core wasn't a h world-beater at introduction.    >  > C >>It will be interesting to see how many details Intel will releaseo >  > today. > G >>IA64 is still one generation behind (Power has had dual core for somen >>time). >  > 1 > Yes, being late on dual-core has not been good.m  E Intel could have had dual-core Itanics any time it wanted them.  But l@ Itanic's appetite for on-chip cache is such that their per-core G performance would have been even less impressive than it has been, and cG the decision to axe the Alpha Tukwila makes is clear that (just as was CE the case with MHz until recently) Intel places a premium on per-core >I performance even in server products which might well be better-served by o$ more emphasis on overall throughput.  E EV8, of course, had the best of both worlds:  4-way fine-grained SMT nB plus lots of execution units for throughput parallelism, plus the B single-threaded dominance which a single-core chip makes possible F (though even it would have gone to multiple cores over time:  it just C didn't have comfortable room to do so at the planned 130 nm. debut aF size).  It will be interesting to see whether POWER6 goes that route: E POWER5 already has fine-grained SMT, but only 2-way and IIRC without u extra execution units.   >  > B >>But that still doesn't give much trust in IA64's future. EV8 was# >>announced but never materialised.l >  > I > You have in the past said that there was nothing beyond 2007, now therekH > is, but as expected there is always a negative side on everything from > your side.  G It's just so hard to avoid, given the amount of ammunition that Itanic ,F and its backers provide to us:  if we didn't use it, the accumulating  pile might explode.1  D For example, even the article you originally cite doesn't have much G that's good to say about Itanic's market penetration, both in absolute O/ numbers and in its failure to meet projections.   I  From the original three-pronged design strategy (Madison was originally >D a third new core design rather than a re-spin of McKinley, and soon H after that design got scrapped the significant revamp for Montecito was G launched), plus the addition of not one but two Alpha teams to the mix  I starting in mid-2001, Intel has fallen back to a single core design plus  F whatever Poulson may be (rather distantly in the future) and canceled E chipset plans (Bayshore) that would have given Itanic a boost before iF (the now-further-delayed) Tukwila arrives.  The mighty Itanic may not C yet be on the ocean floor, but it's taken on rather a lot of water oH recently - and the observation that Poulson/Itanic could enjoy the same C fate as Alpha/EV8 should Intel get tired of bailing is an entirely eG appropriate warning as long as it's couched as such rather than as any c kind of certainty.   - bill   ------------------------------   Date: 1 Mar 2005 01:14:47 -0800. From: mb301@hotmail.com (MB) Subject: NTP and timezones< Message-ID: <1d08b916.0503010114.4a5764b@posting.google.com>  ) Have read the posting about ntp problems.r   http://groups.google.co.uk/groups?hl=en&lr=&threadm=1109187909.564158.73630%40z14g2000cwz.googlegroups.com&prev=/groups%3Fnum%3D25%26hl%3Den%26lr%3D%26group%3Dcomp.os.vms%26start%3D500  5 Is is possible to use NTP across different timezones?R   Node'A' (London)  GMT  Node'B' (London)  GMTD* Node'C' (Atlanta, Georgia) GMT -5Hrs (EST)  F Node'B' keeps time with Node'A' and is in the same timezone (GMT) - no problems  D I need to get Node'C' to be -5Hrs Node'A', and not just synchronize  the time like Node'B' and Node'A'.u    Does NTP obey the timezone rule?   Node'A'p   "SYS$TIMEZONE_NAME" = "GMT" 6   "SYS$TIMEZONE_RULE" = "GMT0BST-1,M3.5.0/1,M10.5.0/1" Node'C'm   "SYS$TIMEZONE_NAME" = "EST" 5   "SYS$TIMEZONE_RULE" = "EST5EDT4,M4.1.0/2,M10.5.0/2"h   ------------------------------  % Date: Tue, 01 Mar 2005 07:03:07 -0500V6 From: Brad Hamilton <brMadAhaPmiSlton@coMmcAasPt.Snet> Subject: Re: NTP and timezones0 Message-ID: <veWdnSw85OFhxLnfRVn-sA@comcast.com>  	 MB wrote:j+ > Have read the posting about ntp problems.s >  > http://groups.google.co.uk/groups?hl=en&lr=&threadm=1109187909.564158.73630%40z14g2000cwz.googlegroups.com&prev=/groups%3Fnum%3D25%26hl%3Den%26lr%3D%26group%3Dcomp.os.vms%26start%3D50n > 7 > Is is possible to use NTP across different timezones?r >  > Node'A' (London)  GMT  > Node'B' (London)  GMTh, > Node'C' (Atlanta, Georgia) GMT -5Hrs (EST) > H > Node'B' keeps time with Node'A' and is in the same timezone (GMT) - no
 > problems > F > I need to get Node'C' to be -5Hrs Node'A', and not just synchronize 
 > the time > like Node'B' and Node'A'.n  E In a similar situation, I made sure that "Node'C'" synchronized to a -D timeserver that was geographically "local" (in the Atlanta, Georgia  area, to use your example).e  " > Does NTP obey the timezone rule?  A Yes.  I had a situation where I had three servers located in the gF Northeastern U.S., each of which served customers in a different time H zone.  All servers synchronized to the same set of "local" timeservers, I and the timezone rules on each Alpha Server "translated" the time to the rI "proper" time zone (the "Central" Alpha Server had a TZ rule for Central .' time, Mountain for Mountain time, etc.)n  E There is also a product from Software Partners available, which will  ? allow one to "serve" multiple time zones from the same VMS box.p   <snip>   ------------------------------  * Date: Tue, 1 Mar 2005 12:06:30 +0000 (UTC) From: david20@alpha1.mdx.ac.uk Subject: Re: NTP and timezones) Message-ID: <d01ls6$8rf$1@news.mdx.ac.uk>m  [ In article <1d08b916.0503010114.4a5764b@posting.google.com>, mb301@hotmail.com (MB) writes:o* >Have read the posting about ntp problems. >d >http://groups.google.co.uk/groups?hl=en&lr=&threadm=1109187909.564158.73630%40z14g2000cwz.googlegroups.com&prev=/groups%3Fnum%3D25%26hl%3Den%26lr%3D%26group%3Dcomp.os.vms%26start%3D50 >e6 >Is is possible to use NTP across different timezones? >  >Node'A' (London)  GMT c >Node'B' (London)  GMT+ >Node'C' (Atlanta, Georgia) GMT -5Hrs (EST)  >nG >Node'B' keeps time with Node'A' and is in the same timezone (GMT) - nor	 >problems. > E >I need to get Node'C' to be -5Hrs Node'A', and not just synchronize y	 >the time  >like Node'B' and Node'A'. >e! >Does NTP obey the timezone rule?1 >6 >Node'A' >  "SYS$TIMEZONE_NAME" = "GMT"7 >  "SYS$TIMEZONE_RULE" = "GMT0BST-1,M3.5.0/1,M10.5.0/1"n >Node'C' >  "SYS$TIMEZONE_NAME" = "EST"6 >  "SYS$TIMEZONE_RULE" = "EST5EDT4,M4.1.0/2,M10.5.0/2"    L NTP works in UTC (ie GMT) - it is up to the individual system to then apply 4 it's own timezone rules to the NTP time it receives.  N So as long as the timezone rules are set correctly then everything should just work.a  
 David Webb Securiy team leaderu CCSS Middlesex University   ------------------------------  % Date: Wed, 02 Mar 2005 01:03:01 +0800l From: prep@prep.synonet.commA Subject: Re: OpenVMS Seminar in Toronto (2005-02-24) a few points-- Message-ID: <87vf8bpad6.fsf@prep.synonet.com>   7 rdeininger@mindspringdot.com (Robert Deininger) writes:   G > In article <1109564155.365a38142e9cca1b572b7c75bacb949f@teranews>, JF - > Mezei <jfmezei.spamnot@teksavvy.com> wrote:   / >>One more thing about the environmental issue:s  B >>EV7 came out last year, the Galaxy-class machines to support EV7C >>came out last year. Not a decade ago, not 5 years ago. Last year.   E > But the design work was started much earlier.  There were prototypesF > systems in 2001.  Once you start building protos, wholesale churning@ > of the BOM would be very bad.  It would be like starting over.  & That is several years AFTER Superdome.   -- :< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              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: 1 Mar 2005 07:13:46 -0600h; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)e( Subject: Re: Ouch! a *MAJOR* bug in TPU.3 Message-ID: <dzNbPEm29yhM@eisner.encompasserve.org>y  ` In article <4223D791.F594434A@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes: > D > How 'bout expecting the cursor to be found where no data currently > exists? That *IS* corruption!   9    There's a reason why the cursor appears on the screen.-  C    Meanwhile I suspect you've never used Columbia's SED, it was thet>    best we could get on TOPS-20 until DEC finally gave us EDT.   ------------------------------   Date: 1 Mar 2005 00:35:59 -0800-- From: pfleging.lka@ekkw.de (pfleging.michael)w/ Subject: Re: Problem with a DEC terminal serverh= Message-ID: <b8cd107b.0503010035.4458307c@posting.google.com>4  K If you have VMS, you can reprogram your Terminalserver via Console Connect:s# example, from documentation of NCP:r   $ MC NCP  8 NCP>CONNECT VIA UNA-0 PHYSICAL ADDRESS 08-00-2B-22-45-CD  @ replace UNA-0 with your Network device (NCP>SHOW KNOWN CIRCUITS)A and 08-00-2B-22-45-CD with the MAC Address of your DECserver 90L+   E you will get a session (port 9) on your Terminal Server, then you can < see and reprogram the port settings according to your manual   drwho8__NOTME__@att.net (The Eighth Doctor) wrote in message news:<BZaUd.81854$Th1.81032@bgtnsc04-news.ops.worldnet.att.net>...e > Hello from Gregg C LevineeM > I have here a DECserver 90L+. According to the manual which I have here, I eT > connected a PC to one of its ports, using a temporary plug. Then set the terminal Y > software to a default of 9600,8,n,1. (Which I suspect isn't the correct settings.) And  W > then when I turned the T/S on, and pressed enter, twice, instead of getting a prompt -T > sequence, I got garbage. Does anyone know the correct way to do a "factory reset"  > for the thing? > -----r! > Gregg drwho8 atsign att dot net-! > "This signature isn't at home."F   ------------------------------  % Date: Tue, 01 Mar 2005 04:02:20 -0500y' From: Dave Froble <davef@tsoft-inc.com>M/ Subject: Re: Problem with a DEC terminal serverh0 Message-ID: <1128bc3b6cs6n5c@corp.supernews.com>   The Eighth Doctor wrote:N > In article <38dtvkF5lrqecU1@individual.net>, hvlems.dotweg@zonnet.nl says... >  >>B >>"The Eighth Doctor" <drwho8__NOTME__@att.net> schreef in berichtB >>news:BZaUd.81854$Th1.81032@bgtnsc04-news.ops.worldnet.att.net... >> >>>Hello from Gregg C LevineM >>>I have here a DECserver 90L+. According to the manual which I have here, IeK >>>connected a PC to one of its ports, using a temporary plug. Then set the  >>
 >>terminal >>J >>>software to a default of 9600,8,n,1. (Which I suspect isn't the correct >> >>settings.) And >>F >>>then when I turned the T/S on, and pressed enter, twice, instead of >> >>getting a prompt >>M >>>sequence, I got garbage. Does anyone know the correct way to do a "factory  >> >>reset" >> >>>for the thing?c >>>-----" >>>Gregg drwho8 atsign att dot net" >>>"This signature isn't at home." >>>1 >>/ >>What happens if you use 9600,7,n,1 on the PC?u >> >>Hans >> >> > & > Hello (again) from the Eighth DoctorY > Well that setting did not work. Nor did further fiddling either. I finally realized it gP > might be my makeshift cable. A fellow I know through the NetBSD Port-VAX list R > sent me a pair of cables, and four DB25 connectors, one pair male, and one pair  > female. It worked. > U > Now all I need to find is that frame that the company described as a backplane for  : > them, with a 10BASE-T connector for that style network.   H If you're refering to the DEChub90, then the next question is where are  you located?   > Thanks guys. > ------! > Gregg drwho8 atsign att dot neteT > "This signature is a fan of the Marx brothers, and Abbot and Costello. Because he  > can."  >    ------------------------------   Date: 1 Mar 2005 04:01:53 -0800d% From: Bart.Zorn@xs4all.nl (Bart Zorn) / Subject: Re: Problem with a DEC terminal server = Message-ID: <a98cd882.0503010401.47676876@posting.google.com>i   drwho8__NOTME__@att.net (The Eighth Doctor) wrote in message news:<MvTUd.302609$w62.267287@bgtnsc05-news.ops.worldnet.att.net>...tN > In article <38dtvkF5lrqecU1@individual.net>, hvlems.dotweg@zonnet.nl says... >d    [ S n i p . . . ] > U > Now all I need to find is that frame that the company described as a backplane for  : > them, with a 10BASE-T connector for that style network.  >  > Thanks guys. > ------! > Gregg drwho8 atsign att dot netoT > "This signature is a fan of the Marx brothers, and Abbot and Costello. Because he  > can."w  E I am afraid that you will not find anything with a 10BASE-T connector B that can be connected to the 90L+. The DEChub90 backplane only has9 10BASE-2, and the DETMR has no network connection at all.   F The DECserver 90M is the only one in the -90 series that has 10BASE-T.   Regards,  	 Bart Zorna   ------------------------------  $ Date: Tue, 1 Mar 2005 09:53:49 -0500# From: "John Smith" <a@nonymous.com>  Subject: Re: Sayonara Tukwilla, Message-ID: <XsednQTV-6BhHLnfRVn-rA@igs.net>   Bill Todd wrote: > Rick Jones wrote:l, >> Bill Todd <billtodd@metrocast.net> wrote: >>8 >>> Are zx1s considered part of the Integrity line now?) >> >>G >> Yes. For some time now.  My dimm memory cannot recall if the initialeE >> zx1-based server systems (IIRC rx2600, rx5670 at 900 MHz and 1GHz)-@ >> shipped before the Integrity naming convention or not though. >(B > I kind of thought that the 'Integrity' moniker appeared when theH > 8-processor-and-up models did (i.e., well after zx1), but my dimms are > dim as well on that point.    D I thought "Integrity" first appeared when everyone began questioning carly(tm)'s.  ;-)3 --  - OpenVMS - The classics never go out of style.n   ------------------------------  # Date: Tue, 01 Mar 2005 18:54:22 GMTt& From: Rick Jones <foo@bar.baz.invalid> Subject: Re: Sayonara Tukwilla0 Message-ID: <yT2Vd.783$I%3.644@news.cpqcorp.net>  3 David J Dachtera <djesys.nospam@comcast.net> wrote:: > Rick Jones wrote:s, >> Bill Todd <billtodd@metrocast.net> wrote:9 >> > Are zx1s considered part of the Integrity line now?)@ >> eG >> Yes. For some time now.  My dimm memory cannot recall if the initial,E >> zx1-based server systems (IIRC rx2600, rx5670 at 900 MHz and 1GHz) @ >> shipped before the Integrity naming convention or not though.  % > Can your simm memory recall it? ;-)n  F Unclear - over time, my simm memory has been relegated to holding whatF I'll call "instinctive memories" somewhere deep within the brainstem IE suspect :) I'm not quite old enough to have instinctive memories held  in core :) :) :)  
 rick jones --  D The glass is neither half-empty nor half-full. The glass has a leak.) The real question is "Can it be patched?"AF these opinions are mine, all mine; HP might not want them anyway... :)A feel free to post, OR email to raj in cup.hp.com  but NOT BOTH...    ------------------------------  $ Date: Tue, 1 Mar 2005 19:23:13 +11006 From: "O'Brien Paddy" <Paddy.O'Brien@transgrid.com.au>: Subject: RE: This is the End... My Only Friend, The End...X Message-ID: <8BAD914A0B8CA84C9E94187103A1AB9E05BE01@EX-TG2-PR.corporate.transgrid.local>  , This is a multi-part message in MIME format.  ' ------_=_NextPart_001_01C51E37.E93660D0 . Content-Type: text/plain; charset="iso-8859-1"+ Content-Transfer-Encoding: quoted-printablev  L I apologise to anyone when I try to "reply" to an info-vax message if they =L get a personal copy.  I am now having to go through "Outlook Web Access", s=L ince an upgrade to the exchange server has lost me access via Mozilla, over=L  which I had a small amount of control.  This BG stuff is absolutely the bi=L ggest cr*p on this planet -- in this universe (there *might* be life on Mar=) s, or on Titan, we are now being told :-)2  L I seem to have lost all control over this beast, and just wish I knew a way=L  to connect via this stupid upgrade via Mozilla to Outhouse from my VMS box.  L I'm having to add the chevrons myself, so apologies if I get attritions wro= ng now or in the future.   -----Original Message-----/ From: Bill Todd [mailto:billtodd@metrocast.net]n Sent: Tue 3/1/2005 4:22 PM To: Info-VAX@Mvb.Saic.Com5: Subject: Re: This is the End... My Only Friend, The End... =20n [snips]e  J >And the article you quote above notes that the layoffs are being 'offset=J  >by new hires', rather than transferring those who jobs are disappearing=K  >to others (as more reputable companies tend to make at least some effort=w	  >to do).a  L There was an article on The Register a few weeks ago, URL lost, where the U=L K Government was doing something like increasing retiring age for civil ser=L vants, but making them redundant to hire younger people.  I think the gist = is as I remember.b  G >It's a shame, and a travesty, to see someone who joined DEC about 6=20tJ >months before I did being given the heave-ho like that after nearly 30=20J >years.  But pretty much the kind of thing I've come to expect from VMS's=  >owner.   >- bill-  L It is also a travesty that lesser mortals are evicted with a small package =L after that length of time and with excellent service records, where high fl=L iers with small time and abysmal records (short term failurs) are given mas=L sive golden parachutes.  Not just HP/Compaq/DEC, but many others are record= ed here as well as US and UK.i   Regards, Paddy    G ***********************************************************************d  C "This electronic message and any attachments may contain privileged @ and confidential information intended only for the use of the=20D addressees named above.  If you are not the intended recipient of=20C this email, please delete the message and any attachment and adviseSD the sender.  You are hereby notified that any use, dissemination,=207 distribution, reproduction of this email is prohibited.   C If you have received the email in error, please notify TransGrid=20hC immediately.  Any views expressed in this email are those of the=20-? individual sender except where the sender expressly and with=20 C authority states them to be the views of TransGrid.  TransGrid usess> virus-scanning software but excludes any liability for viruses contained in any attachment.  < Please note the email address for TransGrid personnel is now$ firstname.lastname@transgrid.com.au"  G ***********************************************************************     ' ------_=_NextPart_001_01C51E37.E93660D0w- Content-Type: text/html; charset="iso-8859-1"2+ Content-Transfer-Encoding: quoted-printable-  1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">U <HTML> <HEAD>L <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-= 1">4K <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7226.0"> @ <TITLE>RE: This is the End... My Only Friend, The End...</TITLE> </HEAD>e <BODY>) <!-- Converted from text/plain format -->4  L <P><FONT SIZE=3D2>I apologise to anyone when I try to &quot;reply&quot; to =L an info-vax message if they get a personal copy.&nbsp; I am now having to g=L o through &quot;Outlook Web Access&quot;, since an upgrade to the exchange =L server has lost me access via Mozilla, over which I had a small amount of c=L ontrol.&nbsp; This BG stuff is absolutely the biggest cr*p on this planet -=L - in this universe (there *might* be life on Mars, or on Titan, we are now = being told :-)<BR> <BR>L I seem to have lost all control over this beast, and just wish I knew a way=L  to connect via this stupid upgrade via Mozilla to Outhouse from my VMS box= <BR> <BR>L I'm having to add the chevrons myself, so apologies if I get attritions wro= ng now or in the future.<BR> <BR> -----Original Message-----<BR>L From: Bill Todd [<A HREF=3D"mailto:billtodd@metrocast.net">mailto:billtodd@= metrocast.net</A>]<BR> Sent: Tue 3/1/2005 4:22 PM<BR> To: Info-VAX@Mvb.Saic.Com<BR>i> Subject: Re: This is the End... My Only Friend, The End...<BR> <BR> [snips]<BR>t <BR>L &gt;And the article you quote above notes that the layoffs are being 'offse= t<BR> L &gt;by new hires', rather than transferring those who jobs are disappearing= <BR>L &gt;to others (as more reputable companies tend to make at least some effor= t<BR>o &gt;to do).<BR>e <BR>L There was an article on The Register a few weeks ago, URL lost, where the U=L K Government was doing something like increasing retiring age for civil ser=L vants, but making them redundant to hire younger people.&nbsp; I think the = gist is as I remember.<BR> <BR>K &gt;It's a shame, and a travesty, to see someone who joined DEC about 6<BR>hL &gt;months before I did being given the heave-ho like that after nearly 30<= BR>4L &gt;years.&nbsp; But pretty much the kind of thing I've come to expect from=
  VMS's<BR> &gt;owner.<BR> <BR> &gt;- bill<BR> <BR>L It is also a travesty that lesser mortals are evicted with a small package =L after that length of time and with excellent service records, where high fl=L iers with small time and abysmal records (short term failurs) are given mas=L sive golden parachutes.&nbsp; Not just HP/Compaq/DEC, but many others are r=& ecorded here as well as US and UK.<BR> <BR> Regards, Paddy<BR> </FONT>- </P>   <FONT SIZE=3D3><BR>9 <BR>K ***********************************************************************<BR>u <BR>G "This electronic message and any attachments may contain privileged<BR>aB and confidential information intended only for the use of the <BR>F addressees named above.  If you are not the intended recipient of <BR>G this email, please delete the message and any attachment and advise<BR>aF the sender.  You are hereby notified that any use, dissemination, <BR>; distribution, reproduction of this email is prohibited.<BR>c <BR>E If you have received the email in error, please notify TransGrid <BR>ME immediately.  Any views expressed in this email are those of the <BR> A individual sender except where the sender expressly and with <BR>1G authority states them to be the views of TransGrid.  TransGrid uses<BR> B virus-scanning software but excludes any liability for viruses<BR>  contained in any attachment.<BR> <BR>@ Please note the email address for TransGrid personnel is now<BR>( firstname.lastname@transgrid.com.au"<BR> <BR>K ***********************************************************************<BR>r </FONT>r </BODY>e </HTML>o) ------_=_NextPart_001_01C51E37.E93660D0--g   ------------------------------  # Date: Tue, 01 Mar 2005 10:13:20 GMT3" From:   VAXman-  @SendSpamHere.ORG: Subject: Re: This is the End... My Only Friend, The End...0 Message-ID: <00A401A5.D915D183@SendSpamHere.ORG>  ` In article <4223E464.ABD59687@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes: >Ken Randell wrote:k >> rJ >> Some 'rumors' were very specific -- xx folks per quarter for the next n >> quarters. >> vN >> However, Sue did say on one of her mailing list things that previous rumorsN >> (in the Inquirer?) were false and if anything major was going to happen she >> would let us know.u >> nL >> I'd be interested in knowing actual employment levels for the past and inL >> the future for VMS engineering, but I don't expect I'll actually get that >> kind of information.. > E >Well, even Sue has to protect her career. Then again, show me anyone.  >with 100% job security anymore.  3 Save for perhaps mortician, there is no such beast.e   --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COMM            e5   "Well my son, life is like a beanstalk, isn't it?" n   ------------------------------   Date: 1 Mar 2005 05:51:01 -0800O! From: kenneth.randell@verizon.netb: Subject: Re: This is the End... My Only Friend, The End...C Message-ID: <1109685061.949651.219700@z14g2000cwz.googlegroups.com>d   Bill Todd wrote: > A > Perhaps more to the point, HP doesn't seem to value experienced[ peopleC > nearly as much as saving a few bucks (which sounds like Carly all> over:fC >   millions in cuts, not one red cent for investment).  In fact, Ig7 > believe some people were gathering up material for anr age-discriminationD > class-action suit a couple of years ago alleging that HP's layoffs had anB > distinct bias toward people nearing retirement but not quite yet) > eligible for early-retirement benefits.5 >:   Don't know about this one.  B > And the article you quote above notes that the layoffs are being 'offsetd< > by new hires', rather than transferring those who jobs are disappearingC > to others (as more reputable companies tend to make at least somet effort	 > to do).e >   4 Such 'new hires' are quite likely overseas in India.  E > It's a shame, and a travesty, to see someone who joined DEC about 65E > months before I did being given the heave-ho like that after nearlyt 30D > years.  But pretty much the kind of thing I've come to expect from VMS's  > owner. >A  G I'd like to know at what level such decisions are made.  It seems to meeG that you can only shave yourself so much before you cut yourself badly.r   ------------------------------  $ Date: Tue, 1 Mar 2005 09:40:18 -0500# From: "John Smith" <a@nonymous.com> : Subject: Re: This is the End... My Only Friend, The End..., Message-ID: <e_ydnRPdc89HHbnfRVn-sw@igs.net>   The new hires are in India.p       Bill Todd wrote: > John Smith wrote:  >> Tom Linden wrote: >>C >>> On Mon, 28 Feb 2005 16:20:00 -0500, John Smith <a@nonymous.com>e
 >>> wrote: >>>e >>>e >>>> Didier MORANDI wrote: >>>> >>>>> Hi Pals, >>>>> G >>>>> I got two days ago a phone call from a friend from SW EngineeringjF >>>>> in the U.S. He spent 29 years and six months at DEC/CPQ/HP (PDP,B >>>>> VAX, Alpha, Itanium). He terminated his current project lastE >>>>> week, then was called by his manager. The manager said (more orsG >>>>> less) "good job, now, I'm sorry but "Business has changed" (sic).nF >>>>> You may leave the Company. Good bye, good luck and thank you for >>>>> all the coding". >>>>> D >>>>> I do not think that a Company can fire people from EngineeringC >>>>> with such skills if the Product is not going to be phased outn >>>>> soon.- >>>> >>>>G >>>> There were many rumors going around that VMS Engineering was goingy >>>> to have5 >>>> significant layoffs once 8.2 / 8.3 was released.  >>>>F >>>> Your friend, was he involved in VMS exclusively? What's your ideaF >>>> of the head count in VMS Engineering prior to January 1, 2005 and	 >>>> now?g >>> C >>> That is curious, in light of the 2003 and 2004 results that VMSb >>> turned in. >> >>< >> http://www.openvms.org/stories.php?story=04/11/23/7489183 >> >>E >> Perhaps mostly Tru64, but carly(tm) style boat burning behind them/$ >> still seems to be in vogue at HP. > H > Perhaps more to the point, HP doesn't seem to value experienced peopleC > nearly as much as saving a few bucks (which sounds like Carly allsG >   over: millions in cuts, not one red cent for investment).  In fact,u > In7 > believe some people were gathering up material for ancE > age-discrimination class-action suit a couple of years ago allegingr= > that HP's layoffs had a distinct bias toward people nearing F > retirement but not quite yet eligible for early-retirement benefits. >mB > And the article you quote above notes that the layoffs are beingD > 'offset by new hires', rather than transferring those who jobs areE > disappearing to others (as more reputable companies tend to make ats > least some effort to do).t >sE > It's a shame, and a travesty, to see someone who joined DEC about 6yH > months before I did being given the heave-ho like that after nearly 30D > years.  But pretty much the kind of thing I've come to expect from > VMS's owner. >  > - bill   --  - OpenVMS - The classics never go out of style.n   ------------------------------  $ Date: Tue, 1 Mar 2005 09:48:57 -0500# From: "John Smith" <a@nonymous.com>3: Subject: Re: This is the End... My Only Friend, The End..., Message-ID: <e_ydnRLdc89HHbnfRVn-sw@igs.net>   Thomas Wirt wrote:" > VAXman- @SendSpamHere.ORG wrote: > E >> In article <1109628331.135314.66430@g14g2000cwa.googlegroups.com>,4 >> bob@instantwhip.com writes: >>6 >>> the product will not be temrinated but sold unless/ >>> HP wants a lot of angry vms users out therep2 >>> including the govt and corporations that would- >>> never purchase another HP branded productc6 >>> again ... talk about corporate suicide, that would; >>> be it ... they would have to really stupid to try that!u >> >> >> Stupidity is ubiquitous!  >>/ >> Sit back and take notes as it's inescapable.: >> >>G > First of all I am not going to assume the worst from what may well beeD > a very bad sign.  Second of all I agree with Bob that they can notE > kill VMS out right.  If they wanted to get rid of it they must sell F > it and do so in a way that looks like a good faith effort to keep itB > alive (to satisfy the DoD guarantees that they made).  Only then > could they even sell it.    J They don't have to enhance it, they only have to bug-fix for bugs existingH in the the products they contracted/guaranteed the DoD they'd deal with.  I Notice I didn't use the word 'promise', because we all know what a solemneJ promise is from HP - not worth the paper it's written on. Also note that I: mean the corporation, not VMS engineering when I say this.    G > If they did do this in an effort to kill it, they might find that the G > new owner actually made money with VMS and continued to keep it statej$ > of the art in the ways that it is.  J It would make HP look like a bunch of rank amateurs if they sold it off toL somebody who actually expanded its marketshare. Hence, it won't be sold off.  F > I would prefer that they not layoff the few engineers that are left,> > but for now I remain hopeful that they are keeping the right > engineers.  G I hate to say this, and I know the PC (politically correct) police willtK stomp on me for saying it, but this sort of acceptance of the status quo is-L exactly what HP is counting on. It's the "we'd best be thankful for what fewL crumbs we have left - can't be seen or heard twisting the dragon's tail", asK opposed to standing up to HP and saying "Quit fucking with us - your paying  customers".p   --- OpenVMS - The classics never go out of style.n   ------------------------------  % Date: Tue, 01 Mar 2005 10:02:41 -0500l6 From: Brad Hamilton <brMadAhaPmiSlton@coMmcAasPt.Snet>: Subject: Re: This is the End... My Only Friend, The End...0 Message-ID: <7sKdnedb5IuOGbnfRVn-1Q@comcast.com>   John Smith wrote:e   <snip>I > I hate to say this, and I know the PC (politically correct) police will M > stomp on me for saying it, but this sort of acceptance of the status quo issN > exactly what HP is counting on. It's the "we'd best be thankful for what fewN > crumbs we have left - can't be seen or heard twisting the dragon's tail", asM > opposed to standing up to HP and saying "Quit fucking with us - your paying 
 > customers".n  H I imagine a number of (former) customers have done so already, yet HP's F presumed attitude of "benign neglect" remains.  Bottom line remains - I standing up for yourself may feel good, but doesn't change the situation.N  G If - as some here suspect - HP is attempting to abandon the enterprise iI computing market, then they will adopt a "take it or leave it" attitude, -I and probably be glad to be rid of the "overhead" involved in maintaining g0 a customer base it no longer desires to possess.   ------------------------------  % Date: Tue, 01 Mar 2005 07:21:02 -0800i# From: "Tom Linden" <tom@kednos.com>l: Subject: Re: This is the End... My Only Friend, The End...( Message-ID: <opsmysxcbkzgicya@hyrrokkin>  3 On Tue, 01 Mar 2005 10:02:41 -0500, Brad Hamilton  t) <brMadAhaPmiSlton@coMmcAasPt.Snet> wrote:e   > John Smith wrote:g >f > <snip>J >> I hate to say this, and I know the PC (politically correct) police willI >> stomp on me for saying it, but this sort of acceptance of the status  l	 >> quo iscH >> exactly what HP is counting on. It's the "we'd best be thankful for   >> what fewwG >> crumbs we have left - can't be seen or heard twisting the dragon's  r >> tail", asI >> opposed to standing up to HP and saying "Quit fucking with us - your  s	 >> payinge >> customers". >rK > I imagine a number of (former) customers have done so already, yet HP's  hI > presumed attitude of "benign neglect" remains.  Bottom line remains -   K > standing up for yourself may feel good, but doesn't change the situation.  >iJ > If - as some here suspect - HP is attempting to abandon the enterprise  L > computing market, then they will adopt a "take it or leave it" attitude,  L > and probably be glad to be rid of the "overhead" involved in maintaining  2 > a customer base it no longer desires to possess.  E Won't happen, that's where they make all their money.  If anything,  t jettisoning $ the PC, where they are losing money.     -- hC Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------  % Date: Tue, 01 Mar 2005 11:20:34 -0500a- From: JF Mezei <jfmezei.spamnot@teksavvy.com> : Subject: Re: This is the End... My Only Friend, The End...B Message-ID: <1109693290.c699cb00d22bd3eacb96cd8fdc386f40@teranews>   John Smith wrote:n >  > The new hires are in India.r  G Would those be HP employees on HP payroll (or an HP subsidiary) or somee& totally different outsourcing outfit ?   ------------------------------  % Date: Tue, 01 Mar 2005 11:30:01 -0500l- From: JF Mezei <jfmezei.spamnot@teksavvy.com> : Subject: Re: This is the End... My Only Friend, The End...B Message-ID: <1109693856.e1cb78f6d2dfb5c2ce0e8b01b00c8e72@teranews>   Tom Linden wrote:6E > Won't happen, that's where they make all their money.  If anything, 
 > jettisoningt& > the PC, where they are losing money.  G Not if you read Wall Street commentaries. Criticism has been focused ateG the enterprise division that has not performed well.  This gives HP thee! PR permission to can enterprise. k  H In both cased of Palmer trying to kill VMS and Curly trying to kill VMS,H the financials prevented both from doing it. The lost profits would haveE really killed the company's core (but money losing)  wintel products.e  ? However, in the case of HP, if the press sees enterprise as notlA performing, and if the profits really come from ink, then killingI! enterprise may not be impossible.   C Remember that "not performing" can be interpresent in many ways. IthH could still be profitable and not generating the margins of yesteryears.E But if wall street says "not performing", then HP has to do somethinghE about it. It could be VP musical chairs, it could be cutting productsh$ with the least growth potential etc.    > I realise that VMS management are humans with mortgages, maybe> kids/dogs/cats/lizzards to feed. However, if they feel that HPG management are not taking care of VMS (or worse, planning on downsizingaD VMS), then perhaps VMS management should take a course on the art ofH leaking information without it being traceable to them. That would allow= the VMS activists to chain themselves to trees in front of HPsH headquarters with large banners "SAVE VMS" and make the rucous necessaryF to force HP management to deny such plans and thus cancel those plans.  G (relace "chain themselsve to trees" with appropriate protest method fori the 21st century).   ------------------------------  $ Date: Tue, 1 Mar 2005 11:28:13 -0500# From: "John Smith" <a@nonymous.com> : Subject: Re: This is the End... My Only Friend, The End..., Message-ID: <CMudnfxevsGABbnfRVn-vw@igs.net>   JF Mezei wrote:o > John Smith wrote:e >> >> The new hires are in India. >0D > Would those be HP employees on HP payroll (or an HP subsidiary) or- > some totally different outsourcing outfit ?o    L Probably just people working at the Alang shipyard for $0.30 per hour - sameF place they haul old ships to be cut up for scrap without environmentalI controls......the ideal place for HP to scrap all those Alphaservers with 7 the non-compliant plastic knobs and solder connections.c  > see: http://www.greenpeaceweb.org/shipbreak/shipsforscrap3.pdf   --- OpenVMS - The classics never go out of style.    ------------------------------  % Date: Tue, 01 Mar 2005 08:30:47 -0800 # From: "Tom Linden" <tom@kednos.com>T: Subject: Re: This is the End... My Only Friend, The End...( Message-ID: <opsmyv5luozgicya@hyrrokkin>  . On Tue, 01 Mar 2005 11:30:01 -0500, JF Mezei  % <jfmezei.spamnot@teksavvy.com> wrote::   > Tom Linden wrote:sF >> Won't happen, that's where they make all their money.  If anything, >> jettisoning' >> the PC, where they are losing money.g >cI > Not if you read Wall Street commentaries. Criticism has been focused atrI > the enterprise division that has not performed well.  This gives HP thes" > PR permission to can enterprise.  H What all is included in the enterprise division?  It includes many partsJ some of which perform poorly and some not.  For the past two years VMS hasD contributed ~$860 Million gross profit on revenues of ~$4 Billion,  	 according H to my sources.  That represent a slight decrease top line YOY and slightH increase bottom line YOY.  So what are losing parts of the business that VMS is subsidizing?n >oJ > In both cased of Palmer trying to kill VMS and Curly trying to kill VMS,J > the financials prevented both from doing it. The lost profits would haveG > really killed the company's core (but money losing)  wintel products.t >sA > However, in the case of HP, if the press sees enterprise as noteC > performing, and if the profits really come from ink, then killing # > enterprise may not be impossible.S >eE > Remember that "not performing" can be interpresent in many ways. IthJ > could still be profitable and not generating the margins of yesteryears.G > But if wall street says "not performing", then HP has to do somethinglG > about it. It could be VP musical chairs, it could be cutting productss& > with the least growth potential etc. >a > @ > I realise that VMS management are humans with mortgages, maybe@ > kids/dogs/cats/lizzards to feed. However, if they feel that HPI > management are not taking care of VMS (or worse, planning on downsizing,F > VMS), then perhaps VMS management should take a course on the art ofJ > leaking information without it being traceable to them. That would allow? > the VMS activists to chain themselves to trees in front of HP%J > headquarters with large banners "SAVE VMS" and make the rucous necessaryH > to force HP management to deny such plans and thus cancel those plans. >(I > (relace "chain themselsve to trees" with appropriate protest method fore > the 21st century).       -- eC Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------  $ Date: Tue, 1 Mar 2005 12:17:53 -0500# From: "John Smith" <a@nonymous.com>m: Subject: Re: This is the End... My Only Friend, The End..., Message-ID: <yMadnV45L5BcPrnfRVn-vA@igs.net>   JF Mezei wrote:' > Tom Linden wrote:MF >> Won't happen, that's where they make all their money.  If anything, >> jettisoning' >> the PC, where they are losing money.s > F > Not if you read Wall Street commentaries. Criticism has been focusedE > at the enterprise division that has not performed well.  This givesl) > HP the PR permission to can enterprise.l >eE > In both cased of Palmer trying to kill VMS and Curly trying to killeD > VMS, the financials prevented both from doing it. The lost profits@ > would have really killed the company's core (but money losing) > wintel products. >sA > However, in the case of HP, if the press sees enterprise as notgC > performing, and if the profits really come from ink, then killing9# > enterprise may not be impossible.s >nE > Remember that "not performing" can be interpresent in many ways. Its= > could still be profitable and not generating the margins ofsG > yesteryears. But if wall street says "not performing", then HP has to C > do something about it. It could be VP musical chairs, it could be 7 > cutting products with the least growth potential etc.r >s >h@ > I realise that VMS management are humans with mortgages, maybe@ > kids/dogs/cats/lizzards to feed. However, if they feel that HP> > management are not taking care of VMS (or worse, planning onF > downsizing VMS), then perhaps VMS management should take a course onD > the art of leaking information without it being traceable to them.D > That would allow the VMS activists to chain themselves to trees inE > front of HP headquarters with large banners "SAVE VMS" and make thebE > rucous necessary to force HP management to deny such plans and thush > cancel those plans.n >aE > (relace "chain themselsve to trees" with appropriate protest method  > for the 21st century).    I The appropriate place is at the HP annual meeting in Chicago (this year), G and the way you do it is to walk in with your proxy and then stand at aeI microphone and ask the assembled BoD why a profitable line-of-business isoH not being promoted by HP, sadly to the detriment of all the shareholders> bottom line (and that includes the BoD who also own HP stock).  K Sort of like "I'd like to address a few questions to Patricia Dunn and Bill-D Wayman, and I'd request that all of them  be addressed at this time.  I Reliable sources within HP have indicated that the OpenVMS unit generatednC nearly $800 million in profit last year, without the benefit of anycI meaningful advertising or marketing. Clearly this is a bright spot withinCJ the Enterprise BCS unit - one that can clearly use a few shining stars. InJ todays' age of viruses, worms, escalating patching costs and concerns overK system reliability amongst computing customers, why is OpenVMS not promotedsK by HP as the most reliable general purpose operating system HP has to offerSJ its customers for backbone servers for their enterprises, large and small?    C According to HP's own commissioned studies, OpenVMS offers the bestwE total-cost-of-ownership and the most sophisticated disaster-tolerancelH features on the market of all enterprise-grade operating systems, a factJ which most corporations who are serious about their computing environmentsL ought to know. OpenVMS has been offering immunity from viruses and unmatchedL reliability and disaster tolerance for over 25 years, a most notable exampleF occuring during the tragic events on 9/11. Isn't it about time we as aB company proudly promoted and offered this excellent product to ourC customers? Shouldn't we be actively offering and advertising to our B customers the very best product in our entire stable of products?"    I You will notice that the wording of the foregoing was crafted in order totG put HP execs in a bad light if they spoke ill of VMS, to show that they F don't care about a profitable product or customers if they don't fullyJ answer the questions, and to get everyone's ears in the meeting to perk upJ at the mention of OpenVMS and 9/11, including the assembled members of the press.  J Now if 5-6 c.o.v. regulars who are HP shareholders were planning to attendE the HP annual meeting. and didn't mind a little public speaking......w   --- OpenVMS - The classics never go out of style.    ------------------------------  $ Date: Tue, 1 Mar 2005 10:09:38 +0200- From: "Kari Keronen" <kari.keronen@digita.fi>t( Subject: Re: VMS Alpha 8.2 with CSWS 2.08 Message-ID: <erVUd.1494$hk3.565@reader1.news.jippii.net>  1 "Tom Linden" <tom@kednos.com> kirjoitti viestisse" news:opsmww9xn6zgicya@hyrrokkin...F > On Mon, 28 Feb 2005 14:56:05 GMT, Nigel Barker <nigel@hp.com> wrote: >>L > > On Mon, 28 Feb 2005 13:58:10 -0000, "Richard Brodie" <R.Brodie@rl.ac.uk>
 > > wrote: > >t > >>= > >> "Kari Keronen" <kari.keronen@digita.fi> wrote in message 8 > >> news:QyEUd.1282$cg3.1241@reader1.news.jippii.net... > >>G > >>> KAJAVA$DKA0:[SYS0.SYSCOMMON.APACHE.][000000]APACHE$APR_SHRP.EXE;1 A > >>> -SYSTEM-W-SYSVERDIF, system version mismatch; please relinkl > >>>  > >>> Known problem or what ?o > >>H > >> Apparently, something in the Apache port required some system level > >> hacking, so I guessH > >> you're out of luck until there is a new release. Someone else might > >> have the inside track oneI > >> this... but obviously, porting the 1.3 stream was a higher priority.  > > K > > CSWS 2.0 does not support OpenVMS 8.2. You'll need to wait for CSWS 2.1  > > ifK > > you're running OpenVMS 8.2. This should ship or rather be available fore > > download > > Real Soon Now. >-! > Have you tried installing WASD?0  I No, but if someone has tried WASD on OpenVMS 8.2 Alpha/ODS-5, I'd like tow know the results.s+ I don't currently have time to do the test.6   -Kari-   > >e > > -- > > Nigel Barker# > > Live from the sunny Cote d'Azurm >a >n >: > -- 3E > Using Opera's revolutionary e-mail client: http://www.opera.com/m2/<   ------------------------------  # Date: Tue, 01 Mar 2005 09:26:09 GMT[! From: Nigel Barker <nigel@hp.com>e( Subject: Re: VMS Alpha 8.2 with CSWS 2.08 Message-ID: <4db82190oq29hh6t0fl3gfn49k5ovco8l5@4ax.com>  J On Tue, 1 Mar 2005 10:09:38 +0200, "Kari Keronen" <kari.keronen@digita.fi> wrote:   >o2 >"Tom Linden" <tom@kednos.com> kirjoitti viestiss# >news:opsmww9xn6zgicya@hyrrokkin...hG >> On Mon, 28 Feb 2005 14:56:05 GMT, Nigel Barker <nigel@hp.com> wrote:- >>M >> > On Mon, 28 Feb 2005 13:58:10 -0000, "Richard Brodie" <R.Brodie@rl.ac.uk>0 >> > wrote:h >> > >> >>o> >> >> "Kari Keronen" <kari.keronen@digita.fi> wrote in message9 >> >> news:QyEUd.1282$cg3.1241@reader1.news.jippii.net...Z >> >> H >> >>> KAJAVA$DKA0:[SYS0.SYSCOMMON.APACHE.][000000]APACHE$APR_SHRP.EXE;1B >> >>> -SYSTEM-W-SYSVERDIF, system version mismatch; please relink >> >>> >> >>> Known problem or what ? >> >> I >> >> Apparently, something in the Apache port required some system levelt >> >> hacking, so I guesscI >> >> you're out of luck until there is a new release. Someone else mighto >> >> have the inside track onJ >> >> this... but obviously, porting the 1.3 stream was a higher priority. >> >L >> > CSWS 2.0 does not support OpenVMS 8.2. You'll need to wait for CSWS 2.1 >> > ifoL >> > you're running OpenVMS 8.2. This should ship or rather be available for
 >> > downloade >> > Real Soon Now.u >>" >> Have you tried installing WASD? >.J >No, but if someone has tried WASD on OpenVMS 8.2 Alpha/ODS-5, I'd like to >know the results., >I don't currently have time to do the test. >e >-Kari--  O I should have mentioned that SWS 1.3-1 does run on OpenVMS 8.2 & ships with thes' OS. It's also available for download atn? http://h71000.www7.hp.com/openvms/products/ips/apache/csws.html    -- Nigel Barker Live from the sunny Cote d'Azur    ------------------------------  % Date: Wed, 02 Mar 2005 01:09:57 +1030e* From: Mark Daniel <mark.daniel@vsm.com.au>( Subject: Re: VMS Alpha 8.2 with CSWS 2.0- Message-ID: <42247eda@duster.adelaide.on.net>>   Kari Keronen wrote:m3 > "Tom Linden" <tom@kednos.com> kirjoitti viestissp$ > news:opsmww9xn6zgicya@hyrrokkin... > F >>On Mon, 28 Feb 2005 14:56:05 GMT, Nigel Barker <nigel@hp.com> wrote: >> >>K >>>On Mon, 28 Feb 2005 13:58:10 -0000, "Richard Brodie" <R.Brodie@rl.ac.uk>m	 >>>wrote:w >>>d >>>i< >>>>"Kari Keronen" <kari.keronen@digita.fi> wrote in message7 >>>>news:QyEUd.1282$cg3.1241@reader1.news.jippii.net...j >>>> >>>>F >>>>>KAJAVA$DKA0:[SYS0.SYSCOMMON.APACHE.][000000]APACHE$APR_SHRP.EXE;1@ >>>>>-SYSTEM-W-SYSVERDIF, system version mismatch; please relink >>>>>n >>>>>Known problem or what ? >>>>G >>>>Apparently, something in the Apache port required some system level  >>>>hacking, so I guess-G >>>>you're out of luck until there is a new release. Someone else mighty >>>>have the inside track onH >>>>this... but obviously, porting the 1.3 stream was a higher priority. >>>0J >>>CSWS 2.0 does not support OpenVMS 8.2. You'll need to wait for CSWS 2.1 >>>iftJ >>>you're running OpenVMS 8.2. This should ship or rather be available for >>>download  >>>Real Soon Now.= >>! >>Have you tried installing WASD?: >  > K > No, but if someone has tried WASD on OpenVMS 8.2 Alpha/ODS-5, I'd like toa > know the results.e- > I don't currently have time to do the test.t >  > -Kari-  C WASD was 'ported'* to I[A]64** way back in December 2003 and a kit oI capable of installation and build on I[A]64 under the 8.1 field-test kit oF released as WASD v8.4 in January 2004.  This (actually WASD v8.5) was B rebuilt during the year under one of the V8.2 field-test releases I without issue.  I should imagine the same will apply to the current WASD =H v9.0 under the final release of VMS V8.2.  Only today (oops, yesterday) C I was informed of the arrival of the V8.2 media kit for the I[A]64 aE system used and that this kit should be installed and available next  B week so I'll soon have first-hand experience doing it.  After the D trivial exercise of the initial 'port'* from Alpha/VAX to Itanium I I expect no issues with a mere rebuild.  WASD can be installed on an ODS-5 oG volume though for compatibility with VMS back to V6.0 retains does not n= require (though as a separate point can elegantly serve) EFS.      *p<    http://www.openvms.org/stories.php?story=04/01/05/0610152     **D    I have not been following it.  Has I64 been settled on in lieu ofD    the original IA64?  The two seem to be being used interchangably.  F +--------------------------------------------------------------------+E   Mark Daniel                         http://wasd.vsm.com.au/adelaidetF   mailto:Mark.Daniel@wasd.vsm.com.au (Mark.Daniel@dsto.defence.gov.au);   A pox on the houses of all SPAMers.  Make that two poxes.eF +--------------------------------------------------------------------+   >>>--  >>>Nigel Barkera" >>>Live from the sunny Cote d'Azur >> >> >> >>-- aE >>Using Opera's revolutionary e-mail client: http://www.opera.com/m2/r   ------------------------------  % Date: Tue, 01 Mar 2005 06:43:29 -0800r# From: "Tom Linden" <tom@kednos.com> ( Subject: Re: VMS Alpha 8.2 with CSWS 2.0( Message-ID: <opsmyq6rdbzgicya@hyrrokkin>  J On Wed, 02 Mar 2005 01:09:57 +1030, Mark Daniel <mark.daniel@vsm.com.au>   wrote:  D >  I have not been following it.  Has I64 been settled on in lieu ofE >   the original IA64?  The two seem to be being used interchangably.h >0  
 I64 = Itaniumd  
 IA64 = x86-64r   I think I got that right.o   -- hC Using Opera's revolutionary e-mail client: http://www.opera.com/m2/h   ------------------------------  # Date: Tue, 01 Mar 2005 16:43:23 GMTi& From: John Reagan <john.reagan@hp.com>( Subject: Re: VMS Alpha 8.2 with CSWS 2.00 Message-ID: <LY0Vd.768$BT3.387@news.cpqcorp.net>   Tom Linden wrote:s2 > On Wed, 02 Mar 2005 01:09:57 +1030, Mark Daniel " > <mark.daniel@vsm.com.au>  wrote: > E >>  I have not been following it.  Has I64 been settled on in lieu ofsF >>   the original IA64?  The two seem to be being used interchangably. >> >  > I64 = Itaniumc >  > IA64 = x86-64  >  > I think I got that right.e >   @ I64 is purely a marketing/naming convention invented by us as a I shorthand for "Industry Standard 64" or some such phrase.  We use I64 as PB a shorthand for "OpenVMS I64" which is itself a shorthand for "HP B OpenVMS Industry Standard 64 Operating System".  We use IA64 as a , shorthand for the architecture name Itanium.     --   John ReaganU/ HP Pascal/{A|I}MACRO for OpenVMS Project Leader= Hewlett-Packard Company    ------------------------------  $ Date: Tue, 1 Mar 2005 11:12:12 -0500# From: "Dan Allen" <dallen@nist.gov>r( Subject: RE: VMS Alpha 8.2 with CSWS 2.0: Message-ID: <JFEPKAPBPMDFDBOIANGDOEAGGCAA.dallen@nist.gov>   > -----Original Message-----* > From: Tom Linden [mailto:tom@kednos.com]' > Sent: Tuesday, March 01, 2005 9:43 AMs > To: Info-VAX@Mvb.Saic.Comh* > Subject: Re: VMS Alpha 8.2 with CSWS 2.0 >u >aJ > On Wed, 02 Mar 2005 01:09:57 +1030, Mark Daniel <mark.daniel@vsm.com.au> > wrote: >uF > >  I have not been following it.  Has I64 been settled on in lieu ofG > >   the original IA64?  The two seem to be being used interchangably.T > >  >a > I64 = Itaniumo >: > IA64 = x86-64e >t > I think I got that right.t  N Perhaps in Info-Vax but Intel uses the term EM64T in their docs for the 64 bit5 Extended Memory technology enchanced version of IA32.i >t > --E > Using Opera's revolutionary e-mail client: http://www.opera.com/m2/n >e >t   ------------------------------  # Date: Tue, 01 Mar 2005 10:42:03 GMT3" From:   VAXman-  @SendSpamHere.ORG9 Subject: VMS V8.2 Source Listings (Shipping Confirmation)40 Message-ID: <00A401A9.DC2D7316@SendSpamHere.ORG>  D If you get VMS source listings and have received your V8.2 listings,D please let me know (here or send me a private email).  It looks likeC I may need to wade through the muck and mire known as HP again.  :(n   --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COMt            t5   "Well my son, life is like a beanstalk, isn't it?" r   ------------------------------  # Date: Tue, 01 Mar 2005 16:26:43 GMT * From: Paul Anderson <paul.anderson@hp.com>= Subject: Re: VMS V8.2 Source Listings (Shipping Confirmation)a5 Message-ID: <010320051056100070%paul.anderson@hp.com>   E In article <00A401A9.DC2D7316@SendSpamHere.ORG>, < @SendSpamHere.ORG>e wrote:  F > If you get VMS source listings and have received your V8.2 listings,F > please let me know (here or send me a private email).  It looks likeE > I may need to wade through the muck and mire known as HP again.  :(   E Did you order the source listings with or without the rack-mount kit?e   Paul   -- p  Paul Anderson   OpenVMS Engineering    Hewlett-Packard Companyr   ------------------------------  # Date: Tue, 01 Mar 2005 16:08:03 GMTf" From:   VAXman-  @SendSpamHere.ORG= Subject: Re: VMS V8.2 Source Listings (Shipping Confirmation)=0 Message-ID: <00A401D7.66E4B20A@SendSpamHere.ORG>  b In article <010320051056100070%paul.anderson@hp.com>, Paul Anderson <paul.anderson@hp.com> writes:F >In article <00A401A9.DC2D7316@SendSpamHere.ORG>, < @SendSpamHere.ORG> >wrote:t >mG >> If you get VMS source listings and have received your V8.2 listings,nG >> please let me know (here or send me a private email).  It looks likenF >> I may need to wade through the muck and mire known as HP again.  :( >aF >Did you order the source listings with or without the rack-mount kit?  G I'll just take the pedestal version, if it ever ships, and shutup.  Thet: rack mount option is too much of a P.I.T.A. to track down.  H FYI, Some kind souls in VMS sent me a rack mount kit.  I'd mention theirI names but fear that they'd get inundated with requests from other Itanium E owners that are trying to navigate the mire of _H_eadache _P_roducer.a   -- uK VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM             a5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  # Date: Tue, 01 Mar 2005 09:34:48 GMTB! From: Nigel Barker <nigel@hp.com>*E Subject: Re: What is the Difference between Shadow and Mirrored disk? 8 Message-ID: <0tb8215v1cqd6j6phpuk4isfa33liqm5fa@4ax.com>  M On Mon, 28 Feb 2005 18:04:28 -0600, Chris Scheers <chris@applied-synergy.com>m wrote:  H >AFAIK, DRAn: (KZPSx) drives are local drives visible to only one node, : >so they can't be used as quorum drives anyways, can they?  L You can use local disks as quorum. It's not ideal but if e.g. you have a twoP node LAVC making one of the local disks a quorum disk at least gives you a 50:507 chance of the cluster staying up if one node goes down.w   -- Nigel Barker Live from the sunny Cote d'Azurh   ------------------------------  % Date: Tue, 01 Mar 2005 09:26:28 +0000w- From: Roy Omond <Roy.Omond@BlueBubble.UK.Com> E Subject: Re: What is the Difference between Shadow and Mirrored disk?p, Message-ID: <38iquuF5lpe37U1@individual.net>   Nigel Barker wrote:lO > On Mon, 28 Feb 2005 18:04:28 -0600, Chris Scheers <chris@applied-synergy.com>h > wrote: >eI >>AFAIK, DRAn: (KZPSx) drives are local drives visible to only one node, a; >>so they can't be used as quorum drives anyways, can they?e >eN > You can use local disks as quorum. It's not ideal but if e.g. you have a twoR > node LAVC making one of the local disks a quorum disk at least gives you a 50:509 > chance of the cluster staying up if one node goes down.e  G If the quorum disk is *local* to node A (i.e. node B has no direct pathsH to it), then it's superfluous.  Might as well give node A the only vote.H Your 50:50 chance remains the same.  Node B goes down - cluster remains.& Node A goes down - cluster evaporates.   ------------------------------  # Date: Tue, 01 Mar 2005 10:24:46 GMTu! From: Nigel Barker <nigel@hp.com>)E Subject: Re: What is the Difference between Shadow and Mirrored disk?r8 Message-ID: <kqe821li8v7v2041gised9ua98sbtrri3j@4ax.com>  K On Tue, 01 Mar 2005 09:26:28 +0000, Roy Omond <Roy.Omond@BlueBubble.UK.Com>  wrote:   >Nigel Barker wrote:P >> On Mon, 28 Feb 2005 18:04:28 -0600, Chris Scheers <chris@applied-synergy.com>	 >> wrote:l >>J >>>AFAIK, DRAn: (KZPSx) drives are local drives visible to only one node, < >>>so they can't be used as quorum drives anyways, can they? >>O >> You can use local disks as quorum. It's not ideal but if e.g. you have a two S >> node LAVC making one of the local disks a quorum disk at least gives you a 50:50r: >> chance of the cluster staying up if one node goes down. > H >If the quorum disk is *local* to node A (i.e. node B has no direct pathI >to it), then it's superfluous.  Might as well give node A the only vote.AI >Your 50:50 chance remains the same.  Node B goes down - cluster remains.e' >Node A goes down - cluster evaporates.h  N Correct but I have seen it done. It's amazing how complicated some people makeO the simple task of quorum & votes in a cluster e.g. assigning different numbers . of votes to individual nodes plus quorum disk.   -- Nigel Barker Live from the sunny Cote d'Azure   ------------------------------   End of INFO-VAX 2005.120 ************************>>> On Mon, 28 Feb 2005 16:20:00 -0500, John Smith <a@nonymous.com>e
 >>> wrote: >>>e >>>e >>>> Didier MORANDI wrote: >>>> >>>>> Hi Pals, >>>>> G >>v40/kill# <<< CWD ../../freewarev40/kill062 E >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/kill062.% <<< CWD ../../freewarev40/kill_node-G >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/kill_nodee! <<< CWD ../../freewarev40/kp093dC >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/kp093e" <<< CWD ../../freewarev40/kprintD >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/kprint" <<< CWD ../../freewarev40/kronosD >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/kronos$ <<< CWD ../../freewarev40/laser011F >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/laser011! <<< CWD ../../freewarev40/ld062dC >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/ld062e$ <<< CWD ../../freewarev40/ledermanF >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/lederman' <<< CWD ../../freewarev40/lincity-109oI >>> 550 %%RMS-E-DNF, directory not found: ../../freewarev40/lincity-109 , <<< CWD ../../freewarev40/