Addressing OLTP Solutions with CICS: The Transaction Server ... - Ibm

4.5.2 CICS Client for DOS
62 CICS for AIX as the Transaction Server
4.5.1.3 Autoinstall User Exits
The CCIN calls user exit DFHCCINX when it is about to autoinstall the CD entry
for the CICS Client for OS/2 system. If your own version of this user exit is in
effect, review its logic to ensure that the CD attributes to be altered are
compatible with those of the model CD entry.
When the first EPI or cicsterm request arrives at the CICS for AIX server the
CCIN has run, the CTIN transaction carries out the autoinstall of a workstation
definition (WD) resulting in a four-character terminal identifier of the format
=xxx, where xxx is a character string chosen by CICS; the first character of = is
fixed. If your autoinstall user exit programs do not expect the = character, you
may have to review their logic to prevent potential problems.
4.5.1.4 Security
The userid and password are the main security mechanisms with the CICS Client
for OS/2 system. The CICS Client for OS/2 holds only a single userid and
password for each CICS for AIX server that it connects. You specify the userid
and password for the particular CICS for AIX server either in the client
initialization file (default name CICSCLI.INI) or by using the cicscli command.
Also you must ensure that a user definition (UD) entry with matching userid
exists in the connecting CICS for AIX region. Otherwise the default userid of the
CICS region is used. In the case of cicsterm, you can enforce the initial
transaction to be invoked to be CESN, the CICS-supplied sign-on transaction.
This would cause the user to authenticate again.
4.5.1.5 3270 Keyboard Mapping
The keyboard mapping for 3270 emulator operation is defined in a keyboard
mapping file. CICS Client for OS/2 supplies a default file, CICSKEY.INI, in the
\CICSCLI\BIN directory. We recommend that you create your own customized
mapping file. To identify this keyboard mapping file, you either specify the /k
option on the cicsterm command or specify the CICSKEY environment variable in
the CONFIG.SYS file.
CICS Client for DOS requires an IBM-compatible PC that supports the DOS
operating system and has sufficient memory for the required software
components.
The disk space required for the client code of CICS Client for DOS is about 0.9
MB. Additional disk space is required if you select the samples and
documentation installation options.
To benefit from NLS support when communicating with a CICS for AIX server,
CICS Client for Windows can run under any of the following operating systems:
• Microsoft or IBM PC DOS 3.3, DOS 4.0, DOS 5.0, or later
• Windows J (Japanese) Version 4.0 or later, Version 5.0/V or later
• Windows H (Korean) Version 4.0 or later, Version 5.0/V or later
A CICS Client for DOS can also run in the DOS box of OS/2.
CICS Client for DOS requires a product providing TCP/IP or APPC support. For
example, IBM TCP/IP for DOS Version 2.1.1 or later provides the TCP/IP support.
The particular product providing APPC support depends on the actual network