JESDS parameter - IBM-JCL

Parameter Type

Keyword, optional

Purpose

Use the JESDS parameter to process the job’s system-managed data sets according to the parameters on this OUTPUT JCL statement. The system-managed data sets consist of:

  • The job log, which is a record of job-related information for the programmer. Printing of the job log is controlled by two JOB statement parameters: the MSGLEVEL parameter controls what is printed and the MSGCLASS parameter controls the system output class.
  • The job’s hard-copy log, which is a record of all message traffic for the job to and from the operator console.
  • System messages for the job.

Note: In a JES3 environment, a job can complete processing before all of its messages have been written to the job log. When this occurs, the job’s output is incomplete. For this reason, do not use the contents of the job log as an automation or as a programming interface.

1.Syntax

JESDS= {ALL} {JCL} {LOG} {MSG}

2.Subparameter Definition

ALL
Indicates that this OUTPUT JCL statement applies to all of the job’s system-managed data sets.

LOG
Indicates that this OUTPUT JCL statement applies only to the JESMSGLG data set, which contains the JES and operator messages for this job.

JCL
Indicates that this OUTPUT JCL statement applies only to the JESJCL data set, which contains the JCL statements for this job.

MSG
Indicates that this OUTPUT JCL statement applies only to the JESYSMSG data set, which contains any JCL error messages and any system messages for this job.

3.Overrides
The NOLOG parameter on a JES2 /*JOBPARM statement overrides the OUTPUT JCL JESDS=ALL parameter.

If an OUTPUT JCL statement contains both JESDS and CLASS parameters, the CLASS parameter will override the MSGCLASS parameter on the JOB statement for the specified JES data sets.

4.Location in the JCL
Place an OUTPUT JCL statement containing JESDS before the first EXEC statement of the job. An OUTPUT JCL statement containing JESDS placed after an EXEC statement is a JCL error.

You can place more than one OUTPUT JCL statement containing JESDS before the first EXEC statement. JES creates a copy of the job’s system data sets for each.

5.Destination for the System Data Sets
If you want the job’s system data sets processed at a particular destination, code a DEST parameter on the OUTPUT JCL statement containing JESDS. Otherwise, JES routes the system data sets to a local device.

6.JES2 Processing with JESDS
JES2 processes OUTPUT JCL statements for system-managed data sets (JESDS parameter) only if a job starts execution.

System-managed data sets are not processed for the following jobs because the jobs do not start execution:

  • Jobs that specify a TYPRUN value on the JOB statement that prevents execution, such as COPY or SCAN.
  • Jobs that do not execute because of a JCL error, an error in a JES2 control statement, or a system failure in JES2 input processing.

7.JES3 Processing with JESDS
System-managed data sets are not processed by JES3 for the following jobs because the jobs do not complete execution:

  • Jobs that specify a TYPRUN value on the JOB statement that prevents execution, such as SCAN.
  • Jobs that do not execute because of a JCL error.

8.Example of the JESDS Parameter

//EXMP JOB MSGCLASS=A //OUT1 OUTPUT JESDS=ALL //OUT2 OUTPUT JESDS=ALL,DEST=AUSTIN . . .

In this example, JES produces two copies of the system-managed data sets: one copy for OUTPUT JCL statement OUT1 and one copy for OUTPUT JCL statement OUT2. The copy for statement OUT2 is sent to AUSTIN.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM-JCL Topics