Use
to specify import options and to specify whether objects that
already exist in the project should be replaced with duplicate import
objects.
- Replace duplicate routines in project
- Select
to overwrite duplicate routines in the project. Routines are considered
duplicate if they have the same name and signature.
- Deploy
- Select to automatically deploy the routine
to the database that is assigned
to the development project.
- Current® schema
- Select or type the name of the current schema to use during the
deploy
process.
- Enable debugging
- DB2® for Linux®, UNIX®,
and Windows® only:
Select to build the stored procedure for debugging.
- JAR ID
- Type the JAR ID that will be used when
you install the stored procedure
on the server, or use the default JAR ID.
- 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.
- 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.
- Package
schema
- Type the qualifier for the packages that db2sqljcustomize
binds. db2sqljcustomize
stores this value in the customized serialized profile, and it is
used when
the associated packages are bound.
- Collection
ID
- DB2 for z/OS® only:
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.
- Advanced
- Opens the z/OS Advanced
Options window.