showjobs

To display the status of all jobs in the acctg job stream defined in the folder echo on workstation site3, stored in folder myfolder,you can run the showjobs command in one of these two formats:

showjobs /myfolder/site3#/echo/acctg.@

or:

showjobs /myfolder/site3#/echo/acctg

To display the status of job JBA belonging to job stream TEST1 on workstation CPUA, on which you are running conman, and ask to show the job stream identifier for the job stream, run the following command:

sj CPUA#TEST1(0900 02/19/18).JBA

A sample output for this command is the following:

Workstation Job Stream SchedTime Job State Pr Start Elapse ReturnCode Dependencies

CPUA        #TEST1    0900 02/19 *** HOLD   0(02/19)                 {02/20/18}; -TEST-
                                 JBA HOLD  66(14:30)                 J2(0600 02/24/18).JB1  

• The at dependency is shown as (14:30) in the Start column and the follows dependency from the job J2(0600 02/24/18).JB1 for job JOBA is shown in the Dependencies column.
• In the Dependencies column the date enclosed in braces, {02/20/15}, indicates that the job stream instance has been carried forward and the date indicates the day when the job stream instance was added to the production plan for the first time.

The following output example displays the status of all jobs, including predecessors and, in particular, job, JOBVACS, defined in job stream, JSHOLIDAYS1, that has a conditional dependency on predecessor job, JOBCHECKCALC, that specifies that JOBVACS runs if JOBCHECKCAL goes into either ABEND or FAIL state:

