DSM/SCM Event Management Programming Manual

Event Messages
DSM/SCM Event Management Programming Manual—529844-003
5-207
5360 ZPHI-EVT-ZDLLRRRA-NOT-ACTIVE
ZPHI-TKN-FROM-SUBVOL-NAME
is the subvolume where the active set of public DLLs exist. An active set of public
DLLs is the set used at last system load.
ZPHI-TKN-FILE-NAME
is the name of the first active public DLL file found to be incorrect.
ZPHI-TKN-DSMSCM-TEXT
indicates why ZPHI-TKN-FILE-NAME was incorrect. The value is either missing or
different (expected fingerprint=%s, actual=%s)”.
ZPHI-TKN-TO-SUBVOL-NAME
is the ZDLLrrr[a] subvolume name template that DSM/SCM has searched.
DSM/SCM also searches subvolumes with this name and an appended alphabetic
character A through Z; for example, ZDLL005. DSM/SCM has searched all
subvolumes ZDLL005[a-z] for a correct set of public DLLs.
Cause. The new configuration is being applied to the running SYSnn subvolume, and
none of the existing set of public DLLs are correct. (When public DLL files are
compared, a Rebase/Rebind sensitive fingerprint type is used. Use the –RS option of
SWID when fingerprinting a public DLL file.) This message is not sent when the
OVERRIDE-SYSNN parameter has been specified.
Effect. DSM/SCM creates a new ZDLLrrr[a] TSV. The Apply completes with
warnings.
Recovery. You must perform a system load to activate the correct set of public DLLs.
5360 ZPHI-EVT-ZDLLRRRA-NOT-ACTIVE
The active set of public DLLs are not correct. Another correct set of public DLLs was
found on the system. The Planner Interface might not have indicated that a system
load is required. This message is not sent when the OVERRIDE-SYSNN parameter
has been specified.
Tokens
ZPHI-TKN-TO-SUBVOL-NAME <1> token-type ZSPI-TYP-DEVICE
ZPHI-TKN-FILE-NAME <2> token-type ZSPI-TYP-STRING
ZPHI-TKN-DSMSCM-TEXT <3> token-type ZSPI-TYP-STRING
ZPHI-TKN-SUBVOL-NAME <4> token-type ZSPI-TYP-DEVICE
Message Text
A coldload will be required to activate the public DLLs in
this new configuration because the active DLLs are not
correct. The active set of public DLLs in $SYSTEM.<1> is
incorrect because <2> is <3>. A correct set of public DLLs
were found in $SYSTEM.<4>.