I 1318041

IBM
Program Directory for

IBM Debug Tool for z/OS
IBM Problem Determination Tools
Common Components
V11.1.0
Program Number 5655-W45
FMIDs HADRB10, JADRB1J, and JADRB1K
for use with

z/OS V1.10.0 or later
Document Date: December 2010
GI13-1804-01
Note
Before using this information and the product it supports, be sure to read the general information under 7.0, “Notices” on
page 52.
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, 2010. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Debug Tool Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Program FMIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.0 Program Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 Basic Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Optional Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.1 Basic Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.2 Optional Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 Program Source Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5 Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.0 Program Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.1 Program Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Preventive Service Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 Statement of Support Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.0 Program and Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.1 Program Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.0 Installation Requirements and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.1 Driving System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.1 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.2 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2 Target System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2.1 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2.2 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2.2.1 Installation Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2.2.2 Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.2.2.3 Toleration/Coexistence Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.2.4 Incompatibility (Negative) Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.3 DASD Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.3 FMIDs Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.4 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.0 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6.1 Installing Debug Tool and Common Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.1.1 SMP/E Considerations for Installing Debug Tool and Common Components . . . . . . . . . . 34
6.1.2 SMP/E Options Subentry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.1.3 SMP/E CALLLIBS Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
© Copyright IBM Corp. 1992, 2010 iii

6.1.4 Sample Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.1.5 Set up ISPF Editor Macro (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.1.6 Allocate and Initialize the SMP/E Data Sets (Optional) . . . . . . . . . . . . . . . . . . . . . . . 41
6.1.7 Perform SMP/E RECEIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.1.8 Allocate SMP/E Target and Distribution Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.1.9 Create DDDEF Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.1.10 Perform SMP/E APPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1.11 Enable/Register Debug Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1.12 Disable Old Debug Tool Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1.13 Run the Installation Verification Programs (IVPs) . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.1.14 Verify the Debug Tool Utilities Setup Utility Function . . . . . . . . . . . . . . . . . . . . . . . 48
6.1.15 Perform SMP/E ACCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.1.16 Run REPORT CROSSZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.1.17 Cleaning Up Obsolete Data Sets, DDDEFs, and Post-Install Jobs . . . . . . . . . . . . . . . 50
6.2 Activating Debug Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.3 Activating Common Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.4 Installing and Activating CCCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.0 Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.1 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Reader's Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figures
1. Program File Content -- Debug Tool Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Program File Content -- Debug Tool Japanese . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Program File Content -- Debug Tool Korean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Program File Content -- CCCA Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Program File Content -- CCCA Japanese . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Program File Content -- Common Components Base . . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Program File Content -- Common Components Japanese . . . . . . . . . . . . . . . . . . . . . . . 9
8. Program File Content -- Common Components Korean . . . . . . . . . . . . . . . . . . . . . . . . 10
9. Basic Material: Unlicensed Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
10. Optional Material: Unlicensed Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
11. Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
12. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
13. Component IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
14. Driving System Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
15. Target System Mandatory Installation Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
16. Service Requisites for Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
17. Target System Conditional Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
iv Debug Tool Program Directory

18. Unsupported Old-levels of Requisite Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
19. Service Requisites for Subsystem and Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
20. Total DASD Space Required by Debug Tool -- Base . . . . . . . . . . . . . . . . . . . . . . . . . . 25
21. Total DASD Space Required by Debug Tool -- Japanese . . . . . . . . . . . . . . . . . . . . . . . 25
22. Total DASD Space Required by Debug Tool -- Korean . . . . . . . . . . . . . . . . . . . . . . . . 25
23. Total DASD Space Required by Common Components -- Base . . . . . . . . . . . . . . . . . . . 26
24. Total DASD Space Required by Common Components -- Japanese . . . . . . . . . . . . . . . . . 26
25. Total DASD Space Required by Common Components -- Korean . . . . . . . . . . . . . . . . . . 26
26. Storage Requirements for Debug Tool Target Libraries -- Base . . . . . . . . . . . . . . . . . . . . 27
27. Storage Requirements for Debug Tool Target Libraries -- Japanese . . . . . . . . . . . . . . . . . 28
28. Storage Requirements for Debug Tool Target Libraries -- Korean . . . . . . . . . . . . . . . . . . 29
29. Storage Requirements for Common Components Target Libraries -- Base . . . . . . . . . . . . . 29
30. Storage Requirements for Common Components Target Libraries -- Japanese . . . . . . . . . . 29
31. Storage Requirements for Common Components Target Libraries -- Korean . . . . . . . . . . . . 30
32. Storage Requirements for Debug Tool Distribution Libraries -- Base . . . . . . . . . . . . . . . . . 30
33. Storage Requirements for Debug Tool Distribution Libraries -- Japanese . . . . . . . . . . . . . . 31
34. Storage Requirements for Debug Tool Distribution Libraries -- Korean . . . . . . . . . . . . . . . 31
35. Storage Requirements for Common Components Distribution Libraries -- Base . . . . . . . . . . 31
36. Storage Requirements for Common Components Distribution Libraries -- Japanese . . . . . . . . 32
37. Storage Requirements for Common Components Distribution Libraries -- Korean . . . . . . . . . 32
38. SMP/E Options Subentry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
39. Sample Installation Jobs -- for Debug Tool Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
40. Sample Installation Jobs -- for Debug Tool Japanese . . . . . . . . . . . . . . . . . . . . . . . . . 35
41. Sample Installation Jobs -- for Debug Tool Korean . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
42. Sample Installation Jobs -- for Common Components Base . . . . . . . . . . . . . . . . . . . . . . 36
43. Sample Installation Jobs -- for Common Components Japanese . . . . . . . . . . . . . . . . . . . 36
44. Sample Installation Jobs -- for Common Components Korean . . . . . . . . . . . . . . . . . . . . 36
45. Debug Tool IVPs for Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
46. Debug Tool IVPs for Full-screen Mode using a Dedicated Terminal . . . . . . . . . . . . . . . . . 47
47. Debug Tool IVPs for Running under CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
48. Debug Tool IVP for Load Module Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
49. Debug Tool IVPs for Debug Tool Coverage Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figures v
vi Debug Tool Program Directory
1.0 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 Debug Tool for z/OS and IBM Problem Determination Tools Common Components.
This publication refers to IBM Debug Tool for z/OS as Debug Tool, and to IBM Problem Determination
Tools Common Components as Common Components.
IBM Debug Tool for z/OS also consists of IBM COBOL and CICS Command Level Conversion Aid for
OS/390 & MVS & VM, referred to as CCCA. See CCCA program directories (GI10-5080-04 and
GI10-6976-02) for information concerning the material and procedures associated with the installation of
IBM COBOL and CICS Command Level Conversion Aid for OS/390 & MVS & VM.
The Program Directory contains the following sections:

2.0, “Program Materials” on page 6 identifies the basic and optional program materials and
documentation for Debug Tool and Common Components.
3.0, “Program Support” on page 12 describes the IBM support available for Debug Tool and Common
Components.
4.0, “Program and Service Level Information” on page 14 lists the APARs (program level) and PTFs
(service level) that have been incorporated into Debug Tool and Common Components.
5.0, “Installation Requirements and Considerations” on page 17 identifies the resources and
considerations that are required for installing and using Debug Tool and Common Components.
6.0, “Installation Instructions” on page 34 provides detailed installation instructions for Debug Tool and
Common Components. It also describes the procedures for activating the functions for Debug Tool
and Common Components, or refers to appropriate publications.
Before installing Debug Tool or Common Components, 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 3.2, “Preventive Service Planning” on page 12
tells you how to find any updates to the information and procedures in this Program Directory.
Debug Tool and Common Components are 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 that is provided with your order. All service and HOLDDATA for Debug Tool are
included on the CBPDO tape.
Do not use this program directory if you install Debug Tool or Common Components with a SystemPac or
ServerPac. When you use these offerings, the jobs and documentation supplied with the offering. This
program directory can point you to specific sections of it as required.
© Copyright IBM Corp. 1992, 2010 1

1.1 Debug Tool Description
IBM Debug Tool for z/OS V11.1 helps developers debug applications running in a variety of environments,
such as batch, TSO, CICS, IMS, DB2, DB2 Stored Procedures, and UNIX System Services.
Debug Tool V11.1 includes the following new features and enhancements:
The IBM Debug Tool Plug-in for Eclipse, when integrated with Debug Tool for z/OS and CICS
Explorer, debugs z/OS-based load modules running on z/OS, including load modules that run in a
subsystem such as CICS, DB2, or IMS. The plug-in GUI interface allows you to access debugging
capability similar to that accessed by the host fullscreen interface, allowing you to do the following
tasks:
– Set and clear breakpoints at a specific line
– Set and clear breakpoints for an error or warning-level error that is based on Language
Environment severities
– Run to a breakpoint
– Step into a procedure
– Step over a procedure
– View variable values and change them as you step through the code
– View variable values in the context of a larger area of storage
– View the call stack
A new mode of operation, explicit debug mode, is now supported. In this mode, the user identifies the
compile units to debug, then Debug Tool loads debug data only for those compile units. This mode
can significantly improve debugger performance when it is debugging very large and complex
programs. This new mode is an alternative to the standard Debug Tool mode of operation where
debug data is automatically loaded for all compile units. It is intended to be used only when
debugging large, complex applications that don't perform as well in the standard Debug Tool mode.
A new user interface is added to the Terminal Interface Manager (TIM) that helps you create and
manage the TEST runtime options data set.
The TIM has been enhanced to remove the need for a site to set up a separate TN3270E port or to
customize a set of terminal LUs.
A GUI interface is added that helps you create and manage the TEST runtime options data set from
the workstation.
The Debug Tool Language Environment user exit for DB2 (EQADDCXT) now supports debugging of
DB2 stored procedures of type SUB invoked using the call_sub function.
EQAOPTS commands can now be specified at run-time in addition to the use of a user-generated
EQAOPTS load module. This allows individual users to enter EQAOPTS commands at run-time by
supplying a data set containing EQAOPTS commands.
2 Debug Tool Program Directory

Support is added for debugging of assembler programs that exploit the latest IBM zEnterprise 196
architecture.
Enhanced performance while debugging C and C++ applications.
A List pop-up window, which displays the result of the LIST expression command when the Log
window is not visible.
Support for the Enterprise PL/I ADDRDATA built-in function and "=>" operator.
Support for the Enterprise PL/I V4.1 compiler and its new GONUMBER(SEPARATE) option.
For programs compiled with any level of Enterprise PL/I, you can now list a single element of an array
of structures. For programs compiled with Enterprise PL/I V4.1, you can list a single element of an
array of structures in automonitor or use the L prefix command in the Source window to list a single
element of an array of structures.
For programs compiled with any level of Enterprise PL/I, you can now change the format in which
Debug Tool displays an array. By using the SET LIST BY SUBSCRIPT ON command, you can have
Debug Tool display the array as it is stored in memory.
A new keyword LABELS is added to the LIST NAMES command where you can list the names of all
section and paragraph names in a COBOL program, and the names of all instruction labels in an
assembler program.
The following breakpoints are enhanced:
– AT CHANGE and AT LABEL breakpoints are enhanced to allow a user to limit the scope of the
breakpoint to a specific compile unit.
– AT GLOBAL is enhanced to provide an OCCURRENCE option or wild card (*) to stop for any
condition raised in the application.
– The QUERY LOCATION command is enhanced to provide more information when Debug Tool
stops for an AT CHANGE breakpoint.
Automonitor enhancements:
– You can change the subscripts of an array directly in the Monitor window.
– You can delete multiple items from Monitor window at one time.
– You can use the cursor (in combination with the CLEAR MONITOR command) to indicate which
variable to remove from the Monitor window.
Automated allocation of the commands, log, preferences, save settings and save breakpoints and
monitor specifications files.
New functions are included in Debug Tool Utilities to help an application programmer more easily start
debugging IMS applications running in BTS.
A CICS transaction, DTNP, is provided which issues NEWCOPY or PHASEIN of application programs.
Documentation is provided to assist debugging of Language Environment C/C++, COBOL, and PLI
programs in the Java JNI environment in z/OS.
Introduction 3
IBM COBOL and CICS Command Level Conversion Aid, refered to as CCCA, helps developers convert
COBOL source from one level of COBOL to another.
Common Components delivers common components used in some of the IBM Problem Determination
Tools (which consists of IBM Application Performance Anlyzer for z/OS, IBM Fault Analyzer for z/OS, IBM
File Manager/CICS for z/OS, and IBM Debug Tool for z/OS).
1.2 Program FMIDs

Debug Tool, CCCA, and Common Components consist of the following FMIDs:
HADRB10
JADRB1J
JADRB1K
H09F210
J09F210
HVWR150
JVWR151
JVWR152
Please note, if you have installed Common Components as part of another product you do not need to
install it again.
If you order only the base feature, you will receive the following materials:
– Debug Tool base (FMID HADRB10) and Common Components base (FMID HVWR150) and its
program directory (GI13-1804-01)
– CCCA base (FMID H09F210) and its program directory (GI10-5080-04)
If you order both the base and Japanese features, you will receive the following materials:
– Debug Tool base and JPN (FMIDs HADRB10 and JADRB1J) and Common Components base
and JPN (FMIDs HVWR150 and JVWR151) and their program directory (GI13-1804-01)
– CCCA JPN (FMID J09F210) and its program directory (GI10-6976-02)
If you order both the base and Korean features, you will receive the following materials:
– Debug Tool base and KOR (FMIDs HADRB10 and JADRB1K) and Common Components base
and KOR (FMIDs HVWR150 and JVWR152) and their program directory (GI13-1804-01)
If you order all--the base, Japanese, and Korean features, you will receive the following materials:
– Debug Tool base, JPN, and KOR (FMIDs HADRB10, JADRB1J, and JADRB1K) and Common
Components base, JPN, and KOR (FMIDs HVWR150, JVWR151, and JVWR152) and their
program directory (GI13-1804-01)

– CCCA JPN (FMID J09F210) and its program directory (GI10-6976-02)
This program directory describes the installation procedure for Debug Tool (HADRB10, JADRB1J and
JADRB1K) and Common Components (HVWR150, JVWR151, and JVWR152).
Introduction 5
2.0 Program Materials
An IBM program is identified by a program number. The program number for Debug Tool is 5655-W45.
Basic Machine-Readable Materials are materials that are supplied under the base license and feature
numbers, and are required for the use of the product. Optional Machine-Readable Materials are orderable
under separate feature numbers, and are not required for the product to function.
The program announcement material describes the features supported by Debug Tool. Ask your IBM
representative for this information if you have not already received a copy.
2.1 Basic Machine-Readable Material

The distribution medium for this program is magnetic tape or downloadable files. This program is in
SMP/E RELFILE format and is installed by using SMP/E. See 6.0, “Installation Instructions” on page 34
for more information about how to install the program.
Figure 1, Figure 2 on page 7, and Figure 3 on page 7 describe the program file contents for Debug Tool.
Figure 4 on page 8 describes the program file content for CCCA. Figure 6 on page 9 describes the
program file content for Common Components. 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.
Figure 1 (Page 1 of 2). Program File Content -- Debug Tool Base

R L
E R
O C E
R F C BLK
Name G M L SIZE
SMPMCS SEQ FB 80 6400
IBM.HADRB10.F1 PDS FB 80 8800
IBM.HADRB10.F3 PDS U 0 6144
6 © Copyright IBM Corp. 1992, 2010

Figure 1 (Page 2 of 2). Program File Content -- Debug Tool Base
R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.HADRB10.F11 PDS VB 255 8800
Figure 2. Program File Content -- Debug Tool Japanese

R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.JADRB1J.F1 PDS FB 80 8800
IBM.JADRB1J.F3 PDS U 0 6144
Figure 3 (Page 1 of 2). Program File Content -- Debug Tool Korean

R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.JADRB1K.F1 PDS FB 80 8800
IBM.JADRB1K.F3 PDS U 0 6144
Program Materials 7
Figure 3 (Page 2 of 2). Program File Content -- Debug Tool Korean
R L
E R
O C E
R F C BLK
Name G M L SIZE
Figure 4. Program File Content -- CCCA Base

R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.H09F210.F1 PDS FB 80 8800
IBM.H09F210.F2 PDS VB 1028 8800
IBM.H09F210.F3 PDS U 0 6144
IBM.H09F210.F4 PDS FB 80 8800
IBM.H09F210.F5 PDS FB 80 8800
IBM.H09F210.F6 PDS FB 80 8800
IBM.H09F210.F7 PDS FB 80 8800
IBM.H09F210.F8 PDS FB 80 8800
IBM.H09F210.F9 PDS FB 40 8800
IBM.H09F210.F10 PDS FB 80 8800
Figure 5 (Page 1 of 2). Program File Content -- CCCA Japanese

R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.J09F210.F1 PDS FB 80 8800
IBM.J09F210.F2 PDS VB 1028 8800
IBM.J09F210.F3 PDS U 0 6144
IBM.J09F210.F4 PDS FB 80 8800
IBM.J09F210.F5 PDS FB 80 8800

Figure 5 (Page 2 of 2). Program File Content -- CCCA Japanese
R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.J09F210.F6 PDS FB 80 8800
Figure 6. Program File Content -- Common Components Base

R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.HVWR150.F1 PDS FB 80 8800
IBM.HVWR150.F3 PDS U 0 6144
IBM.HVWR150.F7 PDS VB 4096 27998
Figure 7. Program File Content -- Common Components Japanese

R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.JVWR151.F1 PDS FB 80 8800
IBM.JVWR151.F3 PDS U 0 6144
Program Materials 9
Figure 8. Program File Content -- Common Components Korean
R L
E R
O C E
R F C BLK
Name G M L SIZE
IBM.JVWR152.F3 PDS U 0 6144
2.2 Optional Machine-Readable Material

No optional machine-readable materials are provided for Debug Tool.
2.3 Program Publications

The following sections identify the basic and optional publications for Debug Tool.
2.3.1 Basic Program Publications

Figure 9 identifies the basic unlicensed program publications for Debug Tool. One copy of each of these
publications is included when you order the basic materials for Debug Tool. For additional copies, contact
your IBM representative.
Figure 9. Basic Material: Unlicensed Publications

Form
Publication Title Number
License Information GI11-9146
The above basic unlicensed publication is also available in displayable softcopy format (BookManager,
PDF) through the Internet. It can be viewed at http://www.ibm.com/software/awdtools/debugtool/library/.

2.3.2 Optional Program Publications
Figure 10 on page 11 identifies the optional unlicensed program publications for Debug Tool. These
publications will be available after product availability. They are also available in displayable softcopy
format (BookManager, PDF) from the Debug Tool Web site at
http://www.ibm.com/software/awdtools/debugtool/library/.
Figure 10. Optional Material: Unlicensed Publications

Form
Debug Tool Customization Guide GC27-3622
Debug Tool Reference and Messages GC27-3624
Debug Tool Reference Summary GC27-3629
Debug Tool API User's Guide and Reference SC27-3623
Debug Tool User's Guide SC27-3631
Debug Tool Coverage Utility User's Guide and Messages SC27-3632
CCCA User's Guide SC26-9400
2.4 Program Source Materials

No program source materials or viewable program listings are provided for Debug Tool.
2.5 Publications Useful During Installation

You might want to use the publications listed in Figure 11 during the installation of Debug Tool. To order
copies, contact your IBM representative or visit the IBM Publications Center at
http://www.ibm.com/shop/publications/order.
Figure 11. Publications Useful During Installation

Form
IBM SMP/E for z/OS User's Guide SA22-7773
IBM SMP/E for z/OS Commands SA22-7771
IBM SMP/E for z/OS Reference SA22-7772
IBM SMP/E for z/OS Messages, Codes, and Diagnosis GA22-7770
Program Materials 11
3.0 Program Support
This section describes the IBM support available for Debug Tool, CCCA, and Common Components.
3.1 Program Services

Contact your IBM representative for specific information about available program services.
3.2 Preventive Service Planning

Before you install Debug Tool, CCCA, and Common Components, make sure that you have reviewed the
current Preventive Service Planning (PSP) information. The PSP Buckets maintain current lists (which
have been identified since the package was created) of any recommended or required service for the
installation of this package. This service includes software PSP information (DEBUGB10, CCCA210, and
IBMPDTOOLSCC) that contains HIPER and required PTFs against the base release.
If you obtained Debug Tool, CCCA, and Common Components as part of a CBPDO, HOLDDATA is
included.
If the CBPDO for Debug Tool, CCCA, and Common Components is older than two weeks old by the time
you install the product materials, you should contact the IBM Support Center or use S/390 SoftwareXcel to
obtain the latest PSP Bucket information. You can also obtain the latest PSP Bucket information by going
to the following Web site:
https://techsupport.services.ibm.com/server/390.psp390
For program support, access the Software Support Web site at http://www.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 Debug Tool, CCCA, and Common
Components are shown as follows:
Figure 12 (Page 1 of 2). PSP Upgrade and Subset ID

UPGRADE SUBSET Description
DEBUGB10 HADRB10 Debug Tool Base
JADRB1J Debug Tool JPN
JADRB1K Debug Tool KOR
CCCA210 H09F210/0321 CCCA for OS/390 & MVS & VM Base
J09F210/0321 CCCA for OS/390 & MVS & VM JPN
IBMPDTOOLSCC HVWR150 IBM PDTCC 01.05.00 English

Figure 12 (Page 2 of 2). PSP Upgrade and Subset ID
UPGRADE SUBSET Description
IBMPDTOOLSCC JVWR151 IBM PDTCC 01.05.00 Japanese
IBMPDTOOLSCC JVWR152 IBM PDTCC 01.05.00 Korean
3.3 Statement of Support Procedures

If you have a problem with Debug Tool, CCCA, or Common Components, you can first check to see
whether the resolution to your problem is already documented in
http://www.ibm.com/software/awdtools/debugtool/support/. If you cannot find an answer, you can report
any difficulties to your IBM Support Center. If an APAR is required, the Support Center will provide the
address to which any needed documentation can be sent.
Figure 13 identifies the component IDs (COMPID) for Debug Tool.
Figure 13. Component IDs

RETAIN
FMID COMPID Component Name Release
HADRB10 5655W4500 Debug Tool Base B10
JADRB1J 5655W4500 Debug Tool JPN B1J
JADRB1K 5655W4500 Debug Tool KOR B1K
H09F210 5648B0500 CCCA for OS/390 & MVS & VM Base 210
J09F210 5648B0500 CCCA for OS/390 & MVS & VM JPN 210
HVWR150 5655IPV00 IBM Problem Determination Tools Common Components 150
JVWR151 5655IPV00 IBM PDTCC - JPN 151
JVWR152 5655IPV00 IBM PDTCC - KOR 152
Program Support 13
4.0 Program and Service Level Information
This section identifies the program and relevant service levels of Debug Tool and Common Components.
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.
4.1 Program Level Information

The following APAR fixes against previous releases of Debug Tool have been incorporated into this
release. They are listed by FMID.
FMID HADRB10
PN65602 PQ18736 PQ57686 PQ77358

PN65603 PQ20342 PQ58729 PQ77547
PN66733 PQ20561 PQ58730 PQ77824
PN69045 PQ24033 PQ59360 PQ78839
PN69895 PQ24271 PQ60272 PQ79534
PN70447 PQ24276 PQ60858 PQ79674
PN74855 PQ24651 PQ61453 PQ80030
PN74858 PQ25905 PQ61687 PQ80566
PN77047 PQ27247 PQ61884 PQ80722
PN77957 PQ29348 PQ63359 PQ80723
PN78462 PQ30470 PQ65072 PQ81519
PN80668 PQ31829 PQ65285 PQ81590
PN86092 PQ33668 PQ65689 PQ82090
PN88015 PQ37039 PQ67364 PQ82201
PN88706 PQ41451 PQ68386 PQ84175
PN88707 PQ42373 PQ68864 PQ86957
PN88762 PQ43111 PQ68865 PQ88120
PN89070 PQ43112 PQ68866 PQ88292
PQ01218 PQ48578 PQ69024 PQ89389
PQ01220 PQ48732 PQ69888 PQ89866
PQ03224 PQ49058 PQ71158 PQ90732
PQ03226 PQ49084 PQ71600 PQ92738
PQ04955 PQ49642 PQ71601 PQ92740
PQ06206 PQ53055 PQ71603 PQ92790
PQ06208 PQ53332 PQ71604 PQ93697
PQ06440 PQ54005 PQ71605 PQ94150
PQ08277 PQ54483 PQ71801 PQ94257
PQ09353 PQ54486 PQ73168 PQ94401
PQ14291 PQ55191 PQ73643 PQ95624
PQ14612 PQ55244 PQ73713 PQ95646
PQ18735 PQ55444 PQ75569 PQ95808

PQ95849 PK23759 PK53826 PK85436
PQ96818 PK25531 PK55355 PK85437
PQ98098 PK27558 PK55648 PK86668
PQ98492 PK28613 PK55719 PK87330
PQ98515 PK29548 PK56806 PK92497
PQ98516 PK30410 PK57671 PK93012
PQ98604 PK30452 PK57838 PK93688
PQ99203 PK31034 PK57955 PK93748
PQ99574 PK31038 PK58192 PK96419
PQ99811 PK32234 PK59078 PK99548
PK00675 PK32888 PK59685 PK99776
PK02447 PK33396 PK59712 PM00321
PK03374 PK34211 PK61137 PM00324
PK04009 PK34664 PK61305 PM00652
PK04304 PK35006 PK61684 PM00777
PK04961 PK35605 PK63156 PM00805
PK04962 PK35655 PK65228 PM02748
PK05285 PK36034 PK65761 PM02918
PK05466 PK36299 PK66732 PM03164
PK07204 PK36707 PK67117 PM03949
PK09226 PK37043 PK68495 PM05431
PK10061 PK37562 PK69617 PM05771
PK12158 PK38081 PK70677 PM06114
PK14451 PK39157 PK70679 PM06203
PK14572 PK40305 PK72478 PM08268
PK14577 PK41235 PK72833 PM08594
PK15170 PK41662 PK73568 PM09411
PK15398 PK42217 PK74667 PM09457
PK16153 PK43404 PK74674 PM09615
PK16434 PK45173 PK74749 PM10572
PK17078 PK46756 PK75885 PM15165
PK17670 PK47234 PK76990 PM15170
PK18521 PK48239 PK77037 PM15923
PK19156 PK48240 PK81244 PM17328
PK19177 PK49405 PK82537 PM20755
PK20260 PK50269 PK83511 PM21383
PK23019 PK50522 PK84928 PM23045
PK23176 PK53470 PK85286 PM24362
PK23583 PK53493 PK85357
FMID JADRB1J
PQ69025 PQ74715 PQ81518 PQ89216

PQ70762 PQ77407 PQ81521 PQ89229
PQ71606 PQ77825 PQ86560 PQ91311
PQ71607 PQ79675 PQ86561 PQ94949
Program and Service Level Information 15

PQ95259 PK16248 PK49389 PK78357
PQ95260 PK19327 PK50271 PK80460
PQ96148 PK21975 PK54129 PK82582
PQ97094 PK24386 PK54866 PK88857
PQ98930 PK24395 PK57111 PK89041
PQ98961 PK28015 PK59741 PK90827
PQ98963 PK31478 PK59744 PM00117
PK00799 PK33336 PK64626 PM04337
PK01491 PK33356 PK64636 PM04354
PK03524 PK35604 PK67123 PM06611
PK15090 PK35662 PK68892 PM08487
PK15093 PK42838 PK72206 PM11779
PK16025 PK44905 PK72211 PM16846
PK16030 PK49381 PK72912 PM18561
PK16157 PK49384 PK77013 PM19809
FMID JADRB1K
PK49393 PK67127 PK80462 PM04355

PK54130 PK68897 PK82583 PM06612
PK54871 PK72207 PK88858 PM08503
PK57117 PK72213 PK89042 PM11780
PK59742 PK72924 PK90828 PM16850
PK59747 PK77014 PM00118 PM18580
PK64632 PK78362 PM04351 PM19817
PK64637
The following APAR fixes against the previous release of Common Components have been incorporated
into the HVWR150 release. They are listed by FMID.
FMID HVWR140
PM05033
4.2 Service Level Information

No PTFs against this release of Debug Tool, CCCA, and Common Components have been incorporated
into the product tape.
It is highly recommended that you frequently check the Debug Tool, CCCA, and Common Components
PSP Buckets for HIPER and SPECIAL Attention PTFs against all FMIDs that you must install.

5.0 Installation Requirements and Considerations
The following sections identify the system requirements for installing and activating Debug Tool and
Common Components. The following terminology is used:
Driving system: the system used to install the program; where SMP/E executes.
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 udpates, 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
access these impacts without disrupting your production system.
5.1 Driving System Requirements

This section describes the environment of the driving system that is required to install Debug Tool and
Common Components.
5.1.1 Machine Requirements

The driving system can run in any hardware environment that supports the required software.
5.1.2 Programming Requirements
© Copyright IBM Corp. 1992, 2010 17

Figure 14. Driving System Software Requirements
Minimum
Service Level Included
will satisfy in this
Program Product Minimum these product's
Number Name VRM APARs shipment?
Any one of the following:
5694-A01 z/OS V1.10.0 or later N/A No
5655-G44 IBM SMP/E for z/OS V3.4.0 N/A No
Note: Installation may 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.
5.2 Target System Requirements

This section describes the environment of the target system that is required to install and use Debug Tool
and Common Components.
Debug Tool and Common Components install in the z/OS (Z038) SREL.
5.2.1 Machine Requirements

The target system can run in any hardware environment that supports the required software.
5.2.2 Programming Requirements
5.2.2.1 Installation Requisites: Installation requisites identify products that are required by and
must be present on the system or products that are not required by 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.

Figure 15. Target System Mandatory Installation Requisites
Minimum
Service Level Included
will satisfy in this
Program Product Minimum these product's
Number Name VRM APARs shipment?
5694-A01 z/OS V1.10.0 or later N/A No
Note: Debug Tool for z/OS V11.1 is tested and supported only for use with the currently supported levels of IBM
software and hardware.
If your operating system is z/OS V1.8 or V1.9, IBM will undertake to fix any problems that you might encounter
when running Debug Tool for z/OS V11.1 on that level of unsupported product. 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 will be developed and tested using the supported levels of IBM software. 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.
Note: Installation may 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.
Figure 16 lists the additional service requisites. Install the appropriate PTFs according to the level of your
operating system.
Figure 16 (Page 1 of 2). Service Requisites for Operating System

FMID Operating System Level PTF
HIP61A0 z/OS 1.10 UK39335
HPM7730 z/OS V1.8 UA27588 UA29931
HUN7730 z/OS V1.8 UA40845
HUN7740 z/OS V1.9 UA40846
HUN7750 z/OS V1.10 UA40847
HLE7730 z/OS V1.8 UK17253 UK17293 UK17609 UK17938 UK17950 UK18320
UK18400 UK19454 UK20247 UK20868 UK21622 UK22106
UK23535 UK24812 UK29181 UK29197 UK30496 UK30859
UK31237 UK33376 UK33605 UK35826 UK35962 UK36047
UK36327 UK37416 UK39709 UK39888 UK42536 UK43925
UK46554 UK47786 UK49113 UK49683 UK50813
UK30860 UK31238 UK33377 UK33606 UK35827 UK35963
UK36048 UK36328 UK37417 UK39710 UK39889 UK42537
UK43926 UK46555 UK47787 UK49114 UK49684 UK50814
UK56570 UK57878 UK58503
UK46556 UK47788 UK49115 UK49685 UK50815 UK56571
UK56630 UK57879 UK58504 UK60609 UK90027
Installation Requirements and Considerations 19

Figure 16 (Page 2 of 2). Service Requisites for Operating System
FMID Operating System Level PTF
UK57880 UK58505 UK60610 UK90028
HLE7770 z/OS V1.12 UK60611 UK90029
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.
Debug Tool has no conditional installation requisites.
5.2.2.2 Operational Requisites: Operational requisites are products that are required by and
must be present on the system or products that are not required by 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.
Debug Tool has no mandatory operational requisites.
Conditional operational requisites identify products that are not required for this product to operate its
basic functions but are required at run time for this product to operate specific functions. These products
are specified as IF REQs.
Figure 17 (Page 1 of 2). Target System Conditional Operational Requisites

Program Product Name and
Number Minimum VRM/Service Level Function
5696-234 High Level Assembler for MVS & VM & VSE V1.6 Debug of Assembler programs
5724-T07 Rational Developer for System z V7.5 or V7.6 Remote debug on workstation
5655-M15 CICS TS for z/OS V3.1 or V3.2 CICS support
5655-S97 CICS TS for z/OS V4.1 CICS support
5625-DB2 DB2 UDB for z/OS V8 DB2 support
5655-J38 IMS V9 IMS support

Figure 17 (Page 2 of 2). Target System Conditional Operational Requisites
5635-A01 IMS V10 IMS support
5635-A02 IMS V11 IMS support
5688-216 AD/Cycle C/370 V1.2 Debug of C/370 programs
5655-121 C/C++ for MVS/ESA V3 Debug of C/C++ programs
5694-A01 z/OS V1.10 (or later) C/C++ Element Debug of C/C++ programs
5655-H31 IBM Enterprise PL/I for z/OS V3.7 or later Debug of PL/I programs
5655-W67 IBM Enterprise PL/I for z/OS V4.1 or later Debug of PL/I programs
5655-G53 IBM Enterprise COBOL for z/OS V3.4 Debug of COBOL programs
5655-S71 IBM Enterprise COBOL for z/OS V4.1 or Debug of COBOL programs
later
5655-S14 File Manager for z/OS V8.1 Tools for working with z/OS data sets, DB2,
CICS and IMS data
5655-U29 File Manager for z/OS V9.1 Tools for working with z/OS data sets, DB2,
CICS and IMS data
5655-V52 File Manager for z/OS V10.1 Tools for working with z/OS data sets, DB2,
CICS and IMS data
5655-W47 File Manager for z/OS V11.1 Tools for working with z/OS data sets, DB2,
CICS and IMS data
5655-S15 Fault Analyzer for z/OS V8.1 Application abend analysis
5655-U28 Fault Analyzer for z/OS V9.1 Application abend analysis
5655-V51 Fault Analyzer for z/OS V10.1 Application abend analysis
5655-W46 Fault Analyzer for z/OS V11.1 Application abend analysis
Figure 18 lists the old releases of requisite products that are no longer in service.
IBM will undertake to fix any problems that you might encounter when running Debug Tool for z/OS V10.1
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 will be developed and tested
using the supported levels of IBM software. 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.

Figure 18. Unsupported Old-levels of Requisite Products
5694-A01 z/OS V1.8 or V1.9 Target system
5696-234 High Level Assembler for MVS & VM & VSE V1.5 Debug of Assembler programs via the
disassembly view
5655-147 CICS TS for OS/390 V1.3 CICS support
5697-E93 CICS TS for z/OS V2.2 or V2.3 CICS support
5675-DB2 DB2 UDB for z/OS and OS/390 V7 DB2 support
5655-B01 IMS V7 IMS support
5655-C56 IMS V8 IMS support
5647-A01 OS/390 V2.10 C/C++ Element Debug of C/C++ programs
5694-A01 z/OS V1.8 to V1.9 C/C++ Element Debug of C/C++ programs
5740-CB1 OS/VS COBOL V1.2.4 Debug of COBOL programs (with
limitations)
5668-958, VS COBOL II V1.3.1, V1.3.2, V1.4 Debug of COBOL programs (with
5688-023 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.1 through V3.3 Debug of COBOL programs
5668-909, OS PL/I V2.1, V2.2, V2.3 Debug of PL/I programs (with
5668-910 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.1 through V3.6 Debug of PL/I programs
Figure 19 lists the additional service requisites. Install the appropriate PTFs according to the subsystems
and compilers at your site.
Figure 19 (Page 1 of 3). Service Requisites for Subsystem and Compiler

FMID Subsystem/Compiler PTF
HADG810 Fault Analyzer for z/OS 8.1 UK45219
HADQ910 Fault Analyzer for z/OS 9.1 UK45132
HADL910 File Manager for z/OS 9.1 UK40694
HCI5300 CICS Transaction Server for OS/390 UQ81716 UQ82557
V1.3
HCI6200 CICS Transaction Server for z/OS V2.2 UQ81557 UQ82628

HCI6300 CICS Transaction Server for z/OS V2.3 UQ83866 UQ83946 UK22257 UK25447
UK31617
HCI6400 CICS Transaction Server for z/OS V3.1 UK11717 UK18764 UK21469 UK25495 UK31566
UK39008 UK40994
HCI6500 CICS Transaction Server for z/OS V3.2 UK27838 UK31567 UK39009 UK40995
HDB7710 DB2 UDB for z/OS and OS/390 V7 UQ57178
HLB7730 z/OS 1.8 XL C/C++ Compiler base UK23297
HLB7750 z/OS 1.9 XL C/C++ Compiler base UK50219 UK50245 UK50246 UK50645 UK51883
HLB7760 z/OS 1.10 XL C/C++ Compiler base UK51669 UK51670 UK51671
HMK8800 IMS V8 UQ79312
HMQ4150 High Level Assembler for MVS & VM & UK33757 UK40904 UK42558 UK59303
VSE V1.5
HMQ4160 High Level Assembler for MVS & VM & UK47103 UK59311
VSE V1.6
HTV7750 z/OS 1.10 Run-Time Library Extensions UK50220 UK50221 UK50252 UK50652 UK58277
Base
HTV7760 z/OS 1.11 Run-Time Library Extension UK48773 UK51673 UK51674 UK51803 UK52065
UK59787
H09F210 CCCA UK18923
H249100 COBOL for OS/390 & VM V2.1 UQ46089 UQ71481 UQ72384
H249200 COBOL for OS/390 & VM V2.2 UQ71482 UQ72385
H26L310 Enterprise COBOL for z/OS and OS/390 UQ72888
V3.1
H26L320 Enterprise COBOL for z/OS and OS/390 UK02152 UQ84365
V3.2
H26L330 Enterprise COBOL for z/OS V3.3 UK02153
H270310 Enterprise PL/I for z/OS and OS/390 UQ71463 UQ83139 UQ83548 UQ84228
V3.1
H270320 Enterprise PL/I for z/OS and OS/390 UK01924 UQ71704 UQ82334 UQ83140
V3.2 UQ83549 UQ84229 UQ96869
H270330 Enterprise PL/I for z/OS V3.3 UK01925 UQ83141 UQ83550 UQ84230
UQ85850 UQ91552 UQ96870
H270340 Enterprise PL/I for z/OS V3.4 UK00175 UK01048 UK01926 UK01955 UK30598
UQ96871

UK31028 UK39549
H270370 Enterprise PL/I for z/OS V3.7 UK31095 UK39550 UK44456
H270380 Enterprise PL/I for z/OS V3.8 UK44457
J249101 COBOL for OS/390 & VM V2.1 UQ46090
(Mixed-case English)
J249102 COBOL for OS/390 & VM V2.1 (JPN) UQ46091
JTV775J z/OS 1.10 Run-Time Library Extensions UK50449
Jpn
JTV776J z/OS 1.11 Run-Time Library Extensions UK52024
Jpn
The Code Coverage support requires the use of one of the following compilers:
C/C++ feature of OS/390 V2.6 through V2.10 (5647-A01)
OS/VS COBOL V1.2.4 (5740-CB1)
VS COBOL II V1.4.0 (5688-958, 5688-023)
COBOL for MVS & VM V1.2 (5688-197)
COBOL for OS/390 & VM V2 (5648-A25)
Enterprise COBOL for z/OS V3 (5655-G53)
Enterprise COBOL for z/OS V4 (5655-S71)
Assembler H V2 (5668-962)
High Level Assembler/MVS & VM & VSE V1.2 through V1.6 (5696-234)
OS PL/I V1.5.1 (5734-PL1, 5734-PL3)
OS PL/I V2.3 (5688-909, 5688-910)
VisualAge PL/I for OS/390 V2.2 (5655-B22)
IBM PL/I for MVS and VM V1.1.1 (5688-235)
Enterprise PL/I for z/OS V3 (5655-H31)
Enterprise PL/I for z/OS V4 (5655-W67)

5.2.2.3 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.
Debug Tool has no toleration/coexistence requisites.
5.2.2.4 Incompatibility (Negative) Requisites: Negative requisites identify products that must
not be installed on the same system as this product.
Debug Tool has no negative requisites.
5.2.3 DASD Storage Requirements

Debug Tool libraries can reside on all supported DASD types. The values below are for a 3390 DASD.
Figure 20, Figure 21, Figure 22, and Figure 23 on page 26 list the total space required for each type of
library.
Figure 20. Total DASD Space Required by Debug Tool -- Base

Library Total Space Required
Type in 3390 Trks
Target 868 Tracks
Distribution 883 Tracks
Figure 21. Total DASD Space Required by Debug Tool -- Japanese

Library
Type Total Space Required
Target 112 Tracks
Figure 22. Total DASD Space Required by Debug Tool -- Korean

Library
Type Total Space Required
Target 112 Tracks

Figure 23. Total DASD Space Required by Common Components -- Base
Type in 3390 Trks
Target 130 Tracks
Figure 24. Total DASD Space Required by Common Components -- Japanese

Type in 3390 Trks
Target 90 Tracks
Figure 25. Total DASD Space Required by Common Components -- Korean

Type in 3390 Trks
Target 90 Tracks
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 6.1.8, “Allocate SMP/E
Target and Distribution Libraries” on page 42.
3. All target and distribution libraries listed have the following attributes:
The default name of the data set may be changed.
The default block size of the data set may be changed.
The data set may be merged with another data set that has equivalent characteristics.
The data set may be either a PDS or a PDSE. However, SEQALPA and SEQAMOD must be
PDS.
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.
The following figures describe the target and distribution libraries required to install Debug Tool. The
storage requirements of Debug Tool must be added to the storage required by other programs having data
in the same library.
Note: The data in these tables should be used when determining 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.
Figure 26 (Page 1 of 2). Storage Requirements for Debug Tool Target Libraries -- Base
R L
T E R No. No.
Y O C E of of
Library Member Target P R F C 3390 DIR
DDNAME Type Volume E G M L Trks Blks
SEQALPA LMOD ANY U PDS U 0 1 1
SEQAAUTH LMOD ANY U PDS U 0 5 3
SEQAMOD LMOD ANY U PDS U 0 444 53
SEQABMOD LMOD ANY U PDS U 0 7 3
SEQASAMP Sample ANY U PDS FB 80 67 18
SEQAEXEC EXEC ANY U PDS FB 80 83 10
SEQABIN Data ANY U PDS VB 255 94 1
SEQAMENU Message ANY U PDS FB 80 1 1
SEQAPENU Panel ANY U PDS FB 80 74 49
SEQASENU Skeleton ANY U PDS FB 80 7 3

Figure 26 (Page 2 of 2). Storage Requirements for Debug Tool Target Libraries -- Base
R L
T E R No. No.
Y O C E of of
SEQATLIB Table ANY U PDS FB 80 3 2
SEQAMENP Message ANY U PDS FB 80 1 1
SEQAPENP Panel ANY U PDS FB 80 74 49
SEQASENP Skeleton ANY U PDS FB 80 7 3
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 Debug Tool Utilities" in chapter "Customizing Debug Tool
Utilities" in the Debug Tool Customization Guide, GC27-3622, for additional considerations if you want
to merge these ISPF libraries into the common system libraries.
Figure 27. Storage Requirements for Debug Tool Target Libraries -- Japanese
R L
T E R No. No.
Y O C E of of
SEQAMOD LMOD ANY S PDS U 0 6 2
SEQABMOD LMOD ANY S PDS U 0 2 1
SEQASAMP Sample ANY S PDS FB 80 2 1
SEQAEXEC EXEC ANY S PDS FB 80 2 1
SEQAMJPN Message ANY U PDS FB 80 1 1
SEQAPJPN Panel ANY U PDS FB 80 90 40
SEQASJPN Skeleton ANY U PDS FB 80 9 2
SEQAMJPN, SEQAPJPN, and SEQASJPN are ISPF libraries in Japanese.


Figure 28. Storage Requirements for Debug Tool Target Libraries -- Korean
R L
T E R No. No.
Y O C E of of
SEQAMOD LMOD ANY S PDS U 0 6 2
SEQABMOD LMOD ANY S PDS U 0 2 1
SEQASAMP Sample ANY S PDS FB 80 2 1
SEQAEXEC EXEC ANY S PDS FB 80 2 1
SEQAMKOR Message ANY U PDS FB 80 1 1
SEQAPKOR Panel ANY U PDS FB 80 90 40
SEQASKOR Skeleton ANY U PDS FB 80 9 2
SEQAMKOR, SEQAPKOR, and SEQASKOR are ISPF libraries in Korean.

Figure 29. Storage Requirements for Common Components Target Libraries -- Base
R L
T E R No. No.
Y O C E of of
SIPVMOD1 LMOD ANY U PDS U 0 50 10
SIPVSAM1 Sample ANY U PDS FB 80 10 10
SIPVPENU Panel ANY U PDS FB 80 15 15
SIPVMENU Message ANY U PDS FB 80 10 10
SIPVTENU Table ANY U PDS FB 80 10 2
SIPVBIN1 Binary (zipped) file ANY U PDS VB 4096 20 2
Figure 30 (Page 1 of 2). Storage Requirements for Common Components Target Libraries -- Japanese
R L
T E R No. No.
Y O C E of of
SIPVPJPN Panel ANY U PDS FB 80 15 15

Figure 30 (Page 2 of 2). Storage Requirements for Common Components Target Libraries -- Japanese
R L
T E R No. No.
Y O C E of of
SIPVMJPN Message ANY U PDS FB 80 10 10
SIPVTJPN Table ANY U PDS FB 80 10 2
Figure 31. Storage Requirements for Common Components Target Libraries -- Korean
R L
T E R No. No.
Y O C E of of
SIPVPKOR Panel ANY U PDS FB 80 15 15
SIPVMKOR Message ANY U PDS FB 80 10 10
SIPVTKOR Table ANY U PDS FB 80 10 2
Figure 32. Storage Requirements for Debug Tool Distribution Libraries -- Base
R L
T E R No. No.
Y O C E of of
Library P R F C 3390 DIR
DDNAME E G M L Trks Blks
AEQAMOD U PDS U 0 472 186
AEQASAMP U PDS FB 80 67 18
AEQAEXEC U PDS FB 80 83 10
AEQABIN U PDS VB 255 94 1
AEQAMENU U PDS FB 80 1 1
AEQAPENU U PDS FB 80 74 49
AEQASENU U PDS FB 80 7 3
AEQATLIB U PDS FB 80 3 2
AEQAMENP U PDS FB 80 1 1
AEQAPENP U PDS FB 80 74 49
AEQASENP U PDS FB 80 7 3
AEQAMENU, AEQAPENU, and AEQASENU are ISPF libraries in mixed-case English.

AEQAMENP, AEQAPENP, and AEQASENP are ISPF libraries in uppercase English.
Figure 33. Storage Requirements for Debug Tool Distribution Libraries -- Japanese
R L
T E R No. No.
Y O C E of of
AEQAMOD S PDS U 0 8 4
AEQASAMP S PDS FB 80 2 1
AEQAEXEC S PDS FB 80 2 1
AEQAMJPN U PDS FB 80 1 1
AEQAPJPN U PDS FB 80 70 37
AEQASJPN U PDS FB 80 7 2
AEQAMJPN, AEQAPJPN, and AEQASJPN are ISPF libraries in Japanese.
Figure 34. Storage Requirements for Debug Tool Distribution Libraries -- Korean
R L
T E R No. No.
Y O C E of of
AEQAMOD S PDS U 0 8 4
AEQASAMP S PDS FB 80 2 1
AEQAEXEC S PDS FB 80 2 1
AEQAMKOR U PDS FB 80 1 1
AEQAPKOR U PDS FB 80 70 37
AEQASKOR U PDS FB 80 7 2
AEQAMKOR, AEQAPKOR, and AEQASKOR are ISPF libraries in Korean.
Figure 35 (Page 1 of 2). Storage Requirements for Common Components Distribution Libraries -- Base
R L
T E R No. No.
Y O C E of of
AIPVMOD1 U PDS U 0 50 20
AIPVSAM1 U PDS FB 80 10 10

Figure 35 (Page 2 of 2). Storage Requirements for Common Components Distribution Libraries -- Base
R L
T E R No. No.
Y O C E of of
AIPVPENU U PDS FB 80 15 15
AIPVMENU U PDS FB 80 10 10
AIPVTENU U PDS FB 80 10 2
AIPVBIN1 U PDS VB 4096 20 2
Figure 36. Storage Requirements for Common Components Distribution Libraries -- Japanese
R L
T E R No. No.
Y O C E of of
AIPVPJPN U PDS FB 80 15 15
AIPVMJPN U PDS FB 80 10 10
AIPVTJPN U PDS FB 80 10 2
Figure 37. Storage Requirements for Common Components Distribution Libraries -- Korean
R L
T E R No. No.
Y O C E of of
AIPVPKOR U PDS FB 80 15 15
AIPVMKOR U PDS FB 80 10 10
AIPVTKOR U PDS FB 80 10 2
5.3 FMIDs Deleted

Installing Debug Tool and Common Components 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 Debug Tool and Common Components 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, see the SMP/E manuals for instructions.
5.4 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.
To prevent unauthorized execution of the AC(1) programs in the APF-authorized data set
hlq.SEQAAUTH, ensure that hlq.SEQAAUTH is access-controlled. The AC(1) programs are:
– EQAINSVC, which installs the Dynamic Debug facility SVCs.
– EQACUOIN, which installs the Debug Tool Coverage Utility SVCs.
– EQAYSESM, which is the Debug Tool Terminal Interface Manager.
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.
A portion of SEQAMOD can be placed in the MLPA. See the sample parmlib update in EQAWMLP2
in hlq.SEQASAMP for more information.

6.0 Installation Instructions
This chapter describes the installation method and the step-by-step procedures to install and to activate
the functions of Debug Tool.
Please note the following:

You can install Debug Tool into existing SMP/E zones or, optionally, into its own unique SMP/E zones.
If you want to install Debug Tool into its own SMP/E environment, a sample job, EQAWSMPE, is
provided. This job creates and initializes the SMPCSI and the SMP/E control data sets. See
Figure 39 on page 35 for more information.
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.
Information on sample jobs for installation of Common Components are also included in this section.
However, if you already have Common Components ( HVWR150 ) installed as part of the installation
of another product, there is no need to reinstall it.
6.1 Installing Debug Tool and Common Components
6.1.1 SMP/E Considerations for Installing Debug Tool and Common

Components
Use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install this release of Debug Tool and
Common Components.
6.1.2 SMP/E Options Subentry Values

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

Subentry Value Comment
DSSPACE 300,150,250 Space allocation for SMPTLIB data sets
PEMAX SMP/E Default IBM recommends using the SMP/E default for PEMAX.

6.1.3 SMP/E CALLLIBS Processing
Debug Tool uses the CALLLIBS function that is provided in SMP/E to resolve external references during
installation. When Debug Tool is installed, ensure that DDDEFs exist for the following libraries:
SCEELKED
CSSLIB
SEZATCP
Note: CALLLIBs use the previous DDDEFs only to resolve the link-edit for Debug Tool. These data sets
are not updated during the installation of Debug Tool.
6.1.4 Sample Jobs

The following sample installation jobs are provided as part of the product to help you install Debug Tool
and Common Components:
Figure 39. Sample Installation Jobs -- for Debug Tool Base

Job Name Job Type Description RELFILE
EQAWEDIT MACRO ISPF Editor macro to aid users in making changes IBM.HADRB10.F1
to the sample jobs (optional)
EQAWSMPE SMP/E Sample job to define and prime a new SMP/E CSI IBM.HADRB10.F1
(optional)
EQAWRECV RECEIVE Sample RECEIVE job IBM.HADRB10.F1
EQAWALOC ALLOCATE Sample job to allocate target and distribution IBM.HADRB10.F1
libraries
EQAWDDEF DDDEF Sample job to define SMP/E DDDEFs IBM.HADRB10.F1
EQAWAPLY APPLY Sample APPLY job IBM.HADRB10.F1
EQAWACPT ACCEPT Sample ACCEPT job IBM.HADRB10.F1
EQAWRPXZ SMP/E Sample REPORT CROSSZONE job IBM.HADRB10.F1
Figure 40. Sample Installation Jobs -- for Debug Tool Japanese

EQAWEDIJ MACRO ISPF Editor macro to aid users in making changes to IBM.JADRB1J.F1
the sample jobs (optional)
EQAWRECJ RECEIVE Sample RECEIVE job IBM.JADRB1J.F1
EQAWALOJ ALLOCATE Sample job to allocate target and distribution libraries IBM.JADRB1J.F1
EQAWDEFJ DDDEF Sample job to define SMP/E DDDEFs IBM.JADRB1J.F1
EQAWAPLJ APPLY Sample APPLY job IBM.JADRB1J.F1
EQAWACPJ ACCEPT Sample ACCEPT job IBM.JADRB1J.F1
Installation Instructions 35
Figure 41. Sample Installation Jobs -- for Debug Tool Korean
EQAWEDIK MACRO ISPF Editor macro to aid users in making changes to IBM.JADRB1K.F1
the sample jobs (optional)
EQAWRECK RECEIVE Sample RECEIVE job IBM.JADRB1K.F1
EQAWALOK ALLOCATE Sample job to allocate target and distribution libraries IBM.JADRB1K.F1
EQAWDEFK DDDEF Sample job to define SMP/E DDDEFs IBM.JADRB1K.F1
EQAWAPLK APPLY Sample APPLY job IBM.JADRB1K.F1
EQAWACPK ACCEPT Sample ACCEPT job IBM.JADRB1K.F1
Figure 42. Sample Installation Jobs -- for Common Components Base

IPVWSMPE SMP/E Sample job to define an SMP/E environment IBM.HVWR150.F2
(optional)
IPVWRECV RECEIVE Sample RECEIVE job for Common Components IBM.HVWR150.F2
IPVWALOC ALLOCATE Sample job to allocate target and distribution IBM.HVWR150.F2
libraries
IPVWDDEF DDDEF Sample job to define SMP/E DDDEFs IBM.HVWR150.F2
IPVWAPLY APPLY Sample APPLY job for Common Components IBM.HVWR150.F2
IPVWACPT ACCEPT Sample ACCEPT job for Common Components IBM.HVWR150.F2
Figure 43. Sample Installation Jobs -- for Common Components Japanese

IPVWRCVJ RECEIVE Sample RECEIVE job for Common Components IBM.JVWR151.F2
IPVWALOJ ALLOCATE Sample job to allocate target and distribution IBM.JVWR151.F2
libraries
IPVWDDFJ DDDEF Sample job to define SMP/E DDDEFs IBM.JVWR151.F2
IPVWAPLJ APPLY Sample APPLY job for Common Components IBM.JVWR151.F2
IPVWACPJ ACCEPT Sample ACCEPT job for Common Components IBM.JVWR151.F2
Figure 44 (Page 1 of 2). Sample Installation Jobs -- for Common Components Korean
IPVWRCVK RECEIVE Sample RECEIVE job for Common Components IBM.JVWR152.F2
IPVWALOK ALLOCATE Sample job to allocate target and distribution IBM.JVWR152.F2
libraries
IPVWDDFK DDDEF Sample job to define SMP/E DDDEFs IBM.JVWR152.F2

Figure 44 (Page 2 of 2). Sample Installation Jobs -- for Common Components Korean
IPVWAPLK APPLY Sample APPLY job for Common Components IBM.JVWR152.F2
IPVWACPK ACCEPT Sample ACCEPT job for Common Components IBM.JVWR152.F2
You can access the sample installation jobs by performing an SMP/E RECEIVE and then copying the jobs
from the relfiles to a work data set for editing and submission. See Figure 39 on page 35, Figure 40 on
page 35, and Figure 41 on page 35 to find the appropriate relfile data sets.
You can also copy the sample installation jobs from the tape or product files by submitting the following
jobs. 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 jobs, modify the JOB cards and
change the lowercase parameters to uppercase values to meet the requirements of your site.
To copy the sample jobs for the Debug Tool base, use this JCL.
//BASEJOBS JOB <job parameters>
//STEP1 EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=
//TAPEIN DD DSN=IBM.HADRB1.F1,UNIT=tunit,
// VOL=SER=volser,LABEL=(x,SL),
// DISP=(OLD,KEEP)
//FILEIN DD DSN=IBM.HADRB1.F1,UNIT=SYSALLDA,DISP=SHR,
// VOL=SER=filevol
//OUT DD DSNAME=jcl-library-name1,
// DISP=(NEW,CATLG,DELETE),
// VOL=SER=dasdvol,UNIT=SYSALLDA,
// SPACE=(TRK,(5,1,2))
//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSIN DD
COPY INDD=xxxxIN,OUTDD=OUT
SELECT MEMBER=(EQAWEDIT,EQAWSMPE,EQAWALOC,EQAWDDEF)
SELECT MEMBER=(EQAWRECV,EQAWAPLY,EQAWACPT,EQAWRPXZ)
/
To copy the sample jobs for the Debug Tool JPN feature, use this JCL.
//JPNJOBS JOB <job parameters>
//TAPEIN DD DSN=IBM.JADRB1J.F1,UNIT=tunit,
// DISP=(OLD,KEEP)
//FILEIN DD DSN=IBM.JADRB1J.F1,UNIT=SYSALLDA,DISP=SHR,
// VOL=SER=filevol
//OUT DD DSN=jcl-library-name2,
// SPACE=(TRK,(5,1,2))
//SYSIN DD
SELECT MEMBER=(EQAWEDIJ,EQAWALOJ,EQAWDEFJ)
SELECT MEMBER=(EQAWRECJ,EQAWAPLJ,EQAWACPJ)
/
To copy the sample jobs for the Debug Tool KOR feature, use this JCL.
//KORJOBS JOB <job parameters>
//TAPEIN DD DSN=IBM.JADRB1K.F1,UNIT=tunit,
// DISP=(OLD,KEEP)
//FILEIN DD DSN=IBM.JADRB1K.F1,UNIT=SYSALLDA,DISP=SHR,
// VOL=SER=filevol
//OUT DD DSN=jcl-library-name3,
// SPACE=(TRK,(5,1,2))
//SYSIN DD
SELECT MEMBER=(EQAWEDIK,EQAWALOK,EQAWDEFK)
SELECT MEMBER=(EQAWRECK,EQAWAPLK,EQAWACPK)
/
To copy the sample jobs for the Common Components Base, use this JCL.
//CCJOBS JOB <job parameters>
//TAPEIN DD DSN=IBM.HVWR15.F2,UNIT=tunit,
// DISP=(OLD,KEEP)
//FILEIN DD DSN=IBM.HVWR15.F2,UNIT=SYSALLDA,DISP=SHR,
// VOL=SER=filevol
// SPACE=(88,(5,2,5))
//SYSIN DD
SELECT MEMBER=(IPVWSMPE,IPVWRECV,IPVWALOC)
SELECT MEMBER=(IPVWDDEF,IPVWAPLY,IPVWACPT)
/

To copy the sample jobs for the Common Components Japanese, use this JCL.
//CCJOBJ JOB <job parameters>
//TAPEIN DD DSN=IBM.JVWR151.F2,UNIT=tunit,
// DISP=(OLD,KEEP)
//FILEIN DD DSN=IBM.JVWR151.F2,UNIT=SYSALLDA,DISP=SHR,
// VOL=SER=filevol
// SPACE=(88,(5,2,5))
//SYSIN DD
SELECT MEMBER=(IPVWRCVJ,IPVWALOJ)
SELECT MEMBER=(IPVWDDFJ,IPVWAPLJ,IPVWACPJ)
/
To copy the sample jobs for the Common Components Korean, use this JCL.
//CCJOBK JOB <job parameters>
//TAPEIN DD DSN=IBM.JVWR152.F2,UNIT=tunit,
// DISP=(OLD,KEEP)
//FILEIN DD DSN=IBM.JVWR152.F2,UNIT=SYSALLDA,DISP=SHR,
// VOL=SER=filevol
// SPACE=(88,(5,2,5))
//SYSIN DD
SELECT MEMBER=(IPVWRCVK,IPVWALOK)
SELECT MEMBER=(IPVWDDFK,IPVWAPLK,IPVWACPK)
/
See the following information to update the statements in the previous sample:
TAPEIN:
tunit is the unit value that matches the product tape.
volser is the volume serial that matches the product tape.
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 locations of IBM.HADRB10.F1,
IBM.JADRB1J.F1, IBM.JADRB1K.F1, IBM.HVWR150.F2, IBM.JVWR151.F2, and
IBM.JVWR152.F2 on the tapes.
FILEIN:
filevol is the volume serial of the DASD device where the downloaded files reside.
OUT
jcl-library-name1, jcl-library-name2, jcl-library-name3, and jcl-library-name4,
jcl-library-name5, and jcl-library-name6 are the names of the output data sets where the sample
jobs are stored.
dasdvol is the volume serial of the DASD device where the output data set resides.
SYSIN
xxxxIN is either TAPEIN or FILEIN depending on your input DD statement.
6.1.5 Set up ISPF Editor Macro (Optional)

To aid you in making changes to the Debug Tool SMP/E installation jobs:
EQAWSMPE, EQAWRECV, EQAWALOC, EQAWDDEF, EQAWAPLY, and EQAWACPT for the base
product
EQAWRECJ, EQAWALOJ, EQAWDEFJ, EQAWAPLJ, and EQAWACPJ for the Japanese feature
EQAWRECK, EQAWALOK, EQAWDEFK, EQAWAPLK, and EQAWACPK for the Korean feature
three ISPF editor macros called EQAWEDIT, EQAWEDIJ, and EQAWEDIK are copied to your output data
sets jcl-library-name1 in job BASEJOBS, jcl-library-name2 in job JPNJOBS, and jcl-library-name3 in
job KORJOBS above.
Use EQAWEDIT in jcl-library-name1 if you install only the base product. Use EQAWEDIJ in
jcl-library-name2 if you install both the base and the Japanese feature. Use EQAWEDIK in
jcl-library-name3 if you install both the base and the Korean feature.
These macros let you substitute proper values for all of the required variables in those jobs instead of
having you make the changes repeatedly by hand.
Edit macro EQAWEDIT, EQAWEDIJ, or EQAWEDIK and provide the proper values. Consult the
instructions in the macro for more information.
After making the changes, either copy EQAWEDIT, EQAWEDIJ, or EQAWEDIK to any data set in your
TSO logon procedure SYSEXEC concatenation, or issue the commands below to make EQAWEDIT,
EQAWEDIJ, or EQAWEDIK immediately accessible to your current ISPF session:

From ISPF option 6, issue:
ALLOCATE FI(SYSUEXEC) DA('dsn') SHR REU

where dsn is jcl-library-name1, jcl-library-name2,
or jcl-library-name3, depending on where your updated
EQAWEDIT, EQAWEDIJ, or EQAWEDIK resides.
ALTLIB ACTIVATE USER(EXEC)
Then edit your installation jobs from this ISPF session.
Consult the instructions in the macro on how to invoke it.
6.1.6 Allocate and Initialize the SMP/E Data Sets (Optional)

You can install Debug Tool in the same SMP/E zone as z/OS V1.10.0 (or later), or in a different zone.
If you install into existing SMP/E data sets, ensure that you have enough space.
If you plan to install into an existing zone, the cluster should have already been allocated and primed.
You can go on to the next step to perform an SMP/E RECEIVE.
To install into a new zone, edit and submit sample job EQAWSMPE to define and prime a new SMP/E
CSI cluster. Consult the instructions in the sample job for more information.
To create a separate SMP/E environment for Common Components, edit and submit the sample job
IPVWSMPE. Consult the instructions in the sample job for information about statements you will need
to change to meet your requirements.
Expected Return Codes and Messages: You will receive a return code of 0 if the job runs correctly.
6.1.7 Perform SMP/E RECEIVE

If you have obtained Debug Tool as part of a CBPDO, use the RCVPDO job in the CBPDO RIMLIB data
set to receive the Debug Tool FMIDs, service, and HOLDDATA that are included on the CBPDO tape. 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
Debug Tool. 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.
Edit and submit the sample job IPVWRECV to perform the SMP/E RECEIVE for Common Components.
Consult the instructions in the sample job for more information.
If your order contains the Japanese feature, edit and submit sample job IPVWRCVJ to perform the SMP/E
If your order contains the Korean feature, edit and submit sample job IPVWRCVK to perform the SMP/E
Expected Return Codes and Messages: You will receive return codes of 0s if all jobs run correctly.
6.1.8 Allocate SMP/E Target and Distribution Libraries

Edit and submit sample job EQAWALOC to allocate the libraries for Debug Tool. 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 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 target
Edit and submit sample job IPVWALOC to allocate the SMP/E target and distribution libraries for Common
Components. Consult the instructions in the sample job for more information.
If your order contains the Japanese feature, edit and submit sample job IPVWALOJ to allocate the target
If your order contains the Korean feature, edit and submit sample job IPVWALOK to allocate the target
6.1.9 Create DDDEF Entries

Edit and submit sample job EQAWDDEF to create DDDEF entries for the SMP/E target and distribution
libraries for Debug Tool. Since library AEQASRC2 is no longer used as of Debug Tool V1.3, ensure that
you do not refer to it in your SYSLIB concatenation. 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 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
Edit and submit sample job IPVWDDEF to create DDDEF entries for the SMP/E target and distribution
libraries for Common Components. Consult the instructions in the sample job for more information.

If your order contains the Japanese feature, edit and submit sample job IPVWDDFJ to create DDDEF
If your order contains the Korean feature, edit and submit sample job IPVWDDFK to create DDDEF
Apply processing for Common Components does not use the CALLIBs function.
6.1.10 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 Debug Tool. 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
information.
HOLDDATA introduces ERROR HOLDs against FMIDs for HIPER APARs. Before the installation,
ensure that you have the latest HOLDDATA, which is available through several different portals,
including http://service.software.ibm.com/holdata/390holddata.html. Install the FMIDs regardless of the
status of unresolved HIPERs. However, don't deploy the software until the unresolved HIPERs are
analyzed to determine applicability.
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. This is because 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 two methods to install FMIDs when ++HOLDs for HIPERs exist for the FMIDs that you
install:
a. To ensure that all recommended and critical service is installed with the FMIDs, if you are using
SMP/E 3.5 or higher and have received the latest HOLDDATA, add the FIXCAT operand to the
APPLY command as shown below. If you are using a prior release of SMP/E, add the
SOURCEID(HIPER,RSU*) operand to the APPLY command.
If using SMP/E V3.5 or higher:
APPLY S(fmid,fmid,...)
FORFMID(fmid,fmid,...)
SOURCEID(RSU)
FIXCAT(IBM.ProductInstall.RequiredService)
GROUPEXTEND .
If using SMP/E V3.4 or prior:
SOURCEID(HIPER,RSU)
GROUPEXTEND .
Some HIPER APARs might not have PTFs available yet. You have to analyze the symptom flags
to determine if you want to bypass the specific ERROR HOLDs and continue the installation of the
FMIDs.
This method requires more initial research, but can provide resolution for all HIPERs that have
fixes available and are not in a PE chain. Unresolved PEs or HIPERs might still exist and require
the use of BYPASS.
b. To install the FMIDs without regard for the HIPERs, you can add a
BYPASS(HOLDCLASS(HIPER)) operand to the APPLY command. In this way, you can install
FMIDs even though HIPER ERROR HOLDs against them still exist. Only the HIPER ERROR
HOLDs are bypassed. After the FMIDs are installed, run the SMP/E REPORT ERRSYSMODS
command to identify missing HIPER maintenance.
SOURCEID(RSU)
GROUPEXTEND
BYPASS(HOLDCLASS(HIPER)) .
..any other parameters documented in the program directory
This method is the quicker of the two, but requires subsequent review of the REPORT
ERRSYSMODS to investigate any HIPERs. If you are running SMP/E V3.5 or higher and have
received the latest HOLDDATA, you can also choose to run REPORT MISSINGFIX for Fix
Category IBM.ProductInstall.RequiredService to investigate missing recommended service.
If you bypass HOLDs during the installation of the FMIDs because PTFs are not yet available, you
can make yourself notified when the 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 operands and run
the job(s) 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.
3. Edit and submit sample job IPVWAPLY to perform an SMP/E APPLY CHECK for Common
Components.

If your order contains the Japanese feature, edit and submit sample job IPVWAPLJ to perform an
information.
If your order contains the Korean feature, edit and submit sample job IPVWAPLK to perform an
information.
4. After you take actions that are indicated by the APPLY CHECK, remove the CHECK operand and run
the job(s) again to perform the APPLY. Consult the instructions in the sample job for more
information.
Expected Return Codes and Messages from APPLY: You will receive return codes of 0s if all jobs
run correctly.
6.1.11 Enable/Register Debug Tool

Ensure that you enable/register Debug Tool before running any applications or any of the Installation
Verification Programs below. To do this, include an entry for Debug Tool in the IFAPRDxx parmlib
member as follows:
PRODUCT OWNER('IBM CORP')
NAME('IBM DEBUG TOOL')
ID(5655-W45)
VERSION() RELEASE() MOD()
FEATURENAME('IBM-DEBUG')
STATE(ENABLED)
Sample registration parmlib entry EQAWIFA, which contains the above statements, is provided in your
hlq.SEQASAMP data set. Update your IFAPRDxx member with the information shown in EQAWIFA.
After you have updated IFAPRDxx, issue the SET PROD=xx operator command. Debug Tool will then be
enabled in your z/OS environment.
6.1.12 Disable Old Debug Tool Registration

It is recommended that you remove all old registration entries that belonged to 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 IFAPRDxx parmlib to
STATE(NOTDEFINED). Then issue a SET PROD=xx operator command.
2. Remove the old entries from IFAPRDxx.
6.1.13 Run the Installation Verification Programs (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 6.1.16, “Run REPORT
CROSSZONE” on page 50.
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 hlq.SEQASAMP library.
Figure 45 lists the IVPs for batch mode.
Figure 45 (Page 1 of 2). Debug Tool IVPs for Batch Mode

IVP Name Description
EQAWIVPA1 Dynamic Debug facility and Language Environment Assembler
EQAWIVPC1 Dynamic Debug facility and Non-Language Environment Assembler
EQAWIVPF1 Dynamic Debug facility and Enterprise PL/I TEST(ALL,SYM,NOHOOK)
EQAWIVPG z/OS C DEBUG(FORMAT(DWARF),HOOK(LINE,NOBLOCK,PATH),SYMBOL)
EQAWIVPI1 Dynamic Debug facility and Enterprise PL/I TEST(ALL,SYM,NOHOOK,SEPARATE)
EQAWIVPP1 Dynamic Debug facility and COBOL TEST(NONE,SYM,SEPARATE)
COBOL for OS/390 & VM
Enterprise COBOL for z/OS
EQAWIVPS1 Dynamic Debug facility and Disassembly
EQAWIVPV1 Dynamic Debug facility and OS/VS COBOL
EQAWIVPX1 Dynamic Debug facility and Non-Language Environment VS COBOL II
EQAWIVP1 COBOL TEST(ALL)
COBOL for MVS & VM
EQAWIVP2 C TEST(ALL)
EQAWIVP3 PL/I for MVS & VM TEST(ALL)
EQAWIVP41 Dynamic Debug facility and COBOL TEST(NONE,SYM)

Figure 45 (Page 2 of 2). Debug Tool IVPs for Batch Mode
EQAWIVP8 VisualAge or Enterprise PL/I TEST(ALL)
Note:
1. See chapter "Installing the Dynamic Debug facility" of the Customization Guide before running these particular
IVPs.
Figure 46 lists the IVPs for full-screen mode using a dedicated terminal.
Figure 46. Debug Tool IVPs for Full-screen Mode using a Dedicated Terminal
EQAWIVPB2 Dynamic Debug facility and Language Environment Assembler
EQAWIVPD2 Dynamic Debug facility and Non-Language Environment Assembler
EQAWIVPW2 Dynamic Debug facility and OS/VS COBOL
EQAWIVPY2 Dynamic Debug facility and Non-Language Environment VS COBOL II
EQAWIVP51 COBOL TEST(ALL)
COBOL for MVS & VM
Enterprise COBOL for z/OS and OS/390
EQAWIVP61 C TEST(ALL)
EQAWIVP71 PL/I for MVS & VM TEST(ALL)
EQAWIVP91 VisualAge or Enterprise PL/I TEST(ALL)
Note:
1. See chapter "Enabling debugging in full-screen mode using a dedicated terminal" in the Customization Guide
before running these IVPs.
2. See chapter "Enabling debugging in full-screen mode using a dedicated terminal" and chapter "Installing the
Dynamic Debug facility" before running these IVPs. Both of these chapters are in the Customization Guide.
Figure 47 lists the IVPs for running under CICS.
Figure 47 (Page 1 of 2). Debug Tool IVPs for Running under CICS
EQAWIVCC2 Dynamic Debug facility and Non-Language Environment Assembler
EQAWIVCG1 z/OS C DEBUG(FORMAT(DWARF),HOOK(LINE,NOBLOCK,PATH),SYMBOL)
EQAWIVCI2 Dynamic Debug facility and Enterprise PL/I TEST(ALL,SYM,NOHOOK,SEPARATE)
EQAWIVCP2 Dynamic Debug facility and COBOL TEST(NONE,SYM,SEPARATE)
EQAWIVC21 C TEST(ALL)
Figure 47 (Page 2 of 2). Debug Tool IVPs for Running under CICS
EQAWIVC81 VisualAge or Enterprise PL/I TEST(ALL)
Note:
1. See chapter "Adding support for debugging under CICS" in the Customization Guide before running these
IVPs.
2. See chapter "Adding support for debugging under CICS" and chapter "Installing the Dynamic Debug facility"
before running these IVPs. Both of these chapters are in the Customization Guide.
Figure 48 lists the IVP for Load Module Analyzer.
Figure 48. Debug Tool IVP for Load Module Analyzer

EQAWLMA Load Module Analyzer
Figure 49 lists the IVPs for Debug Tool Coverage Utility.
Figure 49. Debug Tool IVPs for Debug Tool Coverage Utility
EQACU1VM COBOL for MVS & VM
EQACU2VM PL/I for MVS & VM
EQACU2VV VisualAge PL/I
EQACU2VZ Enterprise PL/I for z/OS
EQACU3VA OS/390 C V2.6 & V2.10
EQACU4VL High Level Assembler
Note:
See section "Customizing Coverage Utility" in chapter "Customizing Debug Tool Utilities" of the Customization
Guide before running these IVPs.
6.1.14 Verify the Debug Tool Utilities Setup Utility Function

You can verify the installation and customization of the Debug Tool Utilities Setup Utility function by
following one (or more) of the samples described in "Appendix D. Examples: Preparing programs and
modifying setup files with Debug Tool Utilities" in the User's Guide. See "Customizing Debug Tool
Utilities" in the Customization Guide first for customization information.

6.1.15 Perform SMP/E ACCEPT
Edit and submit sample job EQAWACPT to perform an SMP/E ACCEPT CHECK for Debug Tool. 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
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. This is because the SMP/E root cause analysis identifies the
cause of only 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 manuals.
After you take actions that are indicated by the ACCEPT CHECK, remove the CHECK operand and run
the job(s) 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.
Edit and submit sample job IPVWACPT to perform an SMP/E ACCEPT CHECK for Common
Components. Consult the instructions in the sample jobs for more information.
If your order contains the Japanese feature, edit and submit sample job IPVWACPJ to perform an SMP/E
If your order contains the Korean feature, edit and submit sample job IPVWACPK to perform an SMP/E
After you take actions that are indicated by the ACCEPT CHECK, remove the CHECK operand and run
the job(s) again to perform the ACCEPT.
Expected Return Codes and Messages from ACCEPT CHECK: You will receive return codes of 0s if
all jobs run correctly.
If PTFs that contain replacement modules are accepted, SMP/E ACCEPT processing will link-edits or
binds 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 return codes of 0s if all jobs
run correctly.
6.1.16 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 Debug Tool, 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.
Edit and submit sample job EQAWRPXZ to run the REPORT CROSSZONE for Debug Tool. Consult the
instructions in the sample job for more information.
Expected Return Codes and Messages: You will receive a return code of 0 if the job runs correctly.
For more information about REPORT CROSSZONE, see the SMP/E manuals.
6.1.17 Cleaning Up Obsolete Data Sets, DDDEFs, and Post-Install Jobs

The following data sets, allocated and used by previous releases of this product, are no longer used in this
release. You may choose to delete these obsolete data sets, with the exception of LPALIB, after you
delete the previous release from your system.
SEQACLIS, SEQADUM, SEQAIENU, SEQALPA, SEQAOS2, SEQAPROC, SEQA2ENU: obsolete as
of Debug Tool V1.3.0.
LPALIB is no longer required as of Debug Tool V4.1. However, if you install Debug Tool V11.1 in a
zone that currently contains an old release of Debug Tool, ensure that you leave the existing LPALIB
allocated so that SMP/E can perform the proper cleanup. After you complete the installation of Debug
Tool V11.1, do not delete this data set as it may contain other products' modules.
SEQALPA, which was obsolete as of Debug Tool V1.3, is now required as of Debug Tool V4.1.
SEQAMLIB, SEQAPLIB, SEQASLIB: obsolete as of Debug Tool V3.1.0.
AEQACLIS, AEQAIENU, AEQAMOD2, AEQAOS2, AEQASRC2, AEQA2ENU: obsolete as of Debug
Tool V1.3.0.
AEQAMLIB, AEQAPLIB, AEQASLIB: obsolete as of Debug Tool V3.1.0.
The following DDDEF entries, created and used by previous releases of this product, are no longer used
in this release. You may choose to delete these obsolete DDDEF entries after you delete the previous
release from your system.

SEQACLIS, SEQADUM, SEQAIENU, SEQALPA, SEQAOS2, SEQAPROC, SEQA2ENU: obsolete as
of Debug Tool V1.3.0.
LPALIB is no longer required as of Debug Tool V4.1. However, if you install Debug Tool V10.1 in a
zone that currently contains an old release of Debug Tool, ensure that you leave the existing DDDEF
entry for LPALIB defined so that SMP/E can perform the proper cleanup. After completing the
installation of Debug Tool V11.1, you can delete this obsolete DDDEF entry.
SEQALPA, which was obsolete as of Debug Tool V1.3, is now required as of Debug Tool V4.1.
SEQAMLIB, SEQAPLIB, SEQASLIB: obsolete as of Debug Tool V3.1.0.
AEQACLIS, AEQAIENU, AEQAMOD2, AEQAOS2, AEQASRC2, AEQA2ENU: obsolete as of Debug
Tool V1.3.0.
AEQAMLIB, AEQAPLIB, AEQASLIB: obsolete as of Debug Tool V3.1.0.
The post-install jobs EQAWLU62 and EQAWLECS are also obsolete as of Debug Tool V1.3.0, and are no
longer needed.
6.2 Activating Debug Tool

The publication Debug Tool Customization Guide, GC27-3622, contains the step-by-step procedures to
activate and customize the functions of Debug Tool.
The publication Debug Tool User's Guide, SC27-3631, 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
Debug Tool.
6.3 Activating Common Components

The publication Debug Tool Customization Guide, GC27-3622, Chapter 16, "Adding support for remote
debug users", contains step-by-step procedures to activate and customize Common Components.
6.4 Installing and Activating CCCA

See the CCCA program directories GI10-5080-04 (Base) and GI10-6976-02 (JPN) for instructions on how
to install and activate IBM COBOL and CICS Command Level Conversion Aid for OS/390 & MVS & VM.
7.0 Notices
References in this document to IBM products, programs, or services do not imply that IBM intends to
make these available in all countries in which IBM operates. Any reference to an IBM product, program,
or service is not intended to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual
property rights may be used instead of the IBM product, program, or service. Evaluation and verification
of operation in conjunction with other products, except those expressly designated by IBM, is the user's
responsibility.
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
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1099 785
USA
For online versions of this book, we authorize you to:

Copy, modify, and print the documentation contained on the media, for use within your enterprise,
provided you reproduce the copyright notice, all warning statements, and other required statements on
each copy or partial copy.
Transfer the original unaltered copy of the documentation when you transfer the related IBM product
(which may be either machines you own, or programs, if the program's license terms permit a
transfer). You must, at the same time, destroy all other copies of the documentation.
You are responsible for payment of any taxes, including personal property taxes, resulting from this
authorization.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply
to you.

Your failure to comply with the terms above terminates this authorization. Upon termination, you must
destroy your machine readable documentation.
7.1 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.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Notices 53
Reader's Comments
Program Directory for IBM Debug Tool for z/OS, December 2010
You may use this form to comment about this document, its organization, or subject matter with the understanding that
IBM may use or distribute whatever information you supply in any way it believes appropriate without incurring any
obligation to you.
For each of the topics below please indicate your satisfaction level by circling your choice from the rating scale. If a
statement does not apply, please circle N.
RATING SCALE
very very not
satisfied <=====================> dissatisfied applicable
1 2 3 4 5 N
Satisfaction
Ease of product installation 1 2 3 4 5 N
Contents of Program Directory 1 2 3 4 5 N
Installation Verification Programs 1 2 3 4 5 N
Time to install the product 1 2 3 4 5 N
Readability and organization of Program Directory tasks 1 2 3 4 5 N
Necessity of all installation tasks 1 2 3 4 5 N
Accuracy of the definition of the installation tasks 1 2 3 4 5 N
Technical level of the installation tasks 1 2 3 4 5 N
Ease of getting the system into production after 1 2 3 4 5 N
installation
How did you order this product?

CBPDO
CustomPac
ServerPac
Independent
Other
Is this the first time your organization has installed this product?
Yes
No
Were the people who did the installation experienced with the installation of z/OS products?
Yes

No
If yes, how many years? __
If you have any comments to make about your ratings above, or any other aspect of the product installation, please
list them below:
Please provide the following contact information:
Name and Job Title
Organization
Address
Telephone
Thank you for your participation.
Please send the completed form to (or give to your IBM representative who will forward it to the IBM Debug Tool for
z/OS Development group):
IBM Corporation, Dept. 8X9A/F354

555 Bailey Avenue
San Jose, CA 95141
USA
FAX Number: (800) 426-7773 in the United States of America
E-Mail: comments@us.ibm.com
Reader's Comments 55
IBM
Printed in USA
GI13-184-1

I 1318041

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

I 1318041

Uploaded by

Copyright:

Available Formats

IBM

Program Directory for

FMIDs HADRB10, JADRB1J, and JADRB1K

for use with

Document Date: December 2010

2.0 Program Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.0 Program Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.0 Program and Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5.0 Installation Requirements and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6.0 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

© Copyright IBM Corp. 1992, 2010 iii

iv Debug Tool Program Directory

The Program Directory contains the following sections:

© Copyright IBM Corp. 1992, 2010 1

2 Debug Tool Program Directory

1.2 Program FMIDs

4 Debug Tool Program Directory

2.1 Basic Machine-Readable Material

Figure 1 (Page 1 of 2). Program File Content -- Debug Tool Base

6 © Copyright IBM Corp. 1992, 2010

Figure 2. Program File Content -- Debug Tool Japanese

Figure 3 (Page 1 of 2). Program File Content -- Debug Tool Korean

Figure 4. Program File Content -- CCCA Base

Figure 5 (Page 1 of 2). Program File Content -- CCCA Japanese

8 Debug Tool Program Directory

Figure 6. Program File Content -- Common Components Base

Figure 7. Program File Content -- Common Components Japanese

2.2 Optional Machine-Readable Material

2.3 Program Publications

2.3.1 Basic Program Publications

Figure 9. Basic Material: Unlicensed Publications

10 Debug Tool Program Directory

Figure 10. Optional Material: Unlicensed Publications

2.4 Program Source Materials

2.5 Publications Useful During Installation

Figure 11. Publications Useful During Installation

3.1 Program Services

3.2 Preventive Service Planning

Figure 12 (Page 1 of 2). PSP Upgrade and Subset ID

12 © Copyright IBM Corp. 1992, 2010

3.3 Statement of Support Procedures

Figure 13 identifies the component IDs (COMPID) for Debug Tool.

Figure 13. Component IDs

4.1 Program Level Information

PN65602 PQ18736 PQ57686 PQ77358

14 © Copyright IBM Corp. 1992, 2010

PQ69025 PQ74715 PQ81518 PQ89216

Program and Service Level Information 15

PK49393 PK67127 PK80462 PM04355

4.2 Service Level Information

16 Debug Tool Program Directory

Use separate driving and target systems in the following situations:

5.1 Driving System Requirements

5.1.1 Machine Requirements

5.1.2 Programming Requirements

© Copyright IBM Corp. 1992, 2010 17

5.2 Target System Requirements

5.2.1 Machine Requirements

5.2.2 Programming Requirements

18 Debug Tool Program Directory

Figure 16 (Page 1 of 2). Service Requisites for Operating System

Installation Requirements and Considerations 19