© Copyright International Business Machines Corporation 1992, 2022. All rights reserved.
Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp.

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 z/OS Debugger. This publication refers to IBM z/OS Debugger as z/OS Debugger.

z/OS Debugger is available as a component of multiple products. Depending on which product you acquired, different functions of z/OS Debugger will be enabled or disabled.

• IBM Developer for z/OS Enterprise Edition 16.0.0, program number 5755-A05 (Shopz orderable)
• IBM Developer for z/OS 16.0.0, program number 5724-T07 (web download)
• IBM Z and Cloud Modernization Stack 2022.3.1, program number 5900-A8N (Passport Advantage orderable)
• IBM Debug for z/OS 16.0.0, program number 5755-A06 (Shopz orderable)

The Program Directory contains the following sections:

• "Program Materials" identifies the basic program materials and documentation for z/OS Debugger.

• "Program Support" describes the IBM support available for z/OS Debugger.

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

• "Installation Requirements and Considerations" identifies the resources and considerations that are required for installing and using z/OS Debugger.

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

The rest of this section only applies when z/OS Debugger is ordered via Shopz. It does not apply when you downloaded it from the web.
Select this link to go to the next section: "z/OS Debugger Description"

Before installing z/OS Debugger, 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.

z/OS Debugger 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 z/OS Debugger are included on the CBPDO.

Do not use this program directory if you install z/OS Debugger 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.

z/OS Debugger Description

IBM z/OS Debugger helps z/OS application developers debug programs running in a variety of environments, such as batch, TSO, CICS, IMS, Db2, Db2 Stored Procedures, and z/OS UNIX System Services.

z/OS Debugger FMIDs

z/OS Debugger consists of the following FMIDs:

HADRG00

JADRG0J

The rest of this section only applies when z/OS Debugger 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:

  • z/OS Debugger Base (FMID HADRG00)

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

  • z/OS Debugger Base (FMID HADRG00)

  • z/OS Debugger Japanese (FMID JADRG0J)

Program Materials

An IBM program is identified by a program number.

z/OS Debugger is available as a component of multiple products. Depending on which product you acquired, different functions of z/OS Debugger will be enabled or disabled.

• IBM Developer for z/OS Enterprise Edition 16.0.0, program number 5755-A05 (Shopz orderable)
• IBM Developer for z/OS 16.0.0, program number 5724-T07 (web download)
• IBM Z and Cloud Modernization Stack 2022.3.1, program number 5900-A8N (Passport Advantage orderable)
• IBM Debug for z/OS 16.0.0, program number 5755-A06 (Shopz orderable)

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 z/OS Debugger. 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 z/OS Debugger 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 z/OS Debugger in the CBPDO Memo To Users Extension.

Table 1 describes the program file content for z/OS Debugger. 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 -- Japanese

Program Publications

The following sections identify the basic publications for z/OS Debugger.

Table 3 identifies the basic unlicensed program publications for z/OS Debugger. Those that are in softcopy format publications can be obtained from the IBM Publications Center website at https://www.ibm.com/resources/publications.

Table 3. Basic Material: Unlicensed Publications

Note: Requisite information can be obtained by creating a report for z/OS Debugger on https://www.ibm.com/software/reports/compatibility/clarity/index.html.

Optional Program Publications

No optional publications are provided for z/OS Debugger.

Program Source Materials

No program source materials or viewable program listings are provided for z/OS Debugger.

Publications Useful During Installation

You might want to use the publications listed in Table 4 during the installation of z/OS Debugger.

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 z/OS Debugger.

Program Services

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

Preventive Service Planning

Before you install z/OS Debugger, 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 z/OS Debugger as part of a CBPDO, HOLDDATA is included.

If the CBPDO for z/OS Debugger 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 z/OS Debugger are included in Table 5.

Table 5. PSP Upgrade and Subset ID

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 z/OS Debugger.

Table 6. Component IDs

Program and Service Level Information

This section identifies the program and relevant service levels of z/OS Debugger. 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

All resolved APARs of previous releases of z/OS Debugger have been incorporated into z/OS Debugger.

