Scribd
Upload
868 views

CA7 Commands & General Information

This document provides information about common commands used to view job history, queues, requirements, dependencies, and schedules in the CA-7 workload automation system. It also defines common terms used in CA-7 like trigger, demand, hold, schid (schedule ID), restart, and re-run. Key commands displayed jobs in the request, ready, active, and JES queues. Other commands showed schedule information, downstream/upstream jobs, and allowed forecasting future schedules from a given date and time span.

Uploaded by

svdontha
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
868 views

CA7 Commands & General Information

This document provides information about common commands used to view job history, queues, requirements, dependencies, and schedules in the CA-7 workload automation system. It also defines common terms used in CA-7 like trigger, demand, hold, schid (schedule ID), restart, and re-run. Key commands displayed jobs in the request, ready, active, and JES queues. Other commands showed schedule information, downstream/upstream jobs, and allowed forecasting future schedules from a given date and time span.

Uploaded by

svdontha
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Global Computer Operations

_________________________________________________________________________________

Common CA-7 Commands / General Information


Displaying Job History
LRLOG,DATE=*YYDDD,SPAN=(YYDDD,HHMM,YYDDD,HHMM),ST=RSTR
,ST=CANC
,ST=FORCE
Note: CA-7 retains the run logs for the previous 4 days, plus the current day.
Examples:
LRLOG,JOB=jobname,DATE=*yyddd
(example: 07085)
Note: if DATE not specified, default is current date.
LRLOG,DATE=*02196,SPAN=(02196,1800,02196,1900)
Note: this command displays the Run Log information between
18:00 and 19:00 on day 196.
LPRRN,JOB=jobname
Note: this will display the date/time of the last run of the job.
Displaying CA-7 Queues
LRLOG,JOB=IICJ030,DATE=* or LPRRN,JOB=IICJ030
To see the last run status of a Job
LQ,SEQ=JOB
Note: displays the Request queue in CA-7. These jobs have been scheduled on CA-7
either by Schedule Scan, being Demanded into the queue, or from being triggered from
another event such as a job completion.
LRDY,SEQ=JOB
Note: displays the Ready queue in CA-7. These jobs have had all of their CA-7
dependencies and/or requirements satisfied either automatically or manually. Jobs
stay in this queue until system resources such as initiators or tape drives are available.
LACT,SEQ=JOB
Note: displays the Active queue in CA-7. These jobs are executing on the system.
LJES,SEQ=JOB
Note: displays the JES number of the job. CA-7 job number and the JES number are
not the same.

Global Computer Operations


_________________________________________________________________________________

Displaying Job Requirements and Dependencies


LSCHD,JOB=jobname,LIST=CALS
FSTRUC,JOB= jobname,SCHID=nnn

Where nnn is the Jobs Schedule ID.

LJOB,JOB=jobname,LIST=NODD
Note: displays all scheduling information, including schedules, prose, and requirements.
LJOB,JOB=jobname,LIST=TRIG
Note: displays all jobs that trigger this job and all jobs triggered by the job.
LJOB,JOB=jobname,LIST=SCHD
Note: displays schedule information only.
LJOB,JOB=jobname,LIST=RQMT
Note: displays all requirements that must be satisfied before the job will run.
LJOB,JOB=jobname,LIST=DEPJ
Note: displays all jobs dependent on the completion of this job.
LCTLG,DSN=JDEP.jobname
Note: displays all jobs dependent on the completion of this job.
LCTLG,DSN=T1E990T.ORA.MRPSIGNL.NORUN
Note: Display the Posted dataset Status
LCTLG,DSN=TRGD.jobname
Note: displays the job that triggered this job.
Forecasting Current or Future Schedules
FJOB,JOB=*,FROM=(122606,0000),SPAN=24,TRIG=N
FJOB,JOB=*,FROM=(mmddyy,0000),SPAN=24,TRIG=N
FJOB,SYS=IMIS,FROM=(041307,1700),SPAN=57,TRIG=N

FSTRUC,JOB=jobname,SCHID=nnn
Note: displays the downstream jobs triggered by the job.
FSTRUC,JOB=jobname,SCHID=nnn,FROM=mmddyy,SPAN=hhhh
Note: displays the downstream jobs triggered by the job on a specific
date and for a specified number of hours.
FRJOB,JOB=joname,SCHID=nnn
Note: displays the upstream (jobs that run before) jobs that this job was triggered from.

Global Computer Operations


_________________________________________________________________________________

FJOB,JOB=jobname,FROM=(MMDDYY,HHMM),SPAN=HHHH
Note: forecasts the job from the specified date and for the specified span.
Misc. Command and Information
HELP - launches CA-7s help panels.
GRAPHJ - launches CA-7s Automated Performance Analysis reports menu. Enter D
and hit enter for a description of the various reports.
CA-11 notes.

Using a RESTART card in the JCL will bypass all CA-11 processing!

Common Terms and Definitions


When a job enters into the CA-7 queue it can complete normally, execute and fail, or wait
in the queue until all requirements are satisfied. For jobs that execute and fail the
operator can take these actions FORCE COMPLETE - A failed job is marked within CA-7 as a normal completion.
Jobs waiting for the successful completion of this job will now run - if all other
requirements of the job are satisfied.
CANCEL - A failed job is removed from the CA-7 queue. Jobs waiting for the successful
completion of this job will not run unless the requirement for the failed job is manually
satisfied and if all other requirements of the job are satisfied.
TRIGGER - Used to describe relationships between jobs in the same schedule. For
example, job1 can trigger job2. Job2 is then described as having been triggered by Job1.
DEMAND - An operator will demand a job into CA-7 when it needs to be brought into
the queue. Once in the queue, it can be ran immediately, or requirements such as job
completions or submit time can be manually added. Key information needed for a
demand request is schedule id (schid) and if the job will run with triggers or without
triggers. Demand with no triggers will result in a stand alone run. Demand with triggers
will result in all downstream jobs (based on schid) to run.
HOLD - A job can be placed on hold before or after it enters the CA-7 queue. The job
will remain in hold, meaning it will not run, until the hold is removed.
SCHID - A schedule or jobstream can have many different variations. Each variation is
called a schid or schedule id. For example, Job1 may trigger Job 2 on schid 1, but on
schid 3 Job 1 may trigger Job 3.
RESTART - The term restart is interpreted as restarting the job in the step in which it has
failed.

Global Computer Operations


_________________________________________________________________________________

RE-RUN - The term re-run is interpreted as re-running the job from the top, or first step
of the job. RESUBMIT and re-run having the same meaning.

You might also like