Installing SQL/MX

After verifying the system requirements and performing the pre-installation tasks, you can install the SQL/MX software and the SQL/MX sample database that is distributed with it.

  1. Log on to the NonStop server as SUPER.SUPER (user ID 255,255) user.

  2. Install the required L-series SUT. Follow all the instructions provided in the associated software release document and any instructions that come with the SUT. For more information about installing the SUT, see the Software Installation and Upgrade Guide.

  3. As needed, use DSM/SCM to install SPRs to obtain the functionality and defect repair for SQL/MX Release 3.5.

    For more information about using DSM/SCM, see the DSM/SCM User’s Guide. For more information about installing SPRs using DSM/SCM, see the Software Installation and Upgrade Guide.

    SQL/MX Release Information

    Your RVU

    Default SQL/MX Release

    L17.02 SQL/MX Release 3.5
  4. If you are using DSM/SCM and your version requires it, run the TACL COPYOSS macro from $SYSTEM.ZOSSUTL. For more information, see the Open System Services Management and Operations Manual and Automatic file installations.

    MXCS is automatically installed from the SUT to the Guardian environment, but you must initialize it using InstallSqlmx script. For more information on setup and configuration, see the SQL/MX Connectivity Service Manual.

    SQL/MX Database Manager (MXDM) is a GUI application that you can use to create and manage database objects. For more information, see the MXDM User Guide for SQL/MX Release 3.5.

  5. FCHECK is a Guardian program to check the internal consistency of DP2 structured files. For more information, see the DP2 FCHECK User's Guide. If you want to run FCHECK independently of the InstallSqlmx script, do it before you run InstallSqlmx. If a large number of disk drives are attached to the local node on your system, the FCHECK portion of InstallSqlmx can take a long time to complete.

    To run FCHECK independently of InstallSqlmx, issue the command for the volumes you want to check:

    FCHECK -MXCHECK -VOL $volume

    If you run FCHECK independently, make sure you specify the -nofcheck option when you run InstallSqlmx.

  6. From a TACL prompt, start the OSS shell by entering:

    osh

    You are now in the OSS environment.

Initializing SQL/MX

The following are the steps to initialize SQL/MX:

NOTE:
  • The InstallSqlmx script is required only for the first installation of SQL/MX, or to regenerate the MXANCHOR file deleted accidentally. You can skip the next three steps for a release upgrade.

  • If you want to configure database services on the system, run the InstallSqlmx script with -e option that enables or disables the EXTERNAL_NAME_CASESENSITIVE CQD.

  1. Before running the InstallSqlmx script, change to the correct directory by entering:

    cd /usr/tandem/sqlmx/bin

    CAUTION:

    InstallSqlmx creates the anchor file and assigns it a security of NCNC. Do not attempt to change this setting. If you change the security setting, and the anchor file is modified, SQL/MX ceases to operate on the system.

    Check if this is the first installation of SQL/MX on your system. For example, check if SQL/MX anchor file exists in /G/system/zsqlmx/mxanchor. Running InstallSqlmx more than once with different values of the -l parameter results in a corrupt SQL/MX environment.

  2. If no anchor file exists, run the InstallSqlmx script by entering all the options in the appropriate case as the OSS environment is case-sensitive:

    InstallSqlmx -l \$volume
    [ -n national_charset_name ]
    [ -nofcheck ]
    [ -initmxcs ]
    [ -b ]

    You must always enter the -l option 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 to which InstallSqlmx installs the SQL/MX system metadata tables.

    InstallSqlmx -l \$dat215

    CAUTION:

    The volume you specify in the InstallSqlmx command-line identifies the system catalog location for the system metadata tables. The specified volume must be audited. This should not go on the $SYSTEM disk volume. If you replace any disk containing the metadata information, you lose the system metadata information.

  3. To develop and execute Java programs that perform SQL operations or Stored Procedures in Java (SPJs), install NonStop Server for Java and JDBC/MX on your NonStop system.

    For details about installing these products, see the NSJ 7.0 Programmer's Manual and JDBC Type 2 Programmer's Reference or JDBC Type 4 Programmer's Reference.

    NOTE:

    Installation of NSJ7 does not automatically create the softlink /usr/tandem/java. If you have migrated all applications to NSJ7, then Hewlett Packard Enterprise recommends you create a softlink manually to point to the NSJ7 JDK/JRE installation (/usr/tandem/nssjava/jdk170_l70).

    Create the softlink /usr/tandem/java to point to the NSJ7 home directory as follows:

    $ ln -s /usr/tandem/nssjava/jdk170_l70 /usr/tandem/java

    After creating this softlink, applications may fail if they are not migrated to NSJ7.

  4. You are now ready to start using SQL/MX.

Related Topics

The InstallSqlmx script

InstallSqlmx syntax

The InstallDBS script

Installing the sample database