Installing and configuring Zowe z/OS components using scripts
Installing and configuring Zowe z/OS components using scripts
A Zowe installation creates two PDS sample libraries, SZWEAUTH
and SZWESAMP
. Before starting the two Zowe started tasks for the main Zowe z/OS components and the cross memory server, you must complete additional configuration steps as described in
- Installing and starting the Zowe started task (ZWESVSTC) or Installing and starting the Zowe high availability started task (ZWESLSTC)
- Installing and configuring the Zowe cross memory server (ZWESISTC)
Zowe provides UNIX shell scripts to assist with installation and configuration for scenarios where you wish to automate this process, for example if you have a DevOps pipeline or other repeatable scenario where you are installing and starting a Zowe runtime. These are the same scripts used by the Zowe community themselves for the automated Zowe continuous integration continuous delivery (CICD) pipeline which creates Zowe releases.
#
Zowe z/OS componentsThe script <RUNTIME_DIR>/scripts/utils/zowe-install-proc.sh -d <dataSetPrefix> [-r <proclib> -l <log_directory]
has the following parameters:
-d <dataSetPrefix>
- Source PDS PrefixDataset prefix of the source PDS
.SZWESAMP
where Zowe was installed into.For an installation from a convenience build, this will be the value of the
-h
argument whenzowe-install.sh
was executed.For an SMP/E installation, this will be the value of
$datasetPrefixIn
in the memberAZWE001.F1(ZWE3ALOC)
.-r <proclib>
- Target PROCLIB PDS (optional)Target PROCLIB PDS where Zowe server started task procedure will be placed. If the parameter is omitted, the script scans the JES PROCLIB concatenation path and uses the first data set where the user has write access
-l <log_directory>
- Log directory (optional)Overrides the default log output directory of
/global/zowe/logs
, if it is writable, or~/zowe/logs
.Example
Executing the command
zowe-install-proc.sh -d MYUSERID.ZWE -r USER.PROCLIB
copies the PDS memberMYUSERID.ZWE.SZWESAMP(ZWESVSTC)
toUSER.PROCLIB(ZWESVSTC)
.
#
Cross memory and auxiliary serverThe script <RUNTIME_DIR>/scripts/utils/zowe-install-xmem.sh -d <dataSetPrefix> [-a <parmlib>] [-r <proclib] [-l <log_directory]
has the following parameters.
-d <dataSetPrefix>
- Source PDS prefix.This is the data set prefix of the source PDS
.SZWESAMP
where Zowe was installed into.-a <parmlib>
- Target DSN for PARMLIB (optional)This is the data set name where the PARMLIB member
ZWESIP00
will be placed. If the parameter is omitted, then source data set.SZWESAMP
will be used by the started task PROCLIBZWESISTC
. If-a
is set, then theEXEC DD PARMLIB=
statement in the JCL PROCLIBZWESISTC
will be updated.-r <proclib>
- Target PROCLIB PDS whereZWESASTC
andZWESISTC
will be placed.If the parameter is omitted, then the script scans the JSE PROCLIB concatenation and uses the first data set where the user running the script has write access.
-l <log_directory>
- Log directory (optional)Overrides the default log output directory of
/global/zowe/logs
, if it is writeable. If it is not writeable,~/zowe/logs
is used.Example:
Executing the command
zowe-install-xmem.sh -d MYUSERID.ZWE -a USER.PARMLIB -r USER.PROCLIB
copies:- the PARMLIB member
MYUSERID.ZWE.SZWESAMP(ZWESIP00)
toUSER.PARMLIB(ZWESIP00)
- the PROCLIB member
MYUSERID.ZWE.SZWESAMP(ZWESISTC)
toUSER.PROCLIB(ZWESISTC)
andMYUSERID.ZWESAMP(ZWESASTC)
toUSER.PROCLIB(ZWESASTC)
- the PARMLIB member
The script zowe-install-xmem.sh
moves and modifies files, but does not perform the steps needed to APF-authorize the PDSE containing the load module ZWESIS00
and does not enable it to run in key(4) non-swappable. Those steps are a requirement for running ZIS. It is also recommended for ZIS plugins to be put within the plugin dataset .SZWEPLUG
which also needs to be APF-authorized. The steps required are described in Installing and configuring the Zowe cross memory server: APF authorize and Installing and configuring the Zowe cross memory server: Key 4 non-swappable.