Responding to my own append:

It appears that this is yet another "issue" with the AIX C compiler port--such a piece of crap.

If I compile the modules and bind using the V4 C compiler-- TGTRLS(V4R4M0)--I get properly merged copyright statements--exactly as I expected.

If I compile the modules and bind using the V5 C compiler-- TGTRLS(*CURRENT)--I get the duplicated copyright statements.

If I use the V4 modules and bind using TGTRLS(*CURRENT) I get properly merged copyright statements.

This suggests to me the problem is in how the V5 C compiler generates the copyright statements for some modules and the binder is just working with what it got.

Just another bloody annoyance in the V5 C compiler. At what point does a list of minor irritations become an aggravation?

Now I'll have to dump the modules and examine the .COPYRIGHT- section to see if I can spot what it's doing differently in some modules. What a pain in the arse!


On 28/08/2009, at 11:12 PM, Simon Coulter wrote:


Does anyone KNOW how the binder organises copyright statements in an
ILE program or service program? These are text strings embedded in the
compiled object using:
o COPYRIGHT TEXT('XYZ 2009') CL command
o #pragma comment(copyright, "XYZ 2009") C directive
o COPYRIGHT('XYZ 2009') RPG IV H-spec
o etc.

My problem is duplicate entries appearing in the copyright section of
the output from DSPPGM or DSPSRVPGM.

My observation is that the binder rationalises copyright statements
such that only one occurrence of a given copyright string should appear.

For example: If I have a program consisting of three modules A, B, and
C, and each module source contains the following:

H COPYRIGHT('(C) XYZ 2009')

then each resulting compiled module will show "(C) XYZ 2009" with
DSPMOD DETAIL(*COPYRIGHT). When these three modules are bound into a
*PGM object DSPPGM DETAIL(*COPYRIGHT) will show only one instance of
"(C) XYZ 2009".

If one module has a different copyright value then DSPPGM
DETAIL(*COPYRIGHT) will show only two strings e.g.:
"(C) XYZ 2009"
"(C) ABC 2000, 2004."

indicating that the duplicates have been merged.

If all three modules have different copyright values then DSPPGM
DETAIL(*COPYRIGHT) will show all three strings.

For this problem I have a *PGM object with 17 bound modules. 13 of
them have exactly the same copyright statement. 1 has no copyright
statement. The remaining three modules each have different copyright
statements.

I was expecting the *PGM object to have 4 copyright statements but I
get 5. The statement from the 13 modules is duplicated.

As part of my investigation I have built the *PGM object in stages by
specifying OPTION(*UNRSLVREF) which allows me to create a *PGM object
with only some of the modules even though all are need to actually run
the program. This shows that 4 of the 13 modules cause the
duplication. If the program is built using only these 4 modules there
is only one copyright statement in the resulting program. If I include
any of these 4 modules with any of the other 9 modules that share the
same copyright statement I get 2 duplicate copyright statements.

Reducing further if I include only the entry module and any one of the
4 problematic modules (i.e., a 2-module program) I get duplicate
copyright statements. If I include only the entry module and any or
all of the other 9 modules I get a single copyright statement.

Although this does not affect the operation of the program the
duplicate copyright statements look extremely ugly.

I KNOW the copyright statements in the 13 modules are IDENTICAL
because they come from the same common include.

So ... what's going on?

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------



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


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].