Use this page to view and edit the T-type (terminal type definition) ttype_name. group_name indicates the group to which this T-type belongs.
The title bar gives details of the T-type you are editing and the resource group it belongs to.
Click this to display the CICS Group page group_name.
Click thtis to save changes you have made to the page and refresh the page. This button is displayed only if you have permission to edit the group in which the T-type resides.
Shows the name for this T-type.
Specify a description of the T-type. The text can be up to 60 characters in length, with no restrictions except that if you use a left parenthesis you must ensure that there is a matching right parenthesis.
Choose the type of terminal device:
Check this to indicate that this physical terminal definition may be shipped to a remote system in support of a transaction routing request. Ifa physical terminal definition is not marked shippable, then the target system must have the terminal explicitly defined as a remote terminal for the transaction routing request to succeed.
Specify the page width for the terminal type being defined. The width is defined as a number of columns, in the range 0 through 999. The default is 80.
Specify the page height for the terminal type being defined. The height is defined as a number of rows, in the range 0 through 999. The default is 24.
Specify the page size for the terminal type being defined, if you have specified an alternate screen size (non-default values for Alt Screen, Width and Alt Screen, Height). Alternate page size width is defined as a number of columns, in the range 0 through 999. The default is 80. Unexpected results may occur if the number of columns is not the same as the number of columns you specify for Alt Screen, Width. Defaults to the values specified in Map Size, Width.
Specify the page size for the terminal type being defined, if you have specified an alternate screen size (non-default values for Alt Screen, Width and Alt Screen, Height). Alternate page size height is defined as a number of rows, in the range 0 through 999. Unexpected results may occur if the number of columns is not the same as the number of columns you specify for Alt Screen, Height. Defaults to the values specified in Map Size, Height.
Check this to enable MSS to use the outbound operator identifiers to support the BMS routing facilities required by this terminal type definition.
Check this to enable MSS BMS to delegate part of the presentation formatting to the client facility.
Choose whether or not this terminal type has an ASCII feature:
| No | The terminal type does not have an ASCII feature |
| 7 Bit | Terminals of this type are ASCII-7 terminals. All outbound data is translated to 7-bit ASCII, and all inbound data is translated to EBCDIC |
| 8 Bit | Terminals of this type are ASCII-8 terminals. All outbound data is translated to 8-bit ASCII, and all inbound data is translated to EBCDIC |
Specify the size, in bytes, of the receive buffer of a terminal of this type. This represents the maximum amount of data that the terminal can receive, and depends on the capability of the device. Considerations of line quality might lead you to specify a buffer size that is less than the terminal type's maximum buffer size. A message longer than the receive buffer is broken into as many request units as are necessary. Defaults to 0 (zero). If you specify a zero buffer size, the message is not broken up; the whole message is presented.
Specify the maximum size, in bytes, of a request unit that can satisfy a receive request. The value you specify may be rounded down.
Indicates whether or not messages are routed to a terminal of this type by the EXEC CICS ROUTE command. Check this to indicate that BMS is to route to this terminal messages that are destined for all terminals, as well as messages destined for this terminal. If not checked, no messages are routed to this terminal, even if they are specifically destined for this terminal.
Check this to specify that the logon transaction is initiated when a session is established and displays the logon message on the terminal. Automatic Transaction Initiation (ATI) is used to start the transaction, so you must check ATI. The transaction competes with any other ATI transactions for use of the terminal. If you check Lastline, the logon message does not overwrite any error message currently displayed.
Check this to specify that a session is to be established with the terminal when the region starts up. Leave unchecked to specify that a session is to be established when the user signs on at the terminal.
Check this to enable a transaction to be automatically initiated on this terminal. If you leave this unchecked, you should check TTI to enable users to initiate transactions.
Check this to specify that a session can be initiated from a terminal of this type: EXEC START requests and Automatic Transaction Initiation (ATI) requests are allowed to create sessions automatically. Leave unchecked to specify that EXEC START requests and Automatic Transaction Initiation (ATI) requests are not allowed to create sessions automatically. Such requests are queued or rejected if a session has not been established.
Specify the transaction class of the node error program. Defaults to 0 (zero), which indicates that the default node error program is to be used.
| No | The terminal is not automatically signed off in the absence of user input. |
| Signoff | When the specified time has elapsed after the last input from the operator, the terminal is automatically signed off from CICS. |
| Signoff/Logoff | When the specified time has elapsed after the last input from the operator, the terminal is automatically signed off from
CICS and then logged off from VTAM. (This is not supported for TCAM-attached terminals.) LOGOFF is useful for an autoinstall
model, because virtual storage is not wasted on entries for terminals that have been timed out. If GNTRAN fails to attach
because of unprocessed data in the terminal buffer (resulting in a BID failure), the terminal will be signed off and logged
off. GNTRAN will not run and will have no effect.
Note: You cannot change the value of this attribute when DEVICE(APPC) is specified. The default value in that case is SIGNOFF(NO).
|
| None | The user is not notified. |
| Message | A message is displayed on the screen to say that the system has recovered. The message is specified in two BMS maps; DFHXRC1 and DFHXRC2 for XRF; and DFHXRC3 and DFHXRC4 for VTAM persistent sessions. These maps are in map set DFHXMSG. If reduced takeover time is important, use MESSAGE rather than TRANSACTION. The terminal must be capable of displaying BMS maps, and ATI.must be checked, to specify this option. |
| Transaction | A transaction is initiated at the terminal. The name of the transaction is specified by the RMTRAN system initialization parameter. (The default transaction for RMTRAN is the one specified in the GMTRAN system initialization parameter: the good-morning transaction.) If reduced takeover time is important, use MESSAGE rather than TRANSACTION. ATI must be checked to specify this option. |
Choose how MSS recovers the session and returns the terminal to normal service.
| Sys Default | MSS selects the best recovery strategy based on session activity and the characteristics of the terminal. |
| Clear Receive | MSS sends a CLEAR request to reset the conversation state, or an UNBIND request if the session does not support the CLEAR request. MSS sends the CLEAR or UNBIND request only if the session was busy. |
| Release Sess | MSS sends an UNBIND request to clear the active session, if the session was busy. |
| Unconditional | MSS sends an UNBIND request to clear the active session, whether or not the session was busy. |
| None | The terminal session is not automatically recovered. If you checked Auto Connect, the terminal is automatically reconnected. |
Check this to specify that error messages are to be displayed at the bottom of the screen: If checked, an error message is displayed at the bottom of the screen, starting at a position that enables the entire message to be shown at once. If messages are received in quick succession, an earlier message might be overwritten before the user has time to read it. Messages displayed in this way may have the additional attributes specified by Intensify, Color and Highlight. If Last Line is not checked, an error message is displayed at the current cursor position, and without any additional attributes.
Check this to have error messages displayed in an intensified field (bold). This only has an effect if Last Line is checked.
Choose the color in which error messages are to be displayed on a terminal of this type. A setting other than No takes effect only if Last Line is checked.
Choose the type of highlighting to be used for error messages displayed on a terminal of this type. A setting other than No takes effect only if Last Line is checked.
Specify the default screen width for the 3270 terminal type being defined. This is the screen width that is used when a transaction definition specifies a default screen. Screen width is defined as columns, in the range 0 through 999. The default is 80. There is no validity checking; incorrect sizes might lead to unpredictable behavior.
Specify the default screen height for the 3270 terminal type being defined. This is the screen height that is used when a transaction definition specifies a default screen. Screen height is defined as rows, in the range 0 through 999 The default is 24. There is no validity checking; incorrect sizes might lead to unpredictable behavior.
Specify the alternate screen width for the 3270 terminal type being defined. This is the screen size that is used when a transaction definition specifies an alternate screen. Screen width is defined as columns, in the range 0 through 999. The default is 80. There is no validity checking; incorrect sizes might lead to unpredictable behavior.
Specify the alternate screen height for the 3270 terminal type being defined. This is the screen size that is used when a transaction definition specifies an alternate screen. Screen height is defined as rows, in the range 0 through 999 The default is 24. There is no validity checking; incorrect sizes might lead to unpredictable behavior.
Check this to specify that the terminal type has the APL keyboard feature.
Check this to specify that the terminal type can support the APL text character set.
Check this to specify that the terminal type has the audible alarm feature.
Check this to specify that the terminal type has the color feature, which enables colors to be selected for individual fields.
Check this to specify that the terminal has a typewriter keyboard. Leave this unchecked to specify that the terminal has an operator console keyboard. Both types of keyboard transmit both upper-case and lower-case data.
Check this to specify that the terminal type has the copy feature.
Check this to specify that the terminal type supports extensions to the 3270 data stream. You must check this if Color or Hilight are checked.
Check this to specify that the terminal type has the extended highlight feature, enabling individual fields or characters to be displayed in bold, reverse video, or blinking.
Check this to specify that the terminal type is a Katakana terminal. Katakana terminals do not support mixed case output. Upper-case characters appear as upper-case English, but lower-case characters appear as Katakana characters.
Check this to specify that the terminal type has the light pen selector feature. MSS emulates this feature using mouse clicks.
Check this to specify that the device has the form feed feature.
Specify the coded graphic character set global identifier (CGCSGID) that enables transaction programs to determine what character set is supported by this terminal. Defaults to 0,0, which means that the terminal type does not support this feature. The first field specifies the graphic character set global identifier (GCSGID), and the second field specifies the code page global identifier (CPGID).
Check this to specify that the device has the horizontal form feature. The devices that can use this feature are batch, batch data interchange, interactive, SCSPRT or LUTYPE4 logical units. If checked, BMS uses horizontal tabbing when formatting output documents. If unchecked, the HTAB option in the BMS map definition is ignored.
Check this to specify that the device has the vertical form feature. The devices that can use this feature are batch, batch data interchange, interactive, SCSPRT or LUTYPE4 logical units. If checked, BMS uses vertical tabbing when formatting output documents. If unchecked, the VTAB option in the BMS map definition is ignored.
Check this to enable a 3270 device to shift its display into its alternate mode.
Check this to specify that the terminal type supports mixed EBCDIC and DBCS fields.
Check this to specify that the terminal type supports the programmed symbol facility. This facility enables you to use a maximum of six sets of 191 characters.
Check this to specify that the terminal type supports field outlining.
Check this to enable the numeric lock.
Check this to specify that BMS buffers formatted data streams that are sent to a terminal of this type, that is, when an application issues a series of SEND TEXT PRINT commands, MSS sends a page to the terminal only when it is full. Leave thus unchecked to specify that when an application issues a series of SEND TEXT PRINT commands, MSS sends a page to the terminal for every command issued, filling up the page by appending blank lines if necessary.
Check this to specify that output BMS screens with the PRINT option set on are copied automatically to an attached printer.
Check this to enable background transparency.
Check this to enable MSS to use the QUERY structured field to determine the characteristics of the device.
Check this to specify that the 3270 device has the text-keyboard feature.
Check this to specify that the terminal type has the magnetic stripe reader feature. MSS emulates this feature using mouse clicks.
Check this:
Check this to enable the device to use partitions. This option is not valid for SCS printers.
Check this to specify that MSS is to reassemble request units into complete messages before passing data from a terminal of this type to a transaction program. Leave this unchecked to specify that messages are to be received by the transaction program in individual request units.
Specify the size, in bytes, of the user area of a terminal of this type. Defaults to 0 (zero).
Check this to force the user area into shared storage such hat it can be accessed by transactions that do not have this device as the primary facility.
Choose how data entered in data entered in lower case is to be treated:
| Yes | Data input in lower case is translated to upper case. |
| No | Data input in lower case is not translated to upper case. |
| Tranid | Transaction identifiers input in lower case are translated to upper case; not other input data is translated. |
Specify the minimum and maximum sizes, in bytes, of the terminal I/O area to be passed to a transaction program when it issues a RECEIVE. If you enter a number in the first field, a terminal I/O area of at least that size is passed to the transaction program. If you specify values in both fields, and a message longer than that specified by the first field, but shorter than that specified by the second field is received, then a terminal I/O area of the maximum size is passed to the transaction program. A message longer than that specified by the second field causes the node abnormal condition program to send an exception response to the terminal. Defaults to 0,0. If you check ATI, you must specify a terminal I/O area of at least one byte.
Click this to display the currently installed definition of this resource.
Click this to install (make active) this resource.
Click this to delete this T-type. You only see this button if you have editing permissions for the group to which the T-type belongs.
Click this to create a new T-type, using the values set on this page as the basis for the new T-type.
Click this to create and view dump information for this T-type.