where SERVER.TO.HOST is the default transmission queue, and QMS is the name of the queue manager (which must be the same as the QMgrName parameter in the service definition).
2 Start the queue manager by typing the following at the command prompt:
strmqm QMS
3 Determine if commands must be sent to the host. If yes, you will have to start the command server. The default system queue used to process commands is SYSTEM.ADMIN.COMMAND.QUEUE. To start the command server, type the following at the command prompt:
strmqcsv QMS
4 Create the required MQ objects for QMS by typing the following at the command prompt:
The file c:\mqm\setup\server.tst must contain the information shown as follows.
To send messages to the host:
DEFINE QREMOTE('QS1') REPLACE + RNAME('QH1') + RQMNAME(QMH) + XMITQ(SERVER.TO.HOST) + DESCR('Messages for host') DEFINE QLOCAL(SERVER.TO.HOST) REPLACE + USAGE(xmitq) + DESCR('Xmit queue to host') DEFINE CHANNEL(SERVER.TO.HOST) + CHLTYPE(sdr) REPLACE + TRPTYPE(tcp) CONNAME(your IP address) + XMITQ(SERVER.TO.HOST) + DESCR('Sender channel from server to host')
To receive messages from the host:
DEFINE QLOCAL('QS2') REPLACE + DESCR('Messages from host') DEFINE CHANNEL(HOST.TO.SERVER) + CHLTYPE(rqstr) REPLACE + CONNAME(your IP address) + TRPTYPE(tcp) + DESCR('Receiver channel from host to server')
where QS1 is the service definition parameter sendToQ, and QS2 is the service definition parameter replyToQ.
If commands such as channel inquiries are to be sent to the host, then an additional queue to hold replies from the host is required. To receive replies from the host:
DEFINE QLOCAL('CHANNELQ') REPLACE + DESCR('Replies from host')
where CHANNELQ is the queue added to receive replies from the host that are related to channel queries.
The definition includes a channel to manage clients when working as a WebSphere MQ client. The definition is set on the server side. To define the server-to-client connection: