Bill,
After you mentioned that a light bulb went off from my old S/3 or /34 days. We used to create simple reports using the report features, saved the generated source and worked it from there. I never could get the CRTS36RPT command to save the source, though. At least now where I thought I was directing it (OUTFILE=JERRY/QS36SRC, OUTMBR=PGMA). Fortunately the RPG II manual covers the auto report function. On the U-spec I could key 'UCJERRY,PGMA' and it did save it in the source PF QS36SRC from which, as you said, ISDB ran fine against it.
Thanks. The tip, reminder is going to save me a lot of time in the future. Personally, I'd rather just covert them all to RPG IV and be done with it. Unfortunately (or fortunately) there's real work to be done.
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 Bill Burnet
Sent: Wednesday, May 21, 2008 7:30 AM
To: Midrange Systems Technical Discussion
Subject: RE: STRISDB and displaying large variables
Jerry,
In the compile options on RPGII and RPGIII RPT programs there is an
option to save the generated source (OUTFILE/OUTMBR). If you save the
source you can use that as the source on the STRISDB to debug the
program without having to create your own with the /copy included.
-----Original Message-----
From: Jerry Adams [mailto:Jerry@xxxxxxxxxxxxxxx]
Sent: Wednesday, May 21, 2008 7:14 AM
To: Midrange Systems Technical Discussion
Subject: RE: STRISDB and displaying large variables
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.
--
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.
--
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
