C H A P T E R 1

Installation

This chapter describes problems you might encounter when installing Sun MTP for the first time or when upgrading or installing a maintenance release. This chapter contains the following topics:

License Problems

First-Time Installation

Maintenance Installation

License Problems

License File Does Not Exist

Sun MTP requires that you have a valid license file, which contains the software enabling key, in the directory specified in the KIXLICDIR environment variable. The license key itself is tied to the host identifier.

To Verify That a License File Exists

1. Set your environment by sourcing the region's setup file.

2. Change to the $KIXLICDIR directory.

3. Verify that the license file exists.

The file must be named xxx.lic, where xxx is the host identifier.

4. If the file does not exist, do either of the following:

Create a license file in the $KIXLICDIR directory following the instructions in the Sun Mainframe Transaction Processing Software Installation Guide.

Determine whether you installed the license file in a directory other than $KIXLICDIR, and if so, reset $KIXLICDIR to the new directory and try starting the region.

License File Error Messages Are Displayed

During startup, Sun MTP issues an error message if the software enabling key has expired or is improperly typed in the file. You must contact your authorized service provider to get a new software enabling key or extend your current one if it has expired. Make sure to provide the host identifier of your system and your current key when reporting the problem.

If the enabling key is new and you experience this problem, you might have typed information incorrectly in the license file. Verify that you typed the exact number of characters using the correct case.

First-Time Installation

To install Sun MTP for the first time, use the unzip command. If you get any errors, report them to your authorized service provider, along with the exact error message.

Insufficient Disk Space

Sun MTP requires a sufficient amount of disk space for installation. In addition, you need disk space for building Sun MTP objects, such as unikixtran and unikixvsam, which are created during installation. If you are having problems building these objects, look for disk space error messages generated during the kixinstall build process in the /tmp/kixinstall.log.pid file. pid is the process identifier (ID) of the kixinstall process.

Refer to the Sun Mainframe Transaction Processing Software Release Notes for information about disk space requirements.

`kixinstall` Displays Error Messages

If error messages are displayed while you are using the kixinstall utility to remake the unikixtran module, examine the following:

The /tmp/kixinstall.log.pid contains unikixtran errors and other build errors. pid is the process ID of the kixinstall process. A message containing the name of this file is displayed when you exit the kixinstall program. If you need further assistance, you can email the kixinstall.log.pid file to your authorized service provider.

If you are using COBOL, verify that you set the $COBDIR and COBOL executables path.

Verify that you set the shared library environment variable (LD_LIBRARY_PATH) to the proper library directories.

If you are using third-party databases, such as Oracle^®, verify that you set the appropriate variables. Review the README.doc in $UNIKIX/test/databasename for a list of the required variables. Also refer to the Sun Mainframe Transaction Processing Software Configuration Guide.

Maintenance Installation

If you are installing a maintenance release of Sun MTP, you must first shut down all regions, then use the same procedure as for a first-time installation.

Do not install a maintenance release on top of the current Sun MTP release. Instead, install it in another directory, using the release number as part of the directory name; for example, /mtp/nnnnnn-nn/MTP8.0.0p1, where nnnnnn-nn is the patch number. The typical maintenance release contains only the changes documented in the patch notes and usually affects only a few modules. However, rather than providing only the changed modules, you will receive the entire package. This minimizes confusion about what to install and makes it easier to go back to a previous release if the maintenance release causes problems.