Set up communication for z/OS
When a distributed-queuing management channel is started, it tries to use the connection specified in the channel definition. To succeed, it is necessary for the connection to be defined and available. This section explains how to define a connection.
DQM is a remote queuing facility for IBM MQ . It provides channel control programs for the queue manager that form the interface to communication links. These links are controllable by the system operator. The channel definitions held by distributed queuing management use these connections.
Choose from one of the two forms of communication protocol that can be used for z/OS :
A message channel using TCP/IP can be pointed at an IBM Aspera fasp.io Gateway, which provides a fast TCP/IP tunnel that can significantly increase network throughput.
A queue manager running on any entitled platform can connect through an Aspera gateway. The gateway itself is deployed on Red Hat or Ubuntu Linux, or Windows.
See Defining an Aspera gateway connection on Linux or Windows.
Each channel definition must specify only one protocol as the transmission protocol (Transport Type) attribute. A queue manager can use more than one protocol to communicate.
We might also find it helpful to refer to Example configuration - IBM MQ for z/OS . If we are using queue sharing groups, see Set up communication for IBM MQ for z/OS using queue sharing groups.
- Defining a TCP connection on z/OS
To define a TCP connection, there are a number of settings to configure. - Defining an LU6.2 connection for z/OS using APPC/MVS
To define an LU6.2 connection there are a number of settings to configure.
Parent topic: Set up communications with other queue managers
Related concepts
- Use the panels and the commands
- Set up communications with other queue managers
- Set up IBM MQ for z/OS
- Monitor and control channels on z/OS
- Preparing IBM MQ for z/OS for DQM with queue sharing groups
- Set up communication for IBM MQ for z/OS using queue sharing groups
Related tasks