| Author |
Message
|
| wilsonho3 |
 Posted: Wed Oct 02, 2002 6:22 am Post subject: Channel can not be started after a network down |
 |
|
Voyager
Joined: 20 Nov 2001
Posts: 98
Location: Hong Kong
|
hi, I have a problem concerning starting of channel. My site has a
NT box talk with the mainframe through MQSeries. I create a channel
in the NT1 and talked to the M/F with no difficultly to start the channel in
the begining. One day, the network is down on purpose for testing the
network. When I start the channel on the NT1 and the status is always
in a retry status. I check the receiver channel in the M/F and is runnung.
I try to resolve channel on both side and the problem remain. I use another NT2 box to create the same channel like the previous one to
connect to the same receiver channel on the M/F. suprisingly, the
NT2 channel is running. It seems that the channel is held on the NT1
for adnormal situation happen and can not be released and lock the
IP address for the NT1 channel. This is the log. Can anyone has such
experience and how to solve
log message
09/30/2002 12:47:09
AMQ9558: Remote Channel is not currently available.
EXPLANATION:
The channel program ended because the channel 'CS.PARRY.MQSD' is not currently
available on the remote system. This could be because the channel is disabled
or that the remote system does not have sufficient resources to run a further
channel.
ACTION:
Check the remote system to ensure that the channel is available to run, and
retry the operation. |
|
| Back to top |
|
 |
| udaybho |
| Posted: Wed Oct 02, 2002 6:57 am Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
Check the log on Mainframe side. That may give you some clue.
Uday Bhosle |
|
| Back to top |
|
|
| wilsonho3 |
| Posted: Wed Oct 02, 2002 7:30 am Post subject: |
|
|
Voyager
Joined: 20 Nov 2001
Posts: 98
Location: Hong Kong
|
I check the log on the M/F
***CHIN
***STR
and the log show no adnormal message. I has the problem solved
until I down up the MQSeries in The M/F. I dont want to down up
the MQseries on the M/F everytimes and I want the origin of the
problem. Does any type of setting to release the MQ resources when
unusual thing happened. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Wed Oct 02, 2002 9:08 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
When the mainframe channel receiver is in run status and the sender is in
retry, you need to stop the rcvr channel using a mode(force) and then restart the rcvr channel and restart the sender this will get you going.
The issue that causes this is the mainframe rcvr channels socket connection is in a wait state for packets and when the network goes down for about 10 min (not 100% sure of time) the connection is broken and once this happens the sender tries to create a new socket connection to the rcvr but the mainframe sez it already has a connection for this channel
and doesnt start up.
To fix this permantly you need to configure the mainframe queue manager to use a attribut AdoptMCA
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Oct 02, 2002 9:41 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| We had the same issues a while ago. AdoptMCA makes it all better. |
|
| Back to top |
|
|
|
|
