Introduction › SQL Collection

SQL Collection

CA 2E lets you use SQL in place of or along with DDS in data definition statements. You use SQL to define tables, views, rows, and columns, rather than IBM i physical files, logical files, records, and fields.

You can implement SQL at both the system level and the model level. If you:

• Implement SQL at the system level, all new models default to SQL.
• Implement SQL at the model level, all access paths and functions default to SQL. Within a model, you can also specify SQL for individual access paths and functions.

The i OS operating system contains the execution objects necessary to execute applications you generate with SQL. However, if you want to generate and compile applications that use SQL, you must have:

• IBM’s SQL/400 program products installed.
• The QSQL library loaded on your IBM i.

To use SQL in a model environment, an SQL collection, equivalent to an IBM i library, must be associated with the model library. The YCRTMDLLIB command can automatically create the SQL collection. This command includes the SQLLIB parameter which lets you create the collection for a particular model.

You can create an SQL collection for an existing model with the Create SQL Library (YCRTSQLLIB) command. This command updates the YSQLLIB model value for the associated model. You then use the Change Model Value (YCHGMDLVAL) command to update the YDBFGEN model value to SQL.

For more information about:

• The YCRTSQLLIB and YCHGMDLVAL commands, see the CA 2E Command Reference Guide.
• For differences between earlier versions of CA 2E SQL implementations and current implementations, see the appendix SQL Implementation.
• IBM’s Structured Query Language, see your IBM documentation.