Steps for provisioning a z/OS software instance

This topic describes the steps for provisioning a z/OS software instance.

1. Define the source z/OS system as a z/OSMF software instance.
   1. From the z/OSMF desktop, select the Software Management task.
   2. In Software Management, select Software Instances.
   3. Select Actions > Add and follow the screen prompts for your z/OS system. For more information, see the online help for the Software Management task.
   4. Verify the z/OS product for your environment:
      • View the software instance: Actions > View > Products, Features, FMIDs. Verify that the z/OS release is 2.5 or 2.4
      • View the data sets and z/OS UNIX files: Actions > View > Data sets.

        Notice that you can sort on the Volume column.

        Determine the number of DASD volumes used for the z/OS software instance. Be sure to check the z/OS UNIX data sets, too.

      • Work with your storage administrator to identify the type of DASD volumes that are associated with source z/OS software instance, such as Mod-9, Mod-18, or Mod-27. You will use the largest capacity of these volumes for the system residence (SYSRES) volume for the provisioned z/OS system (the target system). For example, if largest capacity SYSRES volume for the source z/OS software instance is Mod-18, all DASD volumes for the target system SYSRES must be Mod-18.
        Make note of the following details:

        • Number of volumes used for z/OS
        • Largest capacity device type in use.

        Later in this procedure, you will use this information when you define the LPAR pool entry for the target system.

2. Identify a logical partition (LPAR) to be used for provisioning the z/OS software instance.
   1. In the Hardware Management Console (HMC), locate a logical partition (LPAR) to be used for provisioning a z/OS instance. Or, define a new LPAR for this purpose.
      Note: Consider the potential performance implications of sharing CPU resources between existing systems and the newly provisioned system. Though this consideration applies whenever you share CPU resources between systems, be aware that Cloud Provisioning makes it easier and faster to create z/OS systems. To ensure that production workloads are insulated from competition for CPU resources, work with your systems engineer to ensure that production LPAR weights are defined properly.
   2. In the Sys Admin page, make note of the LPAR characteristics, such as the number of I/O devices and IP addresses. Later in this procedure, you will specify the same number of devices for the system residence volume that you use for the z/OS software instance.
3. Ensure that Base Control Program internal interface (BCPii) is configured and active on the provisioning system (the driving system).

   When you create a z/OS image, the provisioning system uses BCPii services to connect to system resources, such as the Support Element (SE) and the central processing complex (CPC). Therefore, the BCPii address space must be configured and active on the provisioning system.

   To determine whether BCPii is active, enter the following command from the system console:

   d a,hwibcpii

   The BCPii address space (HWIBCPII) starts automatically during system IPL. If it is not active, you can start the address space manually by entering the START HWISTART command at the system console.

   If the BCPii address space is unable to start, look for HWI* messages in the system log that indicate that BCPii failed to become active. Usually, the failures are caused by improper security configuration in the SE for BCPii communication with the local SE and the provisioning system. For more information, see the topic "BCPii address space does not start up at IPL" in MVS Programming: Callable Services for High-Level Languages.

   If the provisioning system is not enabled for BCPii, you must configure the local Support Element (SE) to support BCPii and configure the BCPii address space. For the detailed steps, see the topic "BCPii setup and installation" in MVS Programming: Callable Services for High-Level Languages.

4. Ensure that System REXX is configured and active on the provisioning system.

   For more information, see Ensuring that System REXX is set up and active in IBM® z/OS® Management Facility Configuration Guide.

5. Obtain the provisioning properties file.
   On the provisioning system, copy the zosProvision.properties file from the directory /usr/lpp/zosmf/samples/cpm-sample-zos to a user directory.

   If you need to modify the provisioning workflow, you can copy the contents of the /usr/lpp/zosmf/samples/cpm-sample-zos directory to a user directory.

   Future IBM service updates can include changes to the properties file. It is recommended that you use the most current version.
6. Modify the zosProvision.properties file with values for your environment.
   For descriptions of the properties, refer to the properties file.

   You can choose to provision the z/OS instance with a new RACF database with the base RACF definitions that are required for IPL and z/OSMF. The workflow variable source_racf_db is optional. By leaving this field empty, the provisioning process creates a new RACF database. Creating the new RACF database adds about 5 minutes to the provisioning time.

