The called program will always be processing the same basic data.
The main concern is that if the processing requirements in the called program
change, what is the best way to ensure that I will always get the latest

Jeff Young
Sr. Programmer Analyst

From: "rob@xxxxxxxxx" <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Fri, June 17, 2011 10:37:49 AM
Subject: Re: Trigger Processing Question

"best" is up to more information.  Earlier (this week?) it was discussed
that if the "other processing" may check some data and then block the
update from going through then you do not want a separate process/job - be
it data queue, sbmjob, whatever.

If you plan on making numerous changes then you may wish to have the
initial trigger program be bare bones and perhaps do NO work (not a single
IF statement or whatever) and just pass the same parameters on to a second
program.  This will allow your initial trigger program to run unchanged
and the program it calls can be changed on a whim.

Then you just have your usual concerns with the initial calling program to
ensure that it is running the new mod and not something out of QRPLOBJ or

Rob Berendt

This thread ...


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

This mailing list archive is Copyright 1997-2019 by 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].