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]


Customization

This topic describes

This topic describes how to prepare the client initialization file, and also how you can customize the client keyboard mapping, screen colors, and attributes.


Renaming the client initialization and mapping files

The following files are supplied with CICS clients in the \CICSCLI\BIN directory by default:

CICSCLI.INI

The client initialization file

CICSKEY.INI

The keyboard mapping file

CICSCOL.INI

The color mapping file

It is recommended that you create your own customized versions of these files with different names, because installation of service updates may overwrite the files and cause any customization to be lost.

You should reference your customized files through the following environment variables:

File

Environment variable

client initialization file

CICSCLI

keyboard mapping file

CICSKEY

color mapping file

CICSCOL

You can set these environment variables in the AUTOEXEC.BAT (DOS and Windows), CONFIG.SYS (OS/2) file, or via the System icon in the Windows NT control panel, for example:


        SET CICSCLI = C:\CUSTOM\MYCLI.INI

Note: For CICS Client for Macintosh, the preferences file is used instead of environment variables. You are strongly recommended to keep a backup copy of this preferences file.


Preparing the client initialization file

     

The initialization file contains configuration information used to inform the client of the servers it can connect to and the necessary communication protocols. A sample initialization file is supplied for each IBM CICS Client product.

The default filename for the initialization file is   CICSCLI.INI (in the \CICSCLI\BIN directory by default), but this can be overridden for all CICS clients (apart from CICS Client for Macintosh) by the environment variable CICSCLI, which specifies the name of the initialization file to use.   You can also specify which file to use with the /f parameter of the CICSCLI command (see "Specifying which client initialization file to use").

Note: For CICS Client for Macintosh, a preferences file is provided within which the initialization file is identified. You can change the preferences file using the CICS Client for Macintosh Administration Utility. The CICSCLI.INI file supplied for CICS Client for Macintosh does not contain parameters concerned with NetBIOS communication.

Client initialization file syntax

