Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ errinfo(2) — HP-UX 5.00

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

err(1)

errnet(2)

errno(2)

perror(3C)

ERRINFO(2)  —  Series 500 Only

NAME

errinfo − error indicator

SYNOPSIS

extern int errinfo;

HP-UX COMPATIBILITY

Level: HP-UX/EXTENDED

Origin: HP

Remarks: Errinfo is implemented on the Series 500 only. 

DESCRIPTION

When an error occurs in a system call, the external variable errno is set to the standard HP-UX error number, and more detailed information is stored in the external variable errinfo.  Errinfo obtains its value from the escape code returned by the underlying HP-UX kernel. 

Errinfo is not cleared on successful system calls, so it should only be checked after an error has been indicated. 

Software that is intended to be portable across HP-UX implementations should not reference errinfo. 

The errinfo values and their meanings are as follows:

VALUE MEANING

*4 NVM address out of range;

 5 buffer request is not within valid range;

 6 buffer address space overflow;

*7 address specified does not reference a valid buffer;

*10 specified process priority level out of range;

*11 a non-existent code segment is specified;

*12 attempt to delete non-existent partition;

*13 system parameter not addressable;

*14 system parameter cannot be referenced with an EDS pointer;

*20 invalid message link;

*21 invalid message link;

*22 message limit exceeded;

*23 link limit exceeded;

*24 link being deleted contains processes waiting for messages;

*30 timer canceled;

*31 timer stopped;

*32 cancel already done for specified timer ID;

*33 stop already done for specified timer ID;

*34 timer ID not stopped before cleared;

*35 timer ID not canceled before cleared;

*36 attempt to set time and date to a value outside accessible range (midnight January 1, 1900 to midnight December 31, 25599);

*37 stack extension error;

 40 memory overflow (private partition);

 41 memory overflow;

 42 no free partition available for allocation;

 43 segment table overflow;

 44 memory controller block overflow;

 45 partition overflow;

 46 pointer passed as an argument does not point to a valid segment;

 47 segment size is out of range;

*48 free space chains are inconsistent, segment map corruption;

*49 free space chains are inconsistent, block map corruption;

 50 pointer passed as an argument does not point to a valid segment;

*51 block address within a segment is invalid;

 56 device or interface card timed out;

 57 system call aborted by signal(2);

*59 improper resource management in operating system;

*60 improper resource management in operating system;

*63 routine called for wrong I/O device or at wrong time;

*64 routine called for wrong I/O device or at wrong time;

*65 used in BASIC only;

 66 hardware or firmware error in interface card;

*67 I/O transaction aborted by device or interface card;

 68 an HP-IO interface card failed its self test;

*69 used during power-up, produces "System halted - incompatible IOP’s" message;

*70 no such object;

*73 out of timer ID’s;

*74 timer ID out of range;

*75 start_partition parameters not consistent;

*76 parameter to start_partition not addressable;

*77 attempt to change to non-existent partition;

*78 must be a system process to change to partition;

 80 device not ready for request, may be busy with some other operation, or power may be off;

 81 media is write-protected and cannot be altered;

 82 media has been mis-inserted;

 83 format switch disables driver from doing a media format operation;

 84 media error was detected, usually a CRC, parity, or checksum error; data may not be valid;

 85 cannot find record on media; usually indicates trouble in reading the header/servo information on the media;

 86 the read check of data written to a record has failed;

 88 media may have been changed since last access; buffered data may have to be thrown away;

*89 used to implement internally generated re-tries;

*90 software failure was detected; perhaps data structures were corrupted, or an unexpected event occurred;

 91 unknown error; indicates some type of device or interconnect malfunction;

*94 media_active (true) request must be made before first access;

 95 a parameter for a particular request is not supported by this driver; usually indicates that the type of card does not support a special function;

 97 termination mode is not supported by this device driver;

 98 EOI must have a data byte associated with it before it can be written;