Service Level Information

No PTFs against this release of z/OS Debugger have been incorporated into the product package.

Frequently check the z/OS Debugger 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 z/OS Debugger. 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 z/OS Debugger.

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/

z/OS Debugger is installed into a file system. Before installing z/OS Debugger, you must ensure that the target system file system data sets are available for processing on the driving system. OMVS must be active on the driving system and the target system file data sets must be mounted on the driving system.

zFS must be active on the driving system. Information on activating and using zFS can be found in z/OS Distributed File Service zSeries File System Administration (SC24-5989).

Target System Requirements

This section describes the environment of the target system required to install and use z/OS Debugger.

z/OS Debugger 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.

z/OS Debugger 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.

z/OS Debugger 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.

Table 8. Target System Mandatory Operational Requisites

Note: Installation might require migration to new releases to obtain support. See https://www.ibm.com/support/lifecycle/

Conditional operational requisites identify products that are not required for this product to operate its basic functions but are required at run time for this product to operate specific functions. These products are specified as IF REQs.

Table 9 lists the required service for z/OS operational requisites. Install the appropriate PTFs according to the level of your operating system.

Table 9. Service for z/OS Operational Requisites

Table 10 lists the conditional operational requisites.

Table 10. Target System Conditional Operational Requisites

Note: Installation might require migration to new releases to obtain support. See https://www.ibm.com/support/lifecycle/

Table 11 lists the required service for conditional operational requisites. Install the appropriate PTFs according to the level of your product.

Table 11. Service for Conditional Operational Requisites

Table 12 lists old releases of conditional operational requisite products that are no longer in service.

IBM will undertake to fix any problem with z/OS Debugger that you might encounter when running z/OS Debugger with these unsupported levels. However, IBM must be able to reproduce the problem using a supported level of the same product.

If the problem can be reproduced and fixed, the fix for z/OS Debugger will be developed and tested using the supported levels of the product. If a fix is made available, it is likely to work on the unsupported product level. However, IBM cannot guarantee that the fix will work in this case.

Table 12. Out-of-support Conditional Operational Requisites

Table 13 lists the required service for the old releases of conditional operational requisite products in Table 12. Install the appropriate PTFs according to the level of your product.

Table 13. Service for out-of-support 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.

z/OS Debugger has no toleration/coexistence requisites.

Incompatibility (Negative) Requisites

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

z/OS Debugger has no negative requisites.

DASD Storage Requirements

z/OS Debugger libraries can reside on all supported DASD types.

Table 14 lists the total space that is required for each type of library.

Table 14. Total DASD Space Required by z/OS Debugger -- Base

Table 15. Total DASD Space Required by z/OS Debugger -- Japanese

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. If the value in the "ORG" column specifies "PDS", the data set must be a PDS. If the value in "DIR Blks" column specifies "N/A", the data set must be a PDSE.

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. If the value in the "Member Type" column specifies "APF", the data set must be APF-authorized.

The following figures describe the target and distribution libraries required to install z/OS Debugger. The storage requirements of z/OS Debugger 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 16. Storage Requirements for z/OS Debugger Target Libraries -- Base

• SEQALPA must be a PDS.

• SEQAAUTH, SEQAMOD, and SEQABMOD must be a PDS/E.

• SEQAMENU, SEQAPENU, and SEQASENU are ISPF libraries in mixed-case English.

• SEQAMENP, SEQAPENP, and SEQASENP are ISPF libraries in uppercase English.

• See section "Choosing a method to start z/OS Debugger Utilities" in chapter "Customizing z/OS Debugger Utilities" in the IBM z/OS Debugger Customization Guide for additional considerations if you want to merge these ISPF libraries into the common system libraries.

Table 17. Storage Requirements for z/OS Debugger Target Libraries -- Japanese

• SEQAMOD, and SEQABMOD must be a PDS/E.

• SEQAMJPN, SEQAPJPN, and SEQASJPN are ISPF libraries in Japanese.

