Re: STRDBG problem

Thanks for the info David, and I have passed this e-mail onto our system
guys, but there is one thing that bothers me.
My original request was to be able to use STRDBG against CLP and RPGIII
programs. The last sentence of what you cut and pasted , "Specifying
OPTIMIZE(*FULL) for OPM programs has no effect; a diagnostic message will
be signaled." will probably mean this is NOT a way around my problem
Thanks anyway



Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxxxxx
P:(631) 244-2000 ext. 5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

midrange-l-bounces@xxxxxxxxxxxx wrote on 07/02/2008 01:10:10 PM:

Shannon ODonnell wrote:

Yeah...but STRDBG CAN! Change production data. All you have to do is

use

the command EVAL PGMVAR = NEWVALUE while the program is running

under

debug and you've changed the value of the variable.

I'm not 100% sure about this ... but if you optimize a program to level
30 or higher, you can view variable contents but *NOT* change them.

From the CHGPGM command help ...

*FULL or 30
More optimization is performed in addition to those performed at
optimization level 20 (*BASIC). Variables cannot be changed but can
be displayed while the program is being debugged. However, the
displayed value of the variable during debugging may not be its
actual value. Specifying OPTIMIZE(*FULL) for OPM programs has no
effect; a diagnostic message will be signaled.

david


--
IBM System i - For when you can't afford to be out of business

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.