DFHACxxxx (DFHACP) messages

DFHAC2001
date time applid Transaction 'tranid' is not recognized. Check that the transaction name is correct.
Explanation:

Either transaction tranid does not exist as an installed transaction definition, or it is disabled, or it contains invalid characters.

Note that destination CSMT is used for non-terminal transactions only.

System action:

Processing continues.

User response:

Enter a valid transaction identifier.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2002
date time applid To use this transaction tranid you must sign on or have the right security level.
Explanation:

You are signed on using the default userid but this userid does not have access to the requested transaction.

System action:

CICS does not initialize the invoked transaction. Other processing continues and message DFHAC2003 is sent to destination CSMT.

User response:

Sign on with an authorized userid.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2003
date time applid Security violation has been detected term id = termid, trans id = tranid, userid = userid.
Explanation:

The operator with user ID userid has invoked a transaction tranid at terminal termid for which the operator is not authorized.

System action:

CICS does not initialize the invoked transaction. Either message DFHAC2002 or DFHAC2033 is sent to the terminal operator. Other CICS processing continues.

User response:

Refer to the userid in the preceding message, DFHXS1111 on the CSCS log, to determine the identity of the person trying to invoke transaction tranid and the reason for the attempt.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, termid, tranid, userid

DFHAC2004
time applid Transaction tranid has failed with abend AKCC. Resource backout was successful.
Explanation:

Transaction tranid is abnormally terminated with abend AKCC.

System action:

The transaction (task) is purged.

User response:

Resubmit the transaction.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2005
time applid Transaction tranid has failed with abend abcode.
Explanation:

Transaction tranid has been defined with INDOUBT(WAIT) or INDOUBT(COMMIT) and has been in communication with a partner APPC system. A session failure has occurred while the session was INDOUBT during an explicit or implicit syncpoint. An immediate resync was attempted but could not be completed.

System action:

The task is abnormally terminated with a transaction dump. Unless overridden, APPC resynchronization is retried when the remote system is available.

User response:

For more information, see the abend code abcode. If necessary, resubmit the transaction after the cause of the abend has been removed.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2006
date time applid Transaction tranid program program name abend primary abcode at termid.
Explanation:

The system was unable to execute transaction tranid. termid identifies the terminal which initiated transaction tranid. If there is no associated terminal, termid appears as "????". Program progname is the highest level program and is taken from the installed program definition. abcode is the CICS abend code.

System action:

The task is abnormally terminated with a dump.

User response:

Refer to abend code abcode for further information and guidance on how to solve the problem. If the code is not available, it is a user code generated by an EXEC CICS ABEND ABCODE(abcode) command. This command has been issued by a user program or by an IBM program (for example, a programming language library module).

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid, program name,primary abcode, termid

DFHAC2007
date time applid Transaction tranid cannot run as CICS shutdown is in progress.
Explanation:

Transaction tranid cannot be run during system quiesce.

System action:

The system is in quiesce mode.

Note that destination CSMT is used for non-terminal transactions only.

User response:

Re-enter the transaction when CICS is in normal execution mode, or place an entry for this transaction in the transaction list table (XLT).

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2008
date time applid Transaction tranid has been disabled and cannot be used.
Explanation:

Terminal tranid has been disabled.

Note that destination CSMT is used for non-terminal transactions only.

System action:

Other processing continues.

User response:

Notify the programmer responsible for this area that transaction tranid has been disabled.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2009
date time applid Invalid non-terminal transaction tranid.
Explanation:

Transaction tranid has been entered. No terminal is associated with this transaction. It may be that transaction tranid is a disabled transaction, or is one that cannot be run during system quiesce. Alternatively, an invalid transaction identifier may have been entered.

System action:

Other processing continues.

User response:

Determine and correct the reason for transaction tranid’s invalidity.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2010
time applid Transaction tranid is not executable on terminal termid.
Explanation:

A conflict has been detected between the options specified for transaction tranid’s definition and those specified on terminal termid’s DFHTCT table entry. For example, transaction tranid is reserved for the use of VTAM terminals but the input came from a non-VTAM terminal.

System action:

The input is ignored.

User response:

If transaction tranid is to be entered from terminal termid, ensure that the installed transaction definition value of DVSUPRT is compatible with the DFHTCT entry.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2012
date time applid Remote transaction tranid cannot be run on the local system.
Explanation:

Transaction tranid is specified as remote. An attempt to route the transaction to a remote system failed either because there is no MRO/ISC defined in the running CICS system, or because the remote system name specified in the definition of the transaction is the same as that of the local system.

Note that destination CSMT is used for nonterminal transactions only.

System action:

The task is abnormally terminated.

User response:

Ensure that:

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

Start of changeDFHAC2014End of change
Start of changedate time applid Transaction tranid is not executable because system sysid is not available.End of change
Start of change
Explanation:

Transaction tranid is specified as remote. An attempt to route the transaction to a remote system failed because the link is out of service.

This message is also issued if the connection definition for the remote system has QUEUELIMIT and MAXQTIME specified and a queued allocate has been rejected.

Note that destination CSMT is used for non-terminal transactions only.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

Wait until the link is available.

If QUEUELIMIT and MAXQTIME are specified and this message occurs frequently then see the Intersystem Session Queue Management section in the Intercommunication Guide.

End of change
Start of change
Destination:

CSMT and Terminal End User

End of change
Modules:

Start of changeDFHACPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changesysidEnd of change

Start of changeDFHAC2015End of change
Start of changedate time applid Console consname has not been defined to CICS. Input is ignored.End of change
Start of change
Explanation:

The console operator at the console named consname has directed a MODIFY command to the CICS region, but no terminal definition for that console is installed in the region, and autoinstall for consoles is not enabled.

End of change
Start of change
System action:

The MODIFY command from the console is ignored.

End of change
Start of change
User response:

Notify the system programmer, who should use RDO to DEFINE and INSTALL a console definition that matches the name of the console, or enable autoinstall for consoles. Start of changeThe system programmer may also consider using 'pooled' consoles by defining TERMINAL definitions with a CONSNAME of DFHCONxx, or increasing the number of pooled consoles.End of change

End of change
Start of change
Destination:

CSMT and Terminal End User

End of change
Modules:

Start of changeDFHACP, DFHZATA2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeconsnameEnd of change

DFHAC2016
date time applid Transaction tranid cannot run because program program name is not available.
Explanation:

Transaction tranid is not executable because the initial program for transaction tranid is not available. Possible reasons for this are:

  1. The program is missing.
  2. The installed program definition is missing.
  3. The program is disabled.
  4. The program name in the installed transaction definition is invalid.
  5. The installed transaction has been defined as remote and therefore has no program name, but the name of the remote system is the same as that of the local system.
  6. Start of changeThe program requires a JVM to run but JVM initialization failed.End of change
  7. Start of changeThe autoinstall program abended while attempting to load the program.End of change
  8. Start of changeThe Language Environment options specified in DFHJVMRO are too long.End of change

Note that destination CSMT is used for non-terminal transactions only.

System action:

Other processing continues.

User response:

Determine the cause of the error using the list given in the Explanation. The response depends on the reason as follows:

  1. Load the program into the CICS program library.
  2. Create an installed program definition for the program.
  3. Enable the program.
  4. Use a valid program name in the installed transaction definition.
  5. Carry out whichever of the following is appropriate:
    • Use a local version of this transaction.
    • Use the correct remote version of this transaction.
    • Logon to the correct system and retry the transaction.
  6. Start of changeFor JVM programs check the CSMT log for further information as to why JVM initialization failed.End of change
  7. Start of changeCheck the job output for further information as to why the autoinstall program abended.End of change
  8. Start of changeRemove any unnecessary options and abbreviate any Language Environment option keywords, where possible, in your source for DFHJVMRO.End of change
Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid, program name

DFHAC2017
date time applid Transaction tranid cannot run because terminal profile profname for the transaction is not available.
Explanation:

Transaction tranid is not executable because the terminal profile for the transaction is not available. This is because it has not been defined, or it has not been installed.

Note that destination CSMT is used for non-terminal transactions only.

System action:

Other processing continues.

User response:

Notify the system programmer or system administrator.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid, profname

DFHAC2018
date time applid An unrecognized Process Initialization Parameter (PIP) has been received in ATTACH for transaction tranid.
Explanation:

CICS has received an LU type 6.2 attach header with invalid process initialization parameters (PIPs).

Note that destination CSMT is used for non-terminal transactions only.

System action:

CICS rejects the attach request.

User response:

Inspect the received PIP data and its associated generalized data stream (GDS) header to determine why the parameters are invalid.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2019
date time applid Transaction tranid does not support unmapped conversations.
Explanation:

Transaction tranid received an attach request that required the use of the generalized data stream (GDS) to access unmapped conversations, but transaction tranid does not support the use of the GDS interface.

System action:

CICS rejects the attach request.

Note that destination CSMT is used for non-terminal transactions only.

User response:

Inspect the subsystem that sent the attach header to see if the correct transaction was requested. If the request was correct, check the CICS transaction definition.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2020
time applid The conversation type requested by node netname was not recognized.
Explanation:

CICS received a conversation-type field in an attach header that was not TYPE=MAPPED or TYPE=UNMAPPED.

System action:

The attach request is rejected.

User response:

Notify the system programmer. The validity of the attach function management header (FMH) should be checked and the cause of the error identified.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2021
time applid An unsupported Data Blocking Algorithm (DBA) field in the attach Function Management Header (FMH) has been received from node netname.
Explanation:

The received attach header contained a value for the reserved data blocking algorithm (DBA) field.

System action:

The attach request is rejected.

User response:

Notify the system programmer. The validity of the attach function management header (FMH) should be checked and the cause of the error identified.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2022
date time applid Transaction tranid has initiated an incorrect sync point level request.
Start of change
Explanation:

The requested Synclevel does not match the synclevel negotiated in the Bind request, or Synclevel 2 was requested, but Lognames were not exchanged.

Note that destination CSMT is used for non-terminal transactions only.

End of change
Start of change
System action:

The attach request is rejected.

End of change
Start of change
User response:

Notify the system programmer. The subsystem that sent the attach header should be inspected to determine that the correct transaction was requested. If it was, the CICS transaction definition should be checked.

End of change
Start of change
Destination:

CSMT and Terminal End User

End of change
Modules:

Start of changeDFHACPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranidEnd of change

DFHAC2023
time applid An invalid sync point level has been requested by node netname.
Explanation:

The synchronization level requested in the attach header is invalid for the session being used.

System action:

The attach request is rejected.

User response:

Notify the system programmer. The validity of the attach function management header (FMH) should be checked and the cause of the error identified. The value of the synchronization level in the attach header and the bind should be compared.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2024
date time applid A request from node netname has invalid security parameters.
Explanation:

The received attach header did not match the required security parameters specified in the bind.

Note that destination CSMT is used for non-terminal transactions only.

System action:

The attach request is rejected.

User response:

Notify the system programmer. The validity of the attach function management header (FMH) should be checked and the cause of the error identified. The value of the ACC requirements in the attach header and the bind should be compared.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2025
time applid An invalid Unit of Work Identification (UOWID) has been supplied by node netname.
Explanation:

The received attach header contained an invalid unit of work ID (UOWID). Either the format was wrong, or no UOWID was received when the sync point level required it. This error may also be raised if no conversation correlator is supplied when it is needed.

System action:

The attach request is rejected.

User response:

Notify the system programmer. The validity of the attach function management header (FMH) should be checked and the cause of the error identified. The value of the UOWID/conversation correlator and the sync point level in the attach header should be compared.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2026
time applid An invalid Function Management Header (FMH) has been supplied by node netname.
Explanation:

The length field in the attach header was invalid.

System action:

The attach request is rejected.

User response:

Notify the system programmer. The validity of the attach function management header (FMH) should be checked and the cause of the error identified.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2027
date time applid Transaction tranid does not support conversation restart.
Explanation:

CICS will not accept LU type 6.2 attach headers with restart requested.

Note that destination CSMT is used for non-terminal transactions only.

System action:

The attach request is rejected.

User response:

Notify the system programmer. The subsystem that sent the attach header should be inspected to determine why restart was requested.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2028
date time applid Transaction tranid cannot be used and has been ignored.
Explanation:

The transaction code CSAC or CESC, was entered from a terminal. This is not allowed.

System action:

If the transaction is CSAC, the transaction is run with no effect. If the transaction is CESC, the transaction is abnormally terminated with abend code ATOA.

User response:

Ensure that these transactions are not entered from a terminal.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2029
date time applid Transaction tranid is not executable. The system specified by the dynamic routing program is unavailable.
Explanation:

Transaction tranid is specified as remote AND dynamic. An attempt to dynamically route transaction tranid to the remote system specified by the dynamic routing program has failed because the link is out of service.

Note that destination CSMT is used for non-terminal transactions only.

System action:

CICS continues.

User response:

