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

XPEDITER/TSO and XPEDITER/IMSMessages and Codes

Release 7.2

ii XPEDITER/TSO and XPEDITER/IMS Messages and Codes

This docum

Copyright 1Copyright L

U.S. GOVERrestrictions 227.7202-1(FAR 52.227-

This producdisclosure, oCorporationconditions o

XPEDITER, Ctrademarks o

IBM, CICS, D

CA-MIM, CAtrademarks o

Adobe ® AcrAdobe and A

All other co

Doc. CWXTMX

December 30, 2

Please direct questions about XPEDITER/TSO and XPEDITER/IMSor comments on this document to:

XPEDITER/TSO and XPEDITER/IMS Technical SupportCompuware Corporation

31440 Northwestern HighwayFarmington Hills, MI 48334-2564

1-800-538-7822

Outside the USA and Canada, please contact your local Compuware office or agent.

ent and the product referenced in it are subject to the following legends:

996-2003 Compuware Corporation. All rights reserved. Unpublished rights reserved under the aws of the United States.

NMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to as set forth in Compuware Corporation license agreement and as provided in DFARS a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), 19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation.

t contains confidential information and trade secrets of Compuware Corporation. Use, r reproduction is prohibited without the prior express written permission of Compuware . Access is limited to authorized users. Use of this product is subject to the terms and f the user's License Agreement with Compuware Corporation.

ode Coverage, File-AID, Abend-AID, FrontLine, and Compuware Shared Services are r registered trademarks of Compuware Corporation.

B2, and MQSeries are trademarks of International Business Machines Corporation.

-ROSCOE, ENDEVOR, LIBRARIAN, PANEXEC, and PANVALET are trademarks or registered f Computer Associates International, Inc.

obat ® Reader copyright © 1987-2002 Adobe Systems Incorporated. All rights reserved. crobat are trademarks of Adobe Systems Incorporated.

mpany and product names are trademarks or registered trademarks of their respective owners.

7C

002

iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vSummary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

What’s New in Release 7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vForeground DB2 Stored Procedure Support. . . . . . . . . . . . . . . . . . . . . . vGeneric IDs with DB2 Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . vRetention of IMS Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vDB2 Group Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vSupport for z/OS 1.3 and 1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vIMS Release 8.1 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vAdditional Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

What’s New in Release 7.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viToleration Support for VisualAge PL/I . . . . . . . . . . . . . . . . . . . . . . . . . . viIMS UserID Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiDB2 Support Extended to DB2 Release 7.1 . . . . . . . . . . . . . . . . . . . . . viiDB2 Trigger and UDF Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiSMP/E Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiAdditional Features: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixManual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixIntended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixOperating Environment Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixAccessing Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xNotation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

VisualAge PL/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiRelated Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiDocumentation Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

FrontLine Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiOnline Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiWorld 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-1XPEDITER/ROS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1Condition 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

iv XPEDITER/TSO and XPEDITER/IMS Messages and Codes

v

Preface Sum_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 ChangesThis 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.

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.

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.

viii XPEDITER/TSO and XPEDITER/IMS Messages and Codes

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 OrganizationThe 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 AudienceGenerally, 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 SupportXPEDITER/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

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 ProductsXPEDITER/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 RulesThe 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.

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 PublicationsThe 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

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

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 HelpAt 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 SupportCompuware Corporation

31440 Northwestern HighwayFarmington Hills, MI 48334-2564

1-800-538-7822

Outside the USA and Canada, please contactyour 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

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.

1-1

Chapter 1.
1SIR to DDIO Utility Messages Chap 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.


SSU0024 SYNAD EXIT TAKEN FOR SIR DATASET

Module: ADSSU002

Explanation: A SYNAD error occurred while attempting to read the SIR PDS.


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



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.

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


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.


Module: ADSSU101




Module: ADSSU101


SIR to DDIO Utility Messages 1-3


SSU1015 SIR OPTIONS RECORD NOT FOUND

Module: ADSSU101

Explanation: The utility could not locate a SIR record.


SSU1117 FATAL ERROR - CONTACT TECHNICAL SUPPORT

Module: ADSSU204


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.


SSU1204 RECOMMENDED FORMAT PARAMETERS:

Module: ADSSU120



SSU1510 GETMAIN FOR SIR BUFFER FAILED

Module: ADSSU151

Explanation: A GETMAIN equal in size to the block size of the SIR PDS failed.


SSU1511 OBTAIN FAILED FOR SIR DATASET

Module: ADSSU151

Explanation: An OBTAIN returned a non-zero return code.


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.



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.


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.


2-1

Chapter 2.
2XPEDITER/TSO Messages Chap 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.


XPD0007 ESTAE MACRO ERROR - RETURN CODE X(2)

Module: ADSRA105

Explanation: A critical error occurred while a STAE/ESTAE macro was being issued.


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.


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.

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)


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.



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.


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.


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.


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.



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

Module: ADSRA097

Explanation: There may be a problem with the module’s addressing mode.


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)


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.


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.


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.


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.


XPD0160 TGT DID NOT POINT TO EXPECTED MCB

Module: ADSRA130

Explanation: The Task Global Table did not point to the Module Control Block.



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.


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.


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.


XPD0165 INVALID DATA TYPE DETECTED FOR X(30) IN X(8)


Explanation: An unrecognized data type code was found in the DDIO dataset record for the specified data element and module.


XPD0180 FASTBREAK SUPPRESSED FOR X(8)

Module: ADSRA374

Explanation: FastBreak cannot function for XPEDITER Release 3.0 or releases prior to it.


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.


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


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)


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)


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)


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.



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.


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.


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.


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.


XPD0349 PARSE OF SETUP COMMAND FAILED

Module: ADSRA508

Explanation: Parsing failed for the indicated intercept module.


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.



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


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.


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



XPD0429 TARGET POINTER IS NULL

Module: ADSRA175



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.


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]


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.


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.


XPD0442 NO MEMORY FOR RIM CONTROL BLOCK

Module: ADSRA187

Explanation: XPEDITER attempted to obtain memory in which to build an important control block.


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).


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



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.


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.


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.


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.


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.


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


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


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.


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)


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


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 MONITORNOTMON - Turn Off MONITOR TRACETRASIM - TRACE SIMULATENOTSIM - Turn Off SIMULATE TRACETRAXFR - TRACE TRANSFERNOTXFR - Turn Off TRANSFER TRACETRACHK - TRACE CHECKNOTCHK - Turn Off CHECK TRACETRAPRI - TRACE PRIMARYNOPRI - Turn Off PRIMARY TRACEBOMB - ABEND W/U3000ADSRANNN - Invoke XPED ModuleRATON - TRACE XPED CALLRATOFF - 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.


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.


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.


XPD0869 %CONCAT PANEXEC CONTROL CARD NOT FOUND IN PECNTL

Module: ADSRA284

Explanation: A %CONCAT PANEXEC control card was not found in PECNTL.



XPD0871 CANNOT FIND MODULE X(8)

Module: ADSRA129

Explanation: The MCB could not be found for this module. Severe error.


XPD0872 X(8) WAS NOT LOADED - MODULES LINKED WITH RMODE ANY CANNOT BE TESTED


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.


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.


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


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


XPD0892 INSUFFICIENT STORAGE FOR FILE BUFFER

Module: ADSRA405



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.


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)



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.


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.


XPD0999 USER REQUESTED S0C1 DUMP HAS BEEN CREATED, GPR 0 WILL POINT TO A REGISTER SAVE AREA IN THE FORM OF GPR 0-15, GPR 15 WILL POINT TO THE ORIGINAL INTERRUPT ADDRESS, ORIGINAL GPR VALUES ARE IN SAVE AREA

Module: ADSRA104

Explanation: You requested a dump after a S0C1 ABEND, and set ABNDEXIT OFF and ABNDDUMP ON. This forces a dump, but GPR 0 points to a save area with 0-15 and GPR 15 to the ABEND address.

XPD1000 BTS INTERCEPTION BYPASSED BY XPEDITER

Module: XPTSO

Explanation: Because no program or trancode was entered for a BTS intercept, XPEDITER will not perform any intercepts for this BTS run.

XPD1001 NO MODULE NAME ON TEST COMMAND

Module: XPDRP and XPTSO

Explanation: The syntax for the TEST command requires that a program name be one of the operands. The command has no meaning without it.

XPD1002 NO TEST COMMAND ENTERED

Module: XPTSO

Explanation: A batch XPEDITER/TSO test requires at least one TEST command to specify the module to be tested.

XPD1003 XPOUT DD CARD MISSING, NOTHING SPOOLED

Module: XPTSO

Explanation: The XPOUT DD refers to the XPEDITER/TSO log. If it is not present, you cannot spool (log) the output from a test.

XPD1004 NO PARMS ENTERED FOR IMS TEST


Explanation: When testing an IMS program, XPEDITER/TSO needs a PARM string containing such information as the PSB, the type of test, and so forth. In batch, this is in the JCL; in interactive testing, it should come from the installation defaults, based on the PARM entered on the IMS test screen in the PARM Passing Option field.

XPD1005 NO PARMS ENTERED FOR BTS TEST

Module: XPTSO

Explanation: When testing a BTS program, XPEDITER/TSO needs a PARM string containing such information as the PSB, the type of test, and so forth. In batch, this is in the JCL; in interactive testing, it should come from the installation defaults, based on the PARM entered on the IMS test screen in the PARM Passing Option field.

XPD1007 FIRST COMMAND MUST BE XPED COMMAND

Module: XPTSO

Explanation: In a batch XPEDITER/TSO test, the first command must be an XPED command. This command identifies the environment to be used for the test.

XPD1008 NO MODULE NAME ON INTERCEPT COMMAND

Module: XPTSO

Explanation: The INTERCEPT command requires a program name to identify the program to be tested. The transaction name is not sufficient, because there can be more than one program per transaction.

XPD1009 TOO MANY XPED COMMANDS ENTERED


Explanation: The maximum number of XPED commands that can be entered for a batch or interactive test is one.


XPD1010 ERROR IN ENVIRONMENT ON XPED COMMAND


User Response: For the list of valid environments, consult the XPEDITER/TSO and XPEDITER/IMSXPEDITER/TSO Reference Manual.

XPD1011 ONLY ONE TEST COMMAND ALLOWED IN IMS


Explanation: An attempt was made to perform more than one test in a single IMS/DRP test session. This is not permitted.

XPD1012 TOO MANY INTERCEPT COMMANDS ENTERED


Explanation: The maximum number of INTERCEPT commands that can be entered when testing a transaction is 50.

XPD1015 INVALID MODULE NAME


Explanation: The module name specified on the command that caused this message is not a valid name under MVS naming rules. The module name is probably misspelled.

XPD1019 INVALID COMMAND ENTERED

Module: ADSRA412, ADSRA507, XPTSO, and XPDRP

Explanation: The command entered is not a valid XPEDITER command.

User Response: Check your spelling on the command.

XPD1021 TEST COMMAND ENTERED IN BTS/DLG ENVIRONMENT

Module: XPTSO

Explanation: The TEST command is not valid in the BTS or DLG environments.

User Response: Use the INTERCEPT command instead.

XPD1022 TEST MODULE C(20) NOT IN USER LIBRARY


Explanation: The module to be tested could not be found in the user library (STEPLIB DD in batch; XTASKLIB under TSO).

User Response: If the module is in this library, contact your internal technical support.

XPD1023 INTERCEPT MODULE C(20) NOT IN USER LIBRARY

Module: XPTSO

Explanation: The module to be intercepted could not be found in the user library (STEPLIB DD on the TEST STEP).

User Response: If the module is in this library, contact your internal technical support.

XPD1024 NO XTASKLIB ALLOCATED

Module: XPTSO

Explanation: The XTASKLIB DD must be allocated for an interactive test.


XPD1026 ENVIRONMENT CAN ONLY BE TSO OR SPF


Explanation: There is a severe processing error in XPEDITER/TSO.



XPD1028 PARM STRING FROM JCL USED FOR IMS

Module: ADSRA516

Explanation: This is a warning message. Because no IMS PARM string was specified on the TEST or INTERCEPT command, the PARM was taken from the JCL.

XPD1029 TRANCODE INVALID ON THE TEST COMMAND

Module: ADSRA516

Explanation: The TRANCODE keyword is not valid on the TEST command.

User Response: Use the INTERCEPT command or the LOADM keyword on the TEST command.

XPD1030 MISSING TRANCODE NAME - INTERCEPT COMMAND


Explanation: The TRANCODE name is required on the INTERCEPT command.

User Response: See the XPEDITER/TSO and XPEDITER/IMS Quick ReferenceXPEDITER/TSO or Reference Manual for more information on this command.

XPD1031 BAD TRANCODE NAME ON INTERCEPT COMMAND


Explanation: The syntax for a valid TRANCODE name (according to IMS and BTS rules) was violated by the TRANCODE keyword entry on the INTERCEPT command.

XPD1032 BAD PARMS ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The PARM string on the TEST command contained an invalid character length (not between 1 and 100).

XPD1034 NO PARMS ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The TEST command requires certain parameters to set up the test correctly.

User Response: See the XPEDITER/TSO and XPEDITER/IMS Quick ReferenceXPEDITER/TSO or Reference Manual for more information on this command.

XPD1035 NO PARMS SHOULD BE ENTERED ON THE INTERCEPT COMMAND

Module: ADSRA516

Explanation: The INTERCEPT command should not contain the PARM keyword.

XPD1036 NO ENTRY NAME ON TEST COMMAND

Module: ADSRA516

Explanation: If no entry point is specified, then XPEDITER/TSO uses the link-edited entry point to begin program execution. XPEDITER/TSO could not determine the entry point, and it was not specified.

XPD1037 BAD ENTRY NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The value used for entry point on the TEST command does not follow the naming conventions for a valid entry point or module name.

XPD1038 NO LOAD MODULE NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The TEST command requires that a program name be one of the parameters entered.


XPD1039 NO INITIAL SCRIPT NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The INITSCR keyword was specified on the TEST command, but no value (actual test script) was specified for it.

XPD1040 NO INITIAL SCRIPT NAME ON INTERCEPT COMMAND


Explanation: The INITSCR keyword was specified on the INTERCEPT command, but no value (actual test script) was specified for it.

XPD1041 NO POST SCRIPT NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The POSTSCR keyword was specified on the TEST command, but no value (actual test script) was specified for it.

XPD1042 ADSRA093 BECOMES INVALID

Module: XPINIT and CSSMVS

Explanation: ADSRA093 was reassembled incorrectly. Reassembly usually occurs because of changes to ADSCPDEF (installation defaults).

XPD1044 NO POST SCRIPT NAME ON INTERCEPT COMMAND


Explanation: The POSTSCR keyword was specified on the INTERCEPT command, but no value (actual test script) was specified for it.

XPD1047 BAD LOAD MODULE NAME ON INTERCEPT COMMAND

Module: ADSRA516

Explanation: The load module name entered for the TEST command is invalid under MVS naming conventions.

XPD1048 BAD INITIAL SCRIPT NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The initial test script name entered as a value on the TEST command does not conform to the naming conventions for a member of a PDS.

XPD1049 BAD POST SCRIPT NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The post test script name entered as a value on the TEST command does not conform to the naming conventions for a member of a PDS.

XPD1052 BAD INITIAL SCRIPT NAME ON INTERCEPT COMMAND


Explanation: The initial test script name entered as a value on the INTERCEPT command does not conform to the naming conventions for a member of a PDS.

XPD1053 BAD POST SCRIPT NAME ON INTERCEPT COMMAND


Explanation: The post test script name entered as a value on the INTERCEPT command does not conform to the naming conventions for a member of a PDS.

XPD1056 NO MODULE NAME ON INTERCEPT COMMAND

Module: ADSRA516

Explanation: The syntax for the INTERCEPT command demands that a program name be entered for it. The INTERCEPT command has no meaning without this keyword.


XPD1057 BAD ENTRY NAME ON INTERCEPT COMMAND


Explanation: The ENTRY keyword on the INTERCEPT command specifies an entry point that does not fit the naming requirements for the entry point within a module.

XPD1058 NO ENTRY NAME ON INTERCEPT COMMAND


Explanation: If no entry point is specified, XPEDITER/TSO uses the link-edited entry point to begin program execution. XPEDITER/TSO could not determine the entry point since it was not specified.

XPD1059 NO LOAD MODULE NAME ON INTERCEPT COMMAND


Explanation: The syntax for the INTERCEPT command demands that a program name be entered for it. The INTERCEPT command has no meaning without this keyword.

XPD1060 BAD LOAD MODULE NAME ON INTERCEPT COMMAND


Explanation: The load module name specified on the INTERCEPT command does not conform to the naming conventions for an MVS load module name.

XPD1061 EXTRANEOUS KEYWORD

Module: ADSRA516

Explanation: A keyword parameter specified on either the TEST or the INTERCEPT command was not valid.

User Response: Check to see if this is a spelling error.

XPD1063 NO COMMAND ENTERED TO DELETE

Module: ADSRA516

Explanation: A DELETE has been entered on the INTERCEPT command, but there was no previous INTERCEPT command entered.

XPD1064 CANNOT USE DELETE ON THE TEST COMMAND

Module: ADSRA516

Explanation: A DELETE is not valid on the TEST command.

User Response: If you are trying to do another test, simply enter another TEST command.

XPD1065 NO DB2 PLAN-NAME ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The internal DB2PLAN keyword requires the value of a valid DB2 plan name.

User Response: If you are not running with the DB2 DSN run support, leave this keyword off; otherwise, specify a valid DB2 plan name.

XPD1066 BAD PLAN-NAME ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The plan name specified for the internal DB2PLAN keyword is an invalid plan name, according to the naming rules for a DB2 plan name.

XPD1067 NO PLAN-NAME ENTERED ON THE INTERCEPT COMMAND


Explanation: The internal DB2PLAN keyword requires a value of a valid DB2 plan name.

User Response: If you are not running with the DB2 DSN run support, leave this keyword off; otherwise, specify a valid DB2 plan name.


XPD1068 BAD PLAN-NAME ENTERED ON THE INTERCEPT COMMAND


Explanation: The plan name specified for the internal DB2PLAN keyword is an invalid plan name, according to the naming rules for a DB2 plan name.

XPD1069 NO DB2 SYS-NAME ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The internal DB2SYS keyword requires a value of a valid DB2 system name.

User Response: If you are not running with the DB2 DSN run support, leave this keyword off; otherwise, specify a valid DB2 system name.

XPD1070 BAD DB2 SYS-NAME ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The system name specified for the internal DB2SYS keyword is an invalid system name, according to the naming rules for a DB2 system name.

XPD1071 NO DB2 SYS-NAME ENTERED ON THE INTERCEPT COMMAND


Explanation: The internal DB2SYS keyword requires a value of a valid DB2 system name.

User Response: If you are not running with the DB2 DSN run support, leave this keyword off; otherwise, specify a valid DB2 system name.

XPD1072 BAD DB2 SYS-NAME ENTERED ON THE INTERCEPT COMMAND


Explanation: The system name specified for the internal DB2SYS keyword is an invalid system name, according to the naming rules for a DB2 system name.

XPD1073 DB2 PARMS USED FROM FIRST INTERCEPT COMMAND


Explanation: This is an informational message only. The DB2 PARMS for the current INTERCEPT command will be taken from those established for the first INTERCEPT command.

XPD1074 BAD DB2 PARM ON COMMAND

Module: ADSRA516

Explanation: The DB2 keyword on the INTERCEPT command requires a value of either YES or NO. Something other than one of these two choices was entered for the value.

XPD1075 ERROR IN KEYWORD

Module: ADSRA516

Explanation: An invalid keyword was entered for either the TEST or INTERCEPT command.

User Response: Check the spelling on the keyword. If this is an interactive test, ensure any parameter strings containing spaces or commas are enclosed in apostrophes.

XPD1080 NO START PARAMETER ENTERED - INTERCEPT COMMAND


Explanation: The START keyword was used on the INTERCEPT command but no value was entered along with it. This shuts down the test. If START is not entered, it defaults to 1.

XPD1081 TOO MANY DIGITS ON START PARM - INTERCEPT


Explanation: A maximum of four digits is allowed for the START keyword on the INTERCEPT command.


XPD1082 TOO MANY DIGITS ON MAX PARM - INTERCEPT


Explanation: A maximum of four digits is allowed for the MAX keyword on the INTERCEPT command.

XPD1083 INVALID DIGITS ON START PARM - INTERCEPT


Explanation: A nonnumeric character was detected in the value for the START keyword. The value must be a 1-4 digit number.

XPD1084 INVALID DIGITS ON MAX PARM - INTERCEPT


Explanation: A nonnumeric character was detected in the value for the MAX keyword. The value must be a 1-4 digit number.

XPD1085 NO MAX PARAMETER ENTERED - INTERCEPT COMMAND


Explanation: A MAX keyword was entered on the INTERCEPT command, but no value was assigned to it. This shuts down the test; if the MAX keyword is not entered, it defaults to UNLIMITED.

XPD1091 DEFINE LENGTH OF N(4) IS GREATER THAN DATA GROUP N(4) SIZE OF N(4)

Module: ADSRA286

Explanation: An attempt was made to define an item to a length greater than that available to the data group.

User Response: If it is necessary to define such a large field, contact your internal technical support.

XPD1092 INSUFFICIENT MEMORY FOR X(21)

Module: ADSRA436

Explanation: You must increase the TSO logon size or the REGION permitted on the batch JOB in order to run this test.

User Response: If this is a problem, contact your internal technical support.

XPD1093 INSUFFICIENT MEMORY FOR ALLOCATION OF X(21) FOR X(8)

Module: ADSRA389, ADSRA423, ADSRA608, ADSRA623, and ADSRA695

Explanation: You must increase the TSO logon size or the REGION permitted on the batch JOB in order to run this test.

User Response: If this is a problem, contact your internal technical support.

XPD1095 NO BREAKPOINT TABLE FOR MODULE X(8)


Explanation: In order to set a breakpoint in the specified module, you must compile it under XPEDITER control.

User Response: If the module is compiled with XPEDITER and you still can’t set breakpoints, contact your internal technical support.

XPD1096 NUMBER IN INSERT TOO LARGE (C,8)

Module: ADSRA370

Explanation: You attempted to insert a line on a line number that is greater than the total number of lines in the program.

User Response: Check the listing for a valid line number.


XPD1097 NUMBER IN INSERT NOT NUMERIC

Module: ADSRA370

Explanation: You attempted to insert a line using a line number that is not numeric.

User Response: Check the listing for a valid line number. This is probably a typographical error.

XPD1098 MISSED NUMBER IN INSERT COMMAND

Module: ADSRA370

Explanation: An attempt was made to insert a line of code from a user test script. However, there was no line number specified on the INSERT command.

User Response: Add the line number and resubmit.

XPD1099 MISSED INSERT COMMAND

Module: ADSRA370

Explanation: You attempted to insert lines of code, but no INSERT command was found in the command stream.

User Response: Add the INSERT command if it is not present. If it is already present, contact your internal technical support.

XPD1100 NUMBER IN INSERT LESS PROC. DIV.

Module: ADSRA370

Explanation: An attempt was made to insert a line of code on a statement number that is not a Procedure Division statement number. This is illegal.

User Response: Check the statement numbers in the program: if a discrepancy exists, contact your internal technical support.

XPD1102 NO DEFINITION RECORD FOUND FOR DATA ITEM X(30) IN MODULE X(8)

Module: ADSRA436

Explanation: In trying to supply the linkage section for a COBOL subprogram being unit tested, XPEDITER discovered a problem with the DDIO dataset.

User Response: Recompile the program and test again. If that doesn’t work, contact your internal technical support.

XPD1103 NO ELEMENT DISPLAY BLOCK FOUND FOR DATA ITEM X(30) IN MODULE X(8)

Module: ADSRA436

Explanation: An attempt was made to reference the specified data item, but the necessary element display block (an XPEDITER internal control block) was not available.

User Response: Recompile the program and test again. If that doesn’t work, contact your internal technical support.

XPD1104 NO INTERFACE ITEMS FOUND FOR ENTRY (C,8)

Module: ADSRA436

Explanation: In trying to supply the linkage section for a COBOL subprogram being unit tested, XPEDITER discovered a problem with the DDIO dataset.

User Response: Try recompiling the program and testing again. If that doesn’t work, contact your internal technical support.

XPD1105 NO SNT ENTRY FOUND FOR STATEMENT N(3) IN MODULE X(8)

Module: ADSRA469

Explanation: An attempt was made to reference a statement for which there was no entry in the statement number table (SNT).



XPD1107 NO STATEMENT NUMBER TABLE ENTRY FOUND FOR X(30) IN MODULE X(8)

Module: ADSRA436

Explanation: An attempt was made to reference a statement for which there was no entry in the statement number table (SNT).


XPD1108 PCB COUNT EQUALS MODULE INTERFACE COUNT FOR X(30) IN MODULE X(8) PSB PASSED TO MODULE X(8)

Module: ADSRA436

Explanation: This is an informational message indicating that the PSB appears to contain the proper PCBs for the program.

XPD1109 PCB COUNT FOR X(8) EXCEEDS ITEM INTERFACE COUNT - PCB PASSED TO MODULE X(8)

Module: ADSRA436

Explanation: This is an informational message. There were more PCBs than receiving fields. They will be moved into the receiving fields from the first one, ignoring the extra ones.

XPD1110 INVALID XPEDITER SVC NUMBER (nnn).

Module: ADSRA111

Explanation: The SVC necessary to perform breakpoint processing could not be found.

User Response: Run the job ‘XTSVCINS’, which may be found in your installation libraries, to install the necessary SVC. This job may be included in your IPL procedures. If not included in your IPL procedures, it must be run after each IPL to avoid this error..

XPD1111 UNABLE TO LOCATE MODULE = X(8), ENTRY = X(8), MEMBER = X(8)

Module: ADSRA417

Explanation: The specified module could not be found in the XTASKLIB or STEPLIB.

User Response: Check the spelling on the module and verify that the module you are seeking is in your test load library. If the discrepancy remains, contact your internal technical support.

XPD1113 SVC BREAKPOINTING IS ACTIVE

Module: ADSRA111

Explanation: The optional breakpointing SVC has been installed and is active.


XPD1114 CONTROL BLOCK ERROR N(2)


Explanation: An XPEDITER internal control block was overlayed.


XPD1120 INSUFFICIENT STORAGE TO BUILD CONTROL BLOCK

Module: ADSRA171, ADSRA223, ADSRA380, ADSRA394, ADSRA409, ADSRA593, ADSRA609, ADSRA616, and ADSRA617

User Response: You must increase either the TSO logon size or the REGION parameter on the JCL to run the batch test.

XPD1121 INSUFFICIENT STORAGE TO BUILD LRP BLOCK

Module: ADSRA407


XPD1125 INVALID XPEDITER CONTROL BLOCK - B(2)

Module: ADSRA172, ADSRA173, ADSRA380, ADSRA394, AND ADSRA680


Explanation: An invalid condition was detected when building an XPEDITER control block.


XPD1127 NO CA-OPTIMIZER BASE LOCATORS FOR X(8)

Module: ADSRA217

Explanation: The module was compiled using the CA-OPTIMIZER, but no CA-OPTIMIZER base locators were found.


XPD1129 NO SLS MEMBER FOR X(8)

Module: ADSRA217

Explanation: This is an informational message reminding you that there is no DDIO dataset for the specified module.

User Response: If you wish to use XPEDITER DDIO debugging facilities, you must compile under XPEDITER control.

XPD1130 OUT OF MEMORY

Module: ADSRA418, ADSRA440, ADSRA459, ADSRA670, ADSRA676, ADSRA679, ADSRA689, and ADSRA690

User Response: Increase either the TSO logon size or the REGION parameter on the JCL to run the batch test, and begin the test again.

XPD1133 XPEDITER CONTROL BLOCK STRUCTURE ERROR - N(2)

Module: ADSRA208

Explanation: An XPEDITER internal control block was either overlayed or built incorrectly.


XPD1135 ERROR ON COPY FOR MEMBER X(8)

Module: ADSRA051

Explanation: An attempt to perform a dynamic call intercept on a module failed.


XPD1137 NO BREAKPOINT TABLE ENTRY FOR STATE (B,3) IN MODULE X(8)

Module: ADSRA402

Explanation: During the processing of a primary breakpoint command (such as BEFORE, COUNT, or TRACE), XPEDITER was unable to locate the specified statement.

User Response: If the statement is clearly a valid one, contact your internal technical support.

XPD1139 INSUFFICIENT STORAGE FOR SHOW PREV BUFFER

Module: ADSRA403

Explanation: XPEDITER ran out of memory.

User Response: Increase either the TSO logon size or the REGION parameter on the JCL for the batch test, and begin the test again.

XPD1142 GO TO NOT PERMITTED WHERE TARGET IS WITHIN PERFORMED OUT-OF-LINE PROCEDURE

Module: ADSRA426

Explanation: This is a restriction on the use of the OPTIMIZE option with VS COBOL II. When a paragraph was optimized into a series of multiple performs, you cannot branch to it through the use of the XPEDITER GO TO construct.

User Response: Check the I-level (informational) messages from VS COBOL II in your compilation listing. These will flag the paragraphs that fall into this category.


XPD1144 MODULE X(8) IS COMPILED WITH THE COBOL OPTIMIZE COMPILER OPTION. REFER TO XPEDITER/TSO USER GUIDE FOR LIMITATIONS AND TESTING CONSIDERATIONS.

Module: ADSRA193

Explanation: There are certain limitations on testing programs compiled with the COBOL OPTIMIZE compiler option.

User Response: Refer to the XPEDITER/TSO and XPEDITER/IMS COBOL User’s Guide for more information on these restrictions.

XPD1145 MODULE X(8) HAS BEEN COMPILED WITH THE TEST COMPILER OPTION. THIS OPTION SHOULD BE REMOVED OR UNPREDICTABLE RESULTS MAY OCCUR.

Module: ADSRA193

Explanation: Testing programs compiled with the TEST option can give unpredictable results.

User Response: Refer to the XPEDITER/TSO and XPEDITER/IMS COBOL User’s Guide for more information on these restrictions.

XPD1146 NO PREVIOUS BREAKPOINTS TO SHOW

Module: ADSRA463

Explanation: An attempt to show all the WHEN breakpoints has been made, but no WHEN breakpoints were in effect.

XPD1147 WARNING, COBOL PROGRAM LANGUAGE LEVEL IS NOT IDENTIFIABLE

Module: ADSRA193

Explanation: The COBOL language level could not be determined.

User Response: Make sure the level of the COBOL compiler is supported. Refer to the XPEDITER/TSO and XPEDITER/IMS Installation Guide section entitled “Operating Environment Support” for a list of supported COBOL releases.

XPD1149 XPTSO IMS INTERCEPTION BYPASSED BY XPEDITER

Module: XPTSO

Explanation: This is an informational message telling you that an IMS test is being invoked with XPEDITER/TSO allocations, but XPEDITER will not intercept any modules.

User Response: If this is not your intention, contact your internal technical support.

XPD1153 NOTE: THE AUTOCAN FEATURE DOES NOT AUTOMATICALLY DELETE VS COBOL II MODULES

Module: ADSRA274

Explanation: The SET AUTOCAN feature does not delete modules compiled with VS COBOL II. The automatic cancel will only take effect on modules compiled with OS/VS COBOL or ANS COBOL.

XPD1155 INSERTED LINE MORE THAN 61 BYTES

Module: ADSRA370

Explanation: An inserted line cannot exceed 61 bytes.

XPD1156 COMMAND NOT PERMITTED FOR DISPLAY ONLY LINES

Module: ADSRA370

Explanation: The INSERT command is not permitted on a line that is only for display.

XPD1157 INSERTED LINE NUMBER NOT FOUND IN X(8)

Module: ADSRA370

Explanation: The line number specified does not exist or is a display-only line. INSERT cannot be performed at the indicated line number.


XPD1158 COMMAND NOT PERMITTED FOR THIS COBOL VERB

Module: ADSRA370

Explanation: The INSERT command is not permitted on COBOL verbs such as PERFORM, GOBACK, RUN STOP, and EXIT.

XPD1163 FAILURE TO FIND DSN BY ADSRA558. DDNAME IS X(8)

Module: ADSRA223

Explanation: The call to ADSRA558 to find a DSN and build a pseudo JFCB block failed. The LMB and DCB does not have a pointer to the JFCB to get a DSN for load messages. This condition should not occur.

User Response: Contact your internal technical support. Also check for previous messages in the log.

