|
- If the element entry in your target zone has an RMID value different
from its FMID value, ensure it is a prerequisite of the USERMOD fix;
that is, make sure the bbbbbbb value shown in the example
is accurate. If the RMID and FMID values are equal, the bbbbbbb value
need not be specified.
- If the element entry in your target zone has any UMID values,
you should first check to make sure the USERMOD itself was constructed
so it works correctly in that environment. You should then make sure
each of the UMID values is specified in the PRE operand in place of
the ccccccc values shown in the example. This is not an absolute
requirement, but if it is omitted, SMP/E issues warning messages during
installation identifying that these SYSMODs may have an intersection
with the one you are installing and, therefore, may be regressed.
Putting the UMID values in the PRE list suppresses these messages.
- If you do not specify the requisites that previously replaced
an element, SMP/E does not allow your USERMODs to be installed unless
you specify BYPASS(ID) on the APPLY or ACCEPT commands.
- If you want this SYSMOD installed without any warning or error
messages, you must specify all the current UMID values of each element
in the SYSMOD in the PRE operand. This indicates to SMP/E that the
SYSMOD was designed to be installed on the current function and service
level of the element, including update level.
If you do not specify
the requisites that previously updated an element, the following occurs:
- If your SYSMOD contains an element replacement, SMP/E does not
allow the SYSMOD to be installed unless BYPASS(ID) is specified on
the APPLY and ACCEPT command.
- If your SYSMOD contained an element update, SMP/E allows the SYSMOD
to be installed, but issues a warning message for each requisite not
specified in the PRE list.
This means SMP/E is unable to determine if there is an intersection
between your update and those already on the element. It assumes that
there is none, and you should investigate both updates to verify this.
|