EYUXS1014I I   Task recovery starting for task nnnnn transaction cccc

Explanation

The CICSPlex SM task recovery TRUE, EYU9XSTR, executing in a CMAS or local MAS, encountered a terminating task that did not go through CICSPlex SM cleanup processing, where:
nnnnn
Is the task number
cccc
Is the transaction ID for the task

System action

CICSPlex SM cleanup processing will be attempted for the task. The results of this recovery processing will be reported after recovery is complete by message EYUXS1015I or EYUXS1016E.

User response

The most common causes for a CICSPlex SM task to not go through cleanup processing is if a monitor, interactive debugger, or EYU9WRAM program is being used to "KILL" tasks, either automatically or on demand, or otherwise cause an abnormal termination that does not go through normal CICS HANDLE ABEND processing (for example, issues EXEC CICS ABEND with the CANCEL option). If this message occurs without the benefit of one of the above, or if there is no subsequent EYUXS1015I or EYUXS1016E message to pair with this EYUXS1014I message, then collect as much of the following as possible and contact your IBM Support Center:
  • The complete job output.
  • the unformatted SVC dumps for any abends that may have occurred during the execution of the CMAS or MAS.
  • The unformatted AUXTRACE data sets (if the system is a MAS and AUXTRACE was not active in that system, collect the AUXTRACE data sets from the CMAS to which the MAS was connected).

Module

EYU9XSTR

Destination

Console and SYSPRINT



EYUXS1014I.html | Timestamp icon Last updated: Sunday, 4 June 2017