NonStop Operating System Event Management Programming Manual

Configuration Services Event Messages (ZDSC)
HP NonStop Operating System Event Management Programming Manual520372-020
24-29
Messages
Recovery. Use a FUP INFORMATION command to ensure that the configuration
database file currently in use is a key-sequenced file.
If the configuration database file is not key-sequenced, copy CONFSAVE to a file such
as CONFnnnn, where nnnn is a four-digit number indicating the configuration version
to be saved. Use this CONFnnnn file to load the system by specifying nn.nn as the
saved config version during system load.
If the configuration database file is a key-sequenced file and this error persists, see
Recovery Action Requiring Vendor Support on page 24-10.
1045: ZDSC-EVT-CONFIG-BAD-FCODE
The configuration file does not have the correct file code.
Unconditional Tokens
Cause. The filename specified in the event is a configuration database file, but it does
not have 837 as its filecode.
Effect. Since these events are usually concerned with processing of the configuration
database, they could lead to the specified configuration either not being opened or not
being copied to a temporary file. Both of these scenarios will eventually lead to a halt of
the processor in which the Configuration Database Manager ($ZCDB) process is
running.
Recovery. Change the file code of the configuration database to 837.
Potentially critical event: No
Action event: No
Message sender: $ZCDB
TMDS collector: No
OSM/TSM collector: Yes
Unconditional Tokens
ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT
ZDSC-TKN-FILENAME token-type ZSPI-TYP-STRING
Event-Message Text
Configuration file filename does not have the correct file
code.
Token Description
ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVT-
CONFIG-BAD-FCODE (1045).
ZDSC-TKN-FILENAME Name of the configuration file that does not have the
correct file code. Value is ZDSC-TNM-FILENAME.