zOS V11 Debug Tool 使用手册

需积分: 7 53 浏览量更新于2024-07-18 收藏 2.46MB PDF 举报

"《Debug Tool for zOS V11 User's Guide》是IBM公司发布的一本针对大型主机操作系统zOS的调试工具使用手册，适用于版本11.1，程序编号5655-W45，并且需要配合APAR PM27734的PTF使用。这本书详细介绍了如何使用Debug Tool for zOS对多种编译器进行调试，包括AD/Cycle C/370 V1R2、C/C++ for MVS/ESA V3、C/C++ for OS/390、C/C++ feature of z/OS、OS/VSCOBOL V1R2.4、VSCOBOL II V1R3和V1R4、COBOL/370 V1R1、COBOL for MVS&VM V1R2、COBOL for OS/390&VM V2、Enterprise COBOL for z/OS和OS/390 V3、以及Enterprise COBOL for z/OS V4.2和更早版本，还有High Level Assembler for MVS&VM&VSE V1R4、V1R5和V1R6等。" 在《Debug Tool for zOS V11 User's Guide》中，读者可以了解到如何有效地调试运行在zOS操作系统上的各种应用程序。这本书首先会介绍Debug Tool的基本概念和安装步骤，确保用户能够正确配置和启动调试环境。接着，它将详细阐述与不同编译器的集成，如C/C++和COBOL等，因为这些编译器在zOS系统中广泛使用。对于每个支持的编译器，手册将详细讲解如何设置断点、查看和修改内存状态、跟踪变量变化以及调用堆栈管理等核心调试功能。此外，书中还会涵盖特定于zOS平台的调试技巧，如处理MVS作业控制语言（JCL）错误、多任务环境下的并发问题以及与系统服务的交互。用户可以学习如何使用Debug Tool来诊断和解决性能问题，例如通过分析CPU循环和内存使用情况来优化代码。对于高级用户，书中的内容可能还会涉及到如何调试由High Level Assembler编写的系统级代码。对于那些使用COBOL编程的开发者，该手册将提供关于如何调试COBOL程序的专门章节，包括如何调试COBOL中的错误处理、子程序调用和数据结构等问题。同时，手册还会讨论如何利用Debug Tool与其他IBM提供的工具，如性能分析器和存储管理工具，协同工作以提高整体开发效率。《Debug Tool for zOS V11 User's Guide》是zOS开发人员的必备参考资料，它提供了一套全面的调试策略和技术，帮助用户深入理解系统行为，定位和修复代码中的错误，从而提升软件质量和可靠性。无论是初学者还是经验丰富的专业开发人员，都能从这份详尽的手册中受益匪浅。

You can use the PDF format on either z/OS Licensed Product Library CD-ROM or

IBM Resource Link to print licensed documents.

Using LookAt to look up message explanations

LookAt is an online facility that lets you look up explanations for most of the IBM

messages you encounter, as well as for some system abends and codes. Using

LookAt to find information is faster than a conventional search because in most

cases LookAt goes directly to the message explanation.

You can use LookAt from the following locations to find IBM message

explanations for z/OS elements and features, z/VM

, VSE/ESA, and Clusters for

AIX

and Linux:

v The Internet. You can access IBM message explanations directly from the LookAt

Web site at http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/.

v Your z/OS TSO/E host system. You can install code on your z/OS or z/OS.e

systems to access IBM message explanations, using LookAt from a TSO/E

command line (for example, TSO/E prompt, ISPF, or z/OS UNIX System

Services running OMVS).

v Your Microsoft Windows workstation. You can install code to access IBM

message explanations on the z/OS Collection (SK3T-4269), using LookAt from a

Microsoft Windows command prompt (also known as the DOS command line).

v Your wireless handheld device. You can use the LookAt Mobile Edition with a

handheld device that has wireless access and an Internet browser (for example,

Internet Explorer for Pocket PCs, Blazer, or Eudora for Palm OS, or Opera for

Linux handheld devices). Link to the LookAt Mobile Edition from the LookAt

Web site.

You can obtain code to install LookAt on your host system or Microsoft Windows

workstation from a disk on your z/OS Collection (SK3T-4269), or from the LookAt

Web site (click Download, and select the platform, release, collection, and location

that suit your needs). More information is available in the LOOKAT.ME files

available during the download process.

How this document is organized

