| Author |
Message
|
| pcantin |
 Posted: Fri Apr 26, 2002 12:46 pm Post subject: |
 |
|
Novice
Joined: 16 Apr 2002
Posts: 15
Location: Québec/Canada
|
When my CICS region is shutdown, i got these message in the MSGUSR in SDSF.
CKBR 0000185 Bridge quiescing
CKBR 0000185 Waiting for 310 bridge tasks to complete
CKBR 0000185 Waiting for 310 bridge tasks to complete
CKBR 0000185 Waiting for 310 bridge tasks to complete
CKBR 0000185 Message found on starting or active queue but task not yet started
CKBR 0000185 MsgId 414D512041473432304120202020202095DE9D3C1250F30F
CKBR 0000185 Message found on starting or active queue but task not yet started
CKBR 0000185 MsgId 414D512041473432304120202020202095DE9D3C12D0FA0F
CKBR 0000185 Message found on starting or active queue but task not yet started
CKBR 0000185 MsgId 414D512041473432304120202020202095DE9D3C12F0FA0F
... 310 times
However, there is no message on the queue.
Someone got this problem ?
I have MQSeries 5.2 for OS/390. CICS is at TS 1.3 but the problem is also present with CICS 4.1 for MVS/ESA. |
|
| Back to top |
|
 |
| bob_buxton |
| Posted: Mon Apr 29, 2002 5:25 am Post subject: |
|
|
Master
Joined: 23 Aug 2001
Posts: 266
Location: England
|
The problem is with the MQ-CICS bridge rather than the MQ adapter.
(the adapter allows you to use the MQ API from CICS applications, the bridge is an interface to legacy applications that don't issue MQ calls)
Basically the bridge maintain a list of transactions it has has started and as they complete they are removed from the list.
So what has happened is that at shutdown the bridge has detected 310 transactions that should have run, it waits 3 times to give them a chance to complete and then issues messages listing the associated message ids.
So you need to investigate through the CICS message logs and your applications putting messages to the bridge queue whether you have some underlying problem that is preventing the transactions running successfully.
Also check that you are current with MQ service.
|
|
| Back to top |
|
|
| pcantin |
| Posted: Mon Apr 29, 2002 5:42 am Post subject: |
|
|
Novice
Joined: 16 Apr 2002
Posts: 15
Location: Québec/Canada
|
Thank's for the reply Bob !
Can it maybe a problem in the user application code or a bad parameter that is pass in the message header (MQMD or MQCIH) ? |
|
| Back to top |
|
|
| bob_buxton |
| Posted: Tue Apr 30, 2002 12:37 am Post subject: |
|
|
Master
Joined: 23 Aug 2001
Posts: 266
Location: England
|
It could be a number of things including specifying an invalid program/transaction in the CIH. Abends in the CICS application program,
CICS TCLASS restrictions not allowing the transactions to start etc.
Normally however there should have been some CICS abends and/or error messages plus an error response message on the reply-to message queue or the dead letter queue and the bridge should have removed the entry from its list of started transactions.
If you cant find any other evidence of a problem you may need to open a problem with the support centre.
Bob Buxton
_________________
Bob Buxton
Ex-Websphere MQ Development |
|
| Back to top |
|
|
| pcantin |
| Posted: Tue Apr 30, 2002 4:05 am Post subject: |
|
|
Novice
Joined: 16 Apr 2002
Posts: 15
Location: Québec/Canada
|
| I have opened a problem at ibmlink. |
|
| Back to top |
|
|
|
|
