Re: STRDBG problem -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: STRDBG problem
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Wed, 02 Jul 2008 12:10:10 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

Follow-Ups:

Re: STRDBG problem , Alan Shore

This mailing list archive is Copyright 1997-2026 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.