|
Ending of a SBS would NEVER release the job. Find the job log, or do a DSPLOG and I bet you will see the message Job
NEVEREND/SHERLOCK/123456 has been release by DAISYDUCK.
Good hunting.
JDHorn wrote:
I'll try to be more clear
We have a job running all day in qbatch that checks our data every
1 minute to see if it should go to an ftp site to retrieve data
from one of our customers in response to data we sent them.
Someone held it during the day using option 3 on the wrkactjob
screen. (If you did a wrkactjob of qbatch it was at a hld status)
it stayed at the hld status till 10:30 pm
during our automated night process, subsystem qbatch is ended
controlled at 10:30 PM.
working with the display log and timestamps on the ftplog, I saw
that just seconds after the subsystem was ended controlled, the
held program seemed to "wake up" and processed data from the ftp
site.
I have attempted to use the Sherlock Holmes technique to eliminate
every other possibility, and this seems to be the only one left.
Any ideas?
---- original post -------
Does anyone know?
Is there a chance that - - if a job is held in a subsystem (it had
been started by a jobscde) - if the subsystem is ended controlled then - the job becomes active again while the subsystem ends?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.