Wait until the link becomes available, then try to dynamically route the transaction again.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2030
date time applid All sessions are busy. Please try again.
Explanation:

Transaction tranid is specified as remote AND dynamic. An attempt to dynamically route transaction tranid to the remote system specified by the dynamic routing program has failed because no sessions are immediately available.

Note that destination CSMT is used for non-terminal transactions only.

System action:

CICS continues.

User response:

Wait until a session becomes available, then try to dynamically route the transaction again.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid

Start of changeDFHAC2031End of change
Start of changedate time applid Automatic signon of operator of console consname has failed.End of change
Start of change
Explanation:

The console operator at the console named consname has directed a MODIFY command to the CICS region, and the console was defined with USERID(*FIRST) or USERID(*EVERY). When CICS tried to signon the operator automatically, the signon was rejected.

End of change
Start of change
System action:

The MODIFY command from the console is ignored.

End of change
Start of change
User response:

Contact the system programmer to give the userid in use at the console (which is identified in other messages on the log), the correct access to this console using RACF (or an equivalent External Security manager).

End of change
Start of change
Destination:

CSML and Terminal End User

End of change
Modules:

Start of changeDFHACP, DFHZATA2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeconsnameEnd of change

Start of changeDFHAC2032End of change
Start of changedate time applid CICS autoinstall for console consname has failed.End of change
Start of change
Explanation:

The console operator at the console named consname has directed a MODIFY command to the CICS region, but no terminal definition for that console is installed in the region, and an autoinstall for it has failed.

End of change
Start of change
System action:

The MODIFY command from the console is ignored.

End of change
Start of change
User response:

Notify the system programmer, who should investigate the failure by looking for abends and messages on the log of the CICS system.

End of change
Start of change
Destination:

CSML

End of change
Modules:

Start of changeDFHACP, DFHZATA2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeconsnameEnd of change

DFHAC2033
time applid You are not authorized to use transaction tranid. Check that the transaction name is correct.
Explanation:

Either an operator has attempted to execute transaction tranid while not authorized, or another transaction attempted to start transaction tranid, which was not authorized for this terminal.

System action:

Other processing continues. Message DFHAC2003 is sent to CSMT.

User response:

Either determine why the operator was trying to execute transaction tranid or enter an authorized transaction identifier.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2034
time applid CICS Logic Error. An invalid error code has been passed to DFHACP. Transaction: tranid Terminal: termid.
Explanation:

An invalid error code has been passed to DFHACP.

System action:

Transaction tranid is terminated with a transaction dump. The dump code is AACA. Message DFHAC2035 is sent to the CSMT.

User response:

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

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2035
date time applid An invalid error code has been passed to DFHACP. Transaction tranid is terminated. Terminal termid.
Explanation:

An invalid error code has been passed to DFHACP.

System action:

Transaction tranid is terminated with a transaction dump. A transaction dump is taken. The dump code is AACA. Message DFHAC2034 is sent to the terminal user.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid, termid

DFHAC2036
date time applid Transaction tranid has failed with abend AKCC. Resource backout was successful.
Explanation:

Transaction tranid has abended AKCC.

System action:

The transaction (task) is purged.

User response:

Resubmit the transaction later.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2037
date time applid Transaction tranid is not executable on terminal termid.
Explanation:

A conflict has been detected between the options specified for transaction tranid’s definition and those specified on terminal termid’s DFHTCT table entry. For example, transaction tranid is reserved for the use of VTAM terminals but the input came from a non-VTAM terminal.

System action:

The input is ignored.

User response:

If transaction tranid is to be entered from terminal termid, ensure that the installed transaction definition value of DVSUPRT is compatible with the DFHTCT entry.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid, termid

DFHAC2038
date time applid The conversation type requested by node netname was not recognized.
Explanation:

CICS received a conversation-type field in an attach header that was not TYPE=MAPPED or TYPE=UNMAPPED.

System action:

The attach request is rejected.

User response:

Notify the system programmer. The validity of the attach function management header (FMH) should be checked and the failing subsystem identified.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2039
date time applid An unsupported Data Blocking Algorithm (DBA) field in the attach Function Management Header (FMH) has been received from node netname.
Explanation:

The received attach header contained a value for the reserved data blocking algorithm (DBA) field.

System action:

The attach request is rejected.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. Check the validity of the attach function management header (FMH), and identify the failing subsystem.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2040
date time applid An invalid sync point level has been requested by node netname.
Explanation:

The synchronization level requested in the attach header is invalid for the session being used.

System action:

The attach request is rejected.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. Check the validity of the attach function management header (FMH), and identify the failing subsystem. Compare the value of the synchronization level in the attach header and the bind.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2041
date time applid An invalid Unit of Work Identification (UOWID) has been supplied by node netname.
Explanation:

The received attach header contained an invalid unit of work ID (UOWID). Either the format was wrong, or no UOWID was received when the sync point level required it. This error may also be raised if no conversation correlator is supplied when it is needed.

System action:

The attach request is rejected.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. The validity of the attach function management header (FMH) should be checked and the failing subsystem identified. The value of the UOWID/conversation correlator and the sync point level in the attach header should be compared.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2042
date time applid An invalid Function Management Header (FMH) has been supplied by node netname.
Explanation:

The length field in the attach header was invalid.

System action:

The attach request is rejected.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. Check the validity of the attach function management header (FMH), and identify the failing subsystem.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2043
date time applid Transaction has been rejected - CICS system is being recovered. Please wait for completion of recovery.
Explanation:

A request to initiate a transaction was received while the CICS system was in the process of recovering the session following an XRF takeover or persistent sessions restart. The error is detected by DFHZSUP, which then drives DFHACP to issue this message.

Note that destination CSMT is used for non-terminal transactions only.

System action:

Depending upon the recovery notification requested for this terminal, the system will send either the recovery message or initiate the recovery transaction specified on the RECOVNOTIFY option of the typeterm definition for this terminal (see the CICS Resource Definition Guide for details).

User response:

After the recovery notification has been received, the user is able to continue operations.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid

DFHAC2044
date time applid An error occurred while trying to send SYNCPOINT ROLLBACK to terminal termid.
Explanation:

An attempt was made to send a SYNCPOINT ROLLBACK request. A nonzero return code was received by the sender of the request.

System action:

ABORT processing is initiated for terminal termid.

User response:

Notify the system programmer. Use trace to find the value of the return code from the SYNCPOINT ROLLBACK request. For IRC, the meaning of the return code can be found in the CICS Data Areas manual.

Destination:

CSMT

