1 INFO-VAX	Sun, 16 Apr 2000	Volume 2000 : Issue 213       Contents: Backup stalling - Alpha 7.2-1  Re: CXML and SETI  Re: CXML and SETI  Re: DEC BASIC Open w/RRL set Re: DECC 6.n BUG? /OPTIMIZE  Re: DECC 6.n BUG? /OPTIMIZE < Re: easy which command tells me the model of my vax or alpha Re: faster/smarter FTP clients? K Re: How can you find the exact size of a file in bytes using a  VMScommand? K Re: How can you find the exact size of a file in bytes using a VMS command?  M38 VS for sale  Re: Maximum Password Lengths Need OpenVMS-VAX 6.2 on TK50 PC164 serial port speed < Safe Shipping (was Re: Warning: circuitsurgeon is a ripoff!)% Re: Shock, horror! An OpenVMS advert!  Re: signature file in MAIL1 Re: Too Few Servers Detected from: Node LOCAL.... ( Re: Warning: circuitsurgeon is a ripoff!( Re: Warning: circuitsurgeon is a ripoff!6 Re: Why are there no French people in this newsgroup ?  F ----------------------------------------------------------------------  % Date: Sun, 16 Apr 2000 09:27:26 +0200 $ From: Paul Sture <sture.ch@sture.ch>& Subject: Backup stalling - Alpha 7.2-1* Message-ID: <VA.00000005.04efc56b@peacock>  a I had a weird one last week. One of my weekly backup jobs hadn't finished the other morning, and  >  the process was still there, but not moving (no I/Os or cpu).  [ When I looked at the tape drive, the tape cleaner light was on. I unloaded the tape, put a  5 cleaning one in, then loaded the original tape again.   ^ The backup process didn't respond in any way, it was still "hung". I killed it, re-inited the  tape and started the job again.   b What concerns me is that this could be a bug in V7.2-1 backup, as previous incidences of the tape [ cleaning light coming on during a backup have resulted in either a specific "tape cleaner"  a message, or more generic "parity" or "position lost" errors (can't remember the exact texts, and   I'm at home now).   ` Has anyone else seen similar? My other thought was that maybe quota changes from V7.1 to V7.2-1 ^ mean that the quotas for the account doing the backup need changing, but that's a stab in the Z dark (and at the time I just wanted to get my backup done rather than analyze the hanging 	 process).   
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 16 Apr 2000 02:22:57 -0400 * From: David A Froble <davef@tsoft-inc.com> Subject: Re: CXML and SETI- Message-ID: <38F95C41.F2A125C1@tsoft-inc.com>    Neil Rieck wrote:  > 7 > mrsignor <mrsignor@bellatlantic.net> wrote in message 4 > news:F73K4.3263$X56.184313@typhoon1.gnilink.net...J > > I have read a few posts about CXML being available, and a comment from  > > the Math library group about >  > [snip] > L > > Q - Is anyone (outside of ComPaq) running a standard SETI with CXML, andJ > >       if so, any special install procedure?, and what speed difference > does  it make  > > 	 >  [snip]  > M > It's true. Only Compaq employees are allowed to run the CXML dependant SETI I > client and I've heard that the SETI folk want Compaq to stop. I've been : > given no reason for this but have a (conspiracy) theory: > N > Go to the SETI web site at http://setiathome.ssl.berkeley.edu/ and take noteD > of who the corporate sponsors are. Now visit the CPU stats page atL > http://setiathome.ssl.berkeley.edu/stats/cpus.html and scan the right handL > column. Be sure to check lines #10, #12, and 14. Can you imagine how p/o'dN > the corporate sponsors will be when/if the CXML dependant SETI client startsN > running on EV68? (of course Compaq could squelch any criticism by becoming aN > corporate sponsor; no need to donate any money... just some equipment and/or- > software.. it's all tax deductible, right?)   G Shame on you for thinking that these fine sponsors would resort to such L tactics.  Why, just in this newsgroup we see the honest and fair postings byO that fine Enterprise Archetech Andrew.  Can you point to any times he has tried  to confuse an issue? :-)  L I'm not sure becoming a sponsor would help.  The fine people at Sun may be aK 'substantial' sponsor, and might have a counterpart to Andrew watching this  area.   O It would probably be counter-productive, but I'd like to see Compaq release the N ultra fast SETI client.  It would then force the SETI people to decide whether: they wanted results, or are just another political entity.   Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596; 170 Grimplin Road               E-Mail: davef@tsoft-inc.com  Vanderbilt, PA  15486    ------------------------------  # Date: Sun, 16 Apr 2000 13:45:17 GMT ) From: "Neil Rieck" <n.rieck@sympatico.ca>  Subject: Re: CXML and SETI: Message-ID: <NtjK4.32792$2D6.990236@news20.bellglobal.com>  5 David A Froble <davef@tsoft-inc.com> wrote in message ' news:38F95C41.F2A125C1@tsoft-inc.com...  > Neil Rieck wrote:    [snip]  I > Shame on you for thinking that these fine sponsors would resort to such K > tactics.  Why, just in this newsgroup we see the honest and fair postings  byK > that fine Enterprise Archetech Andrew.  Can you point to any times he has  tried  > to confuse an issue? :-)  * Hey, we all believe in the X-files; right?  L > I'm not sure becoming a sponsor would help.  The fine people at Sun may be a H > 'substantial' sponsor, and might have a counterpart to Andrew watching this > area.  > E > It would probably be counter-productive, but I'd like to see Compaq  release the H > ultra fast SETI client.  It would then force the SETI people to decide whether < > they wanted results, or are just another political entity.  F I'd like to see the fast client released to the public too. Maybe theyH (Compaq) had to enter into some friendly arrangement with the SETI folks& just to get a copy of the source code.  
 Neil Rieck* Kitchener(New Berlin?)/Waterloo/Cambridge, Ontario, Canada.! http://www3.sympatico.ca/n.rieck/ 6 http://www3.sympatico.ca/n.rieck/docs/alpha_diary.html4 http://www3.sympatico.ca/n.rieck/docs/seti_tips.html   ------------------------------  % Date: Sun, 16 Apr 2000 02:40:23 -0400 * From: David A Froble <davef@tsoft-inc.com>% Subject: Re: DEC BASIC Open w/RRL set - Message-ID: <38F96057.2C4CB201@tsoft-inc.com>    Tom Simpson wrote: > E > Does anyone have an example of how to open a file in DEC Basic with M > the RRL (read regardless of lock bit set?)?   I think that's what I want...  > H > I am trying to open a program log file so it can be examined while theJ > program is still running, similar to how you can examine a batch job log > file.  > N > I tried, but have not been able to get it to work so far...   Many moons agoL > I had a routine that would do this in Pascal but I can't locate the source > code for it. >  > Thanks in advance. > 
 > Regards, > Tom   : Below is some simple code, with a very interesting result:  
 $ t t1.basE 10      open "t1.log" for output as file 1%, access write, allow read     20      print #1%, time$(0%)         sleep 30%          goto 20     99      end   M This is a simple program to open a sequential variable text file and write to   it, allowing others read access.  
 $ t t2.basE 10      open "t1.log" for input as file 1%, access read, allow modify             on error goto 90    20      linput #1%, l$         print l$         goto 20    & 90      resume 99 if erl=20 and err=11         on error goto 0     99      end   I This is a simple program to read the text file, while program T1 is still  running.   $ run t2 02:31 AM 02:32 AM 02:32 AM 02:33 AM 02:33 AM 02:34 AM 02:34 AM  F When T2 is run, it reads the data written to the text file, Ok so far.   $ di t1     Directory DKA0:[DFE]   E T1.BAS;1                        1/2       [DFE]       (RWED,RWED,RE,) E T1.EXE;1                        6/6       [DFE]       (RWED,RWED,RE,) E T1.LOG;1                        0/32      [DFE]       (RWED,RWED,RE,) E T1.OBJ;1                        2/2       [DFE]       (RWED,RWED,RE,)     Total of 4 files, 9/42 blocks.  O But wait a minute, I didn't have any used filespace in the text file, according L to the DIRECTORY, and the BASIC program was able to read the data.  I reallyL didn't think this would happen.  It's like the I/O buffer from progeam T1 isM available to T2, or the data was written to the file, but the directory entry  wasn't updated.  Hmmmm....  
 $ t t1.log $   K Finally the TYPE utility is used to view the file, and it displays nothing,  which I expected.   K And that's probably more than you wanted to know.  It appears that the open P statement in program T1 is what you want, and if you want to be able to TYPE theK text file, you will need something to periodically flush the I/O buffer and P update the file directory entry, which is doable from RMS, but possibly not fromL BASIC.  One thing to look at would be the file open, using a USEROPEN to setM some RMS flag to periodically flush the buffer.  I don't know if such exists.    Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596; 170 Grimplin Road               E-Mail: davef@tsoft-inc.com  Vanderbilt, PA  15486    ------------------------------  % Date: Sun, 16 Apr 2000 01:09:17 -0700  From: LBohan@spam_less..dbc.com $ Subject: Re: DECC 6.n BUG? /OPTIMIZE8 Message-ID: <79tifsk6q47hs03s43g8j4vn7ou9jg1u0e@4ax.com>  / On Sat, 15 Apr 2000 03:31:02 +0930, Mark Daniel $ <mark.daniel@wasd.vsm.com.au> wrote:   trying your example on:   @   Compaq C V6.2-007 on OpenVMS Alpha V7.1-2 , DS20 500mhz  (ev6)@   Compaq C V6.2-003 on OpenVMS Alpha V7.1-2 , DS20 500mhz  (ev6);   Compaq C V6.2-003 on OpenVMS Alpha V7.1-2 , 500au (ev56?) A   Compaq C V6.2-003 on OpenVMS Alpha V7.2-1,  Aspen Durango (ev5) /   DEC C V6.0-001 on OpenVMS VAX V7.1  (vax 7.1)       same (correct) results on all.  : for yucks, I'd wonder if you get different results if you  used %u (instead of %d),  ie    7 fprintf (stdout, "%d %d %d\a\n", Count,Whole,Fraction); 	    vs     7 fprintf (stdout, "%u %u %u\a\n", Count,Whole,Fraction);   7 hardware problems are certainly a (small) possibility.    6 I know of only one case firsthand, the rest anecdotal./ the case in question was almost 12 years ago.     > A new hire insisted that the hdw was fault, for a calculation > error, and we basically chuckled, and told him to look harder.  < a few days later, he came up w/ a definitive small example, F that ran differently, on one node of the cluster.  the fix, in the end% was replacing the CPU on that system.   E I remember seeing a similar thread on COV, (perhaps DECUServe Notes?) F that one, and the problem we saw, concerned floating point arithmetic.  = I would think if you had a genuine hdw error, warping integer = arithmetic, that your system would be crashing left && right.   F Does your test example produce the same (wrong) results with each run?  F One thing to try (but doesn't sound possible in your situation), is toD power the system off,  let it cool off overnight, and to see you seeE the same results shortly after boot.  (the idea being that heat makes  flakier hdw, flakier yet) ....   ------------------------------  % Date: Sun, 16 Apr 2000 21:53:56 +0930 / From: Mark Daniel <mark.daniel@wasd.vsm.com.au> $ Subject: Re: DECC 6.n BUG? /OPTIMIZE/ Message-ID: <38F9B0DC.3244D83A@wasd.vsm.com.au>     LBohan@spam_less..dbc.com wrote:   > trying your example on:  > B >   Compaq C V6.2-007 on OpenVMS Alpha V7.1-2 , DS20 500mhz  (ev6)B >   Compaq C V6.2-003 on OpenVMS Alpha V7.1-2 , DS20 500mhz  (ev6)= >   Compaq C V6.2-003 on OpenVMS Alpha V7.1-2 , 500au (ev56?) C >   Compaq C V6.2-003 on OpenVMS Alpha V7.2-1,  Aspen Durango (ev5) 1 >   DEC C V6.0-001 on OpenVMS VAX V7.1  (vax 7.1)  >   > same (correct) results on all.    Rats ... er, I mean that's good.  ; > for yucks, I'd wonder if you get different results if you  > used %u (instead of %d),  ie  I Originally I noticed it with a  sys$fao()  "!UL.!4ZL"  where the !4ZL was A being "****" because the supposedly 0-9999 being generated with a      duration_usecs / 1000000; #   (duration_usecs % 1000000) / 100;   J was, as my experimental results show, actually exceeding that range due toD the mod apparently being "broken" in some way.  Initially I couldn'tD believe it.  It took a lot of expeimentation before I settled on the, conclusion integer arithmetic seemed broken.  8 > hardware problems are certainly a (small) possibility.  H You would think very small considering I brought in a /OPT .EXE from the9 VMS 7.1, DECC 5.6 system and it ran with correct results!   ? > I would think if you had a genuine hdw error, warping integer ? > arithmetic, that your system would be crashing left && right.   D Yes, it's so fundamental.  System has been up essentially since lastJ year-end.  Remember this is only when using the /OPTIMIZE qualifier, so itG seems entirely possible the optimizer is broken subtly, perhaps munging = the code for a slightly different implementation of the chip.   H > Does your test example produce the same (wrong) results with each run?  D Yes, a dozen runs over a period of a couple of hours (as I fought my
 incredulity).   F And, as noted in a previous (slightly garbled) message (it was gettingJ very late ... ah early) this same system seems to be experiencing problems0 processing SETI data from the precompiled .EXE!!  H > One thing to try (but doesn't sound possible in your situation), is toF > power the system off,  let it cool off overnight, and to see you seeG > the same results shortly after boot.  (the idea being that heat makes   > flakier hdw, flakier yet) ....  I Might be able to do better that that.  Have a complete, equivalent system B in mothballs.  Might be able to get our h/w guy to swap CPUs, m/b,0 whatever.  Pity I'm away for the next two weeks.  % Thanks for your trouble and feedback.    Regards,  E +-------------------------------------------------------------------+ D  Mark Daniel            Opinions my own ... and on loan from others.E  mailto:Mark.Daniel@wasd.vsm.com.au (Mark.Daniel@dsto.defence.gov.au) E +-------------------------------------------------------------------+    ------------------------------  % Date: Sun, 16 Apr 2000 16:57:18 +0200 " From: "Hans Vlems" <hvlems@iae.nl>E Subject: Re: easy which command tells me the model of my vax or alpha ( Message-ID: <8dck23$487$1@news.IAEhv.nl>  	 $ sho cpu  or $ sho license/chargeL Joe heeft geschreven in bericht <8F165027Ejoeyahoocom@news.supernews.com>...E >I had to type a command a couple of day a go that would tell me that F >i hava and alpha 1000 i bet there is more than one but i can't get to >it. Thanks.   ------------------------------  % Date: Sun, 16 Apr 2000 02:06:40 -0700  From: LBohan@spam_less..dbc.com ( Subject: Re: faster/smarter FTP clients?8 Message-ID: <thuifsk6srembcblsg12ddjpecum4rmq19@4ax.com>  = I was curious if the version of MGFTP you were testing with,   was  << v2.6 ?  (circa Nov '99) 	           2    2.1    New Features and Bug fixes in MGFTP V2.6  6           o  Increased the throughput performance when=              transferring files from the network to the local =              disk. Previous versions of the server and client 8              wrote binary files out one block at a time,@              resulting in a severe performance penalty. In V2.6,?              the data is written in 127-block chunks per write. ?              This change has resulted in transfers from the net @              to the local disk that are 2 to 6 times faster than              previous versions.   4 w/ the focus on disk i/o performance underlying the 6 FTP (as opposed to the VMS/NT window size mis-matches)  2 I'm reminded of the thread below, inre fast-io;   ? (I was rather impressed w/ the speed of this FAST_IO_COPY demo)   9 I'd been curious if we would ever see similar techniques  E integrated into $COPY, $BACKUP and ftp (or made optional, ie /FAST ).   > I'd imagine there's tradeoffs for doing so, perhaps increased 9 memory usage,  lessened reliability/robustness, or both ?   < If I knew Bliss  (i don't), it might've made an interesting 9 exercise to try and hack this fast-io example into MGFTP.         a http://x42.deja.com/=dnc/[ST_rn=ps]/getdoc.xp?AN=319578088.1&CONTEXT=955873662.708902922&hitnum=1     = From: vandenheuvel@eps.enet.dec.c*m (Hein RMS van den Heuvel)s% Subject: Re: Fast Path I/O C examplesn Date: 27 Jan 1998 00:00:00 GMT* Message-ID: <6ajqur$nl3@usenet.pa.dec.com>+ References: <34C8884B.69F3A323@DeltaTel.RU> + Organization: Digital Equipment Corporationa Newsgroups: comp.os.vmsm  ? In article <34C8884B.69F3A323@DeltaTel.RU>, "Ruslan R. Laishev"i  <RLaishev@DeltaTel.RU> writes...	 >Hi All ! S >       Where I can search any examples written in C using Fast Path I/O routines ?a  8         First of all, there is SYS$EXAMPLES:IO_PERFORM.C  <         I'll also include a program Bob Sampson made a while         ago called FAST_IO_COPYi           hth,                 Hein.n   /*4  * FAST_IO_COPY.C - disk file copy Fast I/O example.5  * This program requires OpenVMS V7.0 (VAX or Alpha).u3  * The DEC C V5.2 (or newer) compiler is preferred.r  */! #include <atrdef.h>o #include <descrip.h>   #if __ALPHA < #include <fatdef.h> /* +sys$library:sys$lib_c.tlb/library */ #else-@ #include "fatdef.h" /* extract this header for VAX from an Alpha	 system */c #endif   #include <fibdef.h>A #include <iodef.h> #include <iosadef.h> #include <lib$routines.h>r #include <rms.h> #include <ssdef.h> #include <starlet.h> #include <stdio.h> #include <stdlib.h>w #include <string.h>o   #define NBYTES_PER_BLOCK 512 #define MAX_BUFFERS 16 #define MAX_BLOCKS_PER_XFER 127 A #define MAX_BYTES_PER_XFER (NBYTES_PER_BLOCK*MAX_BLOCKS_PER_XFER)oB #define MAX_BYTES_PER_BUFFER (NBYTES_PER_BLOCK+MAX_BYTES_PER_XFER)   #pragma extern_model savee% #pragma extern_model common_block shrt #pragma nostandard" extern volatile _align (page) char* buffer[MAX_BUFFERS][MAX_BYTES_PER_BUFFER]; #pragma standard) extern volatile fandle ifan[MAX_BUFFERS];v) extern volatile fandle ofan[MAX_BUFFERS];e* extern volatile int iohan[MAX_BUFFERS][2]; extern struct FAB ifab;n extern struct NAM inam;t$ extern char iexpand[NAM$C_MAXRSS+1];$ extern char iresult[NAM$C_MAXRSS+1]; extern struct FAB ofab;h extern struct NAM onam; $ extern char oexpand[NAM$C_MAXRSS+1];$ extern char oresult[NAM$C_MAXRSS+1]; extern struct XABFHC xabfhc; extern struct XABSUM xabsum;! extern struct XABALL xaball[255];l! extern struct XABKEY xabkey[255];l extern char knm[255][32];- extern volatile int ivbn;  extern volatile int iefn;:' extern volatile int nreads_outstanding;@( extern volatile int nwrites_outstanding;* extern volatile int max_reads_outstanding;+ extern volatile int max_writes_outstanding;r extern volatile int nbuffers;i% extern volatile int nblocks_per_xfer;3$ extern volatile int nbytes_per_xfer;& extern volatile int nbytes_per_buffer; #pragma extern_model restore  % void read_completion_ast(iosa *piosa)  { -   register int status = piosa->iosa$l_status; -   register int nbytes = piosa->iosa$ih_count;a3   register int ibuf   = piosa->iosa$q_context_q[0];n  1   if (nreads_outstanding > max_reads_outstanding)u/     max_reads_outstanding = nreads_outstanding;X     nreads_outstanding--;t  1   if ((status != SS$_ENDOFFILE) && !(status & 1))p   {e     int msgvec[2] = {1,0};     msgvec[1] = status;rD     printf("Could not perform input from VBN %0d to buffer #%0d.\n",*         piosa->iosa$q_context_q[1], ibuf);     sys$putmsg(msgvec,0,0,0);t     goto read_return;    }/  
   if (nbytes)e   {y     ifab.fab$l_ctx++;d  7     status = sys$io_perform(ofan[ibuf], ofab.fab$l_stv, :         &buffer[ibuf][0], &buffer[ibuf][NBYTES_PER_BLOCK],,         nbytes, piosa->iosa$q_context_q[1]);     if (!(status & 1))     {?       int msgvec[2] = {1,0};       msgvec[1] = status;g
       printf( B         "Could not start output (%0d bytes) to VBN %0d from buffer	 #%0d.\n",.2         nbytes, piosa->iosa$q_context_q[1], ibuf);       sys$putmsg(msgvec,0,0,0);o       goto read_return;      }.     nwrites_outstanding++;   }s   read_return:>   if ((nreads_outstanding == 0) && (nwrites_outstanding == 0))     sys$setef(iefn);	   return;e } /* read_completion_ast */   & void write_completion_ast(iosa *piosa) { -   register int status = piosa->iosa$l_status; -   register int nbytes = piosa->iosa$ih_count; 3   register int ibuf   = piosa->iosa$q_context_q[0];r  3   if (nwrites_outstanding > max_writes_outstanding)l1     max_writes_outstanding = nwrites_outstanding;      nwrites_outstanding--;     if (!(status & 1))   {t     int msgvec[2] = {1,0};     msgvec[1] = status;b     printf( D         "Could not perform output (%0d bytes) to VBN %0d from buffer	 #%0d.\n",62         nbytes, piosa->iosa$q_context_q[1], ibuf);     sys$putmsg(msgvec,0,0,0);8     goto write_return;   }-   ofab.fab$l_ctx++;1     if (ivbn <= ifab.fab$l_alq)N   {i+     piosa->iosa$ih_count = nbytes_per_xfer;M&     piosa->iosa$q_context_q[1] = ivbn;7     status = sys$io_perform(ifan[ibuf], ifab.fab$l_stv,s:         &buffer[ibuf][0], &buffer[ibuf][NBYTES_PER_BLOCK],         nbytes_per_xfer, ivbn);      if (!(status & 1))     {r       int msgvec[2] = {1,0};       msgvec[1] = status; 
       printf(,?         "Could not start input from VBN %0d to buffer #%0d.\n",          ivbn, ibuf);       sys$putmsg(msgvec,0,0,0);        goto write_return;     }o     ivbn += nblocks_per_xfer;w     nreads_outstanding++;s   }h  
 write_return:u>   if ((nreads_outstanding == 0) && (nwrites_outstanding == 0))     sys$setef(iefn);	   return;d } /* write_completion_ast */  ( int fast_io_copy(int argc, char *argv[]) #pragma nostandard main_program #pragma standard {C   register iosa *piosa = 0;    register int status = 0;   register int ibuf = 0;"   volatile char *inadr[2] = {0,0};   char *retadr[2] = {0,0};   unsigned short int iosb[4];t   struct atrdef atrlst[2];   struct fibdef fib;!   struct dsc$descriptor_s fibdsc;n
   FAT fat;   /*0  * Require input and output file specifications.  */h   if (argc < 3)    {R>     printf("Usage: %s <input-file> <output-file>\n", argv[0]);
     return 1;.   }t   /*.  * Allow additional arguments to change either3  * the buffer count or the transfer size in blocks.d  */e   nbuffers = MAX_BUFFERS;-)   nblocks_per_xfer = MAX_BLOCKS_PER_XFER;0  !   for (ibuf=3; ibuf<argc; ibuf++)e   {e-     if (!strncmp(argv[ibuf], "-nbuffers", 9))/     { 
       ibuf++;3       if (ibuf < argc)       { $         nbuffers = atoi(argv[ibuf]);8         if ((nbuffers == 0) || (nbuffers > MAX_BUFFERS))!           nbuffers = MAX_BUFFERS;k         else if (nbuffers < 0)           nbuffers = 1;t       }o     }r1     else if (!strncmp(argv[ibuf], "-nblocks", 8))r     {s
       ibuf++;        if (ibuf < argc)       {b,         nblocks_per_xfer = atoi(argv[ibuf]);:         if ((nblocks_per_xfer == 0) || (nblocks_per_xfer > MAX_BLOCKS_PER_XFER))t1           nblocks_per_xfer = MAX_BLOCKS_PER_XFER;r&         else if (nblocks_per_xfer < 0)           nblocks_per_xfer = 1;e       }m     }e     else     {y;       printf("Unrecognized argument #%0d: \"%s\".\n", ibuf,  argv[ibuf]);     }c   }r  8   nbytes_per_xfer = NBYTES_PER_BLOCK * nblocks_per_xfer;9   nbytes_per_buffer = NBYTES_PER_BLOCK + nbytes_per_xfer;   <   printf("Using %0d buffers, with %0d blocks (%0d bytes) per
 transfer.\n",i5         nbuffers, nblocks_per_xfer, nbytes_per_xfer);l  %   for (ibuf=0; ibuf<nbuffers; ibuf++)l   {d      inadr[0] = &buffer[ibuf][0];2     inadr[1] = &buffer[ibuf][nbytes_per_buffer-1];  A     status = sys$create_bufobj(inadr, retadr, 0, 0, iohan[ibuf]);e     if (!(status & 1))     { =       printf("Could not create buffer object #%0d.\n", ibuf);        return status;     }u  '     status = sys$io_setup(IO$_READVBLK,M:         iohan[ibuf], iohan[ibuf], &read_completion_ast, 0,
 &ifan[ibuf]);      if (!(status & 1))     { @       printf("Could not set up input for buffer #%0d.\n", ibuf);       return status;     }R  (     status = sys$io_setup(IO$_WRITEVBLK,;         iohan[ibuf], iohan[ibuf], &write_completion_ast, 0, 
 &ofan[ibuf]);/     if (!(status & 1))     {RA       printf("Could not set up output for buffer #%0d.\n", ibuf);W       return status;     }s   }2   /*-  * Fill in two RMS extended attribute blocks.   */p(   bzero((char*)&xabfhc, sizeof(xabfhc));   xabfhc.xab$b_cod = XAB$C_FHC;a"   xabfhc.xab$b_bln = XAB$C_FHCLEN;$   xabfhc.xab$l_nxt = (char*)&xabsum;  (   bzero((char*)&xabsum, sizeof(xabsum));   xabsum.xab$b_cod = XAB$C_SUM;t"   xabsum.xab$b_bln = XAB$C_SUMLEN;   /*%  * Fill in the input file RMS blocks.g  */ $   bzero((char*)&ifab, sizeof(ifab));   ifab.fab$b_bid = FAB$C_BID;n   ifab.fab$b_bln = FAB$C_BLN;    ifab.fab$l_nam = &inam;a)   ifab.fab$l_fop = FAB$M_NAM | FAB$M_UPI;o   ifab.fab$l_fna = argv[1]; #   ifab.fab$b_fns = strlen(argv[1]);b   ifab.fab$l_dna = 0;t   ifab.fab$b_dns = 0;m   ifab.fab$b_fac = FAB$M_GET;e    ifab.fab$b_shr = FAB$M_SHRGET;  $   bzero((char*)&inam, sizeof(inam));   inam.nam$b_bid = NAM$C_BID;.   inam.nam$b_bln = NAM$C_BLN;    inam.nam$l_esa = iexpand;E    inam.nam$b_ess = NAM$C_MAXRSS;   inam.nam$l_rsa = iresult;n    inam.nam$b_rss = NAM$C_MAXRSS;   /*&  * Fill in the output file RMS blocks.  */-$   bzero((char*)&ofab, sizeof(ofab));   ofab.fab$b_bid = FAB$C_BID;r   ofab.fab$b_bln = FAB$C_BLN;l   ofab.fab$l_nam = &onam;d5   ofab.fab$l_fop = FAB$M_CBT | FAB$M_MXV | FAB$M_OFP;    ofab.fab$l_fna = argv[2];1#   ofab.fab$b_fns = strlen(argv[2]);.   ofab.fab$l_dna = 0;    ofab.fab$b_dns = 0;s5   ofab.fab$b_fac = FAB$M_BIO | FAB$M_PUT | FAB$M_TRN;    ofab.fab$b_shr = FAB$M_NIL;9"   ofab.fab$l_alq = ifab.fab$l_alq;"   ofab.fab$w_deq = ifab.fab$w_deq;"   ofab.fab$b_org = ifab.fab$b_org;"   ofab.fab$b_rat = ifab.fab$b_rat;"   ofab.fab$b_rfm = ifab.fab$b_rfm;"   ofab.fab$w_mrs = ifab.fab$w_mrs;"   ofab.fab$l_mrn = ifab.fab$l_mrn;"   ofab.fab$b_bks = ifab.fab$b_bks;"   ofab.fab$b_fsz = ifab.fab$b_fsz;"   ofab.fab$w_gbc = ifab.fab$w_gbc;  $   bzero((char*)&onam, sizeof(onam));   onam.nam$b_bid = NAM$C_BID;l   onam.nam$b_bln = NAM$C_BLN;y   onam.nam$l_esa = oexpand;o    onam.nam$b_ess = NAM$C_MAXRSS;   onam.nam$l_rsa = oresult;d    onam.nam$b_rss = NAM$C_MAXRSS;   onam.nam$l_rlf = &inam;"   /*:  * Fill in the invariant data for truncating output files.  */l'   atrlst[0].atr$w_size = ATR$S_RECATTR;n'   atrlst[0].atr$w_type = ATR$C_RECATTR;. #if __ALPHA    atrlst[0].atr$l_addr = &fat; #else ,   atrlst[0].atr$l_addr = (unsigned int)&fat; #endif     atrlst[1].atr$w_size = 0;l   atrlst[1].atr$w_type = 0;o   atrlst[1].atr$l_addr = 0;r  &   fibdsc.dsc$w_length  = FIB$C_LENGTH;'   fibdsc.dsc$b_dtype   = DSC$K_DTYPE_T;t'   fibdsc.dsc$b_class   = DSC$K_CLASS_S;l%   fibdsc.dsc$a_pointer = (char*)&fib;e   /*  * Get an event flag.o  */,   lib$get_ef(&iefn);   if (iefn < 0) iefn = 32;   /*&  * Parse the input file specification.  */    status = sys$parse(&ifab);   if (!(status & 1))   {n     unsigned int msgvec[3];      msgvec[0] = 2;     msgvec[1] = ifab.fab$l_sts;      msgvec[2] = ifab.fab$l_stv;o@     printf("Could not parse input file specification \"%s\".\n",	 argv[1]);      sys$putmsg(msgvec,0,0,0);h     return status;   }l   /*"  * Search for the next input file.  */s!   iexpand[inam.nam$b_esl] = '\0'; "   printf("Search: %s\n", iexpand);*   while ((status = sys$search(&ifab)) & 1)   {-#     iresult[inam.nam$b_rsl] = '\0'; $     printf("Reading %s\n", iresult);   /*/  * Open the input file (with implicit display).E  */s     xabsum.xab$l_nxt = 0;w$     ifab.fab$l_xab = (char*)&xabfhc;     ifab.fab$l_ctx = 0;g+     ifab.fab$l_fop = FAB$M_NAM | FAB$M_UPI;      status = sys$open(&ifab);5     if (!(status & 1))     {-       unsigned int msgvec[3];S       msgvec[0] = 2;!       msgvec[1] = ifab.fab$l_sts;V!       msgvec[2] = ifab.fab$l_stv;C-       printf("Could not open input file.\n");g       sys$putmsg(msgvec,0,0,0);p       continue;v     }    /*>  * Get all available information on file allocation and areas.  */ :     ifab.fab$l_xab = xabsum.xab$l_nxt = (char*)&xaball[0];@     for (ibuf=0; (ibuf<xabsum.xab$b_noa) || (ibuf == 0); ibuf++)     {$8       bzero((char*)&xaball[ibuf], sizeof(xaball[ibuf]));)       xaball[ibuf].xab$b_cod = XAB$C_ALL;t,       xaball[ibuf].xab$b_bln = XAB$C_ALLLEN;$       xaball[ibuf].xab$b_aid = ibuf;6       xaball[ibuf].xab$l_nxt = (char*)&xaball[ibuf+1];     }u     if (xabsum.xab$b_noa)i/       xaball[xabsum.xab$b_noa-1].xab$l_nxt = 0;e     else       xaball[0].xab$l_nxt = 0;   /*C  * If there are any indexes, get all of the information about them.   */a     if (xabsum.xab$b_nok)      {        if (xabsum.xab$b_noa)nA         xaball[xabsum.xab$b_noa-1].xab$l_nxt = (char*)&xabkey[0];,
       else0         xaball[0].xab$l_nxt = (char*)&xabkey[0];  1       for (ibuf=0; ibuf<xabsum.xab$b_nok; ibuf++)e       {t:         bzero((char*)&xabkey[ibuf], sizeof(xabkey[ibuf]));+         xabkey[ibuf].xab$b_cod = XAB$C_KEY;u.         xabkey[ibuf].xab$b_bln = XAB$C_KEYLEN;&         xabkey[ibuf].xab$b_ref = ibuf;+         xabkey[ibuf].xab$l_knm = knm[ibuf];i8         xabkey[ibuf].xab$l_nxt = (char*)&xabkey[ibuf+1];       }i/       xabkey[xabsum.xab$b_nok-1].xab$l_nxt = 0;u     }e   /*>  * Display the additional information about allocation, areas, indexes.  */r      status = sys$display(&ifab);     if (!(status & 1))     {a       unsigned int msgvec[3];        msgvec[0] = 2;!       msgvec[1] = ifab.fab$l_sts; !       msgvec[2] = ifab.fab$l_stv;e<       printf("Could not display input file information.\n");       sys$putmsg(msgvec,0,0,0);s       sys$close(&ifab);r       continue;o     }e   /*  * Close the input file.  */e     ifab.fab$l_xab = 0;e     status = sys$close(&ifab);     if (!(status & 1))     {h       unsigned int msgvec[3];i       msgvec[0] = 2;!       msgvec[1] = ifab.fab$l_sts;v!       msgvec[2] = ifab.fab$l_stv;n.       printf("Could not close input file.\n");       sys$putmsg(msgvec,0,0,0);        continue;n     }    /*+  * Show area and index information, if any.   */d/     for (ibuf=0; ibuf<xabsum.xab$b_noa; ibuf++)-;       printf("Area %03u; %0u blocks; %0u-block buckets.\n",m         xaball[ibuf].xab$b_aid,.         xaball[ibuf].xab$l_alq,m          xaball[ibuf].xab$b_bkz);  /     for (ibuf=0; ibuf<xabsum.xab$b_nok; ibuf++)-:       printf("Key  %03u; LAN %03u; IAN %03u; \"%.*s\".\n",A         ibuf, xabkey[ibuf].xab$b_lan, xabkey[ibuf].xab$b_ian, 32,s knm[ibuf]);j   /*?  * Re-open the input file, UFO this time (accessed on user-modes	 channel).c  */8      ifab.fab$l_fop |= FAB$M_UFO;     status = sys$open(&ifab);e     if (!(status & 1))     {5       unsigned int msgvec[3];c       msgvec[0] = 2;!       msgvec[1] = ifab.fab$l_sts;t!       msgvec[2] = ifab.fab$l_stv;l:       printf("Could not access input file on channel.\n");       sys$putmsg(msgvec,0,0,0);-       continue;e     }1   /*C  * Create the output file, using the RMS extended attribute blocks.f  *//$     ofab.fab$l_xab = (char*)&xabfhc;     ofab.fab$l_ctx = 0;47     ofab.fab$l_fop = FAB$M_CBT | FAB$M_MXV | FAB$M_OFP;o$     ofab.fab$l_alq = ifab.fab$l_alq;$     ofab.fab$b_org = ifab.fab$b_org;$     ofab.fab$b_rat = ifab.fab$b_rat;$     ofab.fab$b_rfm = ifab.fab$b_rfm;$     ofab.fab$w_mrs = ifab.fab$w_mrs;     status = sys$create(&ofab);t     if (!(status & 1))     {        unsigned int msgvec[3];        msgvec[0] = 2;!       msgvec[1] = ofab.fab$l_sts;n!       msgvec[2] = ofab.fab$l_stv;s0       printf("Could not create output file.\n");       sys$putmsg(msgvec,0,0,0);i       sys$close(&ifab);i       continue;      }h   /*F  * If the total allocation of the output file is less than that of theF  * input file, extend it to match the input file.  This can happen forD  * non-sequential files when the total blocks specifically allocated to2  * each area do not result in a large enough file.  */h     ofab.fab$l_xab = 0; (     if (ofab.fab$l_alq < ifab.fab$l_alq)     {F>       printf("Extending output file allocation from %0u to %0u blocks.\n",s(         ofab.fab$l_alq, ifab.fab$l_alq);7       ofab.fab$l_alq = ifab.fab$l_alq - ofab.fab$l_alq;r!       status = sys$extend(&ofab);a       if (!(status & 1))       {b         unsigned int msgvec[3];f         msgvec[0] = 2;#         msgvec[1] = ofab.fab$l_sts;x#         msgvec[2] = ofab.fab$l_stv;x2         printf("Could not extend output file.\n");!         sys$putmsg(msgvec,0,0,0);1         sys$close(&ifab);2         sys$close(&ofab);n         continue;.       }      }    /*  * Close the output file.a  */O     status = sys$close(&ofab);     if (!(status & 1))     {u       unsigned int msgvec[3];e       msgvec[0] = 2;!       msgvec[1] = ofab.fab$l_sts;i!       msgvec[2] = ofab.fab$l_stv;u/       printf("Could not close output file.\n");@       sys$putmsg(msgvec,0,0,0);i       sys$close(&ifab);w       continue;      }   #     oresult[onam.nam$b_rsl] = '\0';t$     printf("Writing %s\n", oresult);   /*+  * Re-open the output file by NAM block andO1  * UFO this time (accessed on user-mode channel).o  */p,     ofab.fab$l_fop |= FAB$M_NAM | FAB$M_UFO;     status = sys$open(&ofab);      if (!(status & 1))     {C       unsigned int msgvec[3];        msgvec[0] = 2;!       msgvec[1] = ofab.fab$l_sts;l!       msgvec[2] = ofab.fab$l_stv;);       printf("Could not access output file on channel.\n");e       sys$putmsg(msgvec,0,0,0);c       sys$close(&ifab);i       continue;l     }r   /*@  * Set the completion event flag.  Clear outstanding I/O counts.  */a     sys$setef(iefn);     nreads_outstanding = 0;u     nwrites_outstanding = 0;     max_reads_outstanding = 0;     max_writes_outstanding = 0;e   /*-  * Start as many as <nbuffers> read requests.u  */t     for (       ibuf=0, ivbn=1; >                 ((ibuf<nbuffers) && (ivbn <= ifab.fab$l_alq));                 ibuf++)d     {A       sys$setast(0);       if (ivbn == 1)       {R         sys$clref(iefn);         lib$init_timer(0);       }R  &       piosa = (iosa*)&buffer[ibuf][0];       piosa->iosa$l_status = 1;t-       piosa->iosa$ih_count = nbytes_per_xfer;a(       piosa->iosa$q_context_q[0] = ibuf;(       piosa->iosa$q_context_q[1] = ivbn;  9       status = sys$io_perform(ifan[ibuf], ifab.fab$l_stv,A:         &buffer[ibuf][0], &buffer[ibuf][NBYTES_PER_BLOCK],         nbytes_per_xfer, ivbn);r       if (!(status & 1))       {[         sys$setast(1);F         printf("Could not start input from VBN %0d to buffer #%0d.\n",                 ivbn, ibuf);         return status;       }r       ivbn += nblocks_per_xfer;r       nreads_outstanding++;r       sys$setast(1);     }r   /*2  * Wait for the disk reads and writes to complete.  */x     sys$waitfr(iefn);-     lib$show_timer(0);<     printf("     Total Fast I/O Reads: %0d; Writes: %0d.\n",(         ifab.fab$l_ctx, ofab.fab$l_ctx);<     printf("Maximum Outstanding Reads: %0d; Writes: %0d.\n",7         max_reads_outstanding, max_writes_outstanding);    /*  * Deassign the input channel.  */_(     status = sys$dassgn(ifab.fab$l_stv);     if (!(status & 1))     {t4       printf("Could not deassign input channel.\n");       return status;     }a   /*D  * Completely re-initialize the file information block.  The file ID andiA  * directory ID fields must be zeroed, or the XQP will attempt to_ truncateB  * and modify the attributes of the *original* or *previous* file, *not*n6  * the file that is currently accessed on the channel.  */($     bzero((char*)&fib, sizeof(fib));&     fib.fib$l_acctl = FIB$M_WRITETHRU;"     fib.fib$w_exctl = FIB$M_TRUNC;     fib.fib$l_exsz  = 0;'     fib.fib$l_exvbn = xabfhc.xab$l_ebk; ,     if (xabfhc.xab$w_ffb) fib.fib$l_exvbn++;     fib.fib$w_verlimit = 0;o     fib.fib$l_acl_status = 0;(   /*?  * Copy the file header characteristics to the file attributes.f  */u*     fat.fat$b_rtype    = xabfhc.xab$b_rfo;*     fat.fat$b_rattrib  = xabfhc.xab$b_atr;*     fat.fat$w_rsize    = xabfhc.xab$w_lrl;9     fat.fat$w_hiblkl   = xabfhc.xab$w_hbk0; /* ignored */ 9     fat.fat$w_hiblkh   = xabfhc.xab$w_hbk2; /* ignored */t+     fat.fat$w_efblkl   = xabfhc.xab$w_ebk0;f+     fat.fat$w_efblkh   = xabfhc.xab$w_ebk2;_*     fat.fat$w_ffbyte   = xabfhc.xab$w_ffb;*     fat.fat$b_bktsize  = xabfhc.xab$b_bkz;*     fat.fat$b_vfcsize  = xabfhc.xab$b_hsz;*     fat.fat$w_maxrec   = xabfhc.xab$w_mrz;*     fat.fat$w_defext   = xabfhc.xab$w_dxq;*     fat.fat$w_gbc      = xabfhc.xab$w_gbc;/     fat.fat$w_versions = xabfhc.xab$w_verlimit;    /*   * Modify and truncate the file.  */ C     status = sys$qiow(iefn, ofab.fab$l_stv, IO$_MODIFY, iosb, 0, 0, .                 &fibdsc, 0, 0, 0, &atrlst, 0);%     if (status & 1) status = iosb[0];l     if (status & 1)t     {=A       printf("Output file truncated at VBN %0u by %0u blocks.\n",s1                 fib.fib$l_exvbn, fib.fib$l_exsz);c>       printf("New end-of-file block is %0u, first free byte is %0u.\n",4                 xabfhc.xab$l_ebk, xabfhc.xab$w_ffb);     }i     else     {]E       printf("Could not truncate output file to EBK %0u, FFB %0u.\n", 4                 xabfhc.xab$l_ebk, xabfhc.xab$w_ffb);     }    /*  * Deassign the output channel.f  */ (     status = sys$dassgn(ofab.fab$l_stv);     if (!(status & 1))     {i5       printf("Could not deassign output channel.\n");e       return status;     }     } /* input file search loop */  ,   if ((status != RMS$_NMF) && !(status & 1))   {1     unsigned int msgvec[3];s     msgvec[0] = 2;     msgvec[1] = ifab.fab$l_sts;o     msgvec[2] = ifab.fab$l_stv; 1     printf("Could not search for input file.\n");      sys$putmsg(msgvec,0,0,0);    }    /*,  * Clean up after <nbuffers> buffer objects.2  * This apparently gets done at image exit anyway.  */=%   for (ibuf=0; ibuf<nbuffers; ibuf++)    {e(     status = sys$io_cleanup(ifan[ibuf]);     if (!(status & 1))     {iB       printf("Could not clean up input for buffer #%0d.\n", ibuf);       return status;     }p  (     status = sys$io_cleanup(ofan[ibuf]);     if (!(status & 1))     {eC       printf("Could not clean up output for buffer #%0d.\n", ibuf);t       return status;     }e  ,     status = sys$delete_bufobj(iohan[ibuf]);     if (!(status & 1))     {a=       printf("Could not delete buffer object #%0d.\n", ibuf);h       return status;     }    }f   return status; } /* fast_io_copy() */   ------------------------------  % Date: Sun, 16 Apr 2000 02:55:06 -0400a* From: David A Froble <davef@tsoft-inc.com>T Subject: Re: How can you find the exact size of a file in bytes using a  VMScommand?- Message-ID: <38F963CA.69980258@tsoft-inc.com>+   "Richard B. Gilbert" wrote:[ > G >         First, you have to define exactly what you mean by the "exact H > size"!  Do you want the number of bytes of your data?  Do you want theK > number of bytes between the beginning of the file and the last byte?  TheiI > two numbers can be, but are not necessarily, the same.  Variable length!K > records are preceded by a two byte count and may be  padded with a NUL to<M > make an even number of characters in each record.  VFC records, or VariablelJ > length with fixed control string, have even more metadata.  Fixed lengthG > records have no metadata and the number of bytes per record times thex/ > number of records yields the length in bytes.   H It's been a long time, but I thought that all RMS record types, with theN exception of block I/O had some additional data as part of the record, but notL visable to the user.  This included relative fixed records.  As I said, it's% been a long time, and I may be wrong.t  M >         ANALYZE /RMS MUMBLE.TXT will give you the VBN of the block containg L > the last byte and the offset into that block of the last byte.   From thatK > you can calculate the number of bytes your file occupies on disk.  Such a L > number is rarely relevant because disk space is allocated in clusters and,L > if your cluster size is nine blocks, an empty file or a file with only oneK > byte of data will occupy nine blocks or 4608 bytes of disk no matter whatKL > you do.  If your record format is "Fixed Length" you are finished.  If theJ > record format is something else the only way to find the exact number ofA > bytes is to read the file and count the bytes as you read them!= > M >         Just out of curiosity, what problem are you really trying to solve?sL >  Unix weenies concern themselves with counting the number of characters orK > "words" (natural language) in a file but I've never understood why anyone 
 > would care!l >  > Message text written by RickE > >Sorry to ask such a stupid question, but I have been searching anddG > connot figure it out. I want to know the exact size (number of bytes)(A > of a(ny) file in VMS? Is it possible or is the finest degree ofm* > granularity a block?  Thanks in advance. >  > <S   Dave   -- *4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596; 170 Grimplin Road               E-Mail: davef@tsoft-inc.comm Vanderbilt, PA  15486F   ------------------------------  # Date: Sun, 16 Apr 2000 15:08:44 GMTs From: Rick <rw712@my-deja.com>T Subject: Re: How can you find the exact size of a file in bytes using a VMS command?( Message-ID: <8dcl1l$k0$1@nnrp1.deja.com>  / In article <38F90E02.E81D69A8@vl.videotron.ca>,n3   JF Mezei <jfmezei.spamnot@vl.videotron.ca> wrote:  > "Richard B. Gilbert" wrote:;E > >         Just out of curiosity, what problem are you really trying 	 to solve?t@ > >  Unix weenies concern themselves with counting the number of
 characters orbF > > "words" (natural language) in a file but I've never understood why anyone > > would care!p >FF > I didn't ask the original question, but many file transfer protocols expectA > that the file's sender will tell the receiver how many bytes to0
 expect (toG > ensure that the receiver can store a file of that size for instance).N >9G > In the days where emails were billed by character, this was important  too. >b> The reason I asked the question was to determine if a file wasB transfered to a VMS box correctly using FTP. It was an Oracle dumpD file, and the individual transfered the file using ASCII mode. Well,F that did a bit of translation on it's own, which would modify the fileF (such as converting CRNL to NL), but not so much as to change the sizeF of the file by a number of blocks. How could I tell easily if the fileG had been altered? Oh, I did not expect this person to transfer a binarysF file use text mode... It took quite a while to figure out that was the. cause of the odd messages in loading the dump.   Thanks for the responses.R    & Sent via Deja.com http://www.deja.com/ Before you buy.H   ------------------------------  % Date: Sun, 16 Apr 2000 09:34:13 -0400n# From: dONo <studiodoc@netscape.net>t Subject: M38 VS for sale, Message-ID: <38F9C155.AF4B6A87@netscape.net>  : We're moving, got 2 of these, both w 1Gig and 32 megs ram.   Make offer!D   ------------------------------  % Date: Sun, 16 Apr 2000 15:24:16 +0300= From: "subZ" <subz@sci.fi>% Subject: Re: Maximum Password Lengthse& Message-ID: <8dcbs5$g07$1@tron.sci.fi>  @ "Amiri Jones" <MyFirstName.MyLastName@pseg.com> wrote in message1 news:uCWjU7Vp$GA.196@cppssbbsa02.microsoft.com...t >g? > Michael D. Ober <mdo.@.wakeassoc.com.nospam> wrote in message A > news:u5lJ4.13133$q67.403510@newsread2.prod.itd.earthlink.net...iI > > What is the maximum user password length on VMS 7.2, and NT 4 Domain,  andu > aaA > > Win 2000 Active Directory?  I need information for all three.n > >mH >     The only one I can say for sure is NT 4; maximum is 14 characters. I'ms@ > not at my Win2K machine right now, and I've never used VMS.... >  >n  ! Copy - Paste from the Win2k Help:*  L Windows 2000 passwords can be up to 127 characters long. However, if you areK using Windows 2000 on a network that also has computers using Windows 95 orbK Windows 98, consider using passwords not longer than 14 characters. WindowstL 95 and Windows 98 support passwords of up to 14 characters. If your passwordC is longer, you may not be able to log on to your network from those 
 computers.     subZ   ------------------------------  # Date: Sun, 16 Apr 2000 08:34:07 GMTv" From: psy@get2net.dk (Bent Wagner)% Subject: Need OpenVMS-VAX 6.2 on TK50a/ Message-ID: <38f97903.43295730@news.get2net.dk>   
 Hello all.  F I have a MicroVAX 3100/30 where the harddisk went dead. I got myself aD new harddisk (1Gb), but i don't have a CD-ROM drive to install from.  0 I have a HP2040i CD-R but i won't boot my CDROM.  F Looking thru my hardware stuff, i found the TZ30 drive, which the uVAX
 came with.  A I don't have any tapes for the drive, the company who gave me then? machine wouldn't give me any. They contain backup data i guess.     5 Can anyone help me with an OpenVMS VAX  V6.2 on TK50?n   Yourst   Bent Wagnero psy@get2net.dk   ------------------------------  # Date: Sun, 16 Apr 2000 05:52:21 GMTa3 From: Eric Dittman <dittman@narnia.int.dittman.net>h  Subject: PC164 serial port speed> Message-ID: <pycK4.3405$I75.116479@news-east.usenetserver.com>  4 I've tried setting COM1_BAUD and COM2_BAUD in SRM to1 change the console serial port speed on my PC164, 2 but the variable doesn't last past the INIT.  Does3 the PC164 support a console serial port speed othery4 than 9600, and if so, how do I set it?  And if I set/ the speed to 19200 or 38400, will VMS allow it?=  9 On the subject of SRM, does anyone have any documentation_, on some of the variables like d_* and srm2*?   -- a Eric Dittman dittman@dittman.neti   ------------------------------  + Date: Sun, 16 Apr 2000 12:11:14 -0400 (EDT)1" From: Dan Sugalski <dan@sidhe.org>E Subject: Safe Shipping (was Re: Warning: circuitsurgeon is a ripoff!) H Message-ID: <Pine.LNX.4.10.10004161203360.30413-100000@tuatha.sidhe.org>  $ On Sun, 16 Apr 2000, Beyonder wrote:B > > However, just because it arrived in a defective state does not$ > > mean it was defective when sent. > C > ah but in this case it does. if you knew anything about shipping,13 > packing, and "drop tests" you might realize this.v  D Ummm, no. I worked for UPS for two years in one of the hubs, loadingJ trucks. There is *no* way to package something with moving parts that willC ship UPS (or any of the other major carriers) that can't be broken.dJ Period. Drives can easily be broken in a half-dozen different ways withoutE sign of external damage and if the box was scuffed or showed signs of G wear? Forget it. *Especially* if the drive was mounted in a system. UPSaB can also destroy and damage the info on magnetic media without any indication of trouble.  B Compaq's storageworks packaging is pretty good, and a shipper'd beE hard-pressed to damage them without leaving any sign, but even that'sn	 possible.f   				Dani   ------------------------------  % Date: Sun, 16 Apr 2000 03:01:52 -0400$* From: David A Froble <davef@tsoft-inc.com>. Subject: Re: Shock, horror! An OpenVMS advert!- Message-ID: <38F96560.9F7E4D45@tsoft-inc.com>1   Larry Kilgallen wrote: > i > In article <38F7D95B.8A91D902@earthlink.net>, "David J. Dachtera" <djesys.nospam@earthlink.net> writes:g > > Sue Skonetski wrote: > >>
 > >>  Ade, > >>P > >> This is Sue Skonetski from the OpenVMS Group, send me your name and address% > >> and I will get a few out to you.b > >x > > Sue, > >b+ > > Never mind "preaching to the choir" !!!P > > J > > Get these ads on billboards, buses, bus benches, magazines (especiallyK > > NT, WhineDoze-2000Bugs and UN*X trade rags!) and especially network and # > > cable television in prime time.  > >s? > > The faithful already have the message. The infidels do not!i > A > So send the name and address of an infidel to Sue Skonetski !!!l > > > She will never know the difference (unless the name you send > is Scott McNealy :-).   M I think that Scott should be a receipient, along with our good friend Andrew.    Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596; 170 Grimplin Road               E-Mail: davef@tsoft-inc.come Vanderbilt, PA  15486l   ------------------------------    Date: 16 Apr 2000 17:01:20 +0200* From: eplan@kapsch.net (Peter LANGSTOEGER)# Subject: Re: signature file in MAIL * Message-ID: <38f9d5c0$1@news.kapsch.co.at>  [ In article <8d1hi3$qgs$1@info.service.rug.nl>, helbig@astro.rug.nl (Phillip Helbig) writes:qY >In article <38f39ecf$1@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes: s >1, >> 2) MAIL/OLD (eg. via symbol in LOGIN.COM) > G >That's it!  I use MAIL/OLD because the XLATE stuff in EDT doesn't workcC >with the new MAIL (enables me to SPAWN out of EDT when it has been\ >called from MAIL).   F Why don't you use TPU ? A small customization file and it behaves likeC EDT but a lot better and faster and with X11/mouse support and witheI screens bigger than 24x80 and doesn't restore a scrolling region to 24x80 N but clears the scrolling region at exit and so on. Get serious and discard EDT  ( >Why was MAIL rewritten?  (Was it in C?)  M Don't know. Maybe it was hype. Maybe the fired the good/former VMS developersi= and got only newbie/C-only then. And therefore it was in C...s   >When will this be fixed?   = Just like a lot of some other VMS mail bugs: Proably never...   H >I mean, introducing the /OLD qualifier is rather embarrassing since it I >admits there is a need to use it.  (OK, it's not documented, but still.)o  H MAIL/OLD was documented (at least in the release notes of the version it9 introduced). I saw it then, but now can't double-check...  -- c< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888 < FBFV/Information Services           E-mail  eplan@kapsch.netF <<< KAPSCH AG  Wagenseilgasse 1     PSImail PSI%(0232)281001141::EPLANH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"N "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998   ------------------------------  # Date: Sun, 16 Apr 2000 17:28:51 GMTn8 From: Veli =?iso-8859-1?Q?K=F6rkk=F6?= <korkko@decus.fi>: Subject: Re: Too Few Servers Detected from: Node LOCAL....( Message-ID: <38F9F62A.BA81E21F@decus.fi>  C And I would like to note that since OpenVMS V7.1, if the DTSS clerkiG does not actually see any time servers around (as opposed to "too few")i? it actually allows using $SET TIME command. It will dynamicallyxC disable/enable $SET TIME based on whether it actually sees any timet servers around.r   Also, the NCL commands  > block event dispatcher local sink local_stream global filter - 	((Node,DTSS),Too Few Servers)   should best placed in  file   ' 	sys$common:[sysmgr]net$event_local.nclf   which can be created using N  % 	sys$manager:net$event_local.template   > as a base. Latest versions of DECnet/Plus also actually honourC system level logical NET$EVENT_LOCAL and will execute pointed file. 4 Very handy if managing multiple system disk cluster.   _veli    Wayne Sewell wrote:f > h > In article <005401bfa62d$b6c583c0$0100a8c0@oliver1>, "Miles D. Oliver" <moliver@linux.lgi.com> writes:K > > After upgrading to OpenVMS system from 7.1 to 7.2-1  I am now getting a0@ > > strange error meesage that I havent seen in the operator.log > > < > > %%%%%%%%%%%  OPCOM  14-APR-2000 12:20:19.71  %%%%%%%%%%%& > > Message from user SYSTEM on MDSLB2B > > Event: Too Few Servers Detected from: Node LOCAL:.MDSLB2 DTSS,1 > >         at: 2000-04-14-12:20:19.715-04:00Iinfi > >         Number Detected=0, > >         Number Required=1c; > >         eventUid   0ADCAAD7-11FF-11D4-9B48-4D44534C4232r; > >         entityUid  00DAF636-115B-11D4-8142-AA0004000204e; > >         streamUid  001FCB76-115B-11D4-812D-AA0004000204o > >  > >eJ > > I cannot seem to figure it out. I have no clue what is generating this
 > > error. > >i% > > Could anybody assist me on this??i > >x > P > from the faq (your specific question is answered near the end of the section): > > > ------------------------------------------------------------A > MGMT7.  Why can't I do a SET TIME command?  Help managing DTSS?r > F > If you try to set the system time with the SET TIME command, and see  > one of the following messages: > % > %SET-E-NOTSET, error modifying timea2 > -SYSTEM-F-IVSSRQ, invalid system service request > % > %SET-E-NOTSET, error modifying time2M > -SYSTEM-E-TIMENOTSET, time service enabled; enter a time service command tof > update the time$ > P > A: This occurs if the time on the local system is controlled by a time serviceP > software, for example the distributed time service software (DTSS) provided asQ > part of the DECnet/OSI installation. The DTSS software communicates with one or N > more time servers to obtain the current time. It entirely controls the localM > system time (for DECnet/OSI, there is a process named DTSS$CLERK for this);vQ > therefore, the usage of the SET TIME command (and the underlying $SETTIM system( > service) is disabled.[ > P > The first message is displayed on systems running DECnet/OSI V6.1 and earlier.O > On systems with newer DECnet/OSI (DECnet-Plus) software, the second (and moref  > informative) message is given. > K > You shouldn't have to change the time manually - you should be doing this O > through the time server - but if you insist...  you'll have to shutdown DTSS:, >  > $ MCR NCL  > NCL> DISABLE DTSSx > NCL> DELETE DTSS > N > This will shutdown DTSS$CLERK. You may then change the system time as usual.$ > To restart the DTSS software, type >  > @SYS$STARTUP:DTSS$STARTUPl > O > You'll need a lot of privs : (CMKRNL,SYSPRV,OPER,SYSNAM,PRMMBX,NETMBX,LOG_IO, F > ALTPRI) and must be granted the NET$MANAGE identifer to shutdown and > restart DTSS.gA >                                         [bol@adv.magwien.gv.at]  > P > If you wish to "permanently" disable DTSS on a system running DECnet-Plus, theL > above NCL sequence must be performed each time the system is bootstrapped. > O > If DTSS is running and no time servers are configured, you can (and will) see<. > the following messages at regular intervals: > : > %%%%%%%%%%%  OPCOM   2-SEP-1999 19:41:20.29  %%%%%%%%%%%$ > Message from user SYSTEM on UNHEDI@ > Event: Too Few Servers Detected from: Node LOCAL:.mynode DTSS,/ >         at: 1999-09-02-19:41:20.296-04:00Iinf  >         Number Detected=0, >         Number Required=1#9 >         eventUid   5FA70F4F-616E-11D3-A80E-08002BBEDB0Fs9 >         entityUid  DE9E97DE-6135-11D3-8004-AA000400BD1B 9 >         streamUid  D6513A46-6135-11D3-8003-AA000400BD1Bn > M > You can either configure the appropriate number of time servers, or you can(I > disable DTSS, or you can ignore it and (if OPCOM is set to write to the0L > log via via the logical names in SYLOGICALS.COM/SYLOGICALS.TEMPLATE) clean > out OPERATOR.LOG regularly.y > < > You can also simply disable the display of these messages: > O > $ mcr ncl block event dispatcher outbound stream local_stream global filter -l. >     ((Node, DTSS), Too Few Servers Detected) > B >                                                   [Wayne Sewell] > > > ------------------------------------------------------------ > ; >   The OpenVMS FAQ is archived in the following locations:n > < >     http://www.openvms.digital.com/wizard/openvms_faq.html; >     ftp://ftp.digital.com/pub/Digital/dec-faq/OpenVMS.txt 3 >     ftp://ftp.digital.com/pub/Digital/dec-faq/vmse< >     ftp://rtfm.mit.edu/pub/usenet/news.answers/dec-faq/vms. >     comp.answers and news.answers newsgroups > C >   Other internet FAQs are generally available in these locations:  > . >     comp.answers and news.answers newsgroups' >     ftp://rtfm.mit.edu/pub/usenet/...I > A >   User-created HTML versions of the OpenVMS FAQ are located at:t >   >     http://www.kjsl.com/vmsfaq) >     http://eisner.decus.org/vms/faq.htme >  > --Q > ===============================================================================kM > Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachyon.xxxF8 > http://www.tachyon.xxx/www/tachyon.html and wayne.htmlM > change .xxx to .com in addresses above, assuming you are not a spambot  :-) Q > =============================================================================== P > Butler:"Gentlemen!"  Curly(as he and other Stooges look around):"Who came in?"   ------------------------------  # Date: Sun, 16 Apr 2000 10:18:00 GMTa( From: Terry Kennedy <terry@gate.tmk.com>1 Subject: Re: Warning: circuitsurgeon is a ripoff! ' Message-ID: <Ft3ty1.48G@spcuna.spc.edu>   * This will be my last post on this topic...  4 In comp.org.decus Beyonder <beyonder@vrx.net> wrote: > Terry Kennedy wrote:M >>   Was bad, or went bad? I'm sorry, this story has too many holes in it fort >> me to believe you.e >t@ > was bad. what holes? speak up, show your proof, not just talk!  >   Your exact words (from article <38F1DBF1.1BECEB2A@vrx.net>):  + | NO, the board went bad TWO *DAYS* later!!o | then discovered board is bad.   M >>   I also don't find it credible that you waited 8 months to have the boarde: >> evaluated by Compaq and then to purchase a replacement. >aO > I didn't wait eight months! jeezes you people just don't read. I notified mr.eK > circuitsurgeon immediately! (same DAY!) it only took eight months for him 
 > to respond..     Again, your exact words:  L | 8 months later: final contact with circuitsurgeon: refusal to do anything.K | circuitsurgeon "offers" to rip me off again by selling me an io board foriK | $200 Take unit into compaq/dec on insistance that "nothing is wrong with   | it" by circuitsurgeon.  * >>   Hopefully you've learned some things: >>P >>   1) Deal with people you've heard are reputable (I can't say anything eitherN >>      way about circuitsurgeon, I've never heard of him/her/them/it before). >c  > definitely NOT circuitsurgeon.  H   Had you heard about circuitsurgeon before you started the transaction?I How about Newman Computer / ELI / Digital Basics / etc., all of whom haveiH a long-standing reputation and sell this type of used equipment? Did youJ do any comparison of prices and availability before ordering from circuit- surgeon?  M >>   2) Use a payment method where you can dispute the charges (like a creditw >>      card). >cL > and if they don't accept credit card, you're screwed. and even if they do,4 > it's still called fraud. and very hard to dispute.  I   I believe all of the 3 folks above accept credit cards. And there are aiG number of Internet escrow services around (which I've never used, so I iH can't comment on whether they would have accepted this particular trans- action).  N >>   3) If there is a problem, get it addressed early. At least in the US, youL >>      will lose some of your rights to dispute/complain/etc. by waiting. 2M >>      weeks is a good maximum time to wait before disputing, and you shouldf* >>      have it wrapped up within a month. >sL > I tried! I called every day, I emailed every day. He either hung up on me,0 > never called back, or I was basically ignored.  @   But you let it go on for over 8 months, by your own admission.  J >>   4) Acting as your own importer/exporter is a pain. Avoid it if at allK >>      possible by buying/selling within your own country, or at least use-M >>      the services of a good customers expediter, so you don't wind up pay-sO >>      ing multiple duty/tax on stuff going back and forth for repair/replace-0
 >>      ment.> > E > good luck. thats even MORE of a pain. brokerage fees are not cheap.uL > and I prefer using a real courier. besides, in canada, there are basicallyJ > really no sources for this stuff at all, same can be said for many other > countries.  I   I have repaired a number of items for people in Canada. It's relativelyNI simple and inexpensive to have an expediter handle the paperwork for you,nH and certainly less than paying the duties for the back-and-forth. On theI other hand, if your object is to wail about how much money you lost, then : paying repeated shipping and customs fees certainly helps.  E > Your logic seems to come down to: don't deal outside your own town, ! > and deal with someone you know.  >w# > which eliminates almost everyone.d  J   No, it's "don't deal outside your country if you can avoid it" and "dealI with someone who has been in business for many years and whose reputationyG is known (like the folks on the list I gave above). Along with my otheroI two recommendations - pay with a credit card (or only partial payment be-uG fore you receive and inspect the item) and take decisive action as soon:G as you know the item is defective and are unable to resolve it with thee seller.   I   If you don't follow those rules, you might get screwed. You flipped they/ coin and lost. Sorry, but that's the way it is.-  E   Regardless of which is more emotionally satisfying to you, which isDG better - your attempt to warn people about one particular vendor, or my > suggestions for how to avoid being ripped off by *any* seller?  - 	Terry Kennedy             http://www.tmk.coma5         terry@tmk.com             Jersey City, NJ USAh   ------------------------------  # Date: Sun, 16 Apr 2000 14:53:43 GMT@ From: hobbsb@my-deja.com1 Subject: Re: Warning: circuitsurgeon is a ripoff!2) Message-ID: <8dck5i$vsq$1@nnrp1.deja.com>i  M Dan, you've given your warning.  If folk decide not to heed it, that is their1I decision - you will waste a lot of time and energy trying to change theirAG minds.	Besides, when they see CircuitSurgeon, they'll probably stop and 6 think of you.  Please stop increasing the noise level.      & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Sun, 16 Apr 2000 09:27:23 +0200 $ From: Paul Sture <sture.ch@sture.ch>? Subject: Re: Why are there no French people in this newsgroup ?n* Message-ID: <VA.00000004.04efbb1b@peacock>   > Newsgroups: comp.os.vms-4 > From: kilgallen@eisner.decus.org (Larry Kilgallen)A > Subject: Re: Why are there no French people in this newsgroup ?(- > Reply-To: Kilgallen@eisner.decus.org.nospam % > Date: Wed, 12 Apr 2000 12:46:19 GMT6 >  1b > In article <dZYI4.74807$1C2.2213157@news20.bellglobal.com>, "Neil Rieck" <n.rieck@sympatico.ca>  writes:  >  tP > > Sysops in Quebec in love Solaris and it's probably because of the good multiO > > language support. On the flip side, I'm seeing an increase in the number of G > > web sites running or supporting OpenVMS in France and Germany. ManyfN > > Europeans disillusioned by the realities of Linux are moving (slowly) backP > > to English oriented OpenVMS. (If you learned English in school, you've got aJ > > better chance of running an OpenVMS system where the commands and help > > system are meaningful) >  f< > VMS has great capabilities for working in other languages,= > but DEC never put the effort in (like Apple does) to timelyd= > release of language variants that have all the commands anda* > help text translated to other languages. >  nd A shame that effort wasn't put in. OTOH, English only makes support much easier for me at least ;-) e Back when I was supporting stuff which had localised language interfaces, if the support person with 0e the right language skills didn't know the answer, they would translate the problem into English, and - then everyone could pitch in.c  ; > An interesting parallel discussion in comp.lang.ada about9; > the fact that Ada keyword are in English found many whoseh= > native language is _not_ English saying they even preferred ; > the keywords for Ada being in English since it made quite = > an obvious distinction that these were keywords rather thanb? > being just some natural language word in their native tongue.!  c My Swiss German boss claims that he doesn't like English (although he's pretty good at it), but he - prefers to program in English.  
 Paul Sture Switzerland    ------------------------------   End of INFO-VAX 2000.213 ************************ infidels do not!i > A > So send the name and address of an infidel to Sue Skonetski !!!l > > > She will never know the difference (unaFa/@                          `v,  ` `     

߫4   vaW`t`Jޜanak  $    `Jޭ`J`K 



a.@a[



























































































Vx   vaW`B`Jޜamal`   T    `J



`J`K 



























































































































































Vx   vaW`B`Jޜanpal`   H    `J



`J`2X



































































































































Vx   JaY`B`J8anal`       `J<`J<`L



ab.











4   vaW`٤`1Lao$al`      



    y     }   Z           



























߫4   ma[xa
`x8aoanЀ  6   `L!aaaoaKa[ SIMWAN                                                                           ߫4   ma[xa
`x8apLao8  6   `ada@aaoLa[ 
DL3800_CO