• See section "Choosing a method to start z/OS Debugger Utilities" in chapter "Customizing z/OS Debugger Utilities" in the IBM z/OS Debugger Customization Guide for additional considerations if you want to merge these ISPF libraries into the common system libraries.

Table 18. z/OS Debugger File System Paths

Table 19. Storage Requirements for z/OS Debugger Distribution Libraries -- Base

Table 20. Storage Requirements for z/OS Debugger Distribution Libraries -- Japanese

The rest of this section only applies when z/OS Debugger 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 z/OS Debugger, but are required as input for SMP/E.

Table 21. Storage Requirements for z/OS Debugger Web Download Data Sets -- Base

Table 22. Storage Requirements for z/OS Debugger Web Download Data Sets -- Japanese

FMIDs Deleted

Installing z/OS Debugger 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 z/OS Debugger 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

Target libraries that contain load modules have some special considerations. After you have successfully installed the product, do the following steps:

• Place SEQALPA in the LPA list by adding it to an LPALSTxx member of parmlib that will be used for IPL.

• Place SEQABMOD in the link list by adding a LNKLST ADD statement for it to a PROGxx member of parmlib that will be used for IPL.

• APF-authorize SEQAAUTH, and SEQABMOD by adding APF ADD statements for them to a PROGxx member of parmlib that will be used for IPL. The other load module data sets can be APF-authorized, but it is not required.

• Ensure that the LPA, and APF-authorized data sets are access controlled. This to prevent unauthorized execution of the programs within, and to prevent programs from being added to the data sets.

• For ease of access by the users, you can place SEQAMOD in the link list by adding a LNKLST ADD statement for it to a PROGxx member of parmlib that will be used for IPL.

Installation Instructions

This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of z/OS Debugger.

Please note the following points:

• If you want to install z/OS Debugger 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 z/OS Debugger

SMP/E Considerations for Installing z/OS Debugger

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

SMP/E Options Subentry Values

The recommended values for certain SMP/E CSI subentries are shown in Table 23. 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 23. SMP/E Options Subentry Values

SMP/E CALLLIBS Processing

z/OS Debugger uses the CALLLIBS function provided in SMP/E to resolve external references during installation. When z/OS Debugger is installed, ensure that DDDEFs exist for the following libraries:

• SCEELKED
• CSSLIB
• SEZATCP

Note: CALLLIBS uses the previous DDDEFs only to resolve the link-edit for z/OS Debugger. These data sets are not updated during the installation of z/OS Debugger.

Overview of the installation steps

Overview of steps required to install IBM z/OS Debugger.

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

5. "Run REPORT MISSINGFIX (optional)"

6. "Set up ISPF Editor Macro (optional)"

7. "Create SMP/E environment (optional)"

8. "Perform SMP/E RECEIVE"

9. "Allocate SMP/E Target and Distribution Libraries"

10. "Allocate, create and mount ZFS Files (Optional)"

11. "Allocate File System Paths"

12. "Create DDDEF Entries"

13. "Perform SMP/E APPLY"

14. "Enable/Register z/OS Debugger"

15. "Run the Installation Verification Programs (IVPs)"

16. "Verify the z/OS Debugger Utilities Setup Utility Function"

17. "Perform SMP/E ACCEPT"

18. "Run REPORT CROSSZONE"

19. "Cleaning Up Obsolete Data Sets, Paths, and DDDEFs"

Allocate file system to hold web download package

This section only applies when z/OS Debugger 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 z/OS Debugger are provided as compressed files in archives HADRG00.pax.Z and JADRG0J.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 HADRG00). The size of the file system must be increased if you also include other features:

• base feature, provided in HADRG00.pax.Z: 9975 tracks

