| Author |
Message
|
| durgam4 |
 Posted: Tue Oct 07, 2014 5:42 am Post subject: MQ started task not coming down |
 |
|
Newbie
Joined: 07 Oct 2014
Posts: 5
|
| MQ sarted task is not coming down. The error I see is CSQY291E CSQWDSDM SDUMPX FAILED, RC=00000408,PBP1,ABN=058-00000010,PSW=070C00008. Can somebody throw some light on this error. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Oct 07, 2014 5:55 am Post subject: Re: MQ started task not coming down |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| durgam4 wrote: |
| MQ sarted task is not coming down. The error I see is CSQY291E CSQWDSDM SDUMPX FAILED, RC=00000408,PBP1,ABN=058-00000010,PSW=070C00008. Can somebody throw some light on this error. |
What version of WMQ? There seem to be some fixes in this area.
Mr Google also implies a variety of possible application code problems.
Perhaps if you gave some details? Like why you're trying to stop the started task, i.e. were there any previous errors that led you to try a shutdown? Or why you didn't just abend the address space and call it stopped?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 07, 2014 6:19 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
How did you attempt to shut the qmgr down? And why did you shut it down? Some other problem?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| durgam4 |
| Posted: Tue Oct 07, 2014 7:27 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2014
Posts: 5
|
every week , to run the disaster backup jobs, we bring down mq by giving
QMGR,STOP MODE(QUIESCE). |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 07, 2014 7:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| durgam4 wrote: |
every week , to run the disaster backup jobs, we bring down mq by giving
QMGR,STOP MODE(QUIESCE). |
And you're sure all the tasks using the queue manger have been shut down first?
I also ask again what version of WMQ this is.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| durgam4 |
| Posted: Tue Oct 07, 2014 8:34 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2014
Posts: 5
|
| yes. Version is IBM WebSphere MQ for z/OS V7.1.0 |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 07, 2014 9:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Is this an answer to my "are you sure all the tasks using the queue manager have been shut down"? If so, does this include non-application tasks like Tivoli?
To your original post, you say "started task is not coming down"; to be completely clear, are you asserting that the task issues this message and then hangs, resulting in you having to flush the address space to remove it?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| durgam4 |
| Posted: Tue Oct 07, 2014 9:30 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2014
Posts: 5
|
| this is the last message. "CSQJ139I PBP1 LOG OFFLOAD TASK ENDED " after this it got hanged |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 07, 2014 10:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Gosh, it's like pulling teeth. 
| durgam4 wrote: |
| this is the last message. "CSQJ139I PBP1 LOG OFFLOAD TASK ENDED " after this it got hanged |
So what you're now saying is that you sent the started task a queisce command, you saw the error message in your original post, the shutdown continued despite this apparent error with the output apparently ending with this information message and the task then hung.
So:
- Do you mean "hung" in the sense you had to force the address space?
- Were there any other messages you've not mentioned in the job log, which might offer some insight into what the task was waiting for?
- Can you absolutely and unequivically state that all of the tasks using the queue manager (application and non-application) were ended and there's no chance that the task is "hung" waiting for them to end as it's designed to do when you issue a stop quiesce.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| durgam4 |
| Posted: Tue Oct 07, 2014 10:09 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2014
Posts: 5
|
| Yes. I had to Cancel the started task. there were no messages other than this |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 07, 2014 11:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| durgam4 wrote: |
| Yes. I had to Cancel the started task. |
Ok
| durgam4 wrote: |
| there were no messages other than this |
So the JES log just had:
| Code: |
CSQY291E CSQWDSDM SDUMPX FAILED, RC=00000408,PBP1,ABN=058-00000010,PSW=070C00008
CSQJ139I PBP1 LOG OFFLOAD TASK ENDED
|
for this task? No other lines at all?
And once again I'll ask:
| Vitor wrote: |
| Can you absolutely and unequivically state that all of the tasks using the queue manager (application and non-application) were ended and there's no chance that the task is "hung" waiting for them to end as it's designed to do when you issue a stop quiesce |
Because until you answer that with "I'm absolutely positive that there is absolutely no chance there could be any connected MQ of either an application or a system nature, nor are there any orphaned connections on the queue manager" the solution to your "problem" is that there's no problem. The queue manager is waiting for the connected applications to end, exactly as you told it to.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MQsysprog |
| Posted: Tue Oct 07, 2014 11:09 pm Post subject: |
|
|
Centurion
Joined: 24 Feb 2014
Posts: 116
|
Hello ,
I would strongly suggest a deep review of this document :
http://www-01.ibm.com/support/docview.wss?uid=swg21577300
from the sdumpx message it appears you have a s058 abend and then a hang.
As my valuable colleague already pointed out ,probably this behaviour
derives from some type of connection that remain active and in this way hampers the shutdown of the Qmgr .
For example if you stop manually the chinint and the other connections ,what are thereafter the remaining threads still in the system ?
Hope that helps |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 08, 2014 4:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| durgam4 wrote: |
| I had to Cancel the started task. |
Given that you've had to cancel (never a good thing), it might be an interersting experiment to use FORCE rather than QUIESCE. If the queue manager goes down in this scenario, this points the finger squarely at something being connected to the queue manager.
You might also (separately) look into the log archiving activity of the queue manager. It might be "hanging" waiting for the offload to finish; if the offload either isn't working or is running slowly, this would give the apperance of a stuck task.
Of course, I'd expect a few additional console messages about that, rather than the 2 you claim are all that are produced. But then I find it hard to believe all you got were those 2. The console is typically much more verbose than that.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