XPD1164 ANOTHER USER IS CURRENTLY TESTING THE SAME PROGRAM AS YOU ARE ATTEMPTING TO TEST. COMPILE YOUR PROGRAMS WITH NORES TO AVOID THIS CONFLICT.

Module: ADSRA107

Explanation: If the program is compiled with RES, only one user at a time can execute that program.

User Response: Recompiling programs with NORES can resolve the problem.

XPD1165 ATTACH OF THE IMS REGION FAILED. RETURN CODE = N(4)

Module: ADSIM003

Explanation: During the attach of the XPEDITER/IMS BMP to setup, the test failed. The IBM return code is given.


XPD1166 THE NUMBER OF TRANSACTIONS EXCEEDS THE MAXIMUM OF 45.

Module: ADSIM003

Explanation: Only 45 transactions can be selected for an XPEDITER/IMS test.

User Response: Drop some of the transactions on the Setup panel.

XPD1167 GETMAIN FAILED FOR USER SEGMENT WORK AREA.

Module: ADSIM003

Explanation: An attempt to get storage for work areas failed.

User Response: Try increasing the TSO logon size.

XPD1168 GETMAIN FAILED FOR CLASS WORK AREA.

Module: ADSIM003


User Response: Try increasing the TSO logon size.

XPD1169 X(5) ABEND IN PROCESSING THE IMS REGION. THE INTERNAL XPEDITER IMS PROGRAM HAS ABENDED. PLEASE CHECK THE STATUS OF XPEDITER/IMS ENTITIES. DATABASE = X(8), TRAN = X(8), PSB = X(8)

Module: ADSIM003

Explanation: A system or user ABEND occurred while the XPEDITER/IMS validation BMP was active. User ABEND codes are in decimal format.

User Response: If the reason for the ABEND is not apparent from the code, contact Compuware Technical Support.

XPD1170 THE PSB IS LOCKED OR MARKED NON-SCHEDULABLE.

Module: ADSIM003

Explanation: The PSB associated with the transaction code to be tested is stopped or locked.


User Response: Restart the PSB and retry the test.

XPD1171 A DATABASE USED BY THIS PSB IS STOPPED.

Module: ADSIM003

Explanation: One of the databases used by this PSB is stopped.

User Response: Restart the database and retry the test.

XPD1172 THE TRANCODE IS MARKED AS STOPPED, LOCKED, OR NON-SCHEDULABLE.

Module: ADSIM003

Explanation: The transaction code to be tested is stopped, locked, or cannot be scheduled.

User Response: Restart the transaction code and retry the test.

XPD1173 THE TRANSACTION NAME ENTERED IS NOT DEFINED TO IMS.

Module: ADSIM003

Explanation: The transaction specified on the test panel is not defined to this control region.

User Response: Verify that the transaction code is spelled correctly and the IMS region ID is correct.

XPD1174 THE PSB NAME ENTERED IS NOT DEFINED TO IMS.

Module: ADSIM003

Explanation: The PSB associated with this test is not defined in this control region.

User Response: Verify that the PSB libraries are correct and the PSB GEN has been done.

XPD1175 NEITHER A TRANSACTION OR PSB NAME WAS ENTERED.

Module: ADSIM003

Explanation: The XPEDITER test could not find a valid PSB or transaction to test.

User Response: If a valid PSB or transaction code was entered on the Setup panel, contact Compuware Technical Support.

XPD1176 IN AN MPP TEST THE PSB HAS NO TRANSACTIONS.

Module: ADSIM003

Explanation: The XPEDITER test could not find a valid PSB or transaction to test.

User Response: If a valid PSB or trancode was entered on the Setup panel, contact Compuware Technical Support.

XPD1177 IN AN IFP TEST THE PSB HAS NO TRANSACTION DEFINED.

Module: ADSIM003

User Response: Make sure the IMS GEN was done and the correct program was specified on the panel.

XPD1178 AN XPEDITER INTERNAL ERROR HAS OCCURRED.

Module: ADSIM003


XPD1179 IN AN MPP OR IFP TEST, THIS PSB REQUIRES A TRANCODE.

Module: ADSIM003

User Response: Make sure the correct program was specified on the Setup panel and the library allocations specified during setup are correct.

XPD1180 THE PSB NAME ENTERED IS NOT GENED FOR THIS TRANSACTION.

Module: ADSIM003

Explanation: The trancode and module entered on the Setup panel do not agree.


User Response: If the trancode/module pair is unique, only one of them has to be entered on the Setup panel. Also, check if the IMS APPLCTN and TRANSACT macros are correct.

XPD1181 THIS PARALLEL SCHEDULABLE PSB CANNOT BE RUN AS A BMP.

Module: ADSIM003

Explanation: As generated, this PSB cannot be run as a BMP.

User Response: Use either IFP or MPP to test.

XPD1182 THIS BMP OR IFP PSB CANNOT BE RUN AS AN MPP.

Module: ADSIM003

Explanation: As generated, this PSB cannot be run as an MPP.

User Response: Try using the BMP or IFP option.

XPD1183 NO CLASS AVAILABLE FOR THIS MPP TEST.

Module: ADSIM003

Explanation: All available classes used for testing an MPP program are in use.

User Response: Try later or have the XPEDITER installer increase the number of classes.

XPD1184 TRANSACTION X(43) IS CURRENTLY IN USE.

Module: ADSIM003

Explanation: The named transaction is currently in use by another XPEDITER/IMS test session.

User Response: Try later. The INTER command on the Setup panel will show the current XPEDITER/IMS test sessions.

XPD1185 THE INFORMATIONAL ENQUE FAILED. CONTACT TECHNICAL SUPPORT.

Module: ADSIM003

Explanation: There is an internal problem in XPEDITER/IMS.


XPD1186 ERROR IN ASSIGNING AN XPEDITER TEST CLASS. SOME TEST TRANSACTIONS MAY NOT HAVE BEEN REASSIGNED TO THEIR ORIGINAL CLASS.

Module: ADSIM003

Explanation: The assign/reassign of the user’s trancode class failed on the setup or at the end of the test.

User Response: If the failure is at the end of the test, the trancode can be reassigned by the IMS operator or anyone else with the proper authority. Verify that the IMS security GEN was done and is active before contacting Compuware Technical Support.

XPD1187 XPEDITER INTERNAL ERROR - INVALID RETURN CODE FROM IMS EXIT.

Module: ADSIM003


XPD1188 ERROR IN REASSIGNING THE TEST TRANSACTION/S. SOME TEST TRANSACTIONS MAY NOT HAVE BEEN REASSIGNED TO THEIR ORIGINAL CLASS.

Module: ADSIM003

Explanation: The reassign of the user’s trancode class failed at the end of the test.

User Response: The trancode can be reassigned by the IMS operator or anyone else with proper authority. Verify that the IMS security GEN was done before contacting Compuware Technical Support.

XPD1189 THE ENQ TO SERIALIZE THE XPEDITER BMP FAILED. PLEASE TRY AGAIN.

Module: ADSIM003


Explanation: Another user can be starting an XPEDITER/IMS test and the setup BMP is in use.

User Response: Try starting the test again. If the error persists, contact Compuware Technical Support.

XPD1190 THE REASSIGN OF USER TRANSACTIONS WAS NOT DONE.

Module: ADSIM003

Explanation: The internal BMP used at test-end could not be run. The test transactions remain assigned to the XPEDITER classes.

User Response: Have the IMS operator reassign them to their original class. If the problem persists, contact your internal technical support.

XPD1198 BTSCOM00 NOT FOUND IN MODULE BTSRC000. TEST TERMINATED.

Module: XPBTBTSF

Explanation: XPEDITER received an incorrect address of CSECT BTSCOM00 within BTSRC000. The problem occurs because BTSCOM00 is not the first CSECT in BTSRC000 at the user site.

User Response: Contact your internal technical support if the problem cannot be corrected at the user site.

XPD1199 THERE HAS BEEN A PARSING ERROR - CONTACT TECHNICAL SUPPORT.

Module: ADSIM003

Explanation: The PARM string passed to XPEDITER/IMS is not in the correct format.

User Response: Check the PARM strings as installed before contacting Compuware Technical Support.

XPD1200 THE RESTART OF X(5) X(8) FAILED. STATUS = X(2)

Module: ADSIM003

Explanation: A restart of the named IMS entity (i.e., TRAN...) failed. The IMS status code is given.


XPD1201 A CONVERSATIONAL TRANSACTION IS NOT ALLOWED IN A BMP TEST.

Module: ADSIM003

Explanation: This transaction is generated as Conversational (SPA was specified on the TRANSACT macro).

User Response: Try testing with MPP or IFP.

XPD1202 X(5) ABEND IN PROCESSING THE X(3) REGION. XPEDITER WILL ATTEMPT TO RESTART THE USER PGM AND/OR TRAN. IF THE IMS TERMINAL IS LOCKED, IT WILL HAVE TO BE STARTED MANUALLY.

Module: ADSIM003

Explanation: There was an ABEND during a user test in an MPP, BMP, or IFP message region. User ABEND codes are in decimal format.

User Response: Check the status of the test tran and program. XPEDITER/IMS may not have been able to restart them. If your IMS terminal is locked, it will have to be restarted by someone with authorization. If the reason for the ABEND is not apparent from the code, contact Compuware Technical Support.

XPD1203 PROCESSING ENDED DUE TO ATTENTION INTERRUPT.

Module: ADSIM002

Explanation: The XPEDITER/IMS test was ended when the attention key was hit. This is an informational message.


XPD1204 A NON-BLANK STATUS CODE OF X(2) WAS RETURNED AFTER A DLI CALL.

Module: ADSIM003

Explanation: While running the XPEDITER BMP to set up an IMS test, one of the calls to the database returned a bad status code. The code is given.

User Response: Check the IMS system log for additional error messages. If the error is not apparent, contact your internal technical support.

XPD1205 ABEND OCCURRED DURING PROCESSING

Module: ADSIM002

Explanation: The IMS region ended with a system or user ABEND. User ABEND codes are in decimal format.

User Response: If the reason for the ABEND is not apparent from the code, contact Compuware Technical Support.

XPD1206 A NON-BLANK STATUS CODE OF X(2) OCCURRED DURING /RSTART PROCESSING. THE INTERNAL CODE WAS N(3).

Module: ADSIM003

Explanation: XPEDITER is unable to RSTART the terminal associated with the IMS transaction.

User Response: If your terminal is hung in response mode, try to free it by entering the IMS /RSTART command.

XPD1207 UNABLE TO OPEN DDNAME XXXXXXXX

Module: XPBTBTSE

Explanation: An OPEN failed for the ddname specified.

User Response: Make sure that the ddname specified is available.

XPD1208 LOAD MODULE XXXXXX NOT FOUND

Module: XPBTBTSE

Explanation: The load module specified was not found in the allocated library.


XPD1209 LOAD MODULE IN OVERLAY FORMAT - NOT SUPPORTED BY XPEDITER/TSO

Module: XPBTBTSE

Explanation: XPEDITER/TSO does not support overlay format.

User Response: The module should be recompiled without overlays for testing purposes.

XPD1210 UNABLE TO OPEN DDNAME XDYNAMIC

Module: XPBTBTSE

Explanation: An OPEN failed for the XDYNAMIC ddname.

User Response: Verify that the XDYNAMIC ddname is available.

XPD1212 READ FAILURE FOR DDNAME XXXXXXXX

Module: XPBTBTSE

Explanation: XPEDITER/TSO was unable to read the specified ddname.


XPD1213 WRITE FAILURE FOR DDNAME XDYNAMIC

Module: XPBTBTSE

Explanation: XPEDITER/TSO was unable to write to the XDYNAMIC ddname.



XPD1214 INSUFFICIENT DIRECTORY BLOCKS FOR XDYNAMIC

Module: XPBTBTSE

User Response: Reallocate XDYNAMIC with increased number of directory blocks.

XPD1215 INSUFFICIENT MEMORY FOR BUFFER

Module: XPBTBTSE


XPD1216 XXXXXXXX MUST BE ALLOCATED TO SUPPORT BLOCKSIZE XXXXX

Module: XPBTBTSE

Explanation: The ddname must have a blocksize greater than or equal to the blocksize specified.

User Response: Reallocate the ddname specified with an increased blocksize.

XPD1222 NO RESUME POINT IN X(8) AFTER SKIP ON STATEMENT N(3) - TEST TERMINATED

Module: ADSRA649

Explanation: After a SKIP statement was encountered, there was no instruction available to resume execution. The test was terminated when no return linkage was found.

XPD1223 THIS OFFSET LOWER THAN PREVIOUS ONE X(40)

Module: ADSRA608

Explanation: A possible error may have been detected. Even though statements are in sequential order, offsets may not be (i.e., multiple CSECT).


XPD1228 X(30) TRUNCATED TO 64 CHARACTERS

Module: ADSRA614

Explanation: Any name greater than 64 characters is truncated. This can create unintentional duplicate names.

User Response: One solution is to rename to retain uniqueness.

XPD1229 X(30) IN X(8) HAS INVALID ADDRESS OF N(4)

Module: ADSRA409

Explanation: The address of the designated data item is either invalid or fetch-protected. A value of zero is substituted for the address of the item.

User Response: This condition should not occur and should be reported to your internal technical support.

XPD1231 THE XPEDITER X(5) EXIT ROUTINE HAS BEEN ISSUED AGAIN AFTER BEING RESET

Module: ADSRA105

Explanation: A S0C1 program interrupt was intercepted by the ESTAE exit routine when the XPEDITER ESPIE/SPIE macro was issued. The appropriate exit is established again.

XPD1232 (4) BREAKPOINT(S) RESET IN MODULE X(8) AFTER MEMORY OVERLAY

Module: ADSRA602

Explanation: One or more breakpoints were reset as a consequence of the execution of an XPEDITER command that changed memory contents in a module being tested.

User Response: The breakpoints can be restored if valid OP codes are found at the original offsets.

XPD1233 NO DEFINITION FOR MACRO ON STATE N(3)

Module: ADSRA608


Explanation: Since the verb was not on the list of OP codes, a macro is assumed. But no OPSYN or definition for the macro was found on the indicated statement.

XPD1234 ATTEMPT TO LOAD X(8) FAILED - ABEND CODE = X(4) REASON CODE = N(1)

Module: ADSRA107

Explanation: The module specified with the USERABTX SET command for use as the batch abnormal termination exit routine could not be loaded. The ABEND and reason codes describing the problem are formatted in this message.

XPD1235 CANCEL REQUEST BY X(8) SATISFIED - X(8) HAS BEEN DELETED


Explanation: The cancel of the previously loaded dynamic module was performed as requested.

XPD1236 CANCEL REQUEST BY X(8) IGNORED - NO PRIOR DYNAMIC CALL OF X(8)


Explanation: A cancel was requested for a module which was either not called dynamically or was previously cancelled.

XPD1240 XPEDITER ESPIE RESET BY X(8) MASK BITS N(2) - XPEDITER ESPIE RESTORED

Module: ADSRA273

Explanation: The XPEDITER issued ESPIE was reset by the specified program. The XPEDITER issued ESPIE must be the active ESPIE, therefore, the XPEDITER issued ESPIE was restored.

XPD1243 INSUFFICIENT MEMORY INDICATED BY X(7) ABEND - LARGER REGION SIZE MAY BE REQUIRED

Module: ADSRA105

Explanation: A system ABEND was caused by insufficient memory.

User Response: The test should be reinitiated with a larger region or address space.

XPD1244 STATEMENT NUMBER N(3) SKIPPED AFTER NULL PERFORM IN MODULE X(8)

Module: ADSRA449

Explanation: A skip was processed for a PERFORM that did not have code associated with it. The next statement with one or more instructions was bypassed even though it was not designated for skip processing.

XPD1245 X(8) X(10) FROM LINKLIST

Module: ADSRA222

Explanation: The load module name was preloaded or loaded from LINKLIST. XPEDITER may not be able to access the module.


XPD1246 NO INCORE JFCB FOR X(8)

Module: ADSRA222

Explanation: There was an I/O operation error in the JOB file control block accessing the XTASKLIB or USERLIB.


XPD1247 RECURSIVE ABEND CONDITION ENCOUNTERED - NOTIFY TECHNICAL SUPPORT


Explanation: An ABEND occurred during the processing of a previous ABEND. The test is terminated with a user 3007 abend and a dump.

User Response: The information in the log should be given to the your internal technical support.


XPD1360 INVALID PARAMETER FOR REVIEW MODE

Module: ADSRA136

Explanation: The parameter is not valid for revision mode.

User Response: Check the command syntax.

XPD1362 COMMAND REJECTED - REVIEW MODE NOT IN EFFECT

Module: ADSRA136

Explanation: The command is valid only when review mode is in effect.

User Response: Check your reference manual.

XPD1365 REVIEW PROCESSING INTERRUPTED BY ATTENTION

Module: ADSRA136

Explanation: A review execution pause was requested with the attention key.


XPD1940 /TIME OPTION HAS BEEN DISABLED - BY DEFAULT

Module: ADSRA194

Explanation: Checking for a date/time mismatch has been disabled.


XPD1941 SECURITY CHECK FAILED FOR <language-type> LANGUAGE

Module: ADSRA194

Explanation: An attempt was made to access the DDIO file for a member of a language type for which you are not licensed.

User Response: Contact your internal technical support if you believe you are licensed for the specified language.

XPD1942 NO DATE/TIME PRESENT FOR MODULE <module-name>

Module: ADSRA194

Explanation: The specified load module does not contain a date/time stamp. Therefore, XPEDITER/TSO cannot guarantee an exact match between the load module and the DDIO file member.


XPD1943 PLEASE COMPILE WITH CURRENT CSS FOR FULL NESTED COBOL SUPPORT

Module: ADSRA194

Explanation: The nested COBOL program was processed with a back-level CSS. For full nested COBOL support, you must recompile your program with a currently supported level of LP.


XPD1944 A DSA FOR MODULE X(8) WAS NOT FOUND DURING TERMINATION

Module: ADSRA194

Explanation: During termination of a test that was initiated by the EXIT command, the named module had opened files, but did not close them. XPEDITER tried to determine the Dynamic Storage Area (DSA) for the module in order to close the files but was unsuccessful. The files will be closed by MVS.

User Response: None. This message is informational only.

XPD1945 ADSRA194 CSS SHARED DIRECTORY HAS ALLOCATED > 32767 DSNAMES

Explanation: There is a limitation of 32,767 dataset names for DDIO/source libraries.


User Response: Eliminate some DDIO/source dataset names via combination or by breaking the test case into smaller units.

XPD2210 PL/I OPT MODULE WAS PRELOADED OR IS IN PROTECTED STORAGE

Module: ADSRA221

Explanation: XPEDITER was unable to preset a desired number of options because they had already been implemented or the options module is in protected storage and cannot be modified.

User Response: Depending on the environment and the type of XPEDITER functions used, testing may function normally. If an ABEND occurs or breakpoints are not recognized, the user should place loadable modules into a non-authorized library as specified in SETUP and then rerun the test.

XPD2211 LE/370 LIBRARIES ARE PRELOADED OR IN PROTECTED STORAGE

Module: ADSRA221

Explanation: XPEDITER was unable to preset a desired number of options because they had already been implemented or the options module is in protected storage and cannot be modified.

User Response: Depending on the environment and the type of XPEDITER functions used, testing may function normally. If an ABEND occurs or breakpoints are not recognized, the user should place loadable modules into a non-authorized library as specified in SETUP and then rerun the test.

XPD2212 NO PL/I OPTIONS MODULE TO RESET

Module: ADSRA221

Explanation: XPEDITER was unable to preset desired options because it could not locate a PL/I options module.

User Response: Depending on the environment and the XPEDITER functions used, testing may or may not function normally. If an ABEND occurs or breakpoints are not recognized, the user should ensure that language options and modules are in a library specified in SETUP.

XPD2222 MODULE X(8) HAS LINKAGE SECTION WITHOUT USING

Module: ADSRA417

Explanation: Normally, when a linkage section is coded in a program, there is a USING clause in the Procedure Division or entry statement.

XPD3000 ABEND-AID DD HAS BEEN ALLOCATED TO A TEMPORARY DATASET

Module: ADSRA311

Explanation: If you don’t have an ABEND-AID DD card allocated to your test session, XPEDITER will dynamically allocate one for you (if you are using the AA SNAP command).


XPD3001 NO LEAID MODULE FOUND UNDER LE/370 ENVIRONMENT

Module: ADSRA311

Explanation: In order for the ‘AA SNAP’ command to function in an LE environment, Compuware’s ABEND-AID LEAID must be installed as an LE abnormal termination exit.

User Response: Refer to the Language Environment (LE) section of Compuware’s ABEND-AID Installation Guide.

XPD3002 THE AA SNAP FUNCTION REQUIRES A SUPPORTED RELEASE OF ABEND-AID/SNAPAID

Module: ADSRA311

Explanation: In order to use the AA SNAP command, you must have previously installed and activated Compuware’s ABEND-AID product.

User Response: If ABEND-AID is installed at your site, ensure that it has been activated.


XPD3030 CHANGED KEYWORD IGNORED WITH DEFINE

Module: ADSRA286

Explanation: The changed keyword and the defined keyword are mutually exclusive. If both are specified, the defined keyword takes precedence.

XPD3031 DEFINE LENGTH OF X(4) AND OFFSET OF X(4) EXCEEDS THE END OF DATA GROUP B(4) WHICH HAS A SIZE OF X(4)

Module: ADSRA286

Explanation: The field being defined must not overlap the data group boundary.


XPD3032 DEFINE LENGTH OF ’,(X,4),’ IS GREATER

Module: ADSRA286



XPD3035 INSUFFICIENT MEMORY FOR X(21)

Module: ADSRA436

Explanation: No storage can be allocated for the element display block.

User Response: Increase the REGION size for the TSO logon or batch JOB.

XPD3051 MAXIMUM OF 15 BASE REGISTERS EXCEEDED

Module: ADSRA217

Explanation: The maximum number of base locator cells that XPEDITER can maintain is 15. This maximum was exceeded.


XPD3052 ALLOCATION OF GPR BUFFER FAILED

Module: ADSRA217

Explanation: An attempt to allocate memory failed for the GPR buffer.


XPD3067 TO BROWSE PDS - ENTER LIB AND MEMBER

Module: ADSRA407

Explanation: To browse a dataset, you must enter the member name as well as the name of the dataset.


XPD3072 NO BLI FOR OFFSET ’(X,4)’ IN ’(C,8)’

Module: ADSRA217



XPD3073 NO CAPEX BASE LOCATORS FOR ’(C,8)’

Module: ADSRA217



XPD3081 ATTEMPT TO LOAD ’(C,8)’ FAILED -

Module: ADSRA308

Explanation: Because Test Case Facility is obsolete, this message is no longer valid.



XPD3082 TCF FUNCTION: ’(C,4)’ FAILED

Module: ADSRA308



XPD3083 LOOKUP FOR ’(C,44)’ FAILED

Module: ADSRA308



XPD3097 INSUFFICIENT STORAGE TO BUILD CONTROL BLOCK

Module: ADSRA307 if Testing PL/I, ADSRA309 if Testing C/370

Explanation: An Element Display Block for a data item could not be created.

User Response: Increase either the TSO logon size or the REGION parameter on the JCL in order to run the batch test and begin the test again.

XPD3333 CEE COBOL TRAP OPTION WAS FORCED TO OFF

Module: ADSRA417



XPD3650 STATEMENT IS NOT AN EXEC

Module: ADSRA365

Explanation: The GEN command is only allowed on EXEC statements.


XPD3651 GEN PREVIOUSLY PERFORMED FOR EXEC

Module: ADSRA365

Explanation: A GEN was previously performed on this statement.


XPD3652 DELETE PREVIOUSLY PERFORMED FOR EXEC

Module: ADSRA365

Explanation: A DELETE GEN was previously performed on this statement.


XPD3700 NUMBER IN INSERT NOT NUMERIC ,(C,8,1<MODULE>)

Module: ADSRA370

Explanation: The statement number in the INSERT command within the INCLUDE test script is not numeric.

User Response: Use the numeric value as a statement number in the INSERT command.

XPD3730 CONTROL BLOCKS DISAGREE ON COBOL TGT LENGTH

Module: ADSRA373

Explanation: The COBOL TGT length calculated by module ADSRA373 does not agree with the length contained in the XPEDITER COBOL extension block. This may be a result of incorrect Memory Map information that was supplied by CSS. If testing is continued, it is likely that data displayed by Peek and/or Keep will be incorrect or not addressable.



XPD3801 NO MATCH ON EXTERNAL NAME: ,(C,8)


XPD3860 ERROR RETRIEVING NPMAP RECORDS FROM CSS FOR <module>

Module: ADSRA386

Explanation: A CSS error has occurred while trying to retrieve NPMAP records for the specified module. This is probably caused by running XPEDITER with a back-level version of CSS.

User Response: Check to make sure you are using a currently support CSS release. If you have installed the correct release, contact your internal technical support.

XPD3870 GETMAIN FAILED IN MODULE X(8) FOR N(4) HEX BYTES

Module: ADSRA387

Explanation: An attempt to allocate memory for the XPEDITER breakpoint table failed.

User Response: Increase the REGION size and try again.

XPD3871 INVALID TOKEN IN CSS CLIST - N(4) - X(30)

Module: ADSRA387

Explanation: A valid verb matching the token cannot be found in the CSS CLIST.


XPD3872 NO BREAKPOINTS FOUND FOR NEXT COMMAND - MODULE X(8)

Module: ADSRA387

Explanation: An attempt to resolve breakpoints for the NEXT command failed.


XPD3873 SIZE ERROR - BREAKPOINT TABLE BUILD HALTED FOR MODULE <module-name>

Module: ADSRA387

Explanation: An internal error occurred in calculating the length of the breakpoint table. If allowed to continue, serious run-time errors would occur attempting to process breakpoint requests.


XPD3874 ERROR RETRIEVING EXTENDED CLIST FROM CSS FOR <module>

Module: ADSRA387

Explanation: A CSS error has occurred while retrieving an extended CLIST for the specified module. This is probably caused by running XPEDITER with a back-level version of CSS.

User Response: Check to make sure you are using a currently support CSS release. If you have installed the correct release, contact your internal technical support.

XPD3880 INSUFFICIENT STORAGE TO BUILD STATEMENT NUMBER TABLE FOR X(8)


Explanation: You must increase either the TSO logon size or the REGION parameter for the JCL used to run the batch test.

XPD3881 ERROR IN SOURCE LISTING - CANNOT BUILD STATEMENT NUMBER TABLE FOR X(8) - ERROR CODE X(4)

Module: ADSRA388

Explanation: An error was found building the SNT. XPEDITER encountered a problem with the source listing.


XPD3882 UNABLE TO RETRIEVE LAST SOURCE LINE. CSS RC=N(4)

Module: ADSRA388


Explanation: While constructing the statement number table (SNT), XPEDITER could not retrieve the last statement in the source.


XPD3883 UNABLE TO RETRIEVE FIRST SOURCE LINE. CSS RC=N(4)

Module: ADSRA388

Explanation: While constructing the statement number table (SNT), XPEDITER could not retrieve the first statement in the source.


XPD3884 INVALID STATEMENT NUMBER IN SOURCE. SLPDLLN# = N(4)

Module: ADSRA388

Explanation: The indicated source line has an invalid external number.


XPD3885 INVALID DATA IN DMAP RECORD. SLPDMDEF=N(4); TOKEN=N(4)

Module: ADSRA388

Explanation: XPEDITER found an invalid definition line in the DMAP.


XPD3886 UNABLE TO RETRIEVE THE CSS COLUMN TABLE. CSS RC=N(4)

Module: ADSRA388

Explanation: There was a failure in the CSS Column Table that was needed to create the statement number table (SNT).


XPD3887 PROGRAM X(8) DOES NOT HAVE A PROCEDURE DIVISION

Module: ADSRA388

Explanation: The named program does not have a Procedure Division statement. XPEDITER does not support testing of these types of programs.


XPD3920 INVALID TOKEN IN CSS CLIST - N(4) - X(30) - X(8)

Module: ADSRA392

Explanation: A valid verb matching the token cannot be found in the CSS CLIST.


XPD3930 INSUFFICIENT STORAGE TO BUILD PROCEDURE HIERARCHY TABLE FOR X(8)

Module: ADSRA393

Explanation: XPEDITER attempted to obtain memory for the Procedure Hierarchy Table, but there was not enough memory.

User Response: Increase the region size and try again.

XPD3931 SEVERE ERROR OCCURRED DURING LINE NUMBER CONVERSION:

Module: ADSRA393

Explanation: A severe error occurred in the conversion of internal statement numbers to external statement numbers.


XPD3932 SNT = N(4) EXTERNAL = N(4) INTERNAL = N(4)

Module: ADSRA393


Explanation: A severe error occurred in the conversion of statement numbers. This message tells you the name of the statement number table (SNT) that XPEDITER is trying to convert.


XPD3933 A ZERO SRBLSEXT VALUE HAS ENDED THE SRB BUILD PROCESS.

Module: ADSRA393

Explanation: During the SRB build process, a value of zero was found for the last external number in the range. A zero value is not valid.


XPD3934 ASSOCIATED VALUES: SRBFSEXT = N(4) SRBFSINT = N(4)

Module: ADSRA393

Explanation: This message gives associated values relating to the preceding message which should be of assistance in locating the failing source statement.


XPD3960 ERROR BUILDING VARIABLE REFERENCE TABLE - SEE LOG

Module: ADSRA396

Explanation: An error occurred when trying to retrieve the PL/I Variable Reference Table.

User Response: Recompile your program with the ’DDIO(OUTPUT(VARREF))’ parameter.

XPD3961 X(8) WAS COMPILED WITHOUT THE “DDIO(OUTPUT(VARREF))” PARM WHICH IS REQUIRED FOR PEEK/KEEP FUNCTIONALITY.

Module: ADSRA396

User Response: Recompile using the correct parameter.

XPD3962 X(8) WAS COMPILED WITHOUT THE “DDIO(OUTPUT(VARREF))” PARM WHICH IS REQUIRED FOR PEEK/KEEP FUNCTIONALITY.

Module: ADSRA396

User Response: Recompile using the correct parameter.

XPD3963 GETMAIN FAILED FOR THE VARIABLE REFERENCE TABLE

Module: ADSRA396

Explanation: XPEDITER attempted to obtain memory for the Variable Reference Table, but there is not enough memory.

User Response: Increase the region size and try again.

XPD3964 THE CSS LIBRARIES ALLOCATED TO THIS SESSION DO NOT SUPPORT THE REQUIREMENTS OF THIS RELEASE OF XPEDITER/TSO.

Module: ADSRA396

Explanation: The CSS libraries installed are not compatible with the current version of XPEDITER/TSO.

User Response: Make sure that the correct version of CSS is used.

XPD3965 THE CSS LIBRARIES ALLOCATED TO THIS SESSION DO NOT SUPPORT THE REQUIREMENTS OF THIS RELEASE OF XPEDITER/TSO.

Module: ADSRA396

Explanation: The CSS libraries installed are not compatible with the current version of XPEDITER/TSO.

User Response: Make sure that the correct version of CSS is used.

XPD3970 A GETMAIN FOR N(4) HEX BYTES FAILED. SEE LOG.


Explanation: An attempt to allocate memory for the XPEDITER breakpoint table failed.


User Response: Increase the REGION size and try again.

XPD3971 A WORKAREA GETMAIN FAILURE OCCURRED FOR N(4) HEX BYTES OF STORAGE.

Module: ADSRA397


User Response: Try logging on with a larger REGION size.

XPD3972 A WORKAREA GETMAIN FAILURE OCCURRED FOR N(4) HEX BYTES OF STORAGE.

Module: ADSRA397


User Response: Try logging on with a larger REGION size.

XPD4020 NO BREAKPOINT TABLE ENTRY FOR STATEMENT

Module: ADSRA402

Explanation: During the processing of a primary breakpoint command (such as BEFORE, COUNT, or TRACE), XPEDITER was unable to locate the specified statement.

User Response: If the statement is clearly a valid one, contact your internal technical support.

XPD4021 STATEMENT NUMBER NOT FOUND IN MODULE

Module: ADSRA402

Explanation: The requested statement number does not exist in this module.

XPD4022 BREAKPOINT NOT PERMITTED FOR DISPLAY ONLY LINE

Module: ADSRA402

Explanation: Breakpoints are not permitted on lines that are for display only.

XPD4029 SPECIFIED EXECUTION MAX HAS BEEN REACHED

