�ݺ�ߣ

Editor's Notes

• #9: Make sure your hardware installation is complete, including all external devices. See the documentation provided with your system unit for installation instructions. Make sure you have that information your system needs to communicate with other systems and access their resources, before proceeding:
• #11: Configuring TCP/IP for WebSphere MQ varies according to the platform on which WebSphere MQ is installed. On Unix systems, the inet daemon is used as a listener for messages, and must be configured to listen on the WebSphere MQ default port, 1414. On Windows, the control command runmqlsr is used. See WebSphere MQ Intercommunication manual for details. Starting a message channel To start a message channel, the MQSC command START CHANNEL is used, providing the name of the channel to be started. There is also a PING CHANNEL command to test a message channel configuration. In addition to the MQSC command, there is a control command runmqchl to start a channel. It takes a -c parameter to name the channel to be started. The MQSC command START CHANNEL and the control command runmqchl do not contain retry logic for starting a channel. If retry logic is required, as in the case of difficulty starting a channel, or especially for restarting a channel after an error has occurred, then you should use a channel initiator. The MQSC command for starting a channel initiator is START CHINIT. The control command is runmqchi.
• #12: The objects in this network are: A remote queue A transmission queue A local queue A sender channel A receiver channel Appl1 and Appl2 are both application programs; Appl1 is putting messages and Appl2 is receiving them. Appl1 puts messages to a remote queue. The definition for this remote queue specifies the name of a target queue manager, a local queue on that queue manager, and a transmission queue on this the local queue manager. When the queue manager receives the request from Appl1 to put a message to the remote queue, it looks at the queue definition and sees that the destination is remote. It therefore puts the message, along with a transmission header, straight onto the transmission queue specified in the definition. The message remains on the transmission queue until the channel becomes available, which may happen immediately.
• #13: Create Message Queue Manager (CRTMQM) Type choices, press Enter. Message Queue Manager name . . . Text 'description' . . . . . . . *BLANK Trigger interval . . . . . . . . 999999999 0-999999999 Undelivered message queue . . . *NONE Default transmission queue . . . *NONE Maximum handle limit . . . . . . 256 1-999999999 Maximum uncommitted messages . . 1000 1-10000 Default Queue manager . . . . . *NO *YES, *NO Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys
• #14: Note: The words in bold are user-specified and reflect the names of WebSphere MQ objects used throughout these examples. If you change the names used here, ensure that you also change the other references made to these objects throughout this book. All others are keywords and should be entered as shown. The WebSphere MQ channel ping command (PNGMQMCHL) runs interactively, whereas starting a channel causes a batch job to be submitted. If a channel ping completes successfully but the channel will not start, this indicates that the network and WebSphere MQ definitions are probably correct, but that the i5/OS environment for the batch job is not. For example, make sure that QSYS2 is included in the system portion of the library list and not just your personal library list. Note: AMQ* errors are placed in the log relating to the job that found the error. Use the WRKACTJOB command to display the list of jobs. Under the subsystem name QSYSWRK, locate the job and enter 5 against it to work with that job. WebSphere MQ logs are prefixed ‘AMQ’.
• #15: Channel states use DISPLAY CHSTATUS. INITIALISING A channel initiator is attempting to start the channel. STARTING A channel waits in this state if there is no active slot available. If there is an active slot immediately available, it remains in this state a very short time. The number of active slots is defined by the MAXCHL attribute of a queue manager. BINDING Establishing a communications connection and performing the initial data exchange. REQUESTING A requester is waiting for callback from a sender. RUNNING Transferring messages, or waiting for messages to arrive on the transmission queue. PAUSED Waiting for the message-retry interval to complete before attempting to put a message on its destination queue. STOPPING An error has occurred, the STOP CHANNEL command has been issued, or the disconnect interval has expired. RETYRING Waiting until it is time for the channel initiator to make the next attempt to start the channel. STOPPED The channel is disabled and needs manual intervention to start it again. INACTIVE An inactive channel is one that has never been started or has disconnected normally.
• #16: It involves a payroll query application connected to queue manager QM1 that sends payroll query messages to a payroll processing application running on queue manager QM2. The payroll query application needs the replies to its queries sent back to QM1. The payroll query messages are sent from QM1 to QM2 on a sender-receiver channel called QM1.TO.QM2, and the reply messages are sent back from QM2 to QM1 on another sender-receiver channel called QM2.TO.QM1. Both of these channels are triggered to start as soon as they have a message to send to the other queue manager. The payroll query application puts a query message to the remote queue "PAYROLL.QUERY" defined on QM1. This remote queue definition resolves to the local queue "PAYROLL" on QM2. In addition, the payroll query application specifies that the reply to the query is sent to the local queue "PAYROLL.REPLY" on QM1. The payroll processing application gets messages from the local queue "PAYROLL" on QM2, and sends the replies to wherever they are required; in this case, local queue "PAYROLL.REPLY" on QM1. Both queue managers are assumed to be running on i5/OS. In the example definitions, QM1 has a host address of 9.20.9.31 and is listening on port 1411, and QM2 has a host address of 9.20.9.32 and is listening on port 1412. The example assumes that these are already defined on your i5/OS system, and are available for use.
• #17: T The object definitions that need to be created on QM1 are: Remote queue definition, PAYROLL.QUERY Transmission queue definition, QM2 (default=remote queue manager name) Sender channel definition, QM1.TO.QM2 Receiver channel definition, QM2.TO.QM1 Reply-to queue definition, PAYROLL.REPLY The object definitions that need to be created on QM2 are: Local queue definition, PAYROLL Transmission queue definition, QM1 (default=remote queue manager name) Sender channel definition, QM2.TO.QM1 Receiver channel definition, QM1.TO.QM2 The connection details are supplied in the CONNAME attribute of the sender channel definitions. Note: The remote queue definition is not a physical queue, but a means of directing messages to the transmission queue, QM2, so that they can be sent to queue manager QM2.
• #18: The reply-to queue is defined as PUT(ENABLED). This ensures that reply messages can be put to the queue. If the replies cannot be put to the reply-to queue, they are sent to the dead-letter queue on QM1 or, if this queue is not available, remain on transmission queue QM1 on queue manager QM2. The queue has been defined as GET(ENABLED) to allow the reply messages to be retrieved. A WebSphere MQ client application can participate in a local unit of work involving the resources of the queue manager it is connected to. To do this, it uses the MQCMIT and MQBACK calls in the normal way.
• #19: . QNAME PAYROLL queue is defined as PUT(ENABLED) and GET(ENABLED) for the same reason as the reply-to queue definition on queue manager QM1. QNAME QM1 When the first message is put on this transmission queue, a trigger message is sent to initiation queue: SYSTEM.CHANNEL.INITQ. The channel initiator gets the message from the initiation queue and starts the channel identified in the trigger data.