HP Integrity NonStop H-Series - Manual (Page 102)

WVP NonStop Storage Analyzer User Guide – 536988-001
- 102 -
Recovery: Recovery will depend on the specific Guardian error returned. Make sure that the file exists
before being opened. If the max numbers of File Opens have been reached, then close all open file
handles and then try again.
NSSTORA 110
<Program Name> <Function Name>: Pair Info Error <Error Number>
Relating to function or activity: SAMGR attempting to communicate with the primary.
Cause: Occurs on the “PROCESS_GETPAIRINFO_” Guardian procedure call. The Guardian error
number indicating what the cause was is part of the event text. This could occur due to various
reasons, for e.g. non-existent process (Error 9).
Effect: The backup process will not be able to communicate with the primary. This will prevent the
backup process to take over as the primary in case the primary process goes down.
Recovery: Recovery will depend on the specific Guardian error returned. E.g. Error 9 can be
recovered from by restarting the Web ViewPoint (and hence Storage Analyzer) processes.
NSSTORA 111
<Program Name> <Function Name>: Error reading from an opened process
<Filename>:<Error Number>
Relating to function or activity: Unable to read from the opened process. The process may no longer
be running.
Cause: The Guardian Procedure call READX failed to return information from a process. The process
may not be running or an invalid buffer is specified in the READX Guardian Call. The EMS Event
indicates the value returned by the procedure call. Please refer to the Guardian Procedure Manual for
the description of the value returned by READX.
Effect: The READ Operation on the opened process fails. If the process is not running, then
subsequent calls to the process will fail too.
Recovery: Recovery will depend on the specific Guardian error returned. If the process is not running,
then make sure it is running again before trying the operation again.
NSSTORA 112
<Program Name> <Function Name>: Error writing to an opened process <Filename>:<Error
Number>
Relating to function or activity: Unable to write to a given process. The process may no longer be
running or an invalid buffer is being specified in the WRITEX call
Cause: The Guardian Procedure call WRITEX failed to complete a write to the process. The process
may not be running or an invalid buffer or count is specified in the WRITEX Guardian Call. The EMS
Event indicates the value returned by the procedure call. Please refer to the Guardian Procedure
Manual for the description of the value returned by WRITEX.
Effect: The WRITE Operation on the opened process fails. If the process is not running, then
subsequent calls to the process will fail too.
Recovery: Recovery will depend on the specific Guardian error returned. If the process is not running,
then make sure it is running again before trying the operation again.