| Note |
|---|
|
Before using this information and the product it supports, be sure to read the general information under "Notices". |
Copyright Contributors to the Zowe Project. 2019, 2022, 2024
Program and Service Level Information
Installation Requirements and Considerations
This program directory is intended for system programmers who are responsible for program installation and maintenance. It contains information about the material and procedures associated with the installation of Zowe Open Source Project. This publication refers to Zowe Open Source Project as Zowe.
The Program Directory contains the following sections:
Zowe is an open source project created to host technologies that benefit the Z platform from all members of the Z community (Integrated Software Vendors, System Integrators and z/OS consumers). Zowe, like Mac or Windows, comes with a set of APIs and OS capabilities that applications build on and also includes some applications out of the box.
Zowe offers modern interfaces to interact with z/OS and allows you to work with z/OS in a way that is similar to what you experience on cloud platforms today. You can use these interfaces as delivered or through plug-ins and extensions that are created by clients or third-party vendors.
Zowe consists of the following FMIDs:
Basic Machine-Readable Materials are materials that are supplied under the base license and are required for the use of the product.
The distribution medium for this program is downloadable files. This program is in SMP/E RELFILE format and is installed by using SMP/E. See "Installation Instructions" for more information about how to install the program.
The following sections identify the basic publications for Zowe.
Table 1 identifies the basic unlicensed program
publications for Zowe.
Table 1. Basic Material: Unlicensed
| Publication Title | Form Number | Media Format |
|---|---|---|
|
https://docs.zowe.org/stable/user-guide/install-zos
| online | See note 1 |
Note:
| ||
Requisite information can be obtained from https://docs.zowe.org/stable/user-guide/systemrequirements-zos. From the version drop-down list, find the documentation for the Zowe version you are using.
No optional publications are provided for Zowe.
No program source materials or viewable program listings are provided for Zowe. However, program source materials can be obtained from https://github.com/zowe/.
You might want to use the publications listed in
Table 2 during
the installation of Zowe.
Table 2. Publications Useful During Installation
| Publication Title | Form Number |
|---|---|
| IBM SMP/E for z/OS User's Guide | SA23-2277 |
| IBM SMP/E for z/OS Commands | SA23-2275 |
| IBM SMP/E for z/OS Reference | SA23-2276 |
| IBM SMP/E for z/OS Messages, Codes, and Diagnosis | GA32-0883 |
Note: These publications can be found in IBM Documentation. Use a web browser with internet access to refer to: https://www.ibm.com/docs/en/zos/2.5.0?topic=zos-smpe
This section describes the support available for Zowe.
Report any problems which you feel might be an error in the product materials to the Zowe community via https://github.com/zowe/community/issues/new/choose. You may be asked to gather and submit additional diagnostics to assist the community in their analysis.
This section identifies the program and relevant service levels of Zowe. The program level refers to the APAR fixes that have been incorporated into the program. The service level refers to the PTFs that have been incorporated into the program.
All APARs of previous releases of Zowe that were resolved before March 2024 have been incorporated into Zowe.
No PTFs against this release of Zowe have been incorporated into the product package.
Zowe service can be downloaded from https://zowe.org/download/.
The following sections identify the system requirements for installing and activating Zowe. The following terminology is used:
The program might have specific operating system or product level requirements for using processes, such as binder or assembly utilities during the installation.
The program might have specific product level requirements, such as needing access to the library of another product for link-edits. These requirements, either mandatory or optional, might directly affect the element during the installation or in its basic or enhanced operation.
In many cases, you can use a system as both a driving system and a target system. However, you can make a separate IPL-able clone of the running system to use as a target system. The clone must include copies of all system libraries that SMP/E updates, copies of the SMP/E CSI data sets that describe the system libraries, and your PARMLIB and PROCLIB.
Use separate driving and target systems in the following situations:
This section describes the environment of the driving system required to install Zowe.
The driving system can run in any hardware environment that supports the required software.
Table 3. Driving System Software Requirements
| Program
Number | Product
Name | Minimum
VRM | Minimum
Service Level will satisfy these APARs | Included
in the shipped product? |
|---|---|---|---|---|
| 5650-ZOS | z/OS | 2.3.0 | N/A | No |
| Note: The minimum product version is either what is listed in the table, or the currently minimum supported version, whichever is the most recent. | ||||
Note: SMP/E is a requirement for Installation and is an element of z/OS.
Note: Installation might require migration to new z/OS releases to be service supported. See https://www.ibm.com/support/lifecycle/
Zowe is installed into a file system. Before installing Zowe, you must ensure that the target system file system data sets are available for processing on the driving system. OMVS must be active on the driving system and the target system file data sets must be mounted on the driving system.
zFS must be active on the driving system. Information on activating and using zFS can be found in z/OS Distributed File Service zSeries File System Administration (SC24-5989).
This section describes the environment of the target system required to install and use Zowe.
Zowe can install in the z/OS (Z038) SREL.
The target system can run in any hardware environment that supports the required software.
Installation requisites identify products that are required and must be present on the system or products that are not required but should be present on the system for the successful installation of this product.
Mandatory installation requisites identify products that are required on the system for the successful installation of this product. These products are specified as PREs or REQs.
Zowe has no mandatory installation requisites.
Conditional installation requisites identify products that are not required for successful installation of this product but can resolve such things as certain warning messages at installation time. These products are specified as IF REQs.
Zowe has no conditional installation requisites.
Operational requisites are products that are required and must be present on the system or products that are not required but should be present on the system for this product to operate all or part of its functions.
Mandatory operational requisites identify products that
are required for this product
to operate its basic functions.
Table 4. Target System Mandatory Operational Requisites
| Program Number | Product Name and
Minimum VRM/Service Level |
|---|---|
| 5655-NOD | IBM SDK for Node.js - z/OS 14.0.0 or higher
See note 1 |
| 5655-DGH | IBM 64-bit SDK for z/OS Java Technology Edition 8.0.0 |
| 5650-ZOS | IBM z/OS Management Facility 2.3.0 or higher |
| 5650-ZOS | IBM z/OS 2.3.0 or higher |
| Note: The minimum product version is either what is listed in the table, or the currently minimum supported version, whichever is the most recent. | |
Conditional operational requisites identify products that
are not required for this product to operate its basic
functions but are required at run time for this product to operate
specific functions. These products are specified as IF REQs.
Table 5. Target System Conditional Operational Requisites
| Program
Number | Product Name and
Minimum VRM/Service Level | Function |
|---|---|---|
| 5650-ZOS | z/OS OpenSSH 2.3.0 or higher | SSH connection |
| Note: The minimum product version is either what is listed in the table, or the currently minimum supported version, whichever is the most recent. | ||
Toleration/coexistence requisites identify products that must be present on sharing systems. These systems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASD environment (such as test and production), or systems that reuse the same DASD environment at different time intervals.
Zowe has no toleration/coexistence requisites.
Negative requisites identify products that must not be installed on the same system as this product.
Zowe has no negative requisites.
Zowe libraries can reside on all supported DASD types.
Table 6 lists the total space that is required for each
type of library.
Table 6. Total DASD Space Required by Zowe
| Library Type | Total Space Required
in 3390 Trks | Description |
|---|---|---|
| Target | 95 Tracks | |
| Distribution | 12980 Tracks | |
| File System(s) | 27900 Tracks | |
| Web Download | 39945 Tracks |
These are temporary data sets, which can be removed after the SMP/E
install.
|
Notes:
| U | Unique data set, allocated by this product and used by only this product. This table provides all the required information to determine the correct storage for this data set. You do not need to refer to other tables or program directories for the data set size. |
| S | Shared data set, allocated by this product and used by this product and other products. To determine the correct storage needed for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. |
| E | Existing shared data set, used by this product and other products. This data set is not allocated by this product. To determine the correct storage for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. |
If you currently have a previous release of this product installed in these libraries, the installation of this release will delete the old release and reclaim the space that was used by the old release and any service that had been installed. You can determine whether these libraries have enough space by deleting the old release with a dummy function, compressing the libraries, and comparing the space requirements with the free space in the libraries.
For more information about the names and sizes of the required data sets, see "Allocate SMP/E Target and Distribution Libraries".
| N | New path, created by this product. |
| X | Path created by this product, but might already exist from a previous release. |
| P | Previously existing path, created by another product. |
Table 7. Storage Requirements for SMP/E Work Data Sets
| Library
DDNAME | T
Y P E | O
R G | R
E C F M | L
R E C L | No.
of 3390 Trks | No.
of DIR Blks |
|---|---|---|---|---|---|---|
| SMPWRK6 | S | PDS | FB | 80 | (5250,525) | 50 |
| SYSUT1 | U | SEQ | -- | -- | (5250,525) | 0 |
Table 8. Storage Requirements for SMP/E Data Sets
| Library
DDNAME | T
Y P E | O
R G | R
E C F M | L
R E C L | No.
of 3390 Trks | No.
of DIR Blks |
|---|---|---|---|---|---|---|
| SMPPTS | S | PDSE | FB | 80 | (5250,5250) | 50 |
The following figures describe the target and distribution libraries and file system paths required to install Zowe. The storage requirements of Zowe must be added to the storage required by other programs that have data in the same library or path.
Note: Use the data in these tables to determine which libraries can be
merged into common data sets. In addition, since some
ALIAS names may not be unique, ensure that no naming conflicts will be
introduced before merging libraries.
Table 9. Storage Requirements for Zowe Target Libraries
| Library
DDNAME | Member
Type | Target
Volume | T
Y P E | O
R G | R
E C F M | L
R E C L | No.
of 3390 Trks | No.
of DIR Blks |
|---|---|---|---|---|---|---|---|---|
| SZWEAUTH | APF Load Modules | ANY | U | PDSE | U | 0 | 60 | N/A |
| SZWEEXEC | Scripts | ANY | U | PDSE | FB | 80 | 15 | 30 |
| SZWESAMP | Samples | ANY | U | PDSE | FB | 80 | 20 | 30 |
Table 10. Zowe File System Paths
| DDNAME | T
Y P E | Path Name |
|---|---|---|
| SZWEZFS | X | /usr/lpp/zowe/SMPE |
Table 11. Storage Requirements for Zowe Distribution Libraries
| Library
DDNAME | T
Y P E | O
R G | R
E C F M | L
R E C L | No.
of 3390 Trks | No.
of DIR Blks |
|---|---|---|---|---|---|---|
| AZWEAUTH | U | PDSE | U | 0 | 60 | N/A |
| AZWESAMP | U | PDSE | FB | 80 | 20 | 30 |
| AZWEZFS | U | PDSE | VB | 6995 | 12900 | 30 |
The following figures list data sets that are not used by Zowe,
but are required as input for SMP/E.
Table 12. Storage Requirements for Zowe Web Download Data Sets
| Data Set
Name | T
Y P E | O
R G | R
E C F M | L
R E C L | No.
of 3390 Trks | No.
of DIR Blks |
|---|---|---|---|---|---|---|
| hlq.ZOWE.AZWE003.F1 | U | PDSE | FB | 80 | 7 | N/A |
| hlq.ZOWE.AZWE003.F2 | U | PDSE | FB | 80 | 13 | N/A |
| hlq.ZOWE.AZWE003.F3 | U | PDSE | U | 0 | 41 | N/A |
| hlq.ZOWE.AZWE003.F4 | U | PDSE | VB | 6995 | 10722 | N/A |
| hlq.ZOWE.AZWE003.SMPMCS | U | SEQ | FB | 80 | 2 | N/A |
| z/OS UNIX file system | U | zFS | N/A | N/A | 29160 | N/A |
| Note: These are temporary data sets, which can be removed after the SMP/E install. | ||||||
Installing Zowe might result in the deletion of other FMIDs. To see which FMIDs will be deleted, examine the ++VER statement in the SMPMCS of the product.
If you do not want to delete these FMIDs at this time, install Zowe into separate SMP/E target and distribution zones.
Note: These FMIDs are not automatically deleted from the Global Zone. If you want to delete these FMIDs from the Global Zone, use the SMP/E REJECT NOFMID DELETEFMID command. See the SMP/E Commands book for details.
Zowe has no special considerations for the target system.
This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of Zowe.
Please note the following points:
Use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install this release of Zowe.
The recommended values for certain SMP/E CSI subentries are shown in
Table 13. Using values lower than the recommended values
can result in failures in the installation.
DSSPACE is a subentry in the
GLOBAL options entry. PEMAX is a subentry of the GENERAL entry in the
GLOBAL options entry. See the SMP/E manuals for instructions on
updating the global zone.
Table 13. SMP/E Options Subentry Values
| Subentry | Value | Comment |
|---|---|---|
| DSSPACE | (1200,1200,1400) | Space allocation |
| PEMAX | SMP/E Default | We recommend using the SMP/E default for PEMAX. |
Overview of steps required to install Zowe Open Source Project.
These instructions are also in the AZWE003.readme.txt file that you downloaded from the web.
The SMP/E input data sets to install Zowe Open Source Project are provided as compressed files in AZWE003.pax.Z, which must be uploaded to z/OS as a z/OS UNIX file. You can either create a new z/OS UNIX file system (zFS) or create a new directory in an existing file system to place AZWE003.pax.Z.
You can use the following sample JCL to create a new file system, and directory, for the download package.
//FILESYS JOB <job information>
//*
//* - Provide valid job card information
//* - Change:
//* @zfs_path@
//* ----+----1----+----2----+----3----+----4----+----5
//* - To the absolute z/OS UNIX path for the download
//* package (starting with /)
//* - Maximum length is 50 characters
//* - Do not include a trailing /
//* @zfs_dsn@
//* - To your file system data set name
//*
//* Your userid MUST be defined as a SUPERUSER to successfully
//* run this job
//*
//CREATE EXEC PGM=IDCAMS,REGION=0M,COND=(0,LT)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER ( -
NAME(@zfs_dsn@) -
TRK(29160 30) -
LINEAR -
SHAREOPTIONS(3) -
)
//*
// SET ZFSDSN='@zfs_dsn@'
//FORMAT EXEC PGM=IOEAGFMT,REGION=0M,COND=(0,LT),
// PARM='-aggregate &ZFSDSN -compat'
//*STEPLIB DD DISP=SHR,DSN=IOE.SIOELMOD before z/OS 1.13
//*STEPLIB DD DISP=SHR,DSN=SYS1.SIEALNKE from z/OS 1.13
//SYSPRINT DD SYSOUT=*
//*
//MOUNT EXEC PGM=IKJEFT01,REGION=0M,COND=(0,LT)
//SYSEXEC DD DISP=SHR,DSN=SYS1.SBPXEXEC
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
PROFILE MSGID WTPMSG
oshell umask 0022; +
mkdir -p @zfs_path@
MOUNT +
FILESYSTEM('@zfs_dsn@') +
MOUNTPOINT('@zfs_path@') +
MODE(RDWR) TYPE(ZFS) PARM('AGGRGROW')
//*
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
These instructions are also in the AZWE003.readme.txt file that you downloaded from the web.
Upload the AZWE003.readme.txt file in text format and the AZWE003.pax.Z file in binary format from your workstation to the z/OS UNIX file system.
In the following sample dialog, we use FTP from a Microsoft Windows
command line to do the transfer. Commands or other information entered
by the user are in bold, and the following values are assumed:
| User enters: | Values |
|---|---|
| mvsaddr | TCP/IP address or hostname of the z/OS system |
| tsouid | Your TSO user ID |
| tsopw | Your TSO password |
| d: | Location of the downloaded files |
| @zfs_path@ | z/OS UNIX path where to store the files. This matches the @zfs_path@ variable you specified in the previous step. |
C:\>ftp mvsaddr Connected to mvsaddr. 220-FTPD1 IBM FTP CS %version% at mvsaddr, %time% on %date%. 220 Connection will close if idle for more than 5 minutes. User (mvsaddr:(none)): tsouid 331 Send password please. Password: tsopw 230 tsouid is logged on. Working directory is "tsouid.". ftp> cd @zfs_path@ 250 HFS directory @zfs_path@ is the current working directory ftp> ascii 200 Representation type is Ascii NonPrint ftp> put d:\AZWE003.readme.txt 200 Port request OK. 125 Storing data set @zfs_path@/AZWE003.readme.txt 250 Transfer completed successfully. ftp: 9412 bytes sent in 0.01 sec. (1366.67 Kb/s) ftp> binary 200 Representation type is Image ftp> put d:\AZWE003.pax.Z 200 Port request OK. 125 Storing data set @zfs_path@/AZWE003.pax.Z 250 Transfer completed successfully. ftp: 481549824 bytes sent in 1.26 sec. (1040.52 Kb/s) ftp> quit 221 Quit command received. Goodbye.
These instructions are also in the AZWE003.readme.txt file that you downloaded from the web.
The AZWE003.readme.txt file uploaded in the previous step holds a sample JCL to expand the compressed SMPMCS and RELFILEs from the uploaded AZWE003.pax.Z file into data sets for use by the SMP/E RECEIVE job. The JCL is repeated here for your convenience.
//EXTRACT JOB <job information>
//*
//* - Provide valid job card information
//* - Change:
//* @PREFIX@
//* ----+----1----+----2
//* - To your desired data set name prefix
//* - Maximum length is 20 characters
//* - This value is used for the names of the
//* data sets extracted from the download-package
//* @zfs_path@
//* ----+----1----+----2----+----3----+----4----+----5
//* - To the absolute z/OS UNIX path for the
//* download package (starting with /)
//* - Maximum length is 50 characters
//* - Do not include a trailing /
//*
//UNPAX EXEC PGM=IKJEFT01,REGION=0M,COND=(0,LT)
//SYSEXEC DD DISP=SHR,DSN=SYS1.SBPXEXEC
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
oshell cd @zfs_path@/ ; +
pax -rvf AZWE003.pax.Z
//*
//GIMUNZIP EXEC PGM=GIMUNZIP,REGION=0M,COND=(0,LT)
//*STEPLIB DD DISP=SHR,DSN=SYS1.MIGLIB
//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(50,10))
//SYSUT4 DD UNIT=SYSALLDA,SPACE=(CYL,(25,5))
//SMPOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SMPDIR DD PATHDISP=KEEP,
// PATH='@zfs_path@/'
//SYSIN DD *
<GIMUNZIP>
<ARCHDEF archid="AZWE003.SMPMCS"
newname="@PREFIX@.ZOWE.AZWE003.SMPMCS"/>
<ARCHDEF archid="AZWE003.F1"
newname="@PREFIX@.ZOWE.AZWE003.F1"/>
<ARCHDEF archid="AZWE003.F2"
newname="@PREFIX@.ZOWE.AZWE003.F2"/>
<ARCHDEF archid="AZWE003.F3"
newname="@PREFIX@.ZOWE.AZWE003.F3"/>
<ARCHDEF archid="AZWE003.F4"
newname="@PREFIX@.ZOWE.AZWE003.F4"/>
</GIMUNZIP>
//*
The following sample installation jobs are provided as part of the
product to help you install Zowe:
Table 15. Sample Installation Jobs
| Job Name | Job Type | Description | SMPTLIB Data Set |
|---|---|---|---|
| ZWE1SMPE | SMP/E | Sample job to create an SMP/E environment (optional) | ZOWE.AZWE003.F1 |
| ZWE2RCVE | RECEIVE | Sample SMP/E RECEIVE job | ZOWE.AZWE003.F1 |
| ZWE3ALOC | ALLOCATE | Sample job to allocate target and distribution libraries | ZOWE.AZWE003.F1 |
| ZWE4ZFS | ALLOMZFS | Sample job to allocate, create mountpoint, and mount zFS data sets | ZOWE.AZWE003.F1 |
| ZWE5MKD | MKDIR | Sample job to invoke the supplied ZWEMKDIR EXEC to allocate file system paths | ZOWE.AZWE003.F1 |
| ZWE6DDEF | DDDEF | Sample job to define SMP/E DDDEFs | ZOWE.AZWE003.F1 |
| ZWE7APLY | APPLY | Sample SMP/E APPLY job | ZOWE.AZWE003.F1 |
| ZWE8ACPT | ACCEPT | Sample SMP/E ACCEPT job | ZOWE.AZWE003.F1 |
| Note: When Zowe is downloaded from the web, the RELFILE data set name will be prefixed by your chosen high level qualifier, as documented in section "Extract and expand the compressed SMPMCS and RELFILEs". | |||
You can access the sample installation jobs by performing an SMP/E RECEIVE (refer to "Perform SMP/E RECEIVE") then copy the jobs from the SMPTLIB data sets to a work data set for editing and submission. See Table 15 to find the appropriate data set.
You can also copy the sample installation jobs from the product files by submitting the following job. Before you submit the job, add a job card and change the lowercase parameters to uppercase values to meet the requirements of your site.
//STEP1 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //IN DD DSN=ZOWE.AZWE003.F1, // DISP=SHR, //* VOL=SER=filevol, // UNIT=SYSALLDA //OUT DD DSNAME=jcl-library-name, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(5,5,5)), //* VOL=SER=dasdvol, // UNIT=SYSALLDA //SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1)) //SYSIN DD * COPY INDD=IN,OUTDD=OUT SELECT MEMBER=(ZWEMKDIR,&ZREXZFS.,ZWE1SMPE,ZWE2RCVE,ZWE3ALOC) SELECT MEMBER=(ZWE4ZFS,ZWE5MKD,ZWE6DDEF,ZWE7APLY,ZWE8ACPT) //*
Note: When Zowe is downloaded from the web, the RELFILE data set name will be prefixed by your chosen high level qualifier, as documented in section "Extract and expand the compressed SMPMCS and RELFILEs".
See the following information to update the statements in the previous sample:
If you are using an existing CSI, do not run the sample job ZWE1SMPE.
If you choose to create a new SMP/E environment for this install, a sample job is provided or you may choose to use your own JCL. If you choose to use the sample job provided, edit and submit ZWE1SMPE. Consult the instructions in the sample job for more information.
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
Edit and submit sample job ZWE2RCVE to perform the SMP/E RECEIVE for Zowe. Consult the instructions in the sample job for more information.
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
Edit and submit sample job ZWE3ALOC to allocate the SMP/E target and distribution libraries for Zowe. Consult the instructions in the sample job for more information.
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
This job allocates, creates a mountpoint, and mounts zFS data sets.
If you plan to install Zowe into a new z/OS UNIX file system, you can edit and submit the optional ZWE4ZFS job to perform the following tasks:
The recommended z/OS UNIX file system type is zFS. The recommended mountpoint is /usr/lpp/zowe.
Before running the sample job to create the z/OS UNIX file system, you must ensure that OMVS is active on the driving system. zFS must be active on the driving system if you are installing Zowe into a file system that is zFS.
If you create a new file system for this product, consider updating the BPXPRMxx PARMLIB member to mount the new file system at IPL time. This action can be helpful if an IPL occurs before the installation is completed.
MOUNT FILESYSTEM('#dsn')
MOUNTPOINT('/usr/lpp/zowe')
MODE(RDWR) /* can be MODE(READ) */
TYPE(ZFS) PARM('AGGRGROW') /* zFS, with extents */
See the following information to update the statements in the previous sample:
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
The target file system data set must be mounted on the driving system when running the sample ZWE5MKD job since the job will create paths in the file system.
Before running the sample job to create the paths in the file system, you must ensure that OMVS is active on the driving system and that the target system's file system is mounted to the driving system. zFS must be active on the driving system.
If you plan to install Zowe into a new file system, you must create the mountpoint and mount the new file system to the driving system for Zowe.
The recommended mountpoint is /usr/lpp/zowe.
Edit and submit sample job ZWE5MKD to allocate the file system paths for Zowe. Consult the instructions in the sample job for more information.
If you create a new file system for this product, consider updating the BPXPRMxx PARMLIB member to mount the new file system at IPL time. This action can be helpful if an IPL occurs before the installation is completed.
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
Edit and submit sample job ZWE6DDEF to create DDDEF entries for the SMP/E target and distribution libraries for Zowe. Consult the instructions in the sample job for more information.
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
The latest HOLDDATA is available through several different portals, including http://service.software.ibm.com/holdata/390holddata.html. The latest HOLDDATA may identify HIPER and FIXCAT APARs for the FMIDs you will be installing. An APPLY CHECK will help you determine if any HIPER or FIXCAT APARs are applicable to the FMIDs you are installing. If there are any applicable HIPER or FIXCAT APARs, the APPLY CHECK will also identify fixing PTFs that will resolve the APARs, if a fixing PTF is available.
You should install the FMIDs regardless of the status of unresolved HIPER or FIXCAT APARs. However, do not deploy the software until the unresolved HIPER and FIXCAT APARs have been analyzed to determine their applicability. That is, before deploying the software either ensure fixing PTFs are applied to resolve all HIPER or FIXCAT APARs, or ensure the problems reported by all HIPER or FIXCAT APARs are not applicable to your environment.
To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the PRE, ID, REQ, and IFREQ on the APPLY CHECK. The SMP/E root cause analysis identifies the cause only of errors and not of warnings (SMP/E treats bypassed PRE, ID, REQ, and IFREQ conditions as warnings, instead of errors).
Here are sample APPLY commands:
APPLY S(fmid,fmid,...) CHECK FORFMID(fmid,fmid,...) SOURCEID(RSU*) FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE) GROUPEXTEND .
Some HIPER APARs might not have fixing PTFs available yet. You should analyze the symptom flags for the unresolved HIPER APARs to determine if the reported problem is applicable to your environment and if you should bypass the specific ERROR HOLDs in order to continue the installation of the FMIDs.
This method requires more initial research, but can provide resolution for all HIPERs that have fixing PTFs available and are not in a PE chain. Unresolved PEs or HIPERs might still exist and require the use of BYPASS.
APPLY S(fmid,fmid,...) CHECK FORFMID(fmid,fmid,...) SOURCEID(RSU*) FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE) GROUPEXTEND BYPASS(HOLDCLASS(HIPER)) . ..any other parameters documented in the program directory
This method is quicker, but requires subsequent review of the Exception SYSMOD report produced by the REPORT ERRSYSMODS command to investigate any unresolved HIPERs. If you have received the latest HOLDDATA, you can also choose to use the REPORT MISSINGFIX command and specify Fix Category IBM.PRODUCTINSTALL-REQUIREDSERVICE to investigate missing recommended service.
If you bypass HOLDs during the installation of the FMIDs because fixing PTFs are not yet available, you can be notified when the fixing PTFs are available by using the APAR Status Tracking (AST) function of ServiceLink or the APAR Tracking function of ResourceLink.
Note: The GROUPEXTEND operand indicates that SMP/E applies all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions.
Expected Return Codes and Messages from APPLY CHECK: You will receive a return code of 0 if this job runs correctly.
Expected Return Codes and Messages from APPLY: You will receive a return code of 0 if this job runs correctly.
Edit and submit sample job ZWE8ACPT to perform an SMP/E ACCEPT CHECK for Zowe. Consult the instructions in the sample job for more information.
To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the PRE, ID, REQ, and IFREQ on the ACCEPT CHECK. The SMP/E root cause analysis identifies the cause of errors but not warnings (SMP/E treats bypassed PRE, ID, REQ, and IFREQ conditions as warnings rather than errors).
Before you use SMP/E to load new distribution libraries, it is recommended that you set the ACCJCLIN indicator in the distribution zone. In this way, you can save the entries that are produced from JCLIN in the distribution zone whenever a SYSMOD that contains inline JCLIN is accepted. For more information about the ACCJCLIN indicator, see the description of inline JCLIN in the SMP/E Commands book for details.
After you take actions that are indicated by the ACCEPT CHECK, remove the CHECK operand and run the job again to perform the ACCEPT.
Note: The GROUPEXTEND operand indicates that SMP/E accepts all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions.
Expected Return Codes and Messages from ACCEPT CHECK: You will receive a return code of 0 if this job runs correctly.
If PTFs that contain replacement modules are accepted, SMP/E ACCEPT processing will link-edit or bind the modules into the distribution libraries. During this processing, the Linkage Editor or Binder might issue messages that indicate unresolved external references, which will result in a return code of 4 during the ACCEPT phase. You can ignore these messages, because the distribution libraries are not executable and the unresolved external references do not affect the executable system libraries.
Expected Return Codes and Messages from ACCEPT: You will receive a return code of 0 if this job runs correctly.
The SMP/E REPORT CROSSZONE command identifies requisites for products that are installed in separate zones. This command also creates APPLY and ACCEPT commands in the SMPPUNCH data set. You can use the APPLY and ACCEPT commands to install those cross-zone requisites that the SMP/E REPORT CROSSZONE command identifies.
After you install Zowe, it is recommended that you run REPORT CROSSZONE against the new or updated target and distribution zones. REPORT CROSSZONE requires a global zone with ZONEINDEX entries that describe all the target and distribution libraries to be reported on.
For more information about REPORT CROSSZONE, see the SMP/E manuals.
The web download data sets listed in Table 12 (section "DASD Storage Requirements") are temporary data sets. You can delete these data sets after you complete the SMP/E install.
If you mount the file system in which you have installed Zowe in read-only mode during execution, then you do not have to take further actions to activate Zowe.
The publication https://docs.zowe.org/stable/user-guide/install-zos (online) contains the necessary information to customize and use Zowe.
Additional documentation can be found at https://docs.zowe.org/stable/. From the version drop-down list, find the documentation for the Zowe version you are using.
APAR numbers are provided in this document to assist in locating PTFs that may be required. Ongoing problem reporting may result in additional APARs being created. Therefore, the APAR lists in this document may not be complete.
ZOWE, the ZOWE logo, and zowe.org are trademarks or registered
trademarks of Linux Foundation, registered in many jurisdictions worldwide.
Other product and service names might be trademarks of Linux Foundation or
other companies.
Program Directory for Zowe Open Source Project, March 2024
We appreciate your input on this publication. Feel free to comment on the clarity, accuracy, and completeness of the information or give us any other feedback that you might have.
Report your comments in https://github.com/zowe/community/issues/new/choose.
Thank you for your participation.