In my debug experiences, you have to make sure you have the correct library references for the objects. I've had situations where I set up a debug only to wonder why it didn't stop. I found out it was due to a different version of the program being called; that is, from another library. You might want to check if that's what is happening here.
I have had success in dual debug sessions, but I find RDi is not as friendly in telling you what you are seeing. For example, if I want to debug a field in both programs, I have to remember which field (in the Monitors view) is to which debug session. But at the same time dual debug sessions has been very helpful in RDi to spot what is causing a program to behave differently in another environment.
-- Ken
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Greg Wilburn
Sent: April 13, 2016 12:35 PM
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] Set Service Entry Point for two programs?
ASSOCIATED BANK SECURITY NOTICE: External email. Please make sure you trust the sender before responding, clicking links or opening attachments.
I need to debug two separate processes at once.
1. Program 1 writes records to a file
2. Program 2 is a PF Trigger on that file (triggered *after *insert)
I set service entry points for both. Called program 1 and stepped through just fine. However, program 2 never popped up into debug. I'm absolutely certain that records were being written to the file one-at-a-time. I'm also certain that the trigger program was firing (I could see the results immediately).
Can I not do this, or am I doing something wrong?
Greg
--
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
