Re: Removing a procedure from a service program

Module or procedure?

You say "called the module", but modules are not callable.

The module a procedure is in has no effect the *SRVPGM signature, AFAIK.
Perhaps with a system generated sig, but with a user specified sig in the
binder source it won't.

From a stand point of never having to recompile the world, you are better

off never removing a procedure. There's a couple techniques to depreciate
a procedure so that it's not used going forward.

Charles


On Thu, Feb 20, 2014 at 2:22 PM, Koester, Michael <mkoester@xxxxxxxxxxxxx>wrote:

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.

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.

Thanks.
Michael Koester
Programmer/Analyst

DataEast


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.