0 INFO-VAX	Tue, 10 Jan 2006	Volume 2006 : Issue 19      Contents:' Re: Beginner: nesting DCL command files / Re: foreign commands, .com files, and dcltables / Re: foreign commands, .com files, and dcltables & Re: Free to a good home: OSF/1 manuals  Re: Free: AlphaServer 2100 5/250- Re: Great new antivirus software for windoze! ( How to prevent users from telnet-login ?, Re: How to prevent users from telnet-login ?, Re: How to prevent users from telnet-login ? Re: HP's strategy explained : $ Re: HSZTerm under newer VMS versions$ Re: HSZTerm under newer VMS versions# Re: Java 1.4.2 installation problem  Re: KVM Switches Re: KVM Switches Re: KVM Switches Re: KVM SwitchesP Large Amount of Upper Case Alert!!! Re: foreign commands, .com files, and dcltabB Re: Search loop gets file while still being written - How to avoidB Re: Search loop gets file while still being written - How to avoidG Search loop gets file while still being written - How to avoid conflict K Re: Search loop gets file while still being written - How to avoid conflict P Re: Search loop gets file while still being written - How to avoid conflict confP Re: Search loop gets file while still being written - How to avoid conflict conf- Suggestion for INSTALL PURGE and SHUTDOWN.COM + Re: WVNETcluster uptime reaches 10 years...   F ----------------------------------------------------------------------  % Date: Mon, 09 Jan 2006 20:17:16 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>0 Subject: Re: Beginner: nesting DCL command files+ Message-ID: <43C3192C.B9FAAB1E@comcast.net>    Alder wrote: >  > [snip]H > Can anyone help with a pointer on where I went wrong, or what to read? >  > SYSTARTUP_VMS.COM  > =================  > ... A > $ DEFINE/SYS/EXEC/TRANS=(CONCEALED)SAMBA_ROOT DISK$NET:[SAMBA.]  > ... ! > $ @SYS$STARTUP:STARTUP_PRODUCTS  > , > SYS$STARTUP:STARTUP_PRODUCTS.COM (level 1) > ================== > ... & > $ @SYS$STARTUP:TCPIP$DEFINE_COMMANDS# > $ @SAMBA_ROOT:[BIN]SAMBA_COMMANDS   D Well, first, you need to understand the difference between a logicalG name (can be system-wide or private to a specific process) and a symbol  (always private to a process).  G Defining these symbols in the STARTUP process does nothing because they C cannot be seen by any other process except subprocesses of STARTUP.   D TCPIP$DEFINE_COMMANDS seems to have an issue because it doesn't even* work as intended on my site. Not sure why.  G You'd want to include them in either the system-wide login-time command > procedure (pointed to by the SYS$SYLOGIN logical name, usuallyC SYS$MANAGER:SYLOGIN.COM) or in another login-time procedure that is : local to specific groups of users as defined by your site.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 09 Jan 2006 14:23:30 -0500 ' From: Dave Froble <davef@tsoft-inc.com> 8 Subject: Re: foreign commands, .com files, and dcltables0 Message-ID: <11s5e1in85jpve6@corp.supernews.com>   Jeff Cameron wrote:   > On 1/7/06 10:47 PM, in articleL > 1136702859.840797.313230@f14g2000cwb.googlegroups.com, "mabbuttg@yahoo.ca" > <mabbuttg@yahoo.ca> wrote: >  > - >>I'm fairly new to OpenVMS, so bear with me:  >>F >>A consultant implemented a process for us where several programs nowC >>call a .com file with arguments to complete some file operations.  >>I >>To make this work, we had to add a foreign command symbol definition to 6 >>our users' login scripts, similar to 'NEWPROGRAM :== >>"@[DIR]NEW_PROGRAM" '. >>E >>While we've gone through and added this symbol to what we're pretty C >>sure are all the users who are affected by this, I was doing some H >>research to see what could be done on a global level just to make sureD >>(in our setup it doesn't matter if all users have the above symbolI >>defined, as we have additional access restrictions on the programs that 4 >>call it, and most users don't have prompt access). >>I >>What I've found is some info on modifying the global DCLTABLES, using a ' >>.cld file, with the sample syntax of:  >> >> >>DEFINE VERB FOO  >>   IMAGE "SYS$SYSEXE:FOO.EXE"  >>   QUALIFIER BAR >>/ >>then adding it to the system DCLTABLES using:  >>3 >>$ SET COMMAND/TABLE=SYS$LIBRARY:DCLTABLES.EXE -_$ 9 >>/OUTPUT=SYS$COMMON:[SYSLIB]DCLTABLES.EXE NEWCOMMAND.CLD  >> >>and  >>- >>$ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE  >> >>E >>So, I have several questions on this that I can't find answers for, 	 >>namely:  >>H >>- all the examples I've seen of .cld files refer to "images", eg, .exe7 >>files - will the CDU let me do this with a .com file?  >>9 >>- if it will, I'm guessing my .cld file syntax will be:  >> >>DEFINE VERB MYPROGRAM   >>  IMAGE "@[DIR]MY_PROGRAM.COM" >>G >>as I don't have any qualifiers (just arguments).  I'm a bit unsure of I >>the syntax, as it's a .com file, and the symbol defined earlier had the 0 >>"@" in it - not sure if that's necessary here. >> >>E >>- if I do add this to the DCLTABLES, and some users have it already G >>defined in their login scripts, will this conflict in any way?  If we F >>have to change something in the future, which would take precedence? >>G >>- if for some reason I wanted to remove this entry from the DCLTABLES G >>after adding it, how can I do that?  I've only found reference to SET E >>COMMAND/DELETE, which appears to only operates on the local copy of   >>DCLTABLES, not the global one. >> >>Thanks for all suggestions.  >> >>Glenn  >> > E > As you have seen in other responses, the DCL tables and the command F > definition utility does not allow you to define commands for commandJ > procedures. This opens a rather large security hole, but that aside, theM > whole purpose of the DCL tables is to allow images to have a common command 0 > parsing method with parameters and qualifiers. > M > One other point; while you can change the actual system wide DCL tables, it N > is typically not a good idea. This is because when you upgrade or patch VMS,J > the kit my overwrite your changes. Instead (if you go the executable/CLDN > route) that you include your SET COMMAND in the system wide login procedure. > N > This is because each process that uses DCL copies the entire DCL tables intoJ > the context of the process when the process is created, so that when youB > execute the SET COMMAND it only changes the process' DCL tables. > H > But if your whole purpose is to add a new global command for a commandI > procedure, the best and most accepted method is to make a global symbol F > definition in your system wide login procedure. One other point, forL > security reasons you would typically want to assign these file protections9 > to any globally used command procedures to avoid hacks:  > = > $SET SECURITY/PROT=(S:RE,O:RWED,G:RE,W:RE) <procedure-name>  >  > Jeff >   G Agreed, with the exception for S:RE.  If a user has SYSTEM priviledge,  F that user had better be trusted, or your security is compromised.  By ? setting the system protection mask to RE, you introduce system  F management issues.  Then again, anyone doing such management probably 2 has BYPASS, and there is then no management issue.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Mon, 09 Jan 2006 20:39:18 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>8 Subject: Re: foreign commands, .com files, and dcltables+ Message-ID: <43C31E56.74B84148@comcast.net>    Jeff Cameron wrote:  > [snip]M > One other point; while you can change the actual system wide DCL tables, it N > is typically not a good idea. This is because when you upgrade or patch VMS,J > the kit my overwrite your changes. Instead (if you go the executable/CLDN > route) that you include your SET COMMAND in the system wide login procedure.  D OOOOOOOOOOOOHHHHHHHHHHHHHHH!!!!!!!!! *DEFINITELY* *NOT* a good idea!  A The answer to the question why is (almost) your next paragraph...   N > This is because each process that uses DCL copies the entire DCL tables intoJ > the context of the process when the process is created, so that when youB > execute the SET COMMAND it only changes the process' DCL tables.  H Well, that's close. Your process's command table is mapped to the sharedH command table UNLESS you issue "SET COMMAND filespec", at which time theA command tables get copied into your process's address space which > reduces the amount of working set available for code and data.  = I solved a heavy paging problem once (on VAX, I grant you) by C eliminating SET COMMANDS ins SYLOGIN and several proc.'s it invoked H becase they were no longer needed. Page faults went down and performance( increased much more than I had expected.  H > But if your whole purpose is to add a new global command for a commandI > procedure, the best and most accepted method is to make a global symbol F > definition in your system wide login procedure. One other point, forL > security reasons you would typically want to assign these file protections9 > to any globally used command procedures to avoid hacks:  > = > $SET SECURITY/PROT=(S:RE,O:RWED,G:RE,W:RE) <procedure-name>   G Well, the best way to avoid hacks is to ensure that your proc.'s always 	 end with:    $ EXIT  / This way, any code appended will never execute.   / Note also the explanation of GRPPRV and SYSPRV:   C GRPPRV               may access group objects via system protection = SYSPRV               may access objects via system protection   F Now, I don't know if SYSPRV overrides GRPPRV in cas we're both "SystemG class users", but if you're in my UIC group and the file belongs to me, E I may be able to Write/Delete the file, but you won't. Also, the only H reason to have W access to a .COM file is to permit APPENDing or, in the odd case, perhaps WRITE/UPDATE.   A To avoid unauthorized replacement (new version) of a file, manage  directory protections.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------   Date: 9 Jan 2006 11:49:45 -0800 ) From: "eventhorizon5" <ryan@tliquest.net> / Subject: Re: Free to a good home: OSF/1 manuals B Message-ID: <1136836185.316548.43870@g49g2000cwa.googlegroups.com>  B Now that's ironic lol - I live in La Grange IL also (and I've beenF messing around with Tru64 5.0 lately - I mostly work with Debian Linux and Solaris/SPARC though)   
 -eventhorizon    ------------------------------  # Date: Mon, 09 Jan 2006 22:59:49 GMT 2 From: Scott Squires <squires@zargon.hobbesnet.org>) Subject: Re: Free: AlphaServer 2100 5/250 1 Message-ID: <7e6b93-a3d.ln1@zargon.hobbesnet.org>   3 Scott Squires <squires@zargon.hobbesnet.org> wrote: E > I have moved into a studio apartment and no longer have room for my I > AlphaServer.  It is very difficult to part with, but I don't see a time H > in the near future that I will be able to use it.  I hope someone will > have a better home for it.   This machine has been adopted.   --Scott    ------------------------------  % Date: Mon, 09 Jan 2006 20:31:00 -0000 1 From: wspencer@ap.dontspamme.org (Warren Spencer) 6 Subject: Re: Great new antivirus software for windoze!1 Message-ID: <9746954C7wspenceraporg@216.168.3.30>   6 bob@instantwhip.com wrote in <1136323093.122676.178350 @g49g2000cwa.googlegroups.com>:   G >It's called "Pull the Plug" antivirus software written by Garbagefixer  >Inc.  > E >guaranteed to work on 100% of all windoze viruses and trojans ... :)  >  >located at  >  >www.windozesecuritystinks.com >   M URL doesn't work.  "Guaranteed to work on 100% of all windoze viruses ...".   4 Sorry but that doesn't pass the BS detector test ;-)   ws --   Warren Spencer Senior Software Engineer The Associated Press   ------------------------------   Date: 9 Jan 2006 21:10:38 -0800 ( From: "maloninc" <hiroyuki@maloninc.com>1 Subject: How to prevent users from telnet-login ? C Message-ID: <1136869837.984043.264680@g14g2000cwa.googlegroups.com>    Hi. E I heard that making "CAPTIVE" user is usual way to deny telnet-login. . Does anyone know another UAF flags to do that?   ------------------------------  * Date: Mon, 9 Jan 2006 23:51:13 -0600 (CST)* From: sms@antinode.org (Steven M. Schweda)5 Subject: Re: How to prevent users from telnet-login ? 2 Message-ID: <06010923511372_20331674@antinode.org>  ( From: "maloninc" <hiroyuki@maloninc.com>  G > I heard that making "CAPTIVE" user is usual way to deny telnet-login.   E    That sounds wrong to me.  First, I doubt that it would deny Telnet 7 access.  Second it would (greatly) affect local access.   D    If you don't mind disabling DECnet access, too, you might try (in AUTHORIZE):    UAF>  MODIFY user /REMOTE = 0-0      alp $ telnet alp% %TELNET-I-TRYING, Trying ... 10.0.0.9 0 %TELNET-I-SESSION, Session 01, host alp, port 23( -TELNET-I-ESCAPE, Escape character is ^]         I'm ALP.  Who are you?  
 Username: sms 	 Password: , You are not authorized to login at this time- %TELNET-S-REMCLOSED, Remote connection closed 0 -TELNET-I-SESSION, Session 01, host alp, port 23 alp $     %    Undo all access restrictions with:    UAF> MODIFY user /ACCESS  H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------   Date: 9 Jan 2006 22:43:27 -0800 ( From: "maloninc" <hiroyuki@maloninc.com>5 Subject: Re: How to prevent users from telnet-login ? C Message-ID: <1136875407.187193.143990@z14g2000cwz.googlegroups.com>   % I'll try it and thank you very match.    ------------------------------  % Date: Mon, 09 Jan 2006 19:39:45 -0500  From: ASAAR <caught@22.com> & Subject: Re: HP's strategy explained :8 Message-ID: <8f06s1p4051nrqgk75jdmhavi6jjlj2b66@4ax.com>  0 On 9 Jan 2006 07:18:39 -0600, Bob Koehler wrote:  9 >> Unions, which are voluntary, with no govt privileges,  ' >> are a rational option for employees.  > D >    In many places unions are not really voluntary.  Although thereE >    are laws in most places allowing a worker to opt-out, the worker I >    is often told "you must join the union".  And if the worker opts-out . >    he/she still often has to pay union dues. > ; >    The inverse (prohibiting union membership) is illegal.   >   I guess that explains why so many employees of mega-retailer Walmart are unionized . . .    ------------------------------   Date: 9 Jan 2006 13:34:58 -0500 . From: brooks@cuebid.zko.hp.nospam (Rob Brooks)- Subject: Re: HSZTerm under newer VMS versions , Message-ID: <W3u5omhmJS3i@cuebid.zko.hp.com>   (Malcolm Dunnett) writes:   L >  Should I be doing the $SET HOST to the command console (GGxx: device) or N > to one of the drives (DGxx: devices), or does it matter?. Both seem to work.  K I have no idea what the "supported" method is, but I use both the GG device  and a disk with no issue.    --    L Rob Brooks    VMS Engineering -- I/O Exec Group     brooks!cuebid.zko.hp.com   ------------------------------  % Date: Mon, 09 Jan 2006 20:27:04 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>- Subject: Re: HSZTerm under newer VMS versions + Message-ID: <43C31B78.A318583D@comcast.net>    Rob Brooks wrote:  >  > (Malcolm Dunnett) writes:  > M > >  Should I be doing the $SET HOST to the command console (GGxx: device) or P > > to one of the drives (DGxx: devices), or does it matter?. Both seem to work. > M > I have no idea what the "supported" method is, but I use both the GG device  > and a disk with no issue.   H I'm told that officially, the "supported" method is something other than HSZterm.  E Also, you should *ONLY* use the virtual console device, and never use ' both SWCC and HSZterm at the same time.   B For HSGs, the virtual console device will be a $1$GGAxxxx: device.  E For HSZ70 and later, the virtual console device will be a specific DK C device as programmed at the HSZ console. The virtual console device ; appears to VMS as a disk device, but is not an actual disk.   H As it was explained to me, the reason for only using the virtual console@ device is to avoid a possible race condition between HSZterm andF DKDRIVER resulting in data loss or corruption if a disk device is used instead.  B The reason for not using both SWCC and HSZterm at the same time isC similar: access contention gives rise to a possible race condition. G They're both trying to use the virtual console device at the same time. B If you see data you didn't request rolling up your screen when youF access an HSG or HSZ using SET HOST/SCSI, hit CTRL+Z when stuff stops,C then shutdown SWCC Agent before proceeding to access the controller  again.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 09 Jan 2006 15:56:37 -0500 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>, Subject: Re: Java 1.4.2 installation problem. Message-ID: <43C287B5.6352.144E4B93@localhost>  - On 9 Jan 2006 at 17:26, Keith A. Lewis wrote: ' > Do you get the the following results?  >  > $ dir java$jvm_shr > 7 > Directory SYS$COMMON:[JAVA$142.JRE.LIB.ALPHA.CLASSIC]  >  > JAVA$JVM_SHR.EXE;1  E Instead of SYS$COMMON:[...], I get FAST$DKA100:[SYS0.SYSCOMMON...].    But that's the same place.  A Just for fun, I changed it to the SYS$COMMON form, and still got  , "Error: no `classic' JVM at `java$jvm_shr'."  
 --Stan Quayle  Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com) "OpenVMS, when downtime is not an option"    ------------------------------  $ Date: Mon, 9 Jan 2006 21:39:01 +0100+ From: "Michel HERRSCHER" <mhc@herrscher.fr>  Subject: Re: KVM Switches 7 Message-ID: <43c2c9e0$0$19679$8fcfb975@news.wanadoo.fr>   1 Dans un message vmsmangler@earthlink.net disait :    >  > Bill LaCounte  > Retired VMS Systems Manager  ~~~~~~~~ Bill,   L With the current HP HR policy, you will have to return to the working world  ....   ;-))))   --   Michel HERRSCHER CONSULTANT ; Prsident WINDASSO - Association des utilisateurs WxxDEV(c) # Tel : +33450870912 Fax:+33450871741  http://www.windasso.org    ------------------------------  $ Date: Mon, 9 Jan 2006 16:41:29 -0500- From: William Webb <william.w.webb@gmail.com>  Subject: Re: KVM Switches H Message-ID: <8660a3a10601091341w27aaab5o129a6d8acb497b5a@mail.gmail.com>  5 On 1/9/06, Michel HERRSCHER <mhc@herrscher.fr> wrote: 3 > Dans un message vmsmangler@earthlink.net disait :  >  > >  > > Bill LaCounte  > > Retired VMS Systems Manager 
 > ~~~~~~~~ > Bill,  > L > With the current HP HR policy, you will have to return to the working wor= ld > .... >  > ;-)))) >  > -- > Michel HERRSCHER CONSULTANT ? > Pr=E9sident WINDASSO - Association des utilisateurs WxxDEV(c) % > Tel : +33450870912 Fax:+33450871741  > http://www.windasso.org  >  >  >   D I was wondering whether he formerly managed VMS systems and retired,> or if he managed VMS systems that had themselves been retired.   WWWebb   --C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------   Date: 9 Jan 2006 13:53:45 -0800 ; From: "vmsmangler@earthlink.net" <vmsmangler@earthlink.net>  Subject: Re: KVM Switches C Message-ID: <1136843625.253904.144280@g43g2000cwa.googlegroups.com>    William Webb wrote: 7 > On 1/9/06, Michel HERRSCHER <mhc@herrscher.fr> wrote: 5 > > Dans un message vmsmangler@earthlink.net disait :  > >  > > >  > > > Bill LaCounte ! > > > Retired VMS Systems Manager  > > ~~~~~~~~	 > > Bill,  > > L > > With the current HP HR policy, you will have to return to the working w= orld > > .... > > 
 > > ;-)))) > >  > > -- > > Michel HERRSCHER CONSULTANT A > > Pr=E9sident WINDASSO - Association des utilisateurs WxxDEV(c) ' > > Tel : +33450870912 Fax:+33450871741  > > http://www.windasso.org  > >  > >  > >  > F > I was wondering whether he formerly managed VMS systems and retired,@ > or if he managed VMS systems that had themselves been retired. >  > WWWebb >  > --E > NOTE: This email address is only used for noncommerical VMS-related  > correspondence. E > All unsolicited commercial email will be deemed to be a request for : > services pursuant to the terms and conditions located at% > http://bellsouthpwp.net/w/e/webbww/   D Actually both scenarios are correct. I have managed VMS systems thatE were then retired. And I have managed VMS systems and then decided to 0 retire myself. Lots of fun since the early '80s.   Bill   ------------------------------  % Date: Mon, 09 Jan 2006 16:58:31 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: KVM Switches , Message-ID: <43C2DC7A.E0906058@teksavvy.com>  ! "vmsmangler@earthlink.net" wrote: # > > > > Retired VMS Systems Manager   F > Actually both scenarios are correct. I have managed VMS systems thatG > were then retired. And I have managed VMS systems and then decided to 2 > retire myself. Lots of fun since the early '80s.   But you forgot:   ; Managing systems that are on retirement but still kicking !    ------------------------------   Date: 9 Jan 2006 19:07:40 -0800 $ From: "AEF" <spamsink2001@yahoo.com>Y Subject: Large Amount of Upper Case Alert!!! Re: foreign commands, .com files, and dcltab B Message-ID: <1136862460.747012.32050@o13g2000cwo.googlegroups.com>   David J Dachtera wrote:  > Jeff Cameron wrote: 
 > > [snip]O > > One other point; while you can change the actual system wide DCL tables, it P > > is typically not a good idea. This is because when you upgrade or patch VMS,L > > the kit my overwrite your changes. Instead (if you go the executable/CLDP > > route) that you include your SET COMMAND in the system wide login procedure. > F > OOOOOOOOOOOOHHHHHHHHHHHHHHH!!!!!!!!! *DEFINITELY* *NOT* a good idea!    6 Where are the uppercase police when you need them? :-)     [...]    AEF    ------------------------------   Date: 9 Jan 2006 16:17:16 -0600  From: briggs@encompasserve.orgK Subject: Re: Search loop gets file while still being written - How to avoid 3 Message-ID: <ekrWsslyR9tT@eisner.encompasserve.org>   ^ In article <43C2C2CA.61066566@vaxination.ca>, JF Mezei <jfmezei.spamnot@vaxination.ca> writes: > norm.raphael@metso.com wrote: $ >> $   IF F$FILE(dfile,"EOF") .NE. 0- >> %SYSTEM-W-ACCONFLICT, file access conflict  >>  \USERAREA:FILE_02.DAT;1\ > ' > The simple method would be to try to   >  > $LOOP: > $   dfile=F$search("fi*.dat") & > $   IF dfile .EQS. "" THEN goto test+ > $OPEN/READ/NOSHARE/ERROR=LOOP temp 'dfile 
 > $CLOSE temp ! > $	IF F$FILE(dfile,"EOF") .NE. 0  > etc  > E > Yep, serious overhead in opening and closing the file all the time.   ? Not only that, but it still leaves you open to race conditions.    	John Briggs   ------------------------------   Date: 9 Jan 2006 16:22:07 -0600  From: briggs@encompasserve.orgK Subject: Re: Search loop gets file while still being written - How to avoid 3 Message-ID: <Rwo5zBw0kM26@eisner.encompasserve.org>   \ In article <43C2CF56.7AC68BBE@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > AEF wrote:	 >> $loop:   >> $   dfile=F$search("fi*.dat")) >> $   IF (dfile .EQS. "") THEN goto test E >> $   SET NOON                              ! Disable error checking ? >> $   FILE_EOF = F$FILE(dfile,"EOF")        ! Get the EOF info D >> $   STATUS = $STATUS                      ! Save the status valueE >> $   SET ON                                ! Restore error checking C >> $   IF (.NOT.STATUS) THEN GOTO LOOP       ! Skip file if no good  >> $   IF (FILE_EOF .NE. 0)  >  > @ > I have also not tested it, but would the following also work ? >  > $LOOP: > $	dfile=f$search("fi*.dat") $ > $	if dfile .eqs. "" then goto test > $! > $	on error then goto loop   * Make that on warning and you should be ok.  I > You might also wish to use SET MESSAGE to turn off error message before I > the f$file_attributes and turn it back on to make this cleaner looking.   H I believe that SET MESSAGE involves an image activation.  If performance> is important, you might want to keep it outside the main loop.   ------------------------------  $ Date: Mon, 9 Jan 2006 14:48:55 -0500 From: norm.raphael@metso.comP Subject: Search loop gets file while still being written - How to avoid conflictQ Message-ID: <OF46C38BB6.5B432497-ON852570F1.006C3195-852570F1.006CD1F4@metso.com>    This is from the batch log:  ===  $loop: $   dfile=F$search("fi*.dat") $ $   IF dfile .EQS. "" THEN goto test! $   IF F$FILE(dfile,"EOF") .NE. 0 * %SYSTEM-W-ACCONFLICT, file access conflict  \USERAREA:FILE_02.DAT;1\  $   then@ %DCL-E-INVIFNEST, invalid IF-THEN-ELSE nesting structure or data
 inconsistency  === C The search loop is finding the ".dat" files beginning with "FI" and  appending themI to another file.  In this case FILE_02.dat;1 was still being written into  the USERAREA9 logical directory when the f$search() procedure found it. B Is there a way to just skip such a file or files within the DCL IF structure without it breaking?   ------------------------------   Date: 9 Jan 2006 12:39:05 -0800 $ From: "AEF" <spamsink2001@yahoo.com>T Subject: Re: Search loop gets file while still being written - How to avoid conflictC Message-ID: <1136839145.452289.177890@o13g2000cwo.googlegroups.com>    norm.raphael@metso.com wrote:  > This is from the batch log:  > ===  > $loop: > $   dfile=F$search("fi*.dat") & > $   IF dfile .EQS. "" THEN goto test# > $   IF F$FILE(dfile,"EOF") .NE. 0 , > %SYSTEM-W-ACCONFLICT, file access conflict >  \USERAREA:FILE_02.DAT;1\ 
 > $   thenB > %DCL-E-INVIFNEST, invalid IF-THEN-ELSE nesting structure or data > inconsistency  > === E > The search loop is finding the ".dat" files beginning with "FI" and  > appending themK > to another file.  In this case FILE_02.dat;1 was still being written into  > the USERAREA; > logical directory when the f$search() procedure found it. D > Is there a way to just skip such a file or files within the DCL IF  > structure without it breaking?   Yes.  D Get the EOF information in a separate line and use error checking to skip files that produce errors.      *** NOTE ***  E *** This is not tested. *** Use at your own risk. *** This is just to  illustrate the idea:   ...  $loop: $   dfile=F$search("fi*.dat") & $   IF (dfile .EQS. "") THEN goto testB $   SET NOON                              ! Disable error checking< $   FILE_EOF = F$FILE(dfile,"EOF")        ! Get the EOF infoA $   STATUS = $STATUS                      ! Save the status value B $   SET ON                                ! Restore error checking@ $   IF (.NOT.STATUS) THEN GOTO LOOP       ! Skip file if no good $   IF (FILE_EOF .NE. 0) $   then ...     < This separates the error-prone part from the IF-THEN block.    AEF    ------------------------------  % Date: Mon, 09 Jan 2006 15:08:48 -0500 . From: JF Mezei <jfmezei.spamnot@vaxination.ca>Y Subject: Re: Search loop gets file while still being written - How to avoid conflict conf - Message-ID: <43C2C2CA.61066566@vaxination.ca>    norm.raphael@metso.com wrote: # > $   IF F$FILE(dfile,"EOF") .NE. 0 , > %SYSTEM-W-ACCONFLICT, file access conflict >  \USERAREA:FILE_02.DAT;1\   % The simple method would be to try to     $LOOP: $   dfile=F$search("fi*.dat") $ $   IF dfile .EQS. "" THEN goto test) $OPEN/READ/NOSHARE/ERROR=LOOP temp 'dfile  $CLOSE temp  $	IF F$FILE(dfile,"EOF") .NE. 0  etc   C Yep, serious overhead in opening and closing the file all the time.    ------------------------------  % Date: Mon, 09 Jan 2006 16:02:24 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> Y Subject: Re: Search loop gets file while still being written - How to avoid conflict conf , Message-ID: <43C2CF56.7AC68BBE@teksavvy.com>  
 AEF wrote: > $loop: > $   dfile=F$search("fi*.dat") ( > $   IF (dfile .EQS. "") THEN goto testD > $   SET NOON                              ! Disable error checking> > $   FILE_EOF = F$FILE(dfile,"EOF")        ! Get the EOF infoC > $   STATUS = $STATUS                      ! Save the status value D > $   SET ON                                ! Restore error checkingB > $   IF (.NOT.STATUS) THEN GOTO LOOP       ! Skip file if no good > $   IF (FILE_EOF .NE. 0)    > I have also not tested it, but would the following also work ?   $LOOP: $	dfile=f$search("fi*.dat") " $	if dfile .eqs. "" then goto test $! $	on error then goto loop + $	file_eof = f$file_ATTRIBUTES(dfile,"EOF")  $	on error then continue $	IF FILE_EOF .ne. 0 .....     G You might also wish to use SET MESSAGE to turn off error message before G the f$file_attributes and turn it back on to make this cleaner looking.    ------------------------------  % Date: Mon, 09 Jan 2006 16:56:46 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 6 Subject: Suggestion for INSTALL PURGE and SHUTDOWN.COM+ Message-ID: <43C2DC11.61DEB5A@teksavvy.com>   B When shutting down a system, proper dismounting of disks is alwaysF important, especially when you have shadowsets involved since it makesE the rebooting process and subsequent remounting of drives much faster D (no volume rebuidling needed and in case of shadowsets, a much fater. re-integration of a disk into the shadow set).  C The standard shutdown procedure does the INSTALL PURGE after having G called the site SYSHUTDWN.COM procedure. But SYSHUTDWN is the one where > the system manager is responsible for properly dismounting all? non-system disks. Unfortunatily, proper dismounting of disks is 8 impossible if there are still installed or opened files.  $ As a result, I have two suggestions:   1- INSTALL PURGE/DEVICE=disk:   D This would limit the de-installation of files to those on a specific@ drive. This would enable a procedure to deinstall all files on a' specific disk prior to dismounting it.      C 2- add a SYSHUTDWN_DISKS.COM procedure to be called by SHUTDOWN.COM F after all processes have been stopped, files deinstalled etc, at whichE point the user would have a far better chance of properly dismounting  the disks.      E Currently, SYSHUTDWN.COM is called before logicals such as OPC$REBOOT E have been set. So that procedure isn't aware if a reboot will be made  quickly or not.   C In the case of disks mounter clusterwide, if you're going to reboot H within a minute, then you may not need to dismount/CLUSTER a local driveH since the other nodes will regain access to it within mount-verificationH deadline. But if not doing a reboot, you may wish to really dismount theD drive clusterwide because that drive is really becoming unavailable.E (and INSTALL PURGE/DEVICE becomes useful in a SYSMAN operation to zap + installed files on that disk on all nodes).    ------------------------------   Date: 9 Jan 2006 13:52:33 -0600 4 From: kuhrt.nospammy@encompasserve.org (Marty Kuhrt)4 Subject: Re: WVNETcluster uptime reaches 10 years...3 Message-ID: <JCbIxXBHfck4@eisner.encompasserve.org>   j In article <VMHvf.3263$Kp.2817@southeast.rr.com>, "Kenneth Farmer" <kfarmer@NOSPAM.spyderbyte.com> writes:9 > "George Cook" <cook@wvnvms.wvnet.edu> wrote in message   > news:vMcZsp5mA0WO@wvnvms... N >> In article <Xfxvf.3003$iQ.1619@tornado.southeast.rr.com>, "Kenneth Farmer" * >> <kfarmer@NOSPAM.spyderbyte.com> writes:H >>> "David B Sneddon - bigpond" <dbsneddon#bigpond.com> wrote in message& >>> news:43BE1804.70801@bigpond.com... >>>>E >>>> http://uptimes.hostingwired.com/account.php?op=details&hid=13922  >>>>
 >>>> Regards, 	 >>>> Dave  >>>> -- G >>>> David B Sneddon (dbs) VMS Systems Programmer dbsneddon#bigpond.com G >>>> Sneddo's quick guide ...   http://www.users.bigpond.com/dbsneddon/ G >>>> DBS freeware   http://www.users.bigpond.com/dbsneddon/software.htm  >>>  >>> L >>> That's impressive.  Is there any way those stats can be smudged by OSes? >>B >> I know for a fact that the uptime for WVNETcluster is accurate.C >> FWIW, if a major power problem hadn't happened, the uptime would  >> have been since 21-Feb-1993.  >>/ >> $ write sys$output f$getsyi("cluster_ftime")  >> 5-JAN-1996 05:14:46.72  >> >> >> George Cook >> WVNET >  > L > I'm sure it's correct.  I'm wondering if other OS fanatics could argue it  > can be rigged. > M > Of course Paul mentioned the "Faking" paragraph found on the Uptimes site.  5 > I probably should have read the FAQ before I asked.  >  > Thanks guys. >  > Ken   ? I had some uptimes declared bogus because the cluster ftime and   last boot times did not match.     ------------------------------   End of INFO-VAX 2006.019 ************************