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-4
Installing NonStop SQL/MX
OSS environment is case-sensitive, so enter all commands in the appropriate
case. You must be a super ID user to execute the InstallSqlmx script.
Before running the InstallSqlmx script, you might want to set your terminal type
to VT320 (from OutsideView) to obtain the most readable block-mode screen
displays.
7. Run the InstallSqlmx script by entering:
InstallSqlmx -l \$volume [ -n national_charset_name ]
[ -nofcheck ]] | -initmxcs | -b
You must enter the -l option, and always first. The other options are optional and
can be entered in any order. In this next example, the volume $dat215 is
specified as the location into which InstallSqlmx installs the SQL/MX system
metadata tables.
InstallSqlmx -l \$dat215
8. To develop and execute Java programs that perform SQL operations or SPJs,
install NonStop Server for Java and JDBC/MX on your NonStop system. For
detailed download and installation instructions, see the README files on the
product CDs for NonStop Server for Java and JDBC/MX.
9. If you are migrating from Release 1.8 to Release 2.1 or Release 2.0:
a. If you want to preserve the settings for the SQL/MP DEFAULTS, MPALIAS,
PROCS, PARAMS, ZOAS2DS, ZODS, ZOENV, ZONAM2ID, and ZORES
tables, use the migrate utility to copy the contents of these tables to their
corresponding Release 2.1 or Release 2.0 metadata tables. For information
about migrating metadata from Release 1.8 to Release 2.1 or Release 2.0, see
Using the migrate Utility to Migrate SQL/MP Metadata From Release 1.8 on
page 14-5.
b. Before you run the migrate utility, create the user catalogs and schemas in
the Release 2.1 or Release 2.0 database. The user catalogs and schemas are
required to migrate SPJs and SQL/MP aliases from Release 1.8 to Release 2.1
or Release 2.0. If you do not create the user catalogs and schemas, migrate
returns error messages reporting that they do not exist, and the CREATE
MPALIAS and CREATE PROCEDURE statement portion of the utility fails. For
catalog and schema naming guidelines, see Table 14-1 on page 14-5.
c. Be sure to use the migrate utility immediately after you have installed
Release 2.1 or Release 2.0. Until you run the migrate utility, your SQL/MP
Caution. InstallSqlmx creates the anchor file and assigns it a security of “N----.” The super ID
should not change this setting.
Caution. The volume you specify in the InstallSqlmx command line specifies the system
catalog location for the system metadata tables. The volume should not go on the $SYSTEM
disk volume. If you ever replace the $SYSTEM disk, you can lose system metadata information.
The specified volume must be audited.