Modules:

DFHZIS1

XMEOUT Parameters: date, time,applid, termid

Start of changeDFHAC2045End of change
Start of changedate time applid CICS autoinstall for console consname was rejected by the autoinstall control program.End of change
Start of change
Explanation:

The console operator at the console named consname has directed a MODIFY command to the CICS region, but no terminal definition for that console is installed in the region, and an autoinstall for it has failed because the autoinstall program has rejected the install request.

End of change
Start of change
System action:

The MODIFY command from the console is ignored.

End of change
Start of change
User response:

Notify the system programmer, who should alter the autoinstall program to allow this console to be installed.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHACP, DFHZATA2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeconsnameEnd of change

DFHAC2047
date time applid While performing an attach for node netname a security violation was detected.
Explanation:

A request to attach a remote transaction failed due to a security problem. The security fields extracted from the Attach FMH5 were passed to the Security Domain to signon the user in the remote system, but the signon call failed.

System action:

The attach request is rejected.

User response:

Refer to previous security messages which are written to TDQ CSCS such as DFHSN1604 for further information and guidance. If no previous messages were issued, examine the trace to determine the reason for the signon failure. Check that if the userid, password or profile are passed on the Attach FMH5, then they are valid.

Destination:

CSMT and Terminal End User

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2050
time applid An invalid function management header (FMH) has been supplied by node netname.
Explanation:

The access security information length field in the attach header is invalid.

System action:

An exception trace entry containing the invalid FMH5 is issued. The attach request is rejected.

User response:

Notify the system programmer. Check the validity of the attach function management header and identify the cause of the error.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2051
date time applid An invalid Function Management Header (FMH) has been supplied by node netname.
Explanation:

The Access Security Information length field in the attach header was invalid.

System action:

An exception trace entry containing the invalid FMH5 has been issued. The attach request is rejected.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. Check the validity of the attach function management header (FMH), and identify the failing subsystem.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2052
time applid While performing an attach for node netname a security violation was detected.
Explanation:

A password was required in the attach FMH5, but was missing. A user ID was found, however, because the attach did not specify already verified (AV) or persistent signed-on (PV1), a password should have been present.

System action:

An exception trace entry is issued tracing the invalid FMH5. The attach request is rejected.

User response:

Notify the system programmer. Inspect the subsystem that sent the attach header to determine why the password was not sent.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2053
date time applid While performing an attach for node netname a security violation was detected.
Explanation:

A password was required in the attach FMH5, but was missing. A user ID was found, however, since the attach did not specify already verified (AV) or persistent signed-on (PV1), a password should have been present.

System action:

An exception trace entry is issued tracing the invalid FMH5. The attach request is rejected. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. Inspect the subsystem that sent the attach header to determine why the password was not sent.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2054
time applid You are not authorized to access this system.
Explanation:

The attach header that was sent to the remote system did not match the required security parameters specified in the bind.

System action:

The attach request is rejected by the remote system and the session is unbound. The remote system issues messages DFHAC2055 on CSMT and DFHZC4946 on CSNE.

User response:

Inform the system programmer. Investigate the reason why the attach request failed. See messages DFHAC2055 on CSMT and DFHZC4946 on CSNE issued by the remote system for more diagnostic information.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2055
date time applid An attach request from node netname has sent BIND/FMH5 security data that is invalid.
Explanation:

A request to attach a task has been received across an APPC link. However, there is an error in the FMH attach parameters. An attach parameter is present that is not authorized by the bind security indicators.

System action:

The attach request is rejected and the session is unbound. An exception trace point (number 1737) for component TF is issued, tracing the invalid attach header (FMH type 5). Message DFHZC4946 on CSNE contains sense information to help identify the reason for the failure. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Investigate the cause of the error which is in the remote system. Use the FMH5 in the exception trace, to determine why the remote system sent an invalid attach request.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2056
time applid You are not authorized to access this system.
Explanation:

The attach header that was sent to the remote system did not conform to the APPC protocol.

System action:

The attach request is rejected by the remote system and the session is unbound. The remote system will produce messages DFHAC2057 on CSMT and DFHZC4947 on CSNE.

User response:

Inform the system programmer. Investigate the reason why the attach request failed. See messages DFHAC2057 on CSMT and DFHZC4947 on CSNE issued by the remote system for more diagnostic information.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2057
date time applid While performing an attach for node netname a security violation was detected.
Explanation:

A request to attach a task has been received across an APPC link. However, the FMH attach parameters do not conform to the APPC protocol.

System action:

The attach request is rejected and the session is unbound. An exception trace point (number 1737) for component TF is issued tracing the invalid attach header (FMH type 5). Message DFHZC4947 is issued. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Investigate the cause of the error which is in the remote system. Use the FMH5 in the exception trace to determine why the remote system sent an invalid attach request. See message DFHZC4947 on CSNE which contains sense information to help identify the reason for the failure.

If the remote system has an earlier release of CICS or CICS on another platform then you may need to set USEDFLTUSER. See Attach Time Security and the USEDFLTUSER option in the CICS RACF® Security Guide.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, netname

DFHAC2201
time applid Transaction tranid has lost contact with its coordinator system during syncpoint processing and has abended with code ASP1. The unit of work is shunted until contact is restored. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. The coordinator of the syncpoint is not this CICS system but is remote.

Transaction tranid has lost contact with its coordinator system during the critical period of syncpoint processing known as the 'indoubt window'.

In accordance with the transaction definition (WAIT YES), the unit of work is not completed but is allowed to wait for resynchronization with the coordinator system. The transaction is abnormally terminated with abend code ASP1. The unit of work is shunted to await the return of the coordinator system.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2231 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

None. Any updates performed by the unit of work are resolved automatically when resynchronization with the coordinator takes place.

Alternatively, the user may force resolution of the updates independently of the coordinator system by making a CEMT request to commit or to back out the unit of work.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2202
time applid Transaction tranid has lost contact with its coordinator system during syncpoint processing and has abended with code ASPO. All updates will be unilaterally committed. condmsg
Explanation:

Transaction tranid has lost contact with its coordinator system during the critical period of syncpoint processing known as the 'indoubt window'. The transaction is abnormally terminated with abend code ASPO.

In accordance with the transaction definition (WAIT NO and ACTION COMMIT), all recoverable updates performed by the unit of work are unilaterally committed. Note that integrity of updates may be lost because the coordinator system may either commit or back out its changes.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2232 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

