Service programs are incredibly versatile, but sometimes versatility makes it hard to get started.
By Joe Pluta
In my previous article, I explained why you would use a service program. Much of it centered on the ability to call the same logic using multiple paths. You simply create multiple procedures—I called them convenience procedures—that act as different entry points to the main business logic within your service program. They may provide default values for some arguments, or act as pre- and post-processors for the input and output values. The uses are varied, but you can probably see that you can end up with a lot of procedures. How then to manage the complexity?
