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

failed. For backup process, recovery will depend on the specific Guardian error returned. For e.g.
Error 2 can be recovered from by providing a valid process handle.
WVPASAP 103
<Program Name> <Function Name>: Decompose Error: <Error Number>
Relating to function or activity: Primary or backup TERMMAN, SPMON, WASAP or SHUTWAS
process trying to retrieve process information from the process handle.
Cause: Occurs on the “PROCESSHANDLE_DECOMPOSE_” 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 14).
Effect: The primary TERMMAN, SPMON, WASAP or SHUTWAS process will not be able to
communicate with the backup and vice versa. This will prevent the backup process to take over
as the primary in case the primary process goes down. The primary will not be aware if the
backup goes down and the nonstop operation of WASAP will not take effect.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 14 can be
recovered from by restarting the Web ViewPoint (and hence WASAP) processes.
WVPASAP 104
<Program Name> <Function Name>: PROCESS_GETINFO_ error: <Error Number>
Relating to function or activity: Creating and verifying creation of a new process or accessing
information about an existing process.
Cause: Occurs on the “PROCESS_GETINFO_” Guardian procedure call that is triggered after
process creation. The Guardian error number indicating what the cause was is part of the event
text. This error condition could occur due to various reasons, for e.g. Error 1 for a file system
error.
Effect: The daily database updates or the one-time loads will not be completed.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 5 means
the processor where the process was to be run is unavailable. To correct this, run the process on
another processor.
WVPASAP 108
<Program Name> <Function Name>: TermManager Process Name Error <Error
Number>,<Error Detail>
Relating to function or activity: WASAP Teminal Manager process name could not be found.
Cause: Wrong or Invalid name being specified to stop the Terminal Manager process during
shutdown of WASAP.
Effect: The process will not be stopped.
Recovery: Specify a correct or valid process name and then retry the operation. Also make sure
that the process name which you specify does not already exist.
WVPASAP 110
<Program Name> <Function Name>: Pair Info Error <Error Number>
Relating to function or activity: WASAP processes 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 WASAP) processes.
Web ViewPoint ASAP User Guide – 528941-003
23