The Question is:
I have a series of batch jobs which are submitted to a queue with a job limit
of 5. These batch jobs simply create Oracle reports by running a pro-c program
against an Oracle database. However I have a problem with the number of
reports running at once on
the database. When I look at vms accounting it appears that the .exe which
runs within a batch job completes execution AFTER the completion time of the
batch job. This means that the queue believes the job has completed and thus
runs the next pending job
even though the .exe has not completed.
Is this a known bug? I have raised the issue initially with Oracle but they say
it is a vms problem so I hand it over to you.
The Answer is :
This could simply be a case of skewed clocks within an OpenVMS Cluster.
If this is not an OpenVMS Cluster or if the times are not sufficiently
skewed, then something is seriously weird with the system as the image
accounting record -- the OpenVMS Wizard assumes this is what you are
looking at -- should be timestamped prior to the execution of the
process rundown that occurs at the end of the batch job execution, and
is effectively what causes the queue manager itself to dequeue the next
available job, and is also what triggers the logging of the batch job
Assuming this is not simply a case of system clocks that need to be
(re)synchronized within an OpenVMS Cluster, please contact the Compaq
Customer Support Center directly for assistance in resolving this.