Fault Analyzer messages

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

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

An out-of-storage condition has occurred.

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.

DYNALLOC error=error-code info=info-code

An out-of-storage condition has occurred.

An error occurred using the CSVINFO service.

An error occurred while using the Binder.

An abend occurred in Fault Analyzer.

An abend occurred in Fault Analyzer. This message is followed by message IDI0013S.

This message follows message IDI0012S.

An error occurred during MTRACE processing.

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

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

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

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

Dynamic data set allocation failed.

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 IDI0019W.

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 IDI0019W.

Dynamic data set concatenation failed.

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

Dynamic allocation information retrieval failed.

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

If module-name is IPVLANGX or IPVLANGP (or their aliases IDILANGX or IDILANGP), then these modules are provided by ADFz Common Components and must be available via LINKLIST or LPA. See Making Fault Analyzer modules available for details.

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

Dynamic allocation of JES spool data set failed.

An unsuccessful attempt was made to open DDname ddname.

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

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

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

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.

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

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

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.

An attempt to bring a multicultural support message module into storage failed. The load module name identified in module-name is composed of IDIHM 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.

As the result of the NoDup(NORMAL(hours)) option in effect, Fault Analyzer 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.

Fault Analyzer terminated abnormally with the abend code shown.

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

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.

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

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

A minidump consisting of count 4K pages was suppressed by Fault Analyzer 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.

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

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.

Dynamic allocation of a temporary work data set failed.

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

Fault Analyzer was invoked using an invalid format history file data set.

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

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

A CICS® command failed.

The following table lists the possible response codes:

The reason codes are associated with each command:

An action performed in the CICS® invocation exit failed.

As the result of the NoDup(CICSFAST(…)) option in effect, Fault Analyzer 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.

This message occurs for CICS® if a task abend has been running the Fault Analyzer SubTask for more than 10 minutes and a new CICS® task abend is also needing to do Fault Analyzer 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 Fault Analyzer SubTask processing.

An unknown error has occurred.

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

This message provides the current exit program name and status.

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

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.

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 Fault Analyzer.

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

This message is an internal Fault Analyzer message used to display specific diagnostic information.

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

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(IDI0081I).

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.

An error occurred during the Fault Analyzer SVC execution. Refer to reason for details about the error.

Intermittent occurrences of this message can be expected since Fault Analyzer traverses subsystem address spaces without holding any locks.

An invocation exit was found to be at a different version or maintenance level than the main Fault Analyzer module, IDIDA.

An abending CICS® task was running Fault Analyzer when the task was purged by the operator. Fault Analyzer is detaching its analysis subtask TCB.

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

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 IDI0055E precedes this message to indicate the required above-the-line region size that could not be obtained.

While attempting to map CSECTs in a load module, Fault Analyzer 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.

This message is issued when an unexpected condition occurred in the Fault Analyzer IDIS 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

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

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

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

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

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

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.

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 IDITRACE DDname.

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

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

Fault Analyzer was attempted invoked without the Fault Analyzer SVC having been installed.

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

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

A call to the MVS™ Binder program was unsuccessful.

When Fault Analyzer invokes the IDINDFUE program exit, it passes a 256-byte work area. On return from IDINDFUE, Fault Analyzer has detected that the storage surrounding this work area has been overwritten.

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

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 IDIREPRT.

This message is issued whenever the Fault Analyzer 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.

This message is issued by the Fault Analyzer IDIS 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 IDIS subsystem.

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

This message is issued when an error has occurred in the Fault Analyzer subsystem program call interface.

IDISSPC PC recovery IDISSPC=16703250 IDISAMAN=16700000
IDISSPC R0-R3     00000001 171EAE20 80FF28FE 00000002
IDISSPC R4-R7     008A6770 008A69E0 008FD0C8 00F7DA00
IDISSPC R8-R11    00000000 00FF24AC 00000C80 00F7DA00
IDISSPC R12-R15   00000000 00000000 80FF2A2A 808A69E0
IDISSPC AR0-AR3   00000000 00000000 00000000 00000000
IDISSPC AR4-AR7   00000000 00000001 00000000 00000000
IDISSPC AR8-AR11  00000000 00000001 00000000 00000000
IDISSPC AR12-AR15 00000000 00000000 00000000 00000000

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

