CICS® Transaction Server for z/OS®, Version 3 Release 1 supports terminals directly through interfaces to the following access methods:
CICS supports operating system consoles as terminals too, but through operating system services rather than through an access method. The terminal control interface to a console is the same as to other terminals (though certain consoles might have certain restrictions), but BMS is not available. You can find a full list of the terminals supported by CICS in the CICS Resource Definition Guide.
Earlier releases of CICS also supported terminals through
the ‘DCB’ interface of TCAM. You can still execute transactions under
CICS from terminals using TCAM/DCB. However, the terminals themselves must
be attached to a remote, pre-CICS TS 3.1, terminal-owning region. Local terminals
using TCAM/DCB are not supported. The ACB interface of TCAM is not supported
at all.
A transaction running under CICS communicates with a local surrogate for the remote TCAM terminal, and the two CICS systems manage the correspondence between the surrogate and the real terminal. The transaction is invoked either when the CICS that owns the terminal routes the transaction to the CICS region, or by automatic transaction initiation (ATI) in the CICS region. With ATI, this region arranges assignment of the terminal as principal facility for the transaction through the CICS region that owns the terminal.
[[ Contents Previous Page | Next Page Index ]]