First of all let me thank all the senior members of this forum.I am able to resolve several queries searching/researching in this forum.
I want to discuss following situation in CA7.
An FSTRUC is cancelled without executing all the jobs in the FSTRUC due to some problem not related to CA7.
Next time (just after cancelling the previous FSTRUC within the lead time of all the jobs) , when the same FSTRUC is demanded few of the requirements got posted because of the jobs that ran in the previous run.
Is there any way to flush out the CA7 memory to wipe out information from previous FSTRUC run?
Joined: 06 Jun 2008 Posts: 8165 Location: East Dubuque, Illinois, USA
The CA-7 manual on CANCEL says
126.96.36.199 Usage Notes
The record for the specified job is deleted from the appropriate queue, and if CA-11 is
used, an attempt is made to clear the CMT. See the CA-7 Interfaces Guide for further
discussion related to CA-11.
Obviously, canceling a job stops all triggering by the canceled job and does not satisfy
requirements for other jobs which may be dependent on the canceled job.
The job does not go through normal job completion; therefore, job triggering and requirement
posting are not performed.
All output workstation networks for the canceled job are notified and their records are
deleted from the postprocess queue.
The QM.1 screen may also be used to cancel jobs.
But if the job is executing already, you'll need to issue a cancel command in z/OS for the job as well.