Abend codes AIxx

AICA
Explanation:

A task has been executing for longer than the runaway time interval (defined by the ICVR operand on the system initialization table macro, DFHSIT) without giving up control. The runaway task condition indicates a possible loop in the application.

System action:

The task is terminated with an AICA transaction dump.

User response:

See the CICS® Problem Determination Guide for guidance on dealing with loops.

Modules:

DFHSRP

AICB
Explanation:

A RETRIEVE WAIT request has been reissued in system shutdown.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

None

Modules:

DFHICP

AICC
Explanation:

An incorrect response was returned from a timer (TI) domain request.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHTAJP, DFHICP

AICD
Explanation:

A incorrect response was returned from a kernel (KE) domain request.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHICP

AICE
Explanation:

An incorrect response was returned from a dispatcher (DS) domain request (other than AICG).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHICP

AICF
Explanation:

An incorrect response was returned from a transaction manager (TM) domain request.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHICP

AICG
Explanation:

A PURGED response was returned from a dispatcher domain (DS) request, with a reason code of TASK_CANCEL. TASK_CANCEL was returned as the transaction had been explicitly cancelled.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Notify your system programmer to determine why the task has been purged.

Modules:

DFHICP

AICH
Explanation:

The task was purged before a request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition will have provided an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. This is either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHICP, DFHEIIC

AICJ
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. The domain that detected the original error will have provided an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related message produced by the domain that detected the original error.

Modules:

DFHICP

AICK
Explanation:

Module DFHEIIC has issued a resource level security check (RSLC) request to module DFHXSRC and received a response other than OK or EXCEPTION.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Examine the trace to find the exception trace entry created by DFHXSRC at the time of the error. Use this trace entry to determine the cause of the return code from DFHXSRC.

Modules:

DFHEIIC

AICL
Explanation:

DFHEIIC detected an invalid function code in the command level parameter list. This is caused either by a storage overwrite or a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 trace of the IC and EI components would aid problem determination. Look in the program storage section of the transaction dump and compare argument 0, the exec interface descriptor (EID), for the command being processed with the argument 0 produced by the translator for the same command. Any differences mean that an overwrite of the application program may have occurred. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHEIIC

AICN
Explanation:

An incorrect response has been returned from a user domain (US) request.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHICP

AICO
Explanation:

An unexpected EXCEPTION response was received from a call to the user (US) domain.

The call was issued during initialization of a transaction that was started without a terminal. The call was made as part of processing to associate the transaction with its intended user. The attempt to associate the intended user with the transaction has failed.

The userid for the intended user of the transaction may not be correctly defined.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Determine why the intended user of the transaction is not correctly defined.

Examine messages produced for the CICS job by the external security manager (ESM). This may require the assistance of a security administrator.

It may be necessary to examine the transaction dump to determine why the external security manager has informed CICS that the user is not correctly defined.

When the user has been correctly defined, consider rerunning the transaction.

Modules:

DFHICXM

Start of change
AICQ
Explanation:

Module DFHDFST is executing at a terminal which is not permitted.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Determine why this transaction is executing at a terminal.

Modules:

DFHDFST

End of change
AICR
Explanation:

A DFHTC write request has failed for IRC. The return codes within TCATPAPR and TCTEIRET should be examined to determine the cause of failure.

System action:

The CSNC transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRR

Start of change
AICS
Explanation:

Module DFHDFST has encountered an error during Retrieve processing.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Use level 1 trace entries to determine the cause of the failure.

Modules:

DFHDFST

End of change
Start of change
AICT
Explanation:

Module DFHDFST has encountered an error during START processing.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Use level 1 trace entries to determine the cause of the error.

Modules:

DFHDFST

End of change
Start of change
AIEA
Explanation:

An unexpected EXCEPTION response was received from a call to the user (US) domain.

The call was issued during initialization of a transaction that was started without a terminal. The call was made as part of processing to associate the transaction with its intended user. The attempt to associate the intended user with the transaction has failed.

