1. Application Runtime for CICS Reference Guide
  2. CICS Runtime Configuration Files
  3. Typeterm Configuration File

3.14 Typeterm Configuration File

The following table lists and defines Typeterms supported by ARTTCP.

The filename is typeterms.desc.

The format of a typeterm definition is: 

[typeterm]
<field_name_1>=<field_value_1>
<field_name_2>=<field_value_2>
… …
<field_name_n>=<field_value_n>

For example,

[typeterm]
name=IBM-3278-2
userarealen=255
katakana=YES

Table 3-12 Typeterm Parameters

Field Name Type Values Description
ALTSCREENCOLU MN 9(3) {80|132| …} Specifies the terminal screen size total columns. If the SCRNSIZE=alternate, this parameter is mandatory.
ALTSCREENROW 9(3) {24|32|4 3|27|…} Specifies the terminal screen size total rows If the SCRNSIZE=alternate, this parameter is mandatory.
ALTSUFFIX X(1) 0-9|a-z| A-Z Optional Specifies a 1-character ALTSUFFIX name for the typeterm. Only an alphanumeric character or a blank which means no suffix is accepted. The value is case-insensitive and will be converted to upper-case automatically.
DESCRIPTION X(79) Optional A small textual zone for description of the resource.
EXTERCODE X(10) {ibm-37 | ibm-1388 |ibm-138 0|…} Specifies which encoding type of outbound data is used. The value of this attribute could be any EBCDIC encoding type used in z/OS platform. The default value is ibm-37.
INTERCODE X(10) {ASCII | UTF-8|Sh ift-JIS| …} Specifies which encoding type of inbound data is used. The value of this attribute could be any encoding type used in universal platform. The default value is ASCII.
NAME X(79) Mandatory Name of the typeterm.
PROGSYMBOLS X(3) NO | YES Specifies whether the programmed symbol (PS) facility is supported or not. The default value is NO.
SCRNSIZE X(9) DEFAULT| ALTERNATE Optional. Specifies whether to send/receive map/text with alternative screen size or not. The default value is DEFAULT which does not send/receive map/text with alternative screen size.
SOSI X(3) NO | YES Specifies whether mixed EBCDIC and double-byte character set (DBCS) is supported or not. The default value is NO.
color X(3) NO | YES Designates extended color attributes.
defscreencolumn 9(3) 80 Number of columns of the default screen size.
defscreenrow 9(3) 24 Number of rows of the default screen size.
hilight X(3) NO | YES Indicates whether a terminal supports the highlight feature or not.
logonmsg X(3) NO | YES Indicates whether the “Good Morning” (CSGM) transaction is automatically started on the terminal or not.

Oracle Tuxedo ART provides a default CSGM transaction. Please refer to section for the configuration of the default “Good Morning” (CSGM) transaction.

outline X(3) NO | YES Indicates whether the terminal supports field outlining or not.
swastatus X(10) ENABLED| DISABLED Specifies the resource status.
  • If set to ENABLED, the resource is available.
  • If set to DISABLED, the resource is unavailable for use by the system.
uctran X(10) NO | YES | TRAN
  • YES: translate lowercase alphabetic characters to uppercase.
  • NO: do not translate lowercase alphabetic characters to uppercase
  • TRAN: only translate the transaction ID from lowercase to uppercase.
userarealen 9(3) 0 ~ 255 The terminal control table user area (TCTUA) area size for the terminal.
KATAKANA x(3) NO | YES, Optional Specifies whether KATAKANA support is required. The default value is NO. KATAKANA function can be enabled only if KATAKANA is specified to YES.

Note:

You can either set KATAKANA in terminals.desc or typeterms.desc; however, only if KATAKANA in terminals.desc is not specified to YES or NO, KATAKANA specified in typeterms.desc will take effect.
ATI X(3) NO | YES, Optional Specifies whether transactions can start at the terminal by automatic transaction initiation.

YES: Transactions can start at the terminal by automatic transaction initiation.

NO: Transactions cannot start at the terminal by automatic transaction initiation.

ATI(YES) allows transactions to be started at the terminal by transient data control or by an EXEC CICS START command issued by another transaction. If there is already a transaction at the terminal, the ATI transaction is held until it ends. If you specify ATI(YES), you must specify an IOAREALEN of at least one byte, except for DEVICE(APPC) when ATI and IOAREALEN have forced default values of YES and 0.

If ATI is specified as YES and CREATESESS is specified as YES, and if a transaction is initiated when the terminal is not ACQUIRED, it is automatically acquired.

If this field is defined to neither of above values, it is treated as YES.

TTI X(3) NO | YES, Optional Specifies whether transactions can be initiated at the terminal by a user.

YES: Transactions can be initiated at the terminal by a user. If you also specify ATI(YES), transactions can also be initiated automatically. In this case, the automatic transaction initiation, either by transient data control or interval control, sets a condition in an appropriate terminal control table terminal entry. If both ATI and TTI are specified as YES, and if there is no transaction at the terminal, terminal control initiates the user-defined task. This task is expected to send messages to the terminal.

For a terminal used in the processing of transactions such as inquiries or order entries, specify TTI(YES) and ATI(NO). This also applies to a display station or hard-copy terminal to which no messages are sent without a terminal request and through which transactions are entered. Note that this is the only specification allowed for 3790 inquiry logical units.

NO: Transactions cannot be initiated at the terminal by a user. If you specify NO, specify ATI(YES) to allow transactions to be initiated automatically. An example of this type of terminal is one that is located in a remote location, such as a warehouse, and is unattended but may receive messages. If this field is defined to neither of above values, it is treated as YES.

Parent topic: CICS Runtime Configuration Files