Re: SrvPgm Procedure Prototype change - update program?

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Kurt

What messages are you getting - lots of possibilities, unfortunately.

I've used the second version successfully - default is *NONE for the 
BNDSRVPGM parameter. But there are matters of library and whether you 
are allowed to update the program and all that.

Let us know more, please.

Vern

Kurt Anderson wrote:
> I recently had to change a service program Prototype to use EXTPROC(*CL).  Without recompiling all of the programs that use this service program (and most of them use the procedure in question), is there a way to update the programs?
>
> I've never used the UPDPGM before, although I tried both of the commands below.  This didn't seem to have an impact.
> UPDPGM(MYPGM) MODULE(*NONE)
> UPDPGM(MYPGM) MODULE(*NONE) BNDSRVPGM(MYSRVPGM)
>
> If it matters, most of our programs were created using: CRTBNDRPG
>
> Another thought I had is to create a CL-only version of this procedure, but doing so goes against standard (in that this is an "Open...()" procedure for a service program).
>
> Any input would be great.  This is the bad part about "growing up" on a CMS and then suddenly not having one.  Although it's very rare that I change procedures, putting me into this situation (especially in such a widely used service program).
>
> Thanks,
>
> Kurt Anderson
> Sr. Programmer/Analyst
> CustomCall Data Systems
>
>
>