1 INFO-VAX	Wed, 24 Jul 2002	Volume 2002 : Issue 404       Contents:% better porting library/Mozilla jacket 4 COBOL Calling C -- Handling Args Passed by Reference8 Re: COBOL Calling C -- Handling Args Passed by Reference RE: CSA -> DSPP  Re: CSA -> DSPP % Re: Cygwin/xfree86 and VMS/DecWindows ; Re: different behavior of a C++ binary in different machine ; Re: different behavior of a C++ binary in different machine ; Re: different behavior of a C++ binary in different machine ; Re: different behavior of a C++ binary in different machine & DiskXcel vs OpenVMS 7.3 read cacheing?* Re: DiskXcel vs OpenVMS 7.3 read cacheing?4 Re: Excellent Commerzbank OpenVMS public testimonialA Re: How to create a shareable image from an object library (long) A Re: How to create a shareable image from an object library (long) 0 Re: HP "OpenVMS Path to Itanium" Roadshow report0 RE: HP "OpenVMS Path to Itanium" Roadshow report0 Re: HP "OpenVMS Path to Itanium" Roadshow report0 Re: HP "OpenVMS Path to Itanium" Roadshow report$ Re: HP Lan Console x Itanium servers# Re: HSV , Snaps and older databases # Re: HSV , Snaps and older databases # Re: HSV , Snaps and older databases > Re: HSV snapshots vs. Spiralog ? (Was: CLI access to HSV's...)> RE: HSV snapshots vs. Spiralog ? (Was: CLI access to HSV's...)> Re: HSV snapshots vs. Spiralog ? (Was: CLI access to HSV's...) Intel to smash AMD Re: Intel to smash AMD+ Re: Itanic2 - the cHumPaq spin continues... + Re: Itanic2 - the cHumPaq spin continues... + Re: Itanic2 - the cHumPaq spin continues...  low-level formatting SCSI disks # Re: low-level formatting SCSI disks ) Re: Mail degraded from VAX 6.2 to VAX 7.3  Re: MV 3400 won't keep settings * Re: Need 80' Fortran/VAX training material9 P.Thread: setting RR scheduling policy on default thread?   RE: Questions about license paks  Re: Questions about license paks( Raid Array 7000 firmware update question re: RDB Questions  RZ40 Disk Problem  Re: Security Banner displayed  Re: security monitoring  Single Column text output?; RE: Size of the comp.os.vms readership ? , was: RE: OpenVMS @ Size of the comp.os.vms readership ? , was: RE: OpenVMS webring:D RE: Size of the comp.os.vms readership ? , was: RE: OpenVMS webring:D Re: Size of the comp.os.vms readership ? , was: RE: OpenVMS webring: TDMS (was re: RDB Questions) Re: TSM and Newer Circuit Names ( Re: Upgrading from 7.2-1 and latest ECOs( Re: Upgrading from 7.2-1 and latest ECOs( Re: Upgrading from 7.2-1 and latest ECOs( Re: Upgrading from 7.2-1 and latest ECOs( Re: Upgrading from 7.2-1 and latest ECOs3 Re: VMS Mail problems Internal/External receipient. * [Hobbyist] install of SQL/Services problem! Re: [Hobbyist] User account setup  [OT] Attn: LennyH [Q] How is condition code selected for $STATUS from multi-line messages?L Re: [Q] How is condition code selected for $STATUS from multi-line messages?  F ----------------------------------------------------------------------    Date: 23 Jul 2002 13:15:12 -0600- From: koehler@encompasserve.org (Bob Koehler) . Subject: better porting library/Mozilla jacket3 Message-ID: <hM5HJXEnU1yp@eisner.encompasserve.org>   F    If you're using the VMS C porting library (Mozilla does), here's anF    edit you can make to improve the listing of "/".  It shows the diskF    names by logical name instead of by device name.  The format of theF    change is as input to edit/slp.  The change is to opendir_jacket.c.  G    If you're using Mozilla, you can use this by downloading the porting H    library, building the vms_jackets.exe shareable image, and replacing ;    the one which shipped with Mozilla (Mozilla kit calls it '    sys$common:[mozilla]vms_jackets.so).    opendir_jacket.upd:  -  316 <// rdk -start changes'       	    	int item2 = DVI$_LOGVOLNAM; )     	    	struct dsc$descriptor_s lognam; "       	    	unsigned short namlen;A       	    	#define LOG_MAX 64  	// cf: System Services Reference %     	    	char lognam_buf[LOG_MAX+1];   +     	    	lognam.dsc$b_dtype=DSC$K_DTYPE_T; +     	    	lognam.dsc$b_class=DSC$K_CLASS_S; &     	    	lognam.dsc$w_length=LOG_MAX;*     	    	lognam.dsc$a_pointer=lognam_buf;D       	    	/* try to get the logical volume name (logical name used&       	    	 * in the MOUNT command */A       	    	rv=lib$getdvi(&item2,0,&devnam,NULL,&lognam,&namlen);    -  322,  322  0       	    	/* use logical name if we got one */9       	    	if ($VMS_STATUS_SUCCESS(rv) && (namlen != 0)) 
       	    	{        	    	  pin = lognam_buf; "                   retlen = namlen;
       	    	}        	    	else#                   pin = devnam_buf;  <// rdk -end changes /    ------------------------------  # Date: Wed, 24 Jul 2002 00:55:14 GMT  From: jrbrady@mindspring.com= Subject: COBOL Calling C -- Handling Args Passed by Reference 3 Message-ID: <3d3df047.89133689@news.mindspring.com>    All,  G Recently I started a project to implement two utility programs in C.    D The utilities were originally written in VAX MACRO and I decided to F rewrite them instead of porting the MACRO code to OpenVMS Alpha. BeingE new to the world of C, I'd greatly appreciate ideas for improving the 8 way in which the arguments are handled by the C program.  G The utility programs are passed a fairly complex data structure and two E single-byte character strings by reference.  The data structure is of I varying size depending on the number of repeating field groups following  F several fixed fields.  I defined a nested structure for the groups andF point to it; incrementing the structure pointer allows access to each,J but it's up to the program to prevent incrementing into unrelated memory. B There might be a better way to do this.  There are pointers to twoJ character strings, and the way in which I construct the string descriptor H using a separate function seems rather convoluted.  Finally, the utilityC programs are called on an interactive basis and must be efficient.    G Following are a couple of prototype programs, CALLER (COBOL) and CALLEE G (C), preceded by their output.  They were compiled and executed on both H an Alphaserver and a VAXstation with the same results.  Both systems are running OpenVMS 7.2 Hobbyist.     Thanks much for your assistance!  > Jason Brady   jrbrady@nospam mindspring.com   Lynnwood, WA USA  J ========================================================================== $ run caller >> Calling CALLEE <<  % ********** Starting CALLEE **********  Parm 1           A Parm 2           k Longword 1       1234  Longword 2       5678  Char 1           a Char 2           b Char 3           c Char 4           d Field 1 a        15  Field 1 e        a Field 2 a        17  Field 2 e        g Field 3 a        24  Field 3 e        d Field Set Qty    3 Char String Len  50 C Char String      abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWX # ********** Ending CALLEE **********    >> Returned to CALLER << >> Return code is +000001234 $ F ======================================================================F /* CALLEE - C program to test passing data structures and character */F /*          strings by reference from COBOL. Written 18-July-2002.  */F /*          Tested on OpenVMS 7.2 for Alpha and VAX.                */   #pragma  module CALLEE "1-1"   #include <descrip> #include <stdio> #include <stdlib>  #include <string>  #include <stsdef>    static struct field_set_s  {      long field_a;      long field_b;      long field_c;      long field_d;      char field_e;      char field_f;      char field_g;      char field_h;  };   static struct data_struct  {      long longword_1;     long longword_2;     long *field_set_qty_ptr;     long *field_set_ptr;     long *char_string_ptr;     long *char_string_len_ptr;     char char_1;     char char_2;     char char_3;     char char_4;!     struct field_set_s field_set;  };   /* Function Prototypes */ B int callee(struct data_struct *data_struct_ptr, char *parm_1_ptr,             char *parm_2_ptr); ; void display_char_string(int string_len, char *string_ptr);    /* Callee Routine */B int callee(struct data_struct *data_struct_ptr, char *parm_1_ptr,             char *parm_2_ptr) {      int  return_code;      int  field_set_qty;      int  char_string_len;      char *char_string_ptr;     int  field1a;      int  field2a;      int  field3a;      char field1e;      char field2e;      char field3e;      char parm1[2];     char parm2[2];&     struct field_set_s *field_set_ptr;         '     $DESCRIPTOR(parm_1_dsc,parm_1_ptr); '     $DESCRIPTOR(parm_2_dsc,parm_2_ptr);   .     strncpy(parm1,parm_1_dsc.dsc$a_pointer,1);.     strncpy(parm2,parm_2_dsc.dsc$a_pointer,1);     parm1[1] = '\0';     parm2[1] = '\0';<     char_string_len = *data_struct_ptr->char_string_len_ptr;B     char_string_ptr = (char (*)) data_struct_ptr->char_string_ptr;  2     field_set_ptr   = &data_struct_ptr->field_set;:     field_set_qty   = *data_struct_ptr->field_set_qty_ptr;-     field1a         = field_set_ptr->field_a; -     field1e         = field_set_ptr->field_e;      ++field_set_ptr;  -     field2a         = field_set_ptr->field_a; -     field2e         = field_set_ptr->field_e;      ++field_set_ptr;-     field3a         = field_set_ptr->field_a; -     field3e         = field_set_ptr->field_e;   8     printf("\n********** Starting CALLEE **********\n");+     printf("Parm 1           %s\n", parm1); +     printf("Parm 2           %s\n", parm2); A     printf("Longword 1       %d\n", data_struct_ptr->longword_1); A     printf("Longword 2       %d\n", data_struct_ptr->longword_2); =     printf("Char 1           %c\n", data_struct_ptr->char_1); =     printf("Char 2           %c\n", data_struct_ptr->char_2); =     printf("Char 3           %c\n", data_struct_ptr->char_3); =     printf("Char 4           %c\n", data_struct_ptr->char_4); -     printf("Field 1 a        %d\n", field1a); -     printf("Field 1 e        %c\n", field1e); -     printf("Field 2 a        %d\n", field2a); -     printf("Field 2 e        %c\n", field2e); -     printf("Field 3 a        %d\n", field3a); -     printf("Field 3 e        %c\n", field3e); 3     printf("Field Set Qty    %d\n", field_set_qty); 5     printf("Char String Len  %d\n", char_string_len); :     display_char_string(char_string_len, char_string_ptr);6     printf("********** Ending CALLEE **********\n\n");  .     return_code = 1234;                            return(return_code); } & /* Display Character String Routine */: void display_char_string(int string_len, char *string_ptr) { !     char char_string[string_len]; +     struct dsc$descriptor char_string_dsc = 3          { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL };   /     char_string_dsc.dsc$w_length  = string_len; /     char_string_dsc.dsc$a_pointer = string_ptr;      B     strncpy(char_string,char_string_dsc.dsc$a_pointer,string_len);1     printf("Char String      %s\n", char_string);  }   H ========================================================================        Identification Division.         Program-Id.    CALLER.         Author.        J Brady.#        Date-Written.  18-July-2002.         Date-Compiled. H       ******************************************************************H       * CALLER - COBOL program to test passing data structures and     *H       *          character strings to C.                               *H       ******************************************************************        Environment Division.        Configuration Section.         Source-Computer. AXP.        Object-Computer. AXP.          Data Division. H       ******************************************************************H       * Working Storage Variables                                      *H       ******************************************************************        Working-Storage Section.           01  General-Variables. 2            03 Parm-1                        Pic X.2            03 Parm-2                        Pic X.;            03 The-Return-Code               Pic S9(9) Comp. =            03 The-Return-Code-Display       Pic S9(9) Display $               Sign Leading Separate.        01  Data-Structure.F            03 Longword-1                    Pic S9(9) Comp Value 1234.F            03 Longword-2                    Pic S9(9) Comp Value 5678.B            03 Pointer Value Reference       Field-Set-Quantity.   :            03 Pointer Value Reference       Field-Set.    8            03 Pointer Value Reference       Char-String.?            03 Pointer Value Reference       Char-String-Length. <            03 Char-1                        Pic X Value 'a'.<            03 Char-2                        Pic X Value 'b'.<            03 Char-3                        Pic X Value 'c'.<            03 Char-4                        Pic X Value 'd'.F            03 Field1-A                      Pic S9(9) Comp Value 0015.F            03 Field1-B                      Pic S9(9) Comp Value 0062.F            03 Field1-C                      Pic S9(9) Comp Value 0010.F            03 Field1-D                      Pic S9(9) Comp Value 0001.<            03 Field1-E                      Pic X Value 'a'.<            03 Field1-F                      Pic X Value 'U'.<            03 Field1-G                      Pic X Value 'N'.<            03 Field1-H                      Pic X Value 'X'.F            03 Field2-A                      Pic S9(9) Comp Value 0017.F            03 Field2-B                      Pic S9(9) Comp Value 0004.F            03 Field2-C                      Pic S9(9) Comp Value 0005.F            03 Field2-D                      Pic S9(9) Comp Value 0016.<            03 Field2-E                      Pic X Value 'g'.<            03 Field2-F                      Pic X Value 'P'.<            03 Field2-G                      Pic X Value 'N'.<            03 Field2-H                      Pic X Value 'N'.F            03 Field3-A                      Pic S9(9) Comp Value 0024.F            03 Field3-B                      Pic S9(9) Comp Value 0079.F            03 Field3-C                      Pic S9(9) Comp Value 0001.F            03 Field3-D                      Pic S9(9) Comp Value 0021.<            03 Field3-E                      Pic X Value 'd'.<            03 Field3-F                      Pic X Value 'P'.<            03 Field3-G                      Pic X Value 'N'.<            03 Field3-H                      Pic X Value 'N'.        01  Field-Set. 6            03 Field1-I                      Pic X(10).5            03 Field2-I                      Pic X(5). 2            03 Field3-I                      Pic X.F        01  Field-Set-Quantity               Pic S9(9) Comp Value 0003.F        01  Char-String-Length               Pic S9(9) Comp Value 0050.        01  Char-String. ;            03 Filler                        Pic X(50) Value C               'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWX'.   H       ******************************************************************H       * Mainline Program                                               *H       ******************************************************************        Procedure Division.          AA00-Call-Callee.  '            Initialize General-Variables                        Field-Set                      Move 'A' to Parm-1             Move 'k' to Parm-2   )            Display '>> Calling CALLEE <<'   .            Call 'CALLEE' Using Data-Structure,&                                Parm-1,%                                Parm-2 .                         Giving The-Return-Code  :            Move The-Return-Code to The-Return-Code-Display  -            Display '>> Returned to CALLER <<' ?            Display '>> Return code is ' The-Return-Code-Display               Stop Run             .H ========================================================================   ------------------------------  % Date: Tue, 23 Jul 2002 21:37:17 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> A Subject: Re: COBOL Calling C -- Handling Args Passed by Reference , Message-ID: <3D3E04BA.FD4458E9@videotron.ca>   jrbrady@mindspring.com wrote: F > Recently I started a project to implement two utility programs in C.) >     $DESCRIPTOR(parm_1_dsc,parm_1_ptr); ) >     $DESCRIPTOR(parm_2_dsc,parm_2_ptr);  > 0 >     strncpy(parm1,parm_1_dsc.dsc$a_pointer,1);0 >     strncpy(parm2,parm_2_dsc.dsc$a_pointer,1); >     parm1[1] = '\0'; >     parm2[1] = '\0';  # You could replace the strncpy with lW 	parm1[0] = *(parm_1_dsc.dsc$a_pointer) ;	(much more efficient than a call to strncpy).E  5 It isn't clear why you create the descriptor though. V  K Also the $DESCRIPTOR use above is not quite correct. the size of the stringe" will always be 3 bytes (on a vax).- the $DESCRIPTOR macro does the equivalent of:o3 		 parm_1_dsc.dsc$w_length = sizeof(parm_1_ptr) - 1e  iU The problem is that sizeof(parm_1_ptr) gives the size of the pointer, not the string.i  Y Note that one way to pass strings between cobol, and C is through the use of descriptors:e  ( 01 CHOCOLATE PIC X(50) VALUE 'VALROHNA'. 01 CAKE PIC S9(5) COMP.   8 CALL 'RECIPE' USING CHOCOLATE BY DESCRIPTOR GIVING CAKE.   and in your C program:  + int recipe( struct dsc$descriptor *flavour)h { % flavour->dsc$w_length will then be 50MH flavour->dsc$a_pointer will point to a 50 character, blank padded string containing VALROHNA. }n  H you can then use memcpy to play with the string and you know how big the! string is in the calling program.n   ------------------------------  % Date: Tue, 23 Jul 2002 14:41:07 -0400 * From: WILLIAM WEBB <WWEBB1@email.usps.gov> Subject: RE: CSA -> DSPP- Message-ID: <0033000073644743000002L032*@MHS>C  3 =0APerhaps you should adjust your targeting upward.o   WWWebb   -----Original Message-----/ From: Info-VAX-Request@Mvb.Saic.Com at INTERNETc# Sent: Monday, July 22, 2002 8:27 PMaB To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET Subject: RE: CSA -> DSPP    : In article <0033000073419225000002L052*@MHS>, WILLIAM WEBB <WWEBB1@email.usps.gov> wrote:  E >=3D0ASo did you drop the webminions an email asking them to do this?l  D _I_ did.  It's supposedly being worked.  I've learned not to hold my8 breath when webminions (and other minions) are involved.  E But it would have been so much more satisfying to whine here instead.i   Sigh.r     >i
 ><conspiracy>t >t? >http://h21007.www2.hp.com/partner/technologies/1,2610,,00.html  >i! >contains NOTHING about OpenVMS.=,   ------------------------------  % Date: Tue, 23 Jul 2002 23:08:22 -0400 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: CSA -> DSPPK Message-ID: <rdeininger-2307022308230001@1cust208.tnt2.nashua.nh.da.uu.net>   : In article <0033000073644743000002L032*@MHS>, WILLIAM WEBB <WWEBB1@email.usps.gov> wrote:  4 >=0APerhaps you should adjust your targeting upward.  ( That would be possible, but just barely.   ------------------------------    Date: 23 Jul 2002 18:24:33 -0700# From: tadamsmar@aol.com (Tom Adams)o. Subject: Re: Cygwin/xfree86 and VMS/DecWindows= Message-ID: <793af3df.0207231724.4cb7a40a@posting.google.com>   h tadamsmar@aol.com (Tom Adams) wrote in message news:<793af3df.0207221111.6a33c37b@posting.google.com>...S > david20@alpha2.mdx.ac.uk wrote in message news:<ahh3qm$e56$1@aquila.mdx.ac.uk>... g > > In article <793af3df.0207220403.7bc1238d@posting.google.com>, tadamsmar@aol.com (Tom Adams) writes:a > > >Jordi Guillaumes i Pons <jguilla-at-attglobal-dot-net@nospam.please> wrote in message news:<3D387A58.2030004@nospam.please>...  > > >> Tom Adams wrote:mM > > >> 3) In the other, telnet to your VMS machine. Now you have two chances:o > > >> c> > > >> a) Do a SET DISPLAY/CREATE/NODE=yourpcname/TRANSP=tcpipK > > >> b) $ CREATE/TERMINAL/DETACH at your discretion, or MCR DECW$VUE, or  3 > > >> whatever Decwindows program you want to run.g > > >> j > > >> -OR-a > > >> a( > > >> a) Login to the VMS box as SYSTEM= > > >> b) $SET DISPLAY/CREATE/NODE=yourpcname/TRANSPORT=tcpipv > > >> c) $ MCR DECW$STARTLOGINt > > >>   > > >/J > > >Thank you, dear wizard. I had overlooked the TRAN qualifier during my4 > > >own perusal of the tomes, leaving me befuddled. > > >mI > > >But isn't an advance offering required so that the system will deign K > > >to recognize the node's name "youpcname" when it arrives at the gates.YH > > > If I am not mistaken, I was told it in response to the chant "HELPK > > >SET DISPLAY".  But, it was in a language that I little comprehend, and*K > > >I did not understand how to cast the spell that causes the node's name G > > >to materialize in some network database on my VMS system.  The our,& > > >local wizard says that NCP is not+ > > >involved, since it only covers DECnet.  > > >f > > Q > > Since your using TCPIP translating the "yourpcname" to the correct IP addressb? > > is handled as always by either DNS or the local hosts file.  > > K > > If the VMS system is setup to use DNS and "yourpc.domain" is setup in a-P > > properly configured accessible DNS server somewhere on the internet then you > > are all set.M > > If not then you need to get "yourpc.domain" set up in the local host file.L > > on the VMS system. With DEC TCPIP Services / UCX  this is done using the/ > > UCX set host/address=x.x.x.x yourpc.domain e > > command. > > Q > > This should probably be enough to get it working with most PC based X-serverseO > > since they generally come with no security restrictions restricting who can O > > connect. Most/all do though come with the ability to close down this gapingtQ > > security hole - but you'll need to see the documentation for the PCs X serverr > > package. > >  rN > > VMS workstations in contrast default to not allowiung any remote X windows7 > > connections - you have to specifically enable them.f > >a > ' > I get a "can't open display message".o > O > I can ping the PC by name, so the PC is not locking me completely out.  ThereoI > is no obvious firewall on the PC.  There could be some sort of firewalleL > between the PC and the VMS system (this is within the U.S. EPA and I thinkG > they have relatively good security), but I doubt it since ping works.m > & > I can telnet to the VMS system fine. > I > That "-ac" switch on the XWin command seems odd. I don't find it in then7 > documentation that I have seen, but it seems to work.C > ; > I could not issue "xwin -ac" directly without some setup.e > L > I revised a copy of the default startwin.bat that came with cygwin. in theI > x11 bin directory.  It said "start xwin" which I revised to "xwin -ac".  > : > Otherwise, I just installed/ran CYWIN as is, no changes. >  > What does "-ac" do?= > K > The XFree86 user manual on the web, seems to go in a different direction,E > taking about XDMCP.t >   E Anyone have any ideas why I am getting a "can't open display message" : when I try to run a client on the VMS system?  (See above)   > >  > >  > > David Webb > > VMS and Unix team leader > > CCSS > > Middlesex University   ------------------------------  % Date: Tue, 23 Jul 2002 17:37:36 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> D Subject: Re: different behavior of a C++ binary in different machine, Message-ID: <3D3DCC9D.FC97DC20@videotron.ca>   wing wrote:E >  > Hi,t > D > I have a binary executables which is well tested in my developmentF > machine, but when I deliver to clients, the binary encounters error.  M Beware of assumption of order of incoming messages from external sources such-K as DECNET or TCPIP etc. For instance, on a microvaxII, I would always get a K DECNET-open, DECNET-DATA and then DECNET-CLOSE messages in that order. At ai@ customer, the DECNET-DATA sometimes came after the DECNET-CLOSE.  M (eg: remote program opens link to server, sends a transaction packet and thenf closes the link).f  F Originally, upon reception of the DECNET-CLOSE, I would deallocate theN structures and consider the transaction done, so I had to add code to postpone= that task until after a transation is received and processed._   ------------------------------  % Date: Tue, 23 Jul 2002 18:57:32 -0700h0 From: Mark Berryman <Mark.Berryman@Mvb.Saic.Com>D Subject: Re: different behavior of a C++ binary in different machine, Message-ID: <3D3DA71C.6C8C3D4B@Mvb.Saic.Com>   Paul Winalski wrote: > A > On 22 Jul 2002 20:45:58 -0700, wingwong@witty.com (wing) wrote:i > E > >Is there any chance that a binary behaves differently in differentc2 > >machine?  If so, any precautions to avoid this? > D > Another one I forgot to mention that can crop up on Alpha systems: > F > There have been extensions to the Alpha architecture over the years.> > For example, starting with the EV56, Alpha has byte and wordF > instructions.  If you compiled your application to make use of theseD > instructions, the executable might not work properly on EV4 or EV5
 > systems. >   A Um, we are talking VMS here.  VMS has always striven very hard totF present a consistent view of its platform's instruction set regardlessA of which member of a particular platform the code was built on orh executed on.  H For example, there are optional instructions and instruction sets in theD VAX platform - i.e. some VAXes have instructions that others don't. F However, any program compiled under VMS on any VAX could run under VMS? on any other VAX.  If the executing VAX didn't happen to have a H particular instruction (Decimal arithmetic, for example) the instruction% was trapped and emulated in software.i  F The same is true for Alpha.  Some Alphas have instructions that othersG don't.  However, a VMS image from one Alpha will still run on any other-G Alpha running VMS.  Missing instructions are still trapped and emulated  in software.  
 Mark Berryman" Mark.Berryman@Mvb.Saic.Com   ------------------------------  % Date: Tue, 23 Jul 2002 22:43:10 -0400c- From: JF Mezei <jfmezei.spamnot@videotron.ca> D Subject: Re: different behavior of a C++ binary in different machine, Message-ID: <3D3E1428.45324C1E@videotron.ca>   Mark Berryman wrote:H > The same is true for Alpha.  Some Alphas have instructions that othersI > don't.  However, a VMS image from one Alpha will still run on any otheraI > Alpha running VMS.  Missing instructions are still trapped and emulated  > in software.  N Wasn't there some fairly major change with EV6 which required some programs toN be recompiled with a newer compiler otherwise there would be problems with theG executable on the newer platform ? (something about alignment I think).\   ------------------------------   Date: 24 Jul 2002 05:48:06 GMT- From: djweath@attglobal.net (Dave Weatherall)eD Subject: Re: different behavior of a C++ binary in different machine5 Message-ID: <DTiotGxQ0bj6-pn2-WSq53bNB3hjw@localhost>   A On Tue, 23 Jul 2002 06:10:54 UTC, Dirk Munk <munk@home.nl> wrote:/  
 > wing wrote:a > > Hi,i ...r  F > > Is there any chance that a binary behaves differently in different3 > > machine?  If so, any precautions to avoid this?  > O > Did you check if those machines have the latest real time libraries loaded ? lD > Otherwise your executable will not run (library version mismatch). >  >  >  > > I > > The compile I am using is Compaq C++ V6.3-020 for OpenVMS Alpha V7.3 " > >   4 I agree with Dirk. The RTL's are the probable cause.  E I had the very same situation with a Fortran program some years ago.  D The Q/A'ed version worked perfectly happily on our main machine but F failed on another in a neighbouring cluster. The cause was the FortranE RTL. It had a bug in the routine that supported the Z format on READ C1 and WRITE statements. DEC had a patch kit for it.    D OTOH the cause can still be in the code but triggered by changes in D the RTL. In all cases, it points to something in a RTL routine. The D error message/register dump should give a us clue. Please post them.   -- S Cheers - Dave.   ------------------------------  # Date: Wed, 24 Jul 2002 01:47:22 GMT*. From: Keith Brown <kbrown2720@NOSPAMattbi.com>/ Subject: DiskXcel vs OpenVMS 7.3 read cacheing? / Message-ID: <KGn%8.621829$352.132778@sccrnsc02>*   Hi all,*  C I would like to solicit opinions  on which read caching product is eJ preferred by this group for OpenVMS Alpha systems. I have an I/O bottle I I am trying to cure (read performance). I'm currently running V7.2-1 on an  H ES40 with 4GB ram and dual HSZ70's with 64MB writeback cache.  Should I K upgrade to V7.3-1 and hope that helps or purchase a 3rd party product like S7 DiskXcel from Networking Dynamics, I/O Express, others?o  J Is it true that 7.3 still does file caching like 6.1 or 6.2 or does it do I block based caching? Any experience on how much improvement I can expect eL from 7.3. How large can the cached files be? The data files I need to cache J are 600MB in size and about will range from 80 to 100 in number. Some are  obviously hotter than others.e   Thanks in advance. Keithg   ------------------------------  % Date: Tue, 23 Jul 2002 23:15:26 -0400 2 From: rdeininger@mindspring.com (Robert Deininger)3 Subject: Re: DiskXcel vs OpenVMS 7.3 read cacheing?aK Message-ID: <rdeininger-2307022315260001@1cust208.tnt2.nashua.nh.da.uu.net>   J In article <KGn%8.621829$352.132778@sccrnsc02>, kbrown2720@NOSPAMattbi.com wrote:   >Hi all, > D >I would like to solicit opinions  on which read caching product is K >preferred by this group for OpenVMS Alpha systems. I have an I/O bottle I  J >am trying to cure (read performance). I'm currently running V7.2-1 on an I >ES40 with 4GB ram and dual HSZ70's with 64MB writeback cache.  Should I UL >upgrade to V7.3-1 and hope that helps or purchase a 3rd party product like 8 >DiskXcel from Networking Dynamics, I/O Express, others? >0K >Is it true that 7.3 still does file caching like 6.1 or 6.2 or does it do lJ >block based caching? Any experience on how much improvement I can expect M >from 7.3. How large can the cached files be? The data files I need to cache  K >are 600MB in size and about will range from 80 to 100 in number. Some are   >obviously hotter than others.  I I think you should at least try VMS V7.3-1 (when it ships).  There aren'tGE enough details here about your workload to make precise predictions.  B V7.3-1 has various other performance improvements besides caching.  F How much of your 4 GB of memory is available for caching?  Can you Buy% More Memory (tm) if that's indicated?   H XFC in VMS 7.3 and later can devote LOTS of memory to file caching.  HowH much good it does obviously depends on the cache hit rate, which depends on the workload.  L From the limited results I have seen from XFC, it does way better than VIOC.  > I'm not familiar with any of the other products you mentioned.   ------------------------------  % Date: Tue, 23 Jul 2002 22:25:14 -0400 2 From: "warren sander" <sander.ma.ultranet@rcn.com>= Subject: Re: Excellent Commerzbank OpenVMS public testimonial + Message-ID: <ahl38k$1qt$1@bob.news.rcn.net>   J I'm still waiting to get the official version from the vendor.. Then I get& to make it into html and pretty it up.   -warren    --B ------------------------------------------------------------------9 Warren Sander                           OpenVMS Marketing B Hewlett-Packard Company         Work:  warren.sander@remove.hp.comG 200 Forest Street MR01-3/J1     Personal: sander@remove.ma.ultranet.com 3 Marlboro, MA 01752                   (508) 467-4875 5    My opinions are my own and I only speak for myself*,          Read http://www.openvms.compaq.com/B ------------------------------------------------------------------7 "WILLIAM WEBB" <WWEBB1@email.usps.gov> wrote in message ' news:0033000073084675000002L052*@MHS...    Ed-    Warren's not *that* fast.D  - The article to which you refer is dated 1999.   & They seem to have upgraded since then-  ( This one is dated July 2002 and entitled   "hp AlphaServer technology helps Commerzbank tolerate disaster on 9/11"   3 OpenVMS and GS160s are mentioned on the front page.y  0 "Because of the intense heat in our data center,7 all systems crashed except for our AlphaServer GS160...i1 OpenVMS wide-area clustering and volume-shadowing=2 technology kept our primary system running off the) drives at our remote site 30 miles away."-  / It's everything you'd want to see in an OpenVMSm promotional piece.  ' Kudos to whoever put this one together.C   (Hurry up, Warren!)g   WWWebb   -----Original Message-----/ From: Info-VAX-Request@Mvb.Saic.Com at INTERNETg% Sent: Thursday, July 18, 2002 4:10 PMoB To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET= Subject: RE: Excellent Commerzbank OpenVMS public testimonial     E Interestingly enough the Compaq Success Stories web site reports that,4 Commerzbank is using Tru64 for its database servers.   Full story is at:;I <http://www.success-stories.compaq.com/cgi-bin/cssextusr/s=display/i=438>i  # Here's an excerpt from the article.l What makes it work:i	 Products:w? Two AlphaServerTM 8400 systems running Tru64TM UNIX with Compaqe' StorageWorksTM, and an Oracle8 databaset2 An AlphaServerTM 4100 as a standby recovery system   EdE **Please apply a generous amount of all the usual disclaimers here.**o     > -----Original Message-----6 > From: rob@netcarrier.net [mailto:rob@netcarrier.net]' > Sent: Thursday, July 18, 2002 2:51 PM  > To: Info-VAX@Mvb.Saic.Com,? > Subject: Re: Excellent Commerzbank OpenVMS public testimonial5 >V >E >A7 > "Bob Ceculski" <bob@instantwhip.com> wrote in message 9 > news:d7791aa1.0207181124.4bb916b4@posting.google.com...aD > > "Sue Skonetski" <susan.skonetski@hp.nospam.com> wrote in message( > news:<ah6i8h$51l$1@web1.cup.hp.com>... > > > Dear Newsgroup,5 > > >c >,E > > hear that Andrew, all with 4 alphas with a few chips each and thepF > > best clustering around ... with any other platform the above wouldE > > be impossible ... that's why I always say, an app is only as good0D > > as the os it runs on ... if your os is down, so is your app, andC > > so are you, and so is your profits, and so is your stock price!  >P >a= >      mmmmm Really seems to have helped Digital and Compaq'aO > stock  ......... >r >=   ------------------------------  % Date: Tue, 23 Jul 2002 13:29:41 -07007' From: David Mathog <mathog@caltech.edu>fJ Subject: Re: How to create a shareable image from an object library (long)+ Message-ID: <3D3DBCB5.33CEE1E8@caltech.edu>    James Gessling wrote:r  @ > The trick to making the shareable image is to create an option7 > file with all the entry points.  This is pretty easy.v   Well, usually.  See:  F   ftp://saf.bio.caltech.edu/pub/software/openvms/make_opt_from_olb.com  ; I've run into cases (for instance, Xforms) where there werei@ global variables in the library which the SYMBOLS program didn't< catch.  At link time there'd be all sorts of unresolved bits; which had to be manually edited into the .opt file.  Still, 2 the procedure (actually, SYMBOLS) does most of it.   Regards,   David Mathog mathog@caltech.edu   ------------------------------  # Date: Tue, 23 Jul 2002 20:22:00 GMTu1 From: "David J. Dachtera" <djesys.nospam@fsi.net>HJ Subject: Re: How to create a shareable image from an object library (long)' Message-ID: <3D3DBF6A.8F41499A@fsi.net>d   James Gessling wrote:r > 7 > I had occasion to do this, so thought I'd share.  The8* > object library is libcurl available from6 > http://curl.haxx.se/libcurl/ This library allows you3 > to write programs to do various things that a webg> > browser would do.  We use it for programmicaly communicatingB > to web servers with HTTP post and get, but it can do a lot more. > B > The provided build script makes a libcurl.olb which provides the6 > curl_ routines that are called from the application.@ > I could have linked each application against this library, but: > since the plan was to have several processes running the@ > application at the same time, it made sense to use a shareable > image to reduce memory usage.e > @ > The trick to making the shareable image is to create an option7 > file with all the entry points.  This is pretty easy.N > 8 > First list all the entry points in the object library. > . > $ library/list=libcurl.opt/names libcurl.olb > < > In libcurl.opt, you will see a header and then lines like: >  > Module BASE64S >  > CURL_BASE64_DECODE > CURL_BASE64_ENCODE >  > Module CONNECT >  > CURL_CONNECTHOST > CURL_NONBLOCKt > B > There's more than this, but this will do for an example. In yourF > favorite editor, remove all the blank lines and those lines starting% > with "Module", this now looks like:  >  > CURL_BASE64_DECODE > CURL_BASE64_ENCODE > CURL_CONNECTHOST > CURL_NONBLOCKy > = > To make these into procedure entries for the symbol_vector,n. > use a learn sequence to make them look like: > ! > CURL_BASE64_DECODE=PROCEDURE, -n! > CURL_BASE64_ENCODE=PROCEDURE, -* > CURL_CONNECTHOST=PROCEDURE, -o > CURL_NONBLOCK=PROCEDURE, - > @ > This library was built from C code using /names=uppercase (theA > default).  I like to provide upper and lower case entry points,vC > especially if a shareable is to be used from different languages.i: > So I added an lower case alias to each entry, like this: > ! > CURL_BASE64_DECODE=PROCEDURE, -r4 > curl_base64_decode/CURL_BASE64_DECODE=PROCEDURE, -! > CURL_BASE64_ENCODE=PROCEDURE, -p4 > curl_base64_encode/CURL_BASE64_ENCODE=PROCEDURE, - > CURL_CONNECTHOST=PROCEDURE, -e0 > curl_connecthost/CURL_CONNECTHOST=PROCEDURE, - > CURL_NONBLOCK=PROCEDURE, -* > curl_nonblock/CURL_NONBLOCK=PROCEDURE, - > 7 > (good time to learn how to do learn sequences in EVE)uA > Add the top and bottom sections to make it a real options file,m > note removal of last comma.b >  > case_sensitive=YES > GSMATCH=LEQUAL,1,1000  > SYMBOL_VECTOR=( - ! > CURL_BASE64_DECODE=PROCEDURE, -y4 > curl_base64_decode/CURL_BASE64_DECODE=PROCEDURE, -! > CURL_BASE64_ENCODE=PROCEDURE, - 4 > curl_base64_encode/CURL_BASE64_ENCODE=PROCEDURE, - > CURL_CONNECTHOST=PROCEDURE, -n0 > curl_connecthost/CURL_CONNECTHOST=PROCEDURE, - > CURL_NONBLOCK=PROCEDURE, -) > curl_nonblock/CURL_NONBLOCK=PROCEDURE -s > )  > case_sensitive=NOe > & > Now create your shareable like this: > - > $ link/share=libcurl.exe libcurl.olb/lib, -  >         libcurl.opt/option, - 6 >         [--.OPENSSL-0_9_6D.AXP.EXE.SSL]libssl/lib ,-9 >         [--.OPENSSL-0_9_6D.AXP.EXE.CRYPTO]libcrypto/lib  > 2 > Needed those other two libraries to support SSL. > . > To link an application using this shareable. > ( > $ define libcurl disk:[dir]libcurl.exe+ > $ link /exe=app.exe app.obj,sys$input/opt  >           libcurl/shareX > 8 > At runtime be sure the definition of libcurl points to; > the shareable library so the image activator can find it. < > As a side benefit linking against the shareable versus the9 > object library is significantly faster, this can make a $ > real difference in large projects.  4 Could be done fully automated with minimal DCL code:  + 1. LIBR/OBJ/LIST=outfle object_library_namen  + 2. Open the options file ("optfle") /WRITE.e,    WRITE out the leading options statements.  7 3. Open "outfle", READ past the header text, then loop:h  # 4. Read each input record into VBL.      Construct the output like so::    WRITE optfle F$EDIT( VBL, "LOWERCASE" ), "/", VBL, ",-"7    (except leave the comma off the last output record).S  
 5. At EOF:     WRITE the last output record.)    WRITE the trailing options statements.7     Close input and output files.  # Execute the LINK command as needed.d   -- t David J. Dachterab dba DJE Systemst http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/n   ------------------------------    Date: 23 Jul 2002 13:43:40 -0700( From: bob@instantwhip.com (Bob Ceculski)9 Subject: Re: HP "OpenVMS Path to Itanium" Roadshow report = Message-ID: <d7791aa1.0207231243.1defde2e@posting.google.com>o  _ WILLIAM WEBB <WWEBB1@email.usps.gov> wrote in message news:<0033000073587041000002L012*@MHS>...m1 > The person making the presentation said that itD >   was a recent decision. > 7 >   This decision was mentioned in the context of beinge: >   a direct contrast to the strategic decision made three7 >   years ago to (only?) promote VMS in specific marketl* >   segments like telecom and health care. > 
 >   WWWebb >   : and that was confirmed to me recently by Rich Marcello ...   ------------------------------  % Date: Tue, 23 Jul 2002 17:17:54 -0400,* From: WILLIAM WEBB <WWEBB1@email.usps.gov>9 Subject: RE: HP "OpenVMS Path to Itanium" Roadshow reportb- Message-ID: <0033000073670517000002L072*@MHS>e  % =0AI have heard it aptly described as>  "the shackles have been loosed".   Is that good enough?   WWWebb   -----Original Message-----/ From: Info-VAX-Request@Mvb.Saic.Com at INTERNETd$ Sent: Tuesday, July 23, 2002 4:59 PMB To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET9 Subject: RE: HP "OpenVMS Path to Itanium" Roadshow reporta    5 WILLIAM WEBB <WWEBB1@email.usps.gov> wrote in message.H news:<0033000073587041000002L012*@MHS>... > The person making the prese= ntationI said that it >   was a recent decision. >f7 >   This decision was mentioned in the context of beingp: >   a direct contrast to the strategic decision made three7 >   years ago to (only?) promote VMS in specific marketo* >   segments like telecom and health care. > 
 >   WWWebb >w  ; and that was confirmed to me recently by Rich Marcello ...=    ------------------------------  % Date: Tue, 23 Jul 2002 17:49:02 -0400n- From: JF Mezei <jfmezei.spamnot@videotron.ca>v9 Subject: Re: HP "OpenVMS Path to Itanium" Roadshow reportm, Message-ID: <3D3DCF4B.8459438D@videotron.ca>  9 > >   This decision was mentioned in the context of beingv< > >   a direct contrast to the strategic decision made three9 > >   years ago to (only?) promote VMS in specific market , > >   segments like telecom and health care.  O When will Stallard's infamous memo be covertly changed to reflect this change ?n   ------------------------------  # Date: Tue, 23 Jul 2002 23:26:17 GMTd1 From: "David J. Dachtera" <djesys.nospam@fsi.net>k9 Subject: Re: HP "OpenVMS Path to Itanium" Roadshow report ' Message-ID: <3D3DEA9E.EC7B42EF@fsi.net>r   WILLIAM WEBB wrote:p > $ > I have heard it aptly described as" > "the shackles have been loosed". >  > Is that good enough?  5 Rather depends who you heard it from, I should think.    > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNETo& > Sent: Tuesday, July 23, 2002 4:59 PMD > To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET; > Subject: RE: HP "OpenVMS Path to Itanium" Roadshow reports > 7 > WILLIAM WEBB <WWEBB1@email.usps.gov> wrote in message P > news:<0033000073587041000002L012*@MHS>... > The person making the presentation > said that it > >   was a recent decision. > >u9 > >   This decision was mentioned in the context of being < > >   a direct contrast to the strategic decision made three9 > >   years ago to (only?) promote VMS in specific marketb, > >   segments like telecom and health care. > >j > >   WWWebb > >l > < > and that was confirmed to me recently by Rich Marcello ...     -- o David J. Dachterae dba DJE Systemsr http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/p   ------------------------------    Date: 23 Jul 2002 19:39:34 -0700# From: dooleys@snowy.net.au (dooley)d- Subject: Re: HP Lan Console x Itanium servers(= Message-ID: <1ca82fc6.0207231839.725127c7@posting.google.com>   v Fabio Cardoso <fabiopenvms@yahoo.com.br> wrote in message news:<20020715161858.28800.qmail@web20209.mail.yahoo.com>... > Just imagining:  > 4 > As HP Itanium machines will run HP-UX and OpenVMS / > in the same box (I hope) , and to mantain the 6 > compatibility  of HP-UX environments, I imagine that6 > HP will develop a Lan Console for Itanium (for HP-UX6 > use). So, it could be used for OpenVMS machines too. > 7 > Anyone from the PA-RISC x Alpha x Itanium engineeringc! > here to answer my question ????e >  > 	 > Regardsh >  > FC l >  I'm just a customer but...  > At the recent DECUS in Sydney, system management presentations> indicated that HP Openview will be the network/datacentre tool= but will be "hardware vendor neutral", Compaq Insight Managerr> (which can already interface to openview network node manager)? will continue to be the management tool for Proliants and IA64,76 with agents for PCs and Alphas running VMS and Tru-64.1 New servers will have integrated "insight boards"e0 (with some very neat remote management features)  < So to maintain compatibility I would guess that the Insight 2 agents will be ported to HP-UX for running on IA64   Phil   ------------------------------    Date: 24 Jul 2002 01:06:26 +0800, From: Paul Repacholi <prep@prep.synonet.com>, Subject: Re: HSV , Snaps and older databases- Message-ID: <87vg76tlv1.fsf@prep.synonet.com>o  - young_r@encompasserve.org (Rob Young) writes:l  @ > 	While what you bring up is correct, I believe you would be in= > 	the same spot with HSJ/HSG.  The wrinkle is that you woulde> > 	probably always have situations where you have inconsistent; > 	views of volumes.  As a for instance (from EncompasserveeA > 	discussion a year or two ago), you could be in the middle of a ? > 	bucket split when backup occurs.  Something as simple as VMSn? > 	mail bucket splitting at the point in time that MAIL.MAI wasa= > 	backup scanned, you won't be getting a consistent restore..  ? With an HSJ, but not a HSG, you can shut down, and dismount thecD volume. This will flush out *everything* and then off-line the unit,F as per MSCP. That does not exist in SCSI. Also, the unit off-line is aB sequential command, everthing before must have completed before it0 starts, so the storage is in a consistant state.   -- i< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.p@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Tue, 23 Jul 2002 20:08:52 -0500p& From: jlsue <jlsuexxxz@screaminet.com>, Subject: Re: HSV , Snaps and older databases8 Message-ID: <potrjucoaht8vjp813mvjpdp71aaa1heeb@4ax.com>  D On 22 Jul 2002 12:18:31 -0600, young_r@encompasserve.org (Rob Young) wrote:  M >In article <ahhdsf$hb0$1@aquila.mdx.ac.uk>, david20@alpha1.mdx.ac.uk writes:wd >> In article <88WphCoBv34W@eisner.encompasserve.org>, young_r@encompasserve.org (Rob Young) writes:    O >> Sure for many purposes a less than perfect backup is "good enough". If thatsM1 >> the case then you can use backup/ign=interlocka >> tN >> However sometimes thats not good enough. Splitting shadowsets or mirrorsetsL >> isn't much better than backup/ign=interlock unless you have quiesced your >> applications. >> n >o: >	Right... and that is exactly what I am highlighting when >	I said at the outset:t >oC >	The issue of course is older database technology whereby you must08 >	quiesce the volume, "break off" a copy and back it up. >@< >	How do you do that with HSV?  You don't apparently (or you3 >	do it but it is unsupported as jlsue points out).t  E With HSV, there is no mirrorset to break out.  Snap and Snapclone arenC the only options - i.e., it's not a question of supporting it, it's-C just not possible (controller-based, anyway).  You quiesce the app,nD and then do the snap.  The act of quiescing should flush data caches for the app.     > > >	Put off?  Okay.  But I guess if something is 20 years old or@ >	older, it is safe to say it is heritage.  Anyhow, I was tryingH >	to highlight the fact that there are a number of database technologiesF >	that are older that don't have the luxury of being put in hot backupC >	mode whereby transactions are logged to archive logs, i.e. OracleWA >	and/or RDB and of course the language may be munged but you getL >	the point. >d  E If the app doesn't provide the ability to quiesce (and flush caches),eF then it must be shutdown so that the files will be closed and the data flushed to disk.  ) Not speaking for anyone, certainly not HPm- (get rid of the xxxz in my address to e-mail)    ------------------------------    Date: 23 Jul 2002 20:38:09 -0600+ From: young_r@encompasserve.org (Rob Young)e, Subject: Re: HSV , Snaps and older databases3 Message-ID: <OMSjYBrCYnSP@eisner.encompasserve.org>o  a In article <potrjucoaht8vjp813mvjpdp71aaa1heeb@4ax.com>, jlsue <jlsuexxxz@screaminet.com> writes:hF > On 22 Jul 2002 12:18:31 -0600, young_r@encompasserve.org (Rob Young) > wrote: > N >>In article <ahhdsf$hb0$1@aquila.mdx.ac.uk>, david20@alpha1.mdx.ac.uk writes:e >>> In article <88WphCoBv34W@eisner.encompasserve.org>, young_r@encompasserve.org (Rob Young) writes:l >  > P >>> Sure for many purposes a less than perfect backup is "good enough". If thats2 >>> the case then you can use backup/ign=interlock >>> O >>> However sometimes thats not good enough. Splitting shadowsets or mirrorsetsdM >>> isn't much better than backup/ign=interlock unless you have quiesced yourc >>> applications.d >>>  >>; >>	Right... and that is exactly what I am highlighting wheno >>	I said at the outset: >>D >>	The issue of course is older database technology whereby you must9 >>	quiesce the volume, "break off" a copy and back it up.y >>= >>	How do you do that with HSV?  You don't apparently (or you 4 >>	do it but it is unsupported as jlsue points out). > G > With HSV, there is no mirrorset to break out.  Snap and Snapclone aredE > the only options - i.e., it's not a question of supporting it, it's:E > just not possible (controller-based, anyway).  You quiesce the app,CF > and then do the snap.  The act of quiescing should flush data caches > for the app. >  >  >>? >>	Put off?  Okay.  But I guess if something is 20 years old ortA >>	older, it is safe to say it is heritage.  Anyhow, I was tryingNI >>	to highlight the fact that there are a number of database technologiescG >>	that are older that don't have the luxury of being put in hot backupmD >>	mode whereby transactions are logged to archive logs, i.e. OracleB >>	and/or RDB and of course the language may be munged but you get
 >>	the point., >> > G > If the app doesn't provide the ability to quiesce (and flush caches),aH > then it must be shutdown so that the files will be closed and the data > flushed to disk. >    	It does... Gee Whiz folks...a  c http://groups.google.com/groups?selm=Ebp3tbVW0SqY%40eisner.encompasserve.org&oe=UTF-8&output=gplaina  @ http://www.compaq.com/products/quickspecs/10432_na/10432_na.html  I Enterprise Volume Manager (EVM) is a web-enabled application program thatnJ enables users to create and execute jobs that use storage controller-based snapshots and clones.   A 	It doesn't appear that runs out of a VMS batch queue.  So if thee+ 	following line up (end-user requirements):t    2 			1)  No Volume Shadowing as HSV does not support 				mini-merge8 			2)  Heritage database product that requires quiescing& 				volumes and "break out" (or snap).2 			3)  EVM supported "clone" or "snapclone" method  > 	Seems 3) means there is an operator sitting there clicking on/ 	something and we all know how well that works.u   	What am I missing?-  I 	What is the best solution if a backup is being driven from VMS and 1) +  
 	2) are true?f     ---   B 	At least one other person seems to understand what I am asking...  m http://groups.google.com/groups?selm=aa5ec19e.0207221049.79ec63ee%40posting.google.com&oe=UTF-8&output=gplainu  ; Nice post.  I am in agreement and like wonderment with you.m  " I hope someone at HP is listening.   :) jck   ---u  1 	One more time from a slightly different angle...g 	 @ 	"How do you get a consistent copy of a database from VMS?  Keep? 	in mind this database must be quiesced and then a copy made of D 	that quiesced database.  How do you do that FROM VMS in a supported" 	manner if using HSV controllers?"  A 	How would I do it?  Using Volume Shadowing.  But then you may bei> 	at risk if you have a node crash and are in full merge during
 	prime time. p   	Thanks.   				Robi   ------------------------------    Date: 24 Jul 2002 01:13:41 +0800, From: Paul Repacholi <prep@prep.synonet.com>G Subject: Re: HSV snapshots vs. Spiralog ? (Was: CLI access to HSV's...)t- Message-ID: <87r8hutliz.fsf@prep.synonet.com>   A Jim.Johnson@software-exploration.nospam.com (Jim Johnson) writes:l  E > Unless you are saying that HSV disks become irretrievably corrupted F > in the event of a system crash (something that I cannot bring myself? > to believe), any and all caches held on any and all hosts are 
 > irrelevant.a  ( May... What is fsck used for? and when?   rF > The consistent view that I was referring to, and the only consistentA > view that matters if the previous paragraph is true, is the one @ > presented by the storage itself -- that certainly involves the@ > caches on the disk device, and probably involves caches on theD > controller.  It does NOT involve caches at any higher layer of the	 > system.n  G The consistant view may only exist on the user side of the kernel. ThatUH is the state you must preserve. There must be a mechinism that runs fromC userland to the metal to flush out ALL state, and totally serializecF everything. Note, that in a SAN, this means all the SAN is potentially involved in this.   B If some of your data is cached in the host when you perform a snapB and it does not get out first, you have corruped your data to some extent.,   -- U< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Tue, 23 Jul 2002 17:31:45 -0400r' From: "Main, Kerry" <Kerry.Main@hp.com>iG Subject: RE: HSV snapshots vs. Spiralog ? (Was: CLI access to HSV's...)OT Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF40266087C@kaoexc01.americas.cpqcorp.net>  
 G'day Jim,  D >>> any and all caches held on any and all hosts are irrelevant...>>  7 Would this not assume write through caches in the host?=  D What about write back host caches whereby the application thinks the@ update is complete, but it is actually in the host cache/memory?  F Perhaps I am old fashioned, but imho, the host server should always be in charge of data integrity.   :-)    RegardsP  
 Kerry Main Senior Consultanti Hewlett-Packard Canada! Consulting & Integration Services/ Voice: 613-592-4660o Fax   : 613-591-4477 Email: Kerry.Main@hp.com     -----Original Message-----I From: Jim Johnson [mailto:Jim.Johnson@software-exploration.nospam.com]=20. Sent: July 23, 2002 4:35 AM  To: Info-VAX@Mvb.Saic.Com G Subject: Re: HSV snapshots vs. Spiralog ? (Was: CLI access to HSV's...)l    F Unless you are saying that HSV disks become irretrievably corrupted inD the event of a system crash (something that I cannot bring myself toF believe), any and all caches held on any and all hosts are irrelevant.  D The consistent view that I was referring to, and the only consistent? view that matters if the previous paragraph is true, is the oneEH presented by the storage itself -- that certainly involves the caches onH the disk device, and probably involves caches on the controller. It does5 NOT involve caches at any higher layer of the system.D   Jim.  E On 23 Jul 2002 00:13:57 +0800, Paul Repacholi <prep@prep.synonet.com>u wrote:  B >Jim.Johnson@software-exploration.nospam.com (Jim Johnson) writes: >lH >> In the absence of losing the battery power, an HSV presents a disk=20H >> that is consistent with the I/Os done to it up to a specific point in  J >> time.  Ignore where it is getting that data -- be it from its cache,=20E >> the on-disk cache, or the oxide.  The point is that the HSV can=202H >> always, during operation, present a wholly consistent view of that=20 >> disk. >PE >But it does not. It is consistant from the other side of any host=20dH >caches and buffers, but not nessisarily when seen from just the HSV.=20H >And in fact, as we are talking SAN etc, possibly serveral host resident  C >caches.  Now even if we handwave and posit that they are c kept=20dH >consistant, there is no mechinism to keep them also consistant with the  J >HSV as well.  If we want to form as snapshot/clone that is consistant,=20I >then we MUST ensure that all updates have got to some reference point=20 7 >(that need not be the disk, it could be the controlleroC >cache) from all hosts. If one or more hold back data or, worse,=2070 >metadata, the base of the snap is inconsistant. >=20J >> It is therefore possible, reasonable, and probably required that any=20G >> snapshot facility operate against that presented view of the disk=20 H >> contents, rather than some lower (inconsistent) state of the data.=20H >> Doing so means that a snapshot operation will present a snapshot that  J >> matches the I/Os done to a disk up to a specific point in time. That=20J >> is sufficient for a consistent snapshot.  No host operations need be=20 >> involved. >IH >The problem is that the `presented' data is not what the ontrollers can  H >see. There is the caching and functional stuff that is in the hosts.=20H >That layer has to co-operate across all hosts, and with the controllers  - >to ensure that the base for a snap is valid.r >=20J >> Does it work this way?  I don't know, but I'd be willing to bet that=203 >> it either does, or it uses something very close.  >W >Close: dancing, artillary...m >t >e >--=20= >Paul Repacholi                               1 Crescent Rd.,a8 >+61 (08) 9257-1001                           Kalamunda.I >                                             West Australia 6076 Raw,=20hH >Cooked or Well-done, it's all half baked. EPIC, The Architecture of the  ) >future, always has been, always will be.    Jim Johnsonc Software Exploration, Ltd.) (remove '.nospam' from the reply address))   ------------------------------  % Date: Tue, 23 Jul 2002 20:08:43 -0500r& From: jlsue <jlsuexxxz@screaminet.com>G Subject: Re: HSV snapshots vs. Spiralog ? (Was: CLI access to HSV's...)-8 Message-ID: <j3trjucvso0q3tkp8c4g4vj26122ijr3pr@4ax.com>  F I think that much of this host-cache problem is fixed by the fact thatC the app is supposed to be quiesced before taking the snap.  In many F apps, this means shutting it down - which closes the files and flushes
 the cache.  E For others that support some internal "quiesce" command, you'd expectaB that the developers are intelligent enough to realize they need to, flush their caches as part of the quiescing.  E On 24 Jul 2002 01:13:41 +0800, Paul Repacholi <prep@prep.synonet.com>; wrote:  B >Jim.Johnson@software-exploration.nospam.com (Jim Johnson) writes: >oF >> Unless you are saying that HSV disks become irretrievably corruptedG >> in the event of a system crash (something that I cannot bring myself @ >> to believe), any and all caches held on any and all hosts are >> irrelevant. > ) >May... What is fsck used for? and when?   > G >> The consistent view that I was referring to, and the only consistent(B >> view that matters if the previous paragraph is true, is the oneA >> presented by the storage itself -- that certainly involves theiA >> caches on the disk device, and probably involves caches on therE >> controller.  It does NOT involve caches at any higher layer of thep
 >> system. >:H >The consistant view may only exist on the user side of the kernel. ThatI >is the state you must preserve. There must be a mechinism that runs fromcD >userland to the metal to flush out ALL state, and totally serializeG >everything. Note, that in a SAN, this means all the SAN is potentiallym >involved in this. >eC >If some of your data is cached in the host when you perform a snapaC >and it does not get out first, you have corruped your data to some  >extent.  ) Not speaking for anyone, certainly not HPt- (get rid of the xxxz in my address to e-mail)    ------------------------------    Date: 23 Jul 2002 13:11:30 -0600+ From: young_r@encompasserve.org (Rob Young)  Subject: Intel to smash AMDl3 Message-ID: <XJxgSrVADrVG@eisner.encompasserve.org>i  < 	Intel's strategy apears to be "gain market share in lieu of= 	profits."  With a surprising move up to 2.8 GHz and 3 GHz byeE 	September, AMD has nothing in response left.  AMD currently tops outoA 	at 1.8 GHz (their 2200+ XP part) which goes for $202.  With the  D 	upcoming 63% slice in Pentium 4 2.53 GHz prices (currently $597, a C 	63% price cut brings the 2.53 GHz part down to about $220), Intel tF 	puts a hurt on AMD.  The 2.53 GHz P4 significantly outperforms AMD's  	top speed part.  @ 	This move leaves AMD in a very bad spot over the next 6 months.B 	No compelling reason to buy an AMD part here on out (until HammerF 	of course).  However, Hammer boxes don't show up unti Q1 2003 missing> 	the very important back-to-school and holiday shopping cycle.  B 	With Hammer arriving Q1 2003, Intel will have effectively stuffedC 	the channel with low cost Pentium 4 leaving AMD in a "who cares??"eC 	marketing battle: Hammer versus Pentium 4.  Great Hammer part, but, 	little demand left.   				Robe   ------------------------------  % Date: Tue, 23 Jul 2002 17:46:48 -0400s- From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Re: Intel to smash AMDa, Message-ID: <3D3DCEC5.4EB6CFF7@videotron.ca>   Rob Young wrote: > E >         Intel's strategy apears to be "gain market share in lieu ofa >         profits."   . Wall Street won't tolerate this for very long.        3 > With a surprising move up to 2.8 GHz and 3 GHz byeN >         September, AMD has nothing in response left.  AMD currently tops outI >         at 1.8 GHz (their 2200+ XP part) which goes for $202.  With thepL >         upcoming 63% slice in Pentium 4 2.53 GHz prices (currently $597, aK >         63% price cut brings the 2.53 GHz part down to about $220), Intela >         puts a hurt on AMD.     N And every action that Intel takes to make its 8086 more competitive with AMD's$ offering will hurt IA64 just as bad.   ------------------------------    Date: 23 Jul 2002 12:47:47 -0700/ From: Brannon_Batson@yahoo.com (Brannon Batson)P4 Subject: Re: Itanic2 - the cHumPaq spin continues...= Message-ID: <4495ef1f.0207231147.5bffe808@posting.google.com>2  u "Bill Todd" <billtodd@metrocast.net> wrote in message news:<%Q6%8.279257$Im2.14362024@bin2.nnrp.aus1.giganews.com>...- > [snip]A > Now, it's your turn (and boy, do I have some good questions)...0 >  > - bill  0 Shoot away.  We'll see how many I can answer :-)   Brannon$ not speaking for Intel   ------------------------------  % Date: Tue, 23 Jul 2002 17:20:50 -0400s- From: JF Mezei <jfmezei.spamnot@videotron.ca>)4 Subject: Re: Itanic2 - the cHumPaq spin continues..., Message-ID: <3D3DC8B1.87AE2610@videotron.ca>  K You can have as much propaganda and performance number fudging as you wish.s  I But in the end, both Alpha and PA-RISC will eventually fade due to no newaL performance improvements and IA64 will become HP's leading performance chip,J possibly used by other companies. Pointless to argue what Alpha could haveN been. We have to accept that IA64 will be HP's leading chip no matter what its performance is.   H Sun managed to be extremely succesful with a chip that wasn't as fast asJ Alpha, there is no intrinsic reason that HP couldn't succeed with a slowerD IA64 chip versus Power or whatever else exists in the server market.  L However, Winkler and Capellas' words may come back to haunt them. If WindowsM does concquer the server market, it is also likely that the 8086 architecture L will also concquer the IA64 one because what makes Wintel tick in the marketC is its use of commodity hardware. IA64 is far from being commodity.    ------------------------------  % Date: Tue, 23 Jul 2002 17:28:11 -0400	- From: JF Mezei <jfmezei.spamnot@videotron.ca>f4 Subject: Re: Itanic2 - the cHumPaq spin continues..., Message-ID: <3D3DCA69.6CCF9E3F@videotron.ca>   david20@alpha2.mdx.ac.uk wrote:t, > VMSs future is (currently) tied to Itanic.  M Currently, VMS' future is tied to Alpha. It won't be tied to IA64 for anotherpM few years. The period between the declaration of Alpha's murder and the firsthJ marketing of VMS on IA64 hardware (if such marketing ever materialises) isJ perhaps one of the most critical period in this sick/weak operating systemK that is now forced to survive through a very difficult void period, merger,-; new architecture that is still an unknown quantity etc etc.R   ------------------------------  % Date: Tue, 23 Jul 2002 14:27:05 -0400a- From: Jonathan Boswell <jsb@ost.cdrh.fda.gov>v( Subject: low-level formatting SCSI disks0 Message-ID: <3D3D9FF9.58ED5AFA@ost.cdrh.fda.gov>  N Is there a test 70 console command that I could use to low-level format a SCSIM disk on a VAXstation 4000/VLC, an AlphaStation 200, or an AlphaServer 2000 orp 2100?  Thanks in advance!v    - JBo   ------------------------------    Date: 24 Jul 2002 07:14:42 +0800, From: Paul Repacholi <prep@prep.synonet.com>, Subject: Re: low-level formatting SCSI disks- Message-ID: <87wurmrq8t.fsf@prep.synonet.com>e  / Jonathan Boswell <jsb@ost.cdrh.fda.gov> writes:r  B > Is there a test 70 console command that I could use to low-levelF > format a SCSI disk on a VAXstation 4000/VLC, an AlphaStation 200, or2 > an AlphaServer 2000 or 2100?  Thanks in advance!  % Yes, In fact I think it IS T70 or 72.r  < On the Alpha it is also in the SCSI test. Varies with model,< but a bit of a poke around with help etc should bring it to  life.a   -- H< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.i@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  # Date: Tue, 23 Jul 2002 20:06:54 GMTh1 From: "David J. Dachtera" <djesys.nospam@fsi.net> 2 Subject: Re: Mail degraded from VAX 6.2 to VAX 7.3' Message-ID: <3D3DBBE4.533C4A4E@fsi.net>y   Phillip Helbig wrote:  > O > > This last weekend, I upgraded my sole remaining VAXstation from 6.2 to 7.3.eI > > It is on this machine that I read my mail, including listservers liker
 > > Info-VAX.l > > O > > I noticed the following differences in DECWindows mail which I do not like.g > G > I'm not sure when the BLISS-to-C rewrite (why oh why?!?!) was done; IiJ > jumped from 5.5-2 to 7.1. This introduced so many bugs that MAIL/OLD wasC > introduced.  :-)  Perhaps you can get your DECwindows MAIL to run.I > MAIL_OLD.EXE instead of MAIL.EXE and see if the problem is still there.0  & DECwindows MAIL invokes DECW$MAIL.EXE.   --   David J. Dachtera. dba DJE Systemsk http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/t   ------------------------------    Date: 24 Jul 2002 01:29:10 +0800, From: Paul Repacholi <prep@prep.synonet.com>( Subject: Re: MV 3400 won't keep settings- Message-ID: <87n0sitkt5.fsf@prep.synonet.com>r  * Nic Clews <sendspamhere@127.0.0.1> writes:  B > As others have said, find yourself some tagged (sometimes calledD > industrial) NiCads and rebuild your own. Then you'll need 24 hoursC > of power. With the age of the machine, I have had to have some of C > these battery packs replaced in similar aged machines, so odds-on  > this is the problem.  C Specifically, you need 3 AAA NiCds. Many better battery places will E weld them into a pack for nix if you ask, as well as fit solder tags. @ *NEVER* solder directly onto the NiCds. The `bump' is a pressureD valve, and the heat will damage the rubber/plastic seal resulting inB loss of water, and that is why we are replacing the damm things to start with!   C This is one area where one size fits all. Well, except for the leaduE length, so you can have a could made up in one go if you have severalu	 machines.i   -- o< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.b@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------    Date: 23 Jul 2002 19:54:19 -0700# From: dooleys@snowy.net.au (dooley) 3 Subject: Re: Need 80' Fortran/VAX training materialo= Message-ID: <1ca82fc6.0207231854.2983ae2c@posting.google.com>a  \ Didier Morandi <Didier.Morandi@Free.fr> wrote in message news:<3D37DFDF.3D1A1D73@Free.fr>...O > I urgently need a copy of this two documents: Programming VAX/VMS in Fortran,yQ > student guide and teacher guide. The last edition was in two thick red binders.h > 7 > I _swear_ that I will send them back im-me-dia-te-ly.d >  > MANY thanks, >  > D.5 I have the "Utilizing VMS features from VAX fortran" d4 course (EY-3511E-MT) containing a 9-track tape and a- language workbook and a programming workbook.t/ Send the airfare and I will deliver!             Phil   ------------------------------    Date: 23 Jul 2002 13:44:42 -0700 From: ohm62@hotmail.com (OHM)dB Subject: P.Thread: setting RR scheduling policy on default thread?= Message-ID: <9d337b47.0207231244.27904c87@posting.google.com>t   Hello,  F I'd like to use the round robin scheduling policy for my POSIX threads based application...  D I could set it successfully for threads I create explicitely, using D the thread attributes along with pthread_attr_setschedpolicy() prior to pthread_create()i  B However the default thread desperately stays in throughput mode inC spite of all my attempts to turn it to RR;  Here's how I try to setr5 its scheduling policy before I create the other guys:i       int rs = 0;      int policy = 0; "     pthread_t id = pthread_self();      struct sched_param schedPrm;  @     // Set the round robin scheduling policy on the main thread.9     rs = pthread_getschedparam( id, &policy, &schedPrm );u     if ( ! rs ) {l         policy = SCHED_RR;<         rs = pthread_setschedparam( id, policy, &schedPrm );     }4  B This is using the standard PThreads calls (no draft 4), on OpenVMSE Alpha V7.2, V7.2-1, V7.2-2 and V7.3, all most recent O/S updates, RMS5A and PThreads patches applied where applicable, and the Compaq C++> V6.5-004 compiler...  B Side question: what are the implications of leaving that thread inE throughput mode, while the other threads are running on round robin? iB Namely about shared RMS file synchronous access, with multistreamsF (one stream per thread) open to a single file, and implicit RMS recordC level locking trusted for mutual exclusion on concurrently accesseddD records?  I am asking this as I get a deadlock once in a while, thatD looks like happening on concurrent access to the first record of the? file, despite my triple checks for explicit sys$release() where-	 needed...    Thanks & Regards,i  	   -- OHM.i   ------------------------------    Date: 23 Jul 2002 13:16:00 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)c) Subject: RE: Questions about license paksL3 Message-ID: <UXHDwvcGiwPb@eisner.encompasserve.org>t  _ In article <CIEJLCMNHNNDLLOOGNJIEEPNFGAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes:b  6 >>From: Larry Kilgallen [mailto:Kilgallen@SpamCop.net]  K >>Presuming you paid the $300 Transfer Fee to DEC/Compaq/HP (and if you diddL >>not, you have no license anyway), I think the only way you can make use ofM >>the license is to fix that AlphaServer 1000a.  One way to do that for those I >>of us who are not hardware-inclined is to buy another AlphaServer 1000asJ >>on eBay (without a license, and therefore cheaper, and without having toK >>pay a second $300 Transfer Fee).  Then swap parts in (like the backplane)m >>until the licensed one works.p > L > So it has to be the same exact type of system, not another workgroup class
 > machine?  D The procedure I describe involves no license transfer (once you haveD paid the original $300 fee to transfer the license with the originalB hardware).  Therefore notions of "workgroup class" are irrelevant.  F I propose you transfer parts from a good (but unlicensed) machine intoF the licensed machine until it works.  That works wherever you can findI parts that work.  I believe there is an AlphaServer (300?) whose hardwarei9 closely matches an AlphaStation 250, and that would work.   F The reason I suggested buying (a working instance of) exactly the sameG machine is to ensure the parts are interchangeable.  For people who are 3 experts with hardware, that caution need not apply.    ------------------------------  % Date: Tue, 23 Jul 2002 20:46:23 -0400 1 From: "Island (hpaq.net)" <dbturner@islandco.com>o) Subject: Re: Questions about license pakst/ Message-ID: <ujru46eiakf918@news.supernews.com>m  4 We have replacementAS1000a motherboards for $400 fyi     David,   -- Island Computers US Corp.t 2700 Gregory Streett Savannah GA 31404r Toll Free: 1-877 636 4332u International: 001 912 447 6622i  Facsimile:      001 912 201 0096 dbturner@hpaq.net2 www.hpaq.net; Stuart Johnson <ssj152 AT charter DOT net> wrote in message0) news:ujr0r4fkcguk0b@corp.supernews.com...oJ > I recently purchased a surplus AlphaServer 1000a that turned out to be aI > dud; it seems to have a short somewhere on the main board, rendering itt moreK > or less useless. It was supplied with the license pak's provided with then& > original sale of the machine by DEC. >  > Here are my questions: >dH > 1) Can I sell the license paks? I've seen licenses for sale on eBay. IK > remember that, in the "old" days at least, certain licenses could be soldsI > with a machine and others (layered products) coundn't. I haven't a cluei' > about selling the license paks alone.o >tI > 2) If it is OK to sell the licenses, does anyone have suggestions as to-J > their current value? Most of the paks I have are still sold by HPQ, many of > them for > $1,000. > < > I have the following paks (unless indicated, one of each): > < > QL-MT1AE-6R, OpenVMS-ALPHA, 15 units, activity A, no_shareC > QL-0LXAE-AA, UCX, 1050 units,, availability H, (mod_units, alpha)nH > QL-MTFAE-AA, DVNETEND, 1050 units,, availability H, (mod_units, alpha)H > QL-MV4AE-AA, DW-MOTIF, 1050 units,, availability H, (mod_units, alpha)I > QL-09MAE-AA, DCPS-PLUS, 1050 units,, availability H, (mod_units, alpha) H > QL-09KAE-AA, DCPS-OPEN, 1050 units, availability H, (mod_units, alpha)7 > QL-5LQAE-AA, ABS-OMT, 0 units, constant=100, no_share : > QL-5LSA9-3B, ABS-NT-CLIENT-USER, 100 units, constant=100A > QL-5M3AE-AA, VIEWPOINT-DC-V4.2, 0 units, constant=100, no_sharesF > QM-2CLAA-AB, PWLMXXXFP05.00, 100 units, constant=100 (2 each of this
 > license)F > QM-5LKAA-AB, PWXXWINAT07.00, 100 units, constant=100 (3 each of this
 > license) >aH > I will appreciate any advice offered regarding the legality of selling these  > items. >t
 > Regards, > Stuart Johnson? > ssj152 AT charter DOT net (demangling this should be obvious)r >: >  >m   ------------------------------    Date: 23 Jul 2002 19:36:07 -07001 From: nothome@spammers.are.scum (Malcolm Dunnett)i1 Subject: Raid Array 7000 firmware update question - Message-ID: <yoXSza1NiXFE@malvm7.mala.bc.ca.>e  +  I've just acquired a used Raid Array 7000.h  ,  It currently has HSOF 7.0 firmware on it, I) understand 7.3(?) is the current version.t  3  What are the implication of using the 7.0 firmwaren3  in a VMS cluster ( VMS 7.2-2, disk array on shared / SCSI bus with two hosts )? Alternately, what ise. the proper method of getting updated firmware?- Is it available for download or does one haveo to purchase it?l  0 The unit has dual controllers - do I need to buy+ two platform kits so that I can get two neww/ program cards ( I already have 2 program cards,h& but with the older firmware on them) ?  M =============================================================================tB Malcolm Dunnett      Malaspina University-College   Email: dunnettE                                                      Host: mala.bc.caoH Information Systems  Nanaimo, B.C. CANADA V9R 5S5     Tel: (250)740-6297   ------------------------------  # Date: Tue, 23 Jul 2002 23:00:27 GMTiL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr") Subject: re: RDB Questions8 Message-ID: <00A115EA.86DA8234@SSRL04.SLAC.STANFORD.EDU>   In article <20020723084440.5808.qmail@web21003.mail.yahoo.com>, =?iso-8859-1?q?Tadimeti=20Keshav?= <keshav_tadimeti@yahoo.co.uk> writes: >Hello all,a/ >I guess COBOL programs containing embedded SQLr6 >statements requires Oracle CDD without which it won't >compile. Is this correct? > 7 >Re: JCC's RDB list, I had set it to DIGEST. Ever sincet$ >I haven't been recieving any mails. >m4 >TDMS: Where can I find documents related to the now7 >discontinued TDMS? Does Anyone have any old documents?   I Really, don't get involved with TDMS if you don't have to.  If you reallyp need forms, how about DECForms?   G Are you on VAX or Alpha?  TDMS didn't even get ported to Alpha, and thep3 emulator (from PRAXA) isn't available to hobbyists.a   -- Alano  O ===============================================================================n0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056wM  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210eO ===============================================================================    ------------------------------  # Date: Tue, 23 Jul 2002 21:14:33 GMT ! From: rob.buxton@wcc.spam.govt.nze Subject: RZ40 Disk Problem% Message-ID: <3d3dc538.175178823@news>.  	 Hi Chaps,o  E I've had an RZ40-AS die on me. This was located inside an AlphaServer : 300. Running OpenVMS 7.2-2, plus most recent Level 1 ECOs.  , There's also a BA350 attched to this system.  A I've removed the dead RZ40-AS from inside and tried to install aneD RZ40-VA into the BA350. I got hold of two RZ40-VAs, one was meant to be a spare.8  , From >>>INIT it sees the disk as an RZ40-AS.D Could see it from VMS and, on the first attempt, actually managed toA Initialize it. Come the restore it drops of line. I Get an error:tD SYSTEM-F-DEVOFFLINE, device is not in configuration or not available  D At this point I'd successfully mounted the disk with and without the /foreign switch.  D I don't have the docs. on the BA350 or this system so I was guessing as to compatibility.  C So, can anyone confirm if the RZ40-VA is compatible within a BA350?-   Many thanks,   Rob.   ------------------------------  % Date: Tue, 23 Jul 2002 23:59:01 +0200B- From: Didier Morandi <Didier.Morandi@Free.fr>s& Subject: Re: Security Banner displayed& Message-ID: <3D3DD1A3.6DDD887@Free.fr>  L Afaik, Larry, most of the remaining VMS users around are still using VTs or E VTERM emulation on their PCs (well, this is my experience in France /pK Switzerland), and the good old username/password prompt. I also noticed the1M "icon" word and decided to think that the user is inexperimented and believesa; that all and every VMS system has a mouse driven interface.7   D.   Larry Kilgallen wrote: > Y > In article <3D3D55E7.4CA5ECBF@Free.fr>, Didier Morandi <Didier.Morandi@Free.fr> writes:pP > > What about a text in the ANNOUNCE.TXT if the given text is a "law" agreementF > > warning a user about his/her rights and obligations when login in? > J > I don't believe ANNOUNCE.TXT is reliably delivered for DECwindows login. > J > Use of the term "icon" in the original problem statement (below) made me4 > believe the requirement was for DECwindows logins. >  > > David Lee wrote: > >>N > >> Does anyone know how to display a "Warning Message Displayed" everytime aP > >> user log in to the computer.  The warning message probably a 100 words long > >> and* > >> has icon of "Agree" as a default item   ------------------------------  % Date: Tue, 23 Jul 2002 22:16:41 +0200a/ From: "Marc Van Dyck" <marc.vandyck@brutele.be>e  Subject: Re: security monitoring* Message-ID: <ahkdiu$pka$1@news.brutele.be>  8 "Chuck Aaron" <caaron@ceris.purdue.edu> wrote in message* news:3D3D6769.936AE418@ceris.purdue.edu... > Group, >mF > Can you share with me what software products you use to monitor yourF > VMS system and it's security? I am in touch with PointSecure now but > looking for alternatives.( >r	 > Thanks,  > Chuck.  I Digital once developped its own, named at that time DECinspect, and latertF renamed "polycenter security compliance manager". As a system manager,K I used it a lot (it was mandatory on all Digital own systems). It can stilli be: obtained from Touch Technologies Inc, see www.ttinet.com .   Marc.r   ------------------------------  % Date: Wed, 24 Jul 2002 11:18:33 +0800e) From: Kiasu Surfer <verykiasu@hotpop.com>i# Subject: Single Column text output?-8 Message-ID: <gn6sjug2aki5fplce93dqm5pr7tdm9liv8@4ax.com>  J I had a weird experience in spooling a log file from my DCL script calling Oracle scripts.I  @ When I use TYPE to list out, the spooled text displayed as norm.P But when I EDIT it, the visual display show the spooled text as single character in single column vertical down.i   Should be:-l+ ORACLE Server Manager... blah blah blah....v   In Edit mode:- O- R- A- C- L- E-  , Can someone help me to rectify this problem. Thanks.o Regards,  	 Kevin Laio   **************** ** SPAM BLOCK ** ****************? REPLACE "verykiasu" with "iamverykiasu" at verykiasu@hotpop.com@   ------------------------------  % Date: Tue, 23 Jul 2002 14:39:23 -0400o* From: WILLIAM WEBB <WWEBB1@email.usps.gov>D Subject: RE: Size of the comp.os.vms readership ? , was: RE: OpenVMS- Message-ID: <0033000073644491000002L012*@MHS>I   =0AThen the answer must be 42.  / I was speaking figuratively about the Internet,e3 not necessary about the membership of the newsgroupr and the mailing list.-  6 The matter remains that I tried calling Mr. Taylor and3 left a message stating that I was calling about theK OpenVMS webring.  8 No response so far.  Anybody who actually knows him care to give it a try?-   WWWebb   -----Original Message-----/ From: Info-VAX-Request@Mvb.Saic.Com at INTERNET $ Sent: Tuesday, July 23, 2002 2:18 PMB To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNETE Subject: Size of the comp.os.vms readership ? , was: RE: OpenVMS webro    H In article <BA52530E3149734A9BAABDBBFA808E4901479EF6@rlghncst964.usps.g= ov>,? "Webb, William W Raleigh, NC" <wwebb1@email.usps.gov> writes: > ( > Why is it that posting before millions$ > that you're having trouble finding- > something/someone is the final prerequisiteh > to finding something/someone?d >   H Millions ? Nice dream about the size of the online VMS user base, but I=  don't think so sadly... :-)   H I would be interested in guesses about the size of the comp.os.vms read= ershipH however. Obviously, with Usenet been Usenet, you can't put an accurate = figureH on the number of readers, but there are a couple of sources of informat= ion H to allow you to make a guess for the ratio between posters and people w= ho only read the group.  : 1) Mark Berryman knows how many are subscribed via E-Mail.  H 2) Large sites with local news servers will have statistics on how many=  H people access comp.os.vms and they will know how many of their collegue= sn actually post.  H So, does anybody want to have a go at estimating the size of the comp.o= s.vms  readership ?   Simon.   --; Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFPd, Microsoft: The Lada of the computing world.=   ------------------------------    Date: 23 Jul 2002 12:57:41 -0600B From: clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley)I Subject: Size of the comp.os.vms readership ? , was: RE: OpenVMS webring: 3 Message-ID: <sGcl+L3ba1Ax@eisner.encompasserve.org>f   In article <BA52530E3149734A9BAABDBBFA808E4901479EF6@rlghncst964.usps.gov>, "Webb, William W Raleigh, NC" <wwebb1@email.usps.gov> writes:  > ( > Why is it that posting before millions% > that you're having trouble finding  . > something/someone is the final prerequisite  > to finding something/someone?x >   M Millions ? Nice dream about the size of the online VMS user base, but I don'te think so sadly... :-)o  M I would be interested in guesses about the size of the comp.os.vms readership1M however. Obviously, with Usenet been Usenet, you can't put an accurate figure J on the number of readers, but there are a couple of sources of informationI to allow you to make a guess for the ratio between posters and people who- only read the group.  : 1) Mark Berryman knows how many are subscribed via E-Mail.  G 2) Large sites with local news servers will have statistics on how manysH people access comp.os.vms and they will know how many of their collegues actually post.  L So, does anybody want to have a go at estimating the size of the comp.os.vms readership ?   Simon.   -- sB Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP       + Microsoft: The Lada of the computing world.e   ------------------------------  % Date: Tue, 23 Jul 2002 17:22:57 -0400A' From: "Main, Kerry" <Kerry.Main@hp.com>nM Subject: RE: Size of the comp.os.vms readership ? , was: RE: OpenVMS webring:aT Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF40266087B@kaoexc01.americas.cpqcorp.net>   Simon,  > Boy, I was just thinking about this yesterday as well - what a co-incidence..=200  D Imho, comp.os.vms is one of the great aspects of OpenVMS i.e.. many,F many experienced vendor, system and application readers that typically? have multi-platform backgrounds and a great deal of experience.   ? Heck, even the competition feels a burning need to participate.o   :-)   * Also, looking forward to reader estimates.   Regards   
 Kerry Main Senior Consultantp Hewlett-Packard Canada! Consulting & Integration Services  Voice: 613-592-4660h Fax   : 613-591-4477 Email: Kerry.Main@hp.com     -----Original Message----- From: Simon ClubleyI8 [mailto:clubley@remove_me.eisner.decus.org-Earth.UFP]=20 Sent: July 23, 2002 2:58 PM  To: Info-VAX@Mvb.Saic.Com @ Subject: Size of the comp.os.vms readership ? , was: RE: OpenVMS webring:    
 In articleG <BA52530E3149734A9BAABDBBFA808E4901479EF6@rlghncst964.usps.gov>, "Webb, 6 William W Raleigh, NC" <wwebb1@email.usps.gov> writes: >=20( > Why is it that posting before millions$ > that you're having trouble finding0 > something/someone is the final prerequisite=20 > to finding something/someone?2 >=20  G Millions ? Nice dream about the size of the online VMS user base, but Is don'td think so sadly... :-)t  B I would be interested in guesses about the size of the comp.os.vms
 readershipF however. Obviously, with Usenet been Usenet, you can't put an accurate figure> on the number of readers, but there are a couple of sources of informationsE to allow you to make a guess for the ratio between posters and people  whod only read the group.  : 1) Mark Berryman knows how many are subscribed via E-Mail.  G 2) Large sites with local news servers will have statistics on how manyiH people access comp.os.vms and they will know how many of their collegues actually post.  @ So, does anybody want to have a go at estimating the size of the comp.os.vms- readership ?   Simon.   --=20eD Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP      =20+ Microsoft: The Lada of the computing world.p   ------------------------------  # Date: Wed, 24 Jul 2002 00:50:28 GMT<! From: rob.buxton@wcc.spam.govt.nzdM Subject: Re: Size of the comp.os.vms readership ? , was: RE: OpenVMS webring:i% Message-ID: <3d3df6a8.187835342@news>n  C comp.os.vms is certainly a very active newsgroup. Actual readershipoE would be difficult to quantify. I certainly agree with the quality off6 postings, but you do see the same, not so many, names.  D I know there's probably a lot like me who only access the news groupB say once a day and only contribute when there's an issue that they) believe they can offer something new on.      E On Tue, 23 Jul 2002 17:22:57 -0400, "Main, Kerry" <Kerry.Main@hp.com>n wrote:   >Simon,e >r? >Boy, I was just thinking about this yesterday as well - what ao >co-incidence..=20 > E >Imho, comp.os.vms is one of the great aspects of OpenVMS i.e.. many, G >many experienced vendor, system and application readers that typicallyg@ >have multi-platform backgrounds and a great deal of experience. >n@ >Heck, even the competition feels a burning need to participate. >n >:-) >h+ >Also, looking forward to reader estimates.s >e >Regards >  >Kerry Mainh >Senior Consultant >Hewlett-Packard Canada3" >Consulting & Integration Services >Voice: 613-592-4660 >Fax   : 613-591-4477  >Email: Kerry.Main@hp.comy >  >w >-----Original Message-----h >From: Simon Clubley9 >[mailto:clubley@remove_me.eisner.decus.org-Earth.UFP]=20  >Sent: July 23, 2002 2:58 PM >To: Info-VAX@Mvb.Saic.ComA >Subject: Size of the comp.os.vms readership ? , was: RE: OpenVMS0	 >webring:I >n >h >In articletH ><BA52530E3149734A9BAABDBBFA808E4901479EF6@rlghncst964.usps.gov>, "Webb,7 >William W Raleigh, NC" <wwebb1@email.usps.gov> writes:c >>=201) >> Why is it that posting before millions % >> that you're having trouble findingG1 >> something/someone is the final prerequisite=207  >> to finding something/someone? >>=202 > H >Millions ? Nice dream about the size of the online VMS user base, but I >don't >think so sadly... :-) >>C >I would be interested in guesses about the size of the comp.os.vmse >readershipsG >however. Obviously, with Usenet been Usenet, you can't put an accurateo >figureh? >on the number of readers, but there are a couple of sources ofs >informationF >to allow you to make a guess for the ratio between posters and people >who >only read the group.e >e; >1) Mark Berryman knows how many are subscribed via E-Mail.e >iH >2) Large sites with local news servers will have statistics on how manyI >people access comp.os.vms and they will know how many of their colleguest >actually post.v >tA >So, does anybody want to have a go at estimating the size of thei >comp.os.vms
 >readership ?e >n >Simon.  >g >--=20E >Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP      =20y, >Microsoft: The Lada of the computing world.   ------------------------------  + Date: Wed, 24 Jul 2002 04:18:30 +0100 (BST)VF From: =?iso-8859-1?q?Tadimeti=20Keshav?= <keshav_tadimeti@yahoo.co.uk>% Subject: TDMS (was re: RDB Questions) @ Message-ID: <20020724031830.67177.qmail@web21009.mail.yahoo.com>   HI4 WE are supporting an application that uses TDMS. Yes it runs on VAX.   6 So I really need to find documentation on TDMS. WE are3 willing to purchase old/used documentation from anyu one willing to sell.  
 --Keshav--  2 __________________________________________________ Do You Yahoo!?+ Everything you'll ever need on one web pagea- from News and Sport to Email and Music Chartst http://uk.my.yahoo.com   ------------------------------  # Date: Tue, 23 Jul 2002 21:24:39 GMTs0 From: rickm@oregon.uoregon.edu (Rick Millhollin)( Subject: Re: TSM and Newer Circuit Names1 Message-ID: <3d3dc865.271009300@news.uoregon.edu>g  2 On Tue, 23 Jul 2002 08:52:10 +0200, Karl Rohwedder, <extern.karl.rohwedder@volkswagen.de> wrote:  B >TSM can learn abount new hardware, if you a define a logical nameF >in LNM$SYSTEM, e.g. "TSM$SERVICE_CIRCUITS" [exec,no_alias] = "EZ/ISA" >...  E Cool!  One more (probably dumb) question.  Mine would then be definedaC as "ddd/EWA" but I can't figure out what the "ddd" device is for my  DEGPA GB enet adapter.  1 Rick Millhollin, Director of Computing Facilities @ University of Oregon Computing Center, Eugene, Oregon 97403-12120 Phone: (541)346-1730  FAX: (541)346-6438 or 4397C E-mail: rickm123@oregon456.uoregon789.edu (remove anti-spam digits)t   ------------------------------    Date: 24 Jul 2002 01:52:37 +0800, From: Paul Repacholi <prep@prep.synonet.com>1 Subject: Re: Upgrading from 7.2-1 and latest ECOso- Message-ID: <87it36tjq2.fsf@prep.synonet.com>t  D clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley) writes:  D > _If_ the above is correct, then I have got to ask once again, what7 > is going on with quality control in VMS Engineering ?l   Do you want fries with that?  E There used to be whole teams doing noting but testing and QC, both of F hardware and SW. But this is ineficient and a waste of executive pork, so they got `rationalized'.   I Another question would be Why, oh why, in the face of version numbers, domC patch kits re-name things to <mumble>-old rather than the canonicalr# way of just creating a new version?g   -- 0< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.9@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------    Date: 23 Jul 2002 14:20:31 -0600B From: clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley)1 Subject: Re: Upgrading from 7.2-1 and latest ECOso3 Message-ID: <Z8UlhzNbiwFU@eisner.encompasserve.org>   \ In article <87it36tjq2.fsf@prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:F > clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley) writes: > E >> _If_ the above is correct, then I have got to ask once again, what-8 >> is going on with quality control in VMS Engineering ? >  > Do you want fries with that? > G > There used to be whole teams doing noting but testing and QC, both of H > hardware and SW. But this is ineficient and a waste of executive pork, > so they got `rationalized'.A >   B So they got rid of one of the features that makes VMS be VMS ? :-(  K I was wondering if this was the case, and given that, I really hope that we2H are not going to be condemned to a future of Microsoft levels of quality as future work is done.D  E I wonder if the people in charge of the VMS Engineering purse stringsmK realise that one of the reasons that people (myself included) stay with VMSmH is that it has always been traditionally a rock-solid reliable operatingM system that we can _trust_ and that major quality control efforts are a majorn
 part of that.   E If quality control issues were to start becoming persistant, then thei= reasons for staying with VMS start to become less compelling.h   Simon.   -- aB Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP       + Microsoft: The Lada of the computing world.c   ------------------------------    Date: 23 Jul 2002 14:35:17 -0600+ From: young_r@encompasserve.org (Rob Young) 1 Subject: Re: Upgrading from 7.2-1 and latest ECOsA3 Message-ID: <xqBu6gAipoqg@eisner.encompasserve.org>l  \ In article <87it36tjq2.fsf@prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:F > clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley) writes: > E >> _If_ the above is correct, then I have got to ask once again, whatr8 >> is going on with quality control in VMS Engineering ? >  > Do you want fries with that? > G > There used to be whole teams doing noting but testing and QC, both of(H > hardware and SW. But this is ineficient and a waste of executive pork, > so they got `rationalized'.  > K > Another question would be Why, oh why, in the face of version numbers, dodE > patch kits re-name things to <mumble>-old rather than the canonical7% > way of just creating a new version?  >   = 	Because that nightly system disk purge that you have runningiF 	puts a damper on backing off.  Surely they received a ton of calls on2 	that one... and no, I am not one of the culprits.   				Robr   ------------------------------  % Date: Tue, 23 Jul 2002 19:35:54 +0000 2 From: John Eisenschmidt <jweisen@eisenschmidt.org>1 Subject: Re: Upgrading from 7.2-1 and latest ECOst3 Message-ID: <20020723193554.B3242@eisenschmidt.org>E  c Unless the Voices are Mistaken, Simon Clubley (clubley@remove_me.eisner.decus.org-Earth.UFP) Wrote:g^ > In article <87it36tjq2.fsf@prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:H > > clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley) writes: > > G > >> _If_ the above is correct, then I have got to ask once again, what : > >> is going on with quality control in VMS Engineering ? > >   > > Do you want fries with that? > > I > > There used to be whole teams doing noting but testing and QC, both of3J > > hardware and SW. But this is ineficient and a waste of executive pork, > > so they got `rationalized'.  > >  > D > So they got rid of one of the features that makes VMS be VMS ? :-( > M > I was wondering if this was the case, and given that, I really hope that wepJ > are not going to be condemned to a future of Microsoft levels of quality > as future work is done." > G > I wonder if the people in charge of the VMS Engineering purse stringssM > realise that one of the reasons that people (myself included) stay with VMStJ > is that it has always been traditionally a rock-solid reliable operatingO > system that we can _trust_ and that major quality control efforts are a majoru > part of that.  > G > If quality control issues were to start becoming persistant, then thee? > reasons for staying with VMS start to become less compelling.s  9After the set of ECOs broke my NIC duplex settings (which it was supposed to fix), and TCPIP being what it is, I just stopped patching. My systems are standalone, stable, sit behind a firewall, packet filters, and a three headed robot dog named Aibo. I just sort of live with it, not optimal but, what can you do?m   What pisses me off is that they're torquing the building down in September, which means all the power has to be off for 24 hours. There goes my uptime.u   >  > Simon. >  > --  D > Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP       - > Microsoft: The Lada of the computing world.>   -- c/ John W. Eisenschmidt <jweisen@eisenschmidt.org>:6  Homepage URL    | http://www.eisenschmidt.org/jweisenM  GPG Public Key  | http://www.eisenschmidt.org/jweisen/misc/jeisenschmidt.asc D  GPG Fingerprint | 5F9B F916 5AD1 3295 CF99 BC1E 1F97 E6A3 37E3 BEF2  O This mail is an attachment? Read http://www.jensbenecke.de/misc/outlook.en.htmla   ------------------------------  # Date: Tue, 23 Jul 2002 20:00:06 GMTs8 From: hammond@not@peek.ppb.cpqcorp.net (Charlie Hammond)1 Subject: Re: Upgrading from 7.2-1 and latest ECOs-2 Message-ID: <aBi%8.41$UO6.719978@news.cpqcorp.net>  . In article <87it36tjq2.fsf@prep.synonet.com>, . Paul Repacholi <prep@prep.synonet.com> writes:  J >Another question would be Why, oh why, in the face of version numbers, doD >patch kits re-name things to <mumble>-old rather than the canonical$ >way of just creating a new version?  C FIRST -- The PCSI utility deletes the old version before installingfC the new version.  There once was a /KEEP option on PRODUCT INSTALL,nD but it was dropped for whatever reason.  It could cause lots of disk@ space problems if /KEEP was used when installing large products.  H SECOND -- As someone else mentioned, multiple versions tend to disappearD when PURGEs are executed.  "_OLD" tends to be at least a little more robust in this respect.u   -- pG     Charlie Hammond -- Hewlett-Packard Company -- Pompano Beach  FL USAeH        (hammond@not@peek.ppb.cpqcorp.net -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------  # Date: Tue, 23 Jul 2002 21:22:30 GMTe. From: peter@langstoeger.at (Peter LANGSTOEGER)< Subject: Re: VMS Mail problems Internal/External receipient.4 Message-ID: <qOj%8.59300$Se4.1691801@news.chello.at>  b In article <3d3d776b$1@news.si.com>, "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:3 >>Can someone help me with this mail setup problem?i >sD >All Compaq TCP/IP SMTP problems can be fixed by downloading MX from >www.madgoat.com.2   I second that.  I And you are then even able to switch the IP stacks beneath to and/or from:N (eg. TCPware) without any required config changes (once configured of course)!8 btw DCPS solves the problem for the printer queues then.  6 I solved a lot of problems (speak crashes) this way...   -- b Peter "EPLAN" LANGSTOEGERw% Network and OpenVMS system specialisth E-mail  peter@langstoeger.atP A-1030 VIENNA  AUSTRIA              I'm looking for (a) Network _and_ VMS Job(s)   ------------------------------  % Date: Tue, 23 Jul 2002 13:01:25 -0700 * From: "Alder" <MUNDDGNTDYTV@spammotel.com>3 Subject: [Hobbyist] install of SQL/Services problemt) Message-ID: <3d3db66e@obsidian.gov.bc.ca>m  , This is a multi-part message in MIME format.  + ------=_NextPart_000_0011_01C23249.0CF0E330g Content-Type: text/plain;e 	charset="iso-8859-1"p+ Content-Transfer-Encoding: quoted-printable   = I'm installing the hobbyist version of Rdb and SQL/Services =rG (multiversion), and have run up against a problem.  It seems that the =iF Installation Verification Procedure for SQL/Services cannot find the =I GENERIC service.  At least that is my interpretation of the output from =eD the installation procedure.  The output is the result of my second =F attempt; messages referring to existing registry entries refer to my =! first attempt to install the kit.u  @ Can someone possibly offer some sage advice on how to get this =@ successfully installed?  Here is a portion of the installation =E procedure's output along with the output of SHOW SYSTEM immediately =  following the IVP's completion:    Thanks,e Alderb  J -------------------------------------------------------------------------= ---cE %REGISTER-I-DUP SQLSRV_PRVSHR70, (SQLSRV_PRVSHR, V7.0-6) already in =w registry< %REGISTER-I-SUMMARY  images examined: 1, dependent images: 1 =20eA     *************************************************************l =20o9     Please refer to the Oracle SQL/Services release notesn4     for specific instructions for setting up SQL*Net9     configuration files for use with Oracle SQL/Services.o =20kA     *************************************************************C =20tA %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target =o directories... =20a  Starting Oracle SQL/Services. =20@% Installing Oracle SQL/Services images E %REGISTER-I-DUP SQLSRV_PRVSHR70, (SQLSRV_PRVSHR, V7.0-6) already in =U registry< %REGISTER-I-SUMMARY  images examined: 1, dependent images: 1 Starting Oracle SQL/Services SQLSRV> Server started =20 *  Now executing the Oracle SQL/Services IVP =20B   Starting the TCP/IP test.. =20g) ***** Connecting to generic service *****1 =20l) ***** Oracle SQL/Services IVP Error *****p =20g1 SQLCA: SQLCODE: -2051  SQLERRD[0]: 0 SQLERRD[2] 0iD SQLERRM.SQLERRMC -SQLSRV-E-SVCNOTRUN, The requested service is not =
 running or is2  not defined =20?H *** Oracle SQL/Services IVP failed when accessing the  generic service = ***o( %NONAME-E-NOMSG, Message number 00000002 =20s3    **** Oracle SQL/Services client test failed ****e =20O =20s9  Now executing the following command to verify the Oracleu
  RMU service:e =20r)    RMU/EXECUTE/COMMAND "RMU/SHOW VERSION"f =20o0 %DCL-W-ACTIMAGE, error activating image RDMPRV70 -CLI-E-IMGNAME, image file =2 HOBBY$DKA0:[SYS0.SYSCOMMON.][SYSLIB]RDMPRV70.EXE;29 -SYSTEM-F-PROTINSTALL, protected images must be installedt =20a>  *** Oracle RMU IVP failed.  Check to make sure Oracle Rdb 7.0#      is running on this system. ***n =20t= %VMSINSTAL-E-IVPFAIL, The IVP for SQLSRVAMVF V7.0 has failed.  =20a>     Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY =20 &     Creating installation data file: =' VMI$ROOT:[SYSUPD]SQLSRVAMVF070.VMI_DATAr =20: =20L)         VMSINSTAL procedure done at 12:03- =20- =20-	 $ sho sysaH OpenVMS V7.2  on node HOBBY  23-JUL-2002 12:06:46.01  Uptime  2 12:20:09I   Pid    Process Name    State  Pri      I/O       CPU       Page flts  =i PagesgJ 00000081 SWAPPER         HIB     16        0   0 00:00:05.14         0   =    0J 00000084 LANACP          HIB     12       54   0 00:00:00.11       127   =   95J 00000086 IPCACP          HIB     10        9   0 00:00:00.02        31   =   43J 00000087 ERRFMT          HIB      8     6583   0 00:00:07.07        88   =  103J 00000089 OPCOM           HIB      9      464   0 00:00:00.34       159   =   47J 0000008A AUDIT_SERVER    HIB      9      320   0 00:00:00.42       139   =  168J 0000008B JOB_CONTROL     HIB     10      365   0 00:00:00.26        62   =   85J 0000008C SECURITY_SERVER HIB     10      720   0 00:00:02.07       707   =  248J 0000008E SYSTEM          LEF      5    60704   0 00:02:29.17     67822   =  113J 0000008F TCPIP$INET_ACP  HIB     10      223   0 00:00:00.22       276   =  144J 00000097 QUEUE_MANAGER   HIB      8      104   0 00:00:00.17       135   =  172J 00000098 TNT_SERVER      HIB      6     1398   0 00:00:28.33       800   =  833J 0000009C TNT198          LEF      4       41   0 00:00:00.18       598   =  322  SeJ 0000009D VPM_SERVER      HIB     15       14   0 00:00:00.11       227   =  147J 000000B0 SETI@home 36%   COM      3   436052   1 11:47:44.69      7812   = 2219  B.J 000000CF _TNA24:         LEF      7    52742   0 00:01:06.79     16173   =  411J 000000D6 _TNA25:         CUR      4    21641   0 00:00:37.56     22259   =  153J 000000E0 sqlsrv_mon_0070 HIB      6      229   0 00:00:00.46       444   =  264J 000000E1 RMU_DISP00470   HIB      6       82   0 00:00:00.21       453   =  215J 000000E2 SQLSRV_DIS00370 HIB      6       93   0 00:00:00.22       497   =  218J 000000E3 RMU_SE005000170 HIB      6      429   0 00:00:01.07       878   =  227J 000000E4 RMU_SE005000270 HIB      6      429   0 00:00:00.86       879   =  228J 000000E5 RMU_SE005000370 HIB      6      434   0 00:00:01.05       878   =  227J 000000E6 RMU_SE005000470 HIB      6      436   0 00:00:01.01       879   =  228 $   + ------=_NextPart_000_0011_01C23249.0CF0E330u Content-Type: text/html; 	charset="iso-8859-1"s+ Content-Transfer-Encoding: quoted-printableu  > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>7 <META http-equiv=3DContent-Type content=3D"text/html; =l charset=3Diso-8859-1">8 <META content=3D"MSHTML 5.50.4727.700" name=3DGENERATOR> <STYLE></STYLE>m </HEAD>a <BODY>F <DIV><FONT face=3D"Courier New" size=3D2>I'm installing the hobbyist = version of Rdb=20e< and SQL/Services (multiversion), and have run up against a = problem.&nbsp; It=20E seems that the Installation Verification Procedure for SQL/Services =  cannot find=20F the GENERIC service.&nbsp; At least that is my interpretation of the = output from=20I the installation procedure.&nbsp; The output is the result of my second =< attempt;=20tC messages referring to existing registry entries refer to my first =2
 attempt to=207 install the kit.</FONT></DIV>o< <DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>J <DIV><FONT face=3D"Courier New" size=3D2>Can someone possibly offer some = sage advice=20G on how to get this successfully installed?&nbsp; Here is a portion of =- the=20F installation procedure's output along with the output of SHOW SYSTEM = immediately=20, following the IVP's completion:</FONT></DIV>< <DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>= <DIV><FONT face=3D"Courier New" size=3D2>Thanks,</FONT></DIV>m; <DIV><FONT face=3D"Courier New" size=3D2>Alder</FONT></DIV>M <DIV>&nbsp;</DIV>N" <DIV><FONT face=3D"Courier New"=20J size=3D2>----------------------------------------------------------------= ------------</FONT></DIV>s: <DIV><FONT face=3D"Courier New" size=3D2>%REGISTER-I-DUP = SQLSRV_PRVSHR70,=20 J (SQLSRV_PRVSHR, V7.0-6) already in registry<BR>%REGISTER-I-SUMMARY&nbsp; =	 images=20oC examined: 1, dependent images: 1<BR>&nbsp;<BR>&nbsp;&nbsp;&nbsp;=20 J *************************************************************<BR>&nbsp;<B= R>&nbsp;&nbsp;&nbsp;=20M1 Please refer to the Oracle SQL/Services release =r" notes<BR>&nbsp;&nbsp;&nbsp; for=20D specific instructions for setting up SQL*Net<BR>&nbsp;&nbsp;&nbsp; = configuration=20J files for use with Oracle SQL/Services.<BR>&nbsp;<BR>&nbsp;&nbsp;&nbsp;=20J *************************************************************<BR>&nbsp;<B= R>%VMSINSTAL-I-MOVEFILES,=20* Files will now be moved to their target=204 directories...<BR>&nbsp;<BR>&nbsp;Starting Oracle=20< SQL/Services.<BR>&nbsp;<BR>Installing Oracle SQL/Services=20D images<BR>%REGISTER-I-DUP SQLSRV_PRVSHR70, (SQLSRV_PRVSHR, V7.0-6) =
 already in=20oE registry<BR>%REGISTER-I-SUMMARY&nbsp; images examined: 1, dependent =t
 images:=209 1<BR>Starting Oracle SQL/Services<BR>SQLSRV&gt; Server=20oC started<BR>&nbsp;<BR>&nbsp;Now executing the Oracle SQL/Services=20iF IVP<BR>&nbsp;<BR>&nbsp; Starting the TCP/IP test.<BR>&nbsp;<BR>***** =
 Connecting=20 E to generic service *****<BR>&nbsp;<BR>***** Oracle SQL/Services IVP =  Error=20J *****<BR>&nbsp;<BR>SQLCA: SQLCODE: -2051&nbsp; SQLERRD[0]: 0 SQLERRD[2]=20I 0<BR>SQLERRM.SQLERRMC -SQLSRV-E-SVCNOTRUN, The requested service is not = 
 running=20E or is<BR>&nbsp;not defined<BR>&nbsp;<BR>*** Oracle SQL/Services IVP =u failed when=20E accessing the&nbsp; generic service ***<BR>%NONAME-E-NOMSG, Message = 	 number=20 I 00000002<BR>&nbsp;<BR>&nbsp;&nbsp; **** Oracle SQL/Services client test = 	 failed=20 J ****<BR>&nbsp;<BR>&nbsp;<BR>&nbsp;Now executing the following command to =	 verify=20j< the Oracle<BR>&nbsp;RMU service:<BR>&nbsp;<BR>&nbsp;&nbsp; = RMU/EXECUTE/COMMAND=20J "RMU/SHOW VERSION"<BR>&nbsp;<BR>%DCL-W-ACTIMAGE, error activating image=20) RDMPRV70<BR>-CLI-E-IMGNAME, image file=20eJ HOBBY$DKA0:[SYS0.SYSCOMMON.][SYSLIB]RDMPRV70.EXE;2<BR>-SYSTEM-F-PROTINSTA= LL,=20J protected images must be installed<BR>&nbsp;<BR>&nbsp;*** Oracle RMU IVP =  - failed.&nbsp; Check to make sure Oracle Rdb =u% 7.0<BR>&nbsp;&nbsp;&nbsp;&nbsp; is=20dH running on this system. ***<BR>&nbsp;<BR>%VMSINSTAL-E-IVPFAIL, The IVP = for=20D SQLSRVAMVF V7.0 has failed.<BR>&nbsp;<BR>&nbsp;&nbsp;&nbsp; Adding = history entry=20G in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY<BR>&nbsp;<BR>&nbsp;&nbsp;&nbsp; =  Creating=20n installation data file:=20J VMI$ROOT:[SYSUPD]SQLSRVAMVF070.VMI_DATA<BR>&nbsp;<BR>&nbsp;<BR>&nbsp;&nbs=# p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20f@ VMSINSTAL procedure done at 12:03<BR>&nbsp;<BR>&nbsp;<BR>$ sho = sys<BR>OpenVMS=20 > V7.2&nbsp; on node HOBBY&nbsp; 23-JUL-2002 12:06:46.01&nbsp; = Uptime&nbsp; 2=20MJ 12:20:09<BR>&nbsp; Pid&nbsp;&nbsp;&nbsp; Process Name&nbsp;&nbsp;&nbsp;=200 State&nbsp; Pri&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20) I/O&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =t* CPU&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20$ Page flts&nbsp; Pages<BR>00000081=20: SWAPPER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20J HIB&nbsp;&nbsp;&nbsp;&nbsp; 16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =   0&nbsp;&nbsp; 0 =T> 00:00:05.14&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=200 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<BR>00000084=20? LANACP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20.E HIB&nbsp;&nbsp;&nbsp;&nbsp; 12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20gC 54&nbsp;&nbsp; 0 00:00:00.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20r- 127&nbsp;&nbsp;&nbsp;&nbsp; 95<BR>00000086=20m? IPCACP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 J HIB&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =  H 9&nbsp;&nbsp; 0 00:00:00.02&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20, 31&nbsp;&nbsp;&nbsp;&nbsp; 43<BR>00000087=20? ERRFMT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 = HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8&nbsp;&nbsp;&nbsp;&nbsp; =t 6583&nbsp;&nbsp; 0=20t7 00:00:07.07&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =  88&nbsp;&nbsp;&nbsp;=20s 103<BR>00000089=20D OPCOM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20D HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20D 464&nbsp;&nbsp; 0 00:00:00.34&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20, 159&nbsp;&nbsp;&nbsp;&nbsp; 47<BR>0000008A =! AUDIT_SERVER&nbsp;&nbsp;&nbsp;=20-D HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20D 320&nbsp;&nbsp; 0 00:00:00.42&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20' 139&nbsp;&nbsp;&nbsp; 168<BR>0000008B =-& JOB_CONTROL&nbsp;&nbsp;&nbsp;&nbsp;=20> HIB&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 365&nbsp;&nbsp; 0=207 00:00:00.26&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =. 62&nbsp;&nbsp;&nbsp;&nbsp;=20r= 85<BR>0000008C SECURITY_SERVER HIB&nbsp;&nbsp;&nbsp;&nbsp;=20s5 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 720&nbsp;&nbsp; 0=20 H 00:00:02.07&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 707&nbsp;&nbsp;&nbsp;=20 248<BR>0000008E = ? SYSTEM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20aI LEF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5&nbsp;&nbsp;&nbsp; 60704&nbsp;&nbsp; =  0=20= 00:02:29.17&nbsp;&nbsp;&nbsp;&nbsp; 67822&nbsp;&nbsp;&nbsp; =e 113<BR>0000008F=203 TCPIP$INET_ACP&nbsp; HIB&nbsp;&nbsp;&nbsp;&nbsp;=20 5 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 223&nbsp;&nbsp; 0=20 H 00:00:00.22&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 276&nbsp;&nbsp;&nbsp;=20+ 144<BR>00000097 QUEUE_MANAGER&nbsp;&nbsp; =a$ HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=204 8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 104&nbsp;&nbsp; 0=20H 00:00:00.17&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 135&nbsp;&nbsp;&nbsp;=20; 172<BR>00000098 TNT_SERVER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 = HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6&nbsp;&nbsp;&nbsp;&nbsp; =o 1398&nbsp;&nbsp; 0=20 H 00:00:28.33&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 800&nbsp;&nbsp;&nbsp;=20 833<BR>0000009C =f? TNT198&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20hJ LEF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20C 41&nbsp;&nbsp; 0 00:00:00.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 0 598&nbsp;&nbsp;&nbsp; 322&nbsp; S<BR>0000009D=20G VPM_SERVER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HIB&nbsp;&nbsp;&nbsp;&nbsp;=20k: 15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 14&nbsp;&nbsp; 0=20H 00:00:00.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 227&nbsp;&nbsp;&nbsp;=20; 147<BR>000000B0 </FONT><A href=3D"mailto:SETI@home"><FONT =  face=3D"Courier New"=20 C size=3D2>SETI@home</FONT></A><FONT face=3D"Courier New" size=3D2> =  36%&nbsp;&nbsp;=20G COM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3&nbsp;&nbsp; 436052&nbsp;&nbsp; 1=20TH 11:47:44.69&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7812&nbsp;&nbsp; 2219&nbsp;=20H B<BR>000000CF _TNA24:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20I LEF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp; 52742&nbsp;&nbsp; =s 0=20= 00:01:06.79&nbsp;&nbsp;&nbsp;&nbsp; 16173&nbsp;&nbsp;&nbsp; =E 411<BR>000000D6=20: _TNA25:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20I CUR&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4&nbsp;&nbsp;&nbsp; 21641&nbsp;&nbsp; =  0=20= 00:00:37.56&nbsp;&nbsp;&nbsp;&nbsp; 22259&nbsp;&nbsp;&nbsp; =c 153<BR>000000E0=204 sqlsrv_mon_0070 HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=204 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 229&nbsp;&nbsp; 0=20H 00:00:00.46&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 444&nbsp;&nbsp;&nbsp;=20+ 264<BR>000000E1 RMU_DISP00470&nbsp;&nbsp; =c$ HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=209 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 82&nbsp;&nbsp; 0=20wH 00:00:00.21&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 453&nbsp;&nbsp;&nbsp;=20D 215<BR>000000E2 SQLSRV_DIS00370 HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=209 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 93&nbsp;&nbsp; 0=20aH 00:00:00.22&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 497&nbsp;&nbsp;&nbsp;=20D 218<BR>000000E3 RMU_SE005000170 HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=204 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 429&nbsp;&nbsp; 0=20H 00:00:01.07&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 878&nbsp;&nbsp;&nbsp;=20D 227<BR>000000E4 RMU_SE005000270 HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=204 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 429&nbsp;&nbsp; 0=20H 00:00:00.86&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 879&nbsp;&nbsp;&nbsp;=20D 228<BR>000000E5 RMU_SE005000370 HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=204 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 434&nbsp;&nbsp; 0=20H 00:00:01.05&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 878&nbsp;&nbsp;&nbsp;=20D 227<BR>000000E6 RMU_SE005000470 HIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=204 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 436&nbsp;&nbsp; 0=20H 00:00:01.01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 879&nbsp;&nbsp;&nbsp;=20# 228<BR>$</FONT></DIV></BODY></HTML>m  - ------=_NextPart_000_0011_01C23249.0CF0E330--i   ------------------------------  % Date: Tue, 23 Jul 2002 15:25:00 -0700 * From: "Alder" <MUNDDGNTDYTV@spammotel.com>* Subject: Re: [Hobbyist] User account setup) Message-ID: <3d3dd7be@obsidian.gov.bc.ca>r  8 "Peter Weaver" <peter.weaver@stelco.ca> wrote in message/ news:ahh337$sna04$1@ID-141708.news.dfncis.de...  >sA > BTW: If anyone else gives you the advice of either rebooting orpH > re-installing VMS, please don't. It is so seldom that VMS breaks it isB > interesting to have some practice trouble-shooting a problem. :) >-  L I'm sure VMS didn't break, but I did, so I took the advice of Bill Gates and reinstalled.  = Sorry to those of you who were looking for some more practicebB trouble-shooting, but my head was beginning to ache.  Frustration,, confusion, and fatigue got the better of me.   Kindest regards to all,3   Aldern   ------------------------------  # Date: Tue, 23 Jul 2002 21:58:07 GMTq From: "H.Vlems" <hvlems@iae.nl>g Subject: [OT] Attn: Lennyb1 Message-ID: <Pjk%8.5323$Q4.54949@typhoon.bart.nl>u   Thanks for the card.6 I lost your email address owing to a harddisk failure. Please send it again.    Hans   ------------------------------    Date: 23 Jul 2002 14:13:14 -0700. From: SPAMSINK2001@YAHOO.COM (Alan E. Feldman)Q Subject: [Q] How is condition code selected for $STATUS from multi-line messages?t= Message-ID: <343f30ae.0207231313.204dee4e@posting.google.com>o   Hello,  C I used to think that $STATUS was "defined" to be the condition coded9 for the line starting with the percent sign. For example,p   DCL> TYPE [ASDF]ASDFB %TYPE-W-SEARCHFAIL, error searching for DISK$DATA1:[ASDF]ASDF.LIS; -RMS-E-DNF, directory not found-" -SYSTEM-W-NOSUCHFILE, no such file DCL> STATUS = $STATUS= DCL> SHOW SYMBOL STATUSQ   STATUS = "%X10951238"V DCL> WSO F$MESS(STATUS)w+ %TYPE-W-SEARCHFAIL, error searching for !ASn DCL>  E Sometimes there is more than one line starting with the percent sign.*F In those cases, I assumed $STATUS was "defined" to be the code for the8 most serious one. That seems to work as I can't recall a counter-example.  > Now, if the "percent rule" were true, then one could judge theD severity from the running of a command by simply noting the severityA given in the line starting with the percent sign, and if multipleiB %-lines were displayed, to choose the most severe from among them.  5 But many years ago I noticed there was the exception:H   DCL> DIR ASDF:@ %DIRECT-E-OPENIN, error opening ASDF:[FELDMAN.DCL]*.*;* as inputA -RMS-F-DEV, error in device name or inappropriate device type forV	 operationa DCL> STATUS = $STATUSi DCL> SHOW SYMBOL STATUSs   STATUS = "%X100184C4"e DCL> WSO F$MESS(STATUS)*A %RMS-F-DEV, error in device name or inappropriate device type fori	 operationo DCL>  A and I thought that maybe this was the only exception. But later I.E found other exceptions. An RMS suberror (one starting with a hyphen),rA would often (if not always) supersede the "main" message (the onecE starting with the percent sign). Also, problems with running an image0 have the same behavior:c   DCL> RUN NOSUCHIMAGE3 %DCL-W-ACTIMAGE, error activating image NOSUCHIMAGEo% -CLI-E-IMAGEFNF, image file not foundU* IDS03$DKA200:[FELDMAN.DCL]NOSUCHIMAGE.EXE; DCL> STATUS = $STATUS  DCL> SHOW SYMBOL STATUSt   STATUS = "%X100388B2"C DCL> WSO F$MESS(STATUS)=) %CLI-E-IMAGEFNF, image file not found !ASV  D Recently I noticed that sometimes the messages don't even match up!:   DCL> DIR NOSUCHFILE ! %DIRECT-W-NOFILES, no files foundR DCL> STATUS = $STATUS  DCL> SHOW SYMBOL STATUSt   STATUS = "%X10018290"h DCL> WSO F$MESS(STATUS)  %RMS-W-FNF, file not found DCL>  D Here the messages differ in facility, ident, and text! OK, they bothB correctly indicate "no such file(s)", but I would have expected an exact match.  E Also, sometimes a command completing with -I- severity in the message7D assigns the success status to $STATUS instead of informational (with $SEVERITY = 1 instead of 3).  C So to be really sure one must explicitly check the value of $STATUS : and/or $SEVERITY instead of relying on the error messages.  B So, my question is: Is there a method behind the madness or simply> madness behind the method? And if there is a method behind the madness, what is it?  C Thanks. (Examples were run under VMS v6.1, works the same on v6.2.)    Disclaimer: JMHO Alan E. Feldman  afeldman gfigroup com    ------------------------------    Date: 23 Jul 2002 18:18:24 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) U Subject: Re: [Q] How is condition code selected for $STATUS from multi-line messages?03 Message-ID: <tBQ30V9cqTRa@eisner.encompasserve.org>7  n In article <343f30ae.0207231313.204dee4e@posting.google.com>, SPAMSINK2001@YAHOO.COM (Alan E. Feldman) writes: > Hello, > E > I used to think that $STATUS was "defined" to be the condition codeE; > for the line starting with the percent sign. For example,   H That is guaranteed (aside from the MSG_INHIB bit) for messages displayedG by DCL.  But DCL only displays single line messages, so for any chained D message you are guaranteed the output was done by the program rather than by AOL.  G > Sometimes there is more than one line starting with the percent sign.7H > In those cases, I assumed $STATUS was "defined" to be the code for the: > most serious one. That seems to work as I can't recall a > counter-example.  F No, $STATUS is whatever 32 bit code is returned to DCL by the program./ That is up to the person who wrote the program.   @ > Now, if the "percent rule" were true, then one could judge theF > severity from the running of a command by simply noting the severityC > given in the line starting with the percent sign, and if multiple D > %-lines were displayed, to choose the most severe from among them.  E That is one algorithm a programmer can choose to implement, but it isH by no means universal.   ------------------------------   End of INFO-VAX 2002.404 ************************