Z Abend Investigator messages

These messages are issued by Z Abend Investigator.

HFZ0001I   Z Abend Investigator version-info invoked by exit-name using config-member

Explanation

Z Abend Investigator was invoked for real-time analysis. In the message text:
  • version-info provides information about the version of Z Abend Investigator used and the current maintenance level.
  • exit-name identifies the exit which invoked Z Abend Investigator.
  • config-member is the data set and member name containing the parmlib configuration options, or indicates the use of default options if no configuration member could be found.

System action

Normal processing continues.

User response

None

HFZ0002I   analysis-summary

Explanation

Fault analysis has completed. In the message text, analysis-summary provides a brief summary of the problem.

The analysis summary is typically presented in the format:
  • [point-of-failure:] symptom
where:
point-of-failure
The point in the user application at which the error occurred, or where control left the user application prior to the error. If available, module name, program or CSECT name, offset, and source line number or compiler listing statement number is provided.
symptom
The type of error that occurred (for example, the initial abend code).

System action

Normal processing continues.

User response

None

HFZ0003I   Fault ID faultid assigned in history file history-file-name

Explanation

Z Abend Investigator has completed real-time analysis and has assigned the fault identifier faultid in the history file history-file-name to this abend.

System action

Processing has ended.

User response

None

HFZ0004S   The input dump data set data-set-name could not be opened because: reason

Explanation

The dump data set identified by data-set-name could not be opened for reanalysis for the reason that is identified in reason.

System action

Processing terminates.

User response

Correct the data set name and resubmit the job.

HFZ0005S   module-name:line-number Storage allocation for dec-count (X'hex-count') bytes failed - processing terminated

Explanation

An out-of-storage condition has occurred.

System action

Processing terminates.

User response

Specify a larger region size and resubmit the job—see Storage recommendations for more information. If using TSO, specify a larger region size on the logon panel.

Z Abend Investigator deliberately attempts not to use up all available 31-bit storage before issuing this message, as using up all storage might cause MVS™ to use 24-bit storage instead with possibly disastrous consequences for non-terminating address spaces, such as CICS® regions.

HFZ0006E   Open of context data set data-set-name failed because: reason

Explanation

The data set identified by data-set-name could not be opened for the reason that is identified in reason.

The context in which the data set was attempted opened is provided in context. This context might be an associated DDname, or some other description of the type of data set involved.

When reason is in the form of
DYNALLOC error=error-code info=info-code
then refer to z/OS®: MVS Programming: Authorized Assembler Services Guide for information about the error and info codes.
The reasons for some of the more common DYNALLOC info codes are as follows:
Info code
Reason
210
Data set is allocated to another job.
1708
Data set not found.

System action

Processing attempts to continue without the use of this data set.

User response

Determine the reason for the open failure and resubmit the job.

HFZ0007S   GETMAIN failed resource-name rc=return-code

Explanation

An out-of-storage condition has occurred.

System action

Processing terminates.

User response

Specify a larger region size and resubmit the job.

HFZ0008E   CSVINFO error, rc=return-code

Explanation

An error occurred using the CSVINFO service.

System action

Processing terminates.

User response

This might be an internal error. Contact HCL Support.

HFZ0009E   IEWBUFF error

Explanation

An error occurred while using the Binder.

System action

Processing terminates.

User response

This might be an internal error. Contact HCL Support.

HFZ0010E   IEWBIND error function module-name rc=reason-code

Explanation

A call to the MVS Binder program was unsuccessful. In the message text, function identifies the type of function requested, module-name is the module attempted bound, and reason-code is the reason code returned by the Binder.
Note: The value in reason-code is the Binder API reason code. The Binder API reason codes can be found in z/OS: MVS Program Management: Advanced Facilities.

System action

Processing continues but analysis might be incomplete.

User response

This might be an internal error. Contact HCL Support.

HFZ0011S   Abend abend-code occurred in Z Abend Investigator analysis

Explanation

An abend occurred in Z Abend Investigator.

System action

Processing terminates.

User response

This is an internal error. Contact HCL Support.

HFZ0012S   Abend abend-code occurred in abend exit processing,

Explanation

An abend occurred in Z Abend Investigator. This message is followed by message HFZ0013S.

System action

Processing terminates.

User response

This is an internal error. Contact HCL Support. Ensure that the SVC dump written by Z Abend Investigator is kept for later analysis.

HFZ0013S   R15=r15-value PSW=program-status-word DCAPSUB=base-reg-value

Explanation

This message follows message HFZ0012S.

System action

See message HFZ0012S.

User response

See message HFZ0012S.

HFZ0014E   MTRACE error calling IEEMB879 for buffer accumulation, rc=rc.

Explanation

An error occurred during MTRACE processing.

System action

Processing of MTRACE is terminated and information about console messages might be missing in the Fault History file.

User response

This might be an internal error. Contact HCL Support.

HFZ0015W   Message message-number was not found for display

Explanation

An unsuccessful attempt was made to issue the message identified by message-number.

System action

Processing continues.

User response

This is an internal error. Contact HCL Support.

HFZ0016E   Abend abend-code during fault history file OPEN/READ processing

Explanation

During real-time processing, an abend occurred while attempting to OPEN or READ the history file.

System action

Processing continues, however, no fault entry is created and no duplicate counts is updated.

User response

Determine the reason for the abend.

HFZ0018W   Parmlib member read error: reason

Explanation

A problem occurred while attempting to open or read the HFZCNF00 parmlib configuration member. The reason for the error is provided in reason.

System action

Processing continues without the use of the HFZCNF00 parmlib member.

User response

Ensure that an HFZCNF00 member exists in the logical parmlib concatenation, or in the alternative parmlib data set specified via the HFZOPTLM configuration-options module HFZCNF setting. For details, see Customize Z Abend Investigator by using an HFZOPTLM configuration-options module.

HFZ0019W   options-source syntax error on line line-number column column-number: reason

Explanation

A syntax error was encountered while processing options that are specified in options-source, where options-source is one of the following:
Analysis Control user exit
The option was provided by an Analysis Control user exit.
Environment variable _HFZ_OPTS
The option was provided through the _HFZ_OPTS environment variable.
Options line for interactive reanalysis
The option was specified in the "Options line for interactive reanalysis" field on the Interactive Reanalysis Options display, which is shown when selecting "Interactive Reanalysis Options..." from the action bar Options pull-down menu.
PARM field
The option was specified in one of these places:
  • The PARM field of the EXEC card for PGM=HFZDA in a batch reanalysis job.
  • The Options line for batch reanalysis field on the Batch Reanalysis Options display. This field is shown when selecting Batch Reanalysis Options... from the action bar Options pull-down menu.
Parmlib config member
The option was specified in the HFZCNFxx parmlib member, or in a data set and member identified by an HFZCNFUM user-options module.
User options file
The option was specified through the HFZOPTS DDname.

System action

Processing continues.

User response

Correct the error and resubmit your job.

HFZ0020W   options-source contained invalid option option

Explanation

An invalid option was encountered while processing options that are specified in options-source. For the possible values of options-source, see message HFZ0019W.

System action

The option option is ignored and processing continues.

User response

Correct the error and resubmit your job.

HFZ0021W   Allocation failed: DD=ddname DSN=data-set-name RC=return-code Error=error-code Info=info-code

Explanation

Dynamic data set allocation failed.

System action

Processing continues without the data set identified in data-set-name.

User response

Refer to z/OS: MVS Programming: Authorized Assembler Services Guide for information about the return code, error code, and info code.

HFZ0022W   Suboption(s) missing for options-source option option

Explanation

An option with missing required suboptions(s) was encountered while processing options that are specified in options-source. For the possible values of options-source, see message HFZ0019W.

System action

Processing continues with default value for option option.

User response

Correct the error and resubmit your job.

HFZ0023W   Suboption(s) ignored for options-source option option

Explanation

An option in options-source invalidly specified one or more suboptions when no suboptions were allowed. For the possible values of options-source, see message HFZ0019W.

System action

Processing continues with default value for option option.

User response

Correct the error and resubmit your job.

HFZ0024W   Concatenation failed for DSN=data-set-name to DD=ddname RC=return-code Error=error-codeInfo=info-code

Explanation

Dynamic data set concatenation failed.

System action

Processing continues without the data set identified in data-set-name.

User response

Refer to z/OS: MVS Programming: Authorized Assembler Services Guide for information about the return code, error code, and info code.

HFZ0025W   Suboption sub-opt invalid for options-source option option

Explanation

An option in options-source specified one or more invalid suboptions. For the possible values of options-source, see message HFZ0019W.

System action

Processing continues with default value for option option.

User response

Correct the error and resubmit your job.

HFZ0026W   Information retrieval failed for DD=ddname RC=return-code Error=error-code Info=info-code

Explanation

Dynamic allocation information retrieval failed.

System action

Processing continues without the data set identified in data-set-name.

User response

Refer to z/OS: MVS Programming: Authorized Assembler Services Guide for information about the return code, error code, and info code.

HFZ0027E   Fetch/load failed for module module-name

Explanation

An attempt to fetch or load module module-name failed.

System action

Processing continues without module module-name. However, depending on the functionality of the subject load module, processing might be incomplete.

User response

Contact your systems programmer.

HFZ0028W   Error reading user options file

Explanation

An error occurred while reading the user options file via DDname HFZOPTS.

System action

Processing continues without the user options file.

User response

This might be an internal error. Contact HCL Support.