None. In accordance with the transaction definition, all updates are unilaterally committed.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2203
time applid Transaction tranid has lost contact with its coordinator system during syncpoint processing and has abended with code ASPP. All updates will be unilaterally backed out. condmsg
Explanation:

Transaction tranid has lost contact with its coordinator system during the critical period of syncpoint processing known as the 'indoubt window'. The transaction is abnormally terminated with abend code ASPP.

In accordance with the transaction definition (WAIT NO and ACTION BACKOUT), all recoverable updates performed by the unit of work are unilaterally backed out. Note that integrity of updates may be lost because the coordinator system may either commit or back out its changes.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2233 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

None. In accordance with the transaction definition, all updates are unilaterally backed out.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2204
time applid A commit failure has occurred during syncpoint processing for transaction tranid. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources local to this CICS system, for example files, temporary storage, transient data, have been updated. A commit failure occurred during phase 2 of the syncpoint protocol for a local resource owner.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2234 is sent to the master terminal operator (destination CSMT). For an EXEC CICS SYNCPOINT, processing completes normally and processing continues with the next unit of work. For EXEC CICS RETURN, the transaction completes normally.

Resources affected by the commit failure remain locked and the unit of work is shunted.

User response:

Refer to earlier messages output by the local resource owner to discover the cause of the commit failure.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2205
time applid A backout failure has occurred during syncpoint processing for transaction tranid. condmsg
Explanation:

An attempt to backout a unit of work has suffered a backout failure. For the local resource owner(s) that suffered the backout failure, the resources updated by the unit of work remain locked. All other resources are backed out.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2235 is sent to the master terminal operator (destination CSMT). For an EXEC CICS SYNCPOINT, processing completes normally and processing continues with the next unit of work. For EXEC CICS RETURN, the transaction completes normally.

Resources affected by the backout failure remain locked and the unit of work is shunted.

User response:

Refer to earlier messages output by the local resource owner to discover the cause of the backout failure.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2206
time applid Transaction tranid failed with abend abcode. Updates to local recoverable resources backed out. condmsg
Explanation:

Transaction tranid is abnormally terminated with abend code abcode. Any changes to recoverable resources in the local system that have been performed by the current unit of work are backed out.

abcode is either a CICS transaction abend code or a user abend code generated by a CICS ABEND ABCODE(abcode) command. This command is issued either by a user program or by an IBM program (for example, a programming language library module).

If possible, a conditional message condmsg from the remote system will be appended to this message.

When this message is issued in the terminal owning region because a remote transaction has failed, there may be no recoverable resources to be backed out in the local system. In this case, the conditional message tells you whether or not resources in the remote system have been backed out.

System action:

Message DFHAC2236 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

Use the abend code, abcode, to diagnose the problem. In a transaction routing environment, the original cause of the failure is usually indicated in the conditional message. If the abend is issued by an IBM program product other than CICS, the code is documented in the library of that other product.

Resubmit the transaction after the cause of the original abend has been removed.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2215
time applid A CICS-generated syncpoint request has failed because a connected system has requested that the UOW be rolled back. Transaction tranid has been abnormally terminated with code ASPF. condmsg
Explanation:

CICS has been unable to comply with an internally generated syncpoint request because a connected system has notified it that the unit of work must be rolled back. (This may also occur as a result of a session failure or a protocol error).

Transaction tranid is abnormally terminated with abend code ASPF. Any changes to recoverable resources that have been performed by the current unit of work are backed out.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2245 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

Determine why the connected system sent the indication to roll back the unit of work.

Resubmit the transaction after the cause of the indication to roll back has been removed.

Destination:

Terminal End User

Modules:

DFHTFP

Start of change
DFHAC2216
time applid Transaction termination processing for transaction tranid has failed because a connected system has requested that the UOW be rolled back. condmsg
Explanation:

A transaction has issued an EXEC CICS RETURN in backout required program state. The backout required program state is set when an application receives a backout request on a protected conversation.

Recoverable resources updated by the unit of work are backed out and locks released.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2246 is sent to the master terminal operator (destination CSMT). Termination processing continues.

User response:

To avoid the error, the application should code an EXEC CICS SYNCPOINT command before the EXEC CICS RETURN. A syncpoint issued in 'backout required' program state results in a backout being performed, and the ROLLEDBACK condition returned on the EXEC CICS SYNCPOINT command. If this condition is then handled, a subsequent EXEC CICS RETURN will complete successfully.

Resubmit the transaction after the cause of the indication to roll back has been removed.

Destination:

Terminal End User

Modules:

DFHTFP

End of change
DFHAC2217
time applid Transaction tranid has requested rollback, but was using a type of processing for which rollback is not supported. The transaction has been abnormally terminated with code ASP8. message
Explanation:

An application requested syncpoint rollback, but was using a type of processing that does not support rollback, for example LU6.1.

Transaction tranid is abnormally terminated with abend code ASP8. Any changes to recoverable resources that have been performed by the current unit of work will be backed out.

If possible, a conditional message condmsg from the linked system will be appended to this message.

System action:

Message DFHAC2247 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

Refer to the explanation of abend ASP8.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2218
time applid Transaction tranid has failed with abend ASP7 following the failure of a local resource owner in the prepare phase of syncpoint. Updates will be backed out. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources local to this CICS system, for example files, temporary storage, or transient data, have been updated, and so the local resource owners have been sent a syncpoint request. A local resource owner has replied 'No' to a request to 'Prepare', during the two phase syncpoint protocol.

Transaction tranid is abnormally terminated with abend code ASP7. Any changes to recoverable resources that have been performed by the current unit of work are backed out.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2248 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

Refer to the explanation of abend ASP7.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2219
time applid Transaction tranid has failed with abend ASP7 following the failure of a remote system in the prepare phase of syncpoint. Updates will be backed out. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources remote to this CICS system, for example files, temporary storage, transient data on remote CICS systems, or database managers communicating via the RMI, have been updated, and so the remote resource owners have been sent a syncpoint request. A remote resource owner has replied 'No' to a request to 'Prepare', during the two phase syncpoint protocol.

Transaction tranid is abnormally terminated with abend code ASP7. Any changes to recoverable resources that have been performed by the current unit of work are backed out.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2249 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

Refer to the explanation of abend ASP7.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2220
time applid The coordinator system has indicated that the current unit of work is to be backed out. Transaction tranid has been abnormally terminated with abend ASP3. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. The coordinator of the syncpoint is not this CICS system but is remote. During the syncpoint protocol the remote coordinator has decided that the unit of work cannot be committed and must be backed out.

