# Managing terminal resource definitions - IBM - AS/400

Use the terminal control table (TCT) to define:

• The characteristics of a display terminal or printer, that can be used by transactions running on this system. The terminal may be local or remote.
• Model terminals for automatic installation (autoinstall). Because many terminals have many characteristics in common and their resource definitions would be identical, you can use the TCT to create model definitions. Each model definition may apply to a number of terminals. These models are used by CICS/400 to create the necessary terminal definitions for individual terminals when the system is started.
• A terminal to be used for automatic transaction initiation.

Uppercase conversion of terminal input
Transaction IDs and application data can be entered at terminals. In some installations, transaction IDs are case-sensitive; for example, ABCD, abcd, and aBcDcould represent three different transactions. Some applications require all inputdata in uppercase.

Using the interaction of UCTRN options in the TCT and PCT resource definitions, CICS/400 can distinguish between transaction IDs and data, and can apply the correct uppercase conversion to either, neither, or both, as required.

For user data, UCTRN(*YES) in a TCT or PCT entry forces uppercase conversion for all user data associated with the terminal or transaction being defined. UCTRN(*YES) or UCTRN(*TRANID) in the TCT forces uppercase conversion of all transaction IDs entered at the terminal being defined. To suppress uppercase conversion of data, both the TCT and the PCT must specify UCTRN(*NO). When both the TCT and PCT specify UCTRN(*YES), a DBCS character is subject to alteration if either its first or second byte has the equivalent code point as that of an SBCS small Latin character in the code page used by CICS. To avoid this, a user who would like to allow DBCS data in the application is advised to set UCTRN(*NO) in the PCT and either UCTRN(*NO) or UCTRN(*TRNID) in the TCT.

Table shows the results of the various combinations of UCTRN values in the TCT and PCT.

Table . Results of UCTRN settings in TCT and PCT.

This table shows when terminal-entered transaction IDs and data are converted to uppercase, as indicated in each box by Yes or No.

Datastream compression
Datastream compression reduces the length of datastreams at a cost in performance1. In the system initialization table (SIT), the DSCOMP option has four possible values– *ALL, *NONE, 3270, and 5250, which allow compression for all terminals, no terminals, 3270 terminals only, or 5250 terminals only, respectively. In the terminal control table (TCT), the DSCOMP option gives flexibility at the terminal level. In a 3270 terminal definition, DSCOMP(*SITVAL) allows compression for the terminal if DSCOMP in the SIT specifies *ALL or 3270. In a 5250 terminal definition, DSCOMP(*SITVAL) allows compression for the terminal if DSCOMP in the SIT specifies *ALL or 5250. DSCOMP(*NO) for a terminal prevents compression, regardless of the SIT specification. An X in the Compress column, indicates when compression takes place.

The table shows that compression occurs only when the TCT entry specifies DSCOMP(*SITVAL) and the SIT allows compression for the type of terminal.

Table . Results of DSCOMP settings in TCT and SIT

Note: Programming techniques can also be used to reduce the size of the datastream, but may be considered unnecessary if CICS/400 datastream compression is used. If these techniques are employed, they are not affected by the datastream compression applied by the system.

Using the ADDCICSTCT command

Flowchart

Notes:

1. The RMTDEV parameter is not valid when SYSID(*NONE) is specified.
2. The PRTFILE parameter is valid, and required, when DEVTYPE(SCS) is specified.
3. The DEVD parameter is valid, and required, when SYSID(*NONE) is specified, DEVTYPE is not SCS, and DEVMODEL is not *MODEL.
4. The DEVMODEL parameter is valid only when DEVTYPE(5250), DEVTYPE(3270), DEVTYPE(3270J),or DEVTYPE(3151) is specified.
5. The NETWORK parameter is not valid when DEVMODEL(*MODEL) is specified.
6. All parameters preceding this point can be specified positionally.
7. TTISTS(*NO) is valid only when ATISTS(*YES) is specified.

Function
Use the Add CICS/400 Terminal Control Table (ADDCICSTCT) command to add an entry to the TCT.

Required parameters

