IBM CICS Transaction Gateway Version 7.1.0.4 - README for HP-UX Itanium

IBM CICS Transaction Gateway Version 7.1.0.4 - README for HP-UX Itanium

The product documentation is provided as an Eclipse Information Center available at: http://publib.boulder.ibm.com/infocenter/cicstg/v7r1m0/index.jsp

This file contains important information about the IBM CICS Transaction Gateway (CICS TG) that might not be available in the Eclipse Information Center.

This readme file is available in plain text and HTML. Both files contain the same information. After installation the files are included in the <install_path> directory.

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

SUMMARY OF TOPICS

NEW FEATURES

SNA support on HP-UX

Additional statistics

Interact with request monitoring exits dynamically

Remote Statistics API

Please see the product documentation for further information on these features.

INSTALLING AND UNINSTALLING THE FULL PRODUCT

This section applies to running the full product installer which either installs the product or replaces an existing version of 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 root user.

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 the CICS TG; a umask of 022 allows all users to run the CICS TG.

Before running the CICS TG installer it is strongly recommended that you shut down all programs running on your system.

INSTALLING THE FULL PRODUCT

To install the CICS TG launch the InstallShield wizard:

installer

To install the CICS TG in console mode launch the InstallShield wizard with the -console option:

installer -console

To install the CICS TG with no user interaction launch the InstallShield wizard with the -silent and -V licenseAccepted options:

installer -silent -V licenseAccepted=true

Further information on how to use the installer can be found in the the Eclipse Information Center. Known issues are documented in this readme file.

UNINSTALLING THE FULL PRODUCT

Use the command:

ctguninst

GUI mode uninstall can be launched using the following command:

ctguninst -swing

Console mode uninstall can be launched using the following command:

ctguninst -console

Unattended uninstall can be launched using the following command:

ctguninst -silent

INSTALLING AND UNINSTALLING A 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 shut down any local CICS TG applications, the Gateway daemon and then the Client daemon.

It is strongly recommended that you shut down all programs running on your system before running the Fix Pack utility.

INSTALLING THE FIX PACK

Change to the directory where the Fix Pack has been unpacked and issue the following command:

ctgfix

The installer will prompt for confirmation before installing. Enter 'y' to proceed. If you do not wish to be prompted for confirmation, issue the command:

ctgfix -y

During installation, the Fix Pack utility creates a log file named <CICS TG 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.

If the CICS TG is using messages that are not in English, issue the ctgmsgs command to switch to your language of choice:

ctgmsgs XX code_set

For help on the ctgmsgs command, issue the command:

ctgmsgs -?

UNINSTALLING A FIX PACK

Change to the <CICS TG 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. If you do not wish to be prompted for confirmation, 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 <CICS TG 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.

INSTALLING THE JAVA RUNTIME ENVIRONMENT

The supplied version of Java is HP 32-bit Runtime Environment for J2SE HP-UX 11i platform, adapted by IBM for IBM software, Version 5 Service Release 7.

Create a directory for the Java Runtime Environment files to be extracted to. Expand and extract the Java Runtime Environment from the package file into this new directory. The following example uses the Java default location:

mkdir /opt/java1.5
cd /opt/java1.5
gzip -cd <package_path>/hpia32devhybridifx-20080413-jre.tar.Z | tar -xvf -

After installing the Java Runtime Environment read the Java documentation for guidance on how to define the PATH and other environment variables.

CONFIGURING SNA ON HP-UX ITANIUM

The LD_LIBRARY_PATH environment variable must include the path of the 32-bit SNA libraries. If this is not set the Client daemon will fail to successfully load the SNA protocol driver (cclibmsn.a). The default location for the 32-bit SNAPlus2 libraries is /opt/sna/lib/hpux32.

CICS TG STATISTICS API DOCUMENTATION

Reference documentation for the statistics API is included in the information center. The documentation is also included as part of the CICS TG installation, in <install_path>/docs/ctgstatsdoc.zip. To view the documentation, expand the contents of the ZIP file into a suitable directory and view file 'index.html' with a Web browser.

