Transoft Component Adapters (Deployment) 2.10
Release Notice

Contents

• Introduction
• New Features
• Bugs Fixed
• Language Integration
• Additional Notes

Welcome to revision 2.10 of Transoft Component Adapters (Deployment).

The Transoft Component Adapters (Deployment) — Installation & Licensing Guide can be found in the base directory of this CD-ROM, along with Microsoft's Word Viewer 97. Install Word Viewer 97.

• New online help.
• Updated Transoft Component Adapters Deployment Installation and Licensing guide.
• Java remote components.
• Dynamically linkable/loadable ODBC Driver Manager for UNIX using shared object libraries. This has been tested with iODBC and MERANT DataDirect Connect ODBC. See the section entitled Configuring SQL Data Sources on UNIX in Chapter 5 — Configuring TCA in the
Transoft Component Adapters Deployment Installation and Licensing guide for details.
• Support for Liant RM/COBOL 7.1, in which a COBOL ABA (application bus adapter) shared object library is used. This shared object library also works with Micro Focus Server Express.
• UNIX shell scripts are now also supplied with the release to re-link the RTEs (run-time environments) for ACUCOBOL, Liant RM/COBOL and Micro Focus COBOL. If RM/COBOL 7.1 is detected, rather than re-link the RTE, the COBOL ABA shared object library is copied to the correct location.
• Transoft Screen
Component Adapters VT-100 terminal emulator extended to support a number of its successors. If you require support for post-VT-100 emulation, please contact Transoft Customer Services for an up-to-date list of those VT-100-based terminal emulators supported.
• Fixes and enhancements to Transoft Screen Component Adapters, particularly with respect to IBM 5250 emulation. e.g. shutdown, timeout, delay and keep-alive.
• IBM 3270 emulation support for Transoft Screen Component Adapters. (Available on request.)
• Component clean-up period.
• Screen Adapter Monitor (samonitor): a DOS console/UNIX application to monitor screen adapter activity.

• UK23952. Fixed intermittent problem in which the Screen Component fails to start causing a general protection fault on Windows platforms, and a core dump on UNIX platforms.
• UK23953. Fixed corruption of language initialisation file settings.
• UK23955. Transoft Component Adapters Deployment Installation & Licensing Guide updated with details of the IBM OS/400 release.
• UK23965. Fixed parsing of SQL services in SDL files, in which a line of SQL of three characters or less causes a parsing error.
• Fixed infinite loop when parsing HTTP parameters where the name of the parameter being looked for formed part of another parameter being passed in.
• Increase buffer size with >30K parameters.
• UK18561. Don't get the client port settings if there's no server setting.
• UK23196. Fix error message for unknown component.
• UK23521. Generate a parse error when we get a decimal instead of an integer.
• UK23714. Fixed server-side components looping if set-up functionality incorrect, and minimum number of instances set.
• UK23773. Reset the "numrowsvar" back to NULL on a new service.
• UK24060. HTTP keep-alive connections were leaving IREFs in the shared memory. Clear them out on a disconnection.
• UK23966. We used to report the next SQL service on an error. This gets the error line text right too.
• Made EBCDIC processing for RM/COBOL soft—now initialised with the CFINIT call.
• UK24094. Fix for numeric fields when PC is in Spanish mode.

When using COBOL under UNIX, the runtime system will need to be rebuilt or enhanced by linking in the COBOL Application Bus Adaptor library (cobcf.a), or by placing a shared object library version in the appropriate directory.

There is a UNIX shell script within the cobol subdirectory for each COBOL language type supported:

• aculinktca.sh for ACUCOBOL
• mflinktca.sh for Micro Focus COBOL
• rmlinktca.sh for Liant RM/COBOL

Run the relevant script, and follow any instructions provided.

Users of the SCO UnixWare client-side library should note that the client timeout feature is not supported under UnixWare and possibly other platforms that use the same binary.