Modifying Access Paths › Understanding Access Path Auxiliaries › For DDS Query (QRY) Access Paths

For DDS Query (QRY) Access Paths

Use the following three types of i OS objects to implement a QRY access path in DDS:

• An i OS logical file based on the real physical file whose data is being referenced.
• An i OS physical file, which does not contain any data, but is used to define a record format and keys to any HLL program generated for a function based on the QRY access path.
• A CL program that executes the OPNQRYF command. It is called at execution by any program generated for a function based on the QRY access path.

Each object type has its own source, either DDS or CL, which is held in the appropriate source file in the generation library.

All three of the auxiliary objects must be generated and compiled.

You can control the implementation names given to the auxiliary objects by controlling the names given to the source members generated for them. If the YALCVNM model value is set to YES, CA 2E will automatically supply source member names.

Note: The current implementation of DDL generation mode uses only *TABLE as data access method. Therefore, QRY access path is not generated in DDL mode as it uses only SQL views.

For more information about access path auxiliaries and QRY access paths, see the "Access Paths: An Introduction" chapter.