DSM/SCM Event Management Programming Manual

Event Messages
DSM/SCM Event Management Programming Manual—529844-003
5-160
5028 ZPHI-EVT-CANNOT-OVERRIDE-EOF
5028 ZPHI-EVT-CANNOT-OVERRIDE-EOF
An Apply request detected that the old and new OSIMAGE files are different versions.
The OVERRIDE-SYSNN-DIFFERENT-OS parameter is required for processing to
continue.
ZPHI-TKN-SYS-NN-NBR
is the octal number of the currently executing SYSnn subvolume.
Cause. An Apply detected that the old and new OSIMAGE files are different versions,
and the OVERRIDE-SYSNN-DIFFERENT-OS parameter was not specified to ignore
the difference.
Effect. The Apply request stops restartable.
Recovery. You have three alternatives:
•
Perform a system load from a different SYSnn subvolume and then restart the
Apply.
•
Cancel the Apply and then start a new Apply request specifying a different target
SYSnn subvolume.
•
Force an Apply to the same SYSnn subvolume and ignore the new OSIMAGE;
then specify this OVERRIDE Pathway parameter to the Target Activator (TA):
PATHCOM $YPHI
> ALTER TA-001, param "OVERRIDE-SYSNN-DIFFERENT-OS" "logical-
target-nameRevision"
For example, for the logical target named default with configuration revision
number 19, logical-target-nameRevision is default19. There is no space
between the configuration name and number, and 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 new OSIMAGE file is different
from the currently executing OSIMAGE in SYSnn <1>. The
OVERRIDE-SYSNN param has been specified to allow the APPLY to
go to SYSnn <1> anyway. However, the current OSIMAGE and new
OSIMAGE file are different sizes. If you are sure the two
OSIMAGE files are the same version, specify the OVERRIDE-
SYSNN-DIFFERENT-OS param and restart the request. Otherwise,
either coldload from a different SYSnn and RESTART the
activity, or CANCEL this activity and START a new APPLY
specifying a different target SYSnn.