At runtime, for a single program, there are always three independent VLS object members (or load modules)-one reentrant, one non-reentrant, and one for the symbol table. There can be more VLS members depending on the size of the program.
The distinction between reentrant and non-reentrant is significant because the execution of CA Ideal applications online takes place in pseudo-conversational mode. At the end of each CICS transaction, some or all of the in-core resources are written to CICS auxiliary temporary storage or CICS EDSA. Exactly what is written to auxiliary temporary storage and what remains in core depends on the format of the program or panel.
If programs and panels were converted to load modules, they are controlled by CICS. The CA Ideal program or panel run status has no effect on load module format.
The program symbol table is loaded only when a runtime error occurs.
In a DB2 environment, execution of programs containing SQL in static mode requires an application plan. The “Preparing DB2 Application Plans” chapter describes how application plans are generated and used at runtime.
In CA Datacom/DB, SQL access plans are built at compile time.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|