Configuring IBM® WebSphere® MQ on z/OS®

You must configure IBM® WebSphere® MQ on IBM® z/OS® to set up the required queues and namelists. Based on your system security requirement, you might need to grant permissions to enable HCL OneTest™ API to intercept the queue messages. From HCL OneTest™ API 9.1.1 onwards, you can do the required setup using the example configuration JCL templates (RITDEFN, RITCFGS, and RITCFGG) which are provided with the RIT.PROC.XMIT.BIN package.

Note: As of version 9.5.0, new namelists (COM.GREENHAT.EXIT.INTERCEPT, COM.GRENHAT.EXIT.DIVERT1, and COM.GREENHAT.DIVERT2) and a new queue (COM.GREENHAT.ALLOW.GENERIC.QNAMES) are required by the MQ agent. The RITDEFN sample job includes commands for creating these objects, and RITCFGS and RITCFGG were updated to reflect the RACF permissions required.

About this task

Do the following steps to configure IBM® WebSphere® MQ on IBM® z/OS®. In order to perform the steps, you need permissions for editing and submitting jobs on your z/OS system.

Procedure

  1. Determine whether your queue manager is part of a queue sharing group.
  2. Follow the instructions within the RITDEFN template to customize the JCL for creating the required namelists and queues.
    Note: If your queue manager is part of a queue sharing group, and if you want to use HCL OneTest™ API to record messages to shared queues, you must run the job once for each queue manager in the queue sharing group.
  3. Provide the required permissions to the user IDs so that they have access to all the required resources.
    For the list of resources and the required security permissions, see Security settings for MQ agent resources on z/OS. Depending on whether your security is set up at the queue manager level or at the queue sharing group level, you can use either the RITCFGS or RITCFGG JCL template with some customization based on your environment to set up the required permissions. Consult your security administration team to customize RITCFGS or RITCFGG for your environment.
    Note: The example templates do not have the commands to provide resources with the required permissions for the application user IDs. You must set up these permissions manually.