An ID is connection data that must be unique to each session with a host. The type of connection data provided by ID Manager varies with each type of host:
|Unisys ClearPath LX/NX or A Series||Station ID|
|Unisys ClearPath IX or 2200 Series (INT1)||Terminal ID|
|Unisys ClearPath IX or 2200 Series (MATIP)||Station ID (SID)|
|IBM Mainframe||3270E logical unit (LU)|
|IBM AS/400||5250E logical unit (LU)|
|Apollo Galileo Airline Reservation System||Client ID|
|EDS SHARES, AMADEUS, System One, or Sabre Airline Reservation System||LNIATA|
|IBM TPF (MATIP)||Terminal address (TA)|
Each ID has its own unique properties, such as whether it should be used for terminal emulation or host printer emulation. In addition, each ID can be limited to use with a particular host, or used with multiple hosts. UTS terminal IDs can also be limited to specific ClearPath IX or 2200 Series host applications.
For example, you can assign T101 to Alice for use with both a ClearPath NX and ClearPath IX host. You can also assign T101 to Alice for use with both Demand and MAPPER on the same ClearPath IX host, and all viewer windows can be open simultaneously. However, the UTS terminal ID must be restricted to use with the specified host applications; you cannot do this if Grant Access To Any Application is selected in the ID properties.
|Do not assign IDs for both T27 and UTS sessions to the same name if the IDs are configured for use with e-Vantage Gateway. If you do, the T27 station IDs might be allocated to UTS sessions, and vice versa.|
You can assign the same ID to two different names only if they're being used for two different hosts. For example, you can assign T101 to Alice for use with a T27 session, and to Bob for use with a UTS session. However, if you assign T101 to both Alice and Bob for use with a T27 session, connection errors will occur if both Alice and Bob try to open a T27 session simultaneously (unless each ID is restricted to a different host name alias).
You can also group IDs into sets to ensure that certain IDs are always used together (for example, to ensure that a certain terminal emulation ID is always used with a certain host printer emulation ID).
|Overview of ID Manager|
|Overview of Names|
|Overview of Host Name Aliases|
|Overview of ID Sets|
|Assigning IDs to Names|