The userid for the intended user of the transaction may not be correctly defined.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Determine why the intended user of the transaction is not correctly defined.

Examine messages produced for the CICS job by the external security manager (ESM). This may require the assistance of a security administrator.

It may be necessary to examine the transaction dump to determine why the external security manager has informed CICS that the user is not correctly defined.

When the user has been correctly defined, consider rerunning the transaction.

Modules:

DFHIEXM

End of change
Start of change
AIEB
Explanation:

The transaction id (CIEP) of the ECI for TCP/IP listener task has been initiated invalidly, probably by entering the id at a terminal. This transaction must only be initiated by CICS internal processes.

System action:

The transaction is abnormally terminated.

User response:

Do not initiate CIEP directly.

Modules:

DFHIEP

End of change
Start of change
AIIA
Explanation:

An error occurred in the IIOP Request Processor which prevented it from sending a reply to the Request Receiver.

System action:

The transaction is abnormally terminated.

User response:

The Request Processor will have issued an exception trace and a message.

Examine this information to determine why the Request Processor failed.

Modules:

com.ibm.cics.iiop.RequestProcessor

End of change
Start of change
AIID
Explanation:

The IIOP Request Processor attempted to use a CorbaServer that has been disabled or failed to initialize.

System action:

The transaction is abnormally terminated.

User response:

Determine why the CorbaServer has been disabled or failed to initialize.

Modules:

com.ibm.cics.iiop.RequestProcessor

End of change
AIIP
Explanation:

An EJB was running in an OTS transaction and the timeout for this transaction was exceeded.

System action:

The transaction is abnormally terminated.

User response:

Check that an appropriate value has been set for the OTS timeout.

Modules:

com.ibm.cics.iiop.RequestProcessor

Start of change
AIIT
Explanation:

The IIOP Request Processor timed out waiting for a request from a Request Receiver. It received a timed out notification from the RZ domain in response to a listen on the RequestStream of which it is the target.

Reasons for this problem include:-

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See any related diagnostic material and determine the reason for the failure. In the case of a CICS logic error, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

com.ibm.cics.iiop.RequestProcessor

End of change
Start of change
AII1
Explanation:

An IIOP Request Receiver transaction (default CIRR) was started invalidly. This transaction can only be initiated internally by CICS.

System action:

The transaction is abnormally terminated.

User response:

Do not issue this transaction.

Modules:

DFHIIRRS

End of change
Start of change
AII2
Explanation:

The IIOP Request Receiver program DFHIIRR returned an exception which may have been caused by data received from the client.

System action:

The transaction is abnormally terminated.

User response:

DFHIIRR will have issued an exception trace point and a message and attempted to send a messageError or systemException to the client.

Examine this information to determine why the request receiver rejected the request.

Modules:

DFHIIRRS

End of change
Start of change
AII3
Explanation:

An IIOP Request Receiver task has been purged.

System action:

The transaction is abnormally terminated.

User response:

None.

Modules:

DFHIIRRS

End of change
Start of change
AII4
Explanation:

The IIOP Request Receiver program DFHIIRR has returned a disaster response due to a call to another CICS program failing.

System action:

The transaction is abnormally terminated.

User response:

DFHIIRR, or the program it called, will have issued an exception trace point and a message.

Examine this information to determine why the request receiver failed.

Modules:

DFHIIRRS

End of change
Start of change
AII5
Explanation:

The IIOP Request Receiver stub program was invoked from the sockets domain. However the TCPIPSERVICE defined in RDO did not specify a PROTOCOL of IIOP.

System action:

The transaction is abnormally terminated.

User response:

Change the TCPIPSERVICE definition to specify PROTOCOL(IIOP).

Modules:

DFHIIRRS

End of change
AINA
Explanation:

An application program has issued an EXEC CICS LINK command to the Start of changeindoubt testing tool program DFHINDT but has failed to pass a commarea containing the request to be executed. Valid requests are: ON, OFF, RESYNC COMMIT or RESYNC BACKOUT.End of change

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Correct the application program so that it passes a commarea to DFHINDT containing a valid request for DFHINDT.

