Use this page to specify routine options.
- Precompile options
- Type the SQL precompile options that you want to use to build stored procedures.
You can enter PRECOMPILE PROGRAM (PREP) and BIND options. SQL precompile options
that name data sets are not recognized. See the IBM® DB2® Command Reference for more information
about the PRECOMPILE PROGRAM (PREP) and BIND options.
- Compile options
- Type a string that specifies compiler options that you want to use with
this stored procedure.
- Enable debugging
- DB2 for Linux®, UNIX®,
and Windows® only:
Select to build the stored procedure for debugging.
- Apply folder settings
- Specifies that the settings that you applied to the folder will be applied
to the selected routine.
- SQLJ translator location
- Specify the full path and file name of the JAR file containing the SQLJ
class library that implements SQLJ translation support.
- SQLJ translator class name
- Specify the full package-qualified name of the SQLJ class used for translating
SQLJ statements.
- 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.
- Apply defaults
- Specifies that the default values from the preferences will be applied.
- Apply settings to folder
- Specifies that the settings that you applied to the folder will be applied
to all the routines under the folder.
- 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 a collection ID is not specified, the
collection name of the package that contains the CALL statement is used when
the stored procedure is run. If the calling program does not use a package,
the package collection is set to the value of special register CURRENT PACKAGESET.
- Runtime options
- Type the language environment run-time options for the stored procedure.
If run-time options are not specified, the language environment uses its installation
defaults.
- WLM environment
- Type the name of the MVS™ workload manager (WLM) environment in which to run
the object. The name can contain up to 18 alphanumeric characters. When you
do not specify a WLM environment, the object runs in the address space that
was established by DB2 during installation. When you use different WLM environments,
you can isolate one group of programs from another. You might want to isolate
programs based on security requirements. Work with your system administrator
to determine whether to use this option.
- ASU time limit
- Shows the total amount of processor time, in CPU service units, that a
single invocation of a stored procedure can run. Specify an integer value.
If you do not specify an integer value, then the NO LIMIT option is
used. Setting a limit can be helpful when you are debugging a stored procedure.
- Stay resident
- Select to specify that the stored procedure load module in memory after
the stored procedure runs. When this option is not selected, the load module
is deleted from memory after the stored procedure runs. When the stored procedure
remains in memory, performance is enhanced because you eliminate the time
it takes to load the application. However, this option increases the amount
of virtual storage that is required by the stored procedure address space.
- DB2
- Select to specify that the stored procedure will not run in an external
security environment. If the stored procedure accesses resources that an external
security product protects, the access is performed by using the authorization
ID that is associated with the stored procedure address space.
- User
- Select to specify that the stored procedure will run in an external security
environment. If the stored procedure accesses resources that an external security
product protects, the access is performed by using the authorization ID of
the user who invoked the stored procedure.
- Definer
- Select to specify that the stored procedure will run in an external security
environment. If the stored procedure accesses resources that an external security
product protects, the access is performed by using the authorization ID of
the owner of the stored procedure.
- Build utility
- Shows the name of the stored procedure build utility to call when a Java™ stored
procedure is built on a z/OS® server. Your DBA can configure copies of the build
routine to use different resources as necessary. If valid names are found
in the database, you can select them here.
- Build owner
- Shows the DB2 for z/OS authorization
ID that will hold responsibility for building, rebuilding, and dropping the
routine. When you specify a secondary authorization ID or group name as the
build owner, more than one user can 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 options for the prelinker. The prelinker
combines the object modules in an application into a single object module.
- Link options
- Type a string that specifies options for your linkage editor. The linkage
editor processes the object module that the prelinker creates and generates
a load module that can be retrieved for execution.
- Bind options
- Type a string that specifies bind options for packages.
- Build stored procedure on the server
- Select this option to build the stored procedure on the server. If you
do not select this option, the DB2 Universal JDBC driver is used to build
the stored procedure. This option limits stored procedure source code to 32KB.
Otherwise, source code can be up to 10MB.
- Root package
- 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.
- Verbose build
- Select to view the detailed status of the progress of the build. The build
messages display in the Output View.
- Jar name
- Derby Version 10 source database only: Shows the JAR file name that will
be used to install the routine on the server. DB2 also uses this JAR file name as the
JAR ID in the DB2 catalog.
- Source file
- Derby Version 10 source database only: Specify the full path to the Java source
file, or click Browse to find it.
- 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.