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

WVP NonStop Storage Analyzer User Guide – 536988-001
- 103 -
NSSTORA 114
<Program Name> <Function Name>: READUPDATEX error <Filename>:<Error Number>
Relating to function or activity: Reading from some process and replying to that process failed
Cause: The process with which communication was being attempted has expired. The EMS Event
indicates the error value returned by the Guardian Procedure call READUPDATEX
Effect: Any future I/O Operations with the deceased process will fail.
Recovery: The parent process should restart the child process that died prematurely.
NSSTORA 115
<Program Name> <Function Name>: REPLYX Error <Error Number>
Relating to function or activity: SAMGR process replying to a message it receives from the admin user
interface.
Cause: Occurs on the “REPLYX” Guardian procedure call. The Guardian error number indicating what
the cause was is part of the event text.
Effect: The user will not be alerted of the status of the updates made on the Admin screen, relating to
change in the daily run time and the trigger of the one-time loads.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 14 (device
non-existent) can be recovered from by ensuring that the processes (for SAMGR) are up and running.
NSSTORA 116
<Program Name> <Function Name>: Process waiting for a message<Filename>:<Error
Number>
Relating to function or activity: During Inter Process communication when the communicating process
dies prematurely.
Cause: The process with which communication was being attempted has expired. The EMS Event
indicates the error value returned by the Guardian Procedure call AWAITIOX
Effect: Any future I/O Operations with the deceased process will fail.
Recovery: The parent process should restart the child process that died prematurely.
NSSTORA 130
<Program Name> <Function Name>: Error opening $RECEIVE <Filename>:<Error Number>
Relating to function or activity Unable to open $RECEIVE for communication.
Cause: FILE_OPEN on $RECEIVE failed. This may be because of too many opens already on
$RECEIVE being specified.
Effect: The process will not be able to read from its $RECEIVE.
Recovery: Make sure that the maximum opens on $RECEIVE has not reached and also make sure
that every open on $RECEIVE is followed up with a corresponding FILE_CLOSE_ Guardian
Procedure call.
NSSTORA 140
<Program Name> <Function Name>: Error creating file <Filename>:<Error Number>
Relating to function or activity: Unable to create the given file.