************************************************************************
* IBM CICS Transaction Gateway for OS/2 - README                v3.1.2 *
************************************************************************

Welcome to the IBM CICS Transaction Gateway ...

This file contains important information about the IBM CICS Transaction
Gateway that may not be available in the printed documentation.

In the following information  refers to the directory in which
you installed the Transaction Gateway.

Summary of Topics
=================
- IBM NetStation support
- DBCS and the Java APIs and Terminal Servlet
- Treminal Servlet whitespace and neutral color
- Request classes and string truncation
- JNI Tracing
- CICS Connectors
  - Extended Attribute Support for EPI Connector
  - Use of the CICSELUW flag in the ECI Connector
- Configuration Tool update
- Trace filesize parameter
- Service and Updates
- Client README information


IBM NetStation Support
======================
Applets running within the JVM supplied with the NC browser fail to
make successful connections with the CICS Transaction Gateway. Message
number CCL6652E is returned to the Applet. Currently there is no solution
to this problem.


DBCS and the Java APIs and Terminal Servlet
===========================================
The higher level EPI Classes, EPI Beans and the Terminal Servlet do not
contain any specific support for 3270 datastreams that contain DBCS fields.


Terminal Servlet whitespace and neutral color
=============================================
The screen handler has been amended so that if the user specifies
the screen@TrimFields=true parameter in the servlet properties
file, we 'trim' the field to remove excess whitespace from the
begining and end of any input fields.

The screen handler has been amended so that the user can specify what
HTML colour to translate the 'neutral' 3270 colour to. This is
achieved using a new parameter (screen@NeutralColor=usercolour)
which can be added to the servlet properties file.


Request Classes and string truncation
=====================================
the ECI and EPI Request classes take strings for various parameters, eg
Server, Userid, Password and so forth. If you specify a string that is
too long, when the request is flowed, the string will be truncated to the
maximum length.


JNI Tracing
===========
JNI tracing is NOT enabled through the normal Gateway tracing options. To
enable it all you do is set an environment variable CTG_JNI_TRACE to the path
and file where you want the information stored. For example
set CTG_JNI_TRACE=c:\temp\ctgjni.trc


CICS Connectors
===============

Extended Attribute Support for EPI Connector
--------------------------------------------
You are now able to get the extended attributes using the EPI Connector
The following information explains the changes made to the EPI Connector
classes to support this facility.

The EPIInteractionSpec has 2 new properties.

Mode
====

available values
----------------
MODE_SEND_AND_RECEIVE (0)
MODE_SEND             (1)
MODE_RECEIVE          (2)

description
-----------
This works as defined for CCF. The receive will receive back the last screen
contents.



OutputAttributeType
===================

available values
----------------
ATTRIBUTE_NONE            (0)
ATTRIBUTE_BASE            (1)
ATTRIBUTE_FOREGROUNDCOLOR (2)
ATTRIBUTE_BACKGROUNDCOLOR (3)
ATTRIBUTE_HIGHLIGHT       (4)
ATTRIBUTE_TRANSPARENCY    (5)

description
-----------
Allows you to select which attribute will populate the attribute byte in the output
record of the Connector execute call. The default is ATTRIBUTE_BASE


Use of the CICSELUW flag in the ECI Connector
---------------------------------------------
If you are using the ECI connector with a real Co-ordinator, you MUST set the
CICSELUW flag on the ECIInteractionSpec to TRUE. The default is FALSE. If you
don't then the ECI Resource will NOT be registered with the co-ordinator and
you will not extend logical units of work as expected.


v3.04 Client Restriction
========================
Connecting a v3.04 client java application to a v3.1x, or later, gateway over
SSL or HTTPS is not supported.


Configuration Tool update
=========================
To clarify the 'Require Security' option on the HTTP, HTTPS, TCP and SSL panels,
it has been renamed to 'Require clients to use security classes'.


Trace filesize parameter
========================
To specify the maximum size of the trace textfile, use the -tfilesize
option on ctgstart. The parameter is the size in kilobytes.


Service and Updates
===================
Service and updates will be made available via the Internet.
See:
   http://www.software.ibm.com/ts/cics/support/details

APAR Fixes in v3.1.0
--------------------
PQ25945 Java Gateway won't restart without stopping the client
PQ28840 Terminal Servlet does not support colour
PQ28843 CTG Terminal Servlet HTML field size
PQ28312 Cursor location specified by BMS page ignored by Terminal Servlet
PQ30148 Terminal Servlet doesn't access multiple servers as it should

APAR Fixes in v3.1.1
--------------------
PQ31837 Jgate -time does not produce timestamps in jgate log
PQ33058 Commarea not returned in ASCII by CTG
PQ33193 CTG using Local: protocol loses data
PQ34612 Input field full of blanks (terminal servlet)

APAR Fixes in v3.1.2
--------------------
PQ38877 Better identification of threads, ports and sockets in CTG trace
PQ39299 A new Terminal object may fail to run more than one transaction
PQ39377 CTG trace shows misleading messages for terminal indexes
PQ39725 Ability to produce wrapping trace for CTGSTART tracing
PQ40466 A Java NullPointer exception is driven by the setText method
        of the Field object

Also refer to the Universal Client fixes.