HFZ0029W   options-source options syntax error at offset offset: reason

Explanation

A syntax error was encountered while processing options that are specified in options-source, where options-source is one of the following:
PARM field
This field is the JCL EXEC statement PARM field specified in a job that executes program HFZDA.
Environment variable _HFZ_OPTS
This environment variable is set by the abending application.

System action

Processing continues.

User response

Correct the error and resubmit your job.

HFZ0030W   Allocation to SYSOUT=(class,,form-name) failed: DD=ddname RC=return-code Error=error-code Info=info-code

Explanation

Dynamic allocation of JES spool data set failed.

System action

Processing continues without the DDname identified in ddname.

User response

Refer to z/OS: MVS Programming: Authorized Assembler Services Guide for information about the return code, error code, and info code.

HFZ0031W   Open of DD=ddname failed: reason

Explanation

An unsuccessful attempt was made to open DDname ddname.

System action

Processing continues without the DDname identified in ddname.

User response

Refer to reason for a possible explanation.

HFZ0032W   I/O error writing report: reason

Explanation

An I/O error occurred while writing the analysis report.

System action

Processing continues, however, the analysis report might be missing information.

User response

Refer to reason for a possible explanation.

HFZ0033E   I/O error writing to history-file-dsn: System abend abend-code-reason-code reason-text

Explanation

An I/O error occurred while writing a fault history record to the history file data set shown in history-file-dsn.

System action

Processing continues, however, the history file does not contain information for the current job.

User response

Refer to abend-code, reason-code and reason-text for a possible explanation.

HFZ0034I   Fault analysis skipped due to: reason

Explanation

A job was excluded from fault analysis for the reason that is identified in reason as one of the following:
  • EXCLUDE option specification (FAST)

    A match for the current fault was found during fast Exclude options processing (see Fast Exclude options processing).

  • Parmlib config member Exclude option specification

    An Exclude option that is specified in the HFZCNF00 configuration member matched the current fault attributes. No subsequent Include or Exclude option specifications in a user options file matched, and no attempt was made to override the exclusion by an Analysis Control user exit.

  • User options file Exclude option specification

    An Exclude option that is specified in the HFZOPTS user options file matched the current fault attributes. No attempt was made to override the exclusion by an Analysis Control user exit.

  • Analysis Control user exit request

    No Exclude option specification in either the HFZCNF00 configuration member or the HFZOPTS user options file matched the current fault attributes. Instead, an Analysis Control user exit requested the exclusion.

  • Abend abend-code during options processing

    An abend occurred during real-time options processing.

System action

No fault analysis is performed.

User response

If an abend occurred, and the problem persists, contact HCL Support.

HFZ0035W   No dump records found in data-set-name

Explanation

An attempt was made to read a dump data set during reanalysis, but the dump data set did not contain any data.

System action

Z Abend Investigator attempts to continue without using the dump data set.

User response

Ensure that the correct dump data set was specified to Z Abend Investigator.

HFZ0036E   Abend abend-code during processing of exit-type user exit exit-name--refer to message explanation for problem determination information

Explanation

An abend occurred during execution of a user exit. In the message text, abend-code is the type of abend that occurred, exit-type is the type of user exit that abended, and exit-name is the name of the user exit.

System action

Processing continues but no further calls are made to this exit.

User response

To obtain a dump of this situation for debugging purposes, allocate DDname HFZTRACE to anything other than DUMMY and a dump data set to the abending job using, for example, the following JCL statements:
//HFZTRACE DD SYSOUT=*
//SYSMDUMP DD DISP=SHR,DSN=my.dumpdsn

HFZ0037E   Incomplete fault history file record detected

Explanation

An error occurred when attempting to open a fault entry for reanalysis.

System action

The reanalysis is terminated.

User response

If the problem persists, contact HCL Support.

HFZ0038W   I/O error writing to softcopy book cache: reason

Explanation

An error occurred when attempting to write to the softcopy book cache data set.

System action

Processing continues.

User response

Refer to reason for a possible explanation. If problems persist, delete and reallocate the data set.

HFZ0042W   Dump data set data-set-name with timestamp timestamp might not match current history file fault entry

Explanation

The dump header record timestamp in the dump data set name was either more than five minutes earlier than or more than 35 minutes later than the timestamp recorded in the current history file fault entry.

System action

Processing continues.

User response

Ensure that the dump data set has not been reused or restored with the contents of a dump from another fault.

HFZ0043W   Fetch failed for message module module-name - using language old-language-option instead of new-language-option

Explanation

An attempt to bring a multicultural support message module into storage failed. The load module name identified in module-name is composed of HFZHM followed by the Language option in effect. Either the specified language identifier is unsupported or the load module library in which the module resides was not found in the MVS search path.

System action

The current Language option setting shown in old-language-option is retained.

User response

Ensure that the Language option specifies a supported language identifier (see Language) and that the load module is available to Z Abend Investigator through the normal MVS search path.

HFZ0044I   Current fault is a duplicate of fault ID faultid - the duplicate count is count

Explanation

As the result of the NoDup(NORMAL(hours)) option in effect, Z Abend Investigator determined that the current fault was a duplicate of an existing fault in the same history file. The duplicate count of the existing fault is incremented by one and is displayed as count in the message. Refer to NoDup for the conditions that are used to determine the duplicate fault.

System action

Processing continues. Unless an End Processing user exit is used to change the normal behavior of duplicate fault processing, both the system dump (if any) and the history file entry is suppressed.

User response

None

HFZ0046I   MVS SVC dump registration skipped due to: reason

Explanation

MVS SVC dump registration via the Z Abend Investigator HFZXTSEL post-dump exit was not performed for the reason that is identified in reason as one of the following:
  • Parmlib config member Exclude option specification

    An Exclude option that is specified in the HFZCNF00 configuration member matched the current fault attributes. No subsequent Include or Exclude option specifications in a user options file matched, and no attempt was made to override the exclusion by an Analysis Control (dump registration) user exit.

  • Analysis Control user exit request

    No Exclude option specification in the HFZCNF00 configuration member matched the current fault attributes. Instead, an Analysis Control (dump registration) user exit requested the exclusion.

  • Abend abend-code during options processing

    An abend occurred during options processing.

System action

No fault entry is created.

User response

None

HFZ0047S   HCL Z Abend Investigator internal abend abend-code

Explanation

Z Abend Investigator terminated abnormally with the abend code shown.

This message is equivalent to the HFZ0120S message, but issued under different circumstances.

System action

Processing terminates.

User response

Contact HCL Support.

A dump taken at the time of the HFZ0047S message being issued is required for problem analysis. If no existing recovery fault recording dump is available, one can be obtained by setting the following SLIP trap before recreating the problem:
SL SET,ID=xxxx,MSGID=HFZ0047S,A=SVCD,END

HFZ0048W   Incomplete minidump: Expected expected-pages pages, read read-pages pages

Explanation

During real-time analysis, the number of minidump pages that was expected to be saved in the history file was expected-pages. However, only read-pages was found during reanalysis.

System action

Processing continues.

User response

If read-pages is less than expected-pages, contact HCL Support.

HFZ0049S   Fault ID faultid not found in history file

Explanation

A non-existing fault identifier was specified in the FaultID option.

System action

Processing terminates.

User response

Ensure that the history file that is used contains the fault ID specified in the FaultID option.

HFZ0050S   Fault reanalysis attempted without FaultID or DumpDSN option specified

Explanation

Reanalysis of a fault was attempted but neither the FaultID option, nor the DumpDSN option, was specified. Without either of these, Z Abend Investigator cannot perform fault reanalysis.

System action

Processing terminates.

User response

Specify either the FaultID or the DumpDSN option and retry the reanalysis.

HFZ0052I   count page minidump suppressed from the fault entry being created

Explanation

A minidump consisting of count 4K pages was suppressed by Z Abend Investigator and therefore not written to the history file with the fault entry being created. However, the remainder of the fault entry is still attempted written. The suppression might be due to the maximum number of minidump pages having been exceeded, or a decision made by an invoked End Processing user exit.

System action

Processing continues.

User response

None.

HFZ0053I   Fault history file entry suppressed due to: reason

Explanation

No updates were made to the history file for the current fault. The reason for the suppression is provided in reason as one of the following:
DUMMY history file specification
The HFZHIST DDname was specified as DUMMY
History file ENQ timeout
Z Abend Investigator was unable to serialize on the history file within a set period of time.
History file access error
If a history file open or read failure, it's likely that message HFZ0016E or HFZ0078E was issued prior to this message.
Duplicate fault or End Processing user exit
If duplicate fault detection was the reason, then message HFZ0044I is issued prior to this message. Otherwise, an End Processing user exit requested suppression.
End Processing user exit
During fault entry refresh processing, an End Processing user exit requested suppression.

System action

Processing continues.

User response

Unless the reason for suppression of the fault entry was that it had either been deemed a duplicate, or a user exit had requested suppression, then if the problem persists, the cause of suppression should be investigated. Check if earlier issued messages provide more information, or check if another user or job continues to hold an ENQ against the history file.

HFZ0055E   Z Abend Investigator processing excluded because num MB of 31-bit storage is not currently available

Explanation

Not enough above-the-line storage was available in the region for analysis to be performed.

System action

Processing terminates.

User response

