You are on page 1of 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. Forecasting Current or Future Schedules FJOB. LCTLG.1700). including schedules.TRIG=N FJOB.FROM=mmddyy. LJOB.SCHID=nnn.SPAN=hhhh Note: displays the downstream jobs triggered by the job on a specific date and for a specified number of hours.LIST=RQMT Note: displays all requirements that must be satisfied before the job will run.JOB=*.JOB=jobname.DSN=JDEP.FROM=(041307.JOB=jobname. LJOB. LJOB.FROM=(mmddyy.DSN=T1E990T.JOB=jobname.jobname Note: displays the job that triggered this job.JOB=jobname.ORA.TRIG=N FSTRUC.LIST=CALS FSTRUC.SYS=IMIS. FRJOB.LIST=NODD Note: displays all scheduling information.SCHID=nnn Where nnn is the Jobs Schedule ID. LJOB.JOB=jobname.LIST=DEPJ Note: displays all jobs dependent on the completion of this job. and requirements.LIST=TRIG Note: displays all jobs that trigger this job and all jobs triggered by the job. LJOB.JOB=*.0000). prose.JOB= jobname.SPAN=57.JOB=jobname.FROM=(122606.jobname Note: displays all jobs dependent on the completion of this job.JOB=jobname.TRIG=N FJOB. LCTLG. FSTRUC. .SCHID=nnn Note: displays the upstream (jobs that run before) jobs that this job was triggered from.LIST=SCHD Note: displays schedule information only.SCHID=nnn Note: displays the downstream jobs triggered by the job.0000).MRPSIGNL.DSN=TRGD.JOB=joname.NORUN Note: Display the Posted dataset Status LCTLG.SPAN=24.SPAN=24.JOB=jobname.

.A failed job is marked within CA-7 as a normal completion.A failed job is removed from the CA-7 queue.Global Computer Operations _________________________________________________________________________________ FJOB. CANCEL .FROM=(MMDDYY. Misc. Command and Information HELP .An operator will demand a job into CA-7 when it needs to be brought into the queue. Jobs waiting for the successful completion of this job will now run . GRAPHJ .Used to describe relationships between jobs in the same schedule.A schedule or jobstream can have many different variations. job1 can trigger job2.SPAN=HHHH Note: forecasts the job from the specified date and for the specified span.A job can be placed on hold before or after it enters the CA-7 queue. Job1 may trigger Job 2 on schid 1. Key information needed for a demand request is schedule id (schid) and if the job will run with triggers or without triggers.launches CA-7’s help panels. RESTART . SCHID . execute and fail. Each variation is called a schid or schedule id. 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. until the hold is removed. or wait in the queue until all requirements are satisfied. but on schid 3 Job 1 may trigger Job 3. 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.if all other requirements of the job are satisfied. For example.HHMM). Demand with triggers will result in all downstream jobs (based on schid) to run. meaning it will not run. HOLD . DEMAND .The term restart is interpreted as restarting the job in the step in which it has failed. For jobs that execute and fail the operator can take these actions FORCE COMPLETE . For example. Job2 is then described as having been triggered by Job1. Enter “D” and hit enter for a description of the various reports. The job will remain in hold. it can be ran immediately.JOB=jobname. or requirements such as job completions or submit time can be manually added. TRIGGER . Demand with no triggers will result in a stand alone run.launches CA-7’s Automated Performance Analysis reports menu. CA-11 notes. Once in the queue.

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