Errors that are detected by an Adapter service, and written to
the CMAQ transient data queue (TDQ), are captured in an error file to help
with troubleshooting problems.
The error file contains relevant information related to the processing
that was taking place when the error occurred. It includes, but is not limited
to, capturing error information for the following components:
- VSAM files
- CICS® BTS
APIs and BTS data-containers
- CICS APIs
- FEPI
- WebSphere® MQ
- Link3270 bridge mechanism
- XML processing and parsing
- Temporary storage queues (TSQ)
- Run time processing and abends
You can access the contents of the error file by dumping it using
the provided sample JCL job DFHMAMED. This job runs the dump utility DFHMAEUP,
which formats the file so that you can read it to help with problem determination.
The dump of the error file contains two sections:
- A static section, that contains a standard set of fields to provide key
information about the error, no matter which type of error has been captured.
- A dynamic section, that contains specific information related to the type
of error that has been captured. The contents of this section can vary.
Errors that occur outside of the control of the Adapter service
are not written to the error file. For example, the following types of errors
would not be written to the error file:
- Errors in the WebSphere MQ or CICS environments that occur outside of
the CICS SFR environment.
These errors would be reported in the WebSphere MQ or CICS environments.
- Errors in CICS applications.
- Errors in WebSphere MQ-enabled
applications that are invoked by a WebSphere MQ server adapter in the
Adapter service.
- Errors in target DPL programs that are invoked by a DPL server adapter
in the Adapter service.