• Japanese feature, provided in JADRG0J.pax.Z: 120 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(9975  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 z/OS Debugger 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 HADRG00.readme.txt file, and JADRG0J.readme.txt if required, in text format and the HADRG00.pax.Z file, and JADRG0J.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 24. User Entered Values

Issue these commands to upload the z/OS Debugger 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:\HADRG00.readme.txt
200 Port request OK.
125 Storing data set @zfs_path@/HADRG00.readme.txt
250 Transfer completed successfully.
ftp: 20331 bytes sent in 0.01 sec. (1366.67 Kb/s)
ftp> binary
200 Representation type is Image
ftp> put d:\HADRG00.pax.Z
200 Port request OK.
125 Storing data set @zfs_path@/HADRG00.pax.Z
250 Transfer completed successfully.
ftp: 134184960 bytes sent in 1.26 sec. (1040.52 Kb/s)
ftp> quit
221 Quit command received. Goodbye.

Issue these commands to upload the z/OS Debugger 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:\JADRG0J.readme.txt
200 Port request OK.
125 Storing data set @zfs_path@/JADRG0J.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:\JADRG0J.pax.Z
200 Port request OK.
125 Storing data set @zfs_path@/JADRG0J.pax.Z
250 Transfer completed successfully.
ftp: 870912 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 z/OS Debugger 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 HADRG00.readme.txt and JADRG0J.readme.txt files uploaded in the previous step each hold a sample JCL to expand the compressed SMPMCS and RELFILEs from the uploaded HADRG00.pax.Z and JADRG0J.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 z/OS Debugger 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=BPXBATCH,REGION=0M,COND=(0,LT)
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*
//STDPARM  DD *
SH cd @zfs_path@/
;  pax -rvf HADRG00.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.HADRG00.SMPMCS"
         newname="@PREFIX@.IBM.HADRG00.SMPMCS"/>
<ARCHDEF archid="IBM.HADRG00.F1"
         newname="@PREFIX@.IBM.HADRG00.F1"/>
<ARCHDEF archid="IBM.HADRG00.F2"
         newname="@PREFIX@.IBM.HADRG00.F2"/>
<ARCHDEF archid="IBM.HADRG00.F3"
         newname="@PREFIX@.IBM.HADRG00.F3"/>
<ARCHDEF archid="IBM.HADRG00.F4"
         newname="@PREFIX@.IBM.HADRG00.F4"/>
<ARCHDEF archid="IBM.HADRG00.F5"
         newname="@PREFIX@.IBM.HADRG00.F5"/>
<ARCHDEF archid="IBM.HADRG00.F6"
         newname="@PREFIX@.IBM.HADRG00.F6"/>
<ARCHDEF archid="IBM.HADRG00.F7"
         newname="@PREFIX@.IBM.HADRG00.F7"/>
<ARCHDEF archid="IBM.HADRG00.F8"
         newname="@PREFIX@.IBM.HADRG00.F8"/>
<ARCHDEF archid="IBM.HADRG00.F9"
         newname="@PREFIX@.IBM.HADRG00.F9"/>
<ARCHDEF archid="IBM.HADRG00.F10"
         newname="@PREFIX@.IBM.HADRG00.F10"/>
<ARCHDEF archid="IBM.HADRG00.F11"
         newname="@PREFIX@.IBM.HADRG00.F11"/>
</GIMUNZIP>
//*

Customize and submit this JCL to expand the z/OS Debugger 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=BPXBATCH,REGION=0M,COND=(0,LT)
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*
//STDPARM  DD *
SH cd @zfs_path@/
;  pax -rvf JADRG0J.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.JADRG0J.SMPMCS"
         newname="@PREFIX@.IBM.JADRG0J.SMPMCS"/>
<ARCHDEF archid="IBM.JADRG0J.F1"
         newname="@PREFIX@.IBM.JADRG0J.F1"/>
<ARCHDEF archid="IBM.JADRG0J.F2"
         newname="@PREFIX@.IBM.JADRG0J.F2"/>
<ARCHDEF archid="IBM.JADRG0J.F3"
         newname="@PREFIX@.IBM.JADRG0J.F3"/>
<ARCHDEF archid="IBM.JADRG0J.F4"
         newname="@PREFIX@.IBM.JADRG0J.F4"/>
<ARCHDEF archid="IBM.JADRG0J.F5"
         newname="@PREFIX@.IBM.JADRG0J.F5"/>
<ARCHDEF archid="IBM.JADRG0J.F6"
         newname="@PREFIX@.IBM.JADRG0J.F6"/>
</GIMUNZIP>
//*

Sample Jobs

The following sample installation jobs are provided as part of the product to help you install z/OS Debugger:

Table 25. Sample Installation Jobs -- BASE

Table 26. Sample Installation Jobs -- Japanese

The rest of this section only applies when z/OS Debugger is ordered via Shopz. It does not apply when you downloaded it from the web.
Select this link to go to the next section: "Run REPORT MISSINGFIX (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 25 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 z/OS Debugger Base, use this JCL:

//STEP1    EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//IN       DD DSN=IBM.HADRG00.F1,
//            DISP=SHR,
//*           VOL=SER=filevol,
//            UNIT=SYSALLDA
//OUT      DD DSNAME=jcl-library-name,
//            DISP=(NEW,CATLG,DELETE),
//            SPACE=(TRK,(15,5,5)),
//            DSNTYPE=LIBRARY,
//*           VOL=SER=dasdvol,
//            UNIT=SYSALLDA
//SYSUT3   DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSIN    DD *
    COPY INDD=IN,OUTDD=OUT
    SELECT MEMBER=(EQAWEDIT,EQAWSMPE,EQAWRECV,EQAWALOC)
    SELECT MEMBER=(EQAWDDEF,EQAWAPLY,EQAWACPT,EQAWRPXZ)
    SELECT MEMBER=(EQAWZFS,EQAWMKD,EQAWMNT,EQAWMKDR)
//*

To copy the sample jobs for z/OS Debugger Japanese feature, use this JCL:

//STEP1    EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//IN       DD DSN=IBM.JADRG0J.F1,
//            DISP=SHR,
//*           VOL=SER=filevol,
//            UNIT=SYSALLDA
//OUT      DD DSNAME=jcl-library-name,
//            DISP=(NEW,CATLG,DELETE),
//            SPACE=(TRK,(15,5,5)),
//            DSNTYPE=LIBRARY,
//*           VOL=SER=dasdvol,
//            UNIT=SYSALLDA
//SYSUT3   DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSIN    DD *
    COPY INDD=IN,OUTDD=OUT
    SELECT MEMBER=(EQAWEDIJ,EQAWRECJ,EQAWALOJ)
    SELECT MEMBER=(EQAWDEFJ,EQAWAPLJ,EQAWACPJ)
//*

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.

Run REPORT MISSINGFIX (optional)

The SMP/E REPORT MISSINGFIX command helps you determine whether any FIXCAT PTFs exist that are applicable and have not yet been installed. If you find that there are PTFs that need to be installed, we recommend that you install them, before installing z/OS Debugger.

Before you install z/OS Debugger, it is recommended that you run REPORT MISSINGFIX. This requires a global zone with ZONEINDEX entries that describe all the target and distribution libraries to be reported on, and the SET BOUNDARY command must specify the global zone.

Here is a sample REPORT MISSINGFIX command to run against your z/OS CSI:

SET BDY(globalzone).
REPORT MISSINGFIX ZONES(targetzone) FIXCAT(IBM.z/OS.Debugger).

For more information about REPORT MISSINGFIX, see the SMP/E manuals.

Set up ISPF Editor Macro (optional)

An ISPF editor macro is provided to aid you in making changes to z/OS Debugger SMP/E installation jobs. The macro lets you substitute proper values for all of the required variables in those jobs instead of having you make the changes repeatedly by hand.

• EQAWEDIT, provided with the SMP/E jobs for the base product, updates the SMP/E jobs for the base product:
  EQAWSMPE, EQAWRECV, EQAWALOC, EQAWZFS, EQAWMKD, EQAWDDEF, EQAWAPLY, EQAWACPT

• EQAWEDIJ, provided with the SMP/E jobs for the Japanese feature, updates the SMP/E jobs for the base product and the Japanese feature:
  EQAWSMPE, EQAWRECV, EQAWALOC, EQAWZFS, EQAWMKD, EQAWDDEF, EQAWAPLY, EQAWACPT,
  EQAWRECJ, EQAWALOJ, EQAWDEFJ, EQAWAPLJ, EQAWACPJ

Edit the macro and provide the proper values. Consult the instructions in the macro for more information.

After making the changes, either copy the macro to any data set in your TSO logon procedure SYSEXEC concatenation, or issue the commands below to make the macro immediately accessible to your current ISPF session:

From ISPF option 6, issue:
 
ALLOCATE FI(SYSUEXEC) DA('dsn') SHR REU
  where dsn is the data set holding the macro
ALTLIB ACTIVATE USER(EXEC)

Consult the instructions in the macro on how to invoke it.

Create SMP/E environment (optional)

If you are using an existing CSI, do not run the sample job EQAWSMPE.

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 EQAWSMPE. 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 z/OS Debugger as part of a CBPDO, use the RCVPDO job in the CBPDO RIMLIB data set to receive the z/OS Debugger 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 EQAWRECV to perform the SMP/E RECEIVE for z/OS Debugger. Consult the instructions in the sample job for more information.

If your order contains the Japanese feature, edit and submit sample job EQAWRECJ 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 EQAWALOC to allocate the SMP/E target and distribution libraries for z/OS Debugger. Consult the instructions in the sample job for more information.

If your order contains the Japanese feature, edit and submit sample job EQAWALOJ 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.

Allocate, create and mount ZFS Files (Optional)

This job allocates, creates a mountpoint, and mounts zFS data sets.

If you plan to install z/OS Debugger into a new z/OS UNIX file system, you can edit and submit the optional EQAWZFS job to perform the following tasks:

• Create the z/OS UNIX file system
• Create a mountpoint
• Mount the z/OS UNIX file system on the mountpoint

The recommended z/OS UNIX file system type is zFS. The recommended mountpoint is /usr/lpp/IBM/debug.

Before running the sample job to create the z/OS UNIX file system, you must ensure that OMVS is active on the driving system. zFS must be active on the driving system if you are installing z/OS Debugger into a file system that is zFS.

If you create a new file system for this product, consider updating the BPXPRMxx PARMLIB member to mount the new file system at IPL time. This action can be helpful if an IPL occurs before the installation is completed.

MOUNT FILESYSTEM('#dsn')
 MOUNTPOINT('/usr/lpp/IBM/debug')
 MODE(RDWR)        /* can be MODE(READ) */
 TYPE(ZFS) PARM('AGGRGROW') /* zFS, with extents */

See the following information to update the statements in the previous sample:

#dsn is the name of the data set holding the z/OS UNIX file system.

/usr/lpp/IBM/debug is the name of the mountpoint where the z/OS UNIX file system will be mounted.

Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.

Allocate File System Paths

The target file system data set must be mounted on the driving system when running the sample EQAWMKD job since the job will create paths in the file system.

Before running the sample job to create the paths in the file system, you must ensure that OMVS is active on the driving system and that the target system's file system is mounted to the driving system. zFS must be active on the driving system.

If you plan to install z/OS Debugger into a new file system, you must create the mountpoint and mount the new file system to the driving system for z/OS Debugger.

The recommended mountpoint is /usr/lpp/IBM/debug.

Edit and submit sample job EQAWMKD to allocate the file system paths for z/OS Debugger. Consult the instructions in the sample job for more information.

If you create a new file system for this product, consider updating the BPXPRMxx PARMLIB member to mount the new file system at IPL time. This action can be helpful if an IPL occurs before the installation is completed.

Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.

Create DDDEF Entries

Edit and submit sample job EQAWDDEF to create DDDEF entries for the SMP/E target and distribution libraries for z/OS Debugger. Consult the instructions in the sample job for more information.

If your order contains the Japanese feature, edit and submit sample job EQAWDEFJ 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 EQAWAPLY to perform an SMP/E APPLY CHECK for z/OS Debugger. Consult the instructions in the sample job for more information.

   If your order contains the Japanese feature, edit and submit sample job EQAWAPLJ 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 http://service.software.ibm.com/holdata/390holddata.html. The latest HOLDDATA may identify HIPER and FIXCAT APARs for the FMIDs you will be installing. An APPLY CHECK will help you determine if any HIPER or FIXCAT APARs are applicable to the FMIDs you are installing. If there are any applicable HIPER or FIXCAT APARs, the APPLY CHECK will also identify fixing PTFs that will resolve the APARs, if a fixing PTF is available.

   You should install the FMIDs regardless of the status of unresolved HIPER or FIXCAT APARs. However, do not deploy the software until the unresolved HIPER and FIXCAT APARs have been analyzed to determine their applicability. That is, before deploying the software either ensure fixing PTFs are applied to resolve all HIPER or FIXCAT APARs, or ensure the problems reported by all HIPER or FIXCAT APARs are not applicable to your environment.

   To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the PRE, ID, REQ, and IFREQ on the APPLY CHECK. The SMP/E root cause analysis identifies the cause only of errors and not of warnings (SMP/E treats bypassed PRE, ID, REQ, and IFREQ conditions as warnings, instead of errors).

   Here are sample APPLY commands:

   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)
      FIXCAT(IBM.z/OS.Debugger)
      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.

      You can also include BYPASS(HOLDFIXCAT) to indicate that the held APARs associated with the specified fix category reason IDs, like IBM.z/OS.Debugger, should not be held. If a list of fix category reason IDs is not included, all fix category reason IDs are bypassed.

      APPLY S(fmid,fmid,...) CHECK
      FORFMID(fmid,fmid,...)
      SOURCEID(RSU*)
      FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE)
      FIXCAT(IBM.z/OS.Debugger)
      GROUPEXTEND
      BYPASS(HOLDCLASS(HIPER),HOLDFIXCAT) .
       ..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.