Ensure that at least num MB of above-the-line storage are available in the region to abending jobs that should be analyzed by Z Abend Investigator. The necessary storage can be made available by using the JOB or EXEC JCL statement REGION parameter. See Storage recommendations.
Note:
  • Due to the MVS implementation of the REGION parameter, it might not be sufficient to simply add the required amount of storage to the value in an already specified REGION parameter.
  • For CICS, this entire amount of storage must be provided through the JOB or EXEC JCL statement REGION parameter; not through the EDSALIM parameter.

Although Z Abend Investigator was unable to perform real-time analysis due to storage constraints, recovery fault recording (see Recovery fault recordingRecovery fault recording) is attempted in a non-CICS environment.

HFZ0056E   REXX environment initialization failed, IRXINIT rc=rc reason=reason

Explanation

At attempt to initialize a REXX environment failed. In the message text, rc is the return code and reason is the reason code returned by the REXX initialization routine, IRXINIT. For information about the return and reason codes, see z/OS: TSO/E REXX Reference.

System action

Processing continues. However, no REXX exec user exits are invoked and no diagnostic information is written to the HFZTRACE DDname.

User response

Refer to the description of return and reason codes in z/OS: TSO/E REXX Reference.

HFZ0058W   Allocation of temporary work data set failed: Type=type RC=return-code Error=error-code Info=info-code

Explanation

Dynamic allocation of a temporary work data set failed.

System action

Processing attempts to continue without the data set.

User response

Refer to z/OS: MVS Programming: Authorized Assembler Services Guide for information about the return code, error code, and info code.

HFZ0059W   Logical parmlib concatenation list error: RC=return-code Reason=reason

Explanation

An attempt to use the logical parmlib list service to determine the data sets contained in the logical parmlib concatenation failed.

System action

Processing continues without the use of the HFZCNF00 parmlib member.

User response

Refer to z/OS: MVS Programming: Assembler Services Reference for information about the return and reason codes.

HFZ0061E   Data set organization of history file data-set-name is not PDS or PDSE

Explanation

Z Abend Investigator was invoked using an invalid format history file data set.

System action

Processing continues, but a fault entry cannot be written.

User response

Ensure that the history file is either PDS or PDSE.

HFZ0062W   Error in file data-set-name. reason

Explanation

An error identified in reason occurred when reading data set data-set-name.

System action

Processing attempts to continue.

User response

Message HFZ0062W might be issued for a particular fault entry, or for the $$INDEX member. If message HFZ0062W is issued for the $$INDEX member due to a corrupted HI segment, an attempt will be made to automatically recover the HI segment from the $$BACKUP member when the history file is next updated, for example when a new fault entry is written.

Ensure that the data set identified is a valid history file PDS or PDSE, and if necessary, delete the member in error. However, take care not to delete the $$INDEX member, unless the problem persists, as this deletion might result in the loss of duplicate fault information.

HFZ0063W   Deletion of file data-set-name failed. reason

Explanation

An attempt to delete data set data-set-name failed. The reason is identified in reason.

System action

Processing attempts to continue.

User response

Refer to the identified reason for the failure to delete the data set.

HFZ0064W   CICS Exit command failed. Response=response reason=reason

Explanation

A CICS command failed.

The following table lists the possible response codes:

Table 1. Response codes
Response code Meaning
1 OK
2 Exception
3 Disaster
4 Invalid
5 Kernel error
6 Purged

The reason codes are associated with each command:

Table 2. Reason codes
Reason code Meaning
FREEMAIN
(No applicable reason codes)
GETMAIN
1 Insufficient storage
INQ_APPLICATION_DATA
1 DPL program
2 No transaction environment
3 Transaction domain error
4 Invalid function
5 Abend
6 Loop
7 Inquiry failed
INQUIRE_TRANSACTION
1 No transaction environment
3 Buffer too small
7 Invalid transaction token
37 Abend
39 Loop
START_PURGE_PROTECTION
(No applicable reason codes)
STOP_PURGE_PROTECTION
(No applicable reason codes)
WAIT_MVS
3 Task canceled
4 Timed out

System action

Processing attempts to continue.

User response

Refer to the identified reason for the failure.

HFZ0065W   CICS Exit action failed. Return code=rc

Explanation

An action performed in the CICS invocation exit failed.

System action

Processing attempts to continue.

User response

Refer to the identified action and return code for the failure.

HFZ0066I   CICS Fast No Dup processing for task task-number found duplicate for program-name abend-code fault-id

Explanation

As the result of the NoDup(CICSFAST(…)) option in effect, Z Abend Investigator determined that a CICS transaction abend was a duplicate of a previous CICS transaction abend. Refer to NoDup for the conditions that are used to determine the duplicate fault.

In the message text, fault-id identifies the fault ID of which the current fault was deemed to be a duplicate.

System action

Processing continues without creating a history file entry for the abending CICS transaction.

User response

None.

HFZ0068I   Z Abend Investigator SubTask for token has been executing for num minutes.

Explanation

This message occurs for CICS if a task abend has been running the Z Abend Investigator SubTask for more than 10 minutes and a new CICS task abend is also needing to do Z Abend Investigator SubTask Processing. The condition could occur if CPU utilization on the system is very high preventing the analysis from occurring in a reasonable time, or it could indicate a problem with Z Abend Investigator SubTask processing.

System action

Processing continues.

User response

None.

HFZ0069E   command-name failed. Resp=response-code field=value

Explanation

An unknown error has occurred.

System action

Processing attempts to continue.

User response

Contact HCL Support. If possible, send the joblog.

HFZ0071I   function-name of program program-name (api,concurrency) completed successfully

Explanation

This message is a confirmation that the command that was issued has completed.

System action

Processing terminates.

User response

None.

HFZ0072I   Program program-name is status

Explanation

This message provides the current exit program name and status.

System action

Processing continues.

User response

None.

HFZ0073I   Usage: CFA <Install|Uninstall>

Explanation

The arguments passed to the CFA transaction were incorrect. The message provides the user with a brief reminder of the correct usage.

System action

Processing continues.

User response

None.

HFZ0074E   User not authorized to issue command command-name

Explanation

The user that is associated with the issuing task is not authorized to use this command or is not authorized to access resources in the way required by this command.

System action

The attempted command was not successful.

User response

Ensure that the necessary command authority is provided.

HFZ0075E   HFZXCCEE CICS exit must abort. CICS SOS pending.

Explanation

Not enough storage was available to initiate analysis. This lack of storage might happen during times of high CICS system activity or when multiple CICS transaction abends are being analyzed concurrently by Z Abend Investigator.

System action

Processing terminates.

User response

If the problem did not occur due to high CICS system activity or the analysis of multiple concurrent CICS transaction abends, try increasing the CICS DSA size.

HFZ0076E   A Z Abend Investigator CSVINFO MIPR routine abend occurred

Explanation

An abend occurred during the processing of a CSVINFO macro to retrieve information about a load module.

System action

CSVINFO processing terminates for the load module.

User response

Contact HCL Support.

HFZ0077I   Z Abend Investigator internal diagnostic: text

Explanation

This message is an internal Z Abend Investigator message used to display specific diagnostic information.

System action

Processing continues.

User response

None.

HFZ0078E   Open of fault history file data-set-name failed because: reason

Explanation

The history file that was identified by data-set-name could not be opened for the reason that is identified in reason.

If reason is shown as "DDfopenw() rc=X'800sssrc'", then this reason indicates an abend during open processing, where:
sss
The hexadecimal MVS system abend code.
rc
The associated hexadecimal reason code.

System action

A fault entry might not have been written to the history file.

User response

Determine the reason for the open failure and resubmit the job. Check that the attributes for the file definition are VB LRECL 10000 PDS or PDSE. If the history file is a PDSE that is shared across a sysplex, then refer to Sharing of history files across a sysplex for more information.

HFZ0081I   IEWBIND unusual condition function module-name rc=reason-code

Explanation

An error occurred while using the Binder.

A reason-code of 83000526 indicates an unusual condition encountered for an input module. This condition occurs when a third-party product adds its own management information to a load module. To suppress this message, use Quiet(HFZ0081I).

System action

Processing continues.

User response

The value in reason-code is the Binder API reason code. The Binder API reason codes can be found in z/OS: MVS Program Management: Advanced Facilities.

HFZ0082E   DB2 subsys-id Call Level Interface error: reason

Explanation

An attempt to obtain DB2® information through the DB2 Call Level Interface (CLI) failed for the DB2 subsystem identified by subsys-id. Refer to reason for details about the error.

System action

Processing continues but analysis might be incomplete.

User response

Ensure that the DB2 Call Level Interface is installed and required setup has been performed. An application plan to bind DBRMs to packages must exist. A default application plan can be created using the sample job in member DSNTIJCL of the DB2 SDSNSAMP data set (for further information, see Binding DB2).

If reason is "SQL return code -1 for SQLAllocConnect to DB2 system system-name", then the problem is likely to be resolved by starting the Z Abend Investigator HFZS subsystem as explained in Using the Z Abend Investigator HFZS subsystem.

Included in the message reason is normally the result of calling the SQLError ODBC function, which provides more detailed information about the error. Of particular interest is the 8-digit hexadecimal reason code following the REASON= keyword (for example, REASON=00f30034). The explanation for this reason code can be found in DB2 for z/OS: Codes

HFZ0083E   Z Abend Investigator SVC error: reason

Explanation

An error occurred during the Z Abend Investigator SVC execution. Refer to reason for details about the error.

Intermittent occurrences of this message can be expected since Z Abend Investigator traverses subsystem address spaces without holding any locks.

System action

Processing continues but analysis might be incomplete.

User response

