Part 4: Cloning

• Cloning IOA Environments

  • Limitations

  • Before You Begin

  • IOA Environment Cloning Checklist

  • Cloning Steps

  • Post-cloning Procedures

  • Target Environment Parameters

  • Troubleshooting

Cloning IOA Environments

Often customers require more than one IOA environment. The additional IOA environments can be used for testing and debugging purposes, as well as for additional production systems.

Instead of repeating the installation process, you can simply create copies of your base (source) IOA environment, using a cloning process.

IOA provides a toolkit that can be used for efficiently cloning the existing IOA environment on the same MVS system (local cloning) or to another MVS system (remote cloning). Both SMP/E managed and non-SMP/E managed cloned environments can be created with the toolkit.

The cloning process consists of the following major steps:

1. Provide parameters for the cloning process.

   In this step, the user defines the type of cloning process (local or remote) and the characteristics of the cloned environment (such as the cloned environment ID and description, whether the cloned environment is SMP/E managed, whether the user data will be cloned, and whether the allocation attributes of the cloned environment will be defined).

2. Specify parameters for a target cloned environment.

   In this step, the user specifies various parameters of the target cloned environment. These parameters are then validated by ICE. In addition, jobs and definitions are built in preparation for the later cloning steps.

3. Create Cloning Package data set.

   In this step, the Cloning Package is built. The package contains all the data sets of the source base IOA environment that will be copied to the target cloned environment.

4. Create target cloned environment.

   In this step, all data sets from the Cloning Package are restored on the target LPAR with new names for the target cloned IOA environment. The Renaming tool is then executed on the target LPAR, adjusting internals of the target cloned IOA environment according to the new data sets names and parameters. Afterwards, post-cloning steps are performed by the user to achieve a working cloned IOA environment.

For more information, see

• Limitations

• Before You Begin

• IOA Environment Cloning Checklist

• Cloning Steps

• Post-cloning Procedures

• Target Environment Parameters

• Troubleshooting

Limitations

Before performing a cloning procedure, note that the cloning procedure is based on DFDSS. FDR is not supported.

A cloned IOA environment has the following limitations:

• When the CLALLOC cloning parameter is set to N, the allocation of cloned data sets is performed according to the SMS rules on the target system and depends on the new prefixes specified for the data sets.

• The ECAPARMx, IOADSNL, and TCPMAP members are not handled by the cloning process.

A non-SMP/E managed cloned environment has the following additional limitations:

• The MAINTENANCE activity cannot be performed on a cloned environment.

• The SECURITY activity is limited to the customization of the SECPARM member.

• Cloning of a cloned environment is not supported.

Before You Begin

To prepare for the IOA environment cloning

1. Run ICE.

2. Select the "Clone, Deploy IOA Environment" option.

3. Select the "Create Cloned IOA" option.

You are now ready to clone an IOA environment using ICE.

IOA Environment Cloning Checklist

The following list is a summary of the steps required to clone an IOA environment. Detailed step-by-step instructions follow.

• Step 1 – Provide Parameters for Cloning Process

• Step 2 – Specify Parameters for Target Environment

• Step 3 – Create Cloning Package Data Set

• Step 4 – Create LOCAL Target Environment

• Step 5 – Create REMOTE Target Environment

Cloning Steps

Perform the major and minor steps below to clone an IOA environment using ICE.

Step 1 – Provide Parameters for Cloning Process

Review the cloning process considerations, define the type of the cloning process and characteristics of the cloned environment.

Step 1.1 – Process Consideration

Review the cloning process considerations.

Step 1.2 – Provide Cloning Specifications

Define the type of the cloning process and characteristics of the cloned environment:

Step 2 – Specify Parameters for Target Environment

Specify parameters of the target cloned environment and perform validation of the parameters.

Step 2.1 – Specify Parameters for Target Environment

Specify parameters of the target cloned environment. The step consists of the following parameter entry panels:

• Products and Sizes panel

• Short Parameter Data Entry panel

• Long Parameter Data Entry panel

• Allocation Attributes Entry panel

Navigate between the panels using the PF10 and PF11 keys. The Allocation Attributes Entry panel is displayed only if the CLALLOC cloning parameter is set to Y.