Module: ADSRA403

Explanation: The maximum breakpoint execution count has been reached.

XPD4032 PAUSE REQUESTED WITH ATTENTION/PA1 KEY

Module: ADSRA403

Explanation: A pause of the execution was requested by pressing the attention key.

XPD4037 CANNOT EXCEED SPECIFIED EXECUTION MAX

Module: ADSRA403

Explanation: A maximum breakpoint execution count has been reached and cannot be exceeded.

User Response: Reset breakpoint execution count.

XPD4038 BREAKPOINT WITHOUT ACTION INDICATOR

Module: ADSRA403

Explanation: An ABEND or GOBACK processing is in progress.

XPD4039 WHEN PAUSE WITH NO SATISFIED CONDITION

Module: ADSRA403

Explanation: A WHEN “true” condition was not found in the WHEN chain.

XPD4040 CODE COVERAGE RESULTS FOR PROGRAM PGMNAME WITH SYSTEM NAME SYSNAME HAVE SUCCESSFULLY BEEN WRITTEN TO THE REPOSITORY REPOSITORY-NAME

Module: ADSRA432


Explanation: The program identified by pgmname has had it’s Code Coverage data written to the Repository specified by repository-name with the user identifier specified by sysname.

XPD4041 XVTTARIO - <MESSAGE> RPERRRET=<ERR1> RPERRCD=<ERR2>

Module: ADSRA432

Explanation: The repository I/O module has returned the error code specified by RPERRRET. RPERRCD will vary based on the message content. Currently, the values of RPERRRET and the message can be:

– 04 - MISSING DDNAME/DD CARD– 08 - RECORD NOT FOUND - UNABLE TO PROCESS– 12 - INVALID REPOSITORY DATASET– 16 - INVALID RPIO PARMLIST - NO VALID REQUEST SPECIFIED– 20 - I/O ERROR, RPERRCD CONTAINS THE RPL CONDITION CODE– 24 - OPEN ERROR, RPERRCD CONTAINS ACB ERROR FLAG– 28 - REPOSITORY ENQUEUE FAILED– 32 - LOGIC ERROR BUILDING MULTI-PART REC– 36 - LOGIC ERROR, UPDATE FOUND DUPLICATE TIMESTAMP– 40 - LOGIC ERROR, SEGMENT NOT FOUND WHILE UPDATING

User Response: For RPERRCD = 04 through 12, correct the error and retry. For codes 16 through 40, contact Compuware Technical Support.

XPD4042 ERROR CODE <ERRCODE> ACCESSING REPOSITORY FOR DEBUG=<TYPE>

Module: ADSRA433

Explanation: The CCHILITE command attempted to retrieve a repository record with the DEBUG type indicated. However, no record matched the specified retrieval criteria.

User Response: If RPERRCD is not = 8 (8 = Not found), contact Compuware Technical Support.

XPD4043 REPOSITORY REC FOR <CSECT> DEBUG=<OPTION> RETRIEVED FOR HIGHLIGHTING

Module: ADSRA433

Explanation: The CCHILITE command succeeded in retrieving a repository record with the DEBUG type indicated.

XPD4050 LOAD MODULE NOT FOUND FOR SOURCE NAME

Module: ADSRA405



XPD4120 INVALID COMMAND

Module: ADSRA412

Explanation: The command specified is not a valid XPEDITER command.

User Response: Check your spelling of the specified command. Refer to the XPEDITER/TSO and XPEDITER/IMS Reference Manual.

XPD4121 EXTRANEOUS KEYWORD

Module: ADSRA412

Explanation: When parsing the command issued, an extraneous keyword was found.

User Response: Check command syntax and try again.

XPD4122 RETEST INVALID IN THIS ENVIRONMENT

Module: ADSRA412

Explanation: The RETEST command is not valid in a Dialog, DB2, or IMS message region environment.


XPD4123 RETEST INVALID IN THIS ENVIRONMENT

Module: ADSRA412

Explanation: The RETEST command is not valid in an IMS message region or an IMS BMP or Fast Path environment.

XPD4140 IDENTIFIER NAME NOT FOUND IN MODULE

Module: ADSRA538

Explanation: The data name specified in the DISPLAY command cannot be found in the current module.

XPD4141 COMMAND NOT PERMITTED FOR DISPLAY ONLY LINE

Module: ADSRA414

Explanation: The specified command is not valid on null lines or display-only lines.

XPD4142 COMMAND NOT PERMITTED FOR MODULE WITHOUT SOURCE

Module: ADSRA414

Explanation: The specified command is valid only when there is available source for the module.


XPD4145 CTLDTOFF=N PREVENTS SET DATETIME OFF COMMAND DURING CODE COVERAGE (DEFAULT)

Module: ADSRA612

Explanation: The date/time off option (CTLDTOFF) as specified in the installation defaults is set to ’N’ (No). This means that the SET DATETIME OFF command cannot be used.

User Response: To allow the ’SET DATETIME OFF’ command, change CTLDTOFF=N to CTLDTOFF=Y in the ADSCPDEF macro and reassemble/recompile (refer to the XPEDITER/TSO and XPEDITER/IMS Installation Guide).

XPD4146 CTLDEBUG=N PREVENTS LOGIC ALTERING ACTIONS DURING CODE COVERAGE

Module: ADSRA353, ADSRA612, ADSRA688

Explanation: Certain XPEDITER commands and/or actions can alter the logic flow of a program. For Code Coverage, if CTLDEBUG=N in the ADSCPDEF macro (XPEDITER/TSO installation defaults - refer to the XPEDITER/TSO and XPEDITER/IMS Installation Guide), the following commands will be prevented:

– ACCEPT– DROP– DLI– FADB2– GOBACK (GO BACK)– GOTO (GO TO)– MOVE– RETURN– SKIP– USE– USING– Overtyping Storage

User Response: To allow logic altering commands, change CTLDEBUG=N to CTLDEBUG=Y in the ADSCPDEF macro and reassemble (refer to the XPEDITER/TSO and XPEDITER/IMS Installation Guide).

XPD4147 POTENTIAL LOGIC ALTERING ACTION, DEBUG BIT SET


Explanation: The natural logic flow of the program may have been altered by the use of an XPEDITER/TSO command or feature. The records that are written to the Code Coverage Repository for this test will reflect that.


XPD4148 ****** CODE COVERAGE ******


Explanation: This line of text is designed as an attention-getter to alert the user to other, more complex error messages.


XPD4149 ONE (OR MORE) OF THE GPREGS HAS BEEN ALTERED

Module: ADSRA353

Explanation: Since changes to the General Purpose Registers are not logged, this message informs the user when they have been changed during a Code Coverage test session.


XPD4150 BASE LOCATOR NOT INITIALIZED


Explanation: There was a failure in constructing the element display block (EDB) for the specified data. Base locator cells were not initialized.


XPD4151 NO IDENTIFIER NAME LOCATED

Module: ADSRA623

Explanation: No data information was found for the specified data name.

XPD4170 CEE COBOL TRAP OPTION WAS FORCED TO OFF


Explanation: This is an XPEDITER default.

XPD4171 NO SOURCE LISTING DATA SET MEMBER FOR X(8)

Module: ADSRA417

Explanation: The specified source listing cannot be found in the allocated DDIO dataset.

User Response: Check to make sure that the correct DDIO is allocated. Recompile the program and try again.

XPD4172 X(3) APPLICATION MODULE NOT FOUND IN USER LIBRARY

Module: ADSRA417

Explanation: The application module being referenced could not be found in the user library.

User Response: If the application is in the user library, contact your internal technical support.

XPD4173 CSECT IS NOT A MAIN PROCEDURE

Module: ADSRA417

Explanation: In validating the test command parameter, the module found does not represent a main procedure.


XPD4174 NO DATE/TIME PRESENT FOR X(9) MODULE

Module: ADSRA417

Explanation: The module control block (MCB) of the specified module does not have date/time information.


XPD4175 EXECUTION OF BEFORE COMMAND FAILED

Module: ADSRA417


Explanation: There was a failure in setting a before breakpoint on a module.


XPD4176 PL/I RUNTIME LIBRARIES MUST BE ALLOCATED IN XTASKLIB


Explanation: The PL/I run-time libraries must be specified on the Load Module Libraries screen (option 1 on the Setup Menu).

User Response: Verify that the libraries are present on the Load Module Libraries screen. If the libraries are listed and the message persists, contact your internal technical support.

XPD4177 PL/I SPIE AND STAE WERE RESET BY XPEDITER

Module: ADSRA221

XPD4178 PLIXOPT SPIE AND STAE RESET BY XPEDITER

Module: ADSRA221

XPD4180 REQUESTED SOURCE MODULE NOT AVAILABLE

Module: ADSRA418

Explanation: No SLS member in the DDIO dataset matches the requested source module.


XPD4181 DATA DEFINITION INVALID, NOT FOUND OR DUPLICATED

Module: ADSRA418

Explanation: No data table entry (DTE) can be found for the specified COBOL level 88 data name.


XPD4182 DATA DEFINITION NOT FOUND FOR X(64)

Module: ADSRA418

Explanation: No data table entry (DTE) can be found for the specified data name.


XPD4183 UNABLE TO ACCESS X(64), ERROR BUILDING EDB.

Module: ADSRA418

Explanation: An error has occurred while trying to build the element display block (EDB).


XPD4184 A LABEL IS NOT A VALID VARIABLE NAME

Module: ADSRA418

Explanation: The label that is referenced is not valid.

XPD4185 DUPLICATE DATA NAME, QUALIFICATION IS REQUIRED

Module: ADSRA418

Explanation: The specified data name has a duplicate data name specified in the application program.

User Response: Qualify the desired data name. Refer to the User Guide or Reference Manual for qualification rules.

XPD4186 DATA DEFINITION NOT FOUND

Module: ADSRA418

Explanation: The specified data name is unknown to the application program.



XPD4190 PROCEDURE NAME NOT FOUND IN MODULE SOURCE LISTING

Module: ADSRA419

Explanation: The procedure name specified in the command is not found in the source module.


XPD4191 NO SOURCE MODULE CONTROL BLOCK FOUND FOR PROCEDURE

Module: ADSRA419

Explanation: When trying to evaluate a paragraph or section name, they could not be found in the existing source module window block.

User Response: Verify that the correct DDIO file is allocated. Recompile the program and try again.

XPD4192 MODULE NOT FOUND

Module: ADSRA419

Explanation: The specified module cannot be found in the allocated user library.

XPD4193 LOAD OF MODULE <MODNAME> FAILED

Module: ADSRA432, ADSRA433

Explanation: This message will usually be followed by a User 3398 ABEND. The module could not be found, processing is terminated.

User Response: Check your STEPLIB, JOBLIB or LIBDEF/ISPLLIB concatenations for the proper Code Coverage libraries.

XPD4200 SOURCE LISTING TIME STAMP DOES NOT MATCH LOAD MODULE

Module: ADSRA194

Explanation: There is a time mismatch between the SLS member in the DDIO dataset and the corresponding module found in the dataset referenced by XTASKLIB DD.

User Response: Recompile the program with XPEDITER.

XPD4201 NO SOURCE LISTING INFORMATION FOUND FOR MODULE


Explanation: No SLS member was found in the DDIO dataset for the specified module.

User Response: Compile with XPEDITER.

XPD4204 SPECIFIED SOURCE LISTING NOT COMPATIBLE WITH XPEDITER. SEE LOG.

Module: ADSRA194

Explanation: The specified source listing was compiled with a version of the Language Processor (LP) that is not compatible with the current release of XPEDITER/TSO.

User Response: Recompile with the correct LP libraries.

XPD4205 THE SPECIFIED SOURCE LISTING WAS COMPILED/ASSEMBLED WITH A

XPD4206 PRIOR VERSION OF THE LANGUAGE PROCESSOR THAT’S NOT COMPATIBLE

XPD4207 WITH XPEDITER/TSO. THE REQUESTED ACTION HAS BEEN TERMINATED.

Module: ADSRA194


XPD4210 A LANGUAGE PROCESSOR INCOMPATIBILITY HAS OCCURRED.

Module: ADSRA194

Explanation: The specified Language Processor release is not compatible with XPEDITER when utilized at execution or compile.


User Response: Ensure that the Language Processor release used at execution is greater than or equal to the release used at compile. If the two releases fit the requirement, contact Compuware Technical Support. If they do not coincide, contact your internal technical support.

XPD4211 THE LANGUAGE PROCESSOR RELEASE USED TO COMPILE = NNNNNN.

Module: ADSRA194

User Response: Refer to Message XPD4210 for the appropriate user action.

XPD4212 THE LANGUAGE PROCESSOR RELEASE USED TO EXECUTE = NNNNNN.

Module: ADSRA194

User Response: Refer to Message XPD4210 for the appropriate user action.

XPD4250 STATEMENT NUMBER NOT FOUND IN MODULE

Module: ADSRA425

Explanation: An attempt was made to reference a statement number that does not exist in the module.

User Response: Check the entered statement number and try again.

XPD4251 GOTO NOT PERMITTED TO AN INACTIVE MODULE

Module: ADSRA425

Explanation: A statement in an inactive module cannot be the target of the GOTO command.

XPD4260 GOTO STATEMENT DOES NOT CONTAIN A VALID VERB

Module: ADSRA426

Explanation: The target of the GOTO command does not have executable code.

XPD4261 GOTO INACTIVE BLOCK IS NOT ALLOWED

Module: ADSRA426

Explanation: Statements in an inactive block cannot be targets of the GOTO command.

XPD4262 GOTO A PROC STATEMENT IS NOT PERMITTED

Module: ADSRA426

Explanation: PROC statements are not valid targets for the GOTO command.

XPD4263 UNABLE TO PROCESS THE GOTO STATEMENT

Module: ADSRA426

Explanation: XPEDITER cannot obtain PL/I records or cannot find the base register of the program that contains the target statement of the GOTO command.


XPD4264 GOTO CANNOT SPECIFY MERGED OUT-OF-LINE PERFORM

Module: ADSRA426

Explanation: GOTO is not permitted where the target is a performed out-of-line procedure. When a paragraph is optimized into a series of multiple performs, you cannot branch into it using the GOTO command.

XPD4265 NO GOBACK OR STOP RUN VERB FOUND FOR MODULE

Module: ADSRA426

Explanation: When trying to execute a GOBACK or STOP RUN, XPEDITER could not find either verb in the module.

XPD4266 GOTO STATEMENT IS A PROGRAM ENTRY POINT

Module: ADSRA426


Explanation: The program entry point statement cannot be the target of a GOTO command.

XPD4267 GOTO MUST BE FOR CURRENT MODULE

Module: ADSRA426

Explanation: The target of a GOTO command must be in the current module.

XPD4268 TOO MANY PARAMETERS FOR GO COMMAND

Module: ADSRA426

Explanation: Invalid GO command syntax.

User Response: Check the command syntax in the Reference Manual.

XPD4270 NO GOBACK VERB FOUND IN NESTED PROGRAM

Module: ADSRA427

Explanation: The XPEDITER GOBACK command was issued while paused in a nested COBOL program and no GOBACK verb was found within that procedure.

User Response: If a COBOL GOBACK verb was coded within the confines of the nested procedure, contact your internal technical support.

XPD4271 GOBACK NOT ALLOWED DUE TO COBOL OPTIMIZATION

Module: ADSRA427

Explanation: The XPEDITER GOBACK command is not allowed when the nested COBOL program has been compiled with the OPTIMIZE compiler option.

User Response: Specify NOOPTIMIZE on your compile if you want to use the XPEDITER GOBACK command within a nested program.

XPD4272 ’GOTO’ TARGET MUST BE WITHIN THE CURRENT PROCEDURE DIVISION

Module: ADSRA427

Explanation: A GOTO command was issued in which the destination target was outside the confines of the currently active Procedure Division. This violates the rules of COBOL and is not allowed by XPEDITER.

User Response: Designate a destination target that is within the confines of the currently active Procedure Division.

XPD4273 ’GOTO’ NOT ALLOWED DUE TO COBOL OPTIMIZATION

Module: ADSRA427

Explanation: GOTO is not allowed in nested COBOL programs when the compile unit has been compiled with the OPTIMIZE compiler option.

User Response: If you want to use the GOTO command, recompile your program with NOOPTIMIZE.

XPD4290 TRACE INTERRUPTED BY TERMINAL I/O

Module: ADSRA429

Explanation: Your program wrote data to the terminal while XPEDITER was tracing the program flow.

User Response: Continue testing.

XPD4301 XPEDITER COMMAND TABLE CANNOT BE FOUND

Module: ADSRA430

Explanation: An internal error has occurred while executing inserted code.


XPD4302 COMMAND NUMBER OUT OF SYNC WITH TABLE IN ADSRA430

Module: ADSRA430

Explanation: An internal error has occurred while executing inserted code.



XPD4351 EXPLICIT BREAKPOINT NOT PERMITTED ON INSERTED LINES

Explanation: Breakpoints are only allowed to be placed on code lines in the original source, not on lines which were inserted after the test began.


XPD4352 STATEMENT DELETED BY COBOL OPTIMIZER

Explanation: The source line in an application did not have underlying machine instructions generated by the compiler.

User Response: No breakpoints will be allowed on this line.

XPD4353 ONLY D, F, L COMMANDS ARE PERMITTED ON EXCLUDED LINES

Explanation: The only line commands allowed on lines excluded by the user are the commands to reshow the excluded lines.

User Response: Reshow the line(s) before attempting to place a breakpoint.

XPD4354 INSERT COMMAND IS INVALID IN REVIEW MODE

Explanation: Lines are not allowed to be inserted once the execution direction has been reversed.

User Response: Enter the REVERSE command again to cause execution to resume before attempting to insert lines.

XPD4355 INVALID COMBINATION OF REQUESTS SPECIFIED

Explanation: Multiple line commands were entered, two of which are mutually-exclusive.


XPD4356 BLOCK REQUEST NOT PERMITTED WITH NUMBER

Explanation: Line commands can be entered in blocks (ie, RR – RR) or with a replication factor (ie, R99), but not both.


XPD4357 BLOCK REQUEST PREVIOUSLY ENTERED IN LINE AREA

Explanation: Multiple block line commands are not allowed on the same line.


XPD4358 GT LINE COMMAND INVALID ON INSERTED CODE

Explanation: The GOTO line command can only indicate as a destination an original source code line, not a line inserted by the user.


XPD4359 GT LINE COMMAND INVALID IN REVERSE MODE

Explanation: Once execution has been reversed, the GOTO line command is not permitted.

User Response: Enter the REVERSE command again to cause execution to resume before attempting to use the GT line command.


Module: ADSRA441

Explanation: An internal error has occurred while passing the command.


XPD4415 OCCURRENCE NUMBER OUT OF BOUNDS

Module: ADSRA441


Explanation: This is a warning message. It occurs if you display a subscripted variable using a subscript that does not fall within the extent of the array or table. This usually indicates an error in the subscript value.

User Response: Examine your program to see if out of range subscripts can be used. If not, search for the cause of the bad subscript value.

XPD4416 SUBSCRIPT LIST DOES NOT MATCH DEFINITION

Module: ADSRA441

Explanation: The array or table in question has a different number of dimensions than what you have provided within the parenthesis.

User Response: Examine the variable definition to determine the correct number of dimensions in the array or table.

XPD4444 PL/I SPIE AND STAE ARE NOT FUNCTIONAL

Module: ADSRA417

Explanation: XPEDITER has disabled the PL/I SPIE and STAE options. This is necessary to run XPEDITER. These options are needed only under LE/370.


XPD4471 DDNAME FOR XPSHOW NOT ALLOCATED

Module: ADSRA447

Explanation: The SHOW command requires the ddname XPSHOW to be allocated.

User Response: Use SHOW ALLOC to check your allocations. There may be an installation error. Have your internal technical support contact Compuware Technical Support.

XPD4473 OPTION NOT SUPPORTED FOR QUALIFIED MODULE WRITTEN IN (C,9,1,<LANG>)

Module: ADSRA447

Explanation: The SHOW FILES command is invalid for this programming language.

User Response: Use the ALC or SHOW ALLOC command instead.

XPD4474 INVALID SHOW OPTION IN BATCH OR INCLUDE SCRIPT

Module: ADSRA447

Explanation: Some SHOW commands cannot be used in batch mode or in an include script.

User Response: Use an interactive test or remove the SHOW command from your script.

XPD4506 CSS INTERFACE LEVEL IS INCOMPATIBLE, PLEASE UPGRADE.

Module: ADSRA450

Explanation: You are attempting to run XPEDITER with a CSS interface level that is not current (a back-level DDIO can be used, but the execution-time interface must be current).

User Response: Allocate your test session with the current level of CSS. The currently supported level of CSS was delivered with XPEDITER but possibly was not installed.

XPD4520 ******TOP OF MODULE******

Module: ADSRA452

Explanation: The top of the current source listing has been reached.


XPD4521 ******BOTTOM OF MODULE******

Module: ADSRA452

Explanation: The bottom of the current source listing has been reached.



XPD4522 1 LINE NOT DISPLAYED

Module: ADSRA631

Explanation: A single line has been excluded from the source display.


XPD4523 (F,4,1<LINECT>),’LINES NOT DISPLAYED’

Module: ADSRA631

Explanation: Two or more consecutive lines have been excluded from the source display.


XPD4524 INVALID MESSAGE LENGTH

Module: ADSRA631

Explanation: An error has occurred while attempting to issue a message.

User Response: Contact customer support.

XPD4561 NO PARAGRAPH ON LINE FOR TRACE BTE ENTRY

Module: ADSRA456

Explanation: An error has occurred attempting to TRACE a paragraph name.


XPD4563 SOURCE INFORMATION NOT FOUND FOR MODULE

Module: ADSRA456

Explanation: An internal error has occurred attempting to execute the TRACE command.


XPD4590 OUT OF MEMORY

Module: ADSRA459

User Response: Increase either the TSO logon size or the REGION parameter on the JCL to run the batch test and begin the test again.

XPD4800 NO SUBSCRIPTS ARE ASSOCIATED WITH THIS VARIABLE

Module: ADSRA480

Explanation: Your command specified a variable with subscripts (an array). The variable in question is not defined as an array or table.

User Response: Check the variable definition. If you have specified subscripts correctly, please contact customer support.

XPD4860 CALL NUMBER MUST HAVE AT LEAST 3 CHARACTERS

Explanation: The Call Number entered had less than 3 characters.

User Response: Enter the Call Number that was supplied by the Compuware Technical Support Representative.

XPD4861 CALL NUMBER LENGTH MAY NOT EXCEED 10 CHARACTERS

Explanation: The length of the Call Number prefix, the hyphen, and the Call Number suffix is greater than 10 characters.


XPD4862 JFCB FOR XPDOC DD NOT FOUND

Explanation: An attempt was made to retrieve the JFCB of the XPDOC DD dataset so that the high level node can be obtained.



XPD4863 INVALID PARAMETER, MUST BE T, TAPE, F, OR FTP

Explanation: While entering the DOCUMENT command, an incorrect parameter was entered for the Transfer Type.

User Response: Change the incorrect parameter value to either T, TAPE, F, or FTP.

XPD4864 JCL TO RETRIEVE DOCUMENTATION HAS BEEN CREATED

Explanation: The successful completion of the JCL creation process has occurred.


XPD4865 CALL NUMBER PREFIX IS MISSING

Explanation: A hyphen was encountered without any characters preceding it.


XPD4866 CALL NUMBER PREFIX MAY NOT BE > 7 CHARACTERS

Explanation: The Call Number prefix was greater than 7 characters.


XPD4867 CALL NUMBER SUFFIX IS MISSING

Explanation: There is a space following the hyphen in the Call Number.


XPD4868 CALL NUMBER SUFFIX MAY NOT BE > 2 CHARACTERS

Explanation: The Call Number suffix is greater than 2 characters.


XPD4869 TIOT IS NOT AVAILABLE FOR XPDOC DD

Explanation: An attempt to retrieve the TIOT for the XPDOC dataset failed.


XPD4870 TIOT ADDRESS IS NOT VALID

Explanation: An attempt to retrieve the TIOT for the XPDOC dataset failed.


XPD4871 XPDOC DATASET HIGH LEVEL NODE IS > 8 CHARACTERS

Explanation: The high level qualifier for the XPDOC dataset is invalid.


XPD4872 DOCUMENT COMMAND PASSED THE EDIT ROUTINE

Explanation: The values that were entered with the DOCUMENT command passed the edit routines.


XPD4873 THE OPEN FAILED FOR THE XPDOC DATASET

Explanation: An unsuccessful attempt was made to open the XPDOC dataset.


XPD4874 THE CALL NUMBER IS MISSING A HYPEN OR HAS IMBEDDED SPACES

Explanation: The hyphen that separates the Call Number prefix from the Call Number suffix is missing, or there are imbedded spaces before the hyphen.



XPD4875 NOT ENOUGH STORAGE AVAILABLE FOR REQUEST

Explanation: An unsuccessful attempt was made to get storage during the processing of the DOCUMENT command.

User Response: Increase the amount of region available to the test and try the command again. If you are still having the problem, contact Compuware Technical Support.

XPD4876 FREEMAIN FOR A STORAGE BUFFER FAILED

Explanation: During the DOCUMENT command process, storage was obtained for various tables. An attempt to free this storage failed.

User Response: To free the storage, exit the XPEDITER/TSO test.

XPD4877 INVALID PARAMETER, MUST BE B, BOTH, D, DOC, L, OR LOG

Explanation: While entering the DOCUMENT command, an incorrect parameter was entered for the JCL print location.

User Response: Change the incorrect parameter value to either B, BOTH, D, DOC, L, or LOG.

XPD4878 LMB CONTROL BLOCK ADDRESS IS INVALID

Explanation: An XPEDITER/TSO control block has an invalid address.


XPD4879 MCB CONTROL BLOCK ADDRESS IS INVALID

Explanation: An XPEDITER/TSO control block has an invalid address.


XPD4880 AN OVERFLOW CONDITION HAS OCCURRED ON ONE OF THE INTERNAL COUNTERS

Explanation: A table to hold the names of the requested modules has surpassed its limit.


XPD4881 AN OVERFLOW CONDITION HAS OCCURRED ON THE COLLCTIN BUFFER

Explanation: The buffer to store the control cards from the COLLCTIN dataset has reached the end and there are more control cards to process.


XPD4882 THE SEARCH FOR LOAD MODULE, xxxxxxxx, FAILED.

Explanation: While putting together the STEPLIB DD for one of the JCL steps, either module CWDDSUTL or module ADSSU300 could not be found.

User Response: Make sure that the CSS load library is accessible to the XPEDITER/TSO test.

XPD4930 LOAD MODULE X(8) IS LINKED AMODE=31 OR RMODE=ANY.

Module: ADSRA493

Explanation: Refer to message XPD4939.

User Response: Refer to messages associated with XPD4939. There is a problem with the way this program is linked.

XPD4931 IT CONTAINS AN OS/VS COBOL MODULE.

Module: ADSRA493



XPD4932 ISSUE THE SHOW MODULES COMMAND TO LIST THE LOAD MODULE AND CSECTS.

Module: ADSRA493




XPD4933 ***ENTER INPUT DATA FOR ACCEPT FROM SYSIN***


Explanation: This is a request via the ACCEPT verb, designed to enter data from the terminal for the SYSIN DD.

User Response: Enter the input information and press Enter.

XPD4934 AN OPEN WAS ISSUED TO AN OPEN FILE; UNABLE TO CONTINUE


Explanation: A request has occurred to open a file which is already open.

User Response: Check the program for multiple open statements against the same DDname.

XPD4935 AN ERROR OCCURRED DURING JFCB RETRIEVAL


Explanation: XPEDITER could not retrieve the JFCB for a DDname.

User Response: Contact Technical Support.

XPD4936 NO FILE ALLOCATION FOR DDNAME X(8)

Module: ADSRA493

Explanation: Your program is trying to access the named DDname, but that file has not been previously allocated.

User Response: Use the ALLOC command to modify your File Allocation Utility (FAU) to include this file. You may also use TSO ALLOC on the command line for a simple allocation.

XPD4937 MEMBER X(8) IS NOT IN FILE X(8)

Module: ADSRA493

Explanation: The PDS member name specified in the allocation of your file does not exist.

User Response: Check your file allocations.

