z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


026

z/OS MVS System Codes
SA38-0665-00

026

Explanation

Cross-system extended services (XES) encountered an error. See z/OS MVS Diagnosis: Reference for more information on diagnosing sysplex problems.

A hexadecimal reason code in register 15 explains the error:
Code
Explanation
08110102
XES has terminated the task or address space associated with a coupling facility structure connector to resolve a hang in a structure-related process, which is caused when the connector failed to provide a required response within the time specified by the CFSTRHANGTIME interval defined in the SFM policy (over and above the time required to determine that the response is overdue, approximately 2 minutes).

Capture the dump produced by this ABEND and contact the owner of the application with which the terminated connector was associated to determine the cause of the hang.

08118001
XES has recognized that an overdue connector response has caused a hang in a structure-related process. This ABEND is issued to capture diagnostic data related to the overdue response.

If the SFM policy specifies a non-zero value for CFSTRHANGTIME to limit the time that an overdue connector response may remain outstanding, this ABEND indicates that XES is about to initiate potentially disruptive action to resolve the hang.

If the connector does not provide the required response before the interval defined by the CFSTRHANGTIME specification elapses, the system will take progressively more aggressive actions to resolve the hang, which may include terminating the connector. Connector, termination, if required, will be accompanied by a second ABEND X'026', this time with reason code X'08110102', to collect connector and application data pertaining to the hang.

0A060002
XES processing could not prevent SRB to task percolation however its processing has continued successfully and no action need be taken on the part of the user.
0C010101
Error in user's Complete Exit. The connector will be terminated. Review the exit processing of the application. The system does not issue a dump.
0C150101
Error in user's Contention Exit. The connector will be terminated. Review the exit processing of the application. The system does not issue a dump.
0C150103
Return code error from user's Contention Exit. The user specified that the Contention Exit was to be deferred during rebuild processing, but the structure was not being rebuilt. The connector will be terminated. Review the exit processing of the application. The system does not issue a dump.
0C340102
Error in user's Complete Exit for a list or cache connection. The connection is terminated.
0C3F0101
Error in user's Notify Exit. The connector will be terminated. Review the exit processing of the application. The system does not issue a dump.
0C5A0003
XES processing could not prevent SRB to task percolation. However, its processing has continued successfully and no action need be taken on the part of the user.
0C5A0004
XES processing could not prevent SRB to task percolation. However, its processing has continued successfully and no action need be taken on the part of the user.
0C680101
Error in user's Notify Exit. The connector will be terminated. Review the exit processing of the application. The system does not issue a dump.
0E0A0101
Error in user's List Transition Exit. The connector will be terminated. Review the exit processing of the application. The system does not issue a dump.
0E0D0001
Unexpected return code from user's Event Exit. Register 0 contains the event code (EEPLevent) presented to the user's Event Exit. Register 2 contains the return code (EEPLretcode) returned by the user's Event Exit. See IXLYEEPL mapping macro for EEPL fields. The connector will be terminated. Review the exit processing of the application. The system does not issue a dump.
0E0D0101
Error in user's Event Exit. The connector will be terminated. Review the exit processing of the application. The system does not issue a dump.

System action

Additional messages explaining the error may precede the ABEND. If there is a hexadecimal value of '01' in the third byte of the reason code the connector issuing the IXLCONN service will be terminated by the system. The system issues an SVC dump, unless the abend is related to the failure of a user exit.

Operator response

The following reason codes represent errors internal to the XES component. Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.

Reason Codes:
02040001 020A0001 020D0001 02120001 03200001
05010001 05060001 070B0001 07160001 081A0001
09100001 09100002 09100003 09100004 0A010001
0A010002 0A010102 0A020102 0A040103 0A060101
0A060103 0A090101 0A0D0001 0A0D0002 0A0D0004
0A060003 0A0D0101 0A130103 0A130104 0A130106
0A160001 0A160101 0A160102 0C080001 0C090001
0C090020 0C0A0001 0C0B0106 0C0C0105 0C0D0101
0C0E0001 0C130101 0C170101 0C190001 0C1Cxxxx
0C1D0101 0C21xxxx 0C23xxxx 0C26xxxx 0C2A0001
0C2A0002 0C2A0003 0C2A0004 0C2A0005 0C2A0006
0C2A0007 0C2A0008 0C2A0009 0C2A000A 0C2A000B
0C2A000C 0C2A000D 0C2A000E 0C2A000F 0C2A0010
0C2A0011 0C2A0012 0C2A0013 0C2A0014 0C2A0020
0C2D0001 0C2F0101 0C2F0102 0C30xxxx 0C340001
0C340002 0C340101 0C340103 0C340104 0C340105
0C340106 0C380001 0C380002 0C380003 0C380004
0C380005 0C380009 0C380106 0C380107 0C380108
0C390001 0C391013 0C3C0107 0C3C0108 0C400101
0C41xxxx 0C440101 0C460101 0C4A0101 0C4A0103
0C54xxxx 0C560002 0C540101 0C560001 0C560003
0C560004 0C560005 0C560150 0C5A0101 0C5A0102
0C5B1013 0C650001 0C670101 0C680102 0C6C0001
0C700102 0C740101 0C740103 0C760102 0C7C0001
0C7C0002 0C7C0003 0C830001 0C830002 0C830003
0C890101 0C890102 0C920002 0C950001 0C950102
0C950103 0C9E0001 0C9E0101 0D010001 0D010101
0D010102 0D010103 0D010104 0D070101 0D070102
0D070103 0D070104 0D070105 0D0C0001 0D0C0150
0D120101 0D120102 0D120103 0D120007 0D120008
0D120150 0D150004 0D150101 0D150102 0D150103
0D150150 0D180101 0D1C0001 0D1C0150 0E0A0102
0E0B0004 0E0C0103 0E0D0102 0E0F0101 0E120001
0E130004 0E130101 0E130102 11050001

System programmer response

Format the SVC dump with the following IPCS subcommands:
  • XESDATA, including all the reports at all levels - summary, detail, and exception.
  • CTRACE COMP(SYSXES) SUB((GLOBAL))
  • CTRACE COMP(SYSXES) SUB((individual-connections))

    You can determine the individual connections by issuing the CTRACE QUERY command to see the sub name traces associated with SYSXES.

Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the formatted SVC dump.

Source

Cross-system extended services (XES)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014