Non-autoinstalled terminals and connections

Because members of a generic resource should be functionally equivalent, it is not recommended that you should predefine terminals to specific members of a generic resource.

Important:

Use autoinstall instead, and allow the z/OS® Communications Server to balance the TORs' workload dynamically. However, there may be times—for example, while you are migrating an existing TOR into a generic resource—when it is necessary to use static definitions.

If an LU is predefined to a specific terminal-owning region, and the LU initiates the connection (that is, it sends the first bind request) using the TOR's generic resource name, the generic resource function must make the connection to the “correct” terminal-owning region—the one that has the definition. This requirement means that you must install the Communications Server generic resource resolution exit program, ISTEXCGR, to enforce selection of the correct applid (for the terminal-owning region).

Note that this is not necessary if the connection is always initiated by the terminal-owning region (by means, for example, of a START request).

A sample ISTEXCGR exit program is supplied with the z/OS Communications Server 4.2. For details, see the z/OS Communications Server: SNA Programming manual.



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