Beruflich Dokumente
Kultur Dokumente
lq,job=gtb*
By giving this you can know whether the job is the ready queue or is it waiting for any
resource or like that
LQ
LIST= DATE=01.150 PAGE 00
JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB
NAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ
STATUS
GCP05BKP REQ 7635 143/0021 143/0225 143/0110 ALL-ANZH 001 SSCN 001 R-C0008
GTBAREND REQ 4258 145/2024 *NONE* 145/2032 ALL- 001 AUTO 009 LATE
GTBASEND REQ 4259 145/2024 *NONE* 145/2032 *NOEX* 001 AUTO 002 LATE
GTBASINI REQ 4290 145/2046 *NONE* 145/2054 ALL- 001 AUTO 001 LATE
2. xqm,job=gtb*
in this the job GTBASINI is in hold. if you want to release it , put " r" in the left most
side of the job.
3. To restart the job, "f" in the left most side and then use the appropriate option.
3. ljob,job=g3zarip,list=all
It will give information about which job is triggering this job , which jobs will be triggered by
this and what are dependencies.
4. FSTRUC,JOB=JOBNAME
It will give whole flow of jobs taking job name mentioned above at top of the hierarchy.
5. XQ,JOB=JOBNAME
It will display job if that job is went in queue, that is going to run once it’s dependency is
finished.
6. RUN,JOB=JOBNAME
It is going to run job independently.
7.RUNH,JOB=JOBNMAE
It will put job in queue with hold so you can do jcl edit ie u can give file override etc before
running that.
8.DEMAND,JOB=JOBNAME
It’s same as RUN except it also initiate the jobs which are being triggered by this.
9.DEMANDH,JOB=JOBNAME
It is same as DEMAND except it put the job in queue with hold so that you can do jlc edit ,
file overide etc.
10.LJCL,JOB=JOBNAME
It will display the jcl of that job.
Method I:
Type "List" in function and the "JOB name" in "PRED FOR JOB" field. This will list all the
jobconn holds that are active for this job.
Type "UPD" in function and the "JOB name" in "PRED FOR JOB" field. Then type "A" in
"OPT" and the comments indicating the reason for the hold in the field "*--- MEMO-FORM
USER PREDECESSOR ---* ".
If the requirement is to run a job from the override just once then put a "Y" in the field "USE-
OVRD-LIB".
By doing this CA7 does the following:
• Picks up the JCL from the override library for the next run only.
• Resets the value of the field "USE-OVRD-LIB" to a "N".
• Deletes the JCL from the override library.
This way we can just make the change once and forget about it (we don't need to reset the
job to run from normal after the first run).
In the event that you are unable to perform a JOBCONN hold, try this
If requirment is to be added
go to ca7
type JOBCONN
select fuction 4
following screen will come
--------------------- CA-7 INPUT/OUTPUT NETWORK TASKS ----------------------
FUNCTION: (FORMAT,LIST,UPD) PAGE 0001
TASK FOR JOB: LIST-SCHID:
OPT SCHID LEADTM NETWORK SUB-ID NWK-SCHID DESCRIPTION NEXT-RUN
CA7 queues
Ca7 has 3 queues.
REQ = this is the request queue. Any job waiting to be run will be in the request queue. A job
will enter the request queue once the job that triggers it completes normally. It will wait in this
queue until all requirements for it to run are satisfied. This queue can be viewed using the
PF1 function key.
RDY = This is the ready queue. All job that have been submitted to JES will enter this queue.
This queue can be viewed using <shift><PF1>. If a job returns with a JCL error in the job
card, it will remain in this queue.
ACT = All jobs that start execution will enter this queue.
PF2 will display jobs in all the queues. PF4 is the customised version of this queue as
described before.
/PROF
PF04 LQ,SYS=GEMSXPR9