I just felt a great disturbance in the force as the 1500 list members all experienced deja vu at the same time. -- T.Rob T.Robert Wyatt, Consulting IT Specialist IBM Software Services for Websphere email: [EMAIL PROTECTED] 704-719-2107 Access Line
MQSeries List <[email protected]> wrote on 03/30/2007 11:11:05 AM: > I found the culprit that was causing trigger on FIRST to behave like > tiger on EVERY. It was a badly coded CICS transaction that was > opening, putting and closing a queue and used the MQOO _INPUT as an > open option. Messages were put to that queue from a distributed > platform and CICS screens. A batch program was supposed to kick off > and process the messages. With users working on a CICS screen, there > were occasions when because of volume, many transactions were put > between the batch job being triggered and actually starting. We are > talking about a couple of seconds here, but this was enough for > multiple trigger messages to be generated, one for each message put > during this interval. > > I was stumped because the batch job started long before TRIGINT had > expired, yet executed and retrieved zero messages from the queue on > many occasions. Everyone was convinced that it was an MQ problem > until I looked at the code and painstakingly walked them through how > what they did caused this problem. > > > > > List Archive - Manage Your List Settings - Unsubscribe > Instructions for managing your mailing list subscription are > provided in the Listserv General Users Guide available at http://www.lsoft.com To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
