TYPETERM attributes

You will get unexpected results if the columns value of ALTPAGE is different from that of ALTSCREEN. The rows value of ALTPAGE can usefully be less than that of ALTSCREEN, perhaps to reserve the bottom line of the screen for error messages.

If you use the QUERY structured field, the alternate page size used is the size set up as the alternate screen size. For terminals that can be queried, you can set ALTPAGE to zero and have the ALTSCREEN value defined explicitly by the CINIT BIND. If ALTPAGE is not zero, it is possible to have different values for the ALTPAGE and the ALTSCREEN.

No validity checking is performed on the screen size selected, and incorrect sizes may lead to unpredictable results.

For BSC devices, both the alternate and default screen sizes are determined by the device hardware. The alternate screen size is the maximum screen size. For the 3290 display, both the default and alternate screen sizes are determined by the customer setup procedure.

For SNA devices (LUTYPE2 and LUTYPE3), you can specify any value for both alternate and default screen sizes, up to the maximum physical screen size. In particular, both the alternate and default screen sizes can be the maximum screen size, or the default screen size can be the maximum screen size with no alternate screen size specified. The SNA bind is generated by CICS® from this information. You do not need to provide logmode table entries, or to customize the device.

For non-SNA 3270 and LUTYPE2 devices, you can use the QUERY structured field to determine the alternate screen size that has been set up for the display. To use QUERY, leave the DEFSCREEN to default to (24,80) and leave ALTSCREEN unspecified. The alternate screen size is the size set up by the terminal user. Otherwise, QUERY(COLD) or QUERY(ALL) has no effect on the alternate screen size. Leaving ALTSCREEN unspecified without using QUERY under the conditions described results in an alternate screen size of (00,00).

If you use dual screen sizes, you can make a CICS transaction use the alternate screen size by coding SCRNSIZE(ALTERNATE) in its associated profile. If an application consists of several pseudo-conversationally linked transactions, specify SCRNSIZE(ALTERNATE) in the profile for each of these transactions if the application uses the alternate screen size.

For 3287 and 3289 printers, the value specified must equal the buffer size of the particular device. For non-SNA 3287 and 3289 printers, the sizes depend on the feature ordered, not on the model number. For SNA printers, there are no features, and any two sizes can be specified from the list of valid sizes. When printing to a printer whose associated TERMINAL definition has PRINTERCOPY(YES) specified, the ALTSCREEN value should match the screen size of the terminal whose screen is to be printed. If the values differ, unpredictable results may occur.

blank

Leave this attribute blank if you do not want a suffixed map set.

number

BMS appends this suffix to map set names if the screen size being used is the same value as the alternate screen size; that is, if the transaction has an alternate screen size specified in the PROFILE definition, or if the default and alternate screen size are the same. In this case, BMS map selection routines attempt to load the map set with the suffix specified in the ALTSUFFIX operand.

If there is no such map set, BMS tries to load a map set suffixed with M or L and, if this load fails, BMS tries to load an unsuffixed map set version.

If the transaction uses default screen size, BMS first tries to load a map set suffixed with M or L and, if this load fails, BMS tries to load an unsuffixed map set version.

To use a suffixed map set, you must specify the BMS=(,,,DDS) system initialization parameter.

YES

The 3270 device has the APL keyboard feature.

NO

The 3270 device does not have the APL keyboard feature.

YES

The 3270 device has the APL text feature.

NO

The 3270 device does not have the APL text feature.

You can use the QUERY structured field to determine whether the device is set up to use the APL text feature.

NO

This terminal does not have an ASCII feature.

7

Specify this value to communicate with ASCII-7 terminals. Devices configured with the ASCII-7 feature must be LUTYPE2 or LUTYPE3 without extended 3270 features. Only the following devices are supported:

• 3274 Model 1C and 51C
• 3276 Model 12
• 3278
• 3287

Any terminal configured with the ASCII-7 option has all FM data outbound from CICS converted to ASCII-7, and all FM data inbound to CICS converted to EBCDIC. Only FM request data is translated. All other data in the RU such as LU status or sense data is assumed to be in EBCDIC on output. ASCII-7 does not support data streams that contain extended attributes, such as structured fields and function management headers.

The ASCII-7 support is available on 3274-1C as an option on the configuration of the standard microcode. The use of the ASCII-7 option is determined at session initiation by BIND parameters set by CICS as a result of the TCT definition described.

8

