-----Original Message-----
From: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Date: Mon, 17 Dec 2007 11:20:57 -0600
Subject: RE: module/pgm analysis (lines of code)
Why not DSPPGMREF to an outfile......
Eric
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Jay Vaughn
Sent: Monday, December 17, 2007 11:03 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: module/pgm analysis (lines of code)
DSPPGM PGM(ROUTINES/ACCTDEL) DETAIL(*MODULE)
ahh man... only if that supported *outfile i would be in biz... is there a
command that will output referenced modules for a pgm into an outfile?
-----Original Message-----
From: rob@xxxxxxxxx
To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
Date: Mon, 17 Dec 2007 11:16:58 -0500
Subject: Re: module/pgm analysis (lines of code)
See APIs.
There are some Retrieve Program Information API's. Based on those you
should be able to ascertain what modules make up those programs. Where
those source members were (at compile time). Then use the Retrieve Member
Description API to find out how many lines of source were in that.
Should be comparable to
DSPPGM PGM(ROUTINES/ACCTDEL) DETAIL(*MODULE)
and
RTVMBRD FILE(ROUTINES/QRPGLESRC) MBR(ACCTDEL)
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: module/pgm analysis (lines of code), (continued)
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.