The IBM Health
Checker for z/OS reason codes
for the 290 abend code and actions that you can use to correct the
problem are:
- 002D
- The HZSCPARS REQUEST=PARSE was issued a second time without freeing
the parse area that was obtained for the first HZSCPARS REQUEST=PARSE
request.
Action: Verify that a HZSCPARS REQUEST=FREE before
a subsequent HZSCPARS REQUEST=PARSE is issued.
- 0035
- The HZSCPARS REQUEST=FREE was requested for an area that does
not match the area returned by REQUEST=PARSE.
Action: Verify
that the HZSCPARS REQUEST=FREE request is passing the matching area.
- 1xxx
- An internal error in the IBM Health
Checker for z/OS component.
Action: Search
problem reporting data bases for a fix to the problem. If no fix is
found, contact the IBM Support
Center. Provide the LOGREC data set and SVC dump, if one is issued.
- 4007
- HZSADDCK could not load the specified check routine.
Action: Make
sure that you specified the proper check routine name. The check routine
module must be in an APF-authorized library. The system must be able
to locate the check routine within the joblib, the steplib of the IBM Health Checker for z/OS address space, the LPA, or the LNKLST.
- 4008
- HZSADDCK could not load the specified message table.
Action: Make
sure that you specified the proper message table name. The message
table module must be in an APF-authorized library. The system must
be able to locate the message table within the joblib, the steplib
of the IBM Health Checker for z/OS address space, the LPA, or
the LNKLST.
- 4009
- HZSADDCK found a message table that is not supported on this release,
or the message table was not created by HZSMSGEN.
Action: Verify
the check and the message table are intended for the release of MVS™ that is active on this system
and that it was created by HZSMSGEN.
- 4016
- The variable defined in the HZSMGB area has a length greater than
the value defined by Maxlen in the message table.
Action: Verify
that you specified the correct length for the variable.
- 4106
- The HZSMGB data area or the HZSMGB data area variable array is
not available or could not be accessed.
Action: Verify that
the input parameter is correct on the HZSFMSG macro.
- 4107
- A variable described in the HZSMGB data area had a bad address
or length.
Action: Verify that you specified the correct
address and length for the variable.
- 4108
- The message number provided in MGB_Id does not exist in the message
table.
Action: Verify that you specified the correct message
ID on the HZSFMSG macro.
- 4109
- The maximum number of variables allowed in a check message is
defined by Mgb_MaxInserts.
Action: Verify that you specified
the correct number of variables on the HZSFMSG macro.
- 410A
- The message table requested a variable that is out of sequence
or too few inserts.
Action: Verify that you specified the
correct variable on the HZSFMSG macro.
- 410B
- The message definition requires a variable that does not exist
in the HZSMGB data area.
Action: Verify that you specified
the correct variable on the HZSFMSG macro.
- 410C
- The HZSMGB data area contained variables that were not requested
in the associated message.
Action: Verify that you specified
the correct variables on the HZSFMSG macro.
- 410D
- A variable described in the HZSMGB data area had a bad address
or length.
Action: Verify that you specified the correct
address and length for the variable on the HZSFMSG macro.
- 410E
- A variable described in the HZSMGB data area had a bad address
or length.
Action: Verify that you specified the correct
address and length for the variable on the HZSFMSG macro.
- 410F
- The HZSFMSG macro parameter was not accessible or not in the caller's
key.
Action: Verify that the parameter list for the HZSFMSG
macro is accessible and in the caller's key.
- 4110
- The HZSFMSG request CHECKMSG requires a valid HZSMGB data area.
Action: Verify
that you specified a valid control block on the HZSFMSG macro.
- 4111
- The HZSFMSG parameter list contained an unsupported version number.
Action: Verify
that you specified the correct version number on the HZSFMSG macro.
- 4112
- The HZSFMSG request was issued by a program that was not a check
routine.
Action: Verify that you did not issue the HZSFMSG
macro from a program that was not a check routine.
- 4113
- The HANDLE parameter issued on the HZSFMSG contained an incorrect
value.
Action: Verify that the HANDLE parameter on the HZSFMSG
request contains a valid value.
- 4114
- The HZSFMSG macro was requested from a remote routine that was
not a check routine.
Action: Verify that the HZSFMSG macro
is issued from a check routine.
- 4115
- The system could not set the ABENDRESULT parameter on the HZSFMSG
macro request.
Action: Verify that the input parameter is
correct on the HZSFMSG macro.
- 4116
- The variable defined in the HZSMGB area has a length greater than
the value defined by Fieldsize in the message table.
Action: Verify
that you specified the correct length for the variable.
- 4117
- The message table supplied by a remote check is not valid.
Action: Verify
that the message table was built via the HZSMSGEN exec and has not
been overlaid.
- 4118
- A remote check issued HZSFMSG other than from the INITRUN or RUN
function.
Action: Verify that HZSFMSG is only issued the
check has gotten control with PQE_Function_code of either PQE_Function_code_Init
or PQE_Function_Code_Check.
- 4FFF
- A check was terminated by DELETE FORCE=YES.
Action: A
DELETE FORCE=YES command was processed, which terminated the specified
checks with this abend reason code.