Transoft Component Adapters (Deployment) 3.10
Release Notice

Contents

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

Welcome to revision 3.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.

• 64 bit versions of TCA are available extending your investment in our technology. Platforms available on request are Solaris (SPARC and Intel), AIX and HP-UX (PA-RISC and Itanium).
• The TCF Screen Adapter now supports high-ASCII characters in VT100 emulation - this enables use of a range of character sets used in different European languages.
• TCF Screen Adapter has been enhanced to handle any number of different key codes, This is achieved using a customisable, XML format, mapping file to define the terminal emulation. One benefit is that Screen Adapter is able to handle a large number of different function keys.
• The Composite Services Adapter has been enhanced to allow for multiple concurrent TCA connections.
• The SQL component has been enhanced to allow use of the Datadirect ODBC driver as well the iODBC driver.
• Support for RemoteHost and RemotePort settings. This gives a method of overriding the host/port for Remote Components as specified in the SDL and is useful where the same SDL file is to be deployed on different servers.
• Logging has been enhanced. This can be very helpful in fine tuning and debugging components.
• A FetchTimeOut setting added. This provides a means of handling an errant client that locks a component and fails to fetch the results, thus improving resilience.

• TCF Screen Adapter - Fix problem with HP3000 terminal flow control.
• TCF Screen Adapter - Fix problem when using control keys in enter statements.
• Fixed problems with license slots being left in use.
• Stricter enforcement of the CPU license check.
• Fix problems with interactive component debuggers on XP/2003.
• Fix limitation with XML results of over 10Mb.
• Composite Services - Problem where output parameters were returned as NULL.
• Composite Services - Fix empty resultset bug
• Composite Services - Fix TCA Connection problems

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.

When using COBOL under Windows, the COBOL runtime should dynamically link with the Application Bus Adapter, CFACOB.DLL, although some additional configuration may be required:

• For ACU COBOL, make sure the CODE_PREFIX environment variable contains C:\WINNT\System32 or wherever your Windows system files reside. Also, make sure that the dll-convention setting is 0 (this is the default)
• For RM COBOL 7, you cannot use the standard CFACOB.DLL, as RM requires it's extensions to be in a different format. Instead, use the RMCOB7.DLL DLL by adding the option L=RMCOB7.DLL to the command line.

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.