Different Tools That We Use For Monitoring (Ca-7, CA-11, $avours)

DIFFERENT TOOLS THAT WE USE FOR MONITORING (CA-
7, CA-11, $avours)
CA-7
CA-7 is an automated production control system. It is an online system that automatically

controls, schedules, and initiates work according to time-driven and even-driven activities
 Time – Driven : - Jobs run based on the time specified in the Job.
 Event – Driven : - Jobs are dependent on other Jobs and run only when they are
completed.
These time-driven and event-driven facilities are used to schedule CPU production jobs.
By using the CA7 job triggering feature a series of production jobs can be submitted
based on the successful completion of one single job
CA-11
CA-11 is an Automated Rerun and Tracking System. It can be used as an effective

management tool in a production environment. CA-11 is designed to perform as a Run
Handler, and as a Job Tracking System or a combination of both.
 RUN HANDLER
The Run Handler provides the means for automatically handling all MVS catalog
maintenance, dataset maintenance, and GDG bias adjustments for job reruns and
restarts
 JOB TRACKING SYSTEM
The Tracking System captures job execution data, permitting you to analyze the
impact of reruns on personnel and resources. The Tracking System provides for
retention of history data in the Job Execution History File.
$AVRS (Sysout Accumulation Viewing / Retrieval System)
$AVRS is mainly used to check the sysout of a job, once the job got abended or to check
the output of the job once it completes.
By entering into the $AVRS screen we can able to view the PROCSTEPs &
STEPNAMEs of a job along with its CONDCODE (condition code)
Steps to get into $AVRS
For SYS1/SYS7, $AVRS of SYS1 will be used to check the sysout of a job
& For SYS2/SYS4/S4HS, $AVRS of SYS2 will be used.
 Type $ in the ISPF panel of SYS1/SYS2 to get into $AVRS

 Select the $AVRS Database in the popup window (i.e) AP, MC, SS, DR according to
the job & hit Enter
 Enter the Jobname in the Name field & Hit enter
 Check the sysout of the job for the current date & time in the $AVRS JOB
SELECTION Panel displayed
- THU 05 APR 2007.095 ------ $AVRS JOB SELECTION ------------------ ROW 1 OF 2

COMMAND ===> SCROLL ===> PAGE
S=BRS,F=FIL,P=PRT,I=INF,D=DEL,O=ODS,A=ANN #LINES TOTAL 1303
SEL# ACT JOBNAME JOB # C ACK CCODE START DATE TIME FILES
_ 1 G2CT86AA 8305 J RC=0000 MON 02 APR 2007.092 12:12 7
_ 2 I G2CT86AA 2623 J RC=0000 WED 04 APR 2007.094 12:17 7
******************************** END OF DATA **********************************
 Toggle before the current sysout of the job & type I to view the stepwise return code
information
--------------------------- STEP INFORMATION -------------------------------------LINE 1 OF

COMMAND ===> SCROLL ===> PAGE
NAME: G2CT86AA JOB 2623 PGNAME: JCP
START: WED 04 APR 2007.094 12:17 FILES: 7 LINES 570 PAGES: 8
END: WED 04 APR 2007.094 12:21 CLASS: J CODE: RC=0000 USER: G2IUC7B
---- STEPNAME -- PROCSTEP -- CONDCODE ------ CPU TIME -------------------------
1. CA07RMS RMS@2X 0000 0MIN 00.02SEC
2. STEP01 0000 0MIN 31.27SEC
3. STEP02 0000 0MIN 08.33SEC
******************************** END OF DATA **********************************
INTRODUCTION OF CA-7
CA-7:
CA-7 is an online, real time, interactive system which automatically

Controls, schedules and initiates work according to time-driven and / or event-driven
activities.
CA-7 provides information from the database and queued sets. This information
can be used to investigate the datasets, determines status of a task from the queue, review
JCL or control cards, etc.
JOB:
A task performed by a computer system. For example, printing a file is a job. Jobs can
be performed by a single program or by a collection of programs.
BATCH CYCLE
Sequencing of Jobs to run in order is called Batch Cycle. Here Successive Jobs are
initiated automatically when the previous Jobs are completed and all requirements are
satisfied.
SCHID:
A job can be a part of different batch cycles. To run the same job in different batch
cycles, we use schid.
 Schids can be any number between 1-255.
 Every job running in Ca7 should have a Schid.
 Schid is very important when triggers are on.
Importance of Schid:
For example, on schid 1Job1 may trigger Job 2, but on schid 3 Job 1 may trigger Job
A CA-7 schedule job can be defined with a number of diff schedule ids.Each schedule
id can define different scheduling dates, execution environments, sets of jobs, job
statements etc.
PRODUCTION JOBS:
The jobs which are defined to CA-7 are production jobs. As a production monitor we
need to give more importance to the production jobs.
If the job has a job definition then it is a production job, we will check by using the
command  JOB, JOBNAME
FUNCTION: LIST (ADD,DELETE,DD,PURGE,DELPRRN,FORMAT,LIST,UPD)
JOB: G1QQ21PD
GENERAL: SYSTEM: FLEETXTR JOBNET: OWNER: UID: 20
JCL: ID: 0 MEMBER: G1QQ21PD RELOAD: N EXEC: Y RETAIN-JCL: N

LIB:
REQUIREMENTS: HOLD: N JCL-OVRD: N USE-OVRD-LIB: N VERIFY: N MAINT: Y
SATISFACTION LEAD-TIME: JOB: 0 DSN: 0 ARFSET:
EXECUTION: MAINID: SY3 INSERT-RMS: Y COND-CODE: 0 RO: LT
NON PRODUCTION JOBS
The jobs which are not defined to CA-7 are non-production jobs.These are also
called User jobs. We cannot demand a non production job.We will run the job using Run
command.
User jobs do not have any schid.
FUNCTION: LIST (ADD,DELETE,DD,PURGE,DELPRRN,FORMAT,LIST,UPD)

JOB: GH0BYTE
GENERAL: SYSTEM: JOBNET: OWNER: UID:
JCL: ID: MEMBER: RELOAD: EXEC: RETAIN-JCL:

A (001)-Job A with schid 001
LIB:
Ljob, job=D, list=depj
REQUIREMENTS: HOLD: will
JCL-OVRD: USE-OVRD-LIB: VERIFY: Frjob,
MAINT: job=D will tell you
SATISFACTION LEAD-TIME:
display the jobs for which JOB: DSN: ARFSET: how job D enters the
D is the internal job. A (001) T request queue. It will
EXECUTION: MAINID: INSERT-RMS: COND-CODE: RO:
r
For D, S1, S2 display as follows
DONT SCHEDULE -- BEFORE: AFTER:
and S3 are the i D
successor jobs g For D, ABC
B (001) C
g are
INTRODUCTION ABOUT PREDECESSOR / SUCCESSOR/ B
TRIGGERED / by
triggered
TRIGGERED BY / STANDALONE JOBS IN CA-7 e A
jobs
r
C (001)
S1The following S3 us to know about the given eterms that are used in CA-7
S2 figure helps
d
 Predecessor Jobs Predecessor jobs
 Successor Jobs D b
 Successor
Triggered Jobs y
 jobs
Triggered by Jobs
P1 P2 P3
 Standalone Jobs E (001)
Fstruc, job=D will Ljob, job=D, list=rqmt will

display the jobs that will F (001) T display all the internal
be triggered by job D. It r jobs
will display as follows i Of job D For D, P1P2
D For D, g and P3 are the
G (001)
E EFGH are g Predecessor
F triggered e jobs.
G jobs r
H H (001) e
d
standalone job
1. Here Job D is the job which is taken as reference to show all the commands.
2. Here Job A with schid 001is the first job which will trigger the batch cycle. Job A
with schid 001 triggers B which Triggers C and inturn C will trigger D.
3. So the Entry of D with schid id 001 into the CA-7 request queue depends on the
completion of job C with Schid 001.
4. So if you get a request to check the status of the job D, We need to follow the
following steps.
 Check whether the job is in the Queue or not by giving the command LQ,
job=job name.
 If you get a message no records found, check whether the job ran fine or not
by giving the command Lrlog, job=job name.
 IF you find a completed instance, we can leave that job. Other wise check the
last successful run of the job by giving the command lprrn, job=job name.
 Get the entry mode of the job. There are three types of modes.
o SSCAN: These are time dependant jobs i.e the entry of the job into the
queue depends on the Time. If these jobs are not in the queue, we need
to check the schedule of the job by giving the command,
 LSCHD,job=jobname,list=cals.
 This command will display the calendar of the job and we can
get whether the job is scheduled on that day or not
o AUTO: These jobs are event triggered jobs i.e the entry of the job into
the queue depends on the successful completion of the job that
triggered this job. Here in the above figure Except A(001) and p1 p2
p3 and s1,s2 s3 all the other jobs are auto jobs. Job D is an AUTO job.
 For Example, If Job D is not in the queue,we need to check the
reverse structure of the job D by using the command.
 Frjob, job=D.This will display all the jobs that will trigger job
D.
 We need to check whether any job in the given structure is any
of the queues or not. If you find any job in the queue.
 In this Example,we need whether any of the jobs A,B,C in the
request queue or not.
o DEMAND: These jobs Enters into the Request queue when demanded
by the operator upon a request by using the command DEMAND,
Job=Job name.
 If the job is a demanded job, we can inform the user that the
job is a demanded job.
o RUN: If the Entry mode of the job is RUN.i.e The job is a non ca7 job
or it entered into ca7 by using RUN command. This will not satisfy
any requirements.
INTERNAL JOB REQUIREMENT OR PREDECESSOR JOBS
o Internal jobs are the jobs where the main job come into the request
queue with these internal jobs as the requirements and the main job
will remain in the queue until all the internal jobs ran successfully.
o In the above example,the After the completion of Job C,JobD will be
triggered and enters the request queue with P1,P2 and P3 as the
internal jobs.After job D finds the successful completion of Job P1,P2
and P3 the job D will start running.
o Job D will not check for the schids of P1,P2 and P3.It is Independent
of the schids.
o Entry of Job D into the request queue doesnot depend on the
completion of Job P1,Job P2 and Job P3.
o These jobs are also known as predecessor jobs.
o Ljob,job=jobname,list=rqmt will show all the requirements that should
be satisfied before entering into the active queue.
o For Job D,P1,P2 and P3 are predecessor jobs and for job P1,P2 and P3,
job D is the Successor job.
INTRODUCTION OF TRIGGERED BY AND TRIGGERED JOBS
 Triggered by Jobs are the jobs which upon the completion trigger the main
job i.e. that jobs are responsible for the main job to come into the request
queue.
 Triggered Jobs are the jobs which will be triggered by the main job as soon
as its completion.
 For e g: Consider jobs A->B->C->D->F->G->H.
 Job D will come into request queue after completion of Job A, Job B and Job
C .Then Jobs A, B, C are Triggered jobs.
 After successful completion of those three jobs Job D comes into the request
queue.
 Then Job D triggers Job F,Job G, Job G .If Job D completes successfully then
only the other three jobs(F,G,H)
 Completes.
 Job triggering is usually performed after the schedule ids are defined.
Triggering defines the execution sequence of the application jobs. The CA-7
Job Triggering screen is used to define a list of triggered jobs for a specific
job. Job triggering can be limited to a specific schedule ID.
SCHID 000 means that the triggered job initiated by a job with any schedule id.By
default, a job’s schedule id is passed to the triggered job unless otherwise specified in
the TRIG field
COMMAND TO CHECK THE TRIGGERED BY JOBS AND TRIGGERED JOBS
LJOB,JOB=G1JZAPWX,LIST=TRIG
JOB=G1JZAPWX LIST=TRIG DATE=07.085 PAGE 0001
MSGS 0010
JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
G1JZAPWX 000 G1JZAPWX VFSPMS 013 SY1 *NONE* *NONE* 001 004 0992 07083/0203
----------------- TRIGGERED BY JOBS/DATASETS/NETWORKS ------------------

JOB=G1JZDONE SCHID=001 QTM=0010 LEADTM=0000 SUBMTM=0000
PREDECESSOR JOBS AND SUCCESSOR JOBS :

• Internal jobs are the jobs where the main job comes into the request queue with
these internal jobs as the requirements and the main job will remain in the queue
until all the internal jobs ran successfully.
• In the above example, the after the completion of Job C, JobD will be triggered
and enters the request queue with P1, P2 and P3 as the internal jobs. After job D
finds the successful completion of Job P1, P2 and P3 the job D will start running.
• Job D will not check for the schids of P1, P2 and P3.It is Independent of the
schids.
• Entry of Job D into the request queue does not depend on the completion of Job
P1, Job P2 and Job P3.
• These jobs are also known as predecessor jobs.
• Ljob, job=jobname, list=rqmt will show all the requirements that should be
satisfied before entering into the active queue.
• The Job Dependency feature ensures that all required predecessor jobs have
completed processing successfully before any successor batch jobs are released.
COMMAND TO CHECK THE PREDECESSOR JOBS AND SUCCESSOR JOBS
 Ljob, job=jobname, list=rqmt  predecessor jobs
