By expiring, I mean the DISCONNECT Interval value.  You could set it to a low value, e.g. 1 minute, so you don't have to wait very long for the state to change from RUNNING to INACTIVE.



Shmuel Koller <[EMAIL PROTECTED]>
Sent by: MQSeries List <[email protected]>

02/28/2006 01:36 PM

Please respond to
MQSeries List <[email protected]>

To
[email protected]
cc
Subject
Re: LeftOver CHSTATUS





Thanks,
For the LeftOver CHSTATUS on z/OS - I can indeed define partner channel receiver  (on Windows) and get them connected in RUNNING status. But this does not help me to delete CHSTATUS when STOPPING.
 
I would love the definition to expire, as you say - do not know how, what does it mean in my case of CLUSTER SENDER.
 
This CHSTATUS behaves like  a permanent object without CHANNEL. When stopped, it is displayed under SAVED option. CHINIT always tries to start it.
 
I tried RESET for the channels, RECOVER - nothing helps.
 
Ideally I would look for a way to delete SAVED CHstatus - as any other object.
 
Shmuel Koller
Discount Bank
 
 
----- Original Message -----
From: [EMAIL PROTECTED]
To: [email protected]
Sent: Monday, February 13, 2006 5:08 PM
Subject: Re: LeftOver CHSTATUS


I've run into a similar situation using a sdr/rcvr pair, but it was my monitor that complained about it.  Eventually, I just defined the missing channels, started it and let it expire, then deleted them.  You may want to try the same thing.



Shmuel Koller <[EMAIL PROTECTED]>
Sent by: MQSeries List <
[email protected]>

02/27/2006 03:18 PM

Please respond to
MQSeries List <[email protected]>


To
[email protected]
cc
Subject
LeftOver CHSTATUS







I am testing MQ cluster made of Windows and z/OS QMGRs, disolving cluster
and creating again.
Windows QMGRs are easily deleted altogether and recreated, each time new
CLUSTER name.

Now I am stuck under MQ V6 on z/OS with a stubborn  CHSTATUS lets say
CLUSTER.TO.MQSK
(MQSK on Windows) in RETRY status.

This used to be a  Cluster-Sender channel on z/OS, channel which does not
exist any more, except as CHSTATUS.
The cluster itself was aslso disolved.

I attempt many things to get rid of this CHSTATS - recycle z/OS CHINIT,
recycle z/OS QMGR, define a channel that corresponds to CHSTATUS and
stop+delete it; nothing helps:   the CHSTATUS appears in RETRY mode  after
QMGR startup.

How to I clean this away ?

Shmuel Koller
Discount Bank

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html


Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Reply via email to