| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| How to Close a Queue on z/OS |
View previous topic :: View next topic |
| Author |
Message
|
| Ross |
 Posted: Fri Jan 12, 2007 9:56 am Post subject: |
 |
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
It is being kicked off as a batch job.
It looks like we are going to recycle the CHIN to fix this... Beaten it seems  |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Sun Jan 14, 2007 10:40 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
CHIN? No, the MSTR (unless the stuck queue is a XMITQ)
Please let us know your results..... this is a very interesting one....
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Ross |
| Posted: Mon Jan 15, 2007 5:43 am Post subject: |
|
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
I was on a call with support from IBM and when they suggested recycling the CHIN, I had raised this question as it was not being held across a channel. But CHIN was the answer I got, so was pushing for a Qmgr recycle. This was the decision made, but not necessary it seems.
I logged on to check it out further yesterday, and the thread was gone. I am trying to get hold of the developer to find out if she did anything, because so far noone seems to know what fixed it! So I can’t try other options now!
There was no recycle. I will post the answer when I have it. |
|
| Back to top |
|
|
| Ross |
| Posted: Tue Jan 16, 2007 10:29 am Post subject: |
|
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
Hi,
The issue is fixed, but not 100% sure how! Here is some information.
I logged on to my queue manager on Sunday morning to verify the status of the queue, before the Qmgr recycle was scheduled a few hours later.
The queue had no open threads so was looking fine, and this issue is now resolved. This was without the need for the Queue Manager recycle.
I have been following this up with the developers and other support areas and they all seem to believe this was resolved by the recycle (hours later) so were not aware of it being fixed earlier.
I have been trying to find out the issue, but all I have is the following.
Issue arose when the job was “force completed” in ca7(Thursday night). Although there were no visible jobs in SDSF, I believe they may be still “active” in ca7. So the scheduled jobs (runs hourly) were removed from the schedule (Friday night) so they would not try to start until after the recycle.
This is the only piece of information that seems a possible resolution of the issue. Unless I have a helpful ghost!
Thanks for the help.
Ross. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Tue Jan 16, 2007 10:47 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
setting a job "force complete" in ca7 just updates its status, because ca7 did not encounter the job end. i dont think that caused anything.
very suspicious....... that it has gone away...... from my point of view, something must still have been active in MVS or in IMS.
you said it was an IMS batch. so was IMS recycled before sunday morning when you checked the queue status and found it thread-free?
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
