|
IBM United States
Software Announcement 202-194 August 20, 2002 IBM Debug Tool for z/OS and OS/390 V3.1
At a GlanceIBM Debug Tool for z/OS and OS/390 V3.1 helps examine, monitor, and control the execution of application programs by enabling you to:
Debug Tool also supports many programming languages and numerous execution environments. For ordering, contact: Your IBM representative, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL (Reference: LE001). OverviewIBM Debug Tool for z/OS™ and OS/390® V3.1 is IBM's interactive source-level debugging tool for compiled applications. It is a program testing and analysis aid that helps you examine, monitor, and control the execution of application programs written in C/C++, COBOL, PL/I, High Performance Java™ (HPJ), or Assembler (by using the disassembly view) on a z/OS or OS/390 system. Debug Tool also provides support of applications that include other languages by using the disassembly view. Debug Tool supports debugging of application programs in various environments, including:
V3.1 provides enhanced optimized code debug capability for COBOL programs. Key Prerequisites
DescriptionInteractive Full-Screen Debugging: Using the full-screen interface, you can interactively debug any application as it runs (including batch applications). You can start Debug Tool when an application is initialized, or it can be started dynamically when a condition occurs. The application itself can also start Debug Tool. The full-screen interface is divided into three windows:
The available PF keys are displayed at the bottom of the screen. These provide a basic set of screen manipulation and debugging commands. You can customize the screen display and these keys to suit your testing and development needs. Separate File Support and Dynamic Debug Support: Debug Tool supports COBOL production load modules compiled with the SEPARATE suboption of TEST, such as TEST (NONE, SYM, SEPARATE). This suboption causes the compiler to create the debug information in a separate file. In addition, the need to have compiled-in hooks for Debug Tool to control the application has been removed with the addition of the Dynamic Debug Support. The SEPARATE suboption permits debugging of a load module that does not have debug information embedded in the load module. The combination of this new compile option and Dynamic Debug support allows you to generate load modules which are smaller in size and do not have compiled-in hooks, while retaining the ability to use all of the features of Debug Tool without compromising the performance of the application when deployed in a production environment. Optimized COBOL Code Debug Support: This support provides enhanced optimized code debug capability for COBOL programs compiled with the OPT (STD) or OPT (FULL) compiler options. You can set breakpoints to suspend the execution of the program, and inspect the contents of data items. You can step through your program one statement at a time, or resume execution until the next breakpoint is encountered. Source-level Debugging: You can monitor source code for C/C++, HPJava, PL/I (when used with Enterprise PL/I V3) or a compiler listing for COBOL and PL/I. Compiler listings are an expanded source listing that, in addition to program source, contains copy book source for COBOL or include file source for PL/I. Mixed-Language Applications Debugging: Debug Tool supports seamless debugging of mixed-language applications within the same session, and recognizes when the current programming language changes. Language modules not supported by Debug Tool are tolerated; debugging support is provided only through the disassembly view. Dynamic Patching: For each supported programming language, there is a set of interpreted commands that you can use to specify actions to be taken. These commands are subsets of the programming languages, so they are easy to learn, and allow you to make adjustments to your application while you debug it. You can use the commands to alter the value of variables and structures, and to control the flow of an application. For example, a programmer can declare a new variable and use the variable to patch a program as it executes. Dynamic Breakpoint Setting: You can set breakpoints in an application program, monitor variables for changes, and watch for specified exceptions and conditions during program execution. For example, you can cause an application to stop when a specific variable or location in storage is changed. You can set, change, and remove breakpoints as you go through the application. You do not need to know where you want to set a breakpoint before you start. Single-Step Debugging: To focus on a problem area, you can step line by line through the execution of an application. For example, when an application stops for a breakpoint, you can carefully examine each line that follows. Single-step debugging, along with the ability to set dynamic breakpoints, allows you to monitor, interrupt, and continue through the flow of the program to identify errors easily. Program Frequency Counting: Debug Tool counts how many times a statement or verb has been processed in an application program. This helps you to verify the coverage of your code paths. Program Information Gathering: Debug Tool can display program and environment information. You can display, monitor, and alter program variables or storage in real time. You can also check how your application was compiled, and look at its structure. Session Logging: Each debug session can be recorded in a log file for reviewing, editing, or replaying. This allows you to replay the actions taken in a session to pinpoint errors in an application. General Testing: You can also use Debug Tool as a test tool. By using the session logging feature as you debug code, you can save the results of your session for use as input to a future Debug Tool session. As you make changes to your code, you can use the saved log file as input to Debug Tool in order to verify that no unexpected behavior occurs as a result of these changes. Session logging allows you to create suites of regression test cases that you can use to minimize the number of defects introduced during the normal application development process. Setup Utility: The Debug Tool setup utility helps you create a setup file that contains information about your program. The setup file contains information on file allocation, run-time options, program parameters, and the name of the program to be executed. The setup utility also provides a run command which can perform the file allocations and then start the program with the specified options in a foreground environment. The setup utility can also submit a batch job that does file allocations and starts the program with the specified options in a batch environment. Hardware and Software Support ServicesSmoothStart™/Installation ServicesIBM SmoothStart and Installation Services are not provided.
Trademarks
Technical InformationSpecified Operating EnvironmentHardware Requirements
Debug Tool for z/OS™ and OS/390® will run on any hardware
configuration supported by the licensed programs specified below.
Software RequirementsUnless otherwise announced by IBM, Debug Tool for z/OS and OS/390 runs under the control of, or in conjunction with, the currently supported releases of the following programs and their subsequent releases or their equivalents. For more information on programs listed below that require program temporary fixes (PTFs), refer to the program directory, the customization guide, and the PSP bucket for this product. Required Licensed Programs
Optional Licensed Programs
Planning InformationThe Debug Tool for z/OS and OS/390 V3.1 package includes:
Security, Auditability, and ControlThe announced program uses the security and auditability features of the host operating system software. The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities. Ordering InformationNew Licensees
Entry Support License (ESL): To order an ESL license, specify the program number, feature number 9001 for asset registration, and the applicable ESL one-time charge (OTC) feature number. Also specify the feature number of the desired distribution medium.
Program Number/ ESL OTC Description Feature Number IBM Debug Tool for 0015 z/OS and OS/390 V3 (5655-H32) ESL machines can be determined by referring to the IBM Entry End User/390 Attachment (Z125-4379). Parallel Sysplex® License Charge (PSLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the PSLC Base feature. If applicable, specify the PSLC Level A and PSLC Level B, and PSLC Level C, and PSLC Level D features and quantity. If there is more than one program copy in a Parallel Sysplex, the charge for all copies is associated to one license by specifying the applicable PSLC feature numbers and quantity represented by the sum of the Service Units in Millions (MSUs) in your Parallel Sysplex. For all other program copies, specify the PSLC No-Charge (NC) Identifier feature on the licenses. Also, specify the feature number of the desired distribution medium.
PSLC PSLC Basic License
Machine Feature MLC Feature
MSU Capacity Number Description
1 0001 PSLC Base, 1 MSU
2 0002 PSLC Base, 2 MSUs
3 0003 PSLC Base, 3 MSUs
4 -- 45 0004 PSLC Level A, 1 MSU
0005 PSLC Level A, 42 MSUs
46 -- 175 0006 PSLC Level B, 1 MSU
0007 PSLC Level B, 10 MSUs
0008 PSLC Level B, 50 MSUs
176 -- 315 0009 PSLC Level C, 1 MSU
0010 PSLC Level C, 10 MSUs
0011 PSLC Level C, 50 MSUs
316 or more 0012 PSLC Level D, 1 MSU
0013 PSLC Level D, 50 MSUs
NA 0014 PSLC NC IDENTIFIER
NA = Not Applicable
Example 1: For a single machine with 11 MSUs, the PSLC features to be ordered would be:
Example 2: For two machines in a Parallel Sysplex, which have an aggregation of 60 MSUs, the PSLC features to be ordered would be:
Workload License Charge (WLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Also, specify the feature number of the desired distribution medium. Variable Workload License Charge Features (VWLC)
VWLC VWLC MLC Feature Feature Description Number Base, Level 1 includes 45 MSUs 0019 Additional quantity, Level 1 up to 175 MSUs 0020 Additional quantity, Level 2 176 -- 315 MSUs 0021 Additional quantity, Level 3 316 -- 575 MSUs 0022 Level 3, Per 50 MSUs for machine capacity of 316 -- 575 MSUs 0023 VWLC VWLC MLC Feature Feature Description Number Additional quantity, Level 4 576 -- 875 MSUs 0024 Level 4, Per 50 MSUs for machine capacity of 576 -- 875 MSUs 0025 Additional quantity, Level 5 876+ MSUs 0026 Level 5, Per 50 MSUs for machine capacity of 876+ MSUs 0027 Registration Base, Level 1 includes 1 MSU 0028 Registration additional quantity Level 1 up to 175 MSUs 0029 Registration additional quantity Level 2 176 -- 315 MSUs 0030 Registration additional quantity Level 3 316 -- 575 MSUs 0031 Registration additional quantity Per 50 MSUs for machine Level 3 316 -- 575 MSUs 0032 Registration additional quantity Level 4 576 -- 875 MSUs 0033 Registration additional quantity Per 50 MSUs for machine Level 4 576 -- 875 MSUs 0034 Registration additional quantity Level 5 876+ MSUs 0035 Registration additional quantity Per 50 MSUs for machine Level 5 876+ MSUs 0036 Growth Opportunity License Charge (GOLC): To order a GOLC software, specify the program number, feature number 9001 for asset registration, and the GOLC monthly charge feature number from the table below. Also, specify the feature number for the desired distribution medium.
GOLC GOLC Category Feature Number H30 0016 H50 0017 H70 0018 zSeries Entry License Charge (zELC): To order zELC software, specify the program number, feature number 9001 for asset registration, and the zELC monthly charge feature number from the table below. Also, specify the feature number for the desired distribution medium.
z800 Models zELC Feature Number 0A1 -- 1 engine 0037 0B1 -- 1 engine 0038 0C1 -- 1 engine 0039 001 -- 1 engine 0040 0A2 -- 2 engines 0041 002 -- 2 engines 0042 003 -- 3 engines 0043 004 -- 4 engines 0044 Single Version Charging: To elect single version charging, the customer must notify and identify to IBM the prior program and replacement program and the designated machine the programs are operating on. Basic Machine-Readable Material
Feature Distribution
Environment Number Medium
z/OS 5802 3480 tape cartridge
z/OS 6729 4MM-DAT cartridge
Customization Options: Select the appropriate feature numbers to customize your order to specify the delivery options desired. These features can be specified on the initial or MES orders. Example: If publications are not desired for the initial order, specify feature number 3470 to ship media only. For future updates, specify feature number 3480 to ship media updates only. If, in the future, publication updates are required, order an MES to remove feature number 3480; then, the publications will ship with the next release of the program.
Feature
Description Number
Initial Shipments
Serial Number Only (suppresses shipment 3444
of media and documentation)
Ship Media Only (suppresses initial 3470
shipment of documentation)
Ship Documentation Only (suppresses 3471
initial shipment of media)
Update Shipments
Ship Media Updates Only (suppresses 3480
update shipment of documentation)
Ship Documentation Only (suppresses 3481
update shipment of media)
Suppress Updates (suppresses update 3482
shipment of media and documentation)
Expedite Shipments
Local IBM Office Expedite 3445
(for IBM use only)
Customer Expedite Process Charge 3446
($30 charge for each product)
Expedite shipments will be processed to receive 72-hour delivery from the time IBM Software Delivery and Fulfillment (SDF) receives the order. SDF will then ship the order via overnight air transportation. Unlicensed Documentation: A Program Directory (GI10-8493) and Licensed Program Specifications (GC18-7175) is supplied automatically with the basic machine-readable material. No other hardcopy publications are shipped with the product. Displayable Softcopy Publications: All IBM Debug Tool for z/OS and OS/390 V3 publications are available free of charge in displayable softcopy format (BookManager®, PDF) on the IBM Debug Tool Web site:
Subsequent updates (technical newsletters or revisions between releases)
to the publications shipped with the product will be distributed to the
user of record for as long as a license for this software remains in
effect. A separate publication order or subscription is not needed.
Customized OfferingsMost product media is shipped only via Customized Offerings (that is, CBPDO, ServerPac, Systempac®). Non-customized items (CDs, diskettes, source media, media kits) will continue to be shipped via the stand-alone product. Terms and ConditionsLicensing: IBM Customer Agreement Indexed Monthly License Charge (IMLC) Applies: No Educational Allowance: Yes, 15% education allowance applies to qualified education institution customers. Volume Discount: Not applicable.
Replaced Program(s) Replacement Program(s)
Program Program Program Program
Number Name Number Name
5734-CB4 COBOL 5655-H32 IBM Debug Tool
Interactive for z/OS and
Debug OS/390 V3
5658-995 Inspect 5655-H32 IBM Debug Tool
for C/370 for z/OS and
and PL/I V1 OS/390 V3
5688-194 CODE/370 5655-H32 IBM Debug Tool
V1 for z/OS and
OS/390 V3
5688-194 IBM Debug 5655-H32 IBM Debug Tool
Tool for for z/OS and
z/OS and z/OS and
OS/390 V1 OS/390 V3
5655-H32 IBM Debug To a follow-on if any
Tool for
z/OS and
OS/390 V3
Licensed Program Materials Availability
Testing Period: Two months (Basic license only)
Support Center Yes
applies: Access is available through the
IBM Support Center
Available until 12 months' written notice
discontinued:
APAR Mailing IBM Corporation
Address: APAR Processing
P.O. Box 49023
San Jose, CA 95161-9023
Order Now
Use Priority/Reference Code: LE001
Phone: 800-IBM-CALL
Fax: 800-2IBM-FAX
Internet: ibm_direct@vnet.ibm.com
Mail: IBM Atlanta Sales Center
Dept. LE001
P.O. Box 2690
Atlanta, GA 30301-2690
You can also contact your local IBM Business Partner or IBM representative. To identify them, call 800-IBM-4YOU.
Note: Shipments will begin after the planned availability date.
Trademarks
|
