trafodion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dbirds...@apache.org
Subject [05/14] incubator-trafodion git commit: Backup checkin. The basic edit of the guide has been done. Need to change it to refer to trafci commands to complete.
Date Fri, 08 Apr 2016 18:51:04 GMT
Backup checkin. The basic edit of the guide has been done. Need to change
it to refer to trafci commands to complete.


Project: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/commit/6f5d4cc4
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/tree/6f5d4cc4
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/diff/6f5d4cc4

Branch: refs/heads/master
Commit: 6f5d4cc40b2e3b40e9075cd7c916ec693b11d534
Parents: 10e61eb
Author: Gunnar Tapper <gtapper@esgyn.local>
Authored: Tue Mar 22 23:57:09 2016 -0600
Committer: Gunnar Tapper <gtapper@esgyn.local>
Committed: Tue Mar 22 23:57:09 2016 -0600

----------------------------------------------------------------------
 docs/spj_guide/pom.xml                          |    4 +
 .../spj_guide/src/asciidoc/_chapters/about.adoc |    4 +-
 .../src/asciidoc/_chapters/create_spjs.adoc     |  498 ++--
 .../src/asciidoc/_chapters/deploy_spjs.adoc     |  366 +--
 .../src/asciidoc/_chapters/execute_spjs.adoc    |  595 +++--
 .../asciidoc/_chapters/grant_privileges.adoc    |  229 +-
 .../_chapters/performance_troubleshooting.adoc  |  458 ++--
 .../src/asciidoc/_chapters/sample_database.adoc |  826 +-----
 .../src/asciidoc/_chapters/sample_spjs.adoc     | 2396 ++++++------------
 docs/spj_guide/src/asciidoc/index.adoc          |   23 +-
 .../src/images/call-statement-elements.jpg      |  Bin 0 -> 16652 bytes
 .../src/resources/source/Inventory.java         |  120 +
 .../spj_guide/src/resources/source/Payroll.java |  151 ++
 docs/spj_guide/src/resources/source/Sales.java  |  346 +++
 .../src/resources/source/adjustSalary.java      |   41 +
 .../src/resources/source/employeeJob.java       |   32 +
 .../resources/source/invent_partloc_table.sql   |   56 +
 .../resources/source/invent_partsupp_table.sql  |  128 +
 .../src/resources/source/invent_schema.sql      |    2 +
 .../resources/source/invent_supplier_table.sql  |   35 +
 .../src/resources/source/lowerPrice.java        |   44 +
 .../src/resources/source/numDailyOrders.java    |   29 +
 .../src/resources/source/numMonthlyOrders.java  |   41 +
 .../src/resources/source/orderSummary.java      |   76 +
 .../src/resources/source/partData.java          |  103 +
 .../src/resources/source/partlocations.java     |   42 +
 .../src/resources/source/persnl_dept_table.sql  |   70 +
 .../resources/source/persnl_employee_table.sql  |   99 +
 .../src/resources/source/persnl_job_table.sql   |   20 +
 .../resources/source/persnl_project_table.sql   |   45 +
 .../src/resources/source/persnl_schema.sql      |    2 +
 .../src/resources/source/projectTeam.java       |   25 +
 .../resources/source/sales_customer_table.sql   |   30 +
 .../resources/source/sales_odetail_table.sql    |   84 +
 .../src/resources/source/sales_orders_table.sql |   66 +
 .../src/resources/source/sales_parts_table.sql  |   45 +
 .../src/resources/source/sales_schema.sql       |    2 +
 .../src/resources/source/supplierinfo.java      |   38 +
 .../src/resources/source/supplyquantities.java  |   32 +
 .../src/resources/source/topSalesReps.java      |   43 +
 .../src/resources/source/totalPrice.java        |   47 +
 41 files changed, 3687 insertions(+), 3606 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/6f5d4cc4/docs/spj_guide/pom.xml
----------------------------------------------------------------------
diff --git a/docs/spj_guide/pom.xml b/docs/spj_guide/pom.xml
index d569367..8c2b3b4 100644
--- a/docs/spj_guide/pom.xml
+++ b/docs/spj_guide/pom.xml
@@ -184,6 +184,8 @@
                 <!-- Location of centralized stylesheet -->
                 <stylesheet>${basedir}/../shared/trafodion-manuals.css</stylesheet>
                 <project-version>${env.TRAFODION_VER}</project-version>
+                <project-name>${env.PROJECT_NAME}</project-name>
+                <project-logo>${env.PROJECT_LOGO}</project-logo>
                 <build-date>${maven.build.timestamp}</build-date>
                 <google-analytics-account>UA-72491210-1</google-analytics-account>
               </attributes>
@@ -209,6 +211,8 @@
                 <idprefix/>
                 <idseparator>-</idseparator>
                 <project-version>${env.TRAFODION_VER}</project-version>
+                <project-name>${env.PROJECT_NAME}</project-name>
+                <project-logo>${env.PROJECT_LOGO}</project-logo>
                 <build-date>${maven.build.timestamp}</build-date>
               </attributes>
             </configuration>

http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/6f5d4cc4/docs/spj_guide/src/asciidoc/_chapters/about.adoc
----------------------------------------------------------------------
diff --git a/docs/spj_guide/src/asciidoc/_chapters/about.adoc b/docs/spj_guide/src/asciidoc/_chapters/about.adoc
index c4b69cd..ebf0801 100644
--- a/docs/spj_guide/src/asciidoc/_chapters/about.adoc
+++ b/docs/spj_guide/src/asciidoc/_chapters/about.adoc
@@ -24,7 +24,7 @@
 ////
 
 = About This Document
-This guide describes how to develop, deploy, and manage Stored Procedures in Java (SPJs) on the Trafodion database.
+This guide describes how to develop, deploy, and manage Stored Procedures in Java (SPJs) on the {project-name} database.
 
 == Intended Audience
 This manual is intended for application programmers who are writing and compiling Java code for stored procedures
@@ -50,7 +50,7 @@ and lists steps for developing and deploying SPJs on Trafodion.
 | *<<get-started, Get Started>>*                       | Describes the software requirements for using SPJs on the Trafodion database.
 | *<<develop-spj-methods, Develop SPJ Methods>>*       | Provides guidelines for writing and compiling a Java method to be used as the
 body of a stored procedure.
-| *<<xeploy-spj-jar-files, Deploy SPJ JAR Files>>*     | Explains how to deploy SPJ JAR files on the Trafodion database.
+| *<<deploy-spj-jar-files, Deploy SPJ JAR Files>>*     | Explains how to deploy SPJ JAR files on the Trafodion database.
 | *<<create-spjs, Create SPJs>>*                       | Explains how to create, drop, and alter an SPJ on the Trafodion database.            
 | *<<grant-privileges, Grant Privileges>>*             | Explains how to grant and revoke privileges for executing SPJs on the
 Trafodion database.

http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/6f5d4cc4/docs/spj_guide/src/asciidoc/_chapters/create_spjs.adoc
----------------------------------------------------------------------
diff --git a/docs/spj_guide/src/asciidoc/_chapters/create_spjs.adoc b/docs/spj_guide/src/asciidoc/_chapters/create_spjs.adoc
index 11c2bc1..3a89bad 100644
--- a/docs/spj_guide/src/asciidoc/_chapters/create_spjs.adoc
+++ b/docs/spj_guide/src/asciidoc/_chapters/create_spjs.adoc
@@ -30,13 +30,14 @@ drop a procedure from the Trafodion database, use the HP Database Manager
 
 Follow these procedures:
 
