|
- 00
- APPLY processing completed successfully.
- 04
- APPLY processing completed, but one or more warning messages have
been issued. Processing did not stop for any SYSMODs. The user needs
to determine whether the warnings issued really identify an error
that needs to be addressed by some corrective action. These are some
possible situations that can cause a warning message to be issued
during APPLY processing:
- 08
- APPLY processing completed, but processing errors occurred. Processing
stopped for at least one SYSMOD. These are some possible errors:
- APPLY called a system utility program to perform some work, but
the utility program issued a nonzero and unacceptable return code.
Calls to one of the following utility programs could generate this
return code:
- Assembler (default: ASMBLR)
- Copy, compress, retry utility (default: IEBCOPY)
- Update utility (default: IEBUPDTE)
- Superzap utility (default: IMASPZAP)
- Linkage editor (default: IEWL or IEWBLINK)
SMP/E sets the APPLY and ERROR status indicators in the
affected target zone SYSMOD entries.
- A SYSMOD was held for an error reason ID that was not resolved.
Check the Causer SYSMOD Summary report and, if necessary, error messages
in the SMPOUT output to determine the cause of the problem.
- SMP/E encountered an error while scanning superzap control statements.
Check SMPOUT output for error messages to determine the cause of the
problem.
SMP/E sets the APPLY and ERROR status indicators in the
affected target zone SYSMOD entries. However, the module was not updated
unless an EXPAND linkage editor control statement was included in
the modification. In this case, the module was link-edited to expand
its size and the load module was replaced in the target library.
- A superzap VERIFY REJECT was encountered by the superzap. Check
SYSPRINT output for error messages to determine the cause of the problem.
SMP/E sets the APPLY and ERROR status indicators in the affected
target zone SYSMOD entries. However, the module was not updated unless
an EXPAND linkage editor control statement was included in the modification.
In this case, the module was link-edited to expand the size, and the
load module was replaced in the target library.
- A DD statement required by SMP/E was missing. APPLY did not process
any SYSMOD that required the missing DD statement.
- The target zone entry for a SYSMOD specified on the SELECT operand
indicates that the SYSMOD was superseded by another SYSMOD.
- A TXLIB or LKLIB member cannot be found. SMP/E sets the APPLY
and ERROR status indicators in the affected target zone SYSMOD entries.
- A SYSMOD specified in the SELECT operand list was not found on
the SMPPTS.
- The PEMAX value being used was too small to process one or more
SYSMOD entries or selected element entries being modified. If PEMAX
was too small for the element entries, SMP/E may have set the APPLY
and ERROR status indicators in the affected target zone SYSMOD entries.
Check SMPOUT output for error messages to determine which SYSMODs
or elements were affected.
- SMP/E could not open a target or distribution library. SMP/E may
have set the APPLY and ERROR status indicators in the affected target
zone SYSMOD entries.
- A SYSMOD containing an element update (++MACUPD, ++SRCUPD, or
++ZAP) attempted to change the ownership of the element with the ++VER
VERSION operand. The ownership can be changed only if the SYSMOD provides
a replacement for the element.
- 12
- APPLY processing stopped. These are some possible errors:
- A function SYSMOD was selected for processing. However, processing
stopped for the function before any target libraries were updated.
- No SYSMODs met APPLY specifications.
- GETMAIN failed during APPLY processing.
- SMP/E could not open or close a data set.
- The APPLY command contained a syntax error.
- A DD statement required by SMP/E was missing.
- A previous command issued an unacceptable return code.
- 16
- A severe error caused SMP/E processing to stop. These are some
possible errors:
|