IBM CICS Transaction Gateway for Multiplatforms Version 8.0.0.1 - README for Solaris

This readme file contains important information about the IBM CICS Transaction Gateway for Multiplatforms (CICS TG) that might not be available in the information center.

The product documentation is provided in the information center at: http://publib.boulder.ibm.com/infocenter/cicstgmp/v8r0/index.jsp

This readme file is available in plain text and HTML. Both files contain the same information. After installation the files are included in the /opt/IBM/cicstg directory.

The term <install_path> is used in file paths to represent the directory where you installed the product.

The text version of this file is suitable for use with a screen reader or braille device.

SUMMARY OF TOPICS

INSTALLING AND UNINSTALLING THE PRODUCT

Before running the CICS TG installer the Korn shell must be installed on your system.

Installation and uninstallation must be done by the user with root authority. Before you install the product, check the root user's umask to ensure that files created during the installation are readable by the user IDs that will run the CICS TG. A umask of 077 restricts access to the root user that installed CICS TG; a umask of 022 allows all users to run CICS TG.

Ensure that 240 MB of temporary storage is available to successfully complete installation.

It is recommended that at least 100 MB of additional storage is available in the location where CICS TG is installed to allow diagnostic information to be collected if required.

INSTALLING THE PRODUCT

Install can be run in GUI, console or unattended mode. The default mode is GUI.

GUI mode installation can be launched using the following command:

installer

Console mode installation can be launched using the following command:

installer -i console

Unattended installations can be launched using the following command:

installer -i silent -DLICENSE_ACCEPTED=true

UNINSTALLING THE PRODUCT

Use the command:

ctguninst

By default the CICS TG uninstall command matches the mode used at installation. You can override the default mode to run in GUI, console or unattended mode.

GUI mode uninstall can be launched using the following command:

ctguninst -i swing

Console mode uninstall can be launched using the following command:

ctguninst -i console

Unattended uninstall can be launched using the following command:

ctguninst -i silent

INSTALLING AND UNINSTALLING THE FIX PACK

This section applies to running the Fix Pack utility which updates an existing installation of the product.

The Fix Pack utility runs in console mode and must be run by a user with root privileges. Before installing or uninstalling the Fix Pack shutdown any local CICS TG applications, the Gateway daemon and then the Client daemon.

INSTALLING THE FIX PACK

To install, change to the directory to which the Fix Pack has been unpacked and issue the following command:

ctgfix

The installer will prompt for confirmation before installing. Enter 'y' to proceed. To perform an unattended install, issue the command:

ctgfix -y

During installation, the Fix Pack installer creates a log file named <install_path>/ctgfix/ctgfix.log. The log file contains details of each file that is updated by the Fix Pack, and details of any errors. Further information about the error messages is available in text file ctgfix.hlp located where the Fix Pack has been unpacked.

After installing the Fix Pack, symbolic links must be redefined, issue the command:

ctgsymlinks -add /opt/IBM/cicstg

If the CICS TG was originally installed in a language other than English, now issue the ctgmsgs command to switch back to that language:

ctgmsgs XX code_set

where XX is the two character message language. Refer to the CICS Transaction Gateway for Multiplatform Information Center for further details.

UNINSTALLING THE FIX PACK

To uninstall, change to the <install_path>/ctgfix directory and issue the following command:

ctgfix -u

The Fix Pack utility will prompt for confirmation before uninstalling. Enter 'y' to proceed. To perform an unattended uninstall, issue the command:

ctgfix -u -y

During uninstall, the Fix Pack utility appends to the ctgfix.log file. The log file contains details of each file that is restored by the Fix Pack, and details of any errors. Further information about the error messages is available in text file <install_path>/ctgfix/ctgfix.hlp.

DETERMINING THE PRODUCT VERSION

After installing the Fix Pack, determine the product version by issuing the command:

cicscli -v

Components that have not been updated by this Fix Pack will display the original version.

CONFIGURING THE JAVA RUNTIME ENVIRONMENT

Before CICS TG can be started a Java Runtime Environment must be available, this can be specified by defining the CTG_JAVA environment variable or by defining the location of java on the PATH. The CTG_JAVA variable identifies the java executable, for example:

export CTG_JAVA=/opt/IBM/cicstg/jvm16/bin/java

UPGRADING FROM AN EARLIER VERSION OF CICS TG

Configuration files that worked with previous releases might not work after upgrade; configuration checking has been improved to ensure that the values used by CICS TG are the intended ones. For more information refer to the "Upgrading" section of the information center.

CICS SERVER SUPPORT FOR IPIC

