Creating the broker runtime environment on z/OS

This is part of the larger task of creating a broker on z/OS.

Before you start:

Before starting this step, you must have completed the following tasks:
Check that you have access to the installation libraries. For example, use the following command to display information about the directory structure:
ls -l /usr/lpp/wmqi
This command displays lines like the following example:
drwxr-xr--   2 A8LIGH2  MQM         8192 Aug 20 16:22 lib
In this example, MQM is the group associated with the file or directory structure. Those who will be using the files, for example the WebSphere Business Integration Message Broker administrators, and the started task user IDs, should be in the group of the files. Use the id userid command to display the groups a user ID is in. If a user ID is not in the group, you can:
  • Add the user ID to the group using standard ESM facilities.
  • Change the group of the file using the example command below:
    chgrp -R WMQI /usr/lpp/wmqi

You might need super user authority to issue this command.

Use the mqsicreatebroker command to create a broker and its runtime environment. The command syntax is:
mqsicreatebroker brokername -c ComponentDirectory -q QueueManagerName 
[-s UserNameServerQueueManagerName] [-g ConfigurationTimeOut]
[-k ConfigurationDelayTimeOut] [-f]
For further information, see mqsicreatebroker command.

If you create an uppercase broker name, you must use this name in uppercase also for your broker in the workbench.

If you get the message:
mqsicreatebroker: FSUM7351 not found
refer to Setting up your OMVS user ID.
Related concepts
Brokers
Broker domains
Related tasks
Setting up your OMVS user ID
Creating a broker on z/OS
Creating the broker directory on z/OS
Editing the Customization Input File (mqsicompcif) for a broker
Related reference
mqsicreatebroker command