CICS TG SERVER NAMES IN STATISTICS QUERIES

If the ctg.ini configuration file contains server names which have one or more underscore characters '_' in them, when the server name appears in a ctgadmin command or statistics API query, any underscore characters will have been replaced by a minus character '-'.

IP INTERCONNECTIVITY PROTOCOL (IPIC)

CICS TS v3.2 has introduced a new IP interconnectivity protocol as an alternative to that provided by ISC or MRO. Using IPIC, CICS Transaction Gateway v7.1 adds support for the Channels and Containers programming model which provides relief from the 32k commarea limit; 2-phase commit (XA) via the JCA Resource Adapter and enhanced security options. IPIC also provides request tracking facilities and SSL support in Local mode.

CICS TS SUPPORT FOR IPIC

IPIC is supported to CICS TS version 3.2 regions with the following APARS applied:

CICS TS APARS REQUIRED FOR IPIC SUPPORT

PK55716
Resync XID data incorrectly sent by CICS TS 3.2 to the CICS Transaction Gateway when using IPIC connections

PK49015
CIST transaction hangs during drain processing of one-way IPCONN resources

PK49017
Multiple SYNCONRETURNS over IPIC connection from single task fails TERMERR, RESP2=17

PK49021
Sending a bit container with CCSID=0 on a DPL with channel causes AITJ abend

PK49116
Protocol IPIC requires TCP keepalive to be set

PK49490
Invalid container data returned on DPL from CTG

PK51587
Message DFHIS1027 security violation from z/OS CICS using CICS Transaction Gateway

PK53783
Data conversion codepage(-1) not done when calling CICS TS over IPIC

PK57726
XA Recovery fails with security enabled

PK65134
Per-transaction shunting causes transaction rollback

PK85173
Using CTG with IPIC a DPL program runs in the AOR under tranid CSMI when defined with a specific tranid (XXXX)

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 the CICS TG has started. This is expected behavior, and does not mean that the CICS TG has failed to start. To determine if the CICS TG started correctly, listen for the message:

'CTG6512I CICS Transaction Gateway initialization complete'.

If the CICS TG did not start successfully, one of the following messages is output:

'CTG8821E The CICS Transaction Gateway was unable to start the Client daemon'.
or
'CTG6513E CICS Transaction Gateway failed to initialize'.

KNOWN ISSUES DURING INSTALLATION OR UNINSTALLATION

THE GRAPHICAL USER INTERFACE STOPS RESPONDING

When installing with the graphical user interface the installer program may stop responding. If this problem occurs, issue "Ctrl C" to end the installer program and retry the installation using the "-console" option.

SERVICE AND UPDATES

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

APARS INCLUDED IN 7.1.0.4

PK69017
ECIConnection.close() Javadoc incorrectly states when a ResourceException will be thrown

PK69840
Client daemon appears to become unresponsive during startup

PK71172
Moving a container between channels in CICS causes the CICS TG to ignore the modified container

PK72228
The Client daemon terminates unexpectedly with CCL2010E Internal transport error (Function = 'FaarqPutMsg', Error Code = '-5010')

PK76390
Client daemon issues CCL2012E after CICS abends a transaction

PK76458
Terminal definitions are not released in CICS if an emulator terminates when the Client daemon is at MAXREQUESTS

PK78293
Modified data tag reset on some EPI screens

PK82305
Improve diagnostic information available when a signal occurs in the Client daemon

PK82711
IPIC container data corruption at 122750 bytes

PK82718
CICS TG reports errors on TCP/IP connections to CICS servers

PK83549
Short mirror transaction names fail over IPIC

PK85498
Access violation in cclclnt.exe when running an EPI workload and the CICS server becomes unavailable

PK88549
Improve serviceability of IPIC protocol handler

PK89000
Servername can not contain ':','/' OR '#' characters. Results in error CTG6670E Invalid chars in APPLID for ISC connection

PK89359
Multiple instances of message CCL1048E written to the Client error log, reporting error code -4 from FaarqGetMsg.