This message is issued if the IDIS 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.

An error occurred while performing interactive reanalysis under CICS®. This error might be caused by an abend, or by an incomplete setup of the interactive reanalysis component under CICS® (see Performing interactive reanalysis under CICS).

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

An abend occurred during the fault analysis.

An abend occurred in the IDILANGX program.

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

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.

The Fault Analyzer IDIS subsystem has detected that a request has not terminated as expected.

Fault Analyzer terminated abnormally with either system abend code system-abend-code or user abend code user-abend-code.

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

Fault Analyzer 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).

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

A subtask in the Fault Analyzer subsystem terminated abnormally.

A subtask in the Fault Analyzer IDIS subsystem terminated abnormally.

Fault Analyzer 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 Fault Analyzer terminated.

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.

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 IDIS on SYS8.

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

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

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

Not enough storage was available in the private region to perform recovery fault recording processing using the IEATDUMP dump type, and Fault Analyzer was unable to use the SDUMP dump type due to insufficient access authority. The SDUMP is written from the IDIS 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.

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

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

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.

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 IDI0006E).

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

F name,STOP

P name

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

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

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

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

IDI0145I IDISXCFA TCB XCF startup
IDI0145I IDIS subsystem, IDISMAIN Started. V9R1M0
         (MVS 2009/02/03)
IDI0145I Starting Termination.

This message is issued by the IDIS 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.

This message is issued by the IDIS 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 IDI_SDUMP_ACCESS resource class.

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

An incorrect version of the IDIMAPS 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 Fault Analyzer in required-date.

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

This message is issued by the IDIS subsystem.

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.

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.

The load module identified by module-name, which can be used to provide configuration-options for Fault Analyzer, was found in a load library which was not APF-authorized. The load module name can be either IPVOPTLM or IDIOPTLM. 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.

If an IDIJLIB DDname has not been specified in the IDIS subsystem JCL, then Fault Analyzer instead uses the IDIS subsystem user ID OMVS segment HOME path for work files. In this case, neither an IDIJLIB DDname, nor a HOME path were available.

When the IDIS 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.

When an IDIRFRON DD statement is used, Fault Analyzer 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 IDIRFRON DDname, see Verifying the recovery fault recording setup.

Analysis of a Java™ fault was attempted but failed due to the absence of data set IDI.SIDIAUT2 in the IDIS subsystem STEPLIB concatenation.

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

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

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.

During start-up of the IDIS 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 IDIVSENU, IDIVSJPN or IDIVSKOR. However, no //IDIDOC2 DD statement had been provided to identify the IDI.SIDIDOC2 data set containing the updates.

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

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

It is a requirement that the Fault Analyzer 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.

This message is issued by the Fault Analyzer IDIS subsystem if updates are available for the message and abend code explanation repository data set identified by data-set-name but the IDIS 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.

This message is issued by the Fault Analyzer IDIS 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.

This message is issued during Fault Analyzer initialization under CICS®. Its purpose is to provide diagnostic aid for IBM in case of errors.

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.

The Fault Analyzer IDIS 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.

This message is issued by the IDIS 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.

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.

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

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

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, Fault Analyzer analysis is skipped.

Fault Analyzer has detected a Short on Storage condition within the subsystem. The subsystem is stopping and restarting the IDIS DB2® subtasks when necessary to try to alleviate the condition.

A message was passed back from the Fault Analyzer IDIS subsystem due to an unexpected condition. The passed-back message in error_message usually includes a separate message ID.

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

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

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.

• Execution abend abend_code
• Found in non-authorized load library
• LOAD abend abend_code-reason_code
• LOAD error R15=load_reason_code
• CSVQUERY error R15=csvquery_reason_code