z/OS MVS Planning: APPC/MVS Management
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Protecting the Generic User ID at Installation Time

z/OS MVS Planning: APPC/MVS Management
SA23-1388-00

Because the generic user ID applies to processing that must be isolated from the different conversation users, the generic user ID must be secure from unauthorized specification and modification in the TP profile. At the time of installation, your RACF® administrator must use the APPCMVS.TP.MULTI.genusrid profile in the RACF FACILITY class to protect the generic user ID and control access to TP profiles for multi-trans TPs. The command shown in Figure 1 prevents all users from adding or modifying multi-trans TP profiles with any generic user ID.

Figure 1. Protecting the Generic User ID
RDEFINE FACILITY APPCMVS.TP.MULTI.* UACC(NONE)

After issuing the RDEFINE command shown in Figure 1, your RACF administrator can permit individual users to define multi-trans profiles with a specific user ID. For example, if Bob needs to create a multi-trans TP profile with the generic user ID ADMIN, he must first get permission from a RACF administrator. Your RACF administrator would then issue the command shown in Figure 2.

Figure 2. Permitting Update Access to a Multi-trans TP
RDEFINE FACILITY APPCMVS.TP.MULTI.ADMIN UACC(NONE)
PERMIT APPCMVS.TP.MULTI.ADMIN CLASS(FACILITY) ID(BOB) ACCESS(UPDATE)

After receiving RACF UPDATE access, Bob can use the TPADD command to create a multi-trans profile with a generic user ID of ADMIN. For more information about the TPADD command see Using the APPC/MVS Administration Utility.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014