-* link:#_bookmark116["Create a Procedure" (page 37)]
-* link:#_bookmark128["Drop a Procedure" (page 42)]
-* link:#bookmark130["Display Procedures and Their Properties" (page 42)]
+* <<create-a-procedure, Create a Procedure>>
+* <<drop-a-procedure, Drop a Procedure>>
+* <<display-procedures-and-their-properties, Display Procedures and Their Properties>>
+
 This chapter also covers:
-* link:#_bookmark114["Required Privileges for Creating or Dropping an
-SPJ" (page 37)]
-* link:#_bookmark136["Altering an SPJ and Its Java Bytecode" (page 44)]
+
+* <<required-privileges-for-creating-or-dropping-an-spj, Required Privileges for Creating or Dropping an SPJ>>
+* <<altering-an-spj-and-its-java-bytecode, Altering an SPJ and Its Java Bytecode>>
 
 == Required Privileges for Creating or Dropping an SPJ
 
@@ -45,17 +46,16 @@ have the CREATE_PROCEDURE privilege for that schema, and you must have
 the CREATE_PROCEDURE privilege for the SQL_OPERATIONS component. You
 must also have the USAGE privilege for the library that will be used in
 the creation of the stored procedure. For more information, see the
-requirements in link:#_bookmark116["Create a Procedure" (page 37)].
+requirements in <<create-a-procedure, Create a Procedure>>.
 
 To drop an SPJ from a schema, you must be the schema owner, or you must
 have the DROP_PROCEDURE privilege for that schema. For more information,
-see the requirements in link:#_bookmark128["Drop] link:#_bookmark128[a
-Procedure" (page 42)].
+see the requirements in <<drop-a-procedure, Drop a Procedure>>.
 
 To display the current ownership and privileges, see
-link:#bookmark130["Display Procedures and Their Properties"]
-link:#bookmark130[(page 42)].
+<<display-procedures-and-their-properties, Display Procedures and Their Properties>>.
 
+[[create-a-procedure]]
 == Create a Procedure
 
 The Create Procedure tool registers an existing Java method as a stored
@@ -63,292 +63,250 @@ procedure in Java (SPJ) within SQL.
 
 NOTE: HPDM creates procedures with default privileges only. For more
 information about privileges for SPJs, see the Grant/Revoke Privileges
-Tool in HPDM or the GRANT PROCEDURE statement in the __Trafodion SQL
-Reference Manual__.
+Tool in HPDM or the GRANT PROCEDURE statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
 
 Requirements:
 
 * You must have the CREATE_PROCEDURE privilege for the SQL_OPERATIONS
 component. For more information, see the component privileges in the _HP
 Database Manager (HPDM) User Guide_ or the online help in HPDM.
+
 * You must have been granted the USAGE privilege for the library that
 will be used in the creation of the stored procedure. This privilege
 provides you with read access to the library's underlying JAR file,
 which contains the SPJ Java method. For more information, see the
-Grant/Revoke Privileges Tool in HPDM or the GRANT LIBRARY statement in
-the __Trafodion SQL Reference Manual__.
+Grant/Revoke Privileges Tool in HPDM or the GRANT LIBRARY statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
+
 * You must either be the owner of the schema or have the
 CREATE_PROCEDURE privilege for the schema to create the procedure. The
 schema owner can grant such a schema-level privilege to other users or
 roles. For more information, see the Grant/Revoke Privileges Tool in
-HPDM or the GRANT SCHEMA statement in the _Trafodion SQL Reference
-Manual_
+HPDM or the GRANT SCHEMA statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
 
 To create a procedure:
 
 1.  In HPDM, select the Database area.
+
 2.  Expand the navigation tree pane so that you can see the name of the
 schema in which you want to create the procedure and the Procedures
 folder under the schema.
+
 3.  Right-click the Procedures folder, and select Create Procedure. The
 Create Procedure dialog box appears.
+
 4.  In the Procedure Name field, enter a name for the stored procedure.
 For detailed information about the Procedure Name field, see
-link:#_bookmark120["Use the Create Procedure Dialog Box" (page 39)].
-5.  In the Code group box, click [ Browse ] to find a Java method.
+<<use-the-create-procedure-dialog-box, Use the Create Procedure Dialog Box>>.
 
+5.  In the Code group box, click [ Browse ] to find a Java method.
++
 The [ Browse ] button opens Library Browser. Use the browser to select a
-method from a JAR file within a library. See link:#_bookmark109["Use the
-Library Browser" (page 35)]. If a library containing the JAR file does
-not exist on the Trafodion platform, you can create one by clicking the [
-Create ] button in the Library Browser. See link:#_bookmark98["Use the
-Create Library Dialog Box" (page 31)].
+method from a JAR file within a library. See
+<<use-the-library-browser, Use the Library Browser>>. If a library containing the JAR file does
+not exist on the Trafodion platform, you can create one by clicking the
+[ Create ] button in the Library Browser. See
+<<use-the-create-library-dialog-box, Use the Create Library Dialog Box>>.
 
-1.  In the Parameters group box, verify that the SQL parameters are
+6.  In the Parameters group box, verify that the SQL parameters are
 mapped correctly to the Java parameters of the SPJ method.
-
-NOTE: The result set parameters (java.sql.ResultSet[]) in the Java
++
+NOTE: The result set parameters (`java.sql.ResultSet[]`) in the Java
 signature do not have corresponding SQL parameters.
-
++
 a.  To change an SQL parameter, such as the name of the parameter, the
-SQL data type,
-or the parameter mode or direction (IN, INOUT, or OUT), select the
-parameter and click
-
-[ Edit ]. The Edit Parameter dialog box appears.
-
-a.  In the Edit Parameter dialog box, enter a new name for the
+SQL data type, or the parameter mode or direction (IN, INOUT, or OUT), select the
+parameter and click [ Edit ]. The Edit Parameter dialog box appears.
++
+b.  In the Edit Parameter dialog box, enter a new name for the
 parameter, select a different SQL data type, if permitted, or select a
 different parameter mode (direction), if permitted.
-
++
 When changing the parameter name, note that the parameter name:
-
++
 * Is not case-sensitive
 * Must not be a reserved word
 * Must not contain spaces
 * Must begin with a letter, digit, or underscore
-
++
 When changing the SQL data type, select a data type that is appropriate
 for the parameter of the underlying Java method. For information about
-SQL data types, see the __Trafodion SQL Reference Manual__.
-
+SQL data types, see the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
++
+////
 For character string parameters, select either ISO88591 or UCS2
 depending on the column definition in the database. For guidelines, see
 the __Trafodion Character Sets Guide__.
+////
++
+c.  Click [ OK ] to accept the changes, or click [ Cancel ] to quit the Edit Parameter dialog box.
++
+d.  Repeat steps a to c for each parameter that you want to change.
 
-a.  Click [ OK ] to accept the changes, or click [ Cancel ] to quit the
-Edit Parameter dialog box.
-b.  Repeat steps a to c for each parameter that you want to change.
-
-1.  In the Attributes group box, if your SPJ method returns result sets,
+7.  In the Attributes group box, if your SPJ method returns result sets,
 enter the maximum number of result sets to be returned for Number of
 dynamic result sets. The valid range is 1 to 255 inclusive. The actual
 number of result sets returned by the SPJ method can be less than or
 equal to this number.
