This part describes how to implement security for CICSPlex® SM.
Implementing CICSPlex SM security
This topic explains how to implement RACF® security for CICSPlex SM.
The first section provides general information to help you determine who
needs access to the various CICSPlex SM functions.
The remaining sections provide detailed information on defining CICSPlex SM class
names, using resource names, activating security, and refreshing RACF profiles.
Invoking a user-supplied external security manager CICSPlex SM provides
an interface to an external security manager (ESM), which can be user-supplied
or can be Resource Access Control Facility (RACF).
Writing an API security exit CICSPlex SM provides
a security validation exit that allows you to control access to a CMAS from
application programming interface (API) programs. The security routine
is called when security is active in a CMAS, but the environment in which
the API program is running does not provide security of its own.CICSPlex SM attempts
to extract user authorization data from the environment. If authorization
data does not exist, the security routine is called.
Example tasks: security
This topic provides examples of typical security setup tasks that
you can use as a model for your own.