This topic provides examples of typical security setup tasks that
you can use as a model for your own.
Here are some general points that apply to all of the RACF® examples:
- Each RACF command
shown in these task examples must be issued once against every RACF database
in your CICSPlex® SM configuration.
So, if there are two unconnected RACF databases, one on MVS1 and one on
MVS2, each RACF command
must be issued twice (once on each system).
- In all of the RACF command examples, strings in lowercase must be
replaced by values suitable for your own enterprise. For example, you must
replace the string admin_user with the USERID of the administrator
responsible for security of the relevant CICSPlex SM resources.
- All of the RACF task
examples use the enhanced generic naming facility (**) of RACF. If you
don't use this at your enterprise, see the RACF documentation for information about
creating equivalent profiles.
- Operations and administration RACF groups have been used in these examples:
we recommend that you create such groups.
We're going to start by creating some RACF profiles to protect all CICSPlex SM functions
and resources. When we've done this, we'll permit access selectively to particular
users of particular resources.