|
----- Original Message -----
From: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Subject: RE: Relating a statement number to a source line number
Date: Fri, 7 Dec 2007 11:47:53 -0600
I always add an Option(*SrcStmt:*NoDebugIO) to my H specs, so that
the compiler uses the source line ID instead of statement number.
Otherwise, if you have source, you could just compile the object to
qtemp and review the compiler listing to see the statement
numbers....
hth,
Eric
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Albert York
Sent: Friday, December 07, 2007 11:17 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Relating a statement number to a source line number
I am having trouble with an RPGLE program hanging up. When I look
at the job stack it shows me a statement number. How do I relate
that back to the source? With RPG you could generate a listing of
the generated program. Is there a way to do that with RPGLE?
Thanks,
Albert
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.