Table 1 is the sample record broken into fields which are described after the table.

Field

Contents

1

The address of the I/O buffer or data this record traces. You will see trace entries with the same addresses as JES2 reuses IOBs.

2 - 7

Trace buffer prefix.

8 - first 2 characters

I/O completion flags from the IOB. Successful completion = X'42'. Error = X'46'.

8 - last 4 characters

First 2 sense bytes of the I/O operation. See sense information for individual devices.

9

Event control block (ECB) completion codes and the JES2 pointer to the ECB. Common completion codes are:

X'41'

I/O error. Check the sense information.

X'44'

IOB intercept. CSW is not valid.

X'48'

I/O was purged.

X'7F'

Normal completion.

X'FF'

Requeued BSC buffer. This value only occurs on a JES2 system.

row 2, field 2 - last 6 characters

This is the beginning CSW without its first byte. This information is 7 bytes long. The first 3 bytes is an address that points 8 bytes past the last CCW completed. The count field in this CSW is the residual data count of the CCW just completed. The actual number of bytes read or written is the difference between this value and the CCW byte count in the CCW just completed.

row 2, field 4 - first 2 characters

The start I/O (SIO) condition code.

row 2, field 4 - next 4 characters

Address of the start of the channel program.

Row 3, field 4

Channel programs.

The output contains CCW entries preceded by the characters CCW. Data associated with a particular CCW immediately follows the CCW. See z/OS MVS System Messages, Vol 5 (EDG-GFS) for a complete list of completion codes and information about networking I/O.

See the description of message $HASP094 in z/OS JES2 Messages for additional information about some of the previous fields.