Contact HCL Support if the problem persists. If reason indicates an abend during the Z Abend Investigator SVC execution, an SVC dump should have been written. Retain this dump for diagnostic purposes.

HFZ0084E   Z Abend Investigator Exit and Main task level mismatch

Explanation

An invocation exit was found to be at a different version or maintenance level than the main Z Abend Investigator module, HFZDA.

System action

Processing continues but errors might occur.

User response

Ensure that all Z Abend Investigator modules used are at the same version and maintenance level.

HFZ0085E   Z Abend Investigator purged, detaching subtask TCB

Explanation

An abending CICS task was running Z Abend Investigator when the task was purged by the operator. Z Abend Investigator is detaching its analysis subtask TCB.

System action

Processing terminates.

User response

None.

HFZ0086E   Z Abend Investigator processing excluded because size k of 24 bit storage is not currently available

Explanation

Not enough below-the-line storage was available for analysis to be performed. The size indicates the amount of storage required in kilobytes.

System action

Fault analysis is excluded for the current fault.

User response

Ensure that sufficient below-the-line storage is available. For more information, see Storage recommendations.

Although Z Abend Investigator was unable to perform real-time analysis due to storage constraints, recovery fault recording (see Recovery fault recording) is attempted in a non-CICS environment.

HFZ0087I   size Meg of 31 bit storage could be provided by SETPROG LPA,ADD,MOD(module-list),DSN=LNKLST

Explanation

When analysis could not be performed due to insufficient above-the-line storage, and all required modules of significant size have not yet been loaded into LPA, this message is issued to indicate the region size space savings that could be achieved if loading these modules into LPA. For more information, see Storage recommendations.

Message HFZ0055E precedes this message to indicate the required above-the-line region size that could not be obtained.

System action

Processing terminates.

User response

Ensure that the amount of above-the-line storage indicated in message HFZ0055E is made available. By issuing the SETPROG command provided in the text for this message, the number of megabytes indicated in size can be made available.

HFZ0088E   Z Abend Investigator captured IEWBIND abend abend-code, processing continues

Explanation

While attempting to map CSECTs in a load module, Z Abend Investigator invoked the Binder program which abnormally terminated with the abend code indicated.

The abend code is in the format xxxyyy, where xxx is a 3-digit hexadecimal system abend code and yyy is the 3-digit hexadecimal representation of a 4-digit decimal user abend code.

System action

Processing continues, but module information might be incomplete.

User response

Determine the reason for the Binder failure.

HFZ0089I   Subsystem subsystem-name RC=rc, Rsn=rsn description

Explanation

This message is issued when an unexpected condition occurred in the Z Abend Investigator HFZS subsystem interface.

Included in the message description might be the result of calling the SQLError ODBC function, which provides more detailed information about the error. Of particular interest is the 8-digit hexadecimal reason code following the REASON= keyword (for example, REASON=00f30034). The explanation for this reason code can be found in DB2 for z/OS: Codes

System action

Processing continues, but the analysis might be incomplete.

User response

See if another message, such as HFZ0082E, was also issued, which might help explain the situation.

HFZ0090E   Execution of REXX exec exec-name failed, IRXEXEC rc=return-code

Explanation

This message is issued when the execution of a REXX user exit was unsuccessful.

System action

Processing continues although the execution of the exit failed.

User response

Using HFZTRACE, look for REXX messages explaining the problem. Refer to z/OS: TSO/E REXX Reference for explanation of the return code from IRXEXEC. For rc=20, check that the exec shown in exec-name is available in the HFZEXEC concatenation.

HFZ0091S   GETMAIN failed in HFZXTSEL initial entry

Explanation

Not enough storage was available for execution of the HFZXTSEL MVS post-dump exit.

System action

Dump registration processing is terminated.

User response

None.

HFZ0092S   condition exceeded, the subtask is canceled

Explanation

In the message text, condition might be one of the following:
Short term interval
Environment checking did not complete within the imposed time limit. This check is performed prior to commencing the real-time fault analysis, and the time limit having been exceeded is likely indicative of environmental problems that might otherwise have caused significant delays or hangs during the analysis.
Time for HFZDA execution
Real-time analysis did not complete within the maximum amount of time permitted. The time limit is automatically adjusted based on elapsed time at various checkpoints during the analysis.

System action

Processing is terminated.

User response

Contact HCL Support if the problem persists.

For problem analysis, a dump that was taken when the HFZ0092S message was issued is required. If no existing recovery fault recording dump is available, one can be obtained by setting the following SLIP trap before recreating the problem:
SL SET,ID=xxxx,MSGID=HFZ0092S,A=SVCD,END

To disable the Z Abend Investigator wait and loop protection feature for other than short term interval conditions (see "Short term interval" above), the NoLoopProtection option can be used. For details, see LoopProtection.

HFZ0093W   Binder processing stopped because num meg of 31 bit storage is not currently available

Explanation

Not enough above-the-line storage is available for successful execution of the Binder.

System action

Binder processing is terminated, but Z Abend Investigator analysis continues.

User response

If possible, increase the available 31-bit region size and retry.

HFZ0094W   Binder processing stopped because num k of 24 bit storage is not currently available

Explanation

Not enough below-the-line storage is available for successful execution of the Binder.

System action

Binder processing is terminated, but Z Abend Investigator analysis continues.

User response

If possible, increase the available 24-bit region size and retry.

HFZ0095W   Unexpected condition found in source-location description

Explanation

A condition was encountered which should be reported to HCL Support.

System action

Processing continues.

User response

Contact HCL Support.

HFZ0096S   CICS Task task-id was force purged by an operator while state fault analysis

Explanation

Analysis of a CICS transaction fault has been terminated by operator intervention.

In the message text, task-id identifies the task that was force purged, and state might be either "waiting for" or "performing" to indicate the fault analysis activity that was terminated.

System action

Processing terminates.

User response

None.

HFZ0097W   Unsupported REXX execution environment detected - no REXX services available

Explanation

The protection key of the job-step TCB was found to be set to a key other than 8. Since this environment is an environment which is not supported by REXX, then no REXX services are available during the fault analysis. This lack of services includes any calls to REXX user exits and all output to the HFZTRACE DDname.

System action

Processing continues without REXX services.

User response

None.

HFZ0098S   Exit exit-name NOT installed, Z Abend Investigator SVC not found

Explanation

The Z Abend Investigator invocation exit, identified in exit-name), was attempted installed. However, since the Z Abend Investigator SVC has not yet been installed, processing is terminated.

System action

Processing terminates.

User response

Install the Z Abend Investigator SVC (see step 4) and retry.

HFZ0099S   transaction-id transaction cannot be used, Z Abend Investigator SVC not found

Explanation

The Z Abend Investigator CFA transaction (which might be called by another name, identified in transaction-id) was attempted used. However, since the Z Abend Investigator SVC has not yet been installed, processing is terminated.

System action

Processing terminates.

User response

Install the Z Abend Investigator SVC (see step 4) and retry.

HFZ0100S   Z Abend Investigator not available, Z Abend Investigator SVC not found

Explanation

Z Abend Investigator was attempted invoked without the Z Abend Investigator SVC having been installed.

System action

Processing terminates.

User response

Install the Z Abend Investigator SVC (see step 4) and retry.

HFZ0101I   Z Abend Investigator processing skipped due to CICSDUMPTABLEEXCLUDE option. Abend code abend-code

Explanation

Analysis of a CICS transaction fault has been excluded as the result of using the CICSDumpTableExclude option. For details of this option, see CICSDumpTableExclude.

System action

Processing terminates.

User response

None.

HFZ0102S   Z Abend Investigator processing terminated due to inappropriate execution environment

Explanation

An abend occurred while checking the execution environment prior to commencing fault analysis.

System action

Processing terminates.

User response

Contact HCL Support if the problem persists.

HFZ0103I   Binder processing of member member-name from data-set-name received a 'not found' condition.

Explanation

A call to the MVS Binder program was unsuccessful.

System action

Processing continues, but analysis might be incomplete.

User response

Contact HCL Support if the problem persists.

HFZ0104S   The storage prior and/or after the HFZNDFUE work area has been overwritten - processing terminated.

Explanation

When Z Abend Investigator invokes the HFZNDFUE program exit, it passes a 256-byte work area. On return from HFZNDFUE, Z Abend Investigator has detected that the storage surrounding this work area has been overwritten.

System action

Z Abend Investigator processing is terminated immediately.

User response

Investigate the HFZNDFUE program exit code to determine why the storage has been overwritten.

HFZ0105S   module-name:line-number Storage allocation for dec-count (X'hex-count') bytes failed - processing terminated

Explanation

An invalid request for storage has occurred. This message is similar to message HFZ0005S, but is used for all storage allocation requests involving a negative length.

System action

Processing terminates.

User response

Contact HCL Support.

A dump taken at the time of the HFZ0105S message being issued is required for problem analysis. If no existing recovery fault recording dump is available, one can be obtained by setting the following SLIP trap before recreating the problem:
SL SET,ID=xxxx,MSGID=HFZ0105S,A=SVCD,END

HFZ0106E   ENQ timed out for major-name minor-name held by jobname on system-name

Explanation

The time limit set for an ENQ against the history file, prior to creating a new fault entry, was exceeded. The time limit is approximately 1 minute.

The ENQ resource was held by the job jobname on system system-name.

Although a fault entry is not created, an analysis report is still written to HFZREPRT.

System action

Processing continues.

User response

