× 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.


  1.  Home
  2. RPG400-L
  3. December 2007

RE: Relating a statement number to a source line number

If you have the default of DBGVIEW *STMT - then the listing will have
the statement numbers. Like others have mentioned - add a H spec that
sets the compiles to use *SRCSTMT and you won't have that problem going
forward. We use a /copy to the following to set options. Combined with
some /define's we can set our activation groups and other common
settings:

H bnddir('YOURBINDDIR':'QC2LE')
H copyright('Your copyright here)
H debug option(*srcstmt:*nodebugio)
/if defined(#CALLER)
H dftactgrp(*no)
H actgrp(*CALLER)
/elseif defined(#new)
H dftactgrp(*no)
H actgrp(*new)
/elseif defined(#service)
H Nomain
/else
H dftactgrp(*no)
H actgrp('QILE')
/endif

-----Original Message-----
From: rpg400-l-bounces+kevin=medtronsoftware.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+kevin=medtronsoftware.com@xxxxxxxxxxxx] On
Behalf
Of Albert York
Sent: Friday, December 07, 2007 12:26 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Relating a statement number to a source line number

I'm sorry. I meant the generated MI program listing which contains the
statement numbers (not the source line numbers) shown in the program
stack.

Albert

----- 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 12:11:26 -0600


LOL, now you've got me all confused.....

WRKSPLF to view the compiler output. Your compile command should
include the OUTPUT(*PRINT) option so that the compile listing is
produced. If this is not what you are asking, then please try
again. <g>

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:59 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Relating a statement number to a source line number


How do I get the compiler listing?

Thanks,

Albetr

----- 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.




--
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.




--
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 thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.