-
++
 NOTE: The Number of dynamic result sets control is enabled only if the
 method signature contains a java.sql.ResultSet[] object.
 
-1.  If your SPJ method performs any SQL operations, select the Accesses
+8.  If your SPJ method performs any SQL operations, select the Accesses
 Database option.
-
++
 NOTE: If you do not select the Accesses Database option and your SPJ
 method performs SQL operations, SQL returns an error when trying to
 execute the procedure.
 
-1.  Select either Invoker or Definer for the external security of the
+9.  Select either Invoker or Definer for the external security of the
 stored procedure.
-
++
 * The Invoker setting determines that users can execute, or invoke, the
 stored procedure using the privileges of the user who invokes the stored
-procedure. This behavior is referred to as __invoker rights__.
+procedure. This behavior is referred to as _invoker rights_.
++
 * The Definer setting determines that users can execute, or invoke, the
 stored procedure using the privileges of the user who created the stored
-procedure. This behavior is referred to as __definer rights__. The
+procedure. This behavior is referred to as _definer rights_. The
 advantage of definer rights is that users are allowed to manipulate data
 by invoking the stored procedure without having to be granted privileges
 to the underlying database objects.
++
+For more information, see <<understand-external-security, Understand External Security>>.
 
-For more information, see link:#_bookmark124["Understand External
-Security" (page 41)].
-
-1.  For the Transaction Required attribute, select either Yes to require
+10.  For the Transaction Required attribute, select either Yes to require
 the procedure to run in a transaction inherited from the calling
 application (the default behavior) or No to allow the procedure to run
 without an inherited transaction. For more information, see
-link:#_bookmark157["Transaction] link:#_bookmark157[Behavior" (page
-49)].
-2.  Click [ Create ] to create the procedure.
+<<transaction-behavior, Transaction Behavior>>.
 
-Related Topics
-
-link:#_bookmark120["Use the Create Procedure Dialog Box" (page 39)]
+11.  Click [ Create ] to create the procedure.
 
 == Use the Create Procedure Dialog Box
 
 This table shows reference information for the Create Procedure dialog
 box:
 
-[cols=",,",options="header",]
+[cols="20%,30%,50%",options="header",]
 |===
-Group Box
-Control or Field
-Action
-Name
-____
-
-Catalog
-Name of the catalog where the procedure will be created. This is a
-read-only field.
-Schema
-Name of the schema where the procedure will be created. This is a
-read-only field.
-Procedure Name
-Enter a name for the procedure. The name must be unique and must not
+| Group Box   | Control or Field | Action
+| *Name*      | Catalog          | Name of the catalog where the procedure is created. This is a read-only field.
+|             | Schema           | Name of the schema where the procedure is created. This is a read-only field.
+|             | Procedure Name   | Enter a name for the procedure. The name must be unique and must not
 exist for any procedure, table, or view in the same schema. The
 procedure name is not case-sensitive. The database engine automatically
 qualifies the procedure name with the name of the catalog and schema in
-which you are creating the procedure. For example, if you enter
-*monthlyorders* as the procedure name, the database engine stores the
-procedure as
-
-__catalog-name__.__schema-name__.MONTHLYORDERS.
-Code
-Library
-Click [ Browse ] to navigate to a library or JAR file.
-Class Name
-Select a class.
-Method Name
-When you select a class, the method names and parameter types for that
-class appear in the right pane.
+which you are creating the procedure. +
+ +
+For example, if you enter *monthlyorders* as the procedure name, the database engine stores the
+procedure as `_catalog-name_._schema-name_.MONTHLYORDERS`.
+| *Code*      | Library          | Click [ Browse ] to navigate to a library or JAR file.
+|             | Class Name       | Select a class.
+|             | Method Name      | When you select a class, the method names and parameter types for that
+class appear in the right pane. +
+ +
 NOTE: Only methods that can be used in a procedure are visible. For
-details, see link:#_bookmark123["Use a Method in a Procedure" (page
-40)].
-Parameters
-Name
-____
-
-Is the name for this SQL parameter.
-Direction
-IN passes data to a procedure
-INOUT passes data to and accepts data from a procedure. The parameter
-|===
-
-must be an array.
-
-
-* OUT accepts data from a procedure. The parameter must be an array.
-
-SQL Data Type
-
-Displays the SQL data type that is the best match for the Java signature
-in the
-
-Java Data Type column.
-
-Java Data Type Displays the signature for the Java method that you
-selected.
-
-[ Edit ] Click to edit the selected parameter.
-
-Group Box
-
-Control or Field
-
-Action
-
-Attributes
-
-Number of dynamic result sets
-
-Accesses Database
-
-Controls the maximum number of result sets the procedure can return.
-This control is enabled only if the method signature contains a
-java.sql.ResultSet[] object. If the method contains a result set object,
-the valid range is 1 to 255. This value is automatically set to zero if
-the selected Java method does not have a java.sql.ResultSet[] object.
-
-If selected, the procedure performs SQL operations. If cleared, the
-procedure does not perform SQL operations.
-
+details, see <<use-a-method-in-a-procedure, Use a Method in a Procedure>>.
+| *Parameters* | Name            | Is the name for this SQL parameter.
+|              | Direction       | 
+- IN passes data to a procedure +
+- INOUT passes data to and accepts data from a procedure. The parameter must be an array. +
+- OUT accepts data from a procedure. The parameter must be an array.
+|              | SQL Data Type   | Displays the SQL data type that is the best match for the Java signature in the Java Data Type column.
+|              | Java Data Type  | Displays the signature for the Java method that you selected.
+|              | [ Edit ]        | Click to edit the selected parameter.
+| *Attributes* | Number of dynamic result sets | Controls the maximum number of resulat sets the procedure can return. +
+ +
+This control is enabled only if the method signature contains a `java.sql.ResultSet[]` object. +
+ +
+If the method contains a result set object, then the valid range is 1 to 255. +
+ +
+ This value is automatically set to zero if the selected Java method does not have a `java.sql.ResultSet[]` object.
+|              | Accesses Database | If selected, then the procedure performs SQL operations.
+If cleared, then the procedure does not perform SQL operations. +
+ +
 NOTE: SQL returns an error when trying to execute the procedure if this
 attribute is cleared and the procedure performs SQL operations.
-
-External Security
-
-Transaction Required
-
-Select either Invoker or Definer for the external security of the stored
-procedure.
-
-* The Invoker setting determines that users can execute, or invoke, the
+|              | External Security |  Select either Invoker or Definer for the external security of the stored procedure. +
+ +
+- The Invoker setting determines that users can execute, or invoke, the
 stored procedure using the privileges of the user who invokes the stored
-procedure. This behavior is referred to as __invoker rights__.
+procedure. This behavior is referred to as _invoker rights_. +
+ +
 * The Definer setting determines that users can execute, or invoke, the
 stored procedure using the privileges of the user who created the stored
-procedure. This behavior is referred to as __definer rights__. The
+procedure. This behavior is referred to as _definer rights_. The
 advantage of definer rights is that users are allowed to manipulate data
 by invoking the stored procedure without having to be granted privileges
-to the underlying database objects.
-
-For more information, see link:#_bookmark124["Understand External
-Security" (page 41)].
-
+to the underlying database objects. +
+ +
+For more information, see <<understand-external-security, Understand External Security>>.
+|               | Transaction Required |
 Select either Yes to require the procedure to run in a transaction
 inherited from the calling application (the default behavior) or No to
 allow the procedure to run without an inherited transaction. For more
