|
Hello,
1. The ability, when using DBGVIEW(*SOURCE) to override the debugger and tell it where the source *really* is - this is a huge hassle if a source library has changed its name.
In today's environment, where we're constantly stepping from one program object into another program or srvice program object, it seems like there'd be much more than one member to specify.
Perhaps this feature woudl be better suited to the screen where it shows the list of modules (in green screen, the "F14 screen") rather than on the STRDBG command directly?
2. The ability to use DBGVIEW(*LIST) and include an *encrypted* copy of the source in the *PGM object. That way, you get the best of both worlds - the source stays with the object, but it's not available to the end user without a password.
Interesting idea. I'm surprised you haven't written a utility that does this yet, Rory!
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
