|
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 ] What I do is STRDBG on the trigger program from an Interactive session, then either call the program that updates the triggered file our use something like DFU to change the file and cause the trigger to fire. Bill Erhardt Baldwin Hardware Corp > -----Original Message----- > From: afvaiv [SMTP:afvaiv@wanadoo.es] > Sent: Wednesday, November 20, 2002 6: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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.