One possibility could be a timing issue. During a cold start, more
processing could be occuring vs. a warm start. Since CKTI is fired from
the PLTPI, it could have started the first instance of your triggered
transaction. If, for some reason, that instance got hung up, e.g. busy
system, and didn't have a chance to open the queue, another trigger message
could be created if another message arrives in the interim, causing the
second instance to be created
My question is, why doesn't your transaction terminate if it finds nothing
on the queue?
[EMAIL PROTECTED]
EMM.COM.AU To: [EMAIL PROTECTED]
Sent by: cc:
MQSeries List Subject: Re: Triggering Z/OS DLQH
CSQUDLQH
<[EMAIL PROTECTED]
en.AC.AT>
04/03/2003 05:39
PM
Please respond
to MQSeries List
Hi
I have once seen this abberrant behaviour of two trigger FIRST firing in
CICS - i wonder if anyone can explain why?
My CICS transaction is started by TRIGGER=FIRST on one queue and once it is
started it stays alive processing messages that arrive on the queue. Often
when CICS starts up there will messages on the queue and only one instance
of the transaction is started as expected.
One day the development CICS region crashed (cancelled by ops) and after a
cold restart I later saw that I had two instances of my trigger=first
transaction running. Both started at virually the same time when CICS came
up - nearly consecutive transaction numbers. Both were processing the same
queue as the transaction reports what queue it is started for, and nothing
else is taking messages off the queue. There would have been expired and
expiring messages on the queue, so could this have caused the queue manager
to create a additional trigger message?
This is CICS 4.1, MQ 5.2 on OS390 2.6
Thanks
Alan
Alan Turnbull
Senior Developer
QBEMM
Direct: (02) 8275 9880
[EMAIL PROTECTED]
Robert Broderick
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
TMAIL.COM> cc:
Sent by: MQSeries Subject: Re: Triggering
Z/OS DLQH CSQUDLQH
List
<[EMAIL PROTECTED]
AC.AT>
04/04/2003 07:21 AM
Please respond to
MQSeries List
The transaction will not trigger. One of the rules for first is that the
queue is not opened for input.
>From: Ronald Weinger <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Triggering Z/OS DLQH CSQUDLQH
>Date: Thu, 3 Apr 2003 15:54:29 -0500
>
>If a CICS transaction, for example, starts due to trigger on first, and
>then does a GET WAIT UNLIMITED, it is possible than a new message on the
>queue will trigger a second execution of the transaction, but the current
>execution will retrieve the message before the second one is attached.
>So the second will get a 'no-message-available', and if coded to issue a
>GET WAIT UNLIMITED, will remain suspended. A third message will trigger
>another transaction, but it will be retrieved by one of the two currentl;y
>suspended transactions. That sequence could continue until max tasks are
>reached.
>
>However, have you found a MVS batch trigger monitor ?
>
>
>
>
>
> "Gary P. Klos"
> <[EMAIL PROTECTED]> To:
>[EMAIL PROTECTED]
> Sent by: cc:
> "MQSeries List" Subject: Triggering Z/OS
>DLQH CSQUDLQH
> <[EMAIL PROTECTED]
> n.AC.AT>
>
>
> 04/03/2003 02:59
> PM
> Please respond to
> "MQSeries List"
>
>
>
>
>
>
>
> I am setting up to use the Z/OS utility CSQUDLQH, which handles the
> dead letter queue for a queue manager. What I was thinking was to put
> a trigger on FIRST on the dead letter queue and once it starts
> CSQUDLQH, then I could leave it running indefinitely. My question is
> this, if I use TRIGGER ON FIRST, and the queue triggers then CSQUDLQH
> removes all messages from the queue and stays running, then later
> another message goes on the dead letter queue, CSQUDLQH will start
> again. Does that mean I will have two batch jobs running CSQUDLQH, or
> does this program know to not run if it is already running with the
> same dead letter queue?
>
> Thanks,
> Gary
>
>Instructions for managing your mailing list subscription are provided in
>the Listserv General Users Guide available at http://www.lsoft.com
>Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
>
>
>
>
>
>
>The information contained in this message may be CONFIDENTIAL and is for
>the intended addressee only. Any unauthorized use, dissemination of the
>information, or copying of this message is prohibited. If you are not the
>intended addressee, please notify the sender immediately and delete this
>message.
>
>Instructions for managing your mailing list subscription are provided in
>the Listserv General Users Guide available at http://www.lsoft.com
>Archive: http://vm.akh-wien.ac.at/MQSeries.archive
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
________________________________________________________________________
IMPORTANT NOTICE : The information in this email is confidential and may
also be privileged. If you are not the intended recipient, any use or
dissemination of the information and any disclosure or copying of this
email is unauthorised and strictly prohibited. If you have received this
email in error, please promptly inform us by reply email or telephone. You
should also delete this email and destroy any hard copies produced.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
