Zowe has a number of runtimes on z/OS: the z/OS Service microservice server, the Zowe Application Server, and the Zowe API Mediation Layer microservices. A single PROCLIB
ZWESVSTC is used to start all of these microservices. This member is installed by Zowe into the data set SAMPLIB
SZWESAMP during the installation or either a convenience build or SMP/E.
This topic describes how to configure the z/OS runtime in order to launch Zowe. You can do these manually (as described in this topic) or use scripts to install and configure the cross memory server (see Installing and Configuring Zowe z/OS components using scripts.
When the Zowe runtime is launched, it is run under a z/OS started task with the PROCLIB member named
ZWESVSTC. A sample PROCLIB is created during installation into the PDS
SZWESAMP(ZWESVSTC). To launch Zowe as a started task, you must copy this member to a PDS that is in the proclib concatenation path.
ZWESVSTC should be configured as a started task under the
ZWESVUSR user ID with the administrator user ID of
ZWEADMIN. If you do not have these IDs already created, the commands to create the user ID and group are supplied in the PDS member
ZWESECUR. See Configuring the z/OS system for Zowe. To associate the
ZWESVSTC started task with the user ID and group, see Configuring a z/OS system for Zowe. This step will be done once per z/OS environment by a system programmer who has sufficient security privileges.
You can launch the Zowe started task in two ways. To see whether the started task has successfully launched see Troubleshooting installation and startup of Zowe z/OS components
To launch the
ZWESVSTC started task, run the
zowe-start.sh script from a USS shell. This reads the configuration values from the
instance.env file in the Zowe instance directory.
<ZOWE_INSTANCE_DIR> is the directory where you set the instance directory to. This script starts
ZWESVSTC for you so you do not have to log on to TSO and use SDSF.
Option 2: Starting Zowe with a
/S TSO command#
You can use SDSF to start Zowe.
If you issue the SDSF command
/S ZWESVSTC, the JCL will need to know the instance directory containing the launch and configuration information. To do this add the
INSTANCE parameter on the START command when you start Zowe in SDSF:
$ZOWE_INSTANCE_DIR argument is the fully qualifed path to the USS directory containing the
instance.env file containing the Zowe configuration.
JOBNAME='ZWEXSV' argument is optional and the started task will operate correctly without it, however having it specified ensures that the address spaces will be prefixed with
ZWEXSV which makes them easier to find in SDSF or locate in RMF records.
If you have a default instance directory you want you always start Zowe with, you can tailor the JCL member
ZWESVSTC at this line
to replace the
instance_directory with the location of the Zowe instance directory that contains the configurable Zowe instance directory.