Hi all,
Chapter 14 of the Applications Programming Guide has a good topic:
What is triggering?
-Original Message-
From: Anderson, Lizette T. (RyTull)
[mailto:[EMAIL PROTECTED]]
Sent: 19 November 2002 09:52
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
My initiation queue
Thanks for the explanation.
-Original Message-
From: Robert Broderick [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 2:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
The LOCAL queue you are putting to has the name of the INITQ and the process
name. The INITQ is
:41 PM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
You certainly need a trigger monitor for each initq. But that begs the
question, why do you have another initq?
> -Original Message-
> From: Anderson, Lizette T. (RyTull)
> [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday,
: [EMAIL PROTECTED]
Subject: Re: Trigger problem
One INITQ should do it, unless of course you are working with a Client
Trigger monitor in addition to the regular trigger monitor.
bobbee
>From: Stefan Sievert <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTE
)" <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
Date: Tue, 19 Nov 2002 12:53:39 -0600
Bobbee thanks so much for your help, but I am still confused. Here is how
I
have it setup:
-The local queue points to t
; Subject: Re: Trigger problem
>
> But we are also using a different init queue.
>
> -Original Message-
> From: Stefan Sievert [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 18, 2002 4:20 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Trigger problem
>
>
>
One INITQ should do it, unless of course you are working with a Client
Trigger monitor in addition to the regular trigger monitor.
bobbee
From: Stefan Sievert <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Trigger probl
Thanks.
-Original Message-
From: Peter Heggie [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 1:57 PM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
Application queues (and transmission queues on distributed platforms) can
use triggering, so they would have an entry in
November 19, 2002 8:10 AM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
The values for the target of the trigger is handled in the Process object.
One trigger monitor can handle two queues. The process defination is based
in the triggering queue, not the INITIATION queue.
bob
Sievert [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 12:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
The obvious question would be: why? ;-)
You really only need one INITQ in most cases, unless - as Dennis pointed out
- you have different trigger monitors; or a very
I am lucky. I only have two. I will change this to use just one trigger
monitor. Maybe that will correct my problem. Thanks.
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 12:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
PROTECTED]
Subject: Re: Trigger problem
The values for the target of the trigger is handled in the Process object.
One trigger monitor can handle two queues. The process defination is based
in the triggering queue, not the INITIATION queue.
bobbee
>From: "Anderson,
tions you might
already have, you can always create an alias for the 'second' INITQ pointing
to the 'first' and do the cleanup one-by-one.
HTH,
Stefan
From: "Anderson, Lizette T. (RyTull)" <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To:
)
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 10:20 AM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
But we are also using a different init queue.
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 18, 2002 4:20 PM
To: [EMAIL PROTECTED
ECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
Date: Mon, 18 Nov 2002 14:57:30 -0600
It triggers a different program in a different directory.
-Original Message-
From: Miller, Dennis [mailto:[EMAIL PROTECTED]]
Sent: Monday, N
But we are also using a different init queue.
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 18, 2002 4:20 PM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
Doesn't matter, it's the process definition which controls what gets
trig
your
train has more engines that boxcars.
regards,
Dennis
> -Original Message-
> From: Anderson, Lizette T. (RyTull)
> [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, November 18, 2002 12:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Trigger problem
>
> It triggers
Doesn't matter, it's the process definition which controls what gets
triggered. One trigger monitor is all you need.
Stefan
From: "Anderson, Lizette T. (RyTull)" <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: T
It triggers a different program in a different directory.
-Original Message-
From: Miller, Dennis [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 18, 2002 11:19 AM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
Unless you have extenuating circumstances, one trigger monitor should
Unless you have extenuating circumstances, one trigger monitor should work
for both applications.
> -Original Message-
> From: Anderson, Lizette T. (RyTull)
> [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, November 15, 2002 8:13 AM
> To: [EMAIL PROTECTED]
> Subject: Trigger problem
>
> I
I think V5.2 under Windows sets up a trigger monitor for you when you create
your queue manager via the GUI. If you remove one of the trigger monitors,
it should be ok.
- Original Message -
From: "Anderson, Lizette T. (RyTull)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, Nov
21 matches
Mail list logo
