I have a service program that contains 8 modules. One of those modules I want to replace with another of a different name - deprecating one and adding a new one that is similar but different enough to be named differently. The one program that called the module to be removed is being changed and recompiled (to use the new & improved one), so the old module would not really be missed.You can add new modules in UPDSRVPGM command. Create *BNDDIR object, add new modules to *BNDDIR, and run UPDSRVPGM BNDDIR(your-binding-directory). But you can not remove module from service program using UPDSRVPGM command, then you should run CRTSRVPGM.
Questions: 1) Would updating the service program (UPDSRVPGM) to add the new module cause signature violation issues? I have binder source, which would be updated, but some of the programs that call other modules of the service program were created before the binder source.
2) Is that old module forever part of the service program (and a source of confusion to everyone that follows me and wonders about this phantom module)?
3) Would I be better off recreating the service program (CRTSRVPGM) to permanently remove the old module?
Running 7.1, no TR 7 yet.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact