ASAP 3.2 Messages Manual

HP NonStop Messages Manual Page 271 of 414
2009: ZASP-EVT-BAD-ENFSV-TRANS-CODE
ENFSV trans code bad
Cause. An incomprehensible input request was received.
Effect. The Collect server cannot behave as an Enform server because it cannot
understand the request.
Recovery. Check your Enform request and retry it. If the problem persists, contact
your HP support representative and provide all relevant information:
Descriptions of the problem and accompanying symptoms
Details from the messages generated
System number
Numbers and versions of all related products
Supporting documentation such as Event Management Service (EMS) logs, trace files,
and a CPU dump, if applicable
Data Tokens.
ZEMS-TKN-TEXT contains the message text.
ZASP-TKN-ASAP-ERRORNUM is ―2009‖.
2010: ZASP-EVT-COL-STARTUP-ERROR
Startup msg parse error: charoffset
charoffset
is the offset of the message that was not recognized.
Cause. An invalid parameter was detected while ASAP was attempting to read its
startup message.
Effect. The system does not start.
Recovery. Correct the startup message in your configuration file.
Data Tokens.
ZEMS-TKN-TEXT contains the message text.
ZASP-TKN-ASAP-ERRORNUM is ―2010‖.
2011: ZASP-EVT-COL-OPEN-TERM-ERROR
Startup Can’t Open TERM