Deploy Routines wizard - Deploy Options page

Use this page to specify options for the deployment.
Use current database
Select to deploy the routine to the database that you are currently connected to.
Use different database
Select to deploy the routine to a database that you are not currently connected to.
Database
Select the name of the database that you want to connect to to deploy the routine, or click Connection to connect to a new database.
Target schema
Select or type the name of the schema to use during the deployment process. For DB2® for z/OS® Version 7 and DB2 for z/OS Version 8 (compatibility mode), the target schema is the SQLID that will be used for unqualified objects.

For Informix databases, this field is called Target owner.

Default path
Type the path to use during deployment.
For DB2, the default path is used when you deploy SQL stored procedures, but not Java™ stored procedures. At run time, the default path is used for Java stored procedures, but not for SQL stored procedures.
Specify the default path as a list of one or more comma-separated schema names. Optionally, to preserve case, enclose a schema name in double quotation marks; for example, FERMAT, "McDrw #8", SYSIBM.
Stop and roll back on errors
Specifies that the deployment process will stop when there is an error. The routines that were deployed successfully before this error occurred will be rolled back. This option is not available for Java SQLJ stored procedures.
Note: If you are deploying multiple external stored procedures to a DB2 for z/OS database, procedures that were deployed before an error occurs cannot be rolled back.
Duplicate handling
Specify options for how to handle duplicate routines on the database.
Drop duplicates
Specifies that any routine that already exists in the database will be dropped before the routine is deployed.
Treat duplicates as errors
Specifies that an error occurs when a routine already exists in the target database.
Ignore duplicates and continue to next routine
Specifies that the deployment process will ignore routines that already exist in the target database and continue with the next routine.
Deploy by building source
Select to do a full build and to deploy the source and the binaries to the database.
Deploy by using binaries if available
Select to deploy the binaries that you built on the source database instead of doing a full build. If the binaries are not available in the source database, then a full build is done before deploying the binaries.
Target load library
For DB2 for z/OS only: Type the name of the target load library for the deployment.
Deploy source to database
For Java stored procedures, select to deploy the Java source to the database.
Deploy pureQuery runtime to database server
Select for the workbench to deploy the JAR files for pureQuery runtime to the database when you deploy the stored procedure.
Bind pureQuery interfaces specified in bindProps
Select for the workbench to run the StaticBinder utility on all of the interfaces that are listed in the .bindProps file that is associated with the stored procedure.

Feedback