Running a customization script adds runtime information to the SQLJ serialized profiles in your project that is specific to DB2® and binds the profiles to the database.
An SQLJ-enabled Java™ project uses a customization script to create packages on the database for the SQLJ profiles that are generated by the SQLJ translator. The customization script also binds the SQLJ profiles to the database, which enables your Java project to use static SQL rather than dynamic SQL. If you omit this activity, your project will use dynamic SQL, as JDBC does.
The DB2SQLJCustomize wizard generates the customization script from the information that you specify. If you want to use the existing customization script that is associated with a Java project to bind the SQLJ profiles to another database, the wizard can bypass the customization process and only bind the profiles in the package to the database.
The customize process creates a customization script for the options selected and the values specified in the wizard, and then runs the script. The bind process creates four packages that reflect the four isolation levels that the DB2 database manager supports.
After you customize and bind the SQLJ profiles in a project, only the profiles that are associated with updated SQLJ files need to be customized and bound again. You can start the customize and bind processes by selecting a command on the pop-up menu for the SQLJ file. When you customize and bind the profiles for an updated SQLJ file, you do not need to use the DB2SQLJCustomize wizard unless you want to change the customization settings. The customize process uses the customization settings that you specified when you used the wizard to customize and bind the profiles in the project that contains the SQLJ file. The customize process determines the packages that are associated with the SQLJ profiles and specifies them in the customization script.