The following checklist can help you to identify the source of
the problem that is occurring in the runtime environment.
About this task
For recommended responses to specific errors, see the applicable
sections of Messages and codes.
Procedure
- Do you have the latest APARs applied?
IBM® might have
already published a fix for your problem. See
About fixes and updates for
details on how to check for the latest available fixes.
- Does the problem occur when you are applying an APAR?
- Ensure that you are following the correct process to apply the
APAR.
- If you are following the correct process and still have difficulties,
contact IBM Software
Support.
- Are you having problems when running the postinstallation jobs?
For example, you receive a return code other than 0 when a job completes.
- Does the problem occur when you are deploying a service flow?
For example, the service flow installs in an unusable state.
- Check that the PROCESSTYPE resource for the service flow is
installed in the CICS region.
The name of the resource is the same
as the request name of the service flow.
- If the PROCESSTYPE resource has been discarded, reinstall it.
- Try to install the service flow again using the CMAN transaction.
- Does the problem occur when a service requester invokes a deployed
service flow?
When a problem occurs in the runtime environment,
errors are written to the CMAC transient data queue. The message contains
the details of the error.
- Analyze the message to determine if a server adapter is causing
the problem.
The
Error
field contains the message
ID. Read the
Messages and codes to find the
type of error that has occurred. Also take note of the
Program
field,
because it indicates the program in which the error occurred which might be
the name of a server adapter.
- If you receive a DFHMA06021E message, check
the request name to ensure that it is the name of deployed service flow.
Also check that the service flow properties file for the service flow
is in the deployment directory.
- Optional: Dump and analyze the CICS® BTS audit trail if you have configured
it for use.
- Debug your applications.
- Dump and analyze any CICS trace and dump information available.
- Use additional CICS-supplied transactions.
Results
If this checklist does not guide you to a resolution, contact IBM to report a problem. Before you contact IBM, you might have to collect additional diagnostic data. This data is required when reporting a problem to IBM and can increase the problem resolution time. For details on the information to collect and how to send it to IBM, see Collecting CICS troubleshooting data (CICS MustGather) for IBM Support.