You have several options for loading SQL source into a data view. You can either load native SQL DDL or create SQL schemas from your SQL DDL source. It is highly recommend that you create SQL schemas rather than loading native SQL DDL. The advantage to creating a schema over loading native SQL DDL is that the schema, which is primarily a list of tables, is easier to maintain. A single SQL schema can reference tables from several SQL DDL files. Therefore, if a table changes you only need to edit it in one place, then rebuild the schemas that include it.
As an alternative, you can also load SQL DDL source from the command line.
Before loading your SQL, set the properties that describe the SQL you are loading. For example, you might be loading SQL that is for HCO (DB2) or SQL that is specifically for Micro Focus's SQL Option for DB2. You can also specify whether or not to allow mixed case in your SQL tables, and whether or not you want AppMaster Builder to automatically generate a REDEFINES statement for any copybook field whose corresponding SQL field is a DATE, TIME, or TIMESTAMP. This lets you specify a particular date and/or time format, such as U.S. or European.
Before you begin, be sure that the SQL DDL source is in your project SQLDDL directory. If your SQL DDL source file contains a CREATE SUBSCHEMA statement, all tables you want in the data view must be in that file. For information on coding SQL DDL source, see Coding SQL DDL Sources.
To take make the best use of this feature, create a series of SQL DDL files that each contain one table, along with any associated indexes or views on that table, and no CREATE SUBSCHEMA statement. You can include each table in as many SQL schemas as you like.