z/OS Options window

Use the z/OS® Options window to set advanced options for stored procedures targeting DB2® for z/OS.

Stored procedure options page

Runtime options

For SQL stored procedures only: Type a string that specifies the IBM® Language Environment® run-time options to use with stored procedures. Language Environment is an IBM product that combines run-time libraries for different programming languages. If you do not specify any run time options, Language Environment uses its installation defaults. Requirement: If routines run concurrently, you must specify a particular set of run time options. The run-time option TEST generates debugging information at run time. If NOTEST is specified, no debugging information is generated.

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.
WLM environment
Type the name of the MVS™ workload manager (WLM) environment in which to run the routine. The name can contain up to 18 alphanumeric characters. When you do not specify a WLM environment, the routine runs in the address space that was established when DB2 was installed. When you use different WLM environments you can isolate one group of programs from another. For example, you can isolate programs based on their security requirements. Work with your system administrator to determine whether to use this option.
ASUTIME 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 keep 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.
External security
Specify security options for the routine.
DB2
Specifies that if the stored procedure accesses resources that an external security product protects, the access is performed using the authorization ID that is associated with the stored procedure address space. Select this option if you do not want the stored procedure to run in a special external security environment.
User
Specifies that if the stored procedure accesses resources that an external security product protects, the access is performed using the authorization ID of the user who invokes the stored procedure. Select this option if you want the stored procedure to run in an external security environment.
Definer
Specifies that if the stored procedure accesses resources that an external security product protects, the access is performed using the authorization ID of the owner of the stored procedure. Select this option if you want the stored procedure to run in an external security environment.

Deploy options page

Build utility
For SQL stored procedures only: Specify the name of the stored procedure build utility to call when an SQL stored procedure is built on a z/OS server. Your database administrator can configure copies of the build routine to use different resources as necessary. The current database is queried to retrieve valid build utility names. If valid names are found, you can select them here. For example, the DSNTPSMP build utility can be entered in this field after the database administrator configures it on the z/OS system.
Build owner
For SQL stored procedures only: Type the DB2 for z/OS authorization ID that will hold responsibility for building, rebuilding, and dropping the routine. If 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.
Precompile options
For SQL stored procedures only: Type the SQL precompile options that you want to use to build stored procedures. See the IBM DB2 for z/OS Application Programming and SQL Guide for more information about precompile options.
Compile options

Type a string that specifies compiler options that you want to use with this stored procedure. The compiler option TEST generates debugging information at compile time. If you specify NOTEST, no debugging information is generated.

Prelink options
For SQL stored procedures only: Type a string that specifies options for the prelinker. The prelinker combines the object modules of an application into a single object module.
Link options
For SQL stored procedures only: Type a string that specifies options for your linkage editor. The linkage editor processes the object module that is created by the prelinker and generates a load module that can be retrieved and run. See the documentation for your linkage editor for more information.
Bind options

The first field shows the collection ID that was specified for the package. The collection ID was specified on the Options page of the wizard that creates new stored procedures.

In the second field, type a string that specifies bind options for both Java and SQL 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 that process releases the row.

Root package
For Java SQLJ stored procedures only: Type a unique root name for the packages that the SQLJ binder will create, or use the generated default name. The default name is seven characters, but you can type up to a maximum length of 127 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
Select to view the detailed status of the progress of the deploy. The deploy messages are displayed in the SQL Results view.

Feedback