Return code 90 indicates that a processing error occurred. This return code has a trace facility that lets you determine the cause of the processing error. This facility is enabled during SOLVE SSI setup.
When you issue a PPI call, processing messages from the receiver program are written as WTOs to your system console. If tracing is enabled, and a return code of 90 is recorded in register 15, register 0 records debugging information which is also sent to the system console. This additional information can be used by you to debug the processing error.
Note: For more information about PPI parameters, see the SOLVE Subsystem Interface Guide.
Register 0 contains the debugging information as follows:
X'rrrrmm5A'
Is the reason code of the debugging information, in signed hexadecimal, length 2 bytes. For example, a reason code of 10 would be X'000A' and -141 would be X'FF73'.
Is the module identification of the debugging information in hexadecimal. For example, 35 would be X'23'.
Is 90 in hexadecimal, which indicates that the debugging information has been set in R0.
Following is the resulting message format that you receive on the system console:
NS3580 PPI RC=90 MOD=aa REAS=bbbbbb - RPB FOLLOWS... NS3581 RPB +nnn xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx NS3581 ... (for total RPB length) NS3582 *END*
The fields in the messages are:
Contains the module identification of the debugging information, in decimal. For example, MOD=35.
Contains the (signed) reason code of the debugging information, in decimal. For example, REAS=-00121.
Contains the offset, in hexadecimal, of the start of the hexadecimal dump of the RPB (up to 16 bytes is dumped per line).
8 hexadecimal digits representing RPB data.