Re: STRISDB and displaying large variables

On 21/05/2008, at 8:36 AM, Walden H. Leverich wrote:

Before you can use the ILE debugger (STRDBG) on an OPM program, you must
first compile it with OPTION(*LSTDBG) or OPTION(*SRCDBG).

What he said! :)

We simply changed the compiler options to we don't even think about it
anymore. To us it's a matter of using the supported STRDBG vs the
(effectively) unsupported STRISDB.

What I want to know is WHY must I ALSO specify OPMSRC(*YES) on the STRDBG command.

Surely the default should be to use whatever debug visibility is present in the program. If I bothered to compile the OPM program with OPTION(*SRCDBG | *LSTDBG) then surely I WANT source level debug active when I attempt debugging?

In my not so humble opinion the STRDBG command should not even support OPMSRC keyword because it seems unnecessary. If source debug visibility is present just use it; if not then use the old way. However it MAY be useful to allow a developer to force the old behaviour therefore STRDBG should have OPMSRC(*PGM) as the default with *NO and *YES as allowable values. That way it would behave the way I (and I suspect most others) want it to.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------