You might want to create an audit trail for the BTS processes and
activities that are used by an adapter service and run in your CICS® systems.
This can assist in problem determination.
Audit log records are written to an MVS™ logstream by the CICS log manager. You can read the records
offline using the CICS audit trail utility program DFHATUP.
- Use the AUDITLOG and AUDITLEVEL attributes of the PROCESSTYPE resource
for the adapter service to control the audit logging that takes place and
where the logs are stored. Although you can create audit trails
in production, you should use caution as this can significantly affect system
performance.
- Use the INQUIRE PROCESSTYPE command to check
that an audit log has been defined. If this attribute is not defined
for the resource, audit logging cannot take place. If an audit log is not
defined, delete the existing resource and create a new resource definition
with the AUDITLOG attribute specified.
- To enable or disable audit logging, or to change the type of
audit logging that is taking place, use the SET PROCESSTYPE command. The audit levels that you can select are:
- ACTIVITY
- FULL
- OFF
- PROCESS
This has no effect on any existing processes that
are running in the CICS system for that process type. Only new processes of
that process type perform write audit records to the audit log.
- To read the records in the audit log, use the sample job DFHMABAP
that is located in the SCIZSAMP samples library. This job runs
the DFHATUP utility. See Audit file dump JCL (DFHMABAP) to
view the sample JCL.
For detailed information about audit levels and configuration, see
the CICS Business
Transaction Services manual.