LU6 connections

If there are LU6 (APPC or LU6.1) connections to your terminal-owning region, not counting connections to other members of the generic resource, we recommend that they log on using the generic resource name. However, you will probably want to migrate to generic resource without requiring all your LU6 network partners to change their logon procedures.

About this task

One option is to use the applid of your existing terminal-owning region as the new generic resource name. Because this requires you to choose a new applid, it is also necessary to change the CONNECTION definitions of MRO-connected application-owning regions and RACF® profiles that specify the old applid. Note, however, that you do not need to change the APPL profile to which the users are authorized—CICS passes the GRNAME to RACF as the APPL name during signon validation, and the old applid is now the GRNAME. The recommended migration steps are:
  1. Configure your CICSplex with a single terminal-owning region.
  2. Set the generic resource name to be the current applid of that terminal-owning region.
  3. Change the current applid to a new value.
  4. Change CONNECTION definitions in MRO partners to use the new applid for the terminal-owning region.
  5. Change RACF profiles that specify the old applid.
  6. Restart the CICSplex.
    At this point:
    • Non-LU6 terminals can log on using the old name (without being aware that they are now using a z/OS® Communications Server generic resource). They will, of course, be connected to the same TOR as before because there is only one in the generic resource set.
    • LU6 connections log on using the old name (thereby conforming to the recommendation that they should connect by generic resource name).
  7. Install new cloned terminal-owning regions with the same generic resource name and the same connectivity to the set of AORs.
    At this point:
    • Autoinstalled non-LU6 terminals start to exploit session balancing.
    • Autoinstalled APPC sync level 1 connections start to exploit session balancing.
    • Because of affinities, existing LU6.1 and APPC sync level 2 connections continue to be connected to the original terminal-owning region (by generic resource name).
    • Special considerations apply to non-autoinstalled terminals and connections, and to LU6 connections used for outbound requests. These are described in Dealing with special cases.


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