× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



 A colleague was testing the new CL enhancements and came across what
seems to be a bug in the debugger.

 Here's the test code:
             PGM        PARM(&QUALOBJ)
             DCL        VAR(&QUALOBJ) TYPE(*CHAR) LEN(20)
             DCL        VAR(&MAINOBJ) TYPE(*CHAR) LEN(20)
             DCL        VAR(&QUAL01) TYPE(*CHAR) STG(*DEFINED) +
                          LEN(10) DEFVAR(&QUALOBJ 1)
             DCL        VAR(&QUAL02) TYPE(*CHAR) STG(*DEFINED) +
                          LEN(10) DEFVAR(&QUALOBJ 11)

             CHGVAR     VAR(&MAINOBJ) VALUE(&QUALOBJ)
             SNDPGMMSG  MSG(&QUAL01) TOPGMQ(*PRV (*PGMBDY))
             SNDPGMMSG  MSG(&QUAL02) TOPGMQ(*PRV (*PGMBDY))

             ENDPGM

 CALL TEST PARM( '1234567890abcdefghij' )

 The messages generated contain the correct info:
1234567890
abcdefghij

 Doing the same CALL, step through via debug.
 Both &QUAL01 and &QUAL02 will show 1234567890 throughout the entire run.

 This happens in both the green screen and WDSC.

 Program is compiled with no optimization.  Is this a debugger bug?

 -mark

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.