|
Keith, If you're on a box on your system, you can create a DDM file on the production box. For instance, if the source for program MYPGM (on the production box PRDAS400) is in member MYPGM in file SOURCE/QRPGLESRC on the development box DEVAS400, you can do the following on PRDAS400: 1. CRTLIB LIB(SOURCE) 2. CRTDDMF FILE(SOURCE/QRPGLESRC) RMTFILE(SOURCE/QRPGLESRC) RMTLOCNAME(DEVAS400) In theory, you can then use STRDBG on program MYPGM on PRDAS400 and it will retrieve the source member for the debug session via the DDM file. In practice I've had varied success with this - it's a bit flaky and somewhat slower than if the source member is actually on PRDAS400. About 50% of the time it says it can't find the source member and the joblog shows random error messages (usually to do with the DDM connection). When it works, however, it's a lifesaver. Rory On 1/10/07, Keith Carpenter <carpcon@xxxxxxx> wrote:
<snip> Would be nice the debugger code access the source from a remote or (support) client system. Could be useful for more typical multisystem environments where production does not have source. Keith
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.