Re: Service programs compiled incorrectly

[Buck <kc2hiz@xxxxxxxxx>]

>      It looks like I bit myself in the b__t again with the activation 
> group.   In one test, I changed the activation group from *CALLER to 
> QILE on the program using the service program procedures and it worked.

If you find it difficult to re-create service programs, consider writing 
a script to do it for you.  I use CL, but ReXX or RPG works great too. 
Create the service program by hand, and when you get it working 
properly, copy/paste the create command(s) into your script.  Put a 
comment in one or all of the service program modules to CALL MYSRVPGMCRT 
to recreate the service program.

In my own case, my service programs tend to be quite simple, running in 
*CALLER.  All I have to do is CRTRPGMOD and UPDSRVPGM.  My programs all 
run in a single named activation group, so my service programs (*caller) 
never run in the default AG.

Others have a different strategy that works for them; there's no single 
'right' answer.  One popular standard is that the menu programs use *NEW 
and everything else is *CALLER.

This issue of re-creating service programs and their dependent programs 
is one of the very nice things that change management software brings to 
the table.  Automation is good :-)  Manual steps are bad :-(
  --buck