Configure options that require rebinding SQL statements

Except for the option -cleanConfigure TURE, Configure utility options generally do not affect all SQL statements or all named statement sets in a pureQueryXML file. When the Configure utility changes a statement set, the SQL statements in the statement set usually need to be rebound before the statements can be executed statically on a DB2® database.
For most options, the value of the configureStatus attribute for a named statement set determines whether the Configure utility option changes a statement set:
  • If value of the configureStatus attribute is AUTO, the statement set is changed only if an option requires a change. If the statement set is not changed, the SQL statements in the set do not require rebinding.
  • If value of the configureStatus attribute is FINAL, the statement set is not changed.
  • If value of the configureStatus attribute is REQUIRED, the statement set is changed. The SQL statements in the set must be rebound.

The Configure utility option -setPreStatusOfAllPkgs affects the value of the configureStatus attribute. If the option is specified, the Configure utility process the SQL statements and statement sets after the effect of the option is taken into account. The processing is not the based on the value of the configureStatus attribute at the start of the Configure operation.

You run the StaticBinder utility specifying the pureQueryXML file to bind or rebind the SQL statements in the statement sets. You can specify the StaticBinder option -differenceOnly TRUE when performing a bind operation. The option limits the bind operation to only the statements in statement sets that need to be rebound.

Note: The StaticBinder utility attempts to create packages and bind the packages for SQL statements only in named statement sets. You must run the Configure utility to put SQL statements that are in unnamed statement sets into named statement sets.

The following table lists the Configure utility options that change named statement sets if the value of the -cleanConfigure option is FALSE or is not specified. If you run the Configure utility with the value of the -cleanConfigure option set to TRUE, all statement sets are modified. All Configure utility options apply to all SQL statements that are in unnamed statement sets.

Table 1. Configure utility options that change statement sets and require rebinding SQL statements.
Option Named statement sets that are changed
-allowStaticRowsetCursors Statement sets with the value of the configureStatus attribute set to REQUIRED.
-collection Statement sets with the value of the configureStatus attribute set to REQUIRED.
-forceSingleBindIsolation Statement sets with the value of the configureStatus attribute set to REQUIRED.
-groupSQLBySpecialRegisters Statement sets with the value of the configureStatus attribute set to REQUIRED or AUTO.
-groupSQLByStrings Named statement sets are not changed. Only unnamed statement sets are changed.
-markDDLForBind Statement sets with the value of the configureStatus attribute set to REQUIRED.
-maxMissingSections Statement sets with the value of the configureStatus attribute set to REQUIRED or AUTO.
-pkgVersion Statement sets with the value of the configureStatus attribute set to REQUIRED or AUTO.
-removeSQLInactiveForDays Statement sets with the value of the configureStatus attribute set to REQUIRED or AUTO.
-removeInvalidSQL Statement sets with the value of the configureStatus attribute set to REQUIRED or AUTO.
-replaceLocations Statement sets with the value of the configureStatus attribute set to REQUIRED or AUTO.
-replaceSchemas Statement sets with the value of the configureStatus attribute set to REQUIRED or AUTO.
-restoreInvalidSQLForce All named statement sets.
-rootPkgName Named statement sets are not changed. Only unnamed statement sets are changed.
-setPostStatusOfAllPkgs All named statement sets.
-setPreStatusOfAllPkgs All named statement sets.
-sqlLimit Named statement sets are not changed. Only unnamed statement sets are changed.

There are Configure utility operations that are not associated with an option. The operations maintain the pureQueryXML file and ensure its validity.

Except for named statements sets with the value of the configureStatus attribute is FINAL, any of the following changes might occur. The changes require that the impacted packages be rebound.

Note: A pureQueryXML file is not fully useful by the StaticBinder utility for the binding process if section numbers are out of order or if SQL statements are in the wrong statement set. When the value of the configureStatus attribute is FINAL and the Configure utility determines that one of these changes apply, the utility either terminates the configure operation if necessary, or logs information about the problem.

Feedback