In order to use MQe as a system queue which is turned on by default we can invoke:
TDI_install_dir\jars\plugins\mqeconfig.bat(.sh) TDI_install_dir\jars\plugins\mqeconfig.props create server
If we do not want to use the system queue, set the systemqueue.on property of the global.properties or solution.properties file to false.
The text files as installed by SMP/E are encoded using the IBM-1047 encoding. If the default character encoding on your system is different from IBM-1047 we need to perform the following post-installation steps before the IBM TDI installation directory is made read-only in order to convert the text files to our default encoding:
iconv -f IBM-1047 -t YOUR_DEFAULT_ENCODINGencconvz > ../encconvz
chmod u+x encconvz
Ensure that either the JRE_PATH or the JAVA_HOME environment variable is set accordingly. For example: If your Java SDK is installed in "/usr/lpp/java/MyJava5.0", then
JAVA_HOME=/usr/lpp/java/MyJava5.0
or
JRE_PATH=/usr/lpp/java/MyJava5.0/bin
Since the install directory of TDI (/usr/lpp/itdi) is read-only, TDI must be run from a solution directory (as explained in the documentation) which is different from the install directory. That is why before running TDI, we should create a solution directory (which is just a normal directory different from the install directory), make this solution directory the current working directory and then launch the TDI server. We can follow these steps in order to accomplish the creation of a solution directory and launching the TDI server:
where TDI_PARAMETERS are just the normal parameters the TDI server reads from the command line. The first time the server runs this way, it will populate the solution directory with a number of configuration files based on those in the installation directory; we can now customize the files in the solution directory for our own needs.
All license files are UTF-8-encoded so that NLS characters are preserved. Most OS tools can only read files encoded using the default (native) character encoding. That is why before we can read a license file using a general purpose tool, we need to convert its encoding. We can do that using the iconv utility in the following way:
iconv -f UTF-8 -t YourDefaultCharacterEncoding LicenseFile DestinationFile
where YourDefaultCharacterEncoding is the native character encoding of the z/OS system, LicenseFile is the license file you wish to convert and DestinationFile is the text file that will contain the contents of LicenseFile, but encoded using YourDefaultCharacterEncoding.
After this command completes we should be able to open and read DestinationFile (provided we have specified the correct encoding and that encoding supports all characters in LicenseFile).
Another option for reading the license files is to transfer them in BINARY mode via FTP to a system which can read UTF-8-encoded text files and supports the NLS characters contained in the license file you wish to read.