For a more powerful Find/Replace action when specifying parameters for the target cloned environment, you can use the CHANGE (or C) command in the command line. This is especially useful when you want to replace a prefix from the source environment with the prefix of the target environment. The CHANGE command is available on all panels in this step except for the Products and Sizes panel. The CHANGE command can be used in two modes:

Command ===>  CHANGE SYS1 SYS2

Command ===>  CHANGE SYS1 SYS2 ALL

For the full list of target environment parameters that can be defined in this step, see Target Environment Parameters.

Step 2.2 – Validate Parameters

Validate parameters of the target cloned environment defined in the previous steps. The step is fully automatic. Review the step output and fix any invalid parameter values in the previous step, if required.

Step 3 – Create Cloning Package Data Set

Build the Cloning Package. The package contains all data sets of the source base IOA environment that will be copied to the target cloned environment.

Step 3.1 – Create Cloning Package Data Set

Select the step to submit the job IOACJPKG that builds the Cloning Package. This job invokes IBM DFDSS utility to pack the relevant files in the IOA source environment into the Cloning Package data set. The name of the Cloning Package data set is defined in the job JCL variable DSN. The default package data set name has the following format: ilprefa.Pmmddsss where: mm = month (from 01 to 12), dd = day of month (from 01 to 31); sss = are the first three digits of the 5-digit number of seconds since 12:00 midnight (from 000 to 863). The maximum return code for successfully running IOACJPKG job is 4.

Step 4 – Create LOCAL Target Environment

In this step, all data sets from the Cloning Package are restored on the target LPAR with new names for the target cloned IOA environment. The Renaming tool is then executed on the target LPAR, adjusting internals of the target cloned IOA environment according to the new data sets names and parameters. Afterwards, post-cloning steps are performed by the user to achieve a working cloned IOA environment.

Step 4.1 – Validate Cloning Type

Perform the step to validate the value of the CLTYPE cloning parameter.

Step 4.2 – Review Local Cloning Steps

Review the local cloning steps that will be performed in the following steps.

Step 4.3 – Restore Cloning Package

Submit the IOACJRSD job that restores cloned environment data sets from the Cloning Package. The data sets will be restored with new names according to the cloning parameters defined in Step 2.1 – Specify Parameters for Target Environment.

Step 4.4 – Run Renaming Tool

Submit the IOACJRND job that invokes the Renaming tool for adjusting the target cloned IOA environment internals according to the new data sets names and cloning parameters defined in Step 2.1 – Specify Parameters for Target Environment.

Step 4.5 – Perform Post-cloning Steps

Perform all post-cloning actions listed in this step. For detailed information see Post-cloning Procedures.

Step 5 – Create REMOTE Target Environment

Follow the minor steps to create REMOTE target environment.

Step 5.1 – Validate Cloning Type

Perform the step for validating the value of the CLTYPE cloning parameter.

Step 5.2 – Review Remote Cloning Steps

To create a REMOTE cloned environment

1. Copy the following items to the target LPAR:

   • The Cloning Package data set created in Step 3.1 – Create Cloning Package Data Set.

   • The IOACJRSD restore job from the INSTWORK library.

   • The IOACDRND restore definitions from the INSTWORK library.

2. Adjust the IOACJRSD restore job on the target LPAR in the following way:

   • Set the value of the PKGDSN JCL variable to the Cloning Packaged data set name on the target LPAR.

   • Set the value of the PKGRND JCL variable to the location of the restore definitions member IOACDRND on the target LPAR.

3. Restore the Cloning Package by submitting the IOACJRSD Restore job on the target LPAR.

4. Run Renaming tool by submitting the IOACJRND job from the INSTWORK library of the restored cloned IOA environment on the target LPAR.

5. To make a working target system, after the successful completion of the Renaming tool with RC0, perform the relevant post cloning steps, described in Post-cloning Procedures, on the target LPAR.

Post-cloning Procedures

This section describes procedures that can only be performed after the cloning procedure is completed. Only perform the post-cloning steps that are relevant to the installed products.

To make a working target system, perform the following post cloning processes:

