HP Neoview Messages Manual page 390

Table of Contents

Advertisement

Error Number
0201
0210
0211
0213
0214
0215
0216
0217
0218
0219
0220
0221
0222
0223
0224
0225
0230
0231
0232
0233
0240
0241
0246
0248
0249
0250
0251
0252
0255
0512
0513
0514
0515
0516
0517
0518
0519
0520
0521
390
File-System Errors
File-System Error Text
The current path to the device is down, an attempt was made to write to a nonexistent process,
the message-system request was incorrectly formatted, or an error was found in the message
system interface.
Device ownership changed during operation.
The node performing the operation failed during the operation.
Channel data parity error (path error).
Channel timeout (path error).
I/O attempted to absent memory page (hardware path error).
Memory breakpoint encountered during this I/O operation.
Memory parity error during this I/O (hardware path error).
Interrupt timeout occurred on a channel, or a controller, modem, or the line between, or lost the
modem clock (path error).
Illegal device reconnect (path error).
Protect violation; an I/O controller attempted an illegal write.
Controller handshake violation (path error).
Bad channel status from EIO instruction (path error).
Bad channel status from IIO instruction (path error).
Controller error (fatal error).
No unit assigned or multiple units assigned to the same unit number (path error).
Node power failed, then restored.
Controller power failed, then restored.
Access is denied due to error in communication with the security monitor.
Error in call to SERVERCLASS_SEND_.
Network line handler error; operation not started. Ownership switch was performed.
Network error; operation not started.
External cluster bypass error; operation aborted.
Network line handler error; operation aborted.
Network error; operation aborted.
All paths to the system are down.
Network protocol error (path error).
Required class is not available.
Net line handler flooded; too many interrupts.
An invalid parameter was specified.
A file name was missing.
The sequential I/O procedures do not support the specified device type.
The specified access is invalid.
The specified buffer address is invalid.
The specified file code in the SET^FILE call does not match the file code of the file.
The block buffer provided to OPEN^FILE is too small.
The block length specified in the SET^FILE call does not match the block buffer length in
OPEN^FILE.
The specified record length was either too small or too large.
The specified file is not a valid EDIT file.

Advertisement

Table of Contents
loading

Table of Contents