Re: Newbie: debug a program running in batch -- WDSCI-L

Subject: Re: Newbie: debug a program running in batch
From: dlclark@xxxxxxxxxxxxxxxx
Date: Thu, 3 Nov 2016 10:12:29 -0400
List-archive: <http://archive.midrange.com/wdsci-l/>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 11/02/2016 09:15:40 PM:

I've got the SEP set on the program. I'm in the debug perspective. I

have

the source code up and have a breakpoint set on the first executable
statement in the program.

Normally, you do not have to be in the debug perspective and you
do not have to manually set a breakpoint. The "trick" is to make sure the
user and library are correct for the actual job and program that will be
running. By default, the SEP will take care of stopping at the module
entry point for all modules. When the program starts the debug
perspective will be activated automatically -- at least, that is how it
works for me.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Newbie: debug a program running in batch , Justin Taylor

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.