|
|
|
|
Administration
Migrating from CICS for OS/2 Distributed Feature clients
This topic describes how to migrate from using the Distributed Feature clients of CICS for OS/2 to using IBM CICS Clients. Distributed Feature clients were first shipped with CICS for OS/2 Version 2.0 and are supported for CICS for OS/2 Version 2.0.1. (Although the use of IBM CICS Clients is recommended.) Upgrading Distributed Feature clientsExisting CICS for OS/2 initialization files used by CICS for OS/2 Distributed Feature clients are supported by the IBM CICS clients. Keywords Sysid, TRClientTerm and TRTraceControl are ignored, because these functions are not supported by IBM CICS Clients. Any attempt to mix the old and new format files results in an error. The following shows the mapping between the parameter names in the Distributed Feature client initialization file (FAARQ.INI) and the IBM CICS Clients file (default CICSCLI.INI):
Application compatibilityApplications that run on the CICS for OS/2 Distributed Feature clients should run successfully on CICS clients. Note: For CICS Client for Macintosh, only applications written in the C language are supported. The PL/I language is supported for CICS Client for OS/2 only.
ECI and EPI compatibilityDOS, Windows, and OS/2 ECI and EPI applications written for Distributed Feature clients of CICS for OS/2 are portable at the binary level to the corresponding members of the IBM CICS Clients family (although it is not possible to port 16-bit applications to 32-bit applications). If such applications are to be changed, or if they need to be ported to other client platforms, the ECI call requires very minor changes before recompiling. Notes:
ECI and EPI client applications are portable between members of the CICS clients family, provided the application does not contain operating-system-specific calls. For more information, refer to the CICS Family: Client/Server Programming book.
[ IBM home page | (C) | (TM) ] © IBM Corporation 1994, 1997. All Rights Reserved |
|
|