How users start a full-screen mode debug session with the Terminal Interface Manager

The following steps describe how a user would start a full-screen mode debugging session for a batch job with the Terminal Interface Manager. Study these steps to understand how z/OS® Debugger uses the Terminal Interface Manager to display a full-screen mode debugging session and to understand why you need to do the configuration steps described in Enabling full-screen mode using the Terminal Interface Manager.

Start two terminal sessions. These sessions can be either of the following situations:
- Two separate terminal emulator sessions.
- If you use a session manager, two sessions selected from the session manager menu.
In either situation, ensure that the second session connects to the Terminal Interface Manager.
On the first terminal session, log on to TSO.
On the second terminal session, provide your login credentials to the Terminal Interface Manager and press Enter. The login credentials can be your TSO user ID and password, PassTicket, password phrase, or MFA token.
Notes:
1. You are not logging on TSO. You are indicating that you want your user ID associated with this terminal LU.
2. When the number of characters entered into the password field, including blanks, exceeds 8, the input is passed to the security system as a password phrase.
3. To use PassTickets with Terminal Interface Manager, define the PTKTDATA profile by following the rules for MVS batch jobs. For more information, see Defining profiles in the PTKTDATA class in the z/OS documentation.
A panel similar to the following panel is then displayed on the second terminal session:
```
                     z/OS Debugger Terminal Interface
Manager

EQAY001I Terminal TRMLU001 connected for user USER1
EQAY001I Ready for z/OS Debugger



















               PF3=EXIT  PF10=Edit LE options data set  PF12=LOGOFF                              
```
The terminal is now ready to receive a full-screen mode debugging session.
Edit the PARM string of your batch job so that you specify the TEST runtime parameter as follows:
```
TEST(,,,VTAM%userid:*)
```
Submit the batch job. The following tasks are done:
1. z/OS Debugger allocates a VTAM® ACB (EQAMVnnn) for its end of a VTAM session.
2. z/OS Debugger communicates with the Terminal Interface Manager to request a session with the terminal LU on which it is running.
3. The Terminal Interface Manager releases the terminal LU and passes control of it to z/OS Debugger.
On the second terminal session, a full-screen mode debugging session is displayed. Interact with it the same way you would with any other full-screen mode debugging session.
After you exit z/OS Debugger, the second terminal session displays the panel and messages you saw in step 3. This indicates that z/OS Debugger can use this session again. (This happens each time you exit z/OS Debugger.)
If you want to start another debugging session, return to step 5. If you are finished debugging, you can do one of the following tasks:
- Close the second terminal session.
- Exit the Terminal Interface Manager by choosing one of the following options:
  - Press PF12 to display the Terminal Interface Manager logon panel. You can log in with the same ID or a different user ID.
  - Press PF3 to exit the Terminal Interface Manager.

This technique requires you to define and configure a number of items in the z/OS Communications Server. Section Enabling full-screen mode using the Terminal Interface Manager describes these definitions and configuration.