A nonzero value in this field usually indicates that the problem was due to a non-hardware related error.
For certain user errors, it may be possible for you to easily determine the problem and make the appropriate modifications to your program.
Table 1 is a list of diagnostic codes.
Diagnostic Code | Description |
---|---|
1 (X'01') | Bad parameter list passed to asynchronous completion routine by SMS system service (PDSE). |
2 (X'02') | Program check encountered in asynchronous completion routine (PDSE). |
3 (X'03') | Error return code returned from SMS system service when processing PDSEs. |
4 (X'04') | Invalid token encountered by POINT.1 |
5 (X'05') | Unsuccessful attempt to position to a member by using POINT (PDSE). |
6 (X'06') | Data set open for output, but the token passed to POINT was not for the current member (PDSE).1 |
7 (X'07') | Outstanding I/O was in progress when POINT issued.1 |
8 (X'08') | Token passed to POINT would have caused POINT to position beyond the end of the data set.1 |
9 (X'09') | Unable to get appropriate locks during POINT processing (PDSE). |
10 (X'0A') | Attempt to POINT to a nonexistent member (PDSE).1 |
11 (X'0B') | A padding error encountered (extended format data set). |
12 (X'0C') | Error return code returned from a system service when processing extended format data sets. |
13 (X'0D') | An I/O error was encountered in a shadow IOB (compressed format data set). |
14 (X'0E') | A READ/WRITE issued against a compressed format data set whose DCB specifies NOTE/POINT (MACRF=P) was for a block whose user RBN value exceeds the 3-byte token limit of 16 777 215 (compressed format data set). |
15 (X'0F') | An error was encountered while processing a UNIX file. |