Re: Debug into /INCLUDE -- WDSCI-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.

That works, thank you!

-----Original Message-----
From: MichaelQuigley@xxxxxxxxxx [mailto:MichaelQuigley@xxxxxxxxxx]
Sent: Thursday, August 30, 2018 10:47 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debug into /INCLUDE

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 08/30/2018 10:45:56 AM:

----- Message from Justin Taylor <JUSTIN@xxxxxxxxxxxxx> on Thu, 30 Aug
2018 13:43:02 +0000 -----

To:

"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] Debug into /INCLUDE

Yes, it debugs into the *SRVPGM just fine. For the procedures that
aren't exported, the /INCLUDE brings the actual RPG code itself into
the RPGUnit test. It runs fine, but it seems the debugger can't see
the source in the /INCLUDE, so it just goes to the /INCLUDE directive

itself.

I'm not married to this method of testing non-exported procedures.
If someone has a better way, I'm all ears.

Thanks

Do you need to right-click and switch to the *LISTING view?

Michael Quigley
Computer Services
The Way International

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.