Defining the default CICS userid to RACF
For each CICS® region where you specify SEC=YES, define a RACF® user profile whose userid matches the value of the DFLTUSER system initialization parameter.
For example, if you specify DFLTUSER=NOTSIGND, define a RACF user profile named NOTSIGND. If you do not specify a value for the DFLTUSER parameter, the CICS-supplied default userid is CICSUSER. Define a RACF user profile named CICSUSER.
- The default CICS userid requires different security attributes (such as membership in RACF groups).
- The default CICS userid requires different operator data (CICS segment of the RACF user profile).
- The default CICS userid requires a different default language (LANGUAGE segment of the RACF user profile).
ADDUSER CICSUSER DFLTGRP(group_id) NAME(user_name)
OWNER(userid or group)
PASSWORD(password)
CICS(OPCLASS(1,2,...,n) OPIDENT(identifier) OPPRTY(priority)
TIMEOUT(timeout_value) XRFSOFF(xrf_sign-off_option))
The security administrator should always define the password for default userids and started tasks, instead of allowing it to default.
Each CICS region should use its own default user, as an aid to debugging. Set up a RACF default user group to keep the definitions similar.
PERMIT CICSUSER.DFHINSTL CLASS(SURROGAT) ID(cics_region_userid)
During startup, CICS "signs on" the default userid. If the default user sign-on fails (because, for example, the userid is not defined to RACF), CICS issues message DFHXS1104 and terminates CICS initialization.
- The CICS segment of the default user's RACF user profile
- Built-in CICS system default values
CICS also assigns the security attributes of the default userid to any “trigger level transactions” that are initiated for transient data queues without a USERID parameter.
- Give the default user access to the region's APPLID. See Authorizing access to the CICS region.
- Give the default user access to the CICS-supplied transactions that are intended to be used by everybody. See the definitions in Identifying CICS terminal users, especially those transactions that are recommended for inclusion in the ALLUSER example group of transactions.