You create or edit the initialization file with a text editor according to the following syntax rules:

  1. Parameters are entered on individual lines, and cannot be continued over more than one line:
    
        parameter=value
    
    

  2. Any line where the first nonblank character is either a semicolon (;) or a hash (#) is treated as a comment.

  3. Blank characters before the parameter keyword, and either side of the = (equals) character, are ignored.

  4. The parameter value is taken as the first nonblank character following the = (equals) character up to the last nonblank character on the line. However, if the equals is followed by # or ; preceded by one or more blanks, the parameter value continues up to the last nonblank character before the string of blanks. (Unless the # or ; is the first character of the parameter value.)

    To illustrate:

    
    # this is a comment line
    
    Server = CICSESA      # here is a comment
    
      Netname = #cicse    # the first hash is part of the value
    
    

  5. Parameter values must not contain embedded blanks.

  6. The parameter keyword is not case-sensitive; however, the values themselves may be. (The parameter descriptions in "Client initialization file parameters" indicate which values are case-sensitive.)

Client initialization file structure

The initialization file is structured into sections, each containing a set of parameters specific to that section:

  1. At most one Client section.

  2. One or more Server sections. The first server definition is used as the default server for the client.

  3. One or more Driver sections. You must create one Driver section for each unique protocol referenced in the Server sections.

The Client section should precede the Server sections, and the Server sections should precede the Driver sections.

Note: Use of a section-specific parameter within another section generates an error. Parameters that are operating-system specific, for example, DosMemory which is applicable only to CICS Client for DOS, are ignored on other platforms.

You can change the client initialization file at any time, but you must stop and then restart the client before the changes take effect. See "Operation" for details of how to stop and start the client.

The full syntax for the initialization file is shown in Figure 23. Items bracketed with [ and ] are optional. Values separated by | indicate that one item from the list should be selected.

Figure 23. Client initialization file syntax


      [Client=* | applid

        [MaxBufferSize=nn]

        [TerminalExit=name]

        [TraceFile=filename]

        [LogFile=filename]

        [MaxServers=nnn]

        [MaxRequests=nnnnn]

        [DosMemory=nnn]

        [PrintCommand=command]

        [PrintFile=filename]

        [DumpMemSize=nn]

        [DumpFile=filename]

      ]



      Server=Servername

        NetName=Applid | LUName | HostName | IPAddress

        Protocol=ProtocolName

        [Description=desc]

        [UpperCaseSecurity=Y|N]

        [InitialTransid=transid]

        [ModelTerm=name]

        [Port=nnnn]

        [Adaptor=0|1|2|3]

        [LocalLUName=LUName]

        [Modename=modename]

        [AppleGateWay=name]

        [AppleZone=zone]

        [SnaLocalLUAddr=nnn]

        [SnaSessionLimit=nnn]

        [SnaDLCName=name]

        [SnaPLUAdapterAddr=address]

        [SnaMaxRUSize=nnnn]

        [SnaPacingSize=nn]

        [SnaRetryCount=nnn]



      Driver=ProtocolName

        Drivername=drivername


Client initialization file parameters

You will find it useful to refer to the following list when working through the definition checklists in "Setting up client/server communication".      

Client

This parameter introduces the section of the initialization file defining aspects of the client itself. If this parameter (and hence section) is omitted, default values are used.   

applid

Up to 8 characters. The default is *.

This value specifies the applid of the CICS client workstation in the form in which it will be autoinstalled as a system at the CICS server. The name must be unique within the CICS server system. The value of * can be used to automatically generate a name that is guaranteed to be unique.

Note: If the client is autoinstalled to more than one CICS server, and if applid specifies a specific name, that name must be unique with respect to all servers it is connected to. If the name is not unique, then attempts to connect to a server may be rejected because another client has already been installed using the same name. If a name of * is used, the client may be known by a different unique name at each server.

If the client is to communicate with a given server via APPC, then this applid may be overridden at the time the client is installed at the server by the LUName for the client as defined in the Server definition.    

MaxBufferSize

A number of kilobytes, in the range 4 through 32. The default is 32 KB.

This value specifies the size of the transmission buffers in which application or terminal data will flow. The value should be large enough to cater for the largest possible COMMAREA or terminal input/output area (TIOA) to be used. The value does not include an overhead of 512 bytes needed by the clients for some protocols.

This parameter need normally be set only for clients running in a memory-constrained environment.    

Note: For CICS Client for Windows running on an Intel 80286 microprocessor, or on a later microprocessor in standard mode, and communicating over NetBIOS, MaxBufferSize must normally be set to 4, otherwise the client will not start. However, if it is necessary to send and receive large COMMAREA data blocks, a larger value for MaxBufferSize must be set.     To allow this, set the NetHeapSize parameter in the [Standard] or [386Enh] stanza in the Windows SYSTEM.INI file as appropriate for your system. For example:


    [Standard]

    NetHeapSize=48

A NetHeapSize value of 48 should allow a maximum MaxBufferSize of 32 for a Windows client in standard mode. For enhanced mode, Windows usually suggests an appropriate value to use the first time the CICS client is run.

TerminalExit    

A 1- to 4-character string; the default is EXIT.

The string, when entered at a terminal emulator at any time and place where a transaction name can be entered, causes the terminal emulator to terminate. The string must not contain any blank characters.

The string is case-sensitive. If a terminal emulator has uppercase translation in its CICS terminal definition, this string should be specified in uppercase.

TraceFile    

The name of the trace file to be used for problem diagnosis. If not specified, it defaults to CICSCLI.TRC in the client \BIN directory.    

LogFile  

The name of the log file to be used for problem diagnosis. If not specified, it defaults to CICSCLI.LOG in the client \BIN directory.      

MaxServers

A value in the range 1 through 256. The default is 1.

This value specifies the maximum number of servers that can be accessed concurrently from the client.

For more information on the use of MaxServers, see "NetBIOS resources".    

MaxRequests

A value in the range 1 through 10 000. The default is 20. This value specifies the maximum number of concurrent items that may be executing on the client, when an item is defined as a terminal emulator, an EPI terminal or an ECI unit of work.

This value is used to detect runaway situations where an application could, in error, submit an excessive number of requests to a server. The actual limit may be less than this parameter if other operating system limits (for example, memory constraint or communication sessions), come into effect.        

DosMemory

Required for CICS Client for DOS only. A value in kilobytes in the range 8 through 500. The default is 48 KB.

Defines the amount of memory to be reserved for the CICS Client for DOS terminate and stay resident (TSR) program.

The value must be greater than (MaxBufferSize + 4). A value of 48 permits a MaxRequests limit of at least 16. Specifying a larger value increases the maximum number of concurrent activities.

If the trace to memory function is to be used, the DosMemory value should be increased by (32 + DumpMemSize value).    

PrintCommand

A character string, from 1- to 256-characters long.

The specified string is a command specific to the operating system under which the client is running. When a request to print is received at the client, the client generates a temporary print file with a unique name per print request.

The parameter string is appended with the temporary file name, and the resultant command executed. This allows, for example, print requests to be copied to a file, directed to a local printer, formatted for inclusion into documentation, and so on.

A command file may be necessary to act as an interface between the syntax of the invocation command defined here, and more general operating system syntax. For example, if the desired final command was COPY printfile LPT2, a simple command file would be required to reorder the parameters. It is the responsibility of the PrintCommand to delete the temporary print file after it has finished processing it.

See also the PrintFile description for more information.

Note: This parameter is ignored for CICS Client for Macintosh.    

PrintFile

A character string, 1 to 256 characters long.

This option is applicable only if the PrintCommand option is omitted.

The specified string identifies a file to which output from print requests received at the client is directed. Each print request is appended to the end of the current file.

If both this value and PrintCommand are omitted, the default action for CICS Client for DOS, CICS Client for OS/2, and CICS Client for Windows Family is to direct the print data to LPT1.

Note: For CICS Client for Macintosh the default is to direct the output to the default printer.

Note: This initialization file setting acts only as a default. The terminal and print emulators provide options to override this value (see "CICSTERM command reference" and "CICSPRNT command reference").    

DumpMemSize

A number of kilobytes, in the range 1 through 32. The default is 16 KB. For CICS Client for DOS, a small value is recommended.

This value specifies the size of the internal buffer to which trace records are written by the CICS clients trace to memory function. This internal buffer is dumped to a file using the CICSCLI /z command, and also if CICS Client for OS/2 terminates abnormally. The buffer wraps, so it is the most recent trace records that are available.

For more information on the trace to memory function, see "CICS clients trace".

DumpFile    

The name of the file to be used for the CICS clients trace to memory function. If not specified, it defaults to CICSCLI.DMP in the client \BIN directory.  

   

Server

A separate definition must be included for each server to which the client needs to connect.   

Servername

A 1- to 8-byte character string providing a communications-protocol-independent name for the server local to the client. Requests to access the server from ECI, EPI, or terminal emulators reference the server through this name.    

NetName

A character string, the length and format of which depend on the communications protocol to the server. The string provides the client with the identification of the server as it is known to the communications protocol.

The string is case-sensitive.

For NetBIOS, Applid specifies the NetBIOS name of the server, and for CICS for OS/2 and CICS for Windows NT (Version 2 only), this is specified in the Local System Appl ID field in the system initialization table (SIT).

For APPC, LUName specifies the LUName of the server as it is known to the APPC configuration at the client. This must be a qualified 17-character name, for example, ABC3XYZ4.PQRS1234. For Client Access/400, if you want to use the default remote system specified by the RTDN identifier in the Client Access/400 configuration file, then specify * for NetName. For SNA*ps, NetName must reference the APPC Remote LU Name in the SNA*ps configuration file.

For TCP/IP, HostName or IPAddress specify the character or numeric TCP/IP identifier for the host on which the server is running. For example, cicssrv2.company.com (HostName) or 9.20.4.1 (IPAddress). Hostnames are mapped to IP addresses either by the name server or in a HOSTS file. It is, however, better to use a Hostname in case the IP address changes.    

Protocol

A 1- to 8-character string identifying the communication protocol to be used to communicate between the client and the server. This parameter is mandatory, and must match the ProtocolName parameter in the Driver section.

There are no predefined values for the protocol name. You must provide a Driver parameter group for each communication protocol referenced, mapping the protocol name to the interface code provided with the client.    

Description

An optional 1- to 60-character string offering a description for the server. This description is returned to applications running on the client via the CICS_EpiListSystems and CICS_EciListSystems functions (see the CICS Family: Client/Server Programming book).

UpperCaseSecurity      

Y or N. If set to Y, any userid or password from an ECI application or resulting from a user prompt is converted to uppercase. See "Setting up security" for more information.    

InitialTransid

A 1- to 128-character string.

This string identifies the initial transaction (and any parameters) to be run when the terminal emulator connects to the server. If this option is omitted, no initial transaction is run. The first four characters, or the characters up to the first blank in the string are taken as the transaction. The remaining data is passed to the transaction on its invocation.

The string is case-sensitive.    

ModelTerm

A 1- to 16-character string. The default is *.

The string is case-sensitive and specifies the name of a model terminal definition at the server, identifying the characteristics of terminals to be autoinstalled from the client. If the model cannot be located at the server, or this parameter is not specified, a default terminal definition is used. This default is server-specific.

The interpretation of the ModelTerm value is server-specific. For example, for a CICS for OS/2 server, the value is validated (by the server) as a 1- to 4-character string identifying a model entry in the CICS terminal definition control tables with a terminal name set to the value specified on this parameter. For a CICS for AIX server, the value is 1 to 16 characters, and is the DevType for a CICS terminal definition entry to be used as the model.    

Port

Required for TCP/IP communication only. A numeric value in the range 0 through 65 535 defining the port number at the server to which the client should connect. If this parameter is omitted, a default value of 0 is assumed. A value of 0 indicates that the SERVICES file in the TCP/IP \ETC directory should be used to locate the port number for the service CICS using a protocol of TCP.

If no entry can be located in the SERVICES file, a value of 1435 is assumed, this being the TCP/IP architecture assigned port for CICS clients.

Note: For CICS Client for Macintosh, no reference is made to a SERVICES file. If a value of 0 is entered, 1435 is assumed.    

Adapter

Required for NetBIOS communication only. A numeric value in the range 0 through 3 specifying which LAN adapter the client should use. The default is 0.    

LocalLUName

Required for APPC communication only. The name of a local LU to be used when connecting to the server. The same LU can be used for all server connections.

Note: For CICS Client for Macintosh you can obtain this from your SNA*ps gateway administrator. While it is possible for several CICS Client for Macintosh systems to use the same LocalLUName at the same time (all concentrated through a common SNA*ps Gateway machine) this is not recommended, as incoming Allocates may be routed to the wrong client. Unless all you are using under the client is ECI applications, you should define multiple Local LUs in your SNA*ps configuration file and use a different one in each CICS Client for Macintosh connected through the Gateway.    

ModeName

Required for APPC communication only. A 1- to 8-character string specifying the mode name to be used when connecting to the server. For Client Access/400 APPC communications, this value can be omitted, because the fixed mode name of QPCSUPP required by Client Access/400 is used. For other APPC communication, omitting this parameter results in a blank mode name.

A value of * can be specified if a blank mode name is required.        

AppleGateWay

Required for CICS Client for Macintosh communicating via SNA*ps. A 1- to 32-character string specifying the name of the SNA*ps gateway. For CICS Client for Macintosh you can obtain this from your SNA*ps gateway administrator.

AppleZone

Required for CICS Client for Macintosh communicating via SNA*ps. A 1- to 32-character string identifying the zone for the SNA*ps gateway. A value of * indicates that the local zone is to be used. If this parameter is omitted, a default of * is used.

The following seven parameters are required for APPC communication using NetWare for SAA.   

SnaLocalLUAddr

A 2-character string specifying the logical session number for the local LU. The value is specified as a pair of hexadecimal characters, for example, X'01' or X'FE'. If omitted, a default of X'00' is used. See the appropriate NetWare Configuration Guide for full details.    

SnaSessionLimit

A value in the range 1 through 255, specifying the maximum number of concurrently active sessions that will be permitted between the client and the partner LU. If not specified, the parameter defaults to 1. See the appropriate NetWare Configuration Guide for full details.

SnaDLCName    

One of ITRN, SDLC, QLLC or CUSTOM, which is the data link control identification needed for communication with the remote LU. If not specified, the default is ITRN (used for a Token Ring link). See the appropriate NetWare Configuration Guide for full details.    

SnaPLUAdapterAddr

A 1- to 12-character string identifying the PLU adapter address (the network adapter address of the partner LU). If not specified, the parameter defaults to a null string. See the appropriate NetWare Configuration Guide for full details.    

SnaMaxRUSize

A value in the range 256 through 4096, specifying the maximum request unit (RU) size to be used. If not specified, this parameter defaults to 1024. See the appropriate NetWare Configuration Guide for full details.    

SnaPacingSize

A value in the range 0 through 63, specifying the maximum number of SNA messages that the local LU can receive without sending a pacing response. If not specified, this parameter defaults to 8. See the appropriate NetWare Configuration Guide for full details.    

SnaRetryCount

A value in the range 1 through 100, specifying the maximum number of retry attempts for the CICS Client when allocating a conversation to, or receiving data from, the CICS server. If not specified, this parameter defaults to 10. See the appropriate NetWare Configuration Guide for full details.

   

Driver

This parameter introduces a section of the initialization file defining the protocol drivers required to communicate with the servers.   

ProtocolName

A 1- to 8-character string. For each protocol referenced from the Server sections, you must provide a Driver section with ProtocolName matching the name of the protocol as specified in the Server section.      

Drivername

A 1- to 8-character string, naming the device driver to be loaded to enable the client to communicate with the server:    
Client Driver Protocol and product
DOS, OS/2, Windows 3.x CCLIBMNB NetBIOS for OS/2, Windows, and DOS
Windows 95 and Windows NT CCLWNTNB NetBIOS for Windows 95 and Windows NT
DOS, OS/2 CCLIBMIP IBM TCP/IP for OS/2 and DOS
DOS, OS/2 CCLFTPIP FTP TCP/IP for OS/2 and DOS
DOS, OS/2 CCLNOVIP Novell LAN Workplace TCP/IP for OS/2 and DOS
Windows 3.x CCLWINIP Windows TCP/IP, as provided by any vendor offering a WINSOCK interface (including IBM, FTP, and Novell)
Windows 95 and Windows NT CCLWNTIP TCP/IP for Windows 95 and Windows NT
Macintosh CCLMACIP MacTCP
Windows CCLIBMSN IBM APPC Networking Services for Windows APPC
OS/2 CCLIBMSN IBM OS/2 Communications Manager/2 APPC
DOS, Windows CCL400SN IBM Client Access/400 APPC for DOS and Windows
DOS, Windows CCLNOVSN Novell NetWare for SAA APPC
Macintosh CCLMACSN APPC using SNA*ps.
Windows 3.x, Windows 95 and Windows NT CCLWNTSN APPC using Microsoft SNA Server.


Customizing the keyboard

   

The keyboard mapping for emulator operation is defined in a keyboard mapping file. The file supplied is CICSKEY.INI in the \CICSCLI\BIN directory by default. It is however, recommended that you create your own customized mapping file.

The keyboard mapping file can be identified by:

  • The /k option of the CICSTERM command, which identifies a keyboard mapping file with a particular terminal (see topic reference #6).

  • The CICSKEY environment variable in CICS Client for DOS, CICS Client for OS/2 and CICS Client for Windows. For example:
    
            SET CICSKEY = C:\CUSTOM\MYKEYS.INI
    
    

    You can set this environment variable in the CONFIG.SYS (CICS Client for OS/2), AUTOEXEC.BAT file (CICS Client for DOS and CICS Client for Windows) or via the System icon in the Windows NT control panel.    

If neither of these is specified, a filename of CICSKEY.INI   in the current directory is assumed.

Note: For CICS Client for Macintosh you can identify the keyboard mapping file by creating an appropriate options file for the CICSTERM command (see "Options files for CICSTERM").

You can change the keyboard mapping file at any time, although changes do not take effect until the next time the terminal emulator is started.

Keyboard mapping file syntax

This section describes the syntax of the keyboard mapping file. A statement must be provided for each key that is needed, because there are no default assignments (except for the alphabetic and numeric keys). There is no case sensitivity, so keywords and values may be entered in uppercase, lowercase or mixed case. Each binding must be on a separate line, and of the following form:

* Figure ccla05 not displayed.

For example, to map the 3270 function EraseEof to the Ctrl+Delete keys pressed together the binding would be as follows:




  bind     EraseEof              Ctrl+Delete ;erase to end of field


The keyboard mapping file

In the mapping file, 3270function can be any one of the following:






      backspace       pa1            pf1      pf13

      backtab         pa2            pf2      pf14

      clear           pa3            pf3      pf15

      cursordown                     pf4      pf16

      cursorleft      printscreen    pf5      pf17

      cursorright     reset          pf6      pf18

      cursorselect    tab            pf7      pf19

      cursorup                       pf8      pf20

      delete          ignore         pf9      pf21

      enter                          pf10     pf22

      eraseeof                       pf11     pf23

      eraseinput                     pf12     pf24

      home

      insert

      newline




The value of ignore is provided to permit unwanted control keys on the keyboard to be ignored. (Unexpected glyphs are not generated.)

The Modifier can be any one of:






      Alt      (IBM keyboards only)

      Ctrl

      Shift




The Key can be any one of the keys shown in Table 17, but some combinations of modifier+key are not supported:

Table 17. CICS client keys that can be mapped
Group Keys
Escape key Escape
Function keys f1 f2 f3 f4 f5 f6 f7 f8 f9 f10 f11 f12
Numeric keys 0 1 2 3 4 5 6 7 8 9
Alphabetic keys a b c d e f g h i j k l m
n o p q r s t u v w x y z
Tab key Tab
Movement keys newline backspace
insert home pageup
delete end pagedown
up left down right
Keypad keys keypad/ keypad* keypad-
keypad7 keypad8 keypad9
keypad4 keypad5 keypad6 keypad+
keypad1 keypad2 keypad3
keypad0 keypad. keypadenter

Keys specific to particular keyboards

 

Some keys are specific to particular types of keyboard.

For CICS Client for Macintosh users:

Function keys

Function keys are available only on the Apple Macintosh extended keyboard.

Movement keys

insert, home, pageup, end, pagedown, delete are available only on the Apple Macintosh extended keyboard.

Apple extras

f13, f14, f15 are available only on the Apple Macintosh extended keyboard.

The following additional keys are unique to Apple Macintosh keyboards:




    § &rprime. f13 f14 f15 keypad=


The following additional key is unique to IBM keyboards:




    rightctrl


Key combinations

The following combinations of modifier and key can be mapped:

No modifier

All keys available for mapping.

Alt modifier

Only function keys, numeric keys, movement keys, and alphabetic keys can be mapped.

Ctrl modifier

Only function keys, movement keys, alphabetic keys, tab key, and keypad keys can be mapped.

Shift modifier

Only function keys, numeric keys, tab key, and alphabetic keys can be mapped.

Note: For CICS Client for Windows, all modifier and key combinations that are not preempted by Windows can be mapped.

A sample key mapping file is shown in Figure 24.

Figure 24. Sample keyboard mapping file for CICS clients



;***********************************************************************

;* IBM CICS Client - 3270 Emulator Keyboard Binding File               *

;***********************************************************************



; Format:

;   bind 3270_key [modifier+]workstation_key

;

; Refer to the "IBM CICS Clients Administration" book for full details

; of available values.



; Note: There are no default key bindings, ensure all required 3270

;       keys are mapped.  "Enter" and "Clear" are particularly

;       important.



; Miscellaneous keys

bind Enter         RightCtrl

bind Enter         KeypadEnter

bind Enter         Ctrl+KeypadEnter

bind Clear         Escape

bind Reset         Alt+R

bind Newline       Newline

bind Tab           Tab

bind Backtab       Shift+Tab

bind Backspace     Backspace

bind Delete        Delete

bind Delete        Keypad.

bind Insert        Insert

bind Insert        Keypad0

bind EraseEof      Ctrl+Delete

bind EraseInput    Alt+End

bind Ignore        End

bind PrintScreen   Alt+P



; Cursor movement

bind CursorUp      Up

bind CursorUp      Keypad8

bind CursorDown    Down

bind CursorDown    Keypad2

bind CursorLeft    Left

bind CursorLeft    Keypad4

bind CursorRight   Right

bind CursorRight   Keypad6

bind CursorSelect  Alt+F3

bind Home          Home

bind Home          Keypad7





; PF and PA keys

bind Pf1           F1

bind Pf2           F2

bind Pf3           F3

bind Pf4           F4

bind Pf5           F5

bind Pf6           F6

bind Pf7           F7

bind Pf7           Keypad9

bind Pf7           PageUp

bind Pf8           F8

bind Pf8           Keypad3

bind Pf8           PageDown

bind Pf9           F9

bind Pf10          F10

bind Pf11          F11

bind Pf12          F12

bind Pf13          Shift+F1

bind Pf14          Shift+F2

bind Pf15          Shift+F3

bind Pf16          Shift+F4

bind Pf17          Shift+F5

bind Pf18          Shift+F6

bind Pf19          Shift+F7

bind Pf20          Shift+F8

bind Pf21          Shift+F9

bind Pf22          Shift+F10

bind Pf23          Shift+F11

bind Pf24          Shift+F12

bind Pa1           Alt+Insert

bind Pa2           Alt+Home

bind Pa3           Alt+PageUp



;***********************************************************************

;* End of file                                                         *

;***********************************************************************



Customizing the screen colors

   

The screen colors and attributes are defined in a color mapping file. A sample is provided for you to tailor. The file supplied is CICSCOL.INI in the \CICSCLI\BIN directory by default. It is recommended that you create your own customized mapping file.

The color mapping file can be identified by:

  • The /c option of the CICSTERM command, which identifies a color mapping file with a particular server (see topic reference #5).

  • The CICSCOL environment variable, in CICS Client for DOS, CICS Client for OS/2, and CICS Client for Windows.     For example:
    
            SET CICSCOL = C:\CUSTOM\MYCOLS.INI
    
    

    You can set this environment variable in the CONFIG.SYS (CICS Client for OS/2) or AUTOEXEC.BAT file (CICS Client for DOS and CICS Client for Windows) or via the System icon in the Windows NT control panel.

If neither of these is specified, a filename of CICSCOL.INI   in the current directory is assumed.

Note: For CICS Client for Macintosh you can identify the color mapping file by creating an appropriate options file for the CICSTERM command (see "Options files for CICSTERM").

A color mapping file is used to provide alternative representations in hardware environments where it is not possible to exactly replicate 3270 screen attributes, for example, blinking or underscore. The color mapping file therefore defines how 3270 screen attributes are emulated on the client hardware.

The color mapping file is optional. However, for most hardware environments a mapping file is required if blinking or underscore support is required by the emulator.

Notes:

  1. If the color mapping file specifies a mapping for an attribute, this mapping is used even if the hardware upon which the client is running actually supports the screen attribute.

  2. If an application requests a 3270 field to be displayed with, for example, underscore, and no emulation setting has been specified, and the hardware cannot display underscore, then the field is displayed without any highlighting at all.

You can change the color mapping file at any time, although changes do not take effect until the next time the terminal emulator is started.

Color mapping syntax

The syntax of the color mapping file is as follows. There is no case sensitivity--keywords and values may be entered in uppercase, lowercase or mixed case. Each binding must be on a separate line, and of the form:

* Figure ccla06 not displayed.

The color mapping file

In the color mapping file, 3270attrib can be any one of the following:




    normal_protected    intensified_protected

    normal_unprotected  intensified_unprotected



    default    blinking_default    underscored_default

    blue       blinking_blue       underscored_blue

    green      blinking_green      underscored_green

    cyan       blinking_cyan       underscored_cyan

    red        blinking_red        underscored_red

    magenta    blinking_magenta    underscored_magenta

    white      blinking_white      underscored_white

    yellow     blinking_yellow     underscored_yellow



    default_highlight



    operator_information_area


Each of fg_color and bg_color (foreground color and background color) can be any one of the following:




    black       light_gray

    blue        light_blue

    brown       yellow

    cyan        light_cyan

    green       light_green

    magenta     light_magenta

    red         light_red

    gray        white


If bg_color is omitted, a default value of black is taken.

The sample color mapping file is shown in Figure 25.

Figure 25. Sample color mapping file



;***********************************************************************

;* IBM CICS Client - 3270 Emulator Color Binding File                  *

;***********************************************************************



; Format:

;   bind 3270_field foreground_color/background_color

;

; Refer to the "IBM CICS Clients Administration" book for full details

; of available values.



; Operation information area at the bottom of the screen.

bind operator_information_area  black/green



; Color used as default for a terminal defined as monochrome, or to display

; characters displayed in the default color when character or field

; attributes are used

bind default                   light_green/black



; Color used for an intense field when either the terminal is defined as

; monochrome, or the screen has been formatted with extended attributes but

; the data to be displayed has default color and highlight.

bind default_highlight         white/black



; Colors used for datastream formatted with field attributes when no

; extended character or field attributes are in use

bind normal_unprotected        light_green/black

bind intensified_unprotected   light_red/black

bind normal_protected          light_cyan/black

bind intensified_protected     white/black



; Colors used for datastream formatted with extended field attributes

; or datastream formatted with character attributes.

bind red                       light_red/black

bind green                     light_green/black

bind blue                      light_cyan/black

bind magenta                   light_magenta/black

bind cyan                      light_cyan/black

bind yellow                    yellow/black

bind white                     white/black



; The following bindings provide a mapping for 3270 blink and under-

; score attributes, as most workstation displays do not provide blink

; or underscore capabilities.  For those that do these bindings could

; be deleted.

bind blinking_default          light_green/gray

bind blinking_red              light_red/gray

bind blinking_green            light_green/gray

bind blinking_blue             light_cyan/gray

bind blinking_magenta          light_magenta/gray

bind blinking_cyan             light_cyan/gray

bind blinking_yellow           yellow/gray

bind blinking_white            white/gray



bind underscored_default       light_green/light_gray

bind underscored_red           light_red/light_gray

bind underscored_green         light_green/light_gray

bind underscored_blue          light_cyan/light_gray

bind underscored_magenta       light_magenta/light_gray

bind underscored_cyan          light_cyan/light_gray

bind underscored_yellow        yellow/light_gray

bind underscored_white         white/light_gray



;* End of file                                                         *



Testing the client/server link

 

After you have prepared the client initialization file, and customized the keyboard and screen color attributes, you can test the client/server link.

  1. Start the CICS server in the normal manner, as described in the documentation for the server.  

  2. For CICS Client for DOS only. You must run the CICSDOSC program before you can start the client.

  3. On the client workstation, enter the command CICSCLI /s=servername), (or click on the equivalent icon), where servername is the name of the server from the client initialization file.

    Note: For CICS Client for Macintosh, you can do this using the CICS Client for Macintosh Administration Utility (see "The CICS Client for Macintosh Administration Utility").

  4. After a few moments, enter the command CICSCLI /l, or click on the equivalent icon. This displays information on the status of the servers to which the client is connected or attempting connection. Verify that the server is available.

If the connection to the server cannot be made, examine any messages and the client error log to determine the cause of the error (see "Problem determination").


[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