4.1 Overview of zCX provisioning process To provision the zCX instance, you run a workflow in z/OSMF. However, before you run the  workflow you first must plan and prepare a number of items in z/OS, as described in this  section.  Table 4-1 lists the section that describe how to prepare for and then run the workflow to  provision a zCX Instance. Table 4-1 Chapters that explain the zCX provisioning process Section Topic 4.2, “RACF planning” How to set up the RACF environment 4.3, “USS planning” on page 54 What directories in USS are required 4.4, “z/OSMF” on page 55 How z/OSMF is required 4.5, “Configure TCPIP addresses” on page 57 TCPIP requirements and how to configure 4.6, “SMS planning” on page 59 SMS requirements for VSAM linear data sets that are used 4.7, “zCX property file” on page 60 Preparation of the property file to use in the workflow 4.8, “Run zCX provisioning workflow” on page 62 How to execute the zCX provisioning workflow 4.9, “Starting the zCX instance” on page 73 How to start the zCX instance 4.10, “Log on to the zCX instance” on page 79 How to log on to the zCX instance 4.2 RACF planning 4.2.1 Overview GLYPH<SM590000> Provision the zCX instance in z/OSMF. GLYPH<SM590000> Run the zCX instance started task. GLYPH<SM590000> Administer the zCX instance. Prior to creating zCX instances, you must consider what RACF user IDs and groups are  required to manage the provisioning and operation of those instances. The three user IDs and groups that we use in our environment have these distinct roles: You provision a zCX instance in three main steps: 1. Use z/OSMF to run the zCX provisioning workflow. 2. Run the zCX instance as a started task on z/OS. 3. Access the zCX instance by using the admin user ID. Before you start the preceding process, you must plan what user IDs and groups to use for  the different parts. You could use a single user ID for all steps of provisioning a zCX instance,  but that is not recommended. When you plan your RACF setup, it is always recommended that you define a user ID under  which a started task runs on z/OS. That way, you can prevent this user ID from being used to  log on to any z/OS application. 50  Getting started with z/OS Container Extensions