Overview of Managing Host Access IDs

Management & Control Services (MCS) provides IDs to client applications at runtime. An ID is connection data that is unique for an individual session with a host. If you use MCS to manage IDs, you can omit unique connection data from the client session configuration. This lets you create a single configuration that can be used by multiple clients to establish multiple sessions with a host, rather than having to create a separate configuration for each host connection.

To use this feature of MCS:

The feature must be supported by the client (viewer, printer applet, or custom application).
Depending on your host type, the IDs may need to map to existing IDs on the host.
You must set up your directory service in MCS before you can create pools based on your directory service or user names.

When a user starts a client, the client gets an ID from MCS and uses the ID to connect to the host. MCS keeps track of (monitors) the IDs that are in use. If all the IDs assigned to a pool are in use, no other host sessions can be opened through that pool.

If you're using SNA Gateway, whether or not an ID obtained from MCS is actually used depends on how the gateway is configured. For more information, refer to the documentation for that product.

In client applications that support it, you can implement ID management by performing the following basic steps:


Decide how you want to manage the IDs, and create pools of IDs. In previous versions of MCS, these pools were called names. For example, you might want to assign specific IDs to specific users, or you might want to assign a large number of IDs to a named pool that any user can access on a first-come, first-served basis. Assign IDs to the pools you've created. Once you have defined a pool, you can assign IDs to it, and each ID can have its own properties. For example, a T27 station ID can be flagged for use with a terminal emulation session, a printer session, or a gateway connection. Create a configuration or application that obtains its ID from MCS. Alternatively, you can create your configurations first, and then assign IDs to pools. However, you cannot use the configuration to establish a host connection until you have assigned IDs to pools. Monitor your pools.

Decide how you want to manage the IDs, and create pools of IDs. In previous versions of MCS, these pools were called names.
For example, you might want to assign specific IDs to specific users, or you might want to assign a large number of IDs to a named pool that any user can access on a first-come, first-served basis.
Assign IDs to the pools you've created.
Once you have defined a pool, you can assign IDs to it, and each ID can have its own properties. For example, a T27 station ID can be flagged for use with a terminal emulation session, a printer session, or a gateway connection.
Create a configuration or application that obtains its ID from MCS.
Alternatively, you can create your configurations first, and then assign IDs to pools. However, you cannot use the configuration to establish a host connection until you have assigned IDs to pools.
Monitor your pools.


	Configuring ID Pools
	Logging ID Management Events
	Reclaiming IDs