Re: calling a program v using a SRVPGM

Yes it does help.  Thank you.  I was misunderstanding what is a binding directory.  I was equating binding directory to directory, then directory to library, and concluding  that a library was not what I needed.

So Monday will be  "Learn about Binding Directories Day."

(And yes, there is a lot of terminology mismatch.  I learn slow.)


On 12/30/2018 11:27 PM, Joe Pluta wrote:

There's a little bit of terminology mismatch, Booth, because you don't just combine programs into a service program.  Each of the programs is now a procedure within the service program.  One may indeed be called pgmB, but it's no longer a program, it's a procedure.  If you left the name of the procedure to be pgmB, then you would use EXTPROC(pgmB) on your prototype; note the keyword EXTPROC, not EXTPGM.  Then in order to bring that service program into ProgA, you would create a binding directory with SRVPGM01 in it, and use that binding directory in the CTL-OPT specification. Say you called the binding directory BNDDIR01, then you add BNDDIR('BNDDIR01') in your CTL-OPT specification.

Hope that helps!