Terminal Configuration File

3.13 Terminal Configuration File

The following table lists and defines terminal available to the CICS application.

The filename is terminals.desc.

The format of a terminal definition is:

[terminal]
<field_name_1>=<field_value_1>
<field_name_2>=<field_value_2>
… …

For example,

[terminal]
name=0001
netname=CICS0001
katakana=YES
[terminal]
name=0002
netname=CICS0002
katakana=YES

ART CICS stores all the terminal runtime status by using Tuxedo /Q. For more information about Implementing Asynchronous CICS Delayed Transactions.

Table 3-11 Terminal Parameters

Field Name	Type	Values	Description
`ALTSUFFIX`	`X(1)`	`0-9\|a-z\|A\u0002Z, Optional`	Specifies a 1-character `ALTSUFFIX` name for the terminal. 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.
`KATAKANA`	`x (3)`	`NO \| YES, Optional`	Specifies whether `KATAKANA` support is required. `NO`: Default value. `KATAKANA` function is disabled. `YES`: `KATAKANA` function is enabled. `Other values`: Invalid values. System will automatically search `KATAKANA` in `typeterms.desc.`
`GROUP`	`X(10)`	`Mandatory`	The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
`NAME`	`X(4)`	`Mandatory`	Terminal identifier. Note: When there are multiple entries with same `TERMID`, the last entry takes effect. If the length exceeds, the value will be ignored and warning message will be logged in ULOG; if the length is shorter than four characters, spaces will be padded on the right.
`NETNAME`	`X(8)`	`Mandatory`	Network name of the terminal. Note: The value of `NETNAME` must be unique; otherwise, `ARTCNX` server fails to boot and reports the error output in ULOG and stdout. If the length exceeds, the value will be ignored and warning message will be logged in ULOG; if the length is shorter than eight characters, spaces will be padded on the right.
`INSERVICE`	`X(3)`	`NO \| YES, Optional`	Specifies the status of the terminal that is being defined. `YES`: Transactions may be initiated and messages may automatically be sent to the terminal. `NO`: The terminal can neither receive messages nor transmit input. The default value is `YES`. If this field is defined to neither of above values, it is treated as `YES`.
`ATI`	`X(3)`	`NO \| YES, Optional`	Specify whether or not the terminal is available for use by transactions that are automatically initiated from within CICS. `YES`: The terminal is available for use by transactions that are automatically initiated from within CICS. `NO`: The terminal is not available for use by transactions that are automatically initiated from within CICS. If this field is defined to neither of above values, it is treated as `UNKNOWN`. However, in the event that the same field in `typeterms.desc` is defined to `UNKNOWN` as well, the final value of this field is `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 `UNKNOWN`. However, in the event that the same field in `typeterms.desc` is defined to `UNKNOWN` as well, the final value of this field is `YES`.

Note:

The section name must be set to "terminal"; all keywords are case-insensitive. ART CICS reserves "."; users can use it neither in NAME nor in NETNAME when defining terminals.desc.

Parent topic: CICS Runtime Configuration Files