IPIC is supported to CICS TS version 3.2 and later, and TXSeries version 7.1 and later. Ensure that your CICS server has the latest IPIC maintenance applied.

USING THE JCA CICS RESOURCE ADAPTERS WITH NONMANAGED APPLICATIONS

Outside a J2EE environment, you must ensure that the following Java extensions are available:

* Java Authentication and Authorization Service (JAAS), required for the 
  EPI resource adapter. 
* J2EE Connector Architecture (JCA) 1.5 Connector class file, required for
  the ECI resource adapter. 
* Java Transaction API (JTA), required for XA transactions.

Note: JAAS is included with IBM JREs and JDKs by default. The JCA 1.5 Connector class file and the JTA libraries are available for download from the Sun Java Web site.

ACCESSIBILITY FEATURES

STARTING THE GATEWAY DAEMON FROM A COMMAND PROMPT USING A SCREEN READER

In some Telnet sessions, the screen reader might re-read CICS TG log output or the command prompt, after CICS TG has started. This is expected behavior, and does not mean that CICS TG has failed to start. To determine if CICS TG started correctly, listen for the message:

'CTG6512I CICS Transaction Gateway initialization complete'.

If CICS TG did not start successfully the following message is output:

'CTG6513E CICS Transaction Gateway failed to initialize'.

KNOWN ISSUES DURING INSTALLATION OR UNINSTALLATION

USING A TURKISH LOCALE

When installing or uninstalling you need to use uppercase parameters to control the mode. For example:

installer -i SILENT -DLICENSE_ACCEPTED=true

GZIP MUST BE AVAILABLE ON THE PATH

When installing you must ensure gzip is available on the PATH. If gzip is not available you will see messages similar to:

$ ./installer -i console
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
gzip not found
/tmp/install.dir.467026/AIX/resource/vm.tar.Z: not in compressed format
./installer[581]: gzip:  not found
The included VM could not be uncompressed (GZIP/UNCOMPRESS). Please try to
download the installer again and make sure that you download using 'binary'
mode.  Please do not attempt to install this currently downloaded copy.

SERVICE AND UPDATES

Below is a list of APARs included in this version of the CICS Transaction Gateway for Multiplatforms. Full details can be found on the support pages: http://www.ibm.com/software/htp/cics/ctg/support/

APARS INCLUDED IN 8.0.0.1

PM23319
Unexpected results when using CICS TG trace
PM22622
ECI requests fail after restart of CICS TG
PM22621
ChannelNameException thrown by Gateway daemon when a zero length channel or container name is used
PM22618
Install is corrupted if the install path contains DBCS characters
PM20958
CICS TG might not generate unique correlators for use with CICS
PM20903
Applications cannot be compiled using Microsoft Visual Studio 2010
PM20895
Miscellaneous problems when connecting to CICS over IPIC
PM20887
Errors in documentation and messages
PM20882
Miscellaneous problems when using the Java ECI API
PM20871
Miscellaneous problems when running XA transactions
PM19800
Backslash in trace file name prevents memory mapped wrapping trace from starting
PM18876
CICS TG V7.2 ECI resource adapter prevents the use of MappedRecord with COMMAREA applications
PM16908
Send() timeout causes delay in CICS TG processing.
PM13698
The configuration tool allows non-valid log file parameters to be defined, preventing the Gateway daemon from starting

APARS INCLUDED IN 8.0.0.0

PM10467
Extended mode ECI requests over IPIC with large containers fail with abend AXTG reported to the client and abend AITJ in CICS
PM10466
CICS TG fails to reconnect to CICS using an IPIC connection and the client application receives an ECI_ERR_NO_CICS
PM10465
When a COMMAREA is returned unchanged by a target CICS program, over an IPIC connection, it contains only nulls
PM08404
A client application becomes unresponsive after specifying an incorrect mirror transaction with a large channel over IPIC
PM06919
NoSuchAlgorithmException thrown during connection to Gateway daemon using SSL protocol
PK87193
Using the statistics and ECI V2 APIs in the same application causes a segmentation fault

PREVIOUS MAINTENANCE

CICS Transaction Gateway for Multiplatforms V8 includes all fixes previously shipped in fix pack V7.2.0.2. Details of this fix pack can be found in the following document: http://www.ibm.com/support/docview.wss?uid=swg21386563

Future service and updates to CICS TG will be made available on Fix Central at http://www.ibm.com/support/fixcentral/


© Copyright IBM Corporation 2010. All rights reserved.
For legal information, see http://www.ibm.com/legal/copytrade.shtml