HP Integrity NonStop J-Series - Manual (Page 24)

WVPASAP 113
: WRITEREADX error :
Relating to function or activity: Unable to write to a given process.
Cause: The Guardian Procedure call WRITEREADX failed to complete communication with the
process. The process may not be running or an invalid buffer or count is specified in the
WRITEREADX Guardian Call. Please refer to the Guardian Procedure Manual for a better
description of the values returned by WRITEX.
Effect: The WRITEREADX Operation on the opened process fails. If the process is not running,
then subsequent calls to the process will fail too.
Recovery: If the process is not running, then make sure it is running again before trying the
operation again.
WVPASAP 114
: READUPDATEX error :
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.
WVPASAP 115
: REPLYX Error
Relating to function or activity: TERMMAN process replying to a message it received from the
SEEVIEW process.
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 communication with the SEVIEW process will not complete, the SEEVIEW process will
be terminated and al files opened by it will be closed.
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 are up and running.
WVPASAP 130
: Error opening $RECEIVE :
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.
WVPASAP 143
: Error opening File :
Relating to function or activity: The File could not be opened to perform I/O Operation.
Cause: The file could not be opened. The EMS Event indicates the error value returned by the
Guardian Procedure call FILE_OPEN_.
Effect: Any future I/O Operations on the file will fail.
Recovery: 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.
WVPASAP 144
: Error Reading file :
Web ViewPoint ASAP User Guide – 528941-003
24