RE: Stray module in service program

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Hiebert, Chris
Sent: Wednesday, December 30, 2015 10:10 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: Stray module in service program

--BNDDIR(... *LIBL/PROVISION ...)
--BNDSRVPGM(... PROVISION)

Assuming PROVISION service program is the only thing in the PROVISION
binding directory, you shouldn't need to include both the binding
directory and the service program.

BNDSRVPGM
By binding the service program you are giving every module in your new
service program direct access to the bound service program. This Means
that they will use the last updated version of PROVISION service program
at runtime.

BNDDIR
By using the binding directory, you are telling the compiler that it
should lookup other references in the binding directory.

If the reference is a module reference, that module will be included at
compile time. Meaning your NEONOVAAPI will need to be updated every time a
change is made to the modules used.

If the reference is a service program reference, then it is the same thing
as using the BNDSRVPGM option on the compile.

Doing both can sometimes cause strange duplicate reference errors.

Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.