Transaction tranid is abnormally terminated with abend code ASP3. Any changes to recoverable resources that have been performed by the current unit of work are backed out.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2250 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

Refer to the remote coordinator system to discover the reason why the unit of work was backed out.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2221
time applid Transaction tranid has failed with abend ASPQ. Syncpoint commit processing has failed while communicating with a remote system. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources remote to this CICS system such as files, temporary storage, and transient data on remote CICS systems have been updated, and so the remote resource owners have been sent a syncpoint request. A failure occurred during phase 2 of syncpoint protocol.

Transaction tranid has abnormally terminated with abend code ASPQ. Recoverable resources have successfully been committed but a subsequent error occurred.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2251 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

Refer to the associated messages already issued by the communication components of CICS to determine the cause of the intersystem session problem.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2222
time applid Transaction tranid has lost contact with its coordinator system during syncpoint processing. No updates have been performed by this system; it has abended with code ASPR. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. The coordinator of the syncpoint is not this CICS system but is remote.

Transaction tranid has lost contact with its coordinator system during the critical period of syncpoint processing known as the 'indoubt window'. However no recoverable resources have been updated by this system, so there is no data integrity problem.

Transaction tranid is abnormally terminated with abend code ASPR.

If possible, a conditional message condmsg from the linked system is appended to this message.

System action:

Message DFHAC2252 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

Refer to messages on the remote system to determine if the remote resources were backed out or committed.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2223
time applid Transaction tranid has failed with abend ASP2 due to the links to the remote systems being in an invalid state. Updates will be backed out. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources remote to this CICS system, for example files, temporary storage, transient data on remote CICS systems, or database managers communicating via the RMI, have been updated, and so the remote resource owners would be sent a syncpoint request. The links to the remote resource owners are in an invalid state to be sent the PREPARE request of the two phase syncpoint protocol.

Transaction tranid is abnormally terminated with abend code ASP2. Any changes to recoverable resources that have been performed by the current unit of work are backed out.

System action:

Message DFHAC2253 is sent to the master terminal operator (destination CSMT). Normal abend processing continues.

User response:

See the explanation of abend ASP2 for guidance.

Destination:

Terminal End User

Modules:

DFHTFP

DFHAC2230
date time applid Transaction tranid terminal termid not executed due to I/O error at session startup. message
Explanation:

Transaction tranid could not be executed because an I/O error occurred in the start-up program on terminal termid.

System action:

Transaction tranid is not executed.

User response:

Correct the cause of the I/O error, which is probably due to the terminal not being powered on.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid, termid, message

DFHAC2231
date time applid Transaction tranid running program program name term termid has lost contact with its coordinator system during syncpoint and has abended with code ASP1. The unit of work is shunted until contact is restored{. EXCI job = }exci_id. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. The coordinator of the syncpoint is not this CICS system but is remote.

Transaction tranid has lost contact with its coordinator system during the critical period of syncpoint processing known as the 'indoubt window'.

In accordance with the transaction definition (WAIT YES), the unit of work is not completed. It is allowed to wait for resynchronization with the coordinator system. The transaction is abnormally terminated with abend code ASP1. The unit of work is shunted to await the return of the coordinator system.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier, sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2201 is sent to the terminal user. Normal abend processing continues.

User response:

Refer to explanation of abend code ASP1.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2232
date time applid Transaction tranid running program program name term termid has lost contact with its coordinator system during syncpoint and has abended with code ASPO. All updates will be unilaterally committed{. EXCI job = }exci_id. condmsg
Explanation:

Transaction tranid has lost contact with its coordinator system during the critical period of syncpoint processing known as the 'indoubt window'. The transaction is abnormally terminated with abend code ASPO.

In accordance with the transaction definition (WAIT NO and ACTION COMMIT), all recoverable updates performed by the unit of work are unilaterally committed. Note that integrity of updates may be lost since the coordinator system may either commit or back out its changes.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system termid is a terminal identifier (transaction routing) or a session identifier, sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2202 is sent to the terminal user. Normal abend processing continues.

User response:

None. In accordance with the transaction definition, all updates are unilaterally committed.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2233
date time applid Transaction tranid running program program name term termid has lost contact with its coordinator system during syncpoint and has abended with code ASPP. All updates will be unilaterally backed out{. EXCI job = }exci_id. condmsg
Explanation:

Transaction tranid has lost contact with its coordinator system during the critical period of syncpoint processing known as the 'indoubt window'. The transaction is abnormally terminated with abend code ASPP.

In accordance with the transaction definition (WAIT NO and ACTION BACKOUT), all recoverable updates performed by the unit of work are unilaterally backed out. Note that integrity of updates may be lost since the coordinator system may either commit or back out its changes.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier, and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2203 is sent to the terminal user. Normal abend processing continues.

User response:

None. In accordance with the transaction definition, all updates are unilaterally backed out.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

Start of changeDFHAC2234End of change
Start of changedate time applid A commit failure has occurred during syncpoint processing for transaction tranid, terminal termid. The transaction will be allowed to complete normally {. EXCI job = }exci_id. condmsgEnd of change
Explanation:

Start of changeAn application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources local to this CICS system, for example files, temporary storage, or transient data, have been updated. A failure occurred during phase 2 of the syncpoint protocol for a local resource owner. The affected unit of work has recorded its outcome (either forwards or backwards) on the system log, but the resources managed by the local resource owner that failed will remain locked.End of change

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

termid is a terminal identifier (transaction routing) or a session identifier.

System action:

If possible, message DFHAC2204 is sent to the terminal user. For an EXEC CICS SYNCPOINT, processing completes normally and processing continues with the next unit of work. For EXEC CICS RETURN, the transaction completes normally.

Start of changeResources affected by the failure remain locked and the unit of work is shunted.End of change

Start of change
User response:

Refer to earlier messages issued by the local resource owner to determine the cause of the failure.

End of change
Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2235
date time applid A backout failure has occurred during syncpoint processing for transaction tranid, terminal termid. The transaction will be allowed to complete normally {. EXCI job = }exci_id. condmsg
Explanation:

An attempt to back out a unit of work has suffered a backout failure. For the local resource owner(s) that suffered the backout failure, the resources updated by the unit of work remain locked. All other resources are backed out.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

termid is a terminal identifier (transaction routing) or a session identifier.

System action:

If possible, message DFHAC2205 is sent to the terminal user. For an EXEC CICS SYNCPOINT, processing completes normally and processing continues with the next unit of work. For EXEC CICS RETURN, the transaction completes normally.

Resources affected by the backout failure remain locked and the unit of work is shunted.