Determine the reason why the ENQ could not be satisfied. This reason might be a TSO/ISPF user who is editing the history file member.

HFZ0107I   transaction-id date time exit status

Explanation

This message is issued whenever the Z Abend Investigator Control Transaction (transaction-id) is used to alter the status of one or more of the CICS exits (identified by exit): XPCABND, XDUREQ, LE Exit, or SDUMP Exit. The status field shows either Uninstalled or Installed.

System action

Processing continues.

User response

None.

HFZ0108I   The HFZS subsystem will not process data-set-name because it is not a PDSE history file.

Explanation

This message is issued by the Z Abend Investigator HFZS subsystem when PARM='UPDINDEX' is used and a history file, which is not a PDSE, is attempted opened. In the message text, data-set-name identifies the history file that cannot be cached in the HFZS subsystem.

For more information about HFZS subsystem caching, see Caching of history file $$INDEX data.

System action

Processing continues, but all I/O to the history file $$INDEX member is performed by the requester (real-time analysis, batch or interactive reanalysis, or Z Abend Investigator ISPF interface).

User response

If you want to use the potential performance improvements that can be realized by having the Z Abend Investigator HFZS subsystem manage the history file $$INDEX member, then a PDSE history file must be used.

HFZ0109E   PC recovery entered psw program-status-word abend=abend-word

Explanation

This message is issued when an error has occurred in the Z Abend Investigator subsystem program call interface.

Immediately following this message are usually extra messages that provide more detailed information about the error. For example:
HFZSSPC PC recovery HFZSSPC=16703250 HFZAMAN=16700000
HFZSSPC R0-R3     00000001 171EAE20 80FF28FE 00000002
HFZSSPC R4-R7     008A6770 008A69E0 008FD0C8 00F7DA00
HFZSSPC R8-R11    00000000 00FF24AC 00000C80 00F7DA00
HFZSSPC R12-R15   00000000 00000000 80FF2A2A 808A69E0
HFZSSPC AR0-AR3   00000000 00000000 00000000 00000000
HFZSSPC AR4-AR7   00000000 00000001 00000000 00000000
HFZSSPC AR8-AR11  00000000 00000001 00000000 00000000
HFZSSPC AR12-AR15 00000000 00000000 00000000 00000000

System action

Processing continues, but the subsystem service that failed might cause unexpected results.

If it is a S102 abend, then this problem can happen if the job or task that was requesting services from the Z Abend Investigator subsystem was canceled before the subsystem request had completed.

User response

Contact HCL Support if the problem persists.

HFZ0111W   Timer for HFZ0092S has expired but the NoLoopProtection option was set, execution continues

Explanation

This message is issued if the loop/wait protection feature interval timer expires, but the NoLoopProtection option is in effect.

System action

Processing continues.

User response

None.

HFZ0112W   db2_name SYSIBM.SYSDBRM access time took num_secs seconds, further HFZS requests for this table suspended for 30 minutes—create index on SYSIBM.SYSDBRM for improved performance

Explanation

This message is issued if the HFZS subsystem attempts to query the SYSIBM.SYSDBRM DB2 catalog table for DB2 subsystem name db2_name exceeded the expected maximum time indicated by the num_secs value. No further attempts to access the SYSIBM.SYSDBRM table on the identified DB2 subsystem is made for 30 minutes.

System action

Processing continues, but some DB2-related information might be missing from the analysis report for the fault that caused this message to be issued, as well as for any subsequent faults involving the same DB2 subsystem.

User response

Create an index on SYSIBM.SYSDBRM for improved performance. For details, see Improving Z Abend Investigator DB2 performance.

HFZ0114W   XMEM POST ABEND S102, requester termination

Explanation

This problem can happen if the job or task that was requesting services from the Z Abend Investigator subsystem was canceled before the subsystem request had completed.

System action

The analysis has already been canceled.

User response

Contact HCL Support if the problem persists.

HFZ0115E   LE enclave abend system-abend-code user-abend-code, execution continues

Explanation

An abend occurred during the fault analysis.

System action

Processing continues.

User response

If the problem persists, contact HCL Support.

HFZ0116E   HFZLANGX abend abend-code, execution continues

Explanation

An abend occurred in the HFZLANGX program.

System action

Processing continues, but source-level information might be incomplete.

User response

If the problem persists, contact HCL Support.

HFZ0117E   ABEND<abend-code> during return POST, request from task jobname job-id may have been canceled

Explanation

An abend occurred in the Z Abend Investigator subsystem POST processing. This abend might have been caused by a CANCEL of the request from the task identified by jobname and job-id.

System action

Processing continues.

User response

If the problem persists, contact HCL Support.

HFZ0118W   CICS task task-number abend abend-code analysis skipped due to max waiting exceeded. CICSFAtasks(max_slots,max_waits)

Explanation

The maximum number of faults allowed to be queued for analysis had already been reached when another fault occurred. This limit is controlled by the CICSFAtasks suboption of the DeferredReport option, and the current values in effect are provided in the message text.

System action

Analysis is skipped, and normal CICS transaction dump analysis needs to be performed (that is, not using Z Abend Investigator).

User response

Unless the maximum values are already in effect, the CICSFAtasks suboption of the DeferredReport option can be used to permit more parallel execution tasks to be used, or to increase the number of faults that are allowed to be waiting for analysis. See DeferredReport.

HFZ0119E   HFZS subsystem request server-id resource-id by jobname job-id has hung and will be canceled

Explanation

The Z Abend Investigator HFZS subsystem has detected that a request has not terminated as expected.

System action

The request is canceled.

User response

If the problem persists, contact HCL Support.

HFZ0120S   HCL Z Abend Investigator internal abend system-abend-code user-abend-code

Explanation

Z Abend Investigator terminated abnormally with either system abend code system-abend-code or user abend code user-abend-code.

This message is equivalent to the HFZ0047S message, but issued under different circumstances.

System action

Processing terminates.

User response

Check for previously issued severe (S-level) Z Abend Investigator messages that might explain the reason for the problem (for example, message HFZ0005S, which indicates a storage shortage problem). If no prior S-level messages were found, contact HCL Support.

HFZ0121I   ImageFast NoDup processing found duplicate of ims_pgm fault_id histfile

Explanation

Z Abend Investigator determined that the current fault was an IMS NoDup(ImageFast(…)) duplicate. (For information about IMS NoDup(ImageFast(…)) duplicate detection, see NoDup.) The earlier occurring fault, of which the current fault was deemed to be a duplicate, is identified by the IMS program name (ims_pgm), the assigned fault ID (fault_id), and the history file data set name (histfile).

System action

Processing continues. No fault analysis is performed, but the duplicate count of the earlier occurring fault is incremented, and the duplicate details recorded for later viewing with the Z Abend Investigator ISPF interface (see Viewing the fault entry duplicate history).

User response

None.

HFZ0122W   User exit HFZALLOC command failed: DD=ddname DSN=data-set-name RC=return-code Error=error-code Info=info-code

Explanation

A REXX user exit issued an HFZALLOC command to dynamically allocate a data set, but the allocation failed.

System action

Processing continues without allocation of the data set identified in data-set-name.

User response

Refer to z/OS: MVS Programming: Authorized Assembler Services Guide for information about the return code, error code, and info code.

HFZ0123S   Processing of abend abend-code terminated due to unsupported execution environment: reason

Explanation

Before or during analysis of the abend shown in abend-code, Z Abend Investigator determined that processing could not proceed for one of the following reasons:
  • SUB=MSTR address space

    The address space was started with SUB=MSTR and does therefore not permit SYSOUT allocations.

  • Not full function address space

    The current address space was found to be a limited function address space, which does not support required system services, such as allocation of data sets.

  • System address space

    The started task was a known system address space for which Z Abend Investigator analysis is not appropriate and likely to fail.

  • Abend in system task

    The abend occurred under an RB for a system task, such as the IEFIIC initiator TCB.

  • JES not available

    The primary subsystem (JES) was found to be not available.

  • Z Abend Investigator invoked during JES shutdown

    Z Abend Investigator determined that JES became unavailable during the processing of an abend.

  • Dynamic Allocation not available

    Required Dynamic Allocation services (SVC 99) were found to be not available for the current task.

  • Owning Job-step TCB is abending

    If the current TCB is not the job-step TCB, and the owning job-step TCB is terminating, then load failures are likely to occur.

  • Abend in resource manager

    A resource manager was active for the current TCB.

  • Concurrent analysis in the address space

    To prevent exhausting system resources, only one TCB in a given address space is allowed to perform Z Abend Investigator abend analysis at a time. When Z Abend Investigator was invoked for the current abend, it was determined that another Z Abend Investigator abend analysis was already active, causing the current analysis to be canceled.

  • SYSZTIOT enqueued by TCB tcb-address

    Z Abend Investigator was invoked to analyze an abend with the SYSZTIOT major name already enqueued by the TCB identified by the address in tcb-address. An example of when this situation might occur is during shutdown of IMS when Z Abend Investigator is invoked for a U0002 abend.

  • TCB Not protect KEY 8 or 9

    Z Abend Investigator was invoked to analyze an abend for a task not running in protect key 8 (non-CICS) or 9 (CICS).

System action

Processing terminates.

User response

Real-time analysis is not possible under these conditions. Z Abend Investigator might still be used to aid with the problem determination by setting a SLIP trap using the MSGID=HFZ0123S and A=SVCD parameters, and then performing analysis of the resulting SVC dump by way of the Z Abend Investigator ISPF interface File menu option 5.