*99 driver must be opened for request;

 100 record number out of allowed range; usually indicates corrupt directory structure;

*101 the transfer length was negative, zero, or odd for a halfword read or write request; can also indicate a transfer past the end of the media volume;

 102 halfword or byte mode transfers are not supported by this driver;

*103 cannot close a locked driver; this is a fault of the calling code;

 105 the argument specified for this ioctl request is out of range or points to the wrong type of structure;

 106 The ioctl command given is not recognized by this device;

 107 an attempt was made to attach two different drivers to the same device; these drivers are incompatible and cannot co-exist; the new driver is not attached, but the old driver remains unchanged;

 108 the size of the string is not correct for this string register access;

 109 interleave factor not supported by disc; it is either zero, negative, or too big;

 110 invalid address was detected by the driver, or the interface card occupies the same subaddress as the device;

*111 capacity of disc exceeds 32-bit record address range assumed by driver;

 112 reference to an unsupported pseudo-register was made; if the request accessed multiple registers, the previous (if valid) register accesses were made;

 113 HP-IB TCT byte must be at the end of the ATN sequence because you have passed control;

 114 a request is not supported by this driver;

 115 no driver with that name was found;

 116 no driver is available for that card, or the device address value is out of range;

 117 write verify is not supported for this mass storage device;

 118 length of −1 specifying that a transfer should be used is invalid;

 119 an invalid value was assigned to a pseudo-register;

 120 data transfer was terminated due to the reception of a secondary address;

 121 for buffered devices, a data transfer cannot be satisfied due to un-transferred data from the other direction; for example, a write may not be possible if there is still unread data present on the device;

 122 device cannot satisfy this request because of a previous request or the current state of the device;

 123 the beginning of the tape was encountered before the operation could be completed;

 124 the interface cannot be the HP-IB active controller when doing this operation;

 125 synchronous data rate could not be met to complete the operation; system may be too heavily loaded, or the specified bandwidth parameters for this or another device may be wrong;

 126 a hardware fault was detected; controller/status card should be examined for further information;

 127 the device/interface was not found at the specified address; power may be off, or the address could be wrong;

 128 the end of tape was encountered before the operation was complete;

 129 the device failed its self test or a diagnostic; no further access to this device should be attempted;

 130 the HP-IB interface is too slow for this synchronous device;

 131 tape end of file was encountered before request could be completed;

 132 the device was busy and could not handle the request;

 133 the media is absent from the device;

 134 the media is not formatted, and must be formatted before use;

 135 too many media errors prevent formatting to complete; formatting operation may be only partially done;

 136 the media has no more spares left but had to spare some data; the sparing was not done;

 137 the HP-IB interface must be the active controller to execute this operation;

 138 the HP-IB interface must be the system controller to execute this operation;

 139 no data seen on media after a device specific length of media; this is a sequential tape error;

 140 more data was found in the record than was requested for the read operation; the remaining data was lost, and cannot be read by the next read request;

 141 the media physical format is incorrect for this disc;

 142 media failure has occurred, or the media has deteriorated such that replacement is suggested; writing is no longer allowed; media may only last long enough for a back-up;

 143 the HP-IB interface is not addressed to read or write as requested, and because it is active controller, it cannot become addressed;

 144 the read or write request data transfer was aborted by an HP-IB IFC or an HP-IB device clear operation;

 145 not all the data (or commands) were accepted by the device;

 146 not all the data was sourced by the device;

 147 controller or unit fault was reported by the device;

 148 some failure occurred in receiving the device status result; usually means that not all the status was returned, or the controller reported a failure when the driver attempted to receive the status;

 149 the operation cannot be completed because a user programmed hold off has occurred;

*150 system problem or failure;

