| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Client Connection To Mainframe |
« View previous topic :: View next topic » |
| Author |
Message
|
| moepi |
 Posted: Wed Jan 07, 2004 2:11 am Post subject: Client Connection To Mainframe |
 |
|
Novice
Joined: 11 Jul 2001
Posts: 21
Location: South Africa
|
Hi,
I have a 'C' application thats running on a Solaris server. The application can connect remotely to other Unix and Windows server as a client without any problem. But when I try to connect to Mainframe I get the following error,
"Channel MAINFRAME.MQCLIENT.01 started
Channel MAINFRAME.MQCLIENT.01 is no longer active"
What might be the cause of this. And how do I overcome this problem.
Ta,
Moepi |
|
| Back to top |
|
 |
| offshore |
| Posted: Wed Jan 07, 2004 8:42 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
moepi,
do you have the client attachment feature installed on the mainframe? unlike the distributed side you have to contact IBM for the CAF of MQ.
Check your xxxxCHIN joblog on the mainframe and look for this message
+CSQX099I +QMGR_NAME CSQXGIP Client attachment feature available
if that message isn't in the joblog that is the problem, otherwise i'll need more info like:
is that all the "error" type information in the joblog?
did the client side return any errors? |
|
| Back to top |
|
|
| RatherBeGolfing |
| Posted: Wed Jan 07, 2004 12:23 pm Post subject: |
|
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
Unless I'm not remembering correctly (we don't use the mainframe CAF feature any longer - too expensive!), but the channels are very transient. They connect when there are messages to deliver, then disconnect immediately. And, I don't think there is any configuration to them, like you don't have control of things like disconnect interval.
So, the two messages you see in the CHIN task look completely normal to me!
Larry
Certifiably MQ |
|
| Back to top |
|
|
| moepi |
| Posted: Wed Jan 07, 2004 11:37 pm Post subject: |
|
|
Novice
Joined: 11 Jul 2001
Posts: 21
Location: South Africa
|
Hi Guys,
Thanks for you replies.
On the client side(Sun Solaris) I get Return Code 2059 -
'2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE'
But the queue manager is running and processing messages/requests from other applications that are not doing the client connection.
Ta,
Moepi,
x3611 |
|
| Back to top |
|
|
| offshore |
| Posted: Thu Jan 08, 2004 4:10 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
moepi,
From the MQ Messages and Codes book:
1:
This reason code can occur if the call is issued by an MQSeries client application and there is an error with the client-connection or the corresponding server connection channel definitions.
Do you have a ServerConn channel defined w/ the same name?
If you have a ClientConn Channel called MAINFRAME.MQCLIENT.01 I think you need a ServerConn created called MAINFRAME.MQCLIENT.01
2:
On OS/390 or z/OS this reason code can also occur if the optional OS/390 or z/OS client attachment feature has not been installed.
Did you verify the CAF was installed? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
