SQL/MX 3.2.1 Installation and Upgrade Guide (H06.26+, J06.15+)

SeeFor more information about
“Summary of installed SQL/MX files” (page 22)Descriptions of the SQL/MX files that were installed
on your system
“Verifying executable file versions” (page 25)The executable SQL/MX files installed on your system
Automatic file installations
This subsection identifies the activities that automatically occur during installation of the H06.25 ,
J06.14 and later RVUs:
1. The H06.25 , J06.14 and later RVUs include SQL/MX executables and libraries. When you
install the SUT, the installation automatically copies these files to their default locations:
• To $SYSTEM.SYSTEM, the files IMPORT,MXTOOL, MXIMPDDL, MXAUDSRV, MXCMP,
MXESP, MXOMSG, MXRTDSRV, MXUDR, MXUTP, SQLCLIO, and ESQLCLIO.
• To $SYSTEM.ZMXTOOLS, the files MXGNAMES, MXVQP, T0607SET,and T0610SET.
• To $SYSTEM.ZMXODBC, the files MXOAS, MXOCFG, MXODSN, MXOSRVR,and
TDMODBC.
2. The SUT installation automatically copies these PAX files to $SYSTEM.ZOSSUTL, a temporary
OSS directory on your system:
• T0517PAX, which contains the setmxdb script file.
• T0611PAX, which contains the system module and user module files.
• T1050PAX, which contains the SQL/MX internal module files.
• T1051OBJ, which contains the object files sqlcli.o, esqlcli.o, mxrpm and the
ANSI names server process executable, ansp.exe.
• T1051PAX, which contains the header files Platform.h, mxmaintain, 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, import, mximportddl, and mxexportddl.
• T1056INI, which contains InstallSqlmx.
• T1057PAX, which contains the SQL/MX agent (tdm_br.tlo).
• T1058PAX, which contains mxcierrors.cat, the MXCI 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. The SQL/MX Release 3.2.x installs YCLIDLL, which is a 64-bit
version of ZCLIDLL.
CAUTION: It is expected that DSM/SCM is installed on each Integrity NonStop 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.
Verifying the SQL/MX installation 19