Start of change

HZSLPDRD Output variables

The following REXX variables are returned by HZSLPDRD:
Table 1. HZSLPDRD output variables
Variable name Description
HZSLPDRD_RSN The reason code explaining a return code of 8 or more. The reason codes are as follows:
nnnn0881
Meaning: HZSPREAD reported an error.

Action: See the reason code for macro service HZSPREAD as indicated by the first half (“nnnn”) of HZSLPDRD_RSN.

xxxx0882
Meaning: HZSLPDRD_IPL was not valid.

Action: Make sure that variable HZSLPDRD_IPL has been set to a valid value.

xxxx0883
Meaning: HZSLPDRD_INSTANCE was not valid.

Action: Make sure that variable HZSLPDRD_INSTANCE has been set to a valid value.

xxxx0884
Meaning: HZSLPDRD_STARTBYTE was not valid.

Action: Make sure that variable HZSLPDRD_STARTBYTE has been set to a valid value, or let it default to zero.

xxxx0885
Meaning: HZSLPDRD_DATALEN was not valid.

Action: Make sure that variable HZSLPDRD_DATALEN has been set to a valid value, or let it default to its maximum.

xxxx0886
Meaning: HZSLPDRD_CHECKOWNER was not valid.

Action: Make sure that variable HZSLPDRD_CHECKOWNER has been set to a valid check owner name (only alphanumeric and national characters and the underscore ('_') character are allowed).

xxxx0887
Meaning: HZSLPDRD_CHECKNAME was not valid.

Action: Make sure that variable HZSLPDRD_CHECKNAME has been set to a valid check name (only alphanumeric and national characters and the underscore ('_') character are allowed).

xxxx0C16
Meaning: The HZSLPDRD function has been invoked by a non-SYSREXX caller.

Action: Ensure that HZSLPDRD is only called from a REXX health check routine.

xxxx0C17
Meaning: The HZSLPDRD function has been invoked without an EvalBlock.

Action: Ensure that HZSLPDRD is invoked as a regular function in a REXX health check routine.

 
nnnn0C81
Meaning: HZSPREAD reported an error.

Action: See the reason code for macro service HZSPREAD as indicated by the first half (“nnnn”) of HZSLPDRD_RSN.

xxxxrryy with rr = “10” or higher
Meaning: An unexpected error occurred while executing function HZSLPDRD.

Action: Retry the service. If HZSLPDRD continues to fail, obtain the value of the REXX variables HZSLPDRD_RSN and HZSLPDRD_SYSTEMDIAG and contact IBM service.

HZSLPDRD_BUFFER The system will create this variable and set its value to the requested data as found in the persistent data set, up to the length specified via HZSLPDRD_DATALEN. If no data is found, the variable will be of length zero.
HZSLPDRD_BYTESAVAIL The system will create this variable and set its value to the total number of persistent data bytes available for the data record. The returned HZSLPDRD_BUFFER variable might be of a shorter length, depending on what HZSLPDRD_STARTBYTE and HZSLPDRD_DATALEN values were used.
HZSLPDRD_RETIPLTOD The system will create this variable and set its value to the IPL TOD of the persistent data. This timestamp is in STCK format (for example, compare BLSUXTOD to format this as human readable timestamp).
HZSLPDRD_RETPTIME The system will create this variable and set its value to the time the persistent data record as identified on input was written. This timestamp is in STCK format (for example, compare BLSUXTOD to format this as human readable timestamp).
HZSLPDRD_SYSTEMDIAG Additional diagnostic information for non-zero return codes. An ABEND 290 will be issued for additional error cases, with the following hex reason codes:
xxxx0858
Meaning: HZS_HANDLE was not valid.

Action: Make sure that the HZSLPDRD function is only called from a REXX exec called by IBM Health Checker for z/OS. The check must not modify variable HZS_HANDLE. If this function is used within a procedure, make sure you use the EXPOSE option to make HZS_HANDLE accessible to the procedure code.

xxxxrryy with rr = “10” or higher
Meaning: An unexpected error occurred while executing function HZSLPDRD.

Action: Retry the service. If HZSLPDRD continues to fail contact IBM service.

End of change