HP Guardian Errors Manual page 60

For a process file, either an attempt was made to write to a nonexistent process or a pending
WRITE or WRITEREAD was aborted because the server process read the request using
READUPDATE but died before it could reply.
For a device, the current path to the device was down.
Effect Either the operation never starts, the operation finishes but the path fails before a reply can
be made, or the processor fails.
For a process file opened with a sync depth of 0, the primary process fails if the process file is a
process pair.
Recovery For a process file, retry the operation once to establish communication with the backup
process. If a second error 201 occurs, no backup exists (both paths are down) and programmatic
recovery is impossible.
For disk server processes, open these processes with a sync depth greater than 0.
Then take corrective action appropriate to the device and the application.
210
Cause This error is associated with concurrent operations involving more than one unit connected
to a multiunit controller.
This error occurs when an operation is in progress in one unit on a multiunit controller and an error
is detected during an operation with another unit on the same controller. (The other operation
could have been on behalf of this or another application process.)
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is device dependent and application dependent.
211
Cause The processor module controlling the device associated with this file operation failed (path
error).
Effect The procedure sets the error code and returns without performing the requested operation.
The file operation itself stopped at some indeterminate point.
Recovery Corrective action is device dependent and application dependent.
213
Cause A controller or channel failure occurred (path error).
For a 3106 controller, a command could have arrived at the same instant that the controller was
busy processing a seek. However, if the problem is due to 3106 synchronization, this is an
informative message only.
Effect The file operation stopped at some indeterminate point.
Recovery Corrective action is device dependent and application dependent.
For the 3106 controller, use the IOTRACE program to examine the I/O trace area of the affected
processor.
214
60 File-System Errors
(%322) Device ownership changed during
operation. (device type: any except 2)
(%323) The processor performing the operation
failed during the operation.
(device type: any)
(%325) Channel data parity error
(path error). (device type: any except 2)
(%326) Channel timeout (path error).
(device type: any except 2)