CICS Universal Clients Current Service Status
************************************************************************
* IBM CICS Universal Client for Solaris - README v3.1.2 *
************************************************************************
Welcome to the IBM CICS Universal Client ...
This file contains important information about the IBM CICS Universal
Client for Solaris that may not be available in the printed documentation.
Summary of Topics
=================
- Installation issues
- Java Runtime Environment
- Adobe Acrobat Reader
- CICSTERM Behaviour and Signon Capable Terminals
/****************************************************************************/
/* WARNING: The default CICSTERM behaviour changed for release 3.1 and later*/
/* See below for details. */
/****************************************************************************/
- CICS TS v1.3 Servers
- TX Series Servers
- Security on OS/390 Servers
- EPI Purge Terminal Restriction
- XTERM and function keys
- Running the CICS client over telnet
- Using X-Windows clients
- Timeout processing on TCP/IP protocol
- DBCS Support in the COM and C++ Libraries
- Update to Client/Server Programming Book
- Updates to C++ and COM Automation programming books
- Disconnect Documentation
- exObject method in CclException Class
- SNA driver requirements
- Patches required for the SunLink 9.1 product
- Using C++ version 5
- Patches required for Solaris C++ 5
- Compiling C++ applications that use the C++ libraries
- Tracing enhancements
- Service and Updates
- Service process for JREs on Solaris
- Giving feedback
Installation Issues
===================
Java Runtime Environment
------------------------
The Java Runtime Environment is required to run the GUI configuration
tool (ctgcfg). Version 1.1.7 is recommended. Note, JDK 1.2.2
(version 1.2.2-05a) is supported, but not Java 3.
If this product has been supplied on CD the Java Runtime Environment is
included. It can be found in the directory JRE/Solaris with
the filename Solaris_JRE_1.1.7_08_sparc_ibm.tar. To install:
1. Use the command: tar -xvf Solaris_JRE_1.1.7_08_sparc_ibm.tar
2. Move the Solaris_JRE_1.1.7_08_sparc_ibm directory to your target
directory.
3. Add to your path the bin directory contained beneath the target
directory.
Adobe Acrobat Reader
--------------------
If this product has been supplied on CD the English Adobe Acrobat Reader
is included. It can be found in the directory Acrobat/Solaris with the
filename aix-rs-40_tar.gz. To install:
1. Run the command: gunzip sunsparc-rs-40_tar.gz
2. Run the command: tar -xvf SSOLRS.tar
3. Change to the directory SSOLRS.install
4. Follow the instructions in the file INSTGUID.TXT
It is recommended that the Acrobat Reader is installed into the default
location.
CICSTERM Behaviour and Signon Capable Terminals
===============================================
CICSTERM now attempts to install a signon capable terminal by default.
Use the option '-a' to request the default CICSTERM behaviour as in
releases prior to v3.1.0.
CICS Servers require APAR fixes to support the terminal signon capability
function available in this release:
CICS/ESA 4.1 PQ30167
CICS TS v1.2 and v 1.3 PQ30168
CICS/VSE TS v1.1 PQ30170
TX Series IY03691
CICS TS v1.3 Servers
--------------------
If the server does not have the required APAR applied and the '-a' option
is not specified on CICSTERM, the installed terminal will give unpredictable
results.
TX Series Servers
-----------------
If the server does not have the required APAR applied and the '-a' option
is not specified on CICSTERM, the Client will display the message:
'CCL7053E Errors found while communicating with server'
and the message:
CCL3105 Inbound CICS datastream error (CTIN, 4, 0)
will be written to CICSCLI.LOG.
On the server, the message:
'ERZ042004E/0112: An invalid request was received from client'
will be written to CSMT.out and console.msg will include:
'ERZ014016E/0036: Transaction CTIN Abend A42B'.
Security on OS/390 Servers
--------------------------
Security checking done in the server for transactions started at a signon
capable terminal installed by a Client application does not depend on what is
specified by the ATTACHSEC option for the connection representing the Client.
Instead security checking depends on whether the user signs on while using the
terminal.
If the user does not sign on, the Client installed terminal is associated with
the default user defined for the server in the SIT. When a transaction is run,
the security checks are carried out against this default user. A check is also
done against the userid associated with the connection to see whether
the Client itself has authority to access the resource.
When a user does sign on, the terminal is associated with the userid just
authenticated. For transactions attempting to access resources, security
checking is done against the userid associated with the connection and the
signed-on user's userid.
It is recommended that the Usedfltuser parameter on the server connection
definition is set to Yes if using signon capable terminals and to No if using
signon incapable terminals.
EPI Purge Terminal Restriction
==============================
The EPI purge terminal function will not cancel ATI requests queued
against the terminal. This is a temporary restriction in this release.
XTERM and function keys
=======================
When running in an XTERM window, cicsterm may not recognise all function
keys. This is because of the terminal type. If you are having problems
with cicsterm recognising functions, either run cicsterm in a different
window or set the TERM environment variable to a different terminal type
such as vt100 (by default, this environment variable is often set to
xtterm).
Running the CICS client over telnet
===================================
If you run the CICS client over telnet, you may find that certain telnet
clients cause problems with the display. For example, your telnet session
may truncate message lines which are over a certain length. This is usually
a problem with the telnet client that you are using, or the terminal type
that you are going in as.
Using X-Windows clients
=======================
You may find that some X-Windows clients (such as Exceed) corrupt the text on
the title bar of the window that you are trying to display. For example,
this might happen with the Configuration Tool. This is usually a problem
with the X-Windows client that you are using.
Also you may find the title bar is not displayed when using Exceed. To solve
this problem you have two choices:
1. Start a window manager before launching the Configuration Tool. A window
manager HWM, is shipped with Exceed.
2. Alter you settings in Exceeds Xconfig as follows:
- Launch Xconfig
- Select 'screen definition'
- Alter the 'Window Manger' to 'native'
- Make sure 'Use Native WM for Embedded Clients' is checked
Unfortunaley this has the effect of not allowing you to run any other window
manager.
Timeout processing on TCP/IP protocol
=====================================
Client timeout processing will only result in server cleanup processing
on a server linked via the TCP/IP protocol, if the server has support
for this function installed.
DBCS Support in the COM and C++ Libraries
=========================================
The COM and C++ libraries do not provide any specific support for 3270
datastreams that contain DBCS fields.
Update to Client/Server Programming Book
========================================
Additional return code on CICS_EpiTerminate:
CICS_EPI_ERR_TTI_ACTIVE
A transaction started from the EPI is still active or a
CICS_EpiGetEvent call is still outstanding.
Updates to C++ and COM Automation programming books
===================================================
Disconnect Documentation
------------------------
There is a mistake in the CclTerminal Reference section, specifically in the
definition of disconnect. It should read as follows :-
disconnect (1)
void disconnect()
Disconnects the terminal from CICS. No attempt is made to purge any
outstanding running transaction.
disconnect (2)
void disconnect(Ccl::Bool withPurge)
withPurge
Ccl::Yes - Disconnects the terminal from CICS and will attempt
to purge any outstanding running transaction
Ccl::No - Disconnects the terminal from CICS. No attempt is
made to purge any outstanding running transaction.
In the COM Automation programming book the definitions of disconnect and
disconnectwithpurge are the same, this is not correct it should be
Disconnect
Disconnects the terminal from CICS. No attempt is made to purge any
outstanding running transaction.
DisconnectWithPurge
Disconnects the terminal from CICS and will attempt to purge any
outstanding running transaction
exObject method in CclException Class
-------------------------------------
This method is relevent to both ECI AND EPI.
exObject now will return the relevent CclTerminal object pointer in the
exception block for EPI applications. It will need to be cast to a CclTerminal*.
For example:
CclTerminal* pTerm = (CclFlow*)ex.exObject();
SNA driver requirements
=======================
Automatic Transaction Initiation (ATI) is not available.
Patches required for the Solaris SNA support
--------------------------------------------
SNA is supported on the Solaris client through the Sunlink 9.1 product.
It is recommended that the latest set of patches are applied to the Sunlink
product before using it with the CICS Client.
At the time of testing, patches 105860, 106162, 106164, 106165 and 106723
were required as these provide a new reentrant version of the Lu6.2
library (liblu62_r.so) which is required.
Using C++ version 5
===================
Two versions of the C++ Client library are provided.
The library libcclcp.so is provided for Solaris C++ version 4.2.
Due to changes in the Solaris C++ version 5 linking, a new Client
library libcclcp5.so is provided for linking with version 5 applications.
Patches required for Solaris C++ 5
==================================
To overcome problems found in testing the version 5 C++ library,
the following patches must be installed:
Solaris 2.5.1
-------------
106529-07
107357-09
107289-05
107311-11
Solaris 2.6
-----------
105591-09
107357-09
107289-05
107311-11
Solaris 2.7
-----------
32 bit:
106327-08
106748-04
107289-05
107311-11
107355-06
107357-09
64 bit (in addition to 32 bit patches):
106300-09
107058-01
107390-11
These patches install a new version of the C++ runtime and fix various
problems with the version 5 compiler. Please refer to the Solaris patch
site for updates to the listed patches and instructions on the order
in which to apply them.
Compiling C++ applications that use the C++ libraries
=====================================================
If you are compiling C++ applications which use the CICS C++ libraries
then you need to define the CICS_SOL macro instead of using CC_UNIX.
CC_UNIX will still work in this release but may be removed in a future release.
Tracing enhancements
====================
There are two new command line switches on cicsftrc:
/s Do summary trace formatting
/d Do detailed trace formating
Summary trace formatting is driven from a text file (CCLSUMTR.TXT) which is
read in at initialization time. This defines the set of trace points we want
summary tracing for, and also what type of trace point it is. As DetailFormat
hits each trace point, if it is one of the ones read in from this file, a line
is generated in the summary file. This should be used as requested by Service.
Service and Updates
===================
Service and updates will be made available via the Internet.
See:
http://www.software.ibm.com/ts/cics/support/details
Service process for JREs on Solaris
-----------------------------------
The JRE packaged with the CICS Transaction Gateway and CICS Universal Client
for the Solaris platform is supported by Sun Microsystems, Inc.
Customers using this JRE can keep up to date with Sun upgrades by accessing
the Sun Web site below and installing fixes/JRE refreshes as they become
available from Sun.
http://www.sun.com/solaris/jre/index.html
APAR Fixes in v3.0.2
--------------------
PQ17866 ALLOCATE FAILURE HANGS EPI
PQ10841 TERMINAL CAN'T RECONNECT AFTER HOST IS CYCLED
PQ14864 MORE API INFORMATION IN TRACE
PQ16053 MISSING METHODS IN CCLEPI CLASS
PQ16369 MOVING DATA INTO LAST ATTRIBUTE CORRUPTS MAP
PQ16521 PROBLEMS WHEN USING ECI AND EPI TOGETHER
PQ16971 EPI HANG WHEN TRACING ACTIVE
PQ18131 ATI REQUESTS NOT INITIATED WITH C++ CLASSES
PQ19262 PASSWORD VISIBLE IN TRACE
PQ18267 ENABLEPOPUPS = N HAS NO EFFECT
PQ19523 EPIADDTERMINAL CAN SOMETIMES CAUSE EPI TO HANG
PQ19525 EPI CALLBACK ROUTINE MAY BE INCORRECTLY DRIVEN
PQ18445 LOOP IN EPIGETEVENT
PQ20250 C++ EPI CLASSES DO NOT BUILD FIELDS CORRECTLY
APAR Fixes in v3.0.3
--------------------
PQ22297 CICSPRNT cpu usage in background
PQ22301 CICSPRNT 1 print job per txn
PQ21189 Failure to reconnect over SNA session
PQ22831 SIGPIPE handle error
PQ22830 Variable retry interval parameter
PQ22426 Redesign to use pthread semaphores
PQ25017 Improvement of client security
PQ24339 Memory leak when server down
PQ21176 problem with lots of terminal deinstalls
PQ22983 CICSPRNT deals with file system errors incorrectly
PQ20693 PCOMM supplied with client upgraded to fixpack 2 level
PQ20313 ECI request to unavailable server may trap
PQ21147 Errors during shutdown of Win95 Client
PQ23435 Client hang with C++ forcereset between 2 asynchronous calls
PQ21700 Trap when multithreaded EPI program stresses client
PQ21621 C++ & OLE programs don't notice server has been restarted
APAR Fixes in v3.1.0
--------------------
PQ27201 The Comma (,) is not allowed as a decimal point
PQ25265 A CICS Universal Client on Solaris appears to hang
PQ28458 CICS Client - cannot use SBAS, RAS and EUA orders on screens
PQ30588 Large screen support for CICSPRNT
PQ27872 CCLLOG.TXT for CCL4413 needs to be changed from 'PORT=%U3' to 'PORT=%HD3'
APAR Fixes in v3.1.1
--------------------
PQ29864 Datastream3270.class incorrectly inserts zero byte at start of BMS fields
PQ31293 CCL8036 when using cicscli.ini on network drive due to 60 sec timeout
PQ32974 Config tool does not pick up mode names starting with hash
PQ33148 Starting cicscli -s=servername when LANG=En_US ...
PQ33162 Default trace file name incorrect after file migrated
PQ33343 Cicsprnt does not work with /j or /p option ...
PQ33833 Cicsbmsc conversion utility put negative in 1st field of constant
PQ34080 If null passed to SETTEXT method in COM class field...
PQ35012 When ECI requests get around 250Kb of data, the application hangs
PQ35123 During ATI processing, message 'CCL3227 Conversation (1) is not in send state' is intermittently received.
PQ35237 Client blew up immediately at address 0x00AF209A which was trying to reference memory location x00000000
PQ35981 Sunlink problem
APAR Fixes in v3.1.2
--------------------
PQ36608 Java applications using the local protocol under the Solaris JVM
may crash if JIT enabled
PQ37526 Trap occurs if servername called against a null CclConn object
PQ37752 Alarm subroutine unpredictable when used with CICS Client API calls
PQ37790 Reduce CPU usage of CICS Client daemon
PQ38008 Increase stack size in advanced samples
PQ38268 A signed on signon-capable terminal loses its security when an
ATI task is started against it
PQ39229 Client closes connection if TXSeries transaction times out
PQ39866 CICSSetDefaultSecurity always fails
PQ39890 The rsh command hangs trying to execute 'cicscli -s' on remote machine
PQ39894 Cicsterm's IPC queue is not cleaned up on termination
************************************************************************
IBM, AIX, CICS and OS/2 are trademarks of the IBM Corporation in
the United States or other countries.
Sun, Java and JavaBeans are a trademark of Sun Microsystems, Inc. in
the United States or other countries.
Microsoft, Windows, Windows 95, Windows 98 and Windows NT are trademarks
of Microsoft Corporation in the United States or other countries.
Adobe and Acrobat are trademarks of Adobe Systems, Inc. in the United
States or other countries.
Other company, product, and service names may be trademarks or service
marks of others.
************************************************************************
* (C) Copyright IBM Corporation 1999. All rights reserved. *
************************************************************************
************************************************************************
* End of file *
************************************************************************
|
