JES2 system data sets

The job log is a collection of data sets that include the user's console messages and replies to WTORs issued during job processing. The job log can appear in the job output on the page following the job's separator page. The job log is grouped into a single output group and only printed once, unless JESLOG=SPIN is specified. Installations can choose to print or suppress the job log by using the JES2 JOBCLASS initialization statement or by using JCL.

The system ID and system NODE found in the title line of the JES2 job log are the JES2 member name and NODE name of whichever phase of JES2 processing first puts messages into the job log.

To provide an indication when a particular message was logged for jobs that run multiple days, JES2 provides day/date messages in the JES2 JOBLOG. The time stamp on the first message matches the time that the first data record (PUT) was processed. The time stamp on all subsequent day/date messages is always midnight (00.00.00). See Figure 1 to illustrate the following example: If a job is submitted on day 1 (27 MAR 1995), issues no messages for the next three days (28, 29, and 30 March), and ends on day 5 (31 MAR 1995), the JOBLOG contains two dates only; the first at the top of the JOBLOG when the job began and the second before the end on day 5 at midnight. There is no entry for a day in which no messages were logged, and therefore, never two consecutive lines with the day/date message.

Figure 1. Sample JES2 job log

J E S 2 J O B  L O G - S Y S T E M  A Q T S - N O D E P O K

- MONDAY, 27 MARCH 2003 -
IRR010I  USERID PAULAC IS ASSIGNED TO THIS JOB.
ICH70001I PAULAC   LAST ACCESS AT 09:13:23 ON WEDNESDAY, MARCH 29, 2003
$HASP373 PAULACD  STARTED - INIT   12 - CLASS U - SYS AQTS
IEF403I PAULACD - STARTED - TIME=09.17.56
- ========================================================================================
-                               REGION      - STEP TIMINGS -           -PAGING COUNTS-
- STEPNAME PROCSTEP PGMNAME  CC USED   CPU TIME ELAPSED TIME EXCP SERV PAGE SWAP VIO SWAPS
- TSO               IKJEFT01 00 452K 00:00:01.46 00:00:06.48  538 37817   0    0   0     0
- FRIDAY,   31 MARCH 2003 -
$HASP395 PAULACD   ENDED
IEF404I PAULACD  - ENDED - TIME=15.20.02
- ========================================================================================
- NAME-PAULAK    TOTALS: CPU TIME=00:00:51.46 ELAPSED TIME=04:06:06.51 SERVICE UNITS=37817
- ========================================================================================
- JES2 JOB STATISTICS -
  27 MAR 2003 JOB EXECUTION DATE
           72 CARDS READ
        7,287 SYSOUT PRINT RECORDS

JES2 produces JES2 system data sets for each job according to parameters defined on the JESDS JCL statement or the /*JOBPARM JES2 control statement. These data sets are collectively called the job log. These data sets are written by JES2 and accompany user's output; they can also be accessed by the process SYSOUT (PSO) interface through the external writer or using the TSO/E OUTPUT command.

Table 1 shows the names and purposes of these JES2 system data sets.

Table 1. JES2 system data sets
Data Set Name	Purpose of data set
JESJCLIN	Indicates the actual JCL submitted.
JESMSGLG	Indicates any system messages for this job.
JESJCL	Indicates all job control statements in the input stream, that is, all JCL statements and JES2 control statements, plus all procedure statements from any in-stream or cataloged procedure a job step calls, plus all messages about job control statements.
JESYSMSG	Indicates the job's hardcopy log, which contains the JES2 and operator messages about the job's processing: allocation of devices and volumes, execution and termination of job steps and the job, and disposition of data sets.

JES2 does not produce JES2 system data sets for jobs that do not complete execution (that is, jobs that specify TYPRUN on JOB JCL statements, JCL errors, or failure because of an MVS™ system failure). See z/OS MVS JCL Reference for information about using the job log.

For more information on displaying or suppressing a job log, see z/OS JES2 Initialization and Tuning Reference.