Troubleshooting BTS

Try these solutions for some of the more common problems that you might encounter when running a BTS system.

Dealing with stuck processes
Consider the causes of a stuck process, when it cannot proceed because it is waiting for an event that cannot, or does not, occur. You can use timers or process timers to restart a stuck process.
Dealing with activity abends
You can deal with activity abends by coding your application to try the failed activity again or compensate the siblings of the failed activity.
Dealing with unserviceable requests
An unserviceable request is a request that cannot currently be satisfied; for example, an activity that is not available, or the region on which the request is to run is not accessible.
Dealing with CICS failures
If one of your CICS regions fails, all BTS processes on the failing region are halted. Processes on other regions might also become stuck, because expected events are not generated. If a CICS region fails, you must perform an emergency restart.
Creating a BTS audit trail
You can create an audit trail for BTS processes and activities to track the progress of transactions. You can control the amount of audit logging. Follow the example to see a series of activations.
Examining BTS repository records
You can examine records on a BTS repository data set with the DFHBARUP utility, which takes a snapshot of your BTS system.
BTS messages
You can use BTS messages to help you understand and respond to BTS activities and issues.
Setting trace levels for BTS
Using system initialization parameters or the CETR transaction, you can use the CICS component codes to specify the level of standard and special tracing that you require for your BTS processes.
Extracting BTS information from a CICS system dump
You can use dump formatting keywords to extract BTS information from a CICS system dump.

Parent topic: Troubleshooting and support