Getting started with objects

Channels must be defined, and their associated objects must exist and be available for use, before a channel can be started. This section shows you how.

1. Define message channels and associated objects
2. Monitor and control message channels

The associated objects you might need to define are:

• Transmission queues
• Remote queue definitions
• Queue manager alias definitions
• Reply-to queue alias definitions
• Reply-to local queues
• Processes for triggering (MCAs)
• Message channel definitions

The particular communication link for each channel must be defined and available before a channel can be run. For a description of how LU 6.2, TCP/IP, NetBIOS, SPX, and DECnet links are defined, see the particular communication guide for the installation. See also Example configuration information.

For more information about creating and working with objects, see the following subtopics:

• Create associated objects
  MQSC is used to create associated objects.
• Create default objects
  Default objects are created automatically when a queue manager is created. These objects are queues, channels, a process definition, and administration queues. After the default objects have been created, we can replace them at any time by running the strmqm command with the -c option.
• Create a channel
  Create two channel definitions, one at each end of the connection. You create the first channel definition at the first queue manager. Then you create the second channel definition at the second queue manager, on the other end of the link.
• Display a channel
  Use the MQSC command DISPLAY CHANNEL to display the attributes of a channel.
• Display channel status
  Use the MQSC command DISPLAY CHSTATUS, specifying the channel name and whether we want the current status of channels or the status of saved information.
• Check links using Ping
  Use the MQSC command PING CHANNEL to exchange a fixed data message with the remote end.
• Starting a channel
  Use the MQSC command START CHANNEL for sender, server, and requester channels. For applications to be able to exchange messages, we must start a listener program for inbound connections.
• Stopping a channel
  Use the MQSC command STOP CHANNEL to request the channel to stop activity. The channel does not start a new batch of messages until the operator starts the channel again.
• Renaming a channel
  Use MQSC to rename a message channel.
• Resetting a channel
  Use the MQSC command RESET CHANNEL to change the message sequence number.
• Resolving in-doubt messages on a channel
  Use the MQSC command RESOLVE CHANNEL when messages are held in-doubt by a sender or server. For example because one end of the link has terminated, and there is no prospect of it recovering.

Parent topic: Monitor and control channels on UNIX, Linux, and Windows