Re: Easiest way, in a CL pgm, to find out what source member a program was compiled from?

Luis

DSPOBJD works for some things, including OPM programs, but not ILE
programs, because those are not directly based on source, as OPM are. In
fact, it's the module that would have the source information.

So the program information APIs do a better job, because DSPPGM doesn't
have an output file option.

Vern

On 3/31/2011 3:23 PM, Luis Rodriguez wrote:

James,

Would this help?

DSPOBJD OBJ(MyLib/*ALL)
OBJTYPE(*PGM)
DETAIL(*SERVICE)
OUTPUT(*OUTFILE)
OUTFILE(QTEMP/LIST)

Some fields of interest would be:

ODLBNM - Lib Name
ODOBNM - Object Name
ODOBTP - Object Type
ODOBAT -. Attribute (eg. CLP)

ODSRCF Source file name
ODSRCL Source file lib
ODSRCM Source file member

HTH,


Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Thu, Mar 31, 2011 at 3:33 PM, James Lampert<jamesl@xxxxxxxxxxxxxxxxx
wrote:

Anybody know, off-hand, an easy way for a CL program to find out what
source member a program (or the main entry-point module of a
multi-module program) was compiled from?

The idea is to go through a list of programs, and refresh them.

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