This document is divided into areas of similar information for easy retrieval of

appropriate information. The following list describes how the information is

grouped:

v Part 1 groups together introductory information about Debug Tool. The

following list describes each chapter:

– Chapter 1 introduces Debug Tool and describes some of its features.

– Chapter 2 describes a simple scenario of how to use Debug Tool in full-screen

mode, introducing you to some basic commands that you might use

frequently.

v Part 2 groups together information about how to prepare programs for

debugging. The following list describes each chapter:

– Chapter 3 describes how to choose compiler options, debugging mode, and

runtime options so that you can prepare programs for debugging. It also

describes your options for debugging COBOL programs compiled with

compilers that are now out-of-service.

– Chapter 4 describes how to implement the choices you made in chapter 3.

– Chapter 5 describes how to prepare a LangX COBOL program.

xiv Debug Tool V11.1 User's Guide

– Chapter 6 describes how to prepare an assembler program.

– Chapter 7 describes how to prepare a DB2 program.

– Chapter 8 describes how to prepare a DB2 stored procedures program.

– Chapter 9 describes how to prepare a CICS program.

– Chapter 10 describes how to prepare an IMS program.

– Chapter 11 describes how to include a call to the TEST runtime option into a

program.

v Part 3 groups together information that describes the different methods you can

use to start Debug Tool. The following list describes each chapter:

– Chapter 12 describes how to write the TEST runtime option to indicate how

and when you want to start Debug Tool.

– Chapter 13 describes how to start Debug Tool from Debug Tool Utilities.

– Chapter 14 describes how to start Debug Tool from a program.

– Chapter 15 describes how to start Debug Tool for your batch or TSO

programs.

– Chapter 16 describes how to start Debug Tool from CICS programs.

– Chapter 17 describes how to start Debug Tool in full-screen mode.

– Chapter 18 describes how to start Debug Tool in full-screen mode using the

Terminal Interface Manager. This chapter also describes some tips to starting

Debug Tool from a stored procedure.

v Part 4 groups together information about how to debug a program in full-screen

mode and provides an example of how to debug a C, COBOL, and PL/I

program in full-screen mode. The following list describes each chapter:

– Chapter 19 provides overview information about full-screen mode.

– Chapter 20 provides a sample COBOL program to describe how to debug it

in full-screen mode.

– Chapter 21 provides a sample OS/VS COBOL program as representative of

non-Language Environment COBOL programs to describe how to debug it in

full-screen mode.

– Chapter 22 provides a sample PL/I program to describe how to debug it in

full-screen mode.

– Chapter 23 provides a sample C program to describe how to debug it in

full-screen mode.

– Chapter 24 provides a sample C++ program to describe how to debug it in

full-screen mode.

– Chapter 25 provides a sample assembler program to describe how to debug it

in full-screen mode.

– Chapter 26 describes how to modify the appearance of a full-screen mode

debugging session and save those changes, as well as other settings, into files.

v Part 5 groups together information about how to enter and use Debug Tool

commands.

– Chapter 27 provides information about entering mixed case commands, using

DBCS characters, abbreviating commands, entering multiline commands, and

entering comments.

– Chapter 28 describes how to use Debug Tool commands to debug COBOL

programs.

– Chapter 29 describes how to use Debug Tool commands to debug LangX

COBOL programs.

About this document xv

– Chapter 30 describes how to use Debug Tool commands to debug PL/I

programs.

– Chapter 31 describes how to use Debug Tool commands to debug C or C++

programs.

– Chapter 32 describes how to use Debug Tool commands to debug assembler

programs.

– Chapter 33 describes how to use Debug Tool commands to debug

disassembly programs.

v Part 6 groups together information about debugging DB2, DB2 stored

procedures, IMS, CICS, ISPF, UNIX System Services, and production-level

programs.

– Chapter 34 describes how to debug a DB2 program.

– Chapter 35 describes how to debug a DB2 stored procedure.

– Chapter 36 describes how to debug an IMS program.

– Chapter 37 describes how to debug a CICS program.

– Chapter 38 describes how to debug an ISPF program.

– Chapter 39 describes how to debug a production-level program.

– Chapter 40 describes how to debug a program running in the UNIX System

Services shell.

– Chapter 41 describes how to debug programs that do not start or run in

Language Environment.

v Part 7 groups together information about how to debug programs written in

