Re: RPG Service Program vs Include Source for Shared Subprocedures and SQL Calls

Richard said:

In the past I've leaned towards copybooks, but I'm curious what others think.

I'm solidly in the *SRVPGM camp.
When a customer has developers with pre-ILE skills, it's an
opportunity to introduce them to how easy it is to use a *SRVPGM.

I'm a little cautious of burying SQL functionality into one or more service programs.

Virtually all of our service programs use embedded SQL. I haven't
found that more problematic than F-specs.
With so many edge case shops, it's unfair of me to generalise so I
have to ask: have you encountered a situation where SQL in a service
program has been an issue?

--buck