*151 successful completion of task; should not be visible;

 157 the volume label specified in the volume specifier does not match the volume label on the volume;

 158 links may not be removed if the file has been opened with the "no purge link" option;

 160 cannot open a directory with write access;

 161 two or more volumes have the same volume label and the file system is unable to distinguish between them for this request;

 162 an attempt was made to access an open file in a way forbidden by the file system;

 163 the disc format does not support the requested operation;

 164 the file cannot be opened for writing because it is currently being execed, or the file may not be opened with execute access because it is currently opened for writing;

 165 the file/device could not be opened because the system open file table is full; this is caused by a memory overflooverflow

 166 a file may not be opened in both "shared" and "exclusive" modes; your access mode conflicts with the current mode;

 167 a signal was received while waiting to read or write to a pipe;

 168 the request cannot be performed because the designated file is open or in use at the current time;

 169 an attempt was made to purge a link to the file without obtaining the necessary access rights;

 170 not enough disc space could be allocated to satisfy the request;

 171 a file with the same name already exists in the directory;

 172 the file ID passed to the system was bad;

 173 an attempt was made to read beyond the physical end of the file;

 174 tried to write to a pipe for which there are no readers;

*175 the request made is not supported by the file system;

 176 same as error 162, except that the file may not be open;

 177 a "position" (lseek) request was made on a pipe;

 178 the device driver specified in the volume specifier does not match the current device driver being used for the volume;

 179 the disc format specified in the volume specifier does not match the disc format on the volume;

 181 some file in the file path could not be found;

 182 the device specified is not a random access blocked device;

 183 the disc format on the disc does not support volume labels;

 184 the disc format on the disc does not support file passwords;

 185 the disc does not contain a recognizable disc format; the disc format name given for an initialize request is not known to the system;

 188 the region of the file that was accessed is currently locked;

 189 a volume may not be initialized while there are open files on it;

 193 a non-directory was specified where a directory was required;

 198 the request cannot be satisfied because another file cannot be added to the directory; no i-nodes were available;

 201 the request cannot be satisfied because the directory is not empty;

 204 the file system was unable to extend a "contiguous" file without creating another extent;

*210 invalid file code;

 216 the select code in the device address in the volume specifier is not within the acceptable range for this hardware configuration;

*217 an attempt was made to remove or change a password which does not exist;

*218 an attempt was made to put two identical passwords on a file with different capability sets;

*219 a simple deadlock was encountered when locking a file;

 221 the file name is too long (LIF discs support 10 characters, HP 9845 format discs support 6 characters, and SDF discs support 16 characters);

 222 invalid character in LIF or HP 9845 format disc file name;

*223 invalid character in LIF or HP 9845 format disc password;

*224 volume label is too long on a LIF or HP 9845 format disc;

*225 password too long on a LIF or HP 9845 format disc;

*226 invalid character in volume label on a LIF or HP 9845 format disc;

*227 invalid date on LIF or HP 9845 format disc;

*228 invalid record size on LIF or HP 9845 format disc;

 229 invalid record mode on LIF or HP 9845 format disc;

 230 a file name was expected and none was specified, or an attempt was made to purge the "." or ".." links from a directory;

 231 a subdirectory was specified when the disc format does not support subdirectories;

 232 links not supported on LIF or HP 9845 format discs;

 233 non-UNIX systems are not allowed to establish duplicate links to a directory;

 234 the device (file) specified for the mount/umount request is not a block special device;

 235 the device (file) specified for the umount request is not currently mounted;

 236 a volume could not be unmounted because it is currently being used (there are open files or working directories established on the mounted volume); a volume could not be mounted because it is already mounted; the directory being mounted on is open or is the root directory;

 237 an attempt was made to establish a link from one volume to another;

 238 raw discs must be lseeked and read/write sizes must be multiples of the device’s physical sector size (256 bytes for discs, 1024 bytes for cartridge tapes). 

 241 the byte address on a file access was outside the acceptable range for the file; the byte address must be non-negative;

 242 the file system saw a directory, i-node, or bit map record which contains inconsistent data;

 244 an attempt was made to read beyond the logical end of the file;

 249 an attempt was made to unlock an unlocked file;

