Appendix a, 1-1 software support, 1-2 error & advisory messages (ems events) – HP Integrity NonStop H-Series User Manual
Page 79: 5 appendix a
Appendix A
WVP Event Analyzer Plug-in User Guide V01 – 536989-001
- 79 -
5 Appendix
A
5-1-1 Software Support
Support for Event Analyzer Plug-in is available through HP's 24-hour Global Mission Critical Support
Centers (GMCSC) throughout the world. In the U.S. please call 1-800-255-5010. International
numbers plea
5-1-2 Error & Advisory Messages (EMS Events)
This section lists all EMS Events that can be generated specifically from the Event Analyzer
application conditions and processing.
Event Analyzer EMS SSID: TANDEM.289 or TANDEM.NSEVNTA
(Note: The proper EMS template must be installed to implement the symbolic SSID subsystem name
for Event Analyzer. The default ID will be 289. The instructions for installing the Event Analyzer EMS
template are described in
Possible Critical EMS Messages
NSEVNTA 101
<Program Name> <Function Name>: Error Opening <Filename>:<Error>
Relating to function or activity: Opening a file.
Cause: Occurs on the “FILE_OPEN_” Guardian procedure call. The Guardian error number indicating
what the cause was is part of the event text. Could occur due to various reasons, including non-
existent file (Error 11), etc.
Effect: If the error occurs on the collector program, the daily database updates or the one-time loads
will not be completed. If the error occurs on the UI, the screen or data requested will not be displayed.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 11 can be
recovered from by ensuring the file exists in its proper location or that the program is pointing to the
right volume.
NSEVNTA 102
<Program Name> <Function Name>: Error Setting Key for file <Filename>:<Error>
Relating to function or activity: Positioning the file pointer within a key-sequenced file (database file) to
access contents.
Cause: Occurs on the “FILE_SETKEY_” Guardian procedure call. The Guardian error number
indicating what the cause was is part of the event text. Could occur due to various reasons, for e.g.
non-existent record (Error 11).
Effect: If the error occurs on the collector program, the daily database updates or the one-time loads
will not be completed. If the error occurs on the UI, the screen or data requested will not be displayed.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 11 can be
recovered from by restoring the file in question to its original form, using a backup for e.g.