How can a physical terminal id be passed to an application using TPX?

Products

• TPX - Session Management

Issue/Introduction

Pass a physical terminal id to an application in TPX.

Environment

Release:  5.4
Component: TPX for Z/OS

Resolution

Use one of four possible methods to meet this requirement:

1. 1. Pass the original VTAM network name to an application session by using the symbolic &NETNAME specified in the
      SessionData field (profile-level or user-level session detail) or by using a session signon ACL/E.
      
      Note: Information can be passed using the SessionData field only if the application will accept that information from the
      DATA parameter of the un-formatted system services (USS) table.
      
      
   2. Implement a terminal-masking rule (in a virtual terminal masking rule table) for the application (defined in the ACT table with
      the mask rule name) that will "map" a physical terminal ID to a virtual terminal ID where only one character is different.
      
      For example: Set up a rule that will map all physical terminals to a virtual terminal mask that changes only the first position of the terminal ID,
      but retains the remaining positions (physical terminal ID A55U0109 would "map" to Z55U0109), or some variation of this mapping logic.
      The application, however, will need to know that the Zxxxxxxx virtual terminals are derived from Axxxxxxx physical terminals.
      
      
   3. OEM Terminal-ID Query allows to incorporate code, as part of your application, that utilizes a special data stream sent from the application.
      TPX intercepts this data stream and responds with a data stream that contains the LUNAME of the physical terminal; no data is actually
      transmitted to or from the terminal. The CB0VSRC library contains two samples: CICS#OEM and TSO#OEM.
      
      
   4. Set up the application session to be a PASS session (PASS = Y in profile-level or user-level session definition) so that when a user selects
      the session, CA TPX "passes" the physical terminal to the session. The application communicates directly with the physical terminal as if
      a session manager is not in use.
      While in PASS mode, TPX function, such as toggling between sessions, is unavailable.
      When the pass mode application session is terminated, TPX regains control of the physical terminal.