© 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.

Table of Contents

Figures

Introduction

Program Materials

Program Support

Program and Service Level Information

Installation Requirements and Considerations

Installation Instructions

Notices

Reader's Comments

Figures

Introduction

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:

• "Program Materials" identifies the basic program materials and documentation for ADFzCC.

• "Program Support" describes the IBM support available for ADFzCC.

• "Program and Service Level Information" lists the APARs (program level) and PTFs (service level) that have been incorporated into ADFzCC.

• "Installation Requirements and Considerations" identifies the resources and considerations that are required for installing and using ADFzCC.

• "Installation Instructions" provides detailed installation instructions for ADFzCC. It also describes the procedures for activating the functions of ADFzCC, or refers to appropriate publications.

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.

ADFzCC Description

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 Performance Analyzer for z/OS

IBM Fault Analyzer for z/OS

IBM File Manager for z/OS

IBM Debug for z/OS

IBM Developer for z/OS

IBM Developer for z/OS Enterprise Edition

IBM Application Delivery Foundation for z/OS Common Components 1.9.0 now provides TLS 1.3 support in the Common Server.

ADFzCC FMIDs

ADFzCC consists of the following FMIDs:

HVWR190

JVWR191

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:

• If you order only the base feature, you will receive the following materials:

  • ADFzCC Base (FMID HVWR190)

• If you order both the base and Japanese features, you will receive the following materials:

  • ADFzCC Base and JPN (FMID HVWR190)

  • ADFzCC JPN (FMID JVWR191)

Program 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.

Basic Machine-Readable Material

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:

1. The data set attributes in this table must be used in the JCL of jobs that read the data sets. However, because the data sets are in IEBCOPY unloaded format, their actual attributes might be different.

2. If any RELFILEs are identified as PDSEs, ensure that SMPTLIB data sets are allocated as PDSEs.

Table 1. Program File Content -- Base

Table 2. Program File Content -- JPN

Program Publications

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

Optional Program Publications

No optional publications are provided for ADFzCC.

Program Source Materials

No program source materials or viewable program listings are provided for ADFzCC.

Publications Useful During Installation

You might want to use the publications listed in Table 4 during the installation of ADFzCC.

Table 4. Publications Useful During Installation

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

Program Support

This section describes the IBM support available for ADFzCC.

Program Services

Contact your IBM representative for specific information about available program services.

Preventive Service Planning

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

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

Statement of Support Procedures

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.

Table 6. Component IDs

Program and Service Level Information

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.

Program Level Information

The following APAR fixes against previous releases of ADFzCC have been incorporated into this release. They are listed by FMID.

• FMID HVWR190
  
  PH00357 PH00651 PH01565 PH02012 PH02298 PH03338 PH03562 PH04064 PH05040 PH05271 PH05851 PH06407 PH07617 PH07618 PH08662 PH09231 PH09364 PH09880 PH12369 PH12483 PH12926 PH14694 PH16201 PH17036 PH17561 PH18736 PH19128 PH20368 PH20536 PH20609 PH23356 PH23513 PH24548 PH27164 PH27221 PH28163 PH29008 PH29059 PH29671 PH31652 PH31966 PH32482 PH32485 PH32670 PH34783 PH34950 PH35012 PH35686 PH36152 PH36345 PH36693 PH36745 PH36876 PH37670 PH38401 PH39416 PH40197 PH40404 PH41316 PH41317 PH42425 PH42464 PH43709 PH44200 PH46546 PH47067 PH47117 PH47118 PH47838 PH48069 PI21149 PI54400 PI90002 PI91210 PI91469 PI92117 PI94511 PI94558 PI95412 PI96342 PI97749 PI97779 PI99052 PI99337

   

Service Level Information

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.

Installation Requirements and Considerations

The following sections identify the system requirements for installing and activating ADFzCC. The following terminology is used:

• Driving system: the system on which SMP/E is executed to install the program.

  The program might have specific operating system or product level requirements for using processes, such as binder or assembly utilities during the installation.

• Target system: the system on which the program is configured and run.

  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:

