SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)

Table Of Contents
Installation ManualSoftware Requirements
TMF Planning and Configuration GuideTMF
TCP/IP Configuration and Management ManualHP NonStop TCP/IP
*For installation instructions and the latest version requirements, see the Softdoc file delivered with
the product, either on the product CD or on the website for Scout for NonStop Servers, at HP
NonStop eServices portal: https://onepoint.nonstop.compaq.com/.
Verifying correct versions of independent software products
If you intend to develop and execute Java programs that perform SQL operations or Stored
Procedures for Java (SPJs) on your NonStop system, verify that you have installed the correct versions
of these independent software products:
NonStop Server for Java
JDBC/MX driver
These independent products need to be ordered separately from the software products provided
with the latest product release.
For the latest product release information for the JDBC/MX driver, see the JDBC Softdoc and JDBC
Driver for SQL/MX Programmer’s Reference.
The product numbers are minimum versions on systems running H-series or J-series RVUs. For
installation instructions and the latest version requirements, see the Softdoc file delivered with the
product, either on the product CD or on the website for Scout for NonStop Servers, at HP NonStop
eServices portal https//onepoint.nonstop.compaq.com/.
Starting TMF
To install and then use SQL/MX, it is required that TMF be running and configured for all the data
volumes on which SQL/MX objects are created.
For more information about TMF auditing requirements, configuration guidelines, and considerations
for SQL/MX, see SQL/MX Management Manual and the TMF Planning and Configuration Guide.
The product version of TMF provided on the SUT must be compatible with the SQL/MX software
provided with the SQL/MX SPR you install.
When you start the TMF subsystem, only the accessible configured data volumes are started for
transaction processing. You must ensure that the volumes you intend to use for SQL/MX metadata
and audited objects are configured and started for transaction processing. You must also ensure
that the TMF subsystem as a whole is started for transaction processing. You can request status
from TMFCOM by entering the TMFCOM command at the operating-system command interpreter
prompt and then issuing specific STATUS commands through TMFCOM.
For more information on TMF configuration information, see the TMF Reference Manual.
Verifying correct versions of independent software products 13