So, does the APPL need to be scheduled in advance or could it be triggered in by OPS in response to the CICS message?
If all of the jobs in the APPL are related to processing that should happen whenever CICS issues the message this might be an option. Remove the SCHEDULE statement from the EVENT and change the AJ jobtask COMPLETE to a TRIGGER cics.event. Where this would not work is if the JOBA.1 TASK is in the middle of an application that is waiting on the CICS message.
With this approach you only have a generation of the application active when it is really needed. Even if CICS is running late, no problem. When the CICS message is issued the APPL is built to submit the job(s).
Gene Budbill
Sr Services Consultant
CA Technologies
From: CA Workload Automation (Mainframe) Global User Community [mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, April 04, 2012 11:06 AM
To:
mb.2271275.97784483@myca-email.ca.com
Subject: [CA Workload Automation ESP Edition] RE: OPS/JES/ESP
It's confusing, I know.
This was all set up before my time at W&S. When we had Jobtrac, the job had a manual hold on it. CICS issued a system message that OPS captured. OPS then would issue a command to Jobtrac telling it to release the manual hold on the job.
When we converted to ESP, CA's solution to this was to schedule a task (dummy job) that would release the actual job. CICS issues a system message to OPS, OPS issues a command to ESP to force complete the task. The job is then released. The OPS rule issued is "F 'ESP',AJ 'JOBTASK' COMPLETE APPL('APPL')"
APPL TODAY
Job JOBA.1 TASK
RUN WORKDAY
RELEASE ADD(JOBA)
ENDJOB
Job JOBA
RUN WORKDAY
RELEASE ADD(JOBB)
ENDJOB
JOBA.1 is loaded in schedule TODAY. CICS is running behind and has not yet issued the message for JOBA.1 task to be force completed. Schedule TODAY is loaded again. We now have two occurances of JOBA.1 task. The default in ESP is to find the newest appl. You can change this to oldest but you have the same problem in reverse. The CICS message is issued, OPS captures it and marks the newest task complete.
My solution (that will not work) was to get rid of the tasks and just put the job on hold along with a delaysub. I wanted OPS to issue a command to release the job. If the wrong job was released due to the ESP default and CICS being behind, the delaysub would keep the job from running and a hold could be put back on.
--
CA Communities Message Boards
97787023
mb.2271275.97784483@myca-email.ca.com<mailto:
mb.2271275.97784483@myca-email.ca.com>