Use the Deploy options page of the New Stored Procedure wizard
to specify options for deploying and debugging the stored procedure.
- Jar ID
- For Java™ stored procedures only: Type the JAR ID that will
be used when you install the stored procedure on the server, or use the default
JAR ID.
- Specific name
- For SQL stored procedures only: Type a unique name for the stored procedure.
If you do not enter a name here, a unique name will be created for you. You
can use this name to drop or comment on a stored procedure. You cannot use
the specific name to run the stored procedure.
- Deploy
- Select to automatically deploy the stored procedure when you finish using
this wizard. The deploy action compiles the stored procedure and creates the
class file and JAR file for Java stored procedures. If you do not select
this option, you can continue to make changes and deploy the stored procedure
later.
- Enable debugging
- For SQL stored procedures targeting DB2® Linux®, UNIX®, and Windows® only: Select to build the stored
procedure for debugging.
- Current® schema
- Specify the name of the current schema to use during the deploy process.
- Collection ID
- For stored procedures targeting DB2 for z/OS® only: Type the name of the collection
ID, or click Browse to open a window so that you can
select a 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
- For stored procedures targeting DB2 for z/OS only: Click to open a window so that
you can set advanced options for DB2 for z/OS stored procedures.