G1JO0BCV 000 G1JO0BCV VFSCATS 013 SY3 *NONE* *NONE* 003 178 3208 07082/0533
---------------- REQUIREMENTS AND NETWORK CONNECTIONS -----------------

JOB=IDMVPCUP SCHID=000 VRSN=97105/1405 LEADTM=08
JOB=G1JO07CV SCHID=000 VRSN=94277/1423 LEADTM=01
JOB=G1JO26CV SCHID=000 VRSN=94277/1423 LEADTM=01
DSN=G1JM00AT.APPVFS.DCDEV.LOADLIB **** PERM DSN ****
DSNBR=DS052117 SCHID=000 VRSN=94278/1031
CREATED BY **NONE**
DSN=G1ITIDAP.IDMSR.RELTEN2.LOADLIB **** PERM DSN ****
DSNBR=DS014811 SCHID=000 VRSN=94278/1031
 Ljob, job=jobname, list=depj  Successor jobs
LJOB,JOB=G1JP75PW,LIST=DEPJ
JOB=G1JP75PW LIST=DEPJ DATE=07.085 PAGE 0001
MSGS 0006
JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
G1JP75PW 000 G1JP75PW CEFPMS 250 SY1 *NONE* *NONE* 003 115 0971 07084/0111
--------------------------- SUCCESSOR JOBS ----------------------------

JOB=G1JN20PW SCHID=000
STANDALONE JOB: The job neither triggers any job nor it will be an internal job of
any other job. In the above figure, H is a stand alone job.
DETAILED DISCUSSION ABOUT ALL THE QUEUES
 Request Queue
 Ready Queue
 Active Queue
REQUEST QUEUE
COMMANDS TO VIEW THE JOBS IN REQUEST QUEUE:

TTD
LREQ – Displays all the Jobs which are in Request Queue
LREQ
LIST= DATE=07.039 PAGE 0001
JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB
LREQ,JOB=G1KLD5PD
NAME NAMEJOB=G1KLD5PD
LIST=STATUS JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN
DATE=07.039 ID0001
PAGE MODE REQ
STATUS
G1KLC2PD
NAME NAME REQJOB#8273 DEADLINE
039/1301 039/1300 039/1310
SUB/START *NOEX*
DUE-OUT 009 AUTO
SPEC/RUN ID 001
MODE REQ
G1KLD5PD
STATUS REQ 8589 039/1731 039/1730 039/1740 SY3- 004 AUTO 002
G1QT56PD REQ 8785 039/0841 *NONE* 039/0850 SY3- 003 AUTO 001 LATE
G1IVFF00 REQ 8565 039/2159 *NONE* 039/2249 SY3- 002 AUTO 001
G1KLC3PD
G1KLD5PD REQ REQ 8875
8589 039/1031
039/1731 039/1030
039/1730 039/1040
039/1740 SY3-
SY3- 009 004 AUTO
AUTO 001 002
G1JOSTCV REQ 8795 039/1016 039/1015 039/1025 SY3- 011 SSCN 001
GISS0GPD REQ 8848 039/1154
------------------------- 039/1100 039/1200
REQUIREMENTS STATUS SY3- 011 AUTO 001
-------------------------
MEMO REQ 7817 039/1051 039/1000 039/1100
_______ WAITING FOR SUBMIT TIME (07039 17:30) *NOEX* 007 AUTO 001
G1JOB1QD REQ 8873 039/0942 039/0945 039/0950
_______ INTERNAL JOB=G1KLP2PD DATE/TIME=07038/2200 SY1- 008 AUTO 001
G1XRZZPH REQ 8849 039/1001 039/1000 039/1010 SY3- 003 AUTO 001
SLIF-00 REQUEST COMPLETED AT 09:41:44 ON 07.039
LREQ,JOB=Jobname – Displays a particular Job in Request Queue

JOB DEFINITION SCREEN
Mainly we use this screen to check whether a job is a CA7 job / not
We can also use this screen

 To check whether the job is Executable / not
 To know the Main-id of the job
 To know on which Application the job is running.
 To know whether the CA-11 RMS step is automatically inserted at
execution time of the job by CA-7
COMMAND USED TO GET INTO THIS SCREEN:
Type JOB as a top line command
(Or)
Type DB.1 in the top line
------------------------- CA-7 CPU JOB DEFINITION --------------------------

FUNCTION: (ADD,DELETE,DD,PURGE,DELPRRN,FORMAT,LIST,UPD)
JOB:
GENERAL: SYSTEM: JOBNET: OWNER: UID:
JCL: ID: MEMBER: RELOAD: EXEC: RETAIN-JCL:

LIB:
REQUIREMENTS: HOLD: JCL-OVRD: USE-OVRD-LIB: VERIFY: MAINT:
SATISFACTION LEAD-TIME: JOB: DSN: ARFSET:
EXECUTION: MAINID: INSERT-RMS: COND-CODE: RO:

DONT SCHEDULE -- BEFORE: AFTER:
MESSAGES: LTERM: REQUIREMENT-LIST: PROMPTS:

ERROR MSGS -- RQMTS NOT USED: DSN NOT FOUND:
RESOURCES: REGION: CLOCK-TIME: CPU-TIME:

CLASS: PRTY: MSGCLASS:
TAPE DRIVES...TYPE1: M C TYPE2: M C
PROGRAM: SM20 MSG-INDX: 00 -- DB.1 -- 07.046 / 17:18:56 MSGS 0006

MESSAGE: ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE
FIELD DESCRIPTIONS
FUNCTION:
ADD : Adds a job to the database.

DELETE : Deletes a job and its associated data from the database
DD : Same as DELETE, but deletes any data sets which this job references if
the data sets have no users and no documentation, and do not cause job
triggering
PURGE : Same as DD, but also deletes job trigger definitions that trigger the job
Being deleted, job requirement definitions that require the job being
deleted; and, if the CA-11 interface is active, deletes the CA-11 CMT
member for the job being deleted
DELPRRN : Deletes the JCL saved in the trailer queue from the job's prior run.
FORMAT : Clears the screen of all input data.
LIST : Lists a job and job related information. In batch, a formatted screen is not
listed; only a found or not found message is returned.
UPD : Updates database information about a job.
JOB: The job name on which the indicated function is to be performed.
GENERAL Indicates that this section of the screen contains general information
:
about the job. No input is allowed for this field.
SYSTEM : The user-defined application system name of which this job is a part.
JOBNET : The name of a CPU job network of which this job is a part.
OWNER : ID identifying ownership of this job.
UID : The CA-7 user security identification.
JCL: Indicates that this line of the screen contains JCL information about
the job. No input is allowed for this field.
ID : A numeric index value associated with a JCL library. Two values

have special significance: 254 is reserved to indicate the override
library (see USE-OVRD-LIB field for additional information) and
255 is reserved for use with the HELP library
MEMBER : The JCL library member name.
RELOAD : Indicates if this job's JCL is to be reloaded (Y, N, or X).
EXEC : Indicates whether this job should be executed (Y or N).
RETAIN-JCL: Indicates whether execution JCL is to be retained in the trailer queue
after a successful run (Y or N).
LIB : JCL library identification
REQUIREMENTS: Indicates that this section of the screen contains requirements

information about the job. No input is allowed for this field.
HOLD Indicates whether this job is to be placed in a hold status when it

:
enters the request queue (Y or N).
JCL-OVRD : Indicates whether this job needs manual JCL overrides before it can
be submitted (Y or N).
USE-OVRD-LIB: Indicates whether the JCL is to be retrieved from the JCL Override
library (JCLID=254) for the next run only (Y or N). This field is
automatically set back to N the next time the job comes into the
request queue.
VERIFY : Indicates whether this job requires any presubmission manual verification
(Y or N).
MAINT : Indicates whether this job is a maintenance job (for example, a
system utility) with no production data set requirements (Y or N).
SATISFACTION: Indicates that this area of the screen contains lead time information
LEAD-TIME about the job requirements.
JOB : The number of hours to be considered when satisfying job dependent
requirements.
DSN : The number of hours to be considered when satisfying data set
requirements.
ARFSET : Names the collection of ARF definitions that apply to this job
EXECUTION: Indicates this screen section contains execution information about the
job.
MAINID : Indicates on which CPU the job may or may not be scheduled.
INSERT-RMS :Indicates if the CA-11 RMS step is to be automatically inserted at

execution time by CA-7. Specify Y to insert the step with the
CA-11 processing code of P. Enter N to indicate the RMS step is
not to be inserted
COND-CODE : Used with RO (relational operator) to define the job-level condition
codes used to determine if a job executes successfully or not.
RO : Indicates the relational operator of the condition code
(COND-CODE) or if the step level #SCC statements are being used
in the job's JCL.
DONT SCHEDULE
BEFORE : Indicates that this job is not to be scheduled before this date and
time. Especially helpful for timing the start of new jobs.
AFTER : Indicates that this job is not to be scheduled after this date and time.
Especially helpful for timing permanent discontinuation of a job.
MESSAGES: Indicates that these lines of the screen contain information about
messages which may occur for the job.
LTERM : Messages about this job are to be routed to this logical terminal
name.
REQUIREMENT
LIST : Indicates whether preexecution requirements are to be listed for this
job when it enters the request queue (Y or N).
PROMPTS : Indicates if prompt messages are to be issued if this job is late
(Y or N).
ERROR MSGS -- RQMTS NOT USED:
Indicates whether error messages for job requirements not used are to
be issued (Y or N).
DSN NOT FOUND: Indicates whether error messages for data sets used at execution time
but not found in the CA-7 database are to be listed (Y or N).
RESOURCES: These lines contain resource information about the job.
REGION : The region size required by this job.

CPU-TIME : CA-7 maintains weighted average CPU time usage values for each
job in its database
CLASS : Indicates the CA-7 WLB job class.
PRTY : Indicates the CA-7 WLB job priority.
MSGCLASS : Indicates the job's message class. Informational only.
TAPE DRIVES : Indicates that this line of the screen contains informationabout tape
drives needed for the job.
TYPE1 : Indicates that the two following fields (M and C) contain information
about TYPE1 tape drives needed for the job.
M : It is used to update a job where tape drive requirements have been
significantly changed, higher or lower, and the job has not been reloaded
since the change.
C : This field indicates the calculated value for the number of TYPE1
tape drives needed for the job.
TYPE2 : Indicates that the following two fields (M and C) contain information
about TYPE2 tape drives needed for the job.
M : Indicates a manual override value for the number of TYPE2 tape

drives needed for the job.
C : This field indicates the calculated value for the number of TYPE2
tape drives needed for the job.
Different modes by which the Jobs comes in to the Queue
There are five ways by which the jobs comes into the Queue
 SSCAN
 AUTO
 DEMAND
 RUN
 LOAD
SSCAN: In this mode, the entry of the jobs into the queue depends on the Time (i.e)
these are time dependant jobs .If these jobs are not in the queue, we need to check the
schedule of the job by giving the command,
 LSCHD,job=jobname,list=cals
This command will display the calendar of the job and we can
get whether the job is scheduled on that day or not
G1SGYFSD REQ 8883 039/1156 039/1155 039/1205 SY3- 006 SSCN 001
AUTO: In this Mode, the entry of the job into the queue depends on the successful
completion of the job that triggered this job (ie) these jobs are event triggered jobs
 FRJOB, job=xxxxx
This will display all the jobs that will trigger job xxxxx
G1KLD5PD REQ 8589 039/1731 039/1730 039/1740 SY3- 004 AUTO 002
DEMAND: In this mode, the Jobs Enters into the Request queue when demanded by the
operator upon a request by using the command. This Demand Mode will satisfy the
requirements of the job(if any).
 DEMAND, Job=Job name
This will puts the job in the ca-7 request queue.

if there are no requirements to be posted, job will
automatically become active.
RUN: If the Entry mode of the job is RUN.i.e If the job is a non ca7 job or it entered into
ca7 by using RUN command, then it will not satisfy any requirements.
LOAD:
 The LOAD/LOADH command is to create or recreate job profile data in the database
(i.e.,) builds the database profile for a new job or rebuilds the profile for a job whose
JCL was changed.
 Job profiles should agree with the current JCL. Therefore, any changes to the
JCL must be resynchronized with the database by loading the job.
 When a job is scheduled using the LOAD command, the LOAD step executes but the
rest of the job's JCL is flushed. The job returns to the request queue with a JCL error.
 The LOAD command cannot be used for a job that has been marked as nonexecutable
(for example, EXEC=N) on the DB.1 screen.
 LOAD,JOB=jobname,{Dotm=hhmm,leadtm=hhmm}
This command will load a job,which specifies the Due-out

time & Elapsed Lead time for processing.
 LOAD,JOB=jobname,{Jclid=nnn}
