SQLJ stored procedures

The SQLJ Stored Procedures general tab has an over view of the information about a stored procedure. It includes information about who created the stored procedure and when, and the group number. This is a static page, except that you can rename the procedure from this page.

The SQLJ Stored Procedure parameter tab displays information about the attributes of the input parameters. The attributes are:

Name – displays the name of the input parameter.
Type – displays the datatype of the input parameter.
Mode – displays the mode is either in or out, with in being an input parameter, and out being an output parameter.
Order – the order of the parameter in the list of parameters. This is a numeric vlaue.

The SQLJ Store Procedure parameters tab is a static tab displaying the properties of the parameters for the stored procedure. To change the parameters displayed here, you must change the definition of the procedure by dropping it and recreating it with the new definition.

The SQLJ Store Procedure permission tab displays a property sheet for the permissions. You can grant execute permissions for a stored procedure to users, groups, or roles.

When you chose a user to whom you want to grant stored procedure execute permission, you can select the property button to display the property sheet for the object you are selecting.

To grant a permission on an object, click in the grid box for the object and type of permission. Continue clicking in the box to cycle through the options:

Grant
Grant with grant
Revoke
Revoke with cascade
No permissions

Using Java-SQL capabilities, you can install Java classes in the database and then invoke those methods from a client or from within the SQL system. You can also invoke Java static (class) methods in another way--as SQLJ stored procedures.

SQLJ stored procedures:

Can return result sets and/or output parameters to the client.
Behave exactly as Transact-SQL stored procedures when executed.
Can be called from the client using ODBC, isql, or JDBC.
Can be called within the server from other stored procedures or native Adaptive Server JDBC

The end user need not know whether the procedure being called is a SQLJ stored procedure or a Transact-SQL stored procedure. They are both invoked in the same way.