To generate z/OS® Communications
Server generic resource support for your CICS® TORs, you must perform these steps.
About this task
If your CICSplex comprises separate terminal-owning regions
and application-owning regions, do not include TORs and AORs in the
same generic resource group.
Procedure
- Use the GRNAME system
initialization parameter to define the generic resource name under
which CICS is to register to z/OS Communications Server. To
comply with the CICS naming
conventions, pad the name to the permitted 8 characters with one of
the characters #, @, or $.
For example:
GRNAME=CICSH###
If
you specify a valid generic resource name on GRNAME,
specify only name1 on the APPLID system
initialization parameter. If you do specify both name1 and name2 on
the APPLID parameter, CICS ignores name1 and uses name2 as
the z/OS Communications Server
APPLID.
- Use an APPL statement to define the attributes of each
participating TOR to z/OS Communications
Server.
The attributes defined on each individual APPL
statement should be identical. The name on each APPL statement must
be unique. It identifies the TOR individually, within the generic
resource group.
- Shut down each terminal-owning region normally before registering
it as a member of the generic resource.
An immediate shutdown
is
not sufficient; nor is a CICS failure
followed by a cold start. Do not specify a shutdown assist transaction,
to avoid the possibility of the transaction force closing z/OS Communications Server or performing
an immediate shutdown. The default shutdown assist transaction, DFHCESD,
is described in
Shutdown assist program (DFHCESD).
If CICS has not been shut down
cleanly before you try to register it as a member of a generic resource, z/OS Communications Server might
(due to the existence of persistent sessions) fail to register it,
and issue a return code-feedback (RTNCD-FDB2) of X'14', X'86'.
To correct this, you must restart CICS (with
the same APPLID), and then shut it down cleanly. Alternatively, if
you have written a batch program to end affinities (see Writing a batch program to end affinities), you might be able to use it
to achieve the same effect. As part of its processing, the batch program
opens the original z/OS Communications
Server ACB with the original APPLID, unbinds any persisting sessions,
and closes the ACB.