This command will identifies the JCL data set which contains
the execution JCL to be submitted.
[Note : RELOAD field in the DB.1 screen is an alternative to this command]
DIFFERENCE BETWEEN RUN AND DEMAND MODE
RUN DEMAND
RUN will force immediate scheduling of a DEMAND will force immediate
job without verifying the availability of any scheduling of jobs controlled by CA-7 by
input requirements verifying the availability of input
requirements
The RUN will run a job without satisfying The DEMAND will run a job by posting
any requirements or triggering anything any requirements or triggering anything
else else
Running a job through RUN will Demanding a job into the request queue
automatically result in immediate does not automatically result in immediate
Submission for execution Submission for execution.
SCHID is not required when running a job SCHID is required when running a job
through RUN through DEMAND
Through RUN we can run both CA-7 & But Through Demand, only CA-7 jobs can
non CA-7 jobs run
RUN wont take Job Definition panel into Demand will consider the Job Definition
account while running a job panel while running a job
SKELETON STATUS
When a Job comes with a SKELETON status, it means that CA-7 cannot bring the JCL
for the job into the request queue.
Main Reasons why the job comes with Skeleton status are:
 When the JCL is not located in the specified JCL library (production or override)
 If the JCL library is unavailable (being compressed, etc.)
 CA-7 JCL control records (#SCC, #JI, etc) are not coded properly
LQ,ST=SKEL - command used to list the jobs in skeleton status
[Note: If the job is in skeleton status, the job will remain in the request and it will
not run until we cancel the job and redemand it]
PROCEDURE TO FOLLOW WHEN THE JOB IS IN SKELETON STATUS
 Contact the Analyst and inform him that the job is in skeleton status.
 Open a GEMS ticket, update it and assign the ticket to the appropriate scheduling
group.
 As per the Analyst, cancel the job from the restart queue and then re-demand the same
to the request queue correcting the library. Make sure the same SCHID is used when
re-demanding it.
 Cancellation of the job from the request queue, which is in the skeleton status, will
not work by putting a “C” beside the job name. Instead we have to issue the following
command:
CANCEL, JOB=ca7-id,REASON=SKELTON STATUS, FORCE=YES
XQM PANEL (CPU JOB STATUS SCREEN)
XQM Panel is mainly used to check the jobs that are in REQUEST Queue waiting
for some requirements as well as the abended jobs that are waiting for Restart
requirement.
-------------------------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS -----------------

F-JOBNAME-- CA7#
G1OLCHKA 1103 JOB: G1OLCHKA
SEQ: ENTRY
QUEUE: REQ
LIST: ALL
FUNCTIONS:
C=CANCEL
F=RESTART
H=HOLD
J=JCLOVRD
P=RSVP
Q=REQUEUE
R=RELEASE
S=SUBTM OFF
U=UPDATE
V=VERIFY
X=RQMT POST
E=EDIT QJCL
PROGRAM: QM20 MSG-INDX: 00 -- QM.1-X -- 07.091 / 11:23:45 MSGS 0004
MESSAGE: ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE
FIELD DESCRIPTIONS
F : Function field
JOBNAME : CA-7 job name
CA7# : CA-7 job number
JOB : Job name selection criteria
SEQ : Display sequence
QUEUE : Queue that was searched: request, ready, or active

LIST : Display selection criteria
FUNCTIONS: Possible line functions
As this Panel is an Editable Panel, We can also update the status of the job by
FUNCTIONS like CANCEL, RESTART, HOLD, RELEASE, REQUEUE, UPDATE
RQMT POST, EDIT JCL etc.,
COMMANDS
XQ - Displays the jobs in the order they entered CA-7

XQJ – Displays the job alphabetically by Jobname
XQN- Displays the jobs in Numerical Order(i.e) by CA-7 ID
XQM – Displays the jobs in the order they entered CA-7 along with its requirements
-------------------------------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS) --------------

F-JOBNAME---J--I--E--U--N-SHJV F-JOBNAME---J----I---E--U---N--SHJV
CLSBAR01 . . . . . ……….S . G1OLHRBR . . . . . …….……. S JOB: *
CSEXNWE3 . . . . . ……...S G1OLHRLY . . . . ……….….. S SEQ: JOBNAME
CSTPEME1 . . . . ……… *RST G1OLMN01 . . . . ……….…... S QUEUE: REQ
GISC04PD . . . . . …………S G1OLMN15 . . . . ……….….. . S LIST: ANY
G1GACHEK . . . . ……… . S G1OLQMN1 . . . . ………….. . S
G1IVFF00 . 8 . . ………… G1OLQMN1 . . . …………. .. . S FUNCTIONS:
G1OLAFQD . . . ………. . . G1OLQSRP . . . . …………... . S C=CANCEL
G1OLAFQD . . . ……….. . S G1OLQSRP . . . ……….…… . S F=RESTART
G1OLCHEK . . . ……….. . S G1OLREPT . . . …………. … . S H=HOLD
G1OLDAQ1 . . . ……….. . S G1OL250P ….1 . . …………. . . J=JCLOVRD
G1OLDAQ2 . . . ………. . . S G1OL250P ….1 . . . . P=RSVP
G1OLDUM1 . . . ……… . . S G1OL280A . . . . …………….. S Q=REQUEUE
G1OLFRAQ . . … 1 …….. . . G1OL280B . . …………….. . . S R=RELEASE
G1OLGPQA . . . ……….. . S G1RJ90OE . . …………….. . . S S=SUBTM OFF
G1OLGPQB . . . . ………... S G1RTV5PD …. 1 . .. . . U=UPDATE
G1OLGP2A . . . ………... . S G1SGS2RT . . . …………… . . S V=VERIFY
G1OLGP4B . . . ……….. . . S G2A111PM 1 . . . . X=RQMT POST
G1OLHRBR . . . ……….. . S G2A2ADRJ . . …………… . . . S E=EDIT QJCL
PROGRAM: QM20 MSG-INDX: 00 -- QM.1-M -- 07.091 / 12:30:59 MSGS 0010
(USE 'PF8' KEY TO SEE NEXT PAGE)

The jobs will be displayed in this XQM panel for one/more of the following requirements
to be completed:
J Number of outstanding job requirements

I  Number of outstanding internal data set requirements
E Number of outstanding external data set requirements
U Number of outstanding user requirements
N Number of outstanding network requirements
S Indicates an outstanding submit time requirement
Special character settings beginning with an asterisk may appear

under the SHJV heading to indicate special situations. They are:
*CMP Indicates job is in completed status
*ERR Indicates an error occurred attempting to collect the
requirement information
*NOF Indicates job not found in requested queue. (This normally
happens when you post the last requirement for a job, and
it moves from the request to the ready queue.)
*RST Indicates job is in restart status
*SKL Indicates job is in skeleton status
H Indicates an outstanding hold requirement
J  Indicates an outstanding JCL override requirement
V Indicates an outstanding verify requirement
COMMANDS TO CHECK THE XQM PANEL
XQ - Displays the jobs in the order they entered CA-7

XQJ – Displays the job alphabetically by Jobname
XQN- Displays the jobs in Numerical Order(i.e) by CA-7 ID
XQM – Displays the jobs in the order they entered CA-7 along with its requirements
-------------------------------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS) --------------

F-JOBNAME---J--I--E--U--N-SHJV F-JOBNAME---J----I---E--U---N--SHJV
CLSBAR01 . . . . . ……….S . G1OLHRBR . . . . . …….……. S JOB: *
CSEXNWE3 . . . . . ……...S G1OLHRLY . . . . ……….….. S SEQ: JOBNAME
CSTPEME1 . . . . ……… *RST G1OLMN01 . . . . ……….…... S QUEUE: REQ
GISC04PD . . . . . …………S G1OLMN15 . . . . ……….….. . S LIST: ANY
G1GACHEK . . . . ……… . S G1OLQMN1 . . . . ………….. . S
G1IVFF00 . 8 . . ………… G1OLQMN1 . . . …………. .. . S FUNCTIONS:
G1OLAFQD . . . ………. . . G1OLQSRP . . . . …………... . S C=CANCEL
G1OLAFQD . . . ……….. . S G1OLQSRP . . . ……….…… . S F=RESTART
G1OLCHEK . . . ……….. . S G1OLREPT . . . …………. … . S H=HOLD
G1OLDAQ1 . . . ……….. . S G1OL250P ….1 . . …………. . . J=JCLOVRD
G1OLDAQ2 . . . ………. . . S G1OL250P ….1 . . . . P=RSVP
G1OLDUM1 . . . ……… . . S G1OL280A . . . . …………….. S Q=REQUEUE
G1OLFRAQ . . … 1 …….. . . G1OL280B . . …………….. . . S R=RELEASE
G1OLGPQA . . . ……….. . S G1RJ90OE . . …………….. . . S S=SUBTM OFF
G1OLGPQB . . . . ………... S G1RTV5PD …. 1 . .. . . U=UPDATE
G1OLGP2A . . . ………... . S G1SGS2RT . . . …………… . . S V=VERIFY
G1OLGP4B . . . ……….. . . S G2A111PM 1 . . . . X=RQMT POST
G1OLHRBR . . . ……….. . S G2A2ADRJ . . …………… . . . S E=EDIT QJCL
PROGRAM: QM20 MSG-INDX: 00 -- QM.1-M -- 07.091 / 12:30:59 MSGS 0010
(USE 'PF8' KEY TO SEE NEXT PAGE)

DIFFERENT TIMES:
DEAD LINE TIME: This is the time before which the job needs to satisfy all the
requirements and it should start execution. In other words, the job needs to move from
the request queue to ready queue before the deadline time.
DUE OUT TIME: This is the time before which the job needs to complete its execution.
In other words the job should be out of CA-7 before the Due out time.
LOOK BACK TIME: Look back time is the time interval where the successor job will
look back from the time it enters the request queue.In this Interval the predecessor job
should start and complete successfully
ELAPSED TIME:
Average time of last five successful runs of the Job is called Elapsed time and is
calculated by CA7.
Procedure to check the look back time or lead-time
o Give jobconn,job at the command prompt.

o Give job name as successor job name.
o Give Function as list.
o It will display the look back times of all the internal jobs of that job.
If the look back time is 8 hrs.Check the time when the successor job that is late entered
into the queue and look back 8 hrs from that time. That becomes the interval for that
predecessor job. If the predecessor job starts and ends in that interval then the successor
job will not come into the queue with the predecessor job as the requirement.
The look back time starts from 1 – 98hrs i.e. minimum is 1 hour and maximum is
98hrs.
0 and 99 are special cases.
99: The requirement will be posted if and only if the predecessor job start and complete
successfully when the successor job is in the request queue.
0: There is no interval. The requirement will be posted if there is a successful run of a
predecessor job and that run is not satisfied by any of the instance of this successor job.
REMOVING JOBS FROM THE REQUEST QUEUE
Jobs can be removed from the Request Queue in two ways:
 Force complete
 Cancel
(1) FORCE COMPLETING JOB:
Force complete jobs through CA-7 when instructed by support

For job with a non zero return code.
Always appears on the screen. If used, the job is processed as if
a good end-of-job had occurred. This causes triggering and
requirement posting for other dependent jobs. Job triggering and
posting occur.
(i.e, successor job dependencies are satisfied and job triggering occurs).
 Go to XQM screen,
 Type ‘F’ beside the job,
 Type the reason and put a ‘X’ beside Force complete.
The screen is:

Note: Force completing a job will satisfy all the post execution requirements of a job
that needs to be satisfied if it completes successfully.
(2) CANCELING A JOB
The CANCEL command cancels jobs from the CA-7 queues. The command may
typically be used when lack of input for the scheduled run eliminates the need for that run
or when a scheduled run of a job was demanded to run ahead of schedule and should not
be run again. Jobs that go into SKELETON (no JCL attached) status must be canceled
specifying FORCE=YES. FORCE=YES will clear the CMT (Catalog Management
Table) so future runs will not attempt to use the restart information.
Use the CANCEL command to delete jobs from the CA-7 queues. This
command only removes the job from the CA-7 queues. Cancelation of a job in the CA-7
active queue or ready queue (if it has been submitted) does not cause termination of the
job's execution.
If the job needs to be CANCEL as per programmer, you can cancel a job with the
command
CANCEL, JOB=XXXX, REASON=PER USER, FORCE=YES
After command is issued the following message will be displayed on the screen:
For example:
JOB XXXX (6666) HAS BEEN CANCELED. - AND CMT CLEARED
CANCEL,JOB=6666,REASON=X PER APC,FORCE=YES (command entered to cancel

job number 6666)
Field Description:-
JOB NAME : Specifies the name of the job to be canceled.

