1 3.3 SYSTEM CHARACTERISTICS
8.3 RESOURCE REOUIREMENTS
The Basic I/O System obtains memory from the calling job's memory pool when creating obje.cts. The values listed here refleci Release 3 of the iRMX II Operating System.
Object Number of 16-b1te paragraphs
required by the Basic I/O Syst€m
I/O Result 4 (5 for an intemal IORS that the Operating Segment Systeú creates wheo attaching a device)
Connection (to 6
named îile)
Connectíon (to 4
physicalfile)
User object 3 (mínimum)
8.2 Nucleus Uset's Guide
C.1 INTRODUCTION
Table C-1 provides a c.mplete list of the Extended iRMX II condirion codes rhat can occul during system operations. It lists the condition codes by layer with their numeric values alld mnemonics.
--continued
Table C-1. Conditions ard Their Codes Category/
Mnemonic Meaning
Numeric Code Hex Decimal E$OK The most recenî system call was
successful. OH 0
A time limit (possibly a limit of zero time) expired without a task's request being satisfied.
There is not sufficient memory avail-able to satisry a task's request.
Anofher task currently has access to the data p.otected by a region.
A task artempted an operation which, if it had been successful, would have violated a Nucleus-enforced limit.
A system call was issued out of co[text or the operating system was asked to perform an impossible operation.
A toke[ pammeter has a value which is not the token of an existing
oolect.
EXCEPTION CODES
Table C-1. Conditions And Their Codes lcontinued) Category/
A task attempted an operation which would have caused an impossible tîansition of a task's state.
This system call is not part of the present mnfiguration.
An interrupt task has accumulated the maximum aÌlowable number ol SIGNAL$-INTERRUPT reqùests.
An intenupt task has accumulated more than the maximum allowable
amount of SIGNAI-$INTERRUPI requests.
A NACK, tìmeout, or bus error occurred There are no available GDT slots.
A data chain has been returned. The
Nucleus Communications System Environmental Conditions E$CANCELLED
A SEND$RS\ry transaction has been remotely cancelled.
The host$id portion ofthe socket parameter is not valid.
The local buffer is too small to hold the message data.
The buffer on the remote agent is too small to hold the message data.
Either the simultaneous messages, o!
or trarisactions is not adequate.
0081H 225
EXCEPTION CODES
Table C-1. Corditions And Theh Codes lcontinuedì Category/
The transmission is already done, or the specified trans$id is invalid.
The socket is zero and the local port There has been a transmission I/O System Environmental Conditions
E$FEXIST
The specified file already exists.
The specificd file does not exist.
The device driver and file driver are not compatible.
The combination of parameters entered is not supported.
The specilied entry in a directory file is empty.
The specified directory entry index is beyond the end of the directory file.
The connection does not have the correct access to the file.
The requested operation is not valid for this file type.
The requested operation attempted an improper kind of file sharing.
There is no space left on the volume, An invalid device driver request
Table C.1. Conditions And Their Codes (continued)
The mnnection specified in the call was deleted before the operation completed.
The device contains an invalid or improperly formatted volùme.
The device being accessed is now offline.
An invalid file driver request occurred.
The file is îoo fragmented to be extended.
The call is atte.npting to delete a directory that is not empty.
The connection parameter is a device connection, not a file connection.
The connection parameter is not a device conlection.
The connection is not open for reading writing or updating.
The task attempted to open a connection that is already open.
The specified connection was opened by the EIOS, and used by the BIOS which is not allowed. Once you have an open connectlon, you must manipulate it with a system call provided by the same I/O S1,stem.
A soft detach was specified, but connectioDs to the device still exist.
The specified device is already attached.
The file specified is on a device that the operating system is in the process of detaching.
The existing pathname and the new pathname refer to different devices.
You cannot simultaneously rename a file and move it to another device.
The call is attempting to rename a directory to a new path containing itself.
A strcam fiÌe request is out oi context. Either it is a query
request and another query request is already queued, or it is a
satis8' rcquest and either the reques. queue N empry or a query request is queued.
The connection refers to a file with an invalid fnode. You should dclete this file.
The specified pathname contains invaÌid characters.
The volume aheady contains the maximum number offiles- No more fnodes are available for new files.
The specified pathname staÍs with a colon (:), but it does not contain a second, matching colon; the specified pathname has more than 12 characters or contains invalid characters.
The Basic I/O System has insuf-ficient memory to proccss a request.
EXCEPTION CODES Table C-1. Conditions And Theh Codes lcontinued)
Nucleus Uset's Guide c-5
Table C-1. Conditions And Their Codes lcontinuedì
Extended I/O System was unable to lind the name in the object
directories of the local job, the global job, and the rootjob.
The user who attempted to detach the device is not the owner of the
device.
The Efended I/O System carinot create an l/O job because the size specified for the object directory
The User Delinition File is not
i . r h è . ; o h r f ^ r - " r
The user name specified in the call is not listed in îhe Ilser DeJ:nition File.
The user ID in the specified user object does not match the ID listed in the User Definitior File for the corresponding user name.
The password specified in the call does not match the one Iisted in the User Dcfinition File for the corrcs-ponding user name.
'I'he User Definition File specified cannot be found.
An unknown type of I/O error
o@ufred.
A soft I/O error occurred. A retry might be successful.