1. Enter the name of the deployment package data set where it can be accessed from the cloned site. Although, the original name was indicated in the deployment packaging job (see Step 6 in Building the change deployment package), the name might have changed, for example, if the package was copied to the cloned site.
2. Define the working mode for running the deployment process.

   Valid values:

   • PROD - The process runs in production mode, extracting and applying the maintenance package.
   • TEST - The process runs in simulation mode, extracting the data sets from the change deployment package, performing analysis (includes space requirements) and reporting, but without changing or deleting any datasets. So the cloned environment will not be affected.

     As part of this process, the list of elements to be deployed are displayed on the screen and duplicated to the ICELOG.

3. Define the allocation attributes to be used when data sets are restored.

   You can use the NULLSTORCLAS and NULLMGMTCLAS keywords to pass null storage and management classes to the ACS routines by defining Y(yes) values in the appropriate fields.

   If you do not want extracted data sets to be SMS-managed, specify the BYPASSACS and NULLSTORCLAS keywords.

   See the DFSMSdss Manuals for more detailed information.

At this stage, the process performs the following steps:

1. Extracts the data sets from the change deployment package, using a DFDSS job, to temporary data sets in the cloned environment with prefix mlprefa.Emmddsss (where: mm = month, dd = day of month, sss =seconds). After the job has completed, the DFDSS input string used for the extract, can be found in ilprefa.INSTWORK(IOAFDEXT).
2. Checks if this cloning was from the same base environment.
3. Compares the CSI PTFs of the extracted and cloned environments, to ensure which elements are to be copied to the cloned environment. The sequential files of the base ilprefa.CSITZN and the cloned ilprefa.CSITZN are compared. These sequential files are created on the base and clone systems especially for CSI levels comparison. As result, the IOAFMML member is created in the INSTWORK library.
4. Checks the cloned environment to ensure that it contains sufficient free space to install the maintenance upgrade.

Note: Only the Installation libraries are affected by the change deployment process. The space requirements for the maintainable data sets in the cloned environment are identical to their requirements in the base environment.

Collect all the required information about the Pre- and Post- action lists, User exits, User mode. Displays all the collected information in a window, with confirmation to continue the process of deploying the changes.

This information is divided into the following groups:

• items that must be handled before the deployment process to continue the deployment process.
• items that require reviewing and planning, but must be handled on Step 3 – List post Deploy changes activities.

• Type CONFIRM to acknowledge your awareness of all the required preinstallation and postinstallation activities and to continue with deployment process, described in the next step (6).
• Enter CANCEL. The extracted (temporary) data sets are removed from the cloned site. The cloned environment is automatically restored to its original state. The deployment process ends and can be run again.

1. Backs up the cloned environment, before continuing with the deployment process. The name of the backup dataset is displayed. After the backup job has completed, the DFDSS input string used for the backup, can be found in ilprefa.INSTWORK(IOACDBKP).
2. Automatically submits a job that uses IEBCOPY to copy elements from the single extracted (temporary) library to an appropriate cloned data set. The job will be submitted for each library according to the list in the IOAFMML member from the INSTWORK library.

Do one of the following, depending how the process terminates:

• If the deployment completes successfully, continue with on Step 3 – List post Deploy changes activities.
• If the deployment stops, the JOBNAME and JOBID are displayed to help you correct the problem. After you correct the problem, run the deployment again, opening ICE from the cloned site, starting from Step 1 – Process considerations.

If there is insufficient space for one or more data sets a message, similar to the following one, is displayed:

MNTPSPC2 ==>                                               Row 1 of 4 

 -  S Select Dataset to see more details 

 Enter: Process                          PF3/END: Return 

Note:The Table shows the Space/Dir Blocks that need to be added

0 Dataset                                      Space    DirBlk Alloc

   Name                                        Reqd     Reqd   Units

  IOA.V900.CLN.BASE.INSTALL                      1801     -     BLK 

  IOA.V900.CLN.SAMPEXIT                          1615     -     BLK 

************************** Bottom of data *************************** 

For more details about a particular data set, select the data set in the list and a pop-up, similar to the following one, is displayed:

MNTPSPC3 ==> 

 Dataset Name  : IOAE.K68B.BASE.INSTALL

 Space Allocation 

 Allocation Units: BLK 

 Space to be Added: 1801

 Total Allocated: 5640     Used: 4165    Extents: 1

 Total Free     : 1475     Required: 1788 

 Dir Blocks

 Blocks to be Added: - 

 Total Allocated: 180      Used: 146

 Total Free     : 34       Required: 10 

You can correct the space problem and continue with the deployment without stopping the process.

If you choose to stop the process, press PF3 (END). The process stops and you exit from ICE. To continue the deployment process later, open ICE from the cloned site and start from Step 1 – Process considerations

The deployment can stop if there are PTFs in the cloned environment that were not applied to the base environment. In this situation a pop-up, similar to the following one, is displayed:

MNTCSI ==>                                               Row 1 of 4

************************** Top of Data ****************************

# PTF / APAR That exist at the cloned environment that does not exist at the base

 # environment.

 PC01251

 PC01394

************************* Bottom of Data ***************************

Determine if the deployment package is at the correct maintenance level for the cloned environment. If necessary, run the deployment process again with a deployment package at an equal or greater maintenance level than the cloned environment. Open ICE from the cloned site and start from Step 1 – Process considerations.

• Enter CANCEL. The extracted and temporary data sets are removed from the cloned site. The deployment process ends.