User Profile Requirements

Any user ID used to run a TIBCO EMS Client for z/OS (MVS) application must have a valid RACF OMVS segment defined. Therefore, if you are starting such an application as:

• Batch job, verify that the submitter's user ID has a valid OMVS segment defined.
• Started task, verify that the user ID assigned by the RACF STARTED class or ICHRIN03 started procedures table has a valid OMVS segment. Verification can be done by using the RACF LISTUSER command.

TSO LISTUSER TIBCO01 OMVS NORACF

USER=TIBCO01

OMVS INFORMATION
UID= 0000012345
HOME= /tibco/tibco01
PROGRAM= /bin/sh
CPUTIMEMAX= NONE
ASSIZEMAX= NONE
FILEPROCMAX= NONE
PROCUSERMAX= NONE
THREADSMAX= NONE
MMAPAREAMAX= NONE
***

For best results, run TIBCO messaging applications with a user ID without resource limits specified in the OMVS segment, as shown in the previous example user ID TIBCO01, so that TIBCO messaging applications can run within the limits defined to the overall system in BPXPRMxx. There are no special requirements for UID, HOME, or PROGRAM to run TIBCO messaging applications.

If an existing user ID does not have an OMVS segment, you can define one by using the RACF ALTUSER command. For more information about the use of the various RACF commands and the setup of an OMVS segment, see SecureWay Security Server RACF Command Language Reference or equivalent documentation published by IBM.

If the installation is using the FACILITY class profile BPX.DEFAULT.USER instead of defining OMVS segments for every user ID, the user ID defined in the FACILITY class profile BPX.DEFAULT.USER must be examined to ensure that it does not have resource limits defined if the user submits TIBCO EMS jobs. For more information about managing the FACILITY class profile BPX.DEFAULT.USER, see the SecureWay Security Server RACF Security Administrator's Guide published by IBM.