Modules:

DFHINDT

AINB
Explanation:

An application program has issued an EXEC CICS LINK command to the indoubt testing tool program DFHINDT passing a commarea that did not contain a valid request to be executed, Valid requests are: ON, OFF, RESYNC COMMIT or RESYNC BACKOUT

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Correct the application program so that it passes a commarea to DFHINDT containing a valid request for DFHINDT.

Modules:

DFHINDT

AINC
Explanation:

The indoubt testing tool issued a EXEC CICS INQUIRE EXITPROGRAM command to inquire on the status of the indoubt testing tool task related user exit program DFHINTRU, and the command failed with a NOTAUTH response.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

The indoubt testing tool can be run under transaction CIND , under a user transaction where the program EXEC CICS LINKs to DFHINDT. or under a transaction where the program EXEC CICS LINKs to DFHINDAP. If command security checking is active for the transaction (CMDSEC=YES), check that the user has read access to resource EXITPROGRAM. If resource security checking is active for the transaction (RESSEC=YES), check that the user has read access to resource DFHINTRU.

Modules:

DFHINDT, DFHINDAP

AIND
Explanation:

The indoubt testing tool issued a EXEC CICS INQUIRE EXITPROGRAM command to inquire on the status of the indoubt testing tool task related user exit program DFHINTRU, and the command failed with an unexpected response.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT, DFHINDAP

AINE
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an START_LINK_BROWSE command issued by the indoubt tool to recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHINDT provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AINF
Explanation:

An EXCEPTION response with an unexpected reason occurred on an GET_NEXT_LINK call issued by the indoubt testing tool to recovery manager (RM) domain. DFHINDT provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AING
Explanation:

