Re: Trigger Question

Albert,

That's what I was thinking too. Have the trigger program submit a job
passing the original value of the field in question.

Then that submitted job will check the value after 30 seconds. It
should eliminate the worry about holding up any other active jobs
itself.

Brad

On Mon, Apr 4, 2011 at 11:39 AM, Albert York <alfromme@xxxxxxxxx> wrote:

Instead of pausing in your trigger program, submit a job to do it.
Better yet, have an active job waitiing on a data queue.

Albert


On Mon, Apr 4, 2011 at 9:27 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

Ok, before I get too deep into this, I've had a request to make this change:

1.  Add a trigger to a file for when records are added.
2.  If after 30 seconds, the record isn't updated (a status type
field), send a message to QSYSOPR

Now, sounds easy enough, but I'm wondering if that 30 second delay
that I'd put in would hold a lock or anything on that record, or cause
any other problems?  It's been a while since I did a trigger.  :)

What I would do is:

Trigger PGM

store original value from ADD to file
pause(30)
Chain to the file and check that original value <> new value

Thanks!

Brad
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.