Author |
Message
|
barney0810 |
Posted: Fri Dec 08, 2006 2:04 am Post subject: Clustering on Mainframe |
|
|
Newbie
Joined: 10 Mar 2006 Posts: 5 Location: South Yorkshire
|
Has anybody come across a problem on the mainframe whereby you have items in the SYSTEM.CLUSTER.TRANSMIT.QUEUE and the Remote QMGR has been demised. Therefore the Sender channel is in Retry and the messages remain on the Q. If you force remove the QMGR from the cluster will the messages automatically be removed???? |
|
Back to top |
|
 |
Mr Butcher |
Posted: Fri Dec 08, 2006 2:23 am Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
no i dont think so. you have to remove the messages from the SCTQ by your own (or supply an alternative destination within the Cluster) _________________ Regards, Butcher |
|
Back to top |
|
 |
barney0810 |
Posted: Fri Dec 08, 2006 3:15 am Post subject: |
|
|
Newbie
Joined: 10 Mar 2006 Posts: 5 Location: South Yorkshire
|
Took a chance and did a force remove of the QMGR with queues, and the messages have dissapeared (Thank God!)
cheers all |
|
Back to top |
|
 |
Mr Butcher |
Posted: Fri Dec 08, 2006 6:39 am Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
very interesting.
thanks for letting us know. _________________ Regards, Butcher |
|
Back to top |
|
 |
Nigelg |
Posted: Fri Dec 08, 2006 7:12 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
Are you sure the msgs have not just been put to the DLQ?
This sounds a bit like the distributed APAR IC34717 (qv) which was fixed back in 2002. If the same APAR (or similar) is in the mainframe code, the msgs will now be in the DLQ, and you will need to decide what to do with them now. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
barney0810 |
Posted: Fri Dec 08, 2006 7:53 am Post subject: |
|
|
Newbie
Joined: 10 Mar 2006 Posts: 5 Location: South Yorkshire
|
They did infact go to the DLQ but thats good because now I can delete them. The problem I had before is that I was unable to delete the messages because other objects had exclusive GET on the SYSTEM.CLUSTER.TRANSMIT.QUEUE. |
|
Back to top |
|
 |
|