7. Create the z/OS provisioning template from the samples directory.
   1. In z/OS Cloud Provisioning, click Software Services.
   2. Select the Templates tab of Software Services to work with software services templates.
   3. Modify the template property file with values that are appropriate for your environment.
   4. Add the template by selecting Actions > Add Template > Standard.
   5. Specify the template name.

      Rather than specifying each of the files individually, you can specify just the manifest file: /usr/lpp/zosmf/samples/cpm-sample-zos/zos_provision.mf. Then click Load.

   6. Modify the location of the properties file where you saved the updated properties file.
      If you modified the workflow files or actions file, specify the location of the updated files.
   7. Click OK to create the template.
8. Associate the template with a tenant and create the LPAR resource pool.
   The LPAR resource pool is required for the z/OS provisioning. It can be created in either a dedicated or shared resource pool.
   1. For the template you created, click Actions > Associate Tenant and select an existing tenant.
      If you need to create a new tenant, use the Resource Management task to create a tenant in the domain in which the z/OS provisioning template is created. After a new tenant is created, you can perform Actions > Associate Tenant.
   2. Select the option to either create a dedicated resource pool, use an existing tenant-shared resource pool, or use an existing domain-shared resource pool.
   3. Click OK to associate the template with the tenant.
   4. If you chose to create a dedicated resource pool, the resource management task will open with the Add Template and Resource Pool displayed. If you chose to use an existing tenant-shared resource pool or use an existing domain-shared resource pool, the template will be added to the shared pool, but you will need to open the Resource Management task and modify the shared resource pool that you selected.
      • To modify a tenant-shared resource pool, from the Resource Management task select the Modify action for the domain, select the Modify action for the tenant, and then select the Modify action for the shared resource pool.
      • To modify a domain-shared resource pool, from the Resource Management task select the Modify action for the domain, and then select the Modify action for the shared resource pool.
   5. In the dialog Add Template and Resource Pool or the dialog Modify Template and Resource Pool, complete the fields in the Instance Details tab with appropriate values.
   6. In the Resource Pools tab, click Actions > Add Entry to add the LPAR to the LPAR resource pool for the template. This LPAR is used to host the provisioned z/OS system.
   7. In the dialog Add LPAR Pool Entry, complete each of the tabs to define the LPAR.
      When you define the LPAR entry, ensure that the number of SYSRES volumes are equal or greater than number of SYSRES volumes identified in Step 1. Other operational volumes and network properties are set with the information you collected in Step 2.
   8. When you have completed the input fields, click Complete.
   9. You can define multiple LPARs for the LPAR resource pool. If you want to identify more LPARs for hosting provisioned z/OS systems, repeat steps f through g.
      Note the following rules:

      • LPARs can be in same CPC or a different CPC.
      • The same LPAR/CPC cannot be specified in more than one LPAR resource pool.
   10. Click OK to associate the template with the tenant and create the LPAR resource pool.
9. If the template is in Pending Approvals state, you can approve it by clicking Actions > Approvals.
10. Test-run the template.
    To test run a template before publishing it, use the Test Run action that is provided in the Templates table.

    If you choose to provision the z/OS instance with a new RACF database, you are required to add the values for racf_user and racf_password.

    1. Select the checkbox to Create a new RACF database.
    2. Enter a value for the user ID for the new RACF database. This user ID is the only active user ID in the new RACF database and is used to log in into the provisioned system.
    3. Enter a value for the password for the user ID. Be sure to save this value in a safe space, as it cannot be recovered or reset when the system IPLs. At initial login, this password expires and prompts you to create a new one.

    If the test run encounters a problem and provisioning fails, examine the workflow and resolve the issue that is associated with the failed step. It is advised to perform a complete deprovision after a failure.

11. Publish the template.
    Publish makes a template available to consumers and prepares it for the Run action. It locks the template, allowing only limited modification, and puts it in the published state.
12. Run the template.
    To run a template, use the Run action that is provided in the templates table. This action creates an instance. Repeat this step every time you want to provision a new instance of z/OS.