Example: Defining the VTAM EQAMVnnn and Terminal Interface Manager APPL definition statements when z/OS Debugger runs on four LPARs

The instructions in Enabling debugging in full-screen mode using the Terminal Interface Manager assume that you create all the definitions and start the Terminal Interface Manager on one LPAR. This example describes the connections that need to be made in a VTAM® network that has four LPARs that run z/OS® Debugger jobs with one of the LPARs managing the terminals.

• LPAR 1 runs a TN3270E server and the Terminal Interface Manager with the default ACB name. Its VTAM also owns all the terminal LUs. Users connect their TN3270E emulator to this LPAR for the Terminal Interface Manager session. Users use the Terminal Interface Manager to create the connection between z/OS Debugger and the terminal LU used for their full-screen mode using the Terminal Interface Manager debugging session.
• VTAM on LPAR 1 defines the terminal LU APPL definition statements and the EQASESSM APPL definition statement for the Terminal Interface Manager.
• VTAM on LPAR 1 needs visibility to the EQAMVnnn APPL definition statements on LPARs 2, 3 and 4. This enables communication between the Terminal Interface Manager and z/OS Debugger.
• Each VTAM on LPAR 1, 2, 3 and 4 has a unique set of EQAMVnnn APPL definition statements. For example, LPAR 1 has APPL definition statements 001-050, LPAR 2 has APPL definition statements 051-100, LPAR 3 has APPL definition statements 101-150, and LPAR 4 has APPL definition statements 151-200.
• Each VTAM on LPAR 2, 3 and 4 needs visibility to the EQASESSM APPL definition statement on LPAR 1. This enables communication between z/OS Debugger and the Terminal Interface Manager.
• Each VTAM on LPAR 2, 3 and 4 needs visibility to the terminal LU APPL definition statements on LPAR 1.