• When you install a new level of a product that is already installed, the new level of the product will replace the old one. By installing the new level onto a separate target system, you can test the new level and keep the old one in production at the same time.

• When you install a product that shares libraries or load modules with other products, the installation can disrupt the other products. By installing the product onto a separate target system, you can assess these impacts without disrupting your production system.

Driving System Requirements

This section describes the environment of the driving system required to install ADFzCC.

Machine Requirements

The driving system can run in any hardware environment that supports the required software.

Programming Requirements

Table 7. Driving System Software Requirements

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/

Target System Requirements

This section describes the environment of the target system required to install and use ADFzCC.

ADFzCC installs in the z/OS (Z038) SREL.

Machine Requirements

The target system can run in any hardware environment that supports the required software.

Programming Requirements

Installation Requisites

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

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

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.

Incompatibility (Negative) Requisites

Negative requisites identify products that must not be installed on the same system as this product.

ADFzCC has no negative requisites.

DASD Storage Requirements

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

Table 9. Total DASD Space Required by ADFzCC -- JPN

Notes:

1. For non-RECFM U data sets, IBM recommends using system-determined block sizes for efficient DASD utilization. For RECFM U data sets, IBM recommends using a block size of 32760, which is most efficient from the performance and DASD utilization perspective.

2. Abbreviations used for data set types are shown as follows.

   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".

3. All target and distribution libraries listed have the following attributes:
   • The default name of the data set can be changed.
   • The default block size of the data set can be changed.
   • The data set can be merged with another data set that has equivalent characteristics.
   • The data set can be either a PDS or a PDSE, with some exceptions. The exceptions are listed after the table.

4. All target libraries listed have the following attributes:
   • These data sets can be SMS-managed, but they are not required to be SMS-managed.
   • These data sets are not required to reside on the IPL volume.
   • The values in the "Member Type" column are not necessarily the actual SMP/E element types that are identified in the SMPMCS.

5. All target libraries that are listed and contain load modules have the following attributes:
   • These data sets can not be in the LPA, with some exceptions. If the value in the "Member Type" column specifies "LPA", it is advised to place the data set in the LPA.
   • These data sets can be in the LNKLST.
   • These data sets are not required to be APF-authorized, with some exceptions. The exceptions are listed after the table.
   • Check your SMPLTS allocation if the table indicates that a load library ("RECFM" column specifies U) must be a PDSE ("DIR Blks" column specifies N/A). If you have an existing SMPLTS, and it is a PDS, you must allocate a new PDSE and copy your SMPLTS into it; then change the SMPLTS DDDEF entry to indicate the new PDSE data set.

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

• SIPVLPA1 must be a PDS.

• SIPVMODA must be a PDSE.

• SIPVMOD1 must be a PDSE.

• SIPVMODA must be APF authorized.

Table 11. Storage Requirements for ADFzCC Target Libraries -- JPN

Table 12. Storage Requirements for ADFzCC Distribution Libraries -- Base

• AIPVLPA1 must be a PDS.

• AIPVMODA must be a PDSE.

• AIPVMOD1 must be a PDSE.

Table 13. Storage Requirements for ADFzCC Distribution Libraries -- JPN

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

• hlq.IBM.HVWR190.F3, and hlq.IBM.HVWR190.F9 must be a PDS.

• hlq.IBM.HVWR190.F7, and hlq.IBM.HVWR190.F8 must be a PDSE.

Table 15. Storage Requirements for ADFzCC Web Download Data Sets -- JPN

• hlq.IBM.JVWR191.F2 must be a PDS.

• hlq.IBM.JVWR191.F6 must be a PDSE.

FMIDs Deleted

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.

Special Considerations

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.

Installation Instructions

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:

• If you want to install ADFzCC into its own SMP/E environment, consult the SMP/E manuals for instructions on creating and initializing the SMPCSI and the SMP/E control data sets.

• You can use the sample jobs that are provided to perform part or all of the installation tasks. The SMP/E jobs assume that all DDDEF entries that are required for SMP/E execution have been defined in appropriate zones.

