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
-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
Sent: Thursday, August 30, 2018 6:56 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debug into /INCLUDE
Hi Justin
Mr Obvious here - are the service programs debuggable? You are describing behavior when the thing being called is not.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
