| Note |
|---|
|
Before using this information and the product it supports, be sure to read the general information under "Notices". |
© Copyright International Business Machines Corporation 2020, 2021. All rights reserved.
Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp.
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 IBM Z Open Automation Utilities. This publication refers to IBM Z Open Automation Utilities as ZOAU.
The Program Directory contains the following sections:
Before installing ZOAU, read the CBPDO Memo To Users and the CBPDO Memo To Users Extension that are supplied with this program in softcopy format and this program directory; after which, keep the documents for your reference. Section "Preventive Service Planning" tells you how to find any updates to the information and procedures in this program directory.
ZOAU is supplied in a Custom-Built Product Delivery Offering (CBPDO, 5751-CS3). The program directory that is provided in softcopy format on the CBPDO is identical to the hardcopy format if one was included with your order. All service and HOLDDATA for ZOAU are included on the CBPDO.
Do not use this program directory if you install ZOAU with a SystemPac or ServerPac. When you use one of those offerings, use the jobs and documentation supplied with the offering. The offering will point you to specific sections of this program directory as needed.
IBM Z Open Automation Utilities (ZOAU) provides a set of utilities for z/OS which are modeled after similar standard Linux commands but updated to work with z/OS data sets and file systems.
Language support for these utilities is extended to allow programmers to use a preferred programming language, such as Python, to develop scripts and automation tools.
ZOAU consists of the following FMIDs:
An IBM program is identified by a program number.
Basic Machine-Readable Materials are materials that are supplied under the base license and are required for the use of the product.
The program announcement material describes the features supported by ZOAU. Ask your IBM representative for this information if you have not already received a copy.
The distribution medium for this program is physical media or 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.
You can find information about the physical media for the basic machine-readable materials for ZOAU in the CBPDO Memo To Users Extension.
Table 1 describes the program file content for ZOAU. You can refer to the CBPDO Memo To Users Extension to see where the files reside on the image.
Notes:
| Name | O
R G |
R
E C F M |
L
R E C L |
BLK
SIZE |
|---|---|---|---|---|
| SMPMCS | SEQ | FB | 80 | 8800 |
| IBM.HAL5120.F1 | PDS | FB | 80 | 8800 |
| IBM.HAL5120.F2 | PDS | VB | 255 | 27998 |
The following sections identify the basic publications for ZOAU.
No optional publications are provided for ZOAU.
No program source materials or viewable program listings are provided for ZOAU.
You might want to use the publications listed in
Table 2 during
the installation of ZOAU.
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: IBM Publications Center
(
https://www.ibm.com/shop/publications/order)
IBM Documentation
(
https://www.ibm.com/docs/)
This section describes the IBM support available for ZOAU. The service number for ZOAU is 0509589.
Contact your IBM representative for specific information about available program services.
Before you install ZOAU, make sure that you have reviewed the current Preventive Service Planning (PSP) information. Review the PSP Bucket for General Information, Installation Documentation, and the Cross Product Dependencies sections. For the Recommended Service section, instead of reviewing the PSP Bucket, it is recommended you use the IBM.PRODUCTINSTALL-REQUIREDSERVICE fix category in SMP/E to ensure you have all the recommended service installed. Use the FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE) operand on the APPLY CHECK command. See "Perform SMP/E APPLY" for a sample APPLY command
If you obtained ZOAU as part of a CBPDO, HOLDDATA is included.
If the CBPDO for ZOAU is older than two weeks by the time you install the product materials, you can obtain the latest PSP Bucket information by going to the following website:
https://www14.software.ibm.com/webapp/set2/psearch/search?domain=psp
You can also use S/390 SoftwareXcel or contact the IBM Support Center to obtain the latest PSP Bucket information.
For program support, access the Software Support Website at https://www.ibm.com/products/software
PSP Buckets are identified by UPGRADEs, which specify product levels;
and SUBSETs, which specify the FMIDs for a product level. The UPGRADE
and SUBSET values for ZOAU are included in Table 3.
Table 3. PSP Upgrade and Subset ID
| UPGRADE | SUBSET | Description |
|---|---|---|
| ZOAU120 | HAL5120 | IBM Z Open Automation Utilities |
Report any problems which you feel might be an error in the product materials to your IBM Support Center. You may be asked to gather and submit additional diagnostics to assist the IBM Support Center in their analysis.
Table 4 identifies the component IDs
(COMPID)
for ZOAU.
| FMID | COMPID | Component Name | RETAIN
Release |
|---|---|---|---|
| HAL5120 | 5724T0753 | IBM Z Open Automation Utilities | 120 |
This section identifies the program and relevant service levels of ZOAU. 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 resolved APARs of previous releases of ZOAU have been incorporated into ZOAU.
Frequently check the ZOAU PSP Bucket for HIPER and SPECIAL attention PTFs against all FMIDs that you must install. You can also receive the latest HOLDDATA, then add the FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE) operand on your APPLY CHECK command. This will allow you to review the recommended and critical service that should be installed with your FMIDs.
The following sections identify the system requirements for installing and activating ZOAU. 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 ZOAU.
The driving system can run in any hardware environment that supports the required software.
Table 5. 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 | V02.03.00 or higher | N/A | No |
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/software/support/lifecycle/index_z.html.
ZOAU is installed into a file system, either HFS or zFS. Before installing ZOAU, 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.
If you plan to install ZOAU in a zFS file system, this requires that zFS 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 ZOAU.
ZOAU installs 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.
Table 6. Target System Mandatory Installation Requisites
| Program
Number | Product
Name | Minimum
VRM | Minimum
Service Level will satisfy these APARs | Included
in the shipped product? |
|---|---|---|---|---|
| 5650-ZOS | z/OS | 02.03.00 or higher | N/A | No |
Note: Installation might require migration to new z/OS releases to be service supported. See https://www.ibm.com/support/home/pages/lifecycle/?from=index_z.
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.
ZOAU 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.
ZOAU has no mandatory operational requisites.
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.
ZOAU has no conditional operational requisites.
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.
ZOAU has no toleration/coexistence requisites.
Negative requisites identify products that must not be installed on the same system as this product.
ZOAU has no negative requisites.
ZOAU libraries can reside on all supported DASD types.
Table 7 lists the total space that is required for each
type of library.
Table 7. Total DASD Space Required by ZOAU
| Library Type | Total Space Required
in 3390 Trks | Description |
|---|---|---|
| Target | 5 Tracks | |
| Distribution | 225 Tracks | |
| File System(s) | 620 Tracks | /usr/lpp/IBM/zoautil |
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. |
The following figures describe the target and file system paths and distribution libraries required to install ZOAU. The storage requirements of ZOAU 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 8. Storage Requirements for ZOAU 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 |
|---|---|---|---|---|---|---|---|---|
| SBGYSAMP | Samples | ANY | U | PDS | FB | 80 | 5 | 5 |
Table 9. ZOAU File System Paths
| DDNAME | T
Y P E |
Path Name |
|---|---|---|
| SBGYA001 | X | /usr/lpp/IBM/zoautil/IBM |
Table 10. Storage Requirements for ZOAU 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 |
|---|---|---|---|---|---|---|
| ABGYSAMP | U | PDS | FB | 80 | 5 | 5 |
| ABGYZFS | U | PDS | VB | 8796 | 220 | 5 |
Installing ZOAU 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 ZOAU 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.
ZOAU 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 ZOAU.
Please note the following points:
Use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install this release of ZOAU.
The recommended values for certain SMP/E CSI subentries are shown in
Table 11. 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 11. SMP/E Options Subentry Values
| Subentry | Value | Comment |
|---|---|---|
| DSSPACE | (1500,1500,1500) | Space allocation |
| PEMAX | SMP/E Default | IBM recommends using the SMP/E default for PEMAX. |
Overview of steps required to install IBM Z Open Automation Utilities.
The following sample installation jobs are provided as part of the
product to help you install ZOAU:
Table 12. Sample Installation Jobs
| Job Name | Job Type | Description | SMPTLIB Data Set |
|---|---|---|---|
| BGY1SMPE | SMP/E | Sample job to create an SMP/E environment (optional) | IBM.HAL5120.F1 |
| BGY2RCVE | RECEIVE | Sample SMP/E RECEIVE job | IBM.HAL5120.F1 |
| BGY3ALOC | ALLOCATE | Sample job to allocate target and distribution libraries | IBM.HAL5120.F1 |
| BGY4ZFS | ALLOMZFS | Sample job to allocate, create mountpoint, and mount zFS data sets | IBM.HAL5120.F1 |
| BGY5MKD | MKDIR | Sample job to invoke the supplied BGYMKDIR EXEC to allocate file system paths | IBM.HAL5120.F1 |
| BGY6DDEF | DDDEF | Sample job to define SMP/E DDDEFs | IBM.HAL5120.F1 |
| BGY7APLY | APPLY | Sample SMP/E APPLY job | IBM.HAL5120.F1 |
| BGY8ACPT | ACCEPT | Sample SMP/E ACCEPT job | IBM.HAL5120.F1 |
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 12 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=IBM.HAL5120.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
/*
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 BGY1SMPE.
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 BGY1SMPE. 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.
If you have obtained ZOAU as part of a CBPDO, use the RCVPDO job in the CBPDO RIMLIB data set to receive the ZOAU FMIDs, service, and HOLDDATA that are included on the CBPDO package. For more information, see the documentation that is included in the CBPDO.
You can also choose to edit and submit sample job BGY2RCVE to perform the SMP/E RECEIVE for ZOAU. 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 BGY3ALOC to allocate the SMP/E target and distribution libraries for ZOAU. 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 ZOAU into a new z/OS UNIX file system, you can edit and submit the optional BGY4ZFS job to perform the following tasks:
The recommended z/OS UNIX file system type is zFS. The recommended mountpoint is /usr/lpp/IBM/zoautil.
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 ZOAU 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/IBM/zoautil')
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 system HFS or zFS data set must be mounted on the driving system when running the sample BGY5MKD job since the job will create paths in the HFS or zFS.
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 HFS or zFS file system is mounted to the driving system. zFS must be active on the driving system if you are installing ZOAU into a file system that is zFS.
If you plan to install ZOAU into a new HFS or zFS file system, you must create the mountpoint and mount the new file system to the driving system for ZOAU.
The recommended mountpoint is /usr/lpp/IBM/zoautil.
Edit and submit sample job BGY5MKD to allocate the HFS or zFS paths for ZOAU. 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 BGY6DDEF to create DDDEF entries for the SMP/E target and distribution libraries for ZOAU. 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 https://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 BGY8ACPT to perform an SMP/E ACCEPT CHECK for ZOAU. 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 ZOAU, 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.
If you mount the file system in which you have installed ZOAU in read-only mode during execution, then you do not have to take further actions to activate ZOAU.
Refer to IBM Documentation for ZOAU to complete the configuration tasks.
https://www.ibm.com/docs/en/zoau/1.2.0
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
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. To obtain current service recommendations and to identify current product service requirements, always contact the IBM Customer Support Center or use S/390 SoftwareXcel to obtain the current "PSP Bucket".
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the
IBM Director of LicensingFor license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property LicensingIBM, the IBM logo, and other IBM trademark listed on the
IBM Trademarks List are trademarks or registered trademarks of
International Business Machines Corporation, in the United States
and/or other countries. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM
trademarks is available on ibm.com/trademark.
Program Directory for IBM Z Open Automation Utilities, September 2021
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.
Send your comments by emailing us at ibmdocs@us.ibm.com, and include the following information:
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you submit.