Debug OPM programs was (CONVERT TO RPGLE and CLLE) was WDSC vs SEU

Thanks Micheal for the Wiki link

As far as the Wiki, see:
http://wiki.midrange.com/index.php/Service_Entry_Point
Michael Quigley
AS/400 Programming Section
The Way International
www.TheWay.org

Also I will see that we get the V5R3 PTF SI28283 installed, so that
the programmers dont need *SERVICE (shhh dont say it too loud, auditors
about).


Thanks Charles for the debug tip.

date: Fri, 26 Oct 2007 08:42:51 -0400
from: "Wilt, Charles" <WiltC@xxxxxxxxxx>
subject: Re: [WDSCI-L] (CONVERT TO RPGLE and CLLE) was WDSC vs SEU
Frank,
Make sure your RPG III programs are compiled with OPTION(*SRCDBG) or

OPTION(*LSTDBG).

If you want to debug an interactive program, you need to go to a 5250

session and issue the following

command: STRRSESVR NAME('your wdsc connection name')
For example, in WDSCi, my connection is named "Dev - Fire and First Aid",

so the STRRSESVR command I

used is:
STRRSESVR NAME('Dev - Fire and First Aid'). This creates an link between

the 5250 session and WDSCi

which allows WDSCi to use the session for running interactive commands.
Then right click on the program object in RSE and select Debug As or

Debug(Prompt). By default, the

system will start the program with a simple call (for interactive) or

SBMJOB (for batch) with no

parameters. If you need to start it in some other way, make sure you

choose Debug(Prompt). From the

menu that displays when you select Debug As or Debug(Prompt) select Batch

or Interactive.

Since we have a menuing system that does some stuff behind the scenes,

when I need to debug an

interactive app, I find it easiest to simply do the Debug

(Prompt)-->Interactive and on the "how to

Start" tab, I enter the command which starts our menuing system. Then I

work my way through the

menuing system and when I start the program I had select for debug, it

pops up in the WDSCi debugger.

HTH,
Charles

Frank Kolmann