The RECEIVE command tells SMP/E to take the HOLDDATA from the input
data set on which it was delivered and store it in the SMP/E database.
The two operands that control input processes are:
- SYSMOD, which tells SMP/E to process the SYSMODs from the
data set specified by the SMPPTFIN DD statement
- HOLDDATA, which tells SMP/E to process the HOLDDATA (++HOLD
and ++RELEASE statements) from the data set or file in a UNIX file system specified by the SMPHOLD DD
statement
You can specify one or both operands on the RECEIVE command. If
neither operand is specified, SMP/E attempts to receive the SYSMODs
from SMPPTFIN, and HOLDDATA from SMPHOLD.
When receiving a SYSMOD, SMP/E creates two entries:
- An MCS entry is created on the SMPPTS. This
entry is a copy (possibly compacted) of the SYSMOD as it appeared
in the SMPPTFIN data set.
- A SYSMOD entry is created in the global zone. This entry contains
information that describes the installation requirements and element
content of the SYSMOD.
When receiving the HOLDDATA, SMP/E also creates (or modifies) two
entries:
- A HOLDDATA entry is created
(or modified) in the global zone. This entry is an exact copy of the
++HOLD statements as they appeared in SMPHOLD. The name of the entry
is the ID of the SYSMOD affected by this ++HOLD statement. The HOLDDATA
entry for a single SYSMOD can contain multiple ++HOLD statements.
Note: When a ++RELEASE statement is processed, SMP/E removes the
corresponding ++HOLD statement from the HOLDDATA entry. When all ++HOLD
statements are removed, the HOLDDATA entry is automatically deleted.
- A SYSMOD entry is created (or modified) in the global zone. This
entry contains information that describes the exception SYSMOD conditions.
For each ++HOLD statement processed, SMP/E updates the global
zone SYSMOD entry to add a HOLD reason ID subentry. There are three
types of HOLD reason ID subentries, HOLDERROR, HOLDSYSTEM, and HOLDUSER,
corresponding to the three categories of exception SYSMODs.
Note: When
a ++RELEASE statement is processed, SMP/E removes the corresponding
reason ID from the global zone SYSMOD entry. Do not use the ++RELEASE
statement to install a SYSMOD with an unresolved reason ID. Use the
appropriate BYPASS operand instead.