Re: Newbie: debug a program running in batch

Sending this again as the body of my reply got deleted in transmission
somehow. 8-{

Michael Quigley
Computer Services
The Way International
www.TheWay.org

----- Forwarded by Michael Quigley/TheWay on 11/03/2016 11:00 AM -----

Michael Quigley/TheWay wrote on 11/03/2016 08:28:20 AM:

From: Michael Quigley/TheWay
To: wdsci-l@xxxxxxxxxxxx
Date: 11/03/2016 08:28 AM
Subject: Re: [WDSCI-L] Newbie: debug a program running in batch

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

PM:

----- Message from Dan <dan27649@xxxxxxxxx> on Wed, 2 Nov 2016 21:
15:40 -0400 -----

To:

Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] Newbie: debug a program running in batch

I'm on a v7r1 box and using RDi v9.5.0.3. I need to debug a program

that

runs in batch. I haven't had to use debug in quite awhile and the

last

time I had to debug a program running in batch predated my RDi

experience.

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.

When I call the program from the green screen, nothing happens in RDi
debug. The program finishes normally.

What am I missing?

The first things I always check when this happens are:

- Library list--i.e., Is RDi using the same library list as the green

screen?

- Verify connection--to make certain something is not amiss in your
IBM i or the connection to it.

- Another check related to the library list is to use WRKOBJ
*ALLUSR/program-name on the green screen. Then you can be sure that
there aren't multiple copies of your code.

- Try a RCLACTGRP *ELIGIBLE. (This is only a good idea to do in
development.) If you've recently recompiled, the green screen may be
running a version of the code in the QRPLOBJ library.

I also figure it would be good to make sure certain other points are

clear:

1) You do not need to be in the Debug Perspective before starting a
program with a SEP set. When the SEP is triggered, RDi will switch
to the Debug Perspective.

2) The source need not be open (RDi will open the source in Browse
mode) nor do you need to have a breakpoint set on the first
executable line. RDi always stops on the first line of the procedure.

These last two points said, it shouldn't cause any problem to be in
the debug perspective nor have the source open. A breakpoint set on
the first executable line is simply superfluous.

HTH,
Michael Quigley
Computer Services
The Way International
www.TheWay.org