Enable/Register z/OS Debugger

Run the Installation Verification Programs (IVPs)

z/OS Debugger is available as a component of multiple products. Depending on which product you acquired, z/OS Debugger might only offer access via a GUI interface that is part of the workstation client. This implies that in this situation, you cannot run the 3270-based IVPs listed here, except EQAWIVPB. EQAWIVPB has instructions describing how to run it in remote mode (rather than full-screen using the Terminal Interface Manager).

• IBM Developer for z/OS Enterprise Edition 16.0.0, program number 5755-A05, can run all IVPs
• IBM Developer for z/OS 16.0.0, program number 5724-T07, can run only EQAWIVPB
• IBM Z and Cloud Modernization Stack 2022.3.1, program number 5900-A8N, can run only EQAWIVPB
• IBM Debug for z/OS 16.0.0, program number 5755-A06, can run all IVPs

Some IVPs require that certain PTFs be applied before you can successfully run them. To find the requisite PTFs, run the REPORT CROSSZONE job as shown in section "Run REPORT CROSSZONE".

Some IVPs also require certain customization to the product before you can successfully run them. See the specific information in each table below.

Depending on the compiler languages (COBOL, C, PL/I, or assembler) that your site uses, you can run one or all of the IVPs. Consult the instructions in each IVP for the expected return code and output. All of the IVPs are in the SEQASAMP library.