multiple language or running in multiple processes.

– Chapter 42 describes how to debug a program written in multiple languages.

– Chapter 43 describes the restrictions when you debug a multithreaded

program.

– Chapter 44 describes how to debug a program that runs across multiple

processes and enclaves.

– Chapter 45 describes how to debug a multiple-enclave interlanguage

communication (ILC) application.

– Chapter 46 describes how to debug programs that are called by Java native

methods.

– Chapter 47 describes how to instruct Debug Tool to handle problems created

by program names or the large size of programs.

v Part 8 groups together appendixes. The following list describes each appendix:

– Appendix A describes the data sets that Debug Tool uses to retrieve and store

information.

– Appendix B describes the process Debug Tool uses to locate source, listing, or

side files.

– Appendix C describes the compiler options you should choose to create

programs that can be used by all the Problem Determination Tools,

eliminating recompiles when you want to switch tools.

– Appendix D provides an example that guides you through the process of

preparing a sample program and modifying existing setup files by using

Debug Tool Utilities.

– Appendix E provides information about debugging a program in batch mode.

– Appendix F describes how to use the DTST transaction to display and modify

CICS storage.

xvi Debug Tool V11.1 User's Guide

v Compiled with Enterprise PL/I for z/OS, Version 3.5, with the PTFs for

APARs PK35230 and PK35489 applied and run with the following versions of

Language Environment:

– Language Environment Version 1.9, or later

– Language Environment Version 1.6, Version 1.7, or Version 1.8, with the

PTF for APAR PK33738 applied

Debug Tool provides facilities that apply only to programs compiled with specific

levels of compilers. Because of this, Debug Tool User's Guide uses the following

terms:

assembler

Refers to assembler programs with debug information assembled by using

the High Level Assembler (HLASM).

COBOL

Refers to the all COBOL compilers supported by Debug Tool except the

COBOL compilers described in the term LangX COBOL.

disassembly or disassembled

Refers to high-level language programs compiled without debug

information or assembler programs without debug information. The

debugging support Debug Tool provides for these programs is through the

disassembly view.

Enterprise PL/I

Refers to the Enterprise PL/I for z/OS and OS/390

and the VisualAge

PL/I for OS/390 compilers.

LangX COBOL

Refers to any of the following COBOL programs supported through use of

the EQALANGX (or IDILANGX) debug file:

v Programs compiled using the IBM OS/VS COBOL compiler.

v Programs compiled using the VS COBOL II compiler with the NOTEST

compiler option.

v Programs compiled using the Enterprise COBOL compiler with the

NOTEST compiler option.

As you read through the information in this document, remember that

OS/VS COBOL programs are non-Language Environment programs, even

though you might have used Language Environment libraries to link and

run your program.

VS COBOL II programs are non-Language Environment programs when

you link them with the non-Language Environment library. VS COBOL II

programs are Language Environment programs when you link them with

the Language Environment library.

Enterprise COBOL programs are always Language Environment programs.

Note that COBOL DLL's cannot be debugged as LangX COBOL programs.

Read the information regarding non-Language Environment programs for

instructions on how to start Debug Tool and debug non-Language

Environment COBOL programs, unless information specific to LangX

COBOL is provided.

PL/I Refers to all levels of PL/I compilers. Exceptions will be noted in the text

that describe which specific PL/I compiler is being referenced.

xviii Debug Tool V11.1 User's Guide

剩余563页未读，继续阅读

fstar8999

粉丝: 0
资源: 2

zOS V11 Debug Tool 使用手册

DB2 Version 9.1 for zOS Utility Guide and Reference

DB2 Admin guide for zos

DB2 Version 9.1 for zOS AdministrationAdministration Guide

zos 是什么输出

zos.setf(std::ios::fixed);zos.precision(6); 加入这些命令需要增加什么头文件吗？ 显示zos未定义

zemax的zos文件是什么文件

error: 'zos' was not declared in this scope; did you mean 'cos'? 44 | zos.setf(std::ios::fixed); | ^~~ | cos

zos文件与zmx文件有什么qubie

SAP中ZOS_APPRWF_HIST

为什么zos流入文件之后 时间戳格式会发生变化

最新资源

zos.setf(std::ios::fixed);zos.precision(6); 加入这些命令需要增加什么头文件吗？显示zos未定义

为什么zos流入文件之后时间戳格式会发生变化