The InstallSqlmx script

The InstallSqlmx script is used only for the first install of SQL/MX. The following list describes the various activities performed by InstallSqlmx during the installation. If InstallSqlmx cannot successfully initialize SQL/MX, it aborts generating a log file.

  • Verifies that all processors on the system are valid processor types for SQL/MX Release 3.5. If InstallSqlmx detects a problem, it generates a non-SQLCODE error message that identifies the processor or processors that have not met the hardware requirements.

  • Verifies that the SQL/MX SPRs, objects, files, executables, and libraries are installed and copied correctly to their default locations from the SUT installation. If any required SQL/MX objects are missing from their default locations, the script notifies the user about the missing objects and aborts the installation. For more information on the files and default locations, see Automatic file installations. Also, see the SQL/MX Management Manual.

  • Creates an anchor file that specifies the volume location of system metadata tables and assigns a security of “NCNC” to the anchor file.

    The anchor file is a simple text file with ASCII tokens that identifies the volume where system metadata will reside. The file resides in the Guardian space $SYSTEM.ZSQLMX.MXANCHOR

    CAUTION:

    The user who runs InstallSqlmx must have super ID (SUPER.SUPER) privileges on the node. InstallSqlmx does not support user aliases for SUPER.SUPER.

    Do not change the NCNC setting in the anchor file. If the anchor file is modified, SQL/MX ceases to operate on the system.

  • After successfully creating the anchor file, InstallSqlmx issues an INITIALIZE SQL statement to initialize SQL/MX. If SQL/MX cannot be successfully initialized, the installation is aborted and the anchor file is removed. Whether initialization is successful or not, InstallSqlmx creates a log at /usr/tandem/ sqlmx/bin/initlog. This log file contains the status information about the initialization of SQL/MX.

    InstallSqlmx also implements the national character set specified with the -n option. The national character set is associated with NCHAR and NATIONAL CHARACTER types and with N string literals, host variables, and SQL functions and predicates.

    The INITIALIZE SQL operation also creates metadata tables for the schema MXCS_SCHEMA in the system catalog.

  • Initializes the SQL/MX Connectivity Service (MXCS) and loads MXCS metadata tables in the MXCS_SCHEMA of the system catalog with their default values. After loading the MXCS metadata tables, the script creates a log at /usr/tandem/ sqlmx/bin/mxcslog. This log file contains the status information about the MXCS initialization operation.

  • Initializes the HELP_CONTENTS metadata table for MXCI online help. The InstallSqlmx script automatically invokes the InstallSqlMxHelp script with the command-line option -installHelp, which handles the creation and initialization of the MXCI help contents.

    If the MXCI online help does not get automatically installed, see Installing the SQL/MX MXCI online help.

  • Verifies that the system metadata tables are created in the specified volume with the -l option of the InstallSqlmx command.

  • If the -nofcheck option is not specified in the syntax, InstallSqlmx performs FCHECK on all volumes on the local node to locate and possibly correct the labels of SQL/MP tables with added columns. If a SQL/MP table with an added column was duplicated, the addedColumn flag might not be carried over to the duplicated table, resulting in problems. FCHECK correctly sets this flag.

    The script also creates a viewable log at /usr/tandem/sqlmx/bin/fchecklog, which contains details about the FCHECK operation.

    NOTE:

    If a large number of disk drives are attached to the local node, the FCHECK portion of InstallSqlmx can take a long time to complete. To avoid this delay, run FCHECK before you run InstallSqlmx.