Determining whether a module must be assembled

To determine whether a module must be assembled, SMP/E checks whether the DISTLIB subentry is SYSPUNCH. If so, the module does not reside in a distribution library; it must then be assembled from some other source before it is link-edited. SMP/E must, therefore, determine how to assemble the module:

If there is an ASSEM entry with the same name as the module, the statements in the ASSEM entry can be used to assemble the module.
If there is no ASSEM entry, SMP/E checks for an SRC entry with the same name as the module. If one exists, the source can be used to assemble the module.
If there are no ASSEM or SRC entries for the module, it cannot be assembled, nor can it be link-edited into any load modules.

If FORFMID was specified and the module being assembled does not have an FMID, it may still be eligible. If an ASSEM entry can be used to assemble the module, SMP/E checks whether that assembly uses macros owned by any of the specified FMIDs. If so, the module is included in the installation job stream. Otherwise, SMP/E assumes that the assembly is not needed for any of the selected FMIDs, and the module is not included in the installation job stream.

Note: To determine whether the ASSEM uses any selected macros, SMP/E checks all the MAC entries to see if any of them specify that ASSEM entry in the MAC GENASM list.

Because SYSPUNCH is used as a DISTLIB value for modules in the SMPOBJ data set, SMP/E also checks for a DD statement or DDDEF entry for SMPOBJ. This data set contains preassembled modules that can be used to avoid re-assembling the modules. If SMPOBJ is found, SMP/E checks whether it contains a member with the same name as the module that must be assembled. If so, the SMPOBJ version of the module can be used with no need to reassemble the module. Otherwise, the module must be assembled.