HFZ0124E   HFZS subsystem subtask server-id resource-id has terminated with abend code abend-code

Explanation

A subtask in the Z Abend Investigator subsystem terminated abnormally.

System action

The Z Abend Investigator subsystem subtask is terminated, but is restarted as necessary.

Requester processing continues, but results might be unexpected depending on the type of subsystem request that failed.

User response

If the problem persists, contact HCL Support.

HFZ0125W   HFZS subsystem subtask server-id resource-id has terminated with return code rc

Explanation

A subtask in the Z Abend Investigator HFZS subsystem terminated abnormally.

System action

The HFZS subsystem subtask is terminated, but is restarted as necessary.

Requester processing continues, but results might be unexpected depending on the type of subsystem request that failed.

User response

If the problem persists, contact HCL Support.

HFZ0126I   Recovery fault recording fault ID faultid assigned in history file history-file-name

Explanation

Z Abend Investigator was unable to complete normal real-time analysis, but has created a recovery fault recording fault entry faultid in history file history-file-name. Reanalysis of this fault entry should provide information about the fault that was being analyzed when Z Abend Investigator terminated.

System action

Processing has ended.

User response

None

HFZ0127W   Recovery fault recording failed for job-id. reason

Explanation

Recovery fault recording processing failed for the job identified by job-id and the reason that is identified in reason as one of the following:
  • SDUMP suppressed, capture phase of another SVC dump was in progress.

    SDUMP failed with return code 8 and reason code 2, indicating that an SVC dump was suppressed because the capture phase of another SVC dump was in progress.

  • SDUMP DASD space or overload error.

    SDUMP failed with return code 8 and reason code 3E, indicating that SVC dump is already using the maximum amount of virtual storage (as determined by the installation, using the MAXSPACE parameter on the CHNGDUMP command) to process other dumps.

    Typically, the reason for this condition is a shortage of DASD space.

  • SDUMP rc=return-code reason=reason-code error.

    SDUMP failed with return code return-code and reason code reason-code. Refer to z/OS: MVS Programming: Authorized Assembler Services Reference, Volume 3 (LLACOPY-SDUMPX) for an explanation of these codes.

  • RFR requires the HFZS subsystem to be functioning correctly.

    A situation occurred for which recovery fault recording would normally be performed. However, since the HFZS subsystem was not functioning correctly, recovery fault recording was not possible.

System action

Termination continues.

User response

Perform any appropriate action, depending on the reason that is identified.

To enable recovery fault recording, the HFZS subsystem must be started and be functioning.

HFZ0129W   Recovery fault recording IEATDUMP failure, rc=return-code reason=reason-code dump=data-set-name

Explanation

An error occurred while attempting to write the IEATDUMP data set during recovery fault recording processing. In the message text, return-code and reason-code are the return and reason codes from the IEATDUMP service, while data-set-name is the name of the dump data set attempted written. Refer to the section on IEATDUMP return and reason codes in z/OS: MVS Programming: Assembler Services Reference for an explanation of the problem.

System action

Termination continues.

User response

Perform any appropriate action to resolve the IEATDUMP error.

HFZ0130E   Response from HFZS subsystem task-id1 task-id2 not returned within 2 minutes, request canceled

Explanation

System action

Processing continues, but the canceled subsystem request might affect the expected result.

User response

Determine the reason why the HFZS subsystem is not responding by checking for other messages that might have been issued. Also ensure that the HFZS subsystem has not been prioritized lower than any of the abending tasks for which it might be invoked.

If missing responses are persistent, and no reason can be determined, contact HCL Support.

HFZ0131W   Waiting mins minutes for dsn(mbr) SPFEDIT ENQ owner

Explanation

There was a problem obtaining exclusive access to the history file data set member identified by dsn and mbr. The period waited so far is indicated as a number of minutes in the mins value. If available, the current owner of the ENQ is shown in owner. For example: "held by HFZS on SYS8".

System action

The HFZS subsystem continues to wait for the required data set access.

User response

Determine why the identified data set member is not available for update. A possible reason is that a TSO/ISPF user is editing the member.

HFZ0132W   MaxWaitSeconds of seconds exceeded for transaction transaction (task task), analysis will be skipped

Explanation

The MaxWaitSeconds value in effect for the DeferredReport(CICS(FATasks(…))) option was exceeded. For details about this option, see DeferredReport.

System action

No analysis is performed for the identified CICS transaction.

User response

None.

HFZ0133W   DeferredReport option overridden due to MaxMinidumpPages(max_pages) exceeded by num_pages pages

Explanation

The DeferredReport option was in effect while the MaxMinidumpPages option limit was exceeded.

System action

No minidump is written to the fault entry, but the analysis is still performed and a report is written to both the fault entry and to HFZREPRT.

User response

The following might help to prevent this situation:

HFZ0134E   Z Abend Investigator processing excluded because size k of 24 bit LSQA storage is not currently available

Explanation

The minimum required amount of storage shown as size in kilobytes was not available for the below-the-line LSQA.

System action

Processing is terminated.

User response

None.

HFZ0135E   Recovery fault recording terminating. Severe private storage shortage and no SVC dump access.

Explanation

Not enough storage was available in the private region to perform recovery fault recording processing using the IEATDUMP dump type, and Z Abend Investigator was unable to use the SDUMP dump type due to insufficient access authority. The SDUMP is written from the HFZS subsystem, and is therefore normally able to be used when there is a severe storage shortage in the abending region, which prevents the IEATDUMP from being written.

System action

Processing is terminated without a recovery fault recording fault entry.

User response

If possible, resubmit with a larger region size, or provide the necessary access authority to use the SDUMP dump type instead (see SDUMP recovery fault recording data sets).

HFZ0136W   Recovery fault recording IEATDUMP not taken because NULLFILE has been selected for the DSN

Explanation

Recovery fault recording processing was unable to write an IEATDUMP data set due to no eligible data set name having been determined.

System action

Processing is terminated.

User response

None.

HFZ0137W   I/O Error

Explanation

An error occurred during a data set I/O operation.

System action

Processing continues.

User response

Check for more messages related to this error.

HFZ0138S   No minidump or MVS dump data set is available for reanalysis of history file hist-file fault ID fault-id

Explanation

Batch reanalysis was attempted of a fault entry that did not either include a minidump, or was associated with an existing MVS dump data set. Without one or both of these, reanalysis is not possible.

System action

Processing is terminated.

User response

None.

HFZ0140S   Processing terminated due to data set open error for DDname ddname

Explanation

The open of a data set for a required DDname failed.

Normally, this message is preceded by one or more other messages which provide more detailed information about the error (for example, message HFZ0006E).

System action

Processing is terminated.

User response

Check options specification relating to the identified DDname.

HFZ0141W   Please use MODIFY-STOP for the HFZS subsystem

Explanation

This message is issued if the CANCEL command was used to stop the HFZS subsystem.

The correct way to stop the HFZS subsystem is to use the MODIFY or STOP command:
F name,STOP
or
P name

System action

The HFZS subsystem is stopped.

User response

None.

HFZ0142W   Dispatch delay in HFZS subsystem (Priority=hfzs-priority) exceeded num seconds for jobname job-id (Priority=job-priority)

Explanation

This message is issued if the HFZS subsystem response time exceeded expectations for the requester shown.

System action

Processing continues.

User response

Review the dispatch priority of the HFZS subsystem to ensure that it is not less than that of the job identified by jobname and job-id which was requesting Z Abend Investigator subsystem services.

HFZ0143W   Binder processing stopped because num k of 24 bit LSQA storage is not currently available

Explanation

Not enough 24-bit LSQA storage was available to invoke the Binder.

System action

Processing continues, but source line information might be missing from the analysis report.

User response

None.

HFZ0144E   HFZS subsystem TCB tcb-address detection-location abended abend-code

Explanation

An HFZS subsystem TCB or function abended or detected an error condition.

System action

Processing continues, but information might be missing from the analysis report.

User response

If the problem persists, contact HCL Support. If a fix is not available, set a SLIP trap as follows and provide the dump for analysis:
SL SET,ID=xxxx,MSGID=HFZ0144E,A=SVCD,END

HFZ0145I   message-text

Explanation

This message is used for all status messages that are issued by the HFZS subsystem.

Examples of these messages are:
HFZ0145I HFZSXCFA TCB XCF startup
HFZ0145I HFZS subsystem, HFZSMAIN Started. V9R1M0
         (MVS 2009/02/03)
HFZ0145I Starting Termination.

System action

Processing continues.

User response

None.

HFZ0146I   HFZS subsystem storage use is at percent-value percent of JCL REGION size, running number-of-tasks tasks

Explanation

This message is issued by the HFZS subsystem whenever the amount of storage used exceeds 80% of the maximum available storage, as specified in the JCL REGION parameter, or imposed by default. The message is reissued at intervals while the storage usage remains high, but is not issued if the storage usage drops below 80% again.

System action

Processing continues.

User response

If this message is issued regularly, increase the region size to avoid termination of the HFZS subsystem due to insufficient storage being available.

HFZ0147I   Alter access to XFACILIT HFZ_SDUMP_ACCESS is required for Z Abend Investigator SDUMPs

Explanation

This message is issued by the HFZS subsystem whenever an RFR dump is written, and it is determined that the user ID associated with the abending job does not have ALTER access to the XFACILIT HFZ_SDUMP_ACCESS resource class.

System action

The RFR dump is attempted written as an IEATDUMP instead of an SDUMP.

