StaticBinder utility, as used for client optimization

With the StaticBinder utility, you can create and bind DB2® packages that contain the SQL statements in your pureQueryXML files. You can also choose to create DBRM files that you can later transfer to a z/OS® data set and use to create DB2 packages. XML schema validation can also be performed on the input pureQueryXML files.
The privilege set of the user that invokes the utility must include one of the following authorities:
  • SYSADM authority
  • DBADM authority
  • If the package does not exist, the BINDADD privilege, and one of the following privileges:
    • CREATEIN privilege
    • DB2 for z/OS: PACKADM authority on the collection or on all collections
    • DB2 Database for Linux, UNIX, and Windows: IMPLICIT_SCHEMA authority on the database if the schema name of the package does not exist
  • If the package exists:
    • DB2 for z/OS: The BIND privilege on the package
    • DB2 Database for Linux, UNIX, and Windows: ALTERIN privilege on the schema and BIND privilege on the package
The user also needs all privileges that are required to compile any static SQL statements in the application. Privileges that are granted to groups are not used for authorization checking of static statements.

DB2 Database for Linux, UNIX, and Windows: If the user has SYSADM authority, but no explicit privileges to complete the bind, the DB2 database manager grants explicit DBADM authority automatically.

Named parameter markers: If you bind SQL statements that use named parameter markers, you must specify the property enableNamedParameterMarkers with the value 1 when you specify the connection to the data source. The StaticBinder -url option specifies the connection to the data source. The following example -url option connects to the SAMPLE database on testserver.test.com and specifies the propertyenableNamedParameterMarkers.
-url jdbc:db2://testserver.test.com:50000/SAMPLE:enableNamedParameterMarkers=1;

Feedback