Use the Deploy page to specify deploy options for the stored procedure.
Depending on whether you are using DB2® for LUW, DB2 for iSeries™, DB2 for z/Series, or Derby, some of these
fields may not apply to you.
- Precompile options
- Type the SQL precompile options that you want to use for building this
SQL stored procedure.
- Compile options
- Type a string that specifies the compiler options to use with this stored
procedure.
- Bind options
- Shows a string that specifies the bind options for packages. The default
options are ACTION(REPLACE) and ISOLATION(CS). ACTION(REPLACE) specifies that
the package replaces an existing package with the same name. ISOLATION(CS)
ensures that your application does not read a row that another process changes
until the process releases that row
- Collection ID
- Type the name of the collection ID. The collection ID identifies the package
collection that is used when the stored procedure is run. The name can contain
up to 18 alphanumeric characters. If you are creating a Java™ stored
procedure for z/OS®,
the collection ID that you specify in this field must match the one that was
used when binding the JDBC driver on DB2 for z/OS.
- Root package
- DB2 for Linux®, UNIX®,
and Windows® only:
Type the root name of the packages that the SQLJ binder will create. If an
option is not specified, a root name will be derived from the name of the
profile. The names will have a maximum length of seven characters. The digits
1, 2, 3, and 4 will be appended to the root package name to create the four
final package names (one for each isolation level). Packages are bound with
the following isolation levels: PACKAGENAME1 bound with isolation level UR;
PACKAGENAME2 bound with isolation level CS; PACKAGENAME3 bound with isolation
level RS; PACKAGENAME4 bound with isolation level RR.
- WLM environment
- Shows the name of the MVS™ workload manager (WLM) environment in which the stored
procedure runs. To change the WLM environment for a SQL stored procedure,
modify the WLM ENVIRONMENT in the source page.
- Build utility
- Type the name of the stored procedure build utility to call when building
a SQL stored procedure on a z/OS server. Your DBA can configure copies of build
routine to use different resources as necessary. These custom routines are
called build utilities and are identified with unique names.
- Build owner
- Type the DB2 for z/OS authorization
ID that will hold responsibility for building, rebuilding, and dropping the
routine. By specifying a secondary authorization ID or group name as the
build owner, more than one user could share responsibility for maintaining
this routine. If you do not specify a build owner, the build utility designates
one of your process authorization IDs, such as the CURRENT SQLID, as the build
owner.
- Prelink options
- Type a string that specifies the prelink options for the pre-linker. The
pre-linker combines object modules that comprise an application into a single
object module. See the documentation for your pre-linker.
- Link options
- Type a string that specifies the link options for your linkage editor.
The linkage editor processes the object module created by the pre-linker
and generates a load module that can be retrieved for execution. See the documentation
for your linkage editor.
- Java compile
options
- Type the Java compile options that you want to use when building
the stored procedure. Consult your Java compiler documentation for the valid Java compile
options.
- Verbose build
- Select the check box to view the detailed status of the progress of the
build, The build messages are displayed in the Output view when you deploy
the procedure.
- Build stored procedure on the server
- For Java stored procedures only: Select this option to build
stored procedures by using DSNTJSPP on the DB2 for z/OS server. If you do not select this
option, the Java source is compiled on the client. This option limits
stored procedure source code to 32 KB. Otherwise, source code can be up to
10 MB.
- DB2 Package
- DB2 for iSeries only:
Specify the DB2 package
name that you want to use when building SQLJ stored procedures. For example,
QUSRSYS/SER3283432 where QUSRSYS is a library name which is followed by a
10 character serialized profile name. For information about valid values,
see the DB2 documentation
on building SQLJ stored procedures.
- Enable debugging
- DB2 for Linux, UNIX,
and Windows only:
Select to build the stored procedure for debugging.