These reason codes (Table 1 ) apply to all 3800 or 3900 printers and the IBM® 4245 printer. Return code X'1C' returned in register 15. The reason code is placed in byte 3 of register 0.
| Reason Code (Byte 3) | Meaning |
|---|---|
| X'00' | Indicates no data lost. |
| X'04' | Indicates data has been lost. |
Table 2 shows the reason codes in addition to return code X'48' returned in register 15. The reason code is placed in byte 3 of register 0.
| Reason Code (Byte 3) | Meaning |
|---|---|
| X'04' | A paper jam caused a restart. A possible lost data condition was detected. |
| X'08' | The cancel key was pressed. |
| X'0C' | Resources were lost after a paper jam. |
Table 3 shows the reason codes in addition to return code X'50' returned in register 15. The reason code is placed in byte 3 of register 0.
| Reason Code (Byte 3) | Meaning |
|---|---|
| X'04' | An invalid SETPRT request for a SYSOUT data segment was specified. An in-storage address was used for a copy modification, character arrangement table, FCB, or user library DCB. Only load module IDs in SYS1.IMAGELIB are allowed for SYSOUT setup. |
| X'08' | During SETPRT processing for a SYSOUT data segment, an error was detected while attempting to read a JFCB or JFCBE control block from SWA. |
| X'0C' | During SETPRT processing for a SYSOUT data segment, an error was detected while invoking the CLOSE subsystem interface (SSI) for the previous data segment. |
| X'10' | During SETPRT processing for a SYSOUT data segment, an error was detected while invoking the OPEN subsystem interface (SSI) for the new data segment being created. |
| X'14' | During SETPRT processing for a SYSOUT data segment, an error was detected while the scheduler spool file allocation routine was segmenting the data set. |
| X'18' | An ENQ macro failed. The ENQ was issued by SETPRT processing. |
| X'1C' | More than one DCB is open for the SYSOUT data set. |