Access plans for programs that access CA Datacom SQL dataviews are generated automatically when you compile the program. You can set plan options, such as the cursor isolation level, date and time format, and the ordering of table joins, in the Environment fill-in of the program definition. Or you can allow them to default to site or session DBSQL options.
The plan options are included in the program object and are stored as intersection data in the PGM-PLN-USES relationship in the dictionary. The plan entity is stored in the PLAN table in the dictionary. You can change these options in the program object by specifying the ALTER PROGRAM ENVIRONMENT command, but to include those changes in the plan itself, you must rebind the plan.
You can define multiple plans for a program by defining additional authorization IDs for the program. You can then select the plan dynamically by assigning the authorization ID at runtime.
Note: DB2 plans are generated and maintained differently. For more information, see the “Preparing DB2 Application Plans” chapter.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|