1. Grant APF authorization to the following libraries:

   • STEPLIB

   • STEPLIBE

   • ilprefa.CTRANS

   To permanently define them as authorized, edit member IEAAPFxx or member PROGxx in SYS1.PARMLIB (where xx is the number specified in the IEASYSxx member in SYS1.PARMLIB). The libraries will become authorized after the next IPL.

   Dynamically define them with the following MVS command:

   Copy

   SETPROG APF,ADD,DSN=DsName,VOLUME=VolSer
                           SETPROG APF,ADD,DSN=IOA.V900.CLONE.CTRANS,VOLUME=CLONEV
                           SETPROG APF,ADD,DSN=IOA.V900.CLONE.LOAD,VOLUME=CLONEV
                       SETPROG APF,ADD,DSN=IOA.V900.CLONE.LOADE,VOLUME=CLONEV

2. Refresh LLA

   If the IOA LOAD library resides in the MVS Linklist, refresh the LLA using the MVS command:

   Copy

   F LLA,REFRESH

   If a program fetch optimization product, such as PDSMAN, QUICKFETCH, PMO, and so on, is in use at your site, you may need to refresh the Linklist tables.

   Log off from TSO/ROSCOE and log on again.

   Perform the following steps from ICE, as indicated in the parenthesis. In each of the steps, when a window is displayed, asking whether you want to replace the existing copy, specify Y.

3. Update defining subsystems to z/OS if IOAPARM member parameter SSALLOC (Allow Dynamic SubSystem Definition) is set to N.

4. Set IOA Online Monitor Parameters (ICE Customization, IOA Product Customization, Step 15.1).

5. Specify IOA CPUs (ICE Customization, Control-O Product Customization, Step 1.4 or Control-M Product Customization, Step 1.17).

6. To set ENABXES=Y and ENABXAE=Y, review and adjust the IOAPLEX parameters (ICE Customization, IOA Product Customization, Step 20.8).

7. If ENABXES=Y and ENABXAE=Y, Build the IOAPLEX member (ICE Customization, IOA Product Customization, Step 20.9).

8. Allocate Global AutoEdit Libraries (ICE Customization, Control-O Product Customization, Step 2.4) - for each SMFID.

9. Allocate and Format Control-O Statistics Files (ICE Customization, Control-O Product Customization, Step 2.5) - for each SMFID.

10. Allocate the Automation Log Files (ICE Customization, Control-O Product Customization, Step 2.6) - for each SMFID.

11. Allocate Subsystem Communication File (ICE Customization, Control-M Product Customization, Step 5.3).

12. Allocate and Format Communication Files (ICE Customization, Control-M Product Customization, Step 5.4) - for each SMFID.

13. If SYSTLOGR=Y, Perform CMEM SYSPLEX Configuration (ICE Customization, Control-M Product Customization, Step 5.5).

14. If SYSTLOGR=Y, Build CMMPLEX Parameter Member (ICE Customization, Control-M Product Customization, Step 5.6).

15. For remote cloning, edit the password members for each of the installed products.

16. Review and adjust the ECAPARMx parameter members (ICE Customization, IOA Product Customization, Step 14.2).

17. Review and adjust the CTMPLEX parameter member (ICE Customization, Control-M Product Customization, Step 3.1).

18. If the base (source) environment has alternative indexes created for the Control-D Active, Migration, and History User files, perform one of the following manual operation, depending on whether you want to use alternative indexes in the cloned environment:

    • If you want to use alternative indexes in the cloned environment, see "Using Alternative Index Components" in the INCONTROL for z/OS Administrator Guide, and perform the process described in "Creating Alternative Index Components".

    • If you do not want to use alternative indexes in the cloned environment, delete the alternative index components described in the DEFALTI member from the ALCCTDJB, ALCCTD, ALCCTVJB, ALCCTV, and ALCDOLV members in the IOA PARM library.

19. Allocate the SYSPROC site library for the TSO users.

20. Review the operational libraries to ensure that there are no references to the base (source) installation.

21. Activate IOA and INCONTROL Product Security (ICE Customization, IOA Security Customization, Step 1.8).

Target Environment Parameters

This section lists the following target environment parameters that can be defined in cloning Step 2.a, “Specify parameters for Target environment”:

• Products and Sizes

• Short Parameter Data Entry

• Long Parameter Data Entry

• Allocation Attributes Entry

