Use the New Stored Procedure wizard to create a new stored procedure.
- Name
- Type a name for the stored procedure. The name can be qualified with the schema name, and can contain letters and numbers but must start with a letter. The stored procedure name can be delimited with quotation marks to preserve lowercase characters or spaces. This name does not have to be unique within the database, but you cannot create a stored procedure with the exact same name and signature.
- Project
- Select the data development project that is associated with the connection that you are currently using in the Data Source Explorer. The projects available are existing development projects that are associated with the same connection that you are working with in the Data Source Explorer. The new stored procedure will be created in the selected development project.
- New
- Opens the New Project window, where you can create a new project that is associated with the connection that you are currently using in the Data Source Explorer.
- Language
- Select a language for the stored procedure.
- Java package
- Shows the Java package that is generated using the timestamp value attached to PKG.
- Dynamic SQL using JDBC
- Select to use Java Database Connectivity (JDBC) with dynamic SQL to access the database. Select this option to create a stored procedure that can be ported to other database management systems.
- Static SQL using SQLJ
- Select to use embedded SQL that adheres to the SQLJ standard to access the database. Using SQLJ allows you to embed SQL statements into Java programs. Select this option when you want to encapsulate authorizations. Requirement: SQLJ supports SQL syntax that follows SQL92 or earlier standards. This requirement applies to all static SQL statements in your stored procedures. Stored procedures that contain static (SQLJ) statements must run in fenced mode.
- Root package
- DB2® for Linux, UNIX, and Windows only: 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.
- 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.
- 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.