JOB NUMBER : Specifies the job number of the job to be canceled.
REASON : Specifies the reason for the cancellation.
FORCE : Forces the cancellation of the job. If the job to dump the log data set is to
be canceled, FORCE=YES must be specified to prevent the job from being resubmitted.
Note: Before canceling the job, always cross check for any dependent job. If there
are any dependent jobs, inform customer before canceling.
DIFFERENCE BETWEEN CANCELING AND FORCE COMPLETING A JOB
Cancellation of a job does not automatically satisfy the requirements of other jobs
that are dependent upon the canceled job and job triggering DOES NOT occur.
Force complete flags the job as a normal completion and normal processing is performed
Note: Cancellation of a job in CA7's active queue does not cause termination of the
jobs execution. The execution must be terminated from an OS system console.
In addition, before canceling a job from the CA7 Request queue you must resolve any
issues regarding successor jobs that are dependent upon the job that is being canceled.
Use the LJOB,JOB=JOBNAME,LIST=DEPJ command to determine any other jobs
that are dependent upon the job being cancelled and consult the on-call person for
instructions on what action to take on the job. Also, use the
LJOB,JOB=JOBNAME,LIST=TRIG command to identify jobs that would normally be
triggered by the job being cancelled. Once again, consult the on-call person for
instructions on what action to take on the job.
READY QUEUE
COMMANDS TO VIEW THE JOBS IN READY QUEUE:

LRDY – Lists all the jobs, which is in Ready Queue.
LRDY
LIST= DATE=07.050 PAGE 0001
NAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID
MODE REQ STATUS
G2TE02PD RDY 1350 050/1433 *NONE* 050/1442 SY7- 001 AUTO 000 LATE
G2TR97PD RDY 1724 050/1635 *NONE* 050/1635 SY7- 001 DEMD 000 LATE
G2TRSCPD RDY 0941 050/1459 *NONE* 050/1459 SY7- 001 DEMD 000 LATE
G2TRKLPD RDY 1520 050/1547 *NONE* 050/1547 SY7- 001 DEMD 000 LATE
G2TR96PD RDY 1726 050/1636 *NONE* 050/1636 SY7- 001 DEMD 000 LATE
G2TRMJPD RDY 1769 050/1646 *NONE* 050/1646 SY7- 001 DEMD 000 LATE
LRDYP - Lists all the jobs which is in Ready Queue along with the priority & tape drives
needed for each job(Mainly we use this command to check whether the job
has been submitted to spool / not)
LRDYP
SEQ=PRTY DATE=07.050 PAGE 0001
JOB QUE CA-7 JOB TAPE1 TAPE2 CPU START TIME PRIORITY
NAME NAME NMBR CLS NBR/PRTY NBR/PRTY %UTLIL/PRTY MINS/PRTY ORIG/NEW
CLSBAR01 RDY 9444 0 00/000 00/000 000.000/000 L000/000 *255/0000

G2TR97PD RDY 1724 M 00/000 00/000 000.000/000 L000/000 100/0000
G2TRSCPD RDY 0941 0 00/000 00/000 000.000/000 L000/000 100/0000
G2TRKLPD RDY 1520 M 00/000 00/000 000.000/000 L000/000 100/0000
G2TRWAPD RDY 2486 B ..... JOB IS WAITING FOR VRM RESOURCES .....
G2TRWDPD RDY 2485 B ..... JOB IS WAITING FOR VRM RESOURCES .....
LRDYP,JOB=Jobname – List the resources for which the job is waiting(i.e.) tape drives,
barriers etc.,
LRDYP,JOB=G2TR97PD
JOB=G2TR97PD SEQ=PRTY DATE=07.050 PAGE 0001
JOB QUE CA-7 JOB TAPE1 TAPE2 CPU START TIME PRIORITY
NAME NAME NMBR CLS NBR/PRTY NBR/PRTY %UTLIL/PRTY MINS/PRTY ORIG/NEW
G2TR97PD RDY 1724 M 00/000 00/000 000.000/000 L000/000 100/0000

. CLASS BARRIER REACHED
SLIF-00 REQUEST COMPLETED AT 22:51:12 ON 07.050

LRDYR - List the outstanding job resource requirement information (i.e., unsatisfied
requirement) on CPU jobs in the ready queue
LRDYR
DATE=07.055 PAGE 0001
MSGS 0002
JOB SYSTEM MAIN JOB CPU CA-7# CPU/ELAPS TOTAL TAPES CPU% SUBMIT
NAME - NAME- -ID- C/PRT -ID NUMBR --TIME--- TP1 TP2 UTIL DATE/TIME
G2TE02PD TRAMS SY7 5/100 1511 00004/0004 00 00 01.67 *NONE*

G2TRBEVD SPS SY7 4/100 1573 00002/0004 00 00 00.83 *NONE*
G2TRHPJD SPS SY7 0/100 1574 00003/0004 00 00 01.25 *NONE*
G2TRNPPD SPS SY7 0/100 1575 00006/0004 00 00 02.50 *NONE*
G2TR97PD ENTRY SY7 M/100 1577 00005/0004 00 00 02.08 *NONE*
G2TR98PD ENTRY SY7 A/100 1602 00005/0004 00 00 02.08 *NONE*
REASONS WHY THE JOBS WILL WAIT IN THE READY QUEUE
Normally Jobs wont be in the READY Queue for a long time, Once it gets all its needed
resources, it will get into the ACTIVE Queue. But there are some reasons that the Jobs
will wait in the READY Queue :
 Job might have a JCL Job card Error

 Job might be in Contention with some other Jobs (i.e.,) the resources needed by
this job has been used by some other jobs. So Once those jobs completes, this job
will get that resource & it will enter into the ACTIVE queue
 Job might be waiting for JES Initiators as well as CA-7 Initiators
CA-7 BARRIERS AND CA-7 INITIATORS
CA-7 BARRIERS
CA-7 Barriers will establish the maximum number of jobs that can be submitted
concurrently in an associated job class. Barrier acts as a mediator between ca7 and
MVS.The number of jobs submitted to spool from ca-7 is controlled by barrier
CA7 INITIATORS:
CA-7 Initiators will determine the number of jobs submitted to the JES
DIFFERENCE BETWEEN MVS INITIATORS AND CA-7 INITIATORS
MVS Initiators will determine the number of jobs submitted to CPU whereas CA-7
Initiators will determine the number of jobs submitted to the JES
HOW TO CHECK FOR THE CONTENTION
Usually, a Job may be in contention with a JOB/ USER
JOB – The Job which holds may be a Production Job / User Job. If it is a production job,
then no need to take any action else if it is an user job then we need to cancel that job
because an user job should not hold the Production Job
USER – Sometimes some Users (userid) may hold the job. So at the time, their Ids should
be cancelled from the TSO session to make the job run
REQUEUE COMMAND
REQUEUE command is used to move jobs from the ready queue back to the
request queue (i.e) When a job gets struck up in the ready queue, due to JCLERR,
then, we can requeue the job, so that the job goes back to the (abended) request
queue from the ready queue
Command:
REQUEUE,JOB=JOBNAME,Q=RDY
[Note: Mostly, we use the requeue command to requeue the job in RDY queue only.
Because, if the job is in active queue, then, it means that the job is already submitted
to spool. So, on requeuing the job in active queue, creates another new instance in
Ca-7
One exception: for $HASP310 job (active q), we have to requeue
$HASP310 - The specified job is ended as a result of the abnormal end of the
address space.]
XUPD COMMAND (TO CHANGE THE PRIORITY OF THE JOB IN THE READY QUEUE)
XUPD command is used to displays the class, tape drives needed and priority
of a job. By increasing the priority, a job can be moved from ready queue to
the active queue
XUPD,JOB=JOBNAME
--------------- CA-7 QUEUE MAINTENANCE - CPU JOB ATTRIBUTES -----------------
JOB: G1OLAFQD CA-7#: 8515 MCNT: 001 QUEUE: REQ
---------SCHEDULING----------------- ------MANUAL REQUIREMENTS-------
DEADLINE TIME.... 07088 1111 JOB HELD....................……………………. N
DUE-OUT TIME..... 07088 1120 MANUAL VERIFICATION REQUIRED.. N
SUBMIT TIME...... 07088 1110 JCL OVERRIDES REQUIRED......………..N
MAINID........... SY1
----------RESTART----------------------- ------------- -----------PROMPTING------------
GENERATE CA-11 STEP....... .….N ELIGIBLE FOR PROMPTS.………. N
FORMAT CA-11 CMT.......... ……N PROMPT ACKNOWLEDGED..…... N
RETAIN JCL IN PRRN QUEUE.. N LTERM FOR MESSAGES..………. APC
------------------------------------------------RESOURCES----------------------------------------------------------
JOB CLASS..........…………... A JOB PRIORITY.......... 100
ELAPSED TIME (HHMM)..… 0004 TAPE DRIVES OF TYPE1…….. 000
CPU TIME (MMMSS)...……... 00004 TAPE DRIVES OF TYPE2……... 000
Note:
 Positioning the cursor at the appropriate field and entering a new value can
modify any of the job characteristics appearing on the screen
 Updates are for one run only.
 They do not change information in the CA-7 database
ACTIVE QUEUE
CHECKING JOBS IN SPOOL:
Go to TSO session of the particular Lpar in which the job is running, there we will come
to ISPF (Interactive System Productivity Facility) menu where we have to give the option
Q(QUEUE),in the command prompt. It takes to a SDSF PRIMARY OPTION MENU
from which we can move to all the job queues i.e,active,input,output,held job queues.
For active jobs: Give DA in command Prompt
To check the status of jobs: Give ST to check the status of the job
To check the jobs in spool go to the active jobs,where we can found the jobs.
WHY THE JOB WILL RUN FOR MORE TIME:
Checks the job at what time it started and compare it with the elapsed time.
Check the log of the job to find out at what time it will complete.
By these we can get whether a job is running late or not.
Reasons why the jobs takes more time:
1. The job may be using the dataset, which is in exclusive access with other jobs.
2. The job may be waiting for a region to come up so that it can process files.
3. The job may be waiting for a tape drive, tapes.
ST, DA AND INITIATORS
ST:
In SDSF Panel, ST gives the status of the job whether it is active, held or in print
state.
DA:
In SDSF Panel, DA gives the jobs that are in active queue.
CHECKING LOGS FOR THE COMPLETED JOBS

(LRLOG command and Different parameters of LRLOG command)
LRLOG Command:
Use the LRLOG command to list information from the CA-7 run log. The run log
contains
the information on certain events which occur during CA-7 processing. These
events include job and network completions and exception events such as restarts, force
completes, and cancels.
The run log maintains data for the previous n number of days. The default is to retain 5
days of run log data. That is the current date, up to the moment, and the four previous
calendar days.
Syntax:
LRLOG, JOB=JOBNAME,DATE=*
LPRRN COMMAND:
LPRRN command to review the last run of a job. The information is obtained from the
prior-run queue. The LIST=ALL parameter is optional and provides all data relative to
the queue
DIFFERENCE BETWEEN LRLOG AND LPRRN:
Use the LPRRN command to list job information from the prior-run queue. The
Prior-run queue contains information about the last successful completion of each job.
Parameters allow the user to indicate which job or group of jobs is desired, what
information
is to be reviewed, and the sequence of the displayed data.
LPRRN command to review the last run of a job. The information is obtained from the
prior-run queue. The LIST=ALL parameter is optional and provides all data relative to
the queue.
The LRLOG command to list information from the CA-7 run log. The run log
Contains the information on certain events which occur during CA-7 processing. These
Events include job and network completions and exception events such as restarts,
Force completes, and cancels.
Note:Lprrn will not show the log of the instance if it is cancelled, it will show only
the successful runs of the job where as Lrlog will show the records of the job even if
it is cancelled for the day
ESCALATION PROCEDURES
 The Operator will place a call to the primary on-call person listed in APC or
GEMS. On-call personnel should insure they have the appropriate authority to
perform their job duties.
 Operations will not log on to any system with an on-call person's ID to resolve
a problem.
 Abends are escalated to the Applications on-call person when any of the
following conditions occur.
a. The restart instructions specify to contact the on-call person.
b. The restart instructions contain conflicting information.
c. For all abends except, SB37 space problems, hardware problems, and
contention problems, if restart instructions are provided. Some restart instructions
state to contact the on-call person even for these types of abends. Always follow
the customer provided restart instructions.
d. An abended job has been restarted twice and abends a third time. This includes
jobs restarted due to SB37 space, hardware, and contention problems.
 When escalating to correct an application problem, the procedure is as follows.

a. Page the primary on call listed in APC or GEMS.
b. If the primary on call does not call back within 15 minutes, call the primary
listed in APC or GEMS.
c. If unable to reach primary on call at home, page backup on call listed in APC or
GEMS.
d. If the backup on call does not call back within 15 minutes, call the backup
listed in APC or GEMS.
e. If unable to reach backup on call at home, page the Manager listed in APC or
GEMS.
Inform the TL or DM that the job has been down for 30 minutes and no
contact has been made.
f. If the Manager does not call back within 15 minutes, call the Manager listed in
APC or GEMS.
g. If unable to reach the Manager, page the DPE for the affected business.
I. If the DPE does not call back within 15 minutes, page the DPE's Manager listed
in APC or GEMS.
All timelines pertaining to the escalation of a problem must reside in the

