Valid values:
As part of this process, the list of elements to be deployed are displayed on the screen and duplicated to the ICELOG.
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:
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:
Do one of the following, depending how the process terminates:
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.
Parent Topic |