Table 27 lists the IVPs for batch mode.

Table 27. z/OS Debugger IVPs for Batch Mode

Table 28 lists the IVPs for full-screen mode using the Terminal Interface Manager.

Table 28. z/OS Debugger IVPs for Full-screen Mode using the Terminal Interface Manager

Table 29 lists the IVPs for running under CICS in full-screen mode.

Table 29. z/OS Debugger IVPs for Running under CICS in Full-screen Mode

Table 30 lists the IVPs for z/OS Debugger Code Coverage.

Table 30. z/OS Debugger IVPs for z/OS Debugger Code Coverage

Verify the z/OS Debugger Utilities Setup Utility Function

You can verify the installation and customization of the z/OS Debugger Utilities Setup Utility function by following one (or more) of the samples described in "Appendix C. Examples: Preparing programs and modifying setup files with z/OS Debugger Utilities" in the IBM z/OS Debugger User's Guide.

See "Customizing z/OS Debugger Utilities" in the IBM z/OS Debugger Customization Guide first for customization information.

Perform SMP/E ACCEPT

Edit and submit sample job EQAWACPT to perform an SMP/E ACCEPT CHECK for z/OS Debugger. Consult the instructions in the sample job for more information.

If your order contains the Japanese feature, edit and submit sample job EQAWACPJ 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 z/OS Debugger, 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 21 (section "DASD Storage Requirements") are temporary data sets. You can delete these data sets after you complete the SMP/E install.

