Previous Topic: Allow RLA Access over DDL DatabaseNext Topic: Allow LVLCHK(*YES) for SQL/DDL indexes having RCDFMT keyword


Allow SQL/DDL Generation without hard-coded schema name

When generating SQL/DDL database files in CA 2E, we now have the option to generate SQL/DDL database objects which do not contain a hard-coded schema name. This functionality is controlled using the model value YSQLCOL. Using this feature, the generated database object can be compiled into any desired SQL collection or library (as specified in the YSQLLIB model value). This allows for simplification in the deployment environment and also helps provide support for change management environments where the object needs to be recompiled into a different SQL collection/library, without making changes to the previously generated source.

The YEXCSQL command has been modified to cater to these changes.

Limitation:

There is a long standing limitation with CM wherein 2E created SQL objects cannot be promoted by compiling them. The workaround is to promote (move) the objects as 3GL objects, *without* compilation.

Note: When a change in the CM environment is carried out to create objects into a normal library (from the previous target SQL collection), the CM repository of the target environment might have to be refreshed.

The following documentation deliverables were updated for this feature: