Did you try setting breakpoints for both calls to the RPG programs from within the CL, and use the Step Into function?
Also, are you adding both programs in the "Programs or service programs to be debugged" part of the Debug Configurations panel? From there when you are at the first breakpoint, I believe you can go into the Programs tab (which in my RDI is grouped with tabs such as Variables, Breakpoints, etc.) and navigate into each RPG program to set breakpoints there. I haven't used it much but you might find some value in trying to set things there...
-- Ken
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Englander, Douglas
Sent: January 20, 2015 12:00 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Debug question
I have one CL program that calls two RPG programs. The RPG programs are compiled with a debug view, and a Service Entry Point has been set in both RPG programs. I call the CL program from a green screen session. RDI brings up the first RPG program, and allows me to step through it to see what I need to see. When I am finished debugging the first program, I want it to continue (to the end), and then have the RDI debugger stop when the second program initiates. When I press F8 in the first program, the second program never goes into debug, and then CL ends. I have tried all of the different Step F-keys, and the second program never appears in the debug session.
I am running V 9.1
Has anyone else had this problem? A co-worker of mine has this same issue with a different (older) version of RDI. Are we both doing something wrong?
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
This e-mail and attachment(s) may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this message is strictly prohibited. If received in error, please notify the sender immediately and delete/destroy the message and any copies thereof. Although Associated Banc-Corp and/or its affiliates (collectively "Associated") attempt to prevent the passage of viruses via e-mail and attachments thereto, Associated does not guarantee that either are virus-free, and accepts no liability for any damage sustained as a result of any such viruses. Any federal tax advice contained in this communication (including any attachments) is not intended or written to be used or referred to in the promoting, marketing, or recommending of any entity, investment plan or agreement, nor is such advice intended or written to be used, and cannot be used, by a taxpayer for the purpose of avoiding penalties under the Internal Revenue Tax Code
midrange.com
