++MACUPD MCS

The ++MACUPD MCS describes a single macro update within a PTF, an APAR fix, or a USERMOD. It must immediately precede the macro update statements within the SYSMOD.

Operands

ASSEM

specifies the names of modules to be assembled in addition to those named as GENASM subentries in the MAC entry. The source for the assemblies is the ASSEM entry, SRC entry, or DISTSRC member whose name matches the specified ASSEM value. SMP/E looks for a match—first with an ASSEM entry, then with a SRC entry, and finally with an entry in the DISTSRC data set—and uses the first match it finds. The source must either be known to SMP/E at the time the ASSEM operand is encountered on the ++MACUPD statement, or be included in the same SYSMOD.

Note:

1. APPLY and ACCEPT processing place the specified names into the SYSMOD entry created on the target zone and distribution zone.
2. If the object deck for the element specified on the ASSEM operand is also provided by the SYSMOD, the assembly may not occur. For more information, see the sub-topic on assemblies in the APPLY command topic in SMP/E for z/OS Commands.

DISTLIB

specifies the ddname of the distribution library for the specified macro.

Note:

1. DISTLIB must be specified if the macro has not been previously recorded on the target zone or distribution zone. If a MAC entry already exists in the target zone or distribution zone, and the value currently in that entry does not match that specified in the DISTLIB operand, the SYSMOD is not applied or accepted.
2. You cannot use SYSPUNCH as the DISTLIB. It is used by SMP/E and other products to process assembled modules.

DISTMOD

specifies the ddname of the link-edit distribution library for the modules specified in the ASSEM operand. During ACCEPT processing, the object code from the assembler is link-edited to the library specified.

DISTSRC

specifies the ddname of the library containing the additional assembly or source to be assembled. The additional assembly or source must be specified in the ASSEM operand.

MALIAS

specifies the alias names for the macro in both the target system and distribution libraries.

You can use MALIAS when two or more macros that must be defined in the same zone must have the same name for programming access. For example, you can use MALIAS if several products have a help macro whose name must match the name of the command processing module it describes. You can specify HELP on MALIAS and a unique element name as the macro name.

name

specifies the name of the macro member in the distribution library and, optionally, in the target system library. The name can contain any alphanumeric characters and $, #, @, or hex C0.

PREFIX

specifies the first characters (prefix) of the names of modules to be assembled in addition to those modules named as GENASM subentries in the target zone MAC entry. The prefix values must be 7 characters or less.

The full module names are determined by comparing the prefix with the target zone or distribution zone MOD entry names.

The source for the assembly is the ASSEM entry, SRC entry, or DISTSRC member whose name matches a MOD entry name beginning with one of the specified prefixes. SMP/E looks for a match—first with an ASSEM entry, then with a SRC entry, and finally with an entry in the DISTSRC data set—and uses the first match it finds. The source must be either known to SMP/E at the time the PREFIX operand is encountered on the ++MACUPD statement, or be included in the same SYSMOD.

Note: If the object deck for the element specified on the PREFIX operand is also provided by the SYSMOD, the assembly may not occur. For more information, see the sub-topic on assemblies in the APPLY command topic in SMP/E for z/OS Commands.

SYSLIB

specifies the ddname of the target library, if the macro exists in one. APPLY and RESTORE processing update this library.

Usage notes

• If a SYSMOD containing a ++MACUPD statement attempts to change the ownership (FMID) of the element (with the VERSION operand), the SYSMOD cannot be installed.
• The changes for the macro must immediately follow the ++MACUPD MCS and must not contain any records that start with ++.
• If the macro resides in a target library (rather than the SMPMTS), that target library should be included in the SYSLIB DD concatenation for assemblies during APPLY processing. For additional information about SYSLIB requirements, see SMP/E for z/OS User's Guide and SMP/E for z/OS Commands.
• The only IEBUPDTE control statements allowed in a SYSMOD are ./ CHANGE and ./ ENDUP.
• The only IEBUPDTE CHANGE operand SMP/E checks is NAME, which must specify the same element as the ++MACUPD MCS. Other CHANGE operands may produce undesired results and are used at your own risk. For example, if you code UPDATE=INPLACE, SMP/E may update the distribution library. Once the distribution libraries are changed, there is no way to remove the updates.
• SMP/E does not support a continuation of the ./ CHANGE statement.
• SMP/E generates any ./ ALIAS statements needed and places them in the IEBUPDTE input data following the last text statement. The ./ ALIAS control statements are generated only for macro updates.
• When processing multiple updates to the same lines in a given macro, SMP/E uses the ./ CHANGE statement from the last update to the lines.
• If an APAR fix or USERMOD updates a macro that causes an assembly, SMP/E sets the ASSEMBLY indicator in the MOD entry for the assembled module. This can cause a problem when additional service that does not know about the macro change is installed at the same time as the APAR or USERMOD—for example, if you are installing your own USERMOD and IBM-supplied PTFs with the same APPLY command. In such cases, because the ASSEMBLY indicator is set, the module is reassembled, but does not contain the macro changes from the APAR or USERMOD. To prevent these assemblies, you can reset the ASSEMBLY indicator using UCLIN after installing the APAR or USERMOD.