|
Hi Greg, Does the debugger terminated in between (i.e., you got a message telling you that program is terminated, and after you click on OK to dismiss the message, you coulld see the debug process in the Debug View is showing <terminated> status?) How about if you set a normal breakpoint on the first executable line of that program, will it be hit? Thanks, Xuan Chen, Problem Determination Tools for iSeries (905) 413-3769 T/L 969-3769 xuanchen@xxxxxxxxxx "Fleming, Greg \(ED\)" <GFLEMING@evergla To desdirect.com> <wdsci-l@xxxxxxxxxxxx> Sent by: cc wdsci-l-bounces@m idrange.com Subject [WDSCI-L] Debug doesn't break when called second time from same job 06/02/2006 05:29 PM Please respond to Websphere Development Studio Client for iSeries <wdsci-l@midrange .com> We have a job which calls a program one or more times depending on data conditions. When I set a service entry point for this program, it breaks OK the first time it gets called, then debug terminates as I would expect after last record is set, but then the program gets called again from the same submitted job, but debug doesn't break. If I submit the job again, it will break, but never breaks on subsequent calls from the same submitted job. If I run debug on the green screen using STRSRVJOB and STRDBG, it breaks every time. Am I missing something with the WDSC Debugger ? Thanks Greg Fleming Programmer/Analyst Everglades Direct, Inc. -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
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.