CICS® Transaction Server for z/OS®, Version 3 Release 1 does
not support the TCAM/ACB interface. It supports the TCAM/DCB interface indirectly.
For several CICS releases,
the ACB interface of TCAM has been supported only indirectly: that is, by
transaction routing from a back-level terminal-owning region (TOR) to which
the terminals were attached. In CICS TS for z/OS, Version 3.1,
this indirect support is removed.
In previous CICS releases,
the DCB interface of TCAM has been fully supported. That is:
- TCAM/DCB could be used to connect terminals to a current-level CICS TOR.
- Transactions started by TCAM/DCB-connected terminals could be routed to
a current-level CICS AOR.
In
CICS TS for z/OS, Version 3.1,
only the second operation is supported.
As a result of these changes:
- If you have a network of terminals connected by the ACB interface of TCAM
to a back-level CICS TOR,
you will not be able (as you were in previous CICS releases) to route transactions from
them to a CICS TS for z/OS, Version 3.1 AOR.
You must migrate your connections to use TCAM/DCB or (preferably) ACF/VTAM,
or route to a previous version of CICS. (All terminals that support TCAM/ACB
also support ACF/VTAM.)
- If you have a network of terminals connected by the DCB interface of TCAM
to, for example, a CICS TS 2.3 TOR, you will not be able to migrate the
TOR to CICS TS for z/OS, Version 3.1.
To do so, you must migrate your connections to use ACF/VTAM.
- If you have a network of terminals connected by the DCB interface of TCAM
to a back-level CICS TOR,
you will (as in previous CICS releases) be able to route transactions from them
to a CICS TS for z/OS, Version 3.1 AOR.
However, you are recommended to migrate your connections to use ACF/VTAM.