C H A P T E R 1 - Installation and Migration Issues

C H A P T E R 1

Installation and Migration Issues

This chapter contains information about installing Sun MTP Release 8.0.1 and migration issues you might encounter. It contains the following topics:

General Installation Information

Licensing Changes

Upgrading From Earlier Releases

Future Patch Releases

Go to the SunSolve^SM web site to get information about fixes to previous releases that were also applied to Sun MTP Release 8.0.1.

General Installation Information

Sun MTP Release 8.0.1 has been qualified on the Solaris 8 and Solaris 9 operating systems.

The Sun Mainframe Transaction Processing Software Installation Guide provides the instructions for installing Sun MTP, as well as information you need if you are upgrading from an earlier release.

Hardware Requirements

To run the Sun MTP software on the Solaris OS, your environment must meet the following requirements.

Your Sun system must be at minimum an UltraSPARC^® III technology, E280R system with two CPUs. Your system must have at least 512 megabytes (Mbytes) of memory and .5 gigabytes (Gbytes) of disk storage available for the Sun MTP product.

Qualified Mainframe Rehosting Components

The following mainframe rehosting components have been qualified with Sun MTP 8.0.1. on Solaris platforms:

Sun Mainframe Administration Agent (Sun MAA), Release 1.0, patch level 1

Sun Mainframe Administration Tool (Sun MAT), Release 1.0, patch level 2

Sun Mainframe Batch Manager (Sun MBM), Release 10.0.1

Sun Mainframe Security Facility (Sun MSF), Release 1.0.1, patch level 1

Sun MTP High Availability Data Service for Sun Cluster, Release 1.0, patch level 3

Sun MTP J3270, Release 8.0, patch level 6

Sun MTP Client, Release 7.2, patch level 1

Qualified Compilers and Third-Party Software

This release of Sun MTP on the Solaris operating system has been qualified with the following third-party products:

Oracle^® relational database, versions 8i and 9i

IBM DB2 UDB relational database, versions 7.2 and 8.1

Sybase SQL Server, versions 12 and 12.5

Micro Focus Server Express, releases 2.2 and 4.0

Sun Studio C/C++ compilers; Sun Workshop 6.2 and later

Liant Open PL/I, version 7.4.6

Java, release 1.4 with the latest patches

IBM WebSphere MQ, version 5.3

SNAP-IX 7 (SNA stack for LU6.2)

Open SSL, version 3.3.7

TPS SNA Primer, version 2.9.1.0

Licensing Changes

Sun MTP is now licensed by CPU, rather than by the number of users.

When the term user is used in the documentation, it typically means a session. A single person who is a user could have multiple sessions.

Although licensing is now by CPU, you must still specify a value in the Maximum Number of Users field in the VCT. Because each user consumes Sun MTP session resources, set this field based on your region's requirements for terminals, printers, and intersystem communications (ISC) sessions.

Upgrading From Earlier Releases

If you are upgrading from a release earlier than Release 8.0.0, you must convert the VSAM catalog and the Sun MTP tables. The kixcnvtcat80 utility is used to convert the catalog, and the kixcnvtbl80 utility is used to convert the tables. Refer to the Sun Mainframe Transaction Processing Software Reference Guide for detailed descriptions.

Read the chapter on migration in the Sun Mainframe Transaction Processing Software Installation Guide, and make sure to perform the tasks on the migration checklist.

Migration Issues for This Release

This section contains information about changes to the software that might require you to recompile maps or programs, or make changes to custom scripts.

`kixbms` Behavior

Previously, the kixbms utility did not correctly handle maps containing the OUTLINE or SOSI extended attributes.

Therefore, if your maps contain OUTLINE or SOSI extended attributes, you must recompile the maps with the kixbms utility.

See also COBOL and PL/I Copybooks Generated by kixbms for other changes related to kixbms.

`kixstop` Behavior

In previous releases of Sun MTP, the kixstop command did not properly adhere to the normal shutdown and immediate (panic) shutdown process. Now, any command to shut down the region normally (kixstop, CEMT PERFORM SHUT, and PF3 on the Development System main menu) will wait for all transactions to complete before bringing down the region. If there is a long-running transaction or a conversational transaction, the region will wait until these transactions are finished. At this point, the only way to shut down the region is to execute the kixclean command.

If you want the old functionality of either kixstop (which forced the region to stop by aborting running transactions), CEMT PERFORM SHUT, or PF3 (where these commands immediately shut down the region), you must use one of the following commands:

kixstop -i

CSMT SHUT,YES

CEMT PERFORM SHUT IMMEDIATE

As a result of this change, the following sections in the documentation are no longer accurate:

In the Sun Mainframe Transaction Processing Software Administrator's Guide, in Chapter 2:

In the section "CSMT," the description of the CSMT SHUT,YES transaction should be "Shuts down the region and forces all the users to log off. Active transactions are rolled back."

In the section "Setting the System State," the CEMT SET SYSTEM SHUT and CEMT SET SYSTEM SHUT IMMEDIATE transactions are not implemented.

In the Sun Mainframe Transaction Processing Software Configuration Guide, in Chapter 3:

In the section "Shutting Down the Sun MTP Server," the description of step 1 ("Invoke the CEMT PERFORM SHUTDOWN transaction ..."), should be "Transactions that are active will be allowed to complete normally. No new transactions are allowed to be submitted. No new users can log in."

C Language Programs That Contain `EXEC CICS INQUIRE TDQUEUE` Statements

If you are upgrading from a release earlier that Sun MTP 8.0.0 patch level 4, you must recompile all C language programs that use the EXEC CICS INQUIRE TDQUEUE command.

`ABORT.prt` Files

In previous releases of the software, an ABORT.prt file would be created if a region terminated abnormally. Now, if a region crashes, the unikixmain process executes the kixsnap command automatically, which gathers trace and dump information. All the information that was written to ABORT.prt is now written to the kixsnap snapshot files, and the ABORT.prt file is no longer created. This software change caused the following error message to change:

Old: KIX0157F Writing abort dump to $KIXSYS/ABORT.prt

New: KIX0157I Executing %s command

Future Patch Releases

Check the SunSolve^SM web site on a regular basis for any Sun MTP patches that are available, and apply the recommended patches. The web site is:

http://sunsolve.sun.com

Note - When you download patches to this release at some future time, make sure to read the updated_user_doc.txt file, which is shipped in the $UNIKIX/doc directory. It contains important documentation about the fixes included in the patch release.