*252 time value out of range;

*253 hours, minutes, or seconds value out of range;

*254 day, month, or year value out of range;

*255 invalid date;

 256 specified segment does not exist;

 257 page table has not been initialized;

 258 page has not been initialized;

 259 lock count has overflowed;

 260 lock count has underflowed;

 261 entire working set cannot be locked;

 262 lock length is invalid;

 263 segment is not locked;

 264 locked segment cannot be extended;

 265 page is not locked;

 266 segment is not paged;

 267 segment is not shared;

 268 requested segment lengths are inconsistent;

 269 minimum working set request cannot be satisfied;

 270 frame pool cannot be expanded;

 271 virtual memory device table overflow;

 272 virtual memory device index is invalid;

 273 default virtual memory device cannot be removed;

 274 virtual memory device index is inactive;

 275 virtual memory device index is in use;

 276 a locked page was encountered;

 301 escape through user code for exec;

 302 target process not found in kill call;

 303 target process has the wrong real user ID in kill call;

 304 no processes found in a broadcast signal attempt;

 305 signal number out of range;

 306 not super-user; requires super-user permission;

 307 a bad argument was supplied to a system call;

 308 an attempt was made to wait with no children;

 309 an intrinsic was aborted by a signal;

 310 process stack overflow;

 311 unrecognized  ulimit command;

 312 your DB relative argument had an offset greater than 512 Kbytes;

 313 fix-up offset exceeds segment size (see a.out(5));

 314 stack pointer passed to brk;

 315 invalid segment number in user pointer;

 316 an attempt was made to kill(0,sig) with no current process group;

 317 file number out of range;

 318 specified file ID not open;

 319 ioctl call not implemented;

 320 inappropriate ioctl command for device;

 321 ID not in the range 0 to 65535;

 323 floating point divide-by-zero;

 324 floating point overflow;

 325 floating point underflow;

 327 wrong number of system call parameters;

 328 inconsistent executable file;

 329 front panel timeout (series 500, models 30 and 40 only);

 330 graphics to internal CRT timed out;

 331 graphics hardware does not respond;

*332 unexpected error when performing an open;

*333 unexpected error when performing a close;

 334 illegal mode of driver was requested;

 335 a buffer was passed to an intrinsic that is too large;

 336 DMA terminated abnormally;

 337 received one more x coordinate than y coordinate;

 343 user program called missing kernel segment;

 345 attempt to execute a file which is too small;

 346 attempt to execute a file with a bad magic number;

 347 unimplemented configure function;

 348 maximum stack exceeded;

 349 fatal stack overflow;

 350 the requested heap size is too big;

 358 there is no tty device at this address;

 359 this request is not supported by this device;

 360 semid, msqid or shmid is not a valid IPC identifier;

 361 semnum in semctl(2) or mtype in msgsnd(2) out of range;

 362 invalid cmd to semctl(2), msgctl(2), or shmctl(2);

 363 nsems out of range in semget(2);

 364 ID for key exists but nsems or size inconsistent with existing ID;

 365 mtext is greater than msgsz and msg_noerror is false in msgrcv(2);

 366 IPC key exists but operation permission denied;

 367 IPC operation permission denied;

 368 operation requires caller to be super-user or owner or creator of specified IPC ID;

 369 ID does not exist and IPC_CREATE not specified;

 370 system-imposed limit on number of IDs exceeded; ID not created;

 371 ID exists for key, but IPC_CREATE and IPC_EXCL both specified;

 372 nsops is greater than the system-imposed maximum;

 373 sem_num is less than zero or greater than or equal to the number of semaphores in the set associated with semid;

 374 operation would result in suspension of the calling process but IPC_NOWAIT specified;

 375 operation would cause semval or semadj value overflow;

 376 specified semaphore or message queue ID has been removed from the system;

 377 insufficient memory for IPC structure;

 378 message queue does not contain message of desired type and IPC_NOWAIT specified;

 379 shared memory size or message size (msgsz) out of range;

 380 shmaddr is invalid (non-zero);

 381 number of shared memory segments per user exceeded;

 382 shmflg is invalid (SHM_RDONLY set);

 383 no line discipline of the requested value was found;

 384 the ioctl command given is not recognized by this device;

 385 the argument specified for this ioctl request is out of range or points to the wrong type of structure;

 386 an attempt was made to enable process accounting when it was already enabled. 

 387 the file specified for process accounting is not an ordinary file;

 388 lockf deadlock detected;

 389 lockf no more free locks;

 390 plock permission invalid (not superuser);

 391 PROCLOCK is invalid (PROCLOCK, TXTLOCK, or DATLOCK exists);

 392 TXTLOCK is invalid (PROCLOCK
 or TXTLOCK exists);

 393 DATLOCK is invalid (PROCLOCK or DATLOCK exists);

 394 UNLOCK is invalid (no lock exists);

 395 op is invalid (not PROCLOCK, TXTLOCK, DATLOCK, or UNLOCK);

 396 plock invalid in [vfork,exec] window;

 397 get/setitimer invalid in [vfork,exec] window;

 398 timer specification is invalid;

 399 timeval is invalid;

 400 no interrupt packet for this file descriptor;

 401 illegal mode mask used in hpib_io function call;

