RE: Debugging a Trigger

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Try going to a command line, starting debug on the trigger program, set a
breakpoint on the first line of the calc specs, then use DBU, DFU or
something to add/change/delete a record in the file and voila there's your
breakpoint.  Trigger will do the same thing in batch or interactive, so one
job's as good as another to get your trigger to fire.

-----Original Message-----
From: afvaiv [mailto:afvaiv@wanadoo.es]
Sent: Wednesday, November 20, 2002 3:46 PM
To: MIDRANGE-L
Subject: Debugging a Trigger


Hi, I've been searching thru the archives but could not find an answer.
We have a trigger we'd like to debug.
I remember debugging a batch job with STRSRVJOB, but in this case the
trigger runs as a new job everytime since each instance of  it will end
with *inLR ON, so we have no way of knowing its next job's name/number
in advance.
How should we debug the trigger program?
TIA
-------------------------
Antonio Fernandez-Vicenti
afvaiv@wanadoo.es


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.