The following data sets, which were allocated and used by previous releases of this product, are no longer used in this release. You can delete these obsolete data sets after you delete the previous release from your system.

• AEQABIN: obsolete as of Debug Tool 13.1.

• SEQABIN: obsolete as of Debug Tool 13.1.

• LPALIB is no longer required as of Debug Tool 4.1. However, if you install z/OS Debugger in a zone that currently contains an old release that has an LPALIB, ensure that you leave the old LPALIB allocated so that SMP/E can perform the proper cleanup. After you complete the installation of z/OS Debugger 16.0.0, do not delete this data set as it may contain other products' modules.

• SEQALPA, which was obsolete as of Debug Tool 1.3, is now required as of Debug Tool 4.1.

• AEQAMLIB, AEQAPLIB, AEQASLIB: obsolete as of Debug Tool 3.1.

• SEQAMLIB, SEQAPLIB, SEQASLIB: obsolete as of Debug Tool 3.1.

• SEQACLIS, SEQADUM, SEQAIENU, SEQALPA, SEQAOS2, SEQAPROC, SEQA2ENU: obsolete as of Debug Tool 1.3.

• AEQACLIS, AEQAIENU, AEQAMOD2, AEQAOS2, AEQASRC2, AEQA2ENU: obsolete as of Debug Tool 1.3.

