Devices supported

This topic lists the device names that you can use on the TYPETERM definition.

Table 1 is a list of terminal types supported by RDO. To use this table, find the family number of your device in the leftmost column (headed Terminal or System Type). Then look across at the second column (headed Units) to see if your type of units is specifically mentioned. Next look at the third column (headed Attachment) to see what device type you should use on your TYPETERM definition.

The notes that follow the table provide further explanation where required. The following abbreviations are used:
local
channel or adapter attached
s/s
start/stop transmission
SDLC
synchronous data link control
sw
switched
BSC
binary synchronous
nonsw
nonswitched communications
Table 1. z/OS Communications Server terminals and subsystems supported by RDO
Terminal or System Type Units Attachment Notes
3101   Supported as TWX 33/35 9
3230   Supported as INTLU (z/OS® Communications Server)  
3270 3178, 3179, 3180, 3262, 3271, 3272, 3274, 3276, 3290 local, SDLC, BSC nonsw 1, 2
  3275, 3277, 3278, 3279, 3284, 3286, 3287, 3288, 3289 BSC sw or nonsw 2
3270PC 3270PC, 3270PC/G, 3270PC/GX Supported as 3270  
3287 models 11, 12 SDLC supported as SCSPRT 12
3600 3601, 3602, 3690, 3604, 3610, 3612, 3618, 3614, 3624 SDLC, BSC nonsw 3,4,13
3630 3631, 3632, 3643, 3604 attached as 3600 3,10
3640 3641, 3644, 3646, 3647 SDLC attached as INTLU 12
  3642 SDLC attached as SCSPRT 12
  3643 SDLC supported as LUTYPE2 12
  3645 SDLC supported as SCSPRT 12
3650 3651, 3653, 3275, 3284 SDLC 3
3680 3684 Supported as 3790/3650 3
3730 3791 Supported as 3790 3
3767   SDLC s/s supported as 2740/2741  
3770 3771, 3773, 3774 SDLC 3,5
  3775, 3776, 3777 BSC supported as 2770  
3790 3791 SDLC or local 3,6
4300 4331, 4341, 4361, 4381 BSC or SDLC 3,7
4700 4701-1 Supported as 3600 3,4
5280   Supported as 3270 (z/OS Communications Server)  
5520  
SDLC supported as 3790 full-function LU
BSC supported as 2770
SDLC attached as APPC
 3
5550   Supported as 3270  
5937   SDLC/BSC attached as 3270 2
6670  
SDLC
BSC supported as 2770
  
8100 8130/8140 processors with DPCX Supported as 3790 3
  DPPX/BASE using Host Presentation Services or Host Transaction Facility Attached as 3790 3
  DPPX/DSC or DPCX/DSC (including 8775 attach) Supported as 3270 3,11
8775   SDLC supported as LUTYPE2  
8815   Supported as APPC  
Displaywriter  
Supported as APPC
SNA for EDDS
Supported as 3270;
attached as 2741 (s/s)or 3780 (BSC)
SDLC attached as APPC
  
Personal Computer   Supported as 3270 and as APPC 13
PS/2   Supported as 3270 and as APPC 13
Scanmaster   Supported as APPC  
Series/1   Attached as System/3;supported as 3650 Pipeline (z/OS Communications Server) or 3790 (full function LU) 3
System/32 5320
SDLC supported as 3770
BSC supported as 2770
 3,8
System/34 5340
SDLC supported as 3770
BSC attached as System/3
 3,8
System/36  
Supported as System/34
SDLC attached as APPC
  
System/38 5381
SDLC attached as 3770
SDLC attached as APPC
BSC attached as System/3
 3,8
AS/400 5381
SDLC attached as 3770
SDLC attached as APPC
BSC attached as System/3
 3,8
System/370   SDLC attached as APPC 3
System/390®   SDLC attached as APPC 3
IBM z Systems®   SDLC attached as APPC 3
TWX 33/35  
z/OS Communications Server (via NTO) ss sw
 9
WTTY  
z/OS Communications Server (via NTO) ss nonsw
 9
