>>-jobname--OUTGRP=--grpid,joeid1,joeid2------------------------>

>--BLOCK=--nnnn--devname--TERMINATED –  text, RC=rsnc----------><

In the message text:

jobname

The name of the job.

grpid

The group identifier either assigned by the user JCL or generated by JES2 if the user did not specify it.

joeid1

The number of job output elements in output group grpid.

joeid2

The number of job output elements in the output group identified by grpid and joeid1.

nnnn

The relative block number of the data set in which the error was detected.

rsnc

The reason code.

text

The explanatory text accompanying the reason code.

The device is stopped for the reasons associated with the following reason codes:

rsnc

text

01

DATA SET NOT CLOSED

JES2 stopped processing the current data set because it encountered an error while attempting to read the next block of data. The data set was not closed. This may be because either the job was running during a system failure and is now being printed without being rerun or an abend occurred in CLOSE processing.

02

INVALID TRACK ADDRESS

JES2 detected that the track address of the next data block to be read is incorrect. It may be incorrect because a storage overlay of the track addressing field of the next spool block occurred before the block was written out. If BLOCK=1 is displayed, the error occurred in the control block pointing to the start of the data set (PDDB in the IOT). If BLOCK=1 is not displayed, the error occurred in a data block. If a dump is issued, the $PCE contains the value of the incorrect track address in the PCESEEK field.

03

I/O READ ERROR

An I/O error occurred while JES2 was attempting to read the data block numbered nnnn for the specified data set. A hardware problem is the probable cause for the error.

04

INVALID JOB KEY

The job key field of the data block numbered nnnn does not match the current job key because the same spool address has been allocated to more than one job. This is most likely caused by a JES2 abend after the JES2 checkpoint processor began to replenish the TGMs but before the next checkpoint write started.

05

INVALID DATA SET KEY

The data set key field of data block numbered nnnn does not match the current data set key. Allocation of the same spool address to more than one data set within a multi-tasking program is most likely caused by an error within the JES2 subsystem interface.

06

OBSOLETE OUTPUT ELEMENT

JES2 selected an output element that is ineligible for processing because its corresponding data set was already purged. The probable cause for this error is that, after a JES2 failure, the spin data set was purged without the JOE being removed.

07

AUTHORIZATION FAILED

The user identification associated with the output group is not eligible to use the device that selected this group.

08

BAD I/O FOR SWBIT READ

An I/O error occurred while JES2 was reading the SWBIT(s) for a data set during print separator processing. This is probably a hardware error.

09

NO DATA SET IN THE IOT

JES2 did not find a matching data set for the job output element (JOE) in the IOT during print/punch processing. This is probably an IOT chaining error.