If I have an application that needs to know my physical terminal id, how can I accomplish this using CA TPX Session Management?

Document ID : KB000028195
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

If I have an application that needs to know my physical terminal id, how can I accomplish this using CA TPX Session Management?

 

Answer:

You can use one of four possible methods to meet this requirement:

  1. You can 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: You can pass information using the SessionData field only if the application will accept that information from the DATA parameter of the unformatted system services (USS) table.

  2. You can 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: You can 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 you to incorporate code, as part of your application, that utilizes a special data stream sent from the application. CA 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. You can 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 for the application session, CA TPX functions (such as toggling between sessions) are unavailable. When the application session is terminated, CA TPX regains control of the physical terminal.