User response

See SDUMP recovery fault recording data sets for information about how to use SDUMPs for improved recovery fault recording performance.

HFZ0148E   Unable to create an RFR fault entry due to HFZS subsystem NOUPDINDEX option in effect.

Explanation

This message is issued by the HFZS subsystem when an RFR dump is about to be written, but the subsystem was started with the NOUPDINDEX option.

System action

An SDUMP of the problem might still be taken, but it will not be recorded in a fault entry in a history file.

User response

Perform analysis of the SDUMP, if available, to identify the problem. Restart the subsystem with the UPDINDEX option in effect.

HFZ0149W   HFZMAPS dsname has a build YYMMDD=build-date but the required level is required-date. Execution may be incorrect.

Explanation

An incorrect version of the HFZMAPS data set is being used. The data set identified by dsname was built on the date shown in build-date, which did not match the required date for the installed level of Z Abend Investigator in required-date.

System action

Processing continues, but results might not be correct.

User response

Ensure that the data set name that is specified for the HFZMAPS DDname is correct (this name is normally specified using the DataSets option in the HFZCNFxx parmlib member), and contains the current data from the SMP/E target library.

HFZ0150W   No READ access to DDname ddname data set name dsname. This data set will not be used.

Explanation

A data set provided to Z Abend Investigator, either explicitly or implicitly, was found to be inaccessible due to no security server READ access.

System action

Processing continues, but errors might occur if the data set is critical.

User response

Provide the appropriate access to the data set.

HFZ0151W   SDUMP failure reason

Explanation

Recovery fault recording processing or Java™ analysis failed with the reason that is identified in reason as one of the following:
  • SDUMP rc=8 rsn=2 for job jobname. SVC dump suppressed because capture phase of another SVC dump was in progress.
  • SDUMP rc=8 rsn=3E for job jobname. DUMPSERV has used virtual storage MAXSPACE because of dump DASD space shortage or high activity.
  • SDUMP rc=0 rsn=04 for job jobname. DUMPSERV could only take a partial dump. Examine associated IEA* DUMP messages for more detail.
  • SDUMP rc=return-code rsn=reason-code for job jobname.
  • SDUMP requires the HFZS subsystem to be functioning.
See message HFZ0127W for more information about the SDUMP return and reason codes.

This message is issued by the HFZS subsystem.

System action

HFZS subsystem processing continues.

User response

Perform any appropriate action, depending on the reason that is identified.

HFZ0152I   Job jobname SDUMP requested for history-file(fault-id)

Explanation

An SDUMP recovery fault recording dump data set was requested for the job identified by jobname, which is to be associated with fault ID fault-id in history file history-file.

System action

Processing continues.

User response

None.

HFZ0153I   Binder processing terminated for member module-name because it was created with the LINK=NO option

Explanation

A call to the Binder program for load module module-name failed with rc=83000505 due to the use of the LINK=NO linkedit option.

System action

Processing continues without binder information for the identified load module.

User response

None.

HFZ0154W   Configuration-options module module-name found in non-authorized load library and has been ignored

Explanation

The load module identified by module-name, which can be used to provide configuration-options for Z Abend Investigator, was found in a load library which was not APF-authorized. The load module name can be either IPVOPTLM or HFZOPTLM. Because it is a requirement that this load module must be placed in an APF-authorized load library in order to be used, it has been ignored.

System action

Processing continues.

User response

Place the load module in an APF-authorized load library.

HFZ0155W   The user ID in use for the HFZS subsystem does not have an OMVS segment with a HOME path

Explanation

If an HFZJLIB DDname has not been specified in the HFZS subsystem JCL, then Z Abend Investigator instead uses the HFZS subsystem user ID OMVS segment HOME path for work files. In this case, neither an HFZJLIB DDname, nor a HOME path were available.

System action

Processing continues, but without Java analysis support.

User response

Ensure that either the HFZJLIB DDname has been specified in the HFZS subsystem JCL, or that an OMVS segment HOME path exists for the HFZS subsystem user ID.

HFZ0156W   GETMAIN of count bytes from jobname job-id address space failed abend-code, hfzs-module-name history-file-name HFZS subsystem request failed

Explanation

When the HFZS subsystem was returning data, a cross memory GETMAIN for count bytes failed, resulting in abend abend-code. This abend occurred because of storage shortage in the requester address space identified by jobname and job-id.

System action

Processing continues.

User response

If possible, increase the region size of the requester address space to prevent this problem from happening in the future.

HFZ0157I   Z Abend Investigator about to deliberately abend U0777 and take RFR dump due to HFZRFRON DDname

Explanation

When an HFZRFRON DD statement is used, Z Abend Investigator deliberately issues abend U0777 in order to cause a recovery fault recording fault entry to be created. For more information about the use of the HFZRFRON DDname, see Verifying the recovery fault recording setup.

System action

Processing terminates.

User response

None.

HFZ0158W   HFZS subsystem requires restart with STEPLIB containing SMP/E *.SHFZAUT2 to load DLL dll-name

Explanation

Analysis of a Java fault was attempted but failed due to the absence of data set HFZ.SHFZAUTH in the HFZS subsystem STEPLIB concatenation.

System action

Analysis continues but Java information is missing.

User response

Add HFZ.SHFZAUTH to the HFZS subsystem STEPLIB concatenation. For details, see Starting the HFZS subsystem.

HFZ0159I   SDUMP requested for job-id1 will not be taken because of high job-id2 usage of SDUMP

Explanation

The rate of Z Abend Investigator recovery fault recording SDUMPs (SVC dumps) scheduled exceeded the operating system's capacity to handle these, and as a result, the current dump was not taken. In the message text, job-id1 is the JES job ID of the job for which the SDUMP was requested, and job-id2 is one of the following:
  • The same as job-id1, if the SDUMP rate threshold for the current job has been exceeded.
  • "System", if the threshold for all jobs combined has been exceeded.

System action

The recovery fault recording SDUMP is not taken.

User response

Contact HCL Support to determine why a high rate of Z Abend Investigator recovery fault recording SDUMPs were requested. Provide examples of the SDUMPs that were taken shortly before this message was issued for analysis.

HFZ0160I   History file history-file I/O error recovery successful

Explanation

Following an I/O error indicated by message HFZ0033E, Z Abend Investigator was able to reclaim sufficient space in the history file identified by history-file to permit the subsequent successful rewriting of the fault entry.

System action

Processing continues normally.

User response

None.

HFZ0161W   History file history-file I/O error recovery failed: reason

Explanation

An attempt to recover from an I/O error on the history file identified by history-file failed for the reason that is identified by reason:
  • History file is not a PDSE

    I/O error recovery is not available for PDS history files.

  • History file contains 25 or less fault entries

    As for AUTO-space management, fault entries are only implicitly deleted if the history file contains more than 25 fault entries.

  • IGWFAMS error

    Message HFZ0095W is issued immediately prior to this message with error-specific information.

  • Unable to provide the required space

    No more fault entries could be deleted, but the required amount of space had not yet been made available. This lack of required space might be due to fault entries being locked.

  • Recursive I/O error

    An I/O error occurred during the recovery of an earlier I/O error.

System action

Processing continues, but a fault entry is not written to the history file.

User response

One or more of the following might be appropriate:
  • Reallocate the history file with more space.
  • Use the HFZUTIL SetMinFaultEntries control statement to change the history file space management setting with a lesser value than the current setting.
  • Unlock locked fault entries so they can be implicitly deleted.

HFZ0162I   MVS dump taken to extract Java information

Explanation

An MVS dump has been taken for the purpose of performing asynchronous extraction of Java information for the current fault.

System action

Processing continues.

User response

None.

HFZ0164I   Fault ID fault-id created in history file history-file due to reason

Explanation

The batch analysis of an MVS dump data set caused the creation of a new fault entry fault-id in history file history-file due to reason.

The possible values for reason are:
  • GenerateSavedReport option
  • HFZRegisterFaultEntry command

System action

Processing continues.

User response

None.

HFZ0165A   ddname updates available--restart HFZS subsystem with //HFZDOC2 DD statement for HFZ.SHFZDOC2 data set

Explanation

During start-up of the HFZS subsystem, it was determined that one or more updates were available for the VSAM KSDS message and abend code explanation repository, identified by ddname as either HFZVSENU, HFZVSJPN or HFZVSKOR. However, no //HFZDOC2 DD statement had been provided to identify the HFZ.SHFZDOC2 data set containing the updates.

System action

Processing continues without updating the VSAM KSDS.

User response

  1. Add a DD statement in the HFZS subsystem JCL as follows for the HFZ.SHFZDOC2 data set containing the VSAM KSDS updates:
    //HFZDOC2 DD DISP=SHR,DSN=HFZ.SHFZDOC2
  2. Restart the HFZS subsystem.

HFZ0166E   Error processing ddname update member: reason

Explanation

An error occurred while attempting to update the VSAM KSDS message and abend code explanation repository. In the message text:
ddname
Identifies the DDname as either HFZVSENU, HFZVSJPN or HFZVSKOR.
member
The name of the update member in data set HFZ.SHFZDOC2.
reason
A description of the error which occurred.

System action

Processing continues, but the VSAM KSDS update is incomplete and is attempted again next time the HFZS subsystem is started.

User response

If the problem persists, contact HCL Support.

HFZ0167I   Models processing for CICS release returned count offsets

Explanation

