World Driver Schema

jdeDirect World Driver – Schema Description.

This reference is intended for information purposes only, for those users that are interested in learning how the driver builds the World database schema and presents the files and fields to the application that executed the jdeDirect driver.

Library List

The library list can be established by Environment Name or the User Profile, use the control panel ODBC Driver Controls program to switch from using the Environments library list to the User Profiles library list.

The environment library list is established using a combination of the F0093 and F0094 files, the Users library list is defined in the F0092 file.

Files List

The list of available files is established by looking through the SVR (Software Versions Repository) file (F9801) in ODBC configured security library, both physicals and logicals are picked up including any custom files that are defined in SVR.

Each file found in SVR is then verified against the sessions library list to ensure that it actually exists before being presented back to the application.

The SQL executed is:

SELECT * FROM F9801 WHERE SIMID IN (SELECT TABLE_NAME FROM QSYS2/SYSTABLES WHERE TABLE_TYPE IN ('P', 'L') AND SYSTEM_TABLE_SCHEMA IN

(Library List)) AND SIMID LIKE 'F%' AND SIFUNC IN ('PF', 'LF') AND SISY <> '88'

Individual File

The file specification is established by collecting the fields from the ACTUAL file in the library list, and then building up the representation as configured in the ODBC definition by linking to SVR and the data dictionary and data field specifications file F9201 in A7 and F9210 in A8.

It is important to note that the driver does not query the SVR to retrieve field names, this is due to SVR potentially being out of sync with the physical file structure.

Primary keys are determined from the F9803 file.

Vocabulary Overrides

The vocabulary overrides are then applied for each field.