RE: Stray module in service program

Here is my suggestion:
Create the TSFORDERS service program.
Create the TSFORDERS binding directory with *only* the TSFORDERS *SVRPGM entry

ADDBNDDIRE BNDDIR(LIBNAM/TSFORDERS) OBJ((*LIBL/TSFORDERS *SRVPGM))

If any module that is in NEONOVAAPI service program needs an exported function from TSFORDERS, then include TSFORDERS on the create command for the NEONOVAAPI service program.
CRTSRVPGM SRVPGM(libnam/NEONOVAAPI) MODULE(...)BNDSRVPGM(TSFORDERS)

When you add the modules directly to the binding directory you are side stepping the service program.

I generally don't add modules to binding directories because I want to control access via the service program.

This is my understanding of binding directories, please correct me if you know otherwise.
But when you put modules into the binding directories, they are included with the compiled object.
When you put service programs into binding directories they are just referenced by the compiled object.


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.