To activate CICS® Configuration Manager security checking:
When choosing or creating a class, consider the following:
The client interfaces have this maximum security key length because, in their API command requests, they exclusively use CICS configuration names (up to 8 characters) to refer to the location of resource definitions, never CSD file names (up to 44 characters). The format of security keys for API commands (see below) includes the location parameter that is specified by the API command request; using CICS configuration names keeps the security key length within 39 characters.
However, if you develop a custom client interface, then its API commands may refer to CSD file names. In this case, you need to choose or create a class that supports keys of up to 75 characters. You can also configure an optional security exit that is invoked before and after each SAF call. See the skeleton exit supplied in the CCVX0001 member of the sample library, SCCVSAMP.
CDTINFO(FIRST(ALPHA,NATIONAL,NUMERIC,SPECIAL),
OTHER(ALPHA,NATIONAL,NUMERIC,SPECIAL)
…)
The supplied resource class FACILITY allows special characters.
For API command security checking, consider temporarily defining a general resource profile such as this:
CCM.**
(where CCM is the prefix that you have chosen for the security keys)
with a universal access authority (UACC) of READ. 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. When you have finished defining specific profiles, delete this generic profile.
For more examples of the general resource profiles that you might want to define, see Example security scenario.