|
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Niels Liisberg
Sent: Friday, October 9, 2020 4:30 AM
To: Midrange Systems Technical Discussion <midrange-
l@xxxxxxxxxxxxxxxxxx>
Subject: Re: ILE program object's source infomation
Hello Peter,
Your observations sound crazy and at least inconsistent. And the only
explanation I can come up with is this:
If the creation of programs is done in two steps with CRTRPGMOD and the
CRTPGM like we do in our build chain.
However, if you use option 14 it will use the CRTBNDRPG - and maybe that
is the reason - but I am not sure.
On Thu, Oct 8, 2020 at 2:35 AM Peter Dow <petercdow@xxxxxxxxx> wrote:
Ever since ILE was introduced, the program's object-level sourceinformation is blank.
information has been blank for ILE programs, for the obvious reason
that an ILE program can be made up of multiple modules, each with it's
own source information.
Imagine my surprise when I happened to notice that using DSPPGM on
certain ILE programs started showing the source library, file and
member, but not the source member changed information.
Further surprise when I discovered that it did not match the module
source information, for these single-module ILE programs.
After checking several programs, it seems to have started after my
customer started using Implementer for change control. Is this a
"feature" of Implementer?
The reason I suspect Implementer is that the module's source
information shows the source library as something like IM3851S, and
the object-level source library is MODLPSRC. When I compile that
particular program using PDM option 14, the object-level source
pdow@xxxxxxxxxxxxxx
--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
<mailto:pdow@xxxxxxxxxxxxxx> /
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.