SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)
Table Of Contents
- HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide
- Contents
- About this manual
- 1 Preparing to install SQL/MX
- 2 Installing SQL/MX
- Summary of installation tasks
- Preinstallation tasks
- Using the InstallSqlmx script
- Installing SQL/MX
- Verifying the SQL/MX installation
- Post-Installation tasks
- 3 Installing a sample database
- 4 Overview of SQL/MX system upgrade
- 5 Considerations for upgrading the system to SQL/MX Release 3.2
- 6 Upgrading the system to SQL/MX Release 3.2
- 7 Falling back from SQL/MX Release 3.2
- A Removing security administrator grants
- B Identifying tables that contain an IDENTITY Column
- C Identifying tables where the ownership has changed
- D Version management and interoperability
- SQL/MX releases
- Interoperability of SQL/MX releases
- Versions of SQL/MX software components
- E Conversions
- Index
1. The H06.25 or J06.14 or later H-series or J-series RVU includes 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, 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-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. The SQL/MX Release 3.2 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