-information, see link:#_bookmark157["Transaction]
-link:#_bookmark157[Behavior" (page 49)].
+information, see <<transaction-behavior, Transaction Behavior>>.
+|===
 
-Related Topics
+*Related Topics*
 
-link:#_bookmark116["Create a Procedure" (page 37)]
+* <<create-a-procedure, Create a Procedure>>
 
+[[use-a-method-in-a-procedure]]
 == Use a Method in a Procedure
 
 To be used in a procedure, a Java method must:
 
 * Be qualified as public static void.
-* Have a java.sql.ResultSet[] parameter at the end of the method
-signature if the method uses result sets.
-
-NOTE: There can be more than one java.sql.ResultSet[] parameter, but
-they must all be at the end of the method signature.
+* Have a `java.sql.ResultSet[]` parameter at the end of the method signature if the method uses result sets.
++
+NOTE: There can be more than one java.sql.ResultSet[] parameter, but they must all be at the end of the method signature.
 
 * Have these parameter types:
++
+[cols="40%,60%", options="header"]
+|===
+| Parameter Type or Class | Type
+| 
+| *character*             |
+`java.lang.String` +
+`java.lang.String[]`
+| *numeric*               |
+`java.lang.Integer` +
+`java.lang.Integer[]` +
+`java.lang.Long` +
+`java.lang.Long[]` +
+`java.lang.Float` +
+`java.lang.Float[]` +
+`java.lang.Double` +
+`java.lang.Double[]` +
+`java.math.BigDecimal` +
+`java.math.BigDecimal[]`
+| *date/timestamp*        |
+`java.sql.Date` +
+`java.sql.Date[]` +
+`java.sql.Time` +
+`java.sql.Time[]` +
+`java.sql.Timestamp` +
+`java.sql.Timestamp[]`
+| *primitive short*       | 
+`short[]` +
+`int` +
+`int[]` +
+`long` +
+`long[]` +
+`float` +
+`float[]`+
+`double` +
+`double[]`
+| *result sets* | `java.sql.ResultSet[]`
+|===
 
-Parameter Type or Class
-
-Type
-
-character java.lang.String
-
-java.lang.String[]
-
-numeric java.lang.Integer
-
-java.lang.Integer[] java.lang.Long java.lang.Long[] java.lang.Float
-java.lang.Float[]
-
-Parameter Type or Class
-
-Type
-
-java.lang.Double java.lang.Double[] java.math.BigDecimal
-java.math.BigDecimal[]
-
-date/timestamp java.sql.Date
-
-java.sql.Date[] java.sql.Time java.sql.Time[] java.sql.Timestamp
-java.sql.Timestamp[]
-
-primitive short
-
-short[] int int[] long long[] float float[] double double[]
-
-result sets java.sql.ResultSet[]
-
+[[understand-external-security]]
 == Understand External Security
 
 The external security of an SPJ determines the privileges, or rights,
@@ -356,133 +314,121 @@ that users have when executing (or calling) the SPJ. An SPJ can be
 created with one of these types of external security: invoker or
 definer.
 
-If an SPJ is created with the invoker type of external security, the SPJ
-is executed with __invoker rights__. Invoker rights allow a user who has
-the execute privilege on the SPJ to call the SPJ using his or her
-existing privileges. In this case, the user must be granted privileges
-to access the underlying database objects on which the SPJ operates. If
-a user tries to call an SPJ that has invoker external security and that
-operates on database objects to which the user does not have privileges,
-the CALL statement fails with an error message indicating that the user
-does not have the appropriate permissions. Note: Granting a user
-privileges to the underlying database objects gives the user direct
-access to those database objects, which could pose a risk to more
+If an SPJ is created with the invoker type of external security, then the SPJ
+is executed with _invoker rights_.
+
+Invoker rights allow a user who has the execute privilege on the SPJ to call
+the SPJ using his or her existing privileges.
+
+In this case, the user must be granted privileges to access the underlying
+database objects on which the SPJ operates. If a user tries to call an SPJ
+that has invoker external security and that operates on database objects to
+which the user does not have privileges, then the CALL statement fails with
+an error message indicating that the user does not have the appropriate permissions.
+
+NOTE: Granting a user privileges to the underlying database objects gives the
+user direct access to those database objects, which could pose a risk to more
 sensitive or critical data to which users should not have access. For
 example, an SPJ might operate on a subset of the data in an underlying
 database object, but that database object might contain other more
 sensitive or critical data to which users should not have access.
 
-If an SPJ is created with the definer type of external security, the SPJ
-is executed with __definer rights__. Definer rights allow a user who has
-the execute privilege on an SPJ to call the SPJ using the privileges of
-the user who created the SPJ. In this case, the user does not require
-privileges to access the underlying database objects on which the SPJ
-operates. Instead, the user is allowed to access or manipulate data in
-the underlying database objects by invoking the SPJ. That way, users are
-restricted from directly accessing or manipulating more sensitive or
-critical data in the database. However, be careful about the users to
-whom you grant execute privilege on an SPJ with definer external
-security because those users will be able to execute the SPJ without
-requiring privileges to the underlying database objects.
-
-To set the external security of an SPJ, see link:#_bookmark116["Create a
-Procedure" (page 37)].
+If an SPJ is created with the definer type of external security, then the
+SPJ is executed with _definer rights_.
+
+Definer rights allow a user who has the execute privilege on an SPJ to
+call the SPJ using the privileges of the user who created the SPJ.
+
+In this case, the user does not require privileges to access the underlying
+database objects on which the SPJ operates. Instead, the user is allowed to
+access or manipulate data in the underlying database objects by invoking the
+SPJ. That way, users are restricted from directly accessing or manipulating
+more sensitive or critical data in the database.
 
+However, be careful about the users to whom you grant execute privilege on
+an SPJ with definer external security because those users will be able to
+execute the SPJ without requiring privileges to the underlying database objects.
+
+To set the external security of an SPJ, see <<create-a-procedure, Create a Procedure>>.
+
+[[drop-a-procedure]]
 == Drop a Procedure
 
 To drop a procedure, you must own the procedure or have the
 DROP_PROCEDURE privilege for the schema. The schema owner can grant such
-a schema-level privilege to other users or roles. For example, if the
-schema owner granted you privileges to drop all objects in the schema,
-you could drop procedures. For more information, see the Grant/Revoke
-Privileges Tool in HPDM or the GRANT SCHEMA statement in the __Trafodion
-SQL Reference Manual__.
+a schema-level privilege to other users or roles.
+
+For example, if the schema owner granted you privileges to drop all objects in the schema,
+you could drop procedures. For more information, see the GRANT SCHEMA statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual]
 
 To drop a procedure:
 
 1.  Under the navigation tree pane, click the Database area.
+
 2.  Under My Systems, expand the tree for the Trafodion platform
 containing the procedure until you can see the schema folder and the
 Procedures folder underneath it.
+
 3.  Expand the Procedures folder.
+
 4.  Right-click the name of the procedure that you want to drop, and
 select Drop Procedure. HPDM asks you to confirm the operation.
+
 5.  Click [ Yes ] to continue or [ No ] to quit the operation.
 
+[[display-procedures-and-their-properties}}
 == Display Procedures and Their Properties
 
