Display status of a job
When your attention is drawn to a particular job, because of a user call, a message, or any other trigger, you start with its status. From there you may take any number of other actions, including "wait and see".
The table below contains the set of commands you might use to get the status of a job. Most of the commands have other variations and parameters, though only the relevant ones are discussed here.
Commands
To display... | Key... |
|---|---|
the full description of a job, including any holds. | /JOB Display job-id LONG If there are TM holds, the appropriate hold details are displayed |
standard JES2 information | $DJjob-id,LONG Information from a Job D job-id L command is automatically appended |
a quick look to see if a job has any holds. | /JOB Display job-id |
the service details of a job | /SLM Display JOB job-id |
details about the data set causing a job to be held | /DCS Display job-id |
details about the binds for a job, and whether the job is held | /JBS Display job-id |
details about a job that uses HSM, virtual volumes, or ALS, and whether the job is held | /JSS Display job-id |
Example 1
HOLD=(TM) and the DELAY=(HOLD) fields:
$HASP890 JOB(BNK78DB)
$HASP890 JOB(BNK78DB) STATUS=(AWAITING EXECUTION),CLASS=2,
$HASP890 PRIORITY=2,SYSAFF=(DOCT),HOLD=(TM),
$HASP890 CMDAUTH=(LOCAL),OFFS=(),SECLABEL=,
$HASP890 USERID=RSI01AW,SPOOL=(VOLUMES=(DOCSP0),
$HASP890 TGS=1,PERCENT=0.0025),ARM_ELEMENT=NO,
$HASP890 CARDS=54,DUBIOUS=NO,REBUILD=NO,
$HASP890 SRVCLASS=TMPS1,SCHENV=,
$HASP890 SCHENV_AFF=(ANY),CC=(),DELAY=(HOLD),
$HASP890 CRTIME=(yyy.ddd,23:31:12),JOBGROUP=
DTM0220I Job Display
JOB03621 BNK78DB Awaiting Execution For 1 Min
Class : 2 (Production_Services)
Priority: 2
Sysaff : Any
TM-HOLD
Managed: SLM
DJC HOLD
JBS
At 19:31:29, job was not selected because it is held by
ThruPut Manager
DTM6420I DJC DISPLAY
JOB03621 BNK78DB in PSG.BNK Waiting XEQ Held
- RUNIF BNK1001H NORMAL
DTM6420I JBS BINDING DISPLAY 454
JOB03621 BNK78DB AWAITING EXEC SYS=ANY
BINDS TO - DOCT.ONLY
DTM8226I SLM Job Display
JOB03621 BNK78DB Awaiting Execution
At 19:31:29, job was not selected because it is held by
ThruPut Manager
Workload Type : Production Services
Job Scheduler : None
Production Group Name : BNKDB
Importance : 1
Total Delay Time : 00:00:44
Currently Delayed By : Dependent job
Example 2
Here's the output of a $DJ for a General Services job assigned to the BNK QA service group:
$HASP890 JOB(J527BNK)
$HASP890 JOB(J527BNK) STATUS=(AWAITING EXECUTION),CLASS=1,
$HASP890 PRIORITY=6,HOLD=(RESOURCE),
$HASP890 CMDAUTH=(LOCAL),OFFS=(),SECLABEL=,
$HASP890 USERID=RSI01AW,SPOOL=(VOLUMES=(DOCSP0),
$HASP890 TGS=1,PERCENT=0.0025),ARM_ELEMENT=NO,
$HASP890 CARDS=90,DUBIOUS=NO,REBUILD=NO,
$HASP890 SRVCLASS=TMGS2,SCHENV=,
$HASP890 SCHENV_AFF=(ANY),CC=(),DELAY=(SYSAFF),
$HASP890 CRTIME=(2017.250,23:57:50),JOBGROUP=
DTM0220I Job Display
JOB03645 J527BNK Awaiting Execution For 6 Mins
Class : 1 (General_Services)
Priority: 6
Sysaff : Any
TM-HOLD
Managed: SLM
DJC
JBS HOLD
At 19:58:03 on Sep 7, job was not selected because it is held by
ThruPut Manager
DTM6420I DJC DISPLAY
JOB03645 J527BNK in GSG.ADHOC Waiting XEQ
DTM6420I JBS BINDING DISPLAY 657
JOB03645 J527BNK HELD BY JBS SYS=ANY
BINDS TO - DOCT.ONLY *INACTIVE*
DTM8226I SLM Job Display 658
JOB03645 J527BNK Awaiting Execution
At 19:58:03 on Sep 7, job was not selected because it is held by
ThruPut Manager
Workload Type : General Services
Control Center: BNK (Adhoc banking jobs)
Type : QA (Pre-prod testing)
Batch Service : Before Target
Trend : Stable
Service Mode : Standard
Importance : 2
Job Service : At Target
Estimated Time to Selection: Indeterminate
Primary reason Estimated Time to Selection could not be calculated.
- Job is delayed.
Secondary reason(s) Estimated Time to Selection could not be
calculated.
- Job is being treated as Exceptional.
Exception summary:
- Job encountered unusual delays.
- Service level information is not available.
- Job not selectable on any active member
Effective Queue Time : Less than 1 minute
Total Delay Time : 00:06:19
Currently Delayed By : Binding/Environment
The awaiting execution status may be replaced with over forty BMC ThruPut Manager-specific reasons, such as
- DELAY-HELD Duplic. The job is held by JES2 because its name duplicates that of a running job.
- -SLM- Srv Cls Perf Job cannot be selected on this system due to the performance of the Service Class.
- -SLM-<Sel PT/SvGp means the job cannot run because it has not aged to the selection point designated for the service group.
The inserts are listed in the BMC ThruPut Manager Operating space. Similar descriptions are also used within the JOB command. More meaningful hold reasons are also displayed,
The /SLM D JOB command is automatically appended to $DJ, and /JOB D job-id LONG is automatically appended to $DJ job-id,LONG. The LONG parameter on the /JOB D command automatically issues further commands, such as a JBS or JLS display, to give a more complete picture.
Example 3
This example looks at a job from a JBS point of view:
DTM6420I JBS BINDING DISPLAY
JOB03645 J527BNK HELD BY JBS SYS=ANY
BINDS TO - DOCT.ONLY INACTIVE*
Clearly the binding agent needs to be activated for this hold to be released.