User response:

Refer to an earlier messages issued by the local resource owner to determine the cause of the backout failure.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2236
date time applid Transaction tranid abend secondary abcode in program program name term termid. Updates to local recoverable resources will be backed out{. EXCI job = }exci_id. condmsg
Explanation:

Transaction tranid is abnormally terminated with abend code abcode in program progname. Any changes to recoverable resources in the local system that have been performed by the current unit of work are backed out.

EXCI Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier, and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

When this message is issued in the Terminal Owning region because a remote transaction has failed, there may be no recoverable resources to be backed out in the local system. In this case, the conditional message will tell you whether or not resources in the remote system have been backed out.

Program progname will be unknown when the message is issued in a Terminal Owning region.

System action:

If possible, message DFHAC2206 is sent to the terminal user. Normal abend processing continues.

User response:

See the description of the abend code abcode for guidance. In a transaction routing environment, the original cause of the failure is usually indicated in the conditional message. If abcode is not a CICS abend, it is a user code, in which case you should consult the programmer responsible for this area.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, secondary abcode,program name, termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2245
date time applid A CICS-generated syncpoint request could not be completed normally because a connected system has requested that the unit of work be rolled back. Transaction tranid running program program name term termid has been abnormally terminated with code ASPF{. EXCI job = }exci_id. condmsg
Explanation:

CICS has been unable to complete an internally generated syncpoint request because a connected system has notified it that the unit of work must be rolled back. (This may also occur as a result of a session failure or a protocol error).

Transaction tranid is abnormally terminated with abend code ASPF in program progname. Any changes to recoverable resources that have been performed by the current unit of work are backed out.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier, and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2215 is sent to the terminal user. Normal abend processing continues.

User response:

Determine why the connected system sent the indication to roll back the unit of work.

Resubmit the transaction after the cause of the indication to roll back has been removed.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

Start of change
DFHAC2246
date time applid Transaction termination processing could not be completed normally because a connected system has requested that the unit of work be rolled back. {. EXCI job = }exci_id. condmsg
Explanation:

A transaction has issued an EXEC CICS RETURN in backout required program state. The backout required program state is set when an application receives a backout request on a protected conversation.

Recoverable resources updated by the unit of work are backed out and locks released.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier, and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2216 is sent to the terminal user. Termination processing continues.

User response:

To avoid the error, the application should code an EXEC CICS SYNCPOINT command before the EXEC CICS RETURN. A syncpoint issued in 'backout required' program state results in a backout being performed, and the ROLLEDBACK condition returned on the EXEC CICS SYNCPOINT command. If this condition is then handled, a subsequent EXEC CICS RETURN will complete successfully.

Resubmit the transaction after the cause of the indication to roll back has been removed.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, termid, {1=. EXCI job = }, exci_id, condmsg

End of change
DFHAC2247
date time applid Transaction tranid running program program name term termid has requested rollback, but was using a type of processing for which rollback is not supported. The transaction has been abnormally terminated with code ASP8 {. EXCI job = }exci_id. condmsg
Explanation:

An application requested syncpoint rollback, but was using a type of processing that does not support rollback, for example LU6.1.

Transaction tranid is abnormally terminated with abend code ASP8 in program progname. Any changes to recoverable resources that have been performed by the current unit of work will be backed out.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system termid is a terminal identifier (transaction routing) or a session identifier, sysid is the identifier of the linked CICS system, and the display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2217 is sent to the terminal user. Normal abend processing continues.

User response:

Refer to explanation of abend code ASP8.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2248
date time applid Transaction tranid running program program name term termid has failed with abend ASP7 following the failure of a local resource owner in the prepare phase of syncpoint. Updates will be backed out{. EXCI job = }exci_id. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources local to this CICS system, for example files, temporary storage, transient data, have been updated, and so the local resource owners have been sent a syncpoint request. A local resource owner has replied 'No' to a request to 'Prepare', during the two phase syncpoint protocol.

Transaction tranid is abnormally terminated with abend code ASP7 in program progname. Any changes to recoverable resources that have been performed by the current unit of work will be backed out.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier, and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2218 is sent to the terminal user. Normal abend processing continues.

User response:

Refer to explanation of abend code ASP7.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2249
date time applid Transaction tranid running program program name term termid has failed with abend ASP7 following the failure of a remote system in the prepare phase of syncpoint. Updates will be backed out{. EXCI job = }exci_id. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources remote to this CICS system, for example files, temporary storage, transient data on remote CICS systems, or database managers communicating via the RMI, have been updated, and so the remote resource owners have been sent a syncpoint request. A remote resource owner has replied 'No' to a request to 'Prepare', during the two phase syncpoint protocol.

Transaction tranid is abnormally terminated with abend code ASP7 in program progname. Any changes to recoverable resources that have been performed by the current unit of work will be backed out.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS Interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system termid is a terminal identifier (transaction routing) or a session identifier, and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2219 is sent to the terminal user. Normal abend processing continues.

User response:

Refer to explanation of abend code ASP7.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2250
date time applid The coordinator system has indicated that the current unit of work is to be backed out. Transaction tranid running program program name term termid has been abnormally terminated with abend ASP3{. EXCI job = }exci_id. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. The local unit of work is part of a larger unit of work, and is not the coordinator in the syncpoint. The coordinator is either in a remote system or is another unit of work in the local system (if the transaction is the result of a RUN SYNCHRONOUS command). During the syncpoint protocol the coordinator has decided that the unit of work cannot be committed and must be backed out.

Transaction tranid is abnormally terminated with abend code ASP3 in program progname. Any changes to recoverable resources that have been performed by the current unit of work are backed out.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used this, can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system termid is a terminal identifier (transaction routing) or a session identifier, and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2220 is sent to the terminal user. Normal abend processing continues.

User response:

Refer to the coordinator system to determine the reason why the unit of work was backed out.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2251
date time applid Transaction tranid running program program name term termid has failed with abend ASPQ. Syncpoint commit processing has failed while communicating with a remote system{. EXCI job = }exci_id. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources remote to this CICS system such as files, temporary storage, and transient data on remote CICS systems have been updated, and so the remote resource owners have been sent a syncpoint request. A failure occurred during phase 2 of syncpoint protocol.

Transaction tranid is abnormally terminated with abend code ASPQ in program progname. Recoverable resources have successfully been committed but a subsequent error occurred.

EXCI job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of jobname.stepname.procname - MVSid and identifies the EXCI client job. The stepname and procname may be omitted. MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS; not a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier, sysid is the identifier of the linked CICS system, and the display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2221 is sent to the terminal user. Normal abend processing continues.

