SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)

• After creating the anchor file, InstallSqlmx assigns a security of “N---” to the anchor file.
CAUTION: After InstallSqlmx assigns a security of “N---” to the anchor file, do not
change this setting. If the anchor file is modified, SQL/MX ceases to operate on the system.
• Initializes SQL/MX after successfully creating the anchor file.
• Implements the national character set specified with the -n option.
• Initializes the SQL/MX Connectivity Service (MXCS) after successfully initializing SQL/MX.
• Verifies that the system metadata tables are created in the specified volume.
• Performs FCHECK on all volumes on the local node to locate and possibly correct the labels
of SQL/MP tables with added columns. This step is optional if NOFCHECK is specified. By
default, FCHECK is performed.
Phases of InstallSqlmx
The following table describes the six phases of activity performed by InstallSqlmx. If
InstallSqlmx cannot successfully initialize SQL/MX, it aborts generating a log file.
Table 1 The Phases of InstallSqlmx
Phase ActivitiesPhase
InstallSqlmx verifies that the SQL/MX objects are laid down correctly from the SUT installation. If
any required SQL/MX objects are missing from their default locations, InstallSqlmx notifies the user
1
about the missing objects and aborts the installation. For more information on filename and default
locations, see “Overview of automatic file installations” (page 18) . Also, see the SQL/MX Management
Manual.
InstallSqlmx creates an anchor file that contains the location of the SQL/MX system metadata tables.
The anchor file is a simple text file with ASCII tokens that identifies the volume where system metadata
2
will reside. The file resides in the Guardian space $SYSTEM.ZSQLMX.MXANCHOR and is assigned a
security of “N---.”
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
3
is successful or not, InstallSqlmx creates a log at /usr/tandem/sqlmx/bin/initlog. The
viewable log file initlog contains status information about the initialization of SQL/MX.
The INITIALIZE SQL operation also creates metadata tables for the schema MXCS_SCHEMA in the system
catalog.
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.
InstallSqlmx loads MXCS metadata tables in the MXCS_SCHEMA of the system catalog with their
default values.
4
After loading MXCS metadata tables, InstallSqlmx creates a log at
/usr/tandem/sqlmx/bin/mxcslog. The viewable log file mxcslog contains status information
about the MXCS initialization operation.
InstallSqlmx verifies that the system metadata tables are created in the volume specified with the
-l option of the InstallSqlmx command.
5
If the -nofcheck option is not specified, InstallSqlmx performs FCHECK on volumes of the local
node to locate SQL/MP tables with added columns. If an SQL/MP table with an added column was
6
duplicated, the addedColumn flag might not be carried over to the duplicated table, resulting in
problems. FCHECK correctly sets this flag for SQL/MP tables with added columns.
InstallSqlmx also creates a viewable log at/usr/tandem/sqlmx/bin/fchecklog, that contains
details about the FCHECK operation.
Using the InstallSqlmx script 15