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

•
mxlangman.policy
• mxudr.mak
• mxt_install.ksh
• mxtool_install_procs
• mxtool_verify.jar
CAUTION: Do not move the mxlangman.jar file to a location outside the installation
directory, /usr/tandem/sqlmx/udr. If you do, you will encounter problems invoking
SPJs. For more information, see the SQL/MX Guide to Stored Procedures in Java.
Verifying the files licenses
Make sure that all these files are licensed in $SYSTEM.SYSTEM:
• IMPORT
• MXUTP
• MXIMPDDL
• MXAUDSRV
• MXCMP
• MXESP
• MXRTDSRV
• ZCLIPDLL (this is found under $SYSTEM.ZDLLnnn)
• YCLIDLL (this is found under $SYSTEM.ZDLLnnn)
• MXTOOL
To verify that these files are licensed:
1. From a TACL prompt, issue a FILEINFO command on each of the files. IMPORT, MXAUDSRV,
MXCMP, MXESP, MXRTDSRV, MXUTP, MXIMPDDL and MXTOOL reside in
$SYSTEM.SYSTEM.ZCLIPDLL resides in $SYSTEM.ZDLLnnn. To find out if a file (for
example, MXCMP) is licensed, enter
FILEINFO MXCMP
2. Verify that each of these file shows an L after the file code. The L confirms that the file is
licensed. For example:
$SYSTEM.SYSTEM
CODE EOF LAST MODIFIED OWNER RWEP PExt SExt
MXCMP 800L 170109040 05JAN2011 1:17 255,255 NUNU 128 128
Starting MXCI
MXCI runs as an OSS process and must be started from within the OSS environment.
NOTE: Check that the mxci file in the OSS directory /usr/tandem/sqlmx/bin have read
and execute permissions on your node. If it does not have r execute access, you cannot start it. If
necessary, use the OSS command chmod to change the permissions.
To start MXCI:
1. At a TACL prompt, start the OSS shell by entering:
osh
Verifying the SQL/MX installation 21