Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MQ5.3: Problem starting channel in windows-to-Linux constellation

Status
Not open for further replies.

jo111

Technical User
Jul 21, 2004
3
SE
hello,
I have MQ5.3 installed on one Linux RedHat server and on one WindowsXP.

I can set up a connection from the WindowsXP server to the Linux server, but not vice versa.

The following:
sender workstation (Linux, qmanagerName = davinci.queue.manager), create with MQSC commands

$define qlocal (greece.transmit.queue) usage (xmitq)
:
$define qremote (remote.def.beer.queue) rname (beer.queue) + rqmname ('blacksabbath.queue.manager') xmitq +(greece.transmit.queue)
:
$define channel (third.channel) chltype (sdr) +
conname (192.168.1.26) xmitq (greece.transmit.queue + trptype (tcp)

reveiver workstation (WindowsXP, qmanagerName = blacksabbath.queue.manager)

$define qlocal (beer.queue)
:
$define channel (third.channel) chltype (rcvr) trptype (tcp)

On sender workstation,
$ runmqchl -c THIRD.CHANNEL -m davinci.queue.manager

gives error:
"07/21/2004 03:12:30 PM AMQ9520: Channel not defined remotely."
"07/21/2004 03:12:30 PM AMQ9999: Channel program ended abnormally."


I find it strange that (windows -> Linux) works, (Linux -> windows) fails!
Listner is running, PING works.

I would very much appreciate any suggestions or thoughts.
 
Case!

Your channel are defined in lower case but the $ runmqchl -c THIRD.CHANNEL -m davinci.queue.manager
has it in upper case.

 
I solved the problem. Newbie as I am, the solution was quite simple:
Re-define the channel with a different port, 1415

define channel (third.channel) chltype (sdr) +
conname ('192.168.1.26(1415)') xmitq (greece.transmit.queue + trptype (tcp)

$ runmqlsr -t tcp -p 1415

$ runmqchl -c THIRD.CHANNEL -m davinci.queue.manager

-> works!
 
Ok, when I started the channel I left out "-m davinci.queue.manager" which is ok since that is the default queue manager. However I think it will work the way I wrote it (runmqchl -c THIRD.CHANNEL -m davinci.queue.manager).

Otherwise it is ok to define f.ex a queue in lower-case, but then refer to it with upper-case:

define qlocal (test.queue)

display qlocal (TEST.QUEUE)

Do you mean that it is odd to put TEST.QUEUE (upper-case) and davinci.queue.manager (lowe-case) in "runmqchl" command?

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top