Load Schema (Windows)
Typically, the dictionary is stored in the project root (e.g. E:\Sample). In the example, the script file has been stored in a sub folder OSI (E:\Sample\osi\Sample.osi).
...>E:\Sample\ODL.cmd
This procedure is properly initialized when generating the Sample project but has to be adapted to specific requirements when generating other projects. The options -R and -C is suggested in order to check the schema after being imported and mark data types as checked and ready.
The load protocol is written to console as shown in the example below.
2010-09-23 21:02:33 - Running C:\Programs\odaba\ODL.exe with:
ini-file: E:\Sample\osi\Sample.odl
script file:
Options used: -C: -R:
New database created at 'e:/Sample/Sample.dev'
... checking all persistent structures
Address ... checking structure
Address...checked successfully
Car ... checking structure
Car...checked successfully
Company ... checking structure
Company...checked successfully
Employee ... checking structure
Employee...checked successfully
Person ... checking structure
Person...checked successfully
... checking all extent definitions
Company ... checking extent
Company... checked successfully
Employee ... checking extent
Employee... checked successfully
Persons ... checking extent
Persons... checked successfully
... setting version number for all structures
When there is no odaba.ini stored in the ODABA system folder or when it contains an invalid reference to the ode.sys database, instead of the message
New database created at 'e:/Sample/Sample.dev'
the following two messages will appear:
Undescribed Error : 98 in LDBHandle::Open (e:/Sample/Sample.dev,InputArea,ik_name,,,)
which can be ignored.
When the input file contains invalid characters after being edited, errors like
symbol 'sc_element' accepts empty expressions
SOS Error :
Error at line 2, column 15
No match for 'schema_dcl' at: ... Sample {
in: sc_definition
in: sc_element
in: sc_elements
in: ODL
may occur. Please make sure that the input script is valid.