Provisioning instances to target environments

Learn how to provision z/OS instances to target environments.

The provisioning options in the web server will install and configure the On-Demand Environments emulator on the selected target environment, which is followed by the initial program load of z/OS® that is contained in the selected image.
Note:
  • To ensure that a provisioning is shown as success after IPL is complete, SSHD must be running. The provisioning operation for On-Demand Environments relies on being able to SSH to the target z/OS to determine when the IPL is complete. It is also used as a means of being able to initiate data set restorage after IPL. If SSHD is not started with the IPL process, the web server will time out after ten minutes because a successful SSH connection to the target z/OS is not established. Even the IPL can be completed successfully, the web server determines that the IPL fails, and shows that the provisioning operation has failed.
  • When working with On-Demand Environments v1.0.2, any Linux target environment that was successfully created in v1.0.1 or earlier, must be migrated before it can be used for provisioning new instance(s). The Migrate action button on the Manage Target Environment page can be used to initiate a target environment migration.

Pre-provisioning validation

Before you provision instances from images to a Linux® target environment, you must ensure that the following items are valid. Otherwise, when you provision instances, the pre-provisioning validation function will automatically check the items, and some error messages might occur.
Note: The pre-provisioning validation is only applicable for the Linux target environments.
  1. Linux distribution

    Only RHEL and Ubuntu operating systems are officially supported. CentOS, SLES operating systems are unofficially supported.

  2. CPU architecture

    s390x and x86_64 are supported.

  3. CPs and RAM

    The quantity of processors for Linux on x86-64 hardware cannot be more than 8 and for Linux on s390x hardware the quantity cannot be more than 16.

    The quantity of memory for an instance depends on how much RAM is required for the software that is included in the image.

  4. License server connectivity
    • Your target environment should be able to interact with the licence server using both ports 1947 and 9451 if you use a software-based licence server.
  5. Storage server connectivity
    • The storage server default port is 22 and it can be customized.
  6. Permission on the deployment directory

    Check whether the user ID has the write access to the deployment directory that was specified.

  7. Available disk space on the deployment directory

    Check whether the available disk space of the deployment directory is adequate. To provision instances from created images successfully, a full application size and an extra space of the maximum decompressed volume size are needed.