| Author |
Message
|
| bay hoe san |
 Posted: Fri Dec 14, 2007 12:20 am Post subject: MQGET Slow During the Hour? |
 |
|
Centurion
Joined: 27 Nov 2006
Posts: 117
|
Hello,
I have a rather strange observation in my qmgr setup at my client side. A simple diagram of the appl flow:
Server send msgs -> host MQ > starts a CICS txn (TA11) which will read the msgs via MQGET -> starts another CICS txn (TB12) in anther CICS for each MQGET
The strange phenomenon I observed is that very near to the hour say 11:59:57 to 12:00:30, 14:59:57 to 15:00:10 and 17:59:58 to 18:00:20 there was no TB12 but TA11 is still active. CICS is healthy and MQ is healthy too. No archiving is sighted in the started task of CICS or MQ.
Is there any time parameter setting in MQ where some activities are processing backend?
Pls advise.
Thank you.
.Hoe San. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Dec 14, 2007 2:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The z/OS does do background processing to check for expired messages but I'm not aware it's time driven - IIRC it runs every 15 mins or so when the queue manager is idle.
I'd ask the sys progs if they have an SMS job or similar scheduled at the top of the hour. Sounds far more likely.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bay hoe san |
| Posted: Fri Dec 14, 2007 2:54 am Post subject: |
|
|
Centurion
Joined: 27 Nov 2006
Posts: 117
|
1. Thanks for your advise. I have checked with sys prog, SMS is every 15 mins.
2. There is a parameter setting in CSQ1ZPRM, STATIME=30, is this the time every 30 mins after start up the qmgr, it will write to SMS?
3. I am just wondering will CICS play a part in the observe delay during the hour?
Appreciate all advice.
Thanks. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 14, 2007 3:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I still think it's something external (CICS / SMS / etc) that runs hourly on a wall clock schedule.
Everything you've mentioned uses time from startup. It's going to be a bit odd if the software was started exactly on the hour.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Dec 14, 2007 10:21 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 17, 2007 1:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PeterPotkay wrote: |
On z/OS only you control how often this runs by the QM's Expiry Interval parameter (EXPRYINT).
|
Again I learn from the board 
So it is indeed a countdown timer, expressed in seconds, rather than a wall clock scheduled event. But now I can prove it from the manual!
Many Thanks! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
