Manualshelf

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

ManualsBrandsHP ManualsServerHP Integrity NonStop J-Series
51525354555657585960
Installing NonStop SQL/MX
HP NonStop SQL/MX Installation and Management Guide—544536-007
3-4
Installing NonStop SQL/MX
For a detailed description of InstallSqlmx command syntax, command options,
and informational messages, see Using the InstallSqlmx Script on page 3-18. The
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. Also see Verifying
Correct Versions of Independent Software Products on page 2-3.
9. You are now ready to start using NonStop SQL/MX. Proceed to Verifying the
SQL/MX Installation.
Caution. InstallSqlmx creates the anchor file and assigns it a security of “N----.” Do not
attempt to change this setting. If you change the security setting and the anchor file is
modified, NonStop SQL/MX will cease to operate on the system.
Caution. The volume you specify in the InstallSqlmx command line specifies the system
catalog location for the system metadata tables. This 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.