RE: DEBUGGING TRIGGER ERROR ENDS before it gets started

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Please say more - can you add a record using DFU? Where is it stopping?

What is the message ID?

The trigger program is supposed to run in your own job. You should be able 
to STRDBG TRGLIB/TRGPGM and see the source, where you can set a breakpoint 
(F6) and press F12 to continue, or press F10 to have it break at the first 
executable statement.

According to the IBM info, be sure to create the trigger program with 
*CALLER activation group. Also, have it created with USRPRF(*OWNER) and 
make sure that profile has enough authority.

And be sure the program is created with DBGVIEW(*ALL) - I recommend *ALL 
just to be sure you get it.

Is the program ILE or OPM? If the latter, you need to set a parameter on 
STRDBG to activate OPM debugging.

Then do something like an INSERT in SQL, or use DFU to add a record (if it 
is an BEFORE-ADD trigger).

Uh, check for the kind of trigger it is.

HTH

Vern

At 09:51 AM 3/11/2003 -0800, you wrote:
> Doesn't make it far enough to put in debug
>
> -----Original Message-----
> From: Westdorp, Tom [mailto:Tom.Westdorp@xxxxxxxxxxxxxxxxxx]
> Sent: Monday, March 10, 2003 4:37 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: DEBUGGING TRIGGER ERROR
>
>
> start a debug session for your trigger program in a green screen session,
> set a breakpoint on the first executable line,  use DBU or DFU or something
> to do what causes the error (add a record or update a record or delete a
> record) and step through the code to see what the lower level error is.
>
> -----Original Message-----
> From: Jose Vega [mailto:jvega@xxxxxxxxx]
> Sent: Monday, March 10, 2003 4:23 PM
> To: Midrange Systems Technical Discussion
> Subject: DEBUGGING TRIGGER ERROR
>
>
> Hi All,
> Trigger gives a "trigger error" before the program is called.  No joblog or
> any indication of what the issue may be.
> Plese Help. All advice is greatly appreciated.
>
> TIA
>
> Jose