CORBA 2.6.1 Programmer's Reference
Table Of Contents
- CORBA 2.6.1 Programmer's Reference
- Legal Notice
- Contents
- New and Changed Information
- About This Manual
- Chapter 1. Core CORBA
- Chapter 2. Interoperability and Interworking
- Chapter 3. C++ Language Mapping
- Chapter 4. Java Language Mapping
- Chapter 5. Naming Service
- Chapter 6. Event Service
- Chapter 7. Transaction Service
- Chapter 8. NonStop CORBA vthread Interface
- Chapter 9. NonStop CORBA Event Framework
- Chapter 10. Exception Handling: NonStop CORBA Minor Codes
- Chapter 11. NonStop CORBA System Error Messages
- Index
- Local Disk
Common Error Messages (Error numbers 1000
1099)
1001 - ZDOM-GEN-ERR-NO-MEMORY
User Action: During ORB initialization, access to the NSDCFGDB configuration database is
initiated. If an internal database object can not be instantiated, a no memory message is posted.
This message might indicate a corrupt database.
1002 - ZDOM-GEN-ERR-CONFIG
User Action: During ORB initialization, access to the NSDCFGDB configuration database is
initiated. If a newly instantiated internal database object can not be used, a no configuration error
message is posted. This message might indicate a corrupt database.
Event Framework Messages (Error numbers 1100 -
1199)
1100 - Event FrameWork error
User Action: This error occurs when some notable event occurs in the Event FrameWork. The
detailed error text explains the error in more detail.
Database Error Messages (Error numbers 1200 -
1399)
1203 - Get of first record failed
User Action: This message is issued if NonStop CORBA fails to read the first record in a database.
This message might indicate a corrupt database.
1204 - Attempt to get next record failed: Key xyz Failed
User Action: Due to an operating system error, an I/O error occurred while attempting to access
the next record. Contact your service provider.
1206 - Attempt update failed: Key xyz Failed
User Action: Due to an operating system error, an I/O error occurred while attempting to access
the next record. Contact your service provider.
1209 - Failed to create database: FILE_CREATE name
User Action: An attempt to create a database failed. Some possible reasons might be the file
system might be full, the user might not have proper permissions to update the file, or the database
filename might not be correctly spelled.
1210 - Failed to open database: Cannot open database file name. Aborting.