Professional Documents
Culture Documents
CA-7 & CA-11: /var/www/apps/conversion/tmp/scratch - 5/263057800
CA-7 & CA-11: /var/www/apps/conversion/tmp/scratch - 5/263057800
&
CA-11
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
CA-7
CA-7 is our automated job scheduler. Jobs can be scheduled to run and manipulated in a variety of ways.
Two common terms that have caused confusion are "job triggering" and "job dependency."
Job triggering means a job's JCL is being pulled into the CA-7 queue for execution. If it has no other
dependencies on it, it runs right away. But if there are other dependencies, it will wait for them to be satisfied. In
other works, when a job is triggered, it doesn't necessarily run right then.
A job dependency is a job that must complete before the job waiting in the queue can run. Upon successful
completion of the preceding job, the job waiting in the queue will be submitted. However, if the dependent job does
not complete successfully, the job dependency will not be posted.
Also, the terms "force complete" and "cancel" both mean to remove a job form the CA-7 queue. But the
results are completely different.
A job is forced complete when it returns an acceptable condition code, or when it does not require an immediate
remedy, and the job stream can continue. Forcing a job complete tells CA-7 to treat the job as having completed
successfully, and to continue processing. Any dependencies of this job on other jobs will be posted, and any job
triggering by this job will be done.
Canceling a job from the queue does just the opposite. The job will be removed from the CA-7 queue, but
no job triggering will be done, and any dependencies of this job on others will not be posted. This command is used
to stop a job stream.
Page-1
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
CA -7 SCHEDULING
Jobs can be scheduled in two different ways:
1) Calendar scheduled
2) Triggered
Calendar scheduled means a job has been added to one of the CA-7 calendars for a specific day(s) and time
Page-2
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
CA-7 SCHEDULING
Triggered means job 'B' will only run when job 'A' triggers it in.
Page-3
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
Submit time means that at its set time, the job will automatically be submitted by CA-7, provided any other
dependencies have been met.
Job dependencies are posted by completion of preceding jobs. All jobs are set up with a "look back" time.
That determines how far CA-7 will look back to see if the proceeding jobs completed successfully during that
timeframe.
User requirements are text messages that need to be manually posted for the job to be submitted.
Page-4
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
ACCESSING CA-7
There are 3 different ways to access CA-7.
1) TSO CA7CLIST from the command line on nearly any TSO screen.
2) Select the CA option at the SPF PRIMARY OPTION MENU. From there, select 7 at the CA
PRODUCT SYSTEM MENU.
3) CA7ONL option from the TPX menu.
Option 1:
Option 2:
Option 3
Page-5
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
Page-6
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
HELPFUL DISPLAYS
1) LACT, SEQ=JOB
5) LPRRN, JOB=JOBA
Page-7
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
Page-8
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
CA-11
CA-11 is our rerun management package. Its 2 main functions are:
1) Directs CA-7, which step to restart the job in, no restart parm needed.
2) Performs data set and GDG maintenance.
CA-11 inserts a step at the beginning of the job called CA07RMS. Within this step, CA-11 scans the JCL
being run and looks for any data sets being created in the job. If the first instance of a file in the job has a
disposition beginning with "NEW," CA-11 then checks the system catalog to see if there is already an existing data
set by that name. If there is, CA-11 then deletes it to prevent a NOT CAT 2 error. THIS HAPPENS WHETHER IT
IS A PRODUCTION RUN OF THE JOB, OR A RESTART.
Also, if necessary, GDG adjustments are made by CA-11 in this step. Any changes to bias numbers, (+1) to
(0) on a restart, for example, are done by CA-11.
All activity processed through CA-11 is logged to a data set called the JEHF (job execution history file).
On Sunday nights, a tracking job is run against that file. This job creates a report showing all jobs that were
restarted through CA-11 during the previous 7 days, and their ABEND codes. The report is available in SAR under
the jobname, D50W200S
Page-9
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
Page-10
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
In the event that an abended job would require a separate restore job to run before restarting, CA-11 can be
used to incorporate restore JCL right into your regularly scheduled productions jobs.
Utilizing the CA-7 restart options, the CA-11 step can be forced to return a predetermined condition code.
The restore steps are then coded so they will only execute when the job is restarted with that specific condition code.
We mainly use "03" as the condition code for jobs running in this manner, since that is not a normal return
code, and there is no chance of this step getting that code unless you specify it.
Using this option will enable you to eliminate many of the steps involved in restarting jobs that require
restores before the restart. Here are the guidelines for using this handy feature of CA-11.
Page-11
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
Page-12
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
1) Enter the restore step(s) into the production job immediately before the step that requires the restore to run
before restarting. Be sure the restore steps being copied or entered in are numbered logically for easy reference.
Also be sure no step names are duplicated.
-----------------------------------------------------------------------------------------------------------------//G60N043W
//
//
//
//
//
JOB 'PROD-7753-PC'
'BUILD FORM FILES',
MSGLEVEL=(1,1)
MSGCLASS=G
CLASS=1, REGION=4096K.
COND=(3,LT)
2) Place a condition parm of (3,LT) on the jobcard. This will only allow steps with a condition code of 3 or less in
the job. NOTE: CONDITION PARAMETERS CODED ON THE JOBCARD ARE CHECKED BEFORE PARMS
CODED ON THE INDIVIDUAL STEPS. FOR THAT REASON, GREAT CARE MUST BE TAKEN TO INSURE
THE CONDITION CODING YOU CHOOSE WILL EXECUTE ALL STEPS PROPERLY
-----------------------------------------------------------------------------------------------------------------------------------------
3) Condition code the restore steps (3, NE, CA07RMS.RMS@20). This will ensure that these steps will only run
when the CA-11 step is forced to return a condition code 03. In a normal successful run of the job, these steps
will flush.
Page-13
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
//G60N014W
JOB 'PROD-7735-PC',
//
'BUILD FORM FILES',
//
MSGLEVEL=(1,1),
//
MSGCLASS=G,
//
CLASS=1,REGION=4096K
# SCC,COND=(3,LT,RMS@20)
# SCC,COND=(0,NE,*-RMS@20)
4) Add 2 #SCC statements to the JCL immediately after the jobcard. They are #SCC,COND=(3,LT,RMS@20)
and #SCC,COND=(0,NE,*-RMS@20). The first statement tells CA-7 to pass a condition code of 03 or less in
the CA07RMS step as acceptable and not flag the job as abended. The second tells CA-7 not to accept any
condition code other than 00 in all other steps.
-----------------------------------------------------------------------------------------------------------------------------------------
5) The CA-7 JOB screen must be set. The RO field should be #S. This tells CA-7 to read the #SCC entries added
after the jobcard. Those entries dictate which condition codes are acceptable, if any, and not to flag the job as
abended on these condition codes. ALSO, the job must be running through CA-11 to use this function, so the
INSERT-RMS field must be set to Y
Page-14
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
//****************************************************************************
//* STEP020 - USE INPUTED RELEASED COMPANIES TO BUILD CERT FILE
//*
//* STEP
|
RESTART
|
SPECIAL INSTRUCTIONS
//* ----------------------------------------------------------------------------------------------------------------//* STEP020
|
STEP012
|
RESTART IN STEP012 THROUGH
//*
|
|
CA-11 AND FORCE THE CA-11
//*
|
|
STEP TO RETURN A CONDITION
//*
|
|
CODE 03.
//****************************************************************************
//STEP020
EXEC PGM=UWNCFC02,
//
COND=(3,LT)
//IUWNCF02
DD
DSN=G60.PROD.NEWCASE.SORT,
//
DISP=SHR
//OUWNCF02 DD
DSN=G60.PROD.NEWCASE,CERT,
//
DISP=(NEW,CATLG,DELETE),
//
UNIT=DISK,
//
SPACE=(TRK,(8,2),RLSE)
//*
---------------------------------------------------------------------------------------------------------------------------------------//*
//****************************************************************************
//* STEP012 - USE RELEASED COMPANIES TO REBUILD CERT FILES
//*
//* STEP
|
RESTART
|
SPECIAL INSTRUCTIONS
//* -----------------------------------------------------------------------------------------------------------------// STEP012
|
STEP012
|
THIS STEP WILL ONLY EXECUTE
//
|
|
ON A RESTART OF A STEP020
//
|
|
ABEND. FORCE THE CA-11 STEP
//
|
|
TO RETURN A CONDITION
//
|
|
CODE 03.
//****************************************************************************
//STEP012
EXEC
PGM=UWNCFC04,
//
COND=(3.NE.CA07RMS.RMS@20)
//IUWNCFR1
DD
DSN=G60.PROD.NEWCASE.CERT,
//
DISP=SHR
//OUWNCFR2 DD
DSN=G60.PROD.CMPY.SORT,
//
DISP=(NEW,CATLG,DELETE),
//
UNIT=DISK
//
SPACE=(TRK,(8,2),RLSE)
6) The documentation for the step requiring the restore should state the restart step (the first restore step) and
instructions to force the CA-11 step to get a condition code 03. ALSO, in the event one of the restore steps
would ABEND, to be restarted, the CA-11 step must again be marked to return a code 03, or the steps will flush.
It is good for this to be mentioned in the documentation of the restore steps as well.
7) As always, there are exceptions to the rule. If you use more than 1 set of restore steps in a single job, be sure to
use different condition codes. For example, code 1 set of restore steps to run if the CA07RMS step returns a
condition code 03. But code the other set of restore steps to run if the CA07RMS step returns a condition code
01. Since 01 is less than 03, the remaining steps coded (3,LT) will still execute.
Page-15
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
Page-16
/var/www/apps/conversion/tmp/scratch_5/263057800.doc
Description
The FSTRUC command. If you list the trigger job it will list all jobs in that structure
The LJOB command. Lists items such as which schedule the job is on, if the job is
executable, job requirements, dependencies, triggers, etc.
Active jobs
Jobs waiting to be submitted. They have some type of dependency on them. The
dependency can be a job dependency, a time dependency, or a user requirement.
Another view of PF 12. This view gives you the actual dependencies that the job is
waiting for. If you want to just see your particular job instead of all jobs, at the end of
the pf4 command, type ,job=jobname
Jobs waiting that are already submitted. All dependencies have been met and the job is
just waiting to be run. The jobs will go from the PF12/PF4 screen to this screen.
Jobs in abended status
Page-17
/var/www/apps/conversion/tmp/scratch_5/263057800.doc