| Author |
Message
|
| FrankBo |
 Posted: Thu Dec 15, 2005 6:04 am Post subject: Msg RC2058 |
 |
|
Apprentice
Joined: 08 Dec 2005
Posts: 36
|
Hi, I've sent data to a queue and when our web server tries to access it msg RC2058 is returned which says queue mgr name not valid or not known. However, the queueu mgr name is correct in the script and on the Work with queue managers screen. Any ideas or thoughts on why this is happening?
Thanks, Frank |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Thu Dec 15, 2005 7:11 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Are you client connecting and have you ended up on the wrong machine? |
|
| Back to top |
|
|
| FrankBo |
| Posted: Thu Dec 15, 2005 7:47 am Post subject: Msg RC2058 |
|
|
Apprentice
Joined: 08 Dec 2005
Posts: 36
|
| Yes, it is a client connecting and we've double checked the ip and we are trying to connect to the correct machine. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu Dec 15, 2005 7:49 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
Can you give us some more information? Queue manager name? I assume you're using the right case? Are there multiple queue managers on the iSeries side, and if so are you going to the right port?
Cheers
Steve |
|
| Back to top |
|
|
| FrankBo |
| Posted: Thu Dec 15, 2005 7:58 am Post subject: Msg RC2058 |
|
|
Apprentice
Joined: 08 Dec 2005
Posts: 36
|
Thanks and yes, I've checked the queue manager name and it's in the proper case. There are multiple queue managers on the iseries and we're using the correct port, 1432, after I reviewed
Work with Listeners
Type options, press Enter.
2=Change 4=End 5=Display 7=Display Log
Opt Queue Manager Port
COPART.ASSGN.QM1 1432 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Dec 15, 2005 7:59 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You have misspelled the QM
You are using the wrong case for the QM
You are using Client Channel tables, and they are built with a blank QM name, but you are specifying the QM name in your app, or the reverse.
You have everything correct with the QM name, but you are really going to ServerB when you think you are going to ServerA.
It is one of these 4 reasons that you are getting a 2058.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| FrankBo |
| Posted: Thu Dec 15, 2005 9:20 am Post subject: Msg RC2058 |
|
|
Apprentice
Joined: 08 Dec 2005
Posts: 36
|
| I originally create an queue manager similar to the one I'm testing now, using port 1431. I have ended that queue manager and when I try to connect on port 1431 I'm getting RC2059 now. Any ideas on why that's happening? That's a little different msg than RC2058 but what does it indicate? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 15, 2005 9:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| FrankBo |
| Posted: Thu Dec 15, 2005 9:35 am Post subject: Msg RC2058 |
|
|
Apprentice
Joined: 08 Dec 2005
Posts: 36
|
The manual says for
Programmer Response:
Ensure that the queue manager has been started. If the connection is from a client application, check the channel definitions.
I'm sure the queue has been started on the AS400 and I've checked the channel definitions.
Also, there's a RUNMQLSR running showing
MQ job 10592 started for COPART.ASSGN.QM1.
What else can I do? |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Dec 15, 2005 9:40 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| I originally create an queue manager similar to the one I'm testing now, using port 1431. I have ended that queue manager and when I try to connect on port 1431 I'm getting RC2059 now. |
If you ended the qmgr, then I'd expect that you would get a 2059.
_________________
-wayne |
|
| Back to top |
|
|
| FrankBo |
| Posted: Thu Dec 15, 2005 9:59 am Post subject: Msg RC2058 |
|
|
Apprentice
Joined: 08 Dec 2005
Posts: 36
|
I've got the following queue manager and queues and channel running and I'm still getting RC2059;
Work with queue managers
Type options, press Enter.
2=Change 4=Delete 5=Display 14=Start 15=End 18=Work with Queues
19=Work with Processes 20=Work with Channels ...
Opt Name Status Default
COPART.ASSGN.QM1 ACTIVE NO
Work with MQ Queues
Queue Manager Name . . : COPART.ASSGN.QM1
Type options, press Enter.
2=Change 3=Copy 4=Delete 5=Display 12=Work with messages ...
Opt Name Type Depth Jobs
COPART.ASSGN.RECV *LCL 0 0
COPART.ASSGN.UNDELIVERABLE *LCL 0 0
COPART.ASSGN.XMIT *LCL 1 0
SYSTEM.ADMIN.CHANNEL.EVENT *LCL 0 0
SYSTEM.ADMIN.COMMAND.QUEUE *LCL 0 0
SYSTEM.ADMIN.PERFM.EVENT *LCL 0 0
SYSTEM.ADMIN.QMGR.EVENT *LCL 1 0
SYSTEM.AUTH.DATA.QUEUE *LCL 31 1
SYSTEM.CHANNEL.INITQ *LCL 0 1
Display Job Log
System: SICASA2
Job . . : RUNMQLSR User . . : QMQM Number . . . : 242699
>> QSYS/CALL PGM(QMQM/RUNMQLSR) PARM(X'6094' X'C3D6D7C1D9E34BC1E2E2C7D54BD8D4
F14040404040404040404040404040404040404040404040404040404040404040' X'60A3
' X'E3C3D7' X'6097' X'F1F4F3F2')
WebSphere MQ job 10592 started for COPART.ASSGN.QM1.
Work with MQ Channels
Queue Manager Name . . : COPART.ASSGN.QM1
Type options, press Enter.
2=Change 3=Copy 4=Delete 5=Display 8=Work with Status 13=P
14=Start 15=End 16=Reset 17=Resolve
Opt Name Type Transport Status
COPART.ASSGN.CHL *SVRCN *TCP INACTIVE
Do I have to reset something on the client side? |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Dec 15, 2005 10:08 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Lets start with the basics ...
How is the client connecting to the qmgr?
Since you mentioned 'web server", I'll assume you're using java. Are you using the base MQ classes or JMS to connect? If JMS, are you specifying the connection info in a JMSAdmin resource or the code itself?
Also,has this worked in the past and not working now, or the first time you're trying to make the connection?
_________________
-wayne |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Dec 15, 2005 10:10 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
2059 means:
The QM is not running.
-or-
The Listener is not running.
-or-
The Listener is running but not on the port the client is trying.
-or-
The channel name you are using on the client side does not exist as a SVRONN channel on the QM side (case sensitive).
-or-
You have network or firewall issues preventing the client from reaching that server/port number.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| FrankBo |
| Posted: Thu Dec 15, 2005 11:00 am Post subject: Msg RC2058 |
|
|
Apprentice
Joined: 08 Dec 2005
Posts: 36
|
| I'm not sure if I'm getting closer or not but I'm now getting RC2033. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu Dec 15, 2005 11:07 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
Well, that means you're now connected. The link that Jeff provided above will detail all the MQ return codes you may possibly run into, 2033 included.
So what was the problem?
Steve |
|
| Back to top |
|
|
|
|
