Per a private email, I looked into this a bit more. PTC Implementer does have an option on the System Control Maintenance (menu option 45), "Bypass Change Program Data API" that uses the QBNCHGPD API. It ships with a default value of 'N', which is to say that it *does* use the API. For reasons unknown to me, someone at my current shop changed it to 'Y'.
For those interested, search for QBNCHGPD in the Installation and Administration Guide and the User Guide. It advises that the only reason to bypass this is if system performance is severely impacted while promoting "a large number of ILE programs", which is probably not an issue for most shops.
- Dan
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dan Bale
Sent: Thursday, April 25, 2024 11:22 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: DBGVIEW(*ALL/*SOURCE) and STRDGB
PTC's Implementer change management has this problem, where compiled programs point to source in Implementer's temporary work libraries that get deleted after successful promotion. It is a PITA, but there are workarounds. IIRC, debug in RDi will prompt you for the source location if the source reference in the compiled object no longer exists. Also IIRC, it will let you select source from a partition that is not the same as the program object you are debugging.
- Dan
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Daniel Gross
Sent: Thursday, April 25, 2024 11:01 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: DBGVIEW(*ALL/*SOURCE) and STRDGB
Am 25.04.2024 um 12:56 schrieb Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>:
Have you tried to add DBGVIEW(*ALL) to the COMPILEOPT in the
CRTSQLRGI Command?
Yes - it includes the *LISTING View then - but the source reference points to the wrong library. The *SOURCE is NOT compiled into the object - only references to the external source file. So if the source file is moved - the references are wrong.
We found that our CMS (called CMOne) can take care of of that, and have configured it accordingly.
CMOne uses an system API called QBNCHGPD - with that API one can change the source reference of the bound module inside the *PGM or *SRVPGM. CMOne then uses an "translation table" to change the library references so the correct source can be found without recompiling the program.
Our QA does not like recompiling after a program is activated into production - but with that API we get around recompiling. So it's like eating AND having your cake at the same time.
Thanks for your help - the problem is solved.
*** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***
midrange.com
