Re: Trigger techniques

The only possible issue with this...

If your actual trigger does an update to another file that also has
the gentrigger attached, the process will blow up because RPG doesn't
allow recursive programs.

Unless,
--- the gentrigger activation group is *NEW, which would be a horribly bad idea.
--- your on 6.1 or higher and gentrigger is a linear-main program that
doesn't use the cycle.

Otherwise, your gentrigger should really be a ILE C or ILE CL program.
( you could also have just a C or CL entry point with RPG modules in
an ILE program)

HTH,
Charles





On Wed, Apr 7, 2010 at 6:30 PM, Rick DuVall <R_C_DUVALL@xxxxxxxxxx> wrote:

Hello Jon,

I use a generic rpg trigger (called gentrigger) which determines the
name of the actual trigger program from the file name and calls it
with the standard parms. The actual trigger program is compiled
*caller. I also have a file which contains the trigger name and
whether to restart it or not.

When I need to replace a trigger, I promote the change and input a
flag in the file that says reload. the next time it fires, it checks
the file, sets on LR and changes the flag back.


Wednesday, April 7, 2010, 5:14:58 PM, you wrote:

Anyone care to share what they do to facilitate being able to bring a
new version of a trigger program into use.

Jon Paris

--
Best regards,
 Rick

Systems Manager
Dealer's Auto Auction of Okc
1028 S. Portland
Oklahoma City, OK 73108
(405) 947-2886
mailto:rick@xxxxxxxxxx
http://www.nothingisreal.com/dfki/no-word

--
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.