Aduke.1668
fa.info-vax
utcsrgv!utzoo!decvax!duke!djc
Mon Jan 25 16:03:17 1982
Non Printing VMS Batch Jobs


Many weeks ago, a request went out about how to keep a VMS batch
job from printing its .LOG file on the system line printer,
and then deleting itself.  ( As somebody pointed out, VMS V3.0
will have some options to get around this.   )

The best kluge I found to keep the .LOG file is to stop the
batch job process pre-maturely after all is done by using a couple
of VMS lexical functions as the last line in the command file.
Thus, the process gets stopped before the job controler can
grab it and print it.  For example:

       $ run myfavorite
       $ ...
       $ if "''f$mode()'".eqs."BATCH" then stop 'f$process()'

This will leave the .LOG file in the SYS$LOGIN directory of
the user.  Also, it will leave you alone if you are executing
the command procedure interactively.


Problems:
 - You need GROUP priv to be able to do the STOP process command.
 - Your interactive process gets killed if used as a command
   file so have to check with the if... nonsense.
 - Leaves no intersting info about job execution times, io,...
   so just do a    $ show process    before the last line.

                               David J. Cherveny, duke!djc

-----------------------------------------------------------------
gopher://quux.org/ conversion by John Goerzen <[email protected]>
of http://communication.ucsd.edu/A-News/


This Usenet Oldnews Archive
article may be copied and distributed freely, provided:

1. There is no money collected for the text(s) of the articles.

2. The following notice remains appended to each copy:

The Usenet Oldnews Archive: Compilation Copyright (C) 1981, 1996
Bruce Jones, Henry Spencer, David Wiseman.

You are viewing proxied material from gopher.quux.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.