DSM/SCM Messages Manual
DSM/SCM EMS Messages
DSM/SCM Messages Manual—529845-006
5-101
5026
5026
sysnn-num
is the octal number of the currently executing SYS
nn
.
Cause. The Apply is not replacing the OSIMAGE in the target SYS
nn
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 SYS
nn
; then restart the activity.
•
Cancel this Apply; then start a new Apply request specifying a different target
SYS
nn
.
•
To force the Apply to the same SYS
nn
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, and the parameter is not case-sensitive.
DSM/SCM checks for the OVERRIDE Pathway parameters and matches their
values with the configuration revision being applied. If a match occurs, the Apply
continues to the specified SYS
nn
without replacing the OSIMAGE, and no system
load is required because the system continues running on the same OSIMAGE. If
the parameter is not detected, is incorrect, or does not indicate the configuration
revision being applied, the OSIMAGE might be replaced, or an error 5026 might be
issued.
DSM/SCM has detected that the OSIMAGE file is different from
the currently executing OSIMAGE file in SYSnn
sysnn-num
. 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.