Implementing Security Exits

This section describes how to implement each type of security exit, and includes information for specific security environments such as, IBM® RACF, CA-ACF2, and CA-TOP SECRET.

Note: User specified program names are limited. For more information, refer to User Specified Program Limitation Feature.
Note: You must have the High-level Assembler to assemble the sample exits.
To avoid out-of-storage ABENDS in Connect:Direct® for z/OS®, examine all user exits to verify that all obtained storage either via GETMAIN or STORAGE OBTAIN is freed. For each GETMAIN/STORAGE OBTAIN that an exit issues, the exit must also issue a corresponding FREEMAIN/STORAGE RELEASE to avoid accumulating storage. If an exit opens a file, you may need to issue a FREEPOOL after the file is closed.