|
Just start debug in your current interactive session for the trigger program. Set your break point, then upddta on the file it is attached to. It should break, debug normally. For a batch job, submit held, strsrvjob, strdbg on the trigger program, release job, enter your debug options. Chris Bipes -----Original Message----- From: afvaiv [mailto:afvaiv@wanadoo.es] 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?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.