Specify this to communicate with ASCII-8 terminals. Devices configured with the ASCII-8 feature can be LUTYPE1, LUTYPE2, or LUTYPE3 with or without extended 3270 and SCS data stream features.

Any terminal configured with the ASCII-8 option has all FM data outbound from CICS converted to ASCII-8, and all FM data inbound to CICS converted to EBCDIC. All FM request data is translated. This includes the AID, cursor address, FM headers and structured fields. Any other form of the RU such as LU status or sense data is assumed to be in EBCDIC on input and is transmitted in EBCDIC on output.

This ASCII-8 support is intended only for devices that operate in EBCDIC but translate or retranslate the data stream to or from ASCII-8, as is done by this CICS support. This is because the data stream is treated as a character string, and any binary number fields are translated byte by byte as though they were graphic characters. Thus they may not represent their true value while in ASCII form.

The ASCII-8 support is available as a microcode RPQ on the 3274 and is mutually exclusive with the ASCII-7 option. The use of the ASCII-8 option is determined at session initiation by BIND parameters set by CICS as a result of the TCT definitions described.

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.

See also the TTI attribute.

YES

The audible alarm feature is installed.

NO

The audible alarm feature is not installed.

NO

CICS does not attempt to bind sessions when the connection is established.

YES

CICS attempts to bind as a contention winner session, when the connection is established.

ALL

Not applicable.

For background information about AUTOCONNECT, see Defining intercommunication resources.

NO

The device does not have the background transparency feature.

YES

The device does have the background transparency feature.

You can use the QUERY structured field to determine whether the device is set up to use the background transparency feature.

YES

Bracket protocol is to be used. This option is required for the 3790 inquiry and full function logical units. BRACKET(YES) is forced for many DEVICE types

NO

Bracket protocol is not to be used. You must specify BRACKET(NO) for a 3614 logical unit and the 3650 Host Command Processor (HCP) session.

NO

The device does not have the extended color feature.

YES

The device has the extended color feature.

You can use the QUERY structured field to determine whether the device is set up to use the color feature.

NO

The copy feature is included.

YES

The copy feature is not included.

See also the PRINTERCOPY and ALTPRINTCOPY attributes of the TERMINAL definition.

For further details about screen copying, see the CICS 3270 Data Stream Device Guide.

NO

Specify this to prevent internally generated session requests from creating a session. During CICS execution, this can be changed only by a CEMT command.

CREATESESS(NO) prevents EXEC START requests and automatic transaction initiation (ATI) requests for this terminal causing a session to be created. This means that the requests are either queued or rejected when no session is currently established.

YES

Specify this for a status that allows internally generated session requests to create a session. During CICS execution, this status can be generated only by a CEMT command.

CREATESESS(YES) allows EXEC START requests and automatic transaction initiation (ATI) requests for this terminal to cause a session to be created automatically.

For BSC devices, both default and alternate screen sizes are determined by the terminal hardware. The default screen size is (24,80), except for the 3278-1 where it is (12,40).

For SNA devices (LUTYPE2 and LUTYPE3), both default and alternate screen sizes can be any value you choose, up to the maximum physical screen size (see ALTSCREEN). In particular, both default and alternate screen sizes can be the maximum screen size; or the default screen size can be the maximum screen size with no alternate screen size specified. The SNA bind is generated by CICS from this TCT information. You do not need to provide logmode table entries, or to customize the device.

If you type DEVICE(xxxx), where xxxx is a valid device type, on the command line, together with SESSIONTYPE and TERMMODEL if appropriate, other attributes are given appropriate default values. For further guidance, see Default values for TYPETERM attributes. Entering or overtyping the DEVICE, SESSIONTYPE, or TERMMODEL values on the overtype-to-modify panel does not provide these defaults.

For SNA z/OS Communications Server 3270 devices, use the LUTYPE2 or LUTYPE3 attribute as appropriate. LUTYPE2 logical units are those defined by SNA, which accept a 3270-display data stream. LUTYPE3 logical units are those defined by SNA, which accept a data stream similar to that for a 3270 printer.

For a list of device types supported by CICS, see DFHTCT: CICS terminals list. See also Default values for TYPETERM attributes for a list of valid device names and the default attributes that they generate.

YES

CICS is to honor a disconnect request for a z/OS Communications Server device, and issue a z/OS Communications Server CLSDST macroinstruction to terminate the z/OS Communications Server session with that logical unit.

In addition, CESF LOGOFF or GOODNIGHT from the terminal causes disconnection if you specify YES.