1. Library (LIB)
2. Enter the name of the OS/400 library that contains the CICS/400 group.
Possible values are:
*LIBL: The library list is used to locate the first OS/400 library that contains the group.
*CURLIB: The current library contains the group. If no current library is specified, the QGPL library is used.
library-name:The name of the OS/400 library that contains the group.
3. Group (GROUP)
4. Enter the name of the remote group to which the TCT entry is to be added.
group-name:The group name may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
5. CICS device (CICSDEV)
6. The terminal id that will be used to refer to this resource. If this TCT entry is defining a model terminal, this parameter identifies the entry, rather than a specific terminal.
terminal-identifier:The terminal identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.

Optional parameters

1. CICS system (SYSID)
2. The name of the remote system identifier defined in the TCS Table in which the device is located. This parameter is required only for remote terminals. If this parameter contains the ID of the local system, the entry will be treated as if *NONE has been entered.
Possible values are:
*NONE: The terminal is defined to the same control region in which it is being used.
system-identifier:The system identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
3. Remote CICS device (RMTDEV)
4. The name by which the terminal is known in the remote system. This parameter is not valid when SYSID(*NONE) is specified.
Possible values are:
*CICSDEV: The terminal associated with the TCT is to be used.
remote-terminal:The remote terminal may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
5. Device type (DEVTYPE)
6. Type of the CICS/400 terminal.
Possible values are:
5250: Terminal supporting 5250 data stream.
3270: Terminal supporting 3270 data stream.
3270P: Printer supporting 3270 data stream.
3270J: Double-byte capable display.
3270JP:
Double-byte capable printer.
3151: ASCII display.
SCS: Printer supporting SCS data stream.
7. Print file (PRTFILE)
8. The name of the print spool file that will be used by this terminal. This is only valid when DEVTYPE(SCS) isspecified.
Possible values are:
*LIBL: The library list for the job that is associated to the control region is used to locate the file.
*CURLIB: The current library for the job that is associated to the control region is used to locate the file. If no library is specified as the current library, the QGPL library is used.
library-name:Specify the name of the library where the file is located.
print-file-name:Specify the name of the file.
9. Device description (DEVD)
10. The OS/400 device name that is associated with the terminal. This is only valid when SYSID(*NONE) is specified, DEVTYPE is not SCS, and DEVMODEL is not *MODEL.
device-description:The device description may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
11. Autoinstall model (DEVMODEL)
12. 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.
Possible values are:
*TERMINAL: The terminal cannot be used as a model to autoinstall terminals.
*MODEL: The terminal can only be used as a model to autoinstall further terminals.
*BOTH: The terminal can be used as a model to autoinstall further terminals.
13. Network (NETWORK)
14. 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 whenDEVMODEL(*MODEL) is specified.
Possible values are:
*CICSDEV: The terminal suffixed with four blanks will be used as the symbolic network name.
network:The network may have a maximum length of 8 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
15. Alternate suffix (ALTSUFFIX)
16. Enter a number to specify an alternate suffix for this device.
Possible values are:
*NONE: The device will not have a user defined alternate suffix.
suffix:A number in the range 0 through 9. This numeric suffix will be appended by BMS to map set names, if the transaction uses the alternate screen size (or if the default and alternate screen sizes are the same).
17. Status (DEVSTS)
18. Indicates whether the terminal can be used by the control region when the TCT entry is defined to the runtime resource table definition Terminal Control facility.
Possible values are:
*ENABLED: The terminal can be used by the control region.
*DISABLED: The terminal cannot be used by the control region.
19. ATI supported (ATISTS)
20. 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.
Possible values are:
*NO: The terminal cannot be used by the control region ATI facility.
*YES: The terminal can be used by the control region ATI facility.
21. Transaction entry supported (TTISTS)
22. Indicates whether transactions may be started at this terminal.
Note: When ATISTS(*NO) is specified, this parameter must be *YES.
Possible values are:
*YES: Transactions may be started at this terminal.
*NO: Transactions may not be started at this terminal. Transactions running on this terminal must be started by ATI or by EXEC CICS START commands.
23. User area size (USRARASIZE)
24. The length of the user area associated with the terminal.
Possible values are:
0: No user area will be used.
user-area-length:The user-area-length must be numeric, greater than or equal to 0 and less than or equal to 255.
25. Character identifier (DEVCHRID)
26. The code page and character set to be used with the terminal.
Possible values are:
1. Element 1: Code page
2. The code page to be used.
*SYSVAL: Use the OS/400 system code page.
code-page:The code-page must be numeric, greater than or equal to 1 and less than or equal to 65 535.
3. Element 2: Graphic character set
4. The graphic character set to be used.
*SYSVAL: Use the OS/400 system character set.
character-set:The character-set must be numeric, greater than or equal to 1 and less than or equal 65 535.
27. Transaction (TRANSID)
28. The transaction identifier defined in the PCT when it is the only transaction that can be run on the terminal.
Possible values are:
*ANY: Any transaction can be executed on the terminal.
transaction-identifier:The transaction identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$,@, or #.
29. Japanese alphabet supported (KATAKANA)
30. 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 provides automatic uppercase translation of lowercase Latin characters, in BMS fields where the CASE=MIXED option is specified, if Katakana support is required on the terminal where the map is to be displayed. User written application may query this terminal attribute and provide additional support if required. Possible values are:
*NO: The terminal does not require Katakana support.
*YES: The terminal does require Katakana support.
31. User specified DBCS data (SOSI)
32. Indicates whether or not the terminal has a mixed EBCDIC/DBCS field capability.
Possible values are:
*NO The terminal does not have a mixed EBCDIC/DBCS field capability.
*YES: The terminal has a mixed EBCDIC/DBCS field capability.
33. Unattended mode (UNATTEND)
34. Indicates whether or not the mode of operation for the terminal is unattended.
Possible values are:
*NO: The terminal is to have an attended mode of operation.
*YES: The terminal is to have an unattended mode of operation.
35. Auto upper case translation (UCTRN)
36. Indicates whether or not the terminal is to have uppercase translation done by CICS/400.
Possible values are:
*NO: CICS/400 translates lowercase characters in data input from this terminal to uppercase only if the transaction requires data in uppercase (UCTRN option in ADDCICSPCT command). CICS/400 never translates lowercase characters in a transaction ID.
*YES: CICS/400 always translates lowercase characters in input (data or transaction ID) from this terminal to uppercase.
*TRANID: CICS/400 translates lowercase characters in data input from this terminal to uppercase only if the transaction requires data in uppercase (UCTRN option in ADDCICSPCT command). CICS/400 always translates a transaction ID that contains any lowercase characters to be completely uppercase.
37. Alternate screen size (ALTSCN)
38. Indicates the alternate screen height and width associated with the terminal.
Possible values are:
*NONE: No alternate screen size will be used.
24x80: 24 rows and 80 columns will be used as the alternate screen size.
27x132: 27 rows and 132 columns will be used as the alternate screen size.
39. Validation capability (VALIDATION)
40. Indicates whether or not the terminal has validation capability. This consists of mandatory fill and mandatory enter.
Possible values are:
*NO: The terminal does not have validation capability.
*YES: The terminal has validation capability.
41. Light pen supported (LIGHTPEN)
42. Indicates whether or not the terminal has light pen capability.
Possible values are:
*NO: The terminal does not have light pen capability.
*YES: The terminal has light pen capability.
43. Ship to another CICS system (SHIP)
44. Indicates whether or not the terminal definition is to be shipped to the other CICS system.
Possible values are:
*NO: The terminal definition will not be shipped to the other CICS system.
*YES: The terminal definition will be shipped to the other CICS system.
45. ATI acquire (DEVACQ)
46. Indicates whether or not the terminal is to be acquired by transactions that are initiated automatically by the control region.
Possible values are:
*NO: The control region ATI facility will wait to initiate the transaction, until the terminal is in an acquire state.
*YES: The control region ATI facility will acquire the terminal if it is not already in an acquire state, before initiating the transaction.
47. Datastream compression (DSCOMP)
48. Indicates whether or not a datastream sent to this terminal is to be compressed.
Possible values are:
*SITVAL: Data output to this terminal is compressed if the DSCOMP option in the SIT (system initialization table) specifies the type of this terminal (3270 or 5250) or *ALL.
*NO: Data output to this terminal is never compressed.

