Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!sdcsvax!ucsdhub!esosun!seismo!uunet!munnari!murdu!u3369429
From: u3369429@murdu.UUCP
Newsgroups: comp.os.vms
Subject: Re: How do I get the COMPLETE batch log file specification ?
Message-ID: <1329@murdu.OZ>
Date: Thu, 3-Dec-87 22:51:24 EST
Article-I.D.: murdu.1329
Posted: Thu Dec  3 22:51:24 1987
Date-Received: Wed, 9-Dec-87 00:47:19 EST
References: <871203030918.087@CitHex.Caltech.Edu>
Followup-To: comp.os.vms
Organization: I.A.E.S.R., Melbourne University
Lines: 27
Summary: why do it simple when you can do it complicately?

In article <871203030918.087@CitHex.Caltech.Edu> carl@CITHEX.CALTECH.EDU (Carl J Lydick) writes:
> > How does a batch job determine the full file specification of its own log
> > file (including version number) ?

Can we assume that the job was submitted without `/NAME=' qualifier?
If yes, the following two lines will return the log-file name:
$ x=F$Parse(F$Element(0,".",F$Environment("Procedure")),".LOG")
$ x=x+F$Element(1,";",F$Search(x))
assuming that the batch job is running in the same directory
where the log-file is.

> > Show queue/full gives most of this information, but not the version number
> > of the log file.
> > 
> > I my case I have the same job running periodically, and I would like to
> > let the job itself decide whether to remove or print/keep its own log
> > file even if there are several versions of the file present.

I don't think a batch job can delete its own log file.

Michael Bednarek		
Institute of Applied Economic and Social Research (IAESR)
Melbourne University, Parkville 3052, AUSTRALIA, Phone : +61 3 344 5744
Domain: u3369429@{murdu.oz.au | ucsvc.dn.mu.oz.au}  or  mb@munnari.oz.au
"bang": ...UUNET.UU.NET!munnari!{murdu.oz | ucsvc.dn.mu.oz}!u3369429

"POST NO BILLS."