The following DDDEF entries, which were created and used by previous releases of this product, are no longer used in this release. You can delete these obsolete DDDEF entries after you delete the previous release from your system.

• AEQABIN: obsolete as of Debug Tool 13.1.

• SEQABIN: obsolete as of Debug Tool 13.1.

• LPALIB is no longer required as of Debug Tool 4.1. However, if you install z/OS Debugger in a zone that currently contains an old release that has an LPALIB, ensure that you leave the old LPALIB allocated so that SMP/E can perform the proper cleanup. After you complete the installation of z/OS Debugger 16.0.0, do not delete this data setas it may contain other products' modules.

• SEQALPA, which was obsolete as of Debug Tool 1.3, is now required as of Debug Tool 4.1.

• AEQAMLIB, AEQAPLIB, AEQASLIB: obsolete as of Debug Tool 3.1.

• SEQAMLIB, SEQAPLIB, SEQASLIB: obsolete as of Debug Tool 3.1.

• SEQACLIS, SEQADUM, SEQAIENU, SEQALPA, SEQAOS2, SEQAPROC, SEQA2ENU: obsolete as of Debug Tool 1.3.

• AEQACLIS, AEQAIENU, AEQAMOD2, AEQAOS2, AEQASRC2, AEQA2ENU: obsolete as of Debug Tool 1.3.

Product Customization

The publication IBM z/OS Debugger Customization Guide contains the necessary information to customize and use z/OS Debugger.

The publication IBM z/OS Debugger User's Guide contains information on possible compilation and link edit changes you may need to make to your build processes in order to debug your programs with z/OS Debugger.

A workstation client is required for some of the products that include z/OS Debugger. The workstation client is optional otherwise. The client is part of the product you acquired. A trial version of the client can be downloaded from the Mainframe DEV download page, https://developer.ibm.com/mainframe/products/downloads/.

• IBM Developer for z/OS Enterprise Edition 16.0.0, program number 5755-A05, client is optional
• IBM Developer for z/OS 16.0.0, program number 5724-T07, client is required
• IBM Z and Cloud Modernization Stack 2022.3.1, program number 5900-A8N, client is required
• IBM Debug for z/OS 16.0.0, program number 5755-A06, client is optional

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 z/OS Debugger, 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.