Terminal connects to an AOR that runs an application that does not use a terminal
In this scenario, your terminal (TRMC) connects to an AOR, which you use to set up a debugging profile using DTCN. When the application starts, z/OS® Debugger is started and issues and EXEC CICS® START of its display transaction (CDT#) on your terminal (TRMC). Your terminal must be connected directly to the AOR. You cannot connect through CRTE because CICS does not support issuing an EXEC CICS START to a terminal connected through CRTE.
.---------------.
| 3270 terminal |
| |
| TRMC |
'------,--------'
|
|
.-----------------------------------+-----------------------------—-.
| AOR | |
| '---------------------, |
| | |
| ,---------------------------------------------, ,------, |
| | Application runs, then z/OS Debugger issues }-----{ CDT# | |
| | EXEC CICS START TRANS(CDT#) TERM(TRMC) | '------' |
| '---------------------------------------------' |
| |
'-------------------------------------------------------------------'
|
|
.-------'-----------.
| Debugging profile |
| repository |
'-------------------'
For this scenario to work, the CICS system administrator must complete the following tasks for the AOR:
- Define z/OS Debugger resources in the CICS CSD and install them in the CICS region, as described in Adding support for debugging under CICS, step 1.
- Provide access to these resources, as described in Adding support for debugging under CICS, step 2.a.