RE: Maintaining Service Program signatures

Or, there have been many discussions here that are in the archives.
Just have a hard-coded signature that never changes. ALWAYS add new
procedures to the end of the binder source, NEVER insert between
existing ones.

Scott Mildenberger


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of sjl
Sent: Tuesday, February 19, 2013 1:44 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Maintaining Service Program signatures

Binding Source, with STRPGMEXP PGMLVL(*PRV) for previous versions ?

- sjl


"RPGLIST" wrote in message
news:mailman.16066.1361306316.10847.rpg400-l@xxxxxxxxxxxx...

Is there an easy way to avoid problems with signatures since we are
supposed to have the ability to add new modules to a service program
that will not require us to recompile all the objects that depend on
that service program.


--
This is the RPG programming on the IBM i (AS/400 and 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.