HP Guardian Errors Manual page 72

Cause A stop request passes the security checks but the process is running at stopmode 2.
Effect The stop request is queued until the process to be stopped reduces its stopmode.
Recovery Informative message only; no corrective action is needed.
639
Cause A stop request does not pass the security checks and the process is running at stopmode 1
or 2.
Effect The stop request is queued until the process to be stopped reduces its stopmode to 0.
Recovery Informative message only; no corrective action is needed.
640
Cause DEBUGNOW is required instead of DEBUG for a privileged process.
Effect Debug mode will not be entered.
Recovery Use DEBUGNOW instead of DEBUG
654
Cause The system has detected that a message request buffer has been modified.
Effect Depending on the value of the AUTO_RETRY_ON_ERROR_654n attribute of the Kernel
subsystem, the system can either immediately report file system error 654 or retry sending the
request up to three times. Here the value of n can be either on or off.
Recovery If the reason for modifying the message request buffer is not legitimate, correct your
program.
700
Cause DP2 received an incorrect message sequence number.
Effect The operation fails.
Recovery Contact your HP service provider.
701
Cause Volume is in the DOWN state.
Effect The operation fails. TMF generates an EMS event that provides information regarding the
error.
72 File-System Errors
(%1177) Process cannot be stopped until
process goes to stopmode 0.
(%1200) DEBUGNOW is required instead of DEBUG
for a privileged process.
(%1216) AUTO_RETRY_ON_ERROR_654n specifies how the
systemhandles situations when a request
buffer is modified.
(%1274) FEWRONGRECOVSEQNUM - The sequence number of the message
received by the disk process from a recovery process
does not match.
(%1275) FEDEVICEDOWNFORTRANSACTIONS - The disk
process received a message from a recovery
process that requires that the disk process
be in the UP state; it is currently in the
DOWN state.