Re: Procedure Examples VR7.1

On 2/2/2017 9:25 AM, Duane Scott wrote:

I'm fairly understanding of how procedures work, but I've not been able to sit down with someone who uses it in a working environment. Can you elaborate on the "Bad, bad thing to do." (More specifically) what is it that is bad and why?

Bind by copy is a lot like using /copy to copy the code into each
program that uses it. When you make a change, you need to recompile /
rebind every program that uses the thing.

Bind by reference (service programs) mean that all the programs point to
one, single copy of the executable code. Change that one copy, and the
whole system follows at the same instant.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Wednesday, February 01, 2017 4:53 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: Re: Procedure Examples VR7.1

As you note, I use the Service program name. Obviously easy if you know the service program name to find the module it is in and usually a service program only has one member anyway and please never bind the same module to multiple programs or service programs. Bad, bad thing to do. Create service programs.

The way I like to do it is dead simple. Needs to be for me to keep it
straight in my head :-)

QRPGLESRC member CONVERSIONS
QPROTOSRC member CONVERSIONS (for /copying prototypes)
QSRVSRC member CONVERSIONS
CRTRPGMOD CONVERSIONS
CRTSRVPGM CONVERSIONS

One source member <-> one service program, and all the pieces have the
same name.