S_MDM      #JSHOLIDAYS  0600 09/23 ********************************** READY 10  (00:01)
                         (S_AGT#)JOBCHECKCAL                          HOLD  19
                         (S_AGT#)JOBVACS                              HOLD  10

JOBCHECKCAL IF ABEND | FAIL 

To display the status of jobs belonging to job stream JSDOC on workstation site3, on which you are running conman, and ask to show the job stream identifier for the job stream, run the following command:

%sj JSDOC.@;showid

A sample output for this command is the following:

Workstation Job Stream SchedTime Job State Pr Start Elapse ReturnCode Dependencies

site3        #JSDOCOM 0600 11/26 *** SUCC  10 11/26 00:01            {0AAAAAAAAAAAACRZ}
                                JDOC SUCC  10 11/26 00:01       0    #J25565

The job stream identifier 0AAAAAAAAAAAACRZ for job stream JDOCOM is shown in the Dependencies column.

To display the status of jobs belonging to job stream JSDOCOM on workstation site3, and ask to show the information about the user ID under which the job runs, run the following command:

sj site3#JSDOCOM.@;logon

A sample output for this command is the following:

Workstation Job Stream SchedTime  Job    State Job#    Logon   ReturnCode
site3       #JSDOCOM  0600 11/26
                                  JDOCOM SUCC  #J25565 me10_99     0
  

To display the status of all jobs in the HOLD state on all workstations, in the deps format, run the following command:

sj @#@.@+state=hold;deps

a sample output is the following:

Workstation Job Stream SchedTime Job  State Pr Start Elapse RetCode Dependencies

CPUA#JS2.JOBB Dependencies are:


CPUA        #JS21     0900 02/19 ***** HOLD  0(02/19)               {02/20/18}; -TEST- JOBA HOLD 66(14:30)
                                                                                 JS22(0600 02/24/18).JOBB

CPUA#JS25.JOBC Dependencies are:


CPUA       #JS25      0600 02/24 ***** HOLD 10(02/24)               {02/20/18}
                                 jobaa HOLD 10(02/24)(00:01)        TEST1; JOBC          TEST2; JOB1
                                                                                 JS18(0600 02/24/18).@

CPUA#JS25.JOB1 Dependencies are:


CPUA       #JS25      0600 02/24 ***** HOLD 10(02/24)                {02/20/18}
                                 JOBC  HOLD 10(02/24)(00:01)         JOB1
                                 jobaa HOLD 10(02/24)(00:01)         TEST1; JOBC         TEST2; JOB1
JS18(0600 02/24/18).@

To display the log from the standard list files for the job JOBC in the job stream JS25(0600 09/24/23) on workstation CPUA, running in a UNIX® environment, run the following command:

sj CPUA#JS25 (0600 09/24/23).JOBC;stdlist

The output is the following:

===============================================================
= JOB : CPUA#JS25[(0600 09/24/23),(0AAAAAAAAAAAABQM)].JOBC
= USER : mdm93mdm
= JCLFILE : ls
= TWSRCMAP :
= AGENT : CPUA
= Job Number: 987278608
= Sun Sep 24 17:06:27 CEST 2023
===============================================================
AE
CAP
IMShared
TWA
WebSphere

===============================================================
= Exit Status : 0
= SC STATUS_OK : true
= OC OUTPUTCOND2 : false
= OC OUTPUTCOND1 : true
= System Time (Seconds) : 0
Elapsed Time (hh:mm:ss) : 00:00:01
= User Time (Seconds)   : 0
= Job CPU usage (ms) : 20
= Job Memory usage (kb) : 1272
= Sun Sep 24 15:16:25 CEST 2023

where:

Exit Status

Is the status of the job when it completed.

OC <output_condition_name>

The result of the evaluation of the output conditions that when satisfied, determine which successor job runs. Output conditions that are satisfied display true, and output conditions that are not satisfied display false. Successful output conditions are represented by the sc flag in the ;stdlist output.

System Time

Is the time the kernel system spent for the job.

Elapsed Time

Is the elapsed time for the job.

User Time

Is the time the system user spent for the job.

To display the properties of the job with job number 227137038, run the following command:

sj 227137038;props

A sample output for this command is the following:

sj SMA1964199;props
General Information
 Job = JOBAUTO
 Workstation = NC005090_1
 Task =
 <?xml version="1.0" encoding="UTF-8"?>
 <jsdl:jobDefinition xmlns:jsdl="http://www.ibm.com/xmlns/prod/scheduling/1.0/jsdl"
   xmlns:jsdle=
     "http://www.ibm.com/xmlns/prod/scheduling/1.0/jsdle">
   <jsdl:application name="executable">
   <jsdle:executable interactive="false">
   <jsdle:script>ping -n 180 localhost</jsdle:script>
   </jsdle:executable>
   </jsdl:application>
   </jsdl:jobDefinition>
 Task Type = executable
 Job Stream = SMA1964199
 Job Stream Workstation = NC005090_1
 Scheduled Time = 11/20/2023 16:57:00 TZ CET
 Priority = 50
 Login =
 Monitored = No
 Requires Confirmation = No
 Interactive = No
 Critical = No

Runtime Information
 Status = Running
 Internal Status = EXEC
 Not Satisfied Dependencies = 0
 Job Number = 227137038
 Rerun Options =
 Information =
 Promoted = No
 Return Code =
 Success Output Conditions
 STATUS_OK = true “RC=0”
Other Output Conditions
 STATUS_ERR1 = false “RC=2”
 STATUS_ERR2 = false “RC=3”

Time Information
 Actual Start = 11/20/2023 16:57:36 TZ CET
 Earliest Start =
 Latest Start =
 Latest Start Action =
 Maximum Duration =
 Maximum Duration Action =
 Minimum Duration =
 Minimum Duration Action =
 Critical Latest Start =
 Deadline =
 Repeat Range =
 Actual Duration =
 Estimated Duration = 00:03:02 (hh:mm:ss)
 Confidence Interval = 00:00:00 (hh:mm:ss)

Recovery Information
 Action = Stop
 Message =
 Job Definition =
 Workstation =
 Retry after =
 Number of attempts=
 Current attempt =
 Run on same workstation =

Extra Information
 PID = 3132 

The following example displays the status of the job dbseload with a return code of 7 and a state of SUCCESSFUL:

$conman sj workstation#DAILY_DB_LOAD
 ####################################################################
  # Licensed Materials - Property of IBM* and HCL**
  # 5698-WSH
  # (C) Copyright IBM Corp. 1998, 2016 All rights reserved.
  # (C) Copyright HCL Technologies Ltd. 2016, 2024 All rights reserved.
  # * Trademark of International Business Machines
  # ** Trademark of HCL Technologies Limited
  ###################################################################
Installed for user "tme10_99".
Locale LANG set to the following: "en"
Scheduled for (Exp) 02/20/18 (#35) on CPUA.
Batchman LIVES. Limit:50,Fence:0,Audit Level:0
sj workstation#DAILY_DB_LOAD
(Est) (Est)
CPU Schedule Job State Pr Start
Elapse Dependencies Return Code
WORKSTATION #DAILY_DB_LOAD ****************************** SUCC 10 22:11
00:04
DATASPLT SUCC 10 22:11
00:01 #J17922 0
DATAMRGE ABEND 10 22:12
00:01 #J17924 1
CHCKMRGE SUCC 10 22:12
00:01 #J17926 0
DATACLNS SUCC 10 22:12
00:01 #J17932 0
DATARMRG SUCC 10 22:13
00:01 #J18704 0
DBSELOAD SUCC 10 22:13
00:01 #J18706 7
DATAREPT SUCC 10 22:13
00:01 #J18712 0
DATARTRN SUCC 10 22:14
00:01 #J18714 0
$

The following example displays the return code for a specific job named workstation#daily_db_load.dbseload:

$ conman sj workstation#daily_db_load.dbseload\;keys\;retcod
  ####################################################################
  # Licensed Materials - Property of IBM* and HCL**
  # 5698-WSH
  # (C) Copyright IBM Corp. 1998, 2016 All rights reserved.
  # (C) Copyright HCL Technologies Ltd. 2016, 2024 All rights reserved.
  # * Trademark of International Business Machines
  # ** Trademark of HCL Technologies Limited
  ###################################################################
Installed for user "tme10_99".
Locale LANG set to the following: "en"
Scheduled for (Exp) 02/20/19 (#35) on CPUA.
Batchman LIVES. Limit:50,Fence:0,Audit Level:0
sj workstation#daily_db_load.dbseload;keys;retcod 8
$

The following example shows a job stream containing a job (named RE_ACCOUNTS_JOB) which ends in ABEND state. After the parent RE_ACCOUNTS_JOB job fails, the recovery job starts. When the recovery job completes in success state, the parent job waits a minute, then reruns. The sequence is repeated for three times, if the parent job keeps failing. If the parent job completes successfully, the rerun sequence is interrupted at the first successful run of the parent job:

SCHEDULE NC053009#RE_JS_04
ON RUNCYCLE RC1 "FREQ=DAILY;INTERVAL=1"
:
NC053009_1#JOB_2
 FOLLOWS RE_ACCOUNTS_JOB
NC053009_1#RE_ACCOUNTS_JOB
END

NC053009_1#RE_ACCOUNTS_JOB
 DOCOMMAND "sleep 60; exit 5"
 STREAMLOGON bankmngr
 TASKTYPE UNIX
 RECOVERY RERUN REPEATEVERY 0001 FOR 3
  AFTER NC053009_1#RECOVERY_JOB

The following is the output of the sj command at the end of the sequence:

NC053009        #RE_JS_04         0000 01/24 ***************************************STUCK 10 17:40
                            (NC053009_1#)JOB_2                                HOLD  10           RE_ACCOUNTS_JOB
                            (NC053009_1#)RE_ACCOUNTS_JOB              ABEND 10 17:40  00:01        5 #J277948077
 >>recovery                 (NC053009_1#)RECOVERY_JOB                 SUCC  10 17:42  00:01        0 #J277948082
 >>rerun 1 of 3             (NC053009_1#)RE_ACCOUNTS_JOB              ABEND 10 17:44  00:01        5 #J277948085
 >>recovery                 (NC053009_1#)RECOVERY_JOB                 SUCC  10 17:45  00:01        0 #J277948087
 >>rerun 2 of 3             (NC053009_1#)RE_ACCOUNTS_JOB              ABEND 10 17:47  00:01        5 #J277948089
 >>recovery                 (NC053009_1#)RECOVERY_JOB                 SUCC  10 17:48  00:01        0 #J277948090
 >>rerun 3 of 3             (NC053009_1#)RE_ACCOUNTS_JOB              ABEND 10 17:50  00:01        5 #J277948092
                                                                                        [Recovery]