| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| can't get sender channel to connect SUN to MVS |
« View previous topic :: View next topic » |
| Author |
Message
|
| sjunejo |
 Posted: Thu Sep 18, 2008 7:58 am Post subject: |
 |
|
Novice
Joined: 12 Sep 2008
Posts: 16
|
First of all thanx for reply...
QMGR2.TO.QMGR1 not found ... is there not a problem.... SERVER means my default QMGR1 and client means my another queue manager QMGR2 just to differentiate both.
My runmqsc < [Script for QMGR1] is as following
def channel(QMGR1.TO.QMGR2) chltype(SDR) +
trptype(tcp) conname('10.44.5.107(1415)') +
xmitq(QMGR2) +
replace descr('QMGR1 to QMGR2 Sender')
def channel(QMGR2.TO.QMGR1) chltype(rcvr) +
trptype(tcp) replace
def qlocal(QMGR2) like(system.default.local.queue) +
replace share usage(xmitq)
def qremote('to.QMGR2') +
like(system.default.remote.queue) xmitq(QMGR2) +
replace rname('from.QMGR1') rqmname(QMGR2)
def qlocal('from.QMGR2') replace
end
My runmqsc < <Script for QMGR2> is as folowing
def channel(QMGR2.TO.QMGR1) chltype(SDR) +
trptype(tcp) conname('10.44.5.107') xmitq(QMGR1) +
replace descr('QMGR2 to QMGR1 sender')
def channel(QMGR1.TO.QMGR2) chltype(SVRCONN) +
trptype(tcp) replace
def qlocal(QMGR1) like(system.default.local.queue) +
replace share usage(xmitq)
def qremote('to.QMGR1') +
like(system.default.remote.queue) xmitq(QMGR1) +
replace rname('from.QMGR2') rqmname(QMGR1)
def qlocal('from.QMGR1')
end
---------------------------------------
If you can tell me is there anything wrong...before 'Channel 'QMGR2.TO.QMGR1' not found.' the output was simillar like 'channel type not suitable....'
 |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Sep 18, 2008 8:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bruce2359 wrote: |
Channel types must be a valid pair: sender-receiver, server-requester, etc.. Take a look at the MQ V6 Intercommunications manual.
To validate channels:
1. use the tcpip ping (from both channel ends): ifconfig -a (or something like it on SunOS), ipconfig on Windows. If you can successfully tcpip ping, continue.
2. from the Sender end of a non-started MQ channel, issue the MQ ping command (from within runmqsc). If this succeeds, your channel definitions are compatible. if successful, continue.
3. from the Sender end of the channel, issue the START CHL command from runmqsc (or runmqchl control command).
As stated elsewhere in this post, refer to the errors folder(s) in the MQ path to identify the detected error. I usually start at the top (in the IBM WebSphere MQ folder, then next try the errors folder with your qmgr name in folder Qmgrs. Look for errors logged at both ends of the channel.
Provide some details here:
-channel definitions
-exact commands you issued
-errors logged |
BEFORE using an old thread to ask a DUPLICATE question, you should take care to make sure you have READ AND UNDERSTOOD all of the answers already given in that THREAD.
 |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu Sep 18, 2008 9:38 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| sjunejo wrote: |
def channel(QMGR1.TO.QMGR2) chltype(SVRCONN) +
trptype(tcp) replace
|
This one should be chltype(RCVR). |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
