User Profile Requirements

Any user ID for running a TIBCO messaging for z/OS application must have a valid RACF OMVS segment defined.

Verifications of OMVS segments vary depending on how you start a TIBCO messaging for z/OS application:
  • If you are starting such an application as a batch job, verify that the user ID of the submitter has a valid OMVS segment defined.
  • If you are starting such an application as a started task, verify that the userid assigned by the RACF STARTED class or ICHRIN03 started procedures table contains a valid OMVS segment. You can perform this verification with the RACF LISTUSER command, as follows: 
    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
***

TIBCO recommends running TIBCO messaging applications with a user ID without resource limits being specified in the OMVS segment. An example is userid TIBCO01, which enables TIBCO messaging applications to run within the limits defined to the overall system in BPXPRMxx. No special requirements are specified for UID, HOME, or PROGRAM to run TIBCO messaging applications.

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

If you use the FACILITY class profile BPX.DEFAULT.USER instead of defining an OMVS segment for each user ID during the installation, examine userid in the FACILITY class profile BPX.DEFAULT.USER to ensure that it does not have resource limits defined for TIBCO messaging jobs. For more information on how to manage the FACILITY class profile BPX.DEFAULT.USER, see the Security Server RACF Security Administrator's Guide published by IBM.