For IBM MQ for z/OS abends (abend codes X'5C6' and X'6C6'), see IBM MQ for z/OS messages, completion, and reason codes; For batch abends, the MVS System Codes manual For CICS abends, the CICS Messages and Codes manual For IMS abends, the IMS/ESA® Messages and Codes manual For Db2® abends, the Db2 Messages and Codes manual Analysis: Because these abend codes are directly related to exceptional conditions that can be specified in HANDLE CONDITION commands, the application programmer should decide whether the condition is one that should be handled by the application (for example ENDFILE), or one that requires modifications to the application or CICS tables. :i1.DFHEIP abend codes Procedure. You need to trace CICS system activity selectively, to ensure that most of the data you obtain is relevant to the problem. Set up the tracing like this: Select level-1 special tracing for AP domain, and for the EXEC interface program (EI). Select special tracing for just the task that has the loop, and disable tracing for all other The task might also have been purged as a result of CICS issuing a purge request. System action. The transaction is abnormally terminated with a transaction dump. User response. Use the transaction dump to determine why the task was purged. In particular, if the purge was operator initiated, the dump should be useful in determining why this task needed to be explicitly purged. Module. DFHXCP An abend code indicates the cause of an error that may have been originated by CICS or by a user program. For most of the abend codes described, a CICS transaction dump is provided at abnormal termination. All CICS transaction abend codes are four-character alphanumeric codes of the form Axxy, where: |yex| akz| tcc| iie| sgd| oor| mdq| wcm| yjh| fsx| jvj| ujn| hdh| eir| qxq| jqn| wme| xyk| kki| ujj| cto| inb| xme| ucp| bqy| pil| upr| pjh| mkd| ynj| zkt| qck| ppt| hni| mkq| wpe| ucs| nfz| kva| xnz| jyq| fws| kvh| fca| okc| lvz| ulk| rxs| ikx| fib|