Note:
  1. CICS® supports the 3290 through both the terminal control and the BMS interfaces. The 3290 can be in one of three states: default, alternate, or partitioned. Up to 16 partitions can be defined. The 3290 also has the programmed symbols and extended highlighting features, as well as two kinds of data validation feature, mandatory fill and mandatory enter. A 3290 terminal can be configured as from one to five logical units. You define the size of each logical unit when setting up the 3290. You must ensure that the resource definitions of each logical unit match the setup size, to prevent unpredictable results. Up to four interactive screens in any configuration can be active at the same time, but only one interactive screen can be defined as having programmed symbols at any time; that is, all programmed symbol sets must be assigned to the interactive screen.

    To display long lines of data, such as the 132-character lines of CEMT output, specify a default screen width of 132 characters.

    If you intend to use the large buffer, you might have to specify a much larger value for IOAREALEN (see TYPETERM attributes). Whether you need to do this depends on whether operators are likely to modify, or enter, large quantities of data. If a terminal is used for inquiry only, or for limited data entry, IOAREALEN need not be large.

  2. SDLC 3270s are supported only through z/OS Communications Server. Printers attached to local or SDLC 3274s and SDLC 3276s are supported through z/OS Communications Server either as LU Type 3 using the 3270 printer data stream or as LU Type 1 using the SCS data stream (which is a subset of that used for SDLC 3767, 3770, and 3790 printers). The 3288 is supported as a 3286 Model 2. CICS supports the 3270 copy feature (#1550).
  3. Devices and features supported by a system or programmable controller are generally transparent to CICS. In some cases, CICS provides specific device support, in which case the units are listed.
  4. SDLC is supported through z/OS Communications Server. The 3614 is supported both for loop attachment to the 3601 and SDLC attachment to the host via a 3704/3705 Communications Controller.

    The 3614 is supported by CICS as BSC only when loop-attached to the 3601/3602 Controllers. The 3624 is supported as a 3614.

    The 3690 is supported as a 3602.

  5. CICS supports the Data Transfer Function of the SDLC Programmable Models of the 3770 Data Communication System. In using this function, you are responsible for allocating data sets and managing the program library.
  6. CICS does not support the 3790/Data Entry Configuration using 3760s. The #9165 or #9169 configuration is required to support the CICS enhancement first made available in Version 1 Release 3.0.
    Printers on 3790 systems are supported with one of the following:
    • A function program that you provide
    • 3270 data stream compatibility with a 3270 printer data stream (LU3)
    • An SCS data stream supporting a subset of that for SDLC 3767 (LU1)
    When operating in 3270 mode, the 3288 Model 2 is supported as a 3286 Model 2.
  7. The 4300 attachment by BSC requires a suitable telecommunications program (for example, the VSE/3270 Bisync Pass Through Program) in the system connected to CICS. CICS is not a suitable program for the remote CPU. Attachment by SDLC is supported by CICS intersystem communication.
  8. The System/32 with its SNA/SDLC workstation system utility program, and the System/34 and System/38, are supported as compatible versions of an appropriately featured 3770 Communication System operating as a batch logical unit. The System/34 or System/38 user-written program is responsible for supporting the correct SNA sequences of the attached subsystem.
  9. TWX and WTTY are supported through z/OS Communications Server via the Network Terminal Option program product (5735-XX7), with attachments as defined by NTO.

    WTTY is attached at 50 bps on common-carrier switched networks where the terminals supported are those interfacing through IBM® World Trade Corporation Telegraph Terminal Control with Telegraph Line Adapter.

    The transmission code used is International Telegraph Alphabet No. 2 (CCITT No. 2). CICS does not support autocall or automatic host disconnect via WRITE break.

  10. The 3643 is supported as a 3604.
  11. 8775 support includes validation of mandatory fill and mandatory enter field attributes.
  12. Attachment is via the Loop Adapter #4830, #4831, and Data Link Adapter #4840 of the 4331 processor.
  13. 3270 support requires that the 3278/3279 Emulation Adapter be installed in the Personal Computer or PS/2.
  14. The 3600 pipeline logical unit is designed to provide high throughput for particular types of transaction, such as credit card authorization or general inquiry applications. To achieve a high throughput of inquiry messages and their replies, the CICS pipeline session uses a restricted set of the communication protocols that are used with the 3601 logical unit.

    These restrictions result in a full duplex message flow whereby many inquiry messages are outstanding at any one time, and the replies may flow back in a different order from that of the original inquiries. The 4700/3600 application program controlling the inquiry terminals is responsible for maintaining the protocols as well as correlating replies with inquiries, and controlling message flow to the group of terminals associated with the pipeline logical unit.

    CICS does not support automatic transaction initiation (ATI) on pipeline terminals.