Program Directory for
IBM z/OS Debugger

V14.0.0

Program Number 5724-T07, 5655-AC5, 5655-Q50

FMIDs HADRE00, JADRE0J, JADRE0K

for Use with
z/OS V01.13.00 or later

Document Date: September 2016

GI13-4540-00

 
Note

Before using this information and the product it supports, be sure to read the general information under "Notices".

A form for reader's comments appears at the back of this publication. 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.

© Copyright International Business Machines Corporation 1992, 2016. 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

  • z/OS Debugger Description
  • z/OS Debugger FMIDs
  • Program Materials

  • Basic Machine-Readable Material
  • Optional Machine-Readable Material
  • Program Publications
  • Optional Program Publications
  • Program Source Materials
  • Publications Useful During Installation
  • Program Support

  • Program Services
  • Preventive Service Planning
  • Statement of Support Procedures
  • Program and Service Level Information

  • Program Level Information
  • Service Level Information
  • Installation Requirements and Considerations

  • Driving System Requirements
  • Machine Requirements
  • Programming Requirements
  • Target System Requirements
  • Machine Requirements
  • Programming Requirements
  • DASD Storage Requirements
  • FMIDs Deleted
  • Special Considerations
  • Installation Instructions

  • Installing z/OS Debugger
  • SMP/E Considerations for Installing z/OS Debugger
  • SMP/E Options Subentry Values
  • SMP/E CALLLIBS Processing
  • Overview of the installation steps
  • Allocate sequential data sets to hold SMPMCS and compressed RELFILEs
  • Upload the SMPMCS and compressed RELFILEs to the host
  • Expand the compressed RELFILEs with TSO RECEIVE
  • Sample Jobs
  • Set up ISPF Editor Macro (optional)
  • Create SMP/E environment (optional)
  • Perform SMP/E RECEIVE
  • Allocate SMP/E Target and Distribution Libraries
  • Create DDDEF Entries
  • Perform SMP/E APPLY
  • Enable/Register z/OS Debugger
  • Remove old registrations
  • Run the Installation Verification Programs (IVPs)
  • Verify the z/OS Debugger Utilities Setup Utility Function
  • Perform SMP/E ACCEPT
  • Run REPORT CROSSZONE
  • Cleaning Up Obsolete Data Sets, Paths, and DDDEFs
  • Product Customization
  • Product FMIDs
  • Notices

  • Trademarks
  • 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.

    The Program Directory contains the following sections:

    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; then keep them for future 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 tape 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 tape.

    Do not use this program directory if you install z/OS Debugger with a SystemPac or ServerPac. When you use one of those offerings, use the jobs and documentation supplied with the offering. The offering will point you to specific sections of this program directory as needed.


    z/OS Debugger Description

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


    z/OS Debugger FMIDs

    z/OS Debugger consists of the following FMIDs:

    HADRE00
    JADRE0J
    JADRE0K

    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:


    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.

    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: "Optional Machine-Readable Material"

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

    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
    Name O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    BLK
    SIZE
    SMPMCS SEQ FB 80 8800
    IBM.HADRE00.F1 PDSE FB 80 8800
    IBM.HADRE00.F2 PDSE FB 80 8800
    IBM.HADRE00.F3 PDSE U 0 6144
    IBM.HADRE00.F4 PDSE FB 80 8800
    IBM.HADRE00.F5 PDSE FB 80 8800
    IBM.HADRE00.F6 PDSE FB 80 8800
    IBM.HADRE00.F7 PDSE FB 80 8800
    IBM.HADRE00.F8 PDSE FB 80 8800
    IBM.HADRE00.F9 PDSE FB 80 8800
    IBM.HADRE00.F10 PDSE FB 80 8800

    Table 2. Program File Content -- JPN
    Name O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    BLK
    SIZE
    SMPMCS SEQ FB 80 8800
    IBM.JADRE0J.F1 PDSE FB 80 8800
    IBM.JADRE0J.F2 PDSE FB 80 8800
    IBM.JADRE0J.F3 PDSE U 0 6144
    IBM.JADRE0J.F4 PDSE FB 80 8800
    IBM.JADRE0J.F5 PDSE FB 80 8800
    IBM.JADRE0J.F6 PDSE FB 80 8800

    Table 3. Program File Content -- KOR
    Name O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    BLK
    SIZE
    SMPMCS SEQ FB 80 8800
    IBM.JADRE0K.F1 PDSE FB 80 8800
    IBM.JADRE0K.F2 PDSE FB 80 8800
    IBM.JADRE0K.F3 PDSE U 0 6144
    IBM.JADRE0K.F4 PDSE FB 80 8800
    IBM.JADRE0K.F5 PDSE FB 80 8800
    IBM.JADRE0K.F6 PDSE FB 80 8800


    Optional Machine-Readable Material

    No optional machine-readable materials are provided for z/OS Debugger.


    Program Publications

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

    Table 4 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 http://www.ibm.com/shop/publications/order/.

    Table 4. Basic Material: Unlicensed
    Publication Title Form Number Media Format
    IBM z/OS Debugger Users Guide SC27-8932 http://www-01.ibm.com/support /docview.wss?uid=swg27048563
    IBM z/OS Debugger Reference Summary SC27-8933 http://www-01.ibm.com/support /docview.wss?uid=swg27048563
    IBM z/OS Debugger Reference and Messages SC27-8934 http://www-01.ibm.com/support /docview.wss?uid=swg27048563
    IBM z/OS Debugger Customization Guide SC27-8935 http://www-01.ibm.com/support /docview.wss?uid=swg27048563
    IBM z/OS Debugger Coverage Utility Users Guide and Messages SC27-8936 http://www-01.ibm.com/support /docview.wss?uid=swg27048563
    IBM z/OS Debugger API Users Guide and Reference SC27-8937 http://www-01.ibm.com/support /docview.wss?uid=swg27048563
    Note:

    • Requisite information can be obtained from the "System Requirements" tab on the z/OS Debugger home page, http://www-03.ibm.com/software /products/en/developer-for-z-systems.

    • Additional publications can be obtained from the z/OS Debugger online library, http://www-01.ibm.com/support /docview.wss?uid=swg27048563.

    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 5 during the installation of z/OS Debugger.

    Table 5. Publications Useful During Installation
    Publication Title Form Number Media Format
    IBM SMP/E for z/OS User's Guide SA22-7773 http://www.ibm.com/shop/
    publications/order/
    IBM SMP/E for z/OS Commands SA22-7771 http://www.ibm.com/shop/
    publications/order/
    IBM SMP/E for z/OS Reference SA22-7772 http://www.ibm.com/shop/
    publications/order/
    IBM SMP/E for z/OS Messages, Codes, and Diagnosis GA22-7770 http://www.ibm.com/shop/
    publications/order/


    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:

    http://www14.software.ibm.com/webapp/set2/psearch/search?domain=psp

    You can also use S/390 SoftwareXcel or contact the IBM Support Center to obtain the latest PSP Bucket information.

    For program support, access the Software Support Website at http://www-01.ibm.com/software/support/.

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

    Table 6. PSP Upgrade and Subset ID
    UPGRADE SUBSET Description
    DEBUGE00 HADRE00 z/OS Debugger Base
    DEBUGE00 JADRE0J z/OS Debugger JPN
    DEBUGE00 JADRE0K z/OS Debugger KOR


    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 7 identifies the component IDs (COMPID) for z/OS Debugger.

    Table 7. Component IDs
    FMID COMPID Component Name RETAIN
    Release
    HADRE00 5724T0713 z/OS Debugger Base E00
    JADRE0J 5724T0713 z/OS Debugger JPN E0J
    JADRE0K 5724T0713 z/OS Debugger KOR E0K


    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:

    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:


    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 8. Driving System Software Requirements
    Program
    Number
    Product
    Name
    Minimum
    VRM
    Minimum
    Service Level
    will satisfy
    these
    APARs
    Included
    in the
    shipped
    product?
    Any one of the following:
    5694-A01 z/OS V01.13.00 N/A No
    5650-ZOS z/OS V02.01.00 or higher N/A No

    Note: SMP/E is a requirement for Installation and is an element of z/OS but can also be ordered as a separate product, 5655-G44, minimally V03.06.00.

    Note: Installation might require migration to new z/OS releases to be service supported. See http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html.


    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. These products are specified as PREs or REQs.

    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.

    The product in which you received z/OS Debugger contains multiple FMIDs, some of which provide services utilized by z/OS Debugger. See "Product FMIDs" for details.

    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
    FMID Product Name PTF
    z/OS V2.2
    HLE77A0 (Language Environment) UI29282 UI30573 UI31702 UI33265
    z/OS V2.1
    HDZ2210 (DFSMS) UA71130
    HLE7790 (Language Environment) UK95549 UI13453 UI16760 UI19022 UI19022 UI20212 UI23232 UI27324 UI27454 UI27850 UI29283 UI29373 UI29946 UI33267
    z/OS V1.13
    HDZ1D10 (DFSMS) UA65929 UA71109
    HLE7780 (Language Environment) UK71835 UK72082 UK72298 UK76507 UK76843 UK77516 UK78140 UK80370 UK82910 UK91519 UK94372 UI16759 UI20211 UI23231 UI27323 UI27453 UI27849 UI29372 UI29945 UI33266

    Table 10 lists the conditional operational requisites.

    Table 10. Target System Conditional Operational Requisites
    Program
    Number
    Product Name and
    Minimum VRM/Service Level
    Function
    5696-234 High Level Assembler for MVS & VM & VSE V1.6 Debug of Assembler programs
    Any one of the following:
    5655-AC5 Developer for z Systems Enterprise Edition V14.0 Remote debug on workstation
    5724-T07 Developer for z Systems V14.0 Remote debug on workstation
    5724-T07 Rational Developer for z Systems V9.5 Remote debug on workstation
    5724-T07 Rational Developer for System z V9.1 Remote debug on workstation
    Any one of the following:
    5655-EX1 Explorer for z/OS V3.0.1 Remote debug on workstation
    5655-EXP Explorer for z/OS V3.0 Remote debug on workstation
    Any one of the following:
    5655-Q12 File Manager for z/OS V13.1 Tools for working with z/OS data sets, DB2, CICS and IMS data
    5655-W68 File Manager for z/OS V12.1 Tools for working with z/OS data sets, DB2, CICS and IMS data
    Any one of the following:
    5655-Q11 Fault Analyzer for z/OS V13.1 Application abend analysis
    5655-W69 Fault Analyzer for z/OS V12.1 Application abend analysis
    Any one of the following:
    5722-DFJ CICS TS for z/OS Value Unit Edition, V5.1 through V5.3 CICS support
    5655-Y04 CICS TS for z/OS V5.1 through V5.3 CICS support
    5655-S97 CICS TS for z/OS V4.1 through V4.2 CICS support
    Any one of the following:
    5697-P43 DB2 11 for z/OS Value Unit Edition DB2 support
    5615-DB2 DB2 11 for z/OS DB2 support
    5697-P31 DB2 10 for z/OS Value Unit Edition DB2 support
    5605-DB2 DB2 10 for z/OS DB2 support
    Any one of the following:
    5655-DSE IMS Database Value Unit Edition, V14 IMS support
    5635-A05 IMS V14 IMS support
    5655-DSM IMS Database Value Unit Edition, V13 IMS support
    5635-A04 IMS V13 IMS support
    5655-DSQ IMS Database Value Unit Edition, V12 IMS support
    5635-A03 IMS V12 IMS support
    Any one of the following:
    5650-ZOS z/OS V2.1 (or later) C/C++ Element Debug of C/C++ programs
    5694-A01 z/OS V1.13 C/C++ Element Debug of C/C++ programs
    5655-121 C/C++ for MVS/ESA V3 Debug of C/C++ programs
    5688-216 AD/Cycle C/370 V1.2 Debug of C/370 programs
    Any one of the following:
    5655-EC6 Enterprise COBOL for z/OS V6.1 Debug of COBOL programs
    5655-W32 Enterprise COBOL for z/OS V5 Debug of COBOL programs
    5655-S71 Enterprise COBOL for z/OS V4.2 Debug of COBOL programs
    Any one of the following:
    5655-PL5 Enterprise PL/I for z/OS V5.1 Debug of PL/I programs
    5655-W67 Enterprise PL/I for z/OS V4.2 through V4.5 Debug of PL/I programs

    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
    FMID Product Name PTF
    sub-systems
    HCI6900 CICS TS for z/OS V5.2 UI22206 UI30410
    HCI6800 CICS TS for z/OS V5.1 UI13727 UI22205
    HCI6600 CICS TS for z/OS V4.1 UK48726 UK62906
    compilers
    HMQ4160 High Level Assembler for MVS & VM & VSE V1.6 UK47103 UK59311
    HLB7790 z/OS 2.1 XL C/C++ Base UI18562
    H270440 Enterprise PL/I for z/OS V4.4 UI22280
    H270430 Enterprise PL/I for z/OS V4.3 UI22279
    H270420 Enterprise PL/I for z/OS V4.2 UI22276

    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
    Program
    Number
    Product Name and
    VRM/Service Level
    Function
    sub-systems
    5655-147 CICS TS for OS/390 V1.3 CICS support
    5697-E93 CICS TS for z/OS V2.2 through V2.3 CICS support
    5655-M15 CICS TS for z/OS V3 CICS support
    5675-DB2 DB2 UDB for z/OS and OS/390 V7 DB2 support
    5625-DB2 DB2 UDB for z/OS V8 DB2 support
    5635-DB2 DB2 V9 for z/OS DB2 support
    5655-J38 IMS V9 IMS support
    5635-A01 IMS V10 IMS support
    5635-A02 IMS V11 IMS support
    compilers
    5696-234 High Level Assembler for MVS & VM & VSE V1.5 Debug of Assembler programs via the disassembly view
    5647-A01 OS/390 V2.10 C/C++ Element Debug of C/C++ programs
    5740-CB1 OS/VS COBOL V1.2.4 Debug of COBOL programs (with limitations)
    5668-958, 5688-023 VS COBOL II V1.3.1, V1.3.2, V1.4 Debug of COBOL programs (with limitations)
    5688-197 IBM COBOL for MVS & VM V1 Debug of COBOL programs
    5648-A25 COBOL for OS/390 & VM V2.2 Debug of COBOL programs
    5655-G53 IBM Enterprise COBOL for z/OS V3 Debug of COBOL programs
    5655-S71 IBM Enterprise COBOL for z/OS V4.1 Debug of COBOL programs
    5668-909, 5668-910 OS PL/I V2.1, V2.2, V2.3 Debug of PL/I programs (with limitations)
    5655-B22 IBM VisualAge PL/I for OS/390 V2 Debug of PL/I programs
    5688-235 IBM PL/I for MVS and VM V1.1.1 Debug of PL/I programs
    5655-H31 Enterprise PL/I for z/OS V3 Debug of PL/I programs
    5655-W67 Enterprise PL/I for z/OS V4.1 Debug of PL/I programs

    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
    FMID Product Name PTF
    sub-systems
    HCI5300 CICS TS for OS/390 V1.3 UQ81716 UQ82557
    HCI6200 CICS TS for z/OS V2.2 UQ81557 UQ82628
    HCI6300 CICS TS for z/OS V2.3 UQ83866 UQ83946 UK22257 UK25447 UK31617
    HCI6400 CICS TS for z/OS V3.1 UK11717 UK18764 UK21469 UK25495 UK31566 UK33555 UK39008 UK40994
    HCI6500 CICS TS for z/OS V3.2 UK27838 UK31567 UK33556 UK39009 UK40995 UK48737
    HDB7710 DB2 UDB for z/OS and OS/390 V7 UQ57178
    compilers
    HMQ4150 High Level Assembler for MVS & VM & VSE V1.5 UK33757 UK40904 UK42558 UK59303
    H26L330 Enterprise COBOL for z/OS V3.3 UK02153
    H26L320 Enterprise COBOL for z/OS and OS/390 V3.2 UK02152 UQ84365
    H26L310 Enterprise COBOL for z/OS and OS/390 V3.1 UQ72888
    H249200 COBOL for OS/390 & VM V2.2 UQ71482 UQ72385
    H249100 COBOL for OS/390 & VM V2.1 UQ46089 UQ71481 UQ72384
    J249101 COBOL for OS/390 & VM V2.1 (Mixed-case English) UQ46090
    J249102 COBOL for OS/390 & VM V2.1 (JPN) UQ46091
    H270380 Enterprise PL/I for z/OS V3.8 UK44457
    H270370 Enterprise PL/I for z/OS V3.7 UK31095 UK39550 UK44456
    H270360 Enterprise PL/I for z/OS V3.6 UK20098 UK21916 UK22225 UK29178 UK30600 UK31028 UK39549
    H270350 Enterprise PL/I for z/OS V3.5 UK20097 UK20187 UK22224 UK29177 UK30599
    H270340 Enterprise PL/I for z/OS V3.4 UK00175 UK01048 UK01926 UK01955 UK30598 UQ96871
    H270330 Enterprise PL/I for z/OS V3.3 UK01925 UQ83141 UQ83550 UQ84230 UQ85850 UQ91552 UQ96870
    H270320 Enterprise PL/I for z/OS and OS/390 V3.2 UK01924 UQ71704 UQ82334 UQ83140 UQ83549 UQ84229 UQ96869
    H270310 Enterprise PL/I for z/OS and OS/390 V3.1 UQ71463 UQ83139 UQ83548 UQ84228

    The z/OS Debugger Coverage Utility requires the use of one of the following compilers:

    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
    Library Type Total Space Required
    in 3390 Trks
    Description
    Target 1749 Tracks
    Distribution 1727 Tracks
    Web Download 2875 Tracks This row only applies when z/OS Debugger is downloaded from the web. It does not apply when you ordered it via Shopz.
    These are temporary data sets, which can be removed after the SMP/E install.

    Table 15. Total DASD Space Required by z/OS Debugger -- JPN
    Library Type Total Space Required
    in 3390 Trks
    Description
    Target 149 Tracks
    Distribution 149 Tracks
    Web Download 273 Tracks This row only applies when z/OS Debugger is downloaded from the web. It does not apply when you ordered it via Shopz.
    These are temporary data sets, which can be removed after the SMP/E install.

    Table 16. Total DASD Space Required by z/OS Debugger -- KOR
    Library Type Total Space Required
    in 3390 Trks
    Description
    Target 149 Tracks
    Distribution 149 Tracks
    Web Download 272 Tracks This row only applies when z/OS Debugger is downloaded from the web. It does not apply when you ordered it via Shopz.
    These are temporary data sets, which can be removed after the SMP/E install.

    Notes:

    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:

    4. All target libraries listed have the following attributes:

    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 17. Storage Requirements for z/OS Debugger Target Libraries -- Base
    Library
    DDNAME
    Member
    Type
    Target
    Volume
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    SEQALPA LMOD ANY U PDS U 0 2 2
    SEQAAUTH LMOD ANY U PDSE U 0 15 N/A
    SEQAMOD LMOD ANY U PDSE U 0 1200 N/A
    SEQABMOD LMOD ANY U PDSE U 0 10 N/A
    SEQASAMP Sample ANY U PDSE FB 80 80 25
    SEQAEXEC EXEC ANY U PDSE FB 80 144 15
    SEQAMENU Message ANY U PDSE FB 80 2 2
    SEQAPENU Panel ANY U PDSE FB 80 138 55
    SEQASENU Skeleton ANY U PDSE FB 80 9 5
    SEQATLIB Table ANY U PDSE FB 80 5 2
    SEQAMENP Message ANY U PDSE FB 80 2 2
    SEQAPENP Panel ANY U PDSE FB 80 138 55
    SEQASENP Skeleton ANY U PDSE FB 80 9 5


    Table 18. Storage Requirements for z/OS Debugger Target Libraries -- JPN
    Library
    DDNAME
    Member
    Type
    Target
    Volume
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    SEQAMOD LMOD ANY S PDSE U 0 10 N/A
    SEQABMOD LMOD ANY S PDSE U 0 4 N/A
    SEQASAMP Sample ANY S PDSE FB 80 4 3
    SEQAEXEC EXEC ANY S PDSE FB 80 6 3
    SEQAMJPN Message ANY U PDSE FB 80 2 2
    SEQAPJPN Panel ANY U PDSE FB 80 138 70
    SEQASJPN Skeleton ANY U PDSE FB 80 9 3


    Table 19. Storage Requirements for z/OS Debugger Target Libraries -- KOR
    Library
    DDNAME
    Member
    Type
    Target
    Volume
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    SEQAMOD LMOD ANY S PDSE U 0 10 N/A
    SEQABMOD LMOD ANY S PDSE U 0 4 N/A
    SEQASAMP Sample ANY S PDSE FB 80 4 3
    SEQAEXEC EXEC ANY S PDSE FB 80 6 3
    SEQAMKOR Message ANY U PDSE FB 80 2 2
    SEQAPKOR Panel ANY U PDSE FB 80 138 70
    SEQASKOR Skeleton ANY U PDSE FB 80 9 3


    Table 20. Storage Requirements for z/OS Debugger Distribution Libraries -- Base
    Library
    DDNAME
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    AEQAMOD U PDSE U 0 1200 N/A
    AEQASAMP U PDSE FB 80 80 25
    AEQAEXEC U PDSE FB 80 144 15
    AEQAMENU U PDSE FB 80 2 2
    AEQAPENU U PDSE FB 80 138 55
    AEQASENU U PDSE FB 80 9 5
    AEQATLIB U PDSE FB 80 5 2
    AEQAMENP U PDSE FB 80 2 2
    AEQAPENP U PDSE FB 80 138 55
    AEQASENP U PDSE FB 80 9 5

    Table 21. Storage Requirements for z/OS Debugger Distribution Libraries -- JPN
    Library
    DDNAME
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    AEQAMOD S PDSE U 0 14 N/A
    AEQASAMP S PDSE FB 80 4 3
    AEQAEXEC S PDSE FB 80 6 3
    AEQAMJPN U PDSE FB 80 2 2
    AEQAPJPN U PDSE FB 80 138 70
    AEQASJPN U PDSE FB 80 9 3

    Table 22. Storage Requirements for z/OS Debugger Distribution Libraries -- KOR
    Library
    DDNAME
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    AEQAMOD S PDSE U 0 14 N/A
    AEQASAMP S PDSE FB 80 4 3
    AEQAEXEC S PDSE FB 80 6 3
    AEQAMKOR U PDSE FB 80 2 2
    AEQAPKOR U PDSE FB 80 138 70
    AEQASKOR U PDSE FB 80 9 3

    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 23. Storage Requirements for z/OS Debugger Web Download Data Sets -- Base
    Data Set
    Name
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    hlq.IBM.HADRE00.F1 U PDSE FB 80 102 N/A
    hlq.IBM.HADRE00.F1.BIN U SEQ FB 80 59 N/A
    hlq.IBM.HADRE00.F2 U PDSE FB 80 168 N/A
    hlq.IBM.HADRE00.F2.BIN U SEQ FB 80 102 N/A
    hlq.IBM.HADRE00.F3 U PDSE U 0 1026 N/A
    hlq.IBM.HADRE00.F3.BIN U SEQ FB 80 912 N/A
    hlq.IBM.HADRE00.F4 U PDSE FB 80 2 N/A
    hlq.IBM.HADRE00.F4.BIN U SEQ FB 80 1 N/A
    hlq.IBM.HADRE00.F5 U PDSE FB 80 152 N/A
    hlq.IBM.HADRE00.F5.BIN U SEQ FB 80 72 N/A
    hlq.IBM.HADRE00.F6 U PDSE FB 80 10 N/A
    hlq.IBM.HADRE00.F6.BIN U SEQ FB 80 5 N/A
    hlq.IBM.HADRE00.F7 U PDSE FB 80 6 N/A
    hlq.IBM.HADRE00.F7.BIN U SEQ FB 80 3 N/A
    hlq.IBM.HADRE00.F8 U PDSE FB 80 2 N/A
    hlq.IBM.HADRE00.F8.BIN U SEQ FB 80 1 N/A
    hlq.IBM.HADRE00.F9 U PDSE FB 80 152 N/A
    hlq.IBM.HADRE00.F9.BIN U SEQ FB 80 72 N/A
    hlq.IBM.HADRE00.F10 U PDSE FB 80 10 N/A
    hlq.IBM.HADRE00.F10.BIN U SEQ FB 80 5 N/A
    hlq.IBM.HADRE00.SMPMCS U SEQ FB 80 13 N/A
    Note: These are temporary data sets, which can be removed after the SMP/E install.

    Table 24. Storage Requirements for z/OS Debugger Web Download Data Sets -- JPN
    Data Set
    Name
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    hlq.IBM.JADRE0J.F1 U PDSE FB 80 4 N/A
    hlq.IBM.JADRE0J.F1.BIN U SEQ FB 80 2 N/A
    hlq.IBM.JADRE0J.F2 U PDSE FB 80 5 N/A
    hlq.IBM.JADRE0J.F2.BIN U SEQ FB 80 3 N/A
    hlq.IBM.JADRE0J.F3 U PDSE U 0 8 N/A
    hlq.IBM.JADRE0J.F3.BIN U SEQ FB 80 7 N/A
    hlq.IBM.JADRE0J.F4 U PDSE FB 80 2 N/A
    hlq.IBM.JADRE0J.F4.BIN U SEQ FB 80 1 N/A
    hlq.IBM.JADRE0J.F5 U PDSE FB 80 151 N/A
    hlq.IBM.JADRE0J.F5.BIN U SEQ FB 80 71 N/A
    hlq.IBM.JADRE0J.F6 U PDSE FB 80 10 N/A
    hlq.IBM.JADRE0J.F6.BIN U SEQ FB 80 5 N/A
    hlq.IBM.JADRE0J.SMPMCS U SEQ FB 80 4 N/A
    Note: These are temporary data sets, which can be removed after the SMP/E install.

    Table 25. Storage Requirements for z/OS Debugger Web Download Data Sets -- KOR
    Data Set
    Name
    T
    Y
    P
    E
    O
    R
    G
    R
    E
    C
    F
    M
    L
    R
    E
    C
    L
    No.
    of
    3390
    Trks
    No.
    of
    DIR
    Blks
    hlq.IBM.JADRE0K.F1 U PDSE FB 80 4 N/A
    hlq.IBM.JADRE0K.F1.BIN U SEQ FB 80 2 N/A
    hlq.IBM.JADRE0K.F2 U PDSE FB 80 5 N/A
    hlq.IBM.JADRE0K.F2.BIN U SEQ FB 80 3 N/A
    hlq.IBM.JADRE0K.F3 U PDSE U 0 8 N/A
    hlq.IBM.JADRE0K.F3.BIN U SEQ FB 80 6 N/A
    hlq.IBM.JADRE0K.F4 U PDSE FB 80 2 N/A
    hlq.IBM.JADRE0K.F4.BIN U SEQ FB 80 1 N/A
    hlq.IBM.JADRE0K.F5 U PDSE FB 80 151 N/A
    hlq.IBM.JADRE0K.F5.BIN U SEQ FB 80 71 N/A
    hlq.IBM.JADRE0K.F6 U PDSE FB 80 10 N/A
    hlq.IBM.JADRE0K.F6.BIN U SEQ FB 80 5 N/A
    hlq.IBM.JADRE0K.SMPMCS U SEQ FB 80 4 N/A
    Note: These are temporary data sets, which can be removed after the SMP/E install.


    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:


    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:


    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 26. 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 26. SMP/E Options Subentry Values
    Subentry Value Comment
    DSSPACE (1200,1200,1400) Space allocation
    PEMAX SMP/E Default IBM recommends using the SMP/E default for PEMAX.

    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:

    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 sequential data sets to hold SMPMCS and compressed RELFILEs
      (only applicable for web download, not Shopz orders)

    2. Upload the SMPMCS and compressed RELFILEs to the host
      (only applicable for web download, not Shopz orders)

    3. Expand the compressed RELFILEs by using the TSO RECEIVE command
      (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 z/OS Debugger

    10. Remove old registrations

    11. Run the Installation Verification Programs (IVPs)

    12. Verify the z/OS Debugger Utilities Setup Utility Function

    13. Perform SMP/E ACCEPT

    14. Run REPORT CROSSZONE

    Allocate sequential data sets to hold SMPMCS and compressed 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 SMP/E input data sets to install IBM z/OS Debugger are provided as binary files in the downloaded package, and must be uploaded to z/OS.

    To ensure that the data sets are allocated correctly, it is advised to allocate empty data sets before uploading the data. You can use the following sample JCL to allocate the data sets. The sample JCL needs the following updates:

    1. Add a JOB card and modify the allocation parameters to meet your site requirements.

    2. hlq specifies the high level qualifier you choose to use for the data sets.

    3. (Optional) Replace vvvvvv with the volume serial you choose to use for the data sets.
    To allocate the data sets for the z/OS Debugger Base, use this JCL:
    //ALLOC    PROC LLQ=,
    //            FMID=HADRE00,
    //            TRKS=
    //ALLOC    EXEC PGM=IEFBR14
    //DATASET  DD DSN=hlq.IBM.&FMID..&LLQ,
    //            DISP=(NEW,CATLG),
    //            RECFM=FB,LRECL=80,
    //            DSORG=PS,BLKSIZE=0,
    //            UNIT=SYSALLDA,
    //*           VOL=SER=vvvvvv,  * uncomment to specify a volser
    //            SPACE=(TRK,(&TRKS,5))
    //EALLOC   PEND
    //*
    //F1       EXEC ALLOC,LLQ=F1.BIN,TRKS=59
    //F2       EXEC ALLOC,LLQ=F2.BIN,TRKS=102
    //F3       EXEC ALLOC,LLQ=F3.BIN,TRKS=912
    //F4       EXEC ALLOC,LLQ=F4.BIN,TRKS=1
    //F5       EXEC ALLOC,LLQ=F5.BIN,TRKS=72
    //F6       EXEC ALLOC,LLQ=F6.BIN,TRKS=5
    //F7       EXEC ALLOC,LLQ=F7.BIN,TRKS=3
    //F8       EXEC ALLOC,LLQ=F8.BIN,TRKS=1
    //F9       EXEC ALLOC,LLQ=F9.BIN,TRKS=72
    //F10      EXEC ALLOC,LLQ=F10.BIN,TRKS=5
    //SMPMCS   EXEC ALLOC,LLQ=SMPMCS,TRKS=13
    //*
    
    To allocate the data sets for the z/OS Debugger JPN feature, use this JCL:
    //ALLOC    PROC LLQ=,
    //            FMID=JADRE0J,
    //            TRKS=
    //ALLOC    EXEC PGM=IEFBR14
    //DATASET  DD DSN=hlq.IBM.&FMID..&LLQ,
    //            DISP=(NEW,CATLG),
    //            RECFM=FB,LRECL=80,
    //            DSORG=PS,BLKSIZE=0,
    //            UNIT=SYSALLDA,
    //*           VOL=SER=vvvvvv,  * uncomment to specify a volser
    //            SPACE=(TRK,(&TRKS,5))
    //EALLOC   PEND
    //*
    //F1       EXEC ALLOC,LLQ=F1.BIN,TRKS=2
    //F2       EXEC ALLOC,LLQ=F2.BIN,TRKS=3
    //F3       EXEC ALLOC,LLQ=F3.BIN,TRKS=7
    //F4       EXEC ALLOC,LLQ=F4.BIN,TRKS=1
    //F5       EXEC ALLOC,LLQ=F5.BIN,TRKS=71
    //F6       EXEC ALLOC,LLQ=F6.BIN,TRKS=5
    //SMPMCS   EXEC ALLOC,LLQ=SMPMCS,TRKS=4
    //*
    
    To allocate the data sets for the z/OS Debugger KOR feature, use this JCL:
    //ALLOC    PROC LLQ=,
    //            FMID=JADRE0K,
    //            TRKS=
    //ALLOC    EXEC PGM=IEFBR14
    //DATASET  DD DSN=hlq.IBM.&FMID..&LLQ,
    //            DISP=(NEW,CATLG),
    //            RECFM=FB,LRECL=80,
    //            DSORG=PS,BLKSIZE=0,
    //            UNIT=SYSALLDA,
    //*           VOL=SER=vvvvvv,  * uncomment to specify a volser
    //            SPACE=(TRK,(&TRKS,5))
    //EALLOC   PEND
    //*
    //F1       EXEC ALLOC,LLQ=F1.BIN,TRKS=2
    //F2       EXEC ALLOC,LLQ=F2.BIN,TRKS=3
    //F3       EXEC ALLOC,LLQ=F3.BIN,TRKS=6
    //F4       EXEC ALLOC,LLQ=F4.BIN,TRKS=1
    //F5       EXEC ALLOC,LLQ=F5.BIN,TRKS=71
    //F6       EXEC ALLOC,LLQ=F6.BIN,TRKS=5
    //SMPMCS   EXEC ALLOC,LLQ=SMPMCS,TRKS=4
    //*
    

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

    Upload the SMPMCS and compressed RELFILEs 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 files in binary format from your workstation to the z/OS data sets.

    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 27. User Entered Values
    User enters: Values
    mvsaddr TCP/IP address or hostname of the z/OS system
    tsouid Your TSO user ID
    tsopw Your TSO password
    d: Location of the downloaded files
    hlq High-level qualifier you used for the data sets you allocated in the previous step

    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 ..
    250 " " is the working directory name prefix.
    ftp> cd hlq
    250 "hlq." is the working directory name prefix.
    ftp> binary
    200 Representation type is Image
    ftp> prompt
    Interactive mode Off.
    
    ftp> mput d:\HADRE00\IBM.HADRE00.F*
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F1.BIN
    250 Transfer completed successfully.
    ftp: 3242000 bytes sent in 0.02 sec. (11293.945 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F2.BIN
    250 Transfer completed successfully.
    ftp: 5676000 bytes sent in 0.33 sec. (8667.350 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F3.BIN
    250 Transfer completed successfully.
    ftp: 50914080 bytes sent in 11.91 sec. (8088.401 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F4.BIN
    250 Transfer completed successfully.
    ftp: 11840 bytes sent in 0.80 sec. (8080.105 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F5.BIN
    250 Transfer completed successfully.
    ftp: 3972880 bytes sent in 0.06 sec. (8515.625 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F6.BIN
    250 Transfer completed successfully.
    ftp: 264000 bytes sent in 0.02 sec. (11293.945 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F7.BIN
    250 Transfer completed successfully.
    ftp: 147840 bytes sent in 0.33 sec. (8667.350 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F8.BIN
    250 Transfer completed successfully.
    ftp: 11840 bytes sent in 11.91 sec. (8088.401 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F9.BIN
    250 Transfer completed successfully.
    ftp: 3972720 bytes sent in 0.80 sec. (8080.105 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.F10.BIN
    250 Transfer completed successfully.
    ftp: 264000 bytes sent in 0.06 sec. (8515.625 Kb/s)
    ftp> put d:\HADRE00\IBM.HADRE00.SMPMCS
    200 Port request OK.
    125 Storing data set hlq.IBM.HADRE00.SMPMCS
    250 Transfer completed successfully.
    ftp: 691920 bytes sent in 0.01 sec. (4151.042 Kb/s)
    ftp> quit
    221 Quit command received. Goodbye.
    

    Issue these commands to upload the z/OS Debugger JPN 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 ..
    250 " " is the working directory name prefix.
    ftp> cd hlq
    250 "hlq." is the working directory name prefix.
    ftp> binary
    200 Representation type is Image
    ftp> prompt
    Interactive mode Off.
    ftp> mput d:\HADRE00\IBM.JADRE0J.F*
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0J.F1.BIN
    250 Transfer completed successfully.
    ftp: 69760 bytes sent in 0.02 sec. (11293.945 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0J.F2.BIN
    250 Transfer completed successfully.
    ftp: 113200 bytes sent in 0.33 sec. (8667.350 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0J.F3.BIN
    250 Transfer completed successfully.
    ftp: 343120 bytes sent in 11.91 sec. (8088.401 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0J.F4.BIN
    250 Transfer completed successfully.
    ftp: 11840 bytes sent in 0.80 sec. (8080.105 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0J.F5.BIN
    250 Transfer completed successfully.
    ftp: 3949680 bytes sent in 0.06 sec. (8515.625 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0J.F6.BIN
    250 Transfer completed successfully.
    ftp: 263920 bytes sent in 0.02 sec. (11293.945 Kb/s)
    ftp> put d:\HADRE00\IBM.JADRE0J.SMPMCS
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0J.SMPMCS
    250 Transfer completed successfully.
    ftp: 190480 bytes sent in 0.01 sec. (4151.042 Kb/s)
    ftp> quit
    221 Quit command received. Goodbye.
    

    Issue these commands to upload the z/OS Debugger KOR 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 ..
    250 " " is the working directory name prefix.
    ftp> cd hlq
    250 "hlq." is the working directory name prefix.
    ftp> binary
    200 Representation type is Image
    ftp> prompt
    Interactive mode Off.
    ftp> mput d:\HADRE00\IBM.JADRE0K.F*
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0K.F1.BIN
    250 Transfer completed successfully.
    ftp: 69760 bytes sent in 0.02 sec. (11293.945 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0K.F2.BIN
    250 Transfer completed successfully.
    ftp: 113840 bytes sent in 0.33 sec. (8667.350 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0K.F3.BIN
    250 Transfer completed successfully.
    ftp: 330720 bytes sent in 11.91 sec. (8088.401 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0K.F4.BIN
    250 Transfer completed successfully.
    ftp: 11760 bytes sent in 0.80 sec. (8080.105 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0K.F5.BIN
    250 Transfer completed successfully.
    ftp: 3926480 bytes sent in 0.06 sec. (8515.625 Kb/s)
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0K.F6.BIN
    250 Transfer completed successfully.
    ftp: 263920 bytes sent in 0.02 sec. (11293.945 Kb/s)
    ftp> put d:\HADRE00\IBM.JADRE0K.SMPMCS
    200 Port request OK.
    125 Storing data set hlq.IBM.JADRE0K.SMPMCS
    250 Transfer completed successfully.
    ftp: 189440 bytes sent in 0.01 sec. (4151.042 Kb/s)
    ftp> quit
    221 Quit command received. Goodbye.
    

    Expand the compressed RELFILEs with TSO RECEIVE

    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 uploaded RELFILEs are in TSO TRANSMIT format and must be expanded with the TSO RECEIVE command to become usable. hlq Specifies the high level qualifier you used for the data sets you allocated in the previous step.

    When prompted on the TSO RECEIVE commands, use the appropriate DSNAME from the list below:

    Sample Jobs

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

    Table 28. Sample Installation Jobs -- BASE
    Job Name Job Type Description RELFILE
    EQAWEDIT MACRO ISPF Editor macro to aid in updating the sample jobs (optional) IBM.HADRE00.F1
    EQAWSMPE SMP/E Sample job to create an SMP/E environment (optional) IBM.HADRE00.F1
    EQAWRECV RECEIVE Sample SMP/E RECEIVE job IBM.HADRE00.F1
    EQAWALOC ALLOCATE Sample job to allocate target and distribution libraries IBM.HADRE00.F1
    EQAWDDEF DDDEF Sample job to define SMP/E DDDEFs IBM.HADRE00.F1
    EQAWAPLY APPLY Sample SMP/E APPLY job IBM.HADRE00.F1
    EQAWACPT ACCEPT Sample SMP/E ACCEPT job IBM.HADRE00.F1
    EQAWRPXZ SMP/E Sample REPORT CROSSZONE job IBM.HADRE00.F1
    Note: When z/OS Debugger is downloaded from the web, the RELFILE data set name will be prefixed by your chosen high level qualifier, as documented in section "Expand the compressed RELFILEs with TSO RECEIVE".

    Table 29. Sample Installation Jobs -- JPN
    Job Name Job Type Description RELFILE
    EQAWEDIJ MACRO ISPF Editor macro to aid in updating the sample jobs (optional) IBM.JADRE0J.F1
    EQAWRECJ RECEIVE Sample SMP/E RECEIVE job IBM.JADRE0J.F1
    EQAWALOJ ALLOCATE Sample job to allocate target and distribution libraries IBM.JADRE0J.F1
    EQAWDEFJ DDDEF Sample job to define SMP/E DDDEFs IBM.JADRE0J.F1
    EQAWAPLJ APPLY Sample SMP/E APPLY job IBM.JADRE0J.F1
    EQAWACPJ ACCEPT Sample SMP/E ACCEPT job IBM.JADRE0J.F1
    Note: When z/OS Debugger is downloaded from the web, the RELFILE data set name will be prefixed by your chosen high level qualifier, as documented in section "Expand the compressed RELFILEs with TSO RECEIVE".

    Table 30. Sample Installation Jobs -- KOR
    Job Name Job Type Description RELFILE
    EQAWEDIK MACRO ISPF Editor macro to aid in updating the sample jobs (optional) IBM.JADRE0K.F1
    EQAWRECK RECEIVE Sample SMP/E RECEIVE job IBM.JADRE0K.F1
    EQAWALOK ALLOCATE Sample job to allocate target and distribution libraries IBM.JADRE0K.F1
    EQAWDEFK DDDEF Sample job to define SMP/E DDDEFs IBM.JADRE0K.F1
    EQAWAPLK APPLY Sample SMP/E APPLY job IBM.JADRE0K.F1
    EQAWACPK ACCEPT Sample SMP/E ACCEPT job IBM.JADRE0K.F1
    Note: When z/OS Debugger is downloaded from the web, the RELFILE data set name will be prefixed by your chosen high level qualifier, as documented in section "Expand the compressed RELFILEs with TSO RECEIVE".

    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: "Set up ISPF Editor Macro (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 RELFILES to a work data set for editing and submission. See Table 28 to find the appropriate relfile data set.

    You can also copy the sample installation jobs from the tape or product files by submitting the following job. Depending on your distribution medium, use either the //TAPEIN or the //FILEIN DD statement and comment out or delete the other statement. 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=*
    //TAPEIN   DD DSN=IBM.HADRE00.F1,
    //            DISP=(OLD,KEEP),
    //            LABEL=(x,SL),
    //            VOL=SER=ADRE00,
    //            UNIT=tunit
    //FILEIN   DD DSN=IBM.HADRE00.F1,
    //            DISP=SHR,
    //*           VOL=SER=filevol,
    //            UNIT=SYSALLDA
    //OUT      DD DSNAME=jcl-library-name,
    //            DISP=(NEW,CATLG,DELETE),
    //            SPACE=(TRK,(102,5,5)),
    //*           VOL=SER=dasdvol,
    //            UNIT=SYSALLDA
    //SYSUT3   DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    //SYSIN    DD *
        COPY INDD=xxxxIN,OUTDD=OUT
        SELECT MEMBER=(EQAWEDIT,EQAWSMPE,EQAWRECV,EQAWALOC)
        SELECT MEMBER=(EQAWDDEF,EQAWAPLY,EQAWACPT,EQAWRPXZ)
    /*
    

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

    //STEP1    EXEC PGM=IEBCOPY
    //SYSPRINT DD SYSOUT=*
    //TAPEIN   DD DSN=IBM.JADRE0J.F1,
    //            DISP=(OLD,KEEP),
    //            LABEL=(x,SL),
    //            VOL=SER=ADRE0J,
    //            UNIT=tunit
    //FILEIN   DD DSN=IBM.JADRE0J.F1,
    //            DISP=SHR,
    //*           VOL=SER=filevol,
    //            UNIT=SYSALLDA
    //OUT      DD DSNAME=jcl-library-name,
    //            DISP=(NEW,CATLG,DELETE),
    //            SPACE=(TRK,(4,5,5)),
    //*           VOL=SER=dasdvol,
    //            UNIT=SYSALLDA
    //SYSUT3   DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    //SYSIN    DD *
        COPY INDD=xxxxIN,OUTDD=OUT
        SELECT MEMBER=(EQAWEDIJ,EQAWRECJ,EQAWALOJ)
        SELECT MEMBER=(EQAWDEFJ,EQAWAPLJ,EQAWACPJ)
    /*
    

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

    //STEP1    EXEC PGM=IEBCOPY
    //SYSPRINT DD SYSOUT=*
    //TAPEIN   DD DSN=IBM.JADRE0K.F1,
    //            DISP=(OLD,KEEP),
    //            LABEL=(x,SL),
    //            VOL=SER=ADRE0K,
    //            UNIT=tunit
    //FILEIN   DD DSN=IBM.JADRE0K.F1,
    //            DISP=SHR,
    //*           VOL=SER=filevol,
    //            UNIT=SYSALLDA
    //OUT      DD DSNAME=jcl-library-name,
    //            DISP=(NEW,CATLG,DELETE),
    //            SPACE=(TRK,(4,5,5)),
    //*           VOL=SER=dasdvol,
    //            UNIT=SYSALLDA
    //SYSUT3   DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    //SYSIN    DD *
        COPY INDD=xxxxIN,OUTDD=OUT
        SELECT MEMBER=(EQAWEDIK,EQAWRECK,EQAWALOK)
        SELECT MEMBER=(EQAWDEFK,EQAWAPLK,EQAWACPK)
    /*
    
    See the following information to update the statements in the previous sample:
    TAPEIN:
    tunit is the unit value that matches the product package.
    x is the tape file number that indicates the location of the data set name on the tape.
    See the documentation that is provided by CBPDO for the location of IBM.HADRE00.F1, IBM.JADRE0J.F1, and IBM.JADRE0K.F1 on the tape.
    FILEIN:
    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.
    SYSIN:
    xxxxIN is either TAPEIN or FILEIN depending on your input DD statement.

    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.

    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.

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

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

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

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

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

    In turn, IBM Developer for z Systems Enterprise Edition can be part of a product suite.

    You must set up product registration for z/OS Debugger to enable the functions within. Products to be enabled on z/OS are defined in the IFAPRDxx parmlib member that will be used for IPL.

    You must specify one of the following IFAPRDxx entries as shown below, depending on how you purchased z/OS Debugger. If you defined the product already using FEATURENAME('*') (for another component of the product), you do not need to repeat the definition.

    Specify the following in IFAPRDxx to define IBM Application Delivery Foundation for z Systems (product code 5655-AC6). Sample member EQAWIFAA, which contains the next statements, is provided in the SEQASAMP sample library.

    PRODUCT OWNER('IBM CORP')
            NAME('IBM APP DLIV FND')
            ID(5655-AC6)
            VERSION(*) RELEASE(*) MOD(*)
            FEATURENAME(*)
            STATE(ENABLED)
    

    Specify the following in IFAPRDxx to define IBM Debug for z Systems (product code 5655-Q50). Sample member EQAWIFAD, which contains the next statements, is provided in the SEQASAMP sample library.

    PRODUCT OWNER('IBM CORP')
            NAME('IBM Debug for z')
            ID(5655-Q50)
            VERSION(*) RELEASE(*) MOD(*)
            FEATURENAME(*)
            STATE(ENABLED)
    

    Specify the following in IFAPRDxx to define IBM Developer for z Systems Enterprise Edition (product code 5655-AC5). Sample member EQAWIFAE, which contains the next statements, is provided in the SEQASAMP sample library.

    PRODUCT OWNER('IBM CORP')
            NAME('IBM IDz EE')
            ID(5655-AC5)
            VERSION(*) RELEASE(*) MOD(*)
            FEATURENAME(*)
            STATE(ENABLED)
    

    Specify the following in IFAPRDxx to define IBM Developer for z Systems (product code 5724-T07). Sample member EQAWIFAZ, which contains the next statements, is provided in the SEQASAMP sample library.

    PRODUCT OWNER('IBM CORP')
            NAME('IBM IDz')
            ID(5724-T07)
            VERSION(*) RELEASE(*) MOD(*)
            FEATURENAME(*)
            STATE(ENABLED)
    

    Note:

    After you have updated IFAPRDxx, issue the SET PROD=xx operator command to dynamically activate the definitions. z/OS Debugger will then be enabled in your z/OS environment.

    Remove old registrations

    It is recommended that you remove all old registration entries that belonged to z/OS Debugger. Note that older versions of z/OS Debugger were known as Debug Tool, or Debug Tool Utilities and Advanced Functions.

    To remove old registration entries, do the following two steps:

    1. Change the STATE(ENABLED) parameter for the old entries in the IFAPRDxx parmlib member to STATE(NOTDEFINED).

    2. Issue a SET PROD=xx operator command to activate your changes.

    3. Remove the old entries from IFAPRDxx. This update will become active at next IPL.

    Run the Installation Verification Programs (IVPs)

    When z/OS Debugger is purchased as part of IBM Developer for z Systems, it only interacts with the GUI interface provided by IBM Developer for z Systems. This implies that in this situation, you cannot run the IVPs listed here.

    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 31 lists the IVPs for batch mode.

    Table 31. z/OS Debugger IVPs for Batch Mode
    IVP Name Description
    EQAWIVPA 1 Dynamic Debug facility and Language Environment Assembler
    EQAWIVPC 1 Dynamic Debug facility and Non-Language Environment Assembler
    EQAWIVPF 1 Dynamic Debug facility and Enterprise PL/I TEST(ALL,SYM,NOHOOK)
    EQAWIVPG z/OS C DEBUG(FORMAT(DWARF),HOOK(LINE,NOBLOCK,PATH),SYMBOL)
    EQAWIVPI 1 Dynamic Debug facility and Enterprise PL/I TEST(ALL,SYM,NOHOOK,SEPARATE)
    EQAWIVPJ 1 Dynamic Debug facility and LangX Language Environment COBOL IVP
    EQAWIVPM z/OS C DEBUG(FORMAT(DWARF),HOOK(LINE,NOBLOCK,PATH),SYMBOL),
    XPLINK
    EQAWIVPP 1 Dynamic Debug facility and COBOL TEST(NONE,SYM,SEPARATE)
    COBOL for OS/390 and VM
    Enterprise COBOL for z/OS and OS/390 V3
    Enterprise COBOL for z/OS V3 and V4
    EQAWIVPS 1 Dynamic Debug facility and Disassembly
    EQAWIVPT 1 Dynamic Debug facility and COBOL TEST
    Enterprise COBOL for z/OS V5 and V6
    EQAWIVPV 1 Dynamic Debug facility and OS/VS COBOL
    EQAWIVPX 1 Dynamic Debug facility and Non-Language Environment VS COBOL II
    EQAWIVP1 COBOL TEST(ALL)
    COBOL for MVS and VM
    COBOL for OS/390 and VM
    Enterprise COBOL for z/OS and OS/390 V3
    Enterprise COBOL for z/OS V3 and V4
    EQAWIVP2 C TEST(ALL)
    EQAWIVP3 PL/I for MVS and VM TEST(ALL)
    EQAWIVP4 1 Dynamic Debug facility and COBOL TEST(NONE,SYM)
    COBOL for OS/390 and VM
    Enterprise COBOL for z/OS and OS/390 V3
    Enterprise COBOL for z/OS V3 and V4
    EQAWIVP8 VisualAge or Enterprise PL/I TEST(ALL)
    Note:

    1. See chapter "Installing the z/OS Debugger SVCs" in the IBM z/OS Debugger Customization Guide (SC27-8935) before running these IVPs.

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

    Table 32. z/OS Debugger IVPs for Full-screen Mode using the
    Terminal Interface Manager
    IVP Name Description
    EQAWIVPB 2 Dynamic Debug facility and Language Environment Assembler
    EQAWIVPD 2 Dynamic Debug facility and Non-Language Environment Assembler
    EQAWIVPK 2 Dynamic Debug facility and LangX Language Environment COBOL IVP
    EQAWIVPU 2 Dynamic Debug facility and COBOL TEST
    Enterprise COBOL for z/OS V5 and V6
    EQAWIVPW 2 Dynamic Debug facility and OS/VS COBOL
    EQAWIVPY 2 Dynamic Debug facility and Non-Language Environment VS COBOL II
    EQAWIVP5 1 COBOL TEST(ALL)
    COBOL for MVS and VM
    COBOL for OS/390 and VM
    Enterprise COBOL for z/OS and OS/390 V3
    Enterprise COBOL for z/OS V3 and V4
    EQAWIVP6 1 C TEST(ALL)
    EQAWIVP7 1 PL/I for MVS and VM TEST(ALL)
    EQAWIVP9 1 VisualAge or Enterprise PL/I TEST(ALL)
    Note:

    1. See chapter "Enabling debugging in full-screen mode using the Terminal Interface Manager" in the IBM z/OS Debugger Customization Guide (SC27-8935) before running these IVPs.

    2. See chapter "Enabling debugging in full-screen mode using the Terminal Interface Manager" and chapter "Installing the z/OS Debugger SVCs" before running these IVPs. Both of these chapters are in the IBM z/OS Debugger Customization Guide (SC27-8935).

    Table 33 lists the IVPs for running under CICS.

    Table 33. z/OS Debugger IVPs for Running under CICS
    IVP Name Description
    EQAWIVCC 2 Dynamic Debug facility and Non-Language Environment Assembler
    EQAWIVCG 1 z/OS C DEBUG(FORMAT(DWARF),HOOK(LINE,NOBLOCK,PATH),SYMBOL)
    EQAWIVCI 2 Dynamic Debug facility and Enterprise PL/I TEST(ALL,SYM,NOHOOK,SEPARATE)
    EQAWIVCJ 2 Dynamic Debug facility and LangX Language Environment COBOL CICS IVP
    EQAWIVCP 2 Dynamic Debug facility and COBOL TEST(NONE,SYM,SEPARATE)
    COBOL for OS/390 and VM
    Enterprise COBOL for z/OS and OS/390 V3
    Enterprise COBOL for z/OS V3 and V4
    EQAWIVCT 2 Dynamic Debug facility and COBOL TEST
    Enterprise COBOL for z/OS V5 and V6
    EQAWIVC2 1 C TEST(ALL)
    EQAWIVC8 1 VisualAge or Enterprise PL/I TEST(ALL)
    Note:

    1. See chapter "Adding support for debugging under CICS" in the IBM z/OS Debugger Customization Guide (SC27-8935) before running these IVPs.

    2. See chapter "Adding support for debugging under CICS" and chapter "Installing the z/OS Debugger SVCs" before running these IVPs. Both of these chapters are in the IBM z/OS Debugger Customization Guide (SC27-8935).

    Table 34 lists the IVP for Load Module Analyzer.

    Table 34. z/OS Debugger IVP for Load Module Analyzer
    IVP Name Description
    EQAWLMA Load Module Analyzer

    Table 35 lists the IVPs for z/OS Debugger Coverage Utility.

    Table 35. z/OS Debugger IVPs for z/OS Debugger Coverage Utility
    IVP Name Description
    EQACU1VM COBOL for MVS and VM
    COBOL for OS/390 and VM
    Enterprise COBOL for z/OS and OS/390 V3
    Enterprise COBOL for z/OS V3 and V4
    EQACU1VT Enterprise COBOL for z/OS V5 and V6
    EQACU2VM PL/I for MVS and VM
    EQACU2VV VisualAge PL/I
    EQACU2VZ Enterprise PL/I for z/OS
    EQACU3VA OS/390 C V2.6 and V2.10
    EQACU4VL High Level Assembler
    Note:

    See section "Customizing Coverage Utility" in chapter "Customizing z/OS Debugger Utilities" of the IBM z/OS Debugger Customization Guide (SC27-8935) before running these IVPs.

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

    Table 36. z/OS Debugger IVP for z/OS Debugger Code Coverage
    IVP Name Description
    EQACC1VZ Enterprise COBOL for z/OS and OS/390 V3
    Enterprise COBOL for z/OS V3 and V4
    EQACC2VZ Enterprise PL/I for z/OS V4.2 through V4.5 and V5
    EQACC3VZ z/OS XL C
    EQACC4VZ Enterprise COBOL for z/OS V5 and V6

    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 D. Examples: Preparing programs and modifying setup files with z/OS Debugger Utilities" in the IBM z/OS Debugger Users Guide (SC27-8932).

    See "Customizing z/OS Debugger Utilities" in the IBM z/OS Debugger Customization Guide (SC27-8935) 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.

    If your order contains the Korean feature, edit and submit sample job EQAWACPK 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 23 (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.

    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.


    Product Customization

    The publication IBM z/OS Debugger Customization Guide (SC27-8935) contains the necessary information to customize and use z/OS Debugger.

    The publication IBM z/OS Debugger Users Guide (SC27-8932) 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.


    Product FMIDs

    The product in which you received z/OS Debugger contains multiple FMIDs, some of which provide services utilized by z/OS Debugger.


    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

    IBM Director of Licensing
    IBM Corporation
    North Castle Drive
    Armonk, New York 10504-1785
    USA

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

    Intellectual Property Licensing
    Legal and Intellectual Property Law
    IBM Japan, Ltd.
    19-21, Nihonbashi-Hakozakicho, Chuo-ku
    Tokyo 103-8510, Japan

    Trademarks

    IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.


    Reader's Comments

    Program Directory for IBM z/OS Debugger, September 2016

    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.

    Use one of the following methods to send us your comments:

    1. Send an email to comments@us.ibm.com

    2. Use the form on the Web at:

    www.ibm.com/software/data/rcf/

    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.