Registering existing subsystems in z/OSMF

Use the provided registration workflows to register existing instances of CICS®, IBM® Db2®, and IBM MQ in the z/OSMF web interface. Registered subsystems are then available to be dynamically linked to during the provision of other containers.

z/OSMF maintains a registry of provisioned and registered subsystems. You can provision a container that automatically links to a registered subsystem by using the link option on the zospt run command. For more information about how to use the link option, see Using the --link option.

The following diagram shows how to dynamically connect to a registered subsystem by using the --link command.
Figure 1. Dynamically connect to a registered subsystem by using the --link command
This image shows how to dynamically connect to a registered subsystem by using the --link command, as described in the surrounding text.
Registering subsystems allows systems that are being provisioned by z/OS® PT to connect to existing subsystems:
  • With minimal configuration.
  • Without the need to install the correct resources in the registered subsystem.

How to register an existing subsystem

A z/OSMF administrator must give you domain administrator authority to enable you to add templates into the domain.
The following diagram shows how to register a subsystem instance in the z/OSMF web interface.
Figure 2. Register a subsystem instance in the z/OSMF web interface
This image shows how to register an instance of a subsystem in the z/OSMF web interface, as described in the surrounding text.
For more information, see Adding an IBM Cloud Provisioning and Management for z/OS template for use with z/OS Provisioning Toolkit. Upload and publish the registration workflow by using the z/OSMF web interface:
  1. Add the template to z/OSMF by going to Cloud Provisioning > Software Services and selecting the Templates tab. Click Add Template and specify the manifest file to load in the Template source file field (this file is the .mf file, found in the ../zospt/workflows/registration/subsystem folder). Click Load. The fields for Workflow file, Actions file, and Workflow variables input are populated automatically. Give your template a name, and click OK.
  2. Associate the template with a tenant. When you make the association, you can set limits for how many times the container can be provisioned and how many each user is allowed to provision. The association automatically creates a resource pool for the template and the network administrator is notified.
    Note: For users of IBM z/OS V2.3, to ensure that a container is visible to other members of the tenant, select the Allow other members of the tenant to access and run actions for software services instances check box.
  3. If you are ready, you can publish the template by selecting Software Services and selecting the Templates tab. Select the template that you want to publish, and select Actions > Publish. No approvals are needed to complete this step. If you do not publish the template at this stage, the template remains in draft state.

Running the template

You can run the template in either of the following ways:
  • Use z/OS PT to build the image (by using the zospt build command), then run the image (by using the zospt run command). If the template is in draft state, use the --draft option on the zospt run command. Add the subsystem properties to the zosptfile. For more information about building and running images, see Building an image with z/OS Provisioning Toolkit and Running a z/OS Provisioning Toolkit image.
  • Use the z/OSMF web interface to run the template by selecting Software Services and selecting the Templates tab. Select the template that you want to run, and select Actions > Run > . If your template is in draft state, select Actions > Test Run. Select the Associated tenant, and enter the subsystem properties. Properties that are marked with an asterisk are mandatory.

Supported z/OS PT commands on a registered subsystem

The following zospt commands are supported on registered subsystems:
  • zospt run
  • zospt rm -f(--force)
  • zospt inspect
  • zospt ps

Further information