C-ISAM Standard Errors |
Virtual Machine |
 |
|
C-ISAM Standard Errors |
Virtual Machine |
|
This section explains the error numbers that may be issued to system variable @ERRand suggests remedial action to be taken.
10000 End of file reached
Action: This is typically handled by PROIV.
10001 File does not exist
Action: Check that the correct file name is being used and, if so, create the file.
10002 File already exists
Action: Check that the correct file name is being used and, if so, delete the existing file if required.
10003 Too many files open
Action: If possible, increase the number of open files allowed per process; otherwise reduce the requirement.
10004 No access permission
Action: Check the access permissions for the file, and correct them if appropriate.
10005 Bad argument passed
Action: Contact your local support representative.
10006 Handle not attached
Action: Contact your local support representative.
10007 Not enough memory
Action: Increase the available memory and try again.
10008 Not enough file space
Action: Increase the available file space if possible and try again.
10009 Maximum users exceeded
Action: Increase the permitted number of users, if possible, or reduce the application's requirements.
10010 Unrecognizable or corrupt file
Action: Check the structure of the file and repair or restore as appropriate.
10011 Invalid index structure
Action: Check the structure of the file and repair or restore as appropriate.
10012 Record does not exist
Cause: An attempt has been made to read or write using a unique key that does not exist in the file.
Action: None - errors at read are typically handled by the PROIV function.
10013 Record (key) already exists.
Cause: An attempt has been made to add a record with one or more unique that already exist in the file.
Action: Code the application so that the user can retry or so that the problem does not arise.
10014 Record or file is locked
Action: This is typically handled by the PROIV function, which will retry until the record or file becomes available.
10015 Bad key value
Action: Check the value of the key used.
10016 Record too large or too small
Action: Check the file definition and the file itself for an illegal record size.
10017 Supplied buffer too small
Action: Contact your local support representative.
10018 Operation valid only on primary key.
Action: Contact your local support representative.
10019 Key description is not valid
Action: Check the specification of a key (typically derived from the PROIV file definition) is legal, and tallies with a key in the actual file.
10020 Currency required for operation
Action: Contact your local support representative.
10021 Bad mode requested
Action: Contact your local support representative.
10022 Connect failure
Action: Check the information used to connect to the database.
10023 File allocation error
Action: Check the system specific error code (@SYSERR) for more information on the cause of the error.
10024 File deallocation error
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error.
10025 File open error
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error.
10026 File close error
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error.
10028 Error reading record
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error.
10029 Error writing record
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error.
10030 Error deleting record
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error.
10040 Transaction Handling Error
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error.
10041 Deadlock
Action: None. PROIV will. perform an automatic rollback when detected.
10042 Transaction already in progress
Action: File create/delete must be separate transactions.
10043 Insecure commit performed
Action: (Warning) separate commit of databases.
10044 Logging error
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error.
10045 Signal handling error
Action: Contact your local support representative.
10090 Interface driver already started
Action: Contact your local support representative.
10091 Interface driver stopped
Action: Contact your local support representative.
10092 Interface driver damaged
Action: Contact your local support representative.
10095 Maximum users exceeded
Action: Purchase less restrictive or reduce requirement.
10096 No interface driver installed
Action: Check that the interface was purchased and correctly installed.
10097 Unsupported operation
Action: Contact your local support representative.
10098 Unsupported service request
Action: Contact your local support representative.
10099 Unexpected error conditions
Action: Check the system-specific error code (@SYSERR) for more information on the cause of the error; contact your local support representative if necessary.
Topic ID: 720232