*440 internal error;

 441 protection modes do not match with existing segment;

 442 device is not a ‘CS80’ device;

 443 attempt to add a device not specified with a device file;

 444 attempt to pass an EMS intrinsic a parameter which is out of range;

 445 attempt to memchmd segment codes which are shared by more than one process;

 446 attempt to filemap a file which has already been filemapped by process;

 447 insufficient memory available to complete memallc request;

 448 the specified memory address is invalid;

 449 attempt to use EMS intrinsic on memory not allocated by memallc;

 450 super-user capability is required to create this kind of file;

 451 specified file or directory does not exist;

 452 an invalid RPM program descriptor was used;

 453 an RPM child process was interrupted;

 455 attempt to close file failed;

 456 abortive file close occurred; data may have been lost;

 457 attempt at an abortive file close failed;

 458 incorrect select code; device or address does not exist;

 459 too much data was given for an RPM request;

 460 a string is too long;

 461 a name used for RPM is too long;

 462 an invalid file ID was used;

 463 an open file could not be found;

 464 attempt to create a process has failed;

 465 connection limit set by the super-user was reached;

 466 login not allowed;

 467 RPM was not allowed to create a remote process;

 470-483
not enough memory could be found; check the network memory limit set with npowerup;

 490 TCP security mismatch;

 491 remote login failed;

 493 an RPM login is invalid;

 494 consumer login sequence is invalid;

 496 login sequence is invalid;

 497 connection attempt was not accepted by the remote system;

 498 new inbound path rejected, possibly due to lack of local resources;

 500 RPM cannot set up the login environment;

 501 RPM service is denied;

 502 service instance is denied;

 503 login on the producer system is invalid;

 505 illegal socket name length was used for IPC;

 506 illegal node name length was used for IPC;

 507 too many file name sets were given for RFA;

 508 too many node names were given in an RFA path specifier;

 510 attempt was made to copy a directory;

 511 parameter contained an illegal value;

 513-516
register number or value is unacceptable;

 517 internal error; contact qualified HP support personnel;

 518 incorrect file type; cannot create RFA remote file;

 519 flag specified for RPM is invalid;

 520 an option specified for RPM is invalid;

 521 unacceptable format for an RPM option;

 522 address given could not be used;

