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.

Implementing the File Utility Security Exit


If your site uses an external security manager such as RACF, CA ACF2, or CA Top Secret, you may want to implement the Code Debug CICS file security exit to ensure full security access to file resources.

The File Utility Security Exit enhances outside security processes and protects areas not usually protected by other vendor's security packages. You can code macros and calls to your external security manager and use BMC-supplied fields to access resources not traditionally protected by external security managers.

The information provided here is important for system programmers who want to secure access to their files. The File Utility Security Exit is discussed in the following topics:

This task requires the following persons:

  • Code Debug CICS Installer
  • z/OS Security Administrator.

 

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