Skip to Content
Information
Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Configuring the File Utility Audit Trail

The Code Debug CICS File Utility Audit Trail lets a site keep track of any changes to its resources that are made with the Code Debug File Utility. These changes can include adds, updates, and deletes of:

  • data set records
  • temporary storage records and queues
  • transient data records
  • IMS segments
  • Db2 tables

The File Utility Audit Trail also records access modifications made to data sets and transient data queues, including opens, closes, and request modifications such as enabling or disabling add or update capabilities with the CICS Data set List screen (5.1.1).

The Code Debug File Utility Audit Trail writes formatted data to a Generation Data Group (GDG) data set. You can tailor the Facility’s output to suit your site’s specific needs. Use of a GDG ensures uninterrupted recording even if a data set fills up, and it allows for easy data set backup.

This section explains how to set up—or disable—the File Utility Audit Trail. Information is also provided on how to start and stop logging and switch to a new generation data set. Extensive examples of entries are used to illustrate how Code Debug formats the information captured by the File Utility Audit Trail.

Follow the step-by-step instructions in  Setting Up the File Utility Audit Trail to enable the Code Debug CICS File Utility Audit Trail. If your site does not want to use the File Utility Audit Trail, go to Disabling the File Utility Audit Trail.

This role involes Code Debug CICS Installer.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI DevX Code Debug for CICS 17.02