Re: Trigger Program

[DAsmussen@xxxxxxx]

Gade,

In a message dated 12/27/99 3:30:48 PM Eastern Standard Time, 
Gade_R_Reddy@consecofinance.com writes:

> Please let me know how do we debug a Trigger program??.

Not to oversimplify, but you should be able to start your debugger of choice 
on the program (without invoking it) and then call a program that 
writes/updates the triggered file from the same session and perform whatever 
action you have triggered on a record.  Triggers become part of the job that 
caused them to be invoked, so your debugger should pop right up with the 
trigger program.  We found out the latter the hard way when a job got 
terminated after the trigger generated enough "...changed to 
SEQONLY(*YES)..." messages to fill the joblog, which wasn't set to *NOWRAP or 
*PRTWRAP.

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"Lots of folks confuse bad management with destiny." -- Kin Hubbard
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---