An error (DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an GET_NEXT_LINK call issued by the indoubt testing tool to recovery manager (RM) domain. The RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

DFHINDT also provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AINH
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an END_LINK_BROWSE command issued by the indoubt tool to recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHINDT provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AINI
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an INQUIRE_UOW command issued by the indoubt testing tool to recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHINDT provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AINJ
Explanation:

An EXCEPTION response with an unexpected reason occurred on an INITIATE_RECOVERY call issued by the indoubt testing tool to recovery manager (RM) domain. DFHINDT provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AINK
Explanation:

An error (DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INITIATE_RECOVERY call issued by the indoubt testing tool to recovery manager (RM) domain. The RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

DFHINDT also provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AINL
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an SET_RECOVERY_STATUS command issued by the indoubt testing tool to recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHINDT provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AINM
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an TERMINATE_RECOVERY command issued by the indoubt testing tool to recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHINDT provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINDT

AINN
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an ADD_LINK command issued by the indoubt testing tool to recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHINTRU provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINTRU

AINO
Explanation:

The indoubt testing tool task related user exit DFHINTRU issued an EXEC CICS INQUIRE TRANSACTION command to inquire whether the current transaction was in the indoubt transaction class DFHTCIND. The command failed with a NOTAUTH response.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

When the indoubt testing tool is active, the task related user exit DFHINTRU is invoked whenever a CICS transaction is started. For all transactions for which command security checking is active, ensure that the user has read access to resource TRANSACTION. If started transaction resource security checking is specified, for all transactions for which resource security checking is active, ensure that the user has read access to the transaction name in the specified RACF resource class.

For more information on command security and resource security see the CICS RACF® Security Guide.

Modules:

DFHINTRU

AINP
Explanation:

The indoubt testing tool task related user exit DFHINTRU issued an EXEC CICS INQUIRE TRANSACTION command to inquire whether the current transaction was in the indoubt transaction class DFHTCIND. The command failed with an unexpected response.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINTRU

AINQ
Explanation:

The indoubt testing tool task related user exit DFHINTRU issued an EXEC CICS INQUIRE TASK command to inquire on the current task to obtain the unit of work ID to include in message DFHIN1009. The command failed with a TASKIDERR response.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINTRU

AINR
Explanation:

The indoubt testing tool task related user exit DFHINTRU issued an EXEC CICS INQUIRE TASK command to inquire on the current task to obtain the unit of work ID to include in message DFHIN1009. The command failed with a NOTAUTH response.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

When the indoubt testing tool is active, the task related user exit DFHINTRU is invoked whenever a CICS transaction is started. For all transactions for which command security checking is active (CMDSEC=YES), ensure that the user has read access to resource TASK.

Modules:

DFHINTRU

AINS
Explanation:

The indoubt testing tool task related user exit DFHINTRU issued an EXEC CICS INQUIRE TASK command to inquire on the current task to obtain the unit of work ID to include in message DFHIN1009. The command failed with an unexpected response.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHINTRU

AISA
Explanation:

The mirror transaction (CSMI) has been attached from some facility other than a terminal. This is not permitted.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Using the dump, check the field TCAFCAAA to identify the invalid attach.

Modules:

DFHMIRS

AISB
Explanation:

The mirror transaction (CSMI) has detected errors in the data passed to it from the attaching transaction.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

The invalid input will be visible in the transaction dump. This error is likely to be caused by some mismatch between the two systems. A typical example might be a DL/I request received on a system generated without DL/I.

Modules:

DFHMIRS

AISC
Explanation:

The mirror transaction (CSMI) has not received a TIOA from the terminal.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the trace in the dump and the dumped TCTTE to analyze the problem further.

Modules:

DFHMIRS

AISD
Explanation:

The mirror program executed the request and received a nonzero return code as a result. The data flow control state of the intersystem link being used was such that this information could not be returned normally.

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

The transaction dump provided will provide information required to analyze the source of the nonzero return code at its point of origin.

Modules:

DFHMIRS

AISF
Explanation:

The CICS mirror program DFHMIRS has been attached in an unsupported manner. The principal facility for the mirror transaction is defined as APPC, however the conversation is unmapped.

System action:

CICS abnormally terminates the transaction with a transaction dump.

User response:

There is a problem with the system that caused the mirror transaction to be attached. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHMIRS

AISG
Explanation:

The mirror program executed the request and produced the reply. This would not be sent because the data flow control state of the intersystem link was such that this could not be done.

System action:

The task (CSMI) is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump provided to analyze the problem.

Modules:

DFHMIRS

AISH
Explanation:

The new connection task, CSNC, has been invoked in an incorrect manner (for example, from a terminal or via an EXEC CICS START request).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

None.

Modules:

DFHCRNP

AISI
Explanation:

A function shipping request was passed by DFHEIP to DFHISP. This was found to be invalid by the transformer, DFHXFP.

System action:

The transaction issuing the function shipping request is abnormally terminated with a CICS transaction dump.

User response:

The transaction dump will provide information to further analyze the problem.

Modules:

DFHISP

AISJ
Explanation:

The IRC control task CSNC has abended because the attempt to LINK to DFHCRR failed.

System action:

CSNC is abnormally terminated with a system dump. All tasks using MRO links to other systems are abnormally terminated. All tasks in other CICS regions (including shared database batch regions) that are currently communicating with this system are also abnormally terminated.

User response:

Ensure that program DFHCRR is available.

Modules:

DFHCRNP

AISK
Explanation:

The user transaction has been abnormally terminated during the execution of a function shipping request on an APPC session. This has happened because the mirror transaction on the remote system has abnormally terminated, and caused a request for syncpoint rollback to be sent across the session. CICS abends the user transaction in these circumstances so that function shipping remains transparent to the transaction.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check the log on the mirror system to determine the reason for the original abend of the mirror task.

Modules:

DFHISP

AISL
Explanation:

The LU services manager transaction has been started directly from a user terminal. This is not permitted.

System action:

The task is abnormally terminated with a transaction dump.

User response:

None. The LU services manager transaction must be started internally by CICS.

Modules:

DFHLUP, DFHCLS3, DFHCLS4, DFHZLS1

AISN
Explanation:

Task CSNC attempted to acquire a SUSPEND TOKEN to enable it to suspend itself until further work arrives. The attempt failed.

System action:

CSNC is abnormally terminated with a dump. The IRC facility is disabled.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRNP

AISO
Explanation:

Task CSNC attempted to suspend itself, awaiting further work. The attempt failed.

System action:

CSNC is abnormally terminated with a dump. The IRC facility is disabled.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRNP

AISP
Explanation:

Start of changeA mirror transaction (transaction identifiers CSHR, CSM1, CSM2, CSM3, CSM5, or CSMI) has been invoked with an invalid principal facility. The mirror transaction executes with an MRO session, an LU6.1 session or an APPC session as its principal facility.End of change

Start of change
System action:

The transaction is abnormally terminated with a CICS transaction dump.

End of change
Start of change
User response:

Do not attempt to invoke the mirror transaction by entering the transaction identifier at a terminal.

End of change
Start of change
Modules:

DFHMIRS

End of change
AISQ
Explanation:

An EXEC CICS command has been issued against a CPI Communications session. A CPI Communications session is one that has a CPI-Communications Control Block (CPC) associated with it.

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

Do not mix EXEC commands with CPI Communications calls on the same end of a conversation.

Modules:

DFHMIRS

Start of change
AISR
Explanation:

The CICS Inter-Region Session Recovery Program (DFHCRR) has been invoked in an incorrect manner, for example, from a terminal.

System action:

The program DFHCRR is abnormally terminated with a CICS transaction dump.

User response:

None.

Modules:

DFHCRR

End of change
AISS
Explanation:

A security violation has occurred while CICS was attempting to start a conversation with a remote APPC system. The security access level of the requestor was insufficient to access the transaction on the connected APPC system. Depending on the nature of the request and the way security has been set up, the requestor with an insufficient access level can be the local CICS system, the requesting transaction, or the terminal user.

Note:
DTP programs do not abend with code AISS after a security failure in the remote region.
System action:

The transaction is abnormally terminated with a transaction dump.

User response:

First, verify that the access was correctly denied. Then, if required, change the access level.

Modules:

DFHZARM

AIST
Explanation:

An unexpected return code has been returned after a DFHTC TYPE=LOCATE command.

System action:

CSNC is abnormally terminated with a system dump. All tasks using MRO links to other systems are abnormally terminated. All tasks in other CICS regions (including shared database batch regions) that are currently communicating with this system are also abended.

User response:

The trace in the system dump should be used to analyze the problem further.

Modules:

DFHCRNP

AISU
Explanation:

An INVALID, DISASTER, or EXCEPTION condition has occurred on a call to the storage manager domain (SM) to FREEMAIN a FCENT control block.

The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump.

System action:

The task is abnormally terminated with a transaction dump.

User response:

See the related message from the domain that detected the original error.

Modules:

DFHMIRS

AISV
Explanation:

A PURGED condition has occurred on a call to the storage manager domain (SM) to FREEMAIN a FCENT control block.

The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Investigate why the task was purged. This is either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHMIRS

AISW
Explanation:

An INVALID, DISASTER, or EXCEPTION condition has occurred on a call to the storage manager domain (SM) to GETMAIN or FREEMAIN a CRB control block.

The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump.

System action:

The task is abnormally terminated with a transaction dump.

User response:

See the related message from the domain that detected the original error.

Modules:

DFHCRSP

AISX
Explanation:

A PURGED condition has occurred on a call to the storage manager domain (SM) to GETMAIN or FREEMAIN a CRB control block.

The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Investigate why the task was purged. It was purged either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHCRSP

AISY
Explanation:

The LU services manager transaction has been started, but invalid parameters have been detected.

System action:

The task is abnormally terminated with a transaction dump.

User response:

See message DFHZC4921 for further guidance.

Modules:

DFHLUP

Start of change
AISZ
Explanation:

DFHMXP has received an unexpected reply when committing START PROTECT NOCHECK requests sent on a LUTYPE6.2 synclevel 1 conversation.

System action:

The task is abnormally terminated.

User response:

Determine what happened to transaction CVMI in the partner system. If the START PROTECT NOCHECK requests had been committed, no further action is necessary. If they had not been committed, user-defined action is required to recover from the error.

Modules:

DFHMXP

End of change
AIS1
Explanation:

An unexpected return code has been returned after a DFHMROQM FUNC=ENQ command was issued.

This command was issued when enqueueing work for the IRC control task (CSNC) during IRC initialization.

System action:

If IRC is being initialized during CICS initialization (as a result of IRCSTRT being specified in the DFHSIT or override parameters), then CICS is abnormally terminated.

If IRC is being initialized during the execution of a CEMT SET IRC OPEN command, then the CEMT transaction is abnormally terminated.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRSP

AIS2
Explanation:

An unexpected return code has been returned after a DFHMROQM FUNC=WAIT_Q command was issued.

This command was issued when waiting for more IRC work to process.

System action:

CSNC is abnormally terminated with a system dump. All tasks using MRO links to other systems are abnormally terminated.

All tasks in other CICS regions (including shared database batch regions) that are currently communicating with this system are also abended.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRNP

AIS3
Explanation:

An attempt to issue a STCK (Store Clock) instruction failed.

System action:

CSNC is abnormally terminated with a system dump.

All tasks using MRO links to other systems are abnormally terminated.

All tasks in other CICS regions (including shared database batch regions) that are currently communicating with this system are also abended.

User response:

Repair or enable the system clock.

Modules:

DFHCRNP

AIS4
Explanation:

An unexpected return code has been returned after a DFHMROQM FUNC=ENQUEUE command. This command was issued when enqueueing work to the IRC ‘delayed work’ queue.

System action:

CSNC is abnormally terminated with a system dump. All tasks using MRO links to other systems are abnormally terminated.

All tasks in other CICS regions (including shared database batch regions) that are currently communicating with this system are also abended.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRNP

AIS5
Explanation:

An unexpected return code has been returned after a DFHMROQM FUNC=ENQUEUE command was issued.

This command was issued when enqueueing work to the IRC ‘immediate work’ queue.

System action:

CSNC is abnormally terminated with a system dump. All tasks using MRO links to other systems are abnormally terminated.

All tasks in other CICS regions (including shared database batch regions) that are currently communicating with this system are also abended.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRNP

AIS6
Explanation:

An INVALID, DISASTER or EXCEPTION condition has occurred on a call to the storage manager domain (SM) to GETMAIN or FREEMAIN a file control read set buffer.

The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump.

System action:

The task is abnormally terminated with a transaction dump.

User response:

See the related message from the domain that detected the original error.

Modules:

DFHMIRS

AIS7
Explanation:

A PURGED condition has occurred on a call to the storage manager domain (SM) to FREEMAIN a file control read set buffer.

The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Investigate the reason why the task was purged. It was purged either by the master terminal operator , or as a result of a deadlock timeout.

Modules:

DFHMIRS

AIS8
Explanation:

An internal logic error has been detected in module DFHMIRS.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHMIRS

AIS9
Explanation:

The mirror program has detected that a DPL server program has returned in an invalid state following the completion of the LINK command. The server program or a program it linked to has initiated a synclevel 2 conversation with another program which in turn has issued a syncpoint. The server program has not responded to the syncpoint request which is still outstanding when control returns to the mirror program.

The mirror program only issues this abend code if the LINK request did not specify SYNCONRETURN.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Correct the design of the DTP application or applications initiated by the server program. If the SYNCONRETURN option is not specified on the LINK request, only the client program should initiate the syncpoint. If it is necessary to issue syncpoint requests from the DTP applications, consider using the SYNCONRETURN option on the LINK request. See the CICS Intercommunication Guide for further details of the LINK command and its options.

Modules:

DFHMIRS

AITA
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain to initialize the recovery status of an IRC session. The domain provides an exit trace, and possibly a console message and a system dump (depending on the options specified in the dump table).

This failure is either the result of a task purge, or a CICS logic error,

System action:

The CSNC task is abnormally terminated with a CICS transaction dump.

User response:

See the related diagnostic material produced by the recovery manager domain and determine the reason for the failure. In the case of a CICS logic error, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRNP

AITB
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain. The domain provides an exit trace, and possibly a console message and a system dump (depending on the options specified in the dump table).

This failure is either the result of a task purge, or a CICS logic error,

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related diagnostic material produced by the recovery manager domain and determine the reason for the failure. In the case of a CICS logic error, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHISP DFHMXP

AITC
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain. The domain provides an exit trace, and possibly a console message and a system dump (depending on the options specified in the dump table).

This failure is either the result of a task purge, or a CICS logic error,

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

See the related diagnostic material produced by the recovery manager domain and determine the reason for the failure. In the case of a CICS logic error, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHMIRS

Start of change
AITD
Explanation:

The mirror program has received an unexpected response from the RX domain.

There are several reasons why this error may occur:

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

Use the exception trace provided by the RX domain to determine the reason for the failure. If the error is caused by an inconsistent request from an EXCI client, there may be an error in the client program.

In the other cases, you might need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHMIRS

End of change
Start of change
AITE
Explanation:

A transaction has executed a transactional EXCI request from a batch region, and has been waiting for one of the following events for longer than the interval specified in the RTIMOUT value for the transaction.

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

Determine why the expected event has not occurred:

If a further transactional EXCI request is expected

If a syncpoint is expected

See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHMIRS

End of change
Start of change
AITF
Explanation:

A transaction has executed a transactional EXCI request from a batch region, and has been purged while waiting for one of the following events:

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

Determine why the expected event has not occurred:

If a further transactional EXCI request is expected

If a syncpoint is expected

See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHMIRS

End of change
Start of change
AITG
Explanation:

A transaction has executed a transactional EXCI request from a batch region, and both of the following events has occurred:

Normally, only one event should occur, and not both.

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

Determine why both events have occurred. This situation may arise when an EXCI client times out on a DPL request that CICS is not ready to receive and then proceeds to take a syncpoint. If this is not the case, you may need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHMIRS

End of change
Start of change
AITH
Explanation:

A mirror transaction processing an ECI request from a TCP/IP connected client has failed while trying to receive data from, or send data to, a client. This could be a read time out, or a more serious error in the flows that prevented CICS from correctly processing the data.

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

If the error was a time out, determine why the client has not continued with the extended ECI conversation. Other errors will have associated IE domain messages to aid in problem determination.

Modules:

DFHMIRS

End of change
AITI
Explanation:

A mirror transaction processing a START CHANNEL or LINK CHANNEL request has failed while trying to receive data from, or send data to, a connected CICS system. Because a channel may include a considerable amount of data, it may require many calls to terminal control to transmit channel data. DFHMIRS calls program DFHAPCR to perform all the inter-system transmission of channel data. Terminal control has detected an error in one of these calls. The error could be a read time out, or a more serious error in the flows that prevented CICS from correctly processing the data.

System action:

The mirror task is abnormally terminated with a CICS transaction dump.

User response:

If the error was a time out, determine why the other end has not continued with the conversation. Other errors will have associated terminal control messages to aid in problem determination. Examine trace entries from DFHAPCR to determine terminal control error and sense information.

Modules:

DFHMIRS

Start of change
AITM
Explanation:

A command has been received by the mirror program to call itself.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Correct the API command in the client system program so that is does not request an EXEC CICS LINK PROGRAM to run that specifies the name of the mirror program.

Modules:

DFHMIRS

End of change [[ Contents Previous Page | Next Page Index ]]