Here is the format of the security keys that the CICS® Configuration Manager server creates to check a user's authority to manipulate resource definitions:
If the resource type does not have a unique name, then specify a "-" (hyphen) character as the name parameter.
For example, specify group as a hyphen and name as a hyphen for the CICSPlex® SM full-function BAS APPLDEF, RASINDSC, and SYSLINK resource types.
For descriptions of the fields in these keys, see API parameters.
For each resource definition, the Copy and Rename API commands create two security keys, and make two calls to the external security manager: one for the source resource definition, and another for the target resource definition.
For the Rename API command, the parameter for the CICS configuration is labelled "target" in both security keys because you can only rename a resource definition within the same CICS configuration.
To simplify group resource profile definitions, the resource definition name is the last qualifier in the security key: some resource types may contain a period (.) as part of the resource name.
As a starting point, consider temporarily defining
a general resource profile such as this:
CCVRES.**
(where CCVRES is
the prefix that you have chosen for the security keys)
with a universal access authority (UACC) of ALTER.
This enables you to activate security checking in CICS Configuration Manager and then continue
to work as before, while you define more specific general resource
profiles.
For examples of general resource profiles, and the
JCL to define those profiles in a RACF environment, see member CCVXSAF3
of the sample library SCCVSAMP.
For more examples of general resource profiles, see Example security scenario.