*523-524
internal error; contact qualified HP support personnel;

 525 illegal characters in an IPC name;

 526 incorrect IPC socket descriptor used;

 529 illegal IPC flag value was used;

 530 illegal IPC data length was used;

 532 illegal IPC control request was used;

 533 illegal IPC option structure was used;

 535 illegal IPC request value was used;

 536 illegal IPC timeout value was specified;

 537 IPC receive size too big;

 540 IPC send size too big;

 541 data unit is too large;

 543 IPC socket specified is not a virtual circuit socket;

 544 illegal address format;

 545 nested remote path names are not allowed;

 546 IPC socket specified is not a destination socket;

 547 IPC socket specified is not a source socket;

 548 error in field endpoint;

 559
 no local IPC socket descriptors are available;

*560-685
internal error; contact qualified HP support personnel;

 690 network is already up;

 691-692
network is down;

*694 internal error; contact qualified HP support personnel;

 695 network is going down;

 700 incorrectly formatted network directory was specified;

 701 2285A LAN Unit download file is bad;

 705 a LAN Interface hardware problem has been detected;

 706 LAN Interface failed its selftest;

 707 LAN Interface failed during a transmit attempt;

 708 LAN Interface failed during a receive attempt;

 709-710
2285A LAN Unit failed during a download;

 711 HP-IB Interface failed;

 720-722
network transport timeout occurred;

 723 remote system did not respond to retransmission attempts;

 724-725
no activity on a connection; the connection has been aborted;

 726 attempt to establish a connection has failed;

 730-732
remote system has violated network protocol;

 733 a message is too long;

 734 request was made that is unacceptable to the transport or to a remote service;

 735 unrecognized RFA request;

 736 request is unserviceable at this time;

 737 unrecognized RFA request;

 738 invalid response from the remote system;

 739 remote RPM process has violated network protocol;

 740 remote RPM process has reported an unrecognized error;

*741 an unrecoverable network protocol error has occurred;

 745 requested service cannot be supplied;

 747 system cannot support an interchange operation;

 748 system cannot support a restart operation;

 749 checkpointing not supported;

 750 system cannot support a transient operation;

 751 unknown system type;

 752 buffer too small;

 753 invalid remote file request;

 754 an error response was received;

 755 RPM does not support the requested feature;

 756 remote node’s version of IPC is incompatible;

*757 internal error; contact qualified HP support personnel;

 761 incorrect or unknown path name;

 762-763
destination is unreachable;

 764 file specified is not a network special file;

*765 internal error; contact qualified HP support personnel;

*767 internal error; contact qualified HP support personnel;

 768 system name used is unknown to the local node;

 770-774
connection has been lost;

 777 IPC connection request failed;

 778 connection to producer is down;

 780 name specified for the producer system could not be found;

 782 name specified for the consumer system could not be found;

 784 insufficient resources on the producer system;

 785 insufficient resources on the consumer system;

 786-787
not enough memory could be obtained on the remote system. The remote system could be out of physical memory or the network memory limit on the remote node could be too small;

 788 IPC socket already exists;

 790 IPC socket name could not be found;

 792 IPC virtual circuit connection was killed;

 794 IPC virtual circuit socket cannot be named;

 796 IPC connection is pending;

 798 IPC process does not own the socket;

 800 IPC operation would block;

 804 the program for RPM is invalid;

 806 the program for RPM could not be loaded;

 808 LAN Interface failed. If resetting the Interface does not eliminate the problem, contact qualified HP personnel. 

All errinfo values marked with an asterisk (*) indicate a serious system problem which should be checked by qualified HP support personnel. 

For errinfo values 360-382, IPC refers to the interprocess communications facilities provided by message queues, shared memory, and semaphores.  For errinfo values 450-999, IPC refers to the interprocess communications facilities provided by local area networking. 

SEE ALSO

err(1), errnet(2), errno(2), perror(3C). 

WARNING

Errinfo is intended for diagnostic purposes only.  Values and meanings may change in future releases of HP-UX. 

Hewlett-Packard  —  last mod. May 11, 2021

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026