XAPPC, XEJB, and XUSER

The syntax of the XAPPC, XEJAB, and XUSER system initialization parameters is slightly different from that of the other Xname parameters. You can only specify YES or NO.

XAPPC=YES indicates that you want session security for APPC sessions. If XAPPC=YES is specified and the APPCLU class is not activated in RACF, CICS fails to initialize. For more information on what happens in these circumstances, see CICS initialization failures related to security.

XAPPC enables RACF LU6.2 bind-time (also known as APPC) security. For more information, see Bind-time security with LU6.2.

For more information on the APPCLU class, see Defining profiles in the APPCLU general resource class.

XEJB specifies whether support of security roles is enabled. For more information, see Java™ Applications in CICS®.

XUSER activates surrogate user security, and AUTHTYPE checking for DB2. For more information, see Surrogate user security. If XUSER=YES is specified and the SURROGAT class is not activated in RACF, CICS fails to initialize.