The Static I/O Modules, created as part of the CA Ideal GENERATE PLAN procedure, are Assembler subprograms that CA Ideal calls during static execution of SQL. These subprograms, which contain the SQL statements from the programs specified in the plan resource definition, are passed to the DB2 precompiler.
The GENERATE PLAN command creates up to 10 Static I/O Modules. At one time the DB2 precompiler imposed a limit on the number of source lines that could be processed, so CA Ideal provided a facility to limit the number of SQL statements that would be used to generate each module. When the SQL content of the next program would exceed this maximum, another module is created. This facility still serves a purpose in limiting the size of the static I/O Static I/O Modules. To enable this process, use the SET PLAN MAXSQL command. This command sets the maximum number of SQL statements allowed in each module
Note: Since the static I/O module for a package is created during a package generation, not a plan generation, any MAXSQL value specified for the GENERATE PLAN does not affect the package static I/O module, only the modules created for the plan.
The name of each Static I/O module is the one- to seven-character plan name, with an eighth character of 0 for the first module, and 1-9 for the second through tenth modules.
If the plan includes any packages, the first static I/O module contains header information for the static I/O modules for the packages. If the plan includes only packages, the (single) static I/O module contains only the global COMMIT, ROLLBACK, and SET CURRENT USER statements.
Note: The load library that the GENERATE PLAN procedure uses as SYSLMOD must be available to any CICS partition DFHRPL or batch STEPLIB where the applications associated with the plan are expected to execute in static mode.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|