| Author |
Message
|
| Ross |
 Posted: Tue Jul 05, 2005 2:10 pm Post subject: MQ Client amqsputc - 2058 |
 |
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
Hi,
I'm hoping for some advice here before I go mad...
I have a current setup of a qmgr on OS/390 connecting to a qmgr on Windows 2003. Both are MQ V5.3
These connect to each other and work fine. I am also trying to do an MQ Client connection from the server directly to the OS/390 qmgr (ie. Doesn't use the server MQ) .
I am getting an MQ2058, Invalid QM name.
This is modelled on an identical setup we have with a different server and MF. All defs and config are identical/copied (I believe). I can't see what we're missing.
The defs are as follows:
Both SVRCONN and CLNTCONN "QM1.CLNTCONN.TCPIP" defined on MF Qmgr.
Listner up and running on port described in CLNTCONN.
I DO NOT have the MQSERVER or MQCHLTAB environment variables defined to either client, but it still works on one, and not the other. I don't want to define these on the non-functioning one as I want them to be identical!
Is there a parameter that I may be missing on one mainframe?
Any tips would be much appreciated. |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Jul 05, 2005 2:22 pm Post subject: Re: MQ Client amqsputc - 2058 |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Ross wrote: |
| Is there a parameter that I may be missing on one mainframe? |
I'm assuming that you have the Client Attachment Facility (CAF) installed on both mainframes? |
|
| Back to top |
|
|
| Ross |
| Posted: Tue Jul 05, 2005 2:43 pm Post subject: |
|
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
I imagine so as it's working on one, and the second MF is a mirror image.
How do I verify that it's running fine? |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Jul 05, 2005 3:05 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Jul 05, 2005 5:09 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
2058 X’080A’ MQRC_Q_MGR_NAME_ERROR
On an MQCONN or MQCONNX call, the value specified for the QMgrName parameter is not
valid or not known. This reason also occurs if the parameter pointer is not valid. (It is not
always possible to detect parameter pointers that are not valid; if not detected, unpredictable
results occur.)
On z/OS for CICS applications, this reason can occur on any call if the original connect
specified an incorrect or unrecognized name.
This reason code can also occur if a WebSphere MQ client application attempts to connect to a
queue manager within a WebSphere MQ-client queue-manager group (see the QMgrName
parameter of MQCONN), and either:
v Queue-manager groups are not supported.
v There is no queue-manager group with the specified name.
Corrective action: Use an all-blank name if possible, or verify that the name used is valid.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| JT |
| Posted: Tue Jul 05, 2005 6:33 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| All defs and config are identical/copied (I believe). |
Surely, there had to be some changes made. For instance, the CONNAME value on the M/F SVRCONN definition has to identify a unique IPAddress or DNS name.
What are those values? |
|
| Back to top |
|
|
| Ross |
| Posted: Wed Jul 06, 2005 2:02 am Post subject: |
|
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
The Client Attachment Feature is up and running fine on both mainframes. The 2 mainframes are located at separate (non-connected) sites. They are mirrored, and the SVRCONN channels use DNS Value "QM1" as the conname on both MF Qmgrs. DNS resolves the differences between the 2 boxes. So When I IP Ping QM1 from each server, it gets a reply from the appropriate queue manager/MF.
How can I verify the client knows where to look (What/Where QM1 is!), or how to connect to QM1? |
|
| Back to top |
|
|
| Ross |
| Posted: Wed Jul 06, 2005 5:13 am Post subject: |
|
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
| Thanks for your help with this. The issue was that I needed to define the amqclchl.tab file to the MQ root folder. If no MQ environment variables (MQSERVER or MQCHLTAB) defined, then MQ will look here as a default. This tab file contants the list of client channels to use to connect to various queue managers. |
|
| Back to top |
|
|
|
|
