Cloning a CICS region started by a batch job

When you clone a CICS® region that is started by a batch job, CICS DA creates the new CICS region and a new batch job to start the region.

Before you begin

Ensure that the CICS region you want to clone is running and that the region start policy has been recorded in the model. See Capturing the region start policy topic for more information about recording the start policy.

Procedure

  1. In the DA Projects view, double-click the CICS region you want to clone, or right-click and click Open. The CICS region editor opens showing the details of the selected region.
  2. In the CICSPlex® System Management section click New CICS Region Wizard. The Create a CICS Region dialog opens. The fields in the dialog show the details for the original CICS region. You must provide values for the new CICS region.
  3. Complete the fields to provide unique attributes and start policy for the new CICS region.
    A screen capture of the Create a CICS Region dialog showing the new region details.
    Click Next.
    CICS DA identifies all the data sets in the original CICS region and attempts to identify any naming convention you use. This information is used to propose new data set names for the new region.
  4. The dialog is updated to show the data sets used by the original CICS region, the proposed name for the new CICS and CICSPlex SM data sets that CICS DA will create, and the share status of the data sets.
    A screen capture showing the original data set names and the proposed new ones.
    You can choose to keep the proposed data set names or overtype them in the dialog. You can choose to share some data sets between the two regions by selecting the Share check box:
    • If the new data set name is grayed out and the Share check box is selected but is also grayed out, the data set must be shared.
    • If the new data set name is grayed out and the Share check box is selected but available, it is suggested that the data set should be shared. However you can choose to clear the check box and not share the data set.
    • If the new data set name and the Share check box are both available, then you can do nothing and accept the proposed name, share the data set, or change the data set name.
    • If the Share check box is not available, then you cannot share the data set, but you can change the data set name.
    Click Finish to confirm your choices and create the new data sets.

Results

The data sets are allocated, and where necessary initialized, and the batch job created. If the allocate fails a red triangle is shown next to the failing data set in the view. You must review the job output to determine the cause of the failure and retry the operation.

If the allocate is successful, CICS DA then adds the new region to your CICSPlex SM definitions and to the system model. Finally, the CICS region editor opens showing details of the CICS region, and a report is shown in the Console view.

What to do next

At this point you might be able to click the Start Region link in the region editor and start the CICS region, however there are some actions that CICS DA is unable to perform, such as defining the region to your security policy, and some connectivity steps. When CICS DA has completed all that it can do, a report is posted to the Console view. The report identifies the setup that has been done, and the further steps that you must take. The report provides the following information:

  • An indication that the job completed successfully showing the original and new region name
  • A list of the data sets that were allocated and are ready to use
  • A list of the data sets that were allocated but require some further initialization before they can be used
  • A list of the data sets that were not allocated and must be added manually if required. These are typically private data sets
  • An indication as to which CICSplex the new region was added
  • An indication as to which CICSPlex SM groups the new region was added
  • The job name for the new region's JCL
  • The member name and qualifiers for the new region's JCL
  • A list of the SIT overrides that were updated in the new JCL
  • A list of the EYUPARM values that were updated in the new JCL
  • A list of SIT overrides that must be update manually
  • A list of the EYUPARM values that must be updated manually
  • A list of other setup tasks you might consider performing for the new region. Examples are security definitions, CICS profile, task tables, VTAM® applid, and so on
Figure 1. An example CICS region clone report
Cloning of CICS region IYK2ZGV1 to create CICS region IYK2ZXX1 completed successfully.

The following data sets were allocated and are ready to be used by the new CICS region:
JT1.IYK2ZXX1.DFHDUMPA
JT1.IYK2ZXX1.DFHDUMPB
JT1.IYK2ZXX1.DFHGCD
JT1.IYK2ZXX1.DFHLCD
JT1.IYK2ZXX1.DFHTRACB
JT1.IYK2ZXX1.DFHTRACA
JT1.IYK2ZXX1.DFHINTRA
JT1.IYK2ZXX1.DFHTEMP

The following data sets were allocated, but require initialization to be used by the new CICS region:
None.

The following data sets used by the original data set were NOT allocated and may require attention:
PP.TCPIP.ZOS111.PARMS(TDATA2C)
JT1.IYK2ZGV1.DFHWBCD
CPSMDEV.JT1.JVMVARS

The new CICS region was added to CICSplex: 
JTPLEX2

The new CICS region was added to the following CICSPlex SM groups:
GROUP1

New JCL was created for the new CICS region.
The jobname for the new CICS region's JCL is:
LMASJT1B

The new CICS region's JCL was created in:
JT1.OMEG.JCL(LMAS99V)

The following SIT overrides were updated in the new JCL:
APPLID=IYK2ZXX1
SYSIDNT=XX1A

The following EYUPARM values were updated in the new JCL:
NAME(IYK2ZXX1)

The following SIT overrides still need to be applied for the new CICS region:
None.

The following EYUPARM values still need to be applied for the new CICS region:
None.

The following list includes some other areas of consideration for the new CICS region:
Security manager: Definitions for CICS profiles, updating started task tables etc.
z/OS WLM definitions
CICS CSD Changes
BAS definition changes
z/OS logstreams
VTAM applid
TCP/IP port number assignment and usage
Updates to automation
Impact on associated products, e.g. WebSphere MQ, IMS and DB2, due to increased workload