• You can use the SMP/E dialogs instead of the sample jobs to accomplish the SMP/E installation steps.

Installing ADFzCC

SMP/E Considerations for Installing ADFzCC

Use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install this release of ADFzCC.

SMP/E Options Subentry Values

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

Overview of the installation steps

Overview of steps required to install IBM Application Delivery Foundation for z/OS Common Components.

1. Allocate file system to hold web download package
   (only applicable for web download, not Shopz orders)

2. Upload the web download package to the host
   (only applicable for web download, not Shopz orders)

3. Extract and expand the compressed SMPMCS and RELFILEs
   (only applicable for web download, not Shopz orders)

   Select this link to skip the web download specific steps: "Sample Jobs"

4. Create SMP/E environment (optional)

5. Perform SMP/E RECEIVE

6. Allocate SMP/E target and distribution libraries

7. Create DDDEF entries

8. Perform SMP/E APPLY

9. Enable/Register ADFzCC

10. Remove old registrations

11. Run the Installation Verification Programs (IVPs)

12. Verify the ADFzCC Utilities Setup Utility Function

13. Perform SMP/E ACCEPT

14. Run REPORT CROSSZONE

Allocate file system to hold web download package

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:

• Base feature, provided in HVWR190.pax.Z: 375 tracks

• Japanese feature, provided in JVWR191.pax.Z: 18 tracks

//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.

Upload the web download package to the host

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:

Table 17. User Entered Values

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.

Extract and expand the compressed SMPMCS and RELFILEs

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.

• @zfs_path@ matches the variable you specified in the previous step.

• If the 'oshell' command gets a RC=256 and message "pax: checksum error on tape (got ee2e, expected 0)", then the archive file was not uploaded to the host in binary format.

• GIMUNZIP allocates data sets to match the definitions of the original data sets. You may encounter errors if your SMS ACS routines alter the attributes used by GIMUNZIP. If this occurs, specify a non-SMS managed volume for the GIMUNZIP allocation of the data sets. For example:
  <ARCHDEF archid="..."
  storclas="storage_class" volume="data_set_volume"
  newname="..."/>

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>
//*

Sample Jobs

The following sample installation jobs are provided as part of the product to help you install ADFzCC:

Table 18. Sample Installation Jobs -- BASE

Table 19. Sample Installation Jobs -- JPN

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)
/*

IN:

filevol is the volume serial of the DASD device where the downloaded files reside.

OUT:

jcl-library-name is the name of the output data set where the sample jobs are stored.

dasdvol is the volume serial of the DASD device where the output data set resides. Uncomment the statment if a volume serial must be provided.

Create SMP/E environment (optional)

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.

Perform SMP/E RECEIVE

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.

Allocate SMP/E Target and Distribution Libraries

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.

Create DDDEF Entries

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.

Perform SMP/E APPLY

1. Ensure that you have the latest HOLDDATA; then edit and submit sample job IPVWAPLY to perform an SMP/E APPLY 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 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:

   1. To ensure that all recommended and critical service is installed with the FMIDs, receive the latest HOLDDATA and use the APPLY CHECK command as follows

      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.

   2. To install the FMIDs without regard for unresolved HIPER APARs, you can add the BYPASS(HOLDCLASS(HIPER)) operand to the APPLY CHECK command. This will allow you to install FMIDs even though one or more unresolved HIPER APARs exist. After the FMIDs are installed, use the SMP/E REPORT ERRSYSMODS command to identify unresolved HIPER APARs and any fixing PTFs.

      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.

2. After you take actions that are indicated by the APPLY CHECK, remove the CHECK operand and run the job again to perform the APPLY.

   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.

Perform SMP/E ACCEPT

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.

Run REPORT CROSSZONE

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.

Cleaning Up Obsolete Data Sets, Paths, and DDDEFs

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.

Product Customization

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.

Notices

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

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Trademarks

IBM, 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.

Reader's Comments

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:

1. Your name and address

2. Your email address

3. Your telephone or fax number

4. The publication title and order number

5. The topic and page number related to your comment

6. The text of your comment

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.