RE: Debug revisited

Okay, let's tackle this one step at a time...


> If I understand correctly, you have a CL program (or few CL
> programs) that
> eventually call RPG.

Correct



> Here is the simplest way to get you going:
>    Get a 5250 session and figure out its job number
>    Bring up the Distributed Debugger (make sure 'Attach'
> dialog is up).

There is no attach dialog.  I have 'Load Program', 'Attach Service' or
'Attach JVM'.  I'm quite certain I don't want either of these "attach"
options...  right?  So, i select 'Load Program'



>    Enter job name of your 5250 session in the following format:
>    jobName/userName/jobNumber
>    Enter the name of your RPG program in the 'Program to add to debug'
>    field.
>    Make sure your RPG program is compiled with debug data
>    Select 'Step Into' checkbox and press 'Attach' button

No problem until you mention the 'Attach' button.  Don't have one.


This must be a 5.1 option?




>    You will be asked to call your application in your 5250.
> Call your CL
>    program that starts the application and press OK on the
> message box.
>
>      If all of your CL code has no debug data, you will stop
> in your RPG
>      program (which must have debug data)
>      If any of your CL programs do have debug data, you will
> stop in the
>      very first one that does. Switch to the 'Programs' pane
> at the top
>      left corner of the debugger workbook. You should see
> your RPG program
>      there. Browse its source and set a line breakpoint
> appropriately. Now
>      you can simply run to a breakpoint in your RPG code.