The Question is:
I have a third party executable (IBM's MQSeries for VMS trigger monitor)
that I'm running in a batch job. What I want is to periodically start a new
batch log file.
Once started, the executable normally does not terminate. I've been
manually entering "delete/entry=job-entry", then "submit command-procedure".
I would like to make this auto-magic. One possibility is to spawn/nowait
the executable and monitor the time in the parent process - at the proper
time, the parent submits itself and exits. Another is separate batch jobs,
one with the executable, the ot
her does a delete/entry at the proper time and then submits a new job.
None of these is particularly pleasing and I'm hoping that you can point me
to an elegant alternative.
The Answer is :
Please contact the maintainer of the application environment, and
determine if there is a way to exit (gracefully or otherwise) from
the job, in order to restart it with a new log file. Alternatively,
if there is a way to operate the application with a local (and
application-specific) log file.
Without the assistance of the application, you will likely be left
with any of a variety of ugly -- but effective -- approaches to
restarting it and thus to recreating the log file...