Migration Considerations › Clone a ReportCenter Control Region

Clone a ReportCenter Control Region

Note: This topic is not about migration between different versions of ReportCenter, but some of the steps are similar to migration.

Sometimes, you want to clone a working ReportCenter environment to create an additional separate environment (but using the same installed version of ReportCenter).

Usually, cloning is required in large sites, for example:

• To move ReportCenter from a testing environment into a production environment
• To set up two production ReportCenter control regions to handle many data regions

The following procedure describes a general approach to clone a ReportCenter environment to another z/OS system (LPAR). The exact technical procedure, what utilities to use, and so on, depends on your own specific processes, tools, and shared DASD environment.

This procedure assumes the following scenario:

• You have installed and implemented a Release 12.1 ReportCenter environment on system SYS1, consisting of ReportCenter control region NM01 and Java Task NMJAVA01.
• You want to deploy an identical ReportCenter environment on system SYS2.
• You already have an Release 12.1 NetMaster region (NM02) implemented on SYS2

Follow these steps:

Note: With CA MSM, you can use the Software Deployment Service to perform some of these steps.

1. Allocate new HFS directories on SYS2 for holding copies of the supplied HFS product code. These directories have the …/nm/reporter/wr76/… paths.

   If you installed with:

   • ESD or Tape, modify and rerun the I21* job that the Install Utility generates, which allocated the original SMP/E HFS Target Libraries on SYS1.
   • CA MSM, define the paths as listed in the file /yourpath/C2DMKDR, which allocated the original SMP/E HFS Target Libraries on SYS1.
2. Copy the HFS files from the existing SYS1 SMP/E HFS Target Library directories to the equivalent SYS2 directories.

   You do not have to reallocate the user directories, …/nm/reporter/usr/…, on or copy them to SYS2; they always start empty.

   These user directories are allocated when you apply the REPORTCENTER Customizer parameter group for the first time in NM02. They eventually contain the reports, logs, and stderr and stdout files, from the new Java task NMJAVA02.

3. Edit the IIAPARMS member that is associated with the region NM02 on SYS2, in data set dsnpref.PARMLIB.

   Copy the contents of that member from the existing equivalent data set on SYS1, and change the directory name if necessary.

   This member tells the ReportCenter control region where the supplied HFS code is, for example:

   BROWSE    DSNPREF.PARMLIB(IIAPARMS) - 01.08    
   Command ===>                                       
   ********************************* Top of Data *******
   WRHFS1='/u/users/netmgmt/reporter/nmjava01'            
   ******************************** Bottom of Data *****
   

4. Ensure that the new region NM02 on SYS2 specifies PROD=REPORTER at startup. The Install Utility sets it up that way; otherwise, add it.

   Perform a REPTEST on the new NM02 region before proceeding. Verify that the result says that it is a Dormant Control Region.

5. Enter /PARMS and then update and action the REPORTCENTER Customizer parameter group on the new NM02 region.

   Note: If you see only the REPORTDATA Customizer parameter group, this region was not started with PROD=REPORTER. Go back to the previous step.

   Ensure that the REPORTCENTER Customizer parameter group actions without errors.

   Look at the initialization log for the creation of the usr directories.

6. Follow the steps in previous topics of this guide for the following tasks:
   • Set up a new empty ReportCenter database on SYS2.
   • Set up the NMJAVA02 ReportCenter Java Task on SYS2.