Debugging a Module -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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 mailing list archive is Copyright 1997-2024 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.