×
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.
OK, I'm going to get dinged for this, but there's another reason to use STRISDB. STRDBG, the iSeries Graphical Debugger, and the WDSc debugger do not run against RPG II programs. There is a gotcha here, though. If it is an RPT36 source member (usually because of /COPY statements), even ISDB won't work against it. It is necessary to create and compile a surrogate program with the /copy stuff copied directly into the source and compiled as an RPG36 member. The only other option is to use the DEBUG op-code, and sometimes this is not enough; been there, done that.
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of sjl
Sent: Tuesday, May 20, 2008 5:14 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: STRISDB and displaying large variables
Alan -
Before you can use the ILE debugger (STRDBG) on an OPM program, you must
first compile it with OPTION(*LSTDBG) or OPTION(*SRCDBG).
- sjl
--
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.
midrange.com
