Note |
---|
Before using this information and the product it supports, be sure to read the general information under "Notices". |
© Copyright International Business Machines Corporation 2013, 2017. All rights reserved.
© HCL Technologies Ltd. 2017, 2022
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 Application Delivery Foundation for z/OS Common Components. This publication refers to IBM Application Delivery Foundation for z/OS Common Components as ADFzCC.
The Program Directory contains the following sections:
The rest of this section only applies when ADFzCC is ordered
via Shopz. It does not apply when you downloaded it from the web.
Select this link to go to the next section:
"ADFzCC Description"
Before installing ADFzCC, 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.
ADFzCC 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 ADFzCC are included on the CBPDO.
Do not use this program directory if you install ADFzCC with a 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 Application Delivery Foundation for z/OS Common Components delivers common components used by some of IBM's problem determination tools for z/OS application development. ADFzCC is automatically included in your order when you obtain one of the following products:
IBM Application Delivery Foundation for z/OS Common Components 1.9.0 now provides TLS 1.3 support in the Common Server.
ADFzCC consists of the following FMIDs:
The rest of this section only applies when ADFzCC is ordered
via Shopz. It does not apply when you downloaded it from the web.
Select this link to go to the next section:
"Program Materials"
You will receive the following materials:
An IBM program is identified by a program number. The program number for ADFzCC is 5755-A03.
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 ADFzCC. 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.
The rest of this section only applies when ADFzCC is ordered
via Shopz. It does not apply when you downloaded it from the web.
Select this link to go to the next section:
"Program Publications"
You can find information about the physical media for the basic machine-readable materials for ADFzCC in the CBPDO Memo To Users Extension.
Table 1 describes the program file content for ADFzCC.
Table 2 describes the program file content for ADFzCC Japanse component.
You can refer to the CBPDO Memo To Users Extension to see where the files reside on the image.
Notes:
Table 1. Program File Content -- Base
Name | O
R G | R
E C F M | L
R E C L | BLK
SIZE |
---|---|---|---|---|
SMPMCS | SEQ | FB | 80 | 3120 |
IBM.HVWR190.F1 | PDS | FB | 80 | 8800 |
IBM.HVWR190.F2 | PDS | FB | 80 | 8800 |
IBM.HVWR190.F3 | PDS | U | 0 | 6144 |
IBM.HVWR190.F4 | PDS | FB | 80 | 8800 |
IBM.HVWR190.F5 | PDS | FB | 80 | 8800 |
IBM.HVWR190.F6 | PDS | FB | 80 | 8800 |
IBM.HVWR190.F7 | PDSE | U | 0 | 6144 |
IBM.HVWR190.F8 | PDSE | U | 0 | 6144 |
IBM.HVWR190.F9 | PDS | U | 0 | 6144 |
Table 2. Program File Content -- JPN
Name | O
R G | R
E C F M | L
R E C L | BLK
SIZE |
---|---|---|---|---|
SMPMCS | SEQ | FB | 80 | 3120 |
IBM.JVWR191.F1 | PDS | FB | 80 | 8800 |
IBM.JVWR191.F2 | PDS | U | 0 | 6144 |
IBM.JVWR191.F3 | PDS | FB | 80 | 8800 |
IBM.JVWR191.F4 | PDS | FB | 80 | 8800 |
IBM.JVWR191.F5 | PDS | FB | 80 | 8800 |
IBM.JVWR191.F6 | PDSE | U | 0 | 6144 |
The following sections identify the basic publications for ADFzCC.
Table 3 identifies the basic unlicensed program
publications for ADFzCC.
Table 3. Basic Material: Unlicensed Publications
Publication Title | Form Number | Media Format |
---|---|---|
IBM Application Delivery Foundation for z/OS Common Components Customization and User's Guide |
| See note 1 |
Note:
|
No optional publications are provided for ADFzCC.
No program source materials or viewable program listings are provided for ADFzCC.
You might want to use the publications listed in
Table 4 during
the installation of ADFzCC.
Table 4. 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 IBM support available for ADFzCC.
Contact your IBM representative for specific information about available program services.
Before you install ADFzCC, 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 ADFzCC as part of a CBPDO, HOLDDATA is included.
If the CBPDO for ADFzCC 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://esupport.ibm.com/customercare/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/mysupport/.
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 ADFzCC are included in Table 5.
Table 5. PSP Upgrade and Subset ID
UPGRADE | SUBSET | Description |
---|---|---|
ADFZCC | HVWR190 | ADFzCC Base (English) |
ADFZCC | JVWR191 | ADFzCC JPN (Japanese) |
For a complete list of available PTFs (both HIPER and non-HIPER PTFs) and the relevant APARs, refer to https://www.ibm.com/support/pages/latest-adfz-common-components-service-information
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 6 identifies the component IDs
(COMPID)
for ADFzCC.
FMID | COMPID | Component Name | RETAIN
Release |
---|---|---|---|
HVWR190 | 5655IPV00 | ADFzCC -- Base | 190 |
JVWR191 | 5655IPV00 | ADFzCC -- JPN | 191 |
This section identifies the program and relevant service levels of ADFzCC. 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.
The following APAR fixes against previous releases of ADFzCC have been incorporated into this release. They are listed by FMID.
No PTFs against this release of ADFzCC have been incorporated into the product package.
Frequently check the ADFzCC 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 ADFzCC. 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 ADFzCC.
The driving system can run in any hardware environment that supports the required software.
Table 7. 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 | 02.04.00 or higher | N/A | No |
Note: The minimum z/OS level is either what is listed in the table, or the currently minimum supported OS level, 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/
This section describes the environment of the target system required to install and use ADFzCC.
ADFzCC 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. These products are specified as PREs or REQs.
ADFzCC 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.
ADFzCC 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.
ADFzCC 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.
ADFzCC 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.
ADFzCC has no toleration/coexistence requisites.
Negative requisites identify products that must not be installed on the same system as this product.
ADFzCC has no negative requisites.
ADFzCC libraries can reside on all supported DASD types.
Table 8 lists the total space that is required for each
type of library.
Table 8. Total DASD Space Required by ADFzCC -- Base
Library Type | Total Space Required
in 3390 Trks | Description |
---|---|---|
Target | 750 Tracks | |
Distribution | 750 Tracks | |
Web Download | 744 Tracks | This row only applies when ADFzCC is downloaded from the web.
It does not apply when you ordered it via Shopz.
These are temporary data sets, which can be removed after the SMP/E install. |
Table 9. Total DASD Space Required by ADFzCC -- JPN
Library Type | Total Space Required
in 3390 Trks | Description |
---|---|---|
Target | 45 Tracks | |
Distribution | 45 Tracks | |
Web Download | 143 Tracks | This row only applies when ADFzCC is downloaded from the web.
It does not apply when you ordered it via Shopz.
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".
The following figures describe the target and distribution libraries required to install ADFzCC. The storage requirements of ADFzCC must be added to the storage required by other programs that have data in the same library.
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 10. Storage Requirements for ADFzCC Target Libraries -- Base
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 |
---|---|---|---|---|---|---|---|---|
SIPVLPA1 | LMOD | ANY | U | PDS | U | 0 | 45 | 2 |
SIPVMENU | Message | ANY | U | PDS | FB | 80 | 15 | 5 |
SIPVMODA | LMOD | ANY | U | PDSE | U | 0 | 600 | N/A |
SIPVMOD1 | LMOD | ANY | U | PDSE | U | 0 | 45 | N/A |
SIPVPENU | Panel | ANY | U | PDS | FB | 80 | 15 | 5 |
SIPVSAM1 | Sample | ANY | U | PDS | FB | 80 | 15 | 5 |
SIPVTENU | Table | ANY | U | PDS | FB | 80 | 15 | 2 |
Table 11. Storage Requirements for ADFzCC Target Libraries -- JPN
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 |
---|---|---|---|---|---|---|---|---|
SIPVMJPN | Message | ANY | U | PDS | FB | 80 | 15 | 5 |
SIPVPJPN | Panel | ANY | U | PDS | FB | 80 | 15 | 5 |
SIPVTJPN | Table | ANY | U | PDS | FB | 80 | 15 | 2 |
Table 12. Storage Requirements for ADFzCC Distribution Libraries -- Base
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 |
---|---|---|---|---|---|---|
AIPVLPA1 | U | PDS | U | 0 | 45 | 2 |
AIPVMENU | U | PDS | FB | 80 | 15 | 5 |
AIPVMODA | U | PDSE | U | 0 | 600 | N/A |
AIPVMOD1 | U | PDSE | U | 0 | 45 | N/A |
AIPVPENU | U | PDS | FB | 80 | 15 | 5 |
AIPVSAM1 | U | PDS | FB | 80 | 15 | 5 |
AIPVTENU | U | PDS | FB | 80 | 15 | 2 |
Table 13. Storage Requirements for ADFzCC Distribution Libraries -- JPN
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 |
---|---|---|---|---|---|---|
AIPVMJPN | U | PDS | FB | 80 | 15 | 5 |
AIPVPJPN | U | PDS | FB | 80 | 15 | 5 |
AIPVTJPN | U | PDS | FB | 80 | 15 | 2 |
The rest of this section only applies when ADFzCC is
downloaded from the web. It does not apply when you ordered it via
Shopz.
Select this link to go to the next section:
"FMIDs Deleted"
The following figures list data sets that are not used by ADFzCC,
but are required as input for SMP/E.
Table 14. Storage Requirements for ADFzCC Web Download Data Sets -- Base
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.IBM.HVWR190.F1 | U | PDS | FB | 80 | 17 | 5 |
hlq.IBM.HVWR190.F2 | U | PDS | FB | 80 | 17 | 16 |
hlq.IBM.HVWR190.F3 | U | PDS | U | 0 | 18 | 10 |
hlq.IBM.HVWR190.F4 | U | PDS | FB | 80 | 19 | 10 |
hlq.IBM.HVWR190.F5 | U | PDS | FB | 80 | 17 | 13 |
hlq.IBM.HVWR190.F6 | U | PDS | FB | 80 | 17 | 6 |
hlq.IBM.HVWR190.F7 | U | PDSE | U | 0 | 36 | N/A |
hlq.IBM.HVWR190.F8 | U | PDSE | U | 0 | 174 | N/A |
hlq.IBM.HVWR190.F9 | U | PDS | U | 0 | 35 | 2 |
hlq.IBM.HVWR190.SMPMCS | U | SEQ | FB | 80 | 19 | N/A |
z/OS UNIX file system | U | zFS | N/A | N/A | 375 | N/A |
Note: These are temporary data sets, which can be removed after the SMP/E install. |
Table 15. Storage Requirements for ADFzCC Web Download Data Sets -- JPN
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.IBM.JVWR191.F1 | U | PDS | FB | 80 | 17 | 5 |
hlq.IBM.JVWR191.F2 | U | PDS | U | 0 | 18 | 10 |
hlq.IBM.JVWR191.F3 | U | PDS | FB | 80 | 19 | 10 |
hlq.IBM.JVWR191.F4 | U | PDS | FB | 80 | 17 | 13 |
hlq.IBM.JVWR191.F5 | U | PDS | FB | 80 | 17 | 6 |
hlq.IBM.JVWR191.F6 | U | PDSE | 6144 | 0 | 18 | N/A |
hlq.IBM.JVWR191.SMPMCS | U | SEQ | FB | 80 | 19 | N/A |
z/OS UNIX file system | U | zFS | N/A | N/A | 18 | N/A |
Note: These are temporary data sets, which can be removed after the SMP/E install. |
Installing ADFzCC 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 ADFzCC 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.
PDSE Considerations:
ADFzCC uses the "partitioned data set extended" or PDSE format for its target libraries. There are some operational differences between PDS and PDSE data sets. The PDS format may be shared by more than one z/OS system and no special precautions are necessary. However the PDSE format may only be shared by z/OS systems which are part of a sysplex or which are connected using Global Resource Serialization (are in a GRS complex). If z/OS systems share use of a PDSE data set outside of a sysplex or GRS environment, you may experience severe problems when the data set is updated. This is due to the fact that PDSE directory information is cached in storage, and when the data set is updated from one system the other system(s) have no knowledge of the update, and their cached directory information will be incorrect.
You must take care not to share the libraries between z/OS systems unless they are in a sysplex or are connected in a GRS complex. If you need to share the content of the libraries, a separate copy must be created for each z/OS system.
This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of ADFzCC.
Please note the following points:
Use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install this release of ADFzCC.
The recommended values for certain SMP/E CSI subentries are shown in
Table 16. 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 16. SMP/E Options Subentry Values
Subentry | Value | Comment |
---|---|---|
DSSPACE | (1200,1200,1400) | Space allocation |
PEMAX | SMP/E Default | IBM recommends using the SMP/E default for PEMAX. |
Overview of steps required to install IBM Application Delivery Foundation for z/OS Common Components.
Select this link to skip the web download specific steps: "Sample Jobs"
This section only applies when ADFzCC is downloaded from the
web. It does not apply when it is ordered via Shopz.
Select this link to skip the web download specific steps:
"Sample Jobs"
The SMP/E input data sets to install IBM Application Delivery Foundation for z/OS Common Components are provided as compressed files in archives HVWR190.pax.Z and JVWR191.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 the download package.
You can use the following sample JCL to create a new file system, and directory, for the download package. The sample assumes that you will upload only the base feature (FMID HVWR190). The size of the file system must be increased if you also include other features:
//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(375 10) - 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.
This section only applies when ADFzCC is downloaded from the
web. It does not apply when it is ordered via Shopz.
Select this link to skip the web download specific steps:
"Sample Jobs"
Upload the HVWR190.readme.txt file, and JVWR191.readme.txt if required, in text format and the HVWR190.pax.Z file, and JVWR191.pax.Z if required, 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. |
Issue these commands to upload the ADFzCC Base:
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:\HVWR190.readme.txt 200 Port request OK. 125 Storing data set @zfs_path@/HVWR190.readme.txt 250 Transfer completed successfully. ftp: 19845 bytes sent in 0.01 sec. (1366.67 Kb/s) ftp> binary 200 Representation type is Image ftp> put d:\HVWR190.pax.Z 200 Port request OK. 125 Storing data set @zfs_path@/HVWR190.pax.Z 250 Transfer completed successfully. ftp: 4612608 bytes sent in 1.26 sec. (1040.52 Kb/s) ftp> quit 221 Quit command received. Goodbye.
Issue these commands to upload the ADFzCC Japanese feature:
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:\JVWR191.readme.txt 200 Port request OK. 125 Storing data set @zfs_path@/JVWR191.readme.txt 250 Transfer completed successfully. ftp: 19521 bytes sent in 0.01 sec. (1323.80 Kb/s) ftp> binary 200 Representation type is Image ftp> put d:\JVWR191.pax.Z 200 Port request OK. 125 Storing data set @zfs_path@/JVWR191.pax.Z 250 Transfer completed successfully. ftp: 96768 bytes sent in 1.26 sec. (1115.22 Kb/s) ftp> quit 221 Quit command received. Goodbye.
This section only applies when ADFzCC is downloaded from the
web. It does not apply when it is ordered via Shopz.
Select this link to skip the web download specific steps:
"Sample Jobs"
The HVWR190.readme.txt and JVWR191.readme.txt files uploaded in the previous step each hold a sample JCL to expand the compressed SMPMCS and RELFILEs from the uploaded HVWR190.pax.Z and JVWR191.pax.Z files into data sets for use by the SMP/E RECEIVE job. The JCLs are repeated here for your convenience.
Customize and submit this JCL to expand the ADFzCC Base:
//EXTRACT JOB <job information> //* //* - Provide valid job card information //* - Change: //* @PREFIX@ //* ----+----1----+----2----+ //* - To your desired data set name prefix //* - Maximum length is 25 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 HVWR190.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="IBM.HVWR190.SMPMCS" newname="@PREFIX@.IBM.HVWR190.SMPMCS"/> <ARCHDEF archid="IBM.HVWR190.F1" newname="@PREFIX@.IBM.HVWR190.F1"/> <ARCHDEF archid="IBM.HVWR190.F2" newname="@PREFIX@.IBM.HVWR190.F2"/> <ARCHDEF archid="IBM.HVWR190.F3" newname="@PREFIX@.IBM.HVWR190.F3"/> <ARCHDEF archid="IBM.HVWR190.F4" newname="@PREFIX@.IBM.HVWR190.F4"/> <ARCHDEF archid="IBM.HVWR190.F5" newname="@PREFIX@.IBM.HVWR190.F5"/> <ARCHDEF archid="IBM.HVWR190.F6" newname="@PREFIX@.IBM.HVWR190.F6"/> <ARCHDEF archid="IBM.HVWR190.F7" newname="@PREFIX@.IBM.HVWR190.F7"/> <ARCHDEF archid="IBM.HVWR190.F8" newname="@PREFIX@.IBM.HVWR190.F8"/> <ARCHDEF archid="IBM.HVWR190.F9" newname="@PREFIX@.IBM.HVWR190.F9"/> </GIMUNZIP> //*
Customize and submit this JCL to expand the ADFzCC Japanese feature:
//EXTRACT JOB <job information> //* //* - Provide valid job card information //* - Change: //* @PREFIX@ //* ----+----1----+----2----+ //* - To your desired data set name prefix //* - Maximum length is 25 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 JVWR191.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="IBM.JVWR191.SMPMCS" newname="@PREFIX@.IBM.JVWR191.SMPMCS"/> <ARCHDEF archid="IBM.JVWR191.F1" newname="@PREFIX@.IBM.JVWR191.F1"/> <ARCHDEF archid="IBM.JVWR191.F2" newname="@PREFIX@.IBM.JVWR191.F2"/> <ARCHDEF archid="IBM.JVWR191.F3" newname="@PREFIX@.IBM.JVWR191.F3"/> <ARCHDEF archid="IBM.JVWR191.F4" newname="@PREFIX@.IBM.JVWR191.F4"/> <ARCHDEF archid="IBM.JVWR191.F5" newname="@PREFIX@.IBM.JVWR191.F5"/> <ARCHDEF archid="IBM.JVWR191.F6" newname="@PREFIX@.IBM.JVWR191.F6"/> </GIMUNZIP> //*
The following sample installation jobs are provided as part of the
product to help you install ADFzCC:
Table 18. Sample Installation Jobs -- BASE
Job Name | Job Type | Description | SMPTLIB Data Set |
---|---|---|---|
IPVWSMPE | SMP/E | Sample job to create an SMP/E environment (optional) | IBM.HVWR190.F2 |
IPVWRECV | RECEIVE | Sample SMP/E RECEIVE job | IBM.HVWR190.F2 |
IPVWALOC | ALLOCATE | Sample job to allocate target and distribution libraries | IBM.HVWR190.F2 |
IPVWDDEF | DDDEF | Sample job to define SMP/E DDDEFs | IBM.HVWR190.F2 |
IPVWAPLY | APPLY | Sample SMP/E APPLY job | IBM.HVWR190.F2 |
IPVWACPT | ACCEPT | Sample SMP/E ACCEPT job | IBM.HVWR190.F2 |
Note: When ADFzCC 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". |
Table 19. Sample Installation Jobs -- JPN
Job Name | Job Type | Description | SMPTLIB Data Set |
---|---|---|---|
IPVWRCVJ | RECEIVE | Sample SMP/E RECEIVE job | IBM.HVWR190.F2 |
IPVWALOJ | ALLOCATE | Sample job to allocate target and distribution libraries | IBM.HVWR190.F2 |
IPVWDDFJ | DDDEF | Sample job to define SMP/E DDDEFs | IBM.HVWR190.F2 |
IPVWAPLJ | APPLY | Sample SMP/E APPLY job | IBM.HVWR190.F2 |
IPVWACPJ | ACCEPT | Sample SMP/E ACCEPT job | IBM.HVWR190.F2 |
Note: When ADFzCC 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". |
The rest of this section only applies when ADFzCC is ordered
via Shopz. It does not apply when you downloaded it from the web.
Select this link to go to the next section:
"Create SMP/E environment (optional)"
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 18 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.
To copy the sample jobs for ADFzCC Base, use this JCL:
//STEP1 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //IN DD DSN=IBM.HVWR190.F2, // 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=(IPVWSMPE,IPVWRECV,IPVWALOC) SELECT MEMBER=(IPVWDDEF,IPVWAPLY,IPVWACPT) /*
To copy the sample jobs for ADFzCC JPN feature, use this JCL:
//STEP1 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //IN DD DSN=IBM.HVWR190.F2, // 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=(IPVWRCVJ,IPVWALOJ) SELECT MEMBER=(IPVWDDFJ,IPVWAPLJ,IPVWACPJ) /*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 IPVWSMPE.
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 IPVWSMPE. 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 ADFzCC as part of a CBPDO, use the RCVPDO job in the CBPDO RIMLIB data set to receive the ADFzCC 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 IPVWRECV to perform the SMP/E RECEIVE for ADFzCC. Consult the instructions in the sample job for more information.
If your order contains the Japanese feature, edit and submit sample job IPVWRCVJ to perform the SMP/E RECEIVE for that feature. 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 IPVWALOC to allocate the SMP/E target and distribution libraries for ADFzCC. Consult the instructions in the sample job for more information.
If your order contains the Japanese feature, edit and submit sample job IPVWALOJ to allocate the SMP/E target and distribution libraries for that feature. 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 IPVWDDEF to create DDDEF entries for the SMP/E target and distribution libraries for ADFzCC. Consult the instructions in the sample job for more information.
If your order contains the Japanese feature, edit and submit sample job IPVWDDFJ to create DDDEF entries for the SMP/E target and distribution libraries for that feature. 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 your order contains the Japanese feature, edit and submit sample job IPVWAPLJ to perform an SMP/E APPLY CHECK for that feature. Consult the instructions in the sample job for more information.
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 IPVWACPT to perform an SMP/E ACCEPT CHECK for ADFzCC. Consult the instructions in the sample job for more information.
If your order contains the Japanese feature, edit and submit sample job IPVWACPJ to perform an SMP/E ACCEPT CHECK for that feature. 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 ADFzCC, 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 14 (section "DASD Storage Requirements") are temporary data sets. You can delete these data sets after you complete the SMP/E install.
The publication IBM Application Delivery Foundation for z/OS Common Components Customization and User's Guide contains the necessary information to customize and use ADFzCC.
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 Application Delivery Foundation for z/OS Common Components, October 2022
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.
Thank you for your participation. above.