Re: Debugging a Module

Grizzly,

If you are using STRDBG, you must start the debug session on the program.
This will initiate the debug session on the Program Entry Procedure. Then
Press F14 and place a 5 in front of the module you wish to debug. This will
display the source for that module. You can set your watches and
breakpoints from there.


Thanks,

Mark


Mark Walter
Sr. Programmer/Analyst
Hanover Wire Cloth a div of CCX, Inc.
mwalter@hanoverwire.com
http://www.hanoverwire.com
717.637.3795 Ext.3040


|--------+-------------------------------->
|        |          "Malchow, Grizzly"    |
|        |          <GMalchow@automaticpro|
|        |          ducts.com>            |
|        |          Sent by:              |
|        |          rpg400-l-admin@midrang|
|        |          e.com                 |
|        |                                |
|        |                                |
|        |          08/01/2002 11:01 AM   |
|        |          Please respond to     |
|        |          rpg400-l              |
|        |                                |
|--------+-------------------------------->
  
>-----------------------------------------------------------------------------------------------------------|
  |                                                                             
                              |
  |       To:     "'rpg400-l@midrange.com'" <rpg400-l@midrange.com>             
                              |
  |       cc:                                                                   
                              |
  |       Subject:     Debugging a Module                                       
                              |
  
>-----------------------------------------------------------------------------------------------------------|




This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hello,
I am trying to debug a module and I'm having a little bit of trouble doing
so. I created the module with the debugging view set to *SOURCE, like I
would when I'm compiling a regular RPG IV program. The module is bound in a
CRTPGM statement. I'm not exactly sure where the conflict is happening. I
don't know if I'm using the right debugging view when I create the module,
and I don't know if I'm taking the right approach to debugging the module.
For example, do I have to set the debug on the program that binds the
module
and then include the module, or do I try to set the debug on the module
straight away.
Any Ideas?

Grizzly Malchow - Programmer/Analyst
Gross-Given Mfg. Co./Automatic Products International
Direct (651) 290-6185
Fax    (651) 224-5559
gmalchow@automaticproducts.com
http://www.automaticproducts.com/


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.