-To display the SPJs in a schema, use either HPDM or trafci:
-
-* link:#_bookmark131["Using HPDM to Display a Procedure in a Schema"
-(page 42)]
-* link:#_bookmark133["Using trafci to Display Procedures in a Schema"
-(page 43)]
-
-=== Using HPDM to Display a Procedure in a Schema
-
-To display one of the procedures in a schema:
-
-1.  Start the HP Database Manager and log on using any user name.
-2.  Click the Database area.
-3.  In the navigation tree pane, select a Schema, and expand the schema
-so that you can see the object folders underneath it.
-4.  Expand the Procedures tab in the right pane and select a procedure
-name, or open the Procedures folder and select a procedure name in the
-tree. HPDM displays the properties of the selected procedure in the
-right pane.
-
-image:media/image7.jpeg[image]
-
-For more information about the procedure properties displayed in HPDM,
-see the _HP Database_ __Manager (HPDM) User Guide__ or the online help
-in HPDM.
-
-==== Using trafci to Display Procedures in a Schema
-
 In the trafci command-line interface, use the SHOW PROCEDURES command to
 display the procedures in a schema. For example, this SHOW PROCEDURES
 command displays a list of the procedures in the SALES schema:
 
-```
-SQL>**set schema demo.sales;**
+[source, sql]
+----
+SQL> SET SCHEMA demo.sales ;
 
---- SQL operation complete. SQL>**show procedures** PROCEDURE NAMES
+--- SQL operation complete.
 
+SQL> SHOW PROCEDURES
+
+PROCEDURE NAMES
 --------------------------------------------------------------------------------
 DAILYORDERS LOWERPRICE MONTHLYORDERS ORDERSUMMARY PARTDATA TOTAL PRICE
 
 SQL>
-```
+----
 
 You can also use a wild-card pattern to search for a particular
 procedure. For example, this SHOW PROCEDURES command displays all the
 procedures in the SALES schema that have price in their names:
 
-```
-SQL>**show procedures %price**
+[source, sql]
+----
+SQL> SHOW PROCEDURES %price
 
 PROCEDURE NAMES
-
 --------------------------------------------------------------------------------
 LOWERPRICE TOTALPRICE
 
 SQL>
-```
+----
 
-For more information about trafci, see the __HP Database Command
-Interface (trafci) Guide__.
+For more information about trafci, see the
+http://trafodion.apache.org/docs/command_interface/index.html[Trafodion Command Interface Guide].
 
-==== Altering an SPJ and Its Java Bytecode
+[[altering-an-spj-and-its-java-bytecode]]
+=== Altering an SPJ and Its Java Bytecode
 
 Occasionally, you might need to update an SPJ or its Java bytecode. The
 Java bytecode includes the SPJ's class file and any associated class
-files that are packaged in the SPJ JAR file. Suppose that you want to
-update the Java bytecode of an SPJ without changing the class name,
-method name, or Java signature of the SPJ method. In this case, you
-would alter the library by selecting the updated JAR file to upload to
-the Trafodion platform, replacing the previous JAR file for the library.
-For more information, see link:#_bookmark100["Alter a Library" (page
-32)].
+files that are packaged in the SPJ JAR file.
+
+Suppose that you want to update the Java bytecode of an SPJ without
+changing the class name, method name, or Java signature of the SPJ method.
+In this case, you would alter the library by selecting the updated JAR file
+to upload to the Trafodion database, replacing the previous JAR file for the
+library. For more information, see <<alter-a-library, Alter a Library>>.
 
 NOTE: You are prevented from uploading a JAR file that is already in use
 by another library in the catalog. This restriction prevents you from
@@ -492,11 +438,11 @@ If you plan to use a JAR file that contains an SPJ method that has a
 different class name, method name, or signature than the original SPJ
 method, you must drop the SPJ from the database before altering the
 library. After altering the library, re-create the SPJ in the database.
+
 You must also drop and re-create an SPJ to rename the procedure or
 change the SQL parameter definitions even if the Java bytecode remains
-the same. For more information, see link:#_bookmark116["Create a
-Procedure" (page 37)] and link:#_bookmark128["Drop a Procedure" (page
-42)].
+the same. For more information, see <<create-a-procedure, Create a Procedure>> and
+<<drop-a-procedure, Drop a Procedure>>.
 
 When you update an SPJ or its Java bytecode, try to avoid making those
 changes when client applications are actively calling the SPJ. If you

http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/6f5d4cc4/docs/spj_guide/src/asciidoc/_chapters/deploy_spjs.adoc
----------------------------------------------------------------------
diff --git a/docs/spj_guide/src/asciidoc/_chapters/deploy_spjs.adoc b/docs/spj_guide/src/asciidoc/_chapters/deploy_spjs.adoc
index 67fed93..d3ca8e0 100644
--- a/docs/spj_guide/src/asciidoc/_chapters/deploy_spjs.adoc
+++ b/docs/spj_guide/src/asciidoc/_chapters/deploy_spjs.adoc
@@ -20,7 +20,7 @@
  */
 ////
 
-[[Deploy-spj-jar-files]]
+[[deploy-spj-jar-files]]
 = Deploy SPJ JAR Files
 
 After developing and packaging the SPJ code into JAR files, you must
@@ -40,7 +40,7 @@ to deploy JAR files.
 See these instructions:
 
 * <<create-a-library, Create a Library>>
-* <alter-a-library, Alter a Library>>
+* <<alter-a-library, Alter a Library>>
 * <<drop-a-library, Drop a Library>>
 * <<download-a-jar-file-from-a-library, Download a JAR File From a Library>>
 * <<display-libraries-and-their-properties, Display Libraries and Their Properties>>
@@ -56,7 +56,7 @@ library, and you must have the required privileges for creating
 libraries in order to deploy a JAR file. To create a library in a
 schema, you must have both the CREATE_LIBRARY component privilege and
 the CREATE_LIBRARY schema-level privilege for the schema. For more
-information, see the requirements in <create-a-library, Create a Library>>.
+information, see the requirements in <<create-a-library, Create a Library>>.
 
 To alter a library in a schema, you must have both the UPDATE privilege
 for the library and the ALTER_LIBRARY privilege for the schema. For more
@@ -94,8 +94,8 @@ library or have the CREATE_LIBRARY privilege for the schema to create
 the library. The schema owner can grant such a schema-level privilege to
 other users or roles. For more information, see the
 
-Grant/Revoke Privileges Tool in HPDM or the GRANT SCHEMA statement in
-the __Trafodion SQL Reference Manual__.
+Grant/Revoke Privileges Tool in HPDM or the GRANT SCHEMA statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
 
 * The JAR file that you select for the library must contain valid Java
 bytecode and must not be used by another library in the catalog.
@@ -103,10 +103,8 @@ bytecode and must not be used by another library in the catalog.
 threshold if one has been set for HPDM's internal WMS service, the data
 source, or the system defaults.
 
-For example, if the CONTROL QUERY DEFAULT (CQD),
-POS_ABSOLUTE_MAX_TABLE_SIZE,
-
-has been set for the HPS_MANAGEABILITY service, it will limit the size
+For example, if the CONTROL QUERY DEFAULT (CQD) `POS_ABSOLUTE_MAX_TABLE_SIZE`
+has been set for the `HPS_MANAGEABILITY` service, it limits the size
 of JAR files that can be uploaded by HPDM. If the JAR file's size
 exceeds the threshold, a warning message is displayed, and the file is
 not uploaded. By default, this CQD is not set for HPDM's internal WMS
