× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Brad,

May I ask why you need to check again the file value? If you add a record to
your file is really easy to check if the operation was successful or not.
Also, you can do an *AFTER INSERT trigger, and (AFAIK), it would fire ONLY
if the record is added.



Regards,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Mon, Apr 4, 2011 at 11:57 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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.