Products sometimes contain modules from other products. For example,
a product may need to:
- Include another product's modules in its load modules.
In
this case, as long as the two products are in the same zone, SMP/E
can automatically include the required modules in the load modules
that need them (if the modules reside in the target library as single-CSECT
load modules). SMP/E also tracks the inclusion of these cross-product
modules in the load modules.
- Update another product's load module with one of its modules.
In
this case, as long as the two products are in the same zone, SMP/E
can automatically relink the load module and include the supplied
module. SMP/E also tracks the inclusion of the modules in the cross-product
load module.
When such products reside in different zones, however, SMP/E cannot
automatically perform the cross-zone link-edits. Instead, you can
use the LINK MODULE command to perform these cross-zone link-edits
as postinstallation steps within SMP/E control. The LINK MODULE command
causes the required load modules in one zone to be linked with modules
residing in another zone, and tracks this inclusion so subsequent
APPLY and RESTORE processing can automatically maintain the affected
load modules.
Note: - The zones used by the LINK MODULE command must be defined in the
same global zone.
- When SMP/E processes the LINK MODULE command, it assumes that
adding the desired modules to the load modules does not require any
changes to the load module definition (that is, the link-edit utility
control statements or link-edit utility attributes). If any such changes
are needed, make them through JCLIN before using the LINK MODULE command.
- There are times when the LINK MODULE command is not appropriate
to use—generally, for products written in a high-level language
and, as a result, include modules from libraries (such as compiler
libraries) owned by a different product. Your options for installing
such a product depend on how the product was packaged.
- SYSLIB DD statements are used in link-edit steps to implicitly
include the necessary modules.
In this case, when you install the
product, the implicitly-included modules are automatically linked
into the load modules.
If the libraries containing those modules are updated, you can
use the LINK LMODS command to rebuild the affected load modules. For
more information, see the The LINK LMODS command.
- No SYSLIB DD statements are used in link-edit steps in order to
implicitly include the necessary modules. In this case, you must use
postinstallation link-edit steps outside of SMP/E.