problem ticket.
RESTART PANEL IN XQM PANEL
The below diagram will show the restart panel which will be used for restarting a job.
------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS -----------
JOB: VPEARD11 CODE: U0999 LAST-STEP: D140#160 MCNT: 001

CA-7#: 4049 JES#: 10808 NODE-NAME: LOCAL
REASON:
-- -- RESUBMIT FOR PRODUCTION
-- -- FORCE COMPLETE
-- -- CA-11 RESTART/RERUN PSEUDO: NO
START: ARDLY1S1.D140#160 END:
CC: BYPGDG: USAGE: LRTCD: =0
CMT STATUS: CMT SHOWS JOB IS SET FOR RESTART
-- -- SET PARM DATA FOR RMS AND RESUBMIT

PARM:
-- -- DO NOT INSERT RMS PROC BUT RESUBMIT

MESSAGE: 'X' THE DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE
‘RESUBMIT FOR PRODUCTION’= This function will re-run the job from the top
without using CA-11
‘FORCE COMPLETE’= this function will clear the CMT (Catalog Management Table)
so future first runs of the job will not attempt to use the restart information. It also
considers the job complete and will post the next job in the cycle.
‘CA-11 RESTART/RERUN’= This function will attempt a CA-11 restart. This will be
the
Start - Starting step JOBSTEP.PROCSTEP
End - Ending step JOBSTEP.PROCSTEP
(used if you wish to end the job before the actual end in the JCL)
CC - Indicates an optional CA-11 condition code within the range of 0-0495 to be
set by the RMS step.
BYPGDG - A value of ‘Y’ means that CA-11 will bypass / skip GDG
restart logic and will not reset PGENS.
USAGE - Optional 1 character code
LRTCD - Highest return code from the previous run / abended - the value
can be reset if needed.
‘SET PARM DATA FOR
RMS AND RESUBMIT’= This function will rerun the job without using CA-11
but the job will be set to use CA-11 if desired if the job abends
again.
‘DO NOT INSERT RMS
PROC BUT RESUBMIT’= To rerun a job set to restart using CA-11 without
using CA-11. Future abends will have to be rerun because the RMS step has been
omitted.
INTRODUCTION ABOUT CA-11

CA-11 is an Automated Rerun and Tracking System. It can be used as an effective
management tool in a production environment. CA-11 is designed to perform as a Run
Handler, and as a Job Tracking System or a combination of both.
 RUN HANDLER
The Run Handler provides the means for automatically handling all MVS catalog
maintenance, dataset maintenance, and GDG bias adjustments for job reruns and
restarts
 JOB TRACKING SYSTEM
The Tracking System captures job execution data, permitting you to analyze the
impact of reruns on personnel and resources. The Tracking System provides for
retention of history data in the Job Execution History File.
These are two methods that can be used to implement CA-11 into your production jobs.
1. When production jobs are submitted by CA-7 a job scheduling system you have
the option to have the CA-11 step inserted into the job’s jcl.
2. The other method is to manually insert the CA-11 step as the first step in the
JCL.
Example:
//STEP1 EXEC PROC=CL720RMS,PARM=P
• CA–11 is activated only when the job get the CPU.

• CA-11 will create a CMT (CATALOG MANAGEMENT TABLE).
• Rules:
• Job should be defined to CA-7.
• Job should be defined to CA-11.
• We need to specify CA-7 that CA-11 tracking is on
• When checked in spool will find the step insert@RMS above all the steps of
the jcl, inserted by CA-11
• INSERT-RMS would be set to Y (Insert-rms:Y)
if CA-11 tracking is on for the job in the job definition panel.
• If the User wants to run the job till certain steps then you need to give the step
name in the field “START:” where the Job should begin and give the step name
in the field “END: “ where the Job should end the processing.

START: ARDLY1S1.D140#160 END:
• “LRTCD:” has to be overridden if there is condition code stated in a

particular step of the JCL and the User wants you to restart from that step
then you need to give that which satisfies the condition code.
E.g.:-
If a job abended at step 4 and we want to restart the job from step 6.Then the
restart step should be changed to 6, and LRTCD should be LRTCD: step 4 = 0.So that the
return code of step 4 would be changed to 0 (success), so that all the other steps from step
6 will run, otherwise all the steps after step 4 will also be flushed.
To check whether the step is restartable or not,we need to enter CA11 by using the
ARTS command.
LSTP Command in CA-11:
LSTP, jobname [,startstep] [,end step]

• Used to inquire on the steps within a specific job and display their restart status
in the CMT.
Used to inquire on the steps within a specific job and display their restart status in the
CMT
The below screen shot will show the CMT table.
STEP# PROCSTEP STEPNAME RESTARTABLE RTCD RTCD CHECKS TO RMS STEP
001 JSTEP001 YES 0000

002 JSTEP005 YES 0000
003 JSTEP006 YES 0000
004 JSTEP010 PSTEP010 YES 0000
005 JSTEP015 YES 0000
006 JSTEP018 YES 0003
007 JSTEP020 STEP010 YES NOEX
008 JSTEP020 STEP020 NO - CA-11 NOEX
009 JSTEP030 STEP010 YES 0000
010 JSTEP030 STEP020 NO - CA-11 0000
011 JSTEP040 STEP010 YES 0008
If CA-11 is available to assist with a restart, the screen returned is similar to this.
CA-11 Installed
------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS ------------

JOB: D463XX33 CODE: JCLERR LAST-STEP: MCNT: 331
REASON:
-- -- RESUBMITFOR PRODUCTION
-- -- CA-11 RESTART/RERUN PSEUDO:
START: END:
CC: BYPGDG: USAGE: LRTCD: = 3
-- -- SETPARM DATA FOR RMS AND RESUBMIT
PARM:
-- -- DO NOTINSERTRMS PROC BUTRESUBMIT
PROGRAM: QM53 MSG-INDX: 33 -- QM.4-X -- YY.DDD / HH:MM:SS
CA-11 Not Installed: If CA-11 is not installed, the following is an example of the
screen.

REASON:
-- -- RESUBMITFOR PRODUCTION
PROGRAM: QM53 MSG-INDX: 33 -- QM.4-X -- YY.DDD / HH:MM:SS
PROCEDURE TO BE FOLLOWED TO RESTART A JOB WITH OUT USING CA-11
Restarting a Job without CA-11 can be done when the job is not restartable
through CA-11 by specifying RESTART CARD in the JCL of the job
 Type XQ,JOB=<abended jobname> to enter into the XQM Panel

 Type E beside the job to edit the JCL of the job and hit enter.
 Specify RESTART=PROCSTEP.STEPNAME in the Job card
 Tab to the upper left corner of the screen & type SR(to Save & Replace the
changes which we made to the JCL)
 Type F beside the Jobname & hit enter
 Specify the reason (i.e r/r-rerun) in the reason field
 Tab to RESUBMIT FOR PRODUCTION option & type X beside it.
SR UPPER NOFILL XSEQ (NONUM) I(010)

00010 //G1OLHRBR JOB (CORE-APPARCP,008),'G1OLHRBR',
00020 // CLASS=B,MSGCLASS=J,REGION=0M,RESTART=G1OLHRBR.STEP010
00030 //*******************************************************************
00040 //*UCC7RESTART UCC7
00050 //*JCLLIB=G2IU00AP.CA7.JCL
00060 //STEP0001 EXEC PGM=IEFBR14,
00070 // REGION=0K
DIFFERENT PROBLEMS FACED IF WE CANCEL A JOB INSTEAD OF FORCE

COMPLETING A JOB
Cancellation of a job does not automatically satisfy the requirements of other jobs that are
dependent upon the canceled job and job triggering DOES NOT occur.
Force complete flags the job as a normal completion and normal processing is performed
Note: Cancellation of a job in CA7's active queue does not cause termination of the
jobs execution. The execution must be terminated from an OS system console.
In addition, before canceling a job from the CA7 Request queue you must resolve any
issues regarding successor jobs that are dependent upon the job that is being canceled.
Use the LJOB,JOB=JOBNAME,LIST=DEPJ command to determine any other jobs
that are dependent upon the job being cancelled and consult the on-call person for
instructions on what action to take on the job. Also, use the
LJOB,JOB=JOBNAME,LIST=TRIG command to identify jobs that would normally be
triggered by the job being cancelled. Once again, consult the on-call person for
instructions on what action to take on the job.
RCA:
The goal of Problem Management is to minimize the effects of incidents caused by errors
in the IT infrastructure and to prevent their recurrence.
Problem Management enables you to identify the underlying reason for one or more
incidents, implement workarounds, identify known errors, and provide permanent
solutions.
Root Cause Analysis (RCA) provides the ability to distinguish the difference between the
symptom of a problem and the root cause of a problem.
A Root Cause Analysis is required for:

Priority (Severity) '1' incidents and IBM responsibility
Priority (Severity) '2' incidents and IBM responsibility, where the outage was thirty
minutes or greater
All failed changes
When requested by IBM management or the customer, via the Delivery Project Executive
(DPE). This is a manual process.
ABOUT CA-11
CMT (CATALOG MANAGEMENT TABLE)
CMT keeps track of the stepwise details of an executed job & it also displays the
return code for each & every step of the job
DIFFERENT TYPES OF PROCESSINGS--PRODUCTION RUN -RESTART RUN
PRODUCTION RUN:
Production Run is an initial execution of a job. By this Production run, the
abended job will run from the first step. It is a CA-7 restart and it just submits the job
from top
 Type XQ,JOB=<abended jobname> to enter into the XQM Panel

 Type F beside the job and hit enter.
 Specify the reason(i.e., r/r-rerun) and type X in front of RESUBMIT FOR
PRODUCTION.
JOB: G1OLCHEK CODE: LAST-STEP: MCNT: 001

CA-7#: 4187 JES#: *NA* NODE-NAME: LOCAL
REASON: r/r as per George...sasi
-- x -- RESUBMIT FOR PRODUCTION

START: END:
CMT STATUS: CMT SHOWS JOB IS SET FOR PRODUCTION

PARM:

*WARNING* - RESTART/RERUN COULD SCRATCH GOOD DATASETS
[Note: This Production Run will create a new CMT table for the Job]
RESTART RUN:
Restart run is an extension or continuation of a production run. By Restart Run,

the job will be restarted from the first step (i.e.,) it will attempt a CA-11 restart & it will
refer to the existing CMT Table
JOB: G1OLHRBR CODE: LAST-STEP: MCNT: 001
REASON: r/r as per George..sasi
-- x -- CA-11 RESTART/RERUN PSEUDO: NO

START: END:
CMT STATUS: CMT SHOWS JOB IS SET FOR PRODUCTION

PARM:

 Type XQ,JOB=<abended jobname> to enter into the XQM Panel

 Type F beside the job and hit enter.
 Specify the reason (i.e., r/r-rerun) in the reason field
 Tab to CA-11 RESTART/RERUN & Type x beside it & Hit enter
ARTS(AUTOMATED RECOVERY TRACKING SYSTEM)
ARTS is a tool, which is mainly used to check whether a job is restartable or not.
LSTP Command in CA-11: It is Used to inquire on the steps within a specific job and
display their restart status in the CMT
LSTP, <jobname>
LSTP,G2TR3VP1
CA-11 ONLINE - JOB STEP INQUIRY FOR JOB G2TR3VP1
JOB IS RESTARTABLE.
JOB IS NOT SET FOR RESTART.
STEP LAST HIGH CONDITION CODE

STEP# PROCSTEP STEPNAME RESTARTABLE RTCD RTCD CHECKS TO RMS STEP
001 SNTP0010 UTIL001 YES 0000

002 SNTP0010 SNTP0010 YES 0000
003 SNTP0010 FINDGDG YES 0000
004 SNTP0010 SNTP0033 YES 0000
--- ONLINE STEP INQUIRY ENDED ---
RESTARTING A JOB WITH AND WITHOUT CA-11
RESTARTING A JOB WITH CA-11:

Restarting a Job with CA-11 can be done when the job is restartable through
CA-11. When Restarting a job through CA-11, it will refer to the existing CMT table &
track the job steps from the abended step

 Type F beside the job and hit enter.
 Specify the reason(i.e., r/r-rerun) in the reason field
 Tab to the Start field & enter the abended step as PROCSTEP.STEPNAME (or)
STEPNAME
 Tab to CA-11 RESTART/RERUN & Type x beside it & Hit enter
------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS ------
JOB: G1OLHRBR CODE:0008 LAST-STEP:STEP009 MCNT: 002
REASON: R/R as per Ganesh…sasi
-- X -- CA-11 RESTART/RERUN PSEUDO: NO

START: G1OLHRBR.STEP010 END:
CC: BYPGDG: USAGE: LRTCD: = 0
Note:
 If we are overriding any data sets on the restart, then Tab to the BYPGDG
field and enter: Y
A value of ‘Y’ means that CA-11 will bypass / skip GDG restart logic]
 Sometimes the restart will be done from the next step of the abended step
