Use the Options page to specify optional settings 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.
- Specific name
- Shows the specific name for the stored procedure, a unique name that
distinguishes multiple stored procedures with the same name and different
parameters. If you do not specify this name, the database generates it the
first time you build the procedure. You can use the specific name to drop
or comment on a stored procedure. You can not use the specific name to invoke
the stored procedure.
- Result sets
- Shows the maximum query result sets that the stored procedure can return.
To change the number of result sets for a SQL stored procedure, change the
number in the CREATE PROCEDURE statement in the source page.
- Language
- Shows the language of that the stored procedure is written in.
- Parameter style
- Shows the conventions used for passing parameters to and returning the
value from stored procedure.
- Package
- Shows the package for the SQL stored procedure.
- Contains SQL
- Specifies that the stored procedure contains SQL statements and does
not read nor modify SQL data.
- Reads SQL data
- Specifies that the stored procedure reads SQL data.
- Modifies SQL data
- Specifies that the stored procedure modifies SQL data.
- No SQL
- Specifies that the stored procedure cannot execute any SQL statements.
Note: Although the NO SQL option implies that no SQL statements can be specified,
non-executable statements are not restricted.
- Jar ID
- Type the Jar identifier for the Java™ stored procedure.
- Class name
- Shows the class name of the Java stored procedure. To change the class
name for a Java stored procedure, modify the class name in the
source code. When you build the stored procedure, the stored procedure with
the old name is dropped from the database, and the stored procedure with the
new class name is created.
- Threadsafe
- Select to specify that the database manager runs the stored procedure
in the same process as other routines. For the stored procedure to be threadsafe,
it cannot use any global or static data areas
- 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 procedure, change
the WLM Environment in the source page.
- Collection ID
- Shows the collection ID of the stored procedure. To change the collection
ID for a SQL stored procedure, modify the collection ID in the source code.
- ASU time limit
- Shows the total amount of processor time, in CPU service units, that a
single invocation of a stored procedure can run. To change the ASU time limit
for a SQL stored procedure, modify the source code by adding the option in
the CREATE PROCEDURE statement.
- Stay resident
- Shows whether the stored procedure load module remains in memory when
the stored procedure ends. When this check box is not selected, the load module
is deleted from memory after the stored procedure runs. To change this option
for a SQL stored procedure, modify the source code by adding this option
in the CREATE PROCEDURE statement.
- Commit on return
- Shows whether the stored procedure sends a COMMIT statement when the stored
procedure returns. The COMMIT statement terminates a unit of work and commits
to the database changes that were made by that unit of work. To change this
option for a SQL stored procedure, modify the source code by adding this option
in the CREATE PROCEDURE statement.
- Deterministic
- Shows whether the stored procedure returns the same result from successive
calls with identical input parameters. When this check box is not selected,
the stored procedure might not return the same result from successive calls
with identical input parameters.
- Fenced
- Shows whether the stored procedure is FENCED. When FENCED, a stored procedure
does not access the database manager's internal resources, such as data buffers.
By default, the created stored procedure runs FENCED. To change whether a
SQL stored procedure runs FENCED, modify the source code by adding the NOT
FENCED option in the CREATE PROCEDURE statement. Requirement: When a stored
procedure returns a result set, it must run FENCED.
- DB2
- Shows whether the stored procedure runs in a special external security
environment. When the button is selected, the stored procedure will not run
in a special external security environment. If the stored procedure accesses
resources that are external security product protects, access is performed
by using the authorization ID associated with the stored procedure address
space.
- User
- Shows whether the stored procedure runs in a special external security
environment. When the User radio button is selected, the stored procedure
runs in an external security environment. If the stored procedure accesses
resources that are protected by an external security product, access is performed
by using the authorization ID of the user who invoked the stored procedure.
- Definer
- Shows whether the stored procedure runs in a special external security
environment. When the Definer radio button is selected, the stored procedure
runs in an external security environment. If the stored procedure accesses
resources that are external security product protects, access is performed
by using the authorization ID of the owner of the stored procedure.