SQL/MX 2.x Installation and Management Guide (H06.10+, J06.03+)

Installing NonStop SQL/MX
HP NonStop SQL/MX Installation and Management Guide—544536-007
3-18
Relinking the SQL/MX UDR Server
1. Use OutsideView, the Receive File option, or FTP to download T610SET to a
Windows workstation.
The setup file for the preprocessor is a binary file. If you use the Receive File
option, select Binary but do not select Add CR LF. Specify setup.exe for the
local file name. The Installshield Wizard installs the preprocessor files. By default,
NonStop SQL/MX places the executable in the C:\Program Files\HP SQL-MX
COBOL Preprocessors directory. If you prefer, click Browse and select another
folder.
2. Delete the temporary folder and SETUP.EXE if you want.
For information about running the Windows-Hosted SQL/MX COBOL preprocessor,
see the SQL/MX Programming Manual for C and COBOL.
Relinking the SQL/MX UDR Server
For the H06.04 or later H-series RVU, you do not need to statically relink the SQL/MX
UDR server to the NonStop Server for Java and the JDBC Driver for SQL/MX
(JDBC/MX). The T1230PAX file is not delivered on the SUT, and the files it contains
(mxudr.mak, mxudr.oby, mxudr.tlo, and mxudrlink) are not needed.
Using Import Catalog Tools
mxexportddl is the only Import Catalog tool available for SQL/MX Release 2.x. Its
primary purpose is to provide a file describing the SQL/MX compilation environment for
a table or a single schema. This file is used by service providers to evaluate reported
problems with the SQL/MX compiler. It can also be used to capture the DDL for tables,
stored procedures, and SQL/MP aliases into a single file that records the DDL for one
instance in time (for example, just before a major change), making mxexportddl
useful as part of a change management process.
Using Module Management Tools
For information about managing user modules, see Section 11, Managing Database
Applications and the SQL/MX Programming Manual for C and COBOL.
Using the InstallSqlmx Script
The InstallSqlmx script:
•
Verifies that all processors on the system are valid processor types for SQL/MX
Release 2.x. If InstallSqlmx detects a problem, it generates a non-SQLCODE
error message that identifies the processor or processors that do not meet
hardware requirements. For information about this and other InstallSqlmx
error messages, see the SQL/MX Messages Manual. For information about
hardware requirements for SQL/MX Release 2.x, see Hardware Requirements on
page 2-1.