C H A P T E R  6

Additional Installation Topics

This chapter describes additional procedures associated with installing and setting up a Sun MTP system. It contains the following topics:

If your site requires it, perform these tasks after installing the Sun MTP software and verifying that it executes correctly.

If your Sun MTP region does not start, refer to the Sun Mainframe Transaction Processing Software Troubleshooting and Tuning Guide. Also, refer to the Sun Mainframe Transaction Processing Software Configuration Guide, which describes configuration parameters that can affect system startup.


Preserving Site-Specific Changes

If an earlier version of the software is installed at your site, you might have modified some utility shell scripts or programs to handle special conditions. If you want to maintain these modifications, you can transfer these files to your new installation.

Modifications involving changes to the Sun MTP source, such as the addition of user-called C functions or customized record processing routines, cannot be preserved. These modifications are specific to the version of the Sun MTP transaction and batch servers with which they are bound.


procedure icon  To Preserve Site-Specific Changes

single-step bulletCopy any shell scripts or programs that were modified to handle site-specific conditions from their current location to a corresponding location within the new installation.


Creating Symbolic Links for Sun MTP

It is a good idea to install each version of Sun MTP in its own directory. To control the version of Sun MTP used for production, use a single symbolic link to link a generic path name to the production version. Any time you want to change from version to version, you only have to change the symbolic link.

Users' setup scripts can remain intact because the scripts only use the symbolic link's name, not the actual directory name. For example, in the setup file, set the UNIKIX environment variable to /pkgs/mtp/MTP8.0.0.


procedure icon  To Create Symbolic Links

1. Choose a generic name like mtp to link to a specific version of the software.

2. Install the system in a version-specific directory, such as /pkgs/mtp/MTP8.0.0.

3. Create a symbolic link to the new installation directory by executing a command like the following, which sets up a symbolic link from /pkgs/mtp/MTP8.0.0 to mtp:

$ cd /pkgs/mtp
$ ln -s MTP8.0.0  mtp

or

$ ln -s /pkgs/mtp/MTP8.0.0  mtp

4. Any time you install a new version of the software, remove the link to the old version and create a link to the new version.



Note - See the ln(1) man page for more information about creating symbolic links.