| Author |
Message
|
| KathyB |
 Posted: Wed Aug 16, 2006 8:02 am Post subject: DPL Bridge - current queue depth in error |
 |
|
Apprentice
Joined: 02 Feb 2004
Posts: 30
|
platform: z/OS - CICS 2.2 - MQ V6
I have recently noticed that a DPL bridge queue field 'current queue depth' is showing a value when, in fact, the queue is empty.
My user sends a message from Region A to Region B with the reply back to Region A. He is not reporting any problems in running his application and is receiving the response that he expects.
Could this be a syncpoint issue and when the Region B program executes it needs to issue an exec cics syncpoint call?
Any insight would be appreciated. |
|
| Back to top |
|
 |
| KathyB |
| Posted: Wed Aug 16, 2006 10:06 am Post subject: DPL Bridge - current queue depth in error |
|
|
Apprentice
Joined: 02 Feb 2004
Posts: 30
|
Mystery solved. The user is debugging his program and ending his debug session prior to issuing a syncpoint.
I do not see that there is a way to reset current queue depth counter? I'm not having any luck issuing get calls with syncpoint. Any other suggestions? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 16, 2006 10:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
On distributed there is a command to resolve uncommitted messages.
I don't know how to do it on zed OS.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| KathyB |
| Posted: Wed Aug 16, 2006 11:10 am Post subject: |
|
|
Apprentice
Joined: 02 Feb 2004
Posts: 30
|
| You must mean resolve with commit on the sender channel. Tried that too without any luck. Thanks for the suggestion. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 16, 2006 11:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| KathyB |
| Posted: Thu Aug 31, 2006 7:45 am Post subject: |
|
|
Apprentice
Joined: 02 Feb 2004
Posts: 30
|
Just an FYI to those using the CICS DPL Bridge Queue.
I reported the problem that I was having with the current queue depth value not reflective of the actual number of messages to IBM IBM.
They said this is a code defect in version 6. The APAR is PK17137 and there is a target date of 9/8/2006 for the PTF.
In the meantime, running the CLEAR QLOCAL command will reset the CurrentQDepth back to zero. Recycling the queue manager will also reset the count. |
|
| Back to top |
|
|
|
|
