Preferences window - Java page

Use the Java™ page to specify default options for building on OS/390® or z/OS®.

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 32 KB. Otherwise, source code can be up to 10 MB. Select this option to build the stored procedure by using DSNTJSPP on the DB2 for z/OS server.
Compile options
Type a string that specifies compiler options that you want to use with this stored procedure.
Bind options
Type a string that specifies bind options for packages.
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.
Build utility name
Specify the name of the stored procedure build utility to call when a 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.
Build utility schema
Type the schema for the build utility that is specified in the Build utility name field.
Collection ID
Type the name of the default 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. The collection ID that you specify must match the one that was used when binding the JDBC driver on DB2 for z/OS.

Comentarios