IBM CICS Universal Client Version 7.0.1.1 - README for Linux on Intel

IBM CICS Universal Client Version 7.0.1.1 - README for Linux on Intel

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

This file contains important information about the IBM CICS Universal Client (CICS UC) 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

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 UC applications 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 UC 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 UC 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 UC install path>/ctgfix/ctgfix.hlp.

INSTALLING THE PRODUCT

Installation and uninstallation must be done by the root user.

Before you install, 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 UC. A umask of 077 restricts access to the root user that installed the CICS UC; a umask of 022 allows all users to run the CICS UC.

USING THE INSTALLSHIELD WIZARD

This section is an aid for installation, the following details list the commonly used options. More information on how to use the installer can be found in the section "Known issues during installation or uninstallation" and the Eclipse Information Center.

To install the CICS UC launch the InstallShield wizard:

installer

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

installer -console

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

installer -silent -V licenseAccepted=true

INSTALLING THE JAVA RUNTIME ENVIRONMENT

The supplied version of Java is IBM 32-bit Runtime Environment for Linux on Intel architecture, Java 2 Technology Edition, Version 5 Service Release 4.

To install the RPM package file, run the command:

rpm -i -v ibm-java2-i386-jre-5.0-4.0.i386.rpm

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

USING IBM COMMUNICATIONS SERVER FOR LINUX REMOTE API CLIENT 6.3

IBM Communication Server for Linux Remote API Client 6.3 and above no longer requires the LD_PRELOAD of the Linux streams (LiS) library. Set LD_PRELOAD to an empty string, for example:

export LD_PRELOAD=""

SECURITY-ENHANCED LINUX (SELINUX)

CICS UC does not support Security-Enhanced Linux.

INSTALLING ON RED HAT ENTERPRISE LINUX (RHEL) 5

To install and run on RHEL 5 the CICS UC product depends on shared libraries that are not installed by default. The RPM's that contain these libraries are:

libXp-1.0.0-8
compat-libstdc++-33-3.2.3

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.

INCORRECT PROGRESS DISPLAYED WHEN MIGRATING FROM OLDER VERSIONS

When upgrading from earlier versions of the CICS UC the installer program does not display progress correctly; ignore the progress display. The installation is unaffected by the incorrect progress display.

RECORDING A RESPONSE FILE

If you create a response file using the installer "-options-record" option with the "Custom" installation selected, you must modify the file before you use it. Find the line:

-W setupTypes.selectedSetupTypeId=custom

and replace it with:

-W setupTypes.active=false

If you do not modify the response file before use, all features will be installed.

USING A RESPONSE FILE

When installing silently the license must be accepted, this is done with the -V option. The following command is for silent installation with a recorded response file.

installer.exe -options "response_file_name" -silent -V licenseAccepted=true

'NO SUCH FILE' ERROR MESSAGE OUTPUT DURING UNINSTALLATION

Messages similar to the following might be output during uninstallation:

cat: /tmp/istemp2752209095151/chunk2: No such file or directory
rm: cannot remove `/tmp/istemp2752209095151/chunk1': No such file or directory
rm: cannot remove `/tmp/istemp2752209095151/chunk2': No such file or directory

The uninstallation completes successfully, and you can ignore these messages.

UNINSTALLATION FAILS WITH 'ENGINE IS MISSING' MESSAGE

If the uninstallation is not performed by a user ID with root privileges, the uninstallation fails, and the following error might be output to the console.

"engine is missing (/root/InstallShield/Universal/common/Gen1):"

The CICS UC must be uninstalled by a user with root privileges.

SERVICE AND UPDATES

Below is a list of APARs included in this version of the CICS Universal Client. All APARs listed are applicable to this platform. Full details can be found on the support pages: http://www-306.ibm.com/software/htp/cics/cuc/support/

APARS INCLUDED IN 7.0.1.1

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

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

PK54693
Client daemon tracepoint CCL5896 contains invalid values for the error code.

PK55050
Client daemon may not correctly report status of a TCP62 link

PK55173
Invalid userid or password on ECI request results in RC-9 ECI_ERR_SYSTEM_ERROR returned by CICS TG

PK56203
After a keepalive timeout on a TCP62 connection, the client daemon is unable to reconnect to the CICS server.

PK57381
Backslash in trace filename prevents memory mapped wrapping trace starting

PK60170
ECI timeout causes a DFHIE1001 bracket protocol violation message

PK62107
CICS TG receives SIGSEGV when attemping to connect to CICS using TCP/IP

PK62540
TCP/IP Keepalive flows are not active on TCP62 connections resulting in unexpected connection terminations.

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

PK68109
Network sockets not closed

PK68968
Fixes to the TCP/IP protocol driver

PK68969
Log message CCL2010 displays incorrectly formatted return code

PK69132
If a Mode Name is rejected by CICS, the CICS TG Client daemon receives a TCP/IP error when releasing the connection.

PK69840
Client daemon appears to become unresponsive during startup

PK70913
CICS Client trace function not able to track when CICS_EPITERMINATE call exits

APARS INCLUDED IN 7.0.1

PK33952
Client daemon may hang when tracing is enabled.

PK33954
The CICS TG hangs when Client daemon tracing is enabled

PK32530
CICS TG may fail to connect to CICS on iSeries

PK30770
Expired passwords cannot be changed using PEM under CICS TG with the TCP62 protocol

PK36915
After a send() call fails, reconnect attempts are not occurring

PK40853
Duplicate PCID's being sent to VTAM

PK42521
Incoming ATI causes Client daemon abend

PK42522
Multiple ATI transactions through EPI applications fail

PK42524
Client daemon ends when unable to establish a connection to CICS

PK42562
CICS TG uses high CPU during network problems

PK42564
CICS TG trace outputs data lengths incorrectly

PK45302
CICS TG Client daemon hangs intermittently on multi-processor machines

PK47041
CICS TG receives an out of memory error from pthread_create()

APARS INCLUDED IN 7.0

PK16738
Client driver triggers bracket protocol error on CICS host.

PK23200
CICS TG and CICS UC fail to reconnect to CICS after a network outage.

PK27139
Socket send() hangs due to hardware problem. Added timeout to call in the cclclnt.

PK27140
Client daemon log message CCL2010 does not always contain full diagnostic information and appears corrupt

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.

LINUX COPYRIGHT STATEMENTS AND LICENSING NOTES

This product uses the following libraries from the glibc package:

ld.so, libc.so, libm.so, libdl.so, libnsl.so, librt.so and libpthread.so.

Refer to the glibc package on your machine for the various copyright statements and licensing terms for these libraries.

This product also uses libncurses.so from the ncurses package. Again, refer to this package on your machine for the copyright statement and licensing terms applicable to this library.

IMPORTANT NOTE:

Your use of the libgcc or libstdc++ packages will be subject to the GNU GPL licence terms which could require you to provide source code in certain circumstances. In this connection, please bear in mind that IBM will not supply source code, e.g. for the CICS UC C++ libraries.


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