Configuration reference

Configuration reference

Use the reference information in this section to help you configure IBM MQ .

The configuration reference information is provided in the following subtopics:

Example IBM MQ configuration for all platforms
The configuration examples describe tasks performed to establish a working IBM MQ network. The tasks are to establish IBM MQ sender and receiver channels to enable bidirectional message flow between the platforms over all supported protocols.
IBM MQ file system permissions applied to /var/mqm
The following information describes the security applied to the files and directories under /var/mqm/ and why the file-system permissions are set as they are. In order to ensure the correct operation of IBM MQ you should not alter the file system permissions as set by IBM MQ
IBM MQ file system permissions on Windows
The following information describes the security applied to the files and directories on Windows. In order to ensure the correct operation of IBM MQ you should not alter the file system permissions as set by IBM MQ.
Naming restrictions for queues
There are restrictions on the length of queue names. Some queue names are reserved for queues defined by the queue manager.
Naming restrictions for other objects
There are restrictions on the length of object names. Some object names are reserved for objects defined by the queue manager.
Queue name resolution
This topic contains information about queue name resolution as performed by queue managers at both sending and receiving ends of a channel.
System and default objects
Lists the system and default objects created by the crtmqm command.
Stanza information
The following information helps you configure the information within stanzas, and lists the contents of the mqs.ini, qm.ini, and mqclient.ini files.
Channel attributes
This section describes the channel attributes held in the channel definitions.
IBM MQ cluster commands
The IBM MQ Script commands runmqsc commands have special attributes and parameters that apply to clusters. There are other administrative interfaces we can use to manager clusters.
Channel programs
This section looks at the different types of channel programs (MCAs) available for use at the channels.
Environment variables
A list of server and client environment variables intended for customer use.
Intercommunication jobs
The following jobs are associated with Intercommunication on IBM i. The names are contained in the following table.
Channel states on IBM i
Channel states are displayed on the Work with Channels panel
Message channel planning example for UNIX, Linux, and Windows
This section provides a detailed example of how to connect two queue managers together so that messages can be sent between them.
Message channel planning example for IBM i
This section provides a detailed example of how to connect two IBM i queue managers together so that messages can be sent between them.
Message channel planning example for z/OS
This section provides a detailed example of how to connect z/OS® or MVS queue managers together so that messages can be sent between them.
Message channel planning example for z/OS using queue sharing groups
This example illustrates the preparations needed to allow an application using queue manager QM3 to put a message on a queue in a queue sharing group that has queue members QM4 and QM5.
Use an alias to refer to an MQ library
We can define an alias to refer to an MQ library in your JCL, rather than use the name of the MQ library directly. Then, if the name of the MQ library changes, we have only to delete and redefine the alias.
mqzOSConnectService element
The MQ Service Provider is provided as a standard Liberty feature and so is configured using server.xml. Each one or two-way service is defined in an mqzOSConnectService element. This element and all of its attributes apply to both z/OS Connect V1 and z/OS Connect EE.

Related information

Configure
Configure z/OS