DSM/SCM Event Management Programming Manual

Event Messages
DSM/SCM Event Management Programming Manual—529844-003
5-158
5026 ZPHI-EVT-OVRIDE-PRM-PASSED
5026 ZPHI-EVT-OVRIDE-PRM-PASSED
The Apply could not finish because the specified SYSnn subvolume could not be
replaced.
ZPHI-TKN-SYS-NN-NBR
is the octal number of the currently executing SYSnn subvolume.
Cause. The Apply is not replacing the OSIMAGE in the target SYSnn subvolume
because it is currently executing. You probably passed the OVERRIDE-SYSNN
parameter incorrectly, or its parameter value does not match the expected value.
Effect. The Apply stops in a restartable state.
Recovery. You have three alternatives:
•
Perform a system load from a different SYSnn subvolume; then restart the activity.
•
Cancel this Apply; then start a new Apply specifying a different target SYSnn
subvolume.
•
To forcibly apply to the same SYSnn subvolume and ignore the new OSIMAGE
that is being made, pass two Pathway parameters to the target activator (TA):
PATHCOM $YPHI
=Alter TA-001, param OVERRIDE-SYSNN "logical-target-
nameRevision"
=Alter TA-001, param OVERRIDE-SYSNN-DIFFERENT-OS "logical-
target-nameRevision"
For example, for the logical target default with configuration revision number 19,
logical-target-nameRevision is default19. There is no space between
the configuration name and number. The parameter is not case-sensitive.
Tokens
ZPHI-TKN-SYS-NN-NBR <1> token-type ZSPI-TYP-STRING
Message Text
DSM/SCM has detected that the OSIMAGE file is different from
the currently executing OSIMAGE file in SYSnn <1>. If you
know that the new OSIMAGE file is really the same as the
‘currently executing’ OSIMAGE file, you can force the APPLY
to adopt the ‘currently executing’ OSIMAGE by specifying
OVERRIDE Pathway params and RESTART the APPLY. Otherwise,
either coldload from a different SYSnn and RESTART this
activity, or CANCEL this activity and START a new APPLY
specifying a different target SYSnn.