IBM
Shop Support Downloads
Home Products Consulting Industries News About IBM Search
IBM > Software > Transaction Systems > CICS > Library > Manuals >
 

 

Administration


[Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index] [Help]


Migrating from CICS for OS/2 Distributed Feature clients

 

This topic discusses

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 clients

 

Existing 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):  

FAARQ.INI

CICSCLI.INI

NetBiosBufSize

MaxBufferSize

ServerName

NetName

Sysid

No equivalent

LocalNetName

Client

AdapterNumber

Adapter

LogicalSessionLimit

MaxRequests

TRModelName

ModelTerm

TRInitialTransid

InitialTransid

TRExitTerm

TerminalExit

TRClientTerm

No equivalent

TRTraceControl

No equivalent

TraceFileName

TraceFile


Application compatibility

 

Applications 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 compatibility

   

DOS, 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:

  1. The header files are now called cics_eci.h (C), cicseci.cbl (COBOL), cics_eci.inc (PL/I); and cics_epi.h (C), cicsepi.cbl (COBOL), cics_epi.inc (PL/I). References to faaecih.h and faaepih.h, or faaeciw.cbl and faaepiw.cbl must be changed.

  2. The CICS ECI entry point is now called CICS_ExternalCall() for C and PL/I, and _CICS_ExternalCall (16-bit) or CICSEXTERNALCALL (32-bit) for COBOL.

  3. The CICS EPI entry point is now called CICSEXTERNALCALL for 32-bit COBOL. Any calls to FaaExternalCall() must be changed.

  4. The correct link libraries are now called CCLDOS.LIB (for DOS), CCLWIN.LIB (for Windows Family) and CCLOS2.LIB or CCLOS232.LIB (for 16-bit and 32-bit OS/2 respectively). Attempts to link with FAACLIB.LIB or FAACIC32.LIB will fail.

  5. Full 32-bit applications are supported for both ECI and EPI by linking with the CCLOS232.LIB. However, some of the client itself is still built as a 16-bit application so you must take care not to pass it data structures that span a 64KB boundary. The IBM C Set++ compiler provides options and facilities to prevent this.

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.


[Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index] [Help]


[ IBM home page | (C) | (TM) ]
© IBM Corporation 1994, 1997. All Rights Reserved
 
Privacy Legal Contact