YES is essential if the TYPETERM definition is referenced by AUTINSTMODEL TERMINAL definitions, so that autoinstalled terminal entries can be deleted automatically.

YES is the default, but in some situations, if your resource definition does not specify this attribute, CICS enforces the NO value for the attribute if this value is required for compatibility with other options in your resource definition.

NO

CICS is not to honor a disconnect request for a z/OS Communications Server device.

NO

The device does not have a dual-case keyboard.

YES

The device has a dual-case keyboard.

The colors you can specify are:

NO

An error message is displayed at the current cursor position and without any additional attributes.

YES

An error message is displayed starting at the beginning of the line nearest the bottom of the screen so that the whole message fits on the screen.

Because all error messages occupy the same line, if the messages are received in quick succession, they overlay one another and earlier messages may disappear before they have been read.

NO

The device does not support 3270 data stream extensions.

YES

The device supports 3270 data stream extensions.

If extended data stream (EXTENDEDDS) is set to YES, the device will support the write structured field COMMAND and Outbound Query structured field.

You can use the QUERY structured field to determine whether the device is set up to use the extended data stream. Using the QUERY structured field sets EXTENDEDDS to YES if query is valid.

NO

Do not accept user-supplied parameters for inclusion in the function management header built by BMS.

YES

Accept user-supplied parameters for inclusion in the function management header built by BMS.

NO

The device does not have the form feed feature.

YES

The device has the form feed feature.

If DEVICE(SCSPRINT) is specified, BMS inserts a form-feed character at the beginning of the data stream. This causes the device to skip to the top margin of a new page before starting to print.

The top margin is defined by a set vertical format (SVF) data stream, and may be a line number equal to or greater than one. If a SVF data stream has not been sent to the printer, the top margin is line one. The line counter in the device is set to 1 when the operator sets up the paper.

Note that the device may also perform an automatic form feed if you try to print beyond a bottom margin. The bottom margin is also determined by the SVF data stream and defaults to the maximum presentation line (MPL). The MPL is the last line on the page and its value represents the page or form length as a number of lines (that is, physical page size times the line density). Both the MPL and the line density can be determined by the SVF data stream. Otherwise the MPL (the number of lines) can be set up on the device by the operator.

If DEVICE(3270), DEVICE(3270P), DEVICE(LUTYPE2), or DEVICE(LUTYPE3) is specified, use FORMFEED(YES) in conjunction with the FORMFEED option in the BMS SEND commands. Using form feed on display devices provides for a skip to a new page when the screen data is copied to a printer.

The options discussed here for SCSPRINT operation do not apply when the devices are operating as 3270P or LUTYPE3 devices. In this case there is only the concept of a form length, and this can be set on the device only by the operator.

A-Z 0-9 $ @ #

The GROUP name can be up to 8 characters in length. Lowercase characters are treated as uppercase characters.

NO

The device does not have the extended highlight facility.

YES

The device has the extended highlight facility.

You can use the QUERY structured field to determine whether the device is set up to use the extended highlight facility.

NO

The device does not have the horizontal form feature.

YES

The device has the horizontal form feature.

NO

The HTAB option in the BMS map definition is ignored.

YES

BMS uses horizontal tabbing when formatting output documents.

The maximum value that you can specify for IOAREALEN is 32767 bytes.

NO

Katakana support is not required.

YES

Katakana support is required. All lowercase characters sent to the terminal from the following transactions are translated to uppercase:

CBRC CDBC CDBI CEBR CECI CEDA CEDF CEMT CEOT CESN CEST CMSG CRTE CSPG CWTO

A-Z 0-9 $ @ #

    listname  DFHTCT TYPE=LDCLIST,
    LDC(aa=nnn,bb=nnn,....)

listname  DFHTCT TYPE=LDC,LOCAL=INITIAL
          DFHTCT TYPE=LDC=(aa=nnn)....
          DFHTCT TYPE=LDC=(bb=nnn)....
          DFHTCT TYPE=LDC,LOCAL=FINAL

You specify this listname as the value for the LDCLIST attribute on the TYPETERM definition.

This attribute applies only to 3600, 3770 batch, 3770, and 3790 batch data interchange, and LUTYPE4 logical units. The list specifies which LDCs are valid for this logical unit and, optionally, which device characteristics are valid for each LDC. CICS uses the first LDC generated in this list when choosing a default LDC for a logical unit. For further guidance, see DFHTCT logical device codes: z/OS Communications Server non-3270.

NO

The 3270 display does not have the selector pen feature.

YES

The 3270 display has the selector pen feature.

