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

Installing NonStop SQL/MX
HP NonStop SQL/MX Installation and Management Guide—523723-004
3-22
Using Import Catalog Tools
For information about running the Windows-hosted SQL/MX COBOL preprocessor, see
the SQL/MX Programming Manual for C and COBOL.
Using Import Catalog Tools
mxexportddl is the only Import Catalog tool available for Release 2.1 or Release 2.0.
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/MX 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, the SQL/MX Programming Manual for Java, and the SQL/MX
Programming Manual for C and COBOL.
Corrective Action Tasks
After you install Release 2.1 or Release 2.0, it might become necessary to perform one
of these tasks:
•
Removing Unwanted Files From the Node on page 3-22
•
Falling Back to Release 1.8 on page 3-22
Removing Unwanted Files From the Node
If you have installed Release 2.1 or Release 2.0 on a system node where Release 1.8
was previously installed, you might want to remove remaining files to increase disk
space and improve performance.
For information about removing files to free up disk space, see Appendix A, Falling
Back From NonStop SQL/MX Release 2.1 or Release 2.0.
Falling Back to Release 1.8
You might decide to fall back from Release 2.1 or Release 2.0 to Release 1.8, either
during installation or after you have successfully installed Release. 2.0. For information
about falling back, see Appendix A, Falling Back From NonStop SQL/MX Release 2.1
or Release 2.0.
Note. Do not remove these remaining files until you are certain that you do not need them to
fall back from Release 2.1 or Release 2.0 to Release 1.8, as they might be required to install
and restore Release 1.8. For example, removing the SQL/MP metadata tables MPALIAS,
DEFAULTS, PROCS, and PARAMS would prevent you from successfully restoring the
metadata settings for Release 1.8.