Example: a debugging session using the z/OS Debugger Terminal Interface Manager

Compare the following steps with the steps shown in How z/OS Debugger uses full-screen mode using a dedicated terminal to understand how using the Terminal Interface Manager affects the flow of work.

Start two terminal emulator sessions. These sessions can be either of the following situations:
- Two separate terminal emulator sessions.
- If you use IBM® Session Manager, two sessions selected from the IBM Session Manager menu.
In either situation, ensure that the second session connects to a terminal that can handle a full-screen mode debugging session through a dedicated terminal and that starts z/OS® Debugger Terminal Interface Manager.
On the first terminal emulator session, log on to TSO.
On the second terminal emulator 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 emulator 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 z/OS Debugger full-screen mode using a dedicated terminal 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 tasks completed are similar to the tasks described in step 5 except that first the batch job communicates with the Terminal Interface Manager to correlate the user ID to the terminal LU of the second terminal emulator session. The remaining steps are the same as described in step 5.
On the second terminal emulator 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 emulator session displays the panel and messages you saw in step 3. This indicates that z/OS Debugger can use this session again. (this will happen each time you exit from 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 emulator 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.