| Author |
Message
|
| sysnemr |
 Posted: Mon Jul 01, 2002 1:35 am Post subject: Unable to connect to qmgr Q2ZP with NT client RC=2059 |
 |
|
Apprentice
Joined: 29 Oct 2001
Posts: 30
Location: Zagreb, Croatia
|
I installed the MQSeries NT client on WIN NT Workstation.
On OS/390 machines I have got the following status
The first OS/390 system
+CSQX099I +P1 CSQXGIP CLIENT ATTACHMENT FEATURE AVAILABLE .
The second OS/390 system
+CSQX099I +P2 CSQXGIP CLIENT ATTACHMENT FEATURE AVAILABLE .
Both OS/390 systems have got queue managers.
They have got the similar objects created because these
OS/390 systems are in //Sysplex. I set the MQseries variables on the NT workstation in this way
For queue manager Q1ZP on the first OS/390 system
SET MQSERVER=CHANNEL.TO.Q1ZP/TCP/10.254.13.1(1418)
SET MQCCSID=852
For queue manager Q2ZP on the second OS/390 system
SET MQSERVER=CHANNEL.TO.Q2ZP/TCP/10.254.6.1(1420)
SET MQCCSID=852
I created the channels on queue managers in this way
Q1ZP
DEFINE CHANNEL(CHANNEL.TO.Q1ZP) CHLTYPE(SVRCONN) TRPTYPE(TCP) MCAUSER(' ') REPLACE
Q2ZP
DEFINE CHANNEL(CHANNEL.TO.Q2ZP) CHLTYPE(SVRCONN) TRPTYPE(TCP) MCAUSER(' ') REPLACE
From the command prompt on NT I can connect to the queue
manager Q1ZP with amqsputc and amqsgetc, and put and get messages from the queues on Q1ZP.
I changed variables on NT workstation for an other queue manager Q2ZP. When I try to issue the command on the workstation
amqsputc TEST.QUEUE
the response is the following message:
MQCONN ended with reason code 2059.
I don't know what to do here because everything is done in same
way on both systems. I can not see any differences
on both systems. What to do here to solve the problem that
amqsputc and amqsputc applications can connect to queue manager Q2ZP as I can normally connect to Q1ZP? |
|
| Back to top |
|
 |