@@ -120,47 +118,45 @@ To upload a JAR file and create a library for the JAR file in a schema:
 of the schema where you want to create the library.
 3.  Right-click the Libraries folder, and select Create Library. The
 Create Library dialog box appears. For more information, see
-link:#_bookmark98["Use the Create Library Dialog Box" (page 31)].
+<<use-the-create-library-dialog-box, Use the Create Library Dialog Box>>.
 4.  In the Create Library dialog box, enter a name for the library.
-
++
 The name must be unique among the libraries in the schema and must not
-exceed 128 characters. The library name is not case-sensitive. For
-example, if you enter Payroll as the library name, the database engine
-stores the library as
-
-__catalog-name__.__schema-name__.PAYROLL. The database engine
+exceed 128 characters. The library name is not case-sensitive.
++
+For example, if you enter `Payroll` as the library name, the database engine
+stores the library as `_catalog-name_._schema-name_.PAYROLL`. The database engine
 automatically qualifies the library name with the name of the catalog
 and schema in which you are creating the library.
 
-1.  Click the [ Browse ] button to locate and select a JAR file on the
-client workstation. The "Select a code file" dialog box appears.
-2.  In the "Select a code file" dialog box, locate and select the JAR
+5.  Click the [ Browse ] button to locate and select a JAR file on the
+client workstation. The *Select a code file* dialog box appears.
+
+6.  In the *Select a code file* dialog box, locate and select the JAR
 file on the client workstation, and click [ Open ] to return to the
 Create Library dialog box. The Create Library dialog box displays the
 full path of the JAR file in the Code File field.
-3.  Click [ Create ] to create the library, or click [ Close ] to quit
-the dialog box without creating the library.
 
+7.  Click [ Create ] to create the library, or click [ Close ] to quit
+the dialog box without creating the library.
++
 If you click [ Create ], HPDM validates the JAR file, uploads the JAR
 file, and creates a library for the JAR file in the schema.
 
-1.  When notified that the library was created successfully, click [ OK
-].
-2.  To upload another JAR file and create a library, repeat steps 4
+8.  When notified that the library was created successfully, click [ OK ].
+9.  To upload another JAR file and create a library, repeat steps 4
 through 8.
-3.  When you are done uploading JAR files and creating libraries, click
-the [ Close ] button image:media/image4.png[image]) to quit the Create
+10.  When you are done uploading JAR files and creating libraries, click
+the [ Close ] button to quit the Create
 Library dialog box and return to the HPDM main window.
 
-Related Topics
-
-link:#_bookmark98["Use the Create Library Dialog Box" (page 31)]
-link:#_bookmark100["Alter a Library" (page 32)]
-
-link:#_bookmark105["Drop a Library" (page 33)]
+*Related Topics*
 
-link:#_bookmark107["Download a JAR File From a Library" (page 34)]
-link:#_bookmark110["Display Libraries and Their Properties" (page 36)]
+* <<use-the-create-library-dialog-box, Use the Create Library Dialog Box>>
+* <<alter-a-library, Alter a Library>>
+* <<drop-a-library, Drop a Library>>
+* <<download-a-jar-file-from-a-library, Download a JAR File From a Library>>
+* <<display-libraries-and-their-properties, Display Libraries and Their Properties>>
 
 [[use-the-create-library-dialog-box]]
 == Use the Create Library Dialog Box
@@ -174,98 +170,83 @@ Requirements:
 * You must have the CREATE_LIBRARY privilege for the SQL_OPERATIONS
 component. For more information, see the component privileges in the _HP
 Database Manager (HPDM) User Guide_ or the online help in HPDM.
+
 * You must either be the owner of the schema where you will create the
 library or have the CREATE_LIBRARY privilege for the schema to create
 the library. The schema owner can grant such a schema-level privilege to
 other users or roles. For more information, see the Grant/Revoke
-Privileges Tool in HPDM or the GRANT SCHEMA statement in the __Trafodion
-SQL Reference Manual__.
+Privileges Tool in HPDM or the GRANT SCHEMA statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html[Trafodion SQL Reference Manual].
+
 * The JAR file that you select for the library must contain valid Java
 bytecode and must not be used by another library in the catalog.
+
 * The JAR file that you select for the library must not exceed a size
 threshold if one has been set for HPDM's internal WMS service, the data
 source, or the system defaults.
 
-For example, if the CONTROL QUERY DEFAULT (CQD),
-POS_ABSOLUTE_MAX_TABLE_SIZE,
-
+For example, if the CONTROL QUERY DEFAULT (CQD) `POS_ABSOLUTE_MAX_TABLE_SIZE`
 has been set for the HPS_MANAGEABILITY service, it will limit the size
-of JAR files that can be uploaded by HPDM. If the JAR file's size
-exceeds the threshold, a warning message is displayed, and the file is
-not uploaded. By default, this CQD is not set for HPDM's internal WMS
+of JAR files that can be uploaded by HPDM.
+
+If the JAR file's size exceeds the threshold, then a warning message is displayed,
+and the file is not uploaded. By default, this CQD is not set for HPDM's internal WMS
 service, the data source, or the system defaults, and HPDM allows you to
 upload JAR files of any size.
 
-[cols=",,",options="header",]
+[cols="20%,30%,50%",options="header",]
 |===
-[[group-box]]
-Group Box
-Control or Field
-Description or Action
-Library
-Catalog
-Name of the catalog where the library will be created. This is a
-read-only field.
-Schema
-Name of the schema where the library will be created. This is a
-read-only field.
-Library Name
-Enter a name for the library. The name must be unique among the
-libraries in the schema and must not exceed 128 characters. The library
-name is not case-sensitive. For example, if you enter Payroll as the
-library name, the database engine stores the library as
-
-__catalog-name__.__schema-name__.PAYROLL. The database engine
-automatically qualifies the library name with the name of the catalog
-and schema in which you are creating the library.
-Code File
-Code File
-Click [ Browse ] to launch the "Select a code file" dialog box and
+| Group Box    | Control or Field | Description or Action
+| *Library*    | Catalog          | Name of the catalog where the library is created. This is a read-only field.
+|              | Schema           | Name of the schema where the library is created. This is a read-only field.
+|              | Library Name     | Enter a name for the library. The name must be unique among the  libraries
+in the schema and must not exceed 128 characters. The library name is not case-sensitive. +
+ +
+For example, if you enter Payroll as the library name, the database engine stores the library as
+`_catalog-name_._schema-name_.PAYROLL`. The database engine automatically qualifies the library name with the
+name of the catalog and schema in which you are creating the library.
+| *Code File* | Code File         | Click [ Browse ] to launch the *Select a code file* dialog box and
 navigate to a JAR file on the client workstation.
-[ Create ]
-Creates the library.
-[ Close ]
-Closes the dialog box without creating a library.
-[ Help ]
-Displays context-sensitive help for this dialog box.
+|             | [ Create ]        | Creates the library.
+|             | [ Close ]         | Closes the dialog box without creating a library.
+|             | [ Help ]          | Displays context-sensitive help for this dialog box.
 |===
 
-[[related-topics]]
-Related Topics
-
-link:#_bookmark95["Create a Library" (page 29)]
-link:#_bookmark100["Alter a Library" (page 32)] link:#_bookmark105["Drop
-a Library" (page 33)]
+*Related Topics*
 
