Re: Compiling Trigger Program

We write a simple CL program to act like a wrapper for the trigger
program containing the logic.

Just getting and passing along the required parameters:

0005.00 PGM PARM(&BUFR &BYNARY)
0006.00
0007.00 DCL VAR(&BUFR) TYPE(*CHAR) LEN(1001)
0008.00 DCL VAR(&BYNARY) TYPE(*CHAR) LEN(4)
0009.00
0010.00 CALL PGM(TTT) PARM(&BUFR &BYNARY)
0011.00
0012.00 ENDPGM

TTT is the "real" trigger program that performs the required logic.

El Tue, 12 Apr 2016 14:23:46 -0400
Vinay Gavankar <vinaygav@xxxxxxxxx> escribió:

Thanks. Just confirmed that the programs are locked. Will defer the
recompilation to a time when there is an 'outage' and all the engines are
down.

On Tue, Apr 12, 2016 at 1:19 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

Vinay Gavankar asked:

Can I recompile a Trigger Program when the Trigger is Enabled and the

file is open?

and Dave Clark replied:

The program object is not locked so it can be replaced/recreated.

That's not MY experience.

In my experience, trigger programs are ALWAYS locked (multiply locked, if
the trigger program is shared by many files) by every job that trips them,
and remain so until the job either ends or closes the triggered file(s) and
does a RCLRSC.

If you expect to be doing a lot of recompilation of trigger programs, you
might want to use a trigger-mediator.

--
JHHL

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.