SQL/MX 3.2.1 Guide to Stored Procedures in Java (H06.26+, J06.15+)

NOTE: Systems running on J06.04 and earlier J-series RVUs or H06.15 and earlier H-series
RVUs have VAILDATEROUTINE internal SPJ only, whereas systems running on J06.05 and
later J-series RVUs or H06.16 and later H-series RVUs have both VALIDATEROUTINE and
VALIDATEROUTINE2 internal SPJs.
Additionally, MXCMP released in H06.16 and later RVUs invokes internal SPJ
VALIDATEROUTINE2 while MXCMP released in H06.15 or earlier RVUs invoke the
VAILDATEROUTINE internal SPJ.
4. The catalog manager inserts information about the SPJ into the system metadata tables:
• The ALL_UIDS table associates the SPJ with a unique identifier (UID).
• The OBJECTS table contains information about each SPJ, such as its object name, unique
identifier (UID), creation time, and ownership.
• The ROUTINES table contains the attributes, such as external name and path, of each
SPJ that is created in a catalog.
• The COLS table contains the attributes of the individual parameters of an SPJ, one row
per parameter.
• The TEXT table contains the text of the Java encoded signature of an SPJ.
• The TBL_PRIVILEGES table contains the ownership and granted privileges for each SPJ in
a catalog.
• The REPLICAS table contains information about the procedure label of an SPJ.
For more information about these system metadata tables, see the SQL/MX Reference Manual.
5. The catalog manager also creates a procedure label owned by the user who issues the CREATE
PROCEDURE statement.
The procedure label is used internally by NonStop SQL/MX to track privileges on an SPJ. For
more information, see Showing the Procedure Label (page 91).
Effect of Invoking an SPJ
When an application issues a CALL statement, the Java method of the invoked SPJ executes inside
a JVM in an SQL/MX UDR server process. Figure 3 shows how SQL/MX processes a CALL statement.
22 Introduction