SQL/MX 2.x Reference Manual (H06.10+, J06.03+)

SQL/MX Statements
HP NonStop SQL/MX Reference Manual—544517-008
2-66
Considerations for CREATE PROCEDURE
Any Guardian file name you specify must match the designated schema
subvolume name for the schema in which the SPJ is being created. Otherwise,
NonStop SQL/MX returns an error.
filename
is an optional Guardian file name. The name must be eight characters long in
length and must end with the digits “00” (zero zero).
NO SQL
specifies that the SPJ cannot perform SQL operations.
CONTAINS SQL | MODIFIES SQL DATA | READS SQL DATA
specifies that the SPJ can perform SQL operations. Currently, all the options allow
an SPJ to read and modify SQL data. If you do not specify an SQL access mode,
the default is CONTAINS SQL.
DYNAMIC RESULT SETS max-result-sets
specifies the maximum number of result sets that the SPJ can return. If you specify
this clause, you must set the value in the range 0 through 255.
NOT DETERMINISTIC | DETERMINISTIC
specifies whether the SPJ always returns the same values for OUT and INOUT
parameters for a given set of argument values (DETERMINISTIC) or does not
return the same values (NOT DETERMINISTIC, the default option). For a
deterministic SPJ, the database server reserves the right to cache the results of a
CALL statement and reuse them during subsequent calls, optimizing the CALL
statement. NonStop SQL/MX allows both options but always treats the SPJ as
nondeterministic.
ISOLATE | NO ISOLATE
specifies that the SPJ executes either in the environment of the database server
(NO ISOLATE) or in an isolated environment (ISOLATE, the default option).
NonStop SQL/MX allows both options but always executes the SPJ in the SQL/MX
UDR server process (ISOLATE).
Considerations for CREATE PROCEDURE
Required Privileges
To issue a CREATE PROCEDURE statement, you must be the owner of the schema,
or be the super ID, and have read access to the Java class file or JAR file that contains
the SPJ method.