Dealing with the problem

Following on from classifying your problem, this section describes how to find the cause of problems in each area.

Dealing with transaction abend codes
When a CICS transaction abends (ends abnormally), a transaction abend message and an abend code of four alphanumeric characters are sent to CSMT, the CEMT transient data destination (or your site replacement).
Dealing with CICS system abends
This information provides guidance about gathering essential information about CICS system abends.
Dealing with waits
This section gives you information about what to do if you are aware that a task is in a wait state, or if CICS has stalled.
How tasks are made to wait
The suspension and resumption of tasks in a CICS system are performed by the dispatcher domain, usually on behalf of some other CICS component. If the exit programming interface (XPI) is being used, it can be at the request of user code.
Dealing with loops
A loop is a sequence of instructions that is executed repetitively. Loops that are coded into applications must always be guaranteed to terminate, because otherwise CICS might experience symptoms such as high CPU usage and transaction abends.
Dealing with performance problems
When you have a performance problem, you might be able to find that it is characterized by one of the following symptoms, each of which represents a particular processing bottleneck.
Dealing with incorrect output
Incorrect output has been categorized into a number of areas. Look at the appropriate section to diagnose why this problem is occurring.
Dealing with storage violations
A storage violation occurs when a transaction attempts to modify storage that it does not own.
Dealing with external CICS interface (EXCI) problems
Dealing with TCP/IP connectivity problems
If you are experiencing TCP/IP connectivity problems, read the following information to find out how to diagnose the problem.
Dealing with log manager problems
The CICS log manager uses services provided by the MVS™ logger to support the logging and journaling of data to the CICS system log, forward recovery logs, autojournals, and user journals.

Parent topic: Troubleshooting and support