| TorpedoSTu |
| Posted: Mon Jul 01, 2002 3:56 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
The only obvious diffence is the ip address.
Does ping work ok ?
Regs
Stu |
|
| Back to top |
|
|
| glen |
| Posted: Mon Jul 01, 2002 4:17 am Post subject: |
|
|
Novice
Joined: 05 Jun 2002
Posts: 13
Location: Dublin, Ireland.
|
if you could connect to one MQS but not the other, then the client is installed correctly.
two things to check
echo %mqserver% from command prompt, make sure the output is correct.
the queue names are case sensitive. check.
eg. amqsputc Test.QUEUE |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jul 01, 2002 4:23 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Check port #'s, Since you are not specifing a queue manager name on
your calls you need to make sure both are default queue managers.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| sysnemr |
| Posted: Mon Jul 01, 2002 4:54 am Post subject: |
|
|
Apprentice
Joined: 29 Oct 2001
Posts: 30
Location: Zagreb, Croatia
|
I don't know how to check if the queue manager on OS/390 is default
queue manager. I know how to s check it on NT. On our OS/390 every application connects to explicit name od qmgr not to default queue manager. The only required parametar for amqsputc is queue name and only changing the NT variable I choose the queue manager, IP and port pair, which is on OS/390. |
|
| Back to top |
|
|
| sysnemr |
| Posted: Mon Jul 01, 2002 5:18 am Post subject: |
|
|
Apprentice
Joined: 29 Oct 2001
Posts: 30
Location: Zagreb, Croatia
|
| I checked the IP address and port. They are OK. Also I used the correct name of queue in amqsputc. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jul 01, 2002 6:28 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Try doing the AMQSPUTC QUEUENAME QMGRNAME
Also try telnet MAINFRAME MQPort#
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| sysnemr |
| Posted: Tue Jul 02, 2002 2:51 am Post subject: |
|
|
Apprentice
Joined: 29 Oct 2001
Posts: 30
Location: Zagreb, Croatia
|
When I specify the qmgrname for example
amqsputc TEST.QUEUE Q2ZP
it doesn't work. I have got the same output message as before without
qmgrname:
Sample AMQSPUT0 start
MQCONN ended with reason code 2059
I noticed in OS/390 log the following messages
+CSQX500I +P2 CSQXRESP CHANNEL CHANNEL.TO.Q2ZP STARTED
+CSQX501I +P2 CSQXRESP CHANNEL CHANNEL.TO.Q2ZP IS NO LONGER ACTIVE
For an other qmgr Q1ZP
amqsputc TEST.QUEUE Q1ZP works and there is no differnce
when I use or ommit the qmgrname.
Also, I tried to telnet to IP + port:
telnet 10.254.6.1 1420
With netstat command I saw the established connection with this IP and port specified in telnet command. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Jul 02, 2002 3:06 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
I have gotten the same thing when our OS390 Queue manager is not set as default. Iam not saying thats is but it certainly looks like it . I just could never explain when specifing the queue manager name it still wont work.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| sysnemr |
| Posted: Tue Jul 02, 2002 3:56 am Post subject: |
|
|
Apprentice
Joined: 29 Oct 2001
Posts: 30
Location: Zagreb, Croatia
|
We haven't got both production qmgrs set default. Before this I didn't know how can I set the MQSeries subsystem on OS/390 as default queue manager. I found in System Management Guide that this can be done with CSQBDEFV. The both queue managers are not set as default queue
managers and maybe this is not cause why I cannot connect with NT MQSeries client to qmgr Q2ZP. Probably is problem somewhere else!? |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Tue Jul 02, 2002 5:28 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hmm,
it sounds pretty strange....
| Quote: |
+CSQX500I +P2 CSQXRESP CHANNEL CHANNEL.TO.Q2ZP STARTED
+CSQX501I +P2 CSQXRESP CHANNEL CHANNEL.TO.Q2ZP IS NO LONGER ACTIVE |
You was seeing the above in the log which MVS LOG or Q2ZPCHIN log ?
By the way are there any security violation in QZ2PMSTR task ?
Normally it's pretty easy to get the client up and running towards OS/390, especially if we check the RC's and the logs.
By the way if you're doing a DIS QMGR command, it responds: QZ2P all upercase, right ?
just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| sysnemr |
| Posted: Tue Jul 02, 2002 6:52 am Post subject: |
|
|
Apprentice
Joined: 29 Oct 2001
Posts: 30
Location: Zagreb, Croatia
|
These messages
+CSQX500I +P2 CSQXRESP CHANNEL CHANNEL.TO.Q2ZP STARTED
+CSQX501I +P2 CSQXRESP CHANNEL CHANNEL.TO.Q2ZP IS NO LONGER ACTIVE
I notice everytime I issue the command
amqsputc TEST.QUEUE Q2ZP
in OS/390 SYSLOG and also in Q2ZPCHIN.
We haven't got activated the MQSeries security in RACF.
So, these messages are triggered only when I test with client apllication
amqsputc. It's really very easy to connect client to qmgr. I did it very fast
and saw that everything is OK with Q1ZP. But with Q2ZP is really strange
because everything was done for Q2ZP in the same way as I did for Q1ZP.
Display is also OK.
+P2 DIS QMGR
CSQM201I +P2 CSQMDMSG DIS QMGR DETAILS 392
QMNAME(Q2ZP)
CSQMDMSG END QMGR DETAILS
CSQ9022I +P2 CSQMDMSG ' DIS QMGR' NORMAL COMPLETION |
|
| Back to top |
|
|
|
|