Products and Sizes

On this panel, you can change database capacities for each installed product in the target cloned environment.

If you want databases to have the same capacity in the cloned environment as in the source environment, either do not change the initial capacity values that are displayed when you first enter this panel, or set each product to a value of R (reference). The R value is especially useful if the source environment was installed through a Customized Installation, and you want to clone your customized space calculations from the source environment to the target environment.

For more information about capacity settings, as set on a similar panel during an Express installation, see the Express Installation Sheet in Installation Guide Planning Sheets.

The following additional parameters are also available on this panel:

Short Parameter Data Entry

Long Parameter Data Entry

Allocation Attributes Entry

Troubleshooting

The following topics describe common situations that might occur when running the cloning utilities:

• Case 1

• Case 2

• Case 3

• Case 4

• Case 5

Case 1

Symptoms

The IOACJPKG packaging job terminates with MAXCC=4. The following warning message is issued to the SYSPRINT in the RUNDFDSS step:

ADR804W (xxx)-DTDSC(yy), EOF FOR DATA SET DsName IN CATALOG CatName WAS NOT FOUND
WHERE EXPECTED. ALL ALLOCATED SPACE WILL BE PROCESSED.

Diagnosis

The results of a job that terminates with MAXCC=4 are valid.

Solution

Continue the cloning procedure.

Case 2

Symptoms

The IOACJRSD job terminates with MAXCC=8. The following message is issued to the SYSPRINT in the RUNDFDSS step:

ICH408I USER(xxxxxxxx) GROUP(yyyyyyyy)
NAME(zzzzzzzz)  nnn        STGADMIN.ADR.RESTORE.IMPORT
CL(FACILITY)                     INSUFFICIENT ACCESS AUTHORITY
FROM STGADMIN.ADR.* (G) 
ACCESS INTENT(READ)  ACCESS ALLOWED (NONE)

Diagnosis

The user performing the cloning does not have the proper RACF facility class authorization.

Solution

The user must obtain the proper RACF facility class authorization from the RACF administrator.

Case 3

Symptoms

The IOACJRSD job terminates with MAXCC=4. The following warning message is issued to the SYSPRINT in the RUNDFDSS step:

ADR744W (xxx)-MRPAM(yy), NO VALID MEMBERS WERE FOUND FOR PDS DATA SET DsName. ONLY THE 
DIRECTORY WILL BE UPDATED

Diagnosis

The results of a job that terminates with MAXCC=4 are valid.

Solution

Continue the cloning procedure.

Case 4

Symptoms

The IOACJRSD job terminates with RC=8. The following error message is issued to the SYSPRINT in the RUNDFDSS step:

ADR472E (xxx)-NEWDS(yy), UNABLE TO SELECT A TARGET VOLUME FOR DATA SET DsName, nn

Diagnosis

DFDSS failed to restore the DsName data set for the nn reason.

Solution

To correct the problem, do the following:

1. Refer to the z/OS V1R9.0 MVS System Messages, Vol 1 (ABA-AOM) SA22-7631-15 for more information regarding the reason code nn failed.

2. Eliminate the cause of the job failure.

3. Delete all data sets created by the job.

4. Submit the job again.

Case 5

Symptoms

The Renaming tool fails due to a shortage of available free disk space on the target system. The following error message is issued:

IOAI22E Failed to process data set DsName

If the failure was caused by a job, then the following information messages are issued after the IOAI22E message:

IOAI23I RC=JobRc Routine
IOAI23I The job JobName(JobId) failed

Diagnosis

The Renaming tool allocates and formats a number of repository data sets of the INCONTROL products on the target system.

Some jobs that allocate new data sets on a target system can fail because a shortage of available free disk space.

Solution

To correct the problem:

1. Analyze the output of the Renaming tool to ensure that the failure was caused by a shortage of available free disk space.

2. Estimate the amount of the free disk space required by analyzing the size of the data sets of the base environment. (The Renaming tool allocates data sets using the size definitions of the base environment.)

3. Free the required amount of disk space on the target system.

4. Delete all the cloned data sets from the target environment.

5. Invoke the Cloning process again from one of the following steps, depending on the selected cloning type; “Create LOCAL target environment” or “Create REMOTE target environment”.