Under CICS, Z Abend Investigator needs certain release dependent field offset values. These offsets are determined when Z Abend Investigator is installed during CICS startup, and this message gives a count of the number of offsets found.

System action

Processing continues.

User response

None.

HFZ0168E   Models processing for CICS release returned 0 offsets

Explanation

Under CICS, Z Abend Investigator needs certain release dependent field offset values. This message is issued when the processing has failed to determine any offset information. This failure prevents Z Abend Investigator operation under CICS.

System action

Z Abend Investigator operation under CICS is not possible without the offset information.

User response

The offset information is extracted from the SHFZMAPS data set member HFZMCICS. Ensure that the HFZMAPS DataSets option has been specified correctly. If the problem persists, set a SLIP trap on this message number and contact HCL Support.

HFZ0169E   Module module-name loaded from library-name is not APF authorized or the concatenation is not APF authorized

Explanation

It is a requirement that the Z Abend Investigator load module, identified by module-name, is executed from an APF-authorized load library. In this case, the load module was executed from the load library identified by library-name, which was either not APF-authorized, or was included in a JOBLIB or STEPLIB concatenation along with one or more other load libraries which were not APF-authorized.

System action

Processing terminates.

User response

Ensure library-name is APF-authorized and not included in a concatenation with other load libraries which are not APF-authorized.

HFZ0170W   Unable to update data-set-name due to no UPDATE access

Explanation

This message is issued by the Z Abend Investigator HFZS subsystem if updates are available for the message and abend code explanation repository data set identified by data-set-name but the HFZS subsystem does not have UPDATE access to this data set. The updates might be to correct formatting issues or typos in existing explanations, or to add new messages or abend codes.

System action

Processing continues without performing the update.

User response

To perform the update, first grant UPDATE access to data-set-name by the HFZS subsystem, then stop and restart the HFZS subsystem.

HFZ0171W   Waiting count minutes for history-file-name PDSE cross-system SHARING contention

Explanation

This message is issued by the Z Abend Investigator HFZS subsystem if access to a history file is taking longer than one minute to be obtained, and is issued every minute thereafter until the access has been obtained.

System action

Processing of the history file is suspended until the access is obtained.

User response

If the problem persists, determine who is holding an ENQ on the history file using the SPFEDIT major name.

HFZ0172I   Z Abend Investigator NameToken anchor built at storage-addr by TCB tcb-addr

Explanation

This message is issued during Z Abend Investigator initialization under CICS. Its purpose is to provide diagnostic aid for HCL in case of errors.

System action

Processing continues normally.

User response

None.

HFZ0173I   Z Abend Investigator system DUMP call already issued for Fault Entry fault-id

Explanation

During recovery fault recording (RFR) processing, the fault entry identified by fault-id was found to already have had a system dump call issued for it. Hence, an extra system dump call is not issued.

System action

Processing continues normally.

User response

None.

HFZ0174I   Z Abend Investigator Java DUMP fault entry written to history-file1(fault-id) because HFZS subsystem cannot write to history-file2

Explanation

The Z Abend Investigator HFZS subsystem was unable to write a Java dump fault entry to history file history-file2 because of insufficient access authorization. Instead, the fault entry fault-id was written to the default history file history-file1.

System action

Processing continues normally.

User response

None.

HFZ0175I   Z Abend Investigator DUMP analysis will use dump-dsn for history-file(fault-id)

Explanation

This message is issued by the HFZS subsystem when the dump data set identified by dump-dsn has been determined to belong to the fault entry identified by history-file(fault-id). The fault entry is updated to add the associated dump data set name.

System action

Processing continues normally.

User response

None.

HFZ0177E   Java DTFJ processing failed for history-file(fault-id)

Explanation

Expected Java information was not found during reanalysis of fault entry fault-id in history file history-file. This message suggests that Java DTFJ processing failed to complete successfully.

System action

Processing continues normally, but without Java information.

User response

Determine the reason why DTFJ processing failed. Ensure the MVS post-dump exit HFZXTSEL is installed (for details, see Installing the MVS post-dump exit HFZXTSEL) and the HFZS subsystem is started (for details, see Using the Z Abend Investigator HFZS subsystem).

HFZ0178E   Z Abend Investigator startup has hung. RFR dump initiated to capture the abend.

Explanation

A hang was detected while attempting to perform real-time analysis.

System action

The real-time analysis is terminated and a recovery fault recording fault entry is written instead.

User response

If the problem persists, contact HCL Support.

HFZ0179W   Process error trying to force side-file-type side-file use for program-name. The side-file will not be used.

Explanation

The "Listing/Side File Mismatch" prompt, "ENTER" key action could not successfully process the side file.

System action

Processing continues without compiler listing or side file support for the program.

User response

If required, check the compile date and the reasons listed for the mismatch, and locate a compiler listing or side file that is a better match for the program.

HFZ0180I   Z Abend Investigator processing skipped due to CICSDUMPTABLEEXCLUDE( CheckMaxCurr). Abend code abend-code.

Explanation

A CICS transaction dump table entry exists for abend-code and the current dump count exceeds the maximum setting. Due to the CICSDUMPTABLEEXCLUDE(CheckMaxCurr) option being specified, Z Abend Investigator analysis is skipped.

System action

Processing terminates.

User response

None

HCL0181W   HFZS now stopping and restarting tasks to conserve storage. Increase REGION size and restart.

Explanation

Z Abend Investigator has detected a Short on Storage condition within the subsystem. The subsystem is stopping and restarting the HFZS DB2 subtasks when necessary to try to alleviate the condition.

System action

Processing continues.

User response

If this message is regularly issued by the HFZS subsystem, then it is recommended to increase the region size to avoid termination of the HFZS subsystem due to insufficient storage being available.

HFZ0182I   Z Abend Investigator subsystem error from HFZSAREQ: error_message

Explanation

A message was passed back from the Z Abend Investigator HFZS subsystem due to an unexpected condition. The passed-back message in error_message usually includes a separate message ID.

System action

Processing continues.

User response

Refer to the message ID in error_message for the problem that occurred in the Z Abend Investigator HFZS subsystem call.

HFZ0183W   No trace records found in data_set_name

Explanation

Mapping of an auxiliary CICS trace data set in data_set_name was requested.

System action

The trace mapping is terminated.

User response

Ensure the data set specified is correct.

HFZ0184W   Unable to allocate extended minidump data set data_set_name: reason

Explanation

An attempt to allocate the extended minidump data set named in data_set_name failed for the reason shown in reason.

System action

Processing continues, but no extended minidump data set will be associated with the fault entry.

Below-the-bar XDUMP storage pages will be converted to minidump pages, unless the total number of minidump pages exceeds the MaxMinidumpPages option in effect. If this is the case, all storage pages that were destined for the XDUMP data set will be discarded.

User response

Address the reason shown in the message.

HFZ0187I   Associated dump data set data_set_name not deleted due to insufficient access authorization; dump data set type: dump-type, history file hist-file, fault ID: fault-id, created by jobname: jobname, user ID: user-id, security server default group ID group-id

Explanation

A fault entry was deleted by automatic history file space management during real-time analysis, fault entry creation following interactive MVS dump analysis, or HFZUTIL batch utility IMPORT processing.

An attempt was made to also delete the associated data set. However, due to insufficient access authorization, the associated dump data set identified by data-set-name could not be deleted.

System action

Processing continues.

User response

Manually delete the identified dump data set.

From the information that is provided in this message, determine if security server access authorization to dump data sets of this type should be changed to allow for their automatic deletion along with their associated fault entries.

Additional information, depending on dump-type:

HFZ0188I   SNAPDATA parameter ignored: text

Explanation

An error in the HFZSNAP SNAPDATA parameter was detected. text contains additional information about the error.

System action

Processing continues.

User response

Refer to text for a possible explanation and then correct the problem.

HFZ0189W   XDUMP data set data_set_name cannot be analyzed separately from its associated fault entry - perform reanalysis of history file history_file_name fault ID fault_id instead

Explanation

data_set_name was selected for analysis as a dump data set, for example from the Fault Entry List display using the File menu option 5. Because the data set is an XDUMP data set, it cannot be analyzed in this manner.

System action

The dump analysis is terminated.

User response

Perform reanalysis of the history file and fault entry in history_file_name and fault_id instead.

HFZ0191W   History file history-file has been created without a secondary space allocation

Explanation

The HFZS subsystem detected that the history-file data set is allocated without secondary space.

System action

Processing continues.

User response

Z Abend Investigator space management is designed to work effectively with secondary space allocations. See Allocating secondary space for history files, and consider reallocating the history file, as described in Changing the size of a PDSE history file.

HFZ0192I   Dump data set data_set_name not deleted timestamp: reason

Explanation

Z Abend Investigator could not delete the data_set_name dump data set associated with the deleted fault entry. The timestamp indicates the time when the associated fault entry was deleted. At this time, the data_set_name dump data set was migrated, and an asynchronous process attempted to delete it. The reason indicates the reason deletion failed.
This message is issued once for each dump data set that could not be deleted. The time when the message is issued depends on the reason, and might occur at one of the following points:
  • At the time when the associated fault entry is deleted.
  • When the HFZS subsystem checks for undeleted dump data sets at regular intervals.
  • When stopping the HFZS subsystem.

System action

Processing continues.

User response

Delete the dump data set, either manually or by automated operations. Failure to do so leaves the unused data set orphaned.

Refer to reason for the reason why the deletion failed, or check the SYSLOG for other messages that might have been issued around the time shown in timestamp.