content_image/989530.jpg content_image/989536.jpg
<img src='content_image/989530.jpg'>

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. 

<img src='content_image/989536.jpg'>

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. 

