Re: Module Library not being updated after UPDPGM

["Glenn Gundermann" <ggundermann@xxxxxx>]

Thank you for the reply Mark  :-)

> Hi, Glenn:
>
> Right or wrong, that's how it has always worked, and it is documented --
> just prompt the UPDPGM or UPDSRVPGM command and press F1=Help in the
> MODULE parameter field. It says:
>
>     If the library of the module being replaced is different from the
>     library of the replacing module, the module's library after the
>     update will remain the library the module was in when the program
>     was first created.  If the RPLLIB parameter is required to determine
>     which module to replace, the value to be entered in the RPLLIB
>     parameter for this module will not change due to the
>     update.
>
> Far more serious, in my opinion, is the fact that, once you have used
> UPDPGM or UPDSRVPGM, the DSPPGMREF command will not always show correct
> information for the *PGM or *SRVPGM.
>
> You could use CRTPGM or CRTSRVPGM to recreate *PGMs and *SRVPGMs from
> their component *MODULEs, and then you will never have the problem you
> mentioned, and DSPPGMREF will always show the correct information.
> (This assumes you do not delete *MODULEs after binding them into *PGMs
> or *SRVPGMs.)
>
> Cheers,
>
> Mark S. Waterbury