You can now order the SMART Table Entity and all of the jobs in table IDGS2. Remember that these jobs are dependent on successful completion of IDJOB1 in table IDGS1, but you will not immediately order that job.
When a SMART Table Entity is ordered, all the jobs in the SMART Table that should be scheduled that day are automatically ordered as well. Because all the jobs have the Schedule RBC EXERCISES, they were all ordered.
Filter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Wait Schedule
IDJOB2 ID 020201 JOB Wait Schedule
IDJOB3 ID 020201 JOB Wait Schedule
IDJOB4 ID 020201 JOB Wait Schedule
IDJOB5 ID 020201 JOB Wait Schedule
========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ========
Notice that the SMART Table Entity, and all its jobs, have a status of Wait Schedule.
------------------------ IDGS2 SCHEDULING ANALYSIS --------------------(3.?)
COMMAND ===> SCROLL===> CRSR
OPT DESCRIPTION
CONDITION JOB1-ENDED-OK ODATE 0202
====== >>>>>>>>>>>>>>>>>>>>> END OF "WHY" LIST <<<<<<<<<<<<<<<<<<<<< =====
As predicted, the job is waiting for condition IDJOB1-ENDED-OK. You should now order IDJOB1.
Job IDJOB1 changes to a status of Wait Submission, then is submitted, then executed, and finally, it ends OK. At that point, the status of the SMART Table Entity changes to Active, and the status of jobs IDJOB2 and IDJOB4 changes to Wait Submission.
Filter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Active
IDJOB2 ID 020201 JOB Wait Submission
IDJOB3 ID 020201 JOB Wait Schedule
IDJOB4 ID 020201 JOB Wait Submission
IDJOB5 ID 020201 JOB Wait Schedule
IDJOB1 ID 020201 COURSE7A/14348 JOB Ended "OK"
========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ========
From that point on, the processing continues. Once job IDJOB2 ends OK, job IDJOB3 is submitted; once IDJOB4 ends OK, job IDJOB5 is submitted.
Job IDJOB3 ends OK, but IDJOB5 does not, due to the condition code C0008. Because at least one of the jobs in the SMART Tables—IDJOB5—ended NOTOK, the SMART Table Entity ends NOTOK. At the end of processing, the status of the jobs appears as follows:
Filter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Ended- Not "OK"
IDJOB2 ID 020201 M21 /14373 JOB Ended "OK"
IDJOB3 ID 020201 M21 /14375 JOB Ended "OK"
IDJOB4 ID 020201 M21 /14374 JOB Ended "OK"
IDJOB5 ID 020201 M21 /14376 JOB Ended- Not "OK" Due to CC
IDJOB1 ID 020201 COURSE7A/14372 JOB Ended "OK"
========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ========
You can go back and correct the JCL for IDJOB5, and then rerun the job.
In the previous chapter, you learned about reruns in context of restarts, but it is also possible to rerun a failed job from the beginning. Do this for IDJOB5.
Filter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Ended- Not "OK"
IDJOB2 ID 020201 +---------------------------------(3.R)+
IDJOB3 ID 020201 | Job IDJOB5 Is to be Rerun |
IDJOB4 ID 020201 | Please Confirm Y (Y/N) |
R IDJOB5 ID 020201 | With Restart N (?/Y/N) |o CC
IDJOB1 ID 020201 | ---------------------------------- |
========= >>>>>>>>>>>>> | From Step/Proc . | < ========
| To Step/Proc . |
| Recapture Abend Codes (Y/N) |
| Recapture Cond Codes (Y/N) |
| Step Adjustment (Y/N) |
| Restart Parm Member Name IDJOB5 |
+--------------------------------------+
The second run of the job ends OK, and so does the SMART Table Entity. The Active Environment screen is displayed as follows:
Filter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Ended "OK"
IDJOB2 ID 020201 M21 /14373 JOB Ended "OK"
IDJOB3 ID 020201 M21 /14375 JOB Ended "OK"
IDJOB4 ID 020201 M21 /14374 JOB Ended "OK"
IDJOB5 ID 020201 M21 /14393 JOB Ended "OK" (Run 2)
Prior Run: Ended- Not "OK" Due
to CC
IDJOB1 ID 020201 COURSE7A/14372 JOB Ended "OK"
========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ========
Go into the IOA Conditions/Resources screen and see the results of these job runs.
-------------------------- IOA CONDITIONS/RESOURCES ------------------------(4)
COMMAND ===> SCROLL ===> CRSR
PREFIX ===> ID COND Y CONTROL Y RES Y STAT Y DATE 0202 - 0202
OPT TYPE CONDITION/RESOURCE IOAID USE QUANTITY MAX *P RBA DATE
COND IDJOB1-ENDED-OK 0202
COND IDJOB2-ENDED-OK 0202
COND IDJOB4-ENDED-OK 0202
COND IDGS2-END-NOTOK 0202
COND IDJOB5-ENDED-OK 0202
COND IDGS2-ENDED-OK 0202
======== >>>>>>>>>>>>>>>> B O T T O M O F L I S T <<<<<<<<<<<<<<<< ========
Notice the following:
Parent Topic |