Previous Topic: Specifying ConditionsNext Topic: Changing a Referenced Access Path

Modifying Access Paths › Choosing Select/Omit Criteria › Select/Omit in DDL Index

Select/Omit in DDL Index

In CA 2E r8.7, a new generation mode *DDL is introduced. Using this generation mode, the existing DDS database can be regenerated to have an SQL type database. You can still access the existing RLA functions that were built using the DDS database without regenerating and recompiling them. Prior to CA 2E r8.7, the select/omit criteria was applicable to *DDS and *SQL generation modes only. Henceforth, the select/omit criteria is applicable to the *DDL generation mode too.

Considering all the three generation modes, *DDS, *SQL, and *DDL, the following table displays the location where the Select/Omit criteria get generated.

Generation Mode

Allow Select/Omit criteria Settings

 

YDBFACC=T(TABLE)

YDBFACC=G(DBFGEN)

DDS

Static

Select/Omit criteria in the logical file

 

 

 

Dynamic

Select/Omit criteria in the logical file

 

 

SQL

Static

 

Select/Omit criteria in the Program code

Select/Omit criteria in the SQL View

 

Dynamic

 

Select/Omit criteria in the Program code

Select/Omit criteria in the Program code

DDL

Static

 

Select/Omit criteria in the DDL index

 

 

Dynamic

 

Select/Omit criteria in the DDL index

 

As shown, when you regenerate the database as a DDL database, the select/omit criteria gets generated into the DDL index as a WHERE clause. Any RLA function that uses the DDL database, can now access the same records that the RLA function has accessed over the DDS database.

In DDL generation mode, irrespective of the "Allow select/omit criteria" settings being static or dynamic, the select/omit criteria gets embedded in the DDL index. You do not have to regenerate and recompile the function. The select/omit criteria are generated for all the access path types that DDL supports.

Note: The select/omit criteria, over DDL implementation supports RTV and RSQ access paths.