blank

A defined terminal definition uses the BIND image generated by the CICS definitions for this device by means of this TYPETERM definition and its associated terminal definitions. An autoinstalled terminal uses the fields specified in the incoming CINIT.

name

This is the LOGMODE name from a z/OS Communications Server logon mode table that has been set up for use by this logical unit. The name may be up to eight characters in length and must follow assembler language rules. The name must start with an alphabetic character.

Acceptable characters: A-Z 0-9 $ @ # Unless you are using the CREATE command, any lowercase characters that you enter are converted to uppercase.

This allows you to override the BIND image provided by CICS for the logical unit. For further information, see the appropriate CICS subsystem guide.

You cannot code a LOGMODE name when the terminal is a cross-domain resource.

The TCTTE is updated to reflect the logmode bind image fields. These include SEND and RECEIVE sizes and default and alternate screen sizes. If the logmode indicates that the terminal is not queriable, the extended data stream fields are all set to zero.

0 (zero)

This causes CICS to use some of the information from the BIND image contained in the CINIT coming from the logical unit. The BIND image in the CINIT was created by z/OS Communications Server based on the LOGMODE entry defined for the logical unit requesting to log on to CICS. The node initialization block (NIB) is built with LOGMODE=0 and BNDAREA=0. When the TYPETERM's SENDSIZE and RECEIVESIZE have been specified as zero, CICS replaces them with the values from the LOGMODE's RUSIZES.

The TCTTE is updated to reflect the incoming CINIT fields. These include SEND and RECEIVE sizes and default and alternate screen sizes. If the logmode indicates that the terminal is not queriable, the extended data stream fields are all set to 0. Use LOGMODE(0) only in exceptional circumstances. Although the LU is bound with the z/OS Communications Server definition, CICS keeps the main session characteristics from the CICS definition. For example, if a printer is defined to z/OS Communications Server as LUTYPE1 but to CICS as an LUTYPE3 with LOGMODE(0), CICS accepts the bind but sends LUTYPE3 control characters to the printer, giving rise to incorrect results. This restriction does not apply to pipeline terminals.

Note:

1. You should only need to use this value for the logmode attribute in exceptional circumstances.
2. For a logical unit in a cross-domain environment, specify LOGMODE(0) and provide the logical unit mode information in the DLOGMOD and MODETAB operands of the z/OS Communications Server(LU) statement. In a cross-domain environment, LOGMODE with a name causes a z/OS Communications Server error.

• Automatically initiated when the logical unit is first logged on to CICS through z/OS Communications Server
• Initiated after the terminal user's TIMEOUT period has expired under certain conditions.

NO

CICS does not run the 'good morning' transaction.

Note: If you are using a non-SNA terminal such as a Telnet 3270, LOGONMSG(NO) does not automatically release the keyboard lock. You need to press the Reset key to release the keyboard lock.

YES

CICS runs the 'good morning' transaction when the OPNDST exit is successfully completed and a session is established. The transaction is initiated by automatic task initiation (ATI) and competes with other ATI transactions for use of the terminal. Specify ATI(YES) for this TYPETERM.

Note: If you are using a non-SNA terminal such as a Telnet 3270, LOGONMSG(YES) also automatically releases the keyboard lock.

You can use the QUERY structured field to determine whether the device is set up to use a magnetic slot reader.

0

This results in a link to the default node error program module.

tranclass

The transaction class for the (nondefault) node error program module. tranclass can be in the range 1 through 255. For programming information about the node error program, see Writing a node error program.

• 3650, SESSIONTYPE(3270)
• LUTYPE2, for an 8100 Information System using the DPPX operating system with DPPX/DPS Version 2 for presentation services

Use the QUERY structured field to determine whether the device is set up to use outboard formatting.

NO

CICS does not use the outboard operator identifiers.

YES

CICS uses the outboard operator identifiers.

NO

The device does not support field outlining.

YES

The device supports field outlining.

Use the QUERY structured field to determine whether the device is set up to use field outlining.

rows

Indicates the number of rows in the page. The PAGESIZE rows value can usefully be less than the DEFSCREEN rows value, perhaps to reserve the bottom line of a screen for error messages (see the ERRLASTLINE attribute), if the same BMS map is being used for both printing and display.

columns

Indicates the number of characters in each line. Unexpected results occur if the columns value specified in PAGESIZE differs from the columns value specified in DEFSCREEN.

The product of rows and columns must not exceed 32767.

The default value depends on the value you specify for the DEVICE attribute. See Default values for TYPETERM attributes for details.

