Where allowed to run:
|
Parameters Examples Error messages |
Use the Add CICS Terminal Control Table (ADDCICSTCT) command to add an entry to the TCT. Use the TCT to define:
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
LIB | Library | Communications name, *LIBL, *CURLIB | Required, Positional 1 |
GROUP | Group | Communications name | Required, Positional 2 |
CICSDEV | CICS device | Communications name | Required, Positional 3 |
SYSID | Remote CICS system | Communications name, *NONE | Optional, Positional 4 |
RMTDEV | Remote CICS device | Communications name, *CICSDEV | Optional, Positional 5 |
DEVTYPE | Device type | 5250, 3270, 3270P, 3270J, 3270JP, 3151, SCS | Optional, Positional 6 |
PRTFILE | Print file | Qualified object name | Optional, Positional 7 |
Qualifier 1: Print file | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
DEVD | Device description | Name | Optional, Positional 8 |
DEVMODEL | Autoinstall model | *TERMINAL, *MODEL, *BOTH | Optional, Positional 9 |
NETWORK | Network | Communications name, *CICSDEV | Optional, Positional 10 |
ALTSUFFIX | Alternate map set suffix | 0-9, *NONE | Optional, Positional 11 |
DEVSTS | Status | *ENABLED, *DISABLED | Optional, Positional 12 |
ATISTS | ATI supported | *NO, *YES | Optional, Positional 13 |
TTISTS | Transaction entry supported | *NO, *YES | Optional, Positional 14 |
USRARASIZE | User area size | 0-255, 0 | Optional, Positional 15 |
DEVCHRID | Character identifier | Element list | Optional, Positional 16 |
Element 1: Code page | 1-65535, *SYSVAL | ||
Element 2: Graphic character set | 1-65535, *SYSVAL | ||
TRANSID | Transaction | Character value, *ANY | Optional, Positional 17 |
KATAKANA | Japanese alphabet supported | *NO, *YES | Optional, Positional 18 |
SOSI | User specified DBCS data | *NO, *YES | Optional, Positional 19 |
UNATTEND | Unattended mode | *NO, *YES | Optional, Positional 20 |
UCTRN | Auto upper case translation | *NO, *YES, *TRANID | Optional, Positional 21 |
ALTSCN | Alternate screen size | *NONE, 24X80, 27X132 | Optional, Positional 22 |
VALIDATION | Validation capability | *NO, *YES | Optional, Positional 23 |
LIGHTPEN | Light pen supported | *NO, *YES | Optional, Positional 24 |
SHIP | Ship to another CICS system | *NO, *YES | Optional, Positional 25 |
DEVACQ | ATI acquire | *NO, *YES | Optional, Positional 26 |
DSCOMP | Datastream compression | *SITVAL, *NO | Optional, Positional 27 |
Top |
Enter the name of the OS/400 library that contains the group. Possible values are:
Top |
Enter the name of the remote group to which the TCT entry is to be added.
Top |
The terminal used to work with a device. This field is used to identify this TCT entry.
Top |
The name of the remote system identifier defined in the TCS Table in which the device is located.
Note: This entry will be installed as if SYSID(*NONE) was specified, into the runtime resource table definitions Terminal Control facility, when the control region has the same system identifier.
The possible SYSID values are:
Top |
The name by which the terminal is known in the remote system. This field is not valid when SYSID(*NONE) is specified.
The possible RMTDEV values are:
Top |
Type of the CICS terminal.
The possible DEVTYPE values are:
Top |
The name of the print spool file that will be used by this terminal. This is only valid when DEVTYPE is specified as SCS, 3270P, or 3270JP.
Possible library values are:
print-file-name: Specify the name of the file.
Top |
The iSeries device name that is associated with the terminal. This is only required when SYSID(*NONE) is specified and DEVTYPE(SCS) and DEVMODEL(*MODEL) are not specified.
Top |
Indicates whether this terminal can be used as a model to autoinstall terminals. This is only valid when DEVTYPE(5250), DEVTYPE(3270), DEVTYPE(3270J), or DEVTYPE(3151) is specified.
The possible DEVMODEL values are:
Top |
The symbolic network name used to identify the logical unit as it is known throughout the network. The name is supplied to VTAM system definition and is used to build the node initialization block (NIB). This is not valid when DEVMODEL(*MODEL) is specified.
The possible NETWORK values are:
Top |
Enter a number to specify an alternate suffix for this device.
Possible values are:
Top |
Indicates if the terminal can be used by the control region when the TCT entry is defined to the runtime resource table definition Terminal Control facility.
The possible DEVSTS values are:
Top |
Indicates whether the terminal can be used for ATI transactions, or for an ISC session. ISC sessions are for transactions using the terminal as an alternate facility to communicate with another CICS system.
The possible ATISTS values are:
Top |
Indicates if the terminal is allowed to initiate transactions.
Note: When ATISTS(*NO) is specified, then this parameter must have *YES.
The possible TTISTS values are:
Top |
The length of the user area associated with the terminal.
The possible USRARASIZE values are:
Top |
The code page and character set to be used with the terminal.
The possible DEVCHRID values are:
Element 1: Code Page
The code page to be used.
Element 2: Character Set
The graphic character set to be used.
Top |
The transaction identifier defined in the PCT when it is the only transaction that can be executed on the terminal.
The possible TRANSID values are:
When there is not enough space to enter the apostrophes, then enter an ampersand (&) in the first character position to get an extended field size that allows for the entry of additional characters. Blanks are accepted but, when the entry is defined to a control region, anything after the blank is ignored. For example, 'ab g' will be treated as 'ab' in the control region.
Hexadecimal characters should be enclosed in apostrophes and preceded by an uppercase X, for example X'A1A2A3A4'. Any hexadecimal value will be accepted, but, if the value is not a printable character, the entry will be rejected when it is defined to a control region.
Top |
Indicates whether Katakana support is required. Katakana terminals cannot display mixed case output; uppercase characters appear as uppercase English characters, but lowercase characters appear as Katakana characters. BMS will provide automatic upper- casing of lower case Latin characters in BMS fields where the CASE=MIXED options specified, if Katakana support is required on terminal where the map is to be displayed.
User written application may query this terminal attribute and provide additional support.
Possible values are:
Top |
Indicates whether or not the terminal has a mixed EBCDIC/DBCS field capability.
The possible SOSI values are:
Top |
Indicates whether or not the mode of operation for the terminal is unattended.
The possible UNATTEND values are:
Top |
Indicates whether the terminal input is to be translated to uppercase.
The possible UCTRN values are:
Top |
Indicates the alternate screen height and width associated with the terminal.
The possible ALTSCN values are:
Top |
Indicates whether or not the terminal has validation capability. This consists of mandatory fill and mandatory enter.
The possible VALIDATION values are:
Top |
Indicates whether or not the terminal has light pen capability.
The possible LIGHTPEN values are:
Top |
Indicates whether or not the terminal definition may be shipped to a remote CICS system.
The possible SHIP values are:
Top |
Indicates whether or not the terminal is to be acquired by transactions that are initiated automatically by the control region.
The possible DEVACQ values are:
Top |
Indicates whether or not datastream compression may be performed for this terminal.
Possible values are:
Top |
Top |
Top |