To work with and manage Db2 for z/OS® on your subsystems, you must have
Db2 DevOps
Experience properly installed and
configured.
Before you begin
- Review the software requirements for Db2 DevOps
Experience. For details, see the
Software requirements for Db2 DevOps
Experience section.
- The latest PTF for IBM Unified
Management Server for z/OS must
be installed.
- You need to retrieve the UMS installation folder path on z/OS
UNIX System Services and the
RUNHLQ
of your UMS installation data
sets.Note: This is not the installation path. It is the path of IZP_UMS_VARDIR
.
- The SMP/E install for Db2 DevOps
Experience should be in the same SMP/E global zone as UMS.
Procedure
-
To stop the Unified Management Server started
task, run the following command:
/S <stc>,ACTION=STOP
where
<stc> is the name of the started task. The default
name is
IZPSRV
. You might have configured a different value
during UMS installation.
-
Shut down Zowe.
-
Go to System Display and Search Facility (SDSF) in 3270.
-
Stop ZSS cross-memory server.
/p <job_name>
If Zowe defaults have been chosen,
job_name
should be replaced with
ZWESISTC
.
-
Stop Zowe server.
/p <job_name>
If Zowe defaults have been chosen,
job_name
should be replaced with ZWESVSTC
.
-
To perform the Db2 DevOps
Experience
SMP/E installation, see the Db2 DevOps
Experience Program
Directory. Note the
z/OS
UNIX
location where Db2 DevOps
Experience is installed.
-
To copy modules into libraries for Db2
experiences and to create
DOEDB2PO
JCL
and a PARMLIB
member
IZPDB2PM
, which are required in later steps, complete the
following steps:
-
Edit
<RUNHLQ>.JCLLIB(IZPEXPIN)
,
which was installed as part of UMS.
Note: The UMSVLOC
variable should already be set to the
UMS USS Read/Write data location.
-
On the following line, specify the
z/OS
UNIX
directory where
Unified Management Server read/write
data is located, as specified by
IZP_UMS_VARDIR
.
//SET1 SET UMSVLOC='#izp_ums_vardir'
-
On the following line, specify the
z/OS
UNIX
directory where
Db2 DevOps
Experience was
SMP/E installed. The default location is:
<dir>/usr/lpp/IBM/doe/<vrm>/bin.
IZP_EXPERIENCE_LOC=#exp_install_location
-
Submit the
JCL
.
-
To set information necessary for later steps, specify the following parameters
in the data management product
PARMLIB
member IZPDB2PM
, which will be
created by IZPEXPIN
if not present in
PARMLIB
:
- IZP_DB2_ALL_SYSNAMES
- List all system names on which to APF-authorize load
module libraries for Db2
experiences
(smphlq.SIZPLINK and
smphlq.SIZPLLIB), which are packaged with
Db2 DevOps
Experience.
Separate multiple names with a space and enclose the list of names
in quotations. For example:
IZP_DB2_ALL_SYSNAMES: "SYS1 SYS2"
- IZP_DB2_IPL
- Specify the name of the
PROCLIB
member to run after
an IPL to invoke the APF authorization facility. The default member
is IZPDB2IP
. For example:
IZP_DB2_IPL: IZPDB2IP
Note: Ignore
the IZPD2DPM
member.
- This will be placed into the location specified by
IZP_PROCLIB
.
-
cmbatchDsn
- In addition to the above stated parameters, there is a commented out
parameter in the platform
IZPD2DPM
parameter
member, cmbatchDsn, which is related to Db2. During Db2 subsystem registration,
UMS will create several batch-related artifacts. The default
location for these is
<dbaUser>.IZPBATCH.PROCLIB. Uncomment
the cmbatchDsn variable to modify this location.
Note that this affects only the newly registered Db2 subsystems.
The following parameters related to the ISPF message library are
required:
- ISPFMessageLibrary
- ISPF message library
- ISPFSkeletonLibrary
- ISPF skeleton library
- ISPFTableLibrary
- ISPF table library
- ISPFLoadLibrary
- ISPF load library
- ISPFLPALibrary
- ISPF LPA library
- defaultPlanName
- Name of the default plan that Unified Management Server will always
bind to a particular subsystem
The following parameters related to the ISPF message library are
optional:
- dbaSqlid
- Owner of Db2 databases and
table spaces. Any value will be converted to uppercase. Default
value is '<NONE>'.
A SQLID
- The specified
Run SQLID
is the
owner of databases and table spaces. If the
specified Run SQLID
is different
from the current owner, the databases, table spaces,
and all dependent objects are dropped and re-created
to accomplish the change of owner.
<NONE>
- No
SET CURRENT SQLID
statements are
generated.
blank
SET CURRENT SQLID
statements are
generated when necessary.
- tempDatasetHLQ
- High-level qualifier (HLQ) for temporary data
sets that are created while different JCL jobs are run. The length
of the
tempDatasetHLQ
parameter must be 1 - 14
characters and the length of each qualifier in the
tempDatasetHLQ
parameter must be 1 - 8
characters. The name of each qualifier must begin with an alphabetic
(A - Z) or a special character (#, @, $). The remaining characters
in the name can be alphanumeric (A - Z, 0 - 9) or special characters
(#, @, $).
-
To create
IZPDB2IP
JCL, which is required in
the next step, edit the JOB statement of DOEDB2PO
in the
location specified by RUNHLQ.JCLLIB
, and
submit the job.
IZPDB2IP
JCL will be located in the
PROCLIB
specified by IZP_PROCLIB
.
-
To APF-authorize load module libraries for Db2
experiences
(smphlq.SIZPLINK and
smphlq.SIZPLLIB), edit the JOB statement of
IZPDB2IP
JCL, and submit the job. After an IPL rerun the
IZPDB2IP JCL
. Alternatively add the two libraries to the
PROGxx z/OS PARMLIB
member to persist it across IPLs.
-
Grant users the access to the
Db2 catalog tables by
completing the steps described in Granting catalog access to Db2 tables.
- Optional:
To specify the DDL definition files for the objects, define the DDL
templates:
-
Edit the
IZPD2DPM PARMLIB
member the IZP_PARMLIB
file,
and specify NICE_NAME: true
.
Note: If you specify NICE_NAME: false
, the files will
be named according to the current naming format. For example,
TB/1af0b92a-8329-4dd2-986e-1e0ed2a8e1f9.txt.
-
Specify the attributes for the templates that you want to define.
-
Start Zowe.
-
Start ZSS cross-memory server.
/s <job_name>,reusasid=yes
If Zowe defaults have been chosen,
job_name should be replaced with
ZWESISTC
. You must specify
reusasid=yes
after
<job_name>.
-
Start Zowe server.
/s <job_name>,instance='<zowe_instance>'
If Zowe defaults have been chosen,
job_name should be replaced with ZWESVSTC
. Replace
<zowe_instance> with the absolute path of
your Zowe instance directory.
-
To start Unified Management Server, run the
following command:
/S <stc>
where
<stc> is the name of the started task (the default
is
IZPSRV
).
-
In a supported browser, log in to Zowe at the following URL and open
IBM Unified
Experience for z/OS.
https://<hostname>:<port>/ZLUX/plugins/org.zowe.zlux.bootstrap/web/#/
where
<hostname> and
<port> are
the host name (or IP address) and port of the
Zowe host computer.
- Optional:
Verify that Db2 DevOps
Experience is
correctly installed by completing the steps mentioned in Verifying the installation of Db2 DevOps Experience.
What to do next
To use the features of Db2 DevOps
Experience, update the subsystem
registration by completing the steps described in Registering Db2 subsystems. If you want to
generate the DDL of an explored object, you must configure a Workload Manager (WLM)
environment for your subsystem:
- Create a WLM environment by using the template in
config_hlq.JCLLIB(WLMPROC)
that
points to the load libraries in
<HLQ>.SIZPLLIB
.
- Start the WLM by using the template in
config_hlq.JCLLIB(WLMPROC)
that points
to the WLM you created in step 1.
- While registering the subsystem, specify the name of the WLM in the
Workload Manager environment field on the
Configuration tab.
Note: If the subsystem is already
registered, edit the subsystem, specify the WLM environment, and click
Update.