XPEDITER/TSO and XPEDITER/IMS
           Messages and Codes


                       Release 7.2
ii       XPEDITER/TSO and XPEDITER/IMS Messages and Codes




                     Please direct questions about XPEDITER/...
iii




Contents

       Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
iv   XPEDITER/TSO and XPEDITER/IMS Messages and Codes
v




Preface                                                                                            S um_ Chgs




  ...
vi    XPEDITER/TSO and XPEDITER/IMS Messages and Codes




Additional Enhancements
              IMS/VS Quickstart for DLI...
Preface      vii




IMS UserID Support
            This new feature will allow XPEDITER/IMS running in MPPs to intercept ...
viii   XPEDITER/TSO and XPEDITER/IMS Messages and Codes
ix




Introduction                                                                                     I nt ro




      ...
x   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



             • Assembler H Version 2, High Level Assembler
       ...
Introduction     xi



           • Most messages are displayed in capital letters.
           • Messages appear in numeri...
xii   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



                  This document contains a series of examples th...
Introduction   xiii




Documentation Availability
FrontLine Support Web Site
          You can access online technical su...
xiv   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



               • Any ISPF error messages, operating system messa...
1-1




Chapter 1.
SIR to DDIO Utility Messages                                                                           ...
1-2   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



              SSU1002    <member>

                  Module:   A...
SIR to DDIO Utility Messages   1-3



   User Response: Verify that SYSUT3 ddname is allocated in the job step as document...
1-4   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



              SSU1514    UNCORRECTABLE I/O ERROR, MEMBER = <memb...
2-1




Chapter 2.
XPEDITER/TSO Messages                                                                                  ...
2-2   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



              XPD0007    ESTAE MACRO ERROR - RETURN CODE X(2)

 ...
XPEDITER/TSO Messages        2-3



   User Response: Ensure that valid values were supplied for the CTLTRLAT field during...
2-4   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



              XPD0105     RECORD HIERARCHY LEVEL COUNT NEGATIVE ...
XPEDITER/TSO Messages       2-5



XPD0150   I/O ERROR WHILE READING MODULE X(8)

   Module:   ADSRA097

   Explanation:  ...
2-6   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



              XPD0162   NO TYPE T RECORD FOUND FOR TGT FIELD IN ...
XPEDITER/TSO Messages         2-7



XPD0250   NO LOAD MODULE FOUND FOR X(8) IN XTASKLIB DATA SET

   Module:   ADSRA054

...
2-8   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



              XPD0318    MAXIMUM NUMBER OF DYNAMIC MEMBERS EXCEE...
XPEDITER/TSO Messages       2-9



   User Response:    Contact your internal technical support.