User response:

Refer to associated messages already issued by the communication components of CICS to determine the cause of the intersystem session problem.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2252
date time applid Transaction tranid in program program name term termid has lost contact with its coordinator system during syncpoint processing. No updates have been performed by this system; it has abended with code ASPR{. EXCI job = }exci_id. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. The coordinator of the syncpoint is not this CICS system but is remote.

Transaction tranid has lost contact with its coordinator system during the critical period of syncpoint processing known as the 'indoubt window'. However no recoverable resources have been updated by this system and so there is no data integrity problem.

Exci Job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of 'jobname.stepname.procname - MVSid' and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier, and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2222 is sent to the terminal user. Normal abend processing continues.

User response:

Refer to messages on the remote system to determine if the remote resources were backed out or committed.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2253
date time applid Transaction tranid running program program name term termid has failed with abend ASP2 due to the links to the remote systems being in an invalid state. Updates will be backed out{. EXCI job = }exci_id. condmsg
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. Resources remote to this CICS system, for example files, temporary storage, transient data on remote CICS systems, or database managers communicating via the RMI, have been updated, and so the remote resource owners would be sent a syncpoint request. The links to the remote resource owners are in an invalid state to be sent the PREPARE request of the two phase syncpoint protocol.

Transaction tranid is abnormally terminated with abend code ASP2 in program progname. Any changes to recoverable resources that have been performed by the current unit of work are backed out.

Exci job =exci_id is added when tranid is a server transaction running on behalf of a non CICS job using the external CICS interface (EXCI). The exci_id consists of jobname.stepname.procname - MVSid and identifies the EXCI client job. The stepname and procname may be omitted. The MVSid identifies the MVS system on which the EXCI client job is running. If MRO/XCF is being used, this can be different from the MVS system on which this CICS system is running. The MVSid is the SMF system identification (SID), hence the MVSid will be omitted if SMF is not active. Terminal termid represents the connection between the EXCI client and CICS rather than a real terminal.

In the case of an MRO or an ISC APPC (parallel sessions) connected system, termid is a terminal identifier (transaction routing) or a session identifier and sysid is the identifier of the linked CICS system. The display ends with the termination message condmsg issued by the linked system.

System action:

If possible, message DFHAC2223 is sent to the terminal user. Normal abend processing continues.

User response:

See the explanation of abend code ASP2 for guidance.

Destination:

CSMT

Modules:

DFHTFP

XMEOUT Parameters: date, time,applid, tranid, program name,termid, {1=. EXCI job = }, exci_id, condmsg

DFHAC2259
date time applid Transaction tranid abend primary abcode in program program name term termid DFHPEP not linked.
Explanation:

Transaction tranid is abnormally terminated with abend code abcode. An error occurred in attempting to link to the user-written program error program (DFHPEP). The error prevented DFHPEP from being given control.

If CICS terminates abnormally because of a program control restart failure, this message can appear during shutdown.

System action:

Depending on the reason for the failure, CICS may abnormally terminate or continue.

User response:

The transaction abend code, abcode, gives the reason for the original transaction failure.

Determine why DFHPEP could not be invoked. It may be disabled.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid, primary abcode,program name, termid

DFHAC2260
date time applid Transaction tranid disabled by DFHPEP.
Explanation:

Transaction tranid, which has abnormally terminated, has been disabled. This is either as a result of user code in DFHPEP, or because the transaction has abended with abend ASRD or ASRE and DISMACP=YES has been specified (or allowed to default) in the startup parameters. No further use can be made of transaction tranid.

System action:

Processing continues.

User response:

Correct the cause of the abnormal termination and enable the transaction.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid

DFHAC2261
System sysid sent message (sense code cccccccc). 'tacbmsg'.
Explanation:

A transaction, which has abnormally terminated, has received a negative response and an explanatory warning message from system sysid. The message tacbmsg is supplied from the remote system.

System action:

Processing continues.

User response:

Correct the reason for the abnormal termination in the remote system and run the transaction again.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2262
date time applid System sysid sent message (sense code cccccccc). tacbmsg
Explanation:

A transaction, which has abnormally terminated, has received a negative response and an explanatory warning message from system sysid. The message tacbmsg is supplied from the remote system.

Start of changeThe tacbmsg may include the following CICS defined sense codes:

'A0000100'x - session failure
'A0010100'x - read timeout
'A0010000'x - deadlock timeout
End of change
System action:

Processing continues.

User response:

Correct the reason for the abnormal termination in the remote system and run the transaction again.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, sysid, cccccccc, tacbmsg

DFHAC2263
date time applid Transaction tranid abend primary abcode in program program name term termid DFHPEP has abnormally terminated.
Explanation:

Transaction tranid has abended and the abnormal completion program (DFHACP) has linked to the user-written error program (DFHPEP). The error program has also abended.

System action:

Processing continues.

User response:

The transaction abend code abcode gives the reason for the original transaction failure. Correct the cause of the abnormal termination in the error program and run the transaction again.

Destination:

CSMT

Modules:

DFHACP

XMEOUT Parameters: date, time,applid, tranid, primary abcode,program name, termid

DFHAC2603
Syst.sense systsense,termid,taskid, No authorization
Explanation:

An operator has attempted to execute a transaction for which the operator was not authorized. Alternatively, the operator’s authorization was set to the capability of the default user and the requested transaction has a security value greater than 1.

System action:

Other processing continues.

User response:

Either sign on or confirm authority to enter this transaction as appropriate. See messages DFHAC2002 and DFHAC2003 for further information.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2605
Syst.sense systsense,termid,taskid, Insufficient resource
Explanation:

The system was unable to execute the transaction at this time.

System action:

The transaction is purged.

User response:

Resubmit the transaction later.

Destination:

Terminal End User

Modules:

DFHACP

DFHAC2606
Syst.sense systsense,termid,taskid, Function not executable
Explanation:

Either the transaction was not valid during system quiesce, or the transaction has been disabled.

System action:

The system action is error specific. For an invalid transaction during system quiesce, refer to the System Action of message DFHAC2007.

For a transaction that has been disabled, refer to the System Action of message DFHAC2008.

User response:

The user response is error specific.

For an invalid transaction during system quiesce, refer to the User Response of message DFHAC2007. For a transaction that has been disabled, refer to the User Response of message DFHAC2008.

Destination:

Terminal End User

Modules:

DFHACP

[[ Contents Previous Page | Next Page Index ]]