290

Explanation

The IBM® Health Checker for z/OS® encountered an error. A reason code is displayed along with the 290 abend code. The format of the abend code is cc-mm-rrrr, where rrrr is the halfword reason code.

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:
00xx
An internal error in the IBM Health Checker for z/OS component, unless listed separately below (for example, 002D).

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.

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.

005E
The CPARAREA or CPARAREAADDR parameter is invalid (NULL).

Action: Ensure that you pass a valid CPARAREA or CPARAREAADDR parameter when using HZSCPARS REQUEST=CHECKPARM.

005F
The CPARAREA or CPARAREAADDR parameter is invalid (NULL).

Action: Ensure that you pass a valid CPARAREA or CPARAREAADDR parameter when using HZSCPARS REQUEST=CHECKNOTPROC.

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.

400A
HZSADDCK found an AMODE 64 check routine. AMODE 64 is not supported for local check routines.

Action: Ensure the CHECKROUTINE parameter of HZSADDCK identifies an AMODE 31 check routine.

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.

4119
HZSFMSG was called with an unrecognized REQUEST type.

Action: Specify only supported REQUEST types, such as CHECKMSG, DIRECTMSG, HZSMSG, STOP, or DOM.

4120
HZSFMSG was called with an unrecognized REASON for this particular REQUEST type.

Action: Specify REASONs which are supported for a particular REQUEST type.

4122
HZSFMSG was called with an IDLEN parameter value which is out of range.

Action: Specify IDLEN values in the range 1 - 10.

4123
HZSFMSG was with a TEXTLEN parameter value which is out of range.

Action: Specify a TEXTLEN value in the range 1 - 65535.

4124
HZSFMSG was called with an ID parameter value of NULL.

Action: Specify a valid ID address.

4125
HZSFMSG was called with a TEXT parameter value of NULL.

Action: Specify a valid TEXT address.

412B
HZSFMSG was called with an EXPL parameter value of NULL.

Action: Specify a valid EXPL address.

412C
HZSFMSG was called with an EXPLLEN parameter value which is out of range.

Action: Specify a EXPLLEN value in the range 1 - 65535.

412E
HZSFMSG was called with a SYSACT parameter value of NULL

Action: Specify a valid SYSACT address.

412F
HZSFMSG was called with a SYSACTLEN parameter value which is out of range.

Action: Specify a SYSACTLEN value in the range 1 - 65535.

4130
HZSFMSG was called with an ORESP parameter value of NULL.

Action: Specify a valid ORESP address.

4131
HZSFMSG was called with an ORESPLEN parameter value which is out of range.

Action: Specify an ORESPLEN value in the range 1 - 65535.

4132
HZSFMSG was called with an SPRESP parameter value of NULL.

Action: Specify a valid SPRESP address.

4133
HZSFMSG was called with an SPRESPLEN parameter value which is out of range.

Action: Specify an SPRESPLEN value in the range 1 - 65535.

4134
HZSFMSG was called with a PROBD parameter value of NULL.

Action: Specify a valid PROBD address.

4135
HZSFMSG was called with a PROBDLEN parameter value which is out of range.

Action: Specify a PROBDLEN value in the range 1 - 65535.

4136
HZSFMSG was called with a SOURCE parameter value of NULL.

Action: Specify a valid SOURCE address.

4137
HZSFMSG was called with a SOURCELEN parameter value which is out of range.

Action: Specify a SOURCELEN value in the range 1 - 65535.

4138
HZSFMSG was called with a REFDOC parameter value of NULL.

Action: Specify a valid REFDOC address.

4139
HZSFMSG was called with a REFDOCLEN parameter value which is out of range.

Action: Specify a REFDOCLEN value in the range 1 - 65535.

413A
HZSFMSG was called with an AUTOMATION parameter value of NULL.

Action: Specify a valid AUTOMATION address.

413B
HZSFMSG was called with an AUTOMATIONLEN parameter value which is out of range.

Action: Specify an AUTOMATIONLEN value in the range 1 - 65535.

4140
HZSFMSG was called with REQUEST=DOM for a health check that was added with DOM=SYSTEM.

Action: Only use REQUEST=DOM for health checks that have been added with DOM=CHECK.

4141
HZSFMSG was called with REQUEST=DOM after a first check exception was issued in a check iteration.

Action: Use REQUEST=DOM to remove previous check exception message WTOs only before any check exception messages are issued in a new check iteration.

4150
HZSFMSG was called with a non-SYSTEM SEVERITY or SEVERITYVAL for a health check that was added with ALLOWDYNSEV=NO.

Action: Use a non-SYSTEM SEVERITY or SEVERITYVAL only for a health check that has been added with ALLOWDYNSEV=YES.

4151
HZSFMSG was called with an unsupported SEVERITY special value.

Action: Specify only valid SEVERITY values, such as SYSTEM, NONE, LOW, MED, HI, or VALUE.

4152
HZSFMSG was called with an unsupported SEVERITYVAL parameter value.

Action: Specify only valid SEVERITYVAL values, such as PQE_LowSeverity (=4), PQE_MediumSeverity (=8), PQE_HighSeverity (=12), PQE_NoSeverity (=255), or PQE_SystemSeverity (=0).

4153
REQUEST=HZSMSG REASON=ENVNA is not allowed after an exception message has been issued already in the same check iteration.

Action: The check writer needs to ensure that only one check status is requested by the check routine: "Exception", via sending exception message(s), or "Successful", for example via REQUEST=HZSMSG REASON=ENVNA, but not both.

4154
An exception message (via DIRECTMSG) is not allowed after HZSFMSG REQUEST=HZSMSG REASON=ENVNA has already been issued in the same check iteration.

Action: The check writer needs to ensure that only one check status is requested by the check routine: "Exception", via sending exception message(s), or "Successful", for example via REQUEST=HZSMSG REASON=ENVNA, but not both.

4155
An exception message (via CHECKMSG) is not allowed after HZSFMSG REQUEST=HZSMSG REASON=ENVNA has already been issued in the same check iteration.

Action: The check writer needs to ensure that only one check status is requested by the check routine: "Exception", via sending exception message(s), or "Successful", for example via REQUEST=HZSMSG REASON=ENVNA, but not both.

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.

System action

The system continues.

System programmer response

See the appropriate reason code in the preceding list and correct the error.

Source

IBM Health Checker for z/OS