| Author |
Message
|
| New2MQ |
 Posted: Thu Nov 07, 2002 7:38 am Post subject: MQSeries NT Server to MQSeries O/S 390 Configuration |
 |
|
Newbie
Joined: 02 Oct 2002
Posts: 8
|
We have sender, receiver and transmission channels set up on local (Virginia) NT server side and remote (Kansas City) O/S 390 side. Using TCP/IP, O/S 390 can ping NT server through MQ channel, but NT server cannot pint O/S 390 through MQ channel (can ping through command prompt). Receiving error "Remote system not availalbe. Could not allocate a conversation to a remote system. The error may be transitory so the allocate may succeed later. (AMQ4061)"
Any idea what could be causing this error?
Thanks. |
|
| Back to top |
|
 |
| migstr |
| Posted: Thu Nov 07, 2002 7:40 pm Post subject: |
|
|
Apprentice
Joined: 05 Jun 2002
Posts: 34
Location: New York
|
Hi,
Are there any other Sender Channels from other servers into your 390 Qmgr that are working? Is this problem unique to your set up?
Are you sure they gave you the right Port # for your conname and that the Listener is running on the 390? |
|
| Back to top |
|
|
| New2MQ |
| Posted: Tue Nov 12, 2002 11:24 am Post subject: |
|
|
Newbie
Joined: 02 Oct 2002
Posts: 8
|
On different sender receiver channels, Win Server can ping O/S 390 through sender channel, but O/S 390 cannot ping Win Server on receiver channel or same sender channel name. O/S 390 getting error "CSQX202E !QFNT CSQXPING Connection or remote listener unavailable, and CSQ9023E !QFNT CSQXCRPS ' Ping Channel' Abnormal Completion."
Essentially, one on sender/receiver channel the O/S 390 can ping, but the Win Server cannot (getting remote channel error previously described). On another sender/receiver channel on a different Win Server queue manager, the Win Server can ping, but the O/S 390 cannot (getting error described above). Using same O/S 390 queue manager for each scenario.
Any assistance would be greatly appreciated.
Thank you. |
|
| Back to top |
|
|
| ghoose |
| Posted: Tue Nov 12, 2002 5:55 pm Post subject: |
|
|
Novice
Joined: 23 Apr 2002
Posts: 16
|
Hi Migstr,
does this mean that your sender channel frm OS390 is in retrying state?
If it is reason could be you dont have a listener on your recieving side
or listener is listening to the same port which is used by some one else.
try changing the listner port restart listener and give it a shot.
BTW sender and reciever channel shud have same name!!!
regards
Ghoose |
|
| Back to top |
|
|
| migstr |
| Posted: Wed Nov 13, 2002 5:25 am Post subject: |
|
|
Apprentice
Joined: 05 Jun 2002
Posts: 34
Location: New York
|
Hi ghoose , NEW2MQ
Actually NEW2MQ is posting the question...but glad you replied. So NEW2MQ, are you saying that this is your scenario?:
Win2k QMGR A ............ 390 QMGR B
Sender A.B =====> Rcvr A.B [this works]
Rcvr B.A <==== Sender B.A [this doesn't work]
Win2k QMGR C ............ 390 QMGR B
Sender C.B =====> Rcvr C.B [this doesn't work]
Rcvr B.C <==== Sender B.C [this works]
Remember a regular old PING vs. a channel PING use two different ports. And a listener must be active for the PORT you are specifying in the CONNAME of the Sender channel. |
|
| Back to top |
|
|
| New2MQ |
| Posted: Wed Nov 13, 2002 8:33 am Post subject: |
|
|
Newbie
Joined: 02 Oct 2002
Posts: 8
|
Yes, the scenario you desribe is correct. I have assigned a port and run the runmqlsr command to start the listener, but the same scenario persists. Have verified correct connection name with IP and port number on the O/S 390 sender channel.
Is there something else I'm missing?
Thanks |
|
| Back to top |
|
|
| ghoose |
| Posted: Wed Nov 13, 2002 9:11 am Post subject: |
|
|
Novice
Joined: 23 Apr 2002
Posts: 16
|
oops for the slip Migstr....
BTW NEW2MQ.. can you let us knw about the port numbers on each queuemanager for each listener you are running. |
|
| Back to top |
|
|
| New2MQ |
| Posted: Wed Nov 13, 2002 10:30 am Post subject: |
|
|
Newbie
Joined: 02 Oct 2002
Posts: 8
|
| On the Win 2K QMGR A, I'm running a listener on port 3010. On the O/S 390 QMGR B, were listening on port 9010. Each of these ports are specified in the connection name of the sender channel. We're attempting to do a channel ping when we get these errors. |
|
| Back to top |
|
|
| migstr |
| Posted: Wed Nov 13, 2002 11:30 am Post subject: |
|
|
Apprentice
Joined: 05 Jun 2002
Posts: 34
Location: New York
|
| NEW2MQ, is there any possibility there is a firewall set up between your remote queue managers and the 390, and it wasn't configured correctly? |
|
| Back to top |
|
|
| ghoose |
| Posted: Wed Nov 13, 2002 11:39 am Post subject: |
|
|
Novice
Joined: 23 Apr 2002
Posts: 16
|
Win2k QMGR A ............ 390 QMGR B
Sender A.B =====> Rcvr A.B [this works] Port 3010
Port 9010 Rcvr B.A <==== Sender B.A [this doesn't work]
Win2k QMGR C ............ 390 QMGR B
Sender C.B =====> Rcvr C.B [this doesn't work] port 3010
port 9010 Rcvr B.C <==== Sender B.C [this works]
If this is the case then it will not work. You cannot make 2 reciever listen to same port. it will be 1st come first serve. hence only one channel (1st one to bind to the port ) will run and second one will not.
Hope this help
Ghoose |
|
| Back to top |
|
|
| migstr |
| Posted: Wed Nov 13, 2002 12:15 pm Post subject: |
|
|
Apprentice
Joined: 05 Jun 2002
Posts: 34
Location: New York
|
ghoose, On the 390 side, I know we have tens if not hundreds of receiver channels working off of the same port, with no problem. But maybe I'm misunderstanding what you are saying. I think you are saying you can only have one listener, listening on a port?
And just to clarify, NEW2MQ, QMGR A and QMGR C are on two different servers aren't they? |
|
| Back to top |
|
|
| New2MQ |
| Posted: Wed Nov 13, 2002 1:16 pm Post subject: |
|
|
Newbie
Joined: 02 Oct 2002
Posts: 8
|
| Yes, QMGR A and QMGR C are on two different physical servers. The 3010 port is on the Win 2K side and the 9010 port is on the O/S 390 side. |
|
| Back to top |
|
|
| ghoose |
| Posted: Wed Nov 13, 2002 1:43 pm Post subject: |
|
|
Novice
Joined: 23 Apr 2002
Posts: 16
|
Im sorry about that confusion. U r right Mig thats what i was trying to say.
I didnk knw both are on 2 diff box  )
for listner u get AMQ9202
AMQ4061 says its a temp error and there is no user action attached to it )
AMQ4061 Remote system not available.
Explanation: Could not allocate a conversation to a
remote system. The error may be transitory so the
allocate may succeed later.
User Response: None
best u can do is retry again and see what u get in the log files (atleast thats what IBM says )
Qmgrname/errors/ |
|
| Back to top |
|
|
| mqonnet |
| Posted: Wed Nov 13, 2002 1:55 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
FYI from the docs.
You MUST have your Command server and Chin running on OS/390 side for PING CHANNEL to work. And that could be the reason your ping channel command too was not working.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| New2MQ |
| Posted: Wed Nov 13, 2002 2:16 pm Post subject: |
|
|
Newbie
Joined: 02 Oct 2002
Posts: 8
|
| We changed the port number on the QMGR A to 1415 and the channel ping worked. I have no idea why the 3010 wasn't working, but thanks for all of your assistance. |
|
| Back to top |
|
|
|
|
