IBM CICS Universal Client Version 7.0.1.1 - README for Windows

IBM CICS Universal Client Version 7.0.1.1 - README for Windows

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 must be run in a command prompt window by a user with administrator 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

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 a user with Administrator authority and for Windows Vista, elevated authority is required.

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 Windows, Java 2 Technology Edition, Version 5 Service Release 4.

To install the Java Runtime Environment, run the command:

ibm-java2-jre-50-win-i386.exe

During Java Runtime Environment installation, you can select to install this Java as the system default. If you choose not to install this Java as the system default, you must run the ctgjava.exe command to specify where the Java executable is located.

TOLERATION FOR WINDOWS VISTA

LIMITATIONS

The use of CICS UC is only supported running in a user session.

Fast User Switching is not supported while the CICS UC product is running.

TCP62 Communications and Named Pipe Communications are not supported on Windows Vista.

The C++ API is not supported on Windows Vista.

When a machine is being upgraded from a previous version of Windows to Windows Vista, the CICS UC product must be uninstalled prior to the Windows upgrade.

OPERATIONAL GUIDANCE

The minimum level of Java required for running CICS UC Configuration tool on Windows Vista is Service Release 4 of IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5.

To configure java for CICS UC the ctgjava utility must be invoked from an elevated command prompt.

On Windows Vista systems the CICSCLI environment variable must be used to name the configuration file. Create the directory specified in the CICSCLI environment variable if it does not exist. The CICSCLI environment variable must be defined for any user who starts or configures the CICS UC product. When setting the CICSCLI environment variable at a Windows command line, Windows auto-completion adds double quotes around the path value. The double quotes must be removed, for example:

CICSCLI=C:\ProgramData\IBM\CICS Universal Client\ctg.ini

Log and trace files for the Client daemon process must be defined with a fully qualified file name, for example:

C:\ProgramData\IBM\CICS Universal Client\cicscli.log

The user who starts the CICS UC product must have write access to the log files.

The ports required by the CICS UC network protocol drivers must be available to the user who starts the CICS UC product. Configuring the system Firewall requires elevated access.

CHANGES TO WINDOWS SERVICES ON NON VISTA PLATFORMS

IBM CICS UNIVERSAL CLIENT SERVICE

The Client daemon service is configured during installation so that users who are members of the "Users" group will be able to start and stop the service.

A utility to change the permissions for the Client daemon service is included with CICS UC. The utility and accompanying documentation are installed as:

<install_path>\bin\resource\cs70.exe
<install_path>\bin\resource\cs70readme.txt

POP-UP MESSAGE WINDOWS

The Client daemon service interacts with the desktop, allowing pop-up message windows to be displayed using the default settings.

To disable pop-up message windows, open the Windows Services control panel and uncheck the 'Allow service to interact with desktop' box on the 'Log on' tab of the properties box for the "IBM CICS Universal Client" service. Also run the Configuration Tool to edit ctg.ini and deselect the 'Enable pop-up windows' field on the Client daemon resources panel.

KNOWN ISSUES DURING INSTALLATION OR UNINSTALLATION

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

When using a response file to uninstall silently, the response file must be given a fully qualified file name.

CANCELLING AN INSTALL OR UNINSTALL ON WINDOWS VISTA

When the installer or uninstaller program is cancelled on Windows Vista the 'Program Compatibility Assistant' will start. Select 'The program installed correctly' to cancel the assistant.

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

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

PK39201
CICS Transaction Gateway install fails with error that msvcr71.dll is missing

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

PK30144
An invalid JVM can be specified and not corrected

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

PK42555
Non administrator user can not start CICS UC service

PK42564
CICS TG trace outputs data lengths incorrectly

PK43797
Output directory cannot be defined when building CICS TG samples

APARS INCLUDED IN 7.0

PK27119
ECI state calls can return incorrect status information if workload manager is active

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 2009. All rights reserved.
For legal information, see http://www.ibm.com/legal/copytrade.shtml