Plan your z/OS UNIX or UNIX System Services environment
Certain processes within the IBM MQ queue manager (MSTR), channel initiator (CHIN), and mqweb server use z/OS UNIX or UNIX System Services (USS) for their normal processing. Plan your configuration if we do not want to use the default USS configuration.
No special action or customization is necessary in order for IBM MQ to use UNIX services as long as a system-wide default OMVS segment has been set up.
If we do not want IBM MQ to invoke USS using the guest or default UID and OMVS segment, define a new OMVS segment. The OMVS segment you define can be modeled on the default segment, as IBM MQ requires no special permissions, and does not run within USS as a superuser.
The MSTR and CHIN started task user Ids also need a UID in the RACF OMVS segment.
Note: Although the MSTR and CHIN jobs make use of USS facilities (for example, to interface with TCP/IP services), they do not need to access any of the content of the USS file system shipped by IBM MQ. As a result, the MSTR and CHIN jobs do not require any configuration to specify the path for the USS file system.The mqweb server, which hosts the IBM MQ Console and REST API, makes use of files in the IBM MQ installation directory in the USS file system. It also needs access to another file system which is used to store data such as configuration and log files. The mqweb started task JCL needs to be customized to reference these USS file systems.
The content of the IBM MQ directory in the USS file system is also used by applications connecting to IBM MQ. For example, applications using the IBM MQ classes for Java or IBM MQ classes for JMS interfaces.
See the following topics for the relevant configuration instructions:- Environment variables relevant to IBM MQ classes for Java
- IBM MQ classes for Java libraries
- Set environment variables
- Configure the Java Native Interface (JNI) libraries
Parent topic: Plan the IBM MQ environment on z/OS