| Author |
Message
|
| Echchatbi |
 Posted: Wed Apr 03, 2002 1:56 am Post subject: |
 |
|
Newbie
Joined: 02 Apr 2002
Posts: 3
|
On our OS390 we have MQSeries for MVS / ESA 1.2 .
I installed and configured a V5.2 client on an NT machine. I constantly get the error 2059 with the amqsgetc sample.
I have checked everything but can't seem to figure this out. Everything looks fine.
The value of the MQSERVER env var is positioned well to : MQST_CLIENT1/TCP/190.06.120.204(1555).
The server reacts by posting a couple of messages in the log :
11.31.03 STC06737 +CSQX500I ; CSQXRESP Channel MQST_CLIENT1 started
11.31.03 STC06737 +CSQX501I ; CSQXRESP Channel MQST_CLIENT1 is no longer active
The client resp is : MQCONN ended with reason code 2059
Any ideas?
Thanks in advance. |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Wed Apr 03, 2002 4:28 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
IS the CAF (MQ Client connection for OS390) installed ???
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| Echchatbi |
| Posted: Wed Apr 03, 2002 5:30 am Post subject: |
|
|
Newbie
Joined: 02 Apr 2002
Posts: 3
|
| I am not certain, but I suppose that not |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Wed Apr 03, 2002 11:10 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| Quote: |
On 2002-04-03 01:56, Echchatbi wrote:
On our OS390 we have MQSeries for MVS / ESA 1.2 .
I installed and configured a V5.2 client on an NT machine. I constantly get the error 2059 with the amqsgetc sample.
I have checked everything but can't seem to figure this out. Everything looks fine.
The value of the MQSERVER env var is positioned well to : MQST_CLIENT1/TCP/190.06.120.204(1555).
The server reacts by posting a couple of messages in the log :
11.31.03 STC06737 +CSQX500I ; CSQXRESP Channel MQST_CLIENT1 started
11.31.03 STC06737 +CSQX501I ; CSQXRESP Channel MQST_CLIENT1 is no longer active
The client resp is : MQCONN ended with reason code 2059
Any ideas?
Thanks in advance.
|
I wouldn't expect you to be able to get that far (CSQX500) without the CAF, but I might be wrong. Have you checked that you provide the 4 digit queue manager name in all UPPERCASE characters on the amqsgetc command line? Arguments to sample programs are treated as is and MQ names are case-sensitive.
Can you please verify?
Cheers,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| mrlinux |
| Posted: Wed Apr 03, 2002 11:20 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Yep you would be able to get that far but no further. OS390 MQSeries when it creates it's default objects creates the SYSTEM.DEF.SVRCONN Channel but you cant use it unless the CAF is installed
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Wed Apr 03, 2002 11:44 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| Quote: |
On 2002-04-03 11:20, mrlinux wrote:
Yep you would be able to get that far but no further. OS390 MQSeries when it creates it's default objects creates the SYSTEM.DEF.SVRCONN Channel but you cant use it unless the CAF is installed
|
That makes sense and the 2059 related description contains the relevant comment (of course). 
The easy way to find out if the CAF is installed is to look at the xxxxMSTR sysout and see if there was a CSQX099I message produced during startup, right!?
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| mrlinux |
| Posted: Wed Apr 03, 2002 12:09 pm Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Actullay the message shows up in the XXXXchin task
CSQX099I -CSQT CSQXGIP Client attachment feature available
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| Echchatbi |
| Posted: Wed Apr 03, 2002 10:11 pm Post subject: |
|
|
Newbie
Joined: 02 Apr 2002
Posts: 3
|
I thank you for your interest in my problem.
1) The four digits QManager name was supplied in capital letters,
2) Effectively, there is no CSQX099I message produced in xxxxCHIN log nor in that of xxxxMSTR. I direct my investigations in this way. |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Thu Apr 04, 2002 10:59 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| Quote: |
On 2002-04-03 22:11, Echchatbi wrote:
I thank you for your interest in my problem.
1) The four digits QManager name was supplied in capital letters,
2) Effectively, there is no CSQX099I message produced in xxxxCHIN log nor in that of xxxxMSTR. I direct my investigations in this way.
|
It looks like Jeff's idea then is a hot one. Also, the CAF is an additional feature on the mainframe and you have to pay for it. That's one reason why some (many?) installations on /390 do not have it installed unless they really need client connectivity.
Cheers,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
|
|