Examples
CICSDEV(AP01)
DEVD(DEVICE1) DEVMODEL(*BOTH)

This command adds a TCT entry called AP01 to group ACCT in OS/400 library QCICSSAMP. The device type is 5250 (by default). The definition may be used both as a model for 5250 device types and as a terminal definition for OS/400 device DEVICE1.

Using the CHGCICSTCT command

Flowchart

Notes:

1. The RMTDEV parameter is not valid when SYSID(*NONE) is specified.
2. The PRTFILE parameter is valid, and required, when DEVTYPE(SCS) is specified.
3. The DEVD parameter is valid, and required, when SYSID(*NONE) is specified, DEVTYPE is not SCS, and DEVMODEL is not *MODEL.
4. The DEVMODEL parameter is valid only when DEVTYPE(5250), DEVTYPE(3270), DEVTYPE(3270J), or DEVTYPE(3151) is specified.
5. The NETWORK parameter is not valid when DEVMODEL(*MODEL) is specified.
6. All parameters preceding this point can be specified positionally.
7. TTISTS(*NO) is valid only when ATISTS(*YES) is specified.

Function
Use the Change CICS/400 Terminal Control Table (CHGCICSTCT) command to change an entry in the TCT.

Required parameters

1. Library (LIB)
2. Enter the name of the OS/400 library that contains the CICS/400 group.
Possible values are:
*LIBL: The library list is used to locate the first OS/400 library that contains the group.
*CURLIB: The current library contains the group. If no current library is specified, the QGPL library is used.
library-name:The name of the OS/400 library that contains the group.
3. Group (GROUP)
4. Enter name of the group containing the TCT entry is to be changed.
group-name:The group name may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
5. CICS device (CICSDEV)
6. The terminal id that will be used to refer to this resource. If this TCT entry is defining a model terminal, this parameter identifies the entry, rather than a specific terminal.
terminal-identifier:The terminal identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.

Optional parameters

1. CICS system (SYSID)
2. The system identifier defined in the TCS Table of the remote device. This parameter is required only for remote terminals. If this parameter contains the ID of the local system, the entry will be treated as if *NONE has been entered.
Possible values are:
*SAME: The value currently specified in the TCT entry will remain the same.
*NONE: The terminal is defined to the same control region in which it is being used.
system-identifier:The system identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
3. Remote CICS device (RMTDEV)
4. The identifier by which the terminal is known on the remote system. This parameter is not valid when SYSID(*NONE) is specified.
Possible values are:
*SAME: The value currently specified in the TCT entry will remain the same.
*CICSDEV: The terminal associated with the TCT is to be used.
remote-terminal:The remote terminal may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
5. Device type (DEVTYPE)
6. Indicates the type of terminal.
Possible values are:
*SAME:
The value currently specified in the TCT entry will remain the same.
5250: Terminal supporting 5250 data stream.
3270: Terminal supporting 3270 data stream.
3270P: Printer supporting 3270 data stream.
3270J: Double-byte capable display.
3270JP:
Double-byte capable printer.
3151: ASCII display.
SCS: Printer supporting SCS data stream.
7. Print file (PRTFILE)
8. The name of the print file to be used by the terminal. This is only valid when DEVTYPE(SCS) is specified.
Possible library values are:
*SAME: The value currently specified in the TCT entry will remain the same.
*LIBL: The library list for the job that is associated to the control region is used to locate the file.
*CURLIB: The current library for the job that is associated to the control region is used to locate the file. If no library is specified as the current library, the QGPL library is used.
library-name:Specify the name of the library where the file is located.
Possible file name values are:
*SAME: The value currently specified in the TCT entry will remain the same.
print-file-name:Specify the name of the file.
9. strong>Device description (DEVD)
10. The OS/400 device name that is associated with the terminal. This is only valid when SYSID(*NONE) is specified, DEVTYPE is not SCS, and DEVMODEL is not *MODEL.
Possible values are:
*SAME: The value currently specified in the TCT entry will remain the same.
device-description: The device description may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
11. Autoinstall model (DEVMODEL)
12. Indicates whether or not this terminal can be used as a model to autoinstall further terminals. This is only valid when DEVTYPE(5250), DEVTYPE(3270), DEVTYPE(3270J), or DEVTYPE(3151) is specified.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*TERMINAL: The terminal cannot be used as a model to autoinstall further terminals.
*MODEL: The terminal can only be used as a model to autoinstall further terminals.
*BOTH: The terminal can be used as a model to autoinstall further terminals.
13. Network (NETWORK)
14. 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.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*CICSDEV: The terminal suffixed with 4 blanks will be used as the symbolic network name.
network:The network may have a maximum length of 8 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
15. Alternate suffix (ALTSUFFIX)
16. Enter a number to specify an alternate suffix for this device.
Possible values are:
*SAME: The value currently defined in the TCT will remain the same.
*NONE: The device will not have a user defined alternate suffix.
suffix:A number in the range 0 through 9. This numeric suffix will be appended by BMS to map set names, if the transaction uses the alternate screen size (or if the default and alternate screen sizes are the same).
17. Status (DEVSTS)
18. Indicates whether or not the terminal can be used by the control region when the TCT entry is defined to the runtime resource table definition Terminal Control facility.
Possible values are:
*SAME: Keep the current value specified in the TCT entry.
*ENABLED: The terminal can be used by the control region.
*DISABLED: The terminal cannot be used by the control region.
19. ATI supported (ATISTS)
20. Indicates whether the terminal can be used by transactions that are initiated automatically by the control region, or in an ISC session. An ISC session is for transactions that are using the terminal as an alternate facility to communicate with another CICS system.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO: The terminal cannot be used by the control region ATI facility.
*YES: The terminal can be used by the control region ATI facility.
21. Transaction entry supported (TTISTS)
22. Indicates whether transactions may be started at this terminal.
Note: When ATISTS(*NO) is specified, this parameter must be *YES.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*YES: Transactions may be started at this terminal.
*NO: Transactions may not be started at this terminal. Transactions running on this terminal must be started by ATI or by EXEC CICS START commands.
23. User area size (User area size (USRARASIZE))
24. The length of the user area associated with the terminal.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
user-area-length:The user-area-length must be numeric, greater than or equal to 0 and less than or equal to 255.
25. Character identifier (DEVCHRID)
26. The code page and character set to be used with the terminal.
Possible values are:
1. Element 1: Code page
2. The code page to be used.
*SAME: Keep the value currently specified in the TCT entry.
*SYSVAL: Use the OS/400 system code page.
code-page:The code-page-number must be numeric, greater than or equal to 1 and less than or equal to 65 535.
3. Element 2: Graphic character set
4. The graphic character set to be used.
*SAME: Keep the value currently specified in the TCT entry.
*SYSVAL: Use the OS/400 system character set.
character-set:The character-set must be numeric, greater than or equal to 1 and less than or equal to 65 535.
27. Transaction (TRANSID)
28. The transaction identifier defined in the PCT, when it is the only transaction allowed to run on the terminal.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*ANY: Any transaction can be executed on the terminal.
transaction-identifier:The transaction identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$,@, or #.
29. Japanese alphabet supported (KATAKANA)
30. 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 provides automatic uppercase translation of lowercase Latin characters, in BMS fields where the CASE=MIXED option is specified, if Katakana support is required on the terminal where the map is to be displayed. User written application may query this terminal attribute and provide additional support if required. Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO: The terminal does not require Katakana support.
*YES: The terminal does require Katakana support.
31. User specified DBCS data (SOSI)
32. Indicates whether or not the terminal has mixed EBCDIC/DBCS field capability.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO The terminal does not have mixed EBCDIC/DBCS field capability.
*YES: The terminal has mixed EBCDIC/DBCS field capability.
33. Unattended mode (UNATTEND)
34. Indicates whether or not the mode of operation for the terminal is unattended.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO: The terminal is to have an attended mode of operation.
*YES: The terminal is to have an unattended mode of operation.
35. Auto uppercase translation (UCTRN)
36. Indicates whether or not the terminal is to have uppercase translation done by CICS/400.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO: CICS/400 translates lowercase characters in data input from this terminal to uppercase only if the transaction requires data in uppercase (UCTRN option in ADDCICSPCT command). CICS/400 never translates lowercase characters in a transaction ID.
*YES: CICS/400 always translates lowercase characters in input (data or transaction ID) from this terminal to uppercase.
*TRANID: CICS/400 translates lowercase characters in data input from this terminal to uppercase only if the transaction requires data in uppercase (UCTRN option in ADDCICSPCT command). CICS/400 always translates a transaction ID that contains any lowercase characters to be completely uppercase.
37. Alternate screen size (ALTSCN)
38. Indicates the alternate screen height and width associated with the terminal.
Possible values are:
*SAME: Keep the value currently specified in the TCT table.
*NONE: No alternate screen size will be used.
24x80: 24 rows and 80 columns will be used as the alternate screen size.
27x132: 27 rows and 132 columns will be used as the alternate screen size.
39. Validation capability (VALIDATION)
40. Indicates whether or not the terminal has validation capability. This consists of the mandatory fill and mandatory enter.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO: The terminal does not have validation capability.
*YES: The terminal has validation capability.
41. Light pen supported (LIGHTPEN)
42. Indicates whether or not the terminal has light pen capability.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO: The terminal does not have light pen capability.
*YES: The terminal has light pen capability.
43. Ship to another CICS system (SHIP)
44. Indicates whether or not the terminal definition is to be shipped to the other CICS system.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO: The terminal definition will not be shipped to the other CICS system.
*YES: The terminal definition will be shipped to the other CICS system.
45. ATI acquire (DEVACQ)
46. Indicates whether or not the terminal is to be acquired by transactions that are initiated automatically by the control region.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*NO: The control region ATI facility will wait to initiate the transaction, until the terminal is in an acquire state.
*YES: The control region ATI facility will acquire the terminal if it is not already in an acquire state, before initiating the transaction.
47. Datastream compression (DSCOMP)
48. Indicates whether or not a datastream sent to this terminal is to be compressed.
Possible values are:
*SAME: Keep the value currently specified in the TCT entry.
*SITVAL: Data output to this terminal is compressed if the DSCOMP option in the SIT (system initialization table) specifies the type of this terminal (3270 or 5250) or *ALL.*NO: Data output to this terminal is never compressed.

Examples
CHGCICSTCT LIB(QCICSSAMP) GROUP(ACCT)
CICSDEV(AP01) SHIP(*YES)

This command changes the TCT entry called AP01 in group ACCT in OS/400 library QCICSSAMP. The definition may now be shipped to other CICS systems.

Using the DSPCICSTCT command

Flowchart

Notes:

1. All parameters preceding this point can be specified positionally.

Function
Use the Display CICS/400 Terminal Control Table (DSPCICSTCT) command to display a TCT entry. You can only view this entry; you can neither make changes to it nor delete it.

Optional parameters

1. Library (LIB)
2. Enter the name of the OS/400 library that contains the CICS/400 group.
Possible values are:
*LIBL: The library list is used to locate the first OS/400 library that contains the group.
*CURLIB: The current library contains the group. If no current library is specified, the QGPL library is used.
library-name:The name of the OS/400 library that contains the group.
3. Group (GROUP)
4. Enter the name of the group containing the TCT entry to be displayed.
Possible values are:
*FIRST: No group is specified, the first group found is used.
group-name:The group name may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
5. CICS device (CICSDEV)
6. The name of the TCT entry to be displayed. This is also known as the terminal used to work with a device.
Possible values are:
*FIRST: Display the first TCT entry.
*ALL: Display all of the TCT entries.
terminal-identifier:The terminal identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
generic*-cicsdev:Specify the generic name of the terminal. A generic name is a string of one or more characters followed by an asterisk (*); for example, ABC*. If a generic name is specified, then all entries with terminal identifiers beginning with the generic name are displayed. If an asterisk is not included with the generic name, the system assumes the value to be the complete terminal.
7. Location of output (OUTPUT)
8. Enter the location of the output from this command.
Possible values are:
*: The output is either displayed (if requested by an interactive job) or printed with the job spool output (if requested by a batch job).
*PRINT: The output is printed with the job spool output.

Examples
DSPCICSTCT LIB(QCICSSAMP) GROUP(ACCT) CICSDEV(*ALL)
This command displays all TCT entries located in group ACCT in OS/400 library QCICSSAMP.

Using the RMVCICSTCT command
Flowchart

Notes:

1. All parameters preceding this point can be specified positionally.

Function
Use the Remove CICS/400 Terminal Control Table (RMVCICSTCT) command to delete an entry from the TCT.

Required parameters

1. Library (LIB)
2. Enter the name of the OS/400 library that contains the CICS/400 group.
Possible values are:
*LIBL: The library list is used to locate the first OS/400 library that contains the group.
*CURLIB: The current library contains the group. If no current library is specified, the QGPL library is used.

Notes:
1 All parameters preceding this point can be specified positionally.

library-name:The name of the OS/400 library that contains the group.

3. Group (GROUP)
4. Enter the name of the group containing the TCT entry to be removed.
Possible values are:
*FIRST: No group is specified, the first group found is used.
group-name:The group name may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
5. CICS device (CICSDEV)
6. The name of the TCT entry to be removed. This is known as the terminal used to work with a device.
Possible values are:
*FIRST: Remove the first TCT entry.
*ALL: Remove all of the TCT entries.
terminal-identifier:The terminal identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
generic*-cicsdev:Specify the generic name of the terminal. A generic name is a string of one or more characters followed by an asterisk (*); for example, ABC*. If a generic name is specified, then all entries with terminal identifiers beginning with the generic name are removed. If an asterisk is not included with the generic name, the system assumes the value to be the complete terminal.

Examples
RMVCICSTCT LIB(QCICSSAMP) GROUP(ACCT)
CICSDEV(ABC*)

This command removes all TCT entries, that start with ABC and end with anything, located in group ACCT in OS/400 library QCICSSAMP.

Using the WRKCICSTCT command

Flowchart

Notes:

1. All parameters preceding this point can be specified positionally.

Function
Use the Work with CICS/400 Terminal Control Table (WRKCICSTCT) command to list entries in the TCT. You can change, remove, copy or display entries, or add new entries to the list.

Optional parameters

1. Library (LIB)
2. Enter the name of the OS/400 library that contains the group.
Possible values are:
*LIBL: The library list is used to locate the first OS/400 library that contains the CICS/400 group.
*CURLIB: The current library contains the CICS/400 group. If no library is specified as the current library, the QGPL library is used.
library-name:Specify the name of the OS/400 library that contains the group.
3. Group (GROUP)
4. Enter the name of the group containing the TCT entries to be listed.
Possible values are:
*FIRST: No group is specified. The first group found is used.
group-name:The group name may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
5. CICS device (CICSDEV)
6. Enter the name of the TCT entry to be listed. This is the name of the terminal.
Possible values are:
*ALL: List all TCT entries.
*FIRST: List the first TCT entry.

Notes:
1 All parameters preceding this point can be specified positionally.

terminal-identifier:The terminal identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or$, @, or #.
generic*-cicsdev:Specify a generic terminal identifier. A generic name is a string of one or more characters followed by an asterisk (*); for example, ABC*. If a generic name is specified, then all entries with terminal identifiers beginning with the generic name are listed. If an asterisk is not included with the generic name, the system assumes the value to be the complete terminal.

Examples
WRKCICSTCT LIB(QCICSSAMP) GROUP(ACCT)

This command lists all TCT entries located in group ACCT in OS/400 library QCICSSAMP.