Using a BTS audit trail for problem determination

You might want to create an audit trail for the BTS processes and activities that are used by a service flow to run in your CICS® systems. An audit trail can assist in problem determination.

About this task

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.

Procedure

  1. Use the AUDITLOG and AUDITLEVEL attributes of the PROCESSTYPE resource for the service flow to control the audit logging that takes place and where the logs are stored. Use caution when creating audit trails in production because they can significantly affect system performance.
    1. 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.
    2. 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
      Changing the audit logging with this command 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 write audit records to the audit log.
  2. To read the records in the audit log, use the sample job DFHMABAP, which is located in the SCIZSAMP samples library. This job runs the DFHATUP utility. See Audit file dump JCL, DFHMABAP to view the sample JCL.

What to do next

For detailed information about audit levels and configuration, see the CICS Business Transaction Services manual.


aboutthebtsauditfile.html | Timestamp icon Last updated: Sunday, 4 June 2017