Migrating a TOR to a generic resource

This section describes how to manage existing terminals and connections when migrating a TOR to membership of a CICS® Transaction Server for z/OS® generic resource. How to establish connections between two CICS TS z/OS generic resources is described separately in Setting up inter-sysplex communications between generic resources.

Note:
For the purposes of this discussion, a "terminal-owning region" is any CICS region that owns terminals and is a candidate to be a member of the generic resource.

Recommended methods

In general, we advise that:

There are two recommended methods for migrating a TOR to a generic resource. Which you use depends on whether there are existing LU6 connections.

No LU6 connections

If there are no LU6 (that is, APPC or LU6.1) connections to your terminal-owning region, we recommend that you choose a new name for the generic resource and retain your old applid. Non-LU6 terminals can log on by either applid or generic resource name, hence they are not affected by the introduction of the generic resource name. You can then gradually migrate the terminals to using the generic resource name. Later, you can expand the generic resource by cloning the first member-TOR.

Note:
If you have several existing TORs that are functionally similar, rather than cloning the first member you might choose to expand the generic resource by adding these existing regions, using their applids as member-names.

LU6 connections

If there are LU6 (APPC or LU6.1) connections to your terminal-owning region12 , 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. 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:

  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:

Related tasks
Planning your CICSplex to use VTAM generic resources
Defining connections in a generic resource environment
Generating VTAM generic resource support
Removing a TOR from a generic resource
Moving a TOR to a different generic resource
Setting up inter-sysplex communications between generic resources
Ending affinities
Using ATI with generic resources
Using the ISSUE PASS command
Dealing with special cases
Related reference
Prerequisites for VTAM generic resources
Rules checklist

12.
Not counting connections to other members of the generic resource.

[[ Contents Previous Page | Next Page Index ]]