as per the requestor.
So at that time, Abended step has to be marked as success to CA-11, by
specifying in the LRTCD field as, LRTCD: <Abended step> = 00
Otherwise job will get abended / all steps will get flushed off immediately
RESTARTING A JOB WITHOUT CA-11(USING RESTART CARD IN JCL):
Restarting a Job without CA-11 can be done when the job is not restartable
through CA-11 by specifying RESTART CARD in the JCL of the job

 Type E beside the job to edit the JCL of the job and hit enter.
 Specify RESTART=PROCSTEP.STEPNAME in the Job card
 Tab to the upper left corner of the screen & type SR(to Save & Replace the
changes which we made to the JCL)
 Type F beside the Jobname & hit enter
 Specify the reason (i.e r/r-rerun) in the reason field
 Tab to RESUBMIT FOR PRODUCTION option & type X beside it.
SR UPPER NOFILL XSEQ (NONUM) I(010)

00010 //G1OLHRBR JOB (CORE-APPARCP,008),'G1OLHRBR',
00020 // CLASS=B,MSGCLASS=J,REGION=0M,RESTART=G1OLHRBR.STEP010
00030 //*******************************************************************
00040 //*UCC7RESTART UCC7
00050 //*JCLLIB=G2IU00AP.CA7.JCL
00060 //STEP0001 EXEC PGM=IEFBR14,
OVERRIDING THE JCL OF THE JOB
FOR THE JOB IN THE REQUEST QUEUE (QJCL):
The QJCL command is used when a request is made to use a different set of driver JCL
than the original . The way it is used in our shop is that the job has to be in the Request
queue or the Restart queue. After the job completes , the changed JCL will no longer be
connected. This is a one time process.
1. At command line enter: JCL (displays the CA-7 JCL LIBRARY

MAINTENANCE screen), and
press Enter.
2. Position the cursor at the FUNCTION: field, enter: fe (fetch edit).
3. Tab to the MEMBER: field and enter: member name (member name of JCL to
be pulled in).
4. Tab to the DSN: field and enter: dataset name (DSN where JCL will be pulled
from), and
press Enter.
5. The new JCL will be displayed on the screen. At the top left corner enter: save
(saves JCL
the to the workspace) and press Enter.
6. This will put you back to the CA-7 JCL LIBRARY MAINTENANCE screen.
Position your
cursor at the CA7 command line, enter: QJCL and press Enter.
7. The CA-7 QUEUE MAINTENANCE - QUEUED JCL screen will be
displayed.
8. In the FUNCTION: field, enter: repl (replace), tab to the JOB: field and enter:
jobname
(job whose JCL is being replaced), and press Enter.
9. The message: "REPL FUNCTION SUCCESSFUL FOR JOB xxxxxxxx (nnnn) "
will be
displayed.
10. Position the cursor in the FUNCTION: field and enter: clear (clear JCL
workspace) and press
Enter
Note :Try to put the screen shots for Jcl and Qjcl if possible
FOR THE JOB NOT IN THE REQUEST QUEUE(SAVING IT TO OVERRIDE

LIBRARY)
If the job is not in the queue first fetch the job the job from user library(187) and
need to save into override library (254).
 Type JCL(In the command line)
 Type FETCH(It will take a copy a job from user library)
 Give job name as a member name
 You will get a message ”FETCH FUCTION IS SUCESSFUL”
 Type SAVE((It will save into override library)

 Give job name as member name..
 You will get a message “SAVE FUNCTION SUCESSFUL”
 Then you have to give the following command:-
 DEMANDH, JOB=XXXXXXX,SCHID=001(It will Demand the job in hold

Where as XXXXXX is the job name)
 Note:
 (Schid id –You need to confirm the programmer)
 Give XQ, JOB=XXXXXX
 Put X infront of the job name
 Give XQM,JOB=XXXXX
 Put X infront of - Re-submit the Job for production
 Give LQ,JOB=XXXXX(Job name)
PUTTING A JOB ON HOLD
ADDING A HOLD FOR A JOB WHICH IS IN THE REQUEST QUEUE:
To hold a job that is already in the CA7 Request queue:

1. Enter: XQJ (list jobs in CA7 request queue in job name sequence) and press
Enter.
2. Tab down to the left side of the job which is to be held and enter: H (hold) and
press Enter.
ADDING A HOLD FOR A JOB WHICH IS NOT IN THE REQUEST QUEUE

ADDRQ COMMAND:-
Adding a hold for a job which is not in the queue:
* By way of using DB3.6 Panel.
* Go to DB3.6 Panel.
* Give the job name and Text
*Type ‘O’ in NEXT-RUN field if you want to add user requirement for next
run
only
 Type UPD in the function field.
ONE TIME REQUEST(REQUEST FOR SERVICE)
RUNNING A JOB WITHOUT TRIGGERS (RUNH)
To run a job without triggers, we have to specify the Function field in

CA-7 LIBRARY MAINTENANCE screen as RUN/RUNH.
[Note: RUN/RUNH commands(note, Here this term specifies the commands &
not the function) can be used but usually we wont use this commands to run the
job without triggers]
Below procedures has to be followed to run a job without triggers.
 Type JCL at the command line.

 Type Fetch in the Function field
 Give Job name at the Member name
 Give 187 as JCL ID and hit Enter. This will fetch the job from the User library
 Give Function as RUNH and hit Enter[This will place the job into the request
queue with Hold]
[Note: Running a job using RUN/RUNH(Function in ca-7 Library Maintenance

screen) will neither trigger the batch nor it will satisfy any requirements]
Alternate Method:
By specifying SET=NTR in DEMAND/DEMANDH command the job can be run
without triggers.
DEMANDH, JOB=JOBNAME,SCHID=XXX,SET=NTR
RUNNING A JOB FROM THE LIBRARY OTHER THAN PRODUCTION

LIBRARY (USERLIB, OVERLIB)
RUNNING A JOB FROM USERLIB:
Below are the procedures to be followed to run the job from userlib (without triggers)
 Type JCL as a topline command & hit enter

 Type FETCH in the function field of CA-7 LIBRARY MAINTENANCE
Screen
 Tab to the Member field & enter the JOBNAME
 Tab to JCL-ID field & enter 187(it will fetch the Jcl of the job from user
library) & Hit enter
 “FETCH FUNCTION SUCCESSFUL “ message will be displayed at the bottom
of the screen
----------------------- CA-7 JCL LIBRARY MAINTENANCE ------------------------

FUNCTION: FETCH (APPEND,CLEAR,DELETE,EDIT,FE,FETCH,
RENAME,REPL,RUN,RUNH,SAVE)
MEMBER: G2SS64PW NEWNAME/OPTION:
DSN: SYSD.CA7.USERLIB JCL-ID: 187

VOLSER: GEP045 JCLLIB:
ACTIVE SIZE: 0000
PROGRAM: SM50 MSG-INDX: 00 -- DB.7 -- 07.090 / 07:42:56

MESSAGE: FETCH FUNTION SUCCESSFUL
 Now, Tab to the function field & type RUN/RUNH without changing the
contents of other fields & press Enter(it will place the job in request queue
with Hold)
 “RUNH FUNCTION SUCCESSFUL, <Jobname>(ca7-id) ADDED TO THE REQ 'Q' “
message will be displayed
 Type XQ,JOB=<Jobname> to enter into the XQM panel
 Check for the Main-id & release the job from Hold(if the function
specified is RUNH) to run.
FUNCTION: RUNH (APPEND,CLEAR,DELETE,EDIT,FE,FETCH,
DSN: SYSD.CA7.USERLIB JCL-ID: 187

ACTIVE SIZE: 0000

MESSAGE: RUNH FUNTION SUCCESSFUL
G2SS64PW(4652) ADDED TO THE REQ ‘Q’ “
RUNNING A JOB FROM OVERLIB:
Running a Job from Override Library means modifying the regular JCL(Master
JCL of the job). It is a temporary action (i.e., ) it is applicable for the next run of the job
alone.
 Type JCL as a topline command & hit enter
 Type FETCH in the function field of CA-7 LIBRARY MAINTENANCE
Screen
 Tab to the Member field & enter the JOBNAME
 Tab to the DSN field & enter the Dataset Name from where the JCL of
the job has to be fetched (else use /Display,st=JCL command to have the
Dataset Names & its related JCL Ids) & Hit Enter
 “FETCH FUNCTION SUCCESSFUL “ message will be displayed at the bottom
of the screen

FUNCTION: FETCH (APPEND,CLEAR,DELETE,EDIT,FE,FETCH,
DSN: G2IU00AP.CA7.JCLDS JCL-ID: 002

ACTIVE SIZE: 0000

MESSAGE: FETCH FUNTION SUCCESSFUL
 Now, tab to the Function field & enter SAVE

 No need to change the JOBNAME in the Member name field
 Tab to the DSN field & erase the Dataset name that is mentioned
 Tab to the JCLID field & type 254(which is a JCLID for override library)
& Hit enter
 “SAVE FUNCTION SUCCESSFUL” message will be displayed at the
bottom of the screen
By doing this, now the next instance of the job will run from Override Library

FUNCTION: SAVE (APPEND,CLEAR,DELETE,EDIT,FE,FETCH,
DSN: G2IU00AP.CA7.OVERRIDE JCL-ID: 254

ACTIVE SIZE: 0000

MESSAGE: SAVE FUNTION SUCCESSFUL
RUNNING A JOB WITH TRIGGERS
(DIFFERENT PARAMETERS OF DEMAND COMMAND)
DEMAND command is used to force immediate scheduling of a job into the

CA-7 request queue. Jobs, which do not have definable processing cycles, can be
scheduled in this manner
To run a job with triggers, we need to use demand command
 DEMAND, JOB=JOB NAME,SCHID=XXX
This will demand the job with the schid with triggers. If there are no
requirements to be posted, job will automatically become active
 DEMANDH,JOB=JOBNAME,SCHID=XXX SET=SKP
This will Demand a job into ca-7 and tells ca-7 to skip the next scheduled
run of this job.
 DEMANDH,JOB=JOBNAME,TYPE=RES,SCHID=XXX
This will demand a job into ca-7 and tells ca-7, this is a restart of the job.
RMS is reset to bring in all DSN generations of the last run.
 DEMANDH,JOB=JOBNAME,SCHID=XXX TIME=HHMM
This will demand a job with submit time requirement

 DEMANDH, JOB=JOBNAME,SCHID=,DATE=-----,TIME=--------
This will demand the job with hold with schid on the given date at a given
time.
We can also use the DEMAND command to demand the job without triggers by using the
command,
 DEMANDH, JOB=JOBNAME,SCHID=XXX,SET=NTR
[Note: Demandh command will place the job into the request queue with hold
requirement. Its always safe to Demand the job with hold. We need to post the
hold requirement manually then only the job will run. Other wise the job will
remain in the request queue with hold]
CHANGE TICKETS & PROBLEM TICKETS
CHANGE TICKETS
Change Tickets are those that are created by the Change Management when there is a
change in the production Environment. Change Tickets will be generated whenever there
is any upgrades/modifications in technology. Mainly During the IPL Maintenance
window, the change tickets will be created. It will contain the complete information of a
change like the requestor name, brief description about the change, impact of changes,
date & time of implementing the change etc.,
PROBLEM TICKETS
Problem tickets are those that are created by the problem management when there is a
recurring incident ticket / an Incident ticket which requires RCA
LATE JOB ANALYSIS
The command for checking the late jobs is LQ, ST=late, list=status,seq=dotm.This will
display all the late jobs with unsatisfied requirements sorted based on due out time.
Tip:
While checking the late jobs, if there are many jobs in the queue, the best way is to give
the first priority to the job which is a predecessor job of many successor jobs that are in
late status. In this way we can escape from analyzing all those successor jobs where the
job which we analyzed is a predecessor job.
Predecessor job and Successor job

Suppose A is a job which is in the queue waiting for the successful completion of B i.e. B
is an internal job of I. In other words, B is the predecessor job of A and A is the Successor
job of B
Why the job shows late:

The status of the job will be changed to late status once the current time crosses the dead
line time or due out time specified in the job.
Dead line Time: This is the time before which the job needs to satisfy all the requirements
and it should start execution. In other words, the job needs to move from the request
queue to ready queue before the deadline time.
Due out Time: This is the time before which the job needs to complete its execution. In
other words the job should be out of CA-7 before the Due out time.
There fore once the current time crosses either the dead line time or the due out time of a
job and the job is still in any of the queues. then the job will be in late status.
Analyzing the Late jobs
Check the job and its requirements by giving the command LQ,job=jobname.
This command will list all the unsatisfied requirements that the job in the request queue is
waiting for.
A job will wait in the request queue because of the following reasons.
1) Submit time Requirement
2) User requirement
3) Internal job requirement
4) Hold Requirements
5) Internal dataset requirement
CASE-1 : SUBMIT TIME REQUIREMENT