-link:#_bookmark107["Download a JAR File From a Library" (page 34)]
+* <<create-a-library, Create a Library>>
+* <<alter-a-library, Alter a Library>>
+* <<drop-a-library, Drop a Library>>
+* <<download-a-jar-file-from-a-library, Download a JAR File From a Library>>
 
 [[alter-a-library]]
 == Alter a Library
 
-When you alter a library, you can change the underlying JAR file of the
-library.
+When you alter a library, you can change the underlying JAR file of the library.
 
 Requirements:
 
 * You must have been granted the UPDATE privilege for the library. For
 more information, see the Grant/Revoke Privileges Tool in HPDM or the
-GRANT LIBRARY statement in the __Trafodion SQL Reference Manual__.
-* You must either be the owner of the schema where you will alter the
+GRANT LIBRARY statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
+
+* You must either be the owner of the schema where you're altering the
 library or have the ALTER_LIBRARY privilege for the schema to alter the
 library. The schema owner can grant such a schema-level privilege to
 other users or roles. For more information, see the Grant/Revoke
-Privileges Tool in HPDM or the GRANT SCHEMA statement in the __Trafodion
-SQL Reference Manual__.
+Privileges Tool in HPDM or the GRANT SCHEMA statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
+
 * The JAR file that you select for the library must contain valid Java
 bytecode and must not be used by another library in the catalog.
+
 * The JAR file that you select for the library must not exceed a size
 threshold if one has been set for HPDM's internal WMS service, the data
 source, or the system defaults.
 
-For example, if the CONTROL QUERY DEFAULT (CQD),
-POS_ABSOLUTE_MAX_TABLE_SIZE,
-
-has been set for the HPS_MANAGEABILITY service, it will limit the size
+For example, if the CONTROL QUERY DEFAULT (CQD) `POS_ABSOLUTE_MAX_TABLE_SIZE`
+has been set for the HPS_MANAGEABILITY service, then it limits the size
 of JAR files that can be uploaded by HPDM. If the JAR file's size
 exceeds the threshold, a warning message is displayed, and the file is
 not uploaded. By default, this CQD is not set for HPDM's internal WMS
@@ -282,18 +263,20 @@ to display the libraries within it.
 you selected a system library, a dialog box appears warning you that you
 cannot alter a system library. If you selected a user library, the Alter
 Library dialog box appears. For more information, see
-link:#_bookmark103["Use the Alter] link:#_bookmark103[Library Dialog
-Box" (page 33)].
+<<use-the-alter-library-dialog-box, Use the Alter Library Dialog Box>>.
+
 4.  In the Alter Library dialog box, click the [ Browse ] button to
-locate and select a new JAR file on the client workstation. The "Select
-a code file" dialog box appears.
-5.  In the "Select a code file" dialog box, locate and select the JAR
+locate and select a new JAR file on the client workstation. The *Select
+a code file* dialog box appears.
+
+5.  In the *Select a code file* dialog box, locate and select the JAR
 file on the client workstation, and click [ Open ] to return to the
 Alter Library dialog box. The Alter Library dialog box displays the full
 path of the new JAR file in the Code File field.
+
 6.  Click [ Alter ] to alter the library, or click [ Close ] to quit the
 dialog box without altering the library.
-
++
 If you click [ Alter ], a dialog box appears warning you that altering a
 library might affect stored procedures that use the library and asking
 if you wish to continue the alter operation. Click [ Yes ] to proceed,
@@ -301,19 +284,17 @@ or click [ No ] to cancel the operation. If you click [ Yes ], HPDM
 validates the JAR file, uploads the JAR file, and alters the library in
 the schema.
 
-1.  When notified that the library was altered successfully, click [ OK
-] to close the Alter Library dialog box and return to the HPDM main
+7.  When notified that the library was altered successfully, click
+[ OK ] to close the Alter Library dialog box and return to the HPDM main
 window.
 
-Related Topics
-
-link:#_bookmark103["Use the Alter Library Dialog Box" (page 33)]
-link:#_bookmark95["Create a Library" (page 29)]
+*Related Topics*
 
-link:#_bookmark105["Drop a Library" (page 33)]
-
-link:#_bookmark107["Download a JAR File From a Library" (page 34)]
-link:#_bookmark110["Display Libraries and Their Properties" (page 36)]
+* <<use-the-alter-library-dialog-box, Use the Alter Library Dialog Box>>
+* <<create-a-library, Create a Library>>
+* <<drop-a-library, Drop a Library>>
+* <<download-a-jar-file-from-a-library, Download a JAR File From a Library>>
+* <<display-libraries-and-their-properties, Display Libraries and Their Properties>>
 
 [[use-the-alter-library-dialog-box]]
 == Use the Alter Library Dialog Box
@@ -325,65 +306,53 @@ Requirements:
 
 * You must have been granted the UPDATE privilege for the library. For
 more information, see the Grant/Revoke Privileges Tool in HPDM or the
-GRANT LIBRARY statement in the __Trafodion SQL Reference Manual__.
+GRANT LIBRARY statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
+
 * You must either be the owner of the schema where you will alter the
 library or have the ALTER_LIBRARY privilege for the schema to alter the
 library. The schema owner can grant such a schema-level privilege to
 other users or roles. For more information, see the Grant/Revoke
-Privileges Tool in HPDM or the GRANT SCHEMA statement in the __Trafodion
-SQL Reference Manual__.
+Privileges Tool in HPDM or the GRANT SCHEMA statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
+
 * The JAR file that you select for the library must contain valid Java
 bytecode and must not be used by another library in the catalog.
+
 * The JAR file that you select for the library must not exceed a size
 threshold if one has been set for HPDM's internal WMS service, the data
 source, or the system defaults.
-
-For example, if the CONTROL QUERY DEFAULT (CQD),
-POS_ABSOLUTE_MAX_TABLE_SIZE,
-
-has been set for the HPS_MANAGEABILITY service, it will limit the size
++
+For example, if the CONTROL QUERY DEFAULT (CQD) `POS_ABSOLUTE_MAX_TABLE_SIZE`
+has been set for the HPS_MANAGEABILITY service, then it limits the size
 of JAR files that can be uploaded by HPDM. If the JAR file's size
 exceeds the threshold, a warning message is displayed, and the file is
-not uploaded. By default, this CQD is not set for HPDM's internal WMS
+not uploaded.
++
+By default, this CQD is not set for HPDM's internal WMS
 service, the data source, or the system defaults, and HPDM allows you to
 upload JAR files of any size.
 
 
-[cols=",,",options="header",]
+[cols="20%,30%,50%",options="header",]
 |===
-[[group-box]]
-Group Box
-Control or Field
-Description or Action
-Library
-Catalog
-Name of the catalog where the library will be created. This is a
-read-only field.
-Schema
-Name of the schema where the library will be created. This is a
-read-only field.
-Library Name
-Name of the library. This is a read-only field.
-Code File
-Code File
-Click [ Browse ] to launch the "Select a code file" dialog box and
+| Group Box   | Control or Field | Description or Action
+| *Library*   | Catalog          | Name of the catalog where the library is created. This is a read-only field.
+|             | Schema           | Name of the schema where the library is created. This is a read-only field.
+|             | Library Name     | Name of the library. This is a read-only field.
+| *Code File* | Code File        | Click [ Browse ] to launch the "Select a code file" dialog box and
 navigate to a new JAR file on the client workstation.
