Terminal aliases

The name by which a terminal is known in the application-owning region is usually the same as its name in the terminal-owning region. You can, however, choose to call the remote terminal by a different name (an alias) in the application-owning region.

You have to provide an alias if the terminal-owning region and the application-owning region each own a terminal with the same name; you cannot have a local terminal definition and a remote terminal definition with the same name. (Nor can you have two remote terminal definitions (for terminals on different remote regions) with the same name.)

If you use an alias, you must also specify the “real” name of the terminal as its remote name, as follows:
Figure 1. Local and remote names for remote terminals
The picture shows a terminal-owning region and an application-owning region. The TOR owns a terminal named L77A, and has a local definition of it, with TRMIDNT=L77A. The AOR also owns a terminal named L77A, and has a local definition of it, with TRMIDNT=L77A. The AOR also has a remote definition of terminal L77A owned by the TOR. The remote definition specifies a TRMIDNT of R77A and a REMOTENAME of L77A.

You specify the remote name in the REMOTENAME attribute of the TERMINAL resource.



dfht173.html | Timestamp icon Last updated: Sunday, 4 June 2017