XPD4938 ***ENTER INPUT RECORD OR/*(AT END) FOR DDNAME INFILE***


Explanation: A request to read a record from an input file that has been assigned to the terminal has occurred. The file that is being read is assigned to the DDname at the end of the message.

User Response: Enter the information for the specific record and press Enter to continue with the program. When you want to signify the end of the file, enter the following:

/* (forward slash, asterisk)

XPD4939 WARNING: COBOL OS/VS MODULE IS LINKED AMODE 31 OR RMODE ANY. SEE LOG.

Module: ADSRA493

Explanation: OS/VS COBOL does not support AMODE 31 or RMODE ANY.

User Response: Refer to the associated messages. There is a problem with the way this program is linked.

XPD4940 CANCEL REQUEST BY (C,8,1<PROGRAM>), SATISFIED-

Module: ADSRA494

Explanation: A COBOL test program issued a CANCEL statement and the function was completed.



XPD4941 CANCEL REQUEST BY (C,8,1<PROGRAM>), IGNORED

Module: ADSRA494

Explanation: A COBOL test program issued a CANCEL statement but the function had already been performed previously.


XPD5555 PL/I LIBRARIES ARE PRELOADED OR IN PROTECT

Module: ADSRA417



XPD5691 LENGTH PREVIOUSLY SPECIFIED

Explanation: The parameter indicating the amount of storage to GETMAIN was specified more than once.

User Response: Remove all length specifications but one.

XPD5692 BOUNDARY VALUE NOT DBLWD OR PAGE

Explanation: The only valid specifications for the BNDRY keyword are DBLWD or PAGE.


XPD5693 INVALID HEX INITIALIZATION DIGIT

Explanation: An invalid hexadecimal digit was specified in the INIT parameter.

User Response: Use only acceptable digits (0-9, A-F) when specifying hex data.

XPD5694 INVALID LENGTH SPECIFIED

Explanation: An invalid value was specified for the LA or LV keyword.

User Response: Use a register specification (0-9 or 10-15) or an address containing valid hex digits (0-9, A-F) for LA, or specify a valid decimal number for LV.

XPD5695 LOCATION OPTION NOT ANY, ABOVE, OR BELOW

Explanation: An invalid value was specified for the LOC keyword.

User Response: Specify a valid option: LOC=ANY, LOC=ABOVE, or LOC=BELOW.

XPD5696 INVALID REFERENCE FOR RETURN OF ADDRESS

Explanation: The value for the Address keyword is not a valid register, address, or label.


XPD5697 SUBPOOL SPECIFICATION NOT IN RANGE OF 0 THRU 127

Explanation: A non-decimal value or number greater than 127 was specified for the SP keyword.

User Response: Specify one of the allowable subpools. Subpools greater than 127 are not supported.

XPD5698 LENGTH OF GETMAIN WAS NOT SPECIFIED

Explanation: No length was specified in the GETMAIN command.

User Response: Specify at least a length value when requesting storage.

XPD5971 NO COUNT BREAKPOINTS IN EFFECT

Module: ADSRA598

Explanation: A SHOW COUNTS command was issued but there are no count breakpoints.



XPD5973 NO WHEN REQUESTS IN EFFECT

Module: ADSRA598

Explanation: A SHOW WHEN command was issued but there are no WHENs currently active.


XPD6010 ADSRA529 RETAIN IMS BREAKPOINTS DISABLED, GETMAIN FOR nnnn BYTES FAILED

Explanation: XPEDITER attempted to obtain nnnn bytes of storage in order to enable the Retain IMS Breakpoints feature. This storage was no available. The test proceeds without the Retain IMS Breakpoints feature.

User Response: Increase the amount of above the line storage available to the test session. For TSO, you may want to use 0M for the LOGON Size.

XPD6011 ADSRA529 RETIMSB COMMAND FAILURE: xxxx

Explanation: XPEDITER is unable to process command xxxx upon the second or latter iteration of the IMS MPP test. In the message, xxxx is the command that failed. It can be up to 100 characters.

User Response: Examine the XPEDITER LOG for more data. If the reason for the command failure is not apparent, contact Compuware Technical Support.

XPD6012 ADSRA529 RETIMSB FAILURE LMBNAME=xxxxxxxx MCBNAME=xxxxxxxx MCBBTECT=nnnn XIMS BTECT=nnnn

Explanation: XPEDITER will issue this message if there is a mismatch between the stored breakpoint count and the current source breakpoint count.

User Response: Please have the LOG as well as the DDIO and LOADLIB available and contact Compuware Technical Support.

XPD6013 ADSRA529 RETIMSB FAILURE: XIMS=xxxxxxxx yyyy=xxxxxxxx

Explanation: XPEDITER will issue this message if there is a mismatch between the stored breakpoint module information and the current source module information. yyyy will be LMB or MCB.


XPD6014 ADSRA529 RETIMSB FAILURE: LMB=xxxxxxxx MCB=xxxxxxxx yyyy=xxxxxxxx

Explanation: XPEDITER will issue this message if there is a mismatch between the stored breakpoint data and the current source breakpoint data. yyyy will be BTE if the data is from the current source or XIMS if it is from the stored breakpoint data, either of which will be followed by the actual control block data.


XPD6033 <ABEND> ABEND ENCOUNTERED, USE “AA SNAP” FOR ADDITIONAL INFORMATION

Module: ADSRA410

Explanation: None.


XPD6070 SOURCE X(8) HAS CONFLICTING TIME-DATE STAMP AND ANY SOURCE REFERENCE TO MODULE X(8) WILL BE REJECTED

Module: ADSRA194

Explanation: Relates to XPD6074.

User Response: Relates to XPD6074.

XPD6071 SOURCE MEMBER X(8) X(5) HAS CONFLICTING TIME-DATE STAMP AND ANY SOURCE REFERENCE TO MODULE X(8) WILL BE REJECTED

Module: ADSRA194




XPD6072 LOAD MODULE X(8) X(5) HAS CONFLICTING TIME-DATE STAMP AND ANY SOURCE REFERENCE TO MODULE X(8) WILL BE REJECTED

Module: ADSRA194



XPD6073 A CONFLICTING TIME-DATE STAMP EXISTS AND ANY SOURCE REFERENCE TO MODULE X(8) WILL BE REJECTED

Module: ADSRA194



XPD6074 A CONFLICTING TIME-DATE STAMP EXISTS. BEFORE CONTINUING, CHECK MESSAGES AND CODES FOR FURTHER ACTION

Module: ADSRA194

Explanation: A date-time conflict exists between the load module and the DDIO member for this module. XPEDITER requires that you run with a matching DDIO and LOADLIB member to generate valid test results.

User Response: Check your SETUP panels to make sure that you have proper LOADLIB and DDIO datasets. Recompile successfully, making sure that the LOADLIB and DDIO specified in the JCL are the same as those in the SETUP. If you are sure the source level of the load module matches that of the DDIO dataset, even though the date-time stamp is different, you may continue the test by using the SET DATETIME OFF command to bypass date-time checking. However, if they do not match, results will be unpredictable, including S0C4s and the display of wrong data, as XPEDITER will be operating with incorrect information. If the date-time stamp information is illegible, XPEDITER may be having a conflict with another vendor product that also writes to the IDRDATA in the load module. In this case, you may need to customize XPEDITER to prevent this conflict. Contact your internal technical support for details.

XPD6076 SOURCE LOAD MODULE HAS CONFLICTING DATE - TIME STAMP

Module: ADSRA607


XPD6077 ADSCPDEF OPTION CTLDTOFF=N OVERRIDES BOTH CTLDTCON=N AND CTLDATTM=Y

Module: ADSRA194

Explanation: Since the settings of CTLDATTM and CTLDTCON could circumvent the setting of CTLDTOFF (N = Don’t allow the SET DATETIME OFF command), they are overridden by CTLDTOFF=N. These options are specified in the JCLRA093 (installation defaults) macro as detailed in the XPEDITER/TSO and XPEDITER/IMS Installation Guide.

User Response: Adjust options as required by your site.

XPD6120 MODULE OR PROCEDURE NAME CANNOT BE FOUND

Module: ADSRA612

Explanation: The specified module was not found in the datasets 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.

XPD6123 INVALID COMMAND FOR ’AT’ DISPLAY

Module: ADSRA612

Explanation: The command entered is not valid for sourceless debugging.

User Response: Refer to the reference manual for a list of valid commands.


XPD6125 INVALID PARAMETER

Module: ADSRA612

Explanation: An invalid parameter was used with the command.

User Response: Refer to the Reference Manual and check the command syntax.

XPD6127 LOAD MODULE CANNOT BE FOUND

Module: ADSRA612

Explanation: The module used for qualification cannot be found in the datasets 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.

XPD6128 DUPLICATE MODULE NAME - QUALIFY WITH LOAD MODULE NAME

Module: ADSRA612

Explanation: A duplicate module name was found in the allocated libraries. Use the load module name as the qualifier.

XPD6129 SKIP MODULE NAME MAY NOT HAVE ADDITIONAL PARAMETERS

Module: ADSRA612

Explanation: Invalid SKIP module syntax.

User Response: Refer to the Reference Manual for valid syntax and try again.

XPD6140 UNBALANCED LITERAL

Module: ADSRA614

Explanation: The command entered does not have a matching delimiter.

User Response: Correct and try again.

XPD6143 CURSOR NOT IN GPR FIELD

Module: ADSRA614

Explanation: The cursor is not positioned in the GPREGS display window.

User Response: Reposition the cursor and try again.

XPD6144 NO SOURCE STRING FOUND

Module: ADSRA614

Explanation: The cursor is not positioned at any data identifier.

User Response: Reposition the cursor and try again.

XPD6145 NO SOURCE DEFINITION FOUND FOR STRING X(64)

Module: ADSRA614

Explanation: The cursor is positioned on a label that is not defined as data.

XPD6147 INVALID ADDRESS STRING FOR PEEK CSR

Module: ADSRA614

Explanation: The cursor is positioned on an address that does not point to a data area.

XPD6148 X(8) IS AN INVALID ADDRESS FOR PEEK CSR

Module: ADSRA614

Explanation: The address specified by the cursor location is not accessible in memory. It is fetch protected.

User Response: Check the address of the memory you want to display to see if it looks like a reasonable address.


XPD6160 INSUFFICIENT STORAGE FOR BRR CONTROL BLOCK

Module: ADSRA616


XPD6170 EXCESSIVE NUMBER OF PARAMETERS SPECIFIED

Module: ADSRA617

Explanation: Too many parameters were entered from the command line for the USING or DROP command.

User Response: Look for extra spaces or commas that may have been entered. Refer to the XPEDITER/TSO and XPEDITER/IMS Reference Manual to check the command syntax.

XPD6171 NO ACTION SPECIFIED BY COMMAND

Module: ADSRA617

Explanation: The USING and DROP commands require additional parameters.

User Response: Refer to the XPEDITER/TSO and XPEDITER/IMS Reference Manual to check the command syntax.

XPD6172 INVALID NAME SPECIFIED BY COMMAND

Module: ADSRA617

Explanation: An invalid dsect item name was entered on the command.

User Response: Check the user program for the exact spelling.

XPD6173 LABEL NAME MUST IMMEDIATELY PRECEDE + OR -

Module: ADSRA617

Explanation: An offset value is not permitted with this command.

User Response: An offset can only be used relative to a dsect item name in the format label+offset.

XPD6175 NO ADDRESS, REGISTER OR ADDRESS EXPRESSION SPECIFIED

Module: ADSRA617

Explanation: The base location for the command was omitted.

User Response: This field can be an address, a register, a variable, or a variable expression.

XPD6176 INVALID REGISTER NUMBER SPECIFIED

Module: ADSRA617

Explanation: An invalid register number was entered.

User Response: Only the general-purpose registers are allowed: registers 0 through 15.

XPD6177 INVALID ADDRESS OR OFFSET SPECIFIED

Module: ADSRA617

Explanation: The base location has an incorrect address.

User Response: The address may have more than 8 digits or an invalid character,as specified.

XPD6178 NO PREVIOUS USING TO DROP

Module: ADSRA617

Explanation: An XPEDITER USING was not entered for this DROP.

User Response: Specify a SHOW USING command to show what USINGs have been entered.

XPD6210 ADDRESS OF ITEM IS BAD, CHECK SUBSCRIPT OR INDEX

Module: ADSRA621


Explanation: The address of the variable that you are attempting to type over is invalid. This may be caused by an out of bounds subscript.

User Response: Check your current subscripts for the variable. If you cannot determine the problem, contact your internal technical support.

XPD6212 VALUE TOO LONG TO PROCESS

Module: ADSRA178

Explanation: Message processing has located an internal message in error.


XPD6213 TARGET DATA ADDRESS IN PROTECTED STORAGE

Module: ADSRA621

Explanation: The variable value that you are attempting to modify may only be browsed. It cannot be updated as it is store protected.


XPD6214 INVALID HEX DATA

Module: ADSRA621

Explanation: The data that was entered does not consist of valid hexadecimal digits.

User Response: Hexadecimal digits are 0 through 9 and A through F. Check the value that was entered.

XPD6215 INVALID NUMERIC DATA

Module: ADSRA621

Explanation: An error was encountered while attempting to move the entered value into the numeric variable.

User Response: Check the entered value for all numeric digits 0 through 9.

XPD6216 INVALID BINARY DATA

Module: ADSRA621

Explanation: Valid binary data consists of ones and zeros. Blanks cannot be imbedded within the data.

User Response: Check the entered value.

XPD6230 DISPLAY OF X(64) NOT SUPPORTED

Module: ADSRA623

Explanation: This type of variable is not yet supported by XPEDITER for display purposes.

User Response: Contact customer support to request an enhancement if it is important for you to view this type of data.

XPD6231 HEX NOT ALLOWED ON BIT DATA

Module: ADSRA623

Explanation: XPEDITER does not currently support doing a hexadecimal display of bit variables.

User Response: Contact customer support to request an enhancement if it is important for you to view this type of data.

XPD6250 INVALID OFFSET SPECIFIED

Module: ADSRA625

Explanation: The offset specified is beyond the end of the current module.

User Response: Supply an offset in this module or use an absolute address.


XPD6251 LOCATION NOT FOUND FOR VALUE

Module: ADSRA625

Explanation: XPEDITER was unable to determine a context for the address or name that was entered. It was not a part of any known module/CSECT.

User Response: Check the spelling of names and the value of the address that was entered.

XPD6252 NO ACTIVE MODULE LOCATED FOR OFFSET

Module: ADSRA625

Explanation: An offset was entered as a parameter, but there is no module that can be used as a base for the offset.

User Response: The command requires at least one module to be active or you must specify the module name in the command.

XPD6253 OFFSET X(64) LOCATED AT X(8)

Module: ADSRA625

Explanation: This is the output of the WHEREIS command when an offset was entered as a parameter.

XPD6254 ADDRESS X(8) LOCATED IN X(8) AT OFFSET X(6)

Module: ADSRA625

Explanation: This is the output of the WHEREIS command when an address was entered as the parameter.

XPD6255 MODULE X(8) LOCATED AT X(8)

Module: ADSRA625

Explanation: This is the output of the WHEREIS command when a module-name was entered as the parameter.

XPD6256 LABEL X(64) LOCATED IN X(8) AT OFFSET X(6)

Module: ADSRA625

Explanation: This is the output of the WHEREIS command when a label was entered as the parameter.

XPD6258 NOT A PARA, PROC OR PROG - DATA NAMES NOT VALID

Module: ADSRA625

Explanation: The parameter on the WHEREIS command could not be resolved to a paragraph, procedure, or program name. Data names are not valid for this command.

XPD6259 LOAD MODULE NAME: WITHOUT MODULE NAME: - INCORRECT

Module: ADSRA625

Explanation: Incorrect syntax was used with the WHEREIS command.

User Response: Correct syntax and try again.

XPD6260 GO OPERAND NOT PERMITTED FOR MODULE WITHOUT SOURCE

Module: ADSRA626

Explanation: The user has issued the GO command in conjunction with an operand.

User Response: If in an abend condition, enter 'GO' without an operand to return to the test panel. If in sourceless debugging, entering 'GO' without an operand will cause the program to run to completion..

XPD6261 GO TO STATEMENT HAS BEEN DEACTIVATED WITH SKIP COMMAND

Module: ADSRA626

Explanation: You may not GOTO a statement that is currently being skipped.



XPD6262 NO DESTINATION FOR GO TO SPECIFIED

Module: ADSRA626

Explanation: GOTO was entered without a valid parameter (e.g., a line number).

User Response: Check the Reference Manual and enter the command again with a valid parameter.

XPD6263 ILLEGAL VALUE ENTERED FOR GO

Module: ADSRA626

Explanation: The parameter entered with GO is invalid.

User Response: Check the Reference Manual for valid parameters and try again.

XPD6265 GO TO STATEMENT DOES NOT CONTAIN VALID REFERENCE

Module: ADSRA626

Explanation: The label/paragraph name specified on the GOTO command cannot be found.

User Response: Verify that the name is correct and try again.

XPD6266 GO TO STATEMENT SAME AS CURRENT STATEMENT

Module: ADSRA626

Explanation: The statement specified is at the same offset as the current statement.

User Response: Select another statement.

XPD6267 GOTO VALID ONLY FROM ACTIVE MODULE SOURCE

Module: ADSRA426

Explanation: No program other that the currently executing program can be displayed on the screen when the XPEDITER GOTO command is entered.

User Response: Use the SOURCE or LOC * command to display the currently executing program, then reissue the GOTO command.

XPD6268 DESTINATION OF GOTO COMMAND MUST BE WITHIN THE CURRENT FUNCTION

Module: ADSRA426

Explanation: GOTO is not permitted where the target exists in a function other than the one currently executing.


XPD6269 EXIT LINKAGE FOR ACTIVE PROC OR FUNCTION NOT FOUND

Module: ADSRA426

Explanation: When trying to execute the RETURN command, XPEDITER could not find code associated with an END instruction causing a return from a PL/I procedure or a closing brace causing a return from a function in C/370.


XPD6305 INVALID ACTION FOR MODULE LEVEL BREAKPOINT ACTION

Module: ADSRA630

Explanation: The command entered cannot be used at the module level but can be used in conjunction with a statement number or paragraph/label name.

User Response: Enter the command again with the correct parameter.

XPD6310 ERROR IN INDIRECT ADDRESSING CALCULATION

Module: ADSRA631

Explanation: An error has occurred during calculation of the indirect address value of the source window.



XPD6340 DATA ITEM NOT FOUND ON SOURCE LINE

Module: ADSRA634

Explanation: A PEEK/KEEP was placed on a line which contains no variables, such as a LR instruction.

XPD6341 NO STORAGE FOR COUNT MAX BLOCK

Module: ADSRA634

Explanation: No storage is available for XPEDITER to build an internal block.

User Response: Log on with more memory.

XPD6360 COMMAND ONLY PERMITTED ON INSTRUCTION LINE

Module: ADSRA636

Explanation: The line indicated did not contain an instruction. It may be a comment, null line, or continued line.

XPD6361 COMMAND ONLY PERMITTED ON CODE OR DATA LINE

Module: ADSRA636

Explanation: The line indicated did not contain code or a data definition.

XPD6362 TYPE OF BLOCK COMMAND NOT ALLOWED ON SPECIFIED LINE

Module: ADSRA636

Explanation: Block commands must start and end on valid lines, depending on the commands used.

User Response: See the Reference Manual for command information.

XPD6363 GT STATEMENT SAME AS CURRENT STATEMENT

Module: ADSRA636

Explanation: The GT (GOTO) line command cannot be put on a line with the active arrow.

XPD6364 GT LINE COMMAND CAN ONLY BE USED IN ACTIVE MODULE

Module: ADSRA636

Explanation: In Assembler and COBOL, the GT (GOTO) line command is restricted to the active module or module where the active arrow resides.

XPD6370 EXECUTION COUNT MAX MUST BE GREATER THAN COUNT

Module: ADSRA637

Explanation: The maximum count must be greater than the number of counts displayed.

User Response: Increase the MAX number.

XPD6371 INVALID COUNT SPECIFIED AS MAXIMUM FOR BREAKPOINT

Module: ADSRA637

Explanation: The maximum count must be a decimal number of not more than 7 digits.

User Response: Be sure the COUNT MAX field contains a decimal number.

XPD6391 ERROR ENCOUNTERED DURING EVALUATION OF CALC SUFFIX

Module: ADSRA639

Explanation: The (+/-) offset field was incorrect.

User Response: Check the digits in the offset field for incorrect hexadecimal digits or for an erroneously entered + or -.

XPD6392 INVALID TARGET REFERENCE

Module: ADSRA639


Explanation: No target for the move was entered, or the information inside the parentheses is incorrect.

User Response: Check command syntax.

XPD6393 NULL VALUE SPECIFIED FOR DATA REFERENCE

Module: ADSRA639

Explanation: The “from” data name is missing.

User Response: Check command syntax.

XPD6395 MODULE REFERENCE INVALID

Module: ADSRA639

Explanation: A module name reference with the “from” data name cannot be found.

User Response: If the module name is correct, check the command syntax.

XPD6396 DUPLICATE MODULE NAME - QUALIFY WITH LOAD MODULE NAME

Module: ADSRA639

Explanation: When more than one module with the same module name is to be loaded by XPEDITER, it is necessary to use the load module name.

User Response: Qualify the module name in the command as follows:LOAD-MODULE-NAME::MODULE-NAME:DATA-NAME

XPD6397 MOVE REQUEST FOR MOD WITH DIFFERENT LANGUAGE THAN SOURCE

Module: ADSRA639

Explanation: XPEDITER only allows moves of information between modules of like languages.

User Response: Check language of both the “from” field and the target field.

XPD6400 INVALID HEXADECIMAL CHARACTER ENTERED

Module: ADSRA640

Explanation: The field was typed over by a character that was not 1 through 9 or A through F.

User Response: Try again.

XPD6401 INVALID MNEMONIC OPERATION CODE

Module: ADSRA640

Explanation: The OPCODE was typed over with an invalid entry.

XPD6402 DATA IS IN PROTECTED MEMORY

Module: ADSRA640

Explanation: The data that was typed over is in protected storage.

XPD6411 INSERT COMMAND NOT VALID ON COMMAND LINE

Module: ADSRA641

Explanation: The INSERT command cannot be used on the command line.

User Response: Use the I line command or use a script.

XPD6412 TOO MANY DIGITS ENTERED FOR GO COMMAND

Module: ADSRA641

Explanation: The maximum number of digits that can be used on the GO n command is 6.

XPD6541 LOCATE AMOUNT OUTSIDE VALID RANGE FOR THIS MEMORY SCREEN

Module: ADSRA654


Explanation: The valid range for the Memory screen is defined by the top and bottom of data lines. This can be extended by manual scrolling.

User Response: Scroll to the desired location by using the scroll commands UP and DOWN.

XPD6590 OPERAND SEPARATOR WORD TO NOT FOUND

Module: ADSRA659

Explanation: The XPEDITER MOVE command requires the TO keyword to separate the operands.

User Response: Place the keyword TO between the operands and try again.

XPD6591 GPR OR SOURCE LISTING TARGET REQUIRED FOR SOURCE OPERAND

Module: ADSRA659

Explanation: The XPEDITER MOVE command requires that the target data area for this source item be a general-purpose register (GPR) or be referred to by a label within the source listing.

User Response: Make sure that the operand after the TO keyword is a GPR or a data label.

XPD6592 TARGET DATA ADDRESS IN PROTECTED STORAGE

Module: ADSRA659

Explanation: An attempt was made with the XPEDITER MOVE command to move to a data item which is addressable but whose address is in protected storage.

User Response: Check the base register and the length of storage obtained for the data item.

XPD6593 NO ADDRESS FOR TARGET DATA ITEM

Module: ADSRA659

Explanation: An attempt was made with the XPEDITER MOVE command to move to an item that is not addressable.

User Response: Execute the program until addressability to the target data item is obtained, or use the XPEDITER USING command.

XPD6594 NUMERIC LITERAL LENGTH EXCEEDS 15 DIGITS

Module: ADSRA659

Explanation: An attempt was made to use the XPEDITER MOVE command with a literal operand longer than allowed by the command.

User Response: Check the length and contents of the literal item and try again.

XPD6595 NUMERIC LITERAL CONTAINS INVALID CHARACTER

Module: ADSRA659

Explanation: The source operand of the XPEDITER MOVE command contains a character which is not in the range of 0 through 9.

User Response: Refer to the MOVE command section in the XPEDITER/TSO and XPEDITER/IMS Reference Manual.

XPD6596 INVALID SOURCE OPERAND

Module: ADSRA659

Explanation: The first operand of the XPEDITER MOVE command is not compatible with the data type of the target operand.

User Response: Check the source operand for spelling errors. Refer to the MOVE command section in the XPEDITER/TSO and XPEDITER/IMS Reference Manual.

XPD6597 NO TARGET OPERAND SPECIFIED FOR MOVE

Module: ADSRA659

Explanation: The XPEDITER MOVE command requires an operand after the TO keyword.


User Response: Use proper syntax for the MOVE command. Refer to the MOVE command section in the XPEDITER/TSO and XPEDITER/IMS Reference Manual for additional information.

XPD6598 HEXADECIMAL LITERAL CONTAINS INVALID CHARACTER

Module: ADSRA659

Explanation: The hexadecimal string of the source operand contains a character that is not EBCDIC code.

User Response: Check the string for invalid characters.

XPD6599 DBCS LITERAL CONTAINS INVALID DATA

Module: ADSRA659

Explanation: The DBCS string of the source operand contains invalid data.

User Response: Check the string for non-DBCS characters.

XPD6610 X(8) COMMAND(S) COMPLETED

Module: ADSRA661

Explanation: confirms a count of the XPEDITER commands Informational message; confirms a count of the XPEDITER commands executed.

User Response: This message can be suppressed, if desired, by issuing the SET CONFIRM OFF command. For additional information, refer to the SET command section in the XPEDITER/TSO and XPEDITER/IMS Reference Manual.

XPD6620 TEST NOT PERMITTED AS PRIMARY COMMAND

Module: ADSRA662

Explanation: The TEST command is not a valid primary command during a test session. It can only be entered in the input command stream (XPIN DD).

User Response: Refer to the TEST command section in the XPEDITER/TSO and XPEDITER/IMS Reference Manual.

XPD6621 INVALID OPTION, DB2 NOT IN EFFECT

Module: ADSRA662

Explanation: The option is only valid if a DB2 environment has been established under XPEDITER.

User Response: Enter YES in the Is This a DB2 Test? field on the front test panel. The System field must also be filled in. Refer to the XPEDITER/TSO and XPEDITER/IMS User’s Guide for additional information.

XPD6666 VALUE TOO LONG TO PROCESS

Module: ADSRA417



XPD6702 OFFSET KEYWORD NOT ALLOWED IN COBOL MODULE

Module: ADSRA670

Explanation: The reference on the command cannot be offset. This is an Assembler only parameter.

User Response: Keywords that can be used are module, paragraph, procedure, or label. Procedure should not be used in COBOL.

XPD6704 NO OFFSET BREAKPT CALCULATION ALLOWED IN COBOL MODULE

Module: ADSRA670

Explanation: A plus sign was detected, which indicates an offset. Offset and address can only be used in Assembler.

User Response: Remove the plus sign if statement number is desired.


XPD6705 CANNOT SET BREAKPOINT ON COBOL SYSTEM MODULES

Module: ADSRA670

Explanation: A module name with the first characters of IGZ or ILBO was detected. These are COBOL system modules.

User Response: XPEDITER does not allow breakpoints to be set on these modules except with the AT command.

XPD6730 UNBALANCED PARENTHESES

Module: ADSRA673

Explanation: Unbalanced parentheses were entered in the command.

User Response: Check command entry.

XPD6732 INVALID SEQUENCE OF LOGICAL OPERANDS

Module: ADSRA673

Explanation: XPEDITER was expecting to find a right or left parentheses.

User Response: Recheck the command structure.

XPD6733 IMPROPER USE OF CHANGED KEYWORD

Module: ADSRA673

Explanation: A mixture of class expression and changed keyword was detected.

User Response: The CHANGE keyword can only be used with a variable.

XPD6750 EXTRANEOUS PARAMETER

Module: ADSRA675

Explanation: More information was found on this command than was required.

User Response: Check command and retry.

XPD6751 INVALID RANGE

Module: ADSRA675

Explanation: An invalid statement number was detected after the THRU keyword.

User Response: Check statement range.

XPD6770 INVALID SHOW OPTION FOR THIS ENVIRONMENT

Module: ADSRA677

Explanation: Not all SHOW commands can be executed in all environments.

User Response: Check the XPEDITER/TSO and XPEDITER/IMS Reference Manual for the SHOW commands that are valid.

XPD6771 SUB-MODULE IS REENTRANT, NOT ACTIVE - NO ADDRESSABILITY

Module: ADSRA677

Explanation: SHOW DCB, SHOW FILES, and SHOW INDEX cannot be executed until the REENTRANT module becomes active.

User Response: Set a breakpoint in the REENTRANT module and try again when module is active.

XPD6780 INVALID SET OPTION

Module: ADSRA678

Explanation: An invalid SET command was entered.

User Response: Check the spelling or refer to the XPEDITER/TSO and XPEDITER/IMS Reference Manual for valid SET commands.


XPD6781 INVALID SET OPTION FOR THIS ENVIRONMENT

Module: ADSRA678

Explanation: The SET command entered cannot be used in a batch environment.

User Response: Check the XPEDITER/TSO and XPEDITER/IMS Reference Manual for uses of specific SET commands.

XPD6931 BOTTOM OF DATA REACHED

Module: ADSRA693, ADSRA702, ADSRA703, ADSRA711, ADSRA769, and ADSRA771

Explanation: The FIND command was issued and the target was not found. As a result, the bottom of the source was encountered.


XPD6932 TOP OF DATA REACHED

Module: ADSRA693, ADSRA702, ADSRA703, ADSRA711, ADSRA769, and ADSRA771

Explanation: The FIND command was issued and the target was not found. As a result, the bottom of the source was encountered.


XPD6933 INVALID LENGTH RECEIVED FOR LITERAL

Module: ADSRA693

Explanation: The string cannot exceed 48 characters.

User Response: Remove some of the characters from the search item.

XPD6934 PARAMETER INVALID FOR THIS ENVIRONMENT

Module: ADSRA693

Explanation: Only string finds can be used with the memory panels.

User Response: Use quotes around the item used for search.

XPD6960 OVERTYPE AREA IS IN PROTECTED STORAGE

Module: ADSRA696

Explanation: The area you wish to type over may be write protected but not fetch protected.

User Response: You cannot type over write protected areas.

XPD7010 GETMAIN FAILED FOR FIND CONTROL BLOCK

Module: ADSRA701

Explanation: GETMAIN for 700 bytes failed.

User Response: Try logging on with a larger region size.

XPD7011 INVALID SEQUENCE OF QUALIFICATION PARAMETERS

Module: ADSRA701

Explanation: An invalid sequence of data-name qualifiers was detected.

User Response: Correct and retry command.

XPD7012 NO PREVIOUS FIND ISSUED

Module: ADSRA701

Explanation: An F * command was issued without a prior FIND command having successfully completed.


XPD7030 NO STRUCTURE VERB FOUND FOR SPECIFIED GROUP(S)

Module: ADSRA703


Explanation: Refer to Format 3 of the FIND command (COBOL language only) Primary Command Syntax located in the XPEDITER/TSO and XPEDITER/IMS Reference Manual for a list of COBOL structure keywords. Refer also to Appendix A, COBOL Structure Keywords, in the XPEDITER/TSO and XPEDITER/IMS Reference Manual for additional information.


XPD7031 (C,7,1,<COUNT>),”,(C,12,2,<TYPE>),’FOUND’

Module: ADSRA703

Explanation: This is the resulting number of COBOL Structure Verbs found.


XPD7032 (C,7,1,<COUNT>),

Module: ADSRA703

Explanation: This is the number of finds qualified for the selected groups.


XPD7040 PROGRAM COMPILED WITHOUT ENHANCED FIND

Module: ADSRA704

Explanation: The enhanced FIND option was not enabled when the program was compiled.

User Response: Refer to the Compuware Shared Services Installation and Customization Guide for information on enhanced FIND.

XPD7041 GETMAIN FAILED FOR THE CSV TABLE - FIND TERMINATED

Module: ADSRA704

Explanation: GETMAIN failure occurred.

User Response: Log on with a larger region size.

XPD7042 SNT/VSTMT MISMATCH. FIND TERMINATED. SEE LOG.

Module: ADSRA704

Explanation: An error was detected while processing enhanced FIND tables.

User Response: See the log for more information.

XPD7043 A MISMATCH OCCURRED BETWEEN SNT RECORDS AND THE VERB RECORDS.

Module: ADSRA704

Explanation: A statement number in the VERB table could not be matched to a statement number table entry.


XPD7051W XOPTIONS FILE NOT ALLOCATED - ENHANCED FIND DISABLED

Module: ADSRA705

Explanation: The XOPTIONS ddname is not available to the XPEDITER session.

User Response: Verify that the dataset allocated to the XOPTIONS ddname is the correct VSAM XOPTIONS file, and that it was entered correctly in your system installation.

XPD7052W ERROR OCCURRED OPENING XOPTIONS FILE

Module: ADSRA705

Explanation: An error was encountered opening the XOPTIONS VSAM file.

User Response: Verify that the dataset allocated to the ddname XOPTIONS is a valid VSAM OPTIONS dataset, and that it has not been damaged.

XPD7053W NO INPUT/OUTPUT MODULE DEFINITIONS FOUND

Module: ADSRA705


Explanation: When processing the XOPTIONS dataset, no record was found for the INPUT/OUTPUT module definition options.

User Response: Supply the appropriate INPUT/OUTPUT record and rebuild the XOPTIONS dataset.

XPD7054W NO DLI OPTIONS RECORD FOUND

Module: ADSRA705

Explanation: When processing the XOPTIONS dataset, no record was found for the DLI options.

User Response: Supply the appropriate DLI options record and rebuild the XOPTIONS dataset.

XPD7055W NO MESSAGE CASE RECORD FOUND

Module: ADSRA705

Explanation: When processing the XOPTIONS dataset, no record was found for the MESSAGE CASE option.

User Response: If uppercase messages are required, supply the appropriate MESSAGE CASE option record and rebuild the XOPTIONS dataset.

XPD7120 REQUIRED STRING MISSING

Module: ADSRA712

Explanation: The string for a string FIND was not found in the command.

User Response: Check the command in the XPEDITER/TSO and XPEDITER/IMS Reference Manual.

XPD7200I XPEDITER/TSO and XPEDITER/IMS VV.RR.MM SVC INSTALLATION PROCESS HAS STARTED.

Module: CWXTSVCI

Explanation: CWXTSVCI has started the process of installing XPEDITER/TSO and XPEDITER/IMS SVC.


XPD7201I CWXTSVCI PROCESSING SUCCESSFULLY COMPLETED.

Module: CWXTSVCI

Explanation: CWXTSVCI has completed and successfully performed the requested function.


XPD7202E CWXTSVCI PROCESSING TERMINATED DUE TO ERROR.

Module: CWXTSVCI

Explanation: CWXTSVCI encountered an error while performing the requested function.

User Response: Check the job log for prior XPD72xxE message(s) and follow the user response for those message(s).

XPD7203I CWXTSVCI PARM=”xxxxxxxxxxxxxxxxxxxxxxxxx”.

Module: CWXTSVCI

Explanation: CWXTSVCI echoes the PARM passed to it for verification and debugging purposes.

User Response: None, unless debugging a PARM related error. In which case follow the user responses for the XPD72xxE error message(s).

XPD7204I CWXTSVC START ADDR=X’nnnnnnnn’, LENGTH=X’nnnnnnnn’.

Module: CWXTSVCI

Explanation: This message is provided for documentation and debugging purposes. It displays the starting address of CWXTSVC and its length.


User Response: None, but this information may be requested by XPEDITER/TSO and XPEDITER/IMS support personnel.

XPD7210E CWXTSVCI PARM “SVC=” MUST BE SPECIFIED.

Module: CWXTSVCI

Explanation: The positional PARM “SVC=” was not found. The PARM for CWXTSVCI has the following format: “PARM=’fffffff,SVC=sss,WAIT=x’". Where fffffff is ’INSTALL’, ’REPLACE’, or ’DEINSTALL’; sss is a valid number from 200 through 255; and x is either ’Y’ (Yes) or ’N’ (No).

User Response: Fix the PARM for CWXTSVCI and resubmit the job. For more information refer to the “SVC Installation Utility” in Chapter 13.0 of the XPEDITER/TSO and XPEDITER/IMS Installation Guide.

XPD7211E CWXTSVCI PARM “SVC=” MUST BE A THREE DIGIT NUMERIC FIELD: 200-255.

Module: CWXTSVCI

Explanation: The number given for the SVC parameter is not valid. The PARM for CWXTSVCI has the following format: “PARM=’fffffff,SVC=sss,WAIT=x’". Where fffffff is ’INSTALL’, ’REPLACE’, or ’DEINSTALL’; sss is a valid number from 200 through 255; and x is either ’Y’ (Yes) or ’N’ (No).


XPD7212E CWXTSVCI PARM LENGTH IS NOT VALID FOR SELECTED OPTION.

Module: CWXTSVCI

Explanation: The length of the PARM is not long enough for the requested function. The PARM for CWXTSVCI has the following format: “PARM=’fffffff,SVC=sss,WAIT=x’". Where fffffff is ’INSTALL’, ’REPLACE’, or ’DEINSTALL’; sss is a valid number from 200 through 255; and x is either ’Y’ (Yes) or ’N’ (No).


XPD7213E CWXTSVCI PARM OPTION IS NOT VALID, MUST BE INSTALL, REPLACE, OR DEINSTALL.

Module: CWXTSVCI

Explanation: The first positional parameter (the option or function) is not valid. The PARM for CWXTSVCI has the following format: “PARM=’fffffff,SVC=sss,WAIT=x’". Where fffffff is ’INSTALL’, ’REPLACE’, or ’DEINSTALL’; sss is a valid number from 200 through 255; and x is either ’Y’ (Yes) or ’N’ (No).


XPD7214E CWXTSVCI PARM “WAIT=” MUST BE SPECIFIED.

Module: CWXTSVCI

Explanation: The positional PARM “WAIT=” was not found. The PARM for CWXTSVCI has the following format: “PARM=’fffffff,SVC=sss,WAIT=x’". Where fffffff is ’INSTALL’, ’REPLACE’, or ’DEINSTALL’; sss is a valid number from 200 through 255; and x is either ’Y’ (Yes) or ’N’ (No).


XPD7215E CWXTSVCI PARM “WAIT=” MUST BE EITHER “Y” OR “N”.

Module: CWXTSVCI

Explanation: The value given for the WAIT parameter is not valid. The PARM for CWXTSVCI has the following format: “PARM=’fffffff,SVC=sss,WAIT=x’". Where fffffff


is ’INSTALL’, ’REPLACE’, or ’DEINSTALL’; sss is a valid number from 200 through 255; and x is either ’Y’ (Yes) or ’N’ (No).


XPD7230E NUCLKUP BYNAME FAILED FOR “IGCERROR”.

Module: CWXTSVCI

Explanation: CWXTSVCI utilizes the MVS service NUCLKUP to locate the entry point of IGCERROR, however the call to NUCLKUP failed.

User Response: Contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Support Representative.

XPD7231E NUCLKUP BYADDR FAILED FOR SPECIFIED SVC NUMBER.

Module: CWXTSVCI

Explanation: CWXTSVCI utilizes the MVS service NUCLKUP to locate the entry point of SVC to be replaced. However, the call to NUCLKUP failed.

User Response: Contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7232E SVC ENTRY TO BE REPLACED IS NOT “IGCERROR” OR “CWXTSVC”.

Module: CWXTSVCI

Explanation: The SVC entry to be replaced for the INSTALL option is not “IGCERROR”. For DEINSTALL or REPLACE, the SVC entry to be replaced is not “CWXTSVC”.

User Response: (1) For INSTALL, the SVC number specified is probably already in use by another product or in-house written routine. Try selecting a new SVC number. If it is not already in use, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative. (2) For REPLACE, the SVC number specified is not CWXTSVC; CWXTSVC may not have been previously installed. If the SVC number specified is correct and CWXTSVC was not previously installed, change REPLACE to INSTALL and resubmit CWXTSVCI. If CWXTSVC was previously installed, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative. (3) For DEINSTALL, the SVC number specified is not CWXTSVC; CWXTSVC may not have been previously installed. If the SVC number specified is correct and CWXTSVC was not previously installed, ignore the error. If CWXTSVC was previously installed, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7233E SVC ENTRY TO BE DEINSTALLED OR REPLACED IS NOT “CWXTSVC”.

Module: CWXTSVCI

Explanation: The SVC entry to be deinstalled or replaced is not “CWXTSVC”.

User Response: (1) For REPLACE, the SVC number specified is not CWXTSVC; CWXTSVC may not have been previously installed. If the SVC number specified is correct and CWXTSVC was not previously installed, change REPLACE to INSTALL and resubmit CWXTSVCI. If CWXTSVC was previously installed, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative. (2) For DEINSTALL, the SVC number specified is not CWXTSVC; CWXTSVC may not have been previously installed. If the SVC number specified is correct and CWXTSVC was not previously installed, ignore the error. If CWXTSVC was previously installed, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.


XPD7240E ENQ FAILED FOR “SYSZSVC” “TABLE” AND WAIT=Y WAS SPECIFIED.

Module: CWXTSVCI

Explanation: An error occurred while CWXTSVCI was trying to obtain exclusive control of the SVC table for MVS.

User Response: Try resubmitting the job. If the error persists, contact Compuware Technical Support. Please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7241E ENQ FAILED FOR “SYSZSVC” “TABLE” AND WAIT=N WAS SPECIFIED.

Module: CWXTSVCI

Explanation: An error occurred while CWXTSVCI was trying to obtain exclusive control of the SVC table for MVS.

User Response: You will receive this message if there are other XPEDITER/TSO and XPEDITER/IMS users currently using the product. Try resubmitting the job with WAIT=Y and ask all other users to exit the product. If the error persists, contact Compuware Technical Support. Please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7242E ENQ FAILED FOR “COMPUWAR” “XPEDITER.CWXTSVC” AND WAIT=Y WAS SPECIFIED.

Module: CWXTSVCI

Explanation: An error occurred while CWXTSVCI was trying to obtain exclusive control of the XPEDITER/TSO and XPEDITER/IMS SVC.

User Response: Try resubmitting the job. If the error persists, contact Compuware Technical Support. Please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7243E ENQ FAILED FOR “COMPUWAR” “XPEDITER.CWXTSVC” AND WAIT=N WAS SPECIFIED.

Module: CWXTSVCI

Explanation: You will receive this message if there are other XPEDITER/TSO and XPEDITER/IMS users currently using the product.

User Response: Try resubmitting the job with WAIT=Y and ask all other users to exit the product. If the error persists, contact Compuware Technical Support. Please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7250E “SVCUPDTE DELETE” FAILED.

Module: CWXTSVCI

Explanation: While processing a DEINSTALL or REPLACE function, the SVCUPDTE DELETE failed for the SVC number.

User Response: The SVC number specified may not be CWXTSVC; CWXTSVC may not have been previously installed. If the SVC number specified is correct and CWXTSVC was previously installed, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7251E “SVCUPDTE REPLACE” FAILED.

Module: CWXTSVCI

Explanation: While processing an INSTALL or REPLACE function, the SVCUPDTE REPLACE failed for the SVC number.


XPD7252E SVC NUMBER CANNOT BE INSTALLED, IT IS ALREADY “CWXTSVC”.

Module: CWXTSVCI


Explanation: While processing an INSTALL function, it was discovered that the requested SVC is already CWXTSVC.

User Response: If you wanted to install the SVC, it has already been installed, so ignore the error. If you have applied maintenance or want to install a newer version of the SVC, change INSTALL to REPLACE and resubmit the job. If CWXTSVC is not already installed, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7260E CSA START ADDRESS AND SVC START ADDRESS DO NOT MATCH.

Module: CWXTSVCI

Explanation: While processing a DEINSTALL or REPLACE function, it was discovered that an inconsistency existed in CWXTSVC.


XPD7261E ERROR FREEING EXISTING SVC.

Module: CWXTSVCI

Explanation: While processing a DEINSTALL or REPLACE function, an error occurred in the FREEMAIN of the previous CWXTSVC.


XPD7270E LOAD OF “CWXTSVC” FROM STEPLIB FAILED.

Module: CWXTSVCI

Explanation: An error occurred loading CWXTSVC while processing an INSTALL or REPLACE function.

User Response: Ensure that CWXTSVC exists in the load library referenced by the STEPLIB DD statement in the JCL submitted. If you have already done this and the problem persists, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7271E GETMAIN FAILED FOR “CWXTSVC”.

Module: CWXTSVCI

Explanation: The GETMAIN failed for the size of CWXTSVC in SUBPOOL 228 (FIXED ECSA) while processing an INSTALL or REPLACE function.

User Response: You may have exhausted the FIXED ECSA in your system, consult your MVS system programmer to determine if an error exists or if you need to have the size of the ECSA for your MVS increased. If ample ECSA exists in your system, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7272E “CWXTSVC” IS NOT AT OFFSET 4 FROM SVC ENTRY.

Module: CWXTSVCI

Explanation: While processing an INSTALL or REPLACE function, it was discovered that an inconsistency existed in CWXTSVC.

User Response: Contact Compuware Technical Support. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7273E “CWXTSVC” IS AT A HIGHER RELEASE THAN “CWXTSVCI”.

Module: CWXTSVCI

Explanation: While processing an INSTALL or REPLACE function, it was discovered that CWXTSVC was at a higher release level than CWXTSVCI.


User Response: SVC maintenance must be performed with the most current version of CWXTSVCI. Locate the library with the most current release of CWXTSVCI and change the library referenced in your STEPLIB DD statement to point to it. If you have already done this and the problem persists, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7274E “CWXTSVC” WAS NOT LINKED AC=1.

Module: CWXTSVCI

Explanation: While processing an INSTALL or REPLACE function, it was discovered that CWXTSVC was not LINKED with AC=1.

User Response: It is important that CWXTSVCI and CWXTSVC are linked using the JCL in JCLLKSVC. Run the JCL JCLLKSVC in the XPEDITER/TSO and XPEDITER/IMS installation library and then resubmit the job. If you have already done this and the problem persists, contact Compuware Technical Support. Please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7275E LOAD OF “CWXTSVCL” FROM STEPLIB FAILED.

Module: CWXTSVCI

Explanation: An error occurred loading CWXTSVCL while processing a LIST function.

User Response: Ensure that CWXTSVCL exists in the load library referenced by the STEPLIB DD statement in the JCL submitted. If you have already done this and the problem persists, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7280E “CWXTSVCI” REQUIRES A MINIMUM OF MVS/ESA 3.1.3 TO FUNCTION PROPERLY.

Module: CWXTSVCI

Explanation: CWXTSVCI and XPEDITER/TSO and XPEDITER/IMS breakpoint processing are only available for MVS 3.1.3 and higher. As such, CWXTSVCI and CWXTSVC were assembled for MVS 3.1.3 and above. They also use the services of MVS only when it is available on MVS 3.1.3 and above.

User Response: The required functionality is not available on this system and you cannot use it on this system. If this system is MVS/ESA 3.1.3 or higher and you received this message, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7281E “CWXTSVCI” IS NOT APF AUTHORIZED.

Module: CWXTSVCI

Explanation: To function, CWXTSVCI must go into “supervisor” state to update the necessary MVS control structure that defines the XPEDITER/TSO and XPEDITER/IMS SVC utility to MVS.

User Response: To run CWXTSVCI, CWXTSVCI and CWXTSVC must reside in an MVS APF authorized library. Refer to Chapter 2 of the XPEDITER/TSO and XPEDITER/IMS Installation Guide. If CWXTSVCI and CWXTSVC are in an MVS APF authorized library, contact Compuware Technical Support. You will probably be asked to send an MVS System Dump to resolve the problem. In addition, please supply your MVS or OS/390 release to the Compuware Technical Support Representative.

XPD7431 IDENTIFIER NOT FOUND

Module: ADSRA753

Explanation: Because the COMPUTE command has not been incorporated for XPEDITER, this message is now obsolete.


XPD7432 (C,64), IS NOT DEFINED AS NUMERIC

Module: ADSRA753




XPD7433 OPERATOR NOT PRECEDED BY IDENTIFIER, A NUMERIC

Module: ADSRA753



XPD7434 COMMA IS NOT PERMITTED EXCEPT TO SEPARATE

Module: ADSRA753



XPD7435 PARANTHESIS ARE IMBALANCED

Module: ADSRA753



XPD7436 COMPUTE COMMAND REQUIRES “=” AND NONE FOUND

Module: ADSRA753



XPD7446 DIVIDE HAS PRODUCED A REMAINDER OF:

Module: ADSRA754



XPD7447 EMBEDDED PARANTHETICAL LEVEL(S) SKIPPED

Module: ADSRA754



XPD7448 EVALUATION COMPLETE FOR LEVEL ’,(B,2),’

Module: ADSRA754



XPD7449 CURRENT LEVEL IS ’,(B,2),’

Module: ADSRA754




XPD7450 EVALUATION WORK TABLE.......AT

Module: ADSRA754



XPD7491 THE NUMERIC VALUE WITHIN THE EXPRESSION BEING EVALUATED FOR

XPD7492 PEEK/KEEP PROCESSING IS EITHER TOO LARGE OR TOO SMALL TO

XPD7493 PROCESS. KEEP/PEEK PROCESSING IS TERMINATED.

Module: ADSRA749

Explanation: The numeric value of the expression was less than -2147483648 or greater than +2147483647.

User Response: You cannot do a KEEP or PEEK on this line.

XPD7521 ’,(C,79),’

Module: ADSRA752

Explanation: Because the COMPUTE command has not been incorporated for XPEDITER, this message is obsolete.


XPD7522 INVALID (OR UNDEFINED) OPERAND’,(C,48),’

Module: ADSRA752



XPD7523 NUMERIC LITERAL IS NOT PERMITTED BEFORE”=”

Module: ADSRA752



XPD7524 COMPUTE COMMAND CONTAINS NO OPERANDS

Module: ADSRA752



XPD7525 ’,(C,30),’ IS UNDEFINED

Module: ADSRA752



XPD7526 ’(C,64)’ IS NOT A NUMERIC FIELD....#62P3

Module: ADSRA752



XPD7540 (X,4),’LVL’,(B,2),PREV EWT’,(X,4)’

Module: ADSRA754




XPD7680 GETMAIN FAILED FOR THE PDT BLOCK - FIND TERMINATED

Module: ADSRA768

Explanation: XPEDITER ran out of storage while processing FIND.

User Response: Restart XPEDITER or logon with a larger memory size.

XPD7681 NO RECORDS EXIST FOR VARIABLES WITHIN PROCEDURE DIVISION

Module: ADSRA768

Explanation: Either there were no variables in the statements in the Procedure Division or the program was not compiled with the enhanced FIND option turned on.

User Response: Recompile with the enhanced FIND option or regard this as just an informational message.

XPD7683 THE ENHANCED FIND TABLES COULD NOT BE PROPERLY BUILT.

Module: ADSRA768

Explanation: This is a general message describing the problem. It will be followed by message XPD7684 or message XPD7685, which will further describe the problem.


XPD7684 AN ENTRY IS MISSING FOR THE XXXXXXXX ASSOCIATED WITH STATEMENT YYYYYY.

Module: ADSRA768

Explanation: A data-name record could not be matched to a Data Division occurrence.


XPD7685 THE SHI TABLE IS INCOMPLETE AFTER STATEMENT ENTRY YYYYYY.

Module: ADSRA768

Explanation: Due to internal conditions, one of the tables used for Enhanced Find is incomplete, preventing further processing and producing the error message. The statement entry refers to the last statement in the module listing that was successfully processed. It may be followed by a ‘Copy Suppress’ statement. Removing the Copy Suppress option may circumvent the problem.


XPD7690 NO MATCH ON SELECTED DATA NAME

Module: ADSRA769

Explanation: The data name entered in the COBOL Primary FIND command (Refer to Format 1 or 2 Syntax) doesn’t match any selected source data name.


XPD7691 END OF INDIRECT SEARCH

Module: ADSRA769

Explanation: The next data name defined by the initial COBOL Primary FIND command (Refer to Format 2 Syntax) could not be found.


XPD7692 NO FIND INDIRECT CURRENTLY IN PROGRESS

Module: ADSRA769

Explanation: The Primary FIND INDirect command was entered without having a prior COBOL FIND command (Refer to Format 2 Syntax) with an INDirect option.


User Response: Enter a COBOL Primary FIND command (Refer to Format 2 Syntax) with and INDirect option.

XPD7693 INVALID DATA ELEMENT FOR NOREDEFINES KEYWORD

Module: ADSRA769

Explanation: A message has been issued to the terminal indicating that a FIND data name was issued with the NORedefine keyword and the data element found was identified with a special level number of 66 or 77. The data name of such a special level number data element cannot be used with the FIND data name NORedefine command.

User Response: Reissue the FIND command with the appropriate data name and keywords.

XPD7694 (C,6,1<REF>), DATA REF: ,(C,10,2<DEF>), <=== MORE

Module: ADSRA769

Explanation: An informational message has been issued to the terminal and optionally, to the log dataset. This messages shows a data name reference count of 1 and the associated define count(s) for a FIND data name command issued with the INDirect keyword or issued as find ALL REFerences.

Note: The message ID is not included as part of the message.

User Response: None. However, activation of the message to the log is controlled by the setting of the LOG FIND command.

XPD7695 (C,6,1<REF>), DATA REFS: ,(C,11,2<DEF>),’ ’, <=== MORE

Module: ADSRA769

Explanation: An informational message has been issued to the terminal and optionally, to the log dataset. This message shows the data name reference counts and any associated define, use, or modification counts for a FIND data name command issued with the INDirect keyword or issued as find ALL REFerences. This message will always contain the DATA REFS: field and its count but other fields with counts of zero will be removed from the message prior to printing.


User Response: None. However. activation of the message to the log is controlled by the setting of the LOG FIND command.

XPD7696 (C,16,1<DEF>) ’ ’,(C,17,2<MODUSE>),’ ’, <=== MORE

Module: ADSRA769

Explanation: An informational message has been issued to the terminal and optionally, to the log dataset. This message shows the results obtained from a FIND data name command issued with one of the three reference keywords (DEF, USE, or MOD) with or without the ALIAS keyword. If ALIAS was not specified or not found, that portion of the message will be eliminated.



XPD7697 LEVEL OF INDIRECTION=,(F,4,1<LEVEL>)

Module: ADSRA769

Explanation: An informational message, issued to the log dataset, has identified the current level of indirection associated with the FIND data name INDirect command, which has just been issued. This message will be followed with the associated source lines found by the FIND data name INDirect command.




XPD7698 PROGRAM=,(C,8,1<PROGRAM>)

Module: ADSRA703, ADSRA711, ADSRA769, and ADSRA771

Explanation: An informational message has been issued to the log dataset, identifying the active program. This message will be preceded, in the log, by an XPEDITER FIND command issued against the active program and the results of the command will be displayed following this message.



XPD7710 NO MATCHING DATA NAME IN REQUESTED COBOL GROUP(S)

Module: ADSRA771

Explanation: A message has been issued to the terminal indicating that a FIND command was issued for a data name in a COBOL group and a match was not located.

User Response: If necessary, reissue the FIND command with the correct information.

XPD7711 (C,6,1,<COUNT>),’OCCURRENCES OF’,(C,30,2<DN>), <=== MORE

Module: ADSRA771

Explanation: An informational message has been issued to the terminal and optionally, to the log dataset, giving a count of occurrences found for a data name in the specified COBOL group.



XPD7777 NO PL/I OPTIONS MODULE TO RESET

Module: ADSRA417

Explanation: The PL/I option module(s) that issue the (E)SPIE and (E)STAE could not be located. XPEDITER/TSO must be able to locate the module and prevent PL/I from issuing any (E)SPIE or (E)STAE.

User Response: Verify that the PL/I options module is contained within the PL/I run-time libraries.

XPD7932 INVALID COMBINATION OF PARAMETERS

Module: ADSRA793

Explanation: Two or more of the parameters entered cannot be used in conjunction with each other.

User Response: Eliminate the invalid combination of parameters from the command and try again.

XPD7933 REQUIRED PARAMETER MISSING

Module: ADSRA793

Explanation: A command was entered that required one or more parameters. The parameter(s) were not found.

User Response: Correct and retry.

XPD7934 A COBOL KEYWORD WAS SPECIFIED BUT THE REQUESTED COBOL DATA NAME WAS NOT FOUND

Module: ADSRA793


Explanation: A find command was entered with a COBOL-specific keyword. The requested COBOL data name could not be located. The data name may have been specified as a quoted string or forced to default as quoted.

User Response: If specified incorrectly, correct and retry. Otherwise, contact Compuware Technical Support.

XPD7950 SPECIFIED STRING REQUIRES AN ENDING DELIMITER

Module: ADSRA795

Explanation: The string must end with a quote, apostrophe, or ==.

User Response: Correct and retry.

XPD8033 XPED DB2 SP DEBUGGING HAS NOT BEEN ACTIVATED SINCE LAST IPL

Explanation: First run of XPDB2SP since IPL.


XPD8034 REQUESTED FUNCTION REQUIRES APF AUTHORITY

Explanation: The program being executed is not in an authorized library.

User Response: Move the program being executed to an authorized library or authorize the library that it resides in.

XPD8035 MISSING OR INCORRECT EXEC PARM

Explanation: PARM is not ACTIVATE, DEACTIVATE, FORCE or MAINTENANCE.

User Response: Correct the PARM and rerun.

XPD8036 INCORRECT SYSIN RECFM OR LRECL

Explanation: The SYSIN dataset must be Fixed or Fixed-Blocked, and the LRECL must be 80.

User Response: Correct the JCL and rerun.

XPD8037 DUPLICATE DB2 SUBSYSTEM NAME 'xxxx' FOUND IN SYSIN

Explanation: Self explanatory.

User Response: Correct the SYSIN input and rerun.

XPD8038 SYNTAX ERROR IN ABOVE SYSIN RECORD

Explanation: The SYSIN card that preceeds this message has a syntax error.


XPD8039 SYSIN DD MISSING OR DOESN'T INCLUDE DB2 SUBSYSTEM NAMES

Explanation: The SYSIN card is missing or no DB2 subsystem names were specified.

User Response: Correct the SYSIN input (at least one DB2 subsystem name is required) and rerun.

XPD8040 XT DD MISSING

Explanation: The XT DD card is missing.

User Response: Add the XT DD card pointing to the XPEDITER loadlib.

XPD8041 MEMBER NAME 'mmmmmmmm' MISSING FROM XPEDITER LOAD LIBRARY DEFINED BY DD 'XT'

Explanation: Required module 'mmmmmmmm' is not in the library specified by the XT DD card.

User Response: Check dataset specified on the XT DD card, ensure that required module 'mmmmmmmm' is in that library, and rerun.

XPD8042 LOAD MODULE 'mmmmmmmm' NOT REENTRANT, TOO LONG, AMODE 24 OR ITS NAME IS AN ALIAS



User Response: Check options used in JCLLKDB2 member, correct and relink, then rerun.

XPD8043 COULDN'T ACQUIRE 'xxxx' BYTES FROM CSA


User Response: Check with your MVS system programmer.

XPD8044 COULDN'T ACTIVATE, ALREADY ACTIVE



XPD8045 COULDN'T DEACTIVATE, ALREADY INACTIVE



XPD8046 COULDN'T APPLY MAINTENANCE, NEED TO BE DEACTIVATED FIRST


User Response: Run the program with PARM=DEACTIVATE.

XPD8047 SUCCESFULLY ACTIVATED



XPD8048 SUCCESFULLY DEACTIVATED



XPD8049 MAINTENANCE APPLIED SUCCESSFULLY



XPD8050 COULDN'T DEACTIVATE BECAUSE OF SOME XPED DB2 SP SESSION(S) STILL IN PROGRESS. USE EXEC PARM=FORCE TO DEACTIVATE


User Response: Wait for active users to finish and run again, or run with PARM=FORCE.

XPD8051 NUMBER OF XPED DB2 SP SESSION(S) IN PROGRESS IS xxxx



XPD8052 WLM IS NOT INSTALLED

Explanation: IBM's Workload Manager is required for XPEDITER DB2 Stored Procedure support.


XPD8053 MVS LEVEL BELOW MINIMUM REQUIREMENT (OS/390 V1.R3). XPED DB2 SP FEATURE CAN'T BE SUPPORTED



XPD8054 +++ MSG # USED BY ROUTINE XPDB2PCR +++




XPD8055 XPED DB2 SP SUPPORT CSA STUB ADDRESS IS xxxxxxxx



XPD8068 IMS USER ID SUPPORT INTERCEPT HAS NOT BEEN ACTIVATED SINCE LAST IPL

Explanation: First run of XPIMSTLR since IPL.


XPD8069 DUPLICATE IMS SUBSYSTEM NAME 'xxxx' FOUND IN SYSIN



XPD8070 SYSIN DD MISSING OR DOESN'T INCLUDE IMS SUBSYSTEM NAMES

Explanation: The SYSIN card is missing or no IMS subsystem names were specified.

User Response: Correct the SYSIN input (at least one IMS subsystem name is required) and rerun.

XPD8071 COULDN'T DEACTIVATE BECAUSE OF SOME XPED/IMS SESSION(S) STILL IN PROGRESS. USE EXEC PARM=FORCE TO DEACTIVATE


User Response: Wait for active users to finish and run again, or run with PARM=FORCE.

XPD8072 NUMBER OF XPED/IMS SESSION(S) IN PROGRESS IS xxxx



XPD8073 MVS LEVEL BELOW MINIMUM REQUIREMENT (ESA 4.2.2). XPED/IMS USER ID SUPPORT FEATURE CAN'T BE SUPPORTED



XPD8077 TRAN AUTH EXIT XPIMSRN0 NOT FOUND

Module: DFSCTRN0

Explanation: The XPEDITER/IMS userid support exit could not locate module XPIMSRN0.

User Response: If your site uses the DFSCTRN0 exit for a function additional to XPEDITER/TSO, the additional exit should be installed as XPIMSRN0. See the XPEDITER/TSO Installation Guide for instructions on installing the additional exit with XPEDITER/TSO IMS userid support.

XPD8078 TRAN AUTH EXIT DFSCTRN0 EPA=8006B2F0

Module: DFSCTRN0

Explanation: The XPEDITER/IMS userid support exit was loaded at the indicated location.


XPD8079 IMS USER ID SUPPORT SETUP NOT FOUND

Module: DFSCTRN0

Explanation: XPEDITER/TSO expected that IMS userid support was installed, but found the installation incomplete.


XPD8081 SEVERE ERROR. DFSCSIIO NOT AVAILABLE

Module: DFSCTRN0

Explanation: IMS service routine DFSCSIIO returned an error to DFSCTRN0. The IMS User ID support is disabled.



XPD8082 SEVERE ERROR. CSA STORAGE NOT AVAILABLE

Module: DFSCTRN0

Explanation: A request for CSA storage failed. The IMS User ID support is disabled.


XPD8083 SEVERE ERROR. UNABLE TO FIND USER EXIT

Module: DFSCTRN0

Explanation: XPEDITER was unable to find your DFSCTRN0 exit (which has been renamed to XPIMSRN0).The IMS Used ID support is disabled.

User Response: Ensure the IMS control region steplib contains the library for XPIMSRN0.

XPD8084 SEVERE ERROR. CSA STUB ADDRESS MISSING

Module: DFSCTRN0

Explanation: Logic error in DFSCTRN0. The address of the IMS User ID table is invalid. The IMS User ID support is disabled.


XPD8085 SEVERE ERROR. CSI SERVICE FAILURE

Module: DFSCTRN0

Explanation: IMS service routine DFSCSIIO returned an error to DFSCTRN0. The IMS User ID support is disabled.


XPD8086 DB2 PC INTERCEPT CODE IS NOT AT THE CORRECT LEVEL

Explanation: This message indicates that the DB2 PC intercept install program has tried to load XPDB2PCR, and the release level of that load module does not match the installing program.

User Response: Correct the STEPLIB or the XPEDITER DD control card for the install job, then rerun the job.

XPD9800 LOG COMMAND NOT VALID IN BATCH

Explanation: Not all XPEDITER commands can be used in batch mode.

User Response: Refer to the user guide or reference manual for valid commands.

XPD9801 EXCLUDE COMMAND NOT VALID IN BATCH


User Response: Refer to the XPEDITER/TSO and XPEDITER/IMS User’s Guide or Reference Manual for valid commands.

XPD9802 COMMAND NOT VALID IN BATCH




Explanation: This is an internal problem; perhaps something has been overlayed.


XPD9804 RETEST COMMAND NOT VALID IN BATCH




XPD9806 TRACE NOT ALLOWED FROM SOURCELESS DEBUGGING SCREEN

Explanation: TRACE can only be used from a source screen.

XPD9807 COUNT NOT ALLOWED FROM SOURCELESS DEBUGGING SCREEN

Explanation: COUNT can only be used from a source screen.

XPD9808 WHEN NOT ALLOWED FROM SOURCELESS DEBUGGING SCREEN

Explanation: WHEN can only be used from a source screen.

XPD9809 INVALID COMMAND TO DELETE

User Response: Refer to the XPEDITER/TSO and XPEDITER/IMS Reference Manual or enter HELP DELETE for a list of valid commands.

XPD9810 COMMAND INVALID WITH DELETE

User Response: Refer to the XPEDITER/TSO and XPEDITER/IMS Reference Manual or enter HELP DELETE for a list of valid commands.

XPD9815 SPECIFIED STATEMENTS NOT EXCLUDED - RESET WITH ’END’

Explanation: An EXCLUDE was not set on this statement.

User Response: All EXCLUDEs can be reset by END or RESET.

XPD9816 COMMAND NOT ALLOWED FOR DISPLAY ONLY LINE

Explanation: The command is allowed only for a code line or data line.

User Response: Retry command on a code line or data line.

XPD9990 MODULE NAME CANNOT END WITH A DOT

Module: ADSRA612

Explanation: Module names must end with a single colon (:) and load module names must end with a double colon (::).

User Response: Check the syntax of the command entered.

XPD9993 MODULE NAME MUST FOLLOW LOAD MODULE NAME

Explanation: When the load module name is entered, the next name must be the module or CSECT name.

XPD9994 INVALID LITERAL SPECIFICATION

Module: ADSRA659

Explanation: No terminal quote was found on the literal.

User Response: Add quote to end of literal and try again.

XPD9995 NO EDB AVAILABLE FOR ITEM

Module: ADSRA659

Explanation: Not enough information could be found to build the XPEDITER control block for the target data name.

User Response: Check the syntax of the command entered. Contact your support person if the syntax and data name are correct.

XPD9997 NUMERIC LITERAL CANNOT BE MOVED TO INSTRUCTION

Module: ADSRA659

Explanation: Neither the numeric literal nor the character literal should be used to change an instruction.

User Response: To change the instruction area of the program, use the hexadecimal literal.

3-1

Chapter 3.
3User Abend Codes Chap 3
ABEND 3000

Module: XPHOGNPF, XPHOGNIF, XPHOGNBF, XPHOGNTF, XPRDLIST, XPBTSLNK, XPEDCTL, ADSRA207, and ADSRA300

Explanation: This ABEND always means there is insufficient storage for an XPEDITER/TSO compile.

User Response: Increase the REGION for the JOB or STEP, and resubmit the compile job.

ABEND 3001 AN INVALID SERVICE REQUEST HAS BEEN SENT TO ADSRA000

Module: ADSRA000

Explanation: Module ADSRA000 is the dynamic CALL TRANSFER version of XPEDITER. One of its functions is to manage XPEDITER modules, both loading and deleting. The module also maintains an internal control stack. An invalid service call was issued.


ABEND 3002 UNABLE TO TEST USER PROGRAM

Module: XPTSO, XPDRP, and XPINIT

Explanation: XPEDITER is unable to test the user program.

User Response: See the session log for additional details. The ABEND reason code is set as follows:

ABEND 3003 XPEDITER BLDL FAILURE

Module: ADSIM002

Explanation: An attempt to call an XPEDITER module failed because the module could not be found in the STEP or JOBLIB libraries.

User Response: Verify that the correct libraries are present; if the problem persists, contact your internal technical support.

ABEND 3007 AN XPEDITER RECURSIVE ABEND HAS OCCURRED

Module: ADSRA105

Explanation: Successive ABENDS occurred while an application module was being tested.


20 The user program named on the TEST and/or INTERCEPT control card could not be found.

22 The XPIN control cards are invalid.

24 The required PARM field was omitted for an IMS or BTS test.

26 The XPOUT DD card was missing or could not be opened.

28 The TASKLIB and/or XTASKLIB DD card was missing or could not be opened.

30 The XPIN DD card was missing or could not be opened.

32 An error exists in the assembly of ADSRA093 (the user may have updated ADSCPDEF).


ABEND 3008 AN XPEDITER TIME-OUT HAS OCCURRED DURING TERMINAL RECOVERY.

Module: ADSRA105

Explanation: XPEDITER exhausted the time threshold while attempting to recover from a terminal ABEND.


ABEND 3009 A DIAGNOSE ABEND HAS BEEN REQUESTED

Module: ADSRA148

Explanation: The XPEDITER DIAGNOSE command was used to generate an ABEND of the XPEDITER region.

User Response: Contact your internal technical support and provide them with the SYSUDUMP and other materials.

ABEND 3051 MAXIMUM OF 15 BASE REGISTERS EXCEEDED

Module: ADSRA217

Explanation: The maximum number of base locator cells that XPEDITER can maintain is 15. This maximum was exceeded.


ABEND 3052 ALLOCATION OF GPR BUFFER FAILED

Module: ADSRA217

Explanation: An attempt to allocate memory failed for the GPR buffer.


ABEND 3092 OPEN FAILED FOR XTASKLIB

Module: XPHOGNFF

Explanation: An attempt to open the XTASKLIB DD failed.

User Response: Add the XTASKLIB DD to your JCL or CLIST and try again.

ABEND 3093 IDENTIFY FAILED FOR SUBTASK

Module: XPHOGNFF and ADSIM004

Explanation: A critical error occurred during setup of the BTS environment.


ABEND 3094 ATTACH OF SUBTASK FAILED

Module: XPHOGNFF and ADSIM004



ABEND 3095 ATTACH OF BTS FAILED

Module: XPBTBTSF, XPHOGNFF, and ADSIM004


User Response: Verify that the appropriate BTS libraries were included in the STEPLIB and run again.

ABEND 3097 BTS CONTROL BLOCK NOT FOUND

Module: ADSIM004

Explanation: A previously constructed BTS control block cannot be located. Probable memory overlay.


User Abend Codes 3-3

ABEND 3099 LOAD OF XPEDITER FAILED

Module: ADSIM004

Explanation: The load module for XPEDITER could not be found.

User Response: Include the XPEDITER load module library in the STEPLIB concatenation and try again.

ABEND 3100 LOAD OF APPLICATION MODULE FAILED

Module: ADSRA000

Explanation: The application load module could not be found.

User Response: Include the library containing the load module in the XUSERLIB concatenation and try again.

ABEND 3104 INVALID BREAKPOINT INSTRUCTION EXECUTED


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.

ABEND 3398 XPEDITER/TSO ABEND IN ADSRANNNEP N(8) IA N(8) DISP N(6)


Explanation: An ABEND occurred in XPEDITER/TSO. An XPEDITER/TSO internal control stack will follow this message.

User Response: Contact Compuware Technical Support for a circumvention and to open a PTN (Problem Tracking Number) to resolve the problem.

ABEND 3399

Explanation: This ABEND occurs if there is not enough memory available for XPEDITER for DB2 Extension.

User Response: Log off and then log back on with more memory.

ABEND U4000 (1) NON-ZERO RETURN CODE FROM ISPEXEC (2) NON-ZERO RETURN CODE FROM PANEL QUERY (3) INSUFFICIENT MEMORY FOR SVT BUFFER (4) NON-ZERO RETURN CODE FROM CONTROL DISPLAY LINE

Module: ADSRA429, ADSSU082, and ADSRA470

Explanation: Module ADSRA429 issues two messages: message 1 indicates an error in an ISPEXEC call for ISPF services; 2 indicates an error in an ISPF panel request. Module ADSSU082 issues message 3, which indicates that the JOB being run needs more memory and should be run in a larger region. Module ADSRA470 issues message 4, which indicates an error in the use of the ISPF DISPLAY function.



4-1

Chapter 4.
4Miscellaneous Messages and Codes Information Chap 4
XPEDITER/ROS MessagesMessages from the XPEDITER/ROS 2.0 system are no longer supported by XPEDITER/TSO and XPEDITER/IMS effective with XPEDITER/TSO and XPEDITER/IMS Release 6.5.

Condition Codes from Recreation UtilityJobs run while utilizing the XPEDITER/TSO documentation recreation utility may end with certain condition codes. These codes are documented in the Enterprise Common Components Messages and Codes MVS Version manual.


5-1

Chapter 5.
5XPEDITER for DB2 Extension Run-Time Messages Chap 5
SQI435 = 1, COMMAND NOT RECOGNIZED

Explanation: The line command entered is not recognized as a valid command.

User Response: Check for a misspelled line command.

SQI435 = 2, ONLY D, F, and L COMMANDS ARE PERMITTED ON EXCLUDED LINES

Explanation: The line command entered is not permitted on excluded lines.


SQI435 = 3, NUMBER NOT ALLOWED WITH SPECIFIED LINE COMMAND

Explanation: A number is not allowed with the specified line command.

User Response: Remove the number, or enter another line command.

SQI435 = 4, COMMAND NOT ALLOWED ON LINE

Explanation: The line command was entered on a non-Procedure Division line.

User Response: Remove the line command.

SQI435 = 5, COMMAND NOT PERMITTED FOR DISPLAY ONLY LINE

Explanation: A line command was entered on a display-only line.

User Response: Check whether the command is entered for the correct line, or entered for a line that was optimized out.

SQI435 = 6, INVALID SQL STATEMENT FOR EXPLAIN

Explanation: An SQL EXPLAIN command was entered on a line that does not contain a legal SQL statement.

User Response: Check whether the command was entered for the correct line, or is missing an SQL statement terminator, semicolon, or END-EXEC.

SQI479 = 1, BLOCK COMMAND INCOMPLETE

Explanation: A matching block command was not entered.

User Response: Enter a matching block command to complete the block command pair.

SQIC00 = 1, INVALID SET COMMAND

Explanation: The SET processor could not identify the category for the SET command.


SQIC00 = 4, ERROR PROCESSING SET COMMAND

Explanation: The SET command was unable to obtain the information needed to process; i.e., no parsed command block.


SQIC00 = 97, COMMAND BLOCK NOT FOUND

Explanation: The SET command was unable to obtain the parsed command block.


SQIC00 = 98, ENTERING SET FUNCTION

Explanation: The SET command is being invoked.



SQIC00 = 99, EXITING SET FUNCTION

Explanation: The SET command is being terminated.


SQIDCI = 2, MORE THAN 256 LEADING BLANKS ON SQL STATEMENT

Explanation: There are more than 256 blanks preceding the SQL verb.

User Response: Make sure that your SQL verb is entered within the first 256 bytes.

SQIDCI = 3, OPEN FAILED ON SQLIN DATA SET

Explanation: An OPEN for the SQLIN dataset failed.

User Response: Make sure you have allocated the dataset—SQLIN is a sequential dataset with an LRECL of 80.

SQIDCI = 4, INTERNAL ERROR

Explanation: An invalid request was made to SQIDCI. This is an internal error.


SQID00 = 1, KEYWORD CURSOR EXPECTED IN SQL STATEMENT, NONE PROVIDED

Explanation: The keyword CURSOR was expected in the SQL statement, and none was provided.


SQID00 = 2, SELECT PORTION ON DECLARE CURSOR STATEMENT MISSING

User Response: Check for the keyword SELECT.

SQID00 = 3, CURSOR_NAME NOT SPECIFIED

Explanation: The CURSOR_NAME was expected in the SQL statement and none was provided.


SQID00 = 4, NO HOST VARIABLE(S) NOR DESCRIPTOR SPECIFIED

Explanation: Parameter markers were present in the SQL statement.

User Response: These must be resolved by supplying host variables or an SQLDA in the SQL call.

SQID00 = 5, ADDRESS OF THE SQLDA_NAME CANNOT BE LOCATED

Explanation: You have supplied an SQLDA in the OPEN statement but its address could not be located in your program.

User Response: Check for spelling errors.

SQID00 = 6, STATEMENT_NAME NOT SPECIFIED

Explanation: The STATEMENT_NAME was not specified on a PREPARE SQL call.


SQID00 = 7, ADDRESS OF THE SQLSOURCE CANNOT BE LOCATED

Explanation: The address of the SQLSOURCE on a PREPARE call cannot be located.


SQID00 = 8, SQL VERB IS NOT KNOWN TO XPEDITER for DB2 Extension

Explanation: The SQL verb is not known to XPEDITER for DB2 Extension.

User Response: Check for a spelling error.

XPEDITER for DB2 Extension Run-Time Messages 5-3

SQID00 = 9, KEYWORD DESCRIPTOR MISSING

Explanation: The keyword DESCRIPTOR on the SQL call is missing.


SQID00 = 21, ATTEMPTING TO USE MORE THAN 10 CURSORS

Explanation: You are attempting to use more than 10 internally defined SQL cursors.

User Response: You should free up a cursor by closing it.

SQID00 = 30, COMMIT NOT EXECUTED BECAUSE AT LEAST ONE CURSOR OPEN

Explanation: The COMMIT was not executed because at least one dynamic cursor was open. Normally, the COMMIT would close the cursor, and any reference to it from the program would return a user -514 SQLCODE.


SQID00 = 101, SQL STATEMENT TOO LONG. XPEDITER for DB2 Extension ALLOWS UP TO 12,288 BYTES

Explanation: Your SQL statement exceeds the maximum permissible length of 12,288, internally set by XPEDITER for DB2 Extension. XPEDITER for DB2 Extension expands your SQL call by filling in the values of host variables. If the expanded length is greater than 12,288 bytes, you will also get this error.

User Response: Reduce the original length by eliminating unnecessary blanks.

SQID00 = 102, SQL VERB NOT KNOWN TO XPEDITER for DB2 Extension

Explanation: The SQL verb is not known. Leading blanks are allowed, but a blank line without a verb is flagged with this error code.

User Response: Check for a spelling error.

SQID01 = 4, NO “INTO” OR HOST VARIABLE FOUND

Explanation: The SQL statement requires either an INTO clause or at least one host variable. Neither of these was found in the SQL statement.


SQID01 = 5, HOST VARIABLE NOT DEFINED IN PROGRAM

Explanation: A host variable was referenced in the SQL statement. However, its address could not be resolved using the DDIO dataset.


SQID01 = 6, INDICATOR VAR. NOT DEFINED IN PROG.

Explanation: An indicator variable was referenced in the SQL statement. However, its address could not be resolved using the DDIO dataset.


SQID01 = 8, HOST VARIABLE NOT RESOLVED. INVALID DATA TYPE

Explanation: The address of the host variable could not be resolved using the DDIO dataset—invalid data type.

SQID01 = 9, INVALID DBCREG

Explanation: An invalid request was made to ADSQID01. This is an internal error.


SQID02 = 21, REQUEST FUNCTION NOT KNOWN (INTERNAL ERROR)

Explanation: This is an internal error.


SQID02 = 22, DATATYPE IN SQLDA NOT KNOWN




SQID02 = 23, NO STORAGE TO OBTAIN. SQLD PROBABLY SET TO ZERO



SQID20 = 1, SQLDA IS IN ERROR, SQLD=0

Explanation: The SQLDA field has a zero value. This should not occur.


SQID20 = 2, DATATYPE REQUIRES ONE OR MORE INDICATOR VARIABLES

Explanation: One or more columns is defined to contain null values. However, no corresponding indicator variable was included in the SQL statement.


SQIF00 = 1, INVALID PRIMARY COMMAND

Explanation: A primary command of the format =x was entered, but x is not a valid option. Valid options are the characters/digits associated with XPEDITER for DB2 Extension functions on the Primary Menu.


SQIG00 = 1, NO ROWS TO DISPLAY

Explanation: No rows were found to display.


SQIG01 = 1, INVALID COMMAND

Explanation: An invalid command or option was entered.

User Response: Check for a misspelled command and reenter.

SQIG01 = 2, INVALID LINE COMMAND ENTERED

Explanation: The line command entered is not recognized as a valid command.


SQIP00 = 1, PROFILE NOT AVAILABLE

Explanation: The TSQLPROFILES table could not be read during XPEDITER for DB2 Extension INIT time. Either you do not have authority to perform at least a SELECT on a table, or a timeout occurred.

User Response: Try getting to the TSQLPROFILES table through option 0. An SQL return code gives the exact reason for denial of access.

SQIRD0 = 1, INVALID COMMAND


User Response: Check for a misspelled command or option and reenter.

SQIRD0 = 2, SQL ERROR

Explanation: An SQL error occurred.


SQIRD0 = 3, NO MORE ROWS TO FETCH

Explanation: No more rows were found to fetch.


SQIR00 = 1, INVALID COMMAND/OPTION ENTERED


User Response: Check for a misspelled command or option and reenter.

XPEDITER for DB2 Extension Run-Time Messages 5-5

SQIR00 = 2, ERROR IN SELECT + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Select.


SQIR00 = 3, ERROR IN DELETE + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Delete.


SQIR00 = 4, ERROR IN PRINT + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Print.


SQIR00 = 5, ERROR IN BROWSE + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Browse.


SQIR00 = 6, INVALID LINE COMMAND ENTERED

Explanation: An invalid line command was entered.

User Response: Check for the misspelled command and reenter.

SQIR03 = 1, ERROR IN SELECT + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Select.


SQIR03 = 2, ERROR IN DELETE + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Delete.


SQIR03 = 3, ERROR IN PRINT + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Print.


SQIR03 = 4, INVALID LINE COMMAND ENTERED

Explanation: An invalid line command was entered.

User Response: Check for the misspelled command and reenter.


6-1

Chapter 6.
6Unsuccessful SQL Error Codes Chap 6
USQL -007 STATEMENT CONTAINS THE ILLEGAL CHARACTER character

Explanation: The specified character is not a valid character in SQL statements.

User Response: Correct the syntax and resubmit the statement. Refer to the SQL Reference Manual for information about the valid SQL character set.

USQL -010 THE STRING CONSTANT BEGINNING string IS NOT TERMINATED

Explanation: The statement contains a string constant, beginning with string, that is not terminated properly.

User Response: Examine the statement for missing quotation marks or apostrophes in the indicated string constant.

USQL -029 INTO CLAUSE REQUIRED

Explanation: SELECT statements embedded in an application program must have an INTO clause to denote where the results of the SELECT are to be placed. Dynamic SELECT statements do not permit the INTO clause.

User Response: Add the INTO clause to the SELECT statement and recompile the application program again.

USQL -060 INVALID type SPECIFICATION: spec

Explanation: type is either LENGTH or SCALE. spec is the specified length or scale. Length or scale must be specified by an unsigned integer constant and the value must be in the range allowed by the data type.

User Response: Correct the statement. Refer to the SQL Reference Manual for rules regarding length and scale.

USQL -084 UNACCEPTABLE SQL STATEMENT

Explanation: This SQL statement is unacceptable to DB2. One of the following actions has occurred:

– An attempt has been made to PREPARE or EXECUTE IMMEDIATE an SQL statement that cannot be prepared; refer to the proper SQL statement as noted in the SQL Reference Manual.

– The embedded SQL statement is not an SQL statement supported by DB2.

– The statement referenced an undeclared cursor.

– An attempt was made to prepare an ALLOCATE CURSOR statement but the statement identifier is already associated with a declared cursor.

User Response: (1) If the situation involves an SQL statement that cannot be prepared, the problem is in the source of the SQL statement, not the application program. Thus, no action is necessary unless the source of the SQL statement is the application program itself.(2) If the situation involves an SQL statement that is not supported by DB2, remove it from the application program and recompile it again.(3) If the situation involves an invalid PREPARE of an ALLOCATE CURSOR statement, change the application program to use a statement identifier that is not associated with a declared cursor.

USQL -101 THE STATEMENT IS TOO LONG OR TOO COMPLEX

Explanation: The statement cannot be executed because it exceeds the system limits for either length or complexity. Enabling parallelism will increase the complexity of the statement.


User Response: Break the statement up into shorter or less complex SQL statements. If parallelism is enabled, try disabling it by (1) using the DEGREE(1) bind option for static SQL or (2) by setting the CURRENT DEGREE special register to “1” for dynamic SQL.

USQL -102 LITERAL STRING IS TOO LONG. STRING BEGINS string

Explanation: The string constant beginning with string has a length greater that 254 characters or 124 graphic characters. Character strings with lengths greater than 254 and graphic strings with lengths greater than 124 can be specified only through careful assignment from host variables. For SET CURRENT PACKAGESET, up to 18 characters are allowed; for SET CURRENT SQLID, up to 8 characters are allowed; for SET CURRENT DEGREE, up to 3 characters are allowed.Two consecutive string delimiters are used to represent one string delimiter within the character string. These count as two bytes when calculating the lengths of character string constants.

User Response: The requested function is not available interactively. If the error occurred in the context of an SQL statement embedded in an application program, the desired result can be achieved by assigning the long string to a host variable, and substituting that variable for the string literal in the SQL statement.

USQL -103 literal IS AN INVALID NUMERIC LITERAL

Explanation: The indicated “literal” begins with a digit, but is not valid integer, decimal, or float literal.

User Response: Correct the invalid literal.

USQL -104 ILLEGAL SYMBOL “token”. SOME SYMBOLS THAT MIGHT BE LEGAL ARE: token-list

Explanation: A syntax error was detected where the symbol “token” occurs in the SQL statement. The list of symbols that might be legal shows some alternate symbols that could possibly be correct at that point, provided the preceding part of the statement is entirely correct.However, the preceding part of the statement might be correct. For example, if an important keyword is omitted, DB2 detects the error at a later time, and not always immediately after the point where the keyword should appear. The list of alternate symbols is only meant to be used as a suggestion. Some of those symbols are possibly correct for statements sent to other database management systems.

User Response: Correct the statement and execute it again.

USQL -105 INVALID STRING

Explanation: The statement contains an invalid string. It is neither a character string nor a graphic string.

User Response: Specify the correct format of the string. Check for a graphic string, paired delimiters, the character G or the character N, and an even number of bytes within the string.

USQL -107 THE NAME name IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS size

Explanation: The name is too long. The maximum permissible length for names of that type is indicated by size. Names for the following item cannot contain more than 64 characters:

– Version-id

Names for the following items cannot contain more than 18 characters (20 including SQL escape characters, if present):

– SQL Columns– SQL Tables– SQL Views– SQL indexes– SQL aliases– SQL synonyms– Collection-ids– Check constraints

Names for the following item cannot contain more than 16 characters:

– Location-name

Unsuccessful SQL Error Codes 6-3

The following items cannot contain more than 8 characters:

– Table qualifiers– View qualifiers– Library member names specified in an INCLUDE statement– Storage group names– Database names– Table space names– Application plans– Database request modules (DBRMs)– Referential constraint names specified in CREATE or ALTER TABLE statements– Package-id

Host variable names cannot contain more than 64 characters. Volume serial numbers cannot contain more than 6 characters. Labels cannot contain more than 30 characters.

User Response: Choose a shorter name for the object.

USQL -108 THE NAME name IS QUALIFIED INCORRECTLY

Explanation: The name name is improperly qualified. A target name on the RENAME statement may not have a qualifier.

User Response: Remove the qualifier and reissue the statement.

USQL -109 clause CLAUSE IS NOT PERMITTED

Explanation: The indicated clause is not permitted in the context in which it appears in this SQL statement for the following reasons:

– A subselect cannot have an INTO clause.– A CREATE VIEW statement cannot have INTO, ORDER BY, or FOR UPDATE

clauses.– An embedded SELECT statement cannot have ORDER BY or FOR UPDATE clauses.– SELECT statements used in cursor declarations cannot have an INTO clause.– A CREATE TABLESPACE statement cannot specify the LARGE clause without the

NUMPARTS option.– A CREATE TABLESPACE statement cannot specify LOCKPART without the

NUMPARTS option.– An ALTER TABLESPACE statement cannot specify LOCKPART for a

non-partitioned table space.– A table space with LOCKPART YES cannot be altered to LOCKSIZE TABLESPACE.– A table space with LOCKSIZE TABLESPACE cannot be altered to LOCKPART YES.

User Response: Correct the SQL statement.

USQL -110 INVALID HEXADECIMAL LITERAL BEGINNING string

Explanation: The literal beginning with the specified string contains one or more characters that are not valid hexadecimal digits.

User Response: Correct the invalid literal.

USQL -111 A COLUMN FUNCTION DOES NOT INCLUDE A COLUMN NAME

Explanation: The specification of a column function (AVG, MAX, MIN, or SUM) was invalid because such functions must include a column name in the operand.

User Response: A column name must be specified as an operand to the function. Refer to the SQL Reference Manual for further information about the proper usage of column functions.

USQL -112 THE OPERAND OF A COLUMN FUNCTION IS ANOTHER COLUMN FUNCTION

Explanation: The operand of a column function can be either an expression or DISTINCT followed by an expression. The operand cannot be another column function.

User Response: Correct the function specification. Refer to the SQL Reference Manual for further information about the proper usage of column functions.


USQL -113 INVALID CHARACTER FOUND IN string, REASON CODE nnn

Explanation: The string contains an invalid character. It can be an SQL ordinary identifier name, a host variable name, or a Double Byte Character Set (DBCS) comment. For single byte character set SQL ordinary identifiers, names of buffer pools, databases, plans, and storage groups must contain only uppercase alphabetic or national characters and numerics when CHARSET is KATAKANA; the first character must be alphabetic or national. The following reason code applies to DBCS identifiers:

– 000 An invalid character was found in the SBCS identifier.

The following reason codes apply to DBCS identifiers or comments:

– 101 An odd number of bytes exists between the shift-out and the shift-in character.

– 102 Either a shift-in or shift-out character is missing.– 103 DBCS blanks X”4040” are not allowed.– 104 There are no characters between the shift-out and the shift-in characters.– 105 Shift-out cannot be the first byte of the DBCS character between the

shift-out and the shift-in characters.

User Response: Correct the name.

USQL -114 THE LOCATION NAME location DOES NOT MATCH THE CURRENT SERVER

Explanation: A 3-part SQL procedure name was provided for one of the following SQL statements:

ASSOCIATE LOCATORSCALLDESCRIBE PROCEDURE

The first part of the SQL procedure name, designated to specify the location where the stored procedure resides, did not match the value of the SQL CURRENT SERVER special register.

User Response: Take one of the actions itemized below to resolvethe mismatch:

– Change the location qualifier to match the CURRENT SERVER special register.– Issue an SQL CONNECT to the location where the stored procedure resides before

issuing the SQL statement. Ensure that the SQL CALL statement is issued before the ASSOCIATE LOCATORS or DESCRIBE PROCEDURE.

USQL -115 A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR operator IS FOLLOWED BY A PARENTHESIZED LIST OR BY ANY OR ALL WITHOUT A SUBQUERY

Explanation: A simple comparison such as: “>” must not be followed by a list of items. ANY and ALL comparisons must be followed by a subselect, rather that an expression or a list of items.

User Response: Correct the SQL statement. Refer to the SQL Reference Manual for information about the syntax of SQL statements.

USQL -117 THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NUMBER OF OBJECT COLUMNS

Explanation: The number of insert values in the value list of the INSERT statement is not the same as the number of object columns specified.

User Response: Correct the statement to specify one and only one value for each of the specified object columns.

USQL -118 THE OBJECT TABLE OR VIEW OF THE INSERT, DELETE, OR UPDATE STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE

Explanation: The table or view specified as the object of an INSERT, DELETE, or UPDATE statement also appears in the FROM clause of a subselect within the statement. The table or view that is the object of an INSERT, UPDATE, or DELETE cannot also be used to supply the values to be inserted or to qualify the rows to be inserted, updated, or deleted.

User Response: The implied function is not supported by DB2. It may be possible to obtain the desired result by creating a temporary copy of the object table or view, and addressing the


subselect to that copy. Refer to the SQL Reference Manual for additional information regarding the syntax of SQL statements.

USQL -119 A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED IN THE GROUP BY CLAUSE

Explanation: A column identified in a HAVING clause (possibly within a scalar function) does not appear in the GROUP BY clause. Columns specified in a HAVING clause must appear within column functions or also be specified in the GROUP BY clause.

User Response: The implied function is not supported by DB2. Refer to the SQL Reference Manual for information regarding the proper usage of HAVING and GROUP BY clauses.

USQL -120 A WHERE CLAUSE OR SET CLAUSE INCLUDES A COLUMN FUNCTION

Explanation: A column function is not permitted in a SET clause. A column function is allowed in a WHERE clause only if the WHERE clause appears within a subquery of a HAVING clause.

User Response: The implied function is not supported by DB2. Refer to the SQL Reference Manual for information regarding restrictions on operands that can be specified within WHERE and SET clauses.

USQL -121 THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE STATEMENT

Explanation: The same column name is specified more than once, either in the list of object columns of an INSERT statement, or the SET clause of an UPDATE statement.

User Response: Correct the syntax of the statement so that each column name is specified only once.

USQL -122 A SELECT STATEMENT WITH NO GROUP BY CLAUSE CONTAINS A COLUMN NAME AND A COLUMN FUNCTION IN THE SELECT CLAUSE OR A COLUMN NAME IS CONTAINED IN THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE.

Explanation: The SELECT statement contains one of the following errors:

– The statement contains a column name and a column function in the SELECT clause, but no GROUP BY clause.

– A column name is contained in the SELECT clause (possibly within a scalar function) but not in the GROUP BY clause.

Note: A HAVING clause specified without a GROUP BY clause implies a GROUP BY with no columns. Thus, no column names are allowed in the SELECT clause.

User Response: Refer to the SQL Reference Manual for information about the use of GROUP BY clauses in SQL statements.

USQL -125 AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT

Explanation: The ORDER BY clause in the statement contains a column number that is either less than one, or greater than the number of columns of the result table (the number of items in the SELECT clause).

User Response: Correct the syntax of the ORDER BY clause so that each column identifier properly denotes a column of the result table.

USQL -126 THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY CLAUSE

Explanation: The SELECT statement in the declaration for a cursor contains both an UPDATE clause and an ORDER BY clause. An ORDER by clause cannot be specified in the declaration for a cursor that is to be used for update.

User Response: The implied function is not supported by DB2. A cursor that is to be used for update cannot be defined to fetch the rows of the object table in a specific order. Refer to the SQL Reference Manual for information about restrictions on the declarations for cursors to be used for update.


USQL -127 DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT

Explanation: The DISTINCT statement qualifier can be used only once in a SELECT statement or a subselect.

User Response: The implied function is not supported by DB2. Refer to the SQL Reference Manual for information about restrictions on the use of the DISTINCT qualifier.

USQL -128 INVALID USE OF NULL IN A PREDICATE

Explanation: The use of NULL in the search condition does not conform to the rules of SQL syntax.

User Response: The implied function is not supported by DB2. Refer to the SQL Reference Manual for information about the proper use of the NULL operand.

USQL -129 THE STATEMENT CONTAINS TOO MANY TABLE NAMES

Explanation: A subselect (including all subqueries) can have a maximum of 15 references to table names.

User Response: Break the SQL statement into two or more simpler statements with 15 or fewer table references in each. The count will include the number of base table occurrences from each table or view on the FROM list. Refer to the SQL Reference Manual for the definition of a subselect.

USQL -130 THE ESCAPE CLAUSE CONSISTS OF MORE THAN ONE CHARACTER, OR THE STRING PATTERN CONTAINS AN INVALID OCCURRENCE OF THE ESCAPE CHARACTER

Explanation: The ESCAPE character must be a single character, either SBCS or DBCS as appropriate. For column-name LIKE pattern, the ESCAPE character can only appear in the character string if it is followed by itself, %, or _ (underscore). The Escape Clause cannot be specified if the column name at the left of the LIKE or NOT LIKE has the mixed subtype.

User Response: Correct the string pattern or choose a different ESCAPE character and change the pattern accordingly. Eliminate the use of the Escape Clause on the LIKE or NOT LIKE predicate where the column name to the left has the MIXED subtype.

USQL -131 STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES

Explanation: If the column name at the left of LIKE or NOT LIKE is of type character, the expression at the right and the ESCAPE character must be of type character. If the column name is of type graphic, the expression at the right and the ESCAPE character must be of type graphic.

User Response: Check the data type of every operand.

USQL -132 A LIKE PREDICATE IS INVALID BECAUSE THE SECOND OPERAND IS NOT A STRING

Explanation: The token following LIKE must be a special register, a string constant, or a host variable with a string value.

User Response: The implied function is not supported by DB2. Refer to the SQL Reference Manual for information about the proper syntax for LIKE and NOT LIKE predicates.

USQL -133 A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID BECAUSE ALL COLUMN REFERENCES IN ITS ARGUMENT ARE NOT CORRELATED TO THE GROUP BY RESULT THAT THE HAVING CLAUSE IS APPLIED TO

Explanation: If a column function has a correlated column reference, it must be correlated from within a HAVING clause to the GROUP BY result that the HAVING clause is applied to. All column references in the argument must satisfy this condition.

User Response: Refer to the SQL Reference Manual for information about restrictions on the syntax of the HAVING clause.

USQL -134 IMPROPER USE OF LONG STRING COLUMN column-name OR A HOST VARIABLE OF MAXIMUM LENGTH GREATER THAN 254

Explanation: A long string was referenced in a context in which long strings are not allowed. For an exhaustive list of such contexts, refer to Chapter 3 of the SQL Reference Manual.

User Response: The requested operation on a long string value is not supported by DB2. Refer to the SQL Reference Manual for information about restrictions on the specification and manipulation of long string values.


USQL -136 SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES

Explanation: A sort key is derived from the list of columns specified following a DISTINCT qualifier, or in an ORDER BY or GROUP BY clause. If both a DISTINCT qualifier and an ORDER BY or GROUP BY clause are present, the sort key is derived from the combination of both lists of columns.The internal length of the sort key cannot exceed 4000 bytes. In attempting to process the SQL statement, the internal length of the sort key derived from the DISTINCT and/or ORDER BY or GROUP BY specifications was found to exceed that 4000-byte maximum.

User Response: The statement must be modified so that the internal length of the sort key will not exceed 4000 bytes. In general, this means that one or more column names must be deleted from the ORDER BY or GROUP BY clause, or the list following the DISTINCT qualifier.

USQL -137 RESULT OF CONCATENATION IS TOO LONG

Explanation: The length of the result of a concatenation exceeds 32,764 (if character operands) or 16,382 (if graphic operands).

User Response: Ensure that the total of the lengths of the concatenated operands is less than or equal to 32,764 (for character operands) or 16,382 (for graphic operands).

USQL -138 THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS OUT OF RANGE

Explanation: One of the following conditions exists:

– The second argument of the SUBSTR function is less than 1 or greater than M.– The third argument of the SUBSTR function is an integer constant 0 or an

expression whose value is less than 0 or greater than M-N+1.

M is the length of the first argument, provided it is of fixed-length, or M is the maximum length of the first argument, provided it is of varying length. N is the value of the second argument.

User Response: Ensure that the second and third arguments of the SUBSTR function have legal values according to the above rules.

USQL -144 INVALID SECTION NUMBER number

Explanation: One of the following applies:

a. The user attempted to execute an invalid section.

b. The release of DB2 does not support the SQL statement.

c. The section number in the call parameter list describes one of the items listed below:

• Negative• An invalid duplicate• Greater than the maximum section number of the DBRM or package.

User Response: For case #1: If you are executing a package that was bound with SQLERROR(CONTINUE), determine whether the statement in question was bound as a valid section. You can use the following statements to query the DB2 catalog:

SELECT SQL ERROR FROM SYSIBM.SYSPACKAGE WHERE COLLID = collection-id AND

NAME = package-id ANDVERSION = version-name;

If that query returns “C”, the package was bound with SQLERROR(CONTINUE).

SELECT STMTNO, TEXT FROM SYSIBM.SYSPACKSTMT WHERE COLLID = collection-id AND

NAME = package-id ANDVERSION = version-name ANDSECTNO = number ANDBINDERROR = "Y";


If that query returns any rows, the section is invalid. Refer to the error messages issued during the bind to determine the cause. Correct any errors and bind the package again using the REPLACE option.For case #2: If the DB2 system has fallen back to a previous release, determine whether there are any SQL statements with a section number of zero that are not supported specifically by that release. You can use the following statements to query the DB2 catalog.When executing from a DBRM, use:

SELECT *FROM SYSIBM.SYSSTMTWHERE SECTNO = 0ORDER BY NAME,PLNAME,STMTNO,SEQNO;

When executing from a package, use:

SELECT *FROM SYSIBM.SYSPACKSTMTWHERE SECTNO = 0ORDER BY COLLID,NAME,VERSION,STMTNO,SEQNO;

For case #3: Examine the application to determine whether the call parameter list was changed in some way. In general, you should not attempt to change the output of the precompiler.

USQL -148 THE SOURCE TABLE source-name CANNOT BE RENAMED BECAUSE IT IS A VIEW OR AN ACTIVE RLST TABLE OR HAS A SYNONYM DEFINED ON IT

Explanation: The RENAME statement cannot be used to rename a view, an active RLST table, or a table for which a synonym is defined.

User Response: Change the source name to the name of an object that canbe renamed and reissue the statement.

USQL -150 THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED

Explanation: The view named in the INSERT, UPDATE, or DELETE statement is defined in such a way that the requested insert, update, or delete operation cannot be performed upon it.Inserts into a view are prohibited if:

– The view definition contains a join, a GROUP BY, or a HAVING clause.– The SELECT clause in the view definition contains the DISTINCT qualifier, an

arithmetic expression, a string expression, a built-in function, or a constant.– Two or more columns of the view are derived from the same column.– A base table of the view contains a column that does not have a default value and

is not included in the view.

Updates to a view are prohibited if:

– The view definition contains a join, a GROUP BY, or a HAVING clause.– The SELECT clause in the view definition contains the DISTINCT qualifier or a

function.

In addition, a given column in a view cannot be updated (i.e., the values in that column cannot be updated) if the column is derived from an arithmetic expression, a constant, a column that is part of the key of a partitioned index, or a column of a catalog table that cannot be updated.Deletes against a view are prohibited if:

– The view definition contains a join, a GROUP BY, or a HAVING clause.– The SELECT clause in the view definition contains the DISTINCT qualifier or a

built-in function.

User Response: The requested function cannot be performed on the view. Refer to Chapter 6 of the SQL Reference Manual for further information regarding inserting, deleting, and updating views.


USQL -151 THE UPDATE STATEMENT IS INVALID BECAUSE THE CATALOG DESCRIPTION OF COLUMN column-name INDICATES THAT IT CANNOT BE UPDATED

Explanation: The specified column cannot be updated for one of the following reasons:

– The object table is partitioned (i.e., resides in a partitioned table space) and the column is included in the partitioning key.

– The object table is a view and the specified column is defined (in the definition of the view) in such a way that it cannot be updated.

– The object table is a catalog table with no columns that can be updated.

The values for columns occurring in the partitioning key of a partitioned table cannot be updated.Individual columns in a view cannot be updated for one of the following reasons:

– The column is derived from an SQL function, an arithmetic expression, or a constant.

– The column is defined for a column that is in the partitioning key of a partitioned table.

– The column is defined for a column of an underlying view that cannot be updated.

User Response: The requested function is not supported by DB2. Refer to the description of the UPDATE statement in Chapter 6 of the SQL Reference Manual for information about restrictions on the ability to update columns in partitioned tables and views.

USQL -152 THE DROP clause CLAUSE IN THE ALTER STATEMENT IS INVALID BECAUSE constraint-name IS A constraint-type

Explanation: Either the DROP FOREIGN KEY clause of an ALTER TABLE statement tried to drop a check constraint, or the DROP CHECK clause of an ALTER TABLE statement tried to drop a referential constraint. The clause is either CHECK or FOREIGN KEY. The constraint-type is either REFERENTIAL CONSTRAINT or CHECK CONSTRAINT.

User Response: Drop the existing object with the correct DROP clause of the ALTER TABLE statement.

USQL -153 THE CREATE VIEW STATEMENT DOES NOT INCLUDE A REQUIRED COLUMN LIST

Explanation: You must specify a list of column names if the result table of the subselect has duplicate column names or an unnamed column (a column derived from a constant, function, or expression).

User Response: Correct the statement by providing a list of names for the columns of the view. Refer to Chapter 6 of the SQL Reference Manual for information about the syntax of the CREATE VIEW statement.

USQL -154 THE CREATE VIEW FAILED BECAUSE THE VIEW DEFINITION CONTAINS A UNION, A UNION ALL, OR A REMOTE OBJECT

Explanation: The view defined in the CREATE VIEW statement contains a UNION, a UNION ALL, or a remote object. DB2 cannot create views containing unions or a remote object.

User Response: Refer to Chapter 6 of the SQL Reference Manual for information about restrictions on the definitions for views.

USQL -156 THE STATEMENT DOES NOT IDENTIFY A TABLE

Explanation: The statements ALTER TABLE, DROP TABLE, LOCK TABLE, and CREATE INDEX apply only to tables. Indexes can be defined only on tables.

User Response: Verify that the proper name was specified in the statement.

USQL -157 ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY CLAUSE. object-name IS NOT THE NAME OF A TABLE.

Explanation: The indicated object was identified in a FOREIGN KEY clause or a CREATE or ALTER TABLE statement. A FOREIGN KEY clause must identify a table.

User Response: Correct the statement to specify a table name in the foreign key clause.


USQL -158 THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE SAME AS THE NUMBER OF COLUMNS SPECIFIED BY THE SELECT CLAUSE

Explanation: The number of column names specified for a view in a CREATE VIEW statement must equal the number of elements (column names, SQL functions, expressions, etc.) specified in the following AS SELECT clause.

User Response: Correct the syntax of the statement to specify a column name for each column in the view to be created. Refer to Chapter 6 of the SQL Reference Manual for information about the syntax of the CREATE VIEW statement.

USQL -159 DROP OR COMMENT ON token IDENTIFIES A(N) token RATHER THAN A(N) token

Explanation: The DROP VIEW statement can have only a view as its object. The DROP ALIAS or COMMENT ON ALIAS statement can have only an alias as its object. You must use the DROP TABLE statement to drop a table that is neither a view nor an alias. You must use the COMMENT ON TABLE statement to comment on a table or view.

User Response: Correct the DROP VIEW, DROP ALIAS, or COMMENT ON ALIAS statement so that the view name or the alias name is specified correctly (with the proper qualifier). If you intended to drop or comment on the specified table, use the DROP TABLE or COMMENT ON TABLE statement.

USQL -160 THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW

Explanation: The WITH CHECK OPTION does not apply to a view definition under either of the following circumstances:

– The view is read-only (for example, the view definition includes DISTINCT GROUP BY, or JOIN).

– The view definition includes a subquery.

User Response: Refer to Chapter 6 of the SQL Reference Manual for rules regarding use of the WITH CHECK OPTION in view definitions.

USQL -161 THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW DOES NOT SATISFY THE VIEW DEFINITION

Explanation: The WITH CHECK OPTION applies to the view that is the object of the INSERT or UPDATE statement. Consequently, all attempts to insert or update rows in that view are checked to ensure that all results will conform to the view definition.

User Response: Examine the view definition to determine why the requested INSERT or UPDATE was rejected. Note that this may be a data-dependent condition.

USQL -164 auth-id1 DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH QUALIFICATION authorization ID

Explanation: The authorization ID auth-id does not have its own authorization ID. Specifically, the attempt to create a view with a qualifier authorization-ID is rejected.

User Response: Do not attempt to create views with other than your own ID as a qualifier. Only an authorization ID that holds SYSADM authority can create views for other authorization IDs.

USQL -170 THE NUMBER OF ARGUMENTS SPECIFIED FOR function-name IS INVALID

Explanation: An SQL statement includes the scalar function function-name with either too many arguments or too few arguments.

User Response: Correct the statement. Refer to Chapter 4 of the SQL Reference Manual for information about the number of arguments required by the scalar function function-name.

USQL -171 THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT nn OF function-name IS INVALID

Explanation: Either the data type, the length, or the value of argument nn of scalar function function-name is incorrect.

User Response: Correct the statement. Refer to Chapter 4 of the SQL Reference Manual regarding rules for each argument of the scalar function function-name.


USQL -173 UR IS SPECIFIED ON THE WITH CLAUSE BUT THE CURSOR IS NOT READ-ONLY

Explanation: The cursor is not a read-only cursor. WITH UR can be specified only if DB2 can determine that the cursor is read-only.

User Response: If the cursor is intended to be read-only but is ambiguous, add the FOR FETCH ONLY clause. If the cursor is updateable, change the isolation level specified on the WITH clause.

USQL -180 THE DATE, TIME, OR TIMESTAMP VALUE value IS INVALID

Explanation: The length or string representation of a DATE, TIME, or TIMESTAMP value does not conform to any valid format.The value can contain one of the following:

– For a host variable, the position number of the input host variable. If the position number cannot be determined, a blank is displayed.

– For a character string constant, the character string constant. The maximum length that is displayed is the length of SQLERRM.

– For a character column, the column name. If the column is a VIEW column and it has a corresponding base column, the VIEW column name is displayed. If the column is a VIEW column but it does not have a corresponding base column, a string of *N is displayed.

Otherwise, value is a string of *N.

User Response: Correct the program to ensure the specified value conforms to the syntax of DATE, TIME, and TIMESTAMP. Refer to Chapter 3 of the SQL Reference Manual for a list of valid DATE and TIME formats.

USQL -181 THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME VALUE

Explanation: The string representation of a datetime is not in the acceptable range or is not in the correct format. The proper ranges for datetime values are as follows:

DATETIME NUMERIC RANGEYears 0001 to 9999Months 1 to 12Days April, June, 1 to 30

September, November 1 to 30(months 4,6,9,11) 1 to 30February (month 2) 1 to 28

(Leap Yearis 1 to 29)

January, March, 1 to 31May, July, August 1 to 31October, December 1 to 31(months 1,3,5,7, 1 to 318,10,12) 1 to 31

Hours 0 to 24(If the houris 24, otherparts of timevalues arezeroes. Ifthe hour isUSA, maximumhour is 12.)

Minutes 0 to 59Seconds 0 to 59Microseconds 0 to 999999

User Response: Check whether the value is within the valid range and is in the proper format. Refer to Chapter 3 of the SQL Reference Manual for information on string data formats.

USQL -182 AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IS INVALID

Explanation: The specified arithmetic expression contains an improperly used datetime value or labeled duration.


User Response: Correct the indicated arithmetic expression.

USQL -183 AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A RESULT THAT IS NOT WITHIN THE VALID RANGE OF DATES

Explanation: The result of an arithmetic operation is a date or timestamp that is not within the valid range of dates which are between 0001-01-01 and 9999-12-31.

User Response: Examine the SQL statement to see if the cause of the problem can be determined. The problem may be data-dependent, in which case it will be necessary to examine the data that was processed at the time the error occurred.

USQL -184 AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER MARKER

Explanation: The specified arithmetic expression contains a parameter marker improperly used with a datetime value.

User Response: Correct the indicated arithmetic expression.

USQL -185 THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME AND NO LOCAL EXIT HAS BEEN INSTALLED

Explanation: The local format option has been used with a datetime value and no datetime exit has been installed. This may occur if the LOCAL DATE LENGTH or LOCAL TIME LENGTH on the Installation Application Programming Defaults Panel indicated that an exit for datetime was supplied, but in fact, the exit supplied by DB2 was not replaced. This may also occur if the datetime exit was replaced and the corresponding LOCAL DATE LENGTH or LOCAL TIME LENGTH on the Installation Application Programming Defaults Panel was not set to a non-zero value.

User Response: Contact the system programmer regarding installation of the date or time exit.

USQL -186 THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN INCREASED AND THE EXECUTING PROGRAM RELIES ON THE OLD LENGTH

Explanation: The local format option has been used with a datetime value and DB2 has discovered that the datetime exit routine has been changed to produce a longer local format.

User Response: If the statement receiving this error is embedded in the application program, a REBIND command must then be issued for the application plan. If the statement was dynamic SQL, the statement can then be re-entered.

USQL -187 A REFERENCE TO A CURRENT DATE/TIME SPECIAL REGISTER IS INVALID BECAUSE THE MVS TOD CLOCK IS BAD OR THE MVS PARMTZ IS OUT OF RANGE

Explanation: DB2 has encountered an invalid time-of-day (TOD) clock. The user referenced one of the special registers: (1) CURRENT DATE, (2) CURRENT TIME, (3) CURRENT TIMESTAMP, or (4) CURRENT TIMEZONE. If the user referenced CURRENT TIMEZONE, the MVS parameter PARMTZ was out of range.

User Response: For CURRENT TIMEZONE, check that the MVS parameter PARMTZ is between -24 and +24 hours. For the other CURRENT special registers, check that the MVS TOD clock has been set correctly.

USQL -188 THE STRING REPRESENTATION OF A NAME IS INVALID

Explanation: The host variable referenced in the DESCRIBE statement does not contain a valid string representation of a name. One of the following error conditions has occurred:

– The first byte of the variable is a period or a blank.– The number of identifiers is greater than 3.– An identifier is too long.– A period not contained in a delimited identifier is followed by a period or a

blank.– A delimited identifier is followed by a character other than a period or a blank.– A delimited identifier is not terminated by a quotation mark.

User Response: Correct the value of the host variable so that it is a valid string representation of a name.


USQL -189 CCSID ccsid IS UNKNOWN OR INVALID FOR THE DATA TYPE OR SUBTYPE

Explanation: To determine the subtype of an input host variable or result column, the SYSSTRINGS catalog table was accessed with the specified CCSID and:

– The CCSID is not a value of either INCCSID or OUTCCSID,or

– The TRANSTYPE column classifies the CCSID as GRAPHIC rather than CHARACTER.

This error can occur when SYSSTRINGS is accessed with a pair of CCSIDs to determine if a translation is defined for the pair. In this case, the error is the inconsistency between the data type of a string and the TRANSTYPE classification of its CCSID (one is GRAPHIC and the other is CHARACTER).

This error can also occur when a CCSID specified in DECP does not exist as a value in the INCCSID or OUTCCSID columns of SYSSTRINGS.

User Response: Ensure that the CCSID is valid and consistent with the data type of the string. If a valid CCSID is not listed in a built-in row of SYSSTRINGS, it can be defined by inserting a user-provided row. If a valid CCSID is misclassified in a user-provided row, that row can be updated to correct the mistake. Refer to the appendices of your SQL Installation Guide for more information on CCSIDs and to the SQL Reference Manual for more information regarding the SYSSTRINGS catalog table.

USQL -191 A STRING CANNOT BE USED BECAUSE IT IS INVALID MIXED DATA

Explanation: The operation required the translation of a mixed data character string to a different coded character set. The string could not be translated because it does not conform to the rules for well-formed mixed data. For example, the string does contains EBCDIC shift codes that are not properly paired.

User Response: If the string contains the intended information, the description of the column or host variable should be changed from MIXED DATA to BIT or SBCS DATA. If the description of the column or host variable is correct, the string is the problem and it must be changed to conform to the rules for the well-formed mixed data. For additional information regarding the well-formed MIXED DATA, refer to Chapter 3 of the SQL Reference Manual.

USQL -197 QUALIFIED COLUMN NAMES IN ORDER BY CLAUSE NOT PERMITTED WHEN UNION OR UNION ALL IS SPECIFIED

Explanation: A SELECT statement that specified both the union of two or more tables and the ORDER BY clause cannot use qualified column names in the ORDER BY clause.

User Response: The statement is not executed.

USQL -198 THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANK OR EMPTY

Explanation: The operand (host variable or literal string) that was the object of the PREPARE or EXECUTE IMMEDIATE statement either contained all blanks or was an empty string. A DBRM built in Version 2, Release 3 cannot be used on a Version 2, Release 2 if the distributive functions were used. If this error appears on Version 2, Release 2 and the DBRM was built on Version 2, Release 3, the program needs to be precompiled again to correct the problem.

User Response: Correct the logic of the application program to ensure that a valid SQL statement is provided in the operand of the PREPARE or EXECUTE IMMEDIATE statement before that statement is executed.

USQL -199 ILLEGAL USE OF KEYWORD keyword. TOKEN token-list WAS EXPECTED

Explanation: A syntax error was detected in the statement at the point where the keyword keyword appears. As an aid to the programmer, a partial list of valid tokens is provided in SQLERRM as token-list. Only those tokens that will fit are listed. Some tokens in the list might not be valid in statements to be executed by DB2; those tokens are valid for sending to other database management systems.

User Response: Examine the statement in the area of the indicated keyword. A colon or an SQL delimited might be missing.


USQL -203 A REFERENCE TO COLUMN column-name is AMBIGUOUS

Explanation: An unqualified column name is ambiguous if more than one table or view identified in the FROM clause has a column with that name, or if more than one column of a nested table expression has that name.A qualified column name is ambiguous only if the qualifier is the correlation name for a nested table expression and the column name is not unique.

User Response: If the problem is caused by a non-unique column name in a nested table expression, you must change the nested table expression so that the column name is unique. If the problem is caused by the use of an unqualified name, qualify it with a table, view, or correlation name.

USQL -204 name IS AN UNDEFINED NAME

Explanation: The object identified by name is not defined in the DB2 subsystem. This SQLCODE can be generated for any type of DB2 object.

User Response: Verify that the object name was correctly specified in the SQL statement, including any required qualifiers. If it is correct, ensure that the object exists in the system before resubmitting the statement.If the specified object is a stored procedure, add a row to the SYSIBM.SYSPROCEDURES catalog table to define the stored procedure. Issue the -START PROCEDURE command to activate the new definition.

USQL -205 column-name IS NOT A COLUMN OF TABLE table-name

Explanation: No column with the specified column-name occurs in the table or view table-name.

User Response: Verify that the column and table names are specified correctly (including any required qualifiers) in the SQL statement.

USQL -206 column-name IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE

Explanation: This return code is utilized to report one of the following errors:

– In the case of an INSERT or UPDATE statement, the specified column is not a column of the table or view that was specified as the object of the insert or update.

– In the case of a SELECT or DELETE statement, the specified column is not a column of any of the tables or views identified in a FROM clause in the statement.

– There is a correlated reference in GROUP BY.– There is an unresolved qualified reference in HAVING.

User Response: Verify that the column and table names are specified correctly in the SQL statement. In the case of a SELECT statement, check to be sure that all of the required tables were named in the FROM clause.

USQL -208 THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS NOT PART OF THE RESULT TABLE

Explanation: The statement is invalid because a column (name) specified in the ORDER BY list does not appear in the result table (that is, it is not specified by the SELECT-list). Only columns that are to appear in the result table can be used in ordering that result.

User Response: Correct the syntax of the statement, either by adding the specified column to the result table, or deleting it from the ORDER BY clause. Refer to Chapter 5 of the SQL Reference Manual for information regarding restrictions on the use of the ORDER BY clause to order the result of an SQL SELECT.

USQL -219 THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST

Explanation: The EXPLAIN statement assumes the existence of the explanation table and it is not defined in the DB2 subsystem as a base table. Refer to Chapter 6 of the SQL Reference Manual for more information.

User Response: Determine whether the required explanation table does exist. If not, create the required table.


USQL -220 THE COLUMN column-name IN EXPLANATION TABLE table-name IS NOT DEFINED PROPELY

Explanation: An error occurred during the insertion of a row into the explanation table. The table is improperly defined for the following reasons:

– A column is missing.– Columns are defined in the wrong order.– The table contains an extra column.– A column description is invalid because of its name, data type, length, or null

attributes.

User Response: Correct the definition of the required explanation table. Refer to Chapter 6 of the SQL Reference Manual for information on defining an explanation table.

USQL -221 “SET OF OPTIONAL COLUMNS” IN EXPLANATION TABLE table-name IS INCOMPLETE. OPTIONAL COLUMN column-name IS MISSING.

Explanation: The EXPLAIN statement assumes the required explanation table is defined properly. The optional column indicated is not defined in the indicated explanation table. PLAN-TABLE can have none or all of the Version 2 Release 2 optional columns (PREFETCH, COLUMN-FN-EVAL, or MIXOPSEQ. If the Version 2 Release 2 optional columns are present, it can also have all or none of the optional Version 2 Release 2 columns (VERSION,COLLID).

User Response: Correct the definition of the required explanation table to include all five optional columns, just the Version 2 Release 2 optional columns, or no optional columns whatsoever. Refer to Chapter 6 of the SQL Reference Manual for information on defining an explanation table.

USQL -240 THE PART CLAUSE OF A LOCK TABLE STATEMENT IS INVALID

Explanation: The LOCK TABLE statement has become invalid for one of the following reasons:

– The table space in which the table resides is not partitioned or does not have the LOCKPART YES attribute, and the PART clause is specified.

– An integer specified in the PART clause does not identify a partition of the table space.

User Response: Determine whether the specified table resides in a partitioned table space defined with LOCKPART YES.

– If it is partitioned and defined with LOCKPART YES, specify a PART clause that identifies the partition you want to lock.

– If it is partitioned but does not have the LOCKPART YES attribute and you want to lock a single partition, use ALTER TABLESPACE to change the LOCKPART attribute to YES.

– If it is not partitioned, do not specify the PART clause.

USQL -250 THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE-PART OBJECT NAME

Explanation: A three-part object name (table, view, or alias) cannot be used until the local location name is defined.

User Response: Define the local location name and then retry the function.

USQL -251 TOKEN name IS NOT VALID

Explanation: A location name cannot contain alphabetic characters. (The standard alphabetic extenders in the United States are #, @, and $.)

User Response: Correct the location name.

USQL -300 THE STRING CONTAINED IN HOST VARIABLE OR PARAMETER position-number IS NOT NUL-TERMINATED

Explanation: A host variable or parameter is invalid. Its entry in the SQLDA is indicated by position-number. The host variable or parameter is a C string variable that is one of the following:


– Used as an input parameter to a stored procedure.– Returned as an output parameter from a stored procedure.– Referenced as an input variable in an embedded SQL statement.– Used to provide a value for a parameter marker of a dynamic SQL statement.

If the data type of the variable is character string, it is invalid because it does not include X”00”. If the data type of the variable is graphic string, it is invalid because it does not include X”0000”.

User Response: Append a NUL-terminator to the end of the string.

USQL -301 THE VALUE OF INPUT HOST VARIABLE OR PARAMETER NUMBER position-number CANNOT BE USED AS SPECIFIED BECAUSE OF ITS DATA TYPE

Explanation: DB2 received data that could not be used as specified in the statement because its data type is incompatible with the requested function.The position-number identifies either the host variable (if the message is issued as a result of an INSERT, UPDATE, DELETE, or SELECT statement), or the parameter number (if the message is issued as the result of a CALL statement).

User Response: Correct the application program or stored procedure. Ensure that the data type of the indicated input host variable or parameter in the statement is compatible with the way it is used.

USQL -302 THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER position-number IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE

Explanation: DB2 received data that was invalid or too large to fit in the corresponding column of the table or the corresponding target value. The position-number identifies either the host variable number (provided the message is issued as a result of an INSERT, UPDATE, DELETE, or SELECT statement), or the parameter number (if the message is issued as the result of a CALL statement).One of the following occurred:

– The column is defined as a string and the host variable or parameter contains a string that is too long for the column.

– The column is defined as numeric and the host variable or parameter contains a numeric value too large for the definition of the column.

– The host variable is defined as decimal, but contains invalid decimal data.– The target value is a string constant and the host variable or parameter contains

a string that is too large for the target value.– The target value is a numeric constant and the host variable or parameter

contains a numeric value that is too large for the target value.

User Response: Correct the application program or stored procedure. Check the column type and length of the value or the data type and contents of the input host variable or parameter position-number. Ensure that the value of the host variable or parameter will fit in the column or contains valid decimal data. Valid decimal data is a System/370 packed decimal number.

USQL -303 A VALUE CANNOT BE ASSIGNED TO AN OUTPUT HOST VARIABLE NUMBER position-number BECAUSE THE DATA TYPES ARE NOT COMPARABLE.

Explanation: A CALL, FETCH, or SELECT into the output host variable, whose entry in the output SQLDA is indicated by position-number, could not be performed. The data type of the variable was not compatible with the data type of the corresponding SELECT or CALL list element. The output host variable and the corresponding SELECT or CALL list element must be in one of the following categories:

– Both values must be numbers.– Both values must be character strings.– Both values must be graphic strings.

In addition, for both datetime and timestamp values, the host variable must be a character string variable with a correct length.

User Response: Verify that the table definitions are current and that the host variable has the correct data type.


USQL -304 A VALUE WITH DATA TYPE data-type1 CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST VARIABLE IN POSITION position-number WITH DATA TYPE data-type2

Explanation: A CALL, FETCH, or SELECT into a host variable list or structure in position number position-number failed because the host variable with data type data-type2 was not large enough to hold the retrieved value with data type data-type1.

User Response: Verify that the table definitions are current. Verify that the host variable has the correct data type. Refer to the explanation for SQL CODE SQL0405 for ranges of SQL data types.

USQL -305 THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER position-number BECAUSE NO INDICATOR VARIABLE IS SPECIFIED

Explanation: A FETCH or embedded SELECT operation resulted in the retrieval of a null value to be inserted into the output host variable, designated by an entry number position-number of the output SQLDA, for which no indicator variable was provided. An indicator variable must be supplied if a column returns a null value.

User Response: Examine the definition of the table that is the object of the FETCH or SELECT, and correct the application program to then provide indicator variables for all host variables into which null values can be retrieved. This includes host variables for columns which can contain null values and host variables which receive the results of column functions whose result table could be empty.

USQL -309 A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL VALUE

Explanation: The statement could not be processed because a host variable appearing in a predicate such as:column-name = host variablehad the NULL value. Such a predicate is not permitted when the host variable contains the NULL value even though the object column might contain nulls.

User Response: Rebind the plan or package containing the statement. The condition described is not an error in DB2 Version 2 Release 3 and later releases.

USQL -310 DECIMAL HOST VARIABLE OR PARAMETER number CONTAINS NON-DECIMAL DATA

Explanation: DB2 received non-decimal data from either an application (in the form of a host variable) or a stored procedure (in the form of a parameter that was passed to or from a stored procedure). The following sentence is the definition of number:

Identifies either the host variable number (if the message is issuedas a result of an INSERT, UPDATE, DELETE, or SELECT statement), orthe parameter number (provided the message is issued as the result ofa CALL statement).

User Response: Correct the application program or stored procedure. Ensure that all decimal variables or parameters contain valid System/370 packed decimal numbers.

USQL -311 THE LENGTH OF THE INPUT HOST VARIABLE NUMBER position-number IS NEGATIVE OR GREATER THAN THE MAXIMUM

Explanation: When evaluated, the length specification for input host string variable, whose entry in the SQLDA is indicated by position-number, was negative or greater than the maximum.

User Response: Correct the program to ensure that the lengths of all host string variables are not negative or that they are not greater than the maximum allowed length.

USQL -312 UNDEFINED OR UNUSABLE HOST VARIABLE variable-name

Explanation: The host variable variable-name appears in the SQL statement, but:

– The SQL statement is a prepared statement,or

– The attributes of the variable are inconsistent with its usage in the static SQL statement,or

– The variable is not declared in the application program.


User Response: Verify that the following items have been completed:

– The variable name is spelled properly in the SQL statement.– The variable is allowed in the SQL statement.– The application program contains a declaration for that variable.– The attributes of the variable are compatible with its use in the statement.

USQL -313 THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETER MARKERS

Explanation: The number of host variables specified in the EXECUTE or OPEN statement is not the same as the number of parameter markers (question marks) appearing in the prepared SQL statement.

User Response: Correct the application program so that the number of host variables specified in the EXECUTE or OPEN statement is the same as the number of parameter markers appearing in the prepared SQL statement.

USQL -314 THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE REFERENCE

Explanation: A host variable used in the statement has been defined more than once in this application program causing confusion as to which host variable definition should be used.

User Response: Make the host variable unique or use qualifications to indicate which host variable definition is to be used.

USQL -327 THE ROW CANNOT BE INSERTED BECAUSE IT IS OUTSIDE THE BOUND OF THE PARTITION RANGE FOR THE LAST PARTITION

Explanation: When a row is inserted, the calculated partition key value for the new row must be within the bounds of a partition (as specified in the VALUES clause of the CREATE INDEX statement).

User Response: Correct the statement to specify a value for the partition key that is within the bounds of the last partition of the partitioned table space.

USQL -330 A STRING CANNOT BE USED BECAUSE IT CANNOT BE TRANSLATED. REASON reason-code, CHARACTER code-point, HOST VARIABLE position-number

Explanation: A translation error occurred during the translation of a string to a different coded character set. The type of error is indicated by the reason-code:

8 Length exception (for example,expansion required for PC MIXEDdata exceeds the maximum lengthof the string).

12 Invalid code point (for example,use of the ERRORBYTE option ofSYSSTRINGS).

16 Form exception (for example,invalid MIXED data).

20 Translate procedure error(for example, an exit setthe length control field ofthe string to an invalidvalue).

24 SBCS character was found ina string contained in awchar_t host variable.

If the reason-code is 12, code-point is the invalid code point. Otherwise, code-point is either blank or an additional reason-code returned by an exit. If the string is the value of an input host variable, the position-number is the ordinality of the variable in the SQLDA. If the string is not the value of a host variable, the position-number is blank.

User Response: Take one of the following actions based on the reason-code:


– If the reason-code is 8, extend the maximum length of the host variable to allow for expansion that occurs when the string is translated.

– If the reason-code is 12, change the translate table to accept the code-point or change the data to eliminate the code-point.

– If the reason-code is 16 and the string is described as MIXED data, change its description or change the string to conform to the rules for well-formed mixed data.

– If the reason-code is 20, correct the translate procedure.– If the reason-code is 24, delete the SBCS character from the graphic string.

USQL -331 A STRING CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE IT CANNOT BE TRANSLATED. REASON reason-code, CHARACTER code-point, POSITION position-number

Explanation: The operation required the translation of a string to the coded character set of the host variable and a translation error occurred. The type of error (noted below) is indicated by the reason-code:

– 8 for length exception (e.g., expansion required for PC MIXED data exceeds the maximum length of the string).

– 12 for invalid code-point (e.g., use of the ERRORBYTE option of SYSSTRINGS).– 16 for form exception (e.g., invalid MIXED data).– 20 for translate procedure error (e.g., an exit set the length of the control field of

the string to an invalid value).

If the reason-code is 12, code-point is the invalid “code point”. Otherwise, code-point is blank. The position-number is the ordinality of the output variable in the SQLDA.

User Response: If the reason-code is 8, the maximum length of the result column must be extended to allow for the expansion that occurs when the string is translated. If the reason-code is 12, the translate table must be changed to accept the code-point or the data must be changed to eliminate the code point. If the reason-code is 16, and the string is described as MIXED data, its description must be changed or the string must be changed to conform to the rules for well-formed MIXED data. If the reason-code is 20, the translate procedure must be corrected. An alternative to these corrective actions is to provide an indicator variable so that a null value and a warning can be returned rather than an error. Refer to Chapter 3 of the SQL Reference Manual for additional information on a coded character set.

USQL -332 SYSSTRINGS DOES NOT DEFINE A TRANSLATION FROM CCSID ccsid TO ccsid

Explanation: The operation required a translation of a string to a different coded character set, but the specific translation is not described in the SYSSTRINGS catalog table. The first ccsid identifies the coded character set of the string and the second ccsid identifies the coded character set to which it must be translated.

User Response: If the CCSIDs are correct, the only corrective action is to provide for the translation by inserting a row into SYSSTRINGS. For an SBCS translation, the row must contain a translate table or the name of a user-provided translate procedure. For a DBCS translation, the row must contain the name of a user-provided translate procedure. Refer to Chapter 3 of the SQL Reference Manual for additional information on a coded character set.

USQL -333 THE SUBTYPE OF A STRING VARIABLE IS NOT THE SAME AS THE SUBTYPE KNOWN AT BIND TIME, AND THE DIFFERENCE CANNOT BE RESOLVED BY TRANSLATION

Explanation: The CCSID in the run time SQLDA is inconsistent with the bind time subtype of the host variable or parameter marker. Either the run time description is BIT and the bind time description was not BIT, or the run time description is not BIT and the bind time description was BIT.

User Response: Change the CCSID in the SQLDA so that the subtype of the host variable is consistent with the bind time subtype of the host variable or parameter marker. Refer to Chapter 3 of the SQL Reference Manual for additional information on a coded character set.

USQL -338 AN ON CLAUSE IS INVALID

Explanation: This return code reports a violation of one of the following:

– One expression of the predicate must only reference columns of one of the operand tables of the associated join operator, and the other expression of the predicate must only reference columns of the other operand table.


– A VALUE or COALESCE function is allowed in the ON clause only when the join operator is a FULL OUTER JOIN or FULL JOIN.

– An operator other than = is not allowed in a FULL OUTER JOIN or FULL JOIN.

User Response: Correct the syntax of the statement so that each ON clause expression references only one of the operand tables. You may work around the second restriction by using a nested table expression with the VALUE/COALESCE function in the SELECT list of the table expression.

USQL -339 THE SQL STATEMENT CANNOT BE EXECUTED FROM AN ASCII BASED DRDA APPLICATION REQUESTOR TO A V2R2 DB2 SUBSYSTEM

Explanation: The application is connected to a DB2 Version 2 Release 3 database server. The SQL statement is using an alias or three-part name, which refers to another DB2 subsystem that is at the Version 2 Release 2 level. DB2 Version 2 Release 2 does not support character conversion. Since the execution of SQL statements from an ASCII DRDA requester to an EBCDIC Version 2 Release 2 DB2 server could require character conversion, access to the Version 2 Release 2 DB2 is denied for data integrity reasons.

User Response: Remove statements from the application that resolve to a DB2 Version 2 Release 2 subsystem.

Note: If the application must refer to the Version 2 Release 2 subsystem data, the Version 2 Release 2 DB2 subsystem must be migrated to Version 2 Release 3 where character conversion is supported.

USQL -351 AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION “<position-number>” ON A PREPARE OR DESCRIBE OPERATION

Explanation: Some SQL data types are not supported by DB2 Version 5. “<position-number>” is the position of the first element with an invalid data type in the SQLDA. A common reason why this error occurs is when DB2 attempts to describe large object data residing at a non-DB2 server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB and DBLOB.

User Response: The application program must not include any SQL operations that describe SQL data types which DB2 Version 5 does not support when DB2 is the application requester (AR). For example, instead of dynamically selecting all columns from SYSTABLES, select only those columns that have data types defined to DB2. If the error is caused by an unsupported LOB type, exclude such data from the list of data to be described.

USQL -400 THE CATALOG HAS THE MAXIMUM NUMBER OF USER DEFINED INDEXES

Explanation: Only one hundred user-defined indexes can be created in the catalog database.

User Response: If this index must be created, another user-defined index on the catalog must be dropped. After that index has been dropped, this statement can be executed.

USQL -401 THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT COMPARABLE

Explanation: An arithmetic operation appearing within the SQL statement has a mixture of numeric and non-numeric operands, or the operands of a comparison operation are not compatible.

User Response: Check the data types of all operands to ensure that their data types are comparable and compatible with their usage in the statement.If all the operands of the SQL statement are correct, and if a view is then being accessed, check the data types of all the operands in the view definition.

USQL -402 AN ARITHMETIC FUNCTION OR OPERATOR arith-fop IS APPLIED TO CHARACTER OR DATETIME DATA

Explanation: A non-numeric operand has been specified for the arithmetic function or operator “arith-fop”.

User Response: Examine and correct the syntax of the SQL statement such that all operands of the specified function or operator are numeric.


USQL -404 THE UPDATE OR INSERT STATEMENT SPECIFIES A STRING THAT IS TOO LONG column-name

Explanation: An INSERT or UPDATE statement specifies a value that is longer than the maximum-length string that can be stored in the indicated column.

User Response: Check the length of the object column and correct the program or SQL statement so that the length of the insert or update string does not exceed that maximum.

USQL -405 THE NUMERIC LITERAL literal CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OF RANGE

Explanation: The specified numeric literal is not in the proper range. The proper ranges for SQL values are displayed below:

– 5.4E-79 to 7.2E+75 for FLOAT values– -(10{31} -1) to + (10{31} -1) for DECIMAL values– -2147483648 to 2147483647 for INTEGER values– -32768 to +32767 for small integer (SMALLINT) values.

User Response: The value of the literal should be reduced to the appropriate size for this data type.

USQL -406 A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN THE RANGE OF ITS OBJECT COLUMN

Explanation: A value derived or calculated during the processing of the SQL statement was outside the range of the data type of its object column. This problem might have arisen because the values occurring in the object column were out of range, or because the SQL operation performed was not appropriate for the values in the object column.

User Response: See the explanation of SQLCODE SQL0405 for allowed ranges for all numeric data types.

USQL -407 AN UPDATE OR INSERT VALUE IS NULL, BUT THE OBJECT COLUMN column-name CANNOT CONTAIN NULL VALUES

Explanation: One of the following conditions has occurred:

– A null insert or update value was specified for a column defined as NOT NULL.– No insert value was provided for a column that does not have a default value.

User Response: Examine the definition of the object table to determine which columns of the table have the NOT NULL attribute, and then correct the SQL statement accordingly.

USQL -408 AN UPDATE OR INSERT VALUE IS NOT COMPARABLE WITH THE DATA TYPE OF ITS OBJECT COLUMN column-name

Explanation: The data type of the value to be inserted or set in the column “column-name” by an INSERT or UPDATE statement is incompatible with the declared data type of that column. Both must be numeric or both must be graphic string; or both must be either:

– Dates or character– Times or character– Timestamps or character.

However, dates, times, or timestamps cannot be assigned to a specific character column that has a field procedure.

User Response: Examine the current definition for the object table and ensure that the host variable or literal value assigned to the specified column has the proper data type.

USQL -409 INVALID OPERAND OF A COUNT FUNCTION

Explanation: The operand of the COUNT function in the statement violates SQL syntax. A common error is a column name or other expression without DISTINCT.

User Response: Correct the syntax and resubmit the statement. Refer to Chapter 4 of the SQL Reference Manual for information about the proper form for the operands of a COUNT function.

USQL -410 THE FLOATING POINT LITERAL literal CONTAINS MORE THAN 30 CHARACTERS

Explanation: The specified floating-point literal is more than 30 characters in length. By definition, a floating-point literal has a maximum length of 30 characters.


User Response: Correct the indicated literal.

USQL -411 CURRENT SQLID CANNOT BE USED IN A STATEMENT THAT REFERENCES REMOTE OBJECTS

Explanation: A reference to the CURRENT SQLID special register is invalid in a statement that contains the three-part name or alias of an object that is remote to the remote server.

User Response: Remove the reference to CURRENT SQLID or remove the reference to the remote object.

USQL -412 THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS

Explanation: In the context in which it was used in the SQL statement, the subquery can have only one column specified in its SELECT clause.

User Response: Correct the syntax of the SQL statement. Refer to Chapter 5 of the SQL Reference Manual for information about restrictions on the syntax for subqueries.

USQL -413 OVERFLOW OCCURRED DURING NUMERIC DATA TYPE CONVERSION

Explanation: During the processing of an SQL statement, an overflow condition arose when converting from one numeric type to another. Numeric conversion is performed according to the standard rules of SQL.

User Response: Examine the syntax of the SQL statement to determine the cause of the error. If the problem is data-dependent, it may be necessary to examine the data processed at the time of the error.

USQL -414 A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT A STRING

Explanation: The data type of the first operand of the LIKE predicate must be a character string or graphic string.

User Response: Respecify the predicate so that the data type of each operand is a character string or a graphic string.

USQL -415 THE CORRESPONDING COLUMNS, column-number, OF THE OPERANDS OF A UNION OR A UNION ALL DO NOT HAVE COMPARABLE COLUMN DESCRIPTIONS

Explanation: The column descriptions of corresponding columns of the operands of a UNION or UNION ALL must be comparable. The columns of ordinality “column-number” of the operands in this UNION or UNION ALL do not satisfy this requirement. For columns to be comparable, they must both be either numeric, character, graphic, date, time, or timestamp. They cannot be a mixture of these groups. If corresponding columns have field procedures, they must both have the same field procedure.

User Response: Check the data types of the specified columns and correct the UNION or UNION ALL statement so that all corresponding columns have comparable column descriptions.

USQL -416 AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN

Explanation: The UNION specified in the SQL statement could not be performed because one of the tables participating in the union contains a long string column (for example, a VARCHAR column with length greater than 254). The operands of a UNION cannot contain long string columns.

User Response: The implied function is not supported by DB2. Refer to Chapter3 of the SQL Reference Manual for information about restrictions on the manipulation of long string columns.

USQL -417 A STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER MARKERS AS THE OPERANDS OF THE SAME OPERATOR

Explanation: The statement string specified as the object of a PREPARE contains a predicate or expression where parameter markers have been used as operands of the same operator. For example:

?>?

This syntax is not permitted.


User Response: Correct the logic of the application program so that this syntax error does not occur. Refer to Chapter 6 of the SQL Reference Manual for information about the proper usage of parameter markers within SQL statements to be prepared.

USQL -418 A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE OF PARAMETER MARKERS

Explanation: Parameter markers cannot be used in the SELECT list, as the sole argument of a scalar function, or in a concatenation function. Parameter markers cannot be used in the string expression of an EXECUTE IMMEDIATE SQL statement.

User Response: Correct the logic of the application program so that this error does not occur. Refer to Chapter 6 of the SQL Reference Manual for information about the proper usage of parameter markers within SQL statements and for EXECUTE IMMEDIATE SQL statement restrictions.

USQL -419 THE DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE RESULT WOULD HAVE A NEGATIVE SCALE

Explanation: The decimal division is invalid because it will result in a negative scale.The formula used internally to calculate the scale of the result for decimal division is explained in Chapter 3 of the SQL Reference Manual.


USQL -420 THE VALUE OF A CHARACTER STRING ARGUMENT WAS NOT ACCEPTABLE TO THE function-name FUNCTION

Explanation: A character string argument did not conform to the requirements of the function. For example, a character string passed to the DECIMAL function did not conform to the rules for forming an SQL integer or decimal constant.

User Response: Change the argument value so it conforms to the requirements of the function as specified in the SQL Reference Manual.

USQL -421 THE OPERANDS OF A UNION OR A UNION ALL DO NOT HAVE THE SAME NUMBER OF COLUMNS

Explanation: The operands of a UNION or UNION ALL must have the same number of columns.

User Response: Correct the SQL statement so that there are exactly the same number of columns in each operand.

USQL -423 INVALID RESULT SET LOCATOR VALUE

Explanation: The value specified in a result set locator host variable does not identify a valid result set locator.

User Response: There are two common causes for this error:

– The host variable used as a result set locator was never assigned a valid result set locator value. Result set locator values are returned by the DESCRIBE PROCEDURE and ASSOCIATE LOCATORS statements. Make sure the value in your host variable is obtained from one of these two statements.

– Result set locator values are only valid as long as the underlying SQL cursor is open. If a commit or rollback operation closes an SQL cursor, the result set locator associated with the cursor is no longer valid.

USQL -426 DYNAMIC COMMIT NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED

Explanation: An application which is executing is using DRDA protocols. This application has attempted to issue a dynamic COMMIT statement, or a stored procedure has attempted to issue a COMMIT_ON_RETURN while connected to a location at which updates are not allowed. A dynamic COMMIT or COMMIT_ON_RETURN can be issued only while connected to a location at which updates are allowed.

User Response: The IMS or CICS protocols should be used to commit work in these environments.


USQL -427 DYNAMIC ROLLBACK NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED

Explanation: An application which is executing using DRDA protocols has attempted to issue a dynamic ROLLBACK statement while connected to a location at which updates are not allowed. A dynamic ROLLBACK may be issued only during the time when an application is connected to a location at which updates are allowed.

User Response: The IMS or CICS protocols should be used to rollback work in these environments.

USQL -440 THE NUMBER OF PARAMETERS IN THE PARAMETER LIST DOES NOT MATCH THE NUMBER OF PARAMETERS EXPECTED FOR STORED PROCEDURE name, AUTHID authid, and LUNAME luname. number PARAMETERS WERE EXPECTED.

Explanation: DB2 has received an SQL CALL statement for a stored procedure. DB2 found the row in the SYSIBM.SYSPROCEDURES catalog table associated with the requested procedure name. However, the number of parameters supplied on the CALL statement did not match the number of parameters defined in the PARMLIST column of the SYSIBM.SYSPROCEDURES table. The definition of a stored procedure might be cached. If you suspect that this message is being issued because the cached definition of a procedure does not match the definition of a procedure in the SYSIBM.SYSPROCEDURES table, issue the -START PROCEDURE command to refresh the cache. Note the following definitions:

name The name of the storedprocedure from thePROCEDURE field inSYSIBM.SYSPROCEDURES.

authid The authorization id fromthe AUTHID field inSYSIBM.SYSPROCEDURES.

luname The logical unit namefrom the LUNAME field inSYSIBM.SYSPROCEDURES.

number The expected number ofparameters for the storedprocedure with the NAME,AUTHID, and LUNAMEdescribed above.

User Response: If the SQL CALL statement is coded incorrectly, you must

modify the SQL application to provide the correct number of parameters on the SQL CALL statement. If the PARMLIST column of the SYSIBM.SYSPROCEDURES table contains incorrect information, you must make required updates to the PARMLIST column and then issue the -START PROCEDURE command to activate the updated definition.

USQL -444 USER PROGRAM name COULD NOT BE FOUND

Explanation: DB2 received an SQL CALL statement for a stored procedure and found the row in the SYSIBM.SYSPROCEDURES catalog table associated with the requested procedure name. However, the MVS load module currently identified in the LOADMOD column of the SYSIBM.SYSPROCEDURES row could not be found. Note the following definition:

name The name of the MVSload module thatcould not be found.

User Response: If the LOADMOD column value in the SYSIBM.SYSPROCEDURES table was specified incorrectly, correct the value and issue the -START PROCEDURE command to activate the changed definition. If the LOADMOD column value is correct, use the MVS linkage editor to create the required MVS load module in one of the MVS load libraries used by your installation for stored procedures.


USQL -450 STORED PROCEDURE name, PARAMETER NUMBER number OVERLAYED STORAGE BEYOND ITS DECLARED LENGTH

Explanation: While returning parameters from a stored procedure to an application, DB2 detected an overlay of one of the parameters. A stored procedure overwrote storage beyond a parameter’s declared length. Note the following definitions:

name The name of the storedprocedure from theNAME field in theSYSIBM.SYSPROCEDUREScatalog table.

number The parameter from thePARMLIST field in theSYSIBM.SYSPROCEDUREScatalog table.

User Response: Examine the stored procedure to determine the cause of the overlay. Ensure that all parameters are declared correctly and that they match the definitions in SYSIBM.SYSPROCEDURES for procedure name. If you suspect that an error exists in DB2, refer to Section 3 of the Diagnosis Guide and Reference for information on identifying and reporting the problem.

USQL -469 SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST VARIABLE FOR PARAMETER number

Explanation: DB2 received an SQL CALL statement for a stored procedure. DB2 found the row in the SYSIBM.SYSPROCEDURES catalog table associated with the requested procedure name. However, parameter number was identified in the PARMLIST column of the SYSIBM.SYSPROCEDURES table as an OUT or INOUT parameter. A host variable must be supplied on the SQL CALL statement for parameters defined as OUT or INOUT. Note the following definition:

number The parameter numberfrom the PARMLIST fieldin SYSIBM.SYSPROCEDURES.

User Response: If the SQL CALL statement is coded incorrectly, you must modify the SQL application to provide an output host variable on the SQL CALL statement. If the PARMLIST column of the SYSIBM.SYSPROCEDURES table contains incorrect information, perform the required updates to the PARMLIST column and issue the -START PROCEDURE command to activate the updated definition.

USQL -470 AN SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT PARAMETER number, BUT THE STORED PROCEDURE DOES NOT SUPPORT NULL VALUES

Explanation: DB2 received an SQL CALL statement for a stored procedure and found a null value in the incoming parameter list. The DB2 stored procedure was defined in the SYSIBM.SYSPROCEDURES catalog table with LINKAGE=” “, which specifies that the DB2 stored procedure does not accept null values. Note the following definition:

number The parameter numberfrom the PARMLIST fieldin SYSIBM.SYSPROCEDURES.

User Response: If the stored procedure should not accept null values, change the calling application to provide a nonnull value. If the stored procedure should accept null values, change the LINKAGE column in SYSIBM.SYSPROCEDURES to N.Use the -START PROCEDURE command to activate the changes to the SYSIBM.SYSPROCEDURES table.

USQL -471 SQL CALL FOR STORED PROCEDURE number FAILED DUE TO REASON rc

Explanation: DB2 received an SQL CALL statement for a stored procedure. The CALL statement was not accepted because of DB2 reason code rc. Note the following definitions:


name The name of the storedprocedure specifiedon the SQL CALLstatement.

rc The DB2 reason codedescribing the causeof the failure. Thepossible values are:00E79000, 00E79001,00E79002, 00E79003,00E79004, 00E79005,00E79006, 00E79007,00E7900B, and 00E7900C.

User Response: Correct the condition described by the DB2 reason code.

USQL -480 THE PROCEDURE procedure-name HAS NOT YET BEEN CALLED

Explanation: The procedure identified in a DESCRIBE PROCEDURE or an ASSOCIATE LOCATORS statement has not yet been called within the application process or the procedure has been called, but an explicit or implicit commit occurred before the statement.

User Response: Correct the order of the statements and rerun them.

USQL -482 THE PROCEDURE procedure-name RETURNED NO LOCATORS

Explanation: The procedure identified in an ASSOCIATE LOCATORS statement returned no result set locators.

User Response: Determine if result set locators are returned from the identified procedure by using the DESCRIBE PROCEDURE statement.

USQL -496 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT REFERENCES A RESULT SET THAT WAS NOT CREATED BY THE CURRENT SERVER

Explanation: The SQL statement cannot be executed because the current server is different from the server that called a stored procedure. The SQL statement can be any of the following:

– ALLOCATE CURSOR– DESCRIBE CURSOR– FETCH (using an allocated cursor)– CLOSE (using an allocated cursor)

User Response: Connect to the server that called the stored procedure which created the result set before running the SQL statement that failed.

USQL -497 THE LIMIT OF 32767 OBIDS HAS BEEN EXCLUDED FOR DATABASE database-name

Explanation: An attempt was made to create an object in database database-name, but the limit of 32767 OBIDs has been exceeded for that database.

User Response: DROP all unused objects in this database and issue a COMMIT, specify a different database, or run the MODIFY utility to reclaim unused OBIDs.

USQL -499 CURSOR cursor-name HAS ALREADY BEEN ASSIGNED TO THIS OR ANOTHER RESULT SET FROM PROCEDURE procedure-name

Explanation: An attempt was made to assign a cursor to a result set using the SQL statement ALLOCATE CURSOR and one of the following applies:

– The result set locator variable specified in the ALLOCATE CURSOR statement has been previously assigned to cursor cursor-name.

– The cursor cursor-name, specified in the ALLOCATE CURSOR statement has been previously assigned to a result set from stored procedure procedure-name.

User Response: Determine if the target result set named in the ALLOCATE CURSOR statement has been previously assigned to a cursor.

If the result set has been previously assigned to cursor cursor-name, choose another target result set or choose the call stored procedure procedure-name again and reissue the ASSOCIATE LOCATOR and ALLOCATE CURSOR statements. If the result set has


not been previously assigned to a cursor, the cursor cursor-name specified in the ALLOCATE CURSOR statement has been previously assigned to some result set from stored procedure procedure-name. You can not assign cursor cursor-name to another result set, so you must specify a different cursort name in the ALLOCATE CURSOR statement.

USQL -500 THE IDENTIFIED CURSOR WAS CLOSED WHEN THE CONNECTION WAS DESTROYED

Explanation: The FETCH, UPDATE, DELETE, or CLOSE statement identifies a closed cursor that was defined with the WITH HOLD option. The cursor was closed when the connection on which it was dependent was destroyed during a commit operation. The connection was destroyed because the application process placed it in the released state, or the application plan was bound with the DISCONNECT(AUTOMATIC) option.

User Response: The correction depends on the desired state of both the cursor and the connection, as noted below:

– If you want the cursor closed, you must change the application program so that the cursor is not referenced in the closed state.

– If you want the cursor open, and the connection was placed in the released state by the application program, you must change the program so that the connection is not placed in the released state until the cursor is explicitly closed.

– If you want the cursor open and the connection was placed in the released state as a result of the DISCONNECT(AUTOMATIC) option, rebind the plan using DISCONNECT(CONDITIONAL).

Correct the error in the application, rebind the plan, and resubmit the job.

USQL -501 THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS NOT OPEN

Explanation: The application program attempted to do one of the following:

a. FETCH using a cursor, or

b. CLOSE using a cursor

at a time when the specified cursor was not open.

User Response: Check for a previous SQL return code that may have closed the cursor. Commit and rollback operations close cursors. UNSUCCESSFUL SQLCODES -404, -652, -679, -901, -904, -909, -910, -911, and -913 will force the cursor to close. After the cursor is closed, any fetches or close cursor statements will receive this USQLCODE -501.

If no previous SQL return codes have been issued, correct the logic of the application program to ensure that the cursor is open at the precise time the FETCH or CLOSE statement is executed.

USQL -502 THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY OPEN

Explanation: The application program attempted to execute an OPEN statement for a cursor that was already open.

User Response: Correct the logic of the application program to ensure that it does not attempt to execute an OPEN statement for a cursor that is already open.

USQL -503 A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED IN THE UPDATE CLAUSE OF THE SELECT STATEMENT OF THE CURSOR

Explanation: The application program attempted to update (while using a cursor) a value in a column of the object table that was not identified in the FOR UPDATE clause in the cursor declaration. Any column that is to be updated must be identified in the FOR UPDATE clause of the cursor declaration.

User Response: Correct the application program. If the column is to be updated, its name must be added to the FOR UPDATE clause of the cursor declaration.

USQL -504 THE CURSOR NAME cursor-name IS NOT DEFINED

Explanation: Cursor cursor-name was referenced in an SQL statement. One of the following statements is true.


– Cursor cursor-name was not declared (using the DECLARE CURSOR statement) or allocated (using the ALLOCATE CURSOR statement) in the application program before it was referenced.

– Cursor cursor-name was referenced in a positioned UPDATE or DELETE statement which is not a supported operation for an allocated cursor.

– Cursor cursor-name was allocated, but a CLOSE cursor statement naming cursor-name was issued and deallocated the cursor before this cursor reference.

– Cursor cursor-name was allocated, but a ROLLBACK operation occurred and it deallocated the cursor before this cursor reference.

– Cursor cursor-name was allocated, but its associated cursor which was declared in a stored procedure was not declared WITH HOLD, and a COMMIT operation occurred and subsequently deallocated the cursor before this cursor reference. The COMMIT operation can be explicit (like the COMMIT statement) or implicit (like a stored procedure defined as COMMIT_ON_RETURN = “Y” was called before this cursor reference).

– Cursor cursor-name was allocated, but its associated stored procedure was called again since the cursor was allocated, the new results sets were returned, and cursor cursor-name was deallocated.

User Response: Check the application program for completeness and for a possible spelling error in the cursor declaration or allocation. The declaration for, or allocation of, a cursor, must appear in an application program before SQL statements that reference the cursor. If the cursor-name was <UNKNOWN>, the cursor was not successfully declared or allocated. This can occur if SQL(DB2) was used, and a warning message was issued during precompilation. Check the precompile output for warning messages on the DECLARE CURSOR or ALLOCATE CURSOR statement, and then correct the statement. Regarding an allocated cursor, please note the following: If an implicit or explicit COMMIT, ROLLBACK, or CLOSE occurred since the cursor was successfully allocated, you must modify the application program logic to do one of the following tasks:

– After the COMMIT, ROLLBACK, or CLOSE operation, call the associated stored procedure again, and then reissue the ASSOCIATE LOCATORS and ALLOCATE CURSOR statements.

– For COMMIT, declare the associated cursor in the stored procedure WITH HOLD so the COMMIT operation will not deallocate the cursor.

For an allocated cursor, if the associated stored procedure was called again and the new result sets were returned because the cursor was allocated, reissue the ASSOCIATE LOCATORS and ALLOCATE CURSOR statements.

USQL -507 THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT OPEN

Explanation: The application program attempted to execute an UPDATE or DELETE WHERE CURRENT OF cursor statement at a time when the specified cursor was not open.

User Response: Check for a previous SQL return code that might have closed the cursor. UNSUCCESSFUL SQLCODES -404, -652, -679, -901, -904, -909, -910, -911, and -913 force the cursor to close. After the cursor is closed, any fetches or close cursor statements receive USQLCODE -501. Any updates or deletes receive the USQLCODE -507. Correct the logic of the application program to ensure that the specified cursor is open at the time the UPDATE or DELETE statement is executed.

USQL -508 THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT POSITIONED ON A ROW

Explanation: The application program attempted to execute an UPDATE or DELETE WHERE CURRENT OF cursor statement at a time when the specified cursor was not positioned on a row of the object table. The cursor must be positioned on the row that is to be updated or deleted.

Note that the cursor is no longer positioned on a row if the row is deleted or an index column of the row is updated by another cursor in the same application program.

User Response: Correct the logic of the application program to ensure that the cursor is correctly positioned on the intended row of the object table before the UPDATE or DELETE statement is executed. Note that the cursor is not positioned on a row if FETCH returned an SQLCODE = 100.


USQL -509 THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT THE SAME TABLE DESIGNATED BY THE CURSOR

Explanation: The application program attempted to execute an UPDATE or DELETE WHERE CURRENT OF cursor statement where the table named in that statement did not match the name of the table specified in the declaration for that cursor.

User Response: Correct the application program to ensure that the table identified in the UPDATE or DELETE statement is the same table identified in the declaration for the cursor.

USQL -510 THE TABLE DESIGNATED BY THE CURSOR OR THE UPDATE OR DELETE STATEMENT CANNOT BE MODIFIED

Explanation: The application program attempted to execute an UPDATE or DELETE WHERE CURRENT OF cursor statement against a table or view that cannot be updated or deleted. This can occur for a delete from a read-only view or for an update in which the cursor was not defined with the FOR UPDATE clause.

This error code is also returned when the table exists at a remote location and DB2 has employed block fetching because you explicitly declared the cursor FOR FETCH ONLY, or because the application is bound CURRENTDATA(NO) and the cursor is ambiguous. This error code is also returned if DB2 has employed parallelism to execute the SELECT statement associated with the cursor named in a DELETE WHERE CURRENT OF cursor statement. Or, the error code is also returned if a DELETE WHERE CURRENT OF is issued against a row which DB2 cannot guarantee to have not been modified by another application since the specific time when the cursor was positioned upon it (in accordance with ISO(CS) semantics for an ambiguous cursor in an application bound CURRENTDATA(NO)).

User Response: The requested UPDATE or DELETE cannot be performed. Refer to Chapter 6 of the SQL Reference Manual for information about restrictions on using UPDATE and DELETE operations against views. For a remote table, modify the DECLARE CURSOR and then rebind the PLAN. For a cursor that uses parallelism, disable parallelism for the query by using the DEGREE(1) BIND option for static SQL or by setting the CURRENT DEGREE special register to “1” for dynamic SQL. For an ambiguous cursor in a application bound CURRENTDATA(NO), make the cursor unambiguous (declare it FOR UPDATE OF) or rebind the application CURRENTDATA(YES).

USQL -511 THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE TABLE DESIGNATED BY THE CURSOR CANNOT BE MODIFIED

Explanation: The result table of the SELECT statement cannot be updated. This can occur if the SELECT specifies more than one table or view in the FROM clause, provided the SELECT list contains a built-in function or DISTINCT, or if the statement contains an ORDER BY or GROUP BY or HAVING clause. This can also occur if a view is specified in the FROM clause and the view cannot be updated.

User Response: Updates cannot be performed on the result table as it is specified. Refer to Chapter 6 of the SQL Reference Manual for information regarding restrictions on the updating of views.

USQL -512 STATEMENT REFERENCE TO REMOTE OBJECT IS INVALID


– The statement refers to multiple locations.– A statement with a remote reference is being EXPLAINED by a dynamic EXPLAIN

statement or by the EXPLAIN(YES) option.– An alias is used incorrectly.– A three-part name is implicitly or explicitly used in a statement that is not

supported by the DB2 private protocols.

User Response: If the object cannot be meaningfully eliminated from the statement, refer to your Database Administrator for other ways to obtain the data required. Refer to Chapter 4 of the SQL Reference Manual for additional information about using remote objects.

USQL -513 THE ALIAS alias-name MUST NOT BE DEFINED ON ANOTHER LOCAL OR REMOTE ALIAS

Explanation: The object indicated by “alias-name” is a local or remote alias. An alias is not allowed to be defined on a local alias, and it should not be defined on a remote alias.


User Response: Modify the SQL statement to ensure that all object references are to base tables or views.

USQL -514 THE CURSOR cursor-name IS NOT IN A PREPARED STATE

Explanation: The application program has tried to use a cursor, cursor-name that is not in a prepared state. The cursor is associated with a statement that (1) has never been prepared, or (2) has been invalidated by a commit or rollback operation.

User Response: For case (1), ensure that you prepare the statement that is named in the DECLARE CURSOR statement for cursor-name before you try to open the cursor. For case (2), perform one of the following:

– Use the WITH HOLD option of DECLARE CURSOR.– Do not execute a commit or rollback operation until you are finished using the

cursor.– Prepare the statement again after the commit or rollback.

USQL -516 THE DESCRIBE STATEMENT DOES NOT IDENTIFY A PREPARED STATEMENT

Explanation: An attempt was made to execute a DESCRIBE for a statement that had not been successfully prepared beforehand. This error can occur when the DESCRIBE originates on an application requester that supports extended dynamic SQL. Because the target statement is static on the DB2 for MVS/ESA subsystem, the DESCRIBE statement fails.

User Response: Correct the logic of the application program to ensure that a statement is properly prepared before a DESCRIBE of the statement is attempted. If the DESCRIBE is a distributed request that originated on a system that supports extended dynamic SQL, contact your System Administrator about changing the DB2 subsystem parameter DESCSTAT to YES to tolerate these DESCRIBE requests against static SQL.

USQL -517 CURSOR cursor-name CANNOT BE USED BECAUSE ITS STATEMENT NAME DOES NOT IDENTIFY A PREPARED SELECT STATEMENT

Explanation: The cursor “cursor-name” could not be used as specified because the prepared statement named in the declaration for the cursor was not a SELECT statement.

User Response: Verify that the statement-name is specified correctly in the PREPARE statement and in the DECLARE CURSOR statement for cursor “cursor-name”. Alternatively, correct the application program logic to ensure that only prepared SELECT statements are used in association with cursor declarations.

USQL -518 THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT


– The statement named in the EXECUTE statement has not been prepared.– The statement named in the EXECUTE statement identifies a SELECT statement.– The statement named in the EXECUTE IMMEDIATE statement identifies a

SELECT statement.

User Response: Ensure that you prepare the statement prior to EXECUTE. Also, ensure that the statement you prepare is not a SELECT statement.

USQL -519 THE PREPARE STATEMENT IDENTIFIES THE SELECT STATEMENT OF THE OPENED CURSOR cursor-name

Explanation: The application program has attempted to PREPARE (actually, it has attempted to re-PREPARE) the SELECT statement for the specified cursor at a time when that cursor was already open.

User Response: Correct the logic of the application program so that it does not attempt to re-PREPARE the SELECT statement for a cursor when that cursor is open.

USQL -525 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS IN ERROR AT BIND TIME FOR SECTION = sectno PACKAGE = pkgname CONSISTENCY TOKEN = X”contoken”

Explanation: One of the following actions occurred:

– The statement was in error when the package was bound, but the error was ignored at the time because the option SQLERROR (CONTINUE) was used. Since the statement contains an error, it cannot be executed.


– The statement might not be an executable statement at this location, or might only be executable by a DB2 application requester (for example, DECLARE TABLE in an application running on OS/2 causes this message to occur).

The variables are as follows:

– sectno Section Number– pkgname locid.collid.pkgid– contoken Consistency token in hexadecimal

User Response: If the SQL statement is not required to execute at the indicated location, correct the program so that the statement in error does not execute at that point. Precompile, compile, and bind replace the package. If the SQL statement is supposed to execute at the indicated location, correct the problem which was discovered when it was bound and then bind the package over using BIND with ACTION(REPLACE). If multiple versions of the package have been bound, enter the following SELECT statement to determine which version contains the error: SELECT VERSION FROM locid.SYSIBM.SYSPACKAGE WHERE LOCATION = “ “ AND COLLID = “collid” AND NAME = “pkgid” AND HEX(CONTOKEN) = “contoken”Where the variables are:

– locid Location name– collid Collection id– pkgid Program name


Documents

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