XPD0397   LOAD MODULE X(...
2-10   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



                   Explanation:     The length of the specified...
XPEDITER/TSO Messages      2-11



XPD0440   NO DATA ELEMENTS IN TOKEN X(4) FOR MODULE C(8)

   Module:   ADSRA187

   Exp...
2-12   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



               XPD0469    COMMAND NAME INVALID

               ...
XPEDITER/TSO Messages    2-13



XPD0566   NO ITEM FOR INDEX X(30) IN X(8)

   Module:   ADSRA028

   Explanation:     No ...
2-14   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



                   Explanation: There is no module control bloc...
XPEDITER/TSO Messages       2-15



   Explanation: The default list, as found in the global defaults module (ADSRA093), w...
2-16   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



                   because an XPEDITER EXIT was issued while wi...
XPEDITER/TSO Messages          2-17



XPD0851  0 WARNING: BLDL FAILED DURING XPEDITER COBOL TRAP PROCESSING FOR
MEMBER X(...
2-18   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



                   User Response:    Contact your internal tech...
XPEDITER/TSO Messages      2-19



XPD0893   MODULE NAME INVALID FOR FILE BUFFER

   Module:   ADSRA553

   Explanation:  ...
2-20   XPEDITER/TSO and XPEDITER/IMS Messages and Codes



                   Explanation: The specified module could not ...
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2
Upcoming SlideShare
Loading in...5
×

XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2

9,467

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
9,467
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
65
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "XPEDITER/TSO and XPEDITER/IMS Messages and Codes - Release 7.2"

  1. 1. XPEDITER/TSO and XPEDITER/IMS Messages and Codes Release 7.2
  2. 2. ii XPEDITER/TSO and XPEDITER/IMS Messages and Codes Please direct questions about XPEDITER/TSO and XPEDITER/IMS or comments on this document to: XPEDITER/TSO and XPEDITER/IMS Technical Support Compuware Corporation 31440 Northwestern Highway Farmington Hills, MI 48334-2564 1-800-538-7822 Outside the USA and Canada, please contact your local Compuware office or agent. This document and the product referenced in it are subject to the following legends: Copyright 1996-2003 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States. U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation. This product contains confidential information and trade secrets of Compuware Corporation. Use, disclosure, or reproduction is prohibited without the prior express written permission of Compuware Corporation. Access is limited to authorized users. Use of this product is subject to the terms and conditions of the user's License Agreement with Compuware Corporation. XPEDITER, Code Coverage, File-AID, Abend-AID, FrontLine, and Compuware Shared Services are trademarks or registered trademarks of Compuware Corporation. IBM, CICS, DB2, and MQSeries are trademarks of International Business Machines Corporation. CA-MIM, CA-ROSCOE, ENDEVOR, LIBRARIAN, PANEXEC, and PANVALET are trademarks or registered trademarks of Computer Associates International, Inc. Adobe ® Acrobat ® Reader copyright © 1987-2002 Adobe Systems Incorporated. All rights reserved. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. All other company and product names are trademarks or registered trademarks of their respective owners. Doc. CWXTMX7C December 30, 2002
  3. 3. iii Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v What’s New in Release 7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Foreground DB2 Stored Procedure Support. . . . . . . . . . . . . . . . . . . . . . v Generic IDs with DB2 Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . v Retention of IMS Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v DB2 Group Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Support for z/OS 1.3 and 1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v IMS Release 8.1 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Additional Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi What’s New in Release 7.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Toleration Support for VisualAge PL/I . . . . . . . . . . . . . . . . . . . . . . . . . . vi IMS UserID Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii DB2 Support Extended to DB2 Release 7.1 . . . . . . . . . . . . . . . . . . . . . vii DB2 Trigger and UDF Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii SMP/E Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Additional Features: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Manual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Operating Environment Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Accessing Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Notation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x VisualAge PL/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Documentation Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii FrontLine Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii World Wide Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii Chapter 1. SIR to DDIO Utility Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Chapter 2. XPEDITER/TSO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Chapter 3. User Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Chapter 4. Miscellaneous Messages and Codes Information . . . . . . . . . . . . . . . . 4-1 XPEDITER/ROS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Condition Codes from Recreation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1 Chapter 5. XPEDITER for DB2 Extension Run-Time Messages . . . . . . . . . . . . . . . 5-1 Chapter 6. Unsuccessful SQL Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
  4. 4. iv XPEDITER/TSO and XPEDITER/IMS Messages and Codes
  5. 5. v Preface S um_ Chgs XPEDITER is a testing and debugging tool for COBOL, Assembler, PL/I, and C programs that run in TSO (both interactive and batch), IMS, CICS, and ROSCOE environments. XPEDITER simplifies the tasks of testing and debugging by giving programmers complete control over the execution of their programs at the source code level without requiring source or object code changes. Members of Compuware’s XPEDITER family of debugging and testing products include XPEDITER/TSO, XPEDITER/IMS, XPEDITER/CICS, XPEDITER/Code Coverage, XPEDITER/Xchange, and XPEDITER/DevEnterprise (for the workstation). Summary of Changes This section includes brief descriptions of the changes to XPEDITER/TSO and XPEDITER/IMS for Release 7.2. For those updating directly from Release 7.0, changes made for Release 7.1 are also summarized. What’s New in Release 7.2 Compuware is pleased to announce XPEDITER/TSO and XPEDITER/IMS Release 7.2, with these new features: Foreground DB2 Stored Procedure Support The TSO foreground can now be used for debugging DB2 Stored Procedures, eliminating the requirement for available JES-controlled initiators. Generic IDs with DB2 Stored Procedures Now different users running DB2 stored procedures with a common generic ID can be distinguished from one another. Retention of IMS Breakpoints XPEDITER will now save breakpoints set in IMS transactions from one test session iteration to the next. DB2 Group Support With Release 7.2, support is provided for multiple DB2 subsystems configured as data sharing groups on the same LPAR as XPEDITER/TSO. Support for z/OS 1.3 and 1.4 XPEDITER continues to provide support for the latest release of IBM’s operating system. IMS Release 8.1 Support XPEDITER/IMS now provides support for Version 8 of IMS.
  6. 6. vi XPEDITER/TSO and XPEDITER/IMS Messages and Codes Additional Enhancements IMS/VS Quickstart for DLI XPEDITER will read your JCL’s IMS PARM string for APARM information and pass it to the test, unless overridden in XPEDITER’s IMS setup panel. If the DLI test includes DB2, XPEDITER can obtain the DB2 plan name and system name from the DDITV02 file. Abending Module Information The XPEDITER log will now identify the load library of the module in which an abend has occurred so you can verify the correct library was used. Enhanced SHOW ZAPS Display The output of the SHOW ZAPS command will list applied XPEDITER PTFs plus the load library where the PTFs reside. SHOW LINKLIST Command This new SHOW command parameter will display a list of libraries in the system linklist and write the list to the XPEDITER log. C Language KEEPE/PEEKE XPEDITER’s KEEPE and PEEKE commands have been extended to C programs, making it easier to navigate variable content. Batch Connect Log and Script Retention The SCRIPT DATASET and LOG DATASET screens are now used during the creation of the Batch Connect JCL to specify the final disposition of the Log and Script files. Enhanced SHOW WHEN Command Conditional breakpoints can now be selectively deleted when displayed with the SHOW WHEN command. Post Script for Batch Connect With Release 7.2, you can specify a script to run automatically at the conclusion of a Batch Connect session. BIND DB2 Packages XPEDITER’s DB2 BIND PLAN function has been extended to let you BIND packages as well. You can also now edit the generated JCL. What’s New in Release 7.1 Compuware is pleased to announce XPEDITER/TSO and XPEDITER/IMS Release 7.1, with these new features: Toleration Support for VisualAge PL/I XPEDITER has further broadened its language compatibility to provide toleration support for modules processed using IBM’s VA PL/I compiler.
  7. 7. Preface vii IMS UserID Support This new feature will allow XPEDITER/IMS running in MPPs to intercept transactions based on IMS userID. With this new functionality, multiple users can run and/or debug the same IMS transaction without affecting each others’ test sessions. DB2 Support Extended to DB2 Release 7.1 XPEDITER’s industry-leading support for DB2, including Stored Procedure support, has been extended to release 7.1 of DB2. DB2 Trigger and UDF Debugging XPEDITER now enables User Defined Functions (UDFs) and triggers to be intercepted and debugged. SMP/E Delivery Delivery and maintenance of XPEDITER/TSO and XPEDITER/IMS is now performed using IBM’s System Modification Program Extended (SMP/E). Additional Features: Direct Access to File-AID/IMS: Compuware’s powerful File-AID/IMS product is now directly accessible with a new Primary Menu selection. Enhanced Quickstart Support The STEPLIB, execution parameters, DB2 subsystem and plan, and DSNLOAD setup information required for establishing XPEDITER’s interactive testing environment can now be automatically retrieved from your JCL. Integrated File-AID/MVS Browse and Edit Functions: The file browse (FB) and file edit (FE) capabilities in File-AID/MVS can now be accessed conveniently from within XPEDITER. Any file accessible to File-AID/MVS can be browsed or edited via the Preview Files option at test session initialization to confirm the content of test conditions. Extended Batch Connect Terminal Support: Model 3, 4, and 5 terminals are now fully supported by the Batch Connect facility in XPEDITER/TSO. Display of PACKED fields in COBOL 2.2: XPEDITER will now use a scrollable area to display the contents of 31-digit comp-3 fields.
  8. 8. viii XPEDITER/TSO and XPEDITER/IMS Messages and Codes
  9. 9. ix Introduction I nt ro The purpose of this document is to provide a convenient cross-reference of the messages and ABEND codes issued by the following Compuware products: XPEDITER/TSO, XPEDITER/IMS, and XPEDITER for DB2 Extension. Besides system messages and ABEND codes, there are also other types of messages. Some are written to the source display during a test in a one line area below the command line, known as the message area. Others are simply written to the terminal in no specific format. These messages, however, are context sensitive and are intended to be self- explanatory. Unnumbered messages in the log can also fall into this category. Some processing errors are so severe that either the test or the compile must be shut down immediately. If XPEDITER/TSO itself abends, the appropriate action is always to contact your in-house technical support staff for XPEDITER/TSO, XPEDITER/IMS, or XPEDITER for DB2 Extension. In some instances, your internal technical support contact can advise you to call Compuware Technical Support directly. Manual Organization The XPEDITER Messages and Codes Manual is divided into six sections: • Chapter 1, “SIR to DDIO Utility Messages” • Chapter 2, “XPEDITER/TSO Messages” • Chapter 3, “User Abend Codes” • Chapter 4, “Miscellaneous Messages and Codes Information” • Chapter 5, “XPEDITER for DB2 Extension Run-Time Messages” • Chapter 6, “Unsuccessful SQL Error Codes”. Intended Audience Generally, recommended actions and explanations for XPEDITER messages and abend codes are written for the installer and for the end user: the COBOL, Assembler, PL/I, or C Language programmer using one of the XPEDITER products to debug their programs. Operating Environment Support XPEDITER/TSO is invoked as an ISPF dialog under TSO. XPEDITER/IMS DC executes in an IMS-dependent region within your TSO address space. The following environments are supported: • MVS/ESA Versions 5.1 and above • OS/390 Releases 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10 • z/OS Releases 1.1, 1.2, 1.3, and 1.4 • DFSMS • OS/VS COBOL Release 2.4 • VS COBOL II Version 1, Releases 4.0 and above • COBOL for MVS & VM Release 1.2 (in compatibility mode) • COBOL for OS/390 Release 2.1 and 2.2 (both in compatibility mode) • Enterprise COBOL for z/OS and OS/390 Version 3.1 (in compatibility mode) • CA-OPTIMIZER Releases 5.1 and 6.0
  10. 10. x XPEDITER/TSO and XPEDITER/IMS Messages and Codes • Assembler H Version 2, High Level Assembler • PL/I Versions 2.3 and above • AD/CYCLE for PL/I MVS and VM 1.1 (PL/I 370) • VisualAge PL/I for OS/390 Releases 2.2.1 and 2.2.24 (both in toleration mode) • Enterprise PL/I for z/OS Version 3.1 (in toleration mode) • Major sorting packages - DFSORT and SYNCSORT • ISPF/PDF Versions 3.5 through 5.2 • DB2 Versions 3.1, 4.1, 5.1, 6.1, and 7.1 • IMS/VS Versions 2.1 and 2.2 • IMS/ESA Versions 4.1, 5.1, 6.1, 7.1, and 8.1 • BTS • IDMS/DB, ADABAS, TOTAL, TIS, SUPRA, DATACOM/DB, System 2000 • Hogan • AD/CYCLE for COBOL/370 Release 1.1 • LE/370 Versions 1.2, 1.3, and 1.4 • Language Environment for MVS & VM, Versions 1.5, 1.6, 1.7, 1.8, 1.9, 2.7, 2.8, 2.9, 2.10, as well as Language Environment for z/OS Version 1.2 • C for MVS/ESA Version 3.2 • OS/390 C Version 1.2, 1.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, and 2.10. Contact Compuware Technical Support for information on releases not mentioned above. Notes: 1. COBOL for MVS & VM Version 1.2 compatibility mode means that XPEDITER/TSO supports COBOL II and COBOL/370 programs that have been recompiled with COBOL for MVS & VM Version 1.2. XPEDITER/TSO does not support the new COBOL for MVS & VM Version 1.2 features, with the exception of Local-Storage, Recursive, and Returning (requires Compuware Shared Services (CSS) Release 7.4 or greater). 2. In a prior release, support was dropped for Assembler F; VS COBOL II, Releases 3.0, 3.1, and 3.2; PL/I Version 1.5; ISPF/PDF Versions 2, 3.1, 3.2 and 3.3; DB2 Versions 1 and 2; IMS/ESA Version 3; MVS/XA Version 2; IMS/VS Versions 1 and 2; CA- OPTIMIZER Release 5.0; TSO dBUG-AID; and TCF. 3. All release support is dependent on the vendor certifying that the product is Y2K compliant. Accessing Other Products XPEDITER/TSO and XPEDITER/IMS are fully integrated with Compuware’s File-AID for DB2 (Release 3.5 or above), Abend-AID (Release 7.0.2 or above for COBOL and Assembler, and Release 8.0.4 or above for PL/I and C Language), and XPEDITER/DevEnterprise Batch Debugger (Release 2.0 or above). From the XPEDITER/TSO Primary Menu, you can access a CICS region where other Compuware tools, such as XPEDITER/CICS and CICS Abend- AID, can be used. Notation Rules The following notation rules apply: • Messages and abends are shown in the following format, when applicable: – Message number – Message – Module name, if required – Explanation of message – System action, if necessary – User action, if necessary.
  11. 11. Introduction xi • Most messages are displayed in capital letters. • Messages appear in numerical order in the text. • Some messages are identified with a numeric negative value which precedes the message text. These messages correspond to Unsuccessful SQL (USQL) Error Codes. • Messages written to the log and abend messages list one or more modules as the source of the message. This information is used by Compuware Technical Support to help answer your questions. • If the message or abend was generated in response to bad program data, the product can provide information as to the type of data (“X” for alphanumeric, “N” for binary or numeric) and data item length. Under certain circumstances, “C” could be either alphanumeric or a character. For example, “X(30)” means that up to thirty bytes of data (perhaps a dataset name) will be inserted into the message. • Whenever a user abend occurs, there should be another message preceding it. VisualAge PL/I The compiler for VisualAge PL/I is somewhat different in the way it handles certain aspects of the language. One such difference involves the method by which statements are identified. Traditionally, each PL/I statement was given a unique statement number for identification in the various elements of the compiler output. Under VisualAge PL/I compilation, however, the identification is less finite, with only the file and line number being used to discern between language constructs. Because this mechanism is somewhat awkward when using XPEDITER, the Compuware Language Processor instead associates each file and line number combination with a single sequential line number. It is this generated line number which is used by XPEDITER with VisualAge PL/I programs as the replacement notation for statement number under previous PL/I compilers. As a result, references to the term “statement” in XPEDITER documentation, messages and panels actually refer to the line construct (which may contain multiple statements) in a VisualAge PL/I environment. Related Publications The following Compuware documents are also available for use with XPEDITER/TSO and XPEDITER/IMS: • XPEDITER/TSO and XPEDITER/IMS Installation Guide This document describes the steps necessary to install XPEDITER/TSO and XPEDITER/IMS (full-screen IMS/DC) for testing COBOL, Assembler, C, and PL/I programs. XPEDITER/IMS tests COBOL, Assembler, C, and PL/I programs that are executed in MPP, BMP, and IFP(Fast Path) regions. • XPEDITER/TSO and XPEDITER/IMS COBOL User’s Guide This document contains a series of examples that demonstrate simple and advanced debugging techniques that can be applied to your application and development needs. It describes how to use XPEDITER/TSO and XPEDITER/IMS facilities in the COBOL context with minor references to mixed language debugging support. • XPEDITER/TSO and XPEDITER/IMS Reference Manual This document lists all the commands available for use by XPEDITER/TSO and XPEDITER/IMS. It is written for the application programmer engaged in program development. A working knowledge of COBOL, Assembler, C, PL/I, and your local operating system(s) is assumed. • XPEDITER/TSO and XPEDITER/IMS Assembler User’s Guide
  12. 12. xii XPEDITER/TSO and XPEDITER/IMS Messages and Codes This document contains a series of examples that demonstrate simple and advanced debugging techniques that can be applied to your application and development needs. It describes how to use XPEDITER/TSO and XPEDITER/IMS facilities in the Assembler context. • XPEDITER/TSO and XPEDITER/IMS PL/I User’s Guide This document contains a series of examples that demonstrate simple and advanced debugging techniques that can be applied to your application and development needs. It describes how to use XPEDITER/TSO and XPEDITER/IMS facilities in the PL/I context. • XPEDITER/TSO and XPEDITER/IMS C User’s Guide This document contains a series of examples that demonstrate simple and advanced debugging techniques that can be applied to your application and development needs. It describes how to use XPEDITER/TSO and XPEDITER/IMS facilities in the C Language context. • XPEDITER/TSO and XPEDITER/IMS Quick Reference This document provides easy access to XPEDITER/TSO and XPEDITER/IMS COBOL, Assembler, and PL/I commands and command descriptions. • File-AID for DB2 Reference Manual This document provides information about using XPEDITER for DB2 Extension facilities. • XPEDITER/DevEnterprise Suite of Manuals These documents provide information about using XPEDITER/DevEnterprise on the workstation. • XPEDITER/Xchange Installation and Reference Manual This document provides the information needed for testing your date- and time- sensitive applications. • Enterprise Common Components Installation and Customization Guide An introduction, overview, and installation guide for Compuware Shared Services (CSS) components, Compuware’s common files and utilities (DDIO and DDSUTIL), and the Compuware Language Processors. • Compuware Shared Services User/Reference Guide, MVS Version This document provides information to install, customize, and maintain Compuware Shared Services (CSS). It is intended for CSS installers and application programmers. • XPEDITER/Code Coverage Mainframe Installation Guide This document provides information about installing XPEDITER/Code Coverage. • XPEDITER/Code Coverage Mainframe User/Reference Guide This document provides information regarding the use of XPEDITER/Code Coverage. It provides an explanation of the requirement that XPEDITER/Code Coverage work in conjunction with at least one additional mainframe XPEDITER testing and debugging tool. More information on COBOL compiler options is contained in the following documents: • VS COBOL II Application Programming Guide • IBM OS/VS COBOL Compiler and Library Programmer’s Guide • IBM OS Full American National Standard COBOL Compiler and Library, Version 3 Programmer’s Guide
  13. 13. Introduction xiii Documentation Availability FrontLine Support Web Site You can access online technical support for Compuware products via our FrontLine support web site. You can read or download documentation, frequently asked questions, and product fixes, or directly e-mail Compuware with questions or comments. To access FrontLine, you must first register and obtain a password at http://frontline.compuware.com. Online Documentation Documentation for this product is provided on CD-ROM in several electronic formats. PDF files can be viewed with the free Adobe Acrobat Reader, available at http://www.adobe.com. HTML files can be viewed with any standard web browser. BookManager softcopy files can be viewed with any version of IBM BookManager READ or the IBM Softcopy Reader. To learn more about BookManager or download the free Softcopy Reader, go to http://www.ibm.com. World Wide Web Compuware’s site on the World Wide Web provides information about Compuware and its products. The address is http://www.compuware.com. Getting Help At Compuware, we strive to make our products and documentation the best in the industry. Feedback from our customers helps us to maintain our quality standards. Questions about any XPEDITER product or comments on this document should be directed to: XPEDITER/TSO and XPEDITER/IMS Technical Support Compuware Corporation 31440 Northwestern Highway Farmington Hills, MI 48334-2564 1-800-538-7822 Outside the USA and Canada, please contact your local Compuware office or agent. If problems occur, consult your manual or the XPEDITER/TSO and XPEDITER/IMS technical support representative at your site. If problems persist, please obtain the following information before calling Compuware. This information helps us to efficiently determine the cause of the problem. For problems occurring during compile time: • Release level of compiler • List of other vendor products used • Abend module name • Any messages in CWPERRM ddname • Release of Compuware Shared Services (CSS). For problems encountered before bringing up your program (front end problems): • Sequence of events leading up to the problem • Release and level of XPEDITER product
  14. 14. xiv XPEDITER/TSO and XPEDITER/IMS Messages and Codes • Any ISPF error messages, operating system messages, and information provided in the TSO profile WTPMSG. For run-time abends: • Release and level of XPEDITER product • Any ISPF error messages, operating system messages, and information provided in the TSO profile WTPMSG • Information provided in the product log dataset at the time of the abend. Note: When in-depth diagnosis is required, the following documentation will be requested from you: 1. Full SYSUDUMP (not Abend-AID dump) or SYSMDUMP 2. Source listing or tape of problem programs, including all copy books and members used 3. Listing of product log at the time of the abend 4. Listing of the original compile. If, as the in-house XPEDITER technical support contact, you are unable to resolve an XPEDITER product problem, the proper action is to call Compuware directly.
  15. 15. 1-1 Chapter 1. SIR to DDIO Utility Messages C ha p 1 SSU0021 UNABLE TO READ DIRECTORY BLOCK FROM SIR PDS Module: ADSSU002 Explanation: The utility was attempting to read to the SIR PDS directory when a SYNAD exit was taken. User Response: Rerun the job. If the error occurs again, the SIR PDS is unusable for the conversion utility. SSU0022 INVALID DIRECTORY BLOCK FOR SIR PDS Module: ADSSU002 Explanation: The DCBBLKSI for the directory exceeds the maximum allowable size. User Response: The SIR PDS members must be recompiled/reassembled for use by XPEDITER/TSO. SSU0023 ERROR DURING OPEN OF SIR DATASET Module: ADSSU002 Explanation: The utility attempted to open the SIR PDS and failed. User Response: The SIR PDS members must be recompiled/reassembled for use by XPEDITER/TSO. SSU0024 SYNAD EXIT TAKEN FOR SIR DATASET Module: ADSSU002 Explanation: A SYNAD error occurred while attempting to read the SIR PDS. User Response: The SIR PDS members must be recompiled/reassembled for use by XPEDITER/TSO. SSU0025 INVALID OPTION PASSED TO MODULE - N(4) Module: ADSSU002 Explanation: The option passed to the module was not valid. User Response: Contact your internal technical support. SSU0297 DD-’,(C,8),’ IS MISSING Module: ADSSU082 Explanation: This message is no longer valid. User Response: None. SSU0304 OPEN FAILED FOR DD-’,(C,8),’ Module: ADSSU082 Explanation: This message is no longer valid. User Response: None. SSU1001 XTIN DDNAME IS NOT ALLOCATED Module: ADSSU100 Explanation: The XTIN ddname was not allocated in the submitted JCL. User Response: Add the XTIN ddname specifying the SIR dataset to be converted.
  16. 16. 1-2 XPEDITER/TSO and XPEDITER/IMS Messages and Codes SSU1002 <member> Module: ADSSU100 Explanation: The displayed member name did not successfully convert to the DDIO format. User Response: Recompile/reassemble this member for use by XPEDITER/TSO. SSU1004 THE FOLLOWING SIR LIBRARY MEMBERS WERE NOT CONVERTED: Module: ADSSU100 Explanation: The list that follows this message are the members that did not successfully convert to the DDIO format. User Response: Contact your internal technical support. A recompile or reassembly of SIR PDS members may be required. SSU1005 THE DDIO FILE IS FULL. PROCESSING TERMINATED. Module: ADSSU100 Explanation: The DDIO file has reached its defined maximum capacity. User Response: Reallocate the file with a larger space allocation or reallocate with the same space but format with a larger REPTCOUNT value. SSU1006 MEMBER <member> NOT FOUND IN SPECIFIED LIBRARY. Module: ADSSU100 Explanation: A member name was specified in the SIR to DDIO conversion utility but the member name was not found. User Response: Correct the member name and resubmit the conversion request. SSU1007 MEMBER MUST BE SPECIFIED WHEN REQUESTING A START POINT. Module: ADSSU100 Explanation: A request to start the conversion process at a specified member was requested but the member name was not found. User Response: Specify the member name in the parm. SSU1011 UNABLE TO OPEN CWPPRTI Module: ADSSU101 Explanation: The utility failed in an attempt to open a work file. User Response: Verify that CWPPRTI ddname is allocated in the job step. If it was, contact your internal technical support. Otherwise, correct the JCL and rerun the job. SSU1012 UNABLE TO OPEN SYSUT1 Module: ADSSU101 Explanation: The utility failed in an attempt to open a work file. User Response: Verify that SYSUT1 ddname is allocated in the job step as documented. If it was, contact your internal technical support. Otherwise, correct the JCL and rerun the job. SSU1013 UNABLE TO OPEN SYSUT2 Module: ADSSU101 Explanation: The utility failed in an attempt to open a work file. User Response: Verify that SYSUT2 ddname is allocated in the job step as documented. If it was, contact your internal technical support. Otherwise, correct the JCL and rerun the job. SSU1014 UNABLE TO OPEN SYSUT3 Module: ADSSU101 Explanation: The utility failed in an attempt to open a work file.
  17. 17. SIR to DDIO Utility Messages 1-3 User Response: Verify that SYSUT3 ddname is allocated in the job step as documented. If it was, contact your internal technical support. Otherwise, correct the JCL and rerun the job. SSU1015 SIR OPTIONS RECORD NOT FOUND Module: ADSSU101 Explanation: The utility could not locate a SIR record. User Response: None. SSU1117 FATAL ERROR - CONTACT TECHNICAL SUPPORT Module: ADSSU204 Explanation: This message is no longer valid. User Response: Contact Compuware Technical Support. SSU1200 AN ANALYSIS WAS PERFORMED ON DATASET <dataset-name> Module: ADSSU120 Explanation: Refer to SSU1201. SSU1201 FOR DDIO SPACE AND FORMAT RECOMMENDATIONS. Module: ADSSU120 Explanation: The specified dataset was analyzed for suggested space/format recommendations prior to converting SIR members to DDIO members. User Response: None. SSU1204 RECOMMENDED FORMAT PARAMETERS: Module: ADSSU120 Explanation: This message is no longer valid. User Response: None. SSU1510 GETMAIN FOR SIR BUFFER FAILED Module: ADSSU151 Explanation: A GETMAIN equal in size to the block size of the SIR PDS failed. User Response: Contact your internal technical support. A recompile or reassembly of SIR PDS members may be required. SSU1511 OBTAIN FAILED FOR SIR DATASET Module: ADSSU151 Explanation: An OBTAIN returned a non-zero return code. User Response: Contact your internal technical support. A recompile or reassembly of SIR PDS members may be required. SSU1512 OPEN FAILED FOR SIR DATASET Module: ADSSU151 Explanation: An OPEN for INPUT failed. User Response: Contact Compuware Technical Support. A recompile or reassembly of SIR PDS members may be required. SSU1513 SIR MEMBER NOT FOUND; MEMBER = <member> Module: ADSSU151 Explanation: The SIR PDS directory specified a member which a BLDL could not find. User Response: Contact your internal technical support. A recompile or reassembly of SIR PDS members may be required.
  18. 18. 1-4 XPEDITER/TSO and XPEDITER/IMS Messages and Codes SSU1514 UNCORRECTABLE I/O ERROR, MEMBER = <member> Module: ADSSU151 Explanation: A permanent I/O error occurred while reading the specified member. User Response: A recompile or reassembly of the SIR PDS member is required. SSU4101 UNABLE TO OPEN FILE <ddname> Module: ADSSU100 Explanation: The specified file could not be opened. User Response: If the specified ddname is allocated in the JCL, contact your internal technical support. Otherwise, correct and rerun the job. SSU4111 UNABLE TO CLOSE FILE <ddname> Module: ADSSU100 Explanation: The specified file could not be closed. User Response: Contact your internal technical support. SSU7386 NO MESSAGE CASE OPTIONS RECORD WAS FOUND. DEFAULTING TO ASIS. Module: ADSSU100 Explanation: The XOPTIONS dataset did not contain an options record to specify the case type to display messages. User Response: None.
  19. 19. 2-1 Chapter 2. XPEDITER/TSO Messages C ha p 2 XPD@@01E INCORRECT OR MISSING EXEC PARM Explanation: This message can be generated by both the started task and the file formatting program. The only time that it may lead to confusion is when BLK parameter is too small or the QNAME is too short. User Response: If you see this massage generated by a file formatting program and all parameters appear correct, BLK is most likely too small. Please refer to the suggested BLK parameter formula. XPD@@02E DISABLE BLKSIZE OPTIMIZATION, WHATEVER IT IS Explanation: There are I/O optimization products (i.e., ULTIMIZER) that can alter the BLKSIZE. This error is generated when the DCB’s BLKSIZE changes after an OPEN. User Response: XPEDITER requires precise BLKSIZE as specified in EXEC PARM. XPD@@03E THIS IS NOT A STARTED TASK Explanation: It must be a started task. User Response: Please do not submit from TSO. XPD@@04E ENQ PROPAGATING TASK ALREADY STARTED Explanation: The operator already issued a START command for our started task, and it is operating. User Response: Another START command is neither needed nor allowed. XPD@@05W DATA SET FOR ENQ PROPAGATION IS FULL Explanation: This is a warning. The shared file is full and the appropriate action is to stop all started tasks and create a larger file. User Response: If stopping all started tasks is not possible at this time, you may wait and all terminating XPEDITER Batch Connect jobs will be removed from the shared file. This will free up space within the shared file. At that point, the started task will recognize this and continue. XPD@@06E XPEDITER ENQS PROPAGATED WITHOUT STARTED TASK Explanation: In this situation, either CA-MIM is not active or some other means of propagating SYSTEMS ENQs is available. User Response: Due to the fact that the SYSTEMS ENQs are propagated, the started task is redundant and therefore unnecessary. XPD0000 UNABLE TO TERMINATE TEST REQUESTED BY XPEDITER MODULE Module: ADSRA000 User Response: Contact your internal technical support immediately. Compuware needs to be informed of all circumstances leading to this message. XPD0001 LMS ERROR RC = XX, REASON CODE = YYY Module: ADSRA001 Explanation: An error was encountered in License Management software. User Response: Ensure LMSINIT has been run and subsystem is operational. Otherwise, contact Compuware Technical Support with the return and reason codes.
  20. 20. 2-2 XPEDITER/TSO and XPEDITER/IMS Messages and Codes XPD0007 ESTAE MACRO ERROR - RETURN CODE X(2) Module: ADSRA105 Explanation: A critical error occurred while a STAE/ESTAE macro was being issued. User Response: Contact your internal technical support. XPD0011 VTAM NODE: A(8) USER: B(8) JOBNAME: C(8) Module: CSSMVS Explanation: A Batch Connect job is ready for connection—A(8) is the VTAM NODE, B(8) is the userid, C(8) is the job name. Messages XPD0012 and XPD0013 will follow. XPD0012 JOBNUMBER: D(8) STEP: E(8) PROCSTEP: F(8) Module: CSSMVS Explanation: This is a continuation of message XPD0011. D(8) is the job number. E(8) is the step name. F(8) is the procedure step name, if any. Message XPD0013 follows. XPD0013 IS WAITING FOR CONNECTION ON SYSTEM G(4) Module: CSSMVS Explanation: This is a continuation of message XPD0012. G(4) is the system ID. XPD0025 STORAGE AVAILABLE FOR SIMULATE LIST Module: ADSRA058 Explanation: No main storage was available to build a list of simulated module names. User Response: Increase the REGION size and try the test again. XPD0033 MEMORY ALLOCATION FAILED. BYTES REQUESTED N(4) MNEMONIC X(8) Module: ADSRA003 and ADSRA007 Explanation: Allocation of virtual storage in subpool zero failed for XPEDITER control block allocation. User Response: If the length specified seems reasonable, increase the REGION size; or contact your internal technical support. XPD0034 CONTROL STACK ENTRY MAXIMUM EXCEEDED Module: ADSRA106 Explanation: The number of hierarchical levels in XPEDITER exceeds the control stack capacity. This stack is used as an internal control mechanism by XPEDITER to maintain proper linkages between call interfaces. User Response: Contact your internal technical support. XPD0054 OPEN FAILED FOR DDNAME X(8) Module: ADSRA170 Explanation: The dataset from which XPEDITER obtains its input could not be opened. User Response: Check your batch JCL stream, TSO CLIST, or XPEDITER/TSO Installation Defaults panel to include the appropriate DD. If the problem persists, contact your internal technical support. XPD0067 GETMAIN FAILED. BYTES REQUESTED - N(4) Module: ADSRA097, ADSRA448, and ADSRA553 Explanation: An attempt to acquire additional storage failed. User Response: Increase the REGION allocated to the TSO logon session or the JOB step. XPD0070 INVALID TRANSLATE OVERRIDES: X(40) Module: ADSRA007 Explanation: The data supplied in the CTLTRLAT field has failed the validation check.
  21. 21. XPEDITER/TSO Messages 2-3 User Response: Ensure that valid values were supplied for the CTLTRLAT field during the product installation. Changes to offsets X'00' thru X'40' and/or alphanumeric offsets are not allowed. XPD0071 OVERRIDE VALUES CONTINUED: X(40) Module: ADSRA007 Explanation: A continuation of the display from message XPD0070. Displays the next forty bytes of the CTLTRLAT field. User Response: See message XPD0070. XPD0087 BREAKPOINT OFFSET N(4) EXCEEDS THE SIZE OF MODULE X(8) Module: ADSRA104 and ADSRA601 Explanation: An interrupt address is invalid in the module for which a monitor event occurred. User Response: Ensure that the member keyword for the appropriate XPEDITER command was specified. If the problem cannot be resolved, contact your internal technical support. XPD0099 GLOBAL SYSTEM PARAMETER NOT FOUND - X(8) Module: ADSRA110 Explanation: An invalid condition was detected in an XPEDITER control block during processing of the current command. User Response: This message must be communicated to your internal technical support. XPD0100 THIS MODULE FOR MVS - CMS USE ADSRA232 Module: ADSRA242 Explanation: Module ADSRA242 can only be used to list the sizes of modules running under the MVS operating system. User Response: For CMS, use module ADSRA232. XPD0101 NO SBL CELLS TGT ENTRY FOR X(8) Module: ADSRA189 Explanation: The DDIO dataset member for the specified module does not contain a task global table record for the secondary base locator cells. No processing will occur for fields which are assigned secondary base locators (see DMAP for module). XPD0102 X(8) NOT FOUND IN USER LIBRARY Module: ADSRA189 Explanation: The specified load module was not found in the library allocated under the XTASKLIB ddname. This condition precludes referencing of fields with secondary base locators. XPD0103 RDB FOR FIELD RETRIEVAL HAS NO EDB NOTIFY TECHNICAL SUPPORT Module: ADSRA189 Explanation: The XPEDITER element display block retrieve module has been passed a record display block without an EDB pointer. User Response: This condition must be reported to your internal technical support. XPD0104 NESTING DEPTH OF 24 EXCEEDED FOR X(30) Module: ADSRA189 Explanation: The maximum record hierarchy depth of twenty-four levels has been exceeded for the specified data element. As a result, the processing of the current command is terminated. User Response: None.
  22. 22. 2-4 XPEDITER/TSO and XPEDITER/IMS Messages and Codes XPD0105 RECORD HIERARCHY LEVEL COUNT NEGATIVE NOTIFY TECHNICAL SUPPORT Module: ADSRA189 Explanation: The level counter used by the XPEDITER record hierarchy scan module was decremented until it became negative. Processing of the current command is terminated. User Response: This condition should be reported to your internal technical support. XPD0111 NO MODULES FOUND IN RB OR LOAD LISTS Module: ADSRA242 Explanation: An attempt was made to display the sizes of all modules in the RB or LOAD list, but none were found. User Response: This is presumed to be an XPEDITER problem; therefore, contact your internal technical support. XPD0113 EXECUTION CANNOT BE RESUMED WITH THE FOLLOWING INSTRUCTION - iiii oooo, MEMBER=lmod, MODULE=csect, OFFSET=nnnnnnnn, ADDRESS=nnnnnnnn Module: ADSRA129 Explanation: Execution of the application module could not be continued subsequent to XPEDITER processing. The reference point (PROC/STATE/OFFSET) must be changed before another test execution. The current test is terminated by this condition. The OFFSET is relative to the CSECT, unless it is ‘********’, and then it is relative to LMOD. User Response: None. XPD0118 SVRB SEARCH UNRESOLVED AFTER 5 LEVELS Module: ADSRA016 Explanation: SVRB could not be found after five levels of the request block chain were searched. User Response: Contact your internal technical support. XPD0121 UNCORRECTABLE I/O ERROR FOR MEMBER C(8) IN C(8) SYNAD GPR 1 CONTENTS = X(4) Module: ADSRA512 Explanation: An I/O error occurred during an attempt to access the MEMBER and DD as specified in the message. User Response: Verify correct use of DCB information for all datasets allocated per the DD specified. For example: XTASKLIB DD: Ensure that libraries have a RECFM of U and are usable load module libraries. XINCLUDE DD: Ensure that LRECL/BLKSIZE are valid and consistent for all datasets. XPD0125 XPEDITER = N(4) OTHER = N(4) TOTAL = N(4) Module: ADSRA242 Explanation: The accumulated totals of both XPEDITER and subpool zero are printed as the result of an XTEST ADSRA242 command. User Response: None. XPD0138 SIZE OF X(8) AT N(4) IS N(4) Module: ADSRA242 Explanation: This is an informational message printed to communicate the module size and location for XTEST ADSRA242. User Response: None.
  23. 23. XPEDITER/TSO Messages 2-5 XPD0150 I/O ERROR WHILE READING MODULE X(8) Module: ADSRA097 Explanation: There may be a problem with the module’s addressing mode. User Response: Contact your internal technical support. XPD0151 DELETE OF USER MODULE X(8) FAILED - RC = N(2) Module: ADSRA454 Explanation: An attempt to delete an XPEDITER or user module failed. User Response: Probable XPEDITER system error. Contact your internal technical support. XPD0152 TROUBLE CLOSING USER FILES X(8) Module: ADSRA020 and ADSRA097 Explanation: XPEDITER could not close user files. User Response: Either the files were not opened, or you need to try RETEST and then use the EXIT command. XPD0153 DD X(8) NOT OPEN, CANNOT DO FUNCTION Module: ADSRA097 Explanation: XPEDITER cannot perform any function on the indicated ddname and associated dataset because it is not open. User Response: None. XPD0154 ERROR DOING JFCB FOR DDNAME X(8) Module: ADSRA097 Explanation: An I/O operation error (possibly a READ error) was detected while the Job File Control Block was performed for the indicated ddname. User Response: None. XPD0155 NO STORAGE FOR RDJFCB GETMAIN Module: ADSRA559 Explanation: In the type N(13) form of the XA 2.2 RDJFCB, a GETMAIN was done and failed. User Response: Try a larger REGION size. XPD0157 TYPE 07 OF RDJFCB FAILED. CHECK THE FILE ALLOCATIONS. Module: ADSRA559 Explanation: In the type X’07’ form of the RDJFCB, a return code greater than zero was encountered. This should not happen at this point. User Response: Contact your internal technical support. XPD0159 THE ONLY OPTIONS FOR RA206 ARE OPEN (1), CLOSE (2), AND BLDL (3) Module: ADSRA097 Explanation: XPEDITER internal message. The OPTION parameter received in ADSRA097 is incorrect. User Response: Contact your internal technical support. XPD0160 TGT DID NOT POINT TO EXPECTED MCB Module: ADSRA130 Explanation: The Task Global Table did not point to the Module Control Block. User Response: Contact your internal technical support.
  24. 24. 2-6 XPEDITER/TSO and XPEDITER/IMS Messages and Codes XPD0162 NO TYPE T RECORD FOUND FOR TGT FIELD IN MODULE C(8) - CHANGE LOGGING SUSPENDED Module: ADSRA134 Explanation: One of the TGT (Task Global Table) fields required for review mode data change logging was not found in the DDIO file for the specified module. This condition is normally the result of execution with a down-level DDIO. Execution logging will continue. User Response: None. XPD0163 NO X(21) TGT ENTRY FOR X(8) Module: ADSRA458 Explanation: No TGT (Task Global Table) record of the specified type was found in the DDIO dataset member for the designated module. The absence of this record precludes determination of addresses for data elements with this type of base locator. User Response: Contact your internal technical support. XPD0164 X(21) IN THE TASK GLOBAL TABLE NOT INITIALIZED Module: ADSRA458 Explanation: The base locator assigned to the specified module and data element was not initialized. This situation normally is encountered when an attempt is made to reference an item with a secondary base locator before the indicated module is executed. User Response: None. XPD0165 INVALID DATA TYPE DETECTED FOR X(30) IN X(8) Module: ADSRA173 and ADSRA680 Explanation: An unrecognized data type code was found in the DDIO dataset record for the specified data element and module. User Response: None. XPD0180 FASTBREAK SUPPRESSED FOR X(8) Module: ADSRA374 Explanation: FastBreak cannot function for XPEDITER Release 3.0 or releases prior to it. User Response: None. XPD0199 USER MODULE X(8) DELETED Module: ADSRA454 Explanation: XPEDITER successfully deleted the specified module from memory. This occurs during “clean up” processing. XPD0239 MODULE NOT FOUND - X(8) Module: ADSRA017 Explanation: The specified module was not found in the dataset(s) referenced by the XTASKLIB DD. User Response: Check each library for the member. If not found, locate the member and include an appropriate allocation to the XTASKLIB DD. If the problem persists, contact your internal technical support. XPD0240 CONTROL STACK ENTRY MAXIMUM EXCEEDED Module: ADSRA017 Explanation: The module intercept control stack used by XPEDITER to maintain module transfer information exceeded 26 levels. User Response: Determine if the program hierarchy contains more than 26 levels of calls outstanding at any given time. If it does not, check for a module loop where the module calls itself. If unable to resolve the problem, contact your internal technical support.
  25. 25. XPEDITER/TSO Messages 2-7 XPD0250 NO LOAD MODULE FOUND FOR X(8) IN XTASKLIB DATA SET Module: ADSRA054 Explanation: No load module was found for the specified CSECT in the XTASKLIB dataset. User Response: Check your specified CSECT entry. XPD0251 DATA SET NAME X(44) INCORRECT OR COULD NOT BE ALLOCATED Module: ADSRA054 Explanation: The dataset name entered on the LOAD command was in error, or the temporary ddname had a conflict (XPLOADCW). User Response: Check your dataset name entry. XPD0252 DDNAME X(8) INCORRECT OR COULD NOT BE ALLOCATED Module: ADSRA054 and ADSRA097 Explanation: The ddname entered on the LOAD command was in error. User Response: Check your ddname entry. XPD0253 DDNAME LENGTH AS ENTERED IS INCORRECT Module: ADSRA054 Explanation: A maximum of eight (8) characters is allowed for the dataset name. User Response: Check your ddname entry. XPD0254 DSNAME LENGTH AS ENTERED IS INCORRECT Module: ADSRA054 Explanation: A maximum of 44 characters is allowed for the dataset name. User Response: Check your dsname entry. XPD0292 OPEN FAILED FOR DDNAME X(8) Module: ADSRA051, ADSRA097, and ADSRA223 Explanation: The specified ddname could not be opened. User Response: Verify that the ddname is present and that it contains the proper attributes. If the problem reoccurs, contact your internal technical support. XPD0311 BLDL FAILED FOR MODULE X(8) Module: ADSRA051 and ADSRA223 Explanation: The module specified could not be loaded for the reason given. User Response: Check for problems with the dataset. XPD0312 UNCORRECTABLE I/O ERROR FOR MEMBER X(8) IN X(8) SYNAD GPR 1 CONT N(4) Module: ADSRA051, ADSRA097, ADSRA099, and ADSRA223 Explanation: An error was encountered while an attempt was made to READ for a load module library found in the XTASKLIB concatenation. User Response: If the library is otherwise useable, contact your internal technical support. XPD0317 IDENTIFY FAILED FOR MODULE X(8) WITH A RETURN CODE OF N(2) Module: ADSRA495 and ADSRA497 Explanation: A module to be simulated was already loaded and resides in memory. The purpose of the IDENTIFY is to allow the return of an alternate entry point when a load macro is issued for the given module. A SET DYNAMIC command must appear before the first CALL command for the simulation to be effective. User Response: Contact your internal technical support.
  26. 26. 2-8 XPEDITER/TSO and XPEDITER/IMS Messages and Codes XPD0318 MAXIMUM NUMBER OF DYNAMIC MEMBERS EXCEEDED N(2) Module: ADSRA497 Explanation: The maximum number of dynamic members that can be maintained by XPEDITER exceeded XPEDITER capacity. Nothing can be done by the programmer to circumvent this problem. User Response: Contact your internal technical support. XPD0319 MAXIMUM NUMBER OF SIMULATED MEMBERS EXCEEDED N(2) Module: ADSRA495 Explanation: The maximum number of simulated members which can be maintained by XPEDITER exceeded XPEDITER capacity. Nothing can be done by the programmer to circumvent this problem. User Response: Contact your internal technical support. XPD0322 THE LOAD MODULE DID NOT BEGIN WITH IGZ OR CEE C(8) Module: ADSRA322 Explanation: This module only handles IGZ or CEE modules. User Response: Check the context of your load module entry. XPD0323 ATTEMPT TO LOAD C(8) FAILED - ABEND CODE = C(4) REASON CODE = X(1) Module: ADSRA322 Explanation: Could not load COBOL system module. User Response: Contact your internal technical support. XPD0324 CSECT C(8) WAS NOT LINK EDITED WITH THE SYSTEM MODULE C(8) Module: ADSRA322 Explanation: The CSECT could not be found in the system module. System library may not be allocated properly. User Response: Check your system library allocation. XPD0348 EXECUTION OF BEFORE/AFTER COMMAND FAILED Module: ADSRA508 Explanation: Before and after breakpoints could not be set for the indicated intercept module. User Response: Contact your internal technical support. XPD0349 PARSE OF SETUP COMMAND FAILED Module: ADSRA508 Explanation: Parsing failed for the indicated intercept module. User Response: Contact your internal technical support. XPD0352 OFFSET VALUE X(6) INVALID Module: ADSRA286 Explanation: The specified OFFSET contains nonhexadecimal equivalent data. Valid characters are 0 through 9 and A through F. The OFFSET string is terminated by the first blank or left parenthesis. User Response: Check the content of the specified OFFSET string. XPD0396 FIRST CALL COMMAND REQUIRES MODULE NAME Module: ADSRA455 Explanation: The first time a CALL command is entered, a module name is required. If the succeeding CALL command(s) references the same module and entry point, the CALL command can be specified without keywords.
  27. 27. XPEDITER/TSO Messages 2-9 User Response: Contact your internal technical support. XPD0397 LOAD MODULE X(8) NOT FOUND FOR X(8) IN XTASKLIB DATA SET Module: ADSRA455 Explanation: The specified load module was not found for the given CSECT. User Response: Verify that the module specified is located in one of the datasets found in the XTASKLIB DD concatenation. XPD0407 LOAD MODULE FOR X(8) NOT FOUND Module: ADSRA028 Explanation: No load module was found for the specified module. XPD0413 NO PROCEDURE DIVISION FOR X(8) LIST X(5) REJECTED Module: ADSRA208 Explanation: The specified module does not have a PROCEDURE DIVISION statement. The indicated list is rejected for the above reason. XPD0414 X(5) N(4) NOT FOUND IN X(8) Module: ADSRA208 Explanation: The specified module does not contain the requested type. Valid record types are A, B, D, E, G, H, I, P, R, S, T, W, X, Y, 1, 2, 3, 5, @, $, #. XPD0415 EXCESSIVE RECORD STRUCTURE DEPTH ENCOUNTERED WITH X(30) AT STATE N(6) Module: ADSRA208 Explanation: The specified identifier has an excessive record structure depth. XPD0419 NO ELEMENTARY ITEM FOR X(30) IN X(8) Module: ADSRA174 Explanation: No elementary item was found for the specified identifier in the module. XPD0420 CANNOT FIND SOURCE FOR DATA ITEM Module: ADSRA174 Explanation: No data item found. User Response: Verify the data item name. If the data item does exist, contact Compuware Technical Support. XPD0421 INSUFFICIENT MEMORY FOR EDB Module: ADSRA174 Explanation: There was insufficient memory for the element display block. XPD0422 ’(C,1),’ IS AN INVALID TYPE Module: ADSRA175 Explanation: The data conversation failed. The data item has an invalid type and cannot be converted. User Response: Verify the data item type. Contact Compuware Technical Support. XPD0423 EXCESSIVELY HIGH NUMBER Module: ADSRA175 Explanation: A number higher than 1,152,921,504,606,846,976 was encountered when an attempt was made to convert user-specified data to binary. User Response: Correct the data and try the command again. XPD0424 TYPE X(1) HAS LENGTH OF N(2) Module: ADSRA175
  28. 28. 2-10 XPEDITER/TSO and XPEDITER/IMS Messages and Codes Explanation: The length of the specified type exceeds the maximum length permitted. User Response: After determining the length of the field as found in the program, update and execute the command again. If the problem persists, contact your internal technical support. XPD0425 SOURCE LENGTH ZERO OR NEGATIVE Module: ADSRA175 Explanation: The data entered as the value of the field is null. User Response: Include the appropriate data, and try the command again. XPD0426 ZERO OR NEGATIVE TARGET LENGTH Module: ADSRA175 Explanation: The field, which is to contain the converted data, has a null length. User Response: Contact your internal technical support. XPD0427 SOURCE AND TARGET TYPE = X(1) Module: ADSRA175 Explanation: An internal conversion error was encountered. User Response: Contact your internal technical support immediately. XPD0428 SOURCE POINTER IS NULL Module: ADSRA175 Explanation: An internal conversion error was encountered. User Response: Contact your internal technical support immediately. XPD0429 TARGET POINTER IS NULL Module: ADSRA175 Explanation: An internal conversion error was encountered. User Response: Contact your internal technical support immediately. XPD0430 X(1) IS AN INVALID TARGET TYPE Module: ADSRA175 Explanation: The specified target type is invalid. The valid types include Z (zoned), P (packed), or B (binary). This error is not externally controllable. User Response: Contact your internal technical support immediately. XPD0438 X(7) ABEND AT X(4) IN C(8), HANDLER IS IN CONTROL Module: ADSRA304 Explanation: An ABEND occurred within the specified module at the specified offset, but an LE condition handler is registered. Control is passed to the condition handler. XPEDITER takes no action. User Response: None. The application’s registered condition handler received control for the abend. If you would like XPEDITER to handle the abend, alter your application to not register the condition handler. XPD0439 X(7) ABEND AT N(4) REASON CODE N(2) [non-LE/370 format] XPD0439 X(7) COND X(4) ABEND AT N(4) REASON CODE N(2) [LE/370 format] Module: ADSRA104, ADSRA105, and ADSRA304 Explanation: This message is generated when a system or user ABEND occurs during XPEDITER or user module execution. It is followed by additional information. User Response: If you have difficulty exiting the session, issue the RETEST command, and then the EXIT command.
  29. 29. XPEDITER/TSO Messages 2-11 XPD0440 NO DATA ELEMENTS IN TOKEN X(4) FOR MODULE C(8) Module: ADSRA187 Explanation: No data elements were found in the identifier for the specified module. User Response: Check the DDIO dataset for the indicated identifier and, if not present, contact your internal technical support. XPD0441 INVALID DATA TYPE FOR INIT Module: ADSRA187 Explanation: The data type, as found in the DDIO dataset, is invalid. User Response: Contact your internal technical support. XPD0442 NO MEMORY FOR RIM CONTROL BLOCK Module: ADSRA187 Explanation: XPEDITER attempted to obtain memory in which to build an important control block. User Response: Contact your internal technical support. XPD0443 NO RDB FOR ITEM TOKEN X(4) IN C(8) Module: ADSRA187 Explanation: An error occurred while XPEDITER was attempting to locate an internal control block (the RDB). User Response: Contact your internal technical support. XPD0444 NO MEMORY FOR RECORD RDB Module: ADSRA187 Explanation: XPEDITER attempted to obtain memory for an important control block, but was unsuccessful. User Response: Increase the region size and try the test again. XPD0455 MODULE X(8) CONTAINS ONE OR MORE UNRESOLVED EXTERNAL REFERENCES Module: ADSRA222 Explanation: The specified load module was link edited with unresolved external references. XPEDITER recognized this and will try to resolve these external references if the module is called. User Response: Resolve the external references if XPEDITER is unable to do so. If conflicts still exist, contact your internal technical support. XPD0460 TROUBLE CLOSING USER FILES Module: ADSRA020 Explanation: This message is no longer valid. User Response: None. XPD0461 XPEDITER FORCE CLOSING OF DDNAME = X(8) Module: ADSRA020, ADSRA442 Explanation: During test termination, XPEDITER detected that the file allocated to the indicated DDNAME was left open. XPEDITER then attempted to close the file. User Response: None. XPD0468 UNRESOLVED STATIC REFERENCE TO MODULE X(8) HAS BEEN TREATED AS DYNAMIC Module: ADSRA098 Explanation: The load module contained a static call to a module which was unresolved. XPEDITER will load from the XTASKLIB DD if not simulated. This message is only a warning.
  30. 30. 2-12 XPEDITER/TSO and XPEDITER/IMS Messages and Codes XPD0469 COMMAND NAME INVALID Module: ADSRA553 Explanation: An invalid command or option relating to the XCOMPILE or XSYMDIR maintenance was entered. XPD0472 ERROR LOADING X(8) Module: ADSRA222 Explanation: An error was encountered processing the control records in the listed member. User Response: Ensure that the name is a valid member of the library defined by the XTASKLIB DD. XPD0473 NO RLD ENTRIES X(8) Module: ADSRA222 Explanation: The module being loaded has been read to the end of file condition and no RLD or CTL records were found. User Response: Check the link edit for errors. XPD0498 BREAKPOINT AT STATE N(3) OFFSET N(3) IN MODULE X(8) HAS BEEN MODIFIED. Module: ADSRA604 Explanation: The breakpoint specified cannot be reset because it has been modified. The user program may have self-modifying code. Processing is terminated. XPD0529 END OF FILE ENCOUNTERED ON X(8). THE LAST RECORD IS USED FOR ANY LATER ASSIGNS FROM THIS FILE. Module: ADSRA170 Explanation: The file specified on an ASSIGN command using the DDN PARM encountered an end-of-file. This, and all subsequent ASSIGNs from this file, will use the last record. XPD0558 OPTION SUPPLIED TO ADSRA005 IS INVALID Module: ADSRA558 Explanation: A request to ADSRA558 is unknown. User Response: An internal error has occurred. Contact Compuware Technical Support. XPD0559 ADSRA558 GETMAIN REQUEST FAILED Module: ADSRA558 Explanation: A GETMAIN request failed for ADSRA558. User Response: Increase storage allocation for XPEDITER. If the problem continues, contact Compuware Technical Support. XPD0560 NO JFCB POINTER CREATED IN ADSRA558 Module: ADSRA558 Explanation: JFCB pointer was not created. User Response: Contact Compuware Technical Support. XPD0564 NO INDEX CELLS IN TGT FOR X(8) Module: ADSRA028 Explanation: No index cells were listed in the TGT for the specified module. XPD0565 NO DATA DIVISION ENTRIES FOR X(8) Module: ADSRA028 Explanation: No data division entries were listed for the specified module.
  31. 31. XPEDITER/TSO Messages 2-13 XPD0566 NO ITEM FOR INDEX X(30) IN X(8) Module: ADSRA028 Explanation: No identifier was listed for the specified index. XPD0568 UNABLE TO LOAD X(8) LIBRARY ROUTINE X(8) FROM XTASKLIB DATA SET Module: ADSRA227 Explanation: XPEDITER attempted to load a library subroutine for the specified language type to resolve external references in a user program. The subroutine was not found in the XTASKLIB dataset. User Response: Relink the module or include the library subroutines in the XTASKLIB concatenation. XPD0570 ERROR UPDATING XDYNAMIC DATA SET MEMBER X(8) TO X(8) RC=N(4) Module: ADSRA051 Explanation: The STOW macro failed for the specified module. XPD0571 NOTE LIST NOT SUPPORTED FOR LOAD MODULE X(8) Module: ADSRA051 Explanation: The NOTE LIST for load modules is not supported. XPD0572 ERROR WITH IEWBIND FUNC=LOADW, (module name) IS A (“PROGRAM OBJECT” or “LOAD MODULE”) AND THE XDYNAMIC DATASET IS A (“PDS” or “PDSE”). Module: ADSRA051 Explanation: A critical error occurred using the IEWBIND macro. User Response: If you are using program objects and the XDYNAMIC dataset is a PDS, make the XDYNAMIC dataset a PDSE. Otherwise contact Compuware Technical Support. The XDYNAMIC “Dataset type” can be changed via the test panel by entering the SEtup, Extended, and Work commands. XPD0573 UNRESOLVED STATIC REFERENCE TO MODULE X(8) COULD NOT BE RESOLVED Module: ADSRA098 Explanation: The load module contained a static call to a module which was unresolved. XPEDITER was unable to load the module from XTASKLIB DD. The test will be terminated. XPD0574 TRANSFER REFERENCE TO MODULE X(8) COULD NOT BE RESOLVED Module: ADSRA098 Explanation: The load module contains a transfer module, and a call was made to a module that could not be found in the XTASKLIB DD. The test will be terminated. XPD0575 NO DYNAMIC CALL BLOCK FOUND FOR DYNAMIC INTERCEPT Module: ADSRA594 Explanation: No dynamic call block was found for the dynamic intercept. User Response: Contact your internal technical support. XPD0576 ERROR WITH IEWBIND FUNC=SAVEW, (module name) IS A (“PROGRAM OBJECT” or “LOAD MODULE”) AND THE XDYNAMIC DATASET IS A (“PDS” or “PDSE”). Module: ADSRA051 Explanation: A critical error occurred using the IEWBIND macro. User Response: If you are using program objects and the XDYNAMIC dataset is a PDS, make the XDYNAMIC dataset a PDSE. Otherwise contact Compuware Technical Support. The XDYNAMIC “Dataset type” can be changed via the test panel by entering the SEtup, Extended, Work commands. XPD0601 NO MODULE CONTROL BLOCK FOUND TO RESET FOR MODULE X(8) Module: ADSRA058
  32. 32. 2-14 XPEDITER/TSO and XPEDITER/IMS Messages and Codes Explanation: There is no module control block for the module specified. This module may not be a member of the load module, or the load module may not have been loaded. XPD0602 NO OUTSTANDING SKIP FOR MODULE X(8) Module: ADSRA058 Explanation: After skipping the modules, if they are to be reset, they must be loaded. If they cannot be loaded, then recovery is accomplished with a RETEST command. XPD0603 KEYWORD IS MISSING FOR THE SHOW COMMAND. Module: ADSRA245 Explanation: The keyword is missing for the SHOW command. User Response: Reenter the command with the keyword. See the XPEDITER/TSO and XPEDITER/IMS Quick Reference or Reference Manual for valid keywords. XPD0604 ONLY SUBPOOL 0 CAN BE DISPLAYED. Module: ADSRA245 Explanation: Only subpool 0 can be displayed. User Response: Reenter command specifying subpool 0. XPD0605 SKIP CANNOT BE DELETED FROM MODULE ’,(C,8),’ Module: ADSRA058 Explanation: The module has a dummy MOB. Therefore the control blocks for the module are not complete. User Response: ’INTERCEPT’ the program to force the completion of XPEDITER control blocks. XPD0607 X(8) REQUESTED N(4) BYTES - TOTAL IS N(4) Module: ADSRA212 Explanation: The indicated XPEDITER module has requested the specified amount of memory. The total amount allocated in the current session is also displayed. The generation of this message is triggered by assigning the XPEDITER $CONCODE variable a value of 1092. It is suppressed when the value is changed. XPD0610 INVALID KEYWORD X(16) Module: ADSRA245 Explanation: The keyword is invalid for the SHOW command. User Response: Reenter the command with a proper keyword. See the XPEDITER/TSO and XPEDITER/IMS Quick Reference or Reference Manual for valid keywords. XPD0614 NO ENTRY POINT FOUND FOR X(8) IN MODULE X(8) Module: ADSRA455 Explanation: An invalid entry point name was specified for the given load module. User Response: Look at the ENTRY USING parameter list to determine the proper name of the entry point. If some question arises as to the way the load module is link edited, use the MVS AMBLIST utility to generate a link map. XPD0629 SET DYNAMIC WAS NOT THE FIRST REFERENCE TO MODULE X(8) SET DYNAMIC NOT DONE Module: ADSRA497 Explanation: A SET DYNAMIC must be the first reference to an Assembler module that is going to be called dynamically. XPD0678 DEFAULT C(8) LIST HAS BEEN REPLACED BY SET C(8) COMMAND Module: ADSRA055
  33. 33. XPEDITER/TSO Messages 2-15 Explanation: The default list, as found in the global defaults module (ADSRA093), was replaced by the list of modules or DDNAMEs as specified on the XPEDITER SET EXCLUDE/NOCANCEL/DDIGNORE command. XPD0700 XPEDITER INTERNAL TABLE OVERFLOW Module: ADSRA227 Explanation: The XPEDITER internal table for resolving external references in library subroutines exceeded its limit. User Response: Relink the module without NCAL to continue testing, and contact your internal technical support. XPD0732 MAXIMUM NUMBER OF “EXCLUDE” ENTRIES (100) HAS BEEN EXCEEDED Module: ADSRA055 Explanation: The module exclusion list, which is created and updated by the SET EXCLUDE command, cannot contain more than 100 entries. User Response: Contact your internal technical support. XPD0733 CURRENT C(8) LIST HAS BEEN UPDATED TO INCLUDE NEW ENTRIES FOR THE SET C(8) COMMAND Module: ADSRA055 Explanation: The list, which is created and updated by the SET EXCLUDE/NOCANCEL/DDIGNORE command, was updated to include the entries specified. XPD0743 LOAD MODULE X(8) NOT DELETED - DATA HAS BEEN LOGGED FOR ROUTINE X(8) Module: ADSRA085 Explanation: Review mode logging was activated and logged execution information for the specified routine. The load module containing this routine cannot be deleted or cancelled. XPD0745 ATTEMPT TO DELETE MODULE X(8) FAILED WITH RETURN CODE OF N(2) Module: ADSRA085 Explanation: The module specified as the positional value of the DELETE command cannot be handled by the system. The return code from GPR 15 is displayed in hexadecimal format. This module can be statically linked and cannot be deleted. XPD0747 X(8) CANNOT BE DELETED - IT IS A SIMULATED MODULE Module: ADSRA085 Explanation: The module specified as the positional value of the DELETE command is not a load module. It is a dummy module that cannot be deleted. XPD0748 NO DYNAMIC CALL BLOCK FOUND FOR X(8) - CONTACT TECHNICAL SUPPORT Module: ADSRA085 Explanation: The DELETE request could not be satisfied because a special XPEDITER internal control block could not be located. The pseudo module name associated with the control block appears in the message. XPD0768 NO BREAKPOINT TABLE ENTRY FOR OFFSET N(4) IN MODULE X(8) Module: ADSRA130 and ADSRA478 Explanation: No matching offset could be found in the statement breakpoint table corresponding to the interrupt address. User Response: The material required to recreate the problem should be forwarded to your internal technical support. XPD0779 COBOL SORT IN PROGRESS AT TERMINATION Module: ADSRA269 Explanation: This informational message is issued to make you aware that a premature end of a COBOL SORT was initiated. This occurred either because of an abnormal termination, or
  34. 34. 2-16 XPEDITER/TSO and XPEDITER/IMS Messages and Codes because an XPEDITER EXIT was issued while within an interactive PAUSE. Special processing is required by XPEDITER to close the COBOL SORT work file(s). XPD0798 TABLE CAPACITY OF N(2) EXCEEDED FOR PTRTABLE Module: ADSRA001 Explanation: The maximum number of system control parameters, which can be maintained by XPEDITER, was exceeded. User Response: This problem cannot be circumvented and should be reported to your internal technical support. XPD0804 DIAGNOSE DUMP Module: ADSRA148 Explanation: You requested a dump of the XPEDITER session. The task abends with a user 3009 ABEND. XPD0805 OPTION INVALID Module: ADSRA148 Explanation: An invalid action was requested on the DIAGNOSE command. Valid actions include: TRAMON - TRACE MONITOR NOTMON - Turn Off MONITOR TRACE TRASIM - TRACE SIMULATE NOTSIM - Turn Off SIMULATE TRACE TRAXFR - TRACE TRANSFER NOTXFR - Turn Off TRANSFER TRACE TRACHK - TRACE CHECK NOTCHK - Turn Off CHECK TRACE TRAPRI - TRACE PRIMARY NOPRI - Turn Off PRIMARY TRACE BOMB - ABEND W/U3000 ADSRANNN - Invoke XPED Module RATON - TRACE XPED CALL RATOFF - Turn Off XPED CALL TRACE XPD0806 MODULE NAME UNKNOWN TO XPEDITER Module: ADSRA148 Explanation: The DIAGNOSE ADSRANNN option was specified, but the requested module could not be found. This facility is not generally used by application programmers. User Response: If a problem exists, contact your internal technical support. XPD0820 UNKNOWN TRANSLATOR TYPE = X(10) FOR MODULE X(8) INFORMATION ONLY Module: ADSRA252 Explanation: An unknown type of translator was found in the IDR records. User Response: This message should be communicated to your internal technical support. XPD0844 NO SORT-RETURN FOR ANS68 VER 2 COBOL Module: ADSRA409 Explanation: SORT-RETURN is allowed in Versions 3 and 4 of ANS 68 COBOL, but not Version 2. Do not use with this version of COBOL. XPD0850 ERROR WHILE PROCESSING DDNAME X(8) FREE DATA SET AND REALLOCATE CORRECTLY Module: ADSRA170 Explanation: An error occurred while the dataset with the indicated ddname was being read. If the dataset is a PDS, the member name may be incorrectly spelled or nonexistent. User Response: The file must be freed and the dataset with correct member reallocated.
  35. 35. XPEDITER/TSO Messages 2-17 XPD0851 0 WARNING: BLDL FAILED DURING XPEDITER COBOL TRAP PROCESSING FOR MEMBER X(8). Module: ADSRA477 Explanation: This is an XPEDITER internal error and will not affect program execution. User Response: You can use GO to continue. This condition should be reported to your internal technical support. XPD0852 DDNAME X(8) HAS NOT BEEN ALLOCATED Module: ADSRA170 Explanation: The ddname was not allocated. User Response: The XPEDITER/TSO ALLOCATE command can be used to allocate the ddname while in the TSO session. XPD0853 THIS DDNAME X(8) MUST POINT TO A PS DATA SET Module: ADSRA170 Explanation: This ddname must have a physical sequential dataset, or the member name must be added. XPD0854 MORE THAN 600 MODULES DYNAMICALLY LOADED Module: ADSRA051 Explanation: Too many modules were dynamically loaded. User Response: Contact Compuware Technical Support. XPD0863 FILE NAME X(8) FILE TYPE, TEXT NOT FOUND Module: ADSRA455 Explanation: The specified file name was not found for the given CALL. User Response: Verify that the module with the file type TEXT exists on the user disk. XPD0864 PREVIOUS COMMANDS FOR X(8) ARE OF NO EFFECT - DIFFERENT COPY OF MODULE LOADED BY PEM - LINK PARM OF REUS REQUIRED Module: XPHOGNCQ Explanation: PEM invoked a module that was previously loaded by XPEDITER during the processing of one or more commands that made reference to the designated module. Because the module was not linked with the REUS PARM, PEM loaded a fresh copy of the module, negating the XPEDITER processing for the original copy. User Response: If the module cannot be recompiled or relinked, XPEDITER reference to the module should be deferred until it is loaded by PEM. This can be done with a conditionally executed BEGIN group associated with a CALL or TRANSFER command. Processing continues after the message. XPD0865 X(8) NOT LINKED WITH REUS PARM Module: XPHOGNCQ Explanation: HOGAN application modules should be link edited with the REUS PARM. This is a warning message since no XPEDITER function is impaired for the designated module. XPD0868 PECNTL FILE NOT ALLOCATED Module: ADSRA284 Explanation: Use of PANEXEC with one of the XPEDITER products requires that a PECNTL DD be allocated. User Response: Contact your internal technical support. XPD0869 %CONCAT PANEXEC CONTROL CARD NOT FOUND IN PECNTL Module: ADSRA284 Explanation: A %CONCAT PANEXEC control card was not found in PECNTL.
  36. 36. 2-18 XPEDITER/TSO and XPEDITER/IMS Messages and Codes User Response: Contact your internal technical support. XPD0871 CANNOT FIND MODULE X(8) Module: ADSRA129 Explanation: The MCB could not be found for this module. Severe error. User Response: Contact your internal technical support. XPD0872 X(8) WAS NOT LOADED - MODULES LINKED WITH RMODE ANY CANNOT BE TESTED Module: ADSRA051 and ADSRA223 Explanation: The module specified was not loaded by XPEDITER because the VS attribute flags in the associated library directory entry indicated that it had been link edited with RMODE ANY. User Response: If this message occurs after XPEDITER/TSO is installed, contact your internal technical support. XPD0873 31-BIT ADDRESSING MODE WAS DETECTED AT THE TIME MODULE X(8) WAS RETURNING TO MODULE X(8) Module: ADSRA274 Explanation: The addressing mode was changed from 24-bit to 31-bit mode by the specified module. XPEDITER changes the mode back to 24-bit and terminates the test instead of returning control to the calling module. User Response: If this message occurs after XPEDITER/TSO is installed, contact your internal technical support. XPD0881 MODULE X(8) ALREADY IN MEMORY OR IN LPA LIB, INTERCEPT BYPASSED Module: ADSRA497 Explanation: The specified module could not be intercepted under XPEDITER control because it was already resident in real memory or in the link pack area. User Response: Contact your internal technical support. XPD0884 MODULE X(8) COULD NOT BE FOUND IN THE XPEDITER OR USER LIBRARY OR STEPLIB Module: ADSRA497 Explanation: The CTLCBLII installation default parameter was set to prevent the use of DDIO dataset information for testing the specified module. XPD0889 PANEXEC CONTROL CARD DD STATEMENT NOT FOUND Module: ADSRA051 and ADSRA223 Explanation: The PANEXEC control card file was not allocated. User Response: Allocate the file and retry. XPD0890 INSUFFICIENT STORAGE FOR FILE LRP Module: ADSRA405 User Response: The REGION parameter for the TSO session or the batch JOB should be increased. XPD0891 INSUFFICIENT STORAGE FOR FILE FDB Module: ADSRA405 User Response: The REGION parameter for the TSO session or the batch JOB should be increased. XPD0892 INSUFFICIENT STORAGE FOR FILE BUFFER Module: ADSRA405 User Response: The REGION parameter for the TSO session or the batch JOB should be increased.
  37. 37. XPEDITER/TSO Messages 2-19 XPD0893 MODULE NAME INVALID FOR FILE BUFFER Module: ADSRA553 Explanation: The module name was not located in the XCOMPILE or XSYMDIR datasets. XPD0894 CAN’T FIND OPERAND1 Module: ADSRA553 Explanation: The first operand is missing for the command. XPD0895 NO XSYMDIR RECORD Module: ADSRA553 Explanation: XSYMDIR does not contain the record for KAYS support. User Response: Recompile with XPEDITER and try again. XPD0896 CAN’T FIND OPERAND2 Module: ADSRA553 Explanation: The second operand is missing for the command. XPD0897 NO XSYMDIR RECORD Module: ADSRA553 Explanation: The record was not found in the XSYMDIR dataset. User Response: Make sure that it was compiled with XPEDITER. XPD0898 INSUFFICIENT DIRECTORY SPACE IN XCOMPILE Module: ADSRA553 User Response: Reallocate the XCOMPILE dataset with a larger directory block. XPD0899 INSUFFICIENT VIRTUAL STORAGE FOR STOW Module: ADSRA553 User Response: The REGION size for the TSO session or the batch JOB should be increased. XPD0900 XSYMDIR DATASET PERMANENT I/O ERROR Module: ADSRA553 Explanation: Cannot access the XSYMDIR dataset. User Response: Contact your internal technical support. XPD0902 ESTAE EXIT ENTERED - DUMP TAKEN Module: ADSRA553 Explanation: The program encountered ESTAE EXIT and a dump was taken. Control was transferred to EPILG000. XPD0904 INVALID OPERAND PAIR Module: ADSRA553 Explanation: Invalid operands were entered for the command. XPD0911 MODULE X(8) HAS OVERLAY FORMAT - NOT SUPPORTED BY XPEDITER Module: ADSRA223 Explanation: This is a warning message, but it should be heeded if you want to set breakpoints in any areas where overlay structures occur. User Response: The module should be recompiled without overlays in order to permit the use of DDIO information for testing purposes. XPD0912 ATTEMPT TO LOAD X(8) FAILED - ABEND CODE = X(3) REASON CODE = N(1) Module: ADSRA054 and ADSRA223
  38. 38. 2-20 XPEDITER/TSO and XPEDITER/IMS Messages and Codes Explanation: The specified module could not be loaded for the reason indicated by the ABEND code and the reason code. Typically, this is a MODULE MARKED NOT EXECUTABLE problem, such as an S706. XPD0915 MODULE X(8) NOT AUTOMATICALLY CANCELLED - BREAKPOINTS HAVE PREVIOUSLY BEEN SET Module: ADSRA274 Explanation: The specified module was not deleted at the time of return to its dynamic VS COBOL II caller. This is supported in XPEDITER/TSO. User Response: If this message occurs after XPEDITER/TSO is installed, contact your internal technical support. XPD0916 ACCEPT REJECTED FOR DDNAME X(8) RECORD FORMAT MUST BE EITHER FIXED OR VARIABLE Module: ADSRA170 Explanation: This ddname must have a physical sequential dataset, or the PDS member name must be added. XPD0917 INPUT ERROR OCCURRED FOR DDNAME X(8) Module: ADSRA170 Explanation: This ddname must have a physical sequential dataset, or the PDS member name must be added. XPD0955 SPECIAL MCB BUILT FOR MEMBER X(8) Module: ADSRA222 Explanation: This is an informational message only. XPEDITER will not attempt to read any information from a load module; however, a generic MCB (module control block) for the load module is built. No submodules within the load module can be accessed during the test. XPD0965 RETEST WITHOUT A NEW COPY CANNOT BE VALID Module: ADSRA444 Explanation: To retest, a new copy of the program must occur. Due to line edit options, a new copy of the program is required. User Response: Issue the RETEST command with a NEWCOPY option. XPD0966 RETEST WITHOUT NEW COPY CANNOT BE USED WITH REVIEW MODE OPTION Module: ADSRA444 Explanation: The user is in a REVIEW mode. User Response: Exit the REVIEW mode and reissue the RETEST command. XPD0997 INVALID INSTRUCTION DETECTED. BREAKPOINTING CONFLICT !! Module: ADSRA104 Explanation: A breakpoint instruction has been encountered which was not placed by XPEDITER. The XPEDITER SVC or TEST instruction has occurred within the user’s code or a supporting product. These instructions are not supported in a debugging session unless placed by XPEDITER. User Response: The PSW address indicates the location of the offending instruction. If the instruction was not compiled as part of the user’s application and there is no active product utilizing the instruction, contact Compuware Technical Support. XPD0998 PEM DELETES FOR X(8) CANNOT BE SUPPRESSED - NEITHER REENTRANT NOR REUSABLE Module: XPHOGNCQ Explanation: The SET NOPEMDEL facility is valid only for HOGAN programs that have been link edited with either the REUS or RENT parameters.

×