>>-TYPETERM(name)--GROUP(groupname)--+-------------------+------> '-DESCRIPTION(text)-' .-ALTPAGE(0,0)----------. >--+-----------------------+--+------------------+--------------> '-ALTPAGE(rows,columns)-' '-ALTSUFFIX(char1)-' .-ASCII(NO)-. .-ATI(NO)--. .-AUTOCONNECT(NO)--. >--+-----------+--+----------+--+------------------+------------> +-ASCII(7)--+ '-ATI(YES)-' +-AUTOCONNECT(ALL)-+ '-ASCII(8)--' '-AUTOCONNECT(YES)-' .-BRACKET(YES)-. .-BUILDCHAIN(NO)--. >--+---------------+--+--------------+--+-----------------+-----> +-AUTOPAGE(NO)--+ '-BRACKET(NO)--' '-BUILDCHAIN(YES)-' '-AUTOPAGE(YES)-' .-CREATESESS(NO)--. .-DISCREQ(YES)-. >--+-----------------+--DEVICE(char8)--+--------------+---------> '-CREATESESS(YES)-' '-DISCREQ(NO)--' .-ERRCOLOR(NO)--------. >--+---------------------+--------------------------------------> +-ERRCOLOR(BLUE)------+ +-ERRCOLOR(GREEN)-----+ +-ERRCOLOR(NEUTRAL)---+ +-ERRCOLOR(PINK)------+ +-ERRCOLOR(RED)-------+ +-ERRCOLOR(TURQUOISE)-+ '-ERRCOLOR(YELLOW)----' .-ERRHILIGHT(NO)--------. .-ERRINTENSIFY(NO)--. .-ERRLASTLINE(NO)--. .-FMHPARM(NO)--. >--+-----------------------+--+-------------------+--+------------------+--+--------------+--> +-ERRHILIGHT(BLINK)-----+ '-ERRINTENSIFY(YES)-' '-ERRLASTLINE(YES)-' '-FMHPARM(YES)-' +-ERRHILIGHT(REVERSE)---+ '-ERRHILIGHT(UNDERLINE)-' .-IOAREALEN(0,0)-----------. >--+--------------------------+--+---------------+--+------------------+--> '-IOAREALEN(value1,value2)-' '-LDCLIST(list)-' +-LOGMODE(logmode)-+ '-LOGMODE(0)-------' .-LOGONMSG(NO)--. .-NEPCLASS(0)---------. >--+---------------+--+---------------------+-------------------> '-LOGONMSG(YES)-' '-NEPCLASS(tranclass)-' .-OBOPERID(NO)--. >--+---------------+--+------------------------+----------------> '-OBOPERID(YES)-' '-PAGESIZE(rows,columns)-' .-RECOVNOTIFY(NONE)--------. >--+---------------------+--+--------------------------+--------> '-RECEIVESIZE(number)-' +-RECOVNOTIFY(MESSAGE)-----+ '-RECOVNOTIFY(TRANSACTION)-' .-RECOVOPTION(SYSDEFAULT)--. .-RELREQ(NO)--. >--+--------------------------+--+-------------+----------------> +-RECOVOPTION(CLEARCONV)---+ '-RELREQ(YES)-' +-RECOVOPTION(NONE)--------+ +-RECOVOPTION(RELEASESESS)-+ '-RECOVOPTION(UNCONDREL)---' .-RSTSIGNOFF(NOFORCE)-. >--+----------------------+--+---------------------+------------> +-ROUTEDMSGS(ALL)------+ '-RSTSIGNOFF(FORCE)---' +-ROUTEDMSGS(NONE)-----+ '-ROUTEDMSGS(SPECIFIC)-' >--+------------------+--+-------------------+------------------> '-SENDSIZE(number)-' '-SESSIONTYPE(type)-' .-SHIPPABLE(NO)--. .-SIGNOFF(YES)----. >--+----------------+--+-----------------+--+--------------+----> '-SHIPPABLE(YES)-' +-SIGNOFF(NO)-----+ +-TERMMODEL(1)-+ '-SIGNOFF(LOGOFF)-' '-TERMMODEL(2)-' .-TTI(YES)-. .-UCTRAN(NO)-----. .-USERAREALEN(0)-----. >--+----------+--+----------------+--+--------------------+-----> '-TTI(NO)--' +-UCTRAN(TRANID)-+ '-USERAREALEN(0-255)-' '-UCTRAN(YES)----' >--| Device properties |---------------------------------------><
Device properties .-APLKYBD(NO)--. |--+-------------------------+--+--------------+----------------> '-ALTSCREEN(rows,columns)-' '-APLKYBD(YES)-' .-APLTEXT(NO)--. .-AUDIBLEALARM(NO)--. >--+--------------+--+-------------------+----------------------> '-APLTEXT(YES)-' '-AUDIBLEALARM(YES)-' .-BACKTRANS(NO)--. .-CGCSGID(0,0)---------. >--+----------------+--+----------------------+-----------------> '-BACKTRANS(YES)-' '-CGCSGID(gcsid,cpgid)-' .-COLOR(NO)--. .-COPY(NO)--. >--+------------+--+-----------+--+-------------------------+---> '-COLOR(YES)-' '-COPY(YES)-' '-DEFSCREEN(rows,columns)-' .-DUALCASEKYBD(NO)--. .-EXTENDEDDS(NO)--. >--+-------------------+--+-----------------+-------------------> '-DUALCASEKYBD(YES)-' '-EXTENDEDDS(YES)-' .-FORMFEED(NO)--. .-HILIGHT(NO)--. .-HORIZFORM(NO)--. >--+---------------+--+--------------+--+----------------+------> '-FORMFEED(YES)-' '-HILIGHT(YES)-' '-HORIZFORM(YES)-' .-KATAKANA(NO)--. .-LIGHTPEN(NO)--. .-MSRCONTROL(NO)--. >--+---------------+--+---------------+--+-----------------+----> '-KATAKANA(YES)-' '-LIGHTPEN(YES)-' '-MSRCONTROL(YES)-' .-OBFORMAT(NO)--. .-OUTLINE(NO)--. .-PARTITIONS(NO)--. >--+---------------+--+--------------+--+-----------------+-----> '-OBFORMAT(YES)-' '-OUTLINE(YES)-' '-PARTITIONS(YES)-' .-PRINTADAPTER(NO)--. .-PROGSYMBOLS(NO)--. >--+-------------------+--+------------------+------------------> '-PRINTADAPTER(YES)-' '-PROGSYMBOLS(YES)-' .-QUERY(NO)---. .-SOSI(NO)--. .-TEXTKYBD(NO)--. >--+-------------+--+-----------+--+---------------+------------> +-QUERY(ALL)--+ '-SOSI(YES)-' '-TEXTKYBD(YES)-' '-QUERY(COLD)-' .-TEXTPRINT(NO)--. .-VALIDATION(NO)--. >--+----------------+--+-----------------+----------------------> '-TEXTPRINT(YES)-' '-VALIDATION(YES)-' .-VERTICALFORM(NO)--. >--+-------------------+----------------------------------------| '-VERTICALFORM(YES)-'
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 (see TYPETERM resource definitions), 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.
Device | Alternate Screen Size |
---|---|
3276-1, 3278-1 | (12,80) |
3276-2, 3278-2 | (24,80) |
3276-3, 3278-3 | (32,80) |
3276-4, 3278-4 | (43,80) |
3278-5 | (27,132) |
3279-2A, 3279-2B | (24,80) |
3279-3A, 3279-3B | (32,80) |
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 further guidance, see the IBM 3290 Information Panel Description and Reference.
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 above results in an alternate screen size of (00,00). For more information about QUERY, see TYPETERM resource definitions.
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.
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.
You can use the QUERY structured field to determine whether the device is set up to use the APL text feature (see TYPETERM resource definitions).
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 above.
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.
Note that 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 above.
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.
For background information about AUTOCONNECT, see the CICS Intercommunication Guide.
You can use the QUERY structured field to determine whether the device is set up to use the background transparency feature (see TYPETERM resource definitions).
You can use the QUERY structured field to determine whether the device is set up to use the color feature. (See TYPETERM resource definitions).
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.
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.
CREATESESS(YES) allows EXEC START requests and automatic transaction initiation (ATI) requests for this terminal to cause a session to be created automatically.
Device | Screen size |
---|---|
3278-1 | (12,40) |
3278-2 | (24,80) |
3276-3, 3278-3 | (24,80) |
3276-4, 3278-4 | (24,80) |
3278-5 | (24,80) |
3279-2A, 3279-2B | (24,80) |
3279-3A, 3279-3B | (24,80) |
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 VTAM 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 Table 1 for a list of valid device names and the default attributes that they generate.
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.
BLUE
RED
PINK
GREEN
TURQUOISE
YELLOW
NEUTRAL
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.
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 (see TYPETERM resource definitions). Using the QUERY structured field sets EXTENDEDDS to YES if query is valid.
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 above 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. See the CICS Application Programming Reference for programming information on the use of the FORMFEED option.
Acceptable characters:
Any
lower case characters you enter are converted to upper case. |
The GROUP name can be up to eight characters in length. Lowercase characters are treated as uppercase characters. Do not use group names beginning with DFH, because these characters are reserved for use by CICS.
You can use the QUERY structured field to determine whether the device is set up to use the extended highlight facility (see TYPETERM resource definitions).
If value2 is not specified, or is less than value1, it defaults to the value of value1.
The maximum value that may be specified for IOAREALEN is 32767 bytes.
CBRC CDBC CDBI CEBR CECI CEDA CEDF CEMT CEOT CESN CEST CMSG CRTE CSPG CWTO
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
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: VTAM non-3270.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
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.
You can use the QUERY structured field to determine whether the device is set up to use a magnetic slot reader (see TYPETERM resource definitions).
For further guidance, see the CICS/OS/VS IBM 3650/3680 Guide, the CICS/OS/VS IBM 3790/3730/8100 Guide, and the DPPX/Distributed Presentation Services Version 2: System Programming Guide.
Use the QUERY structured field to determine whether the device is set up to use outboard formatting (see TYPETERM resource definitions).
Use the QUERY structured field to determine whether the device is set up to use field outlining (see TYPETERM resource definitions).
The product of rows and columns must not exceed 32767.
The default value depends on the value you specify for the DEVICE attribute. See Table 1 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 VTAM 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.
You can use the QUERY structured field to determine whether the device is set up to use partitions (see TYPETERM resource definitions).
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.
You can use the QUERY structured field to determine whether the device is set up to use programmed symbols (see TYPETERM resource definitions).
The effect of RECEIVESIZE depends on whether a RECEIVE RUSIZE is present in the VTAM LOGMODE table. Table 1 shows the RECEIVE RUSIZE used to bind a session for each possible combination of TYPETERM and LOGMODE values.
RECEIVE RUSIZE (VTAM) | TYPETERM RECEIVESIZE | RUSIZE used in bind |
---|---|---|
0 | 0 | 0 |
0 | specified | TYPETERM RECEIVESIZE size |
specified | 0 | This combination is invalid and results in a bind failure with message DFHZC2403 |
specified | specified | TYPETERM RECEIVESIZE size |
Note: The exception
to this table is LOGMODE(0). If you specify this in your TYPETERM
definition, VTAM values are used, irrespective of what else is specified.
|
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.
The effect of RECEIVESIZE depends on whether a RECEIVE RUSIZE is present in the VTAM LOGMODE table. Table 2 shows the RECEIVE RUSIZE used to bind a session for each possible combination of TYPETERM and LOGMODE values.
RECEIVE RUSIZE (VTAM) | TYPETERM RECEIVESIZE | RUSIZE used in bind |
---|---|---|
0 | 0 and BUILDCHAIN(YES) | 256 |
0 | 0 and BUILDCHAIN(NO) | 0 |
0 | specified | TYPETERM RECEIVESIZE size |
specified | 0 | VTAM RECEIVE RUSIZE size |
specified less than or equal to TYPETERM RECEIVESIZE | specified | VTAM RECEIVE RUSIZE size |
specified greater than TYPETERM RECEIVESIZE | specified | this combination is invalid and results in message DFHZC5963 |
VTAM persistent sessions: In a CICS region running with persistent session support, this specifies how a terminal end user is notified that the terminal session has been recovered.
XRF: In a CICS region running with XRF support, this specifies how the terminal user is notified that an XRF takeover has occurred.When TRANSACTION is specified, the first transaction named in the RMTRAN system initialization parameter is used.
The terminal must be defined with the ATI(YES) option, and must be capable of displaying a BMS map.
For the TRANSACTION option, the terminal must be defined with the ATI(YES) option. If reduced takeover time is important, use MESSAGE rather than TRANSACTION.
VTAM persistent sessions: 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.
XRF: In a CICS region running with XRF support, this option specifies how you want CICS to recover the session, and return the terminal to service after an XRF takeover.
For all recovery options other than NONE, if the action taken is a VTAM UNBIND, the UNBIND is followed by a VTAM 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.
Although sessions are recovered, any transactions in-flight at the time of the failure are abended and not recovered. Transactions are also abended if the recovered session is being used by another CICS region over an APPC connection.
See the CICS Recovery and Restart Guide for more information about persistent sessions.
XRF: In a CICS region running with XRF support, this specifies that CICS is to select the optimum procedure to recover a busy session at takeover, depending on the session activity and on the characteristics of the terminal.
RECOVOPTION(NONE) should be used if this terminal or autoinstall model is to be used with persistent sessions (PSDINT = nnn in the SIT) but the terminal may be the subject of an EXEC CICS ISSUE PASS LUNAME() LOGONLOGMODE.
XRF: In a CICS region running with XRF support, this specifies that the logon state is not tracked by the alternate system, and the terminal session is not automatically recovered after a takeover: in effect, the terminal has no XRF support. After takeover, the terminal is reconnected automatically by the alternate system, if you specify AUTOCONNECT(YES).
The effect of SENDSIZE depends on whether a RECEIVE RUSIZE is present in the VTAM LOGMODE table. Table 3 shows the RECEIVE RUSIZE used to bind a session for each possible combination of TYPETERM and LOGMODE values.
SEND RUSIZE (VTAM) | TYPETERM SENDSIZE | RUSIZE used in bind |
---|---|---|
0 | 0 | 0 |
0 | specified | TYPETERM SENDSIZE size |
specified | 0 | 0 |
specified | specified | TYPETERM SENDSIZE size |
Note: The exception
to this table is LOGMODE(0). If you specify this in your TYPETERM
definition, VTAM values are used, irrespective of what else is specified.
|
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.
The effect of SENDSIZE depends on whether a SEND RUSIZE is present in the VTAM LOGMODE table. Table 4 shows the SEND RUSIZE used to bind a session for each possible combination of TYPETERM and LOGMODE values.
SEND RUSIZE (VTAM) | TYPETERM SENDSIZE | RUSIZE used in bind |
---|---|---|
0 | 0 | 0 |
0 | specified | TYPETERM SENDSIZE size |
specified | 0 | VTAM SEND RUSIZE size |
specified less than or equal to TYPETERM SENDSIZE | specified | VTAM SEND RUSIZE size |
specified greater than TYPETERM SENDSIZE | specified | this combination is invalid and results in message DFHZC5963 |
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.
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.
You can use the QUERY structured field to determine whether the device is set up to use mixed EBCDIC and DBCS fields (see TYPETERM resource definitions).
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.
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.
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.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
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.
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 definitions (see PROFILE definition 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.
Table 5 shows which portion of the terminal input is translated (transaction id and/or data) according to the setting of the UCTRAN on the PROFILE and TYPETERM resource definitions.
UCTRAN in PROFILE | UCTRAN in TYPETERM | TRANID translated? | Data Translated? |
---|---|---|---|
YES | YES | Yes | Yes |
YES | NO | No | Yes |
YES | TRANID | Yes | Yes |
NO | YES | Yes | Yes |
NO | NO | No | No |
NO | TRANID | Yes | No |
The TCT user area may be located above or below the 16Mb line in virtual storage. Where it is located depends on the value of the TCTUALOC system initialization parameter. Specify this so that it caters for any programs you may have that are not capable of handling 31-bit addressing.
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 (see TYPETERM resource definitions).