add_data_disks.xm l Add data disks  workflow Use this workflow when your zCX instances need more disk space for swap  data and user data. During execution of this workflow, new VSAM linear data  sets are allocated and formatted. You can run this workflow against an active  zCX instance, but to use the additional space, you must restart the instance. upgrade.xml Upgrade  workflow Use this workflow to apply service and maintenance to an existing zCX  instance. During execution of this workflow, an alternate root VSAM linear  data set is allocated.  rollback.xml Rollback  workflow Use this workflow to roll back a maintenance level for an existing zCX  instance, in the event that you are suffering any issues with the new  maintenance level. During execution, the original root VSAM data set —  which has been put aside during execution of the upgrade workflow — is  restored. After rollback, stop your zCX instance, and restart it again. deprovision.xml Deprovisioning  workflow Use this workflow to deprovision an existing zCX instance. During execution,  all VSAM data sets and the instance zFS file system are deleted. Workflow name Workflow type Workflow content All z/OSMF workflows in Table 2-1 first retrieve and gather the zCX instance properties. On  that basis, they perform the subsequent steps either manually or through automation. We  suggest that you run the steps through automation, because some of them might take a few  minutes to complete. In z/OSMF, do not make changes to the xml files, because they are managed by SMP/E.  Therefore, any modifications that you make to the files are subject to being overwritten.  Besides the xml files with the workflow contents in  /usr/lpp/zcx_zos/properties , you find a  workflow variable file, which you can use as a template. Copy this template to your own home  directory, and fill in the variables with values that are appropriate for your zCX instances.  Template files can save time after you know the configuration. You supply your customized  template file whenever you provision, thus avoiding the need to type all the values in. z/OSMF workflows for manually starting and stopping zCX instances In Table 2-2 on page 28, we describe two additional workflows that you can use for manual  start and stop actions of your existing zCX containers. You can find the xml file in  /usr/lpp/zcx_zos/workflows/actions. Table 2-2 z/OSMF workflows for manual start and stop actions Workflow name Workflow type Workflow description start_instance.xml Start instance  workflow Use this workflow to start an already provisioned zCX  instance. This workflow uses z/OSMF console REST  services in the background to send out the  start  command. stop_instance.xml Stop instance  workflow Use this workflow to stop an already provisioned zCX  instance. This workflow uses z/OSMF console REST  services in the background to send out the  stop  command. If you plan to use the start and stop workflows, that we describe in Table 2-2 on page 28,  review the chapter on z/OS console services in the following IBM Redbooks publications:  IBM z/OSMF Programming Guide,  SC27-8420. 28  Getting started with z/OS Container Extensions