Suppose if the job is waiting for a submit time requirement the requirement will
automatically get posted if it crosses that submit time. This is mainly because, the
deadline time is less than the submit time.
CASE-2: USER TIME REQUIREMENT

Check the comments in the user requirements and the job will not run until we manually
post the requirement. Check if any turnover is given for this user requirement. If we
could not analyze why the job is waiting for the user requirement it is always better to
call the analyst or the operator who put the user requirement.
Note: Don’t release the user requirement unless you contact the analyst or a
confirmation from the operator who put that user requirement.
CASE-3: HOLD REQUIREMENT

If the job is waiting for a hold requirement, the job will not run until we release the hold
requirement.
Note: Don’t release the HOLD unless you contact the analyst or a confirmation from the
operator who put that HOLD.
CASE-4: INTERNAL DATASET REQUIREMENT

CA-7 will automatically post the requirement as soon as the dataset is created. If the
dataset is not created, the requirement will not get posted. We need to contact the analyst
before posting the requirement
CASE-5: INTERNAL JOB REQUIREMENT

This Internal job requirement will automatically get posted when the internal job
completes successfully. As we discuss earlier, the predecessor job is the internal job and
the successor job will be the main job. As soon as the Successor job enters into the
request Queue it will check whether its predecessor jobs ran successfully or not based on
the look back time or Lead time defined for that job.
Look back time: Look back time is the time interval where the successor job will look
back from the time it enters the request queue.In this Interval the predecessor job should
start and complete successfully
Check the status of the internal job by giving the command LQ, job=jobname.The
following are the different cases depending on the status of the job.
1) Job in Request Queue

Check why the job is in the request queue and repeat the same process from
Step-1.
2) Job in Active status
The requirement will get posted as soon as the job ran successfully. Check the
elapsed time of the job. If the job is running from a long time and exceeds the
elapsed time, then check why the job is running late.
Go To Q;DA and check whether the job is active or not.
If the exception count keeps on increasing, that means that the job is running fine.
Note: If the job is inactive for a long time, then check whether the job is waiting
for any outstanding reply. If the job is waiting for any outstanding reply we need
to take action immediately.
If the job is waiting for any tape devices, check with tape operations and inform
the same to the analyst.
3) Job not in any of the Queues

If the predecessor job is not in the queue that means that the job may be already
completed or it did not enter into the request queue when the successor job enters into
the queue.
Check whether the internal job is already completed or not by using the LRLOG
command. If you find any log of internal job, then check whether the successor job
ran fine or not. If you did not find the run of successor job that means that the job
might have missed the look back time
If you find any successful instance of successor job after the completion of the
predecessor job that means that the successor job will wait till the next instance of the
predecessor job completes successfully.
We need to know the entry mode of the job by checking the LRLOG command.
The following are the different cases that we need to check depending on the Entry
mode.
a) SSCAN :
Check the schedule of the job by using the command
LSCHD, job=job name, list=cals
Check whether that job has a run on that day or not. If that job has a run on
that day the requirement will get posted as soon as the job runs successfully.
Note: SSCAN Jobs will not be scheduled on US Declared holidays. This is
the time where the job will not come into the queue and the jobs for which this
job is predecessor job will wait in the queue till the next run.
We need to contact the analyst and post the requirement on his suggestion.
b) AUTO :
For an Auto job, we need to know how the job enters into the queue.
Use FRQJOB, job=jobname.This will tell us how the job enters into the queue
and it will also show the job which triggers this predecessor job along with the
CA-7 ID.
Take the ca-7 id of that job and repeat the process from step-1.
Note: If you did not find any job in that batch cycle that triggers the job
then check the first job that starts this batch cycle whether it is scheduled
or not
c) Demand: If the entry mode is a demand mode, that means some one need to
manually demand the job and the requirement will get posted once it ran
successfully.
Note: We will demand the job when the analyst raises an RFS or a GEMS
ticket.
Procedure to check the look back time or lead time
o Give jobconn,job at the command prompt.

o Give job name as successor job name.
o Give Function as list.
o It will display the look back times of all the internal jobs of that job.
If the look back time is 8 hrs.Check the time when the successor job that is
late entered into the queue and look back 8 hrs from that time. That becomes
the interval for that predecessor job. If the predecessor job starts and ends in
that interval then the successor job will not come into the queue with the
predecessor job as the requirement.
The look back time starts from 1 – 98hrs i.e. minimum is 1 hour and
maximum is 98hrs.
0 and 99 are special cases.
99: The requirement will be posted if and only if the predecessor job start and
complete successfully when the successor job is in the request queue.
0: There is no interval. The requirement will be posted if there is a successful run
of a predecessor job and that run is not satisfied by any of the instance of this successor
job.
Step- Lq,job=jobname,st=late
1
Submit time User Reqmt Internal Job Hold Req Internal Dataset
Job in Act
Job in req Q Job not in Req Q
Q
Check the normal
Contact
Run of the job
the analyst
Start From through the lrlog
if there is
Step 1 Get the entry command and
no update
mode by giving contact the
from
lrlog, job= analyst
analyst
job name
The job will get Auto

Check for the
posted job which is in
automatically Use FRQJOB,job=job request queue
once it crosses name that triggers
the submit time this job
Start from step-1
Demand
Check the user
requirement and if you We will demand the job and once job completes the
could not find who has requirement will get posted. We will demand only if
put the user rfs is raised by analyst
requirement please call
the analyst
Jobs Missing Lead
Time
SSCAN job
Check lschd
command to check
schedule
FRJOB & FRQJOB (Difference between FRJOB & FRQJOB)
FRJOB :
Use the FRJOB command to answer the question, "How does this job get into the
system?" It presents a reverse job flow (reverse trigger flow) based upon information
in the database. The purpose is to identify how the target job can be brought into the
active scheduling system. It tracks backward through triggers from the target job to
one or more header jobs. A header job is one which has one or more defined date/time
schedules, or, that has no job/data set/network triggers defined. That is, a job,
network, or data set which starts the trigger flow which eventually results in the target
job being brought into the active scheduling system. FRJOB uses only information in
the CA-7 database.
The FRJOB command is useful when you are creating or modifying the schedules and
triggers for a workload flow. If you need to determine all of the paths that schedules
and/or triggers can take to result in a given job being run, FRJOB can be most helpful.
FRJOB,JOB=G2CZ11P6
FRJOB DATE 02-28-07 PAGE 0001
REVERSE STRUCTURE FOR CA-7 JOBS
HDR LEV# JOB NAME SYSTEM SID TYPE TRIGGERS /DSNBR /SCHEDULED
--- G2CZ11P6............ SALES 000
-001 G2CZ06GD.......... SALES 000 JOB G2CZ11P6
-002 G2CZ05PC........ SALES 000 JOB G2CZ06GD
-003 G2CZ04PK...... SALES 000 JOB G2CZ05PC
-004 G2CZ02PN.... SALES 000 JOB G2CZ04PK
-005 G2RT02PD.. SALES 000 JOB G2CZ02PN
-006 G2RT01PD PURCH 000 JOB G2RT02PD
-007 CORE CORE 000 JOB G2RT01PD
**** -008 G2RC00P MECH 000 JOB CORE
SFC1-00 REQUEST COMPLETED AT 17:54:32 ON 07.059
FRQJOB :
The FRQJOB command is useful to answer the question, "How does this job get into
the system today?" It presents a reverse job flow (reverse trigger flow) based on
information in the database. It also checks the status queues (request, ready, and
active) for the presence of each job in the structure as it is being built.
The purpose is to identify how the target job is brought into the active scheduling
system taking into account jobs that are already in the queues. It tracks backward
through triggers from the target job to one or more header jobs. A header job is one
which is already in the request, ready, or active queue or one which has one or more
defined date/time schedules, or one which has no job/data set/network triggers defined.
Main Difference :
The difference between the FRQJOB command and FRJOB is that a check is made in
the status queues for each job present in the structure. If it is found in one of the
queues, that job is considered a header job even though it may have been triggered by
something else. This identifies the shortest possible control path that results in execution
of the target job.
FSTRUC (Forward Structure)
Use this command to produce a report displaying an entire CPU job flow structure
with the starting and ending times. The principal emphasis is on the job flow structure
and the elapsed time of each job. The start time of the first job can be any arbitrary
time. Only the database is used for this forecast.
FSTRUC,JOB=G2CZ11P6
FSTRUC DATE 02-28-07 PAGE 0001
NETWORK STRUCTURE FOR CA-7 JOBS
START TIME : 02-28-07 AT 1758 HRS
LEV# JOB NAME SYS START DTTM END DTTM TRIGGERING JOB/DSN/SID
--- G2CZ11P6............ SALES 07059/1758 07059/1805 :001
001 G1SGCEDR.......... FINSYS1 07059/1815 07059/1818 G2CZ11P6 :001
001 G2CT2APD.......... ACH 07059/1815 07059/1819 G2CZ11P6 :001
002 G2CB2APD........ PAYMENTS 07059/1829 07059/1829 G2CT2APD :001
001 G2CZ11A1.......... SALES 07059/1815 07059/1823 G2CZ11P6 :001
SFC1-00 REQUEST COMPLETED AT 17:58:13 ON 07.059
IPL
IPL(Initial Program Load) is the process of loading the Operating system of a

mainframe into the computer's main memory. IPL is the mainframe equivalent of booting
or rebooting a personal computer
Procedure to stop the barriers in CA-7
We can get the cpu name by giving the command /display, cpu=all
This will display the cpu name and the main-id of the particular network
/DISPLAY,CPU=ALL
*** CPU DISPLAY ***

DDNAME BARRIER SUBMIT-COUNT MAINID
UCC7SUB3 0150 0001 SY0

SY*
UCC7SUB1 0150 0003 SY1
UCC7SUB2 0150 0001 SY2
 By giving the cpu name of the particular system and using the assign command
/ASSIGN,CPU=UCC7SUB1,BARR=n(when IPL n should be O)
 Note: Barrier acts as a mediator between ca7 and MVS.The number of jobs
submitted to spool from ca-7 is controlled by barrier. here n number of jobs will be
submitted to mvs through CA-7.
 At the time of IPL we will make it as 0 so that no jobs that are defined to sys4 will be
submitted to MVS.
 All the jobs will hang up in the ready queue and now we can say that the batch is
stopped
Purging the Initiators:
Before doing the ipl we need to Check whether there are any jobs in the active queue of
CA-7 Make sure that there are no jobs running on CA-7.
Purging the initiators using the $PI command..:
Documents needed for IPL.
 Time line sheet (will get through mail)

 Change number for the IPL.
 We will get a timeline sheet stating the actions and the team which will perform the
specific action at the time of ipl.
 The change number is given in the sheet and we need to update that particular ticket
in GEMS.
 Shutdown document for the system in QMX
 HMC Procedure
 IPL Document
Before 45 min of the IPL time, we need to give a warm transfer regarding the IPL to the
following three groups.
1) NCC i.e. Network group – 800-362-2792
2) Tape Media 770-999-6187/6147
3) IBM Helpdesk (800-525-0587)
1. 1 hour Prior To The Shutdown : Check Focal Point and PROC-OPS

2. proc-ops is one which will help to issue the commands to the master console from the
focal point.
3. We need to Verify that whether we can establish a session to the Procops Operator
Console by entering "ISQTCC NRSS4 OC QUIET".
4. This will take you to the proc ops screen which moves us to sys4 where we can enter the
commands directly on sys4.This is a master console for sys4.
5. If we are not able to connect to sys4 there will be a backup console.
ISQTCC @NRSS4 OC QUIET
(Alternate console for all consoles : @console name)
NOTE : ANY PROBLEMS WITH PROCOPS, CONTACT THE AUTOMATION

TECHNICAL SUPPORT. CONTACT LIST CAN BE FOUND IN ONE CONTACT
UNDER GE CAPITAL "AUTOMATION SUPPORT."
Before 15 mins of Shutdown

 Open the bridge before 15 min of the IPL.
 Bridge details are given in the Time line Sheet.
 Before 15mins of the IPL we need to send a message by this command from the TSO.
 Notify any TSO users of system shutdown approx. 15 minutes before shutdown.
Enter: NRSS4 TSOMSG 15 (if the system is Sys4)
 Check whether there are any jobs in the active queue of CA-7.Make sure that there
are no jobs running on CA-7
 Drain all the initiators on sys4 by giving the command $pi
 For sys4, We need to release initiators of two classes 7 & 8 to allow the jobs related to
journals. these are not CA-7 job.
 Now Inform on the bridge that we stopped the batch and drained the initiators except
class 7 and class 8.
 Follow the instructions as per the shut down document of the respective system and
the bridge.
Post IPL Process:
We need to ask on the bridge whether we can start the regions or not.
 Once we get confirmation we can start the regions.
we need to give reply YES for this message which will bring up all the regions.
 Note : we replied yes on this message which will bring up all the regions
