Xpediter/TSO and Xpediter/IMS
Messages and Codes
Release 9.3
ii
Xpediter/TSO and Xpediter/IMS Messages and Codes
Please direct questions about Xpediter/TSO and Xpediter/IMS
or comments on this document to:
Xpediter/TSO and Xpediter/IMS Customer Support
http://go.compuware.com/
This document and the product referenced in it are subject to the following legends:
Copyright 1996-2013 Compuware Corporation. All rights reserved. Unpublished rights reserved under the
Copyright Laws of the United States.
U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS
227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995),
FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation.
This product contains confidential information and trade secrets of Compuware Corporation. Use,
disclosure, or reproduction is prohibited without the prior express written permission of Compuware
Corporation. Access is limited to authorized users. Use of this product is subject to the terms and
conditions of the user’s License Agreement with Compuware Corporation.
Xpediter, Code Coverage, File-AID, Abend-AID, FrontLine, and Compuware Shared Services are
trademarks or registered trademarks of Compuware Corporation.
IBM, CICS, DB2, IMS, Language Environment, MQSeries, MVS, OS/390, VisualAge, WebSphere MQ, and
z/OS are trademarks of International Business Machines Corporation.
CA-MIM, CA-ROSCOE, ENDEVOR, LIBRARIAN, PANEXEC, and PANVALET are trademarks or registered
trademarks of CA Technologies, Inc.
Adobe® Reader® is a trademark of Adobe Systems Incorporated in the United States and/or other
countries.
All other company and product names are trademarks or registered trademarks of their respective owners.
Doc. CWXTMX9D
October 24, 2013
iii
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Manual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Accessing Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Notation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
VisualAge PL/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Documentation Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Compuware Go Customer Support Website . . . . . . . . . . . . . . . . . . . . . . . .viii
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
World Wide Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Compuware Go Customer Support Website . . . . . . . . . . . . . . . . . . . . . . . .viii
Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Corporate Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Information for Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Chapter 1. Xpediter/TSO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Chapter 2. User Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Chapter 3. Miscellaneous Messages and Codes Information . . . . . . . . . . . . . . . . 3-1
Xpediter/ROS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Condition Codes from Documentation Recreation Utility . . . . . . . . . . . . . . . . 3-1
Chapter 4. Xpediter for DB2 Extension Run-Time Messages . . . . . . . . . . . . . . . . 4-1
Chapter 5. Unsuccessful SQL Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
iv
Xpediter/TSO and Xpediter/IMS Messages and Codes
v
Introduction
Intro
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 selfexplanatory. Unnumbered messages in the session 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 Customer Support directly.
Manual Organization
The Xpediter Messages and Codes Manual is divided into five sections:
•
•
•
•
•
Chapter
Chapter
Chapter
Chapter
Chapter
1,
2,
3,
4,
5,
“Xpediter/TSO Messages”
“User Abend Codes”
“Miscellaneous Messages and Codes Information”
“Xpediter for DB2 Extension Run-Time Messages”
“Unsuccessful SQL Error Codes”.
Intended Audience
Generally, recommended actions and explanations for Xpediter messages and abend
codes are written for the installer and for the end user: the COBOL, Assembler, PL/I, or C
Language programmer using one of the Xpediter products to debug their programs.
Accessing Other Products
Xpediter/TSO and Xpediter/IMS are fully integrated with Compuware’s File-AID for DB2
and Abend-AID. From the Xpediter/TSO Primary Menu, you can access a CICS region
where you can use other Compuware tools, such as Xpediter/CICS and Abend-AID for
CICS. From the Xpediter/TSO Primary Menu, you can also access (if installed), FileAID/MVS and File-AID for IMS.
Notation Rules
The following notation rules apply:
• Messages and abends are shown in the following format, when applicable:
– Message number
– Message
vi
Xpediter/TSO and Xpediter/IMS Messages and Codes
–
–
–
–
Module name, if required
Explanation of message
System action, if necessary
User action, if necessary.
• 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 session log and abend messages list one or more modules as
the source of the message. This information is used by Compuware Customer
Support to help answer your questions.
• If the message or abend was generated in response to bad program data, the product
can provide information as to the type of data (“X” for alphanumeric, “N” for binary
or numeric) and data item length. Under certain circumstances, “C” could be either
alphanumeric or a character. For example, “X(30)” means that up to thirty bytes of
data (perhaps a dataset name) will be inserted into the message.
• Whenever a user abend occurs, there should be another message preceding it.
VisualAge PL/I
The compiler for VisualAge PL/I is somewhat different in the way it handles certain
aspects of the language. One such difference involves the method by which statements
are identified. Traditionally, each PL/I statement was given a unique statement number
for identification in the various elements of the compiler output. Under VisualAge PL/I
compilation, however, the identification is less finite, with only the file and line number
being used to discern between language constructs.
Because this mechanism is somewhat awkward when using Xpediter, the Compuware
Language Processor instead associates each file and line number combination with a
single sequential line number. It is this generated line number which is used by Xpediter
with VisualAge PL/I programs as the replacement notation for statement number under
previous PL/I compilers.
As a result, references to the term “statement” in Xpediter documentation, messages and
panels actually refer to the line construct (which may contain multiple statements) in a
VisualAge PL/I environment.
Related Publications
The following Compuware documents are also available for use with Xpediter/TSO and
Xpediter/IMS:
• Xpediter/TSO and Xpediter/IMS Installation Guide
This document describes the steps necessary to install Xpediter/TSO and
Xpediter/IMS (full-screen IMS/DC) for testing COBOL, Assembler, C, and PL/I
programs. Xpediter/IMS tests COBOL, Assembler, C, and PL/I programs that are
executed in MPP, BMP, and IFP(Fast Path) regions.
• Xpediter/TSO and Xpediter/IMS COBOL User 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
Introduction
vii
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 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
Assembler context.
• Xpediter/TSO and Xpediter/IMS PL/I User 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 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.
• File-AID/MVS Online Reference Manual
This document describes the online product features, screens, options, fields, and
commands of File-AID/MVS.
• File-AID/MVS Batch Reference Manual
This document provides information necessary to fully use the batch features of FileAID.
• File-AID for IMS/ISPF Reference Manual
This document details the information necessary to fully use the features of File-AID
for IMS/ISPF.
• Xpediter/Xchange Installation and Reference Manual
This document provides the information needed for testing your date- and timesensitive 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
viii
Xpediter/TSO and Xpediter/IMS Messages and Codes
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.
Documentation Availability
Compuware Go Customer Support Website
Access online customer support for Compuware products via our Compuware Go
customer support website. View or download documentation, frequently asked questions,
and product fixes, or directly e-mail Compuware with questions or comments. To access
Compuware Go, you must first register and obtain a password at
http://go.compuware.com.
Online Documentation
The installation package includes the following Xpediter documentation in these
electronic formats:
• Release Notes in HTML format
• The product manuals in PDF format
• The Adobe PDF index file (PDX file).
PDF and PDX Files
View and print the PDF files with Adobe Reader. Download a free copy of the reader from
Adobe’s website, http://www.adobe.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.
Customer Support
Compuware provides a variety of support resources to make it easy for you to find the
information you need.
Compuware Go Customer Support Website
You can access online information for Compuware products via our Compuware Go
customer support website at http://go.compuware.com.
Compuware Go provides access to critical information about your Compuware products.
You can review frequently asked questions, read or download documentation, access
product fixes, or e-mail your questions or comments. The first time you access
Compuware Go, you are required to register and obtain a password. Registration is free.
Compuware now offers User Communities, online forums to collaborate, network, and
exchange best practices with other Compuware solution users worldwide. To join, go to
http://groups.compuware.com.
Introduction
ix
Contacting Customer Support
Phone
• USA and Canada: 1-800-538-7822 or 1-313-227-5444.
• All other countries: Contact your local Compuware office. Contact information is
available at http://go.compuware.com.
Web
You can report issues via the Quick Link Create & View Support Cases on the
Compuware Go home page.
Note:
Please report all high-priority issues by telephone.
Mail
Compuware Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099
Corporate Website
To access Compuware’s site on the Web, go to http://www.compuware.com.
The Compuware site provides a variety of product and support information.
Information for Customer Support
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, request Customer Support for
Compuware Shared Services (CSS) and provide the following information:
•
•
•
•
•
Release level of compiler
List of other vendor products used
Abend module name
Any messages in CWPERRM ddname
Release of 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
• 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 session log dataset at the time of the abend.
Note:
When in-depth diagnosis is required, the following documentation will be
requested from you:
x
Xpediter/TSO and Xpediter/IMS Messages and Codes
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 session 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.
Xpediter/TSO Messages
XPD@@01E
Chap 1
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:
XPD@@03E
Xpediter requires precise BLKSIZE as specified in EXEC PARM.
THIS IS NOT A STARTED TASK
Explanation:
User Response:
XPD@@04E
It must be a started task.
Please do not submit from TSO.
ENQ PROPAGATING TASK ALREADY STARTED
Explanation:
User Response:
XPD@@05W
The operator already issued a START command for our started task, and it is operating.
Another START command is neither needed nor allowed.
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
Customer 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.
1-2
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD0011
Contact your internal technical support.
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:
XPD0025
STORAGE AVAILABLE FOR SIMULATE LIST
Module:
ADSRA058
Explanation:
User Response:
XPD0033
This is a continuation of message XPD0012. G(4) is the system ID.
No main storage was available to build a list of simulated module names.
Increase the REGION size and try the test again.
MEMORY ALLOCATION FAILED. BYTES REQUESTED N(4) MNEMONIC X(8)
Module:
ADSRA003 and ADSRA007
Explanation:
Allocation of virtual storage in subpool zero failed for Xpediter control block allocation.
User Response: If the length specified seems reasonable, increase the REGION size; or contact your internal
technical support.
XPD0034
CONTROL STACK ENTRY MAXIMUM EXCEEDED
Module:
ADSRA106
Explanation: The number of hierarchical levels in Xpediter exceeds the control stack capacity. This stack is
used as an internal control mechanism by Xpediter to maintain proper linkages between call interfaces.
User Response:
XPD0054
Contact your internal technical support.
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 and ADSRA553
Explanation:
User Response:
XPD0070
An attempt to acquire additional storage failed.
Increase the REGION allocated to the TSO logon session or the JOB step.
INVALID TRANSLATE OVERRIDES: X(40)
Module:
ADSRA007
Explanation:
The data supplied in the CTLTRLAT field has failed the validation check.
User Response: Ensure that valid values were supplied for the CTLTRLAT field during the product installation.
Changes to offsets X'00' through X'40' and/or alphanumeric offsets are not allowed.
XPD0071
OVERRIDE VALUES CONTINUED: X(40)
Module:
ADSRA007
Xpediter/TSO Messages
1-3
Explanation: A continuation of the display from message XPD0070. Displays the next forty bytes of the
CTLTRLAT field.
User Response:
XPD0087
See message XPD0070.
BREAKPOINT OFFSET N(4) EXCEEDS THE SIZE OF MODULE X(8)
Module:
ADSRA104 and ADSRA601
Explanation:
An interrupt address is invalid in the module for which a monitor event occurred.
User Response: Ensure that the member keyword for the appropriate Xpediter command was specified. If the
problem cannot be resolved, contact your internal technical support.
XPD0099
GLOBAL SYSTEM PARAMETER NOT FOUND - X(8)
Module:
ADSRA110
Explanation:
command.
User Response:
XPD0100
An invalid condition was detected in an Xpediter control block during processing of the current
This message must be communicated to your internal technical support.
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:
XPD0101
For CMS, use module ADSRA232.
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:
XPD0104
This condition must be reported to your internal technical support.
NESTING DEPTH OF 24 EXCEEDED FOR X(30)
Module:
ADSRA189
Explanation: The maximum record hierarchy depth of twenty-four levels has been exceeded for the specified
data element. As a result, the processing of the current command is terminated.
User Response:
XPD0105
None.
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:
XPD0111
This condition should be reported to your internal technical support.
NO MODULES FOUND IN RB OR LOAD LISTS
Module:
ADSRA242
1-4
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation:
found.
An attempt was made to display the sizes of all modules in the RB or LOAD list, but none were
User Response: This is presumed to be an Xpediter problem; therefore, contact your internal technical support.
XPD0113
MACHINE INSTRUCTION (iiii oooo) ENCOUNTERED BY XPEDITER: MEMBER=lmod, MODULE=csect,
OFFSET=xxxxxxxx, ADDRESS=xxxxxxxx
Module:
ADSRA129
Explanation: An unrecognized instruction was encountered in a user program by Xpediter while attempting to
resume execution. The instruction will be executed in the application after any breakpoint has been removed.
User Response:
XPD0118
SVRB SEARCH UNRESOLVED AFTER 5 LEVELS
Module:
ADSRA016
Explanation:
User Response:
XPD0121
None.
SVRB could not be found after five levels of the request block chain were searched.
Contact your internal technical support.
UNCORRECTABLE I/O ERROR FOR MEMBER C(8) IN C(8) SYNAD GPR 1 CONTENTS = X(4)
Module:
ADSRA512
Explanation:
message.
User Response:
example:
An I/O error occurred during an attempt to access the MEMBER and DD as specified in the
Verify correct use of DCB information for all datasets allocated per the DD specified. For
XTASKLIB DD:
Ensure that libraries have a RECFM of U and are usable load module libraries.
XINCLUDE DD:
Ensure that LRECL/BLKSIZE are valid and consistent for all datasets.
XPD0125
XPEDITER = N(4) OTHER = N(4) TOTAL = N(4)
Module:
ADSRA242
Explanation: The accumulated totals of both Xpediter and subpool zero are printed as the result of an XTEST
ADSRA242 command.
User Response:
XPD0138
None.
SIZE OF X(8) AT N(4) IS N(4)
Module:
ADSRA242
Explanation: This is an informational message printed to communicate the module size and location for
XTEST ADSRA242.
User Response:
XPD0150
I/O ERROR WHILE READING MODULE X(8)
Module:
ADSRA097
Explanation:
User Response:
XPD0151
There may be a problem with the module’s addressing mode.
Contact your internal technical support.
DELETE OF USER MODULE X(8) FAILED - RC = N(2)
Module:
ADSRA454
Explanation:
User Response:
XPD0152
None.
An attempt to delete an Xpediter or user module failed.
Probable Xpediter system error. Contact your internal technical support.
TROUBLE CLOSING USER FILES X(8)
Module:
ADSRA020 and ADSRA097
Xpediter/TSO Messages
Explanation:
User Response:
XPD0153
1-5
Xpediter could not close user files.
Either the files were not opened, or you need to try RETEST and then use the EXIT command.
DD X(8) NOT OPEN, CANNOT DO FUNCTION
Module:
ADSRA097
Explanation: Xpediter cannot perform any function on the indicated ddname and associated dataset because it
is not open.
User Response:
XPD0154
None.
ERROR DOING JFCB FOR DDNAME X(8)
Module:
ADSRA097
Explanation: An I/O operation error (possibly a READ error) was detected while the Job File Control Block was
performed for the indicated ddname.
User Response:
XPD0155
NO STORAGE FOR RDJFCB GETMAIN
Module:
ADSRA559
Explanation:
User Response:
XPD0157
None.
In the type N(13) form of the XA 2.2 RDJFCB, a GETMAIN was done and failed.
Try a larger REGION size.
TYPE 07 OF RDJFCB FAILED. CHECK THE FILE ALLOCATIONS.
Module:
ADSRA559
Explanation: In the type X’07’ form of the RDJFCB, a return code greater than zero was encountered. This
should not happen at this point.
User Response:
XPD0159
THE ONLY OPTIONS FOR RA206 ARE OPEN (1), CLOSE (2), AND BLDL (3)
Module:
ADSRA097
Explanation:
User Response:
XPD0160
Xpediter internal message. The OPTION parameter received in ADSRA097 is incorrect.
Contact your internal technical support.
TGT DID NOT POINT TO EXPECTED MCB
Module:
ADSRA130
Explanation:
User Response:
XPD0162
Contact your internal technical support.
The Task Global Table did not point to the Module Control Block.
Contact your internal technical support.
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 downlevel DDIO. Execution logging will continue.
User Response:
XPD0163
None.
NO X(21) TGT ENTRY FOR X(8)
Module:
ADSRA458
Explanation: No TGT (Task Global Table) record of the specified type was found in the DDIO dataset member
for the designated module. The absence of this record precludes determination of addresses for data elements
with this type of base locator.
User Response:
XPD0164
Contact your internal technical support.
X(21) IN THE TASK GLOBAL TABLE NOT INITIALIZED
Module:
ADSRA458
1-6
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation: The base locator assigned to the specified module and data element was not initialized. This
situation normally is encountered when an attempt is made to reference an item with a secondary base locator
before the indicated module is executed.
User Response:
XPD0165
None.
INVALID DATA TYPE DETECTED FOR X(30) IN X(8)
Module:
ADSRA173 and ADSRA680
Explanation: An unrecognized data type code was found in the DDIO dataset record for the specified data
element and module.
User Response:
XPD0180
FASTBREAK SUPPRESSED FOR X(8)
Module:
ADSRA374
Explanation:
User Response:
XPD0199
None.
FastBreak cannot function for Xpediter Release 3.0 or releases prior to it.
None.
USER MODULE X(8) DELETED
Module:
ADSRA454
Explanation:
processing.
Xpediter successfully deleted the specified module from memory. This occurs during “clean up”
XPD0201
THE CSVQUERY MACRO WAS INVOKED FOR MODULE, C(8,1,<MEMBER>), AND FAILED. RETURN CODE
(IN HEX): X(1,2,<REASON>).
Module:
ADSRA223
Explanation:
User Response:
The CSVQUERY macro failed with a non-zero return code.
Contact your internal technical support.
XPD0202
MODULE, C(8,1,<MEMBER>), HAS MORE THAN 2 SEGMENTS, LOAD MODULE CONTROL BLOCK
PROCESSING CONTINUED.
Module:
ADSRA223
Explanation:
segments.
User Response:
XPD0239
The CSVQUERY macro returned information that points to the module having more than two
Contact Compuware Customer Support.
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:
User Response:
No load module was found for the specified CSECT in the XTASKLIB dataset.
Check your specified CSECT entry.
Xpediter/TSO Messages
XPD0251
1-7
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:
XPD0252
DDNAME X(8) INCORRECT OR COULD NOT BE ALLOCATED
Module:
ADSRA054 and ADSRA097
Explanation:
User Response:
XPD0253
Check your ddname entry.
ADSRA054
Explanation:
User Response:
A maximum of eight (8) characters is allowed for the dataset name.
Check your ddname entry.
DSNAME LENGTH AS ENTERED IS INCORRECT
Module:
ADSRA054
Explanation:
User Response:
XPD0292
The ddname entered on the LOAD command was in error.
DDNAME LENGTH AS ENTERED IS INCORRECT
Module:
XPD0254
Check your dataset name entry.
A maximum of 44 characters is allowed for the dataset name.
Check your dsname entry.
OPEN FAILED FOR DDNAME X(8)
Module:
ADSRA051, ADSRA097, and ADSRA223
Explanation:
The specified ddname could not be opened.
User Response: Verify that the ddname is present and that it contains the proper attributes. If the problem
reoccurs, contact your internal technical support.
XPD0311
BLDL FAILED FOR MODULE X(8)
Module:
ADSRA051 and ADSRA223
Explanation:
User Response:
XPD0312
The module specified could not be loaded for the reason given.
Check for problems with the dataset.
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:
XPD0317
If the library is otherwise useable, contact your internal technical support.
IDENTIFY FAILED FOR MODULE X(8) WITH A RETURN CODE OF N(2)
Module:
ADSRA495 and ADSRA497
Explanation: A module to be simulated was already loaded and resides in memory. The purpose of the
IDENTIFY is to allow the return of an alternate entry point when a load macro is issued for the given module. A
SET DYNAMIC command must appear before the first CALL command for the simulation to be effective.
User Response:
XPD0318
Contact your internal technical support.
MAXIMUM NUMBER OF DYNAMIC MEMBERS EXCEEDED N(2)
Module:
ADSRA497
Explanation: The maximum number of dynamic members that can be maintained by Xpediter exceeded
Xpediter capacity. Nothing can be done by the programmer to circumvent this problem.
User Response:
Contact your internal technical support.
1-8
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD0319
MAXIMUM NUMBER OF SIMULATED MEMBERS EXCEEDED N(2)
Module:
ADSRA495
Explanation: The maximum number of simulated members which can be maintained by Xpediter exceeded
Xpediter capacity. Nothing can be done by the programmer to circumvent this problem.
User Response:
XPD0322
THE LOAD MODULE DID NOT BEGIN WITH IGZ OR CEE C(8)
Module:
ADSRA322
Explanation:
User Response:
XPD0323
User Response:
Contact your internal technical support.
ADSRA322
Explanation:
properly.
User Response:
The CSECT could not be found in the system module. System library may not be allocated
Check your system library allocation.
EXECUTION OF BEFORE/AFTER COMMAND FAILED
Module:
ADSRA508
Explanation:
User Response:
Before and after breakpoints could not be set for the indicated intercept module.
Contact your internal technical support.
PARSE OF SETUP COMMAND FAILED
Module:
ADSRA508
Explanation:
User Response:
XPD0352
Could not load COBOL system module.
CSECT C(8) WAS NOT LINK EDITED WITH THE SYSTEM MODULE C(8)
Module:
XPD0349
Check the context of your load module entry.
ADSRA322
Explanation:
XPD0348
This module only handles IGZ or CEE modules.
ATTEMPT TO LOAD C(8) FAILED - ABEND CODE = C(4) REASON CODE = X(1)
Module:
XPD0324
Contact your internal technical support.
Parsing failed for the indicated intercept module.
Contact your internal technical support.
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:
XPD0396
Check the content of the specified OFFSET string.
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.
User Response:
XPD0397
Contact your internal technical support.
LOAD MODULE X(8) NOT FOUND FOR X(8) IN XTASKLIB DATA SET
Module:
ADSRA455
Explanation:
User Response:
concatenation.
The specified load module was not found for the given CSECT.
Verify that the module specified is located in one of the datasets found in the XTASKLIB DD
Xpediter/TSO Messages
XPD0407
LOAD MODULE FOR X(8) NOT FOUND
Module:
ADSRA028
Explanation:
XPD0413
1-9
No load module was found for the specified module.
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:
XPD0419
NO ELEMENTARY ITEM FOR X(30) IN X(8)
Module:
ADSRA174
Explanation:
XPD0420
ADSRA174
Explanation:
User Response:
Verify the data item name. If the data item does exist, contact Compuware Customer Support.
ADSRA174
Explanation:
There was insufficient memory for the element display block.
’C(1),’ IS AN INVALID TYPE
Module:
ADSRA175
Explanation:
User Response:
XPD0423
No data item found.
INSUFFICIENT MEMORY FOR EDB
Module:
XPD0422
No elementary item was found for the specified identifier in the module.
CANNOT FIND SOURCE FOR DATA ITEM
Module:
XPD0421
The specified identifier has an excessive record structure depth.
The data conversation failed. The data item has an invalid type and cannot be converted.
Verify the data item type. Contact Compuware Customer Support.
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:
XPD0424
Correct the data and try the command again.
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:
User Response:
The data entered as the value of the field is null.
Include the appropriate data, and try the command again.
1-10
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD0426
ZERO OR NEGATIVE TARGET LENGTH
Module:
ADSRA175
Explanation:
User Response:
XPD0427
ADSRA175
Explanation:
User Response:
Contact your internal technical support immediately.
ADSRA175
Explanation:
User Response:
An internal conversion error was encountered.
Contact your internal technical support immediately.
TARGET POINTER IS NULL
Module:
ADSRA175
Explanation:
User Response:
XPD0430
An internal conversion error was encountered.
SOURCE POINTER IS NULL
Module:
XPD0429
Contact your internal technical support.
SOURCE AND TARGET TYPE = X(1)
Module:
XPD0428
The field, which is to contain the converted data, has a null length.
An internal conversion error was encountered.
Contact your internal technical support immediately.
X(1) IS AN INVALID TARGET TYPE
Module:
ADSRA175
Explanation: The specified target type is invalid. The valid types include Z (zoned), P (packed), or B (binary).
This error is not externally controllable.
User Response:
XPD0438
Contact your internal technical support immediately.
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
XPD0439
X(7) ABEND AT N(4) REASON CODE N(2) [non-LE/370 format]
X(7) COND X(4) ABEND AT N(4) REASON CODE N(2) [LE/370 format]
Module:
ADSRA104, ADSRA105, and ADSRA304
Explanation: This message is generated when a system or user ABEND occurs during Xpediter or user module
execution. It is followed by additional information.
User Response:
command.
XPD0440
If you have difficulty exiting the session, issue the RETEST command, and then the EXIT
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:
User Response:
The data type, as found in the DDIO dataset, is invalid.
Contact your internal technical support.
Xpediter/TSO Messages
XPD0442
NO MEMORY FOR RIM CONTROL BLOCK
Module:
ADSRA187
Explanation:
User Response:
XPD0443
Contact your internal technical support.
ADSRA187
Explanation:
User Response:
An error occurred while Xpediter was attempting to locate an internal control block (the RDB).
Contact your internal technical support.
NO MEMORY FOR RECORD RDB
Module:
ADSRA187
Explanation:
User Response:
XPD0455
Xpediter attempted to obtain memory in which to build an important control block.
NO RDB FOR ITEM TOKEN X(4) IN C(8)
Module:
XPD0444
1-11
Xpediter attempted to obtain memory for an important control block, but was unsuccessful.
Increase the region size and try the test again.
MODULE X(8) CONTAINS ONE OR MORE UNRESOLVED EXTERNAL REFERENCES
Module:
ADSRA222
Explanation: The specified load module was link edited with unresolved external references. Xpediter
recognized this and will try to resolve these external references if the module is called.
User Response: Resolve the external references if Xpediter is unable to do so. If conflicts still exist, contact your
internal technical support.
XPD0460
TROUBLE CLOSING USER FILES
Module:
ADSRA020
Explanation:
User Response:
XPD0461
This message is no longer valid.
None.
XPEDITER FORCE CLOSING OF DDNAME = X(8)
Module:
ADSRA020, ADSRA442
Explanation: During test termination, Xpediter detected that the file allocated to the indicated DDNAME was
left open. Xpediter then attempted to close the file.
User Response:
XPD0468
None.
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:
entered.
XPD0472
ERROR LOADING X(8)
Module:
ADSRA222
Explanation:
User Response:
XPD0473
An invalid command or option relating to the XCOMPILE or XSYMDIR maintenance was
An error was encountered processing the control records in the listed member.
Ensure that the name is a valid member of the library defined by the XTASKLIB DD.
NO RLD ENTRIES X(8)
Module:
ADSRA222
Explanation:
were found.
The module being loaded has been read to the end of file condition and no RLD or CTL records
1-12
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD0498
Check the link edit for errors.
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
FILE.
END OF FILE ENCOUNTERED ON X(8). THE LAST RECORD IS USED FOR ANY LATER ASSIGNS FROM THIS
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:
User Response:
XPD0559
A request to ADSRA558 is unknown.
An internal error has occurred. Contact Compuware Customer Support.
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
Customer Support.
XPD0560
NO JFCB POINTER CREATED IN ADSRA558
Module:
ADSRA558
Explanation:
User Response:
XPD0564
ADSRA028
Explanation:
ADSRA028
Explanation:
No data division entries were listed for the specified module.
NO ITEM FOR INDEX X(30) IN X(8)
Module:
ADSRA028
Explanation:
XPD0568
No index cells were listed in the TGT for the specified module.
NO DATA DIVISION ENTRIES FOR X(8)
Module:
XPD0566
Contact Compuware Customer Support.
NO INDEX CELLS IN TGT FOR X(8)
Module:
XPD0565
JFCB pointer was not created.
No identifier was listed for the specified index.
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:
XPD0570
ERROR UPDATING XDYNAMIC DATA SET MEMBER X(8) TO X(8) RC=N(4)
Module:
ADSRA051
Explanation:
XPD0571
Relink the module or include the library subroutines in the XTASKLIB concatenation.
The STOW macro failed for the specified module.
NOTE LIST NOT SUPPORTED FOR LOAD MODULE X(8)
Module:
ADSRA051
Xpediter/TSO Messages
Explanation:
1-13
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 Customer 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:
User Response:
No dynamic call block was found for the dynamic intercept.
Contact your internal technical support.
XPD0576
ERROR WITH IEWBIND FUNC=SAVEW, (module name) IS A (“PROGRAM OBJECT” or “LOAD MODULE”)
AND THE XDYNAMIC DATASET IS A (“PDS” or “PDSE”).
Module:
ADSRA051
Explanation:
A critical error occurred using the IEWBIND macro.
User Response: If you are using program objects and the XDYNAMIC dataset is a PDS, make the XDYNAMIC
dataset a PDSE. Otherwise contact Compuware Customer 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:
User Response:
Only subpool 0 can be displayed.
Reenter command specifying subpool 0.
1-14
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD0605
SKIP CANNOT BE DELETED FROM MODULE ’C(8),’
Module:
ADSRA058
Explanation:
User Response:
XPD0607
The module has a dummy MOB. Therefore the control blocks for the module are not complete.
’INTERCEPT’ the program to force the completion of Xpediter control blocks.
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:
dynamically.
XPD0678
A SET DYNAMIC must be the first reference to an Assembler module that is going to be called
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/TDODDXCL
command.
XPD0700
XPEDITER INTERNAL TABLE OVERFLOW
Module:
ADSRA227
Explanation:
limit.
User Response:
support.
XPD0732
The Xpediter internal table for resolving external references in library subroutines exceeded its
Relink the module without NCAL to continue testing, and contact your internal technical
MAXIMUM NUMBER OF ENTRIES (100) HAS BEEN EXCEEDED FOR C(8) SET OPTION
Module:
ADSRA055
Explanation: The exception list, which is created and updated by the SET
EXCLUDE/NOCANCEL/DDIGNORE/TDODDXCL 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/TDODDXCL 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
Xpediter/TSO Messages
1-15
Explanation: Review mode logging was activated and logged execution information for the specified routine.
The load module containing this routine cannot be deleted or cancelled.
XPD0745
ATTEMPT TO DELETE MODULE X(8) FAILED WITH RETURN CODE OF N(2)
Module:
ADSRA085
Explanation: The module specified as the positional value of the DELETE command cannot be handled by the
system. The return code from GPR 15 is displayed in hexadecimal format. This module can be statically linked
and cannot be deleted.
XPD0747
X(8) CANNOT BE DELETED - IT IS A SIMULATED MODULE
Module:
ADSRA085
Explanation: The module specified as the positional value of the DELETE command is not a load module. It is
a dummy module that cannot be deleted.
XPD0748
NO DYNAMIC CALL BLOCK FOUND FOR X(8) - CONTACT TECHNICAL SUPPORT
Module:
ADSRA085
Explanation: The DELETE request could not be satisfied because a special Xpediter internal control block could
not be located. The pseudo module name associated with the control block appears in the message.
XPD0768
NO BREAKPOINT TABLE ENTRY FOR OFFSET N(4) IN MODULE X(8)
Module:
ADSRA130 and ADSRA478
Explanation: No matching offset could be found in the statement breakpoint table corresponding to the
interrupt address.
User Response:
support.
XPD0779
The material required to recreate the problem should be forwarded to your internal technical
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:
support.
XPD0804
DIAGNOSE DUMP
Module:
ADSRA148
Explanation:
XPD0805
This problem cannot be circumvented and should be reported to your internal technical
You requested a dump of the Xpediter session. The task abends with a user 3009 ABEND.
OPTION INVALID
Module:
ADSRA148
Explanation:
TRAMON
NOTMON
TRASIM
NOTSIM
TRAXFR
NOTXFR
TRACHK
An invalid action was requested on the DIAGNOSE command. Valid actions include:
-
TRACE MONITOR
Turn Off MONITOR TRACE
TRACE SIMULATE
Turn Off SIMULATE TRACE
TRACE TRANSFER
Turn Off TRANSFER TRACE
TRACE CHECK
1-16
Xpediter/TSO and Xpediter/IMS Messages and Codes
NOTCHK
TRAPRI
NOPRI
BOMB
ADSRANNN
RATON
RATOFF
XPD0806
-
Turn Off CHECK TRACE
TRACE PRIMARY
Turn Off PRIMARY TRACE
ABEND W/U3000
Invoke XPED Module
TRACE XPED CALL
Turn Off XPED CALL TRACE
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:
XPD0820
UNKNOWN TRANSLATOR TYPE = X(10) FOR MODULE X(8) INFORMATION ONLY
Module:
ADSRA252
Explanation:
User Response:
XPD0844
If a problem exists, contact your internal technical support.
An unknown type of translator was found in the IDR records.
This message should be communicated to your internal technical support.
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:
XPD0851
0 WARNING: BLDL FAILED DURING XPEDITER COBOL TRAP PROCESSING FOR MEMBER X(8).
Module:
ADSRA477
Explanation:
User Response:
support.
XPD0852
User Response:
session.
The ddname was not allocated.
The Xpediter/TSO ALLOCATE command can be used to allocate the ddname while in the TSO
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.
MORE THAN 600 MODULES DYNAMICALLY LOADED
Module:
ADSRA051
Explanation:
User Response:
XPD0863
You can use GO to continue. This condition should be reported to your internal technical
ADSRA170
Explanation:
XPD0854
This is an Xpediter internal error and will not affect program execution.
DDNAME X(8) HAS NOT BEEN ALLOCATED
Module:
XPD0853
The file must be freed and the dataset with correct member reallocated.
Too many modules were dynamically loaded.
Contact Compuware Customer Support.
FILE NAME X(8) FILE TYPE, TEXT NOT FOUND
Module:
ADSRA455
Explanation:
The specified file name was not found for the given CALL.
Xpediter/TSO Messages
User Response:
1-17
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:
User Response:
XPD0869
ADSRA284
Explanation:
User Response:
A %CONCAT PANEXEC control card was not found in PECNTL.
Contact your internal technical support.
CANNOT FIND MODULE X(8)
Module:
ADSRA129
Explanation:
User Response:
XPD0872
Contact your internal technical support.
%CONCAT PANEXEC CONTROL CARD NOT FOUND IN PECNTL
Module:
XPD0871
Use of PANEXEC with one of the Xpediter products requires that a PECNTL DD be allocated.
The MCB could not be found for this module. Severe error.
Contact your internal technical support.
X(8) WAS NOT LOADED - MODULES LINKED WITH RMODE ANY CANNOT BE TESTED
Module:
ADSRA051 and ADSRA223
Explanation: The module specified was not loaded by Xpediter because the VS attribute flags in the associated
library directory entry indicated that it had been link edited with RMODE ANY.
User Response:
XPD0873
X(8)
If this message occurs after Xpediter/TSO is installed, contact your internal technical support.
31-BIT ADDRESSING MODE WAS DETECTED AT THE TIME MODULE X(8) WAS RETURNING TO MODULE
Module:
ADSRA274
Explanation: The addressing mode was changed from 24-bit to 31-bit mode by the specified module. Xpediter
changes the mode back to 24-bit and terminates the test instead of returning control to the calling module.
User Response:
XPD0881
If this message occurs after Xpediter/TSO is installed, contact your internal technical support.
MODULE X(8) ALREADY IN MEMORY OR IN LPA LIB, INTERCEPT BYPASSED
Module:
ADSRA497
Explanation: The specified module could not be intercepted under Xpediter control because it was already
resident in real memory or in the link pack area.
User Response:
XPD0884
Contact your internal technical support.
MODULE X(8) COULD NOT BE FOUND IN THE XPEDITER OR USER LIBRARY OR STEPLIB
Module:
ADSRA497
1-18
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation: The CTLCBLII installation default parameter was set to prevent the use of DDIO dataset
information for testing the specified module.
XPD0889
PANEXEC CONTROL CARD DD STATEMENT NOT FOUND
Module:
ADSRA051 and ADSRA223
Explanation:
User Response:
XPD0890
ADSRA405
User Response:
ADSRA405
User Response:
ADSRA405
User Response:
ADSRA553
Explanation:
ADSRA553
Explanation:
ADSRA553
Explanation:
User Response:
ADSRA553
Explanation:
User Response:
The record was not found in the XSYMDIR dataset.
Make sure that it was compiled with Xpediter.
INSUFFICIENT DIRECTORY SPACE IN XCOMPILE
Module:
ADSRA553
User Response:
Reallocate the XCOMPILE dataset with a larger directory block.
INSUFFICIENT VIRTUAL STORAGE FOR STOW
Module:
ADSRA553
User Response:
XPD0900
The second operand is missing for the command.
NO XSYMDIR RECORD
Module:
XPD0899
Recompile with Xpediter and try again.
ADSRA553
Explanation:
XPD0898
XSYMDIR does not contain the record for KAYS support.
CAN’T FIND OPERAND2
Module:
XPD0897
The first operand is missing for the command.
NO XSYMDIR RECORD
Module:
XPD0896
The module name was not located in the XCOMPILE or XSYMDIR datasets.
CAN’T FIND OPERAND1
Module:
XPD0895
The REGION parameter for the TSO session or the batch JOB should be increased.
MODULE NAME INVALID FOR FILE BUFFER
Module:
XPD0894
The REGION parameter for the TSO session or the batch JOB should be increased.
INSUFFICIENT STORAGE FOR FILE BUFFER
Module:
XPD0893
The REGION parameter for the TSO session or the batch JOB should be increased.
INSUFFICIENT STORAGE FOR FILE FDB
Module:
XPD0892
Allocate the file and retry.
INSUFFICIENT STORAGE FOR FILE LRP
Module:
XPD0891
The PANEXEC control card file was not allocated.
The REGION size for the TSO session or the batch JOB should be increased.
XSYMDIR DATASET PERMANENT I/O ERROR
Module:
ADSRA553
Explanation:
Cannot access the XSYMDIR dataset.
Xpediter/TSO Messages
User Response:
XPD0902
ADSRA553
Explanation:
EPILG000.
The program encountered ESTAE EXIT and a dump was taken. Control was transferred to
INVALID OPERAND PAIR
Module:
ADSRA553
Explanation:
XPD0911
Contact your internal technical support.
ESTAE EXIT ENTERED - DUMP TAKEN
Module:
XPD0904
1-19
Invalid operands were entered for the command.
MODULE X(8) HAS OVERLAY FORMAT - NOT SUPPORTED BY XPEDITER
Module:
ADSRA223
Explanation: This is a warning message, but it should be heeded if you want to set breakpoints in any areas
where overlay structures occur.
User Response: The module should be recompiled without overlays in order to permit the use of DDIO
information for testing purposes.
XPD0912
ATTEMPT TO LOAD X(8) FAILED - ABEND CODE = X(3) REASON CODE = N(1)
Module:
ADSRA054 and ADSRA223
Explanation: The specified module could not be loaded for the reason indicated by the ABEND code and the
reason code. Typically, this is a MODULE MARKED NOT EXECUTABLE problem, such as an S706.
XPD0915
MODULE X(8) NOT AUTOMATICALLY CANCELLED - BREAKPOINTS HAVE PREVIOUSLY BEEN SET
Module:
ADSRA274
Explanation: The specified module was not deleted at the time of return to its dynamic VS COBOL II caller.
This is supported in Xpediter/TSO.
User Response:
XPD0916
ACCEPT REJECTED FOR DDNAME X(8) RECORD FORMAT MUST BE EITHER FIXED OR VARIABLE
Module:
ADSRA170
Explanation:
XPD0917
This ddname must have a physical sequential dataset, or the PDS member name must be added.
INPUT ERROR OCCURRED FOR DDNAME X(8)
Module:
ADSRA170
Explanation:
XPD0955
If this message occurs after Xpediter/TSO is installed, contact your internal technical support.
This ddname must have a physical sequential dataset, or the PDS member name must be added.
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:
XPD0966
Issue the RETEST command with a NEWCOPY option.
RETEST WITHOUT NEW COPY CANNOT BE USED WITH REVIEW MODE OPTION
Module:
ADSRA444
Explanation:
User Response:
The user is in a REVIEW mode.
Exit the REVIEW mode and reissue the RETEST command.
1-20
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD0996
BREAKPOINT REMOVED FROM TARGET OF EXECUTE AT ADDRESS xxxxxxxx
Module:
ADSRA104
Explanation: A breakpoint instruction has been encountered on an instruction that is the target of an
EXECUTE instruction. Because this is not supported by Xpediter, the breakpoint has been removed.
User Response: Execution of the application should continue. If you want a breakpoint action to occur on an
EXECUTE instruction, place the breakpoint on the EXECUTE instead of the target.
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 Customer 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, ALL REGISTERS ARE CORRECT EXCEPT GPR 15, GPR
15 WILL POINT TO THE ORIGINAL INTERRUPT ADDRESS
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 session log. If it is not present, you cannot spool (log)
the output from a test.
XPD1004
NO PARMS ENTERED FOR IMS TEST
Module:
XPDRP and XPTSO
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
Xpediter/TSO Messages
1-21
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
Module:
XPDRP and XPTSO
Explanation:
one.
XPD1010
The maximum number of XPED commands that can be entered for a batch or interactive test is
ERROR IN ENVIRONMENT ON XPED COMMAND
Module:
XPDRP and XPTSO
User Response:
XPD1011
For the list of valid environments, consult the Xpediter/TSO and Xpediter/IMS Reference Manual.
ONLY ONE TEST COMMAND ALLOWED IN IMS
Module:
XPDRP and XPTSO
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
Module:
XPDRP and XPTSO
Explanation: The maximum number of INTERCEPT commands that can be entered when testing a transaction
is 50.
XPD1015
INVALID MODULE NAME
Module:
XPDRP and XPTSO
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:
XPD1021
TEST COMMAND ENTERED IN BTS/DLG ENVIRONMENT
Module:
XPTSO
Explanation:
User Response:
XPD1022
Check your spelling on the command.
The TEST command is not valid in the BTS or DLG environments.
Use the INTERCEPT command instead.
TEST MODULE NAME C(8) NOT IN USER LIBRARY
Module:
XPDRP and XPTSO
Explanation:
under TSO).
User Response:
The module to be tested could not be found in the user library (STEPLIB DD in batch; XTASKLIB
If the module is in this library, contact your internal technical support.
1-22
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD1023
INTERCEPT MODULE C(8) NOT IN USER LIBRARY
Module:
XPTSO
Explanation:
STEP).
The module to be intercepted could not be found in the user library (STEPLIB DD on the TEST
User Response:
XPD1024
NO XTASKLIB ALLOCATED
Module:
XPTSO
Explanation:
User Response:
XPD1026
User Response:
There is a severe processing error in Xpediter/TSO.
Contact your internal technical support.
TRANCODE INVALID ON THE TEST COMMAND
Module:
ADSRA516
Explanation:
User Response:
The TRANCODE keyword is not valid on the TEST command.
Use the INTERCEPT command or the LOADM keyword on the TEST command.
MISSING TRANCODE NAME - INTERCEPT COMMAND
Module:
ADSRA507 and ADSRA516
Explanation:
User Response:
this command.
XPD1031
Contact your internal technical support.
XPDRP and XPTSO
Explanation:
XPD1030
The XTASKLIB DD must be allocated for an interactive test.
ENVIRONMENT CAN ONLY BE TSO OR SPF
Module:
XPD1029
If the module is in this library, contact your internal technical support.
The TRANCODE name is required on the INTERCEPT command.
See the Xpediter/TSO and Xpediter/IMS Quick Reference or Reference Manual for more information on
BAD TRANCODE NAME ON INTERCEPT COMMAND
Module:
ADSRA507 and ADSRA516
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:
and 100).
XPD1034
NO PARMS ENTERED ON THE TEST COMMAND
Module:
ADSRA516
Explanation:
User Response:
this command.
XPD1035
The TEST command requires certain parameters to set up the test correctly.
See the Xpediter/TSO and Xpediter/IMS Quick Reference or Reference Manual for more information on
NO PARMS SHOULD BE ENTERED ON THE INTERCEPT COMMAND
Module:
ADSRA516
Explanation:
XPD1036
The PARM string on the TEST command contained an invalid character length (not between 1
The INTERCEPT command should not contain the PARM keyword.
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.
Xpediter/TSO Messages
XPD1037
1-23
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:
XPD1039
The TEST command requires that a program name be one of the parameters entered.
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
Module:
ADSRA507 and ADSRA516
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 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
Module:
ADSRA507 and ADSRA516
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:
conventions.
XPD1048
The load module name entered for the TEST command is invalid under MVS naming
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
Module:
ADSRA507 and ADSRA516
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.
1-24
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD1053
BAD POST SCRIPT NAME ON INTERCEPT COMMAND
Module:
ADSRA507 and ADSRA516
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
Module:
ADSRA507 and ADSRA516
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
Module:
ADSRA507 and ADSRA516
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
Module:
ADSRA507 and 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.
XPD1060
BAD LOAD MODULE NAME ON INTERCEPT COMMAND
Module:
ADSRA507 and ADSRA516
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:
User Response:
XPD1063
A keyword parameter specified on either the TEST or the INTERCEPT command was not valid.
Check to see if this is a spelling error.
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:
User Response:
XPD1065
A DELETE is not valid on the TEST command.
If you are trying to do another test, simply enter another TEST command.
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
Xpediter/TSO Messages
1-25
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
Module:
ADSRA507 and ADSRA516
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
Module:
ADSRA507 and 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.
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
Module:
ADSRA507 and 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.
XPD1072
BAD DB2 SYS-NAME ENTERED ON THE INTERCEPT COMMAND
Module:
ADSRA507 and 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.
XPD1073
DB2 PARMS USED FROM FIRST INTERCEPT COMMAND
Module:
ADSRA507 and ADSRA516
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.
XPD1076 RA516 BAD TRAN DATA ENTERED ON INTERCEPT COMMAND
Module:
ADSRA516
1-26
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation:
The length of the data found in the transaction buffer exceeds the maximum length permitted.
XPD1077 RA516 NO TRAN DATA ENTERED ON INTERCEPT COMMAND
Module:
ADSRA516
Explanation:
XPD1080
No data was found in the transaction buffer.
NO START PARAMETER ENTERED - INTERCEPT COMMAND
Module:
ADSRA507 and ADSRA516
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
Module:
ADSRA507 and ADSRA516
Explanation:
XPD1082
TOO MANY DIGITS ON MAX PARM - INTERCEPT
Module:
ADSRA507 and ADSRA516
Explanation:
XPD1083
A maximum of four digits is allowed for the START keyword on the INTERCEPT command.
A maximum of four digits is allowed for the MAX keyword on the INTERCEPT command.
INVALID DIGITS ON START PARM - INTERCEPT
Module:
ADSRA507 and ADSRA516
Explanation: A nonnumeric character was detected in the value for the START keyword. The value must be a 14 digit number.
XPD1084
INVALID DIGITS ON MAX PARM - INTERCEPT
Module:
ADSRA507 and ADSRA516
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
Module:
ADSRA507 and ADSRA516
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.
XPD1086 RA516 X(6) KEYWORD MISSING ON DB2SP CARD
Module:
ADSRA516
Explanation:
The specified keyword was missing.
XPD1087 RA516 X(6) DB2SP KEYWORD UNDEFINED
Module:
ADSRA516
Explanation:
The specified keyword was invalid.
XPD1088 RA516 X(6) VALUE HAS INVALID LENGTH
Module:
ADSRA516
Explanation:
permitted.
The length of the value specified for the specified keyword exceeds the maximum length
XPD1089 RA516 X(6) VALUE IS MISSING OR INVALID
Module:
ADSRA516
Explanation:
The value specified for the specified keyword was missing or invalid.
XPD1090 - SETTING LETRAP OFF IN AN XPLINK ENVIRONMENT IS NOT RECOMMENDED
Module:
ADSRA109 and ADSRA410
Explanation: When testing in an XPLINK environment with LETRAP OFF, it is possible to experience a S0C4
ABEND if a stack overflow condition occurs when the Guard Page strategy is deployed.
Xpediter/TSO Messages
1-27
User Response: If vulnerable, retest specifying SET LETRAP ON in an initial script, or specify the LE run-time
STACK parameter to increase the size to a value large enough that an overflow won’t occur.
XPD1091
DEFINE LENGTH OF N(4) IS GREATER THAN DATA GROUP N(4) SIZE OF N(4)
Module:
ADSRA286
Explanation:
User Response:
XPD1092
An attempt was made to define an item to a length greater than that available to the data group.
If it is necessary to define such a large field, contact your internal technical support.
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:
XPD1093
If this is a problem, contact your internal technical support.
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:
XPD1095
If this is a problem, contact your internal technical support.
NO BREAKPOINT TABLE FOR MODULE X(8)
Module:
ADSRA434
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.
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:
support.
XPD1103
Recompile the program and test again. If that doesn’t work, contact your internal technical
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:
support.
XPD1104
Recompile the program and test again. If that doesn’t work, contact your internal technical
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).
User Response:
Contact your internal technical support.
1-28
Xpediter/TSO and Xpediter/IMS Messages and Codes
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).
User Response:
XPD1108
X(8)
PCB COUNT EQUALS MODULE INTERFACE COUNT FOR X(30) IN MODULE X(8) PSB PASSED TO MODULE
Module:
ADSRA436
Explanation:
the program.
XPD1109
Contact your internal technical support.
This is an informational message indicating that the PSB appears to contain the proper PCBs for
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 JCLSVCIN, 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.
XPD1112
TRAP BREAKPOINTING ACTIVATION FAILURE.. RC= X(4)
Module:
ADSRA111
Explanation: The attempt to install and activate the optional TRAP breakpointing has failed. SVC
breakpointing, if specified, will be used instead.
User Response:
breakpointing.
XPD1113
SVC BREAKPOINTING IS ACTIVE
Module:
ADSRA111
Explanation:
User Response:
XPD1114
The optional breakpointing SVC has been installed and is active.
None.
CONTROL BLOCK ERROR N(2)
Module:
ADSRA247 and ADSRA367
Explanation:
User Response:
XPD1115
Contact your internal technical support. Processing will continue, if possible, with SVC
An Xpediter internal control block was overlayed.
Contact your internal technical support.
64-BIT REGISTER INTEGRITY HAS BEEN COMPROMISED
Module:
ADSRA102, ADSRA111, ADSRA105, ADSRA302
Explanation: A system error occurred while Xpediter was attempting to save the high-order halves of the 64-bit
registers on a z/architecture machine.
User Response: Contact your internal technical support. If the application runs strictly without 64-bit
resources, execution should continue normally.
Xpediter/TSO Messages
XPD1116
TRAP BREAKPOINTING IS ACTIVE
Module:
ADSRA111
Explanation:
User Response:
XPD1117
1-29
The optional TRAP breakpointing has been installed and is active.
None.
SVC BREAKPOINTING ACTIVATION FAILURE.. RC= X(4)
Module:
ADSRA111
Explanation: The attempt to install and activate the optional SVC breakpointing has failed. The default ESPIE
breakpointing will be used instead.
User Response:
XPD1120
INSUFFICIENT STORAGE TO BUILD CONTROL BLOCK
Module:
ADSRA171, ADSRA223, ADSRA409, ADSRA593, ADSRA609, ADSRA616, and ADSRA617
User Response:
batch test.
XPD1121
ADSRA407
User Response:
batch test.
ADSRA172, ADSRA173, and ADSRA680
Explanation:
User Response:
Contact your internal technical support.
ADSRA217
Explanation:
found.
User Response:
The module was compiled using the CA-OPTIMIZER, but no CA-OPTIMIZER base locators were
Contact your internal technical support.
NO SLS MEMBER FOR X(8)
Module:
ADSRA217
Explanation:
module.
User Response:
control.
XPD1130
An invalid condition was detected when building an Xpediter control block.
NO CA-OPTIMIZER BASE LOCATORS FOR X(8)
Module:
XPD1129
You must increase either the TSO logon size or the REGION parameter on the JCL to run the
INVALID XPEDITER CONTROL BLOCK - B(2)
Module:
XPD1127
You must increase either the TSO logon size or the REGION parameter on the JCL to run the
INSUFFICIENT STORAGE TO BUILD LRP BLOCK
Module:
XPD1125
Contact your internal technical support. Processing will continue with ESPIE breakpointing.
This is an informational message reminding you that there is no DDIO dataset for the specified
If you wish to use Xpediter DDIO debugging facilities, you must compile under Xpediter
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:
User Response:
XPD1135
An Xpediter internal control block was either overlayed or built incorrectly.
Contact your internal technical support.
ERROR ON COPY FOR MEMBER X(8)
Module:
ADSRA051
Explanation:
An attempt to perform a dynamic call intercept on a module failed.
1-30
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD1137
Contact your internal technical support.
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:
XPD1139
If the statement is clearly a valid one, contact your internal technical support.
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.
XPD1143
OPTION
MODULE X(8) HAS BEEN COMPILED WITH THE OPTIMIZE COMPILER OPTION OR INLINE COMPILER
Module:
ADSRA420
Explanation: There are certain limitations on testing programs compiled with the OPTIMIZE compiler option
or the INLINE compiler option.
User Response:
restrictions.
XPD1144
Refer to the Xpediter/TSO and Xpediter/IMS PL/I or C User Guide for more information on these
MODULE X(8) HAS BEEN COMPILED WITH THE COBOL OPTIMIZE COMPILER OPTION
Module:
ADSRA193
Explanation: There are certain limitations on testing programs compiled with the COBOL OPTIMIZE compiler
option.
User Response:
restrictions.
Refer to the Xpediter/TSO and Xpediter/IMS COBOL User’s Guide for more information on these
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:
User Response:
restrictions.
XPD1146
Testing programs compiled with the TEST option can give unpredictable results.
Refer to the Xpediter/TSO and Xpediter/IMS COBOL User’s Guide for more information on these
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.
Xpediter/TSO Messages
XPD1149
1-31
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:
XPD1153
If this is not your intention, contact your internal technical support.
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.
XPD1162
CLASS CODE > 255 NOT SUPPORTED BY THIS IMS RELEASE
Module:
ADSIM017
Explanation: An IMS message class number reserved for use by Xpediter/IMS is greater than 255. This class
code is valid for IMS 9.1 and newer, but is invalid if IMS 8.1 or older is used.
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 session 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:
User Response:
XPD1165
If the program is compiled with RES, only one user at a time can execute that program.
Recompiling programs with NORES can resolve the problem.
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.
User Response:
XPD1166
THE NUMBER OF TRANSACTIONS EXCEEDS THE MAXIMUM OF 45.
Module:
ADSIM003
Explanation:
User Response:
XPD1167
Only 45 transactions can be selected for an Xpediter/IMS test.
Drop some of the transactions on the Setup panel.
GETMAIN FAILED FOR USER SEGMENT WORK AREA.
Module:
ADSIM003
Explanation:
User Response:
XPD1168
Contact your internal technical support.
An attempt to get storage for work areas failed.
Try increasing the TSO logon size.
GETMAIN FAILED FOR CLASS WORK AREA.
Module:
ADSIM003
Explanation:
User Response:
An attempt to get storage for work areas failed.
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. TRAN = X(8), PSB = X(8)
Module:
ADSIM003
1-32
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation: A system or user ABEND occurred while the Xpediter/IMS validation BMP was active. User ABEND
codes are in decimal format.
User Response:
Support.
XPD1170
THE PSB IS LOCKED OR MARKED NON-SCHEDULABLE.
Module:
ADSIM003
Explanation:
User Response:
XPD1171
User Response:
Restart the database and retry the test.
ADSIM003
Explanation:
User Response:
The transaction code to be tested is stopped, locked, or cannot be scheduled.
Restart the transaction code and retry the test.
THE TRANSACTION NAME ENTERED IS NOT DEFINED TO IMS.
Module:
ADSIM003
Explanation:
User Response:
The transaction specified on the test panel is not defined to this control region.
Verify that the transaction code is spelled correctly and the IMS region ID is correct.
THE PSB NAME ENTERED IS NOT DEFINED TO IMS.
Module:
ADSIM003
Explanation:
User Response:
XPD1175
One of the databases used by this PSB is stopped.
THE TRANCODE IS MARKED AS STOPPED, LOCKED, OR NON-SCHEDULABLE.
Module:
XPD1174
Restart the PSB and retry the test.
ADSIM003
Explanation:
XPD1173
The PSB associated with the transaction code to be tested is stopped or locked.
A DATABASE USED BY THIS PSB IS STOPPED.
Module:
XPD1172
If the reason for the ABEND is not apparent from the code, contact Compuware Customer
The PSB associated with this test is not defined in this control region.
Verify that the PSB libraries are correct and the PSB GEN has been done.
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
Customer Support.
XPD1176
IN AN MPP TEST THE PSB HAS NO TRANSACTIONS.
Module:
ADSIM003
Explanation:
User Response:
Support.
XPD1177
ADSIM003
User Response:
Make sure the IMS GEN was done and the correct program was specified on the panel.
AN XPEDITER INTERNAL ERROR HAS OCCURRED.
Module:
ADSIM003
User Response:
XPD1179
If a valid PSB or trancode was entered on the Setup panel, contact Compuware Customer
IN AN IFP TEST THE PSB HAS NO TRANSACTION DEFINED.
Module:
XPD1178
The Xpediter test could not find a valid PSB or transaction to test.
Contact Compuware Customer Support.
IN AN MPP OR IFP TEST, THIS PSB REQUIRES A TRANCODE.
Module:
ADSIM003
Xpediter/TSO Messages
1-33
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:
User Response:
XPD1182
ADSIM003
Explanation:
User Response:
Try using the BMP or IFP option.
ADSIM003
Explanation:
User Response:
All available classes used for testing an MPP program are in use.
Try later or have the Xpediter installer increase the number of classes.
TRANSACTION X(43) IS CURRENTLY IN USE.
Module:
ADSIM003
Explanation:
User Response:
sessions.
XPD1185
As generated, this PSB cannot be run as an MPP.
NO CLASS AVAILABLE FOR THIS MPP TEST.
Module:
XPD1184
Use either IFP or MPP to test.
THIS BMP OR IFP PSB CANNOT BE RUN AS AN MPP.
Module:
XPD1183
As generated, this PSB cannot be run as a BMP.
The named transaction is currently in use by another Xpediter/IMS test session.
Try later. The INTER command on the Setup panel will show the current Xpediter/IMS test
THE INFORMATIONAL ENQUE FAILED. CONTACT TECHNICAL SUPPORT.
Module:
ADSIM003
Explanation:
User Response:
There is an internal problem in Xpediter/IMS.
Contact Compuware Customer Support.
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 Customer Support.
XPD1187
XPEDITER INTERNAL ERROR - INVALID RETURN CODE FROM IMS EXIT.
Module:
ADSIM003
User Response:
Contact Compuware Customer Support.
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 Customer Support.
1-34
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD1189
THE ENQ TO SERIALIZE THE XPEDITER BMP FAILED. PLEASE TRY AGAIN.
Module:
ADSIM003
Explanation:
User Response:
XPD1190
Another user can be starting an Xpediter/IMS test and the setup BMP is in use.
Try starting the test again. If the error persists, contact Compuware Customer Support.
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:
XPD1199
THERE HAS BEEN A PARSING ERROR - CONTACT TECHNICAL SUPPORT.
Module:
ADSIM003
Explanation:
User Response:
XPD1200
The PARM string passed to Xpediter/IMS is not in the correct format.
Check the PARM strings as installed before contacting Compuware Customer Support.
THE RESTART OF X(5) X(8) FAILED. STATUS = X(2)
Module:
ADSIM003
Explanation:
User Response:
XPD1201
Contact your internal technical support if the problem cannot be corrected at the user site.
A restart of the named IMS entity (i.e., TRAN...) failed. The IMS status code is given.
Contact your internal technical support.
A CONVERSATIONAL TRANSACTION IS NOT ALLOWED IN A BMP TEST.
Module:
ADSIM003
Explanation:
User Response:
This transaction is generated as Conversational (SPA was specified on the TRANSACT macro).
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 Customer Support.
XPD1203
PROCESSING ENDED DUE TO ATTENTION INTERRUPT.
Module:
ADSIM002
Explanation:
message.
XPD1204
The Xpediter/IMS test was ended when the attention key was hit. This is an informational
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.
Xpediter/TSO Messages
XPD1205
1-35
ABEND OCCURRED DURING PROCESSING
Module:
ADSIM002
Explanation:
User Response:
Support.
The IMS region ended with a system or user ABEND. User ABEND codes are in decimal format.
If the reason for the ABEND is not apparent from the code, contact Compuware Customer
XPD1206
A NON-BLANK STATUS CODE OF X(2) OCCURRED DURING /RSTART PROCESSING. THE INTERNAL CODE
WAS N(3).
Module:
ADSIM003
Explanation:
User Response:
command.
XPD1207
XPBTBTSE
Explanation:
User Response:
User Response:
User Response:
The module should be recompiled without overlays for testing purposes.
XPBTBTSE
Explanation:
User Response:
An OPEN failed for the XDYNAMIC ddname.
Verify that the XDYNAMIC ddname is available.
READ FAILURE FOR DDNAME XXXXXXXX
Module:
XPBTBTSE
Explanation:
User Response:
Xpediter/TSO was unable to read the specified ddname.
Contact your internal technical support.
WRITE FAILURE FOR DDNAME XDYNAMIC
Module:
XPBTBTSE
Explanation:
User Response:
Xpediter/TSO was unable to write to the XDYNAMIC ddname.
Contact your internal technical support.
INSUFFICIENT DIRECTORY BLOCKS FOR XDYNAMIC
Module:
XPBTBTSE
User Response:
XPD1215
Xpediter/TSO does not support overlay format.
UNABLE TO OPEN DDNAME XDYNAMIC
Module:
XPD1214
Contact your internal technical support.
XPBTBTSE
Explanation:
XPD1213
The load module specified was not found in the allocated library.
LOAD MODULE IN OVERLAY FORMAT - NOT SUPPORTED BY XPEDITER/TSO
Module:
XPD1212
Make sure that the ddname specified is available.
XPBTBTSE
Explanation:
XPD1210
An OPEN failed for the ddname specified.
LOAD MODULE XXXXXX NOT FOUND
Module:
XPD1209
If your terminal is hung in response mode, try to free it by entering the IMS /RSTART
UNABLE TO OPEN DDNAME XXXXXXXX
Module:
XPD1208
Xpediter is unable to RSTART the terminal associated with the IMS transaction.
Reallocate XDYNAMIC with increased number of directory blocks.
INSUFFICIENT MEMORY FOR BUFFER
Module:
XPBTBTSE
User Response:
The REGION parameter for the TSO session or the batch JOB should be increased.
1-36
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD1216
XXXXXXXX MUST BE ALLOCATED TO SUPPORT BLOCKSIZE XXXXX
Module:
XPBTBTSE
Explanation:
User Response:
XPD1217
XPBTBTSE
User Response:
XPBTBTSE
User Response:
XPBTBTSE
User Response:
XPBTBTSE
User Response:
XPBTBTSE
User Response:
Contact Compuware Customer Support.
DFSMS BINDER ERROR FUNC=
Module:
XPBTBTSE
User Response:
XPD1223
Contact Compuware Customer Support.
- ERROR - GETMAIN FAILURE FOR BINDER GETBUF FUNCTION
Module:
XPD1222
Contact Compuware Customer Support.
- ERROR - IEWBIND MODULE COULD NOT BE LOCATED BY XPEDITER
Module:
XPD1221
Contact Compuware Customer Support.
- ERROR - OPERATING SYSTEM NOT AT CORRECT DFSMS/MVS LEVEL
Module:
XPD1220
Contact Compuware Customer Support.
- ERROR - BINDER INVOKED FROM WITHIN USER EXIT
Module:
XPD1219
Reallocate the ddname specified with an increased blocksize.
ASSEMBLER MACRO ISITMGD FAILED OR IS NOT SUPPORTED ON SYSTEM
Module:
XPD1218
The ddname must have a blocksize greater than or equal to the blocksize specified.
None.
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).
User Response:
XPD1228
THE FOLLOWING VARIABLE HAS BEEN TRUNCATED TO 126 CHARACTERS: X(255)
Module:
ADSRA614
Explanation:
names.
User Response:
XPD1229
Contact your internal technical support.
Any name greater than 126 characters is truncated. This can create unintentional duplicate
One solution is to rename to retain uniqueness.
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:
XPD1231
This condition should not occur and should be reported to your internal technical support.
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.
Xpediter/TSO Messages
XPD1232
1-37
(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:
XPD1233
The breakpoints can be restored if valid OP codes are found at the original offsets.
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
Module:
ADSRA268 and ADSRA494
Explanation:
XPD1236
CANCEL REQUEST BY X(8) IGNORED - NO PRIOR DYNAMIC CALL OF X(8)
Module:
ADSRA268 and ADSRA494
Explanation:
cancelled.
XPD1240
The cancel of the previously loaded dynamic module was performed as requested.
A cancel was requested for a module which was either not called dynamically or was previously
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:
User Response:
XPD1244
A system ABEND was caused by insufficient memory.
The test should be reinitiated with a larger region or address space.
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.
User Response:
XPD1246
Contact your internal technical support.
NO INCORE JFCB FOR X(8)
Module:
ADSRA222
Explanation:
USERLIB.
User Response:
There was an I/O operation error in the JOB file control block accessing the XTASKLIB or
Contact your internal technical support.
1-38
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD1247
RECURSIVE ABEND CONDITION ENCOUNTERED - NOTIFY TECHNICAL SUPPORT
Module:
ADSRA105 and ADSRA304
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:
XPD1250
The information in the session log should be given to your internal technical support.
MESSAGE NUMBER N(4) NOT AVAILABLE
Module:
ADSRA125
Explanation: Xpediter was unable to obtain the message text, for the specified message number, from the
message module.
User Response:
XPD1251
RUN.
IMS INTERCEPT IS NOT AVAILABLE. ENSURE XPEDITER INTERCEPT INSTALL JOB, JCLIMSLR, HAS BEEN
Module:
ADSIM017
Explanation:
User Response:
XPD1252
JCLIMSLR must be run after each IPL of your system.
Contact your internal technical support.
PC ROUTINE ABENDED.
Module:
ADSIM017
Explanation:
User Response:
XPD1253
Contact Compuware Customer Support.
There was an unrecoverable error in Xpediter’s IMS intercept PC.
Contact Compuware Customer Support.
XPEDITER TRANCODE SWITCHING INACTIVE.
Module:
ADSIM017
Explanation: Xpediter’s IMS PC intercept is installed, but is “inactive.” JCLIMSLR must be run with
PARM=ACTIVATE.
User Response:
XPD1254
Contact your internal technical support.
UNKNOWN IMS SUBSYSTEM NAME.
Module:
ADSIM017
Explanation: Xpediter’s IMS PC intercept was not initialized with the IMS subsystem being tested. Either
specify the correct IMS subsystem name, or run JCLIMSLR with PARM=DEACTIVATE, modify the control cards to
include the desired IMS subsystem name, and run JCLIMSLR with PARM=ACTIVATE.
User Response:
XPD1255
HANDSHAKE ALREADY DONE IN ADDRESS SPACE.
Module:
ADSIM017
User Response:
XPD1256
Contact your internal technical support.
Contact Compuware Customer Support.
STORAGE OBTAIN FAILED.
Module:
ADSIM017
Explanation:
The REGION allocated to your TSO ID is insufficient.
User Response: Increase the REGION allocated to your TSO ID and try again. If the problem persists, contact
Compuware Customer Support.
XPD1257
FORCE/ACTIVATE SINCE HANDSHAKE.
Module:
ADSIM017
User Response:
XPD1258
Contact Compuware Customer Support.
NO HANDSHAKE DONE IN ADDRESS SPACE.
Module:
ADSIM017
Xpediter/TSO Messages
User Response:
XPD1259
ADSIM017
User Response:
Contact Compuware Customer Support.
COMMIT FAILED. NO RESERVED TRANCODES.
Module:
ADSIM017
User Response:
XPD1261
Contact Compuware Customer Support.
HANDSHAKE DONE BY ANOTHER TASK.
Module:
XPD1260
1-39
Contact Compuware Customer Support.
RESERVE FAILED. ALL TARGET TRANCODES ARE BUSY.
Module:
ADSIM017
Explanation:
All Xpediter IMS pseudo transaction codes are disabled or busy.
User Response: Try again later or contact the individual(s) responsible for Xpediter/IMS and have them
increase the available number of Xpediter/IMS pseudo transactions and include the new set in the JCLIMSLR
intercept install JCL.
XPD1262
ELIMINATE FAILED. TARGET TRANCODE UNKNOWN.
Module:
ADSIM017
User Response:
XPD1263
ELIMINATE FAILED. TARGET TRANCODE USED BY ANOTHER TASK.
Module:
ADSIM017
User Response:
XPD1264
ADSIM017
User Response:
Contact Compuware Customer Support.
INVALID TRANCODE NAME.
Module:
ADSIM017
User Response:
XPD1266
Contact Compuware Customer Support.
UNEXPECTED RETURN CODE FOR /DISPLAY TRANSACTION COMMAND.
Module:
XPD1265
Contact Compuware Customer Support.
Specify a valid transaction code name.
TARGET TRANCODE UNDEFINED TO IMS.
Module:
ADSIM017
Explanation: The selected Xpediter pseudo transaction is not defined to IMS. (Xpediter pseudo transactions
usually start with XPED followed by a four digit number, e.g. XPED0001.)
User Response: Contact the individual(s) responsible for Xpediter/IMS and have them ensure that the Xpediter
pseudo transactions are defined to the desired IMS subsystem.
XPD1267
UNEXPECTED RETURN CODE FOR /DISPLAY TRANSACTION QCNT CMD.
Module:
ADSIM017
Explanation:
handled.
User Response:
XPD1268
When issuing the above command, Xpediter encountered a return code that could not be
Contact Compuware Customer Support.
INVALID TRANCODE NAME (QCNT).
Module:
ADSIM017
Explanation: While issuing the /DISPLAY transaction QCNT CMD, it was discovered that the transaction name
is invalid.
User Response: Specify the correct transaction code name to be displayed. If the problem persists, contact
Compuware Customer Support.
1-40
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD1269
/ASSIGN TRANCODE FAILED.
Module:
ADSIM017
Explanation:
User Response:
XPD1270
Attempt to assign a dummy transaction code failed on the local LPAR.
Contact Compuware Customer Support.
response-type RECEIVED FROM LPAR lparname
Module:
ADSIM019
Explanation: response-type can be NEGATIVE RESPONSE or POSITIVE RESPONSE. lparname is the name of the
LPAR that provided the response. NEGATIVE RESPONSE indicates that there was a problem with the HCI on
LPAR lparname. Processing continues.
User Response: Review the HCI configuration information supplied at Xpediter/TSO installation and correct as
necessary. Also ensure that the HCI specified is active on LPAR lparname. If these don’t resolve the issue, contact
Compuware Customer Support.
XPD1271
IMS INTERCEPT IS NOT AVAILABLE.
Module:
ADSIM019
Explanation:
User Response:
XPD1272
Run program XPIMSTLT to install and activate Xpediter/IMS intercept.
SYSTEM RELEASE LEVEL LESS THAN OS 390.
Module:
ADSIM019
Explanation:
User Response:
XPD1273
The Xpediter/IMS intercept is not active on this LPAR.
IMS cross-LPAR support requires a minimum operating system level of OS 390.
None.
IMS SUBSYSTEM NOT DEFINED AS AN IMSPLEX TO XPIMSTLR.
Module:
ADSIM019
Explanation: The request received was for an IMS subsystem that is not defined as a member of an IMS Shared
Queue in the XPIMSTLR control cards.
User Response:
necessary.
XPD1274
Review the control cards used as input to the XPIMSTLR program and correct them as
TOO MANY LPARS DEFINED IN IMSPLEX.
Module:
ADSIM019
Explanation: IMS Shared Queue support is limited to ten LPARs. More than that have been defined in the
control cards used as input to the XPIMSTLR program.
User Response:
necessary.
XPD1275
Review the control cards used as input to the XPIMSTLR program and correct them as
THIS LPAR NOT DEFINED DURING INSTALL.
Module:
ADSIM019
Explanation: The current LPAR is not defined as part of an IMS Shared Queue environment in the control cards
used as input to the XPIMSTLR program.
User Response:
necessary.
XPD1276
Review the control cards used as input to the XPIMSTLR program and correct them as
LPAR lparname NOT DEFINED DURING INSTALL.
Module:
ADSIM019
Explanation: The LPAR lparname was not defined in the HCI configuration information supplied at
Xpediter/TSO installation.
User Response: Review the HCI configuration information supplied at Xpediter/TSO installation and correct it
as necessary.
Xpediter/TSO Messages
XPD1277
1-41
LPAR lparname NOT RESPONDING.
Module:
ADSIM019
Explanation:
An attempt to contact LPAR lparname has timed-out. This message can result if an LPAR is down.
User Response: If the LPAR is active, review the LPAR data supplied in the HCI configuration information
specified at Xpediter/TSO installation and correct it as necessary. If this does not resolve the issue, contact
Compuware Customer Support.
XPD1290
EXECUTION CANNOT BE RESUMED, THE ESPIE RECOVERY EXIT HAS BEEN TURNED OFF. MEMBER= X(8),
MODULE= X(8)
Module:
ADSRA129
Explanation: Execution of the application module could not be continued subsequent to Xpediter processing.
The Xpediter ESPIE and the Xpediter SVC recovery exits have been disabled.
User Response: Remove the command SET ESPIE OFF from your initial script, or, if your site has the optional
Xpediter SVC breakpointing installed, add to your initial script the commands SET SVCBP ON and SET USVC
### (where ### is the SVC number that was assigned to Xpediter during installation).
XPD1316
ADSIS316 - MULTI-BATCH STAGING FILE OPEN FAILED.
Module:
ADSIS316
Explanation:
User Response:
XPD1316
ADSIS316
Explanation:
User Response:
The utility requires update access to the file that contains the Multi-Batch records.
Ensure update access is provided to the file that contains the Multi-Batch records.
ADSIS316 - NO PARM PASSED.
Module:
ADSIS316
User Response:
XPD1316
Ensure the file is properly allocated and initialized.
ADSIS316 - NO UPDATE ACCESS TO MULTI-BATCH FILE.
Module:
XPD1316
The utility was unable to open the file that contains the Multi-Batch records.
Contact Compuware Customer Support.
ADSIS316 - TABLE OVERLOW (> 5000 RECS) RUN AGAIN
Module:
ADSIS316
Explanation: When the utility is run, obsolete Xpediter/Eclipse records are deleted. This message indicates that
more than 5000 obsolete Xpediter/Eclipse records were encountered. The first 5000 were deleted, but the utility
must be run again to delete the remaining obsolete records.
User Response:
XPD1316
ADSIS316 - MULTI-BATCH INTERCEPT NOT INSTALLED.
Module:
ADSIS316
User Response:
XPD1316
ADSIS316
Explanation:
User Response:
The utility was unable to read from or write to the file that contains the Multi-Batch records.
Ensure the file is properly allocated and initialized.
ADSIS316 - GETMAIN FOR KEY HOLD AREA FAILED.
Module:
ADSIS316
User Response:
XPD1316
Contact Compuware Customer Support.
ADSIS316 - MULTI-BATCH FILE I/O ERROR.
Module:
XPD1316
Run the utility again to delete the remaining obsolete records.
Increase the REGION size for the job and run it again.
ADSIS316 - INVALID PARM VALUE (NOT G, B OR S).
Module:
ADSIS316
User Response:
Contact Compuware Customer Support.
1-42
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD1316
ADSIS316 - INVALID PARM LENGTH.
Module:
ADSIS316
User Response:
XPD1316
ADSIS316 - INVALID PARM ADDRESS.
Module:
ADSIS316
User Response:
XPD1316
ADSIS316
Explanation:
ADSIS316
Explanation:
ADSRA136
Explanation:
User Response:
User Response:
Check your reference manual.
ADSRA136
Explanation:
User Response:
A review execution pause was requested with the attention key.
None.
DATE/TIME OPTION HAS BEEN DISABLED - BY DEFAULT
Module:
ADSRA194
Explanation:
User Response:
Checking for a date/time mismatch has been disabled.
None.
SECURITY CHECK FAILED FOR <language-type> LANGUAGE
Module:
ADSRA194
Explanation:
not licensed.
User Response:
language.
XPD1942
The command is valid only when review mode is in effect.
REVIEW PROCESSING INTERRUPTED BY ATTENTION
Module:
XPD1941
Check the command syntax.
ADSRA136
Explanation:
XPD1940
The parameter is not valid for revision mode.
COMMAND REJECTED - REVIEW MODE NOT IN EFFECT
Module:
XPD1365
Informational message that indicates that there nnnn obsolete Xpediter/Eclipse records deleted.
INVALID PARAMETER FOR REVIEW MODE
Module:
XPD1362
Informational message that indicates that there were no obsolete Xpediter/Eclipse records.
ADSIS316 - nnnn RECORDS OF TYPE G DELETED.
Module:
XPD1360
Contact Compuware Customer Support.
ADSIS316 - NO RECORDS TO DELETE.
Module:
XPD1316
Contact Compuware Customer Support.
An attempt was made to access the DDIO file for a member of a language type for which you are
Contact your internal technical support if you believe you are licensed for the specified
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.
User Response:
XPD1943
None.
PLEASE COMPILE WITH CURRENT CSS FOR FULL NESTED COBOL SUPPORT
Module:
ADSRA194
Xpediter/TSO Messages
1-43
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.
User Response:
XPD1944
None.
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:
XPD1945
None. This message is informational only.
ADSRA194 CSS SHARED DIRECTORY HAS ALLOCATED > 32767 DSNAMES
Explanation:
User Response:
smaller units.
There is a limitation of 32,767 dataset names for DDIO/source libraries.
Eliminate some DDIO/source dataset names via combination or by breaking the test case into
XPD2100
THE COMBINED CSECT SIZES HAVE EXCEEDED THE LOAD MODULE LENGTH VALUE CONTAINED IN THE
CDE EXTENT LIST
Module:
ADSRA218 and ADSRA219
Explanation: The combined CSECT sizes have exceeded the size of the load module. Continued processing
could lead to the building of incorrect control blocks and possible storage corruption.
User Response:
XPD2210
Contact your internal technical support.
PL/I OPT MODULE WAS PRELOADED OR IS IN PROTECTED STORAGE - CANNOT RESET ESPIE OR ESTAE
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 - CANNOT TURN TRAP OFF AS
REQUESTED
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.
XPD2213
CEE SPIE OPTION WAS FORCED TO ON
Module:
ADSRA221
Explanation: Xpediter expects the LE TRAP option to be TRAP(ON,SPIE). Xpediter has found
TRAP(ON,NOSPIE) and has forced TRAP(ON,SPIE).
User Response:
XPD2214
None.
LE ENVIRONMENT RECOGNIZED
Module:
ADSRA221
1-44
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation:
User Response:
XPD2215
None.
LE ENVIRONMENT HAS NOT BEEN RECOGNIZED AND THE LE ROUTINES HAVE NOT BEEN ESTABLISHED
Module:
ADSRA221
Explanation:
User Response:
XPD2222
LE module CEEBINIT was found.
LE module CEEBINIT was not found.
Add the LE runtime libraries to your SETUP.
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.
XPD2520
MAXIMUM NUMBER OF DDIO FILES ALLOCATED
Module:
ADSRA252, ADSRA253
Explanation:
User Response:
XPD3000
The maximum number of DDIO files are currently allocated.
Exit Xpediter/TSO to dynamically unallocate all DDIO files.
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).
User Response:
XPD3001
None.
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 ABENDAID LEAID must be installed as an LE abnormal termination exit.
User Response:
XPD3002
Refer to the Language Environment (LE) section of Compuware’s ABEND-AID Installation Guide.
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:
XPD3003
If ABEND-AID is installed at your site, ensure that it has been activated.
PASSING mmmmmmmm DDIO INFO TO aaaaaaaa RELEASE vvrr
Module:
ADSRA311
Explanation: This message is informational. It indicates the source member and the release of SNAPAID or
LEAID being used for an AA SNAP command.
User Response:
XPD3030
None.
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:
User Response:
The field being defined must not overlap the data group boundary.
None.
Xpediter/TSO Messages
XPD3032
DEFINE LENGTH OF ’,X(4),’ IS GREATER
Module:
ADSRA286
Explanation:
User Response:
XPD3035
This message is no longer valid.
None.
INSUFFICIENT MEMORY FOR X(21)
Module:
ADSRA436
Explanation:
User Response:
XPD3051
1-45
No storage can be allocated for the element display block.
Increase the REGION size for the TSO logon or batch JOB.
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.
User Response:
XPD3052
ALLOCATION OF GPR BUFFER FAILED
Module:
ADSRA217
Explanation:
User Response:
XPD3067
User Response:
User Response:
This message is no longer valid.
None.
NO CAPEX BASE LOCATORS FOR ’C(8)’
Module:
ADSRA217
Explanation:
User Response:
This message is no longer valid.
None.
ATTEMPT TO LOAD ’C(8)’ FAILED -
Module:
ADSRA308
Explanation:
User Response:
Because Test Case Facility is obsolete, this message is no longer valid.
None.
TCF FUNCTION: ’C(4)’ FAILED
Module:
ADSRA308
Explanation:
User Response:
XPD3083
None.
ADSRA217
Explanation:
XPD3082
To browse a dataset, you must enter the member name as well as the name of the dataset.
NO BLI FOR OFFSET ’X(4)’ IN ’C(8)’
Module:
XPD3081
Contact your internal technical support.
ADSRA407
Explanation:
XPD3073
An attempt to allocate memory failed for the GPR buffer.
TO BROWSE PDS - ENTER LIB AND MEMBER
Module:
XPD3072
Contact your internal technical support.
Because Test Case Facility is obsolete, this message is no longer valid.
None.
LOOKUP FOR ’C(44)’ FAILED
Module:
ADSRA308
Explanation:
User Response:
Because Test Case Facility is obsolete, this message is no longer valid.
None.
1-46
Xpediter/TSO and Xpediter/IMS Messages and Codes
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
Explanation:
User Response:
XPD3650
ADSRA365
Explanation:
User Response:
User Response:
A GEN was previously performed on this statement.
None.
DELETE PREVIOUSLY PERFORMED FOR EXEC
Module:
ADSRA365
Explanation:
User Response:
A DELETE GEN was previously performed on this statement.
None.
NUMBER IN INSERT NOT NUMERIC C(8)
Module:
ADSRA370
Explanation:
User Response:
XPD3701
None.
ADSRA365
Explanation:
XPD3700
The GEN command is only allowed on EXPANDABLE statements.
GEN PREVIOUSLY PERFORMED FOR EXEC
Module:
XPD3652
None.
STATEMENT IS NOT EXPANDABLE
Module:
XPD3651
This message is no longer valid.
You attempted to insert a line using a line number that is not numeric.
Check the listing for a valid line number. This is probably a typographical error.
MISSED NUMBER IN INSERT COMMAND C(8)
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:
XPD3702
INSERTED LINE MORE THAN 61 BYTES C(8)
Module:
ADSRA370
Explanation:
XPD3703
Add the line number and resubmit.
An inserted line cannot exceed 61 bytes.
INSERTED LINE NUMBER NOT FOUND IN C(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.
XPD3704
COMMAND PERMITTED ONLY ON CODE LINE
Module:
ADSRA370
Explanation:
User Response:
The INSERT command is allowed only for a code line.
Retry the INSERT command on a code line.
Xpediter/TSO Messages
XPD3705
1-47
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.
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.
User Response:
XPD3801
NO MATCH ON EXTERNAL NAME: xxxxxxxx USING TOKEN: xxxxxxxx
Module:
ADSRA380 and ADSRA394
Explanation:
User Response:
XPD3860
Contact your internal technical support.
External CSECT name was not found using indicated CSS Token.
Contact your internal technical support.
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:
Multiple modules.
Explanation:
User Response:
XPD3871
ADSRA387
Explanation:
User Response:
A valid verb matching the token cannot be found in the CSS CLIST.
Contact your internal technical support.
NO BREAKPOINTS FOUND FOR NEXT COMMAND - MODULE X(8)
Module:
ADSRA387
Explanation:
User Response:
XPD3873
Increase the REGION size and try again.
INVALID TOKEN IN CSS CLIST - N(4) - X(30)
Module:
XPD3872
An attempt to acquire additional storage failed.
An attempt to resolve breakpoints for the NEXT command failed.
Contact your internal technical support.
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.
User Response:
XPD3874
Contact your internal technical support.
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.
1-48
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD3880
INSUFFICIENT STORAGE TO BUILD STATEMENT NUMBER TABLE FOR X(8)
Module:
ADSRA388, ADSRA389, and ADSRA608
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:
User Response:
XPD3882
An error was found building the SNT. Xpediter encountered a problem with the source listing.
Contact your internal technical support.
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.
User Response:
XPD3883
Contact your internal technical support.
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.
User Response:
XPD3884
INVALID STATEMENT NUMBER IN SOURCE. SLPDLLN# = N(4)
Module:
ADSRA388
Explanation:
User Response:
XPD3885
Contact your internal technical support.
ADSRA388
Explanation:
User Response:
Xpediter found an invalid definition line in the DMAP.
Contact your internal technical support.
UNABLE TO RETRIEVE THE CSS COLUMN TABLE. CSS RC=N(4)
Module:
ADSRA388
Explanation:
table (SNT).
User Response:
XPD3887
The indicated source line has an invalid external number.
INVALID DATA IN DMAP RECORD. SLPDMDEF=N(4); TOKEN=N(4)
Module:
XPD3886
Contact your internal technical support.
There was a failure in the CSS Column Table that was needed to create the statement number
Contact your internal technical support.
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.
User Response:
XPD3920
INVALID TOKEN IN CSS CLIST - N(4) - X(30) - X(8)
Module:
ADSRA392
Explanation:
User Response:
XPD3930
None.
A valid verb matching the token cannot be found in the CSS CLIST.
Contact your internal technical support.
INSUFFICIENT STORAGE TO BUILD PROCEDURE HIERARCHY TABLE FOR X(8)
Module:
ADSRA393
Xpediter/TSO Messages
1-49
Explanation: Xpediter attempted to obtain memory for the Procedure Hierarchy Table, but there was not
enough memory.
User Response:
XPD3931
SEVERE ERROR OCCURRED DURING LINE NUMBER CONVERSION:
Module:
ADSRA393
Explanation:
numbers.
User Response:
XPD3932
Increase the region size and try again.
A severe error occurred in the conversion of internal statement numbers to external statement
Contact your internal technical support.
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.
User Response:
XPD3933
Contact your internal technical support.
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.
User Response:
XPD3934
Contact your internal technical support.
ASSOCIATED VALUES: SRBFSEXT = N(4) SRBFSINT = N(4)
Module:
ADSRA393
Explanation: This message gives associated hexadecimal values relating to the preceding message which should
be of assistance in locating the failing source statement.
User Response:
XPD3940
VARIABLE OPTIMIZED OUT/NOT REFERENCED USING TOKEN: xxxxxxxx
Module:
ADSRA394
Explanation:
User Response:
retest.
XPD3960
Contact your internal technical support.
Unable to display variable because it was not referenced or has been optimized out.
If desired variable has been referenced in your program, recompile without optimization and
ERROR BUILDING VARIABLE REFERENCE TABLE - SEE LOG
Module:
ADSRA396
Explanation:
User Response:
An error occurred when trying to retrieve the PL/I Variable Reference Table.
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:
XPD3963
Recompile using the correct parameter.
GETMAIN FAILED FOR THE VARIABLE REFERENCE TABLE
Module:
ADSRA396
Explanation:
memory.
Xpediter attempted to obtain memory for the Variable Reference Table, but there is not enough
1-50
Xpediter/TSO and Xpediter/IMS Messages and Codes
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:
User Response:
The CSS libraries installed are not compatible with the current version of Xpediter/TSO.
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:
User Response:
XPD3970
The CSS libraries installed are not compatible with the current version of Xpediter/TSO.
Make sure that the correct version of CSS is used.
A GETMAIN FOR N(4) HEX BYTES FAILED. SEE LOG.
Module:
ADSRA340, ADSRA387, ADSRA397, and ADSRA621
Explanation: An attempt to allocate memory for the Xpediter breakpoint table or Unicode Conversion services
failed.
User Response:
XPD3971
A WORKAREA GETMAIN FAILURE OCCURRED FOR N(4) HEX BYTES OF STORAGE.
Module:
ADSRA397
Explanation:
User Response:
XPD4020
Increase the REGION size and try again.
An attempt to get storage for work areas failed.
Try logging on with a larger REGION size.
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:
XPD4021
STATEMENT NUMBER NOT FOUND IN MODULE
Module:
ADSRA402
Explanation:
XPD4022
ADSRA402
Explanation:
ADSRA403
Explanation:
ADSRA402
Explanation:
Onetime breakpoints are not allowed on lines already containing a before breakpoint.
SPECIFIED EXECUTION MAX HAS BEEN REACHED
Module:
ADSRA403
Explanation:
XPD4032
Execution has paused at a breakpoint set by a ONETIME or RUNTO command.
ONETIME/RUNTO NOT PERMITTED - BEFORE BREAKPOINT EXISTS
Module:
XPD4029
Breakpoints are not permitted on lines that are for display only.
ONETIME BREAKPOINT ENCOUNTERED
Module:
XPD4025
The requested statement number does not exist in this module.
BREAKPOINT NOT PERMITTED FOR DISPLAY ONLY LINE
Module:
XPD4024
If the statement is clearly a valid one, contact your internal technical support.
The maximum breakpoint execution count has been reached.
PAUSE REQUESTED WITH ATTENTION/PA1 KEY
Module:
ADSRA403
Xpediter/TSO Messages
Explanation:
XPD4037
ADSRA403
Explanation:
User Response:
A maximum breakpoint execution count has been reached and cannot be exceeded.
Reset breakpoint execution count.
BREAKPOINT WITHOUT ACTION INDICATOR
Module:
ADSRA403
Explanation:
XPD4039
A pause of the execution was requested by pressing the attention key.
CANNOT EXCEED SPECIFIED EXECUTION MAX
Module:
XPD4038
1-51
An ABEND or GOBACK processing is in progress.
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 - text message RPERRRET=nn RPERRCD=nnnn
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
08
12
16
20
24
28
32
36
40
48
52
-
MISSING DDNAME/DD CARD
RECORD NOT FOUND - UNABLE TO PROCESS
INVALID REPOSITORY DATASET
INVALID RPIO PARMLIST - NO VALID REQUEST SPECIFIED
I/O ERROR, RPERRCD = RPLRTNCD+RPLERRCD
OPEN ERROR, RPERRCD CONTAINS ACB ERROR FLAG
REPOSITORY ENQUEUE FAILED
LOGIC ERROR BUILDING MULTI-PART REC
LOGIC ERROR, UPDATE FOUND DUPLICATE TIMESTAMP
LOGIC ERROR, SEGMENT NOT FOUND WHILE UPDATING
LOGIC ERROR - UPDATING, REC LVL BAD
REPOSITORY DOWNLEVEL RELEASE
User Response: For RPERRRET = 04 through 12, correct the error and retry. Ensure that the repository file was
created and initialized correctly and that it was properly allocated through the Xpediter setup panels or in the
JCL (if a Batch test). For codes 16 through 52, contact Compuware Customer 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:
XPD4043
REPOSITORY REC FOR <CSECT> DEBUG=<OPTION> RETRIEVED FOR HIGHLIGHTING
Module:
ADSRA433
Explanation:
indicated.
XPD4050
If RPERRCD is not = 8 (8 = Not found), contact Compuware Customer Support.
The CCHILITE command succeeded in retrieving a repository record with the DEBUG type
LOAD MODULE NOT FOUND FOR SOURCE NAME
Module:
ADSRA405
Explanation:
This message is no longer valid.
1-52
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD4120
None.
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:
User Response:
XPD4122
Check command syntax and try again.
RETEST INVALID IN THIS ENVIRONMENT
Module:
ADSRA412
Explanation:
XPD4123
When parsing the command issued, an extraneous keyword was found.
The RETEST command is not valid in a Dialog, DB2, or IMS message region environment.
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:
XPD4142
COMMAND NOT PERMITTED FOR MODULE WITHOUT SOURCE
Module:
ADSRA414
Explanation:
User Response:
XPD4145
The data name specified in the DISPLAY command cannot be found in the current module.
The specified command is valid only when there is available source for the module.
None.
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, and 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
Xpediter/TSO Messages
1-53
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
Module:
ADSRA353, ADSRA612, ADSRA688
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 ******
Module:
ADSRA353, ADSRA612, ADSRA688
Explanation:
messages.
User Response:
XPD4149
This line of text is designed as an attention-getter to alert the user to other, more complex error
None.
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.
User Response:
XPD4150
None.
BASE LOCATOR NOT INITIALIZED
Module:
ADSRA439 and ADSRA459
Explanation: There was a failure in constructing the element display block (EDB) for the specified data. Base
locator cells were not initialized.
User Response:
XPD4151
Contact your internal technical support.
NO IDENTIFIER NAME LOCATED
Module:
ADSRA623
Explanation:
No data information was found for the specified data name.
XPD4156 TGT ADDRESS FOR PROGRAM <MODULE> IS INVALID, ADDRESS = <ADDRESS>
Module:
ADSRA246
Explanation:
User Response:
XPD4170
ADSRA221 and ADSRA417
Explanation:
ADSRA417
Explanation:
User Response:
The specified source listing cannot be found in the allocated DDIO dataset.
Check to make sure that the correct DDIO is allocated. Recompile the program and try again.
X(3) APPLICATION MODULE NOT FOUND IN USER LIBRARY
Module:
ADSRA417
Explanation:
User Response:
XPD4173
This is an Xpediter default.
NO SOURCE LISTING DATA SET MEMBER FOR X(8)
Module:
XPD4172
Contact your internal technical support.
CEE COBOL TRAP OPTION WAS FORCED TO OFF
Module:
XPD4171
The SHOW DCB command failed because the COBOL TGT was invalid.
The application module being referenced could not be found in the user library.
If the application is in the user library, contact your internal technical support.
CSECT IS NOT A MAIN PROCEDURE
Module:
ADSRA417
Explanation:
procedure.
In validating the test command parameter, the module found does not represent a main
1-54
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD4174
NO DATE/TIME PRESENT FOR X(9) MODULE
Module:
ADSRA417
Explanation:
User Response:
XPD4175
The module control block (MCB) of the specified module does not have date/time information.
Contact your internal technical support.
EXECUTION OF BEFORE COMMAND FAILED
Module:
ADSRA417
Explanation:
User Response:
XPD4176
Contact your internal technical support.
There was a failure in setting a before breakpoint on a module.
Contact your internal technical support.
PL/I RUNTIME LIBRARIES MUST BE ALLOCATED IN XTASKLIB
Module:
ADSRA221 and ADSRA417
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:
XPD4178
PLIXOPT SPIE AND STAE RESET BY XPEDITER
Module:
XPD4180
ADSRA221
ADSRA221
REQUESTED SOURCE MODULE NOT AVAILABLE
Module:
ADSRA418
Explanation:
User Response:
XPD4181
ADSRA418
Explanation:
User Response:
No data table entry (DTE) can be found for the specified COBOL level 88 data name.
Contact your internal technical support.
DATA DEFINITION NOT FOUND FOR X(64)
Module:
ADSRA418
Explanation:
User Response:
XPD4183
Contact your internal technical support.
DATA DEFINITION INVALID, NOT FOUND OR DUPLICATED
Module:
XPD4182
No SLS member in the DDIO dataset matches the requested source module.
No data table entry (DTE) can be found for the specified data name.
Contact your internal technical support.
ERROR PROCESSING X(38)... MAY BE OPTIMIZED OUT
Module:
ADSRA418
Explanation: An internal error occurred while Xpediter was processing a variable. This can be caused when a
compiler optimizes out a variable, which usually occurs if a variable is declared, but not used.
User Response: If the variable was optimized out, any attempt to reference the variable cannot be successful. If
the variable was not optimized out, contact your internal technical support.
XPD4184
A LABEL IS NOT A VALID VARIABLE NAME
Module:
ADSRA418
Explanation:
XPD4185
The label that is referenced is not valid.
DUPLICATE DATA NAME, QUALIFICATION IS REQUIRED
Module:
ADSRA418
Xpediter/TSO Messages
Explanation:
User Response:
rules.
XPD4186
1-55
The specified data name has a duplicate data name specified in the application program.
Qualify the desired data name. Refer to the User Guide or Reference Manual for qualification
DATA NAME X(64) WAS NOT FOUND
Module:
ADSRA418
Explanation:
User Response:
The specified data name is unknown to the application program.
Contact your internal technical support.
XPD4187 EXPRESSION ERROR (X,4,1,<Return Code>) - C,44,1,<Reason>
Module:
ADSRA418
Explanation: CSS could not locate a variable in the C Language expression for the Return Code (in HEX) and
Reason given.
User Response: Check for errors based on the Reason given. If the error is not apparent, contact Compuware
Customer Support with the Return Code and Reason.
XPD4190
PROCEDURE NAME NOT FOUND IN MODULE SOURCE LISTING
Module:
ADSRA419
Explanation:
User Response:
XPD4191
The procedure name specified in the command is not found in the source module.
Contact your internal technical support.
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:
XPD4192
MODULE NOT FOUND
Module:
ADSRA419
Explanation:
XPD4193
Verify that the correct DDIO file is allocated. Recompile the program and try again.
The specified module cannot be found in the allocated user library.
LOAD OF MODULE C(8) 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:
libraries.
Check your STEPLIB, JOBLIB, or LIBDEF/ISPLLIB concatenations for the proper Code Coverage
XPD4194
ADSRA432 "**********************************************************"
XPD4194
ADSRA432 "
XPD4194
ADSRA432 " XPEDITER/CODE COVERAGE RESULTS ARE BASED, IN PART, ON THE"
XPD4194
ADSRA432 " MAPPING OF PROGRAM SOURCE CODE TO THE COMPILER-GENERATED "
XPD4194
ADSRA432 " MACHINE INSTRUCTIONS EXECUTED. BECAUSE THE RESULTS FOR
"
XPD4194
ADSRA432 " OPTIMIZED PROGRAMS CAN SEEM ILLOGICAL, XPEDITER/CODE
"
XPD4194
ADSRA432 " COVERAGE MAY MAKE CERTAIN INFERENCES, INDICATED BY AN
"
XPD4194
ADSRA432 " ASTERISK (*), IN AN ATTEMPT TO CLARIFY ACTUAL PROGRAM
XPD4194
ADSRA432 " EXECUTION.
XPD4194
ADSRA432 "**********************************************************"
Module:
ADSRA432
---- WARNING ----
"
"
"
1-56
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation: There are certain limitations on testing programs compiled with the COBOL OPTIMIZE compiler
option.
User Response:
restrictions.
XPD4200
Refer to the Xpediter/TSO and Xpediter/IMS COBOL User’s Guide for more information on these
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:
XPD4204
Recompile the program with Xpediter.
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
User Response:
XPD4210
Contact your internal technical support.
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 Customer Support. If they do
not coincide, contact your internal technical support.
XPD4211
THE LANGUAGE PROCESSOR RELEASE USED TO COMPILE = NNNNNN.
Module:
ADSRA194
User Response:
XPD4212
THE LANGUAGE PROCESSOR RELEASE USED TO EXECUTE = NNNNNN.
Module:
ADSRA194
User Response:
XPD4263
Refer to Message XPD4210 for the appropriate user action.
Refer to Message XPD4210 for the appropriate user action.
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.
User Response:
XPD4268
TOO MANY PARAMETERS FOR GO COMMAND
Module:
ADSRA426
Explanation:
User Response:
XPD4290
Contact your internal technical support.
Invalid GO command syntax.
Check the command syntax in the Reference Manual.
TRACE INTERRUPTED BY TERMINAL I/O
Module:
ADSRA429
Xpediter/TSO Messages
Explanation:
User Response:
XPD4301
Continue testing.
ADSRA430
Explanation:
User Response:
An internal error has occurred while executing inserted code.
Contact your internal technical support.
COMMAND NUMBER OUT OF SYNC WITH TABLE IN ADSRA430
Module:
ADSRA430
Explanation:
User Response:
XPD4350
Your program wrote data to the terminal while Xpediter was tracing the program flow.
XPEDITER COMMAND TABLE CANNOT BE FOUND
Module:
XPD4302
1-57
An internal error has occurred while executing inserted code.
Contact your internal technical support.
INSERT NOT ALLOWED - MODULE IN PROTECTED STORAGE
Module:
ADSRA435
Explanation:
The qualified module is in protected storage. An INSERT cannot be performed.
User Response: The requested function cannot be performed if the qualified module resides in protected
storage. Ensure that the requested function is intended for the module being viewed and that access to the
module is available. Generally, the module should be in the test SETUP or XTASKLIB concatenations.
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.
User Response:
XPD4352
None.
STATEMENT DELETED BY COBOL OPTIMIZER
Explanation: The source line in an application did not have underlying machine instructions generated by the
compiler.
User Response:
XPD4353
No breakpoints will be allowed on this line.
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:
XPD4354
INSERT COMMAND IS INVALID IN REVIEW MODE
Explanation:
User Response:
lines.
XPD4355
Lines are not allowed to be inserted once the execution direction has been reversed.
Enter the REVERSE command again to cause execution to resume before attempting to insert
INVALID COMBINATION OF REQUESTS SPECIFIED
Explanation:
User Response:
XPD4356
Reshow the line(s) before attempting to place a breakpoint.
Multiple line commands were entered, two of which are mutually-exclusive.
None.
BLOCK REQUEST NOT PERMITTED WITH NUMBER
Explanation: Line commands can be entered in blocks (i.e., RR – RR) or with a replication factor (i.e., R99), but
not both.
User Response:
XPD4357
None.
BLOCK REQUEST PREVIOUSLY ENTERED IN LINE AREA
Explanation:
User Response:
Multiple block line commands are not allowed on the same line.
None.
1-58
Xpediter/TSO and Xpediter/IMS Messages and Codes
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.
User Response:
XPD4359
None.
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.
XPD4414
COMMAND NUMBER OUT OF SYNC WITH TABLE IN ADSRA441
Module:
ADSRA441
Explanation:
User Response:
XPD4415
An internal error has occurred while passing the command.
Contact your internal technical support.
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.
XPD4420
PSEUDOSOURCE COMMAND NOT ALLOWED AFTER SOURCE HAS BEEN RETRIEVED
Module:
ADSRA632
Explanation: Source information has already been retrieved from a Compuware DDIO file for the specified
module. DDIO-provided source code and pseudo-assembler code generated by Xpediter are mutually exclusive.
User Response: If you wish to use a pseudo-assembler listing instead of the DDIO information, issue the
PSEUDO command before issuing a command which retrieves the DDIO information.
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.
User Response:
XPD4471
None.
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 Customer Support.
XPD4473
OPTION NOT SUPPORTED FOR QUALIFIED MODULE WRITTEN IN C(9,1,<LANG>)
Module:
ADSRA447
Explanation:
User Response:
The SHOW FILES command is invalid for this programming language.
Use the ALC or SHOW ALLOC command instead.
Xpediter/TSO Messages
XPD4474
INVALID SHOW OPTION IN BATCH OR INCLUDE SCRIPT
Module:
ADSRA447
Explanation:
User Response:
XPD4506
1-59
Some SHOW commands cannot be used in batch mode or in an include script.
Use an interactive test or remove the SHOW command from your script.
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:
User Response:
XPD4521
ADSRA452
Explanation:
User Response:
User Response:
User Response:
Two or more consecutive lines have been excluded from the source display.
None.
INVALID MESSAGE LENGTH
Module:
ADSRA631
Explanation:
User Response:
An error has occurred while attempting to issue a message.
Contact customer support.
NO PARAGRAPH ON LINE FOR TRACE BTE ENTRY
Module:
ADSRA456
Explanation:
User Response:
An error has occurred attempting to TRACE a paragraph name.
Contact customer support.
SOURCE INFORMATION NOT FOUND FOR MODULE
Module:
ADSRA456
Explanation:
User Response:
XPD4590
None.
ADSRA631
Explanation:
XPD4563
A single line has been excluded from the source display.
(F,4,1<LINECT>),’LINES NOT DISPLAYED’
Module:
XPD4561
None.
ADSRA631
Explanation:
XPD4524
The bottom of the current source listing has been reached.
1 LINE NOT DISPLAYED
Module:
XPD4523
None.
******BOTTOM OF MODULE******
Module:
XPD4522
The top of the current source listing has been reached.
An internal error has occurred attempting to execute the TRACE command.
Contact customer support.
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.
1-60
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD4592
WHEN NOT ALLOWED - MODULE IN PROTECTED STORAGE
Module:
ADSRA459
Explanation:
The qualified module is in protected storage. A WHEN cannot be performed.
User Response: The requested function cannot be performed if the qualified module resides in protected
storage. Ensure that the requested function is intended for the module being viewed and that access to the
module is available. Generally, the module should be in the test SETUP or XTASKLIB concatenations.
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:
User Response:
XPD4861
The Call Number entered had less than 3 characters.
Enter the Call Number that was supplied by the Compuware Customer Support Representative.
CALL NUMBER LENGTH MAY NOT EXCEED 11 CHARACTERS
Explanation: The length of the Call Number prefix, the hyphen, and the Call Number suffix is greater than 11
characters.
User Response:
XPD4862
Enter the Call Number that was supplied by the Compuware Customer Support Representative.
JFCB WAS NOT FOUND FOR DDNAME, X(8)
Explanation: An attempt was made to retrieve the JFCB of the specified ddname so that the high level node
could be obtained.
User Response:
XPD4863
INVALID PARAMETER, MUST BE T, TAPE, F, OR FTP
Explanation:
Type.
User Response:
XPD4864
User Response:
User Response:
User Response:
None.
A hyphen was encountered without any characters preceding it.
Enter the Call Number that was supplied by the Compuware Customer Support Representative.
The Call Number prefix was greater than 7 characters.
Enter the Call Number that was supplied by the Compuware Customer Support Representative.
CALL NUMBER SUFFIX IS MISSING
Explanation:
User Response:
XPD4868
The successful completion of the JCL creation process has occurred.
CALL NUMBER PREFIX MAY NOT BE > 7 CHARACTERS
Explanation:
XPD4867
Change the incorrect parameter value to either T, TAPE, F, or FTP.
CALL NUMBER PREFIX IS MISSING
Explanation:
XPD4866
While entering the DOCUMENT command, an incorrect parameter was entered for the Transfer
JCL TO RETRIEVE DOCUMENTATION HAS BEEN CREATED
Explanation:
XPD4865
Contact Compuware Customer Support.
There is a space following the hyphen in the Call Number.
Enter the Call Number that was supplied by the Compuware Customer Support Representative.
CALL NUMBER SUFFIX MAY NOT BE > 3 CHARACTERS
Explanation:
User Response:
The Call Number suffix is greater than 3 characters.
Enter the Call Number that was supplied by the Compuware Customer Support Representative.
Xpediter/TSO Messages
XPD4869
TIOT IS NOT AVAILABLE FOR DDNAME, X(8)
Explanation:
User Response:
XPD4870
User Response:
User Response:
User Response:
Contact Compuware Customer Support.
The high level qualifier for the XPDOC dataset is invalid.
Contact Compuware Customer Support.
The values that were entered with the DOCUMENT command passed the edit routines.
None.
THE OPEN FAILED FOR THE XPDOC DATASET
Explanation:
User Response:
XPD4874
An attempt to retrieve the TIOT for the XPDOC dataset failed.
DOCUMENT COMMAND PASSED THE EDIT ROUTINE
Explanation:
XPD4873
Contact Compuware Customer Support.
XPDOC DATASET HIGH LEVEL NODE IS > 8 CHARACTERS
Explanation:
XPD4872
An attempt to retrieve the TIOT for the specified ddname failed.
TIOT ADDRESS IS NOT VALID
Explanation:
XPD4871
1-61
An unsuccessful attempt was made to open the XPDOC dataset.
Contact Compuware Customer Support.
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.
User Response:
XPD4875
Enter the Call Number that was supplied by the Compuware Customer Support Representative.
NOT ENOUGH STORAGE AVAILABLE FOR REQUEST
Explanation:
command.
An unsuccessful attempt was made to get storage during the processing of the DOCUMENT
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 Customer 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:
XPD4877
To free the storage, exit the Xpediter/TSO test.
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:
XPD4878
Change the incorrect parameter value to either B, BOTH, D, DOC, L, or LOG.
LMB CONTROL BLOCK ADDRESS IS INVALID
Explanation:
User Response:
An Xpediter/TSO control block has an invalid address.
Contact Compuware Customer Support.
XPD4879 MCB CONTROL BLOCK ADDRESS IS INVALID
Explanation:
User Response:
XPD4880
An Xpediter/TSO control block has an invalid address.
Contact Compuware Customer Support.
AN OVERFLOW CONDITION HAS OCCURRED ON ONE OF THE INTERNAL COUNTERS
Explanation:
User Response:
A table to hold the names of the requested modules has surpassed its limit.
Contact Compuware Customer Support.
1-62
Xpediter/TSO and Xpediter/IMS Messages and Codes
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.
User Response:
XPD4882
Contact Compuware Customer Support.
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:
XPD4930
LOAD MODULE X(8) IS LINKED AMODE=31 OR RMODE=ANY.
Module:
ADSRA493
Explanation:
User Response:
linked.
XPD4931
Refer to messages associated with XPD4939. There is a problem with the way this program is
ADSRA493
Explanation:
User Response:
linked.
Refer to message XPD4939.
Refer to messages associated with XPD4939. There is a problem with the way this program is
ISSUE THE SHOW MODULES COMMAND TO LIST THE LOAD MODULE AND CSECTS.
Module:
ADSRA493
Explanation:
User Response:
linked.
XPD4933
Refer to message XPD4939.
IT CONTAINS AN OS/VS COBOL MODULE.
Module:
XPD4932
Make sure that the CSS load library is accessible to the Xpediter/TSO test.
Refer to message XPD4939.
Refer to messages associated with XPD4939. There is a problem with the way this program is
***ENTER INPUT DATA FOR ACCEPT FROM SYSIN***
Module:
ADSRA493 and ADSRA494
Explanation: This is a request via the ACCEPT verb, designed to enter data from the terminal for the SYSIN DD.
User Response:
XPD4934
AN OPEN WAS ISSUED TO AN OPEN FILE; UNABLE TO CONTINUE
Module:
ADSRA493 and ADSRA494
Explanation:
User Response:
XPD4935
A request has occurred to open a file which is already open.
Check the program for multiple open statements against the same ddname.
AN ERROR OCCURRED DURING JFCB RETRIEVAL
Module:
ADSRA493 and ADSRA494
Explanation:
User Response:
XPD4936
Enter the input information and press Enter.
Xpediter could not retrieve the JFCB for a ddname.
Contact Compuware Customer Support.
NO FILE ALLOCATION FOR DDNAME X(8)
Module:
ADSRA493
Explanation:
allocated.
Your program is trying to access the named ddname, but that file has not been previously
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
Xpediter/TSO Messages
Explanation:
User Response:
XPD4938
1-63
The PDS member name specified in the allocation of your file does not exist.
Check your file allocations.
***ENTER INPUT RECORD OR/*(AT END) FOR DDNAME INFILE***
Module:
ADSRA493 and ADSRA494
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:
User Response:
XPD4940
Refer to the associated messages. There is a problem with the way this program is linked.
CANCEL REQUEST BY C(8,1<PROGRAM>), SATISFIED-
Module:
ADSRA494
Explanation:
User Response:
XPD4941
OS/VS COBOL does not support AMODE 31 or RMODE ANY.
A COBOL test program issued a CANCEL statement and the function was completed.
None.
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.
User Response:
XPD4942
None.
X(8) NOT ALLOCATED. ENTER GO AFTER ALLOCATING OR IF DYNAMICALLY ALLOCATED
Module:
ADSRA494
Explanation: Your program is trying to access the named ddname, but that file is not allocated. This was the
second attempt to locate the file. Message XPD4936 was generated at the first attempt to locate the file.
User Response: Entering GO at this point will continue without any further attempts to locate the file.
Xpediter assumes that the file will be dynamically allocated or that the user has performed the allocation.
Entering QUIT or EXIT can be used to terminate the test at this point.
XPD4980
CSS ffffffff FUNCTION FAILURE - RETURN CODE: rrrr
Module:
ADSRA498
Explanation:
An internal service has failed.
User Response: If rrrr is 008C or 0090, the region size may be too small to accommodate the service. Otherwise,
contact Compuware Customer Support.
XPD4981
CONFLICTING MODULE SPECIFICATIONS
Module:
ADSRA498
Explanation: An invalid command was entered, in which a variable reference fell outside the scope of the
specified program.
User Response:
XPD4982
Make sure that the specified variable is defined within the qualified program.
UNSUPPORTED DATANAME REFERENCE
Module:
ADSRA498
Explanation:
A specific variable’s occurrence was specified in a command which required only a data name.
User Response: Simplify the notation to just the variable name. For example, if the variable is repeating, as
with an array or OCCURS clause, specify only the element name — not a specific occurrence.
1-64
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD5555
PL/I LIBRARIES ARE PRELOADED OR IN PROTECT
Module:
ADSRA417
Explanation:
User Response:
XPD5691
User Response:
User Response:
Remove all length specifications but one.
The only valid specifications for the BNDRY keyword are DBLWD or PAGE.
None.
INVALID HEX INITIALIZATION DIGIT
Explanation:
User Response:
XPD5694
The parameter indicating the amount of storage to GETMAIN was specified more than once.
BOUNDARY VALUE NOT DBLWD OR PAGE
Explanation:
XPD5693
None.
LENGTH PREVIOUSLY SPECIFIED
Explanation:
XPD5692
This message is no longer valid.
An invalid hexadecimal digit was specified in the INIT parameter.
Use only acceptable digits (0-9, A-F) when specifying hex data.
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:
User Response:
XPD5696
User Response:
User Response:
User Response:
Specify one of the allowable subpools. Subpools greater than 127 are not supported.
No length was specified in the GETMAIN command.
Specify at least a length value when requesting storage.
ADSRA598
Explanation:
User Response:
A SHOW COUNTS command was issued but there are no count breakpoints.
None.
NO WHEN REQUESTS IN EFFECT
Module:
ADSRA598
Explanation:
User Response:
XPD6010
A non-decimal value or number greater than 127 was specified for the SP keyword.
NO COUNT BREAKPOINTS IN EFFECT
Module:
XPD5973
None.
LENGTH OF GETMAIN WAS NOT SPECIFIED
Explanation:
XPD5971
The value for the Address keyword is not a valid register, address, or label.
SUBPOOL SPECIFICATION NOT IN RANGE OF 0 THRU 127
Explanation:
XPD5698
Specify a valid option: LOC=ANY, LOC=ABOVE, or LOC=BELOW.
INVALID REFERENCE FOR RETURN OF ADDRESS
Explanation:
XPD5697
An invalid value was specified for the LOC keyword.
A SHOW WHEN command was issued but there are no WHENs currently active.
None.
RETAIN IMS BREAKPOINTS DISABLED, GETMAIN FOR nnnn BYTES FAILED
Module:
ADSRA529
Explanation: Xpediter attempted to obtain nnnn bytes of storage in order to enable the Retain IMS Breakpoints
feature. This storage was not available. The test proceeds without the Retain IMS Breakpoints feature.
Xpediter/TSO Messages
1-65
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
RETIMSB COMMAND FAILURE: xxxx
Module:
ADSRA529
Explanation: Xpediter is unable to process the retain IMS breakpoint function upon the second or latter
iteration of the IMS MPP test. In the message, xxxx describes the failure. It can be up to 100 characters.
User Response: Examine the Xpediter session log for more data. If the reason for the command failure is not
apparent, contact Compuware Customer Support.
XPD6012
RETIMSB FAILURE LMBNAME=xxxxxxxx MCBNAME=xxxxxxxx MCBBTECT=nnnn XIMS BTECT=nnnn
Module:
ADSRA529
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 session log as well as the DDIO and LOADLIB available and contact Compuware
Customer Support.
XPD6013
RETIMSB FAILURE: XIMS=xxxxxxxx yyyy=xxxxxxxx
Module:
ADSRA529
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.
User Response: Please have the session log as well as the DDIO and LOADLIB available and contact Compuware
Customer Support.
XPD6014
RETIMSB FAILURE: LMB=xxxxxxxx MCB=xxxxxxxx yyyy=xxxxxxxx
Module:
ADSRA529
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.
User Response: Please have the session log as well as the DDIO and LOADLIB available and contact Compuware
Customer Support.
XPD6032
<ABEND> ABEND ENCOUNTERED, ENTER LOG FOR ADDITIONAL DATA
Module:
ADSRA410
Explanation:
User Response:
XPD6033
None.
<ABEND> ABEND ENCOUNTERED, USE “AA SNAP” FOR ADDITIONAL INFORMATION
Module:
ADSRA410
Explanation:
User Response:
XPD6041
None.
None.
None.
BREAKPOINT ADDRESS IS IN PROTECTED STORAGE
Module:
ADSRA604
Explanation:
The qualified module is in protected storage. A breakpoint cannot be set.
User Response: The requested function cannot be performed if the qualified module resides in protected
storage. Ensure that the requested function is intended for the module being viewed and that access to the
module is available. Generally, the module should be in the test SETUP or XTASKLIB concatenations.
XPD6070
SOURCE C(8) HAS CONFLICTING DATE - TIME STAMP
Module:
ADSRA194
Explanation:
User Response:
Relates to XPD6074.
Relates to XPD6074.
1-66
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD6071
*** SOURCE MEMBER mm/dd/yy hh.mm.ss ***
Module:
ADSRA194
Explanation:
User Response:
XPD6072
ADSRA194
Explanation:
User Response:
Relates to XPD6074, date/time of load module.
Relates to XPD6074.
ANY SOURCE REFERENCE TO MODULE C(8) WILL BE REJECTED
Module:
ADSRA194
Explanation:
User Response:
XPD6074
Relates to XPD6074.
*** LOAD MODULE mm/dd/yy hh.mm.ss ***
Module:
XPD6073
Relates to XPD6074, date/time of source member.
Relates to XPD6074, will only occur if DATETIME enforcement is ON.
Relates to XPD6074.
NOTE: 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
Explanation:
XPD6077
Refer to message XPD6070.
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:
XPD6120
Adjust options as required by your site.
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:
User Response:
XPD6125
The command entered is not valid for sourceless debugging.
Refer to the reference manual for a list of valid commands.
INVALID PARAMETER
Module:
ADSRA612
Xpediter/TSO Messages
Explanation:
User Response:
XPD6127
1-67
An invalid parameter was used with the command.
Refer to the Reference Manual and check the command syntax.
LOAD MODULE CANNOT BE FOUND
Module:
ADSRA612
Explanation:
DD.
The module used for qualification cannot be found in the datasets referenced by the XTASKLIB
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:
qualifier.
XPD6129
SKIP MODULE NAME MAY NOT HAVE ADDITIONAL PARAMETERS
Module:
ADSRA612
Explanation:
User Response:
XPD6140
User Response:
User Response:
The cursor is not positioned in the GPREGS display window.
Reposition the cursor and try again.
NO SOURCE STRING FOUND
Module:
ADSRA614
Explanation:
User Response:
The cursor is not positioned at any data identifier.
Reposition the cursor and try again.
NO SOURCE DEFINITION FOUND FOR STRING X(64)
Module:
ADSRA614
Explanation:
The cursor is positioned on a label that is not defined as data.
INVALID ADDRESS STRING FOR PEEK CSR
Module:
ADSRA614
Explanation:
XPD6148
Correct and try again.
ADSRA614
Explanation:
XPD6147
The command entered does not have a matching delimiter.
CURSOR NOT IN GPR FIELD
Module:
XPD6145
Refer to the Reference Manual for valid syntax and try again.
ADSRA614
Explanation:
XPD6144
Invalid SKIP module syntax.
UNBALANCED LITERAL
Module:
XPD6143
A duplicate module name was found in the allocated libraries. Use the load module name as the
The cursor is positioned on an address that does not point to a data area.
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.
XPD6149
X(17) IS AN INVALID ADDRESS FOR PEEK CSR
Module:
ADSRA614
Explanation:
protected.
The 64-bit address specified by the cursor location is not accessible in memory. It is fetch
1-68
Xpediter/TSO and Xpediter/IMS Messages and Codes
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
User Response:
batch test.
XPD6170
You must increase either the TSO logon size or the REGION parameter on the JCL to run the
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:
User Response:
XPD6172
ADSRA617
Explanation:
User Response:
User Response:
User Response:
The base location for the command was omitted.
This field can be an address, a register, a variable, or a variable expression.
INVALID REGISTER NUMBER SPECIFIED
Module:
ADSRA617
Explanation:
User Response:
An invalid register number was entered.
Only the general-purpose registers are allowed: registers 0 through 15.
INVALID ADDRESS OR OFFSET SPECIFIED
Module:
ADSRA617
Explanation:
User Response:
The base location has an incorrect address.
The address may have more than 8 digits or an invalid character, as specified.
NO PREVIOUS USING TO DROP
Module:
ADSRA617
Explanation:
User Response:
XPD6210
An offset can only be used relative to a dsect item name in the format label+offset.
ADSRA617
Explanation:
XPD6178
An offset value is not permitted with this command.
NO ADDRESS, REGISTER OR ADDRESS EXPRESSION SPECIFIED
Module:
XPD6177
Check the user program for the exact spelling.
ADSRA617
Explanation:
XPD6176
An invalid dsect item name was entered on the command.
LABEL NAME MUST IMMEDIATELY PRECEDE + OR -
Module:
XPD6175
Refer to the Xpediter/TSO and Xpediter/IMS Reference Manual to check the command syntax.
INVALID NAME SPECIFIED BY COMMAND
Module:
XPD6173
The USING and DROP commands require additional parameters.
An Xpediter USING was not entered for this DROP.
Specify a SHOW USING command to show what USINGs have been entered.
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.
Xpediter/TSO Messages
1-69
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:
User Response:
XPD6213
Message processing has located an internal message in error.
Contact Compuware Customer Support.
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.
User Response:
XPD6214
INVALID HEX DATA
Module:
ADSRA621
Explanation:
User Response:
XPD6215
None.
The data that was entered does not consist of valid hexadecimal digits.
Hexadecimal digits are 0 through 9 and A through F. Check the value that was entered.
INVALID NUMERIC DATA
Module:
ADSRA621
Explanation: An error was encountered while attempting to move the entered value into the numeric variable.
User Response:
XPD6216
INVALID BINARY DATA
Module:
ADSRA621
Explanation:
User Response:
XPD6230
User Response:
type of data.
This type of variable is not yet supported by Xpediter for display purposes.
Contact customer support to request an enhancement if it is important for you to view this
HEX NOT ALLOWED ON BIT DATA
Module:
ADSRA623
Explanation:
User Response:
type of data.
Xpediter does not currently support doing a hexadecimal display of bit variables.
Contact customer support to request an enhancement if it is important for you to view this
INVALID OFFSET SPECIFIED
Module:
ADSRA625
Explanation:
User Response:
XPD6251
Check the entered value.
ADSRA623
Explanation:
XPD6250
Valid binary data consists of ones and zeros. Blanks cannot be imbedded within the data.
DISPLAY OF X(64) NOT SUPPORTED
Module:
XPD6231
Check the entered value for all numeric digits 0 through 9.
The offset specified is beyond the end of the current module.
Supply an offset in this module or use an absolute address.
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.
1-70
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD6252
NO ACTIVE MODULE LOCATED FOR OFFSET
Module:
ADSRA625
Explanation:
offset.
An offset was entered as a parameter, but there is no module that can be used as a base for the
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:
XPD6254
ADDRESS X(8) LOCATED IN X(8) AT OFFSET X(6)
Module:
ADSRA625
Explanation:
XPD6255
This is the output of the WHEREIS command when an offset was entered as a parameter.
This is the output of the WHEREIS command when an address was entered as the parameter.
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:
XPD6258
This is the output of the WHEREIS command when a label was entered as the parameter.
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:
User Response:
XPD6290
Incorrect syntax was used with the WHEREIS command.
Correct syntax and try again.
BREAKPOINTS ARE NOT ALLOWED ON A TARGET-OF-EXECUTE INSTRUCTION
Module:
ADSRA434, ADSRA435, and ADSRA629
Explanation: A breakpoint command was issued against, or included in its scope, an instruction that is the
target of an execute (EX) instruction.
User Response: Enter the command again, ensuring that the scope of the command does not include any
instructions that are the target of an execute instruction.
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:
XPD6310
ERROR IN INDIRECT ADDRESSING CALCULATION
Module:
ADSRA631
Explanation:
User Response:
XPD6320
Enter the command again with the correct parameter.
An error has occurred during calculation of the indirect address value of the source window.
Contact Compuware Customer Support.
INVALID OFFSET SPECIFIED FOR PSEUDOSOURCE COMMAND
Module:
ADSRA632
Xpediter/TSO Messages
1-71
Explanation: An offset was specified on the PSEUDO command following the module specification. Either the
offset was not within the bounds of the module, or this is the first request to generate pseudo-assembler source
for this module, in which case the offset value is not allowed.
User Response: If this is the first attempt at creating a pseudo-assembler source view for this module in this test
session, don’t specify an offset. Otherwise, make sure the offset is not beyond the length of the module.
XPD6321
PSEUDOSOURCE CANNOT BE REBUILT FOR A MODULE IN WHICH EXECUTION IS PAUSED
Module:
ADSRA632
Explanation: An offset was specified on the PSEUDO command following the module specification. However,
the application is currently stopped at a breakpoint in the specified module. Xpediter is unable to reconstruct
the pseudo-assembler listing for a module which is active.
User Response: All attempts at reconstructing the pseudo assembler view must be requested before execution
reaches the module or after execution has passed through the module. If the reconstruction is being done due to
a data element being considered an instruction, the SET DATA command may be an alternative to allow
execution to continue.
XPD6322
MODULE LIBRARY NOT FOUND
Module:
ADSRA632
Explanation: A module was specified with the PSEUDO command that 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.
XPD6340
DATA ITEM NOT FOUND ON SOURCE LINE
Module:
ADSRA434 and ADSRA623
Explanation:
XPD6341
NO STORAGE FOR COUNT MAX BLOCK
Module:
ADSRA435
Explanation:
User Response:
XPD6360
ADSRA636
Explanation:
The line indicated did not contain code or a data definition.
TYPE OF BLOCK COMMAND NOT ALLOWED ON SPECIFIED LINE
Module:
ADSRA636
Explanation:
User Response:
Block commands must start and end on valid lines, depending on the commands used.
See the Reference Manual for command information.
GT STATEMENT SAME AS CURRENT STATEMENT
Module:
ADSRA636
Explanation:
XPD6364
The line indicated did not contain an instruction. It may be a comment, null line, or continued
COMMAND ONLY PERMITTED ON CODE OR DATA LINE
Module:
XPD6363
Log on with more memory.
ADSRA636
Explanation:
line.
XPD6362
No storage is available for Xpediter to build an internal block.
COMMAND ONLY PERMITTED ON INSTRUCTION LINE
Module:
XPD6361
A PEEK/KEEP was placed on a line which contains no variables, such as a LR instruction.
The GT (GOTO) line command cannot be put on a line with the active arrow.
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.
1-72
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD6370
EXECUTION COUNT MAX MUST BE GREATER THAN COUNT
Module:
ADSRA637
Explanation:
User Response:
XPD6371
ADSRA637
Explanation:
User Response:
User Response:
entered + or -.
Check the digits in the offset field for incorrect hexadecimal digits or for an erroneously
ADSRA639
Explanation:
User Response:
No target for the move was entered, or the information inside the parentheses is incorrect.
Check command syntax.
NULL VALUE SPECIFIED FOR DATA REFERENCE
Module:
ADSRA639
Explanation:
User Response:
The “from” data name is missing.
Check command syntax.
MODULE REFERENCE INVALID
Module:
ADSRA639
Explanation:
User Response:
XPD6396
The (+/-) offset field was incorrect.
INVALID TARGET REFERENCE
Module:
XPD6395
Be sure the COUNT MAX field contains a decimal number.
ADSRA639
Explanation:
XPD6393
The maximum count must be a decimal number of not more than 7 digits.
ERROR ENCOUNTERED DURING EVALUATION OF CALC SUFFIX
Module:
XPD6392
Increase the MAX number.
INVALID COUNT SPECIFIED AS MAXIMUM FOR BREAKPOINT
Module:
XPD6391
The maximum count must be greater than the number of counts displayed.
A module name reference with the “from” data name cannot be found.
If the module name is correct, check the command syntax.
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::MODULENAME:DATA-NAME
XPD6397
MOVE REQUEST FOR MOD WITH DIFFERENT LANGUAGE THAN SOURCE
Module:
ADSRA639
Explanation:
User Response:
XPD6400
Check language of both the “from” field and the target field.
INVALID HEXADECIMAL CHARACTER ENTERED
Module:
ADSRA640
Explanation:
User Response:
XPD6401
Xpediter only allows moves of information between modules of like languages.
The field was typed over by a character that was not 1 through 9 or A through F.
Try again.
INVALID MNEMONIC OPERATION CODE
Module:
ADSRA640
Explanation:
The OPCODE was typed over with an invalid entry.
Xpediter/TSO Messages
XPD6402
DATA IS IN PROTECTED MEMORY
Module:
ADSRA640
Explanation:
XPD6411
ADSRA641
Explanation:
User Response:
The INSERT command cannot be used on the command line.
Use the I line command or use a script.
TOO MANY DIGITS ENTERED FOR GO COMMAND
Module:
ADSRA641
Explanation:
XPD6541
The data that was typed over is in protected storage.
INSERT COMMAND NOT VALID ON COMMAND LINE
Module:
XPD6412
1-73
The maximum number of digits that can be used on the GO n command is 6.
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:
XPD6590
OPERAND SEPARATOR WORD TO NOT FOUND
Module:
ADSRA659
Explanation:
User Response:
XPD6591
Scroll to the desired location by using the scroll commands UP and DOWN.
The Xpediter MOVE command requires the TO keyword to separate the operands.
Place the keyword TO between the operands and try again.
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 generalpurpose register (GPR) or be referred to by a label within the source listing.
User Response:
XPD6592
Make sure that the operand after the TO keyword is a GPR or a data label.
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:
XPD6593
Check the base register and the length of storage obtained for the data item.
NO ADDRESS FOR TARGET DATA ITEM
Module:
ADSRA659
Explanation:
addressable.
An attempt was made with the Xpediter MOVE command to move to an item that is not
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:
XPD6595
Check the length and contents of the literal item and try again.
NUMERIC LITERAL CONTAINS INVALID CHARACTER
Module:
ADSRA659
1-74
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation: The source operand of the Xpediter MOVE command contains a character which is not in the
range of 0 through 9.
User Response:
XPD6596
Refer to the MOVE command section in the Xpediter/TSO and Xpediter/IMS Reference Manual.
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:
User Response:
XPD6599
Check the string for invalid characters.
DBCS LITERAL CONTAINS INVALID DATA
Module:
ADSRA659
Explanation:
User Response:
XPD6610
The hexadecimal string of the source operand contains a character that is not EBCDIC code.
The DBCS string of the source operand contains invalid data.
Check the string for non-DBCS characters.
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:
XPD6621
Refer to the TEST command section in the Xpediter/TSO and Xpediter/IMS Reference Manual.
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
Explanation:
User Response:
XPD6702
This message is no longer valid.
None.
OFFSET KEYWORD NOT ALLOWED IN COBOL MODULE
Module:
ADSRA670
Xpediter/TSO Messages
Explanation:
1-75
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:
Assembler.
User Response:
XPD6705
ADSRA670
Explanation:
modules.
User Response:
User Response:
User Response:
Xpediter was expecting to find a right or left parentheses.
Recheck the command structure.
IMPROPER USE OF CHANGED KEYWORD
Module:
ADSRA673
Explanation:
User Response:
A mixture of class expression and changed keyword was detected.
The CHANGE keyword can only be used with a variable.
EXTRANEOUS PARAMETER
Module:
ADSRA675
Explanation:
User Response:
More information was found on this command than was required.
Check command and retry.
INVALID RANGE
Module:
ADSRA675
Explanation:
User Response:
XPD6770
Check command entry.
ADSRA673
Explanation:
XPD6751
Unbalanced parentheses were entered in the command.
INVALID SEQUENCE OF LOGICAL OPERANDS
Module:
XPD6750
Xpediter does not allow breakpoints to be set on these modules except with the AT command.
ADSRA673
Explanation:
XPD6733
A module name with the first characters of IGZ or ILBO was detected. These are COBOL system
UNBALANCED PARENTHESES
Module:
XPD6732
Remove the plus sign if statement number is desired.
CANNOT SET BREAKPOINT ON COBOL SYSTEM MODULES
Module:
XPD6730
A plus sign was detected, which indicates an offset. Offset and address can only be used in
An invalid statement number was detected after the THRU keyword.
Check statement range.
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.
1-76
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD6780
INVALID SET OPTION
Module:
ADSRA678
Explanation:
User Response:
commands.
XPD6781
Check the spelling or refer to the Xpediter/TSO and Xpediter/IMS Reference Manual for valid SET
INVALID SET OPTION FOR THIS ENVIRONMENT
Module:
ADSRA678
Explanation:
User Response:
XPD6842
An invalid SET command was entered.
The SET command entered cannot be used in a batch environment.
Check the Xpediter/TSO and Xpediter/IMS Reference Manual for uses of specific SET commands.
64-BIT ADDRESSING IS NOT SUPPORTED WHEN LETRAP IS ON
Module:
ADSRA614, ADSRA639, ADSRA684, ADSRA685, ADSRA688, and ADSRA692
Explanation: Validating 64-bit addresses is not supported when Language Environment is controlling the
trapping (LETRAP is ON), because it is possible for an ABEND to occur which could terminate the test session.
User Response:
XPD6920
Retest specifying SET LETRAP OFF in an initial script.
A 64-BIT ADDRESS REQUEST IS INVALID ON A NON Z/ARCHITECTURE MACHINE
Module:
ADSRA692
Explanation:
A request was made on a non z/architecture machine to use a 64-bit address.
User Response: Remove the 64-bit address reference from the request. It may be in the form of an explicit 64bit address (99999999_99999999) or an indirect address request (!).
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.
User Response:
XPD6932
None.
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.
User Response:
XPD6933
INVALID LENGTH RECEIVED FOR LITERAL
Module:
ADSRA693
Explanation:
User Response:
XPD6934
Remove some of the characters from the search item.
ADSRA693
Explanation:
User Response:
Only string finds can be used with the memory panels.
Use quotes around the item used for search.
OVERTYPE AREA IS IN PROTECTED STORAGE
Module:
ADSRA696
Explanation:
User Response:
XPD7010
The string cannot exceed 48 characters.
PARAMETER INVALID FOR THIS ENVIRONMENT
Module:
XPD6960
None.
The area you wish to type over may be write protected but not fetch protected.
You cannot type over write protected areas.
GETMAIN FAILED FOR FIND CONTROL BLOCK
Module:
ADSRA701
Xpediter/TSO Messages
Explanation:
User Response:
XPD7011
Try logging on with a larger region size.
ADSRA701
Explanation:
User Response:
An invalid sequence of data-name qualifiers was detected.
Correct and retry command.
NO PREVIOUS FIND ISSUED
Module:
ADSRA701
Explanation:
User Response:
XPD7030
GETMAIN for 700 bytes failed.
INVALID SEQUENCE OF QUALIFICATION PARAMETERS
Module:
XPD7012
1-77
An F * command was issued without a prior FIND command having successfully completed.
None.
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.
User Response:
XPD7031
C(7,1,<COUNT>),”,C(12,2,<TYPE>),’FOUND’
Module:
ADSRA703
Explanation:
User Response:
XPD7032
User Response:
None.
ADSRA704
Explanation:
User Response:
The enhanced FIND option was not enabled when the program was compiled.
Refer to the Compuware Shared Services User/Reference Guide for information on enhanced FIND.
GETMAIN FAILED FOR THE CSV TABLE - FIND TERMINATED
Module:
ADSRA704
Explanation:
User Response:
GETMAIN failure occurred.
Log on with a larger region size.
SNT/VSTMT MISMATCH. FIND TERMINATED. SEE LOG.
Module:
ADSRA704
Explanation:
User Response:
XPD7043
This is the number of finds qualified for the selected groups.
PROGRAM COMPILED WITHOUT ENHANCED FIND
Module:
XPD7042
None.
ADSRA703
Explanation:
XPD7041
This is the resulting number of COBOL Structure Verbs found.
C(7,1,<COUNT>),
Module:
XPD7040
None.
An error was detected while processing enhanced FIND tables.
See the session log for more information.
A MISMATCH OCCURRED BETWEEN SNT RECORDS AND THE VERB RECORDS.
Module:
ADSRA704
Explanation:
User Response:
A statement number in the VERB table could not be matched to a statement number table entry.
Contact your internal technical support.
1-78
Xpediter/TSO and Xpediter/IMS Messages and Codes
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:
XPD7054W
Supply the appropriate INPUT/OUTPUT record and rebuild the XOPTIONS dataset.
NO DLI OPTIONS RECORD FOUND
Module:
ADSRA705
Explanation:
User Response:
XPD7055W
When processing the XOPTIONS dataset, no record was found for the DLI options.
Supply the appropriate DLI options record and rebuild the XOPTIONS dataset.
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:
User Response:
XPD7200I
Module:
CWXTSVCI
User Response:
Module:
None.
CWXTSVCI
User Response:
message(s).
Module:
CWXTSVCI has completed and successfully performed the requested function.
CWXTSVCI PROCESSING TERMINATED DUE TO ERROR.
Explanation:
XPD7203I
None.
CWXTSVCI
User Response:
Module:
CWXTSVCI has started the process of installing Xpediter/TSO and Xpediter/IMS SVC.
CWXTSVCI PROCESSING SUCCESSFULLY COMPLETED.
Explanation:
XPD7202E
Check the command in the Xpediter/TSO and Xpediter/IMS Reference Manual.
XPEDITER/TSO AND XPEDITER/IMS VV.RR.MM SVC INSTALLATION PROCESS HAS STARTED.
Explanation:
XPD7201I
The string for a string FIND was not found in the command.
CWXTSVCI encountered an error while performing the requested function.
Check the job log for prior XPD72xxE message(s) and follow the user response for those
CWXTSVCI PARM=”xxxxxxxxxxxxxxxxxxxxxxxxx”.
CWXTSVCI
Xpediter/TSO Messages
Explanation:
1-79
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
Module:
CWXTSVC START ADDR=X’nnnnnnnn’, LENGTH=X’nnnnnnnn’.
CWXTSVCI
Explanation: This message is provided for documentation and debugging purposes. It displays the starting
address of CWXTSVC and its length.
User Response:
personnel.
XPD7210E
Module:
None, but this information may be requested by Xpediter/TSO and Xpediter/IMS support
CWXTSVCI PARM “SVC=” MUST BE SPECIFIED.
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 step
entitled “Install SVC Breakpointing (Optional)” in the Xpediter/TSO and Xpediter/IMS Installation Guide.
XPD7211E
Module:
CWXTSVCI PARM “SVC=” MUST BE A THREE DIGIT NUMERIC FIELD: 200-255.
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).
User Response: Fix the PARM for CWXTSVCI and resubmit the job. For more information refer to the step
entitled “Install SVC Breakpointing (Optional)” in the Xpediter/TSO and Xpediter/IMS Installation Guide.
XPD7212E
Module:
CWXTSVCI PARM LENGTH IS NOT VALID FOR SELECTED OPTION.
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).
User Response: Fix the PARM for CWXTSVCI and resubmit the job. For more information refer to the step
entitled “Install SVC Breakpointing (Optional)” in the Xpediter/TSO and Xpediter/IMS Installation Guide.
XPD7213E
Module:
CWXTSVCI PARM OPTION IS NOT VALID, MUST BE INSTALL, REPLACE, OR DEINSTALL.
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).
User Response: Fix the PARM for CWXTSVCI and resubmit the job. For more information refer to the step
entitled “Install SVC Breakpointing (Optional)” in the Xpediter/TSO and Xpediter/IMS Installation Guide.
XPD7214E
Module:
CWXTSVCI PARM “WAIT=” MUST BE SPECIFIED.
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).
User Response: Fix the PARM for CWXTSVCI and resubmit the job. For more information refer to the step
entitled “Install SVC Breakpointing (Optional)” in the Xpediter/TSO and Xpediter/IMS Installation Guide.
XPD7215E
Module:
CWXTSVCI PARM “WAIT=” MUST BE EITHER “Y” OR “N”.
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).
1-80
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response: Fix the PARM for CWXTSVCI and resubmit the job. For more information refer to the step
entitled “Install SVC Breakpointing (Optional)” in the Xpediter/TSO and Xpediter/IMS Installation Guide.
XPD7230E
Module:
NUCLKUP BYNAME FAILED FOR “IGCERROR”.
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 Customer 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
Module:
NUCLKUP BYADDR FAILED FOR SPECIFIED SVC NUMBER.
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 Customer 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
Customer Support Representative.
XPD7232E
Module:
SVC ENTRY TO BE REPLACED IS NOT “IGCERROR” OR “CWXTSVC”.
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 inhouse written routine. Try selecting a new SVC number. If it is not already in use, contact Compuware Customer
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 Customer 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 Customer 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 Customer 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 Customer 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 Customer Support Representative.
XPD7233E
Module:
SVC ENTRY TO BE DEINSTALLED OR REPLACED IS NOT “CWXTSVC”.
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
Customer 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 Customer 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 Customer 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
Customer Support Representative.
XPD7240E
Module:
ENQ FAILED FOR “SYSZSVC” “TABLE” AND WAIT=Y WAS SPECIFIED.
CWXTSVCI
Explanation:
MVS.
An error occurred while CWXTSVCI was trying to obtain exclusive control of the SVC table for
User Response: Try resubmitting the job. If the error persists, contact Compuware Customer Support. Please
supply your MVS or OS/390 release to the Compuware Customer Support Representative.
Xpediter/TSO Messages
XPD7241E
Module:
1-81
ENQ FAILED FOR “SYSZSVC” “TABLE” AND WAIT=N WAS SPECIFIED.
CWXTSVCI
Explanation:
MVS.
An error occurred while CWXTSVCI was trying to obtain exclusive control of the SVC table for
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 Customer Support. Please supply your MVS or OS/390 release to the Compuware
Customer Support Representative.
XPD7242E
Module:
ENQ FAILED FOR “COMPUWAR” “XPEDITER.CWXTSVC” AND WAIT=Y WAS SPECIFIED.
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 Customer Support. Please
supply your MVS or OS/390 release to the Compuware Customer Support Representative.
XPD7243E
Module:
ENQ FAILED FOR “COMPUWAR” “XPEDITER.CWXTSVC” AND WAIT=N WAS SPECIFIED.
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 Customer Support. Please supply your MVS or OS/390 release to the Compuware
Customer Support Representative.
XPD7250E
Module:
“SVCUPDTE DELETE” FAILED.
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
Customer 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 Customer Support Representative.
XPD7251E
Module:
“SVCUPDTE REPLACE” FAILED.
CWXTSVCI
Explanation: While processing an INSTALL or REPLACE function, the SVCUPDTE REPLACE failed for the SVC
number.
User Response: Contact Compuware Customer 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
Customer Support Representative.
XPD7252E
Module:
SVC NUMBER CANNOT BE INSTALLED, IT IS ALREADY “CWXTSVC”.
CWXTSVCI
Explanation:
CWXTSVC.
While processing an INSTALL function, it was discovered that the requested SVC is already
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 Customer 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 Customer Support Representative.
XPD7260E
Module:
CSA START ADDRESS AND SVC START ADDRESS DO NOT MATCH.
CWXTSVCI
Explanation: While processing a DEINSTALL or REPLACE function, it was discovered that an inconsistency
existed in CWXTSVC.
1-82
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response: Contact Compuware Customer 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
Customer Support Representative.
XPD7261E
Module:
ERROR FREEING EXISTING SVC.
CWXTSVCI
Explanation: While processing a DEINSTALL or REPLACE function, an error occurred in the FREEMAIN of the
previous CWXTSVC.
User Response: Contact Compuware Customer 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
Customer Support Representative.
XPD7270E
Module:
LOAD OF “CWXTSVC” FROM STEPLIB FAILED.
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 Customer 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 Customer Support Representative.
XPD7271E
Module:
GETMAIN FAILED FOR “CWXTSVC”.
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 Customer 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 Customer Support Representative.
XPD7272E
Module:
“CWXTSVC” IS NOT AT OFFSET 4 FROM SVC ENTRY.
CWXTSVCI
Explanation: While processing an INSTALL or REPLACE function, it was discovered that an inconsistency
existed in CWXTSVC.
User Response: Contact Compuware Customer Support. In addition, please supply your MVS or OS/390 release
to the Compuware Customer Support Representative.
XPD7273E
Module:
“CWXTSVC” IS AT A HIGHER RELEASE THAN “CWXTSVCI”.
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 Customer
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 Customer Support Representative.
XPD7274E
Module:
“CWXTSVC” WAS NOT LINKED AC=1.
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 Customer Support. Please supply your MVS or
OS/390 release to the Compuware Customer Support Representative.
Xpediter/TSO Messages
XPD7275E
1-83
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 Customer
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 Customer 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 Customer 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
Customer Support Representative.
XPD7431
IDENTIFIER NOT FOUND
Module:
ADSRA753
Explanation:
obsolete.
User Response:
XPD7432
ADSRA753
Explanation:
obsolete.
User Response:
User Response:
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
None.
COMMA IS NOT PERMITTED EXCEPT TO SEPARATE
Module:
ADSRA753
Explanation:
obsolete.
User Response:
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
None.
PARANTHESIS ARE IMBALANCED
Module:
ADSRA753
Explanation:
obsolete.
User Response:
XPD7436
None.
ADSRA753
Explanation:
obsolete.
XPD7435
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
OPERATOR NOT PRECEDED BY IDENTIFIER, A NUMERIC
Module:
XPD7434
None.
C(64), IS NOT DEFINED AS NUMERIC
Module:
XPD7433
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
None.
COMPUTE COMMAND REQUIRES “=” AND NONE FOUND
Module:
ADSRA753
Explanation:
obsolete.
User Response:
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
None.
1-84
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD7446
DIVIDE HAS PRODUCED A REMAINDER OF:
Module:
ADSRA754
Explanation:
obsolete.
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
User Response:
XPD7447
None.
EMBEDDED PARANTHETICAL LEVEL(S) SKIPPED
Module:
ADSRA754
Explanation:
obsolete.
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
User Response:
XPD7448
None.
EVALUATION COMPLETE FOR LEVEL ’,(B,2),’
Module:
ADSRA754
Explanation:
obsolete.
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
User Response:
XPD7449
None.
CURRENT LEVEL IS ’,(B,2),’
Module:
ADSRA754
Explanation:
obsolete.
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
User Response:
XPD7450
None.
EVALUATION WORK TABLE.......AT
Module:
ADSRA754
Explanation:
obsolete.
Because the COMPUTE command has not been incorporated for Xpediter, this message is now
User Response:
None.
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:
XPD7521
’,C(79),’
Module:
ADSRA752
Explanation:
obsolete.
User Response:
XPD7522
Because the COMPUTE command has not been incorporated for Xpediter, this message is
None.
INVALID (OR UNDEFINED) OPERAND’,C(48),’
Module:
ADSRA752
Explanation:
obsolete.
User Response:
XPD7523
You cannot do a KEEP or PEEK on this line.
Because the COMPUTE command has not been incorporated for Xpediter, this message is
None.
NUMERIC LITERAL IS NOT PERMITTED BEFORE”=”
Module:
ADSRA752
Xpediter/TSO Messages
Explanation:
obsolete.
User Response:
XPD7524
User Response:
Because the COMPUTE command has not been incorporated for Xpediter, this message is
None.
’,C(30),’ IS UNDEFINED
Module:
ADSRA752
Explanation:
obsolete.
User Response:
Because the COMPUTE command has not been incorporated for Xpediter, this message is
None.
’C(64)’ IS NOT A NUMERIC FIELD....#62P3
Module:
ADSRA752
Explanation:
obsolete.
User Response:
XPD7540
None.
ADSRA752
Explanation:
obsolete.
XPD7526
Because the COMPUTE command has not been incorporated for Xpediter, this message is
COMPUTE COMMAND CONTAINS NO OPERANDS
Module:
XPD7525
1-85
Because the COMPUTE command has not been incorporated for Xpediter, this message is
None.
X(4),’LVL’,(B,2),PREV EWT’,X(4)’
Module:
ADSRA754
Explanation:
obsolete.
User Response:
Because the COMPUTE command has not been incorporated for Xpediter, this message is
None.
XPD7650
THE NUMBER OF DMAPS RECORDS AVAILABLE IS LESS THAN THE COUNT SUPPLIED FOR THE
ENHANCED FIND OPERATION. SUBSEQUENT FIND COMMANDS FOR THIS MODULE WILL DEFAULT TO STRING
FINDS.
Module:
ADSRA765
Explanation: There is some corruption of the data that Xpediter uses to build the control blocks for the
enhanced FIND function. The COBOL enhanced FIND function has been disabled for the currently active
module. The FIND command will now function as a string FIND.
User Response: If the user requires the COBOL enhanced FIND function for the module being tested, contact
Compuware Customer Support. Otherwise, the user may continue testing.
XPD7680
GETMAIN FAILED FOR THE PDT BLOCK - FIND TERMINATED
Module:
ADSRA768
Explanation:
User Response:
XPD7681
Xpediter ran out of storage while processing FIND.
Restart Xpediter or logon with a larger memory size.
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:
XPD7683
Recompile with the enhanced FIND option or regard this as just an informational message.
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.
1-86
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD7684
AN ENTRY IS MISSING FOR THE XXXXXXXX ASSOCIATED WITH STATEMENT YYYYYY.
Module:
ADSRA768
Explanation:
User Response:
XPD7685
Contact Compuware Customer Support.
A data-name record could not be matched to a Data Division occurrence.
Contact Compuware Customer Support.
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.
User Response:
XPD7690
Contact Compuware Customer Support.
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.
User Response:
XPD7691
None.
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.
User Response:
XPD7692
None.
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:
XPD7693
Enter a COBOL Primary FIND command (Refer to Format 2 Syntax) with and INDirect option.
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:
XPD7710
Reissue the FIND command with the appropriate data name and keywords.
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:
XPD7777
If necessary, reissue the FIND command with the correct information.
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.
Xpediter/TSO Messages
XPD7932
INVALID COMBINATION OF PARAMETERS
Module:
ADSRA793
Explanation:
User Response:
XPD7933
1-87
Two or more of the parameters entered cannot be used in conjunction with each other.
Eliminate the invalid combination of parameters from the command and try again.
REQUIRED PARAMETER MISSING
Module:
ADSRA793
Explanation: A command was entered that required one or more parameters. The parameter(s) were not found.
User Response:
XPD7934
Correct and retry.
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:
XPD7950
SPECIFIED STRING REQUIRES AN ENDING DELIMITER
Module:
ADSRA795
Explanation:
User Response:
XPD8033
User Response:
User Response:
resides in.
User Response:
User Response:
User Response:
User Response:
PARM is not ACTIVATE, DEACTIVATE, FORCE or MAINTENANCE.
Correct the PARM and rerun.
The SYSIN dataset must be Fixed or Fixed-Blocked, and the LRECL must be 80.
Correct the JCL and rerun.
Self explanatory.
Correct the SYSIN input and rerun.
The SYSIN card that precedes this message has a syntax error.
Correct the SYSIN input and rerun.
SYSIN DD MISSING OR DOESN'T INCLUDE DB2 SUBSYSTEM NAMES
Explanation:
User Response:
XPD8040
Move the program being executed to an authorized library or authorize the library that it
SYNTAX ERROR IN ABOVE SYSIN RECORD
Explanation:
XPD8039
The program being executed is not in an authorized library.
DUPLICATE DB2 SUBSYSTEM NAME 'xxxx' FOUND IN SYSIN
Explanation:
XPD8038
None.
INCORRECT SYSIN RECFM OR LRECL
Explanation:
XPD8037
First run of XPDB2SP since IPL.
MISSING OR INCORRECT EXEC PARM
Explanation:
XPD8036
Correct and retry.
REQUESTED FUNCTION REQUIRES APF AUTHORITY
Explanation:
XPD8035
The string must end with a quote, apostrophe, or ==.
XPED DB2 SP DEBUGGING HAS NOT BEEN ACTIVATED SINCE LAST IPL
Explanation:
XPD8034
If specified incorrectly, correct and retry. Otherwise, contact Compuware Customer Support.
The SYSIN card is missing or no DB2 subsystem names were specified.
Correct the SYSIN input (at least one DB2 subsystem name is required) and rerun.
XT DD MISSING
Explanation:
The XT DD card is missing.
1-88
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD8041
Add the XT DD card pointing to the Xpediter loadlib.
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
Explanation:
User Response:
XPD8043
User Response:
User Response:
User Response:
User Response:
User Response:
Self explanatory.
None.
Self explanatory.
Run the program with PARM=DEACTIVATE.
Self explanatory.
None.
SUCCESFULLY DEACTIVATED
Explanation:
User Response:
XPD8049
None.
SUCCESFULLY ACTIVATED
Explanation:
XPD8048
Self explanatory.
COULDN'T APPLY MAINTENANCE, NEED TO BE DEACTIVATED FIRST
Explanation:
XPD8047
Check with your MVS system programmer.
COULDN'T DEACTIVATE, ALREADY INACTIVE
Explanation:
XPD8046
Self explanatory.
COULDN'T ACTIVATE, ALREADY ACTIVE
Explanation:
XPD8045
Check options used in JCLLKDB2 member, correct and relink, then rerun.
COULDN'T ACQUIRE 'xxxx' BYTES FROM CSA
Explanation:
XPD8044
Self explanatory.
Self explanatory.
None.
MAINTENANCE APPLIED SUCCESSFULLY
Explanation:
User Response:
Self explanatory.
None.
XPD8050
COULDN'T DEACTIVATE BECAUSE OF SOME XPED DB2 SP SESSION(S) STILL IN PROGRESS. USE EXEC
PARM=FORCE TO DEACTIVATE
Explanation:
User Response:
XPD8051
Wait for active users to finish and run again, or run with PARM=FORCE.
NUMBER OF XPED DB2 SP SESSION(S) IN PROGRESS IS xxxx
Explanation:
User Response:
XPD8052
Self explanatory.
Self explanatory.
None.
WLM IS NOT INSTALLED
Explanation:
User Response:
IBM’s Workload Manager is required for Xpediter DB2 Stored Procedure support.
None.
Xpediter/TSO Messages
1-89
XPD8053
MVS LEVEL BELOW MINIMUM REQUIREMENT (OS/390 V1.R3). XPED DB2 SP FEATURE CAN'T BE
SUPPORTED
Explanation:
User Response:
XPD8054
User Response:
Self explanatory.
None.
XPED DB2 SP SUPPORT CSA STUB ADDRESS IS xxxxxxxx
Explanation:
User Response:
XPD8056
None.
+++ MSG # USED BY ROUTINE XPDB2PCR +++
Explanation:
XPD8055
Self explanatory.
Self explanatory.
None.
ACTIVATION WILL BE OF THE PREVIOUSLY LOADED COPY OF THE PC INTERCEPT
Explanation: A non-initial request was made to activate the DB2 stored procedure PC intercept. An initial
request will load a PC intercept and activate it. A non-initial request will activate an already loaded version. This
version can be from the initial activation or from a PARM=MAINTENANCE run.
User Response: If a new copy of the PC intercept code is desired, run PARM=DEACTIVATE (to deactivate the
code), run PARM=MAINTENANCE (to load a new copy of the code), then run PARM=ACTIVATE (to activate the
new copy of the code).
XPD8066
SYSTEM NAME FOR CURRENT SYSTEM IS xxxx
Explanation:
activated.
User Response:
XPD8068
User Response:
First run of XPIMSTLR since IPL.
None.
DUPLICATE IMS SUBSYSTEM NAME 'xxxx' FOUND IN SYSIN
Explanation:
User Response:
XPD8070
If this is the wrong system, resubmit the activation request on the correct system.
IMS USER ID SUPPORT INTERCEPT HAS NOT BEEN ACTIVATED SINCE LAST IPL
Explanation:
XPD8069
This message is to inform the user on which system the DB2 stored procedure intercept was
Self explanatory.
Correct the SYSIN input and rerun.
SYSIN DD MISSING OR DOESN'T INCLUDE IMS SUBSYSTEM NAMES
Explanation:
User Response:
The SYSIN card is missing or no IMS subsystem names were specified.
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
Explanation:
User Response:
XPD8072
Self explanatory.
Wait for active users to finish and run again, or run with PARM=FORCE.
NUMBER OF XPED/IMS SESSION(S) IN PROGRESS IS xxxx
Explanation:
User Response:
Self explanatory.
None.
XPD8073
MVS LEVEL BELOW MINIMUM REQUIREMENT OF OS 390. XPED/IMS USER ID SUPPORT FEATURE CAN'T
BE SUPPORTED
Explanation:
User Response:
XPD8075
Self explanatory.
None.
DFSCAUT0/DFSDAUT0 SA COULD NOT BE LOCATED.
Explanation:
Self explanatory.
1-90
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD8076
None.
TRAN AUTH EXIT XPIMSRN0 EPA= aaaaaaaa
Explanation: The user’s Transaction Authorization Exit named XPIMSRN0 has been located and its entry point
address is aaaaaaaa.
User Response:
XPD8077
None.
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 and Xpediter/IMS Installation Guide for instructions on
installing the additional exit with Xpediter/TSO IMS userid support.
XPD8078
XPEDITER/IMS vv.rr.mm TRAN AUTH EXIT DFSCTRN0 EPA=aaaaaaaa
Module:
DFSCTRN0
Explanation:
User Response:
XPD8079
DFSCTRN0
Explanation:
incomplete.
User Response:
User Response:
Xpediter/TSO has initiated IMS userid support.
None.
SEVERE ERROR. DFSCSIIO NOT AVAILABLE
Module:
DFSCTRN0
Explanation:
disabled.
User Response:
IMS service routine DFSCSIIO returned an error to DFSCTRN0. The IMS User ID support is
Contact Compuware Customer Support.
SEVERE ERROR. CSA STORAGE NOT AVAILABLE
Module:
DFSCTRN0
Explanation:
User Response:
XPD8083
Contact Compuware Customer Support.
DFSCTRN0, DFSMSCE0
Explanation:
XPD8082
Xpediter/TSO expected that IMS userid support was installed, but found the installation
FOUND IMS USER ID SUPPORT SETUP
Module:
XPD8081
None.
IMS USER ID SUPPORT SETUP NOT FOUND
Module:
XPD8080
The Xpediter/IMS userid support exit was loaded, and its entry point address is aaaaaaaa.
A request for CSA storage failed. The IMS User ID support is disabled.
Contact Compuware Customer Support.
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:
XPD8084
Ensure the IMS control region steplib contains the library for XPIMSRN0.
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.
User Response:
Contact Compuware Customer Support.
Xpediter/TSO Messages
XPD8085
SEVERE ERROR. CSI SERVICE FAILURE
Module:
DFSCTRN0
Explanation:
disabled.
User Response:
XPD8086
1-91
IMS service routine DFSCSIIO returned an error to DFSCTRN0. The IMS User ID support is
Contact Compuware Customer Support.
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:
XPD8092
XPEDITER/IMS vv.rr.mm TRAN ROUT EXIT DFSMSCE0 EPA=aaaaaaaa
Module:
DFSMSCE0
Explanation:
User Response:
XPD8100
Correct the STEPLIB or the Xpediter DD control card for the install job, then rerun the job.
The Xpediter/IMS userid support exit was loaded, and its entry point address is aaaaaaaa.
None.
DB2 PC INTERCEPT CANNOT BE FOUND
Explanation: This message indicates that the DB2 PC intercept install program has tried to load XPDB2PCR,
but the load module found is not XPDB2PCR.
User Response:
XPD8101
Contact Compuware Customer Support.
FOUND USER EXIT XPIMSCE0
Module:
DFSMSCE0
Explanation: The Xpediter/IMS DFSMSCE0 exit discovered the site’s version (XPIMSCE0) and will invoke it
after determining that a transaction is not to be routed to an Xpediter region.
User Response:
XPD8102
None.
USER EXIT XPIMSCE0 NOT FOUND
Module:
DFSMSCE0
Explanation:
The Xpediter/IMS DFSMSCE0 exit discovered no site version of DFSMSCE0.
User Response: If it is desired that a site-specific version of the DFSMSCE0 exit be driven, it should be renamed
to XPIMSCE0 and placed in the RESLIB concatenation.
XPD8103
SEVERE ERROR LOADING XPIMSCE0
Module:
DFSMSCE0
Explanation: The IMS LOAD Service experienced an error when the Xpediter/IMS DFSMSCE0 exit attempted to
locate the site’s version (XPIMSCE0).
User Response:
XPD8104
Contact Compuware Customer Support.
VECTOR NOT FOUND FOR USER EXIT XPIMSCE0
Module:
DFSMSCE0
Explanation: The Xpediter/IMS DFSMSCE0 exit discovered the site’s version (XPIMSCE0), but found it was not
properly constructed.
User Response: Check the assembly of the site’s version of DFSMSCE0, ensuring that there were no errors and
that an instance of macro DFSMSCVT FUNC=VECTOR was included.
XPD8105
DFSCSI00 INTERFACE ERROR, CODE=cccccccc… DFSMSCE0 DISABLED
Module:
DFSMSCE0
Explanation:
User Response:
XPD9001
The Xpediter/IMS DFSMSCE0 exit experienced an error with the IMS service routine.
Contact Compuware Customer Support.
XPMINIT ACTIVATE SUCCESSFUL
Module:
XPMINIT
1-92
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD9002
XPMINIT ACTIVATE FAILED
Module:
XPMINIT
User Response:
XPD9003
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
Search job for errors that caused the failure and correct.
XPMINIT PRODUCT STATUS IS UNCHANGE, STILL ACTIVE
Module:
XPMINIT
User Response:
XPD9017
Look for errors and correct if necessary.
XPMINIT MAINTENANCE FAILED
Module:
XPD9016
None
XPMINIT MAINTENANCE SUCCESSFUL, WITH INTERNAL ERRORS
Module:
XPD9015
Search job for errors that caused the failure and correct.
XPMINIT PRODUCT IS NOT ACTIVE
Module:
XPD9014
Search job for errors that caused the failure and correct.
XPMINIT MAINTENANCE FAILED DURING ACTIVATION
Module:
XPD9013
Search job for errors that caused the failure and correct.
XPMINIT PRODUCT DEACTIVATED BY ERROR RECOVERY
Module:
XPD9012
None.
XPMINIT MAINTENANCE FAILED IN DEACTIVATION
Module:
XPD9011
Search job for errors that caused the failure and correct.
XPMINIT XPMINIT ENDED
Module:
XPD9010
None.
XPMINIT REMOVAL FAILED
Module:
XPD9009
None.
XPMINIT REMOVAL SUCCESSFUL
Module:
XPD9008
Search job for errors that caused the failure and correct.
XPMINIT DEACTIVATE SUCCESSFUL
Module:
XPD9007
None.
Search job for errors that caused the failure and correct.
XPMINIT PRODUCT STATUS IS UNCHANGED, NOT ACTIVE
Module:
XPMINIT
User Response:
Search job for errors that caused the failure and correct.
Xpediter/TSO Messages
XPD9018
XPMINIT ACTIVATE FAILED
Module:
XPMINIT
User Response:
XPD9019
XPMINIT ACTIVATE SUCCESSFUL, WITH INTERNAL ERRORS
Module:
XPMINIT
User Response:
XPD9020
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
Search job for errors that caused the failure and correct.
XPMINIT MBF REMAINS INACTIVE
Module:
XPMINIT
User Response:
XPD9030
Search job for errors that caused the failure and correct.
XPMINIT FAILED BEFORE REQUESTED FUNCTION
Module:
XPD9029
Look for errors and correct if necessary.
XPMINIT REMOVE FAILED, MODULES NOT REMOVED
Module:
XPD9028
Look for errors and correct if necessary.
XPMINIT ERROR IN XPMINIT, BUT REMOVE SUCCESSFUL
Module:
XPD9027
Search job for errors that caused the failure and correct.
XPMINIT ERROR IN XPMINIT, MAINTENANCE WAS SUCCESSFUL
Module:
XPD9026
Search job for errors that caused the failure and correct.
XPMINIT FAILED IN MAINTENANCE
Module:
XPD9025
Search job for errors that caused the failure and correct.
XPMINIT ERROR IN XPMINIT, SVC42 FRONT-END NOT ACTIVE
Module:
XPD9024
Look for errors and correct if necessary.
XPMINIT REMOVE FUNCTION FAILED
Module:
XPD9023
Search job for errors that caused the failure and correct.
XPMINIT DEACTIVATE SUCCESSFUL, WITH INTERNAL ERRORS
Module:
XPD9022
Look for errors and correct if necessary.
XPMINIT DEACTIVATE FAILED, MBF DEACTIVATED BY ERROR RECOVERY
Module:
XPD9021
Search job for errors that caused the failure and correct.
Search job for errors that caused the failure and correct.
XPMINIT MBF REMAINS ACTIVE
Module:
XPMINIT
User Response:
Search job for errors that caused the failure and correct.
1-93
1-94
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD9031
XPMINIT EXIT FROM XPMINIT FAILED, MBF SUCCESS FULLY ACTIVATED
Module:
XPMINIT
User Response:
XPD9032
XPMINIT MAINT REQUEST SUCCESSFUL, WITH ERRORS
Module:
XPMINIT
User Response:
XPD9033
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
Contact Compuware Customer Support.
XPMINIT TOKEN DOES NOT POINT TO A GCA
Module:
XPMINIT
User Response:
XPD9043
Contact Compuware Customer Support.
XPMINIT NO TOKEN FOUND, NO BACKOUT NECESSARY
Module:
XPD9042
Search job for errors that caused the failure and correct.
XPMINIT FAILED TO GET TOKEN, NO BACKOUT POSSIBLE
Module:
XPD9041
Search job for errors that caused the failure and correct.
XPMINIT MAINT FAILED DURING DEACTIVATION, MBF REMAINS ACTIVE
Module:
XPD9040
Search job for errors that caused the failure and correct.
XPMINIT ROUTINE DODEACT FAILED, DEACTIVATION DID NOT PROCESS
Module:
XPD9039
Look for errors and correct if necessary.
XPMINIT NOT REACTIVATED FOR MAINTENANCE DUE TO ERROR(S)
Module:
XPD9038
Look for errors and correct if necessary.
XPMINIT PROPERLY FROM DEACTIV ROUTINE
Module:
XPD9037
Search job for errors that caused the failure and correct.
XPMINIT MBF HAS BEEN DEACTIVATED BUT FAILED TO RETURN
Module:
XPD9035
Search job for errors that caused the failure and correct.
XPMINIT MAINTENANCE FAILED DUE TO ERRORS REACTIVATING MBF
Module:
XPD9035
Look for errors and correct if necessary.
XPMINIT MBF NOT REACTIVATED
Module:
XPD9034
Search job for errors that caused the failure and correct.
Contact Compuware Customer Support.
XPMINIT STUB WAS NOT LOADED
Module:
XPMINIT
User Response:
Contact Compuware Customer Support.
Xpediter/TSO Messages
XPD9044
XPMINIT SVC42 FRONT-END WAS NOT LOADED
Module:
XPMINIT
User Response:
XPD9045
XPMINIT
XPMINIT FAILED TO LOAD ADSIS315
Module:
XPMINIT
User Response:
XPD9047
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
Contact Compuware Customer Support.
XPMINIT FAILED TO LOAD XPMDRVR
Module:
XPMINIT
User Response:
XPD9052
Contact Compuware Customer Support.
XPMINIT GCA ALLOCATION FAILED
Module:
XPD9051
Contact Compuware Customer Support.
XPMINIT FAILED TO DELETE XPMDRVR
Module:
XPD9050
Contact Compuware Customer Support.
XPMINIT FAILED TO LOAD ADSIS316
Module:
XPD9049
Contact Compuware Customer Support.
XPMINIT FAILED TO LOAD XPMSTBLD
Module:
XPD9048
Contact Compuware Customer Support.
XPMINIT SVC42 FRONT-END IS NOT CURRENTLY ACTIVE
Module:
XPD9046
1-95
Contact Compuware Customer Support.
XPMINIT XTLIST DD MISSING
Module:
XPMINIT
Explanation:
The Install job, JCLACTMB is missing the DD XTLIST.
User Response: Add the DD XTLIST to JCLACTMB. The dataset refered to by XTLIST is the Xpediter Authorized
library.
XPD9053
XPMINIT XTLIST DSN NOT AUTHORIZED
Module:
XPMINIT
Explanation:
User Response:
XPD9054
XPMINIT
User Response:
Contact Compuware Customer Support.
XPMINIT FAILED TO LOAD XPMSVC42 / XPMSTUB MODULES
Module:
XPMINIT
User Response:
XPD9056
Correct the XTLIST dataset and resubmit the job.
XPMINIT TOKEN CREATION FAILED - NOT ACTIVATED
Module:
XPD9055
The dataset associated with DD XTLIST is not authorized.
Contact Compuware Customer Support.
XPMINIT XTLIBI DD MISSING
Module:
XPMINIT
Explanation:
The Install job JCLACTMB is missing the DD XTLIBI.
1-96
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response: Add the DD XTLIBI to JCLACTMB. The dataset refered to by XTLIBI is the Xpediter load library.
XPD9057
XPMINIT XTMMBF DD MISSING
Module:
XPMINIT
Explanation:
User Response:
staging file.
XPD9058
XPMINIT
Explanation:
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
Explanation:
User Response:
Contact Compuware Customer Support.
XPMINIT XTMMBF OPEN ERROR RC=XXXX, RS=XXXX
Module:
XPMINIT
Explanation:
User Response:
An error occurred when opening the Multi-Batch staging file - DD = XTMMBF.
Ensure the staging file was created correctly.
XPMINIT NO MBF SPECIFICATIONS AVAILABLE
Module:
XPMINIT
User Response:
Contact Compuware Customer Support.
XPMINIT GCA LOADED =
Module:
XPMINIT
Explanation:
User Response:
XPD9067
None.
XPMINIT
User Response:
XPD9066
Multi-Batch was found to be active already.
XPMINIT SVCUPDTE FAILED
Module:
XPD9065
Contact Compuware Customer Support.
XPMINIT MBF ALREADY ACTIVE
Module:
XPD9064
Contact Compuware Customer Support.
XPMINIT XPMSTUB ROUTINE NOT LOCATED - FATAL ERROR
Module:
XPD9063
Contact Compuware Customer Support.
XPMINIT XPMSVC42 ROUTINE NOT LOCATED - FATAL ERROR
Module:
XPD9062
Redefine the Xpediter staging file with the correct IDCAMS parameters and rerun the job.
XPMINIT
User Response:
XPD9061
The Xpediter staging file was defined with incorrect IDCAMS parameters.
XPMINIT GCA NOT LOCATED - FATAL ERROR
Module:
XPD9060
Add the DD XTMMBF to JCLACTMB. The dataset referred to by XTMMBF is the Xpediter
XPMINIT XTMMBF JFCB ERROR
Module:
XPD9059
The Install job JCLACTMB is missing the DD XTLIBI.
Display address where GCA resides - informational.
None.
XPMINIT DEACTIVATE FAILED - MBF NOT ACTIVE
Module:
XPMINIT
User Response:
Search job for errors that caused the failure and correct.
Xpediter/TSO Messages
XPD9068
XPMINIT GCA LOADED =
Module:
XPMINIT
Explanation:
User Response:
XPD9069
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
XPMINIT
User Response:
, RS=
Contact Compuware Customer Support.
XPMINIT WARNING FOR ADD LPA MEMBERS RC=
Module:
Contact Compuware Customer Support.
XPMINIT FAILED TO DELETE LPA MEMBERS RC=
Module:
XPMINIT
User Response:
Contact Compuware Customer Support.
XPMINIT XPMINIT JOB PARM: < 8 OR > 25
Module:
, RS=
XPMINIT
User Response:
XPD9080
RC=
XPMINIT
User Response:
XPD9079
Contact Compuware Customer Support.
XPMINIT FAILED TO ADD LPA MEMBERS
Module:
XPD9078
None.
XPMINIT REMOVE FAILED FOR REMOVE REQUEST
Module:
XPD9077
Search job for errors that caused the failure and correct.
XPMINIT REMOVE DEACTIVATE SUCCESSFUL
Module:
XPD9076
None.
XPMINIT ACTIVATE FAILED FOR MAINTENANCE
Module:
XPD9075
Search job for errors that caused the failure and correct.
XPMINIT MAINTENANCE ACTIVATE SUCCESSFUL
Module:
XPD9074
None.
XPMINIT DEACTIVATE FAILED FOR MAINTENANCE REQUEST
Module:
XPD9073
Contact Compuware Customer Support.
XPMINIT MAINTENANCE DEACTIVATE SUCCESSFUL
Module:
XPD9072
Contact Compuware Customer Support.
XPMINIT CAN NOT IDENTIFY XPMSTUB VERSION - CONTACT COMPUWARE
Module:
XPD9071
None.
XPMINIT FAILED TO FREE SVC CODE
Module:
XPD9070
Display address where GCA resides - informational.
XPMINIT
Explanation:
The JCL parameter is incorrect.
, RS=
1-97
1-98
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response: The JCL parameter must start with either ACTIVATE, MAINTENANCE, or DEACTIVATE. It may
also contain “,IMSP=” with the IMS preprocessor module next.
XPD9081
XPMINIT FAILED TO ESTABLISH ESTAE EXIT
Module:
XPMINIT
User Response:
XPD9082
XPMINIT RETURN CODE = XXXXXXXX, REASON CODE = XXXXXXXX
Module:
XPMINIT
Explanation:
User Response:
XPD9083
Contact Compuware Customer Support.
Return Code and Reason Code returned - see message XPD9081.
Contact Compuware Customer Support.
XPMINIT XTWLMADD OPEN ERROR RC=XXXX, RS=XXXX
Module:
XPMINIT
Explanation:
An error occurred while attempting to open the XTWLMADD dataset.
User Response: Verify that the JCL is pointing to the correct dataset and that the dataset was defined with the
correct attributes.
XPD9084
XPMINIT XTIMSADD OPEN ERROR RC=XXXX, RS=XXXX
Module:
XPMINIT
Explanation:
An error occurred while attempting to open the XTIMSADD dataset.
User Response: Verify that the JCL is pointing to the correct dataset and that the dataset was defined with the
correct attributes.
XPD9085
XPMINIT (input record)
Module:
XPMINIT
Explanation:
XPD9086
XPMINIT (input record)
Module:
XPMINIT
Explanation:
XPD9087
Informational. Displays the 80-byte XTWLMADD DD input record.
Informational. Displays the 80 byte XTIMSADD DD input record.
XPMINIT mmmmmmmm RELEASE vv.rr.mm (DDNAME)
Module:
XPMINIT
Explanation: During Multi-Batch initialization, this message will be displayed so that the user can verify the
release levels, vv.rr.mm, of the selected modules, mmmmmmmm, listed. If the release levels are not the same, an
abend will occur.
User Response:
XPD9088
If an abend occurs, verify that the libraries in the XPMINIT JCL are at the same release level.
XPMINIT mmmmmmmm RELEASE NOT FOUND (DDNAME)
Module:
XPMINIT
Explanation: During Multi-Batch initialization, this message will be displayed when the Xpediter/TSO release
level cannot be found in the module prefix area.
User Response: In the XPMINIT JCL, verify that the libraries are Xpediter/TSO libraries. If they are
Xpediter/TSO libraries, then contact Compuware Customer Support.
XPD9089
XPMINIT RELEASE LEVEL MISMATCH
Module:
XPMINIT
Explanation: During Multi-Batch initialization, this message will be displayed when there is a mismatch
between the selected modules listed in message XPD9087.
User Response: Check the list of modules in message XPD9087 to determine the mismatched modules. In the
XPMINIT JCL, replace the library with the mismatched module with the correct release level library.
Xpediter/TSO Messages
XPD9090
1-99
XPMINIT STORAGE ALLOCATION FAILURE (nn)
Module:
XPMINIT
Explanation: During Multi-Batch initialization, this message will be displayed when there is an error during
storage allocation. nn is an internal diagnostic code.
User Response:
XPD9091
Increase the region size for the XPMINIT batch job.
XPMINIT OPEN FAILED FOR DDNAME dddddddd
Module:
XPMINIT
Explanation: During Multi-Batch initialization, this message will be displayed when there is a failure to open
ddname dddddddd.
User Response: Verify that the correct library is assigned to the specified ddname. For example, the
Xpediter/TSO SLXTLOAD library should be assigned to the XTLIBI DD.
XPD9092
XPMINIT BLDL FAILED FOR MODULE mmmmmmmm IN DDNAME dddddddd
Module:
XPMINIT
Explanation: During Multi-Batch initialization, this message will be displayed when the initialization process
fails to find module mmmmmmmm in ddname dddddddd.
User Response: Verify that the correct library is assigned to the specified ddname. For example, the
Xpediter/TSO SLXTLOAD library should be assigned to the XTLIBI DD.
XPD9093
XPMINIT LOAD FAILED FOR MODULE mmmmmmmm IN DDNAME dddddddd
Module:
XPMINIT
Explanation: During Multi-Batch initialization, this message will be displayed when the initialization process
fails to load module mmmmmmmm from ddname dddddddd.
User Response: Verify that the correct library is assigned to the specified ddname. For example, the
Xpediter/TSO SLXTLOAD library should be assigned to the XTLIBI DD.
XPD9101
XPMMAIN ONE OR MORE DATASETS FAILED TO POST PROCESS
Module:
XPMMAIN
Explanation:
XPD9102
XPMMAIN AT LEAST ONE UNALLOCATE FAILED SEE MESSAGES
Module:
XPMMAIN
Explanation:
User Response:
XPD9103
Review messages to determine cause of failure.
XPMMAIN
Explanation:
User Response:
An error occurred while setting up Xpediter’s XTASKLIB DD.
Review messages to determine cause of failure.
XPMMAIN AN ERROR OCCURED ACCESSING XP3PARMS
Module:
XPMMAIN
User Response:
XPD9105
At least one unallocate failed.
XPMMAIN AN ERROR OCCURED ACCESSING THE DYNAMIC XTASKLIB
Module:
XPD9104
An error occurred while the XTASKLIB DD was being closed.
Contact Compuware Customer Support.
XPMMAIN ERROR DELETING MULTI-BATCH RECORD. SEE RC
Module:
XPMMAIN
Explanation:
An error occurred deleting a Multi-Batch record from the Multi-Batch Staging file.
User Response: These records are also deleted when the Multi-Batch job (JCLACTMB) is executed. If these errors
continue, contact Compuware Customer Support.
XPD9106
XPMMAIN ERROR REFRESHING MULTI-BATCH STORAGE INDEX.
Module:
XPMMAIN
1-100
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
XPD9107
XPMMAIN BAD SPECIFICATION PARAMETER PASSED TO XPMMAIN
Module:
XPMMAIN
User Response:
XPD9108
XPMMAIN
User Response:
XPMMAIN
Explanation:
User Response:
User Response:
User Response:
User Response:
The Multi-Batch Staging file could not be opened.
Review error messages to determine what action is required.
XPMMAIN MBF DATASET ALLOCATION FAILED RC= ,REASON= DSN=
Module:
XPMMAIN
Explanation:
User Response:
allocated.
The Multi-Batch Staging file could not be allocated.
Review the Return Code (RC) and Reason returned to determine why the file could not be
XPMMAIN XPMMAIN ENDED
Module:
XPMMAIN
User Response:
None.
XPMMAIN DYNAMIC ALLOCATION FOR XPIN FAILED
Module:
XPMMAIN
Explanation:
User Response:
The dynamic allocation for DD XPIN failed.
Contact Compuware Customer Support.
XPMMAIN XPIN OPEN FAILED
Module:
XPMMAIN
Explanation:
User Response:
XPD9117
Make sure the Xpediter load library is correct. Add a new record if necessary.
XPMMAIN
Explanation:
XPD9116
The XPLIBI DD dataset could not be found.
XPMMAIN MBF DATASET OPEN FAILED DSN=dsname
Module:
XPD9115
Contact Compuware Customer Support.
XPMMAIN
Explanation:
XPD9114
Xpediter was unable to read the Multi-Batch Staging file.
XPMMAIN XPLIBI DATASET NOT FOUND NAME=dsname
Module:
XPD9113
Look for related messages in the listing. Correct any other issues and retest.
XPMMAIN
Explanation:
XPD9112
The dynamic allocation routine failed because of a problem with a specific DD and dataset.
XPMMAIN MBF DATASET READ FAILED DSN=dsname
Module:
XPD9111
Contact Compuware Customer Support.
XPMMAIN AT LEAST ON DYNALLOC FAILED DD=ddname DSN=dsname
Module:
XPD9110
Contact Compuware Customer Support.
XPMMAIN MBF FACILITY FAILED DURING ATTACH PROCESS
Module:
XPD9109
Contact Compuware Customer Support.
Xpediter was unable to open the XPIN DD dataset.
Review error messages to determine what action is required.
XPMMAIN TEST TYPE NOT I OR U
Module:
XPMMAIN
Xpediter/TSO Messages
Explanation:
User Response:
XPD9118
XPMMAIN
Explanation:
User Response:
User Response:
User Response:
User Response:
Contact Compuware Customer Support.
XPMMAIN
Explanation:
User Response:
Failure occurred while attempting to get storage.
Contact Compuware Customer Support.
XPMMAIN XP3PARM OPEN STORAGE OBTAIN FAILED
Module:
XPMMAIN
Explanation:
User Response:
Failure occurred while attempting to get storage.
Contact Compuware Customer Support.
XPMMAIN XP3PARM OPEN FAILED
Module:
XPMMAIN
Explanation:
User Response:
Xpediter was unable to open the XP3PARM DD dataset.
Contact Compuware Customer Support.
XPMMAIN DYNAMIC ALLOCATION FOR XTMMBF FAILED
Module:
XPMMAIN
Explanation:
User Response:
The dynamic allocation of the Xpediter Multi-Batch Staging file failed.
Look for other messages regarding DD XTMMBF.
XPMMAIN OPEN FOR XTMMBF FAILED
Module:
XPMMAIN
Explanation:
User Response:
XPD9127
The dynamic allocation for DD XP3PARMS failed.
XPMMAIN XP3PARM DCB STORAGE OBTAIN FAILED
Module:
XPD9126
Check the “Test Type” field on the Multi-Batch panel and correct if necessary.
XPMMAIN
Explanation:
XPD9125
The Code Coverage specification is expected to be a combination of C, T, and F.
XPMMAIN DYNAMIC ALLOCATION FOR XP3PARMS FAILED
Module:
XPD9124
Contact Compuware Customer Support.
XPMMAIN
Explanation:
XPD9123
Failure occurred while attempting to get storage.
XPMMAIN INVALID CODE COVERAGE SPECIFICATION - XX
Module:
XPD9122
The REGION parameter for the batch JOB should be increased if possible.
XPMMAIN
Explanation:
XPD9121
Failure occurred while attempting to get storage.
XPMMAIN XPIN DCB STORAGE OBTAIN FAILED
Module:
XPD9120
Check the “Test Type” field on the Multi-Batch panel and correct if necessary.
XPMMAIN XPIN OPEN STORAGE OBTAIN FAILED
Module:
XPD9119
The “Test Type” field must start with either I for Interactive or U for unattended test.
The open failed for the Multi-Batch Staging file.
Review error messages to determine what action is required.
XPMMAIN CLOSE FOR XTMMBF FAILED, PROCESSING CONTINUES
Module:
XPMMAIN
User Response:
Look for other messages regarding DD XTMMBF.
1-101
1-102
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD9128
XPMMAIN XTMMBF RECORD NOT FOUND - record key
Module:
XPMMAIN
Explanation:
User Response:
XPD9129
XPMMAIN
Explanation:
User Response:
User Response:
User Response:
Contact Compuware Customer Support.
XPMMAIN
Explanation:
User Response:
Xpediter was unable to obtain storage for the Xpediter log.
The REGION parameter for the batch JOB should be increased if possible.
XPMMAIN STORAGE ALLOCATION FAILED FOR PRINTLOG TDCB
Module:
XPMMAIN
Explanation:
User Response:
Xpediter was unable to obtain storage for the PRINTLOG.
Contact Compuware Customer Support.
XPMMAIN STORAGE ALLOCATION FAILED FOR PRINTLOG OPEN
Module:
XPMMAIN
Explanation:
User Response:
Xpediter was unable to obtain storage for the PRINTLOG.
The REGION parameter for the batch JOB should be increased if possible.
XPMMAIN OPEN FAILED FOR PRINTLOG
Module:
XPMMAIN
Explanation:
User Response:
XPD9136
Xpediter was unable to obtain storage for the Xpediter log.
XPMMAIN STORAGE ALLOCATION FAILED FOR XPOUT OPEN
Module:
XPD9135
Contact Compuware Customer Support.
XPMMAIN
Explanation:
XPD9134
The XDYNAMIC dataset was not the first dataset in the XTASKLIB concatenation.
XPMMAIN STORAGE ALLOCATION FAILED FOR XPOUT DCB
Module:
XPD9133
Contact Compuware Customer Support.
XPMMAIN
Explanation:
XPD9132
The JCFB was not found for XDYNAMIC DD.
XPMMAIN XDYNAMIC WAS NOT FIRST TASKLINN ALLOCATED
Module:
XPD9131
Make sure the staging file is correct. Add a new record if necessary.
XPMMAIN XDYNAMIC NOT FOUND DD=ddname DSN=dataset name
Module:
XPD9130
The Multi-Batch Staging file did not have a matching record.
Xpediter was unable to open the PRINTLOG.
Review error messages to determine what action is required.
XPMMAIN OPEN FAILED FOR XPLOG IN PRINTLOG
Module:
XPMMAIN
Explanation: The XPOUT DD refers to the Xpediter/TSO session log. If it is not present, you cannot spool (log)
the output from a test.
User Response:
XPD9137
Review error messages to determine what action is required.
XPMMAIN XTASKLIB OPEN FAILED, XTASKLIB NOT ALLOCATED - FATAL
Module:
XPMMAIN
Explanation: The XTASKLIB is a DD dynamically allocated by Xpediter. It will contain a concatenation of files
including the STEPLIB from the JCL and the load libraries saved in the Staging File.
User Response:
Contact Compuware Customer Support.
Xpediter/TSO Messages
XPD9138
1-103
XPMMAIN XTASKLIB OPEN FAILED - FATAL ERROR
Module:
XPMMAIN
Explanation: The XTASKLIB is a DD dynamically allocated by Xpediter. It will contain a concatenation of files
including the STEPLIB from the JCL and the load libraries saved in the Staging File.
User Response:
XPD9139
Review error messages to determine what action is required.
XPMMAIN XTASKLIB OPEN STORAGE OBTAIN FAILED - FATAL ERROR
Module:
XPMMAIN
Explanation: The XTASKLIB is a DD dynamically allocated by Xpediter. It will contain a concatenation of files
including the STEPLIB from the JCL and the load libraries saved in the Staging File.
User Response:
XPD9140
The REGION parameter for the batch JOB should be increased if possible.
XPMMAIN XTASKLIB DCB STORAGE OBTAIN FAILED - FATAL ERROR
Module:
XPMMAIN
Explanation: The XTASKLIB is a DD dynamically allocated by Xpediter. It will contain a concatenation of files
including the STEPLIB from the JCL and the load libraries saved in the Staging File.
User Response:
XPD9141
XPMMAIN XP/TSO TERMINATED WITH cc
Module:
XPMMAIN
Explanation:
User Response:
XPMMAIN
User Response:
XPMMAIN
Explanation:
User Response:
Failure occurred while attempting to get storage.
Contact Compuware Customer Support.
XPMMAIN STORAGE OBTAIN BELOW FAILED FOR
Module:
XPMMAIN
Explanation:
User Response:
Failure occurred while attempting to get storage.
Contact Compuware Customer Support.
XPMMAIN FAILED TO ALLOCATE STORAGE FOR XPLIBI OPEN
Module:
XPMMAIN
Explanation:
User Response:
XPD9148
The XPLIBI DD is the Xpediter load library. Make sure the correct library is being allocated.
XPMMAIN STORAGE OBTAIN BELOW FAILED FOR
Module:
XPD9147
Contact Compuware Customer Support.
XPMMAIN FAILED TO OPEN XPLIBI
Module:
XPD9146
Contact Compuware Customer Support.
XPMMAIN
User Response:
XPD9145
The dynamic allocation for DD XPLIBI failed.
XPMMAIN LOAD FAILED FOR MODULE modname ON XPLIBI
Module:
XPD9144
Review any error messages to determine if any action is required.
XPMMAIN DYNAMIC ALLOCATION FOR XPLIBI FAILED
Module:
XPD9143
COMPLETION CODE
XPMMAIN
User Response:
XPD9142
Review error messages to determine what action is required.
Failure occurred while attempting to get storage.
The REGION parameter for the batch JOB should be increased if possible.
XPMMAIN BLDL FAILED FOR MODULE modname ON XPLIBI
Module:
XPMMAIN
1-104
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation:
User Response:
XPD9161
User Response:
XPMDYNA
XPMDYNA
Explanation:
An error occurred while building a concatenation list.
XPMDYNA INFORMATION INQUIRY FAILED
Module:
XPMDYNA
Explanation:
An error occurred while retrieving dataset information.
XPMDYNA INVALID DD NAME = ddname
Module:
XPMDYNA
Explanation:
User Response:
An error occurred with the DDNAME ddname
Correct error and retest.
XPMDYNA TYPE MUST BE X"00", X"07" OR X"08"
Module:
XPMDYNA
Explanation:
User Response:
An invalid space type was specified.
Correct space type to be TRACKS or CYLINDERS.
XPMDYNA INVALID DS NAME = dsname
Module:
XPMDYNA
Explanation:
User Response:
XPD9171
An error occurred while removing a file from the concatenation list.
XPMDYNA DD NAME ALLOCATION FAILED
Module:
XPD9170
An error occurred while trying to deconcatenate files.
XPMDYNA
Explanation:
XPD9169
An error occurred while trying to concatenate files.
XPMDYNA REMOVE FAILED
Module:
XPD9168
, RS=
XPMDYNA
Explanation:
XPD9167
An error occurred while trying to free a file.
XPMDYNA DECONCATENATE FAILED
Module:
XPD9166
, RS=
XPMDYNA CONCATENATE FAILED RC=
Explanation:
XPD9165
Correct problem and retest.
XPMDYNA
Explanation:
Module:
, DYN@= DDN=ddname , DSN=dsname
The allocate failed for the dataset listed.
XPMDYNA UNALLOCATE FAILED RC=
Module:
XPD9164
, RS=
XPMDYNA
Explanation:
XPD9163
The XPLIBI DD is the Xpediter load library. Make sure the correct library is being allocated.
XPMDYNA ALLOCATE FAILED RC=
Module:
XPD9162
A BLDL failed while attempting to aquire information on modname from DD XPLIBI
The dataset name specified is incorrect.
Correct the dataset name.
XPMDYNA INVALID STATUS PASSED
Module:
XPMDYNA
Explanation:
User Response:
An invalid file disposition was passed.
Check all file disposition parameters (DISP=) for correctness and retest.
Xpediter/TSO Messages
XPD9172
XPMDYNA INVALID NORMAL DISPOSITION PASSED
Module:
XPMDYNA
Explanation:
User Response:
XPD9173
XPMDYNA
Explanation:
User Response:
User Response:
User Response:
XPMDRVR
Explanation:
User Response:
The Xpediter load library could not be dynamically allocated.
Make sure the XTLIBI dataset is the Xpediter load library.
XPMDRVR OPEN OF XTLIBI FAILED
Module:
XPMDRVR
Explanation:
User Response:
Xpediter is unable to allocate the Xpediter load library.
Make sure the XTLIBI dataset is the Xpediter load library.
XPMDRVR LOAD OF XPMMAIN FAILED
Module:
XPMDRVR
User Response:
Make sure program XPMMAIN exists in the Xpediter load library.
XPMDRVR R1 POINTS TO BAD SPECIFICATION CNTL BLOCK
Module:
XPMDRVR
Explanation:
User Response:
Xpediter program XPMDRVR is not pointing to the correct control block.
Retest program. If error continues, contact Compuware Customer Support.
XPMMBCT - MULTI-BATCH CROSS LPAR SUPPORT ACTIVE.
Module:
XPMMBCT
User Response:
XPD9201
None.
XPMDRVR DYNALLOC OF XPEDITER/TSO LOADLIB FAILED
Module:
XPD9200
Contact Compuware Customer Support.
XPMDYNA
User Response:
XPD9194
An internal error occurred.
XPMDYNA XPMDYNA ENDED
Module:
XPD9193
Contact Compuware Customer Support.
XPMDYNA
Explanation:
XPD9192
An internal error occurred.
XPMDYNA INVALID DYNALLOC FUNCTION AFTER FUNCTION VALIDATION
Module:
XPD9191
Check all file disposition parameters (DISP=) for correctness and retest.
XPMDYNA
Explanation:
XPD9176
An invalid file disposition was passed.
XPMDYNA INVALID DYNALLOC FUNCTION NOT X"01"-X"07"
Module:
XPD9175
Check all file disposition parameters (DISP=) for correctness and retest.
XPMDYNA INVALID CONDITIONAL DISPOSITION PASSED
Module:
XPD9174
An invalid file disposition was passed.
None.
XPMMBCT - MISSING HOMEPORT CONTROL CARD
Module:
XPMMBCT
User Response:
Check the MBCTIN file for a correctly coded HOMEPORT control card.
1-105
1-106
Xpediter/TSO and Xpediter/IMS Messages and Codes
XPD9202
XPMMBCT - MISSING RMOTPORT CONTROL CARD
Module:
XPMMBCT
User Response:
XPD9203
XPMMBCT - MORE THAN 1 HOMEPORT CONTROL CARD
Module:
XPMMBCT
User Response:
XPD9204
Check the MBCTIN file for extraneous HOMEPORT control cards.
XPMMBCT - DUPLICATE RMOTPORT CONTROL CARD
Module:
XPMMBCT
User Response:
XPD9205
Check the MBCTIN file for at least one correctly coded RMOTPORT control card.
Check the MBCTIN file for duplicate RMOTPORT control card(s).
XPMMBCT - MULTI-BATCH NOT INSTALLED ON THIS LPAR
Module:
XPMMBCT
User Response: The Multi-Batch Intercept has never been installed on this LPAR. Run the JCL to install/activate
the Multi-Batch Intercept. A JCL sample is located in member JCLACTMB of the SLXTINST dataset.
XPD9206
XPMMBCT - ANOTHER MBCT ALREADY RUNNING ON THIS LPAR
Module:
XPMMBCT
User Response: A Multi-Batch cross-LPAR Task is running on this LPAR. If you are attempting to refresh the
HOMEPORT/RMOTPORT connections, first shut down the MBCT that is currently running.
XPD9207
XPMMBCT - PORT NOT 5 DIGIT NUMERIC
Module:
XPMMBCT
User Response: Check the MBCTIN file and ensure that the HOMEPORT= and RMOTPORT= control cards
specify a 5-digit numeric value.
XPD9208
XPMMBCT - INVALID NAME/IP KEYWORD
Module:
XPMMBCT
User Response:
XPD9209
XPMMBCT - MAXIMUM OF 50 REMOTE PORTS EXCEEDED
Module:
XPMMBCT
User Response:
XPD9210
Check the MBCTIN file and ensure that there are no more than 50 RMOTPORT= control cards.
XPMMBCT - HOST NAME / IP ADDRESS CANNOT BE BLANK
Module:
XPMMBCT
User Response:
XPD9211
Check the MBCTIN file and ensure that the NAME/IP= values are correct.
Check the MBCTIN file and ensure that the NAME/IP= values are not blank.
XPMMBCT - INVALID MBCTIN CONTROL CARD
Module:
XPMMBCT
User Response: A control card other than a comment, HOMEPORT, or RMOTPORT was encountered. Remove
the invalid control cards and resubmit the job.
XPD9212
XPMMBCT - MISSING HOMEPORT AND RMOTPORT CONTROL CARDS
Module:
XPMMBCT
User Response:
control card.
XPD9213
Check the MBCTIN file and ensure that there is at least one HOMEPORT= and RMOTPORT=
XPMMBCT - MULTI-BATCH NOT ACTIVE ON THIS LPAR
Module:
XPMMBCT
User Response: The Multi-Batch Intercept is not active on this LPAR. Run the JCL to install/activate the MultiBatch Intercept. A JCL sample is located in member JCLACTMB of the SLXTINST dataset.
Xpediter/TSO Messages
XPD9214
XPMMBCT - IDENTIFY FOR TCPIP *LISTEN* TASK FAILED
Module:
XPMMBCT
User Response:
XPD9215
XPMMBCT
User Response:
XPMMBCT
User Response:
ABEND.
A console modify command was issued against the Multi-Batch cross-LPAR Task requesting an
XPMMBCT - MBCTIN OR MBCTOUT DD STATEMENT MISSING
Module:
XPMMBCT
User Response:
XPD9218
The Multi-Batch cross-LPAR Task has failed. Contact Compuware Customer Support.
XPMMBCT - DUMP REQUESTED/ADVISED, WILL ABEND USER 3002.
Module:
XPD9217
The Multi-Batch cross-LPAR Task has failed. Contact Compuware Customer Support.
XPMMBCT - ATTACH OF *LISTEN* TASK FAILED
Module:
XPD9216
1-107
Check the JCL and ensure that the MBCTIN DD and/or the MBCTOUT DD card is present.
XPMMBCT - ERROR WITH MBCTIN OR MBCTOUT FILE
Module:
XPMMBCT
User Response: There was an error reading from the MBCTIN or writing to the MBCTOUT file. Ensure that the
file names specified are valid. If they are, contact Compuware Customer Support.
XPD9219
XPMMBCT - A HOST NAME ENTERED IS UNABLE TO BE RESOLVED
Module:
XPMMBCT
User Response: A host name specified for the NAME/IP= parameter could not be resolved to a valid IP address.
Ensure that the names specified are valid. If they are, contact Compuware Customer Support.
XPD9220
XPMMBCT - MULTI-BATCH I/O MODULE COULD NOT BE LOADED
Module:
XPMMBCT
User Response:
XPD9221
XPMMBCT - XPMSTBLD XREQ BUILD MODULE COULD NOT BE LOADED
Module:
XPMMBCT
User Response:
XPD9222
XPMMBCT
User Response:
XPMMBCT
User Response:
XPMMBCT
User Response:
A console stop command was issued against the Multi-Batch cross-LPAR Task.
XPMMBCT - UNABLE TO FREE CIB - SHUTTING DOWN.
Module:
XPMMBCT
User Response:
XPD9226
The Multi-Batch cross-LPAR Task has failed. Contact Compuware Customer Support.
XPMMBCT - STOP COMMAND ISSUED - SHUTTING DOWN.
Module:
XPD9225
The Multi-Batch cross-LPAR Task has failed. Contact Compuware Customer Support.
XPMMBCT - ATTACH OF *GCA WAIT* TASK FAILED
Module:
XPD9224
Ensure that the STEPLIB/JOBLIB DD contains the Xpediter/TSO SLXTLOAD library.
XPMMBCT - IDENTIFY FOR *GCA WAIT* TASK FAILED
Module:
XPD9223
Ensure that the STEPLIB/JOBLIB DD contains the Xpediter/TSO SLXTLOAD library.
The Multi-Batch cross-LPAR Task has failed. Contact Compuware Customer Support.
XPMMBCT - RECEIVED UNKNOWN COMMAND - SHUTTING DOWN.
Module:
XPMMBCT
1-108
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response: A console command other than stop or modify was issued against the Multi-Batch cross-LPAR
Task. The Multi-Batch cross-LPAR Task will terminate.
XPD9227
XPMMBCT - MODIFY COMMAND CONTAINS UNKNOWN VALUE - IGNORED.
Module:
XPMMBCT
User Response: A console modify command was issued against the Multi-Batch cross-LPAR Task, but contained
an unknown request type. The command is ignored.
XPD9800
LOG COMMAND NOT VALID IN BATCH
Explanation:
User Response:
XPD9801
User Response:
XPD9802
User Response:
User Response:
User Response:
This is an internal problem; perhaps something has been overlayed.
Contact your internal technical support.
Not all Xpediter commands can be used in batch mode.
Refer to the Xpediter/TSO and Xpediter/IMS User’s Guide or Reference Manual for valid commands.
TRACE can only be used from a source screen.
COUNT NOT ALLOWED FROM SOURCELESS DEBUGGING SCREEN
Explanation:
COUNT can only be used from a source screen.
WHEN NOT ALLOWED FROM SOURCELESS DEBUGGING SCREEN
Explanation:
XPD9809
Refer to the Xpediter/TSO and Xpediter/IMS User’s Guide or Reference Manual for valid commands.
TRACE NOT ALLOWED FROM SOURCELESS DEBUGGING SCREEN
Explanation:
XPD9808
Not all Xpediter commands can be used in batch mode.
RETEST COMMAND NOT VALID IN BATCH
Explanation:
XPD9807
Refer to the Xpediter/TSO and Xpediter/IMS User’s Guide or Reference Manual for valid commands.
COMMAND NUMBER OUT OF SYNC WITH TABLE IN ADSRA412
Explanation:
XPD9806
Not all Xpediter commands can be used in batch mode.
FIND COMMAND NOT VALID IN BATCH
Explanation:
XPD9804
Refer to the user guide or reference manual for valid commands.
EXCLUDE COMMAND NOT VALID IN BATCH
Explanation:
XPD9803
Not all Xpediter commands can be used in batch mode.
WHEN can only be used from a source screen.
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:
User Response:
XPD9816
All EXCLUDEs can be reset by END or RESET.
COMMAND NOT ALLOWED FOR DISPLAY ONLY LINE
Explanation:
User Response:
XPD9990
An EXCLUDE was not set on this statement.
The command is allowed only for a code line or data line.
Retry command on a code line or data line.
MODULE NAME CANNOT END WITH A DOT
Module:
ADSRA612
Xpediter/TSO Messages
Explanation:
colon (::).
User Response:
XPD9993
Check the syntax of the command entered.
When the load module name is entered, the next name must be the module or CSECT name.
INVALID LITERAL SPECIFICATION
Module:
ADSRA659
Explanation:
User Response:
XPD9995
Module names must end with a single colon (:) and load module names must end with a double
MODULE NAME MUST FOLLOW LOAD MODULE NAME
Explanation:
XPD9994
1-109
No terminal quote was found on the literal.
Add quote to end of literal and try again.
NO EDB AVAILABLE FOR ITEM
Module:
ADSRA659
Explanation:
name.
Not enough information could be found to build the Xpediter control block for the target data
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:
User Response:
Neither the numeric literal nor the character literal should be used to change an instruction.
To change the instruction area of the program, use the hexadecimal literal.
1-110
Xpediter/TSO and Xpediter/IMS Messages and Codes
2-1
Chapter 2.
User Abend Codes
Chap 2
ABEND 3000
Module: XPHOGNPF, XPHOGNIF, XPHOGNBF, XPHOGNTF, XPRDLIST, XPBTSLNK,
XPEDCTL, ADSRA207, and ADSRA300
Explanation:
compile.
User Response:
ABEND 3001
This ABEND always means there is insufficient storage for an Xpediter/TSO
Increase the REGION for the JOB or STEP, and resubmit the compile job.
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.
User Response:
ABEND 3002
Contact your internal technical support.
UNABLE TO TEST USER PROGRAM
Module:
ADSRA410, CSSMVS, XPTSO, XPDRP, and XPINIT
Explanation:
User Response:
follows:
Xpediter is unable to test the user program.
See the session log for additional details. The ABEND reason code is set as
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.
2A
The TEST ID was not specified for a Code Coverage test.
2C
The SYSTEM NAME was not specified for a Code Coverage test.
2E
The XCOVER 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).
34
A DB2 stored procedure test encountered an unrecoverable error.
36
Multi-Batch Communication Task failure – see WTO message.
ABEND 3003
Module:
XPEDITER BLDL FAILURE
ADSIM002
2-2
Xpediter/TSO and Xpediter/IMS Messages and Codes
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:
User Response:
ABEND 3008
Successive ABENDS occurred while an application module was being tested.
Contact your internal technical support.
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.
User Response:
ABEND 3009
Contact your internal technical support.
A DIAGNOSE ABEND HAS BEEN REQUESTED
Module:
ADSRA148
Explanation: The Xpediter DIAGNOSE command was used to generate an ABEND of the
Xpediter region, or the EXIT ABEND command was entered without specifying a System or
User abend code (U3009 is the default).
User Response: If you did not enter the Xpediter EXIT ABEND command, contact your
internal technical support and provide them with the SYSUDUMP and other materials.
ABEND 3010
AN ERROR WAS ENCOUNTERED DURING THE MULTI-BATCH INITIALIZATION
RELEASE VERIFICATION PROCESS
Module:
XPMINIT
Explanation:
During Multi-Batch initialization an unrecoverable error occurred.
User Response: See the XPMINIT JES joblog for error messages. The ABEND reason code is set
as follows:
10
Miscellaneous errors that could occur during Multi-Batch initialization.
20
Unable to find the release level in one of the modules.
30
There is a release level mismatch.
ABEND 3020
Module:
XPEDITER/TSO/IMS SVC HAS ENCOUNTERED AN INVALID PARAMETER LIST
CWXTSVC
Explanation:
installation.
The Xpediter SVC has encountered an invalid parameter. Ensure proper
User Response: Contact Compuware Customer Support and provide them with
SYSUDUMP/SVC dump and other materials.
ABEND 3051
Module:
MAXIMUM OF 15 BASE REGISTERS EXCEEDED
ADSRA217
Explanation: The maximum number of base locator cells that Xpediter can maintain is 15.
This maximum was exceeded.
User Response:
ABEND 3052
Module:
Contact your internal technical support.
ALLOCATION OF GPR BUFFER FAILED
ADSRA217
Explanation:
User Response:
An attempt to allocate memory failed for the GPR buffer.
Contact your internal technical support.
User Abend Codes
ABEND 3092
Module:
OPEN FAILED FOR XTASKLIB
XPHOGNFF
Explanation:
User Response:
ABEND 3093
Module:
Contact your internal technical support.
XPBTBTSF, XPHOGNFF, and ADSIM004
User Response:
run again.
Module:
A critical error occurred during setup of the BTS environment.
ATTACH OF BTS FAILED
Explanation:
ABEND 3097
Contact your internal technical support.
XPHOGNFF and ADSIM004
User Response:
Module:
A critical error occurred during setup of the BTS environment.
ATTACH OF SUBTASK FAILED
Explanation:
ABEND 3095
Add the XTASKLIB DD to your JCL or CLIST and try again.
XPHOGNFF and ADSIM004
User Response:
Module:
An attempt to open the XTASKLIB DD failed.
IDENTIFY FAILED FOR SUBTASK
Explanation:
ABEND 3094
2-3
A critical error occurred during setup of the BTS environment.
Verify that the appropriate BTS libraries were included in the STEPLIB and
BTS CONTROL BLOCK NOT FOUND
ADSIM004
Explanation: A previously constructed BTS control block cannot be located. Probable
memory overlay.
User Response:
ABEND 3099
Module:
LOAD OF XPEDITER FAILED
ADSIM004
Explanation:
User Response:
try again.
ABEND 3100
Module:
Contact your internal technical support.
The load module for Xpediter could not be found.
Include the Xpediter load module library in the STEPLIB concatenation and
LOAD OF APPLICATION MODULE FAILED
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
Module:
INVALID BREAKPOINT INSTRUCTION EXECUTED
ADSRA104 and ADSRA478
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 Customer Support.
ABEND 3333
Module: ADSRA417, XPHOGNBF, XPHOGNEQ, XPHOGNFF, XPHOGNIF, XPHOGNKQ,
XPHOGNPF, XPHOGNSQ, or XPHOGNTF
2-4
Xpediter/TSO and Xpediter/IMS Messages and Codes
Explanation:
message.
An abend occurred in Xpediter/TSO. The abend is preceded by an error
User Response: Contact your internal technical support and provide them with the session
log and other materials.
ABEND 3398
Module:
XPEDITER/TSO ABEND IN ADSRANNNEP N(8) IA N(8) DISP N(6)
ADSRA000 and ADSRA106
Explanation: An ABEND occurred in Xpediter/TSO. An Xpediter/TSO internal control stack
will follow this message.
User Response: Contact Compuware Customer 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.
User Response:
Contact Compuware Customer Support.
3-1
Chapter 3.
Miscellaneous Messages and Codes Information
Chap 3
Xpediter/ROS Messages
Messages 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 Documentation Recreation
Utility
Jobs 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.
3-2
Xpediter/TSO and Xpediter/IMS Messages and Codes
4-1
Chapter 4.
Xpediter for DB2 Extension Run-Time Messages
SQI435 = 1,
COMMAND NOT RECOGNIZED
Explanation:
User Response:
SQI435 = 2,
User Response:
User Response:
The line command entered is not permitted on excluded lines.
Check for a misspelled line command.
A number is not allowed with the specified line command.
Remove the number, or enter another line command.
COMMAND NOT ALLOWED ON LINE
Explanation:
User Response:
SQI435 = 5,
Check for a misspelled line command.
NUMBER NOT ALLOWED WITH SPECIFIED LINE COMMAND
Explanation:
SQI435 = 4,
The line command entered is not recognized as a valid command.
ONLY D, F, and L COMMANDS ARE PERMITTED ON EXCLUDED LINES
Explanation:
SQI435 = 3,
Chap 4
The line command was entered on a non-Procedure Division line.
Remove the line command.
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:
User Response:
SQIC00 = 1,
Enter a matching block command to complete the block command pair.
INVALID SET COMMAND
Explanation:
User Response:
SQIC00 = 4,
A matching block command was not entered.
The SET processor could not identify the category for the SET command.
None.
ERROR PROCESSING SET COMMAND
Explanation: The SET command was unable to obtain the information needed to process;
i.e., no parsed command block.
User Response:
SQIC00 = 97,
COMMAND BLOCK NOT FOUND
Explanation:
User Response:
SQIC00 = 98,
None.
The SET command was unable to obtain the parsed command block.
None.
ENTERING SET FUNCTION
Explanation:
The SET command is being invoked.
4-2
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
SQIC00 = 99,
EXITING SET FUNCTION
Explanation:
User Response:
SQIDCI = 2,
The SET command is being terminated.
None.
MORE THAN 256 LEADING BLANKS ON SQL STATEMENT
Explanation:
User Response:
SQIDCI = 3,
None.
There are more than 256 blanks preceding the SQL verb.
Make sure that your SQL verb is entered within the first 256 bytes.
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:
User Response:
SQID00 = 1,
User Response:
User Response:
Check for the keyword SELECT.
The CURSOR_NAME was expected in the SQL statement and none was
None.
NO HOST VARIABLE(S) NOR DESCRIPTOR SPECIFIED
Explanation:
User Response:
call.
SQID00 = 5,
None.
CURSOR_NAME NOT SPECIFIED
Explanation:
provided.
SQID00 = 4,
The keyword CURSOR was expected in the SQL statement, and none was
SELECT PORTION ON DECLARE CURSOR STATEMENT MISSING
User Response:
SQID00 = 3,
None.
KEYWORD CURSOR EXPECTED IN SQL STATEMENT, NONE PROVIDED
Explanation:
provided.
SQID00 = 2,
An invalid request was made to SQIDCI. This is an internal error.
Parameter markers were present in the SQL statement.
These must be resolved by supplying host variables or an SQLDA in the SQL
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:
SQID00 = 6,
STATEMENT_NAME NOT SPECIFIED
Explanation:
User Response:
SQID00 = 7,
The STATEMENT_NAME was not specified on a PREPARE SQL call.
None.
ADDRESS OF THE SQLSOURCE CANNOT BE LOCATED
Explanation:
User Response:
SQID00 = 8,
Check for spelling errors.
The address of the SQLSOURCE on a PREPARE call cannot be located.
None.
SQL VERB IS NOT KNOWN TO XPEDITER FOR DB2 EXTENSION
Explanation:
User Response:
The SQL verb is not known to Xpediter for DB2 Extension.
Check for a spelling error.
Xpediter for DB2 Extension Run-Time Messages
SQID00 = 9,
KEYWORD DESCRIPTOR MISSING
Explanation:
User Response:
SQID00 = 21,
The keyword DESCRIPTOR on the SQL call is missing.
None.
ATTEMPTING TO USE MORE THAN 10 CURSORS
Explanation:
User Response:
SQID00 = 30,
4-3
You are attempting to use more than 10 internally defined SQL cursors.
You should free up a cursor by closing it.
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.
User Response:
SQID00 = 101,
12,288 BYTES
None.
SQL STATEMENT TOO LONG. XPEDITER FOR DB2 EXTENSION ALLOWS UP TO
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:
SQID00 = 102,
Reduce the original length by eliminating unnecessary blanks.
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:
SQID01 = 4,
Check for a spelling error.
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.
User Response:
SQID01 = 5,
None.
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.
User Response:
SQID01 = 6,
Check for spelling errors.
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.
User Response:
SQID01 = 8,
Check for spelling errors.
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:
User Response:
SQID02 = 21,
None.
REQUEST FUNCTION NOT KNOWN (INTERNAL ERROR)
Explanation:
User Response:
SQID02 = 22,
An invalid request was made to ADSQID01. This is an internal error.
This is an internal error.
Contact Compuware Customer Support.
DATATYPE IN SQLDA NOT KNOWN
Explanation:
This is an internal error.
4-4
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
SQID02 = 23,
NO STORAGE TO OBTAIN. SQLD PROBABLY SET TO ZERO
Explanation:
User Response:
SQID20 = 1,
This is an internal error.
Contact Compuware Customer Support.
SQLDA IS IN ERROR, SQLD=0
Explanation:
User Response:
SQID20 = 2,
Contact Compuware Customer Support.
The SQLDA field has a zero value. This should not occur.
Contact Compuware Customer Support.
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.
User Response:
SQIF00 = 1,
None.
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.
User Response:
SQIG00 = 1,
NO ROWS TO DISPLAY
Explanation:
User Response:
SQIG01 = 1,
User Response:
None.
An invalid command or option was entered.
Check for a misspelled command and reenter.
INVALID LINE COMMAND ENTERED
Explanation:
User Response:
SQIP00 = 1,
No rows were found to display.
INVALID COMMAND
Explanation:
SQIG01 = 2,
None.
The line command entered is not recognized as a valid command.
Check for a misspelled line command.
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
Explanation:
User Response:
SQIRD0 = 2,
User Response:
An SQL error occurred.
Contact your internal technical support.
NO MORE ROWS TO FETCH
Explanation:
User Response:
SQIR00 = 1,
Check for a misspelled command or option and reenter.
SQL ERROR
Explanation:
SQIRD0 = 3,
An invalid command or option was entered.
No more rows were found to fetch.
None.
INVALID COMMAND/OPTION ENTERED
Explanation:
User Response:
An invalid command or option was entered.
Check for a misspelled command or option and reenter.
Xpediter for DB2 Extension Run-Time Messages
SQIR00 = 2,
ERROR IN SELECT + DB2 ERROR MESSAGE
Explanation:
User Response:
SQIR00 = 3,
User Response:
User Response:
User Response:
User Response:
User Response:
User Response:
Contact your internal technical support.
An invalid line command was entered.
Check for the misspelled command and reenter.
An SQL error occurred in Report Select.
Contact your internal technical support.
An SQL error occurred in Report Delete.
Contact your internal technical support.
ERROR IN PRINT + DB2 ERROR MESSAGE
Explanation:
User Response:
SQIR03 = 4,
An SQL error occurred in Report Browse.
ERROR IN DELETE + DB2 ERROR MESSAGE
Explanation:
SQIR03 = 3,
Contact your internal technical support.
ERROR IN SELECT + DB2 ERROR MESSAGE
Explanation:
SQIR03 = 2,
An SQL error occurred in Report Print.
INVALID LINE COMMAND ENTERED
Explanation:
SQIR03 = 1,
Contact your internal technical support.
ERROR IN BROWSE + DB2 ERROR MESSAGE
Explanation:
SQIR00 = 6,
An SQL error occurred in Report Delete.
ERROR IN PRINT + DB2 ERROR MESSAGE
Explanation:
SQIR00 = 5,
Contact your internal technical support.
ERROR IN DELETE + DB2 ERROR MESSAGE
Explanation:
SQIR00 = 4,
An SQL error occurred in Report Select.
An SQL error occurred in Report Print.
Contact your internal technical support.
INVALID LINE COMMAND ENTERED
Explanation:
User Response:
An invalid line command was entered.
Check for the misspelled command and reenter.
4-5
4-6
Xpediter/TSO and Xpediter/IMS Messages and Codes
5-1
Chapter 5.
Unsuccessful SQL Error Codes
USQL -007
Chap 5
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:
occurred:
This SQL statement is unacceptable to DB2. One of the following actions has
– 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.
5-2
Xpediter/TSO and Xpediter/IMS Messages and Codes
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:
float literal.
The indicated “literal” begins with a digit, but is not valid integer, decimal, or
User Response:
USQL -104
Correct the invalid literal.
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:
USQL -105
Correct the statement and execute it again.
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
5-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:
USQL -108
Choose a shorter name for the object.
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:
USQL -109
Remove the qualifier and reissue the statement.
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:
USQL -110
Correct the SQL statement.
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:
USQL -111
Correct the invalid literal.
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.
5-4
Xpediter/TSO and Xpediter/IMS Messages and Codes
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:
USQL -114
Correct the name.
THE LOCATION NAME location DOES NOT MATCH THE CURRENT SERVER
Explanation:
statements:
A 3-part SQL procedure name was provided for one of the following SQL
ASSOCIATE LOCATORS
CALL
DESCRIBE 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 resolve the 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
COLUMNS
THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NUMBER OF OBJECT
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
Unsuccessful SQL Error Codes
5-5
subselect to that copy. Refer to the SQL Reference Manual for additional information regarding
the syntax of SQL statements.
USQL -119
CLAUSE
A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED IN THE GROUP BY
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:
only once.
Correct the syntax of the statement so that each column name is specified
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
RESULT
AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE
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
CLAUSE
THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY
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.
5-6
Xpediter/TSO and Xpediter/IMS Messages and Codes
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:
syntax.
The use of NULL in the search condition does not conform to the rules of SQL
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:
table names.
A subselect (including all subqueries) can have a maximum of 15 references to
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:
USQL -132
Check the data type of every operand.
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.
Unsuccessful SQL Error Codes
5-7
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
AND
VERSION = 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
AND
VERSION = version-name AND
SECTNO = number
AND
BINDERROR = "Y";
5-8
Xpediter/TSO and Xpediter/IMS Messages and Codes
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.SYSSTMT
WHERE SECTNO = 0
ORDER BY NAME,PLNAME,STMTNO,SEQNO;
When executing from a package, use:
SELECT *
FROM SYSIBM.SYSPACKSTMT
WHERE SECTNO = 0
ORDER 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 can be 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.
Unsuccessful SQL Error Codes
5-9
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:
statement.
USQL -153
Drop the existing object with the correct DROP clause of the ALTER TABLE
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.
5-10
Xpediter/TSO and Xpediter/IMS Messages and Codes
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.
Unsuccessful SQL Error Codes
USQL -173
5-11
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
VALUE
THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME
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 RANGE
Years
0001 to 9999
Months
1 to 12
Days April, June,
1 to 30
September, November
1 to 30
(months 4,6,9,11)
1 to 30
February (month 2)
1 to 28
(Leap Year
is 1 to 29)
January, March,
1 to 31
May, July, August
1 to 31
October, December
1 to 31
(months 1,3,5,7,
1 to 31
8,10,12)
1 to 31
Hours
0 to 24
(If the hour
is 24, other
parts of time
values are
zeroes. If
the hour is
USA, maximum
hour is 12.)
Minutes
0 to 59
Seconds
0 to 59
Microseconds
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.
5-12
Xpediter/TSO and Xpediter/IMS Messages and Codes
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
MARKER
AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER
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:
exit.
Contact the system programmer regarding installation of the date or time
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.
Unsuccessful SQL Error Codes
USQL -189
5-13
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:
USQL -198
EMPTY
The statement is not executed.
THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANK OR
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.
5-14
Xpediter/TSO and Xpediter/IMS Messages and Codes
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:
table-name.
No column with the specified column-name occurs in the table or view
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.
Unsuccessful SQL Error Codes
USQL -220
PROPELY
5-15
THE COLUMN column-name IN EXPLANATION TABLE table-name IS NOT DEFINED
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:
reasons:
The LOCK TABLE statement has become invalid for one of the following
– 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:
USQL -251
Define the local location name and then retry the function.
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:
5-16
Xpediter/TSO and Xpediter/IMS Messages and Codes
–
–
–
–
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.
Unsuccessful SQL Error Codes
5-17
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
VALUE
A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL
Explanation: The statement could not be processed because a host variable appearing in a
predicate such as:
column-name = host variable
had 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 issued
as a result of an INSERT, UPDATE, DELETE, or SELECT statement), or
the parameter number (provided the message is issued as the result of
a 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.
5-18
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
–
–
–
–
The
The
The
The
Verify that the following items have been completed:
variable name is spelled properly in the SQL statement.
variable is allowed in the SQL statement.
application program contains a declaration for that variable.
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

12

16

20

24
Length exception (for example,
expansion required for PC MIXED
data exceeds the maximum length
of the string).
Invalid code point (for example,
use of the ERRORBYTE option of
SYSSTRINGS).
Form exception (for example,
invalid MIXED data).
Translate procedure error
(for example, an exit set
the length control field of
the string to an invalid
value).
SBCS character was found in
a string contained in a
wchar_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:
Unsuccessful SQL Error Codes
5-19
– 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.
5-20
Xpediter/TSO and Xpediter/IMS Messages and Codes
– 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.
Unsuccessful SQL Error Codes
5-21
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
RANGE
THE NUMERIC LITERAL literal CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OF
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.
5-22
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
USQL -411
OBJECTS
Correct the indicated literal.
CURRENT SQLID CANNOT BE USED IN A STATEMENT THAT REFERENCES REMOTE
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:
remote object.
USQL -412
Remove the reference to CURRENT SQLID or remove the reference to the
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.
Unsuccessful SQL Error Codes
5-23
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
MARKERS
A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE OF PARAMETER
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.
User Response:
None.
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
COLUMNS
THE OPERANDS OF A UNION OR A UNION ALL DO NOT HAVE THE SAME NUMBER OF
Explanation:
columns.
The operands of a UNION or UNION ALL must have the same number of
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:
environments.
The IMS or CICS protocols should be used to commit work in these
5-24
Xpediter/TSO and Xpediter/IMS Messages and Codes
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:
environments.
The IMS or CICS protocols should be used to rollback work in these
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

authid

luname

number
User Response:
The name of the stored
procedure from the
PROCEDURE field in
SYSIBM.SYSPROCEDURES.
The authorization id from
the AUTHID field in
SYSIBM.SYSPROCEDURES.
The logical unit name
from the LUNAME field in
SYSIBM.SYSPROCEDURES.
The expected number of
parameters for the stored
procedure with the NAME,
AUTHID, and LUNAME
described above.
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 MVS
load module that
could 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.
Unsuccessful SQL Error Codes
5-25
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

number
The name of the stored
procedure from the
NAME field in the
SYSIBM.SYSPROCEDURES
catalog table.
The parameter from the
PARMLIST field in the
SYSIBM.SYSPROCEDURES
catalog 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
number
SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST VARIABLE FOR PARAMETER
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 number
from the PARMLIST field
in 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 number
from the PARMLIST field
in 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 name 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:
5-26
Xpediter/TSO and Xpediter/IMS Messages and Codes
name

rc
The DB2 reason code
describing the cause
of the failure. The
possible values are:
00E79000, 00E79001,
00E79002, 00E79003,
00E79004, 00E79005,
00E79006, 00E79007,
00E7900B, and 00E7900C.
User Response:
USQL -480
The name of the stored
procedure specified
on the SQL CALL
statement.
Correct the condition described by the DB2 reason code.
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:
USQL -482
Correct the order of the statements and rerun them.
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
Unsuccessful SQL Error Codes
5-27
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.
5-28
Xpediter/TSO and Xpediter/IMS Messages and Codes
– 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.
Unsuccessful SQL Error Codes
5-29
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
Explanation:
One of the following conditions exists:
– 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
ALIAS
THE ALIAS alias-name MUST NOT BE DEFINED ON ANOTHER LOCAL OR REMOTE
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.
5-30
Xpediter/TSO and Xpediter/IMS Messages and Codes
User Response:
tables or views.
USQL -514
Modify the SQL statement to ensure that all object references are to base
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
Explanation:
One of the following conditions exists:
– 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.
Unsuccessful SQL Error Codes
5-31
– 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
5-32
Xpediter/TSO and Xpediter/IMS Messages and Codes