PK91072
CICS TG fails to start when TCP/IP localhost is not defined.

PK96066
When using IPIC, an ECI request routed to a remote CICS server runs under the default mirror transaction ID

PK97502
Using the getStats() API causes an access violation if a large number of CICS servers have been defined

PK98202
CICS TG causes exception in TXSeries when using multiple containers

PM00653
CICS TG attempts to process incorrect TCP/IP data as a normal request

PM01320
ClientLocation missing from all XA flows in request monitoring exits

PM03923
CICS TG returns excess data when using an IPIC connection to CICS

PM03931
CICS TG writes messages CCL3315E and CCL3227E to the client error log after transactions have timed out or abended

PM03933
Message CCL3102E written to the client error log file when running a heavy workload

PM06643
Message CCL4406E is written to the client error log when a CICS server becomes unavailable

APARS INCLUDED IN 7.1.0.3

PK77334
Cicsterm abends when running the CICS supplied CSTD transaction on a TXSeries region

APARS INCLUDED IN 7.1.0.2

PK54463
The exclamation mark in a valid password returns ECI_ERR_SECURITY_ERROR (rc=-27)

PK57381
Backslash in trace filename prevents memory mapped wrapping trace starting

PK57891
AZTI abend following failover when using VTAM generic resources for EPI applications

PK60170
ECI timeout causes a DFHIE1001 bracket protocol violation message

PK60594
A mixed case protocol definition for ConnectionURL parameter results in a communication error and IOException

PK60925
The CICS TG information center incorrectly documents the protocol for the IPIC service as ECI

PK62925
An incorrect CCSID is used when non-ASCII CHAR containers are exchanged with CICS

PK65133
Update to IPIC transaction flows

PK66998
GetConnection() is returning a null when it should return an exception

PK67318
APPLID value ignored and '*' is used, resulting in an APPLID generated by CICS being used.

PK67935
Client dameon not reconnecting correctly after third occurrence of send call failure

PK68109
Network sockets not closed

PK68938
Support for SNA on the HP-UX platform

PK68947
Statistics to identify system information

PK68949
CICS TG Statistics API does not connect to CICS TG using a different TCP/IP stack

PK68937
Enhancements to request monitoring user exits

PK68962
Fixes to the IPIC protocol driver

PK68968
Fixes to the TCP/IP protocol driver

PK68969
Log message CCL2010 displays incorrectly formatted return code

PK68970
Enabling Client daemon trace causes a stack overflow error

PK68971
Call to getIdQuery() results in segmentation violation

PK68972
Exception generated when loading ctgjni.dll

PK68973
CTGXid class has an incorrect constructor

PK68975
CICS TG log file not written to specified destination

PK68976
Return code incorrect when worker thread allocation times out

APARS INCLUDED IN 7.1.0.1

PK59674
CICS TG ping processing causes down level client to be unexpectedly disconnected

PK59463
Update to version of ccf2.jar shipped with CICS TG

PK59386
CICS TG does not identify the level of fix pack installed

APARS INCLUDED IN 7.1

PK36000
CICS TG hangs when message queues fill on unix operating systems

PK36914
Client daemon stops processing requests under heavy workload

PK45841
SSL protocol handler shuts down after 50 consecutive connection failures

PK48708
The default behaviour of UPPERCASESECURITY in CICS TG is incorrectly documented

PK51302
Allow to set '0' in SRVRETRYINTERVAL

PK51695
MAXCONNECT not logged when hit

PK52648
CICS TG does not use unique network UOW identifiers using the SNA protocol driver

PK52798
In local mode, CICS ECI resource adapter unable to handle some special characters in password causing security failure.

Contact your IBM Support organization for service and updates to the product.

THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The Program includes "UnZipSFX stub" software from the Info-Zip group which is Copyright (c) 1999-2002, Info-ZIP. All rights reserved. IBM did not modify the UnZipSFX software. There are no extra charges or costs due to the use of this code, and the original compression sources are freely available from http://www.info-zip.org/pub/infozip/ or ftp://ftp.info-zip.org/pub/infozip/ on the Internet.

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