IBM CICS Universal Client Version 7.1.0.5 - README for Solaris

IBM CICS Universal Client Version 7.1.0.5 - README for Solaris

The product documentation is provided as an Eclipse Information Center available at: http://publib.boulder.ibm.com/infocenter/cicsuc/v7r1m0/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

NEW FEATURE - SNA SUPPORT ON HP-UX

See the product documentation for further information on this feature.

NEW CICSPRNT AND CICSTERM COMMAND OPTIONS

CICSPRNT OPTION TO PRINT BLANK LINES

A new -b option is available on the cicsprnt command. By default, cicsprnt does not print blank lines. A blank line is defined as a line that contains only null characters or non-displayable fields, or is undefined in the BMS map. This option causes blank lines in the data stream to be printed, for example enter the command:

cicsprnt -b

CICSTERM SUPPORT FOR ADDITIONAL DEFAULT COLORS

A new -e option is available on the cicsterm command. The -e option specifies that when extended attributes are included in a 3270 datastream received by cicsterm and no color attribute is set, the color of a field is determined by both the intensity and protection attributes. The colors used to display the field are then determined by the normal_unprotected, intensified_unprotected, normal_protected and intensified_protected definitions in the color mapping file. By default, when this option is not specified, the 3270 datastream contains extended attributes and no color attribute is set, the color of fields is determined by the default and default_highlight definitions in the color mapping file. Example command useage:

cicsterm -e

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 UC installer the Korn shell must be installed on your system.

Installation and uninstallation must be done by the root user.

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 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.

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

INSTALLING THE FULL PRODUCT

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

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 CICS UC applications and 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 UC 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.

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 IBM 32-bit Runtime Environment for Solaris, Java 2 Technology Edition, 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 /usr/java5
cd /usr/java5
gzip -cd <package_path>/soldevhybridifx-20080403-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.

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.

SERVICE AND UPDATES

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

APARS INCLUDED IN 7.1.0.5

PM54534
Message CCL1048E written to Client log on shutdown

PM53769
CICS TG ends unexpectedly when a connection to a CICS server ends

PM46110
The CICS TG Client daemon can become unresponsive if a network socket error occurs

PM37312
ESI request over SNA fails to complete because the CICS server is unavailable

PM34809
cicsterm support for additional default colors when using a 3270 datastream with extended attributes

PM32332
Message CCL7060I is displayed incorrectly by cicsterm

PM29332
Screen representations in a Client daemon trace formatted with the detailed option of cicsftrc might be incorrect

PM28737
The cicsprnt 3270 terminal emulator does not have an option to enable printing of blank lines

PM24817
Mouse double-clicks in the cicsterm 3270 terminal emulator resend the previous AID

PM16908
Send() timeout causes delay in CICS TG processing.

APARS INCLUDED IN 7.1.0.4

PK69840
Client daemon appears to become unresponsive during startup

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

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

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

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

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

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

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

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

PK68975
CICS TG log file not written to specified destination

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

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

PK51302
Allow to set '0' in SRVRETRYINTERVAL

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

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

PK42525
CICS UC 7.0 upgrades while CICS UC 6.0.2 still active

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.


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