BMS uses the page size values when preparing output data streams. The specified number of characters in each line of the page should not exceed the physical line width of the terminal. In the case of printers that automatically perform a new-line function on reaching the end of the carriage (for example, 3270 printers), the line width specified here should be less than the physical line width.

This ensures that the formatting of the output data is governed entirely by the new-line (NL) characters supplied by BMS or by you, not by new-line functions performed by the device itself, which would produce additional lines of output, resulting in a physical page depth greater than that specified here.

For 3270-type printers, the hardware limits the amount of data that BMS may transmit. If the map or application program request specifies L40, L64, or L80, or does not specify NLEOM on the SEND MAP command, the product of lines and columns specified in PAGESIZE must not be greater than the buffer size.

If the BMS request specifies NLEOM, the page length may be any number of lines, but the product of lines and columns specified in the DEFSCREEN or ALTSCREEN attributes must not exceed the buffer size of the device. In other words, the number of characters that BMS transmits must not exceed the physical buffer size of the printer.

For a z/OS Communications Server 3600, the PAGESIZE specified is used if a BMS page build operation is attempted without specifying a logical device code (LDC). A default device type of 3604 is assumed.

For 3770, LUTYPE4, or 3790 batch data interchange logical units, the PAGESIZE specified is used if a BMS page build operation is requested without specifying a logical device code (LDC). The default device type is the console printer.

Take care when routing a message to a list of terminals. If the PAGESIZE you have defined (or allowed to default) is too small to accommodate the message, the transaction abends.

For cumulative text processing, the maximum allowed buffer size is 32767. If this is exceeded, BMS internally forces a reduced page length to ensure that the PAGESIZE stays within the limit.

NO

The device is not to use partitions.

YES

The device is to use partitions.

You can use the QUERY structured field to determine whether the device is set up to use partitions.

NO

The printer adapter feature and corresponding 3284 Printer Model 3 are not available.

YES

The printer adapter feature and corresponding 3284 Printer Model 3 are available.

If output is created on the screen by BMS requests with the PRINT option, by BMS requests with the NLEOM option, or by the CMSG command, the contents of the screen are automatically copied to a 3270 printer, whether or not the CICS-defined PRINT key (usually a PA key) was pressed.

NO

Programmed symbol (PS) facility cannot be used.

YES

Programmed symbol (PS) facility can be used.

You can use the QUERY structured field to determine whether the device is set up to use programmed symbols.

NO

CICS does not use the QUERY function.

COLD

CICS uses the QUERY function to determine the characteristics of the device only when the device is first connected after an initial or a cold start of CICS. The device characteristics are stored in the CICS global catalog for use on subsequent warm and emergency starts.

ALL

CICS uses the QUERY function to determine the characteristics of the device each time the device is connected.

APPC terminal For an APPC (LUTYPE6.2) single session terminal, 256 would be a suitable value.

Autoinstalled terminal For an autoinstalled terminal, a nonzero value for RECEIVESIZE specifies either the maximum or actual RECEIVE RUSIZE value used in binding a session for a logical unit defined with this TYPETERM.

In a CICS region running with persistent session support, this option specifies how a terminal end user is notified that the terminal session has been recovered; in a CICS region running with XRF support, it specifies how the terminal user is notified that an XRF takeover has occurred.

In a CICS region running with persistent session support, this option specifies how you want CICS to recover the session, and return the terminal to service on system restart within the persistent session delay interval.

For all recovery options other than NONE, if the action taken is a z/OS Communications Server UNBIND, the UNBIND is followed by a z/OS Communications Server SIMLOGON.

SYSDEFAULT is the default, but in some situations, if your resource definition does not specify this attribute, CICS enforces the NONE value for the attribute if this value is required for compatibility with other options in your resource definition.

NO

CICS is not to release the logical unit.

YES

CICS is to release the logical unit, if the logical unit is not currently part of a transaction.

ALL

BMS routes to this terminal messages that are destined for all terminals as well as those specifically destined for this terminal.

NONE

BMS does not route any messages to this terminal, whether they are destined for all terminals or for this terminal specifically.

SPECIFIC

BMS routes messages to this terminal when they are destined specifically for this terminal, but not when they are destined for all terminals.

FORCE

The terminal will be signed off after a persistent sessions restart or XRF takeover.

NOFORCE

The terminal will remain signed on after a persistent sessions restart or XRF takeover, provided that the RSTSIGNOFF system initialization parameter and the XRFSOFF entry in the CICS segment of the RACF® user profile are both set to NOFORCE.

