Inspect Manual

Debugging PATHWAY Applications

Inspect Manual—429164-006

5-3

Application, Command, and Home Terminals

Application terminals are terminals where users interact with PATHWAY applications.

TCPs manage these terminals and PATHWAY requesters (that is, a TCP executing a

requester program) control them. Sometimes they are called PATHWAY terminals.

Command terminals are terminals where system managers, developers, and

programmers interact with system-level utility programs. There are two command

terminals involved in PATHWAY application debugging: the PATHCOM command

terminal and the Inspect command terminal.

Home terminals are terminals where a process is started. Each process has a home

terminal; if a process is started by another process (instead of from a terminal), it

inherits the home terminal of its creator. Inspect uses home terminals to determine

which terminal it should use as its command terminal.

Debugging PATHWAY Requester Programs

This subsection applies to TNS/R systems, and in some cases to TNS/E systems.

Pathway requestors on TNS/E systems (also known as ServerclassSend) can be TNS,

TNS/E, or Java, and must be debugged with the appropriate tool. Screen COBOL

requestors, however, must be debugged using Inspect. For more information about

debugging TNS code accelerated on TNS/E systems, see the TNSVU Manual and the

Object Code Accelerator (OCA) Manual.

Figure 5-2 on page 5-4 highlights the components of Inspect and the PATHWAY

system used when debugging requester programs.