× 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.



If you are using /COPY and STRDBG, cmd key 15 allows you to bring in copybook source.

This does not apply to /COPYBOOK from ww.rpglanguage.com/copybook.

One option is to debug over the intermediate (expanded) source file.

Regards,
John McKay
www.rpglanguage.com
www.mckaysoftware.ie

----- Original Message ----- From: "Alan Shore" <AlanShore@xxxxxxxx>
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, March 24, 2009 4:21 PM
Subject: STRDBG question


Morning all
I have a STRDBG question
within my program, I have a copybook of free-form code.
When I attempt to debug the program, the source code for the copybook does
NOT appear in my debug session.
Is there an H-spec (or something in debug) that should be used for me to
follow the source code within this copybook within debug?

As always, much appreciated



Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.