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

Installing NonStop SQL/MX
HP NonStop SQL/MX Installation and Management Guide544536-007
3-6
Overview of Automatic File Installations
T1050PAX, which contains the SQL/MX internal module files
T1051OBJ, which contains the object files sqlcli.o, esqlcli.o, and the ANSI
names server process executable, ansp.exe.
T1051PAX, which contains the header files Platform.h and sqlcli.h.
T1052PAX, which contains mxsqlc, the SQL/MX C/C++ preprocessor
T1053PAX, which contains mxsqlco, the SQL/MX COBOL preprocessor
T1054PAX, which contains mxci, the SQL/MX conversational interface
T1056PAX, which contains mxtool and migrate
T1056INI, which contains InstallSqlmx
T1057PAX, which contains the SQL/MX agent
T1058PAX, which contains mxcierrors.cat, the MXCI-related error
messages file
T1231PAX, which contains the SQL/MX language manager files
mxlangman.jar and mxlangman.policy
3. The SUT installation automatically installs the public DLLs ZCLIDLL and
ZCLIPDLL to the $SYSTEM.ZDLLnnn subvolume, where nnn is a number picked
by the public DLL installation during the SYSGEN operation.
4. The SUT installation automatically installs the EMS events file, ZMXSTMPL, to
$SYSTEM.ZTEMPL.
5. Depending on its product version, DSM/SCM automatically or manually configures
the OSS environment, copies all OSS PAX files, and places the new SQL/MX OSS
files in the OSS environment.
In addition, DSM/SCM automatically or manually uses the COPYOSS macro to
install these OSS files into these OSS directories:
a. COPYOSS installs these files in the OSS directory /usr/tandem/sqlmx/bin:
InstallSqlmx
migrate
mxci
mxcierrors.cat
mxCompileUserModule
mxexportddl
mxsqlc
mxsqlco
Caution. It is expected that DSM/SCM is installed on each Integrity NonStop NS-series
system on which you install the DLLs. DSM/SCM handles DLL licensing automatically. If you
do not use DSM/SCM to install the DLLs, you must license the DLLs by other means.
Processor halts can occur if the DLLs are not licensed properly.