*nn DO YOU WANT AUTOMATIC STARTUP OF ALL ONLINE REGIONS
REPLY (YES - PARTIAL – NO)
 And check *we can check whether all the regions are coming up on time by
giving >ophours
 If you find any regions down that should not be, you need to inform it on the
bridge.
 Start the Initiators once the regions are up By the command $SI when we get
good output from ophours
 Start the Barriers in CA-7 by using the command

/ASSIGN,CPU=UCC7SUB1,BARR=150
 Check whether the jobs are running or not in the active queue.
CALLING PROCEDURES/ESCALATION PROCEDURES
How to use Avaya Phones:
To Log in to Phone: *88 + Login id + Password
To Logout: #89
(1) Making an Outside Call :
 Login to the phone
 Dial 91 followed by the US telephone number with ISD Code (001)

for e.g. if the US Number is 001- 303 262 5697 (001 is the ISD Code)
Dial 91+ 001+ 303 262 5697#
(2) Different types of Paging :
Two types of paging is available.
 Numeric paging:-
This type of paging we need to enter the call back number
(888-266-2909)
Note
 Text paging:-
Using ONE CONTACT paging tool.(Login to

www.onecontact.ibm.com).
(3) Protocol to be followed while leaving a voice mail:

 Identify your self with your first name
 Mention the Job name followed by Lpar name
 Mention the ticket number and the LPAR name if it is regarding the console
messages
 Give the call back number for them to give any instructions
For Example: This is kishore from IBM production ctrl, this is regarding the job job name
on Lparname is abended with r/c at step stepname. Please call back
888-266-2909 for further instructions.
INFORMATION TO BE GIVEN WHILE CONTACTING THE ANALYST
 Identify yourself by your first name.

 Name of the system and the job name
 Abended step with the return code
PROCEDURE FOR CONTACTING THE BACKUPS:
1) If no response from the primary After 10mins we need contact the back ups
2) Leave the voice mail to the primary informing that you are going to contact the
backup.
3) Then contact the back up.
ON CALL LIST: CASS CASS JOB/TSK: G2CS42PD TYPE: JCL

DESCRPT: RUNS WITH G2CS41PD AFTER G2CS4BPD FOR LETTERS
CONTACT: E - RESTART PER INSTRUCTIONS; CALL ONLY IF PBLM PERSISTS
PRIMARY PAGER/PIN: 203-767-5735 SECONDARY: 203-650-8394
ON CALL SPECIAL INSTRUCTIONS:
FROM SUN-FRI BETWEEN 11:30 PM EST TO 8:00 AM EST
CALL *INDIA 011-91-22-27610478/011-91-2761-9602 /
011-91-22-27611090 EXTN 1049/DC: 8901-4408'
PRIMARY PERSON'S SPECIAL INSTRUCTIONS:
CHANGE TICKETS & PROBLEM TICKETS
CHANGE TICKETS
Change Tickets are those that are created by the Change Management when there is a
change in the production Environment. Change Tickets will be generated whenever there
is any upgrades/modifications in technology. Mainly During the IPL Maintenance
window, the change tickets will be created. It will contain the complete information of a
change like the requestor name, brief description about the change, impact of changes,
date & time of implementing the change etc.,
PROBLEM TICKETS
Problem tickets are those that are created by the problem management when there is a
recurring incident ticket / an Incident ticket which requires RCA
FJOB COMMAND:
FJOB command is used to Forecasts the Jobs by job name that do presently
not exist in the Queue
(1) FJOB,FROM=(MMDDYY,HHMM),SPAN=time in hrs,JOB=<jobname>
FJOB,FROM=(032807,1101),SPAN=1,JOB=G1OL*
FJOB DATE 03-28-07 PAGE 0001
FORECAST FOR CA-7 JOBS
PERIOD : 03-28-07 AT 1101 HRS TO 03-28-07 AT 1201 HRS
START DTTM END DTTM JOB SYS SCHED# SID TRIGGERING JOB/DSN RQMT
07087/1116 07087/1120 G1OLAFQD APPOS SJ000838 012
07087/1116 07087/1120 G1OLHRBR APPS SJ001296 011
07087/1135 07087/1139 G1OLQRSP APPS LEV001 004 G1OLQMN1
07087/1210 07087/1210 G1OLCHKB APPS SJ000917 002 NOEX
2) FJOB,SPAN=2,JOB=<jobname>
FJOB,SPAN=1,JOB=G1OL*
FJOB DATE 03-28-07 PAGE 0001
FORECAST FOR CA-7 JOBS
07087/0003 07087/0007 G1OLDACT APPS SJ000774 001
07087/0016 07087/0020 G1OLAFQD APPOS SJ000838 001
07087/0030 07087/0037 G1OLPOSD APPS LEV001 001 G1OLAFQD
07087/0039 07087/0040 G1OLDUPD DRAPPS SJ001396 002

[Note: Either TO or SPAN is required. If TO is specified, SPAN must be
omitted. The FROM date and time are used as the start time for the job
unless omitted, in which case current date and time are used]
FQJOB COMMAND
FQJOB command forecasts Jobs by job names including those in the CA-7
queues Request, Ready and Active queues.
FQJOB,TO=(032807,1301),JOB=G1OL*
FQJOB DATE 03-28-07 PAGE 0001
FORECAST FOR CA-7 JOBS (INCLUDING THOSE IN CURRENT QUEUES)
07087/1213 07087/1222 *G1OLGPQA APPS REQ-Q 132
07087/1213 07087/1222 *G1OLGPQB APPS REQ-Q 132
07087/1232 07087/1236 *G1OLMAGA APPS LEV001 132 G1OLGP2A
07087/1232 07087/1236 *G1OLMAGB APPS LEV001 132 G1OLGP4B
[Note: If TO is specified, SPAN must be omitted. If neither is specified, selection is

based on only those jobs in the queues]
LCTLG COMMAND:
LCTLG command is primarily used,
 To list data set information from the CA- 7 index data set.
 To list special entries such as documentation, networks, triggers, or
requirements from the CA-7 database
 To list information from a specific CVOL catalog.
[Note: When LCTLG is used to list data sets, the following information is
displayed: volume information, creation dates and times, and device
information]
(1) LCTLG,DSN=TRGD.<jobname>
Displays the details of all the triggered by jobs of the given Job
LCTLG,DSN=TRGD.G1OL250P
DSN=TRGD.G1OL250P DATE 07.087 PAGE 0001
DATASET NAME TRIGGERED BY JOB/DSN SCHID QTM/DOTM LEADTM SUBMTM
TRGD.G1OL250P G1OL103P 000 0010Q 0010 0000
G1OM103P 000 0010Q 0010 0000
SLID-00 REQUEST COMPLETED AT 08:32:21 ON 07.087
(2) LCTLG,DSN=PRED.<jobname>
Displays all the Successor jobs for the given Job
LCTLG,DSN=PRED.G1OL250P
DSN=PRED.G1OL250P DATE 07.087 PAGE 0001
DATASET NAME SUCCESSOR JOB SCHID
PRED.G1OL250P G1OLYEND 000
(3) LCTLG,DSN=JDEP.<jobname>
Displays the details of all the triggered jobs of the given Job
LCTLG,DSN=JDEP.G1OL250P
DSN=JDEP.G1OL250P DATE 07.087 PAGE 0001
MSGS 0001
DATASET NAME TRIGGERED JOB SCHID QTM/DOTM LEADTM SUBMTM
JDEP.G1OL250P G1OL037P 000 0010Q 0010 0000
G1OL280P 000 0010Q 0010 0000

LDSN
LDSN command is used to list data set information from the database including data
set attributes, device and volume information, and information on which jobs use the
data set or are trigger scheduled as a result of its creation.
Command:
LDSN,DSN=<Dataset Name>,LIST=ALL
LDSN,DSN=SCPP.CA7.JCL,LIST=ALL
LIST=ALL DSN=SCPP.CA7.JCL DATE 07.096 PAGE 0001
MSGS 0024
---------------------------------------------- DATASET NAME --------------- DSNBR PPNBR POSTTM DSTYPE
DSORG RECFM LRECL BLKSZ DEVTYP J-USE J-CRT #RQ MDATE/TIME MTYPE
SCPP.CA7.JCL ....…………………......................... DS165566 *NONE* JTERM PERM
00000 00000 DASD 00001 00000 0000 06111/1800 LOAD
. LAST MAINTENANCE ON 06.111 AT 18:00:00 VIA LOAD

--------------------- DATASET/JOB CROSS REFERENCE ---------------------
JOB=SCPOCPPS STEP-NUMBER=003 DISP=SHR
STEP-NUMBER=003 DISP=SHR
SLIB-00 REQUEST COMPLETED AT 08:11:12 ON 07.096.

Different Tools That We Use For Monitoring (Ca-7, CA-11, $avours)

Uploaded by

Copyright:

Available Formats

Different Tools That We Use For Monitoring (Ca-7, CA-11, $avours)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Different Tools That We Use For Monitoring (Ca-7, CA-11, $avours)

Uploaded by

Copyright:

Available Formats

DIFFERENT TOOLS THAT WE USE FOR MONITORING (CA-

CA-7 is an automated production control system. It is an online system that automatically

CA-11 is an Automated Rerun and Tracking System. It can be used as an effective

 JOB TRACKING SYSTEM

Steps to get into $AVRS

 Type $ in the ISPF panel of SYS1/SYS2 to get into $AVRS

- THU 05 APR 2007.095 ------ $AVRS JOB SELECTION ------------------ ROW 1 OF 2

--------------------------- STEP INFORMATION -------------------------------------LINE 1 OF

CA-7 is an online, real time, interactive system which automatically

JCL: ID: 0 MEMBER: G1QQ21PD RELOAD: N EXEC: Y RETAIN-JCL: N

EXECUTION: MAINID: SY3 INSERT-RMS: Y COND-CODE: 0 RO: LT

NON PRODUCTION JOBS

FUNCTION: LIST (ADD,DELETE,DD,PURGE,DELPRRN,FORMAT,LIST,UPD)

JCL: ID: MEMBER: RELOAD: EXEC: RETAIN-JCL:

Fstruc, job=D will Ljob, job=D, list=rqmt will

INTERNAL JOB REQUIREMENT OR PREDECESSOR JOBS

INTRODUCTION OF TRIGGERED BY AND TRIGGERED JOBS

COMMAND TO CHECK THE TRIGGERED BY JOBS AND TRIGGERED JOBS

----------------- TRIGGERED BY JOBS/DATASETS/NETWORKS ------------------

PREDECESSOR JOBS AND SUCCESSOR JOBS :

COMMAND TO CHECK THE PREDECESSOR JOBS AND SUCCESSOR JOBS

 Ljob, job=jobname, list=rqmt  predecessor jobs

---------------- REQUIREMENTS AND NETWORK CONNECTIONS -----------------

 Ljob, job=jobname, list=depj  Successor jobs

--------------------------- SUCCESSOR JOBS ----------------------------

COMMANDS TO VIEW THE JOBS IN REQUEST QUEUE:

LREQ,JOB=Jobname – Displays a particular Job in Request Queue

We can also use this screen

COMMAND USED TO GET INTO THIS SCREEN:

Type JOB as a top line command

Type DB.1 in the top line

------------------------- CA-7 CPU JOB DEFINITION --------------------------

JCL: ID: MEMBER: RELOAD: EXEC: RETAIN-JCL:

EXECUTION: MAINID: INSERT-RMS: COND-CODE: RO:

MESSAGES: LTERM: REQUIREMENT-LIST: PROMPTS:

RESOURCES: REGION: CLOCK-TIME: CPU-TIME:

PROGRAM: SM20 MSG-INDX: 00 -- DB.1 -- 07.046 / 17:18:56 MSGS 0006

ADD : Adds a job to the database.

JOB: The job name on which the indicated function is to be performed.

ID : A numeric index value associated with a JCL library. Two values

REQUIREMENTS: Indicates that this section of the screen contains requirements

HOLD Indicates whether this job is to be placed in a hold status when it

INSERT-RMS :Indicates if the CA-11 RMS step is to be automatically inserted at

RESOURCES: These lines contain resource information about the job.

REGION : The region size required by this job.

M : Indicates a manual override value for the number of TYPE2 tape

Different modes by which the Jobs comes in to the Queue

 DEMAND, Job=Job name

This will puts the job in the ca-7 request queue.

This command will load a job,which specifies the Due-out

[Note : RELOAD field in the DB.1 screen is an alternative to this command]

DIFFERENCE BETWEEN RUN AND DEMAND MODE

 If the JCL library is unavailable (being compressed, etc.)

LQ,ST=SKEL - command used to list the jobs in skeleton status

PROCEDURE TO FOLLOW WHEN THE JOB IS IN SKELETON STATUS

CANCEL, JOB=ca7-id,REASON=SKELTON STATUS, FORCE=YES

XQM PANEL (CPU JOB STATUS SCREEN)

-------------------------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS -----------------

G2TE02PD TRAMS SY7 5/100 1511 00004/0004 00 00 01.67 NONE