Dumpmaster PDF

I N T E L L I G E N T S Y S T E M S M A N A G E M E N T
DUMPMASTER MVS
User Guide
DMOU-5400-00
DUMPMASTER MVS 5.400
Publication number
DMOU-5400-00 (March 2003)
Trademark acknowledgements
The following are trademarks of Macro 4: DUMPMASTER, VPAM. The following are trademarks or registered trademarks of IBM Corporation: CICS, CICS/ESA, CICS TS, DB2, DFSMS, IMS, Language Environment, MQSeries, MVS, MVS/ESA, MVS/XA, OS/390, VisualAge, WebSphere. CA-Panexec is a registered trademark of Computer Associates International, Inc. IAM is a registered trademark of Innovation Data Processing. QuickRef is a trademark of Chicago-Soft, Ltd. Other product and company names mentioned herein may be the trademarks or registered trademarks of their respective owners.
Documentation set
The documentation relating to this product includes:
I
DUMPMASTER MVS Installation Guide DUMPMASTER MVS Dump Navigation Handbook DUMPMASTER MVS Messages DUMPMASTER MVS Technical Reference DUMPMASTER MVS User Guide
Making comments
We welcome suggestions from all users regarding our software products and their accompanying documentation. Please contact your local Macro 4 representative, email us at tech.authors@macro4.com, or write to: Technical Documentation Macro 4 The Orangery, Turners Hill Road, Crawley, West Sussex RH10 4SS United Kingdom
www.macro4.com
License information
Copyright 2003 Macro 4. All rights reserved. This publication, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The information in this publication is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Macro 4. Macro 4 assumes no responsibility or liability for any errors or inaccuracies which may appear in this publication. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording or otherwise, without prior written permission from Macro 4.
Contents
DUMPMASTER MVS User Guide DMOU-5400-00
About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Release levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Summary of new features . . . . . . . . . . . . . . . . . . . . . . . 9

New features in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Overview of DUMPMASTER components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 DUMPMASTER manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 DUMPMASTER sample dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 DUMPMASTER Initial Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Online Help and the DUMPMASTER tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 2 Dump inspection setup and administration . . . . . . . . . 19

Session Setup displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 LIST Dump List options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 VIEW dump viewing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 PF KEYS PF Key Definitions and Labels display. . . . . . . . . . . . . . . . . . . . . 24 PF SHOW Tailor PF Key Definition display . . . . . . . . . . . . . . . . . . . . . . . . 24 Dump Selection displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 MVS dump selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 CICS dump selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Dump Selection criteria fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Dump List (DLIST) displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 MVS Dump List display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 CICS Dump List display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Dump List fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Dump List commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
DUMPMASTER MVS USER GUIDE
CONTENTS
Dump List action codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 How to change the expiry date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 How to retain an expired dump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Displaying a dump directly from SYSLOG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Administrators Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Chapter 3 Primary dump inspection facilities . . . . . . . . . . . . . . . . 45

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online access to dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes and subnotes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage areas and subareas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use of DUMPMASTER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use of ISPF system commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pull down menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigation menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listings menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traces menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 46 46 47 48 49 52 52 53 53 54 54
Dynamic 'Point and Shoot' access to information . . . . . . . . . . . . . . . . . . . . . . . . . 50
Source listing support in DUMPMASTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Retrieving your program listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Defining the listings search strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listings dataset formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listings search options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to retrieve a remote listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 58 58 62
Abend Summary Display (ASD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Support for IAM datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Specifying a listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Capturing and displaying the job log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Example ASDs (list of) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 ASD for COBOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 ASD for PL/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 ASD for a CICS transaction dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 ASD for a CICS system dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 ASD for Assembler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 ASDs for DB2 and IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 ASD for Language Environment (LE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 ASD for WebSphere MQSeries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 System View display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 CICS Trace Table displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 CICS Application Level Trace display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 CICS System Level Trace display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 CICS Full Trace Entry display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
CONTENTS
Chapter 4 Advanced dump inspection facilities . . . . . . . . . . . . . 125

Dump Menu (DMENU) displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Dump Menu for an MVS dump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Dump Menu for a CICS transaction dump . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Dump Menu for a CICS system dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Dump displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Fields on Dump Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 I/O Summary display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Typical DCB display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Typical ACB display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Enqueue list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Fields on Enqueue List display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Address selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Accessing and referencing the registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Dump inspection special characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Retain command character (&). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Repositioning characters (+ and -) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Special Help character (?) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Advanced pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Batch dump print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Extended Find facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Entries on Extended Find display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Extended Find, Scan display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Note lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Example of a Note List display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 General information on Note Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Note List Generation pull down menu option. . . . . . . . . . . . . . . . . . . . . . . . 148 Note List commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Using procedural language (REXX API) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Running an EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Writing your own EXECs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Diagnostic facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Macro 4 diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Advanced diagnostic facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Chapter 5 Working with VPAM program listings online . . . . . . . 159

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Program Listings Entry displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Program Listings Entry display (without selection criteria). . . . . . . . . . . . . . 161 Program Listings Entry display (with selection criteria) . . . . . . . . . . . . . . . . 162 Program Listings Index panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Program Listings Index primary commands . . . . . . . . . . . . . . . . . . . . . . . . . 164 Program Listings Index line commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Confirming listing deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 'Own VPAM' establishing individualized VPAM listing archives . . . . . . . . . . 167
CONTENTS
Chapter 6 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Appendix A Dump inspection commands . . . . . . . . . . . . . . . . . . . . 173

Control commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Information commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Positioning commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Set commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Search commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Calculation and conversion commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Dump inspection command summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 A F prefixed commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 G O prefixed commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 P R prefixed commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 S Z prefixed commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
About this manual
Welcome to the DUMPMASTER MVS User Guide, which is geared towards endusers of the product. You should read this manual if you will be using DUMPMASTERs online abend analysis and dump management functions to solve your program abends. To understand the manual, you should have some knowledge of MVS and CICS operations and terminology, and should know how storage is handled by CICS. The major topics covered are:
I
Introduction on page 11 Dump inspection setup and administration on page 19 Primary dump inspection facilities on page 45 Advanced dump inspection facilities on page 125 Working with VPAM program listings online on page 159 Glossary on page 169
Appendix:
I
Dump inspection commands on page 173
About this manual
Release levels
Release levels
Macro 4 product release levels are of the form n.nnn. Minor software updates are reflected by a change in the last two digits, and do not necessarily cause the documentation to be reissued.
Release level in figures

In this manual, a DUMPMASTER release level of 9.999X is used in figures and so on for illustration purposes.
Conventions
The following typographic conventions are used:
BOLDface
Indicates a command or keyword that you should type. All characters must be entered in the order shown; lowercase characters are optional but must be typed in uppercase. For example, MAXimum indicates that you should type either MAXIMUM or MAX.
italics monotype
Indicates a variable for which you should substitute an appropriate value. Indicates literal input and output. Indicates two or more keys pressed simultaneously. Brackets surround an optional value. Vertical bars separate alternative values from which you must make a selection. Ellipsis indicates that the preceding element may be repeated.
Ctrl+D
[ | ... ]
Summary of new features
This chapter summarizes changes made to the product in this release which are pertinent to readers of this manual. (A complete description of all changes to the product in this and earlier releases is contained in a like-titled chapter in the Installation Guide.) See:
I
New features in this release on page 10
Upgrading pre-V5.310 VPAM datasets VPAM compilation listings datasets prior to V5.310 and from V5.310 and higher cannot be used interchangeably. Consequently, you need to upgrade your existing pre-V5.310 VPAM datasets to the new format, or devise a strategy to enable you to work with both the old (in read only mode) and new formats. For more information, see Working with pre-V5.310 VPAM datasets in the Technical Reference.
10
Summary of new features
New features in this release

I
Support for IBM Enterprise PL/I compiler If an Enterprise PL/I program is detected by the DUMPMASTER Call Chain analysis, then a PL/I listing analysis is initiated either automatically (for a failing module) or manually (using Point and Shoot). Identifying information for the compiler is shown on the DUMPMASTER online analysis displays (Abend Summary, Call Chain, Call Extra, and so on).
Abend Summary Display (ASD) enhancements

I
For all dumps, the date and time the dump was taken by DUMPMASTER (which is usually the same as the time of the abend) is now reported near the top of the ASD. For CICS system dumps, this is the date and time on which the SVC dump was taken by CICS; previously, DUMPMASTER used the date and time the dump was moved from the SYS1.DUMPnn datasets into the DUMPMASTER Dump File. For a CICS dump, either CICS transaction dump No... or CICS system dump No... appears near the top of the ASD for easier identification.
Revised layout for Dump List display Two alternative views of the Dump List are now available. The DLIST command (which is most effective when assigned to a PF Key) is used to switch between the two views.) View 2 contains the new column headings Dups (the number of duplicate dumps that have been suppressed) and Offset (the offset, in hexadecimal format, into the failing program).
Display of abend code for CICS system dumps The abend code reported in DUMPMASTER displays is the CICS-generated dump code (which can be up to eight characters long) that appears on the console log; for previous versions of DUMPMASTER, the code assigned to all CICS system dumps was SYSD.
COBOL support enhancements

I
In previous releases of DUMPMASTER, the Base Locators & Indexes display was usually accessed by selecting the Point and Shoot item Base Locators from the call chain or call extra displays. For DUMPMASTER 5.400, this Point and Shoot item has been added to the Abend Summary Display. For this release of DUMPMASTER, you can display BLL cells for programs in LE storage.
Improvement to Note List Generation display For this release, if the Point and Shoot indicator for a class (for example, Acquired storage areas) is absent, it means that storage notes are unavailable.
Internal product enhancements When processing CICS system dumps for which all of the storage associated with the original MVS address space has been included, dump capture performance has been significantly improved. (For information on reconfiguring for CICS system dump support, see the DUMPMASTER MVS Technical Reference.)
11
CHAPTER 1
Chapter 1
Introduction
The following topics are covered here:

I
Overview of DUMPMASTER components on page 12 Prerequisites on page 13 DUMPMASTER manuals on page 14 DUMPMASTER sample dumps on page 15 DUMPMASTER Initial Menu on page 16 Online Help and the DUMPMASTER tutorial on page 17
12
CHAPTER 1
Introduction
Overview of DUMPMASTER components
Overview of DUMPMASTER components

DUMPMASTER provides a set of facilities which assist programming and technical support staff to resolve abends. Abends can be resolved online in minimum time, with minimum effort, without redundant effort, and without wasting paper or other resources. In an LE/370 environment, DUMPMASTER may be run with TRAP ON or TRAP OFF, as desired, without adversely affecting operations or performance. DUMPMASTER consists of several components, the following of which are described in this manual:
I
Dump inspection setup and administration Session setup; dump selection; types of Dump List; the Administrators Menu. Dump inspection facility Fast online access to dumps for subsequent investigation. Using procedural language (REXX API) How to run your own execs to automatically perform some of the steps that are frequently repeated when viewing a Dump Display. (How to write these execs is documented in the DUMPMASTER MVS Technical Reference.) Program listings viewing/printing/deleting facility Online viewing, printing, and deleting of program compilation listings for use in online dump analysis.
The following components are described in the DUMPMASTER MVS Technical Reference:
I
Administrators online facility Gives the DUMPMASTER Administrator online access to a variety of system management functions. Batch and CICS dump collection facility Trap abends and collect dumps to a DUMPMASTER Dump Dataset. It provides both Batch and CICS Dump Collection in a single, integrated facility.
Note
DUMPMASTER V4.9 and higher supports only CICS/ESA 4.1 or later, which includes any release of CICS TS.
Program listings capture facility Automatic capture of program compilation listings, transparent to the user. Dump management facility DUMPMASTER provides functions for formatting, deleting, expiring, and reporting on the status of, Dump Datasets. VPAM program listings management facility Full maintenance capabilities for program listings held in VPAM (Virtual Partitioned Access Method) datasets. Dump export/import facility Export and import of dumps.
Security In all cases, access to dumps and program listings may be controlled by an Installations external security system, such as RACF, CA-Top Secret, or ACF2.
CHAPTER 1
Introduction
Prerequisites
13
Prerequisites
The system requirements necessary for DUMPMASTER to run successfully are detailed in the DUMPMASTER MVS Installation Guide. Details such as the following are listed:
I
Operating system versions that are supported. Versions of TSO/E and ISPF that are supported. CICS versions that are supported. Versions of COBOL, DB2, IMS, PL/I, and so on, that are supported (for these optional features).
14
CHAPTER 1
Introduction
DUMPMASTER manuals
DUMPMASTER manuals
The following DUMPMASTER manuals are available:
I
The DUMPMASTER MVS Dump Navigation Handbook, an A5 manual geared towards end-users of the online component of DUMPMASTER. The DUMPMASTER MVS Installation Guide tells you how to install the product on your system(s). The DUMPMASTER MVS Messages manual documents all diagnostic messages. The DUMPMASTER MVS Technical Reference provides detailed information about setting up and using DUMPMASTER facilities. The DUMPMASTER MVS User Guide (this manual).
CHAPTER 1
Introduction
DUMPMASTER sample dumps
15
DUMPMASTER sample dumps

When the product was installed by your DUMPMASTER Administrator, a sample dump file was copied from the product tape to dataset user.SAMPDUMP on your system, where user is the high-level qualifier for the DUMPMASTER datasets. Making reference to the sample dumps, the DUMPMASTER MVS Dump Navigation Handbook tells you how to select a dump and shows you how to navigate through the main Dump Inspection displays associated with different types of dump. The Handbook also describes some fundamental DUMPMASTER concepts and tells you how to use the facilities provided by the product to access program listings online.
16
CHAPTER 1
Introduction
DUMPMASTER Initial Menu
DUMPMASTER Initial Menu

The DUMPMASTER Initial Menu, which provides access to the Dump Inspection Facility, is usually invoked from an ISPF menu. (You should check with your System Administrator for instructions on the menu option to select.) It is used to set up session options and system defaults, to determine whether CICS or MVS dumps are to be inspected, to access the Tutorial, and to present additional information on other DUMPMASTER facilities.
Option ===> 0 1 2 3 4 5 6 7 A C E T X SETUP MVS CICS MVS/F CICS/F VPAM VPAM/F Own VPAM ADMIN CHANGES EXECs TUTORIAL EXIT DUMPMASTER Initial Menu Define/change options for your session View MVS dumps View CICS dumps View MVS dumps with current selection criteria View CICS dumps with current selection criteria View/print program listings View/print program listings with current criteria Customize program listings access Set up defaults for new users and DUMPFILE names Summary of changes in DUMPMASTER Vx.x How to write and use DUMPMASTER execs Tutorial on DUMPMASTER Exit from DUMPMASTER
Software Excellence from Macro 4 HTTP://www.macro4.com (c) Copyright Macro 4 yyyy. Enter the END command to terminate this menu All rights reserved.
The options presented on this menu are discussed in the sections of this manual which follow, although not necessarily in the order presented on the display.
Option See
SETUP
Session Setup displays on page 20 Overview on page 64 Working with VPAM program listings online on page 159 'Own VPAM' establishing individualized VPAM listing archives on page 167 Administrators Menu on page 43 Summary of new features on page 9 Using procedural language (REXX API) on page 153 Online Help and the DUMPMASTER tutorial on page 17
1 4 MVS, CICS, MVS/F, CICS/F 5 6 VPAM, VPAM/F 7 Own VPAM
A C E T
ADMIN CHANGES EXECs TUTORIAL
CHAPTER 1
Introduction
Online Help and the DUMPMASTER tutorial
17

This function uses standard ISPF Help and Tutorial panels. It has been set up so that it may be read from beginning to end. When specific Help is requested the most relevant portion of the Tutorial is displayed.
Option ===> DUMPMASTER Tutorial
Enter HELP to view help information for this tutorial. Press Enter to view the following subjects sequentially, or select a specific option number: G 1 2 3 GENERAL SESSION SETUP DUMP SELECTION DUMP LIST General information about DUMPMASTER. Tailoring the session to your requirements. Using Selection Criteria to create a Dump List. How to use the list of the dumps on the Dump Dataset. The commands and facilities available when a dump has been selected.
4 - DUMP DISPLAY FUNCTION
The following subjects are available if specifically selected: 5 6 7 8 DUMP DISPLAY COMMAND SUMMARY EXEC HELP How to use and write DUMPMASTER execs. PROGRAM LISTINGS ONLINE How to view program listings online. INSTALLATION SPECIFICS Help which may have been set up specifically for your installation. F2=SPLIT F8=DOWN F3=END F9=SWAP F4=Previous F5=Rfind F6=Dmp Menu F10=Dlist F11=PF OnOff F12=Retrieve
F1=HELP F7=UP
The Tutorial is accessed as an option from the Initial Menu. More generally, it is also accessed by entering the ISPF HELP command (this command is usually assigned to a PF Key normally PF1), or from the Help pull down menu (see page 54). When the HELP command is issued on any display within the Dump Inspection Facility, online, context-sensitive help is provided. Once a dump has been selected, the Special Help Character (?) may be used in conjunction with a command to access the Tutorial for a specific DUMPMASTER command. (This feature is available only on displays on which DUMPMASTER commands may be used, that is not on the Initial, Setup, Selection, or List screens.)
18
CHAPTER 1
Introduction
19
CHAPTER 2
Chapter 2
Dump inspection setup and administration
The Dump Inspection Facility provides access to dumps which have been collected into a DUMPMASTER Dump Dataset. This chapter describes session setup, dump selection, and the types of Dump List available, together with the commands and action codes used with them. Also, for continuity, the DUMPMASTER Administrators Menu is described. For details, see:
I
Session Setup displays on page 20 Dump Selection displays on page 25 Dump List (DLIST) displays on page 33 Administrators Menu on page 43
Notes 1 2
Each of the above displays are accessed from the DUMPMASTER Initial Menu see page 16. Once a dump has been selected from a Dump List, the Dump Display Function is invoked, and dump inspection can proceed. This process is described in Primary dump inspection facilities on page 45.
Dump Display Fast Path facility Usually, you select a dump for investigation by specifying your search criteria on the appropriate DUMPMASTER Dump Selection display (MVS or CICS). However, for certain DUMPMASTER messages written to SYSLOG, the Dump Display Fast Path facility enables you to display the corresponding dump directly. In this case, the dump details (dump dataset name, dump number, and so on) are extracted from the selected message. For more information, see Displaying a dump directly from SYSLOG on page 41.
20
CHAPTER 2
Session Setup displays

You use these displays to specify Dump List and dump viewing options and defaults, and the actions to be taken by DUMPMASTER during dump inspection. Also, options are provided for defining values, labels, and the label display format for DUMPMASTER PF Keys. The various Session Setup displays are accessed from the DUMPMASTER Setup Options menu:
Option ===> 1 2 3 4 LIST VIEW PF KEYS PF SHOW DUMPMASTER Setup Options Alter Alter Alter Alter your your your your Dump List and General options Dump Viewing options DUMPMASTER PF key settings DUMPMASTER PF key display details
Press END key to leave this menu
Option
Purpose
See
LIST
Provides a display for specification of various below Dump List default values and actions to be taken by DUMPMASTER during a Dump Inspection session. Provides a display for specification of:
I
VIEW
page 23
Whether or not to use the CICS CMAC file for CICS abend code information. EXECs for DUMPMASTER to invoke when you select a dump.
3 4
PF KEYS
Provides a display for definition of values and page 24 labels for the DUMPMASTER PF Keys.
PF SHOW Provides a display for specification of format page 24 of the PF Key label display area on the screen.
LIST Dump List options

The DUMP LIST and General Options display is used to specify:
I
Default values for the format of dates appearing in the Dump Inspection Facility.
CHAPTER 2
21
The Batch dump list column option, which enables you to specify that, instead of Stepname, an alternative column heading is displayed on a Batch Dump List. The action to be taken by DUMPMASTER when a Delete action code is entered on the Dump List. The actions to be taken by DUMPMASTER when the Dump List is returned to after viewing a dump.
DUMPMASTER DUMP LIST and General Options
Command ===>
Enter or check your DUMP LIST and General options below : Format of date ( E European FORMAT ===> E A American J Julian) I PSB/Step N No) N No) J Job No. U Userid)
Batch dump list column option ( S Stepname CONFIRM ===> S Confirmation when deleting a dump ( Y Yes CONFIRM ===> Y Dump List to be refreshed on return ( Y Yes REFRESH ===> N
Enter the END command to save your changes Enter the HELP command to get Tutorial Information
Dump List display fields
See
Format of date Batch dump list column option Confirmation when deleting a dump Dump List to be refreshed on return
below page 22 page 22 page 22
Format of date
This field determines the format of the dates which will be entered in the Dump Date field of the Dump Selection displays, and all subsequent date displays in the Dump Inspection Facility. Dates may be entered in American, European or Julian format. The field may have the one of the following values:
A
Specifies dates in the North American format of mm/dd/yy.

E
Specifies dates in the European format of dd/mm/yy.

J
Specifies dates in the Julian format of yy/ddd.
22
CHAPTER 2
Batch dump list column option
This field enables you to specify that, instead of Stepname, an alternative heading is displayed on a MVS Dump Selection screen, and also on the corresponding Dump List screen. The allowed values are:
S
This is the default value, which means there is no change to the Dump List (Stepname will appear as a column heading).
I
The Stepname column heading will be replaced by PSB/Step. For IMS message region dumps (identified by the IMSMSGJOB General Control Option see the DUMPMASTER MVS Technical Reference), the PSB name will be shown under this column; for every other sort of Batch dump, the stepname will be shown.
J
The Stepname column heading will be replaced by Job No..

U
The Stepname column heading will be replaced by Userid.
Confirmation when deleting a dump
This field determines the actions to be taken by DUMPMASTER when a Delete action code is entered on the Dump List. The field may have the one of the following values:
Y
Present a Confirm Deletion display prior to deleting any dump.

N
Delete the selected dump immediately, without displaying confirmation.
Dump List to be refreshed on return
This field determines the actions to be taken by DUMPMASTER when the Dump List is returned to after viewing a dump. The field may have the one of the following values:
Y
Rebuild the Dump List to reflect any changes made to the list since it was last created.
N
Do not rebuild the Dump List.
CHAPTER 2
23
VIEW dump viewing options

Command ===> DUMPMASTER Dump Viewing Options
Enter or check your Dump Viewing options below : Use CICS CMAC file for CICS abend code information ( Y Yes CMAC ===> Y Initial EXEC to be supplied when dump selected MVS Dumps ===> %M4ASDGEN CICS Dumps ===> %M4ASDGEN Listings Server name LSSRV ===> AASERVER N No)
Enter the END command to save your changes Enter the HELP command to get Tutorial Information
Dump Viewing Options display fields
See
Use CICS CMAC file Initial EXEC to be supplied Listings Server name
below below page 24
Use CICS CMAC file
This field determines whether DUMPMASTER will use the CICS CMAC file or its own proprietary data for CICS abend information. (Use of the CMAC file is recommended if it is available.) The field may have one of the following values:
Y
Use the CMAC file.

N
Use proprietary DUMPMASTER information.
Initial EXEC to be supplied
If this field is blank when a dump is selected from the Dump List, DUMPMASTER automatically invokes the %M4ASDGEN EXEC to display the Abend Summary Display. These fields are used to specify alternative EXECs you might prefer DUMPMASTER to invoke when you select a dump. The MVS field is used for dumps from the MVS Dump List, and the CICS field is used for dumps from the CICS Dump List. If you specify an EXEC name, you must prefix it with the % character.
Note
DUMPMASTER does not validate Initial EXEC to be supplied field entries. The EXEC must be available to the user and must give rise to a display; otherwise, the dump cannot be viewed.
See also Deferred listings analysis on page 24.
24
CHAPTER 2
Deferred listings analysis When a COBOL or PL/I program is identified as the failing program, the online analysis identifies and processes the compilation listing in order to present the actual failing statement on the Abend Summary Display. You may prefer to defer processing of the listing, in order to review the basic analysis first. The basic analysis provides a language-oriented view of the failing machine instruction similar to the System View Display but locating the offset of the instruction relative to base locator origins, to the TGT or to the PGT. This may be sufficient to diagnose the problem. The basic analysis also offers Point and Shoot items to display the failing statement with data, the Base Locators & Indexes Display, and the conventional System View Display. To defer listings analysis, specify the following Initial EXEC field entries:
Initial EXEC to be supplied when dump selected MVS Dumps ===> %M4ASDGEN OPT(options) CICS Dumps ===> %M4ASDGEN OPT(options)
where options is one or more of ASM1 (Assembler), COB1 (COBOL) or PLI1 (PL/I), which may be separated by blanks or commas. To review the failing statement and listing, Point and Shoot next to the appropriate member name in the call chain.
Listings Server name
If your compilation listing is to be retrieved from a remote system then this field specifies the name of the local AAServer (see AAServer STC in the DUMPMASTER MVS Technical Reference). Under normal (production) circumstances, this field will be set to AASERVER (the default). However, if you are testing a new release of DUMPMASTER then you may need to run more than one AAServer per MVS Logical Partition. In this case, use the Listings Server name field to specify the appropriate AAServer name.
PF KEYS PF Key Definitions and Labels display

The PF Key Definitions and Labels screen invokes the ISPF KEYS command which enables modification of the values and labels of the PF Keys (for the Dump Inspection Facility only). DUMPMASTER incorporates a TOGGLE command which simulates the relevant ISPF PFSHOW command to turn the PF Key display on or off. This command is most effective when it is set up on a PF Key, and is described in TOGGLE on page 176. For the first time user, DUMPMASTER defaults to PFSHOW ON. DUMPMASTER then retains the PFSHOW value for subsequent Dump Inspection sessions.
PF SHOW Tailor PF Key Definition display

The PF Key Display option invokes the ISPF PFSHOW TAILOR command to enable modification of the format of the PF Key display (for the Dump Inspection Facility only). The DISPLAY SET field determines which PF Key labels are shown. The KEYS field determines how many PF Key labels are shown on each line. The labels are set up using the PF Keys option.
CHAPTER 2
Dump Selection displays
25

You use a Dump Selection display to enter selection criteria which control precisely the dumps which are to be included in a Dump List (see Dump List (DLIST) displays on page 33).
Note
To bypass the Dump List, enter a Dump Number. This is the fast path route, and results in immediate display of the dump in the format specified in the Initial EXEC to be supplied field in the Dump Viewing Options (see page 23). The default is the Abend Summary Display.
There are two types of Dump Selection display, one for address space, or MVS, dumps; the other for CICS transaction and system dumps. They differ only in the selection criteria available.
For information on See
MVS dump selection CICS dump selection Dump selection criteria fields
below page 26 page 26
MVS dump selection

An example of the MVS Dump Selection display appears below:
Navigation Setup Listings Help -----------------------------------------------------------------------------DUMPMASTER MVS Dump Selection Command ===> Alter any required dump list selection criteria and press 'ENTER' Dump File: Data Set Name Volume Serial Job Name Step Name Program Name Dump Number MVS System Id Abend Code Dump Date Dump Time ===> DUMPMAST.DUMPFILE ===> (If not catalogued) ===> (Full or generic) ===> (Full or generic) ===> (Full or generic) ===> ===> ===> ( Sxxx or Unnnn ) ===> (Format is dd/mm/yy ) ===> (Format is hh.mm )
F1=HELP F7=UP
F2=SPLIT F8=DOWN
F3=END F9=SWAP
F4=Previous F5=Rfind F6=Dmp Menu F10=Dlist F11=PF OnOff F12=Retrieve
Notes 1
The contents of a field is altered by overtyping the existing value. The Dump File field must be completed. The values entered in the Job Name and Dump File fields are retained for subsequent Dump Inspection sessions. For MVS Dump Selection the MVS System Id field is also retained. Instead of Step Name, you can specify that an alternative heading (one of Job No., Userid, or PSB/Step) should appear on this screen (and also on the corresponding Dump List screen). See Batch dump list column option on page 22 for details.
26
CHAPTER 2
CICS dump selection

An example of the CICS Dump Selection display appears below:
Navigation Setup Listings Help -----------------------------------------------------------------------------DUMPMASTER CICS Dump Selection Command ===> Alter any required dump list selection criteria and press 'ENTER' Dump File: Data Set Name Volume Serial Job Name Transaction Id Program Name Terminal Id User Id Dump Number Type of Dump Abend Code Dump Date Dump Time F1=HELP F7=UP ===> DUMPMAST.DUMPFILE ===> (If not catalogued) ===> (Full or generic) ===> (Full or generic) ===> (Full or generic) ===> (Full or generic) ===> (Full or generic) ===> ===> * ( T C or * for all) ===> (Full or generic) ===> (Format is dd/mm/yy ) ===> (Format is hh.mm ) F3=END F9=SWAP F4=Previous F5=Rfind F6=Dmp Menu F10=Dlist F11=PF OnOff F12=Retrieve
F2=SPLIT F8=DOWN
Note
The contents of a field is altered by overtyping the existing value. The Dump File field must be completed. The values entered in the Job Name and Dump File fields are retained for subsequent Dump Inspection sessions.
Dump Selection criteria fields

There are fifteen Dump Selection Criteria fields. Eight are common to both the MVS and CICS Dump Selection displays, two appear on the MVS display only, and five appear on the CICS display only. These fields, presented in alphabetical order, are described in detail in the following text.
Dump Selection criteria fields MVS CICS See
Abend Code Dump Date Dump File Data Set Name Dump File Volume Serial Dump Number Dump Time Job Name MVS System Id Program Name Step Name Terminal Id Transaction Id
page 27 page 27 page 28 page 29 page 29 page 29 page 30 page 30
page 30 page 31
page 31 page 31
CHAPTER 2
27
Dump Selection criteria fields
MVS
CICS
See
Type of Dump User Id
page 32 page 32
Abend Code
Applicable to MVS and CICS dumps. This field determines which dumps are selected based on the abend code of the job or CICS transaction. MVS address space abend codes Any specific system or user abend code may be entered. Alternatively, the entry S selects all system abend codes, while U selects all user abend codes. For user abend codes, the leading zeros of the abend code may be omitted. DUMPMASTER inserts zeros to make the code the correct length. For example, U213 selects all dumps which have abended with code U0213. CICS abend codes To select dumps by their CICS abend code enter the full or generic abend code (see below).
Note
For DUMPMASTER V5.400 and higher, the abend code assigned to a CICS system dump is the CICS-generated dump code (which can be up to eight characters long) that appears on the console log; for previous versions of DUMPMASTER, the Abend Code field of all CICS system dumps was set to SYSD.
The generic name may include the following special characters:

* (Asterisk)
To indicates any number of characters. For example:

*A abend codes ending in A. *A* abend codes with A surrounded by any other characters. A* abend codes beginning with A. + (Plus)
To indicate any one character in that position. For example:

+A* abend codes of any length with A as the second character. ++A* abend codes of any length with A as the third character.
Dump Date
Applicable to MVS and CICS dumps. Dumps may be selected by their specific creation date or by a range of such dates. The creation date is the date on which the dump was taken by DUMPMASTER (usually it is the same as the date of the abend); for CICS system dumps, the creation date is the date on which the SVC dump was taken by CICS.
Note
The values in the Dump Date field and the Dump Time field (see Dump Time on page 29) are ANDed together by DUMPMASTER before selecting dumps for display.
28
CHAPTER 2
The value of the Dump List option Format of date determines the format of the field. The current format is indicated by Format is after the Dump Date field. The date is taken to be the first six numeric characters entered in the field; separators are optional and may be any non-numeric character. For example, if the date format is the default (European ddmmyy) then the following dates are all acceptable; the first three dates specify 25th December, 2000: 251200 25.12.00 25/12/00 1/1/1 (Specifies 1st January, 2001) A start or end date is specified by preceding the date with the less than (<) or greater than (>) symbol.
<
indicates that dumps with creation dates less than or equal to the date input should be selected.
>
indicates that dumps with creation dates greater than or equal to the date input should be selected. For example, if the date format is the default (European ddmmyy), the following date selects all dumps created on or after 25th December, 2000: >251200
Dump File Data Set Name
Applicable to MVS and CICS dumps. The full DUMPMASTER dump dataset name apostrophes are not required and a TSO prefix will not be added to the dataset name.
Note
The dump dataset name must be entered and the value is retained by DUMPMASTER for subsequent Dump Inspection sessions.
If this field is left blank then DUMPMASTER provides the File Selection list (see below), which is a list of the available Dump Dataset names. The required dataset is then selected from the list.
Command ===> DUMPMASTER File Selection
Enter any letter under Code to select the file you need, press ENTER to select the first file in the list or the END key to return to Dump Selection. Code . Dump file dsname Volser
'DUMPMAST.DUMPFILE' Description : PRODUCTION SYSTEMS FILE . 'SYS2.DUMPMAST.DUMPFILE' Description : PRODUCTION FILE ON SYS2 . 'TEST.CICA.DUMPFILE' Description : CICA DUMPFILE . 'TEST.CICB.DUMPFILE' Description : CICB DUMPFILE ****************************** End of File Table *******************
F1=HELP F7=UP
F2=SPLIT F8=DOWN
F3=END F9=SWAP
CHAPTER 2
29
Dump File Volume Serial
Applicable to MVS and CICS dumps. If the DUMPMASTER dump dataset is uncatalogued, enter the volume serial number of the volume on which it resides. Applicable to MVS and CICS dumps. This is a fast path route to the Dump Display function. By entering only the dump number, the Dump List is bypassed, and the initial command specified for the type of dump is executed immediately. (See Initial EXEC to be supplied on page 23.) To select a dump by its dump number, enter the number (in the range 1 9999) which has been assigned to the dump by DUMPMASTER:
I
Dump Number
For address space abends, the dump number is available from the abending address spaces log in message number DMB615I, which is issued at the time the dump is taken. For CICS system dumps, the dump number is available from the MVS console log in message number DMB616I. For CICS transaction dumps, the dump number is available from the CICS log in message number DMC702I.
Notes 1 2
If the dump does not satisfy any of the other selection criteria then the dump will not be selected. If the dump for that dump number is no longer on the dataset then the Dump List is displayed. The Dump List is based on any other selection criteria entered. If there is insufficient storage to display the dump then the Dump List will be displayed with ER05 in the Err field for that dump.
Dump Time
Applicable to MVS and CICS dumps. Dumps may be selected by their specific creation time or by a range of such times. The creation time is the time on which the dump was taken by DUMPMASTER (usually it is the same as the time of the abend); for CICS system dumps, the creation time is the time on which the SVC dump was taken by CICS.
Note
The values in the Dump Time field and the Dump Date field (see Dump Date on page 27) are ANDed together by DUMPMASTER before selecting dumps for display.
The time, specified in the 24 hour clock format, is the first four numerics entered in the field. Separators are optional and may be any non-numeric character. A start or end time is specified by preceding the time with the less than (<) or greater than (>) symbol.
<
Indicates that dumps with creation times less than or equal to the time input should be selected.
30
CHAPTER 2
>
Indicates that dumps with creation times greater than or equal to the time input should be selected.
Job Name
Applicable to MVS and CICS dumps. To select dumps by their job name enter the full or generic job name (see below).
Note
The value is retained by DUMPMASTER for subsequent Dump Inspection sessions.

* (Asterisk)

*J job names ending in J. *J* job names with J surrounded by any other characters. J* job names beginning with J. + (Plus)

+J two-character job names ending in J. +J* job names of any length with J as the second character.
MVS System Id
Applicable to MVS dumps only. Where dumps on the DUMPMASTER Dump Dataset may originate from more than one MVS system, the installation defined four character system id may be entered.
Note
The value is retained by DUMPMASTER for subsequent Dump Inspection sessions.
For example, two machines are defined as SYS1 and SYS2; entering SYS2 in this field will cause only the dumps taken on SYS2 to be selected for the Dump List.
Program Name
Applicable to MVS and CICS dumps. To select either address space dumps by the program name used on the EXEC statement, or CICS dumps by the abending program name, enter the full or generic program name. The generic name may include the following special characters:
* (Asterisk)

*N program names ending in N. *N* program names with N surrounded by any other characters. N* program names beginning with N. + (Plus)

+N two-character program names ending in N.
CHAPTER 2
31
+N* program names of any length with N as the second character.
Step Name
Applicable to MVS dumps only. To select dumps by step name enter the full or generic step name (see below).
Note
Instead of Step Name, you can specify that an alternative heading (one of Job No., Userid, or PSB/Step) should appear on a MVS Dump Selection screen (and also on the corresponding Dump List screen). See Batch dump list column option on page 22 for details.

* (Asterisk)

*S step names ending in S. *S* step names with S surrounded by any other characters. S* step names beginning with S. + (Plus)

+S two-character step names ending in S. +S* step names of any length with S as the second character.
Terminal Id
Applicable to CICS dumps only. To select dumps by CICS terminal id enter the full or generic terminal id. The generic name may include the following special characters:
* (Asterisk)

*T terminal ids ending in T. *T* terminal ids with T surrounded by any other characters. T* terminal ids beginning with T. + (Plus)

+T two-character terminal ids ending in T. +T* terminal ids of any length with T as the second character.
Transaction Id
Applicable to CICS dumps only. To select dumps by CICS transaction id enter the full or generic transaction id. The generic name may include the following special characters:
* (Asterisk)

*R transaction ids ending in R.
32
CHAPTER 2
*R* transaction ids with R surrounded by any other characters. R* transaction ids beginning with R. + (Plus)

+R two-character transaction ids ending in R. +R* transaction ids of any length with R as the second character.
Type of Dump
Applicable to CICS dumps only. To select CICS dumps, based on whether the dump is a transaction or system dump, enter one of the following values:
T
Selects all CICS transaction dumps.

C
Selects all CICS system dumps.

* (Asterisk)
Selects all the dumps on the dataset.
User Id
Applicable to CICS dumps only. To select dumps by CICS user id enter the full or generic user id (see below). The generic name may include the following special characters:
* (Asterisk)

*U user ids ending in U. *U* user ids with U surrounded by any other characters. U* user ids beginning with U. + (Plus)

+U two-character user ids ending in U. +U* user ids of any length with U as the second character.
CHAPTER 2
Dump List (DLIST) displays
33

The Dump List is a list of the dumps on the dump dataset which have met the selection criteria entered in a Dump Selection screen. On a Dump List display there is one dump information line for each dump; the type of information line depends on whether MVS or CICS dump selection criteria have been used.
Dump List topics See
General information MVS Dump List display CICS Dump List display Dump List fields Dump List commands Dump List action codes How to change the expiry date How to retain an expired dump
below page 34 page 35 page 36 page 37 page 37 page 40 page 40
General information
For display, a Dump List is sorted into descending date and time order. Generally this results in a display in descending dump number order as well, unless dumps have been IMPORTed into the Dump File. A Dump List is scrolled using standard ISPF scrolling commands. The fast path route back to the Dump List is the DLIST command, which is described in DLIST on page 174. Displaying alternative views of the Dump List display Two alternative views of the Dump List are available issue the DLIST command to switch between them. (The DLIST command is most effective when it is assigned to a PF Key.) Selecting a dump to be viewed The dump to be viewed is selected from a Dump List by using action codes see Dump List action codes on page 37. These action codes are also used to perform Dump Dataset maintenance functions.
34
CHAPTER 2
MVS Dump List display

View 1 Here is an example of this (the default) view of the MVS (Batch) Dump List display:
Navigation Setup Listings Help -----------------------------------------------------------------------------DUMPMASTER Dump List Dump 1 of 6 Command ===> Scroll ===> CSR Dumps selected from DMB.V9999.SAMPDUMP Enter action code S Select (default) A Alter DumpNo Jobname Stepname Program Code Date E Expire Time D Delete Expires P Print Blks Errs
7 MQSERIES TEST MQTST3D S0C1 05/06/02 11.23 * EXPD * 99 6 COBRUND7 P010 COBDUMPD U0852 31/05/02 15.00 * EXPD * 1343 4 JDHPL1A GO JDHPL1A S0CB 21/05/02 17.40 * EXPD * 424 5 P390TDB3 HSMCOMM DMDB2DEM S0C1 17/09/99 04.29 * EXPD * 554 2 BJCARJO5 COBOL1 BATCOB05 S0C7 22/05/98 13.51 * EXPD * 405 1 BJDB2BAT DMBSTC#2 DSN8BC3 S0C7 06/03/98 10.42 02/10/03 500 ******************************* End of dump list *****************************
F1=HELP F7=UP
F2=SPLIT F8=DOWN
F3=END F9=SWAP
Note
Instead of Step Name, you can specify that an alternative heading (one of Job No., Userid, or PSB/Step) should appear on this screen (and also on the corresponding MVS Dump Selection screen). See Batch dump list column option on page 22 for details.
View 2 To switch to this view of the MVS (Batch) Dump List, an example of which appears below, issue the DLIST command from View 1. (See also Displaying alternative views of the Dump List display on page 33.)
Navigation Setup Listings Help -----------------------------------------------------------------------------DUMPMASTER Dump List Dump 1 of 6 Command ===> Scroll ===> CSR Dumps selected from DMB.V9999.SAMPDUMP Enter action code S Select (default) A Alter DumpNo Jobname Syst Program Offset E Expire D Delete P Print Blks Errs
Userid
Dup's Expires
7 MQSERIES MVSP MQTST3D 00000204 RJM1 0 * EXPD * 99 6 COBRUND7 MVSP COBDUMPD 000006EC SA 0 * EXPD * 1343 4 JDHPL1A MVS9 JDHPL1A 00000CC4 NWH 0 * EXPD * 424 5 P390TDB3 P390 DMDB2DEM FFFB4C54 P390T 0 * EXPD * 554 2 BJCARJO5 P390 BATCOB05 00003610 0 * EXPD * 405 1 BJDB2BAT P390 DSN8BC3 00001AC4 0 02/10/03 500 ******************************* End of dump list *****************************
F1=HELP F7=UP
F2=SPLIT F8=DOWN
F3=END F9=SWAP
To switch back to View 1 of the MVS (Batch) Dump List, issue the DLIST command again.
CHAPTER 2
35
CICS Dump List display

View 1 An example of this (the default) view of the CICS Dump List display appears in the following figure:
Navigation Setup Listings Help -----------------------------------------------------------------------------DUMPMASTER Dump List Dump 1 of 3 Command ===> Scroll ===> CSR Dumps selected from DMB.V9999.SAMPDUMP Enter action code S Select (default) A Alter DumpNo Jobname Xact Program Code Date E Expire Time D Delete Expires P Print Blks Errs
3 DMCICS41 UPDT DFH0CALL ASRA 24/07/02 11.18 * EXPD * 67 8 DMCICS53 UPDT DFH0CALL ASRA 23/07/02 16.29 * EXPD * 69 9 DMCICS62 UPDT DFH0CALL ASRA 23/07/02 14.04 * EXPD * 75 ******************************* End of dump list *****************************
F1=HELP F7=UP
F2=SPLIT F8=DOWN
F3=END F9=SWAP
View 2 To switch to this view of the CICS Dump List, an example of which appears below, issue the DLIST command from View 1. (See also Displaying alternative views of the Dump List display on page 33.)
Navigation Setup Listings Help -----------------------------------------------------------------------------DUMPMASTER Dump List Dump 1 of 3 Command ===> Scroll ===> CSR Dumps selected from DMB.V9999.SAMPDUMP Enter action code S Select (default) A Alter DumpNo Jobname Xact Program Offset E Expire D Delete P Print Blks Errs
Userid
Dup's Expires
3 DMCICS41 UPDT DFH0CALL 0000107E RACFADM 0 * EXPD * 67 8 DMCICS53 UPDT DFH0CALL 0000107E RACFADM 0 * EXPD * 69 9 DMCICS62 UPDT DFH0CALL 0000107E RACFADM 0 * EXPD * 75 ******************************* End of dump list *****************************
F1=HELP F7=UP
F2=SPLIT F8=DOWN
F3=END F9=SWAP
To switch back to View 1 of the CICS Dump List, issue the DLIST command again.
36
CHAPTER 2
CICS missing data By default, ???? in a field indicates that DUMPMASTER was unable to identify an attributable value (such as program id or transaction id) when the dump was collected. This may happen when a CICS storage violation has occurred. The FILTER parameter of the Dump Collection SECURITY Statement specifies a single character value to be used as a substitute in this situation. For example, to cause such a field to be left blank, set FILTER=' ' (that is, set it to a blank character). For more information, see SECURITY statement in the DUMPMASTER MVS Technical Reference.
Dump List fields

For CICS dumps, please review CICS missing data above before proceeding. Blks (MVS and CICS) The number of blocks occupied by the dump on the Dump Dataset. Code (MVS and CICS) The abend code at the time of the dump. Date & Time (MVS and CICS) The date and time the dump was taken by DUMPMASTER (usually it is the same as the time of the abend); for CICS system dumps, this is the date and time on which the SVC dump was taken by CICS. The format of the date is dependent on the value of the Dump List option Format of date. DumpNo (MVS and CICS) The DUMPMASTER dump number. Dups (MVS and CICS) The number of duplicate dumps that have been suppressed. (The DUPECHECK criteria, which are detailed in the DUMPMASTER MVS Technical Reference, are used to decide whether a failure is to be considered a duplicate of a previously captured dump. Only unexpired dumps are compared with the currently failing program.) Errs (MVS and CICS) The DUMPMASTER Dump List error code. These are detailed in the DUMPMASTER MVS Messages manual. Expires (MVS and CICS) The date on which the dump will expire. * EXPD * indicates that it has expired. The format of the date is dependent on the value of the Dump List option Format of date. Input Area (MVS and CICS) The area which precedes DumpNo; it is used to enter the action codes as line commands. Jobname (MVS and CICS) The jobname at the time of the dump.
CHAPTER 2
37
Offset (MVS and CICS) The offset, in hexadecimal format, into the failing program. Program (MVS and CICS) For address space dumps, the name of the program used in the EXEC statement. For CICS dumps, the abending program name. Stepname (MVS only) The stepname at the time of the dump.
Note
Instead of Stepname, you can specify that an alternative heading (one of Job No., Userid, or PSB/Step) should appear on a MVS Dump List screen (and also on the corresponding MVS Dump Selection screen). See Batch dump list column option on page 22 for details.
Syst (MVS only) The MVS system id at the time of the dump. Userid (CICS only) The CICS user id at the time of the dump. Xact (CICS only) The CICS transaction id at the time of the dump.
Dump List commands

REFRESH
Rebuild the Dump List to reflect the current status of the Dump Dataset. The Dump List is not rebuilt automatically, except when the Dump List option refresh has been specified. To view the latest status of the Dump Dataset enter this command in the Command area.
Dump List action codes

The Dump List action codes apply a specific function to a dump. The action code is entered as a line command for the required dump. The following action codes are available:
S
Select a dump for debugging (the default).

Note A
You can also use Point and Shoot on a dump to select it.
Alter a dump expiry date.

D
Delete a dump from the DUMPMASTER Dump Dataset.

E
Expire a dump.
38
CHAPTER 2
Print a dump from the DUMPMASTER Dump Dataset. The action code should be entered in the Input Area which is at the beginning of the dump information line. Many action codes may be entered for the whole Dump List. DUMPMASTER processes all A, D, E and P action codes before it processes the first S action code on the Dump List. Only the first S action code is processed.
Alter action code Delete action code Expire action code Print action code Select action code
below below page 39 page 39 page 40
Alter action code The A action code is used to change the expiry date of the dump. Alter may be used
even if the dump has already expired. Enter the A action code and then the new date in the Expires field; the remainder of the Expires field should be cleared. Either a date may be entered or the + (plus) command used.
date
Is the first six numeric characters entered in the Expires field; separators are optional and may be any non-numeric character. The date format is determined by the value of the Dump List option Format of date.
Note + (Plus)
Year digits 00 79 signify 2000 2079; year digits 80 97 are not allowed; and year digits 98 99 signify 1998 1999.
Should be followed by the number of days to be added to the expiry date. The maximum number of days is 365. If the dump has already expired then the expiry date is considered to be todays date.
Delete action code
The D action code removes the dump from the dump dataset. It is no longer available to DUMPMASTER. If the Dump List option confirm is N then DUMPMASTER deletes the dump immediately. However, if this option is set to Y then a Confirm Delete display is displayed for each dump to be deleted. The following screen shows the display for address space dumps.
CHAPTER 2
39
Command ===>
DUMPMASTER Confirm Delete
Delete entered for dump number 3948 Job name Step name Program name Abend code MVS System Id Dump taken on at PAYCHEQ CHQPRINT PCHQ1000 S0C4 IPO1 18/01/97 14.23
Press ENTER key to confirm delete request. Press END key to cancel delete request.
Expire action code
The E action code marks the dump * EXPD *. As a result the space occupied by the dump is available to DUMPMASTER. If there is insufficient space on the dump dataset, DUMPMASTER will overwrite dumps which are marked * EXPD *. The oldest dump will be overwritten first.
Print action code The P action code indicates that the dump is to be printed by the DUMPMASTER
Dump Print facility. The printed report includes:
I
Separate sections (Abend, DB2, I/O, PL/I, and IMS summaries; load module details; call chain; and so on), which contain a level of detail similar to the online Dump Inspection facility displays. Information on all storage captured by the dump. An index, which guides you to the various sections of the report.
The printed report does not include program compilation listings analysis.
Notes 1
When you take this option, you are prompted to specify the JCL information to be used to construct the job (job card data (JOB), printer destination (DEST), printer class (SYSOUT), and so on). You also have the option of editing the job before it is submitted. You can also print a selected dump by choosing the Batch dump print option from the Advanced pull down menu (see page 140). Descriptions of abend codes are generated by DUMPMASTER itself; that is, the report does not include Chicago-Soft QuickRef diagnostics. For information on how to trigger an Instant Print, a printed summary report that is integrated into the failing jobs output, please refer to the DUMPMASTER MVS Technical Reference.
2 3 4
Example of a printed detailed report Member PRINTF of user.SAMPLIB contains an example of a printed report.
40
CHAPTER 2
Select action code
The S action code indicates that the dump is to be viewed with the option specified in the Dump List option Initial EXEC to be supplied (see Initial EXEC to be supplied on page 23). The default is the Abend Summary Display. If multiple S action codes have been entered, only the first is processed. For the Abend Summary Display (and any other display option), a window that is updated dynamically appears at the bottom of the Dump List display. In it, the progress of the analysis which results in the Abend Summary Display is presented as it occurs.
How to change the expiry date

A dump may have its expiry date changed by using the Alter action code. Valid year digits are 00 79 for 2000 2079 and 98 99 for 1998 1999; 80 97 may not be used. Enter the A action code as a line command for the required dump and then the new date in the Expires field, the remainder of the field should be cleared. A date may be entered or the + (plus) command used. The A action code is described in the section Alter action code on page 38.
How to retain an expired dump

Once a dump is marked as * EXPD * it is eligible for deletion by DUMPMASTER. This may be avoided by changing the Expiry Date of the dump using the Alter action code. Valid year digits are 00 79 for 2000 2079 and 98 99 for 1998 1999; 80 97 may not be used. Enter the A action code as a line command for the dump to be retained and then the new date in the Expires field; the remainder of the field should be cleared. A date may be entered or the + (plus) command used. The A action code is described in the section Alter action code on page 38.
CHAPTER 2
Displaying a dump directly from SYSLOG
41

Usually, you select a dump for investigation by specifying your search criteria on the appropriate DUMPMASTER Dump Selection display (MVS or CICS). For more information, see Dump Selection displays on page 25. Only when all of the relevant information has been specified can the Abend Summary Display (ASD), the primary DUMPMASTER analytical display (see page 64), be shown. However, for certain DUMPMASTER messages written to SYSLOG, the message contains the full dump dataset name and the dump number:
Message id DMB170I DMC170I
(For MVS dumps) (For CICS dumps)
These messages are described in detail in the DUMPMASTER MVS Messages manual. When you select one of these messages from SYSLOG, DUMPMASTER extracts the dump details (dump dataset name, dump number, and so on) and displays the ASD directly. Therefore, this facility provides a fast path route to the Dump Display function.
Note
Your ISPF library allocations are not compromised by this facility, and when you exit from the ASD you are returned to SYSLOG.
Setting up the Dump Display Fast Path facility For details of how to set up this facility, please refer to the DUMPMASTER MVS Installation Guide. Invoking the Dump Display Fast Path facility The Dump Display Fast Path facility may be invoked from:
I
An ISPF SDSF (Spool Display and Search Facility) SYSLOG display. Here is an example of the top portion of such a display:
Display Filter View Print Options Help ----------------------------------------------------------------------------SDSF SYSLOG 6930.101 MVSP MVSP mm/dd/yyyy LINE 178,769 COLUMNS 51 130 COMMAND INPUT ===> DM SCROLL ===> PAGE 0090 DMB170I DMB9999 V9.999 DUMP NO. 5409 ON DSN - DMB.P30.DUMPFILE 0090 DMF550I DMB9999 DELETED DUMP NO. 5357 0090 DMF550I DMB9999 DELETED DUMP NO. 5365 0090 DMF550I DMB9999 DELETED DUMP NO. 5373 0090 DMB616I DMB9999 V9.999X DMCSDIF DUMP NO 5409 COMPLETED 0090 DMB155I DMB9999 V9.999X Dump no. 5409 completed
A display of the SYSLOG print file. A display of any data source which shows the message in full.
To invoke the Dump Display Fast Path facility from any of these displays:
1
Position the cursor on the line in the display that contains the message. (This is the line that contains message DMB170I in the example above.)
Note
For a long dump dataset name, the message may be spread over two lines on the display, in which case the cursor can be positioned on either of the two lines.
42
CHAPTER 2
Do one of the following:

I
Issue the ISPF command added by your System Administrator to invoke the Dump Display Fast Path facility or, if applicable, press the PF Key assigned to it. The name for this command is DM, unless your System Administrator specified a different name when the facility was set up.
Issue the command TSO %M4DMFPSU or, if applicable, press the PF Key assigned to it.
The ASD for the corresponding dump will be displayed (see Abend Summary Display (ASD) on page 64).
3
When you have finished working with the ASD for the dump, press END to return to the SYSLOG display.
CHAPTER 2
Administrators Menu
43
Administrators Menu
The following options are present on the DUMPMASTER Administrators Menu. (To access the menu itself, use the A (= ADMIN) option on the DUMPMASTER Initial Menu.)
Option ===> 1 2 3 4 5 9 DUMPMASTER Administrators Menu COMMANDS DUMP FILES PROFILE VPAM FILES LISTINGS USER FILES Define/change command table Define/change/delete dump files Define/change user profile Define/delete program listing datasets Define/change listings search strategy Define/change user file dsnames
Software Excellence from Macro 4 HTTP://www.macro4.com (c) Copyright Macro 4 yyyy. All rights reserved. Enter the END command to terminate this menu
Generally, use of these options should be restricted to System Administrators. (In many Installations, general access to them is prevented by external security.) The display is illustrated here only for completeness. The options themselves are covered in detail in the DUMPMASTER MVS Technical Reference manual.
44
CHAPTER 2
Administrators Menu
45
CHAPTER 3
Chapter 3
Primary dump inspection facilities
The basic features of the DUMPMASTER Dump Inspection facility are described in this chapter. Primary dump inspection facility topics
I
Introduction on page 46 (Online access to dumps; Notes and subnotes; storage areas and subareas; Use of ISPF system commands)
Dynamic 'Point and Shoot' access to information on page 50 Pull down menus on page 52 Source listing support in DUMPMASTER on page 55 Defining the listings search strategy on page 58 Abend Summary Display (ASD) on page 64 (Information on an ASD is usually enough to diagnose the error; if not, it serves as the gateway to subsequent in-depth dump analysis)
System View display on page 117 CICS Trace Table displays on page 118
46
CHAPTER 3
Introduction
Introduction
The Dump Inspection Facility provides access to dumps which have been collected into a DUMPMASTER Dump Dataset. Dumps are inspected using the Dump Inspection ISPF dialog (which is accessed directly from the DUMPMASTER Initial Menu see page 16), which is also used for Dump Dataset maintenance.
Online access to dumps Notes and Subnotes Storage areas and subareas Use of DUMPMASTER commands Use of ISPF system commands
below below page 47 page 48 page 49
Online access to dumps

The DUMPMASTER Initial Menu (see page 16) is used to determine which type of Dump List is viewed.
Note
The Initial Menu also provides access to the DUMPMASTER Tutorial, to the Session Setup displays, to viewing facilities for program listings, and to administrative functions and other DUMPMASTER information.
Dump Selection displays (see page 25) are used to enter selection criteria which control the dumps to be included in a Dump List, while a Dump List is a list of the dumps which have met such selection criteria. Dump Display Function When a dump is selected, the Dump Display Function is invoked. The dynamic Abend Summary Display (ASD) is the primary DUMPMASTER analytical display (see page 64) and provides diagnostic information and easy access to areas of a dump. Standard ISPF facilities, such as split screen operation, are available.
Note
If split screen is used, a dump may be viewed in conjunction with the program source or listing. Alternatively, a dump may be compared with another similar dump.
Notes and subnotes

The concept of Notes and Subnotes is an essential element of the Dump Inspection Facility. Notes provide fast access to a specific address in the dump by using a name to denote the actual address. Subnotes are used to differentiate between Notes. Notes are set up either by DUMPMASTER itself when the dump is captured, or by using the NOTE command (see NOTE on page 184), and remain with the dump until they are deleted.
CHAPTER 3
Introduction
47
Storage areas and subareas

DUMPMASTER dumps storage areas. These are blocks of contiguous storage which may be of any length. The beginning of each storage area has a Note associated with it (see Notes and subnotes on page 46). Within a storage area there may be one or many storage subareas. A storage subarea is also contiguous storage which DUMPMASTER has recognized as a logically complete area of storage. Since the address of this area lies within a storage area it is called a storage subarea. A storage subarea may also lie within another storage subarea. The beginning of each storage subarea has a Note associated with it.
Types of Areas Dumped Area Notes
STORAGE 0001
TEST1 PROGRAM S t o r a g e A r e a S u b a r e a
Subarea
TESTFILE DCB
Subarea
TEST2 PROGRAM
This figure shows a storage area STORAGE 0001, and three storage subareas TEST1 PROGRAM, TEST2 PROGRAM and TESTFILE DCB. The storage subarea TESTFILE DCB lies within the storage subarea TEST1 PROGRAM. Storage areas and subareas are significant in determining the automatic value of Origin and the scope of paging commands. Origin is the base address from which the offset values are calculated. Once a Note is selected, Origin is set to the Note associated with the beginning of the storage area or subarea in which the selected Note lies. The storage subarea is selected as Origin in preference to a storage area. However, if Origin has been set using the ORIGIN command (see ORIGIN on page 184) for the storage area or subarea then that Origin is used instead.
48
CHAPTER 3
Introduction
Types of Areas
Dumped Area
Notes
STORAGE 0001
TEST1 PROGRAM S t o r a g e A r e a S u b a r e a
Subarea
TESTFILE DCB
OP1
Subarea
TEST2 PROGRAM INS
In the figure above, if the INS Note is selected then Origin will be set as TEST2 PROGRAM. When the OP1 Note is selected then Origin is set as STORAGE 0001. The scope of the paging commands is determined by the storage area or subarea. Any paging command only acts within the current storage area or subarea. A storage area is accessed from a storage subarea either by entering a specific address, or by using the Repositioning Characters (+ and -). Once the storage area is accessed the Origin will be set as the Note associated with the beginning of the storage area.
Use of DUMPMASTER commands

The Point and Shoot design philosophy of the product frequently eliminates the need to enter one or more DUMPMASTER commands. This enables you to Point with the cursor to an indicator or field on a display and then Shoot by pressing Enter, to obtain more detailed information. See Dynamic 'Point and Shoot' access to information on page 50 for more information. However, certain features are not currently available using the Point and Shoot facility (this issue will be addressed progressively in future releases of the product). In this case, or if you are accustomed to entering DUMPMASTER commands to obtain information, please refer to Dump inspection commands on page 173.
CHAPTER 3
Introduction
49
Use of ISPF system commands

The full range of ISPF System Commands are available where applicable in the Dump Inspection dialog. For example:
I
To exit DUMPMASTER, use the appropriate END or RETURN command. To scroll a display, use the UP or DOWN commands. To vary the scroll amount, use the Scroll field. To recall a command, use the RETRIEVE command. To concatenate commands, use the Command Delimiter which has been defined as an ISPF Terminal Characteristic.
50
CHAPTER 3
Dynamic 'Point and Shoot' access to information

Point and Shoot access to further information is available on most Dump Inspection displays. This enables you to Point with the cursor to an indicator or field on a display and then Shoot by pressing Enter, to obtain more detailed information. A Point and Shoot indicator is a period or full stop (.), while a Point and Shoot field is an abend code, address, and so on. You can tab to all Point and Shoot fields and indicators.
Note
Users of earlier versions of DUMPMASTER accustomed to entering an S or s to select an item may continue to make such an entry on a period or full stop (.) which is a Point and Shoot indicator, although this is unnecessary. Such entries may not be made on Point and Shoot fields.
Point and Shoot frequently eliminates the need to enter one or more commands or to chain through a series of displays in order to obtain specific information. At any point, further commands may be issued or Point and Shoot operations executed to continue exploration of the dump. Abend code When a highlighted abend code is the Point and Shoot target, an explanation of the cause of the abend and, where possible, some hints on how to proceed with debugging, are presented. Other highlighted/unprotected fields For other highlighted and unprotected fields such as addresses, Point and Shoot results in a display of the Dump Display for that address. When positioned at the name of a program, the start address of that program is displayed. Text titles or descriptions Frequently, brief text titles or descriptions of subsidiary diagnostic displays are presented adjacent to Point and Shoot indicators. Usually these are specific to the dump concerned, the displays named having been produced as a result of DUMPMASTER analysis. To view such a display, merely Point and Shoot on the indicator adjacent to its description. 'Display of displays' Displays generated as a result of Point and Shoot operations are stored so that they may be re-called without regeneration. A dynamically-maintained list of such displays is kept in a display of displays, the List of Current Displays, from which they may be selected. The List of Current Displays can be viewed at any time via the Navigation pull down menu (see page 52), or by entering the DISPLAY command (see DISPLAY on page 177) on the Command line. PREVIOUS command When using Point and Shoot and commands to navigate through various views of a DUMPMASTER Dump Display, issue the PREVIOUS command to step back, oneby-one, through previous views of the Dump Display. For example, if Point and Shoot is executed on an address in a Dump Display, followed by UP, DOWN, and
CHAPTER 3
51
+20 commands, followed by another Point and Shoot on an address, each presents a different view of the Dump Display. Issue the PREVIOUS command
repeatedly to step back through each of these views. For more information on this command, see PREVIOUS on page 175. END or QUIT command Issue an END or QUIT command at any point to return directly to the display prior to the Dump Display. For a detailed description of these commands, see Control commands on page 174.
52
CHAPTER 3
Pull down menus
Pull down menus

The most useful dump displays (for example, the Abend Summary Display and the List of Current Displays) have an action bar at the top which provides immediate access to all the information you need to diagnose a dump:
Navigation Setup Listings Advanced Traces Help ------------------------------------------------------------------------------Abend Summary Display ****************************** Top of Display ********************************* Dump No 1647 Job P48324A Step Program was taken on 22/05/98 at 13.51 M4VBR
Point & shoot . items below to select a display Abend code = S878 PSW at time of abend = 070C1000 814B1B9C
To move to the action bar, do one of the following:

I
Key in the command ACTIONS on the Command line and press Enter.
Note
This command is most effective when it is set up on a PF key. Option 2 (= PF KEYS) from the DUMPMASTER Setup Options screen (see page 20) provides a display for DUMPMASTER PF key definition.
Use the Tab key.
When you have moved to the action bar, press Tab to move between the fields, and press Enter to access the pull down menu associated with the particular item. Apart from the Advanced menu, which is described elsewhere (see page 140), the sections that follow describe each pull down menu in turn.
Navigation menu Setup menu Listings menu Traces menu Help menu
below page 53 page 53 page 54 page 54
Navigation menu
This pull down menu lists the major displays for the dump. This includes a selection list of previously-seen displays for the dump (the display of displays), thereby avoiding the overhead of regenerating the display.
Navigation Setup Listings Advanced Traces Help ..................................... ----------------------------------------: 1. Go to Abend Summary Display : ary Display : 2. See Current Displays : : 3. Exit to Dump List : Display ******************************** : 4. Return to Primary Menu : :...................................: ogram M4VBR was taken on 22/05/98 at 13.51 Point & shoot . items below to select a display Abend code = S878 PSW at time of abend = 070C1000 814B1B9C
Note
The only option accessible from the Dump Selection display and the Dump List display is Return to Primary Menu.
CHAPTER 3
Pull down menus
53
Setup menu
Use the Setup pull down menu to specify whether or not a Confirm Quit panel is to be displayed after you use an END or QUIT action (generally F3) to leave a dump.
Navigation Setup Listings Advanced Traces Help ------------....................................------------------------------: 1. Prompt on Quit from dump? : :..................................: ******************************* Top of Display ******************************** Dump No 1647 Job P48324A Step Program was taken on 22/05/98 at 13.51 M4VBR
Listings menu
The Listings pull down menu enables you to set a personalized strategy for searching for program compilation listings in one of several dataset formats.
Navigation Setup Listings Advanced Traces Help ------------------ ....................................-----------------------: 1. Search Strategy : : 2. Revert to Default Strategy : *******************:..................................:************************ Dump No 1647 Job P48324A Step Program was taken on 22/05/98 at 13.51 M4VBR
Option
Description
1 (Search Strategy)
Take this option to define how DUMPMASTER searches one or more repositories for a listing. The DUMPMASTER - Listing Search Options screen appears (see Listings search options on page 58); the initial settings will be based on the search strategy defined by your System Administrator.
2 (Revert to Default Strategy) Select this option to discard your personalized listings search strategy and revert to the search strategy defined by your System Administrator.
54
CHAPTER 3
Pull down menus
Traces menu
Note
This pull down menu is not accessible from the Dump Selection display or the Dump List display.
The Traces pull down menu is used to display CICS trace table entries, so it is only applicable to CICS dumps. (If you are viewing an MVS dump, each option number will appear as an asterisk (*) to indicate that the option is not available.)
Navigation Setup Listings Advanced Traces Help ------------------ ............................................................ : 1. Display CICS Application Level Trace : : 2. Display CICS System Level Trace : ****************** : 3. Change Filters and Display CICS System Level Trace : :..........................................................: Dump No 1647 Job P48324A Step Program M4VBR was taken on 22/05/98 at 13.51 Point & shoot . items below to select a display Abend code = S878 PSW at time of abend = 070C1000 814B1B9C
For further information, please refer to CICS Trace Table displays on page 118.
Help menu
This pull down menu will take you to the key areas of the online Help.
Navigation Setup Listings Advanced Traces Help ---------------------------------------------- ............................. -1. Point & Shoot : Abend Summary Disp : : 2. Help Contents : ******************************* Top of Display : 3. Help Index : ** : 4. DUMPMASTER Commands : Dump No 1647 Job P48324A Step Program M4 :...........................: was taken on 22/05/98 at 13.51 Point & shoot . items below to select a display Abend code = S878 PSW at time of abend = 070C1000 814B1B9C
Note
The only options accessible from the Dump Selection display and the Dump List display are Help Contents and Help Index.
CHAPTER 3
Source listing support in DUMPMASTER
55

For the program language(s) in use at your Installation, if Source Listing Support is enabled and correctly set up then during dump analysis DUMPMASTER will have access to the corresponding program listing. In this situation, the failing instruction can be identified and displayed in most cases. DUMPMASTER can be set up to retrieve and process program listings stored in various formats:
I
Macro 4s VPAM (Virtual Partitioned Access Method) Since its earliest versions, DUMPMASTER has supported program listings stored in VPAM datasets. Consequently, an extensive set of online and batch utilities are available to assist you with the usage and administration of program listings held in this file format.
IBMs PDS and PDSEs Program listings stored in either of these formats are supported by DUMPMASTER and can be administered using conventional TSO/ISPF facilities.
Other manufacturers listings datasets DUMPMASTER provides a customizable interface to enable program listings stored in a format other than VPAM or PDS/PDSE to be retrieved. The details that you provide tell DUMPMASTER how a third party utility program is to retrieve the listings therefore, this method is known as OEM listings access.
Remote program listings Additionally, DUMPMASTER may be configured to retrieve program listings which are stored in a repository (VPAM, PDS/PDSE, or OEM) that is stored on a remote MVS system. In this case, an AAServer (Application Availability Server) is used to retrieve the listing(s) from the remote system. Upgrading pre-V5.310 VPAM datasets VPAM compilation listings datasets prior to V5.310 and from V5.310 and higher cannot be used interchangeably. Consequently, you need to upgrade your existing pre-V5.310 VPAM datasets to the new format, or devise a strategy to enable you to work with both the old (in read only mode) and new formats. For more information, see Working with pre-V5.310 VPAM datasets in the Technical Reference.
Retrieving your program listings

For each of the program listings formats supported by DUMPMASTER, you must define the method used to retrieve the listings the listings search strategy before analyzing a dump. You do this using the Listing Search Options screen:
56
CHAPTER 3
DUMPMASTER - Listing Search Options
Row 1 of 6
To define how DUMPMASTER searches one or more repositories for a compiler listing, complete or modify the details listed below and press ENTER. When your changes are complete press PF3. Action : I Insert, R Reproduce, D Delete or 1 - 99 for new sequence Search : VPAM, SERVER, PDS or 'OEMname' (OEM utility definition module name) Details : (VPAM only) Leave blank (SERVER only) Scheme name (PDS or 'OEMname') DSname(s) Options : (VPAM or SERVER) Leave blank (PDS or 'OEMname') PT Pre-search prompt, CK Check compile date & time Action Search Details Options 1 .......... .................................................... ....... 2 SERVER R1 3 PDS 'HGW.PL1.LISTING.PDSE' PT 4 VPAM .................................................... ....... 5 'M4LSTPDS' 'HGW.PL1.LISTING.PDS' PT CK 6 'M4LSTVPM' 'DMB.VPAM.COBOL' CK ------------------------ End of Listing search options -----------------------Command ===>
These definitions tell DUMPMASTER how to retrieve the program listings. Once the definitions have been established they are saved by DUMPMASTER, but may be amended as required. The rest of this section briefly describes how to set up the required listings search strategy entries for the method(s) of your choice. For details, refer to Defining the listings search strategy on page 58. Program listings stored in a VPAM dataset Although individual users can add their own VPAM datasets (see Establishing individualized VPAM listing archives in the DUMPMASTER MVS Technical Reference), program listings are usually stored in one or more VPAM datasets which have been made accessible to all DUMPMASTER users.
Note
This task is normally performed by your System Administrator. For more information, see Administrators online facilities in the DUMPMASTER MVS Technical Reference.
In the listings search strategy, all that you need to specify is an entry with the value
VPAM in the Search column. For more information on using and administering
VPAM datasets (including how to browse, delete, or print individual members), see Working with VPAM program listings online on page 159. Program listings stored in a PDS or PDSE If the program listings are held in a PDS or PDSE, in the listings search strategy you specify the value PDS in the Search column, and in the corresponding Details column you specify the relevant dataset name(s). For more information, see Listings search options on page 58. Program listings stored in an OEM repository To retrieve program listings from an OEM repository, an OEM utility definition module which is a special REXX EXEC must be set up and customized to the needs of your Installation.
CHAPTER 3
57
Note
This task is normally performed by your System Administrator. For more information, refer to the appendix entitled Defining OEM listings datasets in the DUMPMASTER MVS Technical Reference; in particular, consult the section Customizing OEM utility definition modules for details on how to set up and use an OEM utility definition module.
In the listings search strategy, you specify the name of the OEM utility definition module (that is, the REXX EXEC) in the Search column, and in the corresponding Details column you specify the name(s) of the listings repository dataset(s). For details, see Listings search options on page 58. Program listings stored remotely If the program listings are held on a remote system, an AAServer (Application Availability Server) must be set up and configured to communicate with the remote system and retrieve the required program listing(s).
Note
This task is normally performed by your System Administrator. For more information, refer to the appendix entitled Configuring an AAServer in the DUMPMASTER MVS Technical Reference.
In the listings search strategy, you specify the value SERVER in the Search column, and in the corresponding Details column you specify a name to identify the Scheme which defines how listings are to be retrieved from the listings repositories. For details, see Listings search options on page 58.
58
CHAPTER 3
Defining the listings search strategy

Listings dataset formats Listings search options How to retrieve a remote listing
below below page 62
Listings dataset formats

DUMPMASTER supports compilation listings in the following dataset formats:
I
Macro 4s VPAM (Virtual Partitioned Access Method). IBMs PDS and PDSEs. Other manufacturers listing datasets.
Additionally, DUMPMASTER may be configured to retrieve compilation listings which are held in a repository (VPAM, PDS/PDSE, or OEM) that is remote to the DUMPMASTER instance on which a dump is being stored and analyzed. Setting or changing listing dataset type(s) For information on setting or changing the compilation listing dataset type(s), see Listings search options below.
Listings search options

Select option 1 (= Search Strategy) from the Listings pull down menu (see page 53) and the DUMPMASTER - Listing Search Options screen appears. You use this screen to define how DUMPMASTER searches one or more repositories for a compilation listing.
DUMPMASTER - Listing Search Options Row 1 of 6
To define how DUMPMASTER searches one or more repositories for a compiler listing, complete or modify the details listed below and press ENTER. When your changes are complete press PF3. Action : I Insert, R Reproduce, D Delete or 1 - 99 for new sequence Search : VPAM, SERVER, PDS or 'OEMname' (OEM utility definition module name) Details : (VPAM only) Leave blank (SERVER only) Scheme name (PDS or 'OEMname') DSname(s) Options : (VPAM or SERVER) Leave blank (PDS or 'OEMname') PT Pre-search prompt, CK Check compile date & time Details Options Action Search 1 .......... .................................................... ....... 2 SERVER R1 3 PDS 'HGW.PL1.LISTING.PDSE' PT 4 VPAM .................................................... ....... 5 'M4LSTPDS' 'HGW.PL1.LISTING.PDS' PT CK 6 'M4LSTVPM' 'DMB.VPAM.COBOL' CK ------------------------ End of Listing search options -----------------------Command ===>
The entries on this screen define the listings search strategy that is, the types of search to be performed by DUMPMASTER and the search sequence.
CHAPTER 3
59
For information on
See
Listing strategy default values Input fields on Listing Search Options screen How DUMPMASTER searches for a listing Listing strategy default values
below below page 61
If you are a System Administrator then option 5 (= LISTINGS) from the DUMPMASTER Administrators Menu (see page 43) enables you to establish a default strategy for end-users of the online component of DUMPMASTER who have not previously logged on. The Listing Search Options screen appears (see page 58). If you are an end-user of the online component of DUMPMASTER then option 2 (= Revert to Default Strategy) from the Listings pull down menu (see page 53) enables you to discard your personalized listings search strategy and revert to the search strategy defined by your System Administrator.
Input fields on Listing Search Options screen
The input fields on the Listing Search Options screen (see page 58) are described below. For information on how DUMPMASTER searches for a listing, see page 61. Action Indicates the search sequence number. To move the current line to the nominated line, hence altering the search sequence, overtype the entry in this field with a number in the range 1 99. Alternatively, to work with the entries displayed, specify one of these values:
I
I to insert a blank line after the current line. R to replicate a line that is, insert a copy of the line after the current line. D to delete the current line.
Search Specify VPAM, SERVER, PDS or 'OEMname' to indicate the search type.
VPAM indicates that the listing should be retrieved from a local VPAM dataset. (Only one such entry is allowed on the Listing Search Options screen.) For more information, see Working with VPAM program listings online on page 159. SERVER indicates that the listing should be retrieved by an AAServer (Application Availability Server). Specify the name of the Scheme which defines how the listing is to be retrieved from the repositories in the Details field (see page 60).
Notes
a
Normally, an AAServer is configured to retrieve a listing from repositories that reside on a remote system. However, an AAServer can also be configured to retrieve a listing from local repositories. For details of how to configure DUMPMASTER to retrieve compilation listings that reside on a remote system, see How to retrieve a remote listing on page 62.
60
CHAPTER 3
PDS indicates that the listing should be retrieved from a local PDS dataset.
Specify the name(s) of the PDS dataset(s) in the Details field (see below). 'OEMname' indicates that the listing should be retrieved by the named OEM utility definition module. Enclose the name in single quotes. Specify the name(s) of the listing repository dataset(s) in the Details field (see below). Details
Note
This field is relevant only to a search type of SERVER, PDS or 'OEMname'; for a search type of VPAM, leave this field blank.
The value that you enter in this field depends on the value that you specified for Search (see page 59).
I
If the value was SERVER: Specify a name consisting of a maximum of eight characters to identify the Scheme which defines how listings are to be retrieved from the repositories. For more information on Schemes, see the DUMPMASTER MVS Technical Reference. If the value was PDS or 'OEMname': Specify the relevant dataset name(s) DUMPMASTER will only accept names that refer to existing datasets. Enclose a fully qualified dataset name in single quotes, otherwise the dataset name you supply will be prefixed automatically by your TSO userid.
Options
Note
This field is relevant to a search type of either PDS or 'OEMname'; for other search types (that is, VPAM or SERVER), leave this field blank.
The possible values for Options are PT and/or CK:

PT (Pre-search prompt)
Indicates that during dump analysis, when access to the listing is required, DUMPMASTER should display a panel which enables you to change the search details before the search is performed. This option is not applied by default unless you used an earlier version of the product to retrieve a listing from either a PDS library or OEM repository. The form of the panel displayed depends on the value that you specified for the search type (see Search on page 59). If the search type was PDS: The panel enables you to re-specify the PDS library(ies) to be searched and/or the search sequence see page 69. If the search type was 'OEMname': The panel enables you to re-specify the OEM dataset name(s) and/or the print/extract parameters see page 70.
CK (Check compile date & time)
Specifies that a listing should be retrieved automatically only if its compilation date and time matches the values derived from the dump. This option is not applied by default. (In contrast, for a search type of VPAM, compilation date and time checking is applied automatically.) (A similar option, CHECKDT, can be specified for a listings search performed by an AAServer. For more information, see the DUMPMASTER MVS Technical Reference.)
CHAPTER 3
61
How DUMPMASTER searches for a listing
The following steps are performed by DUMPMASTER during dump analysis, when access to the listing is required:
1
A program listing analysis is initiated either automatically (for a failing module) or manually (using Point and Shoot) which triggers DUMPMASTER to search for the matching listing. DUMPMASTER works through the searches defined on the Listing Search Options screen (see page 58) in the sequence specified. Notes
a b
For more information on how to use a listing held on a remote system, see How to retrieve a remote listing on page 62. If an error arises during a particular search then a message is issued by DUMPMASTER and all subsequent searches in the sequence are aborted.
The actions that are subsequently taken by DUMPMASTER depend on the program language and whether or not the specified listing is found.
3
(For Assembler.) Unlike compiled high-level languages (COBOL, PL/I, and so on), the date of the assembly is known but the time of the assembly is unknown. Since it is not possible to find an exact match (that is, the name and the compilation date/time match the values derived from the dump), the DUMPMASTER - Listing Choice screen will always appear and prompt you to select the correct listing from a list of candidates. For more information, see Listing Choice display on page 71.
Note
The DUMPMASTER listing search procedure uses the name of the CSECT in which the failure occurred to search for the appropriate listing. (By default, the first CSECT name in the Assembler program is used as the name under which the listing is stored in a VPAM dataset.)
(For compiled high-level languages.) For COBOL, PL/I, and so on, if a listing search returns an exact match then the matching listing is used automatically and no further searches are performed. Compilation date and time checking is dependent on the search type:
I
For a search type of VPAM: The compilation date and time is checked automatically. For a search type of SERVER: If the listing is stored in a VPAM dataset then the compilation date and time is checked automatically. Otherwise, these values are not checked unless the value CHECKDT was specified for the particular listings repository in the AAServer configuration. For more information, see the DUMPMASTER MVS Technical Reference. For a search type of either PDS or 'OEMname': The compilation date and time is not checked unless CK (check compile date & time) was specified in the Options field on the Listing Search Options screen (see page 59).
If all listing searches fail to return an exact match then DUMPMASTER displays a panel to inform you that the listing could not be positively identified. It lists alternatives (if any) found by all searches in the sequence that is, all listings having a matching name, but either the compilation date/time does not match the values derived from the dump, or date/time checking was not specified. For more information, see Listing Choice display on page 71.
62
CHAPTER 3
If no suitable listing is found then the Listing Not Found screen is displayed which enables you to specify a new listing name to be used to drive the (entire) search strategy. For more information, see page 68.
How to retrieve a remote listing

Under TSO online, DUMPMASTER provides screens that enable you to set the strategy for searching for remote listings in several dataset formats, and to specify the name of the AAServer running on your local system. Also, during dump analysis when access to the listing is required, a screen is presented which enables you to select a particular listing from a List of alternatives. Prerequisites for using a listing held on a remote system
1
Configure the AAServer(s). There is an AAServer in each system which requires or retrieves compilation listings. Each AAServer is a separate MVS Started Task (STC) which must be configured using a number of keyword parameters. For more information, see the appendix Retrieving remote listings in the DUMPMASTER MVS Technical Reference.
If a listing is to be retrieved from an OEM listings repository then customize the OEM utility definition module(s). Several REXX EXECs (for example, M4LSTOEM) are shipped with DUMPMASTER which define, in skeleton form, the processes required to obtain a listing from a particular OEM listings repository. For more information, see the appendix Defining OEM listings datasets in the DUMPMASTER MVS Technical Reference.
Specify the listing search options. You use the Listing Search Options screen to specify how DUMPMASTER should search for listings.
I
If you are a System Administrator: Use option 5 (= LISTINGS) from the Administrators Menu (see page 43) to establish a default listings search strategy for users who have not previously logged on.
If you are an end-user of the online component of DUMPMASTER: For information on how to specify your listings search strategy, see Listings search options on page 58.
Specify the AAServer name. The default name for the AAServer is AASERVER (see AAServer STC in the DUMPMASTER MVS Technical Reference). However, if you are testing a new release of DUMPMASTER then you may need to run more than one AAServer per MVS Logical Partition. In this case, use the Dump Viewing Options screen to specify an alternative name. For more information, see VIEW dump viewing options on page 23.
CHAPTER 3
63
Select a listing during dump analysis. On successful completion of the previous steps, if a listing is retrieved having values (program id and, if applicable, compile date & time) that match the values derived from the dump then this listing is used automatically by DUMPMASTER in subsequent analyses. Otherwise, the DUMPMASTER - Listing Choice screen prompts you to select an alternative listing during dump analysis, when access to the listing is required. For more information, see Listing Choice display on page 71. If no suitable alternative listing is found then the Listing Not Found screen is displayed which enables you to specify a new listing name to be used to drive the (entire) search strategy. For more information, see page 68.
64
CHAPTER 3
Abend Summary Display (ASD)

The dynamic Abend Summary Display (ASD) is the primary DUMPMASTER analytical display, so it is the first display to be presented once you have selected a specific dump. Information on an ASD is usually enough to diagnose the program error; if not, it serves as the gateway to subsequent in-depth dump analysis.
Overview (Display content; Date and time of dump capture; Source listing support; Point and Shoot; Action Bar; Dump Display Fast Path facility) Support for IAM datasets Listing choice (IBM PDS/PDSE libraries or OEM repository) Capturing and displaying the job log Example ASDs (For COBOL, PL/I, CICS, Assembler, DB2, IMS, Language Environment, and WebSphere MQSeries)
below
page 66 page 68
page 72 page 73
Overview
See:
I
Display content below Date and time of dump capture below Source listing support displays on page 65 Point and shoot on page 65 Action Bar on page 65 Dump Display Fast Path facility on page 65
Display content An ASD is high-level and process-oriented, and its format and content is variable and dynamic. Therefore, the elements displayed depend upon the dump type (Batch or CICS), the program language (Assembler, COBOL, DB2, IMS, PL/I, and so on), and whether or not Source Listing Support is enabled (see below). For example, when the dump is for a COBOL program, the detailed display content and the additional diagnostics it presents are COBOL-oriented and shown in terms familiar to the COBOL user. (Additionally, a brief, formal hexadecimal or Assembler-oriented display is always available to users who require it. See System View display on page 117.) Date and time of dump capture For a particular dump, the date and time the dump was taken is reported near the top of the ASD:
CHAPTER 3
65
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display ******************************* Top of Display ******************************** Dump No 378 Job DMUVWXYZ Step DMSTCS02 was taken on 22/05/98 at 13.51 Program WXYZ
Usually, this date and time is the same as the time of the abend; for CICS system dumps, this is the date and time on which the SVC dump was taken by CICS. Source listing support displays If Source Listing Support is enabled, and the listing is available for the program language (Assembler, PL/I, and so on), then the following analytical displays will be accessible from the ASD:
Failing Statement Display
Source Display
Selected Statement Display
Point and shoot All ASD displays are Point and Shoot oriented (see Dynamic 'Point and Shoot' access to information on page 50). As they are produced, a dynamic window superimposed on the display shows the progress of the analysis. Many displays resulting from Point and Shoot operations also contain Point and Shoot indicators or fields which can lead to further, detailed diagnostic information. (The use of Point and Shoot techniques is simple and intuitive, giving rapid access to pertinent data or diagnostic information to aid in problem analysis and resolution.) Action Bar The ASD has an action bar for Navigation, Setup, Listings, Advanced, and so on. From the appropriate pull down menu (see Pull down menus on page 52), access to further displays (for example the Current Display List, Note Lists, Macro 4 Diagnostics, and Help) is available. Dump Display Fast Path facility Usually, you select a dump for investigation by specifying your search criteria on the appropriate DUMPMASTER Dump Selection display (MVS or CICS).
66
CHAPTER 3
However, for certain DUMPMASTER messages written to SYSLOG, the Dump Display Fast Path facility enables you to display the corresponding dump directly. In this case, the dump details (dump dataset name, dump number, and so on) are extracted from the selected message. For more information, see Displaying a dump directly from SYSLOG on page 41.
Support for IAM datasets

Innovation Data Processings IAM (Innovation Access Method) is a highperformance, indexed access method for operating systems such as MVS/ESA and OS/390. The IAM dataset format, which simulates IBMs VSAM (Virtual Storage Access Method) file types ESDS and KSDS (Entry Sequenced and Key Sequenced Data Set respectively), offers several advantages over VSAM, such as:
I
Reduced CPU usage and faster I/O times. Improved space utilization on DASD. Lifting of the 4.3 Gb file size restriction in VSAM prior to DFSMS V1.3.
DUMPMASTER V5.310 and higher supports the IAM control block structure, and displays information for IAM and VSAM datasets in a similar way. For more information, see Example DUMPMASTER displays for IAM datasets below.
Example DUMPMASTER displays for IAM datasets
I/O Summary display If an open IAM dataset is associated with a dump then it will be listed on the DUMPMASTER I/O Summary display. To reach this display, an example of which is shown below, select the Point and Shoot item I/O Summary from the ASD.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Summary of Open Files ******************************* Top of Display ******************************** Point & shoot . DD names below to display file details . . . . . . . . . DD name IRSFILE IRSFILEO PRINT01 PRINT02 PRINT03 PRINT04 PRINT05 CTASDCPX SYSUDUMP Access QSAM QSAM JES2 JES2 JES2 JES2 JES2 IAM JES2 Disp EXCPs Dataset Name SHR 4 DCTS.SQ.S01.CTB905 NEW 0 DS6S25.IRSLCN NEW 0 DS6S25.DS6S25IL.JOB30873.D0000101.? NEW 0 DS6S25.DS6S25IL.JOB30873.D0000102.? NEW 0 DS6S25.DS6S25IL.JOB30873.D0000103.? NEW 0 DS6S25.DS6S25IL.JOB30873.D0000104.? NEW 0 DS6S25.DS6S25IL.JOB30873.D0000105.? SHR 4 DCTS.VS.S01.CTSADCPX NEW 0 DS6S25.DS6S25IL.JOB30873.D0000106.?
****************************** Bottom of Display ****************************** Command ===> Scroll ===> CSR
Consider the entry for DD name CTASDCPX, which appears near the bottom of the list. Immediately to the right of the DD name, the descriptor IAM is shown in the Access column, which indicates that the associated dataset has the IAM format.
CHAPTER 3
67
IAM File Details display To view detailed information for an IAM dataset, Point and Shoot on the . indicator to the left of its DD name on the I/O Summary display (see above). A File Details display for an IAM dataset shows information such as:
I
Request and OPTCD summary for the last used RPL. Record summary for the last used RPL. Record key from the last used RPL.
An example of such a display is shown in the next figure.

Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Details of CTASDCPX File ******************************* Top of Display ******************************** Dataset Name-------: Volumes------------: Disposition -------: Access Method------: Dataset Type-------: Access Type--------: Macrf--------------: DCTS.VS.S01.CTSADCPX ATS616 SHR IAM KSDS Base cluster Key,Dir,In,Nsr
Maximum Record Size: 90 CI Size------------: 4096 Index CI Size------: 4096 Active strings-----: COUNT Last used RPL's Request and OPTCD Summary The last request was a "GET", which completed normally. The RPL's address is The OPTCD specified SYN(synchronous), LOC(locate mode), NUP(no update), SEQ(sequential access), FKS(full key search), KEQ(search for key equal), ADR(locate the record by an RBA), ARD(users argument determines the record), and FWD(process forwards). Last used RPL's Record Summary The record from the last used RPL has an RBA of 00000000, a length of 90 and is at address 00006DE4 Record Key from the last used RPL Char Zone Digit ...0 010F 0100 1...
Record from the last used RPL Char Zone Digit Char Zone Digit ...0988988987..................................... 010FFFFFFFFFF7300000000000000000000000000000000000 01009889889875002000000000000000000000000000000000 1...5...10....*...20....*...30....*...40....*...50 ........................................ 0000000000000000000000000000000000000000 0000000000000000000000000000000000000000 51...*...60....*...70....*...80....*...90
ACB: 000596C4 DEB: 009CB208 ****************************** Bottom of Display ****************************** Command ===> Scroll ===> CSR
This File Details display is similar to the corresponding display for a VSAM dataset (see Typical ACB display on page 133).
68
CHAPTER 3
Specifying a listing
DUMPMASTER searches for compilation listings during dump analysis, when access to the listing is required. The entries on the DUMPMASTER - Listing Search Options screen define the listings search strategy for more information, see Listings search options on page 58.
Note
For more information on how to use a listing held on a remote system, see How to retrieve a remote listing on page 62.
Pre-search listing selection For a search type of either PDS or 'OEMname', if PT (pre-search prompt) was specified in the Options field on the Listing Search Options screen (see page 59) then DUMPMASTER displays a panel which enables you to change the search details before the search is performed. For more information, see:
I
PDS/PDSE listing selection on page 69. OEM listing selection on page 70.
Listing cannot be positively identified For compiled high-level languages (COBOL, PL/I, and so on), if all listing searches fail to return an exact match (that is, the name and the compilation date/time match the values derived from the dump) then DUMPMASTER displays a panel to inform you that the listing could not be positively identified. This panel also lists alternatives (if any) found by all searches in the sequence for more information, see Listing Choice display on page 71.
Note
For Assembler, unlike compiled high-level languages, the date of the assembly is known but the time of the assembly is unknown. Since it is not possible to find an exact match, the Listing Choice screen will always appear and prompt you to select the correct listing from a list of candidates.
Listing not found If no suitable listing is found then a screen like this will be displayed:
DUMPMASTER - Listing Not Found DUMPMASTER is searching for the compiler listing for a PL/I program, identified in the dump as MQPL1 compiled on 17 Jun 2002 13:42:17 The compiler listing to be retrieved is member MQPL1 , but a listing of this name was not found using the current search strategy. - If the compiler listing is stored under a different name then type the correct name here: MQPL1 , and press ENTER. (DUMPMASTER will search for it using the current search strategy.) - To proceed without a compiler listing, enter the END command. (No attempt will be made to retrieve the listing shown above.) Command ===>
This screen enables you to specify a new listing name to be used to drive the (entire) search strategy.
CHAPTER 3
69
PDS/PDSE listing When a program compilation listing is to be acquired from a local PDS or PDSE, if PT (pre-search prompt) was specified in the Options field on the Listing Search selection
Options screen (see page 59) then the PDS/PDSE Listing Choice panel will appear before the search is performed.
DUMPMASTER - PDS/PDSE Listing Choice The failing program is JDHPL1A compiled 03 Nov 1998 15:02:56 Dump 1 of 4
The compiler listing to be retrieved is member JDHPL1A - If the correct listing datasets are shown below then press ENTER. (The listing will be retrieved from one of these datasets.) - Else, change or extend the search sequence shown below and press ENTER. (Possible Actions are I Insert, R Reproduce, D Delete, or 1 - 9 to specify a new search sequence number.) - To proceed without a compiler listing, enter the END command. (No attempt will be made to retrieve the listing shown above.) PDS/PDSE libraries in search order Comments Action PDS/PDSE DSName 1 ............................................. ....................... 2 DMB.D4700.PLI.PDS THE COLLECTION 3 HGW.PL1.LISTING.PDS my PDS ******************** End of PDS/PDSE listing dataset(s) ******************** Command ===>
The program/procedure name, as determined from earlier analysis, is shown at the top of the display. The input fields on this panel (see below) enable you to re-specify the PDS libraries to be searched, and/or the search sequence. Input fields on PDS/PDSE Listing Choice panel Action In the lower part of the panel, listing datasets are shown in search sequence. To move the current line to the nominated line, hence altering the search sequence, overtype the entry in this field with a number in the range 1 9. Alternatively, to work with the entries displayed, specify one of these values:
I
I to insert a blank line after the current line. R to replicate a line that is, insert a copy of the line after the current line. D to delete the current line.
PDS/PDSE DSName When you see the panel for the very first time, the datasets defined in the listings strategy will be displayed. If you know that the required member is contained elsewhere then use the Action field (see above) to re-specify the name(s) of any listing dataset(s) which might contain the member. To specify just one dataset name, overtype the empty entry; to specify more than one dataset name, use I (insert line) or R (replicate line) in the Action field.
Note
DUMPMASTER will only accept names that refer to existing datasets.
Subsequently, the list will hold your previous input, but the search sequence may be altered or extended if required. When you have supplied the required details, press Enter to initiate the search.
70
CHAPTER 3
OEM listing selection
Note
To use listings from an OEM repository you must customize a separate DUMPMASTER utility definition module (REXX EXEC) for each OEM utility that you intend to use. For details, see the appendix Defining OEM listings datasets in the DUMPMASTER MVS Technical Reference.
When a program compilation listing is to be acquired from a local OEM repository, if PT (pre-search prompt) was specified in the Options field on the Listing Search Options screen (see page 59) then the OEM Listing Selection panel will appear before the search is performed.
DUMPMASTER - OEM Listing Selection The failing program is PROGRM1 captured 05 Feb 2001 13:11:45
The compiler listing to be retrieved is member PROGRM1 - If the details shown below are correct then press ENTER. (The listing will be retrieved from the listing dataset shown below.) - Else, change the details below (as required for the OEM utility defined by exit OEMname ) and press ENTER. - To proceed without a compiler listing, enter the END command. (No attempt will be made to retrieve the listing shown above.) Listing dataset = 'QUAL.EG.PRCSLIST' Listing print/extract parameters: PRINT MEMBER 'PROGRM1' Command ===>
This panel enables you to re-specify the name of your OEM listing repository dataset, and/or modify the print/extract parameters. Input fields on OEM Listing Selection screen Listing dataset This field will initially contain the name of the repository that is defined in the listings search strategy, but you may overtype it as required. Listing print/extract parameters This heading, along with the parameter statements that follow it, will only be present if SHOWPARM utility setup commands have been specified in the DUMPMASTER utility definition module. In this case, the input fields are prefilled with values determined from earlier analysis; overtype them if you know that the values are different. When you have supplied the required details, press Enter to initiate a utility run. If it fails for any reason then the search continues with the next search defined in the listings strategy.
CHAPTER 3
71
Listing Choice display
If a DUMPMASTER listing search returns an exact match (that is, the name and the compilation date/time match the values derived from the dump) then no further searches are performed, and the listing is used by DUMPMASTER in subsequent analyses. See also How DUMPMASTER searches for a listing on page 61. However, if all listing searches fail to return an exact match then DUMPMASTER displays the Listing Choice panel, which lists alternatives (if any) found by all searches in the sequence:
Note
For Assembler, unlike compiled high-level languages (COBOL, PL/I, and so on), the date of the assembly is known but the time of the assembly is unknown. Since it is not possible to find an exact match, the Listing Choice screen will always appear and prompt you to select the correct listing from a list of candidates.
DUMPMASTER - Listing Choice Row 1 to 3 of 3
DUMPMASTER cannot positively identify the compiler listing for a PL/I program, identified in the dump as PAYOLA compiled on 26 Feb 1999 15:36:43 The compiler listing to be retrieved is member PAYOLA - If the correct listing dataset is shown in the table below then tab to the entry and press ENTER. (The listing will be retrieved from the selected listing dataset.) - Else, if the compiler listing is stored under a different name then type the correct name here: PAYOLA , and press ENTER. (DUMPMASTER will search for it using the current search strategy.) - To proceed without a compiler listing, enter the END command. (No attempt will be made to retrieve the listing shown above.) S Source Compiled . Local 26 Feb 1999 14:24:52 . Server 31 Jan 1998 13.01.01 . Local Unknown ************************* End Command ===> Access Listing dataset(s) PDS 'LOCAL.LISTING.PDS' PDS 'REMOTE.LISTING.PDSE' M4LSTNDV 'PROD.NDV.LISTINGS' of listing dataset(s) *************************
Notes 1
Under the Compiled heading, you may see Unknown against one or more entries in the list (see the last entry above), which indicates that the source was not examined to establish its compilation date and time.
I
If the source is Server (that is, for a search type of SERVER): The AAServer was configured such that CHECKDT was not specified for the listing. For more information on this option, see the DUMPMASTER MVS Technical Reference. If the source is Local (that is, for a search type of either PDS or 'OEMname'): The value CK was not specified in the Options field on the Listing Search Options screen (see page 59).
For more information on how to use a listing held on a remote system, see How to retrieve a remote listing on page 62.
From the Listing Choice panel you can perform one of the following actions:
I
Point and Shoot on an entry in the list of alternatives (if any) to indicate that the listing is to be used by DUMPMASTER in subsequent analyses. Re-specify the listing name, then press Enter to initiate another search. Issue the END command to proceed with the analysis without a listing.
For more information, see How DUMPMASTER searches for a listing on page 61.
72
CHAPTER 3
Capturing and displaying the job log

Messages written to the job log prior to an abend may be helpful in problem analysis and resolution. For OS/390 V2R10.0 and higher, the job log can be read while it is open. In a JES2 environment, the SDSB (Spool Data Set Browse) API may be utilized to request and retrieve the job log. How DUMPMASTER captures the job log For a Batch dump, DUMPMASTER V5.310 and higher checks for an appropriate release of the operating system. If your Installation is running JES2 with OS/390 V2R10.0 or higher then the DUMPMASTER subsystem will capture job log records. For a small job log, all the records will be captured; for a large job log, just the last 200 records will be captured. Captured job log records are written to the dump file as a Note with these attributes:
I
The Note name and the Subnote name are set to JESMSGLG. The Notess description is set to Joblog Information for a small job log, or Joblog Information abridged for a large job log. The Note is grouped with the Program associated areas (see Note List Generation pull down menu option on page 148).
How to display the job log To display the job log, select the Point and Shoot item Joblog Information from the ASD. For a small job log, all of the records will be shown (using ISPF Browse); for a large job log, just the last 200 records will be shown. Here is an example of a DUMPMASTER job log display:
DUMPMASTER JESMSGLG Browse Line 00000000 Col 001 080 Command ===> Scroll ===> CSR ********************************* Top of Data ********************************** J E S 2 07.58.44 07.58.44 07.58.48 07.58.48 07.58.48 07.58.49 07.58.49 07.58.57 07.58.57 07.58.58 07.58.58 07.58.58 J O B L O G -S Y S T E M 9 6 7 2 -N O D E
JOB02445 ---- XXXDAY, dd mmm yyyy ---JOB02445 IRR010I USERID M4USER5 IS ASSIGNED TO THIS JOB. JOB02445 ICH70001I M4USER5 LAST ACCESS AT 07:58:31 ON XXXDAY, mmm dd JOB02445 HASP373 TESTLOG STARTED - INIT 3 - CLASS A - SYS 9672 JOB02445 IEF403I TESTLOG - STARTED - TIME=07.58.48 JOB02445 *IEC507D E 1000,VPMVSB,TESTLOG,S010,TEST.DATE.PROTECT JOB02445 *05 IEC507D REPLY 'U'-USE OR 'M'-UNLOAD JOB02445 R 05,M JOB02445 IEC148I 713-08,IFG0194E,TESTLOG,S010,SYSUT2,1000,VPMVSB,TEST. JOB02445 DMB676I ADWT1 DUMPMASTER V9.999X DMBINTRH continuing with dum JOB02445 DMB615I ADWT1 V9.999X DMBINTRH Starting to take Dump No 20 fo JOB02445 DMB170I ADWT1 V9.999X Dump no. 20 on DSN - DMB.SOLO.DUMPFILE
******************************** Bottom of Data ********************************
To reveal portions of the job log that are not shown, reposition the display using the appropriate PF Key or ISPF command. Batch print and Instant Print implications When a Batch Print is produced for a dump, the report includes the job log if it is available. (An entry for the job log will be included in the reports table of contents.) When an Instant Print is produced for a dump, the report does not include the job log. (It is not included because the job log for the failing job is produced at the same time as the Instant Print.)
CHAPTER 3
73
Example ASDs (list of)

Abend Summary Displays, being high-level and process-oriented, are highly variable in format and content. Some typical displays are described in the sections that follow; depending upon the information available for analysis, not all displays will offer the same information or choices.
For information on an ASD for See
COBOL PL/I CICS transaction dump CICS system dump Assembler DB2 and IMS Language Environment (LE) WebSphere MQSeries
below page 79 page 90 page 96 page 98 page 105 page 111 page 113
It must be emphasized that the examples presented are just that examples. Not all dumps will produce as much information, but some may produce more. This is because the ASD is both flexible and dynamic, and brings the user as much pertinent information as is available from the specific dump under analysis, presenting it in format and terms suitable to the environment of the dump, be that COBOL, CICS, DB2, IMS, PL/I, and so on.
ASD for COBOL

In addition to the extensive information furnished on a COBOL ASD, additional displays are available through Point and Shoot operations on highlighted fields:
I
Abend code diagnostics, including Chicago-Soft QuickRef data if available (see Displaying abend code details on page 75). If Source Listing Support is enabled, and the listing is available, then failing statement displays will be accessible from the ASD. Otherwise, only basic COBOL details will appear on the ASD. See also:
I
Source listing support displays on page 65. Deferred listings analysis on page 24.
A detailed Dump Display at the abend address (00FD3658 in the example below); see Dump displays on page 129.
74
CHAPTER 3
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display ******************************* Top of Display ******************************** Dump No 378 Job DMUVWXYZ Step DMSTCS02 was taken on 22/05/98 at 13.51 Program WXYZ
Point & shoot . items below to select a display Program DMOS0C7 failed with Abend Code S0C7 in the following statement 000028 ADD NON-PDEC TO PDEC. 000029 * GO TO LOOP. 000030 * ADD 1 TO SUB. 000031 * SUBTRACT 2 FROM SUB. 000032 BACK. . . . . Failing statement with data Failing statement in source context Base Locators System View (failing instruction & operands) when executing the ADD
Load module WXYZ (cannot identify load library) Call chain (3 levels) Program Language . DMOS0C7 Cobol II . . . . . Last executed statement last executed statement no. 28 verb 1 , offset EE DMOTEST Cobol II called DMOS0C7 in statement no. 33 verb 1 , offset 28C *Unknown type called DMOTEST from address 00FD3658 All programs in Call Sequence (derived from R13) Call Sequence / Compiler Info / Registers I/O Summary Display System Enqueue Information
Note
For greater clarity, in DUMPMASTER V4.9 and higher, Language Environment (LE) modules are not listed in analytical displays.
Point and Shoot on the appropriate indicator (.) to present the information listed below; some of these items will not be accessible if there is no listing available.
I
A display of the failing statement with data (see COBOL Failing Statement display on page 76). A display of the failing statement with adjacent source language (see COBOL Source display on page 76). A display of the base locators for various sections of the program (Working Storage, and so on) and for any variably located or external data items (see Base Locators & Indexes display on page 77). A hexadecimal-oriented presentation of the failure (see System View display on page 117). Job log information, if it is available (see Capturing and displaying the job log on page 72). A display of captured linkedit information (if the load library can be identified). CA-Panexec support In addition to supporting LINKEDIT information held in an IBM PDS or PDSE dataset, the CA-Panexec format (Computer Associates International, Inc.) is supported. Note that the CA-Panexec API modules should be globally available via the LINKLIST or the LPA.
CHAPTER 3
75
A list of the programs involved, in call sequence (derived from R13). Information on the call sequence, compiler, registers, and so on. An I/O Summary for all files which were open when failure occurred (see I/O Summary display on page 131). A display of system ENQs and status (see Enqueue list on page 134).
Displaying abend DUMPMASTER can interface with the Chicago-Soft QuickRef database, or with the IBM CMAC file for CICS abends. To display specific abend code diagnostics, Point code details
and Shoot on the abend code (S0C7) from the ASD (see ASD for COBOL on page 73). For example, if the DUMPMASTER interface to QuickRef is enabled, a list of all matching entries from the QuickRef database is displayed:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------List of QuickRef Matches ******************************* Top of Display ******************************** . . . Item S0C7 S0C7 S0C7 Vendor CANDLE IBM STORAGE TEC. Product !DB(R)/WORKBENCH DB2 OS/390 SYSTEM CODES SCP MESSAGES Release V300 V2R5 V2R0M1
****************************** Bottom of Display ******************************
Command ===>
Scroll ===> CSR
Point and Shoot on the most pertinent entry from this list to display the details for the specific abend code, for example:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Code info from QuickRef ******************************* Top of Display ******************************** Copyright (c) 2001, IBM System ABEND: S0C7 Description: This ABEND is a data exception and can only occur when decimal (packed) instructions are used. One of the following can cause this error: 1) The sign or digit codes of one or more bytes manipulated by the packed or CONVERT TO BINARY instructions is invalid for packed decimal use. Packed decimal digits must be in the range 0 through 9, with only the sign digit being a digit in the range A through F. 2) Fields in decimal (packed) arithmetic overlap incorrectly. Scroll ===> CSR
Command ===>
76
CHAPTER 3
COBOL Failing Statement display
Point and Shoot on the Failing statement with data item on the ASD (see ASD for COBOL on page 73) and a display similar to the one shown below will appear:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------IGYTCARA Failing Statement ****************************** Start of display ****************************** To see the statement in source context, or any of the data definitions, tab to the highlit sequence number and press Enter. Program IGYTCARA failed with Abend Code S0C7 in the following statement 001695 compute tot-mins when executing the COMPUTE
= function sum (stored-minutes(all)).
The following data are referenced by the statement SeqNo Data Definition WORKING-STORAGE SECTION 000868 05 STORED-MINUTES (23) PIC 9999 DISP-NUM OCCURS 50 Content: 17 Subscripts: 23 To display content, overtype subscripts above and press 000873 77 TOT-MINS PIC 9(4) DISP-NUM VALUE ZERO Content: ZERO . . Source Listing display - start of Data Division Full Data Division map (this could take some time) Address 0000D218 Enter 0000D288 Length 4
******************************* End of display ******************************* Command ===> Scroll ===> CSR
This display shows the failing (or any selected) COBOL source language statement in the failing COBOL program, together with the data names referenced by the statement.
Note
To display other element values, overtype the appropriate subscript values.
On the Failing Statement display, a choice of dynamically-generated options is presented, based on program specific diagnostic information available to DUMPMASTER; for example, you can see the statement in source context (see COBOL Source display below). DUMPMASTER provides support for indexed arrays in COBOL see Support for COBOL indexed arrays on page 77.
COBOL Source display
Point and Shoot on the Failing statement in source context item on the ASD (see ASD for COBOL on page 73) and a display like the one shown in the following figure will appear; note that you can scroll backwards or forwards through the program listing.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------IGYTCARA Source 001691 * calculate the total miles driven 001692 compute tot-miles = function sum (stored-miles(all)). 001693 001694 * calculate the total minutes driven 001695 compute tot-mins = function sum (stored-minutes(all)). 001696 compute tot-hours = tot-mins / 60. 001697 compute tot-minutes = function mod (tot-mins 60). 001698 001699 write print-record from i-f-header-line-11. 001700 write print-record from i-f-header-line-12. 001701 write print-record from i-f-header-line-13. 001702 Command ===> Scroll ===> CSR
CHAPTER 3
77
Support for COBOL A COBOL data definition containing an OCCURS clause (that is, defining a table) can be INDEXED BY an index. For nested OCCURS definitions, an index can be indexed arrays
associated with each level of nesting, for example:
01 ARRAY-IXD-FAIL REDEFINES ARRAY-IXD-INV. 10 LEV1-IXD-FAIL OCCURS 5 TIMES INDEXED BY IXF1. 20 LEV2-IXD-FAIL OCCURS 5 TIMES INDEXED BY IXF2 PIC S9(3) COMP-3.
For referenced indexed data items, DUMPMASTER shows the data accessed by the current index values; to display other element values, overtype the subscript values:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------CBLTEST4 Failing Statement 000080 ADD +32 TO LEV2-IXD-FAIL IN ARRAY-IXD-FAIL (IXF1,IXF2)
The following data are referenced by the statement SeqNo Data Definition Address WORKING-STORAGE SECTION 000041 IXF1 INDEX-NAME 00006A98 Content: X'0000,0000' *** or subscript 1 in table 000042 20 LEV2-IXD-FAIL (1,2) PIC S9(3) COMP-3 OCCURS 5 00006B5A Content: X'0000' *** not valid COMP-3 data. Subscript: 1,2 To display content, overtype subscript above and press Enter 000043 IXF2 INDEX-NAME 00006A9C Content: X'0000,0002' *** or subscript 2 in table . . Source Listing display - start of Data Division Full Data Division map (this could take some time) Length 4 2
Also, when an index is displayed as a data item, the subscript corresponding to the stored offset is shown. For example, for index IXF1 the subscript is 1; for index IXF2 the subscript is 2.
Note
To display other element values, overtype the subscript values.
Support for COBOL LOCAL-STORAGE supports recursion because it defines storage that is automatically allocated, initialized and deallocated on every invocation. LOCAL-STORAGE
In DUMPMASTER V5.310 and higher, for recent versions of the COBOL compiler (that is, COBOL for OS/390 and VM, and higher), this sort of storage is shown on the following displays:
I
Base Locators & Indexes display The Point and Shoot item Base Locators is present on a number of displays for example, the ASD, the Call Sequence/Compile Info display, or the Programs in Call Sequence display. Select this item and the Base Locators & Indexes display will appear; LOCAL-STORAGE locators are identified as BLK:
78
CHAPTER 3
Navigation Setup Listings Advanced Traces Help ----------------------------------------------------------------------------FCTORIAL Base Locators & Indexes ****************************** Start of display ***************************** Cobol/370 program FCTORIAL failed with Abend Code S0C7 at offset 332 No files were defined Working Storage BLW=0000 06B004E0 F0F0F0F000000000F0F0F0F0F0F0F0F1 * 0000....00000001 * No indexes were defined No variably located areas were defined No EXTERNAL data was defined Local Storage BLK=0000 000269A0 F0F0F0F0000000000000100100024018 * 0000.......... . * Linkage Section BLL=0000 00000000 ******************************* End of display ****************************** Command ===> Scroll ===> CSR
Data Division Map display To see this display, Point and Shoot on Data Division Map from either the Call Sequence/Compile Info display or the Programs in Call Sequence display. LOCAL-STORAGE variables appear under the heading LOCAL-STORAGE SECTION:
Navigation Setup Listings Advanced Traces Help ----------------------------------------------------------------------------FCTORIAL Data Division Map ****************************** Start of display ***************************** . SeqNo 000006 000007 000008 000009 000010 Failing, or last executed statement Data Definition WORKING-STORAGE SECTION 01 NUMB PIC 9(4) DISP-NUM VALUE 8 Content: ZERO 01 FACT PIC 9(8) DISP-NUM VALUE 0 Content: 1 01 SPACE-FIELD PIC X(2) DISPLAY VALUE SPACES Content: SPACE 01 INV-PD-FLD PIC S9(3) PACKED-DEC REDEFINES SPACE-FIELD Content: X'4040' *** not valid PACKED-DEC data. 01 NUMBER-ONE PIC S9(3) PACKED-DEC VALUE +1 Content: 1 LOCAL-STORAGE SECTION 01 NUM PIC 9(4) DISP-NUM Content: ZERO Address 06B004E0 06B004E8 06B004F0 06B004F0 06B004F8 Length 4 8 2 2 2
000012
000269A0
******************************* End of display ****************************** Command ===> Scroll ===> CSR
Note
A new Data Division display is generated for each program in the call chain. This is because LOCAL-STORAGE is typically used in programs that are called recursively and the values of the variables will probably be different on each invocation.
COBOL listing support displays On these displays, LOCAL-STORAGE variables appear under the heading of LOCAL-STORAGE.
CHAPTER 3
79
ASD for PL/I

An example of a PL/I ASD appears below. This display contains Point and Shoot items similar to those described for the COBOL ASD in ASD for COBOL on page 73.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display ******************************* Top of Display ******************************** Dump No 16 Job HGWPL120 Step GO was taken on 03/11/98 at 17.40 Program PL1203
Point & shoot . items below to select a display Program PL1203 procedure AN_INDEPENDANT_PROC failed with Abend Code S0C7 in statement no. 53 53 . . . . RETURN (fall_Over + AddFix + AddFloat + AddComplex) ; Failing statement with data Failing statement in source context PL/I procedure chain System View
Load module PL1203 was linked on 03/11/98 Load library HGW.APFLIB accessed via DDname STEPLIB . Linkedit Map Call chain (3 user levels in chain of 6) Last executed statement Program Language . AN_INDEPENDANT_PROC PL/I failed with Abend Code S0C7 executing statement no. 53 , offset A2 . ANOTHER_INTERNAL_ROUTINE PL/I called AN_INDEP in statement no. 43 , offset A8 . AN_INTERNAL_ROUTINE PL/I called ANOTHER_ in statement no. 36 , offset 41E . User programs in Call Sequence (derived from R13) . Call Sequence / Compiler Info / Registers . . I/O Summary Display System Enqueue Information
Notes 1
If Source Listing Support is enabled, and the listing is available, then failing statement displays will be accessible from the ASD. Otherwise, only basic PL/I details will appear on the ASD. See also:
I
Source listing support displays on page 65. Deferred listings analysis on page 24.
2 3
On the ASD, and on subsequent displays, DUMPMASTER will list PL/I PROCEDURE names found in the call chain. In PL/I displays, statement numbers in an active procedure (that is, one that is in the call chain) are highlighted, unless there is no machine code associated with them. You can tab to these highlighted statement numbers and press Enter to access further pertinent data or diagnostic information. For greater clarity, in DUMPMASTER V4.9 and higher, Language Environment (LE) modules are not listed in analytical displays.
80
CHAPTER 3
For information on
See
IBM VisualAge/Enterprise PL/I compiler PL/I Failing Statement display PL/I Source display PL/I Selective Data Item display Support for PL/I BASED variables PL/I Summary display Known restrictions in non-VisualAge PL/I support Known restrictions in IBM VisualAge/Enterprise PL/I support Capturing and displaying the job log
below page 81 page 82 page 83 page 83 page 84 page 85 page 87 page 72
IBM VisualAge/ Enterprise PL/I compiler
DUMPMASTER supports the IBM VisualAge PL/I and Enterprise PL/I compilers. There are differences between the listing produced by these compilers and the listing produced by a non-VisualAge PL/I compiler. These differences, which are not a result of the compilation options used, are reflected in DUMPMASTER online displays:
Non-VisualAge PL/I compilers VisualAge/Enterprise PL/I compiler
Statement number format Statement numbers are reported in ascending order. Statement numbering Active statements only are listed.
Statement numbers are reported in the format n.f, where f is the included file no., and n is the sequence within that file.
There is a statement number associated with every line in the file, including A single statement number is used to comments and blank lines. identify a statement consisting of more than one line. Numbered gaps are left if there are multiple statements on a single line.
Other differences
There are differences in the reporting of data item attributes, cross-references, aggregate lengths, and so on. These differences reflect the way the individual compilers report the data. Examples Shown below are a trivial example of a listing from a non-VisualAge PL/I compiler, and a simple example of a listing from the IBM VisualAge PL/I compiler.
Non-VisualAge PL/I compiler STMT 40 DCL VAR1 CHAR(1); DCL VAR2 CHAR(1); 42 DCL VAR3 CHAR(1);
In this example, the statement DCL VAR2 can be assigned to statement 41.
CHAPTER 3
81
IBM VisualAge PL/I compiler Line.File LV NT 52.1 1 DCL VAR1 CHAR(1); DCL VAR2 CHAR(1); 53.1 /* Here is an include 1.2 1 DCL PIC1 PIC '9' INIT(1), 55.1 /* Here is another include 1.3 2 DCL PIC2 PIC '9' INIT(2), 57.1 /*----------------------
In this example:
I
LV reports the statement level number and NT reports the nesting level.
There are two DCL statements for line number 52.1, which cannot be identified separately. Statements 1.2 and 1.3 are the result of %INCLUDE source statements which have been expanded by the preprocessor.
I
As a consequence of the statement number format, a high statement number can precede a low statement number for instance, statement 53.1 (line 53 from file 1) precedes statement 1.2 (line 1 from file 2).
Point and Shoot on the Failing statement with data item on the ASD (see ASD PL/I Failing Statement display for PL/I on page 79) and a display similar to the one shown below will appear:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------PL1203 Failing Statement ****************************** Start of display ****************************** To see the statement in source context, or any of the data definitions, tab to the highlit sequence number and press Enter. Program PL1203 procedure AN_INDEPENDANT_PROC failed with Abend Code S0C7 in statement no. 53 00053 RETURN (fall_Over + AddFix + AddFloat + AddComplex) ;
Data referenced by the statement SeqNo 49 Data item attributes Address Length FALL_OVER 04A014F7 2 /* PARAMETER */ UNALIGNED PICTURE'99' Content: '..' X'FCFC' *** Contains non-DISPLAY characters. ADDFIX 04A014E0 3 STATIC ALIGNED INITIAL DECIMAL FIXED (5,2) Content: 5.2 ADDFLOAT 04A014D0 16 STATIC ALIGNED INITIAL DECIMAL /* EXTENDED */ FLOAT (33) Content: 1.005201E+003 ADDCOMPLEX 04A014E3 8 STATIC ALIGNED INITIAL COMPLEX DECIMAL FIXED (7,0) Content: 21 + 10I
50 51 52
This display shows the failing (or any selected) PL/I source language statement in the PL/I program, together with the data names referenced by the statement. A choice of dynamically-generated options is presented, based on program specific diagnostic information available to DUMPMASTER. For example, you can:
82
CHAPTER 3
See the definition for the abend code (if it is displayed). Point and Shoot address fields to see the contents of the data names in the dump; see Dump displays on page 129. See the statement in source context (see PL/I Source display below), or any of the data definitions, by tabbing to the highlighted statement number and pressing Enter.
DUMPMASTER provides support for BASED variables in PL/I see Support for PL/I BASED variables on page 83.
PL/I Source display
Point and Shoot on the Failing statement in source context item on the ASD (see ASD for PL/I on page 79) and a display like the one shown in the following figure will appear; note that you can scroll backwards or forwards through the program listing.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------PL1203 Source AddFloat Float(33) INIT( 1005.2012 ) ; 52 DCL AddComplex Fixed Complex ( 7 ) init( 21 + 10I ) ; /*-------------------------------------------------------------*\ The failing statement appears below \*-------------------------------------------------------------*/ RETURN (fall_Over + AddFix + AddFloat + AddComplex) ;
53
54 END An_independant_proc ; 55 END PL1203 ; ***************************** Bottom of Display ****************************** Command ===> Scroll ===> CSR
If a statement number is highlighted then you can tab to it and press Enter to display the selected item and, if it is a structure, all the items within it. For more information, see PL/I Selective Data Item display on page 83.
Note
If the statement that you select is the one that failed in the PL/I program then the PL/I Failing Statement display will appear (see page 81).
CHAPTER 3
83
This display is invoked from the PL/I Source display (see page 82) by tabbing to a PL/I Selective Data Item display highlighted statement number for a data definition and pressing Enter. The selected item and, if it is a structure, all the items within it, will be displayed for example:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------PL1203 DCL statement 24 ****************************** Start of display ****************************** . Display statement 24 in source context
Subscripts: 1,1 To recreate display using different subscript value(s), overtype the above, and press Enter. Address Length Data item attributes 1 DATABITS 04A01550 76 STATIC /* STRUCTURE */ 2 BITTER (1,1) 04A01550 0(6) (*,*) /* IN DATABITS */ STATIC /* STRUCTURE */ 3 BITTEN (1,1) 04A01550 0(4) (10,10) /* IN BITTER IN DATABITS */ STATIC UNALIGNED BIT (4) Content: '0000'B 3 BITER (1,1) 04A01550 0(2) (10,10) /* IN BITTER IN DATABITS */ STATIC UNALIGNED BIT (2) Content: '00'B 2 BITPART 04A0159B (2) /* IN DATABITS */ STATIC UNALIGNED BIT (2) Content: '00'B Other options . Failing, or last executed statement ******************************* End of display ******************************* Command ===> Scroll ===> CSR
If the display lists any data item which is subscripted then the Subscripts field lists the subscript(s) used. When the first display for the data item(s) is created, all subscripts are assumed to be one, that is only the first instance of any subscripted items is shown. However, the subscripts may be altered in order to regenerate the display for other instances. To do this, overwrite the Subscripts field with the new subscript values, separated by commas or blanks, and press Enter. DUMPMASTER provides support for BASED variables in PL/I see Support for PL/I BASED variables below.
Support for PL/I In PL/I, the value of a variable declared as BASED maps over another storage area. BASED variables
Declarations based on a simple variable name Here is an example of a declaration based on a simple variable name:
DCL BASED_ON_POINTER3 BASED(POINTER3) BIT(100) VARYING;
For a declaration like this, DUMPMASTER will calculate the base address. Declarations based on constructs involving PL/I keywords A declaration can be based on more than a simple variable name, for example
ADDR(var_name), where var_name is the name of a variable. Here is an example
of this type of declaration:

DCL BASED_ON_ADDR2 BASED(ADDR(BASED_ON_ADDR1)) BIT(40);
84
CHAPTER 3
For such declarations, which can be far more complex than the one shown above, DUMPMASTER will not calculate the base address. Instead, you will prompted to enter the BASED address to use:
Data item attributes BASED_ON_ADDR2 BASED (*) UNALIGNED BIT (40) *** Cannot identify base for BASED Item. *** Enter BASED address to use 06b03a4d Address Length
After you have entered an address, the screen will be rebuilt using this address:
Data item attributes BASED_ON_ADDR2 BASED (*) UNALIGNED BIT (40) Content: '1110001111000101111000101110001111110001'B Other options . Failing, or last executed statement Alter address for BASED: 06b03a40 Address Length 06B03A4D (40)
If you need to re-specify the BASED address for any reason (for example, you mistyped the original address) then, on the rebuilt screen, enter the new address in the Alter address for BASED field.
PL/I Summary display
Use Point and Shoot on the PL/I procedure chain item on a PL/I ASD (see ASD for PL/I on page 79) to access a summary display that shows the PL/I DSAs chain:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Summary of PL1 DSAs chain ********************************* Top of Data ********************************* Point & shoot . . . . items below to select a display
All programs in Call Sequence (derived from R13) Call Sequence / Compiler Info / Registers System View (failing instruction & operands)
PL/I Procedure BEGIN block at +9F4 failed with PL/I OnCode 320 Failed at address: 06B015B6 , offset 24A from entrypoint. . Description of ONCODE 320 . Display failing PL/I statement EP : 06B0136C Static Storage : 06B01C20 Length : 3080 DSA : 00031838 Automatic Storage : 000318B0 Length : 168 TCA : 00015910 TCA Appendage (TIA) : 00051030 ... PL/I Procedure JDHPL1A failed with PL/I OnCode 320 Called from address: 06B011AA , offset 82A from entrypoint. . Description of ONCODE 320 . Display calling PL/I statement EP : 06B00980 Static Storage : 06B01C20 Length : 3080 DSA : 00031360 Automatic Storage : 000313D8 Length : 1120 TCA : 00015910 TCA Appendage (TIA) : 00051030 Compiled : 21 MAY 02 17:40:29 ******************************* Bottom of Data ******************************** Command ===> Scroll ===> CSR
For each identified PL/I procedure, the display shows the procedure name, the statement number and/or offset of the last executed statement, and the addresses of various PL/I storage structures associated with the procedure. To examine a PL/I storage structure, tab to the displayed address and press the Enter key.
CHAPTER 3
85
Known restrictions in non-VisualAge PL/I support
Note
If you are using the IBM VisualAge PL/I or Enterprise PL/I compiler, please refer to page 87.
The DUMPMASTER PL/I Listing analysis feature has a restricted capability under certain circumstances. The restrictions all concern the display of certain types of data, and generally are the result of data omitted or suppressed in the PL/I compiler listing; they are listed below, together with the reasons in each case.
I
INTERNAL CONTROLLED variables If the program is compiled without the LIST option then DUMPMASTER cannot display the values associated with INTERNAL CONTROLLED variables. The anchors for CONTROLLED variables are stored in the PRV (Pseudo Register Vector); this is built by the linkage editor each anchor has an external name, created by the compiler and listed in linkedit output. The difficulty arises because the compiler allocates an external name to each variable as it is encountered during the compilation. It would be possible for DUMPMASTER to determine the order of allocation (and hence the allocated names) only by analysing the actual source, but this would be a highly complex task. However DUMPMASTER can locate CONTROLLED variables when:
a
The compiler listing includes an object listing, because the actual offset in the PRV can be located in the dump by examining where the offset is stored by the linkage editor in the program. The CONTROLLED variable is defined as EXTERNAL, that is where the PRV entry has a specially defined external name, because the name can be located via the link/edit information in the dump.
More than one program in the same listing Two or more programs, separated by * PROCESS statements, may be compiled together and the listing output will include independent compilation reports for each program. It is a restriction in DUMPMASTER that only the first program will be processed the second and subsequent programs will be inaccessible for analysis purposes.
Source data suppressed with %NOPRINT If source is suppressed with %NOPRINT then DUMPMASTER may not be able to display certain information. Much can be derived from the subsidiary compilation reports, but DUMPMASTER needs the source listing for certain specific purposes:
I
To obtain the text of a failing (executable) statement. When an executable statement is suppressed, the ASD (see ASD for PL/I on page 79) and/or the Failing/Selected Statement display (see PL/I Failing Statement display on page 81) may only show the %NOPRINT statement, or even nothing at all. To identify the name of a variable referred to in a DEFINED clause. When the declaration of the DEFINED variable is suppressed, the displays of the variable will report it as inaccessible. To identify the order of parameters supplied to a procedure. When a procedure statement is suppressed, the displays of associated parameter variables will report them as inaccessible.
86
CHAPTER 3
Data items based on non-simple BASE pointers When the base variable is not listed in the Data Attributes for a based array or aggregate, DUMPMASTER may display it as inaccessible. When the base pointer is nominated via the ALLOCATE statement, and not in the based data item definition, DUMPMASTER will display it as inaccessible. When a structure is based on an expression, for example BASED(P+Q), DUMPMASTER will display it as inaccessible. When a structure is based on an array element, for example BASED(P(Q)), DUMPMASTER will display it as if it was based on P(1).
Aggregate items with offsets or lengths marked as ADJ For aggregate items, DUMPMASTER depends on the offset and length as displayed in the Aggregate Length Table report. If these fields are shown as ADJ, the data item may be displayed as inaccessible.
Data items DEFINED referring to indexed data items When a data item is declared as DEFINED referring to an indexed item (either a structure or an elemental item), the data item will be displayed as inaccessible.
Compiler applied adjustments for missing semi-colons When a semi-colon is omitted, the compiler may still be able to recognize the end of the statement, and act accordingly. However DUMPMASTER may not be able to identify the break between statements, especially when two or more statements occur in the same source line. The effect would be that the information for the second statement may be incomplete.
Label on a DECLARE statement A label coded at the start of a DCL statement will have the effect of hiding the declaration from DUMPMASTER analysis, as if it had been suppressed with %NOPRINT.
CHAPTER 3
87
Known restrictions in VisualAge/ Enterprise PL/I support
Note
If you are using a PL/I compiler other than the IBM VisualAge PL/I or Enterprise PL/I compiler, please refer to page 85.
The restrictions in IBM VisualAge/Enterprise PL/I support are listed below, together with the reasons in each case.
I
Use of DEFINED and POSITION() in PL/I declares According to the IBM VisualAge PL/I Language Reference, the DEFINED attribute specifies that the declared variable is associated with some or all of the storage associated with the designated base variable. The POSITION attribute, which can be used only with string-overlay defining, specifies the bit, character, or graphic within the base variable at which the defined variable is to begin:
DEFined reference [(reference)] [POSition(expression)]
where:
reference
Refers to the base variable, for which the storage is associated with the declared (defined) variable. The base variable can be EXTERNAL or INTERNAL. It can be a connected parameter. It cannot be BASED, DEFINED, or CONTROLLED. A change to the base variables value is a corresponding change to the value of the defined variable, and the other way round. The base variable can have adjustable extents. It should be specified as NONVARYING, with a data type of CHARACTER, BIT, or GRAPHIC (other data types produce unpredictable results).
expression
Specifies the position relative to the start of the base variable. If the POSITION attribute is omitted, POSITION(1) is the default. The value specified in the expression can range from 1 to N. The value N is defined in this example: N = N(B) - N(D) + 1, where N(B) is the number of bits, characters, or graphics in the base variable, and N(D) is the number of bits, characters, or graphics in the defined variable. In DUMPMASTER displays, the defining variable will always show POSITION(1) of the base variable. The reason for this is that the VisualAge/Enterprise PL/I compiler does not report the POSITION attribute in the ATTRIBUTES/XREF report. Consequently, for each DEFINED variable in the ATTRIBUTES report, the DUMPMASTER listing strategy requires the source code to be searched for the possibility of a POSITION attribute. If one is found then the expression is evaluated and converted to an integer value to produce a mapping offset.
I
AGGREGATE structure levels For the VisualAge/Enterprise PL/I compiler, the compilation listing AGGREGATE report determines a variables structure level by offsetting the identifier one character to the right of the previous level identifier:
88
CHAPTER 3
Source DCL 1 TREE 2 BRANCH 3 TWIG Aggregate Identifier TREE BRANCH TWIG
In DUMPMASTER, it is possible that the deepest elements within a multi-layered structure may not have any mapping data associated, resulting in them not being located in the dump. The reason for this is that a combination of long data names and many structure levels can lead to a rightmost truncation of one or more identifiers in the AGGREGATE report:
Identifier STRUCTURE_LEVEL_TOP STRUCTURE_LEVEL_NUMBER_02 STRUCTURE_LEVEL_NUMBER_03 STRUCTURE_LEVEL_NUMBER_04 STRUCTURE_LEVEL_NUMBER_05 STRUCTURE_LEVEL_NUMBER_06 STRUCTURE_LEVEL_NUMBER_07 STRUCTURE_LEVEL_NUMBER_08 STRUCTURE_LEVEL_NUMBER_09 STRUCTURE_LEVEL_NUMBER_1 STRUCTURE_LEVEL_NUMBER_ STRUCTURE_LEVEL_NUMBER
The solution is to either compare the AGGREGATE structure to the source code (if it exists) or create a comparison structure from the ATTRIBUTES report.
I
Unknown storage types In PL/I, storage types also known as data attributes describe computational data, program-control data, and program characteristics. Here is the full list of VisualAge/Enterprise PL/I data attributes:
AREA BINARY BIT CHARACTER COMPLEX DECIMAL DIMENSION ENTRY FILE FIXED FLOAT FORMAT GRAPHIC HANDLE LABEL NONVARYING OFFSET ORDINAL PICTURE POINTER PRECISION REAL RETURNS SIGNED STRUCTURE TASK TYPE UNSIGNED UNION VARYING VARYINGZ WIDECHAR
The data attributes highlighted above either generate no usable ATTRIBUTES or mapping data at compilation time, or are new in this version of the PL/I compiler and are not yet analyzed. Either way, they are not yet incorporated into the DUMPMASTER VisualAge/Enterprise PL/I listing strategy.
I
REFER option (self-defining data) In the following example, it is known that the array is BASED:
CHAPTER 3
89
071.1 072.1 073.1 074.1 075.1 082.1 083.1
DCL 1 REFEROPTION 3 ELEMENT_COUNT 3 ARRAY( MAX_AMT 5 ELEMENT1 5 ELEMENT2 DCL MAX_AMT DCL REFER_PTR
BASED(REFER_PTR), FIXED BIN(15), REFER (ELEMENT_COUNT) ), CHAR(04), CHAR(04) ; FIXED BIN(15) INIT(10) ; POINTER ;
However, if one of the array elements is referenced then the message UNKNOWN STORAGE TYPE is issued. The reason for this is that an AGGREGATE report is not produced for a self-defining structure such as this, and, without this report, the top structure data attribute cannot be passed down through the structure.
I
Begin-End statement delimiters A begin-block is a sequence of statements delimited by a BEGIN statement and a corresponding END statement. For example:
B: begin; statement 1 statement 2 . . . statement n end B;
If the failure occurs within the begin-block then the BEGIN statement is marked as the failing statement. The reason for this is that the VisualAge/Enterprise PL/I compiler creates a separate non-user PROCEDURE for each begin-block. The current DUMPMASTER VisualAge/Enterprise PL/I listing strategy deals only with user procedures, so the lines of code within a begin-block are lost. This leaves the begin-block as a program statement, and, since the BEGIN statement ends with a semi-colon, it is regarded as the end of statement.
I
Main PROCEDURE names greater than eight characters VisualAge/Enterprise PL/I PROCEDURE names, like variable names, are limited in size according to the compiler option LIMITS(NAME(n)), where n specifies the maximum length of variable names in the program. The maximum value (and default) for n is 100; the minimum value is 7. If a PROCEDURE name is longer than the defined limit then at compilation time it is contracted to be within the limit by the removal of surplus characters from the middle. For example, if the limit value was 100 and the PROCEDURE name was 110 characters in length then the first and last 50 bytes would be concatenated to form the contracted name. During listings capture, DUMPMASTER contracts any PROCEDURE name with a length greater than eight characters into an eight-character VPAM member name by concatenating the first and last four bytes of the program name. Therefore, take care to avoid duplicate names being created during listings capture, otherwise VPAM members may be overwritten. For example, if two programs are named MyChalkProgram and MyCheeseProgram, the same VPAM member name MYCHGRAM would be created. In this case, rename the programs to (say) MyProgramChalk and MyProgramCheese.
90
CHAPTER 3
Note
If the name of a program is too long to fit into the Title field of a DUMPMASTER display then the name will be replaced by a literal. For example, in a PL/I Source display: would appear unchanged would be replaced by:
MYPROG DCL STATEMENT 018.1
MY_LONGTITLED_PROGRAM DCL STATEMENT 018.1 SOURCE DCL STATEMENT 018.1
ASD for a CICS transaction dump

Note
DUMPMASTER V4.9 and higher supports only CICS/ESA 4.1 or higher, which includes any release of CICS TS.
CICS transaction dump No... appears near the top of an ASD for this sort of dump to distinguish it from a CICS system dump:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display ******************************* Top of Display ******************************** CICS transaction dump No 3 Job DMCICS41 Xact UPDT Program DFH0CALL
The rest of the top portion of an ASD for a CICS transaction dump is very similar to the top portion of a COBOL ASD (see ASD for COBOL on page 73) and includes the following Point and Shoot items: Abend Code Displays Chicago-Soft QuickRef data if available (see Displaying abend code details on page 75)
Failing statement with data Failing statement in source context System View This display will contain the CICS Symptom String, the CICS task ID & user ID, the CICS version, and so on
The bottom portion of the ASD contains sections specific to CICS support:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display The last EXEC CICS command executed was EXEC CICS READ (API) in Cobol/390 02.01.02 program DFH0CALL , transaction UPDT , task number 00037 The command completed successfully. . CICS Summary Load module DFH0CALL was linked on 23/07/02 Load library (PDS) AA.COMMON.CICSLIB accessed via DDname DFHRPL . Linkedit Map Call chain (Top 2 user levels in chain of 6) Program Language Last executed statement . DFH0CALL Cobol/390 failed with Abend Code ASRA at offset 1058 DFHAPLI called DFH0CALL from address 07BA995C DFHAPLI + X'270C' . User programs in Call Sequence (derived from R13) . Call Sequence / Compiler Info / Registers ****************************** Bottom of Display ****************************** Command ===> Scroll ===> CSR
CHAPTER 3
91
Note
If the EXEC CICS command did not complete successfully then the EIBRESP and EIBRESP2 response codes will be shown, for example:
The last EXEC CICS command executed was EXEC CICS DELETEQ TS (API) in HL Assembler program PROGA , transaction RJMA , task number 00031 . The command returned with non-zero response codes: EIBRESP = X'2C' (QIDERR) EIBRESP2 = X'00' (Normal)
Of particular relevance on the ASD is the Point and Shoot item CICS Summary. The CICS Summary display gathers together most of the detailed CICS information in the form of Point and Shoot items see CICS Summary display below.
CICS Summary display
From the ASD for either a CICS transaction or system dump, the Point and Shoot item CICS Summary is available. At the top of a CICS Summary is shown the CICS version and, for a transaction dump, the CICS user ID and transaction ID. Most of the other CICS information is gathered together in the form of Point and Shoot items on the CICS Summary display:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------CICS Summary ********************************* Top of Data ********************************* CICS Version: 4.1 Userid: RACFADM Transaction Id: UPDT
The last EXEC CICS command executed was EXEC CICS READ (API) in Cobol/390 02.01.02 program DFH0CALL , transaction UPDT , task number 00037 The command completed successfully. . . . . . . . EXEC CICS READ (API) in program DFH0CALL Display CICS Trace entries Display CICS Failing Screen Transaction information (CICS supplied) Current program info. (CICS supplied) CMAC Explanation of abend code unavailable Formatted Common System Area (CSA) 00045570 Formatted control blocks for Task Id 00037 , Trans Id
UPDT
******************************* Bottom of Data ******************************** Command ===> Scroll ===> CSR
Notes 1
If the CMAC dataset is not allocated then the CMAC explanation of the abend code will be unavailable (as in the example above).
From the CICS Summary display, you can quickly navigate to more detailed CICS data by further Point and Shoot operations. For example:
I
Select the Point and Shoot item Display CICS Trace entries to access the Application Level Trace display see CICS Trace Table displays on page 118.
92
CHAPTER 3
Unless this facility has been disabled in the configuration (see the CUSTOM statement in the DUMPMASTER MVS Technical Reference), Point and Shoot on Display CICS Failing Screen to display the last output buffer sent to the terminal at abend time. If capture of the CICS failing screen has been disabled then the message Data unavailable will be displayed. Select one of the Formatted items to view the relevant CICS formatted control block display see CICS formatted control block displays on page 93. For a CICS system dump, Formatted control blocks for Task Id items for user tasks appear before long running CICS tasks (such as CSNE). For a COBOL or PL/I dump, Point and Shoot on EXEC CICS to display the last executed CICS command, together with the referenced data names see Last EXEC CICS command on page 92. (This Point and Shoot item will be present only if data is available in the dump to recreate the command.)
Last EXEC CICS command On such a display, the source line that is shown is the call to the CICS routine itself (output from the CICS pre-processor) Call 'DFHEI1' in the example below rather than the EXEC CICS line that was coded by the user.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------DFH0CALL Statement at offset DCC ****************************** Start of display ****************************** To see the statement in source context, or any of the data definitions, tab to the highlit sequence number and press Enter. Program DFH0CALL 000675 000676 000677 Call 'DFHEI1' using by content x'0602f0002700008400f0f0f2f '3f5404040' by content 'FILEA ' by reference FILEA by reference dfhb0020 by reference NUMB IN COMMAREA end-call
The following data are referenced by the statement SeqNo 000158 000344 000380 000388 . . Data Definition Address Length WORKING-STORAGE SECTION 01 FILEA 07C295B8 80 Content: 'U000100S. D. BORMAN SURREY, ENGLAND 321...' X'E4F0,F0F0,F1F0,F0E2,4B40,C44B,40C2,D6D9,D4C1,D540,...' 01 COMMAREA 07C296B0 80 Content: ' 000100S. D. BORMAN SURREY, ENGLAND 321...' X'40F0,F0F0,F1F0,F0E2,4B40,C44B,40C2,D6D9,D4C1,D540,...' 03 NUMB PIC X(6) DISPLAY 07C296B1 6 Content: '000100' 01 DFHB0020 PIC S9(4) BINARY 07C29700 2 Content: 80 Source Listing display - start of Data Division Full Data Division map (this could take some time)
******************************* End of display ******************************** Command ===> Scroll ===> CSR
The EXEC CICS line that was coded by the user will be a few lines above the call to the CICS routine itself. To see it, tab to the highlighted statement number (675 in the example above) and press Enter:
CHAPTER 3
93
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------DFH0CALL SOURCE 000668 000669 000670 000671 000672 000673 000674 000675 000676 000677 000678 000679 000680 000681 000682 Command * IF THIS IS AN UPDATE REQUEST A FILE CONTROL "READ UPDATE" * READS THE EXISTING RECORD USING THE NUMBER STORED IN * "COMMAREA" BY THE LAST INVOCATION OF THIS PROGRAM. * *EXEC CICS READ UPDATE FILE('FILEA') INTO(FILEA) * RESP(RESPONSE) RIDFLD(NUMB IN COMMAREA) END-EXEC Move length of FILEA to dfhb0020 Call 'DFHEI1' using by content x'0602f0002700008400f0f0f2f '3f5404040' by content 'FILEA ' by reference FILEA by reference dfhb0020 by reference NUMB IN COMMAREA end-call Move eibresp to RESPONSE * * CHECK RESPONSE TO COMMAND * ===>
Scroll ===> CSR
On this display, the Call 'DFHEI1' statement is shown in source context; the EXEC CICS READ coded by the user is a few lines above it.
CICS formatted control block displays
The lower portion of a CICS Summary display for either a CICS transaction or system dump contains a number of Point and Shoot items that allow access to formatted displays of the major CICS control blocks of interest to an Applications Programmer. An example of a CICS Summary display for a CICS system dump appears below:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------CICS Summary ********************************* Top of Data ********************************* CICS Version: 4.1 The last EXEC CICS command executed was EXEC CICS DELETEQ TS (API) in transaction RJMA , task number 00031 . The command returned with non-zero response codes: EIBRESP = X'2C' (QIDERR) EIBRESP2 = X'00' (Normal) The task abended at, or near, the command displayed above. . . . . . . . EXEC CICS DELETEQ TS (API) in program PROGA Display CICS Trace entries Display CICS Failing Screen List of Domain Summary Notes CMAC Explanation of abend code unavailable Formatted Common System Area (CSA) 00045570 Formatted control blocks for Task Id 00031 , Trans Id Formatted control blocks for Task Id 00022 , Trans Id
RJMA CSNE
From here, select one of the Formatted items to view the relevant CICS formatted control block display. For either a CICS transaction or system dump, there will be two types of Formatted item on the CICS Summary display:
I
Formatted Common System Area (CSA) Point and Shoot on this item to view a formatted display of the CSA. (Note that there is one CSA per CICS system.)
94
CHAPTER 3
Formatted control blocks for Task Id nn , Trans Id xxxx For a CICS transaction dump, only one entry will appear for the particular task that has abended. For a CICS system dump, there will be one such item for each CICS transaction in the system at the time of the abend; items for user tasks appear before long running CICS tasks, such as CSNE.
See
For information on
Common System Area formatted display Select Formatted CICS Block display
below page 95
Common System Area formatted display From the CICS Summary display for either a CICS transaction or system dump, Point and Shoot on the item Formatted Common System Area (CSA) and a screen similar to the one shown below will appear:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Common System Area ****************************** Start of display ******************************* 00045570 Offset 000000 000000 000048 000048 000049 000049 <== Block base address Type Value DSECT 18F + 00045570 0B '00000000' B '00000000' 0B '00010000' B '00010000' EQU X'10' PL2 '+020' A 00057080 PL4 '+1523243' Description DUMMY SECTION - CSA CONTROL SYSTEM REGISTER AREA SHORT ON STORAGE INDICATOR SYSTEM SIGNAL INDICATOR 1 MAXIMUM NUMBER OF TASKS IND SYSTEM SIGNAL INDICATOR 2 = PLTPI PHASE HAS COMPLETED MAXIMUM NUMBER OF TASKS CURRENTLY DISPATCHED TASK ADDRESS TIME OF DAY. A PACKED INTEGER OF THE FORM HHMMSST WHERE HH IS HOURS, MM IS MINUTES, SS IS SECONDS AND T IS TENTHS OF A SECOND. Scroll ===> CSR
Label DFHCSADS CSAOSRSA CSASOSI CSASSI1 CSAKCMI CSASSI2 CSAPLTPI 00004A CSAKCMT 00004C CSACDTA 000050 CSATODP * * * * Command ===>
Point and Shoot on the item Block base address for a detailed Dump Display corresponding to this address (see Dump displays on page 129). Following the Block base address, the format of the body of the display is built from IBMs assembler DSECTs, which map the blocks. Information which has been extracted from the dump is displayed in the Value column there are three types of entry that can appear in this column:
1
A value, which is not highlighted and is enclosed in apostrophes ('). You cannot Point and Shoot on such an entry (for example, '+1523243' in the figure above), which represents actual data at the calculated address (Block base address+Offset) in the dump. A further example of this type of entry is an address for which the data pointed to by the address is not available in the dump:
000080 CSASPFPA A * '008B4000' ADDRESS OF SPECIAL FETCH-PROTECTED AREA
An address, which is highlighted and not enclosed in apostrophes.
CHAPTER 3
95
Point and Shoot on such an entry (for example, 00057080 in the figure above) for a detailed Dump Display corresponding to the address (see Dump displays on page 129).
3
An address, which is highlighted and prefixed by a + (plus) sign. The + indicates that the length of the data is longer than the maximum display length. Point and Shoot on such an entry (for example, + 00045570 in the figure above) for a detailed Dump Display (see Dump displays on page 129) that presents the data as unformatted fields.
Note
Some values in the control blocks are marked in the IBM DSECT as test bytes, in which case their contents are either tested for matching bit settings (masking) or are compared directly, as appropriate. Where corresponding values are found in the format, they are displayed without highlight:
CSAPLTPI EQU X'10' = PLTPI PHASE HAS COMPLETED
Select Formatted CICS Block display From the CICS Summary display for either a CICS transaction or system dump, Point and Shoot on an item of type Formatted control blocks for Task Id nn , Trans Id xxxx and a screen similar to the one shown below will appear:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Select Formatted CICS Block ********************************* Top of Data ********************************* The last EXEC CICS command executed was EXEC CICS READ (API) in Cobol/390 02.01.02 program DFH0CALL , transaction UPDT , task number 00037 The command completed successfully. 'Point and Shoot' to format the data in the block of your choice: Task number 00037 , transaction id . . . . . . DFHEIBLK DFHEIBLK DFHTCADS DFHTCADY DFHTCTTE UPDT : 001400D0 00055A8C 00055680 00055780 079A0228
EXEC Interface Block (User) EXEC Interface Block (System) Task Control Area (User) Task Control Area (System) Terminal Control Table Terminal Entry
List of transaction storage notes
This display shows the CICS task number, transaction ID, and the last EXEC CICS command executed from this task. This command is extracted from the relevant EXEC Interface Block (EIB) rather than from the users program source, so only the command type is given, not its detail.
Note
From the Select Formatted CICS Block display, Point and Shoot on a particular block to view a formatted display of the block applicable to the transaction ID:
96
CHAPTER 3
The format of each of these displays is similar to the Common System Area display (see page 94). The DFHTCTTE is included only if the relevant Task Control Area has a Facility Address that is, the task has a TCTTE.
Note
The TCTTE uses specific overlays from the IBM DSECT to map data this is dependent on the value of the terminal type field (TCTTETT).
The EIBFN (Function) and EIBAID (3270 key values) fields of the relevant EIB are interpreted to provide textual values.
ASD for a CICS system dump

Notes 1 2
DUMPMASTER V4.9 and higher supports only CICS/ESA 4.1 or higher, which includes any release of CICS TS. For a CICS system dump, optionally, all of the storage associated with the original MVS address space can be captured, so that you can view storage corrupted by violations that occur in MVS-related rather than CICS-related storage. For more information, see Reconfiguring for CICS system dump support in the DUMPMASTER MVS Technical Reference. If DUMPMASTER was configured at installation time to retain CICS system dumps, then they will be copied from SYS1.DUMPnn datasets into permanent datasets of the form hlq.Dyyyyddd.Thhmmss. hlq is a user-specified qualifier; the D and T fields indicate the date and time of copy (yyyy is the year, ddd is the day; hhmmss is the time in hours, minutes and seconds).
An example of an ASD for a CICS system dump appears below. The line CICS system dump No... appears near the top of the ASD to distinguish it from a CICS transaction dump. Also note the entry that appears a few lines further down informing you that this dump has been copied to a permanent dataset.
CHAPTER 3
97
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display ******************************* Top of Display ******************************** CICS system dump No 6486 Job FEWC410C was taken on 05/11/02 at 13.27 Xact Program DFHAPLI1
Point & shoot . items below to select a display This system dump has been copied to the following dataset in system dump format: 'PQM.D2001316.T140252' CICS Abend code = AKAE MVS Abend code = S0C4 Kernel error number = 007
CICS PSW at time of abend = 079D2000 000C234C CICS register contents at time of abend : 0-7 000C282A 00203460 00000000 000188B0 067099F0 0657997F 0657A97E 000C22EE 8-15 002030D0 000C2048 00000000 064858DC 002033F8 00203858 500C232A 00000000 Failing instruction at 000C2348 is at offset 0000001E in program REGDATA Failing instruction is BF213064 - ICM Operand 1 at 00018914 . . . . CICS Dump Summary note Domain Transaction Summary note Summary Notes - full list Discovered error notes R2,M1,0100(R3)
CICS System dump. The last EXEC CICS command executed was EXEC CICS READQ TS (API) in CICS transaction 00212 The command completed successfully. . CICS Summary ****************************** Bottom of Display ****************************** Command ===> Scroll ===> CSR
The bottom portion of the ASD contains sections specific to CICS support. As for a CICS transaction dump, the Point and Shoot item CICS Summary is present, which is described in CICS Summary display on page 91. For a CICS system dump taken as a result of either an EXEC CICS PERFORM DUMP command or a transaction dump being translated to a system dump by the use of the CICS dump table option, the last EXEC CICS command reported is the one issued by the application that caused CICS to generate the system dump:
I
Example resulting from an EXEC CICS PERFORM DUMP command:

The last EXEC CICS command executed was EXEC CICS PERFORM DUMP (SPI) in transaction RJMA , task number 00031 . The dump was taken as the result of the command displayed above.
Example resulting from use of the CICS dump table option:

The last EXEC CICS command executed was EXEC CICS DELETEQ TS (API) in transaction RJMA , task number 00031 . The command returned with non-zero response codes: EIBRESP = X'2C' (QIDERR) EIBRESP2 = X'00' (Normal) The task abended at, or near, the command displayed above.
98
CHAPTER 3
CICS system dump Note List displays Several Point and Shoot items are present on the ASD for a CICS system dump which, when selected, generate Note List displays:
Display invoked SUMM_DUM Browse (Dump summary) SUMM_AP Browse SUMMARY Notes
CICS Dump Summary note Domain Transaction Summary note Summary Notes - full list
(Summary print lines, Application domain) Notes of type SUMM_x, where x=AP (Application domain), DD (Directory Manager domain), DM (Domain Manager), etc.
Discovered error notes
ERRORS Notes
See Note lists on page 146 for more information about invoking and using Note List displays.
ASD for Assembler

Abend Summary Displays also present considerable diagnostic information for Assembler dumps but, due to the nature of the language, these dumps present fewer opportunities for meta-level analysis and interpretation. See:
I I
Basic Assembler details below Assembler mini-display on page 100
(if a matching listing is not available) (if a matching listing is available)
Basic Assembler details If an Assembler program fails, and a matching listing is not available, then just formal hexadecimal or Assembler-oriented details will appear on the ASD. Otherwise, failing statement details will appear on the ASD (see Assembler minidisplay on page 100). A typical display that shows basic details for a simple Assembler dump follows. As in the previous examples of ASDs, the ASD for Assembler-type dumps gives access to a number of additional displays through Point and Shoot operations on highlighted fields. These include:
I
Specific abend code diagnostics, including Chicago-Soft QuickRef data if available (see Displaying abend code details on page 75). A detailed Dump Display at the abend address (000066C6), at each operand address (000066CC and 00006FEC), and for each of the addresses displayed in the registers (if the dump itself includes them); see Dump displays on page 129.
CHAPTER 3
99
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display ******************************* Top of Display ******************************** Dump No 478 Job DMABCDEF Step DMSTCS02 was taken on 08/03/99 at 13.51 Program ABCD
Point & shoot . items below to select a display Abend code = S0C7 PSW at time of abend = 078D2000 800066CC
Register contents at time of abend : 0-7 00000020 00000000 00006438 0000642C 00000014 0000647C 009D1FF8 FD000000 8-15 009FDAA0 809FD4E0 00000000 009FD8E8 80006680 04900510 80FD3658 80006680 Failing instruction at 000066C6 is at offset 000003FE in program ABCD Failing instruction is FA7DC04CC96C - AP 0076(08,RC),2412(14,RC)
Operand 1 at 000066CC length 0008 - 000000000012345C Operand 2 at 00006FEC length 000E - 00123456789ABCDEF01234567890 Load module ABCD was linked 08/03/99 Load library DM.ALPHA.TEST.CAPTURE.LOAD accessed via DDname STEPLIB . Linkedit Map Call chain (2 levels) Program Language S0C7 *Unknown type . . . . Last executed statement failed with Abend Code S0C7 at offset 46 address 000066C6 *Unknown type called S0C7 from address 00FD3658 All programs in Call Sequence (derived from R13) Call Sequence / Compiler Info / Registers
I/O Summary Display System Enqueue Information
Similarly, selecting the appropriate Point and Shoot indicator (.) results in presentation of each of the following:
I
Job log information, if it is available (see Capturing and displaying the job log on page 72). A display of captured linkedit information (if the load library can be identified). CA-Panexec support In addition to supporting LINKEDIT information held in an IBM PDS or PDSE dataset, the CA-Panexec format (Computer Associates International, Inc.) is supported. Note that the CA-Panexec API modules should be globally available via the LINKLIST or the LPA.
A list of the programs involved, in call sequence (derived from R13). Information on the call sequence, compiler, registers, and so on. An I/O Summary for all files which were open when failure occurred (see I/O Summary display on page 131). A display of system ENQs and status (see Enqueue list on page 134). Unlike the previous ASD examples (say for COBOL or PL/I), a System View Point and Shoot option is not offered, because this information is entirely included in the ASD presented for Assembler-type environments.
Note
100
CHAPTER 3
Various diagnostic facilities are also available via the pull down menus see Diagnostic facilities on page 156 for details. Assembler mini-display If an Assembler program fails, and the matching listing has been located, then failing statement details will appear on the ASD within an area termed the Assembler mini-display. Otherwise, just formal hexadecimal or Assembleroriented details will appear on the ASD (see Basic Assembler details on page 98). Assembler compilation options For advice on options that are vital to successful automatic dump analysis, see Known restrictions in Assembler support on page 105. An example of the top portion of an ASD that shows an Assembler mini-display follows:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display ******************************* Top of Display ******************************** Dump No 6745 Job GBTSCS4(JOB14080) was taken on 08/11/02 at 13.51 Step Program GLYN
Point & shoot . items below to select a display HLASM R2.0 CSECT TSTASM Abend code = S0C7 failed with Abend Code S0C7
PSW at time of abend = 078D000000006E4A
Register contents at time of abend: 0-7 00000050 00000050 00006E80 00005F50 008DD930 008DBA70 008BCFF8 FD000000 8-15 008DBF88 008DB558 00000000 00006DA4 40006DFE 00006E8C 40006D9A 00000000 The failing statement is at 00006E44 at offset 0000C4 72 74 + CONVERT AP DECIMAL,NOTDEC generated by the macro:
. Failing statement with data . Statement in context Failing instruction is FA73C0DAC0E2 AP 218(8,RC),226(4,RC)
The Assembler mini-display is headed by the line that shows the Assembler compiler and version (HLASM R2.0), and includes:
I
Abend code details. Register contents at time of abend. The failing statement (macro or raw BAL). Point and Shoot items that enable you to view further pertinent data (statement details, referenced data, and so on) to aid in problem analysis:
I
Failing statement with data. Statement in context.

See
For information on
Assembler Failing Statement display Assembler Source Statement display Assembler Selected Statement display
page 101 page 103 page 103
CHAPTER 3
101
Following the Assembler mini-display, basic Assembler information is shown (failing instruction, operands, and so on), and Point and Shoot items are provided to enable you to display other details pertinent to the dump the Linkedit Map, Call Sequence information, an I/O Summary, Joblog Information (see page 72), and so on.
Assembler Failing Statement display
From the Assembler mini-display area of the ASD (see page 100), Point and Shoot on the item Failing statement with data and a display similar to the one shown below will appear:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Failing Statement with Data ******************************* Top of Display ******************************** HLASM R2.0 CSECT TSTASM failed with Abend Code S0C7 Failing Statement 72 73 + 74 + 75 + 76 + CONVERT CVD AP L BALR Address R1,DECIMAL DECIMAL,NOTDEC R15,=A(PRINT) R14,R15 00006E40 00006E44 00006E4A 00006E4E
Register contents at time of abend: 0-7 00000050 00000050 00006E80 00005F50 008DD930 008DBA70 008BCFF8 FD000000 8-15 008DBF88 008DB558 00000000 00006DA4 40006DFE 00006E8C 40006D9A 00000000 . Alter registers and rebuild this display Referenced Data derived from listing 93 DECIMAL DS PL8 Value X'000000000000080C' 94 NOTDEC DC F'4' Value X'00000004' Referenced Data derived from storage Operand 1 length 0008 displacement 218(X'00DA') from R12 Value X'000000000000080C' Address 00006ED8 00006EE0 Address 00006ED8
Operand 2 length 0004 displacement 226(X'00E2') from R12 00006EE0 Value X'00000004' ****************************** Bottom of Display ******************************
This display provides details of the failing Assembler source language statement in the Assembler program.
Notes 1 2 3
If the failing statement is a macro then, unless it has been suppressed with PRINT NOGEN, the expansion of the macro is shown. The data involved is identified from an inspection of the cross-reference information where it refers to any of the failing statements instructions. Point and Shoot on an address for a detailed Dump Display corresponding to the address (see Dump displays on page 129).
The Assembler Failing Statement display is divided into the following sections: Failure description A description of the failure appears at the top of the Assembler Failing Statement display. This description is obtained from the program table created by the call chain analysis.
102
CHAPTER 3
Failing statement This section lists all the instructions in the statement (unless they have been suppressed by a PRINT statement). The address of each instruction is shown alongside; the actual failing instruction is highlighted. Register contents at time of abend Register contents are listed for reference, and for displaying the addressed storage in dump format. Internally, the register contents are obtained initially either using the DUMPMASTER DMREG function or from the associated RSA, whichever is appropriate. The details are stored in a global variable using the DUMPMASTER DMGLOBAL function, for subsequent use with Assembler Selected Statement displays for the particular module. (For detailed descriptions of the DMREG and DMGLOBAL functions, see the DUMPMASTER MVS Technical Reference.)
Altering the register contents
If there are base and displacement type operands (see Referenced Data derived from storage below) then you can alter the register contents used in calculating base addresses for data items:
1 2 3
Point and Shoot on the item Alter register contents and rebuild this display. On the panel that appears, change the register contents as appropriate. Return to the Failing Statement display. The register contents will show your changes, and the data displayed will be based on the changed register contents.
Again, the (altered) register contents are stored in a global variable using the DUMPMASTER DMGLOBAL function, for subsequent use with Assembler Selected Statement displays for the particular module. Referenced data These sections list all the data referenced by instructions in the failing statement, where known: Referenced Data derived from listing Referenced Data derived from storage If the instructions have labels then the data as seen in the listing is reported. The instructions from storage are reported as base and displacement type operands.
If the label addresses are different to the operand addresses then the base register has been corrupted, in which case you can alter the register contents (see above) to experiment with the correct values.
Address calculation
For data items, addresses are calculated by DUMPMASTER as follows:

I
For a data item within a CSECT, the items address is calculated from the address of the CSECT + the offset. If there are no data items (for example, the instruction is an RR-type instruction) then the message No data fields in statement is displayed.
CHAPTER 3
103
Assembler Source Statement display
Point and Shoot on the item Statement in context from the Assembler minidisplay area of the ASD (see page 100), and a display similar to the one shown below will appear; note that you can scroll backwards or forwards through the program listing.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Statement in Context 68 69 70 71 72 77 78 79 82 83 84 85 86 87 88 89 90 91 92 MVC ADDRESS,=CL20'Newhaven, E.Sussex' LA R2,=CL4'Fred' MVC NAME-TEST(L'MYNAME,R3),=CL4'AAAA' LA R1,80 CONVERT <== Macro containing failed stmt DS 0H L R13,4(,R13) RETURN (14,12) DS 0H LTORG =CL4'1234' =C'ABCD' =C'Fred' =CL20'Newhaven, E.Sussex' =CL4'Fred' =CL4'AAAA' =A(PRINT) DC 18F'0' DS 0D
FIN PRINT
SAVAREA
If a statement number is highlighted then you can tab to it and press Enter to display details for the selected statement. For more information, see Assembler Selected Statement display below.
Notes 1 2 3
From a Point and Shoot on another display, the Source display is positioned so that the failing statement appears as the fifth line in the list. Some statement numbers are not selectable these include AMODE, CSECT, DROP, DSECT, END, ENTRY, EQU, LTORG, ORG, RMODE, START, and USING. Some statement numbers are missing conditional assembly, SPACE or EJECT statements, and macro-generated instructions are not shown.
Assembler Selected Statement display
This display, which is very similar to the Assembler Failing Statement display, is invoked from the Assembler Source display (see above) by tabbing to a highlighted statement number and pressing Enter. The format of the Assembler Selected Statement display depends on the type of statement that was selected:
I
Data format display If the selected statement consists of a pure data definition only, then this sort of display will appear. For more information, see Assembler Selected Statement Data display on page 104.
Procedural format display If the selected statement is a machine instruction, or a macro which contains at least one machine instruction, then this sort of display will appear. For more information, see Assembler Selected Statement Procedural display on page 105.
104
CHAPTER 3
Assembler Selected Statement Data display If the selected statement consists of DC, DS, and/or any other pure data definition only, then this sort of display will appear:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Selected Statement Display ******************************* Top of Display ******************************** HLASM R2.0 CSECT TSTASM failed with Abend Code S0C7 Selected Statement 52 TSTASMX DS 0H Address 00006DFE
Register contents at time of abend: 0-7 00000050 00000050 00006E80 00005F50 008DD930 008DBA70 008BCFF8 FD000000 8-15 008DBF88 008DB558 00000000 00006DA4 40006DFE 00006E8C 40006D9A 00000000 Referenced Data derived from listing 52 TSTASMX DS 0H Value X'18BD' Address 00006DFE
Address Referenced Data derived from storage No data fields in statement ****************************** Bottom of Display ******************************
An Assembler Selected Statement Data display reports:

I
The selected statement. The register contents, together with the Point and Shoot item Alter register contents and rebuild this display. For more information, see Register contents at time of abend on page 102. The referenced data items (but not any embedded comments), handled in the order in which they appear in the program listing. See also:
I
Referenced data on page 102 Specifying a DSECT base address on page 104.
Specifying a DSECT base address
The first time a DSECT field is displayed, the DSECT base register is unknown. Consequently, an entry to that effect will appear on the Assembler Selected Statement display, the Address field will show the field offset within the DSECT, and you will be prompted for the base register to use:
Referenced Data derived from listing 103 MYFIELD DS A *** Field is in DSECT TEST - base register not known *** Specify base register to use Rxx Address 00000000
To specify a valid register name, use the Rxx field and press Enter. Internally, the register name is stored in a global variable using the DUMPMASTER DMGLOBAL function, for any further reference to fields in the DSECT. (For a detailed description of the DMGLOBAL function, see the DUMPMASTER MVS Technical Reference.) After the base register has been specified, the Address field will reflect the true storage address, and any references to fields within the particular DSECT will use the contents of the specified register to calculate the storage address and contents:
Referenced Data derived from listing 103 MYFIELD DS A Value C'ABCD' DSECT TEST using base register Address 00005F50 R3
CHAPTER 3
105
Note
Changes to the contents of the specified register will alter the values displayed for the particular DSECT.
Assembler Selected Statement Procedural display If the selected statement was a machine instruction, or a macro which contains at least one machine instruction, then an Assembler Selected Statement Procedural display will appear. The format of this sort of display is similar to an Assembler Selected Statement Data display (see page 104). In contrast, for a macro, the expansion of the macro is shown:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Selected Statement Display ******************************* Top of Display ******************************** HLASM R2.0 CSECT TSTASM failed with Abend Code S0C7 Selected 59 61 62 63 Statement + + + GETMAIN R,LV=80 LA 0,80(0,0) BAL 1,*+4 SVC 10 Address 00006E14 00006E18 00006E1C
Register contents at time of abend: 0-7 00000050 00000050 00006E80 00005F50 008DD930 008DBA70 008BCFF8 FD000000 8-15 008DBF88 008DB558 00000000 00006DA4 40006DFE 00006E8C 40006D9A 00000000 Address Referenced Data derived from storage No data fields in statement ****************************** Bottom of Display ******************************
Known restrictions in Assembler support
The DUMPMASTER Assembler Listing analysis feature has a restricted capability under certain circumstances. The restrictions all concern the display of certain types of data, and generally are the result of data omitted or suppressed in the Assembler compiler listing. For guidance on Assembler compilation options that are vital to successful automatic dump analysis, see Compilation options required in the chapter Program compilation listings capture in the DUMPMASTER MVS Technical Reference.
ASDs for DB2 and IMS

For DB2 and IMS, the ASD includes information similar to the COBOL display in ASD for COBOL on page 73, but pertinent to those environments.
Abend Summary Display for DB2 DB2 Bind Information DB2 Formatted Host Variables Abend Summary Display for IMS Capturing and displaying the job log
below page 106 page 109 page 110 page 72
Abend Summary Display for DB2
The Point and Shoot item DB2 Summary may be selected from the ASD if the dump selected contains evidence of DB2 activity. Such activity will have occurred in the failing program (if Batch) or failing transaction (if CICS).
106
CHAPTER 3
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------DB2 Summary ****************************** Start of display ******************************* DB2 Subsystem DSN1 DB2 Release 5.10
The last SQL statement executed was an EXEC SQL INSERT , precompiler sequence number 187 for plan DMDB2DEM in Cobol/370 program DMDB2DEM . The statement completed with return code -204 and state code 42704 . . . . . . . . . EXEC SQL statement in program DMDB2DEM DB2 Bind Information Explanation of SQLCODE -204 Analysis of SQLCODE -204 (using DSNTIAR if accessible) Formatted Host Variables Formatted RDI (RDS input parameter list) at 86136A70 Formatted SQLCA (SQL communications area) at 061360D0 Scan dump for other RDIs referring to SQLCA
State code 42704 means An undefined object or constraint name was detected. ******************************* End of display ******************************** Command ===> Scroll ===> CSR
This display offers options to view formatted displays of significant DB2 blocks, if such have been located. Two blocks critical to the DUMPMASTER analysis are:
I
Formatted RDI (RDS input parameter list) Associated with the SQL statement (as generated by the SQL pre-compiler in COBOL programs). Formatted SQLCA (SQL communications area) Conveys the result of the last operation.
Other options include:

I
SQL statement and associated data. Return and state codes. DB2 Bind Information (see below). Formatted Host Variables (see page 109).
RDIs referring to SQLCA (with information on each RDI).
DB2 Bind Information
During a Bind process, output from the DB2 precompiler (the DBRMs) for an application is converted to a usable control structure called a Package or an application Plan, which is used by DB2 to process SQL statements when the application is run. During the Bind process, access paths to the data are selected and some authorization checking is performed. At dump capture time, program DMBDB202 (see the DUMPMASTER MVS Installation Guide) is called by the DUMPMASTER subsystem to retrieve the relevant data from the following DB2 tables:
SYSIBM.SYSPLAN SYSIBM.SYSPLANAUTH SYSIBM.SYSPLANDEP SYSIBM.SYSDPRM SYSIBM.SYSPACKAGE Note SYSIBM.SYSPACKAUTH SYSIBM.SYSPACKDEP
See the IBM manual DB/2 For MVS/ESA V4 SQL Reference for descriptions of the fields associated with these tables.
CHAPTER 3
107
To display the data that DUMPMASTER retrieved from the DB2 tables, select the Point and Shoot item DB2 Bind Information from the DB2 Summary display.
DB2 Plan display DB2 Package display DB2 Plan display
below page 108
An extract from such a display appears below:

Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------DB2 Plan DSN8CC0 **************************** Start of Plan Display **************************** Point & shoot . items below for more information Plan Plan name Owner authorization ID Authorization ID of binder Implicit qualifier Last bind date Last bind time Valid plan Operative Validity check time Isolation level for plan Plan Size Average Size Cache size Resource acquire time Resource release time Explain option CURRENTDATA option at bind Defer prepare option Current server location name Degree option SQL rules option Disconnect Option Package list entries SYSPLSYSTEM entries IBM Required Plan Package Names . DSN8CC0 . DSN8CC1 . DSN8CC2 Plan Authority Grantor Grantee Name Date Granted Time Granted AUTHHOWGOT Bind Authority IBMUSER IBMUSER DSN8CC0 96/12/09 10:17:37:73 Not applicable Privilege held with GRANT option DSN8CC0 IBMUSER IBMUSER IBMUSER 97/02/10 10:37:12:52 Yes Yes Run Cursor stability 2040 0 1024 First use Commit No Allow blocking for ambiguous cursors No 1 DB2 Explicit disconnect 1 0 V2R3 dependency
From the DB2 Plan Display, Point and Shoot on the indicator (.) adjacent to a particular Plan Package Name to display details of the Package.
108
CHAPTER 3
DB2 Package display An extract from this type of display appears in the following figure:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------DB2 Package DSN8CC0 *************************** Start of Package Display *************************** Point & shoot . items below for more information Plan Name . DSN8CC0 Package Package name Collection ID Consistency token Location Owner authorization ID Creator authorization ID Implicit qualifier Create time stamp Bind time stamp Valid Valid Operative Package size Average size Validity check time Isolation level for package Resource release time Explain option SQL delimiter Decimal point representation Host Language Precompile character set Precompile mixed data Precompile DEC31 CURRENTDATA option at bind SQL error Package source Precompile Time Stamp VERSION PDS name Degree option SYSPKSYSTEM entries IBM required Package Authority Grantor Grantee Location Collection ID Package name Time Stamp Grantee Type AUTHHOWGOT DSN8CC0 DSN8CC31 X'15C665B31F8E15FE' IBMUSER IBMUSER IBMUSER 1996-12-09-10.17.06.786054 1997-02-10-10.36.34.538956 Yes Yes Yes 1120 1012 Run Cursor stability Not specified No Apostrophe Period OS/VS Cobol Other than Katakana No No No data currency required for ambiguous cursors. No package Locally bound from a DBRM 1997-02-10-09.55.12.292951 DB2.DBRMLIB.DATA 1 0 V2R1 dependency IBMUSER IBMUSER DSN8CC31 DSN8CC0 1996-12-09-10.17.06.786054 Authorization ID Not applicable
CHAPTER 3
109
DB2 Formatted Host Variables
To display the DUMPMASTER Host Variables screen, select the Point and Shoot item Formatted Host Variables from the DB2 Summary display. Prior to DUMPMASTER V5.310
I
If a program had been pre-compiled with DB2 V6 or higher then Point and Shoot items appeared on the Host Variables screen which enabled you to display variables associated with either the INPUT or OUTPUT SQLDA (SQL Descriptor Area). Here is a portion of a formatted INPUT SQLDA display:
Level, Name & Definition Content, Description & Comments 01 SQLDA. RDS SQL Descriptor Area 02 SQLDAID PIC X(8) 'SQLDA ' Eye catcher VALUE 'SQLDA'. 02 SQLDABC PIC S9(9) 984 Block length BINARY. 02 SQLN PIC 999 BINARY. 22 Expected SQLVAR occurrences 02 SQLD PIC 999 BINARY. 22 Actual SQLVAR occurrences 02 SQLVAR (1) OCCURS DEPENDING ON SQLN. Address 08271618 08271618 08271620 08271624 08271626 08271628
If a program had been pre-compiled with DB2 V5 or lower then the static host variables were shown in a user-friendly format on the Host Variables screen.
DUMPMASTER V5.310 and higher

I
If a program has been pre-compiled with DB2 V6 or higher then the Host Variables screen still contains Point and Shoot items that enable you to display a formatted INPUT or OUTPUT SQLDA (see above). Regardless of the version of DB2 used to pre-compile a program, both static and dynamic host variables are shown in a user-friendly format on the Host Variables screen:
Navigation Setup Listings Advanced Traces Help ----------------------------------------------------------------------------SQL Host Variables ****************************** Start of display ****************************** The following variables are associated with the EXEC SQL SELECT precompiler sequence number 601 for plan DMBPLAN whose RDI is at address 882715F0 Variable INPUT 1 2 3 4 5 Type & Value Fixed Length 'SYSIBM ' Fixed Length 'SYSTABLES Fixed Length 'T' Fixed Length 'DSNDB06 ' Fixed Length 'SYSDBASE' CHARACTER(8) CHARACTER(18) ' CHARACTER(1) CHARACTER(8) CHARACTER(8) Address 08270494 08270704 0827049C 0827049D 082704A5
For a longer-length variable, the view is extended to show the full length of the variable (254 characters in this case):
19 Fixed Length CHARACTER(254) 'BEWARE THE JABBERWOCK ' ' ' ' ' ' ' ' 08270734
'
110
CHAPTER 3
Abend Summary Display for IMS
If the abending program contains evidence that IMS was active then the ASD, and subsequent more detailed diagnostic displays, will contain information pertinent to this environment. This information can include the call status description, the last call to IMS, the AIB map, system search arguments used by the last call, a list of database PCBs with the details of each PCB, the terminal PCB list, AIB/UIB return and reason codes, and so on. Of particular relevance is the Point and Shoot item IMS MPP region diagnosis. On this display, headings contain the IMS release, the IMS region type, the application program name, and the calling parameter format if a call to IMS has been made.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------IMS Diagnostics Menu IMS Release 6.10 Region Type MPP Application Program Name CLAH1INQ Calling parameter format Cobol
Point & shoot . items below to select a display . . . . . . . . . . . MVS system abend S0C9 PCB status code "GE" Last (GU) call to IMS Current Database PCB I/O area storage System Search Arguments(SSAs) Parameter list storage All Database PCBs Terminal PCBs IMS parameter block module DFSPRPX0 IMS online environment block DFSECP
******************************* End of display ******************************** Command ===> Scroll ===> CSR
Access to a structured series of IMS-specific dynamic displays is available via the IMS Diagnostics Menu, for example:
I
PCB status code Displays the status code together with an explanation of the status of the main IMS program control block. Last call to IMS Shows details of the last program call to IMS along with an explanation of what type of call was made.
Also, on the IMS Database PCB screen, there is special formatting for all information derived from JCB trace entries.
CHAPTER 3
111
ASD for Language Environment (LE)

For a dump in which IBMs LE is detected, the ASD reports briefly on the LE status (condition codes, and so on). The top portion of a typical ASD for a simple PL/I dump in which the LE environment is detected is shown in the next figure:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display ******************************* Top of Display ******************************** Dump No 3156 Job NWHPLILE(JOB27286) was taken on 08/11/02 at 13.51 Step GO Program PLILE1
Point & shoot . items below to select a display PL/I Procedure PLILE2 failed with PL/I OnCode 320 Failed at address: 06C22C54 , offset 3CC from entrypoint. . Description of ONCODE 320 . Display failing PL/I statement EP : 06C22888 Static Storage : 06C22C88 Length : 340 DSA : 0005E860 Automatic Storage : 0005E8D8 Length : 200 TCA : 00057068 TCA Appendage (TIA) : 0007E030 Compiled : 17 DEC 01 11:47:39 . . Complete PL/I procedure chain - 6 levels System View (failing instruction & operands)
OS/390 Language Environment V1 R8 . Language Environment Summary . Current condition code is IBM0281S A prior condition was promoted to the ERROR condition. . Initial condition code is CEE3211S The system detected a decimal-divide exception. Command ===> Scroll ===> CSR
Note
In the LE section, Current/Initial condition code is accompanied by the description of the code from LE services; Point and Shoot on a condition code to display the full Chicago-Soft QuickRef description if it is available.
From the ASD, Point and Shoot on the item Language Environment Summary to display a screen containing further information pertaining to LE:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Language Environment Summary ********************************* Top of Data ********************************* Information for OS/390 Language Environment V1 R8 Current and initial Condition Codes: . Current: IBM0281S A prior condition was promoted to the ERROR condition. . Initial: CEE3211S The system detected a decimal-divide exception. . . Runtime Options in effect Stack and Heap storage information Language Environment Control Block Information . . . . . Acronym CAA CCIB DDSA EDB PCB OCB Description Anchor Block Current Condition Information Block Dummy DSA Enclave data Block Process Control Block Options Control Block Address 00057068 0005C478 00057900 00056008 00014558 00056658
From the Language Environment Summary screen, you can quickly navigate to more detailed data by further Point and Shoot operations. For example:
112
CHAPTER 3
Point and Shoot on Current/Initial Condition Code to display the full Chicago-Soft QuickRef description if it is available. The current condition code may be less important than the initial condition code (the current condition will have arisen as a consequence of the initial condition). Select the Point and Shoot item Runtime Options in effect to display the LE options in use and where they came from (that is, Installation default, Programmer default, and so on). Point and Shoot on a particular control block to view a formatted display of the block. The format of each of these displays is similar to the Common System Area display (see page 94). (COBOL only.) Select the Point and Shoot item COBOL programs in LE storage to access the Programs in CLLE Chain display, which lists all loaded COBOL programs. Here is an example of this display:
Navigation Setup Listings Advanced Traces Help ---------------------------------------------------------------------------COBOL Programs in CLLE Chain ********************************* Top of Data ******************************* Most Recently Compiled Programs Cobol/390 Cobol/390 Cobol/390 Cobol/390 Cobol/390 program program program program program CALLED5 CALLED6 CALLED7 CALLED8 CALLER compiled: compiled: compiled: compiled: compiled: 23/10/02 23/10/02 23/10/02 23/10/02 23/10/02 10:31:18 10:31:04 10:30:42 10:30:26 10:15:45 (16 (16 (16 (16 (16 days days days days days ago) ago) ago) ago) ago)
Active and Inactive COBOL Programs CALLED8 Compiled on 23/10/02 10:30:26 Compiler: Cobol/390 TGT: 06C13518 Program Start: 06C24778 CLLE: 000464D0 Working Storage: 06C162D8 Length: 25 . Base Locators CALLED7 Compiled on 23/10/02 10:30:42 Compiler: Cobol/390 TGT: 06C132D8 Program Start: 06C229D8 CLLE: 00046488 Working Storage: 06C16250 Length: 25 . Base Locators CALLED6 Compiled on 23/10/02 10:31:04 Compiler: Cobol/390 TGT: 06C13098 Program Start: 06C20C38 CLLE: 00046440 Working Storage: 06C161C8 Length: 25 . Base Locators CALLED5 Compiled on 23/10/02 10:31:18 Compiler: Cobol/390 TGT: 06C12E58 Program Start: 06C1EE80 CLLE: 00046370 Working Storage: 06C16140 Length: 25 . Base Locators CALLER Compiled on 23/10/02 10:15:45 Compiler: Cobol/390 TGT: 06C12078 Program Start: 06B001B0 CLLE: 00046328 Working Storage: 06C16088 Length: 70 . Base Locators ******************************* Bottom of Data ******************************* Command ===> Scroll ===> CSR
To build this display, information is first gathered for the three programs that have been compiled most recently. Information is then gathered for the other programs only if they have been compiled during the last 30 days. Displaying BLL cells BLL cells are used to address storage outside the Working Storage section of COBOL application programs. To display BLL cells for programs in LE storage, Point and Shoot on a particular Base Locators item on the COBOL Programs in CLLE Chain display. Here is an example of the data displayed:
CHAPTER 3
113
Navigation Setup Listings Advanced Traces Help ---------------------------------------------------------------------------CALLED8 Base Locators & Indexes ****************************** Start of display ***************************** Cobol program CALLED8 was located in LE storage No files were defined Working Storage BLW=0000 06C162D8 7FC3C1D3D3C5C4F87F40A69699928995 * "CALLED8" workin * Linkage Section BLL=0001 06C16250 7FC3C1D3D3C5C4F77F40A69699928995 * "CALLED7" workin * No indexes were defined No variably located areas were defined No EXTERNAL data was defined ******************************* End of display ****************************** Command ===> Scroll ===> CSR
ASD for WebSphere MQSeries

If the abending program contains evidence that IBMs WebSphere MQSeries was active then the ASD, and subsequent more detailed diagnostic displays, will contain information pertinent to this environment. The bottom portion of a typical ASD for an Assembler dump in which the WebSphere MQSeries environment was detected appears in the next figure, and shows the type of the last MQSeries call made:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Abend Summary Display Call chain (Top 1 user levels in chain of 1) Last executed statement Program Language MQTST3D HL Asmblr failed with Abend Code S0C1 at address 00006562 MQTST3D + X'202' . User programs in Call Sequence (derived from R13) . Call Sequence / Compiler Info / Registers . I/O Summary
The last WebSphere MQSeries call was 'MQPUT1' The call completed successfully. . MQSeries call detail . Display System Enqueue Information
**************************** Bottom of Display ******************************** Command ===> Scroll ===> CSR
Note
If the MQSeries call had failed then the Condition Code and Reason Code would also be shown on the ASD.
See
For information on
Last MQSeries call detail Information for MQINQ and MQSET calls Information for CICS system dumps
114
CHAPTER 3
Last MQSeries call detail
From the ASD, Point and Shoot on the item MQSeries call detail to display a screen that shows a reconstruction of the last MQSeries call (MQPUT1 in this example) executed by the failing program:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------MQPUT1 Call A reconstruction of the last MQ call executed by the failing program follows: CALL MQPUT1( Hconn ObjectDesc MsgDesc PutMsgOpts BufferLength Buffer Address CompCode = = = = = = = = Reason = = '08204D60' . 00005B6C . 00005CBC . 00005E00 '00000050' + 00005E88 '0' MQCC_OK '0' MQRC_NONE MQ MQ MQ MQ MQ MQ MQ Connection handle Object Descriptor (MQOD) Formatted Message Descriptor (MQMD) Formatted Put Message Options (MQPMO) Message buffer length in hex Message buffer address Completion Code in decimal
MQ Reason Code in decimal Scroll ===> CSR
) Command ===>
This display shows field values and structures used, an interpretation of MQSeries Completion, and Reason codes, and Point and Shoot items that enable you to access formatted displays of MQSeries structures and message buffer contents.
Note
For MQINQ and MQSET calls, additional data formatting and interpretation is provided. See Information for MQINQ and MQSET calls on page 115. For an MQDISC call (Batch or CICS) or an MQCONN call (CICS), no information is provided (the MQSeries footprint disappears when these calls are processed).
Last MQSeries call value entries Three types of value entry may appear on the Last MQSeries Call display:
1
A value, which is not highlighted and is enclosed in apostrophes ('). You cannot Point and Shoot on such an entry (for example, the message Buffer length '00000050' in the figure above), which represents actual data.
An address, which is highlighted and prefixed by a . (period) sign. Point and Shoot on such an entry (for example, . 00005B6C in the figure above) to view a formatted display of the MQSeries structure. The format of these displays is similar to the Common System Area display (see page 94).
An address, which is highlighted and prefixed by a + (plus) sign. The + indicates that the length of the data is longer than the maximum display length. Point and Shoot on such an entry (for example, + 00005E88 in the figure above) for a partial Dump Display, which presents the data as unformatted fields. This display is similar to a detailed Dump Display (see page 129), but the view of the storage is restricted to the length of the data:
Navigation Setup Listings Advanced Traces Help ----------------------------------------------------------------------------MQ Message Buffer Address Offset 00005E88 00000000 C68999A2 A3409985 83969984 40404040 *First record * 00005E98 00000010 40404040 40404040 40404040 40404040 * * 00005EA8 00000020 40404040 40404040 40404040 40404040 * * 00005EB8 00000030 40404040 40404040 40404040 40404040 * * 00005EC8 00000040 40404040 40404040 F0F0F0F0 F0F1F0F0 * 00000100* Command ===> Scroll ===> CSR
CHAPTER 3
115
Note
Certain fields, such as CompCode and Reason code, have numeric values which have specific meanings. These are also displayed in text form:
CompCode = = Reason = = '0' MQCC_OK '0' MQRC_NONE MQ Completion Code in decimal MQ Reason Code in decimal
Information for MQINQ and MQSET calls
For MQINQ and MQSET calls, additional data formatting and interpretation is provided. Suppose that the last call was MQINQ:
Navigation Setup Listings Advanced Traces Help ----------------------------------------------------------------------------MQINQ Call A reconstruction of the last MQ call executed by the failing program follows: CALL MQINQ( Hconn Hobj SelectorCount Selectors IntAttrCount IntAttrs CharAttrLeng CharAttrs CompCode = = = = = = = = = = Reason = = '08204D60' '00000001' '00000005' + 00005E9C '00000002' . 00005E9C '00000044' . 00005EC0 '0' MQCC_OK '0' MQRC_NONE MQ MQ MQ MQ MQ MQ MQ MQ MQ Connection handle Object handle Selector count Selector address Integer attributes count in hex Integer attributes Character attribute length in hex Character attributes Completion Code in decimal
MQ Reason Code in decimal Scroll ===> CSR
) Command ===>
Point and Shoot on the IntAttrs entry to view the MQSeries Integer attributes:
Navigation Setup Listings Advanced Traces Help ----------------------------------------------------------------------------MQ Attribute Display MQSeries Integer attributes: SelectorMeaning Selector X'0003',0003 MQIA_CURRENT_Q_DEPTH X'0014',0020 MQIA_Q_TYPE Command ===> Attribute IntegerAttributeMeaning 58 Count 00000001 = MQQT_LOCAL Scroll ===> CSR
Similarly, Point and Shoot on the CharAttrs entry to view the MQSeries Character attributes:
Navigation Setup Listings Advanced Traces Help ----------------------------------------------------------------------------MQ Attribute Display MQSeries Character attributes: Selector X'07E0',2016 X'07EB',2027 X'07EC',2028 Command ===> SelectorMeaning MQCA_Q_NAME MQCA_ALTERATION_DATE MQCA_ALTERATION_TIME CharacterAttribute RJM1.QUEUE01 2002-01-09 13.26.30 Scroll ===> CSR
Information for CICS system dumps
For a CICS system dump, several Point and Shoot items pertaining to the WebSphere MQSeries environment may appear on the ASD:
The last Websphere MQSeries call issued by failing task 00053 was 'MQOPEN' The call completed successfully. . MQSeries call detail Details of other tasks in the dump that have accessed Websphere MQSeries . List of tasks
116
CHAPTER 3
MQSeries call detail If the failing task accessed WebSphere MQSeries facilities then this Point and Shoot item will appear on the ASD. Select this item to display a screen that shows a reconstruction of the last MQSeries call executed (see page 114). List of tasks At the time of the abend, if active tasks other than the one that failed were using MQSeries facilities then this Point and Shoot item will appear on the ASD. Tasks that completed before the dump was taken will not be included in the list. Select this item and the resulting display enables you to see whether or not the MQSeries calls associated with these tasks completed successfully:
Navigation Setup Listings Advanced Traces Help ---------------------------------------------------------------------------MQSeries Task List ********************************* Top of Data ******************************* . . . . . . Trans id TRNS , Task id 00051 , the last MQ call was 'MQPUT' The call completed successfully. Trans id TRNS , Task id 00049 , the last MQ call was 'MQCLOSE' The call completed successfully. Trans id TRNS , Task id 00047 , the last MQ call was 'MQCLOSE' The call completed successfully. Trans id TRNS , Task id 00046 , the last MQ call was 'MQCLOSE' The call completed successfully. Trans id TRNS , Task id 00045 , the last MQ call was 'MQPUT' The call completed successfully. Trans id TRNR , Task id 00042 , the last MQ call was 'MQGET' The call completed successfully.
******************************** Bottom of Data *****************************
If any of the MQSeries calls in the list had failed then the corresponding Condition Code, Reason Code, and their text form would also be shown. You can Point and Shoot on an item in the list to display a screen that shows a reconstruction of the particular MQSeries call (see page 114).
CHAPTER 3
System View display
117
System View display

This brief, formal hexadecimal or Assembler-oriented display is available from each Abend Summary Display for COBOL, PL/I, IMS, DB2, and so on, as a Point and Shoot option. (The information presented already is included in all Assemblertype ASDs.) The display also is available from most other appropriate DUMPMASTER displays by entering the command INFO ASM. The user may return to the high-level process-oriented Abend Summary Display by entering the command INFO, that is the INFO command without the ASM parameter (see INFO on page 179).
Note
The System View display also has an action bar for Navigation, Setup, Listings, Advanced, and so on. From the appropriate pull down menu (see page 52), access to further displays (for example the Current Display List, Note Lists, Macro 4 Diagnostics, and Help) is available.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------System View of Failure ******************************* Top of Display ******************************** Abend code = S0C7 PSW at time of abend = 078D2000 800066CC
Register contents at time of abend : 0-7 00000020 00000000 00006438 0000642C 00000014 0000647C 009D1FF8 FD000000 8-15 009FDAA0 809FD4E0 00000000 009FD8E8 80006680 04900510 80FD3658 80006680 Failing instruction at 000066C6 is at offset 000003FE in program ABCD Failing instruction is FA7DC04CC96C - AP0076(08,RC),2412(14,RC) Operand 1 at 000066CC length 0008 - 000000000012345C Operand 2 at 00006FEC length 000E - 00123456789ABCDEF01234567890 ****************************** Bottom of Display ****************************** Command ===> Scroll ===> CSR
As with the Assembler-type ASD, the System View display gives access to a number of displays through Point and Shoot operations on highlighted fields. These include:
I
Specific abend code diagnostics, including Chicago-Soft QuickRef data if available (see Displaying abend code details on page 75). A detailed Dump Display at the abend address (000066C6), at each operand address (000066CC and 00006FEC), and for each of the addresses displayed in the registers (if, of course, the dump itself includes them); see Dump displays on page 129.
118
CHAPTER 3
CICS Trace Table displays

Note
DUMPMASTER V4.9 and higher supports only CICS/ESA 4.1 or higher, which includes any release of CICS TS.
The following types of CICS trace display are available:

I
Application Level Trace System Level Trace Full Trace Entry } }
This display provides a high-level view of the trace entries These displays provide a low-level view of the trace entries.
For information on
See
CICS Application Level Trace display CICS System Level Trace display CICS Full Trace Entry display
CICS Application Level Trace display

The CICS Application Level Trace display provides a high-level view of the trace entries, which will be of particular benefit to an Applications Programmer. See:
I
Ensuring that CICS trace entries are available below. Accessing the CICS Application Level Trace display on page 119.
Ensuring that CICS trace entries are available To ensure that relevant CICS trace entries are available, ask your CICS System Administrator to carry out the steps described in this section.
CAUTION The IBM CICS System Definition Guide should be consulted before any
changes are made to the CICS parameters described below.

1
When a transaction dump is taken by CICS/ESA 4.1 or higher, the internal trace table is copied to a transaction dump trace table. It is the latter trace table that is formatted into the resulting dump. To prevent DUMPMASTER from showing irrelevant information, we recommend that you restrict the contents of this trace table to application trace entries pertinent to the failing task by specifying the CICS override (or SIT) parameter TRTRANTY=TRAN. Verify that the CICS override (or SIT) parameter INTTR=OFF has not been used to turn off internal tracing. The default value for this parameter is INTTR=ON. Check that sufficient space is available in the CICS internal trace table to cope with trace entries from the concurrent workload without wrapping. The size of this trace table is specified using the CICS override (or SIT) parameter TRTABSZ. The storage to hold this trace table is allocated from CICS EDSA and its size needs to be determined locally by estimation and experience. The parameter EDSALIM may also need to be adjusted to accommodate any increase in the value of TRTABSZ.
CHAPTER 3
119
Check that sufficient space is available in the CICS transaction dump trace table to hold trace entries for any particular failing transaction. The size of this table is specified using the CICS override (or SIT) parameter TRTRANSZ. When a transaction fails, the storage to hold this trace table is allocated from MVS storage above the 16Mb line and its size needs to be determined locally by estimation and experience.
Note
If the size of the CICS transaction dump trace table is increased then this will result in more data for DUMPMASTER to process. Consequently, transaction dumps will occupy more space in the dump file, and the time taken to access application trace entries will increase.
Accessing the CICS Application Level Trace display This display may be accessed by using one of the following methods:
I
Using Point and Shoot on the item Display CICS Trace entries on a CICS Summary display (see page 91). Selecting option 1 (= Display CICS Application Level Trace) from the Traces pull down menu (see page 54). Selecting the TRACE option from the CICS Dump Menu (see Dump Menu (DMENU) displays on page 126). Issuing the TRACE command (see TRACE on page 181).
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------CICS Application Level Trace
***************************** Start of Trace Table ***************************** Display of 'Trace Entries' from the most recent, to the oldest. Point & shoot . items below to resolve an entry to a statement in the compile listing, or to the link edit information. Program Name DMCDEM31 DMCDEM31 DMCDEM31 DMCDEM31 DMCDEMO DMCDEMO Return Address 05201C6C 05201A86 05201A4E 052018D8 05201558 052014CE Return Offset 00046C 000286 00024E 0000D8 000158 0000CE Function/Response GETMAIN(LENGERR) LENGTH(0) GETMAIN(OK) LENGTH(80) ADDRESS( 00200738 ) GETMAIN(OK) LENGTH(400) ADDRESS( 05000278 ) RECEIVE-TC(EOC) XCTL PROGRAM( DMCDEM31 ) COMMAREA( 002003E8 ) INQUIRE-SYSTEM(OK)
. . . .
****************************** End of Trace Table ****************************** Command ===> Scroll ===> CSR
Each individual entry on this screen is actually a composite it is built from related
EIP ENTRY and EXIT trace entries that are associated with a request for CICS
services (that is CICS EXEC interface calls). Point and Shoot items marked with . to resolve an entry to a statement in the compile listing, or to the link edit information. Also, Program Name and Return Address are unprotected and may be used as Point and Shoot targets position the cursor on one of these fields and press Enter to display the SUMMARY Notes or the dump at that address respectively.
120
CHAPTER 3
CICS System Level Trace display

The CICS System Level Trace display provides a low-level summary view of the trace entries, which is of particular benefit to a Systems Programmer. This display may be accessed by selecting option 2 (= Display CICS System Level Trace) from the Traces pull down menu (see page 54).
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------CICS System Level Trace ***************************** Start of Trace Table ***************************** Display of 'Trace Entries' from the most recent, to the oldest. Point & shoot . items below to select a trace entry detail display. Task . . . . . . . . . . . . . 00285 00285 00285 00285 00285 00285 00285 00285 00285 TCB Domain 1 1 1 1 1 1 1 1 1 KE KE LM LM DU LM LM DU GC 0202 0201 0004 0003 0501 0004 0003 0601 2050 Progm Type KEDD KEDD LMLM LMLM DUDT LMLM LMLM DUTM CCCC EXIT ENTRY EXIT ENTRY EXIT EXIT ENTRY EXIT EXIT Function
00285 1 00285 1 00285 1 00285 1
DS 0005 DSSR DS 0004 DSSR GC 2010 CCCC DU 0600 DUTM
Command ===>
INQUIRE_ANCHOR/OK 04AFA638 INQUIRE_ANCHOR 0000000B LOCK/OK LOCK 04B1DDE8,EXCLUSIVE,CICS SET_TRAN_DUMPCODE/OK UNLOCK/OK UNLOCK 04B1DE18,EXCLUSIVE SET_TRAN_DUMPCODE/OK GET_UPDATE/EXCEPTION RECORD_NOT_FOUND,00000001 EXIT WAIT_MVS/OK ENTRY WAIT_MVS ASYNRESP,CCVSAMWT,04BE15C0,NO,IO ENTRY GET_UPDATE 04F13072 , 00000000 , 00000009,TRANSACT,AEIV ENTRY SET_TRAN_DUMPCODE AEIV,FFFFFFFF,NO,YES,NO,LOCAL Scroll ===> CSR
For information on
See
Fields on System Level Trace display Changing filters
page 121
The CICS System Trace Filters screen enables you to change filters and (re-)display the System Level Trace display see CICS System Trace Filters screen on page 123. Full Trace display To obtain a Full Trace display for an entry on the CICS System Level Trace display you can either:
I
Point and Shoot on the . marker adjacent to the entry. Enter an S action code against the entry.
For more information, see CICS Full Trace Entry display on page 124.
CHAPTER 3
121
Fields on System The entries on this display are described briefly below; for more information please refer to the following IBM manuals: Level Trace display CICS/ESA Users Handbook.
I I
CICS/ESA Problem Determination Guide.
Task The task number, which is used to identify a task uniquely for as long as it is in the system. It provides a simple way of locating trace entries associated with specific tasks, as follows:
I
A five-digit decimal number shows that this is a trace entry for a task with a TCA, the value being taken from field TCAKCTTA of the TCA. A three-character non-numeric value in this field shows that the trace entry is for a system task. You could, for example, see III (initialization), or TCP (terminal control). A two-character domain index in this field shows that the trace entry is for a task without a TCA. The index identifies the domain that attached the task.
TCB The TCB Index from the Abbreviated Trace display. Abbreviated trace entries show a TCB Index instead of an MVS TCB address. The TCB Index has a value of 1, 2, 3, 4, or 5 and it indicates when CICS task execution switches from one MVS TCB (see below) to another:
I
The quasi-reentrant mode (QR) TCB The resource-owning mode (RO) TCB The file-owning mode (FO) TCB The concurrent mode (CO) TCB (if SUBTSKS=1 is specified) The FEPI (SZ) TCB (if FEPI=YES is specified)
Notes
a
The first abbreviated trace entry always has a value of 1 for the TCB Index. When execution switches to another TCB, the value is shown as 2. When execution switches again, the value shown is either 1 if the previous TCB is used, or 3, 4, or 5 if any of the remaining TCBs are used. A value of 3, 4, or 5 for the TCB Index appears only when certain optional functions are used, which are concurrent mode (SUBTSKS=1 in the system initialization table or start-up overrides), FEPI, or ONC RPC. There is no absolute correlation between the type of MVS TCB (quasireentrant, resource owning, concurrent, FEPI, or ONC RPC) and the value of the TCB Index. A value of 1 is always shown for the TCB that happens to be in use when the first trace entry is made.
Domain The trace point ID. This is an identifier that indicates where the trace point is in the CICS code. In the case of the Application Domain (AP), the request type field included in the entry is also needed to uniquely identify the trace point. For all other domains, each trace point has a unique trace point ID.
122
CHAPTER 3
The format of this field is always a two-character domain index, that shows which domain the trace point is in, then a space, then a four-digit (two-byte) hexadecimal number which identifies the trace point within the domain. The following are examples of trace point IDs: AP 00EE DS 0005 TI 0101 Progm This is the name of the CICS program, with the DFH prefix removed, that produced the trace entry. For example, DUDT is program DFHDUDT; SMMG is program DFHSMMG. Type Values that may appear in this field: ENTRY EXIT *EXC* indicates that the trace is written on entry to the function. indicates that the trace is written on exit from the function. indicates an exception trace entry, that is a trace entry written by CICS system recovery to record first failure data when an unexpected event occurs such as a program check. indicates a trace entry other than one of those listed above. trace point X'00EE' in Application Domain. trace point X'0005' in Dispatcher Domain. trace point X'0101' in Timer Domain.
EVENT Function
This provides an interpretation of the parameters passed to/returned from the function call. For example, suppose a CICS System Level Trace entry has the following values in the Progm, Type, and Function fields:
Progm Type SMMG Function
ENTRY GETMAIN 1A4A,YES,00,TASK
This information tells you that:

I
The trace call was made from within module DFHSMMG. The call was made on entry to the GETMAIN function. The parameters associated with the GETMAIN call are as follows: The request is for X'1A4A' bytes of storage. The task is to be suspended if the storage is not immediately available. The storage is to be initialized to X'00'. The storage class is TASK.
CHAPTER 3
123
CICS System Trace Filters screen
The CICS System Trace Filters screen enables you to specify search criteria by which the CICS System Level Trace display (see page 120) can be reduced to the relevant level of detail. This display may be accessed by selecting option 3 (= Change Filters and Display CICS System Level Trace) from the Traces pull down menu (see page 54).
............................................................................... . . . CICS System Trace Filters . . . . . . Enter up to 100 CICS System Trace Filters below. . . . . The END command will initiate the CICS System Trace display. . . . . . Task TCB Domain Progm Type Function . . ***** * ** **** ***** ***** **************************************** . . . . . . . . . . . . . . . . . . . . . . . . . Command ===> Scroll ===> CSR . . . :.............................................................................:
Notes 1 2
Please refer to Fields on System Level Trace display on page 121 for a full description of each of the fields on the CICS System Trace Filters screen. If you make a mistake specifying your selection criteria then you can press F4 (= Cancel) to return the Trace Filters screen to its initial state.
When you first invoke the CICS System Trace Filters screen in a DUMPMASTER session, each filter field will be filled with asterisks (*), as shown above. An asterisk represents any character, which indicates that trace entries containing any character in the relevant location will be selected. If you specify a character other than * then only trace entries containing that character in that position will be displayed; also, the value will be saved and redisplayed in the relevant position when you next access the CICS System Trace Filters screen. For example (provided no other search criteria are specified): A Task A Task filter of ***** displays all task entries. filter of 00087 displays only those entries for task 00087. displays only Execution Interface Program entries.
A Progm filter of EIP
Filtering fields may be used in conjunction with one another. For example (provided no other search criteria are specified): A Task
and a Type
filter of 00087 } displays only those entries for task 00087 filter of ENTRY } which have been written on entry to a function.
124
CHAPTER 3
CICS Full Trace Entry display

Note
This type of display is applicable to CICS Transaction and System Dumps.
Point and Shoot on the . marker adjacent to any CICS Trace Table display entry (see CICS System Level Trace display on page 120) to obtain a Full Trace display:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------CICS Full Trace Entry ***************************** START OF TRACE ENTRY **************************** Point & shoot . items below to select a display . . Next trace entry. Previous trace entry.
LD 0002 LDLD EXIT - FUNCTION(ACQUIRE_PROGRAM) RESPONSE(OK) ENTRY_POINT(85201840) LOAD_POINT(05201800) PROGRAM_LENGTH(CD0) FETCH_TIME (0) PROGRAM_ATTRIBUTE(REUSABLE) LOCATION(ESDSA) COPY_STATUS(OLD_COPY) TASK-00285 KE_NUM-0033 TCB-009EB238 RET-84D2FA8C TIME-16:05:50.5910147500 INTERVAL-00.0000213750 Trace entry return point 84D2FA8C 1-0000 0010 0020 0030 0040 0050 0060 0070 0080 00880000 B4680A14 C5D4F3F1 00000000 00000CD0 00000000 00000000 02000002 00000000 0000001C 00000000 04C89F50 85201840 00000000 00000000 00000000 00000000 00000000 00000000 01000100 04C91C48 05201800 00000000 00000000 00020000 00000000 is at offset Unknown in program Unknown 00000000 C4D4C3C4 04C89F50 05000008 00000000 00000000 C4D404D4 00000000 *.h..............* *............DMCD* *EM31.H.&.I...H.&* *....e.. ........* *................* *................* *............DM.M* *................* *........*
****************************** END OF TRACE ENTRY *****************************
In this example, the trace entry return point (84D2FA8C) is not on file (that is the R14 address is outside the range of addresses represented by the program area Notes for the dump). If the address was on file then an entry similar to the following would appear:
Trace entry return point 85A01BFC is at offset BFC in program DSN8CC0
In a CICS Full Trace Entry display, Point and Shoot fields are provided to allow you to produce a Full Trace Entry display for either:
I
The next (that is later in time) filtered Trace Table entry (unless the current entry is the most recent in the table). The previous (that is earlier in time) filtered Trace Table entry (unless the current entry is the oldest in the table).
Further, several fields in the display are unprotected and tabbable, so that addresses in the area may be used as Point and Shoot targets, causing DUMPMASTER to display the Dump Display for the address at which the cursor is positioned. (Alternatively, the GOTO command may be used see GOTO on page 182.)
125
CHAPTER 4
Chapter 4
Advanced dump inspection facilities
This chapter tells you how to use some of the more complex facilities of DUMPMASTER which are available if a dump cannot be diagnosed using the most commonly used displays. You might like to try using these facilities when you are familiar with the basics of the product. Advanced dump inspection facility topics
I
Dump Menu (DMENU) displays on page 126 Dump displays on page 129 I/O Summary display on page 131 Enqueue list on page 134 Address selection on page 136 Accessing and referencing the registers on page 137 Dump inspection special characters on page 138 Advanced pull down menu on page 140 Extended Find facility on page 142 Note lists on page 146 Using procedural language (REXX API) on page 153 Diagnostic facilities on page 156
126
CHAPTER 4
Dump Menu (DMENU) displays

The Dump Menu lists the display options available for the dump being viewed.
Overview Dump Menu for an MVS dump
below page 127
Dump Menu for a CICS transaction dump page 127 Dump Menu for a CICS system dump page 128
Overview
The list of options that appears on a Dump Menu depends on the type of selection criteria used to select the dump; this, in turn, depends on the dump type (MVS, CICS transaction, or CICS system). There are several ways of proceeding to debug a dump from any Dump Menu:
I
Select an option which will provide further formatted information about the abend. For example, INFO provides the Abend Summary Display for all types of dumps (MVS and CICS transaction dumps, CICS system dumps, and so on). Select an option which will display a list of Notes. A Note may then be selected to display a specific area of the dump. Enter a Note, address or register. This is the fast path route. Invoke an EXEC. The EXEC name is entered in the Command area and is prefixed by a % character. Invoke the EXEC %M4REXX to display a list of available EXECs.
Notes 1 2
The option number, option name, Note, address, register or EXEC name are all entered in the Command area. An option of the Dump Menu may be jumped to without displaying the Dump Menu either by entering the option name, or by entering the command DMENU with the option number as an operand. For example, enter DMENU 0 (or INFO) for the Abend Summary Display option. Many of the Dump Menu options are also immediately available as Point and Shoot items on the Abend Summary Display.
You can return to the Dump Menu by using the DMENU command (see DMENU on page 174).
CHAPTER 4
127
Dump Menu for an MVS dump

An example of such a display appears in the following figure:
Command ===> Dump No 3948 Job PAYCHEQ Command D 0 1 2 3 4 5 6 7 8 DISPLAY INFO PROGRAMS STORE I/O USERNOTE USERSTOR ENQS SYSTEM SUMMARY DUMPMASTER MVS Dump Menu Step CHQPRINT Description List of currently available displays Abend information Program associated areas Acquired storage areas I/O associated areas User defined storage notes All user areas Current ENQ status of address space System storage areas All storage areas Program PCHQ1000 Abend Code S0C4
F1=HELP F7=UP
F2=SPLIT F8=DOWN
F3=END F9=SWAP
Dump Menu for a CICS transaction dump

An example of this type of display appears below:
Command ===> Dump No 78 DUMPMASTER CICS Dump Menu Job CICSPROD Command D 0 1 2 3 4 5 6 7 8 9 10 11 12 F1=HELP F7=UP DISPLAY INFO PROGRAMS STORE I/O USERNOTE TERMINAL TASK JOURNAL TDATA TRACE SYSTEM ERRORS SUMMARY Xact ACCP Description List of currently available displays Abend information Program associated areas Acquired storage areas I/O associated areas User defined storage notes Terminal-related information Task-related information Journal information Transient data areas Trace information System storage areas Discovered errors All storage areas F3=END F9=SWAP F4=Previous F5=Rfind F6=Dmp Menu F10=Dlist F11=PF OnOff F12=Retrieve Program ACCP1050 Abend Code ASCF
F2=SPLIT F8=DOWN
128
CHAPTER 4
Dump Menu for a CICS system dump

An example of the top portion of such a display appears in the following figure:
Command ===> Dump No 852 DUMPMASTER CICS Dump Menu Job RJMCICS4 Xact ???? Command D 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 F1=HELP F7=UP DISPLAY INFO ERRORS USERNOTE AI AP BF CC CP CS DD DLI DM DS DU FCP ICP JCP KE LD LM ME MN Program DFHAPLI1 Abend Code AP0001
Description List of currently available displays Dump Summary Discovered errors User defined storage notes Auto-install model manager Application domain Built-in functions CICS catalog domain CPI static storage area CICS common system area Directory manager domain CICS DL/I interface Domain manager Dispatcher domain Dump domain File control program Interval control program Journal control program CICS kernel Loader domain Lock manager domain Message domain Monitoring domain F3=END F9=SWAP F4=Previous F5=Rfind F6=Dmp Menu F10=Dlist F11=PF OnOff F12=Retrieve
F2=SPLIT F8=DOWN
The bottom (scrolled) portion of the same display is shown below:

Command ===> Dump No 852 DUMPMASTER CICS Dump Menu Job RJMCICS4 Xact ???? Command 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 F1=HELP F7=UP MRO PA PCP PCT PG PR RM SM SS STD SZ TCP TDP TI TMP TRACE TSP UEH US XM XRF XS Program DFHAPLI1 Abend Code AP0001
Description CICS multiregion operation Parameter manager domain Program control program Program control table Program manager domain Partner resource manager Recovery manager Storage manager domain Static storage areas Statistics domain Front end programming interface Terminal control program Transient data program Timer domain Table manager program Trace information Temporary storage program User exit handler User domain Transaction manager Extended recovery facility Security domain F3=END F9=SWAP F4=Previous F5=Rfind F6=Dmp Menu F10=Dlist F11=PF OnOff F12=Retrieve
F2=SPLIT F8=DOWN
CHAPTER 4
Dump displays
129
Dump displays
Dump Display is a major DUMPMASTER debugging screen. It displays the dumped area in the normal hexadecimal and interpreted format. To obtain the Dump Display a Note, address or command must have been entered. A CICS Dump Display, an example of which is shown below, differs from a Batch Dump Display only in that it includes an additional field Owner.
Command ===> DUMPMASTER Dump Display Scroll ===> CSR Time : 09:54 Program ACCP100 Abend Code ASRA 00028CD4 503E139A 010201D4 00023000 00023190 003F66E0 8026A1F2 9026A036 Origin TCA 003F6AE0 *...........M..\* TCA 003100A0 *.......%........* 80312EA0 * ......A........* 503E139A *..B|.......M&...* 0026A008 *...M.......\....* 00023A80 *..D-.... .......* 00006000 * ...ASRA......-.* 003923FC *................* 00000000 *...QACCPVO02....* 00000000 *......sm........* 00000000 *&...............* 503E139A *..B|.......M&...* 0026A008 *...M.......}....* 01020000 *..D-............* 00000000 *................* 00000000 *................* 000239B0 *TWA ACCP..D-....* TWA
Dump No 89 Job CICSTEST Xact ACCP GR 0-7 00000009 00000000 0001C24F 00000000 GR 8-F 000238D0 0026A008 0001C460 FFFFFFFF Address Offset Owner 00047 00023190 000000 00023000 00000000 010201D4 000231A0 000010 00023420 0830516C 20010100 000231B0 000020 40304844 003051C1 00000009 000231C0 000030 0001C24F 00000000 00028CD4 000231D0 000040 010201D4 00023000 003046E0 000231E0 000050 0001C460 00023000 40304844 000231F0 000060 40392818 C1E2D9C1 00000009 00023200 000070 003934B0 00000000 00359AA0 00023210 000080 FE0038D8 C1C3C3D7 E5D6F0F2 00023220 000090 078D0000 0026A294 00060007 00023230 0000A0 50392A52 9026A036 00000009 00023240 0000B0 0001C24F 00000000 00028CD4 00023250 0000C0 010201D4 00023000 000238D0 00023260 0000D0 0001C460 FFFFFFFF 00020000 00023270 0000E0 00000000 00000000 24000000 00023280 0000F0 00000000 00000000 00000000 00023290 000100 E3E6C140 C1C3C3D7 0001C460
Note
The hexadecimal dumped area and registers are unprotected and tabbable so that addresses therein may be used in conjunction with the Point and Shoot facilities. When so accessed, DUMPMASTER displays the Dump Display for the address at which the cursor is positioned.
Fields on Dump Display

GR These fields show the current contents of the registers. Initially they are set to the register values at the time of the abend. The REGS command (see REGS on page 185) is used to temporarily alter the contents of the registers. Address In this column, the address at the top of the list is the current address. It is set to the requested address or the address associated with the Note. Offset Shows the offset in hexadecimal from the current Origin. This field is followed by four fullword blocks of the dump. The line is X'10' in length and split into fullword blocks. The fullword at the address where a Note has been made is highlighted. Owner (For CICS dumps) Is set to the task which owns the current storage area or subarea. A * (asterisk) indicates that the area is not task related.
130
CHAPTER 4
Dump displays
Origin Is set to the Origin address currently associated with the Storage Area or Storage Subarea in which the current address appears. The relationship between storage areas and subareas is described in the section Storage areas and subareas on page 47. Interpreted data area This area, which follows the hexadecimal representation of the dump, contains an interpreted representation of the dump. This is the EBCDIC interpretation of the hexadecimal area. A non-display character is represented by a period, that is a fullstop (.). Note area This shows the first Note which represents the lowest address on that line.
CHAPTER 4
I/O Summary display
131
I/O Summary display

The item I/O Summary is available as a Point and Shoot option from all Abend Summary Displays. It lists and gives access to detailed information on all files which were open when failure occurred.
Note
The I/O Summary display also has an action bar for Navigation, Setup, Listings, Advanced, and so on. From the appropriate pull down menu (see page 52), access to further displays (for example the Current Display List, Note Lists, Macro 4 Diagnostics, and Help) is available.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Summary of Open Files ******************************* Top of Display ******************************** Point & shoot . DD names below to display file details . . . . . . DD name SYSUDUMP UNLOADXX COMMWXYZ SYSIN SYSPRINT SYSOUT Access JES2 QSAM VSAM JES2 JES2 JES2 Disp EXCPs Dataset Name MOD 0 ++++++++.DMXLPYBZ.JOB14477.D0000132.? OLD 589 SYS98051.T171853.RA000.DMXLPYBZ.R0106476 SHR 63 BJPNH.COBTECH.MASTFILE NEW 0 ++++++++.DMXLPYBZ.JOB14477.D0000132.? MOD 0 ++++++++.DMXLPYBZ.JOB14477.D0000132.? MOD 0 ++++++++.DMXLPYBZ.JOB14477.D0000132.?
Each file which was open when failure occurred is listed on this display. To obtain details on a specific file, Point and Shoot on the . indicator to the left of the files DD name. The format of the resulting File Details display depends upon the type of file that was selected:
Typical DCB (Data Control Block) display Typical ACB (Access Control Block) display Typical IAM File Details display
132
CHAPTER 4
I/O Summary display
Typical DCB display

An example of such a display appears in the following figure:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Details of LOCCODE file ******************************* Top of Display ******************************** Dataset Name------: Volumes-----------: Device Type-------: Disposition-------: Access Method-----: Dsorg-------------: Recfm-------------: Blksize-----------: Lrecl-------------: Opened------------: BJ.LOCATION.FILE SCPMV5 3380/DASD SHR QSAM get locate mode PS (Physical Sequential) FB (Fixed Blocked) 6160 80 INPUT
The current record has a length of 80 and is at address 000626F0 Char Zone Digit Char Zone Digit 24PALO ALTO FFDCDD4CDED444444444444444444444444444444444444444 24713601336000000000000000000000000000000000000000 1...5...10....*...20....*...30....*...40....*...50 444444444444444444444444444444 000000000000000000000000000000 51...*...60....*...70....*...80
The previous record has a length of 80 and is at address 000626A0 Char Zone Digit Char Zone Digit 23REDWOOD CITY FFDCCEDDC4CCEE444444444444444444444444444444444444 23954666403938000000000000000000000000000000000000 1...5...10....*...20....*...30....*...40....*...50 444444444444444444444444444444 000000000000000000000000000000 51...*...60....*...70....*...80
DCB: 0000B568 DEB: 008DE794 ****************************** Bottom of Display ****************************** Command ===> Scroll ===> CSR
As shown above, this display presents all the information available from the DCB (Data Control Block) and, when available, from the current and previous records at the time of failure. For VIO datasets, the Volumes field is blank. The Device Type field contains information about the device type which VIO mimics.
CHAPTER 4
I/O Summary display
133
Typical ACB display

An example of this type of display appears below:
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Details of COMMUTR file ******************************* Top of Display ******************************** Dataset Name-------: Volumes------------: Disposition -------: Access Method------: Dataset Type-------: Access Type--------: Macrf--------------: BJ.COBCARS.MASTFILE MVSWK1 SHR VSAM KSDS Base cluster Key,Seq,In,Nsr
Maximum Record Size: 80 CI Size------------: 22528 Index CI Size------: 512 Active strings-----: COUNT String 1's Request and OPTCD Summary The last request was a "GET", which completed return code 8, component code 0, error code 4. The key of the last record successfully read was Char Zone Digit 20212BRIAN FS FFFFFCDCCD4444CE 2021229915000062 1...5...10....*.
The RPL's address is 0004C944 The OPTCD specified SYN(synchronous), MVE(move mode), NUP(no update), SEQ(sequential access), FKS(full key search), KEQ(search for key equal), KEY(locate the record by a key), ARD(users argument determines the record), and FWD(process forwards). ACB: 0004C8F4 DEB: 008DBF78 ****************************** Bottom of Display ****************************** Command ===> Scroll ===> CSR
As shown above, this display presents in full detail all the information available from the RPL (Request Parameters List) of the ACB (Access Control Block) and, when available, string details of the current record.
134
CHAPTER 4
Enqueue list
Enqueue list
The Enqueue List is a list of all the global and local resource enqueue requests issued by the abending address space which are held or waiting.
Note
The Enqueue List Display also has an action bar for Navigation, Setup, Listings, Advanced, and so on. From the appropriate pull down menu (see page 52), access to further displays (for example the Current Display List, Note Lists, Macro 4 Diagnostics, and Help) is available.
The Enqueue List is only available for MVS, that is address space, dumps. It is accessed from the MVS dump environment by using one of the following methods:
I
Issuing the ENQS command (see ENQS on page 178). Selecting the ENQS option from the Dump Menu. Issuing the DMENU 6 command (see DMENU on page 174). Accessing it by Point and Shoot from the Abend Summary Display.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Display of System ENQs/Status **************************** Start of Enqueue List ***************** Major Name - 'FILEA222' Minor Name - 'ASID0021' TCB - 00AFB3F8 SVRB - 00AFEB20 Scope - SYSTEM Status - EXCLUSIVE/OWNED Major Name - 'SYSDSN ' Minor Name - 'AC6.ACTEST.LOADLIB' TCB - 00AFB8A8 ECB - 00AC3020 Scope - SYSTEM Major Name - 'FILEA222' Minor Name - 'ACTIVE' TCB - 00AFB3F8 ECB - 00D26944 Major Name - 'SYSIEA01' Minor Name - 'IEA' TCB - 00AFB3F8 SVRB - 00AFEA08
Status - SHARED/OWNED
Scope - SYSTEM
Status - EXCLUSIVE/WAITING
Scope - STEP
Status - EXCLUSIVE/OWNED
***************************** End of Enqueue List ****************** Command ===> Scroll ===> CSR
Note
A number of the address fields are unprotected. These fields may be used in conjunction with the Point and Shoot facility. When so accessed, DUMPMASTER displays the Dump Display for the address at which the cursor is positioned.
Fields on Enqueue List display

Major Name Minor Name Represent the name of the resource used in the enqueue request. Scope Represents the scope of serialization. This determines which other tasks, address spaces or systems can use the resource. Scope will have one of the following values: STEP denotes that the scope of the resource is only applicable within an address space.
CHAPTER 4
Enqueue list
135
SYSTEM denotes that the scope of the resource is applicable to more than one address space. SYSTEMS denotes that the scope of the resource is applicable to more than one system. Status Represents the status and ownership of the resource for the enqueue request: EXCLUSIVE denotes exclusive control of the resource. SHARED denotes shared control of the resource. OWNED denotes resource is owned by the task. WAITING denotes task is waiting for the resource. SVRB Is the address of the Supervisor Request Block. TCB Is the address of the Owning Task Control Block. ECB Is the address of the Event Control Block.
136
CHAPTER 4
Address selection
Address selection
You request an address in DUMPMASTER by using one of the following methods:
I
Point and Shoot facilities. Issuing a POINTx type command (see Positioning commands on page 182). Accessing a register. Issuing the GOTO command (see GOTO on page 182).
When an address is requested, DUMPMASTER checks the dump for addresses which match the address in 24 bit and 31 bit mode. Then:
I
If a match is found in both modes then the Address Selection display is presented (see below). If only a single match is found then the Dump Display at that address is displayed immediately (see Dump displays on page 129). If no match is found then a warning message is issued.
Command ===> DUMPMASTER Address Selection
02200F00 is valid within this dump as either a 24 or a 31 bit address Enter a non-blank character beside the address you wish to use or press ENTER to use the 24 bit address Use 24 bit value 00200F00 Use 31 bit value 02200F00 Use neither
When the Address Selection Display is presented either the 24 bit or 31 bit address may be selected and the Dump Display at that address is then displayed.
CHAPTER 4
Accessing and referencing the registers
137
Accessing and referencing the registers

The current value of the registers is available on the Note Lists and Dump Display. The upper portion of a Dump Display appears below, which shows the register area (GR fields) at the top:
Command ===> DUMPMASTER Dump Display Scroll ===> CSR Time : 08:43 Program ACCP100 Abend Code ASRA 00028CD4 503E139A 010201D4 00023000 00023190 003F66E0 8026A1F2 9026A036 Origin TCA 003F6AE0 *...........M..\* TCA 003100A0 *.......%........*
Dump No 1988 Job TESTCICS Xact ACCP GR 0-7 00000009 00000000 0001C24F 00000000 GR 8-F 000238D0 0026A008 0001C460 FFFFFFFF Address Offset Owner 00047 00023190 000000 00023000 00000000 010201D4 000231A0 000010 00023420 0830516C 20010100
The contents of the address in a register is viewed by entering the required register number in the Command area. Each of the registers is referenced by preceding the register number with R, hence R0 R15. Alternatively, R00 R09 may be used, and registers 10 to 15 may be referenced by RA RF. The REGS command (see REGS on page 185) is used to temporarily alter the contents of all or some of the registers. The new values are displayed in the GR fields.
138
CHAPTER 4
Dump inspection special characters

Retain command character (&) Repositioning characters (+ and -) Special Help character (?)
below below page 139
Retain command character (&)

&anycommand
Leave the command in the Command area after processing. anycommand is any DUMPMASTER or ISPF command. For example: The EXPAND command is entered in the Command area. The command is retained in the Command area by prefixing the command with an ampersand (&). Command ===> &expand DUMPMASTER will issue the EXPAND command and leave the command in the Command area: Command ===> &EXPAND
Repositioning characters (+ and -)

+hexoffset|-hexoffset|+Rnn|-Rnn
Reposition the Dump Display relative to current address. hexoffset is the amount in hexadecimal by which current address is to be adjusted. Rnn is the value contained in that register. The adjustment value can be entered as an expression, for example:
R14+R15-2E
would set the new position to be the contents of Register 14 plus the contents of Register 15 minus X'2E'. Repositioning characters can also be used with commands and names of Notes, for example:
POINT+4
sets the new position to the contents of the current address plus 4, and:
SYSPRINT ACB + 28
sets the new position to offset 28 within the Note SYSPRINT ACB.
CHAPTER 4
139
Special Help character (?)

? [command]
Enter the Help Facility for a specific DUMPMASTER command. If the command is omitted or unrecognisable the Dump Display Help Menu is displayed. The abbreviated forms of the command will be recognized. (This feature is available only when a dump has been selected, and not from the Initial, Setup, Selection, or List screens.)
140
CHAPTER 4
Advanced pull down menu

Note
This pull down menu is not accessible from the Dump Selection display or the Dump List display.
If a dump cannot be diagnosed using the most commonly used displays, the Advanced pull down menu lists the more advanced displays that are available. The displays are made available using the Point and Shoot design philosophy of DUMPMASTER, which means that you do not have to remember the corresponding line command.
Navigation Setup Listings Advanced Traces Help ---------------------------- .............................. ------------------: 1. Extended Find : : 2. Note List Generation : **************************** : 3. Batch dump print : ******************* : 4. Supplementary EXECs : Dump No 1647 Job P48324A : 5. Macro 4 Diagnostics : :............................: Point & shoot . items below to select a display Abend code = S878 PSW at time of abend = 070C1000 814B1B9C
The sections that follow describe these advanced DUMPMASTER facilities.

Extended Find facility Note lists Batch dump print Using procedural language (REXX API) Macro 4 diagnostics
page 142 page 146 page 141 page 153 page 156
CHAPTER 4
141
Batch dump print

Take the Batch dump print option from the Advanced pull down menu to print a selected dump using the DUMPMASTER Dump Print facility. The printed report includes:
I
Separate sections (Abend, DB2, I/O, PL/I, and IMS summaries; load module details; call chain; and so on), which contain a level of detail similar to the online Dump Inspection facility displays. Information on all storage captured by the dump. An index, which guides you to the various sections of the report.
The printed report does not include program compilation listings analysis.
Notes 1
When you take this option, you are prompted to specify the JCL information to be used to construct the job (job card data (JOB), printer destination (DEST), printer class (SYSOUT), and so on). You also have the option of editing the job before it is submitted. You can also print a dump by entering the P action code against a dump on the Dump List display (see page 33). Descriptions of abend codes are generated by DUMPMASTER itself; that is, the report does not include Chicago-Soft QuickRef diagnostics. For information on how to trigger an Instant Print, a printed summary report that is integrated into the failing jobs output, please refer to the DUMPMASTER MVS Technical Reference.
2 3 4
Example of a printed detailed report Member PRINTF of user.SAMPLIB contains an example of a printed report.
142
CHAPTER 4
Extended Find facility

Extended Find searches the whole or part of a dump for occurrences of character or hexadecimal search arguments. The facility is available as an option on the Advanced pull down menu (see page 140). (Alternatively, it is obtained by entering the XFIND command on the Command line; see XFIND on page 189.)
Note
Extended Find can be used in lieu of DUMPMASTERs LOCATE command (see LOCATE on page 188), which is limited to a particular display, rather than all of storage if necessary.
DUMPMASTER Extended Find : : T : : : : : + 0 * * XFIND_1 Scroll ===> CSR
Command ===> Search string Search type Context adjustment Note mask Note SubNote Hit note prefix Display name Maximum hits Sort on address?
Character T case insensitive C sensitive Hex X byte aligned H half-byte - or + hex offset e.g. - 1C , + 8 Only search dump storage conforming to the note mask Generate notes e.g. HIT1,HIT2,... (as in the Current Display List) Stop search after this many hits YES or NO (No suppresses the sort)
: 100 : YES
Press ENTER to initiate the search. Enter the END command to quit Find.
Each search option has a default which may be modified to tailor the search to specific needs. Each entry on the display is described below in sequence, followed by an illustration and description of the display of search results.
Note
Pressing the Enter key before all entries have been keyed-in can result in an erroneous search.
See
For information on
Entries on Extended Find display Extended Find, Scan display
below page 144
Entries on Extended Find display

Search string (This is a required entry) Key-in the desired character or hexadecimal string. Character strings may be enclosed in single (') or double (") quotation marks, although this is necessary only if a specific number of trailing blanks are to be included in the string. Hexadecimal digits must be in the ranges 0 9 and A F. Search type Two types of character and two types of hexadecimal search are available. They are mutually exclusive.
Type T C Description
character character
Case is not significant. (This is the default.) Case is significant, for example 'A' and 'a' are not equivalent.
CHAPTER 4
143
Type X
Description
hexadecimal
Byte-aligned; the search string must contain an even number of hexadecimal digits. Only byte-aligned strings will be matched. Half-byte-aligned; the search string may contain any number of hexadecimal digits. Half-byte-aligned strings will be matched. (This is useful in searching for addresses in which the content of the upper four bits is uncertain.)
hexadecimal
Context adjustment This option varies the address displayed after a successful scan by the amount of the adjustment. The increment (+) or decrement (-) sign is required, while the adjustment, specified in hexadecimal, must be in the range -FFF to +FFF. The default is +0, that is no adjustment. For example, this is useful when a search target is used which is offset a known distance from the beginning of a data structure. The adjustment can be used to start the display at the beginning of the structure, rather than at the search target. Note mask This option limits the range of the search to certain parts of the dump. Note and SubNote names are used as masks. Full names may be used, or generics in which * (asterisk) means any number of characters and + (plus) means any single character in that position. A mask may be from one to eight alphanumeric characters long. (The Note and SubNote defaults of * mean the entire dump is to be searched, that is no masking.) Note may be any System or User Note name, full or generic. Subnote may be any System or User SubNote name, full or generic. For example, specifying * for Note and PROGRAM for SubNote means search only program storage, while specifying ABC* for Note and * for Subnote means search all Note names beginning ABC. Hit note prefix When not blank (the default), this option specifies that Notes with this prefix be generated on each search target found, that is on each hit. The prefix will be followed by a sequential decimal integer denoting the hit. The prefix itself may be from one to four alphanumeric characters. For example, if prefix ABCD is specified, the first hit will be allocated Note ABCD1, the second will be allocated Note ABCD2, and so on. Display name This option specifies the name to be used to identify the display presenting the results of this particular search (if successful) in the Current Display List, or display of displays. The name may be from one to 17 alphanumeric characters. The default is XFIND_n, where n is the sequential number of this search in this session.
144
CHAPTER 4
Maximum hits This option specifies the maximum number of hits, or search targets found, after which the search is to be terminated and the results displayed. The range is 1 9999; the default is 100. Sort on address? This option specifies whether or not the hits, or search targets found, are to be sorted on address in the display. (Even if specified, no sort takes place if hits exceed 200.) The default is YES, that is sort the results before display. Sorting results in a more intelligible display, and eliminates lines for duplicate addresses which may arise from multiple Notes for the same address. However, sorting can require considerable time.
Extended Find, Scan display

Scan results from a successful Extended Find search are displayed immediately. They also can be reviewed later from the Current Display List or with the DISPLAY command (see DISPLAY on page 177), using the Display Name as an operand. (The Current Display List itself is available as an option on the Navigation pull down menu see page 52, or by entering the DISPLAY command without an operand.)
Command ===> Scan for SYS Scroll ===> CSR DMO074 - SYS found 25 times. ****************************** Start of Display ******************************* Note X X X X X X STORAGE STORAGE STORAGE STORAGE STORAGE STORAGE STORAGE STORAGE STORAGE STORAGE TIOT SubNote PROGRAM PROGRAM PROGRAM PROGRAM PROGRAM PROGRAM 0002 0002 0002 0002 0002 0002 0003 0004 0005 0006 TIOT Offset 000CA8 000CB0 000CB8 000CC0 000CC8 000CD0 000BB4 000C14 000C74 000CD4 000D34 000D94 006C73 002287 000D4F 002287 000030 Address 00006F70 00006F78 00006F80 00006F88 00006F90 00006F98 00007BB4 00007C14 00007C74 00007CD4 00007D34 00007D94 00016C73 0002F287 00033D4F 0003D287 009D2030 -------------- Data --------------E2E8E2E4E3F14040E2E8 E2E8E2E4E3F24040E2E8 E2E8E2E4E3F34040E2E8 E2E8E2E4E3F44040E2E8 E2E8E2E4E3F54040E2E8 E2E8E2E4E3F940400000 E2E8E2E4E3F140400200 E2E8E2E4E3F240400200 E2E8E2E4E3F340400200 E2E8E2E4E3F440400200 E2E8E2E4E3F540400200 E2E8E2E4E3F940400200 E2E8E2D3C9E2E340D3C5 E2E8E2C5C3C4E2C14040 E2E8E2C5C3C4E2C14040 E2E8E2C5C3C4E2C14040 E2E8E2E4C4E4D4D79E22 * * * * * * * * * * * * * * * * * SYSUT1 SY SYSUT2 SY SYSUT3 SY SYSUT4 SY SYSUT5 SY SYSUT9 .. SYSUT1 .. SYSUT2 .. SYSUT3 .. SYSUT4 .. SYSUT5 .. SYSUT9 .. SYSLIST LE SYSECDSA SYSECDSA SYSECDSA SYSUDUMP.. * * * * * * * * * * * * * * * * *
The results of a typical Extended Find scan are shown above. (The search argument used, the characters SYS, are shown in the display title.) Each line on the display (only a portion of which is shown) indicates a single hit, or search target found. Since sorting on address was specified, and the number of hits did not exceed 200, the lines are in that sequence and duplicate addresses resulting from multiple Notes have been eliminated. The Note and SubNote columns show the Note and SubNote names identifying the storage in which the search string target was found. The Offset column shows the offset, in hexadecimal, of the search string target from the Note.
CHAPTER 4
145
The address at which the search string target was found is shown in the Address column. This has been adjusted by the amount of context adjustment (if any) specified on the display initiating the search. To view a full-screen dump display of the storage at any address shown, Point and Shoot, that is tab to the highlighted address field on the display and press the Enter key. The Data columns show the contents of storage at the (adjusted) address, in both hexadecimal and character formats.
146
CHAPTER 4
Note lists
Note lists
The Note List is used to provide one of the following types of list:
I
All the Notes for a dump. All the Notes which are in a logical group. All the Notes which pass a selection criteria defined by using the SUMMARY command (see Note List SUMMARY command on page 150).
See
For information on
Example of a Note List display (Note formats; Note line commands) General information on Note Lists Note List Generation pull down menu option Note List commands
below
Example of a Note List display

An example of a SUMMARY Notes display appears below:
Command ===> Dump No 1919 DUMPMASTER SUMMARY Notes Job PRODCICS Xact RTSC Program RTSCUPD2 Note 1 of 34 Scroll ===> PAGE Abend Code ASRA
GR 0-7 00000005 0041F7AE 0041F78A 00000074 0055ECD0 00597A58 00058200 005F67A0 GR 8-F 00038C28 000578E0 8002AD58 00419030 00419EE6 00057A30 50419F6C 00000000 Enter Name . . . . . . . . . . . . . . SUMM_KE INS CSA CSAOPFL PCT PPT SYSTCA TCA TCTTE OPFL TWA COMM COMM RTSCUPD2 S Select (default) Subname SUMMARY X Extra information Length F Format Task ALL
Address 00000000 00419F9A 005F67A0 0003EFE8 0003CED4 0003CB24 00038000 00038190 0003A304 005F6BA0 00038290 0002AD58 0003AAA8 004F1008
Description Summary print lines User defined note Common system area CSA optional features list + Program control table Program processing table Task control system area Task control user area Terminal control table terminal entry Optional features list Transaction work area Exec level common area Exec level common area Program
00810 00810 VO02 00810 0001 0002 PROGRAM
1024 1232 96 40 400 4992 440 608 2048 130 8 8192
The fields on this screen are described below: GR This shows the current contents of the registers. Initially they are set to the register values at the time of the abend. The REGS command (see REGS on page 185) is used to temporarily alter the contents of the registers. Task Indicates the current value of the TASK filter, which is altered by using the SETTASK command see SETTASK on page 186.
CHAPTER 4
Note lists
147
Address Is the address which the Note represents. Length Is the length of the storage area or the storage subarea in decimal. If the length is less than 32K then the length is the number of bytes. When the area is larger than 32K, the length is given to the nearest Kilobyte or Megabyte.
Note formats Note line commands
below below
Note formats
There are two formats of Note dump data and text; some Notes contain both:
I
Notes containing dump data or dump data and text generally have a non-blank Length and a non-zero Address. (The exception is PROGRAMS Notes when the program name is an ALIAS name of the load module, in which case Length is blank.) Notes containing only text have both a blank Length and an Address of 00000000.
Note line commands
There are three line commands which may be used with Note Lists:
S
Selects the Note for viewing.

Note
You can also use Point and Shoot on a Note to select it.
DUMPMASTER displays the dumped area from the address associated with the Note, or the Note text. Text Notes are viewed with the ISPF/PDF BROWSE function; all BROWSE commands are supported.
X
Displays additional information for the Note (only when the Description for the Note is followed by a highlighted + (plus), which indicates that DUMPMASTER has further information about the area). Additional information in text is viewed with the ISPF/PDF BROWSE function; all BROWSE commands are supported.
F
Displays the Format Display for that area. The Format Display is described in more detail in FORMAT on page 178. Note List commands provide Note Lists for different groups of Notes. There are three sets of commands, one for each of the three types of dumps serviced: MVS, that is address space dumps, CICS transaction dumps, and CICS system dumps. (Some commands apply to more than one type of dump.)
General information on Note Lists

From a Note List, any command, address or Note may be entered in the Command area. The Note List is pageable using the normal ISPF paging commands.
148
CHAPTER 4
Note lists
Once a Note is selected, the Dump Display screen pertinent to it is displayed. Origin is set to the Origin address currently associated with the storage area or storage subarea in which the Note is set. Current address is set to the address associated with the selected Note. The storage area or storage subarea associated with the Note will become the current area. Notes are assigned priorities. A Note List appears in alphabetical order within priority. Higher priority Notes appear first. Since User Notes are assigned a higher priority than System Notes, they always will be listed before System Notes.
Note List Generation pull down menu option

An option for Note List Generation is available on the Advanced pull down menu (see page 140). Each type of dump (MVS, CICS transaction, or CICS system) gives rise to a different list of available Notes, the entries in the list corresponding to the Note List Commands available for the particular type of dump. For example, the list that appears for an MVS dump appears below each entry in this list is associated with one of the Note List Commands see Note List commands below.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Note List Generation ******************************* Top of Display ******************************** Point & shoot . items below to select a display . . . . . . . Program associated areas Acquired storage areas I/O associated areas User defined storage notes All user areas System storage areas All storage areas
Command ===>
Scroll ===> CSR
From this display, Point and Shoot on the indicator next to the appropriate class (for example, Acquired storage areas) to generate the required set of Notes. If the Point and Shoot indicator for a class is absent, it means that storage notes are unavailable.
Note List commands

MVS dump Note List commands CICS transaction dump Note List commands CICS system dump Note List commands Note List SUMMARY command
page 149 page 149 page 149 page 150
CHAPTER 4
Note lists
149
MVS dump Note List commands
I/O|IO PROgrams STore Summary SYstem USERNote USERStor
I/O storage area Notes. Program area Notes and their related control block Notes. Storage area Notes and their related control block Notes. See Note List SUMMARY command on page 150. System area Notes, that is a combined list of all Notes except those normally listed using the PROGRAMS, STORE, and I/O commands. All user Notes, including Notes generated by DUMPMASTER commands, in alphabetical order. A combined list of all Notes normally listed using the PROGRAMS, STORE, and I/O commands.
CICS transaction ERrors dump Note List I/O|IO commands JOurnal

PROgrams STore Summary SYstem TAsk TData TErminal USERNote
CICS areas in which DUMPMASTER has found errors. I/O storage area Notes. CICS journalling storage area Notes. Program area Notes and their related control block Notes. Storage area Notes and their related control block Notes. See Note List SUMMARY command on page 150. System area Notes, that is a combined list of all Notes except those normally listed using the PROGRAMS, STORE, and I/O commands. CICS task storage area Notes. CICS transient data area Notes. CICS terminal area Notes. All user Notes, including Notes generated by DUMPMASTER commands, in alphabetical order.
CICS system dump Note List commands
AI AP BF CC CP CS DD DLI DM DS DU ERrors FCP ICP JCP KE
Auto-install model manager Notes. Application domain Notes. Built-in functions Notes. CICS catalog domain Notes. CPI static storage area Notes. CICS common system area Notes. Directory Manager domain Notes. CICS DL/I interface Notes. Domain Manager Notes. Dispatcher domain Notes. Dump domain Notes. CICS areas in which DUMPMASTER has found errors. File control program Notes. Interval control program Notes. Journal control program Notes. CICS kernel Notes.
150
CHAPTER 4
Note lists
LD LM ME MN MRO PA PG PCP PCT PR RM SM SS STD Summary SZ TCP TDP TI TMP TSP UEH US USERNote XM XRF XS
Loader domain Notes. Lock manager domain Notes. Message domain Notes. Monitoring domain Notes. CICS multiregion operation Notes. Parameter manager domain Notes. Program manager domain Notes. Program control program Notes. Program control table Notes. Partner resource manager Notes. Recovery manager Notes. Storage manager domain Notes. Static storage areas Notes. Statistics domain Notes. See Note List SUMMARY command below. Front end programming interface Notes. Terminal control program Notes. Transient data program Notes. Timer domain Notes. Table manager program Notes. Temporary storage program Notes. User exit handler Notes. User domain Notes. All user Notes, including Notes generated by DUMPMASTER commands, in alphabetical order. Transaction manager Notes. Extended recovery facility Notes. Security domain Notes.
Note List SUMMARY command
Summary [note] [subnote|COBOL|PL1]
Display a complete or selective Note List for the currently selected dump.
note Any system or user Note; either a full or generic name may be used. subnote Any system or user Subnote; enter either a full or generic name. COBOL Used by DUMPMASTER as a Subnote for all COBOL Notes. PL1 Used by DUMPMASTER as a Subnote for all PL/I Notes.
Specifying generic Note names

note or subnote may incorporate either of the following special characters: * (Asterisk) to indicate any number of characters. + (Plus) to indicate any one character in that position.
CHAPTER 4
Note lists
151
The command default is SUMMARY * *. This creates a Note List of all Notes for a dump. For dumps with a large number of Notes, building such a Note List may require considerable time; thus, it is not recommended with CICS System Dumps.
SUMMARY command examples using generics: SUMMARY MY* * SUMMARY * PR* SUMMARY PR++ SUMMARY * PL1 SUMMARY * COBOL SUMMARY * taskid
Displays all Notes beginning MY, with all Subnotes. Displays all Notes having Subnotes beginning PR. Displays all the four-character Notes beginning PR. Displays all PL/I Notes. Displays all COBOL Notes. Displays all CICS task-related areas for a specific task.
Notes generated for CICS dumps For CICS dumps, DUMPMASTER generates a distinguishing subnote for each of the following notes: note
FCTTE TCA TCADS TCADY TCAPS TCTTE TWA
subnote The DD name of the entry. The CICS task id. The CICS task id. The CICS task id. The CICS task id. The terminal id of the entry. The CICS task id.
For CICS 4.1, DUMPMASTER generates two extra Notes for transaction dumps. These are PROG_INF and TRAN_INF:
PROG_INF
This Note shows program information for the current transaction, for example:
DUMPMASTER PROG_INF Browse Line 00000000 Col 001 080 Command ===> _ Scroll ===> ********************************* TOP OF DATA ********************** PROGRAM INFORMATION FOR THE CURRENT TRANSACTION Number of Levels 00000001 INFORMATION FOR PROGRAM AT LEVEL 00000001 of 00000001 Program Name WOLCICS Invoking Program CICS Load Point 02FBDDC0 Program Length 00004A58 Entry Point 82FBDDE8 Addressing Mode AMODE 31 Language Defined ASSEMBLER Language Deduced ASSEMBLER Commarea Address 02FB6008 Commarea Length 00000008 Execution Key CICS Data Location BELOW Environment User application ******************************** BOTTOM OF DATA ********************* F1=HELP F7=UP F2=SPLIT F8=DOWN F3=END F9=SWAP F4=RETURN F10=LEFT F5=RFIND F11=RIGHT F6=RCHANGE F12=RETRIEVE
152
CHAPTER 4
Note lists
TRAN_INF
This Note shows transaction information for the current transaction, for example:
DUMPMASTER TRAN_INF Browse Line 00000000 Col 001 080 Command ===> _ Scroll ===> PAGE ********************************* TOP OF DATA ********************** Transaction environment for transaction_number(0003077) transaction_id(VTUH) orig_transaction_id(VTUH) initial_program(WOLCICS ) current_program(WOLCICS ) facility_type(TERMINAL) facility_name(VV03) Start_code(TO) netname(S05TVV03) profile_name(WOLPROF ) userid(CICSUSER) cmdsec(NO) ressec(NO) spurge(NO) dtimeout(0000000) tpurge(NO) taskdatakey(CICS) taskdataloc(BELOW) twasize(00000) twaaddr( ) remote(NO) dynamic(NO) priority(001) Tclass(NO) runaway_limit(0005000) indoubt(BACKOUT) cics_uow_id(AA4AA68C23BF6201) system_transaction(NO) restart_count(00000) restart(NO) ******************************** BOTTOM OF DATA *********************
F1=HELP F7=UP
F2=SPLIT F8=DOWN
F3=END F9=SWAP
F4=RETURN F10=LEFT
F5=RFIND F11=RIGHT
F6=RCHANGE F12=RETRIEVE
CHAPTER 4
Using procedural language (REXX API)
153

When viewing a dump, you may sometimes find it useful to have an automatic procedure to perform some of the steps that you frequently repeat when looking at a dump, or perhaps a procedure to process some of the more intricate calculations. The procedural language implementation of DUMPMASTER, that is the REXX API (Application Program Interface), enables such procedures (EXECs) to be run. The implementation uses REXX as supplied by IBM with TSO/E.
Running an EXEC Writing your own EXECs
below page 154
Running an EXEC
When viewing a specific dump, that is viewing a Dump Display, you can invoke an EXEC from the DUMPMASTER Command line. The format is:
%execname operands
Alternatively, from the Advanced pull down menu (see page 140), you can select the Supplementary EXECs option to display a list of the procedural language (REXX API) EXECs that are available to you. From here, you can invoke an EXEC using the R (Run) function. Note that you can also invoke the DUMPMASTER EXEC List display by issuing the following command from the Command line when viewing a dump:
%M4REXX
With either of the latter two methods, you will see a screen similar to the following:
Command ===> Enter REFRESH Parameters: Enter E Edit B Browse R Run EXEC DUMPMASTER EXEC List to rebuild the EXEC list. Scroll ===> PAGE
Member . . . . . . . . . . . . . CLRSTACK CONVSTCK DUMPTIME FORMAT GETREAL ISPEXEC LINKAGE QW2 SAVES SAVETCB SETUP SYSEXEC VSAMRECD F1=HELP F7=UP
Description of EXEC function Clear the STACK and (optionally) run stack as commands REXX to convert STCK TOD to Gregorian This REXX will display time dump occurred, or dump capture time Format a control block - SYNTAX - %FORMAT type address Display real storage. ARG1 is either an address or R0 to R15 Run a command as an ISPF function (M4) Build a display of current linkage stack contents Use QuickRef(r) to display ABEND code information (M4) Chain through the save areas from R13 and display (M4) Chain through save areas from the TCB and display SETUP DUMPMASTER options Run a DUMPMASTER EXEC which is allocated to SYSEXEC/SYSPROC (M4) Note VSAM records read and not yet released F2=SPLIT F3=END F4=Previous F5=Rfind F6=Dmp Menu F8=DOWN F9=SWAP F10=Dlist F11=PF OnOff F12=Retrieve
This display shows a list of available EXECs. Some of these are supplied on the distribution tape by Macro 4 as indicated by (M4) in the Description field. To the left of each EXEC name is a command field in which you can enter:
154
CHAPTER 4
E B R
to edit an EXEC to browse an EXEC to run an EXEC
The Description field of the DUMPMASTER EXEC List display tells you the function(s) performed by each of the EXECs. (The text found in the second line of the member is used as its description, provided that this line starts with a /*.) If the description does not give enough information, you can browse a member to see what it does. The EXECs supplied by Macro 4 often have usage instructions in a commentary box at the beginning. You can run an EXEC from the DUMPMASTER EXEC List display by entering R in the command field to the left of the EXEC name. If the EXEC needs arguments, these can be typed in the Parameters: field which appears towards the top of this display. The arguments are retained in this field so that you can reinvoke an EXEC without having to rekey its arguments. If you cannot find a particular EXEC, it may be in an EXEC library that is not being searched. Refer to the section Specifying EXEC libraries used by ISPF in the DUMPMASTER MVS Installation Guide.
Running an EXEC In addition to the above methods for running an EXEC, you can also set up DUMPMASTER to invoke an EXEC when a dump is first selected. Go into the automatically
DUMPMASTER Setup Options screen (option 0 from the Initial Menu), select VIEW (option 2) and you will see the Dump Viewing Options screen (see VIEW dump viewing options on page 23). There are two fields where you can enter a command to be invoked on initial dump selection, one for MVS and one for CICS. These look like:
Initial EXEC to be supplied when dump selected MVS Dumps ===> %MYEXEC CICS Dumps ===>
In this example, one field has been filled in. Remember that you need to specify the % immediately before the EXEC name just as you would when invoking it from the Command line. See also Deferred listings analysis on page 24.
Writing your own EXECs

You can make this facility more valuable by writing your own EXEC, either by copying one of the supplied EXECs and modifying it, or by creating your own from scratch. This topic is described in detail in the DUMPMASTER MVS Technical Reference. If you choose to do this then please contact your System Programmer who will be able to tell you where to put your new EXEC so that it can be used by DUMPMASTER.
Notes 1
Do not edit any of the Macro 4 supplied EXECs, denoted by (M4) in the Description field. We are unable to provide support for any Macro 4 EXEC which has been changed. Instead, we recommend that you take a copy of a suitable EXEC, and modify the copy.
CHAPTER 4
155
A list of available EXECs is created for each user when they first run %M4REXX. The list of EXEC names and descriptions is not rebuilt when an EXEC is modified or a new one created. Issue the REFRESH command from the DUMPMASTER EXEC List display in order to update the list. However, if you have modified an EXEC, you can still edit, browse, or run the modified EXEC from the DUMPMASTER EXEC List display.
156
CHAPTER 4
Diagnostic facilities
Macro 4 diagnostics Advanced diagnostic facilities
below below
Macro 4 diagnostics
A set of diagnostic facilities are available as an option from the Advanced pull down menu (see page 140). These are to further aid you in problem diagnosis and resolution.
Navigation Setup Listings Advanced Traces Help -----------------------------------------------------------------------------Macro 4 Diagnostics ******************************* Top of Display ******************************** Point & shoot . items below to select a display . . System and DUMPMASTER Software Levels DUMPMASTER File Allocation Details
Command ===>
Scroll ===> CSR
From here, several displays are available by Point and Shoot access.
I
System and DUMPMASTER Software Levels Various system and Macro 4 installed software levels and certain hardware identifiers will be listed. These should be noted in the event it becomes necessary to consult your local Macro 4 Support Representative. DUMPMASTER File Allocation Details This display shows the allocation details of the files necessary for dump viewing and program listing selection. It will generally have been requested by Macro 4 support staff or your local installer of DUMPMASTER.
Advanced diagnostic facilities

Further advanced diagnostic facilities are available as options from the appropriate action bar item.
I
From the Navigation pull down menu (see page 52): A list of currently-available displays. This list is continuously updated as the displays are generated by DUMPMASTER during a session. For more information, see Current Display List on page 178. An option is also available to return to the Abend Summary Display.
From the Setup pull down menu. (See page 53 for details.)
CHAPTER 4
157
From the Listings pull down menu. (See page 53 for details.) From the Advanced pull down menu (see page 140):
I
An extended FIND facility, which conducts a highly-qualified search of all or part of a dump for character or hexadecimal search arguments. For more information, see Extended Find facility on page 142. A display for Note List generation, on which a selection of Notes is offered, each of which may be generated by Point and Shoot. Each type of dump (MVS, CICS transaction, or CICS system) gives rise to a different list of available Notes. For a full description of Note Lists and the Notes provided, see Note lists on page 146. (These Notes are the same as those produced from the Dump Menu with Note List commands; see Dump Menu (DMENU) displays on page 126.)
A list of procedural language (REXX API) EXECs available to the user. (For an example of the display and full description, see Running an EXEC on page 153.)
From the Traces pull down menu. (See CICS Trace Table displays on page 118 for details.) From the Help pull down menu (see page 54), a tutorial on DUMPMASTER commands. Most commands are described in Dump inspection commands on page 173; Note List commands are described in Note List commands on page 148.
158
CHAPTER 4
159
CHAPTER 5
Chapter 5
Working with VPAM program listings online
From the DUMPMASTER Initial Menu, the VPAM - View/print program listings options allow online access to higher-level-language program listings used by DUMPMASTER in source-language-oriented problem diagnosis. From the resulting displays, specified listings can be browsed, printed, or deleted. For details, please refer to the following topics:
I
Overview on page 160 Program Listings Entry displays on page 161 Program Listings Index panel on page 164 Confirming listing deletion on page 166 'Own VPAM' establishing individualized VPAM listing archives on page 167
Upgrading pre-V5.310 VPAM datasets VPAM compilation listings datasets prior to V5.310 and from V5.310 and higher cannot be used interchangeably. Consequently, you need to upgrade your existing pre-V5.310 VPAM datasets to the new format, or devise a strategy to enable you to work with both the old (in read only mode) and new formats. For more information, see Working with pre-V5.310 VPAM datasets in the Technical Reference.
160
CHAPTER 5
Overview
Overview
Higher-level-language program listings, which are used by DUMPMASTER in sourcelanguage-oriented problem diagnosis, are stored in a listing dataset at compilation time. Online access to these program listings is provided by the VPAM View/print program listings entries (Options 5 and 6) on the DUMPMASTER Initial Menu.
Note
When inspecting a dump, DUMPMASTER supports program listings in several dataset formats. See Defining the listings search strategy on page 58 for a description of how to set the strategy for searching for program listings in one of several dataset formats.
In conjunction with batch facilities also provided, this is an effective means of preserving and managing program listings which are of long-term importance to an Installation. It relieves the need to hold information in printed form where it is exposed to potential loss or damage, and allows it to receive the same protection as other classes of data from external security systems. Printed hardcopies can be obtained easily whenever needed, without the need to recompile. Detailed online Help is supplied for accessing and viewing or printing program listings using this feature. Other facilities provided with the feature include program listing capture (already mentioned above) and listing library maintenance, which are described in the DUMPMASTER MVS Technical Reference.
CHAPTER 5
Program Listings Entry displays
161

To view, print, or delete listings online using an ISPF dialog, select either of the VPAM - View/print program listings options (5 or 6) on the DUMPMASTER initial menu:
I
Take option 5, VPAM - View/print program listings, to present an entry display which shows all listing datasets available to you. Take option 6, VPAM/F - View/print program listings with current criteria, to present an entry display which shows only those datasets which meet your current selection criteria.
See
For information on
Program Listings Entry display (without selection criteria) Program Listings Entry display (with selection criteria)
Note
below page 162
For either type of display, if you select a dataset which contains multiple entries then, for the selected dataset, you will be presented with an index panel from which to select the particular listing desired. For more information, see Program Listings Index panel on page 164.
Program Listings Entry display (without selection criteria)

This display lists all the VPAM program listings datasets available to you.
Command ===> DUMPMASTER - Listing Datasets
Tab to listing dataset to be browsed and press ENTER. Listing Dataset Name . 'XYZ.VPAM.COBOL' . 'ABC.VPAM.COBOL' . 'DM.TESTS.VPAMFILE' . 'VPAM.USER.LISTINGS' . None of the above ****************************** Bottom of data ***********************************
To select an entry, either Point and Shoot on the indicator to the left of the desired dataset name, or key an S or an s (select) on the indicator and press the Enter key. A list of the program listings contained in the selected dataset will be produced, from which the desired listing can be selected. In the (unlikely) event that the dataset is not displayed, select the None of the above entry. A display on which the name of the desired dataset may be entered will be produced. (This is the same as the display with selection criteria see below.)
162
CHAPTER 5
Program Listings Entry display (with selection criteria)

This display shows only those datasets which meet your current selection criteria:
DUMPMASTER Program Listings Online Command ===> Listing Dataset From Listing Name To Listing Name ===> XYZ.VPAM.COBOL ===> ===>
- To select a single listing, complete ONLY the 'From' field. - To select a range of listings, complete both 'From' and 'To' fields. - To select all listings, blank out BOTH 'From' and 'To' fields. Action Earliest Date ===>B ===> P (Print) or B (Browse) ddmmyy format, e.g. 21Mar97
With Option P (print) only: Destination Class Forms ===> LOCAL ===>A ===>
Key-in or overtype fields as necessary, then press the ENTER key to execute. Enter the END command to exit without taking action.
On this display, the only required entry is the name of the listing dataset. For the dataset, the user may additionally specify one specific listing, a range of listings, or all listings to be viewed or printed:
I
To select a single listing, key its name in the From Listing Name field and leave blank (or blank out) the To Listing Name field. To select a range of listings, key-in the name of the listing which starts the range in the From Listing Name field and the name of the listing which ends the range in the To Listing Name field. (Listings are stored by name in ascending order.) Partial names formed from the beginning letter(s) of a name may be used, that is ABC references all listings with names beginning ABC. If the From Listing Name is left blank, the range will include all listings from the start of the dataset through the listing named in the To Listing Name field. To select all listings, leave blank (or blank out) both the From Listing Name and To Listing Name fields.
Selection of all or a specified range of listings may be further qualified by specifying a date in the Earliest Date field. Such dates must be in mm/dd/yy format, for example 03/22/99. Only listings bearing that or a later date will be selected. Either of two actions may be specified for the listing(s):
B (Browse, the default action)
The action depends upon the number of listings selected. Single listings are displayed immediately for online viewing with the ISPF browse facility. For multiple listings, a scrollable index display of their names is presented see Program Listings Index panel on page 164. When a listing is selected for browsing, the ISPF/PDF Browse service is invoked. All facilities normally associated with this service can be used to manipulate the listing being viewed. (When browsing is complete, issue the END command to return to the Program Listings Online display.)
CHAPTER 5
163
P (Print)
Prints the specified listing(s). The Destination (a specific printer or network node), output Class, and Forms code may be keyed in the Print option fields, or the defaults used. (Keying a blank or null entry for Destination or Class causes the default(s) to be restored.) When a listing is selected for printing, the output is immediately available for processing; it is unnecessary to logoff from the TSO session to release it. Multiple print requests entered simultaneously are batched together as a single output element.
164
CHAPTER 5
Program Listings Index panel

This display is presented when there are multiple listings contained in a VPAM program listings dataset.
Command ===> Listing Dataset DUMPMASTER Program Listings Online ===> XYZ.VPAM.COBOL
Dest: LOCAL Class: A Forms: 1PRT Enter: B Browse D Delete P Print Listing Lang Compile/Capture No. No. Printed Name Type Date Time Type Pages Lines Date . PAYROLL1 COB 21MAR97 12.29 D 0122 11 355 26MAR97 . PAYROLL1 COB 22MAR97 10.11 S 12 378 27MAR97 . ACCTPBL3 COB 24MAR97 11.47 D 0122 23 692 24MAR97 . PAYROLL1 COB 27MAR97 10.56 D 0153 12 379 27MAR97 ******************************* Bottom of data **********************
In addition to selecting listings for browsing, this display can be used to locate, print, and delete listings, and to sort the listings index itself. Each listing selected is shown by name, together with its language code, date and time of compilation, type of listing, number of pages and lines, and the date it was last printed. (The Index is scrollable if necessary.) Three types of listing may be shown: C, S, and D nnnn. These signify: C A listing which DUMPMASTER has not associated with a particular dump. The Compile/Capture Date and Time shown is that recorded in the listing. S A listing which DUMPMASTER has not associated with a particular dump. The Compile/Capture Date and Time shown is that when the listing was captured, as this could not be determined from the listing itself. D nnnn A listing which is associated with a particular dump number nnnn. Panel functions are available via primary and line (prefix) commands.
Program Listings Index primary commands Program Listings Index line commands
below page 165
Program Listings Index primary commands

Primary commands for the Program Listings Index are entered on the Command line at the top of the display. They select listings for browsing or printing, sort the index, and control printing output.
CHAPTER 5
165
B xxxxxxxx
Displays the listing named xxxxxxxx for browsing with the ISPF browse facility.
C|CLASS=x
Changes the output class for printed listings to x. When x is entered as null or blank, the default class is restored.
D|DEST=xxxxxxxx
Changes the destination for printed listings to the specific printer or network node xxxxxxxx. When xxxxxxxx is entered as null or blank, the default destination is restored.
F|FORMS=xxxx
Changes the forms code for printed listings to xxxx. When xxxx is entered as null or blank, the FORMS= field is blanked out.
L xxxxxxxx
Positions the display at the listing named xxxxxxxx. Partial names may be used. This command is most useful when the Index has been sorted by name (see SN below).
P xxxxxxxx
Prints the listing named xxxxxxxx.

SD
Sorts the Index by date/time (latest first).

SL
Sorts the Index by language code (ascending alphanumeric order).

SN
Sorts the Index by listing name (ascending alphanumeric order). This is the default Index order.
Program Listings Index line commands

Line (or prefix) commands are entered in the line command field adjacent to the listing names on the Index. Multiple line commands may be keyed-in before the Enter key is pressed, in which case they are executed in sequence from the top of the Index. These commands provide for browsing, printing, or deleting listings.
B
Browses the listing, using the ISPF browse facility.

D
Deletes the listing. A confirmation panel is first displayed see Confirming listing deletion on page 166.
P
Prints the listing.
166
CHAPTER 5
Confirming listing deletion
Confirming listing deletion

No listing can be deleted from the listing dataset without that action first being confirmed. A typical example of the display that is presented is shown below.
Command ===> DUMPMASTER Program Listings Online
Deletion Confirmation Listing Name : ACCTPBL3
Listing Dataset: XYZ.VPAM.COBOL
Press the ENTER key to confirm deletion of this listing. Enter the END command to cancel this request.
When this display is presented, either press the Enter key to confirm the deletion or issue the END command to cancel the deletion request. Note that the deletion is not merely from the Index display, but from the actual listing dataset. Once deleted, the listing is unrecoverable.
CHAPTER 5
'Own VPAM' establishing individualized VPAM
167
'Own VPAM' establishing individualized VPAM listing archives

In centralized organizations, all captured program listings usually are stored in one or more datasets which are shared by and generally accessible to all DUMPMASTER users. However, in a more distributed organization, it may be desirable for institutional reasons, or to provide greater efficiency, to give users individualized sets of program listings specific to them. This option is described in detail in Establishing individualized VPAM listing archives in the DUMPMASTER MVS Technical Reference.
168
CHAPTER 5
'Own VPAM' establishing individualized VPAM
169
CHAPTER 6
Chapter 6
Glossary
AAServer
Short for Application Availability Server. A separate long-running DUMPMASTER MVS Started Task that has its own configuration. It provides a variety of services such as producing an Instant Print (a summary report that is integrated into the failing jobs output), retrieving compilation listings which are held in a remote repository, and so on.
The primary DUMPMASTER analytical display; the first display presented to the user once a specific dump is selected. High-level and process-oriented, its contents are dynamically determined by the type of program, type of environment, and the program environment in which the dump occurred.
Abnormal Termination Exit (ATE)
An exit that is invoked at termination for unhandled error conditions.

Current address
The address at the top of the address column of the Dump Display screen.
Current area
An area of storage which may be either a storage area or a storage subarea. It is the whole area which DUMPMASTER is currently displaying.
Current Display List
A dynamically-maintained list of displays generated as a result of Point and Shoot operations; also known as a display of displays. The displays are stored so they may be re-called without regeneration during the life of a session. The list is obtained by entering the DISPLAY command on the Command line.
Dataspace
Used by an AAServer, a Dataspace is a special type of address space which is used as a repository for data. A Dataspace does not include the common areas in its virtual storage, and machine instructions cannot be executed from it.
170
CHAPTER 6
Glossary
DB2 bind
The process by which output from the DB2 precompiler (the DBRMs) for an application is converted to a usable control structure called a Package or an application Plan, which is stored in the database. During the Bind process, access paths to the data are selected and some authorization checking is performed.
DB2 package
A structure created from the Bind of DBRMs (see DB2 Bind).

DB2 plan
The structure created from the Bind of DBRMs or the Bind of collections of DB2 Packages. It is used by DB2 to process SQL statements when the application is run.
Dump Display
The screen of the Dump Inspection Facility which displays the dump in hexadecimal and interpreted format.
Dump Display functions
The collection of screens of the Dump Inspection Facility which assist in debugging the dump. For example the Note Lists, the Dump Display and the Dump Menu.
Filtering parameters
Parameters used on the statements input to the Dump Management Facility. They determine the scope of the functions and are equivalent to the Dump Selection fields.
Minimal address space dump
This sort of dump, which offers greater speed of capture, consists only of selected storage blocks. It will usually include all active programs and programrelated dynamic storage normally sufficient to support complete COBOL or PL/I program listing analysis. However, a minimal dump does not capture DB2, IMS, I/O summary, or GRS (ENQ/DEQ) information.
Note
A name associated with an address for fast access to the address. DUMPMASTER defines System Notes. User Notes are defined using the NOTE command.
Period (Full Stop)
A character (.) which marks the end of a declarative sentence or serves to indicate a decimal, also used on DUMPMASTER displays to indicate a singlecharacter data entry field or Point and Shoot target.
Point and Shoot
A facility which permits a user to position the cursor on a desired field or indicator (point) and press the Enter key (shoot) to obtain diagnostic information, often in a dynamically generated display.
CHAPTER 6
Glossary
171
Point and Shoot field
A field such as an abend code, address, and so on, on a Dump Display to which a user can tab, that is point, and then press Enter, that is shoot, to obtain further diagnostic information.
Point and Shoot indicator
A period or full stop (.) on a Dump Display to which a user can tab, that is point, and then press Enter, that is shoot, to obtain further diagnostic information. Each indicator has a descriptive title appended to identify the resulting display.
Scheme
A structure in the configuration of an AAServer that defines how data sources (remote listings repositories, and so on) are accessed.
Storage area
A block of contiguous storage and of any length. The beginning of each area has a System Note associated with it.
Storage subarea
A logically complete area of storage which has been selected within a storage area by DUMPMASTER.
Subsystem (DUMPMASTER)
A DUMPMASTER subsystem, which is identified to MVS by its subsystem id, acts as a central source of dump information. Usually, there is just one subsystem, whose id is normally M4DM.
VPAM
The Virtual Partitioned Access Method, used for the AUXINFO file supplied on the distribution tape by Macro 4, and by DUMPMASTER in the capture and storage of higher-level language source program compilation listings.
Worker
When a request is made for data that resides on a particular (remote) system, a Worker STC is set up by the AAServer running on that (remote) system. It is the Worker that services the request; that is, it runs the actual programs and utilities required to obtain the required data.
172
CHAPTER 6
Glossary
173
A P P EN D I X A
Appendix A
Dump inspection commands
With the exception of Note List commands, which are described separately, Dump Inspection commands are detailed in the following sections, grouped functionally. See Conventions on page 8 for a description of the typographic conventions used.
Note
For a summary list of the commands in alphabetical order, please refer to Dump inspection command summary on page 195.
See
For information on Control Commands CANCEL QUIT DLIST RETURN DMENU TOGGLE END PREVIOUS QQUIT
page 174
Information Commands CMAC PSW DISPLAY SCREEN ENQS TRACE FORMAT VIEW INFO WHERE LEVEL
page 177
Positioning Commands BOTTOM POINTV GOTO POINTVH OFFSET TOP POINT POINTH POINTS
page 182
Set Commands DELETE NOTE ORIGIN REGS SETTASK
page 184
Search Commands FIND XFIND FINDR LNOT LOCATE LUP LUPNOT
page 187
Calculation and Conversion Commands CALC CD CH DECODE EXPAND FLOAT
page 190
174
APPENDIX A
Control commands
Control commands
See: CANCEL below DLIST below DMENU below END on page 175 PREVIOUS on page 175 QQUIT on page 176 QUIT on page 176 RETURN on page 176 TOGGLE on page 176
CANCEL
CANcel
Exit to the screen which invoked DUMPMASTER.
DLIST
DLIST
Display the Dump List.
DMENU
DMENU [selno]
Jump to a specific Note List or Information screen, where selno is the selection number assigned to the required option on the Dump Menu. (See Dump Menu (DMENU) displays on page 126.) The selno values are listed below.
Note
When DMENU is issued without a selection number, the Dump Menu is displayed; if a selection number is specified then the corresponding option screen is displayed without a display of the Dump Menu.
CICS Transaction Dump Menu
MVS Dump Menu
D - DISPLAY 0 - INFO 1 - PROGRAMS 2 - STORE 3 - I/O 4 - USERNOTE 5 - USERSTOR 6 - ENQS 7 - SYSTEM 8 - SUMMARY
D - DISPLAY 0 - INFO 1 -PROGRAMS 2 - STORE 3 - I/O 4 - USERNOTE 5 - TERMINAL
6 - TASK 7 - JOURNAL 8 - TDATA 9 - TRACE 10 - SYSTEM 11 - ERRORS 12 - SUMMARY
APPENDIX A
Control commands
175
CICS System Dump Menu
D - DISPLAY 0 - INFO 1 - ERRORS 2 - USERNOTE 3 - AI 4 - AP 5 - BF 6 - CC 7 - CP 8 - CS 9 - DD 10 - DLI 11 - DM 12 - DS 13 - DU
14 - FCP 15 - ICP 16 - JCP 17 - KE 18 - LD 19 - LM 20 - ME 21 - MN 22 - MRO 23 - PA 24 - PCP 25 - PCT 26 - PG 27 - PR 28 - RM
29 - SM 30 - SS 31 - STD 32 - SZ 33 - TCP 34 - TDP 35 - TI 36 - TMP 37 - TRACE 38 - TSP 39 - UEH 40 - US 41 - XM 42 - XRF 43 - XS
END
END
Exit to previous display or level of control (ISPF command).

Note
In a DUMPMASTER Dump Display, this is not to a previous view of the Dump Display, but to the display prior to the Dump Display itself.
PREVIOUS
PREvious
Return to the immediately-previous display or, if navigating in a DUMPMASTER Dump Display, to the immediately-previous view of the Dump Display itself, if any Examples: Assume the current Dump Display is of a program, but it would be useful to see the Dump Display for the Note R13, and then continue debugging with the original display. Enter R13; once that storage has been viewed, enter the PREVIOUS command to re-display the Dump Display for the original program. If, in the original program display, Point and Shoot is executed on an address, then UP, DOWN, and +20 commands, and, finally, another Point and Shoot on another address, each action produces a different view of the Dump Display. If repeated PREVIOUS commands are then issued, each presents the immediately-previous view of the Dump Display, that is the one prior to the second Point and Shoot, then the one prior to the +20, and so on. Note that, at any point, further commands may be issued or Point and Shoot operations executed to continue exploration of the dump.
176
APPENDIX A
Control commands
QQUIT
QQuit
Exit to the screen which invoked DUMPMASTER. (Equivalent to the ISPF RETURN command, also recognized by DUMPMASTER; see RETURN below.)
QUIT
Quit
Exit to the previous display or level of control. (Equivalent to the ISPF END command, also recognized by DUMPMASTER; see END on page 175.)
RETURN
RETurn
Exit to the screen which invoked DUMPMASTER (ISPF command).
TOGGLE
TOGGLE
Issue either the ISPF PFSHOW ON or PFSHOW OFF command. The TOGGLE command is most effective when it is assigned to a PF Key.
Note
The ISPF PFSHOW command affects both screens when operating in split screen mode.
The ISPF command issued depends on whether the PF Key display is currently on or off. If no PF Keys are displayed TOGGLE simulates the PFSHOW ON command and the PF Key labels are displayed; if the PF Keys are currently displayed, TOGGLE simulates the PFSHOW OFF command and the PF Key labels are removed from the display. The actual values of the PF Key labels are set up using either the PF Keys Setup option (see PF KEYS PF Key Definitions and Labels display on page 24) or the ISPF KEYS command.
APPENDIX A
Information commands
177
See: CMAC below DISPLAY below ENQS on page 178 FORMAT on page 178 INFO on page 179 LEVEL on page 180 PSW on page 180 SCREEN on page 181 TRACE on page 181 VIEW on page 181 WHERE on page 181
CMAC
CMAc [transaction-abend-code|message-id]
Display the information relating to the CICS transaction abend code, or CICS message id. The information is retrieved from the IBM supplied CMAC file. For example:
CMAC AICA CMAC DFHSR0001
Shows information for the AICA abend. Shows information for the DFHSR0001 message.
If CMAC is entered without an operand, DUMPMASTER retrieves and displays information for the specific transaction abend for the dump being viewed. If the displayed information contains references to messages or abend codes, further information can be displayed for these using the Point and Shoot facilities. Place the cursor on the message id or abend code and press Enter.
DISPLAY
DISplay [display-name [starting-row]]
This command can be used online to produce a particular character-oriented display or a display of displays (the Current Display List) which lists all of the character-oriented displays currently available.
display-name is the same as store-name under which a character-oriented display was stored by a previously-executed DMSTORE function. (See the
DUMPMASTER MVS Technical Reference manual for details.) This name can be up to 17 alphanumeric characters, including the underscore (_).
starting-row is an integer specifying the row in the target data array at which display is to begin.
Note that many character-oriented displays are dynamic, being produced as a result of Point and Shoot operations. As these are generated, they are preserved and added to the Current Display List, or display of displays. This avoids the delay of regeneration.
178
APPENDIX A
Current Display List This can be obtained by entering the DISPLAY command on the Command line with no parameters; various displays then can be selected from the list for viewing. A particular display also can be viewed by entering the DISPLAY command on the Command line with the display name as a parameter. A description of how to use the DISPLAY command in conjunction with M4REXX EXECs is contained in Using procedural language (REXX API) on page 153.
ENQS
ENqs
In the MVS, that is address space dump environment, display the Enqueue List, a list of all global and local resource enqueue requests issued by an abending address space which are held or waiting. (See Enqueue list on page 134.)
FORMAT
FOrmat dataarea
Display the Format Display for the data from current address using the format of the control block specified in dataarea, which must be one of the following:
Code AID CSA DCT DWE EIB FCTE FPF ICE JCTTE OPFL OSPWA PCT PPT QEA RSA SIT SRSDEFN SYSTCA TACB Description
Auto initiation descriptor Common system area Destination control table Deferred work element EXEC Interface Block FCT entry FCT attributes and prefix Interval control element JCT entry CSA optional features list BMS work area Program control table Program processing table Queue element area Register save area System initialization table Series definition table System area of the TCA Transaction abend control block
APPENDIX A
179
Code TCA TCTTE TS TSUTE VOLDSCR
Description
User area of the TCA TCT terminal entry Temporary storage I/O area TS unit table entry Volume descriptor
For each significant field of the data area, the Format Display provides the name, offset, data type and contents of the field. Where possible, DUMPMASTER interprets the value of the field it is formatting. For example, the FORMAT FCTE command is issued for an FCT entry in a CICS dump. The Format Display for the FCT is shown in the following figure.
Command ===> Formatted Control Block FCTE Scroll ===> CSR
*********************** Start of Formatted Control Block ********************* FILE CONTROL TABLE ENTRY +000 FCTDSID C'DFHCSD ' +00A FCTDSVR1 X'BA' = READ VALID = UPDATE VALID = ADD VALID = DELETE VALID = BROWSE VALID = DATASET IS OPEN +00B FCTDSVR2 X'0A' = VARIABLE LENGTH RECORDS = BLOCKED RECORDS +008 FCTDSTEL X'00CC' +00F FCTDSRSL X'00' +00C FCTDSVR3 X'80' = VSAM DATASET +00D FCTDSVR4 X'00' +00E FCTDSTAT X'02' = DATASET DISABLED
INFO
Info [ASM]
When entered without the optional ASM operand, the INFO command automatically presents an Abend Summary Display. The content of the generated ASD will depend upon the type of dump concerned; for example, see ASD for COBOL on page 73 and ASD for Assembler on page 98. When entered with the optional ASM operand, the INFO command automatically presents a formal, hexadecimal or Assembler-oriented display; see System View display on page 117. In a high-level process-oriented environment, if source language compilation information is unavailable, a more hexadecimal-oriented display is presented. Notes are generated by DUMPMASTER during the processing for an Abend Summary Display. These have a description of User Defined Note on the Note List, and appear on the USERNOTE Note List.
180
APPENDIX A
Assembler environments
For these dumps, DUMPMASTER generates the following Notes to assist in debugging:
INS OP1 OP2 Batch
The failing instruction. The first storage operand. The second storage operand.
If the abend occurs while a request for a system service is being processed the following Note is generated:
LINS
The last instruction from the program which issued the system service request.
CICS
If the abend occurs while a request for a CICS service is being processed the following Note is generated:
LINS
The return address of the CICS service call.
Additionally, the following Notes may be generated for CICS:

TACB TWA EIB COBOL and PL/I
Transaction Abend Control Block. Transaction Work Area. EXEC Interface Block.
For these dumps, DUMPMASTER generates a number of Notes with a Subnote of COBOL or PL1 to assist in debugging the dump.
LEVEL
LEVEL
Display the current DUMPMASTER version and modification number in the short message area.
PSW
PSW [ORIG]
Display the PSW. If PSW is entered without an operand, the command displays the PSW at the time of the abend. The message:
PSW at time of abend = 'psw'
is produced in the long message area. If PSW ORIG is entered (for a CICS recursive abend), the message:
PSW at time of original abend = 'psw'
is produced in the long message area. The INS Note is always set to the instruction address portion of the PSW.
APPENDIX A
181
SCREEN
SCReen
(For CICS only.) Unless this facility has been disabled in the configuration (see the CUSTOM statement in the DUMPMASTER MVS Technical Reference), issue this command to display the CICS failing screen for transaction abends. (You can also display this screen from the CICS Summary display see page 91.) The display can be scrolled up and down, left and right.
TRACE
TRace
Use this command to access the CICS Application Trace Display. This display is described in CICS Application Level Trace display on page 118.
VIEW
VIEW note [subnote]
Displays text dump Note information when such information is available.

note is a previously-defined Note. subnote is a previously-defined Subnote.
Example: VIEW SUMM_DUM The command is valid not only for CICS system dump Notes and Subnotes, but for all dumps where text Note information is available. For example, in the case of a CICS transaction dump, the Note could be PROG_INF, TRAN_INF, and so on, and the Subnote, SUMMARY. Likewise, for non-CICS dumps the note could be the failing program name and the Subnote LINKINFO, IDRINFO, and so on, depending upon the information available. The text provided is viewed with the ISPF/PDF BROWSE function; all BROWSE commands are supported. When no text is available, the following message is issued:
No text to display
WHERE
Where [note [subnote]|regno|curraddr]
Display the module or area name and the offset within it of a selected address.
note is a previously-defined Note. subnote is a previously-defined Subnote. regno is any register in the range R0 R15 and RA RF. curraddr is the current address at the top of the address column of the display.
(In Dump Display only, the command will default to the current address if no operand is entered.) If the selected address lies within a program, the message:
Selected address is at offset nnnnnn in program xxxxxxx
is produced in the long message area. If the selected address lies within an area, the message:
Selected address is at offset nnnnnn in xxxxxxxx
is produced in the long message area.
182
APPENDIX A
Positioning commands
See: BOTTOM below GOTO below OFFSET below POINT on page 183 POINTH on page 183 POINTS on page 183 POINTV on page 183 POINTVH on page 183 TOP on page 183
BOTTOM
BOTTOM
Go to the highest address of the current storage area or subarea. If the current area is a storage area, issue the BOTTOM command to display the dump at the highest address of the storage area. If the current area is a storage subarea, issue the BOTTOM command to display the dump at the highest address of the storage subarea.
GOTO
GOTO
Make the address or the address associated with a program name current address and display the dump.
Note
This command has been retained only for compatibility with previous versions of DUMPMASTER. It has been superseded by the Point and Shoot facility.
The GOTO command is most effective when it is assigned to a PF key. Many of the fields on the Abend Summary, System View of Failure, Enqueue List, and Trace displays are unprotected, as are all of the dumped areas and registers on the Dump Display, for use with this command. The GOTO command may be used on any unprotected address or program name in the Dump Display Function.
OFFSET
Offset hexoffset
Make the current address the current Origin plus the hexadecimal offset, hexoffset, and display the dump.
hexoffset should not be less than the minimum offset for the current area and should not be greater than the maximum offset for the current area.
APPENDIX A
183
POINT
Point
This command, which is only available from the Dump Display, displays the dump at the address pointed to by the fullword at current address. The POINT command takes the fullword at current address and uses it as a pointer to the address which is to be displayed. Using this command pointers may be easily followed without the risk of miskeying an address. For example: Entering R1 then POINT goes to the address contained in Register 1 then to the address that is found there. This provides an easy way of getting to calling parameters where R1 points to the list of parameter addresses.
POINTH
POINTH|PH
This command, which is only available from the Dump Display, displays the dump at the address pointed to by the halfword at current address. The POINTH command takes the halfword at current address and uses it as a pointer to the address which is to be displayed.
POINTS
POINTS|PS
This command, which is only available from the Dump Display, displays the dump at the address pointed to by the first two bytes at current address. The address is resolved as an S-type constant, bddd (where b is base and ddd is displacement), based on the current register contents.
POINTV
POINTV|PV
This command, which is only available from the Dump Display, displays the dump at the address which results from adding the fullword at Current Address to Current Address.
POINTVH
POINTVH|PVH
This command, which is only available from the Dump Display, displays the dump at the address which results from adding the halfword at current address to current address.
TOP
TOP
Go to the lowest address of the current storage area or subarea. If the current area is a storage area, issue the TOP command to display the dump at the lowest address of the storage area. If the current area is a storage subarea, issue the TOP command to display the dump at the lowest address of the storage subarea.
184
APPENDIX A
Set commands
Set commands
See: DELETE below NOTE below ORIGIN below REGS on page 185 SETTASK on page 186
DELETE
DELete note [subnote]
Remove an obsolete user Note. The operand note is a previously defined Note. The operand subnote is a previously defined Subnote.
NOTE
Note note [subnote]
Make a Note at Current Address. This command, which is only available from the Dump Display, associates the note with current address. note must be unique and subnote is used to provide further clarification of what the Note represents.
note and subnote are names composed of any alphanumeric characters (A Z, 0 9) and may be 1-8 characters long. However, the name of the Note must
not be equivalent to any form of a DUMPMASTER command or System Note (although the Subnote name may be if desired). The Note may be used subsequently as a command to redisplay the storage at that address. When a Note is made, the hexadecimal fullword at the address where the Note has been made is highlighted. Where space allows, the name of the Note is displayed in the Note area. Generally if more than one Note has been made on a line the first Note which represents the lowest address on that line is displayed. The USERNOTE command (see Note List commands on page 148) may be used to list all the user Notes.
ORIGIN
ORIGin [*|address|note [subnote]|register|RESET]
This command, which is only available from the Dump Display, sets the value of Origin. The default value is ORIGin *. Origin is the base address from which the Offset column is calculated. Either the note and subnote name associated with the address of the current value of Origin, or the actual address, is displayed on the right side of the Dump Display above the dumped area. When the ORIGIN command has been used the value remains associated with that storage area or subarea while the dump remains selected for debugging or until the ORIGIN RESET command is issued for that storage area or subarea.
APPENDIX A
Set commands
185
* (asterisk) is used to represent current address. When it is entered, the address
at current address is displayed as the Origin. The Offset column is recalculated from this base address.
address may be any address in the range 0 FFFFFFFF. note and subnote may be any system or user Note. The register may be any register R0 R15, RA RF. RESET instructs DUMPMASTER to restart its automatic Origin setting for the current storage area or subarea.
For example: A data area is being viewed within a program. It would be useful to change the Offset column so that the offsets are from the beginning of the data area rather than the beginning of the program. A user Note of DATA1 AREA has been made at the beginning of the data area so:
ORIG DATA1 AREA
resets the Origin from the beginning of the program to the beginning of the data area.
REGS
REGs *|regno [toregno]|ORIG|PRB|RESET|SAVE
Alter the values of the registers while the dump remains selected for debugging. DUMPMASTER automatically sets the registers to their values at the time of the abend.
Note
The REGS command is normally only available from the Dump Display. However, REGS PRB, REGS ORIG and REGS RESET may be entered at any time once a dump has been selected.
* (asterisk) instructs DUMPMASTER to load all the registers in the order R0 R15, with the data at current address. regno and toregno, which may be any register in the range 0 15, are used to load all or some of the registers from current address. When regno and toregno are used, DUMPMASTER loads the range of registers with successive
fullwords starting from current address.

ORIG is used to set the registers to their values at the time of the original abend, when a CICS recursive abend has occurred. PRB loads all the registers from the most recent PRB. RESET reloads the registers with the registers at the time of the abend. SAVE sets the registers based on the data at current address. It is assumed to be a standard format save area. Current address becomes R13; R14 R12 are loaded from current address + X'0C'.
For example: To load registers 6 9 from current address, issue the command:
REGS 6 9
DUMPMASTER takes the four fullwords from current address and loads them into registers 6, 7, 8 and 9. The other registers are unaffected.
186
APPENDIX A
Set commands
To load registers 0 15 starting from register 4, issue the command:

REGS 4 3
DUMPMASTER takes the sixteen fullwords from current address and loads them into register 4 15 and 0 3.
SETTASK
SETTask [ALL|taskid]
Set the Task Filter value for Note Lists. The default value is SETTASK ALL.
taskid is the CICS task id. ALL denotes all tasks (no filtering is required).
The task filter determines which Notes are displayed in a Note List. The current value of the filter is displayed in the TASK field. DUMPMASTER will only create Note Lists from Notes which are associated with the currently selected task.
APPENDIX A
Search commands
187
Search commands
See: FIND below FINDR below LNOT on page 188 LOCATE on page 188 LUP on page 188 LUPNOT on page 189 XFIND on page 189
FIND
Find string [NEXT|PREV]
This command, which is only available in character-oriented Dump Displays, searches in the specified direction (in a character-oriented display, for example COBOL or PL/I) for the specified character string.
string, which must be delimited by quotes if it contains blanks or special characters, specifies a string of character data for which DUMPMASTER is to search. The search is not case-sensitive, and stops when string is matched or end-of-data is reached. NEXT|PREV is an optional parameter specifying the direction of the search, either forward by NEXT or backward by PREV through the data. The default value is NEXT.
FINDR
FINDR
This command, which is only available in character-oriented Dump Displays, repeats the immediately-prior FIND command, searching in the same direction for the same string. This command is most effective when it is assigned to a PF key. The FIND command searches character-oriented displays, for example COBOL or PL/I, in a specified direction, for data which matches a specified character string. Once a FIND command has been issued, FINDR can be used to repeat the search in the specified direction, that is when a target string is located, it can be used to search for the next instance. If the FINDR target is not found between its instance on the screen and the bottom of the data then the following message is displayed:
Bottom of Data
and the display is left unchanged. Entering FINDR again then will begin the next search at the top of the data. The display is changed only if the target is found outside that portion of the data displayed on the screen.
188
APPENDIX A
Search commands
LNOT
LNot [']schar
This command, which is only available in hexadecimal-oriented Dump Displays, searches forward for data not equal to the specified hexadecimal or character data. The LNOT command searches addresses in the current storage area which are higher than current address for data which is not equal to the keyed schar. The search starts one byte after current address. When the data is found it is positioned at current address.
' (apostrophe) indicates that schar is in character format. There should be no space between the ' (apostrophe) and schar. schar is the hexadecimal or character data to be searched for. The maximum data length is one character. To search for a lower case letter, schar should be entered in hexadecimal.
LOCATE
Locate [']sdata
This command, which is only available in hexadecimal-oriented Dump Displays, searches forward for the specified hexadecimal or character data. The LOCATE command searches addresses in the current storage area which are higher than current address for the keyed sdata. The search starts one byte after current address. When the data is found it is positioned at current address.
' (apostrophe) indicates that sdata is in character format. There should be no space between the ' (apostrophe) and sdata. sdata is the hexadecimal or character data to be searched for. The maximum data length is 50 characters. To search for lower case letters, sdata should be entered in hexadecimal.
LUP
LUP [']sdata
This command, which is only available in hexadecimal-oriented Dump Displays, searches backward for the specified hexadecimal or character data. The LUP command searches addresses in the current storage area which are lower than current address for data which is equal to the keyed sdata. The search starts one byte before current address. When the data is found it is positioned at current address.
' (apostrophe) indicates that sdata is in character format. There should be no space between the ' (apostrophe) and sdata. sdata is the hexadecimal or character data to be searched for. The maximum data length is 50 characters. To search for lower case letters, sdata should be
entered in hexadecimal.
APPENDIX A
Search commands
189
LUPNOT
LUPNot [']schar
This command, which is only available in hexadecimal-oriented Dump Displays, searches backward for data not equal to the specified hexadecimal or character data. The LUPNOT command searches addresses in the current storage area which are lower than current address for data which is not equal to the keyed schar. The search starts one byte before current address. When the data is found it is positioned at current address.
' (apostrophe) indicates that schar is in character format. There should be no space between the ' (apostrophe) and schar. schar is the hexadecimal or character data to be searched for. The maximum data length is one character. To search for a lower case letter, schar should be
entered in hexadecimal.
XFIND
XFind
Search all or part of a dump for occurrences of hexadecimal or character search arguments, and display the result. This command produces a structured display for parameter input; see Extended Find facility on page 142.
190
APPENDIX A
Calculation and conversion commands

See: CALC below CD below CH on page 191 DECODE on page 191 EXPAND on page 194 FLOAT on page 194
CALC
Calc operand operator operand
Calculate the result of a hexadecimal arithmetic expression.

operand is a hexadecimal value, a Note, or a register. A * (asterisk) may be
used to represent Current Address.

operator may be + (add), - (subtract), * (multiply), or / (divide).
The hexadecimal arithmetic expression must consist of two operands separated by a single operator. The following Notes are generated by the CALC command:
ANS24 ANS31
The result using 24 bits of the three low-order bytes in the calculation. The result using all 32 bits.
CD
CD value
Convert value to decimal.

value is a hexadecimal value in the range 0 FFFFFFFF, the address
represented by a Note or a register. This command will convert the value using 24 bits and 32 bits where appropriate. The results are shown in the long message area in one of two formats:
'hexvalue' CONVERTS TO DECIMAL 'decvalue'
or
'hexvalue' CONVERTS TO DECIMAL '24value' OR '32value'
For example: If you enter this command:

CD F16
then the result shown will be:

'F16' CONVERTS TO DECIMAL '3862'
If you enter this command:

CD 02200f78
APPENDIX A
191

'02200f78' CONVERTS TO DECIMAL '2101112' OR '35655544'
CH
CH decvalue
Convert decvalue to a hexadecimal address.

decvalue is a decimal value; the maximum decimal value which can be converted is 2147483647.
For example: If you enter this command:

CH 35655544

'35655544' CONVERTS to HEX '02200F78'
The following Note is generated by the CH command:

HEX
The value in hexadecimal.
DECODE
DECode
This command, which is only available from the Dump Display, disassembles the contents of a block of storage at the current address. The DECode command causes two dynamic displays to be produced:
a b
An input display for entry of optional user modifications to the default disassembly. An output display of the disassembled block of storage specified by the input display.
See
For information on
Disassembler input display Disassembler output display Specifying register use Disassembler input display
An example of the input display appears below:
192
APPENDIX A
Command ===>
DUMPMASTER DisAssembler
Scroll ===> CSR
Use the DisAssembler to display storage as Basic Assembler Language statements Start Address OR Note Name : 059066F4 Hex address OR valid note name Decompile length : 100 Hexadecimal Display handle (optional) : DASSEN_059066F4 As in Current Display List Register usage (optional) Select Set to P to select for program base, D for DSECT base Register Overwrite with actual base register number (1-15) Base Overwrite to correct base address if required R0 00184CA4 R1 00184EA8 R2 00000000 R3 00000000 R4 0018942F R5 00000771 R6 0018AB80 R7 00188B80 R8 0014CD10 R9 00189B80 R10 05904144 R11 05905E4A R12 05904114 R13 00184B48 R14 859066E8 R15 00000000 Press ENTER to initiate disassembly. Enter the END command to quit.
Start Address OR Note Name This field initially contains the current dump address. This default may be overtyped with any valid address or Note or Subnote name. Decompile length The size (in hexadecimal) of the block of storage to be disassembled. Initially this value defaults to X'100' (256 bytes in decimal), but it may be overtyped. Subsequent displays take the length from the immediately-previous display. Display handle Enables you to assign a name to the display by which it may be recalled with the DISPLAY command (see page 177), that is the name in the leftmost column of the Current Display List. Initially this is a generated name based on the starting address; it may be overtyped if desired. Register usage This section enables you to specify register use and contents to make the disassembly output (see below) more meaningful. Through its use, base and displacement addresses in branch instructions can be replaced with labels which then are displayed if they are within the disassembled storage. Similarly, base and displacement addresses for DSECT references can be replaced with labels, in which case the disassembled instruction will be followed by a display of the contents of the storage so addressed. The 16 Register fields one for each register each consist of three parts:
a
A Select entry, indicated by _ (an underscore) to the left of the register number. Enter a P in this field to select this register as a program base. Enter a D to select it as a DSECT base. A Register entry (R0 R15). This may be overtyped with the name of another register, for example R2, or number (1 15, as Register 0 cannot be used as a base). To do so specifies that the DisAssembler is to use the following Base value as if it were the contents of the new register. (This may be easier than overtyping the Base entry itself; see below.) A Base entry, initially set to the registers contents at abend time or as of the last REGS command. This may be overtyped to change a base address.
See Specifying register use on page 194 for an example of the meaningful information which can be extracted from a dump by specifying register use.
APPENDIX A
193
Disassembler output display When you have made any desired modifications to the input display (see page 191), press Enter to start the disassembly. The selected block of storage is disassembled into BAL (Basic Assembler Language) statements producing an output display like the one shown in the following figure:
Command ===> Disassembly from 059066F4 Scroll ===> CSR
****************************** Start of display ****************************** . To dis-assemble preceding X'100' bytes Object Code 4920 A038 58B0 C028 47B0 B8C8 58B0 C02C 47F0 B728 58B0 47F0 5820 4920 47D0 C028 BA64 918C A038 B9B6 Label Op CH L BNM L B L B L CH BNH Operands R2,X'038'(,R10) R11,X'028'(,R12) X'8C6'(,R11) R11,X'02C'(,R12) X'728'(,R11) R11,X'028'(,R12) X'A64'(,R11) R2,X'18C'(,R9) R2,X'038'(,R10) X'9B6'(,R11) Notes
Address Offset 059066F4 000000 059066F8 000004 059066FC 000008 05906700 00000C 05906704 000010 [49 LINES OMITTED] 059067E0 0000EC 059067E4 0000F0 059067E8 0000F4 059067EC 0000F8 059067F0 0000FC .
To dis-assemble next X'100' bytes
**************************** End of display *******************************
At the top and bottom of this display, Point and Shoot indicators permit disassembly of the previous or next block of storage contents. (The size of the block was determined by the Decompile length specified on the input display.) Address The address of the instruction or data. Tab to this field and press Enter to view the Dump Display at this address. Offset The hexadecimal offset of the address from the lowest base address specified or, by default if there is none, from the start address. Label A label generated by the DisAssembler for the address or data field when, respectively, a program base or DSECT register was specified on input display. Op The BAL operation code. (Some codes may not be recognized; in particular, vector instructions are not.) Operands The usual hex-displacement (base-register) format is employed, unless the instruction uses a program base or DSECT register specified on the input display. In the latter case, the DisAssembler-generated label is shown. Notes The name of any DUMPMASTER or user-defined Note or Subnote against the address is shown here.
194
APPENDIX A
Specifying register use Shown below is an example of the meaningful information which can be extracted from a dump by specifying register use on the DisAssembler input display (see page 191). The block of storage represented is identical to that shown in Disassembler output display on page 193. However, on the input display, P (program base register) was specified for R11, while D (DSECT register) was specified for R10 and R12.
Command ===> Disassembly from 059066F4 Scroll ===> CSR
****************************** Start of display ****************************** . To dis-assemble preceding X'100' bytes Object Code 4920 A038 0000 58B0 C028 05905E4A 47B0 B8C8 5820 918C 4920 A038 0000 47D0 B9B6 Label DA038 DC028 LB99E DA038 Op CH DC L DC BNM EQU L CH DC BNH Operands R2,DA038 HL2'0' R11,DC028 XL4'05905E4A' LB8C6 * R2,X'18C'(,R9) R2,DA038 HL2'0' LB9B6 Notes
Address Offset 059066F4 0008AA 0590417C 059066F8 0008AE 0590413C 059066FC 0008B2 [79 lines omitted] 059067E8 00099E 059067E8 00099E 059067EC 0009A2 0590417C 059067F0 0009A6 .
To dis-assemble next X'100' bytes
**************************** End of display *******************************
Note the generated labels on this display.
EXPAND
EXPand
This command, which is only available from the Dump Display, converts the first byte at current address to binary. The result of the conversion is shown in the message:
HEX VALUE 'nn' EXPANDS TO BINARY 'nnnnnnnn'
which is shown in the long message area. For example: If the EXPAND command is used to check which bits are on for X'9C', the result of the command will be:
HEX VALUE '9C' EXPANDS TO BINARY '10011100'
FLOAT
FLoat
This command, which is only available from the Dump Display, converts the first eight bytes at current address to their decimal floating point equivalent. The result of the conversion is shown in the long message area.
APPENDIX A
Dump inspection command summary
195

In this section, commands are grouped alphabetically.
Alphabetical command groups See
A F prefixed commands G O prefixed commands P R prefixed commands S Z prefixed commands
below page 198 page 200 page 202
A F prefixed commands
AI Display the Auto-install model manager Note List. AP Display the Application domain Note List. BF Display the Built-in functions Note List. BOTTOM Go to the highest address of the current storage area or subarea. CALC
Calc operand operator operand
Calculate the result of a hexadecimal arithmetic expression. CANCEL

CANcel
Exit to the screen which invoked DUMPMASTER. CC Display the CICS catalog domain Note List. CD
CD value
Convert a value (hexadecimal value, a Note or a register) to decimal. CH

CH decvalue
Convert a decimal value to a hexadecimal address.
196
APPENDIX A
CMAC
CMAc [transaction-abend-code|message-id]
Display further information from the CMAC file for a CICS transaction abend code. CP Display the CPI static storage area Note List. CS Display the CICS common system area Note List. DD Display the Directory Manager domain Note List. DECODE
DECode
Disassemble the contents of a block of storage at the current address. DELETE

DELete note [subnote]
Remove an obsolete Note. DISPLAY

DISplay [display-name [starting-row]]
Display an informational array, or, when no display-name is specified, a display of all arrays currently available for display. DLI Display the CICS DL/I interface Note List. DLIST Display the Dump List. DM Display the Domain Manager Note List. DMENU
DMENU [selno]
Jump to a specific Note List or Information screen. DS Display the Dispatcher domain Note List.
APPENDIX A
197
DU Display the Dump domain Note List. END Exit to previous display or level of control (ISPF command). ENQS
ENqs
Display the Enqueue List. ERRORS

ERrors
Display the Errors Note List. EXPAND

EXPand
Convert the first byte at current address to binary. FIND

FIND string [NEXT|PREV]
Search in the specified direction (in a character-oriented display) for the specified character string. FINDR Repeat the immediately-prior FIND command, searching in the same direction (in a character-oriented display) for the same string. FCP Display the File control program Note List. FLOAT
FLoat
Convert the doubleword at current address to a decimal floating point value. FORMAT
FOrmat dataarea
Display the relevant Format Display.
198
APPENDIX A
G O prefixed commands
GOTO Make the address or program name the current address and display the dump. I/O
I/O|IO
Display the I/O area Note List. ICP Display the Interval control program Note List. INFO
Info [ASM]
Display a character or hexadecimal oriented Abend Summary Display. IO See I/O on page 198. JCP Display the Journal control program Note List. JOURNAL
JOurnal
Display the journal Note List. KE Display the CICS kernel Note List. LD Display the Loader domain Note List. LEVEL Display the DUMPMASTER version and modification number. LM Display the Lock manager domain Note List. LNOT
LNot [']schar
Search forward (in a hexadecimal-oriented display) for data not equal to the specified hexadecimal or character data.
APPENDIX A
199
LOCATE
Locate [']sdata
Search forward (in a hexadecimal-oriented display) for the specified hexadecimal or character data. LUP
LUP [']sdata
Search backward (in a hexadecimal-oriented display) for the specified hexadecimal or character data. LUPNOT
LUPNot [']schar
Search backward (in a hexadecimal-oriented display) for data not equal to the specified hexadecimal or character data. ME Display the Message domain Note List. MN Display the Monitoring domain Note List. MRO Display the CICS multiregion operation Note List. NOTE
Note note [subnote]
Make a Note at current address. OFFSET

Offset hexoffset
Make current address the current Origin + hexoffset and display the dump. ORIGIN
ORIGin [*|address|note [subnote]|register|RESET]
Set the value of Origin.
200
APPENDIX A
P R prefixed commands
PA Display the Parameter manager domain Note List. PCP Display the Program control program Note List. PCT Display the Program control table Note List. PG Display the Program manager domain Note List. PH See POINTH on page 200. POINT
Point
Display the dump at the address pointed to by the fullword at current address. POINTH
POINTH|PH
Display the dump at the address pointed to by the halfword at current address. POINTS
POINTS|PS
Display the dump at the address pointed to by the first two bytes at current address. The address is resolved as an S-type constant, bddd (where b is base and ddd is displacement), based on the current register contents. POINTV
POINTV|PV
Display the dump at the address which results from adding the fullword at current address to current address. POINTVH
POINTVH|PVH
Display the dump at the address which results from adding the halfword at current address to current address. PR Display the Partner resource manager Note List.
APPENDIX A
201
PREVIOUS
PREvious
Return to the immediately-previous display or, if navigating in a DUMPMASTER Dump display, to the immediately-previous view of the Dump Display itself, if any. PROGRAMS
PROgrams
Display the Note List for program Notes and their related control block Notes. PS See POINTS on page 200. PV See POINTV on page 200. PVH See POINTVH on page 200. PSW
PSW [ORIG]
Display the PSW. QQUIT

QQuit
Exit to the screen which invoked DUMPMASTER. QUIT

Quit
Exit to the previous display or level of control. (Equivalent to the ISPF END command.) REGS
REGs *|regno [toregno]|ORIG|PRB|RESET|SAVE
Alter the values of the registers. RETURN

RETurn
Exit to the screen which invoked DUMPMASTER (ISPF command). RM Display the Recovery manager Note List.
202
APPENDIX A
S Z prefixed commands
SCREEN
SCReen
(For CICS only.) Unless this facility has been disabled in the configuration (see the CUSTOM statement in the DUMPMASTER MVS Technical Reference), display the CICS failing screen for transaction abends. SETTASK
SETTask ALL|taskid
Set the task filter value for Note Lists. SM Display the Storage manager domain Note List. SS Display the Static storage areas Note List. STD Display the Statistics domain Note List. STORE
STore
Display the Note List for storage area Notes and their related system area Notes. SUMMARY
Summary [note] [subnote|COBOL|PL1]
Display a complete or selective Note List. SYSTEM

SYstem
Display the system area Note List, that is all Notes except those normally included in the PROGRAMS, STORE, and I/O Note Lists. SZ Display the Front end programming interface Note List. TASK
TAsk
Display the task-related Note List. TCP Display the Terminal control program Note List.
APPENDIX A
203
TDATA
TData
Display the transient-data-related Note List. TDP Display the Transient data program Note List. TERMINAL
TErminal
Display the terminal-related Note List. TI Display the Timer domain Note List. TMP Display the Table manager program Note List. TOGGLE Issue either the ISPF PFSHOW ON or the PFSHOW OFF command. TOP Go to the lowest address of the current storage area or subarea. TRACE
TRace
Access the CICS Application Trace Display. TSP Display the Temporary storage program Note List. UEH Display the User exit handler Note List. US Display the User domain Note List. USERNOTE
USERNote
Display the user Note List. USERSTOR

USERStor
Display a Note List combining the PROGRAMS, STORE and I/O Note Lists.
204
APPENDIX A
VIEW
VIEW note [subnote]
Display text information in a CICS system dump Note or Subnote (when text is provided). WHERE
Where [note [subnote]|regno|curraddr]
Display the module or area name and offset within it of a selected address. X Provide additional Note List information. XFIND
XFind
Search all or part of a dump for occurrences of hexadecimal or character search arguments, and display the results. XM Display the Transaction manager Note List. XRF Display the Extended recovery facility Note List. XS Display the Security domain Note List.
205
Index
Symbols
* EXPD * 36, 39, 40
Numerics
24 bit 136, 190 31 bit 136, 190 32 bit 190
A
A Action Code 38, 40 AAServer See Application Availability Server Abend Code displaying details 75 field of Dump Selection 27 generic 27 QuickRef Information Display 75 selecting dumps by 27 selecting system 27 selecting user 27 Abend Summary Display Assembler 73, 98 CICS system dump 73, 96 CICS transaction dump 73, 90 COBOL 73 DB2 73, 105 Examples of 73 Failing statement, Assembler 100 Failing statement, CICS 92 Failing statement, COBOL 74, 76, 77 Failing statement, PL/I 81 Fast Path facility, description of 41 Fast Path facility, invoking 41 Fast Path facility, setting up 41 Glossary entry 169
I/O Summary 131 I/O Summary, ACB 133 I/O Summary, DCB 132 I/O Summary, IAM 67 IMS 73, 105, 110 Language Environment (LE) 111 LINKEDIT information 74, 99 PL/I 73, 79 Purpose of 64 Selective Data Item, PL/I 83 Source language, COBOL 74, 76 Source language, PL/I 82 Abnormal Termination Exit (ATE) 169 Access to addresses 46 ACF2, see RACF Action bar, see Pull down menus Action Code A Action Code 38, 40 D Action Code 38, 38 E Action Code 38, 39 entering in Input Area 36 line command 36, 37 list of for Dump List 37 processing sequence 38 S Action Code 38, 40, 120, 124 using to view a dump 33 ACTIONS command 52 Address accessing 46 field of a Note List 147 Address Selection Display 136 Administrators Menu 43 Advanced Diagnostic Facilities Currently available displays 156 Description of 156 Extended Find Facility 142, 157 Note List generation 157
206
Index
REXX API execs 157 XFIND Command 142 Advanced pull down menu 52, 140, 142, 148, 153, 156, 157 AI Command 149, 195 Alter register values 137, 185 Altering expiry date of a dump online 37, 38 Ampersand (&) in Dump Inspection 138 retain a command 138 ANS24 Generated Note CALC Command 190 see also Generated Notes ANS31 Generated Note CALC Command 190 see also Generated Notes AP Command 149, 195 Apostrophe (') in a dump dataset name 28 in the LNOT Command 188 in the LOCATE Command 188 in the LUP Command 188 in the LUPNOT Command 189 Application Availability Server Glossary entry 169 name, default 24, 62 name, specifying 24 see also Remote listings support Application Trace Table Display see CICS Trace Table Displays Arithmetic expression 190 ASD, see Abend Summary Display Assembler Abend Summary Display 73, 98 Failing Statement Display, restrictions 105 Source Language Display, restrictions 105 Assembler listings check compile date 61 how DUMPMASTER searches for 61 Asterisk (*) Current address 190 in Dump Selection fields 27, 30, 31, 32 in the CALC Command 190 in the ORIGIN Command 185 in the REGS Command 185 in the SUMMARY Command 150 see also Special Characters Attributes, WebSphere MQSeries 115
Batch Dump List Column Option 22 BF Command 149, 195 Binary 194 Bind information, DB2 Bind process 106 DMBDB202 program 106 Glossary entry 170 Blks field of Dump List 36 BOTTOM Command usage 182, 195 see also Positioning Commands Bypassing the Dump List 25, 29
C
Calc. & Conv. Commands CALC Command 190, 195 CD Command 190, 195 CH Command 191, 195 DECODE Command 191, 196 EXPAND Command 194, 197 FLOAT Command 194, 197 CALC Command generated notes 190 usage 190, 195 see also Calc. & Conv. Commands Calculate CALC command 190 using 24 bits 190 using 32 bits 190 Call detail, WebSphere MQSeries 114 CANCEL Command usage 174, 195 see also Control Commands CA-Panexec support 74, 99 Capturing the job log 72 Case-sensitivity in the FIND Command 187 CA-Top Secret, see RACF CC Command 149, 195 CD Command example 190 usage 190, 195 using 24 bits 190 using 32 bits 190 see also Calc. & Conv. Commands Centralized Organization program listing archives 167 CH Command example 191 generated note 191 maximum value 191 usage 191, 195 see also Calc. & Conv. Commands Changing
B
Base address 185 BASED variable support, PL/I 83
Index
207
Value of Origin 184 CICS Abend Summary Display, system 73, 96 Abend Summary Display, transaction 73, 90 CICS generated notes 180 dump collection, see Dump collection, CICS Dump Selection 25 Failing Screen Display 92 Formatted control block displays 93 Program information 151 service call 180 Summary Display 91 Trace Table Displays, see CICS Trace Table Displays Transaction information 152 Versions supported by DUMPMASTER 13 CICS Trace Table Displays Application 118, 118 Application, displaying 118 Application, TRACE command 181 Full Trace Entry 118, 124 System 118, 120 System, displaying 120 System, Domain field 121 System, Function field 122 System, Progm field 122 System, specifying filters 123 System, Task field 121 System, TCB field 121 System, Type field 122 Types of 118 CICS TS See CICS CICS/ESA See CICS CMAC Command 177, 196 CMAC file information 75, 91, 177 COBOL Abend Summary Display 73 Failing Statement Display 74, 76 Failing Statement Display, Indexed array support 77 generated notes 150, 180 listings, see COBOL listings LOCAL-STORAGE support 77 Note List 150, 151, 202 Source Language Display 74, 76 System View Display 117 Versions supported by DUMPMASTER 13 COBOL listings check compile date/time 60, 61
confirming deletion of 166 dataset formats 58 dataset formats, setting 58 deleting online 160 how DUMPMASTER searches for 61 individualized VPAM archives 167 OEM repository 60, 70 OEM, selecting 60 PDS/PDSE 60, 69 pre-search prompt 60, 68 printing online 160 Program Listings Entry displays 161 Program Listings Index panel 164 Remote, see Remote listings support search options 58 search options, default 59 search strategy 58 specifying 68 viewing online 160 VPAM 59 Code (abend) field of Dump List 36 Column Option field (Batch Dump List) 22 Command area entering registers 137 of a Note List 147 of the Dump Menu 126 Command delimiter usage 49 see also Special Characters Command, specifying initial 23 Common System Area Display (CICS) 94 Compilation Listings OEM repository 60 OEM, selecting 60 PDS/PDSE 60 Remote, see Remote listings support search options 58 VPAM 59 Concatenate Commands usage 49 see also ISPF Confirm Deletion Display 22, 38, 38 Control blocks, CICS Formatted displays 93 Control Commands CANCEL Command 174, 195 DLIST Command 174, 196 DMENU Command 134, 174, 196 END Command 175 PREVIOUS Command 175, 201 QQUIT Command 176, 201 QUIT Command 176, 201 RETURN Command 176 TOGGLE Command 176, 203
208
Index
Convert to Binary 194 to Decimal 190 to Floating Point 194 to Hex 191 using 24 bits 190 using 32 bits 190 CP Command 149, 196 Creating a Note 184 Creation Date date ranges 28 CS Command 149, 196 Current address adjusting using hex offsets 138 changing 138 Glossary entry 169 setting the value of 129, 148 Current Area 169 Current Display List 50, 169, 177
D
D Action Code 38, 38 Datasets (DUMPMASTER) maintenance 12 Date field of Dump List 36 format (dump inspection) 21 format (Dump List option) 36, 38 selecting dumps by 27 DB2 Abend Summary Display 73, 105 Bind, DMBDB202 program 106 Bind, Glossary entry 170 Bind, Information 106 Package, Display 108 Package, Glossary entry 170 Plan, Display 107 Plan, Glossary entry 170 Summary Display 105 System View Display 117 Versions supported by DUMPMASTER 13 DD Command 149, 196 Decimal conversion to 190 conversion to Hex 191 DECODE Command usage 191, 196 see also Calc. & Conv. Commands DELETE Command usage 184, 196 see also Set Commands Deleting a dump online 37, 38, 38 Deleting Program Listings 160
Delimiting commands 49 Disassembler DECODE command 191 instructions 191 Display 24 or 32 bit addresses 136 Abend Code Info from QuickRef 75 Abend Summary 64, 169 Address Selection 136 Advanced Diagnostic Facilities 156 an address 184 Assembler Failing Statement, restrictions 105 Assembler Source Language, restrictions 105 CICS Failing Screen 92 CICS Summary 91 CICS Trace Table Displays, see CICS Trace Table Displays COBOL Failing Statement 76 COBOL Failing Statement, Indexed array support 77 COBOL Source Language 76 Common System Area (CICS) 94 Confirm Deletion 22, 38 DB2 Package 108, 170 DB2 Plan 107, 170 DB2 Summary 105 Dump 129 Dump List 33 Dump List Options 21 Dump Menu (DMENU) 126 Dump Selection 25 Failing Transaction 92, 181 I/O Summary 131 I/O Summary, ACB 133 I/O Summary, DCB 132 I/O Summary, IAM 67 IMS Region Diagnostics 110 Job Log 72 Language Environment Summary 111 Listing Choice 71 Listing Choice (PDS/PDSE) 69 Listing Choice (PDS/PDSE), input fields 69 Listing Search Options 58 Listing Search Options, input fields 59 Listing Selection (OEM) 70 Listing Selection (OEM), input fields 70 Macro 4 Diagnostics 156 PL/I Failing Statement 81 PL/I Failing Statement, BASED variable support 83 PL/I Failing Statement, restrictions 85, 87
Index
209
PL/I Selective Data Item 83 PL/I Selective Data Item, BASED variable support 83 PL/I Source Language 82 PL/I Source Language, restrictions 85, 87 PL/I Summary 84 QuickRef Matches List 75 Register 137 Select Formatted CICS Block 95 Session Setup 20 Storage 129, 184 System View 117 DISPLAY Command 177, 196 Distributed Organization program listing archives 167 DLI Command 149, 196 DLIST Command usage 33, 174, 196 see also Control Commands DM Domain Manager Notes Command 149, 196 Fast Path facility command 42 DMB170I message 41 DMB615I message 29 DMB616I message 29 DMBDB202 program 106 DMC170I message 41 DMC702I message 29 DMENU Command Jump to an option 174 usage 126, 134, 174, 196 see also Control Commands Domain field of System Trace Table Display 121 DOWN Command 49 DS Command 149, 196 DU Command 149, 197 Dump altering expiry date 38 deleting, online 38 expiring, online 39 exporting 12 hexadecimal format 129 importing 12 interpreted format 129 minimal address space 170 online access 12 overwriting 39 printing 38, 39, 141 selecting, online 25, 27, 28, 29, 30, 31, 32, 40 Dump collection, Batch facility 12 Dump collection, CICS
facility 12 Dump Dataset block usage by dumps 36 Deleting a dump from Dump List 37 Dump List display 33 field of Dump Selection 28 insufficient space 39 name, specifying online 28 selecting dumps by 28 Dump Date field of Dump Selection 27 Dump Display accessing from a Note List 148 description of 129 Fast Path facility, description of 41 Fast Path facility, invoking 41 Fast Path facility, setting up 41 fast path routes 25, 29, 41, 126 fields 129, 129 Glossary entry 170 Help Menu 139 non-display characters 130 Note area 130 Registers 137 repositioning 138 Dump Display Function Address Selection Display 136 Description of 46 Dump Display 129 Dump Menu 126 Enqueue List 134 Fast Path facility, description of 41 Fast Path facility, invoking 41 Fast Path facility, setting up 41 Fast path routes 25, 29, 41, 126 Glossary entry 170 Note List 146 Dump Export/Import facility 12 Dump File field of Dump Selection 25, 26 Dump Inspection Commands 173 Facility 12, 19, 46 Retained fields 25, 26 Dump List Action Code 36, 37 action code processing sequence 38 Blks 36 bypassing 25, 29 Code (abend) 36 Column Option field 22 Commands 37 Date 36 Description of 33
210
Index
Displays 33 DLIST command 174 Dump Number 29 Dump Selection displays 25 DumpNo 36 Dups 36 Errs 36 Expires 36 fields 36, 37 information line 33, 38 Input Area 36 Insufficient storage for dump 29 Jobname 36 line command 36, 37 Offset 37 Program 37 quick return to 174 refreshing 22 Selecting from Initial Menu 46 Stepname 37 Syst (system id) 37 Time 36 Userid 37 Xact (transaction id) 37 Dump List Options display Column Option field 22 Date Format 38 fields 21 List panel 20 Dump Management facility 12 Dump Menu accessing Dump Display 126 Displays (DMENU) 126 for CICS system dumps 128 for CICS transaction dumps 127 for MVS dumps 127 jump to an option 126, 174 returning to 126 Dump Number Address space abends 29 CICS system dumps 29 CICS transaction dumps 29 field of Dump Selection 29 finding out 29 selecting dumps by 25, 29 Dump Selection displays 25, 33, 46 fields 26, 27, 28, 29, 30, 31, 32 for CICS dumps 25 for MVS dumps 25 Retained fields 25, 26, 28, 30 Dump View Options display CMAC file use 23 fields 23
View panel 20 DUMPMASTER example dumps 15 new features in 9 Sample dumps 15 subsystem, Glossary entry 171 DumpNo field of Dump List 36 Dups field of Dump List 36
E
E Action Code 38, 39 ECB field of the Enqueue List 135 EIB Generated Note 180 END Command usage 49, 175, 197 see also Control Commands, and ISPF ENQS Command 134, 178, 197 Enqueue List accessing 134 description of 134 displaying 178 ENQS Command 178 fields 134 Enqueue request ENQS Command 178 fields on Enqueue List 134 global resource 134, 178 local resource 134, 178 ERRORS Command CICS system dump 149, 197 CICS transaction dump 149, 197 see also Note List Commands Errs field of Dump List 36 Example dumps 15 EXEC initial field 23 Execs How to invoke 153 M4LSTOEM, customizing 62 M4REXX 126, 153, 155 Macro 4 supplied 153 Exit from Dump Inspection 174, 176, 201 to the previous level 176 EXPAND Command example 194 usage 194, 197 see also Calc. & Conv. Commands Expires field of Dump List 36, 38 setting the date on a dump 39
Index
211
setting the date, online 37 Expiry date altering 37, 40 default 38 Dump List 36 Exporting dumps facility 12 Extended Find Facility 142
F
Failing Transaction Display displaying 92, 181 Fast path facility, description of 41 facility, invoking 41 facility, setting up 41 route to Dump List 33 routes to Dump Display 25, 29, 41, 126 FCP Command 149, 197 File Selection List 28 Filtering Parameter 170 Filters specifying for System Trace Table Display 123 FIND Command usage 187, 197 see also Search Commands Finding data backward (FIND) 187 backward (FINDR) 187 backward (LUP) 188 backward (not equal) (LUPNot) 189 case sensitive (FIND) 187 forward (FIND) 187 forward (FINDR) 187 forward (Locate) 188 forward (not equal) (LNot) 188 lower case (Locate) 188 lower case (LUP) 188 lower case (not equal) (LNot) 188 lower case (not equal) (LUPNot) 189 FINDR Command usage 187, 197 see also Search Commands FLOAT Command usage 194, 197 see also Calc. & Conv. Commands Following pointers Fullwords 183 Halfwords 183 S-type constants 183 FORMAT Command usage 178, 197 see also Information Commands Format Display
example 179 fields of 179 FORMAT Command 178 information provided 179 Formatted control block displays (CICS) 93 Full Stop (.) Glossary entry 170 in Dump Display 130 Point and Shoot indicator 50 Full Trace Entry Display see CICS Trace Table Displays Function field of System Trace Table Display 122
G
Generated Notes ANS24 190 COBOL 150, 180 HEX 191 INS 180, 180 LINS 180 OP1 180 OP2 180 PL/I 150, 180 Generic values in Dump Selection fields 27, 30, 31, 32 in the SUMMARY Command 150 Go to highest address of an area 182 lowest address of an area 183 GOTO Command 124, 136, 182 Greater Than (>) usage in the dump date field 28 usage in the dump time field 30
H
Help for individual commands 17, 139, 139 online 17, 139 pull down menu 54, 157 Special Character (?) 17, 139 HELP Command 17 HEX Generated Note usage 191 see also Generated Notes Hexadecimal character in LNOT Command 188 converting decimal value to 191 format of dumps 129 representation of a dump 130 usage in the LNOT Command 188 usage in the LOCATE Command 188 usage in the LUP Command 188
212
Index
usage in the LUPNOT Command 189
I
I/O Command CICS transaction dump 149, 198 MVS 149, 198 see also Note List Commands I/O Summary ACB Display 133 DCB Display 132 IAM Display 67 purpose of 131 IAM datasets 66 IBM information, displaying 177 ICP Command 149, 198 Importing dumps 12 IMS Abend Summary Display 73, 105, 110 Region Diagnostics Display 110 System View Display 117 Versions supported by DUMPMASTER 13 IMSMSGJOB Statement 22 INFO Command ASM Operand 179 generated notes 180 usage 198 Information Commands ENQS Command 178, 197 FORMAT Command 178, 197 INFO Command 198 LEVEL Command 180, 198 PSW Command 180, 201 TRACE Command 119, 181, 203 Information, displaying arrays 177 CMAC 75, 91, 177 DISPLAY Command 177 QuickRef 75 Initial command 154 Initial EXEC field 23 running an exec automatically 154 Initial Menu 16, 17, 19, 43, 46 Input Area field of Dump List 36 Input Area of Dump List 36 Input area of Dump List 38 INS Generated Note address portion of PSW 180 Assembler 180 see also Generated Notes IO COMMAND CICS 149, 198 MVS 149, 198
ISPF command delimiter 49 concatenate commands 49 dialog 46 facilities 46 HELP Command 17 KEYS Command 24 PFSHOW Command 24, 176, 203 primary option menu 46 recall a command 49 scrolling 33, 49 split screen 46 terminal characteristic 49 UP Command 49 versions supported by DUMPMASTER 13
J
JCP Command 149, 198 Job log capturing 72 displaying 72 Job Name field of Dump Selection 25, 26, 30 generic, specifying online 30 selecting dumps by 30 Jobname field of Dump List 36 JOURNAL Command CICS transaction dump 149 usage 198 see also Note List Commands Jump to an option from Dump Menu 126, 174 see also DMENU Command
K
KE Command 149, 198 Keep a dump after expiry 40 a Dump Inspection command 138 KEYS Command usage 24, 176 see also ISPF
L
Language Environment (LE) Abend Summary Display 111 Summary Display 111 see also LE/370 LD Command 150, 198 LE/370 12 Length field of a Note List 147
Index
213
Less Than (<) usage in the dump date field 28 usage in the dump time field 29 LEVEL Command usage 180, 198 see also Information Commands Line command Dump List 36, 37, 40 Note List 147 LINKEDIT information Assembler 99 CA-Panexec support 74, 99 COBOL 74 LINS Generated Note Batch 180 see also Generated Notes Listing Choice Display 71 Listing Choice Display (PDS/PDSE) 69 description of 69 input fields 69 Listing Search Options Display description of 58 input fields 59 Listing Selection Display (OEM) description of 70 input fields 70 Listings datasets check compile date/time 60, 61 deleting 160 formats 58 formats, setting 58 how DUMPMASTER searches for 61 individualized archives 167 OEM repository 60, 70 OEM, selecting 60 PDS/PDSE 60, 69 pre-search prompt 60, 68 printing 160 Remote, see Remote listings support search options 58 search options, default 59 search strategy 58 specifying 68 viewing 160 VPAM 59 see also COBOL listings, PL/I listings, and VPAM datasets Listings pull down menu 53, 157 Listings Server See Application Availability Server LM Command 150, 198 LNOT Command usage 188, 198 see also Search Commands LOCAL-STORAGE support, COBOL 77 LOCATE Command
usage 188, 199 see also Search Commands Locating data backward (FIND) 187 backward (LUP) 188 backward (not equal) (LUPNot) 189 case sensitive (FIND) 187 forward (FIND) 187 forward (FINDR) 187 forward (Locate) 188 forward (not equal) (LNot) 188 lower case (Locate) 188 lower case (LUP) 188 lower case (not equal) (LNot) 188 lower case (not equal) (LUPNot) 189 Lower case in the LNOT Command 188 in the LOCATE Command 188 in the LUP Command 188 in the LUPNOT Command 189 LUP Command usage 188, 199 see also Search Commands LUPNOT Command usage 189, 199 see also Search Commands
M
M4DMFPSU Fast Path facility command 42 M4LSTOEM EXEC Customizing 62 M4REXX EXEC 126, 153, 155 Macro 4 Diagnostics 156 Maintaining the Dump Dataset, online 33, 46 Major name field of the Enqueue List 134 Making a Note 184 ME Command 150, 199 Menus, pull down see Pull down menus Minimal address space dump 170 Minor name field of the Enqueue List 134 Minus (-) Dump Inspection repositioning 138 in the CALC Command 190 Repositioning Character 138 see also Special Characters MN Command 150, 199 MQSeries, see WebSphere MQSeries MRO Command 150, 199 MVS Dump Selection 25
214
Index
N
Navigation pull down menu 50, 52, 144, 156 Non-display character 130 Note address of on Dump Display 129 concept 46 creating 184 fullword of on Dump Display 129 generated (CALC) 190 generated (CH) 191 generated (INFO) 180 generated (PSW) 180 generic, in SUMMARY Command 150 Glossary entry 170 NOTE Command 184 obsolete 184 removing 184 representation on Dump Display 130, 184 SUBNOTE 46, 184 valid characters 184 Note area of Dump Display 130, 184 NOTE Command usage 184, 199 see also Set Commands Note List accessing Dump Display 148 all notes for a dump 146, 151 Command area 147 commands 147 complete 150 description of 146 entering addresses 147 entering commands 147 entering notes 147 fields 146, 147 for a CICS task 151 for COBOL notes 151 for PL/I notes 151 jumping to 174 line commands 147 of notes in a logical group 146 Plus (+) 147 Registers, accessing 137 selecting notes 147 selective 150 sequence 148 Note List Commands AI Command 149, 195 AP Command 149, 195 BF Command 149, 195 CC Command 149, 195
CP Command 149, 196 CS Command 149, 196 DD Command 149, 196 DLI Command 149, 196 DM Command 149, 196 DS Command 149, 196 DU Command 149, 197 ERRORS Command (CICS system dump) 149, 197 ERRORS Command (CICS transaction dump) 149, 197 FCP Command 149, 197 I/O Command (CICS) 149, 198 I/O Command (MVS) 149, 198 ICP Command 149, 198 JCP Command 149, 198 JOURNAL Command 149, 198 KE Command 149, 198 LD Command 150, 198 LM Command 150, 198 ME Command 150, 199 MN Command 150, 199 MRO Command 150, 199 PA Command 150, 200 PCP Command 150, 200 PCT Command 150, 200 PG Command 150, 200 PR Command 150, 200 PROGRAMS Command (CICS) 149, 201 PROGRAMS Command (MVS) 149, 201 RM Command 150, 201 SM Command 150, 202 SS Command 150, 202 STD Command 150, 202 STORE Command (CICS) 149, 202 STORE Command (MVS) 149, 202 SUMMARY Command (CICS system dump) 150, 202 SUMMARY Command (CICS transaction dump) 149, 202 SUMMARY Command (MVS) 146, 202 SYSTEM Command (CICS) 149, 202 SYSTEM Command (MVS) 149, 202 SZ Command 150, 202 TASK Command 149, 202 TCP Command 150, 202 TDATA Command 149, 203 TDP Command 150, 203 TERMINAL Command 149, 203 TI Command 150, 203 TMP Command 150, 203 TSP Command 150, 203 UEH Command 150, 203
Index
215
US Command 150, 203 USERNOTE Command (CICS) 150, 203 USERNOTE Command (MVS) 149, 203 USERSTOR Command 149, 203 XM Command 150, 204 XRF Command 150, 204 XS Command 150, 204
RESET Operand 185 usage 47, 184, 199 see also Set Commands Overwriting dump circumstances 39
P
PA Command 150, 200 Package Display, DB2 108, 170 Paging Note Lists 147 scope of commands 47, 48 Panexec support 74, 99 PCP Command 150, 200 PCT Command 150, 200 Period (.) 50, 170 PF Key Definition Display 20, 24, 24, 176 PF Key Label Display 20 PF Keys accessing Help using 17 changing the value 24 displaying the value 24 Option 24 removing labels 176 Setup option 176 PFSHOW Command usage 24, 176, 203 see also ISPF PG Command 150, 200 PH Command, see POINTH Command PL/I Abend Summary Display 73, 79 BASED variable support 83 Failing Statement Display 81 Failing Statement Display, BASED variable support 83 Failing Statement Display, restrictions 85, 87 generated notes 150, 180 list of PROCEDURE names 79 listings, see PL/I listings Note List 150, 151, 202 Selective Data Item Display 83 Selective Data Item Display, BASED variable support 83 Source Language Display 82 Source Language Display, restrictions 85, 87 Summary Display 84 System View Display 117 Versions supported by DUMPMASTER 13 PL/I listings check compile date/time 60, 61 confirming deletion of 166
O
OEM utility definition modules customizing 70 description of 70 Offset calculating using Origin address 184 field of Dump Display 129 field of Dump List 37 ORIGIN command 185 set the base address 47, 184 set the value of 182 OFFSET Command usage 182, 199 see also Positioning Commands Online access to dumps overview 12 see also Dump Online Program Listings deletion of 166 entry panels 161 index line commands 165 index panel 164 index primary commands 164 Remote, see Remote listings support see also Listings datasets OP1 Generated Note Assembler 180 see also Generated Notes OP2 Generated Note Assembler 180 see also Generated Notes Origin as base address for offset 47, 184 automatic value of 47 changing value of 130, 184 in Dump Display 130 in Dump Display, offset from 129 on selecting a Note 47, 48, 148 ORIGIN command 47, 184 setting value of 47, 48, 184 storage area selected as 47 storage subarea selected as 47 ORIGIN Command default 184 example 185
216
Index
dataset formats 58 dataset formats, setting 58 deleting online 160 how DUMPMASTER searches for 61 individualized VPAM archives 167 OEM repository 60, 70 OEM, selecting 60 PDS/PDSE 60, 69 pre-search prompt 60, 68 printing online 160 Program Listings Entry displays 161 Program Listings Index panel 164 Remote, see Remote listings support search options 58 search options, default 59 search strategy 58 specifying 68 viewing online 160 VPAM 59 Plan Display, DB2 107, 170 Plus (+) as a repositioning character 138 in A Action Code 38, 40 in CALC Command 190 in Dump List fields 38, 40 in Dump Selection fields 27, 30, 31, 32 in SUMMARY Command 150 see also Special Characters Point and Shoot Description of 50 Field 50, 171 Glossary entry 170 Indicator 50, 171 via Pull down menus 52 POINT Command example 183 usage 183, 200 see also Positioning Commands POINTH Command usage 183, 200 see also Positioning Commands POINTS Command usage 183, 200 see also Positioning Commands POINTV Command usage 183, 200 see also Positioning Commands POINTVH Command usage 183, 200 see also Positioning Commands Positioning Commands BOTTOM Command 182, 195 GOTO Command 124, 136, 182 OFFSET Command 182, 199 POINT Command 183, 200
POINTH Command 183, 200 POINTS Command 183, 200 POINTV Command 183, 200 POINTVH Command 183, 200 TOP Command 183, 203 PR Command 150, 200 PRB loading the registers from 185 Prerequisites 13 PREVIOUS Command example 175 usage 175, 201 see also Control Commands Primary Option Menu Accessing Dump Inspection Facility 46 see also ISPF Printing Dumps 38, 39, 141 Program Listings 160 PROCEDURE names, list of PL/I 79 PROG_INF Summary note 151 Progm field of System Trace Table Display 122 Program field of Dump List 37 Program information for CICS transactions 151 Program listings datasets See Listings datasets Program name field of Dump Selection 30 generic, specifying online 30 selecting dumps by 30 usage with GOTO command 182 PROGRAMS Command CICS 149, 201 MVS 149, 201 see also Note List Commands PS Command, see POINTS Command PSW 180 PSW Command ORIG Operand 180 usage 180, 201 see also Information Commands Pull down menus Action bar 52, 65 ACTIONS command 52 Advanced 52, 140, 142, 148, 153, 156, 157 Description of 52 Help 54, 157 Listings 53, 157 Navigation 50, 52, 144, 156 Setup 53, 156 Traces 54, 157
Index
217
PV Command, see POINTV Command PVH Command, see POINTVH Command
Q
QQUIT Command ISPF equivalent 176 usage 176, 201 see also Control Commands QuickRef Information 75 Matches List Display 75 QUIT Command ISPF equivalent 176 usage 176, 201 see also Control Commands
R
RACF 12 Recall a command RETRIEVE Command 49 see also ISPF Redisplay an address 184 Storage 184 Reference information prerequisites 13 REFRESH Command 37 Register accessing 137 alter values 137, 185 display contents of address in 137 fields of a Note List 146 fields of Dump Display 129 formatting as a save area 185 GR fields 137 on a Note List 137 on Dump Display 137 referencing 137 REGS Command 185 representing registers 10-15 137 REGS Command example 185 ORIG Operand 185 PRB Operand 185 RESET Operand 185 SAVE Operand 185 usage 129, 137, 146, 185, 201 see also Set Commands Releases of DUMPMASTER new features in 9 Remote listings support OEM repository 59 OEM, selecting 60
PDS/PDSE 59 prerequisites 62 retrieving a listing online 62 search options 58 selecting a listing 71 VPAM 59 see also Application Availability Server Removing a dump 38 an obsolete note 184 PF Key labels 176 Repositioning Characters (+,-) 48, 138 Retain Command Character (&) 138 Retained fields of Dump Selection 25, 26, 28, 30 RETRIEVE Command 49 RETURN Command usage 49, 176, 201 see also ISPF REXX API 153, 153 RM Command 150, 201
S
S Action Code 38, 40, 120, 124 sample dumps 15 Save area formatting registers as 185 Scope field of the Enqueue List 134 of paging commands 47, 48 of serialization 134 SCREEN Command 181, 202 Screen Display - failing displaying 181 Scrolling how to 33, 49 see also ISPF Search backward FIND 187 LUP 188 LUPNOT 189 Search Commands FIND Command 187, 197 FINDR Command 187, 197 LNOT Command 188, 198 LOCATE Command 188, 199 LUP COMMAND 188 LUP Command 199 LUPNOT Command 189, 199 XFIND Command 189, 204 Search forward FIND 187 LNOT 188 Security
218
Index
access to Administrators facilities 43 external 12 see also RACF Select Formatted CICS Block Display 95 Selected Address which module it lies in 181 Selecting a dump online 37, 40 Selection criteria for CICS dumps 25 for MVS dumps 25 Serialization 134 Session Setup 16, 20, 46 Set Commands DELETE Command 184, 196 NOTE Command 184, 199 ORIGIN Command 184, 199 REGS Command 185, 201 SETTASK Command 186, 202 Set the value of Offset 182 SETTASK Command usage 146, 186, 202 see also Set Commands Setup Options Menu 20 Setup pull down menu 53, 156 SHOWPARM OEM utility setup command 70 Slash (/) in the CALC Command 190 SM Command 150, 202 Source Looking at dumps and source 46 Source failing statement COBOL 74, 76 COBOL, indexed array support 77 PL/I 81, 82 Special Characters Asterisk (*) 150 Command Delimiter 49 in Dump Inspection 138 Minus (-) in Dump Inspection 138 Plus (+) in Dump Inspection 138 Plus (+) in Note List SUMMARY 150 Split screen 46 SS Command 150, 202 Status field of the Enqueue List 135 values of 135 STD Command 150, 202 Step name field of Dump Selection 31 generic, specifying online 31 selecting dumps online 31 Stepname field of Dump List 37 Storage displaying 129
insufficient 29 Storage Area description of 47 example 47 Glossary entry 171 Origin address 130 scope of paging 47, 48 Storage Contents Disassembly 191 Storage Subarea accessing 48 description of 47 example 47 glossary entry 171 STORE Command CICS 149, 202 MVS 149, 202 see also Note List Commands Subnote concept 46 generic, in SUMMARY Command 150 NOTE Command 184 see also Note Subsystem, DUMPMASTER Glossary entry 171 SUMMARY Command CICS system dump 150, 202 CICS transaction dump 149, 202 default 146, 151 example 151 for COBOL notes 150, 151, 202 for PL/I notes 150, 151, 202 generic note 150 generic subnote 150 MVS 149, 202 with Note List 146 see also Note List Commands SVRB field of the Enqueue List 135 Syntax Dump Inspection commands 173 SYSLOG displaying a dump from 41 Syst (system id) field of Dump List 37 SYSTEM Command CICS 149, 202 MVS 149, 202 see also Note List Commands System id field of Dump Selection 25, 30 selecting dumps by 30 System service request 180 System Trace Table Display see CICS Trace Table Displays System View Display
Index
219
COBOL 117 DB2 117 IMS 117 PL/I 117 SZ Command 150, 202
T
TACB Generated Note 180 TASK Command usage 149, 202 see also Note List Commands Task field of System Trace Table Display 121 TCB field of System Trace Table Display 121 of the Enqueue List 135 TCP Command 150, 202 TDATA Command usage 149, 203 see also Note List Commands TDP Command 150, 203 TERMINAL Command usage 149, 203 see also Note List Commands Terminal id CICS 31 field of Dump Selection 31 generic, specifying online 31 selecting dumps by 31 TI Command 150, 203 Time field of Dump List 36 field of Dump Selection 29 format 29 selecting dumps by 29 specific period 29 specifying a start time, online 29 specifying an end time, online 30 TMP Command 150, 203 TOGGLE Command usage 24, 176, 203 see also Control Commands TOP Command usage 183, 203 see also Positioning Commands Top Secret, see RACF TRACE Command 119, 181, 203 Trace Table Displays see CICS Trace Table Displays Traces pull down menu 54, 157 TRAN_INF Summary note 152 Transaction id field of Dump Selection 31 generic, specifying online 31 selecting dumps by 31
Transaction information for CICS transactions 152 TSO Prefix 28 versions supported by DUMPMASTER 13 TSP Command 150, 203 Tutorial accessing from Initial Menu 16, 46 for individual commands 17, 139 special character 139 TWA Generated Note 180 Type field of System Trace Table Display 122 Type of Dump field of Dump Selection 32
U
UEH Command 150, 203 UP Command usage 49 see also ISPF US Command 150, 203 User id CICS 32 field of Dump Selection 32 generic, specifying online 32 selecting dumps by 32 Userid field of Dump List 37 USERNOTE Command CICS system dump 150, 203 CICS transaction dump 149, 203 MVS 149, 203 use with user notes 184 see also Note List Commands USERSTOR Command usage 149, 203 see also Note List Commands
V
VIEW Command 181, 204 Viewing Program Listings 160 Volume field of Dump Selection 29 selecting dumps by 29 VPAM datasets check compile date/time 60, 61 deletion of 166 for program listings 55, 58 Glossary entry 171 how DUMPMASTER searches for 61 individualized 16, 167 listings Index 164
220
Index
maintenance 12 pre-search prompt 60, 68 Program Listings Entry Display 161 Program Listings Index Panel 164 Remote, see Remote listings support search options 58 search options, default 59 search strategy 58 specifying 68 working with 16, 161
W
WebSphere MQSeries ASD for 113 attributes 115 call detail 114 CICS system dumps 115 MQINQ and MQSET calls 115 WHERE Command Dump Inspection 181, 204
X
X Command 204 Xact (transaction id) field of Dump List 37 XFIND Command usage 189, 204 XM Command 150, 204 XRF Command 150, 204 XS Command 150, 204
I N T E L L I G E N T S Y S T E M S M A N A G E M E N T
www.macro4.com

Dumpmaster PDF

Uploaded by

Document Information

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

Dumpmaster PDF

Uploaded by

Copyright:

Available Formats

I N T E L L I G E N T S Y S T E M S M A N A G E M E N T

DUMPMASTER MVS 5.400

DUMPMASTER MVS User Guide DMOU-5400-00

About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Summary of new features . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Dump inspection setup and administration . . . . . . . . . 19

DUMPMASTER MVS USER GUIDE

Chapter 3 Primary dump inspection facilities . . . . . . . . . . . . . . . . 45

Dynamic 'Point and Shoot' access to information . . . . . . . . . . . . . . . . . . . . . . . . . 50

DUMPMASTER MVS USER GUIDE

Chapter 4 Advanced dump inspection facilities . . . . . . . . . . . . . 125

Chapter 5 Working with VPAM program listings online . . . . . . . 159

DUMPMASTER MVS USER GUIDE

Chapter 6 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Appendix A Dump inspection commands . . . . . . . . . . . . . . . . . . . . 173

DUMPMASTER MVS USER GUIDE

About this manual

Dump inspection commands on page 173

DUMPMASTER MVS USER GUIDE

About this manual

Release level in figures

DUMPMASTER MVS USER GUIDE

Summary of new features

New features in this release on page 10

DUMPMASTER MVS USER GUIDE

Summary of new features

New features in this release

Abend Summary Display (ASD) enhancements

COBOL support enhancements

DUMPMASTER MVS USER GUIDE

The following topics are covered here:

DUMPMASTER MVS USER GUIDE

Overview of DUMPMASTER components

Overview of DUMPMASTER components

DUMPMASTER MVS USER GUIDE

DUMPMASTER MVS USER GUIDE

DUMPMASTER MVS USER GUIDE

DUMPMASTER sample dumps

DUMPMASTER sample dumps

DUMPMASTER MVS USER GUIDE

DUMPMASTER Initial Menu

DUMPMASTER Initial Menu

1 4 MVS, CICS, MVS/F, CICS/F 5 6 VPAM, VPAM/F 7 Own VPAM

ADMIN CHANGES EXECs TUTORIAL

DUMPMASTER MVS USER GUIDE

Online Help and the DUMPMASTER tutorial

Online Help and the DUMPMASTER tutorial

4 - DUMP DISPLAY FUNCTION

DUMPMASTER MVS USER GUIDE

Online Help and the DUMPMASTER tutorial

DUMPMASTER MVS USER GUIDE

Dump inspection setup and administration

DUMPMASTER MVS USER GUIDE

Dump inspection setup and administration

Session Setup displays

Session Setup displays

Press END key to leave this menu

LIST Dump List options

DUMPMASTER MVS USER GUIDE

Dump inspection setup and administration

Session Setup displays

Dump List display fields

below page 22 page 22 page 22

Specifies dates in the North American format of mm/dd/yy.