Re: calling a program v using a SRVPGM

Yeah, I get the slow learning part. Don't we all?  Anyway, if you want an overview on using service programs, this is a pretty good one:

https://www.go4as400.com/chapterload.aspx?cid=401

It's pretty high level, and Amit sometimes jumps around a little, but it's a really good introduction to the topic.  When you start talking about service programs, you really need to understand static and dynamic binding, and the difference between modules, programs and service programs.  Amit covers all of this pretty well.

Technically you don't need a binding directory, you can use the BNDSRVPGM keyword on CRTPGM, but that requires a two-step process (compile ProgA into a module, then execute CRTPGM to make a program).  Personally, I much prefer using a binding directory and the BNDDIR keyword in my CTL-OPT spec.

Have fun!



On 12/30/2018 11:38 PM, Booth Martin wrote:

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!