-[ Alter ]
-Alters the library.
-[ Close ]
-Closes the dialog box without altering the library.
-[ Help ]
-Displays context-sensitive help for this dialog box.
+|             | [ Alter ]        | Alters the library.
+|             | [ Close ]        | Closes the dialog box without altering the library.
+|             | [ Help ]         | Displays context-sensitive help for this dialog box.
 |===
 
-[[related-topics]]
 Related Topics
 
-link:#_bookmark100["Alter a Library" (page 32)]
-link:#_bookmark95["Create a Library" (page 29)] link:#_bookmark105["Drop
-a Library" (page 33)]
-
-link:#_bookmark107["Download a JAR File From a Library" (page 34)]
+* <<alter-a-library, Alter a Library>>
+* <<create-a-library, Create a Library>>
+* <<drop-a-library, Drop a Library>>
+* <<download-a-jar-file-from-a-library, Download a JAR File From a Library>>
 
 [[drop-a-library]]
 == Drop a Library
@@ -398,8 +367,8 @@ Requirements:
 library or have the DROP_LIBRARY privilege for the schema to drop the
 library. The schema owner can grant such a schema-level privilege to
 other users or roles. For more information, see the Grant/Revoke
-Privileges Tool in HPDM or the GRANT SCHEMA statement in the __Trafodion
-SQL Reference Manual__.
+Privileges Tool in HPDM or the GRANT SCHEMA statement in the
+http://trafodion.apache.org/docs/sql_reference/index.html#grant_statement[Trafodion SQL Reference Manual].
 
 To drop a library from the database:
 
@@ -417,13 +386,12 @@ fail with an error message.
 5.  Click [ Yes ] to drop the library, or click [ No ] to quit the
 dialog box without dropping the library.
 
-Related Topics
-
-link:#_bookmark95["Create a Library" (page 29)]
-link:#_bookmark100["Alter a Library" (page 32)]
+*Related Topics*
 
-link:#_bookmark107["Download a JAR File From a Library" (page 34)]
-link:#_bookmark110["Display Libraries and Their Properties" (page 36)]
+* <<create-a-library, Create a Library>>
+* <<alter-a-library, Alter a Library>>
+* <<download-a-jar-file-from-a-library, Download a JAR File From a Library>>
+* <<display-libraries-and-their-properties, Display Libraries and Their Properties>>
 
 [[download-a-jar-file-from-a-library]]
 == Download a JAR File From a Library
@@ -437,32 +405,36 @@ Database Manager (HPDM) User Guide_ or the online help in HPDM.
 To download a JAR file from a library:
 
 1.  In HPDM, select the Database area.
+
 2.  In the navigation tree pane, expand the tree to display the folders
 of the schema that contains the library, and expand the Libraries folder
 to display the libraries within it.
+
 3.  Right-click the name of the library, and select Browse Library. The
 Browse Library dialog box appears with the name of the library selected
 in the tree pane and displayed in the right pane. For more information,
-see link:#_bookmark109["Use the Library Browser" (page 35)].
-4.  Click the [ Download ] button. The Browse For Folder dialog box
+see <<use-the-library-browser, Use the Library Browser>>.
+
+4.  Click the [ Download ] button. The *Browse For Folder* dialog box
 appears.
-5.  In the Browse For Folder dialog box, select a target folder on the
+
+5.  In the *Browse For Folder* dialog box, select a target folder on the
 client workstation for downloading the JAR file.
+
 6.  Click [ OK ] to start downloading the library's underlying JAR file
 to the client workstation, or click [ Cancel ] to quit the Browse For
 Folder dialog box and return to the Browse Library dialog box.
+
 7.  When notified that the download completed successfully, click [ OK ]
 to return to the Browse Library dialog box.
 
-Related Topics
-
-link:#_bookmark109["Use the Library Browser" (page 35)]
-link:#_bookmark95["Create a Library" (page 29)]
-
-link:#_bookmark100["Alter a Library" (page 32)] link:#_bookmark105["Drop
-a Library" (page 33)]
+*Related Topics*
 
-link:#_bookmark110["Display Libraries and Their Properties" (page 36)]
+* <<use-the-library-browser, Use the Library Browser>>
+* <<create-a-library, Create a Library>>
+* <<alter-a-library, Alter a Library>>
+* <<drop-a-library, Drop a Library>>
+* <<display-libraries-and-their-properties, Display Libraries and Their Properties>>
 
 [[use-the-library-browser]]
 == Use the Library Browser
@@ -471,70 +443,7 @@ Depending on the context in which the Library Browser is launched, you
 can use it to view, create, or drop libraries in the database; to
 download a JAR file from a library in the database to the client
 workstation; or to select a Java method in a library when creating a
-stored procedure. The Library Browser consists of these main parts:
-
-image:media/image5.jpeg[image]
-
-Use these buttons to perform various library management tasks:
-
-Button Function
-
-[ Create ]
-
-Launches the Create Library dialog box so that you can create a library
-in the database. In the navigation tree pane, select a schema name or
-the Libraries folder to activate this button. For more information, see
-link:#_bookmark98["Use the Create Library Dialog Box" (page 31)].
-
-[ Drop ]
-
-Launches the Drop Library dialog box so that you can delete a library
-from the database. In the navigation tree pane, select the name of a
-library to activate this button. For more information, see
-link:#_bookmark105["Drop a Library" (page 33)].
-
-[ Download ]
-
-[ Refresh ]
-
-Launches the Browse For Folder dialog box so that you can select a
-folder on the client workstation for downloading a library's underlying
-JAR file. In the navigation tree pane, select the name of a library to
-activate this button. For more information, see
-link:#_bookmark107["Download] link:#_bookmark107[a JAR File From a
-Library" (page 34)].
-
-Refreshes the data grid with the latest metadata.
-
-[ OK ]
-
-[ Close ]
-
-Accepts your selected Java method for the stored procedure that you are
-creating, closes the Library Browser, and returns to the Create
-Procedure dialog box. This button appears only if you launched the
-Library Browser from the Create Procedure tool. It is activated after
-you select a Java class name in the navigation tree pane and then select
-a Java method name in the data grid. For more information, see
-link:#_bookmark116["Create a Procedure" (page 37)] or
-link:#_bookmark120["Use] link:#_bookmark120[the Create Procedure Dialog
-Box" (page 39)].
-
-Closes the Library Browser.
-
-[ Help ] Displays context-sensitive help for the Library Browser.
-
-Related Topics
-
-link:#_bookmark95["Create a Library" (page 29)]
-
-link:#_bookmark98["Use the Create Library Dialog Box" (page 31)]
-link:#_bookmark105["Drop a Library" (page 33)]
-
-link:#_bookmark107["Download a JAR File From a Library" (page 34)]
-link:#_bookmark116["Create a Procedure" (page 37)]
-
-link:#_bookmark120["Use the Create Procedure Dialog Box" (page 39)]
+stored procedure.
 
 [[display-libraries-and-their-properties]]
 == Display Libraries and Their Properties
@@ -550,8 +459,3 @@ name, or open the Libraries
 folder and select a library name in the tree. HPDM displays the
 libraries for this schema.
 
-image:media/image6.jpeg[image]
-
-For more information about the library properties displayed in HPDM, see
-the _HP Database Manager (HPDM) User Guide_ or the online help in HPDM.
-


Mime
View raw message