APPC terminal: For an APPC (LUTYPE6.2) single session terminal, 256 is a suitable value.

Autoinstalled terminal: For an autoinstalled terminal, a nonzero value for SENDSIZE specifies either the maximum or actual SEND RUSIZE value used in binding a session for a logical unit defined with this TYPETERM.

NO

This definition cannot be shipped to a remote system.

YES

This definition can be shipped to a remote system.

Using SHIPPABLE(YES) means that you do not need to ensure that a definition of the terminal exists on the remote system for a locally defined terminal to initiate a transaction in that system. This can be useful when the remote system cannot share the CSD file with the local system.

A definition for the terminal must already be installed in (or already shipped to) the remote system.

For guidance on deciding whether to use SHIPPABLE(YES), see Terminals for transaction routing.

YES

When the specified time has elapsed after the last input from the operator, the terminal is automatically signed off from CICS.

NO

The terminal is not timed out.

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 z/OS Communications Server. 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.

NO

The device does not support mixed EBCDIC and double-byte character set (DBCS) fields.

YES

The device supports mixed EBCDIC and double-byte character set (DBCS) fields.

You can use the QUERY structured field to determine whether the device is set up to use mixed EBCDIC and DBCS fields.

1

Specify 1 for the 3270 Model 1 displays and printers (for example, 3277 Model 1) with a default screen or buffer size of 12x40 (480 bytes/characters). TERMMODEL(1) is the default for 3270 Model 1 printers and displays.

Specify 1 for the 3275 Display Station Model 11. The CICS support obtained is identical to that obtained by coding TERMMODEL(1) for 3275 Display Station Model 1.

2

Specify 2 for the 3270 displays and printers (for example, 3278 Model 4) with a default screen or buffer size of 24x80 (1920 bytes/characters). TERMMODEL(2) is the default for the 3286 printer in 3270 compatibility mode.

Specify 2 for the 3275 Display Station Model 12. The CICS support obtained is identical to that obtained by coding TERMMODEL(2) for 3275 Display Station Model 2.

NO

The 3270 device does not have the text-keyboard feature.

YES

The 3270 device has the text-keyboard feature.

NO

The 3288 printer doe not have the text-print feature.

YES

The 3288 printer has the text-print feature.

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.

A-Z 0-9 $ @ #

This name is referred to in all the TERMINAL definitions using this TYPETERM. Note that this TYPETERM definition must be installed before or at the same time as the TERMINAL definitions that reference it.

NO

No uppercase translation is performed.

YES

All the data input from the terminal, both the transaction identifier if present and the program data, is translated to uppercase before any processing.

TRANID

When the input data stream includes a transaction identifier, CICS translates it to uppercase before attempting to locate its definition. However, all the input data, both the transaction identifier and the program data, is passed to the program without any translation.

Therefore both the YES and the TRANID options allow transaction identifiers to be defined in uppercase and to be entered from the terminal in either uppercase or lowercase, but the TRANID option causes the transaction identifier and program data to be passed to the program without any translation.

You can also request translation to uppercase at the transaction level on PROFILE resources (see PROFILE attributes), but be aware that a TYPETERM UCTRAN(YES) definition overrides a PROFILE UCTRAN(NO) definition. So, if you specify TYPETERM UCTRAN(YES), a PROFILE UCTRAN(NO) has no effect. Translation can be overridden by the application program for all RECEIVE requests except the first, by using the ASIS option.

Some national-language characters are not automatically translated when UCTRAN(YES) or UCTRAN(TRANID) is specified. If that is the case, you can use one of the methods described in Uppercase translation.

The terminal user area might be located in 31-bit storage or in 24-bit storage, depending on the value of the TCTUALOC system initialization parameter. The default is that the terminal user area can be in either 31-bit storage or 24-bit storage, but CICS uses 31-bit storage wherever possible. If you require the terminal user area to be in 24-bit storage, because you have application programs that are not capable of 31-bit addressing, specify the system initialization parameter TCTUALOC=BELOW for the CICS region.

For the 3290, specifies whether the 3290 device has the validation feature, which allows fields to be defined as MANDATORY FILL or MANDATORY ENTER.

This option is not valid for SCS printers. If VALIDATION(YES) is specified for an SCS printer, an error message is raised and the option is ignored.

You can use the QUERY structured field to determine whether the device is set up to use the validation feature.

NO

The device does not have the vertical form feature.

YES

The device has the vertical form feature.