Here is what I have done and why I ask.
Step # 1 (completed)
In SYLOGIN an application is executed to log pertinent information of a batch
job (PID, entry #, log-spec, file-spec, start date/time, etc.). This
information is kept in an ISAM file - keyed off the start date/time.
This currently is in DCL but planning to write in FORTRAN (or C).
Step # 2 (working on)
In OpenVMS Utility Routines Manual Chapter 14 LOGINOUT (LGI) Routines you can
define the logical LGI$LOGINOUT_CALLOUTS (/SYS/EXE) to call a single or list of
end-of-job images. (also need to set a SYSGEN parameter)
Refer to :
By using this method I can update the record created in Step # 1 with the
completion time and (hopefully) the completion status.
The plan is NOT to depend on this, however it will allow me to track my batch
jobs. Granted STOP/ID and DELETE/ENTRY will defeat this purpose however how
many times does one delete your batch jobs? Then there is the ocassional CRASH
and "oops I should not have pushed that button" - that was at least 330 days
ago. I would believe that this is the exception and not the rule.
Even if this does happen I still have an outstanding data record (from Step # 1)
that can be periodically detected and addressed.
More than I care to address.
Norm, NOPE! - I thought I was but I am on a roll here, will refrain from that
one till a later date...
There will always be "unforseen" events in my future - what is new?!?
Thanks for the input...!
VMS Systems Administrator