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!

sender channel can't find remote receiver channel, but is DOES exist!

Status
Not open for further replies.

gertvangaever

Technical User
Apr 3, 2002
37
BE
Hello,

We have 2 queue maagers here:
QMAS400 (ccsid 37)
QMWINDOWS (ccsid 437)

There is a sender channel on QMAS400: QMAS400.TO.QMWINDOWS
There is a receiver channel on QMWINDOWS: QMWINDOWS.TO.QMAS400.

Why I try to start the channel, or ping the sender channel QMAS400.TO.QMWINDOWS, it says 'Remote channel not known. There is no definition of this channel on the remote system'. But actually, there is!

When I look in the error logs from mq on QMWINDOWS, I see the following error:

01/09/2004 11:37:22
AMQ9519: Channel 'x¼¯,îFÒ8®Ò¬®0||||' not found.

EXPLANATION:
The requested operation failed because the program could not find a definition
of channel 'x¼¯,îFÒ8®Ò¬®0||||'.
ACTION:
Check that the name is specified correctly and the channel definition is
available.
----- amqrcdfa.c : 1085 -------------------------------------------------------
01/09/2004 11:37:22
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'x¼¯,îFÒ8®Ò¬®0||||' ended abnormally.
ACTION:
Look at previous error messages for channel program 'x¼¯,îFÒ8®Ò¬®0||||' in
the error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------

So, for some reason, the name of the expected receiver channel is not correctly assed through. This probably has something to do with the different CCSID's, but where is that conversion done??
What is also annoying, is that this worked until a few days ago! I don't know about anything being changed on these queue managers, but what could be the cause of this strange behaviour than??

I hope someone can help me...

Gert
 
extra info;

There also is a 3d queue manager, QMWINDOWS2.
There is also a QMAS400.TO.QMWINDOWS2 sender channel & a respective receiver channel. That DOES work!

I have also tried to recreate the channels and reset them.
The definition of the channels for QMWINDOWS & QMWINDOWS2 are the same!!
 
edit. In my first post, I entered an incorrect name for the receiver channel on QMWINDOWS. It's 'QMAS400.TO.QMWINDOWS',so the same as the sender channel, as it should be (of course)
 
Something must be missing somplace. Post the following definitions.

QMAS400:
DIS CHL(QMAS400.TO.QMWINDOWS)
DIS QMGR
DIS QL(<XMITQ USED BY THIS CHANNEL>)


QMWINDOWS:
DIS CHL(QMAS400.TO.QMWINDOWS)
DIS QMGR


On both systems also include the respective commands output of IPCONFIG.




Cheers
KK
 
Just a thought but has someone changed the CCSID of one of the QMgrs? Have you stopped/started both QMgrs since you started getting this problem to see if that sorts it out?

Cheers,
Paul
 
I have stopped/started the qmgr, after deleting the channels. I recreated the channels then.
This has worked.
Probably something that got corrupted, don't know...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top