Re: More Service Program Issues

[Joel Cochran <jrc@xxxxxxxxxx>]

Troy,

>         was just referring to Joel Cochran's article, Binder Source: The 
> Little Language That Could.
> 
> 
> Now you have to create the service program again. There is no way around 
> this step. You must run the CRTSRVPGM command over the new binder source 
> and include PROC4 in the module list. 
> 
> 
> 
> I thought the UPDSRVPGM command was the 'way around this step'.
> Is it?

UPDSRVPGM will update an existing service program object.  Updating
means, among other things, that it will replace a current *MODULE object
with a different *MODULE object (of the same name).  What UPDSRVPGM
doesn't do is add a NEW *MODULE to the bound *SRVPGM object.  That is
why you have to recreate the service program.  Now, if you are adding a
procedure inside a pre-existing module, then UPDSRVPGM can be used.

> Also, I can't seem to recreate the service program without first removing 
> the entry from the Binding Directory.
> Is this normal? 

Yes: I don't have an exact answer, but it has to do with the SRVPGM
already existing in the binding directory you are referencing (via
H-Spec) on the CRTSRVPGM command, and so it is trying to bind it more
than once or something like that.  I think I've seen some of Bob Cozzi's
postings where he is able to avoid that using /IF DEFINED.../ENDIF
compiler instructions, but I honestly don't know how to use them.  

It's an annoyance, but I do it so infrequently anymore that it isn't
really that big of a deal.  When I started I had a separate module for
each procedure, but I'm feeling MUCH better now...


Joel Cochran
http://www.rpgnext.com