Manual de Erros

OS/390 IBM
MVS System Messages

Volume 3 (EWX - IEB)
GC28-1786-16
OS/390 IBM
MVS System Messages

GC28-1786-16
Note
Before using this information and the product it supports, be sure to read the general information under “Appendix. Notices”
on page 789.
Seventeenth Edition, December 2001

This is a major revision of GC28-1786-15.
This edition applies to OS/390 Version 2 (5647-A01) and to all subsequent releases and modifications until otherwise
indicated in new editions.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are
not stocked at the address below.
IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, or you
may address your comments to the following address:
International Business Machines Corporation
Department 55JA, Mail Station P384
2455 South Road
Poughkeepsie, NY 12601-5400
United States of America
FAX (United States & Canada): 1+845+432-9405

FAX (Other Countries):
Your International Access Code +1+845+432-9405
IBMLink (United States customers only): IBMUSM10(MHVRCFS)

Internet e-mail: mhvrcfs@us.ibm.com
World Wide Web: http://www.ibm.com/s390/os390/webqs.html
If you would like a reply, be sure to include your name, address, telephone number, or FAX number.
Make sure to include the following in your comment or note:
v Title and order number of this book
v Page number or topic related to your comment
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1988, 2001. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Who Should Use These MVS System Messages Books . . . . . . . . . . . . . . . . . . . v
How to Use These Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Using LookAt to look up message explanations . . . . . . . . . . . . . . . . . . . . . . vi
Where to Find the Most Current Message Information . . . . . . . . . . . . . . . . . . . vi
Where to Find More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Subsystem, Product, and Hardware Books . . . . . . . . . . . . . . . . . . . . . . vii
Message Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Message Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Message Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Hard-Copy Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
SYSOUT Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
How Messages are Explained in this Book. . . . . . . . . . . . . . . . . . . . . . . 5
Messages Sent to MCS Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Messages Sent to Hard-Copy Log in JES2 System . . . . . . . . . . . . . . . . . . . 7
Messages Sent to Hard-Copy Log in JES3 System . . . . . . . . . . . . . . . . . . . 8
Messages Sent to the Job Log, to Other Data Sets, and to Display Terminals . . . . . . . . . 10
Truncated Data in Multi-line Messages. . . . . . . . . . . . . . . . . . . . . . . . 11
A Method for Finding Changes to MVS and TSO/E Message Texts . . . . . . . . . . . . . . 11
Using SYS1.MSGENU to Find Message Text Changes . . . . . . . . . . . . . . . . . . 11
Chapter 2. LANRES Messages (EWX, ACP, ASD) . . . . . . . . . . . . . . . . . . . . 13

EWX Host Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
EWX Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Chapter 3. EZM Application Enabling Technology Messages. . . . . . . . . . . . . . . 149
Chapter 4. GDE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Chapter 5. GFSA Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Chapter 6. GFSC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Chapter 7. GOS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Chapter 8. GPM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Chapter 9. IAR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Chapter 10. ICP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Chapter 11. ICT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
© Copyright IBM Corp. 1988, 2001 iii

Chapter 12. ICU Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Chapter 13. IDA Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Chapter 14. IDC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Chapter 15. IEA Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Chapter 16. IEB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Appendix. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
iv OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

About This Book
The MVS System Messages books primarily describe messages that are issued to the system operator at
the system console and system messages that are logged. These include:
v Operator messages issued by the BCP and DFSMS/MVS.
v Log messages issued by the BCP and DFSMS/MVS.
v Some SYSOUT messages issued by the BCP and DFSMS/MVS. SYSOUT messages are issued by
utilities that normally run in batch, such as SPZAP.
v Batch job messages issued by the BCP. Messages issued by JES2 or JES3 for batch jobs are in the
JES messages books.
For the most part, messages issued at interactive terminals (like TSO/E and CICS terminals) are
documented by the specific elements and products that support those terminals.
The titles of the MVS System Messages books indicate the range of message prefixes in the books:
v OS/390 MVS System Messages, Vol 1 (ABA-ASA), GC28-1784
v OS/390 MVS System Messages, Vol 2 (ASB-ERB), GC28-1785
v OS/390 MVS System Messages, Vol 3 (EWX-IEB), GC28-1786
v OS/390 MVS System Messages, Vol 4 (IEC-IFD), GC28-1787
v OS/390 MVS System Messages, Vol 5 (IGD-IZP), GC28-1788
If you do not know which book describes a particular message, try searching the messages and codes
bookshelf. Here are some of the books on that bookshelf:
v The MVS System Messages books
v OS/390 MVS Dump Output Messages, GC28-1749
v OS/390 MVS System Codes, GC28-1780
v OS/390 MVS Routing and Descriptor Codes, GC28-1778
v OS/390 HCD Messages, GC28-1849
v OS/390 JES2 Messages, GC28-1796
v OS/390 JES3 Messages, GC28-1804
v OS/390 TSO/E Messages, GC28-1978
v OS/390 UNIX System Services Messages and Codes, SC28-1908
For a list of message books sorted by message prefix, see “Message Directory” on page ix.
Who Should Use These MVS System Messages Books

The system messages books are for all people who receive messages from the system. Usually, these
people are system operators, system programmers, and application programmers who do any of the
following tasks:
v Initialize the operating system and its subsystems
v Monitor system activity
v Keep the system running correctly
v Diagnose and correct system problems
v Diagnose and correct errors in problem programs
How to Use These Books

The system messages books contain descriptions of messages, along with the following:
v “Message Library” on page viii tells how to create a customized message library
© Copyright IBM Corp. 1988, 2001 v

v “Message Directory” on page ix lists all message prefixes and the books containing the message
descriptions
v “Chapter 1. Introduction” on page 1 describes how the system issues messages, where it places them,
and their formats
Message Explanations: Message chapters are arranged alphabetically by the message prefixes. In each
chapter, the messages are arranged numerically by the numbers following the prefix. For a general
description of message explanations, see “How Messages are Explained in this Book” on page 5.
Using LookAt to look up message explanations

LookAt is an online facility that allows you to look up explanations for OS/390 messages and system
abends.
Using LookAt to find information is faster than a conventional search because LookAt goes directly to the
explanation.
LookAt can be accessed from the Internet or from a TSO command line.
You can use LookAt on the Internet at:

http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookat.html
To use LookAt as a TSO command, LookAt must be installed on your host system. You can obtain the
LookAt code for TSO from the LookAt Web site by clicking on News and Help or from the IBM Online
Library Omnibus Edition OS/390 Collection, SK2T-6700.
To find a message explanation from a TSO command line, simply enter: lookat message-id as in the
following example:
lookat iec192i
This results in direct access to the message explanation for message IEC192I.
To find a message explanation from the LookAt Web site, simply enter the message ID. You can select the
release if needed.
Note: Some messages have information in more than one book. For example, IEC192I has routing and
descriptor codes listed in OS/390 MVS Routing and Descriptor Codes. For such messages, LookAt
prompts you to choose which book to open.
Where to Find the Most Current Message Information

The MVS System Messages books are cumulative. As messages are added to the system they are added
to the books. Similarly, when messages are changed on the system, they are changed in the books.
However, when a message is deleted from the system (no longer issued), the message is not deleted from
the book. This means that users can look in the most recent message books for the most current
descriptions of system messages.
To find the most current edition of a book, you can look on the Web. Point your browser to the OS/390
home page and click on Library:
http://www.ibm.com/s390/os390/
When you are in the OS/390 library area, use the messages and codes database to search for the
message ID you are interested in.
vi OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Where to Find More Information
Many message descriptions refer to:
v Data areas and control blocks: See OS/390 MVS Data Areas, Vol 1 (ABEP-DALT), OS/390 MVS Data
Areas, Vol 2 (DCCB-ITZYRETC), OS/390 MVS Data Areas, Vol 3 (IVT-RCWK), OS/390 MVS Data
Areas, Vol 4 (RD-SRRA), and OS/390 MVS Data Areas, Vol 5 (SSAG-XTLST).
v Dumps: For examples of ABEND, stand-alone, and SVC dumps and how to read them, see OS/390
MVS Diagnosis: Tools and Service Aids. For examples of component output from dumps and how to
read and request it, see OS/390 MVS Diagnosis: Reference.
v Identification of a component, subsystem, or product: See the OS/390 MVS Diagnosis: Reference
to identify the component, subsystem, or product from the name of an IBM module or for a macro. The
module prefix and macro tables give the program identifier to be used in a PIDS symptom in a search
argument.
v System completion and wait state codes: See OS/390 MVS System Codes.
v Logrec data set error records: For the formatted records, see OS/390 MVS Diagnosis: Reference.
v Trace output: For the formats and the meaning of the information in the generalized trace facility (GTF)
trace, instruction address trace, master trace, system trace, and component trace, see OS/390 MVS
Diagnosis: Tools and Service Aids.
The following tables list books that contain information related to the information contained in the MVS
System Messages books. For the titles and order numbers of books not in the tables, see OS/390
Information Roadmap.
Use the appropriate Principles of Operation book for the hardware you have installed.
When the MVS System Messages books reference information in other books, the shortened version of
the book title is used. The following tables show the complete titles and order numbers of the books that
you might need while you are using the MVS System Messages books.
Subsystem, Product, and Hardware Books

Title Order Number
ACF/TCAM Base Installation Guide SC30-3132
Asynchronous Adapter Device Driver Table N/A
C/370 Programming Guide N/A
CICS Family: General Information N/A
CICS Recovery and Restart Guide SC33-1698
Common I/O-Device Commands SA22-7204
CPI Communications Reference SC26-4399
DATABASE 2 Application Programming Guide SC26-4293
DFSMS/MVS DFSMSdfp Diagnosis Reference LY27-9606
DB2 Application Programming Guide for TSO and Batch Users SC26-4081
DATABASE 2 General Information Manual GC26-4073
IBM DATABASE 2 Messages SC23-0592
IBM DATABASE 2 Version 2 Messages and Codes SC26-4113
IBM DATABASE 2 Version 2 Release 3 Messages and Codes SC26-4379
IBM Graphics Access Method/SP Messages and Codes SC33-0143
ES/9000: Operating Your System SA24-4350
About This Book vii

Title Order Number
FileNet OSAR Library Unit Product Description PN9000102
IBM 3290 Information Panel Description and Reference SR23-6155
IBM 3990/9390 Operations and Recovery Guide GA32-0253
IBM 3990/9390 Storage Contro Planning, Installation, and Storage Administration GA32-0100
Guide
IBM 3990 Storage Control Reference for Model 6 GA32-0099
IBM 9340 Direct Access Storage Subsystems Reference GC26-4647
LASERDRIVE** 1200 Engineering Specification N/A
LASERDRIVE** 1200 Intelligent Digital Optical Disk Drive with SCSI Engineering N/A
Specification
Maintaining IBM Storage Subsystem Media GC26-4495
Maintenance Information for the 9037 Sysplex Timer SY27-2605
Maintaining IBM Storage Subsystem Media GC26-4495
OS/2 Programming Tools and Info V-1.3 Manage Macro Assembler/2 Z91F-9269
OS/2 WARP Control Program Programming Reference N/A
Portable Netware System Messages SC23-2424
Print Services Access Facility/MVS User’s Guide and Reference S544-3100
IBM Enterprise Systems Architecture/390 Principles of Operation SA22-7201
Remote Copy Administrator’s Guide and Reference SC35-0169
SCSI Adapter Completion Code Table N/A
RT SCSI Adapter Device Driver Table N/A
Sysplex Timer 9037 Maintenance SY27-2605
VM/ESA CP Command and Utility Reference SC24-5519
VM/ESA General User Command Reference SC24-5433
Message Library
The message library is designed so that operators and programmers in an installation can build their own
libraries of the message and code information that fits their specific needs. Each person can place into
binders the chapters and books containing only the messages and codes he or she could receive.
Basic Books
Each installation requires at least one copy of each of the MVS System Messages books and of OS/390
MVS Dump Output Messages. Regardless of your specific system’s options, you will receive at the
console or in listings some subset of the messages in these books.
Each installation also requires at least one copy of OS/390 MVS System Codes, which contains the 3-digit
hexadecimal system completion codes (abend codes) and the wait state codes produced by all the
components of the system.
Note: 4-digit decimal user completion codes appear in books for the component, subsystem, or product
that produces the codes. Codes produced by installation-provided programs do not appear in IBM
books.
All programming and operations personnel need access to the basic books, although application
programmers might not need to have their own copies.
viii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Optional Books
For information about message changes for multiple OS/390 elements including JES2, JES3, RACF,
TCP/IP, and others, see OS/390 Summary of Message Changes.
An installation’s system programmer needs OS/390 MVS Routing and Descriptor Codes for the routing
and descriptor codes for the messages that have these codes.
CD-ROM Collection
A comprehensive source of messages for IBM products is contained in the IBM Online Library Productivity
Edition: Messages and Codes Collection, SK2T-2068.
Message Directory
To use a message prefix to locate the book containing a specific message, see the following table.
Prefix Component Book Title - Order Number

ABA DFSMShsm OS/390 MVS System Messages, Vol 1
(ABA-ASA), GC28-1784
ACP LANRES OS/390 MVS System Messages, Vol 2
(ASB-ERB), GC28-1785
ADF Time Sharing Option Extensions (TSO/E) OS/390 TSO/E User’s Guide, SC28-1968
session manager
OS/390 TSO/E Command Reference,
SC28-1881
OS/390 TSO/E Messages, GC28-1978

ADM Graphical data display manager GDDM Messages, SC33-0869
ADR DFDSS OS/390 MVS System Messages, Vol 1
ADRY DFDSS OS/390 MVS System Messages, Vol 1
ADY Dump analysis and elimination (DAE) OS/390 MVS System Messages, Vol 1
AEM Graphical data display manager GDDM Messages, SC33-0869
AFB VSFORTRAN VSFORTRAN Version 2 Language and Library
Reference, SC26-4221
AHL Generalized trace facility (GTF) OS/390 MVS System Messages, Vol 1
OS/390 MVS Dump Output Messages,

GC28-1749
AMA SPZAP service aid OS/390 MVS System Messages, Vol 1
AMB LIST service aid OS/390 MVS System Messages, Vol 1
AMD Stand-alone dump OS/390 MVS System Messages, Vol 1
AMS Availability manager OS/390 MVS System Messages, Vol 1
RMF Messages and Codes, GC28-1948

ANT Remote Copy OS/390 MVS System Messages, Vol 1
About This Book ix

ANF Starting with Release 8: Infoprint Server OS/390 Infoprint Server Messages and
Diagnosis, G544-5690
AOF System Automation for OS/390 System Automation for OS/390 Messages and
Codes, SC33-7041
AOM Administrative operations manager OS/390 MVS System Messages, Vol 1
AOP Infoprint server OS/390 Infoprint Server Messages and
API Starting with Release 8: Infoprint Server OS/390 Infoprint Server Messages and
APS Print services facility (PSF) Print Services Facility Messages, S544-3675
ARC DFSMShsm OS/390 MVS System Messages, Vol 1
ARRP System Control Program (SCP) See message 52099 in Enterprise System/9000
Models 190, 210, 260, 320, 440, 480, 490, 570,
and 610 Messages Part 2 for a complete
message explanation and appropriate
responses; see GA23-0378
ASA MVS Reuse OS/390 MVS System Messages, Vol 1
ASB Advanced Program-to-Program OS/390 MVS System Messages, Vol 2
Communications/MVS (APPC/MVS) (ASB-ERB), GC28-1785

GC28-1749
ASD LANRES OS/390 MVS System Messages, Vol 2
ASM Auxiliary storage manager (ASM) OS/390 MVS Dump Output Messages,
GC28-1749
ASMA High Level Assembler for MVS & VM & VSE HLASM Programmer’s Guide, SC26-4941
ASR Symptom record (SYMREC) OS/390 MVS Dump Output Messages,
GC28-1749
ATB Advanced Program-to-Program OS/390 MVS System Messages, Vol 2
Communications/MVS (APPC/MVS) (ASB-ERB), GC28-1785

GC28-1749
ATR Resource recovery services (RRS) OS/390 MVS System Messages, Vol 2

GC28-1749
AVM Availability manager OS/390 MVS System Messages, Vol 2
BFS IBM LAN server for MVS OS/390 MVS System Messages, Vol 2
BLG Information System, Information Management The Information/Management Library Messages
and Codes, SC34-4459
BLM Information System, Information Management The Information/Management Library Messages
x OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

BLS Interactive problem control system (IPCS) OS/390 MVS System Messages, Vol 2

GC28-1749
BLX Information System, Information Management The Information/Management Library Messages
BLW Loadwait/Restart OS/390 MVS System Messages, Vol 2
BNH Network Problem Determination Application NPDA Messages, SC34-2115
(NPDA)
BPX OS/390 UNIX System Services OS/390 MVS System Messages, Vol 2

GC28-1749
CBDA Hardware configuration definition (HCD) OS/390 MVS System Messages, Vol 2
OS/390 HCD Messages, GC28-1849

CBR Object access method (OAM) OS/390 MVS System Messages, Vol 2
CEE Language Environment OS/390 Language Environment Debugging
Guide and Run-Time Messages, SC28-1942
CHS MVSSERV messages for the user and system OS/390 TSO/E Messages, GC28-1978
programmer
CMP Compression management services OS/390 MVS System Messages, Vol 2
CNL MVS message service (MMS) OS/390 MVS System Messages, Vol 2

GC28-1749
COF Virtual lookaside facility (VLF) OS/390 MVS System Messages, Vol 2

GC28-1749
OS/390 TSO/E Messages, GC28-1885

CSQ MQSeries MQSeries for OS/390 V2R1 Messages and
Codes, GC34-5375
CSR Callable services requests (CSR) OS/390 MVS System Messages, Vol 2

GC28-1749
CSV Contents supervision, virtual fetch, fetch OS/390 MVS System Messages, Vol 2

GC28-1749
CSY OPC/A Production Control System OPC/A Messages, SH19-6448
About This Book xi

CSZ OPC/A Network Event Communicator OPC/A Messages, SH19-6448
DFH Customer Information Control System/Virtual CICS/ESA Messages and Codes, SC33-0672
Storage (CICS/VS)
DLX DLF installation exit COFXDLF2 These messages are issued by the sample DLF
installation exit, COFXDLF2, whose source can
be found in SYS1.SAMPLIB. Because the
issuing module is a ″sample″, which can be
modified by the customer, the messages are not
described in an IBM book.
DMO Device Manager OS/390 MVS System Messages, Vol 2

GC28-1749
DQD Cache RMF Reporter (CRR) Cache RMF Reporter Program
Description/Operations Manual, SH20-6295
DRK OPC/A Event Manager Subsystem OPC/A Messages, SH19-6448
DSI NetView TME 10 NetView for OS/390 Messages,
SC31-8237
DSM Document Composition Facility DCF: Messages, SH35-0048
DSM Document Library Facility DCF: Messages, SH35-0048
DSN Database 2 DB2 Universal Database for OS/390 Messages
and Codes, GC26-9011
DZI Overlay Generation Language IBM Overlay Generation Language/370 User’s
Guide and Reference, S544-3702
DZJ Print Management Facility Print Management Facility User’s Guide and
Reference, SH35-0059
EDC C/C++ Run-time Library OS/390 Language Environment Debugging
EDG DFSMSrmm OS/390 MVS System Messages, Vol 2
EQQ OPC/ESA OPC/ESA Messages and Codes, SH19-6719
ERB Resource Measurement Facility (RMF) OS/390 MVS System Messages, Vol 2
RMF Messages and Codes, GC28-1948

ERX Graphical data display manager GDDM Messages, SC33-0869
EWX LANRES OS/390 MVS System Messages, Vol 3
(EWX-IEB), GC28-1786
EZA OS/390 SecureWay Communication Server — IP OS/390 eNetwork Communications Server: IP
Messages Volume 1, SC31-8517
EZB OS/390 SecureWay Communication Server — IP OS/390 eNetwork Communications Server: IP
xii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

EZM Application Enabling Technology (AET)/Auto OS/390 Application Enabling Technology:
UNIX System Administration and Programming, GC28-1993
OS/390 Application Enabling Technology:

Customization Guide, GC28-1994
OS/390 MVS System Messages, Vol 3

EZY OS/390 SecureWay Communication Server — IP OS/390 eNetwork Communications Server: IP
EZZ OS/390 SecureWay Communication Server — IP OS/390 eNetwork Communications Server: IP
FDBX UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FLM Software configuration and library manager OS/390 ISPF Messages and Codes, GC28-1326
FOMC UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FOMF UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FOMI UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FOMM UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FOMO UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FOMOA UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FOMOG UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FOMOH UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FSUM UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FSUMA UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FSUMB UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FSUMF UNIX System Services OS/390 UNIX System Services Messages and
Codes, SC28-1908
FOR LE FORTRAN Library IBM Language Environment for MVS & VM
FORTRAN Run-Time Migration Guide,
SC26-8499
GDE Distributed FileManager/MVS (DFM/MVS) OS/390 MVS System Messages, Vol 3
GFSA Network File System Server OS/390 MVS System Messages, Vol 3
GFSC Network File System Server Client Messages OS/390 MVS System Messages, Vol 3
GIM SMP/E OS/390 SMP/E Messages and Codes,
SC28-1738
About This Book xiii

GQD Graphical data display manager GDDM Messages, SC33-0869
GQF Graphical data display manager GDDM Messages, SC33-0869
HASP JES2, network job entry facility for JES2 OS/390 JES2 Messages, GC28-1796
IAR Real storage manager (RSM) OS/390 MVS System Messages, Vol 3

GC28-1749
IAT JES3 OS/390 JES3 Messages, GC28-1804
ICE DFSORT sort program DFSORT Messages, Codes and Diagnosis
Guide R14, SC26-7050
ICH Resource Access Control Facility (RACF) OS/390 SecureWay Security Server RACF
Messages and Codes, SC28-1918
ICK Device Support Facilities Device Support Facilities User’s Guide and
Reference, GC35-0033
ICN NCP/SSP/EP NCP/SSP/EP Messages and Codes, SC30-3169
ICP Input/Output Configuration Program (IOCP) OS/390 MVS System Messages, Vol 3
Input/Output Configuration Program User’s Guide

and Reference, GC28-1027
ICQA Information Center Facility administrator OS/390 TSO/E Messages, GC28-1978
messages
ICQC Information Center Facility user messages OS/390 TSO/E Messages, GC28-1978
ICT Programmed Cryptographic Facility OS/390 MVS System Messages, Vol 3
ICU Cryptographic Unit Support OS/390 MVS System Messages, Vol 3
IDA Virtual storage access method (VSAM) control OS/390 MVS System Messages, Vol 3
block expansion (EWX-IEB), GC28-1786
IDC Access method devices OS/390 MVS System Messages, Vol 3
xiv OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

IEA v Allocation/unallocation OS/390 MVS System Messages, Vol 3
v Auxiliary storage manager (ASM)
v Contents supervision OS/390 MVS Dump Output Messages,
v Communications task (COMMTASK) GC28-1749
v Data Facility Product (DFP) components
v Generalized trace facility (GTF)
v Initial program load (IPL)
v Input/output supervisor (IOS)
v Master scheduler
v Nucleus initialization program (NIP)
v Program Call authorization (PC/AUTH) service
routines
v Reconfiguration
v Recovery termination manager (RTM)
v Supervisor control
v System resources manager
v System trace
v Timer supervision
v Virtual storage management (VSM)
IEB Data Facility Product (DFP) utilities OS/390 MVS System Messages, Vol 3
IEC Data Facility Product (DFP) components OS/390 MVS System Messages, Vol 4
(IEC-IFD), GC28-1787
OS/390 DFSMSdfp Diagnosis Reference,

SY27-7611
IEE v Auxiliary storage manager (ASM) OS/390 MVS System Messages, Vol 4
v Communications task (COMMTASK)
v Data Facility Product (DFP) components OS/390 MVS Dump Output Messages,
v JES2 GC28-1749
v JES3
v Master scheduler
v Reconfiguration
v Recovery termination manager (RTM)
v Supervisor control
v System management facilities (SMF)
v System resources manager (SRM)
v System trace
v Task management
v Timer supervision
About This Book xv

IEF v Allocation/unallocation OS/390 MVS System Messages, Vol 4
v Converter/interpreter
v Data Facility Product (DFP) components OS/390 MVS Dump Output Messages,
v Initial program load (IPL) GC28-1749
v Initiator/terminator
v JES/scheduler services
v JES2
v Master scheduler
v Master subsystem/subsystem interface (MSI)
v Reconfiguration
v Scheduler JCL facilities (SJF)
v Scheduler restart
v Scheduler services (ENF)
v System management facilities (SMF)
IEFC Converter OS/390 MVS System Messages, Vol 4
IEFI Converter/interpreter OS/390 MVS System Messages, Vol 4
IEH Data Facility Product (DFP) utilities OS/390 MVS System Messages, Vol 4
IEV Assembler H Assembler H Version 2 Application
Programming: Guide, SC26-4036
IEW DFSMS (Linkage editor, Binder, Transport utility), OS/390 MVS System Messages, Vol 4
Loader (IEC-IFD), GC28-1787
IFA System management facilities (SMF) OS/390 MVS System Messages, Vol 4

GC28-1749
IFB Input/output environment recording routines: OS/390 MVS System Messages, Vol 4
OBR and SVC 76 (IEC-IFD), GC28-1787
IFC IFCDIP00 service aid for the logrec data set OS/390 MVS System Messages, Vol 4
IFCEREP0 and IFCEREP1 service aids
Environmental Record Editing and Printing
Program (EREP) User’s Guide and Reference,
GC28-1378
IFD Online test executive program (OLTEP) OS/390 MVS System Messages, Vol 4
IFL Network Control Program (NCP) 3704 and 3705 Control Program Generation and
Utilities Guide and Reference Manual,
Advanced Communications Function (ACF) for GC30-3008
Network Control Program (NCP)
Network Control Program/System Support
Programs/Emulation Programs Messages and
Codes, SC30-3169
IFO MVS Assembler OS/VS - VM/370 Assembler Programmer’s
Guide, GC33-4021
xvi OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

IGD Storage management subsystem (SMS) of Data OS/390 MVS System Messages, Vol 5
Facility Product (DFP) (IGD-IZP), GC28-1788

GC28-1749
IGF Dynamic device reconfiguration (DDR) Machine OS/390 MVS System Messages, Vol 5
check handler (MCH) (IGD-IZP), GC28-1788
IGGN Data Facility Product (DFP) OS/390 MVS System Messages, Vol 5
(IGD-IZP), GC28-1788
IGV Virtual storage management (VSM) OS/390 MVS System Messages, Vol 5
IGW Data Facility Product (DFP) Storage OS/390 MVS System Messages, Vol 5
management subsystem (SMS) (IGD-IZP), GC28-1788

GC28-1749
IGY VS COBOL II VS COBOL II Application Programming Guide,
SC26-4045
IGZ VS COBOL II VS COBOL II Application Programming:
Debugging, SC26-4049,
OS/390 Language Environment Debugging

IHJ Data Facility Product (DFP) checkpoint/scheduler OS/390 MVS System Messages, Vol 5
restart (IGD-IZP), GC28-1788
IKF VS COBOL II VS COBOL II Application Programming:
Debugging, SC26-4049
IKJ Time Sharing Option Extensions (TSO/E) OS/390 TSO/E Messages, GC28-1978


GC28-1749
IKM Programming Language/I (PL/I) syntax checker OS/390 MVS System Messages, Vol 5
IKT Time Sharing Option Extensions (TSO/E) OS/390 TSO/E Messages, GC28-1978,
SC27-0614, SC27-0470, SC23-0114
Advanced Communications Function for Virtual
Telecommunications Access Method VTAM Messages and Codes, SC31-6333
(ACF/VTAM)
ILR Auxiliary storage manager (ASM) OS/390 MVS System Messages, Vol 5
ILX VS FORTRAN Compiler VS FORTRAN Version 2 Programming Guide for
CMS and MVS, SC26-4222
IHV System Automation for OS/390 System Automation for OS/390 Messages and
Codes
ING System Automation for OS/390 System Automation for OS/390 Messages and
Codes, SC33-7041
ISQ System Automation for OS/390 System Automation for OS/390 Messages and
Codes, SC33-7041
About This Book xvii

INM Interactive Data Transmission Facility (IDTF) OS/390 TSO/E Messages, GC28-1978
TRANSMIT and RECEIVE commands
IOAC Open Systems Adapter-Express (OSA-Express) OSA-Express Customer’s Guide and Reference,
SA22-7403
IOP Input/output configuration program (IOCP) OS/390 MVS System Messages, Vol 5
ES/3090 Processor Complex IOCP User’s Guide

and Reference, SC38-0066
IOS Input/output supervisor (IOS) OS/390 MVS System Messages, Vol 5

GC28-1749
IPD FORTRAN syntax checker OS/390 MVS System Messages, Vol 5
IRA System resources manager (SRM) OS/390 MVS System Messages, Vol 5

GC28-1749
IRD ESCON Director Device Support (EDDS) OS/390 MVS System Messages, Vol 5
IRR Resource Access Control Facility (RACF) OS/390 SecureWay Security Server RACF
Messages and Codes, SC28-1918
IRX Time Sharing Option Extensions (TSO/E) OS/390 TSO/E Messages, GC28-1978
restructured extended executor language
(REXX)
ISG Global resource serialization OS/390 MVS System Messages, Vol 5

GC28-1749
ISN Service Processor Interface OS/390 MVS System Messages, Vol 5
ISP Interactive system productivity facility OS/390 ISPF Messages and Codes, GC28-1326
ISQ System Automation for OS/390 System Automation for OS/390 Messages and
Codes
ISRB Interactive system productivity facility OS/390 ISPF Messages and Codes, GC28-1326
ISRL Library management facility OS/390 ISPF Messages and Codes, GC28-1326
IST Advanced Communications Function for Virtual Advanced Communications Function for VTAM
Telecommunications Access Method Messages and Codes, SC27-0614, SC27-0470,
(ACF/VTAM) SC23-0114
ITA TOLTEP for Advanced Communications Function Advanced Communications Function for VTAM
for Virtual Telecommunications Access Method Messages and Codes, SC27-0614, SC27-0470,
(ACF/VTAM) SC23-0114
ITT Component trace OS/390 MVS System Messages, Vol 5

GC28-1749
xviii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

ITV Data-in-virtual OS/390 MVS System Messages, Vol 5

GC28-1749
ITZ Transaction trace OS/390 MVS System Messages, Vol 5

GC28-1749
IWM Workload manager (WLM) OS/390 MVS System Messages, Vol 5

GC28-1749
IXC Cross-system coupling facility (XCF) OS/390 MVS System Messages, Vol 5

GC28-1749
IXG System logger (SCLOG) OS/390 MVS System Messages, Vol 5
IXL Cross System Extended Services (XES) OS/390 MVS System Messages, Vol 5

GC28-1749
IXP Input/output configuration program (IOCP) OS/390 MVS System Messages, Vol 5
ES/9000 ES/3090 IOCP User’s Guide Volume

A04, GC38-0097
IXZ JES common coupling services (JESXCF) OS/390 MVS System Messages, Vol 5

GC28-1749
IYP Input/output configuration program (IOCP) OS/390 MVS System Messages, Vol 5
zSeries 900 IOCP User’s Guide for IYP IOCP,

SB10-7029
IZP Input/output configuration program (IOCP) OS/390 MVS System Messages, Vol 5
ES/9000 IOCP User’s Guide and ESCON CTC

Reference Volume A04, GC38-0401
SNM OS/390 SecureWay Communication Server — IP OS/390 eNetwork Communications Server: IP
About This Book xix

Message Translation
Through the MVS message service (MMS), you can translate MVS system messages into other
languages. Messages that cannot be translated include the following:
v Initialization messages
v DFSMS/MVS messages
v JES3 messages
v Some complicated multiple-line messages
See OS/390 MVS Planning: Operations and OS/390 MVS Programming: Assembler Services Guide for
information about using the MMS.
xx OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Summary of Changes
Summary of Changes
for GC28-1786-16
OS/390 Version 2 Release 10
as updated December 2001
Changed Information
Changes have been made to the following messages:

v IDC3009I
v IEA310A
v IEA411I
v IEA611I
v IEA911E
v IEB352I
New Information
The following is a new message for this refresh release:

v IEB1161W
This book includes terminology, maintenance, and editorial changes. Technical changes or additions to the
text and illustrations are indicated by a vertical line ( | ) to the left of the change.
Summary of Changes
for GC28-1786-15
as updated June 2001
Changed Information
Changes have been made to the following message:

v IDC3009I
text and illustrations are indicated by a vertical line ( | ) to the left of the change.
Summary of Changes
for GC28-1786-14
as updated December, 2000
New Information
The following are the new messages for this refresh release:
v IAR013I
v IAR014I
v IAR015I
v IAR016I
v IEA050I
Changed Information
© Copyright IBM Corp. 1988, 2001 xxi

v IAR002A
v IAR003W
v IAR004I
v IAR005E
v IAR006A
v IAR009I
v IAR010I
v IAR011I
v IAR011W
v IAR012W
v IDC3009I
v IDC3351I
v IEA253I
v IEA435I
v IEA437I
v IEA811E
v IEA812E
v IEA848I
v IEA920I
v IEA995I
Messages No Longer Issued
Starting with this release, the following messages are no longer issued:
v IEA941D
v IEA942I
Also, the following section has changes:

v “Using LookAt to look up message explanations” on page vi
text and illustrations are indicated by a vertical line to the left of the change.
Summary of Changes
for GC28-1786-13
This book contains information previously presented in GC28-1786-12, which supports OS/390 Version 2
Release 9.
Please note that any new, changed, or deleted messages can affect your installation’s automation
package. Ensure that your installation’s automation package is updated with these changes.
Rearranged Information
Message explanations have been rearranged to ensure that they follow “How Messages are Explained in
this Book” on page 5.
New Information
The following section is new:

v “Using LookAt to look up message explanations” on page vi
The following are the new messages for this major revision:
v GFSA336E
v GFSA337I
xxii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

v GFSA344I
v GFSA345I
v GFSA346I
v GFSA770I
v GFSA777I
v GFSA784I
v GFSA950I
v GFSA951I
v GFSA952I
v GFSA953I
v GFSA954I
v GFSA955I
v GFSA956I
v GFSA957I
v GFSA958I
v GFSA959I
v GFSA960I
v GFSA961I
v GFSA964I
v GFSA965I
v GFSA966I
v GFSA975A
v GFSC100E
v GFSC101E
v GFSC102E
v GFSC103E
v GFSC105E
v GFSC106E
v GFSC107E
v GFSC110E
v GFSC200E
v GFSC201E
v GFSC202E
v GFSC203E
v GFSC204E
v GFSC205E
v GFSC206E
v GFSC207E
v GFSC208E
v GFSC209E
v GFSC307E
v GFSC318E
v GFSC721E
v GFSC722E
v GFSC723E
v GFSC724E
v GFSC725E
v GFSC840E
v GFSC841E
v GFSC842E
v GFSC843E
v GFSC845I
v GFSC846E
v GFSC847E
v GFSC848E
v GFSC849E
Summary of Changes xxiii

v GFSC850E
v GFSC854I
v GFSC855E
v GFSC856E
v GFSC858E
v GPM069I
v IDC2055I
v IDC3897I
v IEA015A
v IEA016W
v IEA020W
v IEA051I
v IEA052I
v IEA086I
Changed Information

v GPM051I
v GPM054I
v GPM062I
v GPM063I
v GPM064I
v IAR011W
v IDC3009I
v IDC21364I
v IEA253I
v IEA303W
v IEA437I
v IEA480E
v IEA541E
v IEA811E
v IEA812E
v IEA813E
v IEA836I
v IEA837I
v IEA842E
v IEA916E
v IEA918I
v IEA920I
v IEA922D
v IEA923D
v IEA995I
v IEA964I
v IEA797W
Moved Information
EWX and EZM messages have been moved from OS/390 MVS System Messages, Vol 2 (ASB-ERB) to
“Chapter 2. LANRES Messages (EWX, ACP, ASD)” on page 13 and “Chapter 3. EZM Application Enabling
Technology Messages” on page 149.
xxiv OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Summary of Changes
for GC28-1786-12
as updated June, 2000
online only for SK2T-6700-17
The following changes appear only in the online version of this publication. A vertical bar ( | ) in the left
margin indicates changes to the text and illustrations.
Moved Information
In the BookManager form of this book, EWX and EZM messages have been moved from OS/390 MVS
System Messages, Vol 2 (ASB-ERB) to “Chapter 2. LANRES Messages (EWX, ACP, ASD)” on page 13
and “Chapter 3. EZM Application Enabling Technology Messages” on page 149.
This revision reflects the deletion, addition, or changing of information from service items and
maintenance.
Summary of Changes
for GC28-1786-11
Release 8.
New Information
v IEA411I
Changed Information

v IDC0550I
v IDC3009I
v IDC31892I
v IEA195I
v IEA282I
v IEA311I
v IEA437I
v IEA480E
v IEA486E
v IEA989I
Summary of Changes
for GC28-1786-10
Summary of Changes xxv

maintenance.
Summary of Changes
for GC28-1786-09
Release 7.
The following summarizes the changes to that information.
This revision reflects the deletion, addition, or changing of information to support the following APARs:
v OW38678
v OW38984
New Information:
v IEB1160I
Changed Information:
The following are the changed messages for this major revision:
v IDC31562I
v IDC3009I
v IEA145E
v IEA435I
v IEB19CI
v IEB1157E
Summary of Changes
for GC28-1786-08
maintenance.
Summary of Changes
for GC28-1786-07
xxvi OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Release 6.
This book includes terminology, maintenance, and editorial changes.
v OW28604
v OW33588
v OW33967
v OW35980
New Information:
v GFSA322I
v IEA102W
v IEA441I
The following are the changed messages for this major revision:
v IDC3009I
v IDC11374I
v IEA120A
v IEA192I
v IEA194I
v IEA195I
v IEA196I
v IEA253I
v IEA332A
v IEA334A
v IEA339A
v IEA345A
v IEA367A
v IEA405E
v IEA412I
v IEA435I
v IEA442E
v IEA448I
v IEA449A
v IEA451I
v IEA452I
v IEA453I
v IEA454E
v IEA455E
v IEA457I
v IEA458I
v IEA459I
v IEA468I
v IEA469E
v IEA473I
Summary of Changes xxvii

v IEA474E
v IEA475E
v IEA476E
v IEA477I
v IEA478E
v IEA479I changed to IEA479E
v IEA480E
v IEA481I
v IEA482I
v IEA484I
v IEA491E
v IEA510A
v IEA710A
v IEA763I
v IEA765I
v IEA766I
v IEA794I
v IEA888A
v IEB175I
Summary of Changes
for GC28-1786-06
The following changes appear only in the online version of this publication.
v OW28604
Summary of Changes
for GC28-1786-05
Release 5.
v OW15984
v OW29919
New Information:
v GFSA323
v GFSA324
v GFSA436
v GFSA437
v GFSA438
xxviii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

v GFSA439
v GFSA440
v GFSA566
v GFSA786
v GFSA801
v GFSA802
v GFSA822
v GFSA823
v GFSA909
v GFSC210
v GFSC211
v GPM050I
v GPM051I
v GPM052I
v GPM054I
v GPM055I
v GPM056I
v GPM057I
v GPM058I
v GPM059I
v GPM060I
v GPM061I
v GPM062I
v GPM063I
v GPM064I
v GPM065I
v GPM066I
v GPM067I
v IEA494I
v IEA495I
The following are the changed messages for this major revision, including a portion of the message text
and an explanation of the change made to the message.
GFSA320
Explanation and system programmer response have changed.
GFSA321
Operator response has changed.
GFSA559
System programmer response has changed.
GFSA771
Message has changed.
GFSA772
GFSA776
Message and explanation have changed.
GFSA782
Explanation has changed.
GFSA847
Summary of Changes xxix

GFSA877
GFSA970
GFSA973
GFSA974
GFSA976
GFSA977
GFSA978
Message, explanation, and user response have changed.
GFSA979
GFSC300
GFSC301
GFSC302
GFSC303
GFSC304
GFSC305
GFSC306
GFSC309
GFSC315
GFSC317
GFSC319
GFSC320
GFSC502
GFSC503
xxx OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

GFSC505
GFSC506
GFSC703
GFSC707
GFSC708
GFSC709
GFSC711
GFSC712
IEA126I
IEA196I
IEA301I
Explanation and operator response have changed.
IEA326I
Explanation, system action, and system programmer response have changed.
IEA404A
IEA405E
IEA437I
Messages No Longer Issued:
v GPM0001I
v GPM0002I
v GPM0003I
v GPM0004I
v GPM0005I
v GPM0006I
As part of the name change of OpenEdition to OS/390 UNIX System Services, occurrences of OS/390
OpenEdition have been changed to OS/390 UNIX System Services or its abbreviated name OS/390 UNIX.
OpenEdition may continue to appear in messages, panel text, and other code with OS/390 UNIX System
Services.
Summary of Changes
for GC28-1786-04
Summary of Changes xxxi

Release 4.
v OW30281
Changed Information: Changes have been made to the following topics:
Where to Find More Information

Subsystem, Product, and Hardware Books
Message Directory
The following are changed messages for this major revision, including an explanation of the change made
to the message:
IDC3009I
IDC3351I
IEA196I
IEA272I
IEA301I
Explanation, system action, and operator response have changed.
IEA321I
System action has changed.
IEA323I
IEA324I
IEA340I
Explanation and system action have changed.
IEA371I
IEA611I
IEA848I
IEA886A
IEA888A
xxxii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

IEA911E
IEB1029I
Summary of Changes
for GC28-1786-03
This revision also reflects the deletion, addition, or modification of information to support miscellaneous
maintenance items and the following APARs:
v OW13523
v OW25593
v OW26164
v OW27196
v OW27748
v OW28396
v OW28538
Summary of Changes
for GC28-1786-03
Release 3.
v OW20124
v OW22516
v OW23383
New Information: The following are the new message identifiers for this major revision:
v GPM001I
v GPM002I
v GPM003I
v GPM004E
v GPM005E
v GPM006E
v IEA767A
v IEA820I
v IEA822
v IEB1137W
Changed Information: The following are the changed messages for this major revision, including a
portion the message text and an explanation of the change made to the message:
Summary of Changes xxxiii

1.3.0 IDC3009I VSAM CATALOG RETURN CODE IS rtn - REASON CODE IS IGGOCLaa - rsn
Changed message.
The message text and system programmer response have changed.
1.3.0 IDC3020I INSUFFICIENT SPACE ON USER VOLUME
2.4.0 IDC3020I UNABLE TO ALLOCATE SPACE ON USER VOLUME
Changed message.
The message text has changed.
1.3.0 IEA100I ETR SERVICE INFORMATION IS PROVIDED. REASON CODE=rcc
2.4.0 IEA100I ETR SERVICE INFORMATION IS PROVIDED. REASON CODE=rcc
Changed message.
1.3.0 IEA272I ETR SERVICE IS REQUESTED. REASON CODE=rcc
Changed message.
1.3.0 IEA517W IODF IS NOT VALID FOR AN IPL
2.4.0 IEA517W IODF IS NOT VALID FOR AN IPL
Changed message.
The system action has changed.
1.3.0 IEA872I INVALID IPS IN IEAIPSxx
2.4.0 IEA872I INVALID IPS IN IEAIPSxx
Changed message.
The system action, operator response and system programmer response have changed.
1.3.0 IEA900I INVALID ICS IN IEAICSxx
2.4.0 IEA900I INVALID ICS IN IEAICSxx
Changed message.
The system action, operator response and system programmer response have changed.
Summary of Changes
for GC28-1786-03
New Information
This revision also reflects the deletion, addition, or modification of information to support miscellaneous
maintenance items.
Summary of Changes
for GC28-1786-02
xxxiv OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Release 2.
v OW17551
v OW18377
v OW21586
New Information
v GDE007E
v GOS000I
v GOS006I
v GOS007I
v GOS008I
v GOS009I
v GOS010I
v GOS011I
v GOS012I
v GOS013I
v GOS019I
v GOS021I
v GOS022I
v GOS023I
v GOS024I
v GOS025I
v GOS026I
v GOS027I
v GOS031I
v GOS032I
v GOS033I
v GOS041I
v GOS042I
v IDC0018I
v IDC3531I
v IEA100I
v IEA486E
v IEB1063W
v IEB367I
Changed Information
The following are the changed messages for this major revision, including a portion the message text and
an explanation of the change made to the message:
1.2.0 IDC21364I ERROR DETECTED BY DIAGNOSE: {VVDS|ICFCAT} ENTRY: entry RECORD: rec
OFFSET: offset REASON: rsn
Summary of Changes xxxv

1.3.0 IDC21364I ERROR DETECTED BY DIAGNOSE: {VVDS|ICFCAT} ENTRY: entry RECORD: rec
OFFSET: offset REASON: rsn
Changed message.
The explanation has changed.
Changed message.
1.2.0 IEA013E ERROR DETECTED PROCESSING IEASYMxx: text text is one of the following:
1.3.0 IEA013E ERROR DETECTED PROCESSING IEASYMxx: text text is one of the following:
Changed message.
The explanation and system action have changed.
Changed message.
1.2.0 IEA412I SLIP TRAP ID=xxxx, 1 SDUMPS NOT SCHEDULED. RETURN CODE=nn REASON
CODE=mm
1.3.0 IEA412I SLIP TRAP ID=xxxx, 1 SDUMPS NOT SCHEDULED. RETURN CODE=nn REASON
CODE=mm
Changed message.
1.2.0 IEA480E device-number,{SCU|CACHE|DASD|MEDIA}, {ACUTE|SERIOUS|MODERATE|SERVICE}
ALERT,MT=mt, SER=ser,REFCODE=refcode, volser,simid,REPEATED
1.3.0 IEA480E device-number, [type,model,severity] {SCU|CACHE|DASD|MEDIA},
{ACUTE|SERIOUS|MODERATE|SERVICE} ALERT,MT=mt, SER=ser,[MC=mc,ES=es,REF= ref1-ref2-ref3]
REFCODE=refcode, volser,simid,REPEATED
Changed message.
The message text and explanation have changed.
1.2.0 IEA526I SYSNAME SYSTEM PARAMETER INVALID
1.3.0 IEA526I SYSNAME SYSTEM PARAMETER INVALID
Changed message.
The explanation and system programmer response have changed.
1.2.0 IEA527A SPECIFY REQUIRED SYSNAME PARAMETER. SYSNAME=
1.3.0 IEA527A SPECIFY REQUIRED SYSNAME PARAMETER. SYSNAME=
Changed message.
The system programmer response has changed.
1.2.0 IEA650I SYSPLEX DUMP DIRECTORY ENTRY NOT PROCESSED
1.3.0 IEA650I SYSPLEX DUMP DIRECTORY ENTRY NOT PROCESSED
Changed message.
1.2.0 IEA651E SYSPLEX DUMP DIRECTORY PROCESSING TERMINATED
xxxvi OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

1.3.0 IEA651E SYSPLEX DUMP DIRECTORY PROCESSING TERMINATED
Changed message.
1.2.0 IEA705I ERROR DURING {GETMAIN,|FREEMAIN,} SYS CODE= cde-rc {jobname|aaa} stepname
fb W1W2W3W4W5W6
1.3.0 IEA705I ERROR DURING {GETMAIN,|FREEMAIN,} SYS CODE= cde-rc {jobname|aaa} stepname
fb W1W2W3W4W5W6
Changed message.
1.2.0 IEA848I INSTALLATION PREDUMP EXIT, dumpexit, MODIFIED/SUPPRESSED THE DUMP
REQUEST
1.3.0 IEA848I INSTALLATION PREDUMP EXIT, dumpexit, MODIFIED/SUPPRESSED THE DUMP
REQUEST
Changed message.
1.2.0 IEA886A TOD CLOCK(S) MUST BE SET
1.3.0 IEA886A TOD CLOCK(S) MUST BE SET
Changed message.
The operator response has changed.
Summary of Changes
for GC28-1786-01
Release 1.
v OW16294
v OW17076
v OW17355
New Information
v GFSA331E
v GFSA771I
v GFSA772I
v GFSA776I
v GFSA782I
v GFSA783I
v GFSA904I
v GFSA905I
v GFSA908I
Summary of Changes xxxvii

v GFSA991E
v GFSC300E
v GFSC301E
v GFSC302E
v GFSC303E
v GFSC304E
v GFSC305E
v GFSC306E
v GFSC309E
v GFSC310I
v GFSC311I
v GFSC312I
v GFSC313I
v GFSC315E
v GFSC317E
v GFSC319E
v GFSC500I
v GFSC501I
v GFSC502E
v GFSC503E
v GFSC504I
v GFSC505E
v GFSC506E
v GFSC700I
v GFSC701I
v GFSC702I
v GFSC703E
v GFSC704E
v GFSC705E
v GFSC707E
v GFSC708E
v GFSC709E
v GFSC710E
v GFSC711E
v GFSC712E
v GFSC713E
v GFSC714E
v GFSC715E
v GFSC716I
v IDC01880I
v IDC01881I
v IDC01882I
v IDC01883I
v IDC01884I
v IDC01885I
v IDC01886I
v IDC01887I
v IDC01895I
v IDC11468I
v IDC1147I
v IDC11818I
v IDC31880I
v IDC31881I
v IDC31882I
v IDC31883I
v IDC31884I
xxxviii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

v IDC31885I
v IDC31886I
v IDC31887I
v IDC31888I
v IDC31890I
v IDC31891I
v IDC31892I
v IDC31893I
v IDC31894I
v IDC31895I
v IDC31896I
v IDC31897I
v IDC31898I
v IDC31950I
v IDC31951I
v IDC31952I
v IDC31953I
v IDC31954I
v IDC31955I
v IDC31956I
v IDC31957I
v IDC31958I
v IDC31959I
v IEA308I
v IEA309I
v IEA345A
v IEA611I
v IEA651E
v IEA911E
v IEB1138W
v IEB1139W
v IEB1140W
v IEB1141W
v IEB1142W
v IEB1143I
v IEB1144I
v IEB1145I
v IEB1153I
Changed Information
1.1.0 GDE001E DISTRIBUTED FILEMANAGER TARGET SYSTEM INITIALIZATION FAILED. text
1.2.0 GDE001E DISTRIBUTED FILEMANAGER TARGET SYSTEM INITIALIZATION FAILED. text
Changed message.
The system action has changed.
1.1.0 GDE006E INVALID [VALUE FOUND FOR] KEYWORD: kkkkkkkk DISTRIBUTED FILEMANAGER
TARGET SYSTEM NOT STARTED
1.2.0 GDE006E INVALID [VALUE FOUND FOR] KEYWORD: kkkkkkkk DISTRIBUTED FILEMANAGER
TARGET SYSTEM NOT STARTED
Changed message.
The explanation, system action and system programmer response have changed.
Summary of Changes xxxix

1.1.0 GFSA333I DFSMS/MVS 1.2.0 NETWORK FILE SYSTEM SERVER IS NOT STARTED BY A START
COMMAND.
1.2.0 GFSA333I DFSMS/MVS version NETWORK FILE SYSTEM SERVER fmid IS NOT STARTED BY A
START COMMAND.
Changed message.
1.1.0 GFSA348I DFSMS/MVS 1.2.0 NETWORK FILE SYSTEM SERVER STARTED.
1.2.0 GFSA348I DFSMS/MVS version NETWORK FILE SYSTEM SERVER fmid STARTED.
Changed message.
1.1.0 GFSA876I I/O ERROR ON DSN=string1(string2) SENSE. h_digits1 IOBCSW h_digits2 h_digits3.
1.2.0 GFSA876I I/O ERROR ON DSN=string1(string2) SENSE. h_digits1 IOBCSW h_digits2 h_digits3.
ACCESS METHOD RC = h_digits4 ACCESS METHOD RSN = h_digits5
Changed message.
1.1.0 GFSA877I R0 h_digits1 R1 h_digits2 string.
1.2.0 GFSA877I R0 h_digits1 R1 h_digits2 string. ACCESS METHOD RC = h_digits3 ACCESS METHOD
RSN = h_digits4
Changed message.
1.1.0 IDC2893I INVALID PARAMETER SPECIFIED FOR THE RECOVERY OPTION
1.2.0 IDC2893I INVALID PARAMETER SPECIFIED FOR THE RECOVERY OPTION
Changed message.
Changed message.
1.1.0 IDC3351I ** VSAM {OPEN|CLOSE|I/O} RETURN CODE IS rc {RPLFDBWD=nnnnnnnn}
Changed message.
Changed message.
1.1.0 IEA007I STATIC SYSTEM SYMBOL VALUES:
&SYSCLONE.= &sysclone._text
&SYSNAME.= &sysname._text
&SYSPLEX.= &sysplex._text
.
.
.
&symbol._name= symbol_text
xl OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

1.2.0 IEA007I STATIC SYSTEM SYMBOL VALUES:
&SYSCLONE.= &″sysclone._text″
&SYSNAME.= &″sysname._text″
&SYSPLEX.= &″sysplex._text″
.
.
.
&″symbol._name= symbol_text″
Changed message.

1.1.0 IEA008I SYSTEM PARMS FOLLOW FOR RELEASE yy.zz, VERSION ww...w IEASYSxx
.
.
.
IEASYSvv
1.2.0 IEA008I SYSTEM PARMS FOLLOW FOR xx...x
Changed message.
1.1.0 IEA101A SPECIFY SYSTEM PARAMETERS FOR RELEASE xx.yy[VER=ww...w]
1.2.0 IEA101A SPECIFY SYSTEM PARAMETERS FOR xx...x
Changed message.
1.1.0 IEA247I USING IEASYSxx FOR RELEASE zz.yy, VERSION vvvvvvvv
1.2.0 IEA247I USING IEASYSxx FOR xx...x
Changed message.
1.1.0 IEA301I mem {NOT FOUND|IS ALIAS} IN dsn
1.2.0 IEA301I mem {NOT FOUND|IS ALIAS} IN dsn|PARMLIB
Changed message.
1.1.0 IEA328E LNKLSTxx INPUT TRUNCATED AT dsn
1.2.0 IEA328E LNKLSTxx INPUT TRUNCATED AT dsn
Changed message.
The explanation and system programmer response have changed.
1.1.0 IEA334A SYS1.PARMLIB mem HAS AN INVALID RECORD LENGTH - SPECIFY EOB TO
CONTINUE
1.2.0 IEA334A dsn(mem) HAS AN INVALID RECORD LENGTH - SPECIFY EOB TO CONTINUE
Changed message.
v GFSA328I
v GFSA347I
v GFSA349I
Summary of Changes xli

v GFSA360I
v GFSA361I
v GFSA400I
v GFSA403I
v GFSA404I
v GFSA405I
v GFSA406I
v GFSA407I
v GFSA408I
v GFSA409I
v GFSA410I
v GFSA411I
v GFSA412I
v GFSA413I
v GFSA414I
v GFSA415I
v GFSA416I
v GFSA418I
v GFSA419I
v GFSA420I
v GFSA421I
v GFSA422I
v GFSA423I
v GFSA424I
v GFSA425I
v GFSA426I
v GFSA429I
v GFSA430I
v GFSA431I
v GFSA435E
v GFSA450I
v GFSA451I
v GFSA452I
v GFSA501I
v GFSA502I
v GFSA557I
v GFSA561I
v GFSA811I
v GFSA812I
v GFSA813I
v GFSA814I
v GFSA815I
v GFSA816I
v GFSA817I
v GFSA820I
v GFSA827I
v GFSA829I
v GFSA832I
v GFSA833I
v GFSA840I
v GFSA842I
v GFSA843I
v GFSA847I
v GFSA848I
v GFSA849I
v GFSA850I
xlii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

v GFSA851I
v GFSA852I
v GFSA853I
v GFSA854I
v GFSA858I
v GFSA859I
v GFSA860I
v GFSA862I
v GFSA863I
v GFSA871I
v GFSA876I
v GFSA877I
v GFSA877I
v GFSA881I
v GFSA886I
v GFSA895I
v GFSA896I
v GFSA897I
v GFSA898I
v GFSA899I
v GFSA970I
v GFSA971I
v GFSA972I
v GFSA973I
v GFSA974I
v GFSA976I
v GFSA977I
v GFSA978I
v GFSA979I
v GFSA997I
v GFSA998I
Summary of Changes
for GC28-1786-00
This book contains information previously presented in MVS/ESA System Messages, Volume 3 (GDE-IEB),
GC28-1482, which supports MVS/ESA System Product Version 5.
v OW11479
v OW12314
v OW14297
v OW14392
v OW15752
New Information
v IDC1997I
v IDC1998I
v IEA297W
v IEA403I
Summary of Changes xliii

Changed Information
IDC31401I UNABLE TO GET NEXT BASE OBJECT dsname
Changed message.
IEA437I TAPE LIBRARY DEVICE(dev),
Changed message.
IEA611I {COMPLETE|PARTIAL} DUMP ON dsname
Changed message.
IEA774I SUBCHANNEL INITIALIZATION FAILED FOR SUBCHANNEL nnnn,
Changed message.
(5.2.2) IEA848I INSTALLATION PREDUMP EXIT, dumpexit, MODIFIED/SUPPRESSED THE DUMP
REQUEST
(1.1.0) IEA848I INSTALLATION PREDUMP EXIT, dumpexit, MODIFIED/SUPPRESSED THE DUMP
REQUEST
Changed message.
IEA991I SRM CHANNEL DATA NO LONGER AVAILABLE FOR I/O SERVICE
Changed message.
xliv OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Chapter 1. Introduction
The OS/390 operating system issues messages from OS/390 elements and features, and from program
products and application programs running on the system. The system issues messages in different ways
and to different locations:
v Most messages are issued through WTO and WTOR macros to one of the following locations:
– Console
– Hard-copy log
– Job log
– SYSOUT data set
Routing codes determine where the messages are displayed or printed. The routing codes for
messages issued by the operating system are in the OS/390 MVS Routing and Descriptor Codes book.
v Other messages are issued through the WTL macro or the LOG operator command to the system log
(SYSLOG).
v Dump messages are issued through the dumping services routines and can appear in:
– SVC dumps, stand-alone dumps, or SYSMDUMP ABEND dumps formatted by the interactive
problem control system (IPCS)
– Trace data sets formatted by the interactive problem control system (IPCS)
– ABEND dumps or SNAP dumps produced by the dumping services
In dump or trace data sets formatted by IPCS, the messages appear interactively on a terminal or in a
printed dump.
v Some messages are issued through DFSMS/MVS access methods directly to one of the following
locations:
– Output data set
– Display terminal
Locations
Console
Messages sent to a multiple console support (MCS) console or an extended MCS console are intended for
the operators. Operations can control which messages are displayed. See the OS/390 MVS Planning:
Operations book for information about controlling message display.
The system writes in the hard-copy log all messages sent to a console, whether the message is displayed
or not.
Hard-Copy Log
A record of all system message traffic, which consists of the following:
v Messages to and from all consoles
v Commands and replies entered by the operator
In a dump, these messages appear in the master trace. For information about the master trace, see
OS/390 MVS Diagnosis: Tools and Service Aids.
With JES3, the hard-copy log is always written to the system log. With JES2, the hard-copy log is usually
written to the system log, but an installation can specify that the system write the hard-copy log to a
console printer.
© Copyright IBM Corp. 1988, 2001 1

System Log
The system log (SYSLOG) is a SYSOUT data set provided by the job entry subsystem (either JES2 or
JES3). SYSOUT data sets are output spool data sets on direct access storage devices (DASD). An
installation usually prints the system log periodically. The system log consists of:
v All messages issued through WTL macros
v All messages entered by operator LOG commands
v Usually, the hard-copy log
v Any messages routed to the system log from any system component or program
Job Log
Messages sent to the job log are intended for the programmer who submitted a job. The job log is
specified in the system output class on the MSGCLASS parameter of the JCL JOB statement.
SYSOUT Data Set

Messages sent to a SYSOUT data set are intended for a programmer. These messages are issued by an
assembler or compiler, the linkage editor and loader, and an application program. If the SYSOUT data set
and the MSGCLASS parameter on the JCL JOB statement specify the same class, all messages about a
program will appear in the same SYSOUT listing.
Messages
A displayed or printed message can appear by itself or with other information, such as a time stamp. The
following topic shows the format of the message. Then the topics show the information accompanying the
message on the MCS console and on the hard-copy log in a JES2 system and a JES3 system.
Message Format
id CCCnnn text
id CCCnnns text
id CCCnnnns text
id CCCnnnnns text
id CCCSnnns text
id Reply identifier: It is optional. It appears if an operator reply is required. The operator specifies it in the
reply.
CCCnnn, CCCnnns, CCCnnnns, CCCnnnnns, CCCSnnns
Message identifier.
CCC
A prefix to identify the component, subsystem, or product that produced the message. The prefix is
three characters.
S The subcomponent identifier, which is an optional addition to the prefix to identify the
subcomponent that produced the message. The subcomponent identifier is one character.
nnn, nnnn, nnnnn
A serial number to identify the individual message. The serial number is three, four, or five decimal
digits.
s An optional type code, which is one of the following:
A Action: The operator must perform a specific action.
D Decision: The operator must choose an alternative.
E Eventual action: The operator must perform action when time is available.
2 OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

I Information: No operator action is required. Most information messages are for a
programmer.
S Severe error: Severe error messages are for a programmer.
W Wait: Processing stops until the operator performs a required action.
For messages with the prefix ADR, the type codes depend on whether the message is issued to
the operator console or to SYSPRINT. For console messages, the type codes indicate the operator
action:
A Action: Operator must perform a specific action.
D Decision: Operator must choose an alternative action.
I Information: No operator action is required.
W Attention: No operator action is required, but an error occurred.
For SYSPRINT messages, the type code indicates the severity:

I Informational message.
W Attention message. Task continues, but an error occurred.
E Error message. The particular task might end or might continue without completing all
requests.
T Termination message. DFSMSdss ends.
For messages with the prefix BFS, the type codes indicate the severity of the detected error and
are:
E Error. Operator action is required.
I Information
W Attention
For messages with the EWX prefix, an 11-character message exists of the form EWXfffnnnns:
EWX LANRES product code
fff Function (module) identifier
nnnn Message number
s Severity code. Severity codes can be:
E Error. Action is required.
I Information. Action is not required.
S Severe Error. Action is required.
W Attention. Action may be required.
In the EWX messages, the three-character function identifiers are as follows:

Table 1. EWX Message Module Identifiers
Module ID Function Sending Command
ADM Administration EWXADMIN commands
COM Host communications All commands
DSK Disk serving Disk serving commands
DST Distribution EWXDS commands
Chapter 1. Introduction 3
Table 1. EWX Message Module Identifiers (continued)
Module ID Function Sending Command
PHL Host-to-LAN print EWXHLSRV
PLH LAN-to-host print EWXLHSRV
RES Host session initialization EWXCONN
SRV NetWare service EWXNWSRV
Note: When the term “MMC” is used in the messages, it is also referring to the System/370
Parallel Channel Adapter feature of the IBM 3172-3 interconnect controller.
For messages with the prefix CNLC, the type codes indicate the severity of the detected error and
are:
E Error
I Information
S Severe
W Attention
For messages with the prefix IEW and message numbers in the range 2000 through 2999, the
type codes indicate the severity of the detected error and are:
E Error: Severity 8
I Information: Severity 0
S Severe error: Severity 12
T Terminating error: Severity 16
W Attention: Severity 4
For messages with the prefix IGW01, the type codes indicate the severity of the detected error
and are:
E Error: Return code 8
I Information: Return code 0
S Severe: Return code 16
T Ending: Return code 12
W Attention: Return code 4
text
Text: The text provides information, describes an error, or requests an operator action.
Messages with the prefix IDA are preceded by a 2-digit severity code:
04 Attention: Processing may be successful.
08 Error: Processing may fail.
12 Serious error: Processing will probably fail.
Some messages have asterisks (*) before or after the message identifier. Two asterisks after the message
identifier for IDC messages indicates a second-level message that further explains a preceding message.

How Messages are Explained in this Book
The following describes the different parts of message explanations in this book:
Explanation
The meaning of the message, including why the system issued the message.
System Action
v What the system did as a result of the system condition reported by the message. A system
condition could include running out of storage, a hardware or software failure, an abend, a wait
state.
v What the system did as a result of user input. User input can include a system command, a job
running on the system, a transaction, a query, or another user-system interaction.
Operator Response
Instructions for the system operator, including, as appropriate, decisions to make and actions to
take.
Only provided for messages that could appear at the system console.
User Response
Instructions for the end user.
Only provided for messages that could appear at an interactive interface such as a TSO/E terminal
or ISPF application.
Note: Most user messages are explained in other message books, such as OS/390 TSO/E
Messages.
Application Programmer Response
Instructions for an application programmer.
Only provided for messages that could appear in SYSOUT produced by a job, for example
SPZAP.
System Programmer Response
Instructions for the system programmer.
Only provided for messages that require additional action beyond the operator response, user
response, or application programmer response.
Storage Administrator Response
Instructions for the DFSMSdfp storage administrator.
Security Administrator Response
Instructions for the security administrator.
Only provided for security-related messages.
Problem Determination
Additional instructions for determining the cause of the problem, searching problem databases,
and, if necessary, reporting the problem to the IBM support center. These instructions are for a
customer support person who can troubleshoot problems, such as the system programmer or
system administrator, an experienced security administrator, or an experienced storage
administrator.
For additional information on performing problem determination procedures, see OS/390 MVS
Diagnosis: Procedures and the appropriate diagnosis guide for the product or element issuing the
message, such as:
v DFSMS/MVS diagnosis guides and references
v OS/390 JES2 Diagnosis
v OS/390 JES3 Diagnosis
v RMF Diagnosis Guide
Source
Element, product, or component that issued the message.
Detecting Module
Name of the module or modules that detected the condition that caused the message to be
issued.
Messages Sent to MCS Consoles

Messages sent to MCS consoles from the base control program, JES2, JES3 on local processors, or DFP
appear in one of the following formats:
v The MFORM parameter in the OPERPARM segment in the CONSOLxx parmlib member
v The MFORM parameter on the CONTROL S operator command.
hh.mm.ss sysname jobname message

hh.mm.ss sysname message
hh.mm.ss jobname message
hh.mm.ss message
sysname jobname message
sysname message
jobname message
message
Messages sent to JES3 consoles (attached to JES3 global processors only) appear in the format:
hhmmsst i f jobname text
hh.mm.ss
hhmmsst
Time stamp: the hour (00-23), minute (00-59), second (00-59), and, for JES3, tenth of a second (0-9).
sysname
System name for the system that issued the message.
jobname
Job name for the task that issued the message. This field is blank if a job did not issue the message.
i Indicator from the JES3 spool access method (JSAM).
f A screen character to indicate the status of certain messages, as follows:
| The operator has performed the action required for the message. The message has been
deleted.
- The message is for information only; no operator action is required. The message was issued
by the system or by a problem program.
* The message requires specific operator action and was issued by a WTOR or by an
authorized program. The message has a descriptor code of 1, 2, or 11.
@ The message requires specific operator action and was issued by a WTOR or by a problem
program. The message has a descriptor code of 1, 2, or 11.
+ The message requires no specific operator action and was issued by a problem program using
a WTO macro.
blank The message requires no specific operator action.
Note: See the OS/390 MVS Routing and Descriptor Codes book for the descriptor codes.

message
Reply identifier, message identifier, and text.
Messages Sent to Hard-Copy Log in JES2 System

Multiple console support (MCS) handles message processing in:
v A JES2 system
v A JES3 system on a local processor
v A JES3 system on a global processor, if JES3 has failed
MCS sends messages with routing codes 1, 2, 3, 4, 7, 8, and 10 to the hard-copy log when display
consoles are used or more than one console is active. All other messages can be routed to the hard-copy
log by a system option or a VARY HARDCPY operator command.
Messages sent to the hard-copy log appear in the format:
tcrrrrrrr sysname yyddd hh:mm:ss.th ident msgflags message

t message
t lid message
t The first character on the line indicates the record type:

D Data line of a multiple-line message; this line may be the last line of the message.
E End line or data-end line of a multiple-line message.
L Label line of a multiple-line message.
M First line of a multiple-line message.
N Single-line message that does not require a reply.
O Operator LOG command.
S Continuation of a single-line message or the first line of a multi-line message. This
continuation may be required because of the record length for the output device.
W A multi-line message that requires a reply and sent only to the hard-copy log.
X A log entry that did not originate with a LOG command or a system message.
Note: This field does not appear when the hard-copy log is printed on a console in a JES2 system.
c The second character on the line indicates whether the line was generated because of a command:
C Command input.
R Command response.
I Command issued internally. The job identifier contains the name of the internal issuer.
blank Neither command input nor command response.
Note: This field does not appear when the hard-copy log is printed on a console in a JES2 system.
rrrrrrr
Hexadecimal representation of the routing codes 1 through 28. To understand this hexadecimal
number, convert it to binary; each binary 1 represents a routing code. For example, X'420C' represents
routing codes 2, 7, 13, and 14 as shown here:
Hexadecimal: 4 2 0 C
Binary: 0 1 0 0 0 0 1 0 0 0 0 0 1 1 0 0
Routing Codes: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
sysname
The system name from the SYSNAME parameter in the IEASYSxx parmlib member.
yyddd
The Julian date, given as the year (00-99) and the day of the year (000-366).
Note: If HCFORMAT(CENTURY) is specified in the CONSOLxx parmlib member, the Julian date
appears as yyyyddd.
hh:mm:ss.th
Time stamp, given as the hour (00-23), minute (00-59), second (00-59), and hundredths of a second
(00-99).
ident
The job identifier for the task that issued the message, if the second character on the line is blank.
If the second character on the line is C or R, this field contains one of the following:
jobid The job identifier of the task that issued the message, if it was issued by a job.
consname Console name of the console which issued the command or received the message.
INTERNAL For a command generated by a problem program or the system.
INSTREAM For a command read from the input stream.
blank If MCS could not determine the source or destination for the message.
lid Multiple-line identifier for the second and succeeding lines of a multiple-line message. This field
appears after the message text (1) on the first line or (2) in the message area and not followed by text
on a continuation of the first line. The identifier appears on all lines of the same message.
msgflags
Installation exit and message suppression flags. For mapping of these flags, see WQEXMOD in
OS/390 MVS Data Areas, Vol 5 (SSAG-XTLST). For information about the description of the hardcopy
log message flags, see HCL in OS/390 MVS Data Areas, Vol 2 (DCCB-ITZYRETC).
message
Reply identifier, message identifier, and text. The reply identifier and message identifier appear only on
the first line of a multiple-line message.
Messages Sent to Hard-Copy Log in JES3 System

Messages sent to the JESMSG hard-copy log in a JES3 system appear in the format:
hh:mm:sst message
Messages sent to the MLOG/DLOG hard-copy log in a JES3 system appear as follows:

MLG 90131 1734486 SY1 R= SYSLOG IEF196I IEF237I JES3 ALLOCATED TO SYSLOG02
MLG 90131 1734492 SY1 R= SYSLOG IEF196I IEF285I +MASTER+.SYSLOG.JOB00001.D000000A.? SYSOUT
JES CN3E1 90131 1734492 SY1 R= SYSLOG IEE043I A SYSTEM LOG DATA SET HAS BEEN QUEUED TO SYSOUT CLASS A
MLG 90131 1734492 SY1 R= 0000000 SY1 90131 17 34 49.36 SYSLOG 00000000 IEE042I SYSTEM LOG
MLG 90131 1734492 SY1 R= DATA SET INITIALIZED
LOG 90131 1734501 IAT7001 JOB SYSLOG (JOB00001) IS ON WRITER PRT002(002),RECORDS=1343
LOG 90131 1734517 IAT7007 JOB SYSLOG (JOB00001) ON WRITER PRT002 (002), DSN=
LOG 90131 1734517 IAT7007 +MASTER+.SYSLOG.JOB00001.D000000A.?, PURGED.
CN3E1 90131 1735017 +E
MASTER 90131 1735238 +I O
MASTER 90131 1735239 IAT8541 NAME ADDR LV ALT MAIN SWITCH DEPTH DEPQD
MASTER 90131 1735239 IAT8542 CN3E1 (3E1) 15 CN310 SY1 050 00000
MASTER 90131 1735239 IAT8542 MASTER (3E0) 15 -------- -------- TYPE=MCS --- -----
MASTER 90131 1735239 IAT8542 MCS15 (320) 15 -------- -------- TYPE=MCS --- -----
MASTER 90131 1735239 IAT8542 MCS05 (3DC) 05 -------- -------- TYPE=MCS --- -----
MASTER 90131 1735239 IAT8542 MCS00 (3DD) 00 -------- -------- TYPE=MCS --- -----
MASTER 90131 1735240 IAT8542 AUTOMCS ( ) 15 -------- -------- TYPE=MCS --- -----
MASTER 90131 1735240 IAT8542 CN310 (310) 15 CN3E1 SY1 CN3E1 050 00000
MASTER 90131 1735240 IAT8542 CN311 (311) 15 CN3E1 SY1 CN3E1 050 00000
MASTER 90131 1735240 IAT8542 DUMMY ( ) 15 NONE NONE 032 00000
MASTER 90131 1735506 +T SY2 D R,L
MLG 90131 1735506 SY2 R= JES3 D R,L
MASTER 90131 1735522 SY2 R= IEE112I 17.35.50 PENDING REQUESTS 427
MASTER 90131 1735522 SY2 R= RM=0 IM=0 CEM=1 EM=0 RU=0 IR=0 AMRF
MASTER 90131 1735522 SY2 R= ID R/K T SYSNAME JOB ID MESSAGE TEXT
MASTER 90131 1735522 SY2 R= 2 C SY1 *IAT6360 CHECKPOINT DATA SET <CHKPNT2>
MASTER 90131 1735522 SY2 R= UNAVAILABLE - CHKPNT2 DD NOT DEFINED.
CN3E1 90131 1735590 +T SY1 D R,L
CN3E1 90131 1735590 -D R,L
CN3E1 90131 1736007 SY1 R= IEE112I 17.35.59 PENDING REQUESTS 603
CN3E1 90131 1736007 SY1 R= RM=0 IM=0 CEM=2 EM=0 RU=0 IR=0 AMRF
CN3E1 90131 1736007 SY1 R= ID R/K T SYSNAME JOB ID MESSAGE TEXT
CN3E1 90131 1736007 SY1 R= 11 C SY1 JES3 *IAT5525 272 DUPLICATE VOLUME DETECTED, CAN
CN3E1 90131 1736007 SY1 R= NOT MOVE VOLUME SPOOL1 ON SY2
CN(15) 90131 1736049 +Z LOG NEXT COMMAND IS FROM A MCS-ONLY CONSOLE
LOG 90131 1736050 IAT7150 CN(15) NEXT COMMAND IS FROM A MCS-ONLY CONSOLE
CN(15) 90131 1736126 -D T
CN(15) 90131 1736126 SY1 R= IEE136I LOCAL TIME=17.36.12 DATE=90.131 GMT TIME=21.36.12 DATE=90.131
CN(101) 90131 1736353 +Z LOG NEXT COMMAND IS FROM AN EXTENDED MCS-ONLY CONSOLE
LOG 90131 1736354 IAT7150 CN(101) NEXT COMMAND IS FROM AN EXTENDED MCS-ONLY CONSOLE
CN(101) 90131 1736374 +I Q
CN(101) 90131 1736374 IAT8674 JOB SYSLOG (JOB00001) P=15 CL=A MAIN(EXECUTING-SY1)
CN(101) 90131 1736374 IAT8674 JOB VTAM220 (JOB00004) P=15 CL=A MAIN(EXECUTING-SY1)
CN(101) 90131 1736374 IAT8674 JOB TCAS (JOB00005) P=15 CL=A MAIN(EXECUTING-SY1)
CN(101) 90131 1736374 IAT8674 JOB SYSLOG (JOB00007) P=15 CL=A MAIN(EXECUTING-SY2)
CN(101) 90131 1736374 IAT8674 JOB SUPERU (JOB00009) P=15 CL=A MAIN(EXECUTING-SY1)
Messages sent to the MLOG/DLOG hard-copy log appear in the format:
dest console yyddd hhmmsstia[prefix] message
dest
JES3 destination class, which corresponds to the MVS routing code.
console
JES3 console name or MVS console identifier, as follows:
blank For a message issued without a console identifier.
nnnnnnnn The JES3 console name (JNAME) from the JES3 initialization stream.
CN(xx) or CN(xxx)
The MCS console identifier, where xx or xxx is the unit control module (UCM)
identifier.
INTERNAL For a command generated by a problem program or operating system routine.
INSTREAM For a command read from the input stream.
NETWORK For a message issued to the network job entry (NJE) console.
RMT-NS For a message with a JES3 remote console identifier that is incorrect.
UNKNOWN For a message issued with extended MCS console identifier 255.
NOTFOUND For a message issued with a console identifier for which JES3 could not determine the
destination.
yyddd
The Julian date, given as the year (00-99) and the day of the year (000-366).
Note: If HCFORMAT(CENTURY) is specified in the CONSOLxx parmlib member, the Julian date
appears as yyyyddd.
hhmmsst
Time stamp, given as the hour (00-23), minute (00-59), second (00-59), and tenth of a second (0-9).
i Attention indicator for JES3 space constraints, as follows:
blank Normal output or no action required.
# The message is rerouted automatically or by a command from another console.
% Minimum space (track) situation (JSAM).
= Marginal space (track) situation (JSAM).
< Minimum buffer situation (JSAM).
Note: The above four symbols can be changed by a CONSTD statement in the JES3 initialization
stream.
a Action prefix character, as follows:
blank Normal message.
+ JES3 input command, issued on the global processor.
- MVS input command, issued on the global processor.
Operator action required.
prefix
sysname R=jobname
Optional prefix for messages issued outside the JES3 address space or on a local processor, as
follows:
sysname
The name of the system where the issuing program is running. JES3 determines the name from
the ID, RID, or SID parameters on the MAINPROC statement in the JES3 initialization stream.
jobname
The job name of the issuing program. It is all blanks for an system routine.
message
Reply identifier, message identifier, and text.
Messages Sent to the Job Log, to Other Data Sets, and to Display
Terminals
Messages sent to the job log, to other data sets, and to display terminals appear in the format designed by
the program that issued them.

Truncated Data in Multi-line Messages
When a message is being transported from one system to another in a sysplex, the system might
encounter an unexpected error which prevents the entire message text from appearing. This can be
caused by any of the following:
v The issuing system is stopped or quiesced.
v The issuing system fails to end a multi-line message.
v The issuing system has a persistent XCF buffer shortage.
v A disruption occurs in sysplex communication.
For any multi-line message, one of the following messages can appear within the message text, indicating
such an error:
LOSS OF DATA - MESSAGE COMPLETION FORCED
LOSS OF INTERMEDIATE MESSAGE DATA
If a program issues a multi-line WTO message but does not end the message by issuing an endline, the
target console might stop receiving message traffic. The system will detect this condition and end the
message automatically.
To end a multi-line WTO message when it detects that no data line or endline has been issued for the
message after an interval of 30 seconds, the system issues the following endline:
MESSAGE TIMED OUT - MESSAGE COMPLETION FORCED
When this text appears in a multi-line message, perform the action which produced the message again, if
necessary. If the text appears again, contact your system programmer, who should then contact the IBM
Support Center.
When 100% WTO buffer utilization has been reached, as indicated in message IEA404A, a limit is
imposed on the number of lines allowed in multi-line WTO messages. When the line limit is reached for
multi-line WTO messages, the following is appended onto the multi-line message:
v MESSAGE TRUNCATED DURING WQE BUFFER SHORTAGE
A Method for Finding Changes to MVS and TSO/E Message Texts

Automation routines are sensitive to changes to message text between releases. You can find changes to
message texts in the following ways:
v The Summary of Changes of the related messages book can be helpful when you go from one release
to the next.
v Data set SYS1.MSGENU contains data that can help you identify changes to message texts more
accurately. This method allows you to find message text changes between your current release and
whatever release you choose to migrate to. This method is described below.
Using SYS1.MSGENU to Find Message Text Changes

IBM supplies a data set containing the text of system messages that are translated. This data set, called
SYS1.MSGENU, contains the text of system messages in the form of message skeletons. (For more
information, see OS/390 MVS Planning: Operations.)
Note that this method will not show changes to:

v MVS system messages that are not translated, such as IPL and NIP messages (which are issued
before the MVS message service is available)
v Other product messages that are not translated, such as DFSMS/MVS messages, and JES3 messages.
v For JES2 messages, use the appropriate SYS1.VnRnMn.SHASMENU data set.
Also, this method works better if the “old” copy of SYS1.VnRnMn.SHASMENU has the same level of
service as the system from which you are migrating.
Once you have installed the OS/390 Release 4 or higher level of the data set you are comparing, you can
compare the new data set with the data set on the system from which you are migrating. Depending on
how you do the comparison, you can get output like the following.
For new messages, the output might show an I (for Insert) on the left:
I - IEA403I VALUE OF RMAX HAS BEEN CHANGED TO 99
For messages whose text has changed, the output might show both an I and a D, indicating that a record
in the message file has been replaced:
I - IEE162I 46 &NNN. ROLL &A. MESSAGES (DEL=R OR RD)
D - IEE162I 46 &NNN. ROLL &A. MESSAGES (DEL=R, RD)
This means that, in message IEE162I, (DEL=R, RD) was replaced by (DEL=R OR RD).
Using this information, you can decide if your automation routines need to be changed.

Chapter 2. LANRES Messages (EWX, ACP, ASD)
Each message produced by LANRES is preceded by an 10-character prefix of the form EWXxxnnnns:
EWX The LANRES product code
xx Task identifier
nnnn Message number
s Severity code
E Error. Operator action is required. LAN Server continues to function.
I Information. Operator action is not required.
W Warning. Operator action may be required.
LANRES on a Front-end Processor uses OS/2 facilities for displaying messages. With these facilities,
prefixes are displayed in the form BFSnnnn:
EWX The LANRES product code
nnnn Message number
EWX Host Messages
EWXxx0000I **DEBUG** p1 p2 p3 p4 p5 p6 p7 p8 p9 EWXxx0004E Function function was unsuccessful.

Reason: reason.
Explanation: This is a generic diagnostic message
used during LANRES software development and debug. Explanation: The application attempted to perform
function, function. The attempt was unsuccessful with
System Action: Command processing continues.
reason, reason.
User Response: No additional information is given,
System Action: Command processing ends. The
except for information in the message itself.
system status remains the same.
System Programmer Response: None.
User Response: If possible, correct the reason for the
Source: LANRES error. Otherwise, contact your system programmer.
System Programmer Response: If the error cannot
EWXxx0001E A member name is not allowed when be corrected, contact your IBM service representative.
the data set name has special
Source: LANRES
character(s).
Explanation: The user attempted to EWXDS GET or
EWXxx0005E Conflicting option(s) option(s)
EWXDS PUT a member of a partitioned data set where
specified.
the data set name contained special characters (*).
Explanation: Options entered on the command line
were in conflict with other options.
User Response: To EWXDS GET or EWXDS PUT a
single member of a partitioned data set, you must state
the entire data set name with no special character(s) in User Response: Correct the conflict and reenter the
the name. To EWXDS GET or EWXDS PUT all the command.
members of a partitioned data set, you need to write a
routine that will repeatedly call EWXDS GET or EWXDS
PUT specifying a different member with each call. Source: LANRES
EWXxx0006E Duplicate option(s) option specified.
Source: LANRES
Explanation: Duplicate options were entered on the
command line.

EWXxx0011S Level mismatch between Host and
Server programs.
User Response: Correct the duplication and reenter
Explanation: The host is connecting to a NetWare
the command.
server running an unsupported version of the LANRES
System Programmer Response: None. NLMs.
Source: LANRES System Action: Command processing ends. The

EWXxx0008E Incorrect option(s) option(s) specified. User Response: Notify your system programmer.
Explanation: The indicated option(s) are not correct. System Programmer Response: Verify that the
The error may be a misspelling, missing information, NetWare server is running LANRES NLMs at version
incorrect information, incomplete information, or 3.0 or greater.
improper abbreviation.
Source: LANRES
EWXxx0012S Incorrect function connected or
User Response: Correct the error and reenter the being connected.
command. If the error message did not supply an
Explanation: The job is attempting to connect to an
option(s) value, see OS/390 LANRES Configuration
incorrect function or already has connected to an
Files and Commands for the correct syntax.
incorrect function.
Source: LANRES system status remains the same.
User Response: Use the EWXCONN LINK command
EWXxx0009E Incorrect parameter(s) parameter(s) to connect the correct function.
specified.
Explanation: The indicated parameter(s) are not
Source: LANRES
correct. The error may be a misspelling, missing
information, incorrect information, incomplete
information, or improper abbreviation. EWXxx0013S Request cannot be processed by the
server.
system status remains the same. Explanation: A LANRES command has been entered,
but the NLM on the server does not recognize the
User Response: Correct the error and reenter the
command.
command. If the error message did not supply a
parameter(s) value, see OS/390 LANRES Configuration System Action: Command processing ends. The
Files and Commands for the correct syntax. system status remains the same.
System Programmer Response: None. User Response: First, verify that the command is
correct. If it is and the problem persists, notify your
Source: LANRES
system programmer.
System Programmer Response: Check to see if
EWXxx0010E Too many parameters entered.
LANRES is installed correctly. Reinstall LANRES if
Explanation: Extraneous parameters were entered on necessary.
the command line.
Source: LANRES
EWXxx0014S Server program version is not
User Response: Correct the error and reenter the compatible with NetWare version.
command.
Explanation: Your request was directed to a LANRES
System Programmer Response: None. NLM that requires a different version of NetWare than
the one that is installed.
Source: LANRES
User Response: Notify your system programmer.
System Programmer Response: Verify whether

LANRES is installed correctly. Reinstall LANRES if System Action: Command processing ends. The
necessary. system status remains the same.
Source: LANRES User Response: Correct the problem indicated by
error_text. Reenter the command.
EWXxx0015E Command not valid before System Programmer Response: None.
EWXCONN LINK login.
Source: LANRES
Explanation: You cannot enter any administration or
distribution commands until you are logged into the
EWXxx0019E Insufficient parameters specified.
NetWare server.
Explanation: Additional parameters are required for
this command.
User Response: Establish a connection to the
NetWare server with the EWXCONN LINK command. If
you do not have a user ID on the server, notify your User Response: Correct the error and reenter the
system programmer. command.
System Programmer Response: Provide the user System Programmer Response: None.
with a user ID and, optionally, a password on the server.
Source: LANRES
Source: LANRES
EWXxx0020W Cannot close the host file filename.

EWXxx0016E The user ID password entered is Error returned was: error_text
longer than 127 characters.
Explanation: An error occurred while trying to close
Explanation: The user ID password specified was the host file, filename. The explanation for the error,
longer than 127 characters. error_text, was returned in the message. The command
will continue processing even though the indicated file is
not closed.
System Action: Command processing continues but
User Response: If the spelling of the specified user ID
the file is not closed.
password is incorrect, correct it. If the specified
password is to be assigned to a user ID, choose a User Response: Correct the problem indicated by
password with less than 127 characters. Reenter the error_text to close the file.
command.
Source: LANRES
Source: LANRES
EWXxx0021E Permission denied by NetWare

EWXxx0017E Cannot open the host file filename. server.
Error returned was: error_text
Explanation: The user has insufficient authority to
Explanation: An error occurred while trying to open perform the operation. Depending on the task being
the file, filename, on the host. The explanation for the performed, the proper trustee rights, security
error, error_text, was returned in the message. equivalences, or work group manager rights may be
required. This message may also indicate that you are
performing an operation on a read-only file or a
directory.
User Response: Correct the problem indicated by
User Response: Obtain the appropriate authority to
Source: LANRES perform the action. Or, if the file is read-only and a
change does need to be done, the owner of the file, or
the supervisor, needs to change the read attribute of the
EWXxx0018E Cannot read the host file filename.
file, then perform the operation again. It is also possible
Error returned was: error_text
that the operation that you are performing may be on a
Explanation: An error occurred while trying to read directory and not a file. Determine if the filename is a
the file, filename, on the host. The explanation for the directory. You can do this by using the distribution
error, error_text, was returned in the message. command to list the files and specify the same filename
Chapter 2. LANRES Messages (EWX, ACP, ASD) 15

that you entered when you received this message. User Response: Enter the EWXCONN LINK
command to establish a new connection to the NetWare
System Programmer Response: If appropriate, grant
server. Reenter the command that caused the error. If
the proper authority to the user.
the problem persists, notify your system programmer.
Source: LANRES
System Programmer Response: Unload the
LANRES NLMs from the NetWare server and load them
EWXxx0029E Connected to the function1 function, again. If the problem persists, check the NetWare
not the function2 function. server for error messages and contact your IBM service
representative.
Explanation: You are connected to the function1
function on the NetWare server, but tried to enter a Source: LANRES
command to the function2 function. The command
cannot complete.
EWXxx0033E Cannot find host file filename.
Explanation: The host file indicated in the message
cannot be found in the search path.
User Response: If the problem is in the administration
or distribution function, enter the EWXCONN LINK
command to establish a connection to the correct
function on the NetWare server. Reenter the command User Response: Make sure the file name was spelled
that caused the error. correctly, If the file name is correct, make sure the file is
in your search path. Correct the problem and reenter
If the problem is in the disk, host-to-LAN print, or
the command.
LAN-to-host print function, reenter the command that
caused the error. System Programmer Response: None.
If the problem persists, notify your system programmer. Source: LANRES
System Programmer Response: Unload the
LANRES NLMs from the NetWare server and load them EWXxx0034E Error sending data to the NetWare
again. If the problem persists, contact your IBM service server. Error returned was: error_text
representative.
Explanation: A communications error occurred while
Source: LANRES sending data to the NetWare server. The type of error is
indicated by error_text.
EWXxx0031E Cannot write to host file filename. System Action: Command processing ends. The
Error was: error_text LANRES function on the NetWare server tries to
recover from this error.
Explanation: An error occurred while trying to write to
the file, filename, on the host. The explanation for the User Response: Reenter the command that caused
error, error_text, was returned in the message. the error. It may be necessary to enter the EWXCONN
LINK command to reset the connection with the
NetWare server. If the problem persists, notify your
system programmer.
System Programmer Response: Verify that the
communications method is operating correctly. Other
System Programmer Response: None. error messages may be displayed to help you determine
the problem. If the problem persists, contact your IBM
Source: LANRES service representative.
Source: LANRES
EWXxx0032S Authentication error. Connection to
the NetWare server will be dropped.
EWXxx0036E Data was not successfully received
Explanation: Packets sent between the host and the from the NetWare server.
NetWare server contain signatures to verify that the
packet originated from the correct function. If this Explanation: A communications error occurred while
signature does not match what is expected, then a receiving data from the NetWare server.
communications error has occurred and the connection
to the NetWare server will be dropped.
LANRES function on the NetWare server tries to
System Action: Command processing ends. The recover from this error.
connection to the NetWare server is dropped.
User Response: Reenter the command that caused

the error. It may be necessary to enter the EWXCONN Source: LANRES
NetWare server. If the problem persists, notify your
EWXxx0042E Incorrect user name user specified.
system programmer.
Explanation: A user name must be between 1 and 47
characters long, and cannot contain spaces or any of
the following special characters:
error messages may be issued to help you determine
the problem. / (slash)
Source: LANRES \ (backslash)
: (colon)
; (semicolon)
EWXxx0037E Error receiving data from the
NetWare server. Error returned was: , (comma)
error_text * (asterisk)
? (question mark)
receiving data from the NetWare server. The type of
error is indicated by error_text. NetWare may also restrict the user name from
System Action: Command processing ends. The containing other special characters.
LANRES function on the NetWare server tries to System Action: Command processing ends. The
recover from this error. system status remains the same.
User Response: Reenter the command that caused User Response: Correct the spelling of the specified
the error. It may be necessary to enter the EWXCONN user name. Reenter the command.
NetWare server. If the problem persists, notify your System Programmer Response: None.
system programmer.
Source: LANRES
EWXxx0043E Value missing for option option.
error messages may be displayed to help you determine
the problem. If the problem persists, contact your IBM Explanation: The specified option requires that an
service representative. additional value be assigned to it.
EWXxx0041E Incorrect server name server User Response: Correct the error and reenter the
specified. command.
Explanation: A server name must be between 2 and System Programmer Response: None.
47 characters long, and cannot contain spaces or any
Source: LANRES
of the following special characters:
/ (slash) EWXxx0046E Host and Server security passwords

\ (backslash) do not match for the function function.
: (colon)
Explanation: You tried to connect to a LANRES
; (semicolon)
function on the NetWare server but the passwords you
, (comma)
used did not match those expected by the server
* (asterisk) function. Please note that different servers may have
? (question mark) different security passwords.
NetWare may also restrict the server name from connection to the NetWare server is dropped.
containing other special characters. User Response: Retry the server connection request
System Action: Command processing ends. The specifying the correct security passwords for the server
system status remains the same. function.
User Response: Correct the spelling of the specified System Programmer Response: None.
server name. Reenter the command. Source: LANRES

Source: LANRES
EWXxx0050E Double-byte characters cannot be
specified on the command line.
EWXxx0067E Incorrect print server name server
Explanation: Double-type characters were specified
specified.
on the command line but these characters cannot be
processed by the command. Explanation: A print server name must be between 1
and 47 characters long, and cannot contain spaces or
any of the following special characters:
User Response: Correct the error and reenter the / (slash)
command. \ (backslash)
: (colon)
; (semicolon)
Source: LANRES , (comma)
* (asterisk)
EWXxx0063I A value for parameter was previously ? (question mark)
specified; the new value value will be
used.
NetWare may also restrict the print server name from
Explanation: A value was already specified for the containing other special characters.
parameter listed; because the parameter was specified
again, the last value associated with the same System Action: Command processing ends. The
parameter will be used. system status remains the same.
System Action: Processing continues. User Response: Correct the spelling of the specified
print server name. Reenter the command.
User Response: If the value needed was the first
value, retype the command using the parameter only System Programmer Response: None.
once with the correct data. Source: LANRES
Source: LANRES EWXxx0068E Incorrect print queue name queue
specified.
EWXxx0065E Incorrect nickname nickname Explanation: A print queue name must be between 1
specified. and 47 characters long, and cannot contain spaces or
any of the following special characters:
Explanation: A nickname must be between 1 and 47
characters long. A nickname also cannot be the / (slash)
keywords ADMIN, DISK, DIST, HLPRT, or LHPRT. \ (backslash)
System Action: Command processing ends. The : (colon)
system status remains the same. ; (semicolon)
, (comma)
User Response: Enter the command with a shorter or
* (asterisk)
different nickname.
? (question mark)
Source: LANRES
NetWare may also restrict the print queue name from
containing other special characters.
EWXxx0066E Incorrect component password data
set dsname specified.
Explanation: A component password data set was
User Response: Correct the spelling of the specified
specified in the command but the data set name is
print queue name. Reenter the command.
incorrect.
system status remains the same. Source: LANRES
User Response: Correct the data set name and
reenter the command.

server has been lost. The server may no longer be
EWXxx0069E Incorrect group name group
running or the system administrator may have logged
specified.
you off the server.
Explanation: A group name must be between 1 and
47 characters long, and cannot contain spaces or any
connection to the NetWare server is dropped.
of the following special characters:
User Response: Try to reestablish your connection to
/ (slash) the NetWare server. If that fails, make sure the server is
\ (backslash) still running or ask your system administrator to verify
: (colon) that you still have access to the server.
; (semicolon)
System Programmer Response: Verify that the user
, (comma)
still has a valid user ID on the NetWare server.
* (asterisk)
? (question mark) Source: LANRES
EWXxx1001E No procedures file found.

NetWare may also restrict the group name from
containing other special characters. Explanation: The program could not find the
procedures file on the system.
system status remains the same. System Action: LAN-to-host print service machine
stops.
group name. Reenter the command. User Response: Notify your system programmer.
System Programmer Response: None. System Programmer Response: Ensure that the
procedures file has been created and that the
Source: LANRES necessary service machines have access to it. See
OS/390 LANRES Configuration Files and Commands
EWXxx0070E Incorrect volume name volume for more information. Then re-start the service machine.
specified. Source: LANRES
Explanation: A volume name must be between 2 and
15 characters long, and cannot contain spaces or any EWXxx1002I LAN-to-host print function initialization
of the following special characters: completed.
/ (slash) Explanation: Both the LAN-to-host NLM and service
\ (backslash) machine have initialized and are ready to start
: (colon) processing print requests.
; (semicolon) System Action: None.
, (comma)
* (asterisk) User Response: None.
? (question mark) System Programmer Response: None.
Source: LANRES
NetWare may also restrict the volume name from
containing other special characters. EWXxx1003E No valid procedure names found in
procedures file(s).
system status remains the same. Explanation: The LAN-to-host service machine
program reads the procedures file(s) and extracts the
names it finds to be used as user exits. No user exit
volume name. Reenter the command.
programs were found to be valid in the procedures
System Programmer Response: None. file(s).
Source: LANRES System Action: The LAN-to-host print service
machine stops.
EWXxx0071E Your login to the NetWare server has User Response: Notify your system programmer.
been lost.
Explanation: You cannot issue any more names in the procedures file(s) are correct. Verify that
administration or distribution commands to your target the exits exist on the system and are accessible by the
NetWare server because your login to that NetWare LAN-to-host print service machine. Restart the

LAN-to-host print service machine after the corrections
EWXxx1007I Shutting down the LAN-to-host print
have been made.
service machine at the user’s request.
Source: LANRES
Explanation: The service machine is being shutdown
as a result of a interrupt from the keyboard.
EWXxx1004I The NLM requested the service
System Action: A shutdown can only occur when
machine be restarted.
there is no job currently printing; therefore the shutdown
Explanation: A condition that caused the LAN-to-host will be normal.
print NLM to be restarted occurred forcing the host
User Response: None.
service machine to restart.
System Action: The LAN-to-host print service
machine is being restarted; the environment remains the Source: LANRES
same and no information is lost.
User Response: None. EWXxx1008I LAN-to-host print servicing has ended.
System Programmer Response: Usually no Explanation: The service machine has stopped
additional action is necessary, but the cause of the processing.
restart is not known to the host service machine, for any
System Action: Processing ended. The return code
additional information refer to the NetWare system
will be the most severe value encountered, among the
console.
warning messages.
Source: LANRES
System Programmer Response: Refer to the
EWXxx1005I The maximum number of queues has
previous messages to determine the cause of the
been reached.
service machine stopping.
Explanation: The number of queues to be serviced
Source: LANRES
exceeds the allowable number. All other queues will be
ignored.
EWXxx1009E An unknown packet was received.
System Action: The LAN-to-host print service
machine operates on the queues defined. Explanation: The service machine has received a
unknown packet type. The host and NetWare server are
out of sync.
System Programmer Response: Reduce the number
System Action: The LAN-to-host print machine will
of queues this job processes; start another job to handle
restart.
any number of queues above 80.
Source: LANRES
EWXxx1006E Error on the NetWare server. Check Source: LANRES
the NetWare server console for
messages.
EWXxx1010E The print server, server, does not
Explanation: An error condition in the LAN-to-host exist on the NetWare server.
print NLM occurred that the host did not recognize. A
message stating the error will be displayed by the NLM Explanation: The print server entered from the
and can be found on the NetWare server console. LAN-to-host print service invocation or the default of
HOSTPRT does not exist on the NetWare server being
System Action: The LAN-to-host print service connected to.
machine stops; the LAN-to-Host print NLM may or may
not stop, depending upon the severity. System Action: The LAN-to-host print service
machine stops.
User Response: Verify that the correct print server
System Programmer Response: Check the NetWare was specified. If correct, contact the NetWare system
server console and perform the instructions that the programmer to have the print queue added to the file
message states. Restart the service machine after the server.
necessary steps have been taken.
System Programmer Response: If a new print server
Source: LANRES is needed, add it to the NetWare server attached to the
LAN-to-host print service machine. A new print server
can be added by using the NetWare PCONSOLE utility

or the EWXADMIN functions in LANRES.
EWXxx1014I Could not translate print queue name,
Source: LANRES queue.
Explanation: The queue specified associated with the
EWXxx1011E No print queues in the Lan-to-Host NPRINT command could not be translated correctly.
configuration file for, Server. Therefore the LAN-to-host print service machine cannot
determine which user exit to call.
Explanation: There are no print queues associated
with the specified print server. Therefore, no jobs would System Action: The print job is not printed; the
ever be printed. LAN-to-host print function continues to run.
System Action: The LAN-to-host print service User Response: None.

machine stops.
System Programmer Response: If the translation
User Response: Verify that the correct print server routine is incorrect there will be other similar messages.
was specified when starting the LAN-to-host print Otherwise the name of the print queue may not be
service machine. If so, contact your NetWare system correct in EBCDIC.
programmer to have the desired queues associated with
Source: LANRES
the requested print server.
System Programmer Response: If the requested
EWXxx1015I Execution of user exit associated with
print queue does not exist, it must first be created. After
queue, queue stopped.
the print queue exists, it must be associated with the
specified print server, by using the NetWare Explanation: The user exit associated with the queue
PCONSOLE utility or the EWXADMIN functions in specified stopped, because it cannot be found, not
LANRES. executing correctly, or any other possibility.
Source: LANRES System Action: The LAN-to-host print service
machine is not stopped. The queue is removed from the
list of available queues for LANRES. The queue will no
EWXxx1012I The user exit, exit has unknown type.
longer be valid until the service machine is stopped and
Explanation: The user exit listed in the procedures file the problem corrected.
cannot be processed.
System Action: The queue associated with the
System Programmer Response: Determine why the
particular exit will not be added to the list of queues for
user exit cannot be executed.
host processing.
Source: LANRES
System Programmer Response: Check the
EWXxx1016I Job status message could not be
processing type of the user exit and make the
translated.
necessary changes. Valid type are EXEC, OLDEXEC,
TSO, PGM and INTERNAL. Explanation: The message returned from the user exit
stating the status of the print job could not be translated
Source: LANRES
from EBCDIC to ASCII correctly.
System Action: The print job status is unknown; the
EWXxx1013I The user exit, exit listed in the
LAN-to-host print function continues to run.
procedures file cannot be found.
Explanation: The user exit listed in the procedures file
cannot be found in the search order. System Programmer Response: If the translation
routine is in error there will be other similar messages.
System Action: The queue associated with the
Otherwise the message may not be correct in terms of
particular exit will not be added to the list of queues for
translating to ASCII.
host processing.
Source: LANRES
System Programmer Response: Check the accesses
EWXxx1017I The user exit for queue queue is not
granted to the service machine and make the necessary
using the stack correctly.
changes.
Explanation: The expected amount of data is not on
Source: LANRES
the stack.
System Action: The service machine continues to

run. The status message may not be presented to the System Programmer Response: None.
client.
Source: LANRES
System Programmer Response: Change the user EWXxx1022E Did not specify a NetWare print
exit to ensure the proper data is used and returned to server after keyword QS.
the LAN-to-host print service machine.
Explanation: The keyword QS exists in the command
Source: LANRES but the NetWare print server name did not follow.
System Action: Command processing ends.
EWXxx1018E Error allocating storage.
User Response: Reenter the command with a print
Explanation: An error was returned when allocating server name or do not use the QS keyword. If you do
storage. not use the QS keyword, the default print server name
will be used.
System Action: The service machine continues.
Source: LANRES
System Programmer Response: Stop the service
machine, free storage, then restart the service machine.
EWXxx1023I All the fields in the print job
Source: LANRES
configuration structure may not be
translated correctly.
EWXxx1019E The user exit definition for queue,
Explanation: The routine translating the text fields in
queue, is incorrect.
the print job configuration structure indicated that the
Explanation: The syntax of the queue line in the translations may not be complete. Some of the fields
procedures file is incorrect. may not have translated successfully.
System Action: The service machine is not stopped, System Action: The LAN-to-host print service
though the queue will not be placed on the available machine is not stopped. This data is not used by the
queue list. service machine. It is passed directly to the user exits.
Though it is probable the user exit will not succeed.
System Programmer Response: Correct the line in
procedures file associated with the queue. System Programmer Response: Determine why the
translation routine is not translating correctly; keeping in
Source: LANRES mind it may be the type of data being sent from the
NLM.
EWXxx1020E Translation of the NetWare print Source: LANRES
server name is not possible.
Explanation: The NetWare print server name could EWXxx1024I The message was longer than 57
not be translated from EBCDIC to ASCII. bytes.
System Action: The LAN-to-host print service Explanation: The length of the message exceeded 57
machine is stopped. bytes which is the maximum length of a message sent
User Response: None. to a client.
System Programmer Response: Determine why the System Action: The service machine continues to
server name is not being translated and make the run.
necessary changes. User Response: None.
Source: LANRES System Programmer Response: Change the user
exit such that the message length does not exceed the
EWXxx1021I Using the default NetWare print server maximum.
name, server. Source: LANRES
Explanation: No NetWare print server was specified
on the command line. The default is being used.
System Action: None.

Source: LANRES
EWXxx1025I The queuename is being truncated to
its maximum length of length.
EWXxx1029E Did not specify a debug value after
Explanation: The length of the queue name has been
keyword DEBUG.
exceeded. The queue name will be truncated to fit into
the desired length. Explanation: The keyword DEBUG exists in the
command but the value did not follow.
run. System Action: Command processing ends.
User Response: None. User Response: Re-enter the command with a value
for debug, or do not use the DEBUG keyword thus
System Programmer Response: The queue name
defaulting debug to off.
can be changed to a valid queue name to avoid
truncation. Truncation may result in unexpected results. System Programmer Response: None.
Source: LANRES Source: LANRES
EWXxx1026I The file name is being truncated to its EWXxx1030E Cannot create the print job file, file.
maximum length of length. Error was: error_text
Explanation: The length of the file name has been Explanation: The file, file, cannot be created. This file
exceeded. The file name will be truncated to fit into the contains the print job the user exits will process. The
desired length. explanation for the error, error_text, was returned in the
message.
run. System Action: The service machine stops.
User Response: None. User Response: None.
System Programmer Response: The file name can System Programmer Response: Determine why the
be changed to a valid file name to avoid truncation. file cannot be opened.
Truncation may result in unexpected results.
Source: LANRES
Source: LANRES
EWXxx1031E Cannot write to print job file filename.

EWXxx1027I The execution type is being truncated Error was: error_text
to its maximum length of length.
Explanation: An error occurred while trying to write to
Explanation: The length of the execution type has the file, filename, on the host. The explanation for the
been exceeded. The execution type will be truncated to error, error_text, was returned in the message.
fit into the desired length.
System Action: The service machine continues to system status remains the same.
run.
System Programmer Response: Correct the problem
System Programmer Response: The execution type indicated by error_text.
may be changed to a valid type to avoid truncation.
Truncation may result in unexpected results. Source: LANRES
Source: LANRES
EWXxx1032E Unable to run user exit: error_text
EWXxx1028E Could not open procedure file procs. Explanation: An error occurred while trying to run a
Error was: error_text user exit. The explanation for the error, error_text, was
returned in the message.
Explanation: The program found the procedures file
but cannot open the file to read. System Action: Command processing ends. The
System Action: LAN-to-host print service machine
stops. User Response: None.
User Response: Notify your system programmer. System Programmer Response: Correct the problem
indicated by error_text.
System Programmer Response: Ensure that the
procedures file is not accessed by another process. Source: LANRES

System Action: The service machine stops.
EWXxx1033E Incorrect user exit name user_exit.
Explanation: A qualified name is not allowed for this
exit type. Please specify a simple name for the exit in System Programmer Response: Determine why the
the EWXLHPRT.PROCS file. file cannot be deleted. An exit may not have freed the
file.
System Action: The system status remains the same.
Source: LANRES
System Programmer Response: Correct the entry in
EWXxx1038E The print server, server, is in use.
the procedures file.
Explanation: The print server entered from the
Source: LANRES
LAN-to-host print service invocation or the default of
HOSTPRT is already being serviced by LANRES.
EWXxx1034E LANRES connection already
established for another function.
Explanation: A connection to the NetWare server
already exists for another LANRES function. LANRES System Programmer Response: Determine where
supports only one connection at a time to the NetWare the print server should be started from or create another
server. print server. If you need to create another print server, a
new print server can be added by using the NetWare
PCONSOLE utility or the EWXADMIN functions in
User Response: Drop the existing LANRES LANRES.
connection and restart the LAN-to-Host print server.
Source: LANRES
Source: LANRES EWXxx1100E Cannot open output device. Error
returned was: error_text
EWXxx1035E All user exits have been disabled. Explanation: An error occurred while opening the
output device.
Explanation: All the user exits defined have been
disabled due to errors. System Action: The print exit is stopped.
System Action: Command processing ends. User Response: None.
User Response: None. System Programmer Response: Use the error text to
determine why the output device cannot be opened,
System Programmer Response: Review the error
then correct the problem.
messages in the log, correct the problems, and restart
the LAN-to-host print server. Source: LANRES
Source: LANRES
EWXxx1101E File file queued for printing.
EWXxx1036E Unknown internal exit, exit_name. Explanation: The named file has been processed
successfully by LANRES and has been given to the
Explanation: The exit name specified is not defined.
host operating system to print.
System Programmer Response: Correct the entry in
the LAN-to-host print procedures file.
Source: LANRES
Source: LANRES
EWXxx1102E Printing of file failed.

EWXxx1037E Cannot delete the print job file, file.
Error was: error_text Explanation: LANRES processing for the named file
has failed. Examine other messages in the log to
Explanation: The file, file, cannot be deleted. This file
determine the cause of the failure.
contains the print job the user exits will process. The
explanation for the error, error_text, was returned in the System Action: The system status remains the same.
message.
User Response: Correct any errors and resubmit print

job. If problem persists, contact system programmer.
EWXxx1107E Error writing JCL. Error was
System Programmer Response: Determine cause of error_text.
error and take corrective action.
Explanation: An error occurred while writing JCL
Source: LANRES needed to print data. Use the error text to determine the
cause of the failure.
EWXxx1103E Options not found for exit exitname. System Action: The system status remains the same.
Explanation: Print exit exitname expects options to be User Response: Correct any errors and resubmit print
passed in. job. If problem persists, contact system programmer.
System Action: The system status remains the same. System Programmer Response: Determine cause of
Source: LANRES
System Programmer Response: Change the
EWXLHPRT.PROCS file to include the necessary
options. EWXxx1108E Unable to open JCL member member.
Error was error_text.
Source: LANRES
Explanation: An error occurred while trying to read
the member member. The member will be found in the
EWXxx1104E Incorrect translation type type dataset pointed to by DD EWXLHJCL or
specified. prefix.EWXLHPRT.JCL if the DD does not exist.
Explanation: The translation type specified is Member EWXLHJOB is the JOB statement that will be
incorrect. Valid types are: LINE, SEND, and NONE. used for all JCL members that do not start with their
own JOB statements. Use the error text to determine
System Action: The system status remains the same. the cause of the failure.
User Response: None. System Action: The system status remains the same.
System Programmer Response: Correct the User Response: Have the system programmer correct
translation type in the EWXLHPRT.PROCS file. the error then resubmit the print job.
Source: LANRES System Programmer Response: Determine cause of
EWXxx1105E Error writing print data. Error was Source: LANRES
error_text.
Explanation: An error occurred while writing the EWXxx1109E Unable to open job. Error was
processed print data. Use the error text to determine the error_text.
cause of the failure.
Explanation: An error occurred while trying to open
System Action: The system status remains the same. the job. Use the error text to determine the cause of the
User Response: Correct any errors and resubmit print failure.
job. If problem persists, contact system programmer. System Action: The system status remains the same.
System Programmer Response: Determine cause of User Response: Have the system programmer correct
error and take corrective action. the error then resubmit the print job.
Source: LANRES System Programmer Response: Determine cause of
EWXxx1106E Incorrect device type device_type. Source: LANRES
Explanation: The device type specified in the
LAN-to-host print procedures file is incorrect. The device EWXxx1151E Incorrect AFP structured field.
type must be 3820 or 38PP.
Explanation: An Incorrect structured field was found in
System Action: The system status remains the same. the input to Enhanced Print stream transformation.
User Response: Have the system programmer correct System Action: The print stream currently being
the entry in the LAN-to-host print procedure file. translated is terminated.
System Programmer Response: Correct the entry in User Response: Re-submit the print job. If it still fails,
the LAN-to-host print procedure file. there is probably a problem with the print stream to be
Source: LANRES translated.

System Programmer Response: None. Source: LANRES
Source: LANRES
EWXxx1156E Unable to open file filename.
EWXxx1152E Begin Document AFP structured field Explanation: While trying to open file filename needed
not found. for transformation, an error occurred.
Explanation: An Begin Document AFP structured field System Action: The print stream currently being
was not found in the first 100 bytes of information to be translated is terminated.
translated.
System Action: The print stream currently being
System Programmer Response: Verify that the file
translated is terminated.
exists and re-submit the print job.
User Response: Re-submit the print job. If it still fails,
Source: LANRES
there is probably a problem with the print stream to be
translated.
EWXxx1157W Unable to use scalable font file
filename.
Source: LANRES
Explanation: While trying to read file filename a
problem was encountered.
EWXxx1153E Incorrect AFP structured field length.
System Action: Transformation continues, but the
Explanation: An AFP structured field was found with output will not use this font.
an incorrect length.
filename is in PCL Scalable font.
Source: LANRES
translated.
EWXxx1158I The maximum number of Soft fonts
soft_font_max has been reached.
Source: LANRES
Explanation: While trying to add a soft font, it was the
maximum number of soft fonts was reached. The
EWXxx1154E Incorrect AFP SF identifier detected. maximum number of soft fonts is 200.
Explanation: An incorrect AFP structured field System Action: Transformation continues.
identifier was found.
System Programmer Response: Update the queue
profile to contain fewer soft fonts.
Source: LANRES
translated.
EWXxx1159W Font font_name font bitmap file_name
does not exist.
Source: LANRES
Explanation: The font file file_name cannot be found.
EWXxx1155E Dataset dataset_name is not a PDS
output will not use this font.
dataset.
Explanation: While trying to locate a file need for
transformation, a dataset was encountered that was not System Programmer Response: Make sure file
properly allocated. file_name exists.
System Action: The print stream currently being Source: LANRES
User Response: Re-allocate the dataset as a PDS
dataset then re-submit the print job.

EWXxx1160W font_type entry font_name dataset EWXxx1164W Incorrect class definition class in
file_name is incorrect. AFPFONT entry afpfont_name in queue
profile file_name is ignored.
Explanation: The font_type entry file file_name cannot
be found. Explanation: An incorrect AFPFONT entry
afpfont_name was detected in queue profile file_name.
output will not be in this font. System Action: Transformation continues but this
AFPFONT entry is ignored.
System Programmer Response: Make sure file
file_name exists. System Programmer Response: Correct the
AFPFONT entry afpfont_name in the queue profile
Source: LANRES
file_name.
Source: LANRES
EWXxx1161E Mode entry not found in queue
profile file_name.
EWXxx1165W Incorrect scale scale_type of
Explanation: No valid mode entries were found in file
scale_value in queue profile file_name.
file_name.
Explanation: A scale_type scale of scale_value is not
System Action: Transformation is terminated.
valid. Valid values are between 50 and 200.
System Action: Transformation continues but scaling
System Programmer Response: Add a mode entry is set to the default of 100. If no other scale entry was
into the queue profile file_name. found in queue profile file_name.
Source: LANRES User Response: None.

System Programmer Response: Correct the Scale
EWXxx1162W Incorrect entry_type entry in queue entry in the queue profile file_name to have both the
profile file_name. horizontal and vertical scales between 50 and 200.
Explanation: An incorrect entry_type was found in file Source: LANRES

file_name.
System Action: Transformation continues but the EWXxx1166W Scalfont entry class in queue profile
option specified by entry_type will not be used. file_name is incorrect.
User Response: None. Explanation: An incorrect class was found on a
Scalfont entry in the queue profile file_name .
System Programmer Response: Correct the
entry_type entry in the queue profile file_name. System Action: Transformation continues but this
scalfont is not used.
Source: LANRES
EWXxx1163W Duplicate entry_type entry in queue System Programmer Response: Check the class and
profile file_name is ignored. attribute specified on the Scalfont entry.
Explanation: A duplicate entry_type was found in file Source: LANRES

file_name.
System Action: Transformation continues. EWXxx1167W No file specified on Scalfont entry
class in queue profile file_name.
Explanation: The file name is missing from scalfont
System Programmer Response: Remove the entry class.
additional entry_type entry in the queue profile
file_name. System Action: Transformation continues but this
scalfont is not used.
Source: LANRES
System Programmer Response: Add the file name
on the specified on the Scalfont entry.
Source: LANRES

System Action: Transformation is terminated.
EWXxx1168W Unable to open file file_name.
Explanation: The file file_name cannot be opened.
System Programmer Response: Verify that all of the
System Action: Transformation continues but this file
LANRES Transformation files are accessible and
is not used.
re-submit the print job. It the problem persists, contact
User Response: None. your IBM service representative.
System Programmer Response: Verify that the file Source: LANRES
file_name exists.
Source: LANRES EWXxx1178E No free storage available.
Explanation: There is no storage available for a free
EWXxx1169W Incorrect font header in file storage request.
file_name.
System Action: The command terminates.
Explanation: The file file_name does not have a valid
font header.
System Programmer Response: Allocate more
System Action: Transformation continues but this font
storage for host-to-LAN print and restart host-to-LAN
file is not used.
Print.
Source: LANRES
file_name is a PCL font bit map.
EWXxx1179E No User parameters specified for
Source: LANRES user exit EWXHLTRN.
Explanation: There is no queue profile specified for
EWXxx1170W Incorrect Setup index setup_index in the EWXHLTRN user exit.
queue profile file_name.
System Action: The command terminates.
Explanation: The Setup string index setup_index is
not between 1 and 4.
System Programmer Response: Place the name of
System Action: Transformation continues but this
the queue profile as a parameter to the EWXHLTRN
Setup string is not used.
user exit.
Source: LANRES
System Programmer Response: Change the Setup
string index to be between 1 and 4.
EWXxx1180E Transformation output buffer full.
Source: LANRES
Explanation: The buffer used to store transformed
data is full.
EWXxx1171W Font entry class is incorrect.
Explanation: The class, pitch or attribute on the font translated is terminated.
entry are incorrect.
System Action: Transformation continues but this font
entry is not used.
Source: LANRES
System Programmer Response: Enter a valid class
EWXxx1341E The Host to LAN print queue context
pitch or attribute.
could not be set.
Source: LANRES
Explanation: The entry specified for the print queue in
the configuration dataset is probably incorrect.
EWXxx1173E Error found in Host-to-LAN print
System Action: The print job is not processed at the
Transformation file.
server.
Explanation: An internal error has been detected with
User Response: Correct the queue name and context
one of the LANRES enhanced print stream
in the Host to LAN configuration dataset.
transformation files.

Source: LANRES
EWXxx1351E Print user exit exitname has incorrect
type type
EWXxx1342E Host to LAN print storage allocation
Explanation: The type specified for the user exit
failure.
exitname in the host-to-LAN print procedures file is not
Explanation: A storage allocation request has failed EXEC or PGM.
on the server.
System Action: The user exit is ignored. The system
System Action: The print job is not processed at the status remains the same.
server.
User Response: Correct the user exit type so that it is
User Response: Verify that sufficient storage is EXEC or PGM.
available on the server or increase storage if necessary.
Source: LANRES
Source: LANRES
EWXxx1352E No valid exit names were found in
EWXxx1343E The server internal address was not the print exits file.
found.
Explanation: The host-to-LAN print server reads the
Explanation: The address of the server on which the print exits file and verifies that the exits are of the
print queue resides cannot be obtained. proper type. No exit names were found with correct exit
types.
System Action: The print job is not processed at the
server. System Action: Command processing ends. The
User Response: Verify that the selected server is
operational and that the proper volume is mounted. User Response: Correct the user exit types so that
they are EXEC or MODULE.
Source: LANRES
Source: LANRES
EWXxx1344E A file server connection could not be

established. EWXxx1353E An error occurred on the NetWare
server.
Explanation: An attempt to connect to the server on
which the print queue resides has failed. Explanation: An error on the NetWare file server that
the host did not recognize. The error will be displayed
System Action: The print job is not processed at the on the NetWare system console.
server.
System Action: The host server stops.
User Response: Verify that the server user licenses
have not been exceeded. User Response: Notify your NetWare system
programmer.
System Programmer Response: Check the NetWare
Source: LANRES console for error messages and refer to the explanation
associated with the NetWare error messages.
EWXxx1345E The server connection cannot be Source: LANRES
authenticated.
Explanation: The LANRES object does not have EWXxx1354E File server fileserver does not exist.
access to resources on the server.
Explanation: A NetWare file server was selected for
System Action: The print job is not processed at the the print request, but the file server could not be found.
server.
System Action: The print job is canceled.
User Response: Unload and reload the LANRES
object with access to server resources. User Response: Correct the file server name in the
host-to-LAN print defaults file and restart the
System Programmer Response: None. host-to-LAN print server.
Source: LANRES System Programmer Response: If a file server that
was started no longer exists, check the file server
console for error messages. Restart the file server when
the error is corrected and verify operation of the system.

Source: LANRES User Response: Reenter the command with a
numeric timeout value in the correct range.
EWXxx1355E An error occurred while sending print System Programmer Response: None.
data to the NetWare server.
Source: LANRES
Explanation: An error occurred during the
transmission of a print job from the host to the NetWare
EWXxx1359I The timeout value specified is timeout.
server. The most probable cause is the loss of a data
packet. Explanation: The timeout value specified on the
command is displayed.
System Action: The job attempts to print again.
System Action: The command continues.
User Response: If necessary, contact your system
programmer. User Response: None.
System Programmer Response: If this error System Programmer Response: None.
continues on a regular basis, verify that the
communications method is properly configured. Source: LANRES
Source: LANRES
EWXxx1360E API error. Check NetWare server
console for messages.
EWXxx1356E Print queue printqueue was not found.
Explanation: An error occurred while trying to process
Explanation: The specified print queue on the an internal NetWare API call.
NetWare server was not found.
System Action: The job will be printed after the error
System Action: The print job is canceled. is corrected.
User Response: Correct the print queue name in the User Response: Notify your NetWare system
host-to-LAN print defaults file and restart the programmer.
host-to-LAN print server. Notify the system programmer
if a new print queue is needed. System Programmer Response: Look on the
NetWare server console for additional messages. Follow
System Programmer Response: If needed, add a the directions for those messages.
new print queue by using either the NetWare
PCONSOLE utility or the LANRES Add NetWare Print Source: LANRES
Server-Queue command.
Source: LANRES EWXxx1361I Print job jobnumber (jobid) is ready for
printing on the server.
EWXxx1357E The timeout value specified, timeout, Explanation: The specified print job is waiting to be
is not numeric. printed.
Explanation: The timeout value used to determine System Action: None.

how often the host-to-LAN print server checks for User Response: None.
completed jobs is not numeric data. The data must be
in terms of the number of seconds to wait between System Programmer Response: None.
checks. Source: LANRES
system status remains the same. EWXxx1362I Print job jobnumber (jobid) has been
User Response: Reenter the command with a printed.
numeric timeout value. Explanation: The specified print job was transferred
System Programmer Response: None. from the NetWare print queue to the printer.
Source: LANRES System Action: The specified operation was

performed.
EWXxx1358E The timeout value specified, timeout, User Response: None.

is not in a range of 1 through 359999. System Programmer Response: None.
Explanation: The timeout value cannot exceed Source: LANRES
359999 seconds. It must be a positive number.

EWXxx1363I No print jobs currently waiting to be
printed. User Response: Correct the problem indicated by
Explanation: There are no print jobs, for the user ID
specified, residing in the NetWare print queues. System Programmer Response: None.
System Action: None. Source: LANRES
EWXxx1377I Printer printer Host ID hostid NetWare
Queue queue NetWare Server server
Source: LANRES ASCII NOTIFY Exit Name exitname
exittype ( exitparms
EWXxx1364I Error specifying option option, value Explanation: The message lists the value of an entry
value used. in the host-to-LAN print printer definition table.
Explanation: The option option in the host-to-LAN System Action: None.
print defaults file was not set to one of the required
values. It is set to value
System Action: Processing continues.
Source: LANRES
User Response: Correct the value specified in the
host-to-LAN printing defaults file.
EWXxx1378I Printer printer has already been started.
Explanation: The printer printer is currently connected
Source: LANRES
to JES or VTAM and does not need to be started.
System Action: The command to start the printer is
EWXxx1365I The host-to-LAN print server is ending.
not processed.
Explanation: A stop command was entered for the
host-to-LAN print server.
System Action: The host-to-LAN print server stops.
Source: LANRES
EWXxx1379I Printer printer_name is not an active
Source: LANRES printer.
Explanation: The command issued for printer
EWXxx1366E Error reading parameter parameter on printer_name failed because the printer was not found
line line of the host-to-LAN print in the list of active printers.
definition data set dsname.
System Action: The operator command is not
Explanation: The host-to-LAN print server detected an processed.
error in parameter parameter on line line of the
User Response: Reenter the operator command with
definition data set allocated dsname.
the correct printer name.
System Action: The line is ignored.
User Response: Correct the error in the definition
Source: LANRES
data set.
EWXxx1380I An unknown command subcommand
Source: LANRES was entered.
Explanation: An operator command other than F or P
EWXxx1374E Cannot create a REXX stack buffer. was entered.
The error returned was: error_text
Explanation: An error occurred while trying to create a processed.
REXX stack buffer on the host. The explanation for the
User Response: Reenter the operator command with
error, error_text, was returned in the message.
the correct command.

Source: LANRES
EWXxx1385E The JES START command must be
used to start a JES printer.
EWXxx1381I An unknown printer subcommand
Explanation: A host START command was issued for
subcommand was entered.
a host-to-LAN JES printer. JES local printers must be
Explanation: A printer subcommand other than, F, A, started using the JES $S command.
D, or Z was entered.
System Action: The operator command is not processed.
processed.
User Response: Retry the operation using the JES $S
User Response: Reenter the operator command with command.
the correct subcommand.
Source: LANRES
Source: LANRES
EWXxx1387E The LANRES host-to-LAN Print
EWXxx1382I An incomplete operator command was server could not connect with JES.
entered.
Explanation: The LANRES host-to-LAN print server
Explanation: The LANRES host-to-LAN print server received a non-zero return code from the FSIREQ
did not find a complete operator command statement. CONNECT service.
System Action: The operator command is not System Action: The LANRES host-to-LAN print server
processed. ends.
User Response: Reenter the operator command with User Response: Contact your system programmer.
the required information.
System Programmer Response: Check the FSSDEF
System Programmer Response: None. statements to make sure that the host-to-LAN printer
server was correctly defined to JES. If no errors are
Source: LANRES found contact your IBM service representative.
Source: LANRES
EWXxx1383I The printer definition on line lineno is
incomplete.
EWXxx1388I All printer routines have not been
Explanation: The LANRES host-to-LAN print server stopped
did not find a complete printer definition statement.
Explanation: JES requested that the Host-to-LAN print
System Action: The printer definition is not server end, but there were still active printers.
processed.
System Action: The host-to-LAN print server ends.
User Response: If one of the parameters in the
printer definition statement was incorrect, correct it. User Response: Issue the JES commands to stop the
Otherwise add the missing parameters to the printer printers, then try to stop LANRES host-to-LAN print.
definition statement.
Source: LANRES
Source: LANRES
EWXxx1389I The host-to-LAN print server has
EWXxx1384I Error in parameter parameter in ended.
command buffer.
Explanation: The LANRES/MVS host-to-LAN print received a shut-down command from JES, or ended
server found an error in parameter parameter in the abnormally.
command buffer.
System Action: The LANRES host-to-LAN print server
System Action: The operator command is not ends.
processed.
User Response: Correct the error and try the
command again.
Source: LANRES
Source: LANRES

messages to determine why the session could not be
EWXxx1390E The host-to-LAN print server could
established.
not start printer printer_name
Source: LANRES
received a start printer command from JES, but could
not start the printer routine. EWXxx1394E The server name server was not
found in the host-to-LAN print servers
file.
User Response: Contact your system programmer.
Explanation: The host-to-LAN print command could
System Programmer Response: Check the message not find the server name server in the host-to-LAN print
log for the host-to-LAN print server for other error servers file.
messages to determine why the ATTACH failed. If
System Action: The host-to-LAN print command
necessary, contact your IBM service representative.
ends.
Source: LANRES
User Response: Add the entry for the server to the
servers file.
EWXxx1391I The host-to-LAN print server could not
find the specified printer printer_name
Source: LANRES
received a start printer command, but no printer
definition with the specified printer ID was found. EWXxx1395E LANRES connection already
established for another function.
Explanation: A connection to the NetWare server
already exists for another LANRES function. LANRES
System Programmer Response: Check the message supports only one connection at a time to the NetWare
log for the host-to-LAN print server for other error server.
messages to determine why the printer was not found. If
no definition exists for the printer,it may be added using
the MODIFY operator command. User Response: Drop the existing LANRES
connection and restart the host-to-LAN print server.
Source: LANRES
EWXxx1392I The host-to-LAN print server received Source: LANRES
error error_text when requesting a
session with PLU luname
EWXxx1396E Error specifying parameter parameter
Explanation: The LANRES host-to-LAN print server’s of the host-to-LAN print servers file.
attempt to connect to the PLU luname ended with error
error_text. Explanation: The value of parameter parameter in the
host-to-LAN print servers file is incorrect.
System Action: The printer is not started.
User Response: Correct the error and retry the print
System Programmer Response: Check the message command.
log for the host-to-LAN print server for other error
messages to determine why the session could not be System Programmer Response: None.
established. Source: LANRES
Source: LANRES
EWXxx1397E Line number number of the
EWXxx1393I The option option is no longer used. It host-to-LAN print servers file is
is ignored. incomplete.
Explanation: The option specified is no longer used in Explanation: Not enough parameters were specified
the current release of LANRES. in the line of the host-to-LAN print servers file.
System Action: The printer is not started. System Action: Command processing ends.
User Response: Contact your system programmer. User Response: Correct the error in the file.
System Programmer Response: Check the message System Programmer Response: None.
log for the host-to-LAN print server for other error

Source: LANRES
not find module EWXHLPJS.
EWXxx1398I The file server fileserver is on the
Explanation: An error occurred when the host-to-LAN
network.
print server attempted to access module EWXHLPJS in
Explanation: The file server specified in this message STEPLIB.
is currently active on the LAN. This message should
System Action: The host-to-LAN printer task ends.
appear only once for each active file server currently on
the LAN when an EWXCONN QUERY PRINT (TYPE User Response: Contact your system programmer.
SLIST function is requested.
System Programmer Response: Check that a
System Action: None. STEPLIB DD exists in the procedure used to run the
host-to-LAN print functional subsystem, and that module
EWXHLPJS is contained in the library.
Source: LANRES
Source: LANRES
EWXxx1403E The host-to-LAN print server could not open STEPLIB.
not create a linkage table entry.
Explanation: An error occurred when the host-to-LAN
Explanation: An error occurred when the host-to-LAN print server attempted to access a module in STEPLIB.
print server attempted to create a linkage table entry.
System Programmer Response: Check that a
System Programmer Response: Contact IBM STEPLIB DD exists in the procedure used to run the
support. host-to-LAN print functional subsystem.
EWXxx1404E The host-to-LAN print server could EWXxx1408E The host-to-LAN print server could
not create an entry table entry. not create the vector table.
Explanation: An error occurred when the host-to-LAN Explanation: An error occurred when the host-to-LAN
print server attempted to add an entry to the entry table. print server attempted to save the address of the vector
table.
System Programmer Response: Contact IBM
support. System Programmer Response: Contact IBM
support.
Source: LANRES
Source: LANRES
EWXxx1405E The host-to-LAN print server is not a

started task. EWXxx1409E The host-to-LAN print server could
not connect to JES.
Explanation: The host-to-LAN print server determined
that it was not started by JES. Explanation: An error occurred when the host-to-LAN
print server attempted to connect to JES.
User Response: Contact you system programmer.
System Programmer Response: Define the
necessary JES statements to start the host-to-LAN print System Programmer Response: Check that the
server as a functional subsystem. definition of the host-to-LAN print functional subsystem
is correct. If it is, contact IBM support.
Source: LANRES
Source: LANRES

EWXxx1410I The host-to-LAN print server received EWXxx1414I The host-to-LAN print server could not
error error_text when opening the ACB start a printer because
for printer printer_name. communications are not active.
Explanation: The host-to-LAN printer server attempted Explanation: The host-to-LAN printer server received
to open an ACB for printer printer_name and received a request to start a printer from JES. However,
an error. communications with the NetWare server are not active.
System Action: The host-to-LAN printer task ends. System Action: The host-to-LAN printer server
continues. No printers will be started.
User Response: Correct the error. If the error cannot
be corrected, notify your system programmer. User Response: Contact your system programmer.
System Programmer Response: Check that the System Programmer Response: Ensure that the
VTAM definition for the printer is correct. communications definition for the host-to-LAN print
server is correct. A communications definition may be
Source: LANRES
changed using the MODIFY operator command.
Communications may be restarted using the MODIFY
EWXxx1411I The DELETE|MODIFY command cannot operator command.
be issued for an active printer.
Source: LANRES
Explanation: The host-to-LAN printer server received
an operator request to delete an entry from the printer
EWXxx1415I The host-to-LAN print server could not
definition table. However, a printer with name
establish communications with the
printer_name is currently active.
NetWare server.
System Action: The host-to-LAN printer definition
table is not updated.
a non-zero return code when it attempted to
User Response: None. communicate with the NetWare file server.
System Programmer Response: None. System Action: The host-to-LAN printer server
Source: LANRES
EWXxx1412I The definition for printer printer_name System Programmer Response: Ensure that the
was not found. communications definition for the host-to-LAN print
server is correct. A communications definition may be
Explanation: The host-to-LAN printer server received changed using the MODIFY operator command.
an operator request to delete an entry from the printer
definition table. However, an entry with name Source: LANRES
printer_name does not exist.
System Action: The host-to-LAN printer definition EWXxx1416E The host-to-LAN print services
table is not updated. module EWXHLPC could not be
initialized.
System Programmer Response: None. a non-zero return code when it attempted to define the
Source: LANRES services module EWXHLPPC to MVS.
System Action: The host-to-LAN printer server ends.
EWXxx1413I The definition for printer printer_name User Response: Contact your system programmer.
already exists.
System Programmer Response: Contact your IBM
Explanation: The host-to-LAN printer server received service representative.
an operator request to add an entry to the printer
definition table. However, an entry with name Source: LANRES
printer_name already exists.
System Action: The host-to-LAN printer definition EWXxx1417E The host-to-LAN print services
table is not updated. module EWXHLPC could not be found.
User Response: None. Explanation: The host-to-LAN printer server received
a non-zero return code when it attempted to LOAD the
System Programmer Response: None. services module EWXHLPPC.
Source: LANRES System Action: The host-to-LAN printer server ends.

System Programmer Response: Ensure that the server could not obtain the command
host-to-LAN print services module EWXHLPPC is in the scheduler communications list.
library concatenation for the job.
Source: LANRES received a non-zero return code from the EXTRACT
service.
EWXxx1418I No host-to-LAN printer definitions were System Action: The LANRES host-to-LAN print server
processed. ends.
Explanation: Either the host-to-LAN printer definition User Response: Contact your system programmer
data set could not be read, or no valid printer definitions
were found in it.
service representative.
System Action: The host-to-LAN printer server
Source: LANRES
System Programmer Response: Ensure that the server could not run non-swappable.
entries in the host-to-LAN printer definition data set are
correct. Printer definitions may be added dynamically
received a non-zero return code from the SYSEVENT
using the MODIFY operator command.
DONTSWAP service.
Source: LANRES
ends.
EWXxx1419E No START parameters were specified
User Response: Contact your system programmer
for the host-to-LAN print server.
System Programmer Response: Ensure that the PPT
Explanation: The length of the command input buffer
entry for the host-to-LAN Print server allows the server
returned by the EXTRACT service was 0.
to become non-swappable, but does not specify that the
System Action: The host-to-LAN printer server ends. server is non-swappable.
User Response: Contact your system programmer. Source: LANRES

FSS-related statements in the JES initialization data set EWXxx1423E The LANRES host-to-LAN Print
are correct. server could not find the FSI ORDER
routine EWXHLORD.
Source: LANRES
received a non-zero return code when it attempted to
EWXxx1420E The LANRES host-to-LAN Print LOAD module EWXHLORD.
server was not started by JES.
Explanation: The LANRES host-to-LAN print server ends.
determined that it was started by an operator command,
rather than by JES. User Response: Contact your system programmer
System Action: The LANRES host-to-LAN print server System Programmer Response: Ensure that
ends. EWXHLORD is in the library concatenation used by the
host-to-LAN print server.
Do not start the host-to-LAN print server by using the Source: LANRES
START command.
System Programmer Response: Add the necessary EWXxx1424E The LANRES host-to-LAN Print
FSSDEF statements to JES to start the host-to-LAN server could not establish a recovery
Print serving FSS. routine.
Source: LANRES Explanation: The LANRES host-to-LAN print server
received a non-zero return code from the ESTAE
service.
ends.

User Response: Contact your system programmer System Programmer Response: If the error persists,
contact IBM service personnel.
service representative. Source: LANRES
Source: LANRES
EWXxx1603S Error reading data from the NetWare
server: error_text.
EWXxx1425E Storage not available for LANRES
Print FSS. Explanation: An attempt to read data from the
LANRES disk program that runs on the NetWare file
server was unsuccessful.
could not obtain storage.
System Action: The connection to the NetWare file
server is closed and the LANRES disk server program
ends.
continues.
User Response: Contact your system programmer
User Response: If this error message is the result of
System Programmer Response: Ensure there is a data link going down, then do nothing because the
enough storage available for LANRES host-to-LAN print LANRES disk server will regularly attempt to
serving to run. re-establish the connection to the NetWare server.
Otherwise, investigate the cause of the error and correct
Source: LANRES it.
EWXxx1600E Disk image name name is more than
8 characters. Source: LANRES
Explanation: The name for a LANRES disk image is

longer than 8 characters. EWXxx1604W Error opening disk image
disk_image_name: error_text.
Explanation: An attempt to open the indicated disk
User Response: Specify a disk image name with no image was unsuccessful.
more than 8 characters.
System Action: The initialization of the LANRES disk
System Programmer Response: None. server continues. The disk image which failed to open
Source: LANRES will not be used.
User Response: If it is desired for this disk image to
EWXxx1601E Error occurred while processing be used by this LANRES disk server program, correct
LANRES command options. the problem and restart the LANRES disk server.
Explanation: An error was detected while processing System Programmer Response: None.
the LANRES command options. A previous message Source: LANRES
describes the error condition.
System Action: Command processing ends. EWXxx1605E No disk images specified or no disk
User Response: Correct the error and retry the images successfully opened.
command. Explanation: Either no disk images were specified
System Programmer Response: None. when the LANRES disk server was started or none of
the disk images specified were successfully opened.
Source: LANRES
System Action: The LANRES command ends and the
disk server is not started.
EWXxx1602W Incorrect request received from the
LANRES disk driver running on the User Response: Verify that at least one disk image
NetWare server. was specified when the LANRES disk server was
started. If at least one was specified, then for each disk
Explanation: The LANRES disk driver program that image specified, error message EWXDSK1604W should
runs on the NetWare file server sent a request that was have been displayed to explain the reason why it could
not recognized by this LANRES disk server program. not be opened. Correct the problem or problems and
System Action: The LANRES disk serving function retry.
continues. System Programmer Response: None.
User Response: None. Source: LANRES

EWXxx1606E Not enough free storage available. EWXxx1610I Disk server shutting down per request.
Explanation: An attempt to obtain free storage was Explanation: This LANRES disk server is ending in
unsuccessful. response to a shutdown request.
System Action: The LANRES command ends and the System Action: The LANRES disk server ends.
User Response: Make more free storage available for
this LANRES disk server and restart it.
Source: LANRES
Source: LANRES
EWXxx1611I Disk server stopped at request of disk
driver program.
EWXxx1607W Disk image file_name has not been
Explanation: The LANRES disk driver program that
initialized.
runs on the NetWare file server has sent a request to
Explanation: The indicated disk image has not been end this LANRES disk server.
initialized.
System Action: The LANRES disk server ends.
System Action: The disk image will not be used by
the LANRES disk server.
User Response: Initialize the disk image using the
EWXLDCRT command and then restart the LANRES Source: LANRES
disk server.
System Programmer Response: None. EWXxx1612S System error code occurred when
attempting to start a timer.
Source: LANRES
Explanation: An attempt to start a timer was
unsuccessful.
EWXxx1608S Error sending data to the NetWare
server: error_text. System Action: The LANRES disk server program
ends.
Explanation: An attempt to send data to the LANRES
disk driver program that runs on the NetWare file server User Response: Correct the error and restart this
was unsuccessful. LANRES disk server.
System Action: The connection to the NetWare file System Programmer Response: None.
server is closed and the disk server program continues.
Source: LANRES
User Response: If this error message is the result of
a data link going down, then do nothing because the
LANRES disk server will regularly attempt to EWXxx1613E LANRES connection already
re-establish the connection to the NetWare server. established for another function.
Otherwise, investigate the cause of the error and correct Explanation: A connection to the NetWare server
it. already exists for a LANRES function other than disk
System Programmer Response: None. serving. LANRES supports only one connection at a
time to the NetWare server.
Source: LANRES
EWXxx1609I Disk driver program closed the User Response: Drop the existing LANRES
connection. connection and restart the LANRES disk server.
Explanation: The LANRES disk program that runs on System Programmer Response: None.
the NetWare file server closed the connection. Source: LANRES
System Action: The LANRES disk server program
continues. EWXxx1614E NetWare server connection
User Response: None. information not available.
System Programmer Response: None. Explanation: The LANRES disk server is unable to
re-establish a connection to the NetWare server
Source: LANRES because no connection options were specified on the
LANRES command line and the initial server connection

was established before the EWXLDDSK command was
EWXxx1618I Disk Server Release release
issued.
Modification modification Service level
System Action: Command processing ends. service_level started.
User Response: Specify the connection options on Explanation: The LANRES disk server has
the LANRES disk server command line and retry the successfully completed its initialization and is about to
LANRES disk server command. attempt communications with the LANRES disk driver
program that runs on the NetWare file server.
System Action: The LANRES disk server continues.
Source: LANRES
EWXxx1615W Server connection signature System Programmer Response: None.

mismatch.
Source: LANRES
Explanation: The signature information in a request
received from the NetWare server is incorrect. This can
EWXxx1619S Error closing disk image
occur if the NetWare server was restarted after a
connection had been established.
Explanation: LANRES was unable to close the
System Action: The current NetWare server
indicate disk image and commit the changes.
connection will be terminated and a new connection will
be established. System Action: The LANRES disk server continues to
end.
User Response: Investigate the error indicated and
System Programmer Response: Report this problem
correct the error condition before restarting the LANRES
to IBM if it continues to occur and the NetWare server is
disk server. The disk image may not contain all of the
not being restarted.
changes made by the NetWare server as a result of the
Source: LANRES close failure.
EWXxx1616W Actual_number bytes were read from
Source: LANRES
the disk driver program when
expected_number bytes were expected.
EWXxx1625E Incorrect value of value specified for
Explanation: More or less data than expected was
RETRY.
read from the LANRES disk driver program that runs on
the NetWare file server. Explanation: The value indicated is not a valid
specification for the RETRY option. Valid values must
System Action: The connection to the NetWare file
be in a range from 10 through 3,600.
server is closed and the disk server program continues.
System Programmer Response: If the error persists,
User Response: Restart the LANRES disk server with
contact IBM service personnel.
a valid value.
Source: LANRES
Source: LANRES
EWXxx1617S Unable to commit disk image
EWXxx1635E Error opening file filename: error_text.
Explanation: An attempt was made to commit the
data written to the disk image but it was unsuccessful. Explanation: An attempt to open the indicated file was
unsuccessful.
System Action: The LANRES disk server ends.
User Response: Restart the LANRES disk server
program and rewrite any data that may have been
written immediately preceding the error. User Response: Investigate the cause of the error,
correct it, and retry the LANRES command.
Source: LANRES
Source: LANRES

EWXxx1637E Error reading file filename: error_text. EWXxx1644E No disk image definitions found in
configuration file filename.
Explanation: An attempt to read the indicated file was
unsuccessful. Explanation: There were no disk image definition
records found in the indicated configuration file.
disk server is not started. System Action: The LANRES command ends and the
User Response: Investigate the cause of the error,
correct it and restart the LANRES disk server. User Response: Add one or more disk image
definition records to the configuration file and restart the
LANRES disk server.
Source: LANRES
Source: LANRES
EWXxx1638E Disk name disk_name in configuration
file filename is too long.
EWXxx1645S Error reading disk image
Explanation: The disk name field within the indicated
configuration file was longer than 8 characters.
Explanation: An attempt to read data from the
indicated disk image was unsuccessful.
System Action: This LANRES disk server informed
User Response: Correct the configuration file and
the LANRES disk driver program of the error and
restart the LANRES disk server.
continued its usual operations.
User Response: Investigate and correct the error.
Source: LANRES Then stop and restart this LANRES disk server.
EWXxx1640E Missing Dataset Name field in
Source: LANRES
Explanation: The Dataset Name field in the indicated
EWXxx1646S Error writing disk image
configuration file is missing for a disk image definition
record.
Explanation: An attempt to write data to the indicated
disk image was unsuccessful.
System Action: This LANRES disk server informed
the LANRES disk driver program of the error and
continued its usual operations.
User Response: Investigate and correct the error.
Source: LANRES Then stop and restart this LANRES disk server.
EWXxx1643E Dataset name dsname in
Source: LANRES
configuration file filename is too long.
Explanation: The dataset name field of a disk image
EWXxx1650E DBCS characters are not allowed in
definition record in the indicated configuration file is
the disk image name.
longer than 10 characters.
Explanation: A SHIFT OUT (X'0E') or SHIFT IN
(X'0F') character was found in the disk image name.
restart the LANRES disk server. User Response: Specify a disk image name that does
not contain DBCS characters.
Source: LANRES
Source: LANRES

EWXxx1651E Invalid window size size specified in EWXxx2001E The error returned was error.
Explanation: There was an error returned when a
Explanation: The window size field in the indicated query was made to determine what function was
configuration file is incorrect. The window size must be connected to your userid. The error is listed in the
a decimal number between 1 and 2048. message.
System Action: The LANRES command ends and the System Action: Command processing ends.
User Response: From the error returned, fix the
User Response: Correct the configuration file and problem and try the command again. This may require
restart the LANRES disk server. having to bring the connection to the server back up
again.
Source: LANRES
Source: LANRES
EWXxx1653E Duplicate disk image name
disk_name specified. EWXxx2003E Packets lost in the transmission;
command canceled.
Explanation: Two or more disk images with the same
name were specified when this LANRES disk server Explanation: A read request has been sent but the
was started. number of packets read does not agree with the number
of packets sent from the NetWare NLM server on the
NetWare server.
User Response: Remove the specification of all but
one of the disk images and restart this LANRES disk User Response: Reenter the command. It may be
server. necessary to restart the link with the NetWare server. If
the condition persists, notify your system programmer.
System Programmer Response: Check the link
Source: LANRES
between the host and the NetWare server.
Source: LANRES
EWXxx1654E Incorrect Access Mode field
access_mode in configuration file
filename. EWXxx2004E DOS partition cannot be accessed by
the server.
Explanation: The access mode field in the indicated
configuration file is incorrect. Only a single character ’W’ Explanation: A request has been sent to read to or
or ’R’ is correct. write from the DOS partition on the server, however, an
authorized user has entered the REMOVE DOS
command to remove the memory used by DOS in the
server.
Source: LANRES
System Programmer Response: Restart the server
to load DOS back in the server.
EWXxx1655W More than 50 disk images defined.
Source: LANRES
Explanation: There were more than 50 disk images
defined for this LANRES disk server. Only the first 50
EWXxx2005E An error occurred trying to view the
images will be used.
log.
System Action: The LANRES disk serving function
Explanation: A command was issued to view the log.
continues.
The return code indicated that there was an error.
User Response: Start another LANRES disk server to
support the additional disk images.
Source: LANRES

EWXxx2006E File filename already exists. Specify EWXxx2010E File filename in use.
REPLACE option.
Explanation: The file could not be referenced because
Explanation: The specified file already exists. it is active.
System Action: Command processing ends. System Action: Command processing ends. The
User Response: If you want to overwrite the contents
of the file, then reenter the command with the User Response: Wait until the file is closed and then
REPLACE option. Otherwise, use a different file name. reenter the command.
System Programmer Response: None. System Programmer Response: None.
EWXxx2007E File filename already exists; specify EWXxx2011E File filename is read-only.
REPLACE option.
Explanation: The command was unsuccessful
Explanation: The specified file already exists. because it attempted to write to, copy to, rename, or
delete a read-only file.
system status remains the same. System Action: Command processing ends. The
User Response: If you want to overwrite the file,
reenter the command with the REPLACE option. If you User Response: If you want to change this file,
want to keep the file, you can rename the file, using the change the file attributes to NORMAL using the
command to rename, or you can specify a different file CHANGE ATTRIBUTES distribution command and then
name for the new file. If you want to examine the file on reenter the command.
the host, you can use the distribution command to
receive the file to get a copy of it.
Source: LANRES
Source: LANRES
EWXxx2012E The filename specified for the
NetWare server, dirname, is a directory.
EWXxx2008E File filename already exists; file name
Explanation: A filename was entered for the NetWare
not changed.
server. However, the filename that was entered is really
Explanation: The distribution command to rename a a directory.
file request was unsuccessful because the ″new″ file ID
is already being used by another file.
User Response: Reenter the command entering a
valid NetWare filename and not a directory.
User Response: Specify another file ID.
Source: LANRES
Source: LANRES
EWXxx2013E Unsuccessful creating the directory
dname.
EWXxx2009E Directory dname already exists.
Explanation: A distribution command to copy a file or
Explanation: The specified directory already exists. make a directory request was unsuccessful because it
could not create the new directory on the NetWare
server.
User Response: You can use the distribution
command to list files to examine the existing directory.
Use the distribution command to either remove a User Response: Check to see if a file with the same
directory or rename the directory to give it a new name as the directory already exists. Use the
directory name. distribution command to list files. Verify that the volume
name is correct. If the file exists, specify another
directory name or rename the file using the distribution

command. Then, reenter the command to copy files or User Response: None.
make a directory.
Source: LANRES
Source: LANRES
EWXxx2017E File filename has been changed since
EWXxx2014E Error writing file filename LASTMOD; file attributes not changed.
Explanation: An input/output error occurred when the Explanation: The file attributes are not changed
specified file was being written on the server. The because the file was changed at some point after the
volume space limit may have been exceeded. It is last modification date and time information specified on
possible that the primary File Allocation Table or the EWXDS ATTRIBUTES request.
Directory table was damaged.
System Action: Command processing ends. system status remains the same.
User Response: Determine if the disk is full, or if you User Response: Check the file using the EWXDS
have exceeded your volume space limit. If so, remove LIST command and reenter the command with a
files and purge the deleted files with the purge different LASTMOD date and time.
command, or request for your volume space limit to be
increased. Reenter the command. If the error persists,
notify your server administrator. Source: LANRES
System Programmer Response: Verify disk usage
and volume space limits. Determine if the volume is full. EWXxx2018E Message cannot be longer than nn
It may be necessary to purge deleted files on the characters; message not sent.
volume. If the there does not appear to be a disk usage
or limit problem, and the problem persists, run the Explanation: The distribution command to send a
NetWare VREPAIR NLM to correct the problems on the message to a NetWare user has been entered with
volume. VREPAIR will correct many of the problems message text that is longer than the maximum allowed.
that can occur if the primary File Allocation Table or For messages sent to all users or to a specific user ID,
Directory table is damaged. the maximum is 57 characters. For messages sent to
the NetWare console, the maximum is 79 characters.
Source: LANRES
EWXxx2015E An input/output error occurred when
the specified file was being read. User Response: Reenter the command with a shorter
message text.
Explanation: It is possible that the NetWare server’s
primary File Allocation Table or Directory table was System Programmer Response: None.
damaged. Source: LANRES
User Response: Reenter the command. It may be EWXxx2019E User user is not logged in.
necessary to reissue the EWXCONN LINK command to Explanation: The specified user is not logged in to the
reset the connection. If the condition persists, notify NetWare server, so no message has been sent. This
your system programmer. message is applicable only when the userid option of
System Programmer Response: Run the NetWare the command is used.
VREPAIR NLM to correct hard disk problems on the System Action: Command processing ends. The
volume. VREPAIR will correct minor problems that can system status remains the same.
occur if the primary File Allocation Table or Directory
table is damaged. User Response: Try again later after the user is
logged in.
Source: LANRES
EWXxx2016E File filename is empty. Source: LANRES
Explanation: An LANRES command was issued to

copy the file from the server to the host, but the server
file is empty. It is not possible to retrieve an empty file.

the volume information for your particular volume. If you
EWXxx2021E File filename not found.
get message 2021, the volume does not exist. Ask your
Explanation: The specified file was not found. The file system programmer for help. If the volume does exist,
does not reside on the directory, the file identification note the number of the blocks left in the volume. If you
was misspelled, or incomplete identification was decide to erase some of the files, use the distribution
provided. command to delete files.
System Action: Command processing ends. The System Programmer Response: Check that all the
system status remains the same. volumes are correctly allocated. If the specified volume
has not been created, determine if this volume should
User Response: Verify that the volume on which the
be added or a different volume should be used by the
file resides is mounted and that the complete file
user.
identification was spelled correctly.
Source: LANRES
Source: LANRES
EWXxx2025E Paths must end with a backslash
when SUBDIR is specified.
EWXxx2022E Directory dname not found.
Explanation: The SUBDIR option can only be used to
Explanation: The specified directory was not found. copy entire subdirectories and neither a source not
Either the directory does not reside on the volume, the destination file name can be specified. The backslash (\)
directory name was misspelled or incomplete at the end of both the source path and destination path
identification was provided to cause the appropriate verifies that the previous characters are interpreted as
path to be searched. subdirectory names instead of file names.
System Action: Command processing ends. The System Action: Command processing ends. The
system status remains the same. system status remains the same.
User Response: To verify the directory exists, enter User Response: Correct the error and reenter the
the command to list the files. Verify that the volume on command.
which the directory resides is mounted.
Source: LANRES
Source: LANRES
EWXxx2026E Error opening the file filename.
EWXxx2023E Cannot remove a nonempty directory.
Explanation: An input/output error occurred when the
Explanation: The distribution command to remove a specified file was being opened, or the file is an
directory has been entered to remove an existing execute-only file, or the file is being used by another
directory and the specified directory contains files. user.
User Response: Enter the distribution command to list User Response: Check to see if the file is an
file and examine the files in the directory. If you decide execute-only file by using the command to list the files.
to erase all the files in the directory, use the distribution If the file is not an execute-only file, reenter the
delete command. command. If the error persists, notify your system
programmer. The file may also be in use by another
System Programmer Response: None. user. Be sure that there is no one else using the file.
Source: LANRES System Programmer Response: Run the NetWare
VREPAIR NLM to correct hard disk problems on the
EWXxx2024E Volume volname not found or volume volume. VREPAIR will correct minor problems that occur
is full. if the primary File Allocation Table or Directory table is
damaged, which may have been the reason for the
Explanation: The distribution command to copy files error.
was entered to copy files from one directory to another
directory and the specified target volume does not exist Source: LANRES
or the target volume does not have any space left.
User Response: Enter the distribution command to list

not been removed from the server. The DOS error code
EWXxx2027I The log file was cleared on date at time.
meaning can be found in the DOS reference manual.
Explanation: This is an informational message
Source: LANRES
indicating when the log was last cleared.
EWXxx2032E Incorrect distribution command name
issued.
Explanation: The user entered a command that was
System Programmer Response: None. not recognized by the distribution.
EWXxx2028E File(s) must be on the local server. User Response: Verify that the distribution command
was spelled correctly. See OS/390 LANRES
Explanation: The distribution command that you
Configuration Files and Commands for correct syntax.
entered cannot be used to process files on a remote
server. You probably preceded the file name(s) with a System Programmer Response: None.
remote server name. The server name should not be
Source: LANRES
specified, or else it must be the local server name.
EWXxx2033E The UNIT parameter contains
incorrect syntax. The 5th character
User Response: Verify that the local server, the server must be a dash (-).
that your system is physically connected to, is the
Explanation: The fifth character must be a dash (-)
correct server.
when the six character format is specified.
System Action: The distribution command is not
Source: LANRES processed.
User Response: Correct and retry the failing
EWXxx2029E Unable to load file filename on the command.
server.
Explanation: An error occurred while loading the
Source: LANRES
indicated file on the server. Possible causes for the
error are: the NLM is already loaded on the server and
the NLM cannot be loaded more than once, the NLM EWXxx2034E The UNIT parameter has incorrect
requires that other NLMs be loaded first, or the file is length. The length must be 4 to 6
not an NLM. characters.
System Action: Command processing ends. The Explanation: The UNIT parameter must contain at
system status remains the same. least four characters and not more than six.
User Response: Verify that you are specifying the System Action: The distribution command is not
correct NLM and that all prerequisite NLMs are already processed.
loaded.
User Response: Correct and retry the failing
System Programmer Response: None. command.
Source: LANRES System Programmer Response: None.
Source: LANRES
EWXxx2030E command was unsuccessful. DOS
error code-nn
EWXxx2036E Error copying the file filename.
Explanation: An unexpected error has occurred while
working with files on the DOS partition of the server. It Explanation: An input/output error occurred when the
is possible that DOS has been removed from the server. specified file was being copied. The primary File
Allocation Table or Directory table may be damaged.
User Response: Verify that the command syntax is system status remains the same.
correct and retry the command. If the error persists,
notify your server administrator. User Response: Reenter the command. If the error
persists, notify your system programmer.
System Programmer Response: Verify that DOS has

System Programmer Response: Run the NetWare User Response: None.
VREPAIR NLM to correct hard disk problems on the
volume. VREPAIR will correct minor problems that can
occur if the primary File Allocation Table or Directory Source: LANRES
table is damaged.
Source: LANRES EWXxx2044E The length of a directory name
cannot be more than 254 characters.
EWXxx2039E End of file reached; no file was Explanation: The user entered a directory name that
copied. was more than 254 characters in length.
Explanation: The server file contains only an System Action: Command processing ends. The
end-of-file character. This file is considered to be empty system status remains the same.
and cannot be copied. This error will also occur when
request is made to copy from a particular record of the User Response: Correct the directory name to be less
file, and the file contains less than that number of than 254 characters.
records. System Programmer Response: None.
System Action: Command processing ends. Source: LANRES
User Response: Verify that the file does contain data,
and the number of records in the file. Reenter the EWXxx2048E The two volume names vol1 and vol2
command with the correct values or parameters. must be the same.
System Programmer Response: None. Explanation: The attempt to rename the directory or
Source: LANRES file was unsuccessful, because the files/directory to be
renamed must reside on the same volume.
EWXxx2040E Distribution command name ended System Action: Command processing ends. The
with a server error code of nn. system status remains the same.
Explanation: An unexpected error occurred while User Response: Enter the same volume name for
processing the command. both directories or files and reenter the command.
System Action: Command processing ends. The System Programmer Response: None.
User Response: Verify that the command syntax is
correct and reenter the command. If the error persists, EWXxx2049E Directory cannot be removed.
notify your system programmer of the server error code.
Explanation: The attempt to remove a directory on the
System Programmer Response: See the NetWare NetWare server by specifying the option to remove the
System Messages book for the server error code. directory with the delete files command was
Source: LANRES unsuccessful. The error may be caused by: Not all files
have been deleted from the directory, there are
subdirectories inside that directory, or the DeleteInhibit
EWXxx2041I time renaming filename1 to filename2. flag was set on for that directory.
Explanation: The information message is displayed System Action: Files may have been removed from
when the distribution command to rename a file with the the directory but the directory remains.
option to TYPE out information messages is used.
User Response: Check to see if any of the reasons
System Action: The specified operation is performed. for the error listed above apply. Correct the situation
and use the command to remove directories to remove
the directory.
Source: LANRES
Source: LANRES
EWXxx2042I time copying filename1 to filename2.

EWXxx2052E You must be logged into the local
Explanation: The information message is displayed server to run this command.
when the distribution command to copy a file with the
Explanation: You must be logged into the local server
option to TYPE out information messages is chosen.
to enter this command. The local server is the server
System Action: The specified operation is performed. running the LANRES NLMs that you are directly

connected to by one of the LANRES communication
EWXxx2060I p1 p2 p3 p4/p5/p6 p7:p8:p9
methods. If you enter the EWXDS QUERY ID
command, your local server is shown opposite ″File Explanation: This is used for a buffer that will be
Server Name″ and the server you are logged into is formatted and displayed.
shown opposite ″Logged in Server Name″.
User Response: Enter the EWXCONN DROP
command to drop the current connection. Then enter Source: LANRES
the EWXCONN LINK command and directly connect to
the server that you want the command to run on.
EWXxx2061E Error_text returned on open of dataset
System Programmer Response: None. dataset
Source: LANRES Explanation: The attempt to open dataset dataset on
the host, was unsuccessful. The reason for the error is
identified in the message.
EWXxx2056I SERVER number = servername
Explanation: Indicates the server name of a NetWare
server that is connected to the same LAN as the current User Response: The error text will identify the reason
server. for the error. Possible causes include: dataset was not
found or access was denied. Actions will depend on the
specific cause of the error.
Source: LANRES
Source: LANRES
EWXxx2062I Directories found: dirs.
EWXxx2057I Filename Size Attrs Last Arc Date Time
Explanation: Indicates the number of directories found
Explanation: This is used for a header that will be when the distribution command to list the files in a
formatted and displayed. directory was issued.
System Action: None. System Action: None.
EWXxx2058I Filename Size Attrs Create Date Time EWXxx2063I Files found: files (bytes Bytes).
Explanation: This is used for a header that will be Explanation: Indicates the number of files found when
formatted and displayed. the distribution command to list the files in a directory
was issued and the number of bytes these files occupy.
Source: LANRES
Source: LANRES
EWXxx2059I Filename Size Attrs Mod Date Time
EWXxx2064I buffer
Explanation: This is used for a header that will be
formatted and displayed. Explanation: Displays a buffer that has been
formatted to the user.
Source: LANRES

Source: LANRES
EWXxx2069E Incorrect date, date, specified.
Explanation: The date entered in not a valid date.
EWXxx2065I parm1 parm2 parm3 parm4 parm5
Explanation: Sets up a buffer to be formatted and
displayed to the user.
User Response: Choose a valid date and reenter the
command.
Source: LANRES
Source: LANRES
EWXxx2070E Error_text returned on reading of file
EWXxx2066E The directory name, dirname, filename.
specifies a server.
Explanation: An attempt to read the host file,
Explanation: A directory name was entered that filename, was unsuccessful. The reason for the error is
included a server name. The server name cannot be a specified by error_test.
part of the directory name.
System Action: Command processing ends. The system status remains the same.
User Response: Use the information provided by
User Response: You can do one of two things. Enter error_text to determine the cause of this error.
the directory name again without the server name. Or, if
you are not logged in to the server that you want to run
the command against, log in to this server and try Source: LANRES
running the command again.
System Programmer Response: None. EWXxx2071E The connection to the server is to the
administration function.
Source: LANRES
Explanation: You are requesting to run a distribution
command, but you do not have a connection to the
EWXxx2067E Incorrect filename, filename,
distribution function.
specified.
Explanation: The file name entered is not a valid file
name.
User Response: Drop the connection from the current
function, get a connection to the distribution function,
and reenter the command.
User Response: Specify a correct file name.
Source: LANRES
Source: LANRES
EWXxx2072E There is no connection to the server.
EWXxx2068E Incorrect time, time, specified.
Explanation: You issued a command for the LANRES,
Explanation: The time entered in not a valid time. but you do not have a connection to the server.
User Response: Choose a valid time and reenter the User Response: Issue the EWXCONN LINK
command. command to receive a connection to the NetWare
server.
Source: LANRES
Source: LANRES

EWXxx2073E The connection to the server is to the EWXxx2152I Logged in Server Name. . . . . . . . . .
disk function. name
Explanation: You are requesting to run a distribution Explanation: You are logged in to a user ID on this
command, but you do not have a connection to the NetWare server. This may or may not be the same as
distribution function. the local server that you are connected to. The local
server is the server that is running the LANRES NLMs.
system status remains the same. System Action: None.
User Response: Drop the connection from the current User Response: None.
Source: LANRES
Source: LANRES
EWXxx2153I Logged in NetWare Level. . . . . . . . .
vrelease.mod
EWXxx2074E The connection to the server is to the
Explanation: This is the level of the NetWare server
host-to-LAN Print function.
that you are logged in to.
Explanation: You are requesting to run a distribution
command, but you do not have a connection to the
distribution function. User Response: None.
Source: LANRES
User Response: Drop the connection from the current
and reenter the command. EWXxx2154I File Server Name . . . . . . . . . . . . name
System Programmer Response: None. Explanation: This is the NetWare server that you are
connected through. This is the server that is running the
Source: LANRES LANRES NLMs.
EWXxx2075E The connection to the server is to the
LAN-to-host Print function. User Response: None.
Explanation: You are requesting to run a distribution System Programmer Response: None.
command, but you do not have a connection to the Source: LANRES
distribution function.
System Action: Command processing ends. The EWXxx2155I NetWare Level. . . . . . . . . . . . . .
system status remains the same. vrelease.mod
User Response: Drop the connection from the current Explanation: This is the level of the NetWare server
function, get a connection to the distribution function, that you are connected through.
Source: LANRES
EWXxx2151I Logged in Userid . . . . . . . . . . . . userid Source: LANRES
Explanation: You are logged in to this user ID on the

NetWare server. EWXxx2156I Host Function. . . . . . . . . . . . . . function
System Action: None. Explanation: The command you entered were made
by this LANRES host function.
Source: LANRES
Source: LANRES

EWXxx2157I Host Level . . . . . . . . . . . . . . .
vversion.release.mod.sl Source: LANRES
Explanation: This is the level of the host LANRES
program that you are using. EWXxx2177E Error_text returned on closing dataset
dataset.
Explanation: An attempt to close dataset dataset on
System Programmer Response: None. specified by error_text.
EWXxx2158I NLM Function . . . . . . . . . . . . . . User Response: Use the information provided by
function error_text to determine the problem.
Explanation: This is the LANRES function that you System Programmer Response: None.
are connected to on the NetWare server.
Source: LANRES
User Response: None. EWXxx2178E Error_text returned on deleting
dataset dataset.
Explanation: An attempt to delete dataset dataset on
Source: LANRES
specified by error_text.
EWXxx2159I NLM Service Level . . . . . . . . . . .
service_level
Explanation: This is the service level of the LANRES
function that you are connected to on the NetWare
error_text to determine the problem.
server.
Source: LANRES
EWXxx2179E The length of the translated string is
Source: LANRES larger than the buffer.
Explanation: An attempt was made to translate a
EWXxx2175I None string that was larger than the buffer.
Explanation: This is a message used in an System Action: Command processing ends. The
information message. system status remains the same.
System Action: None. User Response: None.
User Response: None. System Programmer Response: None.
Source: LANRES
EWXxx2180E There was an error renaming
filename1 to filename2.
EWXxx2176E Error_text returned on writing to
dataset dataset. Explanation: You requested to rename a file, but an
error occurred.
Explanation: An attempt to write to dataset dataset on
the host, was unsuccessful. The reason for the error is System Action: Command processing ends. The
specified by error_text. system status remains the same.
System Action: Command processing ends. The User Response: There are more informational
system status remains the same. messages that accompany this message. Use these
additional messages to determine the problem.
error_text to determine the problem. System Programmer Response: None.

Source: LANRES User Response: EWXDS GET or EWXDS PUT a
dataset that has a record format of FB or VB.
EWXxx2181E There was an error copying filename1 System Programmer Response: None.
to filename2.
Source: LANRES
Explanation: You requested to copy a file, but an
error occurred.
EWXxx2185E A severe error occurred trying to
System Action: Command processing ends. The view the dsname dataset.
Explanation: An attempt was made to BROWSE the
User Response: There are more informational dataset using the ISPF BROWSE function. The
messages that accompany this message. Use these application indicated a severe error occurred.
additional messages to determine the problem.
System Programmer Response: None. system status remains the same.
Source: LANRES User Response: Determine if there is a problem with
the dataset listed in the error message and fix the
problem.
EWXxx2182I Successfully renamed numfiles of
totfiles files. System Programmer Response: None.
Explanation: This is an informational message Source: LANRES
indicating how many files were successfully renamed.
System Action: Command processing ends. The EWXxx2186E Requested dataset, dsname, is empty.
Explanation: A request was made to view the dataset
User Response: If the two numbers in the message in the message, but the dataset is empty.
are different, then there are some files that were NOT
renamed. Determine what they are from the job log and
the reason why they were not renamed.
Source: LANRES
Source: LANRES
EWXxx2183I Successfully copied numfiles of totfiles
files. EWXxx2187E The member name must be bounded
by ’/’.
Explanation: This is an informational message
indicating how many files were successfully copied. Explanation: If a member name is specified, it must
be bounded by slashes. Or, you may have entered a
dataset name that included a member and didn’t use
the MEMBER option.
User Response: If the two numbers in the message
are different, then there are some files that were NOT
copied. Determine what they are from the job log and
the reason why they were not copied. User Response: Reenter the command with the
slashes around the member name.
Source: LANRES
Source: LANRES
EWXxx2184E Distribution supports FB or VB
recfm’s. The dataset has a RECFM of EWXxx2188E An asterisk may not be a part of the
recfm. member name.
Explanation: The user attempted an EWXDS GET or Explanation: If a member name is specified, it may
EWXDS PUT. But, when the dataset was opened, it not contain an asterisk.
showed a RECFM that was not FB or VB. LANRES only
supports FB or VB record formats. System Action: Command processing ends. The
system status remains the same. User Response: Reenter the command specifying a
member name without asterisk’s.

EWXxx2196E The dataset name entered cannot
Source: LANRES have an asterisk in the fourth qualifier
or beyond.
EWXxx2189W The value for option was not valid. It Explanation: An asterisk was entered in the dataset
was changed to newvalue. name that went beyond the third qualifier.
Explanation: The value for the option specified was System Action: Command processing ends. The
not valid. It was changed so that processing could system status remains the same.
continue.
User Response: Reenter the command. Do not place
System Action: Command processing ends. The an asterisk in the fourth qualifier or above.
Source: LANRES
Source: LANRES EWXxx2197E The dataset specified is not a
partitioned dataset.
EWXxx2190E The dataset name, dsname, is too Explanation: The dataset name specified is not a
long. partitioned dataset. But, you specified the member
option as if it were a partitioned dataset.
Explanation: The dataset name entered is too long.
system status remains the same. User Response: Reenter the command entering a
valid partitioned dataset name if you are using the
User Response: Reenter with a dataset that is the member option or enter a valid sequential dataset name
correct length. without the member option.
EWXxx2191E The member name, member, is too EWXxx2198E The dataset specified is not a
long. sequential dataset.
Explanation: The member name entered is too long. Explanation: The dataset name specified is not a
System Action: Command processing ends. The sequential dataset, but is a partitioned dataset.
system status remains the same. System Action: Command processing ends.
User Response: Reenter with a member that is the User Response: Reenter the command entering a
correct length. valid partitioned dataset name if you are using the
System Programmer Response: None. member option or enter a valid sequential dataset name
without the member option.
Source: LANRES
EWXxx2195E The value specified, value, cannot be Source: LANRES

more than 9 digits long.
Explanation: A value for the option FROM, FOR, EWXxx2199E The option_1 option must be used
OFFSET, LENGTH or LRECL was entered with a value before specifying option_2.
that was more than 9 digits long. Explanation: In order to use the option specified, put
System Action: Command processing ends. The either ASCII or BINARY before the option shown in the
system status remains the same. message.
User Response: Reenter the command with the System Action: Command processing ends.
correct value. User Response: Reenter the command specifying
System Programmer Response: None. either ASCII or BINARY.

Source: LANRES

EWXxx2301E Option option requires a numeric
value. User Response: Reenter the command. If the
problem persists, take down the link using the
Explanation: The specified option requires a numeric
EWXCONN DROP command and restart it with the
value to be specified. Either no value was found or a
EWXCONN LINK command.
non-numeric value was found.
command. EWXxx2306E Error_text returned on read of file
filename
Explanation: The specified error was returned when
Source: LANRES
reading from the identified file.
EWXxx2302E Option option requires a value.
User Response: The cause of the error should be
Explanation: The specified option requires a value to
identified in the error text. Correct the problem and
be specified. No value was found.
Source: LANRES
command.
EWXxx2307W Error_text error returned on close of
file filename
Source: LANRES
attempting to close the identified file. The file may be
EWXxx2303S Storage allocation error. intact.
Explanation: The program running was unable to System Action: Command processing ends.
allocate sufficient storage to complete the command.
User Response: Examine the file to determine if the
System Action: Command processing ends. content is correct. If not, the error text identifies the
cause of the error. Correct the problem and reenter the
command.
Source: LANRES
Source: LANRES
EWXxx2304E Error translating string.

EWXxx2308E Incorrect server volume name:
Explanation: While attempting to translate a string, a volname
translation error occurred. The string may have been a
Explanation: The server volume name specified on
server file name or the actual data that was being sent
the PC file name path was incorrect or missing. The
to the server.
volume name must be specified for all files.
User Response: Correct the volume name and
System Programmer Response: Verify that the user reenter the command.
has the correct code pages selected and that the
translation tables are available.
Source: LANRES
Source: LANRES
EWXxx2309E Incorrect server file name: filename

EWXxx2305E Error_text error returned from pipe.
Explanation: The server file name specified was
Explanation: The identified error was returned from
incorrect or missing. A PC file name must be specified,
the host to server connection. The data link is probably
or the wildcard * must be used. If a wildcard is used,
not available.
then the wildcard may not be accompanied by any other
characters. For example, sys:\t*.ext is incorrect because

the t appears before the *. The length server path
EWXxx2313E Error_text error returned on write to
specified must be less than the NetWare restricted
dataset dataset.
length of 254 characters.
writing to the identified dataset.
User Response: Correct the file name and reenter the
command.
User Response: The cause of the error is identified in
the error text. Correct the problem and reenter the
Source: LANRES command.
EWXxx2310E Error matching file filename_pattern -
Source: LANRES
Error_message
Explanation: While attempting to determine the host
EWXxx2314W Error_text returned on open of
files that matched the specified file name pattern the
dataset dataset.
identified error occurred.
Explanation: An attempt to open the translation
defaults dataset was unsuccessful. The reason for the
User Response: User response will depend on the error is identified by error_text.
error text. If the file was not found, the user should
reenter the command using a different pattern. If the
error was a protection problem, the user should contact User Response: The file transfer will continue using
their system programmer to obtain access. the system default values. If these are not correct,
remove the transferred file and reenter the command
with the correct translation defaults file specified in the
Source: LANRES EWXTRANS ddname. If the error text indicates
improper authorization, see your system programmer.
EWXxx2311E Incorrect host dataset name dataset System Programmer Response: If the user was
denied access, grant them access to the dataset.
Explanation: The dataset name specified was not
valid. Correct the dataset name and reenter the Source: LANRES
command.
System Action: Command processing ends. EWXxx2315I Time starting transfer of name
User Response: Correct the error and reenter the Explanation: name is being transferred to the server
command. or from the server. This message is informational only.
System Programmer Response: None. System Action: None. Message is informational only.
EWXxx2312W An incorrect line received: dataline
Source: LANRES
Explanation: The LANRES list file command returned
an incorrect line of data. The line of data will be
EWXxx2316I Time completed transfer of name
ignored. It is possible that undetected I/O errors are
occurring on the disk, or that undetected Explanation: name is being transferred to the server
communications errors are occurring between the host or from the server. This message is informational only.
and the server. If the problem persists, contact your
System Action: None. Message is informational only.
support programmer.
Warning message only. System Programmer Response: None.
User Response: If the message persists, contact your Source: LANRES
support programmer.
System Programmer Response: Determine if any I/O
errors are occurring on the host system disks or over
the data link.
Source: LANRES

help in finding the cause of the error.
EWXxx2317W The entry filename in defaultname is
too long. System Action: Command processing continues.
Warning message only.
Explanation: The entry, filename, in the translation
defaults, defaultname, was incorrect. Names must be User Response: Determine the cause of the error,
shorter than the system identified maximum length. correct, and if necessary reenter the command.
System Action: Command processing continues. System Programmer Response: None.
Warning message only.
Source: LANRES
User Response: If you are using your own file, correct
the entry. If you are using the system defaults file,
contact your system programmer. EWXxx2323E Error_text returned from read file list.
System Programmer Response: If the problem is in Explanation: As part of the command processing,
the system translation defaults, correct the identified LANRES created a list of the datasets. While reading
entry. from this list an error occurred. The error text describes
the error that occurred.
Source: LANRES
EWXxx2318W Extension entry extension in User Response: Determine the cause of the error
defaultname exceeds 3 characters. from the error text. If necessary contact your software
support personnel.
Explanation: The specified extension entry in the
translation defaults identified above was incorrect. System Programmer Response: None.
Extensions must be less than or equal to 3 characters Source: LANRES
in length.
System Action: Command processing continues. EWXxx2325W Server File extension file_extension
Warning message only. too long - truncated.
User Response: If you are using your own file, correct Explanation: The server file extension given to
the entry. If you are using the system defaults file, LANRES was too long. The file extension is truncated to
contact your system programmer. 3 characters.
System Programmer Response: If the problem is in System Action: Command processing continues.
the system EWXTRANS default file, correct the
identified entry. User Response: None.

Source: LANRES
EWXxx2319W Error_text error returned on read of
dataset dataset EWXxx2326W Server File name file_name too long -
Explanation: This error error_text was returned when truncated.
reading from dataset dataset. The dataset opened was Explanation: The server file name given to LANRES
not critical to the success of the command. was too long. The file name is truncated to 8
System Action: Command processing continues. characters.
Warning message only. System Action: Command processing continues.
User Response: The cause of the error should be User Response: None.
identified in the error text. Correct the problem and if
necessary, reenter the command. System Programmer Response: None.
Source: LANRES
EWXxx2328E Unable to delete dataset - filename
Reason error_text
EWXxx2320W Unable to create directory dirname
DOS Return code dos-return-code Explanation: An error occurred while transferring the
file from the NetWare server. As a result, an attempt
Explanation: While attempting to create a directory on was made to clean up and delete the dataset that was
the NetWare server, an unexpected error condition created. However, the error, error_text, occurred while
occurred. File transfers will continue, but other errors trying to delete the dataset.
may occur. The DOS return code given is displayed to

System Action: Command processing ends. System Programmer Response: None.
User Response: Based on the error text, determine Source: LANRES
why the dataset could not be removed. The dataset
may contain incomplete data and should be removed.
EWXxx2332E Server File name file_name too long
Or, if the dataset is EWXLANDS.LISTUT1, then an
attempt was made to erase the dataset that contained Explanation: The server file name given to LANRES
the list of server files. You need to just erase this was too long. When copying a file from the NetWare
dataset. server, server file name must be between 1 and 8
characters.
Source: LANRES
User Response: Reissue the command, specifying a
valid file name.
EWXxx2329E Option SUBDIR must be specified
when server directory is specified. System Programmer Response: None.
Explanation: The NetWare file name given identified a Source: LANRES
server directory and the SUBDIR option was not
specified, or the SUBDIR option was specified and the
NetWare file name was not a directory name. LANRES EWXxx2333E Subdirectory option not allowed to
considers a path a directory when it ends with a slash DOS partitions.
(/) or a backslash (\). Explanation: A command was issued that requested
System Action: Command processing ends. copying subdirectories to or from the server’s DOS
partition. Subdirectory operations are not supported for
User Response: Reenter the command, specifying a DOS partitions.
file for the server directory, or adding the SUBDIR
option. System Action: Command processing ends.
System Programmer Response: None. User Response: Reissue the command without the
subdirectory option.
Source: LANRES
EWXxx2330E File filename cannot be created. No Source: LANRES

space on device.
Explanation: The NetWare server returned and EWXxx2401I VOLUME NAME
indication that the volume is full. The file cannot be Explanation: This is used for a header that will be
allocated. formatted and displayed.
System Action: Command processing ends. System Action: None.
User Response: This condition may only be User Response: None.
temporary. Retry the command at a later time. If the
problem persists, contact the system programmer. System Programmer Response: None.
System Programmer Response: The volume may Source: LANRES

give a full indication because deleted files have not
been purged. Issue the PURGE command to free up EWXxx2402I BLKSIZE
space. If this does not free sufficient space, add a new
volume segment to the volume. Explanation: This is used for a header that will be
formatted and displayed.
Source: LANRES
EWXxx2331E Server File extension file_extension User Response: None.

too long System Programmer Response: None.
Explanation: The server file extension given to Source: LANRES
LANRES was too long. When copying a file from the
NetWare server, the server file extension given must be
3 characters or less.
User Response: Reissue the command, specifying a
valid extension.

EWXxx2403I BLK USED-(%) EWXxx2409E The file name or directory specified,
filename, is on a DOS partition.
formatted and displayed. Explanation: The file name or directory entered exists
on a DOS partition. The command or command option
that you entered does not support a file or directory
User Response: None. names on a DOS partition.
System Programmer Response: None. System Action: Command processing ends. The
Source: LANRES
User Response: Specify a file or directory name that
is not on a DOS partition.
EWXxx2404I BLK LEFT
formatted and displayed. Source: LANRES

EWXxx2410W EWXDS LIST does not display DOS
User Response: None. partition subdirectory information.
System Programmer Response: None. Explanation: The EWXDS LIST does not support
Source: LANRES showing subdirectory information for a DOS partition.
The SUBDIR option is ignored.
EWXxx2405I BLK TOTAL System Action: Command processing ends. The

formatted and displayed. User Response: Either specify a file name that is not
a DOS partition or find a way to get to the DOS
System Action: None. partition. One way is to DOWN the server.
Source: LANRES
EWXxx2411I The two files names are identical.
EWXxx2406I VOLUME MOUNTED - STATISTICS NOT Explanation: The two file names entered are the
AVAILABLE same. No request was sent to the NetWare server.
Explanation: This is used for a header that will be System Action: Command processing ends. The
formatted and displayed. system status remains the same.
System Action: None. User Response: Determine if the correct file names
User Response: None. were entered. If not, enter the command again with the
correct file names.
Source: LANRES
Source: LANRES
EWXxx2408E The file specified, fname, is a

directory. EWXxx2412I Successfully received nnn of mmm
files.
Explanation: The filename that was specified is not a
file, but a directory. Explanation: This message indicates how many of the
files were successfully received from the server.
system status remains the same. System Action: Command processing ends. The
User Response: Determine the correct filename to be
used for the operation to perform and retry the User Response: None.
operation. System Programmer Response: None.
Source: LANRES

EWXxx2413I Successfully sent nnn of mmm files. EWXxx2452I No compression was done because
storage was not decreased for host file
Explanation: This message indicates how many of the
filename.
files were successfully sent to the server.
Explanation: COMPRESS option was specified, but
was not used because the amount of saved data was
not decreased.
System Action: The file will be saved uncompressed.
Source: LANRES
Source: LANRES
EWXxx2414E Dataset dsname not found.
Explanation: The dataset indicated in the error
EWXxx2453E Error_text error - compression could
message was not found. If you were doing an EWXDS
not be done.
PUT, this could indicate that you specified a partitioned
dataset without a member specified versus a sequential Explanation: COMPRESS option was specified, but
dataset. If you were doing an EWXDS LOG VIEW, the there was an error when trying to compress data.
log dataset does not exist. If you were doing EWXDS
GET, the PDS/E dataset needs to exist when specifying
a member. User Response: None.
System Action: Command processing ends. The System Programmer Response: The cause of the
system status remains the same. error is identified in the error text. Correct the problem.
User Response: If you are trying to run an EWXDS Source: LANRES
PUT or GET command, enter a valid dataset name. If
you are trying to run the EWXDS LOG VIEW command,
you need to have things in the log before it can be EWXxx2454I No page aligned storage available for
viewed. Set logging on by issuing EWXDS LOG ON. compression dictionary.
System Programmer Response: None. Explanation: COMPRESS option was specified, but
there was an error when trying to get page aligned
Source: LANRES storage for a compression/expansion dictionary. An
attempt will be made to compress without using a
dictionary.
EWXxx2450I No compression was done because no
algorithms are available. System Action: Command processing continues.
Explanation: COMPRESS option was specified, but User Response: None.
there are no compression algorithms on the system.
Source: LANRES
System Programmer Response: None. EWXxx2455I No storage available to compress file.
Source: LANRES Explanation: COMPRESS option was specified, but
there was an error when trying to get storage for
compressing a file.
EWXxx2451E Compressed data could not be
expanded because the needed System Action: The file will be saved uncompressed.
algorithm was not available.
Explanation: A file written to the host with the
COMPRESS option could not be retrieved because this System Programmer Response: None.
system did not have the needed expansion algorithm. Source: LANRES
System Action: The PUT function stops.
User Response: None. EWXxx2456E Storage not available to check if
should expand file filename.
System Programmer Response: Ensure that host
compression/expansion algorithms are available. Explanation: A file may have been saved on a GET
using the COMPRESS option. Storage needed to
Source: LANRES determine if the file was compressed was unavailable.

EWXxx2461E COMPRESS option invalid when
User Response: Ensure there is sufficient virtual output is to the display device.
storage available and reenter the command.
Explanation: The COMPRESS option was specified,
System Programmer Response: None. but no output dsname was specified. The output to the
display device would be unreadable.
Source: LANRES
System Action: GET processing for this file stops.
EWXxx2457E Error expanding compressed User Response: Specify a dsname for a file that is to
dictionary - error_text. be compressed, or do not specify the COMPRESS
option if the file is to be displayed.
Explanation: A file written to the host with the
COMPRESS option could not be retrieved because its System Programmer Response: None.
dictionary was compressed and could not be expanded.
Source: LANRES
User Response: None. EWXxx3001E User or group already exists.
System Programmer Response: Correct the problem Explanation: The user or group already exists. Two
causing the compression dictionary to not be able to be causes of this message are:
expanded. v Attempting to add an already existing user or group.
v Attempting to rename a user or group to an already
Source: LANRES existing user or group.
EWXxx2458E Data was compressed using a later If you are using NetWare Version 4.01 or later, this
level of code than PUT expansion code message may indicate that there is another directory
supports. services object by the same name on the server.
Directory services does not allow objects of different
Explanation: The level of code used when data was object types to use the same object name. For example,
compressed on the GET is newer than the level of code you cannot have a user and a print queue named SAM
available to expand the code on the PUT. The code on the same server.
cannot be expanded.
System Action: The PUT function stops. system status remains the same.
User Response: None. User Response: Check the spelling of the specified
System Programmer Response: Ensure that the user or group name. If the spelling is incorrect, correct
newest level of the PUT code is available on the it. Reenter the command.
system. If you are using NetWare Version 4.01 or later, make
Source: LANRES sure there is no other object by the same name on the
server.
EWXxx2459I No compression was done because System Programmer Response: None.

compression dictionary could not be Source: LANRES
built - error_text.
Explanation: COMPRESS option was specified, but EWXxx3002E Incorrect user or group name.
was not used because a compression dictionary could
not be built and an alternate algorithm not requiring a Explanation: A command was entered specifying a
dictionary was not available. user or group that could not be found. The use of
special characters could produce this message.
User Response: None. system status remains the same.
System Programmer Response: Correct the problem User Response: Check the spelling of the specified
causing the compression dictionary to not be built. Also, user or group name. If the spelling is incorrect, correct
ensure that all host compression/expansion algorithms it. Reenter the command.
are available.
Source: LANRES
Source: LANRES

EWXxx3003E Special characters not allowed in
user or group name. Source: LANRES
Explanation: A user or group name cannot contain
spaces or any of the following special characters: EWXxx3006E Command rejected: ″Require
Password″ is set to ″no″.
/ (slash)
\ (backslash) Explanation: A command was entered which requires
: (colon) the “Require Password” field on the Account
Restrictions screen of SYSCON to be set to “YES”.
; (semicolon)
, (comma) If you are using NetWare Version 4.01 or later, the
* (asterisk) “Require Password” field can be found in the Password
? (question mark) Restrictions screen of the NETADMIN or NWADMIN
utility.
NetWare may also restrict the user or group name from system status remains the same.
containing other special characters. This message may
appear if no name is specified. User Response: Enter the EWXADMIN REQPASSW
command and specify the “YES” parameter.
Note: Not all commands produce this message when a System Programmer Response: None.
user or group name contains one of the above
characters. Some commands will return message Source: LANRES
3002E Incorrect user or group name.
System Action: Command processing ends. The EWXxx3007E Command rejected: ″Allow User To
system status remains the same. Change Password″ is set to ″no″.
User Response: Reenter the command with a valid Explanation: A command was entered which requires
name. the “Allow User To Change Password” field in the
Account Restrictions screen of SYSCON to be set to
System Programmer Response: None. “YES”.
Source: LANRES If you are using NetWare Version 4.01 or later, the
“Allow User To Change Password ” field can be found in
EWXxx3004E User or group does not exist. the Password Restrictions screen of the NETADMIN or
NWADMIN utility.
Explanation: A command was entered specifying a
user or group that could not be found. System Action: Command processing ends. The
system status remains the same. User Response: Ask your system programmer or
someone who manages your account to change your
User Response: Check the spelling of the specified user ID’s “Allow User To Change Password” field to
user or group name. If the spelling is incorrect, correct “YES”. If you want your password changed, your system
it. Reenter the command with a valid name. programmer or someone who manages your account
System Programmer Response: None. can change it for you.
Source: LANRES System Programmer Response: Load the NetWare

SYSCON utility at a client workstation. Select Account
Restrictions on the User Information panel. Change the
EWXxx3005E Volume does not exist. “Allow User to Change Password” field in SYSCON to
“YES”. If the user ID’s password needs to be changed,
you may use the SYSCON utility or enter the LANRES
volume that could not be found.
change password command, EWXADMIN CHPW.
If you are using NetWare Version 4.01 or later, you can
use the NETADMIN or NWADMIN utility to change the
User Response: Check the spelling of the specified “Allow User To Change Password ” field in the
volume name. If the spelling is incorrect, correct it. If Password Restrictions screen.
you are unsure of the spelling, use the VOLUMES
Source: LANRES
command at the NetWare server console to view the list
of volumes mounted on the server. Reenter the
command with a valid volume name.

EWXxx3008E Command rejected: ″Force Periodic
Password Changes″ is set to ″no″.
User Response: Check the spelling of the specified
Explanation: A command was entered which requires
print queue or print server name. If the spelling is
the “Force Periodic Password Changes” field in the
incorrect, correct it. Reenter the command.
Account Restrictions screen of SYSCON to be set to
“YES”. System Programmer Response: None.
If you are using NetWare Version 4.01 or later, the Source: LANRES
“Force Periodic Password Changes” field can be found
in the Password Restrictions screen of the NETADMIN
or NWADMIN utility. EWXxx3011E Special characters not allowed in
print queue or print server name.
system status remains the same. Explanation: A print queue or print server name
cannot contain spaces or any of the following special
User Response: Enter the following command with characters:
the interval parameter set to a suitable non-zero value
(SYSCON uses a default of 40): / (slash)
v Enter the EWXADMIN PWEXPINT command. \ (backslash)
: (colon)
; (semicolon)
Source: LANRES , (comma)
* (asterisk)
EWXxx3009E Print queue or print server already ? (question mark)
exists.
Explanation: The command was unsuccessful NetWare may also restrict the print queue or print
because the print queue or print server already exists. server name from containing other special characters.
Two causes of this message are: This message may appear if no name is specified.
v Attempting to add an already existing print queue or
print server Note: Not all commands produce this message when a
v Attempting to rename a print queue or print server to print queue or print server name contains one of
an already existing print queue or print server. the above characters. Some commands will
return message 3010E Incorrect print queue or
If you are using NetWare Version 4.01 or later, this print server name.
message may indicate that there is another directory System Action: Command processing ends. The
services object by the same name on the server. system status remains the same.
Directory services does not allow objects of different
object types to use the same object name. For example, User Response: Examine the specified print queue or
you cannot have a user and a print queue named SAM print queue name. If the name contains any of the
on the same server. special characters, remove them. Reenter the command
with a valid print queue or print server name.
system status remains the same. System Programmer Response: None.
User Response: Check the spelling of the specified Source: LANRES

print queue or print server name. If the spelling is
incorrect, correct it. Reenter the command.
EWXxx3012E Print queue or print server does not
If you are using NetWare Version 4.01 or later, make exist.
sure there is no other object with the same name on the
server.
print queue or print server that could not be found.
EWXxx3010E Incorrect print queue or print server print queue or print server name. If the spelling is
name. incorrect, correct it. Reenter the command.
Explanation: A command was entered specifying a System Programmer Response: None.

print queue or print server that could not be found.
Source: LANRES

User Response: Correct the path name to specify the
EWXxx3013E Print queue not deleted; print jobs
desired file to remove. Reenter the command.
still present.
Explanation: The command to delete the print queue
was unsuccessful because print jobs were still present Source: LANRES
in the print queue.
System Action: Command processing ends. The EWXxx3017E Directory could not be removed.
Explanation: The attempt to remove a directory was
User Response: If you want to delete the print queue unsuccessful. The most likely cause is that the directory
regardless of the existing job count, reenter the is not empty.
command with the FORCE parameter.
Source: LANRES User Response: Connect to the distribution function
and enter the following command to determine the
cause of the error:
EWXxx3014E Directory could not be created.
v Enter the EWXDS RMDIR command.
Explanation: The attempt to create a directory was
unsuccessful. The directory path for the directory being
created may not exist. Source: LANRES
system status remains the same. EWXxx3018E Command rejected: Command
chaining cannot be nested.
User Response: Connect to the distribution function
and enter the following command to determine the Explanation: If you enter a EWXADMIN BEGINCC
cause of the error: command to begin command chaining, you must enter a
v Enter the EWXDS MKDIR command. EWXADMIN ENDCC or EWXADMIN RESTSYS
command to stop command chaining before you can
enter a second EWXADMIN BEGINCC command.
Source: LANRES
EWXxx3015E Specified file(s) or directory could
User Response: Change the command sequence.
not be removed.
Explanation: The attempt to remove a file or files was
unsuccessful. Probable causes are: Source: LANRES
v Subdirectories are present
v “Delete inhibit” flags set in the directory
EWXxx3019E Administration command name was
System Action: Command processing ends. The unsuccessful with internal error code
system status remains the same. xxx nnn.
User Response: Connect to the distribution function Explanation: An unexpected error has occurred while
and enter the following commands to determine the processing the administration command name. The
cause of the error: error code returned from the NLM is displayed. The
v Enter the EWXDS DELETE and EWXDS RMDIR internal error code has two parts, the LANRES error
commands. code xxx and the NetWare error code nnn.
Source: LANRES
User Response: Notify your system programmer of
the internal error code.
EWXxx3016E The path indicated is a directory, not
a path to a file. System Programmer Response: Look up the
NetWare error code nnn in the NetWare System
Explanation: The command attempted to remove one Messages book. The LANRES error code is only used
or more files but determined that the specified path by IBM service.
identified a directory only.
If the NetWare error code is not sufficient to indicate the
System Action: Command processing ends. The problem, enter the following sequence of commands
system status remains the same. and perform the indicated actions:

1. Enter EWXADMIN DEBUG ON. This places the
EWXxx3023E Command rejected: Bindery cannot
administration function in trace mode.
be restored during command chaining.
2. Run the command sequence that caused the error
again. The assumption here is that the error is Explanation: The EWXADMIN RESTBIND command
repeatable. cannot be used while a EWXADMIN BEGINCC
3. Enter EWXADMIN DISPDB. This displays the trace command is in progress. If a EWXADMIN RESTBIND
information on the host terminal screen and also command is processed, the bindery files saved during
writes it to a trace file. The LANRES trace file is the start of command chaining would be restored. In this
prefix.EWXADMIN.DEBUGMSG. case, any bindery modifications after the EWXADMIN
4. Enter EWXADMIN DEBUG OFF. This returns the BEGINCC command and prior to the EWXADMIN
administration function to normal mode. RESTBIND command would be lost.
5. Examine the trace file for problem determination and
fault isolation.
Source: LANRES
EWXxx3020E Command rejected: Command
chaining is not active. Source: LANRES
Explanation: The EWXADMIN ENDCC command
cannot be used unless a EWXADMIN BEGINCC EWXxx3024E Login script file exceeds the limit of
command is in progress. 4000 bytes.
System Action: Command processing ends. The Explanation: The command cannot process login
system status remains the same. script files longer than 4000 bytes.
User Response: Change the command sequence. System Action: Command processing ends. The
User Response: You must use the distribution
Source: LANRES
function to copy the login script file to the server. For
example, assume there is a user named BIGUSER and
EWXxx3021E Command rejected: Command a login script file on the host named
chaining is not active. prefix.BIGLOGIN.SCRIPT is longer than 4000 bytes.
Explanation: The EWXADMIN RESTSYS command Enter the following sequence of commands to install the
cannot be used unless a EWXADMIN BEGINCC file on the server:
command is in progress. 1. While still attached to the administration function,
System Action: Command processing ends. The enter:
system status remains the same. EWXADMIN USERINFO BIGUSER SYS
BIGUSER’s internal ID is returned along with other
System Programmer Response: None. information. Assume the internal ID returned is
1F000037.
Source: LANRES
2. Use the EWXCONN DROP command to drop the
connection to the administration function and the
EWXxx3022E Command rejected: Bindery cannot EWXCONN LINK command to connect to the
be saved during command chaining. distribution function.
Explanation: The EWXADMIN SAVEBIND command 3. If this system is using DOS as an operating system,
cannot be used while a EWXADMIN BEGINCC enter:
command is in progress. If a EWXADMIN SAVEBIND EWXDS PUT 'prefix.BIGLOGIN.SCRIPT'
SYS:\MAIL\1F000037\LOGIN (REPLACE
command is processed, the bindery files saved during
the start of command chaining would be overlaid. In this
If this system is using OS/2 as an operating system,
case, the EWXADMIN RESTSYS command would not
enter:
be able to restore the originally saved bindery files.
EWXDS PUT 'prefix.BIGLOGIN.SCRIPT'
System Action: Command processing ends. The SYS:\MAIL\1F000037\LOGIN.OS2 (REPLACE
system status remains the same. System Programmer Response: None.

User Response: Change the command sequence. Source: LANRES
Source: LANRES

EWXxx3027E Debug facility in use on target server. EWXxx3030E Unable to open bindery information
file.
Explanation: The debug facility is already in use by
another user on the target server. You must wait for that Explanation: The bindery information file could not be
user to stop use of the debug facility before you can opened on the server. This is usually because the user
use it. has insufficient trustee rights or the operating system is
unable to open the file (for example, if it is out of disk
space). The file is BINDERY.LST in SYS:\SYSTEM\,
and is used by the EWXADMIN QUERY BINDERY command.
User Response: Wait and retry the operation.
System Programmer Response: Tell the user of the system status remains the same.
debug facility to stop the debug facility by entering the
following command:
v Enter: System Programmer Response: If the user should
be able to enter the query bindery command, give the
EWXADMIN DEBUG OFF
user trustee rights to BINDERY.LST in SYS:\SYSTEM\.
Source: LANRES
Source: LANRES
EWXxx3028E Command rejected: Debug mode is

EWXxx3031E Current password not entered or
off.
incorrect.
Explanation: This command requires that debug
Explanation: A password in the correct format must
mode be enabled.
be supplied. in the format required.
User Response: Enable the debug facility with the
User Response: Use the keyword NULL for the
following command:
password if you are trying to assign a null password
v Enter: (which means no password) to a user. Otherwise, retry
EWXADMIN DEBUG ON the command with a valid password.
You must have trustee rights to LANADME.DBG and System Programmer Response: None.
LANADMO.DBG in the SYS:\SYSTEM\directory to use
Source: LANRES
the debug function. Reenter the unsuccessful
command.
EWXxx3032E Unable to close debug file.
Explanation: The system could not close the debug
Source: LANRES
file. This might happen if you lost trustee rights to the
file (for example, someone removed them) before you
EWXxx3029E Unable to open debug file. disabled the debug facility.
Explanation: The debug file could not be opened on System Action: Command processing ends. The
the server. This is usually because the user has system status remains the same.
insufficient trustee rights or the operating system is
unable to open the file (for example, if it is out of disk
space). System Programmer Response: Connect to the
administration function as the SUPERVISOR and enter
System Action: Command processing ends. Debug
the following command:
mode is not enabled.
v Enter:
EWXADMIN DEBUG OFF
System Programmer Response: If the user should
Source: LANRES
be able to use the debug facility, give the user trustee
rights to LANADME.DBG and LANADMO.DBG in
SYS:\SYSTEM\. EWXxx3033E Command rejected: New password
duplicated current or previous
Source: LANRES
passwords.
Explanation: The new password must be different
from the current password. In addition, if the user is
required to have unique passwords, then the new

password must be different from the eight previous System Action: Command processing ends. The
passwords. system status remains the same.
System Action: Command processing ends. The User Response: Check the spelling of the user or
system status remains the same. group name specified on the command line. If the
spelling is correct, you may have entered the command
User Response: Reenter the command with a new
previously. If the spelling is incorrect, correct it. Reenter
password.
the command.
Source: LANRES
Source: LANRES
EWXxx3034E Command rejected: SUPERVISOR or

EWXxx3037E Incorrect path specified, or trustee
equivalent authority required.
rights to the path required.
Explanation: The attempted operation requires that
the user be the NetWare SUPERVISOR or have
path that was incorrect or nonexistent, or the proper
security equivalence to SUPERVISOR.
trustee rights are required for the path before the
System Action: Command processing ends. The command can be processed.
User Response: Ask a user with SUPERVISOR system status remains the same.
authority to perform the action for you, or to assign
User Response: Verify that the correct volume name
SUPERVISOR security equivalence to your user ID.
and path were entered correctly on the command line. If
System Programmer Response: If required, assign the path is correct and you need trustee rights for the
SUPERVISOR security equivalence to the user. path, ask your system programmer to assign the trustee
rights to you.
Source: LANRES
System Programmer Response: Assign trustee
rights, if required, to the user for the path specified on
EWXxx3035E Command rejected: Target server the command line.
busy command chaining.
Source: LANRES
Explanation: The function you requested cannot be
performed at this time because another user has begun
command chaining operations on the target server. You EWXxx3038E Member does not exist.
must wait until that user finishes and then retry the
Explanation: The command tried to remove an
command.
existing user or group as a member when the user or
System Action: Command processing ends. The group is not a member.
User Response: Wait and retry the operation. system status remains the same.
System Programmer Response: Inform the user User Response: Check the spelling of the user or
performing command chaining to stop it by entering the group name specified on the command line. If the
following command: spelling is correct, you may have entered the command
v Enter: previously. If the spelling is incorrect, correct it. Reenter
the command.
EWXADMIN ENDCC
or Source: LANRES
EWXADMIN RESTSYS
Source: LANRES EWXxx3039E The password is shorter than the
minimum password length or greater
than 127 characters.
EWXxx3036E Member already exists.
Explanation: The user ID’s password must have a
Explanation: The command was unsuccessful. Two
length greater than or equal to the value of the
causes are:
“Minimum Password Length” field, but not greater than
v Attempting to add a user to a group when the user is 127 characters long.
already a member of that group
v Attempting to make a user a work group manager
when the user is already a work group manager

User Response: Specify a password with a shorter or System Programmer Response: None.
longer length. You may use the NetWare SYSCON
Source: LANRES
utility or enter the EWXADMIN USERINFO command to view
the minimum password length for your user ID.
EWXxx3042W Print queue created but the print
server does not exist.
Source: LANRES
Explanation: The command tried to create a print
queue and assign a print server to it. The print queue
EWXxx3040W Current password was not required was created successfully, but the command was
and was not used. unsuccessful while attempting to assign a print server to
the print queue. The specified print server name could
Explanation: A command was entered to change a
not be found. Use the NetWare PCONSOLE utility to
user ID’s password, and the user issuing the command
verify that the print server exists.
has SUPERVISOR authority or manages the specified
user ID. A SUPERVISOR or the user ID’s manager System Action: The print queue is created but the
need not specify the current password when changing print server is not assigned to it.
the user ID’s password.
System Action: The command continues. print server name. If the spelling is incorrect, correct it.
Use the EWXADMIN ASQSERV command to assign the
User Response: Verify that you have changed the
correct print server to the new print queue.
correct user ID’s password.
Source: LANRES
Source: LANRES
EWXxx3043W Print queue created but print server

EWXxx3041W Print queue created but print server
not assigned to it.
name contains special characters.
was created successfully, but the command was
was created successfully, but the command was
unsuccessful while attempting to assign a print server to
unsuccessful while attempting to assign a print server to
the print queue. This error message may appear when
the print queue. A print server name cannot contain
the server is out of memory or when the bindery is
spaces or any of the following special characters:
locked.
/ (slash) System Action: The print queue is created, but the
\ (backslash) print server is not assigned to it.
: (colon)
User Response: Use the EWXADMIN ASQSERV command
; (semicolon)
to assign the print server to the new print queue. If the
, (comma) command fails, notify your system programmer.
* (asterisk)
? (question mark) System Programmer Response: Use the NetWare
PCONSOLE utility to verify that the print server exists.
Assign the print server to the print queue from
NetWare may also restrict the print server name from PCONSOLE.
containing other special characters. This message may Source: LANRES
appear if no name is specified.
Note: Not all commands produce this message when a EWXxx3044E Security equivalence does not exist.
print queue or print server name contains one of Explanation: The command tried to withdraw a
the above characters. security equivalence from a user, but the user did not
System Action: The print queue is created but the possess that security equivalence.
print server is not assigned to it. System Action: Command processing ends. The
User Response: Examine the specified print server system status remains the same.
name. If the name contains any of the special User Response: Check the spelling of the user or
characters listed, remove them. Use the EWXADMIN group name entered on the command line. If the
ASQSERV command to assign the correct print server to spelling is correct, you may have entered the command
the new print queue. previously. If the spelling is incorrect, correct it. Reenter
the command with the correct information.

System Programmer Response: None. print queue name. If the spelling is incorrect, correct it.
Reenter the command.
Source: LANRES
EWXxx3045E Command rejected: ″Require Source: LANRES
Password″ is set to ″yes″. No null
passwords.
EWXxx3048E Special characters are not allowed in
Explanation: A command was entered which requires print queue name.
the “Require Password” field in the Account Restrictions
Explanation: A print queue name cannot contain
screen of SYSCON to be set to “NO”.
spaces or any of the following special characters:
system status remains the same. / (slash)
\ (backslash)
User Response: Enter the EWXADMIN REQPASSW
: (colon)
command and specify the “YES” parameter.
; (semicolon)
System Programmer Response: None. , (comma)
Source: LANRES * (asterisk)
? (question mark)
EWXxx3046W Print queue renamed but print server

was incorrect or does not exist. NetWare may also restrict the print queue name from
Explanation: The command tried to rename a print containing other special characters.
queue and inform the LAN-to-host print server of the System Action: Command processing ends. The
change. The print queue was renamed successfully, but system status remains the same.
the specified print server name was incorrect or could
not be found. Use the NetWare PCONSOLE utility to User Response: Examine the specified print queue
verify that the print server exists. A print server name name. If the name contains any of the special
cannot contain spaces or any of the following special characters, remove them. Reenter the command.
characters: System Programmer Response: None.
/ (slash) Source: LANRES
\ (backslash)
: (colon)
EWXxx3049E Command rejected: Another QUERY
; (semicolon) BINDERY command is being
, (comma) processed.
* (asterisk)
? (question mark) Explanation: The administration function only allows
one user to enter the EWXADMIN QUERY BINDERY
command at a time. The first EWXADMIN QUERY BINDERY
command must be completed before the next EWXADMIN
NetWare may also restrict the print server name from
QUERY BINDERY command can be entered by another
containing other special characters.
user.
System Action: The print queue is renamed and the
System Action: Command processing ends. The first
LAN-to-host print server is not informed.
EWXADMIN QUERY BINDERY command will continue to be
User Response: None. processed.
System Programmer Response: None. User Response: Wait for the first EWXADMIN QUERY
BINDERY command to be finished before reentering your
Source: LANRES
EWXADMIN QUERY BINDERY command.
EWXxx3047E Print queue does not exist.
Source: LANRES
Explanation: The specified print queue name could
not be found.
EWXxx3050E Print server already assigned to print
queue.
Explanation: The print server has already been
assigned to service the print queue.

EWXxx3054E The NFS ID specified already exists.
Explanation: The attempt to add an NFS ID to the
User Response: Check the spelling of the print server
NFSUSERS or NFSGROUP file in the SYS:\ETC\
and print queue entered on the command line. If the
directory was unsuccessful because the specified ID
spelling is incorrect, correct it. Reenter the command.
already exists in the file.
User Response: Be sure that the NFS ID specified is
EWXxx3051E Print server not servicing print correct. If it is, delete the NFS ID and then add it with
queue. the new NetWare ID.
Explanation: The print server cannot be removed from System Programmer Response: None.
the print queue because it is not servicing the print
Source: LANRES
queue.
EWXxx3055E Unable to unlock the filename file that
is locked.
User Response: Check the spelling of the print server
Explanation: The attempt to unlock the specified file
and print queue entered on the command line. If the
in the SYS:\ETC\ directory was unsuccessful.
spelling is incorrect, correct it. Reenter the command.
Source: LANRES
User Response: Determine why the file is locked. It is
possible that someone is using it. Unlock the file and
EWXxx3052E Unable to open the filename file. reenter the command.
Explanation: The attempt to open the specified file in System Programmer Response: None.
the SYS:\ETC\ directory was unsuccessful. This could
Source: LANRES
occur if the SYS:\ETC\ directory does not exist, you lack
the necessary trustee rights, or the file is locked.
EWXxx3056E The server is out of memory to lock
the filename file.
Explanation: The attempt to lock the specified file in
User Response: Determine which of the conditions
the SYS:\ETC\ directory was unsuccessful because the
mentioned in the explanation exist. Correct the problem
server ran out of memory.
Source: LANRES
User Response: Make more memory available and
EWXxx3053E Unable to create a temporary file.
Explanation: The attempt to create a temporary file in
Source: LANRES
the SYS:\ETC\ directory was unsuccessful. This could
occur if the SYS:\ETC\ directory does not exist, you lack
the necessary trustee rights, or the file is locked. EWXxx3057E There was a time-out trying to lock
the filename file.
system status remains the same. Explanation: The attempt to lock the specified file in
the SYS:\ETC\ directory was unsuccessful. The file is
User Response: Determine which of the conditions
already locked.
and reenter the command. System Action: Command processing ends. The
User Response: Determine why the file is locked. It is
Source: LANRES
possible that someone is using it. Unlock the file and

Source: LANRES
EWXxx3062E Unable to rename the temporary file
to filename.
EWXxx3058E There was an error trying to lock the
Explanation: The attempt to rename a temporary file
filename file.
in the SYS:\ETC\ directory to the specified file name
Explanation: The attempt to lock the specified file in was unsuccessful.
the SYS:\ETC\ directory was unsuccessful.
System Action: Command processing ends. The system status remains the same.
User Response: The temporary file still exists in the
User Response: Determine why the file cannot be SYS:\ETC\ directory. Rename the temporary file to
locked. Correct the problem and reenter the command. NFSUSERS if the request is to work with an NFS user,
otherwise, rename the temporary file to NFSGROUP.
Source: LANRES
Source: LANRES
EWXxx3059E The NFS ID must be an integer

between 0 and (2**32-1). EWXxx3063E The NFS ID did not exist in the
filename file.
Explanation: An incorrect NFS ID was specified. The
NFS ID value must be from 0 to (2**32-1). Explanation: The request to delete an NFS ID from
the specified file in the SYS:\ETC\ directory was
System Action: Command processing ends. The unsuccessful because the NFS ID does not exist in the
system status remains the same. file.
User Response: Change the NFS ID to a value from System Action: Command processing ends. The
0 to (2**32-1) and reenter the command. system status remains the same.
System Programmer Response: None. User Response: Make sure the correct NFS ID was
Source: LANRES entered.
EWXxx3060E The NetWare ID must be less than or Source: LANRES
equal to 47 characters in length.
Explanation: The NetWare ID specified was longer EWXxx3064E Unable to create the filename file.
than 47 characters.
Explanation: The attempt to create the specified file in
System Action: Command processing ends. The the SYS:\ETC\ directory was unsuccessful. The
system status remains the same. SYS:\ETC\ directory may not exist, the user may not
User Response: Change to a correct NetWare ID and have trustee rights to SYS:\ETC\, or the NetWare for
reenter the command. NFS product may not be installed on the server.
Source: LANRES
User Response: Make sure the SYS:\ETC\ directory
exists or that you have the trustee rights to the
EWXxx3061E Unable to open the filename.BKP file. SYS:\ETC\ directory. If the directory does not exist,
Explanation: The attempt to open the backup file in either create the directory or install the NetWare for
the SYS:\ETC\ directory was unsuccessful. This could NFS product on your server.
occur if the SYS:\ETC\ directory does not exist, you lack System Programmer Response: None.
the necessary trustee rights, or the file is locked.
Source: LANRES
EWXxx3065E The filename file did not exist to
User Response: Determine which of the conditions delete the NFS ID.
and reenter the command. Explanation: The attempt to delete an NFS user or
group was unsuccessful. The specified file does not
System Programmer Response: None. exist in the SYS:\ETC\ directory. It is possible that
Source: LANRES NetWare for NFS may not be installed on the server.

system status remains the same. authority to create and configure the print queue or print
server. Ideally, you should have security equivalence to
User Response: There is no NFS ID to delete.
the SUPERVISOR user ID to enter this command.
NetWare for NFS may need to be installed.
Source: LANRES
User Response: Ask the system administrator to give
you the proper authority to create the print queue or
EWXxx3066E Directory cannot be removed. print server, or to create the print queue or print server
for you.
Explanation: You attempted to remove a directory on
the NetWare server but the attempt failed. The failure System Programmer Response: If appropriate,
may be caused by: create the print queue or print server, or grant the
v Not all files have been deleted from the directory proper authority to the user. To grant the proper
v Subdirectories exist inside that directory authority, you may give the user security equivalence to
v The DeleteInhibit flag was set on for that directory. the SUPERVISOR user ID or to another user ID with
the authority to create print queues or print servers.
System Action: Command processing ends. Files
may have been removed from the directory but the Source: LANRES
directory remains.
User Response: Check to see if any of the reasons EWXxx3069E Cannot configure print queue or print
for failure listed above applies. Correct the situation and server, and cannot delete it.
use the EWXADMIN RMDIR command to remove the
Explanation: Your attempt to create a new print queue
directory.
or print server succeeded but you did not have sufficient
System Programmer Response: None. authority to configure the print queue or print server.
The command then tried to delete the print queue or
Source: LANRES print server but was unable to delete it. The system
administrator must grant you the authority to configure
EWXxx3067E This command is not supported on a the print queue or print server. Ideally, you should have
NetWare Version 4.01 or later server. security equivalence to the SUPERVISOR user ID to
enter this command.
Explanation: Certain LANRES administration
commands cannot be entered when you are logged-in System Action: Command processing ends. The print
to a NetWare Version 4.01 or later server. queue or print server was created but not properly
configured.
The new NetWare Version 4.01 architecture does not
support the following administration commands: User Response: Ask the system administrator to give
you the proper authority to configure the print queue or
v EWXADMIN BEGINCC
print server, or to configure the print queue or print
v EWXADMIN ENDCC server for you.
v EWXADMIN RESTBIND
System Programmer Response: If appropriate,
v EWXADMIN RESTSYS configure the print queue or print server, or grant the
v EWXADMIN SAVEBIND proper authority to the user. To grant the proper
authority, you may give the user security equivalence to
There are no substitutes for these unsupported the SUPERVISOR user ID or to another user ID with
administration commands. the authority to configure print queues or print servers.
System Action: Command processing ends. The Source: LANRES

User Response: Enter a supported command. EWXxx3070E Permission denied by NetWare
server. Insufficient trustee rights.
Explanation: You do not have sufficient authority to
Source: LANRES perform the operation. The proper file or directory
trustee rights may be required.
EWXxx3068E Insufficient rights to create and System Action: Command processing ends. The
configure print queue or print server. system status remains the same.
Explanation: Your attempt to create a new print queue User Response: Obtain the appropriate trustee rights
or print server failed because you did not have sufficient to perform the operation.
authority to create or configure the print queue or print
server. The system administrator must grant you the System Programmer Response: If appropriate, grant

the proper trustee rights to the user. System Programmer Response: None.
EWXxx3071W Name has no trustee rights or you EWXxx3075W Lines in file filename may have been
are not authorized for them. truncated.
Explanation: You tried to query the file and directory Explanation: The program tried to write information to
trustee rights assigned to a user ID or a group ID, but the host file filename, but the record length of the file
the trustee rights information cannot be displayed. This was not long enough and lines in the file may have
user or group has no trustee rights, or you do not have been truncated.
sufficient authority over the user or group to see their
trustee rights.
User Response: Set up a file with the correct record
System Action: The command completes and this
length and reenter the command.
warning message is displayed on the screen or written
to a file. System Programmer Response: None.
User Response: If necessary, obtain the appropriate Source: LANRES
authority to perform the operation.
System Programmer Response: If appropriate, grant EWXxx3076E Incorrect data set name dsname
the proper authority to the user. specified.
Source: LANRES Explanation: An incorrect data set name was
specified in the command.
EWXxx3072E Parameter parameter must be USER System Action: Command processing ends. The
or GROUP. system status remains the same.
Explanation: The command syntax requires that the User Response: Correct the data set name and
indicated parameter be either the keyword USER or the reenter the command.
keyword GROUP.

command. EWXxx3077E Incorrect date value date specified.
System Programmer Response: None. Explanation: The date value must be in the format
defined for your system, and be a date that NetWare
Source: LANRES accepts.
The following restrictions on the year also applies. The
EWXxx3073E The full name entered is more than year must be in the range 81 to 99 (1981 to 1999) or in
127 characters. the range 00 to 80 (2000 to 2080).
Explanation: The full name must be less than or System Action: Command processing ends. The
equal to 127 characters in length. system status remains the same.
System Action: Command processing ends. The User Response: Correct the date and reenter the
system status remains the same. command.
User Response: Correct the error and reenter the System Programmer Response: None.
command.
Source: LANRES
Source: LANRES EWXxx3078E Cannot assign or remove security
equivalence from same user.
EWXxx3074I Information Explanation: A user cannot have security equivalence
to himself. Therefore, you cannot make a user security
Explanation: This is a message used to display
equivalent to himself and you cannot make a user not
information requested by the user.
security equivalent to himself.
User Response: None. system status remains the same.

User Response: Verify the two user names in the
EWXxx3082E Cannot remove a non-empty
command. If the user names are incorrect, correct them
directory.
Explanation: A directory which contains files or
subdirectories cannot be deleted.
Source: LANRES
EWXxx3079E Incorrect path name path specified.
User Response: Delete all files and subdirectories
Explanation: A NetWare path name consists of a from the directory. Reenter the command.
correct volume name. a colon, and the file or directory
name within the volume. The file or directory name is
usually optional. Source: LANRES
system status remains the same. EWXxx3083E File or directory already exists.
User Response: Correct the path name and reenter Explanation: The file or directory already exists and
the command. cannot be overwritten.
Source: LANRES
User Response: Reenter the command with a
different file or directory name.
EWXxx3080E File or directory is read-only.
Explanation: The command was unsuccessful
because it attempted to write to, copy to, rename, or Source: LANRES
delete a read-only file or directory.
System Action: Command processing ends. The EWXxx3084E Incorrect directory name specified.
Explanation: The command to create a directory
User Response: Change the file or directory’s failed. The volume was not mounted, the directory name
read-only attribute and reenter the command. The file or was misspelled, part of the directory path does not
directory’s attributes may be changed with a NetWare exist, or incomplete identification was provided.
utility, such as FLAG or FLAGDIR.
Source: LANRES User Response: Reenter the command with a correct
directory name.
EWXxx3081E File or directory not found. System Programmer Response: None.
Explanation: The specified file or directory was not Source: LANRES
found. The file or directory does not reside on the
volume, the volume was not mounted, the file or
EWXxx3085E The DS option is not supported on a
directory name was misspelled, or incomplete
NetWare Version 3.x server.
identification was provided.
Explanation: You are logged-in to a NetWare Version
3.x server and you specified the DS (Directory Services)
option on the EWXADMIN ADDLS command. The DS
User Response: Verify that the file or directory name option is accepted only when you are logged-in to a
was spelled correctly, and that the volume was NetWare Version 4.01 or later server.
mounted.
Source: LANRES User Response: Change the operating system
parameter to DOS or OS2 and reenter the command.
Source: LANRES

Source: LANRES
EWXxx3086E Cannot find Directory Services
functions on the NetWare server.
EWXxx3089I You are logged on tree . . . . . . . . .
Explanation: The command requires Directory
tree_name
Services functions on the NetWare server in order to
perform its task, but these functions are not available. Explanation: This is the NetWare Directory Services
There are several probable causes for this problem: 1) tree name that you are logged in to.
you are logged-in to a NetWare Version 3.x server; 2)
you are logged-in to a NetWare Version 4.x server but System Action: None.
the administration NLM, EWXADMIN.NLM, is running on User Response: None.
a NetWare Version 3.x server; or 3) the NetWare
DSAPI.NLM is not loaded on the server. Directory System Programmer Response: None.
Services functions are only available when NetWare’s Source: LANRES
DSAPI.NLM is loaded on the server.
System Action: Command processing ends. The EWXxx3090I Your current context . . . . . . . . . .
system status remains the same. context_name
User Response: Make sure you are connected to and Explanation: This is the current context the user is
logged-in to a NetWare Version 4.x server. If you are logged into the NetWare Directory Services.
running on a NetWare Version 4.x server, ask your
system programmer to load DSAPI.NLM on the server. System Action: None.
System Programmer Response: Load DSAPI.NLM User Response: None.

on the server. System Programmer Response: None.
EWXxx3087E Cannot login with Directory Services. EWXxx3091I You have logged-in under context
Explanation: The administration function attempted to context as user user.
login with your user ID through Directory Services to Explanation: You are now logged-in as user user on
use Directory Services functions but the attempt failed. the NetWare server under context.
The problem is probably caused by using the
SUPERVISOR user ID on a NetWare Version 4.x System Action: None.
server.
Source: LANRES
User Response: Use the ADMIN user ID or a user ID
security equivalent to the ADMIN user ID. You may also
create a SUPERVISOR user ID with NETADMIN or EWXxx3092E Invalid syntax. Check the syntax in
NWADMIN and make it security equivalent to the context field.
ADMIN user ID.
Explanation: An invalid syntax was entered - most
System Programmer Response: None. likely the context field is entered wrong.
EWXxx3088E EWXADMIN PROGRAM CANNOT BE User Response: Check the syntax and reenter.
FOUND.
Explanation: You have invoked the EWXADMIN
Source: LANRES
REXX procedure which is provided only for compatibility
with previous releases. The procedure tried to call the
main EWXADMIN program but the program was not EWXxx3093E Object objname not found.
found.
Explanation: The specified object was not found.
System Action: Command processing ends. The Either the object does not reside in the context
system status remains the same. specified, the object name was misspelled or incomplete
identification was provided to cause the appropriate
User Response: Make sure you have access to the
path to be searched.
EWXADMIN program.

system status remains the same. but neither the user configuration file nor the system
configuration file can be found. Without these files, the
User Response: To verify the object exists, enter the
connection to the NetWare server cannot be
command with correct name or syntax.
established. The user configuration file is:
System Programmer Response: None. v EWXCONFG.LINKUSER
Source: LANRES The system configuration file is:
v EWXCONFG.LINK
EWXxx3094E Login unsuccessful: User tried to System Action: Command processing ends. The
login to NDS. system status remains the same.
Explanation: The file server or user ID specified on User Response: Notify your system programmer if
the command tried to login to NetWare Directory you need access to the system configuration file or you
Services. NetWare Directory services not installed. may create your own user configuration file. You may
also connect to the NetWare server by specifying all the
System Action: Command processing ends. The required values on the command line.
System Programmer Response: Verify that the user
User Response: Use the proper syntax to login. has access to the system configuration file that was
Reenter the command. customized during installation.
Source: LANRES
EWXxx4002E Parameter parameter not in the form
EWXxx3095E Not logged in to NDS. Reenter the ″server/user″ or NDS format.
command with correct syntax. Explanation: The indicated parameter is not correct. It
Explanation: The syntax used in the command is for must be in the form server/user to specify the NetWare
NetWare Directory Services. Use the non-NDS syntax server and user ID to login to. In case logging in to
for the command. NDS, use NDS format of the parameter.
User Response: Use the proper syntax of the User Response: Correct the error and reenter the
command Reenter the command. command.
EWXxx3096E The two context names context1 and EWXxx4003E Login was unsuccessful (server error
context2 must be the same. code=nn).
Explanation: The attempt to rename/swap the Explanation: An unexpected error has occurred while
directory or file was unsuccessful, because the trying to login to the NetWare server.
files/directory to be renamed must reside in the same System Action: Command processing ends. The
context. system status remains the same.
System Action: Command processing ends. The User Response: Call your system programmer with
system status remains the same. the server error code.
User Response: Enter the same context name for System Programmer Response: Look up the server
both directories or files and reenter the command. error code nn in the NetWare System Messages book.
System Programmer Response: None. Correct the problem which caused the server error
code.
Source: LANRES
Source: LANRES
EWXxx4001E Cannot find user or system

configuration file to establish EWXxx4004I Logging of LANRES messages is on.
connection. Explanation: Messages from LANRES programs will
Explanation: Not all the required values were be recorded in a log file.
specified on the command line. The command tried to System Action: None.
use the configuration files to fill in the missing values

User Response: None. v EWXCOMM.INI file
v EWXxxxx.NPW file
v Specified by the PWIN and PWOUT parameters
Source: LANRES when the NLMs were loaded
You may have to ask the system programmer for the
EWXxx4005I Logging of LANRES messages is off. NetWare server passwords.
Explanation: Messages from LANRES programs will System Programmer Response: Give the user the
not be recorded in a log file. NetWare server passwords for the function to be
connected to.
Source: LANRES
System Programmer Response: None. EWXxx4009E Connection to the NetWare server
Source: LANRES will be dropped.
Explanation: An error has occurred which caused the
EWXxx4006E Command request to the host-to-LAN connection to the NetWare server to be dropped.
print function is too long. Additional error messages may be displayed to help
determine the problem.
Explanation: The request from the EWXCONN PRINT
or EWXCONN QUERY PRINT command cannot be sent System Action: Command processing ends. The
to the host-to-LAN print server on the host. The connection to the NetWare server is dropped.
command that was entered is longer than the maximum User Response: If additional error messages are
length for a valid EWXCONN PRINT or EWXCONN available, use them to determine the problem. Correct
QUERY PRINT command. the problem and reenter the command.
Source: LANRES
User Response: Check the command for misspellings
or duplicate values. Correct the error and reenter the
command. EWXxx4010E Cannot connect to the function
function on the NetWare server.
Explanation: No connection can be made to the
Source: LANRES function function on the NetWare server. Probable
causes are:
EWXxx4007E Cannot connect to the function v You specified an incorrect or unavailable connectivity
function. Password exchange was path
unsuccessful. v You specified an incorrect server name or user name
Explanation: The LANRES functions on the host and for the administration or distribution function and a
the NetWare server perform a password exchange to matching line cannot be found in the configuration
verify that both sides are authorized to connect to each files.
other. This password exchange was unsuccessful. The Other error messages may be displayed to indicate the
error indicates that the PWIN password value on the cause of the problem.
host does not match the PWOUT password value on
the NetWare server. System Action: Command processing ends. The
system status remains the same. User Response: If other error messages were
displayed, use them to find and correct the problem. If
User Response: Make sure that you are using the possible, specify all the parameters and options
correct passwords. On the host, the passwords may be required by the command so the command will not have
found in one of the following places (xxxx may be to use the configuration files.
ADMIN, DISK, DIST, HLPRT, or LHPRT):
v EWXxxxx.MVSPW file System Programmer Response: None.
v Specified by the PWIN and PWOUT options on the Source: LANRES

EWXCONN LINK command
On the NetWare server, the passwords may be found in
one of the following places (xxxx may be ADMIN, DISK,
DIST, HLPRT, or LHPRT):

EWXxx4011E Cannot connect to the NetWare EWXxx4015E No matching line in configuration
server with the nickname nickname. data sets to establish connection.
Explanation: No connection can be made to the Explanation: All the required values were not
NetWare server with the specified nickname. Probable specified on the command line. The command tried to
causes are: use the configuration data sets to fill in the missing
v You specified an incorrect or unavailable connectivity values but cannot find a matching line in the
path configuration data sets. For the administration and
distribution functions, the command tried to match the
v You specified an incorrect server name or user name
nickname, server name, user name, protocol, and target
for the administration or distribution function and a
values. For the disk, host-to-LAN print, and LAN-to-host
matching line cannot be found in the configuration
print functions, the command tried to match the
files
nickname, protocol, and target values. Without these
v You specified an incorrect nickname and a matching missing values, the connection to the NetWare server
line cannot be found in the configuration files cannot be established. The possible configuration data
Other error messages may be displayed to indicate sets are the data sets allocated to the EWXCONFG
what the problem was. DDname, the EWXCONFG.LINK data set, and the data
set defined by the Link_Connection_Configuration
System Action: Command processing ends. The option of the host configuration options data set.
User Response: If other error messages were system status remains the same.
displayed, use them to find and correct the problem. If
possible, specify all the parameters and options User Response: Notify your system programmer if
required by the command so the command will not have you need access to the system configuration data set.
to use the configuration files. You may create your own configuration data set. You
may also connect to the NetWare server by specifying
System Programmer Response: None. all the required values on the command line.
Source: LANRES System Programmer Response: Verify that the user
has access to the configuration data set that was
customized during installation.
EWXxx4012I Connection established to the function
function on the NetWare server. Source: LANRES
Explanation: You are now connected to the function
function on the NetWare server. EWXxx4016E Login unsuccessful: Unknown file
server or user ID.
System Action: Connection made to the NetWare
server. Explanation: The file server or user ID specified on
the command was incorrect or nonexistent.
Source: LANRES
User Response: Check the spelling of the file server
name and user ID. If the spelling is incorrect, correct it.
EWXxx4013E Cannot read login password. Error Reenter the command.
returned was: error_text
Explanation: The user was prompted to type in a
Source: LANRES
password to login to the NetWare server but an error
occurred while getting this password. The explanation
for the error, error_text, was returned in the message. EWXxx4017E Login unsuccessful: Access to
server denied.
system status remains the same. Explanation: The most probable causes for getting
this message are:
error_text. Reenter the command. v The supplied password was incorrect.
v The user account has been locked out of the server
by the NetWare “Intruder Detection/Lockout” feature.
Source: LANRES v The user tried to login when they were not allowed
access to the server.

v The administrator has disabled logins by entering the Source: LANRES
DISABLE LOGIN command at the server console.
System Action: Command processing ends. The EWXxx4022E The raddr operand must be the EVEN
system status remains the same. address of the subchannel pair.
User Response: Reenter the command with the Explanation: When using the CHANNEL or MMC
correct user ID and password. If the error persists, ask protocol, the radder operand on the EWXCONN LINK
your system programmer to grant you access to the command was incorrectly specified. (It must be a three-
server. or four-character hexadecimal number specifying the
even subchannel address of a read/write address pair.)
System Programmer Response: Use the NetWare
SYSCON utility or another utility to unlock the user ID or System Action: Command processing ends. The
to grant the user access to the server during the system status remains the same.
required time period. Enter the ENABLE LOGIN command
User Response: Reenter the EWXCONN LINK
on the server console to allow users to login to the
command with the correct subchannel address.
server.
Source: LANRES
Source: LANRES
EWXxx4018I You have logged-in to server server as
user user. EWXxx4024E Login unsuccessful: Maximum
number of concurrent connections
Explanation: You are now logged-in as user user on
exceeded.
the NetWare server server.
Explanation: NetWare has placed a restriction on the
number of stations that the user may login to at one
User Response: None. time. The login attempt exceeded this number.
Source: LANRES
User Response: Logout of another station before
reentering the command to login to the server. You can
EWXxx4020E Symdestname symdestname is not a
also ask your system programmer to raise the maximum
valid symbolic destination name.
number of concurrent connections for your user ID.
Explanation: When using the APPC protocol, the
System Programmer Response: Increase the
target operand specified an incorrect symbolic
maximum number of concurrent connections for the
destination name. It must be an alphanumeric string of
user.
up to 8 characters.
Source: LANRES
EWXxx4025E Login unsuccessful: User account
has expired or been disabled.
command.
Explanation: The user’s account on the server is
either expired or disabled.
Source: LANRES
EWXxx4021E Raddr raddr is not a valid real
User Response: Ask your system programmer to
subchannel address.
enable your user account on the server and change
Explanation: When using the CHANNEL or MMC your account expiration date. Reenter the command to
protocol, the radder operand on the EWXCONN LINK login to the server.
command was incorrectly specified. (It must be a three-
System Programmer Response: Remove the user
or four-character hexadecimal number specifying the
ID’s account disabled restriction and change his account
even subchannel address of a read/write address pair.)
expiration date on the server.
Source: LANRES
User Response: Reenter the EWXCONN LINK
command with the correct subchannel address.

EWXxx4026E Login unsuccessful: Password has EWXxx4033W Line number of configuration file
expired. filename is too long.
Explanation: The user ID’s password on the server Explanation: The line indicated in the message is too
has expired. long.
System Action: Command processing ends. The System Action: The line in error is bypassed.
User Response: Edit the configuration file and correct
User Response: Ask your system programmer to the specified line. You may have to notify the system
change your user ID’s password, if required, and programmer if the incorrect line is in the system
password expiration date. You may also login to the configuration file and you do not have write access to
server from a PC client and change your password the system configuration file:
when prompted for a new one. Reenter the command to v EWXCONFG.LINK
login to the server. Supply the new password if it has
System Programmer Response: Correct the system
been changed.
configuration file if necessary.
System Programmer Response: Change the user
Source: LANRES
ID’s password and password expiration date on the
server, if required.
EWXxx4035E Hostname hostname is not a valid
Source: LANRES
host name.
Explanation: When using the TCP/IP protocol, the
EWXxx4027E Login unsuccessful: Grace login limit
hostname operand was incorrectly specified. (It must be
exceeded.
specified as a character string of up to 63 characters.)
Explanation: The user ID’s password has expired and
the login attempt exceeded the number of grace logins
permitted.
User Response: Correct and reenter the EWXCONN
LINK command.
User Response: Ask your system programmer to
change your user ID’s password and password Source: LANRES
expiration date, if required. Reenter the command to
login to the server. Supply the new password if it has
been changed. EWXxx4036W Dropping previous connection
before trying new connection.
System Programmer Response: Change the user
ID’s password and password expiration date on the Explanation: You tried to establish a connection to a
server, if required. LANRES function on the NetWare server when there is
already a connection to the NetWare server. There can
Source: LANRES be only one LANRES connection at a time so your
previous connection will be dropped before a new
connection is attempted.
EWXxx4032W Line number of configuration file
filename has an incorrect format. System Action: The previous connection to the
NetWare server will be dropped.
Explanation: The line indicated in the message is in
an incorrect format. Values may be missing or specified User Response: None.
out of order.
System Action: The line in error is bypassed.
Source: LANRES
User Response: Edit the configuration file and correct
the specified line. Follow the formats listed in OS/390
LANRES Configuration Files and Commands. You may EWXxx4041E Incorrect component password
have to notify the system programmer if the incorrect password specified.
line is in the system configuration file and you do not Explanation: A component password must be
have write access to the system configuration file: between 1 and 8 characters long, and be an
v EWXCONFG.LINK alphanumeric string (0-9, a-z, A-Z). The password is not
System Programmer Response: Correct the system case sensitive.
configuration file if necessary. System Action: Command processing ends. The

User Response: Correct the error and reenter the System Programmer Response: None.
command.
Source: LANRES
Source: LANRES EWXxx4046I Dropping protocol connection through
server to function function.
EWXxx4043E Component password file filename Explanation: Your connection to the specified function
cannot be found. is being dropped.
Explanation: The component password file contains System Action: The connection to the NetWare server
the two component passwords required to authorize the is dropped.
connection between the host and the NetWare server.
The command was unsuccessful because these
passwords were not specified with the command and a System Programmer Response: None.
file containing these passwords cannot be found.
Source: LANRES
EWXxx4049E Error dropping the connection. Error
User Response: You may specify these component returned was: error_text
passwords when you enter the command or you may
create a default component password file to hold these Explanation: An error occurred while trying to drop
passwords. your connection. The explanation for the error,
error_text, was returned in the message.
The default password file should be created as
EWXADMIN.MVSPW, EWXDISK.MVSPW, System Action: Command processing ends. The
EWXDIST.MVSPW, EWXHLPRT.MVSPW, or system status remains the same.
EWXLHPRT.MVSPW. User Response: Correct the problem indicated:
Notify your system programmer if you do not know what error_text. Reenter the command. If the problem
these component passwords are. persists, notify your system programmer.
System Programmer Response: Find out what the System Programmer Response: Unload the
component passwords are and inform the user. LANRES NLMs from the NetWare server and load them
again. If the problem persists, contact your IBM service
Source: LANRES representative.
Source: LANRES
EWXxx4044E The PWIN and PWOUT values must
be specified as a pair.
EWXxx4054I protocol connection through server
Explanation: If the PWIN and PWOUT component established to function function.
passwords are to be specified on the command line,
then they must be specified together or not at all. Explanation: Your connection to the NetWare server
has been established.
system status remains the same. System Action: None.
User Response: Correct the error and reenter the User Response: None.
command. System Programmer Response: None.
Source: LANRES
EWXxx4059E Cannot connect to the function
EWXxx4045E No connection to drop. You were not function. Error returned was: error_text
connected to the server. Explanation: An error occurred while trying to connect
Explanation: You were not connected to a LANRES to the function function on the NetWare server. The
function on the NetWare server so there was no explanation for the error, error_text, was returned in the
connection to drop. message.
User Response: None. You are no longer connected User Response: Correct the problem indicated by
to a LANRES function on the NetWare server. error_text. If error_text is NLM NOT LOADED, load the
NLM. If the NLM is LOADED, reenter the command. If

the problem persists, notify your system programmer. User Response: Correct the component password file
System Programmer Response: If necessary, load
additional LANRES NLMs on the server. If the problem System Programmer Response: None.
persists, unload the LANRES NLMs from the NetWare
Source: LANRES
server and load them again. If the problem still persists,
contact your IBM service representative.
EWXxx4064I Information
Source: LANRES
Explanation: This is a message used to display
information requested by the user.
EWXxx4060I Attempted protocol connection through
target. System Action: None.
Explanation: A connection was attempted through the User Response: None.
indicated protocol and target but the attempt failed.
System Action: Command continues with next
connection attempt. Source: LANRES

EWXxx4065W Lines in file filename may have been
System Programmer Response: None. truncated.
Source: LANRES Explanation: The program tried to write information to
the host file filename, but the record length of the file
was not long enough and lines in the file may have
EWXxx4061E Line number of component password
been truncated.
file filename is too long.
Explanation: The line indicated in the message is
longer than 128 characters. Correct lines should not User Response: Set up a file with the correct record
require more than 128 characters. length and reenter the command.
Source: LANRES
User Response: Edit the component password file
and correct the specified line.
EWXxx4066E The command specified in the CMD
System Programmer Response: None. option is too long.
Source: LANRES Explanation: The host command string specified
between the CMD option delimiters cannot be longer
than the maximum length of 255 characters. The CMD
EWXxx4062E Incorrect password in line number of
option must also be the last option on the command
component password file filename.
line.
Explanation: A component password must be
between 1 and 8 characters long, and be an
alphanumeric string (from 0 to 9, a to z, and A to Z).
The password is not case sensitive. User Response: If possible, shorten the command
specified between the CMD option delimiters. If not, put
the lengthy command in a REXX procedure and then
specify the name of the REXX procedure for the CMD
User Response: Correct the component password file option value.
Source: LANRES
Source: LANRES
EWXxx4067E CMD command ″command″ was
EWXxx4063E One or both component passwords unsuccessful. Resulting return code is
cannot be found in filename. return-code.
Explanation: Both component passwords are required Explanation: The command specified as the CMD
to connect the host to a NetWare function. option value was unsuccessful.
System Action: Command processing ends. The System Action: Connection is established with the
system status remains the same. NetWare server but the command failed.

User Response: Check the resulting return code
EWXxx4205E Error closing disk image
found in the message to determine why the command
was unsuccessful.
Explanation: An attempt to close the indicated disk
image was unsuccessful.
Source: LANRES
User Response: Correct the problem and retry the
EWXxx4201E Error opening disk image
failing command.
Explanation: An attempt to open the indicated disk
image was unsuccessful. Source: LANRES
EWXxx4206I Building compression dictionary for
disk image disk_image_name.
failing command.
Explanation: LANRES is building the data
compression dictionary for the indicated disk image
Source: LANRES dataset.
EWXxx4202E Error reading disk image
Explanation: An attempt to read the indicated disk
EWXxx4207I Compression dictionary built for disk
image disk_image_name.
failing command.
Explanation: LANRES has finished building the data
compression dictionary for the indicated disk image
Source: LANRES dataset.
EWXxx4203E Error writing disk image
Explanation: An attempt to write the indicated disk
EWXxx4208I Disk image statistics for dsname.
failing command. Explanation: This is the VSAM linear dataset name.
System Programmer Response: None. System Action: None.
EWXxx4204E Unable to commit disk image
Source: LANRES
Explanation: An attempt to commit the indicated disk
EWXxx4209I NetWare volume size is nwsizeK, actual
image was unsuccessful.
volume size is ldsizeK.
Explanation: The NetWare volume size is the size of
User Response: Correct the problem and retry the the volume reported to the NetWare server while the
failing command. actual volume size is the size of the VSAM linear
dataset. The actual size is the same as the NetWare
volume size for an uncompressed disk image.
Source: LANRES

EWXxx4213E DIV request for dsname failed with
Source: LANRES error error, reason code reason-code.
Explanation: A data-in-virtual request for the indicated
EWXxx4210I sizeK is being used by blocks disk VSAM linear dataspace failed with the indicated error
blocks, compression ratio is ratio%. and reason codes. See OS/390 MVS Programming:
Assembler Services Reference for a description of the
Explanation: Each NetWare disk block is 512 bytes. DIV error codes.
When disk compression is enabled, LANRES will
compress each group of 8 disk blocks before writing the System Action: Command processing ends.
data to the VSAM linear dataset. The compression ratio
User Response: Correct the problem and then retry
is the ratio between the number of bytes actually written
the failing command.
to the VSAM dataset and the number of bytes written by
the NetWare server. System Programmer Response: None.
System Action: None. Source: LANRES
EWXxx4214E DSPSERV request for dsname failed
with error error, reason code
Source: LANRES reason-code.
Explanation: A dataspace request for the indicated
EWXxx4211I usedK in use, unusedK not in use, VSAM linear dataspace failed with the indicated error
unallocatedK not allocated. and reason codes. See OS/390 MVS Programming:
Assembler Services Reference for a description of the
Explanation: Space in the VSAM linear dataset is DIV error codes.
either in use by a NetWare disk block, allocated but not
in use, or not allocated. Initially, all space in the dataset System Action: Command processing ends.
is unallocated. As the NetWare server writes to the disk
User Response: Correct the problem and then retry
volume, space will be allocated to handle the changed
the failing command.
disk blocks. As the disk blocks change in size due to
different compression ratios, the old disk block space System Programmer Response: None.
will be placed in a pool of unused space to be re-used
Source: LANRES
by future space allocations. Disk fragmentation
increases as the unallocated space decreases and the
unused space increases. You should use the EWXxx4215E Data compression support is not
EWXLDCMP and EWXLDRST commands to rebuild the available.
VSAM linear dataset when the unallocated space
becomes zero. Explanation: Data compression is not available on the
current system. The EWXLDDMP and EWXLDRST
System Action: None. commands use data compression services in order to
process the dump dataset. This error can occur if the
EWXLDRST command is issued on a system without
System Programmer Response: None. ZIV data compression support to restore a dataset
created by the EWXLDDMP command on a system with
Source: LANRES
ZIV data compression support.
EWXxx4212E Linear dataspace dsname has not
been initialized. User Response: Use the EWXLDDMP command with
the RLE option to create the dump dataset using RLE
Explanation: The indicated VSAM linear dataspace
data compression instead of ZIV data compression.
has not been initialized for use with LANRES.
Source: LANRES
User Response: Use the EWXLDCRT command to
initialize the dataspace and then retry the failing
command. EWXxx4216E Error opening the EWXDUMP
dataset: error_text.
Explanation: LANRES was unable to open the dump
Source: LANRES
dataset defined by the EWXDUMP DD statement.

EWXxx4221E Unable to build compression
failing command.
dictionary: error.
Explanation: LANRES was unable to build the
Source: LANRES compression dictionary for the indicated reason.
EWXxx4217E Error reading from the EWXDUMP
failing command.
Explanation: LANRES was unable to read from the
dump dataset defined by the EWXDUMP DD statement.
Source: LANRES
EWXxx4222I countK bytes written to dump dataset
failing command.
for disk image dsname.
Explanation: The dump dataset was successfully
Source: LANRES created for the indicated LANRES host disk image.
EWXxx4218E Error writing to the EWXDUMP
Explanation: LANRES was unable to write to the
dump dataset defined by the EWXDUMP DD statement. Source: LANRES
EWXxx4223E The EWXDUMP dataset was not
created by the EWXLDDMP command.
failing command.
Explanation: The dataset specified by the EWXDUMP
DD statement does not contain a valid LANRES disk
Source: LANRES image dump.
EWXxx4219E Error closing the EWXDUMP dataset:
User Response: Use the EWXLDDMP command to
error_text.
create the dump dataset.
Explanation: LANRES was unable to close the dump
dataset defined by the EWXDUMP DD statement.
Source: LANRES
EWXxx4224I Dumping disk image dsname.
failing command.
Explanation: The data for the indicated disk image is
being written to the EWXDUMP dataset.
Source: LANRES
EWXxx4220E The EWXDUMP dataset does not
have variable-length 4100-byte records. System Programmer Response: None.
Explanation: The EWXDUMP dataset used by the Source: LANRES
EWXLDDMP and EWXLDRST commands must have
RECFM=VB and LRECL=4100. The BLKSIZE can be
EWXxx4225E Disk image dsname must be sizeK in
any value which is supported by the device.
order to restore disk image.
Explanation: The disk image dataset for the
User Response: Correct the problem and retry the EWXLDRST command must be the same size as the
failing command. disk image dataset which was dumped using the
EWXLDDMP command when data compression is not
being used.
Source: LANRES

User Response: Allocate a new disk image dataset System Programmer Response: None.
with the required size.
Source: LANRES
Source: LANRES EWXxx4251E Dataset disk_image_name already
exists.
EWXxx4226I Restoring disk image dsname. Explanation: The VSAM linear dataspace dataset
already exists.
Explanation: The indicated disk image is being
restored from the EWXDUMP dataset. System Action: Command processing ends.
System Action: None. User Response: Issue the EWXLDDLT command to
delete the current disk image dataset and then retry the
EWXLDCRT command.
Source: LANRES
Source: LANRES
EWXxx4227I Disk image dsname restored.

EWXxx4253E The disk image size of size is less
Explanation: The indicated disk image has been than the minimum size of 2 megabytes.
restored from the EWXDUMP dataset.
Explanation: The size specified for a new LANRES
System Action: None. disk image was less than 2 megabytes.
User Response: None. System Action: Command processing ends.
System Programmer Response: None. User Response: Specify a disk image size of at least
2 megabytes.
Source: LANRES
EWXxx4228E Insufficient storage available to Source: LANRES

allocate work buffers.
Explanation: LANRES was unable to allocate its EWXxx4254E The disk image size of size is greater
internal work buffers. than the maximum size of 4 gigabytes.
System Action: Command processing ends. Explanation: The size specified for a new LANRES
disk image is greater than 4 gigabytes.
User Response: Increase the region size and retry
the failing command. System Action: Command processing ends.
System Programmer Response: None. User Response: Specify a disk image size no greater
than 4 gigabytes.
Source: LANRES
EWXxx4229W Disk image page page has been Source: LANRES

discarded due to a damaged disk
image dataset.
EWXxx4255E Volume volume is not available.
Explanation: The VSAM dataset containing the host
Explanation: LANRES is unable to create a disk
disk image has been damaged. This can occur if the
image dataset because the indicated volume is not
LANRES disk server is abnormally terminated while it is
available. A volume serial of ’******’ will be displayed if
updating the VSAM dataset. All disk blocks in the
the volume information is being obtained from the
damaged image page will be discarded and the page
system catalog.
contents will be set to zero.
System Action: The dump operation continues.
User Response: Specify a valid volume serial on the
User Response: Run the EWXLDRST command to
EWXLDCRT command if you are creating a new VSAM
restore the VSAM dataset from an earlier dump file or
dataset. Ensure that the system catalog entry contains
from the current dump file. If you restore the VSAM
the correct volume serial if you are using an existing
dataset from the current dump file, you should run
VSAM dataset.
VREPAIR on the NetWare server to correct any disk
structure problems. You may also need to recreate one System Programmer Response: None.
or more of the NetWare disk files.

Source: LANRES
EWXxx4263I disk_image_name was created for
number_of_blocks blocks.
EWXxx4256E The NetWare volume segment size
Explanation: The LANRES disk image has been
specified by the COMPRESS option is
successfully created. There are 512 bytes per disk
invalid.
image block.
Explanation: The NetWare volume segment size must
System Action: The command ends successfully.
be greater than the VSAM linear dataspace size but not
greater than 4 gigabytes. User Response: None.
System Action: Command processing ends. System Programmer Response: None.
User Response: Specify a valid NetWare volume Source: LANRES
segment size.
System Programmer Response: None. EWXxx4264E Unable to delete disk image
Source: LANRES
Explanation: LANRES was unable to delete the
specified disk image.
EWXxx4257E A volume must be specified when
SMS is not active. System Action: Command processing ends.
Explanation: A volume serial must be specified on the User Response: Correct the problem and retry the
EWXLDCRT command in order to create a new disk command.
image dataset when System Managed Storage is not
active.
Source: LANRES
User Response: Specify a volume serial on the
EWXxx4266E The disk image size parameter is
EWXLDCRT command.
invalid.
Explanation: An invalid disk image size was specified.
Source: LANRES The minimum disk image size is 2 megabytes and the
maximum disk image size is 4 gigabytes.
EWXxx4258I disk_image_name has been deleted. System Action: Command processing ends.
Explanation: The LANRES disk image has been User Response: Specify a valid LANRES disk image
successfully deleted. size.
System Action: The command ends successfully. System Programmer Response: None.
EWXxx5001S Unable to create TCP/IP socket: Error
Source: LANRES
error.
Explanation: LANRES was unable to create a TCP/IP
EWXxx4261E Unable to create disk_image_name for
socket. The error code is the value returned for the
number_of_blocks blocks: error_text.
TCP/IP socket() function. See the OS/390 SecureWay
Explanation: LANRES was unable to create the Communications Server: IP Programmer’s Reference for
specified disk image. a description of the error codes.
System Action: Command processing ends. System Action: Command processing ends.
User Response: Correct the problem and retry the User Response: Report the problem to the system
command. programmer.
System Programmer Response: None. System Programmer Response: Report the problem
to IBM.
Source: LANRES
Source: LANRES

EWXxx5002S TCP/IP socket number is too large. EWXxx5006E TCP/IP send() function failed with
error error.
Explanation: The socket number returned by the
TCP/IP socket() function is too large. LANRES supports Explanation: The TCP/IP send() function failed with
a maximum of 32 TCP/IP connections per LANRES the indicated error code. See the OS/390 SecureWay
command. Communications Server: IP Programmer’s Reference for
a description of the error codes.
User Response: Report the problem to the system
programmer. User Response: Report the problem to the system
programmer.
System Programmer Response: Report the problem
to IBM. System Programmer Response: None.
EWXxx5003E TCP/IP select() function failed with EWXxx5007E Incorrect protocol name specified.
error error.
Explanation: An incorrect or unsupported protocol
Explanation: The TCP/IP select() function failed with was specified.
the indicated error code. See the OS/390 SecureWay
Communications Server: IP Programmer’s Reference for
a description of the error codes. User Response: Specify a valid communications
protocol.
programmer. Source: LANRES
EWXxx5008E Incorrect destination name specified.
Source: LANRES
Explanation: An incorrect destination name was
specified. For a channel connection, the destination is
EWXxx5004E TCP/IP connect() function failed with
the even subchannel address assigned to the NetWare
error error.
server. For an APPC connection, the destination is
Explanation: The TCP/IP connect() function failed with either the symbolic destination name or the
the indicated error code. See the OS/390 SecureWay fully-qualified partner LU name. For a TCP/IP
Communications Server: IP Programmer’s Reference for connection, the destination is the host name assigned
a description of the error codes. to the NetWare server.
System Action: Command processing ends. System Action: Command processing ends.
User Response: Report the problem to the system User Response: Specify a valid destination.
programmer.
Source: LANRES
Source: LANRES
EWXxx5009E Service distribution rejected by
EWXxx5005E TCP/IP recv() function failed with server server.
error error.
Explanation: The service distribution request was
Explanation: The TCP/IP recv() function failed with rejected by the target NetWare server because the
the indicated error code. See the OS/390 SecureWay distribution service level is less than or equal to the
Communications Server: IP Programmer’s Reference for current service level installed on the server. You can
a description of the error codes. force the service to be distributed by re-issuing the
command and specifying that service level checking is
to be bypassed.
programmer.
User Response: Retry the command.
Source: LANRES
Source: LANRES

more information on the channel and device status
EWXxx5010E Service distribution to destination
codes.
destination failed.
Source: LANRES
Explanation: The LANRES service distribution
controller was unable to send the current service level
to the NetWare server at the indicated destination. For EWXxx5014E Device address has been halted.
an APPC connection, the destination name is either the
symbolic destination name or the fully-qualified partner Explanation: One of the LANRES channel device
LU name. For a TCP/IP connection, the destination addresses was halted by the operating system. This can
name is the server host name. For a channel occur if the missing interrupt handler determines that
connection, the destination name is the channel device the channel device is not responding to I/O requests or
address assigned to the server. if the NetWare NLM is unloaded after a connection has
been established.
System Action: The current service level is not sent.
User Response: Correct the cause of the error.
System Programmer Response: None. programmer.
Source: LANRES System Programmer Response: Ensure that the
NetWare server is operational and has not abnormally
terminated.
EWXxx5011E The NetWare service package file has
been modified. Source: LANRES
Explanation: The NetWare service package file has
been modified. EWXxx5015E Device address is offline.
System Action: Command processing ends. Explanation: LANRES was unable to allocate one of
the channel device addresses because the device is
User Response: Verify that you are accessing the
offline.
correct NetWare service package file. If the problem
persists, report the problem to the system programmer. System Action: Command processing ends.
System Programmer Response: Re-install the User Response: Vary the device online or use a
LANRES product. Contact IBM if the problem persists. different pair of device addresses.
Source: LANRES
EWXxx5012E Service distribution is not enabled
for destination destination.
EWXxx5016E Device address is not a supported
Explanation: The ACCEPT_SERVICE parameter in device type.
the EWXCOMM.INI control file on the NetWare server is
set to NO. Explanation: The indicated device is not supported by
LANRES.
User Response: Change the EWXCOMM.INI file to
specify ACCEPT_SERVICE=YES. User Response: Make sure that you have specified
the correct device addresses for the channel-attached
System Programmer Response: None. NetWare server. Also make sure that the correct control
unit tables are specified in the channel configuration file
Source: LANRES
on the NetWare server.
EWXxx5013E I/O error on device address: Device
status devstat, Channel status chanstat, Source: LANRES
Sense sense.
Explanation: LANRES encountered an I/O error on EWXxx5017E Device address is allocated to
one of the channel device addresses. another job.
System Action: Command processing ends. Explanation: LANRES was unable to allocate one of
the channel device addresses because the device
address is allocated to another job.
programmer.
System Programmer Response: Correct the error
condition. See the S/390 Principles of Operation for

User Response: End the other job or use a different System Programmer Response: None.
pair of device addresses.
Source: LANRES
Source: LANRES EWXxx5301S ISPF is already active.
Explanation: The EWXISPF command must be
EWXxx5018E Device address does not exist. invoked from the TSO READY prompt. It cannot be
executed once ISPF has been started.
Explanation: The indicated device address is not
defined to the operating system. System Action: Command processing ends.
System Action: Command processing ends. User Response: Issue the EWXISPF command from
the TSO READY prompt.
programmer. System Programmer Response: None.
System Programmer Response: Ensure that the Source: LANRES
device address is correct and that the NetWare server
is online and operational.
EWXxx5302I LANRES READY
Source: LANRES
Explanation: The EWXEXEC command processor is
ready to process a new command. When running in a
EWXxx5019E Device address is not a 3088/CTCA TSO environment, any TSO command may be entered
type device. as well as the TSO, PGM, and REXX special
commands. When running in a non-TSO environment,
Explanation: The device at the specified address is
TSO commands are not supported and only the PGM
not supported by LANRES for channel attachment.
and REXX special commands may be entered.
The TSO special command tells EWXEXEC to process
User Response: Report the problem to the system the rest of the command line as a TSO command and
programmer. not to check for special commands. This is necessary if
you want to run a TSO command named PGM or
System Programmer Response: Ensure that the REXX.
device address is correct and that the NetWare server
is online and operational. The PGM special command tells EWXEXEC to process
the rest of the command line as an MVS program
Source: LANRES invocation. The first token following the PGM command
specifies the dataset name and member of the MVS
EWXxx5020E Device address is not operational. load module. The remainder of the command line will be
passed to the MVS program as the parameter string.
Explanation: The indicated device is not operational. The dataset name prefix will be added unless the
Intervention required status was reported on the I/O dataset name is enclosed in quotes. If the load module
request. is located in a STEPLIB, JOBLIB, or link list dataset,
System Action: Command processing ends. omit the dataset name and specify just the member
name enclosed in parentheses. If a dataset name is
User Response: Make sure that the NetWare server specified, it will be used as a tasklib on the ATTACH
is powered on and that the channel device driver has command.
been loaded.
The REXX special command tells EWXEXEC to
System Programmer Response: None. process the rest of the command line as a REXX
Source: LANRES procedure invocation. The first token following the
REXX command specifies the dataset name and
optional member of the REXX procedure. The
EWXxx5300S The EWXISPF command is valid only remainder of the command line will be passed to the
in the TSO environment. REXX procedure as the argument string. The dataset
name prefix will be added unless the dataset name is
Explanation: The EWXISPF command must be
enclosed in quotes. If the REXX procedure is located in
invoked as a command processor under TSO.
a SYSEXEC dataset, omit the dataset name and
System Action: Command processing ends. specify just the member name enclosed in parentheses.
User Response: Issue the EWXISPF command while System Action: EWXEXEC waits for a command. In
logged on to TSO in the foreground or when the the foreground TSO environment, commands are read
Terminal Monitor Program is active in the background. from the terminal. In the background TSO environment,
commands are read from SYSTSIN. In the batch

environment, commands are read from EWXINPUT.
EWXxx5307S Insufficient storage available.
User Response: Enter a command.
Explanation: The EWXEXEC command was unable to
System Programmer Response: None. allocate storage for work buffers.
Source: LANRES System Action: Command processing ends.

User Response: Run the EWXEXEC command in a
EWXxx5303E Unable to read from the EWXINPUT larger region.
dataset: error.
Source: LANRES
read a record from the command dataset specified by
the EWXINPUT DD statement.
EWXxx5308I command
Explanation: This message is issued by the
User Response: Correct the error and re-issue the
EWXEXEC command when it is reading commands
EWXEXEC command.
from the EWXINPUT dataset. Each command is
System Programmer Response: None. displayed before it is run.
Source: LANRES System Action: None.
EWXxx5304E Unable to get command line:
PUTGET error error.
Source: LANRES
get the next command line.
EWXxx5309E APPC is not available.
Explanation: This message is issued if the APPC
User Response: Correct the error and re-issue the
functions cannot be found in the current step library, job
EWXEXEC command. See the OS/390 TSO/E
library, or link library. APPC is available only on
Programming Services for a description of the PUTGET
MVS/ESA 4.2 and later.
error codes.
System Action: The APPC connection is not
established.
Source: LANRES
User Response: Make sure that SYS1.CSSLIB is in
the step library, job library, or link library and then retry
EWXxx5305E Command is too long. the failing request.
Explanation: The command read by EWXEXEC System Programmer Response: None.

exceeds the maximum length of 512 characters.
Source: LANRES
System Action: The command is not executed.
User Response: Enter a shorter command. EWXxx5310E APPC error error occurred on
connection to server.
Explanation: An error was detected on an APPC
Source: LANRES request. The fully-qualified partner LU name will be
included in the message if it is known at the time of the
EWXxx5306E Premature end of data while reading error. Otherwise, the symbolic destination name used to
the EWXINPUT dataset. establish the connection will be included in the
message.
Explanation: The EWXEXEC command reached the
end of the EWXINPUT dataset while constructing a System Action: The connection to the NetWare server
command to be executed. is dropped.
System Action: The command is not executed. User Response: Correct the cause of the error and
then retry the failing request.
User Response: Make sure that the last command in
the dataset does not end with a continuation character. System Programmer Response: None.
Source: LANRES

EWXxx5402E Unable to execute command: error. EWXxx6005E Print queue name is a required input
Explanation: LANRES was unable to execute a Explanation: Print queue name is a required input for
system command for the indicated reason. this command.
System Action: The request is not performed. System Action: The ISPF panel is re-displayed with
the cursor placed at the beginning of the print queue
name field.
failing command.
User Response: Enter the print queue name and retry
the command.
Source: LANRES
Source: LANRES
EWXxx6001E User ID is a required input
Explanation: The NetWare user ID is a required input
EWXxx6006E Print server name is a required input
for this command.
Explanation: Print server name is a required input for
System Action: The command is not executed, and
this command.
the ISPF panel is re-displayed with the cursor placed on
the Userid input field. System Action: The ISPF panel is re-displayed with
the cursor placed at the beginning of the print server
User Response: Type the NetWare Userid in the field
name field.
and retry the command.
User Response: Enter the print server name and retry
the command.
Source: LANRES
Source: LANRES
EWXxx6002E Group ID is a required input
Explanation: The NetWare Groupid is a required input
EWXxx6009E A user/group ID must be specified
for this command.
Explanation: A NetWare user or group ID is a
required input for this panel.
the Groupid input field. System Action: The ISPF panel is re-displayed with
the cursor placed at the beginning of the field.
User Response: Type the NetWare Groupid in the
field and retry the command. User Response: Enter the NetWare user or group ID
in the field.
Source: LANRES
Source: LANRES
EWXxx6003E Login script file name is a required
input EWXxx6015E A password expiration interval of 0 to
365 must be specified
Explanation: The name of a host data set that
contains or will contain the NetWare login script file is a Explanation: The time interval between forced
required input for this command. password changes must be a positive integer less than
365. Entering 0 means that the password will never
expire.
the login script file name input field. System Action: The ISPF panel is re-displayed with
the cursor placed at the beginning of the password
User Response: Type the NetWare login script file
expiration interval field.
name in the field and retry the command.
User Response: Re-type the password expiration
interval with a value between 0 and 365.
Source: LANRES
Source: LANRES

Source: LANRES
EWXxx6016E A password length of 1 to 20 must be
specified
EWXxx6022E Message text must be specified
Explanation: The minimum password length is a
number between 1 and 20. Explanation: No message text was specified to be
sent as a message.
System Action: The ISPF panel is re-displayed with
the cursor placed at the beginning of the password System Action: The ISPF panel is re-displayed with
length interval field. the cursor placed at the beginning of the VSAM LDS
size field.
User Response: Re-type the password length with a
value between 1 and 20. User Response: Type the message text in the
specified field.
Source: LANRES
Source: LANRES
EWXxx6017E The name of the restricted volume
must be specified EWXxx6025E A date in the form of MM/DD/YY must
be specified
Explanation: The name of the NetWare volume where
the restriction on user disk space will apply must be Explanation: Either a date was not entered, or a date
entered. was not entered in the format MM/DD/YY.
System Action: The ISPF panel is re-displayed with System Action: The ISPF panel is re-displayed with
the cursor placed at the beginning of the volume name the cursor placed at the beginning of the date field.
field.
User Response: Re-type the date in the correct
User Response: Enter the volume name in the format in the specified field.
volume name field.
Source: LANRES
Source: LANRES
EWXxx6026E A time in the form of HH:MM:SS must

EWXxx6019E A valid TSO data set name must be be specified
entered
Explanation: Either a time was not entered, or a time
Explanation: A TSO data set name is required for this was not entered in the format HH:MM:SS.
input field. A valid TSO data set name may be up to 44
characters in length and have as many as 5 levels of System Action: The ISPF panel is re-displayed with
qualification. the cursor placed at the beginning of the time field.
System Action: The ISPF panel is re-displayed with User Response: Re-type the time in the correct
the cursor placed at the beginning of the TSO data set format in the specified field.
name field. System Programmer Response: None.
User Response: Re-type the TSO data set name. Source: LANRES
Source: LANRES EWXxx6027E A valid PC path/file name must be
specified
EWXxx6021E A numeric value must be specified Explanation: The field was left blank or a valid PC
for the data set size path/file name was not entered.
Explanation: The size of the VSAM Linear Data set is System Action: The ISPF panel is re-displayed with
a required input for this panel. the cursor placed at the beginning of the PC path/file
name field.
the cursor placed at the beginning of the VSAM LDS User Response: Enter a valid PC path/file name in
size field. the specified field.
User Response: Enter a numeric value for the size of System Programmer Response: None.
the VSAM LDS in the specified field. Source: LANRES

EWXxx6028E A number between 0 and 200 must EWXxx6035E A value between 0 and 268435455
be specified for grace logins must be specified
Explanation: The number of times a user can log in Explanation: A value between 0 and 268435455 must
with an expired password is a number between 1 and be specified to complete the operation.
200. Entering 0 means that the number of grace logins
is unlimited.
the cursor placed at the beginning of the grace logins System Programmer Response: None.
field.
Source: LANRES
User Response: Enter a number between 0 and 200
in the grace logins field.
EWXxx6036I Processing Successful
Explanation: The user’s request has been
Source: LANRES successfully completed.
EWXxx6029E A number between 0 and 250 must
be specified for concurrent log ins User Response: None.
Explanation: The number of workstations a user may System Programmer Response: None.
be concurrently logged into is a number between 1 and Source: LANRES
250. Entering 0 means that the number of concurrent
logins is unlimited.
EWXxx6037E Processing Unsuccessful
the cursor placed at the beginning of the concurrent Explanation: The user’s request did not complete
logins field. successfully. Refer to the other error messages that
were displayed to determine why the request failed.
User Response: Enter a number between 0 and 200
in the concurrent logins field. System Action: None.
System Programmer Response: None. User Response: None.

Source: LANRES
EWXxx6031E A valid volume name must be
specified EWXxx6040E Password data set cannot be
Explanation: A valid volume name must be specified specified with passwords.
to complete the operation. Explanation: Cannot specify a password data set if
System Action: None. the passwords are also listed.
User Response: None. System Action: None.
System Programmer Response: None. User Response: None.

Source: LANRES
EWXxx6032E A valid device address must be
specified EWXxx6041E LANRES function not specified.
Explanation: A valid device address must be specified Explanation:
to complete the operation.
Source: LANRES
Source: LANRES

System Programmer Response: If the problem
EWXxx6042E A value between 1 and 1000000 must
persists, contact your IBM service representative.
be specified for line limit.
Source: LANRES
Explanation: The maximum number of lines allowed
in the log data set is a number from 1 to 1000000.
EWXxx6047I Initializing data with information from
sample data set
Explanation: The specified data set does not exist.
System Programmer Response: None. The table summarizing data set entries has been
initialized from the sample LANRES configuration data
Source: LANRES
set.
System Action: Entries from the sample configuration
EWXxx6043E A value between 1 and 255 must be
data set are displayed.
specified for copies.
User Response: You can add, modify, or delete
Explanation: You may make from 1 to 255 copies.
entries.
Source: LANRES
Source: LANRES EWXxx6048E Data set name is not valid
Explanation: An invalid data set name was specified.
EWXxx6044E Command not recognized
System Action: The ISPF panel is redisplayed with
Explanation: An invalid command was entered in the the cursor placed at the beginning of the data set name
prefix area. field.
System Action: The ISPF panel is redisplayed. User Response: Enter a valid data set name.
User Response: Enter an S to select an entry for System Programmer Response: None.
display and modification or a D to mark an entry for
Source: LANRES
deletion.
EWXxx6049E Member specified, but data set is not
Source: LANRES partitioned
Explanation: The data set name is conflicting because
EWXxx6045W Some exit parameter data cannot be the data set is sequential, but a member was specified.
displayed due to field constraints
Explanation: The amount of exit parameter data for the cursor placed at the beginning of the data set name
the entry exceeds the length of the parameter fields. field.
This situation can occur if long parameter values are
User Response: Enter a valid data set name.
specified because values are not wrapped across
multiple fields. System Programmer Response: None.
System Action: The exit parameter data is truncated. Source: LANRES
User Response: Data may be lost if the entry is
saved. EWXxx6050E Protected data set cannot be
accessed
Explanation: The specified data set is protected so it
Source: LANRES
cannot be accessed through this interface.
EWXxx6046S Error encountered displaying ISPF
the cursor placed at the beginning of the data set name
panel
field.
Explanation: A severe ISPF error occurred.
User Response: Enter a nonprotected data set name,
System Action: LANRES will attempt to redisplay the or get authorization for the protected data set.
previous panel.
User Response: Restart the ISPF session.

Source: LANRES
EWXxx6055E The disk image name must consist of
alphanumeric characters
EWXxx6051E Error processing requested data set
Explanation: A character other than A-Z, a-z, or 1-9
Explanation: The specified data set name could not was entered in the disk image name field.
be used successfully.
System Action: The ISPF panel is redisplayed with the cursor placed at the beginning of the disk image
the cursor placed at the beginning of the data set name name field.
field.
User Response: Retype the information in the field
User Response: Verify the data set name, and reenter using only the characters A-Z, a-z, and 1-9.
it.
Source: LANRES
Source: LANRES
EWXxx6056E The disk image name must start with
EWXxx6052E Password expected from server and an alphabetic character
reentered value do not match
Explanation: A character other than A-Z or a-z was
Explanation: The value specified for the password entered as the first character of the disk image name.
expected from the NetWare server does not match the
reentered value.
the cursor placed at the beginning of the disk image
System Action: The ISPF panel is redisplayed with name field.
the cursor placed at the beginning of the password field.
User Response: Retype the information in the field
User Response: Reenter the password expected from using only a character in A-Z and a-z for the first
the server and the verification password. character.
EWXxx6053E Password expected by server and EWXxx6057E When data space size is specified,
reentered value do not match access mode must be specified
Explanation: The value specified for the password Explanation: The access mode field was left blank,
expected by the NetWare server does not match the but a value was specified for the data space size.
reentered value. Because the configuration data set is composed of
tokens, if the data space size is specified, the preceding
System Action: The ISPF panel is redisplayed with field (access mode) must also be specified.
the cursor placed at the beginning of the password field.
User Response: Reenter the password expected by the cursor placed at the beginning of the access mode
the server and the verification password. field.
System Programmer Response: None. User Response: Enter a value for the access mode,
Source: LANRES or blank out the value in the data space size field.
EWXxx6054E The password must consist of Source: LANRES
alphanumeric characters
Explanation: A character other than A-Z, a-z, or 1-9 EWXxx6058E Data space size must be in the range
was entered in the password field. of 1 to 2048 megabytes or left blank
System Action: The ISPF panel is redisplayed with Explanation: If a data space size is specified, it must
the cursor placed at the beginning of the password field. be set to a value between 1 and 2048.
User Response: Retype the information in the field System Action: The ISPF panel is redisplayed with
using only the characters A-Z, a-z, and 1-9. the cursor placed at the beginning of the data space
System Programmer Response: None. size field.
Source: LANRES User Response: Reenter the data space size with a
value between 1 and 2048 or blank out the field.

System Programmer Response: None. BLANK, or provide a value in the PC extension field.
Source: LANRES
EWXxx6059E Access mode must be R, W, or left
blank
EWXxx6063E Data was truncated when written to
Explanation: If the access mode is specified, it must the data set
indicate Read only or Write.
Explanation: Data was lost when the entry was
System Action: The ISPF panel is redisplayed with written to the configuration data set because the data
the cursor placed at the beginning of the access mode set logical record length is smaller than the length of the
field. specified data.
User Response: Indicate an access mode value of System Action: A truncated version of the entry is
Read only or Write, or blank out the field. stored in the data set.
System Programmer Response: None. User Response: Increase the logical record length of
the data set and reenter the data, or use a different
Source: LANRES
interface to enter this data.
EWXxx6060E The translation option field must
indicate ASCII, ASCIITAB, or BINARY Source: LANRES
Explanation: The translation option field must indicate
a value of ASCII, ASCIITAB, or BINARY. EWXxx6064E Unable to allocate data set
System Action: The ISPF panel is redisplayed with Explanation: The attempt to allocate the data set so
the cursor placed at the beginning of the translation that the entry could be written to it failed. The data has
option field. not been stored in the data set.
User Response: Indicate a translation option value of System Action: The ISPF panel showing the
ASCII, ASCIITAB, or BINARY. summary of entries is redisplayed.
System Programmer Response: None. User Response: Verify that you have write authority
for the specified data set.
Source: LANRES
EWXxx6061E If type qualifier is ″BLANK″, PC Source: LANRES
extension cannot be specified
Explanation: BLANK was specified as the type EWXxx6065E The notify when printed field must be
qualifier, and a value was entered in the PC extension set to YES or NO
field.
Explanation: Either YES or NO must be selected for
System Action: The ISPF panel is redisplayed with the notify when printed field.
the cursor placed at the beginning of the PC extension
field.
the cursor placed at the beginning of the notify when
User Response: Blank out the PC extension field, or printed field.
change the type qualifier value.
User Response: Indicate YES, that the print job
System Programmer Response: None. owner should be notified when the data has been
printed, or NO, that the owner should not be notified.
Source: LANRES
EWXxx6062E If PC extension is not specified, type Source: LANRES
qualifier must be ″BLANK″
Explanation: A value was not specified for the PC EWXxx6066E The translate data field must be set
extension field, and the type qualifier was set to a value to YES or NO
other than BLANK.
System Action: The ISPF panel is redisplayed with the translate data field.
the cursor placed at the beginning of the type qualifier
field.
the cursor placed at the beginning of the translate data
User Response: Change the type qualifier value to field.

User Response: Indicate YES, that the data should
EWXxx6070E For internal exit type, exit name must
be translated from EBCDIC to ASCII, or NO, that the
be EWXLHJOB or EWXLHLNP
data should not be translated.
Explanation: An exit type of INTERNAL was specified,
but the exit name field was not set to a valid
Source: LANRES IBM-supplied exit.
EWXxx6067E The user exit type field must be set the cursor placed at the beginning of the exit name
to EXEC, INTERNAL, or PGM field.
Explanation: A value other than EXEC, INTERNAL, or User Response: Reenter a value for the exit name
PGM was entered in the user exit type field. field using EWXLHJOB or EWXLHLNP, or change the
exit type.
the cursor placed at the beginning of the user exit type System Programmer Response: None.
field.
Source: LANRES
User Response: Reenter a value for the user exit type
field using EXEC, INTERNAL, or PGM.
EWXxx6071E The function field must be set to
System Programmer Response: None. DISK, HLPRT, or LHPRT
Source: LANRES Explanation: A value indicating disk serving,
host-to-LAN print, or LAN-to-host print must be entered
in the function field.
EWXxx6068E For internal exit type, exit name must
be EWXHLINE, EWXHLTRN, or System Action: The ISPF panel is redisplayed with
EWXHSCS the cursor placed at the beginning of the function field.
Explanation: An exit type of INTERNAL was specified, User Response: Select the disk serving, host-to-LAN
but the exit name field was not set to a valid print, or LAN-to-host print option for the function field.
IBM-supplied exit.
Source: LANRES
the cursor placed at the beginning of the exit name
field.
EWXxx6072E The function field must be set to
User Response: Reenter a value for the exit name
ADMIN or DIST
field using EWXHLINE, EWXHLTRN, or EWXHSCS, or
change the exit type. Explanation: A value indicating administration or
distribution must be entered in the function field.
Source: LANRES
the cursor placed at the beginning of the function field.
User Response: Select the administration or
EWXxx6069E The exit type must be set to EXEC,
distribution option for the function field.
INTERNAL, OLDEXEC, PGM, or TSO
Explanation: A value other than EXEC, INTERNAL,
OLDEXEC, PGM, or TSO was entered in the exit type Source: LANRES
field.
System Action: The ISPF panel is redisplayed with EWXxx6073E The protocol field must be set to
the cursor placed at the beginning of the exit type field. APPC, CHANNEL, or TCPIP
User Response: Reenter a value for the exit type field Explanation: A value indicating APPC, Channel, or
using EXEC, INTERNAL, OLDEXEC, PGM, or TSO. TCP/IP must be entered in the protocol field.
System Programmer Response: None. System Action: The ISPF panel is redisplayed with
the cursor placed at the beginning of the protocol field.
Source: LANRES
User Response: Select the APPC, Channel, or
TCP/IP option for the protocol field.
Source: LANRES

Source: LANRES
EWXxx6074E An entry already exists for the
specified name
EWXxx9001E Log file dsname does not have
Explanation: The specified name matches an existing
fixed-length records.
entry in the configuration data set.
Explanation: The LANRES log file must consist of
System Action: The ISPF configuration action
fixed-length records when wrap mode is selected for
selection panel is redisplayed.
message logging.
User Response: Enter a unique name to add a new
System Action: The log file is not used.
entry, or enter an S by the entry in the summary table to
modify the existing entry. User Response: Change the log file format to
fixed-length records or use the cumulative mode for
LANRES message logging.
Source: LANRES
Source: LANRES
EWXxx6075E The conversion indicator must be set
to YES or NO
EWXxx9002S Unable to open the LANRES
message repository: Error error.
the conversion indicator field.
Explanation: LANRES was unable to access its
message repository in order to display a message.
the cursor placed at the beginning of the conversion
indicator field. System Action: The requested message is not
displayed.
User Response: Indicate YES, that the entry should
be stored in the new format, or NO, that the entry User Response: Report the problem to the system
should be stored in the old format. support programmer.
System Programmer Response: None. System Programmer Response: Make sure that the
EWXMSGS DD is defined for the job and specifies the
Source: LANRES
correct LANRES message repository dataset name.
Source: LANRES
EWXxx6076E Clear and view options require an
established ADMIN or DIST connection
EWXxx9003E Message msgid was not found in the
Explanation: A connection to the administration or
LANRES message repository.
distribution function has not been established. Clear and
view options are not valid until after a connection to one Explanation: LANRES was unable to locate a
of these functions is successfully established. message in its message repository.
System Action: The ISPF panel is redisplayed with System Action: The requested message is not
the cursor placed at the beginning of the message displayed.
logging field.
User Response: Select an option other than clear or support programmer.
view, or establish an administration or distribution
connection and retry the operation. System Programmer Response: Make sure that the
System Programmer Response: None. correct LANRES message repository dataset name.
EWXxx9000S No storage is available to initialize EWXxx9004E Unable to read message msgid from
the heap. the LANRES message repository.
Explanation: LANRES was unable to obtain its initial Explanation: LANRES was unable to display a
storage requirements. message due to an error while reading the message
repository.
System Action: The requested message is not
displayed.
representative.
support programmer.

System Programmer Response: Make sure that the Source: LANRES
correct LANRES message repository dataset name.
EWXxx9010S Connection open exchange was
Source: LANRES unsuccessful with internal error error.
Explanation: The session initialization exchange with
EWXxx9005S LANRES requires MVS/ESA Release the NetWare server was unsuccessful with the specified
3.1.3 or later. internal error code.
Explanation: LANRES does not support the current System Action: Command processing ends. The
level of the host operating system. connection to the NetWare server is dropped.
System Action: Command processing ends. User Response: None.
User Response: None. System Programmer Response: Report the problem
to IBM.
Source: LANRES
Source: LANRES
EWXxx9011E Unable to read filename: error.

EWXxx9006E Unable to write message to dsname:
error.. Explanation: An I/O error occurred while reading a
LANRES configuration file.
Explanation: LANRES was unable to write a log
message to the indicated log file. System Action: Configuration file processing ends.
System Action: The log message is not written to the User Response: Correct the problem and reenter the
file. command.
User Response: Correct the problem indicated by the System Programmer Response: None.
error text.
Source: LANRES
Source: LANRES EWXxx9012E ’keyword’ is an incorrect
configuration keyword.
EWXxx9007R Enter the password for user user: Explanation: An incorrect keyword was specified in
the LANRES configuration options file.
Explanation: A question mark was specified for the
user password. This causes the LANRES command to System Action: The configuration option is not
prompt the user to enter the actual password. processed.
System Action: Wait for the user to enter the User Response: Correct the configuration options file
password. by specifying a valid configuration option.
User Response: Enter the password for the displayed System Programmer Response: None.
user ID.
Source: LANRES
Source: LANRES EWXxx9013E ’option’ is an incorrect value for the
keyword configuration option.
EWXxx9008E Unable to read from terminal: Error Explanation: An incorrect option was specified in the
error. LANRES configuration options file.
Explanation: LANRES was unable to read a user System Action: The configuration option is ignored.
response from the terminal because the PUTGET
User Response: Correct the configuration options file
function failed with the indicated error. See OS/390
by specifying a valid configuration option.
TSO/E Programming Services for a description of the
error codes. System Programmer Response: None.
System Action: Command processing ends. Source: LANRES
support programmer.

Source: LANRES
EWXxx9014E Unable to read NetWare service file:
error.
EWXxx9018E File I/O error detected by server
Explanation: An I/O error occurred while reading the
server.
NetWare service package file. This file contains the
current service level for the LANRES NetWare server Explanation: The service distribution catcher on the
code. NetWare server was unable to write the new service
files to disk.
System Action: NetWare service distribution will not
be done. System Action: Service distribution ends for the
server with the error.
programmer. User Response: Check the NetWare console for error
messages explaining the cause of the error. If the error
System Programmer Response: Re-install the
persists, disable service distribution for the server with
LANRES product. Contact IBM if the problem persists.
the error.
Source: LANRES
Source: LANRES
EWXxx9015I Connection established to server
server at service level level.
EWXxx9019E File CRC error detected by server
Explanation: A connection has been established with
server.
the NetWare server. The LANRES code running on the
server is at the indicated service level. Explanation: The service distribution catcher on the
NetWare server detected a CRC error for one of the
service files. The file was corrupted during transmission
User Response: None. to the server.
System Programmer Response: None. System Action: Service distribution ends for the
server with the error.
Source: LANRES
User Response: Check the NetWare console for error
EWXxx9016E Unable to send service to destination
destination: error.
the error.
controller was unable to send the current service level
to the NetWare server at the indicated destination. For Source: LANRES
an APPC connection, the destination name is either the
symbolic destination name or the fully-qualified partner
EWXxx9020E Packet sequence error detected by
LU name. For a TCP/IP connection, the destination
server server.
name is the server host name. For a channel
connection, the destination name is the channel device Explanation: The service distribution catcher on the
address assigned to the server. NetWare server detected a packet sequence error for
one of the service files. The data was corrupted during
System Action: The current service level is not sent.
transmission to the server.
User Response: Correct the cause of the error.
System Action: Service distribution ends for the
System Programmer Response: None. server with the error.
Source: LANRES User Response: Check the NetWare console for error
EWXxx9017I Service level level sent to server server.
the error.
controller has sent a new LANRES service level to the
indicated NetWare server. This service update will take Source: LANRES
effect the next time the NetWare server is started.

EWXxx9150E Dynamic allocation request for EWXxx9153E Unable to delete member member
dataset dsname failed with return code from dataset dsname: STOW error error,
return-code and error code error. reason code reason-code.
Explanation: A dynamic allocation request failed for Explanation: LANRES was unable to delete the
the indicated dataset. The return code is the decimal indicated partitioned dataset member due to a STOW
value returned in register 15 by SVC 99 and the error failure. See OS/390 DFSMS Macro Instructions for Data
code is the hexadecimal value returned in the error Sets for a description of the error and possible recovery
reason field of the SVC 99 request block. See OS/390 actions.
MVS Programming: Authorized Assembler Services
System Action: The member is not deleted.
Guide for a description of the error and possible
recovery actions. User Response: Correct the problem and retry the
request.
System Action: The dataset is not allocated.
request. Source: LANRES
EWXxx9154E Error reading dsname: error.
Source: LANRES
Explanation: An I/O error occurred while reading the
indicated dataset. The error text consists of the
EWXxx9151E Dynamic unallocation request for DD
messages returned by the SYNADAF system function.
ddname failed with return code
return-code and error code error. System Action: Command processing ends.
Explanation: A dynamic unallocation request failed for User Response: Correct the problem and retry the
the indicated DD. The return code is the decimal value request.
returned in register 15 by SVC 99 and the error code is
the hexadecimal value returned in the error reason field System Programmer Response: None.
of the SVC 99 request block. See the OS/390 MVS Source: LANRES
Programming: Assembler Services Guide for a
description of the error and possible recovery actions.
EWXxx9155E Error writing dsname: error.
System Action: The dataset is not freed.
Explanation: An I/O error occurred while writing the
User Response: Correct the problem and retry the indicated dataset. The error text consists of the
request. messages returned by the SYNADAF system function.
System Programmer Response: None. System Action: Command processing ends.
Source: LANRES User Response: Correct the problem and retry the
request.
EWXxx9152E Dynamic allocation request for System Programmer Response: None.
device ddname failed with return code
return-code and error code error. Source: LANRES
Explanation: A dynamic allocation request failed for

the indicated device. The return code is the decimal EWXxx9156E Unable to open member member in
value returned in register 15 by SVC 99 and the error dataset dsname: FIND error error,
code is the hexadecimal value returned in the error reason code reason-code.
reason field of the SVC 99 request block. See the Explanation: LANRES was unable to open the
OS/390 MVS Programming: Authorized Assembler indicated partitioned dataset member due to a FIND
Services Guide for a description of the error and failure. See OS/390 DFSMS Macro Instructions for Data
possible recovery actions. Sets for a description of the error and possible recovery
System Action: The device is not allocated. actions.
User Response: Correct the problem and retry the System Action: The dataset is not opened.
request. User Response: Correct the problem and retry the
System Programmer Response: None. request.

Source: LANRES

Source: LANRES
EWXxx9157E Unable to store member member in
dataset dsname: STOW error error,
reason code reason-code. EWXxx9161E TSO service routine IKJEFTSR ended
with return code code and reason code
Explanation: LANRES was unable to create the
reason-code.
indicated partitioned dataset member due to a STOW
failure. See OS/390 DFSMS Macro Instructions for Data Explanation: The IKJEFTSR service routine ended
Sets for a description of the error and possible recovery with an unexpected return code. See OS/390 TSO/E
actions. Programming Services for a description of the return
codes and possible recovery actions.
System Action: The member is not stored.
System Action: The TSO command is not executed.
request. User Response: None.
EWXxx9158E Unable to store member member in EWXxx9162E ’name’ was not found.
dataset dsname because the dataset
directory is full. Explanation: The indicated TSO command, REXX
procedure, or host program program was not found.
Explanation: LANRES was unable to create the
indicated partitioned dataset member because there is System Action: The command or program is not run.
no room available in the dataset directory. User Response: Make sure that the name is correct
System Action: The member is not stored. and that the proper DD statements are defined.
User Response: Correct the problem and retry the System Programmer Response: None.
Source: LANRES EWXxx9163E The ’name’ command is not
supported in a non-TSO environment.
EWXxx9159E ’name’ terminated due to attention. Explanation: A TSO command was issued in a
non-TSO environment. A non-TSO environment exists
Explanation: A TSO command or program was when either the Terminal Monitor Program (TMP) is not
terminated by an attention interrupt. running or the CALL command was used to start the
LANRES program.
System Action: The command is terminated.
System Action: The command is not processed.
Source: LANRES
Source: LANRES
EWXxx9160E ’name’ abnormally terminated:
Completion code code, Reason code EWXxx9164E Unable to run program name: error.
reason-code.
Explanation: LANRES was unable to run a host
Explanation: A TSO command, REXX procedure, or system program.
host system program abnormally terminated. The
completion code is either a hexadecimal system System Action: The program is not executed.
completion code (Sxxx) or a decimal user completion User Response: Correct the problem indicated by the
code (Unnnn). error text.
System Action: The command is terminated. System Programmer Response: None.
User Response: For a system completion code, see Source: LANRES
OS/390 MVS System Codes for a description of the
completion code. For a user completion code, refer to
the command or program documentation for a
description of the completion code.

EWXxx9165E Syntax error in command ’command’ EWXxx9169E Unable to run REXX procedure:
IRXEXEC error error.
Explanation: LANRES detected a syntax error in a
system command. Explanation: LANRES was unable to run a REXX
procedure. See OS/390 TSO/E REXX Reference for a
System Action: The command is not run.
description of the error and possible recovery actions.
User Response: Specify a valid system command.
System Action: The REXX procedure is not executed.
Source: LANRES request.
EWXxx9166E Unable to locate program name:
Source: LANRES
BLDL error error, reason code
reason-code.
EWXxx9170E Unable to run REXX procedure name:
Explanation: LANRES was unable to locate the
error.
indicated program due to a BLDL failure. See OS/390
DFSMS Macro Instructions for Data Sets for a Explanation: LANRES was unable to run a REXX
description of the error and possible recovery actions. procedure.
System Action: The program is not executed. System Action: The REXX procedure is not executed.
User Response: Correct the problem and retry the User Response: Correct the problem indicated by the
request. error text.
EWXxx9167E Unable to create REXX environment: EWXxx9171S LANRES task name terminated by
IRXINIT error error, reason code attention interrupt.
reason-code.
Explanation: A TSO attention interrupt was received
Explanation: LANRES was unable to create the while a LANRES task was active. A U0024 user abend
REXX environment. See OS/390 TSO/E REXX will be issued to terminate the current task.
Reference for a description of the error and possible
recovery actions.
EWXxx9172E Online help is not available.
Source: LANRES
Explanation: Online LANRES help was requested but
LANRES is not running in a foreground TSO session.
EWXxx9168E Unable to issue REXX stack request:
IRXSTK error error. System Action: The help information is not displayed.
Explanation: LANRES was unable to issue a REXX User Response: Online help is available only when
data stack request. See OS/390 TSO/E REXX LANRES is invoked as a TSO command in a
Reference for a description of the error and possible foreground TSO session. Retry the help request when
recovery actions. logged on to TSO.
System Action: The stack operation is not performed. System Programmer Response: None.
User Response: Correct the problem and retry the Source: LANRES
request.
System Programmer Response: None. EWXxx9173E Unable to display help panel name:
ISPTUTOR return code code.
Source: LANRES
Explanation: Online LANRES help was requested but
the ISPTUTOR program either was not available or

encountered an error while displaying the help
EWXxx9177E Linear dataspace dsname has not
information.
been initialized.
System Action: The help information is not displayed.
Explanation: The indicated VSAM linear dataspace
User Response: Make sure ISPF is available and that has not been initialized for use with LANRES.
the proper DD statements have been defined.
User Response: Use the EWXLDCRT command to
Source: LANRES initialize the dataspace and then retry the failing
command.
EWXxx9174E Unable to display help panel name: System Programmer Response: None.
error.
Source: LANRES
Explanation: The requested help panel either was not
found in the ISPF panel library or an error occurred
EWXxx9178E DSPSERV request for dsname failed
while attempting to open the panel member.
with error error, reason code
System Action: The help information is not displayed. reason-code.
User Response: Make sure that the LANRES ISPF Explanation: A dataspace request for the indicated
panel library dataset is allocated to the ISPPLIB DD. VSAM linear dataspace failed with the indicated error
and reason codes. See the OS/390 MVS Programming:
System Programmer Response: None. Authorized Assembler Services Reference ALE-DYN for
Source: LANRES a description of the DIV error codes.
System Action: Disk serving is terminated for the
EWXxx9175E IDCAMS error error detected while failing LANRES volume.
listing catalog level level. User Response: Correct the problem and restart the
Explanation: The IDCAMS utility returned an error for disk server job.
the indicated catalog level. The error is usually the last System Programmer Response: None.
three digits of the IDCAMS error message. For
example, a return code of 12 indicates that message Source: LANRES
IDC3012I was issued by IDCAMS. See the
DFSMS/MVS Access Method Services for VSAM
EWXxx9179E Dynamic allocation request for
manual for more information on IDCAMS. See the
SYSOUT failed with return code
OS/390 MVS System Messages, Vol 3 (EWX-IEB)
return-code and error code error.
manual for a description of the IDC messages.
Explanation: A dynamic allocation request failed for a
System Action: The catalog list is not created.
SYSOUT dataset. The return code is the decimal value
User Response: Correct the problem and retry the returned in register 15 by SVC 99 and the error code is
failing command. the hexadecimal value returned in the error reason field
of the SVC 99 request block. See OS/390 MVS
System Programmer Response: None. Programming: Assembler Services Reference for a
Source: LANRES description of the error and possible recovery actions.
System Action: The dataset is not allocated.
EWXxx9176E DIV request for dsname failed with User Response: Correct the problem and retry the
error error, reason code reason-code. request.
Explanation: A data-in-virtual request for the indicated System Programmer Response: None.
VSAM linear dataspace failed with the indicated error
and reason codes. See the OS/390 MVS Programming: Source: LANRES
Authorized Assembler Services Reference ALE-DYN for
a description of the DIV error codes.
EWXxx9180E IDCAMS error error detected while
System Action: Disk serving is terminated for the allocating VSAM dataset dsname.
failing LANRES volume.
Explanation: The IDCAMS utility returned an error for
User Response: Correct the problem and restart the the indicated VSAM dataset. The error code is usually
disk server job. the last three digits of the IDCAMS error message. For
example, a return code of 12 indicates that message
System Programmer Response: None. IDC3012I was issued by IDCAMS. See the
Source: LANRES DFSMS/MVS Access Method Services for VSAM

manual for more information on IDCAMS. See the Source: LANRES
OS/390 MVS System Messages, Vol 3 (EWX-IEB)
manual for a description of the IDC messages.
EWXxx9184E Internal error detected - dictionary
System Action: The LANRES disk image dataset is tree corrupted.
not created.
Explanation: LANRES detected an internal error while
User Response: Correct the problem and retry the building a data compression dictionary.
EWXLDCRT command.
Source: LANRES
to IBM.
EWXxx9181E IDCAMS error error detected while
Source: LANRES
deleting VSAM dataset dsname.
Explanation: The IDCAMS utility returned an error for
EWXxx9185E Unable to read dictionary dsname:
the indicated VSAM dataset. The error code is usually
error.
the last three digits of the IDCAMS error message. For
example, a return code of 12 indicates that message Explanation: An I/O error occurred while reading the
IDC3012I was issued by IDCAMS. See the data compression dictionary dataset.
DFSMS/MVS Access Method Services for VSAM
manual for more information on IDCAMS. See the System Action: Command processing ends.
OS/390 MVS System Messages, Vol 3 (EWX-IEB) User Response: Correct the problem and retry the
manual for a description of the IDC messages. failing command.
System Action: The LANRES disk image dataset is System Programmer Response: None.
not deleted.
Source: LANRES
EWXLDDLT command.
EWXxx9186E dsname does not contain a valid
System Programmer Response: None. dictionary.
Source: LANRES Explanation: The indicated dataset does not contain a
valid data compression dictionary.
EWXxx9182I message_text System Action: Command processing ends.
Explanation: This message is used by the EWXWTO User Response: Change the EWXDICT DD statement
command to send a message to a host system operator to point to a valid data compression dictionary dataset
console. The message text is supplied by the caller of and retry the failing command.
EWXWTO.
Source: LANRES
System Programmer Response: None. EWXxx9187W Disk image dsname is too small for
Source: LANRES data compression.
Explanation: Data compression was requested but the
EWXxx9183E DSPSERV request failed with error disk image dataset is not large enough to contain the
error and reason code reason-code. data compression control tables. As a general rule, the
disk image dataset should not be smaller than one half
Explanation: A dataspace request failed with the the size of the NetWare volume segment.
indicated error and reason codes. See the OS/390 MVS
Programming: Authorized Assembler Services System Action: Data compression is not used for the
Reference ALE-DYN for a description of the DSPSERV disk image.
error codes. User Response: If the error occurred while creating a
System Action: Command processing ends. new disk image dataset, specify either a larger image
dataset size or a smaller NetWare volume segment
User Response: Correct the problem and retry the size. If the error occurred while restoring a disk image
failing command. dataset from a dump file, create a new disk image
dataset and either specify a larger disk image dataset
size or do not request data compression.

EWXxx9197S LANRES task name abnormally
Source: LANRES terminated with completion code code
reason code reason-code.
EWXxx9188E Unable to enqueue dataset dsname: Explanation: A LANRES task was abnormally
Error error. terminated. The completion code is either a
hexadecimal system completion code (Sxxx) or a
Explanation: LANRES was unable to issue an decimal user completion code (Unnnn). The reason
enqueue for a sequential or partitioned dataset. The code is always a hexadecimal value. See OS/390 MVS
error code is the return code from the ENQ macro. System Codes for a description of the system
System Action: The dataset is not opened. completion codes.
User Response: Report the problem to the system LANRES uses the following user completion codes:
programmer. 0016 - The C/370 abort() function was requested.
0020 - Communication subtask abnormally
System Programmer Response: Report the problem terminated.
to IBM. 0024 - Task terminated by attention interrupt.
Source: LANRES System Action: The LANRES command is
terminated.
EWXxx9195S Unable to attach the communication User Response: Correct the problem and retry the
subsystem task: Error error. command.
Explanation: LANRES was unable to start the System Programmer Response: None.
communication subsystem task. This task performs all
inter-task and inter-system communication functions as Source: LANRES
well as message display and logging functions.
Error codes between 0 and 99 are the ATTACH EWXxx9198E Unable to locate C/370 save area
return code. during exit processing.
Error codes between 100 and 199 are the IDENTIFY
return code + 100. Explanation: The LANRES ESTAE exit was unable to
locate a C/370 save area for use during recovery
System Action: The current task is terminated. processing.
User Response: Report the problem to the system System Action: ESTAE recovery is not attempted and
programmer. the task is terminated.
System Programmer Response: Report the problem User Response: Report the problem to the system
to IBM. and is not translated. support programmer.
Source: LANRES System Programmer Response: Report the problem
to IBM.
EWXxx9196S The communication subtask is not Source: LANRES
responding to requests.
Explanation: The LANRES communication subtask is EWXxx9199S The communication subtask has
not responding to requests. This task performs all abnormally terminated.
inter-task and inter-system communication functions as
well as message display and logging functions. This Explanation: The LANRES communication subtask
error can occur if a read has been issued for data from has terminated. This task performs all inter-task and
the NetWare server and the server does not respond. inter-system communication functions as well as
message display and logging functions. There should be
System Action: The current task is terminated with a additional messages in the job log indicating the cause
U0020 abend. of the failure.
User Response: Make sure that the NetWare server System Action: The current task is terminated with a
is operational and that the LANRES NLM has not U0020 abend.
terminated.
System Programmer Response: None. request.
Source: LANRES

EWX Server Messages
EWX Server Messages

control block. Other messages will be issued to
0100I progname initialized.
help determine the problem. The session is
Explanation: The progname program has been loaded cleaned up.
and successfully initialized.
System Action: The failing program is unloaded or
System Action: The program is ready to process restarted.
transactions.
System Programmer Response:
System Programmer Response: None. v For RC=1, a session will have to be made available
Source: LANRES for the program to successfully load. Free up one of
the sessions by unloading LANRES functions that are
not being used or add more sessions using the
0101I progname Service Level level initialized. SESSIONS field in the EWXCOMM.INI file (this
Explanation: The progname program at service level requires unloading and reloading all the LANRES
level has been loaded and successfully initialized. NLMs).
v For RC=6, correct the problem using the other
System Action: The program is ready to process messages. Then restart the EWXCOMM NLM.
transactions.
v For RC=8, use the other messages to determine and
User Response: None. correct the problem. Then restart the failing program.
Source: LANRES
0107E progname level mismatch between Host
and Server programs.
0102E Communications RECEIVE command
error (RC=return-code). Explanation: The version, release, and modification
numbers of program progname do not match the
Explanation: An error occurred while reading data
release and modification numbers of the corresponding
from the host.
program on the host.
System Action: The communication session ends, but
System Action: The server program remains loaded
the failing program will start to listen for a connection
waiting for the correct version of the host program to be
from the host again. Other messages from EWXCOMM
run.
should be issued.
System Programmer Response: Check the levels of
System Programmer Response: The problem could
the server and host programs. Then determine which
be that the host ended the conversation or it could be
level should be run and make the necessary changes.
that the communication link had an error. Use the other
messages to determine the problem. Source: LANRES
Source: LANRES
0109S A request has been received that
cannot be executed by progname.
0103E Unable to start communications
(RC=return-code). Explanation: The server program progname has
received an incorrect command request from the host.
Explanation: The communications driver was unable
to start a session on behalf of an application. The System Action: The request is ignored and a return
possible error return codes are: code is passed back to the host program.
1 Communication layer could not find an empty User Response: None.
control block
System Programmer Response: Ensure the
6 Communication layer failed to initialize and will LANRES host programs are installed at the correct
unload. Other messages will be issued release level that matches the NetWare NLMs. Do this
indicating the failure(s). by entering either the EWXADMIN QUERY ID or
EWXDS QUERY ID command. The user may need to
8 An error occurred after finding the session
enter the EWXCONN LINK command to establish a new
connection to the server.

EWX Server Messages
Source: LANRES and restart it, or enter a EWXCONN DROP command
from the host user ID connected to the NLM.
0110I progname has been unloaded. Source: LANRES
Explanation: The program progname has been
unloaded by a request from the NetWare console. 0130I Connection established with host disk
server program, session session.
System Action: The program is unloaded. Any
session being used by progname becomes available. Explanation: The host disk server has responded with
disk information necessary for connection to the server.
System Action: The disks are now allocated to
NetWare and available for use.
Source: LANRES
Source: LANRES
0111I Host timeout on session session.

0132E Insufficient memory to initialize disks.
Explanation: The host program has not responded to
Explanation: The disk driver, EWXDISK, was unable
a request within the time specified by the disk timeout
to allocate the storage needed to add the disks.
value.
System Action: The disks are not allocated to the
System Action: The program stays loaded waiting for
NetWare server. The disk driver, EWXDISK, will
a connection. The EWXDISK component will deactivate
continue to service disk requests for currently allocated
all disks associated with that line and reactivate the
disks. If this occurs during initialization, EWXDISK will
disks when the connection is reestablished.
unload.
System Programmer Response: Restart the host
System Programmer Response: Unload programs or
program related to the NLM used to reestablish a
install more system memory on the server.
connection.
Source: LANRES
Source: LANRES
0133I Number of disks equals zero on

0112S Host did not read the correct number
session session.
of packets.
Explanation: The disk driver, EWXDISK, received a
Explanation: The server application tried to send a
response from the host program indicating that there
certain number of packets of data to the host program.
are no disks.
The host program was interrupted and all the packets
were not read. System Action: The disk driver, EWXDISK, will
remain loaded.
System Action: The server program remains
operational. The packets received at the host program System Programmer Response: Restart the disk
are discarded. server with the required disks.
System Programmer Response: Other error
messages may indicate why all the packets were not 0134E Disks are currently active; use
read and should be used to correct the problem. QUIESCE or FORCE option.
Source: LANRES Explanation: The EWXCMD DROP DISK command
was entered while disks were still active.
0115E Host program is not a progname server. System Action: The disk is not dropped.
Explanation: The program on the NetWare server User Response: None.
does not match the program on the host. The server is
System Programmer Response: Enter the EWXCMD
connected to a host program that performs a different
DROP DISK command again with the QUIESCE or
function.
FORCE option; for example:
System Action: The program remains loaded, waiting LOAD SYS:\EWXNLM\EWXCMD DROP DISK 20 QUIESCE
for a request from the correct program.
System Programmer Response: Unload the NLM

EWX Server Messages
For more information about the EWXCMD DROP DISK volumes associated with a host server.
command and the QUIESCE and FORCE options, see
OS/390 LANRES Configuration Files and Commands.
System Programmer Response: Do not enter a
Source: LANRES
MOUNT command on the server while the disk driver,
EWXDISK, is mounting these volumes.
0135S Initialization failed; unable to add disk
Source: LANRES
device.
Explanation: The disk driver, EWXDISK, received an
0143I Log file copied to: log-fname.
unacceptable return code from NetWare when adding a
disk to the system. Explanation: The current log has been saved in file
log-fname.
System Action: The disk driver, EWXDISK, unloads.
System Programmer Response: Reload the disk
driver. System Programmer Response: Since the log file
has been saved, it may be desirable to clear the log file
Source: LANRES
using the ″Reset log file″ menu option.
Source: LANRES
0136S Initialization failed; unable to add disk
card.
0144I Message Buffer dumped to:
Explanation: The disk driver, EWXDISK, received an
MB-dumped.
unacceptable return code from NetWare when adding a
disk to the system. Explanation: The wrapping buffer used to save trace
messages has been dumped to file MB-dumped.
System Action: The disk driver, EWXDISK, will
unload. System Action: None.
System Programmer Response: Retry the operation. System Programmer Response: The file may be
used to view the last trace messages saved. Tracing to
Source: LANRES
this buffer is started by selecting the ″Selective Trace to
Buffer″ option from the ″Trace options″ menu.
0137E The subchannel specified is not active.
Source: LANRES
Explanation: The subchannel specified on the DROP
DISK command is not being used by the disk driver,
0146E Log file buffer full, lost-message-count
EWXDISK.
message(s) were lost.
System Action: The disk driver, EWXDISK, continues
Explanation: The log file buffer is used to process
to process requests.
messages before writing them to the log file. The buffer
User Response: None. overflowed before writing completed and
lost-message-count messages were unable to be
System Programmer Response: Enter the DROP
processed.
DISK command again specifying a subchannel that the
disk driver, EWXDISK, is using. To see which System Action: Message logging continues after the
subchannels the disk driver is using, use the EWXCMD loss.
Query Connections command.
For more information about the EWXCMD DROP DISK
System Programmer Response: The log buffer size
command, see OS/390 LANRES Configuration Files
may be increased in the configuration file using the
and Commands.
LOG_BUFFER_SIZE keyword
Source: LANRES
Source: LANRES
0141I Mounting nn volumes; please do not

0199S An internal processing error occurred
issue MOUNT command until done.
with symptom string: symptom.
Explanation: The disk driver, EWXDISK, sends this
Explanation: The system detected that it was in an
message before mounting the volumes.
invalid state.
System Action: The EWXDISK program mounts the

EWX Server Messages
System Action: Unpredictable. System Action: The program is unloaded from the
NetWare server.
User Response: Record the symptom string and
notify IBM service. User Response: None.
System Programmer Response: None. System Programmer Response: Load the program
using the correct syntax. For syntax information, see
Source: LANRES
Source: LANRES
0501E Insufficient parameters specified.
Explanation: Additional parameters are required for
0505E API NetWare API error
this command.
(RC=return-code).
System Action: The program is unloaded from the
Explanation: A LANRES call to the NetWare API API
NetWare server.
returned with the error return-code.
System Action: Error recovery is initiated.
System Programmer Response: Load the program
OS/390 LANRES Configuration Files and Commands. System Programmer Response: Retry the operation
that failed. If the problem persists, look up the return
Source: LANRES
code in the NetWare library.
Source: LANRES
0502E Incorrect parameter(s) parameter(s)
specified.
0506E Duplicate parameter(s) parameter(s)
Explanation: Incorrect parameter(s) were entered on
specified.
the command line following the program name. They
were possibly misspelled, incorrect, incomplete, or Explanation: The parameter(s) listed in the message
improperly abbreviated. are part of the program syntax, but the parameter(s)
have been entered more than once.
NetWare server. System Action: The program is unloaded from the
NetWare server.
using the correct syntax. For syntax information, see System Programmer Response: Load the program
OS/390 LANRES Configuration Files and Commands. using the correct syntax. For syntax information, see
Source: LANRES
Source: LANRES
0503E Too many parameters entered.
0507E Incorrect server name server specified.
Explanation: Extraneous parameters were entered on
the command line following the program name. Explanation: A server name must be between 2 and
47 characters long and cannot contain spaces or any of
the following special characters:
NetWare server.
User Response: None. / (slash)
\ (back slash)
System Programmer Response: Load the program : (colon)
; (semicolon)
, (comma)
Source: LANRES * (asterisk)
? (question mark)
0504E The password entered is longer than
127 characters. System Action: The program is unloaded from the
Explanation: The password can not be longer than NetWare server.
127 characters in length for a NetWare object such as a User Response: None.
user ID or the LANRES object.

EWX Server Messages
0511E Parameter parameter can only be
Source: LANRES specified by the first NLM that is
loaded for this function.
0508E Conflicting parameter(s) parameter(s) Explanation: The program that issued this message
specified. can be loaded multiple times on the NetWare server,
but certain parameters, such as the parameter listed in
Explanation: The parameter(s) listed in the message the message, can be specified only by the first copy of
can not be used with another parameter entered on the this program to be loaded. The value obtained from this
command line. parameter will be used by subsequent copies of the
System Action: The program is unloaded from the program to be loaded.
NetWare server. System Action: The copy of the program that issued
User Response: None. this message is unloaded from the NetWare server.
System Programmer Response: Load the program User Response: None.

using the correct syntax. For syntax information, see System Programmer Response: If you want to use
OS/390 LANRES Configuration Files and Commands. the parameter listed in the message, unload all copies
Source: LANRES of this program from the server and load the program
using your parameters. Otherwise, load the program
with the correct syntax. For syntax information, see
0509E Directory name in parameter parameter OS/390 LANRES Configuration Files and Commands.
is too long.
Source: LANRES
Explanation: The directory associated with the
parameter listed in the message exceeds the allowable
length of 254 characters. 0512E Parameter parameter can only be
specified by the first EWXHLPRT.NLM
System Action: The program is unloaded from the or EWXDIST.NLM loaded.
NetWare server.
Explanation: Multiple copies of the EWXHLPRT.NLM
User Response: None. and EWXDIST.NLM can be loaded on the NetWare
System Programmer Response: Load the program server at the same time, but certain parameters, such
using the correct syntax. For syntax information, see as the parameter listed in the message, can only be
OS/390 LANRES Configuration Files and Commands. specified by the first copy of either EWXHLPRT.NLM or
EWXDIST.NLM to be loaded. The value obtained from
Source: LANRES this parameter will be used by subsequent copies of
EWXHLPRT.NLM and EWXDIST.NLM to be loaded.
0510E Program unloaded. Required values System Action: The copy of the program that issued
were not successfully initialized. this message is unloaded from the NetWare server.
Explanation: Multiple copies of the program listed in User Response: None.
the message were loaded on the NetWare server at the
same time. These copies are dependent on certain System Programmer Response: To use the
values being initialized by the first copy of the program parameter listed in the message, unload all copies of
to be loaded. Not all the required values were initialized EWXHLPRT.NLM and EWXDIST.NLM from the server
successfully. All copies of the program will be unloaded and load the first program using the parameters.
from the server. Otherwise, load the program with the correct syntax. For
syntax information, see OS/390 LANRES Configuration
System Action: All copies of the program are Files and Commands.
unloaded.
Source: LANRES
System Programmer Response: Verify all required 0513E The PWIN and PWOUT parameters
values, such as component passwords or the LANRES must be specified as a pair. If one
object password, are available to the first copy of the parameter is specified, the other
program being loaded. parameter must also be specified.
Source: LANRES Explanation: The PWIN and PWOUT parameters
designate the values for the component passwords and
must be specified as a pair.
NetWare server.

EWX Server Messages
System Programmer Response: Load the program System Programmer Response: Correct the file
using the correct syntax. For syntax information, see filename and load the program again. Verify comments
OS/390 LANRES Configuration Files and Commands. in the file start with ’*’, ’/’, or ’;’ in the first column.
0514E Cannot open component password file 0517I Trace option turned on for function
filename. Program will be unloaded. function.
Explanation: The program listed in the message tried Explanation: The TRACE parameter was specified on
to open the component password file but the file cannot the command line or in the initialization file. The
be found or opened. program that issued this message will now run in
TRACE mode.
NetWare server. System Action: Processing continues.
System Programmer Response: Verify the System Programmer Response: The TRACE
component password file exists. The location where the parameter should be used with the help of an IBM
file can be found can be specified by using the function service representative.
or communication driver command line or from the
Source: LANRES
communication driver initialization file. Default
component password files can be created. The default
file name should be EWXxxxxx.NPW (xxxxx should be 0518E Authentication error. Signature
replaced by the function ADMIN, DIST, DISK, HLPRT, or mismatch between host and server
LHPRT) and the file should be located in the directory programs. Connection will be dropped.
the program is loaded from or in the SYS:\EWXNLM
directory. Explanation: Packets sent between the host and the
NetWare server contain signatures to verify the packet
Source: LANRES originated from the correct function. If a signature that is
received does not match what is expected, then a
communications error has occurred and the connection
0515E Line number of component password
to the host will be dropped.
file filename is too long. Program will be
unloaded. System Action: Connection to the host is dropped.
The program on the NetWare server tries to recover
Explanation: Lines in the component password file,
from this error.
except comments, are limited to 128 characters in
length. Line number in filename exceeded this limit. User Response: The user on the host should enter a
EWXCONN LINK command to establish a new
connection with the NetWare server.
NetWare server.
System Programmer Response: This problem may
occur if the user on the host is using subchannels for
System Programmer Response: Correct the file communications and does not use the LANRES LINK
filename and load the program again. command to change the set of subchannels used for
communications. If the problem persists, contact an IBM
Source: LANRES
service representative.
Source: LANRES
0516E Incorrect password specified in line
number of component password file
filename. Program will be unloaded. 0519E Error sending data to the host
(RC=return-code).
Explanation: A component password must be
between 1 and 8 characters in length, and be an Explanation: A communications error occurred while
alphanumeric string (from 0 to 9, a to z, and A to Z). sending data to the host.
The password is not case sensitive. Line number in
System Action: The program on the NetWare server
filename contains a password that does not fit this
tries to recover from this error.
format.
NetWare server. System Programmer Response: Verify the
communications method is operating correctly.

EWX Server Messages
0520W Error receiving data from the host 0523E Cannot find or open a file which
(RC=return-code). contains the LANRES object password.
Program will be unloaded.
receiving data from the host. Explanation: The program listed in the message tried
to find the LANRES object password in a designated
System Action: The program on the NetWare server
LANRES object password file or in default LANRES
tries to recover from this error.
object password files, but these files could not be found
User Response: None. or opened.
System Programmer Response: Verify the System Action: The program is unloaded from the
communications method is operating correctly. NetWare server.

0521E Cannot open a connection for the LANRES object password file exists. Specify where the
function function because there are no file can be found by using the function or the
available sessions. communications driver command line, or the
communications driver initialization file. A default
Explanation: The SESSIONS parameter in the LANRES object password file can be created. The
communications driver command line or in the default file name should be EWXLOBJ.PWF, and the file
initialization file specifies how many sessions are should be located in the directory the program is loaded
available to the LANRES functions. Each of the from or in the SYS:\EWXNLM directory.
EWXADMIN.NLMs, EWXDIST.NLMs,
EWXHLPRT.NLMs, and EWXLHPRT.NLMs loaded on Source: LANRES
the server take up one of the available sessions. The
EWXDISK.DSK program takes up as many available
0524E Line number of LANRES object
sessions as specified by its DISK_SESSIONS
password file filename is too long.
parameter. This message was issued because all the
Program will be unloaded.
available sessions were taken, so no new LANRES
function can be loaded or started. Explanation: Lines in the LANRES object password
file, except comments, are limited to 128 characters in
System Action: If the function is ADMIN, DIST,
length. Line number in filename exceeded this limit.
HLPRT, or LHPRT, then the program is unloaded from
the NetWare server. If the function is DISK, then the System Action: The program is unloaded from the
new session is not started. NetWare server.
System Programmer Response: Add additional System Programmer Response: Correct the file
sessions with the EWXCMD server command or free up filename and load the program again.
some sessions by unloading one of the LANRES
Source: LANRES
functions.
Source: LANRES
0525E Password specified in line number of
LANRES object password file filename
0522E Incorrect component password is too long. Program will be unloaded.
password specified.
Explanation: A password can not be longer than 127
Explanation: A component password must be characters in length for the LANRES object. Line
between 1 and 8 characters in length, and be an number in filename contains a password that exceeds
alphanumeric string (from 0 to 9, a to z, and A to Z). this limit.
The password is not case sensitive.
System Action: The program is unloaded from the NetWare server.
NetWare server.
System Programmer Response: Correct the file
System Programmer Response: Load the program filename and load the program again.
Source: LANRES

EWX Server Messages
0526I Program has initialized or restarted.
Explanation: The program listed in the message has
performed one of the following:
v The program has been loaded on the NetWare server
and has initialized successfully. Source: LANRES
v The program has recovered from an error and
restarted successfully. 0530E Logfile is full.
System Action: None. Explanation: The log file has reached its maximum
size and the current message cannot be logged.
System Action: The message is not logged.
Source: LANRES
System Programmer Response: Remove the log file
or increase the maximum size for the log file in the
0527E Cannot allocate memory for data
EWXCOMM.INI file.
encryption or decryption. Program will
restart. Source: LANRES
Explanation: Not enough memory is available on the
NetWare server to run the data encryption program for 0531W The size of the logfile has exceeded
processing component passwords. the threshold.
System Action: The connection to the host will be Explanation: While logging a message, the log file’s
dropped. size exceeded the specified threshold.
User Response: None. System Action: None.
System Programmer Response: If the problem User Response: None.
persists, free up server memory by unloading NLMs or
add additional system memory to the server. System Programmer Response: None.
0528S An unauthorized connection was 0532E Parameter parameter is longer than the
attempted to the function function. maximum of number characters.
Connection to the host will be Explanation: The parameter listed in the message is
dropped. too long.
Explanation: Component passwords are used to System Action: The program is unloaded from the
authorize the connection between the host and the NetWare server.
NetWare server. These component passwords must be
the same on the host and the server for the connection User Response: None.
to be maintained. The server program received an System Programmer Response: Load the program
incorrect password, which means the connection is not using the correct syntax. For syntax information, see
authorized and will be dropped. OS/390 LANRES Configuration Files and Commands.
System Action: Connection to the host is dropped. Source: LANRES
System Programmer Response: Verify the 0533E Incorrect value value specified for
component passwords are the same on the host and on parameter parameter.
the server. Explanation: The value listed in the message was
Source: LANRES specified on the command line, but it is not an
acceptable value for the parameter listed in the
message.
0529E Value missing for parameter parameter.
Explanation: The parameter parameter requires an NetWare server.
associated value.
NetWare server. System Programmer Response: Load the program

EWX Server Messages
using the correct syntax. For syntax information, see System Programmer Response: None.
Source: LANRES
Source: LANRES
0538I Connection between NLM_name and
0534E One or both passwords cannot be the host on session session_number
found in the component password file will be dropped.
filename. Program will be unloaded.
Explanation: The program on the host has requested
Explanation: Both component passwords are required that the connection to the NLM be dropped. The internal
to connect the host to a NetWare function. session number is displayed.
System Action: The program is unloaded from the System Action: None.
NetWare server.
System Programmer Response: Correct the file
Source: LANRES
filename and load the program again.
Source: LANRES
0539E Cannot obtain a communication buffer
to send to the host.
0535S Unable to load as EWXCOMM failed
Explanation: The NLM asked the communication layer
initialization.
for a buffer to send to the host but the communication
Explanation: EWXCOMM did not initialize. All other layer was unable to fulfill the request. Suspect
LANRES NLMs will not start. insufficient server memory for the buffer.
System Action: The NLM will unload. System Action: The connection to the host is
restarted or the NLM is unloaded.
System Programmer Response: Examine the log file
or console to determine why EWXCOMM did not System Programmer Response: If the problem
initialize. Fix the problem and then restart EWXCOMM persists, free up server memory by unloading NLMs or
followed by required LANRES NLMs. add more memory to the server.
0536E API NetWare API error (RC=return-code; 0540I NetWare Directory Services not
message). installed / DS.API not loaded.
Explanation: A call was made to the NetWare API Explanation: Either Netware Directory Services is not
listed in the message and an error was returned. The installed or DS.API not loaded.
return code from the API and, if available, an
System Action: Bindery Emulation will be used.
explanation for the error are also displayed.
User Response: If NDS is installed, load DS.API to
use NetWare Directory Services and then reload this
User Response: None. NLM. Otherwise, use bindery services for this NLM.
System Programmer Response: Retry the operation System Programmer Response: Uses bindery
that failed. If the problem persists, look up the return services.
Source: LANRES
Source: LANRES
0541E API NetWare API error
0537I NLM_name has established a (RC=return-code).
connection to the host on session
Explanation: A LANRES call to the NetWare API API
session_number.
returned with the error return-code.
Explanation: The NLM has established a connection
to a program on the host. The internal session number
is displayed. User Response: None.
System Action: None. System Programmer Response: Check the file(s) in
the Print Queue. If the size is blank, delete it and retry

EWX Server Messages
the operation. If the problem persists, look up the return System Action: The program is unloaded.
Source: LANRES
System Programmer Response: If the return code is
1, 3, or 4, report the error to an IBM service
1201I LAN-to-host printing has established representative. If the return code is 2, operation will
host communications. continue normally.
Explanation: A communications link has been Source: LANRES
established between the server and the host.
System Action: The file server will wait indefinitely for 1206I EWXLHPRT.NLM stopped because
the message from the host. When the proper message print server was deleted.
is received and processing of print jobs is to begin, this
Explanation: The NetWare print server associated
message is displayed. Should the connection be lost
with EWXLHPRT.NLM was deleted. When this happens,
and regained, this message will be displayed.
the EWXLHPRT.NLM no longer has access to the
User Response: None. NetWare Queue Management System and cannot
process print jobs.
System Action: The EWXLHPRT.NLM which issued
Source: LANRES
the message is unloaded.
1203S No print queues found for the print
server. System Programmer Response: None.
Explanation: There were no print queues set up on Source: LANRES
the NetWare server that could be attached to the
LAN-to-host print server.
1208E Print queue file read error. Print server
System Action: The program is unloaded. restarting.
User Response: None. Explanation: A system I/O error was detected while
trying to read a print queue file.
System Programmer Response: Use PCONSOLE or
EWXADMIN to create the necessary print queues. See System Action: The program will reset and try to read
EWXADMIN ADDPRTQ in OS/390 LANRES the file again.
Configuration Files and Commands.
Source: LANRES
Source: LANRES
1204S Print server name already in use.
Explanation: The print server specified during the
1209E Number of print queues exceeded 100;
start up of print on the host, or the default name:
excess queues discarded.
HOSTPRT, is already being serviced by another print
server utility such as PSERVER.NLM. Explanation: The print server was assigned more than
100 print queues. The first 100 are queued, the others
System Action: The host side of print exits, and the
are not queued.
NLM waits for the host to restart.
System Action: Subsequent print queues after the
first 100 are discarded. Processing continues normally
System Programmer Response: Verify that the print for the first 100 queues.
server name specified in the host start up is the desired
print server to use. If it is the correct name, determine
what printer utility is using the print server and unloaded System Programmer Response: Use EWXADMIN
it; check PSERVER first. DELPRTQ to delete some queues that are not needed.
This will allow the system to restart and pick up the new
Source: LANRES
queues. For details about the EWXADMIN DELPRTQ
command, see OS/390 LANRES Configuration Files
1205S Error returned using the AddINC and Commands.
function (RC=return-code).
Source: LANRES
Explanation: While trying to call the AddINC program,
an internal error was generated.

EWX Server Messages
1210E A shared print queue, printq, was 1213I Print job purged; empty file.
found.
Explanation: The print job specified to print contained
Explanation: The print server detected that the named no data to print.
print queue is configured in the NetWare bindery as a
System Action: Print job is discarded. Processing of
shared print queue. Shared print queue are not
jobs continues.
supported.
User Response: Do not send empty jobs to be printed
System Action: The shared print queue will not be
at the host.
serviced by EWXLHPRT.
Source: LANRES
System Programmer Response: Use either the
EWXADMIN RMVQSERV command on the host, or the
PCONSOLE utility on the NetWare console to disassociate 1214I Status_of_print_job
the shared print queue from all but one print server.
Then restart the LAN-to-host print connection(s) which Explanation: The status of the print job when sent to
received this error. For information on the EWXADMIN the host is returned through the use of a message that
RMVQSERV command, see see OS/390 LANRES the customer creates/modifies within the host user exits.
Configuration Files and Commands. Use PCONSOLE to The message from the host is displayed by this
display which print queues are associated with which message.
print servers. User Response: None.
Source: LANRES System Programmer Response: Create messages
that are self explanatory. The message will be truncated
1211I Queue queue_name not defined at the after 58 characters.
Host. Source: LANRES
Explanation: The queue specified in the NPRINT
command was not recognized by the Host service 1215I Cannot attach to queue queue.
machine.
Explanation: The queue specified associated with the
System Action: Processing of jobs for other queues print server specified during the start of the LAN to host
continues. print service machine cannot be attached to the
User Response: Use another print queue or contact EWXLHPRT.NLM.
your system programmer with the queue name to be System Action: The queue will not be monitored by
added to the LAN-to-host print configuration. LAN to host print.
System Programmer Response: Add the queue User Response: None.
name and corresponding data into the LAN-to-host print
configuration file, EWXLHPRT PROCS. System Programmer Response: Check the
parameters associated with the queue status by using
Source: LANRES PCONSOLE and modify if necessary.
Source: LANRES
1212I Print job sent to host; status unknown.
Explanation: A user exit processed the job, but no 1216I Could not translate print queue name,
message information was returned. The status of the queue.
print job is unknown. The job may or may not have
printed. This message is generated at the host print Explanation: The queue specified associated with the
service machine, and displayed at the client terminal. NPRINT command could not be translated correctly.
The LAN-to-host print service machine can not
System Action: Processing of jobs continues. determine which user exit to call.
User Response: None. System Action: The print job is not printed. The
System Programmer Response: Determine why the LAN-to-host print function continues to run.
user exit associated with the queue is not returning any User Response: None.
message information.
System Programmer Response: Verify the queue
Source: LANRES name is valid in terms of translating to EBCDIC. If
queue name is correct, check the translation routine.
Source: LANRES

EWX Server Messages
1217I Job status message could not be 1427E Error writing data into the print queue
translated. (RC=return-code).
Explanation: The message returned from the user exit Explanation: An I/O error was detected while trying to
stating the status of the print job could not be translated write the data into the NetWare print queue. This could
from EBCDIC to ASCII correctly, or the message be caused by a hardware problem on a disk or a
returned was longer than 57 bytes. NetWare system problem such as no disk space left.
System Action: The print job status is unknown. The System Action: The NLM closes the file and removes
LAN-to-host print function continues to run. the queue entry from the system. The NLM resets and
waits for the next request.
System Programmer Response: Verify the message
is not longer than 57 bytes and is valid in terms of System Programmer Response: If the problem
translating to ASCII. If the message is correct, check the persists, either the NLM should be unloaded or the host
translation routine. service machine should be stopped, or both should be
done. The cause of the problem should be determined.
Source: LANRES
When the problem is found, then the NLM should be
reloaded and the host service machine restarted.
1218I Error in user exit for queue queue.
Source: LANRES
Explanation: The user exit associated with the queue
returned a nonzero return code signifying that the user
1428E Cannot start the function function
exit did not process as expected.
(RC=return-code; message).
System Action: The print job is not printed. The
Explanation: EWXHLPRT.NLM tried to start the
LAN-to-host print function continues to run.
function indicated in the message as a separate
User Response: None. process in the NetWare server but the attempt failed.
The return code and, if available, an explanation for the
System Programmer Response: Determine why the error are displayed.
user exit is not executing properly.
Source: LANRES
1219W Print job in progress, abend possible if System Programmer Response: Retry the operation
unload continues. that failed. If the problem persists, look up the return
Explanation: The command UNLOAD EWXLHPRT
was entered on the NetWare console and Source: LANRES
EWXLHPRT.NLM is currently processing a print job.
Continuing to unload could cause the NetWare server
1429E Insufficient memory for internal print
processing to stop, print data to be lost, or both.
job information.
System Action: A continue with the unload command
Explanation: EWXHLPRT.NLM creates internal tables
prompt will be displayed.
to store information about file servers and print jobs.
User Response: Discontinue the unload command. This error message is displayed when the NLM cannot
obtain enough memory from the server to add to these
System Programmer Response: None. internal tables.
Source: LANRES System Action: The print job is cancelled and the
connection to the host is restarted.
1426I Host-to-LAN printing User Response: None.
Explanation: This is a data dictionary lookup. System Programmer Response: The host-to-LAN
User Response: None print program on the host should automatically
reconnect to the NLM and resubmit the print job. If the
System Programmer Response: None problem persists, free up server memory by unloading
Source: LANRES NLMs or add more memory to the server.
Source: LANRES

EWX Server Messages
1430W Insufficient memory to save 1433E Incorrect initialization packet received

information for querying host-to-LAN from the host.
print jobs.
Explanation: EWXHLPRT.NLM expected an
Explanation: The host-to-LAN print NLM cannot save initialization packet but did not receive one.
the information necessary for the EWXCONN QUERY
System Action: The connection to the host is
PRINT command.
restarted.
System Action: Processing continues. The print job
will print. The EWXCONN QUERY PRINT command will
not produce any status on the print job. System Programmer Response: The host-to-LAN
print program on the host should automatically
reconnect to the NLM and send another initialization
System Programmer Response: If other messages packet.
are being displayed because of the shortage on
Source: LANRES
memory, follow the direction associated with the other
messages or increase the memory on the NetWare
server. 1434E The host packet that was received is
too small.
Source: LANRES
Explanation: EWXHLPRT.NLM received a packet from
the host that did not contain all the required information
1431E Insufficient memory for number read
to be a valid packet.
buffer records.
System Action: The connection to the host is
Explanation: EWXHLPRT.NLM cannot obtain enough
restarted.
memory from the server to create an internal table
which is used to receive packets from the host. The User Response: None.
number of records for the internal table is taken from
the BUFFERS=number option or the default value. System Programmer Response: If the problem
persists, contact an IBM service representative.
System Action: The NLM is unloaded.
Source: LANRES
System Programmer Response: Load the NLM with 1435E All the thread groups have not ended.
a smaller number in the BUFFERS=number option. If
the problem persists, free up server memory by Explanation: EWXHLPRT.NLM is waiting for all the
unloading NLMs or add more memory to the server. separate processes to end before unloading or
restarting the connection to the host, but all the
Source: LANRES processes have not ended.
System Action: The NLM is unloaded which will force
1432E Insufficient memory for number thread all processes to end.
group records.
Explanation: EWXHLPRT.NLM cannot obtain enough
memory from the server to create an internal table System Programmer Response: If the problem
which is used to keep track of the separate processes persists, contact an IBM service representative.
started by the NLM. The number of processes is taken Source: LANRES
from the PROCESSES=number option or the default
value.
1436E Unknown host packet type number
System Action: The NLM is unloaded. received.
User Response: None. Explanation: EWXHLPRT.NLM does not recognize the
System Programmer Response: Load the NLM with type of the packet received from the host.
a smaller number in the PROCESSES=number option. System Action: The connection to the host is
If the problem persists, free up server memory by restarted.
unloading NLMs or add more memory to the server.
Source: LANRES
Source: LANRES

EWX Server Messages
Source: LANRES
1437W The list of file servers has been locked
the last number minutes.
1754E Incorrect value value given for
Explanation: EWXHLPRT.NLM is processing a lot of
DISK_SESSIONS.
work and is slow in responding to the task that issued
this message. The list of file servers is an internal list Explanation: An incorrect value was given for the
used by the NLM. This message may appear DISK_SESSIONS option when loading EWXDISK.
occasionally on a busy file server.
System Action: EWXDISK will unload.
System Action: The task continues to wait for the list
of file servers. User Response: None.
User Response: None. System Programmer Response: Specify a correct

value for DISK_SESSIONS. If a number is not specified,
System Programmer Response: If this message one additional EWXDISK session will be started.
appears frequently, contact an IBM service
representative. Source: LANRES
Source: LANRES
1755S Initialization failed because of a
session that was not valid.
1438W No receive buffer has been freed the
last minutes minutes. Explanation: A session number greater than the
allowed number of sessions was passed to the
Explanation: EWXHLPRT.NLM is processing a lot of communication layer during initialization.
work and is slow in processing the requests from the
host. Receive buffers are used internally by the NLM to System Action: The connection to the host is
read information from the host. This message may dropped.
appear occasionally on a busy file server. User Response: None.
System Action: The task continues to wait for a System Programmer Response: Determine what
receive buffer. application is causing the problem and correct it.
System Programmer Response: Increase the
BUFFERS value on the LOAD EWXHLPRT.NLM 1756E Unable to start connection.
command line. If this message still appears frequently,
contact an IBM service representative. Explanation: A EWXCMD START DISK command has
encountered an error while starting connection to the
Source: LANRES host for the disk driver. Other error messages
accompany this message.
1751E Incorrect value value given for System Action: No more sessions will be started.
DISKTIMEOUT.
Explanation: An incorrect value was given for the DT=
option when loading EWXDISK. System Programmer Response: If more sessions are
needed, determine the error from the other messages
System Action: EWXDISK will unload. and correct it. Enter the EWXCMD START DISK
User Response: None. command again.
System Programmer Response: Specify a value of 1 Source: LANRES

to 3600 for DT.
Source: LANRES 1757S Not enough memory to begin thread
(RC=return-code).
1753E Incorrect value value given for Explanation: Not enough memory was available to
IDLETIMEOUT. start a thread necessary for the disk driver to run.
Explanation: An incorrect value was given for the IT= System Action: The disk driver unloads.
option when loading EWXDISK. User Response: None.
System Action: EWXDISK will unload. System Programmer Response: Using the NetWare
User Response: None. MODULES command, determine what other programs
have already been loaded, and unload any that are not
System Programmer Response: Specify a value of 1 currently needed. Otherwise, add additional memory to
to 3600 for IT. the server.

EWX Server Messages
Source: LANRES
1761E Error in internal write routine
(RC=return-code).
1758E Not enough memory to begin thread
Explanation: A communications error occurred during
(RC=return-code).
the internal write routine. The host session may have
Explanation: A EWXCMD START DISK command has been stopped.
encountered an error. Not enough memory was
System Action: The session in which the error
available to start a thread that accepts connections from
occurred ends. The disk driver starts another session to
the host.
allow the host to reconnect.
System Action: No additional disk sessions will be
started.
System Programmer Response: Determine what is
causing the problem and correct it. The host side may
System Programmer Response: If more disk have been intentionally stopped or the communications
sessions are desired, use the NetWare MODULES link could have gone down.
command to determine what other programs have
Source: LANRES
already been loaded, and unload any that are not
currently needed. Otherwise, add additional memory to
the server. 1762E Not enough memory to get a buffer
(RC=return-code).
Source: LANRES
Explanation: The buffer request was denied because
there is not enough memory.
1759E Unrecognized command to disk
command routine. System Action: The disks are deleted for this session
and become not recognized by the server. The
Explanation: The disk command routine was not able
connection to the host is ended and the session
to recognize the parameter passed by EWXCMD.
becomes available for the next connection from the
System Action: The EWXCMD command request is host.
discarded. Suspect memory has been overwritten.
System Programmer Response: Using the NetWare
System Programmer Response: Determine which MODULES command, determine what other programs
NLM is causing the problem. have already been loaded, and unload any that are not
currently needed or add additional memory to the
Source: LANRES server. After adding more memory, restart the host
connection using the LANRES LINK command.
1760E Error in internal read routine Source: LANRES
(RC=return-code).
Explanation: A communications error occurred during 1763E Error initializing disks (RC=return-code).
the internal read routine. The host session may have
stopped. Explanation: An error occurred while starting a disk
image. If the return-code is -1, then the disk driver
System Action: The session in which the error thread could not start. If the return-code is 8, then the
occurred ends. The disk driver starts another session SetThreadGroupId API failed. Other messages will be
that accepts a connection from the host. The host can displayed with this.
then reconnect.
System Action: The disk image will not start and the
User Response: None. session will close.
System Programmer Response: Determine what is User Response: None.
causing the problem and correct it. The host side may
have been intentionally stopped or a communications System Programmer Response: If the return-code is
link could have gone down. -1, the NetWare server is probably running out of
memory. Unload unnecessary NLMs or add more
Source: LANRES memory to the server. If the return-code is 8, then follow
the directions from the other message displayed.
Source: LANRES

EWX Server Messages
1764E Incompatible version of NetWare. This 1765E Error on BeginThread call

program was built for execution on (ERRNO=errno).
NetWare Version
Explanation: During the execution of LANRES disk
Intended_NetWare_version but is being
serving, a call was made for the EWXCOMM NLM to
loaded on NetWare Version
begin a thread, via the NetWare BeginThread API, and
Actual_NetWare_version.
the API failed with an errno as indicated.
Explanation: There are two LANRES programs
System Action: The program continues operation.
provided by LANRES for disk serving. One is intended
for use on NetWare Version 3 and is named User Response: None.
EWXDISK3.DSK and the other is intended for use on
NetWare Version 4 and is named EWXDISK4.DSK. System Programmer Response: If the errno
Both programs are shipped on the LANRES diskette displayed is 5 then this indicates that the NetWare file
and the LANRES installation installs both into the server does not have enough memory. Using the
SYS:\EWXNLM subdirectory. The installation program NetWare MODULES command, determine which
also determines what version of NetWare is running on programs can be unloaded to free up memory.
the NetWare file server from which the LANRES Otherwise, add more memory to the server.
installation program is being invoked and copies the Source: LANRES
LANRES disk serving program that is compatible with
that version, to the SYS:\EWXNLM subdirectory as the
program named EWXDISK.DSK. Invoking the LANRES 5501E Insufficient memory available for
installation program from a NetWare 3.xx file server, number_of_sessions sessions.
three programs, EWXDISK3.DSK, EWXDISK4.DSK and Explanation: EWXCOMM detected an error while
EWXDISK.DSK are installed to the SYS:\EWXNLM trying to reserve memory for the number_of_sessions
subdirectory and the EWXDISK.DSK program is a copy that were to be initialized. This number was either
of the EWXDISK3.DSK program and must be loaded specified on the load command for EWXCOMM.NLM, in
only on NetWare version 3.xx file servers. Invoking the EWXCOMM.INI, or the default of 16.
LANRES installation program from a NetWare 4.xx file
server, three programs, EWXDISK3.DSK, System Action: The program unloads.
EWXDISK4.DSK and EWXDISK.DSK are installed to User Response: None.
the SYS:\EWXNLM subdirectory and the
EWXDISK.DSK program is a copy of the System Programmer Response: Determine if all of
EWXDISK4.DSK program and must be loaded only on the identified sessions are necessary, and if possible
NetWare version 4.xx file servers. This error message decrease the number of sessions. Using the NetWare
indicates that EWXDISK.DSK is being executed on a MODULES command, determine what other programs
NetWare file server that is running a different version have already been loaded and unload any that are not
from that which the LANRES installation program was currently needed. Otherwise, add additional memory to
invoked. the server.
System Action: The program is unloaded from the Source: LANRES
NetWare server.
User Response: None. 5503I Initializing TCP/IP.
System Programmer Response: Verify that the Explanation: EWXCOMM is performing TCP/IP
LANRES Disk Driver program is being loaded on a initialization.
version of NetWare that is supported by LANRES. See
System Action: EWXCOMM creates a socket and
the LANRES Licensed Program Specifications for
binds it to the LANRES well known port number.
details on the versions supported. If the NetWare
version is supported then determine what version of User Response: None.
NetWare is running on the NetWare file server that the
EWXDISK.DSK program is being loaded on. If it is
version 3.xx then copy the EWXDISK3.DSK file as the Source: LANRES
EWXDISK.DSK file and reissue the LOAD EWXDISK
command. If it is version 4.xx then copy the
EWXDISK4.DSK file as the EWXDISK.DSK file and 5504E Could not initialize TCP/IP
reissue the LOAD EWXDISK command. (RC=return-code).
Source: LANRES Explanation: The TCP/IP initialization failed with the

specified return value. Possible return values are:
1 Cannot create socket
2 Cannot bind socket

EWX Server Messages
3 Error occurred starting ListenTCPThread 1 Cannot declare resource
4 Unable to locate a port number. 3 Error occurred starting ListenPWSCSThread
System Action: EWXCOMM attempts to initialize the System Action: EWXCOMM attempts to initialize any
other communications options. If any of the other other communications options. If any of the other
communications options successfully initialize, then communication options successfully initialize, then
EWXCOMM continues to operate. If no other EWXCOMM continues to operate. If no other
communications options are successfully initialized, communication options are successfully initialized,
EWXCOMM exits. EWXCOMM exits.
System Programmer Response: Examine the System Programmer Response: Examine the
console to determine if any errors occurred in starting console to determine if any errors occurred in starting
TCP/IP. VM PWSCS. If the error code is 1, then EWXCOMM
v If TCP/IP is a necessary connectivity, unload was unable to be identified as the private resource
EWXCOMM, determine the problem, and correct it manager for the resource EWXCOMM. Verify no other
based on the return values, and then reload programs on this server have already identified this
EWXCOMM. resource using VM PWSCS Display/Configure.
v If the return value was 1, the server is probably Source: LANRES
running out of buffer space. Message
EWXCOM5522E will also be displayed with more
5509I Initialized PWSCS successfully.
information to help determine the problem.
v If the return value was 2, another application might Explanation: VM PWSCS communications code
be using LANRES’s well known port number, or successfully initialized.
TCP/IP has not closed up the port. It might be System Action: EWXCOMM continues
necessary to unload TCP/IP and restart it. Message communications initialization.
EWXCOM5523E will also be displayed with more
information to help determine the problem. User Response: None.
v If the return value was 3, there was not enough System Programmer Response: None.
memory to start a thread. Using the NetWare
MODULES command, determine what other Source: LANRES
programs have already been loaded, and unload any
that are not currently needed. Otherwise, add 5512E Error initializing NetWare for SAA
additional memory to the server. Message (RC=return-code).
EWXCOM5524E may also be displayed with this
message. Explanation: The NetWare CMLOGIN process
returned return-code, indicating a possible problem with
v If the return value was 4, verify that the well known
the NetWare for SAA side information file.
port address for LANRES has been added to the
\ETC\SERVICES file. System Action: EWXCOMM attempts to initialize
other communications options. If any of the other
Source: LANRES
communications options successfully initialize, then
EWXCOMM continues to operate. Otherwise,
5505I Initialized TCP/IP successfully. EWXCOMM exits.
Explanation: The TCP/IP communications code User Response: None.
successfully initialized.
System Programmer Response: Verify the NetWare
System Action: EWXCOMM continues for SAA side information file for EWXCOMM is correct.
communications initialization. Verify there are available SNA sessions for this LU on
the host connection being utilized. If sessions are not
available, modify the NetWare for SAA side information
System Programmer Response: None. file to increase the number of allowed sessions, or
unload the programs using the sessions.
Source: LANRES
Source: LANRES
5508E Could not initialize PWSCS

(RC=return-code).
Explanation: VM PWSCS initialization failed with the
specified return-code:

EWX Server Messages
5513I Initialized NetWare for SAA 5520E An error occurred processing

successfully. arguments (RC=return-code).
Explanation: The NetWare for SAA communications Explanation: An error occurred while processing the
code successfully initialized. EWXCOMM command line arguments or the LANRES
initialization file (the default name is EWXCOMM.INI).
System Action: EWXCOMM continues
communications initialization. System Action: EWXCOMM unloads.
System Programmer Response: None. System Programmer Response: Verify the command
arguments passed to EWXCOMM are valid and the
Source: LANRES
LANRES initialization file exists and can be found.
Examine the LANRES message log or the server
5516E Error initializing channel connection console for further information as to which arguments or
(RC=return-code). initialization values were incorrect.
Explanation: EWXCOMM could not initialize any of Source: LANRES

the identified subchannels.
System Action: If any of the other communications 5521I LANRES communications unloading.
options successfully initialized, then EWXCOMM
Explanation: EWXCOMM is unloading because of an
continues to operate. Otherwise, EWXCOMM exits. An
error.
return-code value of 3 indicates that no threads started
successfully. System Action: EWXCOMM unloads.
System Programmer Response: Use the previous System Programmer Response: Using the other
error messages for information as to which subchannel messages displayed, determine the error and correct
failed and take the appropriate action. the problem. Then reload EWXCOMM.
5517I Initialized channel connection 5522E TCP/IP socket command failed during
successfully. initialization (ERRNO=errno).
Explanation: The channel connections successfully Explanation: An error was encountered creating the
initialized. main socket. An errno of 55 indicates insufficient buffer
space.
System Action: EWXCOMM continues
communications initialization. System Action: This message may be displayed with
message EWXCOM5504E. TCP/IP connections are not
initialized, but EWXCOMM tries to initialize the other
System Programmer Response: None. connectivities. If any of the other connectivities
successfully initialize, EWXCOMM continues. Otherwise,
Source: LANRES EWXCOMM unloads.
5519E No communication drivers loaded or
initialized successfully. System Programmer Response: If TCP/IP
connectivity is necessary, unload EWXCOMM. Using
Explanation: EWXCOMM was unable to initialize the NetWare MODULES command, determine which
communications for any of the supported programs can be unloaded to free memory on the
communications types. server. Otherwise, add additional memory to the server.
System Action: EWXCOMM unloads. Then reload EWXCOMM.
System Programmer Response: Use the previous

error messages to determine what communications 5523E TCP/IP bind on port portnumber failed
types were unsuccessfully initialized and take the during initialization (ERRNO=errno).
necessary corrective action. Explanation: The TCP/IP bind call failed during
Source: LANRES initialization with errno:
9 Socket is already bound to another address

EWX Server Messages
48 Specified port is already in use (637 is the User Response: None.
LANRES port number).
49 Specified port is not available (637 is the \ETC\SERVICES file on the server for a LANRES entry.
LANRES port number). If it has not been added, add a line similar to the
following:
System Action: This message may be displayed with
message EWXCOM5504E. TCP/IP connections are not lanserver 637/tcp
initialized, but EWXCOMM tries to initialize the other Source: LANRES
connectivities. If any of the other connectivities
EWXCOMM unloads. 5526S Error accepting connection
(ERRNO=errno).
Explanation: The TCP/IP accept call failed because
System Programmer Response: If TCP/IP memory has been overwritten.
connectivity is necessary, unload EWXCOMM. Check
\ETC\SERVICES to ensure no other application is using System Action: The thread that listens for TCP/IP
the LANRES well known port number, 637. If another connection from the host has stopped. No TCP/IP
application is using the port number, change the port sessions can be started.
number for LANRES or the other application, and make User Response: None.
the corresponding changes on the host.
System Programmer Response: If TCP/IP is a
If LANRES is the only application using the port, then it needed connectivity, unload EWXCOMM and try to
is possible that TCP/IP has not cleaned up the socket. restart it.
Wait five minutes and reload EWXCOMM. This will give
TCP/IP a chance to clean up the socket. If this still does Source: LANRES
not work, unload the TCPIP.NLM and then restart
TCP/IP.
5527E function function is not available. Load
Source: LANRES the desired NLM.
Explanation: A host user tried to establish a
5524E Error starting TCP thread connection to a LANRES NLM and there is no function
(ERRNO=errno). of that type waiting for a connection. There are sessions
still available to accept more host connections, but the
Explanation: EWXCOMM could not start a thread, desired LANRES function is not available because
using a BeginThread call, because the server does not either the function is not loaded or all loaded copies are
have enough memory. in use by another host user.
System Action: This message may be displayed with System Action: The host connection fails, issuing an
message EWXCOM5504E. TCP/IP connections are not error message.
connectivities. If any of the other connectivities User Response: None.
System Programmer Response: Load the requested
EWXCOMM unloads.
LANRES NLM (EWXADMIN, EWXDIST, EWXDISK,
User Response: None. EWXHLPRT, or EWXLHPRT) so the user can attach to
it. If the EWXDISK is already loaded, add another
System Programmer Response: Using the NetWare session with EWXCMD START DISK 1.
MODULES command, determine which programs can
be unloaded to free up memory. Otherwise, add more Source: LANRES
memory to the server.
Source: LANRES 5528E No sessions were available to start
connection for function function.
5525E Unable to locate port number. Explanation: A host user tried to establish a
connection to a LANRES NLM, but there were no
Explanation: The LANRES well known port number sessions available to satisfy the request.
was not found in the \ETC\SERVICES file.
System Action: The host connection fails, issuing an
System Action: This message may be displayed with error message.
message EWXCOM5504E. TCP/IP connections are not
initialized, but EWXCOMM tries to initialize the other User Response: None.
System Programmer Response: Free up a session
by entering the LANRES DROP command from a host
EWXCOMM unloads.

EWX Server Messages
using the specified LANRES function, enter the
5532W Error queuing buffer for session
EWXADMIN TERM command from a user attached to
session (RC=return-code).
the administration function, or unload EWXADMIN,
EWXDIST, EWXDISK, EWXHLPRT, or EWXLHPRT. Explanation: An error occurred queuing the buffer.
System Action: The buffer was not queued. The
Attention: By entering the UNLOAD command at the
session is cleaned up and stops.
server console, ALL the NLMs by that name will be
unloaded. User Response: None.
Source: LANRES
5529E Error setting TCP/IP parameters
(ERRNO=errno).
5533E Host dropped connection during
Explanation: The setsockopt API failed. initialization.
System Action: TCP/IP communications does not Explanation: The host has stopped the connection.
start.
System Action: EWXCOMM continues to accept more
User Response: None. TCP/IP connections.
System Programmer Response: To use TCP/IP User Response: None.
communications, unload the LANRES NLMs and then
unload TCP/IP and restart it. Then reload the LANRES
NLMs. Source: LANRES
Source: LANRES
5535E Incorrect length sent. Cleaning up
session sessionnumber.
5530E Error starting TCP data thread
(ERRNO=errno). Explanation: During a TCP/IP read, the length sent
was greater than 4K.
Explanation: During a LANRES LINK, EWXCOMM
could not start a thread, using a BeginThread call, System Action: The session ends with the host and is
because the server does not have enough memory. cleaned up. The data received is discarded.
System Action: The host and the NLM are notified of User Response: None.
the error and the connection stops.
User Response: None. persists, contact an IBM service representative.
System Programmer Response: Using the NetWare Source: LANRES
MODULES command, determine which programs can
be unloaded to free up memory. Otherwise, add more
memory to the server. 5536S TCP/IP error on read for session
sessionnumber (ERRNO=errno).
Source: LANRES
Explanation: An error was returned on a TCP/IP read
for session sessionnumber.
5531E TCP/IP error from a read call
(ERRNO=errno). System Action: The session is stopped.
Explanation: An error occurred during the TCP/IP User Response: None.

read call. System Programmer Response: The connection can
System Action: EWXCOMM continues to accept more be restarted and the data move can be retried. If the
TCP/IP connections. problem persists, contact an IBM service representative.

5537W EOF received on TCP/IP read for
Source: LANRES session sessionnumber.
Explanation: The socket was closed causing the
TCP/IP connection to receive an EOF.
System Action: The session sessionnumber is
stopped.

EWX Server Messages
5540E reSetThreadGroupID failed
System Programmer Response: The connection may (RC=return-code).
be restarted.
Explanation: The NetWare API SetThreadGroupID
Source: LANRES failed to reset the thread group ID back to the original
ID. Memory may have been corrupted.
5538E Error starting PWSCS thread System Action: EWXCOMM continues. LANRES
(ERRNO=errno). function may terminate.
Explanation: EWXCOMM could not start the thread, User Response: None.
from the BeginThread call, because the server does
System Programmer Response: If memory
not have enough memory.
corruption is suspected, contact an IBM service
System Action: PWSCS connections are not representative and report the return code.
Source: LANRES
EWXCOMM unloads. 5541W An error occurred while closing
session session (RC=return-code).
Explanation: An error occurred when one of the
System Programmer Response: If PWSCS
LANRES functions closed a session.
connectivity is needed, unload EWXCOMM. Using the
NetWare MODULES command, determine which System Action: EWXCOMM continues.
programs can be unloaded to free up memory.
Otherwise, add more memory to the server.
Source: LANRES
Source: LANRES
5539E Error declaring PWSCS
CPI-Communications resource 5542E Error sending data (RC=return-code).
(RC=return-code).
Explanation: An error occurred sending data to the
Explanation: An error occurred declaring EWXCOMM host with VM PWSCS or NetWare for SAA. The
as a resource manager. The return-code is the return return-code is the return code from the
code from the PWSCS call. CPI-Communications CMSEND call. This message
could be displayed with either EWXCOM5527 or
System Action: PWSCS connections are not
EWXCOM5528.
connectivities. If any of the other connectivities System Action: The host does not get the error, but
successfully initialize, EWXCOMM continues. Otherwise, the conversation is closed as part of routine clean up.
EWXCOMM unloads.
System Programmer Response: Use the return code
System Programmer Response: If the return-code is: to determine the problem.
20 Use the PWSCS Display Configure Utility to 17 The host application has ended abnormally.
examine the log file. If the resource table has The host has deallocated the conversation.
overflowed, then increase the resources Correct the host problem and restart the host
permitted by modifying the value in the application.
PWSCS ACPI.INI file. The new value will take
effect when LANRES is restarted. 20 For PWSCS, use the PWSCS Display
Configure Utility to examine the Log to
28 Another application has already declared this determine the problem. For NetWare for SAA,
resource. Determine which application has the examine the NetWare for SAA console to
resource and remove that application. determine the problem.

EWX Server Messages
5543E Error deallocating conversation
(RC=return-code). System Programmer Response: Correct the host
error, and restart the host application.
Explanation: The CPI-Communications CMDEAL call
failed. Source: LANRES
System Action: The conversation is not cleaned up.
5548E Error setting deallocation type
(RC=return-code).
System Programmer Response: The conversation
Explanation: The CPI-Communications CMSDT call
has already been cleaned up or the conversation
has received an error.
cannot be cleaned up. The next time the system is
restarted the conversation will be cleaned up. System Action: The conversation is not cleaned up.
System Programmer Response: The system will still
5544E Error receiving data (RC=return-code). be usable, but the conversation will not be cleaned up
until the next time LANRES is restarted. If the problem
Explanation: An error occurred receiving data from
the host while using VM PWSCS or NetWare for SAA.
The return-code is the return code from the Source: LANRES
CPI-Communications CMRCV call.
System Action: The error is returned to the LANRES 5549E Unexpected event: event
NLM that is using this conversation. The conversation is
cleaned up. The LANRES NLM may unload or restart. Explanation: The CPI-Communications XCWOE call
has received an unexpected event.
System Action: The PWSCS connectivity thread will
System Programmer Response: If the return code is: end.
17 The host application has ended abnormally. User Response: None.
Correct the host problem and restart the host
application. System Programmer Response: Contact an service
representative.
20 For PWSCS, use the PWSCS Display
Configure Utility to examine the Log to Source: LANRES
determine the problem. For NetWare for SAA,
examine the NetWare for SAA console to 5550E Error wait on event failed
determine the problem. (RC=return-code).
Source: LANRES Explanation: The CPI-Communications XCWOE call
has failed.
5545E Error accepting conversation System Action: The PWSCS connectivity thread
(RC=return-code). stops.
Explanation: An error has occurred on the User Response: None.
CPI-Communications CMACCP call.
System Programmer Response: Contact an IBM
System Action: EWXCOMM keeps issuing CMACCP, service representative.
trying to accept a conversation from the host.
Source: LANRES
System Programmer Response: Contact an IBM 5551E Error starting NetWare for SAA listen
service representative. thread (RC=return-code).
Source: LANRES Explanation: The BeginThread call failed because of
lack of storage.
5546E Partner abnormally stopped. System Action: NetWare for SAA connections is not
Explanation: The host application has ended initialized, but EWXCOMM tries to initialize the other
abnormally. connectivities. If any of the other connectivities
System Action: The CPI-Communications CMRCV EWXCOMM unloads.
call received a status indicating the host application has
abnormally stopped. User Response: None.

EWX Server Messages
System Programmer Response: If NetWare for SAA
5557E Error starting channel thread on
connectivity is needed, unload EWXCOMM. Using the
subchannel subchannel for type adapter
NetWare MODULES command, determine which
adapter. Thread not started
programs can be unloaded to free up memory.
(RC=return-code).
Otherwise, add more memory to the server.
Explanation: The thread that accepts data from the
Source: LANRES
host could not start because there was not enough
memory. The subchannel is the even subchannel for the
5552E Error declaring NetWare for SAA subchannel pair on type adapter adapter.
CPI-Communications resource
System Action: The session is no longer valid and
(RC=return-code).
the connection is dropped and restarted.
Explanation: An error occurred declaring EWXCOMM
as a resource manager. The return-code is the return
code from the CMSLTP call. System Programmer Response: Using the NetWare
MODULES command, determine what other programs
System Action: NetWare for SAA connections are not
have already been loaded and unload any that are not
currently needed. Otherwise, add additional memory to
connectivities. If none of the other connectivities
the server.
successfully initialize, EWXCOMM unloads; otherwise it
continues. Source: LANRES
5558I No subchannels were started.
System Programmer Response: If the return-code is
20, examine the NetWare for SAA console for errors. Explanation: The communications layer was unable to
start a subchannel. This could be because no
Source: LANRES
subchannels were specified in the EWXCOMM.INI file
or on the LOAD command for EWXCOMM. Otherwise,
5554E Error starting NetWare for SAA receive other messages will be issued to determine the
thread (ERRNO=errno). problem.
Explanation: EWXCOMM could not start the thread, System Action: EWXCOMM attempts to initialize
using the BeginThread call, because the server does other communications options. If any of the other
not have enough memory. communications options successfully initialize, then
EWXCOMM continues. Otherwise, EWXCOMM unloads.
System Action: The host is notified and the
connection is severed. EWXCOMM continues. User Response: None.
User Response: None. System Programmer Response: If subchannel

communication is necessary, use the error messages to
System Programmer Response: If this NetWare for determine what the problem is. Verify the
SAA connection is needed, unload EWXCOMM. Using EWXCOMM.INI file has the correct even subchannel
the NetWare MODULES command, determine what and corresponding adapter identified on the
other programs have already been loaded and unload “subchannel=” line. Check the adapter configuration file
any that are not currently needed. If freeing memory (PSCA1.CFG or PSCA2.CFG) to ensure the list of ALL
does not solve the problem, then add additional memory the subchannels used (even and odd) for LANRES are
to the server. in the file.
5555E Error: incorrect session number. 5559E ReadHandle could not be opened for
Explanation: The host has passed a session number subchannel subchannel on type adapter
that is not valid to the server during connection adapter (RC=return-code).
initialization. Explanation: A read subchannel could not be opened
System Action: The connection used to pass the because all the subchannel handles are currently in
incorrect session number is deallocated. use. The MMC card has a limit of 128 simultaneous
subchannels in use per adapter. The subchannel
User Response: None. subchannel specified is the even (read) subchannel of
System Programmer Response: Contact an IBM the subchannel pair on type adapter adapter.
service representative. System Action: The subchannel pair specified does
Source: LANRES not accept connections, but this does not effect the

EWX Server Messages
other pairs that initialize successfully nor the other System Action: The subchannels are closed and the
connectivities. session is stopped.
System Programmer Response: Determine what System Programmer Response: If the error persists,
subchannel pairs on the adapter are not needed and contact an service representative.
update the EWXCOMM.INI accordingly. Use EWXCMD
Source: LANRES
DELETE to remove subchannels and EWXCMD ADD to
add subchannels to be used. If more than 128
subchannels are needed, add another adapter. 5563E Could not assign READ handle during
initialization, subchannel subchannel on
Source: LANRES
type adapter adapter (RC=return-code).
Explanation: An error occurred during initialization on
5560E WriteHandle could not be opened for
the read subchannel. Other messages may be
subchannel subchannel on type adapter
displayed with this message.
adapter (RC=return-code).
System Action: The subchannel pair does not
Explanation: A write subchannel could not be opened
complete initialization. EWXCOMM continues initializing
because all the subchannel handles are currently in
other subchannels and the other communication
use. The MMC card has a limit of 128 simultaneous
options. If none successfully initialize, EWXCOMM
subchannels in use per adapter. The subchannel
unloads.
subchannel specified is the odd (write) subchannel of
the subchannel pair on type adapter adapter. User Response: None.
System Action: The subchannel pair specified does System Programmer Response: Try to reopen the
not accept connections, but this does not effect the subchannel by using the EWXCMD ADD command.
other pairs that initialize successfully nor the other
connectivities. Source: LANRES

5564E Could not assign WRITE handle during
System Programmer Response: Determine what initialization, subchannel subchannel on
subchannel pairs on the adapter are not needed and type adapter adapter (RC=return-code).
update the EWXCOMM.INI accordingly. Use EWXCMD
DELETE to remove subchannels and EWXCMD ADD to Explanation: An error occurred during initialization on
add subchannels to be used. If more than 128 the write subchannel. Other messages may occur with a
subchannels are needed, add another adapter. more detailed explanation of the error.
Source: LANRES System Action: The subchannel pair does not

complete initialization. EWXCOMM continues initializing
other subchannels and the other communication
5561E Error return code from adapter status options. If none successfully initialize, EWXCOMM
for subchannel subchannel on type unloads.
adapter adapter (RC=return-code).
Explanation: An error occurred querying the status of
the type adapter card. System Programmer Response: Try to reopen the
subchannel by using the EWXCMD ADD command.
System Action: The subchannel is closed and made
not available for use by LANRES. Source: LANRES

5565E Could not set extended mode during
System Programmer Response: Try to reopen the initialization, subchannel subchannel on
subchannel by using the EWXCMD ADD command. type adapter adapter (RC=return-code).
Source: LANRES Explanation: An error occurred during subchannel
initialization.
5562E Adapter error opening the subchannel System Action: The subchannel pair does not
subchannel. Command complete initialization. EWXCOMM continues initializing
code=command_code (RC=return-code). other subchannels and the other communication
options. If none successfully initialize, EWXCOMM
Explanation: An adapter error occurred while
unloads.
initializing the subchannel pair subchannel. Status was
taken from the MMC and returned the command code. User Response: None.

EWX Server Messages
System Programmer Response: Try to reopen the System Action: The connection for the MMC stops
subchannel by using the EWXCMD ADD command. and the subchannels close.
System Programmer Response: To make the
5566I Host encountered an error during subchannels available again, use the EWXCMD ADD
initialization for subchannel subchannel command.
on type adapter adapter
Source: LANRES
(RC=return-code).
Explanation: The host encountered an error and
5571E Error sending initialization information
closed the subchannel connection.
to host (RC=return-code).
System Action: EWXCOMM will clean up the
Explanation: The host has ended the channel
connection and then prepare to accept another
connection (either normally or abnormally).
subchannel connection.
System Action: EWXCOMM restarts the subchannels
and accepts another connection.
System Programmer Response: Restart the host
connection using the EWXCONN LINK command.
System Programmer Response: Determine what
Source: LANRES
error occurred on the host and restart the host side
using the EWXCONN LINK command.
5567E Adapter error reading for function
Source: LANRES
(RC=return-code).
Explanation: An error occurred on the MMC adapter.
5572E Adapter error sending initialization
This message is issued with other messages.
information (RC=return-code).
System Action: The connection for the MMC stops
Explanation: An error occurred on the MMC adapter
and the subchannels close.
while sending initialization information to the host. Other
User Response: None. messages explaining the cause of the error in more
detail will be displayed with this message.
subchannels available again, use the EWXCMD ADD System Action: The connection with the host is
command. stopped and the subchannels are closed.
System Programmer Response: Using the other
5568E Error reading initialization information messages, determine what caused the error and correct
from host (RC=return-code). it. Use the EWXCMD ADD command to reopen the
subchannels and restart the host side using the
Explanation: An error occurred reading initialization
EWXCONN LINK command.
information from the host on an MMC connection. This
message is displayed with message EWXCOM5569I, Source: LANRES
which will indicate what subchannels had the error.
System Action: The connection for the MMC stops 5573E Error sending return code to host
and the subchannels close. (RC=return-code).
User Response: None. Explanation: An error occurred sending the
initialization information to the host. The return codes
are:
subchannels available again, use the EWXCMD ADD
command. 119 The MMC adapter did not have resources to
complete request
Source: LANRES
122 The MMC adapter did not have available
buffers to send data
5569I Subchannel pair at subchannel on type
adapter adapter have not been brought 130 The MMC adapter did not have available
on-line. buffers to send a command
Explanation: This message is displayed with message System Action: The EWXCOMM retry count has been
EWXCOM5568E to identify the subchannels in error. exhausted trying to send information to the host. The
MMC connection and the subchannels are closed.

EWX Server Messages
5577E Adapter error occurred on the read.
System Programmer Response: Use EWXCMD ADD Command code=command_code
to make the subchannels available. (RC=return-code).
Source: LANRES Explanation: Status was taken from the MMC and
returned the command code. This message may occur
with other related messages.
5574E Error reading data from host for
session number session System Action: The subchannels are closed and the
(RC=return-code). session is stopped.
Explanation: An error occurred reading data using User Response: None.

MMC.
System Action: The session stops. If the return-code contact an service IBM representative to report the
is 12, the subchannels are closed. Otherwise, the command code.
subchannels are reset and made ready to accept a
Source: LANRES
connection from the host.
5578E Adapter error occurred on the write.
System Programmer Response: If the return-code is Command code=command_code
12, then use the EWXCMD ADD command to add the (RC=return-code).
subchannels back on line. Use the EWXCONN LINK
Explanation: Status was taken from the MMC and
command to restart the host.
returned the command code. This message may occur
Source: LANRES with other related messages.
System Action: The subchannels are closed and the
5575E Error waiting for data from host session is stopped.
(RC=return-code).
Explanation: EWXCOMM was waiting for data from
the host when an MMC adapter error occurred on the
contact an IBM service representative to report the
connection.
command code.
System Action: Status is taken on the adapter to
Source: LANRES
determine the error. The subchannels are closed and
the session is stopped. This message may occur with
other messages. 5579S SetThreadGroupID failed
(RC=return-code).
Explanation: The NetWare API SetThreadGroupID
System Programmer Response: Use the other
failed to set the current thread group ID to
messages to determine the error. After fixing the
EWXCOMM’s ID. Memory has been corrupted.
problem, use EWXCMD ADD to bring the subchannels
back on-line. System Action: EWXCOMM continues. The LANRES
function may terminate. Unpredictable results could
Source: LANRES
occur.
5576E Error querying adapter status
(RC=return-code). System Programmer Response: DOWN the server
and restart it. If the problem persists, contact an IBM
Explanation: An error occurred while trying to obtain
service representative with the return code.
status from the MMC adapter. This message may occur
with other related messages. Source: LANRES
System Action: The subchannels are closed and the
session is stopped. 5580E Adapter error sending EOF to host
(RC=return-code).
Explanation: EWXCOMM was restarting the
System Programmer Response: Use EWXCMD ADD
connection to the host by sending an EOF on the
to add the subchannels.
subchannel, but an error occurred.
Source: LANRES
System Action: The connection does not restart.
Status is taken on the MMC, and the subchannels are
closed.

EWX Server Messages
5584W Host ended session session with
System Programmer Response: Determine the error connection.
from the other messages and correct it. Use EWXCMD
Explanation: The host stopped the session with
ADD to restart the subchannels after the problem has
EWXCOMM.
been corrected.
System Action: The connection is broken and the
Source: LANRES
session is cleaned up. The LANRES function using this
session tries to accept another connection.
5581E Error restarting channel thread on
subchannel subchannel for type adapter
adapter (RC=return-code). System Programmer Response: None.
Explanation: EWXCOMM could not restart the Source: LANRES
connection because of a channel error.
System Action: EWXCOMM made an attempt to 5586S An error occurred on TCP/IP write for
communicate to the host, but failed. The connection session session (RC=return-code).
stops and the subchannels are closed.
Explanation: A TCP/IP write error occurred. Suspect
User Response: None. memory corruption.
System Programmer Response: Use EWXCMD ADD System Action: The connection is stopped and the
to restart the subchannels. session is cleaned up.
System Programmer Response: Contact an IBM
5582E Open received bad status service representative.
(RC=return-code).
Source: LANRES
Explanation: A LANRES function (EWXADMIN,
EWXDISK, EWXDIST, EWXHLPRT, or EWXLHPRT)
5587E Error on adapter sending data on
tried to start a connection with the host, but failed. This
subchannel subchannel on type adapter
message may occur with other error messages.
adapter (RC=return-code).
System Action: No connection is made to the host
Explanation: Channel adapter encountered an error.
and the session is cleaned up. The LANRES functions
try to restart the connection. System Action: Status is taken from the channel
adapter. Other related messages are displayed.
System Programmer Response: Determine the
Source: LANRES
cause of the problem from the other messages.
Source: LANRES
5583W Bad status was returned to read for
session session, status=status.
5588E An error occurred on channel write for
Explanation: This could be caused by one of the
LANRES functions dropping the connection from the
host by issuing a EWXCONN DROP or EWXCONN Explanation: An error occurred sending the data to
LINK command. If an error occurred, other error the host. The return codes are:
messages will be displayed.
119 The MMC adapter did not have resources to
System Action: The connection to the host is broken complete request
and the session is cleaned up.
122 The MMC adapter did not have available
User Response: None. buffers to send data
System Programmer Response: If an error did occur, 130 The MMC adapter did not have available
examine the LANRES message log for other errors to buffers to send a command
determine what happened.
System Action: The EWXCOMM retry count has been
Source: LANRES exhausted trying to send the information to the host.
The MMC connection and the subchannels are closed.

EWX Server Messages
System Programmer Response: Use EWXCMD ADD
5595W Incorrect address for FreeBuf.
to make the subchannels available.
Explanation: FreeBuf was told to deallocate a buffer
Source: LANRES
with a 0 address.
System Action: The request is denied.
5589E An error occurred on NetWare for SAA
write for session session User Response: None.
(RC=return-code).
System Programmer Response: If this continues and
Explanation: The CPI-Communications CMSEND call the NetWare server runs out of memory, contact an IBM
failed. service representative.
System Action: The connection to the host is cleaned Source: LANRES
up.
User Response: None. 5597E Error closing listening socket
(RC=return-code).
System Programmer Response: Use the return code
to determine the problem. Explanation: When unloading EWXCOMM, an error
occurred closing the TCP/IP socket that accepts
17 The host application has ended abnormally.
incoming connections from the host during unload time.
The host has deallocated the conversation.
Correct the host problem and restart the host System Action: EWXCOMM unloads.
application.
20 Examine the NetWare for SAA console to
System Programmer Response: If trouble occurs
determine the problem.
loading EWXCOMM, unload TCPIP NLM and restart
Source: LANRES TCP/IP.
Source: LANRES
5590E An error occurred on PWSCS write for
5598E Error starting channel thread on
Explanation: The CPI-Communications CMSEND call subchannel subchannel for type adapter
failed. adapter. Thread not started
(RC=return-code).
System Action: The connection to the host is cleaned
up. Explanation: A command, like EWXCMD ADD,
encountered an error starting a channel thread to
accept connections on the subchannel because there
System Programmer Response: Use the return code was not enough memory.
to determine the problem.
System Action: EWXCMD continues and unloads
17 The host application has ended abnormally. when finished.
The host has deallocated the conversation.
Correct the host problem and restart the host
application. System Programmer Response: Using the NetWare
20 Use the VM PWSCS Display Configure Utility
have already been loaded and unload any that are not
to examine the Log to determine the problem.
currently needed. Or, add additional memory to the
Source: LANRES server.
Source: LANRES
5592W Channel pair for subchannel
subchannel on type adapter adapter not
5599E Subchannel subchannel on type adapter
found when closing (RC=return-code).
adapter is not active.
Explanation: While closing a session, the subchannel
Explanation: This may occur after entering the
was not found in the control block structure.
EWXCMD DELETE command. The subchannel being
System Action: The NLM continues to clean up the deleted is not being used by LANRES.
session.
System Action: The subchannel is not deleted.
System Programmer Response: Verify the correct
Source: LANRES subchannel was specified.

EWX Server Messages
Source: LANRES System Programmer Response: Load the program
5600E Unable to open message repository
<name> (RC=return-code). Source: LANRES
Explanation: EWXCOMM was unable to open the
indicated message repository. 5604E The log file’s full directory name will
be too long.
System Action: EWXCOMM unloads.
Explanation: The directory name, which includes the
volume name, for the log file cannot be greater than
System Programmer Response: Verify the identified 254 characters in length.
message repository is in the LANRES installation
directory. If the repository is not there, copy the
NetWare server.
repository from the EWXNLM directory of the LANRES
installation diskette. If the repository is in the LANRES User Response: None.
installation directory, examine the console for other
messages that may suggest why the message
repository did not open.
Source: LANRES
Source: LANRES
5601E Duplicate subchannel subchannel

5605W Unable to begin thread to process log
specified.
files. Messages will still be recorded.
Explanation: The same subchannel address was
Explanation: The communications driver tried to start
specified more than once on the command line.
a separate thread to process the log files, but failed. A
System Action: The program is unloaded from the possible cause is the lack of server memory to start a
NetWare server. new thread.
User Response: None. System Action: Log files are not processed at
midnight, but messages continue to be recorded in the
current log file.
OS/390 LANRES Configuration Files and Commands. User Response: None.
Source: LANRES System Programmer Response: Load the
communications driver again. If the problem persists,
free up server memory by unloading NLMs or add
5602E Odd subchannel subchannel specified.
system memory to the server.
Explanation: The subchannel address specified on
Source: LANRES
the command line must be a two digit hexadecimal
number that corresponds to the even subchannel
address of a read/write address pair. 5606E Cannot find or open an initialization
file. Communications driver will be
unloaded.
NetWare server.
Explanation: The initialization file is required by the
communications driver. The communications driver
System Programmer Response: Load the program reads the file to set default values for certain program
using the correct syntax. For syntax information, see parameters.
Source: LANRES NetWare server.
5603E Incorrect adapter number number
System Programmer Response: Use the INIT_FILE
specified.
parameter on the command to specify the location of
Explanation: The adapter number must be 1 or 2. the initialization file, or create a default initialization file.
The default file name should be EWXCOMM.INI and the
System Action: The program is unloaded from the file should be located in the directory that the program
NetWare server. is loaded from or in the SYS:\EWXNLM directory.

EWX Server Messages
5607W Line number of initialization file 5611W Keyword keyword in line number of
filename is too long. Line will not be initialization file filename has an
used. incorrect value. Line will not be used.
Explanation: Lines in the initialization file, except Explanation: A value was assigned to the keyword
comments, are limited to 500 characters in length. listed in the message, but it is not an acceptable value
for the keyword.
initialization file filename. System Programmer Response: Correct the
initialization file filename.
Source: LANRES
Source: LANRES
5608W Line number of initialization file
filename has an incorrect format. Line 5612W Value missing for keyword keyword in
will not be used. line number of initialization file filename.
Line will not be used.
Explanation: Lines in the initialization file must follow
a specific format. For more information about the Explanation: The specified keyword in the initialization
EWXCOMM.INI file, see OS/390 LANRES Configuration file requires a value be associated with it.
Files and Commands.
System Programmer Response: Correct the initialization file filename.
Source: LANRES
Source: LANRES
5613W One or more incorrect subchannel
5609W Duplicate keyword keyword in line addresses were found in line number of
number of initialization file filename. initialization file filename. The incorrect
Previous value is replaced. subchannel addresses were not used.
Explanation: A duplicate keyword is found in the Explanation: One or more values specified in the
initialization file. Values from keywords lower in the file SUBCHANNEL line of the initialization file were
will replace values from keywords higher in the file. incorrect. The incorrect values were discarded, but the
correct values will still be used. Possible causes of this
System Action: The previous keyword value is
message are:
replaced.
v The subchannel address was not a two digit
User Response: None. hexadecimal number.
System Programmer Response: Correct the v The subchannel address was not an even
initialization file filename by deleting one of the duplicate subchannel address.
keywords. v The subchannel address was a duplicate of a
Source: LANRES previous subchannel address on the same line or a
previous line.
v The adapter number was not 1 or 2.
5610W Incorrect keyword keyword in line
number of initialization file filename. v An extra semicolon was encountered after the last
Line will not be used. subchannel address.
Explanation: A keyword in the initialization file is not System Action: The incorrect subchannel addresses
recognized. are bypassed. Other subchannel addresses on the
same line are used.
System Programmer Response: Correct the initialization file filename.
Source: LANRES
Source: LANRES

EWX Server Messages
5617W Unable to close initialization file 5621W Unable to open current log file
filename. filename.
Explanation: An attempt to close the initialization file Explanation: An attempt to archive the current log file
failed. or record messages to it failed because the file cannot
be opened. The file may be opened or locked by
System Action: The initialization file remains open.
another process.
The program continues.
System Programmer Response: Unloading the
communications driver and loading it may be required to System Programmer Response: Unload and reload
access the initialization file. the communications driver if necessary.
5618W Unable to delete file filename. 5622W Unable to open archived log file
filename.
Explanation: An attempt to delete the file listed in the
message failed. The file may be opened or locked by Explanation: An attempt to archive the current log file
another process. failed because the archived log file listed in the
message cannot be opened. The file may be opened or
locked by another process.
System Programmer Response: Try to delete the
specified file from a NetWare client or with the LANRES
data distribution function. System Programmer Response: Unload and reload
the communications driver if necessary.
Source: LANRES
Source: LANRES
5619W Reason for failure: error.
5623W Unable to archive current log file
Explanation: This message is displayed with other
filename.
messages to explain a failure.
Explanation: An attempt to append the current log file
to the appropriate archived log file failed.
System Programmer Response: Use this message
to determine the cause of the error listed in the other
error message. System Programmer Response: Unload and reload
the communications driver if necessary. Delete or
Source: LANRES
archive the current log file with a NetWare client or with
the LANRES Distribution function.
5620W Out of space on volume to archive
Source: LANRES
current log file filename.
Explanation: The current log file cannot be archived
5624W Unable to open log directory directory.
because there is no space to create the archive log file.
Explanation: Archived log files cannot be deleted
because the attempt to open the log directory directory
User Response: None. failed.
System Programmer Response: Free up space on System Action: Processing continues.
the volume by deleting old files, or add more space to
the volume.
System Programmer Response: Unload and reload
Source: LANRES
the communications driver if necessary. Delete the
archived log files with a NetWare client or with the
LANRES Distribution function.
Source: LANRES

EWX Server Messages
host the subchannel is known as 25A, specify 5A as the
5625W Unable to close log directory directory.
subchannel. The subchannel must also be in the
Explanation: An attempt to close the log directory channel adapter’s configuration file (for example,
directory failed. PSCA1.CFG, PSCA2.CFG, or NSCA1.CFG). See the
for more information on these files.
Source: LANRES
System Programmer Response: Unload and reload
the communications driver.
6254E Subchannel number missing from load
Source: LANRES statement.
Explanation: No subchannel number was specified on
5626I Log file started on server server. the LOAD EWXLSA command.
Explanation: This message is recorded in the current System Action: EWXLSA unloads.
log file to indicate which server the log file is from.
System Programmer Response: Specify the
User Response: None. ″Subchannel=subchannel″ parameter on the LOAD
EWXLSA command, where subchannel is the
System Programmer Response: None. subchannel number. Refer to OS/390 LANRES
Source: LANRES Configuration Files and Commands for the correct
format of the LOAD EWXLSA command.
5811I {Add|Delete} available for subchannel Source: LANRES

subchannel. Waiting for function.
Explanation: The requested connection is available, 6255E Adapter type missing from load
and waiting for the associated function NLM to load. statement.
System Action: None. Explanation: The channel adapter type was not
specified on the LOAD EWXLSA command and is
User Response: Load the required NLM. needed.
System Programmer Response: None. System Action: EWXLSA unloads.
System Programmer Response: EWXLSA cannot
6252E Incorrect parameter specified. determine which adapter to use. Specify the
Explanation: An incorrect parameter was specified ″Adapter=adapt_type″ parameter on the LOAD
when loading EWXLSA. EWXLSA command, where adapt_type is either MMC1,
MMC2, or ESCON. Refer to OS/390 LANRES
System Action: EWXLSA unloads. Configuration Files and Commands for the correct
User Response: None. format of the LOAD EWXLSA command.
System Programmer Response: Verify the load Source: LANRES

command is specified correctly. Refer to OS/390
LANRES Configuration Files and Commands for the 6256E Too many parameters specified on
correct format of the LOAD EWXLSA command. load statement.
Source: LANRES Explanation: Two subchannels and one adapter type
can be specified on the load command.
6253E Invalid subchannel specified. System Action: EWXLSA unloads.
Explanation: The subchannel on the LOAD EWXLSA User Response: None.
command was not valid.
System Programmer Response: Correct the LOAD
System Action: EWXLSA unloads. EWXLSA command. Refer to OS/390 LANRES
User Response: None. Configuration Files and Commands for the correct
System Programmer Response: Verify the correct
subchannel was specified. The subchannel is the last Source: LANRES
two digits of the host subchannel. For example, if on the

EWX Server Messages
Source: LANRES
6257E Subchannel number out of range.
Explanation: The subchannel number is out range for
6261E Subchannel assign failed
the channel adapter. The MMC adapter cannot use
(RC=return-code).
subchannel 0xFF. The ESCON adapter cannot use
0xFE and 0xFF. Explanation: EWXLSA could not assign the
subchannel.
System Action: EWXLSA unloads.
System Action: EWXLSA unloads.
System Programmer Response: Use a subchannel
other than 0xFF or 0xFE depending on the adapter System Programmer Response: Verify the
type. subchannel is not being used by another application. If
the subchannel is free, unload and reload the channel
Source: LANRES
adapter driver. If this does not work DOWN, then restart
the server. Then restart the channel adapter. If the
6258E Adapter type is not recognized. problem persists, contact an IBM service representative
and report the return code, return-code.
Explanation: The adapter type specified on the LOAD
EWXLSA was not an accepted value. The acceptable Source: LANRES
values are MMC1, MMC2, and ESCON.
System Action: EWXLSA unloads. 6262E Not enough resources available to
allocate buffer.
Explanation: EWXLSA tried to allocate a buffer, but
System Programmer Response: Correct the LOAD
there was not enough resources.
EWXLSA line with the correct adapter type. Refer to
OS/390 LANRES Configuration Files and Commands System Action: EWXLSA unloads.
for the correct format of the LOAD EWXLSA command.
Source: LANRES
System Programmer Response: The NetWare server
may be running out of memory. Unload unnecessary
6259E Connection to adapter_type adapter NLMs or add more memory to the server.
could not be opened (RC=return-code).
Source: LANRES
Explanation: The adapter, adapter_type could not be
opened.
6263E Error receiving command command on
System Action: EWXLSA unloads. the channel (RC=return-code).
User Response: None. Explanation: EWXLSA did not receive the expected
command command from VTAM,
System Programmer Response: Verify the adapter
specified matches the one installed in the server. If the System Action: EWXLSA unloads.
specified adapter is in the machine, contact an IBM
service representative and report the return code,
return-code. System Programmer Response: Verify VTAM is
operational. It may be necessary to restart the VTAM list
Source: LANRES
that defines the channel adapter for LANRES. Refer to
6260E Could not determine which adapter to for information on the VTAMLST. If the error persists,
use. Please reload using the Adapter contact an IBM service representative and report the
option. return code, return-code.
Explanation: EWXLSA could not determine which Source: LANRES
adapter to use.
System Action: EWXLSA unloads. 6264E Error sending command command on
the channel (RC=return-code).
Explanation: An error occurred sending command to
System Programmer Response: Specify the adapter
the host.
by using the “Adapter” parameter on the LOAD
EWXLSA command. Refer to OS/390 LANRES System Action: EWXLSA unloads.
Configuration Files and Commands for the correct

EWX Server Messages
System Programmer Response: Verify VTAM is User Response: None.
operational. Reload EWXLSA. It may be necessary to
restart the VTAM list that defines the channel adapter
for LANRES. Refer to OS/390 LANRES Configuration Source: LANRES
Files and Commands for information on the VTAMLST.
If the error persists, contact an IBM service
representative and report the return code, return-code. 6269W VTAM sent a stop system.
Source: LANRES Explanation: VTAM has been stopped or restarted

and is informing EWXLSA. EWXLSA will restart and be
ready when VTAM starts.
6265E Error setting VTAM mode
(RC=return-code). System Action: EWXLSA continues.
Explanation: EWXLSA could not set the channel User Response: None.
adapter to VTAM header mode. System Programmer Response: None.
System Action: EWXLSA unloads. Source: LANRES
System Programmer Response: Restart LANRES, 6270W Error writing data to channel
including unloading and reloading the channel adapter (RC=return-code).
driver. If the error persists, contact an IBM service Explanation: EWXLSA tried to send data to the host,
representative and report the return code, return-code. but failed. The primitive is skipped and processing
Source: LANRES continues.
System Action: EWXLSA continues.
6266W Error reading data from channel User Response: None.
(RC=return-code).
Explanation: An error occurred reading data from the
host. Source: LANRES
System Action: EWXLSA will continue.

6271W Error querying adapter status
User Response: None. (RC=return-code).
System Programmer Response: If the error persists, Explanation: EWXLSA could not determine what the
contact an IBM service representative and report the primitive was from VTAM. The primitive is skipped and
return code, return-code. processing continues.
Source: LANRES System Action: EWXLSA continues.
6267W Error reading primitives from channel.
Explanation: This message is displayed with message
6266. An error occurred while reading for primitives sent Source: LANRES
from the host.
System Action: EWXLSA will continue. 6272W Adapter error occurred on the write
(Command code=command:
User Response: None. RC=return-code).
System Programmer Response: If the error persists, Explanation: An adapter error occurred while sending
contact an IBM service representative and report the data to the host.
return code, return-code.
Source: LANRES
6268W Unknown primitive received from System Programmer Response: If the problems
channel, 0xprimitive. persists and diagnostics do not detect an error, contact
an IBM service representative to report the failing
Explanation: EWXLSA could not determine what the command and return-code.
primitive was from VTAM. The primitive is skipped and
processing continues. Source: LANRES

EWX Server Messages
6273W Unknown VTAM request 6278W Invalid length received for command
command=0xcmd. 0xcommand.
Explanation: VTAM sent an unrecognized request. Explanation: The command, command, received a
negative length from VTAM.
System Action: The command, cmd is not processed.
EWXLSA continues. System Action: EWXLSA continues.
System Programmer Response: None. System Programmer Response: If the problem
Source: LANRES
Source: LANRES
6274W Unknown VTAM response
command=0xcmd. 6279W Wrong state for command 0xcommand;
state = state.
Explanation: VTAM sent an unrecognized response.
Explanation: The state does not support execution of
System Action: The response command, cmd, is not
the command, command.
processed. EWXLSA continues.
Source: LANRES
Source: LANRES
6275W Unknown VTAM primitive: 0xcmd.
Explanation: VTAM sent an unrecognized primitive.
6280E LSL registration failed
System Action: The command, cmd, is not (RC=return-code).
processed. EWXLSA continues.
Explanation: EWXLSA was unable to register with the
User Response: None. LSL.
System Programmer Response: None. System Action: EWXLSA will unload.

System Programmer Response: The Return Codes
6276W Subchannel Reset received. are:
Explanation: EWXLSA received a subchannel reset -2 EWXLSA was unable to allocate a resource
indicating VTAM was restarted. tag. DOWN the server and try again.
System Action: EWXLSA resets; waiting for another -3 EWXLSA was unable to allocate memory.
connection from VTAM. DOWN the server and try again.
User Response: None. -119 The NetWare Server has run out of resources.
DOWN the server and try again.
-125 Another program has previously registered the
Source: LANRES name EWXLSA is attempting to register.
-126 A system error has occurred. Contact an IBM
6277I VTAM header mode not reset service representative.
(RC=return-code).
Explanation: The call to the adapter to reset the If the problem persists, contact an IBM service
VTAM header mode failed. representative.
System Action: EWXLSA continues to close the Source: LANRES

channel.
Source: LANRES

EWX Server Messages
6281E Error on BeginThread call 7902E No drop type specified.

(ERRNO=errno).
Explanation: EWXCMD was started without a drop
Explanation: EWXLSA attempt to begin a thread, via type on the command line.
the NetWare BeginThread API, and the API failed with
System Action: The program unloads.
an errno as indicated.
System Action: EWXLSA will unload.
System Programmer Response: Enter a valid drop
type on the EWXCMD command line.
System Programmer Response: An errno of 5
Source: LANRES
indicates that the NetWare file server does not have
enough memory. Using the NetWare MODULES
command, determine which programs can be unloaded 7903E No query type specified.
to free up memory. Otherwise, add more memory to the
server. Explanation: EWXCMD was started without a query
type on the command line.
Source: LANRES
6282W CSUNLOAD has not been done on User Response: None.

service profile. System Programmer Response: Enter a valid query
Explanation: An attempt was made to unload the type on the EWXCMD command line.
EWXLSA.NLM before unloading the corresponding Source: LANRES
service profile. This message is also issued with the
NetWare message ″Unload module anyway?″ and a
prompt. 7904E No start type specified.
System Action: EWXLSA waits for the prompt Explanation: EWXCMD was started without a start
response. A ″y″ response may cause the server to go type on the command line.
down or hang. A ″n″ response should keep EWXLSA System Action: The program unloads.
loaded. Follow the instructions in the System
Programmer’s Response. User Response: None.
User Response: none. System Programmer Response: Enter a valid start

type on the EWXCMD command line.
System Programmer Response: Answer the prompt
with an ″n″. Then unload the following in this order: Source: LANRES
1. Any applications using EWXLSA.NLM (including
LANRES NLMs) for its communications 7905E No subchannel specified.
2. CPIC_SAA
3. The corresponding service profile using CSUNLOAD Explanation: A subchannel was not specified on the
4. EWXLSA command line.
Source: LANRES System Action: The program unloads.
7901E No command specified.
System Programmer Response: Enter the command
Explanation: EWXCMD was started with a blank again specifying the subchannel.
command line.
Source: LANRES
User Response: None. 7906E Time must be between 1 and 3600
seconds.
System Programmer Response: Enter a valid
command on the EWXCMD command line. Explanation: The optional time parameter must be
between 1 and 3600 second.
Source: LANRES
again specifying a valid time parameter.
Source: LANRES

EWX Server Messages
7907E DROP DISK for subchannel subchannel 7912E Incorrect option on DROP Disk:
on type adapter adapter failed options.
(RC=return-code).
Explanation: EWXCMD detected an option on the
Explanation: EWXCMD received an error while trying command line that was not valid.
to drop the requested subchannel.
System Programmer Response: Determine why the with valid options.
DROP command failed and take any necessary action.
Source: LANRES
Source: LANRES
7913E Incorrect option on Query
7908I DROP DISK was successful. Connections: options.
Explanation: EWXCMD successfully dropped the Explanation: EWXCMD detected an option on the
requested subchannel. command line that was not valid.
System Action: Processing continues. System Action: The program unloads.
System Programmer Response: None. System Programmer Response: Enter the command
with valid options.
Source: LANRES
Source: LANRES
7909I Channel device driver is not loaded.
7914E Incorrect option on Query Mmcstatus:
Explanation: EWXCMD was unable to add or delete a
options.
subchannel because no channel device driver was
loaded. Explanation: EWXCMD detected an option on the
command line that was not valid.
Source: LANRES
with valid options.
Source: LANRES
7910E Incorrect command command.
Explanation: EWXCMD detected a command on the
7915E Incorrect query type type.
Explanation: EWXCMD detected a query type on the
System Programmer Response: Enter a valid
command.
Source: LANRES
with a valid query type.
Source: LANRES
7911E Incorrect drop type type.
Explanation: EWXCMD detected a drop type on the
7916E Incorrect start type type.
Explanation: EWXCMD detected a start type on the
System Programmer Response: Reenter the
command with a valid drop type.
Source: LANRES

EWX Server Messages
7921E device_name device driver is not
with a valid start type.
loaded.
Source: LANRES
Explanation: EWXCMD was unable to display the
device driver version because the requested device
7917E Incorrect subchannel subchannel, driver is not loaded.
subchannel must be even.
Explanation: EWXCMD detected an odd subchannel
on the command line.
Source: LANRES
7922E Start for count sessions failed
specifying an even subchannel.
(RC=return-code).
Source: LANRES
Explanation: EWXCMD received an error while trying
to start the requested sessions.
7918E EWXDISK is not loaded.
Explanation: The Start and Drop commands are only
valid if the LANRES disk driver is loaded.
failure occurred and correct the problem.
Source: LANRES
Source: LANRES 7923I Start for count sessions was
successful.
7919I device_name Version Explanation: EWXCMD successfully started the

version.modification. requested sessions.
Explanation: EWXCMD displays the requested device System Action: Processing continues.
driver’s version.
Source: LANRES
Source: LANRES 7924E Unexpected character <character> at
non-blank position.
7920E Missing adapter number for Explanation: EWXCMD found an unexpected

subchannel subchannel. character while parsing a subchannel list.
Explanation: A comma was specified on the System Action: The program unloads.
command line indicating an adapter number would be
supplied, but the adapter number was not specified.
with a valid subchannel list.
Source: LANRES
either removing the comma or specifying a valid adapter
7925E Invalid adapter specified.
number.
Explanation: An Invalid adapter was specified on the
Source: LANRES
command.
System Programmer Response: Reenter the

EWX Server Messages
command with a valid adapter number. User Response: Enter the command with the a valid
clear option.
Source: LANRES
7926E Please specify the device driver type. Source: LANRES
Explanation: The program was unable to determine
which device driver to add the subchannels on. 7931E Incorrect clear type clear-type.
System Action: The program unloads. Explanation: The clear type was not valid.
User Response: None. System Action: Processing continues.
System Programmer Response: Reenter the User Response: Enter the command with a valid clear
command with a device driver. type.
Source: LANRES
7927I {Add|Delete} successful for subchannel
subchannel on type adapter adapter.
7932E Not enough resources available to
Explanation: The requested add or delete function allocate buffer.
completed successfully.
Explanation: EWXCMD tried to allocate a buffer, but
System Action: None. there wasn’t enough resources.
User Response: None. System Action: EWXCMD command status is not
processed.
Source: LANRES
System Programmer Response: Using the NetWare
7928I LANRES service level is service_level.
have already been loaded, and unload any that are not
Explanation: Informational message displayed when currently needed. Otherwise, add additional memory to
the service level is queried. This is the service level the server.
currently running on the NetWare server.
Source: LANRES
User Response: None. 7950I Service level service_level was
successfully received.
Explanation: EWXSRVC has successfully received a
Source: LANRES new service level from an attached host.
7929I LANRES service level service_level will
be applied. User Response: None.
Explanation: Informational message displayed when System Programmer Response: None.

the service level is queried. This is the service level that
Source: LANRES
will be applied to the NetWare server the next time
LANRES starts.
7951E Error receiving service level.
Explanation: An error occurred while receiving
service. See preceding messages to determine exact
System Programmer Response: None. cause of error.
Source: LANRES System Action: The program unloads.
7930E No clear type specified.
System Programmer Response: Review preceding
Explanation: The Logfile to be cleared has not been error messages to determine the cause of failure.
specified.
Source: LANRES

EWX Server Messages
7952I Canceling service level service_level. 7957E Error removing file filename
(ERRNO=errno).
Explanation: A host attempted to send an older
service level to the NetWare server. Explanation: An error occurred while removing the
file.
System Programmer Response: Use the errno to
Source: LANRES
determine why removing the file failed.
Source: LANRES
7953E Incorrect sequence number.
Explanation: An incorrect sequence number was
7958E Error renaming file filename1 to
detected while transferring data.
filename2 (ERRNO=errno).
System Action: The data transfer stops.
Explanation: An error occurred while renaming the
User Response: None. file.
System Programmer Response: None. System Action: Processing continues.
7954E Unable to create file filename determine why renaming the file failed.
(ERRNO=errno).
Source: LANRES
Explanation: An error occurred creating the file.
System Action: Processing continues. 7975E EWXSTART cannot be loaded while
LANRES is active.
Explanation: LANRES cannot be restarted while
System Programmer Response: Use the errno to LANRES NLMs are loaded.
determine why creating the file failed.
Source: LANRES
User Response: Stop all LANRES NLMs before
restarting.
7955E Error writing to file filename
(ERRNO=errno). System Programmer Response: None.
Explanation: An error occurred writing to the file. Source: LANRES

7976E Error opening file filename
User Response: None. (ERRNO=errno).
System Programmer Response: Use the errno to Explanation: An error occurred while opening the file.
determine why writing to the file failed.
Source: LANRES
7956E CRC error. System Programmer Response: Use the errno to

determine why opening the file failed.
Explanation: A CRC (cyclic redundancy check) error
occurred while transferring data. Source: LANRES

7977E Unknown error in ProcessBundle
User Response: None. (RC=return-code).
System Programmer Response: None. Explanation: An unexpected error occurred with
Source: LANRES unpacking the LANRES service.

EWX Server Messages
7982E Error opening output file filename
Source: LANRES
Explanation: An error occurred opening file filename
while unpacking the service bundle.
7978E Error opening file filename.
Explanation: An error occurred will opening a file
contained in the service bundle.
System Programmer Response: Determine why an
error occurred while opening the file.
Source: LANRES
System Programmer Response: Determine why an
error occurred while opening the file.
7983E Error reading header from bundle
Source: LANRES bundle_name (RC=return-code).
Explanation: An error occurred while reading the
7979E Invalid header format in file filename. header information from the service bundle.
Explanation: An invalid header was found in the System Action: Processing continues.
service bundle.
System Programmer Response: Load EWXSTART
User Response: None. again. If the problem persists, remove the service
bundle from the NetWare server and the host.
System Programmer Response: Remove the service
bundle from the NetWare server. If the problem Source: LANRES
reoccurs, disable service distribution on the host with
the incorrect service bundle.
7984E Error reading from bundle bundle_name
Source: LANRES (RC=return-code).
Explanation: An error occurred while reading data
7980I Unpacking file filename from bundle from the service bundle.
bundlename.
Explanation: File filename was successfully extracted.
System Programmer Response: Loading
User Response: None. EWXSTART again. If the problem persists, remove the
service bundle from the NetWare server and the host.
Source: LANRES
Source: LANRES
7985E Error writing file filename

7981E CRC error unpacking file filename from (RC=return-code).
bundle bundlename.
Explanation: An error occurred while writing to a file
Explanation: A CRC (cyclic redundancy check) extracted from the service bundle.
occurred while unpacking the file filename.
System Programmer Response: Remove the service cause of the write error and start EWXSTART again.
bundle from the NetWare server. If the problem
reoccurs, disable service distribution on the host with Source: LANRES
the incorrect service bundle.
Source: LANRES 7986E Error initializing expansion routine.
Explanation: An error occurred while initializing the
service unpacking routines.

EWX Server Messages
System Programmer Response: If the server is Source: LANRES
indicating a memory shortage, unload any unused
NLMs or add more memory to the server. Restart
8001E LANRES object already exists.
EWXSTART.
Explanation: The LANRES object cannot be added
Source: LANRES
because it already exists in the NetWare server’s
bindery.
7987E Unable to set time for file filename
System Action: Execution of the command is
(ERRNO=errno).
stopped. The system status remains the same.
Explanation: An error occurred when changing the
time stamp for the file.
System Programmer Response: The password for
the LANRES object can be changed using the
User Response: None. EWXLOBJ CHANGE command. The LANRES object
can be deleted using the EWXLOBJ DELETE command
and a new LANRES object can be added using the
determine why changing the time stamp for the file
EWXLOBJ ADD command.
failed.
Source: LANRES
Source: LANRES
8002E LANRES object does not exist.

7988E Cannot determine language type for
file filename. Explanation: The LANRES object cannot be deleted
because it cannot be located in the NetWare server’s
Explanation: The application was unable to determine
bindery.
the installed language type. The service bundle may be
defective or the message repository is not where it is System Action: Execution of the command is
expected or the name has been changed. stopped. The system status remains the same.
System Action: Processing continues. User Response: None.
User Response: None. System Programmer Response: Verify the correct
NetWare server is being used.
System Programmer Response: Unload all the
LANRES NLMs. Reload the LANRES product from Source: LANRES
diskette. If the problem persists, contact an IBM service
representative.
8003E Required parameter, PASSWORD or
Source: LANRES NEWPASSWORD, not specified.
Explanation: The PASSWORD or NEWPASSWORD
7989I Service was successfully applied. parameter must be specified. If neither one of these
parameters is specified, then both passwords will
Explanation: The previously received service bundle
default to null passwords which would be the same.
was processed successfully.
NetWare requires the new password be different from
System Action: Processing continues. the current password.
User Response: None. System Action: Execution of the command is

stopped.
Source: LANRES
7990E Error(s) occurred while applying OS/390 LANRES Configuration Files and Commands.
service.
Source: LANRES
Explanation: One or more errors occurred while
processing the previously received service bundle
successfully. 8004E Cannot login to LANRES object on
server servername. Unknown server or
System Action: Processing continues. LANRES object does not exist.
User Response: None. Explanation: The servername server cannot be found
System Programmer Response: See the previous or the LANRES object does not exist in that server’s
messages to determine what errors occurred. bindery.

EWX Server Messages
System Action: Execution of the command is
8009I Password for LANRES object on server
stopped.
server has been changed.
Explanation: The password for the LANRES object in
System Programmer Response: Verify the correct server server has been changed.
server is being used.
Source: LANRES
8005E Cannot login to LANRES object on
server servername. Access denied. Source: LANRES
Explanation: The servername server denied the login
attempt to the LANRES object in its bindery. The most 8010I LANRES object has been made a user
probable cause is an incorrect password. of print queue queue.
System Action: Execution of the command is Explanation: The LANRES object has been made a
stopped. user of the print queue.
User Response: None. System Action: Processing continues.
System Programmer Response: Verify the password User Response: None.
specified is correct.
Source: LANRES
Source: LANRES
8006E The new password is a duplicate of the

8011E Print queue queue does not exist.
current password.
Explanation: The Queue does not exist.
Explanation: NetWare requires the new password be
different from the current password. System Action: Processing continues.
System Action: Execution of the command is User Response: Enter the command with the correct
stopped. Queue name.
System Programmer Response: Load the program Source: LANRES
Source: LANRES
8007I LANRES object has been added.

Explanation: The LANRES object has been added to
the NetWare server’s bindery.
Source: LANRES
8008I LANRES object has been deleted.

Explanation: The LANRES object has been deleted
from the NetWare server’s bindery.
Source: LANRES

Chapter 3. EZM Application Enabling Technology Messages
EZM077E The specified service source is not EZM081E An error occurred accessing the
valid. service data, reason = %d.
Explanation: The source of the service must be either Explanation: While attempting to retrieve the service
file or tape and neither was specified. information from the indicated source, an error occurred.
The problem may be a system error or a problem with
User Response: If you have the source to the
the service package itself.
program that invoked the API, verify that the
EZMSMS20_SOURCE field is being filled in properly. User Response: None.
System Programmer Response: If you have the System Programmer Response: Contact the supplier
source to the program that invoked the API, verify that of the service package.
the EZMSMS20_SOURCE field is being filled in
properly.
EZM082E The length of the application name is
not valid.
EZM078E An error occurred attempting to access
Explanation: An application name cannot exceed
the specified source file.
eight characters in length.
Explanation: When the command attempted to
User Response: Verify the application name specified
retrieve the service package file from the file system, an
is less than eight characters. Contact the owner
error occurred.
provider of the application if you are not sure what
User Response: Verify the correct file name was name to specify.
supplied. Examine the permission bits to verify the
System Programmer Response: Verify the
system has access to the file and reissue the command.
application name specified is less than eight characters.
System Programmer Response: Verify the correct Contact the owner provider of the application if you are
file name was supplied. Examine the permission bits to not sure what name to specify.
verify the system has access to the file and reissue the
command.
EZM083E Unable to determine length of source
file.
EZM079E Service source was specified as file,
Explanation: An error occurred attempting to
but no filename was provided.
determine the length of the specified file.
Explanation: If you have the source that invoked the
User Response: Contact the supplier of the service
API, verify that filename is being properly placed in the
package.
EZMSMS20_FILENAME field when
EZMSMS20_SOURCE specifies file. System Programmer Response: Contact the supplier
of the service package.
User Response: Reissue the command or contact the
owner of the command.
EZM084E The length of the source file name is
System Programmer Response: Reissue the
not valid.
command or contact the owner of the command.
Explanation: The length of the specified file name
exceeded the maximum allowed limit for a file name.
EZM080E The specified application is not known
to the system User Response: Reissue the command specifying a
path whose length does not exceed the maximum file
Explanation: The command must specify the name of
length limit.
the application as it is known to the system. If you are
not sure of this name, contact the owner of the System Programmer Response: Reissue the
application. command specifying a path whose length does not
exceed the maximum file length limit.
User Response: Reissue the command supplying the
name of an application that is known to the system.
EZM085E The source file path must be fully
qualified.
command supplying the name of an application that is
known to the system. Explanation: The source file name must begin with a
’/’.

EZM Application Enabling Technology Messages
User Response: Reissue the command specifying a
EZM090E The list operation has no parameters.
complete path to the file.
Explanation: No parameters are needed for the list
operation.
command specifying a complete path to the file.
User Response: Enter the list operation without
parameters.
EZM086E The user or group name must not
contain the string ’EZM’. System Programmer Response: Enter the list
operation without parameters.
Explanation: Userids and group names containing the
string ’EZM’ are reserved.
EZM091E Parameter entered must be lower case.
User Response: Specify a different userid or group
name. Explanation: Parameters entered must be lower case.
System Programmer Response: Specify a different User Response: Enter parameters in lower case.
userid or group name.
System Programmer Response: Enter parameters in
lower case.
EZM087E The application specified is not defined
to the system.
EZM092E Specified command not found.
Explanation: The application name specified on the
Explanation: The system was unable to cancel the
command is not defined to the system.
command whose SARID (System Administration
User Response: Reissue the command specifying a Request Identifier) was specified because it could not
valid application name or install the application. find an active command with that identifier. Either the
command finished before it could be cancelled, or the
specified SARID is not valid.
command specifying a valid application name or install
the application. User Response: Verify the command you wish to
cancel is still running and that the SARID you specified
is correct.
EZM088E The file contains an empty segment
System Programmer Response: Verify the command
Explanation: The tcpactn file is divided into segments
you wish to cancel is still running and that the SARID
by a special line of text. Two of these lines were found
you specified is correct.
on together. This would cause one of the file segments
to be empty which is not valid.
EZM093E This command was cancelled
User Response: Either remove an extraneous file
segment line or provide contents for the empty file Explanation: The system administration command
segment. service, ezmcmd, was used to cancel this command.
System Programmer Response: Either remove an User Response: None.
extraneous file segment line or provide contents for the
empty file segment.
EZM094E The user must not connected to the

EZM089E The file contains a line which is too
specified primary group
wide
Explanation: Before a new primary group can be
Explanation: A tcpactn file may not contain lines
specified, the user must be connected to the group.
greater than 80 bytes long (not including the new-line
character). User Response: Use the chuser command to connect
the user to the group, then reissue the chuser command
User Response: Find the line which is too long and
to make the group the primary group.
split it into two lines or remove extraneous characters
which cause it to be too wide. System Programmer Response: Use the chuser
command to connect the user to the group, then reissue
System Programmer Response: Find the line which
the chuser command to make the group the primary
is too long and split it into two lines or remove
group.
extraneous characters which cause it to be too wide.

EZM095E Unable to delete this userid. EZM100I Command processing was successful.
Explanation: This userid either does not exist or is a Explanation: All operations for this command were
system id and cannot be deleted. completed successfully.
User Response: Specify the name of a user that User Response: None.
exists and can be deleted.
System Programmer Response: Specify the name of
a user that exists and can be deleted.
EZM101E Command error occurred, structure not
valid, reason code = nn
EZM096I No information found for specified
Explanation: A structure passed by the command to
user(s).
the system administration API was invalid.
Explanation: No information was found for the user(s)
User Response: Report the error and reason code to
specified.
the owner of the command issued.
User Response: Specify the name of a user that
System Programmer Response: Report the error and
exists.
reason code to the owner of the command issued.
System Programmer Response: Specify the name of
a user that exists.
EZM102E Insufficient authority to issue this
command.
EZM097I No information found for specified
Explanation: You do not have sufficient authorization
group(s).
to perform this function.
Explanation: No information was found for the group
User Response: Contact the system program to
name(s) specified.
obtain authority if required.
User Response: Specify the name of a group that
System Programmer Response: Determine if the
exists.
user should have authority to the command and grant it
System Programmer Response: Specify the name of if appropriate.
a group that exists.
EZM103E An internal error occurred while
EZM098E Owner userid specified is not valid. processing the command, reason code
= nnn
Explanation: The userid specified as the owner of the
group is not valid. Explanation: An internal problem prevented execution
of the command. The reason code displayed is the
User Response: Supply a userid which can be used
primary reason code from the request management
to own the group.
block (EZMSARMB).
System Programmer Response: Supply a userid
User Response: Report the problem to IBM.
which can be used to own the group.
EZM104E The system administration server is

EZM099I TCP/IP Definition file contained too few
terminating.
sections
Explanation: During processing of the command the
Explanation: The TCP/IP definition file provided to the
system administration server entered termination
tcpact command must have the correct number of
processing. This could be a normal or abnormal
sub-sections.
termination. Your command was cancelled.
User Response: Provide the command with a file
User Response: Retry the command when the server
containing the correct number of sub-sections.
has restarted.
System Programmer Response: Provide the
System Programmer Response: If the termination of
command with a file containing the correct number of
the server was unexpected, possibly determine why the
sub-sections.
termination occurred and/or report the problem to IBM.
Chapter 3. EZM Application Enabling Technology Messages 151

EZM105E Command processing error, reason = EZM110E Userid not defined to the system.
xxxx
Explanation: The userid specified is not defined to the
Explanation: An problem was encountered in the system.
processing of the command. The reason code displayed
User Response: Retry the command with the correct
is the secondary reason code found in the request
userid.
specific block (EZMSARSB).
System Programmer Response: Retry the command
User Response: Report the problem to the owner of
with the correct userid.
the command.
EZM111A Enter the new password

EZM106E Unable to obtain storage
Explanation: The command is prompting you to enter
Explanation: The command was unable to obtain
the new password for the user.
storage for the request management block
(EZMSARMB) or request specific block (EZMSARSB). User Response: Enter the new password (1 to 8
characters long) and press enter.
the command. System Programmer Response: Enter the new
password (1 to 8 characters long) and press enter.
EZM107I Default string will be used
EZM112E No userid specified
Explanation: No text was entered on the command,
so the default string will be used by the command. Explanation: The userid whose password is to be
changed must be specified as a parameter to the
User Response: None unless you entered text in
command.
which case report the problem to the owner of the
command. User Response: Reissue the command specifying the
userid whose password you wish to change.
System Programmer Response: None unless you
entered text in which case report the problem to the System Programmer Response: Reissue the
owner of the command. command specifying the userid whose password you
wish to change.
EZM108I The following text will be echoed
EZM113E Too many parameters specified
Explanation: This message will be followed by the
text which is being used for the function. It may be the Explanation: More parameters were specified than
default string or the string entered on the command are allowed for this command.
which may be truncated if it is too long.
User Response: Reissue the command with the
User Response: None unless the following text is not correct number of parameters.
what you expected in which case report the problem to
the owner of the command. System Programmer Response: Reissue the
command with the correct number of parameters.
System Programmer Response: None unless the
following text is not what you expected in which case
report the problem to the owner of the command. EZM114E Userid length not valid
Explanation: The length of the specified userid is
EZM109E An internal command error occurred. incorrect. It must be 1 to 8 characters long.
Explanation: The front end processing for the User Response: Reissue the command with a userid
command encountered an internal error not related to of the correct length.
the system administration server. System Programmer Response: Reissue the
User Response: Report the problem to the owner of command with a userid of the correct length.
the command.
System Programmer Response: Report the problem EZM115E No new password specified
to the owner of the command. Explanation: The response to the prompt for a new
password was empty. A new password must be
specified.
User Response: Reissue the command and respond
to message EZM111A with a valid password.

EZM121E An error occurred during restore
command and respond to message EZM111A with a
processing.
valid password.
Explanation: During the process of restoring from
tape, an error message was issued.
EZM116E Password length not valid
User Response: The restore failed. Try another
Explanation: The password must be 1-8 characters
backup tape if one exists or contact the owner of the
long.
command for more information.
User Response: Reissue the command and respond
System Programmer Response: The restore failed.
to message EZM111A with a valid password.
Try another backup tape if one exists or contact the
System Programmer Response: Reissue the owner of the command for more information.
command and respond to message EZM111A with a
valid password.
EZM122I A warning was issued during dump
processing.
EZM117E The specified file system name is not
Explanation: While dumping to tape a warning
valid.
message was issued.
Explanation: The command is unable to locate the file
User Response: Consider executing the dump again
system whose name was specified.
as it may not be valid.
User Response: Specify a valid file system name.
System Programmer Response: Consider executing
System Programmer Response: Specify a valid file the dump again as it may not be valid.
system name.
EZM123E An error occurred during dump
EZM118E Unable to write to write-protected tape processing.
Explanation: The command must write to a tape and Explanation: While dumping to tape an error message
the mounted tape is write-protected. was issued.
User Response: Remount the tape with the write User Response: The dump failed. Try another tape or
protect turned off or use another tape. contact the owner of the command for more information.
System Programmer Response: Remount the tape System Programmer Response: The dump failed.
with the write protect turned off or use another tape. Try another tape or contact the owner of the command
for more information.
EZM119A Mount a tape

EZM124E Error initializing tape
Explanation: A tape needs to be mounted for the
command to continue processing. Explanation: While attempting to initialize the tape
prior to use an error occurred.
User Response: Mount a tape.
User Response: Try another tape.
System Programmer Response: Mount a tape.
System Programmer Response: Try another tape.
EZM120I A warning was issued during restore

processing. EZM125E Function specified not valid.
Explanation: During the process of restoring from Explanation: The function value is not a valid
tape, a warning message was issued. selection.
User Response: Examine the restored file system. User Response: Specify a valid function value.
The restore may or may not have been successful.
System Programmer Response: Specify a valid
System Programmer Response: Examine the function value.
restored file system. The restore may or may not have
been successful.
EZM126E No parameters were specified.
Explanation: This command has required parameters
and none were specified.
User Response: Specify the correct required
parameters for the command.

System Programmer Response: Specify the correct System Programmer Response: Specify a valid
required parameters for the command. group name.
EZM127E Required parameter missing. EZM133E An unknown group name was

specified.
Explanation: A required parameter for this command
was not supplied. Explanation: The group that was specified is not
defined to the system.
User Response: Specify the required parameter.
User Response: Specify a valid group name.
System Programmer Response: Specify the required
parameter. System Programmer Response: Specify a valid
group name.
EZM128E Specified file system name has
incorrect length EZM134E The owner specified is not valid.
Explanation: A file system name must be 15 Explanation: The specified owner userid was not
characters long. valid.
User Response: Specify a valid file system name. User Response: Specify a valid owner userid.
System Programmer Response: Specify a valid file System Programmer Response: Specify a valid
system name. owner userid.
EZM129E Format of specified file system name is EZM135E Specified GID is not in the valid range
not valid.
Explanation: The specified gid value is not in the
Explanation: The name specified is not in the form range of valid gids.
required for a file system
User Response: Specify a valid gid.
User Response: Specify a valid file system name.
System Programmer Response: Specify a valid gid.
System Programmer Response: Specify a valid file
system name.
EZM136E The combination of SU and id values is
not valid.
EZM130E The length of the specified function is
Explanation: You cannot specify SU=N (the default)
not valid.
and id=0.
Explanation: The specified function contains too many
User Response: If you want the user to be a
or too few characters to be a valid value.
superuser, specify SU=Y and id=0 or just SU=Y and
User Response: Specify a valid function value some non-zero id to permit them to issue the SU
command.
function value System Programmer Response: If you want the user
to be a superuser, specify SU=Y and id=0 or just SU=Y
and some non-zero id to permit them to issue the SU
EZM131E Keyword must be specified in lower
command.
case
Explanation: All keywords are in lower case. The
EZM137E Cannot change/delete reserved system
specified value contained upper case characters.
groups
User Response: Specify a valid keyword in lower
Explanation: The specified group is a reserved
case.
system group and cannot be modified.
User Response: Specify another group to
keyword in lower case.
change/delete.
System Programmer Response: Specify another
The specified groupname is not valid.
group to change/delete.
Explanation: A group name was specified that is not
usable.
User Response: Specify a valid group name.

EZM138E Duplicate parameters specified. EZM144E Owner parameter length is not valid.
Explanation: The same keyword was specified more Explanation: The owner name parameter specified on
than once. the command is too long.
User Response: Reissue the command without User Response: Specify a valid owner name on the
specifying the same keyword more than once. command.
System Programmer Response: Reissue the System Programmer Response: Specify a valid
command without specifying the same keyword more owner name on the command.
than once.
EZM145E No value was specified for the gid
EZM139E Syntax Error keyword
Explanation: The command was issued with invalid Explanation: The gid keyword was specified, but no
syntax. value was supplied
User Response: Reissue the command using the User Response: Reissue the command specifying a
proper syntax. value for the gid keyword.
System Programmer Response: Reissue the System Programmer Response: Reissue the
command using the proper syntax. command specifying a value for the gid keyword.
EZM140E Final parameter should be the group EZM146E No value was specified on the owner
name keyword
Explanation: The last parameter on the command Explanation: The owner keyword was specified, but
was not the group name for the command to operate no value was supplied
on.
User Response: Specify the desired group name as value for the owner keyword
the final parameter.
System Programmer Response: Specify the desired command specifying a value for the owner keyword
group name as the final parameter.
EZM147E ’ALL’ is not a valid parameter value
EZM141E Specified keyword is not valid.
Explanation: The value ’ALL’ may not be specified on
Explanation: An unrecognized keyword was specified this command.
on the command.
User Response: Reissue the command using specific
User Response: Specify only valid keywords. values.
System Programmer Response: Specify only valid System Programmer Response: Reissue the
keywords. command using specific values.
EZM142E The length of the specified gid is not EZM148E Nothing to change was specified
valid.
Explanation: No parameters to change were
Explanation: The gid specified on the command is too specified.
long.
User Response: Specify something to change
User Response: Specify a valid gid.
System Programmer Response: Specify something
System Programmer Response: Specify a valid gid. to change
EZM143E Group parameter length is not valid. EZM149E No value entered for a keyword
Explanation: The group name parameter specified on Explanation: A keyword was specified without an
the command is too long accompanying value
User Response: Specify a valid group name on the User Response: Enter a value for the keyword
command.
System Programmer Response: Enter a value for
System Programmer Response: Specify a valid the keyword
group name on the command.

EZM150E The value entered after a keyword is EZM156E Delete failed for groups: xxxxx,xxxx...
not valid.
Explanation: The command was unable to delete the
Explanation: The value entered after a keyword was user from the groups listed
invalid
User Response: Reissue the command properly
User Response: Specify a valid value for the specifying the desired groups.
keyword.
System Programmer Response: Specify a valid command properly specifying the desired groups.
value for the keyword.
EZM157E Userid entered is not valid.
EZM151E A parameter length is not valid.
Explanation: The specified userid is not valid.
Explanation: The length of one of the parameters is
User Response: Specify a valid userid.
invalid
User Response: Specify all parameters with correct
userid.
lengths.
System Programmer Response: Specify all
EZM158E Tried to add too many groups
parameters with correct lengths.
Explanation: More groups were specified to be added
than are permitted by the command.
EZM152E The length of the userid parameter is
not valid. User Response: Reissue the command specifying
fewer groups to be added.
Explanation: The userid specified is too long.
User Response: Specify a userid with a valid length.
command specifying fewer groups to be added.
System Programmer Response: Specify a userid
with a valid length.
EZM159E Tried to delete the user from too many
groups
EZM153E No userid was supplied
Explanation: More groups were specified for the user
Explanation: The command requires a userid to be deleted from than are permitted by the command.
parameter and one was not specified.
User Response: Reissue the command specifying
User Response: Specify a userid. fewer groups.
System Programmer Response: Specify a userid. System Programmer Response: Reissue the
command specifying fewer groups.
EZM154E Unable to determine the default
primary group EZM160E Specified uid is not valid.
Explanation: The command was unable to determine Explanation: The uid specified on the command is not
the default group to use for the prgrp command. valid.
User Response: Report the error to the owner of the User Response: Reissue the command specifying a
command. valid uid.
System Programmer Response: Report the error to System Programmer Response: Reissue the
the owner of the command. command specifying a valid uid.
EZM155E Connect failed for groups: EZM161E Group name to connect to is not valid
xxxxx,xxxx...
Explanation: A group name specified for the user to
Explanation: The command was unable to connect be connected to is invalid.
the user to the groups listed
User Response: Reissue the command properly valid group names
specifying the desired groups
System Programmer Response: Reissue the command specifying valid group names
command properly specifying the desired groups

System Programmer Response: Report the error to
EZM162E Group name to delete user from is not
the owner of the command.
valid.
Explanation: A group name specified for the user to
EZM168E An incorrect tape was mounted. Mount
be deleted from is invalid.
the correct tape.
Explanation: The label on the tape indicates that this
valid group names
tape does not contain the required information.
User Response: Mount a valid tape for this command.
command specifying valid group names
System Programmer Response: Mount a valid tape
for this command.
EZM163E Specified primary group is not valid.
Explanation: The group name specified for the new
EZM169E The source and destination values are
primary group is invalid
required.
User Response: Specify a valid primary group name.
Explanation: The source and destination values must
System Programmer Response: Specify a valid be specified and at least one was not.
primary group name.
User Response: Reissue the command using the
proper syntax.
EZM164E Specified su parameter is not valid
Explanation: The value specified for the su parameter command using the proper syntax.
is invalid.
User Response: Specify a valid value for the su EZM170E Unable to obtain current userid.
parameter.
Explanation: To process the command, the current
System Programmer Response: Specify a valid userid must be obtained and the command was unable
value for the su parameter. to do this successfully.
EZM165E Specified gecos parameter is not valid. the command.
Explanation: The value specified on the gecos System Programmer Response: Report the problem
parameter is not valid. to the owner of the command.
User Response: Specify a valid value for the gecos
parameter. EZM171E Missing required title
System Programmer Response: Specify a valid Explanation: A title must be specified for the captured
value for the gecos parameter. diagnostics
User Response: Specify a title
EZM166E Combination of source and destination
System Programmer Response: Specify a title
is not valid.
Explanation: The selected combination of source and
EZM172I The specified title will not be used.
destination values is invalid.
Explanation: This flavor of the command does not
User Response: Specify compatible source and
require a title to be specified but one was provided. It is
destination values.
ignored.
System Programmer Response: Specify compatible
source and destination values.
EZM167I A warning was issued during
command processing EZM173E Parameter specified is not valid.
Explanation: During the processing of the command a Explanation: A parameter was specified that is not a
warning was issued while moving files between source part of the valid syntax for the command.
and destination.
User Response: Report the error to the owner of the proper syntax.
command.

command using the proper syntax.
EZM179E Specified destination is not valid.
Explanation: The destination value is not a valid
EZM174E Source specified is not valid.
selection.
Explanation: The source parameter specifies an
User Response: Specify a valid destination value.
invalid value.
User Response: Specify a valid value for the source
destination value.
parameter.
EZM180E GID keyword is not valid
value for the source parameter.
Explanation: The syntax of the gid keyword is invalid.
EZM175E This command has no parameters User Response: Reissue the command using the
proper syntax.
Explanation: The command takes no parameters,
however parameters were specified. System Programmer Response: Reissue the
User Response: Reissue the command without
specifying parameters.
EZM181E The first parameter must be the gid.
command without specifying parameters. Explanation: The syntax of the command requires
that the first parameter specify the requested gid value.
The command was unable to find the gid keyword
EZM176I Returned information exceeds
correctly specified in the first parameter.
available space.
Explanation: The command was unable to allocate
proper syntax.
sufficient space to capture information about all the
users/groups requested or to contain all the TCP/IP System Programmer Response: Reissue the
configuration data. command using the proper syntax.
User Response: Reissue the command requesting
information about fewer users/groups or provide a larger EZM182E Input Error
buffer in the EZMSARSB.
Explanation: An error occurred parsing the input to
System Programmer Response: Reissue the the command.
command requesting information about fewer
User Response: Verify the syntax passed to the
users/groups or provide a larger buffer in the
command was valid.
EZMSARSB.
System Programmer Response: Verify the syntax
passed to the command was valid.
EZM177E Parameter must be uppercase
Explanation: The parameter to this command must be
EZM183E Unable to open file
in upper case.
Explanation: The command failed attempting to open
the output file specified.
proper syntax.
file with a valid path that you have authority to open.
command specifying a file with a valid path that you
EZM178E Too many userids/groups specified.
have authority to open.
Explanation: The user exceeded the maximum
number of userids/groups which may be specified on
EZM184E A specified index is not valid.
this command.
Explanation: The specified index is not valid.
fewer userids/groups. User Response: Reissue the command specifying a
valid index.
command specifying fewer userids/groups. System Programmer Response: Reissue the
command specifying a valid index.

index of the error of interest and a file name for the
EZM185E Missing index or filename
information to be written to.
Explanation: The command syntax requires an index
User Response: Reissue the command as
and file name to be specified on the detailed form of the
appropriate if desired.
command.
User Response: Reissue the command with the
command as appropriate if desired.
proper syntax.
EZM191A Confirm you wish to continue with
command with the proper syntax.
system shutdown (Y/N):
Explanation: The command is verifying that you are
EZM186E Text is too long. It will be truncated.
sure you wish to shutdown the system at this time.
Explanation: The text entered exceeds the maximum
User Response: Respond ’Y’ to continue with
length. It will be truncated.
shutdown and ’N’ to not shutdown.
User Response: Reissue the command with less text
System Programmer Response: Respond ’Y’ to
or accept the truncated version.
continue with shutdown and ’N’ to not shutdown.
command with less text or accept the truncated version.
EZM192E The confirmation response is not valid.
Explanation: Respond to prompt with a ’Y’ or ’N’.
EZM187E Unable to write to file
User Response: Respond to prompt with a ’Y’ or ’N’.
Explanation: The command is unable to write to the
output file System Programmer Response: Respond to prompt
with a ’Y’ or ’N’.
file which can be written to.
EZM193I Command processing terminated.
command specifying a file which can be written to. Explanation: The command does not continue to
process your request.
EZM188E An error occurred closing the file User Response: None.
Explanation: While attempting to close the output file, System Programmer Response: None.
an error occurred.
User Response: Examine the contents of the output EZM194E No TCP/IP definition identifier was
file. If the contents are correct, ignore the error, supplied.
otherwise report the problem to the owner of the
command. Explanation: The command requires you to specify
which TCP/IP definition set you wish to active.
System Programmer Response: Examine the
contents of the output file. If the contents are correct, User Response: Reissue the command specifying a
ignore the error, otherwise report the problem to the TCP/IP definition set identifier.
owner of the command. System Programmer Response: Reissue the
command specifying a TCP/IP definition set identifier.
EZM189I No diagnostic information to display
Explanation: The command was unable to locate any EZM195A Are you sure you want to recycle
diagnostic information to report. TCP/IP now? All users will be
terminated. Reply Y/N.
Explanation: Respond ’Y’ to terminate all users and
System Programmer Response: None. recycle TCP/IP using the definition set you specified.
Respond ’N’ to abort the command.
EZM190I Reissue the command with an index User Response: Respond ’Y’ to terminate all users
and output file name for more and recycle TCP/IP using the definition set you
information. specified. Respond ’N’ to abort the command.
Explanation: To receive more information about a System Programmer Response: Respond ’Y’ to
particular error, reissue the command specifying the terminate all users and recycle TCP/IP using the

definition set you specified. Respond ’N’ to abort the
EZM201I The service apply needs to shutdown
command.
the system and reIPL.
Explanation: Automated service application requires a
EZM196E Error opening TCP/IP definition file.
re-IPL to occur
Explanation: An error occurred opening the specified
System Action: Control Center process should re-IPL
TCP/IP definition file.
the system
User Response: Verify the file exists or specify
Operator Response: None.
another file.
System Programmer Response: Verify the file exists
or specify another file. Detecting Module: EZMSAWTO
EZM197E Error closing TCP/IP definition file. EZM202I Installing appl_name service step step
of totalstep
Explanation: An error occurred closing the specified
TCP/IP definition file. Explanation: This message is issued as a status
update as progress is made in applying service.
User Response: Verify the file exists or specify
another file. In the message text:
System Programmer Response: Verify the file exists appl_name
or specify another file. Application name
step
EZM198E Unable to determine length of TCP/IP Current Step
Definition file.
totalstep
Explanation: The command was unable to determine Total Steps
the length of the specified TCP/IP definition file.
System Action: Service apply processing continues
User Response: Examine the definition file to ensure until all steps are complete or an error occurs
it is not corrupted. Report the problem to the owner of
the command.
definition file to ensure it is not corrupted. Report the Detecting Module: EZMSAWTO
problem to the owner of the command.
EZM203I Control Center needs to download its

EZM199I No captured diagnostic information code and recycle.
was found
Explanation: The service includes an update to the
Explanation: No captured diagnostic information was Control Center code. The new code needs to be
found on the system. downloaded to the Health Monitor platform and the
Control Center should recycle to use the new code
EZM200I Service apply is complete or was not System Programmer Response: None.
needed.
Detecting Module: EZMSAWTO
Explanation: Automated service application completed
or was not necessary.
EZM220E appl_name Service level of newlevel
System Action: None. cannot be installed on oldlevel
Operator Response: None. Explanation: An attempt was made to install an
invalid service level. Either you have attempted to skip a
service level that must be applied or you have
Detecting Module: EZMSAWTO attempted to regress to a previous level which is not
supported via this process.
In the message text:

appl_name Operator Response: None.
Application name
System Programmer Response: Restore the system
newlevel from backups and restart it.
New Service Level
oldlevel
Previous Service Level
EZM223I System restore is complete.
System Action: Service apply processing stops. The
Explanation: Processing following restore of the
system must be restored from backup tapes.
system from tape is complete.
System Action: Automation will now make the system
System Programmer Response: Restore the system available for use
from backups and restart it.
EZM221E appl_name Service step step of totalstep
is being repeated due to a system
error. Steps should not be repeated. EZM224E Restore system/HFS failed. Preceding
messages should detail the error.
Explanation: An error occurred during service
application processing. The system attempted to repeat Explanation: Job EZMHFSRS used to restore the
an install step which is not allowed. HFS systems files failed.
In the message text: System Action: System restore processing stops.
Automation stops thus stopping the start of any
appl_name
subsystems.
Application name
step
Current processing step System Programmer Response: Look at the
SYSLOG or dataset EZM.JOBOUT.EZMHFSRS to
totalstep
determine why the EZMHFSRS job failed.
Total number of steps
System Action: Service apply processing stops. The
EZM300I Have automation switch NETVIEW log
Explanation: Automation needs to switch to a new
System Programmer Response: Restore the system
Netview log
from backups and restart it.
System Action: Automation switches to a new
Netview log
EZM222E appl_name Service REXX
EZMSRVrexxid failed with a return code System Programmer Response: None.
of returncode. A preceding message
should detail the error. Detecting Module: EZMSAWTO
Explanation: An exec involved in processing service

application failed. EZM301I Invalid message or fillins: text
In the message text: Explanation: Automation was requested to issue an

undefined message or a valid message without the
appl_name required fillins.
Application name
System Action: The error is returned to the issuer of
rexxid the message.
Last two characters of the Rexx exec name
returncode
The return code from the exec System Programmer Response: None.
System Action: Service apply processing stops. The Detecting Module: EZMSAWTO

appl_name
EZM302I Automation job was successful
Application name
Explanation: A job started by automation has
operation
Operation completed on the Application name
System Action: Job is terminated. Automation
continues with next step. Used when applying service.
EZM307I parameter was not specified.

EZM303I Automation job failed
Explanation: The required parameter was not left out
Explanation: A job started by automation has
in the call to the EZMAPP REXX.
completed but errors were detected.
System Action: Job is terminated. Automation will
issue other messages indicating what actions should be parameter
taken. Used when applying service. Parameter name
Operator Response: None. System Action: None.
System Programmer Response: None. Operator Response: Correct the call to the EZMAPP
REXX. The parameters for the install operation are
INSTALL Application_name Application_REXX. For all
other operations the Application_REXX parameter can
EZM304I Build dump summary for: text be omitted.
Explanation: Automation has found that a dump System Programmer Response: None.
dataset does not have a summary dataset associated
with it.
System Action: Automation builds a summary report
EZM308I Status not specified or is not I or A
dataset in the form dump_dataset_.Rnnn .
Explanation: An application is being added to the
application list by the EZMAPP REXX. However, the
System Programmer Response: None. status of the application was not specified or was not I
or A.
System Action: The application is not added to the
application list.
EZM305I nnn Application(s) Found
Operator Response: Correct the call to the EZMAPP
Explanation: This is the first line in a multi-line
REXX. The parameters are Operation_to_be_performed
message listing all the applications installed and
Application_name Application_REXX Application_status.
activated on the system. The second line is a title line.
The third and remaining lines list the application name, System Programmer Response: None.
the REXX name used to install, activate, uninstall, and
deactivate the application. The last character indicates
the status of the application: I-Installed or A-Activated.
EZM309I Cannot do that operation to that
application.
Explanation: An operation is trying to be performed
System Programmer Response: None. on an application that cannot be done. This might be
trying to uninstall an application that is activated (must
deactivate first) or installing an application that already
exists.
EZM306I appl_name has been operation
System Action: The requested operation is not done
Explanation: The specified operation has been to the application.
performed successfully on the application.
Operator Response: Perform the proper operation on
In the message text: the application. Use Install followed by activate, then
deactivate, and lastly uninstall.

Detecting Module: EZMSAWTO Detecting Module: EZMSAWTO
EZM310I Application not found. EZM313I Unknown EZMAPP Operation.

Explanation: An operation is trying to be performed Explanation: The EZMAPP REXX is being called to
on an application that does not exist (has not been perform an unknown operation.
installed).
System Action: The requested operation is not done.
System Action: The requested operation is not done
Operator Response: Call EZMAPP REXX with a
to the application.
proper operation: LIST, INSTALL, UNINSTALL,
Operator Response: Call EZMAPP REXX with the ACTIVATE, DEACTIVATE, QUERY, or REXX.
INSTALL operation to install the application or use the
LIST operation to list the valid application names and
retry the operation on a listed application name. Detecting Module: EZMSAWTO
EZM314I REXX name is already being used to
support another application.
Explanation: An operation is trying to be install an
EZM311I Application name/rexx must be 8 or
application. However, the REXX name specified on the
less characters in length.
call to EZMAPP is already in the application list to
Explanation: Either the Application name and/or support another application. The REXX name must be
Application_REXX parameters being specified on the unique.
call to the EZMAPP REXX are greater than 8
System Action: The requested operation is not done.
characters.
Operator Response: Call EZMAPP REXX with the
LIST operation to determine the application that is using
name/rexx the REXX name. Determine if the correct REXX names
The words Name or REXX are being used. Two applications cannot use the same
REXX.
Operator Response: Correct the call to the EZMAPP
REXX insuring the Application_name and/or Detecting Module: EZMSAWTO
Application_REXX are 8 or less characters in length.
EZM312I Application was not operation.

rexx_name failed with RC=returncode
Explanation: The EZMAPP REXX has called the
Rexx_name asking it to perform the specified operation.
The Rexx_name failed with the specified return code.
operation
Operation trying to be performed.
rexx_name
Name of REXX that was being called.
returncode
The return code from the REXX
Operator Response: Look at the documentation for
the Rexx_name to determine the condition causing the
return code. Fix as specified in the documentation.

count
EZM315I EZMKILL PARAMETERS: ? - DISPLAY
The number of applications
THIS HELP TEXT NETVIEW NOAUTO -
PREVENT AUTOMATIC RESTART OF appname
NETVIEW/EZMAUTO. NETVIEW AUTO - Application name
RESTART NETVIEW/EZMAUTO IF IT
TERMINATES. JESCOLD - SET THE rexxname
NETVIEW VARIABLES SUCH THAT Application Rexx exec name
WHEN JES2 IS STARTED AGAIN IT status
WILL BE A COLD START. JESWARM - Application Status: (I)nstalled or (A)ctive
SET THE NETVIEW VARIABLES SUCH
THAT WHEN JES2 IS STARTED AGAIN System Action: None.
IT WILL BE A WARM START. RESTHFS Operator Response: None.
- SET THE NETVIEW VARIABLES
SUCH THAT WHEN NETVIEW IS System Programmer Response: None.
RECYCLED OR IPL, RESTORE THE Detecting Module: EZMSAWTO
HFS SYSTEM FILES. NORESTHFS -
SET THE NETVIEW VARIABLES SUCH
THAT WHEN NETVIEW IS RECYCLED EZM900E System Administration Structure
OR IPL, DO NOT RESTORE THE HFS Event: module, errno, errno2, errno3
FILES. CLPAON - MODIFY IEASYS00
Explanation: An error was detected by the System
TO CLEAR LPA DURING THE NEXT
Administration Server
IPL. LONG IPL. CLPAOFF - MODIFY
IEASYS00 TO NOT CLEAR LPA In the message text:
DURING THE NEXT IPL. SHORT IPL.
module
SET SUBSYS ON/OFF - TURN ON/OFF
The detecting module
SYSTEM AUTOMATION FOR A
SUBSYSTEM RESTART SUBSYS - errno
CHANGE STATE OF SUBSYSTEM TO Primary Error Code
RESTART. RECYCLE SUBSYS - STOP
A SUBSYSTEM AND RESTART IT. errno2
SUBSYS=subsys subsys subsys subsys Secondary Error Code
subsys subsys errno3
Explanation: Describes the options available on the Tertiary Error Code
EZMKILL command System Action: The request involved in the error or
In the message text: all active requests may be terminated depending on the
error
subsys
Supported Subsystems Operator Response: None. The System
Administration Server should continue or automatically
System Action: None. recycle depending on the severity of the error
Operator Response: None. System Programmer Response: None. The System
Administration Server should continue or automatically
recycle depending on the severity of the error
EZM316I count Application(s) Found NUMBER

EZM901I Command Processing Successful
NAME REXX STATUS count appname
rexxname status Explanation: A System Administration command
Explanation: This is the first line in a multi-line
message listing all the applications installed and System Action: The successful completion is reported
activated on the system. The second line is a title line. to the issuer of the command by the System
The third and remaining lines list the application name, Administration Structure
the REXX name used to install, activate, uninstall, and
deactivate the application. The last character indicates Operator Response: None.
the status of the application: I-Installed or A-Activated. System Programmer Response: None.
Lists the installed and active applications.

EZM902I Command Processing Failed EZM906I System Administration Server Active

Explanation: A System Administration command failed Explanation: The System Administration Server has
completed initialization and is available for use
System Action: The error is reported to the issuer of
the command by the System Administration Structure System Action: None.
Operator Response: None. Operator Response: None.
EZM903E Unable to Issue Requested Message: EZM907I System Administration Server

msgid Reason Code = rsncode Terminated
Explanation: The EZMSAWTO module was invoked to Explanation: The System Administration Server has
issue a message but was unable to issue the requested ended.
message.
System Action: No further system administration
In the message text: commands may be processed until the server restarts. It
will automatically restart unless the system is shutting
msgid
down.
Requested Message Id
rsncode
Reason Code System Programmer Response: None.
System Action: This message is issued instead. Detecting Module: EZMSAWTO
EZM908W Warning Restoring Dataset
to IBM Explanation: While processing a System
Administration command that requires datasets to be
restored, a warning was issued.
System Action: The warning is returned to the issuer
EZM904I Unable to Find an EZMSARSB
of the command.
Explanation: A System Administration command
expected to have an EZMSARSB control block supplied
to it but could not locate it. System Programmer Response: None.
System Action: The command fails and the command Detecting Module: EZMSAWTO
issuer is notified.
Operator Response: None. EZM909E Error Restoring Dataset
System Programmer Response: Report the problem Explanation: While processing a System
to the owner of the failing command. Administration command that requires datasets to be
restored, an error occurred.
the command.
EZM905I System Administration Server
Initializing Operator Response: None.
Explanation: The System Administration Server has System Programmer Response: None.
been started
System Action: Initialization continues
Operator Response: None. EZM910W Warning Dumping Dataset
System Programmer Response: None. Explanation: While processing a System
Administration command that requires datasets to be
dumped, a warning was issued.
System Action: The warning is returned to the issuer
of the command.

Operator Response: None. v (’EZMKILL RECYCLE TCPIP’)
System Programmer Response: None. v (’EZMSTOP R’)
Detecting Module: EZMSAWTO System Action: The text of the command is

processed as a command by automation
EZM911E Error Dumping Dataset Operator Response: None.
Explanation: While processing a System System Programmer Response: None.

Administration command that requires datasets to be Detecting Module: EZMSAWTO
dumped, an error occurred.
System Action: The error is returned to the issuer of EZM916E DELUSER failed
the command.
Explanation: An error occurred attempting to use the
Operator Response: None. RACF DELUSER command
System Programmer Response: None. System Action: The error is returned to the issuer of
Detecting Module: EZMSAWTO the command.
EZM912E Error from IEHINITT. System Programmer Response: None.
Explanation: An error occurred initializing a tape Detecting Module: EZMSAWTO
the command. EZM917E CHUSER failed
Operator Response: None. Explanation: An error occurred attempting to use the
System Programmer Response: None. RACF ALTUSER command
Detecting Module: EZMSAWTO System Action: The error is returned to the issuer of
the command.
EZM913E ADDUSER failed Operator Response: None.
Explanation: An error occurred attempting to use the System Programmer Response: None.
RACF ADDUSER command Detecting Module: EZMSAWTO
the command. EZM918I MAKESITE failed
Operator Response: None. Explanation: An error occurred attempting to use the
System Programmer Response: None. TCP/IP MAKESITE command
Detecting Module: EZMSAWTO System Action: The error is returned to the issuer of
the command.
EZM914E Connect failed Operator Response: None.
Explanation: An error occurred attempting to use the System Programmer Response: None.
RACF CONNECT command Detecting Module: EZMSAWTO
the command. EZM919I ADRDSSU issued a warning
Operator Response: None. Explanation: Processing by DFSMSdss resulted in a
System Programmer Response: None. warning
Detecting Module: EZMSAWTO System Action: The warning is returned to the issuer
of the command.
EZM915I text Operator Response: None.
Explanation: The text of the command is processed System Programmer Response: None.
as a command by automation Detecting Module: EZMSAWTO
v (’EZMSTOP Q’)

EZM920I ADRDSSU failed EZM925I LISTGROUP failure.

Explanation: Processing by DFSMSdss resulted in an Explanation: An error occurred attempting to use the
error RACF LISTGROUP command
System Action: The error is returned to the issuer of System Action: The error is returned to the issuer of
the command. the command.
EZM921E LSUSER failed EZM926I text

Explanation: An error occurred attempting to use the Explanation: Automation will issue the EZMAPP
RACF LISTUSER command command using the text of this message as parameters.
Usually issued as a WTOR, automation will respond
with the result of the command.
the command.
System Action: Automation issues the command.
EZM922I RUN HOUSKEEPING FOR CPDIAG.
EZM927I cpserve error copying from
Explanation: A System Administration command
SYS1.EZMAPP.SERVICE
requires automation housekeeping to be run
Explanation: During processing of the cpserve
System Action: Automation begins housekeeping
command, an attempt is made to copy the application
processing.
exec, the EZMSRV01 exec, and the EZMSR01 proc
Operator Response: None. from SYS1.EZMAPP.SERVICE. This message indicates
that one of these copies failed.
System Action: cpserve processing is ended. The
Detecting Module: EZMSAWTO error is returned to the issuer of the cpserve command.
EZM923I HOUSKEEPING TASK FINISHED.
Explanation: Automation housekeeping has
completed. Detecting Module: EZMSAWTO
System Action: A command which is waiting for

housekeeping to complete may continue. EZM928I cpserve error restoring
SYS1.EZMAPP.SERVICE
Explanation: During processing of the cpserve
System Programmer Response: None. command, an attempt is made to restore
Detecting Module: EZMSAWTO SYS1.EZMAPP.SERVICE from either tape or from the
SYS1.EZMAPP.SERVICE.FB80 dataset (depending on
where the issuer of the cpserve command indicated the
EZM924I SHOWDIAG failure. service was located). This restore has encountered an
Explanation: An error occurred processing the error. Probably the file is not located in the dump
showdiag command. dataset or the dump dataset could not be found.
System Action: The error is returned to the issuer of System Action: cpserve processing is ended. The
the command. error is returned to the issuer of the cpserve command.


Chapter 4. GDE Messages
GDE001E DISTRIBUTED FILEMANAGER TARGET GDE002I DISTRIBUTED FILEMANAGER TARGET
SYSTEM INITIALIZATION FAILED. text CONVERSATION INITIALIZATION
FAILED FOR ASID=aaaaaaaa
Explanation: A problem occurred during initialization
USERID=uuuuuuuu
of the Distributed FileManager/MVS target function,
PRTNRLU=nnnnnnnnnnnnnnnnn
which was requested via a START command.
CONVID=cccccccc. text
Explanation: The Distributed FileManager/MVS was
text attempting to initialize the DFM target transaction
One of the following: program (TP) in address space aaaaaaaa in response
to an APPC ALLOCATE request issued from a DFM
null-message-text source system. The DFM target TP initialization ended
A system error occurred. Refer to preceding abnormally.
error messages to help determine the specific
error and, if applicable, call the IBM Support In the message text:
Center.
aaaaaaaa
ECSA STORAGE COULD NOT BE OBTAINED. n The address space identifier (ASID).
HEX BYTES REQUIRED
uuuuuuuu
A request for ECSA storage could not be
The MVS user ID specified on the conversation
fulfilled. n indicates the number of ECSA bytes,
allocation request.
in hexadecimal, required to initialize the
Distributed FileManager/MVS. Increase the nnnnnnnnnnnnnnnnn
size of ECSA by at least n hexadecimal bytes The name of the (partner) logical unit (LU) at which
and try again. the DFM source server requesting the conversation
allocation is located.
GDEIGBS COULD NOT BE LOADED. LOAD
ABEND CODE=cccccccc REASON cccccccc
CODE=reason-code ALIAS NAME=alias-name The conversation ID assigned by APPC to this
The DFM load module GDEIGBS could not be conversation.
loaded because of an error detected by the
text
LOAD function while attempting to obtain the
One of the following:
address of the alias name CSECT. Check the
LOAD abend and reason codes and take null-message-text
corrective action. If no corrective action solves A system error occurred. Refer to preceding
the problem, call the IBM Support Center. error messages to help determine the specific
(Note that an ABEND code of 99 and a reason error and, if applicable, call the IBM Support
code of 99 is set by the Distributed Center.
FileManager/MVS to indicate that the alias
name loaded was linkedited above 16 PRIVATE STORAGE COULD NOT BE OBTAINED.
megabytes but is required to be linkedited n HEX BYTES REQUIRED
below 16 megabytes.) A request for private storage could not be
fulfilled. n indicates the number of private
System Action: The Distributed FileManager/MVS storage bytes, in hexadecimal, required to
target function is not activated, except in the case initiate the conversation. Increase the region
where message GDE006E was issued with CDRA size of the conversation address space by at
reason code X'FFFFFFFF'. See message GDE006E for least n hexadecimal bytes and tell the DFM
details. source LU to try again. The region size can be
specified in the TP profile JCL or in the
System Programmer Response: See the abend or
TPDEFAULT REGION(xx) parameter in the
reason codes contained in either the message text or in
ASCHPMxx parmlib member.
any related console messages. If no corrective action
can be taken, contact the IBM Support Center. ECSA STORAGE COULD NOT BE OBTAINED. n
HEX BYTES REQUIRED
Source: Distributed FileManager/MVS (DFM/MVS)
A request for ECSA storage could not be
fulfilled. n indicates the number of ECSA bytes,
in hexadecimal, required to initialize the
conversation. Increase the size of ECSA by at
least n hexadecimal bytes and tell the DFM
source LU to try again.

ATTACH ERROR. ATTACH RTNCD=return-code
GDE005I DISTRIBUTED FILEMANAGER TARGET
An error was detected by the ATTACH function.
SYSTEM {ALREADY ACTIVE|NOT
Check the ATTACH return code and correct the
ACTIVE, START DFM}
problem. Then tell the DFM source LU to try
again. Explanation: Either an attempt was made to start the
Distributed FileManager/MVS target system using the
APPC ERROR. VERB=vvvvvvvv
START DFM command, but the target function is
RTNCD=return-code
already active or an attempt was made to use the
An error was detected by an APPC routine.
DFM/MVS, but the target function is not active and
The name of the APPC verb that was being
needs to be started.
processed is supplied along with the return
code from the APPC verb routine. Correct the System Action: If DFM/MVS is already active, the
problem and tell the DFM source LU to try system ignores the START DFM command. If DFM/MVS
again. is not active, jobs requiring target DFM function will end
with non-zero return codes.
System Action: The conversation is ended. If a
system error occurred, an abend is issued, the error is Operator Response: If DFM/MVS is active, none. If
logged in the logrec data set, and a dump is produced DFM/MVS is not active, enter a START DFM command.
and placed in a SYS1.DUMPnn data set. In all other
cases, an abend is issued but the error is not recorded
and no dump is taken.
GDE006E INVALID [VALUE FOUND FOR]
System Programmer Response: Search problem
KEYWORD: kkkkkkkk DISTRIBUTED
reporting data bases for a fix for the problem. If no fix
FILEMANAGER TARGET SYSTEM NOT
exists, contact the IBM Support Center. Provide the
STARTED
logrec data set and the dump, if available.
Explanation: The DFMxx parmlib member contains an
incorrect value for the indicated keyword. If the keyword
in error is CCSID, a reason code is also provided. See
GDE003I DISTRIBUTED FILEMANAGER TARGET Character Data Representation Architecture (CDRA).
SYSTEM INITIALIZATION COMPLETE For example, RC=00010001 is used by CDRA to
indicate that the CCSID is undefined and RC=00060001
Explanation: Initialization of the Distributed
is used to indicate that the CDRA resource files needed
FileManager/MVS target function was successful.
for data conversion cannot be located.
System Action: The Distributed FileManager/MVS is
System Action: DFM will not be started. There is an
available for use.
exception when the keyword is CCSID and the return
Source: Distributed FileManager/MVS (DFM/MVS) code is X'FFFFFFFF', indicating that the Language
Environment required by CDRA is not present. DFM will
be started in a limited function mode that does not
GDE004E DISTRIBUTED FILEMANAGER TARGET support data conversion.
CENTRAL ADDRESS SPACE FAILED
{IN ASID=aaaaaaaa|ASID=aaaaaaaa System Programmer Response: Correct the DFMxx
REASON=bbbbbbbb} parmlib member with a correct value for the keyword.
Explanation: The main Distributed FileManager/MVS Source: Distributed FileManager/MVS (DFM/MVS)

address space, named DFM, ended abnormally in the
specified address space identifier (ASID).
GDE007E module ERROR INVOKING FUNCTION:
System Action: The Distributed FileManager/MVS function return_code reason_code
DSAS ends. The Distributed FileManager/MVS
Explanation: During DFM DataAgent processing the
conversation address spaces continue running. The
MVS function shown failed with the indicated return and
system logs the error in the logrec data set and
reason codes .
produces a dump in the SYS1.DUMPnn data set.
However, common errors have more specific text. For
example, if the DataAgent routine can’t be found in
reason for the failure and take corrective action. Other
JOBLIB, STEPLIB, or LPALIB, ″LOCATING MODULE
error messages precede this one. Refer to their
DataAgent_routine_name″ will be substituted for
documentation for corrective action. DFM must be
function, return_code, and reason_code.
restarted to restore full Distributed FileManager/MVS
target function. System Action: DFM DataAgent processing is
terminated.
Operator Response: Notify your System Programmer.

System Programmer Response: Refer to
documentation of the indicated function to determine the
meaning of the return and reason codes. Refer to the
job log for any related console messages that may have
occurred at the time of the error
Chapter 4. GDE Messages 171

Chapter 5. GFSA Messages
System Action: The Network File System ends.
GFSA320I NETWORK FILE SYSTEM SERVER
INITIALIZATION FAILED: text Operator Response: Before starting the Network File
System, both the OS/390 UNIX System Services MVS
Explanation: text can be:
and the TCP/IP address spaces must have successfully
v VIRTUAL STORAGE IS UNAVAILABLE, been started.
v MAPPING SIDE FILE NOT FOUND,
Source: DFSMSdfp and Network File System Server
v MAPPING SIDE FILE HAS INVALID SYNTAX OR
FORMAT,
GFSA322I OPENEDITION V_REG FAILED: RV=1
v ERROR OPENING/READING MAPPING SIDE FILE,
RC=h_digit1, RSN=h_digit2.
v SIDE FILE SPECIFIED BUT MAPPING IS
DIS-ALLOWED BY INSTALLATION, Explanation: The Network File System failed to
register.
v TASK IS NOT APF AUTHORIZED, or
v DFP LEVEL MUST BE DFSMS 1.2 OR HIGHER. In the message text:
h_digit1
The server could not be initialized. During server The return code from OpenEdition V_REG callable
initialization, the server: service.
Could not obtain virtual storage,
Was not loaded from an APF-authorized library, or h_digit2
Is running on a system with a release of DFP prior The reason code from OpenEdition V_REG callable
to OS/390 1.2. service.
System Action: The Network File System startup System Action: The Network File System ends.
ends. Operator Response: Contact the system programmer.
Operator Response: Notify the system programmer. System Programmer Response: See the OS/390
System Programmer Response: UNIX System Services File System Interface Reference
manual for addition details on the return code and
v If it is a virtual storage problem, increase the region
reason code from OpenEdition V_REG callable service.
size.
v If an APF-authorization problem, APF authorize all Source: OS/390 NFS Server
libraries in the STEPLIB DD statement.
v If mapping side file is not found, make sure the name GFSA323I OS/390 NETWORK FILE SYSTEM LOCK
specified in the attribute data set is correct and the MANAGER (HDZ11TS) WILL NOT
file exists. START BECAUSE OMVS(UID(0)) IS
v If mapping side file has invalid syntax, check the part NOT DEFINED.
GFSAPMAP in SYS1.NFSSAMP library for mapping Explanation: The Network Lock Manager initialization
side file rules. fails because the Network Lock Manager startup
v If error occurs during opening of the side file, check procedure is not defined as OMVS(UID(0)).
to make sure that the side file is not migrated and it
is readable. System Action: The Network Lock Manager
terminates.
v If sfmax=0 then the side file cannot be specified in
the attribute data set. User Response: Define Network Lock Manager
v If a back-level release of DFP, restart Network File startup procedure as OMVS(UID(0)).
System Server after installing DFSMSdfp 1.2 or a Operator Response: None
later release.
Source: OS/390 NFS server, GFSAPRMN
Source: OS/390 NFS server
GFSA324I OS/390 NETWORK FILE SYSTEM

GFSA321I NETWORK FILE SYSTEM SERVER STATUS MONITOR (HDZ11TS) WILL
INITIALIZATION FAILED: OPENEDITION NOT START BECAUSE OMVS(UID(0))
MVS ADDRESS SPACE HAS NOT IS NOT DEFINED.
BEEN STARTED.
Explanation: The Network Status Monitor initialization
Explanation: The Network File System was not able fails because the Status Monitor startup procedure is
to establish successful communication with the not defined as OMVS(UID(0)).
OPENEDITION MVS address space.

System Action: The Network Status Monitor
GFSA330I SERVER SHUTDOWN COMPLETE.
terminates.
Explanation: The system has ended the network file
User Response: Define Network Status Monitor
system server and its associated subtasks.
startup procedure as OMVS(UID(0)).
System Action: Network File System Server ends.
Operator Response: None
Source: OS/390 NFS server, GFSASMSV
GFSA325I REQUESTED MEMORY NOT
AVAILABLE. GFSA331E RECALL FAILED FOR MIGRATED DATA
SET text.
Explanation: An operation to allocate system memory
failed. If this condition persists, it is for one of the Explanation: DFSMShsm was unable to recall a data
following reasons: set because the data movement program DFSMSdss
v The value specified on the REGION parameter is too detected, during restore, that the migrated data set had
small. internal errors.
v The value specified on the BUFHIGH attribute is too In the message text:
large.
text
System Action: The system ends the request. The data set name.
Network File System Server processing continues.
System Action: The DFSMS/MVS NFS Server
Application Programmer Response: Do one or both processing continues.
of the following:
Operator Response: Notify System Programmer for
v Increase the region size for the job and step or recovery actions.
started task.
System Programmer Response: The data set text
v Decrease the value specified for the BUFHIGH
had an internal error when migrated, and cannot be
attribute of the attribute data set.
recalled. Refer to DFSMShsm Message ARC0075E for
Source: DFSMSdfp and Network File System Server appropriate recovery actions.
Source: DFSMS/MVS NFS Server
GFSA328I DFSMS/MVS 1.2.0 NETWORK FILE
Detecting Module: GFSASCAR
SYSTEM IS NOT APF AUTHORIZED.
Explanation: One or more of the data sets referenced
GFSA333I DFSMS/MVS version NETWORK FILE
by the STEPLIB DD statement is not authorized
SYSTEM SERVER fmid IS NOT
program facility (APF)-authorized.
STARTED BY A START COMMAND.
System Action: The system ends Network File
Explanation: The system programmer tried to start the
System Server startup processing.
Network File System Server with a command other than
Application Programmer Response: Authorize all START.
libraries in the STEPLIB DD statements.
version
The DFSMS/MVS version number, for example:
GFSA329I SERVER SHUTDOWN IN PROGRESS. 1.2.0 or VERSION 1.
Explanation: The system has started server shutdown fmid
procedures. The DFSMS/MVS Network File System Server
FMID started, for example: null, (HDZ11SP), or
System Action: The system continues Network File
(HDZ11SM).
System Server ending processing.
System Programmer Response: Start Network File
System Server by entering the START command.

Operator Response: Contact the system programmer.
GFSA334I MOUNT HANDLE DATABASE CANNOT
BE READ System Programmer Response: The mount handle
data sets probably created with incorrect attributes.
Explanation: The Network File System Server has
tried to read the mount handle database but was unable Detecting Module: GFSAXFHD
to do so. This could occur because the mount handle
database could not be opened or because it contained
a record whose length or contents were not valid. GFSA337I THE FILE SIZE IS TOO LARGE.
FN=text, OFFSET=h_digit1,
System Action: System processing continues but in a LEN=h_digit2.
degraded mode. Some or all of the directories will not
have been remounted. Explanation: The Network File System client user
tried to read or write the file text beyond the 4G.
Operator Response: Notify the system programmer.
System Action: The request is stopped. An error,
System Programmer Response: If this is the first NFSERR_FBIG(27), is returned to the client. Network
startup after installation of a new release, the mount File System processing continues.
handle database will have to be cleared and the server
restarted, because the format of the mount handle User Response: Check the file size used. Split into
database is not recognizable by the new release. multiple files and try again.
Reboot or unmount any previously mounted directories.
Source: DFSMSdfp and Network File System Server GFSA344I OS/390 NETWORK FILE SYSTEM LOCK
MANAGER (fmid) STARTED
GFSA335I MOUNT HANDLE DATA SET CANNOT Explanation: The Network File System Lock Manager
BE WRITTEN, EXPECTING LEN is initialized successfully and is started.
d_digits1 REAL LEN d_digits2, VSAM System Action: The Network File System Lock
R15(DEC) d_digits3 REASON Manager startup ends and continues processing.
CODE(DEC) d_digits4 LAST OP(DEC)
d_digits5. User Response: None.
Explanation: The Network File System Server has Detecting Module: The Network File System Lock
tried to write the mount handle data sets but was unable Manager
to do so.
System Action: System processing continues but in a GFSA345I OS/390 NETWORK FILE SYSTEM
degraded mode. Any further mounts or unmounts are STATUS MONITOR (fmid) STARTED
likely to fail. Explanation: The network File System Status
Operator Response: Contact the system programmer. Manager is initialized successfully.
System Programmer Response: The mount handle System Action: The Network File System Status
data sets have probably become unusable and either Manager startup ends and continues processing.
need to be cleared or restored to some previous level, User Response: None.
and then the server has to be restarted. Reboot or
unmount any previously mounted directories. Detecting Module: The Network File System Status
Monitor
GFSA346I time_stamp.
GFSA336E MOUNT HANDLE DATA SET CANNOT
BE OPENED, VSAM R15(DEC) d_digits1 Explanation: Displays the current time stamp. This
REASON CODE(DEC) d_digits2 LAST message is issued when the NFSLOG switches.
OP(DEC) d_digits3.
Explanation: During resource timeout, the Network GFSA347I ERROR RETURNED TO CLIENT: RC =
File System had tried to open the mount handle data d_digits<string>.
set for writing but unable to do so. The failing Explanation: The system found an error during
information in fopen the VSAM kSDS mount handle processing.
data set is the decimal return code d_digits1, the
decimal error code or reason code d_digits2, and the In the message text:
code for the last operation d_digits3.
d_digits
System Action: The Network File System stops. The error code returned by the system.
User Response: None string The meaning of the error code.
Chapter 5. GFSA Messages 175

System Action: The system continues processing.
GFSA361I NETWORK FILE SYSTEM SERVER IS
Application Programmer Response: None SHORT ON STORAGE.
Source: DFSMSdfp and Network File System Server Explanation: This message is displayed to the
operator console when a shortage of virtual storage is
detected.
GFSA348I DFSMS/MVS version NETWORK FILE
SYSTEM SERVER fmid STARTED. System Action: Network File System Server
continues processing. The storage constraint might be
Explanation: The system has initialized the network relieved when some storage is freed later.
file system server and is ready to accept MODIFY
commands from the operator console. Operator Response: If this message is displayed
repeatedly within a short period of time, stop or cancel
In the message text: Network File System Server and notify the system
version programmer.
The DFSMS/MVS version number, for example: System Programmer Response: Do one of both of
1.2.0 or VERSION 1. the following before restarting Network File System
fmid Server:
The DFSMS/MVS Network File System Server v Increase the region size for the step or started task.
FMID started, for example: null, (HDZ11SP), or v Decrease the value specified for the BUFHIGH
(HDZ11SM). attribute of the attribute data set.
System Action: The system continues processing. Source: DFSMSdfp and Network File System Server
Operator Response: Enter MODIFY commands.
Source: DFSMSdfp and Network File System Server GFSA362I REGION SIZE WILL NOT
ACCOMODATE BUFHIGH AND
LOGICAL CACHE SPECIFICATIONS.
GFSA349I UNEXPECTED ERROR DETECTED:
string. Explanation: The specifications for the BUFHIGH and
LOGICAL CACHE keywords are not valid.
Explanation: The network file system server has
encountered a condition that indicates continued In the message text:
processing will produce undesirable results. line_number
In the message text: The line number on which the specifications
exist.
string Additional debugging information for the
programming support personnel. System Action: The startup for Network File System
Server ends.
System Action: Network File System Server will either
shutdown or end the request and continue processing, System Programmer Response: Either increase the
depending on where the error was detected. region size of the job or reduce the value for BUFHIGH
and LOGICAL CACHE.
System Programmer Response: Contact the IBM
Support Center. Source: Network File System Server

GFSA400I INVALID RECFM SPECIFICATION string.
GFSA360I string. Explanation: string is the invalid record format

specified in the attribute data set.
Explanation: This message displays memory
management statistics. System Action: The system ends Network File
System Server processing.
Application Programmer Response: Correct the
string The memory management statistics. attribute data set.
System Action: The system continues processing. Source: DFSMSdfp and Network File System Server
Source: DFSMSdfp and Network File System Server GFSA401I CANNOT OPEN THE ATTRIBUTES
DATA SET.
Explanation: The server was unable to open the
attributes data set defined in the JCL for DDNAME
NFSATTR. The DD statement might be missing or the

data set name might be incorrect.
GFSA405I PARSE FAILED FOR ATTRIBUTE FIELD
System Action: The system ends Network File - ILLEGAL KEYWORD IN LINE d_digits.
Explanation: The keyword specified in line number
Application Programmer Response: Correct the JCL d_digits of the attribute data set is not a valid attribute
for DDNAME NFSATTR. Run the job again. keyword.
Source: DFSMSdfp and Network File System Server In the message text:
d_digits
GFSA402I READ FAILED FOR THE ATTRIBUTES The specified line number.
DATA SET.
Explanation: An error occurred while the network file System Server processing.
system server was processing the attributes data set.
This message follows other messages that describe the
attribute data set.
error in greater detail. The attributes data set is defined
in the JCL for DDNAME NFSATTR. Source: DFSMSdfp and Network File System Server
System Server processing. GFSA406I MISSING LEFT PARENTHESIS IN LINE
d_digits.
attributes data set. Explanation: An attribute specified on line number
d_digits of the attribute data set is missing a left
parenthesis.
GFSA403I PARSE FAILED IN LINE d_digits string.
d_digits
Explanation: The parsing of line number d_digits in
The specified line number.
the attribute data set failed. This message follows other
messages that describe the error in greater detail. System Action: The system ends Network File
d_digits
attribute data set.
string The actual line from the attribute data set that
contains the failure.
GFSA407I MISSING RIGHT PARENTHESIS IN LINE
d_digits.
Explanation: An attribute specified on line number
d_digits of the attribute data set is missing a right
attribute data set.
parenthesis.
d_digits
GFSA404I UNEXPECTED END OF STRING ON
END OF PARSE IN LINE d_digits.
Explanation: A comma is missing between attributes
on line number d_digits of the attribute data set.
attribute data set.
d_digits
GFSA408I PARSE FAILED ON NUMBER FIELD IN
LINE d_digits.
Explanation: An attribute with a negative number was
attribute data set.
specified on line number d_digits of the attribute data
Source: DFSMSdfp and Network File System Server set.

d_digits Source: DFSMSdfp and Network File System Server
System Action: The system ends Network File GFSA412I INVALID UNIT SPECIFICATION IN LINE
System Server processing. d_digits.
Application Programmer Response: Correct the Explanation: The unit specified in the UNIT attribute
attribute data set. on line number d_digits of the attribute data set is not
valid.
GFSA409I INVALID DSORG SPECIFICATION IN d_digits
LINE d_digits. The specified line number.
Explanation: The data set organization specified in System Action: The system ends Network File
the DSORG attribute on line number d_digits of the System Server processing.
attribute data set is not valid or is not supported by the
network file system server.
attribute data set.
d_digits
GFSA413I THE ATTRIBUTE VALUE d_digits1 IS
System Action: The system ends Network File NOT IN THE RANGE OF d_digits2 TO
System Server processing. d_digits3.
Application Programmer Response: Correct the Explanation: The value, d_digits1, specified in one of
attribute data set. the attributes of the attribute data set must be between
the minimum value, d_digits2, and the maximum value,
d_digits3, for this attribute. Message GFSA403I follows
this message.
GFSA410I INVALID MODEL SPECIFICATION IN
LINE d_digits.
d_digits1
Explanation: The data set specified in the MODEL
The specified value.
attribute on line number d_digits of the attribute data set
is not valid. d_digits2
The minimum specified value.
d_digits3
d_digits
The maximum specified value.
Application Programmer Response: See message
GFSA403I to determine the attribute in error, then
attribute data set.
correct the attribute data set.
GFSA411I INVALID VOL SPECIFICATION IN LINE

GFSA414I THE ATTRIBUTE VALUE d_digits1
d_digits.
EXCEEDS THE MAXIMUM VALUE OF
Explanation: The volume specified in the VOL or d_digits2.
VOLUME attribute on line number d_digits of the
Explanation: The value, d_digits1, specified in one of
attribute data set is not valid.
the attributes of the attribute data set must be less than
In the message text: or equal to d_digits2. Message GFSA403I follows this
message.
d_digits
The specified line number. In the message text:
System Action: The system ends Network File d_digits1

System Server processing. The specified value.
Application Programmer Response: Correct the d_digits2
attribute data set. The maximum value allowed for this attribute.

GFSA417I THE WRITE TIME OUT VALUE d_digits1
IS LESS THAN THE MINIMUM TIME
Application Programmer Response: See message OUT VALUE d_digits2.
GFSA403I to determine the attribute in error, then
Explanation: The value, d_digits1, specified in the
correct the attribute data set.
WRITETIMEOUT attribute of the attribute data set must
Source: DFSMSdfp and Network File System Server be greater than or equal to the value d_digits2 which
was specified in the MINTIMEOUT attribute of the
attribute data set.
GFSA415I THE ATTRIBUTE TIME OUT VALUE
d_digits1 IS LESS THAN THE MINIMUM In the message text:
TIME OUT VALUE d_digits2.
d_digits1
Explanation: The value, d_digits1, specified in the The specified value.
ATTRTIMEOUT attribute of the attribute data set must
d_digits2
be greater than or equal to the value d_digits2 which is
The minimum value allowed, as specified in the
specified in the MINTIMEOUT attribute of the attribute
MINTIMEOUT attribute.
data set.
d_digits1
attribute data set.
d_digits2
GFSA418I THE ATTRIBUTE TIME OUT VALUE
d_digits1 IS GREATER THAN THE
MAXIMUM TIME OUT VALUE d_digits2.
attribute data set.
ATTRTIMEOUT attribute of the attribute data set must
Source: DFSMSdfp and Network File System Server be less than or equal to the value d_digits2 which was
specified in the MAXTIMEOUT attribute of the attribute
data set.
GFSA416I THE READ TIME OUT VALUE d_digits1
IS LESS THAN THE MINIMUM TIME In the message text:
OUT VALUE d_digits2.
d_digits1
Explanation: The value, d_digits1, specified in the The specified value.
READTIMEOUT attribute of the attribute data set must
d_digits2
be greater than or equal to the value d_digits2 which
The maximum value allowed, as specified in
was specified in the MINTIMEOUT attribute of the
the MAXTIMEOUT attribute.
attribute data set.
d_digits1
attribute data set.
d_digits2
GFSA419I THE READ TIME OUT VALUE d_digits1
IS GREATER THAN THE MAXIMUM
TIME OUT VALUE d_digits2.
attribute data set.
READTIMEOUT attribute of the attribute data set must
Source: DFSMSdfp and Network File System Server be less than or equal to the value d_digits2 which was
data set.

d_digits1 NOMAXTIMEOUT attribute in the attribute data set.
The specified value. Correct the attribute data set.
d_digits2 Source: DFSMSdfp and Network File System Server
The maximum value allowed, as specified in
the MAXTIMEOUT attribute.
GFSA422I THE NOREADTIMEOUT ATTRIBUTE
System Action: The system ends Network File WAS SPECIFIED BUT THE
System Server processing. MAXTIMEOUT VALUE WAS SET TO
d_digits.
attribute data set. Explanation: The NOREADTIMEOUT attribute means
that the data set is not to be deallocated following a
read operation. The MAXTIMEOUT attribute specifies
the maximum time out value allowed for any of the
GFSA420I THE WRITE TIME OUT VALUE d_digits1 timeout attributes. These attributes are in conflict. The
IS GREATER THAN THE MAXIMUM NOREADTIMEOUT and MAXTIMEOUT attributes are
TIME OUT VALUE d_digits2. specified in the attribute data set.
Explanation: The value, d_digits1, specified in the In the message text:

WRITETIMEOUT attribute of the attribute data set must
d_digits
be less than or equal to the value d_digits2 which was
Specified as the MAXTIMEOUT value, in
seconds, that the data set is to remain
data set.
allocated.
d_digits1 System Server processing.
Application Programmer Response: If the
d_digits2 NOREADTIMEOUT attribute is desired, specify the
The maximum value allowed, as specified in NOMAXTIMEOUT attribute in the attribute data set.
the MAXTIMEOUT attribute. Correct the attribute data set.
System Action: The system ends Network File Source: DFSMSdfp and Network File System Server
Application Programmer Response: Correct the GFSA423I THE NOWRITETIMEOUT ATTRIBUTE
attribute data set. WAS SPECIFIED BUT THE
MAXTIMEOUT VALUE WAS SET TO
Source: DFSMSdfp and Network File System Server d_digits.
Explanation: The NOWRITETIMEOUT attribute
GFSA421I THE NOATTRTIMEOUT ATTRIBUTE means that the data set is not to be deallocated
WAS SPECIFIED BUT THE following a write operation. The MAXTIMEOUT attribute
MAXTIMEOUT VALUE WAS SET TO specifies the maximum time out value allowed for any of
d_digits. the timeout attributes. These attributes are in conflict.
Explanation: The NOATTRTIMEOUT attribute means The NOWRITETIMEOUT and MAXTIMEOUT attributes
that the data set is not to be deallocated following a are specified in the attribute data set.
LOOKUP or SHOWATTR operation. The MAXTIMEOUT In the message text:
attribute specifies the maximum time out value allowed
for any of the timeout attributes. These attributes are in d_digits
conflict. The NOATTRTIMEOUT and MAXTIMEOUT Specified as the MAXTIMEOUT value, in
attributes are specified in the attribute data set. seconds, that the data set is to remain
allocated.
d_digits System Server processing.
Specified as the MAXTIMEOUT value, in
seconds, that the data set is to remain Application Programmer Response: If the
allocated. NOWRITETIMEOUT attribute is desired, specify the
NOMAXTIMEOUT attribute in the attribute data set.
System Action: The system ends Network File Correct the attribute data set.
NOATTRTIMEOUT attribute is desired, specify the

GFSA424I MINIMUM TIME OUT VALUE, d_digits1, GFSA429I INVALID DSNTYPE SPECIFICATION IN
IS GREATER THAN THE MAXIMUM d_digits.
TIME OUT VALUE, d_digits2.
Explanation: The data set name type specified in the
Explanation: The value specified in the MINTIMEOUT DSNTYPE attribute on line number d_digits of the
attribute of the attribute data set is greater than the attribute data set is not valid.
value specified in the MAXTIMEOUT attribute of the
attribute data set.
d_digits
d_digits1
The value specified in the MINTIMEOUT
attribute.
d_digits2
attribute data set.
The value specified in the MAXTIMEOUT
attribute. Source: DFSMSdfp and Network File System Server
System Server processing. GFSA430I INVALID SMS_keyword SPECIFICATION
IN LINE line_number.
attribute data set. Explanation: The SMS keyword shown is syntactically
incorrect. Refer to SMS documentation for DATACLAS,
MGMTCLAS, and STORCLAS naming conventions.
System Action: Network File System Server startup
GFSA425I INVALID SPECIFICATION
ends if the keyword was specified as a site attribute. If
RECFM(string).
the incorrect SMS keyword was specified by a client as
Explanation: One of the characters in string specified a mount parameter or on a command, the line number
on the RECFM attribute of the attribute data set is not is set to zero and an I/O error is returned to the client.
valid.
In the message text: attributes data set.
string The RECFM attribute specification. Source: DFSMSdfp and Network File System Server
System Server processing. GFSA431I INVALID OPTION SPECIFICATION OF
string IN LINE d_digits.
attribute data set. Explanation: The option specified in the string
attribute on line number d_digits of the attribute data set
is not valid.
GFSA426I INVALID RECFM(string) - MUST
SPECIFY U, F, OR V. System Programmer Response: Correct the site
attributes file, if applicable.
Explanation: One of the characters in string specified
on the RECFM attribute of the attribute data set must Source: DFSMSdfp and Network File System Server
define whether the records are fixed length (F), variable
length (V), or undefined format records (U).
GFSA434I string1(d_digits1) IS SET TO THE
In the message text: DEFAULT VALUE,
string1(d_digits2,d_digits3).
string The RECFM attribute specification.
Explanation: string1(d_digits1) is the value from the
previous release. This value could not be applicable to
the new release. For forward compatibility, this value
Application Programmer Response: Correct the takes on the default value for the new release.
attribute data set.
System Action: Network File System Server
Source: DFSMSdfp and Network File System Server processing continues.

GFSA435E SUM OF d_digit1 PLUS d_digits2 MUST GFSA439I HFS PUBLIC PATHNAME SPECIFIED
BE LESS THAN OR EQUAL TO d_digits BUT HFS IS NOT ENABLED
Explanation: The sum of d_digit1 plus d_digit2 is Explanation: An HFS public pathname was specified
greater than d_digits. This is not allowed. in the public keyword but nohfs was also specified
which disables HFS processing.
processing stops. System Action: The Network File System server
startup ends.
System Programmer Response: Correct the values.
Operator Response: Correct the problem and make
the necessary changes in the installation table.
Source: GFSAFNPA
GFSA436I INVALID SIDEFILE SPECIFICATION IN
LINE d_digits
GFSA440I INVALID SECURITY SPECIFICATION IN
Explanation: A data set name was not specified in the
d_digits
sidefile attribute.
Explanation: The parsing of the security keyword
System Action: The Network File System server
resulted in error for one of the following reasons.
startup ends.
v Missing first parameter
System Programmer Response: Correct the problem
v Invalid first parameter specified
and make necessary changes in the attribute data set.
System Action: The Network File System server
Source: GFSAFNPA
startup ends.
GFSA437I INVALID PUBLIC SPECIFICATION IN
necessary changes in the attributes data set.
LINE d_digits
Source: GFSAFNPA
Explanation: The parsing of the public keyword
resulted in error for one of the following reasons:
v public keyword specification is syntactically incorrect GFSA450I CREATED TASK (h_digits) - string1 -
string2.
v No public pathnames have been specified
v Pathname specified is invalid Explanation: The network file system server is
creating the number of tasks requested in the
v HFS public pathname does not match HFS prefix
NFSTASKS attribute of the attribute data set. This
System Action: The Network File System server message is displayed for each task created.
startup ends
h_digits
the necessary changes in the attributes dataset.
The task control block (TCB) address.
Source: GFSAFNPA
string1 The task name.
string2 The module name.
GFSA438I EXPORT SPANNING PATHNAMES NOT
SUPPORTED System Action: The system continues processing.
Explanation: The Export Spanning Pathnames Application Programmer Response: None
support for a multi-component lookup request is not
supported.
System Action: The request fails. Network File
GFSA451I DELETING TASK(h_digits) - string.
System processing continues.
Explanation: The network file system server is
User Response: Construct a different pathname in
deleting a task. This is in response to the STOP
which the path is not spanned
operand of the MODIFY command. This message is
Operator Response: None displayed for each task deleted.
Source: GFSAFNPA In the message text:
h_digits
The task control block (TCB) address.
string The module name.

System Action: The system continues end processing System Action: ESTAE processing ends. The
for Network File System Server. Network File System Server address space might also
end.
Application Programmer Response: None
Operator Response: Restart the Network File System
Server address space. Notify network users of the
failure.
GFSA452I SUBTASK TERMINATED: h_digits.
Explanation: The network file system server is ending Support Center. Provide a symptom string, the related
a task. This is in response to the STOP operand of the logrec data set entries, any related SVC dumps, and the
MODIFY command. This message is displayed for each Network File System Server error trace log.
task terminated.
h_digits GFSA501I REQUEST HEADER ALLOCATION
The task control block (TCB) address. FAILED.
System Action: The system continues end processing Explanation: An operation to allocate system memory
for Network File System Server. for a request header was attempted, but was
unsuccessful.
System Action: The system ends the request. The
Source: DFSMSdfp and Network File System Server system continues processing for Network File System
Server.
GFSA470I NETWORK FILE SYSTEM SERVER SVC Application Programmer Response: Increase the
DUMP REQUEST FAILED. size of the job and step region.
REASON=reason_code.
Explanation: A request to take an SVC dump failed.
In the message text: GFSA502I REQUEST HEADER DATA BLOCK
reason_code ALLOCATION FAILED.
A hexadecimal value indicating the reason Explanation: An operation to allocate system memory
MVS was unable to take the dump. See the for a request header data block was attempted, but was
description of the SDUMP macro in OS/390 unsuccessful.
MVS Programming: Authorized Assembler
Services Reference LLA-SDU. System Action: The system ends the request. The
system continues processing for Network File System
System Action: Abend processing continues. Server.
Operator Response: If the dump could not be taken Application Programmer Response: Increase the
due to an operational procedure and a dump is size of the job and step region.
necessary to diagnose the failure, correct the
procedure. Source: DFSMSdfp and Network File System Server
System Programmer Response: If the failure

appears to be due to an Network File System Server GFSA554I REGISTER FOR PORT d_digits1
error, contact the IBM Support Center. Provide a PROGRAM d_digits2 - VERSION
symptom string and a copy of the console log. d_digits3 - FAILED.
Source: DFSMSdfp and Network File System Server Explanation: During processing of the network file
system server , the system found an unexpected error.
GFSA471I NETWORK FILE SYSTEM SERVER In the message text:

ESTAE EXIT UNABLE TO COMPLETE
d_digits1
PROCESSING. ABEND=abend-code.
The port number.
Explanation: The Network File System Server for
d_digits2
DFSMS/MVS 1.1.0 ESTAE exit routine abended and is
The RPC program number.
unable to complete processing.
d_digits3
The RPC program version number.
abend-code
Set to the last abend code encountered by a
secondary instance of the ESTAE exit routine.

Application Programmer Response: Contact the IBM Source: DFSMSdfp and Network File System Server
Support Center.
Source: DFSMSdfp and Network File System Server GFSA558I UNABLE TO CREATE IPC QUEUE.
Explanation: An operation to allocate system memory
GFSA555I REGISTER FOR PORT d_digits1 for an IPC queue was attempted, but was unsuccessful.
PROGRAM d_digits2 - VERSION
d_digits3 - SUCCESSFUL.
Explanation: The register for the specified port was Server.
successful.
Application Programmer Response: Increase the
In the message text: size of the job and step region.
d_digits1 Source: DFSMSdfp and Network File System Server
The port number.
d_digits2 GFSA559I CANNOT CREATE UDP SERVICE.
Explanation: UDP service transport could not be
d_digits3 created, or you started TCP/IP before the _ initialization
The RPC program version number. was completed.
System Action: The system ends Network File System Action: The Network File System stops.
Operator Response: Check your MVS TCP/IP setup
Application Programmer Response: None or notify your system programmer. Before starting
TCP/IP, make sure that the _ initialization has
completed, and the TCP/IP-_ connection is established.
System Programmer Response: Check your MVS
GFSA556I UNREGISTER PROGRAM d_digits1
TCP/IP setup. Also check your _ BPXPRMxx parmlib
VERSION d_digits2 - FAILED.
member, specifically the MAXFILEPROC,
Explanation: During processing for the network file MAXSOCKETS, INADDRANYPORT, and
system server , the system found an unexpected error. INADDRANYCOUNT. The INADDRANYPORT and
INADDRANYCOUNT must be specified, but its range
In the message text: cannot include 2049, in order for the server to initialize.
d_digits1 See OS/390 MVS Initialization and Tuning Guide for
The RPC program number. more details.
d_digits2 Source: OS/390 NFS server

System Action: The system continues processing. GFSA561I UNABLE TO REGISTER (PROG:
d_digits1 VERS: d_digits2, UDP).
Application Programmer Response: Contact the IBM
Support Center. Explanation: The specified program number and
version number failed to register with the service
Source: DFSMSdfp and Network File System Server dispatch routine.
GFSA557I UNREGISTER PROGRAM d_digits1
VERSION d_digits2 - SUCCESSFUL. d_digits1
The specified program number.
Explanation: The processing for the unregister
program was successful. d_digits2
The specified version number.
d_digits1 System Server processing.
Application Programmer Response: Contact the IBM
d_digits2 Support Center.
System Action: The system continues processing for
Network File System Server.

System Programmer Response: Determine what has
GFSA564I NETWORK SERVICE IS UNAVAILABLE.
caused the non-zero return code from SMF. Correct the
Explanation: If the port mapper or the transmission problem, and have the operator issue a MODIFY
control protocol/internet protocol (TCP/IP) is not running, command specifying SMF=ON.
the Network File System Server will fail to initialize.
System Action: The startup of Network File System
Server ends.
GFSA752I SMF PROCESSING ACTIVE FOR FILE
System Programmer Response: Ensure that both the TIMEOUT
port mapper and the TCP/IP are operational.
Explanation: SMF processing is active for file timeout
Source: Network File System Server records. This message is displayed in response to the
status operand on the MODIFY command.
GFSA566I CANNOT ACCEPT NEW TCP CLIENT System Action: Network File System Server
CONNECTION — MAXIMUM NUMBER processing continues.
OF SOCKETS HAS REACHED
Explanation: When an NFS TCP client attempts to
connect to the OS/390 NFS server, the server cannot
GFSA753I SMF PROCESSING SUSPENDED FOR
accept the connection because the maximum number of
FILE TIMEOUT
sockets has been reached.
Explanation: SMF processing is suspended for file
System Action: The connection request fails. Network
timeout records. This message is displayed in response
File System processing continues.
to the status operand on the MODIFY command, or
User Response: after receiving a non-zero return code from SMF. See
message GFSA754I for the SMF return code.
Operator Response: Increase the value of
MAXSOCKETS for AF_INET domain in the BPXPRMxx System Action: Network File System Server
parmlib member so that client TCP connections can be processing continues without generating any user or file
accepted by the OS/390 NFS server. Please refer to SMF records.
OS/390 UNIX System Services Planning manual for
Operator Response: Notify the system programmer if
more information.
this message was received as a result of a non-zero
Source: GFSATCPT return code from SMF.
System Programmer Response: Determine what has
GFSA750I SMF PROCESSING ACTIVE FOR USER caused the non-zero return code from SMF. Correct the
LOGOUT problem, and have the operator enter a MODIFY
command specifying SMF=ON.
Explanation: SMF processing is active for user logout
records. This message is displayed in response to the Source: DFSMSdfp and Network File System Server
status operand on the MODIFY command.
System Action: Network File System Server GFSA754I UNEXPECTED RETURN CODE d_digits
processing continues. RECEIVED FROM SMF WHILE
WRITING RECORD TYPE 42 SUBTYPE
[7|8].
Explanation: The Network File System Server
GFSA751I SMF PROCESSING SUSPENDED FOR
received a non-zero return code d_digits while
USER LOGOUT
processing a file timeout (subtype 7) or user logout
Explanation: SMF processing is suspended for user (subtype 8) record.
logout records. This message is displayed in response
to the status operand on the MODIFY command, or
processing continues. No more SMF records of the
after receiving a non-zero return code from SMF. See
same type and subtype are generated until the Network
message GFSA754I for the SMF return code.
File System Server address space is re-started, or the
System Action: Network File System Server SMF=ON operand of the MODIFY command is entered.
processing continues without generating any user or file
SMF records.
System Programmer Response: See OS/390 MVS
Operator Response: Notify the system programmer if
System Management Facilities (SMF) for information
this message was received as a result of a non-zero
about the return code. Correct the problem, and have
return code from SMF.

the operator enter a MODIFY command specifying System Action: The request is stopped. Network File
SMF=ON. System processing continues.
Source: DFSMSdfp and Network File System Server System Programmer Response: Check the SAF
security product user profiles.
GFSA770I OS/390 UNIX REGISTRATION
SUCCESSFUL. GFSA782I NO ACTIVE HFS MOUNT POINTS.
Explanation: Connection with _ established. Explanation: This message is in response to the
list=mounts operand of the MODIFY command and
System Action: Network File System processing
shows that there are no OS/390 UNIX System Services
continues.
clients connected to the Network File System.
GFSA771I UNIX System Services MVS HFS
continues.
MOUNTS SUSPENDED.
Explanation: Mount requests to HFS file systems
have been disabled. Given in response to a console
MODIFY command. GFSA783I NO ACTIVE HFS DATA SETS.
System Action: Network File System processing Explanation: This message is in response to the
continues. list=dsnames operand of the MODIFY command and
shows that there are no clients actively accessing HFS
data sets.
GFSA772I UNIX System Services MVS HFS
continues.
MOUNTS RESUMED.
have been enabled. Given in response to a console
MODIFY command. GFSA784I text1 RPC OS/390 UNIX ERROR
VNODE_OP text2 RC: number1: text3
RSN: number2 number3.
continues.
Explanation: The Network File System has
encountered a problem on an interface call with _. The
error was encountered during processing of a text1 rpc
GFSA776I UNIX System Services MVS CANNOT call. text2 is the function called when failure occurred.
RESOLVE PATH NAME text. number1 is the return code and text3 is the English
description of the return code. The combination of
Explanation: Failure to resolve a path name with number2 number3 represents the reason code as
OS/390 UNIX System Services, when initializing from returned by _. Refer to _ documentation for a full
the mount handle data sets. The HFS file system has explanation of OpenEdition MVS reason codes (for
been removed or renamed. If the user attempts to example, OS/390 UNIX System Services Programming:
access a file object under this mount point, the Network Assembler Callable Services Reference).
File System error response NFSERR_STALE is
returned. System Action: The Network File System continues
processing.
System Programmer Response: Refer to the _
text documentation.
The unresolved path name.
System Action: Network File System processing GFSA786I MULTI-COMPONENT LOOKUP
continues. REQUEST FOR PATHNAME text
Source: DFSMS/MVS NFS Server CANNOT BE RESOLVED.
Explanation: The multi-component lookup request for
GFSA777I OS/390 UNIX SERVICE REQUESTER the path name failed. Possible reasons are:
DOES NOT HAVE SECURITY v Symbolic links cannot be embedded in a
PRIVILEGE. multi-component path name as it is not supported at
this time
Explanation: The client user must be defined to RACF
as a user of OpenEdition MVS to access HFS file v Pathname specified is either not supported or access
objects. is not allowed

v Public path is not set up on this server. Source: DFSMSdfp and Network File System Server
System Action: The request fails. Network File
System processing continues. GFSA812I FLUSH FAILED: RC d_digits1 OFFSET
d_digits2 WAS DROPPED FOR DATA
User Response: Construct a different lookup request
SET string1(string2).
with a valid path name.
Explanation: When the network file system server
was trying to flush cached data at data set close time,
the system detected an error. The data at offset
GFSA801I MOUNT FAILED: text d_digits2 was discarded. This error message follows
more specific error messages.
Explanation: The text can be:
v FILE MAPPING ENABLED BUT NO SIDE FILE In the message text:
SPECIFIED, d_digits1
v STORAGE LIMIT REACHED LOADING MAPPING The specified return code.
SIDE FILE,
d_digits2
v MAPPING SIDE FILE NOT FOUND, The offset at which the data was discarded.
v ERROR OPENING/READING MAPPING SIDE FILE,
string1 The data set that was dropped.
v MAPPING SIDE FILE HAS INVALID SYNTAX OR
FORMAT, or string2 The member of the data set.
v SIDE FILE SPECIFIED BUT MAPPING IS System Action: The data set is closed. The system
DIS-ALLOWED BY INSTALLATION. continues processing for Network File System Server.
User Response: Application Programmer Response: See the
v Specify a side file if fileextmap is ON, or message preceding this message to determine the
correct action. The data set might be incomplete.
v Fix problem with mapping side file, or
v Consult the system administrator to change sfmax Source: DFSMSdfp and Network File System Server
value and re-issue the MOUNT command.
GFSA813I REMOVE FAILED: RC d_digits DSN
GFSA802E REMOUNT FAILED — PHYSICAL FILE string1(string2).
SYSTEM CHANGED. PATH: pathname Explanation: The error was detected when trying to
PREV: datasetname CURRENT: remove member string2 from data set string1.
datasetname
Explanation: During restart of the Network File
System server, rebuild of the mount point recorded in d_digits
the Mount Handle Database failed. The failure occurred The specified return code.
because the physical file system for the mount point string1 The data set.
was changed by a TSO UNMOUNT since the mount
point was originally mounted. string2 The member being removed.
System Action: Network File System server System Action: The system continues processing for
processing continues. Network File System Server.
Source: GFSAPHFS Application Programmer Response: None
GFSA811I CANNOT FLUSH PARTIAL RECORDS
FOR DATA SET. string1(string2): FB
GFSA814I RENAME FAILED: RC d_digits DSN
h_digits
string1 OLDMEM string2 NEWMEM
Explanation: There was not enough memory to string3.
allocate storage required to flush partial records to the
Explanation: The error was detected when trying to
data set at data set close time. The partial record was
rename member string2 to string3 in data set string1.
discarded.
System Action: The data set is closed. The system
continues processing for Network File System Server. d_digits
The specified return code.
size of the job and step region. The data set might be string1 The data set name.
incomplete.

string2 The member name of the old member. Byte 3: DADSM rename return code.
string3 The member name of the new member. 02 Error cataloging new data set name.
System Action: The system continues processing for Byte 1: Recatalog return code for old data set
Network File System Server. name.
Application Programmer Response: None Byte 2: DADSM rename return code for old
data set name.
Byte 3: Catalog return code for new data set
name.
GFSA815I RENAME FAILED: RC d_digits OLDDSN
string1 VOL string2 UNIT h_digits
Catalog and DADSM rename return codes are
NEWDSN string3.
documented in OS/390 DFSMSdfp Storage
Explanation: The error was detected when trying to Administration Reference. Message IEC614I is written
rename data set string1 to string3. for DADSM rename errors and contains further
diagnostic codes. These codes are documented in
OS/390 DFSMSdfp Diagnosis Reference.
d_digits
The specified return code.
string1 The data set name of the old data set.
GFSA816I HOST NAME OF IP ADDRESS (d_digits)
string2 The volume name. WAS NOT FOUND BY TCP/IP.
h_digits Explanation: The client host name of the specified IP

The unit number. address is not defined in either the TCP/IP Domain
Name Server or the TCP/IP Site Table. SeeOS/390 IBM
string3 The data set name of the new data set. Communications Server: IP Migration for more
System Action: The system continues processing for information.
Network File System Server. In the message text:
System Programmer Response: h_digits1 is a d_digits
composite of one or more error return codes The specified IP address.
encountered when trying to rename the data set. The
hexadecimal digits are decoded using the list below. System Action: Network File System Server
processing continues. The dotted IP address is used as
Renaming a data set requires three steps: the host name.
1. Uncatalog the old data set name.
2. Rename the data set in the disk VTOC. Application Programmer Response: Insert this
3. Catalog the new data set name. client’s host entry into either the TCP/IP Domain Name
Server or the TCP/IP Site Table.
Should an error occur in either of the last two steps, the Source: Network File System Server
prior steps are undone to preserve the old data set
name.
GFSA817I string1 REQUEST NOT VALID ON ALIAS
Find the step that failed by matching the value in byte NAME string2
zero of the return code with the values under the Explanation: A REMOVE (RM or RMDIR) or
heading byte 0 below. Byte three contains the return RENAME (MV) request was attempted while using an
code from the first failing MVS/DFP service alias name. The true file name is required.
(Uncatalog/catalog or DADSM rename). If subsequent
errors occur when attempting to recatalog and/or In the message text:
rename the data set back to the old name, the return
string1 Either REMOVE or RENAME.
codes are placed in bytes one and two.
string2 MVS Access Method Services alias name of a
Byte 0 Explanation/Other Bytes
file which also has a true name.
00 Error uncatalog old data set name.
System Action: The request ends. An I/O error
Byte 3: Uncatalog return code. indication is returned. Network File System Server
processing continues.
01 Error renaming the data set.
User Response: Provide the true name of the file on
Byte 1: Recatalog return code for old data set the request.
name.

16 Serializing the DASD volume. See OS/390
GFSA818I EXPORTS: NO VALID HOST NAMES IN
MVS Programming: Authorized Assembler
string LIST.
Services Reference LLA-SDU for the
Explanation: None of the client host names in the RESERVE macro.
READ/WRITE or ACCESS list are defined to the
20 Reading the DSCB. See OS/390 DFSMSdfp
network.
Storage Administration Reference for the
In the message text: CVAFDIR macro.
string Either the READ/WRITE or the ACCESS list. 24 Writing the DSCB. See OS/390 DFSMSdfp
Storage Administration Reference for the
System Action: Network File System Server does not
CVAFDIR macro.
export the associated directory.
System Programmer Response: Correct the host
names in the EXPORTS file or have the host names
defined to the network. Source: DFSMSdfp and Network File System Server
Source: Network File System Server
GFSA822I UNABLE TO PERFORM FILE MAPPING
BECAUSE NO SIDE FILE SPECIFIED
GFSA820I CATALOG ERROR OCCURRED WHILE
OR LOADED
[RETRIEVING|UPDATING] CATALOG
INFORMATION FOR string. RETURN Explanation: File mapping cannot be performed
CODE IS d_digits1, REASON CODE IS because a side file was not specified either as a default
cc-d_digits2. or at the mount point.
Explanation: Catalog Management module IGG0CLcc System Action: Operation fails
returned this return code, d_digits1, and reason code,
User Response: Specify a side file in the mount
d_digits2, as the result of a catalog error or an
command.
exception condition. string was the name of the data set
that the retrieve or update operation was performed System Programmer Response: Specify a side file in
against. the attributes data set.
System Action: Network File System Server Source: GFSAXFB GFSAARDR
System Programmer Response: See message GFSA823I PUBLIC PATH CANNOT BE
IDC3009I for specific return and reason code ESTABLISHED.
information.
Explanation: The public pathname(s) specified in the
Source: DFSMSdfp and Network File System Server public keyword cannot be established during server
startup. This could be because the path is not exported
or it does not exist.
GFSA821I ERROR OCCURRED WHILE UPDATING
THE FORMAT 1 DSCB FOR string1 ON System Action: The Network File System server
string2. FUNCTION CODE IS d_digits1, startup ends.
RETURN CODE IS d_digits2, REASON
CODE IS d_digits3. Operator Response: Make sure the public pathname
exist and is exported if export list checking is enabled.
Explanation: string1 is the name of the data set and Correct the problem and restart the server.
string2 is the volume serial number of the volume on
which the data set resides. The function code can be Source: GFSAMCMN
one of the following:
2 De-serializing the UCB. See OS/390 MVS GFSA827I REQUEST h_digits CREDENTIALS
Programming: Authorized Assembler Services ALLOCATION FAILED.
Reference SET-WTO for the UCBPIN macro. Explanation: An operation to allocate system memory
4 De-serializing the DASD volume. See OS/390 for a credentials block was attempted, but was
MVS Programming: Authorized Assembler unsuccessful.
Services Reference ALE-DYN for the DEQ In the message text:
macro.
h_digits
12 Searching for the UCB. See OS/390 MVS The request block address.
Programming: Authorized Assembler Services
Reference SET-WTO for the UCBLOOK macro. System Action: The system ends the request. The

system continues processing for Network File System h_digits
Server. The request block address.
Application Programmer Response: Increase the string The specified member name of data set name.
size of the job and step region.
Source: DFSMSdfp and Network File System Server system continues processing for Network File System
Server.
GFSA829I REQUEST h_digits INVALID User Response: Correct the error and resubmit the
CREDENTIALS FLAVOR d_digits. request.
Explanation: Incorrect credentials flavor received from Source: DFSMSdfp and Network File System Server
client. Probable client software error. The network file
system server supports UNIX and non-authentication
GFSA840I DYNAMIC ALLOCATION FAILED WITH
styles.
RETURN CODE d_digits FOR DATA SET
In the message text: string1(string2).
h_digits Explanation: A dynamic file allocation error occurred.
The request block address.
d_digits
d_digits
The incorrect credentials flavor.
The dynamic allocation return code.
string1 The data set name.
Server. string2 The member name, if any.
Application Programmer Response: Inform the client System Action: The system ends the request. The
user that the credentials used are not valid. system continues processing for Network File System
Server.
Application Programmer Response: This message
is preceded by either message GFSA853I or GFSA854I.
GFSA832I REQUEST h_digits INVALID
See the programmer response for the message that
MEMBERNAME FOR string.
precedes this message to determine the appropriate
Explanation: The member name of a partitioned data action.
set (PDS) was specified as a file name by the user, but
the file name specified was incorrect or not found in the
PDS.
GFSA842I string UNSUPPORTED DSORG {ISAM |
UNKNOWN}
h_digits
Explanation: The data set organization of data set
string1 is not supported by the network file system
string The specified member name. server.
System Action: The system ends the request. The In the message text:
string The unsupported data set organization.
Server.
User Response: Correct the error and resubmit the
request.
Server.
User Response: Correct the error and resubmit the
job.
GFSA833I REQUEST h_digits PARSE FAILED FOR
string.
Explanation: The member name of a partitioned data
GFSA843I CREATE FAILED FOR string.
set (PDS) or a data set name that was specified as a
file name by the user was incorrect, not found in the Explanation: An error occurred while the network file
PDS, or was an incorrect or nonexistent data set. system server was trying to create the specified data
set. This message follows other messages that describe
the error in greater detail.

string The specified data set name.
GFSA850I FILE string EXISTS.
Explanation: The user attempted to rename a file to
the target name string. A file named string already
Server.
exists.
Application Programmer Response: See the
messages preceding this message to determine the
appropriate response. string The file name.
Source: DFSMSdfp and Network File System Server System Action: The system ends the request. An
error is returned to the user. The system continues
processing for Network File System Server.
GFSA847I IDCAMS ERROR: text.
User Response: Check the filename used. Correct it
Explanation: text is an access method services error
and file it again.
message.
System Action: The request is stopped. Network File
System processing continues.
GFSA851I FILE string DOES NOT EXIST.
System Programmer Response: See OS/390 MVS
System Messages, Vol 3 (EWX-IEB) for more Explanation: The user attempted to rename or
information on the access method services error remove a file that does not exist.
message.
string The specified file name.
GFSA848I PDS string IS NOT EMPTY.
System Action: The system ends the request. An
Explanation: The network file system server user
entered a RMDIR (remove directory) AIX/UNIX
command to remove a partitioned data set (PDS) that
was not empty. The system requires the directory (PDS) User Response: Check the filename used. Correct it
to be empty before it is removed. and attempt to rename or remove the file again.
In the message text: Source: DFSMSdfp and Network File System Server
string The name of the PDS.
GFSA853I DYNAMIC ALLOCATION: INPUT
VALIDATION ROUTINE REJECTED
ALLOCATION.
Explanation: Dynamic allocation failed when issued
User Response: Remove all files in the directory then
by the installation input validation routine. Probable
resubmit the RMDIR request.
installation configuration errors.
GFSA849I NEW AND OLD FILES ARE NOT Server.
MEMBERS OF THE SAME PDS.
Application Programmer Response: See the input
Explanation: Rename is not allowed for a member of validation documentation for more information on the
a partitioned data set (PDS) when the target name is input validation routine.
not in the same PDS.
GFSA854I DYNAMIC ALLOCATION: RC=d_digits
ERROR=h_digits1 INFO=h_digits2: string.
User Response: Check the filename used. Correct it
Explanation: Dynamic allocation processing failed.
and resubmit the request.
d_digits
The return code.
h_digits1
The error reason code.

h_digits2
GFSA860I WRITE FAILED RC d_digits FOR DATA
The information reason code.
string The description of the interrupted dynamic
Explanation: An error occurred while trying to write
allocation request.
the specified data set.
Server. d_digits
The return code.
dynamic allocation documentation for more information string1 The data set name.
about these codes.
string2 The member name, if any.
GFSA858I OPEN FAILED RC d_digits FOR DATA Server.
Application Programmer Response: If this error was
Explanation: An error occurred while trying to open not caused by an out-of-memory condition, contact the
the specified data set. IBM Support Center.
In the message text: Source: DFSMSdfp and Network File System Server
d_digits
The return code. GFSA862I CATALOG string COULD NOT BE
LOCATED.
Explanation: The user catalog that contains the entry
for an index could not be located. The catalog does not
System Action: The system ends the request. The exist or is not mounted. If it does not exist, the entry in
system continues processing for Network File System the master catalog may be incorrect.
Server.
string The user catalog name.
not caused by an out-of-memory condition, contact the
IBM Support Center. System Action: The system continues processing for
GFSA859I READ FAILED RC d_digits FOR DATA Source: DFSMSdfp and Network File System Server
Explanation: An error occurred while trying to read GFSA863I READDIR ON ROOT IS NOT ALLOWED.
the specified data set.
Explanation: The user attempted to list the contents
In the message text: of the master catalog.
d_digits System Action: The system ends the request. The
The return code. system continues processing for Network File System
Server.
Server. GFSA864I CANNOT OPEN THE EXPORTS DATA
SET.
not caused by an out-of-memory condition, contact the Explanation: The server was unable to open the
IBM Support Center. exports file defined in the JCL for DDNAME EXPORTS.
The DD statement might be missing or the data set
name might be incorrect.

Application Programmer Response: Correct the JCL
GFSA868I EXPORTS: HOST (string) WITH
for DDNAME EXPORTS.
UNKNOWN ADDRESS TYPE (d_digits)
Source: DFSMSdfp and Network File System Server HAS BEEN IGNORED.
Explanation: The host named string has an IP
GFSA865I EXPORTS: UNEXPECTED OPTION address that is not valid.
(string)—SHUTDOWN SCHEDULED.
Explanation: The option information provided in string
string The host name.
is incorrect. This error could occur as a result of
unexpected blanks, incorrect syntax, or the use of d_digits
mutually exclusive options. The IP address.
In the message text: System Action: The system continues processing for
string The specified option.
System Action: Checking of the EXPORTS file
EXPORTS file.
continues, but the system will end Network File System
Server when checking is complete. Source: DFSMSdfp and Network File System Server
EXPORTS file and restart Network File System Server. GFSA869I EXPORTS: UNKNOWN HOST (string)
HAS BEEN IGNORED.
Explanation: The client host named string is not
defined to the network.
GFSA866I EXPORTS: DIRECTORY string WAS
NOT EXPORTED. In the message text:
Explanation: An error was encountered severe string The host name.
enough to prevent the data set or index from being
exported. This message follows a more specific error
Network File System Server. If this undefined client host
message.
is the only host specified for an RW or ACCESS option
In the message text: in the EXPORTS file, the Network File System Server
does not export the associated directory. If there are
string The name of the data set or index.
other defined client hosts specified for the option,
System Action: The system continues processing for Network File System Server ignores this undefined
Network File System Server. client host.
Application Programmer Response: Correct the Application Programmer Response: Correct the host
EXPORTS file. name in the EXPORTS file or have this host name
defined to the network.
GFSA867I EXPORTS: string1 CANNOT BE

EXPORTED BECAUSE string2 GFSA871I REQUEST h_digits HAS MISMATCHED
ALREADY IS. UID: CRED = d_digits1 ARGS =
d_digits2.
Explanation: The data set or index named in string1
is a parent directory or a subdirectory of the data set or Explanation: A request was attempted with
index named in string2 which is already exported. mismatched ID numbers. The userid numbers do not
match the credential id numbers.
string1 The name of the data set or index that is a
parent or subdirectory of string2. h_digits
A block created for the logon or logout request.
string2 The name of the data set or index already
exported. d_digits1
Represents the credential user ID number.
Network File System Server. d_digits2
Represents the client user ID number.
EXPORTS file. System Action: The system ends the request. The

system continues processing for Network File System System Programmer Response: A Data
Server. Management message should have been displayed on
the console. See OS/390 MVS System Messages, Vol 2
Application Programmer Response: Inform the
(ASB-ERB) for more information on the Data
Network File System Server client that the credentials
Management error message.
used are not valid.
GFSA881I FUB: h_digits1 UNABLE TO ACCESS
FILE string1 (string2) OWNED BY FUB
GFSA876I I/O ERROR ON DSN=string1(string2) h_digits2.
SENSE. h_digits1 IOBCSW h_digits2
Explanation: A user has attempted to access a data
h_digits3. ACCESS METHOD RC =
set already locked internally by the network file system
h_digits4 ACCESS METHOD RSN =
server for writing by another user. The data set has not
h_digits5
been released yet.
Explanation: The physical I/O layer attempted to
check some previous operation in the data set. The
check failed. h_digits1
The address of the file usage block (FUB).
h_digits2
h_digits1
The address of the file usage block which
The sense bytes 0 and 1 from the device.
currently has the file allocated.
h_digits2
System Action: The system ends the request. A not
The first 3 bytes of the channel status word
owner error is returned to the user. The system
(CSW) from the device.
continues processing for Network File System Server.
h_digits3
Application Programmer Response: None.
The last 4 bytes of the CSW from the device.
h_digits4
The access method return code.
GFSA886I UNABLE TO WRITE RECNO d_digits TO
h_digits5
string1(string2) DUE TO PREVIOUS
The access method reason code.
ERROR.
Explanation: An error was previously detected which
prevents writing to a data set.
Server.
appropriate device documentation for more information d_digits
on the sense bytes and CSW. The record number.
Source: DFSMSdfp and Network File System Server string1 The data set name.
GFSA877I R0=h_digits1 R1=h_digits2: text ACCESS
METHOD RC = h_digits3 ACCESS
METHOD RSN = h_digits4
Server.
Explanation: A SYNAD error was detected during
Application Programmer Response: If the previous
physical I/O operation. h_digits1 is the contents of
error cannot be determined, contact the IBM Support
register 0; h_digits2 is the contents of register 1. The
Center.
text is the message returned from the SYNAD analysis
function macro. h_digits3 is the access method return Source: DFSMSdfp and Network File System Server
code. h_digits4 is the access method reason code.
System Action: The request is stopped. If the error GFSA895I REQUEST h_digits - FILE string NOT
detected is a B37, D37 or E37 abend, the Network File ALLOCATED.
System restores the file size to the last known file size
before the SYNAD error. Network File System Explanation: The network file system server did not
processing continues. have the data set string open on a request to close the
file. The file name may have been specified incorrectly

or the time out may have already occurred for this data string4 The member name, if any.
set, causing Network File System Server to close the
data set.
In the message text: Server.
h_digits Application Programmer Response: None
string The data set name.
System Action: The system ends the request. Return GFSA898I EOL SEQUENCE MISMATCH FOR
code X'131' is passed back to the user. The system DATA SET. string1(string2)
continues processing for Network File System Server.
Explanation: The end-of-line terminator was not found
Application Programmer Response: None in the same place as the previous end-of-line terminator
for an offset that is being re-written by the user.
GFSA896I REQUEST h_digits1 - FILE BLOCK string1 The data set name.
h_digits2 ASSOCIATED WITH FILE string
NOT IN USE BY CREDENTIALS
h_digits3. System Action: The system ends the request. The
Explanation: The request to close file string was
Server.
received, but the file was not opened by the user. A file
can only be closed by the same user that opened the Application Programmer Response: None
file.
h_digits1 GFSA899I BLANKSTRIP MODE: TRAILING
The request block address. BLANK(S) IN RECORD d_digits IS NOT
ALLOWED. DSN = string1(string2).
h_digits2
The file block address. Explanation: The user attempted to write data in text
mode with blank stripping enabled and blanks at the
string The specified file name.
end of the line to a data set with fixed-length records.
h_digits3
The credentials block address.
d_digits
System Action: The system ends the request. Return
The record.
code X'132' is passed back to the user. The system
continues processing for Network File System Server. string1 The data set name.
Application Programmer Response: None string2 The member name, if any.
Source: DFSMSdfp and Network File System Server System Action: The system ends the request. The
Server.
GFSA897I RECORD d_digits1 SIZE d_digits2 IS
{TOO LONG | TOO SHORT}: Application Programmer Response: None
{MAXIMUM | MINIMUM} = d_digits3 DSN
= string3(string4). Source: DFSMSdfp and Network File System Server
Explanation: The record received from the user is

either too long or too short. GFSA900I MOUNT PROCESSING ACTIVE.
In the message text: Explanation: Mounts can be issued from the network.
This message is displayed in response to the STATUS
d_digits1 operand of the MODIFY command.
The record number.
d_digits2 Network File System Server.
The record size.
d_digits3
The maximum or minimum length allowed. Source: DFSMSdfp and Network File System Server

GFSA901I MOUNT PROCESSING SUSPENDED. GFSA905I HFS MOUNT PROCESSING
SUSPENDED
Explanation: Mount processing has been suspended
by the FREEZE=ON operand of the MODIFY command. Explanation: HFS mount processing has been
This message is displayed in response to either the suspended by the freeze=onhfs operand of the MODIFY
FREEZE=ON or STATUS operands of the MODIFY command. This message is displayed in response to
command. either the freeze=onhfs or status operands of the
MODIFY command. Further HFS mount requests from
the network are ignored. Existing mounts are
Network File System Server. Further mount requests
unaffected.
from the network are ignored. Existing mounts are
unaffected. System Action: The Network File System processing
continues.
Detecting Module: GFSACOPR
GFSA902I MOUNT PROCESSING RESUMED.
GFSA908I HFS PROCESSING DISABLED
Explanation: Mount processing has been resumed by
the FREEZE=OFF operand of the MODIFY command. Explanation: HFS processing is suspended. This
message is displayed in response to the status operand
of the MODIFY command.
Network File System Server. Further mount requests
from the network will be honored. Existing mounts are System Action: The Network File System processing
unaffected. continues.
Operator Response: None Source: DFSMS/MVS NFS Server
Source: DFSMSdfp and Network File System Server Detecting Module: GFSACOPR
GFSA903I TASK h_digits1 TCB h_digits2 GFSA909E UNMOUNT COMMAND FAILED: MOUNT
PROGRAM = string1 = string2. POINT STILL IN USE
Explanation: This message is issued in response to Explanation: This message is in response to the
the STATUS operand of the MODIFY command. UNMOUNT operand of the MODIFY command. The
unmount processing fails because the file system is still
in use. The user can retry the UNMOUNT command
h_digits1 later after there is no reference to file system.
The task queue address.
h_digits2 system continues processing for the Network File
The task control block (TCB) address. System.
string1 The program name. Source: OS/390 NFS server
string2 The specific task name.

GFSA910I string ACTIVE = d_digits.
Network File System Server. Explanation: This message is in response to the
LIST=MOUNTS operand of the MODIFY command and
Operator Response: None shows the mounted file space (MVS path) and the
Source: DFSMSdfp and Network File System Server number of active users mounting those files by that
path. The number may not be accurate if a user has
crashed without unmounting the files.
GFSA904I HFS MOUNT PROCESSING ACTIVE.
Explanation: Mounts can be issued from the network.
This message is displayed in response to the status string The mounted file space.
operand of the MODIFY command. d_digits
System Action: Network File System processing The number of active users mounting the files
continues. by the specified path.
Source: DFSMS/MVS NFS Server System Action: The system continues processing for

GFSA914I string DEALLOCATED.
Explanation: The data set name appears in response
GFSA911I string1(string2) ACTIVE = d_digits.
to a RELEASE=dsname(member) operand of the
Explanation: This status message is in response to MODIFY command after successful deallocation.
the LIST=MOUNTS operand of the MODIFY command
and shows the mounted file space (MVS path) and the
number of active users mounting those files by that string The data set name.
path. The number may not be accurate if a user has
crashed without unmounting the files.
d_digits GFSA915I string NOT ALLOCATED.
The number of active users mounting the files
by the specified path.
to the RELEASE=dsname(member) operand of the
System Action: The system continues processing for MODIFY command if the data set or member specified
Network File System Server. to be released was not found.
Operator Response: None In the message text:
Source: DFSMSdfp and Network File System Server string The data set name.
GFSA912I string. Network File System Server.
Explanation: The data set name appears in response Operator Response: None
to a LIST=DSNAMES operand of the MODIFY
command and shows a currently active data set.
GFSA916I string UNMOUNTED.
System Action: The system continues processing for to an UNMOUNT (data set or member) operand of the
Network File System Server. MODIFY command after a successful unmount.
Operator Response: None. In the message text:
Source: DFSMSdfp and Network File System Server string The data set name.
GFSA913I string1(string2). Network File System Server.
Explanation: The partitioned data set (PDS) member Operator Response: None
appears in response to the LIST=DSNAMES operand of
the MODIFY command and shows a currently active
data set.
GFSA917I string NOT MOUNTED.
to the UNMOUNT (data set or member) operand of the
string2 The member name, if any. MODIFY command if the data set or member specified
to be unmounted was not found in the current mount
list.

GFSA918I string IS NOT A VALID DATA SET GFSA922I VERIFY: (string) IS NOT A VSAM DATA
NAME. SET.
Explanation: The data set name specified on either Explanation: This message is in response to the
the RELEASE or UNMOUNT operand of the MODIFY VERIFY operand of the MODIFY command and shows
command is not a valid data set name. that the data set name specified is not a virtual storage
access method (VSAM) data set.
Network File System Server. System Action: The system ends the request. The
Operator Response: Respecify the command with a
Server.
valid data set name.
GFSA919I string IS NOT A VALID MEMBER NAME.
GFSA923I VERIFY SUCCESSFUL FOR (string).
Explanation: The member name specified on either
the RELEASE or UNMOUNT operand of the MODIFY Explanation: This message is in response to the
command is not a valid MVS member name. VERIFY operand of the MODIFY command and shows
that the verify was successful for the virtual storage
access method (VSAM) data set.
string The incorrect member name.
Operator Response: Respecify the command with a
valid member name.
GFSA920I NO ACTIVE MOUNT POINTS.
GFSA924I VERIFY FAILED WITH RC = d_digits
Explanation: This message is in response to the
FOR (string).
LIST=MOUNTS operand of the MODIFY command and
shows that there are no clients connected to the Explanation: This message is in response to the
network file system server . VERIFY operand of the MODIFY command and shows
that the verify failed with a return code for the data set.
Message GFSA847I follows this message in the error
log.
d_digits
The return code.
GFSA921I NO ACTIVE DATA SETS.
Explanation: This message is in response to the
LIST=DSNAMES operand of the MODIFY command
and shows that there are no users actively accessing
data sets. Application Programmer Response: See message
GFSA847I to determine the correct action.
Network File System Server. Source: DFSMSdfp and Network File System Server
GFSA925I ERROR WAS DETECTED IN THE
EXPORTS FILE - EXPORT LIST NOT
REBUILT.
Explanation: This is the reply from the EXPORTFS
operand of the MODIFY command, indicating that one

or more errors were detected in the EXPORTS file; for switched-to log data set is filled.
example, the EXPORTS file cannot be opened.
System Programmer Response: Consider allocating
System Action: Network File System Server larger error log data sets for future Network File System
processing continues. The existing EXPORTS file will Server usage. Note that the last data buffer will be lost
not be changed. when the log is switched.
Operator Response: Notify the system programmer. Source: DFSMSdfp and Network File System Server
System Programmer Response: Review previous
console error messages for detailed information as to GFSA931I NETWORK FILE SYSTEM SERVER
the specific error in the EXPORTS file. LOGGING IS TERMINATED.
Source: DFSMSdfp and Network File System Server Explanation: The Network File System Server logging
ends. This can be caused by a “no space” condition of
the log data set.
GFSA926I EXPORT LIST HAS BEEN REBUILT
SUCCESSFULLY System Action: Network File System Server
operand of the MODIFY command, indicating that the System Programmer Response: Allocate a larger log
command has completed normally. data set for future Network File System Server usage.
System Action: Network File System Server Source: DFSMSdfp and Network File System Server
processing continues with the new EXPORTS file in
effect.
GFSA932I LOG DATA SET string IS FLUSHED.
Explanation: The data buffer of the active log data set
is flushed to disk. If the log is written to standard error,
GFSA927I MODIFY EXPORTS COMMAND string is STDERR. Otherwise, string is the associated
IGNORED - THE EXPORTS FILE IS NOT DD of the active log data set.
BEING USED FOR SECURITY
CHECKING.
operand of the MODIFY command, indicating that the
command was ignored because the site attribute for
security requested that no EXPORTS file checking be GFSA933I LOG DATA SET IS RE-INITIALIZED.
done.
Explanation: The error log is re-initialized.
processing continues with the security options System Action: Network File System Server
unchanged. processing continues.
Source: DFSMSdfp and Network File System Server Source: DFSMSdfp and Network File System Server
GFSA930I LOG DATA SET IS SWITCHED FROM GFSA934I NFSLOG1 OR NFSLOG2 DD

string1 TO string2. STATEMENTS NOT DEFINED.
Explanation: A “no space” or an I/O error condition is Explanation: The NFSLOG1 or the NFSLOG2 DD
detected when writing to the log data set. Network File statements are not coded in the Network File System
System Server logging is now switched to the other log Server start-up cataloged procedure.
data set. System Action: Network File System Server ends.
In the message text: System Programmer Response: Code the NFSLOG1
string1 The DD associated with the switched-from log and NFSLOG2 DD statements and allocate the
data set. associated log data sets.
string2 The DD associated with the switched-to log Source: DFSMSdfp and Network File System Server
data set.
Operator Response: If requested by the installation,
back up the switched-from log data set. The
switched-from log data set will be reused when the

GFSA935I SWITCHED-TO LOG IN ERROR. GFSA953I PASSWORD CHANGE REQUIRED BY
NETWORK FILE SYSTEM SERVER HOST.
LOGGING CONTINUED ON DD:string.
Explanation: The MVS password for the user ID
Explanation: An operator entered a SWITCHLOG passed to the host has expired. A new password is
command but an open error is detected in the new log required. Message GFSA974I follows this message.
data set.
string The DD associated with the original log data GFSA954I HOST text1 RETURNED ERROR
set. d_digits:text2
System Action: Network File System Server logging Explanation: An error was detected during mvslogin
continues in the original log data set. processing. Host text1 returned error code d_digits and
message text2 to the client.
Operator Response: Correct the non-active log data
set. User Response: The password or user ID might be
incorrect. Start the mvslogin command sequence again
and use the correct password or user ID.
GFSA949I COMMAND string NOT VALID.

GFSA955I text LOGGED IN OK.
Explanation: The operator has entered the operator
Explanation: The MVS user ID text was logged in
command or operand string which is not valid.
without any errors.
string The incorrect operator command or operand.
System Action: The system continues processing for GFSA956I usage: text [-pn][-g group][-a account]
Network File System Server. hostname [mvs_username]
Operator Response: Enter the operand of the Explanation: Usage information for the text command.
MODIFY command again with the correct syntax.
User Response: Enter the command using the correct
Source: DFSMSdfp and Network File System Server syntax.
GFSA950I UNKNOWN FLAG ’-character’ GFSA957I HOST text1 RETURNED ERROR

d_digits:text2
Explanation: The character character specified on the
mvslogin, mvslogout, or showattr command is not a Explanation: An error was detected during mvslogout
valid option. A usage message might follow this processing. Host text1 returned error code d_digits and
message. message text2 to the client.
User Response: See OS/390 Network File System User Response: Notify your MVS system
User’s Guide for a description of the valid options used programmer.
with the command.
GFSA958I UID text LOGGED OUT OK.
GFSA951I text: CAN’T FIND NAME FOR UID
Explanation: The MVS user ID text was logged out
d_digits.
successfully.
Explanation: There was an error reading information
for UID d-digits from the etc/passwd file.
User Response: Correct the etc/passwd file and try
GFSA959I USAGE: text HOSTNAME
the command again.
Explanation: Usage information for the text command.
GFSA952I RETYPED PASSWORD DOES NOT User Response: Enter the command using the correct
MATCH syntax.
Explanation: The password entered when message
GFSA975I was displayed does not match the password
entered when message GFSA974A was displayed.
User Response: Start the mvslogin command
sequence again.

GFSA960I text1: HOST ″text2″ UNKNOWN. GFSA970I REGISTERED WITH UNIX System
Services MVS.
Explanation: The host text2, specified on command
text1, is not known to the network. Explanation: Connection with OS/390 UNIX System
Services established.
User Response: Correct the host name specified and
try the command again. System Action: Network File System Server
GFSA961I text1: text2 Source: DFSMSdfp and Network File System Server
Explanation: Command text1 received an error when
trying to create a client transport handle using the GFSA971I HFS MOUNTS DISABLED.
clntudp_create TCP/IP remote procedure call. text2 is
the message produced by the clnt_pcreateerror
have been disabled. Given in response to a console
TCP/IP procedure. This message is issued if:
MODIFY command.
v The host name is unknown
v The host is not operational
v The Network File System on the named host is not
operational Source: DFSMSdfp and Network File System Server
User Response:
GFSA972I HFS MOUNTS ENABLED.
v Correct the host name specified and try the
command again, Explanation: Mount requests to HFS file systems
v Make sure the specified host is operational and try have been enabled. Given in response to a console
the command again, or MODIFY command.
v Make sure the OS/390 NFS server on the named System Action: Network File System Server
host is operational and try the command again. processing continues.
GFSA964I text: ERROR: CANNOT DETERMINE
SERVER.
GFSA973I UNIX System Services MVS IS NOT
Explanation: The text command found the mount RESPONDING.
path, but the server name was not returned by the local
operating system service that keeps mount point Explanation: Registration with OS/390 UNIX System
information. Services has been successful but a request for an HFS
file object has failed.
User Response: Correct the mount point table and try
the command again. System Action: The request is stopped. Network File
System Server processing continues.
GFSA965I text1: ERROR: text2 MOUNTED FROM System Programmer Response: If the log is being
SERVER text3, NO text4. flooded with these messages, restart the Network File
System Server and set site attribute nohfs.
Explanation: The wrong host name was specified for
the text1 command. text2 is mounted from server text3 Source: DFSMSdfp and Network File System Server
instead of server text4.
User Response: Specify the command again with the GFSA974I INVALID UNIX System Services MVS
correct host name. RELEASE LEVEL.
Explanation: The Network File System Server only
GFSA966I text: ERROR: UNKNOWN RETURN works with MVS/SP 5.1 or later.
FROM USAGE ROUTINE. System Action: Network File System Server
Explanation: The usage routine used for the text processing continues. Access to conventional MVS data
command returned an unknown error code. sets is not impacted.
User Response: Contact your programming support System Programmer Response: Install MVS/SP 5.1
personnel. or later.

GFSA975A RETYPE NEW MVS PASSWORD: GFSA991E MESSAGE FORMAT FROM USER EXIT
ROUTINE(S) IS INCORRECT. USER text
Explanation: MVS requires the new password to be
EXIT ROUTINE(S) HAS(HAVE) ENDED.
entered twice for verification.
Explanation: The text exit routine returned an
User Response: Enter the new MVS password again.
incorrect length message.
In the message text, text is one of the following:
GFSA976I CANNOT RESOLVE PATHNAME WITH
UNIX SYSTEM SERVICES MVS. LOGON AND FILE SECURITY
User logon and file security exit routines.
Explanation: A failure occurred when attempting to
resolve a pathname with UNIX System Services MVS, FILE SECURITY
when initializing from the mount handle data sets. The User file security exit routine.
HFS file system has been removed or renamed. If the
System Action: The Network File System Server
user attempts to access a file object under this mount
processing continues without the user exit routine(s).
point, the Network File System Server error response
NFSERR_STALE is returned. Operator Response: Record the MVS operator
console message and notify the DFSMS/MVS NFS
system programmer.
System Programmer Response: Correct user exit
routine(s), relink the user exit routine(s), and restart the
DFSMS/MVS NFS server.
GFSA977I SERVICE REQUESTER DOES NOT
HAVE SECURITY PRIVILEGE.
Detecting Module: GFSASCLO
Explanation: The client user must be defined to RACF
as a user of OS/390 UNIX System Services MVS to GFSASCSE
access HFS file objects.
System Action: The request is stopped. Network File GFSA996E INSTALLATION DEFAULT
System Server processing continues. TRANSLATION TABLE CANNOT BE
INITIALIZED.
System Programmer Response: Check the SAF
security product user profiles. Explanation: The Network File System Server ends
because one of these conditions happens during
Network File System Server startup:
v The NFSXLAT DD statement is not coded in the
GFSA978I text logged in ok. Mismatch in uid/gid: Network File System Server start-up catalog
UNIX System Services uid is digit_1, procedure, and the xlat processing attribute is
gid is digit_2, client uid is digit_3, gid is specified.
digit_4 v Translation table data set defined in the NFSXLAT
DD statement is not a PDS or PDSE.
Explanation: The OS/390 UNIX System Services
v Translation table specified in the translation table
UID/GID does not match the client machine UID/GID.
data set cannot be found.
The authentication is successful and the message is for
v Translation table contained in the translation table
informational use only.
data set is in an incorrect format.
User Response: None
processing stops.
GFSA979I SECURITY PRODUCT IS NOT
System Programmer Response: Do the following
INSTALLED.
before restarting the Network File System Server:
Explanation: OS/390 UNIX System Services has v Code the NFSXLAT DD statement in the Network File
detected that the security product is not installed. The System Server start-up catalog procedure correctly.
user receives an NFS error response NFSERR_ACCES v Allocate the translation table data set defined in the
to the request. NFSXLAT DD statement.
v Make sure the translation table in the translation table
System Action: The request is stopped. Network File data set exists.
System Server processing continues. v Make sure the translation table specified in the
System Programmer Response: Ensure the correct translation table data set is in the correct format.
release of the security product is installed. Source: DFSMSdfp and Network File System Server

GFSA997I ERROR IN READING THE
TRANSLATION TABLE, string
Explanation: The Network File System Server tried to
read the translation table, string, during the mount but
was unsuccessful. string is the member name that
contains the translation table. The cause might be:
v The NFSXLAT DD statement is not coded in the NFS
start-up catalog procedure.
v The NFSXLAT DD statement is not coded correctly in
the NFS start-up catalog procedure.
v Translation table data set defined in the NFSXLAT
DD statement is not a PDS or PDSE.
v Translation table specified in the translation table
data set cannot be found.
v The format of the translation table contained in the
translation table data set is not valid.
processing stops.
User Response: This error occurs on mount
operation. Contact your system programmer for the
correct member name for the translation table.
GFSA998I TRANSLATION TABLE string IS

LOADED.
Explanation: NFS loaded the translation table, string,
successfully.

Chapter 6. GFSC Messages
Detecting Module: OS/390 NFS client, module
GFSC100E RPC REQUEST (h_digit) FAILED,
GFSCCXDR
RETURN VALUE -1 RETURN CODE
returncd REASON CODE rsnc (text)
GFSC103E NETWORK FILE SYSTEM SERVER
Explanation: RPC request failed. (h_digit) is the
REQUEST FAILED (h_digit),
request block address. Reason code, rsnc, is the return
OPENEDITION RETURN CODE returncd
code returned from TCP/IP. text is the failure reason.
NETWORK FILE SYSTEM SERVER
For the explanation of return code, returncd, refer to
RETURN CODE retc
OS/390 UNIX System Services Messages and Codes.
Explanation: Network File System server failed the
System Action: Client continues processing.
request from the client. (h_digit) is the request block
User Response: See the return code, returncd, in address. Return code, retc, is returned from Network
OS/390 UNIX System Services Messages and Codes, File System server. For the explanation of return code,
and the reason code, rsnc, in OS/390 eNetwork returncd, is referred to in OS/390 UNIX System
Communications Server: IP Messages. Services Messages and Codes.
Detecting Module: OS/390 NFS client, module System Action: Client continues processing.
GFSCCXDR
User Response: See the return code, returncd, in
OS/390 UNIX System Services Messages and Codes,
GFSC101E NETWORK FILE SYSTEM SERVER and the return code, retc, in the Network File System
REQUEST FAILED (h_digit), Protocol Specification, RFC 1094.
OPENEDITION RETURN CODE returncd
NETWORK FILE SYSTEM SERVER
GFSCCXDR
RETURN CODE retc (text)
Explanation: Network File System server failed the
GFSC105E READ FAILED, RETURN VALUE -1
request from the client. (h_digit) is the request block
RETURN CODE returncd REASON
address. Return code, retc, is returned from Network
CODE reasoncd.
File System server. text is the failure reason for the
request. For the explanation of return code, returncd, Explanation: While reading a block of data from a
refer to OS/390 UNIX System Services Messages and remote file, an error returncd was detected.
Codes.
System Action: The read operation ends. OS/390
System Action: Client continues processing. NFS client processing continues.
User Response: See the return code, returncd, in User Response: Refer to OS/390 UNIX System
OS/390 UNIX System Services Messages and Codes, Services Messages and Codes for a description of the
and the return code, retc, in the Network File System return code returncd and the reason code reasoncd to
Protocol Specification, RFC 1094. determine corrective action.
Detecting Module: OS/390 NFS client, module Detecting Module: OS/390 NFS client, module
GFSCCXDR GFSC2BIO
GFSC102E RPC REQUEST (h_digit) FAILED, GFSC106E WRITE FAILED, RETURN VALUE -1
RETURN VALUE -1 RETURN CODE RETURN CODE returncd REASON
returncd REASON CODE rsnc CODE reasoncd.
Explanation: RPC request failed. (h_digit) is the Explanation: While writing a block of data to a remote
request block address. Reason code, rsnc, is the return file, an error returncd was detected.
code returned from TCP/IP. For the explanation of
return code, returncd, is referred to in OS/390 UNIX System Action: The write operation ends. OS/390
System Services Messages and Codes. NFS client processing continues. The remote file may
not be complete.
System Action: Client continues processing.
User Response: Refer to OS/390 UNIX System
User Response: See the return code, returncd, in Services Messages and Codes for a description of the
OS/390 UNIX System Services Messages and Codes, return code returncd and the reason code reasoncd to
and the reason code, rsnc, in OS/390 eNetwork determine corrective action.
Communications Server: IP Messages.
GFSC2BIO

GFSC107E FLUSH FAILED, RETURN VALUE -1 GFSC201E NETWORK FILE SYSTEM CLIENT
RETURN CODE returncd REASON DOES NOT SUPPORT SYNCHRONOUS
CODE reasoncd. MOUNT REQUEST.
Explanation: While flushing cached data to a remote Explanation: OS/390 NFS client only supports
file during close processing, an error returncd was asynchronous mount.
detected.
System Action: The MOUNT command ended with an
System Action: The write operation ends. OS/390 error. OS/390 NFS client processing continues.
NFS client processing continues. The remote file may
User Response: Reissue MOUNT command with the
not be complete.
asynchronous option.
Services Messages and Codes for a description of the
GFSCVMNT
return code returncd and the reason code reasoncd to
determine corrective action.
GFSC202E A FILE SYSTEM WITH THE SAME
NAME IS ALREADY MOUNTED.
GFSC2BIO
Explanation: Cannot mount on an existing mount
point.
GFSC110E text FAILED, RETURN VALUE -1
RETURN CODE returncd REASON System Action: The MOUNT command ended with an
CODE reasoncd error. No mount point was established. OS/390 NFS
client processing continues.
Explanation: The OS/390 NFS client has detected an
error in the function, text. User Response: Reissue MOUNT command with a
different mount point.
System Action: The request has ended. OS/390 NFS
client processing continues. Detecting Module: OS/390 NFS client, module
GFSCVMNT
return code returncd and the reason code reasoncd to GFSC203E PARSING MOUNT OPTION FAILED,
determine corrective action. RETURN VALUE -1 RETURN CODE
returncd REASON CODE reasoncd
System Programmer Response: Collect the detail
OPTION=’text’.
trace log from client and from server if any.
Explanation: The mount option text was incorrectly
Detecting Module: OS/390 NFS client, modules
specified.
GFSCVNAC, GFSCVNAT, GFSCVNDR, GFSCVNLK,
GFSCVNRM, and GFSCVNRW System Action: The MOUNT command ended with an
error. No mount point is established. OS/390 NFS client
GFSC200E VFS_MOUNT FAILED, RETURN VALUE
-1 RETURN CODE returncd REASON User Response: Refer to OS/390 UNIX System
CODE reasoncd. Services Messages and Codes for a description of the
return code returncd, and refer to OS/390 Network File
Explanation: The MOUNT command failed because of
System Customization and Operation for further details
error returncd.
of the reason code reasoncd. Correct the mount option,
System Action: The MOUNT command ended and reissue MOUNT command.
abnormally. OS/390 NFS client processing continues.
User Response: Refer to OS/390 UNIX System GFSCVMNT
GFSC204E VFS_UMOUNT FAILED, RETURN
determine the corrective action, and reissue MOUNT
VALUE -1 RETURN CODE returncd
command.
REASON CODE reasoncd.
Explanation: The UMOUNT or UNMOUNT command
GFSCVMNT
failed.
System Action: The UMOUNT or UNMOUNT
command ended with an error. The mount point may
still exist. OS/390 NFS client processing continues.

Services Messages and Codes for a description of the no fix exists, contact the IBM Support Center. Provide
return code returncd and the reason code reasoncd to all the printed output and copies of output data sets
determine the corrective action. Correct it and reissue related to the problem.
UNMOUNT again.
Detecting Module: OS/390 NFS client, module GFSCVMNT
GFSCVMNT
GFSC208E VFS_PFSCTL FAILED, RETURN VALUE
GFSC205E VFS_STATFS FAILED, RETURN VALUE -1 RETURN CODE returncd REASON
-1 RETURN CODE returncd REASON CODE reasoncd.
CODE reasoncd.
Explanation: The VFS_PFSCTL operation failed.
Explanation: The VFS_STATFS operation failed.
System Action: The VFS_PFSCTL ended with an
While trying to get the status of a remote file system, an
error. OS/390 NFS client processing continues.
error returncd was detected.
System Action: The VFS_STATFS ended with an
User Response: Refer to OS/390 UNIX System determine the corrective action. If the error occurs and
Services Messages and Codes for a description of the the program is not in error, look at the messages in the
return code returncd and the reason code reasoncd to client log data sets for more information. Search
determine the corrective action. problem reporting data bases for a fix for the problem. If
no fix exists, contact the IBM Support Center. Provide
all the printed output and copies of output data sets
GFSCVMNT
related to the problem.
GFSC206E VFS_SYNC FAILED, RETURN VALUE -1
GFSCVMNT
RETURN CODE returncd REASON
CODE reasoncd.
GFSC209E THE IP ADDRESS OF REMOTE HOST
Explanation: The VFS_SYNC operation failed. While
NAME, hostname, COULD NOT BE
flushing cached data of remote files, an error returncd
RESOLVED.
was detected.
Explanation: The VFS_MOUNT operation failed. The
System Action: The VFS_SYNC ended with an error.
mount processing failed when it tried to resolve the
The remote files may not be complete. OS/390 NFS
remote host name hostname to a dotted IP address.
client processing continues.
System Action: The MOUNT command ended with an
return code returncd and the reason code reasoncd to User Response: Correct the remote host name or use
determine the corrective action. the dotted IP address of the remote host, and reissue
the MOUNT command.
GFSCVMNT Detecting Module: OS/390 NFS client, module
GFSCMNTD
GFSC207E VFS_RECOVER FAILED, RETURN
VALUE -1 RETURN CODE returncd GFSC210E NFS SERVER <hostname> DOES NOT
REASON CODE reasoncd. SUPPORT NFS VERSION 3 PROTOCOL
WHILE ’VERS(3) WAS SPECIFIED
Explanation: The VFS_RECOVER operation failed.
While trying to recover from a previous abend, an error Explanation: The VFS_MOUNT operation failed. The
returncd was detected. mount processing failed because the server does not
support NFS version 3 protocol, which the user
System Action: The VFS_RECOVER ended with an
requested with the mount parameter vers(3).
System Action: The mount command ended with an
error. OS/390 NFS client processing continue.
return code returncd and the reason code reasoncd to User Response: Verify that the server actually does
determine the corrective action. If the error occurs and not support NFS version 3 protocol. Remove vers(3)
the program is not in error, look at the messages in the from the mount parameter, and reissue the mount
client log data sets for more information. Search command.
problem reporting data bases for a fix for the problem. If
Chapter 6. GFSC Messages 207

Source: OS/390 NFS client, module GFSCMNTD Operator Response: Record the MVS operator
console message and notify the MVS system
programmer.
GFSC211E NFS SERVER <hostname> DOES NOT
SUPPORT ’AUTH_UNIX’ System Programmer Response: If the error is in the
AUTHENTICATION. mount parameter, correct the parameter, and reissue
the mount command. If the error occurs in the
Explanation: The VFS_MOUNT operation failed. The
DFSMS/MVS NFS client installation parameter, correct
mount processing failed because the server does not
the parameter, stop OS/390 UNIX System Services, and
do UNIX authentication. (AUTH_UNIX). OS/390 does
restart OS/390 UNIX System Services.
not support other authentication such as Kerboros.
Source: DFSMS/MVS NFS Client
System Action: The mount command ended with an
error. Detecting Module: GFSCPARS
User Response: Verify that the server actually does
not support AUTH_UNIX authentication. Notify the GFSC302E MISSING RIGHT PARENTHESIS IN text
server system administrator. KEYWORD.
Source: OS/390 NFS client, module GFSCMNTD Explanation: Specified keyword, text, is missing a
right parenthesis.
GFSC300E MISSING LEFT PARENTHESIS IN text In the message text:
KEYWORD.
text
Explanation: Specified keyword, text, is missing a left The installation or mount parameter keyword.
parenthesis.
System Action: Network File System Client
In the message text: processing stops if the error is in the Network File
System Client installation parameter. The mount
text
command failed if the error is in the mount parameter.
The installation or mount parameter keyword.
Operator Response: Record the MVS operator
processing stops if the error occurs in the DFSMS/MVS
programmer.
NFS client installation parameter. The mount command
failed if the error is in the mount parameter. System Programmer Response: If the error is in the
mount parameter, correct the parameter, and reissue
programmer.
System Programmer Response: If the error is in the restart OS/390 UNIX System Services.
DFSMS/MVS NFS client installation parameter, correct Detecting Module: GFSCPARS
GFSC303E THE SPECIFIED VALUE d_digit1 IS NOT
Source: DFSMS/MVS NFS Client IN THE RANGE OF d_digit2 TO d_digit3
FOR text KEYWORD.
Detecting Module: GFSCPARS
Explanation: The value, d_digit1, specified in the
keyword, text, must be between the minimum value,
GFSC301E PARSE FAILED ON NUMERIC FIELD
d_digit2, and the maximum value, d_digit3.
FOR text KEYWORD.
Explanation: Specified keyword, text, contains
alphabetic data in numeric field. d_digit1
The value specified in the installation or mount
parameter.
text
d_digit2
The minimum allowed value.
d_digit3
processing stops if the error is in the Network File
The maximum allowed value.
command failed if the error is in the mount parameter. text

System Action: Network File System Client In the message text, text2 is the installation or mount
processing stops if the error is in the Network File parameter keyword.
Operator Response: Record the MVS operator System Client installation parameter. The mount
console message and notify the MVS system command failed if the error is in the mount parameter.
programmer.
System Programmer Response: If the error is in the console message and notify the MVS system
mount parameter, correct the parameter, and reissue programmer.
System Programmer Response: If the error is in the
mount parameter, correct the option for the keyword,
text2, and reissue the mount command. If the error
occurs in the DFSMS/MVS NFS client installation
Source: DFSMS/MVS NFS Client parameter, correct the option for the keyword, text2,
stop OS/390 UNIX System Services, and restart OS/390
UNIX System Services.
GFSC304E PARSE FAILED ON ALPHABETIC
FIELD FOR text KEYWORD. Detecting Module: GFSCPARS
Explanation: Specified keyword, text, contains
numeric data for alphabetic field. GFSC306E INCORRECT OPTION text SPECIFIED
FOR DELIM KEYWORD, VALID OPTION
IS BINARY, NL, CR, LF, CRLF, OR
text LFCR.
Explanation: An incorrect option, text, has been
System Action: Network File System Client specified for the keyword, delim.
In the message text, text is one of the following:
command failed if the error is in the mount parameter. binary
The binary option for the installation or mount
delim parameter. Specifies that the access method
does not add a delimiter for each record on output
programmer.
and treats any delimiters on input as data.
nl The nl option for the installation or mount delim
parameter. Specifies the EBCDIC new line delimiter
(X'15').
the parameter, stop OS/390 UNIX System Services, and cr The cr option for the installation or mount delim
restart OS/390 UNIX System Services. parameter. Specifies the EBCDIC carriage return
delimiter (X'0D').
lf The lf option for the installation or mount delim
parameter. Specifies the EBCDIC line feed delimiter
(X'25').
GFSC305E INCORRECT OPTION text1 SPECIFIED
crlf
FOR text2 KEYWORD, VALID OPTION
The crlf option for the installation or mount delim
IS Y OR N.
parameter. Specifies the EBCDIC carriage return
Explanation: An incorrect option, text1 , was specified delimiter followed by the EBCDIC line feed delimiter
for the keyword, text2. (X'0D25').
In the message text, text1 is one of the following: lfcr

The lfcr option for the installation or mount delim
Y Yes option for the installation or mount parameter parameter. Specifies the EBCDIC line feed delimiter
keyword. followed by the EBCDIC carriage return delimiter
N No option for the installation or mount parameter (X'250D').
keyword. System Action: Network File System Client

GFSC310I READAHEAD AND DELAYWRITE
Operator Response: Record the MVS operator OPTIONS WILL BE IGNORED AS
console message and notify the MVS system DATACACHING IS OFF.
programmer.
Explanation: The keywords, readahead and
System Programmer Response: If the error is in the delaywrite, will be ignored because datacaching has
mount parameter, correct the option for the keyword, been set off.
delim, and reissue the mount command. If the error
System Action: DFSMS/MVS NFS client continues
occurs in the DFSMS/MVS NFS client installation
processing.
parameter, correct the option for the keyword, delim,
stop OS/390 UNIX System Services, and restart OS/390 Operator Response: Record the MVS operator
UNIX System Services. console message and notify the MVS system
programmer.
System Programmer Response: Check parameters
to make sure that datacaching is supposed to be off.
GFSC307E text IS AN INCORRECT KEYWORD FOR
MOUNT PARAMETER. Detecting Module: GFSCPARS
Explanation: text can only be specified as an
installation parameter. GFSC311I CLN_CCSID AND SRV_CCSID WILL BE
IGNORED AS XLAT OPTION IS OFF.
System Action: The mount command failed.
Explanation: The keywords, cln_ccsid and
System Programmer Response: Correct the mount
srv_ccsid, will be ignored because xlat has been set
parameter keyword, text.
off.
GFSCPARS
processing.
GFSC309E UNKNOWN KEYWORD ENCOUNTERED
AROUND POSITION d_digit.
programmer.
Explanation: The keyword specified in position,
d_digit, is not a valid keyword.
to make sure that xlat is supposed to be off.
d_digit
The installation or mount parameter keyword
position.
GFSC312I ACREGMIN, ACREGMAX, ACDIRMIN,
AND ACDIRMAX OPTIONS WILL BE
IGNORED AS ATTRCACHING IS OFF.
command failed if the error is in the mount parameter. Explanation: The keywords, acregmin, acregmax,
acdirmin and acdirmax, will be ignored because
attrcaching has been set off.
programmer. System Action: DFSMS/MVS NFS client continues
processing.
mount parameter, correct the keyword, and reissue the Operator Response: Record the MVS operator
mount command. If the error occurs in the DFSMS/MVS console message and notify the MVS system
NFS client installation parameter, correct the keyword, programmer.
stop OS/390 UNIX System Services, and restart OS/390
to make sure that attrcaching is supposed to be off.

GFSC313I RETRANS OPTION WILL BE IGNORED
AS HARD OPTION IS ON.
GFSC318E READ FAILED FOR NETWORK FILE
Explanation: The keyword, retrans, will be ignored
SYSTEM CLIENT MOUNT
because hard has been set on.
PARAMETERS.
Explanation: An error occurred while the Network File
processing.
System Client was processing the mount parameters.
Operator Response: Record the MVS operator This message follows other messages, GFSC3xxE, that
console message and notify the MVS system describe the error in greater detail.
programmer.
System Programmer Response: Correct the mount
to make sure that hard is supposed to be on.
parameter options, and reissue mount command.
Detecting Module: GFSCPARS GFSCPARS
GFSC315E ERROR ENCOUNTERED WHILE GFSC319E text IS AN INCORRECT KEYWORD FOR

PARSING MOUNT PATH, REASON NETWORK FILE SYSTEM CLIENT
CODE reason_code. INSTALLATION PARAMETER.
Explanation: The specified mount path is not correct. Explanation: text can only be specified as a mount
parameter.
reason_code
The error reason code. text
The incorrect installation parameter keyword.
processing stops.
programmer. Operator Response: Record the MVS operator
System Programmer Response: Refer to OS/390
programmer.
UNIX System Services Messages and Codes for a
description of the reason code reason_code. Correct the System Programmer Response: Correct the Network
mount path, and reissue the mount command. File System Client installation parameter, stop OS/390
UNIX System Services, and restart OS/390 UNIX
System Services.
GFSC317E ERROR ENCOUNTERED WHILE
PARSING HOSTNAME, REASON CODE
reason_code. GFSC320E INCORRECT OPTION text SPECIFIED
FOR DELIM KEYWORD, VALID OPTION
Explanation: The specified hostname is not correct.
IS BINARY, CR, CRLF, CRNL, LF, LFCR,
In the message text: OR NL.
reason_code Explanation: An incorrect option, text, has been

The error reason code. specified for the keyword, delim.
System Action: The mount command failed. In the message text, text is one of the following:
Operator Response: Record the MVS operator binary
console message and notify the MVS system The binary option for the installation or mount
programmer. delim parameter. Specifies that the access method
does not add a delimiter for each record on output
System Programmer Response: Refer to OS/390 and treats any delimiters on input as data.
UNIX System Services Messages and Codes for a
description of the reason code reason_code. Correct the cr The cr option for the installation or mount delim
hostname, and reissue the mount command. parameter. Specifies the EBCDIC carriage return
delimiter (X'0D').

crlf
GFSC501I CLIENT LOG DATA SET text
The crlf option for the installation or mount delim
RE-INITIALIZED.
delimiter followed by the EBCDIC line feed delimiter Explanation: The error log data set is re-initialized.
(X'0D25').
crnl
text
The crnl option for the installation or mount delim
The associated data set name of the active
DFSMS/MVS NFS Client log data set.
delimiter followed by the EBCDIC new line delimiter
(X'0D15'). System Action: Network File System Client
lf The lf option for the installation or mount delim
parameter. Specifies the EBCDIC line feed delimiter Source: DFSMS/MVS NFS Client
(X'25').
Detecting Module: GFSCTLOG
lfcr
The lfcr option for the installation or mount delim
parameter. Specifies the EBCDIC line feed delimiter GFSC502E CANNOT OPEN CLIENT LOG DATA
followed by the EBCDIC carriage return delimiter SET, text1, text2.
(X'250D'). Explanation: DFSMS/MVS NFS client failed to open
nl The nl option for the installation or mount delim client log data set.
parameter. Specifies the EBCDIC new line delimiter In the message text:
(X'15').
text1
System Action: Network File System Client The DD associated with the client log data set
processing stops if the error is in the Network File which cannot be opened.
command failed if the error is in the mount parameter. text2
The failure reason of the C function, fopen.
console message and notify the MVS system System Action: Network File System Client
programmer. processing stops.
System Programmer Response: If the error is in the Operator Response: Record the MVS operator
mount parameter, correct the option for the keyword, console message and notify the MVS system
delim, and reissue the mount command. If the error programmer.
occurs in the DFSMS/MVS NFS client installation System Programmer Response: Fix client log data
parameter, correct the option for the keyword, delim, set and reply to the OS/390 UNIX System Services
stop OS/390 UNIX System Services, and restart OS/390 message to restart DFSMS/MVS NFS client.
GFSC503E CLIENT LOGGING ENDED.

GFSC500I CLIENT LOG DATA SET, text,
FLUSHED. Explanation: DFSMS/MVS NFS client failed to
manipulate the client log data set. See previous
Explanation: The data buffer of the active client log operator console message for the failure reason.
data set, text, was flushed to disk.
In the message text: processing continues.
text Operator Response: Record the MVS operator
The associated data set name of the active console message and notify the MVS system
DFSMS/MVS NFS Client log data set. programmer.
System Action: Network File System Client System Programmer Response: Fix client log data
processing continues. set, stop DFSMS/MVS NFS client, and reply to the
Source: DFSMS/MVS NFS Client OS/390 UNIX System Services message to restart
DFSMS/MVS NFS client.

GFSC504I CLIENT LOG DATA SET SWITCHED TO
text.
programmer.
Explanation: A ″no space″ or an I/O error condition
System Programmer Response: Fix client log data
was detected while writing to the client log data set.
set, stop DFSMS/MVS NFS client, and reply to the
Network File System Client logging switched to the
OS/390 UNIX System Services message to restart
other log data set, text.
DFSMS/MVS NFS client.
text
The associated data set name of the active
DFSMS/MVS NFS Client log data set.
GFSC700I DFSMS/MVS version NETWORK FILE
SYSTEM CLIENTfmid STARTED
Explanation: The Network File System Client is
initialized and ready to process NFS requests.
In the message text, version is one of the following:
VERSION 1
GFSC505E MISSING DD STATEMENT OR
Version 1 of DFSMS/MVS.
INCORRECT DATA SET
ORGANIZATION FOR LOG DATA SET.
In the message text, fmid is one of the following:
Explanation: The error log data set has incorrect data
set organization, or missing DD statement. (HDZ11SE)
DFSMS/MVS Network File System Client FMID
System Action: Network File System Client started.
processing stops if the error occurred during
initialization time. Network File System Client processing System Action: DFSMS/MVS NFS client continues
continues with client logging ended if the error occurred processing.
after initialization time. Source: DFSMS/MVS NFS Client
Operator Response: Record the MVS operator Detecting Module: GFSCMAIN
programmer.
GFSC701I NETWORK FILE SYSTEM CLIENT
System Programmer Response: Correct error log SHUTDOWN IN PROGRESS.
data set DD statement or data set organization, stop
DFSMS/MVS NFS client, and reply to the OS/390 UNIX Explanation: DFSMS/MVS NFS client shutdown
System Services message to restart DFSMS/MVS NFS processing has started.
client. System Action: DFSMS/MVS NFS client shutdown
Source: DFSMS/MVS NFS Client processing continues.
Detecting Module: GFSCTLOG Source: DFSMS/MVS NFS Client

Detecting Module: GFSCTERM
GFSC506E text1 FAILED FOR text2, text3.
Explanation: DFSMS/MVS NFS client failed to GFSC702I NETWORK FILE SYSTEM CLIENT
manipulate the client log data set, text2. SHUTDOWN COMPLETE.
In the message text: Explanation: DFSMS/MVS NFS client has completed

shutdown processing.
text1
The C function where the failure occurred. System Action: Network File System and its
associated subtasks have ended.
text2
The associated data set name of the DFSMS/MVS Source: DFSMS/MVS NFS Client
NFS Client log data set. Detecting Module: GFSCTERM
text3
The reason for the C function failure.

memory is not available during the DFSMS/MVS NFS
GFSC703E NETWORK FILE SYSTEM CLIENT
client initialization. Do one or both of the following
INITIALIZATION FAILED: NETWORK
before restarting the Network File System Client:
FILE SYSTEM CLIENT IS ALREADY
STARTED. v Increase the REGION size for the client procedure.
v Decrease the value specified for the bufhigh attribute
Explanation: Only one Network File System Client
of the FILESYSTYPE parameter in the BPXPRMxx
can be started on an MVS system.
Parmlib member.
System Action: This Network File System Client
ends.
Detecting Module: GFSCMAIN
programmer. GFSC707E NETWORK FILE SYSTEM CLIENT
INITIALIZATION FAILED: INCORRECT
System Programmer Response: A prior
PARAMETER IN INSTALLATION
DFSMS/MVS NFS client session has not ended.
PARAMETERS.
OS/390 UNIX System Services MVS end processing
should have ended the DFSMS/MVS NFS client colony Explanation: The DFSMS/MVS NFS client has
address space. Collect installation parameters, dumps, detected an error in the installation parameters.
DFSMS/MVS NFS client log data sets, and contact IBM
programming support personnel. Use the force System Action: The Network File System Client ends.
command to end the DFSMS/MVS NFS client colony Operator Response: Record the MVS operator
address space and then restart OS/390 UNIX System console message and notify the MVS system
Services. programmer.
Source: DFSMS/MVS NFS Client System Programmer Response: Check previous
Detecting Module: GFSCMAIN console messages prefixed with GFSC. Correct the
parameter, stop OS/390 UNIX System Services, and
INITIALIZATION FAILED: DOWN LEVEL Source: DFSMS/MVS NFS Client
SECURITY PRODUCT. Detecting Module: GFSCMAIN
Explanation: RACF MVS security product is down
level. GFSC708E NETWORK FILE SYSTEM CLIENT
System Action: The Network File System Client ends. INITIALIZATION FAILED: CDRA IS NOT
INSTALLED OR NOT AVAILABLE
Operator Response: Record the MVS operator RETURN CODE retc, REASON CODE
console message and notify the MVS system reason_code.
programmer.
Explanation: CDRA initialization request failed.
System Programmer Response: Check OS/390
Network File System Customization and Operation to System Action: The Network File System Client ends.
determine the required RACF level. Operator Response: Record MVS operator console
Source: DFSMS/MVS NFS Client message and notify the MVS system programmer.
Detecting Module: GFSCMAIN System Programmer Response: Refer to OS/390

MVS System Messages, Vol 2 (ASB-ERB) for a
description of the return code return_code and the
GFSC705E NETWORK FILE SYSTEM CLIENT reason code reason_code to determine the corrective
INITIALIZATION FAILED: MAIN action.
STORAGE IS UNAVAILABLE.
Source: OS/390 NFS client, module GFSCMAIN
Explanation: The Network File System Client was not
able to allocate the necessary storage. The cause might
be the value specified on the bufhigh attribute is too GFSC709E NETWORK FILE SYSTEM CLIENT
large or the REGION size is too small. INITIALIZATION FAILED: NOT
STARTED IN A STANDALONE COLONY
System Action: The Network File System Client ends. ADDRESS SPACE.
Operator Response: Record the MVS operator Explanation: The DFSMS/MVS NFS client has
console message and notify the MVS system detected an error during initialization processing.
programmer. DFSMS/MVS NFS client was started by some other
System Programmer Response: The requested

means, other than OS/390 UNIX System Services MVS System Services and TCP/IP connection failure.
kernel.
System Action: The Network File System Client ends.
return_code
Operator Response: Record the MVS operator The error return code.
programmer.
Operator Response: Collect any dumps,
System Programmer Response: The DFSMS/MVS
DFSMS/MVS NFS client log data sets, and notify the
NFS client must be initialized by OS/390 UNIX System
system programmer.
Services kernel.
System Programmer Response: Collect installation
parameters, dumps, DFSMS/MVS NFS client log data
Detecting Module: GFSCMAIN sets, and Contact IBM programming support personnel.
INITIALIZATION FAILED: ESTAE
INITIALIZATION FAILED.
Explanation: The DFSMS/MVS NFS client has
LOGGING IS TERMINATED.
detected an error during the initialization processing.
detected an error. The Client Log daemon has ended.
Operator Response: Collect any dumps,
System Action: The Network File System ends.
system programmer. Operator Response: Collect any dumps,
system programmer.
sets, and Contact IBM programming support personnel. System Programmer Response: Collect installation
sets, and Contact IBM programming support personnel.
Detecting Module: GFSCSTAE
INITIALIZATION FAILED: UNIX System
Services KERNEL SERVICE FAILED. GFSC714E NETWORK FILE SYSTEM CLIENT SVC
DUMP REQUEST FAILED, RETURN
CODE returncd REASON CODE
detected an error during the second phase of
reason_code.
initialization processing.
Explanation: A request to take an MVS SVC dump
failed. Refer to the description of the SDUMP macro in
Operator Response: Collect any dumps, OS/390 MVS Programming: Authorized Assembler
DFSMS/MVS NFS client log data sets, and notify the Services Reference LLA-SDU, for the meaning of the
system programmer. return code, return_code, and reason code,
reason_code.
parameters, dumps, DFSMS/MVS NFS client log data In the message text:
sets, and Contact IBM programming support personnel.
return_code
Source: DFSMS/MVS NFS Client The error return code.
Detecting Module: GFSCMAIN reason_code
The error reason code.
GFSC712E NETWORK FILE SYSTEM CLIENT System Action: The Network File System Client ends.
INITIALIZATION FAILED: SOCKET
Operator Response: Collect the MVS console log,
CALL GETHOSTNAME FAILED,
RETURN CODE return_code.
system programmer.
Explanation: The Network File System Client has
detected an error (return_code) during the initialization
processing. This error may be caused by OS/390 UNIX

sets, and Contact IBM programming support personnel. Operator Response: Collect any dumps, the MVS
console log, OS/390 NFS client log data sets, and notify
the system programmer.
System Programmer Response: If the error occurs
and the program is not in error, look at the messages in
GFSC715E NETWORK FILE SYSTEM CLIENT the client log data sets for more information. Search
ESTAE EXIT UNABLE TO COMPLETE, problem reporting data bases for a fix for the problem. If
ABEND CODE d_digit. no fix exists, contact the IBM Support Center. Provide
Explanation: The DFSMS/MVS NFS client recovery related to the problem.
exit has detected a recursive abend.
In the message text: GFSC0RPC
d_digit
The last abend code encountered by a secondary GFSC722E A SOCKET COULD NOT BE CREATED,
instance of the ESTAE exit routine. RETURN VALUE -1 RETURN CODE
System Action: The ESTAE processing stops. The returncd REASON CODE reasoncd.
DFSMS/MVS NFS client ends. Explanation: OS/390 NFS client Daemon or thread
Operator Response: Collect any dumps, the MVS processing failed to create a socket for network
console log, DFSMS/MVS NFS client log data sets, and communication.
notify the system programmer. System Action: If the error occurred in the daemon,
System Programmer Response: Collect installation OS/390 NFS client has initiated shutdown processing. If
parameters, dumps, the MVS console log, DFSMS/MVS the error occurred in the thread, the associated
NFS client log data sets, and Contact IBM programming operation ends and OS/390 NFS client continues
support personnel. processing.
Source: DFSMS/MVS NFS Client Operator Response: Collect any dumps, the MVS
console log, OS/390 NFS client log data sets, and notify
Detecting Module: GFSCSTAE the system programmer.
GFSC716I NETWORK FILE SYSTEM CLIENT UNIX System Services Messages and Codes for a
DAEMON TASK RESTARTED. description of the return code returncd and the reason
Explanation: The DFSMS/MVS NFS client detected a code reasoncd to determine the corrective action. If the
stopped asynchronous daemon task. The DFSMS/MVS error occurs and the program is not in error, look at the
NFS client has restarted the stopped asynchronous messages in the client log data sets for more
daemon task. information. Search problem reporting data bases for a
fix for the problem. If no fix exists, contact the IBM
System Action: The DFSMS/MVS NFS client daemon Support Center. Provide all the printed output and
has restarted. DFSMS/MVS NFS client processing copies of output data sets related to the problem.
continues.
Source: DFSMS/MVS NFS Client GFSC0RPC
GFSC721E UNABLE TO SETUP ERROR ABEND @ module+offset.
RECOVERY (ESTAE), RETURN CODE Explanation: OS/390 NFS client encountered a
returncd. programming error. SVC dump was issued to capture
Explanation: OS/390 NFS client daemon or thread the diagnostic information.
failed to setup error recovery. See OS/390 MVS System Action: OS/390 NFS client has initiated
Programming: Authorized Assembler Services shutdown processing.
Reference ENF-IXG for information the ESTAE macro
return code, returncd. System Programmer Response: Look at the
messages in the client log data sets for more
System Action: If the error occurred in the daemon, information. Search problem reporting data bases for a
OS/390 NFS client has initiated shutdown processing. If fix for the problem. If no fix exists, contact the IBM
the error occurred in the thread, the associated Support Center. Provide all the printed output and
operation ends and OS/390 NFS client continues copies of output data sets related to the problem.
processing.
Detecting Module: OS/390 NFS client, modules

GFSC0RPC, GFSC1RPC, GFSC0BIO, GFSC1BIO, and -e Display the list of exported directories from host
GFSC2BIO NFS server
GFSC724E UNABLE TO BIND A RESERVED PORT GFSC841E UNKNOWN HOST text

TO SOCKET socketnum.
Explanation: The user entered incorrect host address
Explanation: The MOUNT daemon or UMOUNT information, text.
thread failed to obtain a reserved port for socket,
System Action: Command stops processing.
socketnum, for network communication.
User Response: Correct syntax and re-issue the
System Action: If the error occurred in the daemon,
command.
OS/390 NFS client has initiated shutdown processing. If
the error occurred in the thread, the associated
operation ends and OS/390 NFS client continues GFSC842E CANNOT RESOLVE LOCAL HOST
processing. NAME
System Programmer Response: If the error occurs Explanation: Local host name is not found.
the client log data sets for more information. Search System Action: Command stops processing.
problem reporting data bases for a fix for the problem. If User Response: Contact your system administrator to
no fix exists, contact the IBM Support Center. Provide check TCP/IP configuration.
GFSC843E UNKNOWN FLAG ’-character’
GFSC0RPC Explanation: An incorrect option, ’-character’, is
specified.
GFSC725E SOCKET, socketnum, COULD NOT BE System Action: Command stops processing.
CLOSED, RETURN VALUE -1 RETURN User Response: Correct syntax and re-issue the
CODE returncd REASON CODE command.
reasoncd.
Explanation: While closing a socket, socketnum, an GFSC845I USAGE: text INPUT OUTOUT
error returncd was detected.
Explanation: This is the usage for the os22mvs and
System Action: OS/390 NFS client continues mvs2os2 commands. text is the command as entered
processing. by the user. The valid parameters are as follows:
System Programmer Response: Refer to OS/390 input
UNIX System Services Messages and Codes for a Absolute path name of the input file to be converted
description of the return code returncd and the reason
code reasoncd to determine the corrective action. If the output
error occurs and the program is not in error, look at the Absolute path name of the output file
messages in the client log data sets for more
information. Search problem reporting data bases for a GFSC846E CANNOT OPEN INPUT FILE, text1:text2
Support Center. Provide all the printed output and Explanation: Cannot open input file, text1. text1 is the
copies of output data sets related to the problem. input path name as entered by the user. text2 is the
failure information returned when attempting to open the
Detecting Module: OS/390 NFS client, module input file.
GFSC0RPC
GFSC840I usage: text [-a] [-d] [-e] [host] User Response: Check input file, text1.
Explanation: This is the usage for the showmount

command. text is the command as entered by the user. GFSC847E CANNOT OPEN OUTPUT FILE,
The valid options are as follows: text1:text2
-a Display all mounts in the format Explanation: Cannot open output file, text1. text1 is
Hostname:Directory from host NFS server the output path name as entered by the user. text2 is
the failure information returned when attempting to open
-d Display only directory names of all mounts from the output file.
host NFS server

User Response: Check output file, text1.
GFSC855E MUST BE A ROOT USER TO ISSUE
’character’ flag
GFSC848E CANNOT READ INPUT FILE, text1: text2
Explanation: The option, ’character’, can only be
Explanation: Cannot read input file, text1. text1 is the issued with the root authority.
input path name as entered by the user. text2 is the
failure information returned when attempting to read the
input file. User Response: Contact your system administrator to
issue this command.
User Response: Check input file, text1.
COMMAND, text, FAILED RETURN
GFSC849E CANNOT WRITE OUTPUT FILE, text1: VALUE -1 RETURN CODE returncd
text2 REASON CODE reasoncd
Explanation: Cannot write output file, text1. text1 is Explanation: The command, text, failed.
the output path name as entered by the user. text2 is
the failure information returned when attempting to write
the output file. User Response: Refer to OS/390 UNIX System
return code, returncd. Refer to OS/390 Network File
User Response: Check output file, text1. System Customization and Operation for further
information on the reason code, reasoncd.
GFSC850E INPUT PATH NAME CANNOT BE

EQUAL TO OUTPUT PATH NAME. GFSC858E DIRECTORY text NOT MOUNTED.
Explanation: Input path name cannot be equal to Explanation: The directory, text, was not mounted.
output path name.
User Response: Issue ’nfsstat -m’ to view the list of
User Response: Correct syntax and re-issue the active mount points. If the mount point does not exist,
command. contact system administrator to mount the directory.
Detecting Module: GFSCWO2M or GFSCWM2O
GFSC854I usage: text [-crnzm <mount point> ]

Explanation: This is the usage for the nfsstat
command. text is the command as entered by the user.
The valid parameters are as follows:
-c Display both NFS and RPC statistics about OS/390
NFS client
-n Display NFS statistics about OS/390 NFS client
-r Display RPC statistics about OS/390 NFS client
-z Initializes statistics to zero. This is for use by root
user only and can be combined with any of the
above options. Zero particular set of statistics after
printing them.
-m Display the name of each NFS mounted file system
-m mount point
Display information of NFS mounted file system on
the specified mount point

Chapter 7. GOS Messages
than 8 characters, begins with an invalid symbol, or
GOS000I SOM/MVS SUBSYSTEM ssname:
contains an imbedded blank.
PRODID=productid PRODLVL=productlvl
COMPID=compid (C) COPYRIGHT IBM In the message text:
CORP. 1995, 1997 ALL RIGHTS
RESERVED. U.S. GOVERNMENT ssname
USERS RESTRICTED RIGHTS - USE, is the name of the SOMobjects subsystem.
DUPLICATION, OR DISCLOSURE System Action: SOMobjects subsystem initialization
RESTRICTED BY GSA ADP SCHEDULE continues. The specified command prefix value is
CONTRACT WITH IBM CORP. ignored and as a default, the subsystem name ssname
Explanation: This is a proprietary statement is used as the command prefix.
concerning the use of the SOMobjects product. The Operator Response: If the default command prefix is
second line of the message indicates the product id, unacceptable, enter a CANCEL command prefixed by
product level, and component id of the product. the ssname to cancel the SOMobjects subsystem
In the message text: immediately. Then if the bad command prefix was
entered by you as a parameter on the START command
ssname when you first started SOMobjects, re-enter the START
is the name of the SOMobjects subsystem. command to restart the SOMobjects subsystem with a
valid command prefix value.
productid
The SOMobjects product id. If the bad command prefix was not specified by you on
the START command, notify your system programmer.
productlvl
The SOMobjects product level. System Programmer Response: If the bad command
prefix was specified as a parameter in the job procedure
compid
that was used to start the SOMobjects subsystem,
The SOMobjects component id.
correct the command prefix parameter in the procedure
System Action: SOMobjects subsystem processing so the next time the subsystem is started, the desired
continues. command prefix will be used.
Source: SOM Source: SOM
GOS006I SOM/MVS SUBSYSTEM JOBNAME GOS008I SOM/MVS ssname COMMAND PREFIX

jobname IS NOT VALID. IS cmdprefix
Explanation: The SOMobjects procedure name, which Explanation: The command prefix that is being used
is used as the name of the subsystem, is not a valid 1-4 by the SOMobjects subsystem ssname is cmdprefix. All
character name. commands entered for the subsystem should begin with
this prefix.
jobname
The name of the SOMobjects job or started ssname
procedure. The name of the SOMobjects subsystem.
System Action: The SOMobjects address space cmdprefix
ends. is a 1-8 character command prefix.
System Programmer Response: Ensure that the System Action: SOMobjects subsystem initialization
SOMobjects job name/procedure name is a valid continues.
subsystem name (1-4 characters).
Operator Response: Whenever you enter one of the
Source: SOM commands supported by the SOMobjects subsystem,
you must begin the command with the indicated
command prefix (e.g., cmdprefix STATUS).
GOS007I SOM/MVS ssname INPUT COMMAND
PREFIX IS NOT VALID. DEFAULT Source: SOM
PREFIX USED.
Explanation: A command prefix value that was
specified as input to the SOMobjects subsystem
ssname is not valid. The prefix value is either greater

Operator Response: If you were restarting the
GOS009I SOM/MVS ssname INITIALIZATION
SOMobjects subsystem after an error situation, ensure
COMPLETE.
that the first instance of the subsystem ends before
Explanation: The SOMobjects subsystem ssname has issuing the START command.
completed its initialization.
Source: SOM
ssname GOS013I SOM/MVS ssname IS NOT A VALID
is the name of the SOMobjects subsystem. SUBSYSTEM.
System Action: The SOMobjects subsystem Explanation: The SOMobjects subsystem ssname is
continues processing. It is now ready to accept not a defined subsystem name known by the system.
distributed SOM requests.
Source: SOM
ssname
The name of the SOMobjects subsystem.
GOS010I SOM/MVS ssname ENDED.
System Action: The SOMobjects subsystem ends.
Explanation: The SOMobjects subsystem ssname has
completed shutting down.
SOMobjects subsystem name ssname is defined as a
In the message text: valid subsystem name in the IEFSSNxx SYS1.PARMLIB
member that was used to IPL the system.
ssname
is the name of the SOMobjects subsystem. Source: SOM
System Action: The SOMobjects subsystem address
space ends. GOS019I INITIALIZATION COMPLETE FOR
SOM/MVS SERVER server_name WITH
Source: SOM
ALIAS alias_name
Explanation: A SOMobjects server has completed
GOS011I SOM/MVS ssname INITIALIZATION
initialization. The ALIAS for this server is aliasname.
FAILED.
Explanation: The SOMobjects subsystem ssname
could not be successfully initialized. The specific server_name
initialization error is indicated by a SOMobjects error The name of the SOMobjects server, which is
message or abend that was issued just prior to this specified on DSOM server utility commands. See
message. OS/390 SOMobjects Configuration and
Administration Guide for a descriptions of those
commands.
ssname
alias_name
is the name of the SOMobjects subsystem.
The alias of the SOMobjects server.
System Action: The SOMobjects server continues
System Programmer Response: Examine the processing. It is ready to accept requests from
SYSLOG to determine the error message or abend that distributed SOM clients.
caused initialization to fail and then correct the condition
Source: SOM
that caused the error.
Source: SOM
GOS021I SOM/MVS ssname SUBSYSTEM
FUNCTIONS DISABLED.
GOS012I SOM/MVS ssname ALREADY ACTIVE.
Explanation: In the process of ending either normally
Explanation: One instance of the SOMobjects or abnormally, the SOMobjects subsystem ssname
subsystem ssname already exists. Starting more than disabled the subsystem functions it normally provides
one SOMobjects subsystem is not allowed. for jobs that use Distributed SOM (DSOM) services via
the SOMobjects subsystem.
ssname
The name of the SOMobjects subsystem. ssname
is the name of the SOMobjects subsystem.
System Action: The SOMobjects subsystem that
issued this message ends. System Action: The SOMobjects subsystem ends.

Distributed SOM requests will no longer be processed. cmdname
Any usage of servers, clients, and DSOM utilities will be The name of the command that was entered.
affected.
System Action: The SOMobjects subsystem stops
Source: SOM processing the command.
Operator Response: If the keyword was misspelled,
GOS022I SOM/MVS ssname SUBSYSTEM enter the command again with the correct keyword
FUNCTION DISABLEMENT FAILED. specified. Otherwise, if the keyword should not have
been specified, enter the command again without the
unsupported keyword.
or abnormally, the SOMobjects subsystem ssname
attempted to disable the subsystem functions it normally Source: SOM
provides for jobs that use Distributed SOM (DSOM)
services via the SOMobjects subsystem. However, a
GOS025I MVS/DSOM ssname cmdname
failure occurred that prevented the subsystem from
COMMAND ERROR -- NOT
completely disabling all the subsystem functions it
AUTHORIZED TO ISSUE COMMAND.
supports.
Explanation: The operator/console is not authorized to
enter the command, cmdname.
ssname
ssname
Any jobs, managed by the subsystem shown in the
message text, that try to use DSOM services might cmdname
abnormally end. The name of the command that was entered.
Source: SOM System Action: The SOMobjects subsystem stops
processing the command.
GOS023I SOM/MVS SUBSYSTEM ssname Operator Response: Contact your installation’s
ALTERED TO USE THE PRIMARY security administrator to ensure both you and the
SUBSYSTEM. console are properly authorized to enter the command
that you were attempting.
Explanation: The SOMobjects subsystem is to be
started only under the primary subsystem. The system Source: SOM
issues this message if your installation specifies the
SOMobjects subsystem initialization routine,
GOSAMSSI, on the initialization statement for the GOS026I MVS/DSOM ssname STOP INITIATED.
SOMobjects subsystem in the IEFSSNxx parmlib Explanation: In response to a STOP command, the
member. The SOMobjects subsystem initialization SOMobjects subsystem ssname has initiated stop
routine will always force the specified SOMobjects processing.
subsystem is to be initialized under only the primary
subsystem. This message is written to hardcopy only. In the message text:
In the message text: ssname

ssname
The name of the SOMobjects subsystem. System Action: The SOMobjects subsystem quiesces
its processing and ends processing for servers that are
System Action: System initialization continues. in running. When all server activity ends, the
Source: SOM SOMobjects subsystem ends normally.
Source: SOM
GOS024I SOM/MVS ssname cmdname COMMAND
ERROR -- SPECIFIED KEYWORD IS GOS027I hh.mm.ss ssname HELP INFO
NOT VALID. MVS/DSOM COMMAND SYNTAX: ...
Explanation: The command entered, cmdname, STOP DAEMON ... CANCEL DAEMON
specified a keyword that is not supported. ..... Not Supported
In the message text: Explanation: This message is a multiline message

issued in response to the HELP command. It displays a
ssname summary of the syntax for the commands supported by
The name of the SOMobjects subsystem. the SOMobjects subsystem shown in the message text.
Chapter 7. GOS Messages 221

In the message text: (prefix ITT) accompanying this message.
hh.mm.ss Source: SOM
The time in hours (00-23), minutes (00-59), and
seconds (00-59).
GOS033I DSOM TRACE REQUEST FAILED.
ssname OPTIONS ARE NOT ALLOWED.
Explanation: The system rejected the request to trace
System Action: Processing continues. the system object model (SOM). The TRACE command
specified options, but options are not allowed.
Source: SOM
System Action: The system rejects the request to
trace SOM.
GOS031I SOM/MVS ssname INITIALIZATION OF
DAEMON SUBTASK FAILED. Operator Response: Enter the TRACE command
again without specifying any options.
Explanation: The SOMobjects subsystem ssname
could not properly initialize the SOM subsystem Source: SOM
subtask. More error information may be available from
the SYSPRINT output, if available, or from the TRACE
GOS041I SOM/MVS ssname WAITING FOR
log, if available.
SERVERS TO END.
ssname or abnormally, the SOMobjects subsystem ssname must
is the name of the SOMobjects subsystem. wait for distributed SOM (DSOM) servers to end before
the subsystem is ended.
ssname
SYSLOG or the job’s log or the SYSPRINT data set for
the job to determine the error message or abend that System Action: The SOMobjects subsystem will wait
caused initialization to fail. Analyze the TRACE log, if for the servers to end. If the servers do not end, the
one was requested. Ensure that the correct data sets SOMobjects subsystem stops waiting and finishes
are specified for the GOSRTL1 DD. Correct the ending. After that time, servers may end abnormally.
condition that caused the error.
Source: SOM
Source: SOM
GOS042I SOM/MVS ssname WAITING FOR OMVS
GOS032I SYSDSOM COMPONENT TRACE TO START.
FAILED. DIAG1: nnnnnnnn xxxxxxxx
Explanation: In the process of initialization, the
Explanation: The SYSDSOM (SOMobjects) SOMobjects subsystem ssname must wait for the
component tried to initialize component tracing using OS/390 UNIX address space to initialize before
default options. The system is now running without completing subsystem initialization.
component tracing for SYSDSOM.
ssname
nnnnnnnn The name of the SOMobjects subsystem.
Used by IBM for problem determination.
System Action: The SOMobjects subsystem waits for
xxxxxxxx the OMVS address space to initialize.
Used by IBM for problem determination.
Source: SOM
System Action: Initialization continues without
component tracing for SYSDSOM. The system issues
component trace messages (prefix ITT) explaining the
problem.
Operator Response: See the operator response for
the component trace messages (prefix ITT)
accompanying this message.
System Programmer Response: See the system
programmer response for component trace messages

Chapter 8. GPM Messages
GPM001I PM OF OS/390 DATA SERVER ACTIVE GPM006E TCP/IP PORT NUMBER NOT
SPECIFIED
Explanation: The PM of OS/390 data server has been
initialized and is ready to receive connection requests Explanation: The PM of OS/390 data server has been
from PWS clients. started without a valid TCP/IP port parameter.
System Action: Processing continues. System Action: The PM of OS/390 data server ends
processing.
Source: Resource Measurement Facility (RMF) -
Performance Monitoring of OS/390 (PM of OS/390) Operator Response: Specify a valid TCP/IP port
number with the START command of the PM of OS/390
data server.
GPM002I PM OF OS/390 DATA SERVER
TERMINATED Source: Resource Measurement Facility (RMF) -
Performance Monitoring of OS/390 (PM of OS/390)
Explanation: The PM of OS/390 data server has
ended.
GPM050I GPMSERVE CANNOT FIND MEMBER
System Action: System processing continues.
member IN PARMLIB
Explanation: The DDS host server address space
GPM003I PM OF OS/390 IDLE TIME EXCEEDED
cannot find the specified PARMLIB member. It continues
Explanation: The time specified by the MAXIDLE processing and uses defaults parameters.
parameter for the PM of OS/390 data server has
System Action: The host server continues the
elapsed without any transaction requests.
initialization using default parameters.
System Action: The PM of OS/390 data server ends
Operator Response: Inform the system programmer.
processing.
System Programmer Response: Make sure that a
Operator Response: Restart the PM of OS/390 data
valid GPMSRVxx PARMLIB member exists in the
server.
parameter library (usually the PARMLIB concatenation).
System Programmer Response: If needed, specify a
longer period for the MAXIDLE parameter.
GPM051I TCP/IP IS NOT ACTIVE ON THE OS/390
HOST
GPM004E LIBRARY IS NOT IN APF TABLE
Explanation: The PM of OS/390 data server resides Performance Monitoring of OS/390 (PM of OS/390)
in a load library without APF authorization.
Explanation: The TCP/IP component of OS/390 is not
System Action: The PM of OS/390 data server ends active on the OS/390 host. The GPMSERVE address
processing. space has detected that TCP/IP services are not
available.
System Programmer Response: Ensure that the PM
of OS/390 load library is APF authorized. System Action: The host server terminates.
Source: Resource Measurement Facility (RMF) - Operator Response: Inform the system programmer.
System Programmer Response: Make sure that the
TCP/IP component of OS/390 is active before the DDS
GPM005E INVALID COMMAND FOR PM OF host server is started.
OS/390
Explanation: An unsupported MODIFY command has GPM052I TRACE IS NOW (IN)ACTIVE
been entered for the PM of OS/390 data server.
System Action: Processing continues. Performance Monitoring of OS/390 (PM of OS/390)
Source: Resource Measurement Facility (RMF) - Explanation: This message is issued in response to
Performance Monitoring of OS/390 (PM of OS/390) the MODIFY command for the GPMSERVE address
space with the TRACEON or TRACEOFF option.

System Action: If the trace is active, GPMSERVE will System Action: The server is terminated immediately.
put its trace output to DDNAME SYSOUT. If the trace is
inactive, GPMSERVE will no longer write trace output to
erroneous option member.
DDNAME SYSOUT.
GPM057I SPECIFIED HOSTNAME ’hostname’

GPM054I PERMANENT ERROR IN PM OF OS/390
CANNOT BE RESOLVED
SERVER THREAD
Explanation: The ACCEPT_DATAGRAM parameter in
Explanation: The DDS host server has detected that
the GPMSRVxx member contains a hostname, that can
an important component of the server address space
not be resolved by the name server.
has encountered a permanent error. In this case, the
component that accepts incoming TCP/IP session System Action: The indicated hostname is discarded.
requests has abnormally terminated. The most probable
cause for this problem is, that TCP/IP is inactive or has System Programmer Response: Correct the
produced an error. erroneous option member.
System Action: The component is restarted. After 5

unsuccessful requests. the component is deactivated. GPM058I I/O ERROR READING PARMLIB
MEMBER name
System Programmer Response: Make sure that all
required prerequisites for the component are active and Source: Resource Measurement Facility (RMF) -
operational (for example, TCP/IP). Make sure that the Performance Monitoring of OS/390 (PM of OS/390)
specified port in the GPMSRVxx PARMLIB member Explanation: The DDS host server address space
(SESSION_PORT option) is free and can be used by detected an I/O error reading the specified PARMLIB
the DDS host server. member. It continues processing and uses default
parameters.
GPM055I SESSION WITH partner ABNORMALLY System Action: The server is terminated immediately.
TERMINATED
Operator Response: Inform the system programmer.
Performance Monitoring of OS/390 (PM of OS/390) System Programmer Response: Make sure that a
valid GPMSRVxx PARMLIB member exists in the
Explanation: A session with the specified partner has parameter library (usually the PARMLIB concatenation).
been terminated because of a timeout or an error
condition. The specified partner may be specified as
v An IP address such as ″9.164.181.128″ GPM059I COMMAND ’ccccc’ IS NOT VALID
v A symbolic host name such as Source: Resource Measurement Facility (RMF) -
″smith.boeblingen.ibm.com″ Performance Monitoring of OS/390 (PM of OS/390)
v A unix path name such as ″/tmp/GPMServe.C00″
Explanation: The MODIFY command that was issued
System Action: The session is terminated against the DDS data server is not a valid command.
immediately.
System Action: The command is ignored.
required prerequisites for the component are active and User Response: Specify a valid command.
operational (for example, TCP/IP). Make sure that the
timeout option in the GPMSRVxx PARMLIB member GPM060I DDS SERVER READY FOR
(TIMEOUT option) is set properly, and that the DDS COMMANDS
host server is active.
GPM056I SYNTAX ERROR IN GPMSRVNN
MEMBER. LINE: ll NEAR TEXT ’ttttttt’ Explanation: The DDS server is now accepting
commands from the console.
Performance Monitoring of OS/390 (PM of OS/390) User Response: None.
Explanation: A syntax error was detected in the

GPMSRVxx member. The error was detected in the line
that is indicated in the message, and the string indicates
the erroneous text.

GPM061I OPTIONS IN EFFECT: options GPM064I PERMANENT ERROR IN UNIX
SESSION SERVER
Performance Monitoring of OS/390 (PM of OS/390) Source: Resource Measurement Facility (RMF) -
Explanation: This message lists the currently active
options for the DDS server. Explanation: The DDS host server has detected that
component that accepts incoming session requests via
GPM062I component last_status UNIX domain sockets (for example, PM of OS/390
APPC clients) has abnormally terminated.
Performance Monitoring of OS/390 (PM of OS/390) System Action: The component is restarted. After 5
unsuccessful requests. the component is deactivated.
Explanation: This message displays the status of an
active component of the DDS server. The component System Programmer Response: Make sure that all
may be: required prerequisites for the component are active and
operational (mainly OS/390 UNIX System Services).
RMF-REFR The automatic data refresher
Make sure that the pathname
DM-SERV The datagram server
/tmp/gpmserve/pmos390
INET-LIS Task that listens for incoming TCP/IP
requests is free and can be used by the DDS server.
CMD-HNDL MODIFY command handler
If more than one instance of the DDS host server is
INET-CLI TCP/IP client started, this message will appear for all instances but
UNIX-CLI UNIX client the first one, because the UNIX socket pathname
cannot be shared by different servers. In this case,
HTTP-LIS The task that listens for incoming always the first server will handle incoming UNIX
HTTP requests session requests.
HTTP-CLI The HTTP session client
This message might be caused by using the old OS/2
System Action: None version of PM of OS/390 which is not supported
anymore. Please, insure that only the Java Edition of
User Response: None
PM of OS/390 will be used.
GPM063I PERMANENT ERROR IN DM/390

GPM065I SERVER NOT STARTED FROM AN
SERVER THREAD
AUTHORIZED LIBRARY
Explanation: The DDS host server has detected that
Explanation: The DDS host server has not been
started from an APF-authorized library, but APF
authorization is necessary for the GPMDDSRV host
component that processes incoming performance
server module.
request datagrams has abnormally terminated. The
most probable cause for this problem is, that TCP/IP is System Action: The host server is terminated.
inactive or has produced an error.
System Action: The component is restarted. After 5 library, where the GPMDDSRV module resides (usually
unsuccessful requests. the component is deactivated. SYS1.SERBLINK) is APF-authorized.
required prerequisites for the component are active and GPM066I DDS SERVER TERMINATED
operational (for example, TCP/IP). Make sure that the
specified port in the GPMSRVxx PARMLIB member Source: Resource Measurement Facility (RMF) -
(DATAGRAM_PORT option) is free and can be used by Performance Monitoring of OS/390 (PM of OS/390)
the DDS host server. Explanation: The DDS host server has terminated.
System Action: None
System Programmer Response: None
Chapter 8. GPM Messages 225

GPM067I VALUE ’xxxx’ IS NOT ALLOWED FOR
OPTION yyyyy
Explanation: The specified option value is not allowed
or outside the allowed range for the option.
System Action: The server is terminated immediately.
erroneous option member.
GPM069I SEVERE ERROR: ALLOCATION FAILED

FOR CACHE STORAGE
Explanation: The server has detected a problem
when trying to allocate additional storage for the data
cache. The most probable cause for this problem is,
that the REGION size is too small.
System Action: The server is terminated with a fatal
error.
v Increase the REGION parameter on the JOB or
EXEC record.
v Make sure that the requested region size is really
available to the server program (check that the
system exit IEFUSI does not reduce the requested
region size).
v Reduce the number of cache slots in the PARMLIB
member GPMSRVxx (CACHESLOTS option). The
default number of slots is 4.

Chapter 9. IAR Messages
IAR002A ‘REAL = xxxx’ IS TOO LARGE, IAR004I THE RSU PARAMETER WAS NOT
MAXIMUM AVAILABLE IS yyyy. COMPLETELY SATISFIED
RESPECIFY OR PRESS ENTER FOR
Explanation: During system initialization, the real
THE DEFAULT
storage manager (RSM) found that system storage
Explanation: The system cannot allocate the requirements and the REAL parameter have not left
requested V=R area because it would overlap the virtual enough central storage to satisfy the reconfiguration
storage allocated for the common service area (CSA). storage units (RSU) parameter. The REAL and RSU
parameters are in the IEASYSxx parmlib member.
System Action: The system makes available as many
xxxx The kilobytes of central (real) storage specified.
storage units as possible for reconfiguration, but the
yyyy The maximum kilobytes of central storage RSU parameter is not completely satisfied.
allowed.
Operator Response: Enter a Display M command to
System Action: The system waits for the operator to determine which storage units are available for
reply. reconfiguration. Notify the system programmer.
Operator Response: Reenter the parameter with a System Programmer Response: Change the
value equal to or less than yyyy or press ENTER to get parameters in IEASYSxx before the next IPL.
the default. The default value for the REAL parameter is
Source: Real storage manager (RSM)
the smaller of the following two values:
v 76 kilobytes Detecting Module: IARMT, IAXMT
v The amount of storage available for a V=R area that
does not overlap the CSA IAR005E PREFERRED AREA HAS EXPANDED,
RECONFIGURABILITY AND
PERFORMANCE MAY BE IMPAIRED.
Detecting Module: IARMS, IAXMS CHECK RSU VALUE.
Explanation: The real storage manager (RSM)
IAR003W AN INVALID SEGMENT TABLE ENTRY converted one or more nonpreferred frames to preferred
WAS FOUND FOR THE area AREA frames. The system may no longer be able to
reconfigure all or part of the storage in the nonpreferred
Explanation: During system initialization, the real area. If this expansion involves frames below 16
storage manager (RSM) attempted to page protect an megabytes, the system can page fix these frames,
area. RSM found an incorrect segment table entry which might lead to performance problems.
(SGTE) for this area.
System Action: The system can use the newly
In the message text, area identifies the area to be page designated frames as preferred storage for additional
protected and is one of the following: long term resident pages.
MLPAModified link pack area Operator Response: Enter a Display M command to

EXTENDED MLPA determine the number of frames remaining in the
READ-ONLY NUCLEUS nonpreferred area.
NUCMAPNucleus map System Programmer Response: Check that the
PLPAPageable link pack area reconfigurable storage unit (RSU) value specified in the
EXTENDED PLPA IEASYSxx parmlib member is appropriate for your
BLDLBuild directory entry list installation. See OS/390 MVS Initialization and Tuning
FLPAFixed link pack area Reference for more information about the IEASYSxx
EXTENDED FLPA parmlib member.
System Action: The system enters wait state X'A21'. Source: Real storage manager (RSM)
Operator Response: See the operator response for Detecting Module: IARUC, IAXUC
wait state code X'A21'.
programmer response for wait state code X'A21'.
Detecting Module: IARMN, IAXMN

PREVIOUS INVOCATION TERMINATION HAS NOT
IAR006A INVALID {VRREGN|REAL|RSU} PARM -
COMPLETED.
RESPECIFY OR PRESS ENTER FOR
THE RSM TRACE DATA SPACE COULD NOT BE
THE DEFAULT
CREATED.
Explanation: The VRREGN, REAL, or RSU parameter TOTAL SIZE OF BUFFERS EXCEEDS TRACE
contains a value that is not valid. DATA SPACE SIZE.
UNIDENTIFIED OPTION.
System Action: The system waits for the operator to
reply. System Action: The system does not start the RSM
component trace.
Operator Response: Reenter the VRREGN, REAL, or
RSU parameter with a valid value. Operator Response: Depending on the value of text,
do one of the following:
INVALID PARAMETER SPECIFIED FOR BUFF=
Detecting Module: IARMU, IARMS, IARMT, IAXMU,
OPTION or UNIDENTIFIED OPTION
IAXMS, IAXMT
One of the options is incorrect. Correct the error.
Reenter the TRACE command.
IAR007I RSM COMPONENT TRACE DATA
PREVIOUS INVOCATION TERMINATION HAS NOT
SPACE IS NAMED ″SYSIARnn″.
COMPLETED
Explanation: The operator started the real storage Wait a few minutes and reenter the TRACE
manager (RSM) component trace using the TRACE CT command. If the error occurs again, contact the
operator command and requested that RSM use a data IBM Support Center.
space for its trace buffers.
System Programmer Response: Depending on the
If the TRACE command specified NODMPOFF but not value of text, do one of the following:
DMPREC, the system does not dump these buffers.
ENVIRONMENTAL ERROR or THE RSM TRACE
The operator has to request a dump.
DATA SPACE COULD NOT BE CREATED
In the message text: An unexpected error occurred during trace
initialization. Contact the IBM Support Center.
SYSIARnn
The name and number of the data space. INSUFFICIENT STORAGE FOR TRACE BUFFERS
There is not enough fixed common service area
System Action: The system starts the RSM (CSA) storage for trace buffers. First, ensure that
component trace. RSM uses data space SYSIARnn to the size specified on the BUFF option is correct. If
contain the trace data. the BUFF option was specified correctly, then either
Operator Response: Use the data space name in this reduce the amount specified or increase the
message to obtain the RSM trace buffers in an SVC amount of CSA available to the system.
dump requested by a DUMP command or in a INSUFFICIENT STORAGE FOR TRACE
stand-alone dump. However, to obtain the dump when INITIALIZATION
the RSM trace is turned off or through the use of the There is not enough system queue area (SQA)
DMPREC option, the data space name is unnecessary. virtual or central storage available for trace
Source: Real storage manager (RSM) initialization; a request failed for a relatively small
amount of SQA storage. Increase the size of SQA
Detecting Module: IARQC virtual or central storage.
TOTAL SIZE OF BUFFERS EXCEEDS TRACE DATA
IAR008E RSM TRACE TERMINATED, text SPACE SIZE
Explanation: The operator attempted to start the real The size of the trace buffers that reside in fixed
storage manager (RSM) component trace using the CSA storage is larger than the size of the trace
TRACE CT operator command. RSM did not start the data space. The size of the fixed trace buffers must
trace. be smaller than the data space size so they can be
copied to the data space. Respecify the size of the
In the message text, text tells why RSM did not start the fixed buffers and the size of the trace data space.
trace, as follows:
ENVIRONMENTAL ERROR. Source: Real storage manager (RSM)
INSUFFICIENT STORAGE FOR TRACE BUFFERS. Detecting Module: IARQC
INSUFFICIENT STORAGE FOR TRACE
INITIALIZATION.
INVALID PARAMETER SPECIFIED FOR BUFF=
OPTION.

Detecting Module: IARQZ, IAXQZ
IAR009I RSM COMPONENT TRACE HAS LOST
AN ENTRY BECAUSE ALL BUFFERS
WERE FULL. IAR011I RSM COMPONENT TRACE EXTERNAL
WRITER MAY HAVE LOST ENTRIES
Explanation: The operator started the real storage
manager (RSM) component trace and requested that a Explanation: The operator started the real storage
trace data space be used to contain the trace data. manager (RSM) component trace and requested that
RSM lost some of the trace entries because it was the system write the trace entries to a trace data set
creating trace entries faster than it could copy them through the external writer. The system could not write
from central storage to the trace data space. the trace entries to the data set for one of the following
reasons:
System Action: The RSM component trace continues.
Trace entries continue to be lost until RSM finishes v The operator did not start the external writer before
copying the trace buffers to the data space. RSM then connecting the RSM component trace to the external
re-uses the buffers for newer trace entries. writer.
v RSM reused the full trace buffer before the system
could write the trace entries out to the trace data set.
System Programmer Response: If the RSM trace Some older trace entries have been lost.
successfully captured enough data to diagnose the
System Action: The system continues processing the
problem, the message indicates no problem. When the
RSM component trace.
trace is turned off, examine the trace entries in the
dump. The trace data gives the number of entries lost. System Programmer Response: Do one of the
following:
If the trace did not capture enough data to diagnose the
problem, re-create the problem and ask the operator to v If you did not start the external writer, start it before
start the trace again and either: connecting the RSM component trace to the external
writer,
v Increase the size of the central storage trace buffers,
using the BUFF option v Use IPCS to examine the trace entries that the
system collected. If the trace did not collect enough
v Decrease the need for buffers by specifying fewer
data to successfully diagnose the problem, start the
RSM trace functions and events
trace again and either:
Source: Real storage manager (RSM) – Use more trace buffers.
– Increase the size of the trace buffers.
Detecting Module: IARQZ, IAXQZ
IAR010I RSM COMPONENT TRACE HAS Detecting Module: IARQZ, IAXQZ
WRAPPED AN ALREADY FULL
BUFFER.
IAR011W A PAGE WITHIN FLPA IS NOT PAGE
Explanation: The operator started the real storage FIXED.
manager (RSM) component trace and requested that
the trace data be collected in central storage buffers.
detected pageable storage within the range of the fixed
RSM overlaid some older trace entries with newer trace
link pack area (FLPA) or the EXTENDED FLPA.
entries when the central storage buffers filled up.
System Action: The system enters wait state X'A20'.
System Action: The RSM component trace continues.
Newer trace entries continue to overlay older trace Operator Response: See the operator response for
entries. wait state X'A20'.
Operator Response: Notify the system programmer. System Programmer Response: See the system
programmer response for wait state X'A20'.
System Programmer Response: This message
almost always appears when the RSM component trace Source: Real storage manager (RSM)
is being used without a trace data space. It usually does
not indicate a problem. When the trace is turned off, Detecting Module: IARMN, IAXMN
examine the trace entries in the dump. If the trace did
not capture enough data to diagnose the problem, IAR012W A PAGE WITHIN PLPA OR MLPA HAS
re-create the problem and ask the operator to start the NO COPY ON AUXILIARY STORAGE
trace again and either:
v Increase the size of the central storage trace buffers
detected a page within the range of the pageable link
v Use a trace data space pack area (PLPA), EXTENDED PLPA, the modified link
Source: Real storage manager (RSM) pack area (MLPA), or the EXTENDED MLPA that has
never been paged to auxiliary storage. Ranges of
Chapter 9. IAR Messages 229

system storage that are page protected must have a the additional storage should be configured as
copy on auxiliary storage so the system can refresh the expanded storage and the system re-IPLed.
page if necessary.
System Action: The system enters wait state X'A2A'.
Detecting Module: IARMI
wait state X'A2A'.
IAR016I THE SYSTEM WAS IPLED IN ESAME
programmer response for wait state X'A2A'.
MODE WITH EXPANDED STORAGE
Source: Real storage manager (RSM) DEFINED. THIS STORAGE WILL NOT
BE USED BY THE SYSTEM
Detecting Module: IARMN, IAXMN
Explanation: In z/Architecture mode, the system does
not support expanded storage. However, the storage
IAR013I xxxxxxM STORAGE IS
may be defined as central storage and made available
RECONFIGURABLE
to the system for use.
Explanation: The indicated amount of storage,
xxxxxxM, has been made reconfigurable in response to
However, the expanded storage is not used.
the value specified in the RSU parameter.
Operator Response: None. However, to take full
advantage of the storage available in the configuration,
Operator Response: None. the expanded storage should be configured as central
storage and the system re-IPLed.
Detecting Module: IARMT, IAXMT
Detecting Module: IAXMN
IAR014I MORE CENTRAL STORAGE IS

AVAILABLE TO THE SYSTEM THAN
SUPPORTED. THE MAX OF 128G OF
STORAGE WILL BE USED.
Explanation: The operating system supports a
maximum of 128 gigabytes of central storage, but more
than that is available in the current hardware
configuration. The additional storage will not be used.
However, the excess storage is not used.
Detecting Module: IAXMN
IAR015I THE SYSTEM WAS IPLED IN ESA/390

MODE WITH MORE THAN 2
GIGABYTES OF CENTRAL STORAGE.
Explanation: In ESA/390 mode, the system supports
a maximum of 2 gigabytes of central storage, but more
than that is available in the current hardware
configuration. The additional storage will not be used.
System Action: The ability to reconfigure storage has
been disabled. Any excess storage is not used. The
system continues processing.
Operator Response: None. However, to take full
advantage of the storage available in the configuration,

Chapter 10. ICP Messages
message ICP050D, that this job failed to build the level
ICP050D SHOULD jobname WRITE TO LEVEL
indicated input/output configuration data set (IOCDS).
xxx IOCDS? REPLY ‘YES’, ‘NO’, OR
‘CANCEL’ Operator Response: Notify the system programmer
that the job failed.
Explanation: A job processed the input/output
configuration program (IOCP) with a WRTCDS option System Programmer Response: Review the
other than NO on the PARM parameter of an EXEC messages on the job listing, and take the necessary
statement. actions.
In the message text: Source: Input/output configuration program (IOCP)
jobname Detecting Module: ICPPCNTL
The jobname.
xxx The specified level. ICP057I IOCP JOB jobname SUCCESSFUL.
LEVEL xxx IOCDS REPLACED.
System Action: IOCP issues this message to request
permission from the system operator for the job to write Explanation: A job was processing the input/output
to the specified level input/output configuration data set configuration program (IOCP) with the WRTCDS=
(IOCDS) in the processor controller. If two or more jobs option on the PARM parameter of an EXEC statement.
are allowed to update concurrently the specified level
IOCDS, the outcome could be an IOCDS that is In the message text:
logically inconsistent with the input from any one job. jobname
Using this IOCDS at power-on reset or SYSIML CLEAR The jobname.
could produce undesirable results.
xxx The specified level.
Operator Response: A reply of ‘YES’ allows the job to
continue processing and, if no errors are encountered, System Action: IOCP abnormally ends the job with a
to replace the input/output configuration data in the return code of 4. IOCP issues this message to inform
specified level IOCDS in the processor controller with the system operator, who had previously granted
the input/output configuration data generated by this permission to write the IOCDS in response to message
job. Use the IOCDSM frame to ensure the level IOCDS ICP050D, that this job successfully replaced the level
is not write-protected. indicated input/output configuration data set (IOCDS).
A reply of ‘NO’ allows the job to continue generating Operator Response: Follow the installation
input/output configuration data in storage and to procedures.
produce reports, but does not permit the job to replace Source: Input/output configuration program (IOCP)
the input/output configuration data in the level IOCDS in
the processor controller. Detecting Module: ICPPCNTL
A reply of ‘CANCEL’ ends the job immediately with

system completion code X'222'.
Source: Input/output configuration program (IOCP)
Detecting Module: ICPPCNTL
ICP056I IOCP JOB jobname FAILED. DID NOT

BUILD LEVEL xxx IOCDS.
Explanation: A job processed the input/output
configuration program (IOCP) with the WRTCDS=
option on the PARM parameter of an EXEC statement.
jobname
The jobname.
xxx The specified level.
System Action: IOCP abnormally ends the job with
return code 8. IOCP issues this message to inform the
system operator, who had previously responded to

Chapter 11. ICT Messages
ICT010I CRYPTOGRAPHY SYSTEM MASTER ICT020I synad message from VSAM while
KEY HAS BEEN SET processing CKDS
Explanation: The key generator utility program has Explanation: A physical I/O error occurred while the
successfully set the host master key. If there are any key manager was attempting to read the cryptographic
control statements requesting updates to the secondary key data set (CKDS).
key-encrypting keys, these statements are processed at
this time.
System Programmer Response: See the explanation
Note: The security administrator must ensure that an of the accompanying VSAM physical I/O error message.
authorized person was running the key generator If the volume caused the error, use a backup copy of
utility program. More information about the the CKDS on a different volume. (If you do not want to
requester is recorded in SMF record type 82. re-IPL the system, be ensure that the new copy of the
CKDS uses the same host master key as the old copy.)
System Action: Key generator utility processing
If the device caused the error, move the volume
continues.
containing the CKDS to an alternate device. To change
Source: Programmed Cryptographic Facility (PCF) the volume or device, stop the Programmed
Cryptographic Facility (via IPL or an operator STOP
command) and restart it (via an operator START
ICT011I CRYPTOGRAPHY KEY UPDATE command), specifying an alternate data set name on
STARTED the START command, if required. Rerun the job.
Explanation: The key generator utility program, has To ensure that you have all the messages issued for
successfully updated the cryptographic key data set this problem, specify MSGLEVEL=(1,1) for the job.
(CKDS) to reflect a new, changed, or deleted secondary
key-encrypting key. This message is issued only for the Source: Programmed Cryptographic Facility (PCF)
first update to the CKDS for a secondary key-encrypting
key although the job may contain several update
ICT021I VIOLATION ON RETKEY BY text text is
requests.
USER (userid) GROUP (groupid) JOB (jjj)
STEP (sss)
Note: The security administrator must ensure that an
authorized person was running the key generator Explanation: An unauthorized program has issued the
utility program. More information about the RETKEY SVC requesting that a data-encrypting key
requester is recorded in SMF record type 82. enciphered under a cross key be enciphered again
under the host master key. The RACF (Resource
System Action: Key generator utility processing Access Control Facility) user (userid) and group name
continues. (groupid) are given if they are available. Otherwise, the
Source: Programmed Cryptographic Facility (PCF) job name (jjj) and step name (sss) are supplied. The
REMKEY field in SMF record type 82 contains the label
of the cross key.
ICT012I ERROR IN EXECUTING KEY
GENERATOR UTILITY Note: The security administrator must determine if an
Explanation: The key generator utility program did not attempted security violation occurred. Follow the
complete successfully. A message identifying the nature security procedures established by your
of the problem is routed to the data set defined by the installation.
SYSPRINT DD statement. System Action: Key manager processing ends.
Note: The security administrator must ensure that an Operator Response: Notify the security administrator.
authorized person was running the key generator Source: Programmed Cryptographic Facility (PCF)
utility program. More information about the
requester is recorded in SMF record type 82.
ICT022I xxx ABEND DURING [GENKEY |
System Action: Key generator utility processing ends. RETKEY ] PROCESSING
Application Programmer Response: Respond to the Explanation: An error occurred during processing of
problem identified by the message appearing in the data either the GENKEY or RETKEY function of the key
set defined by the SYSPRINT DD statement. manager. In the message, xxx indicates the system
Source: Programmed Cryptographic Facility (PCF) completion code.

System Action: Key manager processing ends. program, stop the Programmed Cryptographic
Facility, run the utility when there are no
cryptographic sessions or jobs running on the
Application Programmer Response: Notify the system, and restart the facility. Rerun the job that
system programmer. failed.
System Programmer Response: Respond to the

If host master keys are identical, or if the CKDS was not
problem identified by the system completion code.
replaced, use a backup copy of the CKDS. Stop the
To ensure that a dump is produced for this problem, run Programmed Cryptographic Facility and restart it
the job again with a SYSABEND DD statement. specifying the name of the backup CKDS in the START
command. Do not use the original data set again. Rerun
Source: Programmed Cryptographic Facility (PCF) the job that failed.
Source: Programmed Cryptographic Facility (PCF)
ICT023I KEY label HAS INCORRECT PARITY
Explanation: The key-encrypting key identified by ICT024I UNEXPECTED VSAM ERROR CODE rc
label has been read from the cryptographic key data set [FDBK code]
(CKDS) by the key manager and the key manager has
determined that the clear form of the key has bad parity. Explanation: An error occurred when the key
manager attempted to read the cryptographic key data
This situation can occur if there is a problem with the set (CKDS). In the message, rc is the return code that
CKDS. It can also occur when the CKDS used to identifies the error. If rc identifies a logical error, then
initialize the host master key in storage has been FDBK code indicates the specific logical error that has
replaced by a CKDS that contains a different host occurred. For an explanation of the return code and
master key but storage was not reinitialized. Storage is feedback code, see the description of the VSAM macro.
initialized the first time you start the Programmed
Cryptographic Facility or run the key generator utility System Action: Key manager processing ends.
program after an IPL. It is reinitialized when the key
generator utility program is used to change the host
master key (CHGM function). System Programmer Response: See the explanation
of the accompanying VSAM physical I/O error message.
System Action: Key manager processing ends.
Correct the problem and rerun the job.
To ensure that you have all the messages issued for
System Programmer Response: If the CKDS was this problem, specify MSGLEVEL=(1,1) for the job.
replaced, compare the two output listings produced by
running the key generator utility program: one when
setting the host master key in the CKDS that is currently
on the system and the other when setting the host ICT030I CRYPTOGRAPHY INITIALIZATION
master key in the CKDS that was used to initialize UNABLE TO LOCATE name in LPA
storage.
Explanation: The Programmed Cryptographic Facility
If the listings indicate that the host master key values installation process invoked by the operator START
are not the same, do one of the following: command or the key generator utility program was
v Replace the CKDS on the system with a CKDS that unable to locate the routine specified by name in a
contains the same host master key as the one in search of the active link pack area queue and the link
storage. To replace the data set, stop the pack area directory.
Programmed Cryptographic Facility and restart it with System Action: Programmed Cryptographic Facility
an operator START command that specifies the name initialization processing ends.
of the CKDS that contains the correct value for the
host master key. Rerun the job that failed. Operator Response: Notify the system programmer.
v Reinitialize storage so that the value of the host Application Programmer Response: Determine if the
master key in storage matches the value in the GENKEY or RETKEY installation exit routine (module
CKDS currently on the system. To reinitialize storage, ICTMGR90 or ICTMGR95) is properly link edited into
you can re-IPL the system and restart the SYS1.LPALIB. If the module has been replaced since
Programmed Cryptographic Facility with an operator the Programmed Cryptographic Facility was installed,
START command that specifies the name of the check the linkage editor output from the most recent
CKDS currently on the system. Or, you can change. If it has not been replaced, check the output of
reinitialize storage with the key generator utility the install process (SMP or SYSGEN) to see that the
program, using the CHGM function and specifying a module was properly installed. Correct the problem and
host master key value that matches the value on the reissue the operator START command or rerun the key
current CKDS. To run the key generator utility generator utility program.

ICT033I LOAD FAILED FOR CRYPTOGRAPHY
this problem, specify MSGLEVEL=(1,1) for the job.
INSTALLATION OPTIONS MODULE
initialization process invoked by the operator START
ICT031I INVALID CRYPTOGRAPHY USER SVC command or the key generator utility program was
NUMBER SPECIFIED unable to load the installation options module,
ICTOPTNS.
initialization process invoked by the operator START System Action: Programmed Cryptographic Facility
command or the key generator utility program has initialization processing ends.
determined that the options module, ICTOPTNS,
Application Programmer Response: Check the
contains a user SVC number that is not valid.
output of the install process (SMP) to verify that the
System Action: Programmed Cryptographic Facility installation options module was properly installed in
initialization processing ends. SYS1.LINKLIB. Correct the problem and reissue the
operator START command or rerun the key generator
Operator Response: Notify the system programmer. utility program.
System Programmer Response: Update the To ensure that you have all the messages issued for
installation options module, ICTOPTNS, to reflect a valid this problem, specify MSGLEVEL=(1,1) for the job.
user SVC number in the range of 200 through 255. See
the Programmed Cryptographic Facility Program Source: Programmed Cryptographic Facility (PCF)
Directory for information on how to modify the options
module. When the update is complete, reissue the
ICT034I CRYPTOGRAPHY INITIALIZATION
UNABLE TO ESTABLISH ESTAE CODE
utility program.
xxx
Source: Programmed Cryptographic Facility (PCF) command or the key generator utility program was
unable to establish an ESTAE recovery environment.
The code from ESTAE processing is specified by xxx.
ICT032I CRYPTOGRAPHY INITIALIZATION
UNABLE TO OPEN ddname System Action: Programmed Cryptographic Facility
initialization processing ends.
initialization process invoked by the operator START Operator Response: If the code is 14, reissue the
command or the key generator utility program was operator START command. For all other codes, contact
unable to open the data set identified by ddname. For a your system programmer. When the problem is
VSAM data set, this message is accompanied by a corrected, reissue the START command.
VSAM error message that further identifies the problem.
Application Programmer Response: If the code is
System Action: Programmed Cryptographic Facility 14, rerun the key generator utility program. For all other
initialization processing ends. codes, contact your system programmer. When the
problem is corrected, or rerun the utility program.
System Programmer Response: Verify that the reporting data bases for a fix for the problem. If no fix
specified ddname has been included in the JCL for the exists, contact the IBM Support Center.
START procedure or in the JCL for the key generator
utility program. For a VSAM data set, see the To ensure that you have all the messages issued for
accompanying VSAM error message for additional this problem, specify MSGLEVEL=(1,1) for the job.
information. Correct the problem and reissue the
utility program.
ICT035I synad message from VSAM while
processing CKDS
Explanation: A physical I/O error occurred during
Programmed Cryptographic Facility initialization
processing while reading the host master key from the
cryptographic key data set (CKDS).
System Action: Programmed Cryptographic Facility
Chapter 11. ICT Messages 235

Operator Response: Notify the system programmer. Source: Programmed Cryptographic Facility (PCF)
of the accompanying VSAM physical I/O error message. ICT041I CRYPTOGRAPHY FACILITY HAS BEEN
Correct the problem and rerun the job. If the volume ACTIVATED
caused the error, use a backup copy of the CKDS on a
Explanation: An operator START command has
different volume. (If you do not want to re-IPL the
successfully activated the Programmed Cryptographic
system, ensure that the new copy of the CKDS uses the
Facility. All functions of the facility are currently
same host master key as the old copy.) If the device
operational.
caused the error, move the volume containing the
CKDS to an alternate device. To change the volume or System Action: The Programmed Cryptographic
device, stop the Programmed Cryptographic Facility, if it Facility is active.
is active (via IPL or an operator STOP command). Make
the required change and then reissue the START Source: Programmed Cryptographic Facility (PCF)
command or rerun the key generator utility program. If
applicable, specify the alternate data set name. ICT042I START CRYPTO TERMINATED
To ensure that you have all the messages issued for Explanation: The START command procedure ended
this problem, specify MSGLEVEL=(1,1) for the job. abnormally when attempting to start the Programmed
Source: Programmed Cryptographic Facility (PCF) Cryptographic Facility. Another message that explains
the nature of the error precedes this message.
ICT036I UNEXPECTED VSAM ERROR System Action: START command processing ends.
PROCESSING CKDS CODE rc [FDBK The Programmed Cryptographic Facility is not active.
code] Operator Response: Notify the system programmer.
Explanation: An error occurred during Programmed System Programmer Response: Respond to the
Cryptographic Facility initialization processing while problem described by the preceding message.
reading the host master key from the cryptographic key
data set (CKDS). In the message, rc is the return code Source: Programmed Cryptographic Facility (PCF)
that identifies the error. If rc identifies a logical error,
then FDBK code indicates the specific logical error that ICT043I UNABLE TO OPEN SYSCKDS
has occurred.
Explanation: The START command procedure used to
System Action: Programmed Cryptographic Facility start the Programmed Cryptographic Facility was not
initialization processing ends. able to open the cryptographic key data set (CKDS)
Operator Response: Notify the system programmer. defined by the SYSCKDS DD statement. This message
is accompanied by a VSAM error message that further
System Programmer Response: For an explanation identifies the problem.
of the return code and feedback code, see the
description of the VSAM macro. Correct the problem System Action: START command processing ends.
and reissue the operator START command or rerun the Operator Response: Notify the system programmer.
key generator utility program.
System Programmer Response: Verify that a DD
To ensure that you have all the messages issued for statement has been included in the START procedure
this problem, specify MSGLEVEL=(1,1) for the job. for the CKDS with the ddname SYSCKDS. Check the
Source: Programmed Cryptographic Facility (PCF) accompanying VSAM error message for additional
information. Correct the problem and reissue the
operator START command.
ICT040I CRYPTOGRAPHY FACILITY HAS BEEN
DEACTIVATED: REQUESTS FOR NEW To ensure that you have all the messages issued for
CRYPTOGRAPHY SESSIONS WILL BE this problem, specify MSGLEVEL=(1,1) for the job.
REJECTED Source: Programmed Cryptographic Facility (PCF)
Explanation: An operator STOP command has
successfully deactivated the Programmed Cryptographic ICT044I START CRYPTO UNABLE TO
Facility. All current sessions or jobs using the EMK or ESTABLISH ESTAE CODE xxx
CIPHER functions of the facility can continue
processing. All new sessions or jobs requesting the Explanation: The START procedure used to start the
facility (using a GENKEY or RETKEY macro instruction) Programmed Cryptographic Facility was unable to
will be rejected. establish an ESTAE recovery environment. The return
code from ESTAE processing is specified by xxx.
System Action: START command processing ends.

Operator Response: If the code is 14, reissue the Application Programmer Response: Supply a new
operator START command. When the problem is clear key value on the control statement or remove the
corrected, reissue the START command. For all other KEY parameter completely to let the key generator
codes, contact your system programmer. utility program generate a clear key value. See “Security
Highlights and Requirements” in OS/VS1 and OS/VS2
MVS Programmed Cryptographic Facility: Installation
Reference Manual for a description of weak key values.
exists, contact the IBM Support Center.
Rerun the utility program, specifying the CHGK function
To ensure that you have all the messages issued for on the EXEC statement and providing the corrected
this problem, specify MSGLEVEL=(1,1) for the job. control statement as input.
Source: Programmed Cryptographic Facility (PCF) Source: Programmed Cryptographic Facility (PCF)
ICT045I START CRYPTO OR KEY GENERATOR ICT1002 INVALID VERB

ALREADY IN PROGRESS
Explanation: A verb that was specified on a control
Explanation: An operator START command was statement for the key generator utility program was not
issued to start the Programmed Cryptographic Facility valid. The control statement containing the error
but the facility has already been started, the START precedes this message.
command procedure is currently running, or the key
System Action: Processing ends for this control
generator utility program is running.
statement. Processing continues for any other control
System Action: The START command is ignored. statements.
Operator Response: If a START command was Application Programmer Response: Correct the verb
issued when the Programmed Cryptographic Facility is on the control statement. The valid verbs are LOCAL,
already active or the START command procedure is REMOTE, CROSS, EXTRA-LOCAL, EXTRA-REMOTE,
already running, an operator STOP command must be EXTRA-CROSS, and INSTDAT. The verb must be
issued before another START command can be preceded and followed by a blank. Rerun the key
accepted. If the key generator utility program is currently generator utility program, specifying the CHGK function
running, reissue the START command when the utility on the EXEC statement and providing the corrected
program ends. control statement as input.
ICT046I STOP CRYPTO IN PROGRESS ICT1003 SYNTAX ERROR IN KEY
Explanation: An operator STOP for the Programmed Explanation: The clear key value specified on a
Cryptographic Facility has been accepted. STOP LOCAL, REMOTE, or CROSS control statement for the
command processing waits until all outstanding requests key generator utility program was not valid. The control
to access the cryptographic key data set (CKDS) are statement containing the error precedes this message.
finished before closing the CKDS and stopping the
Programmed Cryptographic Facility task. (Requests to
access the CKDS are made by the GENKEY or the
statements.
RETKEY macro instructions.) Once the STOP command
is accepted, all new sessions or jobs requesting the Application Programmer Response: Supply a valid
Programmed Cryptographic Facility are rejected. clear key value on the control statement. A valid value
consists of 16 hexadecimal digits. (Valid hexadecimal
System Action: STOP command processing waits
digits are 0 through 9 and A through F.) Rerun the key
until the CKDS is not being used.
generator utility program, specifying the CHGK function
Source: Programmed Cryptographic Facility (PCF) on the EXEC statement and providing the corrected
control statement as input.
ICT1001 WEAK KEY SPECIFIED Source: Programmed Cryptographic Facility (PCF)
Explanation: A weak clear key value was specified on

a LOCAL, REMOTE, or CROSS control statement for ICT1004 SYNTAX ERROR IN LABEL
the key generator utility program. The control statement
Explanation: A label specified on a LOCAL, REMOTE,
containing the weak key precedes this message.
or CROSS control statement for the key generator utility
System Action: Processing ends for this control program was not valid. The control statement containing
statement. Processing continues for any other control the error precedes this message.
statements.

statement. Processing continues for any other control requested on the control statement. The sum of these
statements. two values must not exceed 9999.
Application Programmer Response: Supply a valid Rerun the key generator utility program, specifying the
label on the control statement. A valid label consists of 1 CHGK function on the EXEC statement and providing
to 8 alphameric characters. Valid alphameric characters the corrected control statement.
are A through Z and 0 through 9. Rerun the key
on the EXEC statement and providing the corrected
control statement as input. ICT1007 STATEMENT REJECTED BY
INSTALLATION EXIT
Explanation: A control statement was rejected by the
key generator utility program installation exit routine.
ICT1005 INVALID OR REDUNDANT KEYWORD
The rejected control statement precedes this message.
SPECIFIED
Explanation: A keyword parameter specified on a
LOCAL, REMOTE, or CROSS control statement for the
statements.
key generator utility program was redundant or not
valid. The control statement containing the error Application Programmer Response: Follow local
precedes this message. procedures for errors detected by the key generator
utility program installation exit routine. Correct the error
and, if necessary, rerun the utility program. Specify the
CHGK function on the EXEC statement and provide the
statements.
corrected control statement.
keyword parameter or remove the redundant keyword
parameter on the control statement. Rerun the key
generator utility program, specifying the CHGK function ICT1008 REQUIRED PARAMETER
on the EXEC statement and providing the corrected INFORMATION MISSING
control statement.
Explanation: The key generator utility program found
Source: Programmed Cryptographic Facility (PCF) that the value for the SETM, CHGM, or SEED
parameter on the EXEC statement is missing.
ICT1006 INVALID VALUE SPECIFIED ON EXTRA System Action: Key generator utility processing ends.
STATEMENT
Application Programmer Response: Supply the
Explanation: One of the following conditions was missing value in the PARM field of the EXEC statement
encountered on an EXTRA-LOCAL, EXTRA-CROSS, or and rerun the key generator utility program.
EXTRA-REMOTE control statement for the key
generator utility program: To ensure that you have all the messages issued for
v The first through fourth characters of the value for
label-base were not alphameric. Source: Programmed Cryptographic Facility (PCF)
v The fifth through eighth characters of the value for
label-base were not numeric. ICT1009 DUPLICATE LABEL; KEY NOT ADDED
v An incorrect number of additional keys was
Explanation: A user requested the key generator
requested.
utility program to add a label and its associated
secondary key-encrypting key to the cryptographic key
The control statement containing the error precedes this data set (CKDS), but the specified label was already
message. defined in the CKDS. The rejected control statement
System Action: Processing ends for this control precedes this message.
statement. Processing continues for any other control System Action: Processing ends for this control
statements. statement. Processing continues for any other control
Application Programmer Response: If the statements.
alphameric portion of the label-base is incorrect, supply Application Programmer Response: Assign a unique
a valid value on the control statement. A valid value label to the key and rerun the key generator utility
consists of 4 alphameric characters. Valid alphameric program, specifying the CHGK function on the EXEC
characters are A through Z and 0 through 9. statement and providing the corrected control statement.
Otherwise, correct the numerical portion of the Source: Programmed Cryptographic Facility (PCF)
label-base and/or the number of additional keys

System Action: Key generator utility processing ends.
ICT1010 LABEL NOT FOUND; NOT
PROCESSED Application Programmer Response: Follow local
procedures.
Explanation: A user requested the key generator
utility program to update a secondary key-encrypting Source: Programmed Cryptographic Facility (PCF)
key or to delete a label and its associated key from the
cryptographic key data set (CKDS), but the specified Detecting Module: ICTMKG00, ICTMKG01
label was not defined in the CKDS. The rejected control
statement precedes this message. ICT1013 PROCESSING ENDED DUE TO ESTAE
System Action: Processing ends for this control OR STAE RETURN CODE xxx
statement. Processing continues for any other control Explanation: The key generator utility program
statements. attempted to use the ESTAE system service, but the
Application Programmer Response: Supply the error code xxx was returned.
correct label and rerun the key generator utility program, System Action: Key generator utility processing ends.
specifying the CHGK function on the EXEC statement. No control statements are processed.
Source: Programmed Cryptographic Facility (PCF) Application Programmer Response: If the code is
14, run the key generator utility program again. For all
ICT1011 synad I/O error message from VSAM other codes, contact your system programmer. When
the problem is corrected, rerun the utility program.
Explanation: A physical I/O error occurred when the
key generator utility program attempted to access the System Programmer Response: Search problem
SYSCKDS or SYSNCKDS data set. reporting data bases for a fix for the problem. If no fix
of the accompanying VSAM physical I/O error message. Detecting Module: ICTMKG00, ICTMKG01
If the volume caused the error, use a backup copy of
the CKDS on a different volume. (If you do not want to ICT1014 SYSIN DATA SET EMPTY; NO
re-IPL the system, ensure that the new copy of the PROCESSING OCCURRED
CKDS uses the same host master key as the old copy.)
If the device caused the error, move the volume Explanation: The CHGK function of the key generator
containing the CKDS to an alternate device. utility program was requested but no control statements
could be found.
Rerun the key generator utility program as follows. If the
SETM or CHGM function was requested and the host System Action: Key generator utility processing ends.
master key was not set (message ICT010I was not Application Programmer Response: Add the desired
issued), rerun the entire job. Otherwise, use this listing control statements to the SYSIN data set and rerun the
to determine which control statements were processed key generator utility program.
successfully. Then rerun the utility program using the
CHGK function to process the remaining control Source: Programmed Cryptographic Facility (PCF)
statements. Detecting Module: ICTMKG01
this problem, specify MSGLEVEL=(1,1) for the job. ICT1015 UNABLE TO [OPEN | CLOSE ] ddname
Source: Programmed Cryptographic Facility (PCF) [CODE rc]
Detecting Module: ICTMKG00, ICTMKG01 Explanation: The key generator utility program was
unable to open or close the data set defined by the DD
statement identified by ddname.
ICT1012 PROCESSING TERMINATES DUE TO
INSTALLATION EXIT REQUEST If the data set is a VSAM data set (SYSCKDS or
SYSNCKDS), the VSAM return code rc is included to
Explanation: The key generator utility program stops help identify the error.
processing at the request of the installation exit routine.
If the problem occurred while the utility program was System Action: Key generator utility processing ends.
processing a change to the host master key, the Application Programmer Response: If the problem
contents of the PARM field of the EXEC statement occurred while trying to open a data set, check the JCL.
precede this message. If the problem occurred while the Be sure the required DD statements were included, that
utility program was processing a SYSIN control they have the correct ddnames, and that they define the
statement, the control statement precedes this correct data sets. The following ddnames are valid:
message. SYSCKDS, SYSNCKDS, SYSIN, and SYSMKDS.

An open failure can also occur if the SYSCKDS or For information on defining and reorganizing the CKDS,
SYSNCKDS data set was defined without the proper see “Defining Storage for the CKDS and MKDS” in
parameters. See “Defining Storage for the CKDS and OS/VS1 and OS/VS2 MVS Programmed Cryptographic
the MKDS” in OS/VS1 and OS/VS2 MVS Programmed Facility: Installation Reference Manual. The commands
Cryptographic Facility: Installation Reference Manual for needed to define, reorganize and copy the data set are
instructions on using the access method services described in your VSAM catalog administration books.
DEFINE CLUSTER command.
Notify the security administrator.
Correct the problem and rerun the key generator utility
program as follows. If the SETM or CHGM function was
requested and the host master key was not set, To ensure that you have all the messages issued for
(message ICT010I was not issued), rerun the entire job. this problem, specify MSGLEVEL=(1,1) for the job.
Otherwise, use this listing to determine which control Source: Programmed Cryptographic Facility (PCF)
statements were processed successfully. Then rerun the
utility program using the CHGK function to process the Detecting Module: ICTMKG00, ICTMKG01
remaining control statements.
To ensure that you have all the messages issued for ICT1017 CRYPTOGRAPHY STARTED; INVALID
this problem, specify MSGLEVEL=(1,1) for the job. KEY GENERATOR REQUEST
Source: Programmed Cryptographic Facility (PCF) Explanation: The key generator utility program was
unable to run because the Programmed Cryptographic
Detecting Module: ICTMKG00, ICTMKG01 Facility was active.
ICT1016 INSUFFICIENT SPACE ON CKDS
Application Programmer Response: When the
Explanation: The key generator utility program could Programmed Cryptographic Facility is stopped and there
not complete a request to update the cryptographic key are no cryptographic sessions or jobs running in the
data set (CKDS) because there is insufficient space on system, rerun the key generator utility program to
the target data set. The target data set is defined by the change the host master key. Restart the Programmed
SYSNCKDS DD statement if the CHGK function was Cryptographic Facility by entering an operator START
requested. command.
If the problem occurred while the utility program was Source: Programmed Cryptographic Facility (PCF)
processing a change to the host master key, the
contents of the PARM field of the EXEC statement Detecting Module: ICTMKG00
precede this message. If the problem occurred while the
utility program was processing a SYSIN control ICT1018 KEY GENERATION NOT ALLOWED -
statement, the control statement precedes this text
message.
Explanation: In the message, text is one of the
System Action: Key generator utility processing ends. following:
Application Programmer Response: If the SETM or
CHGM function was requested and the host system TOD CLOCK ERROR
master key was not set (the contents of the PARM field SEED NOT SUPPLIED
precede this message), define a larger target data set
for the CKDS and rerun the job. Otherwise, the key An error was encountered when the key generator utility
generator utility program failed while processing a program attempted to read the time-of-day (TOD) clock,
SYSIN control statement and one of the following must the TOD clock was inoperative, or a seed value was not
be done: supplied on the EXEC statement. Processing continues;
v Reorganize the target CKDS to force more efficient however, no keys can be generated.
space utilization. System Action: Key generator utility processing
v Define a larger data set for use as the new target continues.
CKDS and copy the contents of the original target
Application Programmer Response: If the problem
CKDS to the larger data set.
involves the TOD clock, contact your service
representative. If a seed value was not supplied, ignore
Then, use this listing to determine which control this message unless message ICT1025 also appears. If
statements were processed successfully and rerun the message ICT1025 appears, see the description of
key generator utility program using the CHGK option to message ICT1025.
process the remaining control statements.
Detecting Module: ICTMKG00, ICTMKG01

CURRENT MASTER KEY
ICT1019 CRYPTOGRAPHY SYSTEM MASTER
NEW MASTER KEY
KEY HAS BEEN SET
NEW MASTER KEY COMPLEMENT SEED
Explanation: The key generator utility program has
successfully set the host master key. If there are any An incorrect value was specified for the SETM, CHGM,
control statements requesting updates to the secondary or SEED parameter in the PARM field of the EXEC
key-encrypting keys, they are processed at this time. statement for the key generator utility program.
System Action: Key generator utility processing System Action: Key generator utility processing ends.
continues.
Source: Programmed Cryptographic Facility (PCF) value in the PARM field of the EXEC statement. A valid
value consists of 16 hexadecimal digits. (Valid
Detecting Module: ICTMKG00
hexadecimal digits are 0 through 9 and A through F.)
Rerun the key generator utility program.
ICT1020 INVALID KEYWORD SPECIFIED IN
PARM FIELD
Explanation: A keyword parameter specified in the
PARM field of the EXEC statement for the key
generator utility program was not valid. Detecting Module: ICTMKG00
ICT1023 INVALID RETURN CODE FROM
Application Programmer Response: Supply a valid
INSTALLATION EXIT; PROCESSING
keyword parameter in the PARM field. The valid
TERMINATES
keyword parameters are SETM, CHGM, CHGK, and
SEED. Rerun the key generator utility program. Explanation: A return code provided by the key
generator utility program installation exit was not valid. If
the problem occurred while the utility program was
Source: Programmed Cryptographic Facility (PCF) contents of the PARM field of the EXEC statement
utility program was processing a SYSIN control
statement, the control statement precedes this
ICT1021 WEAK SYSTEM MASTER KEY message.
SPECIFIED
Explanation: A weak value for the new host master
key was specified in the PARM field of the EXEC
installation exit routine to determine if there are any
statement for the key generator utility program.
problems in the module and make any necessary
System Action: Key generator utility processing ends. corrections. Link edit the key generator utility program
with the corrected exit routine. (See “Adding
Application Programmer Response: Supply a new User-Written Exit Routines” in OS/VS1 and OS/VS2
host master key value and its complement in the PARM MVS Programmed Cryptographic Facility: Installation
field of the EXEC statement. See “Security Highlights Reference Manual.) Rerun the key generator utility
and Requirements” in OS/VS1 and OS/VS2 MVS program as follows. Rerun the entire job if the SETM or
Programmed Cryptographic Facility: Installation CHGM function was requested and the host master key
Reference Manual for a description of weak key values. was not set (the contents of the PARM field precede
Rerun the key generator utility program. this message).
To ensure that you have all the messages issued for Otherwise, use this listing to determine which control
this problem, specify MSGLEVEL=(1,1) for the job. statements were processed successfully. Then rerun the
Source: Programmed Cryptographic Facility (PCF) utility program using the CHGK function to process the
ICT1022 INVALID SYNTAX FOR text
Explanation: In the message, text is one of the
following: Detecting Module: ICTMKG00, ICTMKG01

to the cryptographic key data set (CKDS). In the
ICT1024 REQUIRED OPERAND[S] MISSING;
message, rc is the return code that identifies the error. If
STATEMENT IGNORED
rc identifies a logical error, then FDBK code indicates
Explanation: While scanning a SYSIN control the specific logical error that has occurred.
statement, the key generator utility program could not
find one or more required parameters. LOCAL,
REMOTE, and CROSS control statements require a System Programmer Response: For an explanation
label. EXTRA-LOCAL, EXTRA-REMOTE, and of the return code and feedback code, see the
EXTRA-CROSS control statements require a number description of the VSAM macro. Correct the problem
and a label-base. The REASGN control statement and rerun the utility program as follows. If the SETM or
requires an existing label and a new label. The control CHGM function was requested and the host master key
statement containing the error precedes this message. was not set (message ICT010I was not issued), rerun
the entire job. Otherwise, use this listing to determine
which control statements were processed successfully.
Then rerun the utility program using the CHGK function
statements.
to process the remaining control statements.
Notify the security administrator.
control statement. Rerun the key generator utility
program, specifying the CHGK function on the EXEC To ensure that you have all the messages issued for
statement and providing the corrected control statement. this problem, specify MSGLEVEL=(1,1) for the job.
Detecting Module: ICTMKG01 Detecting Module: ICTMKG00, ICTMKG01
ICT1025 REQUIRED INPUTS FOR KEY ICT1027 SYSTEM MASTER KEY PREVIOUSLY
GENERATION NOT AVAILABLE SET; INVALID KEY GENERATOR
REQUEST
Explanation: The key generator utility program
attempted to generate a key for a control statement and Explanation: An attempt was made to use the SETM
either a problem occurred with the time-of-day (TOD) function of the key generator utility program to set host
clock or a valid seed value was not supplied on the master key, but the host master key has already been
EXEC statement. Message ICT1018, which identifies set. Any change to it must be requested using the
the specific problem, and the control statement being CHGM function of the utility program.
processed when the problem occurred, precede this
message. System Action: Key generator utility processing ends.
System Action: Processing ends for this control Application Programmer Response: If you want to
statement. Processing continues for any other control change the host master key and secondary
statements. key-encrypting keys, rerun the key generator utility
program specifying CHGM on the EXEC statement. If
Application Programmer Response: Respond as you want to change secondary key-encrypting keys
follows: only, rerun the utility program specifying CHGK on the
v If message ICT1018 stated that there is a problem EXEC statement.
involving the TOD clock, contact your service
representative. Source: Programmed Cryptographic Facility (PCF)
v If message ICT1018 stated that a seed value was Detecting Module: ICTMKG00
supplied, add a seed value to the EXEC statement.
Rerun the key generator utility program specifying the ICT1028 SYSTEM MASTER KEY
CHGK function on the EXEC statement and providing Explanation: When attempting to change the host
the control statement that was being processed when master key, the key generator utility program
the problem occurred. encountered an incorrect current host master key value
Source: Programmed Cryptographic Facility (PCF) in the PARM field of the EXEC statement.
Detecting Module: ICTMKG01 System Action: Key generator utility processing ends.
ICT1026 UNEXPECTED VSAM ERROR CODE rc value of the current host master key in the EXEC
[FDBK code] statement and rerun the key generator utility program.
Explanation: An error occurred when the key To ensure that you have all the messages issued for
generator utility program attempted to read from or write this problem, specify MSGLEVEL=(1,1) for the job.

ICT1031 INVALID DELIMITER IN PARM FIELD
Explanation: While scanning the PARM field of the
EXEC statement, the key generator utility program did
ICT1029 INVALID PARITY IN NEW MASTER KEY not find an expected delimiter or encountered an
unexpected delimiter.
Explanation: A value specified for the new host
master key in the PARM field of the EXEC statement for System Action: Key generator utility processing ends.
the key generator utility program was not valid.
Application Programmer Response: The valid
System Action: Key generator utility processing ends. delimiters are comma, right and left parentheses, and
blank. Correct the error and rerun the key generator
Application Programmer Response: Supply a valid utility program.
value for the new host master key and the complement
of the value in the EXEC statement. The new key value To ensure that you have all the messages issued for
must contain odd parity in each byte. Rerun the key this problem, specify MSGLEVEL=(1,1) for the job.
generator utility program.
ICT1032 CRYPTOGRAPHY EMK FUNCTION
Detecting Module: ICTMKG00 FAILED - CODE xx
Explanation: An error occurred during the processing
ICT1030 INVALID SMF DATA LENGTH FROM of an EMK macro instruction issued by the key
INSTALLATION EXIT; PROCESSING generator utility program. In the message text, xx is the
TERMINATES error return code from the EMK macro. The values of xx
and their explanations are as follows:
Explanation: The key generator installation exit
routine returned the SMF buffer with a value greater Code Explanation
than 64 in the length field.
4 The Programmed Cryptographic Facility has
System Action: The key generator utility program not been initialized.
does not include the installation-defined data in the SMF
8 The operation requested was not valid; the
record. The program writes the SMF record to the SMF
macro was not EMK.
data set and stops processing.
12 An ESTAE recovery environment could not be
established.
installation exit routine to determine if there are any
problems in the module and make any necessary 32 The address of the clear key-encrypting key or
corrections. Link edit the key generator utility program the address of the enciphered key-encrypting
with the corrected exit routine. (See “Adding key was specified as zero.
User-Written Exit Routines” in OS/VS1 and OS/VS2
MVS Programmed Cryptographic Facility: Installation
Reference Manual.) Rerun the key generator utility Application Programmer Response: Contact your
program as follows. If the SETM or CHGM function was programming support personnel. When the problem has
requested and the host master key was not set been corrected, rerun the key generator utility program
(message ICT010I was not issued), rerun the entire job. as follows. If the SETM or CHGM function was
Otherwise, use this listing to determine which control requested and the host master key was not set,
statements were processed successfully. Then rerun the (message ICT010I was not issued), rerun the entire job.
utility program using the CHGK function to process the Otherwise, use this listing to determine which control
remaining control statements. Notify the security statements were processed successfully. Then rerun the
administrator. utility program using the CHGK function to process the
this problem, specify MSGLEVEL=(1,1) for the job. To ensure that you have all the messages issued for

ICT1033 CRYPTOGRAPHY CIPHER FUNCTION
established.
FAILED - CODE xx
24 Bad parity was detected in the local, remote, or
Explanation: An error occurred during the processing
cross key.
of a CIPHER macro instruction issued by the key
generator utility program. In the message text, xx is the 28 The program requesting the key translation
error return code from the macro. The values of xx and function is not APF-authorized or in supervisor
their explanations are as follows: state or running under storage protect key 0
through 7.
Code Explanation
32 The address of the enciphered data-encrypting
key or the address of the enciphered
not been initialized. The data could not be
key-encrypting key was specified as zero.
enciphered or deciphered.
8 The operation requested was not valid; the
macro was not CIPHER. Application Programmer Response: Contact your
programming support personnel. When the problem has
been corrected, rerun the key generator utility program
established.
as follows. If the SETM or CHGM function was
16 The length of the data to be enciphered or requested and the host master key was not set
deciphered was specified as zero or as a (message ICT010I was not issued), rerun the entire job.
negative number. Otherwise, use this listing to determine which control
20 The BRANCH=YES parameter was specified,
utility program using the CHGK function to process the
but the program issuing the macro is not
running in supervisor state.
32 The address of the clear data or the
enciphered data was specified as zero.
Application Programmer Response: Contact your
system programmer. When the problem has been
corrected, rerun the key generator utility program as ICT1035 synad message for non-VSAM
follows. If the SETM or CHGM function was requested
Explanation: An I/O error occurred while the key
and the host master key was not set (message ICT010I
generator utility program was processing the non-VSAM
was not issued), rerun the entire job. Otherwise, use
data set defined by the SYSMKDS or SYSIN DD
this listing to determine which control statements were
statement.
processed successfully. Then rerun the utility program
using the CHGK function to process the remaining System Action: Key generator utility processing ends.
control statements.
Application Programmer Response: For the format
To ensure that you have all the messages issued for and explanation of the message, see the description of
this problem, specify MSGLEVEL=(1,1) for the job. the SYNADAF macro instruction in your data
administration macro instruction book. Correct the
problem and rerun the key generator utility program as
Detecting Module: ICTMKG00 follows. If the SETM or CHGM function was requested
and the host master key was not set (message ICT010I
was not issued), rerun the entire job. Otherwise, use
ICT1034 CRYPTOGRAPHY KEY TRANSLATION
this listing to determine which control statements were
FAILED - CODE xx
processed successfully. Then rerun the utility program
Explanation: An error has occurred during key using the CHGK function to process the remaining
translation processing. The translation was requested by control statements. Notify the security administrator.
the key generator utility program. In the message text,
xx is the error return code from the key translation
process. The values of xx and their explanations are as
follows: Source: Programmed Cryptographic Facility (PCF)
Code Explanation Detecting Module: ICTMKG00, ICTMKG01
not been initialized.
8 The operation requested was not valid.

ICT1036 CKDS ENTRY SUCCESSFULLY
DELETED
successfully deleted an entry from the cryptographic key
data set (CKDS). The control statement that was
processed precedes this message.
ICT1037 INVALID VALUE FOR NEW SYSTEM

MASTER KEY COMPLEMENT
Explanation: An incorrect new host master key or its
complement value was specified on the PARM field of
the EXEC statement for the key generator utility
program.
Application Programmer Response: Check both the
new host master key and its complement value to
determine which one was not correct. Supply the correct
new host master key value or its complement value on
the EXEC statement and rerun the key generator utility
program.

Chapter 12. ICU Messages
Source: Cryptographic Unit Support Program (CUSP)
ICU010I CRYPTOGRAPHY SYSTEM MASTER
KEY HAS BEEN SET
ICU013I KEY GENERATOR UTILITY jobname
STARTED AT time
successfully set the host master key. If there are any
control statements requesting updates to the secondary Explanation: The key generator utility job, indicated
key-encrypting keys, these statements are processed at by jobname, began running at the time shown in the
this time. message.
Note: The security administrator must ensure that an Note: The security administrator must ensure that an
authorized person was running the key generator authorized person was running the key generator
utility program. More information about the utility program. More information about the
requester is recorded in SMF record type 82. requester is in SMF record type 82.
System Action: Key generator utility processing System Action: Key generator utility processing
continues. continues.
Source: Cryptographic Unit Support Program (CUSP) Source: Cryptographic Unit Support Program (CUSP)
ICU011I CRYPTOGRAPHY KEY UPDATE ICU014I KEY GENERATOR UTILITY jobname

STARTED IN KEY GENERATOR ENDED AT time
UTILITY job name
Explanation: The key generator utility job, indicated
Explanation: The key generator utility program, by jobname, completed processing at the time shown in
identified by jobname, has successfully updated the the message.
cryptographic key data set (CKDS) to reflect a new,
changed, or deleted secondary key-encrypting key. This Note: The security administrator must ensure that an
message is issued only for the first update to the CKDS authorized person was running the key generator
for a secondary key-encrypting key although the job utility program. More information about the
may contain several update requests. requester is in SMF record type 82.
Note: The security administrator must ensure that an System Action: Key generator utility processing ends.
authorized person was running the key generator Application Programmer Response: Respond to any
utility program. More information about the error messages that were issued.
requester is recorded in SMF record type 82.
continues.
ICU020I synad message from VSAM while
Source: Cryptographic Unit Support Program (CUSP) processing CKDS
Explanation: A physical I/O error occurred while the
ICU012I ERROR IN EXECUTING KEY key manager was attempting to read the cryptographic
GENERATOR UTILITY jobname key data set (CKDS).
Explanation: The key generator utility program, Operator Response: Notify the system programmer.
identified by jobname, did not complete successfully. A
message identifying the nature of the problem is routed System Programmer Response: See the explanation
to the data set defined by the SYSPRINT DD statement. of the accompanying VSAM physical I/O error message
in your VSAM macro instruction book. If the volume
Note: The security administrator must ensure that an caused the error, use a backup copy of the CKDS on a
authorized person was running the key generator different volume. (If you do not want to re-IPL the
utility program. More information about the system, ensure that the new copy of the CKDS uses the
requester is recorded in SMF record type 82. same host master key as the old copy.) If the device
System Action: Key generator utility processing ends. CKDS to an alternate device. To change the volume or
device, stop the Cryptographic Unit Support (via IPL or
Application Programmer Response: Respond to the
an operator STOP command) and restart it (via an
problem identified by the message appearing in the data
operator START command), specifying an alternate data
set defined by the SYSPRINT DD statement.

set name on the START command, if required. Rerun Operator Response: Notify the system programmer.
the job.
System Programmer Response: For an explanation
To ensure that you have all the messages issued for of the return code and feedback code, see the
this problem, specify MSGLEVEL=(1,1) for the job. description of the VSAM macro. Correct the problem
and rerun the job.
ICU021I VIOLATION ON RETKEY BY text
Explanation: text is
USER (userid) GROUP (groupid) ICU025I ENTRY xxxxxxxx FAILS

JOB (jobname) STEP (stepname) AUTHENTICATION TEST
Explanation: The key manager has determined that
An unauthorized program has issued the RETKEY SVC the secondary key-encrypting key, stored in the
requesting that a data-encrypting key enciphered under cryptographic key data set (CKDS) entry indicated by
a cross key be enciphered again under the host master xxxxxxxx, has been changed since it was stored in the
key. The RACF (Resource Access Control Facility) user CKDS. The key authentication procedure, using the test
(userid) and group name (groupid) are given if they are pattern in the CKDS entry, detected the problem.
available. Otherwise, the job name (jobname) and step
name (stepname) are supplied. The REMKEY field in System Action: Processing stops for this request.
SMF record type 82 contains the label of the cross key.
Note: The security administrator must determine if an System Programmer Response: Ensure that the
attempted security violation occurred. Follow the CKDS and MKDS that are mounted are the current
security procedures established by your versions of the data sets. Rerun the job.
installation.
Operator Response: Notify the security administrator. ICU026I INTERNAL CKDS LOOKUP FAILED
AND DISABLED. ERROR CODE xx yy
Explanation: A failure occurred in the cryptographic
key table (CKT). xx and yy are the return and reason
ICU022I xxx ABEND DURING [GENKEY | codes for the error. An error was encountered when
RETKEY ] PROCESSING ICUMKM18 attempted to locate a CKDS record from the
Explanation: An error occurred during processing of in-core cryptographic key table (CKT).
either the GENKEY or RETKEY function of the key System Action: Access to the cryptographic key data
manager. In the message, xxx indicates the system set (CKDS) resumes.
completion code.
Operator Response: Respond according to the
System Action: Key manager processing ends. specific return and reason codes.
Operator Response: Notify the system programmer. Source: Cryptographic Unit Support Program (CUSP)
problem identified by the system completion code. Return Reason Description
Code Code
To ensure that a dump is produced for this problem, run
the job again with a SYSABEND DD statement.
Source: Cryptographic Unit Support Program (CUSP) 8 8 CKT address not passed by
ICUMKM14.
ICU024I UNEXPECTED VSAM ERROR CODE rc 16 CKT information passed from
[FDBK code] ICUMKM14 was not valid.
20 Invalid CKT record key passed
Explanation: An error occurred when the key by ICUMKM14.
manager attempted to read the cryptographic key data 24 Invalid record buffer passed by
set (CKDS). In the message, rc is the return code that ICUMKM14.
identifies the error. If rc identifies a logical error, then 28 No entries in CKT to retrieve.
FDBK code indicates the specific logical error that has
32 Invalid CKT RKP passed by
occurred.
ICUMKM14.

40 CKT record failed modification Source: Cryptographic Unit Support Program (CUSP)
detection check (MDC). CKT
has become corrupted. ICU033I LOAD FAILED FOR CRYPTOGRAPHY
12 36 Recovery environment could INSTALLATION OPTIONS MODULE
not be established in
ICUMKM18. Explanation: The Cryptographic Unit Support
command or the key generator utility program was
unable to load the installation options module,
ICU030I CRYPTOGRAPHY INITIALIZATION ICUOPTN2.
UNABLE TO LOCATE name IN LPA
System Action: Cryptographic Unit Support
Explanation: The Cryptographic Unit Support initialization processing ends.
installation process invoked by the operator START
command or the key generator utility program was Application Programmer Response: Check the
unable to locate the routine specified by name in a output of the install process (SMP) to verify that the
search of the active link pack area queue and the link installation options module was properly installed in
pack area directory. SYS1.LINKLIB. Correct the problem and reissue the
System Action: Cryptographic Unit Support utility program.
Operator Response: Notify the system programmer. this problem, specify MSGLEVEL=(1,1) for the job.
System Programmer Response: Determine if the Source: Cryptographic Unit Support Program (CUSP)
GENKEY or RETKEY installation exit routine (module
ICUMGR90 or ICUMGR95) is properly link edited into
SYS1.LPALIB. If the module has been replaced since ICU034I CRYPTOGRAPHY INITIALIZATION
the Cryptographic Unit Support was installed, check the UNABLE TO ESTABLISH ESTAE CODE
linkage editor output from the most recent change. If it xxx
has not been replaced, check the output of the install Explanation: The Cryptographic Unit Support
process (SMP) to see that the module was properly initialization process invoked by the operator START
installed. Correct the problem and reissue the operator command or the key generator utility program was
START command or rerun the key generator utility unable to establish an ESTAE recovery environment.
program. The code from ESTAE processing is specified by xxx.
To ensure that you have all the messages issued for See OS/390 MVS Programming: Assembler Services
this problem, specify MSGLEVEL=(1,1) for the job. Reference for further information.
Source: Cryptographic Unit Support Program (CUSP) System Action: Cryptographic Unit Support
ICU031I INVALID CRYPTOGRAPHY USER SVC Operator Response: If the code is 14, reissue the
NUMBER SPECIFIED operator START command. For all other codes, contact
your system programmer. When the problem is
Explanation: The Cryptographic Unit Support corrected, reissue the START command.
command or the key generator utility program has Application Programmer Response: If the code is
determined that the options module, ICUOPTN2, 14, run the key generator utility program again. For all
contains an user SVC number that is not valid. other codes, contact your system programmer. When
the problem is corrected, run the key generator utility
System Action: Cryptographic Unit Support program again.
Operator Response: Notify the system programmer. reporting data bases for a fix for the problem. If no fix
System Programmer Response: Update the exists, contact the IBM Support Center.
installation options module, ICUOPTN2, to reflect a valid To ensure that you have all the messages issued for
user SVC number in the range of 200 through 255. See this problem, specify MSGLEVEL=(1,1) for the job.
the Cryptographic Unit Support Program Directory for
information on how to modify the options module. When Source: Cryptographic Unit Support Program (CUSP)
the update is complete, reissue the operator START
command or rerun the key generator utility program.
Chapter 12. ICU Messages 249

corrected, reissue the START command.
ICU041I CRYPTOGRAPHY FACILITY HAS BEEN
ACTIVATED System Programmer Response: The return code
from ESTAE processing is specified by xxx. See
OS/390 MVS Programming: Assembler Services
successfully activated the Cryptographic Unit Support.
Reference for further information.
All functions of the facility are currently operational.
System Action: The Cryptographic Unit Support is
active.
ICU045I CRYPTOGRAPHIC UNIT SUPPORT OR

ICU042I START jobname TERMINATED
KEY GENERATOR OR PROGRAMMED
Explanation: The START command procedure, CRYPTOGRAPHIC FACILITY ALREADY
identified by jobname, ended abnormally when IN PROGRESS
attempting to start the Cryptographic Unit Support. One
Explanation: An operator START command was
or more messages that explain the nature of the error
issued to start the Cryptographic Unit Support but a
precede this message.
cryptographic function is already in progress. The
System Action: START command processing ends. cryptographic function could be the Cryptographic Unit
The Cryptographic Unit Support is not active. Support, the key generator for the Cryptographic Unit
Support, the Programmed Cryptographic Facility, or the
key generator for the Programmed Cryptographic
System Programmer Response: Respond to the Facility.
problem described by the preceding message.
System Action: The START command is ignored.
Operator Response: If a START command was
issued when the Cryptographic Unit Support is already
ICU043I UNABLE TO OPEN SYSCKDS active or the START command procedure is already
running, an operator STOP command must be issued
Explanation: The START command procedure used to before another START command can be accepted. If
start the Cryptographic Unit Support was not able to the key generator utility program is currently running,
open the cryptographic key data set (CKDS) defined by reissue the START command when the utility program
the SYSCKDS DD statement. This message is ends.
accompanied by a VSAM error message that further
identifies the problem. Source: Cryptographic Unit Support Program (CUSP)
System Action: START command processing ends.

ICU047I MODIFY CRYPTOGRAPHY COMMAND
Operator Response: Notify the system programmer. REJECTED
System Programmer Response: Verify that a DD Explanation: An operator MODIFY command was
statement has been included in the START procedure issued to change the configuration of cryptographic
for the CKDS with the ddname SYSCKDS. Check the units, but the configuration established by the MODIFY
accompanying VSAM error message for additional command does not include any cryptographic units
information. Correct the problem and reissue the available to the Cryptographic Unit Support.
operator START command.
System Action: MODIFY command processing ends.
To ensure that you have all the messages issued for System processing continues with the configuration that
this problem, specify MSGLEVEL=(1,1) for the job. existed before the MODIFY command was issued.
Source: Cryptographic Unit Support Program (CUSP) Operator Response: Ensure that the cryptographic
units specified in the command are physically online.
ICU044I START jobname UNABLE TO Reissue the MODIFY command.
ESTABLISH ESTAE CODE xxx Source: Cryptographic Unit Support Program (CUSP)
Explanation: The START procedure used to start the
Cryptographic Unit Support, identified by jobname, was ICU048I MODIFY CRYPTOGRAPHY -- NEW
unable to establish an ESTAE recovery environment. DEVICE CONFIGURATION IS
System Action: START command processing ends. device-addr
Operator Response: If the code is 14, reissue the Explanation: An operator MODIFY command has
operator START command. For all other codes, notify successfully changed the configuration of cryptographic
your system programmer. When the problem is units. In the message, device-addr identifies the

cryptographic unit now available to the Cryptographic System Action: Key generator utility processing ends.
Unit Support.
CKDS and MKDS that are defined on the specified DD
ICU050I USER-SUPPLIED KEY AND DEVICE statements are the current versions of the data sets.
device-addr KEY DO NOT MATCH Rerun the key generator utility program. Notify the
security administrator.
Explanation: The host master key supplied as input to
the key generator does not have the same value as the Source: Cryptographic Unit Support Program (CUSP)
host master key installed in the cryptographic unit
identified by device-addr.
ICU053I USER-SUPPLIED KEY AND KEY USED
System Action: Processing continues if another TO CREATE ddname DO NOT MATCH
cryptographic unit is available. Otherwise, processing
Explanation: The value supplied to the key generator
ends.
as the old host master key (for a CHGM request) is not
Operator Response: Notify the security administrator. the value whose variants were used to encipher the
entries on the cryptographic key data set (CKDS),
Application Programmer Response: If a
identified in the message by ddname.
cryptographic unit was not available to continue
processing, rerun the key generator utility program. System Action: Key generator utility processing ends.
Security Administrator Response: Ensure that the Operator Response: Notify the system programmer.
host master key installed in the cryptographic unit and
the value supplied in the PARM field of the EXEC
CKDS that is defined on the specified DD statement is
statement are the same.
the current version of the data set. Ensure that the
Source: Cryptographic Unit Support Program (CUSP) value supplied to the key generator is the value that
was in the cryptographic unit just before the most recent
change. Rerun the key generator utility program. Notify
ICU051I KEY USED TO CREATE DATA SET
the security administrator.
ddname AND DEVICE device-addr KEY
DO NOT MATCH Source: Cryptographic Unit Support Program (CUSP)
Explanation: The host master key installed in the
cryptographic unit, identified by device-addr, is not the ICU054I KEY VERIFICATION NOT EXECUTED.
same value as the host master key whose variants were INVALID INPUT.
used to encipher entries on the cryptographic key data
Explanation: The code that indicates which of the key
set (CKDS), identified in the message by ddname.
verification tests is to be performed was not valid. The
System Action: If another cryptographic unit is code did not indicate any of the defined key verification
available, processing continues. Otherwise, processing tests.
ends.
System Action: The program that requested key
Operator Response: Notify the system programmer. verification (either the key generator utility, START
command processing, or MODIFY command
processing) ends.
CKDS, defined by the specified ddname, is the current
version of the data set. If a cryptographic unit was not Operator Response: Notify the system programmer.
available to continue processing, rerun the key When the problem has been corrected, issue the
generator utility program. Notify the security START or MODIFY command again.
administrator.
Application Programmer Response: Notify the
Source: Cryptographic Unit Support Program (CUSP) system programmer. When the problem has been
corrected, run the key generator utility again.
ICU052I DATA SETS ddname-1 AND ddname-2 Source: Cryptographic Unit Support Program (CUSP)
NOT CREATED WITH SAME MASTER
KEY
ICU055I KEY VERIFICATION TEST FAILED DUE
Explanation: The entries on the cryptographic key TO I/O ERROR
data set (CKDS), identified in the message by
Explanation: A cryptographic unit failed the key
ddname-1, were not enciphered under the host master
verification test because of an I/O error. This error can
key variants that are stored on the master key variant
occur following the invocation of the cryptographic unit
data set (MKDS), identified in the message by
access routine.
ddname-2.

System Action: If another cryptographic unit is
ICU062I INITIALIZATION OF CRYPTOGRAPHY
available, processing continues. Otherwise, processing
FACILITY AND OPEN SYSCKDS
ends. A logrec data set record is written.
SUCCESSFUL
Operator Response: Contact hardware support. Notify
successfully initialized the Cryptographic Unit Support
System Programmer Response: Run OLTEP and has opened the cryptographic key data set defined
diagnostics for the problem device. by the SYSCKDS DD statement. Key verification must
still be performed on the cryptographic unit(s) before all
Source: Cryptographic Unit Support Program (CUSP) functions of the Cryptographic Unit Support are
operational.
ICU060I INTERNAL CKDS LOAD FAILURE - System Action: System processing continues.
ERROR CODE xx yy
Explanation: A module attempted but failed to load
the cryptographic key table (CKT). The module returns
xx and yy, the return and reason codes for the error. An ICU070I INTERNAL BUFFER BAD ON DEVICE
error was encountered when ICUMKM17 attempted to device-addr
load the CUSP cryptographic key data set (CKDS) into
Explanation: The internal buffer of the cryptographic
an in-core tabular image of the file called the
unit identified by device-addr is not functioning properly.
cryptographic key table (CKT).
System Action: If at least one other cryptographic unit
System Action: Processing associated with creating
is available, processing continues. Otherwise,
the cryptographic key table (CKT) ends.
processing ends.
Operator Response: Respond according to the
Operator Response: Contact hardware support. Notify
specific return and reason codes.
Return Reason Description
Code Code ICU071I I/O PROCESSING FAILED ON DEVICE
device-addr
Explanation: The cryptographic unit, identified by
4 20 Error closing the CUSP CKDS. device-addr, was unable to process input/output data
12 4 Error opening the CUSP CKDS. because of a hardware error.
12 Unable to get storage for CKT
(in subpool 231).
16 Error occurred during VSAM
ends.
GET on CUSP CKDS. If the
error is a VSAM physical error, Operator Response: Contact hardware support. Notify
this message is preceded by the security administrator.
message ICU020I. If the error
is a VSAM logical error, this
message is preceded by
message ICU024I. ICU072I NO DEVICE PATH TO DEVICE
28 Recovery environment could device-addr
not be established in
Explanation: There is no physical I/O path to the
ICUMKM17.
cryptographic unit identified by device-addr.
ICU061I CRYPTOGRAPHY FACILITY HAS BEEN
ends.
TERMINATED
Explanation: An operator STOP command has
successfully deactivated the Cryptographic Unit Support. System Programmer Response: Ensure that the
All current sessions and all new sessions will fail. cryptographic unit is physically online and logically
online (by means of a VARY command) and that the
cryptographic unit’s physical key is locked. Then issue a
Source: Cryptographic Unit Support Program (CUSP) MODIFY command to add this unit to the configuration
of cryptographic units, or issue a START command after
the Cryptographic Unit Support is stopped.

To ensure that you have all the messages issued for Operator Response: Notify the system programmer
this problem, specify MSGLEVEL=(1,1) for the job. and security administrator.
Source: Cryptographic Unit Support Program (CUSP) System Programmer Response: Ensure that all
access to any cryptographic unit is controlled by the
Cryptographic Unit Support to benefit from the
ICU073I INTERNAL LINE BUFFER TEST
authorization checks it performs to ensure the security
UNABLE TO GETMAIN STORAGE
of the cryptographic unit.
Explanation: The test to determine if the internal
buffer is functioning properly could not be performed
because the routine could not obtain sufficient storage.
ends. ICU078I DEVICE device-addr UNAVAILABLE -
OFFLINE AND IN USE BY A SYSTEM
COMPONENT
System Programmer Response: Ensure that
Explanation: The Cryptographic Unit Support
sufficient storage is available in subpool 252. Reissue
attempted to allocate the cryptographic unit identified by
the START command or rerun the key generator utility
device-addr, but the unit was designated as not
program.
allocatable (UCBNALOC=ON).
Source: Cryptographic Unit Support Program (CUSP) ends.
Operator Response: Notify the system programmer
ICU074I UNABLE TO DYNAMICALLY and security administrator.
ALLOCATE DEVICE device-addr CODE
System Programmer Response: Ensure that all
xxxx
access to any cryptographic unit is controlled by the
Explanation: Dynamic allocation failed with code xxxx Cryptographic Unit Support to benefit from the
while attempting to allocate or deallocate the authorization checks it performs to ensure the security
cryptographic unit identified by device-addr. of the cryptographic unit.
System Action: If another cryptographic unit is To ensure that you have all the messages issued for
available, processing continues. Otherwise, processing this problem, specify MSGLEVEL=(1,1) for the job.
ends.
System Programmer Response: See OS/390 MVS ICU080I I/O INITIALIZATION UNABLE TO
Programming: Authorized Assembler Services Guide for ESTABLISH ESTAE CODE xxx
the explanation of the error code. Correct the problem
Explanation: The Cryptographic Unit Support I/O
and reissue the START command or rerun the key
initialization routine, invoked by the operator START
generator utility.
command or the key generator utility program, was
To ensure that you have all the messages issued for unable to establish a recovery environment. The return
this problem, specify MSGLEVEL=(1,1) for the job. code from ESTAE processing is specified by xxx. See
OS/390 MVS Programming: Assembler Services
Source: Cryptographic Unit Support Program (CUSP) Reference for further information.
System Action: The Cryptographic Unit Support I/O
ICU077I DEVICE device-addr PREVIOUSLY initialization or key generator utility ends.
ALLOCATED TO ANOTHER JOB OR
TASK Operator Response: If the code is 4, reissue the
Explanation: The Cryptographic Unit Support utility program. For all other codes, contact your system
attempted to allocate the cryptographic unit identified by programmer. When the problem is corrected, reissue
device-addr, but the unit is allocated to another job or the START command or rerun the key generator.
task in the system.
Application Programmer Response: If the code is 4,
System Action: If another cryptographic unit is rerun the key generator utility program. For all other
available, processing continues. Otherwise, processing codes, contact your system programmer. When the
ends. problem is corrected, reissue the START command or
rerun the key generator.

System Programmer Response: Search problem System Action: START command or key generator
reporting data bases for a fix for the problem. If no fix utility processing ends.
To ensure that you have all the messages issued for When the problem is corrected, issue the START
this problem, specify MSGLEVEL=(1,1) for the job. command again.
Source: Cryptographic Unit Support Program (CUSP) Application Programmer Response: Notify the
system programmer. When the problem is corrected,
run the key generator utility program again.
ICU081I I/O INITIALIZATION UNABLE TO
GETMAIN SP227 STORAGE System Programmer Response: Ensure that
sufficient storage is available in subpool 230.
Explanation: The Cryptographic Unit Support I/O
initialization routine, invoked by the operator START To ensure that you have all the messages issued for
command or the key generator utility program, was this problem, specify MSGLEVEL=(1,1) for the job.
unable to obtain sufficient storage from subpool 227.
System Action: START command or key generator
utility program processing ends.
ICU085I NO CRYPTOGRAPHIC UNITS
Operator Response: Notify the system programmer. AVAILABLE
System Programmer Response: Ensure that Explanation: All cryptographic units failed with one of
sufficient storage is available in subpool 227. Reissue the following errors:
the START command or rerun the key generator utility v Key verification test failed
program.
v Internal buffer test failed
To ensure that you have all the messages issued for v Sufficient storage to perform the internal buffer test
this problem, specify MSGLEVEL=(1,1) for the job. could not be obtained.
Source: Cryptographic Unit Support Program (CUSP) v The cryptographic unit could not be opened.
One or more messages that explain the error precede

ICU082I NO 3848 CRYPTOGRAPHIC UNITS
this message.
SYSGENED INTO ELIGIBLE DEVICE
TABLE System Action: START command or key generator
processing ends.
Explanation: No entries with UNITNAME=3848 were
found in the eligible device table. An entry with Operator Response: Notify the system programmer.
UNITNAME=3848 must exist for each cryptographic unit
defined in the configuration, and at least one such entry System Programmer Response: Respond to the
must exist for successful initialization of the problem described by the preceding message.
Cryptographic Unit Support. Source: Cryptographic Unit Support Program (CUSP)
System Action: START command or key generator
utility processing ends. ICU1001 WEAK KEY SPECIFIED
Operator Response: Notify the system programmer. Explanation: A weak clear key value was specified on
System Programmer Response: Ensure that at least a LOCAL, LOCAL-GROUP, REMOTE, or CROSS
one cryptographic unit is defined during system control statement for the key generator utility program.
generation. Reissue the START command or rerun the The control statement containing the weak key
key generator utility program. precedes this message.
To ensure that you have all the messages issued for System Action: Processing ends for this control
this problem, specify MSGLEVEL=(1,1) for the job. statement. Processing continues for any other control
statements.
Application Programmer Response: Supply a new
clear key value on the control statement or remove the
ICU084I IEFAB4UV UNABLE TO GETMAIN KEY parameter completely to let the key generator
SP230 STORAGE utility program generate a clear key value. See OS/390
DFSMS: Using Data Sets for a description of weak key
Explanation: The allocation unit verification routine
values. Rerun the utility program, specifying the CHGK
(IEFAB4UV) that is used by the I/O initialization routine,
function on the EXEC statement and providing the
invoked by the operator START command or the key
corrected control statement as input.
generator utility program, was unable to obtain sufficient
storage from subpool 230. Source: Cryptographic Unit Support Program (CUSP)

ICU1002 INVALID VERB ICU1005 INVALID OR REDUNDANT KEYWORD
SPECIFIED
Explanation: A verb specified on a control statement
for the key generator utility program was not valid. The Explanation: An incorrect or redundant keyword
control statement containing the error precedes this parameter was specified on a LOCAL, LOCAL-GROUP,
message. REMOTE, CROSS, or REASGN control statement for
the key generator utility program. The control statement
containing the error precedes this message.
statements. System Action: Processing ends for this control
Application Programmer Response: Correct the verb
statements.
on the control statement. The valid verbs are LOCAL,
LOCAL-GROUP, REMOTE, CROSS, EXTRA-LOCAL, Application Programmer Response: Correct the
EXTRA-REMOTE, EXTRA-CROSS, REASGN, and keyword parameter or remove the redundant keyword
INSTDAT. The verb must be preceded and followed by parameter on the control statement. Rerun the key
a blank. Rerun the key generator utility program, generator utility program, specifying the CHGK function
specifying the CHGK function on the EXEC statement on the EXEC statement and providing the corrected
and providing the corrected control statement as input. control statement.
Source: Cryptographic Unit Support Program (CUSP) Source: Cryptographic Unit Support Program (CUSP)
ICU1003 SYNTAX ERROR IN KEY ICU1006 INVALID VALUE SPECIFIED ON EXTRA

STATEMENT
Explanation: An incorrect clear key value was
specified on a LOCAL, LOCAL-GROUP, REMOTE, or Explanation: One of the following conditions was
CROSS control statement for the key generator utility encountered on an EXTRA-LOCAL, EXTRA-CROSS, or
program. The control statement containing the error EXTRA-REMOTE control statement for the key
precedes this message. generator utility program:
System Action: Processing ends for this control v The first through fourth characters of the value for
statement. Processing continues for any other control label-base were not alphameric.
statements. v The fifth through eighth characters of the value for
label-base were not numeric.
clear key value on the control statement. A valid value v An incorrect number of additional keys was
consists of 16 hexadecimal digits. (Valid hexadecimal requested.
digits are 0 through 9 and A through F.) Rerun the key
generator utility program, specifying the CHGK function The control statement containing the error precedes this
on the EXEC statement and providing the corrected message.
control statement as input. System Action: Processing ends for this control
Source: Cryptographic Unit Support Program (CUSP) statement. Processing continues for any other control
statements.
ICU1004 SYNTAX ERROR IN LABEL Application Programmer Response: If the

alphameric portion of the label-base is incorrect, supply
Explanation: An incorrect label was specified on a a valid value on the control statement. A valid value
LOCAL, LOCAL-GROUP, REMOTE, CROSS, or consists of 4 alphameric characters. Valid alphameric
REASGN control statement for the key generator utility characters are A through Z and 0 through 9.
program. The control statement containing the error
precedes this message. Otherwise, correct the numerical portion of the
label-base and/or the number of additional keys
System Action: Processing ends for this control requested on the control statement. The sum of these
statement. Processing continues for any other control two values must not exceed 9999.
statements.
Rerun the key generator utility program, specifying the
Application Programmer Response: Supply a valid CHGK function on the EXEC statement and providing
label on the control statement. A valid label consists of 1 the corrected control statement.
to 8 alphameric characters. Valid alphameric characters
are A through Z and 0 through 9. Rerun the key Source: Cryptographic Unit Support Program (CUSP)
on the EXEC statement and providing the corrected
control statement as input.

label was not defined in the CKDS. The rejected control
ICU1007 STATEMENT REJECTED BY
statement precedes this message.
INSTALLATION EXIT
Explanation: A control statement was rejected by the
key generator utility program installation exit routine.
statements.
The rejected control statement precedes this message.
correct label and rerun the key generator utility program,
specifying the CHGK function on the EXEC statement.
statements.
Application Programmer Response: Follow local
procedures for errors detected by the key generator
utility program installation exit routine. Correct the error ICU1011 synad I/O error message from VSAM
and, if necessary, rerun the utility program. Specify the
CHGK function on the EXEC statement and provide the Explanation: A physical I/O error occurred when the
corrected control statement. key generator utility program attempted to access the
SYSCKDS or SYSNCKDS data set.
ICU1008 REQUIRED PARAMETER System Programmer Response: See the explanation

INFORMATION MISSING of the accompanying VSAM physical I/O error message
in your VSAM macro instruction book. If the volume
Explanation: The key generator utility program found caused the error, use a backup copy of the CKDS on a
that the value for the SETM, CHGM, or SEED different volume. (If you do not want to re-IPL the
parameter on the EXEC statement is missing. system, ensure that the new copy of the CKDS uses the
same host master key as the old copy.) If the device
Application Programmer Response: Supply the CKDS to an alternate device.
missing value in the PARM field of the EXEC statement
Rerun the key generator utility program as follows. If the
and rerun the key generator utility program.
SETM or CHGM function was requested and the host
To ensure that you have all the messages issued for master key was not set (message ICU010I was not
this problem, specify MSGLEVEL=(1,1) for the job. issued), rerun the entire job. Otherwise, use this listing
to determine which control statements were processed
CHGK function to process the remaining control
ICU1009 DUPLICATE LABEL; KEY NOT ADDED statements.
Explanation: A user requested the key generator To ensure that you have all the messages issued for
utility program to add a label and its associated this problem, specify MSGLEVEL=(1,1) for the job.
secondary key-encrypting key to the cryptographic key
data set (CKDS), but the specified label was already
defined in the CKDS. The rejected control statement
precedes this message. ICU1012 PROCESSING TERMINATES DUE TO
INSTALLATION EXIT REQUEST
statement. Processing continues for any other control Explanation: The key generator utility program stops
statements. processing at the request of the installation exit routine.
If the problem occurred while the utility program was
Application Programmer Response: Assign a unique
label to the key and rerun the key generator utility
contents of the PARM field of the EXEC statement
program, specifying the CHGK function on the EXEC
statement and providing the corrected control statement.
Source: Cryptographic Unit Support Program (CUSP) statement, the control statement precedes this
message.
ICU1010 LABEL NOT FOUND; NOT System Action: Key generator utility processing ends.
PROCESSED
Application Programmer Response: Follow local
Explanation: A user requested the key generator procedures.
utility program to update a secondary key-encrypting
key or to delete a label and its associated key from the
cryptographic key data set (CKDS), but the specified

Correct the problem and rerun the key generator utility
ICU1013 PROCESSING ENDED DUE TO ESTAE
program as follows. If the SETM or CHGM function was
OR STAE RETURN CODE xxx
requested and the host master key was not set,
Explanation: The key generator utility program (message ICU010I was not issued), rerun the entire job.
attempted to use the ESTAE system service, but the Otherwise, use this listing to determine which control
error code xxx was returned. statements were processed successfully. Then rerun the
No control statements are processed.
Application Programmer Response: If the code is To ensure that you have all the messages issued for
14, run the key generator utility program again. For all this problem, specify MSGLEVEL=(1,1) for the job.
other codes, contact your system programmer. When
the problem is corrected, run the key generator utility
program again.
ICU1017 CRYPTOGRAPHY STARTED; INVALID
KEY GENERATOR REQUEST
exists, contact the IBM Support Center. Explanation: The key generator utility program was
unable to run because the Cryptographic Unit Support
was active.
ICU1014 SYSIN DATA SET EMPTY; NO
PROCESSING OCCURRED Application Programmer Response: When the
Cryptographic Unit Support is stopped and there are no
Explanation: The CHGK function of the key generator
cryptographic sessions or jobs running in the system,
utility program was requested but no control statements
rerun the key generator utility program to change the
could be found.
host master key. Restart the Cryptographic Unit Support
System Action: Key generator utility processing ends. by entering an operator START command.
Application Programmer Response: Add the desired Source: Cryptographic Unit Support Program (CUSP)
control statements to the SYSIN data set and rerun the
key generator utility program.
ICU1018 KEY GENERATION NOT ALLOWED -
Source: Cryptographic Unit Support Program (CUSP) text
text is
ICU1015 UNABLE TO [OPEN | CLOSE ] ddname
TOD CLOCK ERROR
[CODE rc]
SEED NOT SUPPLIED
Explanation: The key generator utility program was
Explanation: An error was encountered when the key
unable to open or close the data set defined by the DD
generator utility program attempted to read the
statement identified by ddname.
time-of-day (TOD) clock, the TOD clock was inoperative,
If the data set is a VSAM data set (SYSCKDS or or a seed value was not supplied on the EXEC
SYSNCKDS), the VSAM return code rc is included to statement. Processing continues; however, no keys can
help identify the error. For the explanation of the return be generated.
code, see the description of the VSAM macro. This
message is accompanied by a VSAM error message
continues.
that further identifies the problem.
Application Programmer Response: If the problem
involves the TOD clock, contact your service
Application Programmer Response: If the problem representative. If a seed value was not supplied, ignore
occurred while trying to open a data set, check the JCL. this message unless message ICU1025 also appears. If
Be sure the required DD statements were included, that message ICU1025 appears, see the description of
they have the correct ddnames, and that they define the message ICU1025.
correct data sets. The following ddnames are valid:
SYSCKDS, SYSNCKDS, SYSIN, and SYSMKDS.
Note: An open failure can also occur if the SYSCKDS ICU1019 CRYPTOGRAPHY SYSTEM MASTER
or SYSNCKDS data set was defined without the KEY HAS BEEN SET
proper parameters on the access method
services DEFINE CLUSTER command.
successfully set the host master key. If there are any
control statements requesting updates to the secondary

key-encrypting keys, they are processed at this time. with the corrected exit routine. (See OS/390 DFSMS:
Using Data Sets .) Rerun the key generator utility
program as follows. Rerun the entire job if the SETM or
continues.
CHGM function was requested and the host master key
Source: Cryptographic Unit Support Program (CUSP) was not set (the contents of the PARM field precede
this message).
ICU1020 INVALID KEYWORD SPECIFIED IN Otherwise, use this listing to determine which control
PARM FIELD statements were processed successfully. Then rerun the
Explanation: A keyword parameter specified in the remaining control statements.
PARM field of the EXEC statement for the key
generator utility program was not valid. To ensure that you have all the messages issued for
keyword parameter in the PARM field. The valid
keyword parameters are SETM, CHGM, CHGK, and ICU1024 REQUIRED OPERAND[S] MISSING;
SEED. Rerun the key generator utility program. STATEMENT IGNORED
To ensure that you have all the messages issued for Explanation: While scanning a SYSIN control
this problem, specify MSGLEVEL=(1,1) for the job. statement, the key generator utility program could not
find one or more required parameters. LOCAL,
Source: Cryptographic Unit Support Program (CUSP) LOCAL-GROUP, REMOTE, and CROSS control
statements require a label. EXTRA-LOCAL,
ICU1021 WEAK SYSTEM MASTER KEY EXTRA-REMOTE, and EXTRA-CROSS control
SPECIFIED statements require a number and a label-base. The
REASGN control statement requires an existing label
Explanation: A weak value for the new host master and a new label. The control statement containing the
key was specified in the PARM field of the EXEC error precedes this message.
statement for the key generator utility program.
System Action: Key generator utility processing ends. statement. Processing continues for any other control
Application Programmer Response: Supply a new statements.
host master key value and its complement in the PARM Application Programmer Response: Correct the
field of the EXEC statement. See OS/390 DFSMS: control statement. Rerun the key generator utility
Using Data Sets for a description of weak key values. program, specifying the CHGK function on the EXEC
Rerun the key generator utility program. statement and providing the corrected control statement.
To ensure that you have all the messages issued for Source: Cryptographic Unit Support Program (CUSP)
Source: Cryptographic Unit Support Program (CUSP) ICU1025 REQUIRED INPUTS FOR KEY
GENERATION NOT AVAILABLE
ICU1023 INVALID RETURN CODE FROM Explanation: The key generator utility program
INSTALLATION EXIT; PROCESSING attempted to generate a key for a control statement and
TERMINATES either a problem occurred with the time-of-day (TOD)
Explanation: A return code provided by the key clock or a valid seed value was not supplied on the
generator utility program installation exit was not valid. If EXEC statement. Message ICU1018, which identifies
the problem occurred while the key generator utility the specific problem, and the control statement being
program was processing a change to the host master processed when the problem occurred, precede this
key, the contents of the PARM field of the EXEC message.
statement precede this message. If the problem System Action: Processing ends for this control
occurred while the utility program was processing a statement. Processing continues for any other control
SYSIN control statement, the control statement statements.
precedes this message.
v If message ICU1018 stated that there is a problem
System Action: Key generator utility processing ends. involving the TOD clock, contact your service
representative.
installation exit routine to determine if there are any v If message ICU1018 stated that a seed value was
problems in the module and make any necessary supplied, add a seed value to the EXEC statement.
corrections. Link edit the key generator utility program

Rerun the key generator utility program specifying the error return code from the EMK macro. The values of xx
CHGK function on the EXEC statement and providing and their explanations are as follows:
the control statement that was being processed when
Code Explanation
the problem occurred.
4 The Cryptographic Unit Support has not been
initialized.
8 An incorrect operation was requested; the
ICU1030 INVALID SMF DATA LENGTH FROM
macro was not EMK.
INSTALLATION EXIT; PROCESSING
TERMINATES 12 An ESTAE recovery environment could not be
established or an unrecoverable I/O error
Explanation: The key generator installation exit
occurred.
routine returned the SMF buffer with a value greater
than 64 in the length field. 32 The address of the clear key-encrypting key or
the address of the enciphered key-encrypting
System Action: The key generator utility program
key was specified as zero.
does not include the installation-defined data in the SMF
record. The program writes the SMF record to the SMF System Action: Key generator utility processing ends.
data set and stops processing.
Application Programmer Response: Check the programming support personnel. When the problem has
installation exit routine to determine if there are any been corrected, rerun the key generator utility program
problems in the module and make any necessary as follows. If the SETM or CHGM function was
corrections. Link edit the key generator utility program requested and the host master key was not set,
with the corrected exit routine. See OS/390 DFSMS: (message ICU010I was not issued), rerun the entire job.
Using Data Sets Rerun the key generator utility program Otherwise, use this listing to determine which control
as follows. If the SETM or CHGM function was statements were processed successfully. Then rerun the
requested and the host master key was not set utility program using the CHGK function to process the
(message ICU010I was not issued), rerun the entire job. remaining control statements.
Otherwise, use this listing to determine which control
statements were processed successfully. Then rerun the To ensure that you have all the messages issued for
utility program using the CHGK function to process the this problem, specify MSGLEVEL=(1,1) for the job.
remaining control statements. Notify the security Source: Cryptographic Unit Support Program (CUSP)
administrator.
To ensure that you have all the messages issued for ICU1033 CRYPTOGRAPHY CIPHER FUNCTION
this problem, specify MSGLEVEL=(1,1) for the job. FAILED - CODE xx
Source: Cryptographic Unit Support Program (CUSP) Explanation: An error occurred during the processing
of a CIPHER macro instruction issued by the key
ICU1031 INVALID DELIMITER IN PARM FIELD generator utility program. In the message text, xx is the
error return code from the macro. The values of xx and
Explanation: While scanning the PARM field of the their explanations are as follows:
EXEC statement, the key generator utility program did
not find an expected delimiter or encountered an Code Explanation
unexpected delimiter. 4 The Cryptographic Unit Support has not been
System Action: Key generator utility processing ends. initialized. The data could not be enciphered or
deciphered.
Application Programmer Response: The valid
delimiters are comma, right and left parentheses, and 8 An incorrect operation was requested; the
blank. Correct the error and rerun the key generator macro was not CIPHER.
utility program. 12 An ESTAE recovery environment could not be
To ensure that you have all the messages issued for established or an unrecoverable I/O error
this problem, specify MSGLEVEL=(1,1) for the job. occurred.
Source: Cryptographic Unit Support Program (CUSP) 16 The length of the data to be enciphered or
deciphered was specified as zero or as a
negative number, or exceeded the maximum
ICU1032 CRYPTOGRAPHY EMK FUNCTION specified in the installation options module.
FAILED - CODE xx
20 The BRANCH=YES parameter was specified,
Explanation: An error occurred during the processing but the program issuing the macro is not
of an EMK macro instruction issued by the key running in supervisor state.
generator utility program. In the message text, xx is the

32 The address of the clear data or the statements were processed successfully. Then rerun the
enciphered data was specified as zero. utility program using the CHGK function to process the
40 A retry of the CIPHER request was required
but could not be performed because the input To ensure that you have all the messages issued for
area and output area overlapped. this problem, specify MSGLEVEL=(1,1) for the job.
System Action: Key generator utility processing ends. Source: Cryptographic Unit Support Program (CUSP)
programming support personnel. When the problem has ICU1035 synad message for non-VSAM
Explanation: An I/O error occurred while the key
as follows. If the SETM or CHGM function was
generator utility program was processing the non-VSAM
requested and the host master key was not set
data set defined by the SYSMKDS or SYSIN DD
(message ICU010I was not issued), rerun the entire job.
statement. The format and explanation of the message
is in the description of the SYNADAF macro in your
VSAM macro instruction book.
remaining control statements. System Action: Key generator utility processing ends.
To ensure that you have all the messages issued for Application Programmer Response: See OS/390
this problem, specify MSGLEVEL=(1,1) for the job. DFSMS Macro Instructions for Data Sets for the
explanation of the message. Correct the problem and
rerun the key generator utility program as follows. If the
SETM or CHGM function was requested and the host
ICU1034 CRYPTOGRAPHY KEY TRANSLATION master key was not set (message ICU010I was not
FAILED - CODE xx issued), rerun the entire job. Otherwise, use this listing
to determine which control statements were processed
Explanation: An error has occurred during key
translation processing. The translation was requested by
CHGK function to process the remaining control
the key generator utility program. In the message text,
statements.
xx is the error return code from the key translation
process. The values of xx and their explanations are as Notify the security administrator.
follows:
Code Explanation this problem, specify MSGLEVEL=(1,1) for the job.
4 The Cryptographic Unit Support has not been Source: Cryptographic Unit Support Program (CUSP)
initialized.
8 The operation requested was not valid. ICU1036 CKDS ENTRY SUCCESSFULLY
DELETED
established or an unrecoverable I/O error Explanation: The key generator utility program has
occurred. successfully deleted an entry from the cryptographic key
data set (CKDS). The control statement that was
24 Bad parity was detected in the local, remote, or
processed precedes this message.
cross key.
28 The program requesting the key translation
function is not APF-authorized or in supervisor Source: Cryptographic Unit Support Program (CUSP)
state or running under storage protect key 0
through 7.
ICU1038 NO CRYPTOGRAPHIC UNITS ARE
32 The address of the enciphered data-encrypting AVAILABLE WITH A VERIFIED KEY
key or the address of the enciphered
Explanation: The key generator has determined that
key-encrypting key was specified as zero.
either key verification has not completed successfully for
System Action: Key generator utility processing ends. any of the cryptographic units that are online or that key
verification has completed successfully for a
cryptographic unit but the master key in the
programming support personnel. When the problem has
cryptographic unit has been changed.
as follows. If the SETM or CHGM function was System Action: Key generator utility processing ends.
requested and the host master key was not set
(message ICU010I was not issued), rerun the entire job.
security administrator. Determine if message ICU050I,
ICU051I, ICU052I, ICU053I, ICU054I, or ICU055I was

issued; if so, refer to that message for the appropriate
ICU1041 CONTINUATION CARD EXPECTED AND
response and rerun the job. If not, then the
NOT FOUND
cryptographic unit was tampered with while the key
generator was running. Ensure that the master key in Explanation: A LOCAL-GROUP or CROSS control
the cryptographic unit is properly installed. Then rerun statement was expected to continue (that is, it ended
the key generator as follows. If the SETM or CHGM with a comma) but did not. The control statement
function was requested and the host master key was containing the error precedes this message.
not set (message ICU010I was not issued), rerun the
entire job. Otherwise, use this listing to determine which
control statements were processed successfully. Then
statements.
rerun the utility program using the CHGK function to
process the remaining control statements. Application Programmer Response: Correct the
format of the control statement or add the continuation
card. Rerun the key generator utility program, specifying
the CHGK function on the EXEC statement and
Source: Cryptographic Unit Support Program (CUSP) providing the corrected control statement.
ICU1039 LABEL IS A RESERVED KEY WORD
Explanation: The label supplied for a cryptographic ICU1042 INVALID CHANGE REQUESTED
key data set (CKDS) entry is not valid. The following
Explanation: A control statement requests a change
key words cannot be used for labels: LOCAL, REMOTE,
to an entry in the cryptographic key data set (CKDS);
CROSS, REASGN, ADD, UPDATE, DELETE, KEY,
however, the change conflicts with the existing entry.
IKEY, KEYLOC, IKEYLOC, KEYREM, IKEYREM. The
For a REASGN control statement, if the new label
control statement containing the error precedes this
already exists on the CKDS, it must contain the same
message.
type of key-encrypting key as the existing label entry.
System Action: Processing ends for this control For a LOCAL, REMOTE, or CROSS control statement,
statement. Processing continues for any other control the updated or deleted entry must have the same type
statements. of key-encrypting key as the old CKDS entry. That is, to
update or delete a local key, use a LOCAL control
statement; to update or delete a remote key, use a
label on the control statement. Rerun the key generator
REMOTE control statement; and to update or delete
utility program, specifying the CHGK function on the
cross keys, use a CROSS control statement. The
EXEC statement providing the corrected control
control statement containing the error precedes this
statement.
message.
ICU1040 LOCAL-GROUP STATEMENT statements.
CONTAINS TOO MANY LABELS
Explanation: The maximum number of labels that can control statement in error. Rerun the key generator
be specified on a LOCAL-GROUP control statement is utility program, specifying the CHGK function on the
64. The control statement containing the error precedes EXEC statement and providing the corrected control
this message. statement.
System Action: Processing ends for this control Source: Cryptographic Unit Support Program (CUSP)
statements.
ICU1043 CKDS RECORD WITH VERIFICATION
Application Programmer Response: Rerun the key PATTERNS NOT FOUND
Explanation: The key generator has searched the
on the EXEC statement. Provide more than one
cryptographic key data set (CKDS) and cannot locate
LOCAL-GROUP control statement as necessary so that
the records that contain the verification patterns. (These
each does not specify more than 64 labels.
verification patterns are derived when the CKDS is
Source: Cryptographic Unit Support Program (CUSP) created and are used in the key verification procedure.)
The records are expected to have labels of
X'DACBEDFCEDCCFEE1' and
X'DACBEDFCEDCCFEE2'.

security administrator. The CKDS is probably not v Define a larger data set for use as the new target
usable. If a back-up copy of the CKDS is available, use CKDS and copy the contents of the original target
it; otherwise, the CKDS must be recreated. CKDS to the larger data set.
Then, use this listing to determine which control
statements were processed successfully and rerun the
Source: Cryptographic Unit Support Program (CUSP) key generator utility program using the CHGK option to
process the remaining control statements.
ICU1044 THE ATTACH OF TASK ICUMKG04
For information on defining and reorganizing the CKDS,
FAILED WITH CODE xx
see DFSMS/MVS Access Method Services for VSAM
Explanation: An error occurred when the key The commands needed to define, reorganize, and copy
generator issued the ATTACH macro instruction for the data set are described in DFSMS/MVS Access
ICUMKG04. The module could not be found in Method Services for VSAM and OS/390 DFSMS Macro
SYS1.LINKLIB. This module is invoked when the key Instructions for Data Sets.
generator has determined that the cryptographic unit
has been tampered with. ICUMKG04 will try to locate Notify the security administrator.
another cryptographic unit that is available to the
Cryptographic Unit Support. To ensure that you have all the messages issued for
System Action: Key generator utility processing ends. this problem, specify MSGLEVEL=(1,1) for the job.
Application Programmer Response: Notify the Source: Cryptographic Unit Support Program (CUSP)
security administrator. Ensure that the module
ICUMKG04 is properly loaded in SYS1.LINKLIB and ICU1046 INVALID SYNTAX FOR {OLD MASTER
rerun the key generator utility. KEY | NEW MASTER KEY | SEED}
To ensure that you have all the messages issued for Explanation: An incorrect value for the SETM, CHGM,
this problem, specify MSGLEVEL=(1,1) for the job. or SEED parameter was found in the PARM field of the
Source: Cryptographic Unit Support Program (CUSP) EXEC statement for the key generator utility program.
ICU1045 INSUFFICIENT SPACE ON ddname Application Programmer Response: Correct the
Explanation: The key generator utility program could value in the PARM field of the EXEC statement. A valid
not complete a request to build or update the data set value consists of 16 hexadecimal digits. (Valid
defined in the message by ddname because there is hexadecimal digits are 0 through 9 and A through F.)
insufficient space on the target data set. Rerun the key generator utility program.
If the problem occurred while the utility program was Source: Cryptographic Unit Support Program (CUSP)
contents of the PARM field of the EXEC statement ICU1047 UNEXPECTED VSAM ERROR ON
precede this message. If the problem occurred while the ddname CODE rc [FDBK code]
statement, the control statement precedes this Explanation: An error occurred when the key
message. generator utility program attempted to read from or write
to the data set identified by ddname in the message. In
System Action: Key generator utility processing ends. the message, rc is the return code that identifies the
Application Programmer Response: Notify your error. If rc identifies a logical error, then FDBK code
system programmer. indicates the specific logical error that has occurred.
System Programmer Response: If the SETM or System Action: Key generator utility processing ends.
CHGM function was requested and the host system System Programmer Response: For an explanation
master key was not set (the contents of the PARM field of the return code and feedback code, see the
precede this message), define a larger target data set description of the VSAM macro. Correct the problem
for the CKDS and rerun the entire job. Otherwise, the and rerun the utility program as follows. If the SETM or
key generator utility program failed while processing a CHGM function was requested and the host master key
SYSIN control statement and one of the following must was not set (message ICU010I was not issued), rerun
be done. the entire job. Otherwise, use this listing to determine
v Reorganize the target CKDS to force more efficient which control statements were processed successfully.
space utilization. Then rerun the utility program using the CHGK function
to process the remaining control statements. Notify the
security administrator.

ICU1048 INCORRECT VALUE SPECIFIED ON

PARM CARD FOR OLD SYSTEM
MASTER KEY
Explanation: When attempting to change the host
master key (CHGM), the key generator utility
encountered a incorrect old host master key value in the
PARM field on the EXEC statement.
value of the old host master key in the EXEC statement
and rerun the key generator utility program.

Chapter 13. IDA Messages
keyword
IDA001 INVALID POSITIONAL PARAMETER,
The keyword.
prm - IGNORED
System Action: The system does not expand the
Explanation: The specified positional parameter is not
macro.
valid.
Application Programmer Response: This is probably
an error in the calling program. Correct the erroneous
prm Indicates the specified positional parameter. value. Submit the job again.
System Action: The system ignores the positional System Programmer Response: If the error recurs
parameter. The system expands the macro normally. and the program is not in error, search problem
an error in the calling program. Correct the positional
program listing, the assembly listing, and the source
parameter. Submit the job again.
input associated with the job.
System Programmer Response: If the error recurs
Source: DFSMSdfp
and the program is not in error, search problem
reporting data bases for a fix for the problem. If no fix Detecting Module: IDAMDVRP
IDA004 keyword KEYWORD NOT VALID FOR
input for the job.
EXECUTE FORM - IGNORED
Source: DFSMSdfp
Explanation: The indicated keyword is not valid for
Detecting Module: IDAMDVRP the execute form of the macro.
IDA002 keyword KEYWORD REQUIRED - NOT
keyword
SPECIFIED
The keyword.
Explanation: The caller omitted a required keyword.
System Action: The system ignores the keyword. The
In the message text: system expands the macro normally.
keyword Application Programmer Response: This is probably
The keyword. an error in the calling program. Remove the keyword
from the execute form of the macro. Specify the
keyword on the list form, which is referred to by the
macro.
execute form.
an error in the calling program. Provide the required
keyword and value. Submit the job again.
System Programmer Response: If the error recurs exists, contact the IBM Support Center. Provide the
and the program is not in error, search problem program listing, the assembly listing, and the source
reporting data bases for a fix for the problem. If no fix input associated with the job.
Source: DFSMSdfp
input for the job.
IDA005 INVALID OR DUPLICATE SUBLIST
Source: DFSMSdfp
ITEM FOR keyword KEYWORD, xxx
Explanation: The specified sublist item is not valid or
IDA003 INVALID VALUE, value, SPECIFIED FOR
is duplicated for the keyword.
keyword KEYWORD
Explanation: The value specified for the indicated
keyword was incorrect. keyword
The keyword.
xxx The name of the sublist item.
value The specified value.

System Action: The system does not expand the Source: DFSMSdfp
macro.
Application Programmer Response: This is probably IDA008 INCOMPATIBLE SUBLIST ITEMS. xxx
an error in the calling program. Correct the sublist item. AND yyy, FOR keyword KEYWORD
Resubmit the job.
Explanation: The sublist items specified for the
System Programmer Response: If the error recurs keyword are incompatible.
exists, contact the IBM Support Center. Provide the xxx
input for the job. yyy The specified sublist names.
Source: DFSMSdfp keyword

The keyword.
IDA006 keyword VALUE, value, NOT VALID FOR System Action: The system does not expand the
LIST FORM macro.
Explanation: The specified value for the keyword is Application Programmer Response: Remove one of
not valid for the list form of the macro. the incompatible sublist items. Run the job again.
In the message text: System Programmer Response: If the error recurs

keyword reporting data bases for a fix for the problem. If no fix
The keyword. exists, contact the IBM Support Center. Provide the
value The specified value.
input for the job.
Source: DFSMSdfp
macro.
IDA009 nnn CONTROL BLOCK KEYWORDS
an error in the calling program. Correct the erroneous
SPECIFIED - ONLY ONE ALLOWED
value. Submit the job again.
Explanation: The caller specified more than one
control block for a TESTCB macro. This is an error.
reporting data bases for a fix for the problem. If no fix In the message text:
program listing, the assembly listing, and the source nnn The number of control block keywords
input for the job. specified.
Source: DFSMSdfp System Action: The system does not expand the
macro.
IDA007 LOGIC ERROR IN MACRO mac Application Programmer Response: Remove all but
one of the control block keywords. Run the job again.
Explanation: The system detected a logic error in the
macro. System Programmer Response: If the error recurs
In the message text: reporting data bases for a fix for the problem. If no fix
mac The name of the macro.
System Action: The system does not expand the input for the job.
macro.
Source: DFSMSdfp
Application Programmer Response: Determine
where the error occurs in the macro. Correct the error.
IDA010 EXIT ADDRESS REQUIRED FOR
Run the job again.
keyword KEYWORD - NOT SPECIFIED
Explanation: An exit address required for the keyword
was not specified.
exists, contact the IBM Support Center. Provide the In the message text:
input for the job. keyword
The keyword.

System Action: The system does not expand the Source: DFSMSdfp
macro.
Application Programmer Response: Supply the IDA019 KEYWORDS keyword1 AND keywd2
required exit address. Run the job again. ARE INCOMPATIBLE
System Programmer Response: If the error recurs Explanation: The indicated keywords cannot be
and the program is not in error, search problem specified together.
program listing, the assembly listing, and the source keyword1
input for the job.
Source: DFSMSdfp keyword2
The specified keywords.
IDA011 keyword IS NOT A VALID xxx System Action: The system does not expand the
KEYWORD - IGNORED macro.
Explanation: The specified keyword is not valid for the Application Programmer Response: Correct the
control block. error by specifying compatible keywords. Run the job
again.
keyword
The keyword.
xxx The control block. exists, contact the IBM Support Center. Provide the
System Action: The system ignores the incorrect
input for the job.
keyword. The system expands the macro normally.
Source: DFSMSdfp
Application Programmer Response: Remove the
incorrect keyword. Run the job again. Detecting Module: IDA0192V
and the program is not in error, search problem IDA020 VTAM SUBLIST ITEM, xxx, SPECIFIED
reporting data bases for a fix for the problem. If no fix FOR keyword KEYWORD WITHOUT
exists, contact the IBM Support Center. Provide the SPECIFYING AM=VTAM
Explanation: The VTAM sublist item specified for the
input for the job.
keyword is not valid because AM=VTAM was not
Source: DFSMSdfp specified.
IDA018 VTAM KEYWORD, keyword, SPECIFIED
xxx The specified sublist item.
WITHOUT SPECIFYING AM=VTAM
keyword
Explanation: The specified VTAM keyword is not valid
The keyword.
because AM=VTAM was not specified.
macro.
keyword
Application Programmer Response: Specify
The keyword.
AM=VTAM. Run the job again.
macro.
Application Programmer Response: Either remove reporting data bases for a fix for the problem. If no fix
the incorrect keyword or specify AM=VTAM. Run the job exists, contact the IBM Support Center. Provide the
again. program listing, the assembly listing, and the source
input for the job.
and the program is not in error, search problem Source: DFSMSdfp
Detecting Module: IDA0200T
input for the job.
Chapter 13. IDA Messages 267

IDA021 keyword1 AND keywd2 KEYWORDS
MUST BE SPECIFIED TOGETHER BUT keyword
ONE IS MISSING The keyword.
Explanation: The keywords specified in the message System Action: The system does not expand the
text form a pair. One cannot be specified without the macro.
other.
In the message text: error by specifying a non-VSAM keyword. Run the job
again.
keyword1
keyword2
The keywords.
System Action: The system does not expand the program listing, the assembly listing, and the source
macro. input for the job.
Application Programmer Response: Supply the Source: DFSMSdfp
missing keyword or remove the one specified. Run the
job again.
IDA025 www, xxx, yyy CONFLICTING
System Programmer Response: If the error recurs SUBPARAMETERS IN keyword
and the program is not in error, search problem KEYWORD, www ASSUMED
Explanation: More than one subparameter was
specified for the indicated keyword. This is an error.
input for the job. In the message text:
Source: DFSMSdfp www
xxx
IDA022 CONFLICTING SUBLIST ITEMS WERE
SPECIFIED FOR keyword KEYWORD yyy The specified subparameters.
Explanation: The keyword was specified with keyword

conflicting sublist items. The keyword.
In the message text: System Action: The system expands the macro using
www as the default.
keyword
The keyword. Application Programmer Response: Specify one of
the conflicting subparameters for the keyword. Run the
System Action: The system does not expand the job again.
macro.
Application Programmer Response: Correct the and the program is not in error, search problem
sublist item or items that are in conflict. Run the job reporting data bases for a fix for the problem. If no fix
again. exists, contact the IBM Support Center. Provide the
input for the job.
reporting data bases for a fix for the problem. If no fix Source: DFSMSdfp
input for the job. IDA026 keyword1 CONFLICTS WITH keywd2.
keywd1 IGNORED.
Source: DFSMSdfp
Explanation: The meaning of the first keyword
specified either conflicts with or repeats the meaning of
IDA024 keyword, A VSAM KEYWORD the second keyword specified.
SPECIFIED FOR A NON-VSAM
CONTROL BLOCK In the message text:
Explanation: The specified keyword is a VSAM keyword1

keyword, but it is being specified for a non-VSAM
control block. keyword2
The specified keywords.

System Action: The macro expands, using keyword2.
Application Programmer Response: Remove one of
the keywords from the macro. Run the job again.
Source: DFSMSdfp
IDA027 ALL FOUR PARAMETERS: keyword1,

keywd2, keywd3, AND keywd4 MUST BE
SPECIFIED.
Explanation: The indicated keywords must be
specified in the macro.
System Action: The request ends unsuccessfully.
Application Programmer Response: Probable user
error. All of the listed keywords must be specified.
Check the spelling.
Source: DFSMSdfp
Detecting Module: IDAMDVRP
Chapter 13. IDA Messages 269

Chapter 14. IDC Messages
to the output data set. If the Access Method
IDC0001I FUNCTION COMPLETED, HIGHEST
Services Cryptographic Option Program
CONDITION CODE WAS cde
Product is installed and the ENCIPHER
Explanation: The system issues this message upon parameter of the REPRO command was
completion of any functional command. If an error has used, then the number includes one or more
occurred, the condition code is not 0. If an error has header records.
occurred, it will be indicated by error messages that
precede the completion message.
Source: DFSMSdfp
Detecting Module: IDCPR01
cde The highest condition code of the completed
function.
IDC0014I LASTCC=cde
System Action: The system sets the last condition
code (LASTCC) to cde. The system sets the maximum Explanation: The system issues this message when a
condition code (MAXCC) if cde is greater than the nonzero condition code is returned by any functional
current MAXCC value. command upon its completion. If the condition code is
greater than 0, error messages precede this message.
Source: DFSMSdfp
Detecting Module: IDCAL01, IDCBI01, IDCCC01,
IDCDE01, IDCDL01, IDCLC01, IDCLR01, IDCMP01, cde The condition code, as follows:
IDCPM01, IDCPR01, IDCRC01, IDCRM01, IDCRP01,
IDCRS01, IDCVY01, IDCXP01 4 Attention message. The system will
complete processing.
IDC0002I IDCAMS PROCESSING COMPLETE. 8 Serious error. The system completed

MAXIMUM CONDITION CODE WAS cde processing.
Explanation: The system issues this message at the 12 Abnormal error. The system
completion of the job. If an error occurred, the condition abnormally ends the command.
code is not 0. System Action: The system either completes or
In the message text: abnormally ends processing depending on the condition
code.
cde The highest condition code of the completed
job. Application Programmer Response: Determine the
cause of the error. Correct the error. Run the job again.
System Action: The system places the highest
condition code (MAXCC) set during the step in register Source: DFSMSdfp
15. Detecting Module: IDCAL01, IDCBI01, IDCCC01,
Source: DFSMSdfp IDCDE01, IDCDL01, IDCLC01, IDCMP01, IDCRM01,
IDCRS05, IDCVY01, IDCXP01
IDC0005I NUMBER OF RECORDS PROCESSED

WAS nnn IDC0018I MAXIMUM NUMBER OF CVOL
ENTRIES EXCEEDED
Explanation: The system issues this message to
indicate the number of records processed by the job. Explanation: Only 1455 CVOL entries may be
referenced.
System Action: JOB COMPLETES
nnn Depending on the command, nnn indicates the
following: User Response: None
v For the catalog reload function of the Operator Response: None

REPRO command, the number of records
read from the input data set.
v For EXPORT and all other REPRO and System Programmer Response: None
PRINT commands, the number of records Source: IDCAMS
written to the output data set. If input
records were selectively processed, the Detecting Module: IDCSA02
number includes only those actually written

If ADDV, MODIFYV, or STOREV abnormally ends
IDC0038I IDC0038I COMPRESSION INTERFACE
without indicating the status of the rename operation,
USED, DATA TRANSFER COMPLETE.
run LISTMSVI to determine if the volume is flagged
Explanation: This message may be issued after doing for recovery purposes. If the mismatch flag is set in
a REPRO of a compressed data set to another the volume record, LISTMSVI not only lists the
compressed data set and no decompress conditions standard information for the volume but also
were met. highlights the volume report with a note that a
rename operation failed for the preceding volume and
Source: IDCAMS
that the serial number is recorded in the volume label
Detecting Module: IDCRP01 of the volume.
v If a rename operation failed for MODIFYV, recover
IDC0061I CARTRIDGE csn EJECTED from a MODIFYV rename failure by:
– If the volume is inactive and has no volume serial
Explanation: Either a scratch cartridge or an old or mismatch condition, run ADDV to activate the
defective data cartridge was ejected from the Mass volume.
Storage Facility.
– If the volume is inactive and has a volume serial
In the message text: mismatch condition, run ADDV to activate the
volume and to complete the rename operation.
csn The cartridge.
– If the volume is active and has a mismatch
System Action: The command continues processing. condition, run MODIFYV to complete or retry the
Source: DFSMSdfp rename operation.
– If the volume is active and a duplicate volume
serial number is desired, run STOREV to
IDC0063I CARTRIDGE LABELS AND INVENTORY
complete or retry the rename operation.
RECORD RESTORED
Explanation: The system restored the cartridge labels
and Inventory data set to original status after an error
the job log for more information. Search problem
had been encountered while relabeling a Mass Storage
Volume.
exists, contact the IBM Support Center. Provide the job
System Action: The command continues processing. control language (JCL), the SYSOUT output, and all
output data sets related to the problem.
Application Programmer Response: Take the
following action for the command that failed: Source: DFSMSdfp
v If a rename operation failed for ADDV and if the Detecting Module: IDCAV01, IDCMV01
volume is inactive, run ADDV to back out or retry the
rename operation. If the volume is active, run
MODIFYV or STOREV to either back out or retry the IDC0064I text UPDATED IN CARTRIDGE LABELS
rename operation. AND INVENTORY RECORD
If the ADDV, MODIFYV, or STOREV commands are Explanation: text is one of the following:
run to recover from a rename failure, specify a DD SERIAL
statement for the volume with deferred mounting. OWNER
The values specified for the VOLUME and SERIAL, OWNER
NEWSERIAL parameters depend upon how the
volume record is recorded in the Inventory data set. If The volume serial number, the owner name, or both
the cartridge labels have been updated, the volume was updated in the label of the data cartridges assigned
record will be identified by the new volume serial to the Mass Storage Volume and in the volume record
number, as follows: in the Inventory data set. However, the data may not yet
be updated in the software volume label.
– For the VOLUME parameter, specify the volume
serial number as recorded in the cartridge labels System Action: The command continues processing.
and the volume record.
Source: DFSMSdfp
– For the NEWSERIAL parameter, specify the
desired volume serial number. Note that the Detecting Module: IDCAV01, IDCMV01, IDCSR01
security check for non-VSAM status and password
protected data sets is bypassed only if the
NEWSERIAL parameter specifies the same
volume serial number as recorded in the Inventory
data set for the volume label.

Operator Response: Remove the ejected cartridge or
IDC0068I nnn BACKUP COPIES EXIST BEYOND
cartridges from the cartridge access station of the Mass
MAXIMUM BACKUP
Storage Facility.
Explanation: The number of backup copies exceeds
Source: DFSMSdfp
the backup number specified through the use of the
CREATEV or MODIFYV command.
IDC0085I CARTRIDGES csn [csn] EJECTED
Explanation: The cartridges assigned to a Mass
nnn The number of backup copies that exceed the
Storage Volume were ejected from the Mass Storage
maximum.
Facility.
System Action: The command continues processing.
Application Programmer Response: The excess
msn The cartridge serial numbers of the sequence
backup copies are scratched by:
one and sequence two cartridges.
v The next COPYV command processed to create a
new backup copy. The oldest backup copies will be System Action: The system continues processing.
scratched. Source: DFSMSdfp
v Specify the SCRATCHV command for each backup
copy to be scratched. Detecting Module: IDCEV01, IDCCO01, IDCSR01
Source: DFSMSdfp
IDC0086I text UPDATED IN VOLUME LABEL
Detecting Module: IDCCO01, IDCMV01
Explanation: text is one of the following:
SERIAL
IDC0073I VOLUME ATTRIBUTES CHANGED TO OWNER
AGREE WITH GROUP grpname SERIAL, OWNER
Explanation: The attributes of a general use volume
were changed to match the attributes defined at the The volume serial number, the owner name, or both
group level for all general use volumes belonging to the was changed in the volume label.
group. If the caller did not explicitly request the attribute System Action: The command continues processing.
change, the attributes are changed implicitly because:
Source: DFSMSdfp
v The volume is being assigned to a different group
v A volume that does not belong to a group is being Detecting Module: IDCAV01, IDCMV01, IDCSR01
assigned to a group
v The group level attributes were changed while a IDC0088I CARTRIDGES csn [csn] SCRATCHED
general use volume was inactive and is now being FOR COPY yyddd
activated
Explanation: The cartridges assigned to the copy
System Action: The command continues processing. volume were successfully scratched. If only one
cartridge was in the Mass Storage Facility (MSF), the
Source: DFSMSdfp
single cartridge serial number identifies the sequence
Detecting Module: IDCAV01, IDCMV01 one or sequence two cartridge that was scratched. If
both cartridges were in the MSF, both cartridges were
scratched, and the cartridge serial numbers of the
IDC0083E csn [csn] EJECTED; VOL volser - sequence one and sequence two cartridges are listed.
jobname sss
Explanation: One or both cartridges assigned to the
Mass Storage Volume were ejected from the Mass csn The cartridge serial number.
Storage Facility.
yyddd The date on which the cartridges were
In the message text: scratched.
csn The cartridge serial number. System Action: The command continues processing.
volser The volume serial number. Source: DFSMSdfp
jobname Detecting Module: IDCCO01, IDCSV01

The jobname.
sss The stepname.
Chapter 14. IDC Messages 273

grpname
IDC0098I ** LOCATION OF VOLUME: location
The group name.
Explanation: The location information recorded in the
System Action: If any groups remain to be processed,
Inventory data set and assigned to the Mass Storage
the system continues processing with the next group.
Volume is listed. See the preceding message for the
Otherwise, the system abnormally ends the command.
cartridge serial numbers of these cartridges.
Source: DFSMSdfp
Detecting Module: IDCLD01, IDCSD01
location
The location in the Inventory data set.
IDC0106I NO ACTIVE GENERAL USE VOLUMES
System Action: The system abnormally ends the
IN GROUP grpname
command.
Explanation: Either there are no mass storage
Application Programmer Response: Insert the
volumes in the indicated group or there are no base
missing cartridges when the Mass Storage Volume
volume records in the Inventory data set that have the
Control portion of the Mass Storage System
active and general-use flags on.
Communicator is enabled. Run the command again. If
the cartridges assigned to the volume are lost, use the System Action: If any groups remain to be processed,
REMOVEVR command to delete the volume record the system continues processing with the next group.
from the Inventory data set before running the Otherwise, the system abnormally ends the command.
command again.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCRV01, IDCSV01
IDC0107I NO DATA SETS ELIGIBLE FOR

IDC0102I NO ACTIVE NON-GROUPED VOLUMES SELECTION ON VOLUME volser
IN THE INVENTORY DATA SET
Explanation: No data sets on the indicated volume
Explanation: There are no non-grouped, active mass met the criteria specified on the command for either
storage volumes in the inventory data set. listing or scratching.
System Action: The system abnormally ends the System Action: If there are more volumes to be
command. The system returns a reason code from the processed, the system processes the next volume.
Mass Storage Volume Control functions. Otherwise, the system abnormally ends the command.
Source: DFSMSdfp Source: DFSMSdfp
Detecting Module: IDCLD01, IDCSD01 Detecting Module: IDCLD01, IDCSD01
IDC0104I NO ACTIVE VOLUMES IN THE IDC0112I dsname SCRATCHED

INVENTORY DATA SET
Explanation: The data set was successfully scratched
Explanation: Either there are no base volume records from the volume table of contents (VTOC).
in the Inventory data set or there are no base volume
records with the active flag on in the Inventory data set. System Action: If other data sets remain to be
The Mass Storage Volume Control functions returned a scratched, the system continues processing with the
reason code of either X'208' or X'223'. next data set. Otherwise, the system abnormally ends
the command.
command. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCSD01

IDC0117I VOL volser IN GROUP grpname NOT
PROCESSED BY SIS
IDC0105I NO ACTIVE VOLUMES IN GROUP
grpname Explanation: The system-initiated scratch function
scheduled for processing an entry that indicated the
Explanation: Either there are no mass storage volume in a group. The entry was found:
volumes in the group or there are no base volume v when modifying the group status with the OFFT or
records with the active flag on in the group. OFFP parameter
In the message text: v when scratching the group scratch record

v when removing a volume from the group. System Action: The system maintains the passwords.
Application Programmer Response: Do not specify
passwords.
volser The volume serial number.
Source: DFSMSdfp
grpname
Detecting Module: IDCAL01, IDCDE01, IDCMP01
The group name.
System Action: The system continues processing;
IDC0181I construct USED IS constnme
however, the system does not process the volume.
Explanation: The Storage Management Subsystem
Application Programmer Response: Use the
(SMS) construct was specified in an access method
SCRDSET command as required to perform necessary
services DEFINE or IMPORT command. The construct
scratch processing for the volume. The volume is not
name was the construct actually used during processing
scheduled for system-initiated scratch processing.
of the command. The values for construct and
Source: DFSMSdfp constnme may be one of the following:
Detecting Module: IDCMV01, IDCSR01 v DATACLASS
v MANAGEMENTCLASS
IDC0140I ALIASES ARE NOT EXPORTED FOR v STORAGECLASS.

VSAM MASTER CATALOGS
For each specific command, the value of the construct
Explanation: An integrated catalog facility catalog is may differ from that of the construct name. Any
being exported, but its user catalog pointer entry is in a difference between the two constructs resulted from
virtual storage access method (VSAM) master catalog. automatic class selection processing.
Therefore, EXPORT will not export the aliases of this
integrated catalog facility catalog. In the message text:
System Action: The system continues processing with construct
the export of the integrated catalog facility catalog. The construct.
Source: DFSMSdfp constnme
The construct name.
IDC0144I VOLUME SERIAL FOR catname System Action: The system continues processing.
DURING EXPORT DISCONNECT WAS
volser Source: DFSMSdfp
Explanation: This is an informational message Detecting Module: IDCDE01, IDCMP01

indicating the volume serial number for the volume that
contains the catalog being disconnected. IDC0182I EXPIRATION DATE RESET TO yyyy.ddd
In the message text: Explanation: The system issues this message for one
catname of the following reasons:
The name of the catalog being disconnected. v The expiration date specified during an access
method services ALTER or DEFINE operation
exceeded the management class retention period.
System Action: The system continues processing. The system resets the date.
Source: DFSMSdfp v An alternate index (AIX) expiration date is being
overridden. For an SMS managed AIX, CATALOG
processing does not allow the expiration date to
IDC0180I PASSWORD SPECIFICATION FOR exceed that of the related cluster.
entrynme MAY BE INEFFECTIVE
System Action: The system uses the reset date
Explanation: During an access method services instead of the expiration date. For an AIX that does not
ALTER or DEFINE operation, the system found that one have a management class, the system sets the
or more passwords were specified. Since the object expiration date to that of the related cluster.
entry name is managed by the Storage Management
Subsystem (SMS), these passwords will be ineffective Application Programmer Response: If the reset date
for the protection of that object. is incorrect, change it by doing one of the following:
v By MANAGEMENTCLASS, specify a different
management class that allows the expiration date
entrynme originally specified
The entry name.

v By FOR or TO, specify an expiration date that does and the calling program is not in error, search problem
not exceed the management class retention period reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
SYSOUT output for the job.
Detecting Module: IDCAL01, IDCDE01
Source: DFSMSdfp
Detecting Module: IDCRI01
IDC0196I dsname HAS BEEN ROLLED OFF AND
action
IDC0222I WARNING: COMMAND-END DELIMITER
Explanation: Changing the maximum number of
APPEARS WITHIN APOSTROPHES
generation data sets (GDSs) that can be associated
with a generation data group (GDG) caused one or Explanation: The system found a semicolon, the
more of the GDSs to be rolled off. In addition to being optional command delimiter, in an item that is enclosed
rolled off, the GDS data set name was: within apostrophes. A closing apostrophe may have
v Recataloged as a non-VSAM data set been omitted.
v Uncataloged, but still exists
System Action: The system accepts the usage. The
v Deleted
system continues processing, treating the semicolon as
a valid character.
Application Programmer Response: Insert the
dsname
missing apostrophe, if one was omitted. Run the job
The data set name.
again.
action Indicates whether the GDS was recataloged,
uncataloged or deleted.
and the calling program is not in error, search problem
System Action: The system continues processing. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp SYSOUT output for the job.
Detecting Module: IDCAL01 Source: DFSMSdfp
IDC0204I PRECEDING COMMAND BYPASSED
DUE TO CONDITION CODES
IDC0233I TOO MANY RIGHT PARENTHESES
Explanation: The modal command structure FOUND. EXCESS IGNORED
specification caused the command to be bypassed.
Explanation: The system found too many right
System Action: The system checks the command for parentheses at the end of a subparameter list or
syntax errors. The system does not process the following a first-level parameter.
command.
System Action: The system ignores the excess
System Programmer Response: If the problem parameters. Scanning continues.
recurs and the program is not in error, search problem
reporting data bases for a fix for the problem. If no fix Application Programmer Response: Correct the
exists, contact the IBM Support Center. Provide the syntax of the parameters.
Source: DFSMSdfp and the calling program is not in error, search problem
Detecting Module: IDCRI03 exists, contact the IBM Support Center. Provide the
IDC0206I IMPROPERLY PLACED COMMA HAS Source: DFSMSdfp
BEEN FOUND AND IGNORED
Explanation: The caller coded an unnecessary
comma. Omitted positional parameters may not be
denoted by consecutive commas. IDC0234I WARNING: TOO FEW RIGHT
PARENTHESES FOUND AT END OF
System Action: The system accepts the usage and COMMAND
ignores the comma.
Explanation: The system found too few right
Application Programmer Response: Remove the parentheses at the end of the command to close off the
extra comma. subparameter lists.
System Programmer Response: If the error recurs System Action: The system accepts the usage. The

system continues processing. Application Programmer Response: Save the key
value for use when the data set is deciphered.
syntax of the parameters. Source: DFSMSdfp
System Programmer Response: If the error recurs Detecting Module: IDCIO01
IDC0361I ** dsname NOT LOCATED
SYSOUT output for the job. Explanation: The virtual storage access method
(VSAM) or OS locate request for the indicated data set
Source: DFSMSdfp
was unsuccessful. A preceding message indicates the
Detecting Module: IDCRI01 reason for the failure.
IDC0254I CANCEL COMMAND WAS EXECUTED
dsname
Explanation: An IDCAMS CANCEL command was The data set name.
issued to end the current job step. The step will be
System Action: If the SCRDSET command is being
ended with a return code in register 15 equal to the
run, this data set is not scratched. If the LISTDSET
value of the highest condition code encountered before
command is being run, this data set is listed unless the
the CANCEL command was run.
UNCATALOGED, EXPIRATIONDATE, EXPIRATION,
System Action: The system ends the job step. The CREATIONDATE, or CREATION parameter is specified.
remainder of the command stream is not processed.
Application Programmer Response: Determine why
Application Programmer Response: The maximum the data set was not located. Correct the problem if
condition code is returned in register 15 and will be necessary. Run the command again.
printed out on the IDCAMS completion message,
IDC0002I. Perform the programmer response from
message IDC0002I.
the job log for more information.
Source: DFSMSdfp
Issue the access method services LISTCAT command
to list catalog entries and information about objects
IDC0339I ENCIPHERED DATAKEY FOR keyname defined in the catalog.
IS keyval
Then search problem reporting data bases for a fix for
Explanation: The key value field provides information the problem. If no fix exists, contact the IBM Support
for the data encrypting key enciphered under the Center. Provide the JCL, and the SYSOUT output for
secondary file key whose external label is the key the job.
name.
Source: DFSMSdfp
Detecting Module: IDCSA07
keyname
The key name.
IDC0362I ** dsname NOT SCRATCHED
keyval The key value.
Explanation: An error occurred during a virtual
System Action: The system continues processing. storage access method (VSAM) delete request. The
error prevented the data set from being scratched. A
Application Programmer Response: Save the key
preceding message explains the type of error.
value for use when the data set is deciphered.
Source: DFSMSdfp
dsname
Detecting Module: IDCIO01
The data set name.
System Action: The command continues to scratch
IDC0342I PRIVATE DATA KEY IS keyval
and uncatalog remaining eligible data sets.
Explanation: The caller did not specify a private data
encrypting key. REPRO command processing provided
error identified in the preceding message and do one of
the data encrypting key.
the following:
In the message text: v Run the SCRDSET command again
keyval The key value. v Specify DELETE in the DISP parameter on the DD
statement to scratch the data set

v Run the DELETE command to scratch the data set v Specify DELETE in the DISP parameter on the DD
statement to scratch the data set.
and the program is not in error, look at the messages in v Run the DELETE command to scratch the data set.
the job log for more information. v Run the IEHPROGM utility to scratch and uncatalog
the data set.
Run the LIST service aid with the following control
statements: System Programmer Response: If the error recurs
v LISTOBJ: to obtain an object module listing and the program is not in error, look at the messages in
the job log for more information. Run the LIST service
v LISTLOAD OUTPUT=BOTH: to obtain a formatted
aid with the following control statements:
listing of the load module with its module map and
cross references v LISTOBJ: to obtain an object module listing
v LISTLOAD OUTPUT=BOTH: to obtain a formatted
If the error still exists, search problem reporting data listing of the load module with its module map and
bases for a fix for the problem. If no fix exists, contact cross references
the IBM Support Center. Provide the JCL and the
If the error cannot be determined, search problem
Source: DFSMSdfp exists, contact the IBM Support Center. Provide the
JCL, the SYSOUT output, and all printed output and
Detecting Module: IDCSA07 output data sets related to the problem.
Source: DFSMSdfp
IDC0363I ** dsname NOT UNCATALOGED
Explanation: One of the following situations occurred:
v An error occurred during a virtual storage access
method (VSAM) delete request. IDC0394I jobname.sss 3850 DEMOUNT FAILED,
VOL=vvvvvv,vua, RC=X'cde'
The error prevented the data set from being
uncataloged. Explanation: The system was unable to demount the
v An error occurred during an operating system (OS) virtual volume requested in the indicated step of the job.
uncatalog request. In the message text:
The error prevented the data set from being
jobname
uncataloged.
The jobname.
v An error occurred during the scratch of the data set.
sss The specified job step.
Because the data set cannot be scratched, no
attempt was made to uncatalog the data set. vvvvvv The virtual volume serial address.
vua The virtual unit address.
cde The failed reason code.
dsname
The data set name. System Action: The system continues processing.
System Action: The command continues to scratch Application Programmer Response: Correct the
and uncatalog remaining eligible data sets. The system problem indicated by the Mass Storage System (MSS)
explains the error with a preceding message. reason codes. Then issue the UNLOAD command.
Application Programmer Response: Correct the Source: DFSMSdfp
error identified in the preceding message. If the data set
Detecting Module: IDCSA06, IDCSA10
was already scratched from the volume table of
contents (VTOC), do one of the following:
v Specify UNCATLG in the DISP parameter on the DD IDC0396I ** dsname NOT RECATALOGED
statement to uncatalog the data set. Explanation: The data set was not recataloged. The
v Run the DELETE command to uncatalog the data system writes a preceding message that explains the
set. reason for the error.
v Run the IEHPROGM utility to uncatalog the data set. In the message text:
If the data set was not scratched from the VTOC, do dsname
one of the following: The data set name.
v Run the SCRDSET command again. System Action: The command continues processing.
Application Programmer Response: Examine the

preceding message for response. If the error cannot be determined, search problem
Source: DFSMSdfp
Detecting Module: IDCSA07 JCL, the SYSOUT output, and all printed output and
IDC0397I DATA SET CATALOGED IN VSAM Source: DFSMSdfp
CATALOG THAT DOES NOT OWN
VOLUME
Explanation: The data set identified in the subsequent
IDC0497E CARTRIDGE EJECTED; jobname,
message was located in a virtual storage access
stepname
method (VSAM) catalog that does not own the volume.
VSAM catalog management does not support altering Explanation: The system writes an informational
device type and volume serial number in VSAM message to the system operator, notifying him of the
catalogs other than the owning catalog. presence of a cartridge in the cartridge access station.
System Action: The command continues processing. In the message text:
Application Programmer Response: Use the access jobname
method services LISTCAT, DELETE, and DEFINE The jobname.
commands to determine the fields defined in the entry.
stepname
Delete the entry and redefine the entry with the new
The job step.
device type.
and the program is not in error, look at the messages in Operator Response: Remove the cartridge from the
the job log for more information. Issue the access cartridge access station.
method services LISTCAT command to list catalog
entries and information about objects defined in the Source: DFSMSdfp
catalog.
If the error cannot be determined, search problem IDC098D ACCESS REQUESTED TO text
reporting data bases for a fix for the problem. If no fix VOL=SER=volser: REPLY Y OR N text
exists, contact the IBM Support Center. Provide the Explanation: Processing of REPAIRV DISPLAY or
JCL, the SYSOUT output, and all printed output and REPAIRV COPY command requests authorization to
output data sets related to the problem. access a staging pack, or processing of the REPAIRV
Source: DFSMSdfp MODIFY command requests authorization to update the
volume table of contents (VTOC) or its header
Detecting Module: IDCSA07 (VTOCHEADER).
IDC0398I DATA SET RESIDES ON MORE THAN
TWENTY VOLUMES text STAGING PACK VTOCHEADER VTOC.
Explanation: The data set identified in the subsequent volser The volume serial number.
message resides on more than twenty volumes. It has System Action: Processing of the REPAIRV
not already been recataloged. Recataloging is not command waits for the operator to respond. If the
supported by this program if the data set resides on response is Y, the system continues processing. If the
more than 20 volumes. If the data set is cataloged in response is N, the system abnormally ends the
the virtual storage access method (VSAM) owning command.
catalog, it has already been recataloged.
Operator Response: Enter Y to allow access, or enter
System Action: The command continues processing. N to deny access.
Application Programmer Response: Use System Programmer Response: If the error recurs
IEHPROGM utility or access method services DELETE and the program is not in error, search problem
and DEFINE command to recatalog the data set if it is reporting data bases for a fix for the problem. If no fix
cataloged and not already recataloged. exists, contact the IBM Support Center. Provide the JCL
System Programmer Response: If the error recurs and the SYSOUT output for the job.
and the program is not in error, look at the messages in Source: DFSMSdfp
the job log for more information. Issue the access
method services LISTCAT command to list catalog Detecting Module: IDCRD07
entries and information about objects defined in the
catalog.

Detecting Module: IDCDE01
IDC0508I DATA ALLOCATION STATUS FOR
VOLUME volser IS return-code
IDC0511I SPACE ALLOCATION STATUS FOR
Explanation: The system indicates the allocation
status for a volume containing the data component. The
code indicating the status is the virtual storage access Explanation: The system indicates the allocation
method (VSAM) catalog return code. status for a volume on which virtual storage access
method (VSAM) space is being defined. The code
indicating the status is the VSAM catalog return code.
ser The volume serial number.
return-code The return code. A 0 indicates
success.
success.
IDC3009I for a complete explanation of the return code.
Source: DFSMSdfp
Detecting Module: IDCDE01, IDCMP01, IDCRM01
Source: DFSMSdfp
IDC0509I INDEX ALLOCATION STATUS FOR
IDC0512I NAME GENERATED - (x) dsname
status for a volume containing the index component. Explanation: Data and index component names are
The code indicating the status is the virtual storage generated by virtual storage access method (VSAM)
access method (VSAM) catalog return code. catalog management, when these names have not been
specified.
x Either a D or an I. It indicates which
component the data set names.
success.
dsname
The data set name.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCDE01, IDCMP01, IDCRM01
IDC0520I CATALOG RECOVERY VOLUME IS ser

IDC0510I CATALOG ALLOCATION STATUS FOR
VOLUME volser IS return-code Explanation: the system writes this message to
indicate the volume serial number of the volume that
contains and will contain all catalog recovery data for
status of a volume containing the virtual storage access
the object just defined.
method (VSAM) catalog. The code indicating the status
is the VSAM catalog return code. In the message text:
In the message text: ser The volume serial number.
ser The volume serial number. System Action: The system continues processing.
return-code The return code. A 0 indicates Application Programmer Response: Mount the
success. named volume for any future operation that modifies the
catalog entry for the object just defined.
Source: DFSMSdfp
IDC3009I for a complete explanation of the return code. Detecting Module: IDCDE01, IDCMP01, IDCRM01
Source: DFSMSdfp

system output indicates the reason the member name
IDC0526I ALTERED ALLOCATION STATUS FOR
was not renamed. The system continues processing.
Explanation: The system writes this message to
problem indicated by the previous message. Run the
indicate the allocation status of volumes being added or
command again.
removed from a virtual storage access method (VSAM)
data set. The code indicating the status is the VSAM Source: DFSMSdfp
catalog return code.
Detecting Module: IDCAL01
ser The volume serial number. IDC0535I MEMBER mem RENAMED
return-code The return code. See message Explanation: The indicated member has been
IDC3009I for an explanation of the successfully renamed.
return code.
mem The indicated member.
Source: DFSMSdfp
Source: DFSMSdfp
IDC0531I ENTRY xxx ALTERED Detecting Module: IDCAL01
Explanation: The system writes this message to

indicate that the specified entry has been successfully IDC0548I ** MEMBER mem NOT DELETED
altered. Explanation: The system writes this message to
In the message text: inform the operator or programmer that the member
was not deleted.
xxx The altered entry.
mem The indicated member.
Source: DFSMSdfp
System Action: An associated message accompanies
Detecting Module: IDCAL01 this message indicating why the member was not
deleted. The system continues processing.
IDC0532I ** ENTRY xxx NOT ALTERED Source: DFSMSdfp
Explanation: The system writes this message to Detecting Module: IDCDL01
indicate that the entry was not altered.
In the message text: IDC0549I MEMBER mem DELETED
xxx The unaltered entry. Explanation: The system writes this message to
indicate the member that has been successfully deleted.
System Action: The preceding message in the
system output indicates the reason the entry was not In the message text:
altered. The system continues processing.
mem The deleted member.
problem indicated by the previous message. Run the System Action: The system continues processing.
command again. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCDL01
IDC0550I ENTRY (x) dsname DELETED
IDC0534I ** MEMBER mem NOT RENAMED Explanation: The specified data set name entry was
Explanation: The system writes this message to deleted from the virtual storage access method (VSAM)
indicate the member name that was not renamed. catalog.
In the message text: In the message text:
mem The member name. dsname

The data set name.
System Action: The preceding message in the

x The type of entry, as follows: ser The volume serial number.
C--cluster
System Action: The volume is still owned by the
D--data
catalog in which it was originally defined.
G--alternate index
I--index Source: DFSMSdfp
R--path
V--volume Detecting Module: IDCDL01
U--user catalog
M--master catalog IDC0571I CATALOG RELOAD HAS BEEN
A--non-VSAM INVOKED
B--GDG base
X--alias Explanation: A REPRO command has been
processed where the target data set is a catalog. This
System Action: The system deletes a volume entry marks the beginning of processing of a catalog reload
only when the volume no longer contains any data operation.
spaces. The system uncatalogs, but does not delete, a
data set with indirect or extended indirect VolSer. The System Action: The system continues processing.
system continues processing. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCRP01
Detecting Module: IDCDL01, IDCMP01, IDCRM01,
IDCXP01 IDC0594I PORTABLE DATA SET CREATED
SUCCESSFULLY ON date AT hh:mm:ss
IDC0551I ** ENTRY dsname NOT DELETED Explanation: At this point, the portable data set
Explanation: The system writes this message to contains all information necessary to re-create the
indicate that the entry that was not deleted. An cluster being exported.
accompanying message will indicate why the entry was In the message text:
not deleted.
date The date of the data set creation.
hh:mm:ss
dsname The time of the data set creation in hours,
The data set name. minutes, and seconds.
System Action: The named data set is not deleted. System Action: The system continues processing.
cause of the error.
Detecting Module: IDCXP01
the job log for more information. IDC0603I CONNECT FOR USER CATALOG
dsname SUCCESSFUL
Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Explanation: This message identifies the name of the
Center. Provide the JCL and the SYSOUT output for the catalog for which CONNECT completed successfully.
job. In the message text:
Source: DFSMSdfp dsname
Detecting Module: IDCDL01, IDCXP01 The data set name.
IDC0555I DELETION OF SPACE OBJECT DID Source: DFSMSdfp
NOT CAUSE ser TO BE DELETED
Detecting Module: IDCMP01
Explanation: When a DELETE command is processed
against the volume serial number and the FORCE
parameter is not specified, all empty data spaces are IDC0604I DATA SET BEING IMPORTED WAS
deleted. Data spaces that still contain data set EXPORTED ON date AT hh:mm:ss
segments are not deleted. Only when all data spaces
Explanation: This message informs the caller of the
on a volume are deleted or when FORCE is specified,
date and time that the data set was exported.
is that volume deleted from its owning catalog.

date The date on which the data set was exported.
IDC0634I NUMBER OF ENTRIES CONVERTED
hh:mm:ss WAS nnn
The time at which the data set was exported,
Explanation: The number of catalog entries
in hours, minutes, and seconds.
successfully converted into entries in the virtual storage
System Action: The system continues processing. access method (VSAM) or the integrated catalog facility
(ICF) catalog is indicated. All base entries and their
Source: DFSMSdfp associations are counted. Data and index component
Detecting Module: IDCMP01, IDCRM01 entries are not counted.
IDC0611I DATA SET TO BE IMPORTED nnn The number of entries converted.
ALREADY EXISTS - DELETE
ATTEMPTED System Action: The system continues processing.
Explanation: A catalog define was attempted for the Source: DFSMSdfp
data set to be imported. The command failed because
Detecting Module: IDCCC01
an entry with that name already existed in the catalog.
This situation occurs when a temporarily exported data
set is imported back into the catalog from which it was IDC0635I ** dsname NOT CONVERTED
exported.
Explanation: During CNVTCAT processing, the
System Action: An attempt is made to delete the catalog entry data set was not converted.
existing entry. The message following this message in
the listing indicates whether the delete was successful.
dsname
Source: DFSMSdfp
The data set name.
System Action: An associated message contains the
information required to correct the error. The system
IDC0622I USERCATALOG catname continues processing with the next entry.
DISCONNECTED
Source: DFSMSdfp
Explanation: A caller’s catalog has been disconnected
by IMPORTRA in order to connect a new pointer to the
user catalog.
IDC0636I NUMBER OF ENTRIES UPDATED WAS
nnn
catname
Explanation: The number of non-virtual storage
The catalog name.
access method (VSAM) entries whose volume
System Action: The system continues processing. information has been updated is indicated. Volume
information of a non-VSAM entry is updated when the
Source: DFSMSdfp
volume information of a duplicate entry being converted
Detecting Module: IDCRM01 from the operating system (OS) source catalog is
different from that of the existing non-VSAM entry.
IDC0626I IMPORTRA SUCCEEDED FOR dsname In the message text:
Explanation: The data set has been successfully nnn The number of entries updated.
imported.
Source: DFSMSdfp
dsname
The data set name.
System Action: Normal processing continues.
IDC0637I ** dsname NOT UPDATED
Source: DFSMSdfp
Explanation: The operating system (OS) catalog entry
Detecting Module: IDCRM01 specified was not converted.
dsname
The data set name.

System Action: An accompanying message contains
IDC0659I SORT PRODUCT MESSAGE DATA SET
the information required to correct the error. The system
NOT ALLOCATED: REASON CODE IS
continues processing.
reason-code
Source: DFSMSdfp
Explanation: DFSORT (or an equivalent product) was
Detecting Module: IDCCC01 unable to allocate the DFSORT (or equivalent product)
message data set.
IDC0639I SPHERE CONVERSION STARTED FOR In the message text, reason-code is:
dsname
04 Allocation failed
Explanation: The conversion of the specified base
08 Insufficient virtual storage to perform allocation
sphere and its associations has started.
System Action: BLDINDEX will process the command
using DFSORT (or an equivalent product) but no
dsname messages will be written to the DFSORT (or equivalent
The data set name. product) message data set.
System Action: The system continues processing. Application Programmer Response: For reason
code 04, supply a DD statement for the DFSORT (or
Source: DFSMSdfp equivalent product) message data set (see the
Detecting Module: IDCCC01 SORTMESSAGEDD parameter).
For reason code 08, increase the virtual storage region
IDC0652I dsname SUCCESSFULLY BUILT size and resubmit the job.
Explanation: Building of the alternate index identified Detecting Module: IDCBI01

by the data set name has been successfully completed
with no errors encountered. IDC0665I NUMBER OF ENTRIES THAT
In the message text: MISCOMPARED IN THIS CRA - nnn
dsname Explanation: The COMPARE option was requested

The data set name. and this informational message indicates the number of
entries for which a miscompare between the catalog
System Action: The system continues processing. recovery area (CRA) and catalog occurred. The types of
Source: DFSMSdfp entries are as follows:
v Volume
Detecting Module: IDCBI01 v Cluster
v Alternate index
IDC0657I REQUIRED SORT PRODUCT v non-virtual storage access method (VSAM)
FUNCTIONS UNAVAILABLE v user catalog entries
Explanation: DFSORT (or an equivalent product) with In the message text:

the functions required for BLDINDEX was not available.
nnn The number of entries miscompared.
System Action: The system stops processing the
command. System Action: The system continues processing.
System Programmer Response: Correct the error as Application Programmer Response: Determine
indicated in the preceding messages if they exist. If no whether recovery is required.
preceding messages exist, check the DFSORT (or Source: DFSMSdfp
equivalent product) message data set for detailed
information on the cause of the failure. If Detecting Module: IDCLR01
SORTMESSAGELEVEL(ALL) was specified use the call
identifier to find the set of DFSORT (or equivalent IDC0669I EXPORTING FROM CRA ON VOLUME
product) messages for this call (see IDC01850I and volser
DFSORT message ICE200I or the appropriate message
for an equivalent product), and correct the DFSORT (or Explanation: This message indicates the current
equivalent product) error that caused the failure. catalog recovery area (CRA) and volume being used to
export the data sets named in the following messages.
Detecting Module: IDCBI01

Source: DFSMSdfp Detecting Module: IDCRC01
Detecting Module: IDCRC01
IDC0680I VOLUME volser CREATED ON
CARTRIDGES csn1 csn2
IDC0670I DATA SET SUCCESSFULLY EXPORTED
Explanation: A new volume was created.
Explanation: The data set named in message
IDC0674I was successfully retrieved and written to the In the message text:
portable data set.
csn1
Source: DFSMSdfp
csn2 The cartridge serial numbers.
Source: DFSMSdfp
IDC0672I ** LOCKED ON CATALOG catname
Detecting Module: IDCCV01
Explanation: This message provides the name of the
owning catalog whose catalog recovery areas (CRA) will
be processed. It is the name of the catalog owning the IDC0686I PARTIALLY CREATED VOLUME volser
first CRA processed. SCRATCHED
In the message text: Explanation: The partially created volume was
scratched during back out because an error occurred.
catname
The catalog name. In the message text:
System Action: The system continues processing. volser The volume serial number.
Source: DFSMSdfp System Action: The command ends normally.
Detecting Module: IDCRC01 Application Programmer Response: Correct the
error indicated in a preceding message. Run the
command again.
IDC0674I ** NAME IS dsname
Source: DFSMSdfp
Explanation: This second-level message gives the
data set name of the object referred to in the preceding Detecting Module: IDCCV01
messages.
In the message text: IDC0703I ** VOL volser COPIES TO CART csn1
csn2, DATE yyddd
dsname
The data set name. Explanation: The volume was copied to the cartridges
on the date indicated.
System Action: See the primary message.
Application Programmer Response: See the primary
message. volser The volume serial number.
Source: DFSMSdfp csn1
Detecting Module: IDCRC01 csn2 The cartridge serial numbers.
yyddd The date, in year and days.
IDC0676I PORTABLE DATA SET CREATED
SUCCESSFULLY ON date AT time System Action: The system continues processing.
Explanation: This message indicates the portable Source: DFSMSdfp

data set contains the necessary information to recreate Detecting Module: IDCCO01
the data sets by IMPORTRA.
In the message text: IDC0704I ** CARTRIDGES OF OLDEST BACKUP
date Date on which data set was created. COPY yyddd SELECTED FOR REUSE
time Time at which data set was created. Explanation: The COPYV command selected the
cartridges of the oldest backup copy volume indicated
System Action: The system continues processing. by the date for reuse. The preceding message
describes the status of the new copy volume.
Source: DFSMSdfp

In the message text: Application Programmer Response: Run the
MODIFYV command to change the volume attributes or
the volume serial number of the active volume.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCAV01
Detecting Module: IDCCO01
IDC0724I ** SERIAL NUMBER OF VOLUME volser
IDC0705I ** CARTRIDGES OF AN INCOMPLETE NOT CHANGED
COPY VOLUME SELECTED FOR
Explanation: The volume has been activated but the
REUSE
volume serial number could not be changed. See the
Explanation: Due to a previous failure by the COPYV preceding message for further explanation of the error.
command, the cartridges of an incomplete copy volume
were reused by the command. The preceding message
identifies the status of the new copy volume. volser The volume serial number.
System Action: The system continues processing. System Action: The system continues processing.
Source: DFSMSdfp Application Programmer Response: Run the
MODIFYV command to change the volume serial
number of the active volume. Correct the problem as
indicated in the preceding message.
IDC0711I ** VOLUME volser1 RESTORED FROM
Source: DFSMSdfp
COPY VOLUME volser2, COPY DATE
yyddd Detecting Module: IDCAV01
Explanation: The designated volume was successfully
restored using either the latest backup copy or a user IDC0725I READWRITE ATTRIBUTE SET FOR
designated copy created on the date indicated. VOLUME volser
However, if the target volume serial number is different
Explanation: The volume is assigned the readwrite
than the copy volume, the target volume serial number
attribute as requested.
was overwritten during the copy operation and must be
restored. The target volume is currently flagged as an In the message text:
incomplete copy in the Inventory data set. The
command restores the volume label and clears the volser The volume serial number.
incomplete copy flag from the Inventory data set before System Action: The system continues processing.
processing of the command ends.
Source: DFSMSdfp
volser1 The volume serial number of the restored
volume.
IDC0731I VOLUME volser HAS BEEN MADE
volser2 The volume serial number of the restoring INACTIVE
volume.
Explanation: The designated volume was successfully
yyddd The date, in year and days. deactivated and made nonmountable.
System Action: The system continues processing. In the message text:
Source: DFSMSdfp volser The volume serial number.
Detecting Module: IDCRV01 System Action: The system continues processing.
Source: DFSMSdfp
IDC0722I VOLUME volser HAS BEEN ACTIVATED
Detecting Module: IDCSR01
Explanation: The inactive volume was made active
but either the volume attributes could not be updated or
the volume serial could not be changed. IDC0733I VOLUME LABEL RESTORED TO
ORIGINAL STATUS
Explanation: The volume label is restored to its
volser The volume serial number. original status because the volume cannot be
System Action: The system continues processing. deactivated or the volume serial number changed in the
cartridge labels. A flag in the Inventory data set,

indicating a mismatch between the volume label and volume is active and if a duplicate volume serial
cartridge labels, will remain set only if the flag was number is desired as a result of the rename.
previously set from an earlier relabel failure by:
v The MODIFYV command For the DD statement requirements, the proper
v The ADDV command VOLUME and NEWSERIAL parameter values, and
v The STOREV command use of LISTMSVI, refer to the description above for
an ADDV rename failure.
System Action: The command abnormally ends with
an error message. v For a Rename Operation failure for STOREV, run
STOREV again or run MODIFYV to either backout or
Application Programmer Response: Take one of the retry the rename operation.
following actions for the command that failed:
For the DD statement requirements, the proper
v For a Rename operation failure for ADDV, run ADDV VOLUME and NEWSERIAL parameter values, and
to backout or retry the rename operation if the use of LISTMSVI, refer to the description above for
volume is inactive. If the volume is active, run an ADDV rename failure.
MODIFYV or STOREV to either backout or retry the
rename operation. System Programmer Response: If the error recurs
If the ADDV, MODIFYV, or STOREV commands are
run to recover from a rename failure, a DD statement
for the volume is required and must specify deferred
mounting.
JCL, the SYSOUT output for the job, and all printed
The values specified for the VOLUME and output and output data sets related to the problem.
volume record is recorded in the Inventory data set. If Source: DFSMSdfp
the cartridge labels have been updated, the volume Detecting Module: IDCSR01
record will be identified by the new volume serial
number. For the VOLUME parameter, specify the
volume serial number as recorded in the cartridge IDC0737I FURTHER PROCESSING TERMINATED
labels and the volume record. For the NEWSERIAL
Explanation: An error occurred which prevents any
parameter, specify the desired volume serial number.
further processing. Preceding messages indicate the
Note that the security check for non-VSAM status
extent of the processing which has been completed.
and password protected data sets is bypassed only if
Functions which may not be completed are:
the NEWSERIAL parameter specifies the same
volume serial number as recorded in the Inventory v Updating the alternate track information in the volume
data set for the volume label. This allows the original table of contents (VTOC) of the TO volume.
volume serial number of a VSAM volume to be v If the volume is virtual storage access method
restored if the volume is left partially renamed. (VSAM), updating the time stamp in the VTOC of the
If ADDV, MODIFYV, or STOREV terminates without TO volume.
indicating the status of the rename operation, v If the FROM and TO volume serial numbers are
LISTMSVI can be run to determine whether the different, updating the serial number in the label of
volume is flagged for recovery purposes. If the the TO volume.
mismatch flag is set in the volume record, LISTMSVI v Updating the owner in the label of the TO volume.
not only lists the standard information for the volume
v If a recatalog option was specified or defaulted to,
but also highlights the volume report with a note that
recataloging the data sets.
a rename operation failed for the preceding volume
and that serial number ‘nnnnnn’ is recorded in the v If the scratch option was specified or defaulted to,
volume label of the volume. scratching the data sets on FROM volume.
v For a Rename Operation failure for MODIFYV, For conversion from a 3336 Model 1 Disk Pack to a
recover by: mass storage volume the incomplete copy flag is set
in the Inventory data set for any of the following
– Run ADDV to activate the volume if the volume is
cases:
merely inactive and has no volume serial
mismatch condition v The FROM and TO volume serial numbers are not
the same, and processing ended during the copy
– Run ADDV to both activate the volume and
operation.
complete the rename operation if the volume is
both inactive and has a volume serial mismatch v The FROM and TO volume serial numbers are not
condition the same, and processing ended before the VTOC
and volume label were updated.
– Run MODIFYV again to complete or retry the
rename operation if the volume is active but has a v The TO volume is VSAM and processing ended
mismatch condition, or 4) run STOREV to before the VSAM recataloging was completed.
complete or retry the rename operation if the

System Action: The command abnormally ends with System Action: The command continues processing.
an error message indicating the severity of the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01
incomplete copy flag is on in the Inventory data set, run
the CONVERTV command again. Recover from a copy
volume using the RECOVERV command, or scratch the IDC0748I ELIGIBLE NON-VSAM DATA SETS
Mass Storage Volume using the SCRATCHV command. SUCCESSFULLY RECATALOGED
Otherwise, decide whether to run the CONVERTV
command again or complete the functions not Explanation: The data sets not in the virtual storage
performed by CONVERTV using other access method access method (VSAM) owning catalog have been
services commands or utility programs. The owner in recataloged if there were any that needed to be
the volume label can be updated by the MODIFYV recataloged.
command for Mass Storage Volumes. Data sets can be System Action: The command continues processing.
recataloged using access method services DELETE and
DEFINE commands or IEHPROGM utility. Data sets can Source: DFSMSdfp
be scratched using the access method services Detecting Module: IDCCN01
DELETE command or IEHPROGM utility.
System Programmer Response: If the error recurs IDC0749I VTOC OF FROM VOLUME SCRATCHED
the job log for more information. Search problem Explanation: The volume table of contents (VTOC) of
reporting data bases for a fix for the problem. If no fix the source volume was successfully scratched.
exists, contact the IBM Support Center. Provide the System Action: The command continues processing.
output and output data sets related to the problem. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCCN01
IDC0751I CARTS csn1 csn2 SCRATCHED FOR
VOLUME volser
IDC0743I FROM VOLUME COPIED TO THE TO
VOLUME Explanation: The requested volume was scratched.
The cartridge IDs in the message are in reverse order
Explanation: The source volume was successfully from the order in which they were scratched.
copied to the target volume.
Source: DFSMSdfp
csn1
csn2 The cartridge serial numbers of the cartridges
that were scratched.
IDC0746I DATA SETS IN VSAM CATALOG
SUCCESSFULLY RECATALOGED System Action: The command continues processing.
Explanation: Data sets in the virtual storage access Source: DFSMSdfp
method (VSAM) catalog owning the volume have been
Detecting Module: IDCSV01
successfully recataloged.
IDC0760I RECORD FOR COPY yyddd REMOVED
Source: DFSMSdfp
Explanation: The copy record created on the date
Detecting Module: IDCCN01 indicated was removed from the Inventory data set.
IDC0747I VTOC AND LABEL OF TO VOLUME
UPDATED
Explanation: The converted volume now has the
appropriate alternate track information and virtual Source: DFSMSdfp
storage access method (VSAM) time stamp in the
Detecting Module: IDCRR01
volume table of contents (VTOC). The converted
volume now has the appropriate owner and volume
serial number in the label.

IDC0763I RECORD FOR VOLUME volser IDC0790I CARTRIDGE csn1 REPLACED BY
REMOVED CARTRIDGE csn1
Explanation: A base volume record for the indicated Explanation: An old or defective cartridge of a Mass
volume was removed from the Inventory data set. Storage Volume has been replaced by a scratch
cartridge selected by the user or at random by the Mass
Storage Controller (MSC). The data on the old or
volser The volume serial number. defective cartridge has been copied to the new
cartridge.
Source: DFSMSdfp
csn1 The cartridge serial number of the replaced
Detecting Module: IDCRR01 cartridge.
csn2 The cartridge serial number of the replacing
IDC0780I SCRATCH CARTRIDGE csn EJECTED cartridge.
Explanation: A scratch cartridge was ejected from the System Action: The system continues processing.
Mass Storage Facility (MSF).
Source: DFSMSdfp
Detecting Module: IDCRL01
csn The cartridge serial number.
System Action: The system continues processing. IDC0791E REPLACED CARTRIDGE
Source: DFSMSdfp {csn|UNIDENTIFIED} EJECTED; jjj sss
Detecting Module: IDCEC01 Explanation: The cartridge serial number identifies an

ejected cartridge. An old or defective cartridge of a
Mass Storage Volume is ejected from the Mass Storage
IDC0781I NUMBER OF SCRATCH CARTRIDGES Facility (MSF) after being replaced with a different
EJECTED IS nnn cartridge. The jobname and the stepname identify the
Explanation: A number of scratch cartridges were job associated with the ejected cartridge.
ejected successfully from the library. If the cartridge was ejected, the replacement failed and
In the message text: the system failed to read the base volume record. The
cartridge serial number could not be identified.
nnn The number of scratch cartridges ejected. Messages IDC2080I and IDC2400I will follow this
System Action: The system continues processing. message indicating that the base volume could not be
read.
Source: DFSMSdfp
Detecting Module: IDCEC01
csn The cartridge serial
number.
IDC783E SCRATCH CARTRIDGE csn EJECTED;
jjj sss UNIDENTIFIED The cartridge serial
number could not be
Explanation: A scratch cartridge was ejected from the identified.
Mass Storage Facility (MSF).
jjj The jobname.
sss The job step.
jjj The jobname.
Operator Response: Remove the cartridge from the
sss The job step. Cartridge Access Station and label it as an old or
defective cartridge.
Source: DFSMSdfp
Operator Response: Remove the scratched cartridge
from the Cartridge Access Station and label it as a
scratch cartridge. IDC0810I VOLUME volser BEING PROCESSED
Source: DFSMSdfp Explanation: A new volume is being processed.
Messages follow to indicate the data sets on the volume
that are scratched.

In the message text: Source: DFSMSdfp
ser The volume serial number. Detecting Module: IDCSD01
System Action: The system begins processing of data
sets on the volume. IDC0814I nnn CATALOGED MULTI-VOLUME
DATA SETS WERE NOT SCRATCHED
Source: DFSMSdfp
Explanation: The number of cataloged multivolume
Detecting Module: IDCSD01
data sets that were not scratched is specified. The
SCRDSET command does not scratch multivolume
IDC0811I dsname UNCATALOGED cataloged data sets.
Explanation: The data set entry was successfully In the message text:
removed from the catalog.
nnn The number of multi-volume data sets that
In the message text: were not scratched.
dsname System Action: The system continues processing with

The data set name. the next volume.
System Action: The system continues processing. Application Programmer Response: If the data sets
must be scratched, use one of the following methods to
Source: DFSMSdfp scratch them:
Detecting Module: IDCSD01 v Run the IEHPROGM utility.
v Run the DELETE command.
v Specify DELETE in the DISP parameter of the DD
IDC0812I nnn DATA SETS WERE SCRATCHED statement.
FROM VOLUME volser
Source: DFSMSdfp
Explanation: The number of data sets scratched from
the indicated volume is specified. Detecting Module: IDCSD01

IDC0815I VOLUME volser IN GROUP grpname
nnn The number of the data sets scratched. BEING PROCESSED
ser The volume serial number. Explanation: A new volume in the indicated group is
System Action: The system continues processing. being processed. Additional messages follow to indicate
the data sets that have been scratched, if any.
Source: DFSMSdfp
Detecting Module: IDCSD01
IDC0813I nnn CATALOGED GDG TYPE DATA grpname

SETS WERE NOT SCRATCHED The group name.
Explanation: The number of cataloged generation System Action: The system processes the volume.
data group (GDG) type data sets that were not Source: DFSMSdfp
scratched is specified. The SCRDSET command does
not scratch cataloged data sets with names that end in Detecting Module: IDCSD01
name.GnnnnVnn.
In the message text: IDC0816I SYSCTLG DATA SET NOT SCRATCHED
nnn The number of the data sets that were not Explanation: The PURGE parameter was not
scratched. specified on a SCRDSET command and an OS system
or control volume (CVOL) catalog data set SYSCTLG
System Action: The system continues processing with met the limiting criteria for data set scratching. Data set
the next volume. SYSCTLG was not scratched.
Application Programmer Response: If the data sets System Action: The system continues processing with
must be scratched, use one of the following methods to the next volume.
scratch them:
v Run the IEHPROGM utility. Application Programmer Response: If the SYSCTLG
v Run the DELETE command. data set must be scratched, use the IEHPROGM utility
v Specify DELETE in the DISP parameter on the DD or run the SCRDSET command with the PURGE
statement. parameter.

Source: DFSMSdfp
IDC0861I NO TAPE DATA SETS OPEN FOR THIS
Detecting Module: IDCSD01 CHECKPOINT
Explanation: No type 1 DSDRs were found for this
IDC0817I ALL ACTIVE VOLUMES IN GROUP checkid.
grpname WERE EXCLUDED
System Action: Normal processing continues, but the
Explanation: No volumes were processed in the checkpoint is not processed.
specified group. Each active volume that normally would
Source: DFSMSdfp
have been processed was excluded with the
EXCLUDEVOLUMES parameter. Detecting Module: IDCCK01
IDC0862I DUPLICATE SELECTED CHECKID
grpname
xxxxxxxx
The group name.
Explanation: The same checkid was selected by the
System Action: If any groups remain to be processed,
user more than once.
the system continues processing with the next group. If
no groups remain to be processed, the system In the message text:
abnormally ends the command.
xxxxxxxx
Source: DFSMSdfp The duplicated check identification.
Detecting Module: IDCSD01 System Action: Normal processing continues, but the
checkpoint is not processed.
IDC0832I NO text RECORDS EXIST IN THE Application Programmer Response: Check to see if
INVENTORY another checkid was intended. Run the job again.
Explanation: text is one of the following: Source: DFSMSdfp
BASE VOLUME
Detecting Module: IDCCK01
DUPLICATE VOLUME
NON—GROUPED VOLUME
CARTRIDGE INDEX IDC0863I DUPLICATE CHECKPOINT ENTRY
PLACE HOLDER xxxxxxxx
GROUP SCRATCH
GROUP CATALOG Explanation: A duplicate entry was found for a
user-selected checkid already.
No records of the type requested exist in the inventory. In the message text:
System Action: The system continues processing. xxxxxxxx
The duplicated checkpoint entry.
Source: DFSMSdfp
Detecting Module: IDCLV01
Source: DFSMSdfp
ICBVUT02
IDC0855I CHANGE OF prm SUCCESSFUL
IDC0874I FOLLOWING NOT ALPHABETIC -
Explanation: The specified TUNE command
INSUFFICIENT WORK SPACE FOR
parameter was successfully changed.
SORT
Explanation: Insufficient virtual storage is available for
prm The specified parameter. alphabetically sorting the objects to be listed by a
LISTCRA command.
System Action: The system does not sort the objects.
Source: DFSMSdfp
The system lists the objects in the order in which they
Detecting Module: IDCTU01 are encountered while reading the catalog recovery
area.
Application Programmer Response: If a sorted
listing is desired, run the job with a larger storage
allocation.
Source: DFSMSdfp

Detecting Module: IDCLR01 System Action: The system ignores the dump
element.
IDC0877I NUMBER OF RECORDS THAT Application Programmer Response: Correct the
MISCOMPARED IN THIS CRA - nnn length and/or type of the specified dump element.
Explanation: The COMPARE option found a number Source: DFSMSdfp
of records for which a miscompare between the catalog
Detecting Module: IDCDB02
recovery area (CRA) and the catalog occurred.
IDC0923I ‘xxx’ ARRAY HEADER INVALID FOR
nnn The number of records miscompared. SYMBOLIC DUMP
System Action: The system continues processing. Explanation: The specified array header in a symbolic
dump list:
Application Programmer Response: Determine
whether recovery is required. v Has an incorrect extent field. The field must be
greater than 0 and less than or equal to 99.
Source: DFSMSdfp
v Has an incorrect item count field. The field must be
Detecting Module: IDCLR01 greater than 0.
v Is an array header within an existing array
IDC0888I ** ENTRY CONTAINS NO DATA specification.
RECORDS
The condition code remains unchanged.
Explanation: There are no data records in the virtual
storage access method (VSAM) data set to be exported. System Action: The system ignores the array header.
See the primary message for the name of the data set. Dump elements within the array specification are treated
as single, non-arrayed items.
System Action: Processing of catalog information only
for this data set is attempted. See the primary message Application Programmer Response: Correct the
for processing result. If processing was successful, then fields of the specified array header.
the portable data set contains the necessary information Source: DFSMSdfp
to redefine the data set through IMPORTRA.
Detecting Module: IDCDB02
Source: DFSMSdfp
Detecting Module: IDCRC01 IDC0924I DUMP ROUTINE INVOKED AT ‘mac’
Explanation: The access method services dump
IDC0896I MIGRATED ENTRY dsname DELETED routine has been invoked at the specified UDUMP
Explanation: The migration utility deleted the specified macro, a dump entry point.
data set. In the message text:
In the message text: mac The macro entry point.
dsname System Action: The system provides a dump of the
The data set name. IDCAMS trace tables, as well as symbolic and/or full
System Action: The system continues processing. region dumps, if requested by the IDCAMS user.
Detecting Module: IDCDL01 Detecting Module: IDCDB01
IDC0922I ‘xxx’ DUMP ELEMENT INVALID FOR IDC0925I DUMP xxx PRODUCED AT DUMP
SYMBOLIC DUMP POINT ‘mac’
Explanation: The specified dump element in a Explanation: A dump was requested and produced at
symbolic dump list has an incorrect type field or the the specified UDUMP macro.
length field is incorrect for the specified type. The In the message text:
condition code remains unchanged.
xxx The dump identifier.
mac The macro entry point.
xxx The specified dump element.
Source: DFSMSdfp

Detecting Module: IDCDB01 not be corrected. If the volume is a real volume, use the
AMASPZAP service aid to place the information from
the subsequent message into the VTOC.
IDC0932I STORAGE MANAGEMENT
SUBSYSTEM CALL FAILED. RETURN Source: DFSMSdfp
CODE WAS rc
Detecting Module: IDCVS01
Explanation: The subsystem interface was unable to
complete successfully the call to the storage
IDC0974I ** LAST USE DATE NOT CHANGED
management subsystem (SMS).
FOR DATA SET(S) ON VOLUME volser
Register 15 contains a hexadecimal reason code that
Explanation: An attempt to set or clear the
explains the error:
date-last-used field for one or more data sets failed on
Code Explanation the indicated volume. This message is preceded by a
message that specifies the error.
04 SMS does not support the requested function.
16 The function was not completed because of an
error. volser The volume serial number.
System Action: The system continues processing. System Action: The system continues processing.
Source: DFSMSdfp Application Programmer Response: Correct the
error specified in the previous message. Run the
command again to set or clear the date-last-used field.
System Programmer Response: Run the IEHLIST
utility:
SUBSYSTEM EXISTS, BUT IS NOT
OPERATIONAL. v With LISTVTOC FORMAT: to format and show the
volume table of contents (VTOC) for the volume
Explanation: The call to the storage management associated with the problem
subsystem (SMS) was unsuccessful because the
v With LISTVTOC DUMP: to list the VTOC for the
subsystem is not operational.
associated volume
System Action: The system continues processing. v With LISTPDS: to list the directory of the partitioned
Source: DFSMSdfp data set (PDS) associated with the problem
Detecting Module: IDCSA11 If the error recurs and the program is not in error,
search problem reporting data bases for a fix for the
IDC0935I STORAGE MANAGEMENT problem. If no fix exists, contact the IBM Support
SUBSYSTEM DOES NOT EXIST. Center. Provide the JCL, the SYSOUT output for the
job, and all printed output and output data sets related
Explanation: The system does not recognize the to the problem.
storage management subsystem (SMS) as a valid
subsystem. Source: DFSMSdfp
System Action: The system continues processing. Detecting Module: IDCVS03
Source: DFSMSdfp
IDC1002I RESETCAT CATALOG catname VOL
Detecting Module: IDCSA11 volser LEVEL timestmp
Explanation: This message indicates the catalog to be
IDC0970I ** NUMBER OF TRACKS = nnn; CCHH reset and the time stamp on the volume.
OF NEXT TRACK =X'cchh'
Explanation: The above data could not be restored in
the volume table of contents (VTOC). catname
The catalog name.
nnn The number of tracks.
timestmp
System Action: The command continues processing. The time stamp on the volume.
Application Programmer Response: If the volume is System Action: The system continues processing.
a virtual volume, ignore this error since alternate tracks
do not apply for virtual volumes and the problem need Source: DFSMSdfp

Detecting Module: IDCRS01 Storage Volume Control Journal data set.
IDC01011I CRA CHOSEN FOR RESET - VOL volser
cde The reason code returned from the Mass
LEVEL timestmp
Storage System Communicator.
Explanation: This message indicates the catalog
recovery area (CRA) to be reset and the time stamp on
A subsequent function may fail because of the error in
the volume.
the Inventory data set.
Application Programmer Response: Investigate the
volser The volume serial number. reason code returned from the Mass Storage System
Communicator. Contact the system programmer. The
timestmp
Inventory data set should be restored from the backup
The time stamp on the volume.
copy of the Inventory data set and the Journal data set.
Source: DFSMSdfp and the program is not in error, look at the messages in
Detecting Module: IDCRS01 reporting data bases for a fix for the problem. If no fix
IDC01037I catname HAS BEEN RESET JCL, the SYSOUT output for the job, and all printed
output and output data sets related to the problem.
Explanation: This message indicates that RESETCAT
processing has been completed for the indicated Source: DFSMSdfp
catalog.
In the message text: IDC1116I ERROR UPDATING CARTRIDGE
LABEL: text
catname
The catalog name. Explanation: text is one of the following:
VOLUME=volser, SEQ=nnn
System Action: The system continues processing. CSN=csn [,CSN=csn2]
Source: DFSMSdfp
One of the following has occurred:
Detecting Module: IDCRS01
v For a REPLACEC command, a Copy Cartridge order
resulted in the replacement of one of two cartridges
IDC01049I NON-VSAM/USERCATALOG ENTRIES in the indicated volume with the sequence number.
MOVED TO NEW CATALOG’S CRA An unrecoverable error occurred while the label of
the other cartridge was being updated to point to the
Explanation: This message indicates that RESETCAT
target cartridge.
processing has moved non-virtual storage access
method (VSAM), generation data group (GDG) base, v For a COPYV, CREATEV, or SCRATCHV command,
alias, or user catalog entries from the catalog recovery a Define Volume or Eliminate Volume order resulted
area (CRA) on the old catalog’s volume to the CRA on in the cartridges being listed on the scratch cartridge
the new catalog’s volume. list table. The cartridge or cartridges in error are
given an unusable cartridge serial number because
System Action: The system continues processing. the label could not be updated successfully.
Source: DFSMSdfp
IDC1069I FUNCTION PERFORMED - ERROR nnn The sequence number.

UPDATING INVENTORY, CODE = csn
X'cde'.
Explanation: If a Mass Storage Control function was
requested, the function was performed by the Mass System Action: The system completes processing of
Storage Control. However, an error prevented the Mass the failing order. Environmental data that identifies the
Storage Volume Control Inventory data set from being failing cartridge was logged on the primary processing
updated. If Inventory data set updating was requested, unit.
at least one record was updated in the Inventory. An Application Programmer Response: For a
error prevented the rest of the records from being REPLACEC command, if the REPLACEC command
updated. The request has been journaled in the Mass detected the error, reissue the command to replace the

other cartridge of the volume, which is indicated by the reporting data bases for a fix for the problem. If no fix
sequence number. If either the COPYV, CREATEV, or exists, contact the IBM Support Center. Provide all
SCRATCHV command detected the error, issue the printed output and output data sets related to the
MODIFYC command with the DIRECTEJECT parameter problem.
to move the failing cartridge or cartridges to the exit
Source: DFSMSdfp
station. Then issue the NULLIFYC SCRC CSN
command to eliminate the records for the ejected Detecting Module: IDCCH04
cartridges from the Mass Storage Facility.
Source: DFSMSdfp IDC01122I SUM=nnn OF INDIVIDUAL counts FROM
table NOT EQUAL TO TOTAL VALUE
IDC01120I INCONSISTENT field Explanation: The sum of the individual counts or
value counts obtained from the specified table does not
Explanation: The fields do not match in table entries
match the field that should contain the total of the
that are otherwise matching. Two secondary messages
counts or values. A secondary message identifies the
identify the specific field or attribute values that are
total value, and the table and table indices to locate the
inconsistent, and the respective tables and table indices
entry containing the total.
in which the inconsistencies occur.
nnn The sum of individual counts.
field The inconsistent field.
counts The specified counts.
table The specified table.
Application Programmer Response: Investigate the
inconsistency. Issue the DUMPMSS, LISTMSF, or System Action: The system continues processing.
LISTMSVI command to obtain dumps of the table with
the inconsistency. If there is any doubt whether the Application Programmer Response: Investigate the
inconsistency is temporary or not, issue the inconsistency. Issue the DUMPMSS, LISTMSF, or
CHECKMSS command again. LISTMSVI command to obtain dumps of the table with
the inconsistency. If there is any doubt whether the
System Programmer Response: If the error recurs inconsistency is temporary or not, run the CHECKMSS
and the program is not in error, search problem command again.
exists, contact the IBM Support Center. Provide all System Programmer Response: If the error recurs
printed output and output data sets related to the and the program is not in error, search problem
problem. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide all
Source: DFSMSdfp printed output and output data sets related to the
problem.
Detecting Module: IDCCH04
Source: DFSMSdfp
IDC01121I DUPLICATE field REFERENCE FOUND Detecting Module: IDCCH04
Explanation: More than one table entry references the
same field or attribute. All entries should be unique with IDC01123I ** VALUE=value table (index)
respect to that field or attribute. Two secondary
messages identify the specific field or attribute values Explanation: This secondary message identifies the
that are identical, and the tables and table indices in value of the field or attribute named in a primary
which the duplicate occurs. message: the table name containing the field or
attribute, and the table indices that identify the particular
In the message text: table entry containing the field or attribute.
field The duplicated field. In the message text:
System Action: The system continues processing. value The specified value.
Application Programmer Response: Investigate the table The table containing the field.
duplicate table entries. Issue the DUMPMSS, LISTMSF,
or LISTMSVI command to obtain dumps of the table index The index that identifies the table.
containing the duplicate information. If there is any System Action: The system continues processing.
doubt whether the duplicate is temporary or not, issue
the CHECKMSS command again. Application Programmer Response: See the
programmer response for the primary message.
and the program is not in error, search problem System Programmer Response: Search problem

IDC1142I OBJECT NOT SUPPORTED IN
RECORDMODE, CIMODE USED
printed output and output data sets related to the
problem. Explanation: The user has requested EXPORT
RECORDMODE for an object that must be processed
Source: DFSMSdfp
using control interval access. EXPORT RECORDMODE
Detecting Module: IDCCH04 cannot be used for linear data set (LDS) clusters.
System Action: The system continues processing
IDC01124I MATCHING field=value NOT FOUND IN using EXPORT CIMODE.
table1 TO MATCH table2 (index)
Application Programmer Response: Verify the
Explanation: An entry in the first table did not have a attributes of the data set being exported.
matching entry in the second table.
Source: DFSMSdfp
field=value Identifies the field or attribute and its
value for which a matching entry was
IDC01146I NO DISCREPANCIES FOUND, REPORT
not found or was not valid.
NOT PRINTED
table1
Explanation: No report was printed by the AUDITMSS
table2 The specified tables. command with the CHECK or READLABEL parameter.
No discrepancies were found.
index The table indices that locate the
unmatched entries. System Action: The command ends normally.
System Action: The system continues processing. Source: DFSMSdfp
Application Programmer Response: Investigate the Detecting Module: IDCAU03

inconsistency. Issue the DUMPMSS, LISTMSF, or
LISTMSVI command to obtain dumps of the tables with
IDC1147I IT IS RECOMMENDED THAT
the inconsistency. If there is any doubt whether the
DIAGNOSE AND EXAMINE BE RUN
inconsistency is temporary or not, run the CHECKMSS
BEFORE IMPORT OF CATALOG
command again.
Explanation: After the EXPORT of an integrated
catalog facility catalog and before IMPORT of that
catalog, it is recommended to run DIAGNOSE and
EXAMINE to detect any possible structure errors and
report on the structural integrity of the basic catalog
structure (BCS) of the catalog.
problem.
Source: DFSMSdfp
Source: DFSMSdfp
IDC1141I OBJECT NOT SUPPORTED IN CIMODE,
RECORDMODE USED IDC1178I DEFINE SPACE SUBCOMMAND
IGNORED - CATALOG IS ICF FORMAT
Explanation: The programmer requested EXPORT
CIMODE for an object that the system cannot process Explanation: A DEFINE SPACE subcommand was
using control interval access. EXPORT CIMODE can found to be oriented to an integrated catalog facility
only be used for ESDS base clusters that do not have (ICF) catalog. This function is incorrect in the ICF
an alternate index. catalog environment and thus this command is ignored.
System Action: The system continues processing System Action: This is an attention message. The
using EXPORT RECORDMODE. system writes this message with a return code of 4 to
call attention to the condition.
attributes of the data set the system is exporting. System Programmer Response: If the error recurs
Source: DFSMSdfp
exists, contact the IBM Support Center. Provide the JCL
and the SYSOUT output for the job.

Detecting Module: IDCRD04
IDC01190I CARTRIDGE csn IS NOW A SCRATCH
CARTRIDGE
IDC1252I COMMAND ALLOWS NO
Explanation: The cartridge with the specified cartridge PARAMETERS - PARAMETERS
serial number is now a scratch cartridge. IGNORED
In the message text: Explanation: This message indicates that for a
command defined to have no parameters, some
csn the cartridge serial number of the scratched
parameters were coded.
cartridge.
System Action: The system ignores the parameters
but processes the command.
Source: DFSMSdfp
Detecting Module: IDCNC01 and the program is not in error, search problem
IDC01215I LAST RECORD NOT FOUND IN dsname printed output and output data sets related to the
Explanation: While displaying or copying the problem and the control statements for the job.
requested records, the last record specified in the Source: DFSMSdfp
DATASETRANGE or the REPAIRRANGE parameter
was not found in the data set. Detecting Module: IDCRI04

IDC01360I THE FOLLOWING ENTRIES HAD NO
dsname ERRORS
The data set name.
Explanation: The entries that follow this message
System Action: REPAIRV DISPLAY/COPY ends. passed the DIAGNOSE checks with no errors.
Control returns to access method services. The return
code is 0. System Action: The system lists the entries without
errors.
IDC01371I RECORD DISPLAY SUPPRESSED,
ALREADY DUMPED
Source: DFSMSdfp
Explanation: The record described by message
Detecting Module: IDCRD02 IDC21365I will not be dumped here because the record
has already been dumped. If DIAGNOSE is unable to
IDCRD06 obtain enough storage to show which records have
been dumped, suppression of duplicates are
IDC01236I TRACK cchh WAS DEBLOCKED INTO suspended.
nnn RECORDS System Action: The system continues processing.
Explanation: The DEBLOCK function has deblocked Source: DFSMSdfp
the R‘0/R’1 pair into a number of records (including R0).
Detecting Module: IDCDA03
cchh Indicates the track. IDC01379I NO VVDS ENTRY FOR DSCB NAME
nnn The number of records the rack was deblocked dscbname
into. Explanation: A data set control block (DSCB) with no
System Action: REPAIRV DEBLOCK has written matching VVDS entry was found.
deblocked records to repair work. In the message text:
System Programmer Response: If the error recurs dscbname
and the program is not in error, search problem The DSCB name.
exists, contact the IBM Support Center. Provide the JCL System Action: The system continues processing the
and the SYSOUT output for the job. current command.

Source: DFSMSdfp action is because one of the associations could not be
defined in the target catalog and the sphere base and
any other associations already defined must be deleted
from the target catalog.
IDC01380I GENERATION DATA SET FOUND IN
DEFERRED ROLL IN STATE
dsname
Explanation: It is an informational message only.
The data set name.
Comparison of GDs is deferred and roll in state and
catalog recording continues. System Action: The system continues processing with
the next base object.
Application Programmer Response: Another
message will give the name of the object and the
IDC01381I VVR INTERRUPT RECOGNITION FLAG
reason it could not be defined. Correct this problem.
FOUND ON FOR dsname
Run the job again.
Explanation: During system processing, DIAGNOSE
Source: DFSMSdfp
found the interrupt recognition flag (IRF) on in the
VSAM volume record (VVR) for the specified data set. Detecting Module: IDCCC01
The IRF was left on when data facility data set services
(DFDSS) was moving the subject data set and had not
IDC01408I DATA SPACES TO BE DELETED FOR
completed the operation.
VOLUME volser
Explanation: During processing of a CNVTCAT
dsname command, suballocated entries in a virtual storage
The specified data set name. access method (VSAM) catalog have been found. The
specified volume’s VSAM data spaces will be deleted to
allow conversion. Unless an error message follows this
current command.
message indicating the delete failed, the data spaces
Application Programmer Response: Because the will have been deleted.
VVR may not correctly describe the extent of the data
set, do the following:
1. Copy the data set to a new data set. volser The volume serial number.
2. Verify the correct number of records were copied. System Action: The system continues processing if
3. Delete the old data set. the delete of the volume’s VSAM data space is
successful.
If the correct number of records was not copied, other
methods will be required to restore the data set. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCCC01
IDC01402I SPHERE CONVERSION COMPLETED IDC1412I TRACE ALREADY IN REQUESTED

FOR dsname STATE
Explanation: The conversion of the specified base Explanation: The hardware trace is already in the
sphere and its associations has completed successfully. requested state. The Mass Storage System
Communicator reason code is X'7F'.
System Action: The command completes normally.
dsname
The data set name. Source: DFSMSdfp

IDC01460I THE NUMBER OF ENTRIES MERGED
Source: DFSMSdfp WAS nnn
Detecting Module: IDCCC01 Explanation: The number of entries merged from the
source catalog to the target catalog is specified. This
IDC01407I SPHERE BACKED OUT OF TARGET count does not include data or index components.
CATALOG FOR dsname In the message text:
Explanation: The specified sphere base and any of its nnn The number of entries merged.
associations defined in the target catalog have been
deleted from the target catalog. The reason for this System Action: Normal processing continues.

Source: DFSMSdfp System Action: The ALTER command continues
processing with a condition code of 4, altering any
Detecting Module: IDCRP01
parameters other than KEYS and RECORDSIZE.
Incorrect key values also prevent alteration of record
IDC01500I {BIND | UNBIND} SUCCESSFUL FOR size values in the same command.
(SUBSYSTEM CONTAINING) volser
Application Programmer Response: If the default
Explanation: The data was successfully bound or values are not correct, run an ALTER command to
unbound for the device specified or unbound for the correct the values.
subsystem.
In the message text: and the program is not in error, look at the messages in
volser The volume serial number. reporting data bases for a fix for the problem. If no fix
System Action: The system performed the I/O exists, contact the IBM Support Center. Provide the JCL
operation without error. and the SYSOUT output for the job.
Detecting Module: IDCSS03 Detecting Module: IDCAL01
IDC1502I PASSWORD SUPPRESSION IN MODEL IDC1544I KEYS AND/OR RECORDSIZE VALUES

OBJECT EQUAL TO PRIOR NON-DEFAULT
VALUES
Explanation: The password information in the model
object was inaccessible because there was insufficient Explanation: The ALTER command specified the
password protection authorization or RACF KEYS or maximum RECORDSIZE parameter with
authorization. This is an informational or attention values equal to those already defined.
message that occurs if the password or RACF System Action: The ALTER command continues
authorization provided is not high enough to locate the processing with a condition code of 4, altering any
passwords themselves. The passwords were not used parameters other than KEYS and RECORDSIZE.
for the object being defined. Incorrect key values also prevent alteration of record
System Action: The system continues processing. size values in the same command.
The passwords are not modeled. Application Programmer Response: If the specified
Application Programmer Response: If the values are not correct, run an ALTER command to
passwords are to be modeled, delete the data set. correct the values.
Before redefining, either supply the MASTERPW System Programmer Response: If the error recurs
password of the model object or have your user profile and the program is not in error, look at the messages in
modified so you have RAC-alter access to the model the job log for more information Search problem
object. reporting data bases for a fix for the problem. If no fix
System Programmer Response: If the error recurs exists, contact the IBM Support Center. Provide the JCL
and the program is not in error, search problem and the SYSOUT output for the job.
and the SYSOUT output for the job. Detecting Module: IDCAL01
Source: DFSMSdfp
IDC01551I type CACHING STATUS: stat FOR SD
Detecting Module: IDCDE02 X‘ss’ DEV X‘dd’
Explanation: This message is routed to the systems
IDC1543I NEW KEYS AND/OR RECORDSIZE console by the LISTDATA command in response to a
VALUES EQUAL TO PRIOR DEFAULT request for status with the WTO parameter.
VALUES.
Explanation: The ALTER command specified the
KEYS or maximum RECORDSIZE parameter with type Identifies the DASD type.
values equal to the default values chosen by the
stat Status, as follows:
DEFINE command. The DEFINE defaults are KEYS (64
0) and RECORDSIZE (4089 4089) for non-spanned v ACTIVE if the subsystem is active.
record data sets or RECORDSIZE (4086 32600) for
spanned record data sets.

v SUBSYSTEM ERROR if an I/O error Operations and Recovery Guide for detailed recovery
occurred when requesting status from the actions.
subsystem and the model is not 3990 Model
Source: DFSMSdfp
3 or Model 6.
v HOST TERMINATION if a SETCACHE Detecting Module: IDCLA01
command has been previously issued to turn
off caching in the subsystem and the model IDC01553I NVS STATUS: stat DEV X‘ddd’
is not 3990 Model 3 or Model 6.
Explanation: This 3990 Model 3 or Model 6 message
ss The address of the subsystem’s caching is routed to the systems console by the LISTDATA
storage director. command in response to a request for status with the
dd The channel connection address of the device WTO parameter. This message might appear with
on which the I/O was done. IDC01552I, IDC01554I, IDC01555I, and IDC01556I.
System Action: The system continues processing. A In the message text:

full status report appears on SYSPRINT or in the stat Status, as follows:
alternate data set described in the procedure used to
issue the LISTDATA command. v ACTIVE if the nonvolatile storage is active.
v DEACTIVATED-SUBSYSTEM ERROR when
Source: DFSMSdfp an internal subsystem error caused
Detecting Module: IDCBD0I nonvolatile storage termination.
v DEACTIVATED-HOST/SF when an explicit
host system or support facility request
IDC01552I SUBSYSTEM CACHING STATUS:
caused nonvolatile storage termination.
stat-DEV X‘ddd’
v DEACTIVATION IN PROGRESS when a
Explanation: This 3990 Model 3 or Model 6 message request for deactivation has been received
is routed to the systems console by the LISTDATA and the destage is in progress.
command in response to a request for status with the
v DEACTIVATION FAILED when a request for
WTO parameter. This message might appear with
deactivation was received and the destage
IDC01553I, IDC01554I, IDC01555I, and IDC01556I.
failed.
In the message text: v DISABLED when the nonvolatile storage is
stat Status, as follows: disabled for maintenance.
v ACTIVE if the subsystem is active. ddd The device number on which the I/O operation
v ACTIVATION PENDING if the cache is being occurred.
brought online. System Action: The system continues processing. A
v DEACTIVATED-SUBSYS when an internal full status report appears on SYSPRINT or in the
subsystem error caused caching termination. alternate data set described in the procedure used to
v DEACTIVATED-HOST/SF when an explicit issue the LISTDATA command.
host system or support facility request Operator Response: If the device associated with this
caused caching termination. message is attached via the IBM 3990 Model 3 or
v DEACTIVATION PENDING when a request Model 6 Storage Control, see IBM 3990/9390
for deactivation has been received and the Operations and Recovery Guide for detailed recovery
operation is in progress. actions.
v DEACTIVATION FAILED when a request for Source: DFSMSdfp
deactivation was received and the operation
failed. when the status is represented by an Detecting Module: IDCLA01
undefined bit combination.
ddd The device number on which the I/O operation IDC01554I DASD FAST WRITE STATUS: stat DEV
occurred. ddd
System Action: The system continues processing. A Explanation: This 3990 model 3 message is routed to
full status report appears on SYSPRINT or in the the systems console by the LISTDATA command in
alternate data set described in the procedure used to response to a request for status with the WTO
issue the LISTDATA command. parameter. It may appear with IDC01552I, IDC01553I,
IDC01555I, or IDC01556I.
Operator Response: If the device associated with this
message is attached via the IBM 3990 Model 3 or In the message text:
Model 6 Storage Control, see IBM 3990/9390 stat Status, as follows:

v ACTIVE if DASD fast write is active.
IDC01556I CACHE FAST WRITE STATUS: stat DEV
v DEACTIVATION PENDING when transfer of ddd
modified DASD fast write data to DASD
failed. Explanation: This 3990 model 3 message is routed to
the systems console by the LISTDATA command in
v DEACTIVATED when DASD fast write is
response to a request for status with the WTO
disabled. combination.
parameter. It may appear with IDC01552I, IDC01553I,
ddd The device number on which the I/O operation IDC01554I, or IDC01555I.
occurred.
System Action: The system continues processing. A
full status report appears on SYSPRINT or in the
v ACTIVE if cache fast write is active.
alternate data set described in the procedure used to
v DISABLED if cache fast write is disabled.
issue the LISTDATA command.
ddd The device address (370) on which the I/O
operation occurred.
message is attached via the IBM 3990 Model 3 or
Model 6 Storage Control, see IBM 3990/9390 System Action: The system continues processing. A
Operations and Recovery Guide for detailed recovery full status report appears on SYSPRINT or in the
actions. alternate data set described in the procedure used to
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCLA01
IDC01555I DUPLEX PAIR STATUS: stat {PRI | SEC}
DEV X‘ddd’ {pri|sec} DEV X‘xx’ IDC01557I ACCESS CODE FOR SCU X‘scu’ SC
X‘sc’ IS X‘acode’
Explanation: This 3990 Model 3 or Model 6 message
is routed to the systems console by the LISTDATA Explanation: The LISTDATA command to retrieve the
command in response to a request for status with the remote access authorization code was successful. One
WTO parameter when the device in the status request message is routed to the systems console for each
is part of a duplex pair. This message might appear with storage cluster.
IDC01552I, IDC01553I, IDC01554I, and IDC01556I.
scu The box serial number.
sc The 2 hexadecimal digit storage cluster
v ACTIVE if the duplex pair is active. number.
v PENDING when the copy to establish a
acode The 8 hexadecimal digit remote access code.
duplex pair is in progress.
v SUSPENDED when the duplex pair is System Action: The system continues processing.
suspended by a host command (for Source: DFSMSdfp
example, SETCACHE SUSPENDPRIMARY),
or by the subsystem. Detecting Module: IDCLA01
pri Indicates that the addressed device is primary.

IDC1561I WKSPC LACKING FOR dsname
sec Indicates that the addressed device is
secondary. Explanation: A larger region size is required for this
particular invocation of access method services and
ddd The device number on which the I/O operation LISTCAT.
occurred.
xx The channel connection address (CCA) of the
other device in the duplex pair returned in the dsname
sense subsystem status data. The data set name.
System Action: The system continues processing. A System Action: The LISTCAT command bypasses the
full status report appears on SYSPRINT or in the indicated entry and continues processing with a
alternate data set described in the procedure used to condition code of 4.
Application Programmer Response: Run the job
Source: DFSMSdfp again in a larger region for those entries that were
bypassed.

System Programmer Response: If the error recurs System Action: The LISTCAT command bypasses the
and the program is not in error, look at the messages in specified entry and continues processing with a
the job log for more information. Search problem condition code of 4.
again with the correct type or types specified.
Source: DFSMSdfp
Detecting Module: IDCLC02 reporting data bases for a fix for the problem. If no fix
IDC1562I ser VOLUME SERIAL NUMBER TOO
LONG Source: DFSMSdfp
Explanation: A volume serial number exceeds six Detecting Module: IDCLC01
characters for the LISTCAT SPACE request.
In the message text: IDC1566I ** xxx NOT LISTED
ser The volume serial number. Explanation: One of the following conditions is
present:
System Action: The LISTCAT command bypasses the
indicated entry and continues processing with a v An entry name specified in the LISTCAT ENTRIES
condition code of 4. parameter does not exist in the catalogs to be listed.
v An associated object for a CLUSTER, AIX or GDG
group does not exist if LISTCAT was requested with
again with the corrected volume serial numbers.
no entry types specified.
System Programmer Response: If the error recurs v Password verification failed.
v An entry name specified in the ENTRIES parameter
was a volume serial number and the catalogs to be
listed is an integrated catalog facility (ICF) catalogs.
v A catalog error has occurred.
Source: DFSMSdfp
Detecting Module: IDCLC01 In the message text:
xxx The entry name.
IDC1564I chartyp IS AN UNKNOWN TYPE System Action: The system bypasses the designated
Explanation: An entry returned from the catalog is a entry. The system continues processing with a return
type not supported by LISTCAT. code of 4.
In the message text: Application Programmer Response: Correct the

entry name. Return the job to list only this entry or refer
chartyp The unsupported type. to the documentation for message IDC3009I and
System Action: The LISTCAT command bypasses the respond as indicated for the specified return code and
entry and continues processing with a condition code of reason code.
4. If the name should be in the virtual storage access
System Programmer Response: If the error recurs method (VSAM) volume data set (VVDS), run a PRINT
and the program is not in error, search problem of the VVDS to verify the presence of the catalog name.
reporting data bases for a fix for the problem. If no fix System Programmer Response: If the error recurs
exists, contact the IBM Support Center. Provide the JCL and the program is not in error, look at the messages in
and the SYSOUT output for the job. the job log for more information. Search problem
Source: DFSMSdfp reporting data bases for a fix for the problem. If no fix
Detecting Module: IDCLC01 and the SYSOUT output for the job.
Source: DFSMSdfp
IDC1565I xxx NOT A REQUESTED TYPE
Detecting Module: IDCLC01
Explanation: A desired entry was not among the types
requested.
xxx The desired type.

IDC1567I ** INVALID CONTROL INTERVAL IDC1575I ONLY {BACKUP|TARGET} DEFINES
NUMBER nnn {dsname|ser}
Explanation: An entry identified by a control interval Explanation: This message indicates that either the
number in the virtual storage access method (VSAM) backup or target catalog does not contain the data set
catalog does not exist. or volume entry.
nnn The incorrect control interval number. dsname
The data set name.
System Action: The system bypasses the designated
entry. The system continues processing. ser The volume serial number.
System Programmer Response: If the error recurs System Action: The system continues reload
and the program is not in error, look at the messages in processing.
Application Programmer Response: Do one of the
following:
and the SYSOUT output for the job. v If only the backup defines a data set, the physical
data for the data set probably does not exist on the
Source: DFSMSdfp volumes indicated. Delete the catalog entry. Use the
Detecting Module: IDCLC01, IDCLC02 DELETE NOERASE option, since the ERASE option
may affect other users’ data.
v If only the backup defines a volume, the volume is
IDC1569I EXPIRATION PARAMETER DOES NOT
probably no longer owned by this catalog. Delete any
APPLY TO ENTRY TYPE(S)
data sets indicated as residing on this volume. Then
Explanation: The EXPIRATION option of LISTCAT delete the volume.
was specified with entry types that contain either no v If only the target defines a virtual storage access
expiration-date field or an expiration-date field that is method (VSAM) data set, access to the data set has
never initialized. been lost. Obtain and import (IMPORT command) a
System Action: LISTCAT continues normally after the backup copy of the data set (output from EXPORT).
attention message, processing the specified entry types. v If only the target defines a non-VSAM data set or an
The listing is not restricted by the EXPIRATION option. alias or generation data group (GDG), reestablish the
All specified entry types will be listed. catalog entries with the DEFINE command.
Source: DFSMSdfp v If only the target defines a volume, access has been
lost to the volume. It cannot be reused by VSAM until
Detecting Module: IDCLC01 the VSAM ownership and data space protection
attributes have been removed. Run access method
services ALTER REMOVE VOLUME.
IDC1574I CATALOG ENTRY COMPARISON NO
LONGER FUNCTIONING Source: DFSMSdfp
Explanation: This message follows the 100th Detecting Module: IDCRP01
IDC1575I message. Comparison of the backup and
target catalog continues but only volume serial number
mismatches are listed. IDC1595I PASSWORDS SUPPRESSED FOR THE
EXPORTED DATA SET
System Action: The system continues reload
processing. Explanation: The password and other protection
information was inaccessible due to insufficient
Application Programmer Response: The large password or RACF authorization. The portable version
number of discrepancies detected between the target of the data set has been created, but without the
and backup catalogs indicate that the reloaded catalog protection attributes.
should be used until the LISTCAT output obtained
before and after the reload has been carefully checked. When protection information is exported, it does not
include the RACF profile, the passwords, and other
Source: DFSMSdfp protection information for the data set. However, the
RACF indicator is exported.
command.
Application Programmer Response: If the protection
attributes are desired, specify the master level password

or have your user profile modified so it indicates unit address makes the second cache storage director
RACF-alter access to the data set. accessible.
Source: DFSMSdfp Operator Response: Contact hardware support.
Detecting Module: IDCXP01 Source: DFSMSdfp
Detecting Module: IDCSS03
IDC1597I THE text PARAMETER IS INVALID FOR
AN ICF CATALOG
IDC01605I STORAGE DIRECTOR X‘yy’ SET {ON |
Explanation: text is one of the following: OFF}, PREVIOUSLY {ON | OFF}
INHIBITSOURCE
Explanation: The SETCACHE command to set the
INHIBITTARGET
storage director on or off completed successfully.
PERMANENT
An integrated catalog facility (ICF) catalog is to be
yy Indicates the address of the storage director.
exported and INHIBITSOURCE or INHIBITTARGET was
specified or PERMANENT was specified or defaulted. System Action: The system sets the return code to 0.
These parameters are incorrect when exporting an ICF
catalog. Source: DFSMSdfp
System Action: The system ignores the incorrect Detecting Module: IDCSC0I
parameter. The system exports the object.
Application Programmer Response: If an ICF IDC1631I DUPLICATE ‘SYS1. DATA SET NAME’
catalog is being exported, do not specify IN TARGET CATALOG
INHIBITSOURCE or INHIBITTARGET and specify Explanation: A duplicate SYS1. data set entry was
TEMPORARY. found in the virtual storage access method (VSAM) or
System Programmer Response: If the error recurs integrated catalog facility (ICF) catalog while attempting
and the program is not in error, search problem to convert an OS catalog entry.
reporting data bases for a fix for the problem. If no fix System Action: An accompanying message identifies
exists, contact the IBM Support Center. Provide the JCL the entry not converted. The system does not convert
and the SYSOUT output for the job. the entry.
Source: DFSMSdfp Application Programmer Response: If duplicates
Detecting Module: IDCXP01 exist and the one on the control volume (CVOL) is the
copy wanted in the target catalog, then delete the copy
in the target catalog prior to issuing the CNVTCAT
IDC01600I CACHING SET {ON | OFF} FOR command.
(SUBSYSTEM CONTAINING) volser.
Explanation: The I/O operation to set the cache on or and the program is not in error, search problem
off completed successfully. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
System Action: the system sets the return code to 0.
Source: DFSMSdfp
Detecting Module: IDCSS03 IDC1632I CVOL POINTER ‘xxx’ TO VOLUME ‘ser’
NOT CONVERTED
IDC01603I EQUIPMENT CHECK ON FIRST UNIT Explanation: The control volume (CVOL) name was
ADDRESS, SECOND ADDRESS not converted to an alias entry in the virtual storage
ACCESSED access method (VSAM) or integrated catalog facility
(ICF) master catalog because the CVOLEQUATES
Explanation: An I/O operation received an equipment
parameter was not specified, or was specified but the
check on the first unit address because the first cache
CVOL volume serial number in the CVOL pointer entry
storage director could not access the second cache
was not the one specified in the parameter.
storage director in the subsystem.
System Action: The system starts a second I/O
operation using the second unit address. The second xxx The CVOL pointer.

ser The volume serial number. Application Programmer Response: After the
alternate index is built, delete the short record. Rewrite
System Action: The system does not convert the
a long enough record through a user program with the
entry.
alternate index as part of the upgrade set. The alternate
Application Programmer Response: Use the index will be upgraded to reflect this particular base
DEFINE ALIAS command to create an alias entry in the record.
master catalog.
System Programmer Response: If the error recurs and the program is not in error, search problem
and the program is not in error, look at the messages in reporting data bases for a fix for the problem. If no fix
the job log for more information. Search problem exists, contact the IBM Support Center. Provide the JCL
reporting data bases for a fix for the problem. If no fix and the SYSOUT output for the job.
Source: DFSMSdfp
Source: DFSMSdfp
IDC1645I NONUNIQUE AIX KEY key PRIME
{KEY|RBA} IS xxx
IDC1638I ALIASES OF GENERATION INDEX
Explanation: The alternate index being built was
POINTER ENTRIES ARE NOT
defined with the UNIQUEKEY attribute. That is, the
CONVERTED
alternate key exists on only one base cluster record.
Explanation: An alias name of an OS catalog However, multiple occurrences of the same alternate
generation index pointer entry (GIPE) was encountered. key have been encountered. The system writes this
Because aliases of virtual storage access method message for each multiple occurrence. The message
(VSAM) or integrated catalog facility (ICF) catalog gives the alternate key first, up to a maximum of the
generation data group (GDG) base entries are not first ten bytes, expressed in hexadecimal.
allowed, the GIPE alias name is not converted.
If the base cluster is a key-sequenced data set, the
System Action: The system does not convert the specified record is the prime key (up to a maximum of
entry. the first ten bytes) expressed in hexadecimal.
System Programmer Response: If the error recurs If the base cluster is an entry-sequenced data set, the
and the program is not in error, look at the messages in specified record is the prime relative block address
the job log for more information. Search problem (RBA) in decimal.
and the SYSOUT output for the job. key Indicates the nonunique key.
Source: DFSMSdfp xxx Indicates the prime key.
Detecting Module: IDCCC01 System Action: An alternate index record is created
containing the alternate key and only the first prime key
or RBA listed. All subsequent prime keys/RBAs will not
IDC1644I ALTERNATE INDEX KEY NOT IN BASE
be reflected in the alternate index record.
RECORD xxx
Explanation: The base cluster record is not long
UNIQUEKEY attribute was correctly specified, then the
enough to contain the entire alternate key. If the base
base cluster is in error. Correct it through a calling
cluster is a key-sequenced data set, the specified
program
record is the key of the short base cluster record (up to
a maximum of the first ten bytes) expressed in If the UNIQUEKEY attribute was incorrectly specified:
hexadecimal. v and the alternate index was defined with the REUSE
If the base cluster is an entry-sequenced data set, the parameter, change it to NONUNIQUEKEY using the
specified record is the relative block address (RBA) of access method services ALTER command.
the short base cluster record, given in decimal. v and the alternate index was defined with the REUSE
parameter, change it to NONUNIQUEKEY using the
access method services ALTER command.
xxx Indicates the base cluster record. v and the alternate index was not defined with the
System Action: The system bypasses the base REUSE attribute, delete the alternate index and
cluster record. The record will not be reflected in the redefine it with the NONUNIQUEKEY attribute.
alternate index being built. See the subsequent
message for the name of the alternate index.

Then rebuild the alternate index using the BLDINDEX In the message text:
Command.
dsname
System Programmer Response: If the error recurs The data set name.
System Action: The building of the alternate index is
complete.
and the SYSOUT output for the job. Application Programmer Response: Refer to the
action outlined for the individual errors.
Source: DFSMSdfp
IDC1646I nnnnn EXCESS PRIME {KEY|RBL} exists, contact the IBM Support Center. Provide the JCL
VALUES FOR AIX KEY key and the SYSOUT output for the job.
Explanation: The specified key is the key of an Source: DFSMSdfp
alternate index record that was too short to contain all
the prime key or relative block address (RBA) pointer
values that occurred for that alternate index key.
IDC01653I ALIASES FROM THE PORTABLE DATA
SET WERE DEFINED
nnnnn The number of pointers that could not fit into
Explanation: The names that follow this message are
the record. The name of the alternate index
aliases from the portable data set; they have been
being built is given in a subsequent message.
defined for the integrated catalog facility catalog being
key Indicates the key. imported.
System Action: The alternate index record is created System Action: Processing continues with the aliases
with only those pointers that could fit. defined and listed.
Application Programmer Response: Delete the Application Programmer Response: None.
alternate index and redefine it using the access method
Source: DFSMSdfp
services commands with a maximum record size long
enough to contain the maximum number of pointers for Detecting Module: IDCXP01
any one alternate key. Then rebuild the alternate index
using the BLDINDEX command.
IDC01654I ALIASES FROM THE PORTABLE DATA
System Programmer Response: If the error recurs SET WERE NOT DEFINED
reporting data bases for a fix for the problem. If no fix Explanation: The names that follow this message are
exists, contact the IBM Support Center. Provide the JCL aliases from the portable data set; they have not been
and the SYSOUT output for the job. defined for the integrated catalog facility catalog being
imported.
Source: DFSMSdfp
System Action: Processing continues with the aliases
Detecting Module: IDCBI01 listed.
IDC1653I dsname BUILT WITH ERRORS
Source: DFSMSdfp
Explanation: Building of the alternate index has been
completed but some non-ending errors were Detecting Module: IDCXP01
encountered. Non-ending errors consist of:
v Alternate index key not contained in one or more IDC01657I OBJECT WAS SMS-MANAGED WHEN
base cluster records. EXPORTED. CHANGED TO
v Multiple occurrences of one or more alternate keys UNMANAGED.
for an alternate index defined with the UNIQUEKEY Explanation: The object of an IMPORT command was
attribute. SMS managed when it was exported to the portable
v One or more alternate index records too short to data set. After processing of the IMPORT command, the
contain all the prime key or RBA pointers. object became unmanaged.
All non-ending errors for this alternate index have been System Action: The object is imported to unmanaged
identified in messages that precede this message. storage.
Source: DFSMSdfp

IDC1664I ASSOCIATION ERROR, dsname
Explanation: The named catalog entry described a
IDC1661I OUT-OF-SYNC DATA SET
generation data set having no relationship to any
SUCCESSFULLY EXPORTED (BY
OS/VS2 generation data group, or the entry describes a
FORCE)
non-VSAM data set containing other than an OS/VS
Explanation: The portable data set contains the alias related to it.
necessary information to recreate the data set through
IMPORTRA. At the time of export the data set was out
of synchronization, caused by a mismatch between time dsname
stamps or space information. See the secondary The data set name.
message for the data set name.
System Action: The association cannot be processed.
System Action: The system continues processing. The system continues processing of the named object.
Source: DFSMSdfp Application Programmer Response: List the named
object after performing an IMPORTRA operation to
determine missing related objects and to redefine the
related objects.
IDC1662I OUT-OF-SYNC DATA SET NOT
Source: DFSMSdfp
EXPORTED
Explanation: The virtual storage access method
(VSAM) data set named in the message that follows is
out of synchronization and the FORCE parameter was IDC1667I VOLUME volser1 IS OUT-OF-SYNC AND
not specified. The out-of-synchronization is caused by a LATER THAN VOLUME volser2
mismatch of the space information.
Explanation: The data-set-directory-entry time stamp
System Action: The system bypasses processing of mismatches the time stamp for the virtual storage
the VSAM data set. access method (VSAM) data set named in the following
message. The volumes are out of synchronization,
Application Programmer Response: If the data set,
although some of the data sets may still be recoverable.
with its possible problems, is desired, then specify the
FORCE parameter on the EXPORTRA command. Run In the message text:
the job again.
ser1
Source: DFSMSdfp
ser2 The volume serial numbers that indicate the
Detecting Module: IDCRC01 volumes that are out of synchronization.
System Action: The system bypasses the VSAM data
IDC1663I BYPASSED RELATION dsname set entry and associations.
Explanation: An error occurred or a catalog entry Application Programmer Response: Get the two
could not be located for a path or an alternate index to volumes in synchronization. Run the job again.
a virtual storage access method (VSAM) cluster, an
Source: DFSMSdfp
OS/VS alias for a non-VSAM object, or a non-VSAM
object associated with an OS/VS2 generation data Detecting Module: IDCRC01
group.
In the message text: IDC1678I ** DATA SET EXPORTED WITH MINOR
ERRORS
dsname
The name of the cluster, non-VSAM object, or Explanation: An error occurred while processing an
generation data group (GDG). associated object for an object being exported.
System Action: The system bypasses the related System Action: The system bypasses processing of
object. The system continues processing of the named the associated object.
object.
Application Programmer Response: List the named preceding message to determine the type of error and
object after performing an IMPORTRA operation to the recovery procedure.
determine missing related objects and to redefine the
related objects. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCRC01

size Indicates the control interval size.
IDC1679I ** OUT-OF-SYNC DATA SET
EXPORTED WITH MINOR ERRORS Source: DFSMSdfp
Explanation: An error occurred while processing an
associated object for an out-of-synchronization data set. IDC01705I CONTROL AREA SIZE IS size
The out-of-synchronization is caused by a mismatch
between the time stamps or space information on the Explanation: This message displays the control area
various volumes of a multi-volume data set. size in decimal.
System Action: The system bypasses processing of In the message text:

the associated object. size Indicates the control area size.
Application Programmer Response: See the Source: DFSMSdfp
preceding message to determine the type of error and
the recovery procedure.
IDC01706I RBA IS rba
Source: DFSMSdfp
Explanation: This message displays a relative byte
Detecting Module: IDCRC01 address (RBA) in decimal.
IDC01700I INDEXTEST BEGINS
rba Indicates the relative byte address.
Explanation: The INDEXTEST diagnostic procedure is
beginning to process. Source: DFSMSdfp
System Action: The system begins processing.

IDC1707I ** OWNER ownerid NOT UPDATED IN
Source: DFSMSdfp INVENTORY FOR NEW COPY yyddd
Explanation: The owner data in the volume label of
IDC01701I DATATEST BEGINS the new copy volume, created on the specified date,
Explanation: The DATATEST diagnostic procedure is could not be updated in the copy volume record or in
beginning to process. the cartridge labels.
System Action: The system begins processing. This condition occurred because the cartridges of an
existing copy volume were reused. See the preceding
Source: DFSMSdfp message for further explanation of the problem.
IDC01702I HIGH-USED RBA IS rba
ownerid
Explanation: This message displays the component Indicates the owner of the data.
high-used relative byte address (RBA) in decimal.
rba Indicates the high-used relative byte address.
Application Programmer Response: This
Source: DFSMSdfp discrepancy cannot be corrected. The LISTMSVI reports
will reflect different owners for the source volume and
the designated copy volume, even though the owner
IDC01703I HIGH-ALLOCATED RBA IS rba
data is correct in the volume labels of both volumes.
Explanation: This message displays the component
Source: DFSMSdfp
high-allocated relative byte address (RBA) in decimal.
rba Indicates the high-allocated relative byte
IDC01707I CURRENT INDEX LEVEL IS level
address.
Explanation: This message displays the level of the
Source: DFSMSdfp
index being processed when an error is detected.
IDC01704I CONTROL INTERVAL SIZE IS size
level Indicates the current index level.
Explanation: This message displays the control
interval size in decimal. Source: DFSMSdfp

System Action: The system concludes processing
IDC01708I nnn CONTROL INTERVALS
normally.
ENCOUNTERED
Source: DFSMSdfp
Explanation: This message indicates the total number
of control intervals read.
IDC01713I DATA CONTROL INTERVAL DISPLAY
AT RBA rba FOLLOWS
nnn The number of control intervals.
Explanation: This message displays the relative byte
System Action: The system continues processing. address (RBA) in decimal of the control interval. The
control interval display follows.
Source: DFSMSdfp
IDC01709I DATATEST COMPLETE - NO ERRORS rba The relative byte address.
DETECTED
Source: DFSMSdfp
Explanation: The entire data component has been
tested and no errors have been found.
IDC01714I ERROR LOCATED AT OFFSET offset
Explanation: This message follows a control interval
normally.
display and specifies the location in hexadecimal of the
Source: DFSMSdfp item in error.
IDC01710I DATA COMPONENT CONTAINS nnn
offset The offset.
RECORDS
Source: DFSMSdfp
Explanation: After DATATEST concludes, this
message displays the number of records contained in
the data set. IDC01716I INDEX KEY FOLLOWS
In the message text: Explanation: The key value follows this message.
Where applicable, two key values follow.
nnn The number of records.
Source: DFSMSdfp
normally.
IDC01717I DATA KEY FOLLOWS
Source: DFSMSdfp
Explanation: The key display follows this message.
IDC01711I DATA COMPONENT CONTAINS nnn Source: DFSMSdfp
DELETED CONTROL INTERVALS
Explanation: After DATATEST concludes, this IDC01718I RECORD UPDATE NUMBER IS number
message displays the number of unreclaimed empty
control intervals. Explanation: This message displays the expected
update number of the spanned record segment.
nnn The number of control intervals.
number The number of the record update.
normally. Source: DFSMSdfp
Source: DFSMSdfp
IDC01720I INDEX CONTROL INTERVAL DISPLAY
AT RBA rba FOLLOWS
IDC01712I MAXIMUM LENGTH DATA RECORD
CONTAINS nnn BYTES Explanation: This message displays the relative byte
address (RBA) in decimal of the control interval. The
Explanation: After DATATEST concludes, this control interval display follows.
message displays the length in decimal of the longest
data record encountered. In the message text:
In the message text: rba The relative byte address.
nnn The number of bytes. Source: DFSMSdfp

IDC01722I nnn PERCENT FREE SPACE
rba The relative byte address.
Explanation: After DATATEST concludes, this
message displays the percentage of free space in the Source: DFSMSdfp
data set.
In the message text: IDC1742I RECATALOG OPTION INVALID FOR
VOLUME
nnn The percentage of available space.
Explanation: The source volume is not owned by a
Source: DFSMSdfp
virtual storage access method (VSAM) catalog.
Therefore, the VSAMCATALOG option does not apply.
IDC01723I ERRORS MAY BE DUE TO
System Action: No recataloging is performed. The
CONCURRENT ACCESS
command continues processing.
Explanation: The catalog OPEN indicator or AMDSB
indicates that the data set may have been updated
IEHPROGM utility or the access method services
during EXAMINE testing. Some or all of the detected
DELETE and DEFINE commands to recatalog data
errors may not exist.
sets.
Application Programmer Response: If possible, run
EXAMINE again without any users having the data set
OPEN for output. If this is not possible, ensure that the
data set is not updated during testing.
Source: DFSMSdfp :sysact.The system continues JCL, the SYSOUT output for the job, and all printed
processing. output and output data sets related to the problem.
Source: DFSMSdfp
IDC01724I INDEXTEST COMPLETE - NO ERRORS
DETECTED
Explanation: The entire index component has been
IDC1784I NO SCRATCH CARTRIDGES FOUND IN
tested and no errors have been found.
MSF
Explanation: No scratch cartridges can be ejected
normally.
from the Mass Storage Facility (MSF) because there are
Application Programmer Response: Run DATATEST no cartridges in the MSF.
to validate the data component.
System Action: The command abnormally ends with
Source: DFSMSdfp a message.
Source: DFSMSdfp
IDC01725I REFER TO DATA CONTROL INTERVAL
DISPLAY FOR RBA rba
Explanation: This message is issued in lieu of
IDC01806I NO VOLUMES WERE SELECTED TO
message IDC01713I when an error is detected in a
BE PROCESSED
previously-displayed data control interval. This message
displays the relative byte address (RBA) in decimal of Explanation: The volumes specified in the volumes
the data control interval. parameter or resolved from the storage group
parameter do not exist on the system or are not
available for processing.
rba The relative byte address.
Source: DFSMSdfp
Application Programmer Response: Ensure that the
specified volumes exist and are on line.
IDC01726I REFER TO INDEX CONTROL INTERVAL
DISPLAY FOR RBA rba
Explanation: This message is issued in lieu of the job log for more information. Search problem
message IDC01720I when an error is detected in a reporting data bases for a fix for the problem. If no fix
previously-displayed index control interval. This exists, contact the IBM Support Center. Provide the
message displays the relative byte address (RBA) in JCL, the SYSOUT output for the job, and all printed
decimal of the index control interval. output and output data sets related to the problem.

Source: DFSMSdfp
IDC01850I SORT PRODUCT CALL
IDENTIFICATION NUMBER xxxx
IDC01811I NUMBER OF n RECORDS PROCESSED
Explanation: xxxx represents the identification number
WAS xxxx
of a call to DFSORT (or an equivalent product) by
Explanation: Indicates the number of n-type records BLDINDEX. This identification number corresponds to
written to the output data set. the call identifier in DFSORT message ICE200I (or to
the identifier in the appropriate message for an
In the message text: equivalent product).
n The type of record written. System Action: None.
xxxx The number of records written. System Programmer Response: None.
System Action: Processing continues. Detecting Module: IDCBI01
Source: DFSMSdfp
IDC01851I ″NOSORTCALL″ invalid parameter for
IDC1840I TRACE AREA EMPTY - NO DATA extended addressability data set.
DUMPED Explanation: User must use SORTCALL parameter in
Explanation: An attempt was made to dump trace BLDINDEX command for building alternate indexes for
data but the trace areas requested were null. extended addressability data sets.
System Action: The command ends normally. System Action: Processing for the BLDINDEX
STEP/JOB Terminated.
Application Programmer Response: Turn the trace
on before requesting a dump. Application Programmer Response: Specify sortcall
parameter on the BLDINDEX command to build
System Programmer Response: If the error recurs alternate indexes for extended addressability data set.
reporting data bases for a fix for the problem. If no fix System Programmer Response: IDCBI01
exists, contact the IBM Support Center. Provide the Source: DFSMSdfp
IDC1860I SELECTED CHECKID, xxxxxxxx NOT
Source: DFSMSdfp FOUND
Detecting Module: IDCTR01 Explanation: The checkid listed was selected by the
user, but not found in the checkpoint data set.
IDC1841I END OF CURRENT DATA COULD NOT In the message text:
BE DETERMINED - ALL DATA DUMPED
xxxxxxxx
Explanation: An attempt was made to dump only The check identification.
current trace data, but the end of the current data was
not found. Therefore, all of the trace data was dumped. System Action: The system continues processing, but
There may be data from a previous trace period in the the CHECKID is not processed.
output data set.
System Action: The command dumped all the data in checkid spelling, and that the correct checkpoint data
the requested trace area. set was used.
Application Programmer Response: Run the trace System Programmer Response: If the error recurs
report program and select only the data from the current and the program is not in error, look at the messages in
trace period for processing. the job log for more information. Search problem
and the program is not in error, search problem SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCTR01

IDC1864I NO CHECKPOINTS FOUND ON DATA
SET
Explanation: No CHR records were found on the exists, contact the IBM Support Center. Provide the
checkpoint data set. SYSOUT output for the job.
System Action: The system abnormally ends Source: DFSMSdfp
CHKLIST.
Application Programmer Response: Verify that the
correct checkpoint data set was used, then resubmit
IDC1867I CURRENT VOLUME NOT FOUND
job.
‘xxxxxxxx’
Explanation: The volume sequence number exceeded
the number of volumes for the indicated ddname.
SYSOUT output for the job. xxxxxxxx
The ddname.
Source: DFSMSdfp
Application Programmer Response: Keep all related
data sets and listings for reference.
IDC1865I xxxxxxxx ADDITIONAL VOLUME
SERIAL NOT FOUND IN CHKPT DATA System Programmer Response: If the error recurs
SET and the program is not in error, look at the messages in
Explanation: Probable checkpoint logic error. A type 1 reporting data bases for a fix for the problem. If no fix
or type 2 DSDR indicated the presence of a type 2 exists, contact the IBM Support Center. Provide the JCL
DSDR which did not exist. for the job.
xxxxxxxx Detecting Module: IDCCK01
The additional volume serial number.
System Action: Incomplete CHKLIST information is IDC1870I ** IGNORED VSAM ERROR READING
listed. The system continues processing with the next CRA - CI ‘nn’X
checkpoint entry.
Explanation: A LISTCRA function encountered an I/O
Application Programmer Response: Keep all related error reading a catalog recovery area (CRA) record at
data sets and listing for reference. the specified control interval.
System Programmer Response: If the error recurs In the message text:
the job log for more information. Search problem nn The control interval number in hexadecimal.
reporting data bases for a fix for the problem. If no fix System Action: The system ignores the record. The
exists, contact the IBM Support Center. Provide the system continues processing as long as no more than
SYSOUT output for the job. 50 errors have been encountered while processing the
Source: DFSMSdfp LISTCRA command. When the number of errors
reaches 50, the system ends processing.
preceding message to determine the cause of the I/O
IDC1866I UNEXPECTED EOF ON CHECKPOINT error. Correct the problem. Run the job again.
DATA SET
Source: DFSMSdfp
Explanation: End-of-file occurred while processing
DSDRs. Detecting Module: IDCLR01, IDCCK01

CHKLIST utility. IDC1871I ** IGNORED VSAM ERROR READING
CATALOG - CI ‘nn’X
Application Programmer Response: Keep all related
data sets and listings for reference. Explanation: A LISTCRA function encountered an I/O
error reading a catalog record at the specified control
System Programmer Response: If the error recurs interval.

In the message text: The following list identifies each LISTCRA procedure
and the field for which it was searching when it
nn The control interval number in hexadecimal.
encountered the error:
System Action: The system ignores the record. The
CATOPEN The catalog name in the cluster
system continues processing as long as no more than
record of the catalog.
50 errors have been encountered while processing the
LISTCRA command. When the number of errors CKEYRNG The high key value in a given catalog
reaches 50, the system ends processing. recovery area (CRA) record.
Application Programmer Response: See the CRAOPEN Either the owning catalog name or the
preceding message to determine the cause of the I/O volume serial number in the CRA.
error. Correct the problem. Run the job again.
CTTBLD The entry type of the catalog CI in the
Source: DFSMSdfp CRA record.
Detecting Module: IDCLR01, IDCLR02 GETPRT The entry type or the entry name in
the CRA record.
IDC1875I ERROR TRANSLATING CRA CI FROM INTASOC The associated entry type or entry
CATALOG CI - ‘nn’X name fields in the CRA records.
Explanation: An error occurred when translating an INTSORT The name in a given CRA record.
entry’s catalog control interval number, which points at a
INTVEXT The extension pointer in a given CRA
related entry, to a catalog recovery area (CRA) control
record.
interval before reading the entry.
PRTCMP The used length field in a given CRA
record.
nn The catalog control interval number in
PRTDMP The used length field in a given CRA
hexadecimal.
record.
This will normally result from an incomplete entry PRTOJVL The volume information of high key
definition or an I/O error identified in a preceding value in a given CRA record.
message.
PRTVOL The volume time stamp information in
System Action: The system bypasses the error. The a given catalog or CRA record.
system continues processing. However, there may be
System Action: The system bypasses the error. The
minor errors in the list.
system continues processing. There may be minor
Application Programmer Response: Restore the errors in the list.
volume on which the error occurred to a previous valid
Application Programmer Response: Restore the
condition.
volume on which the error occurred to a previous valid
System Programmer Response: If the error recurs condition.
Source: DFSMSdfp and the SYSOUT output for the job.
Detecting Module: IDCLR01 Source: DFSMSdfp
Detecting Module: IDCLR01
IDC1878I xxxxxxxx IGNORED ERROR FROM
FIELD MANAGEMENT
IDC1880I IGNORED I/O ERROR READING
Explanation: An error occurred when called by VOLUME LABEL
LISTCRA.
Explanation: A LISTCRA command encountered an
In the message text: I/O error reading the format-4 data set control block
(DSCB) in the VTOC to obtain the time stamp
xxxxxxxx
information.
The LISTCRA procedure in control when the
error was detected. System Action: The system ignores the error. The
system does not print the time stamps.

IDC01884I UNBOUND LOCKS DELETED FOR
dsname
Explanation: A SHCDS FRDELETEUNBOUNDLOCKS
Source: DFSMSdfp
command was executed for data set dsname. Locks
Detecting Module: IDCLR01 being retained for the data set have been removed.
Source: DFSMSdfp
IDC1881I IGNORED OPEN FAILURE FOR
Detecting Module: IDCSH11
ALTERNATE OUTPUT DATA SET
Explanation: LISTCRA encountered an error
IDC01885I NON-RLS UPDATE PERMITTED FOR
attempting to open the alternate output data set.
dsname
System Action: The system ignores the error. The
Explanation: The data set that has been accessed in
system uses the output data set.
RLS mode is now permitted to be accessed in non-RLS
Application Programmer Response: If the output is mode.
desired in the alternate data set, determine the cause of
Source: DFSMSdfp
the error. Correct the error. Run the job again.
Source: DFSMSdfp
IDC01886I NON-RLS UPDATE DENIED FOR
dsname
IDC01880I RECOVERY SET FOR dsname
Explanation: A SHCDS FRSETRR command was non-RLS mode is now denied access in non-RLS mode.
executed for data set dsname.
Source: DFSMSdfp
Source: DFSMSdfp
IDC01887I SUBSYSTEM subsystem REMOVED
IDC01881I UNBIND SET FOR dsname
Explanation: The subsystem with connections
Explanation: A SHCDS FRUNBIND command was remaining for RLS is removed. All lock and subsystem
executed for data set dsname. The locks for the data connectivity information is deleted.
set have been unbound or disconnected from the data
Source: DFSMSdfp
set.
Source: DFSMSdfp
IDC1885I CRA RECORD COULD NOT BE READ
BY FIELD MANAGEMENT
IDC01882I BIND SET FOR dsname
Explanation: The Data Facility Product (DFP) called
Explanation: A SHCDS FRBIND command was by LISTCRA to read catalog recovery area (CRA) fields
executed for data set dsname. The locks for the data for the miscompare list was unable to return the
set have been bound or connected to the data set. requested field. This message normally results from an
I/O error identified in the preceding message.
Source: DFSMSdfp
System Action: The system bypasses the error. The
Detecting Module: IDCSH09 system continues processing. There may be minor
errors in the list.
IDC01883I RECOVERY RESET FOR dsname Application Programmer Response: Restore the
Explanation: A SHCDS FRRESETRR command was volume on which the error occurred to a previous valid
executed for data set dsname. condition. Contact your programming support personnel
and make sure the job stream and system output
Source: DFSMSdfp associated with this job is available for problem
Detecting Module: IDCSH10 determination. LRPM is the last access method services
diagnostic dump point before the error was detected.

exists, contact the IBM Support Center. Provide the JCL System Action: The system continues processing the
and the SYSOUT output for the job. command.
Source: DFSMSdfp System Programmer Response: If the error recurs
IDC1887I ERROR REFERENCING CRA ON and the SYSOUT output for the job.
VOLUME ser - REASON CODE cde
Source: DFSMSdfp
Explanation: In opening the catalog recovery area
Detecting Module: IDCDL01
(CRA) there was a problem indicated by the reason
code.
IDC01895I DATA SETS SUCCESSFULLY
PROCESSED
Explanation: An SHCDS CFREPAIR or CFRESET
cde The reason code, as follows: command was issued. The list of datasets successfully
processed is presented.
Code Explanation
Source: DFSMSdfp
3 Time stamp for volume was not
obtained. Detecting Module: IDCSH15, IDCSH16
6 I/O error reading the CRA record.

IDC1927I INVALID ‘MARGINS’ VALUES
System Action: The system continues processing. SPECIFIED, DEFAULT MARGINS
Application Programmer Response: This message ASSUMED
requires no action, but the problem causing it may Explanation: The left margin value specified in a
cause other messages that may require a response. MARGINS parameter is not strictly less than the right
Source: DFSMSdfp margin value. At least two character positions must be
provided.
System Action: The system assumes the default
margin values of 2 and 72.
IDC1890I RACF PROFILE COULD NOT BE
DELETED — NOT ELIGIBLE Application Programmer Response: Correct the
MARGINS specifications.
Explanation: As the result of a DELETE or EXPORT
command, a RACF indicated member was successfully System Programmer Response: If the error recurs
deleted. However, the RACF profile for this data set is and the program is not in error, look at the messages in
not eligible for deletion for one of these reasons: the job log for more information. Search problem
v RACDEF was failed by the installation exit.
v The resource name in the profile was not previously and the SYSOUT output for the job.
defined to RACF.
Source: DFSMSdfp
command. Detecting Module: IDCPM01

and the program is not in error, search problem IDC1968I VSAM TIME STAMP NOT UPDATED IN
reporting data bases for a fix for the problem. If no fix VTOC OF {FROM|TO} VOLUME volser
exists, contact the IBM Support Center. Provide the JCL Explanation: An error was encountered reading or
and the SYSOUT output for the job. updating the volume table of contents (VTOC) so the
Source: DFSMSdfp virtual storage access method (VSAM) time stamp was
not updated for the volume.
IDC1891I RACF PROFILE COULD NOT BE FROM|TO

DELETED — NOT FOUND Indicate which value encountered the error for
commands that process more than one value.
Explanation: As the result of a DELETE or EXPORT
command, a RACF indicated member was successfully volser The volume serial number.
deleted. However, the RACF profile for this data set System Action: The command ends normally if no
could not be found.
315
functions have been performed yet. If some functions catname
have been performed, the command continues The Catalog being deleted.
processing.
Operator Response: Reply ’Y’ to delete or ’N’ to
Application Programmer Response: Run the job cancel the command.
again if the job was not completed. If the function
System Programmer Response: To eliminate the
completed, use the SPZAP service aid to correct the
issuance of the WTOR see the Modify Catalog
VSAM time stamp or ignore the error.
command in MVS/ESA SYSTEM COMMANDS or the
System Programmer Response: If the error recurs DFSMS/MVS MANAGING CATALOG books.
Source: DFSMSdfp
reporting data bases for a fix for the problem. If no fix Detecting Module: IDCDL01
output and output data sets related to the problem. IDC1998I vvdsname AND ITS VVRS AND NVRS
ARE ABOUT TO BE DELETED REPLY
Source: DFSMSdfp ’Y’ TO DELETE ’N’ TO CANCEL.
Detecting Module: IDCVS01 Explanation: This message is an attention that a
VVDS is about to be deleted.
IDC1969I ALTERNATE TRACK DATA NOT In the message text:
RESTORED IN VTOC OF TO VOLUME
volser vvdsname
The VVDS being deleted.
Explanation: An error was encountered reading or
updating the volume table contents (VTOC) so the Operator Response: Reply ’Y’ to delete, or ’N’ to
alternate track information was not restored in the cancel the command.
VTOC of the target volume after the copy of data. A System Programmer Response: To eliminate the
previous message explains the error. issuance of the WTOR see the Modify Catalog
In the message text: command in MVS/ESA SYSTEM COMMANDS or the
DFSMS/MVS MANAGING CATALOG books.
Source: DFSMSdfp
Application Programmer Response: If the volume is
a Mass Storage Volume, ignore this error since
alternate tracks do not apply for Mass Storage Volumes. IDC2011I FUNCTION CANNOT BE EXECUTED.
INSUFFICIENT MAIN STORAGE.
If the volume is a real volume, use the AMASPZAP
service aid to place the information from the subsequent Explanation: An access method services function has
message into the VTOC. been requested that requires more virtual storage than
was available. Reasons for this message being issued
System Programmer Response: If the error recurs by the utility include the attempt to get storage by:
and the program is not in error, look at the messages in v IDCSS01 to build the output buffer.
reporting data bases for a fix for the problem. If no fix v IDCSS02 to add to the work area, or for storage for
exists, contact the IBM Support Center. Provide the the SSSCB.
JCL, the SYSOUT output for the job, and all printed v IDCSS05 to obtain pinned track or dsname areas, or
output and output data sets related to the problem. for storage for the SSSCB.
Source: DFSMSdfp v IDCSS06 for storage for the SSSCB.
v IDCSS07 for storage for the SSSCB.
v asynchronous operations manager (returns a return
code 4, reason code 4 to the utility).
IDC1997I catname AND ITS DATA SETS TO BE
DELETED, REPLY ’Y’ TO DELETE ’N’ System Action: The function requested was not
TO CANCEL. performed.
Explanation: This message is an attention that a Application Programmer Response: Run the job
Catalog is about to be deleted. again in a larger address space.


IDC2054I INVALID AUTHORIZATION TO
EXECUTE FUNCTION
for the job.
Explanation: A caller without the proper RACF facility
Source: DFSMSdfp
class authorization requested a function that involves a
Detecting Module: IDCLM01 storage management subsystem data set.
System Action: The system ends the request.
IDC2035I INVALID ERROR CONVERSION TABLE
Application Programmer Response: Acquire the
Explanation: An error was detected in the information proper RACF facility class authorization. Run the job
transmitted in the Error Conversion Table, when again.
attempting to convert a numeric error code to a prose
Source: DFSMSdfp
message.
Detecting Module: IDCTP06
System Action: The conversion request is ended.
IDC2055I ERROR DURING RETRIEVAL OF
ALLOCATION MESSAGES - RETURN
CODE WAS returncode REASON CODE
WAS rsncode
Explanation: An error occurred during calls to
Source: DFSMSdfp
dynamic allocation error message processor program
Detecting Module: IDCTP06 (IEFDB476) to return allocation messages, with the
return code, reason code from IEFDB476.
IDC2053I STEP CONTAINING JOBCAT/STEPCAT In the message text:

REFERENCES SMS-MANAGED DATA
returncode The return code.
SET
rsncode The reason code.
Explanation: A step that referenced an SMS-managed
data set contains one of the following: System Action: The function terminates.
v a JOBCAT DD statement Application Programmer Response: None.
v a STEPCAT DD statement
System Programmer Response: See the OS/390
v both a JOBCAT and a STEPCAT DD statement MVS Programming: Authorized Assembler Services
System Action: The system voids the step action for Guide for more explanation on the return code and
the SMS-managed data set. reason code from IEFDB476.
Application Programmer Response: Depending on Source: DFSMSdfp

the DD statements present in the step, take one of the Detecting Module: IDCTP06
following corrective actions:
v Remove the JOBCAT DD statement if there is no
IDC2065I ** UNABLE TO CLEAR
need for it.
SERIAL-MISMATCH FLAG FROM
v Remove the JOBCAT DD statement, and insert INVENTORY RECORD
STEPCAT DD statements only where required.
Explanation: A flag indicating a volume serial
v Remove the STEPCAT DD statement if there is no
mismatch between the cartridge labels and the volume
need for it.
label for a Mass Storage Volume could not be cleared
v If a single step references one or more from the Inventory data set. See the previous message
SMS-managed data sets and still requires a for further explanation of the problem.
STEPCAT DD statement, split the step into two or
more steps such that those steps referencing any System Action: The command ends with an error
SMS-managed data sets do not require a STEPCAT message.
DD statement. Application Programmer Response: Correct the
v Ensure that all referenced integrated catalog facility problem as identified in the previous message and take
(ICF) catalogs are connected to the system master the following actions for the command that failed:
catalog. v For a Rename operation failure for ADDV run ADDV
Source: DFSMSdfp to backout or retry the rename operation if the
volume is inactive. If the volume is active, run
Detecting Module: IDCTP06 MODIFYV or STOREV to either backout or retry the
rename operation.
317
If the ADDV, MODIFYV, or STOREV commands are System Programmer Response: If the error recurs
run to recover from a rename failure, a DD statement and the program is not in error, look at the messages in
for the volume is required and must specify deferred the job log for more information. Search problem
mounting. reporting data bases for a fix for the problem. If no fix
The values specified for the VOLUME and exists, contact the IBM Support Center. Provide the
NEWSERIAL parameters depend upon how the JCL, the SYSOUT output for the job, and all printed
volume record is recorded in the Inventory data set. If output and output data sets related to the problem.
the cartridge labels have been updated, the volume Source: DFSMSdfp
number. For the VOLUME parameter, specify the Detecting Module: IDCAV01, IDCMV01, IDCSR01
volume serial number as recorded in the cartridge
labels and the volume record. For the NEWSERIAL IDC2074I VOLUME ser NOT ACTIVE
parameter, specify the desired volume serial number.
Note that the security check for non-VSAM status Explanation: The specified volume is not active and is
and password protected data sets is bypassed only if recorded in the Inventory data set as inactive. The
the NEWSERIAL parameter specifies the same command issuing the message requires an active
volume serial number as recorded in the Inventory volume.
data set for the volume label. This allows the original
volume serial number of a VSAM volume to be
restored if the volume is left partially renamed. ser The volume serial number.
If ADDV, MODIFYV, or STOREV terminates without System Action: Processing of the command ends
indicating the status of the rename operation, with a message indicating the final condition code.
LISTMSVI can be run to determine whether the
volume is flagged for recovery purposes. If the Application Programmer Response: Run the ADDV
mismatch flag is set in the volume record, LISTMSVI command to activate the volume. Run the command
not only lists the standard information for the volume again. If the volume is already active but only the record
but also highlights the volume report with a note that indicates that the volume is inactive, contact the space
a rename operation failed for the preceding volume manager. The Inventory data set may need to be
and that serial number ‘nnnnnn’ is recorded in restored from the backup copy and the Journal data set.
volume label of the volume. System Programmer Response: If the error recurs
v For a Rename operation failure for MODIFYV, and the program is not in error, look at the messages in
recover from the failure by: the job log for more information. Search problem
– Running ADDV to activate the volume if the reporting data bases for a fix for the problem. If no fix
volume is merely inactive and has no volume exists, contact the IBM Support Center. Provide the
serial mismatch condition JCL, the SYSOUT output for the job, and all printed
– Running ADDV to both activate the volume and
complete the rename operation if the volume is Source: DFSMSdfp
both inactive and has a volume serial mismatch
condition Detecting Module: IDCLD01
– Run MODIFYV again to complete or retry the
rename operation if the volume is active but has a IDC2075I ** VOLUME volser CANNOT BE
mismatch condition ACTIVATED
– Run STOREV to complete or retry the rename Explanation: An attempt to make the specified volume
operation if the volume is active and if a duplicate active and mountable failed. See preceding message
volume serial number is desired as a result of the for further explanation of the failure.
rename.
For the DD statement requirements, the proper volser The volume serial number.
VOLUME and NEWSERIAL parameter values, and
use of LISTMSVI, refer to the description above for System Action: The command ends with an error
an ADDV rename failure. message.
v For a Rename operation failure for STOREV run Application Programmer Response: Run the
STOREV again or run MODIFYV to either backout or command again after:
retry the rename operation. v Reentering one or both cartridges if the cartridges are
For the DD statement requirements, the proper outside the Mass Storage Facility (MSF)
VOLUME and NEWSERIAL parameter values, and v Correcting the problem as indicated in the preceding
use of LISTMSVI, refer to the description above for message
an ADDV rename failure.

v Running the EJECTV command to eject the volume
IDC2078I ** COPY RECORDS FOR VOL volser
and then reentering the cartridges if the cartridges
CANNOT BE RETRIEVED
were originally entered while the Mass Storage
Volume Control (MSVC) was disabled. Explanation: An attempt to access a record in the
Inventory data set for an existing copy volume failed.
The base volume record indicates additional copy
volumes exist. The record for the next copy volume in
time stamp sequence cannot be read. See the
preceding message for further explanation of the failure.
output and output data sets related to the problem. In the message text:
Detecting Module: IDCAV01, IDCCV01, IDCMV01 System Action: The command ends with a message.
IDC2076I ** CART csn1 [csn2] NOT IN MSF FOR error as indicated in the preceding message.
COPY yyddd
Explanation: The cartridges assigned to the copy and the program is not in error, search problem
created on the indicated date cannot be found in the reporting data bases for a fix for the problem. If no fix
Mass Storage Facility (MSF). See preceding message exists, contact the IBM Support Center. Provide the
for additional information. JCL, the SYSOUT output for the job, and all printed
Source: DFSMSdfp
csn1
Detecting Module: IDCCO01, IDCLV01, IDCRR01,
csn2 The cartridge serial numbers that identify the
IDCSV01
sequence one and sequence two cartridges
not in the MSF.
IDC2079I ** RECORD FOR GROUP grpname
CANNOT BE RETRIEVED FROM
System Action: The command ends with a message INVENTORY
unless additional copies are specified for processing.
Explanation: An attempt to access the record in the
Application Programmer Response: Correct the Inventory data set for the specified group failed. See the
condition as indicated in the preceding message. Run preceding message for further explanation of the failure.
the command after:
v Reentering the missing cartridges
grpname
v Selecting another copy volume
The group name.
v If one of the cartridges is lost, running the
SCRATCHV command to make the remaining System Action: The command ends with a message
cartridge assigned to the volume scratch cartridge unless additional groups are specified for processing.
and to delete the record from the Inventory data set Application Programmer Response: Correct the
v Running the REMOVEVR command to delete the error as indicated in the preceding message. Verify that
record for the copy volume if both cartridges are lost the group name is specified correctly. Run the
command again.
and the program is not in error, search problem System Programmer Response: If the error recurs
reporting data bases for a fix for the problem. If no fix and the program is not in error, search problem
exists, contact the IBM Support Center. Provide the reporting data bases for a fix for the problem. If no fix
JCL, the SYSOUT output for the job, and all printed exists, contact the IBM Support Center. Provide the
output and output data sets related to the problem. JCL, the SYSOUT output for the job, and all printed
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCRV01, IDCSV01
Detecting Module: IDCAV01, IDCCV01, IDCLC01,
IDCLV01, IDCMG01, IDCMV01, IDCSD01
319
that one cartridge. See the preceding message for
IDC2080I ** RECORD FOR VOL volser CANNOT
further explanation of the failure.
BE RETRIEVED FROM INVENTORY
Explanation: An attempt to access the record in the
Inventory data set for the specified volume failed. See csn1
the preceding message for further explanation of the
failure. csn2 The cartridge serial numbers that identify the
sequence one and sequence two cartridges
In the message text: not scratched.
volser The volume serial number. yyddd The date, in year and days.
System Action: The system sends messages about System Action: The command continues processing.
the job to the job log.
Application Programmer Response: Correct the problem as indicated in the preceding message. If the
error as indicated in the preceding message. Before cartridges are out of the MSF, enter the cartridges into
running the command again check that the volume the MSF and run the command again. If the cartridges
serial number is specified correctly. are lost, run the REMOVEVR command to delete the
record for the copy from the Inventory data set. Run the
command again.
exists, contact the IBM Support Center. Provide the and the program is not in error, search problem
JCL, the SYSOUT output for the job, and all printed reporting data bases for a fix for the problem. If no fix
output and output data sets related to the problem. exists, contact the IBM Support Center. Provide the
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCN01, IDCCO01,
Source: DFSMSdfp
IDCLD01, IDCLV01, IDCMG01, IDCMV01, IDCRL01,
IDCRR01, IDCRV01, IDCSD01, IDCSR01, IDCSV01 Detecting Module: IDCCO01, IDCSV01
IDC2084I ** CARTRIDGES NOT EJECTED IDC2091I ** {READONLY|READWRITE}

ATTRIBUTE NOT SET FOR VOLUME
Explanation: The cartridges assigned to a Mass
volser
Storage Volume could not be ejected from the Mass
Storage Facility (MSF). If only one cartridge was in the Explanation: The specified volume could not be
MSF, an attempt to eject that one cartridge failed. See assigned the READONLY or READWRITE attribute.
the preceding message for further explanation of the READONLY may be required because the volume
failure. belongs to a group which has the READONLY attribute
specified for all general-use volumes. See the preceding
message for further explanation of the problem.
error as identified in the preceding message. Run the
command again. volser The volume serial number.
System Programmer Response: If the error recurs System Action: The command continues processing.
reporting data bases for a fix for the problem. If no fix Application Programmer Response: Run the
exists, contact the IBM Support Center. Provide the MODIFYV command to change the volume attribute to
JCL, the SYSOUT output for the job, and all printed READONLY or READWRITE.
output and output data sets related to the problem. System Programmer Response: If the error recurs
Source: DFSMSdfp and the program is not in error, search problem
Detecting Module: IDCCO01, IDCEV01, IDCSR01 exists, contact the IBM Support Center. Provide the
IDC2087I ** CART csn1 [csn2] NOT SCRATCHED
FOR COPY yyddd Source: DFSMSdfp
Explanation: The cartridges assigned to the copy Detecting Module: IDCAV01, IDCCV01, IDCMV01
volume created on the indicated date could not be
scratched. If only one cartridge was in the Mass
Storage Facility (MSF) an attempt was made to scratch

FROM|TO
IDC2093I ** VOLUME ATTRIBUTES NOT
Designate which volume is unusable for those
CHANGED TO AGREE WITH GROUP
commands processing both a source and
grpname
target volume having the same volume serial
Explanation: An attempt to change the attributes of a numbers.
general-use volume failed. The attributes of the volume
do not agree with the attributes specified for all
general-use volumes belonging to the specified group. System Action: The command ends with a message
See the preceding message for additional information reflecting the severity of the error.
on the problem.
The following are valid attributes: problem as identified in the preceding message and
v bind/nobind take the following actions for the command that failed:
v exclusive/shared v For a Rename operation failure for ADDV, run ADDV
to backout or retry the rename operation if the
v readonly/readwrite
v dasderase/nodasderase MODIFYV or STOREV to either backout or retry the
v pagefault/nopagefault rename operation.
In the message text: run to recover from a rename failure, a DD statement
grpname for the volume is required and must specify deferred
The group name mounting. The values specified for the VOLUME and
System Action: The command continues processing. volume record is recorded in the Inventory data set. If
the cartridge labels have been updated, the volume
Application Programmer Response: Run the
LISTMSVI command to list the information recorded in
number.
the Inventory data set about the group. After
determining the volume attributes specified at the group For the VOLUME parameter, specify the volume
level, run the MODIFYV command to update the volume serial number as recorded in the cartridge labels and
attributes to agree with the group specifications. the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number. Note that
If there are many volumes in the group whose attributes the security check for non-VSAM status and
do not agree with the group, run the MODIFYG password protected data sets is bypassed only if the
command to request a change of the group attributes. If NEWSERIAL parameter specifies the same volume
you specify the same attributes on the MODIFYG serial number as recorded in the Inventory data set
command as are recorded already in the group record, for the volume label. This allows the original volume
MODIFYG will still change the attributes of all the active serial number of a VSAM volume to be restored if the
general-use volumes for the group. volume is left partially renamed.
System Programmer Response: If the error recurs If ADDV, MODIFY, or STOREV terminates without
and the program is not in error, search problem indicating the status of the rename operation,
reporting data bases for a fix for the problem. If no fix LISTMSVI can be run to determine whether the
exists, contact the IBM Support Center. Provide the volume is flagged for recovery purposes. If the
JCL, the SYSOUT output for the job, and all printed mismatch flag is set in the volume record, LISTMSVI
output and output data sets related to the problem. not only lists the standard information for the volume
but also highlights the preceding volume and that
Source: DFSMSdfp
serial number nnnnnn is recorded in the volume label
Detecting Module: IDCAV01, IDCMV01 of the volume.
v For a Rename operation failure for MODIFYV,
IDC2095I {FROM|TO} VOLUME volser recover from a MODIFYV by:
INCOMPLETELY RENAMED IN A PRIOR – Running ADDV to activate the volume if the
OPERATION volume is merely inactive and has no volume
serial mismatch condition
Explanation: The specified column cannot be used. A
previous MODIFYV, ADDV, or STOREV command – Running ADDV to both activate the volume and
ended before completely changing the volume serial complete the rename operation if the volume is
number of the volume. The volume serial number on the both inactive and has a volume serial mismatch
cartridge labels and in the Inventory record does not condition
agree with the volume serial number in the volume – Running MODIFYV again to complete or retry the
label. rename operation if the volume is active but has a
mismatch condition
321
– Running STOREV to complete or retry the rename to the target volume that is flagged as an incomplete
operation if the volume is active and if a duplicate copy volume. Otherwise, run SCRATCHV to scratch
volume serial number is desired as a result of the the target volume. The incomplete copy volume may
rename even be used as the target volume in the
CONVERTV command. In all cases, the empty
For the DD statement requirements, the proper volume table of contents (VTOC) check or security
VOLUME and NEWSERIAL parameter values, and check for password protected data sets is bypassed.
use of LISTMSVI, refer to the description above for If the SCRATCHV command is run, the DD statement
an ADDV rename failure. is not required for the volume and if provided, must
System Programmer Response: If the error recurs specify deferred mounting. If the RECOVERV
and the program is not in error, search problem command is run again, the DD statement is not
reporting data bases for a fix for the problem. If no fix required for the target volume, which is flagged as an
exists, contact the IBM Support Center. Provide the incomplete copy, unless the volume serial number of
JCL, the SYSOUT output for the job, and all printed the target volume is different from the source volume.
output and output data sets related to the problem. If a DD statement is provided for the target volume,
deferred mounting must be specified. If a VSAM
Source: DFSMSdfp catalog is on the volume, a DD statement for the
catalog is not required; if provided, deferred mounting
Detecting Module: IDCAV01, IDCLD01, IDCSD01,
must be specified.
IDCRV01, IDCEV01, IDCMG01, IDCMV01, IDCSR01,
IDCSV01, IDCCN01, IDCCO01 If RECOVERV terminates without indicating the
status of the recover operation, LISTMSVI can be run
to determine whether the volume is flagged for
IDC2096I {FROM|TO} VOLUME volser recovery purposes. If the incomplete copy flag is set
INCOMPLETELY COPIED IN A PRIOR in the target volume record, LISTMSVI not only lists
OPERATION the standard information for the volume but also
Explanation: The specified volume was incompletely highlights the volume report with a note that a copy
copied by the COPYV, RECOVERV, or CONVERTV operation failed for the preceding volume.
commands and cannot be used. v For a Copy operation failure for CONVERTV, run
CONVERTV again to complete the conversion
operation to the target volume that is flagged as an
FROM|TO incomplete copy volume. Otherwise, run SCRATCHV
Designate which volume is unusable for those to scratch the target volume. The incomplete copy
commands processing both a source and volume may even by used as the target volume in
target volume having the same volume serial the RECOVERV command. In all cases, the empty
number. VTOC check or the security check for password
protected data sets is bypassed.
If the SCRATCHV command is run, the DD statement
System Action: The command terminates with a is not required for the incompletely copied volume
message containing the severity code. and if provided, must specify deferred mounting. If a
VSAM catalog is on the volume and a DD statement
for the target volume must be provided and must
problem as indicated in the preceding message. Then,
specify deferred mounting. If a VSAM catalog is on
take one of the following actions for the command that
the volume and a DD statement is provided for the
failed:
catalog, the DD statement must also specify deferred
v For a Copy operation failure in COPYV, run COPYV mounting.
again to complete the copy operation to the
If CONVERTV ends without indicating the status of
incomplete copy volume. COPYV will reuse the
the conversion operation, LISTMSVI can be run to
cartridges of the incomplete copy volume for the new
determine whether the volume is flagged for recovery
copy. Or run SCRATCHV to scratch the incomplete
purposes. If the incomplete copy flag is set in the
copy volume before rerunning the COPYV command.
target volume record, LISTMSVI not only lists the
IF COPYV ends without indicating the status of the standard information for the volume but also
copy operation, LISTMSVI can be run to determine highlights the volume report with a note that a copy
whether the volume is flagged for recovery purposes. operation failed for the preceding volume.
If the incomplete copy flag is set in the copy volume
record, LISTMSVI not only lists the standard System Programmer Response: If the error recurs
information for the volume but also highlights the and the program is not in error, search problem
volume report with a note that a copy operation failed reporting data bases for a fix for the problem. If no fix
for the preceding copy volume. exists, contact the IBM Support Center. Provide the
v For a Copy operation failure for RECOVERV, run
RECOVERV again to complete the recover operation

Source: DFSMSdfp System Action: The command continues processing.
Detecting Module: IDCAV01, IDCCO01, IDCLD01, Application Programmer Response: Correct the
IDCSD01, IDCSR01, IDCRV01, IDCEV01, IDCMG01, error. Recatalog the data set using IEHPROGM utility or
IDCMV01, IDCCN01 the access method services DELETE and DEFINE
commands.
IDC2097I {FROM|TO} VOLUME volser System Programmer Response: If the error recurs
INCOMPLETELY CREATED IN A PRIOR and the program is not in error, look at the messages in
OPERATION the job log for more information. Search problem
Explanation: The specified volume was incompletely
created by the CREATEV command and could not be
used.
Source: DFSMSdfp
FROM|TO
Designate which volume is unusable for those
commands processing both a source and
target volume having the same volume serial IDC2101I CATALOG RETURN CODE FOR RECAT
number. REQUEST WAS return-code - REASON
CODE rsncde
Explanation: The return code from an OS/VS
System Action: The command ends with a message
recatalog request was specified. The reason code in
reflecting the severity of the error.
register 0 was specified. A subsequent message
Application Programmer Response: Before creating identifies the data set not cataloged.
the volume using the CREATEV command run the
SCRATCHV command to scratch the partially created
volume. In the SCRATCHV run, there must be no DD return-code The return code.
statement for the partially created volume. The empty
rsncode The reason code.
volume table of contents (VTOC) check is bypassed.
and the program is not in error, look at the messages in Application Programmer Response: Correct the
the job log for more information. Search problem error and recatalog the data set using the IEHPROGM
reporting data bases for a fix for the problem. If no fix utility or the Access Method Services DELETE and
exists, contact the IBM Support Center. Provide the DEFINE commands.
output and output data sets related to the problem. System Programmer Response: If the error recurs
Source: DFSMSdfp the job log for more information. If the error recurs and
the program is not in error, search problem reporting
Detecting Module: IDCAV01, IDCLD01, IDCSD01,
data bases for a fix for the problem. If no fix exists,
IDCSR01, IDCRV01, IDCMG01, IDCMV01, IDCCN01,
contact the IBM Support Center. Provide the JCL, the
IDCEV01, IDCCO01
SYSOUT output for the job, and all printed output and
IDC2100I CATALOG RETURN CODE FOR
Source: DFSMSdfp
LOCATE REQUEST WAS return-code
Explanation: The return code from an OS/VS locate
request was specified. The error was detected either in
the virtual storage access method (VSAM) or OS IDC2103I VOLUME IN RECORD CHAIN CANNOT
Catalog Management. The subsequent message BE RETRIEVED
identifies the data set not recataloged. During a
CONVERTV operation, if the data set was cataloged in Explanation: An Inventory data set error caused a
a VSAM user catalog on the converted volume, the data break in the group or non-grouped volume chain. The
set may have been recataloged, and this message can next record in the chain either was not found, or the
be ignored. record indicates that it does not belong in the chain
being processed. A reason code of X‘208’ or X‘224’ was
In the message text: returned from the Mass Storage Volume Control
functions. The error may be caused by another
return-code
command updating the Inventory data set while this
The reason code.
command is running.
323
System Action: The system continues processing with JCL, the SYSOUT output for the job, and all printed
the next group if the request is for grouped volumes. If output and output data sets related to the problem.
the request is for non-grouped volumes, the system
Source: DFSMSdfp
ends processing.
command again. If there is a permanent Inventory data
set error, contact the system programmer. IDC2110I ** REMAINING VOLUMES IN GROUP
grpname CANNOT BE PROCESSED
and the program is not in error, look at the messages in Explanation: An Inventory data set error occurred to
the job log for more information. Search problem prevent processing down the volume chain for the
reporting data bases for a fix for the problem. If no fix specified group. The problem may be temporary, or the
exists, contact the IBM Support Center. Provide the Inventory data set may have permanent errors. A
JCL, the SYSOUT output for the job, and all printed preceding message indicates the type of error
output and output data sets related to the problem. encountered with the Inventory data set.
Source: DFSMSdfp In the message text:
Detecting Module: IDCLD01, IDCSD01 grpname
The group name.
IDC2108I ** UNABLE TO PROCESS VOLUME ser System Action: The system continues processing with
the next group. If there are no more groups, the
Explanation: The specified volume cannot be
command ends.
processed. A preceding message indicates the reason
why the volume cannot be processed. Application Programmer Response: Refer to the
preceding message to determine why processing for
this group ended. Contact the system programmer to
ser The volume serial number. correct the Inventory data set if necessary. Run the
command again.
System Action: The command continues with the next
volume to be processed. If there are no more volumes, System Programmer Response: If the error recurs
the command ends. and the program is not in error, look at the messages in
Application Programmer Response: Determine from
the preceding message whether a problem exists, and
correct it. Run the command again to process the
volume.
Problem Determination: Follow the problem
Source: DFSMSdfp
determination steps for the preceding message.
Source: DFSMSdfp
IDC2111I ** REMAINING GROUPS CANNOT BE
PROCESSED
IDC2109I ** REMAINING VOLUMES CANNOT BE
Explanation: An error occurred in the Inventory data
PROCESSED
set that prevented any more group records from being
Explanation: An error occurred in the Inventory data read. A preceding message indicates the type of
set that prevents any more volume records from being Inventory data set error.
read. Remaining volumes cannot be processed by the
System Action: The command ends.
command. A preceding message indicates the type of
error encountered with the Inventory data set. Application Programmer Response: Refer to the
preceding message for the type of Inventory data set
error.
Application Programmer Response: Contact the
system programmer to correct the problem with the
Inventory data set.
System Programmer Response: If the error recurs reporting data bases for a fix for the problem. If no fix
and the program is not in error, look at the messages in exists, contact the IBM Support Center. Provide the
the job log for more information. Search problem JCL, the SYSOUT output for the job, and all printed
reporting data bases for a fix for the problem. If no fix output and output data sets related to the problem.
Source: DFSMSdfp

Detecting Module: IDCLD01, IDCSD01 reporting data bases for a fix for the problem. If no fix
IDC2118I ** SCRATCH RECORD FOR GROUP
grpname CANNOT BE RETRIEVED
Source: DFSMSdfp
Explanation: The scratch record for the specified
group cannot be retrieved because either: Detecting Module: IDCLV01
v The attempt to access a scratch record in the
inventory data set for the group failed IDC2160I INVALID REFERENCE TO VOLUME
v The scratch record did not contain volumes xxxxxx, OBJECT BYPASSED
scheduled for processing by the system-initiated
Explanation: EXPORTRA has encountered a virtual
scratch function.
storage access method (VSAM) object that references a
volume entry that contains no reference to the object.
See the preceding message for further explanation of
This may be the result of a system failure during a prior
the failure.
delete operation.
grpname xxxxxx Indicates the volume.

The group name.
System Action: EXPORTRA bypasses the VSAM data
System Action: The command ends with this set and its associations.
message unless additional groups are specified for
Application Programmer Response: Copy the data
processing.
on valid volumes using the REPRO command. Delete
Application Programmer Response: Correct the the data set using the DELETE command. The data set
error specified in the preceding message. Before cannot be opened for output.
running the command again, check that the group name
is specified correctly.
and the program is not in error, search problem exists, contact the IBM Support Center. Provide the
reporting data bases for a fix for the problem. If no fix JCL, the SYSOUT output for the job, and all printed
exists, contact the IBM Support Center. Provide the output and output data sets related to the problem.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCLV01
IDC2360I CATALOG ENTRY FOR DATA SET
INDICATES DIFFERENT DEVICE TYPE
IDC2119I ** CATALOG RECORD FOR GROUP
Explanation: The ULOCATE function, after locating a
grpname CANNOT BE RETRIEVED
data set name in the catalog, determined that the data
Explanation: An attempt to access the catalog record set resides on a device type other than the catalog
in the inventory data set for the specified group failed. indicates, or else a duplicate data set name exists.
See the preceding message for further explanation of
System Action: The system continues processing with
the failure.
the next data set on the volume.
Application Programmer Response: If the device
grpname type is incorrect, uncatalog the data set and then
The group name. recatalog it with the correct device type.
System Action: The command ends with this System Programmer Response: Issue the access
message unless additional groups are specified for method services LISTCAT command to list catalog
processing. entries and information about objects defined in the
catalog.
error specified in the preceding message. Verify that the If the error recurs and the program is not in error, look
group name is specified correctly. Run the command at the messages in the job log for more information.
again. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support
System Programmer Response: If the error recurs Center. Provide the JCL, the SYSOUT output for the
325
job, and all printed output and output data sets related JCL, the SYSOUT output for the job, and all printed
to the problem. output and output data sets related to the problem.
Detecting Module: IDCSA07 Detecting Module: IDCIO05
IDC2364I CATALOG ENTRY TYPE FOR DATA IDC2371I UNABLE TO OBTAIN STORAGE FOR
SET IS OTHER THAN NON-VSAM I/O PROCESSING
Explanation: The ULOCATE function, after locating a Explanation: There was insufficient storage to perform
data set name in the catalog, determined that the the necessary I/O processing.
catalog entry type was not for a virtual storage access
System Action: The command ends normally.
method (VSAM) data set, or else a duplicate data set
name exists. Application Programmer Response: Increase the
region size for the job. Run the command again.
the next data set on the volume. System Programmer Response: If the error recurs
Application Programmer Response: If the data set
entry is cataloged, rerun the SCRDSET command after
restructuring the STEPCAT concatenation.
System Programmer Response: Issue the access JCL, the SYSOUT output for the job, and all printed
method services LISTCAT command to list catalog output and output data sets related to the problem.
Source: DFSMSdfp
catalog.
If the error recurs and the program is not in error, look
at the messages in the job log for more information.
Search problem reporting data bases for a fix for the IDC2372I OPEN ABEND EXIT {dsname|VTOC}
Center. Provide the JCL, the SYSOUT output for the Explanation: The OPEN macro encountered an error
job, and all printed output and output data sets related that resulted in the OPEN DCB ABEND exit being
to the problem. entered. This error prevented the opening of the data
control block (DCB) and stopped further I/O processing.
Source: DFSMSdfp The specified data set or the volume table of contents
(VTOC) was being opened.
IDC2370I UNABLE TO READ JFCB FOR DD dsname
ENTRY ddname RDJFCB CODE x The data set name.
Explanation: The system was not able to read the job System Action: The command ends normally.
file control block (JFCB) for the specified DD statement.
The RDJFCB macro return code was specified. This Application Programmer Response: Examine the
condition generally occurs when the DD statement was write-to-programmer message issued by the OPEN
not supplied. macro for the specific error code. Correct the problem.
Run the command again.
ddname and the program is not in error, look at the messages in
The data definition name. the job log for more information. Search problem
x The macro return code.
System Action: The command ends normally. JCL, the SYSOUT output for the job, and all printed
Application Programmer Response: Ensure the DD
name in the FILE parameter is correct and there is a Source: DFSMSdfp
corresponding DD statement in the JCL statements.

IDC2373I INVALID PASSWORD dsname
Explanation: One of the following errors occurred:
write-to-programmer message issued by the CLOSE
v The operator did not supply the correct password for macro for the specific error. Correct the problem. Run
the specified non-VSAM data set, for the specified the command again if the function was not performed.
VSAM unique data or index component, or for a data
or index component within the specified VSAM data System Programmer Response: If the error recurs
space. and the program is not in error, look at the messages in
v There is no JOBCAT or STEPCAT DD statement for
the VSAM catalog that owns the volume.
dsname
Source: DFSMSdfp
The data set name.
System Action: The command ends normally. The
requested function cannot be performed.
IDC2375I **I/O ERROR volser IOS RC =
Application Programmer Response: If the operator
return-code
supplied the incorrect password, do the following:
v Tell the system operator the correct password. The Explanation: An I/O error occurred from the
operator is prompted for the password that command.
corresponds to: In the message text:
1. The data or index component name or code word
(VSAM data sets)
2. The name of the DD statement for the data set return-code The IOS completion code, that comes
(non-VSAM data sets). from the IOSCOD field of the IOSB
data area.
Rerun the command. System Action: The system ends processing of the
command.
If there is no JOBCAT or STEPCAT DD statement for
the VSAM catalog, do the following: Application Programmer Response: This is a
probable subsystem problem. Correct any error. Run the
v Supply a JOBCAT or STEPCAT DD statement for the
command again.
catalog or supply the master password of the VSAM
catalog on the command or via operator prompting. Source: DFSMSdfp
IDC2376I SECURITY VIOLATION dsname
reporting data bases for a fix for the problem. If no fix Explanation: One of the following errors occurred:
exists, contact the IBM Support Center. Provide the v The system operator did not supply the correct
JCL, the SYSOUT output for the job, and all printed password for the non-VSAM data set for the virtual
output and output data sets related to the problem. storage access method (VSAM) unique data or index
Source: DFSMSdfp component, or for a data or index component within
the specified VSAM data space.
v There is no JOBCAT or STEPCAT DD statement for
the VSAM catalog that owns the volume.
IDC2374I CLOSE ABEND EXIT {dsname|VTOC} v The user does not have the proper RACF
Explanation: The CLOSE macro encountered an error authorization to the VSAM unique data or index
that resulted in the CLOSE DCB ABEND exit being component or for a data or index component within
entered. This error prevented the closing of the DCB the specified VSAM data space.
and stopped further I/O processing. The specified data
set or volume table of contents (VTOC) was being In the message text:
closed. dsname
In the message text: The data set name.
dsname System Action: The command ends normally. The

The data set name. requested function is not performed.
327
Application Programmer Response: If the operator
IDC2386I UNIT ASSIGNED TO ddname COULD
supplied the incorrect password, tell the system
NOT BE READIED FOR MOUNTING
operator the correct password. The operator is
prompted for the password that corresponds to the data Explanation: The unit assigned by the DD statement
or index component name or code word (VSAM data cannot be used to mount needed volumes, because a
sets) or the name of the DD statement for the data set previous volume cannot be demounted.
(non-VSAM data sets). Reissue the command.
If there is no JOBCAT or STEPCAT DD statement for
ddname
the VSAM catalog, supply a JOBCAT or STEPCAT DD
The data definition name.
statement for the catalog or supply the master password
of the VSAM catalog on the command or through the System Action: The command ends normally.
use of operator prompting. Reissue the command.
If the protection violation occurred for a RACF-protected command again. Specify the correct volume serial on
VSAM component, acquire the proper RACF user the DD statement. If the same unit is assigned to the
authorization to all RACF-protected VSAM components DD statement and the same error occurs, run the
on the volume or the VSAM catalog that owns the command again after the operator varies the unusable
volume. Reissue the command. unit offline.
System Programmer Response: If the error recurs System Programmer Response: If the error recurs
and the program is not in error, look at the messages in and the program is not in error, look at the messages in
the job log for more information. Search problem the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the exists, contact the IBM Support Center. Provide the
JCL, the SYSOUT output for the job, and all printed JCL, the SYSOUT output for the job, and all printed
output and output data sets related to the problem. output and output data sets related to the problem.
Detecting Module: IDCIO05 Detecting Module: IDCSA06
IDC2381I VOLUME WITH SERIAL volser IDC2387I ** VOLUME volser COULD NOT BE
ALREADY MOUNTED IN SYSTEM MOUNTED
Explanation: After mounting the specified mass Explanation: The mount of the specified volume is
storage volume the user control block (UCB) cannot be unsuccessful. A preceding message gives the
posted because it causes a duplication of volume label explanation for this error.
within the system.
System Action: The system demounts the mass
storage volume. The command ends normally. Application Programmer Response: Examine the
preceding message and correct the problem. Run the
Application Programmer Response: Run the command again.
command again after the volume with the same serial
number is demounted. System Programmer Response: If the error recurs
System Programmer Response: If the error recurs the job log for more information. Search problem
the job log for more information. Search problem exists, contact the IBM Support Center. Provide the
reporting data bases for a fix for the problem. If no fix JCL, the SYSOUT output for the job, and all printed
exists, contact the IBM Support Center. Provide the output and output data sets related to the problem.
output and output data sets related to the problem. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCSA06

return-code The return code.
IDC2388I ** VOLUME volser COULD NOT BE
DEMOUNTED System Action: The system does not continue the
function.
Explanation: The demount of the specified volume is
unsuccessful. A preceding message gives the Application Programmer Response: Examine the
explanation for this error. return code and correct the problem. Run the command
again.
System Action: The command ends normally. the job log for more information. Search problem
preceding message and correct the problem. Run the
command again.
Source: DFSMSdfp
the job log for more information. Search problem Detecting Module: IDCSA06
IDC2399I CATALOG ENTRY FOR DATA SET
INDICATES DIFFERENT VOLUME
Explanation: The ULOCATE function, after locating
Source: DFSMSdfp
the data set name in the catalog, determined that the
Detecting Module: IDCSA06 data set resides on a different volume than the catalog
indicates, or else a duplicate data set name exists.
IDC2390I VOLUME volser COULD NOT BE System Action: The system continues processing with
ENQUEUED FOR EXCLUSIVE USE the next data set on the volume.
Explanation: The enqueue of the specified volume for Application Programmer Response: Uncatalog the
exclusive use cannot be done because the volume data set, then recatalog it with the correct volume serial
serial is enqueued for shared use. number.
In the message text: System Programmer Response: Issue the access
System Action: The command ends normally. catalog.
Application Programmer Response: Run the If the error recurs and the program is not in error, look
command again after the volume is not being used by at the messages in the job log for more information.
any other job. Specify the volume serial on the DD Search problem reporting data bases for a fix for the
statement. problem. If no fix exists, contact the IBM Support
Center. Provide the JCL, the SYSOUT output for the
System Programmer Response: If the error recurs job, and all printed output and output data sets related
and the program is not in error, look at the messages in to the problem.
IDC2533I MEMBER CANNOT BE SPECIFIED
Source: DFSMSdfp
WITH A GENERIC NAME
Explanation: A generic entry name was given followed
by a member name in parentheses, which is not an
IDC2391I UNABLE TO ESTABLISH E/STAE allowable combination.
ENVIRONMENT - RETURN CODE
X'return-code'
Explanation: The STAE or ESTAE macro returned a
asterisk (*) indicating a generic entry name or remove
non-zero return code that prevented recovery protection
the member name to achieve the desired alteration.
in case of an abnormal end of the command.
Source: DFSMSdfp
329
Detecting Module: IDCAL01 System Action: The system ends processing for this
entry.
IDC2552I ENTRY TYPE IS INVALID FOR DELETE Application Programmer Response: Refer to the
dynamic allocation error messages or supply a FILE
Explanation: The caller attempted to delete an entry
parameter.
type that cannot be deleted. The only types of entries
that can be deleted are as follows: System Programmer Response: If the error recurs
v Cluster and the program is not in error, look at the messages in
v User the job log for more information. Search problem
v Catalog reporting data bases for a fix for the problem. If no fix
v Master catalog exists, contact the IBM Support Center. Provide the JCL
v Non-VSAM and the SYSOUT output for the job. Obtain the ABEND
v Space dump for the failing job step.
v Alias
Source: DFSMSdfp
v GDG base
v Path and alternate index
IDC2557I SCRATCH NOT AVAILABLE FOR TYPE
System Action: The system does not delete the entry.
OF OBJECT TO BE DELETED
The rest of the entries are deleted if possible.
Explanation: The SCRATCH option is incorrect for the
Application Programmer Response: If the caller
entry type being deleted. SCRATCH is incorrect for a
thinks the entry is one of these types, he should list that
virtual storage access method (VSAM):
entry with LISTCAT to check the type field.
v Master catalog
System Programmer Response: If the error recurs v User catalog
and the entry type is listed as valid in the LISTCAT, v Path
search problem reporting data bases for a fix for the v Alias
problem. If no fix exists, contact the IBM Support v GDG base
Center. Provide the JCL and the SYSOUT output for the
System Action: The system ends processing for the
job.
entry.
Source: DFSMSdfp
Application Programmer Response: Ensure that
Detecting Module: IDCAL01 SCRATCH is valid for all entries specified, or do not use
the SCRATCH option.
IDC2553I ERASE OPTION IS INVALID FOR Source: DFSMSdfp
ENTRY TYPE
Explanation: Only virtual storage access method
(VSAM) clusters and alternate indexes can be erased.
IDC2559I MEMBER CANNOT BE SPECIFIED
System Action: The system does not delete the entry. WITH A GENERIC NAME
The remaining VSAM entries, if any, are deleted.
Explanation: The generic name used is followed by a
Application Programmer Response: Submit the member name enclosed in parentheses. This
request again without the ERASE parameter. combination is incorrect.
System Programmer Response: If the error recurs System Action: The system ends processing for the
and the program is not in error, look at the messages in entry.
asterisk (*) which indicates a generic entry name or
remove the member name.
JCL, the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCDL01 the job log for more information. Search problem
IDC2554I DYNAMIC ALLOCATION FAILED OR
FILE WAS NOT CODED WITH
SCRATCH Source: DFSMSdfp
Explanation: A dynamic allocation failed. Preceding Detecting Module: IDCDL01
messages (prefixed by IKJ) indicate the reason for the
failure.

IDC2563I ALLOCATION/VOLUME PARAMETER IS
INVALID FOR ENTRY TYPE(S)
IDC2620I OBJECT TYPE NOT SUPPORTED FOR
Explanation: A LISTCAT command request for
OBJECT dsname
allocation or volume information conflicts with the
desired entries or types of entries. Explanation: A duplicate data set name was found in
the virtual storage access method (VSAM) catalog while
System Action: The LISTCAT command attempts
attempting to convert an OS catalog entry.
recovery to list that part of the request that does not
conflict. The portable data set format is not supported on this
system for one of the following reasons:
v The object is empty.
again with LISTCAT parameters that are compatible
v The object has the NOALLOCATE attribute.
with the fields specification.
v The object has the SAM ESDS attribute.
and the program is not in error, search problem In the message text:
exists, contact the IBM Support Center. Provide the JCL dsname
and the SYSOUT output for the job. The data set name.
Source: DFSMSdfp System Action: An associated message identifies the

entry not converted.
Application Programmer Response: Resolve the
duplicate name.
IDC2616I PATH path WAS NOT SUCCESSFULLY
IMPORTED System Programmer Response: If the error recurs
Explanation: IMPORT was not able to define the job log for more information. Search problem
successfully path over the object being imported. The reporting data bases for a fix for the problem. If no fix
most likely cause is a duplicate object name already in exists, contact the IBM Support Center. Provide the JCL
the catalog. and the SYSOUT output for the job.
path The path object. Detecting Module: IDCMP01
System Action: The system continues processing,
attempting to define any remaining paths whose catalog IDC2621I IMPORTRA FAILED FOR obj
information is stored on the portable data set.
Explanation: The object named could not be
Application Programmer Response: Determine if the imported. The preceding messages will give the reason
paths whose defines failed already exist in the catalog. for the failure.
If so, delete and redefine them.
Source: DFSMSdfp
obj The specified object.
the next object on the portable data set unless one of
IDC2618I INVALID OBJECTS SUBPARAMETER the following conditions exists:
FOR PATH path v A failure occurred while attempting to alter the name
Explanation: An OBJECTS subparameter other than of the cluster to or from the dummy name provided in
NEWNAME or FILE was specified for path object. the OUTFILE DD statement. (Message IDC3619I
precedes this message.)
v An error occurred while trying to read the portable
path The path object. data set.
System Action: The system continues IMPORT
In both cases, the command ends.
processing, attempting to define any remaining paths
from the portable data set. Application Programmer Response: Determine the
cause of the failure by examining previous messages on
the SYSPRINT output. Correct the indicated error. Run
error. Correct the OBJECTS parameter. Submit the job
the job again.
again.
Source: DFSMSdfp
Source: DFSMSdfp
331
Detecting Module: IDCRM01
IDC2642I dsname NOT RELATED TO BASE
Explanation: The specified data set is an alternate
IDC2630I DUPLICATE DATA SET NAME IN
index or a path over an alternate index, but the
TARGET CATALOG
alternate index is not related to the base cluster
Explanation: A duplicate data set name was found in identified by the INFILE or INDATASET parameter. All
the target catalog while attempting to convert an OS or alternate indexes identified by the OUTFILE or
virtual storage access method (VSAM) catalog entry. OUTDATASET parameter of the BLDINDEX command
must have been defined as being related to the base
System Action: An associated message identifies the cluster identified by the INFILE or INDATASET
entry not converted. parameter. This relationship is established by the
Application Programmer Response: Resolve the RELATE parameter in the DEFINE ALTERNATEINDEX
duplicate name. command.

and the program is not in error, look at the messages in dsname
the job log for more information. Search problem The data set name.
exists, contact the IBM Support Center. Provide the JCL System Action: The system sends processing for this
and the SYSOUT output for the job. alternate index. However, the system continues
processing for any other alternate indices identified by
Source: DFSMSdfp the OUTFILE or OUTDATASET parameter.
Detecting Module: IDCRM01 Application Programmer Response: Either the
alternate index identified by the OUTFILE or
IDC2640I dsname NOT AN AIX OUTDATASET parameter or the base cluster identified
by the INFILE or INDATASET parameter must be
Explanation: The specified data set is not an alternate corrected so that the proper relationship exists. If the
index or a path over an alternate index. The data set alternate index was defined improperly, it must be
name was specified in either the: deleted and redefined with the proper relationship
v Job control identified through the OUTFILE dname specified in the RELATE parameter. Submit the job
subparameter again.
v OUTDATASET dsname subparameter System Programmer Response: If the error recurs
The OUTFILE data set must be a defined alternate reporting data bases for a fix for the problem. If no fix
index or a path over the alternate index. exists, contact the IBM Support Center. Provide the JCL
Source: DFSMSdfp
dsname
The data set name. Detecting Module: IDCBI01
System Action: The system ends processing for this

OUTFILE or OUTDATASET subparameter. However, the IDC2647I INSUFFICIENT STORAGE TO OBTAIN
system continues processing with any other BUFFERS AND WORK AREAS
subparameters specified in the OUTFILE or Explanation: BLDINDEX encountered a failure when
OUTDATASET parameter. attempting to obtain storage for buffers, work areas and
Application Programmer Response: Correct the data a minimum sort area. BLDINDEX is the amount of
set name in the job control identified by the OUTFILE storage required to build one alternate index. The name
dname subparameter or the data set name specified in of the alternate index is given in a subsequent
the OUTDATASET subparameter to be a defined message.
alternate index or a path over an alternate index. System Action: The system ends processing for this
Submit the job again. alternate index. However, BLDINDEX attempts to
System Programmer Response: If the error recurs process any other alternate indices identified by the
and the program is not in error, search problem OUTFILE or OUTDATASET parameter.
reporting data bases for a fix for the problem. If no fix Application Programmer Response: Increase the
exists, contact the IBM Support Center. Provide the JCL virtual storage region size. Submit the job again.
Detecting Module: IDCBI01 reporting data bases for a fix for the problem. If no fix

and the SYSOUT output for the job. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
Source: DFSMSdfp
IDC2648I JOB CONTROL CARDS FOR
EXTERNAL SORT MISSING OR IN
ERROR IDC2650I INSUFFICIENT STORAGE TO FINISH
INTERNAL SORT
Explanation: If this message occurs by itself, the
caller specified the EXTERNALSORT parameter, but did Explanation: During initialization, BLDINDEX
not provide the proper job control for the sort work files. calculates the amount of storage required for an internal
sort. This calculation is based on the number of records
If this message is preceded by IDC2649I or IDC2650I,
in the base cluster statistic stored in the virtual storage
BLDINDEX was not able to complete an internal sort.
access method (VSAM) catalog entry for the base
Proper job control for the external sort work files was
cluster.
not supplied. The alternate index being built is named in
a subsequent message. In the case of this message, BLDINDEX was able to
obtain enough virtual storage to meet the calculated
requirement. However, the statistic was erroneously low,
alternate index. However, BLDINDEX attempts to
probably due to a failure during a close of the base
process any other alternate indices specified by the
cluster, and the initial amount of storage obtained was
OUTFILE or OUTDATASET parameter.
exhausted. Under these circumstances, BLDINDEX
Application Programmer Response: Correct the must perform an external sort. The system issues this
external sort work file job control. Submit the job again. message only when proper job control for the external
Alternatively, provide enough virtual storage so that an sort work files was not supplied.
internal sort can be performed.
System Programmer Response: If the error recurs alternate index. However, BLDINDEX attempts to
and the program is not in error, search problem process any other alternate indices specified by the
reporting data bases for a fix for the problem. If no fix OUTFILE or OUTDATASET parameter.
Application Programmer Response: Correct the sort
work file job control. Alternatively, delete the alternate
Source: DFSMSdfp index. Use the EXPORT command to create a portable
copy of the base cluster, followed by an IMPORT
Detecting Module: IDCBI01 command to rebuild the base cluster. This will correct
the erroneous statistic. Then redefine the alternate
IDC2649I INSUFFICIENT STORAGE TO index. Submit the job again.
PERFORM INTERNAL SORT System Programmer Response: If the error recurs
Explanation: Although BLDINDEX was able to obtain and the program is not in error, search problem
a minimum amount of virtual storage to start the sort, it reporting data bases for a fix for the problem. If no fix
was less than the amount calculated to be required for exists, contact the IBM Support Center. Provide the JCL
the entire sort. This is based on the number of records and the SYSOUT output for the job.
in the base cluster statistic stored in the virtual storage Source: DFSMSdfp
access method (VSAM) catalog entry for the base
cluster. Under these circumstances, BLDINDEX Detecting Module: IDCBI01
attempts to prepare for an external sort. The system
writes this message only when proper job control for the
IDC2651I DEFINE OF SORT WORK FILES
external sort work files was not supplied.
FAILED
Explanation: In preparing for an external sort
BLDINDEX attempts to define dynamically two sort work
process any other alternate indexes specified via the
files. However, the define was rejected by virtual
OUTFILE or OUTDATASET parameter.
storage access method (VSAM) catalog management.
Application Programmer Response: Correct the This message is preceded by either message IDC3007I
external sort work file job control, or provide enough or IDC3009I giving the VSAM catalog return code. Refer
virtual storage so that an internal sort can be performed. to the appropriate message for an explanation of the
Submit the job again. code.
System Programmer Response: If the error recurs System Action: The system ends processing for this
and the program is not in error, search problem alternate index. However, BLDINDEX attempts to
333
process any other alternate indexes specified by the BLDINDEX attempts to process any other alternate
OUTFILE or OUTDATASET parameter. indices identified by the OUTFILE or OUTDATASET
parameter.
error as explained for the return code. Submit the job Application Programmer Response: Follow the
again. problem determination actions.
and the program is not in error, search problem and the program is not in error, search problem
exists, contact the IBM Support Center. Provide the JCL exists, contact the IBM Support Center. Provide the JCL
and the SYSOUT output for the job. and the SYSOUT output for the job.
Detecting Module: IDCBI01 Detecting Module: IDCBI01
IDC2654I dsname WAS NOT BUILT IDC2656I LOCATE FAILED FOR dsname
Explanation: An error was encountered for the Explanation: The virtual storage access method
alternate index. The message containing the error (VSAM) catalog locate function issued against the base
precedes this message. cluster or alternate index failed. Message IDC3009I
precedes this message and gives the catalog return
code. Refer to that message for an explanation of the
dsname code.
The data set name.
The locate failure may have been against the named
System Action: The system ends processing for this object or an object associated with the named object.
process any other alternate indexes identified by the
OUTFILE or OUTDATASET parameter. dsname
The data set name specified by the
INFILE/INDATASET or
OUTFILE/OUTDATASET parameter.
exists, contact the IBM Support Center. Provide the JCL System Action: If the failure is associated with the
and the SYSOUT output for the job. base cluster, the system ends processing for the entire
BLDINDEX command.
Source: DFSMSdfp
If the failure is associated with an alternate index, the
system ends processing for the alternate index.
However, BLDINDEX attempts to process any other
IDC2655I UNABLE TO LOCATE ATTRIBUTES OF alternate indices identified by the OUTFILE or
dsname OUTDATASET parameter.
Explanation: The virtual storage access method Application Programmer Response: Correct the
(VSAM) catalog locate function issued by BLDINDEX error as explained for the return code. Submit the job
has been unable to obtain all the necessary information again.
regarding the entry. This indicates a serious catalog
error since the information requested should be present
for all catalog entries, as follows:
v Entry type exists, contact the IBM Support Center. Provide the JCL
v Associated objects and the SYSOUT output for the job.
v AMDSB control block for data objects Source: DFSMSdfp
In the message text: Detecting Module: IDCBI01
dsname
The data set name. IDC2658I SORT PRODUCT FAILED
System Action: If the specified data set name is the Explanation: BLDINDEX has invoked DFSORT (or an
base cluster, the system ends BLDINDEX processing.i If equivalent product) to sort the alternate index. An error
it is an alternate index or a path over an alternate index, has occurred during this processing.
the system ends processing for the alternate index.

IDC2668I DATA SET NOT EXPORTED, VOLUME
command.
ser REQUIRED BUT NOT SUPPLIED
System Programmer Response: Correct the error as
Explanation: Synchronization checking was attempted
indicated in the preceding messages if they exist. If no
on a volume not included in the list of volumes in the
preceding messages exist, check the DFSORT (or
catalog recovery area (CRA) keyword.
equivalent product) message data set for detailed
information on the cause of the failure. If In the message text:
SORTMESSAGELEVEL(ALL) was specified use the call
identifier to find the set of DFSORT (or equivalent
product) messages for this call (see IDC01850I and System Action: The system does not process the
DFSORT message ICE200I or the appropriate message virtual storage access method (VSAM) entry.
for an equivalent product), and correct the DFSORT (or
equivalent product) error that caused the failure. Application Programmer Response: Add the volume
serial number to the CRA keyword. Run the job again.
Source: DFSMSdfp
IDC2660I INVALID ENTRY TYPE IN CATALOG, Detecting Module: IDCRC01

OBJECT BYPASSED
Explanation: The entry type field indicates the object IDC2671I WILL NOT PROCESS CRA ON VOLUME
being exported is not one of the following: ser, DIFFERENT CATALOG NAME
v A virtual storage access method (VSAM) cluster Explanation: This volume does not belong to the
v Alternate index catalog named in the following message.
v User catalog In the message text:

v Non-VSAM object ser The volume serial number.
v OS/VS2 generation data group (GDG)
System Action: The system discontinues processing
System Action: The system ends processing for the of this volume.
object.
Application Programmer Response: Redefine the with the correct catalog name.
object in error. For the object name, see the following
Source: DFSMSdfp
second-level message.
reporting data bases for a fix for the problem. If no fix IDC2673I CONFLICTING JCL SPECIFICATIONS
exists, contact the IBM Support Center. Provide the JCL FOR DNAME dname
Explanation: Incorrect volume information was
Source: DFSMSdfp specified in the JCL or EXPORTRA command. Either
the catalog recovery area (CRA) DNAME is missing
from the job control or is not specified correctly in
EXPORTRA, or more than a single volume is specified
IDC2666I ENTRY NAME SPECIFIED CANNOT BE in the job control for a CRA.
FOUND IN SPECIFIED CRA
Explanation: The data set named in the ENTRIES
dname The specified DNAME.
parameter of the EXPORTRA command cannot be
found in the catalog recovery area (CRA) specified. See System Action: The system ends processing for this
message IDC0674I for the name of that unlocated data request.
set.
System Action: The system ends processing of this volume information in error. Run the job again.
object. The system begins processing of the next object.
Source: DFSMSdfp
Application Programmer Response: Verify the name
and CRA of the data set to be exported using the
LISTCRA command.
Source: DFSMSdfp
335
System Action: The command scratches the partially
IDC2675I DUPLICATE NAME ENCOUNTERED,
created volume and ends processing normally.
NAME ON VOLUME ser BYPASSED
Explanation: Duplicate names were found in the
error as indicated in the preceding message. Run the
catalog recovery areas (CRA) on two different volumes.
command again, requesting creation of the volumes not
In the message text: created.
ser The volume serial number. Source: DFSMSdfp
System Action: The system skips the name specified Detecting Module: IDCCV01
in the following second-level message.
Application Programmer Response: If the copy of IDC2685I ** NO ATTEMPT MADE TO CREATE
the data set skipped was on a volume not to be ADDITIONAL VOLUMES
skipped, run the job again specifying only the desired
Explanation: An error occurred preventing the
volume and data set.
creation of all volumes requested. A preceding message
Source: DFSMSdfp explains the error.
Detecting Module: IDCRC01 System Action: The command ends normally.
IDC2677I ** DATA SET NOT EXPORTED error indicated in the preceding message. Run the
command again, requesting creation of the volumes not
Explanation: An error occurred or a catalog field could
created.
not be located for the object being exported.
Source: DFSMSdfp
System Action: The system ends processing for the
EXPORTRA command. Detecting Module: IDCCV01
Application Programmer Response: Determine the
type of error from the preceding message, and redefine IDC2687I ** PARTIALLY CREATED VOLUME
the object. volser NOT SCRATCHED
Source: DFSMSdfp Explanation: The partially created volume was not
scratched during back out because an error occurred. A
preceding message explains the error.
IDC2681I ** VOLUME volser NOT CREATED
Explanation: The volume was not created for the
specified volume serial number. A preceding message System Action: The command ends normally. The
explains the error. volume record in the Inventory data set for the volume
indicates the volume was incompletely created.
error indicated in the preceding message.
System Action: The command does not attempt to
Run SCRATCHV to scratch the partially created volume
create any subsequent volumes and ends normally.
before running CREATEV again to recreate the same
Application Programmer Response: Correct the volume. A DD statement is not required even if the
error as indicated in the preceding message. Run the partially created volume is active. If a DD statement is
command again. provided, deferred mounting must be specified.
SCRATCHV bypasses the empty volume table of
Source: DFSMSdfp contents (VTOC) check of the partially created volume.
Detecting Module: IDCRC01 If CREATEV ends without indicating the status of the
volume create operation, run LISTMSVI to determine
IDC2684I ** VOLUME volser NOT INITIALIZED whether the volume is flagged for recovery purposes. If
the incomplete create flag is set in the volume record,
Explanation: The newly created volume was not LISTMSVI not only lists the standard information for the
initialized with a volume label and an empty volume volume but also highlights the volume report with a note
table of contents (VTOC). A preceding message that a create operation failed for the preceding volume.
explains the error.
volser The volume serial number. the job log for more information. Search problem

csn1
output and output data sets related to the problem. csn2 The unscratched cartridges.
Detecting Module: IDCCV01 System Action: The command ends normally.
IDC2688I ** INCOMPLETE VOLUME CREATION error indicated in the preceding message. Run the
FLAG NOT RESET FOR VOLUME volser command again.
Explanation: The recovery flag for incomplete volume Source: DFSMSdfp
creation was not turned off in the Inventory record after
new volume creation was completed for the specified Detecting Module: IDCCV01
volume. A preceding message explains the error.
In the message text: IDC2753I VOLUME volser NOT SCRATCHED,
COPIES EXIST
Explanation: The base volume was not scratched
System Action: The command scratches the partially because copies still exist.
created volume.
error indicated in the preceding message. Run the volser The volume serial number.
command again. System Action: The command ended normally.
System Programmer Response: If the error recurs Application Programmer Response: Correct the
and the program is not in error, look at the messages in error that prevented the copies from being scratched.
the job log for more information. Search problem Run the command again, specifying the ALL parameter.
JCL, the SYSOUT output for the job, and all printed Detecting Module: IDCSV01
Source: DFSMSdfp IDC2761I ** RECORD FOR COPY yyddd NOT
Detecting Module: IDCCV01 REMOVED
Explanation: The volume copy record created on the
IDC2689I INSUFFICIENT NUMBER OF indicated date was not removed from the Inventory data
CARTRIDGES SPECIFIED ON set. A preceding message explains the reason for the
COMMAND error.
Explanation: The number of cartridges specified in the In the message text:

CARTRIDGE parameter is insufficient to create the yyddd The date, in year and days.
number of new volumes requested.
System Action: The command either continues
System Action: The command creates as many processing or ends depending on the severity of the
volumes as possible before ending normally. error encountered.
Application Programmer Response: Specify Application Programmer Response: Correct the
sufficient cartridges in the CARTRIDGE parameter for error indicated in the preceding message. Run the
all volumes to be created or do not specify any command again to remove records not removed.
cartridges in the CARTRIDGE parameter. Run the
Source: DFSMSdfp Detecting Module: IDCSV01
Detecting Module: IDCCV01

IDC2762I ** RECORD FOR VOLUME volser NOT
REMOVED
IDC2752I ** CARTS csn1 cns2 NOT SCRATCHED
FOR volser Explanation: The volume record was not removed
from the Inventory data set. A preceding error message
Explanation: The requested volume was not explains the reason for the error.
scratched.
337
volser The volume serial number. Detecting Module: IDCRR01
IDC2782I ** SCRATCH CARTRIDGE csn NOT
EJECTED
error indicated in the preceding message. Run the
command to remove the volume record. Explanation: The requested scratch cartridge could
not be ejected. See the preceding message for further
Source: DFSMSdfp
explanation of the problem.
IDC2764I CARTRIDGES STILL IN MASS
STORAGE FACILITY System Action: The system continues processing.
Explanation: The REPLACEVOLUME keyword is Application Programmer Response: Correct the
specified, but the base volume cartridges have been problem as identified in the preceding message. Run
reentered into the Mass Storage Facility (MSF) while the command again to eject the cartridge.
the Mass Storage Volume Control was disabled.
System Action: The system bypasses the request. and the program is not in error, search problem
The remaining requests will be attempted. reporting data bases for a fix for the problem. If no fix
Application Programmer Response: When the Mass
Storage Volume Control is enabled, eject the base
volume from the Mass Storage Control and reenter it.
Source: DFSMSdfp
Issue the following access method services commands:
v MSS LISTMSF for mountable volumes
v MSS LISTMSF with the CARTRIDGES parameter IDC2800I ATTRIBUTES COULD NOT BE
v PRINT to list the contents of the mass storage CHANGED FOR REMAINING VOLUMES
volume control inventory data set IN GROUP
v LISTMSVI
Explanation: Although the group level attributes have
v LISTMSF with the ALL parameter
been successfully changed in the group record in the
Source: DFSMSdfp Inventory data set, the attributes cannot be changed for
the general-use volumes remaining in the group
because storage for an event control block (ECB) and
message area cannot be obtained or a base volume
IDC2765I RECORD FOR VOLUME volser NOT record cannot be retrieved from the Inventory data set.
REMOVED. RECORD FOR COPY
The following are valid attributes:
EXISTS
v bind/nobind,
Explanation: A copy volume record still exists.
Therefore, the base volume record for the specified
volume cannot be removed. See a preceding message v dasderase/nodasderase
for the error that prevented removal of all copy records. v exclusive/shared,
In the message text: v pagefault/nopagefault
volser The volume serial number. System Action: The command ends with a message.
System Action: The command ends normally. Application Programmer Response: Correct the
problem as identified in a preceding message. To
Application Programmer Response: Correct the determine the number of additional volumes in the
error indicated in the preceding message. Run the group that must be updated, run the LISTMSVI
REMOVEVR command again with the ALL parameter. command. Run the command again if a large number of
System Programmer Response: If the error recurs volumes remain to be updated. Otherwise, run the
and the program is not in error, search problem MODIFYV command to change the volume attributes of
reporting data bases for a fix for the problem. If no fix each volume if the number of remaining volumes is
exists, contact the IBM Support Center. Provide the small.
JCL, the SYSOUT output for the job, and all printed System Programmer Response: If the error recurs
output and output data sets related to the problem. and the program is not in error, search problem

JCL, the SYSOUT output for the job, and all printed exists, contact the IBM Support Center. Provide the
output and output data sets related to the problem. JCL, the SYSOUT output for the job, and all printed
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCMG01
Detecting Module: IDCLM01
IDC2801I ** ATTRIBUTES NOT CHANGED FOR
VOLUME volser IDC2823I ** text TOTAL COULD NOT BE
CALCULATED
Explanation: Although the attributes have been
changed in the group record, the attributes of the Explanation: text is one of the following:
specified volume cannot be changed. The volume may SCRATCH CARTRIDGE
be currently mounted, marked in the Inventory data set MOUNTABLE VOLUME
for recovery purposes, or unavailable for another NON-MOUNTABLE VOLUME
reason. See the preceding message for further EMPTY CELL
explanation of the problem.
Because of an error, the summary count information
The following are valid attributes:
could not be calculated. A previous message explains
v bind/nobind the error.
v readonly/readwrite,
System Action: The command continues processing,
v dasderase/nodasderase but the indicated count is not listed.
v exclusive/shared
v pagefault/nopagefault error identified in the previous message. Run the
System Action: The system continues processing. command again.
Application Programmer Response: Correct the System Programmer Response: If the error recurs
problem as identified in the preceding message. Run and the program is not in error, search problem
the MODIFYV command to change the volume reporting data bases for a fix for the problem. If no fix
attributes of each volume that could not be updated. exists, contact the IBM Support Center. Provide the
System Programmer Response: If the error recurs output and output data sets related to the problem.
the job log for more information. Search problem Source: DFSMSdfp
reporting data bases for a fix for the problem. If no fix Detecting Module: IDCLM01
output and output data sets related to the problem. IDC2831I ** RECORD CHAIN BROKEN, REST OF
CHAIN NOT LISTED
Source: DFSMSdfp
Explanation: The record could not be found for a
Detecting Module: IDCMG01 volume recorded in the Inventory data set as part of a
chain of non-grouped volumes or a chain of volumes
IDC2821I ** text REPORT NOT PRODUCED belonging to a specific group. See the preceding
message for further explanation of the error.
SCRATCH CARTRIDGE System Action: The system continues processing.
MOUNTABLE VOLUME Application Programmer Response: Correct the
NON-MOUNTABLE VOLUME error as indicated in the preceding message. Run the
command again to list volumes that could not be listed.
The indicated report was not produced due to a
previously identified error. System Programmer Response: If the error recurs
System Action: The command continues with the next the job log for more information. Search problem
report. reporting data bases for a fix for the problem. If no fix
Application Programmer Response: Check the exists, contact the IBM Support Center. Provide the
previous error message for the cause of the failure. JCL, the SYSOUT output for the job, and all printed
Correct the error. Run the command again. output and output data sets related to the problem.
System Programmer Response: If the error recurs Source: DFSMSdfp

and the program is not in error, search problem Detecting Module: IDCLV01
339
prm The tuning parameter.
IDC2833I ** CARTRIDGE RECORD csn NOT
FOUND IN INVENTORY System Action: The command ended normally. The
system does not display more parameters.
Explanation: The cartridge record for the cartridge
cannot be found in the Inventory data set. Application Programmer Response: Correct the
error. Run the command again.
Source: DFSMSdfp
Detecting Module: IDCTU01
Application Programmer Response: Correctly
IDC2854I ** CHANGE OF prm NOT SUCCESSFUL
specify the cartridge serial number. Run the job again. If
the problem is not the result of a user error, contact the Explanation: An attempt to change the specified
space manager. TUNE command parameter failed. See preceding
message for an explanation of the error.
and the program is not in error, look at the messages in In the message text:
reporting data bases for a fix for the problem. If no fix prm The indicated parameter.
exists, contact the IBM Support Center. Provide the System Action: The command ends normally. The
JCL, the SYSOUT output for the job, and all printed system does not change any more tuning parameters.
Source: DFSMSdfp error. Run the command again.
Detecting Module: IDCLV01 Source: DFSMSdfp
Detecting Module: IDCTU01
IDC2843I FUNCTION SUSPENDED DUE TO I/O
ERROR - RECORDS DUMPED nnn
IDC2872I CRA IS OWNED BY catname
Explanation: While dumping trace data records, an
I/O error was encountered and no further processing Explanation: The catalog recovery area (CRA) on this
was possible. A preceding message explains the I/O volume belongs to a catalog other than the one for
error. which COMPARE was specified.
nnn The number of records dumped. catname

The catalog name.
System Action: No more data was dumped. The
command ends normally. System Action: The system ignores the COMPARE
option. The system continues processing.
command again to get the remaining trace data. If the Application Programmer Response: Specify the
problem continues, reallocate and recatalog the data set correct catalog in the CATALOG parameter. Run the job
which is getting I/O errors. again.

and the program is not in error, search problem Detecting Module: IDCTU01
JCL, the SYSOUT output for the job, and all printed IDC2873I ** COMPARE OPTION IGNORED
output and output data sets related to the problem. Explanation: The catalog recovery area (CRA) on this
Source: DFSMSdfp volume cannot be opened or belongs to a catalog other
than the one for which COMPARE was specified. If an
Detecting Module: IDCTR01 error occurred in open, a preceding message gives the
cause.
IDC2853I ** DISPLAY OF prm NOT SUCCESSFUL System Action: The system ignores the COMPARE
Explanation: An attempt to retrieve the information for option of the LISTCRA command. The system continues
the indicated tuning parameter failed. See preceding processing.
message for an explanation of the error. Application Programmer Response: Specify the
In the message text: correct catalog name in the CATALOG parameter or
correct the cause of the Open error. Run the job again.

Source: DFSMSdfp
IDC2876I IGNORED VERIFY FAILURE FOR CRA
Explanation: When a catalog recovery area (CRA) is
opened, a VERIFY is issued by LISTCRA to set up the
proper end-of-file condition. The VERIFY was IDC2884I IGNORED VERIFY FAILURE FOR
unsuccessful. CATALOG
System Action: The system ignores the error. The Explanation: When a catalog is opened, a VERIFY
system continues processing. An incomplete listing of command is issued by LISTCRA to set up the proper
the contents of the catalog recovery area may result. end-of-file condition. The VERIFY was unsuccessful.
Application Programmer Response: Restore the System Action: The system ignores the command.
volume on which the error occurred to a previous valid The system continues processing. Erroneous
condition. miscompares or I/O errors may result.
System Programmer Response: If the error recurs Application Programmer Response: Restore the
and the program is not in error, search problem volume on which the error occurred to a previous valid
reporting data bases for a fix for the problem. If no fix condition.
Source: DFSMSdfp
IDC2879I CATALOG NOT LOCKED UP FOR THIS
EXECUTION Detecting Module: IDCLR01
Explanation: LISTCRA was unable to gain exclusive
control of the catalog. One or more other programs may IDC2886I UNABLE TO REFERENCE CRA ON
be updating the catalog during LISTCRA processing. VOLUME ser - REASON CODE cde
System Action: The system continues LISTCRA Explanation: When opening the catalog recovery area
processing. Some listing errors or miscompares may (CRA) the system detected an error.
result if a catalog or recovery area entry is updated
during LISTCRA processing.
Application Programmer Response: If the accuracy
of this catalog recovery area (CRA) listing can be cde The hex reason code, as follows:
doubted, run the job again when no other programs are
accessing the catalog. Codes Explanation
Source: DFSMSdfp 1 Cannot verify the CRA.
Detecting Module: IDCLR01 2 Cannot open the CRA.

4 I/O error on control interval No.0
IDC2882I VSAM ERROR READING CRA 5 I/O error on control interval No.3
CONTROL RECORD
7 Error on number of directories.
Explanation: A LISTCRA command encountered an
error reading the control record in the catalog recovery 8 Error on directory entries.
area (CRA) to determine the size of the table necessary System Action: The system marks the CRA as bad.
for its processing. No entries are placed on the portable data set.
System Action: The system ends processing for this Application Programmer Response: If the reason
CRA. code is 1, 2, 4, or 5, restore the volume on which the
Application Programmer Response: Restore the error occurred to a previous valid condition.
volume on which the error occurred to a previous valid If the reason code is 7 or 8, provide the FORCE
condition. keyword in the EXPORTRA command to override the
System Programmer Response: If the error recurs synchronization problem.
341
Source: DFSMSdfp parameter has not been specified. The RECOVERY
parameter is only valid for integrated catalog facility
(ICF) catalogs and VSAM volume data sets and
generation data groups (GDG).
IDC2889I UNUSABLE DATA SET NOT
EXPORTED
The remaining entries, if any, are deleted.
Explanation: A multi-volume data set, identified in the
following message and marked unusable, was
parameters specified. If RECOVERY is specified for a
encountered by EXPORTRA. The data set is not on one
GDG, the GENERATIONDATAGROUP parameter must
or more of its secondary volumes. This situation is
be specified. Run the job again.
probably the result of a prior RESETCAT operation.
System Action: EXPORTRA bypasses the virtual
storage access method (VSAM) data set and its
associations.
Application Programmer Response: The data on and the SYSOUT output for the job.
valid volumes can be removed using the REPRO
Source: DFSMSdfp
command prior to deletion. The data set cannot be
opened for output.
IDC2894I GENERIC NAME NOT ALLOWED FOR
NVR, VVR OR TRUENAME DELETE
reporting data bases for a fix for the problem. If no fix Explanation: On a DELETE command, a name in the
exists, contact the IBM Support Center. Provide the generic form, a name with a qualifier of asterisk (*), was
JCL, the SYSOUT output for the job, and all printed specified along with the NVR, VVR or TRUENAME
output and output data sets related to the problem. parameter. Generic names are not allowed when
deleting NVR, VVR or TRUENAME entries. One
Source: DFSMSdfp
DELETE command is required for each NVR, VVR or
Detecting Module: IDCRC01 TRUENAME entry to be deleted.
System Action: The system ends processing of the
IDC2892I INVALID ENTRY TYPE FOR A VSAM command.
VOLUME DATA SET
Explanation: A virtual storage access method (VSAM) name specification. Run the job again.
volume data set name was specified on a DELETE
command and either an entry type other than CLUSTER
was specified or the entry type in the catalog is not a
cluster.
System Action: The system does not delete the entry. exists, contact the IBM Support Center. Provide the JCL
The remaining entries, if any, are deleted. and the SYSOUT output for the job.
Application Programmer Response: Specify the Source: DFSMSdfp

CLUSTER parameter or run a LISTCAT against the
catalog to verify the entry type. Correct the error. Run
the job again.
IDC2895I ALL REQUIRED VOLUMES NOT
INCLUDED IN DD STATEMENT
SPECIFIED IN FILE PARAMETER
exists, contact the IBM Support Center. Provide the JCL Explanation: A FILE parameter was specified on a
and the SYSOUT output for the job. DELETE command. The DD statement does not contain
all of the required volumes to delete the entry.
Source: DFSMSdfp
However, it does delete any remaining entries.
IDC2893I INVALID PARAMETER SPECIFIED FOR
THE RECOVERY OPTION Application Programmer Response: You may
perform one of the following procedures:
Explanation: The RECOVERY parameter has been
v Add the missing volumes to the DD statement. Run
specified for a DELETE command and a virtual storage
the job again.
access method (VSAM) volume data set (VVDS) is not
v Remove the FILE parameter and allow dynamic
to be deleted, or the GENERATIONDATAGROUP
allocation to allocate the necessary volumes. You

may need a JOBCAT or STEPCAT to insure that the
IDC2910I ** NO VOLUME MOUNTED
volumes contain the correct mount status.
Explanation: None of the volumes specified for the
data set are mounted.
the job log for more information. Search problem System Action: The data set is not scratched.
Application Programmer Response: Mount the
proper volumes. Submit the job again.
Source: DFSMSdfp
Detecting Module: IDCDL01 the job log for more information. Search problem
IDC2908I ddname NOT FOUND IN SYSTEM
Explanation: An attempt was made to use the
Source: DFSMSdfp
specified volume. The DD statement corresponding to
the ddname could not be found. Detecting Module: IDCSA08
IDC2912I ** PASSWORD VERIFICATION FAILED
ddname
The ddname. Explanation: The console operator did not supply the
proper password for the data set to be scratched.
System Action: The volume cannot be accessed.
System Action: The data set is not scratched.
erroneous ddname or provide a DD statement. Submit Application Programmer Response: Submit the job
the job again. again, supplying the correct password when prompted.
and the SYSOUT output for the job. and the SYSOUT output for the job.
Detecting Module: IDCIO03 Detecting Module: IDCSA08
IDC2909I UNABLE TO SCRATCH dsname IDC2913I ** DATA SET HAS NOT EXPIRED ON
VOLUME ser
Explanation: An error occurred while attempting to
scratch the specified data set. A subsequent Explanation: The PURGE option was not specified,
second-level message explains the error. and the data set retention period has not expired.
dsname ser The volume serial number.
The data set name.
Application Programmer Response: Submit the job
System Programmer Response: If the error recurs again, specifying PURGE to delete the data set.
Source: DFSMSdfp and the SYSOUT output for the job.
Detecting Module: IDCSA08 Source: DFSMSdfp
343
Source: DFSMSdfp
IDC2914I ** PERMANENT I/O ERROR ON
VOLUME ser Detecting Module: IDCSA08
Explanation: The volume table of contents (VTOC)
cannot be read because of an I/O error. IDC2917I NO RACF PROFILE ON resname
In the message text: Explanation: The specified resource is recorded in the
volume table of contents (VTOC) as RACF protected.
However, no RACF profile could be found for the
System Action: The data set is not scratched. resource. RACF could not perform the user
authorization check for the resource.
Application Programmer Response: Request that
the volume be restored. In the message text:
System Programmer Response: If the error recurs resname
and the program is not in error, look at the messages in The resource name. resname can be either a
the job log for more information. Search problem RACF FACILITY class or a DASD volume. In
reporting data bases for a fix for the problem. If no fix the case of a RACF FACILITY class, resname
exists, contact the IBM Support Center. Provide the JCL will be the name of the class. For a DASD
and the SYSOUT output for the job. volume, resname will contain the volume serial
number.
Source: DFSMSdfp
System Action: If a Cache-DASD command was
issued, the system continues processing. Otherwise, the
command ends.
IDC2915I ** UNABLE TO MOUNT VOLUME ser
Cache-DASD commands are as follows:
Explanation: An appropriate unit was not available for v BINDDATA
mounting, or JES3 will not permit the volume to be
v LISTDATA
mounted.
v SETCACHE
Application Programmer Response: Before running
ser The volume serial number. the job again, define the resource to RACF. If the
System Action: The data set is not scratched. resource is a data set, use the RACF ADDSD
command. Otherwise, use the RACF RDEFINE
Application Programmer Response: Ensure that a command.
unit is available for mounting.
These commands can be run in the foreground or with
System Programmer Response: If the error recurs the Terminal Monitor Program in the background.
the job log for more information. Search problem System Programmer Response: If the error recurs
reporting data bases for a fix for the problem. If no fix and the program is not in error, look at the messages in
exists, contact the IBM Support Center. Provide the JCL the job log for more information. Search problem
and the SYSOUT output for the job. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp JCL, the SYSOUT output for the job, and all printed
Source: DFSMSdfp
IDC2916I ** DATA SET WAS IN USE Detecting Module: IDCSA08
Explanation: The data set to be scratched was in use.
IDC2918I RACHECK FAILED FOR resname
Explanation: An unauthorized caller requested access
Application Programmer Response: To delete the
to a RACF protected resource. The caller does not have
data set, ensure that no one else is using the data set
the proper authorization for the specified resource.
when you run the job again.
and the program is not in error, look at the messages in resname
the job log for more information. Search problem The resource name.
exists, contact the IBM Support Center. Provide the JCL System Action: The system ends the command.
and the SYSOUT output for the job. Application Programmer Response: Contact the

RACF security administrator to acquire the proper
IDC2950I INVALID FORMAT STRUCTURE
authorization. Run the job again.
Explanation: An element of one of the text format
structures is incorrect. If it does, it is a system error.
the job log for more information. Search problem System Action: The system ignores the request to
reporting data bases for a fix for the problem. If no fix print a line.
Application Programmer Response: Follow the
problem determination steps.
Source: DFSMSdfp
Detecting Module: IDCSA08 and the program is not in error, search problem
IDC2919I INVALID URACHECK PARAMETER
LIST
Source: DFSMSdfp
Explanation: The parameter list passed to the
URACHECK macro is incorrect. The access method Detecting Module: IDCTP01
services module which invoked the URACHECK macro
either set up the parameter list incorrectly or passed an
IDC2951I OUTPUT COLUMN SPECIFIED OUT OF
incorrect pointer to the parameter list. This is a system
RANGE
error.
Explanation: An output column specified is outside
System Action: The system ends the command.
the print line width. This should not occur on a
System Programmer Response: If the error recurs checked-out access method services command.
System Action: The ignored this field and subsequent
fields.
exists, contact the IBM Support Center. Provide the Application Programmer Response: Follow the
JCL, the SYSOUT output for the job, and all printed problem determination steps.
IDC2930I ** INVALID RACF AUTHORIZATION
Source: DFSMSdfp
Explanation: The data set to be scratched is
RACF-protected. The caller does not have the proper
RACF authorization to scratch the data set.
IDC2952I EXCESSIVE FIELD LENGTH FOR BD
OR PU CONV
Explanation: A binary to decimal or packed to
RACF security administrator to acquire the proper
unpacked conversion length was specified as greater
authorization. Run the job again.
than 15 characters. This should not occur in a valid
System Programmer Response: If the error recurs program.
System Action: The system uses the default.
output and output data sets related to the problem. exists, contact the IBM Support Center. Provide the JCL
Source: DFSMSdfp
Source: DFSMSdfp
345
IDC2953I A REDO SUB-STRUCTURE IS NESTED IDC2960I NO PSWDFILE FOR dsname
Explanation: A redo structure cannot be defined within Explanation: A password protected data set was
the set of structures to be redone. This should not occur found on the volume table of contents (VTOC) but no
in a valid program. DD statement was found with that data set name.
System Action: The current redo operation is ended. In the message text:
All structures will be treated only once.
dsname
System Programmer Response: If the error recurs The data set name.
exists, contact the IBM Support Center. Provide the JCL Application Programmer Response: Provide a DD
and the SYSOUT output for the job. statement with the name of the data set. Specify the
name of the DD statement on the PASSWORDFILE
Source: DFSMSdfp
parameter. Run the command again.
IDC2954I STATIC TEXT ENTRY REQUESTED the job log for more information. Search problem
NOT IN MODULE reporting data bases for a fix for the problem. If no fix
Explanation: A static text request indicated an entry
that was not in the specified module. This should not
occur in a valid program.
Source: DFSMSdfp
System Action: The system does not honor the
request. Detecting Module: IDCVS01
and the program is not in error, search problem IDC2961I {FROM|TO} VOLUME volser CONTAINS
reporting data bases for a fix for the problem. If no fix NON-VSAM DATA SETS
Explanation: The command requires that no
non-virtual storage access method (VSAM) data sets
Source: DFSMSdfp can reside on the specified volume. However, a format
1 DSCB was found for a non-VSAM data set.
IDC2955I INVALID PACKED DECIMAL FIELD FROM|TO
Indicate which volume contains the data set for
Explanation: A conversion request for packed to
those commands that process more than one
unpacked found a digit that was not in the range 0 to 9.
command.
The input data may be wrong. This occurs when an
incorrect field is being printed. volser The volume serial number.
System Action: Conversion stops. Previously System Action: The command ends normally.
converted data will be printed.
Application Programmer Response: Check the input and the program is not in error, look at the messages in
data. the job log for more information. Search problem
exists, contact the IBM Support Center. Provide the JCL Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCTP01 IDC2962I ENTRY NOT FOUND FOR VOLUME
volser IN VSAM CATALOG
Explanation: The volume entry could not be located
for the volume in the volume storage access method
(VSAM) catalog specified by the caller on the command

or, if not specified on the command, in the VSAM the job log for more information. Search problem
catalog in the STEPCAT, JOBCAT, master catalog reporting data bases for a fix for the problem. If no fix
hierarchy. exists, contact the IBM Support Center. Provide the
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCVS01 IDC2965I ATTEMPT TO SCRATCH DATA SETS
TERMINATED
IDC2963I FORMAT 4 DSCB NOT FOUND ON Explanation: An error occurred reading or updating
VTOC OF {FROM|TO} VOLUME the volume table of contents (VTOC) so that no more
data sets could be scratched. The virtual storage
Explanation: The program positioned to the first access method (VSAM) ownership flag has been set off
record in the volume table of contents (VTOC) of the in the VTOC.
volume but it was not a Format 4 DSCB.
System Action: The system does not make any
In the message text: further attempts to scratch a data set. The command
FROM|TO continues processing.
Indicate which volume encountered the error Application Programmer Response: Run the
for the commands that process more than one AMASPZAP service aid program to alter the VTOC if
volume. the VTOC contains VSAM data sets and the data sets
System Action: The command ends normally. have been recataloged. If the volume is not a VSAM
volume, use the IEHPROGM utility’s SCRATCH VTOC
Application Programmer Response: This probably statement.
indicates an access method services error. Possibly the
VTOC has been destroyed. Attempt to list the VTOC System Programmer Response: If the error recurs
using the IEHLIST utility, and reconstruct the VTOC. and the program is not in error, look at the messages in
Run the command again. the job log for more information. Search problem
and the program is not in error, look at the messages in JCL, the SYSOUT output for the job, and all printed
the job log for more information. Search problem output and output data sets related to the problem.
JCL, the SYSOUT output for the job, and all printed Detecting Module: IDCVS01
Source: DFSMSdfp IDC2966I RECATALOGING OF NON-VSAM DATA
Detecting Module: IDCVS01 SETS NOT PERFORMED
Explanation: An error occurred which prevented any
IDC2964I ** SCRATCH OF DATA SETS NOT non-virtual storage access method (VSAM) data sets
PERFORMED from being recataloged. A preceding message will
indicate the specific reason for the error.
Explanation: An error occurred which prevented any
data set from being scratched. The volume is still System Action: The command ends normally. The
marked as virtual storage access method (VSAM) system performs no further function.
volume. A preceding message indicates the specific Application Programmer Response: Use the
error. IEHPROGM utility or the access method services
System Action: The command continues processing. DELETE and DEFINE commands to recatalog the data
sets. If the error recurs and the program is not in error,
Application Programmer Response: Run look at the messages in the job log for more
AMASPZAP service aid program to alter the volume information. Search problem reporting data bases for a
table of contents (VTOC) if any VSAM data sets are on fix for the problem. If no fix exists, contact the IBM
the volume and the VSAM data sets have been Support Center. Provide the JCL, the SYSOUT output
recataloged. If the volume is not a VSAM volume, use for the job, and all printed output and output data sets
the IEHPROGM utility’s SCRATCH VTOC statement. related to the problem.
347
IDC2972I LSPACE ERROR. LSPACE RETURN
CODE WAS return-code.
IDC2967I ATTEMPT TO RECATALOG NON-VSAM
Explanation: The LSPACE macro failed to return
DATA SETS TERMINATED
volume free space information for a LISTDSET space
Explanation: An error occurred after some data sets usage report.
were recataloged. A preceding message indicates the
specific reason for the error.
return-code The return code, as follows:
System Action: The system does not recatalog any
more non-virtual storage access method (VSAM) data Code Explanation
sets. The command terminates normally. The system
4 An I/O error occurred while
does not perform any further function.
reading the DSCBs.
Application Programmer Response: List the catalog
8 The last allocation of the
to determine which data sets were recataloged or, if the
volume was made under
LIST parameter was specified, examine the SYSPRINT
DOS.
listing to see which data sets were recataloged.
Recatalog the data sets not previously recataloged 12 The user control block (UCB)
using the IEHPROGM utility or the access method address is incorrect. The
services DELETE and DEFINE commands. UCB is not for a
direct-access device, or the
UCB-not-ready bit is on,
indicating the device is not
ready.
exists, contact the IBM Support Center. Provide the 16 Indicates an incorrect
JCL, the SYSOUT output for the job, and all printed message area address or
output and output data sets related to the problem. system management facility
(SMF) indicator.
Source: DFSMSdfp
System Action: The volume is not processed. The
system processes other specified volumes.
Application Programmer Response: Determine why
IDC2971I RESERVE FOR VOLUME volser NOT
the LSPACE macro failed. Message IDC2108I follows
SUCCESSFUL
this messages and identifies the failing volume.
Explanation: The reserve with the HAVE option
returned an unsuccessful condition code.
In the message text: the job log for more information. Search problem
System Action: The command ends processing. JCL, the SYSOUT output for the job, and all printed
System Programmer Response: If the error recurs Detecting Module: IDCVS03

IDC2973I VTOC ON volser, VOLUME TO BE
COPIED, IS IN ERROR
JCL, the SYSOUT output for the job, and all printed Explanation: Either an error occurred when the
output and output data sets related to the problem. volume services routine attempted to redefine a
format-5 data space control block (DSCB) or the DIRF
Source: DFSMSdfp
bit is on in the format-4 DSCB. The DIRF bit is used to
Detecting Module: IDCVS01 detect a system failure or permanent I/O error while the
volume table of contents (VTOC) is being updated.
System Action: Instead of attempting to copy only

allocated cylinders, the system makes a copy of all
IDC3006I FUNCTION TERMINATED DUE TO
cylinders of the volume.
BEGINNING POSITIONING ERROR
Explanation: An error occurred when positioning to a
VTOC is not in error. Try to list the VTOC using the
record in a data set was attempted. The position
IEHLIST utility program.
indicator may be beyond the limits of the data set or an
System Programmer Response: If the error recurs I/O error may have occurred in positioning. An I/O error
and the program is not in error, look at the messages in message may have been printed.
System Action: The system ends the operation.
Source: DFSMSdfp
Detecting Module: IDCVS01 positioning parameter value. See the I/O error message
description for the I/O error indicated ahead of this
message.
IDC3003I FUNCTION TERMINATED. CONDITION
CODE IS cde. System Programmer Response: If the error recurs
Explanation: The system writes this message when the job log for more information. Search problem
an error condition has occurred in the processing of a reporting data bases for a fix for the problem. If no fix
functional command. Messages printed just before this exists, contact the IBM Support Center. Provide the
message in the program listing indicate the error that JCL, the SYSOUT output for the job, and all printed
occurred. output and output data sets related to the problem.
cde The condition code of the abnormally ended Detecting Module: IDCPR01
function.
System Action: The system continues processing with IDC3007I VSAM CATALOG RETURN-CODE IS
the next command. The system sets LASTCC to the return-code
condition code. The system also sets MAXCC if the
condition code is greater than the current MAXCC Explanation: This condition code was returned as the
value. result of a catalog error or exceptional condition. The
system uses this message only when a more
Application Programmer Response: Preceding specifically worded message does not exist. In most
messages indicate the appropriate programmer instances, a subsequent message will indicate the
response. action taken for the command that encountered the
Source: DFSMSdfp condition.
Detecting Module: IDCVS01 In the message text:

return-code The return code. It may be either a
IDC3004I FUNCTION TERMINATED. virtual storage access method (VSAM)
INSUFFICIENT MAIN STORAGE. return code or a control volume
(CVOL) processor return code. To
Explanation: The region size was not large enough to determine which, determine whether
process a functional command. the entry name specified in the
System Action: The system continues processing with command was directed to a VSAM
the next command. catalog or a CVOL catalog. For a
return code to be a CVOL return
Application Programmer Response: Increase the code, the entry name specified in the
size of the storage allocated. command must be qualified; and the
System Programmer Response: If the error recurs first qualifier must be identical to an
and the program is not in error, look at the messages in alias entry in the master catalog. The
the job log for more information. Search problem alias entry must be related to a
reporting data bases for a fix for the problem. If no fix non-VSAM entry of the form
exists, contact the IBM Support Center. Provide the JCL SYSCTLG.
for the job.
The CVOL processor return codes follow. The VSAM
Source: DFSMSdfp catalog return codes are listed with message IDC3009I,
Detecting Module: IDCAL01, IDCBI01, IDCCC01, where they appear together with reason codes. For
IDCDE01, IDCED02, IDCLC01, IDCMP01, IDCPR01, message IDC3007I, ignore the VSAM return codes:
IDCRC01, IDCRM01, IDCRP01, IDCRS05, IDCVY01, Code Explanation
IDCXP01
349
4 Cannot allocate catalog, catalog does not exist, 8 Check that the entry name is spelled correctly.
or is not open. Verify the use of JOBCAT and STEPCAT
catalogs, if employed.
8 The data set does not exist, or a CVOL
contains a CVOL pointer or generation data 20 See your system programmer for assistance in
group (GDG) alias, or the entry name reorganizing the CVOL.
duplicates an existing name.
24 Have the volume restored or try mounting the
20 There is insufficient space in the CVOL data volume on a different device.
set.
28 Have the volume restored or try mounting the
24 LOCATE operation - Permanent I/O error, volume on a different device.
unrecoverable error, or nonzero return code
44 Change the LEVEL or ENTRIES parameter of
from ESTAE. The CVOL processor issues the
the LISTCAT command to limit the number of
ESTAE.
eligible entries to 1,456.
28 Non-LOCATE operation - Permanent I/O error,
48 Verify the use of JOBCAT and STEPCAT
unrecoverable error, or nonzero return code
catalogs, if employed, to ensure that the
from ESTAE. The CVOL processor issues the
catalog being acted upon is appropriate to the
ESTAE.
action you are attempting.
44 All eligible entries could not be listed by the
56 Message IEC301A has been printed until the
LISTCAT function. LISTCAT can handle a
maximum number of attempt is exceeded.
maximum of 1,456 entries.
Provide the operator with the correct password.
48 Function inconsistent with CVOL processor. Run the job again.
56 An attempt to delete an entry failed because 84 Specify the PURGE option, if desired. Run the
the DELETE command specified SCRATCH, job again.
but password verification failed for the
102 Get authorization for the data set. Run the job
password protected data set.
again.
84 An attempt to delete an entry failed because
164 Increase the region size for the step.
the DELETE command specified SCRATCH
without PURGE, but the expiration date of the 168 If the data set was cataloged using an esoteric
data set has not been reached. device type, such as SYSDA, a non-standard
device type is cataloged, such as, “000B2000”.
102 An attempt to delete an entry failed because
To delete the entry, use the access method
the DELETE command specified SCRATCH,
services DELETE command with NOSCRATCH
but the data set is defined to RACF and the
specified. Then, to scratch the data set, specify
accessor is not authorized to it.
DISP=(OLD, DELETE), or IEHPROGM to
164 There is insufficient virtual storage available for scratch the data set.
a CVOL catalog management work area.
184 Run the job again. To ensure proper
168 An attempt to delete an entry failed because completion, specify a disposition of OLD, not
the DELETE command specified SCRATCH, SHR.
but the device type of the cataloged volume
did not match the user control block (UCB)
device type.
184 An attempt to delete an entry failed because reporting data bases for a fix for the problem. If no fix
the DELETE command specified SCRATCH, exists, contact the IBM Support Center. Provide the JCL
but the data set is currently open and cannot and the SYSOUT output for the job.
be scratched.
Source: DFSMSdfp
Detecting Module: IDCAL01, IDCDE02, IDCMP01,
Application Programmer Response: Respond IDCRM01, IDCTR01
according to the return code, as follows:
Code Response IDC3008I FUNCTION IS NOT SUPPORTED IN
THIS ENVIRONMENT
4 Ensure that the CVOL is mounted. Verify the
use of the STEPCAT and JOBCAT JCL or of Explanation: A request for prompting or data set
the ddname DD statement. name qualifying has been received while not in a Time
Sharing Option/Extensions (TSO/E) environment.
System Action: The system ends the request.

and the program is not in error, look at the messages in and the SYSOUT output for the job.
Some return and reason code combinations may also
produce an SVC dump. This dump should also be
provided with any other documentation supplied to the
Support Center.
Source: DFSMSdfp
The list of return codes and reason codes follows:
RETURN CODE 4
IDC3009I VSAM CATALOG RETURN CODE IS Explanation: The system encountered an error while
return-code - REASON CODE IS performing open/close processing for a catalog. If the
IGGOCLaa - reason-code catalog is being accessed dynamically (e.g. no JOBCAT
or STEPCAT DD statement in the JCL), dynamic
Explanation: Catalog management returned this allocation may have failed because the volume is
return code and reason code as a result of a catalog allocated exclusively. The volume may be allocated
error or exceptional condition. exclusively due to one of the following:
In the message text: v Specification of deferred mount on a DD statement
return-code The return code. v Volume count greater than unit count on a DD
statement
reason-code The reason code.
v Previous access method services command in the
job step needed to demount the volume and changed
For an explanation of the return and reason codes, the allocation of the volume to exclusive.
check below to:
v Find the underlined heading for the return code.
v Scan for the associated reason code. Reason
Code Description
If you are using BookManager, to quickly find the x Explanation: An internal error has
explanation of the return and reason codes, enter the occurred during Catalog processing.
search argument:
IDC3009I rtn rsn Programmer Response: Contact the
IBM Service Center. An SVC dump may
Do not specify leading zeros. For example, for message have been produced for this error.
IEC331I 004-33,XXXXXXXX,YYYYYYYY,OPN VSM ACB,ZZZZZZZZ 2 Explanation: An error occurred while
opening a new catalog that is being
search for defined, or the master catalog.
IDC3009I 4 33
Programmer Response: Check for
open/close problem determination
If the search takes you to a description of the reason messages in the job stream output.
code ″x″, it means the reason code you received is one
6 Explanation: A request has referenced
of a group of reason codes having a common
a catalog while catalog management is
description. Most of these represent internal logic errors
processing, or after catalog management
and they will indicate you should contact the IBM
has processed, an access method
Support Center.
services DELETE command for the
Source: Data Facility Product (DFP) specific catalog.
System Action: The system ends processing

Programmer Response: The catalog
associated with the error return code.
needed for the request has been
Application Programmer Response: See the deleted. If needed, the catalog must be
programmer response for the specific return code and redefined before attempting the request
reason code. Inspect other messages concerning again.
DADSM or open/close to aid in solving this problem. If
necessary, contact your programming support
personnel.
351
Reason Reason
Code Description Code Description
8 Explanation: An incorrect access 34 Explanation: An attempt to open a
method control block (ACB) was catalog could not find the VVR record for
supplied to catalog management for a the catalog.
catalog to be used during a catalog
request. Programmer Response: It is possible
that the catalog name is still defined in
Programmer Response: Contact your the master catalog but does not
programming support personnel. physically exist on the expected volume.
23 Explanation: While performing a This is usually a result of reinitializing
GETMAIN from the requested subpool, the volume without doing an EXPORT
the VSAM volume data set (VVDS) DISCONNECT of any user catalogs on
manager protocol module returned an the volume.
error. 60 Explanation: Unable to get storage in
subpool 252 (for EOV) or in subpool 253
Programmer Response: Increase the (for CLOSE).
size of the CSA or run the job again
when more CSA is available. Programmer Response: Increase the
25 Explanation: Unable to get CSA storage REGION size.
(subpool 241). 83 Explanation: The catalog has been
deleted, and CAXWA is still on the chain
Programmer Response: Increase the until all jobs allocated to it end or logoff.
size of CSA or run the job when more
CSA is available. Programmer Response: Do not use the
26 Explanation: Unable to get storage for catalog, or a new catalog with the same
scheduler workarea (subpool 252). name, until all jobs allocated to the old
catalog end or logoff.
Programmer Response: Increase the 84 Explanation: CAXWA count of active
REGION size. users has reached 32767, the maximum
27 Explanation: Unable to get CSA for allowed.
catalog (subpool 241).
Programmer Response: Do not use the
Programmer Response: Increase the catalog until one of the current jobs
size of CSA or run the job when more allocated to it ends or logs off.
CSA is available. 85 Explanation: Unable to get CSA for the
30 Explanation: Unable to get in subpool catalog ACB or for the PCTT (subpool
252. 241)
Programmer Response: Increase the Programmer Response: Increase the

REGION size. size of the CSA or run the job when
31 Explanation: The VVDS manager more CSA is available.
encountered an error processing a 86 Explanation: An error occurred while
VSAM volume record (VVR) request. opening the catalog.
32 Explanation: The system was unable to
complete verification that the required Programmer Response: See
volume is mounted. associated message IEC161I and/or
IEC331I for information about the OPEN
Programmer Response: Ensure that error. The catalog might be damaged.
the unit is available for mounting and Run the DIAGNOSE or EXAMINE
that the correct volume is mounted. command to analyze the catalog.
102 Explanation: An invalid catalog ACB
address was passed in the catalog
parameter list.
Programmer Response: Point the ACB

pointer passed in the parameter list to
the valid ACB of a user catalog.

Reason Reason
104 Explanation: A necessary catalog could 120 Explanation: The master catalog
not be dynamically allocated in the connector record was not found for the
catalog address space, and the catalog named catalog.
parameter list indicated dynamic
allocation in the callers address space Programmer Response: Enter the
was not allowed. access method services LISTCAT
command to display the entries in the
Programmer Response: Check for master catalog. If the user catalog is not
allocation problem determination listed, enter the access method services
messages in the job stream output. IMPORT CONNECT command to
Follow the programmer response for connect the catalog. If the user catalog
these messages. data set name is listed, ensure that the
106 Explanation: A necessary catalog could entry is for a user catalog.
not be dynamically allocated in the 122 Explanation: The master catalog
catalog address space, and the catalog connector record was not found for the
parameter list indicated dynamic named catalog.
allocation in the callers address space
was not allowed. Programmer Response: Enter the
access method services LISTCAT
Programmer Response: Check for command to display the entries in the
allocation problem determination master catalog. If the user catalog is not
messages in the job stream output. listed, enter the access method services
Follow the programmer response for IMPORT CONNECT command to
these messages. connect the catalog. If the user catalog
108 Explanation: A necessary catalog could data set name is listed, ensure that the
not be dynamically allocated in the entry is for a user catalog.
catalog address space, and the catalog
parameter list indicated dynamic
allocation in the callers address space RETURN CODE 8
was not allowed.
Explanation: The entry does not exist, if action is one
Programmer Response: Check for that locates the entry. The entry already exists, if action
allocation problem determination is one which adds an entry to a catalog.
messages in the job stream output.
Follow the programmer response for
Reason
these messages.
Code Description
114 Explanation: A a catalog needed for the
0 Explanation: An entry was not found on
request could not be allocated to the
LOCATE REQUEST.
Catalog address space, and the caller
did not request it be allocated to the
callers address space. Programmer Response: Ensure that
the proper entry was specified.
Programmer Response: When a 2 Explanation: The catalog cluster record
catalog cannot be dynamically allocated was not found.
to the Catalog Address Space, it must
be allocated to the user address space Programmer Response: Call your
before the catalog request is issued. programming support personnel.
118 Explanation: The catalog needed for 6 Explanation: No record was found from
this request has been deleted. record management.
Programmer Response: Redefine the Programmer Response: Ensure that

deleted catalog and reissue the request. the entry name is spelled correctly. In
the instance of an improper DELETE
command entry type, either remove the
type specification or correct it. Check
also that the proper catalog is being
searched for the name you specified.
353
Reason Reason
8 Explanation: A request to place a | 38 Explanation: During an attempt to add
record by key into a catalog resulted in a | an entry to a catalog, either a duplicate
duplicate key error from VSAM. | name or an alias that matches one or
| more level of qualification of the new
Programmer Response: Ensure that | name was found in the target catalog.
the entry name is spelled correctly and | See section on Multi Level Alias Facility
that the proper catalog is being used. | in your ″Managing Catalogs″ manual.
12 Explanation: An incorrect entry type
occurred for super-locate on the entry | Programmer Response: In the DEFINE
named. The data set was not found in a | command, specify a name that does not
catalog. | already exist in the target catalog. In the
| case of a DEFINE ALIAS, make sure
Programmer Response: Ensure that | there are no datasets that currently exist
the proper data set name was specified | with that same high-level qualifier.
in the job control language DD 40 Explanation: A DEFINE GDG command
statement. was not issued prior to the DEFINE
14 Explanation: A generation data group NONVSAM command with GDG entry
(GDG) entry type for super-locate did not name.
find the specified entry in a catalog.
Programmer Response: Ensure that
Programmer Response: Ensure that the GDG base is defined prior to
the proper data set name was specified defining the non-VSAM with a GDG
in the job control language DD entry name.
statement. 42 Explanation: The catalog record for the
16 Explanation: A GDG entry was found to requested entry could not be found.
be deleted from a catalog.
Programmer Response: Ensure that the entry name specified on the access
the proper data set name was specified method services command is in the
in the job control language DD catalog specified.
statement. 44 Explanation: A request to place a
18 Explanation: A GDG type of record by key into an ICF catalog
super-locate request specified an resulted in a duplicate key error from
incorrect generation number. VSAM.
Programmer Response: Ensure that Programmer Response: Ensure that

the proper data set name was specified the entry name is spelled correctly and
in the job control language DD that the proper catalog is being used.
statement. 46 Explanation: A base record was not
20 Explanation: The volume entry being found upon deletion of a cluster, AIX or
removed from an catalog entry during GDG in an ICF catalog.
ALTER REMOVEVOLUMES processing
cannot be found the catalog record. Programmer Response: Run the
DIAGNOSE command to analyze the
Programmer Response: Verify that the catalog. The ICF catalog may have to be
volume serial numbers specified actually restored or rebuilt.
exist in the catalog entry for the data set 50 Explanation: A record was not found
being altered. during LISTCAT ALL processing.
Programmer Response: The requested

record may have been moved during
concurrent catalog updating. Ignore the
error or run the job again.

Reason Reason
52 Explanation: A duplicate data 10 Explanation: An incorrect VSAM volume
component name was found. record was read from the VSAM volume
data set and was detected while
Programmer Response: Ensure that all modifying the catalog’s VSAM volume
data component names are unique and record.
run the job again.
54 Explanation: A duplicate index Programmer Response: Perform the
component name was found. following steps:
1. Try accessing the catalog from
Programmer Response: Ensure that all another system, if shared.
index component names are unique and 2. Run DIAGNOSE or EXAMINE from
run the job again. either system.
3. Use catalog address space (CAS)
RETURN CODE 10 commands to refresh control blocks.
4. IPL will refresh control blocks if CAS
Explanation: An incorrect record type was found. is not available.
5. If the above steps show actual
damage, rebuild or restore the
Reason
catalog. Use the MODIFY
Code Description
CATALOG,CLOSE command if
x Explanation: A record being processed necessary.
contained inconsistent or incorrect data
12 Explanation: The record type for a data
for the type of entry.
set was found to be incorrect during
reset of a reusable data set.
Programmer Response: Run the
DIAGNOSE command to check for a Programmer Response: Ensure that
damaged catalog record. A SYS1.DUMP the target of a reset is a VSAM data set.
may have been produced for this error. Call your programming support
personnel.
0 Explanation: An incorrect record type is
found when trying to find a subrecord to 14 Explanation: On a disconnect request,
be moved. the connector record was missing or
incorrect.
Programmer Response: Run the Programmer Response: Run the
DIAGNOSE command to check for a DIAGNOSE command to determine if
damaged catalog record. the user catalog connector record is
damaged and take the recommended
action.
20 Explanation: The volume cell in the
VVDS catalog record could not be found.
DIAGNOSE command to determine if
the VVDS catalog record is damaged
and take the recommended action.
42 Explanation: A VVDS record contained
inconsistent data.
DIAGNOSE command to check for a
damaged VVDS record.
50 Explanation: VVR or NVR exceeds its
maximum size.
RETURN CODE 12
Explanation: An attempt to locate a needed component

entry in a catalog record failed.
355
Reason Reason
x Explanation: A required component was 4-10,98 Explanation: An ALTER for a migrated
not found within a catalog record. data set was issued, but the call to
DFSMShsm failed. The reason-code
Programmer Response: Run the code is from DFSMShsm.
damaged catalog record. A SYS1.DUMP Programmer Response: Refer to
may have been produced for this error. DFSMShsm message ARC0073I in
(ASB-ERB) for an explanation of the
RETURN CODE 14 reason code and take the appropriate
action.
Explanation: A required cell has not been found in a
catalog record when expected.
RETURN CODE 20
Reason Explanation: There is insufficient space in the catalog

Code Description to perform the requested update or addition.
x Explanation: A required cell was not
found in a catalog record during
processing. Reason
Code Description
Programmer Response: Run the 0 Explanation: The catalog is full. It is
access method services DIAGNOSE impossible to obtain another extent,
command to check for a damaged because there is no more space on the
catalog record. A SYS1.DUMP may have volume in which the catalog resides, or
been created. the maximum number of extents has
been reached.
RETURN CODE 18 Programmer Response: Scratch

unneeded data sets from the volume.
Explanation: An ALTER error occurred. Delete all unnecessary entries from the
catalog. The catalog may need to be
reallocated and rebuilt if these steps do
Reason not resolve the space shortage.
Code Description
0 Explanation: A system request to alter
the backup-while-open (BWO) options RETURN CODE 22
specified an inconsistent or unsupported
state. Explanation: The Field Vector Table (FVT) address is
zero or an incorrect FVT field was found.
Programmer Response: This is most
likely an invalid catalog parameter list.
Contact the IBM Support Center. Reason
2 Explanation: An attempt to alter a data Code Description
set’s storage class name or x Explanation: An invalid structure was
management class name has fail passed as input to a catalog request.
because DFSMShsm was not active.
The system found incorrect data for an Programmer Response: Contact the
alter of a backup while the backup was IBM Support Center.
open.
Programmer Response: Verify RETURN CODE 24

DFSMShsm is operational and retry the
request. Explanation: Permanent read error of a catalog.

Reason Reason
2 Explanation: An I/O error occurred while 4 Explanation: An I/O error occurred
attempting to read information from the during catalog OPEN.
catalog.
Programmer Response: Messages
Programmer Response: Messages IEC331I, IEC332I, and IEC333I have
IEC331I, IEC332I, and IEC333I have been printed to aid in determining the
been printed to aid in determining the cause of the error and where the error
cause of the error and where the error occurred. If a hardware error is not
occurred. If a hardware error is not causing the problem, restore or rebuild
causing the problem, restore or rebuild the catalog.
the catalog. 6 Explanation: One or more entries were
not deleted due to an I/O related error
during DELETE processing.
RETURN CODE 26
Explanation: A VSAM record management error has IEC331I, IEC332I, and IEC333I have
occurred. been printed to aid in determining the
cause of the error and where the error
occurred. If a hardware error is not
Reason
causing the problem, restore or rebuild
Code Description
the catalog.
x Explanation: A VS record management
26 Explanation: An I/O error occurred while
error occurred while processing a
writing the catalog’s self-describing
catalog request.
records.
Programmer Response: Contact the
IBM Support Center. An SVC dump will
IBM Support Center.
be created for this error.
28 Explanation: A close error occurred
after the writing of the catalog’s
RETURN CODE 28 self-describing records.
Explanation: Permanent I/O error in catalog. Programmer Response: Contact the

IBM Support Center.
30 Explanation: An I/O error occurred
Reason writing records to the catalog.
Code Description
2 Explanation: An I/O error processing Programmer Response: Contact the
the catalog occurred while processing an IBM Support Center.
access method services command that
requires modifying the catalog.
RETURN CODE 30
IEC331I, IEC332I, and IEC333I have Explanation: Automated Tape Library Data Server
been printed to aid in determining the (ATLDS) processing error.
cause of the error and where the error
occurred. If a hardware error is not
causing the problem, restore or rebuild Reason
the catalog. Code Description
x Explanation: An internal logic error has
occurred.

IBM Support Center. An SVC dump may
be created for this error, depending on
the specific reason code.
357
Reason Reason
6 Explanation: Attempt to define an alias 48 Explanation: Required volume name
that relates to a volume category. not specified for a define volume
request.
Programmer Response: This is an
incorrect function. Possible user error. Programmer Response: Supply a
18 Explanation: The required library name volume name and rerun the job.
was not specified for a define library 50 Explanation: Incorrect date format
request. specified.
Programmer Response: Supply a Programmer Response: Respecify the

library name and rerun the job. date in the following format:
20 Explanation: Required library id was not YYYY-MM-DD.
specified for a define library request. 56 Explanation: Attempt to alter the
number of scratch volume message
Programmer Response: Supply a thresholds for an incorrect media type.
library id and rerun the job.
22 Explanation: The library logical type Programmer Response: Supply a valid
specified is incorrect for a define library media type and rerun the job.
record request. 58 Explanation: Attempt to alter the
number of scratch volumes for an
Programmer Response: Supply a valid incorrect media type.
library logic type and rerun the job.
34 Explanation: Incorrect name was Programmer Response: Supply a valid
specified for a define volume category media type and rerun the job.
request. 60 Explanation: JOBCAT/STEPCAT was
specified for a request associated with
Programmer Response: The volume volume or library record.
category’s name must begin with
SYS1.VOLCAT.V. Programmer Response: Remove
40 Explanation: Incorrect checkpoint JOBCAT/STEPCAT and rerun the job.
indicator was specified for a define 62 Explanation: No general volume
volume request. category was found.
Programmer Response: Supply a valid Programmer Response: Define

checkpoint indicator and rerun the job. SYS1.VOLCAT.VGENERAL then rerun
42 Explanation: Incorrect volume location the job.
was specified for a define volume 68 Explanation: Non-volume category was
request. specified for a request associated with
volume or library record.
Programmer Response: Supply a valid
volume location and rerun the job. Programmer Response: Insure
44 Explanation: Required library name not SYS1.VOLCAT.VGENERAL is a volume
specified for a define volume request category for library requests. For volume
with a volume location of library entry requests, check all catalogs with
specified. volume category naming convention to
be volume categories.
Programmer Response: Supply a 70 Explanation: A duplicate entry name
library name and rerun the job. was found during define library or
46 Explanation: Incorrect volume use volume request.
attribute specified for a define volume
request. Programmer Response: Remove the
duplicate entry and rerun the job.
Programmer Response: Supply a valid 72 Explanation: General volume category
use attribute and rerun the job. had been deleted or disconnected.
Programmer Response: Redefine or

reconnect general volume category.

Reason Reason
98 Explanation: Incorrect library name 2 Explanation: An incorrect record type
specified for a define library request. The was found in the access method
library name cannot begin with ‘V’. services ALTER command.
Programmer Response: Supply a valid Programmer Response: Determine if

library name and rerun the job. the correct name was specified in the
154 Explanation: Attempting to delete a command or if the proper fields are
library record which is not empty, or requested to be modified for the entry
scratch volumes is not equal to zero. type.
4 Explanation: A data set name was not
Programmer Response: Verify the found on the VTOC.
library record tried to delete. If the library
record is empty and the scratch volumes Programmer Response: Ensure that
count equal to zero then contact the IBM the proper versions of the volume and
Support Center catalog are being processed and that the
158 Explanation: Attempting to delete a volume is synchronized with the catalog,
volume record that has not reached its or ensure that the VVR/NVR entry type
expiration date. in the VVDS matches its corresponding
format 1 DSCB record type from the
Programmer Response: Verify the VTOC.
expiration date. ALTER command may 12 Explanation: A super-locate request to
be used to alter the expiration date. catalog management requires dynamic
168 Explanation: Attempting to delete a access to a catalog.
record without specifying the correct type
in catalog parameter list. Programmer Response: If this error
causes a job to end, ensure that the
Programmer Response: Specify the master catalog references the proper
type and rerun the job. catalogs and that they are available to
the system when the job stream is
processed.
RETURN CODE 32
Explanation: There is an error in the catalog parameter RETURN CODE 38

list. Such a condition indicates an internal error in
access method services (IDCAMS). Explanation: The catalog installation exit module,
replaced by an installation-supplied module,
encountered an error while processing an SVC 26
Reason request. If the module was supplied by the data facility
Code Description hierarchical storage manager (DFHSM), the message
x Explanation: An internal logic error has with this return code was preceded by one or more
occurred. DFHSM messages (ARCxxxI) that indicate the
processing error.
IBM Support Center. A SYS1.DUMP may
be created for this problem.
RETURN CODE 36
Explanation: Data set not found or DSCB indicates a

VSAM data set.
359
Reason Reason
2 Explanation: An error was encountered 12 Explanation: The catalog installation
while attempting to recall a data set with exit module issued a locate request, and
a volume serial of MIGRAT. The catalog catalog indicated that the request was
entry indicated that the data set was not successful.
migrated, but DFHSM determined that
the data set was not migrated. Programmer Response: Review the
DFHSM message or messages and take
Programmer Response: Review the the appropriate action. For reason codes
DFHSM message or messages and take 16 and 24, the DFHSM message was
the appropriate action. For reason codes issued through a TPUT request to the
16 and 24, the DFHSM message was user ID specified on the job that
issued through a TPUT request to the requested this function. In other words,
user ID specified on the job that the message was not routed to the job
requested this function. In other words, log.
the message was not routed to the job 16 Explanation: The catalog installation
log. exit module was processing a JES3
4 Explanation: An error was encountered converter/interpreter (C/I) request for a
while attempting to recall a data set with data set with a volume serial of MIGRAT
a volume serial of MIGRAT (the catalog (the catalog entry indicated that the data
entry indicated that the data set was set was migrated). The exit module
migrated). determined that DFHSM was not ready
to process the JES3 C/I request
Programmer Response: Review the because of one of the following:
DFHSM message or messages and take v DFHSM was not active
the appropriate action. For reason codes v DFHSM did not have volumes defined
16 and 24, the DFHSM message was to which the migrated data set could
issued through a TPUT request to the be recalled
user ID specified on the job that v The storage management subsystem
requested this function. In other words, was not available to determine the
the message was not routed to the job storage class for a migrated
log. SMS-managed data set
8 Explanation: An error was encountered v The recall exit was inoperable
while attempting to delete a data set with
a volume serial of MIGRAT (the catalog Programmer Response: Review the
entry indicated that the data set was DFHSM message or messages and take
migrated). the appropriate action. For reason codes
16 and 24, the DFHSM message was
Programmer Response: Review the issued through a TPUT request to the
DFHSM message or messages and take user ID specified on the job that
the appropriate action. For reason codes requested this function. In other words,
16 and 24, the DFHSM message was the message was not routed to the job
issued through a TPUT request to the log.
user ID specified on the job that 24 Explanation: The catalog installation
requested this function. In other words, exit module was processing a JES3 (C/I)
the message was not routed to the job request for a data set, and determined
log. that the request was from an
unauthorized user.
Programmer Response: Review the

DFHSM message or messages and take
the appropriate action. For reason codes
16 and 24, the DFHSM message was
issued through a TPUT request to the
user ID specified on the job that
requested this function. In other words,
the message was not routed to the job
log.

Reason RETURN CODE 44
Code Description
48 Explanation: The referenced data set is Explanation: The catalog work area for returning
in an incomplete status. results of a catalog request is too small to contain all of
the requested results. If you are using the Catalog
Programmer Response: Recall the Search Interface (CSI) you need to increase the size of
data set and then issue your request the work area you provide for the request. Other
again. occurences of this problem may indicate logic errors in
components or products that use catalog services.
RETURN CODE 40
Reason
Explanation: The volume list or work area is too small. Code Description
This return code would normally represent an error in 2 Explanation: The delete catalog work
the calling program. If the user is using the Catalog area is too small.
Search Interface, this return code indicates that a large
enough return workarea was not provided. Programmer Response: Check the
work area length. If it is correct, contact
the IBM Support Center. If the length is
Reason not correct, run the job again with a valid
Code Description length.
0 Explanation: The user provided work 4 Explanation: The caller’s work area is
area is too small. too small.
Programmer Response: Run the job Programmer Response: If this is a

again with a work area length that is at Catalog Search Interface (CSI) request,
least equal to the required length. you need to increase the size of the
2 Explanation: The format 1 work area is work area. Otherwise, this may be a
too small. logic error or limitation in the component
making the request.
Programmer Response: Run the job 6 Explanation: An access method
again with a work area length that is at services DELETE command to delete an
least equal to the required length. entire generation data group, with the
8 Explanation: The volume list is too FORCE parameter, encountered a work
small to include the storage area too small to contain names of
management subsystem workarea. entries deleted. However, the entire
GDG was successfully deleted. The
following then occurs:
RETURN CODE 42
1. The work area is not large enough to
return the name of the generation
Explanation: A DADSM error occurred on branch entry data base.
to DADSM back end. The DADSM error return data
from the invoked sub-function (SFI) field is the value of 2. The system does not delete the
the variable sfierror in message IEC331I. catalog.
Programmer Response: Run the job

Reason again with a larger work area.
Code Description 8 Explanation: The caller’s work area is
2 Explanation: A DADSM RENAME error too small.
occurred on branch entry.
4 Explanation: A DADSM ALLOCATE Programmer Response: If this is a
error occurred on branch entry. Catalog Search Interface (CSI) request,
6 Explanation: A DADSM SCRATCH error you need to increase the size of the
occurred on branch entry. work area. Otherwise, this may be a
logic error or limitation in the component
making the request.
361
Reason Reason
12 Explanation: The amount of data that 14 Explanation: A data set is update
the system will return may overflow the inhibited.
workarea.
Programmer Response: Do not open a
Programmer Response: Either divide data set for reset processing that is
the catalog into smaller catalogs or inhibited for update processing.
convert to the ICF catalog format. 16 Explanation: A data set is not reusable.
14 Explanation: The amount of data
returned by the system cannot be Programmer Response: Do not open a
contained in a 2-byte length field. non-empty data set for reset processing
that is not reusable.
Programmer Response: None. This is 18 Explanation: It is only valid to change
a design limitation. If you are using the the attributes or ownerid fields of a GDG
CSI (Catalog Search Interface), you base entry by the access method
must request that fullword lengths be services ALTER command.
used for all lengths.
Programmer Response: Do not attempt
the incorrect ALTER commands. Correct
RETURN CODE 48 the commands and rerun the job.
24 Explanation: It is not valid to attempt to
Explanation: Incorrect catalog function. change the name of a user catalog or
alias entry through the use of the access
method services ALTER Command.
Reason
Code Description
x Explanation: An internal logic error has
occurred.
the commands and rerun the job.
change the name of a non-VSAM entry
IBM Support Center.
that is a GDG base or member through
6 Explanation: An ALTER of a non-VSAM
the use of the access method services
entry is not allowed for the fields being
ALTER command.
modified.
the proper entry name was specified on
the commands and rerun the job.
the access method services ALTER
command and that only fields that exist
delete a GDG base entry that contains
for a non-VSAM entry are requested to
non-VSAM entries.
be changed.
8 Explanation: An ALTER of the catalog
Programmer Response: Delete the
name is not allowed.
members of the GDG base explicitly.
Alternatively, the GDG base and its
members may be deleted with the use of
the catalog name was not used by
the FORCE parameter in the DELETE
mistake. Catalog names can only be
command.
changed by DELETE and then
29 Explanation: RBA too large for data set.
re-DEFINE catalog commands.
10 Explanation: Erase option delete, but
file name is for incorrect catalog.
Programmer Response: Do not use a

DD name on the catalog parameter in
the access method services DELETE
command if erase processing is to be
performed.

Reason Reason
30 Explanation: It is not valid to delete the 64 Explanation: A DEFINE of a
master catalog with the FORCE SYS1.VVDS.Vvolser cannot request
parameter. If the user catalog is being space in records.
force-deleted, a stepcat or jobcat card
may be missing or specifies the wrong Programmer Response: Change
catalog. records to tracks or cylinders. Run the
DEFINE command again.
Programmer Response: The master 70 Explanation: An ALTER LOCK of the
catalog cannot be deleted. To delete the master catalog is not allowed.
user catalog, correct the stepcat or 72 Explanation: An incorrect catalog
jobcat card. Submit the job again. management function alter of a
36 Explanation: The ALTER non-VSAM data set name that is
REMOVEVOLUMES volume cleanup cataloged with an indirect volser
function contains incorrect coded occurred.
parameters. 74 Explanation: An alter newname of a
tape data set is incorrect.
Programmer Response: Only the
master catalog name, password, and file Programmer Response: Do not attempt
parameters may be coded for the ALTER the incorrect ALTER commands. Correct
REMOVEVOLUMES function. the commands. Run the job again.
40 Explanation: An incorrect catalog 76 Explanation: An alter of non-VSAM data
management function, ALTER of a VVDS set that contains the extended format
name, occurred. cell is not allowed.
Programmer Response: Do not attempt Programmer Response: None

the incorrect ALTER commands. Correct 78 Explanation: The conversion of SMS to
the commands. Run the job again. non-SMS managed cannot be done for a
42 Explanation: The maximum number of data set that contains the extended
extensions was exceeded. format cell.
80 Explanation: Define data set with
Programmer Response: Redefine the extended format information is not valid
catalog with a RECORDSIZE specifying for a non-SMS data set.
a maximum of 32400. 90 Explanation: Recataloging a temporary
54 Explanation: An incorrect reset of a VSAM data set is not allowed.
non-reusable data set was detected. 94 Explanation: The conversion of SMS to
non-SMS managed cannot be done for a
Programmer Response: Do not open a data set that contains attributes
non-empty data set for reset processing extension information.
that is not reusable. 96 Explanation: Define data set with
56 Explanation: The data set update is attributes extension information is not
inhibited. valid for a non-SMS data set.
98 Explanation: A define of non-extended
Programmer Response: Do not open a data set that contains compress
data set for reset processing that is information is not allowed.
inhibited for update processing.
60 Explanation: A define no-allocate or Programmer Response: None
RECATALOG was not APF authorized. 102 Explanation: The request is against an
SMS-managed data set, but the
Programmer Response: Probable user specified data set is not SMS managed.
error. Ensure that access method 104 Explanation: The user is not authorized
services is APF authorized. to issue ALTER no VVDS update.
108 Explanation: The specified SMS
construct cannot be altered.
112 Explanation: A VSAM data set cannot
be converted to an SMS managed data
set because not all of its components’
names resolve to the same catalog.
363
Reason Reason
118 Explanation: A SMS storage class 152 Explanation: An attempt has been
construct cannot be blanks. made to define a PDSE as a member of
120 Explanation: The ALTER NEWNAME is a GDG base. PDSEs may not be a
not allowed for non-VSAM data set with member of a GDG base
an alias when the new name resolves to
a different catalog than the current one. Programmer Response: Be sure that
122 Explanation: The ALTER NEWNAME is the IGDSMS00 parmlib member has
not allowed for VSAM data set when the DSNTYPE default of PDS.
new name resolves to a different catalog 156 Explanation: The alter backup while
than the current one. open (BWO) request is not for valid
124 Explanation: A VSAM data set cannot component or record.
be converted to SMS managed because
not all of the volumes belong to the Programmer Response: Ensure that
same storage group. the BWO alter request is for cluster,
126 Explanation: A VSAM data set cannot data, non-VSAM, or GDS only.
be converted to SMS managed because 158 Explanation: The alter backup while
not all of its associated names in the open (BWO) indicator is incorrect for
sphere resolve to the same catalog. non-SMS managed datasets
128 Explanation: An SMS storage class
construct cannot have a length of zero. Programmer Response: Ensure that
130 Explanation: Altering a non-SMS the data set is SMS-managed.
managed VSAM data set to an SMS 160 Explanation: An attempt was made to
managed one (or vice versa) is a alter a non-SMS managed non-VSAM
stand-alone function. No other ALTER data set to a name in the format of a
functions are allowed. GDS (e.g. the name ends with
132 Explanation: Altering a non-specific GnnnnVnn).
volume serial to a specific one is a
stand-alone function. No other ALTER Programmer Response: Change the
functions are allowed. name of the new data set to be a
134 Explanation: The caller is not non-GDS format name.
authorized to issue ALTER non-specific 162 Explanation: An attempt was made to
volume. alter a non-SMS managed GDS to a
136 Explanation: An incorrect component non-GDS name.
was supplied for ALTER non-specific 166 Explanation: An alter volume or device
volume. type on OAM entries is not allowed.
140 Explanation: An ALTER GDG limit of 0
is not allowed. Programmer Response: None
142 Explanation: An ALTER fails due to 168 Explanation: An attempt was made to
unsuccessful DADSM UPDATE function. alter an SMS-managed non-VSAM data
144 Explanation: A Record unit of allocation set to a GDS name (e.g. the name ends
not valid for linear data sets. with GnnnnVnn), but there is no GDG
146 Explanation: The ALTER NONVSAM base associated with the new name.
RECATALOG function and the caller
pass SMS information for conversion, Programmer Response: Change the
but the caller is not authorized to use name of the new data set to one that
this function. has an existing GDG base definition.
148 Explanation: Alter request is not valid 170 Explanation: When defining an OAM
for stand-alone function such as alter of data set, a generation data set low level
backup while open (BWO) data set. qualifier (i.e., G0000V00) or an
increment of a GDG number (i.e., +1) is
Programmer Response: Ensure that invalid.
the field requested to be altered is valid
for stand-alone function. Programmer Response: Use a name
other than the GDS low level qualifier or
a GDG increment number. Rerun the
define request.

Reason Reason
172 Explanation: REUSE was specified for 200 Explanation: The ALTER ADDVOL
a non-cluster component or a function cannot be used to cause the
component that had an AIX Associated number of volumes of a SMS-managed
with it. data set to exceed the maximum of 59
174 Explanation: ALTER REUSE was volumes.
specified for a cluster that has an AIX
defined over it. Programmer Response: The maximum
175 Explanation: A DEFINE of a striped allowable volumes for a SMS-managed
data set specified REUSE, which is data set is 59. If this error was issued
invalid. incorrectly, contact the IBM Support
176 Explanation: ALTER REUSE was Center.
specified for a cluster that contains a 202 Explanation: A request to recatalog a
KEYRANGE. temporary non-VSAM data set is not
178 Explanation: ALTER-REUSE-ON and valid.
ALTER-REUSE-OFF are mutually
exclusive. They cannot be active at the Programmer Response: Correct the
same time. request. If the error recurs, contact the
IBM Support Center.
Programmer Response: Only one 204 Explanation: HSM-INCOMPLETE-ON
ALTER-REUSE bit should be set at a and HSM-INCOMPLETE-OFF are
time. mutually exclusive. They cannot be
184 Explanation: Attempted to ALTER the active at the same time.
DDM file class attribute for other than a
CLUSTER or NONVSAM entry. Programmer Response: Only one
186 Explanation: Attempted to ALTER the HSM-INCOMPLETE bit should be set at
pointer to the last active record for other a time.
than CLUSTER or NONVSAM entry. 216 Explanation: Define of ACCOUNT
188 Explanation: Attempted to ALTER DFM information is invalid for
attributes for a non-SMS data set. nonSMS-managed data sets.
190 Explanation: Attempted to ALTER DFM
attributes for other than a CLUSTER Programmer Response: Ensure that
entry. the data set is SMS- managed and then
192 Explanation: Attempted to ALTER DFM rerun the request.
attributes for other than a CLUSTER or 218 Explanation: Alter of ACCOUNT
NONVSAM entry. information is invalid for
194 Explanation: A specific request to locate nonSMS-managed data sets.
an OAM data set was made and a data
set was found, but it is not an OAM data Programmer Response: Ensure that
set. name. the data set is SMS-managed and then
rerun the request.
Programmer Response: Verify that the 222 Explanation: Extended attribute (AX)
name of the data set desired is an OAM cell and ACCOUNT information are
data set. mutually exclusive for define or alter
196 Explanation: A specific request to locate request.
an OAM data set was made and a data
set was found, but it is not an OAM data Programmer Response: Ensure that
set. name. the AX cell and ACCOUNT information
are not both specified during define or
Programmer Response: Verify that the alter of the data set.
name of the data set desired is an OAM
data set.
RETURN CODE 50
Explanation: An error has been detected in VVDS

manager error. Message IEC331I may be produced for
the error and may contain additional information (SFI)
for diagnostic use.
365
Reason Reason
x Explanation: An internal logic error has 7 Explanation: One or more of the 3
occurred, or an error has been detected required VVRs for a catalog was not
in the structure or contents of a VVDS. found. SFI in message IEC331I contains
the first 8 characters of the catalog
Programmer Response: Run a name whose VVR(s) was missing.
DIAGNOSE and print the VVDS
associated with the problem. These Programmer Response: Run
errors will usually be accompanied by DIAGNOSE command against the VVDS
additional console messages which and correct any problem detected.
contain SFI information necessary to 8 Explanation: A DEFINE command for a
diagnose the problem. Contact the IBM VVDS has failed because a VVDS
Support Center. already exists on the volume. No SFI
2 Explanation: New catalog name added. data.
This is a normal return code returned
during the adding of a new VVR. The Programmer Response: If the existing
associated catalog name of the VVR VVDS is to be replaced, delete it before
was new to the VVDS and was added to defining the new VVDS.
the VVCR/VVCN record. 9 Explanation: A dynamic allocation will
require a TIOT slot, but a search finds
Programmer Response: None none available. No SFI data.
4 Explanation: VVDS Manager parameter
list had incorrect information. This Programmer Response: Contact the
attention error code does not effect the IBM Support Center.
operation of the request. 10 Explanation: Bad return code from
dynamic allocation issued from
Programmer Response: Contact the DFSMS/MVS. SFI contains the SVC 99
IBM Support Center. reason code.
5 Explanation: The VVDS required for
LISTCAT could not be accessed. The Programmer Response: Ensure that
missing data in the LISTCAT output will the VVDS name or the volume serial
contain Xs. The volume might be offline, number provided is correct. If an access
but a mount request is not automatically method services command was being
issued for a LISTCAT operation. processed, ensure that all required FILE
parameters are supplied. Ensure that the
Programmer Response: Ignore the volume will be mounted and available by
return code or ensure the volume is providing a DD statement for the
online and available for the LISTCAT volume.
operation. 11 Explanation: The caller of the VVDS
6 Explanation: A requested VVR or NVR manager passed a volume serial number
was not found in the VVDS specified. sfi in the parameter list and a UCB address.
in message IEC331I contains characters The UCB’s volume serial does not match
5 through twelve of the requested VVR the parameter list volume serial. The SFI
name. contains the UCB volume serial while
the parameter list volume serial is in the
Programmer Response: Ensure that second field in the SFI data.
the volume serial numbers provided in
VOLUMES parameters and DD Programmer Response: Contact the
statements are correct. If all the IBM Support Center.
commands are specified correctly, this
condition may indicate an error in the
catalog or VVDS. Run the DIAGNOSE
command to determine if any catalog
records are in error.

Reason Reason
12 Explanation: An attempt to allocate 25 Explanation: An OBTAIN was issued to
space on a DASD volume has failed. read the F1 DSCB for an existing VVDS
SFI contains the historical return code and OBTAIN returned with an error. SFI
from DADSM allocate. contains the register 15 return code from
OBTAIN.
there is enough space for the VVDS Programmer Response: A failure to
data set being defined. The data set will obtain a DSCB for a VVR may indicate
require a minimum of three to four either a damaged VVDS or the existence
tracks. If space was available when the of an orphan VVR. In either case, enter
error occurred, contact the IBM Support the DIAGNOSE command to check the
Center. integrity of the VVDS. Correct any errors
14 Explanation: A request to delete a found as a result of using the
VVDS has failed because the VVDS still DIAGNOSE command.
contained VVRs. SFI contains the RBA 26 Explanation: An OBTAIN was issued to
of the first CI that contains a VVR. read the F1 DSCB for a new VVDS and
OBTAIN returned with an error. SFI
Programmer Response: If the VVDS is contains the register 15 return code from
to be deleted, first delete the VSAM data OBTAIN.
sets on the volume and then run the
DELETE command again. Or, if the Programmer Response: A failure to
VVDS is to be recovered, run the obtain a DSCB for a VVR may indicate
DELETE command again with the either a damaged VVDS or the existence
RECOVERY parameter. of an orphan VVR. In either case, enter
16 Explanation: No storage was available the DIAGNOSE command to check the
for the VVDS manager work area. There integrity of the VVDS. Correct any errors
may be no SFI data because the found as a result of using the
working storage for the VVDS manager DIAGNOSE command.
could not be obtained. Otherwise, SFI 28 Explanation: A call to VSAM end of
will contain the register 15 return code volume to extent the VVDS has failed.
from the GETMAIN request. SFI contains register 15 return code
from end of volume.
IBM Support Center. Programmer Response: There is
17 Explanation: No storage was available probably insufficient space on the
for VVDS manager buffers. SFI contains volume or in the VTOC to extend the
‘xxxxzzzz’ where xxxx is the amount of VVDS, in which case no more VSAM
storage being requested and zzzz is the data sets can be defined on that volume
register 15 return code from the until space is made available to extend
GETMAIN request. the VVDS. If sufficient space is available
at the time this error occurs, contact the
Programmer Response: Increase IBM Support Center.
available LSQA storage. This error can 30 Explanation: While updating the VVDS,
sometimes be avoided by decreasing the it was found to be full and needed to
region size. extend, but was already at the maximum
number of extents (123). There is no SFI
data.
Programmer Response: The volume

must be recovered from backup after
creating a larger VVDS, or unneeded
data sets on the volume must be deleted
to release space in the VVDS.
367
Reason Reason
32 Explanation: The VVDS is full 85 Explanation: During synchronization
(maximum 65536 CIs). There is no SFI processing of the VTOC and VVR
data. extents, the VVDS manager was unable
to read the DSCBS.
Programmer Response: If a VSAM
data set was being defined, use an Programmer Response: Print the
alternate volume. If a VVDS was being VVDS and VTOC. Contact the IBM
defined, decrease the primary space Support Center.
allocation. 86 Explanation: The VVR for the VVDS
38 Explanation: A DELETE command with number of extents field is not valid; it
the NOSCRATCH parameter has been has more than 123 extents in it. SFI
issued for a catalog. The VVR for the contains the VVR’s extent number.
catalog was not deleted because the
catalog has data on the volume. SFI Programmer Response: Print the
contains the RBA of the first CI that has VVDS. Contact the IBM Support Center.
a VVR owned by the catalog. 87 Explanation: During open processing of
a data set, the system discovered that
Programmer Response: Ensure that the extent information in the VVR does
the correct catalog is being used and not match the extent information in the
that the VVDS is correctly specified. DSCB.
40 Explanation: A call to scratch the F1
DSCB from a volume has failed. SFI Programmer Response: Use LISTCAT
contains the return code from the and LISTVTOC statements to determine
scratch. the mismatch. Delete the data set, then
define and reload it.
Programmer Response: It is possible 88 Explanation: A VVR or NVR with the
that a user other than the one issuing correct component name was found, but
the delete has an outstanding ENQ on the catalog name did not match. On a
the VVDS. If this is the case, the ENQ delete request, the BCS record will be
should be removed. deleted, but the VVR or NVR and the
82 Explanation: The system discovered, format 1 DSCB will not be scratched.
during synchronization processing of the There is no SFI data.
VTOC and VVR extents, that the number
of extents indicated for the data set in Programmer Response: No action is
the VTOC is more than the number required because this code is for
indicated in the VVR. information only.
92 Explanation: A request to allocate
Programmer Response: Print the dynamically the VVDS has failed. SFI
VVDS and VTOC. Contact the IBM contains the dynamic allocation error
Support Center. reason code returned in the SVC 99
84 Explanation: The system discovered, request block, or text stating why the
during synchronization processing of the allocation routine failed.
VTOC and VVR extents, that the number
of extents indicated for the data set in Programmer Response: Determine why
the VVR is more than the number the dynamic allocation reason code was
indicated in the VTOC. returned.
94 Explanation: A VSAM OPEN request to
Programmer Response: Print the open the VVDS failed. SFI contains
VVDS and VTOC. Contact the IBM ‘xxrrrrrr’, where rrrrrr=register 15 from
Support Center. the OPEN and xx is ACBERFLG.
Programmer Response: Determine why

the OPEN reason code was returned.

Reason Reason
100 Explanation: A F1 DSCB with a 2 Explanation: The system attempted to
SYS1.VVDS.Vxxxxxx was found and it is verify alter authority to the master
not a VSAM data set. A VVDS cannot be catalog (update authority for an ALTER
created or opened for this volume. NEWNAME), but the the user did not
have the required authority.
Programmer Response: Determine the
source of the non-VSAM data set and Programmer Response: Ensure the
have it renamed or removed. user has the proper authority to the
master catalog. For some types of
requests, only the proper data set
RETURN CODE 52 authority is required, and the master
catalog is only checked if they do not
Explanation: An OBTAIN error occurred while have necessary data set authority.
attempting to access a DSCB in the VTOC. Granting the authority to the data set
may eliminate this error.
4 Explanation: A non-system caller has
Reason specified request special authority level
Code Description checking in the catalog parameter list.
x Explanation: The reason codes are
either the OBTAIN return code, the Programmer Response: Contact the
DADSM diagnostic code, or the CVAF IBM Support Center if the user written
CVSTAT code associated with the error. programs are not calling catalog
management.
Programmer Response: See OS/390 6 Explanation: The user did not have the
DFSMSdfp Diagnosis Reference for an required access authority to the specified
explanation of the completion codes. entry.
RETURN CODE 54 Programmer Response: Ensure the

user has the proper RACF authorization
for the function being requested.
Explanation: Incorrect use of JOBCAT or STEPCAT.
8 Explanation: The return code from the
RACHECK REQUEST=AUTH was other
Reason than 0, 4, or 8.
Code Description
2 Explanation: A JOBCAT or STEPCAT Programmer Response: Determine the
was found in a step that referenced an reason for the unexpected RACF return
SMS data set. code.
4 Explanation: An attempt to define an 14 Explanation: An implicit alter of a GDG
SMS data set with JOBCAT or was denied because the user did not
STEPCAT failed. have the the proper authority to the
GDG base and the catalog.
RETURN CODE 56 Programmer Response: Ensure the

user has the proper authority for the
Explanation: A security verification failed. GDG base.
16 Explanation: The caller is not
authorized for the requested SMS
Management Class, SMS Storage Class,
or both.
28 Explanation: An unauthorized caller
attempted to define an SMS data set.
Programmer Response:Ensure the

caller is APF authorized, or system key
or system state.
369
Reason Reason
30 Explanation: The caller was not 4 Explanation: An incorrect entry type
authorized to the catalog when defining (cluster or non-VSAM) was detected.
an SMS data set into the master catalog.
32 Explanation: The return code from the Programmer Response: Ensure that
RACHECK REQUEST=AUTH was other the name of the entry specified in the
than 0, 4, or 8 when attempting to verify command is correct. Ensure that the
access to a facility class. catalog entry is still valid, by performing
a LISTCAT run. If the reason code
Programmer Response: Determine the indicates a system error, list the catalog
reason for the unexpected RACF return using the PRINT command with the
code. DUMP option. Contact the IBM Support
34 Explanation: An internal logic error has Center. Otherwise, correct the error. Run
occurred. the job again.
6 Explanation: An incorrect cluster entry
Programmer Response: Contact the for ALTER of data set attributes was
IBM Support Center. detected.
36 Explanation: The caller is not
authorized. When no profile exists for Programmer Response: Ensure that
functions that require RACF the name of the entry specified in the
authorization, the caller must be at least command is correct. Ensure that the
APF authorized. catalog entry is still valid, by performing
40 Explanation: RACF options do not a LISTCAT run. If the reason code
permit use or cataloging of uncataloged indicates a system error, list the catalog
non-SMS managed data sets. using the PRINT command with the
42 Explanation: Caller is not authorized to DUMP option. Contact the IBM Support
use the specified volume. Center. Otherwise, correct the error. Run
the job again.
Programmer Response: Acquire 8 Explanation: An incorrect cluster or
authority to the specified volume and index entry for ALTER of buffer size was
resubmit the job. detected.
44 Explanation: Caller is not authorized to
update catalog for DEFINE ATL request Programmer Response: Ensure that
the name of the entry specified in the
command is correct. Ensure that the
RETURN CODE 60 catalog entry is still valid, by performing
Explanation: Incorrect entry type for requested action. indicates a system error, list the catalog
using the PRINT command with the
DUMP option. Contact the IBM Support
Reason Center. Otherwise, correct the error. Run
Code Description the job again.
2 Explanation: Probable system error. An 10 Explanation: An incorrect entry type
incorrect entry type for an extract (CLUSTER) to ALTER the FREESPACE
operation was detected. or WRITECHECK parameters was
detected.
the name of the entry specified in the Programmer Response: Ensure that
command is correct. Ensure that the the name of the entry specified in the
catalog entry is still valid, by performing command is correct. Ensure that the
a LISTCAT run. If the reason code catalog entry is still valid, by performing
indicates a system error, list the catalog a LISTCAT run. If the reason code
using the PRINT command with the indicates a system error, list the catalog
DUMP option. Contact the IBM Support using the PRINT command with the
Center. Otherwise, correct the error. Run DUMP option. Contact the IBM Support
the job again. Center. Otherwise, correct the error. Run
the job again.

Reason Reason
12 Explanation: An incorrect entry type 22 Explanation: The data association in the
(CLUSTER) to ALTER volumes was cluster record does not point to a data
detected. record.

the name of the entry specified in the the name of the entry specified in the
command is correct. Ensure that the command is correct. Ensure that the
catalog entry is still valid, by performing catalog entry is still valid, by performing
a LISTCAT run. If the reason code a LISTCAT run. If the reason code
indicates a system error, list the catalog indicates a system error, list the catalog
using the PRINT command with the using the PRINT command with the
DUMP option. Contact the IBM Support DUMP option. Contact the IBM Support
Center. Otherwise, correct the error. Run Center. Otherwise, correct the error. Run
the job again. the job again.
14 Explanation: Probable system error. An 26 Explanation: ALTER of
incorrect catalog parameter list was EXCEPTIONEXIT was specified, but the
supplied in an attempt to add a volume. entry is not a data or index component.

the name of the entry specified in the the name of the entry specified in the
command is correct. Ensure that the command is correct. Ensure that the
catalog entry is still valid, by performing catalog entry is still valid, by performing
a LISTCAT run. If the reason code a LISTCAT run. If the reason code
indicates a system error, list the catalog indicates a system error, list the catalog
using the PRINT command with the using the PRINT command with the
DUMP option. Contact the IBM Support DUMP option. Contact the IBM Support
Center. Otherwise, correct the error. Run Center. Otherwise, correct the error. Run
the job again. the job again.
14 Explanation: A specific volume serial 28 Explanation: ALTER of average
has been specified in an ALTER RECORDSIZE was specified, but the
ADDVOLUMES or ALTER entry is not a data or index component.
REMOVEVOLUMES for an
SMS-managed data set. Programmer Response: Ensure that
the name of the entry specified in the
Programmer Response: Change the command is correct. Ensure that the
volume serial(s) to a nonspecific value catalog entry is still valid, by performing
(″*″). a LISTCAT run. If the reason code
20 Explanation: The upgrade set indicates a system error, list the catalog
association in the base cluster data using the PRINT command with the
record does not point to an upgrade set DUMP option. Contact the IBM Support
record. Center. Otherwise, correct the error. Run
the job again.
Programmer Response: Ensure that 30 Explanation: ALTER of expiration date
the name of the entry specified in the was specified but the entry is not a
command is correct. Ensure that the cluster, alternate index, or path.
catalog entry is still valid, by performing
a LISTCAT run. If the reason code Programmer Response: Ensure that
indicates a system error, list the catalog the name of the entry specified in the
using the PRINT command with the command is correct. Ensure that the
DUMP option. Contact the IBM Support catalog entry is still valid, by performing
Center. Otherwise, correct the error. Run a LISTCAT run. If the reason code
the job again. indicates a system error, list the catalog
DUMP option. Contact the IBM Support
Center. Otherwise, correct the error. Run
the job again.
371
Reason Reason
32 Explanation: ALTER of last back-up 44 Explanation: An incorrect entry type
date was specified, but the component is was encountered in a DELETE
not a cluster, non VSAM, or GDS. operation, other than the expected alias
34 Explanation: ALTER of last back-up entry.
date was specified, but the data set is
non-SMS managed and does not have a Programmer Response: Ensure that
last back-up date. the proper entry name was specified and
36 Explanation: An alias entry may only be that the catalog reflects the expected
defined for non-VSAM or user catalog structure. It may be necessary to rebuild
entries. the catalog.
46 Explanation: An incorrect entry type
Programmer Response: Do not attempt was encountered in a DELETE
an incorrect DEFINE operation. operation, other than the expected VVR
38 Explanation: A LOCATE or ALTER was type.
specified for a GDG base, and entry is
not a GDG. Programmer Response: Ensure that
the proper entry name was specified.
Programmer Response: GDGs must 48 Explanation: An entry type other than
have qualified names. Ensure that all the expected NVR type was encountered
levels of qualification are specified for in a DELETE operation.
GDG. Submit the job again. 50 Explanation: An incorrect entry type,
40 Explanation: An input base record to other than the expected BCS type, was
catalog upgrade management is not an encountered in a delete operation.
alternate index, cluster or data type
entry. Programmer Response: Ensure that
the correct entry type was specified.
Programmer Response: Ensure that 52 Explanation: ALTER of SMS constructs
the name of the entry specified in the was specified, but the component is not
command is correct. Ensure that the a cluster, non-VSAM, or GDS.
catalog entry is still valid, by performing 54 Explanation: Define an Extended
a LISTCAT run. If the reason code Format UCAT is not allowed.
indicates a system error, list the catalog
using the PRINT command with the Programmer Response: Define the
DUMP 11 option. Contact the IBM UCAT as a non-Extended Format data
Support Center. Otherwise, correct the set.
error. Run the job again. 56
42 Explanation: An input base record to Explanation: ALTER of FILEID or
catalog reusable processing is not a CCSID is not allowed with other DFM
data type entry. attributes.
Programmer Response: Ensure that Programmer Response: Ensure that no

the name of the entry specified in the other DFM attributes are being altered in
command is correct. Ensure that the the same request. Run the job again.
catalog entry is still valid, by performing 58
Explanation: ALTER of CCSID is not
indicates a system error, list the catalog
allowed for non-SMS managed data set,
or the data component of a catalog.
DUMP 11 option. Contact the IBM
Support Center. Otherwise, correct the
error. Run the job again.
the entry being altered is an SMS
managed VSAM or non-VSAM data set.
Correct the error. Run the job again.

Reason Reason
60 74
Explanation: ALTER of FILEDATA is not Explanation: ALTER of ’DFM/NFSS
allowed for non-SMS managed data set. LAST SIZE CHANGE’ field is not
allowed for non-SMS managed data set.
the entry being altered is an SMS Programmer Response: Ensure that
managed VSAM or non-VSAM data set. the entry being altered is an SMS
Correct the error. Run the job again. managed VSAM or non-VSAM data set.
62 Correct the error. Run the job again.
Explanation: An attempt has been 76
made to alter DFM attributes for a Explanation: ALTER of ’DFM/NFSS
non-SMS managed data set. MODIFIED TIME’ field is not allowed for
non-SMS managed data set.
Explanation: ALTER of ’DFM/NFSS 78
ACCESS AUTH’ field is not allowed for Explanation: ALTER of ’DFM/NFSS
non-SMS managed data set. ATTR CHNG TIME’ field is not allowed
for non-SMS managed data set.
ACCESS TIME’ field is not allowed for Explanation: ALTER of ’DFM/NFSS
non-SMS managed data set. BINARY FILE SIZE’ field is not allowed
for non-SMS managed data set.
USERID’ field is not allowed for Explanation: ALTER of ’DFM/NFSS
non-SMS managed data set. LOGICAL RECORD COUNT’ field is not
allowed for non-SMS managed data set.
72 84
Explanation: ALTER of ’DFM/NFSS Explanation: ALTER of ’DFM/NFSS
GROUPID’ field is not allowed for CHARS NO PADDING’ field is not
non-SMS managed data set. allowed for non=SMS managed data set.

the entry being altered is an SMS the entry being altered is an SMS
managed VSAM or non-VSAM data set. managed VSAM or non-VSAM data set.
Correct the error. Run the job again. Correct the error. Run the job again.
373
Reason Reason
86 96
Explanation: ALTER of ’DFM/NFSS Explanation: ALTER of the RLS
TEXT TIMESTAMP’ field is not allowed recovery timestamp (GMT) is not
for non-SMS managed data set. allowed for a data set that is not capable
of being used by RLS. Data sets that are
Programmer Response: Ensure that Linear, non-SMS managed, keyrange or
the entry being altered is an SMS temporary are not eligible for RLS
managed VSAM or non-VSAM data set. access.
88 Programmer Response: Ensure that
Explanation: ALTER of ’DFM/NFSS the entry being altered is eligible for RLS
ATTRIBUTE EXTENSION FLAGS’ is not processing. Correct the error. Run the
allowed for non-SMS managed data set. job again.
98
Programmer Response: Ensure that Explanation: ALTER of the RLS flags is
the entry being altered is an SMS not allowed for a data set that is not
managed VSAM or non-VSAM data set. capable of being used by RLS. Data
Correct the error. Run the job again. sets that are Linear, non-SMS managed,
90 are keyrange or temporary are not
Explanation: ALTER of ’DFM/NFSS eligible for RLS access.
EXTENDSION AREA’ field is not allowed
for non-SMS managed data set. Programmer Response: Ensure that
the entry being altered is eligible for RLS
Programmer Response: Ensure that processing. Correct the error. Run the
the entry being altered is an SMS job again.
managed VSAM or non-VSAM data set. 100
Correct the error. Run the job again. Explanation: ALTER of the BWO flag is
92 not allowed for non-SMS managed data
Explanation: ALTER of the RLS SMS set or a linear data set.
flag is not allowed for a data set that is
not capable of being used by RLS. Data Programmer Response: Ensure that
sets that are Linear, non-SMS managed, the entry being altered is an SMS
keyrange or temporary are not eligible managed VSAM data set that is not
for RLS access. LINEAR. Correct the error. Run the job
again.
Programmer Response: Ensure that 102
the entry being altered is eligible for RLS Explanation: ALTER of ’ACCOUNT
processing. Correct the error. Run the INFORMATION’ is specified but the entry
job again. type is not Data, NonVSAM, or GDS.
94
Explanation: ALTER of the RLS Programmer Response: Ensure that
recovery timestamp (local) is not allowed the name of the entry specified in the
for a data set that is not capable of command is correct. Ensure that the
being used by RLS. Data sets that are catalog is still valid by performing a
Linear, non-SMS managed, keyrange or LISTCAT run. If the reason code
temporary are not eligible for RLS indicates a system error, list the catalog
access. using the PRINT command with the
DUMP11 option. Contact the IBM
Programmer Response: Ensure that Support Center. Otherwise, correct the
the entry being altered is eligible for RLS error and run the job again.
processing. Correct the error. Run the 104 Explanation: Invalid entry type for alter
job again. of extended addressability data set.

Reason Reason
106 Explanation: ALTER of the x Explanation: An attempt to extend a
LOGSTREAMID parameter is not striped data set to a new volume
allowed for a data set that is not capable encountered an internal logic error when
of being used by RLS. Data sets that are locating the volume information in the
Linear, non-SMS managed, are catalog to be updated.
keyrange or temporary are not eligible
for RLS access. Programmer Response: Contact the
IBM Support Center.
processing. Correct the error. Run the RETURN CODE 64
job again.
108 Explanation: ALTER of the LOG Explanation: The associated entry does not exist. This
parameter is not allowed for a data set condition indicates that a system error has occurred
that is not capable of being used by such that the catalog cannot find either a data or an
RLS. Data sets that are Linear, non-SMS index entry which is associated with a cluster or
managed, are keyrange or temporary alternate index entry.
are not eligible for RLS access.
Reason
Code Description
processing. Correct the error. Run the x Explanation:An internal logic error has
job again. occurred.
110 Explanation: ALTER of the FRLOG
parameter is not allowed for a data set Programmer Response: Contact the
that is not capable of being used by IBM Support Center.
RLS. Data sets that are Linear, non-SMS 6 Explanation: The association of a
managed, are keyrange or temporary truename record in an ICF catalog is
are not eligible for RLS access. incorrect.
Programmer Response: Ensure that Programmer Response: Use access

the entry being altered is eligible for RLS method services to define the associated
processing. Correct the error. Run the base of the truename record.
job again.
112 Explanation: An IDCAMS SHCDS
RETURN CODE 66
command with either the CFRESET or
CFRESETDS keywords was issued
Explanation: Bad DADSM parameter list.
against a data set not capable of being
used by RLS. Data sets that are Linear,
non-SMS managed, are keyrange or Reason
temporary are not eligible for RLS Code Description
access.
x Explanation: The reason code listed is
the return code from the DADSM
Programmer Response: Ensure that function, which may have been a
the entry being altered is eligible for RLS RENAME or a SCRATCH request.
processing. Correct the error. Run the
job again.
RETURN CODE 68
RETURN CODE 62
Explanation: No space is available on the user volume.
Only the primary volume will be used for ICF catalogs.
Explanation: An error was encountered while initializing
the extension of a data set.
375
Reason Reason
x Explanation: The return DADSM 8 Explanation: An error occurred while
Historic Return Code was other than 0, attempting to mount the user volume.
4, 8, or 12. The reason code shown is Examples of possible errors include
the DADSM return code. See OS/390 insufficient virtual storage for workareas
DFSMSdfp Diagnosis Reference for an or a time-stamp mismatch problem.
explanation of the DADSM return and
diagnostic codes. Programmer Response: Verify that the
volume and the volume information (time
Programmer Response: The return stamps) contained in the catalog are at
code is returned by DADSM. the same level. If the problem is due to
20,22,24 Explanation: An attempt to allocate an insufficient virtual storage, specify a
SMS-managed data set using the Best larger region parameter. Run the job
Fit interface was able to allocate space again.
on all supplied volumes, but the amount
of space allocated was not the total
amount required. RETURN CODE 74
Programmer Response: The storage Explanation: Cell not found.

group did not contain sufficient space to
allocate the data set.
Reason
Code Description
RETURN CODE 70 0 Explanation: The volume cell for a base
clusters data or index component was
Explanation: Component not found. not found. A DEFINE alternate index
command was being processed.
Reason Programmer Response: Run access

Code Description method services DIAGNOSE command
0 Explanation: An internal logic error has for additional information. The base
occurred procesing a GDS record. cluster may have to be deleted with the
NOSCRATCH option and redefined with
Programmer Response: Contact the the RECATALOG option.
IBM Support Center. 2 Explanation: The relate cell was not
found in the base cluster sphere record
while a moved subrecord update was in
RETURN CODE 72 progress.
Explanation: The user volume is not mounted. The
reason codes are from VSAM open/close/end-of- Programmer Response: Run access
volume, volume mount and verify routine IDA0192V. method services DIAGNOSE command
against the catalog and then determine
the action to be taken. Delete with the
Reason NOSCRATCH parameter. Define with the
Code Description RECATALOG parameter.
4 Explanation: Unable to mount user 4 Explanation: An association cell was
volumes. not found for a path or alias record while
a subrecord move update was in
Programmer Response: Ensure that progress.
proper volumes are implicitly or explicitly
allocated by the JCL. Programmer Response: Run access
method services DIAGNOSE command
against the catalog and then determine
the action to be taken. Delete with the
NOSCRATCH parameter. Define with the
RECATALOG parameter.

Reason Reason
10 Explanation: The SMS cell was not 2 Explanation: The volume was not
found in the VVDS entry for a data set, mounted when expected.
even though the data set is
SMS-managed. Programmer Response: Ensure that
JCL statements cause the proper
Programmer Response: Run access volumes and units to be allocated. Also,
method services DIAGNOSE command ensure that all ddnames specified match
against the catalog and then determine the access method services dname
the action to be taken. The data set may parameter when specified. Determine a
need to be copied to a new SMS data minimum unit count and have sufficient
set and the failing data set deleted. units available for job processing.
12 Explanation: The SMS cell was not Ensure that volumes are allocatable by
found in the BCS entry for a data set, the use of dynamic allocation.
even though the data set is 8 Explanation: A scan of the task I/O
SMS-managed. table (TIOT) failed to find a needed JCL
dd statement.
Programmer Response: Run access
method services DIAGNOSE command Programmer Response: Ensure that
against the catalog and then determine you have all needed JCL DD statements
the action to be taken. The catalog may and that all JCL statements cause the
be repaired by doing a DELETE proper volumes and units to be
NOSCRATCH, followed by DEFINE allocated. Also, ensure that all ddnames
RECATALOG. specified match the access method
services dname parameter when
specified. Determine a minimum unit
RETURN CODE 76 count and have sufficient units available
for job processing. Ensure that volumes
Explanation: No unit available for mounting or volume are allocatable by the use of dynamic
not mounted. allocation.
For a non-VSAM data set, ensure the

Reason number of volumes on the DD statement
Code Description match the number of volumes where the
0 Explanation: Access method services data set resides.
ALTER name change of a unique object 10 Explanation: A scan of the task I/O
was specified, but no volumes containing table (TIOT) failed to find the user
any part of the data set were mounted. specified JCL ddname statement.

JCL statements cause the proper JCL statements cause the proper
volumes and units to be allocated. Also, volumes and units to be allocated. Also,
ensure that all ddnames specified match ensure that all ddnames specified match
the access method services dname the access method services dname
parameter when specified. Determine a parameter when specified. Determine a
minimum unit count and have sufficient minimum unit count and have sufficient
units available for job processing. units available for job processing.
Ensure that volumes are allocatable by Ensure that volumes are allocatable by
the use of dynamic allocation. the use of dynamic allocation.
377
Reason Reason
12 Explanation: A scan of the task I/O 2 Explanation: The related object is a
table (TIOT) failed to find the user relative-record data set or a linear data
specified JCL ddname statement. set.
Programmer Response: Ensure that Programmer Response: Correct the

JCL statements cause the proper DEFINE command so that the entry
volumes and units to be allocated. Also, named in the RELATE parameter is
ensure that all ddnames specified match proper for the type of object being
the access method services dname defined.
parameter when specified. Determine a 4 Explanation: The related object does
minimum unit count and have sufficient not exist.
units available for job processing.
Ensure that volumes are allocatable by Programmer Response: Correct the
the use of dynamic allocation. DEFINE command so that the entry
named in the RELATE parameter is
proper for the type of object being
RETURN CODE 78 defined.
6 Explanation: An alternate index or path
Explanation: Subrecord move error. is not allowed to be built over a catalog.
Reason Programmer Response: Correct the

Code Description DEFINE command so that the entry
named in the RELATE parameter is
x Explanation: An internal logic error
occurred while processing a subrecord.
defined.
8 Explanation: The names of an alternate
index or path and a related object are
IBM Support Center.
identical.
RETURN CODE 80 Programmer Response: Correct the

DEFINE command so that the entry
Explanation: Incorrect related object. The object named in the RELATE parameter is
specified in the RELATE parameter of a DEFINE proper for the type of object being
command does not exist, or is improper for the type of defined.
object being defined. 10 Explanation: There is no pointer to a
related object of an alternate index or
path.
Reason
Code Description Programmer Response: Correct the
x Explanation: An internal logic error DEFINE command so that the entry
occurred. named in the RELATE parameter is
Programmer Response: Contact the defined.
IBM Support Center. 12 Explanation: An alternate index is not to
0 Explanation: The related object is be built over a base cluster, or the
reusable. related path object is not a cluster or an
alternate index.
Programmer Response: Correct the
DEFINE command so that the entry Programmer Response: Correct the
named in the RELATE parameter is DEFINE command so that the entry
proper for the type of object being named in the RELATE parameter is
defined. proper for the type of object being
defined.

Reason Reason
14 Explanation: A DEFINE PATH command 0 Explanation: An unexpired purge date
specified a PATHENTRY name of a exists. An attempt to delete an entry
PAGESPACE object. failed because its expiration date has not
been reached, and the DELETE
Programmer Response: Correct the command did not specify the PURGE
path entry name. Run the DEFINE PATH option.
command again.
16 Explanation: A DEFINE PATH command Programmer Response: Specify the
has specified a PATHENTRY name for a PURGE option if desired. Run the
VVDS. DELETE command again.
2 Explanation: There are conflicting date
Programmer Response: Correct the formats. An attempt to retrieve a date in
path entry name. Run the DEFINE PATH the new format (YYYYDDD) failed
command again. because the request used the old format
20 Explanation: The related object for a (YYDD) by passing the old format field
DEFINE ALTERNATEINDEX is a VVDS. dictionary name DSETEXDT or
DSETCRDT. The date cannot be passed
Programmer Response: Correct the correctly in the old format.
related name. Run the DEFINE AIX
command again. Programmer Response: Submit the job
28 Explanation: The related name again using the new format field
specified for a DEFINE ALIAS command dictionary name DSCRDT2 (creation
is for a record type other than date) or DSEXDT2 (expiration date).
NONVSAM or USERCATALOG. 4 Explanation: An unexpired new format
purge date exists. An attempt to delete
Programmer Response: Ensure that an entry failed because its expiration
the related name is correct and that a date has not been reached, and the
DEFINE ALIAS command is desired. If DELETE command did not specify the
the above is true refer to access method PURGE option. This expiration date is
services DIAGNOSE command to obtain stored in the new format (YYYYDDD)
additional information. and it is beyond the year 1999.
30 Explanation: The version number of the
related generation data set name does Programmer Response: Specify the
not match the version number in the PURGE option if desired. Run the
base GDG. The DEFINE ALIAS will fail. DELETE command again.

RETURN CODE 86
version number in the GnnnnVnn part of
the generation data set name. Run the
Explanation: Recatalog error.
DEFINE ALIAS command again.
40 Explanation: The related object is a
variable relative-record data set. Reason
Code Description
0 Explanation: No related PATHENTRY
RETURN CODE 84
name was found on the path catalog
record.
Explanation: Date error.
the PATHENTRY name is correct. If it is,
refer to access method services,
DIAGNOSE command, to obtain
additional information.
2 Explanation: An internal logic error
occurred.

IBM Support Center.
379
Reason Reason
4 Explanation: Something other than a 10 Explanation: The catalog associated
CLUSTER or alternate index type object with this data set does not match the
specified the RECATALOG parameter. catalog name found in the VVR.
Programmer Response: Ensure that Programmer Response: You can only

the object being recataloged is a cluster recatalog pagespace, swapspace, or
or alternate index. SYS1 data sets to a different catalog
6 Explanation: Either the primary VSAM than the one specified in the VVR. If the
volume record (VVR) points to another data set you are recataloging is one of
catalog, or the primary VVR or those types, or if you are getting this
non-VSAM volume record (NVR) for the error in response to a REPRO
object being recataloged was not found MERGECAT command, contact the IBM
on the first volume serial number support center.
specified. The primary VVR or NVR
contains the data set information needed If your data sets is not one of those
to recatalog the object. types, print the VVR to determine which
catalog the data set should be
Possible causes of this error are: associated with.
v No VVR exists. 12 Explanation: The VVR for the data set
being recataloged indicated it was for a
v A VVR exists, but it points to another
LINEAR data set, but the DEFINE
catalog.
RECATALOG command did not specify
v Parameters were not specified as they the LINEAR keyword.
were when the cluster was originally 14 Explanation: The DEFINE RECATALOG
defined. The parameters are NAME, command specified the LINEAR
INDEXED, LINEAR, NONINDEXED, keyword, but the VVR for the data set
NUMBERED, and VOLUMES. did not indicate it was a LINEAR data
set.
Programmer Response: 16 Explanation: NVR for the object being
recataloged was not found on the
If no VVR exists, then re-issue the volume serial numbers specified.
DEFINE command, without the 18 Explanation: Something other than the
RECATALOG parameter, for the ICF expected NVR was retrieved.
catalog. 20 Explanation: A DEFINE NONVSAM
RECATALOG request was issued on a
If the VVR exists but points to a different volume that does not have the UCBSMS
catalog, specify the correct catalog and indicator on.
re-issue the DEFINE command with the
RECATALOG parameter. Programmer Response: This could
result from an IDCAMS DEFINE
If the original values for parameters NONVSAM RECATALOG request or an
NAME, INDEXED, LINEAR, IDCAMS REPRO request that would
NONINDEXED, NUMBERED, and cause the DEFINE RECATALOG to be
VOLUMES were not specified, specify issued. A DEFINE NONVSAM
the original values and re-issue the RECATALOG request is valid only for
DEFINE command with the SMS NONVSAM data sets. Therefore,
RECATALOG parameter. the volume specified must have the
8 Explanation: The RECATALOG UCBSMS indicator set to on. Check to
parameter is incorrect on the DEFINE see if the volume was removed from the
command for an ICF catalog. active configuration or if the volume was
set to non-SMS status. Correct the error
and run the job again.
22 Explanation: The VVR/NVR catalog
name does not match the name of the
catalog currently oriented to.

RETURN CODE 90 Reason
Code Description
Explanation: Delete error. 18 Explanation: The usercatalog parameter
is missing.
Reason Programmer Response: Specify the file

Code Description parameter. Run the job again.
2 Explanation: An attempt was made to 20 Explanation: DELETE NVR request for
delete the Master Catalog. a NVR with an associated catalog.
Programmer Response: Determine if Programmer Response: This is

the correct catalog is specified. If so, run probably a user error.
the job again with a different master 22 Explanation: No DD was found to
catalog. match the DD name on the DELETE
4 Explanation: The system was unable to NVR request.
determine if the catalog is empty.
Programmer Response: User error.
Programmer Response: Specify Respecify the DDname in the FILE
FORCE, RECOVERY, or run DIAGNOSE parameter. Run the job again.
and recommended action. 24 Explanation: The request is to delete an
6 Explanation: An incorrect DELETE SMS data set only, but the data set is
TRUENAME request was specified. The non-SMS managed.
associated base object exists.
Programmer Response: This is
Programmer Response: User error. probably a user error.
8 Explanation: A pagespace record was 26 Explanation: A required FILE parameter
damaged. It could not be determined if was not specified on the DELETE NVR
pagespace was active. command.
Programmer Response: Run Programmer Response: This is

DIAGNOSE and take the recommended probably a user error.
action. 30 Explanation: DELETE VVR resulted in
10 Explanation: The generation data set an attempt to delete a DSCB that has an
was not found in the GDG. associated VVR with a catalog name
other than the one specified. Nothing
Programmer Response: Run LISTCAT was deleted.
to determine the generation data sets in
the GDG. Run the delete job again with Programmer Response: This is
the correct generation/version number. probably a user error.
12 Explanation: A required FILE parameter 32 Explanation: For DELETE VVR/NVR,
was not specified on the DELETE VVR the VVR/NVR was not found, but a
command. DSCB was found. The DSCB was
deleted.
Programmer Response: Specify FILE
parameter. Run the job again. Programmer Response: This is an
14 Explanation: No DD was found to informational message. No action is
match the supplied DD name on the required.
DELETE VVR request. 34 Explanation: DELETE VVR resulted in
an attempt to delete a non-VSAM DSCB.
Programmer Response: Check FILE Nothing was deleted.
parameter. Run the job again with the
correct DD name. Programmer Response: User error.
16 Explanation: DELETE VVR request for DELETE VVR cannot be used to delete
a VVR with an associated catalog. non-VSAM data sets.
381
Reason Reason
36 Explanation: DELETE VVR resulted in 52 Explanation: The SMSVSAM Server
an attempt to delete a DSCB whose encountered an internal error performing
name resolves to an associated the delete operation. Diagnostic data will
keyrange VVR. Nothing was deleted. be written to Logrec, and a system dump
may have been taken.
Use DELETE CLUSTER. Programmer Response: Refer the
38 Explanation: For DELETE VVR, both problem to IBM programming support
the VVR and DSCB were not found. center.
Nothing was deleted.
Programmer Response: Informational RETURN CODE 94

message. Neither the VVR nor the
DSCB were found. The object name may Explanation: A DADSM OBTAIN request failed during a
be misspelled. If so, run the job again catalog delete request.
with the correct object name specified.
40 Explanation: For DELETE VVR, the
Reason
DSCB was not found.
Code Description
4 Explanation: The correct volume was
Programmer Response: Informational
not mounted for OBTAIN.
message. The VVR was found, but the
associated DSCB was not found. The
Programmer Response: Check the JCL
VVR is deleted.
and file parameters, and ensure that the
42 Explanation: An NVR was retrieved
required volume is mounted.
during a DELETE VVR request.
8 Explanation: OBTAIN did not find
requested format-1 DSCB on specified
volume.
Specify DELETE NVR and run the job
again.
44 Explanation: A VVR was retrieved
the correct volume is mounted.
during a DELETE NVR request.
12 Explanation: OBTAIN encountered an
I/O error in the volume’s VTOC.
Specify DELETE VVR and run the job
Programmer Response: Check for a
again.
possible hardware error.
46 Explanation: DELETE VVR failed to
x Explanation: The reason code is the
specify the system master catalog name
OBTAIN return code.
in the catalog parameter.

meaning of the obtain return code.
Rerun the failing DELETE VVR job
specifying the system master catalog
name in the catalog parameter.
48 Explanation: DELETE CLUSTER failed RETURN CODE 96
because the data set is using RLS
resources. Explanation: An error occurred in specifying key length,
key position, or record size for an alternate index or
Programmer Response: This data set spanned cluster.
must be deleted on a DFSMS/MVS 1.3
or higher system to ensure the RLS
resources are freed.
50 Explanation: DELETE failed because
SMSVSAM Server was not available.
Programmer Response: Retry the

operation when the SMSVSAM Server is
available.

Reason Reason
0 Explanation: The key specified for x Explanation: The reason code is the
spanned record exceeds the control DADSM SCRATCH function status code.
interval size.
Programmer Response: Correct the meaning of the SCRATCH status code.
erroneous parameter (KEYS or See OS/390 DFSMSdfp Diagnosis
RECORDSIZE). Run the job again. Reference for these status codes and
4 Explanation: The maximum logical take the appropriate corrective action
record size for spanned records exceeds before rerunning the job that failed.
the control area size.
Programmer Response: Correct the RETURN CODE 108

erroneous parameter (KEYS or
RECORDSIZE). Run the job again. Explanation: An incorrect field name was found in the
6 Explanation: The alternate index key field parameter list (CTGFL). The field name passed by
position plus the key length for the base AMS does not exist in the catalog management
cluster is larger than the control interval dictionary.
size minus 10 for spanned records.
Reason
Programmer Response: Correct the Code Description
0 Programmer Response: The message
RECORDSIZE). Run the job again.
indicates that the caller’s AMS release
8 Explanation: The alternate index key level or maintenance level is different
position plus the key length for the base from the CATALOG level that is being
cluster is larger than the record size. called. Ensure that IDCAMS and
CATALOG are at the same level.
RECORDSIZE). Run the job again. RETURN CODE 110
Explanation: Unable to modify or delete RACF profile.

RETURN CODE 98
Explanation: An unusual condition occurred during an Reason

ALTER name of a unique or non-VSAM data set. Code Description
4 Explanation: The data set to which an
ALTER RENAME command is directed is
Reason RACF indicated. However, there is no
Code Description RACF profile.
x Explanation: The reason code is the
same as returned by the DADSM Programmer Response: Make the data
RENAME function in the status byte of set RACF-protected or remove the
the RENAME volume list. RACF indicator.
8 Explanation: An ALTER RENAME
Programmer Response: Determine the command has been issued for a
meaning of the RENAME return code, as RACF-protected data set. This failed
documented in the ″Status Codes from because as a result of the new name,
RENAME″ section in OS/390 DFSMSdfp the data set cannot be defined to the
Diagnosis Reference. Correct the error. security subsystem.
Run the job again.
Programmer Response: Use a new
RETURN CODE 102 name acceptable to the security
subsystem.
Explanation: A DADSM SCRATCH request failed
during a catalog delete request for a unique or
non-VSAM data set.
383
RETURN CODE 112 RETURN CODE 118
Explanation: Incorrect field parameter list (FPL). Explanation: The data set name is ineligible for RACF
definition.
Reason
Code Description Reason
4 Explanation: An internal logic error Code Description
occurred. 0 Explanation: As the result of a DEFINE,
IMPORT, or IMPORTRA command,
Programmer Response: Probable VSAM attempted to define a RACF
system error. Contact the IBM Support profile for the object. The profile could
Center. However, if a user program is not be established because the user
interfacing directly with catalog does not have sufficient authority for the
management, the FPL contains improper specified data set characteristics.
data.
Programmer Response: Check the
installation security subsystem guidelines
RETURN CODE 114 for defining a data set in the security
subsystem. Modify the data set
Explanation: A duplicate RACF profile exists. characteristics accordingly.
12 Explanation: As a result of a DEFINE,
IMPORT or IMPORTRA command,
Reason VSAM attempted to define a RACF
Code Description profile for the object. RACF was
0 Explanation: As a result of an IMPORT incapable of building the profile.
or DEFINE command, VSAM has
attempted to establish a RACF profile for Programmer Response: RACF was
a cluster/alternate index, data, or index inactive and could not process the profile
object. This failed because a profile with build request. To activate RACF, contact
the same name already exists. the system security administrator.
Programmer Response: Either:

v Enter an IMPORT or DEFINE RETURN CODE 120
command for the data set with a
different cluster/alternate index, data, Explanation: Attempt to modify the non-existent or
or index name system field. This is a system error.
v Have the owner of the profile with the
name you wish to use delete that
Reason
profile and associated data, if any.
Code Description
0 Programmer Response: Contact the
RETURN CODE 116 IBM Support Center.
2 Explanation: The storage management
Explanation: A catalog record has been damaged, or subsystem field in the BCS is
contains inconsistent data. inconsistent with that field in the VVDS
entries.
Reason
Code Description RETURN
24 Explanation: An incorrect association CODE 124
was returned during upgrade retrieval.
Explanation:
Programmer Response: An IDCAMS Incorrect
DIAGNOSE should be run against the control
catalog and any errors identified interval
corrected. number.

Reason Programmer Response: For the ACS reason code
Code Description referenced in the appropriate SMS SUB-System
2 Explanation: An incorrect relative block Message Manual. Refer to the Storage Management
address (RBA) return code was returned Subsystem Reason Codes, Sub-Sections Subsystem
from VSAM record management. Interface Reason Codes and ACS Service Reason
Codes in the OS/390 DFSMSdfp Diagnosis Reference
for a complete description of the reason codes.
Programmer Response: This is a
system error indicating that the catalog RETURN CODE 128
may need to be restored. Use of the
access method services list catalog
Explanation: A user-provided storage is outside the
(LISTCAT) or DIAGNOSE commands
user region. Probable system error.
may help identify the incorrect entry. It
may be necessary to contact the IBM
Support Center. Reason
34 Explanation: DASDCALC returns either Code Description
an incorrect physical block size or an 0 Explanation: An integrity check of the
incorrect index into the physical block user catalog parameter list (CPL), the
size table. FPL, or the FVT, failed.
Programmer Response: The possible Programmer Response: Contact the

cause of this error is a CI size that is not IBM Support Center unless a
compatible with the physical device. user-written program is interfacing
Correct the CI size and rerun the job. directly with catalog management.
36 Explanation: VSAM record 2 Explanation: A storage validity check
management has returned an invalid CI failed on a user FPL or on the user work
error on an access to a catalog record. area referenced from the CPL.
This error generally occurs because an
invalid CIDF or RDF is detected within a Programmer Response: Contact the
catalog CI. One possible cause is IBM Support Center unless a
damage as a result of a hardware user-written program is interfacing
failure. An IEC331I message will be directly with catalog management.
issued and the SFI information will
6 Explanation: A CPL field that references
contain additional information about the
the work area is zero.
VSAM error.
Programmer Response: Run an access
IBM Support Center unless a
method services DIAGNOSE command,
user-written program is interfacing
and EXAMINE DATATEST against the
directly with catalog management.
catalog. The catalog may need to be
recovered.
RETURN CODE 130
RETURN CODE 126
Explanation: An ALTER RENAME recatalog error.
Explanation: Alter new name of a GDS, non-VSAM or
cluster failed because an ACS service returns a Reason
non-zero return code. Code Description
4 Explanation: Only the old name catalog
entry remains to be deleted, but the
Reason
VTOC still has the DSCB with the old
Code Description
name.
ACS reason Explanation: Catalog management can
6 Explanation: Only the old name catalog
code = only support ACS services reason codes
entry remains to be deleted, but the
catalog from 1000 to 1255. The ACS services
VVDS still has the NVR with the old
reason code return and reason codes are
name.
+ 1000 documented in the OS/390 DFSMSdfp
Diagnosis Reference. 8 Explanation: The DSCB has been
renamed, but no DSCB with either the
old name or the new name can be
found.
385
Reason Reason
10 Explanation: The data set DSCB cannot 124 Explanation: Backout while open
be located. specificaion not valid for non-VSAM data
12 Explanation: The NVR has been set.
renamed, but the NVR with the new 126 Explanation: Backout while open
name cannot be located. specification not valid for ALTER of
14 Explanation: There should be an NVR non-SMS data set.
with the old name, but that NVR cannot 128 Explanation: An internal logic error has
be located. occurred.
16 Explanation: The DSCB has been
renamed without error, but the NVR Programmer Response: Contact the
cannot be renamed because there is IBM Support Center.
already an NVR with that name. 130 Explanation: An internal logic error has
occurred.
RETURN CODE 132 Programmer Response: Contact the

IBM Support Center.
Explanation: Incorrect pointer value in argument list. 132 Explanation: Record Level Sharing
Probable system error. attributes not valid for non-VSAM data
set.
Reason 134 Explanation: Record Level Sharing
Code Description attributes not valid for non-SMS data set.
x Explanation: An expected field value
was not supplied or an internal logic RETURN CODE 136
error occurred. This is probably a logic
error in the caller of catalog
Explanation: Required parameters not supplied.
management.
Probable system error.
Programmer Responsse: Contact the
IBM Support Center. Reason
0 Explanation: Expected component not Code Description
found. x Explanation: An internal logic error has
20 Explanation: There is no pointer to the occurred.
catalog work area in the catalog
parameter list, and the DEFINE function Programmer Responsse: Contact the
is unable to return the names generated IBM Support Center.
for a component. 22 Explanation: A unique data set needs a
DD statement for a rename, or the DD
Programmer Response: Contact the statement is missing.
IBM Support Center unless a
user-written program is interfacing Programmer Response: Supply a
directly with catalog management. dname job control statement.
48 Explanation: The AMDSB information 32 Explanation: An alias name was not
has not been found in the VVR, or provided on a DEFINE command.
VSAM CLOSE passed invalid AMDSB
data to update the VVR. In the latter Programmer Response: Correct the
case, message IEC251I will be issued. DEFINE command. Run the job again.
not found.
34 Explanation: GDG limit or attribute data
were not provided on a DEFINE
Programmer Response: Run the command.
damaged catalog record. Contact the
IBM Support center if message IEC251I
DEFINE command. Run the job again.
was issued.
122 Explanation: Define master catalog or
user catalog with extended format
information or attributes extension
information is not valid.

Reason Reason
40 Explanation: A required DD statement is 4 Explanation: The key range is incorrect
missing for a mountable unit. The for catalog define, or the key ranges are
system is unable to mount the volume not specified in ascending sequence in
required for DELETE NONVSAM the DEFINE of a VSAM key sequenced
SCRATCH processing. data set.
Programmer Response: Use file Programmer Response: Correct the

parameter on DELETE and allocate a DEFINE command.
mountable unit to the job through a DD 6 Explanation: Key ranges were found on
statement. Specify DEFER mount. both data and cluster catalog FVT. This
42 Explanation: An error occurred from is a system error.
IDA0192V while attempting to mount a
volume required for DELETE NONVSAM Programmer Response: If the reason
SCRATCH processing. code indicates a system error, contact
the IBM Support Center. Otherwise,
Programmer Response: Ensure that follow the programmer response
the mountable unit was allocated for indicated by the reason code.
DELETE processing. 8 Explanation: The work area is too
46 Explanation: No storage class small. This is a system error.
information was passed for an SMS
managed data set. Programmer Response: If the reason
code indicates a system error, contact
RETURN CODE 138 follow the programmer response
indicated by the reason code.
Explanation: DADSM RENAME error. 10 Explanation: Space parameters were
found on both cluster and data catalog
FVT. This is a system error.
Reason
Code Description
Programmer Response: If the reason
x Explanation: Volume status code from
code indicates a system error, contact
DADSM.
follow the programmer response
RETURN CODE 140 indicated by the reason code.
20 Explanation: The key lengths for data
Explanation: Inconsistent or conflicting arguments were and index are not equal. This is a
provided. system error.

Reason code indicates a system error, contact
Code Description the IBM Support Center. Otherwise,
2 Explanation: The index component was follow the programmer response
found for relative record data set or indicated by the reason code.
entry-sequenced data set. This is a 28 Explanation: There are an unequal
system error. number of volume serial numbers and
file sequence numbers in list entries.
code indicates a system error, contact Programmer Response: Correct the
the IBM Support Center. Otherwise, input. Run the job again.
follow the programmer response 30 Explanation: More device type entries
indicated by the reason code. exist than volume serial numbers.

input. Run the job again.
387
Reason Reason
34 Explanation: An incorrect space request 74 Explanation: The define of a VVDS had
type on DEFINE was detected. This is a the INDEX option specified. A VVDS is
system error. an entry sequenced data set.
Programmer Response: If the reason Programmer Response: Remove the

code indicates a system error, contact INDEX option. Run the define operation
the IBM Support Center. Otherwise, again.
follow the programmer response 78 Explanation: The request to field
indicated by the reason code. management was not valid.
44 Explanation: A relative-record data set
has a maximum record length that is not Programmer Response: Check the
equal to the average record length. CPL for calling field management.
80 Explanation: The size of the generation
Programmer Response: Correct the data set subrecord exceeds the
input. Run the job again. maximum spanned record size of the
60 Explanation: The logical record size for ICF catalog.
an ICF catalog has been exceeded. The
DEFINE ALIAS has caused the updated Programmer Response:
catalog record to exceed the catalog’s
logical record size. Do one of the following:
v Reduce the size of the generation
Programmer Response: Redefine the data set by removing unused volume
catalog record size to increase the serial numbers.
logical record size to a value up to the
32,400 byte maximum. Run the DEFINE v Define a new ICF catalog with a
of the alias again. larger maximum spanned record size.
The default is 32,400 bytes.
62 Explanation: The maximum average
logical record size is less than 4086 82 Explanation: Key ranges are not
bytes for an ICF catalog define. allowed on a DEFINE of an ICF catalog.
Programmer Response: Remove the
Programmer Response: Increase the KEYRANGES parameter. Run the
maximum average logical record size. DEFINE command again.
Run the DEFINE command again. 84 Explanation: The REUSE parameter
64 Explanation: An incorrect group code was specified with UNIQUE or KEY
for field management was detected. ranges.
Programmer Response: Remove one
Programmer Response: This is a of the conflicting parameters. Run the
system programming error. DEFINE command again.
66 Explanation: The component key length 90 Explanation: More than one volume
exceeds the limit. serial number is specified for the
DEFINE request of a non-VSAM data
Programmer Response: Run the set, and one of the volume serial
DIAGNOSE command to check for a numbers is ******.
damaged catalog record. Programmer Response: If the indirect
72 Explanation: Duplicate volumes exist in volser feature (a non-VSAM data set
the volume list of a non-keyrange data defined with a volser of ******) is wanted,
set. remove the other volsers from the
DEFINE request.
Programmer Response: For a DEFINE, 92 Explanation: A format 2 work area is
remove the duplicate volume from the incorrect for this catalog request.
volume list and rerun the DEFINE. For Programmer Response: Run the job
an ALTER ADDVOLUMES, a volume again with a format 1 work area.
being added might already exist as a
94 Explanation: DEFINE NONVSAM no
primary or candidate volume for the data
BCS for a non-SMS managed data set
set; therefore, remove the volume from
cannot be requested.
the ADDVOLUMES list and rerun the
ALTER.

Reason
Code Description
RETURN CODE 142
96 Explanation: DEFINE NONVSAM no
NVR for a non-SMS managed data set
Explanation:DADSM OBTAIN error.
cannot be requested.
98 Explanation: The new record length will
exceed the maximum VVR or NVR size. Reason
100 Explanation: The number of volumes Code Description
passed exceeds the number of UCB x Explanation: Return code from OBTAIN.
addresses.
102 Explanation: The Volser in the UCB
does not match the volser in the volume RETURN CODE 144
list.
104 Explanation: An incorrect number of Explanation: An incorrect entry name format or the
device types were passed for the ALTER name has an initial character as a numeric.
non-specific volume request.
106 Explanation: An incorrect number of
volumes were passed for the ALTER Reason
non-specific volume request. Code Description
110 Explanation: A 31-bit overflow occurred 2 Explanation: An incorrect first character,
while calculating the required space non-alphabetic, was detected. The
allocation with the values specified in the alternate index or path name is incorrect.
RECORDS parameter.
Programmer Response: Define the entry name.
data set with a smaller space allocation 6 Explanation: The data and index names
request. are not allowed for a catalog.
112 Explanation: An incorrect high-allocated
RBA was found during a define of a data Programmer Response: Avoid the use
component. The high-allocated RBA was of names at the INDEX and DATA level
less than the high-used RBA. of DEFINE MASTERCATALOG and
DEFINE USERCATALOG.
Programmer Response: Reduce the 8 Explanation: A syntax error was
amount of space specified for the data encountered in examining a GDG name.
component of the cluster. Enter the
DEFINE command again. Programmer Response: Correct the
116 Explanation: A request was made to name. Run the job again.
compress a data set that is not an 10 Explanation: A reserved high-level
Extended Format data set. qualifier name was specified on an ICF
define operation. CATINDEX is a
Programmer Response: Contact the reserved high-level qualifier.
IBM Support Center.
120 Explanation: Compressible request is Programmer Response: Change the
allowed for KSDS data set only. name to use a different high-level
qualifier. Run the define operation again.
Programmer Response: Change the 12 Explanation: The data name specified
job to define the data set as a for an SMS VSAM data set does not
non-compressible data set. orient to the same user catalog that the
122 Explanation: Catalog G1000Vxx will cluster did.
cause the GDG to exceed the limit of 16 Explanation: The index name does not
10,999. resolve to the same catalog as the
cluster name did.
Programmer Response: Clean up the
GDG in error then catalog G1000Vxx.
RETURN CODE 150
124 Explanation: Invalid data set type for
extended addressability.
Explanation: Name length error for an SMS construct.
Programmer Response: Clean up the
GDG in error then catalog G1000Vxx.
389
Reason Reason
2 Explanation: An incorrect storage class 2 Explanation: One of the following has
name length was detected. occurred:
4 Explanation: An incorrect data class 1. An access method services DEFINE
name length was detected. or IMPORT command specifies a
6 Explanation: An incorrect management device type that was not system
class name length was detected. generated into the system, or is not
acceptable for a catalog or data set.
2. The volume serial number specified
RETURN CODE 152
is incorrect, or the volume serial
number is missing.
Explanation: A non-empty catalog cannot be deleted.
Programmer Response: Specify a
Reason device type or device name that is
Code Description acceptable to the system.
0 Programmer Response: If the catalog 4 Explanation: An incorrect device name
and all of its entries are to be deleted was specified on a define of a
specify the FORCE parameter on the non-VSAM entry.
access method services DELETE
CATALOG command. Programmer Response: Specify a
device type or device name that is
acceptable to the system.
RETURN CODE 164
Explanation: Insufficient storage is available for a work RETURN CODE 172

area. This condition arises when there is insufficient
virtual storage available for catalog management. Explanation: A duplicate data set name was detected
on a volume during a DEFINE or ALTER NEWNAME, or
a DADSM error occurred during an ALTER NEWNAME.
Reason
Code Description
2 Explanation: A GETMAIN failure Reason
occurred. There is insufficient virtual Code Description
storage available. x Explanation: The return code from a
failed DADSM RENAME.
Programmer Response: Increase the 2 Explanation: A duplicate name was
region size available to the step. detected on a volume during a define of
10 Explanation: A GETMAIN failure a data set.
occurred. There is insufficient virtual
storage available for the catalog Programmer Response: Select another
communication area. data set name, scratch the original data
set from the volume, or ensure that there
Programmer Response: Increase the are as many volumes as key ranges for
region size available to the step. the define of a unique key sequenced
data set (KSDS).
RETURN CODE 168

RETURN CODE 176
Explanation: Unsupported device type.
Explanation: There is no space in the VTOC for a
DSCB. During the definition or extension of a data
space, an attempt was made to perform a DADSM
allocate or extend function on a volume in which a new
DSCB was to have been written, but there is no space
in the VTOC for an additional DSCB.

Reason Reason
0 Programmer Response: Delete any x Explanation: Internal logic error.
unneeded data sets from the volume, in
order to make additional DSCBs Programmer Response: Contact the
available, or recreate the volume with a IBM Support center.
larger VTOC.
RETURN CODE 184

RETURN CODE 178
Explanation: The data set is currently open and cannot
Explanation: An error occurred during ICF catalog be deleted or altered. This condition arises when two
processing of a VSAM partial release request. different jobs are referencing the same VSAM data set
simultaneously, or an attempt was made to delete a
pagespace while there was an active pagespace on the
Reason same volume.
Code Description
2 Explanation: The open-for-output
indicator was found on in the catalog Reason
while a partial release request was being Code Description
processed. Partial release processing 0 Explanation: A rename is not allowed
cannot occur if there are other users for an open data set. The backout has
opened to the data set. been done successfully.
2 Explanation: The data set is currently
Programmer Response: Run an open to another user.
IDCAMS verify against the data set to 4 Explanation: The data or index
reset the open-for-output indicator and component (or both) is in use, and the
re-run the partial release request. data set cannot be deleted.
4 Explanation: The data set is not an
extended format VSAM cluster. Partial Programmer Response: Run the
release processing is supported only for command again. To ensure proper
extended format VSAM clusters. completion, specify a disposition
6 Explanation: The data set name passed parameter of OLD, not SHR.
to a VSAM partial release request was 6 Explanation: The attempted DELETE or
not a VSAM cluster data component. ALTER of a PAGESPACE, or attempted
DELETE CATALOG FORCE that
Programmer Response: Ensure the implicitly deletes a PAGESPACE, cannot
name being passed is the VSAM cluster be allowed. UCB indicates the possibility
data component and re-run the partial of an active PAGESPACE on the
release request. volume.
8 Explanation: A DADSM partial release
request failed. Programmer Response: If a
PAGESPACE is to be deleted or altered,
Programmer Response: Examine the it must not be known at IPL as an
job and system log for related messages eligible PAGESPACE, or the volume
explaining the DADSM failure. must not be online at IPL.
10 Explanation: An attempt was made to 8 Explanation: The data set is in use by
perform partial release processing another job; this reason code usually
against a data set defined with means that a Backup-While-Open
guaranteed space. Guaranteed space (BWO) dump of the data set is in
data sets are not supported for partial progress.
release processing.
requested function again after verifying
RETURN CODE 182 the data set is not currently being
dumped.
Explanation: Bad DADSM UPDATE parameter list.
391
Code Description
Explanation: Error attempting to lock a catalog or 2 Explanation: A required JOBCAT or
access a locked catalog. STEPCAT is not available for processing
of a catalog request. The system ignores
the request until the catalog is available.
Reason
Code Description Programmer Response: If this error
0 Explanation: Lock verification failed. causes a job to end, contact the IBM
Support Center. Otherwise, it is only a
Programmer Response: An means of communicating a condition
unauthorized caller attempted to access within the system that is not an error.
a locked catalog. To access a locked 6 Explanation: The catalog is temporarily
catalog, a user must have read authority unavailable.
to the profile IGG.CATLOCK of class
type FACILITY. Obtain the correct Programmer Response: Try the
authorization. Run the job again. request again at a later time. If a COPY
2 Explanation: Access was denied for one or IMPORT operation has failed, do a
of the following reasons: DELETE RECOVERY and import a
v No profile IGG.CATLOCK of class backup copy of the catalog.
type FACILITY was found
v RACF, or an equivalent product, was As a volume error code: Catalog
not active unavailable for the remainder of
processing which establishes volumes
v No MVS router exit was found
as candidates for future extension. This
occurs during define of VSAM data sets
Programmer Response: Either define only when another error is encountered
the profile IGG.CATLOCK, activate during candidate processing. This code
RACF, or supply an MVS router exit. appears as a volume error code for the
4 Explanation: The caller was not volumes that are not processed due to
authorized for DEFINE LOCK. the other error code which will appear in
the access method services jobstream
Programmer Response: To use the output.
DEFINE LOCK command, a caller must
have read authority to the profile
IGG.CATLOCK of class type FACILITY. RETURN CODE 190
Obtain the correct authorization. Run the
job again. Explanation: Authorization error on a facility class
6 Explanation: The caller was not function applied to SMS data sets.
authorized for ALTER LOCK.
Programmer Response: A caller Reason

attempted to issue either the ALTER Code Description
LOCK command for an unlocked 0 Explanation: The function was ALTER
catalog, or the ALTER UNLOCK BCS only.
command for a locked catalog for which 2 Explanation: The function was
the caller was unauthorized. To use the DIRECTED CATALOG.
ALTER LOCK and ALTER UNLOCK 4 Explanation: The function was DEFINE
commands, a caller must have read NONVSAM with no BCS.
authority to the profile IGG.CATLOCK of 6 Explanation: The function was DEFINE
class type FACILITY. Obtain the correct NONVSAM with no NVR.
authorization. Run the job again. 8 Explanation: The function was DELETE
NVR with no BCS check.
10 Explanation: The function was DELETE
RETURN CODE 188
NOSCRATCH.
12 Explanation: The function was DELETE
Explanation: As a catalog management return code:
GDG FORCE.

Reason Reason
14 Explanation: The function was ALTER 28 Explanation: An error occurred during a
UNCONVERT from SMS managed generic search of the alias table for the
VSAM data set back to non-SMS input data set name.
managed. 30 Explanation: MLA was unable to obtain
16 Explanation: The user is not authorized sufficient memory to hold its in-storage
to perform a ATLDS define, alter or tables.
delete request. 34 Explanation: MLA was unable to obtain
sufficient memory to rebuild its in-storage
Programmer Response: Insure that the tables.
user has read access authority to 40 Explanation: The system number of
’STGADMIN.IGG.LIBRARY’. qualification was not between 1 and 4.
The search order of the multi-level alias
facility is undefined. All requests
RETURN CODE 192 requiring the multi-level alias facility will
fail until the situation is rectified.
Explanation: Maximum logical record length specified
is greater than 32,761 for a non-spanned data set. Programmer Response: Use the
MODIFY CATALOG,ALIASLEVEL
operator command to send a valid level
Reason
of qualification.
Code Description
42 Explanation: MLA detected a damaged
0 Programmer Response: Reduce the
master catalog record. A snap dump was
maximum logical record length or define
taken to aid in resolution of the problem,
the data set as spanned.
and MLA facility in-storage tables were
invalidated.
RETURN CODE 194 44 Explanation: MLA detected a damaged
Explanation: An error occurred during multi-level alias taken to aid in resolution of the problem,
(MLA) facility processing. and MLA facility in-storage tables were
invalidated.
46 Explanation: An error occurred during a
Reason generic search of the alias table for the
Code Description input data set name.
8 Explanation: MLA was unavailable for 50 Explanation: The MLA tables are
the request. incorrect. The generic request cannot be
10 Explanation: MLA detected a damaged fulfilled.
and MLA facility in-storage tables were RETURN CODE 196
invalidated.
14 Explanation: MLA detected a damaged Explanation: The data component control interval size
master catalog record. A snap dump was specified is greater than 32,767.
Reason
invalidated.
Code Description
18 Explanation: MLA detected a damaged
0 Programmer Response: Reduce the
control interval size of the data
component.
invalidated.
20 Explanation: MLA detected a damaged RETURN CODE 198
taken to aid in resolution of the problem, Explanation: An attempt has been made to use an
and MLA facility in-storage tables were unsupported feature.
invalidated.
393
Code Description
6 Explanation: Invalid use of JOBCAT or Explanation: Key specification extends beyond end of
STEPCAT. The catalog pointed to by the maximum logical record.
JOBCAT/STEPCAT resides on a device
that has a UCB defined above 16MB.
Reason
Code Description
RETURN CODE 200 0 Programmer Response: Reduce the
key length, change the key position, or
Explanation: The specified or defaulted control interval increase the logical record length.
size of the index component is greater than the
maximum block size of the index device.
RETURN CODE 208
Reason Explanation: The buffer space specified is too small.

Code Description The buffer size specified is too small to contain the
0 Programmer Response: Reduce the minimum number of control intervals for the type of
control interval size of the index VSAM data set being defined or altered. An indexed
component or use a different device with data set requires enough virtual storage for 2 data
a larger maximum block size. component control intervals, plus 1 for an index
component control interval. A non-indexed data set
requires 2 for the data component.
RETURN CODE 202
Explanation: Storage management subsystem call Reason

error. Code Description
0 Programmer Response: Increase the
buffer size specified through the
Reason BUFFERSPACE parameter of the
Code Description DEFINE command.
0 Explanation: An error was detected 4 Programmer Response: Increase the
during a call to SMS. buffer size specified through the
BUFFERSPACE parameter of the
Programmer Response: Print the OBR ALTER command.
record to get the appropriate error
messages.
2 Explanation: An error was detected RETURN CODE 210
during a call to determine whether all
volumes belong to the same storage Explanation: Subsystem call error.
group.
4 Explanation: An incorrect definition was
passed to the SMS. Reason
Code Description
6 Explanation: Insufficient space was
provided for that definition to the SMS x Explanation: Return code from
subsystem. Subsystem call.
8 Explanation: An attempt was made to
alter the expiration date of an RETURN CODE 212
SMS-managed data set that was defined
with a management class whose
Explanation: Control interval size calculation
maximum number of retention days was
unsolvable. This condition arises should catalog
specified as zero.
management be unable to compute an acceptable
control interval size value. This condition only occurs in
Programmer Response: Redefine the the DEFINE and IMPORT commands.
data set with a management class with
no retention limit or with a specified
retention value equal to or exceeding the
date specified in the ALTER command.

Code Description
0 Explanation: The control interval and Explanation: Alter new name of a GDS, non-VSAM or
the control area calculations are cluster failed because an ACS service returns a
unsolvable with specified parameters. non-zero return code.
Programmer Response: Determine

which of the specifications may have Reason
caused the problem. Code Description
ACS reason Explanation: Adding decimal 256 to the
The following are the possible code = catalog reason code will give the correct
specifications: catalog ASC reason code. The ACS services
reason code return and reason codes are
v Buffer size
+ decimal documented in the OS/390 DFSMSdfp
v Control interval size 256 Diagnosis Reference
v Device type
v Logical record size
4 Explanation: Specified and default Programmer Response To ACS reason code add
values result in only one control interval decimal 256 to obtain the correct error code for
per control area for a key-sequenced reference in the appropriate SMS SUB-System
data set. Message Manual. Refer to the Storage Management
Subsystem Reason Codes, Sub-Sections Subsystem
Programmer Response: Correct the Interface Reason Codes and ACS Service Reason
input. Run the job again. Codes in the OS/390 DFSMSdfp Diagnosis Reference &
6 Explanation: Using the specified or for a complete description of the reason codes.
default values, the maximum index
control interval size for the device would RETURN CODE 224
be exceeded for nonunique objects.
Programmer Response: Increase the Explanation: A field in a catalog entry has exceeded
data control interval size or decrease the the maximum allowable number of repetitions. This
data control area size. condition arises when one of the repeating fields within
8 Explanation: Using the specified or the catalog entry is to be extended, and the extension is
default values, the maximum index not possible. For example, should more than 255
control interval size for the device would volume serials be attempted to be placed in the entry,
be exceeded for unique objects. as might happen when an ALTER command attempts,
through the ADDVOLUMES parameter, to add more
Programmer Response: Increase the
candidate volumes to the entry.
data control interval size or decrease the
data control area size.
10 Explanation: The buffer space is too Reason
small for a nonunique object. Code Description
Programmer Response: Correct the 0 Explanation: The maximum number of
buffer size. Run the job again. volume extent (group occurrence)
12 Explanation: The specified and default pointers have been processed.
value result in only one control interval
per control area for a variable Programmer Response: Determine why
relative-record data set. the excessive values are being supplied.
2 Explanation: More than 255 volume
extent (group occurrence) pointers exist
RETURN CODE 214 in a record, or more than 125 alternate
indexes exist in the upgrade set.
Explanation: Subsystem call error.
System Action: The additional values
are not added to the entry.
Reason
Code Description
Programmer Response: Determine why
x Explanation: Return code from
the excessive values are being supplied.
Subsystem call.
395
Code Description
Explanation: Test authorization macro failed. The caller 13 ECS activation was requested for a
is not authorized to perform the requested function. catalog with the NOECSHARING
attribute.
26 Returned on a non-ECS system when
Reason an attempt is made to access a catalog
Code Description that is ECS-active on another system.
4 Explanation: To OPEN a catalog, the 28 Catalog is temporarily in use by a
caller must be running in key 0 - 7, must non-ECS system.
be in supervisor state, or must be APF 29 ECS-activation of a catalog is requested
authorized. but the catalog does not have
cross-system share options or is not on
To do CLOSE or EOV processing for a a shared volume.
catalog the caller must be running in key | 47 A Coupling Facility error has occurred.
0 - 7, must be in supervisor state, or
must be APF authorized.
| Programmer Response: Correct the
| Correct the coupling facility error (see
To process the CONVERTV function, the | the IXL messages that accompany the
caller must be APF authorized. | coupling facility error). Next, reactivate
| ECS by ensuring that all systems are
Scheduler type superlocate | connected to the ECS structure, and
(non-generic) is restricted. To issue | then issue the F
LOCATE SVC, the caller must be | CATALOG,ECSHR(AUTOADD)
running in key 0 - 7, must be in | command.
supervisor state, or must be APF 48 An attempt was made to add a catalog
authorized. to the Coupling Facility structure for
Enhanced Catalog Sharing use, but the
Programmer Response: Respond to structure is full.
the particular error accordingly. If there is
no fix for the problem, contact the IBM Programmer Response: Increase the
Support Center. size of the ECS structure definition in the
CFRM policy.
RETURN CODE 228
RETURN CODE 232
Explanation: An error occurred while processing an
Enhanced Catalog Sharing request. The following Explanation: An error was encountered while Catalog
reasons may be corrected by the installation. Codes not Management was performing system management
shown indicate an internal system error. facility (SMF) processing.
Reason Reason
x An internal logic error has occurred. x Explanation: The reason code
represents the catalog management
Programmer Response: Contact the return code encountered while
IBM Support Center. performing SMF processing. The catalog
2 ECS workarea storage is not available. management return codes correspond to
3 Coupling Facility connection error. If the return codes listed for this message.
received with message IEC377I, fields
aaaa and bbbb contain the return and Programmer Response: Examine the
reason codes from IXLCONN. reason code returned. Run the job again
4 An ECS request was made but the after performing the required corrective
system is not ECS-active. measures.
9 Coupling Facility disconnection error. If
received with messge IEC377I, fields
aaaa and bbbb contain the return and
reason codes from IXLDISC.

Code Description
Explanation: No user catalog entry in the master 16 Explanation: A delete of a non-VSAM
catalog for Convert Volume processing. object with the scratch option was
specified, but no DD statement was
supplied.
Reason
Code Description Programmer Response: Provide the
0 Programmer Response: Use the required parameter, ensure that the DD
access method services IMPORT statement name is correctly spelled, or
CONNECT command to put an entry for that the DD statement is present for the
the user catalog into the master catalog. step. Also, ensure that the volumes can
be allocated by dynamic allocation. If
these are correct, contact the IBM
RETURN CODE 240 Support Center.
18 Explanation: A delete of a VSAM object
Explanation: Required DD statement not supplied. with the erase option was specified, but
no DD statement was supplied.
Reason
Code Description Programmer Response: Provide the
required parameter, ensure that the DD
0 Explanation: An ALTER of expiration
statement name is correctly spelled, or
date was specified, but no DD statement
that the DD statement is present for the
was supplied.
step. Also, ensure that the volumes can
4 Explanation: The DEVTYPE function
failed during DEFINE processing.
Support Center.
Programmer Response: Provide the
22 Explanation: There was no DDname
match found in the TIOT.
Support Center.
8 Explanation: An incorrect device type
was encountered during DEFINE
processing.
Support Center.
34 Explanation: The system was unable to
determine the DD statement name for a
CRA.
Support Center.
14 Explanation: A delete of a unique object
was specified, but no DD statement was
supplied.
Support Center.
Support Center.
397
Reason Reason
36 Explanation: Either a required DD x Explanation: The reason codes
statement is missing or, if the user is correspond to the VSAM OPEN error
dynamically allocating the data set, the codes. The system write message
limit to the number of data sets that can IEC161I with this message.
be dynamically allocated has been
exceeded. System Action: The system voids the
delete action on that data set.
required parameter, ensure that the DD Programmer Response: Determine why
statement name is correctly spelled, or the erasure was impossible. Alternatively,
that the DD statement is present for the run the DELETE command again with
step. Also, ensure that the volumes can the NOERASE option.
be allocated by dynamic allocation.
Check the DYNAMNBR parameter in the
user’s LOGON procedure to determine if RETURN CODE 246
the limit on the number of data sets that
can be dynamically allocated was Explanation: An internal error has occurred while
exceeded. If these are correct, contact processing a catalog request.
the IBM Support Center.
Reason
RETURN CODE 242 Code Description
x Explanation: An internal error has
Explanation: A physical I/O error occurred trying to occurred.
erase the data set being deleted.
System Action: An SVC dump may be
produced for the error, depending on the
Reason reason code. Processing of the catalog
Code Description request is terminated.
x Explanation: The reason codes
correspond to the VSAM Record Programmer Response: Determine if
Management error codes. an SVC dump was created for this
failure, and contact the IBM Support
Programmer Response: Run the job Center for assistance.
again with the NOERASE option. The
data set cannot be deleted.
RETURN CODE 250
RETURN CODE 244 Explanation: VSAM Record Management has found a

logical error during erase processing while deleting a
Explanation: Erase action failed. This condition arises VSAM data set.
when Catalog Management is unable to open the
VSAM data set being deleted.
Reason
Code Description
x Explanation: The reason codes
correspond to the VSAM record
management logical error codes.
System Action: The system ignores the

delete action on that data set. The
Programmer Response: The data set

cannot be erased. Run the DELETE
command again with the NOERASE
option.

RETURN CODE 254 entname
The entry name.
Explanation: An error was encountered during catalog Application Programmer Response: Verify that the
reorientation. entry name is spelled correctly. If a catalog was
specified in the command or in a JOBCAT or STEPCAT
statement, ensure that it is correct.
Reason
Code Description If no catalog was specified, ensure that the first-level
2 Explanation: The opening of a catalog qualifier of the data set name is the name of a user
failed during catalog reorientation. catalog or the alias of a user catalog.
4 Explanation: The allocation of a catalog Source: DFSMSdfp
unit failed.
Detecting Module: IDCCN01, IDCLC01, IDCMP01,
IDCSA02, and IDCXP02 processing associated with the
entry name.
IDC3010I UNABLE TO OPEN dsname
Explanation: The dname specified in the command IDC3013I DUPLICATE DATA SET NAME
indicated either concatenated catalogs or a different
data set. Explanation: One of the following conditions has
occurred:
v The data set name supplied by the caller already
dsname exists in the specified catalog.
The data set name. v The data set name supplied by the caller already
System Action: The command ends with a condition exists as the first-level qualifier of a data set name in
code of 12. the specified catalog.
v The first-level qualifier of the data set name supplied
by the caller already exists as either a data set name
dname specified in the command does not identify a DD
or an alias name in the catalog.
statement that defines concatenated catalogs, unless
the desired catalog is the first in the concatenation.
See the associated second-level message for the
Ensure that the command and the JCL specify the
specific catalog management error code values.
same data set.
System Programmer Response: If the error recurs In the Time Sharing Option/Extensions (TSO/E)
and the program is not in error, look at the messages in environment the second-level message is not displayed,
the job log for more information. Search problem except by request. To request it, enter a question mark
reporting data bases for a fix for the problem. If no fix (?) after the TSO READY message.
and the SYSOUT output for the job. System Action: The system ends processing of the
command.
Source: DFSMSdfp
Application Programmer Response: Verify that the
Detecting Module: IDCAL01, IDCBI01, IDCCC01, entry name is spelled correctly. Check the use of the
IDCCN01, IDCDE01, IDCDE02, IDCDL01, IDCLC02, JOBCAT and STEPCAT catalogs, if employed. Ensure
IDCMP01, IDCRC02, IDCRM01, IDCRS01, IDCRS06, that the data set name or the first-level qualifier of the
IDCSA02, IDCXP01 data set name specified is not the same as a data set
name or the first-level qualifier of either a data set name
or an alias name that already exists in the specified
IDC3012I ENTRY entname NOT FOUND
catalog.
Explanation: The data set name supplied by the caller
Source: DFSMSdfp
is not in the specified catalog. If a catalog was not
specified, the entry name is the first-level qualifier of a Detecting Module: IDCTP06
qualified data set name and not the name of a user
catalog or an alias of a user catalog, as expected. See
the associated second-level message for the specific IDC3014I CATALOG ERROR
catalog management error code values. Explanation: An error occurred during a catalog
In the Time Sharing Option/Extensions (TSO/E) operation. See the associated second-level message for
environment the second-level message is not displayed, the specific catalog management error code values.
except by request. To request it, enter a question mark In the Time Sharing Option/Extensions (TSO/E)
(?) after the TSO READY message. environment the second-level message is not displayed,
In the message text: except by request. To request it, enter a question mark
399
(?) after the TSO READY message.
IDC3017I INSUFFICIENT SPACE IN CATALOG
System Action: The system ends processing
Explanation: The catalog is full. There is no more
associated with the catalog error.
space on the volume in which the catalog resides, or
Application Programmer Response: See the the maximum number of extents has been reached. See
programmer response associated with the second-level the associated second-level message for the specific
message. catalog management error code values.
Source: DFSMSdfp In the Time Sharing Option/Extensions (TSO/E)

environment the second-level message is not displayed,
Detecting Module: IDCTP06 except by request. To request it, enter a question mark
IDC3015I ** VSAM CATALOG RETURN CODE IS System Action: The system ends the command.
return-code - REASON CODE IS
reason-code Application Programmer Response: Scratch
unneeded data sets from the volume. Delete unneeded
Explanation: System interface errors. Catalog VSAM data sets. See your system programmer for
management returned the return code and reason code assistance in reorganizing the catalog.
indicating either a catalog error or exceptional condition.
Source: DFSMSdfp
return-code
The return code
IDC3018I SECURITY VERIFICATION FAILED
reason-code
The reason code, which is one of the following: Explanation: The number of attempts was exceeded
by the operator, or the user-specified verification routine
Code Explanation failed to authorize use of the data set or the caller’s
004 Non existent catalog RACF authorization was inadequate. See the
associated second-level message for the specific
122 Common filter service error catalog management error code values.
186 Catalog log related error In the Time Sharing Option/Extensions (TSO/E)
188 Catalog temporarily unavailable environment the second-level message is not displayed,
except by request. To request it, enter a question mark
System Action: Processing associated with the error (?) after the TSO READY message.
return code is halted.
programming support personnel. Application Programmer Response: Correct the
password specified, obtain the required RACF
Source: DFSMSdfp authorization, or determine why the verification routine
Detecting Module: IDCLC01 did not allow access.
Source: DFSMSdfp
IDC3016I CATALOG IS NOT AVAILABLE Detecting Module: IDCTP06
Explanation: A required catalog is unavailable to
perform the specified command. See the associated IDC3019I INVALID ENTRY TYPE FOR
second-level message for the specific catalog REQUESTED ACTION
management error code values.
Explanation: This condition arises if, for example, an
In the Time Sharing Option/Extensions (TSO/E) attempt was made to DELETE an index component of a
environment the second-level message is not displayed, VSAM data set. See the associated second-level
except by request. To request it, enter a question mark message for the specific catalog management error
(?) after the TSO READY message. code values.
System Action: The system ends the command. In the Time Sharing Option/Extensions (TSO/E)
Application Programmer Response: Ensure that the environment the second-level message is not displayed,
catalog specified by the command exists or determine except by request. To request it, enter a question mark
why it cannot be accessed. (?) after the TSO READY message.
Source: DFSMSdfp System Action: The system ends the command.
Detecting Module: IDCTP06 Application Programmer Response: Ensure that the

specified action is allowed for this entry type. The entry

type can be validated by the LISTCAT command. RELATE parameter is correct.
Detecting Module: IDCTP06 Detecting Module: IDCTP06
IDC3020I UNABLE TO ALLOCATE SPACE ON IDC3023I UNEXPIRED PURGE DATE

USER VOLUME
Explanation: An attempt to delete an entry failed
Explanation: A specified volume cannot accommodate because its expiration date has not been reached. The
either the initial allocation of space or a subsequent PURGE option was not specified. See the associated
extension. See the associated second-level message second-level message for the specific catalog
for the specific catalog management error code values. management error code values.
In the Time Sharing Option/Extensions (TSO/E) In the Time Sharing Option/Extensions (TSO/E)
environment the second-level message is not displayed, environment the second-level message is not displayed,
except by request. To request it, enter a question mark except by request. To request it, enter a question mark
(?) after the TSO READY message. (?) after the TSO READY message.
System Action: The system ends the command. System Action: The system ends the command.
Application Programmer Response: Scratch Application Programmer Response: Specify the
unneeded data sets from the volume, or run an ALTER PURGE option. Run the command again.
command to add candidate volumes for the data set.
Source: DFSMSdfp
Source: DFSMSdfp
IDC3024I VOLUME OWNED BY ANOTHER
IDC3021I USER VOLUME NOT MOUNTED CATALOG
Explanation: An attempt to update the volume table of Explanation: Only one catalog may own or allocate
contents (VTOC) on a volume failed because the space upon a given volume. See the associated
volume was not mounted. See the associated second-level message for the specific catalog
second-level message for the specific catalog management error code values.
management error code values.
In the Time Sharing Option/Extensions (TSO/E)
In the Time Sharing Option/Extensions (TSO/E) environment the second-level message is not displayed,
environment the second-level message is not displayed, except by request. To request it, enter a question mark
except by request. To request it, enter a question mark (?) after the TSO READY message.
Application Programmer Response: Do one of the
Application Programmer Response: Ensure that the following:
volume is mounted. v Specify an unowned volume. Run the command
Source: DFSMSdfp again.
v Use the ALTER REMOVEVOLUMES command to
reset the volume ownership if a catalog does not own
the volume.
IDC3022I INVALID RELATED OBJECT
Source: DFSMSdfp
Explanation: The object specified in the RELATE
parameter of a DEFINE command does not exist or is
improper for the type of object being defined. See the
associated second-level message for the specific IDC3025I INSUFFICIENT SUBALLOCATION DATA
catalog management error code values. SPACE
In the Time Sharing Option/Extensions (TSO/E) Explanation: A volume does not contain a data space
environment the second-level message is not displayed, with sufficient room for allocation of another virtual
except by request. To request it, enter a question mark storage access method (VSAM) data set. See the
(?) after the TSO READY message. associated second-level message for the specific
catalog management error code values.
DEFINE command so that the entry named in the
401
except by request. To request it, enter a question mark v Delete any unneeded data sets or data spaces from
(?) after the TSO READY message. the volume to make additional DSCBs available.
System Action: The system ends the command. v Recreate the volume with a larger VTOC.
Application Programmer Response: Do one of the Source: DFSMSdfp

following: Detecting Module: IDCTP06
v Use the DEFINE command to create additional data
space.
IDC3028I DATA SET IN USE
v Delete unneeded VSAM data sets.
Explanation: The data set is currently open and
v Decrease the amount of storage required by the
cannot be deleted. This condition arises when two
object being defined.
different jobs are referencing the same virtual storage
Source: DFSMSdfp access method (VSAM) data set simultaneously. See
the associated second-level message for the specific
IDC3026I DUPLICATE DATA SPACE NAME ON
VOLUME
Explanation: A DEFINE operation specifies the name (?) after the TSO READY message.
of a data set, with the UNIQUE attribute, but there is
already a data set on the volume with the same name.
This will also occur when attempting to define a key Application Programmer Response: Run the
sequenced data set (KSDS), with the UNIQUE attribute, command again. Specify disposition of OLD, not SHR.
which has more than one key range on the same
Source: DFSMSdfp
volume. See the associated second-level message for
the specific catalog management error code values. Detecting Module: IDCTP06
environment the second-level message is not displayed, IDC3029I LOGICAL RECORD LENGTH EXCEEDS
except by request. To request it, enter a question mark 32761
Explanation: The maximum logical record length
System Action: The system ends the command. specified is greater than 32,761 for a non-spanned data
set. See the associated second-level message for the
Application Programmer Response: Choose another
data set name. Scratch the original data set from the
volume. If duplication is due to key ranges, ensure that In the Time Sharing Option/Extensions (TSO/E)
each UNIQUE key range is on a separate volume. environment the second-level message is not displayed,
Source: DFSMSdfp
Application Programmer Response: Reduce the
IDC3027I NO SPACE IN VTOC OR VTOC INDEX
maximum logical record length or define the data set as
Explanation: During the definition or extension of a spanned.
data space, an attempt was made to perform a DADSM
Source: DFSMSdfp
allocate or extend function, but either there was no
space in the volume table of contents (VTOC) for an Detecting Module: IDCTP06
additional data set control block (DSCB) or there was
not enough space in the VTOC index for a new entry.
See the associated second-level message for the IDC3030I CONTROL INTERVAL SIZE TOO
specific catalog management error code values. LARGE
In the Time Sharing Option/Extensions (TSO/E) Explanation: The data component control interval size
environment the second-level message is not displayed, specified is greater than 32,768 or the index component
except by request. To request it, enter a question mark control interval size is greater than the maximum block
(?) after the TSO READY message. size of the index device. See the associated
second-level message for the specific catalog
System Action: The system ends the command. management error code values.
Application Programmer Response: Do one of the In the Time Sharing Option/Extensions (TSO/E)
following: environment the second-level message is not displayed,

IDC3033I VOLUME RECORD NOT FOUND IN
CATALOG
Explanation: This condition arises when a function
Application Programmer Response: Do one of the requires a volume that is not owned by the virtual
following: storage access method (VSAM) catalog being used.
v Reduce the control interval size. See the associated second-level message for the
v If the error occurred due to the index component’s
device type, use a different device with a larger In the Time Sharing Option/Extensions (TSO/E)
blocksize. environment the second-level message is not displayed,
Source: DFSMSdfp (?) after the TSO READY message.
Detecting Module: IDCTP06 System Action: The system ends the command.
IDC3031I KEY EXTENDS BEYOND MAXIMUM volumes specified have been defined in the catalog
RECORD LENGTH against which the request is being issued.
Explanation: The KEY specification extends beyond Source: DFSMSdfp
the end of the maximum logical record. See the
associated second-level message for the specific Detecting Module: IDCTP06
In the Time Sharing Option/Extensions (TSO/E) IDC3034I COMMAND FAILED DUE TO
environment the second-level message is not displayed, DUPLICATE RACF PROFILE
Explanation: As a result of an IMPORT, IMPORTRA
or a DEFINE command, virtual storage access method
System Action: The system ends the command. (VSAM) catalog management has attempted to
establish a profile. This attempt failed because a profile
Application Programmer Response: Do one of the with the same name exists. Note that in addition to this
following: message, an IDC3009I message with a 114 return code
v Reduce the key length will also be issued.
v Change the key position System Action: The system ends the command.
v Increase the record length
Source: DFSMSdfp reason code on the accompanying IDC3009I message.
Take the recommended action for this reason code. Run
the job again.
Source: DFSMSdfp
IDC3032I BUFFERSPACE TOO SMALL
Explanation: The buffer size specified during a define
operation is too small to contain the minimum number of
control intervals for the virtual storage access method IDC3036I DATA SET COULD NOT BE DEFINED
(VSAM) data set being defined. See the associated TO SECURITY SUBSYSTEM
second-level message for the specific catalog
management error code values. Explanation: Catalog management attempted to
define a RACF profile for the data set. The security
In the Time Sharing Option/Extensions (TSO/E) subsystem rejected the RACF DEFINE command
environment the second-level message is not displayed, because the characteristics of the caller and the data
except by request. To request it, enter a question mark set make the data set not eligible for definition.
Application Programmer Response: Compare the
Application Programmer Response: Increase the characteristics of the data set with the inclusion
BUFFERSPACE parameter of the DEFINE command. standards of the security subsystem package as
specified in the installation security subsystem
Source: DFSMSdfp
documentation. Modify the data set characteristics. Run
Detecting Module: IDCTP06 the job again.
Source: DFSMSdfp
403
standard information for the volume but also
IDC3037I STORAGE FOR NUMBER OF ENTRIES
highlights the preceding volume and that serial
EXCEEDS 16M LIMIT
number is recorded in the volume label of the
Explanation: IDCAMS runs below the 16M line and is volume.
unable to satisfy the users request due to a storage v For a rename operation failure for MODIFYV, recover
constraint. from a MODIFYV rename by:
System Action: The system ends the request. – Running ADDV to activate the volume if the
volume is merely inactive and has no volume
Application Programmer Response: The user can
serial mismatch condition
modify the command to avoid this situation. For
example, when issuing a LISTCAT level, additional – Running ADDV to both activate the volume and
qualifiers can be specified which will avoid exhausting complete the rename operation if the volume is
storage. both inactive and has a volume serial mismatch
condition
– Running MODIFYV again to complete or retry the
IDC3062I ** CARTRIDGE LABELS AND
rename operation if the volume is active but has a
INVENTORY RECORD NOT RESTORED
mismatch condition
Explanation: An error was encountered while – Running STOREV to complete or retry the rename
relabeling a mass storage volume. The attempt to operation if the volume is active and if a duplicate
restore the labels of the cartridges and Inventory data volume serial number is desired as a result of the
set to their original status failed. The volume serial rename. For the DD statement requirements, the
mismatch may exist between the cartridge labels and proper VOLUME and NEWSERIAL parameter
volume label for the volume. See the preceding values, and use of LISTMSVI, refer to the
message for further explanation of the problem. description above for an ADDV rename failure.
System Action: The system ends the command. System Programmer Response: If the error recurs
Application Programmer Response: Correct the and the program is not in error, look at the messages in
problem as identified in the preceding message. Take the job log for more information. Search problem
the following actions for the command that failed: reporting data bases for a fix for the problem. If no fix
v For a rename operation failure for ADDV, run ADDV JCL, the SYSOUT output for the job, and all printed
to backout or retry the rename operation if the output and output data sets related to the problem.
MODIFYV or STOREV to either backout or retry the Source: DFSMSdfp
rename operation.
Detecting Module: IDCAV01, IDCMV01, IDCSR01
run to recover from a rename failure, a DD statement
for the volume is required and must specify deferred IDC3066I ** UNABLE TO CLEAR INCOMPLETE -
mounting. The values specified for the VOLUME and COPY FLAG FROM INVENTORY
NEWSERIAL parameters depend upon how the RECORD
volume record is recorded in the Inventory data set. If Explanation: The incomplete-copy flag in the
the cartridge labels have been updated, the volume Inventory record for the volume could not be cleared.
record will be identified by the new volume serial See the preceding message for further explanation of
number. the failure.
For the VOLUME parameter, specify the volume
System Action: The system ends the command with
serial number as recorded in the cartridge labels and
an error message.
the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number. Note that Application Programmer Response: Correct the
the security check for non-virtual storage access problem as indicated in the preceding message. Take
method (VSAM) status and password protected data one of the following actions for the command that failed:
sets is bypassed only if the NEWSERIAL parameter v For a copy operation failure in COPYV, run COPYV
specifies the same volume serial number as recorded again to complete the copy operation to the
in the Inventory data set for the volume label. This incomplete copy volume. COPYV will reuse the
allows the original volume serial number of a VSAM cartridges of the incomplete copy volume for the new
volume to be restored if the volume is left partially copy. Or run SCRATCHV to scratch the incomplete
renamed. copy volume before rerunning the COPYV command.
If ADDV, MODIFYV, or STOREV terminates without If COPYV ends without indicating the status of the
indicating the status of the rename operation, run copy operation, run LISTMSVI to determine whether
LISTMSVI to determine whether the volume is the volume is flagged for recovery purposes. If the
flagged for recovery purposes. If the mismatch flag is incomplete copy flag is set in the copy volume
set in the volume record, LISTMSVI not only lists the

record, LISTMSVI not only lists the standard information for the volume but also highlights the
information for the volume but also highlights the volume report with a note that a copy operation failed
volume report with a note that a copy operation failed for the preceding volume.
for the preceding copy volume.
v For a copy operation failure for RECOVERV, run and the program is not in error, search problem
RECOVERV again to complete the recover operation reporting data bases for a fix for the problem. If no fix
to the target volume that is flagged as an incomplete exists, contact the IBM Support Center. Provide the
copy volume. Otherwise, run SCRATCHV to scratch JCL, the SYSOUT output for the job, and all printed
the target volume. The incomplete copy volume may output and output data sets related to the problem.
even be used as the target volume in the
CONVERTV command. In all cases, the empty Source: DFSMSdfp
volume table of contents (VTOC) check or security Detecting Module: IDCAV01, IDCMV01, IDCSR01
check for password protected data sets is bypassed.
If the SCRATCHV command is run, the DD statement
is not required for the volume and if provided, must IDC3067I {FROM|TO}VOLUME volser OWNED BY
specify deferred mounting. If the RECOVERV A VSAM CATALOG
command is run again, the DD statement is not Explanation: A virtual storage access method (VSAM)
required for the target volume, which is flagged as an catalog owns the specified volume. The volume cannot
incomplete copy, unless the volume serial number of be used.
the target volume is different from the source volume.
If a DD statement is provided for the target volume, In the message text:
deferred mounting must be specified. FROM|TO
If a virtual storage access method (VSAM) catalog is Indicate which volume is unusable for those
on the volume, a DD statement for the catalog is not commands processing both a source and
required. If one is provided, specify deferred target volume having the same volume serial
mounting. numbers.
If RECOVERV ends without indicating the status of volser The volume serial number.
the recover operation, run LISTMSVI to determine
whether the volume is flagged for recovery purposes. System Action: The system ends the command with
If the incomplete copy flag is set in the target volume a message.
record, LISTMSVI not only lists the standard Application Programmer Response: Before running
information for the volume but also highlights the the command, do one of the following:
volume report with a note that a copy operation failed
for the preceding volume. v Select a volume not cataloged in a VSAM catalog.
v For a copy operation failure for CONVERTV, run v Use the access method services DELETE command
CONVERTV again to complete the conversion to delete all VSAM data sets and data spaces on the
operation to the target volume that is flagged as an volume, provided the volume is active and
incomplete copy volume. Otherwise, run SCRATCHV mountable.
to scratch the target volume. The incomplete copy v Do not specify a new serial number through the
volume may even be used as the target volume in NEWSERIAL parameter in the command statement.
the RECOVERV command. In all cases, the empty
System Programmer Response: Enter the access
VTOC check or the security check for password
protected data sets is bypassed.
If the SCRATCHV command is run, the DD statement catalog.
is not required for the incompletely copied volume
and if provided, must specify deferred mounting. If the error recurs and the program is not in error,
If a VSAM catalog is on the volume and a DD
statement for the target volume must be provided and
must specify deferred mounting. If a VSAM catalog is
on the volume and a DD statement is provided for
to the problem.
the catalog, the DD statement must also specify
deferred mounting. Source: DFSMSdfp
If CONVERTV ends without indicating the status of Detecting Module: IDCAV01, IDCCN01, IDCCO01,
the conversion operation, run LISTMSVI to determine IDCRV01
whether the volume is flagged for recovery purposes.
If the incomplete copy flag is set in the target volume
record, LISTMSVI not only lists the standard
405
rename operation failed for the preceding volume and
IDC3070I ** text NOT UPDATED IN VOLUME
that the serial number is recorded in the volume label
LABEL [OF TO VOLUME]
of the volume.
Explanation: text is one of the following: v For a rename operation failure for MODIFYV, recover
SERIAL from a MODIFYV rename by:
OWNER
– Running ADDV to activate the volume if the
SERIAL, OWNER
volume is merely inactive and has no volume
serial mismatch condition.
Either the volume serial number or owner name or both
was not updated in the volume label as requested. A – Running ADDV both to activate the volume and
mismatch may exist between the cartridge labels and complete the rename operation if the volume is
the volume label for the mass storage volume. See the both inactive and has a volume serial mismatch
preceding message for further explanation of the condition
problem. – Running MODIFYV again to complete or retry the
rename operation if the volume to complete or
In the message text: retry the rename operation if the volume is active
and if a duplicate volume serial number is desired
OF TO VOLUME as a result of the rename.
Indicates which volume could not be updated
for those commands processing both a source
For the DD statement requirements, the proper
and target volume having the same volume
VOLUME and NEWSERIAL parameter values, and
serial number.
use of LISTMSVI, refer to the description above for
System Action: The system ends the command with an ADDV rename failure.
a message reflecting the severity of the error. v For a rename operation failure for STOREV, run
Application Programmer Response: Take one of the STOREV again or run MODIFYV to either backout or
following actions for the command that failed: retry the rename operation. For the DD statement
requirements, the proper VOLUME and NEWSERIAL
v For a rename operation failure for ADDV, run ADDV parameter values, and use of LISTMSVI, refer to the
to backout or retry the rename operation if the description above for an ADDV rename failure.
MODIFYV or STOREV to either backout or retry the System Programmer Response: If the error recurs
rename operation. If the ADDV, MODIFYV, or and the program is not in error, search problem
STOREV commands are run to recover from a reporting data bases for a fix for the problem. If no fix
rename failure, a DD statement for the volume is exists, contact the IBM Support Center. Provide the
required and must specify deferred mounting. The JCL, the SYSOUT output for the job, and all printed
values specified for the VOLUME and NEWSERIAL output and output data sets related to the problem.
parameters depend upon how the volume record is
Source: DFSMSdfp
recorded in the Inventory data set. If the volume
record is identified by the new volume serial number Detecting Module: IDCAV01, IDCCN01, IDCRV01
because the cartridge labels have been updated,
both the VOLUME and NEWSERIAL parameters
IDC3071I ** COPY NOT COMPLETED
must specify the new volume serial number.
Otherwise, specify the old volume serial number with Explanation: The copy operation failed. The target
the VOLUME parameter. Note that the security check volume is marked incomplete in the Inventory data set
for non-VSAM status and password protected data and will be reused when the command is run again.
sets is bypassed only if the NEWSERIAL parameter See the preceding message for further explanation of
specifies the same volume serial number as recorded the failure.
in the Inventory data set for the volume label. This System Action: The system ends the command with
allows the original volume serial number of a VSAM an error message.
volume to be restored if the volume is left partially
renamed. Application Programmer Response: Correct the
If ADDV, MODIFYV, or STOREV ends without error as identified by the preceding message. To run the
indicating the status of the rename operation, run command again, follow the recovery actions identified
LISTMSVI to determine whether the volume is for the recovery of space management.
flagged for recovery purposes. If the mismatch flag is System Programmer Response: If the error recurs
set in the volume record, LISTMSVI not only lists the and the program is not in error, search problem
standard information for the volume but also reporting data bases for a fix for the problem. If no fix
highlights the volume report with a note that a exists, contact the IBM Support Center. Provide the

Detecting Module: IDCAV01, IDCRV01
IDC3072I VOLUME ATTRIBUTES DO NOT AGREE output and output data sets related to the problem.
WITH GROUP ATTRIBUTES
Source: DFSMSdfp
Explanation: One or more of the specified volume
Detecting Module: IDCAV01, IDCCV01
attributes do not agree with the group level
specifications for all general-use volumes belonging to
the group. IDC3081I ** RECORD NOT RETRIEVED FROM
INVENTORY FOR COPY yyddd, NO. nnn
The possible attributes are as follows:
v bind/nobind Explanation: The record cannot be accessed in the
Inventory data set for the copy created on the indicated
date and assigned the copy sequence number for that
v dasderase/nodasderase date. See the preceding message for a further
v exclusive/shared explanation of the error.
v pagefault/nopagefault In the message text:
System Action: The system ends the command with yyddd The date in year and days.
an error message.
nnn The copy sequence number.
LISTMSVI command to list the group level System Action: The system ends the command with
specifications. Run the command again with volume a message unless additional copies are to be
attributes specified that correspond to the group that the processed.
volume is being assigned. Application Programmer Response: Correct the
System Programmer Response: If the error recurs error as indicated in the preceding message. Before
and the program is not in error, search problem running the command again, ensure that copy date and
reporting data bases for a fix for the problem. If no fix sequence number are specified correctly.
exists, contact the IBM Support Center. Provide the System Programmer Response: If the error recurs
JCL, the SYSOUT output for the job, and all printed and the program is not in error, search problem
output and output data sets related to the problem. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp exists, contact the IBM Support Center. Provide the
Detecting Module: IDCCN01, IDCRV01 output and output data sets related to the problem.
Source: DFSMSdfp
IDC3077I ** CART csn1 [csn2] NOT IN MSF FOR
VOL volser Detecting Module: IDCAV01, IDCRR01, IDCRV01
Explanation: The cartridges assigned to the specified

volume cannot be found in the Mass Storage Facility IDC3082I ** COPY NOT PERFORMED
(MSF). See the preceding message for additional Explanation: The copy operation could not be started
information. to the target volume. The target volume remains usable
In the message text: since the original data on the volume has not been
destroyed. See the preceding message for a further
csn1 explanation of the problem.
csn2 The cartridge serial numbers that identify the System Action: The system ends the command with
sequence one and sequence two cartridges an error message.
not in the MSF.
volser The volume serial number. error as identified in the preceding message. To run the
System Action: The system ends the command with command again, follow the recovery actions for space
a message. management.
Application Programmer Response: Correct the System Programmer Response: If the error recurs
problem as indicated in the preceding message. If the and the program is not in error, search problem
cartridges are outside the MSF, enter the cartridges reporting data bases for a fix for the problem. If no fix
again. Run the command again. exists, contact the IBM Support Center. Provide the
407
Source: DFSMSdfp attribute to READWRITE. If the volume to be relabeled
is inactive, use the ADDV command and specify the
Detecting Module: IDCAV01, IDCRR01, IDCRV01
READWRITE parameter.
IDC3089I A DUPLICATE VOLUME EXISTS WITH
SERIAL NO. volser
Explanation: More than one volume with the specified exists, contact the IBM Support Center. Provide the
volume serial number is recorded in the Inventory data JCL, the SYSOUT output for the job, and all printed
set. Duplicate volumes within the same Mass Storage output and output data sets related to the problem.
System occur when:
Source: DFSMSdfp
v The record is deleted from the Inventory data set for
an ejected volume, and before the volume is Detecting Module: IDCAV01, IDCEV01
reentered the serial number has been assigned to
another volume. IDC3092I FILE PARAMETER WITH DEFERRED
v The record for an ejected copy volume is deleted MOUNT REQUIRED
from the Inventory data set and the copy is
Explanation: The volume is recorded in the Inventory
reentered.
data set as:
v A volume is entered in the Mass Storage Facility from
v Incompletely created
another Mass Storage System.
v Incompletely copied
In the message text: v Having a volume serial number mismatch
These problems may cause dynamic allocation of the
System Action: The system ends the command with volume to encounter an error. Therefore, this command
an error message. requires a FILE parameter on the command statement.
The FILE parameter must specify the name of a JCL
DD statement which allocates a unit with deferred
LISTMSVI command to obtain the sequence one and
mounting to prevent allocation from mounting the
sequence two cartridge serial numbers of the correct
volume.
volume to be processed. Run the command again
specifying either cartridge serial number with the System Action: The system ends the command with
CARTRIDGE parameter so that the command can a message identifying the severity of the error.
select the correct volume.
System Programmer Response: If the error recurs command again with the FILE parameter specifying the
and the program is not in error, search problem name of a JCL DD statement which allocates a unit with
reporting data bases for a fix for the problem. If no fix deferred mounting.
Detecting Module: IDCCN01, IDCRV01
IDC3090I VOLUME volser CANNOT BE
Source: DFSMSdfp
RELABELED: READONLY ATTRIBUTE
IS ASSIGNED Detecting Module: IDCAV01, IDCMV01, IDCSR01
Explanation: The specified volume has the attribute
assigned which prohibits any changes to be made to IDC3094I VOLUME volser CANNOT BE
the volume. RENAMED; COPIES EXIST
In the message text: Explanation: The volume serial number cannot be
changed on the specified volume because there are
existing copies of the volume made through the COPYV
System Action: The system ends the command with command.
a message identifying the severity of the error.
Application Programmer Response: If the volume is
recorded as active in the Inventory data set, use the
MODIFYV command to change the READONLY

System Action: The system ends the command with
IDC3113I INVALID LEVEL PARAMETER
an error message.
Explanation: There is an asterisk (*) in the last
position of the LEVEL parameter. This is an error.
SCRATCHV command to scratch all existing copies of
the volume. Run the command again. If the copies must System Action: The system ends the command.
be saved, run the EJECTV command with the
NORECORD option for each copy volume, or run the
asterisk from the last position of the LEVEL parameter.
REMOVEVR command if the copy is already ejected.
This deletes the copy volume record information
recorded in the Inventory data set and permits the System Programmer Response: If the error recurs
original volume to be renamed. and the program is not in error, look at the messages in
If an ejected copy volume, not recorded in the Inventory
data set, is reentered in the Mass Storage Facility, the
copy will be recorded as a duplicate volume.
Source: DFSMSdfp
exists, contact the IBM Support Center. Provide the Detecting Module: IDCAV01, IDCCO01, IDCCV01,
JCL, the SYSOUT output for the job, and all printed IDCEC01, IDCEV01, IDCLV01, IDCMC01, IDCRL01
Source: DFSMSdfp IDC3114I VOLUME ser HAS DOWN LEVEL
SPACE
Detecting Module: IDCAV01, IDCMV01, IDCRV01,
IDCSR01 Explanation: The specified volume that belongs to a
group as a general use volume is being:
IDC3099I LENGTH OF CARTRIDGE SERIAL v Activated through the use of the ADDV command
NUMBER csn INVALID v Made a general use volume in a group through the
use of the MODIFY command.
Explanation: A cartridge serial number cannot be less
than eleven characters in length.
In either case, the base volume record in the Inventory
In the message text: data set indicates the volume has down level space. If
the MODIFY command is being used, the following
csn The cartridge serial number containing the
applies:
incorrect length.
v A JCL DD statement was not provided (or was
System Action: The system ends the command with provided but allocated to a volume different than the
a message unless additional cartridges have been volume being modified) and the attempt by the
specified for processing. MODIFY command dynamically to allocate the
Application Programmer Response: Specify an 11- volume failed.
or 12-character cartridge serial number. Run the
command again. If a cartridge serial number of 11 If the ADDV command is being used, the following
characters is specified, the command extends the applies:
cartridge serial number to 12 characters by inserting a v A JCL DD statement was not provided specifying
blank character in the fourth position from the left. If you deferred mount and the attempt by the ADDV
specify 12 characters, include the value in quotes command dynamically to allocate the volume failed.
because a blank is required as the fourth character.
and the program is not in error, search problem ser The volume serial number.
exists, contact the IBM Support Center. Provide the System Action: The system ends the MODIFYV or
JCL, the SYSOUT output for the job, and all printed ADDV command.
output and output data sets related to the problem. Application Programmer Response: Either provide
Source: DFSMSdfp the appropriate OS/VS JCL DD statement or allow the
MODIFYV or the ADDV command dynamically to
Detecting Module: IDCAV01, IDCCO01, IDCCV01, allocate the volume. Run the MODIFYV or ADDV
IDCEC01, IDCEV01, IDCLV01, IDCMC01, IDCRL01 command again. If dynamic allocation is failing,
determine the reason for this failure before running the
job again.
409
System Programmer Response: If the error recurs v BUFNI
and the program is not in error, look at the messages in v CONTROLINTERVALSIZE
v FREESPACE
exists, contact the IBM Support Center. Provide the v IMBED
JCL, the SYSOUT output for the job, and all printed v NOREPLICATE
output and output data sets related to the problem. v RECORDSIZE
Source: DFSMSdfp v REPLICATE
Detecting Module: IDCLD01 v SHAREOPTIONS
v STRNO
IDC3143I THE OUTPUT DATA SET CANNOT BE System Action: The system ends processing of this
THE SAME AS THE INPUT DATA SET command.
Explanation: The data set specified on the Application Programmer Response: Determine the
Outfile/Outdataset parameter is the same one that the catalog format to be defined. Remove the incorrect
system is exporting. parameters from the command or specify
ICFCATALOG. Run the job again.
System Action: The system ends processing.
source or target specifications. Run the job again.
and the program is not in error, look at the messages in exists, contact the IBM Support Center. Provide the JCL
the job log for more information. Search problem and the SYSOUT output for the job.
Source: DFSMSdfp
IDC3174I SPECIFIED MAXIMUM RECORD SIZE
Source: DFSMSdfp
LESS THAN REQUIRED MINIMUM
Detecting Module: IDCAV01, IDCMV01
Explanation: During the define of an ICF catalog, the
value specified for the data component maximum record
IDC3145I INVALID PORTABLE DATA SET size was found to be less than the minimum required
ORGANIZATION value, 4086 bytes. The maximum record size value
specified for the data component will override any value
Explanation: An attempt was made to export either a
specified for the catalog component.
virtual storage access method (VSAM) data set or a
user catalog, using a VSAM data set as the portable System Action: The system ends processing of this
data set. The portable data set can be only a sequential command.
access method file.
Application Programmer Response: Change the
System Action: The system ends the command. maximum record size specification. Run the job again. If
RECORDSIZE has been specified at both the catalog
and data component levels, ensure that the value
specification of portable data set to sequential
specified for the data component is at least the
organization.
minimum required value.
Source: DFSMSdfp
IDC3170I ICF CATALOG PARAMETER SPECIFIED the job log for more information. Search problem
FOR A VSAM CATALOG reporting data bases for a fix for the problem. If no fix
Explanation: During the define of a virtual storage and the SYSOUT output for the job.
access method (VSAM) user or master catalog, a
parameter applicable only to an ICF catalog was Source: DFSMSdfp
encountered. The parameter has been specified at the
catalog, data or index component levels. A VSAM
IDC3175I RESTRICTED VVDS NAME SPECIFIED
catalog is being defined because the VSAMCATALOG
FOR INVALID OBJECT TYPE
parameter has been specified or defaulted.
Explanation: During the define of an object, not a
The parameter is one of the following:
NONINDEXED (ESDS) cluster, the specified name was
v BUFND found to have the format of the restricted virtual storage

access method (VSAM) volume data set (VVDS) prefix, ranging from 1900 to 2155 or a two-digit number
‘SYS1.VVDS.V’. Define processing will disallow the use ranging from 00 to 99. The day must be a three-digit
of any name having this prefix if the name is not number ranging from 001 to 366. The expiration date
specified at the cluster component level of a DEFINE must not be less than the current date.
CLUSTER subcommand with the NONINDEXED
Source: DFSMSdfp
parameter specified. This prefix has a special use and
should only be specified to define a VVDS. Detecting Module: IDCAL01, IDCDE02
System Action: The system ends processing of this
command. IDC3183I UNABLE TO PROCESS SMS
CONSTRUCTS
data set name specified in the NAME parameter if a Explanation: An access method services DEFINE or
VVDS is not to be defined. If a VVDS is to be defined, IMPORT command specified storage management
specify the NONINDEXED parameter. subsystem (SMS) constructs, but during processing of
the command, SMS was not available to process any
constructs.
the job log for more information. Search problem System Action: The system ends processing of the
reporting data bases for a fix for the problem. If no fix command.
JCL. Application Programmer Response: If the data set
must reside on managed storage, ensure that the SMS
Source: DFSMSdfp is operational. Enter the command again.
If the data set can reside on non-SMS managed
IDC3176I VSAM VOLUME DATA SET VOLUME storage, enter the command again without specifying an
SERIAL NUMBER SPECIFICATION SMS construct.
ERROR
Source: DFSMSdfp
Explanation: During the define of a virtual storage
access method (VSAM) volume data set (VVDS), the Detecting Module: IDCAL01, IDCDE02
volume serial number specified by volser of the VVDS
name, ‘SYS1.VVDS.Vvolser’, did not match the volume IDC3184I DUPLICATE VOLUMES SPECIFIED FOR
serial number specified on the VOLUMES parameter. NON-KEYRANGE DEFINITION
Only the first volume serial number specified by
VOLUME is valid and is compared. Explanation: A DEFINE command for a data set
specified duplicate volume serials for a non-keyrange
System Action: The system ends processing of this request.
command.
Application Programmer Response: Check the command.
NAME and VOLUMES specifications. Change the
parameter in error. Run the job again. Application Programmer Response: Check the
VOLUMES parameter for duplicate volume serial
System Programmer Response: If the error recurs names. Either code keyranges or remove the duplicate
and the program is not in error, look at the messages in name.
exists, contact the IBM Support Center. Provide the JCL Detecting Module: IDCDE01, IDCMP01
Source: DFSMSdfp IDC3185I TOO MANY VOLUMES SPECIFIED
Explanation: A DEFINE command for a storage
IDC3179I INCORRECT SPECIFICATION OF management subsystem (SMS) managed data set
EXPIRATION DATE specified more than 59 volume serial numbers. 59 is the
Explanation: Using the TO parameter, an access maximum volume serials.
method services ALTER or DEFINE command specified System Action: The system ends processing of the
an incorrect expiration date. DEFINE command.
System Action: The application aborts with a return Application Programmer Response: Reduce the
code of 12. amount of volume serial numbers in the VOLUMES
Application Programmer Response: Respecify the parameter to 59 or less. Submit the command again.
TO parameter. The year must be a four-digit number Source: DFSMSdfp
411
IDC3186I INVALID VOLUME SERIAL SPECIFIED
Explanation: An attempt was made to define a
Source: DFSMSdfp
non-SMS-managed data set with a volume serial of ’*’.
A volume serial of ’*’ is only permitted for Detecting Module: IDCAL01
SMS-managed data sets.
System Action: The system fails the job. IDC3191I VSAM VOLUME DATA SET NAME OR
ITS GENERIC FORM NOT ALLOWED
User Response: Correct the volume serial and run the
job again. Explanation: During processing of an access method
services command, a name was specified and had the
Source: DFSMSdfp
restricted virtual storage access method (VSAM) volume
Detecting Module: IDCDE01 data set (VVDS) prefix or one of its generic forms. The
VVDS prefix, allowed for the following:
v ENTRYNAME for the ALTER command.
IDC3187I THE VOLCATALOG ENTRYNAME IS
v NEWNAME for the ALTER command.
INVALID
v INDATASET for the REPRO command.
Explanation: The entryname specified on an IDCAMS v MODEL for the DEFINE command.
DEFINE USERCATALOG command is not valid for a
volume catalog. The general volume catalog must be in The requested operation is not allowed for a VVDS.
the form:
xxxxxxxx.VOLCAT.VGENERAL command.
Where xxxxxxxx is either SYS1 or another high level Application Programmer Response: Do not use the
qualifier specified in the LOADxx member of restricted data set name prefix for the data sets. If a
SYS1.PARMLIB. The specific volume catalog must be in data set has been created with the restricted prefix, an
the form: alternate method must be found to complete the desired
operation.
xxxxxxxx.VOLCAT.Vx
Where xxxxxxxx is either SYS1 or another high level
qualifier specified in the LOADxx member of
SYS1.PARMLIB and x is either a number from 0-9 or an
uppercase alphabetic character A-Z.
System Action: The system stops processing the and. the SYSOUT output for the job.
command.
Source: DFSMSdfp
entryname.
Source: DFSMSdfp
IDC3192I LIBRARYNAME MUST REMAIN
Detecting Module: IDCDE01 “SHELF” WHILE LOCATION IS
“SHELF”
IDC3190I ‘keywd’ PARAMETER INVALID WITH Explanation: An attempt to alter LIBRARYNAME from
ENTRY TYPE SHELF was made while LOCATION was SHELF.
LOCATION and LIBRARYNAME must be consistent.
Explanation: The specified key word is improper for
the type of object being altered. This is usually a System Action: The system stops processing the
problem in distinguishing between cluster and command.
data/index component attributes.
System Programmer Response: Use the IDCAMS
In the message text: ALTER command to change LOCATION from SHELF to
LIBRARY when altering LIBRARYNAME.
keywd The keyword.
Source: DFSMSdfp
Application Programmer Response: Specify the
proper data set name. Run the command again.

IDC3193I dsname IS NOT A CANDIDATE FOR IDC3197I INVALID AUTHORIZATION TO ALTER
ROLLIN STORAGECLASS OR
MANAGEMENTCLASS
Explanation: An access method services ALTER
request specified a ROLLIN operation for a non-VSAM Explanation: An attempt was made by an
data set that is not in the deferred or rolled off state. unauthorized caller to alter either the STORAGECLASS
or MANAGEMENTCLASS name for the data set being
altered. The caller of application management
dsname subsystem (AMS) at the time of the ALTER must be
The data set name. It may be in the active running in an authorized program facility (APF)
state already, or it was not originally defined to authorized state.
the generation data group (GDG) base.
System Action: The system ends the command. ALTER command.
Application Programmer Response: Check whether Source: DFSMSdfp

the data set name is the intended candidate for a
ROLLIN operation.
Source: DFSMSdfp
IDC3198I SLOT VALUE CANNOT BE SPECIFIED
Detecting Module: IDCAL01 FOR A MANUAL LIBRARY
Explanation: NUMBERSLOTS and
IDC3194I SMS CONSTRUCT conname SPECIFIED NUMBEREMPTYSLOTS are not valid parameters for a
FOR NON-SMS MANAGED OBJECT manual library.
Explanation: An access method services ALTER System Action: The system stops processing the
command requested to change the storage command.
management subsystem (SMS) construct that is either
System Programmer Response: Either remove the
the storage or management class name. However, the
NUMBERSLOTS and/or NUMBEREMPTYSLOTS
specified object is not SMS managed, so the construct
parameters or specify LOGICALTYPE(AUTOMATED) on
cannot be changed.
the IDCAMS ALTER command.
Source: DFSMSdfp
conname
The construct name.
IDC3199I LIBRARYNAME OF “SHELF” IS NOT
ALTER command.
ALLOWED WITH A LOCATION OF
Application Programmer Response: Ensure that this “LIBRARY”
request is made against only SMS managed objects.
Explanation: The LIBRARYNAME of SHELF can only
Source: DFSMSdfp be specified when LOCATION is SHELF.
Detecting Module: IDCAL01 System Action: The system stops processing the
command.
IDC3195I OBJECT IS NOT SMS MANAGED System Programmer Response: Choose a

LIBRARYNAME other than SHELF or change the
Explanation: An access method services ALTER LOCATION parameter to LIBRARY.
command requested that a generation data set (GDS)
be rolled in, but the GDS is not managed by the storage Source: DFSMSdfp
management subsystem (SMS).
command.
IDC3200I TOO MANY POSITIONAL
Application Programmer Response: Remove the PARAMETERS AFTER ‘prm’
ROLLIN specification on the ALTER command.
Explanation: A parameter list has too many positional
Source: DFSMSdfp parameters specified.
Detecting Module: IDCAL01 In the message text:
prm The parameter list.
System Action: Processing skips to the end of the
413
command. The system resumes interpretation with the Detecting Module: IDCRI01
next command.
Application Programmer Response: Remove the IDC3203I ITEM ‘xxx’ DOES NOT ADHERE TO
excess parameters. Run the command again. RESTRICTIONS
System Programmer Response: If the error recurs Explanation: The specified constant does not meet
and the program is not in error, search problem the naming restrictions on its format. This is usually a
reporting data bases for a fix for the problem. If no fix problem in specifying data set names.
xxx The constant.
Source: DFSMSdfp
command. The system resumes interpretation with the
next command.
IDC3201I CONSTANT ‘xxx’ EXCEEDS LENGTH
Application Programmer Response: Check the data
LIMIT
restrictions for the parameter and correct the item. Run
Explanation: A constant is longer than the maximum the command again.
allowed by the parameter definition or by the
implementation.
xxx The constant that exceeded the maximum
length.
Source: DFSMSdfp
command. The system resumes interpretation with the Detecting Module: IDCRI01
next command.
Application Programmer Response: See the IDC3205I DELIMITER ‘xxx’ IS NOT PROPERLY
definition of the parameter value in question. Specify an PRECEDED BY A CONSTANT OR KEY
allowable value. Run the command again. WORD
System Programmer Response: If the error recurs Explanation: A delimiter has been specified where a
and the program is not in error, search problem subparameter list or data should have appeared. The
reporting data bases for a fix for the problem. If no fix delimiter is being used improperly. Parentheses are
exists, contact the IBM Support Center. Provide the likely to be improper or a positional parameter may be
SYSOUT output for the job. missing.
Detecting Module: IDCRI01 xxx The delimiter.
IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT command. The system resumes interpretation with the
COMMAND. CONDITION CODE IS 12. next command.
Explanation: Following the occurrence of an error in Application Programmer Response: Correct the
the current command, the remainder of the command is usage. Run the command again.
bypassed. An error message preceding this message in
the program listing will pinpoint the error.
System Action: The system performs no further reporting data bases for a fix for the problem. If no fix
syntax or semantic checking on the command. exists, contact the IBM Support Center. Provide the
related error. Run the job again. Source: DFSMSdfp
System Programmer Response: If the error recurs Detecting Module: IDCRI01
Source: DFSMSdfp

IDC3207I REMAINDER OF COMMAND INPUT
next command.
STREAM IGNORED
Explanation: An error has occurred that prohibits
usage. Run the command again.
further scanning of the input stream. There are
preceding error messages to explain the error. The System Programmer Response: If the error recurs
condition code (MAXCC) is always set to 16 when the and the program is not in error, search problem
remainder of the input stream is ignored. reporting data bases for a fix for the problem. If no fix
System Action: The system ignores the remainder of
the command input stream.
Source: DFSMSdfp
related error. Run the job again. Detecting Module: IDCRI01
and the program is not in error, search problem IDC3210I INVALID PARENTHESES FOR
reporting data bases for a fix for the problem. If no fix SPECIFYING REPEATED
exists, contact the IBM Support Center. Provide the SUBPARAMETER LIST
Explanation: Parentheses for delimiting repetitions of
Source: DFSMSdfp a repeated subparameter list are missing or unmatched.
Detecting Module: IDCRI01 System Action: Processing skips to the end of the
command. The system begins interpretation with the
next command.
IDC3208I LEFT PARENTHESIS MISSING
FOLLOWING KEY WORD ‘keywd’ Application Programmer Response: Correct the
Explanation: An opening parenthesis delimiting the
subparameter list or constants associated with the System Programmer Response: If the error recurs
keyword does not precede the keyword. and the program is not in error, search problem
keywd The keyword. SYSOUT output for the job.
System Action: Processing skips to the end of the Source: DFSMSdfp
next command.
IDC3211I KEY WORD ‘keywd’ IS IMPROPER
requirements of the parameter. Correct the usage. Run
the command again. Explanation: A keyword has been found which is not
recognized in its specified usage. It may be misspelled,
not applicable, or specified as a subparameter in the
wrong subparameter list.
keywd The keyword.
Source: DFSMSdfp
Detecting Module: IDCRI01 command. The system begins interpretation with the
next command.
IDC3209I RIGHT PARENTHESIS MISSING AFTER Application Programmer Response: Check the
‘xxx’ usage of the keyword and the parentheses.
Explanation: A right parenthesis is missing which System Programmer Response: If the error recurs
should delimit the end of one or more constants. Too and the program is not in error, search problem
many items might be specified. reporting data bases for a fix for the problem. If no fix
xxx The item before which the parenthesis is
Source: DFSMSdfp
missing.
415
IDC3212I INVALID LEFT PARENTHESIS AFTER
‘prm’
Explanation: A left parenthesis appears to delimit a exists, contact the IBM Support Center. Provide the
positional parameter. However, the positional parameter SYSOUT output for the job.
is not a constant or list of constants, so no parentheses
Source: DFSMSdfp
are allowed.
prm The positional parameter.
IDC3216I ABOVE TEXT BYPASSED UNTIL NEXT
System Action: Processing skips to the end of the COMMAND
Explanation: Following the occurrence of an error in
next command.
the current command, the remainder of the command is
Application Programmer Response: Correct the bypassed. An error message preceding this message
usage. Run the job again. will pinpoint the error. The command was being
scanned for syntax checking purposes only when the
error was found.
reporting data bases for a fix for the problem. If no fix System Action: The system performs no further
exists, contact the IBM Support Center. Provide the syntax or semantic checking on the command. The
SYSOUT output for the job. system condition code is not affected.
related error. Run the job again.
IDC3213I KEY WORD ‘keywd’ APPEARS TOO
OFTEN
Explanation: A keyword has been coded more than SYSOUT output for the job.
once in the same parameter list or subparameter list.
Source: DFSMSdfp
keywd The keyword.
System Action: Processing skips to the end of the IDC3217I PASSWORD IMPROPER AFTER ‘prm’
Explanation: A password is found following a data
next command.
item that does not allow a password.
redundant keyword. Run the command again.
prm The data item that does not allow a password.
and the program is not in error, search problem System Action: Processing skips to the end of the
reporting data bases for a fix for the problem. If no fix command. The system begins interpretation with the
exists, contact the IBM Support Center. Provide the next command.
Source: DFSMSdfp improper password. Run the command again.
Detecting Module: IDCRI01 System Programmer Response: If the error recurs
IDC3214I HEX OR BINARY CONSTANT
SPECIFIED IMPROPERLY
Explanation: A hexadecimal or binary constant is not
Source: DFSMSdfp
in its proper form.
next command.

IDC3218I TOO MANY REPEATED
SUBPARAMETER LISTS APPEAR System Programmer Response: If the error recurs
Explanation: More repeated subparameter lists are
coded than are allowed.
System Action: Processing skips to the end of the SYSOUT output for the job.
Source: DFSMSdfp
next command.
parameter description to see how many repetitions are
allowed. Correct the usage. Run the job again. IDC3221I CONSTANT ‘xxx’ NOT WITHIN VALUE
RANGE
and the program is not in error, search problem Explanation: A constant is of a value not within the
reporting data bases for a fix for the problem. If no fix range of values allowed for this parameter.
SYSOUT output for the job. In the message text:
Source: DFSMSdfp xxx The constant.
Detecting Module: IDCRI01 System Action: Processing skips to the end of the
next command.
IDC3219I VERB NAME ‘verb’ UNKNOWN
Explanation: The specified verb name is not known to usage. Run the command again.
the system.
In the message text: and the program is not in error, search problem
verb The verb name.
System Action: Processing skips to the end of the SYSOUT output for the job.
Source: DFSMSdfp
next command.
improper verb name. Run the command again.
IDC3223I TOO MANY CONSTANTS IN LIST
BEGINNING AT ‘xxx’
reporting data bases for a fix for the problem. If no fix Explanation: Too many constants have been coded in
exists, contact the IBM Support Center. Provide the a list.
Source: DFSMSdfp
xxx The constant that begins the list.
IDC3220I IMPROPER NUMERIC DIGIT FOUND IN next command.
‘prm’
Explanation: An incorrect numeric digit has been parameter definition to see how many constants appear
found. A decimal number may use only 0-9, a in the list. Correct the usage. Run the job again.
hexadecimal number may use only 0-9 and A-F, and a
binary number may use only digits 0 and 1. System Programmer Response: If the error recurs
prm The parameter in which the incorrect digit was
found.
Source: DFSMSdfp
command. The system begins interpretation with the Detecting Module: IDCRI01
next command.
417
IDC3225I REQUIRED (SUB)PARAMETER OF ‘prm’
IS MISSING
Explanation: The system issues this message for one problem and the control statements for the job.
of the following reasons:
Source: DFSMSdfp
v A parameter required by the command is missing.
v For Cache-DASD the specified parameter is required.
In the message text: IDC3241I INVALID ‘prm’ NAME-xxx

prm The required parameter. Explanation: A DSNAME or DDNAME does not
adhere to naming restrictions.
command. The system begins interpretation with the In the message text:
next command.
prm The specified parameter.
Application Programmer Response: Add the missing
xxx The first sixty-four characters of the name, if
parameter. Run the job again.
more than sixty-four characters were entered.
System Action: The system prompts the caller for a
valid name. See message IDC3249I.
exists, contact the IBM Support Center. Provide the Application Programmer Response: Enter a valid
SYSOUT output for the job. name.
IDC3226I INCONSISTENT PARAMETERS printed output and output data sets related to the
INVOLVING prm problem and the control statements for the job.
Explanation: A user issued an IDCAMS command Source: DFSMSdfp
that has conflicting or inconsistent parameters.
prm The conflicting or inconsistent parameter. IDC3242I ‘prm’ VALUE HAS INVALID LENGTH-xxx
System Action: Processing skips to the end of the Explanation: A constant is either too long or has a
command; interpretation begins at the next command. null length.
Application Programmer Response: Correct the In the message text:
error. Issue the command again.
Source: DFSMSdfp
xxx The first sixty-three characters of the constant,
Detecting Module: IDCRI01 if more than sixty-three were entered.
System Action: The system prompts the caller for a
IDC3240I ‘prm’ VALUE OF ‘nnn’ OUT OF RANGE valid constant. See message IDC3249I.
Explanation: A number is either larger or smaller than Application Programmer Response: Enter a valid
is allowed for the specified parameter. constant.
nnn Represents the first ten digits of the number. exists, contact the IBM Support Center. Provide all
System Action: The system prompts the caller for a problem and the control statements for the job.
valid number. See message IDC3249I.
Source: DFSMSdfp
Application Programmer Response: Enter a number
within the allowable value range. Detecting Module: IDCRI04


IDC3243I ‘prm’ LIST TOO LONG BEGINNING AT IDC3246I ENTER REPLY NUMBER OF
xxx PARAMETER TO BE RETAINED
Explanation: A list of nonnumeric constants or Explanation: This message follows message
subparameter lists has too many elements. IDC3244I and allows the operator to specify which
parameter to retain.
System Action: The system waits for the caller to
reply.
xxx The first sixty-three characters of the constant,
Application Programmer Response: Enter ‘1’ to
if more than sixty-three characters were
keep the first parameter listed in the preceding
entered.
message. Enter ‘2’ to keep the second parameter.
System Action: The system prompts the caller to
Source: DFSMSdfp
indicate whether the excess list elements may be
ignored. See message IDC3250I. Detecting Module: IDCRI04
Application Programmer Response: Enter ‘OK’ to
allow the excess elements to be ignored. Any other IDC3247I ENTER SUBFIELD OF KEY WORD
response ends the command. ‘keywd’
System Programmer Response: If the error recurs Explanation: A keyword parameter is missing. It is
and the program is not in error, search problem required by the command or by some other parameter
reporting data bases for a fix for the problem. If no fix that has been coded.
problem and the control statements for the job. keywd The keyword.
Source: DFSMSdfp System Action: The system waits for the caller to
reply. Either a constant or a subparameter set is
required.
Application Programmer Response: Enter the
IDC3244I ‘prm1’ (REPLY‘1’) AND prm2 (REPLY ‘2’)
requested subfield data.
ARE IN CONFLICT
Explanation: Two parameters have been coded that
conflict with each other.
In the message text: exists, contact the IBM Support Center. Provide all
prm1
problem and the control statements for the job.
prm2 The conflicting parameters.
Source: DFSMSdfp
indicate which of the two parameters should be kept.
See message IDC3246I.
IDC3248I ‘prm’ LIST TOO LONG BEGINNING AT
Application Programmer Response: Enter ‘1’ to
nnn
keep the first parameter. Enter ‘2’ to keep the second
parameter. Explanation: A list of numbers contains too many
elements.
and the program is not in error, search problem In the message text:
printed output and output data sets related to the nnn The first ten digits of the number.
problem and the control statements for the job.
Source: DFSMSdfp indicate whether the excess elements can be ignored.
See message IDC3250I.
Application Programmer Response: Reply ‘OK’ to
allow the excess elements to be ignored. Any other
response ends the command.
419
IDC3253I MISSING SUBFIELD OF KEY WORD
keywd
problem and the control statements for the job. Explanation: A keyword subparameter is missing, but
the system is not able to prompt the Time Sharing
Source: DFSMSdfp
Option/Extensions (TSO/E) user for it because a
Detecting Module: IDCRI04 PROFILE NOPROMPT command has been issued.
IDC3249I REENTER
keywd The keyword.
Explanation: This prompting message follows
messages that identify incorrect constants: IDC3240I,
command.
IDC3241I, and IDC3242I.
Operator Response: The TSO/E user should reenter
System Action: The system requests the caller to
the command with the proper keyword.
enter a valid constant.
Application Programmer Response: Enter a valid
constant.
Source: DFSMSdfp exists, contact the IBM Support Center. Provide all
Detecting Module: IDCRI04 problem and the control statements for the job.
Source: DFSMSdfp
IDC3250I REPLY ‘OK’ TO IGNORE EXCESS AND
CONTINUE Detecting Module: IDCRI04
Explanation: This prompting message follows

message IDC3243I or IDC3248I which indicate too IDC3300I ERROR OPENING {dsname|ddname}
many elements have been coded in a list.
Explanation: An error was detected attempting to
System Action: The system prompts the caller to open the data set name. See associated message for
indicate whether the excess elements can be ignored. explanation.
Application Programmer Response: If the response In the message text:
is ‘OK’ or ‘OK’, ‘OK’, ‘OK’ the excess elements are
dsname
ignored. Any other response causes the command to
The data set name.
end.
ddname
Source: DFSMSdfp
The ddname. Appears only when the data set
Detecting Module: IDCRI04 name is not available.
IDC3251I FOR SUBFIELD REPETITION nnn
Explanation: This message prefaces any other error associated message.
message when the parameter involved in the error is
within a repeated subparameter list. It is used to help
identify the problem.
nnn The subparameter list repetition. and the SYSOUT output for the job.
System Action: The system continues processing. Source: DFSMSdfp
Application Programmer Response: Examine the Detecting Module: IDCRI04
indicated subparameter list repetition.
Source: DFSMSdfp IDC3301I ERROR CLOSING dsname
Detecting Module: IDCRI04 Explanation: An error was detected while attempting
to close the data set. See the associated message in
the program listing for an explanation.

dsname
IDC3304I ** JCL STATEMENT MISSING
The data set name.
Explanation: The DD statement named in a FILE,
INFILE, or OUTFILE parameter cannot be found. If the
Application Programmer Response: Check the job or Time Sharing Option/Extensions (TSO/E) session
associated message. contains a delete request that causes the system to
invoke dynamic deallocation, the DD statement for the
System Programmer Response: If the error recurs deleted data set is not accessible for the remainder of
and the program is not in error, look at the messages in the job or session.
reporting data bases for a fix for the problem. If no fix System Action: The system ends processing of the
exists, contact the IBM Support Center. Provide the JCL command.
Application Programmer Response: Check ddnames
Source: DFSMSdfp for incorrect spelling or check for missing DD
statements. Correct the error. Run the job again.
Detecting Module: IDCIO02, IDCIO05
IDC3302I ACTION ERROR ON dsname the job log for more information. Search problem
Explanation: An error was detected while attempting reporting data bases for a fix for the problem. If no fix
to access the data set. See the associated message in exists, contact the IBM Support Center. Provide the JCL
the program listing for explanation. and the SYSOUT output for the job.
dsname Detecting Module: IDCIO02

The data set name.
System Action: The system ends the command. IDC3305I ** CANNOT BE OPENED FOR OUTPUT
Application Programmer Response: Check the Explanation: The processor cannot open this
associated message. non-virtual storage access method (VSAM) data set for
output. Specifically, indexed sequential access method
System Programmer Response: If the error recurs (ISAM) data sets may not be output data sets.
the job log for more information. System Action: The system ends processing of the
command.
Source: DFSMSdfp
Detecting Module: IDCIO02 keyword value to specify either a VSAM or SAM data
set.
IDC3303I ** CANNOT OPEN FOR UPDATE System Programmer Response: If the error recurs
Explanation: Only virtual storage access method and the program is not in error, look at the messages in
(VSAM) data sets may be opened for update mode. the job log for more information. Search problem
System Action: The system does not open the data exists, contact the IBM Support Center. Provide the JCL
set. The system ends the command. and the SYSOUT output for the job.
Application Programmer Response: Change the DD Source: DFSMSdfp
statement to specify a VSAM data set.
the job log for more information. Search problem IDC3306I ** PS PROCESSING INVALID FOR
reporting data bases for a fix for the problem. If no fix KEYED DATA SET
exists, contact the IBM Support Center. Provide the JCL Explanation: Physical sequential access is not
and the SYSOUT output for the job. possible for the data set. Indexed sequential access
Source: DFSMSdfp method (ISAM) data sets may not be processed other
than sequentially by key.
Detecting Module: IDCIO01, IDCIO03, IDCRS06
command.
JCL statement to specify a virtual storage access
421
method (VSAM) data set, or correct the usage of the exists, contact the IBM Support Center. Provide the JCL
data set. and the SYSOUT output for the job.
exists, contact the IBM Support Center. Provide the JCL IDC3309I ** RECORD xxx NOT WRITTEN.
and the SYSOUT output for the job. LENGTH INVALID.
Source: DFSMSdfp Explanation: The specified record was not written for
one of the following reasons:
v The record length was greater than the LRECL of the
output data set (logical processing).
IDC3307I ** DATA SET CANNOT BE OPENED
v The record length was less than the LRECL of the
FOR KEYED PROCESSING
output data set and output RECFM=FIXED, or output
Explanation: Only indexed virtual storage access is a relative record data set.
method (VSAM) and indexed sequential access method v The control-interval length to be written did not equal
(ISAM) data sets can be opened for keyed processing. the control interval size for the output data set.
System Action: The system ends processing of the v The record length was less than the minimum output
command. LRECL allowed (input LRECL + 4) when RECFM=F
and output is to a subsystem device.
JCL statement to specify a keyed data set or correct the
usage of the data set in the command. Run the job
again. xxx The first five bytes of the record in
hexadecimal format.
and the program is not in error, look at the messages in System Action: The system continues processing
the job log for more information. Search problem until four such errors occur, in which case no more
reporting data bases for a fix for the problem. If no fix records are written to the data set.
and the SYSOUT output for the job. Application Programmer Response: Redefine the
output data set with the correct LRECL or control
Source: DFSMSdfp interval size.
Detecting Module: IDCIO02 System Programmer Response: If the error recurs
IDC3308I ** DUPLICATE RECORD xxx
Explanation: The output data set of a REPRO exists, contact the IBM Support Center. Provide the JCL
command already contains a record with the same key and the SYSOUT output for the job.
or record number.
Source: DFSMSdfp
xxx For an indexed data set, the first five bytes of
the duplicate key, in hexadecimal format.
IDC3310I ** KEY SUPPLIED IS LONGER THAN
For a relative record data set, the relative KEY LENGTH OF DATA SET
record number (in decimal) of the duplicate
Explanation: The key supplied for positioning was
record.
longer than the key length of the data set. For example,
System Action: The system does not write the record. the key specified by FROMKEY is longer than the key
The system continues processing with the next record, length of the data set.
unless this is a copy catalog and a duplicate record is
encountered or there has been a total of four errors.
command.
The system ends in either case. For example, if a
duplicate record is encountered while REPRO is Application Programmer Response: Specify the
copying a catalog, the system ends processing. correct key on the command. Run the job again.

exists, contact the IBM Support Center. Provide the JCL System Programmer Response: If the error recurs
and the SYSOUT output for the job. and the program is not in error, look at the messages in
Source: DFSMSdfp
Detecting Module: IDCIO01 exists, contact the IBM Support Center. Provide the JCL
IDC3311I ** TYPE OF POSITIONING NOT Source: DFSMSdfp
SUPPORTED
Explanation: Positioning is valid only for virtual
storage access method (VSAM) and indexed sequential
IDC3314I RECORD xxx OUT OF SEQUENCE
access method (ISAM) data sets.
Explanation: The key of the record to be written is
less than or equal to the key of the last record written.
command.
Application Programmer Response: Respecify the
JCL statement defining a VSAM or ISAM data set or xxx The first five bytes in hexadecimal format of
remove the positioning parameter. Run the job again. the key of the record that is out of sequence.
System Programmer Response: If the error recurs System Action: If the output data set is a virtual
and the program is not in error, look at the messages in storage access method (VSAM) data set, the system
the job log for more information. Search problem ends processing of the command after four errors. If the
reporting data bases for a fix for the problem. If no fix output data set is a NONVSAM data set, the system
exists, contact the IBM Support Center. Provide the JCL continues processing the command. During an
and the SYSOUT output for the job. EXPORT, the system ends processing of the command
after the first error.
Source: DFSMSdfp
Application Programmer Response: Rearrange the
records to be written so that they are in ascending key
sequence. The record can be written to the data set
IDC3312I ** SYSTEM UNABLE TO OPEN using skip sequential processing. Run the job again and
the output data set will be opened for skip sequential
Explanation: DCBOFLG was not set after an OPEN processing (because data already exists in the data set)
request. and records that were out of sequence will be written.
System Action: The system ends the command. System Programmer Response: If the error recurs
Application Programmer Response: In the and the program is not in error, look at the messages in
description of the OPEN macro instruction, check for an the job log for more information. Search problem
explanation of failure to set the DCBOFLG field in a reporting data bases for a fix for the problem. If no fix
non-virtual storage access method (VSAM) data control exists, contact the IBM Support Center. Provide the JCL
block (DCB) after an OPEN request. and the SYSOUT output for the job.

and the program is not in error, look at the messages in Detecting Module: IDCIO01, IDCIO05
exists, contact the IBM Support Center. Provide the JCL IDC3315I ** RECORD SIZE GREATER THAN
and the SYSOUT output for the job. 32760 NOT SUPPORTED
Source: DFSMSdfp Explanation: Access method services cannot process
a non-virtual storage access method (VSAM) data set
Detecting Module: IDCIO03 with a logical record length greater than 32,760 bytes.
The DCB LRECL parameter was specified with a value
IDC3313I synadaf-message greater than 32,760. This value was obtained either
from the DD statement, the format-1 data set control
Explanation: An I/O error occurred for a non-virtual block (DSCB) or the data set label (for a tape data set)
storage access method (VSAM) data set. The for a non-VSAM data set, or it was generated by the
SYNADAF message is written. EXPORT or EXPORTRA command for a portable data
System Action: The system ends the command. set. The logical record length for the EXPORT or
EXPORTRA command is based on the maximum record
Application Programmer Response: Check the size of the VSAM data set being exported plus system
explanation in the SYNADAF message. Correct the overhead. The maximum VSAM record size that can be
error. Submit the job again. handled by EXPORT is:
423
v 32,752 for relative record data sets
IDC3317I ** PERMANENT I/O ERROR
v 32,756 for all other types of VSAM data sets
Explanation: An I/O error was detected performing an
The maximum record size that can be handled by I/O operation on the data set named in the preceding
EXPORTRA is: message.
v 32,748 for relative record data sets
v 32,752 for all other types of VSAM data sets
command.
Application Programmer Response: Check the job
command.
control statement to ensure that the data set was
Application Programmer Response: Do one of the correctly defined. If it was correctly defined, a hardware
following: I/O error was encountered. The data set must be
v Change the DD statement to specify a DCB LRECL created in a new location.
parameter of less than 32,760 bytes or to refer to a System Programmer Response: If the error recurs
non-VSAM data set whose logical record length (as and the program is not in error, look at the messages in
specified in its format-1 DSCB or data set label) is the job log for more information. Search problem
less than 32,760 bytes reporting data bases for a fix for the problem. If no fix
v Change the VSAM maximum logical record size to exists, contact the IBM Support Center. Provide the JCL
conform to the restrictions given above. In order to and the SYSOUT output for the job.
use the second alternative, redefine and reload the
Source: DFSMSdfp
VSAM data set.
entries and information about objects defined in the IDC3318I ** INVALID DATA SET SPECIFICATION
catalog.
Explanation: A STOW was issued against the data
If the error recurs and the program is not in error, look set, but the specified data control block (DCB) is not
at the messages in the job log for more information. open or is opened incorrectly.
Center. Provide the JCL and the SYSOUT output for the System Programmer Response: If the error recurs
job. and the program is not in error, look at the messages in
Source: DFSMSdfp
Detecting Module: IDCIO01 exists, contact the IBM Support Center. Provide the JCL
IDC3316I ** DATA SET IS NOT VSAM CATALOG Source: DFSMSdfp
Explanation: A request is for a virtual storage access Detecting Module: IDCIO01, IDCIO02, IDCIO03
method (VSAM) catalog to be opened and the data set
is not a VSAM catalog.
IDC3321I ** OPEN/CLOSE/EOV ABEND EXIT
System Action: The system ends the command. TAKEN
Application Programmer Response: Correct the Explanation: The OPEN/CLOSE/EOV SVC routines
catalog keyword to specify a user catalog. Run the job detected an error, and an ABEND message has been
again. written to the system output data set.
System Programmer Response: If the error recurs System Action: The system ends the command.
write-to-programmer (WTP) message written by the
OPEN/CLOSE routine. Correct the error. Submit the job
again.
Source: DFSMSdfp
Detecting Module: IDCIO02 the job log for more information. Search problem
Source: DFSMSdfp

Detecting Module: IDCIO02 Source: DFSMSdfp
IDC3322I ** DATA SET ORGANIZATION IS NOT
VSAM
IDC3327I ** DUPLICATE RECORD IN UPGRADE
Explanation: A request for an existing data set SET - BASE RECORD xxx
indicated that the data set was virtual storage access
Explanation: During a REPRO operation an attempt
method (VSAM). The data set was in fact not VSAM.
has been made to add a record to the output base
System Action: The system ends the command. cluster. However, a duplicate record in the upgrade set
has been encountered when upgrading an alternate
Application Programmer Response: Correct the data
index with the UNIQUEKEY attribute over the output
set name or type. Run the job again.
data set.
the job log for more information. Search problem xxx If the base cluster is a key-sequenced data set,
reporting data bases for a fix for the problem. If no fix the first five bytes of the prime key expressed
exists, contact the IBM Support Center. Provide the JCL in hexadecimal.
If the base cluster is an entry-sequenced data
Source: DFSMSdfp set, the first five bytes of the record expressed
in hexadecimal.
System Action: The system does not write the record
into the base cluster. The system continues processing
IDC3325I ** INCORRECT BLOCKSIZE SPECIFIED
until four action errors occur, at which point the system
FOR IMPORTRA
ends processing.
Explanation: The data set cannot be opened due to
an incorrect block size in the INFILE parameter.
UNIQUEKEY attribute was correctly specified, the base
System Action: The system ends processing of the cluster record being added is in error and must be
IMPORTRA command. corrected. If the UNIQUEKEY attribute was incorrectly
specified, it may be changed to NONUNIQUEKEY using
Application Programmer Response: Change the the ALTER command. Run the job again using just
block size in the INFILE parameter to that used in the those records that were in error as input.
EXPORTRA command. Run the job again.
Detecting Module: IDCIO01 the job log for more information. Search problem
IDC3326I ** REPLACE INVALID FOR OUTPUT and the SYSOUT output for the job.
THROUGH A PATH
Source: DFSMSdfp
Explanation: The caller has specified the REPLACE
parameter in a REPRO command when the output data Detecting Module: IDCIO02
set is a path. REPLACE processing is not allowed for
an output path. IDC3330I ** xxx NOT FOUND
System Action: The system ends processing of this Explanation: The indicated entry does not exist in the
command. directory.
Application Programmer Response: If the input does In the message text:
not contain any records duplicating prime keys (and
alternate keys of any upgrade set alternate index having xxx The entry not found.
the UNIQUEKEY attribute) in the output, the caller may
still run REPRO by simply removing the REPLACE
parameter. Application Programmer Response: Correct the
entry name. Run the job again.
and the program is not in error, look at the messages in System Programmer Response: If the error recurs
the job log for more information. Search problem and the program is not in error, look at the messages in
reporting data bases for a fix for the problem. If no fix the job log for more information. Search problem
exists, contact the IBM Support Center. Provide the JCL reporting data bases for a fix for the problem. If no fix
425
exists, contact the IBM Support Center. Provide the If it is not empty, delete whatever is defined in it, then
SYSOUT output for the job. delete it, and redefine it.
Source: DFSMSdfp Enter the REPRO command again.
Detecting Module: IDCIO01 System Programmer Response: If the error recurs
IDC3331I ** mem ALREADY EXISTS
Source: DFSMSdfp
Explanation: A member with the new member name
already exists in the PDS directory. Detecting Module: IDCIO02, IDCIO03, IDCSA02
IDC3334I ** INVALID CI NUMBER
mem The member.
Explanation: The REPRO command to copy a source
catalog into a target catalog failed because there was
Application Programmer Response: Specify a an incorrect control-interval number in an entry in the
different new name. Run the job again. source catalog.
System Programmer Response: If the error recurs System Action: The system does not carry out the
and the program is not in error, look at the messages in copy operation. The system ends the command.
LISTCAT command to list all of the entries in the source
catalog. Examine messages from LISTCAT to determine
the entry that contains the incorrect control-interval
Source: DFSMSdfp number.
Detecting Module: IDCIO03 Use the DELETE command to delete that entry. If the
DELETE fails, use the PRINT command to get a
dump-format listing of the source catalog to identify the
IDC3332I ** INSUFFICIENT MAIN STORAGE catalog record that contains the incorrect control-interval
Explanation: There is not sufficient main storage number and to determine what the control-interval
allocated. number should be. Contact the IBM Support Center.
System Action: The system ends the job. System Programmer Response: If the error recurs
Application Programmer Response: Specify a larger the job log for more information. Search problem
region size. Run the job again. reporting data bases for a fix for the problem. If no fix
and the program is not in error, look at the messages in and the SYSOUT output for the job.
exists, contact the IBM Support Center. Provide the JCL Detecting Module: IDCIO01
Source: DFSMSdfp IDC3335I {ENCIPHER|DECIPHER} ERROR
Detecting Module: IDCIO03 Explanation: An error was detected while attempting

to use a Programmed Cryptographic Facility service to
encipher or decipher data. See the accompanying
IDC3333I ** CATALOG IS NOT EMPTY message for an explanation of the error.
Explanation: The REPRO command to copy a source System Action: The system ends the command.
catalog into a target catalog failed because the target
catalog was not empty or was empty but had been Application Programmer Response: Respond to the
used. That is, it has entries defined in it, then deleted problem described by the accompanying message.
from it. System Programmer Response: If the error recurs
System Action: The system does not carry out the and the program is not in error, look at the messages in
copy operation. The system ends the command. the job log for more information. Search problem
Application Programmer Response: Ensure that the exists, contact the IBM Support Center. Provide the JCL
correct target catalog has been specified. If it has, use and the SYSOUT output for the job.
the LISTCAT command to determine whether the
catalog is empty. If it is empty, delete it and redefine it. Source: DFSMSdfp

Detecting Module: IDCIO01 System Action: The system ends the command.
IDC3336I ** text RETURN CODE IS return-code and the program is not in error, look at the messages in
CIPHER
EMK
GENKEY
RETKEY Source: DFSMSdfp
The indicated Programmed Cryptographic Facility (PCF)
service returned a nonzero return code. PCF and
cryptographic unit support program (CUSP) macros will IDC3337I TARGET DATA SET IS NOT EMPTY
receive identical error return codes if they run on FOR {ENCIPHER|DECIPHER}
integrated cryptographic service facility (ICSF)/MVS or
Explanation: The target virtual storage access method
on PCF/CUSP, with one exception. If a key is installed
(VSAM) entry-sequenced data set (ESDS) for the
in the cryptographic key data set (CKDS) with the
ENCIPHER or DECIPHER operation was not empty.
correct label but an incorrect key type, an attempt to
use that key by RETKEY or GENKEY will result in a System Action: The system ends the command.
return code of 8 from PCF/CUSP, indicating that the key
was not of the correct type. ICSF will issue a return Application Programmer Response: Change the DD
code of 12, indicating the key could not be found. statement for the target data set pointed to by the
Installations must ensure that PCF/CUSP LOCAL or OUTFILE parameter or the data set name specified by
CROSS 1 keys are installed on the ICSF CKDS as the OUTDATASET parameter to specify an empty
EXPORTER keys, and that REMOTE and CROSS 2 VSAM ESDS, or, if the VSAM ESDS was defined with
keys are installed as IMPORTER keys. the REUSE option, specify REUSE in the command.
text The text of the message.
return-code The return code, as follows: exists, contact the IBM Support Center. Provide the JCL
For CIPHER/EMK:
Source: DFSMSdfp
Code Explanation
4 PCF was not initialized.
12 The system encountered an
IDC3338I INVALID SOURCE DATA SET FOR
error that forced an abnormal
DECIPHER
end.
Explanation: The source data set was not enciphered
For GENKEY/RETKEY: by a REPRO ENCIPHER command, and therefore
cannot be deciphered.
Code Explanation
4 PCF was not active.
Application Programmer Response: Change the DD
8 The key type was incorrect. statement pointed to by the INFILE parameter or the
12 The key name was not found data set name specified by the INDATASET parameter
in the CKDS. to specify a data set that was produced by a REPRO
ENCIPHER operation.
16 An installation exit caused
the request to fail. System Programmer Response: If the error recurs
24 An error occurred in the the job log for more information. Search problem
installation exit routine. reporting data bases for a fix for the problem. If no fix
28 The authorization check exists, contact the IBM Support Center. Provide the JCL
failed. and the SYSOUT output for the job.
32 The key has incorrect parity. Source: DFSMSdfp
36 The system encountered an Detecting Module: IDCIO01

error that forced an abnormal
end.
427
IDC3340I SYSTEMKEYNAME text
Source: DFSMSdfp
ENCIPHERED SYSTEMDATAKEY Detecting Module: IDCIO01
NOT FOUND IN SOURCE DATA SET
IDC3350I synad[SYNAD]message[from VSAM]

The caller did not specify the key name or enciphered
data encrypting key to be used to decipher the data. Explanation: An I/O error occurred for a virtual
REPRO command processing tried to obtain the needed storage access method (VSAM) data set. The message
information from the header of the source data set, but text, format, and explanation of VSAM I/O errors are
the information was not stored in the header when the provided in OS/390 DFSMS Macro Instructions for Data
data set was enciphered by the REPRO ENCIPHER Sets.
command.
synad The synad data.
needed key name or enciphered data encrypting key in message
the command using the SYSTEMKEYNAME or The message text.
SYSTEMDATAKEY parameter. System Action: If possible, the system continues
System Programmer Response: If the error recurs processing.
and the program is not in error, look at the messages in Application Programmer Response: Check the
the job log for more information. Search problem explanation of the error. Correct the error. Submit the
reporting data bases for a fix for the problem. If no fix job again.
and the SYSOUT output for the job. System Programmer Response: If the error recurs
Source: DFSMSdfp the job log for more information. Search problem
Detecting Module: IDCIO01 reporting data bases for a fix for the problem. If no fix
IDC3341I DECIPHER KEY IS INVALID
Source: DFSMSdfp
Explanation: One of the keys supplied by the caller to
decipher the data is not the same as the key that was Detecting Module: IDCIO01
used to encipher the data. If the SYSTEMKEY
parameter was specified, then one of the following is IDC3351I ** VSAM {OPEN|CLOSE|I/O} RETURN
incorrect: CODE IS return-code
v The secondary file key name specified by the {RPLFDBWD=nnnnnnnn}
SYSTEMKEYNAME parameter.
Explanation: An error was encountered during virtual
v The secondary file key name contained in the header. storage access method (VSAM) open, close, or action
v The enciphered data encrypting key specified by the request processing, as indicated in the text of the
SYSTEMDATAKEY parameter. message.
v The enciphered data encrypting key contained in the In the message text:
header.
nnnnnnnn
If the DATAKEYVALUE parameter was specified, then The meaning of RPLFDBWD, the RPL
the specified value (plain text data encrypting key) is Feedback Word. For detailed information on
incorrect. If the DATAKEYFILE parameter was specified, the RPL Feedback Word, see OS/390 DFSMS
then the first record in the data encrypting key data set Macro Instructions for Data Sets.
is incorrect. rc The return code, as follows:
System Action: The system ends the command. For a CLOSE Error
Application Programmer Response: Supply the Code Explanation
correct key. Run the job again.
4 The data set indicated by the
System Programmer Response: If the error recurs access-method control block is
and the program is not in error, look at the messages in already closed.
reporting data bases for a fix for the problem. If no fix 124 A request was cancelled from a use
exists, contact the IBM Support Center. Provide the JCL JRNAD Exit.

128 Index search horizontal chain pointer 88 A previous extend error has occurred
loop encountered. during EOV processing of the data
set.
129 TCLOSE was issued against a media
manager’s structure. 92 Attention message: Inconsistent use
of CBUF processing. Sharing options
132 An uncorrectable I/O error occurred
differ between index and data
while VSAM was reading the job file
components.
control block (JFCB).
96 Attention message: an unusable data
136 Not enough virtual storage was
set was opened for input.
available in the program’s address
space for a work area for CLOSE. 100 Attention message: OPEN
encountered an empty alternate index
that is part of an upgrade set.
while VSAM was reading or writing a
catalog record. 104 Attention message: the time stamp of
the volume on which a data set is
145 An uncorrectable error occurred in the
stored doesn’t match the system time
VSAM volume data set (VVDS).
stamp in the volume record in the
148 An unidentified error occurred while catalog; this indicates that extent
VSAM was searching the catalog. information in the catalog record may
not agree with the extents indicated in
180 A VSAM catalog specified in the JCL the volume’s VTOC.
either does not exist or is not open,
and no record for the data set to be 108 Attention message: the time stamps of
closed was found in any other catalog. a data component and an index
component do not match; this
184 An uncorrectable I/O error occurred indicates that either the data or the
while VSAM was completing index has been updated separately
outstanding I/O requests. from the other. Check for possible
236 A permanent destaging error occurred duplicate VVRs.
in the Mass Storage System 110 Attention message: JRNAD exit was
(RELINQUISH). With temporary not specified on the first ACB opened
CLOSE, destaging error or a staging for the data set. Processing continues
error (ACQUIRE) occurred. without journaling.
246 The compression management 116 Attention message: the data set was
services (CMS) close function failed. not properly closed or was not
opened. If the data set was not
For an OPEN Error properly closed, then data may be lost
0 When register 15 contains 0, no error. if processing continues. Use the
When register 15 contains 8, one of access method services VERIFY
the following conditions exists: command to attempt to close the data
set properly. See DFSMS/MVS
1. VSAM is processing the
Access Method Services for ICF for a
access-method control block for
description of the VERIFY command.
some other request.
In a cross-system shared DASD
2. The access-method control block environment, a return code of 116 can
is already open. have two meanings:
3. DDNAME was not specified v The data set was not properly
correctly in the access-method closed.
control block.
v The data set is opened for output
4. The access-method control block on another processor.
address is incorrect.
4 The data set indicated by the Note: If you use the VERIFY
access-method control block is command, this message can
already open. appear again when VERIFY
processing opens the data set.
76 Attention message: The interrupt If VERIFY processing then
recognition flag (IRF) was detected for successfully closes the data
a data set opened for input set, VERIFY processing issues
processing. condition code 0 at the end of
429
its processing. In addition, an Improved control interval processing
empty cluster cannot be (ICIP) was specified for an extended
verified. format data set will also result in this
error.
118 Attention message: The data set was
not properly closed but OPEN’s For more information on this return
implicit verify was successfully code, see OS/390 DFSMSdfp
processed. Diagnosis Reference.
128 DD statement for this access method 164 An uncorrectable I/O error occurred
control block is missing or incorrect. while VSAM was reading the volume
label.
132 One of the following errors occurred:
v Not enough storage was available 168 The data set is not available for the
for work areas. type of processing specified, or an
attempt was made to open a reusable
v The required volume could not be
data set with the reset option while
mounted.
another user had the data set open.
v An uncorrectable I/O error occurred
while VSAM was reading the job 176 An error occurred while VSAM was
file control block (JFCB). attempting to fix a page of virtual
storage in central storage.
v The format-1 DSCB or the catalog
cluster record is incorrect. 180 A VSAM catalog specified in JCL
v The user-supplied catalog name either does not exist or is not open,
does not match the name on the and no record for the data set to be
entry. opened was found in any other
catalog.
v The user is not authorized to open
the catalog as a catalog. 184 An uncorrectable I/O error occurred
while VSAM was completing an I/O
136 Not enough virtual-storage space is
request.
available in the program’s address
space for work areas, control blocks, 188 The data set indicated by the
or buffers. access-method control block is not of
the type that may be specified by an
140 The catalog indicates this data set has
access-method control block.
an incorrect physical record size.
190 An incorrect high-allocated RBA was
found in the catalog entry for this data
while VSAM was reading or writing a
set. The catalog entry is bad and will
catalog record.
have to be restored.
145 An uncorrectable error occurred in the
192 An unusable data set was opened for
VSAM volume data set (VVDS).
output.
148 No record for the data set to be
193 The interrupt recognition flag (IRF)
opened was found in the available
was detected for a data set opened
catalog(s), or an unidentified error
for output processing.
occurred while VSAM was searching
the catalog. 194 Direct access of a compressed data
component is not allowed.
152 Security verification failed; the
password specified in the 195 An attempt was made to open a
access-method control block for a VSAM Extended Addressable data set
specified level of access doesn’t on a release other than DFSMS/MVS
match the password in the catalog for 1.30.
that level of access; user is not
196 Access to data was requested through
authorized to access this file.
an empty path.
160 The operands specified in the ACB or
200 Volume is unusable.
GENCB macro are inconsistent with
each other or with the information in 204 The ACB MACRF specification is GSR
the catalog record. This error can also and caller is not operating in
occur when the VSAM cluster being supervisor protect key 0 to 7, or the
opened is empty. ACB MACRF specification is CBIC
(control blocks in common) and caller

is not operating in supervisor state duplicate key, or there is a duplicate
with protect key 0 to 7. record for an alternate index with the
unique key option.
205 The ACBCATX option or VSAM
Volume data set OPEN was specified 12 You attempted to store a record out of
and the calling program was not ascending key sequence in
authorized. skip-sequential mode; record had a
duplicate key; for skip-sequential
208 The ACB MACRF specification is GSR
processing, your GET, PUT, and
and caller is using a VS1 system.
POINT requests are not referencing
212 The ACB MACRF specification is GSR records in ascending sequence; or, for
or LSR and the data set requires skip-sequential retrieval, the key
create processing. requested is lower than the previous
key requested. For shared resources,
216 The ACB MACRF specification is GSR buffer pool is full.
or LSR and the key length of the data
set exceeds the maximum key length 16 Record not found.
specified in BLDVRP.
20 Record already held in exclusive
220 The ACB MACRF specification is GSR control by another requester.
or LSR and the data set’s control
24 Record resides on a volume that
interval size exceeds the size of the
cannot be mounted.
largest buffer specified in BLDVRP.
28 Data set cannot be extended because
224 Improved control interval processing is
VSAM cannot allocate additional
specified and the data set requires
direct-access storage space. Either
create mode processing.
there is not enough space left to make
228 The ACB MACRF specification is GSR the secondary allocation request, you
or LSR and the VSAM shared attempted to increase the size of a
resource table (VSRT) does not exist data set while processing with
(no buffer pool is available). SHROPT=4 and DISP=SHR, or the
index CI is not large enough to hold
232 Reset (ACB MACRF=RST) was the entire CA. This error could also be
specified for a nonreusable data set due to a data set trying to extend
and the data set is not empty. beyond 4GB on a system that does
236 Indicates a stage or destage error. not support extended addressability.
240 Format-4 DSCB and catalog time 32 An RBA specified that does not give
stamp verification failed during volume the address of any data record in the
mount processing for output data set.
processing. 36 Key ranges were specified for the
244 The volume containing the catalog data set when it was defined, but no
recovery area was not mounted and range was specified that includes the
verified for output processing. record to be inserted.
245 The ESCON channel is required to 40 Insufficient virtual storage in the user’s
process an extended format data set. address space to complete the
request.
246 The compression management
services (CMS) open function failed. 44 Work area not large enough for the
data record (GET with OPTCD=MVE).
For a Logical I/O Error 56 At the beginning of CI or CA split for
4 End of data set encountered (during backup while open (BWO), an error
sequential retrieval), or the search was detected in catalog update
argument is greater than the high key processing.
of the data set. Either no EODAD 64 As many requests are active as the
routine is provided, or one is provided number specified in the STRNO
and it returned to VSAM and the parameter of the ACB macro;
processing program issued another therefore, another request cannot be
GET. activated.
8 You attempted to store a record with a 68 An attempt was made to use a type of
431
processing (output or control-interval) TRANSID was greater than 31 or
that was not specified when the data the shared resource option was
set was opened. not specified.
72 You made a keyed request for access 6. ICI processing was specified, but
to an entry-sequenced data set, or a request other than a GET or a
you issued a GETIX or PUTIX to an PUT was issued.
entry-sequenced or relative record 7. MRKBFR MARK=OUT or
data set. MARK=RLS was issued, but the
RPL did not have a data buffer
76 You issued an addressed or
associated with it.
control-interval PUT to add to a
key-sequenced data set, or you 8. The RPL specified WAITX, but the
issued a control-interval PUT to a ACB did not specify LSR or GSR.
relative record data set. 108 The RECLEN specified was larger
80 You issued an ERASE request for than the maximum allowed, equal to
access to an entry-sequenced data 0, or smaller than the sum of the
set, or you issued an ERASE request length and the displacement of the
for access to an entry-sequenced data key field of the base cluster or related
set via a path. alternate index (AIX). The RECLEN
was not equal to the slot size
84 OPTCD=LOC specified for a PUT specified for a relative record data set.
request or in a request parameter list
in a chain of request parameter lists. 112 KEYLEN specified was too large or
equal to 0.
88 You issued a sequential GET request
without having caused VSAM to be 116 During initial data set loading (that is,
positioned for it, or you changed from when records are being stored in the
addressed access to keyed access data set the first time it’s opened),
without causing VSAM to be GET, POINT, ERASE, direct PUT, and
positioned for keyed-sequential skip-sequential PUT with
retrieval; there was no positioning OPTCD=UPD are not allowed. During
established for sequential PUT insert initial data set loading, VERIFY is not
for a relative record data set, or you allowed except for an
attempted an incorrect switch between entry-sequenced data set (ESDS)
forward and backward processing. defined with the RECOVERY option.
For initial loading of a relative record
92 You issued a PUT for update or an data set, the request was other than a
ERASE without a previous GET for PUT insert.
update or a PUTIX without a previous
GETIX. 120 The request was operating under an
incorrect TCB. For example, an
96 An attempt was made to change the end-of-volume call or a GETMAIN
prime key or key of reference while would have been necessary to
making an update. complete the request, but the request
100 An attempt was made to change the was issued from a job step other than
length of a record while making an the one that opened the data set. The
addressed update. request can be resubmitted from the
correct task if the new request
104 The RPL options are either incorrect reestablishes positioning.
or conflicting in one of the following
ways: 124 A request was cancelled for a user
JRNAD exit.
1. SKP was specified and either KEY
was not specified or BWD was 128 A loop exists in the index horizontal
specified. pointer chain during index search
2. BWD was specified for CNV processing.
processing. 132 An attempt was made in locate mode
3. FWD and LRD were specified. to retrieve a spanned record.
4. Neither ADR, CNV, nor KEY was 136 You attempted an addressed GET of
specified in the RPL. a spanned record in a key-sequenced
5. WRTBFR, MRKBFR, or SCHBER data set.
was issued was issued, but either

140 Inconsistent spanned record. SVC 109 by ACQRANGE, CNVTAD,
and MNTACQ macros (return code =
144 Incorrect pointer (no associated base
36).
record) in an alternate index.
217 Incorrect AMBL detected by SVC 109
148 The maximum number of pointers in
called by ACQRANGE, CNVTAD, and
the alternate index has been
MNTACQ macros (return code = 40).
exceeded.
218 Unrecognizable return code from SVC
152 Not enough buffers are available to
109.
process your request (shared
resources only). 224 MRKBFR OUT was issued for a buffer
with incorrect contents.
156 An addressed GET UPD request
failed because the control interval flag 228 Caller in cross-memory mode is not in
was on, or an incorrect control interval supervisor state or RPL of caller in
was detected during keyed SRB or cross-memory mode does not
processing. In the latter case, the specify SYN processing.
control interval is incorrect for one of
229 The record length changed during
the following reasons:
decompression processing of a
1. A key is not greater than the compressed data set.
previous key.
232 UPAD error. ECB was not posted by
2. A key is not in the current control
user in cross-memory mode.
interval.
3. A spanned record RDF is present. 236 Validity check error for
SHAREOPTIONS 3 or 4.
4. A free space pointer is incorrect.
5. The number of records does not 240 For shared resources, one of the
match a group RDF record count. following is being performed:
6. A record definition field is 1. An attempt is being made to
incorrect. obtain a buffer in exclusive control.
7. An index CI format is incorrect. 2. A buffer is being invalidated.
3. The buffer use chain is changing.
160 One or more candidates were found
with a modified buffer marked to be For more detailed feedback, reissue
written. The buffer was left in write the request.
status with valid contents. With this
condition, it is possible to have other 244 Register 14 stack size is not large
buffers invalidated or found under enough.
exclusive control. 245 A severe error was detected by the
192 Incorrect relative record number. compression management services
(CMS) during compression
196 You issued an addressed request to a processing.
relative record data set.
246 A severe error was detected by the
200 You attempted addressed or compression management services
control-interval access through a path. (CMS) during decompression
processing.
204 PUT insert requests are not allowed in
backward mode. 248 Register return offset went negative.
208 The user has issued an ENDREQ 250 A valid dictionary token does not exist
macro instruction against an RPL that for the compressed data set. The data
has an outstanding WAIT against the record cannot be decompressed.
ECB associated with the RPL. This
can occur when an ENDREQ is 252 Record mode processing is not
issued from a STAE or ESTAE routine allowed for a linear data set.
against an RPL that was started 253 VERIFY is not a valid function for a
before the ABEND. No ENDREQ linear data set.
processing has been done.
254 I/O activity on the data set was not
212 Unable to split index; increase index quiesced before the data set was
CI size. closed.
216 Incorrect parameter list passed to
433
Note: See OS/390 DFSMS Macro Instructions for Data ddname
Sets. for additional information on the return The DD name.
codes.
System Action: The action depends on the function
being processed. See the message in the program
UNIT parameter. Run the command again.
listing following this message.
cause of the error.
and the program is not in error, look at the messages in exists, contact the IBM Support Center. Provide the
the job log for more information. Search problem JCL, the SYSOUT output for the job, and all printed
reporting data bases for a fix for the problem. If no fix output and output data sets related to the problem.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCIO01, IDCIO02, IDCIO03
IDC3384I FILE ddname SPECIFIED AN INVALID
UNIT FOR FUNCTION REQUESTED
IDC3380I FILE ddname MUST SPECIFY A
Explanation: The direct access storage unit, specified
DEMOUNTABLE UNIT
on the DD statement through the FILE parameter, is not
Explanation: The unit for the file defined by the DD supported by this function. The unit is not a direct
statement with the name indicated was not assigned for access device or, if DASD, is not a 3330 or 3330V.
exclusive control. Volumes cannot be mounted or
demounted on this unit. Either the volume allocated by
the DD statement was already mounted when the ddname
statement was processed, or the correct parameters The DD name.
were not specified on the DD statement.
ddname UNIT parameter. Run the command again.
The DD name.
System Action: The system ends the job. and the program is not in error, look at the messages in
again after demounting the volume. This causes the
device to be assigned for exclusive control while the job
or step is running.
Source: DFSMSdfp
the job log for more information. Search problem Detecting Module: IDCSA06
JCL, the SYSOUT output for the job, and all printed IDC3385I VOLUME ser IS PERMANENTLY
output and output data sets related to the problem. RESIDENT OR RESERVED
Source: DFSMSdfp Explanation: The volume is marked permanently

resident or reserved in the unit control block (UCB).
Detecting Module: IDCIO01, IDCIO02, IDCIO03, Therefore, the volume cannot be demounted. The
IDCRS06 volume needs to be demounted either to perform a
Mass Storage Control (MSC) function or so that the
proper volume can be mounted on that unit.
IDC3383I FILE ddname MUST SPECIFY A
VIRTUAL UNIT In the message text:
Explanation: The DD statement specified through the ser The volume serial number.
FILE parameter does not specify a virtual unit but a
virtual unit is required. System Action: The system ends processing.
In the message text: Application Programmer Response: Ensure that the

DD statement named in the FILE parameter specifies

the correct volume serial. You might have mistakenly Application Programmer Response: Check the input
specified the volume serial of a permanently resident or parameters of the MODIFYC command for errors. If any
reserved volume. If the DD statement does have the errors are found, correct the input. Run the command
correct volume serial, then you cannot run the again. If errors cannot be found, one of the following
command while that volume is permanently resident or commands can be run to help determine where the
reserved. cartridge is and what the cartridge status is.
System Programmer Response: If the error recurs The command is:
and the program is not in error, look at the messages in v LISTMSF command if the cartridge is a scratch
the job log for more information. Search problem cartridge.
v LISTMSVI command if the cartridge is part of a mass
storage volume.
output and output data sets related to the problem. v AUDITMSS command if the cartridge to be modified
was requested by using the CELL parameter.
Source: DFSMSdfp
If the cartridge still cannot be located, see Problem
IDC3392I NO UNIT AVAILABLE FOR VOLUME Determination.
volser System Programmer Response: If the error recurs
Explanation: The TEST enqueue indicates that the and the program is not in error, look at the messages in
volume is allocated to a job step, but no unit is available the job log for more information.
for mounting the volume. All units that have open virtual Source: DFSMSdfp
storage access method (VSAM) catalogs are
non-shareable and cannot be used. Detecting Module: IDCMC01
IDC3437I ACCESSED CELL IS EMPTY OR THE
volser The volume serial number. DESTINATION CELL IS FULL
System Action: The system ends the job. Explanation: The attempt to modify a cartridge failed
Application Programmer Response: Either change because the home cell where the cartridge was
the disposition of your data set to share or run the job supposed to be was empty, or an attempt to reassign a
again when a non-shareable unit is available. cartridge to a new location failed because the new
location is already occupied.
Source: DFSMSdfp
System Action: The system ends the MODIFYC
Detecting Module: IDCSA06 command.
Application Programmer Response: Check the input
IDC3435I CARTRIDGE NOT EJECTED, EXIT parameters of the MODIFYC command for errors. If
STATION FULL errors are found, correct them and submit the command
Explanation: A request was made to eject a cartridge again. If errors cannot be found, do the following:
from the cartridge access station, but the cartridge 1. Run the MODIFYC command again unchanged
access station was already full. because the cartridge that was requested might
have been at a data recording device when the
System Action: The system ends the MODIFYC initial request was processed. If the same error
command. The cartridge remains in its original location occurs, one of the following commands can be run
in the cartridge store. to help determine the nature of the error. If the
Application Programmer Response: Have the home cell location is not known, the commands
operator empty the cartridge access station and run the LISTMSF for scratch cartridges or LISTMSVI for
command again. cartridges that are part of volumes, can be run to
determine the home cell location. The AUDITMSS
Source: DFSMSdfp command can then be run against the found cell
location and the new location specified in the TO
parameter to determine the status of the cells.
2. Correct any errors that were found in Step 1. Run
IDC3436I CARTRIDGE TO BE MODIFIED COULD the MODIFYC command again.
NOT BE LOCATED 3. If the above actions do not correct the problem, see
the Problem Determination.
Explanation: The request to modify a cartridge failed
because the cartridge could not be found. System Programmer Response: If the error recurs
System Action: The system ends the MODIFYC
command.
435
Source: DFSMSdfp Detecting Module: IDCDE02
Detecting Module: IDCMC01
IDC3503I FILE SEQUENCE LIST IS
INCONSISTENT WITH VOLUME LIST
IDC3438I ACCESSED OR DESTINATION CELL
ADDRESS IS INVALID FOR THIS MSF Explanation: The number of elements in the
FILESEQUENCENUMBERS parameter list is not equal
Explanation: The accessed or destination cell address
to the volumes in the VOLUMES parameter list.
is specified incorrectly. Either the Mass Storage Facility
is incorrectly identified or the cell address parameter did System Action: The command is ended.
not follow the rules of specification for each model of a
Mass Storage Facility.
error. Check the elements in both lists, and make
System Action: The MODIFYC commands ends. The corrections where needed.
return code is 12.
Application Programmer Response: Examine the and the program is not in error, search problem
input parameters of the MODIFYC command. Ensure reporting data bases for a fix for the problem. If no fix
that the parameters are consistent with the Mass exists, contact the IBM Support Center. Provide the JCL
Storage System requirements for each model of a Mass and the SYSOUT output for the job.
Storage Facility. Correct any errors in the input
Source: DFSMSdfp
parameters and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCMC01
IDC3504I THE RANGE LIST CANNOT BE
CONSTRUCTED
IDC3500I A VALID VSAM DEFINE STRUCTURE
Explanation: In the construction of the RANGE LIST,
WAS NOT PROVIDED
the allotted area was not sufficient.
Explanation: The object parameter list was not
System Action: The command is ended.
specified properly. The access method services
reader/interpreter should have detected this error. Application Programmer Response: Possible system
error. Rerun the job with the PARM option--PARM TEST
(FULL((DEFN.1.1))); contact your system programmer.
System Programmer Response: Probable system
error. See DFSMS/MVS Access Method Services for
ICF for the valid specification. If the error recurs and the
program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact
the IBM Support Center. Provide the JCL and the
SYSOUT output for the job. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCDE02
IDC3505I INCORRECT SPECIFICATION OF
SPACE ALLOCATION
IDC3501I MODEL ENTYPE IS NOT CONSISTENT
WITH THE OBJECT BEING DEFINED Explanation: The space parameters TRACKS,
CYLINDER, or RECORDS do not appear on the
Explanation: The object being used to model a VSAM
appropriate object parameter list.
data set or user catalog differs from that being defined.
error. See the DEFINE command and space
error. Ensure that the model object type is identical to
specifications in DFSMS/MVS Access Method Services
that being defined.
for ICF
Source: DFSMSdfp

Source: DFSMSdfp
IDC3514I KEYRANGES ARE INVALID
Explanation: The KEYRANGES parameter (DEFINE
or IMPORT command) specified incorrect key values for
IDC3506I A REQUIRED VOLUME OR DEVT LIST the low or high key values:
HAS BEEN OMITTED v The high key value is lower than the low key value in
Explanation: The VOLUMES parameter does not a low-key high-key pair.
appear in the command when required. v Two or more low-key high-key pairs overlap, or are
identical.
error. A volume list must be available to DATA and Application Programmer Response: Correct the
INDEX objects (the INDEX object appears only if the KEYRANGES specifications.
data set is KSDS). The availability may be through
Source: DFSMSdfp
explicit specification of volumes, via propagation of
volumes from the Cluster parameter list or from the Detecting Module: IDCDE02
model object.
IDCMP01
IDC3515I AVERAGE RECORD SIZE EXCEEDS
MAXIMUM RECORD SIZE
and the SYSOUT output for the job. Explanation: The first size value of the RECORDSIZE
parameter is greater than the second.
Source: DFSMSdfp
System Action: Processing for the command is
ended.
Application Programmer Response: Correct either
IDC3507I THE RECORDSIZE PARAMETER IS
the average or the maximum size value.
REQUIRED BUT NOT SPECIFIED
Source: DFSMSdfp
Explanation: The RECORDSIZE parameter must be
specified when defining VSAM space and the allocation Detecting Module: IDCDE02
unit is records.
System Action: The command is ended. IDC3516I KEYS PARAMETER REQUIRED FOR
KEY SEQUENCED DATA SET
error. Specify RECORDSIZE and resubmit the job. Explanation: The definition of a KSDS requires the
specification of the key position and length, via the
KEYS parameter.
reporting data bases for a fix for the problem. If no fix System Action: Processing for the command is
exists, contact the IBM Support Center. Provide the JCL ended.
Source: DFSMSdfp DEFINE command.
Detecting Module: IDCDE01 Source: DFSMSdfp
IDC3513I DYNAMIC ALLOCATION FAILED OR
FILE NOT CODED WHEN REQUIRED
IDC3517I AVG AND MAX RECORDSIZE NOT
Explanation: FILE was specified in a utility command EQUAL FOR RELATIVE RECORD DATA
and the ddname was not found. SET
System Action: The command is ended. Explanation: The RECORDSIZE parameter specified
average and maximum record sizes that were not equal.
Application Programmer Response: See if the
Relative record data sets must have fixed-length
ddname on the FILE parameter is the same as the
records.
corresponding dd statement ddname.
Source: DFSMSdfp
the average or the maximum size value.
437
Source: DFSMSdfp
IDC3522I SPANNED ATTRIBUTE REQUIRED FOR
Detecting Module: IDCDE02 RECORDSIZE GREATER THAN 32,761
Explanation: The RECORDSIZE parameter specifies
IDC3518I REUSE PARAMETER INVALID WITH a maximum size greater than 32,761, but SPANNED is
UNIQUE OR KEYRANGES not specified.
Explanation: The REUSE attribute may not be System Action: The command is ended.
specified for a cluster or an alternate index together with
the UNIQUE or KEYRANGES parameter, either
RECORDSIZE parameter, or specify the SPANNED
explicitly or implicitly thru use of the MODEL parameter.
parameter.
Source: DFSMSdfp
command by deleting either the REUSE or the UNIQUE
and/or KEYRANGES parameter; then rerun the job.
IDC3523I GENERATION DATA GROUP NAME
Source: DFSMSdfp
EXCEEDS 35 CHARACTERS
Explanation: The name specified for a generation
data group cannot exceed 35 characters.
IDC3519I REUSE ATTRIBUTE CONFLICT
BETWEEN DATA AND INDEX
Application Programmer Response: Shorten the
Explanation: The REUSE attribute was not the same
generation data group name and rerun the job.
for the data and index objects. Examples:
1. NOREUSE is specified at the cluster level and Source: DFSMSdfp
REUSE is specified at the data level with nothing Detecting Module: IDCDE02
specified at index level resulting in index defaulting
to NOREUSE.
IDC3524I KEYRANGE VALUES EXCEED
2. Modeling at the cluster level and explicitly overriding
KEYLENGTH OR ARE NOT IN
model attributes at data or index level but not both.
ASCENDING ORDER
Explanation: This message is issued by DEFINE
Application Programmer Response: Redefine the when the key values of the KEYRANGE parameter are
object ensuring that data and index REUSE attributes specified incorrectly. Either a key range key value was
are in harmony. longer than the user specified/defaulted key length or
the key range pairs were in nonascending order.
Source: DFSMSdfp
key range values on the DEFINE command. Determine
IDC3521I SPANNED ATTRIBUTE INVALID FOR A
what the key length will be for the data set and insure
RELATIVE RECORD DATA SET
that all key values specified in the KEYRANGE
Explanation: SPANNED and NUMBERED were parameter are no longer than this length. Also, insure
specified together, either explicitly or through use of the that key range pairs are ordered in ascending
MODEL parameter. Records of an RRDS may not span sequence. Then resubmit the job.
control intervals.
Source: DFSMSdfp
Detecting Module: IDCDE01, IDCDE02
SPANNED parameter or the data set type specification.
IDC3525I INSUFFICIENT SECURITY
Source: DFSMSdfp AUTHORIZATION TO ALTER KEYS
Detecting Module: IDCDE01 Explanation: The level of password supplied was not
high enough or the RACF authorization was insufficient
to permit the ALTER to occur. To modify KEY values,
the master password of the cluster, alternate index, or
path is needed or, alternatively, the catalog master
password could be supplied. Since both the data and
index components will be altered, if one component is

password-protected and the other is not, the master Source: DFSMSdfp
password of the protected component is sufficient.
System Action: Processing of the command is ended.
Application Programmer Response: Supply the IDC3530I ENTRY AND NEWNAME PDS NAMES
proper level password or have your RACF profile MUST BE THE SAME
altered to the required level of access. Rerun the job.
Explanation: An attempt was made to rename PDS
Source: DFSMSdfp member but the entry name and the new name
referenced different partitioned data set names.
IDC3527I ALTER WAS UNABLE TO LOCATE Application Programmer Response: Make sure that
ATTRIBUTES OF OBJECT TO BE the same PDS name is given in both the entry name
MODIFIED and new name parameters.
Explanation: The entry to be modified could not be Source: DFSMSdfp
found in the catalog.
Application Programmer Response: Verify that the IDC3531I dsname IS A RLS DATA SET WHICH IS
catalog entry exists and the catalog being used is INCOMPATIBLE WITH THIS LEVEL OF
proper. DFSMS
System Programmer Response: If the error recurs Explanation: The data set specified on an IDCAMS
and the program is not in error, search problem ALTER NEWNAME command is a RLS data set and
reporting data bases for a fix for the problem. If no fix cannot be altered on this level of DFSMS.
dsname The data set name.
Source: DFSMSdfp
command.
Application Programmer Response: Run command
IDC3528I THE OBJECT TO BE MODIFIED IS
on appropriate level of DFSMS.
PASSWORD SUPPRESSED
Source: DFSMSdfp
Explanation: The MASTERPW password of the entry
or the UPDATEPW or higher level catalog password Detecting Module: IDCAL02
must be supplied for modifications to be allowed to the
entry.
IDC3536I INVALID USE OF * WITH THE
System Action: The command is ended. NEWNAME PARAMETER
Application Programmer Response: Verify which Explanation: If either the ENTRYNAME or
password is required and provide the password. NEWNAME parameter specifies a generic name (*),
then both must.
Source: DFSMSdfp
both the ENTRYNAME and NEWNAME parameters
IDC3529I NAME CREATED FROM GENERIC
specify a generic name if either do.
NEWNAME IS LONGER THAN 44
CHARACTERS System Programmer Response: If the error recurs
Explanation: The access method services ALTER
command issues this message when it is asked to
rename data sets using a generic name, and one of the
resulting new data set names is longer than 44
characters. Source: DFSMSdfp
System Action: The command is ended. Detecting Module: IDCAL01
error and rerun the job.
439
IDC3537I INVALID ALTERNATE INDEX IDC3540I KEYS/RECORDSIZE VALUES
PARAMETERS SPECIFIED CONFLICT WITH CONTROL INTERVAL
SIZE
Explanation: Either UPGRADE is specified but the
object being altered is not an alternate index, or Explanation: The new key length, key position, or
UNIQUEKEY is specified but the data object being maximum record size is such as to require a larger
altered is not the data object of an alternate index. control interval.
System Action: The command is ended. System Action: The object’s catalog entry is not
altered.
specify the name of an alternate index, or the data Application Programmer Response: Delete and
object name of an alternate index. redefine the object with the proper KEYS and
RECORDSIZE parameters.
IDC3541I NEW ALTERNATE INDEX KEY VALUES
Source: DFSMSdfp
CONFLICT WITH BASE CLUSTER
Detecting Module: IDCAL01 RECORDSIZE
Explanation: The ALTER command for an alternate
IDC3538I UNIQUEKEY/UPGRADE INVALID FOR index specifies a KEYS parameter for a key whose
NON-EMPTY ALTERNATE INDEX ending position is outside the base cluster’s maximum
record size. If the base cluster is spanned, the ending
Explanation: The UNIQUEKEY or UPGRADE
key position must be in the base cluster’s first control
parameter is specified, but the alternate index is
interval.
non-empty. These parameters may only be specified if
the alternate index contains no records. System Action: The object’s catalog entry is not
altered.
Application Programmer Response: If
ALTER command or correct the base cluster’s
UNIQUEKEY/UPGRADE alternate index is truly desired,
maximum record size or control interval size.
the alternate index must be deleted and redefined with
proper attributes, then rebuilt with BLDINDEX. Source: DFSMSdfp
System Programmer Response: If the error recurs Detecting Module: IDCAL01
IDC3542I AVG AND MAX RECORDSIZE NOT
EQUAL FOR RELATIVE RECORD DATA
SET
Source: DFSMSdfp
Explanation: The RECORDSIZE parameter specified
Detecting Module: IDCAL01 average and maximum record sizes that were not equal.
Relative record data sets must have fixed-length
records.
IDC3539I KEYS AND/OR RECORDSIZE
PARAMETER SPECIFIED FOR System Action: Processing of the command is ended.
NON-EMPTY OBJECT
Explanation: The ALTER command specified the the average or the maximum size value.
KEYS or RECORDSIZE parameter, but the cluster or
Source: DFSMSdfp
alternate index contains data records.
System Action: The object’s catalog entry is not
altered.
IDC3545I KEYS AND/OR RECORDSIZE VALUES
Application Programmer Response: If you want to
CANNOT BE ALTERED
change key position and/or record size, you must
delete, redefine, and reload the object. Explanation: The ALTER command specified new
KEYS or maximum RECORDSIZE values for an object
Source: DFSMSdfp
whose corresponding values were specified when the

object was defined, or which have been altered to
IDC3568I (xxx) INVALID USE OF *
non-default values.
Explanation: The level name starts or ends with an *,
System Action: The object’s catalog entry is not
which is not allowed.
altered.
Application Programmer Response: Delete and
correctly redefine the object. xxx The indicated level name.
Source: DFSMSdfp System Action: The command is ended.
Detecting Module: IDCAL01 Application Programmer Response: Correct the
level name and rerun the job.
IDC3546I NEW KEY VALUES CONFLICT WITH System Programmer Response: If the error recurs
RECORDSIZE and the program is not in error, search problem
Explanation: The ALTER command specifies a KEYS
parameter that defines a key whose ending position is
outside the maximum recordsize.
Source: DFSMSdfp
Application Programmer Response: Specify key
length and position such that the key is entirely
contained in the base cluster record. IDC3570I DELIMITERS MUST NOT BE SPECIFIED
WHEN RELOADING A CATALOG
Source: DFSMSdfp
Explanation: REPRO command delimiters
(FROMKEY, TOKEY, etc.) cannot be specified for
reloading a catalog.
IDC3547I ENTRY TYPE INVALID WITH
KEYS/RECORDSIZE PARAMETER
Application Programmer Response: Remove
Explanation: The entry name specified is not the data
delimiters from the REPRO command.
component of a cluster or alternate index, nor is it a
cluster or alternate index, nor is it a path over a cluster System Programmer Response: If the error recurs
or alternate index. and the program is not in error, search problem
System Action: The entry’s catalog data is not
altered. Processing of the command is ended.
Source: DFSMSdfp
entry name and rerun the job.
Source: DFSMSdfp
IDC3572I TARGET CATALOG IS TOO SMALL TO
CONTAIN THE BACKUP CATALOG
IDC3558I FORCE OPTION IS INVALID FOR
Explanation: The size of the target catalog is
ENTRY TYPE
inadequate.
Explanation: The FORCE option on the DELETE
command can be used to delete only data spaces,
generation data groups, and VSAM user catalogs, but Application Programmer Response: Determine size
the FORCE option was specified on a DELETE of the backup catalog from LISTCAT output obtained at
command for some other type of entry. the time of the unload. Redefine the target catalog with
adequate space to contain the low key range of the
System Action: The DELETE command is not run.
catalog.
Processing continues.
Source: DFSMSdfp
441
v VVDS Sphere Record (maybe)
IDC3573I text
Explanation: text is one of the following: An additional record has been found.
NAME OF BACKUP AND TARGET CATALOG DO
NOT AGREE System Action: Processing is ended.
VOLSER OF BACKUP AND TARGET CATALOG DO Application Programmer Response: Use the PRINT
NOT AGREE command to display the contents of the target catalog. If
DEVTYP OF BACKUP AND TARGET CATALOG DO it contains more than the expected records redefine the
NOT AGREE catalog and rerun the job.
The target catalog name, its volume serial number, System Programmer Response: If the error recurs
and/or the device type do not agree with the backup. and the program is not in error, search problem
System Action: The command is ended. exists, contact the IBM Support Center. Provide the JCL
Application Programmer Response: Check whether
you are reloading from the proper backup into the Source: DFSMSdfp
intended catalog.
reporting data bases for a fix for the problem. If no fix IDC3578I SOURCE AND TARGET CATALOG ARE
exists, contact the IBM Support Center. Provide the JCL SAME
and the SYSOUT output for the job. Explanation: During an ICF catalog REPRO copy
Source: DFSMSdfp request, it has been determined that the ICF catalog
names, identified by the INFILE/INDATASET and
Detecting Module: IDCRP01 OUTFILE/OUTDATASET parameters, specify the same
name. This implies a copy to itself and is not allowed.
IDC3576I ALTER CATALOG NAME FOR dsname System Action: Processing is ended.
FAILED
Explanation: During REPRO copy of a catalog entry source or target catalog specification and rerun the job.
record, from one ICF catalog to another, an attempt was
made to update the catalog pointer in the corresponding System Programmer Response: If the error recurs
VVR record. This update processing for dsname failed. and the program is not in error, search problem
In the message text: exists, contact the IBM Support Center. Provide the JCL
dsname
System Action: Processing is ended. Detecting Module: IDCRP01
Application Programmer Response: Resolve
problem described by preceding message(s), restore IDC3579I SOURCE CATALOG LRECL IS LARGER
volumes and rerun the job. THAN TARGET CATALOG LRECL
System Programmer Response: If the error recurs Explanation: Before an ICF catalog copy operation,
and the program is not in error, search problem the LRECL of the source catalog has been compared to
reporting data bases for a fix for the problem. If no fix that of the target catalog. It has been determined that
exists, contact the IBM Support Center. Provide the JCL the source catalog LRECL value is larger than the
and the SYSOUT output for the job. target LRECL value and thus records in the source
catalog may not fit in the target catalog.
Source: DFSMSdfp
System Action: Processing is ended.
Application Programmer Response: Review the
attributes of the target catalog and redefine it with an
IDC3577I TARGET CATALOG IS NOT EMPTY
LRECL value equal to or greater than that of the source
Explanation: During a REPRO copy of an ICF catalog. Rerun the job.
catalog, a non-empty target catalog has been found. An
empty catalog should contain only the following:
v Catalog Sphere Record
v Catalog Data Component Truename Record
v Catalog Index Component Truename Record

Source: DFSMSdfp v the source is a non-relative record data set and the
target is a non-empty relative record data set that is
not specified for reuse; or
v one data set is linear and the other data set is
IDC3580I dsname DOES NOT SPECIFY A BASE non-linear. The LRECL of the physical sequential
OBJECT data set is not equal to the CISIZE of the linear data
Explanation: During a REPRO ICF catalog merge set.
operation, catalog entry dsname was found to identify: System Action: The command is ended.
v An entry for an object other than
– a cluster Application Programmer Response: Check the
– a non-VSAM status of the input and output data sets. REPRO is
– a GDG unable to satisfy your request. Set up data sets
– a user catalog correctly and rerun the job.
v A VVDS name System Programmer Response: If the error recurs
v The source catalog name and the program is not in error, search problem
dsname and the SYSOUT output for the job.
System Action: Processing is ended. Detecting Module: IDCRP01
ENTRIES specification and rerun the job. IDC3583I ‘prm’ INCOMPATIBLE WITH INFILE
System Programmer Response: If the error recurs DATA SET TYPE
and the program is not in error, search problem Explanation: The specified parameter is not correctly
reporting data bases for a fix for the problem. If no fix used with this type data set. A conflict results between
exists, contact the IBM Support Center. Provide the JCL delimiters and the data set type. An example is
and the SYSOUT output for the job. specifying the TOKEY parameter with an relative-record
Source: DFSMSdfp data sets.
Detecting Module: IDCRP01 In the message text:

IDC3581I REPRO OF CATALOGS CANNOT System Action: The command is ended.
SPECIFY DELIMITERS
Explanation: The REPRO command does not process parameters or data set specified and rerun.
beginning and ending delimiters when you are copying
catalogs. System Programmer Response: If the error recurs
System Action: The command is ended. reporting data bases for a fix for the problem. If no fix
Application Programmer Response: Remove the exists, contact the IBM Support Center. Provide the JCL
incorrect parameters from the command and rerun job. and the SYSOUT output for the job.

and the program is not in error, search problem Detecting Module: IDCPR01
exists, contact the IBM Support Center. Provide the JCL IDCRP01
Source: DFSMSdfp IDC3584I RECOVERABLE CATALOGS CANNOT
BE COPIED
Explanation: A REPRO command specified a VSAM
catalog copy operation where either the input catalog or
IDC3582I INPUT DATA SET ORGANIZATION the output catalog or both was defined with the
INCOMPATIBLE WITH OUTPUT DATA RECOVERABLE attribute. Neither the source or target
SET catalog can be recoverable in a catalog copy operation.
Explanation: When you attempt to copy information System Action: The command is ended.
from one data set into another, this error condition
occurs when one of the following is true: Application Programmer Response: To convert a
443
unrecoverable catalog into a recoverable catalog, you Application Programmer Response: Change the DD
must export each VSAM data set from the statement pointed to by the OUTFILE parameter or the
unrecoverable catalog, then import it into the newly data set name specified by the OUTDATASET
defined recoverable catalog. To convert a recoverable parameter to specify a target data set with the
catalog into a unrecoverable catalog or to copy a appropriate record length.
recoverable catalog into a recoverable catalog, you can
either export each VSAM data set from the source
catalog and then import it into the target catalog or use
the EXPORTRA/IMPORTRA commands to accomplish
the same thing on a volume basis.
Source: DFSMSdfp
Source: DFSMSdfp
IDC3585I dsname IS INVALID FOR

IDC3587I UNLOAD/RELOAD NOT ALLOWED
{ENCIPHER|DECIPHER}
FOR CATALOG
Explanation: The data set is not a valid source or
Explanation: An ICF catalog was identified as the
target for an ENCIPHER or DECIPHER operation. The
source or target catalog during a REPRO request and
data is incorrect for one of the following reasons:
the other object identified was a non-VSAM data set.
v ENCIPHER was specified and the source is a VSAM This implies an ICF catalog unload or reload operation
catalog. and it is not allowed.
v ENCIPHER was specified and the target is not a
SAM or VSAM ESDS (entry-sequenced data set)
data set. Application Programmer Response: Correct the
v DECIPHER was specified and the target is a VSAM source and/or target specifications and rerun the job.
catalog. System Programmer Response: If the error recurs
v DECIPHER was specified and source is not a SAM and the program is not in error, search problem
or VSAM ESDS data set. reporting data bases for a fix for the problem. If no fix
In the message text: and the SYSOUT output for the job.
dsname Source: DFSMSdfp
The data set name.
Application Programmer Response: Change the DD IDC3588I WRONG CATALOG TYPE FOR
statement pointed to by the INFILE or OUTFILE MERGECAT PARAMETER
parameter or the data set name specified by the
Explanation: The MERGECAT parameter has been
INDATASET or OUTDATASET parameter to specify a
coded but the source and target catalogs, identified by
data set of the correct type for the operation.
the INFILE/INDATASET and OUTFILE/OUTDATASET
System Programmer Response: If the error recurs parameters, are not both ICF catalogs.
exists, contact the IBM Support Center. Provide the JCL Application Programmer Response: Remove the
and the SYSOUT output for the job. MERGECAT parameter or correct the source and target
catalog specifications and rerun the job.
Source: DFSMSdfp
IDC3586I CANNOT ENCIPHER RRDS TO exists, contact the IBM Support Center. Provide the JCL
TARGET DATA SET and the SYSOUT output for the job.
Explanation: The source data set for an encipher Source: DFSMSdfp
operation is a VSAM RRDS (relative record data set),
but the record size (VSAM) or the logical record length
(SAM) of the target data set is not at least 4 bytes
greater than the record size of the source RRDS.

IDC3589I VVDS NOT ALLOWED FOR REPRO
Source: DFSMSdfp
Explanation: A VVDS has been identified as the
source or target object of a REPRO command. The Detecting Module: IDCRX01, IDCCC01, IDCRC02,
data set identified by the INFILE/INDATASET or IDCXP01
OUTFILE/OUTDATASET parameters has the VVDS
prefix ‘SYS1.VVDS.V’.
IDC3596I THE DATA SET SPECIFIED IN THE
System Action: Processing is ended. EXPORT PARAMETER IS NOT USABLE
Application Programmer Response: Correct the Explanation: The data set specified in the EXPORT
source or target specifications and rerun the job. command has been marked as not usable by a
DELETE FORCE operation or by a RESETCAT
operation because of space occupancy conflicts.
reporting data bases for a fix for the problem. If no fix System Action: Processing of the command is ended.
and the SYSOUT output for the job. Application Programmer Response: This data set
cannot be exported under current catalog conditions. If
Source: DFSMSdfp you wish to recover the data, use the REPRO
command.
IDC3592I THE ENTRY NAME IS NOT A CLUSTER,
ALTERNATE INDEX OR ICF CATALOG
Explanation: The object identified by the entry and the SYSOUT output for the job.
parameter in the EXPORT command is not a cluster,
Source: DFSMSdfp
alternate index or ICF catalog. Only cluster, alternate
index or ICF catalog objects can be exported. Detecting Module: IDCXP01
System Action: The command is ended. No export
action takes place. IDC3598I OBJECT IS A VSAM VOLUME DATA
SET WHICH CANNOT BE EXPORTED
Application Programmer Response: If a catalog is to
be disconnected, DISCONNECT must be specified in Explanation: The object identified by the entry
the command. Check to be sure your entry name is a parameter in the EXPORT command is a VSAM volume
cluster, alternate index or ICF catalog object name. Data Set which cannot be exported.
System Programmer Response: If the error recurs System Action: The command is ended. No export
and the program is not in error, search problem action takes place.
exists, contact the IBM Support Center. Provide the JCL Application Programmer Response: Do not attempt
and the SYSOUT output for the job. to export a VSAM Volume Data Set.

Detecting Module: IDCXP01 reporting data bases for a fix for the problem. If no fix
IDC3593I A REQUIRED CATALOG FIELD WAS
NOT LOCATED Source: DFSMSdfp
Explanation: One of the following required catalog Detecting Module: IDCXP01
fields could not be located by catalog management:
ENTYPE, ENTNAME, or NAMEDS.
IDC3599I UNABLE TO SERIALIZE ON CATALOG
System Action: The command is ended. No export catname
action takes place.
Explanation: An attempt was made and has failed to
Application Programmer Response: Something is serialize the catalog, CNVTCAT or REPRO. The catalog
wrong with the catalog entry for this cluster. If this is to be serialized to prevent its update during
happens, consult your system programmer. processing.
reporting data bases for a fix for the problem. If no fix catname
exists, contact the IBM Support Center. Provide the JCL The catalog name.
445
System Action: The CNVTCAT or REPRO command subparameters in OBJECTS parameter and rerun the
is ended. job.
Application Programmer Response: You should Source: DFSMSdfp
restrict access to the catalog during this process and
rerun the job.
IDC3606I PORTABILITY DATA SET IN ERROR
the job log for more information. Search problem Explanation: The data on the portable data set is not
reporting data bases for a fix for the problem. If no fix as was expected; specifically, the record preceding the
exists, contact the IBM Support Center. Provide the data records for the cluster or alternate index is
JCL, the SYSOUT output for the job, and all printed incorrect. Probable user error.
Source: DFSMSdfp
Detecting Module: IDCXP01 portable data set to be processed by IMPORT was
created by EXPORT, or that a portable data set to
processed by IMPORTRA was created by EXPORTRA.
IDC3602I IMPORT OF DATA SET FAILED AFTER
If the problem reoccurs, do the problem determination
DEFINE – DELETE ATTEMPTED
action.
Explanation: The cluster or alternate index being
imported was defined successfully, but an error
occurred before all the data was copied into the
newly-defined cluster or alternate index. An attempt is
being made to delete the cluster. There is a message
preceding this message in the program listing that
explains why the import failed (incorrect DD statement, Source: DFSMSdfp
I/O error on portability data set, for instance).
Detecting Module: IDCMP01, IDCRM01
For IMPORTRA, message IDC2621I follows this
message and gives the name of the failing cluster or
alternate index. IDC3607I DELETE UNSUCCESSFUL - NOT A
TEMPORARY DATA SET
System Action: For IMPORT, the command is ended.
For IMPORTRA, processing continues with the next Explanation: The deletion that was to be attempted
object on the portable data set unless an I/O error was not performed. A duplicate name was found in the
occurred on the portable data set, in which case the catalog, and the temporary export flag was not on for
command is ended. the duplicate data set or the data set was not empty.
Application Programmer Response: Consult the System Action: The command is ended.
message preceding this message in the program listing. Application Programmer Response: Change the
System Programmer Response: Search problem name, or delete the duplicate cluster if you mean to
reporting data bases for a fix for the problem. If no fix replace it.
and the SYSOUT output for the job. and the program is not in error, search problem
Detecting Module: IDXMP01, IDCRM01 and the SYSOUT output for the job.
Source: DFSMSdfp
IDC3605I INVALID OBJECTS SUBPARAMETER
FOR ICF CATALOG Detecting Module: IDCMP01
Explanation: The NEWNAME or KEYRANGES

parameters, has been specified as a subparameter(s) of IDC3608I CONNECT FOR dsname FAILED
the OBJECTS parameter, on an IMPORT command. Explanation: This message merely identifies the name
The portable data set contains an ICF catalog for which of the user catalog which could not be connected. A
these subparameters are incorrect. message will follow to explain the catalog return code
System Action: IMPORT ends processing. received when attempting to connect the user catalog.
Application Programmer Response: Remove these In the message text:

dsname System Action: The command is ended.
The data set name.
Application Programmer Response: Specify device
System Action: The command is ended. types and volumes in the command to connect a user
catalog.
message following this message in the program listing. System Programmer Response: If the error recurs
and the SYSOUT output for the job. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCMP01
IDC3612I DELETE UNSUCCESSFUL - NOT A
CLUSTER OR AIX
IDC3609I VOLUME SPECIFICATION NEEDED
FOR dsname Explanation: An attempt was made to delete the
duplicate entry because catalog define of the cluster or
Explanation: Volume information could not be found
alternate index being imported failed due to the
on the portable data set or in the IMPORT command.
existence of a duplicate name in the catalog. A locate
You are probably trying to import a portable data set
performed on the name revealed that the entry was not
from a system using the first release of access method
a cluster or alternate index.
services (OS/VS2 Release 2, OS/VS2 Release 1.6,
OS/VS1 Release 2, or DOS/VS Release 29). System Action: The command is ended.
In the message text: Application Programmer Response: Use the
NEWNAME parameter to change the name of the
dsname
cluster or alternate index you are attempting to import.
The data set name.
Do a LISTCAT to see what you really have; what you
System Action: The command is ended. are trying to import has a conflicting name in the
catalog.
Application Programmer Response: If the portable
data set was created with the EXPORT PERMANENT System Programmer Response: If the error recurs
option on a system using the first release of access and the program is not in error, search problem
method services (as listed above), you must specify reporting data bases for a fix for the problem. If no fix
volume information by using the OBJECTS parameter of exists, contact the IBM Support Center. Provide the JCL
the IMPORT command. If you specify the cluster name and the SYSOUT output for the job.
in the entryname subparameter of the OBJECTS
Source: DFSMSdfp
parameter, the volume information will be propagated to
the data component and, for a key-sequenced cluster, it Detecting Module: IDCMP01
will be propagated to the index component. Volume
information may be specified separately for the data and
IDC3613I ERROR ENCOUNTERED OPENING
index components by repeating the OBJECTS
PORTABILITY DATA SET
parameter list, which will override any cluster
specification. Explanation: The portability data set could not be
opened.
and the program is not in error, search problem System Action: The command is ended.
exists, contact the IBM Support Center. Provide the JCL Application Programmer Response: None. The
and the SYSOUT output for the job. preceding message in the listing explains why the entry
data set was not opened.
Source: DFSMSdfp
Detecting Module: IDCMP01, IDCRM01 and the program is not in error, look at the messages in
the job log for more information. search problem
IDC3610I SPECIFICATION OF DEVICE TYPES,
VOLUMES REQUIRED FOR CONNECT
Explanation: When connecting a user catalog, the
Source: DFSMSdfp
DEVICETYPES and VOLUMES parameters, as well as
the catalog name, are required. Detecting Module: IDCMP01, IDCRM01
447
(d) The maximum record size of the data set being
IDC3614I INVALID NAME IN OBJECTS
imported into is less than that of the data set
PARAMETER: obj
exported.
Explanation: The name specified in the OBJECT
System Action: IMPORT processing is ended.
parameter in the IMPORT command does not match
any of the object names for the VSAM data set being Application Programmer Response: Delete and
imported. redefine the predefined data set with proper attributes.
Then rerun the job.
Source: DFSMSdfp
obj The specified object.
IDC3619I ALTER RENAME FOR IMPORTRA
object name.
FAILED
Explanation: During processing of an IMPORTRA
command that specified the OUTFILE parameter, the
ALTER operation failed in an attempt to rename the
object being imported. Normally, this command alters
the name of each VSAM object it defines so it can be
Source: DFSMSdfp opened for loading. The name is changed to the name
specified in the JCL, the data set is loaded, and then
the name is changed back to the original name.
The reason for the failure in ALTER processing is given
IDC3615I DSNAME ON THE OUTFILE JCL
in a preceding message. Message IDC2621I follows this
STATEMENT INCORRECT
message. It gives the real name of the failing object.
Explanation: The cluster or alternate index name of
System Action: Processing of the IMPORTRA
the imported data set does not match the data set name
command is ended.
specified in the JCL statement identified by the
OUTFILE parameter. The data set name in the JCL Application Programmer Response: Determine the
statement must be the same as the object being reason for the failure of the ALTER, correct the problem,
imported or a path over it. and rerun the job.
System Action: Processing for the command is System Programmer Response: If the error recurs
ended. and the program is not in error, search problem
Application Programmer Response: Correct the data
set name specification in the JCL. Note that if the
NEWNAME parameter is specified, the specified data
set name must be that name specified in this parameter. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCRM01
IDC3624I UNABLE TO OBTAIN OUTPUT DATA
SET NAME
IDC3617I ATTRIBUTES OF PREDEFINED ENTRY
INCOMPATIBLE WITH THOSE Explanation: IMPORTRA was unable to obtain the
EXPORTED data set name from the OUTFILE JCL statement. This
is probably due to an error in the JCL statement.
Explanation: The control interval size of the data set
being imported into is not equal to the size of the data System Action: Processing is ended.
set exported. The data set being imported into is not
consistent with that one which previously exported and
statement. Ensure that it contains a data set name,
now being imported. One of the following things is
volume, unit, DISP=OLD, and the AMP=‘AMORG’
wrong:
parameter.
(a) The relative key positions are not equal.
(b) The data sets are not of the same type (KSDS, and the program is not in error, search problem
RRDS, ESDS, and LDS). reporting data bases for a fix for the problem. If no fix
(c) The key lengths are not the same.

Source: DFSMSdfp
IDC3629I THE PORTABILITY DATA SET FORMAT
Detecting Module: IDCRM01 IS INVALID – CI MODE NOT
SUPPORTED
IDC3625I ‘INTOEMPTY’ KEY WORD Explanation: The portability data set format is control
{REQUIRED|NEEDED TO IMPORT INTO interval (CI) mode which is not supported on this
AN EMPTY DATA SET} operating system.
Explanation: A duplicately named empty data set was System Action: The IMPORT command is ended.
encountered while attempting to perform the import. The
Application Programmer Response: The portability
loading of this data set with the data of the portable
data set must be created with record mode for it to be
data set was not allowed to occur because the user did
supported on this system.
not specify the INTOEMPTY key word. As a security
precaution, the system does not allow imports into an Source: DFSMSdfp
empty data set unless the INTOEMPTY key word has
Detecting Module: IDCMP01, IDCRM01
been specified.
IDC3633I SCANNING ERROR ON OS CATALOG
Application Programmer Response: If you own an WHILE PROCESSING ‘xxx’ INDEX
empty data set into which you have planned to import,
Explanation: An error occurred while scanning the OS
rerun the job and specify the INTOEMPTY key word. If
catalog. Processing was at the indicated index.
not, determine who owns the existing empty data set
and resolve the conflict in usage of this data set name In the message text:
to insure proper protection for your data.
xxx The indicated index.
and the program is not in error, search problem System Action: Conversion is ended.
reporting data bases for a fix for the problem. If no fix Application Programmer Response: Verify that the
exists, contact the IBM Support Center. Provide the JCL OS catalog being converted is valid by listing the OS
and the SYSOUT output for the job. catalog using IEHLIST. If the catalog appears valid,
Source: DFSMSdfp rerun the job with a PARM command as follows:
(PARM TEST (FULL((CCVE,1,1), (CCIE,1,1), (CCSE,1,1))))
This will produce a SNAP dump at the error point.
IDC3628I DUMMY NAME REMAINS IN CATALOG
Explanation: IMPORTRA has renamed a cluster or and the program is not in error, look at the messages in
alternate index to the dummy name specified by the the job log for more information. Search problem
DSN parameter on the OUTFILE DD statement. The reporting data bases for a fix for the problem. If no fix
dummy name cannot be renamed to the real name and exists, contact the IBM Support Center. Provide the JCL
the cluster or alternate index remains in the catalog with and the SYSOUT output for the job.
the dummy name. The reason for the failure is given in
Source: DFSMSdfp
a preceding message. Message IDC2621I also
precedes this message. It gives the real name of the Detecting Module: IDCCC01
failing cluster or alternate index.
System Action: The command ends. IDC3641I dsname NOT A BASE CLUSTER
Application Programmer Response: Delete the Explanation: The data set is not a base cluster or a
cluster or alternate index using the dummy name in the path over a base cluster. The entry name was specified
DELETE command. Correct any other error conditions in job control identified via (1) the INFILE dname
as indicated by previous messages and rerun the job. subparameter or (2) the INDATASET dsname
subparameter. The INFILE or INDATASET data set must
be a defined, non-empty base cluster or a path over a
base cluster.
exists, contact the IBM Support Center. Provide the JCL In the message text:
dsname
Source: DFSMSdfp The data set name.
Detecting Module: IDCRM01 System Action: Processing is ended for the entire
BLDINDEX command.
449
Application Programmer Response: The data set
IDC3683I volser PLUS COUNT EXCEEDS
name in the job control identified via the INFILE
MAXIMUM VOLUME SERIAL NUMBER
subparameter or the data set name in the INDATASET
subparameter must be corrected to be that of a defined, Explanation: The number of volumes to be created,
non-empty base cluster or a path over a base cluster. added to the specified volume serial number (volser),
Then resubmit the job. exceeds the maximum value of 999999.
exists, contact the IBM Support Center. Provide the JCL System Action: Command ends normally.
Application Programmer Response: Specify a
Source: DFSMSdfp volume serial number with a lower number or request
less volumes to be created and rerun the command.
Source: DFSMSdfp
IDC3643I dsname IS EMPTY Detecting Module: IDCCV01
Explanation: The base cluster contains no records. In
order to build an alternate index, the base cluster must IDC3691I VOLUME ser LABEL NOT REBUILT
contain at least one record.
Explanation: The rewriting of the new volume label
In the message text: failed. Either the volume is specified as READONLY or
an I/O error occurred when writing the label.
dsname
The data set name. In the message text:
System Action: BLDINDEX processing is ended. ser The volume serial number.
Application Programmer Response: The base System Action: The command ends. The return code
cluster must be loaded via a user program (alternatively, is 12.
the access method services REPRO command may be
used) with at least one record. Then resubmit the job. Application Programmer Response: Rerun the
command or take the Problem Determination actions.
reporting data bases for a fix for the problem. If no fix Detecting Module: IDCMV01
IDC3692I VTOC HEAD ADDRESS CANNOT
Source: DFSMSdfp EXCEED X'0012'
Detecting Module: IDCBI01 Explanation: The VTOC head address specified is too
large; it cannot exceed X'0012'.
IDC3682I FINAL CHARACTER(S) IN volser NOT System Action: The command ends. The return code
NUMERIC is 12.
Explanation: A character in the volume serial number Application Programmer Response: Specify a VTOC
is not a numeric value and cannot be incremented to head address not exceeding X‘0012’ and rerun the
created new volume serial numbers. command.
volser The volume serial number. Detecting Module: IDCMV01
System Action: Function ends normally.
Application Programmer Response: Specify a IDC3700I ** LATEST COPY RECORD CANNOT
beginning volume serial number with adequate number BE RETRIEVED FROM INVENTORY
of numeric characters and rerun the command. Explanation: An attempt to access the record for the
Source: DFSMSdfp latest copy recorded in the Inventory data set failed.
The command checks if the latest copy is incomplete
Detecting Module: IDCCV01 due to a previous copy failure; the cartridges will be
reused if an incomplete copy exists. See the preceding
message for the error condition.

System Action: The command ends with an error v Run the REMOVEVR command to delete the copy
message. volume record from the Inventory data set if both
cartridges are lost.
problem as indicated in the preceding message and v Reenter the missing cartridges in the Mass Storage
rerun the command. Facility (MSF) while the Mass Storage Volume
Control (MSVC) is enabled.
reporting data bases for a fix for the problem. If no fix Detecting Module: IDCCO01
output and output data sets related to the problem. IDC3706I ** COPY TO CARTRIDGES csn1 csn2 IS
INCOMPLETE
Source: DFSMSdfp
Explanation: The copy operation to the copy volume
Detecting Module: IDCCO01 failed. The copy volume is marked incomplete in the
Inventory data set and will be reused by the COPYV
IDC3701I ** OLDEST BACKUP COPY RECORD command when the command is run again. The
CANNOT BE RETRIEVED FROM cartridges of the copy volume were selected either by
INVENTORY the user, by the Mass Storage Control (MSC) at
random, or by the command using an existing copy
Explanation: An attempt to access the record for the volume. See the preceding message for further
oldest backup copy volume recorded in the Inventory explanation of the error.
data set failed. The cartridges of the oldest backup copy
are to be either reused or scratched. See the preceding In the message text:
message for the error condition. csn1
System Action: This command ends with an error csn2 The cartridge serial numbers.
message.
Application Programmer Response: Before
Application Programmer Response: Correct the rerunning the COPYV command correct the problem as
problem as indicated in the preceding message and indicated in the preceding message.
rerun the command.
Rerun COPYV to complete the copy operation to the
System Programmer Response: If the error recurs incomplete copy volume (COPYV will reuse the
and the program is not in error, search problem cartridges of the incomplete copy volume for the new
reporting data bases for a fix for the problem. If no fix copy) or run SCRATCHV to scratch the incomplete copy
exists, contact the IBM Support Center. Provide the volume before rerunning the COPYV command.
output and output data sets related to the problem. If COPYV ends without indicating the status of the copy
operations, LISTMSVI can be run the determine
Source: DFSMSdfp whether the volume is flagged for recovery purposes. If
Detecting Module: IDCCO01 the incomplete copy flag is set in the copy volume
record, LISTMSVI not only lists the standard information
for the volume but also highlights the volume report with
IDC3702I TARGET COPY yyddd CANNOT BE a note that a copy operation failed for the preceding
USED copy volume.
Explanation: The command selected the cartridges of System Programmer Response:
an existing copy volume created on the date indicated
for reuse but the cartridges cannot be used. The If the error recurs and the program is not in error, look
following message explains why the designated copy at the messages in the job log for more information.
volume cannot be used. Search problem reporting data bases for a fix for the
In the message text: Center. Provide the JCL, the SYSOUT output for the
yyddd The date in year and days. job, and all printed output and output data sets related
to the problem.
System Action: The command ends with an error
message. Source: DFSMSdfp
Application Programmer Response: Before Detecting Module: IDCCO01

rerunning the COPYV command, either:
v Run the SCRATCHV command to scratch the
remaining cartridge of this unusable copy and delete
the record from the Inventory data set.
451
IDC3708I ** COPY VOLUME COULD NOT BE
CREATED volser The volume serial number.
Explanation: No existing copy volumes were eligible System Action: The command ends with an error
for reuse for this copy request. An attempt to create a message.
new target volume from scratch cartridges failed. A new
copy volume was not created. See the preceding Application Programmer Response: Rerun the
message for further explanation of the problem. command requesting a specific nonbackup copy volume
if any exist.
message. System Programmer Response: If the error recurs
Application Programmer Response: Correct the reporting data bases for a fix for the problem. If no fix
error condition as indicated in the preceding message exists, contact the IBM Support Center. Provide the
and rerun the command. JCL, the SYSOUT output for the job, and all printed
exists, contact the IBM Support Center. Provide the Detecting Module: IDCRV01
output and output data sets related to the problem. IDC3712I ** LATEST BACKUP COPY RECORD
Source: DFSMSdfp CANNOT BE RETRIEVED FROM
INVENTORY
Explanation: The recovery operation requires the
latest backup copy, but the record for that copy volume
IDC3709I ** COPY TO CARTRIDGES csn1 csn2 could not be retrieved from the Inventory data set. See
NOT PERFORMED the preceding message for further explanation of the
error.
Explanation: The Mass Storage Controller (MSC)
could not perform the copy operation to the copy System Action: The command ends with an error
volume. The copy volume remains usable because the message.
original data on the volume was not destaged. See the
preceding message for further explanation of the error. Application Programmer Response: Before
rerunning the command correct the error as indicated in
In the message text: the preceding message or specify another copy to be
used in the recovery operation.
csn1
System Action: The command ends with an error reporting data bases for a fix for the problem. If no fix
message. exists, contact the IBM Support Center. Provide the
error as indicated in the preceding message and rerun
the command. Source: DFSMSdfp
System Programmer Response: If the error recurs Detecting Module: IDCRV01
IDC3720I NEW SERIAL NO. REQUIRED TO
ACTIVATE A COPY OR DUPLICATE
VOLUME
Explanation: A copy or duplicate volume cannot be
Source: DFSMSdfp
activated unless the volume is relabeled with a unique
Detecting Module: IDCCO01 volume serial number.
System Action: The command ends with a message.
IDC3710I ** NO BACKUP COPY VOLUMES EXIST
Application Programmer Response: Rerun the
FOR VOLUME volser
command specifying the NEWSERIAL parameter and a
Explanation: The designated volume has no backup unique volume serial number that can be used to
copy. The option to restore from the latest backup relabel the copy or duplicate volume in order to activate
cannot be satisfied. See the preceding message for it.
further explanation of the problem.

System Programmer Response: If the error recurs command to store the volume, but do not request the
and the program is not in error, search problem volume serial number be changed. If the volume must
reporting data bases for a fix for the problem. If no fix be renamed, run the SCRATCHV command to scratch
exists, contact the IBM Support Center. Provide the all copies before requesting STOREV to rename and
JCL, the SYSOUT output for the job, and all printed store the volume.
IDC3721I VOLUME volser IS ALREADY ACTIVE output and output data sets related to the problem.
Explanation: The designated volume is already active. Source: DFSMSdfp
In the message text: Detecting Module: IDCSR01
IDC3732I ** VOLUME volser COULD NOT BE
System Action: The command ends with a message. MADE INACTIVE
Application Programmer Response: None. Explanation: The status of the volume could not be
Source: DFSMSdfp changed from active to inactive. See the preceding
message for further explanation of the error.
IDC3726I UNABLE TO REPLACE THE BASE volser The volume serial number.
VOLUMES System Action: Processing continues.
Explanation: The REPLACEVOLUME key word Application Programmer Response: Correct the
parameter is specified, but the base volume cartridges error as identified in the preceding message.
are not reassigned or are in the Mass Storage Facility.
Rerun STOREV or run MODIFYV to either backout or
System Action: The request is bypassed, but an retry the rename operation.
attempt is made to fulfill the remaining requests.
If the STOREV or MODIFYV commands are run to
Application Programmer Response: The request recover from a rename failure, the DD statement for the
can be modified and rerun. A new serial number volume is required and must specify deferred mounting.
(NEWSERIAL) must be supplied without the
REPLACEVOLUME key word parameter. The same The values specified for the VOLUME and NEWSERIAL
request can be rerun if the base volume is first ejected parameters depend upon how the volume record is
or nullified. recorded in the Inventory data set. If the cartridge labels
have been updated, the volume record will be identified
System Programmer Response: If the error recurs by the new volume serial number. For the VOLUME
and the program is not in error, search problem parameter, specify the volume serial number as
reporting data bases for a fix for the problem. If no fix recorded in the cartridge labels and the volume record.
exists, contact the IBM Support Center. Provide all For the NEWSERIAL parameter, specify the desired
printed output and output data sets related to the volume serial number. Note that the security check for
problem. non-VSAM status and password protected data sets is
Source: DFSMSdfp bypassed only if the NEWSERIAL parameter specifies
the same volume serial number as recorded in the
Detecting Module: IDCAV01 Inventory data set for the volume label. This allows the
original volume serial number of a VSAM volume to be
IDC3730I VOLUME volser CANNOT BE restored if the volume is left partially renamed.
RELABELED; COPIES EXIST If STOREV ends without indicating the status of the
Explanation: The volume serial number of the volume rename operation, LISTMSVI can be run to determine
cannot be changed because copies of the volume exist. whether the volume is flagged for recovery purposes. If
the mismatch flag is set in the volume record,
In the message text: LISTMSVI not only lists the standard information for the
volser The volume serial number. volume but also highlights the volume report with a note
that a rename operation failed for the preceding volume
System Action: The command ends with an error and that serial number ’nnnnnn’ is recorded in the
message. volume label of the volume.
453
Source: DFSMSdfp To recover from a MODIFYV rename failure 1) run
ADDV to activate the volume if the volume is merely
Detecting Module: IDCSR01
inactive and has no volume serial mismatch
condition, or 2) run ADDV to both activate the volume
IDC3734I ** VOLUME LABEL COULD NOT BE and complete the rename operation if the volume is
RESTORED TO ORIGINAL STATUS both inactive and has a volume serial mismatch
condition, or 3) rerun MODIFYV to complete or retry
Explanation: Following a failure to deactivate the the rename operation if the volume is active but has
volume and change the volume serial number in the a mismatch condition, or 4) run STOREV to complete
cartridge labels, an attempt to restore the volume label or retry the rename operation if the volume is active
to its original status also failed. A volume and if a duplicate volume serial number is desired as
serial-mismatch exists between the volume label and result of the rename.
the cartridge labels of the cartridges assigned to the
Mass Storage Volume. A flag indicating the mismatch is For the DD statement requirements, the proper
set in the Inventory data set for the volume. See the VOLUME and NEWSERIAL parameter values, and
preceding message for further explanation of the use of LISTMSVI, refer to the description above for
problem. an ADDV rename failure.
v If a Rename Operation Failed for STOREV
message. Rerun STOREV or run MODIFYV to either backout or
retry the rename operation.
Application Programmer Response: Correct the For the DD statement requirements, the proper
error as identified in the preceding message. VOLUME and NEWSERIAL parameter values, and
v If a Rename Operation Failed for ADDV use of LISTMSVI, refer to the description above for
Run ADDV to backout or retry the rename operation an ADDV rename failure.
if the volume is inactive. If the volume is active, run System Programmer Response: If the error recurs
MODIFYV or STOREV to either backout or retry the and the program is not in error, look at the messages in
rename operation. the job log for more information. Search problem
If the ADDV, MODIFYV, or STOREV commands are reporting data bases for a fix for the problem. If no fix
run to recover from a rename failure, a DD statement exists, contact the IBM Support Center. Provide the
for the volume is required and must specify deferred JCL, the SYSOUT output for the job, and all printed
mounting. output and output data sets related to the problem.
The values specified for the VOLUME and Source: DFSMSdfp
volume record is recorded in the Inventory data set. If Detecting Module: IDCSR01
the cartridge labels have been updated, the volume
IDC3736I ddname MUST NOT BE ALLOCATED
number. For the VOLUME parameter, specify the
TO SHARED OR SHARED U.P. UNITS
volume serial number as recorded in the cartridge
labels and the volume record. For the NEWSERIAL Explanation: CONVERTV can only use non-shareable
parameter, specify the desired volume serial number. spindles, and cannot be a uniprocessor unit.
Note that the security check for non-VSAM status
and password protected data sets is bypassed only if
the NEWSERIAL parameter specifies the same ddname
volume serial number as recorded in the Inventory The DD name.
data set for the volume label. This allows the original
volume serial number of a VSAM volume to be System Action: The command is ended.
restored if the volume is left partially renamed. Application Programmer Response: See your
If ADDV, MODIFYV, or STOREV ends without system programmer to determine if a shared spindle
indicating the status of the rename operation, was used or if the system was sysgened for
LISTMSVI can be run to determine whether the uniprocessor operations.
volume is flagged for recovery purposes. If the
Source: DFSMSdfp
mismatch flag is set in the volume record, LISTMSVI
not only lists the standard information for the volume
but also highlights the volume report with a note that IDC3738I ** DATA SETS NOT RECATALOGED IN
a rename operation failed for the preceding volume VSAM CATALOG
and that serial number ’nnnnnn’ is recorded in the
Explanation: An error occurred which prevented all
volume label of the volume.
the data sets in the VSAM owning catalog from being
v If a Rename Operation Failed for MODIFYV recataloged. A preceding message explains the error.
System Action: The command ends normally. If the

target volume is a 3336 Model 1 Disk Pack, use Device System Programmer Response: If the error recurs
Support Facilities to reformat the volume to meet the and the program is not in error, look at the messages in
empty VTOC requirement of the CONVERTV command. the job log for more information. Search problem
error and rerun the command.
System Programmer Response: Enter the access output and output data sets related to the problem.
Source: DFSMSdfp
catalog. If the error recurs and the program is not in Detecting Module: IDCCN01
error, search problem reporting data bases for a fix for
the problem. If no fix exists, contact the IBM Support
IDC3741I RECATALOG OPTION INVALID FOR
VSAM VOLUME
to the problem. Explanation: The source volume is owned by a VSAM
catalog and the volume and any VSAM data sets on the
Source: DFSMSdfp
volume must be recataloged. Therefore, NONE is an
Detecting Module: IDCCN01 incorrect option.
IDC3739I FROM AND TO UNITS ARE THE SAME
DEVICE TYPE
VSAMCATALOG option on the RECATALOG parameter
Explanation: The device type specified in the UNIT or omit the control statement. Rerun the command.
parameter of the FROMFILE DD statement is the same
as the device type specified in the UNIT parameter of
the TOFILE DD statement.
System Action: The command ends normally with an exists, contact the IBM Support Center. Provide the
error message. JCL, the SYSOUT output for the job, and all printed
Application Programmer Response: Either correct
the UNIT parameter and rerun the command or if you Source: DFSMSdfp
want to move data between two volumes of the same
type, use the IEHMOVE utility program.
IDC3744I JOBCAT/STEPCAT MUST NOT BE
SPECIFIED FOR VSAM CATALOG ON
VOLUME
exists, contact the IBM Support Center. Provide the Explanation: A JOBCAT or STEPCAT DD statement
JCL, the SYSOUT output for the job, and all printed was used to allocate the VSAM user catalog on the
output and output data sets related to the problem. volume to be processed. If the VSAM user catalog is on
the volume being processed, the user catalog must not
Source: DFSMSdfp
be open as a result of the use of a JOBCAT or
Detecting Module: IDCCN01 STEPCAT DD statement.
IDC3740I MULTIPLE VOLUME SERIAL NUMBERS
Application Programmer Response: Use a standard
ASSOCIATED WITH FILE ddname
DD statement ddname rather than JOBCAT or
Explanation: CONVERTV will only convert a single STEPCAT to allocate the VSAM user catalog, and
volume at a time. The specified ddname has more than supply that ddname in the CATALOG parameter. Rerun
one volume associated with it. the command. In VS2 you can omit the DD statement
and only specify the name of the catalog on the
CATALOG parameter.
ddname
The specified DD name.
System Action: The command ends normally. the job log for more information. Search problem
Application Programmer Response: Specify only exists, contact the IBM Support Center. Provide the
one volume serial on the DD statement or supply a JCL, the SYSOUT output for the job, and all printed
FROMVOLUME statement for the volume to be output and output data sets related to the problem.
converted. Rerun the command.
455
Source: DFSMSdfp is not created or modified. Control is returned to the
user with a condition code of 12.
Detecting Module: IDCCN01, IDCSR01
correct combination of parameters and rerun the job.
IDC3745I DD NAME MUST BE SPECIFIED FOR
VSAM USER CATALOG ON VOLUME Source: DFSMSdfp
Explanation: No ddname was specified for the VSAM Detecting Module: IDCGR01, IDCMG01
CATALOG residing on the volume being processed
preventing the catalog from being opened.
IDC3820I ** TABLES COULD NOT BE COPIED TO
System Action: Command ends normally. WORK DATA SET
Application Programmer Response: Supply a DD Explanation: An error code was returned from the
statement for the catalog that owns the volume. The DD request to copy the MSC tables to the work data set. A
statement name cannot be JOBCAT or STEPCAT. preceding message explains the reason.
Specify the name of the DD statement which allocates
System Action: The command preceding ends
the catalog in the CATALOG parameter. Rerun the
normally.
command.
preceding message to determine the exact error.
Correct the error and rerun the command.
exists, contact the IBM Support Center. Provide the System Programmer Response: If the error recurs
JCL, the SYSOUT output for the job, and all printed and the program is not in error, search problem
output and output data sets related to the problem. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
Detecting Module: IDCCN01, IDCSR01 output and output data sets related to the problem.
Source: DFSMSdfp
IDC3770I VOLUME volser ACTIVE
Detecting Module: IDCLM01
Explanation: The volume is active and cannot be
ejected.
IDC3822I MSF NOT AVAILABLE
Explanation: The Mass Storage Facility (MSF) does
volser The volume serial number. not have a staging adapter assigned to it in the Mass
Storage Control (MSC) tables and cannot be considered
to exist for system use.
message.
STOREV command to both deactivate and eject the Application Programmer Response: Specify a valid
volume. MSF on the command and rerun the command.
and the program is not in error, search problem and the program is not in error, search problem
JCL, the SYSOUT output for the job, and all printed JCL, the SYSOUT output for the job, and all printed
output and output data sets related to the problem. output and output data sets related to the problem.
Detecting Module: IDCEV01 Detecting Module: IDCAU01, IDCLM01
IDC3802I INVALID SIS PARAMETER IDC3835I AN MSVI ERROR WAS DETECTED

WHILE PROCESSING CART (csn)
Explanation: Either an incorrect combination of
parameters was specified for the system-initiated Explanation: A Mass Storage Volume Inventory
scratch function, or incorrect subparameters were (MSVI) error occurred because either one or both
specified with the SIS parameter in the CREATEG or cartridge serial numbers of the volume record that was
MODIFYG command. being read were not properly initialized.
System Action: The request is ended and the group In the message text:

csn The cartridge serial number. Detecting Module: IDCTR01
IDC3850I THE NUMBER OF SECONDS IN THE
Application Programmer Response: The problem
LRU CLOCK IS INVALID
was probably caused by a system failure during the
CREATEV command. Issue the SCRATCHV command Explanation: The number of seconds in the LRU clock
to scratch the incomplete mass storage volume. Rerun (LRUCLOCK parameter) is incorrect. The only valid
the command. numbers are 128, 256, 512, 1024, 2048, 4096, 8192,
and 16384.
and the program is not in error, search problem System Action: The command ends normally. No
reporting data bases for a fix for the problem. If no fix tuning parameters have been changed.
JCL, the SYSOUT output for the job, all printed output
LRUCLOCK parameter and rerun the command.
and output data sets related to the problem, and the
program listing for the job. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCTU01
IDC3842I ORDER OF TRACE AREAS COULD IDC3851I LOWER VALUE MUST BE LESS THAN
NOT BE DETERMINED - NO DATA HIGHER VALUE FOR ACTIVEPAGES
DUMPED
Explanation: On the ACTIVEPAGES parameter, the
Explanation: An attempt was made to dump both lower number of pages is a number greater than or
trace areas, but the first trace area could not be equal to the higher number of pages. The lower number
determined. Therefore, no trace data was dumped. The must be less than the higher number.
programmer will have to submit individual X and/or Y
trace dump requests. System Action: The command ends normally. No
tuning parameters have been changed.
Application Programmer Response: Rerun the ACTIVEPAGES parameter and rerun the command.
TRACE command specifying either trace area X or
trace area Y. Source: DFSMSdfp
System Programmer Response: If the error recurs Detecting Module: IDCTU01

reporting data bases for a fix for the problem. If no fix IDC3852I TOTAL OF UNITS IN LRUGROUPS
exists, contact the IBM Support Center. Provide the MUST BE LESS THAN OR EQUAL TO
JCL, the SYSOUT output for the job, and all printed 16
Explanation: When the LRU clock units for all groups
Source: DFSMSdfp are added together they exceed the maximum (16).
Detecting Module: IDCTR01 System Action: The command ends normally. No
tuning parameters have been changed.
IDC3844I BLOCKSIZE OF OUT DATA SET IS NOT Application Programmer Response: Correct the
A MULTIPLE OF 264. LRUGROUPS parameter (which specifies the number of
Explanation: Because trace records are 264 bytes LRU clock units) and rerun the command.
long, they must be blocked in multiplies of 264. That is, Source: DFSMSdfp
the blocksize specified for the Output Data set must be
a multiple of 264. Detecting Module: IDCTU01
System Action: The Trace Utility is ended.

IDC3860I GROUP PARAMETERS CANNOT BE
Application Programmer Response: Correct the SPECIFIED FOR NONGROUPED
blocksize specification in the JCL and rerun the job. VOLUMES
System Programmer Response: If the error recurs Explanation: A request to set group level attributes for
and the program is not in error, search problem a volume that does not belong to a group is incorrect.
exists, contact the IBM Support Center. Provide the JCL System Action: The command ends with an error
and the SYSOUT output for the job. message.
Source: DFSMSdfp Application Programmer Response: Rerun the
457
command after removing the conflicting parameters that
IDC3885I VOLUME ser PERMANENTLY
specify group attributes.
RESIDENT OR RESERVED
Explanation: The volume is marked permanently
resident or reserved in the unit control block (UCB).
Therefore, this volume cannot be demounted. The
volume described by the volume serial (ser) needs to be
demounted so that a MSC function can be performed or
to enable the proper volume to be mounted on the unit.
Source: DFSMSdfp
Detecting Module: IDCMV01
IDC3861I VOLUME ser LABEL NOT REBUILT
Explanation: The rewriting of the new volume label
correct volume serial number was specified on the DD
failed. Either the volume is specified as READONLY or
statement for the FILE parameter. If the correct volume
an I/O error occurred when writing the label.
serial was specified, you cannot run the command while
In the message text: that volume is permanently resident or reserved.
ser The volume serial number. System Programmer Response: If the error recurs
System Action: The command ends. The return code the job log for more information. Search problem
is 12. reporting data bases for a fix for the problem. If no fix
Application Programmer Response: Rerun the exists, contact the IBM Support Center. Provide the
command or take the Problem Determination actions. JCL, the SYSOUT output for the job, and all printed
Source: DFSMSdfp
Source: DFSMSdfp
IDC3862I VTOC HEAD ADDRESS CANNOT

EXCEED X'0012' IDC3897I CONFLICT EXISTS BETWEEN
ENTRYNAME AND DD SPECIFIED ON
Explanation: The VTOC head address specified is too DATA SET NAME
large; it may not exceed X'0012'.
Explanation: Conflict between the entryname
System Action: The command ends. The return code specified on DELETE command and data set name
is 12. specified on the file parameter referenced DD
Application Programmer Response: Specify a VTOC statement.
head address not exceeding X‘0012’ and rerun the System Action: The system processing continues.
command.
Operator Response: Correct the data set name
Source: DFSMSdfp specified on the file parameter referenced DD
statement, if incorrectly specified. Or, correct the
IDC3883I ** ERROR COUNT EXCEEDED UPPER entryname in the entryname parameter on the DELETE
LIMIT, FUNCTION TERMINATED command, if incorrectly specified.
Explanation: A LISTCRA command encountered more System Programmer Response: Determine the
than 50 I/O errors. reason for the failure of the DELETE command; correct
the problem and rerun the job.
System Action: Processing of the LISTCRA command
is ended. Source: DFSMSdfp
Application Programmer Response: See previous

messages to determine the cause of the I/O errors. IDC3900I PUTGET ERROR CODE IS return-code
Correct the problem, and rerun the job. Explanation: The PUTGET macro instruction failed.
Detecting Module: IDCLR01 return-code The return code, as follows:
Code Explanation
8 The PUTGET service routine
did not complete. An

attention interrupt occurred
IDC3901I ERROR QUALIFYING dsname
during the processing of
PUTGET, and the attention Explanation: The Time Sharing Option/Extensions
handler turned on the (TSO/E) default service routine failed to qualify the data
completion bit in the set indicated.
communications ECB.
12 No prompting was allowed on
dsname
a PROMPT request. Either
The data set name.
the user at the terminal
requested no prompting with System Action: The request is ended.
the PROFILE command, or
the current source of input is Application Programmer Response: An associated
an in-storage list. message, IDC3902I directs the user in how to correct
this error.
12 A line could not be obtained
after a MODE request. A System Programmer Response: If the error recurs
chain of second level and the program is not in error, look at the messages in
informational messages the job log for more information. Search problem
exists, and the current stack reporting data bases for a fix for the problem. If no fix
element is non-terminal, but exists, contact the IBM Support Center. Provide the JCL
the terminal user did not and the SYSOUT output for the job.
request PAUSE processing Source: DFSMSdfp
with the PROFILE command.
The messages are therefore Detecting Module: IDCSA02
not available to him.
16 The NOWAIT option was IDC3902I ** DEFAULT SERVICE ROUTINE
specified for TPUT and no ERROR CODE return-code, LOCATE
line was put out or received. ERROR CODE cde
20 The NOWAIT option was Explanation: This message contains the return code
specified for TGET and no information required to correct the error indicated in
line was received. associated message IDC3901I. The LOCATE error code
is part of VSAM Catalog Management. Refer to
24 Incorrect parameters were message IDC3009I for the return codes as well as the
supplied to the PUTGET possible system and programmer responses.
service routine.
28 A conditional GETMAIN was
issued by PUTGET for output cde The LOCATE error code.
buffers and there was not rc The possible system and programmer
sufficient space to satisfy the responses for the default service routine error
request. conditions along with the return code, as
32 The terminal has been follows:
disconnected. Code Explanation
System Action: The command is ended. 4 Return code from PUTLINE or
Application Programmer Response: Correct the PUTGET was not zero.
error based on the return code information and rerun 8 Data set name was longer than 44
the job. bytes.
System Programmer Response: If the error recurs 12 An I/O error occurred while searching
and the program is not in error, look at the messages in the catalog, the catalog data set was
the job log for more information. Search problem not available or the data set name
reporting data bases for a fix for the problem. If no fix was not specified correctly.
and the SYSOUT output for the job. 16 The index structure of the catalog was
not consistent with the data set name.
Source: DFSMSdfp For example, the name specified was
Detecting Module: IDCSA02 “A.B.C”, but there is a data set called
“A.B,” so there cannot be one called
“A.B.C.”
459
20 The data set name could not be found In the message text:
in the catalog.
reason-code The reason code returned by SMS
24 An attention interruption occurred
System Action: The system may end processing of
during processing of this request.
the IDCAMS command.
28 Incorrect parameters were specified.
Application Programmer Response: Refer to
32 It was necessary to prompt the user, OS/390 DFSMSdfp Diagnosis Reference for an
but the caller specified that the user explanation of the SMS reason code.
should not be interrupted.
Source: DFSMSdfp
36 Not enough qualifiers were specified
for the data set name. For example,
IDC3933I ATTACH RETURN CODE WAS
the name specified was “A.B,” but the
return-code
catalog contains an entry for “A.B.C.”
Explanation: An ATTACH SVC returned the specified
code due to an error during the ATTACH operation.
Application Programmer Response: The response
depends on the return codes, rc and cde. Possible
responses for return code rc follow: return-code The specified return code.
Code Response System Action: The system ends processing of the
command.
4 Make sure the user is still logged on to the
system. Application Programmer Response: None.
8 Correct the data set name. Source: DFSMSdfp
12 Examine the data set name for syntax errors, Detecting Module: IDCSA11
for example, embedded punctuation marks.
Check the CVOL index structures to be sure
CVOLs are properly linked. If an I/O error IDC3936I CVAFFILT ERROR RETURN CODE IS
occurred, it may be necessary to rebuild the return-code - REASON CODE IS
catalog. reason-code
16 Respecify the data set name or recatalog the Explanation: During DIAGNOSE processing, an error
data set. occurred in CVAFFILT.
20 Respecify the data set name or recatalog the In the message text:
data set. return-code The return code.
24 None. reason-code The reason code.
28 Check to be sure the parameter list for System Action: The system ends processing of the
IKJEHDEF was not improperly modified. command.
32 None. Application Programmer Response: None.
36 Respecify the data set name. Source: DFSMSdfp
System Programmer Response: If the error recurs Detecting Module: IDCSA11
reporting data bases for a fix for the problem. If no fix IDC4227I AN ‘ELSE’ COMMAND APPEARS
exists, contact the IBM Support Center. Provide the JCL IMPROPERLY
and the SYSOUT output for the job. Explanation: An ELSE modal command appears
Source: DFSMSdfp without a matching IF-THEN modal command. Modal
command continuation may be incorrect.
System Action: The remainder of the command input
stream is ignored.
SUBSYSTEM CALL FAILED. REASON Application Programmer Response: Correct the
CODE WAS reason-code usage and rerun.
Explanation: An IDCAMS command called a Storage System Programmer Response: If the error recurs
Management Subsystem (SMS) service, but the call and the program is not in error, search problem
failed. reporting data bases for a fix for the problem. If no fix

SYSOUT output for the job. SYSOUT output for the job.
Detecting Module: IDCRI01 Detecting Module: IDCRI01
IDC4228I AN ‘END’ COMMAND IS INVALID IDC4232I IMPROPER OR MISSING ‘THEN’ KEY

WORD
Explanation: An END modal command occurs without
a matching DO modal command. Explanation: The THEN portion of the IF modal
command is misspelled or missing. Modal command
continuation may be incorrect.
stream is ignored.
System Action: The remainder of the input stream is
ignored.
DO-END usage and rerun.
usage and rerun.
SYSOUT output for the job. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
Source: DFSMSdfp
IDC4229I ‘IF’ COMMAND HAS INVALID
RELATIONAL EXPRESSION
IDC4236I INPUT STREAM END-OF-FILE FOUND
Explanation: An IF modal command has an incorrect
BEFORE END-OF-COMMAND
relational expression.
Explanation: Command input stream end-of-file has
been found while scanning a command. There may be
stream is ignored.
input records missing.
System Action: The current command is not
syntax and semantic requirements of the IF command.
processed.
Correct the usage and rerun.
Application Programmer Response: Add the missing
data and rerun.
SYSOUT output for the job. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
Source: DFSMSdfp
IDC4230I ‘SET’ COMMAND HAS INVALID

IDC4237I TOO MANY LEVELS OF ‘IF’ COMMAND
ASSIGNMENT EXPRESSION
NESTING
Explanation: A SET modal command has an incorrect
Explanation: IF modal commands have been nested
assignment expression.
to a level that cannot be handled.
stream is ignored.
stream is ignored.
Application Programmer Response: Restructure the
syntax and semantic restrictions on the SET command.
modal commands to conform to the restriction of ten
Correct the usage and rerun.
levels of nesting.
461
exists, contact the IBM Support Center. Provide the and the program is not in error, look at the messages in
SYSOUT output for the job. the job log for more information. Search problem
Source: DFSMSdfp
Detecting Module: IDCRI01 and the SYSOUT output for the job.
Source: DFSMSdfp
IDC4999I UABORT CODE return-code
Explanation: This message indicates an error, which
caused the processor to abort. The code number
IDC11003I CONTROL INTERVAL nnnnnn
indicates the nature of the error. Since the error is
BYPASSED IN CRA volser
usually such that no further processor code may be run
with confidence, this message appears in the output Explanation: IGNORE was specified and an I/O error
listing by a write-to-programmer action. was encountered. The record is ignored. This message
is preceded by IDC3351I which indicates the nature of
the error.
return-code The return code, as follows:
Code Explanation
24 Text processor’s print control
nnnnnn The control interval number of the record in the
table address not set in GDT.
catalog.
28 No virtual storage available
for one of the following:
v Text processor’s translate Application Programmer Response: This may cause
table. errors to be detected in objects on the volume specified,
or objects on the volume may be totally lost without
v Initialization of the I/O
notification. Perform a LISTCAT operation of the catalog
adapter.
to determine which objects still exist after the reset
v Automatic (dynamic) operation.
storage of a module.
v Text processor dynamic
storage.
catalog.
See the in-virtual storage
trace tables to determine Source: DFSMSdfp
which is the correct condition.
32 There was a request to
access an unopened data
IDC11015I CONTROL INTERVAL nnnnnn
set.
BYPASSED IN CATALOG
36 The processor was unable to
Explanation: IGNORE was specified and an I/O error
open SYSPRINT (or
was encountered. The record is ignored. Message
whichever DD name is
IDC3351I precedes this message indicating the specific
employed to denote the
error.
processor’s standard listing
output data set). In the message text:
40 Incorrect U-macro argument nnnnnn The control interval number of the record in the
list found. catalog.
44 The processor is unable to System Action: Processing continues.
produce a dump.
Application Programmer Response: The record
56 The BLDL macro failed to noted in the catalog is inaccessible. If it contained a
find a required AMS (access corresponding reset CRA entry, the entry will be
method services) module. recovered. If it contained a non-reset CRA entry, the
entry remains inaccessible. A LISTCAT may reveal
72 An internal RESETCAT error
whether the error is of any consequence. nnnnnn is the
occurred (probable system
control interval number of the record in the catalog.
error).

entries and information about objects defined in the Source: DFSMSdfp
catalog.
Source: DFSMSdfp
Detecting Module: IDCRS06 IDC11029I SPACE MAP FOR VOLUME volser
CORRECTED
IDC11022I entryname, type CONTAINS A Explanation: The suballocated VSAM data space has
CONNECTOR TO INVALID RECORD been corrected to reflect what is on the volume. This
nnnnnn, type correction occurs if entries are deleted by RESETCAT,
or space stated as suballocated is not suballocated
Explanation: An object contains a dependency on a
(that is, the space map is incorrect on entry to
record that does not exist. The base record is noted by
RESETCAT).
name and type. The dependent record which is
incorrect is noted by its expected control interval In the message text:
number and record type. The reference to the incorrect
record is deleted. See either message IDC21024I,
IDC21025I or IDC21026I which follows. The message System Action: Processing continues.
will note the other action taken as a result of this error.
In the message text: is given for information only. It is a correction of some
state of error. The error may be specifically noted in a
entryname The base record noted by name.
preceding error message or not at all. In the latter case,
nnnnnn The control interval number of the the situation is due to space being suballocated from
record in the catalog. available suballocatable space; however, no entry can
be found which claims this space. No corrective action
type The entry type of the record. The
by the programmer is required.
value are defined under message
IDC21045I. Source: DFSMSdfp
System Action: Processing continues. Detecting Module: IDCRS03
following message (noted in the explanation) to IDC11031I UNIQUE DATA SET entryname HAS
determine what action was taken. FEWER EXTENTS THAN THE DATA
SPACE
Source: DFSMSdfp
Explanation: The unique data or index component
has less space described than the data space. No
problem exists for this data set; this message is given to
IDC11023I entryname, type, ERROR FOR inform you that space exists which is not in use. If the
ASSOCIATION [nnnnnn,] type data set is extended, this space will be used. No
corrective action is taken.
Explanation: An entry is chained to a record of a type
different than anticipated, or the object noted consists of In the message text:
incomplete set of records. If the control interval number
entryname The specified entry name.
of the expected association is not given, then no
association for that object exists in the base record; an System Action: Processing continues.
association for that type is required for the entry name
noted. Message IDC21026I follows, noting that the entry
has been deleted. Source: DFSMSdfp
In the message text: Detecting Module: IDCRS03
entryname The entry name noted.
IDC11033I dsname, volser NOT DELETED
nnnnnn The control interval number of the
record in the catalog. Explanation: A unique data set, on a volume not
being reset, has no corresponding DATA or INDEX
type The entry type of the record. The
component. The component was defined on one of the
values of are defined under message
volumes being reset, but no longer exists on that
IDC21045I.
volume.
IDC21026I.
463
dsname
IDC11041I dsname SPACE CORRECTED
The unique data set name.
Explanation: The extents in the space header for the
data space noted were not identical to the extents in the
Application Programmer Response: If the data set is corresponding Format 1 DSCB. The extents in the
no longer valid, then SCRATCH it. space header were corrected using the extents in the
Format 1 DSCB and the Format 3 DSCB if one exists.
Source: DFSMSdfp
dsname
The data set name.
IDC11036I entryname, type OUT-OF-SYNC ON
volser System Action: Processing continues.
Explanation: The data set named may have incorrect Application Programmer Response: This may be
space information. The extents occupied by the named caused by some previous system error. This message is
data set are not in conflict with any other VSAM data given for information purposes. A later message may
set or with the system; however, a self-checking field indicate whether objects were marked unusable,
failed to check. The data set itself may be all right. perhaps as a result of this condition if fewer extents
existed in the data set than the data space. Watch for
In the message text: message IDC21027I or IDC21030I.
volser The volume serial number. Source: DFSMSdfp
entryname The entry name indicated. Detecting Module: IDCRS03
type The type specified. The values of type
are defined under message IDC11042I dsname SPACE DELETED
IDC21045I.
Explanation: The space header for the data space
System Action: Processing continues. referred to a nonexistent Format 1 DSCB. The space
Application Programmer Response: List the data set header for the data space was deleted.
and ensure that it is correct and accessible. In the message text:
Detecting Module: IDCRS03 The data set name.
IDC11040I dsname UNKNOWN Application Programmer Response: This may be
Explanation: The VSAM Format 1 DSCB did not have caused by some previous system error. This message is
a corresponding space header in the volume record. given for information purposes. A later message may
Hence, the catalog does not account for the space indicate whether objects were marked unusable,
allocated to the data set. The data set noted above was perhaps as a result of this condition. Watch for
scratched. message IDC21037I or IDC21020I.
dsname Detecting Module: IDCRS03

The data set name.
System Action: Processing continues. IDC11043I TIME STAMP FOR VOLUME RECORD
ON VOL volser WAS CORRECTED
Application Programmer Response: If an I/O error
occurred when reading from the CRA for this volume, Explanation: The time stamp for the volume record
this condition may arise. It may also be caused by some did not match the time stamp in the VTOC. This may
previous system error. This message is given for have resulted from a failure in Catalog Management
informational purposes. A later message may indicate after updating one and not the other. The time stamps
whether objects were marked unusable, perhaps as a are synchronized.
result of this condition. Watch for message IDC21027I In the message text:
or IDC21030I.
Source: DFSMSdfp
Source: DFSMSdfp

Detecting Module: IDCRS03 dsname The indicated data set name.
System Action: REPAIRV DEBLOCK continues
IDC11044I dsname NOT SCRATCHED processing at the next valid stage error record pair. The
return code is 4.
Explanation: The attempt to scratch the data set for
the reason stated in preceding message IDC11040I Application Programmer Response: Display the
failed. repair work file records. If necessary rebuild the repair
work file using REPAIRV COPY.
dsname
The data set name.
System Action: Processing continues. exists, contact the IBM Support Center. Provide the JCL
Application Programmer Response: See IDC11040I.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: ICRD04
IDC11218I THE R‘0/R‘1 (volsercchh) PAIR ARE NOT

IDC11216I INVALID R‘0/R‘1 STAGE ERROR UNMODIFIED STAGE ERROR
RECORD PAIR: R‘0 NOT FOUND RECORDS IN REPAIR WORK FILE
(volsercchh) IN REPAIR WORK FILE dsname
dsname
Explanation: The specified records in the repair work
Explanation: During deblocking, the record was not file are not a R‘0/R‘1 pair created by a stage error. If
found in the file indicated by dsname. If your installation your installation had D/T3350 support, ignore R0 (record
has D/T3350 support, ignore R0 (record 0). It is no 0). It is no longer flagged with stage error information.
longer flagged with stage error information.
volsercchh The indicated record.
dsname The indicated data set name.
dsname The indicated data set name.
System Action: REPAIRV DEBLOCK continues with
System Action: REPAIRV DEBLOCK continues the next valid stage error record pair. The return code is
processing at the next valid state error record pair. The 4.
return code is 4.
Application Programmer Response: Necessary,
Application Programmer Response: Display the display the repair work file records.
repair work file records. If necessary rebuild the repair
work file using REPAIRV COPY. System Programmer Response: If the error recurs
and the program is not in error, search problem exists, contact the IBM Support Center. Provide the JCL
reporting data bases for a fix for the problem. If no fix and the SYSOUT output for the job.
Source: DFSMSdfp Detecting Module: ICRD04
Detecting Module: ICRD04
IDC11219I DEBLOCK FAILED FOR R‘0/R‘1
(volsercchh) IN REPAIR WORK FILE
IDC11217I INVALID R‘0/R‘1 STAGE ERROR dsname
RECORD PAIR: R‘1 NOT FOUND
(volsercchh) IN REPAIR WORK FILE Explanation: Two consecutive errors were found while
dsname trying to deblock the stage error record pair. An error
occurs when the length specified in the count field of a
Explanation: The record following the specified R‘0 record is wrong. This is determined by inspecting the
stage error record is not an R‘1 stage error record. If bytes following the specified length and not finding a
your installation had D/T3350 support, ignore R0 (record valid count field. REPAIRV DEBLOCK cannot continue
0). It is no longer flagged with stage error information. processing this record pair. If your installation had
In the message text: D/T3350 support, ignore R0 (record 0). It is no longer
flagged with stage error information.
465
In the message text: this condition is recommended to determine if there is a
serious problem. First, check for spelling errors. The
entries may no longer be in the catalog or VVDS. Run
dsname The indicated data set name. LISTCAT to verify the presence or absence of the entry
in the catalog.
System Action: REPAIRV DEBLOCK continues with
the next valid stage error record pair. The return code is If the entry is in the catalog but DIAGNOSE cannot
4. locate it, consult your hardware support personnel.
Application Programmer Response: Display the Source: DFSMSdfp
repair work file to verify contents of record pair in error,
then return REPAIRV DEBLOCK using the LENGTH
parameter to specify the key length and data length of
every original record in the track. IDC11362I THE FOLLOWING CATALOG
REFERENCED VOLUMES WERE NOT
ENCOUNTERED
reporting data bases for a fix for the problem. If no fix Explanation: The catalog contains some entries for
exists, contact the IBM Support Center. Provide the JCL VVDSs (volumes) that are not referred to by any of the
and the SYSOUT output for the job. entries processed. The volume serial numbers of the
volumes containing the VVDSs are listed. This indicates
Source: DFSMSdfp
that certain entries in the catalog may be missing
Detecting Module: ICRD04 volume information. However, under the following
circumstances, this message may indicate a normal
condition:
IDC11250I WARNING: NO VOLUME ATTRIBUTES v If you converted or deleted all data sets on the
MODIFIED. volume that are cataloged in the specified catalog.
Explanation: While processing a MODIFYC v If you chose to explicitly catalog the VVDS.
command, a cartridge label was changed to reflect it as System Action: DIAGNOSE considers this an
csn1|csn2 of a volume. However, no changes to the attention condition and processing continues.
volume attributes were requested in the command. If
the cartridge being modified was a scratch cartridge, the Application Programmer Response: If DIAGNOSE
scratch cartridge bit in the label remains on, to the encountered any errors which precluded looking at any
exclusion of all volume attributes. If the cartridge being volume cells, this message may be issued. Therefore,
modified was not a scratch cartridge, then the volume first fix other errors indicated by DIAGNOSE.
attributes remain unchanged and might not agree with
If DIAGNOSE was run with any entry qualification, such
the mass storage control tables and the inventory data
as INCLUDE or EXCLUDE, this message may be
set.
issued. In this case, the entries which were bypassed
Modification of one or more volume attributes turns off may refer to the listed volume.
the scratch cartridge bit in the label.
If a data set is missing volume information, to recover
System Action: The command continues normally. the missing volume information, use the DEFINE
command with the RECATALOG option to recatalog the
Application Programmer Response: Correct the data set. Then make any candidate volumes available
error, if necessary, and rerun the command. to the recataloged data set by using the ALTER
Source: DFSMSdfp command with the ADDVOLUMES parameter.
Detecting Module: IDCMC01 If the VVDS entry is extraneous, you can delete it using
DELETE NOSCRATCH for the specified VVDS.
IDC11361I THE FOLLOWING Source: DFSMSdfp

{INCLUDE|EXCLUDE} ELEMENTS Detecting Module: IDCDA03
WERE NOT ENCOUNTERED
Explanation: The names which follow the messages IDC11367I THE FOLLOWING VVDS REFERENCED
were expected to be in the catalog or VVDS as they CATALOGS WERE NOT
were specified in the INCLUDE or EXCLUDE list. These ENCOUNTERED
names were not encountered during processing.
Explanation: The list of catalog names which follow
System Action: DIAGNOSE considered this an are referenced by the VVDS as catalog entries but
attention condition and continued to process the catalog these names were not found in any entries for scanned
or VVDS. VVDSs. There may be missing or damaged VVDS
Application Programmer Response: An analysis of entries. This may be a normal condition if all data sets

on the volumes which are cataloged in the specified
IDC11374I THESE ADDITIONAL CATALOG
catalog have been converted or deleted, or if
REFERENCED VOLUMES WERE
DIAGNOSE was run with any entry qualification, such
ENCOUNTERED volume-serial-numbers
as INCLUDE or EXCLUDE.
Explanation: The listed volume serial numbers
System Action: DIAGNOSE considers this an
volume-serial-numbers are referenced by catalog entries
attention condition and processing continues.
but these volume serial numbers were not found as
Application Programmer Response: Run VVDS entries. This may indicate entries are referencing
DIAGNOSE ICFCATALOG for the extraneous catalog volumes for which the catalog has no record. There
name. Determine whether data sets are missing from should be a ‘SYS1.VVDS.Vvolser’ entry for each volume
the volume. If no data sets are missing, use the referenced by VSAM entries in the catalog, except
DELETE command with the NOSCRATCH option to where the ‘SYS1.VVDS.Vvolser’ is created by EOV.
remove the VVDS entry from the extraneous catalog. Vvolser is the volume serial number of the volume.
If any data sets are missing from the volume, recover System Action: DIAGNOSE considers this an
the data sets in their entirety. Multivolume data sets attention condition and processing continues.
require that all volumes are recovered together, not just
the affected volume.
is an attention and may signal entries which are missing
Source: DFSMSdfp or damaged. To add an entry for the missing VVDS to
the catalog, using DEFINE RECATALOG on the VVDS.
Detecting Module: IDCDA03 If a VSAM data set incorrectly references the volume,
remove the reference from the data set entry with
IDC11373I THE FOLLOWING COMPARE ALTER REMOVEVOLUMES.
ELEMENTS WERE NOT Source: DFSMSdfp
ENCOUNTERED
Explanation: The names that follow this message
were given in the comparison list but were not
encountered during processing. The entries may no IDC11375I THESE ADDITIONAL VVDS
longer be in the catalog or VVDS. REFERENCED CATALOGS WERE
ENCOUNTERED
System Action: DIAGNOSE considers this an
attention condition and continues processing the catalog Explanation: The catalog names listed are referenced
or VVDS. by VVDS entries but these names were not found as
catalog entries in the VVDS. The VVDS contains the
Application Programmer Response: Check the names of all referenced catalogs in the VVDS control
spelling carefully. If you are using DD statements to record (VVCR). Each entry in the VVDS contains the
define catalogs, ensure that a DSNAME has been name of the catalog in which the component is
coded. If a volume serial number has been coded, cataloged. There were catalog names in VVDS entries
ensure that it is correct. If the command is correctly which were not also in the VVCR.
coded, take the following steps:
v For a BCS, use LISTCAT to verify the catalog This message applies only for volumes and catalogs
contains an entry for the listed VVDS. Determine with non-SMS-managed data sets.
whether any data sets in the catalog are missing
System Action: Consider this an attention condition,
volume entries. If volume entries are missing, use
DEFINE RECATALOG to recatalog these data sets
and to pick up missing volumes. If volume entries are Application Programmer Response: This message
not missing, change the DIAGNOSE command to is an attention and may signal entries which are missing
remove the reference to the missing compare name; or damaged. Either the VVCR entry for the catalog is
there is no error. missing, or a VVDS record is referring to a catalog
v For a VVDS, determine whether any VVDS entries incorrectly. Run DIAGNOSE ICFCATALOG against each
should be referencing the named catalog. catalog listed, and compare each to the VVDS.
To add the catalog name to the VVCR, define a dummy
If the entry is in the catalog but DIAGNOSE cannot
data set on the volume by using the DEFINE command,
locate it, contact your service representative.
and specify the catalog name needed in the CATALOG
Source: DFSMSdfp parameter. Then delete the dummy data set by using
the DELETE command. The catalog name remains in
Detecting Module: IDCDA03 the VVDS control record because a VVDS entry refers
to the catalog.
To remove the VVDS entry, if the reference to the
catalog is the result of an extraneous VVDS entry, use
467
the DELETE VVR command.
IDC11468I NVR/VVR NOW POINTS TO TARGET
Source: DFSMSdfp CATALOG
Detecting Module: IDCDA03 Explanation: After a REPRO of one integrated catalog

facility catalog to another, the NVR/VVRs are changed
to point to the target catalog and all subsequent
IDC11441I ENTRY WAS INTERRUPTED DURING A processing must be done under the target catalog.
PREVIOUS PROCESS
Explanation: This ICF catalog entry was previously
interrupted before completion of a delete or Source: DFSMSdfp
update-extend function.
System Action: LISTCAT processing continues listing
the entry’s remaining information normally.
IDC11560I NO PINNED TRACKS EXIST FOR
Application Programmer Response: It may be VOLUME volser
desirable to run the access method services
Explanation: There are no pinned tracks on the
DIAGNOSE command. See DFSMS/MVS Access
specified volume. Two requests can result in the
Method Services for ICF for details on DIAGNOSE.
issuance of this message:
System Programmer Response: If the error recurs v a LISTDATA PINNED request for a PINNED TRACK
and the program is not in error, look at the messages in REPORT.
v a SETCACHE DISCARDPINNED request to
invalidate all cache fast write and DASD fast write
data for the device.
Detecting Module: IDCLC02 volser The volume serial number specified in the
LISTDATA/SETCACHE command.
IDC11462I REQUESTED RANGE END BEYOND System Action: Processing continues.
END OF DATA SET
Explanation: A PRINT or REPRO command was
Source: DFSMSdfp
issued. The TO value or COUNT value specified was
beyond the end of the data set. Processing continues,
defaulting to the end of the data set. IDC11563I INCOMPLETE {COUNTS | STATUS}
FOR THIS VOLUME, SD OFFLINE
System Action: The command continues processing
with a condition code of 4. Explanation: There is no path to the other storage
director for 3880 Model 21 or 23, COUNTS and/or
Application Programmer Response: None if the
STATUS REPORTS.
default is correct. Otherwise, correct the range value
and rerun the command. System Action: The report for the available storage
director is printed. The other half of the report for Model
Source: DFSMSdfp
21 COUNTS or STATUS, or Model 23 STATUS is not
printed. The Model 23 COUNTS report depicts the
IDC11465I DELIMITERS WERE SPECIFIED, BUT performance statistics for both storage directors in the
NO RECORDS WERE PROCESSED. same report; therefore the offline storage director will
have zero counts.
Explanation: An IDCAMS REPRO was executed with
delimiters specified, however due to an error in their Application Programmer Response: None.
specification no records were processed.
Source: DFSMSdfp
System Action: Job Completes condition code 4
User Response: Correct the delimiters and resubmit. IDC11613I DUAL COPY VOLUMES SHOULD BE IN
SEPARATE STORAGE FACILITIES
Explanation: This attention message indicates that a
SETCACHE command to establish or re-establish a
System Programmer Response: None duplex pair was issued, and the requested devices were
not on separate storage facilities. This attention is also
Source: IDCAMS issued when the devices are on separate 2-path strings
Detecting Module: IDCRP01 having the same string address in a DLSE mode

subsystem with intermixed 2-path and 4-path DASD to continue ending the duplex pair.
strings. Separate storage facilities are recommended to
avoid single points of failure when duplexing. The
message is attached via the IBM 3990 Model 3 or
SETCACHE commands that could cause this attention
Model 6 Storage Control, see IBM 3990 Operations and
message to be generated are:
Recovery Guide. for detailed recovery actions.
v SETSECONDARY, if the prospective primary and
secondary devices are on the same storage facility. Application Programmer Response: If a true copy
was required, another method for the copy will have to
v REESTABLISHDUPLEX, if the primary device and
be used.
the requested alternate device are on the same
storage facility. Source: DFSMSdfp
IDC11651I A DUPLICATE ENTRY WAS FOUND
System Programmer Response: See the IBM 3990
FOR ALIAS alias
Operations and Recovery Guide. manual for additional
recovery comments for this message. Explanation: A duplicate name was found in the
master catalog while attempting to define an entry into it
Source: DFSMSdfp
for the IMPORT of an integrated catalog facility catalog.
IDC11614I AUTHORIZATION CHECKING HAS
BEEN BYPASSED. VOLSER NOT alias The name of the alias.
AVAILABLE FOR THE OFFLINE
DEVICE. System Action: Processing continues with the next
alias to be defined.
Explanation: An IDCAMS command requiring volume
authorization checking was issued. That checking was Application Programmer Response: None, but you
not possible because the volume serial could not be may want to verify that the alias names, existing after
obtained from the offline device. The DASDVOL ALTER the IMPORT is complete, are still valid.
authorization checking for the volume is bypassed and Source: DFSMSdfp
processing of the command continues. This message
can result from the following commands: Detecting Module: IDCXP01
v SETCACHE SETSECONDARY, for the secondary
volume IDC11656I ‘ALIAS’ KEY WORD IGNORED WITH
v SETCACHE REESTABLISHDUPLEX, for the VSAM MASTER CATALOGS
alternate volume Explanation: The system is operating under a VSAM
System Action: Processing continues. master catalog and the keyword ALIAS was coded.
Aliases on the portable data set for integrated catalog
Application Programmer Response: None. facility user catalogs cataloged in a VSAM master
Source: DFSMSdfp catalog are not defined.
Detecting Module: IDCSS01 System Action: Aliases that may exist on the portable
data set are ignored. Processing continues.
IDC11617I RESETTOSIMPLEX COMMAND IN Application Programmer Response: None.

PROCESS. HOWEVER, DASD FAST Source: DFSMSdfp
WRITE COULD NOT BE DEACTIVATED.
COPIES MAY NOT BE IDENTICAL. Detecting Module: IDCXP01
Explanation: If an active duplex pair is ended with

DASD fast write active, the resulting simplex volumes IDC11659I INSUFFICIENT WORKAREA PROVIDED
may not be true copies. When ending a duplex pair, TO RETURN FULL VOLUME LIST
IDCAMS issues a channel command to deactivate Explanation: A problem program issued a VOLLIST
DASD fast write to allow for destage of any DASD fast request, but didn’t provide a large enough workarea to
write data. This attention message is issued when the contain the response to that request.
attempt to deactivate DASD fast write failed (probably
because DASD fast write was in pending state from System Action: The system continues processing.
another job). If DASD fast write was on prior to issuing Application Programmer Response: Make sure the
the RESETTOSIMPLEX channel command, then DASD workarea you provide is large enough to list all volume
fast write would have been reactivated for the primary of serial names (VOLSERs) necessary to satisfy the
the ended pair. VOLLIST request. In DFSMS/MVS Access Method
System Action: Processing continues with the attempt Services for ICF refer to the section about invoking
access method services from a problem program; that
469
section describes VOLLIST requirements.
IDC11704I INDEX KEYS ARE NOT IN SEQUENCE
Source: DFSMSdfp
Explanation: The present key has a smaller value
Detecting Module: IDCMP02 than the previously tested key.
System Action: The relevant control interval is
IDC11700I HIGH-LEVEL INDEX STRUCTURE IS dumped, and processing continues.
NOT UNIQUE
Application Programmer Response: See summary
Explanation: A single level index structure is messages for final analysis.
expected, but a horizontal pointer linking one control
Source: DFSMSdfp
interval to another is found.
System Action: The control interval is dumped, and
IDC11705I INDEX RECORD CONTAINS
DUPLICATE INDEX POINTERS
Application Programmer Response: See summary pointer-value
messages for final analysis. Issue a VERIFY command
Explanation: An index control interval has duplicate
and reissue the EXAMINE command.
vertical pointers. The pointer value is displayed in HEX.
Source: DFSMSdfp
pointer-value
IDC11701I STRUCTURAL PROBLEM FOUND IN
The value of the pointer, in hexadecimal.
INDEX
Explanation: A single level index structure, the
sequence set, is expected, but a control interval
assigned to a higher level is found. Application Programmer Response: See summary
messages for final analysis.
processing continues. Source: DFSMSdfp
messages for final analysis. IDC11706I MISSING SEQUENCE SET ENTRIES
Source: DFSMSdfp Explanation: A sequence set control interval does not
contain pointers to all of the control intervals in the data
control area that this sequence set control interval
IDC11702I BASE RBA IS NOT ZERO
represents.
Explanation: A base relative byte address of zero (0)
System Action: Supportive information is displayed
is expected for the first sequence set control interval,
and processing continues.
but a nonzero value is found.
Source: DFSMSdfp
IDC11707I DUPLICATE INDEX POINTERS FOUND
Source: DFSMSdfp
IN SEQUENCE SET
Explanation: A sequence set control interval has
IDC11703I DUPLICATE KEYS IN INDEX
duplicate data or free control interval pointers.
Explanation: The present and previous keys of the
System Action: The sequence set control interval is
current index level are identical.
dumped, and processing continues.
Source: DFSMSdfp
Source: DFSMSdfp

IDC11708I HIGH-USED INDEX RBA DOES NOT IDC11712I DATA HIGH-ALLOCATED RBA IS NOT
EQUAL HIGHEST RBA FOUND A MULTIPLE OF CI SIZE
Explanation: The largest relative byte address Explanation: The high-allocated relative byte address
encountered while processing the index does not equal is not an integral multiple of the control interval size.
the index high-used relative byte address less index
System Action: Supportive messages display
control interval size.
pertinent data, and processing continues.
System Action: One or more supportive messages
display the addresses found, and processing continues.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11714I UNUSED INDEX SPACE IS NOT A
MULTIPLE OF CI SIZE
IDC11709I DATA HIGH-USED RBA IS GREATER
Explanation: The difference between the
THAN HIGH-ALLOCATED RBA
high-allocated and high-used relative byte address for
Explanation: The data component high-used relative an extent is not an integral multiple of the control
byte address is greater than the high-allocated relative interval size.
byte address.
System Action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11715I INDEX HIGH-USED RBA IS NOT A
IDC11710I DATA HIGH-USED RBA IS NOT A MULTIPLE OF CI SIZE
MULTIPLE OF CI SIZE
Explanation: The index component high-used relative
Explanation: The data component high-used relative byte address is not an integral multiple of the control
byte address is not an integral multiple of the control interval size.
interval size.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11716I INDEX HIGH-ALLOCATED RBA IS NOT
IDC11711I INDEX CONTROL INTERVAL COUNT A MULTIPLE OF CI SIZE
ERROR
Explanation: The high-allocated relative byte address
Explanation: The arithmetic count of all index control for the index component is not an integral multiple of
intervals less all unused index control intervals does not the control interval size.
equal the actual number of index control intervals read.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11717I HIGH-LEVEL INDEX CI EXPECTED BUT
NOT ACQUIRED
Explanation: An attempt to acquire the highest-level
index control interval resulted in acquiring a lower-level
index control interval.
471
System Action: Supportive message display pertinent
IDC11722I DUPLICATE INDEX BASE RBA FOUND
data, and processing continues.
Explanation: Two sequence set control intervals have
identical base relative byte addresses.
System Action: Supportive messages are displayed,
Source: DFSMSdfp
IDC11718I DATA COMPONENT HIGH-USED RBA
IS NOT EQUAL TO CA SIZE
Source: DFSMSdfp
Explanation: For a data set with a single level index,
the calculated control area size does not equal the
high-used relative byte address for the data component. IDC11723I BASE RBA NOT ON CA BOUNDARY
System Action: Supportive messages display Explanation: A sequence set base relative byte
pertinent data, and processing continues. address is not an integral multiple of the control area
size.
messages for final analysis. System Action: The control interval is dumped, and
Source: DFSMSdfp
IDC11719I MISSING CI WITHIN INDEX LEVEL
Source: DFSMSdfp
Explanation: An index control interval is not
referenced in the index horizontal pointer chain. The
next higher level indicates it should exist. IDC11724I DATA COMPONENT CA NOT KNOWN
TO SEQUENCE SET
Explanation: A data control area exists that does not
have a corresponding sequence set control interval.
Source: DFSMSdfp
IDC11720I NUMBER OF INDEX LEVELS IS ZERO
Explanation: The number of index levels in the index
Source: DFSMSdfp
component of AMDSB is zero.
IDC11725I SEQUENCE SET RBA INCONSISTENT
Application Programmer Response: See summary WITH VSAM-MAINTAINED RBA
Explanation: The first sequence set control interval
Source: DFSMSdfp relative byte address obtained from level two of a
multiple level index is not the same as the relative byte
address maintained by VSAM in the AMDSB for the
IDC11721I OUT OF RANGE INDEX POINTER index component.
WITHIN SEQUENCE SET
System Action: Supportive messages supply pertinent
Explanation: A data or free control interval pointer in a data, and processing continues.
sequence set control interval was found with a value
greater than the maximum allowed. Application Programmer Response: See summary
System Action: The sequence set control interval is
dumped, and processing continues. Source: DFSMSdfp

messages for final analysis. IDC11726I CI ON CURRENT LEVEL NOT POINTED
TO BY NEXT LEVEL
Source: DFSMSdfp
Explanation: A control interval on the current index
level is not pointed to by the next higher index level.

IDC11732I DATA FOUND IN FREE AREA OF DATA
CI
Source: DFSMSdfp
Explanation: The free space of a data component
control interval contains residual data.
IDC11727I INDEX HIGH-USED RBA IS GREATER
THAN HIGH-ALLOCATED RBA
Explanation: The index component high-used relative
byte address is greater than the high-allocated relative
byte address.
Source: DFSMSdfp
IDC11733I DATA COMPONENT KEY SEQUENCE
ERROR
Explanation: A key sequence error exists in or
Source: DFSMSdfp
between data control intervals.
System Action: The previous key and the current
IDC11728I DATA FOUND IN EMPTY CI
data control interval are dumped, and processing
Explanation: The free area of an empty control continues.
interval contains data.
System Action: The control interval is dumped, and messages for final analysis.
Source: DFSMSdfp
IDC11734I SEQUENCE SET AND DATA CI KEY
Source: DFSMSdfp SEQUENCE MISMATCH
Explanation: The data key is not within the range of
IDC11730I UNSPANNED RECORD FOUND WHEN keys valid for this data control interval. It must be
SPANNED RECORD SEGMENT greater than the index key of the previous data control
EXPECTED interval, and less than or equal to the index key for this
data control interval.
Explanation: The first segment of a spanned record
has been read, but the current record is not identified as System Action: The previous and current index keys
being in an intermediate or last segment. and the current data control interval are dumped, and
System Action: The index and data control intervals
are dumped, and processing continues. Application Programmer Response: See summary
messages for final analysis. Source: DFSMSdfp
Source: DFSMSdfp
IDC11735I EMPTY CI ENCOUNTERED WHILE
PROCESSING SPANNED RECORDS
IDC11731I SPANNED RECORD UPDATE NUMBER
ERROR Explanation: An empty control interval was read, but
a spanned record segment was expected.
Explanation: The spanned record update number is
not the same for all segments of the record. System Action: The relevant index and data control
intervals are dumped, and processing continues.
System Action: The relevant index and data control
intervals are dumped, and processing continues. Application Programmer Response: See summary
messages for final analysis. Source: DFSMSdfp
Source: DFSMSdfp
473
control interval definition field or overlaps the leftmost
IDC11736I ERROR IN RDF
record definition field.
Explanation: The record definition field flag byte
contains incorrect bits, or, for an index control interval,
dumped, processing continues.
the length field is incorrect.
Source: DFSMSdfp
IDC11741I DUPLICATE CONSECUTIVE KEYS
Source: DFSMSdfp
FOUND
Explanation: Two consecutive keys are identical.
IDC11737I A RIGHT RDF IS CODED AS
CONTAINING THE NUMBER OF System Action: The current control interval is
RECORDS IN CI dumped, and processing continues.
Explanation: A right record definition field is coded Application Programmer Response: See summary
with the attributes of a left record definition field. messages for final analysis.
System Action: The relevant control interval is Source: DFSMSdfp
Application Programmer Response: See summary IDC11742I MORE SEQUENCE SET CONTROL
messages for final analysis. INTERVALS FOUND THAN EXPECTED
Source: DFSMSdfp Explanation: The index contains too many sequence
set control intervals.
IDC11738I A LEFT RDF IS CODED AS System Action: The relevant control interval is
CONTAINING THE LENGTH OF dumped, and processing continues.
RECORDS IN CI
Explanation: A left record definition field is coded with messages for final analysis.
the attributes of a right record definition field.
Source: DFSMSdfp
IDC11743I SOFTWARE EOF FOUND IN INDEX
Application Programmer Response: See summary SEQUENCE SET CI
Explanation: An index sequence set control interval
Source: DFSMSdfp contains a software end-of-file.
IDC11739I SPANNED RECORD SEGMENT processing continues.
SEQUENCE ERROR
Explanation: A record coded as a first segment is messages for final analysis.
found, but an intermediate or last segment is expected,
or an intermediate or last segment is found when no Source: DFSMSdfp
first segment was read.
System Action: The relevant control interval is IDC11744I SOFTWARE EOF NOT FOUND IN THE
dumped, processing continues. HIGH-USED RBA CI
Application Programmer Response: See summary Explanation: The last data control interval does not
messages for final analysis. contain a software end-of-file.
Source: DFSMSdfp System Action: The control interval is dumped, and

IDC11740I DATA RECORDS OVERLAP FREE Application Programmer Response: See summary
SPACE OR CONTROL INFORMATION messages for final analysis.
Explanation: The length of the records in the current Source: DFSMSdfp

control interval exceeds the length specified in the

IDC11745I ERROR IN CIDF IDC11758I SOFTWARE EOF FOUND IN INDEX CI
Explanation: An error has been found in the control Explanation: An index control interval contains a
information definition field of the current control interval. software end-of-file.
System Action: The control interval is dumped, and System Action: The control interval is dumped, and
processing continues. processing continues.
Application Programmer Response: See summary Application Programmer Response: See summary
messages for final analysis. messages for final analysis.
IDC11751I INCONSISTENCY EXISTS BETWEEN IDC11760I CI SIZE INVALID

CODING OF LEFT AND RIGHT RDF
Explanation: The control interval size was not n times
Explanation: The control information of a left record 512 bytes, where n is an integer one to sixteen.
definition field does not agree with the control
System Action: The control interval size is displayed,
information of a right record definition field.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11761I DATA KEY POSITION OR LENGTH
ERROR
IDC11755I LENGTH OF FREE SPACE NOT EQUAL
Explanation: The calculated ending position of the key
TO VALUE IN CIDF
is greater than the maximum record length, the
Explanation: The length of the free space in a data maximum spanned record length, or the length of the
control interval does not equal the value in the control record being processed.
interval definition field.
System Action: The control interval is dumped, if
System Action: The control interval is dumped, and applicable, and processing continues.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11762I LENGTH OF VERTICAL POINTER
IDC11756I SOFTWARE EOF FOUND IN FREE CI INVALID
Explanation: A free data control interval contains a Explanation: The index vertical pointer length is not 1,
software end-of-file. 2, or 3 bytes.
System Action: The control interval is dumped, and System Action: Processing continues.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11763I RBA OF INDEX CI GREATER THAN OR
IDC11757I SOFTWARE EOF FOUND IN DATA CI EQUAL TO HIGH-USED RBA
Explanation: A data control interval contains a Explanation: The relative byte address of an index
software end-of-file. control interval is greater than or equal to the index
high-used relative byte address.
processing continues. System Action: RBAs are displayed, and processing
continues.
messages for final analysis. Application Programmer Response: See summary
Source: DFSMSdfp
475
Source: DFSMSdfp
IDC11769I MORE INDEX POINTERS THAN
EXPECTED
IDC11764I NUMBER OF CONTROL INTERVALS IN
Explanation: More vertical, horizontal, or base relative
CA NOT GREATER THAN ZERO
byte address pointers have been found while
Explanation: The number of control intervals per processing an index level than should exist on that
control area found in AMDSB is zero. level.
System Action: Processing continues. System Action: Processing continues.
Application Programmer Response: See summary Application Programmer Response: See summary
messages for final analysis. messages for final analysis.
IDC11765I DATA HIGH-USED RBA IS NOT A IDC11770I INDEX RECORD HORIZONTAL

MULTIPLE OF CA SIZE POINTER POINTS TO ITSELF
Explanation: The data high-used relative byte address Explanation: An index control interval contains a
is not an integral multiple of the control area size. horizontal pointer specifying the relative byte address of
the control interval itself.
Application Programmer Response: See summary processing continues.
Source: DFSMSdfp messages for final analysis.
Source: DFSMSdfp
IDC11766I ERROR IN INDEX RECORD
Explanation: A field in the index header or entries IDC11771I INVALID RBA GENERATED
contain incorrect data.
Explanation: An incorrect relative byte address has
System Action: The index control interval is dumped, been generated from index component data.
messages for final analysis. Application Programmer Response: See summary
Source: DFSMSdfp
Source: DFSMSdfp
IDC11767I DATA HIGH-ALLOCATED RBA IS NOT

A MULTIPLE OF CA SIZE IDC11772I HORIZONTAL POINTER CHAIN LOOP
Explanation: The data high-allocated relative byte Explanation: A long loop has been discovered in the
address is not an integral multiple of the control area horizontal pointer chain in an index level.
size.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11808I ERRORS WERE DETECTED FOR
IDC11768I CI SPLIT IN PROGRESS dsname ON VOLUME volser ERROR
BYTE WAS X‘nn’
Explanation: A control interval split
in-progress-indicator was encountered. Explanation: During data collection for the specified
data set, errors were detected.
processing continues. In the message text:
Application Programmer Response: See summary dsname
messages for final analysis. The data set name.

nn The hexadecimal error byte.
IDC11816I DYNAMIC ALLOCATION FAILED FOR
System Action: Processing continues. VOLUME volser
Application Programmer Response: See the field Explanation: Volume volser could not be dynamically
‘DCDERROR’ in that data set’s “D” record for the allocated by the system. Severity is 4.
specific failure.
System Action: Processing continues with the next
System Programmer Response: If the error recurs volume to be processed.
Operator Response: The volume may have been
taken off line after the initial list of volumes to be
processed was generated by DCOLLECT. Run the job
again.
output and output data sets related to the problem. Application Programmer Response: If the error
recurs and the program is not in error, look at the
Source: DFSMSdfp
messages in the job log for more information. Search
IDC11812I MESSAGE PROCESSING SUSPENDED, no fix exists, contact the IBM Support Center. Provide
ERROR LIMIT EXCEEDED the JCL, the SYSOUT output for the job, and printed
Explanation: The number of error messages printed
exceeds the number specified in the error limit
parameter. IDC11818I type INFORMATION NOT FOUND
System Action: Processing continues. Explanation: This message indicates that a requested
definition was not found or unavailable.
Application Programmer Response: If all error
messages are required, increase the error limit or do In the message text:
not specify the error limit parameter.
type
System Programmer Response: If the error recurs The type of definition not found:
and the program is not in error, look at the messages in v STORAGE CLASS CONSTRUCT
v MANAGEMENT CLASS CONSTRUCT
exists, contact the IBM Support Center. Provide the v STORAGE GROUP CONSTRUCT
JCL, the SYSOUT output for the job, and all printed v SMS VOLUME
output and output data sets related to the problem. v BASE CONFIGURATION
Source: DFSMSdfp v CACHE SET NAME
v AGGREGATE GROUP CONSTRUCT
IDC11813I ERRORS WERE DETECTED FOR volser v OPTICAL DRIVE
ERROR BYTE WAS X‘nn’ v OPTICAL LIBRARY
Explanation: During volume information processing, v ACS ROUTINE
errors were detected for the specified volser.
Note: CACHE SET NAME in this context refers to
a VSAM RLS cache set. See OS/390
volser The volume serial number. DFSMSdfp Storage Administration
Reference.
nn The error byte.
System Programmer Response: None, the message
Application Programmer Response: See the field
is informational only.
‘DCVERROR’ in that volser’s V record for the specific
error. Source: DFSMSdfp
System Programmer Response: If the error recurs Detecting Module: IDCDC03
IDC11819I DEVICE PENDING OFFLINE - NO
RECORDS PROCESSED FOR (volser)
JCL, the SYSOUT output for the job, and all printed Explanation: The specified volume is offline and no
output and output data sets related to the problem. data can be processed for this volume.
Source: DFSMSdfp
477
IDC21009I entryname, type DOES NOT EXIST ON
the next volume.
VOLUME volser
Source: DFSMSdfp
Explanation: A multivolume data set existed on a
volume prior to reset. The data set is not on the volume
IDC11860I NO DBCS CHARACTERS INDICATED and will be marked unusable.
IN SOURCE DATA SET
Explanation: DBCS was specified on an access
method services (AMS) PRINT or REPRO copy of a
data set. This indicated that AMS was to criteria check entryname The specified entry name.
the DBCS characters in the source data set. However,
type The type of record. The values are
the data set does not indicate the presence of DBCS
defined under message IDC21045I.
characters (no SO or SI characters were located).
Application Programmer Response: The data set on
valid volumes may be removed via REPRO prior to
is informational. However, you may want to recheck the
deleting the data set. The data set cannot be opened
specification of the data set name to ensure that the
for output.
proper data set was processed, or specify
INSERTSHIFT values to insert SO and SI characters to Source: DFSMSdfp
allow the detection of DBCS characters.
Source: DFSMSdfp
IDCRS03
IDC11861I INVALID DBCS CHARACTER IN

RECORD number AT OFFSET offset IDC21020I UNABLE TO ALLOCATE volser
Explanation: INSERTSHIFT or INSERTALL was Explanation: An attempt to allocate a volume for

specified on an access method services (AMS) PRINT RESETCAT failed. See message IDC3905I.
or REPRO copy of a data set. AMS, while criteria In the message text:
checking the DBCS characters in the source data set,
detected an incorrect DBCS character. volser The volume serial number.
In the message text: System Action: Processing continues.
number The record number. Application Programmer Response: Make the

volume indicated available to RESETCAT via
offset The offset indicated. CRAFILES and reissue the command.
System Action: Processing continues. Source: DFSMSdfp
Application Programmer Response: This message Detecting Module: IDCRS06
is informational. However, you may want to recheck the
specification of the INSERTSHIFT offsets or the DBCS
data. On the AMS PRINT command these characters IDC21024I entryname, type CONTAINS AN INVALID
will be replaced with DBCS periods. ALIAS CHAIN
Source: DFSMSdfp Explanation: The alias chain for a user catalog or

non-VSAM entry is incorrect.
IDC11902I parameter-name SET TO DEFAULT OF In the message text:

default-value entryname
Explanation: The system accepted a default value for The specified entry name.
the specified parameter. type The type of record. The values are defined
System Action: The system continues processing the under message IDC21045I.
command. System Action: Processing continues.
Source: DFSMSdfp Application Programmer Response: The alias chain
Detecting Module: IDCAL02 will be corrected. A LISTCAT should be run to determine
which aliases may be lost.

IDC21027I {CRA|CATALOG} SPACE NOT VOLUME
catalog.
volser NOT OWNED BY CATALOG
Source: DFSMSdfp
Explanation: The CRA extents or catalog extents
Detecting Module: IDCRS02 have no matching extents in any data space.
IDC21025I entryname, type HAS AN INVALID GDG
DATA SET ASSOCIATION
Explanation: The records associating the GDG data
set with the GDG base are in error. The GDG base has Application Programmer Response: The resultant
been recovered; however, the generation data set string catalog is vulnerable because there are conflicting
associated with this base has been altered to reflect space ownership requests between the VTOC and the
only those data set descriptions which can be located. catalog. After the RESETCAT, use EXPORT to transfer
all data sets on the volume noted and remove VSAM
ownership to the volume. Check the data sets to ensure
entryname The specified entry name. that they contain reasonable data. Then add ownership
to the volume, and then use import to reestablish the
type The type of record. The values of type data sets.
are defined under message
IDC21045I. Source: DFSMSdfp
System Action: Processing continues. Detecting Module: IDCRS03
Application Programmer Response: Perform a

LISTCAT for the GDG base and determine which IDC21030I entryname, type HAS INVALID SPACE
entries no longer exist. Though entries do not exist, DESCRIPTION FOR volser
RESETCAT has not altered/scratched the data sets. If
Explanation: The entry noted claims space on
the resulting GDG data set string is in error, delete the
volume. That space is not allocated to that entry.
GDG and redefine it; then catalog the correct
generations by name. In the message text:
Source: DFSMSdfp entryname The specified entry name.
Detecting Module: IDCRS03 type The type of record. The values of type
IDC21045I.
IDC21026I entryname, type DELETED
Explanation: A previous message indicates an error
which resulted in this entry being deleted from the System Action: Processing continues.
catalog.
Application Programmer Response: The data set is
In the message text: marked unusable and the volume description
invalidatable. LISTCAT may be run to determine the
incorrect extents. Delete the data set. Redefine it and
type The type of record. The values of type reload it.
IDC21045I.
System Action: Processing continues. entries and information about objects defined in the
catalog.
Application Programmer Response: The entry noted
was deleted. Any space that it occupied has been Source: DFSMSdfp
returned for suballocation if it was a VSAM object. If the
entry is desired, it must be redefined and loaded. Note
that any objects dependent on this object are also
deleted, but no message is given for them. For IDC21032I type DELETED FROM entryname, type
instance, if a cluster is deleted, all paths, alternate
Explanation: An object of the type specified was
indexes, and the upgrade set are also deleted.
defined over the entry named. However, the records
Source: DFSMSdfp describing the object could not be found. Therefore, an
object of the type specified was deleted from the given
entry name description. No name for the deleted object
is given because the record with its name cannot be
found.
479
In the message text: type The type of record. The values of type
IDC21045I.
type The type of record. The values of type
avol The volume.
IDC21045I. System Action: Processing continues.
System Action: Processing continues. Application Programmer Response: If the renamed
entry was a non-VSAM entry, the associated format-1
Application Programmer Response: Perform a
DSCB has not been renamed. The entry may be
LISTCAT for the entryname noted, and try to determine
deleted (NOSCRATCH), the conflict resolved and the
which entity was deleted and redefine it.
entry redefined.
Source: DFSMSdfp
If a GDG base or GDG set has been renamed, the base
Detecting Module: IDCRS02, IDCRS03 and its associated data sets should be deleted
(NOSCRATCH) and redefined after resolving the
conflict.
IDC21034I SPACE MAP ERROR FOR volser
If a catalog connector was renamed, that catalog may
Explanation: The space map, which indicates which be EXPORTed (using the DISCONNECT option), the
space is available for suballocation on a volume, is not conflict resolved, and the catalog connector entry
the correct length in the catalog. This may be due to a IMPORTed.
damaged catalog or CRA. This situation is not
correctable by RESETCAT. If an ALIAS was renamed the conflict may be resolved,
and ALTER issued to rename the entry back.
Note that the non-VSAM and GDG data sets will be
volser The volume serial number. inaccessible via this new name, because the Format 1
System Action: Processing continues. DSCB name does not correspond to the catalog name.
The catalog entry is accessible.
Application Programmer Response: All data sets on
the volume noted may be EXPORTed, the volume and Source: DFSMSdfp
all VSAM space should be deleted. Redefine the Detecting Module: IDCRS07
volume in the catalog and IMPORT the data sets. The
error noted may create a conflict in space allocated
between the VSAM catalog and DADSM allocate. IDC21046I entryname, type ON cravol RENAMED
entryname
Source: DFSMSdfp
Explanation: An attempt was made to reset a unique
Detecting Module: IDCRS03 object into a catalog which contains an object of the
same name. The unique object was renamed along with
IDC21045I entryname, type avol RENAMED its corresponding format-1 DSCB on all volumes.
entryname In the message text:
Explanation: An attempt was made to reset an object entryname The specified entry name.
that bears the same name as some other object in the
catalog. One of the objects was chosen to be renamed type The type of record. The values of type
as noted in the message. are defined under message
IDC21045I.
The types of entries are as follows:
A -- non-VSAM cravol The catalog recovery area (CRA)
B -- GDG base volume.
C -- cluster
D -- data
G -- alternate index Application Programmer Response: The object
I -- index noted is accessible. If desired, the conflicting named
R -- path object in the catalog may be moved or renamed, and
U -- user catalog this object renamed via ALTER back to its former name.
X -- alias
Source: DFSMSdfp
In the message text: Detecting Module: IDCRS07

Remaining dump requests are processed.
IDC21047I entryname, type ON cravol MAY NOT BE
ACCESSED BY NAME Application Programmer Response: Correct the
sector range, specifying a low sector value that is lower
Explanation: An attempt was made to reset a unique
than the high sector value. Resubmit the command.
object into a catalog which contained an object of the
same name. RESETCAT attempted to rename the Source: DFSMSdfp
unique object, but failed either because all volumes
were not available (see message IDC3906I) or the Detecting Module: IDCDU01
RENAME failed.
In the message text: IDC21103I INVALID SSID nnnn
entryname The specified entry name. Explanation: The SSID value was incorrectly specified
for a Staging Adapter. SSIDs for Staging Adapters must
type The type of record. The values of type be of the form X'08x0', where x is in the range 0
are defined under message through F.
IDC21045I.
cravol The catalog recovery area (CRA)
volume. nnnn The SSID value.
System Action: Processing continues. System Action: Requests for this SSID are bypassed.
Remaining dump requests are processed.
Application Programmer Response: The object
noted may be accessed via the cluster name, but not Application Programmer Response: Correct the
the data or index name noted. The data set may be SSID and rerun the command.
EXPORTed, and then IMPORTed after resolving the Source: DFSMSdfp
name conflict in order to gain accessibility via the date
or index component name. Detecting Module: IDCDU01
Source: DFSMSdfp
IDC21104I UNABLE TO DUMP SA nnnn MAIN
Detecting Module: IDCRS07 STORAGE
Explanation: An error occurred while the main storage
IDC21100I UNABLE TO DUMP MSC MAIN of the Staging Adapter was being read. The main
STORAGE storage for that Staging Adapter cannot be dumped.
Explanation: An error occurred while the Mass There is a preceding message that indicates the MSSC
Storage Control main storage was being read. The reason code associated with the error.
Mass Storage Control main storage cannot be dumped. In the message text:
There is a preceding message that indicates the MSSC
reason code associated with the error. nnnn The SSID value.
System Action: This dump request is bypassed. System Action: This dump request is bypassed.
Remaining dump requests are processed. Remaining dump requests are processed.
Application Programmer Response: Take the action Application Programmer Response: Take the action
associated with the MSSC reason code in the preceding associated with the MSSC reason code in the preceding
message. message.
Detecting Module: IDCDU01 Detecting Module: IDCDU01
IDC21101I LOWSECTOR X'll' IS GREATER THAN IDC21105I UNABLE TO DUMP SA nnnn

HIGHSECTOR X'hh'. EXTENDED STORAGE
Explanation: A sector range was specified incorrectly. Explanation: An error occurred while the extended
The low sector value was greater than the high sector storage of the Staging Adapter was being read. The
value. extended storage for that Staging Adapter cannot be
dumped. There is a preceding message that indicates
In the message text: the MSSC reason code associated with the error.
ll The low sector value. In the message text:
hh The high sector value. nnnn The SSID value.
System Action: This dump request is bypassed. System Action: This dump request is bypassed.
481
Remaining dump requests are processed. Source: DFSMSdfp
Application Programmer Response: Take the action Detecting Module: IDCCH01
associated with the MSSC reason code in the preceding
message.
IDC21143I ** INCOMPLETE READ REPORT
Source: DFSMSdfp PRODUCED, ERROR AT X LOCATION
xxx
Detecting Module: IDCDU01
Explanation: The AUDITMSS command is unable to
read the labels of all the requested cartridges.
IDC21109I ONE OR MORE REQUESTED
EXTENDED SECTORS ARE NOT In the message text:
AVAILABLE
xxx The X coordinate of the cell where the error
Explanation: One or more of the sectors requested for occurred.
a Staging Adapter extended storage dump are incorrect
in this configuration.
System Action: The incorrect sectors are bypassed,
command for the values not processed (all the cells with
but all valid requested sectors are dumped.
X coordinate equal to or greater xxx), after corrective
Application Programmer Response: Correct the action was taken as indicated in the primary message.
values for future dumps.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCCAU03
Detecting Module: IDCDU01
IDC21144I LOW XRANGE lowx IS GREATER THAN
IDC21125I SA 8x0 TABLES CANNOT BE READ: HIGH XRANGE highx
SA IS OFFLINE OR SUU.
Explanation: The low value in the XRANGES
Explanation: While interrogating the MSC (Mass parameter is greater than the high value. The values
Storage Control) main sectors 7C-7F, the staging must be in the range 150 through 247, and the low
adapter UCB for staging adapter 8 x 0 showed that value must not be greater than the high value.
either the staging adapter was incorrect or, if valid, that
the staging adapter was not online, not ready, or both.
The common definition for SUU (subsystem unit lowx The low range.
unusable) is valid and online but not ready.
highx The high range.
System Action: The request is bypassed. All
processing regarding this staging adapter is bypassed, System Action: The incorrect XRANGE is ignored,
and the remaining requests are attempted. and processing continues.
Application Programmer Response: If the staging Application Programmer Response: Correctly

adapter is offline, vary it online. If it is SUU, see specify the incorrect range and rerun the command.
Problem Determination. Resolve the equipment problem Source: DFSMSdfp
and then rerun the job.
Detecting Module: IDCCAU03
Source: DFSMSdfp
Detecting Module: IDCCH01 IDC21147I ** INCOMPLETE AUDIT REPORT
PRODUCED, ERROR WITHIN X RANGE
IDC21127I UNABLE TO READ STAGING ADAPTER Explanation: The AUDITMSS command is unable to
STORAGE check the status of all the requested cells. The X
Explanation: An error occurred while the system was coordinates of the range of cells that could not be
reading staging adapter main storage. Staging adapter checked are indicated by n1 n2.
main storage cannot be dumped. A message indicating System Action: The command ends.
the MSSC (Mass Storage System Communicator)
reason code for the error appears prior to this message. Application Programmer Response: Rerun the
command for the values not processed (all the cells
System Action: The request is bypassed, and the within the range n1 through n2), after corrective action
remaining requests are attempted. was taken as indicated in the primary message.
Application Programmer Response: Perform the Source: DFSMSdfp
response indicated in the description of the message
that identified the MSSC reason code. Detecting Module: IDCAU03

IDC21276I QCB FOR VOLUME volser HAS BEEN
MARKED IN ERROR
IDC21364I ERROR DETECTED BY DIAGNOSE:
Explanation: The QCB (queue control block) for the
{VVDS|ICFCAT} ENTRY: entry RECORD:
active, general-use volume has been marked in error.
rec OFFSET: offset REASON:
The volume being marked in error is valid only if the
reason-code
MSC (mass storage controller) is at EC level 737573 or
later. Explanation: The entry has an error indicated by the
reason code. The error occurred in the record specified,
where the record is either the key of the record in a
volser The volume serial number. BCS, or an RBA for a VVDS. In most cases, this
message is followed by an IDC21365I message that
System Action: The system ends with a message that
displays the record in error. An IDC21363I message
indicates the severity of the error.
summarizes all entries with errors at the conclusion of
Operator Response: None. the DIAGNOSE run.
Application Programmer Response: Use the In the message text:

NULLIFYC command with the NULLIFYQCBINERROR
entry The entry name. The entry name is
parameter to clear the error flag in the base volume
followed by a character which
record. You must also specify the ACTIVE and
indicates the entry type. See OS/390
VOLUME parameters.
DFSMS: Managing Catalogs for an
System Programmer Response: If the error recurs explanation of the entry types.
rec The record in which the error
occurred. If the record name is
followed by a number greater than
X'00', the record is an extension
record.
Source: DFSMSdfp
offset The offset into the record at which the
Detecting Module: IDCC001 error was found.
reason-code The reason code, as follows:
IDC21363I THE FOLLOWING ENTRIES HAD
Code Explanation
ERRORS
1 CELL LENGTH IS ZERO
Explanation: This message provides a summary of
the errors found by the DIAGNOSE FSR. Each entry Each record is composed of
name is followed by a reason code indicating the cells, each of which has a
specific error for that entry. For example: cell type and a cell length.
The indicated entry has a cell
SYS1.VVDS.VCATALG (D) - REASON CODE: 17 length of zero, which is an
error. This error may be
Here SYS1.VVDS.VCATALG is the entry name and 17 caused by incorrect
is the reason code. (D) is the entry type. positioning (caused by some
other error) or the length may
When the error was initially encountered, a specific actually be zero.
message was printed and a record dump may have 2 CELL TYPE NOT
been done. The IDC21363I message provides a RECOGNIZED
summary of the entries which had errors. For VSAM
data sets, the entry name may be a cluster, component Various catalog records can
(data or index), path or true name entry. For non-VSAM only contain certain cell
entries, the entry name may be an entry or an alias. types. The record being
analyzed contained a cell
System Action: DIAGNOSE ended processing of that type that either did not
particular entry and moved along to another entry. belong in the record or was
Application Programmer Response: Decide on the not a legal cell type. This
seriousness of the error and correct the error if need be. error may be caused by an
The reason codes set by DIAGNOSE are detailed below incorrect length in the
under message IDC21364I. preceding cell that resulted in
incorrect positioning.
Source: DFSMSdfp
483
3 RECORD TYPE NOT The record length at the front
RECOGNIZED of the record is not the same
as the length stored by
Each record in a BCS or
VSAM record management.
VVDS has an record type.
The record named has an 10 INCOMPLETE EXTEND
invalid type for integrated DETECTED
catalog facility catalogs.
The EXTEND function did not
4 UNEXPECTED RECORD ID execute to completion. The
ENCOUNTERED named entry was interrupted
in the middle of an
While processing an entry, a
EXTEND/EOV operation.
cell type was encountered
that signalled the beginning 11 INCOMPLETE DELETE
of a new record. This may be DETECTED
caused by an invalid length
The DELETE function did not
value or a damaged entry.
execute to completion. This
5 COMPONENT LENGTH IS may indicate existence of
ZERO partial record structures in
the BCS.
VSAM clusters and alternate
indexes, and generation data 12 CATLG AND VVDS NAMES
groups, have components. UNEQUAL
While checking one of these
There are four name fields in
types of entries, DIAGNOSE
a VVDS record. The BCS
found a component length of
entry and the VVDS entry do
zero. However, component
not have precisely the same
length should always be
names (length fields must
greater than zero.
also be the same) for one of
6 CELL LENGTH TOO LARGE the following four fields:
v Record name
A cell length was found that
v Subrecord name
is inconsistent with
v Component name
component or record length.
v Catalog name
This may describe the cell
being processed or the 13 VVDS AND VTOC EXTENT
preceding cell. SEQ. NO. UNEQUAL
7 CELL LENGTHS SUM AND VTOC sequence numbers
COMPONENT LENGTH start at 0; VVDS record
DISAGREE sequence numbers start at 1.
The VVDS record number
The sum of all cell lengths in
should always be one greater
a component is not equal to
than the VTOC number. An
the component length, which
exception to this rule is the
it should be. Either the
VVR sequence number for
component length is wrong or
key range data sets.
one of the cell lengths is
wrong. 14 CATLG AND VVDS VOLFLG
UNEQUAL
8 REPEATING CELL NOT
VALID VOLFLG is a field in the
VVDS record for the named
Although certain cells such
entry. This field has prime
as volume cells can occur
and overflow indicators. For
more than once in an entry,
the named entry, the
most cells may not. The
indicators in the BCS and
indicated cell occurred more
VVDS are not equal.
than once, but is a type of
cell that should not. 15 CATLG AND VVDS KEYS
UNEQUAL
9 RECORD LENGTH
INCORRECT BCS and VVDS records both
have high and low key fields.

The fields and their lengths point back to the non-VSAM
must be equal; they were data set record.
not.
22 TRUENAME NOT FOUND
16 VVDS AND VTOC
VSAM clusters with
STARTING CCHH
components have more than
UNEQUAL
one catalog entry. The
The extents in the VTOC associated components have
DSCB and VVDS record truename entries. A truename
were compared. They were entry was not found,
not equal, although they although there should be
should be. one.
17 VTOC ENTRY NOT FOUND 23 TRUENAME LOOP FAILURE
The data set control block The truename entry for a
(DSCB) for the named entry cluster did not point back to
could not be found in the the cluster record.
VTOC.
24 REQUIRED CELL MISSING,
18 VVDS ENTRY NOT FOUND CELL TYPE type
There should be a VVDS Depending on the component
entry for this BCS entry, but or entry type, certain cells
one could not be found. are required. The cell type
indicated is required, but
19 CATLG ENTRY NOT FOUND
missing.
The BCS should have an
25 ALLOCATE OF COMPARE
entry for the VVDS record,
DATA SET FAILED
but one could not be found.
The BCS named in the
20 ASSOCIATION NOT FOUND
VVDS record could not be
Certain types of BCS entries allocated.
may be paired with other
26 CELL TYPE INVALID IN
BCS entries. For example,
CONTEXT
catalogs, non-VSAM data
sets, and generation data The indicated cell is a valid
sets are paired with their cell type, but it is not valid for
aliases, and VSAM data sets the type of entry being
are paired with their paths. scanned.
This pairing of one record
27 ENTRY MISSING FROM
with another is called an
GAT CELL
“association.” Associations
between entries are Each generation data set
connected by name and are entry should be reflected in
indicated by an association the generation aging table
cell in an entry. The indicated (GAT) cell of the generation
association name cannot be data group entry. An entry is
found elsewhere in the BCS. missing.
21 ASSOCIATION LOOP 28 GAT CELL ENTRY NOT
FAILURE FOUND
For an explanation of Each entry in a GAT cell
“association”, see reason represents a generation data
code 20. If an association set entry within the current
can be found, but the generation data group
association does not point record. No generation data
back to the original entry, an set could be found for a GAT
association loop failure cell entry.
exists. For example, if a
non-VSAM data set has an 29 ENTRY MISSING FROM
alias, the alias record should REL CELL
485
Each alternate index entry is 38 CLUSTER AND EXTENSION
reflected in the REL RECS SMS MISMATCH
(“relation”) cell of the
A VSAM extension record
associated cluster record. An
indicates that the cluster is
alternate index entry was
SMS-managed, but the
found that was not reflected
associated cluster record
in a REL cell.
indicates that the cluster is
30 REL CELL ENTRY NOT not SMS-managed, or vice
FOUND versa.
An entry in a REL (“relation”) 39 BASE OR COMPONENT
cell in a cluster record does CELL NOT FOUND
not represent an alternate
Although a truename record
index entry.
was found for a component,
31 OPEN OF COMPARE DATA the associated cluster record
SET FAILED or component cell was not
found.
The BCS named in the
VVDS record could not be 40 COMPONENT CELL NOT
opened. FOUND
32 WRONG RECORD TYPE The component cell for a
VSAM cluster could not be
A BCS record which matches
found within the cluster’s
a VVDS record was found,
sphere record in the BCS.
but the BCS record is not a
cluster, truename, or 41 DUPLICATE VVR/NVRS IN
non-VSAM record. VVDS
33 INCOMPLETE UPDATE Two VVRs for a VSAM
DETECTED component, or two NVRs for
a non-VSAM data set, were
The current entry was
found in the VVDS. Both
undergoing a subrecord
records are displayed.
update/move operation that
did not complete. This record 42 NONSYSTEM DEFAULT
or subrecord may be CATALOG NAME IN VVDS
damaged.
The catalog named in the
34 VVDS AND VTOC ENDING VVDS record for an
CCHH UNEQUAL SMS-managed data set is
not the system default
The extent information kept
catalog. (The default catalog
in the VTOC and VVDS
is the catalog that is chosen
should agree, but do not.
for a data set when the
35 VVDS AND VTOC EXTENT catalog search is not being
COUNTS UNEQUAL directed by the user.)
The extent information kept 43 CATALOG AND VVDS SMS

in the VTOC and VVDS CONSTRUCTS UNEQUAL
should agree, but do not.
The storage class or
36 LENGTH OF NAME INVALID management class names
are not the same in the
The length of a name cell catalog and VVDS records.
should be from 1 to 45 The catalog and VVDS
characters long, but is not. records are displayed.
37 ASSOCIATION NAME CELL 45 VOLUME CELL NOT FOUND
NOT FOUND
A volume cell that matches
A BCS entry that matches a the volume serial number of
VVDS record was found, but the VVDS was not found.
the BCS entry was missing This may indicate an
its required association cell. orphaned VVDS record or

multiple VVDS records 1. Use DELETE NOSCRATCH to remove the sphere
pointing to the same BCS. or base record, if it exists.
2. Use DELETE TRUENAME to remove any remaining
46 VVDS ENTRY NOT FOUND.
association records.
ALLOCATION ERROR.
3. Reintroduce the removed entries into the catalog, by
An attempt to allocate the recataloging or redefining them. Introduce
BCS named in the VVR generation data sets into the generation data group
failed. in the proper order.

For VVDS records:
DATA SET OPEN ERROR.
1. Use DELETE NOSCRATCH to remove the entries
An attempt to open the BCS from the BCS, if they exist.
named in the VVR failed. 2. Use DELETE VVR or NVR to remove the damaged
VVDS records.
48 VVDS ENTRY NOT FOUND. 3. Restore the data set from a backup copy.
GET RECORD FAILED.
An attempt to get a For the following reason codes, recover as indicated:
VVR/NVR record that
Code Action
matches the BCS record
failed. 10 You should recover the data set. Records
existing in a data set prior to the aborted
extend operation should still be accessible if
SCAN RECORD FAILED.
the data set is opened for input only. You can
An attempt to get the specific retrieve these records by using the REPRO
VVR/NVR within the CI that command. After you retrieve the records, you
matches the BCS record can delete or redefine the data set. Then
failed. reinsert the records by using the REPRO
command.
GET VVDS FAILED. 11 You can finish the deletion process by
rerunning the DELETE job.
An attempt to get the entire
VVDS record that matches 12 If the catalog names disagree, remove the
the BCS record failed. entries in the BCS by using the DELETE
command with the NOSCRATCH option. At this
51 VVDS ENTRY NOT FOUND. point, if the VVDS record contains the desired
SCAN VVDS FAILED. catalog name, you can catalog the data set
An attempt to get the specific into the desired BCS by using the DEFINE
VVR/NVR within the VVDS RECATALOG command; otherwise, catalog the
that matches the BCS record data set into the catalog indicated in the VVDS
failed. record. (It will be necessary to define this
catalog if it does not exist.) Then move the
52 INVALID VOLSER FOR catalog record to the desired catalog by using
MIGRATION CELL. the REPRO MERGECAT command.
A Migration Cell was found in If the names that disagree are not catalog
the BCS, but the VOLSER in names, and if the VVDS record is correct,
the Volume Cell is not equal remove the entries from the BCS by using the
to ’MIGRATE’. DELETE command with the NOSCRATCH
53 RESERVED BITS SET IN option. Then use the DEFINE RECATALOG
CATALOG ALIAS ENTRY. command to recatalog the data set.
The alias entry shown If the VVR is incorrect, remove the data set by
contains reserved flags that using the EXPORT command. At this point,
are incorrectly set. you can import the data set using the IMPORT
command with the desired NEWNAMES
System Action: Processing continues with another parameter.
record.
25 Check for OPEN or allocation error messages
Application Programmer Response: Except for the to determine the source of the problem.
reason codes listed below, use the following procedures
to recover from these conditions: 31 Check for OPEN or allocation error messages
to determine the source of the problem.
For BCS Entries:
487
38 Delete the cluster entry with DELETE indicates which error; the record is the key or RBA of
NOSCRATCH, and recatalog it with DEFINE the record involved in the error. The first X'44' bytes of
RECATALOG. Then rebuild the alternate index the Format 1 DSCB are not displayed.
with DEFINE ALTERNATEINDEX and
BLDINDEX. In the message text:
41 Delete the data set. Then use DELETE VVR or rec The record in which the error occurred.
NVR to delete the duplicate VVDS record.
Recover the data set from a backup copy. System Action: The record is displayed and
DIAGNOSE continues.
42 Use REPRO MERGECAT to move the data
set’s catalog entry to the correct catalog. Application Programmer Response: Use this record
display to analyze the error and determine correction
43 Use DELETE NOSCRATCH to delete the BCS techniques.
record, and DEFINE RECATALOG to recreate
the BCS record. The storage class and System Programmer Response:
management class may be changed with If the error recurs and the program is not in error, look
ALTER if they are incorrect. at the messages in the job log for more information.
45 Delete the orphaned or extra VVDS records. Search problem reporting data bases for a fix for the
46 Determine if the BCS named in the VVR is Center. Provide the JCL, the SYSOUT output for the
valid. If necessary, see OS/390 DFSMS: job, and all printed output and output data sets related
Managing Catalogs for the appropriate to the problem.
recovery procedures.
Source: DFSMSdfp
47 Determine if the BCS named in the VVR is
valid. If necessary, see OS/390 DFSMS: Detecting Module: IDCDA03
Managing Catalogs for the appropriate
recovery procedures. IDC21372I xxxxxxxxxxxxxx IS NOT {AN
48 Determine whether the BCS entry or the ICFCATALOG|A VVDS}
VVR/NVR entry is in error. See OS/390 Explanation: The DDNAME or DSN given was not the
DFSMS: Managing Catalogs for the type indicated in the DIAGNOSE command syntax. If
appropriate recovery procedures. the data set to be scanned is an ICFCATALOG, the
49 Determine whether the BCS entry or the compare parameter should indicate a VVDS. If input
VVR/NVR entry is in error. See OS/390 data set is a VVDS, the compare parameter should
DFSMS: Managing Catalogs for the indicate an ICFCATALOG.
appropriate recovery procedures. In the message text:
50 Determine whether the BCS entry or the xxxxxxxxxxxxxx The indicated DD
VVR/NVR entry is in error. See OS/390 name or data set
DFSMS: Managing Catalogs for the name.
appropriate recovery procedures.
Application Programmer Response: Check for
51 Determine whether the BCS entry or the spelling error. Check for message IDC11373I to see if
VVR/NVR entry is in error. See OS/390 compare elements were not used during the
DFSMS: Managing Catalogs for the DIAGNOSE run. Correct the statement and resubmit the
appropriate recovery procedures. job.
53 Delete and redefine the alias entry to correct Source: DFSMSdfp
the problem.
Source: DFSMSdfp
Detecting Module: IDCDA02 IDC21404I dsname IS AN INVALID ASSOCIATION
FOR SPHERE TYPE
IDC21365I text RECORD DISPLAY: RECORD: rec Explanation: The data set is not a valid association
Explanation: text is one of the following: for its base object.
ICFCATALOG In the message text:
VVDS
VTOC dsname
The data set name.
The record which follows was involved in an error System Action: The base object and any of its
detected by DIAGNOSE. A previous error message associations already defined will be deleted from the

target catalog and the processing will continue with the v If the operation was a CNVTCAT, restore the
next base object. volumes, correct the problem and rerun the job.
v If the operation was a REPRO MERGECAT and the
delete failed for the source catalog, issue an Access
problem and rerun the job.
Method Services DELETE NOSCRATCH to remove
System Programmer Response: Enter the access the catalog entries for sphere dsname from the
method services LISTCAT command to list catalog source catalog.
entries and information about objects defined in the v If the delete failed for the target catalog, restore the
catalog. If the error recurs and the program is not in volumes, correct the problem and rerun the job.
error, look at the messages in the job log for more
information. Search problem reporting data bases for a
Support Center. Provide the JCL, the SYSOUT output
catalog.
for the job, and all printed output and output data sets
related to the problem. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCCC01
IDC21411I DATA SET dsname IS MARKED NOT
USABLE
IDC21409I CONVERSION FAILED FOR SPHERE
dsname Explanation: The specified data set has been marked
as not usable by a DELETE FORCE operation or by a
Explanation: The specified sphere base could not be
RESETCAT operation because of space occupancy
converted to the target catalog.
conflict.
dsname
dsname
The data set name.
The data set name.
System Action: Processing is continued with the next
System Action: If the sphere base and any of its
base object.
associations have been defined in the target catalog
Application Programmer Response: Correct the they will be deleted from the target catalog. Then
problem indicated in a preceding message and rerun processing is continued with the next base object.
the job.
Source: DFSMSdfp can be recovered by using the REPRO command. Then
reissue the CNVTCAT command.
IDC21410I DELETE OF SPHERE sph FROM entries and information about objects defined in the
{TARGET|SOURCE} CATALOG FAILED catalog.
Explanation: CNVTCAT or REPRO MERGECAT has Source: DFSMSdfp
attempted to delete a sphere from the source or target
catalog and has failed. When the sphere is not deleted Detecting Module: IDCCC02
from the source catalog, the sphere exists in both
source and target catalogs. When the sphere is not
IDC21412I DEFINE FAILED FOR dsname
deleted from the target catalog, only a partial sphere
may exist in the target catalog and the sphere exists in Explanation: The define failed for the specified data
the source catalog as it did before the processing set.
began.
dsname
sph The indicated sphere. The data set name.
System Action: Processing of the sphere is ended System Action: If dsname is a base object and any of
and processing continues with the conversion of the its associations have been defined in the target catalog,
next sphere’s base. dsname and its associations will be deleted from the
target catalog. The processing is continued with the
Application Programmer Response: You can
next base object. If dsname is a VSAM Volume Data
respond to one of the following conditions:
Set (VVDS), CNVTCAT processing is ended.
489
IDC21701I MAJOR ERRORS FOUND BY
catalog volume and all volumes owned by the catalog;
INDEXTEST
correct the problem and reissue the CNVTCAT
command. Explanation: INDEXTEST found major errors during
evaluation of the data set index component.
Source: DFSMSdfp
System Action: INDEXTEST concludes with a return
code of eight (8).
IDC21558I THE REQUEST FOR AN ACCESS
should not be accessed using the index prior to further
CODE CANNOT BE COMPLETED FOR
diagnostic testing. If DATATEST processing completes
CLUSTER X'cluster' - reason
successfully, you should be able to use export and
Explanation: The LISTDATA command to retrieve the import of the data set (via the EXPORT and IMPORT
remote access authorization code was not successful commands) to rebuild the index.
for the reason specified. In the message text:
Source: DFSMSdfp
cluster The 2 hexadecimal digit storage cluster
number.
IDC21702I MINOR ERRORS FOUND BY DATATEST
reason The reason for the error, as follows:
Explanation: DATATEST found minor errors during
v THE SUPPORT FACILITY IS NOT evaluation of the data set data component. Error
AVAILABLE messages displayed prior to this message describe
v THE MODEM ENABLE/DISABLE SWITCH whether the problem lies within the data repository or
IS NOT ENABLED the index sequence set.
System Action: Processing continues. System Action: DATATEST concludes with a return
code of four (4).
error. Ascertain why the access authorization code was Application Programmer Response: Minor errors do
not returned from the reason specified and resubmit the not generally result in loss of data. Regeneration of the
request when the access code is obtainable. data set, using a backup copy, is advisable to eliminate
any current or future problems.
Source: DFSMSdfp
Source: DFSMSdfp
IDC21703I MAJOR ERRORS FOUND BY

IDC21608I PAIR IS NOT IN SUSPENDED DUPLEX DATATEST
MODE, CANNOT {RESETTODUPLEX |
REESTABLISHDUPLEX} Explanation: DATATEST discovered one or more
major errors during evaluation of the data set data
Explanation: A SETCACHE command requiring that component. Error messages displayed prior to this
the duplex pair be in suspended mode was issued and message describe whether the problem lies within the
the devices were not in suspended duplex state. data repository or the index sequence set.
System Action: Processing continues. System Action: DATATEST concludes with a return
Application Programmer Response: None. code of eight (8).
Source: DFSMSdfp Application Programmer Response: Data validity is

in question; records may be missing, duplicated, or in
error. The data set must be reconstructed using a
IDC21700I MINOR ERRORS FOUND BY backup copy.
INDEXTEST
Source: DFSMSdfp
Explanation: INDEXTEST discovered minor errors
during evaluation of the data set index component.
IDC21803I STORAGE GROUP NAME name DOES
System Action: INDEXTEST concludes with a return NOT EXIST
code of four (4).
Explanation: The specified storage group name is not
Application Programmer Response: The discovered defined to the system.
errors should not affect normal processing; however, the
user may wish to verify or rebuild the data set to In the message text:
eliminate the diagnostic errors. name The storage group name.
Source: DFSMSdfp

System Action: Processing continues with the next 04 No functions to perform.
storage group.
05 Incorrect combinations of
Application Programmer Response: Verify validity of options.
specified storage group.
08 Error opening DFHSM control
System Programmer Response: If the error recurs data set.
01 DFSMShsm MCDS
could not be opened.
exists, contact the IBM Support Center. Provide the 02 DFSMShsm BCDS could
JCL, the SYSOUT output for the job, and all printed not be opened.
0C Error reading DFSMShsm control
Source: DFSMSdfp data set.
01 More than 10 read errors
IDC21804I FAILURE DURING function occurred accessing the
PROCESSING - RETURN CODE WAS DFSMShsm MCDS.
return-code, REASON CODE WAS
reason-code VOLSER WAS volser 02 More than 10 read errors
occurred accessing the
Explanation: The return code and reason code were DFSMShsm BCDS.
returned by catalog management module ARCUTIL,
DEVINFO, or VVAS as a result of an exceptional 03 User specified DUMMY
condition. The VOLSER line will only be output if the on the MCDS or BCDS
failure was from the VVAS. DD statement. This is
not accepted when
In the message text: requesting the
corresponding
function The name of the function that was
MCDS/BCDS statistics.
processing when the error occurred.
10 Error writing to the output data
set.
reason-code The reason code.
The reason code
volser The Volume Serial number. (Only if contains the contents of
VVAS failure.) register 1 received from
the SYNADAF macro.
System Action: Processing associated with the error
return code is ended. 14 An abnormal end occurred.
System Programmer Response: If the error recurs The reason code
and the program is not in error, look at the messages in contains the system
the job log for more information. Search problem completion code.
Function
DEVICE INFORMATION SERVICE
output and output data sets related to the problem. Code Reason Explanation
A list of the return and reason codes follow for each 00
function affected:
10
Function
MIGRATION DATA COLLECTION SERVICE 04 Storage for the
parameter list is not
Code Reason Explanation owned by the caller.
04 Incorrect parameter list. 08 Size of parameter list is
incorrect.
01 UPID not equal to
UPIDNAME. 0C Storage for the return
area is not provided or is
02 UPVERS incompatible
not owned by the caller.
with current version used
by ARCUTIL. 10 Storage for the volume
serial list is not owned
03 Data control block (DCB)
by the caller.
address not provided.
491
14 Storage for the device the VSAM volume data set
number list is not owned (VVDS). The reason code
by the caller. contains the VVDS Manager
return code. See the list of reason
18 Storage for the PDAREA
codes for IDC3009I, return code
is not provided, is not
50.
owned by the caller, or is
too small. 10 Processing error. The reason
code is the SVC number.
1C Storage for the return
area is too small to 20 Parameter list error.
contain at least a header
Source: DFSMSdfp
and one entry.
20 A bad resume code was
IDC21805I ATTEMPT TO ACQUIRE INFORMATION
passed by the caller.
FAILED FOR VOLSER volser
24 No matches were found;
Explanation: The specified volume was selected for
search arguments given
processing but extracted information was insufficient to
are too restrictive.
continue processing.
28 No requests specified.
2C Incorrect parameter list
level.
30 Conflicting features
volume.
request.
34 Incorrect device number
user control block (UCB) for this volume is valid.
passed.
38 Incorrect device number
passed.
3C A release call was made reporting data bases for a fix for the problem. If no fix
but there was no storage exists, contact the IBM Support Center. Provide the
to free. JCL, the SYSOUT output for the job, and all printed
14
Source: DFSMSdfp
04 The pointer in JESCT to
the EDT is zero.
IDC21807I FAILURE DURING function
18 An error return code was received
PROCESSING - RETURN CODE WAS
from common filter services.
return-code
1C An abend occurred.
Explanation: The return code was returned by the
20 A nonzero return code was named function as a result of an exceptional condition.
returned from IEFEB4UV.
24 A nonzero return code was
function
returned from DEVTYPE.
The name of the function, such as TRACK
Function CIRCULATION SERVICE or LSPACE service.
VTOC/VVDS ACCESS SERVICE
return-code
Code Explanation The return code. See OS/390 DFSMSdfp
Storage Administration Reference for the return
08 An error occurred while accessing codes to TRACK CIRCULATION SERVICE.
the volume table of contents
(VTOC). The reason code System Action: Processing associated with the error
contains the CVAFFILT return return code ends.
code. See OS/390 DFSMSdfp
Diagnosis Reference for more
information about the CVAF
reason code.
0C An error occurred while accessing exists, contact the IBM Support Center. Provide the

JCL, the SYSOUT output for the job, and all printed 04 Information for this data set could
output and output data sets related to the problem. not be calculated.
Source: DFSMSdfp 10 Return area provided is too small.
14 Associated with the following
IDC21809I FAILURE ATTEMPTING TO WRITE reason codes:
xx-TYPE RECORD FOR DATA SET
00 Size of parameter list is
dsname ON VOLUME volser
incorrect.
Explanation: The record built for the specified data
04 Parameter list not owned
set could not be written to the output data set.
be the caller.
08 Incorrect device
xx The type record. specification.
dsname 0C RTNAREA not specified
The data set name. (address is zero).
volser The volume serial number. 10 RTNAREA not owned by
caller.
14 PDAREA not specified
(address is zero).
problem. Run the utility again.
18 PDAREA not owned by
caller.
the job log for more information. Search problem 1C PDAREA too small.
20 DCSDS table not owned
by caller.
output and output data sets related to the problem. 24 No requests specified.
Source: DFSMSdfp 18 Error encountered in call to CVAF.
1C ABEND detected with RETRY
IDC21814I FAILURE DURING function parameter specified.
PROCESSING FOR dsname - RETURN
CODE WAS return-code 20 Storage unavailable.
Explanation: The return code was returned with the 24 DCS unable to open volume table
named function as a result of an exceptional condition. of contents (VTOC).
In the message text: 28 Error encountered in call to

device information services.
function The name of the function.
2C Error encountered in call to
dsname The data set name. TRKCALC for a globally used
value (value is not data
set-specific).
System Action: Processing associated with the error
Source: DFSMSdfp
return code ends.
IDC21815I ARCUTIL NOT CALLED. DATA
CONTROL BLOCK ADDRESS IS
INVALID
exists, contact the IBM Support Center. Provide the Explanation: The address of the output data set’s
JCL, the SYSOUT output for the job, and all printed data control block (DCB) cannot be passed to
output and output data sets related to the problem. ARCUTIL, which builds the records for migrated data
sets, backup versions, and capacity planning
A list of the return and reason codes follow for each
information. The severity is 8.
function affected:
System Action: Processing associated with ARCUTIL
Function
is bypassed.
DASD CALCULATION SERVICE
Operator Response: The output data set’s I/O is
Code Reason Explanation
being controlled by the user. If ″M″, ″B″, ″C″, or ″T″
493
records are required, IDCAMS must open the output Application Programmer Response: Ensure that the
data set so that the DCB can be passed to ARCUTIL. catalog to be reset is not in use as a master catalog
before issuing RESETCAT.
Application Programmer Response: If the error
recurs and the program is not in error, look at the Source: DFSMSdfp
the JCL, the SYSOUT output for the job, and printed IDC31004I DEFINE OF WORK FILE FAILED
Explanation: DEFINE failed for the work file. Message
IDC3009I precedes this message identifying the Catalog
IDC21862I DBCS CRITERIA ERROR IN RECORD Management return code which will indicate the reason
number AT OFFSET offset for failure.
Explanation: DBCS was specified on an access System Action: The RESETCAT command is ended.
method services (AMS) PRINT or REPRO copy of a No change has been made to the catalog or a Catalog
data set operation. AMS, while criteria checking DBCS Recovery Area (CRA).
characters to be printed or copied, detected that
characters indicated as DBCS do not meet criteria. Application Programmer Response: Take corrective
action as noted in the IDC3009I message.
Source: DFSMSdfp
offset The offset.
number The record number in the source data set.
System Action: Processing continues. The return IDC31005I WORK FILE DEFINED IN THE
code is 8. CATALOG TO BE RESET
Application Programmer Response: Make sure the Explanation: The work file was defined in the catalog
DBCS data meet the following criteria: to be reset.
v The data must be bracketed by paired SO and SI System Action: The RESETCAT command is ended.
characters when in combination with SBCS data. No change has been made to be catalog or a Catalog
v The number of bytes between the SO and SI Recovery Area (CRA).
characters must be even, since each DBCS character
requires two bytes to represent it. Application Programmer Response: Specify a
catalog other than the one being reset via the
Source: DFSMSdfp WORKCAT parameter, or specify another catalog as the
first concatenated entry in the JOBCAT or STEPCAT
statement.
IDC31000I CATALOG NOT A RECOVERABLE
CATALOG Source: DFSMSdfp
Explanation: The catalog specified for reset is not a Detecting Module: IDCRS02
recoverable catalog.
System Action: The RESETCAT command is ended. IDC31006I PHYSICAL I/O ERROR - VSAM ACTION
No change has been made to the catalog or a Catalog CODE actcde
Recovery Area (CRA).
Explanation: A physical I/O error on the catalog was
Application Programmer Response: Respecify the encountered while extending the catalog.
catalog to be reset.
Source: DFSMSdfp
actcde The action code.
System Action: The RESETCAT command is ended.
IDC31001I SYSTEM MASTER CATALOG Application Programmer Response: Correct the

SPECIFIED FOR RESET physical error and reissue RESETCAT. The VSAM
action code can be found in the OS/390 DFSMS Macro
Explanation: The master catalog was specified for Instructions for Data Sets . The catalog and CRA entries
reset. The master catalog cannot be reset while it is in have not been altered and hence are recoverable in
use as a master catalog. their current state - barring the I/O error.
System Action: The RESETCAT command is ended. Source: DFSMSdfp
No change has been made to the catalog or a Catalog
Recovery Area (CRA). Detecting Module: IDCRS07

IDC31007I LOGICAL I/O ERROR - VSAM ACTION IDC31012I MAXIMUM RELATIVE RECORD
CODE actcde NUMBER EXCEEDED IN WORK FILE
Explanation: A logical I/O error was encountered Explanation: The work file relative record number (rrn)
while extending the catalog during RESETCAT. There limit has been exceeded. No more records can can be
were not enough free records in the catalog being reset, written to the work file. The resultant catalog is too
consequently RESETCAT attempted to get more. large.
In the message text: System Action: The operation is ended.
actcde The action code. Application Programmer Response: Respecify
subsets of the CRA volumes specified for reset and
System Action: The operation is ended.
issue multiple RESETCAT commands. The catalog
Application Programmer Response: Correct the entries have not been altered.
logical error. The VSAM action code can be found in
Source: DFSMSdfp
OS/390 DFSMS Macro Instructions for Data Sets. If the
catalog has reached 16 extents and cannot be Detecting Module: IDCRS06
extended further, a larger catalog may be defined in
which to perform the RESETCAT. The catalog and CRA
IDC31013I COULD NOT MERGE ONE OR MORE
entries have not been altered.
CRAS
Source: DFSMSdfp
Explanation: See preceding message which indicates
Detecting Module: IDCRS07 that:
v Open failed for CRA (IDC3300I)
v Close failed for CRA (IDC3301I)
IDC31008I ERROR ACCESSING THE CATALOG
v CRA does not belong to catalog to be reset
Explanation: RESETCAT encountered an error trying (IDC31010I)
to access the data set specified by the CATALOG
parameter. Message IDC3009I precedes this message
identifying the specific error. Application Programmer Response: Correct the
error in the referenced message and reissue the
command. The catalog entries have not been altered.
Source: DFSMSdfp
error specified in the IDC3009I message and reissue
the command. If the error is not correctable, a new Detecting Module: IDCRS01
catalog of the same name may be defined into which all
of the volumes owned by the failing catalog may be
IDC31014I DELETE OF WORK FILE FAILED
reset using RESETCAT. The entries in the catalog have
not been altered. Explanation: DELETE failed for the work file.
Message IDC3009I precedes this identifying the specific
Source: DFSMSdfp
error.
Application Programmer Response: Unless some
IDC31010I CRA DOES NOT BELONG TO
previous message indicates an ending error, the
CATALOG - VOL volser
RESETCAT operation has been completely performed.
Explanation: The CRA was specified for reset, but it The work file may be deleted using the DELETE
belongs to a catalog other than the catalog to be reset. command after correcting the error indicated in
message IDC3009I.
Source: DFSMSdfp
IDC31016I NO CRA SPECIFIED FOR RESET
correct volume to be reset and reissue the command.
Explanation: The CRAFILES parameter specified no
Source: DFSMSdfp
CRA with the ALL option; hence, no volume was
Detecting Module: IDCRS01 specified for reset.
495
correct volumes for reset and issue the command.
IDC31035I BAD VOLUME RECORDS FOR volser
Source: DFSMSdfp
Explanation: In a CRA, either the volume record for
Detecting Module: IDCRS01 the volser indicated does not exist or one of its
secondary records does not exist (IEC11022I). If
IGNORE was specified, the reset will occur. This may
IDC31017I UNABLE TO GET EXCLUSIVE USE OF mean that all data sets allocated on this volume will be
THE CATALOG marked unusable. If NOIGNORE was specified, the
Explanation: Some other task is open to the catalog RESETCAT operation ends before updating the catalog
requested to be reset. The RESET operation is unable or CRA(s).
to reset a catalog without exclusive use. In the message text:
System Action: The operation is ended. volser The volume serial number.
Application Programmer Response: For the catalog System Action: The command may end (see
being reset, specify DISP=(OLD,KEEP) on the DD Explanation).
statement, or get exclusive use. Reissue the command.
Application Programmer Response: If IGNORE was
Source: DFSMSdfp specified, no error exists in the catalog; accompanying
Detecting Module: IDCRS01 messages will indicate any action taken on individual
data sets as a result of this. If NOIGNORE was
specified, use EXPORTRA to export all VSAM data sets
IDC31018I CRA UNAVAILABLE on this volume, FORCE DELETE the volume, and use
Explanation: RESETCAT required a volume that could IMPORTRA to recover all data sets.
not be allocated. Source: DFSMSdfp
System Action: The operation is ended. Detecting Module: IDCRS01, IDCRS03
Application Programmer Response: A secondary
CRA volume was required during the reset of a catalog IDC31038I COULD NOT UPDATE ONE OR MORE
and it was not available. If enough units are not CRAS
available, specify the volume via a DD statement and
include that DD statement in the CRAFILES parameter Explanation: See preceding message which indicates
on the command indicating NONE. See message that:
IDC21020I. v Open failed for CRA (IDC3300I)
v Close failed for CRA (IDC3301I)
Source: DFSMSdfp
error in the referenced message and reissue the
IDC31019I CRA volser SPECIFIED FOR RESET command. The catalog entries have been updated but
MORE THAN ONCE the CRA entries have not.
Explanation: The CRAVOLS parameter specified the Source: DFSMSdfp
same volser more than once, or the CRAFILES
parameter specified the same volser more than once via Detecting Module: IDCDA01, IDCRS01
ddnames.
In the message text: IDC31126I UNABLE TO READ MSC MAIN
STORAGE
Explanation: An error occurred while the system was
System Action: The operation is ended. reading MSC (Mass Storage Control) main storage.
Application Programmer Response: Specify the MSC main storage cannot be dumped. A message
correct volumes for reset and reissue the command. indicating the MSSC (Mass Storage System
Communicator) reason code for the error appears prior
Source: DFSMSdfp to this message.
Detecting Module: IDCRS01 System Action: The operation is ended.
Application Programmer Response: Perform the
response indicated in the description of the message
that identified the MSSC reason code.
Source: DFSMSdfp

IDC31160I TOSTAGINGDRIVE SSID SPECIFIED IS
NOT A VALID MSC TABLES SSID
IDC31143I ** INCOMPLETE {CHECK|READ}
Explanation: The SSID specified as a target for the
REPORT PRODUCED, ERROR AT X
table copy is not a valid mass storage control table
LOCATION xxx
SSID. The SSID must be X'000', X'002', X'004', or
Explanation: The AUDITMSS command is unable to X'006'.
check the status of all the requested cells, or to read
System Action: Processing of this command ends.
the labels of all the requested cartridges.
specify the SSID used with the TOSTAGINGDRIVE
xxx The X coordinate of the cell where the error parameter, and rerun the command.
occurred.
Source: DFSMSdfp
Detecting Module: IDCST01
Application Programmer Response: Reissue the
command for the values not processed (all the cells with
IDC31170I UNABLE TO DETERMINE PRIMARY
X coordinate equal to or greater than xxx), after
MSC TABLES LOCATION
corrective action was taken as indicated in the primary
message. Explanation: The attempt to read the Mass Storage
Control main storage to determine the primary mass
Source: DFSMSdfp
storage control tables location failed. The information
Detecting Module: IDCAU03 necessary to build the SSID for the primary tables is not
available.
IDC31145I ** NO READ REPORT PRODUCED, System Action: Processing of this command ends.
ERROR AT X LOCATION xxx
Explanation: The AUDITMSS command is unable to command after the problem with the Mass Storage
read the labels of any of the requested cartridges. Control has been corrected.
xxx The X coordinate of the cell where the error Detecting Module: IDCST01
occurred.
System Action: The command ends. IDC31180I PRIMARY TABLES CANNOT BE
COPIED TO WORK DATA SET
command for the values not processed (all the cells with Explanation: The primary mass storage control tables
X coordinate equal to or greater than xxx), after cannot be copied to the work data set.
corrective action was taken as indicated in the primary
message.
Source: DFSMSdfp
work data set is allocated properly, and rerun the
Detecting Module: IDCAU03 command.
Source: DFSMSdfp
IDC31148I ** NOT AUDIT REPORT PRODUCED,
Detecting Module: IDCCP01
ERROR WITHIN X RANGE n1 n2
Explanation: The AUDITMSS command is unable to
IDC31181I SECONDARY TABLES CANNOT BE
check the status of any of the requested cells.
COPIED TO WORK DATA SET
Explanation: The secondary mass storage control
n1 n2 The X coordinates of the range of cells that tables cannot be copied to the work data set.
could not be checked.
command for the values not processed for all the cells
work data set is allocated properly, and rerun the
within the range n1 through n2, after corrective action is
command.
taken as indicated in the primary message.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCCP01, IDCEC01
Detecting Module: IDCAU03
497
in error, search problem reporting data bases for a fix
IDC31201I REPAIRRANGE PARAMETER cchhr1 GT
for the problem. If no fix exists, contact the IBM Support
cchhr2 FOR dsname
Explanation: The named repair work file (repair work job.
file) keys in the REPAIRRANGE parameter of REPAIRV
Source: DFSMSdfp
DISPLAY were incorrectly specified.
cchhr1 The first key, which is greater than the second,
IDC31203I UNIT INDICATES A VIRTUAL DEVICE
identifies a record address.
Explanation: The unit address specified in the DD
cchhr2 The second key identifies a record address.
statement referred to by INFILE indicates a virtual
dsname device; if the STAGINGRANGE parameter was
The data set name. specified, the unit specified must be real. Either the
STAGINGRANGE parameter is incorrect or you have
System Action: REPAIRV DISPLAY ends. Control
specified the wrong unit parameter in the JCL.
returns to access method services. The return code is
12. System Action: REPAIRV DISPLAY/COPY ends.
Application Programmer Response: Correct
code is 12.
REPAIRRANGE so that the second key is greater than
or equal to the first key and resubmit. Application Programmer Response: Either change
the unit parameter in the JCL to a real unit or change
STAGINGRANGE to DATASETRANGE, as appropriate,
and resubmit.
Source: DFSMSdfp
Detecting Module: IDCRD02 and the SYSOUT output for the job.
Source: DFSMSdfp
IDC31202I BEGINNING KEY volsercchhr DOES
NOT EXIST FOR dsname
Explanation: The first key specified in
IDC31204I STAGING PACK VOL=SER=volser NOT
REPAIRRANGE of REPAIRV DISPLAY was not found in
FOUND IN STAGINGRANGE
the specified repair work file. Either the volume serial
number is incorrect, the address is incorrect, or the Explanation: The volume serial number of the staging
repair work file is not the one containing the specified pack specified in STAGINGRANGE of REPAIRV
record. DISPLAY/COPY does not match the volume serial
number specified in the VOL=SER= parameter (as
shown in the message) of the DD statement referred to
volser The volume serial number. by INFILE. The JCL and REPAIRV syntax must
correspond.
cchhr The five hexadecimal characters that identify
the record address. In the message text:
dsname volser The volume serial number.

The repair work file.
System Action: REPAIRV DISPLAY/COPY ends
System Action: REPAIRV DISPLAY ends. Control control returns to access method services. The return
returns to access method services. The return code is code is 12.
12.
Application Programmer Response: Correct correct volume serial number and correct either the job
REPAIRRANGE to specify a valid key for the first record control language or STAGINGRANGE, as appropriate,
to be displayed. Ensure that the repair work file dsname and resubmit.
is correct and that the key specified is in that work file.
Resubmit.
System Programmer Response: Enter the access reporting data bases for a fix for the problem. If no fix
method services PRINT command to print the repair exists, contact the IBM Support Center. Provide the JCL
work data set. If the error recurs and the program is not and the SYSOUT output for the job.

Source: DFSMSdfp
IDC31207I INCORRECT STAGINGRANGE cchhr
Explanation: A count of characters specified in the
STAGINGRANGE parameter of the REPAIRV DISPLAY
IDC31205I INVALID STAGINGRANGE cchhr FOR or the REPAIRV COPY command showed the length of
DEVICE TYPE the address to be other than 5, the DISPLAY to be
other then 3, or COPY to be other than 1 in the volume.
Explanation: The address in the STAGINGRANGE Anything other than 5, 3, or 1 is incorrect.
parameter of REPAIRV DISPLAY/COPY is not valid for
the device type specified in the UNIT parameter of the In the message text:
DD statement specified by the ddname parameter of
cchhr Identify a record in the track.
INFILE. Either a portion of STAGINGRANGE is incorrect
or the UNIT parameter is incorrect. System Action: REPAIRV DISPLAY/COPY ends.
code is 12.
cchhr Identify a record address.
System Action: REPAIRV DISPLAY/COPY ends. STAGINGRANGE and resubmit.
code is 12.
Application Programmer Response: Determine the reporting data bases for a fix for the problem. If no fix
correct device type of the staging pack and correct exists, contact the IBM Support Center. Provide the JCL
either STAGINGRANGE or the UNIT parameter in the and the SYSOUT output for the job.
job control language, as appropriate, and resubmit.
Source: DFSMSdfp
Ensure that the cc is a valid cylinder address and hh a
valid head (track) address for the device. Detecting Module: IDCRD07
and the program is not in error, search problem IDC31208I STAGINGRANGE cchhr1 GT cchhr2 FOR
reporting data bases for a fix for the problem. If no fix STAGING PACK VOL=SER=volser
Explanation: The record address parameters in the
STAGINGRANGE parameter of the REPAIRV DISPLAY
Source: DFSMSdfp or the REPAIRV COPY command were incorrectly
specified for the volume. The first key is greater then
the second key specified in this parameter.
IDC31206I AUTHORIZATION TO ACCESS TO
STAGINGPACK VOL=SER=volser cchhr1 The first key specified. It indicates a record
DENIED BY SYSTEM OPERATOR address.
Explanation: The system operator has responded “N” cchhr2 The second key specified. It indicates a record
to REPAIRV’s request (IDC499D) for access to the address.
specified volume.
System Action: The REPAIRV DISPLAY or the
volser The volume serial number. REPAIRV COPY command ends. Control returns to
access method services. The return code is 12.
System Action: REPAIRV DISPLAY/COPY/MODIFY
ends. Control returns to access method services. The Application Programmer Response: Correct
return code is 12. STAGINGRANGE so that the second key (cchhr) is
greater then or equal to the first key (cchhr) and
Application Programmer Response: Check with the
resubmit.
appropriate system operations personnel for the reason
for access denial. System Programmer Response: If the error recurs
Source: DFSMSdfp Detecting Module: IDCRD07
499
the data set whose records are to be processed and
IDC31209I INCORRECT INDATASET PARAMETER
correct either the JCL or parameter as appropriate, and
FORMAT4.DSCB
resubmit.
Explanation: The dsname in INDATASET refers to a
volume’s VTOC, which is an incorrect specification for
this parameter.
System Action: REPAIRV DISPLAY/COPY ends. exists, contact the IBM Support Center. Provide the JCL
Control returns to access method services. The return and the SYSOUT output for the job.
code is 12.
Source: DFSMSdfp
Application Programmer Response: Verify the name
of the volume or data set containing the records you
want processed. If the data set name is a volume’s
VTOC, use the INFILE parameter and specify IDC31211I UNIT INDICATES A REAL DEVICE FOR
FORMAT4.DSCB as the data set name on the DD dsname
statement of INFILE. Otherwise, specify a valid data set
name in INDATASET; that is, one referring to a data set Explanation: The unit parameter specified in the DD
cataloged in the system master catalog, a catalog statement referred to by INFILE indicates a real device;
specified in a STEPCAT or JOBCAT DD statement, or a it must indicate a Mass Storage volume. Either the data
catalog having the data set’s highest level qualifier as set name is incorrect or you have specified the wrong
an alias. unit parameter in the JCL.

and the program is not in error, search problem dsname
reporting data bases for a fix for the problem. If no fix The data set name.
and the SYSOUT output for the job. System Action: REPAIRV ends. Control returns to
access method services. The return code is 12.
Source: DFSMSdfp
Application Programmer Response: Either change
Detecting Module: IDCRD07 the unit in the job control language to a virtual unit or
change the parameters as appropriate, and resubmit.
IDC31210I VOL=SER=volser IN parameter DOES System Programmer Response: If the error recurs
NOT MATCH THE VOLSER IN DD and the program is not in error, search problem
STATEMENT ddname reporting data bases for a fix for the problem. If no fix
Explanation: The volume serial number in the exists, contact the IBM Support Center. Provide the JCL
parameter does not match the volume serial number and the SYSOUT output for the job.
specified in VOL=SER parameter of the DD statement Source: DFSMSdfp
referred to by INFILE. The JCL and REPAIRV syntax
must correspond. Detecting Module: IDCRD07
Valid parameter values follow:

v DATASETRANGE IDC31212I DATASETRANGE cchhr1 TO cchhr2 NOT
v INDATASETADDRESS WITHIN EXTENTS OF dsname
v OUTDATASETADDRESS Explanation: The address range specified in
v VTOCHEADERADDRESS DATASETRANGE is outside the extents of the specified
v VTOCHEADER data set.
volser The volume serial number. cchhr1 The first key of the range. It indicates a record
address.
parameter
The specified parameter. cchhr2 The second key of the range. It indicates a
record address.
ddname
The specified DD name. dsname
The data set name.
ends. Control returns to access method services. The System Action: REPAIRV DISPLAY/COPY ends.
return code is 12. Control returns to access method services. The return
code is 12.
correct volume serial number of the volume containing Application Programmer Response: Determine the

actual extents of the data set. Correct the Application Programmer Response: Correct RANGE
DATASETRANGE parameters of the named data set to specify a valid key for the first record to be
and resubmit. deblocked. Ensure that the repair work file is the one
desired and that the key specified is in that work file.
Resubmit.
output and output data sets related to the problem. exists, contact the IBM Support Center. Provide the JCL
Source: DFSMSdfp
Source: DFSMSdfp
IDC31213I (hh1) GREATER THAN hh2 FOR dsname
IDC31220I HEADER RECORD EITHER NOT
Explanation: The stage error record keys in the
FOUND OR INVALID FOR dsname
RANGE parameter of REPAIRV DEBLOCK were
incorrectly specified for repair work file. The first key is Explanation: Either no header record was found at
greater than or equal to the second key. the beginning of the specified file (repair work) or the
record found was not a valid header record, indicating
that this file is not a repair work file.
hh1 The first key.
hh2 The second key.
dsname
dsname The data set name.
The data set name.
System Action: REPAIRV DEBLOCK ends. Control
System Action: REPAIRV DEBLOCK/MODIFY ends. returns to access method services. The return code is
Control returns to access method services. The return 12.
code is 12.
Application Programmer Response: Correct the job
Application Programmer Response: Correct RANGE control language to indicate the appropriate repair work
or INREPAIRRANGE so that the second key (hh) is file or recreate the repair work file using REPAIRV
greater then or equal to the first key (hh) and resubmit. COPY and resubmit.
System Programmer Response: If the error recurs System Programmer Response: Enter the access
and the program is not in error, search problem method services PRINT command to print the repair
reporting data bases for a fix for the problem. If no fix work data set. If the error recurs and the program is not
exists, contact the IBM Support Center. Provide the JCL in error, search problem reporting data bases for a fix
and the SYSOUT output for the job. for the problem. If no fix exists, contact the IBM Support
Source: DFSMSdfp job.
Detecting Module: IDCRD04 Source: DFSMSdfp
IDC31214I FIRST KEY (volsercchh) IN THE RANGE
NOT FOUND FOR dsname
IDC31221I RECORD IN INDATASETADDRESS
Explanation: The first key specified in RANGE was volsercchhr NOT FOUND FOR dsname
not found in the repair work file. Either the volume serial
number is incorrect, the address is in correct, or the Explanation: The specified record is not in the
repair work file is not the one desired. referenced input data set. That is, the address specified
is not within the extents of the specified data set or
In the message text: within the first track of the VTOC (VTOCHEADER).
volser The volume serial number. Either the address is incorrect or the wrong data set
was specified.
cchh The address of a record.
dsname
The data set name. volser The volume serial number.
System Action: REPAIRV DEBLOCK ends. Control cchh The address of a record.
12.
501
dsname In the message text:
The data set name.
System Action: REPAIRV MODIFY ends. Control
12. dsname
The output data set name.
actual extents of the data set, then correct the parameter
INDATASETADDRESS parameter and resubmit. The specified parameter.
System Programmer Response: If the error recurs System Action: REPAIRV MODIFY ends. Control
and the program is not in error, search problem returns to access method services. The return code is
reporting data bases for a fix for the problem. If no fix 12.
JCL, the SYSOUT output for the job, and all printed Application Programmer Response: Determine the
output and output data sets related to the problem. actual address of the record. Correct the
OUTDATASETADDRESS or VTOCHEADER parameter
Source: DFSMSdfp and resubmit.
Detecting Module: IDCRD05 System Programmer Response: If the error recurs
IDC31222I RECORD IN INREPAIRKEY volsercchhr
NOT FOUND FOR dsname
Explanation: The record specified in INREPAIRKEY is output and output data sets related to the problem.
not in the referenced repair work file.
Source: DFSMSdfp
cchh The address of a record. IDC31224I RECORD IN OUTREPAIRKEY
volsercchhr NOT FOUND FOR dsname
dsname
The repair work file. Explanation: The record specified in OUTREPAIRKEY
is not in the referenced repair work file.
returns to access method services. The return code is In the message text:
12.
Application Programmer Response: Display the
repair work file records. If necessary, recreate the repair
work file using REPAIRV COPY, or correct the dsname
INREPAIRKEY parameter, and rerun. The repair work file.
System Programmer Response: Enter the access System Action: REPAIRV MODIFY ends. Control
method services PRINT command to print the repair returns to access method services. The return code is
work data set. If the error recurs and the program is not 12.
for the problem. If no fix exists, contact the IBM Support Application Programmer Response: Display the
Center. Provide the JCL and the SYSOUT output for the repair work file records. If necessary, recreate the repair
job. work file using REPAIRV COPY, or correct the
OUTREPAIRKEY parameter, and resubmit.
Source: DFSMSdfp
Detecting Module: IDCRD05 method services PRINT command to print the repair
work data set. If the error recurs and the program is not
IDC31223I RECORD volsercchhr IN parameter NOT
FOUND FOR dsname VTOCHEADER
Explanation: The record specified in job.
OUTDATASETADDRESS or VTOCHEADERADDRESS
Source: DFSMSdfp
is not in the specified user data set. That is, the address
specified is not within the extents of the specified output Detecting Module: IDCRD05
data set or within the first track of the VTOC
(VTOCHEADER).

INREPAIRRANGE parameter to specify only allocated
IDC31225I RECORD volsercchhr IN parameter
tracks and resubmit.
DOES NOT MATCH THE FIRST
INREPAIRRANGE ADDRESS System Programmer Response: Enter the access
method services PRINT command to print the repair
Explanation: Both OUTDATASETADDRESS or
VTOCHEADERADDRESS and INREPAIRRANGE were
specified, indicating a full track replacement is to be
performed.
In the message text: job, and all printed output and output data sets related
to the problem.
Source: DFSMSdfp
cchhr The address of a record, where r of the
VTOCHEADERADDRESS or Detecting Module: IDCRD05
OUTDATASETADDRESS volume must be 0 to
indicate the beginning of the track or did not
IDC31227I RECORD ZERO FOR volsercchh WAS
match the first INREPAIRRANGE address.
NOT FOUND IN dsname
parameter
Explanation: Record zero in the stage error deblocked
The specified parameter.
track specified in the message could not be found in the
System Action: REPAIRV MODIFY ends. Control specified repair work file. Either the volume serial
returns to access method services. The return code is number or the range in INREPAIRRANGE is incorrect.
12.
address in OUTDATASETADDRESS or
VTOCHEADERADDRESS to ensure a 0 in the record cchh The address of a record.
field, and a match to the INREPAIRRANGE first
address. dsname
and the program is not in error, search problem System Action: REPAIRV MODIFY ends after the
reporting data bases for a fix for the problem. If no fix entire range. Control returns to access method services.
exists, contact the IBM Support Center. Provide the JCL The return code is 12.
and the SYSOUT output for the job. Application Programmer Response: Display the
Source: DFSMSdfp repair work file records. If necessary, recreate the repair
work file using REPAIRV COPY. Correct
Detecting Module: IDCRD05 INREPAIRRANGE and resubmit.
IDC31226I NOT ALL TRACKS SPECIFIED IN method services PRINT command to print the repair
INREPAIR RANGE ARE ALLOCATED work data set. If the error recurs and the program is not
TO OUTPUT text in error, search problem reporting data bases for a fix
dsname
job.
VTOCHEADER
Source: DFSMSdfp
Some or all of the tracks specified in INREPAIRRANGE
do not exist within the extents allocated for the specified
data set or VTOCHEADER. No modification is done.
IDC31228I RECORD volsercchhr IS NOT A
In the message text: DEBLOCKED STAGE ERROR RECORD
IN dsname
dsname
The specified data set name. Explanation: The indicated record in the input repair
work file specified in INREPAIRRANGE is not a stage
error deblocked record. The input record range contains
records other than ones having stage errors which have
12.
been corrected by DEBLOCK.
actual extents of the data set. Correct the
503
cchhr The address of a record. n The offset.
dsname System Action: REPAIRV MODIFY ends. Control
The repair work file. returns to access method services. The return code is
12.
System Action: REPAIRV MODIFY ends after
checking the entire range. Control returns to access Application Programmer Response: Correct the
method services. The return code is 12. OFFSET parameter and resubmit.
Application Programmer Response: Correct System Programmer Response: Enter the access
INREPAIRRANGE and resubmit. method services PRINT command to print the repair
to the problem.
job. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCRD05
IDC31231I INPUT RECORD TOO LARGE
{dsname|VTOCHEADER}
IDC31229I DEBLOCKED TRACK cchh TOO LARGE
FOR dsname Explanation: A record that was to replace another
record in the specified output data set or
Explanation: The modified records from the specified
VTOCHEADER does not fit in the output data set track.
repair work file will not fit within the track of the
specified data set. Either one or more records have In the message text:
been lengthened or added to the original track, or you
dsname
are moving from a device with longer tracks to one with
The output data set name.
shorter tracks.
cchh The address of a record. 12.
dsname Application Programmer Response: Ensure that the
The specified data set name. replacement record will fit in the output data set track.
System Action: REPAIRV MODIFY ends. Control System Programmer Response: Enter the access
returns to access method services. The return code is method services PRINT command to print the repair
12. work data set. If the error recurs and the program is not
Application Programmer Response: Verify that your
input is correct and will fit within the specified track.
System Programmer Response: Enter the access job.
Source: DFSMSdfp
in error, search problem reporting data bases for a fix Detecting Module: IDCRD05
IDC31232I MODIFIED RECORD TOO LARGE FOR
job.
{dsname|VTOCHEADER}
Source: DFSMSdfp
Explanation: The input string specified in the
Detecting Module: IDCRD05 command causes the record being modified to exceed
the track boundaries of the specified data set or repair
work file or VTOCHEADER.
IDC31230I OFFSET n OUTSIDE KEY OR DATA
FIELD In the message text:
Explanation: The offset specified for the key or data dsname
field is longer than the actual key or data field length. The specified data set name or repair work file.
In the message text: System Action: REPAIRV MODIFY ends. Control

returns to access method services. The return code is ends. Control returns to access method services. The
12. return code is 12.
Application Programmer Response: Verify that the Application Programmer Response: Determine the
input string does not cause the modified record to correct device type of the data set and correct either the
exceed its track boundary. cchhr in the parameter or the UNIT parameter in the job
control language, as appropriate, and resubmit. Ensure
that cc is a valid cylinder address and hh is a valid head
(track) address for the device.
Source: DFSMSdfp
Detecting Module: IDCRD05 and the SYSOUT output for the job.
Source: DFSMSdfp
IDC31233I INCORRECT parameter cchh FOR
dsname
Explanation: A count of characters specified in the
IDC31235I DATASETRANGE cchhr1 GT cchhr2
parameter of REPAIRV DISPLAY/COPY/MODIFY
FOR dsname
showed the length of the record address to be other
than 5, or COPY to be other then 3. Anything other then Explanation: The parameters in the DATASETRANGE
5 or 3 is incorrect. parameter of REPAIRV DISPLAY/COPY were incorrectly
specified. The first key is greater than the second key
specified in this parameter.
parameter
The specified parameter.
cchhr1 The first key specified. It indicates the address
of a record.
dsname
cchhr2 The second key specified. It indicates the
address of a record.
dsname
ends. Control returns to access method services. The
return code is 12.
System Action: REPAIRV DISPLAY/COPY ends.
parameters and resubmit.
code is 12.
DATASETRANGE so that the second cchhr is greater
then or equal to the first cchhr and resubmit.
and the SYSOUT output for the job. System Programmer Response: If the error recurs
Source: DFSMSdfp
Detecting Module: IDCRD07 exists, contact the IBM Support Center. Provide the JCL
IDC31234I INVALID PARAMETER cchhr FOR Source: DFSMSdfp

DEVICE
Explanation: The address parameter of REPAIRV
DISPLAY/COPY/MODIFY is not valid for the device type
IDC31237I THE SUM OF THE LENGTH
specified in the UNIT parameter of the DD statement
SUBPARAMETERS IS TOO
specified by the ddname parameter of INFILE. Either a
{LARGE|SMALL}
portion of the parameter is incorrect or the UNIT
parameter is incorrect. Explanation: The DEBLOCK function tried to use the
key and data lengths provided in the LENGTH
subparameters and the total sum of these lengths is
cchhr The address of a record. either larger or smaller than the actual sum of the
original records.
505
System Action: REPAIRV DEBLOCK ends. Control System Programmer Response: If the error recurs
returns to access method services. The return code is and the program is not in error, search problem
12. reporting data bases for a fix for the problem. If no fix
Application Programmer Response: Correct the key
and data lengths specified in the LENGTH parameter
are correct: display the R‘0/R’1 records, correct, and Source: DFSMSdfp
rerun.
IDC31240I OUTDATASETADDRESS cchhr DOES
NOT REFER TO A RECORD IN VTOC
for the problem. If no fix exists, contact the IBM Support Explanation: The record address value in the
Center. Provide the JCL and the SYSOUT output for the OUTDATASETADDRESS parameter of the MODIFY
job. function is not within the range of the VTOC.
Detecting Module: IDCRD04 cchhr The address of a record.
IDC31238I UNABLE TO DEFINE dsname returns to access method services. Return code is 12.
Explanation: REPAIRV COPY was not able to define Application Programmer Response: Correct the
the repair work file as specified in the DD statement condition causing the failure.
referred to by OUTFILE. The last message issued prior
to this one explains why the attempted definition failed. System Programmer Response: If the error recurs
dsname
The specified data set name.
Source: DFSMSdfp
System Action: REPAIRV COPY ends. Control
returns to access method services. The return code is Detecting Module: IDCRD07
12.
Application Programmer Response: Correct the IDC31241I NEWCOUNT MUST BE EIGHT BYTES
condition causing the failure. LONG
System Programmer Response: If the error recurs Explanation: The length specified in the NEWCOUNT
and the program is not in error, search problem parameter is less than 8 bytes long.
exists, contact the IBM Support Center. Provide the JCL System Action: REPAIRV MODIFY ends. Control
and the SYSOUT output for the job. returns to access method services. The return code is
12.
Source: DFSMSdfp
Detecting Module: IDCRD03 NEWCOUNT parameter to be exactly 8 bytes long.
IDC31239I VTOCHEADERADDRESS cchhr DOES and the program is not in error, search problem
NOT REFER TO THE FIRST TRACK OF reporting data bases for a fix for the problem. If no fix
VTOC exists, contact the IBM Support Center. Provide the JCL
Explanation: The VTOCHEADERADDRESS
parameter of the MODIFY function is not the first track Source: DFSMSdfp
of the VTOC of the output volume.
cchhr The address of a record. IDC31242I BAD RECORD
{PRECEDING|SUBSEQUENT TO}
System Action: REPAIRV MODIFY ends, control
RECORD volsercchhr IN OUTPUT
dsname
12.
Explanation: It is necessary to read all records in the
track to calculate if the record to be modified would fit in
condition causing the failure.

the track; either a previous or subsequent record to the In the message text:
one to be modified had an I/O error in the repair work
file.
System Action: The command ends. The return code
is 12.
Application Programmer Response: Verify that you
cchh The address of a record. specified the correct address in the command. The R‘1
record can be replaced in the repair work file or in the
dsname
original data set with the correct records from another
source by using the REPAIRV MODIFY command.
System Action: REPAIRV MODIFY ends. Control Alternatively, the R‘1 record can be restored by using
returns to access method services. The return code is the REPAIRV MODIFY command.
12.
Application Programmer Response: Rerun the job; method services PRINT command to print the repair If
the error should correct itself, that is, it either goes away the error recurs and the program is not in error, search
or becomes a destage error. problem reporting data bases for a fix for the problem. If
System Programmer Response: If the error recurs the JCL and the SYSOUT output for the job. work data
and the program is not in error, search problem set.
Source: DFSMSdfp
Detecting Module: IDCRD05 IDC31245I AN UNCORRECTABLE I/O ERROR
WAS ENCOUNTERED WHILE
MODIFYING cchh OF dsname
IDC31243I THE COUNT OF RECORD ZERO cchhr
CANNOT BE MODIFIED Explanation: An I/O error was encountered while
writing to the specified data set.
Explanation: The user tried to modify the count, or
increase the length of the data field or insert a key in a In the message text:
record zero address, which is not permissible.
dsname
cchhr The address of a record. The repair work file.
System Action: REPAIRV MODIFY ends. Control System Action: REPAIRV MODIFY processing ends.
returns to access method services. The return code is Control returns to access method services. The return
12. code is 12.
Application Programmer Response: Ensure that you Application Programmer Response: The results are
really want to modify record zero; if you are going to unpredictable. Run REPAIRV DISPLAY command to
modify record zero, you are allowed only to modify the display the track on which the error occurred to
data field without increasing its length. Resubmit. determine how much of modify process completed. Take
appropriate action to reconstruct data.
IDC31246I OBTAIN FAILED FOR dsname
Source: DFSMSdfp
Explanation: OBTAIN SVC failed for the specified
data set name.
IDC31244I UNABLE TO DEBLOCK cchh
dsname
Explanation: The record pair (R‘0 or R‘1) that results
from the stage error could not be deblocked because
the R‘1 record contained a dummy data field length of System Action: REPAIRV ends. Control returns to
1. This condition is caused by the loss of the track access method services. The return code is 12.
descriptor during staging.
Application Programmer Response: If processing a
507
VSAM data set, ensure that unit and volume information
IDC31265I A SECURE MOUNTED VOLUME
are not present on the DD statement for the specified
CANNOT BE COPIED
data set name. Correct the condition causing the failure
and resubmit. Explanation: A secure volume cannot be copied while
it is mounted. The COPYV command checks the
inventory data set to see if the DASDERASE flag is on
before attempting to copy the volume.
exists, contact the IBM Support Center. Provide the JCL System Action: The command ends.
Source: DFSMSdfp COPYV command specifying NOT MOUNTED.
Detecting Module: IDCRD07 Source: DFSMSdfp
IDC31247I TRACK DOES NOT BEGIN WITH
RECORD 1
IDC31366I INPUT DATA SET IS NOT {AN
Explanation: The data portion of record pair R‘0, ICFCATALOG|A VVDS}
which shows the original first record number, shows that
Explanation: The data set to be diagnosed was not
record number to be other than record 1.
an ICF catalog or a VVDS as the type indicated in the
System Action: The command ends. The return code DIAGNOSE command syntax. If the data set to be
is 12. scanned is an ICF catalog, the syntax should be
‘DIAGNOSE ICFCATALOG’; if the data set is a VVDS,
Application Programmer Response: Issue REPAIRV
the syntax should be ‘DIAGNOSE VVDS’.
DISPLAY to display the blocked stage error records R‘0
and R‘1. If the records appear to be valid, usable System Action: The DIAGNOSE processing ends.
records that you want to deblock, issue REPAIRV
MODIFY to change the R‘0 data portion of record 0,
statement and resubmit the job.
mapping the original record number of record 1 to the
value 1. Then, after issuing REPAIRV DISPLAY to verify Source: DFSMSdfp
your change, issue REPAIRV DEBLOCK to deblock
your blocked stage error records. Detecting Module: IDCDA01

method services PRINT command to print the repair IDC31368I CATALOG MAY NOT BE SPECIFIED
work data set. If the error recurs and the program is not WITH ICFCATALOG
in error, search problem reporting data bases for a fix Explanation: The CATALOG parameter may not be
for the problem. If no fix exists, contact the IBM Support coded as an include or exclude subparameter for
Center. Provide the JCL and the SYSOUT output for the ICFCATALOG. CATALOG qualification is only intended
job. for diagnosis of a VVDS.
Source: DFSMSdfp System Action: DIAGNOSE considers this an error
Detecting Module: IDCRD04 condition; processing ended.
IDC31251I CARTRIDGE NOT EJECTED DIAGNOSE statement and rerun the job. If DIAGNOSE
is being run against an ICFCATALOG, replace the
Explanation: An unsuccessful attempt was made to catalog parameter with either ENTRIES or LEVEL. If not
eject a cartridge with the DIRECTEJECT option of the analyzing a catalog but a VVDS, change the
MODIFYC command. The location of the cartridge is not ICFCATALOG parameter to VVDS.
known.
Source: DFSMSdfp
System Action: The MODIFYC command ends. The
return code is 12. Detecting Module: IDCDA01
Source: DFSMSdfp
IDC31369I text PROCESSING TRUNCATED
Detecting Module: IDCRD04, IDCMC01
MAXIMUM ERROR LIMIT REACHED
I/O ERROR ON INPUT DATA SET
The number of errors encountered in the input or

compared data sets has reached the error limit value.

This message may also result from I/O errors, if so, v Uplevel the BCS.
message IDC3351I, which precedes IDC31369I, may be v Re-run DIAGNOSE.
used to determine the cause of the I/O error. In either
Source: DFSMSdfp
case, this may be indicative of a badly damaged input
data set.
IDC31377I FIRST CATALOG ENTRY NOT FOUND
System Action: DIAGNOSE considers this an error
condition; processing ended. Explanation: DIAGNOSE cannot locate the first ICF
catalog entry. The self describing cluster entry for the
catalog is absent or damaged.
ERRORLIMIT value is too low, set a different value and
rerun the job. ERRORLIMIT has a default value, System Action: The system ends processing.
determine the default value (you may wish to allow
DIAGNOSE to detect more errors than the default Application Programmer Response: Take the
value) and rerun the job. If the problem is an I/O error, following actions.
the data set is too damaged for DIAGNOSE to analyze. v Import the BCS to restore it.
Consider initiating BCS or VVDS recovery procedures. v Uplevel the BCS.
v Re-run DIAGNOSE.
Source: DFSMSdfp
Source: DFSMSdfp
IDC31400I UNABLE TO OBTAIN CATALOG NAME

IDC31370I UNABLE TO OBTAIN INFORMATION
ON {dsname|ddname} Explanation: CNVTCAT did not receive either the
source or target catalog name. The source catalog is
Explanation: An attempt to extract allocation identified via the INFILE or INDATASET parameter and
information for the named data or dd statement has the target catalog via the OUTFILE, OUTDATASET or
failed. If the data set in question is the input data set, CATALOG parameter.
DIAGNOSE cannot continue. If the data set in question
is a compare data set then compare processing cannot System Action: The command is ended.
occur. Application Programmer Response: Correct the
In the message text: specification of the catalog and rerun the job.
dsname Source: DFSMSdfp

The data set name. Detecting Module: IDCCC01
ddname
The DD name. IDC31401I UNABLE TO GET NEXT BASE OBJECT
System Action: DIAGNOSE considers this an error dsname
condition; processing may end or continue, depending Explanation: Catalog management could not get the
on which data set incurred the error. next base object and the catalog end of file has not
Application Programmer Response: Check the been reached.
spelling of the named data set or dd statement. Correct In the message text:
and then rerun the job. If the spelling is not in error,
contact your service representative. dsname
The data set name.
Source: DFSMSdfp
Detecting Module: IDCDA01 catalog volume, and all volumes owned by the catalog,
correct the problem identified in the associated
IDC31376I INPUT CATALOG HAS NO VVDS message and rerun the job.
ENTRIES System Programmer Response: Enter the access
Explanation: The ICF catalog that the system is method services LISTCAT command to list catalog
currently diagnosing has no SYS1.VVDS.Vvoler entries. entries and information about objects defined in the
This indicates BCS damage; there should be a VVDS catalog.
entry for the volume. Source: DFSMSdfp
System Action: The system ends DIAGNOSE Detecting Module: IDCCC01
processing.
Application Programmer Response: Take the
following actions.
v Import the BCS to restore it.
509
and rerun the job. If correct, the master catalog must be
IDC31403I UNABLE TO DETERMINE CATALOG
made a user catalog before it may be converted.
TYPE FOR dsname
Source: DFSMSdfp
Explanation: A catalog management LOCATE failed
and the catalog type could not be determined. Detecting Module: IDCCC01
IDC31440I SPACE PARAMETER IS INVALID FOR
dsname
AN ICF CATALOG
The data set name.
Explanation: The catalog selected by LISTCAT to be
listed was an ICF catalog. ICF catalogs do not contain
Application Programmer Response: Correct the space entries. This message is issued if a single entry
problem identified in the associated message and rerun type parameter of ‘SPACE’ is specified or if multiple
the job. types have been specified and one of them is ‘SPACE’.
This message is also issued if the ENTRIES parameter
is specified for a space entry and the CATALOG
parameter is not specified and all catalogs searched are
ICF catalogs.
catalog.
Source: DFSMSdfp
Application Programmer Response: Check if the
correct catalog has been specified to be listed. Check
either the LISTCAT CATALOG parameter or the
IDC31405I INVALID COMBINATION OF CATALOGS STEPCAT JOBCAT DD parameter. If none are
FOR CONVERT specified, then the master catalog must be an ICF
catalog.
Explanation: Prior to converting an OS CVOL or a
VSAM catalog it was determined that the source and System Programmer Response: If the error recurs
target object types constitute an incorrect conversion and the program is not in error, search problem
combination. The source and target object types were reporting data bases for a fix for the problem. If no fix
such that the conversion could not be allowed. The exists, contact the IBM Support Center. Provide the
following are valid source and target combinations: SYSOUT output for the job.
Source Target Source: DFSMSdfp
OS CVOL VSAM Detecting Module: IDCLC01
OS CVOL ICF
IDC31461I REPRO MERGECAT FROM MASTER
VSAM ICF CATALOG NOT ALLOWED
System Action: Processing of this command is Explanation: During REPRO catalog validation, it was
ended. found that the source catalog specified by the user is
Application Programmer Response: Correct the the system master catalog. All objects that have been
source and/or target catalog specification and rerun the successfully merged are deleted from the source
job. catalog; therefore, merging from the master catalog
cannot be allowed.
Source: DFSMSdfp
System Action: Processing of this command is
Detecting Module: IDCCC01 ended.
IDC31406I CONVERSION OF THE SYSTEM source catalog name specification. If in error, correct
MASTER CATALOG NOT ALLOWED and rerun the job. If correct, the master catalog must be
Explanation: During catalog validation, it was found made a user catalog before it may be merged.
that the source catalog specified by the user is the System Programmer Response: If the error recurs
system master catalog. All entries are deleted from the and the program is not in error, look at the messages in
source catalog during conversion and thus conversion the job log for more information. Search problem
of the master catalog cannot be allowed. reporting data bases for a fix for the problem. If no fix
System Action: Processing of this command is exists, contact the IBM Support Center. Provide the JCL
ended. and the SYSOUT output for the job.
Application Programmer Response: Verify the Source: DFSMSdfp

source catalog name specification. If in error, correct

IDC31503I UNABLE TO OBTAIN DEVICE
INFORMATION
IDC31466I THE SOURCE DATA SET CANNOT BE
Explanation: A DEVTYP (device type) macro
A type
instruction, issued by a program, failed to obtain cchh
Explanation: The type is either CVOL or CATALOG. boundaries, probably because of a system error.
DBCS was specified on an access method services
System Action: The system does not process the
(AMS) REPRO copy of a data set. AMS, while checking
request.
the data set type, detected that the source data set was
either a catalog or CVOL. REPRO will not copy a Application Programmer Response: Probable
catalog or CVOL if DBCS is specified. system error. Add an AMSDUMP DD statement to the
JCL, and run the program again.
Source: DFSMSdfp
type The specified type.
Detecting Module: IDCBD01
System Action: The command is ended. The return
code is 12.
IDC31504I NOT ENOUGH ROOM IN THE CACHE
Application Programmer Response: Recheck the
TO HOLD THE SPECIFIED DATA
specification of the data set name to ensure the proper
data set was processed. If you intend to copy a catalog Explanation: The LOWCCHH and HIGHCCHH
or CVOL, remove the DBCS keyword from your parameters specify more data to be bound than can be
command. contained in the available cache space of the 3880
device.
Source: DFSMSdfp
IDC31467I MAXIMUM ERROR LIMIT REACHED Application Programmer Response: Issue the
LISTDATA command with the STATUS parameter to
Explanation: The number of errors encountered has
determine how much cache space is available. If the
reached the error limit value.
amount of offline space available is excessive, contact
System Action: Processing terminates. your programming support personnel.
Application Programmer Response: If ERRORLIMIT Change the values of the LOWCCHH and HIGHCCHH
value is too low, set a different value and rerun the job. parameters to fit the available cache space. Then issue
ERRORLIMIT has a default value (you may wish to the BIND command again.
allow REPRO to detect more errors than the default
Source: DFSMSdfp
value) and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCI001
IDC31550I UNABLE TO LOCATE ANY CACHING
SUBSYSTEM DEVICES ONLINE
IDC31502I SPECIFIED cchh IS NOT IN BOUNDS
Explanation: The user issued either a LISTDATA or
OF THE 3380
SETCACHE command, but the system could not find
Explanation: The record address has the value of any subsystem devices online for the associated UNIT
LOWCCHH or HIGHCCHH, as specified on the and VOLSER.
BINDDATA command. The value should be in range for
System Action: Processing is ended for this
the device attached to the Model 13.
command.
Application Programmer Response: Do the
cchh The address of a record. following:
System Action: The command is not processed. v Ensure that the correct UNIT and VOLSER are
specified.
Application Programmer Response: Correct the v Make sure there are volumes online. You can use the
command and resubmit. DEVSERV PATHS command to determine the
Source: DFSMSdfp volume and path status.
v Rerun the command.
Detecting Module: IDCBD01, IDCSS04
Source: DFSMSdfp
511
Return Code 4: Reason Codes
IDC31559I ASYNCHRONOUS OPERATIONS
MANAGER RC=return-code 4 INSUFFICIENT STORAGE
REASON=reason-code other
GETMAIN failure occurred within the service.
Explanation: An IDCAMS channel program was This may indicate that the region size for your
passed to the asynchronous operations manager. The IDCAMSjo job or your region size for TSO/E
resulting return and reason codes from the needs to be increased. IDCAMS should have
asynchronous operations manager were unexpected. issued IDC2011I when this error code was
returned. Please refer to IDC2011I for details
on the error condition. If the GETMAIN failure
return-code The return code from the is for a system area, then a system message
asynchronous operations manager. indicating the failure appears on the system
console and you should follow the directions
reas The reason code from the
for the system message.
asynchronous operations manager.
8 INVALID PARAMETER LIST
other Additional information, when available,
from the asynchronous operations Internal error. IDCAMS should have issued
manager: IDC31601I or IDC31550I for this error
v 32 bytes of I/O sense data in the condition. Please refer to this message for
form: further details on the error.
SENSE BYTES 0-15 xxxxxxxx xxxxxxxx
xxxxxxxx xxxxxxxx 12 UNAUTHORIZED REQUEST
16-31 xxxxxxxx xxxxxxxx
xxxxxxxx xxxxxxxx
IDCAMS was not authorized for this request.
Sense data will be returned when Possible reasons are that IDCAMS was
available. invoked via a TSO/E CALL command, was not
linkedited as authorized, or does not reside in
v ABEND CODE=abndcde: the an authorized library. Contact your systems
abend code returned from the programmer.
asynchronous operations manager
for return code 12, reason code 8. 16 UNABLE TO ESTABLISH ESTAE
v INTERNAL QUEUE ERROR Internal error. IDCAMS should have issued
CODE=internal queue error return IDC2391I for this error condition. Please refer
code: the code returned from the to this message for further details on the error
asynchronous operations manager condition.
for return code 12, reason code 4.
20 INVALID CCW OR DATA AREA POINTER
v Blank when no additional
information is available. Internal error. IDCAMS should have issued
message IDC31602I for this condition. Please
The Asynchronous Operations Manager return and refer to this message for further details on the
reason codes are: error condition.
24 INVALID REQUEST TYPE FOR CONTROL
Return Codes UNIT
0 SUCCESSFUL Internal error.
The request to the service completed without 28 SUBSYSTEM DATA AREA NOT LARGE
error. ENOUGH
4 REQUEST FAILED Internal error.
The request to the service failed with the 32 UNABLE TO LOCATE SSSCB ENTRY
reason code specified below.
Internal error.
8 OPERATION FAILED
36 REQUEST BUFFER SIZE NOT A MULTIPLE
The request to the service failed with the OF 8
Internal error.
12 ASYNCHRONOUS OPERATIONS MANAGER
ERROR 40 CONFIGURATION TABLE INDEX TOO HIGH
The request to the service failed with the Internal error.
44 SSSCBUPD VALUE(S) INVALID

Internal error. 132 INVALID EYE-CATCHER IN INPUT BUFFER
48 UNABLE TO OBTAIN COMPLETE SSSCB Internal error.
ENTRY
136 SSDP POINTS AT AREA NOT OWNED BY
Internal error. CALLER
52 DEVICE NUMBER INVALID Internal error.
Internal error. 140 AOM services caller requested an operation
56 UCB ADDRESS OR DEVICE NUMBER against an exposure address of a multiple
NEEDED FOR RACF CHECK exposure device, which was supported prior to
MVS/ESA SP 5.2. AOM services caller
Internal error.
requested an operation against an alias device
60 INVALID RACF LEVEL number of a parallel access volume.
Internal error.
76 ONLY ONE ACCESS CODE AVAILABLE
4 I/O ERROR EXECUTING CALLER’S
Internal error. CHANNEL PROGRAM
80 INVALID EYE-CATCHER IN SERVL OR An I/O error occurred. IDCAMS issues
UNABLE TO ACCESS LAST BYTE IN SERVL message IDC31559I when sense data is
available. Otherwise IDCAMS issues message
Internal error. IDC2375I. Please refer to that message for
84 UCB ADDRESS OR DEVICE NUMBER further information on the error condition.
POINTS AT NON-DASD DEVICE 8 ASYNCHRONOUS OPERATION PENDING
Internal error. The asynchronous operation is still in progress
88 SSDL MISSING and IDCAMS should still be waiting for
completion.
Internal error.
12 ASYNCHRONOUS OPERATION COMPLETED
92 REQTYPE DRVR PARM(S) NOT ALLOWED IN ERROR
Internal error. IDCAMS should have issued IDC2391I for this
96 SSDP AND SSDL NOT ALLOWED error condition. Please refer to that message
for details on the error.
Internal error.
16 ASYNCHRONOUS OPERATION FAILED
100 REQUEST BUFFER HAS ONLY ONE
SUB-BUFFER IDCAMS should issue IDC31610I message for
this error condition. Refer to that message for
Internal error. details on the error.
104 INDIRECT ADDRESS LISTS NOT ALLOWED 20 ASYNCHRONOUS OPERATION TIME OUT
IN DRVR CHANNEL PROGRAM
The asynchronous operation is still in progress,
Internal error. but the timer for IDCAMS waiting for the
108 TIC MUST POINT AT *-8 operation has expired. When the asynchronous
operation completes, if it ’Fails’ or ’Completes
Internal error. In Error’ an AOM000I message will be issued
to the system console. If the operation is
112 UCB ADDRESS OR DEVICE NUMBER
successful the status will be correctly reflected
MISSING
in the storage control and in all attached host
Internal error. systems. Generally this error will occur while
establishing or reestablishing a dual copy pair
116 SSDP MISSING
and contention from other hosts or the host
Internal error. trying to do the operation cause time to be
taken away from the 3990 copy operation to
124 NO 3990 MODEL 3 IN THE SYSTEM service these other I/O operations.
Internal error. 24 REQUEST LOST BY SUBSYSTEM
128 INVALID REQUEST FOR REQTYPE MULTI The storage control lost knowledge of the
Internal error. asynchronous operation. Please refer to a
merged LOGREC listing for more details.
513
Running an IDCAMS LISTDATA report will give System Action: Processing continues.
you the current state of the subsystem and
Application Programmer Response: For MVS/ESA
device. After determining the current state, you
or MVS/XA, refer to OS/390 DFSMSdfp Storage
may need to rerun your IDCAMS job to
Administration Reference for the meanings of CVSTAT
establish the new states that you desire.
codes. For OS/390, see OS/390 MVS System Data Set
28 DESTAGE-ALL DID NOT COMPLETE Definition.
SUCCESSFULLY
For logical errors, return codes 4 and 12, contact your
Message AOM001I is issued for failing local IBM support personnel. For VTOC structure errors,
subsystem. Refer to message AOM001I for return code 8, and for I/O errors, return code 16, correct
information on the problem determination the cause of the error and resubmit the job.
required to isolate the devices attached to the
Source: DFSMSdfp
subsystem that have pinned data.
32 I/O ERROR EXECUTING INTERNAL
IDC31562I THE parameter PARAMETER IS NOT
CHANNEL PROGRAM
AVAILABLE FOR THE SPECIFIED
Internal error. SUBSYSTEM OR DEVICE
36 I/O ERROR, RETRIES EXHAUSTED FOR Explanation: A LISTDATA or SETCACHE command
CALLERS CHANNEL PROGRAM was issued. Either a parameter that is not supported on
the device specified was encountered or a hardware
Permanent I/O error.
error might have caused the device to be unable to
40 AN ATTEMPTED I/O OPERATION RESULTED perform the requested command. This message is also
IN A CONDITION CODE 3. printed if:
Permanent I/O error. v The device specified for a duplex pair secondary or
alternate device is not attached to a 3990 Model 3 or
44 AN I/O OPERATION TO A DEVICE Model 6.
ENCOUNTERED AN INTERVENTION v DIRECTOR (SD) is requested for a device not
REQUIRED CONDITION. attached to a 3880 Model 21.
v SETCACHE REINITIALIZE, SETCACHE
SUBSYSTEM OFF, SETCACHE NVS OFF, or
4 INTERNAL QUEUE ERROR LISTDATA ACCESSCODE is issued to the secondary
device of a duplex pair.
Internal error.
v DUAL COPY OPERATION (SETSECONDARY,
8 ABNORMAL TERMINATION SUSPENDPRIMARY, SUSPENDSECONDARY,
Internal error. RESETTODUPLEX, REESTABLISHDUPLEX,
RESETTOSIMPLEX) was issued to a 2105 storage
System Action: Processing continues. control unit.
Application Programmer Response: If the sense
data is returned, find the returned sense data in IBM In the message text:
3990 Storage Control Reference. Otherwise, refer to parameter
IBM 3990 Operations and Recovery Guide. The parameter that is not applicable for the
Source: DFSMSdfp specified subsystem.
For SETCACHE, unsupported parameters
IDC31561I VTOC ACCESS ERROR RC=return-code include:
CVSTAT=stat ADDR=cccchhhhrr v CACHEFASTWRITE
v DASDFASTWRITE
Explanation: The LISTDATA command to print a v DESTAGE
PINNED TRACK REPORT was issued and was v DIRECTOR
unsuccessful. The attempt to access the VTOC for the v DISCARDPINNED
volume failed. v NVS
v PENDINGOFF
v REESTABLISHDUPLEX
return-code The decimal return code from a v REINITIALIZE
CVAFSEQ or CVAFDIR macro. v RESETTODUPLEX
v RESETTOSIMPLEX
stat The CVAF status code in decimal.
v SETSECONDARY
cccchhhhrr The hexadecimal address in the v SUSPENDPRIMARY
VTOC of the DSCB being read. v SUSPENDSECONDARY

v UNITNUMBER
IDC31602I LOAD REAL ADDRESS FAILED ON I/O
v DEVICE
OPERATION
v SUBSYSTEM
Explanation: The Load Real Address (LRA)
For LISTDATA, unsupported parameters assembler instruction failed during an I/O operation.
include: This is probably a system error.
v DSTATUS
System Action: The system could not process the
v PINNED
instruction.
v ACCESSCODE
Application Programmer Response: Add an
AMSDUMP DD statement to the JCL and run the
Application Programmer Response: Resubmit the program again.
job, specifying the appropriate device. Check the status
of the device to verify that it can perform the requested
command.
Source: DFSMSdfp
IDC31564I THE SUBSYSTEM WILL NOT SUPPORT Detecting Module: IDCSS03

PAGING MODE: THE CACHE MUST BE
INITIALIZED
IDC31604I UNITTYPE SPECIFIED IS NOT A VALID
Explanation: This message is issued when a SUBSYSTEM UNITTYPE
permanent error occurs and the subsystem can no
Explanation: The unit type specified in the unit
longer support paging. The message appears at the end
parameter was not valid. 3350 and 3380 are valid unit
of the subsystem status report containing the status
types for LISTDATA and SETCACHE commands. 3380
counts at the time the error occurred.
is the only valid unit type for a BINDDATA command.
System Action: The cache is initialized when MVS is This message is also issued if the request is not
IPLed (if the subsystem is online), or during the first supported for the storage control model.
PAGEADD command.
System Action: Processing is ended for this
Application Programmer Response: IPL MVS with command.
the subsystem online, or set the subsystem online after
Application Programmer Response: Change the unit
the IPL and do a PAGEADD to initialize the cache.
type and reissue the command.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCBD01, IDCLA01, IDCSC01
IDC31601I VOLUME volser NOT ON A CACHING
SUBSYSTEM
IDC31606I UNABLE TO action -PROBABLE CAUSE
Explanation: The FILE or VOLUME parameter
IS cause -VOLUME volser
specifies a volume that is not on a caching subsystem.
Explanation: A SETCACHE or LISTDATA request
cannot be run because the state of the subsystem or
volser The volume serial number. device is not as required.
System Action: The system does not process the For a SETCACHE request, action and cause can be
command with the FILE or VOLUME parameter. replaced with the following values:
Application Programmer Response: Probable user Action Causes/Responses

error, or the operator varied offline the device with the
SET DEVICE CACHING ON
specified volume.
-PINNED DATA: Probable cause for the device
Correct the DD statement associated with the FILE being in pending state is pinned data. In order
parameter, or correct the volser on the VOLUME for the device to be activated for caching the
parameter. Make sure that the required device is online. pinned data must first be discarded
Then issue the command again. (SETCACHE DISCARDPINNED).
Source: DFSMSdfp A PINNED TRACK REPORT can be generated

(LISTDATA PINNED), and the data set with
Detecting Module: IDCSS02 pinned retriable or non-retriable tracks can then
be copied to a device prior to discarding the
515
pinned data. (Possible utilities for copying the discarding the pinned data. (Possible utilities
data set are IEBCOPY and IEBGENER.) For for copying the data set are IEBCOPY and
other types of pinned data, reaccess and try to IEBGENER.) For other types of pinned data,
destage or discard. reaccess and try to destage or discard.
SET DEVICE CACHING OFF SET NVS ON
-DASDFASTWRITE FAILED: The ‘DASD fast -PINNED DATA: Probable cause for the NVS
write failed’ condition exists for this device. The being in pending state is pinned data. To
command is ended and results in no action activate the NVS, the pinned data for each
taken. volume must first be discarded (SETCACHE
DISCARDPINNED). If the volume is a DASD
DISCARDPINNED
fast write volume and in pending state, the
-DASDFASTWRITE FAILED: The ‘DASD fast
data can be discarded with a SETCACHE
write failed’ condition exists for this device. The
DASDFASTWRITE PENDINGOFF. A PINNED
command is ended and results in no action
TRACK REPORT can be generated
taken.
(LISTDATA PINNED), and then the data set
DESTAGE with pinned retriable or non-retriable tracks can
-NVS FAILED: The nonvolatile storage is be copied to a device prior to discarding the
failed. The command is ended and results in pinned data. (Possible utilities for copying the
no action taken. data set are IEBCOPY and IEBGENER.) For
other types of pinned data, reaccess and try to
SET SUBSYSTEM STORAGE OFF destage or discard.
-NVS FAILED: The nonvolatile storage is
failed. The command is ended and results in -PINNED DATA OR NVS FAILED: If the DASD
no action taken. FAST WRITE volumes show pending in the
‘STATUS REPORT’ or NVS is failed (which is
SET SUBSYSTEM STORAGE ON caused by a malfunction or NVS being taken
-PINNED DATA: Probable cause for the offline by a SR action), a SETCACHE
subsystem being in pending state is pinned DASDFASTWRITE PENDINGOFF can be
data. To activate the subsystem storage, the issued for the devices which are pending (have
pinned data must first be discarded by a pinned data). A PINNED TRACK REPORT can
SETCACHE DISCARDPINNED for each be generated (LISTDATA PINNED), and then
volume with pinned data or a SUBSYSTEM the data set with pinned retriable or
PENDINGOFF, which causes cache fast write non-retriable tracks can be copied to a device
pinned data in the cache to be discarded. prior to discarding the pinned data. (Possible
(SUBSYSTEM PENDINGOFF will not work for utilities for copying the data set are IEBCOPY
data pinned in the NVS.) A PINNED TRACK and IEBGENER.) For other types of pinned
REPORT can be generated (LISTDATA data, reaccess and try to destage or discard.
PINNED), and then the data set with pinned
retriable or non-retriable tracks can be copied -DISABLED FOR MAINTENANCE: To activate
to a device prior to discarding the pinned data. the NVS, rerun the SETCACHE command
(Possible utilities for copying the data set are when the NVS is no longer disabled for
IEBCOPY and IEBGENER.) For other types of maintenance (probable SR action to enable).
pinned data, reaccess and try to destage or
SET NVS OFF
discard.
-NVS INITIALIZING: Rerun the SETCACHE
-DISABLED FOR MAINTENANCE: To activate job when the NVS has finished initialization.
subsystem storage, rerun the SETCACHE
SET DASD FAST WRITE ON
command when the subsystem is no longer
-NVS FAILED: Probable cause is malfunction
disabled for maintenance (probable SR action
or SR action. This message may occur after a
to enable).
duplex pair has been ended (with a
SET SUBSYSTEM STORAGE PENDINGOFF RESETTOSIMPLEX parameter). If DASD fast
-WRONG COMMAND ISSUED: The write is on prior to ending a duplex pair,
subsystem is not in pending state with scan IDCAMS will attempt to set DASD fast write off
complete. The SETCACHE SUBSYSTEM OFF and then restore to active status after the end.
would probably have resulted in the subsystem This is done to assure that the pairs are true
storage being deactivated. copies.
-NVS PINNED DATA: There is pinned data in SET DASD FAST WRITE OFF
the NVS. A PINNED TRACK REPORT can be -DASDFASTWRITE FAILED: This is caused by
generated (LISTDATA PINNED), and then the an incorrect ‘device ID’ (DASD fast write failed)
data set with pinned retriable or non-retriable and the device is DASD fast write active.
tracks can be copied to a device prior to

-INVALID DFW DATA FOR SYNC: There is hosts and there is host activity using this
data for the device in the failed nonvolatile volume. (Operator commands like a DEVSERV
storage and the data is not in cache storage. against the target volume will cause host I/O to
This condition prevents the scheduling of the volume.) Synchronize the target secondary
destage of all DASD fast write data for the device on all attached hosts and reissue the
device, and the setting of indicators to prevent command.
further DASD fast write activity on the device.
-PATH-GROUPS ARE NOT COMPATIBLE:
SET DASD FAST WRITE PENDINGOFF The 3990 command rejected the establishment
-WRONG COMMAND ISSUED: The of the duplex pair with sense indicating that the
SETCACHE DASDFASTWRITE OFF command proposed secondary device for the duplex pair
would probably have resulted in the DASD fast has at least one path group established, and
write being deactivated. that the primary and secondary devices do not
have the same path groups established on all
SET CACHE FAST WRITE ON
channel paths. A possible reason for this is that
-PINNED DATA: A PINNED TRACK REPORT
some other host attached to this device had
can be generated (LISTDATA PINNED), and
the device ONLINE and another non-MVS host
then the data set with pinned retriable or
attached to the secondary has a path group
non-retriable tracks can be copied to a device
established for the secondary. Note that this
prior to discarding the pinned data. (Possible
3990 check is to help insure that the secondary
utilities for copying the data set are IEBCOPY
is in the proper state; that is, either no path
and IEBGENER.) For other types of pinned
group exists or the path group of the
data, reaccess and try to destage or discard.
secondary is the same as that for the primary.
ESTABLISH A DUPLEX PAIR Insure that the target secondary device is
-NVS OFFLINE: Issue a SETCACHE NVS ON OFFLINE to all attached MVS hosts. If
to activate NVS. non-MVS hosts are attached to the device
insure that the path groups for the secondary
-CACHE OFFLINE: Issue a SETCACHE device are resigned or equal to the primary.
SUBSYSTEM ON to activate subsystem
storage. REESTABLISH A DUPLEX PAIR
-PINNED DATA: The suspended duplex
-PRIMARY DEVICE NOT SIMPLEX: A volser primary volume has pinned data. A PINNED
was selected which is already being used for TRACK REPORT can be generated
dual copy operations. Reissue the command (LISTDATA PINNED), and then the data set
with a non-duplex pair volser specified. with pinned retriable or non-retriable tracks can
-SECONDARY DEVICE NOT SIMPLEX: A be copied to a device prior to discarding the
device ID was selected which is already being pinned data. (Possible utilities for copying the
used for dual copy operations. Reissue the data set are IEBCOPY and IEBGENER.)
command with a non-duplex pair device ID Discard using DISCARDPINNED or
specified. DASDFASTWRITE PENDINGOFF (depending
on the circumstances).
-CACHING ACTIVE: Although IDCAMS will set
device caching off to both devices prior to -NVS OFFLINE: Issue a SETCACHE NVS ON
attempting to establish a duplex pair, if device to activate NVS.
caching is inadvertently set back on (perhaps -CACHE OFFLINE: Issue a SETCACHE
by another host) or is in pending state this SUBSYSTEM ON to activate subsystem
cause is given. Note that IDCAMS restores the storage.
device caching state of the duplex pair to the
original state of the primary device after the -DEVICE IS NOT A PRIMARY: The volser
establish duplex pair channel program has run. specified as the primary volume is not part of a
duplex pair or is the secondary volume of a
-PRIMARY AND SECONDARY ARE SAME duplex pair. Probable user error. Correct the
DEVICE: The volser of the requested primary volser and reissue the command. volser.
and the device id of the requested secondary
are the same device. -ALTERNATE DEVICE NOT SIMPLEX: A
device ID was selected which is already being
-DEVICE RESERVED OR BUSY TO used for dual copy operations. Reissue the
ANOTHER PROCESSOR: An attempt to command with a non-duplex pair device ID
establish a duplex pair has failed because the specified.
target secondary device was busy when the
3990 attempted to claim the volume. A possible -CACHING ACTIVE: Although IDCAMS will set
reason for the target secondary to be busy is device caching off to the alternate device prior
that the device is not offline to ALL attached to attempting to establish a duplex pair, if
517
device caching is inadvertently set back on -DEVICE IS NOT A PRIMARY: The volser
(perhaps by another host) or is in pending specified as the primary volume is not part of a
state this cause is given. duplex pair or is the secondary volume of a
duplex pair. Probable user error. Correct the
-PRIMARY AND ALTERNATE ARE SAME
volser and reissue the command.
DEVICE: The volser of the requested primary
and the device ID of the requested alternate TERMINATE A DUPLEX PAIR
are the same device. -DEVICE IS NOT A PRIMARY: The volser
specified as the primary volume is not part of a
-DEVICE RESERVED OR BUSY TO
duplex pair or is the secondary volume of a
ANOTHER PROCESSOR: An attempt to
duplex pair. Probable user error. Correct the
establish a duplex pair has failed because the
volser and reissue the command.
target alternate device was busy when the
3990 attempted to claim the volume. The target -PINNED DATA: DASD fast write is in pending
alternate could be busy because the device is state. A PINNED TRACK REPORT can be
not offline to all attached hosts and there is generated (LISTDATA PINNED), and then the
host activity using this volume (operator data set with pinned retriable or non-retriable
commands like a DEVSERV against the target tracks can be copied to a device prior to
volume will cause host I/O to the volume). discarding the pinned data. (Possible utilities
Synchronize the target alternate device on all for copying the data set are IEBCOPY and
attached hosts and reissue the command. IEBGENER.) Discard using DISCARDPINNED
or DASDFASTWRITE PENDINGOFF
-PATH-GROUPS ARE NOT COMPATIBLE:
(depending on the circumstances).
The 3990 command rejected the establishment
of the duplex pair with sense indicating that the SUSPEND A DUPLEX PAIR
proposed alternate device for the duplex pair -DEVICE IS NOT A PRIMARY: The volser
has at least one path group established and specified as the primary volume is not part of a
that the primary and alternate devices do not duplex pair or is the secondary volume of a
have the same path groups established on all duplex pair. Probable user error. Correct the
channel paths. A possible reason for this is that volser and reissue the command.
some other host attached to the alternate had
-PAIR ALREADY SUSPENDED: A request to
the alternate ONLINE and another non-MVS
suspend an already suspended duplex pair
host attached to this device has a path group
results in no action being taken.
established for the device. Note that this 3990
check is to help insure that the alternate is in -SUSPENDPRIMARY TO DUPLEX PENDING
the proper state; that is, either no path group PAIR: A request to suspend a duplex pair with
exists or the path group of the alternate is the the primary as the suspended device while
same as that for the primary. Insure that the establishing a duplex pair is pending. The
target alternate device is OFFLINE to all SUSPENDPRIMARY command is ended with
attached MVS hosts. If non-MVS hosts are no action taken.
attached to the device insure that the path
groups for the alternate device are resigned or For a LISTDATA request, action and cause can be
equal to the primary. replaced with the following values:
ESTABLISH A DUPLEX PAIR FROM SUSPENDED Action Cause
DUPLEX
-PINNED DATA: The suspended duplex READ PINNED TRACK DATA
primary volume has pinned data. A PINNED -CACHE STORAGE IS FAILED OR
TRACK REPORT can be generated UNAVAILABLE: An attempt to read pinned
(LISTDATA PINNED), and then the data set track data was unsuccessful because cache
with pinned retriable or non-retriable tracks can storage was not available or pending.
be copied to a device prior to discarding the
pinned data. (Possible utilities for copying the In the message text:
data set are IEBCOPY and IEBGENER.) volser The volume serial number.
Discard using DISCARDPINNED or
DASDFASTWRITE PENDINGOFF (depending action The specified action.
on the circumstances).
cause The cause of the error.
-NVS OFFLINE: Issue a SETCACHE NVS ON
to activate NVS.
Application Programmer Response: Resubmit when
-CACHE OFFLINE: Issue a SETCACHE
the state changes to allow the command. Most can be
SUBSYSTEM ON to activate subsystem
checked with LISTDATA...STATUS. In the case of a
storage.

user error, correct the volser or other erroneous asynchronous operation completed, but during the
condition and reissue the command. operation sense data was offloaded to an attached host
with the environmental data present bit set. This sense
Source: DFSMSdfp
data indicates the errors that occurred with the
asynchronous operation.
IDC31607I THE SPECIFIED COMMAND REQUIRES
For the FAILED condition, the asynchronous operation
ALTER AUTHORIZATION. THE USER
did not complete. This error may be accompanied by an
DOES NOT HAVE SUFFICIENT ACCESS
I/O error message on the console relating to the specific
AUTHORITY FOR devid TO BE
error. There may also be environmental sense data
INCLUDED IN A DUPLEX PAIR
present that could help identify this error.
Explanation: A SETCACHE SETSECONDARY
System Action: The asynchronous operation in the
command or a SETCACHE REESTABLISHDUPLEX
storage control has completed. IDCAMS processing
command was issued. The volume serial of offline
continues.
volume which is either the secondary or the alternate
volume is not equal to the volume serial of the primary Application Programmer Response: Examine a
volume. The requestor does not have DASDVOL ALTER merged LOGREC from all hosts attached to the storage
authority for the offline volume specified. control. For the COMPLETED IN ERROR condition,
examine the environmental data to determine what the
specific error was and if it pertained to an area on the
devid The device identification. volume within an allocated data set. From this
information you can determine the severity of the error.
Source: DFSMSdfp Note that there may be a collection of environmental
Detecting Module: IDCSS01 sense data caused by this one asynchronous operation.
Additional information can be gathered by issuing the
DEVSERV command to the device and examining
IDC31609I DEVICES SELECTED TO FORM A output from message IEE459I. After completing this
DUPLEX PAIR ARE NOT examination take the appropriate actions to correct the
COMPATIBLE-reason specific data set or entire volume error. If all errors were
Explanation: The SETCACHE command requiring not in allocated space on the volume, the impact of the
compatible devices was unsuccessful. Commands error may be minimal. Once you have made these
requiring compatible devices are: corrections, the volume should be ready to be
completely used. Note that the asynchronous operation
v SETSECONDARY (establish a duplex pair).
need not be repeated because it did complete and the
v REESTABLISHDUPLEX (reestablish a duplex pair state of the subsystem or volume should be as desired.
using an alternate device).
For the FAILED condition, examine the sense data
In the message text: associated with the specific error as well as any I/O
messages that may have appeared on the system
reason The reason for the error, as follows: console. Environmental sense data may also be helpful
v THE DEVICES ARE NOT THE SAME in determining the reason for the asynchronous
GEOMETRY AND CAPACITY operations failure. Additional information can be
gathered by issuing the DEVSERV command to the
v THE DEVICES ARE NOT IN THE SAME
device and examining output from message IEE459I.
LOGICAL DASD SUBSYSTEM
After completing this examination take the appropriate
System Action: Processing continues. actions to correct the problem, and then attempt to
reissue the asynchronous operation using the IDCAMS
Application Programmer Response: Select
utility.
compatible devices and rerun the command.
Source: DFSMSdfp
Source: DFSMSdfp
IDC31611I WHEN CREATING A DUPLEX PAIR THE

IDC31610I THE REQUESTED ASYNCHRONOUS
{SECONDARY | ALTERNATE} DEVICE
OPERATION {COMPLETED IN ERROR |
MUST BE OFFLINE
FAILED}
Explanation: A SETCACHE request which requires
Explanation: A SETCACHE command requesting an
that certain volumes be offline was unsuccessful. The
asynchronous operation was unsuccessful. The
following requests require the specified volume to be
asynchronous operations manager returned a return
offline:
code 8, with reason code 12 (COMPLETED IN ERROR)
or reason code 16 (FAILED). v SETSECONDARY (establish a duplex pair) requires
the secondary volume to be offline.
For the COMPLETED IN ERROR condition, the
519
v REESTABLISHDUPLEX (reestablish a duplex pair)
IDC31616I REINITIALIZE FAILED device IS NOT
requires the alternate volume to be offline.
OFFLINE
Explanation: A SETCACHE REINITIALIZE request
Application Programmer Response: Vary the requires that all devices attached to the subsystem be
secondary/alternate device offline (in ALL hosts offline. This message is issued for the first volume
attached to the subsystem) and rerun the command. found to be not offline.

device The device identifier (unit number) for one of
IDC31612I NO PATHS ARE AVAILABLE TO THE the devices attached to the subsystem.
REQUESTED SD; TO SET ON, ISSUE A
SETCACHE SUBSYSTEM ON
Application Programmer Response: Resubmit the
Explanation: This message is applicable to a 3880
command after all volumes have been varied offline.
Model 21. When a storage director is varied online a
SETCACHE SUBSYSTEM ON is required to set the Source: DFSMSdfp
storage director on.
System Action: Processing continues. IDC31617I THE COMMAND command IS
COMPLETE FOR {THE SUBSYSTEM
Application Programmer Response: Vary the
CONTAINING} volser | unitaddr
storage director online and issue a SETCACHE
SUBSYSTEM ON. Explanation: The I/O operation for the SETCACHE
command completed successfully.
Source: DFSMSdfp
IDC31615I THE SPECIFIED DEVICE ID device WAS command
NOT FOUND OR IS NOT CONNECTED One of the following:
TO A CACHING CONTROLLER. v SUSPENDPRIMARY
v SUSPENDSECONDARY
Explanation: A command requiring I/O to an offline
v SETSECONDARY
device was issued and could not be run. The specified
v DISCARDPINNED
device identifier was not found or the device was
v REINITIALIZE
connected to a non-caching controller. Commands
v RESETTODUPLEX
which allow I/O to offline devices are:
v RESETTOSIMPLEX
v LISTDATA ACCESSCODE v REESTABLISHDUPLEX
v LISTDATA STATUS v CACHEFASTWRITE ON
v SETCACHE NVS OFF v CACHEFASTWRITE OFF
v DASDFASTWRITE ON
v SETCACHE REINITIALIZE v DASDFASTWRITE OFF
v SETCACHE RESETTOSIMPLEX v DASDFASTWRITE PENDINGOFF
v SETCACHE SUBSYSTEM OFF v DESTAGE
v NVS ON
v the secondary device ID in SETCACHE
v NVS OFF
SETSECONDARY
v the alternate device ID in SETCACHE volser The volume serial number.
REESTABLISHDUPLEX unitaddr
The unit address.
System Action: The system sets the return code to 0.
device The device identifier.
Source: DFSMSdfp
Application Programmer Response: Resubmit the
command using a device identifier (unit number)
attached to a supported subsystem for which the IDC31652I OBJECT NOT SUPPORTED IN CIMODE
request is to be run. Explanation: An attempt was made to import an
Source: DFSMSdfp object from a CIMODE portable dataset, which is not
supported on this system. IMPORT CIMODE can only
use ESDS base clusters that do not have an alternate
index.

IDC31662I UNAUTHORIZED CALLER REQUESTED
Application Programmer Response: You must either AN AUTHORIZED FUNCTION
create the portable data set in record mode, or change
Explanation: Access method services was called to
its attributes to an ESDS cluster with no alternate
IMPORT a catalog using the problem program interface.
indexes.
However, the caller was not running in an authorized
Source: DFSMSdfp mode.
System Action: The request is ended.
IDC31655I ‘keywd’ PARAMETER INVALID WITH
Application Programmer Response: Obtain APF
ENTRY TYPE
authorization for the caller of access method services
Explanation: The specified keyword is improper for using the problem program interface.
the type of object being imported.
Source: DFSMSdfp
keywd The specified keyword. IDC31700I VSAM OPEN ERROR
System Action: The command is ended. Explanation: An error during OPEN processing
prevents testing of the data set.
proper parameters for the type of object being imported System Action: Processing ends.
and retry the command.
Application Programmer Response: For more
Source: DFSMSdfp information, see message IDC3009I, which immediately
precedes this message.
Source: DFSMSdfp
IDC31658I INVALID AUTHORIZATION TO BYPASS

ACS PROCESSING IDC31701I INSUFFICIENT VIRTUAL STORAGE
AVAILABLE
Explanation: A caller supplied a pointer to the ACERO
in the AMS processor invocation argument list; that Explanation: Virtual storage is insufficient to continue
pointer ordinarily causes the caller to bypass ACS processing.
processing. However, the caller was not APF
System Action: The data set is closed, and
authorized, and thus cannot bypass ACS processing.
processing ends.
command.
region size and re-run.
Application Programmer Response: Either clear the
Source: DFSMSdfp
ACERO pointer in the AMS processor invocation
argument list, or reissue the command in an
APF-authorized state. IDC31702I DATA SET REQUESTED IS NOT A
VSAM KSDS CLUSTER
Source: DFSMSdfp
Explanation: At open time it is found that the data set
is not a key-sequenced data set.
IDC31660I INVALID CATALOG NAME ON
processing ends.
OUTDATASET OR OUTFILE.
Explanation: The catalog name on the out data set or
are using the correct data set name.
outfile does not match the catalog name in the exported
copy. This is an error. Source: DFSMSdfp
System Action: The system ends command
processing. IDC31703I DATA SET REQUESTED FOUND TO BE
IN CREATE MODE
catalog name on the out data set or outfile. Run the job Explanation: The data set is in create mode and,
again. therefore, cannot be tested.
Source: DFSMSdfp System Action: The data set is closed, and
processing ends.
521
are using the correct data set name. attempt to determine the cause of the problem. See
OS/390 DFSMSdfp Diagnosis Guide for information on
Source: DFSMSdfp
dump points.
Source: DFSMSdfp
IDC31704I DATA SET IS ALREADY OPEN FOR
OUTPUT OR WAS NOT CLOSED
CORRECTLY IDC31708I ERROR OBTAINING FORMAT ONE
DSCB FROM VTOC
Explanation: The data set is already OPEN for output
by a user on another system, or was not previously Explanation: An error other than 'DSCB Not Found'
closed. occurred when EXAMINE tried to obtain a Format-1
DSCB for the cluster.
processing ends. System Action: Processing ends.
Application Programmer Response: If the data set is Application Programmer Response: You should
OPEN for output, it must be closed before running attempt to determine the cause of the problem. See
EXAMINE. If it is not OPEN for output, you must run OS/390 DFSMSdfp Diagnosis Guide for information on
verify (via the VERIFY command) before running dump points.
EXAMINE.
Source: DFSMSdfp
Source: DFSMSdfp
IDC31709I ERROR OBTAINING VOLUME
IDC31705I DATATEST NOT PERFORMED DUE TO INFORMATION
SEVERE INDEXTEST ERRORS
Explanation: Volume information for the specified
Explanation: You have requested both INDEXTEST entry name cannot be obtained.
and DATATEST. Errors encountered during the index
System Action: Processing ends.
test are of such severity that further testing of the data
component might not yield usable information. Application Programmer Response: You should
attempt to determine the cause of the problem. Refer to
OS/390 DFSMSdfp Diagnosis Guide for information on
processing ends.
dump points.
Application Programmer Response: You should
Source: DFSMSdfp
analyze the information presented by INDEXTEST and
take appropriate action to rebuild or recover the data
set. You may run the data test by specifying the IDC31710I CI ACCESS ERROR
NOINDEXTEST DATATEST parameters.
Explanation: An I/O error has been encountered while
Source: DFSMSdfp attempting to read a control interval.
IDC31706I VSAM CONTROL BLOCK ERROR
Explanation: At least one field within a VSAM control attempt to determine the cause of the problem. See
block built by OPEN contains incorrect data. OS/390 DFSMSdfp Diagnosis Guide for information on
dump points.
processing ends. Source: DFSMSdfp
attempt to determine the cause of the problem. See IDC31750I IMPROPER ENVIRONMENT FOR
OS/390 DFSMSdfp Diagnosis Guide for information on COMMAND
dumps points.
Explanation: During processing of a command,
Source: DFSMSdfp access method services detected that the environment
was improper for that command. Processing occurred in
either a Time Sharing Option (TSO) or TSO/Extensions
IDC31707I ERROR OBTAINING TSO QUALIFIER
(TSO/E) release 1 environment; the command requires
Explanation: The Time Sharing Option/Extensions a TSO/E release 2 or higher.
(TSO/E) user id cannot be prefixed to the unqualified
data set name.
command.
Application Programmer Response: If TSO/E
Application Programmer Response: You should release 2 or higher is installed, run the command in the

foreground as a TSO command. Application Programmer Response: Notify the
system programmer.
Source: DFSMSdfp
Detecting Module: IDCTC01
IDC31751I COMMAND ABNORMALLY reporting data bases for a fix for the problem. If no fix
TERMINATED. TMP ABEND CODE IS exists, contact the IBM Support Center. Provide the
code JCL, the SYSOUT output for the job, and all printed
Explanation: The terminal monitor program (TMP)
indicated to access method services (AMS) that a Source: DFSMSdfp
command abnormally ended.
In the message text: IDC31810I INSUFFICIENT FACILITY CLASS
AUTHORIZATION TO PERFORM
code The abend code. FUNCTION
System Action: The system ends the command. Explanation: An attempt was made to perform a
Application Programmer Response: None. function without proper authority to
‘STGADMIN.IDC.DCOLLECT’.
Source: DFSMSdfp
Detecting Module: IDCTC01
Application Programmer Response: Obtain proper
facility class authorization to
IDC31801I INVALID FORMAT FOR OUTPUT DATA ‘STGADMIN.IDC.DCOLLECT’.
SET name
Explanation: Data set had an incorrect data set and the program is not in error, look at the messages in
organization or an incorrect record format. the job log for more information. Search problem
name The data set name. JCL, the SYSOUT output for the job, and all printed
System Action: The system ends the command. output and output data sets related to the problem.
Application Programmer Response: Ensure that the Source: DFSMSdfp

data set has a data set organization of physical
sequential and a record format of “V” or “VB”. IDC31863I OFFSET MISSING OR SPECIFICATION
System Programmer Response: If the error recurs INVALID IN OFFSET PAIR number
and the program is not in error, look at the messages in REASON CODE IS reason-code
the job log for more information. Search problem Explanation: INSERTSHIFT was specified on an
reporting data bases for a fix for the problem. If no fix access method services (AMS) PRINT or REPRO copy
exists, contact the IBM Support Center. Provide the of a data set operation. AMS, while checking offset
JCL, the SYSOUT output for the job, and all printed values, detected one of the following:
Code Reason
Source: DFSMSdfp
4 One or more pairs have the offset missing.
IDC31802I LOAD OF MODULE name WAS 8 The difference between the first offset and the
UNSUCCESSFUL. ABEND CODE IS xx - second offset is not an even number.
REASON CODE IS reason-code 12 The first offset was specified as greater than
Explanation: The named module could not be loaded the second offset.
into system storage.
number The offset pair in which the error was
name The name of the module. detected.
xx The abend code. reason-code The reason code.
reason-code The reason code. System Action: The command is ended. The return
System Action: Processing provided by the named code is 12.
module is not performed. Application Programmer Response: Recheck the
523
specification of the offset pairs in the INSERTSHIFT Detecting Module: IDCSH07
keyword. Make sure offset1 is not greater than offset2
in any offset pair and that the difference between
IDC31881I UNBIND NOT SET FOR dsname
offset1 and offset2 is an even number.
Explanation: A SHCDS FRUNBIND command failed
Source: DFSMSdfp
for data set dsname. The explanation for the command
failure follows the message.
IDC31864I OFFSET PAIR number1 RANGE
Source: DFSMSdfp
OVERLAPS OFFSET PAIR number2
Explanation: INSERTSHIFT was specified on an
access method services (AMS) PRINT or REPRO copy
of a data set operation. AMS, while checking offset IDC31882I BIND NOT SET FOR dsname
values, detected that a set of offset pairs had
overlapping ranges. This would cause the data to fail Explanation: A SHCDS FRBIND command failed for
during DBCS criteria checking. data set dsname. The explanation for the command
failure follows the message.
Source: DFSMSdfp
number1 and number2
The offset pairs with overlapping values. Detecting Module: IDCSH09
System Action: The command is ended. The return

code is 12. IDC31883I IDC31883I RECOVERY NOT RESET
FOR dsname
Application Programmer Response: Recheck the
offset pair specifications in the INSERTSHIFT keyword. Explanation: A SHCDS FRRESETRR command failed
You should make sure that offset pair values do not for data set dsname. The explanation for the command
overlap. failure follows the message.

IDC31865I OFFSET offset IN OFFSET PAIR number
EXCEEDS MAXIMUM RECORD IDC31884I UNBOUND LOCKS NOT DELETED FOR
LENGTH dsname
Explanation: INSERTSHIFT was specified on an Explanation: A SHCDS FRDELETEUNBOUNDLOCKS
access method services (AMS) REPRO copy of a data command failed for data set dsname. The explanation
set. AMS, while comparing offsets and target data sets for the command failure follows the message.
(maximum) record length, discovered that the offset
exceeds the maximum record length of the target data Source: DFSMSdfp
set. Detecting Module: IDCSH11
offset The offset. IDC31885I NON-RLS UPDATE NOT PERMITTED
FOR dsname
number The offset pair.
System Action: The command is ended. The return RLS mode has failed to be permitted access in
code is 12. non-RLS mode. The explanation for the command
Application Programmer Response: Recheck the failure follows the message.
offset pair specifications in the INSERTSHIFT keyword. Source: DFSMSdfp
Make sure that an offset value does not exceed the
maximum record length of the target data set. Detecting Module: IDCSH12
Source: DFSMSdfp
IDC31886I NON-RLS UPDATE NOT DENIED FOR
dsname
IDC31880I RECOVERY NOT SET FOR dsname
Explanation: A SHCDS FRSETRR command failed for non-RLS mode is not denied access in non-RLS mode.
data set dsname. The explanation for the command
failure follows the message. Source: DFSMSdfp
Source: DFSMSdfp Detecting Module: IDCSH13

Source: DFSMSdfp
IDC31887I SUBSYSTEM subsystem NOT
REMOVED Detecting Module: IDCSH01, IDCSH02, IDCSH03,
IDCSH04, IDCSH05, IDCSH06, IDCSH07, IDCSH08,
Explanation: subsystem was not disconnected from
SMSVSAM. The messages that follow explain the
IDCSH14, IDCSH15
reason the subsystem was not removed.
System Programmer Response: Be sure the correct
IDC31890I DATASET NOT LISTED
subsystem name is specified.
Explanation: The SMSVSAM address space did not
Source: DFSMSdfp
contain information related to the data set requested.
Detecting Module: IDCSH14 Can be issued also in response to SHCDS
sub-commands LISTDS, LISTSUBSYS, or
LISTSUBSYSDS. Data sets are not listed if they are not
IDC31888I UNEXPECTED ERROR FROM
currently open for RLS mode or do not have related
SMSVSAM SERVER DIAGNOSTIC
lock information being maintained in the SMSVSAM
INFORMATION: RC = return-code RS =
address space.
reason-code
Application Programmer Response: Ensure the data
Explanation: The SMSVSAM address space returned
set name has been specified correctly. Verify the related
error indicated by the return-code and reason-code
catalog has connectivity to the system being used for
values.
the SHCDS command. Contact system programmer for
User Response: Contact the system programmer SMSVSAM diagnosis instructions.
regarding procedures to start the SMSVSAM address
System Programmer Response: See the OS/390
space.
DFSMSdfp Storage Administration Reference for
Operator Response: Contact the system programmer requirements.
Source: DFSMSdfp
space.
Detecting Module: IDCSH02, IDCSH04, IDCSH05,
IDCSH06
system programmer regarding procedures to start the
SMSVSAM address space.
IDC31891I SUBSYSTEM NOT LISTED
DFSMSdfp Diagnosis Reference for providing Explanation: The SMSVSAM address space did not
documentation for SMSVSAM problem. contain information related to the subsystem requested.
Can be issued also in response to SHCDS
Source: DFSMSdfp
sub-commands LISTDS, LISTSUBSYS, or
Detecting Module: IDCSH01, IDCSH02, IDCSH03, LISTSUBSYSDS. Subsystems are not listed if they are
IDCSH04, IDCSH05, IDCSH06, IDCSH07, IDCSH08, not currently active or do not have related lock
IDCSH09, IDCSH10, IDCSH11, IDCSH12, IDCSH13, information being maintained in the SMSVSAM address
IDCSH14, IDCSH15 space.
Application Programmer Response: Ensure the
IDC31889I SMSVSAM SERVER NOT AVAILABLE subsystem has been specified correctly. Contact system
programmer for SMSVSAM diagnosis instructions.
Explanation: The SMSVSAM address space is not
available to handle the request. System Programmer Response: See the OS/390
User Response: Contact the system programmer requirements.
space. Source: DFSMSdfp
Operator Response: Contact the system programmer Detecting Module: IDCSH02, IDCSH03, IDCSH04,
regarding procedures to start the SMSVSAM address IDCSH05, IDCSH06
space.
Application Programmer Response: Contact the IDC31892I INSUFFICIENT USER AUTHORIZATION
system programmer regarding procedures to start the FOR SHCDS COMMAND
SMSVSAM address space.
Explanation: To use the SHCDS List subcommands,
System Programmer Response: Make the READ authority to the FACILITY class profile
SMSVSAM address space available. See the OS/390 STGADMIN.IGWSHCDS.REPAIR is required. UPDATE
DFSMSdfp Storage Administration Reference for authority to this FACILITY class profile is required for
requirements. the FR* subcommands, the PERMITNONRLSUPDATE,
525
DENYNONRLSUPDATE, and REMOVESUBSYS DFSMSdfp Storage Administration Reference for
subcommands. requirements.
For the CFREPAIR and CFRESET subcommands, Source: DFSMSdfp
ALTER authority is required to the specified catalog.
The following additional authority is required:
v For the FR*, PERMITNONRLSUPDATE, IDC31895I DATA SETS UNSUCCESSFULLY
DENYNONRLSUPDATE subcommands, UPDATE PROCESSED
authority to the base cluster.
Explanation: An SHCDS CFREPAIR, CFRESET, or
v For the REMOVESUBSYS subcommand, UPDATE
CFRESETDS command was issued. For each data set
authority to the RACF SUBSYSNM class.
that was not processed, the following information is
Application Programmer Response: Obtain the presented:
proper authorization for the command. v The data set name
v The reason that the data set was not processed
System Programmer Response: Provide
authorization for using the SHCDS command. Application Programmer Response: Examine the
return and reason codes and determine if any further
Source: DFSMSdfp
action needs to be taken.
Detecting Module: IDCSH01, IDCSH15, IDCSH16
Source: DFSMSdfp
Detecting Module: IDCSH15, IDCSH16, IDCSH17
IDC31893I NO SUBSYSTEM INFORMATION
FOUND
IDC31896I INSUFFICIENT USER AUTHORIZATION
FOR CATALOG UPDATE
contain information related to the subsystem requested.
Can be issued also in response to SHCDS Explanation: The user does not have sufficient
sub-commands LISTDS, LISTSUBSYS, or authority to the catalog that was specified in the SHCDS
LISTSUBSYSDS. Subsystems are not listed if they are CFREPAIR, CFRESET, or CFRESETDS command.
not currently active or do not have related lock
Application Programmer Response: Obtain the
information being maintained in the SMSVSAM address
proper authorization for the command.
space.
System Programmer Response: Provide
Application Programmer Response: Ensure the
authorization for using the SHCDS command.
subsystem has been specified correctly. Contact system
programmer for SMSVSAM diagnosis instructions. Source: DFSMSdfp
System Programmer Response: See the OS/390 Detecting Module: IDCSH15, IDCSH16, IDCSH17
requirements.
IDC31897I CATALOG MUST BE ICF FOR SHCDS
Source: DFSMSdfp COMMAND
Detecting Module: IDCSH02, IDCSH03, IDCSH04, Explanation: An SHCDS CFREPAIR, CFRESET, or
IDCSH05, IDCSH06 CFRESETDS command was issued against a catalog
that is not an ICF catalog.
IDC31894I NO DATASET RECOVERY Application Programmer Response: Specify the
INFORMATION FOUND name of an ICF catalog as the parameter of the
INDATASET option.
contain lock recovery information related to the data set Source: DFSMSdfp
requested. Can be issued also in response to SHCDS
sub-commands LISTRECOVERY. Data sets are not Detecting Module: IDCSH15, IDCSH16, IDCSH17
listed if they do not have retained or lost locks, do not
have non-RLS permit status, or not marked with forward IDC31898I SECURITY VERIFICATION FAILED FOR
recovery required. DATA SET
Application Programmer Response: Ensure the data Explanation: Requestor does not have sufficient
set or data set qualifiers have been specified correctly. authorization to perform function on the specified data
Contact system programmer for SMSVSAM diagnosis set.
instructions.
Application Programmer Response: Obtain the
System Programmer Response: See the OS/390 required authorization for the data set.

Source: DFSMSdfp System Programmer Response: Specify a valid
value and rerun the job.
IDCSH10, IDCSH11 Source: DFSMSdfp
Detecting Module: IDCCR01
IDC31900I INCORRECT SPECIFICATION OF
date-field
IDC31903I parameter1 IS GREATER THAN
Explanation: A date was incorrectly specified when parameter2
using the IDCAMS ALTER or CREATE commands. Date
Explanation: The value specified for an IDCAMS
is expected in the format YYYY-MM-DD.
CREATE or ALTER command will cause the value for
In the message text: parameter1 to exceed parameter2.
date-field In the message text:
The specific field in error. Possible values include:
parameter1
YEAR The year is not valid. Acceptable values Parameter value that should be lesser than or
are between 0000 - 2155. equal to parameter2.
MONTH parameter2
The month is not valid. Acceptable values Parameter value that should be greater.
are between 00 - 12.
DAY The day is not valid. Acceptable values are command.
between:
Value Corresponding Dates appropriate parameter to ensure that the value of
parameter2 is greater than or equal to the value of
01 - 28 for February (not a leap year).
parameter1.
01 - 29 for February (leap year).
Source: DFSMSdfp
01 - 30 for April, June, September, and
November
01 - 31 for January, March, May, July,
IDC31950I NO LOCKS TO BIND/UNBIND
August, October and December.
Explanation: There were no locks found for the
32 which means ’never expire’ (date
FRBIND/FRUNBIND request for the data set.
of 1999-12-32).
Application Programmer Response: Be sure the
HYPHEN
correct data set has been specified. Verify lock status
The required hyphen is missing from either
for the data set with the SHCDS LISTDS subcommand.
the fifth or the eighth position in date-field.
Source: DFSMSdfp
command. Detecting Module: IDCSH08, IDCSH09
System Programmer Response: Correct the date
and rerun the job. IDC31951I DATA SET IS OPEN. TRY AGAIN LATER
Source: DFSMSdfp Explanation: Data set is currently in use by another
job or user. Rerun the command at a later time.
Application Programmer Response: Verify the data
sets availability with the SHCDS LISTDS subcommand.
IDC31901I INCORRECT VALUE FOR parameter
Once the data set is no longer in use execute the
Explanation: An invalid value was specified for the command.
named parameter. See DFSMS/MVS Access Method
Source: DFSMSdfp
Services for ICF for more information about valid
values. Detecting Module: IDCSH07, IDCSH08, IDCSH09,
IDCSH10, IDCSH11, IDCSH12, IDCSH13
parameter
The named parameter.
command.
527
IDC31952I NOT SMS-MANAGED VSAM DATA SET IDC31957I SUBSYSTEM NOT FOUND
Explanation: The SHCDS subcommand requires that Explanation: The requested subsystem was not
the object of the command be an SMS-managed VSAM found.
data set.
Application Programmer Response: Ensure that the subsystem is specified correctly. Use the SHCDS
data set is specified correctly. LISTSUBSYS or LISTSUBSYSDS subcommands to
verify the subsystem status.
Source: DFSMSdfp
Source: DFSMSdfp
IDCSH10, IDCSH11 Detecting Module: IDCSH02, IDCSH03, IDCSH04,
IDCSH05, IDCSH06, IDCSH11, IDCSH12, IDCSH13
IDC31953I NO UNBOUND LOCKS TO DELETE
IDC31958I SUBSYSTEM CURRENTLY ACTIVE
Explanation: No unbound locks were found for the
data set. Explanation: The requested subsystem was active
with the SMSVSAM address space.
data set is specified correctly. Application Programmer Response: Ensure that the
subsystem is specified correctly. Use the SHCDS
Source: DFSMSdfp
LISTSUBSYS or LISTSUBSYSDS subcommands to
Detecting Module: IDCSH11 verify the subsystem status.
Source: DFSMSdfp
IDC31954I DATA SET DOES NOT HAVE RETAINED
OR LOST LOCKS
Explanation: No retained or lost locks were found for
IDC31959I ERROR DATA: X’diagnostic-error-data’
the data set.
Explanation: The FR* command failed and the
diagnostic-error-data was returned. return-code and
data set is specified correctly.
reason-code values.
Source: DFSMSdfp
Application Programmer Response: Refer to the
Detecting Module: IDCSH12, IDCSH13 OS/390 DFSMSdfp Diagnosis Reference for causes of
the failure.
IDC31955I DATA SET IS NOT RECOVERABLE System Programmer Response: Refer to the OS/390
DFSMSdfp Diagnosis Reference for providing
Explanation: The data set was not recoverable. documentation for SMSVSAM problem.
Redefine the data set or use the ALTER command to
add the LOG(ALL) OR LOG(UNDO) option for the data Source: DFSMSdfp
set.
Application Programmer Response: Ensure that the IDCSH10, IDCSH11
Source: DFSMSdfp
Detecting Module: IDCSH12, IDCSH13
IDC31956I DATA SET NOT FOUND

Explanation: The catalog search failed or the data set
is not active within SMSVSAM.
Source: DFSMSdfp
IDCSH11, IDCSH12, IDCSH13

Chapter 15. IEA Messages
Two consecutive commas or a field containing blanks or
IEA000A SWAP FROM xxx TO zzz FAILED,
asterisks in the message text indicates that a field could
RETRY (R) OR TERMINATE (T)
not be determined or is contained on the next or
Explanation: The 3851 ERP (error recovery previous line of the message. If the sense data to be
procedure) detected that the dynamic device inserted in the sens field of the message text exceeds 6
reconfiguration (DDR) swap service could not swap the bytes, the sens field and the optional field that follows
primary mass storage control (MSC) to the alternate (dcbctfd or opxxterm or cylntrck) do not appear on the
MSC. Previous operator messages indicate the reason first line. Consecutive commas appear instead. The
for the DDR swap service failure. The operator can retry system then issues a second line that includes the
the swap or end the swap. If the swap operation fails device number of the device, the sense data, and,
consistently, a permanent I/O condition exists. optionally, dcbctfd, opxxterm, or cylntrck. In other words,
if the sense data exceeds six bytes, the message has
this format:
xxx The low number in the range. IEA000I dev,err,cm,stat,,,[ser],jjj
[,hh.mm.ss]
zzz The high number in the range. IEA000I dev,,,sens {,dcbctfd|,opxxterm|
,cylntrck}
System Action: The system waits for the operator’s
reply (see the operator response for this message). Because two separate WTO instructions issue the two
messages shown above, it is possible that one or more
Operator Response: Retry (R). If the error continues unrelated messages could appear between the first
to occur, end (T). message and the second message.
If the swap is ended, the system places both MSCs
offline. The system continues processing without the In the message text:
MSCs and probably without the MSS (mass storage dev
system) functions. Device number of the device or line address of the
If the error continues to occur, it is probably because of telecommunication device, in hexadecimal. If the
a hardware problem. The system issues message error is a channel program check (CPC) or channel
IEA000I. Follow installation procedures to take protection check (PRC), this field will be zeros; the
corrective action. Notify the system programmer. error was not caused by a hardware error on the
device, but was caused by the program issuing the
Source: DFSMSdfp I/O.
Detecting Module: ERPs. IECIOSCN, IGE0025C err Description of the error based on status and sense
information:
IEA000I dev,err,cm,stat,sens, DSN - data streaming is not operational.
{dcbctfd|opxxterm|cylntrck} RST - the I/O Restart routine was entered by
[ser],jjj[,hh.mm.ss] Alternate CPU Recovery, the Channel Check
Handler, or the Missing Interrupt Handler.
--or-- SAF - Staging Adapter failure. The Staging
Adapter controlling the DASD address specified
has lost communications with the mass storage
dev,err,cm,stat - MESSAGE EXIT
control.
UNAVAILABLE - [exitname]
UEX - unit exception.
Explanation: For the first format of the message, an
uncorrectable input/output error was detected by the I/O MSS users should check the “possible values of err
supervisor, the basic telecommunication access method and appropriate responses” in the Operator
(BTAM), or the telecommunication access method Response part of this message description.
(TCAM) routine. In systems with the graphics access
method (GAM), unit checks and conditions that require cm Command code, in hexadecimal, of the channel
operator intervention indicate devices that do not exist command word (CCW) being executed when the
or that were included at system generation time but not error occurred. If the channel command word
attached to the system. cannot be found, this field appears as **.
For the second format of the message, the message stat

writer was unable to locate the routine that builds the Status portion, in hexadecimal, of the channel
device dependent portion of the above message. If the status word (CSW).
name of the routine is available, it is included in the sens
message as exitname. The first byte, in hexadecimal, describes a unit

check type error condition (for telecommunication the operation. Check that tapes being used by this job
devices). The second byte, in hexadecimal, have not been replaced or removed. Each message
contains sense information resulting from the should be considered as a potential attention of a
execution of a diagnostic write/read or read/skip marginal condition.
command (from TCAM) which ended with a unit
For other than magnetic tape devices, note that some
check status (2701 data adapter unit). For other
abnormal error condition occurred. Depending on the
devices, these same two bytes will appear, in
severity of the error (check status and sense
hexadecimal, if a unit check condition is indicated in
information) and depending on the installation
the stat field. For devices that give more than two
requirements, take the appropriate action.
bytes of sense information, this field will also
contain the remaining sense bytes, in hexadecimal. Possible values of err and appropriate responses are as
For devices which give more than 6 sense bytes, follows:
this field continues on the second line of the v For MSS users, an attempt has been made to write
message. For DASD devices, this field will contain on a virtual volume that was specified READ ONLY
the 8 sense bytes for program errors or 24 sense on the CREATEV command.
bytes for equipment and data checks. For the 3340,
this field will contain 24 sense bytes for seek v SAF - Staging Adapter failure. Use your path chart to
checks. determine the SSID of the Staging Adapter involved
or use 8nn for the SSID, where nn is byte 25 of the
The message on the system console reflects the MSS sense data in this message.
sense-byte information from the last entry for direct
access devices; the sense-byte information located Source: DFSMSdfp
in the logrec data set data reflects the data from Detecting Module: ERPs
the initial error condition.
debctfd IEA000I dev,err......hh.mm.ss
Record count, in hexadecimal, not including label
records. This field appears only for magnetic tape Explanation: The processor’s error recovery
and indicates the count of the record preceding the procedures detected an error that requires either a CEM
error record. (CE message), or an SUU (subsystem unit unusable)
message. An equipment check might occur with either
opxxterm CEM or SUU. Because the system WTO routine can
TP operation code, in hexadecimal, describing the print only one message, the error recovery procedure
type of channel command word (CCW) being prints the CEM or SUU message and the system WTO
executed when the error occurred. xx is not used, routine prints the remaining message with full sense
but is followed by the terminal identification data. The error recovery procedure continues recovery
characters, in hexadecimal. It may be either two action based on the error condition.
bytes or one byte, depending on the terminal type.
If it is one byte, it is left justified. If a dial line is In the message text:
being used with TCAM, the last four digits of the dev
dial number are provided. Device number of the mass storage control.
cylntrck err Description of the error. The values are as follows:
Address, in hexadecimal, of the cylinder (cyln), and
v CEM -- CE message. The Mass Storage Facility
the track (trck) where the error occurred. When an
has detected an error important to the service
error occurs while trying to obtain this data, the last
representative.
seek address is substituted. This field appears only
for certain disk and drum direct access device v SUU -- Subsystem unit unusable. The Mass
errors. Storage Facility has marked one of its units as
unusable because of an error condition. The
ser Serial number of the volume on which the error SSID of that unit is in the second half of sense
occurred. This field appears only for magnetic tapes byte 1 and all of byte 2 in the accompanying
or direct access devices. message. The system continues processing;
jjj Job name. If the error is a channel program check notify your service representative.
(CPC) or channel protection check (PRC), this field hh.mm.ss
will indicate the program in error. Time that the message was received in hours,
hh.mm.ss minutes, and seconds.
Time that the message was received in hours, System Action: The error recovery procedure will
minutes, and seconds. continue the recovery action based on the error
Operator Response: For all values of err, probable condition.
hardware error. For magnetic tape devices, proceed Operator Response: Probable hardware error. Each
with caution in unconditionally accepting the results of

message should be considered as a potential attention Source: DFSMSdfp
of a marginal condition. Depending on the installation
Detecting Module: ERPs
requirements, take appropriate action.
Source: DFSMSdfp
IEA005I DATE (AND CLOCK, IF SPECIFIED)
Detecting Module: ERPs REJECTED. DATE MUST BE
SPECIFIED AS A 4-DIGIT YEAR
IEA000I I/O ERR,aaa,bb,cccc,dd00, ffgghhhh Explanation: A 2 digit year was specified.
Explanation: This message is sent to the primary
operator control station when TCAM error recovery IEA007I STATIC SYSTEM SYMBOL VALUES:
procedures fail to correct an I/O error. This message is
in addition to the record of permanent errors that is &SYSCLONE. = ″sysclone-text″
created on disk when such an error occurs. TCAM &SYSNAME. = ″sysname-text″
inserts no line control, not even EOT, into this type of &SYSPLEX. = ″sysplex-text″
message. If line control is required, you must see to it &symbol.-name = ″symbol-text″
.
that MSGEDIT or MSGFORM inserts the line control. .
.
Some devices display a new line character (X'15') and
15 pad characters (X'32') preceding the message. symbol.-name = ″symbol-text″
In the message text, the fields, in hexadecimal format,
are: Explanation: This message displays the static system
symbols and their associated substitution texts. The
aaa system issues this message:
Address of the line where the error occurred.
v In response to the DISPLAY SYMBOLS command
bb The command code as specified in the failing v During system initialization, when the operator
channel program. specifies an initialization message suppression
cccc indicator (IMSI) that does not suppress informational
The status bytes of the channel status word (CCW) messages.
as specified in the input/output block (IOB).
dd The first sense byte as specified in the IOB.
&sysclone.-text
ff The TP op code as specified in the failing CCW in The text associated with the &SYSCLONE. static
the channel program for the last retry attempt. system symbol. The substitution text for
gg The TP op code of the failing CCW for the first &SYSCLONE. is defined in the IEASYMxx parmlib
occurrence of the error. member.
hhhh &sysname.-text
For stations on switched lines, if the station is The text associated with the &SYSNAME. static
known, hhhh is replaced by the last four dial digits, system symbol. The substitution text for
if assigned. For stations on nonswitched lines, hhhh &SYSNAME. is defined in the IEASYMxx or
is replaced by polling characters for receiving IEASYSxx parmlib member.
operations and addressing characters for sending &sysplex.-text
operations. If the station is on a switched line and The text associated with the &SYSPLEX. static
TCAM cannot identify it at the time the error occurs, system symbol. The substitution for &SYSPLEX. is
hhhh is replaced by the polling characters for defined in the COUPLExx or LOADxx parmlib
stations on this line. If no polling characters are member.
assigned, hhhh is replaced by zeros.
symbol.-name
System Action: See the explanation. The name of a static system symbol that your
Operator Response: In some applications, the installation defined in the IEASYMxx parmlib
generation of the IEA000I message may be faster than member.
the handling capacity of the primary operator control symbol.-text
station. When the primary operator control station is the The substitution text associated with the
system console, a backlog may create a system queue installation-defined system symbolname.
area shortage. If allowed to continue without operator
intervention, a serious shortage could result and could System Action: The system continues processing.
cause a system wait state to be entered. To reduce The system uses the substitution texts that are
generation of these error messages, TCAM’s threshold displayed in the message text.
support should be used.
Chapter 15. IEA Messages 531

System Programmer Response: Determine if the list v The operator specifies an initialization message
of system symbols and substitution texts are suppression indicator (IMSI) that does not suppress
appropriate. If a system symbol is not correct, change informational messages.
the definition in one of the following parmlib members: v The system programmer specifies the ,L parameter
COUPLExx on the IEASYM statement in the LOADxx parmlib
IEASYMxx member.
IEASYSxx
LOADxx In the message text:
Source: System initialization (IPL/NIP) xx The suffix of the first IEASYMxx parmlib member in
Detecting Module: IEAVESYM the system parameter concatenation.
zz The suffix of the last IEASYMxx parmlib member in
IEA008I SYSTEM PARMS FOLLOW FOR xx...x the system parameter concatenation.
Explanation: This message displays the IEASYSxx System Action: The system continues processing.
parmlib members that contain system parameters for The system uses the system symbol definitions in the
this system image. The IEASYSxx members are IEASYMxx members that appear in the message text.
specified in the LOADxx and IEASYMxx parmlib System Programmer Response: Determine if the list
members. of IEASYMxx members is correct. If the list is not
In the message text: correct, change the IEASYM statement in LOADxx to
specify the correct IEASYMxx members. Then reIPL the
xx...x system.
Contains the full product name, version, release,
modification level and FMID. For example, in Source: System initialization (IPL/NIP)
OS/390 Release 2, xx...x is 01.02.00 JBB6602. Detecting Module: IEAVNPIL
This field can be changed by the installation using
the SPZAP service to change the value in the IEA010I SYMBOLIC DEFINITION ALTERED:
CVTVERID field of the communication vector table
(CVT).
SYMBOL = &symbol.-name
System Action: The system continues processing. ORIGINAL VALUE = old-text
The system uses the system parameters specified in NEW VALUE = new-text
the IEASYSxx members that are displayed in the
Explanation: This message displays a value in the
message text.
static system symbol table that was changed during
System Programmer Response: Determine if the initialization. The system issues this message when the
system parameters are appropriate for the system. If the substitution text for the &SYSPLEX.system symbol is
list is not correct, see the section on determining where specified in COUPLExx but not in LOADxx.
to specify system parameters in OS/390 MVS
Initialization and Tuning Reference for information about
how to respecify IEASYSxx members. &symbol.-name
The name of the static system symbol whose
Source: System initialization (IPL/NIP)
substitution text was changed during system
Detecting Module: IEAVNPC4 initialization.
old-text
IEA009I SYMBOLIC DEFINITIONS WILL BE The substitution text for the symbol-name static
READ FROM: system symbol before the change.
new-text
IEASYMxx The substitution text for the symbol-name static
. system symbol after the change.
.
.
The system uses the new substitution text for the
IEASYMzz
system symbols displayed in the message text.
Explanation: This message displays the IEASYMxx
System Programmer Response: Determine if the
parmlib members that define system symbols for this
new substitution text displayed in the message text is
system. The IEASYMxx members are specified in the
appropriate for the associated system symbol. If not,
LOADxx parmlib member. The system displays this
see OS/390 MVS Initialization and Tuning Reference for
message during system initialization if both of the
information about how to change system symbol
following occur:
definitions in parmlib. After you change the definitions

for the system symbol, reIPL the system.
IEA012E CIRCULAR SYMBOLIC DEFINITION
If &symbol.-name shown in the message text is DETECTED
&SYSPLEX:
v Specify the desired substitution text for &SYSPLEX text
on the SYSPLEX parameter in the LOADxx parmlib Explanation: Where text is:
member.
v Specify SYSPLEX(&SYSPLEX.) on the SYSPLEX UNRESOLVED STATIC SYMBOL DEFINITIONS FOLLOW:
parameter in the COUPLExx parmlib member, which IEASYMyy:&symbol-name = symbol-text
ensures that &SYSPLEX. resolves to the substitution
.
text defined on the SYSPLEX parameter in LOADxx. .
.
IEASYMzz:&symbol-name = symbol-text
Detecting Module: IEAVESYM
The system found one or more static system symbol
IEA011A RESPECIFY ENTIRE IEASYMXX definitions that are circular. That is, one or more system
SUFFIX LIST OR U TO BYPASS symbol definitions contain other system symbols that
refer back to each other.
Explanation: If this message is preceded by message
IEA013E, one of the following occurred:
The following is an example of a circular system symbol
v The system found an error in a parameter or definition:
parameter value in one or more IEASYMxx parmlib
SYMDEF(&LNK.='&APF.(-2:2)')
members that were used during IPL. SYMDEF(&APF.='&LNK.(-2:2)')
v The system could not find an IEASYMxx member
specified in LOADxx parmlib member. In the example above, the definition of &APF. depends
on the resolution of &LNK. . However, because the
Otherwise, the system found a syntax error in the definition of &LNK. also depends on the resolution of
IEASYMxx parmlib member. &APF. , the two system symbols can never be resolved.
The system issues this message only for statements in In the message text:
IEASYMxx that apply to the processor or LPAR on
which this system is being initialized. xx The suffix of the first IEASYMxx parmlib member in
which a circular definition appears.
System Action: The system issues this message on
the nucleus initialization program (NIP) console and yy The suffix of the last IEASYMxx parmlib member in
waits for the operator to respond. The system discards which a circular definition appears.
any processing of IEASYMxx members that occurred &symbol-name
before the error. The system might issue messages that The name of the installation-defined system symbol
describe the error prior to issuing this message, as that specifies a circular definition.
described in the message explanation.
symbol-text
System Programmer Response: Do one of the The unresolved substitution text.
following:
System Action: The system enters non-restartable
v If you want to respecify the IEASYMxx members,
wait state X'07D' with return code X'0000'.
enter all the suffixes of the IEASYMxx members in
response to this message. (For example, if you System Programmer Response: Correct the circular
specified three IEASYMxx suffixes and only one was reference in the IEASYMxx parmlib member, then reIPL
not valid, you must respecify the two valid suffixes, the system.
and replace or remove the suffix that was not valid.)
v Reply U to bypass IEASYMxx processing and
continue with system initialization. Detecting Module: IEAVNPCF

IEA013E ERROR DETECTED PROCESSING
Detecting Module: IEAVNPIL IEASYMxx: text
001 MEMBER NOT FOUND
002 RESERVED SYMBOLIC DEFINED :
system-symbol-name
003 SYMBOL LENGTH ERROR :
system-symbol-name

004 SYMBOL NAME ERROR: system-symbol-name required ampersand (&) at the beginning and
005 MAXIMUM DEFINITIONS EXCEEDED AT the period (.) at the end.
SYMBOL: system-symbol-name
System Programmer Response: Change
006 DATA LENGTH ERROR FOR SYMBOL:
symbol name specified on the SYMDEF
system-symbol-name
parameter to a name is 1-8 characters long
007 UNDEFINED PARAMETER DETECTED:
(excluding the ampersand and the period).
parameter-name
Then respond to message IEA011A.
008 DATA FOR parameter-name IN ERROR:
parameter-value 004 Meaning: A SYMDEF parameter in a
IEASYMxx parmlib member did not begin with
The system found an error in an IEASYMxx parmlib an ampersand (&) followed by an alphanumeric
member. or national character.
System Programmer Response: Change
symbol name specified on the SYMDEF
xx The suffix of the IEASYMxx parmlib member in parameter to a name that begins with an
which the error occurred. ampersand followed by an alphanumeric or
national character. Then respond to message
system-symbol-name IEA011A.
The name of a system symbol, defined in
IEASYMxx, that contained an error. 005 Meaning: The number of installation-defined
system symbols exceeds the maximum of 100
parameter-name for this system.
The name of a parameter in IEASYMxx that
contained an error. System Programmer Response: Reduce the
number of installation-defined system symbols
parameter-value in the IEASYMxx parmlib member so there are
The value of a parameter in IEASYMxx that no more than 100 for the system. Then
contained an error. respond to message IEA011A.
The reason code in the message text identifies the 006 Meaning:
error: v A SYMDEF parameter in an IEASYMxx
parmlib member specified a substitution text
Code Meaning and Action that is too long. The substitution text is
001 Meaning: The system could not find the longer than the length of the associated
IEASYMxx parmlib member specified in the system symbol name, which includes the
LOADxx parmlib member. ampersand (&) character. For example, the
length of the value assigned to the symbol
System Programmer Response: Change the &FRED. cannot exceed five characters.
value on the IEASYM parameter in LOADxx so v A SYSCLONE parameter in an IEASYMxx
it specifies one or more valid IEASYMxx parmlib member specified a substitution text
parmlib members. Then respond to message that was not 1 or 2 characters long.
IEA011A.
002 Meaning: A SYMDEF parameter in the System Programmer Response: Change the
IEASYMxx parmlib member specified a symbol system symbol definition in IEASYMxx to
that is reserved for system use (for example, specify a substitution text that does not exceed
&SYSNAME., which specifies the system the length of the system symbol name or
name). correct the SYSCLONE parameter specification
in IEASYMxx. Then respond to message
System Programmer Response: See the IEA011A or re-IPL.
section on defining system symbols in OS/390
MVS Initialization and Tuning Reference for a 007 Meaning: A parameter is specified in a
list of symbols that are reserved for system IEASYMxx parmlib member. The undefined
use. Change the symbol name specified on the parameter is displayed in the message text.
SYMDEF parameter to a name that is not System Programmer Response: Correct the
reserved for system use. Then respond to name of the parameter in IEASYMxx. Then
message IEA011A. respond to message IEA011A.
003 Meaning: A SYMDEF parameter in an 008 Meaning: An undefined parameter in a
IEASYMxx parmlib member specified a symbol IEASYMxx parmlib member specified a value.
name that is too long. Symbol names must The parameter and its value are displayed in
consist of 1-8 characters, excluding the the message text.

System Programmer Response: Correct the IF THIS EVENT OCCURRED ON SOME, BUT NOT
parameter and the value in IEASYMxx. Then ALL SYSPLEX MEMBERS, THE LIKELY CAUSE IS
respond to message IEA011A. A LINK FAILURE. TO FIX, ENSURE THAT EACH
AFFECTED SYSTEM HAS AT LEAST ONE CORRECTLY
System Action: The system will do one of the
CONNECTED AND FUNCTIONAL LINK.
following:
v Issue message IEA011A, which asks the operator to
IF THIS EVENT OCCURRED ON ALL SYSPLEX MEMBERS,
respecify the suffix for IEASYMxx. The system issues
THEN THE LIKELY CAUSE IS A SYSPLEX TIMER FAILURE.
message IEA011A only for statements in IEASYMxx
TO FIX, REFER TO THE MESSAGE
that apply to the processor or LPAR on which this
IEA015A DESCRIPTION IN MVS SYSTEM MESSAGES.
system is being initialized.
v Continue with the IPL. This action is taken when the
AFTER FIXING THE PROBLEM, REPLY ″RETRY″ FROM THE
error occurs in a statement that does not apply to this
SERVICE CONSOLE (HMC). IF THE PROBLEM WAS NOT
system.
CORRECTED, THIS MESSAGE WILL BE REISSUED AND YOU
v Enter a non-restartable wait state X’07D’ with reason
MAY TRY AGAIN. REPLY ″ABORT″ TO EXIT MESSAGE
code X’0004’. The system enters the wait state when
LOOP. PROBABLE RESULT: 0A2-114 WAITSTATE
the error occurs in a statement that applies to this
system and it was discovered at a point too late to
The system has lost all connections to its sysplex
accept a new IEASYMxx.
timer(s).
System Action: The system waits for a reply to
System Programmer Response: See the system message IEA015A.
programmer response in the list of reason codes in the
message explanation.
loss of Sysplex Timer connectivity occurred, repair the
Detecting Module: IEAVNPIL, IEAVNPCF problem, and then reply to the message on each
system where it occurs.
IEA014W NONRECOVERABLE ERROR IN There are two basic scenarios for which this message
IEASYMxx PROCESSING may be issued. You should first determine if a subset of
the ETR synchronized MVS images have issued
Explanation: The system found an error in an
IEA015A or whether ALL have issued it. If only a few
IEASYMxx parmlib member from which it cannot
MVS images issued IEA015A, then it is likely that ETR
recover.
links have failed to those machines. Repair the failed
In the message text: links and then reply with ″RETRY″ on each issuing
system. If the problem was corrected, processing will
xx The suffix of the IEASYMxx parmlib member in resume. If the problem was not resolved, the message
which the error occurred. will be reissued until the problem is fixed or until you
System Action: The system might also issue reply ″ABORT″. A reply of of ″ABORT″ will result in a
message IEA012E or IEA013E. The system enters 0A2-114 waitstate if the MVS image is a member of a
non-restartable wait state X'07D' with reason code multisystem Sysplex. If it is not, processing will resume
X'0004'. in local TOD clock mode.
Operator Response: Contact the system programmer. If ALL ETR synchronized MVS images issue IEA015A,
then there has been a failure of one or both Sysplex
System Programmer Response: If the system issues Timers. If one Sysplex Timer fails, the other may go into
message IEA012E or IEA013E, see the system dormant state when it can not communicate with the
programmer responses for those messages. Otherwise, failed 9037. In this case, it may be possible to recover
see the system programmer response for wait state the dormant 9037 and then reply ″RETRY″ as
X'07D' with reason code X'0004'. previously described. See the redbook SG24-2070-00,
Source: System initialization (IPL/NIP) S/390 Time Management and IBM 9037 Sysplex Timer
for more information on how to recognize this condition
Detecting Module: IEAVNPCF and how to recover from it. See sections 10.12 and
10.13 in Chapter 10 for detailed information.
IEA015A text Source: Timer Supervision
Explanation: In the message, text is: Detecting Module: IEATSWLH
THIS SYSTEM HAS LOST ALL

CONNECTION TO THE SYSPLEX TIMER.

IEA016W REQUIRED LEVEL OF DFSMS IS NOT
programmer response for wait state X'084' in OS/390
INSTALLED
MVS System Codes.
Explanation: The current release of OS/390 requires
Source: Recovery termination manager (RTM)
a particular release of DFSMS in order to IPL. OS/390
R10 requires DFSMS R10. Detecting Module: IEAVTRTV
System Action: The system issues wait state code
X'009' reason 0. IEA024I ERROR IN GTF. opt TRACE OPTION
WAS DISABLED
System Programmer Response: Install the proper
release of DFSMS, and then re-IPL. Explanation: During formatting of the trace table of
the generalized trace facility (GTF), the dump formatter
found an error record for a trace option. This error
Detecting Module: IEAVNPC4 record was produced when GTF encountered a program
check while attempting to create a trace record.
IEA020W AN FRR STACK POINTER FOR CPU x This message is followed by a hexadecimal dump of the
IS DAMAGED, THE ERROR MASK IS error record. Refer to messages AHL118I and AHL1201.
abcdefghijklmnopqrst.
Explanation: MVS found found uncorrectable damage
opt The trace option, which is one of the following:
to at least one functional recovery routine (FRR) stack
DSP
pointer.
EXT
The CPU which had the damaged stack pointer or IO
pointers is identified by the value for x. PI
SIO
The error mask tells you which FRR stack pointers were
SVC
incorrect.
v If a is 1, PSACSTK is incorrect. System Action: The program check for the error
record caused GTF to bypass recording further events
v If b is 1, PSANSTK is incorrect.
for the trace option. However, GTF continued to record
v If c is 1, PSASSTK is incorrect. all events for the other trace options requested.
v If d is 1, PSAMSTK is incorrect.
After issuing this message, the system writes a
v If e is 1, PSAPSTK is incorrect. hexadecimal dump of the error record. Refer to
v If f is 1, PSAESTK1 is incorrect. messages AHL118I and AHL1201.
v If g is 1, PSAESTK2 is incorrect.
Note: If opt is SVC, SVC tracing will continue.
v If h is 1, PSAESTK3 is incorrect.
v If i is 1, PSARSTK is incorrect. System Programmer Response: Ensure that problem
programs are not altering the GTF region.
v If j is 1, PSATSTK is incorrect.
v If k is 1, PSAASTK is incorrect. Ensure that sufficient storage is available within the
GTF region for a SNAP dump (an additional 4 kilobytes
v If l is 1, PSASSAV is incorrect.
is needed for ABDUMP/SNAP processing). Ensure that
v If m is 1, PSAMSAV is incorrect. the GTFSNP cataloged procedure is used to obtain an
v If n is 1, PSAPSAV is incorrect. ABDUMP/SNAP dump.
v If o is 1, PSAESAV1 is incorrect. Search problem reporting data bases for a fix for the
v If p is 1, PSAESAV2 is incorrect. problem. If no fix exists, contact the IBM Support
v If q is 1, PSAESAV3 is incorrect. Center.
v If r is 1, PSARSAV is incorrect. Source: Generalized trace facility (GTF)

v If s is 1, PSATSAV is incorrect.
v If t is 1, PSAASAV is incorrect. IEA025I INVALID GTF RECORD FOLLOWS
System Action: The system: Explanation: During formatting of the trace table of
1. Issues this message. the generalized trace facility (GTF), the dump formatter
found a GTF record with an incorrect EID or FID field.
2. Places all processors on this system in ABDUMP prints this message and follows it with a
non-restartable X'084' wait state, with reason code hexadecimal dump of the error record.
X'04'.
wait state X'084' in OS/390 MVS System Codes. System Programmer Response: Ensure that problem

programs are not altering the trace table. specified on the command. The system continues
processing.
Source: Generalized trace facility (GTF)
System Programmer Response: Avoid setting
Detecting Module: IGC0F05A
multiple traps that are likely to contend for the resource
needed for remote action processing.
IEA030I OPEN FAILED FOR DUMP DATA SET
Source: SLIP
FOR {JS|ST} DUE TO {Scde|Ucde}
Detecting Module: IEAVTSL2
Explanation: While abending a task, the system tried
to open a SYSABEND, SYSMDUMP, or SYSUDUMP
dump data set, but failed. IEA040W REMOTE SLIP TRAP ID=xxxx FROM
SYSTEM ssssssss MATCHED.
ACTION=WAIT RESTART THE SYSTEM
JS A dump data set for the job step task could not be TO CONTINUE
opened.
Explanation: A remote system found a match for a
ST A dump data set for a subtask could not be SLIP trap. The SLIP trap requested that this system be
opened. placed into a wait state so that the operator could
capture diagnostic data.
Scde
The system was in the process of abnormally In the message text:
ending a task with system completion code cde.
ID=xxxx
Ucde The SLIP trap identifier specified on the SLIP
The system was in the process of abnormally command.
ending a task with user completion code cde.
ssssssss
System Action: The system does not write a dump, The system on which the trap matched.
but abends the task. The system sends messages
System Action: This system is placed into a
about the problem to the job log.
restartable wait state.
System Programmer Response: Do the following:
Operator Response: Perform the actions requested
1. Continue diagnosis with the original completion by the system programmer for this trap.
code.
Either:
2. Use the messages in the job log to determine why
the system could not open the dump data set. v Restart the system.
3. If the problem appears to be in the system, search v Obtain a stand-alone dump and reIPL the system.
problem reporting data bases for a fix for the System Programmer Response: To capture
problem. If no fix exists, report the problem to the diagnostic data, ask the operator to obtain a
IBM Support Center. Provide the messages from the stand-alone dump. The system cannot be restarted if a
job log and all problem data for the original abend. stand-alone dump is written; ask the operator to reIPL
Source: Recovery termination manager (RTM) the system.
Detecting Module: IEAVTABD Source: SLIP

IEA039I SLIP TRAP ID=xxxx REMOTE ACTION
WAS NOT PERFORMED. IEA041I SDUMP SCHEDULED FOR REMOTE
Explanation: A SLIP trap requested ACTION=SVCD SLIP TRAP ID=xxxx FROM SYSTEM
or ACTION=SYNCSVCD and also requested one or ssssssss
more remote actions. The system cannot activate the Explanation: A remote system found a match for a
action on the remote system because another SLIP trap SLIP trap. The SLIP trap requested that this system
with ACTION=WAIT or a remote action is active in the write an SVC dump. This system scheduled the SVC
system. dump.
ID=xxxx ID=xxxx
The SLIP trap identifier specified on the SLIP The SLIP trap identifier specified on the SLIP
command. command.
System Action: The system performs the local SVCD ssssssss
or SYNCSVCD action, but not the remote action The system on which the SLIP trap matched.

System Action: This system schedules an SVC dump specified on the MAXSPACE parameter of the
and continues processing. CHNGDUMP operator command at the time
the limit was reached.
Source: SLIP
System Action: SVC dump ends the capture of the
current dump. This dump will be written out to a dump
data set, but it will be a partial dump. SVC dump will not
IEA042I SDUMP NOT SCHEDULED FOR allow other dumps to be captured until the amount of
REMOTE SLIP TRAP ID=xxxx FROM available space is greater than the threshold value. The
SYSTEM ssssssss. REASON - text threshold value is the lower of two values: 35
megabytes or ten percent of the MAXSPACE value. To
Explanation: text is one of the following: view the amount of available space, use the DISPLAY
ANOTHER DUMP WAS IN PROGRESS DUMP command.
DUMP=NO WAS SET AT IPL OR INDICATED BY
CHNGDUMP Operator Response: Do one of the following:
NO SYS1.DUMP DATA SET WAS AVAILABLE v If any dump is captured, but there are no available
NO SRBS COULD BE SCHEDULED TO START dump data sets, use the DUMPDS command or
THE DUMP another utility to make dump data sets available.
SVC DUMP ABNORMALLY TERMINATED
v If any dump is captured but not required by the
A STATUS STOP SRBS CONDITION WAS
installation, reply D to message IEA793A to delete
DETECTED
the dumps.
A remote system found a match for a SLIP trap. The v Use the MAXSPACE parameter on the CHNGDUMP
SLIP trap requested that this system write an SVC command to increase the value of MAXSPACE,
dump. However, this system could not write the dump allowing SVC dump processing to use more virtual
for the reason indicated in the message. storage to hold captured dumps.
Source: SVC dump
ID=xxxx IEA050I DUPLEX IS AN OBSOLETE KEYWORD.
The SLIP trap identifier specified on the SLIP DUPLEXING NO LONGER
command. SUPPORTED.
ssssssss Explanation: Duplexing of PLPA and Common is no
The system on which the SLIP trap matched. longer supported.
text System Action: The system continues processing.
The reason why the system could not write the However, the DUPLEX keyword is ignored, and no
SVC dump. duplexing occurs.
System Action: The system processes the SLIP Operator Response: None.
command, but the system does not write the requested
SVC dump. Source: Auxiliary Storage Manager
System Programmer Response: Determine why the Detecting Module: ILRASRIM

remote system could not write an SVC dump. If the
problem cannot be corrected, search problem reporting IEA051I THE PAGTOTL SWAP PARAMETER IS
data bases for a fix for the problem. If no fix exists, OBSOLETE AND IS IGNORED.
notify the IBM Support Center.
Explanation: Swap data sets are no longer supported.
Source: SLIP The swap parameter specified for the PAGTOTL
Detecting Module: IEAVTSL5 keyword is ignored.
IEA043I SVC DUMP REACHED MAXSPACE However, the swap parameter is ignored.
LIMIT - MAXSPACE=xxxxxxxx MEG Operator Response: None.
Explanation: The limit that an installation placed on Source: Auxiliary Storage Manager
the amount of storage available for SVC dump to hold
captured dumps is reached. Detecting Module: ILRASRIM

xxxxxxxx
The amount of storage, in megabytes,

IEA052I THE SWAP KEYWORD IS OBSOLETE IEA084W ENTRY POINT entrypt NOT FOUND IN
AND IS IGNORED. THE NUCLEUS
Explanation: Swap data sets are no longer supported. Explanation: During system initialization, the system
The SWAP keyword specified in the IEASYSxx parmlib could not find an entry point in the nucleus for one of
member or on the IPL parameters is ignored. the following:
v A device descriptor table (DDT)
v An error recovery program (ERP)
However, the SWAP keyword is ignored, and the
v The unit control blocks (UCB)
system will continue without dedicated swap data sets.
v The device class queue (DCQ)
Operator Response: None. v The device characteristic table (DCT)
Source: Auxiliary Storage Manager The system loaded one of the following:
Detecting Module: ILRASRIM v An incomplete nucleus

v An incomplete I/O configuration
IEA080D IOS KEYWORD PARAMETER INVALID. v Both an incomplete nucleus and an incomplete I/O
REPLY IOS=XX OR IOS=DEFAULT configuration
Explanation: In response to message IEA101A or In the message text:

IEA080I, the operator entered an incorrect IECIOSxx
parmlib member on the IOS=xx parameter. entrypt The entry point address.
System Action: The system waits for the operator to System Action: The system enters nonrestartable
respond. The system issues this message on the disabled wait state X'035'.
nucleus initialization program (NIP) console. Operator Response: See the operator response for
Operator Response: Reply with one of the following wait state X'035'.
responses: System Programmer Response: See the system
REPLY 0,IOS=xx, where xx is a valid member programmer response for wait state X'035'.
REPLY 0,IOS=DEFAULT
REPLY 0,IOS=DEF Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL03
In the case of the last two responses, the system uses
the IBM defaults for MIH and HOTIO.
IEA086I memname NOT FOUND IN
Source: Input/output supervisor (IOS) SYS1.NUCLEUS
Explanation: The initial program load (IPL) program
IEA081I ERROR - IECIOSxx RECORD nnnn I/O was unable to locate in SYS1.NUCLEUS a member
ERROR specified on an INCLUDE statement of NUCLSTxx. The
Explanation: During system initialization, the system NUCLST statement of LOADxx did not specify that a
could not read a record from the IECIOSxx parmlib wait state is to be loaded if any of the INCLUDE
member. statements in the NUCLSTxx member specify a
member that cannot be found in SYS1.NUCLEUS.
This message appears on the nucleus initialization
program (NIP) console. In the message text: In the message text:
IECIOSxx memname
The parmlib member, with the suffix xx. The missing member.
nnnn The record name. System Action: The IPL proceeds.
System Action: System initialization continues. The Operator Response: Notify the system programmer.
system processes all previous records to establish the System Programmer Response: Either provide the
missing interrupt handler (MIH) and HOTIO missing member or update NUCLSTxx.
environment. The system rejects the unreadable record
and all records that follow it. Source: System initialization (IPL/NIP)
Source: Input/output supervisor (IOS) Detecting Module: IEAIPL41

IEA086W memname NOT FOUND IN
programmer response for wait state X'025'.
SYS1.NUCLEUS
was unable to locate a necessary member in the Detecting Module: IEAIPL41
SYS1.NUCLEUS data set.
In the message text: IEA088W NUCLEUS REQUIRES MORE STORAGE
BELOW 16MB THAN IS AVAILABLE
memname
The missing member, as follows: Explanation: Initial program load (IPL) cannot
continue because the system does not have enough
IEANUC0x
virtual storage. The DAT-on nucleus requires more
x may not be the correct identifier for the
storage than is available below 16 megabytes. (DAT is
nucleus you need.
the acronym for dynamic address translation.)
If memname is another name, the member is either a System Action: The system enters non-restartable
module list table (MLT), a nucleus module list (NML), a wait state X'071'.
nucleus device support module, or a member that was
This message appears in the IPL WTO buffer.
specified on an INCLUDE statement in the NUCLSTxx
member. System Programmer Response: See the system
disabled wait state X'055'. Source: Initial program load (IPL)
Because a console is not available for messages at IPL Detecting Module: IEAIPL41
time, the system stores this message in the IPL WTO
buffer.
IEA089W memname HAS MORE THAN 1 CSECT
Operator Response: See the operator response for BUT WAS NOT LINK EDITED WITH
wait state X'055' SCTR OPTION
System Programmer Response: See the system Explanation: The system detected an error with a
programmer response for wait state X'055'. member of the SYS1.NUCLEUS being loaded into the
dynamic address translation (DAT)-on nucleus region
during system initialization. The member contained
Detecting Module: IEAIPL02 more than one control section (CSECT) and was not
link-edited with the scatter (SCTR) option.
IEA087W ENTRY POINT entrypt APPEARS IN In the message text:
mod1 AND mod2
memname
Explanation: The system detected a duplicate entry The member of SYS1.NUCLEUS in error.
point name appearing in more than one module. The
entry points appear in modules being loaded into the
disabled wait state X'054' with reason code X'01'.
DAT-on nucleus. (DAT is the acronym for dynamic
Because a console is not available for messages at IPL
address translation.)
time, the system stores this message in the IPL WTO
In the message text: buffer.
entrypt The duplicate entry point name Operator Response: See the operator response for
wait state X'054'.
mod1 The first module where the duplicate entry
point name appears. System Programmer Response: See the system
mod2 The second module where the duplicate entry
point name appears. Source: System initialization (IPL/NIP)
This message accompanies wait state code X'025'.
IEA090W LOAD REAL ADDRESS FAILED
wait state X'025'. Because a console is not available for
DURING irimname PROCESSING
messages at IPL time, the system stores this message
in the IPL WTO buffer. Explanation: An initial program load (IPL) resource
initialization module (IRIM) issued a Load Real Address
(LRA) instruction that failed to return a valid real
wait state code X'025'.
address.

In the message text: contains the unresolved external reference.
irimname If IBM supplied the module, search problem reporting
The IRIM that issued the failed instruction. data bases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
wait state X'074' with reason code X'06'. Because a Source: System initialization (IPL/NIP)
console is not available for messages at IPL time, the
system stores this message in the IPL WTO buffer.
IEA093I MODULE modname CONTAINS
wait state X'074'.
UNRESOLVED WEAK EXTERNAL
System Programmer Response: See the operator REFERENCE refname
response for wait state X'074'.
Source: System initialization (IPL/NIP) loaded a module into the DAT-on nucleus region. (DAT
is the acronym for dynamic address translation.)
However, the module contained an unresolved external
reference.
IEA091I NUCLEUS x SELECTED
Explanation: The system selected module IEANUC0X
modname
as the base nucleus module to load into the DAT-on
The nucleus module
nucleus region. (DAT is the acronym for dynamic
address translation.) The system issues this message refname
so that the operator can verify the nucleus selected. The unresolved external reference
In the message text: System Action: The IPL proceeds. The unresolved
external references should not affect the success of the
x The identifier for the nucleus module,
IPL or subsequent processing.
IEANUC0x
System Programmer Response: This might be a
System Action: The initial program load (IPL)
normal situation. Consult the program directory and the
program loads IEANUC0x into the DAT-on nucleus
PSP bucket to ensure that the reason for this message
region.
is expected. If the message is expected, ignore it.
Operator Response: If x is the correct identifier, no
response is necessary. If x is incorrect, reIPL the
system, specifying the correct identifier for the nucleus. Detecting Module: IEAIPL02
IEA099A JOBNAME= jobname ASID= asid HAS
REACHED THE WTO BUFFER LIMIT
Explanation: The number of write to operator (WTO)
IEA092I WARNING: UNRESOLVED EXTERNAL
buffers for an address space has reached the limit
REFERENCE symbol IN MODULE
specified in the MLIM field of the CONSOLxx parmlib
modname
member.
loaded a module into the DAT-on nucleus region. (DAT
is the acronym for dynamic address translation.) Operator Response: Notify the system programmer.
However, the module contained an unresolved external
System Programmer Response: Do one of the
reference.
following:
In the message text: v If the program is in a WTO loop, correct the program.
symbol The unresolved external reference v Increase the value of the MLIM field in the
CONSOLxx parmlib member.
modname
The nucleus module v Automate the message to slow down or cancel the
offending address space.
System Action: The IPL proceeds, but the success of
ATTENTION: Data may be lost if you do not use
the IPL or subsequent processing is unpredictable.
caution when cancelling the address space.
Operator Response: Notify the system programmer. v Modify the WTO macro so it uses the
System Programmer Response: If the module is MCSFLAG=BUSYEXIT parameter. The system stops
IEANUC0x, link edit it again to determine which CSECT

WTO processing and returns control to the program System Action: The system prompts the operator for
issuing the macro when the WTO buffer limit is a reply, then changes the system parameters as
reached. specified by the operator.
Source: Communications task (COMMTASK) Operator Response: Reply as specified by the
system programmer, for example:
Detecting Module: IEAVH600
REPLY 00,CLPA,SYSP=83,LNK=(04,05,PQ),SYSNAME=AQ
IEA100I ETR SERVICE INFORMATION IS If the reply is longer than one line (there are 80
PROVIDED. REASON characters per line), you can follow the last parameter
CODE=reason-code with a comma or a blank and CONT. For details about
Explanation: The External Time Reference (ETR) specifying system parameters, including how to continue
provided service information. ETR is the MVS generic system parameters, see the description of the REPLY
name for the IBM Sysplex Timer (9037) or equivalent. command in OS/390 MVS System Commands.
In the message text: System Programmer Response: Tell the operator

which responses to enter.
REASON CODE=reason-code
A reason code explaining the information follows. For
more information about the reason codes, see Detecting Module: IEAVNPC4
Maintenance Information for the 9037 Sysplex Timer.
These codes are informational and require no action. IEA102W OPERATOR PROMPT NOT ALLOWED
005 Unit recovered. FOR A SYSPLEX TEST DATESOURCE
LPAR
006 Control Link A operational.
Explanation: In the CLOCKxx parmlib member,
007 Control Link B operational. OPERATOR PROMPT is specified. This is not a valid
008 Communication established with console. specification when IPLing a sysplex datesource LPAR.
009 Communication established with standby System Action: The system enters a non-restartable
console. wait state.
038 Maintenance mode set. Operator Response: Notify the system programmer.
039 Maintenance mode cleared. System Programmer Response: Modify the

CLOCKxx parmlib member for the sysplex datesource
042 The 9037 is now tracking the external time LPAR to specify OPERATOR NOPROMPT.
source. This service request is provided to
indicate a prior problem has been resolved. Source: Timer supervision
System Action: Processing continues. Detecting Module: IEAVNP21
Source: Timer supervision

IEA107I prm IGNORED
Detecting Module: IEATEEIH
Explanation: In reply to message IEA101A, the
IEATESMR operator specified a value for a parameter, prm.
However, in the current IEASYSxx parmlib member,
OPI=NO is specified for that parameter. The system
IEA101A SPECIFY SYSTEM PARAMETERS FOR
therefore rejects the value specified by the operator.
xx...x
System Action: The nucleus initialization program
Explanation: This message is issued during system
(NIP) continues processing.
initialization to allow the operator to change certain
system parameters. Operator Response: If requested by the system
programmer, obtain a stand-alone dump
xx...x Contains the full product name, version,
parameter was not restricted from operator changes in
release, modification level and FMID. For
the IEASYSxx parmlib member (OPI=NO option).
example, in OS/390 Release 2, xx...x is
01.02.00 JBB6602. If IEASYSxx is correct and if the problem persists,
This field can be changed by the installation
using the SPZAP service to change the value
Center. Provide a stand-alone dump.
in the CVTVERID field of the communication
vector table (CVT). Source: System initialization (IPL/NIP)

Detecting Module: IEAVNP03 cause of the problem. If replying WAIT does not resolve
the problem, then determine if the IPL can continue
without the device. If it can, tell the operator to reply
IEA116A CONTINUE SYSTEM PARAMETERS
‘CONT’. If the device is required for NIP processing, tell
Explanation: During nucleus initialization, the reply to the operator to reIPL the system using the appropriate
message IEA101A specified CONT as its final entry. backup device.
CONT indicates that the reply was incomplete and that
Source: Input/Output Supervisor (IOS)
additional parameters are to be specified.
Detecting Module: IEAVNP02
System Action: The system prompts the operator for
a reply.
IEA121I UNABLE TO OBTAIN
Operator Response: Continue the reply to message
CHANNEL-SUBSYSTEM INFORMATION
IEA101A. Begin the continuation with REPLY 00.
DUE TO A BUSY CONDITION. IPL
Source: System initialization (IPL/NIP) CONTINUES.
Detecting Module: IEAVNPC4 Explanation: During system initialization, the system
returned a busy condition.
IEA120A DEVICE dev VOLID NOT READ, REPLY System Action: System initialization continues.
‘CONT’ OR ‘WAIT’
Operator Response: Contact hardware support.
Explanation: A direct access storage device (DASD)
Source: Input/output supervisor (IOS)
did not respond to a request to read the volume label.
Possible causes include:
v The device is shared and is reserved by a processor IEA122I ERROR OBTAINING CHANNEL
other than the initializing processor. SUBSYSTEM INFORMATION DUE TO
HARDWARE FAILURE. IPL
v A hardware malfunction could be causing the device
CONTINUES.
to appear busy.
Explanation: During system initialization, the system
In the message text: tried to issue the channel-subsystem information
command. A hardware failure occurred.
dev
The device number. System Action: System initialization continues.
System Action: The system waits for the operator to Operator Response: Contact hardware support.
reply.
Take one of the following actions:
IEA123I CONSOLE DELAYED SVC
v Enter REPLY id, ‘WAIT’ to cause the system to wait PROCESSING RESUMED. RESTART
for the device to become available. If the device is SUCCESSFUL
still not available after 15 seconds, the system issues
message IOS124A to prompt the operator again. Explanation: The system previously issued message
IEA544I or IEA555E. The system restart was successful
v Enter REPLY id,‘CONT’ to purge outstanding I/O
after the problems indicated by message IEA544I or
requests and mark the device offline. Replying CONT
IEA555E were resolved.
means that the device is no longer available; NIP
processing continues without it. System Action: The system continues processing.
Because the device is no longer available, replying Source: Communications task (COMMTASK)
CONT can cause later errors if the device, such as
the SYSRES device is required for NIP processing. Detecting Module: IEAVM613
Thus, reply ‘CONT’ only when the device is not
available because of a hardware problem that can IEA124I SYSTEM CONSOLE consname
not be corrected and the device is not required for QUEUING RESUMED
NIP processing.
Explanation: After the system suspended message
While it is also possible to take no action, (which the queuing to a console, the system resumed message
system considers an implicit ‘WAIT’), do so only at the queuing to that console.
direction of the system programmer. Taking no action is In the message text:
an appropriate response only for a device that times out
and is not required for NIP processing. consname
The system console name.

System Action: The system continues processing. v Enter the CONTROL M,RLIM command to increase
the value of the buffer limit.
Source: Communications task (COMMTASK)
v Use the VARY CN command to remove routing codes
Detecting Module: IEAVM605 from the system console, or take other actions to
reduce the number of messages being sent to the
IEA125I SYSTEM CONSOLE consname console.
QUEUING SUSPENDED, ERROR CODE v Issue VARY CN(*) , DEACTIVATE from the system
= code console.
Explanation: The system suspended message Source: Communications task (COMMTASK)
queuing to the specified system console.
Detecting Module: IEAVM605
consname IEA127I SYSTEM CONSOLE NOT ACCEPTING
The system console name. [PRIORITY] OPERATOR INPUT
code The error code, which is one of the following: Explanation: The system could not initialize the
system console input listener exit routine.
Code Explanation
8001 The service processor logical console
is not available for output processing. PRIORITY
The system is not accepting operator input
8002 The message queue limit for the from the screen that accepts priority
system console was reached. commands.
8003 The system found an internal queue System Action: The system console does not process
error. any other commands.
System Action: Depending on the error code, one of Operator Response: Notify the system programmer.
the following:
Code System Action reporting data bases for a fix for the problem. If no fix
8001 The system does not display messages that exists, contact the IBM Support Center.
were queued to the system console. The Source: Communications task (COMMTASK)
system does not queue new messages to the
system console. Detecting Module: IEAVN701
8002, 8003
The system displays messages that were IEA128I SYSTEM CONSOLE ONLY
queued to the system console. The system SUPPORTING SYNCH OUTPUT
does not queue new messages to the system
Explanation: The system could not define the system
console.
console as an extended MCS console.
System Action: The system does not display
System Programmer Response: Search problem non-SYNCH messages on the system console.
Detecting Module: IEAVM605 exists, contact the IBM Support Center.
IEA126I THE SYSTEM CONSOLE QUEUE IS
Detecting Module: IEAVN701
80% FULL
Explanation: The buffer that holds the messages on
IEA129I MASTER CONSOLE REQUIRED.
the system console queue is 80% full.
Explanation: The operator must use a console with
master authority because the hardware that supports
Operator Response: If desired, do one or more of the the enhanced system console function is not installed,
following: or the system console is not available. Also, one of the
v Reply to outstanding messages. following conditions exists:
v Cancel any jobs that are currently issuing messages. v CON is not specified on the system parameter.

v CON=NONE is specified on the system parameter, or
IEA139E PC/AUTH SERVICES ARE
in the IEASYSxx parmlib member.
INOPERABLE
System Action: The system prompts the operator to
Explanation: The system gave Program
specify a console with master authority on the CON
Call/authorization (PC/AUTH) recovery control.
parameter.
PC/AUTH recovery was unable to successfully validate
Operator Response: Enter the parmlib member name the PC/AUTH control blocks. This can be caused by an
that specifies a valid console with master authority on abend code X'053'.
the CON parameter. ReIPL the system.
System Action: The system issues an SVC dump. In
Source: Communications task (COMMTASK) most cases, tasks running when the error occurred
continue normally, and the Program Call (PC) instruction
Detecting Module: IEAVNPA1 and other cross-memory instructions can still be used.
After the error, programs that attempt to use PC/AUTH
IEA133E THE TRACE ADDRESS SPACE HAS services are abended with system completion code
TERMINATED X'053' reason code X'nn98'.
Explanation: The system trace address space has System Programmer Response: Do the following:
abnormally ended. v Obtain the SVC dump for this message.
System Action: The system continues processing. No v If abend X'053' with a reason code other than X'nn98'
system tracing is active. The system writes a logrec accompanies this message, see the system
data set error record and may write an SVC dump. programmer response for abend code X'053'.
v If the message is not accompanied by abend X'053',
Operator Response: Enter a TRACE ST command to
restart system tracing.
System Programmer Response: If the error recurs, Center. Provide the dump.
Source: Program Call/authorization (PC/AUTH)
Center. Provide the logrec data set error record and the Detecting Module: IEAVXPCR
SVC dump, if available.
Source: System trace IEA140W TOTAL SIZE OF NUCLEUS,
{SQA|ESQA}, {LPA|ELPA} TOO LARGE,
Detecting Module: IEAVETRM
NO SPACE FOR {CSA|ECSA}
Explanation: The system could not initialize the
IEA134I TRACE ERROR, REISSUE TRACE
common service area (CSA). No space is left for the
COMMAND IF STATUS NOT AS
CSA because the following storage areas, in
REQUESTED
combination, overlapped the private area:
Explanation: While processing a TRACE ST v The nucleus
command, the system detected an error. v The system queue area (SQA)
v The link pack areas (LPA)
The system attempts to record the error in logrec data System Action: The system enters restartable wait
set, write an SVC dump, and repair any problems in the state X'0E3'.
system trace structure.
Operator Response: If the status is not as requested,
enter the TRACE command again. To determine the
programmer response for wait state X'0E3'.
status, enter the TRACE STATUS command.
Source: Virtual storage manager (VSM)
System Programmer Response: If the error recurs,
search problem reporting data bases for a fix for the Detecting Module: IEAVNP08
Center. Provide the logrec data set error record and the
SVC dump, if available. IEA145E MESSAGES/COMMANDS MAY HAVE
BEEN LOST, COMMANDS MAY NEED
Source: System trace TO BE REISSUED
Detecting Module: IEECB925 Explanation: In a sysplex, commands, messages, or
both may have been lost.
System Action: The system writes an SVC dump and

Operator Response: If console sysplex integrity is resulted from a misspelling on the NONVIO system
critical, reIPL the system that issued the message to parameter. If it was, correct it. Otherwise, add the data
rejoin the sysplex. Otherwise, none. set to the list of data sets specified on the PAGE
system parameter, or remove it from the list specified on
the NONVIO system parameter.
exists, contact the IBM Support Center. Source: Auxiliary storage manager (ASM)
Source: Communications task (COMMTASK) Detecting Module: ILRASRM2
Detecting Module: IEAVR601
IEA163E ALL PAGING RESOURCES ARE
RESTRICTED VIA NONVIO
IEA152I HARDCPY SPECIFICATION INVALID
SPECIFICATION
Explanation: The operator responded to message
Explanation: All of the local paging data sets specified
IEA101A or IEA332A by specifying a device for a
on the PAGE system parameter are also specified on
hard-copy log. The device cannot be used for hard
the NONVIO system parameter. Therefore, the system
copy.
has no local paging data sets available for VIO. The
System Action: The system issues message auxiliary storage manager (ASM) must direct VIO pages
IEA332A. to NONVIO data sets.
Operator Response: See the operator response for System Action: System initialization continues.
the accompanying message.
System Programmer Response: If the system needs
Detecting Module: IEAVNPA1 a page data set for VIO pages, wait until system
initialization processing completes. Then ask the
operator to enter a PAGEADD command to add the
IEA153I HARDCPY CONSOLE UNAVAILABLE data set.
Explanation: In response to message IEA101A, the Source: Auxiliary storage manager (ASM)
operator specified a valid console for the HARDCOPY
field in the CONSOLxx parmlib member, but the console Detecting Module: ILRASRM1
is unavailable.
System Action: The system issues message IEA332A IEA166I VATLSTxx: NO VOLUME MATCH
after issuing this message. FOUND FOR VOLUME volser ON
DEVICE TYPE devicetype
the accompanying message. Explanation: During processing of the VATLSTxx
parmlib member, the system could not find a volume
Source: Communications task (COMMTASK) that matches a generic volume serial number entry.
Detecting Module: IEAVNPA1
Note: The system may issue this message when you
code a generic volume serial and every possible
IEA162I dsname CANNOT BE RECOGNIZED explicit volume serial covered by this generic
FOR NONVIO RESTRICTION volume serial in the VATLST. In this case, ignore
Explanation: The auxiliary storage manager (ASM) the message.
did not recognize a data set. The data set name
appeared in the list of page data sets specified on the In the message text:
NONVIO system parameter, but not on the list of paging
VATLSTxx The parmlib member, with a suffix of
data sets specified on the PAGE system parameter.
xx.
dsname
devicetype The type of device.
The name of the data set.
System Action: The system ignores the data set
the next VATLST statement.
name and continues processing the NONVIO system
parameter. Other system initialization continues. Operator Response: Verify that you have mounted
the correct volumes, and ask the programmer to check
the device type in the volume attribute statement.
System Programmer Response: Before the next
Source: Allocation/unallocation
system initialization, check to see if the problem

Detecting Module: IEAVAP02
IEA169I VATLSTxx: DUPLICATE
{SYSUSE|IPLUSE} SPECIFICATION
IEA167I VATLSTxx: VATDEF charstring IGNORED.
IGNORED. text
Explanation: During processing of the VATLSTxx
Explanation: text is one of the following: parmlib member, the system found more than one
UNRECOGNIZED KEYWORD SYSUSE or IPLUSE keyword. In the message text:
VALUE NOT VALID FOR IPLUSE
VATLSTxx
VALUE NOT VALID FOR SYSUSE
The parmlib member, with a suffix of xx.
The system issues this message during processing of System Action: VATLST processing ignores any
the VATLSTxx parmlib member. A character string on additional SYSUSE or IPLUSE keywords specified on a
the VATDEF statement is not a valid VATDEF keyword VATDEF statement.
or operand. In the message text:
System Programmer Response: Remove the
VATLSTxx duplicate SYSUSE or IPLUSE keyword from the
The parmlib member, with a suffix of xx. VATDEF statement.
charstring Source: Allocation/unallocation

The character string on the VATDEF statement.
System Action: VATLST processing ignores the
incorrect character string in the VATDEF statement.
IEA170I VATLSTxx: DUPLICATE VATDEF
System Programmer Response: Correct the SPECIFICATION IGNORED
character string on the VATDEF statement.
Explanation: During processing of the VATLSTxx
Source: Allocation/unallocation parmlib member, the system found a duplicate VATDEF
statement. When processing one or more parmlib
Detecting Module: IEAVAP01 members during an IPL, the system uses the SYSUSE
and IPLUSE keyword values specified in the first
IEA168I VATLSTxx: {VATLST|SYSTEM} VATLSTxx member. It ignores the VATDEF statements
DEFAULT USE ATTRIBUTE OF specified in subsequent members. In the message text:
{PUBLIC|PRIVATE|STORAGE} VATLSTxx
{USED.|ASSUMED.} The parmlib member, with a suffix of xx.
Explanation: The system issues this message during System Action: The system uses the values for
processing of the VATLSTxx parmlib member to indicate SYSUSE and IPLUSE specified on the VATDEF
the value of the IPLUSE or SYSUSE keyword: PUBLIC, statement in the first parmlib member. Processing
PRIVATE, or STORAGE. In the message text: continues with the next record in VATLSTxx.
VATLSTxx System Programmer Response: During IPL, the
The parmlib member, with a suffix of xx. system uses the keyword values specified on the first
USED The installation explicitly defined the value on a parmlib member. Remove the duplicate keyword from
VATDEF statement. subsequent parmlib members before the next IPL.
ASSUMED Source: Allocation/unallocation

The installation did not explicitly define the Detecting Module: IEAVAP01
value.
System Action: VATLST processing continues with IEA171I VATLSTxx: MISSING RIGHT
the next member. PARENTHESIS ON VATDEF
System Programmer Response: Check the value STATEMENT.
indicated for the IPLUSE keyword. If the messages Explanation: The system issues this message during
indicate an assumed value and you want an explicit processing for the VATDEF statement in the VATLSTxx
value, specify that value on the VATDEF statement. parmlib member. The VATDEF statement contains a
Source: Allocation/unallocation keyword that is missing a right (ending) parenthesis.
The system assumes a right parenthesis following the
Detecting Module: IEAVAP01 last operand. In the message text:
VATLSTxx
System Action: VATLST processes the VATDEF

statement and continues on to the next record. Operator Response: Notify the system programmer.
ReIPL the system.
System Programmer Response: Before the next IPL,
add a right parenthesis to the VATDEF statement. System Programmer Response: See the system
Source: Reconfiguration
IEA180I USING IBM DEFAULT PFK
DEFINITIONS. NO PFK TABLES IEA183W RECONFIGURATION INITIALIZATION
REQUESTED. FAILED TO OBTAIN SIDE
INFORMATION FROM THE SERVICE
Explanation: The CONSOLxx parmlib member did not
PROCESSOR.
contain a PFKTABxx member.
Explanation: During reconfiguration initialization, the
System Action: The system uses IBM-supplied
system requested side information from the service
defaults for the program function keys (PFKs) for all
processor. The service processor did not return side
consoles.
information. This is probably a hardware error.
Operator Response: To specify PFK definitions, enter
a SET PFK=xx command. Then enter a CONTROL
wait state X'020' The system writes a logrec data set
N,PFK=xx command for each console.
error record about the failure.
Detecting Module: IEAVC701 ReIPL the system.
IEA181I USING IBM DEFAULT PFK programmer response for wait state X'020'.
DEFINITIONS. ERROR DURING PFK
PROCESSING
Explanation: The system could not change the
definition of the program function keys (PFKs).
IEA184W RECONFIGURATION INITIALIZATION
System Action: The system ignores the specified
FAILED TO OBTAIN THE LENGTH OF
PFKTABxx field and uses IBM-supplied defaults for the
THE SIDE INFORMATION BLOCK
PFKs for all consoles.
Explanation: During reconfiguration initialization, the
Operator Response: To specify PFK definitions, enter
system tried to obtain the length of the resource group
a SET PFK=xx command. Then enter a CONTROL
information block but failed.
N,PFK=xx command for each console. If the problem
persists, notify the system programmer. System Action: The system enters non-restartable
wait state X'020'. The system writes a logrec data set
exists, contact the IBM Support Center. Operator Response: Notify the system programmer.
ReIPL the system.
Detecting Module: IEAVC701
IEA182W RECONFIGURATION INITIALIZATION
FAILED TO OBTAIN CHANNEL PATH Detecting Module: IEEVORGI
INFORMATION FROM THE SERVICE
PROCESSOR.
IEA186I FORMAT OF THE CSCBLOC SYSTEM
Explanation: During reconfiguration initialization, the PARAMETER IS NOT VALID.
system requested channel path information, but the
Explanation: The syntax of the CSCBLOC system
service processor did not return channel path
initialization parameter in the IEASYSxx parmlib
information. This is probably a hardware error.
member is incorrect.
System Action: The system defaults the CSCBLOC
wait state X'020' The system writes a logrec data set
parameter to CSCBLOC=ABOVE.

System Programmer Response: If necessary, In the message text:
change the CSCBLOC parameter so it is in one of the
CONSOLxx
following formats:
The parmlib member with a suffix of xx.
CSCBLOC=ABOVE
CSCBLOC=BELOW dev
CSCBLOC=(ABOVE) The device number.
CSCBLOC=(BELOW)
UNIT NOT SUPPORTED.
Source: Communications task (COMMTASK) The system does not support the specified device.
Detecting Module: IEAVNPB1 NO IODEVICE STATEMENT FOR dev.
The specified console device was not defined in the
IODF.
IEA187I FORMAT OF THE CON SYSTEM
PARAMETER IS NOT VALID. System Action: The system ignores the specified
console.
Explanation: The CON parameter on the CONSOLE
statement in a CONSOLxx parmlib member is incorrect. System Programmer Response: Ensure that the
device number and device type are specified in the
System Action: The system issues message
IODF and in a CONSOLE statement in the CONSOLxx
IEA332A.
parmlib member.
message IEA332A.
System Programmer Response: Update the CON
system parameter in the CONSOLxx parmlib member if
necessary. IEA190I CONSOLxx: MASTER CONSOLE dev
WAS OFFLINE DURING IPL.
Explanation: The console with master authority
Detecting Module: IEAVNPA1
specified in the CONSOLxx parmlib member was offline
during initial program load (IPL). In the message text:
IEA188I CONSOLxx: NO MASTER CONSOLE
CONSOLxx
SPECIFIED.
Explanation: The CONSOLE statement in the
dev
CONSOLxx parmlib member did not specify a console
The specified console device.
with master authority.
System Action: The system issues message IEA191I
and continues processing. Message IEA191I identifies
CONSOLxx The parmlib member, with the suffix the master console.
xx.
System Action: The system selects a console with
master authority, issues message IEA191I, and
continues initialization. Message IEA191I identifies the
console that the system selected as the console with IEA191I CONSOLE dev (consname) text AS
master authority. MASTER CONSOLE
System Programmer Response: Before the next Explanation: text is one of the following:
system initialization, define a console with master DEFINED
authority in the CONSOLxx parmlib member. SELECTED
This message identifies the master console.
IEA189I CONSOLxx: dev IGNORED. text dev
Explanation: text is one of the following: The device number.
UNIT NOT SUPPORTED. consname
NO IODEVICE STATEMENT FOR dev. The console name.
The system does not support a specified console DEFINED

device. The CONSOLxx parmlib member defines the
console as the master console.

SELECTED
IEA193I CONSOLxx NOT USABLE. text
The system selected the console as the master
console. In this case, this message follows Explanation: text is one of the following:
message IEA188I, IEA189I, or IEA190I. NOT USABLE. UNABLE TO SELECT MASTER.
REASON=reason-code
NOT USABLE. NO VALID CONSOLE STATEMENTS
Operator Response: Enter a VARY command to alter FOUND.
the master console if the current master console is NOT USABLE. I/O ERROR OCCURRED.
unacceptable.
The system found an error while processing a
IEA192I CONSOLxx dev ALTERNATE CONSOLxx
DEFAULTED TO {consname|dev}. The parmlib member, with a suffix of xx.
REASON=reason-code
NOT USABLE. UNABLE TO SELECT MASTER.
Explanation: The system selected an alternate REASON=reason-code
console. The system was unable to select a console with
master authority.
reason-code
dev
The reason code, as follows:
The device number in the CONSOLxx parmlib
member. 1 No full capability console is defined in the
consname
The default console name. 2 No valid full capability console is defined in
the CONSOLxx parmlib member.
CONSOLxx
The parmlib member, with the suffix xx. 3 No online full capability console is defined
in the CONSOLxx parmlib member.
reason-code
The reason code. It is one of the following: NOT USABLE. NO VALID CONSOLE STATEMENTS
FOUND.
1 An alternate console was not specified in
No valid console statement is defined in the
the CONSOLxx parmlib member. In this
case, the system uses the master console
as the alternate console. NOT USABLE. I/O ERROR OCCURRED.
While the system was processing the CONSOLxx
2 The alternate console is not a valid
parmlib member, an error occurred.
console. The system uses the master
console as the alternate console. System Action: The system issues message IEA332A
to ask the operator to specify a new CON system
3 The alternate console has an operating
parameter.
mode that is not valid. For example, a
printer console is defined as the alternate System Programmer Response: Before the next
for a full capability console. system initialization, specify a valid CON parameter in
4 No alternate console is defined. The
system uses the master console. Source: Communications task (COMMTASK)
System Action: The system uses the specified Detecting Module: IEAVN613
console as the alternate console. The system continues
processing.
IEA194I CONSOLxx dev: HARDCOPY
Operator Response: Notify the system programmer. DEFAULTED TO SYSLOG.
REASON=reason-code
System Programmer Response: Specify an alternate
console with a CONSOLE statement in the CONSOLxx Explanation: The hard-copy console specified in the
parmlib member, if desired. CONSOLxx parmlib member is not valid.
Source: Communications task (COMMTASK) In the message text:
Detecting Module: IEAVG607, IEAVN613 CONSOLxx

dev CONSOLE STATEMENT IGNORED.
The device number. REASON=reason-code
The system could not identify the DEVNUM
reason-code
parameter on the CONSOLE statement. The
The reason code, which is one of the following:
reason code, reason-code, is one of the following:
1 The console is not a specified console.
1 The DEVNUM keyword is not the first
There may be no CONSOLE statement for
keyword following the CONSOLE
the console.
statement type.
2 The console is not valid.
2 The DEVNUM keyword value was not
3 The console is a display device. hexadecimal, did not fall in the range of
X'000' to X'FFF', or the value was not
System Action: The system assigns the device used SUBSYSTEM or SYSCONS.
for the system log as the default hard-copy log. The
system continues processing. 4 **This reason code was deleted as of
MVS/SP 4.2**
system initialization, ensure that the device number and 5 A CONSOLE statement named a console
the device type are the same in both the IODF and the that was already defined as a multiple
CONSOLE statement in the CONSOLxx parmlib console support (MCS) console.
member. Ensure that a hard-copy device is defined as a
99 CONSOLES DEFINED. STATEMENT IGNORED.
console in CONSOLxx.
The system issues this message for each
Source: Communications task (COMMTASK) CONSOLE statement it encounters beyond the 99
console definition maximum. The system ignores
Detecting Module: IEAVN615 consoles defined beyond the 99th console.
MISPLACED num STATEMENT IGNORED.
IEA195I CONSOLxx LINE lnnum; text A CONSOLE, HARDCOPY, DEFAULT, or INIT
Explanation: text is one of the following: statement was not the first statement in the
UNRECOGNIZED STATEMENT TYPE IGNORED. CONSOLxx member. The system ignores the
keywd IGNORED FOR SUBSYSTEM CONSOLE. incorrect statement.
CONSOLE STATEMENT IGNORED. num The statement number in CONSOLxx.
REASON=reason-code
99 CONSOLES DEFINED. STATEMENT IGNORED. SYSTEM ERROR mmmm-nnnn
MISPLACED num STATEMENT IGNORED. The system received an unexpected return code
SYSTEM ERROR mmmm-nnnn when parsing the CONSOLxx member.
keyword IGNORED FOR SYSTEM CONSOLE.
mmmm-nnnn
The range of statements in the erroneous
The system found an error on a statement in a CONSOLxx member.
keyword IGNORED FOR SYSTEM CONSOLE.
In the message text: The specified keyword is not valid for a system
console. Valid keywords are NAME, ROUTCODE,
CONSOLxx LEVEL, MONITOR, MSCOPE, CMDSYS, and UD.
System Action: If the message text is SYSTEM
lnnum ERROR mmmm-nnnn, the system stops processing the
The line number in CONSOLxx containing the CONSOLxx member and issues message IEA332A.
statement in error.
For all other errors, the system continues processing
UNRECOGNIZED STATEMENT TYPE IGNORED the valid statements in the CONSOLxx parmlib member.
The first non-blank or non-comment character string
on a statement was not a valid statement type. The Operator Response: If the message text is SYSTEM
system skips data until it finds a valid statement ERROR mmmm-nnnn, see the operator response for
type. message IEA332A. For other errors, notify the system
programmer.
keywd IGNORED FOR SUBSYSTEM CONSOLE.
The system ignores the keyword. The keyword is If the system issued this message during the IPL of a
not valid for a subsystem console. system into a sysplex, and no MVS consoles were
initialized on this system, the system console or other
keywd The keyword name in CONSOLxx. extended MCS consoles may be activated and used for
console functions until CONSOLxx members of
SYS1.PARMLIB have been corrected.

System Programmer Response: Check for incorrect SUBSYS
statements and parameters in the CONSOLxx parmlib
UNRECOGNIZED KEYWORD keywd IGNORED.
member. Correct these statements or parameters. If the
The system could not identify a keyword on the
error occurs again, search problem reporting data bases
CONSOLE statement.
for a fix for the problem. If no fix exists, contact the IBM
Support Center. In the message text:
If you are running a sysplex, the IEARELCN utility may keywd The unidentified keyword.
be used to remove one or more console definitions.
This will allow systems which subsequently join the keywd VALUE IGNORED. REASON=reason-code
sysplex to have a subset of consoles from their The system ignores an incorrect keyword value and
CONSOLxx member of SYS1.PARMLIB to be defined processes other valid data, except when the
and available. See OS/390 MVS Planning: Operations keywords MSGRT and AREA are specified.
and OS/390 MVS Initialization and Tuning Reference for keywd The incorrect keyword.
details on the 99-console limit for CONSOLxx.
reason-code The reason code, which is one of
Source: Communications task (COMMTASK) the following:
Detecting Module: IEAVN600, IEAVN601, IEAVN602, 1 The value does not
IEAVN611, IEAVN612, IEAVN615 conform to the syntax of
the keyword, the value is
IEA196I CONSOLxx stmt-type: text out of range for the
keyword, or the value is
Explanation: text is one of the following: out of range for the
UNRECOGNIZED KEYWORD keywd IGNORED. console’s device type.
keywd VALUE IGNORED. REASON=reason-code
IODEVICE STATEMENT UNIT APPLIED. 2 The FORMAT or XWTR
REASON=reason-code keyword values cannot
keywd IGNORED. REASON=reason-code be specified on a
INCONSISTENT keywd VALUE IGNORED. HARDCOPY statement
MISSING RIGHT PARENTHESIS ASSUMED. that does not have the
USE(xx) FORCED. REASON=reason-code system log (SYSLOG) as
CONSOLE NOT ACTIVATED. REASON=reason- HARDCOPY.
code 3 A CONSOLE statement
DUPLICATE SPECIFICATION IGNORED. defines a console with
DEVNUM ALREADY DEFINED. STATEMENT the same name as a
IGNORED. console that already
DUPLICATE keywd KEYWORD IGNORED. exists. The keyword
DUPLICATE keywd VALUE IGNORED. specified an attribute
UNBALANCED COMMENT FOUND. DATA value that was different
IGNORED. from the attribute value
PREMATURE END OF FILE DETECTED. of the existing console.
DEL(RD) FORCED. In a sysplex, the value
EXTRA keywd VALUES IGNORED. does not match the
DEFAULT: RMAX VALUE IGNORED. corresponding value of a
REASON=reason-code console with the same
name that is already
The system found an error while processing a defined to the sysplex.
CONSOLE statement in a CONSOLxx parmlib member. The system uses the
attribute of the existing
In the message text: console. To obtain the
current console attribute
CONSOLxx
values, issue the D C
command.
stmt-type
4 The specified keyword
value differs from the
cccccccc, specifying the console name.
current sysplex value.
dev, specifying the device number.
CONSOLE 5 The value of RMAX
DEFAULT exceeds the subsystem
HARDCOPY limit. The system sets
INIT

the value of RMAX to AUTH parameter that
the subsystem maximum was specified for a UNIT
limit. of PRT.
6 The console group 3 The AREA specification
definition as specified by was not valid because
the CNGRP parameter the total out-of-line
has been defined by AREA exceeded the
another system already screen size of the
active in the sysplex. device.
7 If the first system joining 4 An MSCOPE or
the sysplex is at CMDSYS keyword was
MVS/ESA SP 5.1 or specified while the
higher, and the value system was running in
specified for RMAX is cross-system coupling
less than 99, RMAX is facility (XCF)-local mode
set to 99. or as a single-system
sysplex (monoplex). The
8 The ROUTTIME value
MSCOPE or CMDSYS
cannot be specified on a
keyword is only valid in a
single system. A value of
multi-system sysplex
zero is used.
mode.
9 DEVNUM(SYSCONS)
INCONSISTENT keywd VALUE IGNORED.
was specified, but the
The value of keywd is not consistent with a
system console
previous value for that keyword.
hardware has not been
installed. For example, ROUTCODE(ALL,NONE) is
inconsistent because you cannot assign both all
IODEVICE STATEMENT UNIT APPLIED.
and none of the routing codes to the same console.
REASON=reason-code The system accepts the first value (ALL in this
The UNIT parameter was specified incorrectly. The case).
system ignores this parameter and uses the unit
type defined in the IODF for the specified device
number. keywd The ignored value.
reason-code MISSING RIGHT PARENTHESIS ASSUMED.
The reason code, which is one of the A right parenthesis is missing at the end of a
following: statement. The system assumes it is present.
1 The device type specified in the USE(xx) FORCED. REASON=reason-code
The system’s operating mode was changed to
keywd IGNORED. REASON=reason-code
maintain consistency with the AUTH or UNIT
The system rejected a parameter in the CONSOLxx
keyword.
member.
xx The new value of the USE
parameter, which controls the
keywd The rejected keyword. types of data sets that the system
can allocate on a tape or direct
reason-code The reason code, which is one of access storage device (DASD)
the following: volume.
1 The system ignores the reason-code The reason code, which is one of
keywords DEL, CON, the following:
SEG, RNUM, RTME,
AREA, PFKTAB, and 1 A statement contained
UTME. One or more of AUTH(MASTER) and
these keywords were USE(MS) or USE(SD),
specified for a UNIT of indicating that the
PRT. console had master
authority. Since a
2 The system ignores the console with master
authority must also have

full capability, the system beginning of a comment, but did not find an
changes the parameter asterisk slash (*/) to indicate the end of the
to USE(FC). comment before the end of the file.
2 An operating mode of full PREMATURE END OF FILE DETECTED.
capability or status The end of file was reached before the system
display was specified for completed parsing a statement.
a printer console. The
DEL(RD) FORCED.
system forces USE(MS).
The system changed the deletion mode to action
CONSOLE NOT ACTIVATED. RC=reason-code. messages retained “RD” from a deletion mode of
The system did not activate the console. either automatic message deletion “Y” or manual
message deletion “N”.
EXTRA keywd VALUES IGNORED.
reason-code The reason code, which is one of
The keyword had too many values specified. The
the following:
system ignores the extra values.
1 A console with the same
name already exists in
the sysplex and is keywd The ignored keyword.
currently active on
System Action: Depending on the message text, the
another system.
system does one of the following:
2 The console that is
keywd VALUE IGNORED. REASON=reason-code
logically associated with
The system ignores an incorrect keyword value and
this name was assigned
processes other valid data, except when the
to a system component.
keywords MSGRT and AREA are specified.
3 A console on a system
IODF IODEVICE STATEMENT UNIT APPLIED.
joining the sysplex has
the same name as the REASON=reason-code
failed master console. The system ignores this parameter and uses the
The joining system’s unit type defined in the IODF for the specified
console is not activated. device number.
DUPLICATE SPECIFICATION IGNORED. INCONSISTENT keywd VALUE IGNORED.
The system ignored a duplicate HARDCOPY, The system accepts the first value.
DEFAULT, or INIT statement.
MISSING RIGHT PARENTHESIS ASSUMED.
In the message text: The system assumes the parenthesis is present.
stmt-type USE(xx) FORCED. REASON=reason-code
The duplicate statement type. The system’s operating mode was changed to
maintain consistency with the AUTH or UNIT
DEVNUM ALREADY DEFINED. STATEMENT
keyword.
IGNORED.
The system ignored the device number because CONSOLE NOT ACTIVATED. RC=rc.
the same device number was specified in a The system does not activate the console.
previous CONSOLE statement.
DUPLICATE SPECIFICATION IGNORED.
DUPLICATE keywd KEYWORD IGNORED The system ignores the duplicate HARDCOPY,
Keyword keywd was specified more than once on DEFAULT, or INIT statement.
the CONSOLE statement.
DEVNUM ALREADY DEFINED. STATEMENT
IGNORED.
keywd The duplicate keyword. The system ignored the device number because
the same device number was specified in a
DUPLICATE keywd VALUE IGNORED.
previous CONSOLE statement.
A keyword on the statement has a duplicate value.
The system ignores the duplicate value. DUPLICATE keywd VALUE IGNORED.
The system ignores the duplicate value.
keywd The ignored keyword. In all cases, the system continues processing the
statements in the CONSOLxx parmlib member.
UNBALANCED COMMENT FOUND. DATA IGNORED
The system found a slash asterisk (/*) indicating the System Programmer Response: Before the next

system initialization, correct the statement(s) in the 4. After the system programmer corrects the member,
CONSOLxx member. reIPL the system.
Source: Communications task (COMMTASK) System Programmer Response: Validate that the
MSTRJCL parameter in the IEASYSxx parmlib member
Detecting Module: IEAVN600, IEAVN601, IEAVN602,
specifies a MSTJCLxx parmlib member or MSTJCLxx
IEAVN610, IEAVN611, IEAVN612, IEAVN615
CSECT in linklib that exists and is correct. If the
member does not exist or is not correct, create or
IEA200I memberxx - text correct the member. Then ask the operator to enter the
MSTRJCL system parameter again (in response to this
Explanation: During system initialization, the system message). Otherwise, ask the operator to enter the
could not use a data set member that was to contain an MSTRJCL parameter again (in response to this
alternate version of the master scheduler JCL. message).
In the message text: Source: Master scheduler
memberxx Detecting Module: IEAVNP13
The member of SYS1.LINKLIB or SYS1.PARMLIB
that the system could not use.
IEA208I func FUNCTION INOPERATIVE
text
A description of the error, which is one of the Explanation: During system initialization, the system
following: detected unrecoverable errors while initializing a
function. The function is now inoperative because of
MEMBER NOT FOUND these errors. This is probably an installation error.
The system could not find the MSTJCLxx
parmlib member or MSTJCLxx load module in In the message text:
linklib that is to contain the alternate version of
func
the master scheduler JCL.
The function. If func is LPA PACKING, the PAK
I/O ERROR DURING BLDL parameter was not specified, and NIP could not
An input/output error occurred when the read the default IEAPAK00 parmlib member.
system used the build list to find the specified
System Action: The system continues initialization. If
module.
NIP found an error in the PAK parameter, NIP will ask
I/O ERROR DURING READ the operator to specify it again or to cancel the request.
An input/output error occurred when the
Otherwise, the system usually issues another message
system was reading the data set that was to
to identify the errors.
contain the alternate version of the master
scheduler JCL. The system issues other messages about the problem.
UNEXPECTED END OF FILE Operator Response: See operator responses for
The system found an end-of-file (EOF) before accompanying messages.
the normal end of processing.
System Programmer Response: See system
INTERNAL CONVERSION ERROR programmer responses for accompanying messages.
An internal error occurred.
Source: The following:
UNEXPECTED FAILURE v Nucleus initialization program (NIP)
An internal error occurred. v Master scheduler
v Contents supervision
System Action: The system prompts the operator to
respecify the MSTRJCL system parameter. Detecting Module: IEAVNP13
Operator Response: Do the following:
1. Contact the system programmer. Provide the IEA211I OBTAIN FAILED FOR dsname DATA
message number and message text. SET
2. At the request of the system programmer, do one of Explanation: During system initialization, the system
the following in response to the prompt to respecify could not find a data set for one of the following
the MSTRJCL system parameter: reasons:
v Specify the MSTRJCL system parameter on the v The operator did not mount the volume containing the
console; then press ENTER. data set
v Press ENTER on the console. v The data set control block (DSCB) was not in the
3. If the system prompts for the MSTRJCL system volume table of contents (VTOC)
parameter again, ask the system programmer to v A permanent I/O error occurred
correct the specified member.

IEA214A DUPLICATE SYSRES volname FOUND
dsname ON DEVICE dev. VERIFY THAT
The specified data set name. CORRECT DEVICE WAS USED FOR
IPL. DUPLICATE DEVICE WILL REMAIN
System Action: System initialization continues. OFFLINE. REPLY ’CONT’ TO
Operator Response: Do the following: CONTINUE IPL
v If the volume that contains the data set is not Explanation: During system initialization, the system
mounted, mount it. found a direct access storage device (DASD) with
v If the volume is mounted, record the device number. volume label the same as the SYSRES device (IPL
Notify the system programmer. device).
System Programmer Response: Do the following: In the message text:

v List the VTOC of the volume that is supposed to volname
contain the data set. The duplicate volume serial name.
v If the data set is not on the volume, create the data dev
set. The device number of the device on which the
Source: DFSMSdfp duplicate volume serial name was found.
Detecting Module: IEAVNPM3 System Action: The system suspends nucleus

initialization. When the operator replies ’CONT’, the
system issues message IEA313I and marks as offline
IEA213A DUPLICATE VOLUME volname FOUND the device that has the same volume serial name as the
ON DEVICES dev1 AND dev2. REPLY SYSRES. Then the system continues initialization.
DEVICE NUMBER WHICH IS TO
REMAIN OFFLINE Operator Response: The operator should verify that
the correct device has been used to IPL the system as
Explanation: During system initialization, the system specified in the system control frame. If the wrong
found direct access storage devices (DASD) with the volume has been chosen, the operator must correct the
same volume label. load device in the system control frame and reIPL. If the
In the message text: correct device has been used for IPL, then the operator
should indicate that the IPL can continue.
volname
The name of the duplicate volume. Source: Input/output supervisor (IOS)
dev1 Detecting Module: IEAVNP02

The device number for the first device with a
duplicate volume label. IEA230E WTOR BUFFER SHORTAGE. 80% FULL
dev2 Explanation: The write to operator with reply (WTOR)
The device number for the second device with a message buffers are currently 80% full.
duplicate volume label.
System Action: The system suspends nucleus The system puts unauthorized tasks issuing WTOR
initialization. When the operator identifies which device macros in a wait state.
to put offline, the system issues message IEA313I and
marks that device offline. The other device will be Operator Response: Do one or more of the following:
online. Then the system continues initialization. v Reply to outstanding WTOR messages.
Operator Response: The operator must determine v Cancel any jobs that are currently issuing WTOR
which of the two devices having the same volume label messages.
name is correct. The operator can refer to the “required v Enter the CONTROL M,RLIM command to increase
volumes” list for your installation or make the the value of the WTOR buffer limit.
determination by some other means. When the
determination is made, reply to this message with the System Programmer Response: If the shortage
device number of the device that you want to place persists, increase the value of RLIM in the CONSOLxx
offline. parmlib member.
When specifying the device, you can optionally precede Source: Communications task (COMMTASK)
the device number with a slash (/). Detecting Module: IEAVMQWR

IEA231A SEVERE WTOR BUFFER SHORTAGE. IEA233I LOAD COMMAND IMSI VALUE OF C
100% FULL NOT VALID. DEFAULTED TO BLANK
Explanation: The outstanding write to operator with Explanation: When the LOAD command was entered,
reply (WTOR) messages have filled the buffer. the initialization message suppression indicator (IMSI)
was specified as a value other than a blank, A, P, or M.
System Action: The system puts tasks issuing WTOR
The system takes the default actions: It suppresses
macros in a wait state (if they did not specify a busy exit
informational messages and does not prompt for system
return) until the operator either reduces the number of
parameters.
outstanding WTORs or increases the number of WTOR
buffers. System Action: The system continues processing.
Operator Response: Enter a DISPLAY R,R command Source: Communications task (COMMTASK)
to see the accumulated WTOR messages. Do one of
the following:
IEA234I NO MCS CONSOLES DEFINED
v Reply to outstanding WTOR messages.
Explanation: No multiple console support (MCS)
v Cancel jobs that are currently issuing WTOR macros.
consoles are currently defined to the system.
v Enter the CONTROL M,RLIM command to increase
the number of WTOR buffers. System Action: System initialization continues.
Operator Response: Perform all operator functions on
Note: The RLIM value cannot be higher than the extended MCS consoles, subsystem allocatable
RMAX value (RMAX is the highest possible consoles, or the system console.
reply ID). If you need to increase RLIM higher
than RMAX, consider entering the CONTROL Source: Communications task (COMMTASK)
M,RMAX command to increase RMAX. To Detecting Module: IEAVN613
determine the current values of RLIM and
RMAX, issue the K M,REF command.
IEA235I RECURSIVE ABEND IN SYSCON
The value of RMAX controls the number of DOMLIST QUEUE PROCESSING.
digits in all reply IDs. For example, increasing QUEUEING SUSPENDED. DOMS TO
RMAX to 100 (or higher) causes all WTORs to SYSTEM CONSOLE MAY BE LOST.
have 3-digit reply IDs. This might affect Explanation: An error occurred when the system was
automation routines. Check with the system processing the system console delete operator message
programmer before increasing RMAX higher (DOM) queue.
than 99.
System Action: The system does not queue DOM
System Programmer Response: If the shortage requests to the system console. Some held messages
recurs, increase the value for RLIM or RMAX in the may not be deleted.
Detecting Module: IEAVMQWR reporting data bases for a fix for the problem. If no fix
IEA232I WTOR BUFFER SHORTAGE RELIEVED Source: Communications task (COMMTASK)
Explanation: In response to message IEA230E or Detecting Module: IEAVG719
IEA231A, this message indicates that the shortage of
buffer space for write to operator with reply (WTOR)
messages was relieved. IEA236I SYSCON DOMLIST QUEUE
PROCESSING RESUMED.
The system deletes messages IEA230E and IEA231A, Explanation: The system resumed processing of the
if they are outstanding. system console delete operator message (DOM) queue.
Source: Communications task (COMMTASK) System Action: The system continues processing.
Detecting Module: IEAVMQWR Source: Communications task (COMMTASK)
Detecting Module: IEAVG719

IEA238I SYSTEM CONSOLE [PRIORITY] IEA247I USING IEASYSxx FOR xx...x
OPERATOR INPUT PROCESSING
Explanation: For system initialization, the system is
ABENDED, PROCESSING
using the IEASYSxx parmlib member displayed in the
REESTABLISHED, LAST INPUT MAY
message text for system parameters.
BE LOST
If you are using multiple IEASYSxx parmlib members,
Explanation: The system deleted and reestablished
the system displays message IEA008I in place of this
the listener exit routine. Commands that the operator
message.
entered before the error occurred may be lost.
xx...x Contains the full product name, version,
PRIORITY
release, modification level and FMID. For
The system is not accepting operator input
example, in OS/390 Release 2, xx...x is
from the screen that accepts priority
01.02.00 JBB6602.
commands.
This field can be changed by the installation
using the SPZAP service to change the value
Operator Response: If the system did not process the in the CVTVERID field of the communication
previous command, enter the command again from the vector table (CVT).
system console.
System Action: System initialization continues.
Detecting Module: IEAVNPC4
IEA240I OBSOLETE BLDLF OR BLDL SYSTEM

IEA248I NUCLEUS MODULE modname IS
PARAMETER(S) IGNORED
LISTED IN IEANxdd1 AND IEANxdd2
Explanation: Either the operator or the IEASYSxx
Explanation: The system detected a duplicate module
parmlib member specified obsolete system parameters
entry appearing in two nucleus module lists (NML). This
BLDLF and/or BLDL.
may represent an error in a non-MVS product.
System Action: The system ignores BLDLF or BLDL
parameters.
modname
Operator Response: Do not specify BLDLF or BLDL
The duplicated module name
for this system.
IEANxdd1
System Programmer Response: Remove any BLDLF
The first nucleus module list
and BLDL specifications from the IEASYSxx parmlib
members. IEANxdd2
The second nucleus module list
Source: Contents supervision (CSV)
System Action: System initialization continues. The
system loads module modname as part of the system
nucleus.
IEA246I memname ID xx SELECTED
Explanation: For system initialization, the system
selected the parmlib member memname.
correct version of module modname resides in the
In the message text: SYS1.NUCLEUS data set. Delete the module name
from one of the NMLs listed in the message. Do not
memname
delete the name from both NMLs unless this module
The parmlib member selected for initial program
should not be loaded as part of the system nucleus.
load (IPL) processing. memname is one of the
following: Source: Initial program load (IPL)
v LOAD
v NUCLST
IEA250I [RER | RDE ] PARAMETER NOT VALID.
xx The identifying number of the parmlib member. DEFAULT OF ‘NO’ TAKEN.
System Action: System initialization continues. Explanation: One of the system parameters, RER or
RDE, was specified incorrectly in the IEASYSxx parmlib
member.

System Action: Processing continues. --or--
System Programmer Response: This is probably an
DEVSUP MTL SHARE IS IGNORED
installation error. Make sure that the RER or RDE
parameter is correct. Explanation: There are several variations of this
message. The first variation of this message is issued at
IPL time if any DEVSUPxx members exist to show
IEA251I {DEVSUPyy: | IGDDFPKG:} INVALID
which installation default applies. The message is
SYNTAX. MEMBER PROCESSING
informational, and requires no action or response.
TERMINATED ON LINE nnnn
In the message text of the first variation:
Explanation: The IGDDFPKG or the DEVSUPyy
parmlib member contains an incorrect keyword. V3 Is ISO/ANSI Version 3
In the message text: V4 Is ISO/ANSI Version 4
yy The member number Forced V3
ISO/ANSI Version 3 is being forced
keyword
The incorrect keyword. Forced V4
ISO/ANSI Version 4 is being forced
System Action: IPL continues.
value Is a numeric value
keyword parameter.
Note: For descriptions of forced and other DEVSUPxx
Source: DFSMSdfp parameters displayed in this message, see
OS/390 MVS Initialization and Tuning Reference.
Message DEVSUP MTLSHARE=YES SPECIFIED is
IEA252I {DEVSUPyy: | IGDDFPKG:} INVALID issued when MTLSHARE=YES is specified in the active
SYNTAX. MEMBER PROCESSING DEVSUPxx member of PARMLIB. This message can be
TERMINATED ON LINE nnnn issued on DFSMS 1.2, DFSMS 1.3, and DFSMS 1.4
systems.
Explanation: The DEVSUPyy or IGDDFPKG parmlib
member contains a syntax error.
Message DEVSUP MTL SHARE IS IGNORED is issued
In the message text: when MTLSHARE=YES is specified in the active
DEVSUPxx member of PARMLIB. This message can be
yy The number of the member being processed.
issued on OS/390 DFSMS Version 2 Release 10 and
nnnn The line number, relative to the beginning of higher systems.
the member, where the error was found.
Source: DFSMSdfp
syntax.
Source: DFSMSdfp
IEA254I CONSOLxx: RLIM EXCEEDS RMAX,
Detecting Module: IEAVNP16 RLIM IS SET TO RMAX
Explanation: The RLIM specified on the INIT
IEA253I DEVSUP 3480X RECORDING MODE statement exceeds the RMAX value on the DEFAULT
DEFAULT IS statement, if specified, or the default value of RMAX.
[NO-COMPACTION|COMPACTION]
System Action: The RLIM for the sysplex is set to the
DEVSUP ISO/ANSI TAPE LABEL
RMAX value.
VERSION DEFAULT IS (V3|V4|FORCED
V3|FORCED V4) Operator Response: Report the error to the system
DEVSUP TAPE OUTPUT DEFAULT programmer.
BLOCK SIZE LIMIT IS
[value|valueK|valueM|valueG;] Application Programmer Response: Adjust either
DEVSUP COPYSDB DEFAULT is the RMAX or RLIM value in the CONSOLxx member to
[YES|NO|INPUT| SMALL|LARGE] insure that RMAX >= RLIM.
--or--
DEVSUP MTLSHARE=YES SPECIFIED

sysname
IEA255I CONSOLE INITIALIZATION DELAYED.
The name of the system that was partitioned.
AWAITING CONSOLE PARTITION
CLEANUP OF SYSTEM sysname. System Action: The system continues processing.
Explanation: System initialization is delayed so Source: Communications task (COMMTASK)
another system in the sysplex can complete console
partition cleanup processing for the system specified in
the message text. IEA259I CLOCKxx: ENVIRONMENT NOT VALID
FOR SIMETRID
Explanation: The SIMETRID parameter was
sysname incorrectly specified in a CLOCKxx parmlib member.
The system that is undergoing console partition The SIMETRID parameter is only valid when the system
cleanup. is running as a virtual machine (VM) or processor
resource/systems manager (PR/SM) guest.
System Action: The system delays initialization for
five seconds while another system in the sysplex In the message text:
completes console partition cleanup processing. The
system may issue message IEA256I or IEA255I again. CLOCKxx
The parmlib member, with the suffix xx.
Operator Response: If the system issues message
IEA256I after this message, no action is necessary. If System Action: The system ignores all CLOCKxx
the system issues this message again, restart or parmlib members. The system issues message
partition from the sysplex any systems that are in a IEA906A.
stopped or disabled state. Operator Response: Reply to message IEA906A. If
Source: Communications task (COMMTASK) you press the enter button in reply to message
IEA906A, the system sets the following default values:
Detecting Module: IEAVN703 v No operator prompting for time-of-day (TOD) clock
initialization.
IEA256I CONSOLE INITIALIZATION RESUMED. v External Time Reference (ETR) synchronization
mode. ETR is the MVS generic name for the IBM
Explanation: The system resumed console
Sysplex Timer (9037) or equivalent.
initialization after another system in the sysplex
completed console partition cleanup. v ETRDELTA value of 10 seconds.
v Time zone constant obtained from ETR (or set to 0 if
System Action: The system issues message IEA255I
time zone cannot be obtained from ETR).
before issuing this message. System initialization
continues. System Programmer Response: Specify the correct
synchronization mode (ETRMODE) in the CLOCKxx
parmlib member.
If you specify ETRMODE NO, you cannot specify
ETRZONE YES.
IEA257I CONSOLE PARTITION CLEANUP IN
PROGRESS FOR SYSTEM sysname
Explanation: Console partition cleanup is in progress,
after a system in the sysplex was partitioned.
IEA260I THE CPC IS NOW OPERATING IN ETR
MODE.
sysname
Explanation: The central processing complex (CPC) is
The name of the system that was partitioned.
now synchronized with the External Time Reference
System Action: The system continues processing. (ETR). ETR is the MVS generic name for the IBM
System Action: Processing continues in ETR
synchronization mode.
IEA258I CONSOLE PARTITION CLEANUP
COMPLETE FOR SYSTEM sysname Source: Timer supervision
Explanation: Console partition cleanup completed Detecting Module: IEATEEIH
after a system in the sysplex was partitioned.

IEA261I NO ETR PORTS ARE USABLE. CPC
The system records the error in the logrec data set.
CONTINUES TO RUN IN LOCAL MODE.
Operator Response: Contact your
Explanation: There is no operational port from the
configuration/cabling personnel and have the
central processing complex (CPC) to the External Time
configuration error corrected. Provide the logrec data
Reference (ETR). ETR is the MVS generic name for the
set error records.
IBM Sysplex Timer (9037) or equivalent.
System Action: Processing continues in local
synchronization mode. The system records the error in Detecting Module: IEATPORT
the logrec data set.
Operator Response: Check the system console IEA264I PORT n TO ETR xx WAS DISABLED
associated with this processor. If you have already BECAUSE IT IS INCORRECTLY
contacted the IBM Support Center, no further action is CONNECTED.
required.
Explanation: The system disabled the specified port
Otherwise, contact 9037 hardware support. Note that to an External Time Reference (ETR). ETR is the MVS
the same event might occur on more than one of the generic name for the IBM Sysplex Timer (9037) or
processors in a sysplex. equivalent. The port was not connected to the same
ETR as the link from the remaining or initial port.
n The port number.
IEA262I ETR PORT n IS NOT OPERATIONAL. xx The ETR identifier. If a question mark appears,
there was no ETR identifier available from the
Explanation: The specified External Time Reference
port.
(ETR) port is not working. ETR is the MVS generic
name for the IBM Sysplex Timer (9037) or equivalent. System Action: The system continues processing.
The system records the error in the logrec data set.
Operator Response: Contact your
n The port number.
configuration/cabling personnel and have the
System Action: The system continues processing. configuration error corrected. Provide the logrec data
The system records the error in the logrec data set. set error records.
Operator Response: One of the following: Source: Timer supervision
v If an ETR is installed, check the system console Detecting Module: IEATPORT
associated with this processor. If you have already
contacted the IBM Support Center, no further action
is required. IEA265I UNABLE TO SYNC TOD CLOCKS TO
ETR. CPC CONTINUES IN LOCAL
Otherwise, contact 9037 hardware support. Note that
MODE.
the same event might occur on more than one of the
processors in a sysplex. Explanation: The central processing complex (CPC)
v If an ETR is not installed, ensure that the CLOCKxx could not synchronize with the External Time Reference
member of SYS.PARMLIB contains ETRMODE NO (ETR). This occurred for one of the following reasons:
and ETRZONE NO. v A hardware error occurred.
Source: Timer supervision v The time difference between the ETR and time-of-day
(TOD) clocks exceeded the ETRDELTA value in a
Detecting Module: IEATPORT CLOCKxx parmlib member.
ETR is the MVS generic name for the IBM Sysplex
IEA263I BOTH CPC PORTS ARE CONNECTED Timer (9037) or equivalent.
TO THE SAME SIDE OF ETR xx.
System Action: The system continues processing in
Explanation: Both central processing complex (CPC) local synchronization mode. The system records the
ports are connected to the same side of a coupled error in the logrec data set.
External Time Reference (ETR). ETR is the MVS
generic name for the IBM Sysplex Timer (9037) or Operator Response: Contact hardware support.
equivalent. Provide the logrec data set error records.
In the message text: Source: Timer supervision
xx The ETR identifier. Detecting Module: IEATESMR

name for the IBM Sysplex Timer (9037) or equivalent.
IEA266I CLOCKxx: {ETRMODE NO AND
ETRZONE YES|OPERATOR PROMPT In the message text:
AND SIMETRID} ARE MUTUALLY
EXCLUSIVE PARMS. n The port number.
Explanation: Both ETRMODE NO and ETRZONE System Action: The system disables the port.
YES, or OPERATOR PROMPT and SIMETRID, were Operator Response: Check the system console
specified in a CLOCKxx parmlib member. The timer associated with this processor. If you have already
synchronization mode must be External Time Reference contacted the IBM Support Center, no further action is
(ETR) (ETRMODE YES) to obtain the time zone value required.
from the ETR. ETR is the MVS generic name for the
IBM Sysplex Timer (9037) or equivalent. Otherwise, contact 9037 hardware support. Note that
In the message text: processors in a sysplex.
CLOCKxx Source: Timer supervision
System Action: The system ignores all CLOCKxx
parmlib members. The system issues message
IEA906A. IEA269I A CPC SIDE ID CHANGE FROM SIDE x
TO SIDE y HAS OCCURRED.
Operator Response: Reply to message IEA906A. If
you press the enter button in reply to message Explanation: The central processing complex (CPC)
IEA906A, the system sets the following default values: switched from using the External Time Reference (ETR)
ports on one side to the ports on another side. ETR is
v No operator prompting for time-of-day (TOD)
the MVS generic name for the IBM Sysplex Timer
initialization.
(9037) or equivalent.
v ETR synchronization mode.
v ETRDELTA value of 10 seconds.
v Time zone constant obtained from ETR (or set to 0 if x, y The side identifiers.
time zone cannot be obtained from ETR). System Action: Processing continues.
System Programmer Response: Specify the correct Source: Timer supervision
synchronization mode (ETRMODE) in the CLOCKxx
parmlib member. Detecting Module: IEATESMR
If you specify ETRMODE NO, you cannot specify

ETRZONE YES. IEA270I BOTH PORTS TO THE ETR HAVE
BEEN DISABLED. CPC CONTINUES IN
Source: Timer supervision LOCAL MODE.
Detecting Module: IEAVNP20 Explanation: The system disabled both ports to an
External Time Reference (ETR). ETR is the MVS
IEA267I ETR PORT n IS NOW AVAILABLE. generic name for the IBM Sysplex Timer (9037) or
equivalent.
Explanation: An External Time Reference (ETR) port
is now working. ETR is the MVS generic name for the System Action: Processing continues in local mode.
IBM Sysplex Timer (9037) or equivalent. Operator Response: Contact your
In the message text: configuration/cabling personnel and have the
configuration error corrected. Provide the logrec data
n The port number. set error records.
System Action: The system continues processing. Source: Timer supervision
Source: Timer supervision Detecting Module: IEATEEIH
IEA271I ETR TIME OFFSET CHANGES HAVE
IEA268I ETR PORT n IS DISABLED DUE TO AN OCCURRED.
EXCESSIVE NUMBER OF STATE Explanation: The system encountered a problem with
CHANGES. the External Time Reference (ETR). One of the
Explanation: The system detected an excessive following occurred:
number of availability state changes for an External v A leap second increment or decrement
Time Reference (ETR) port. ETR is the MVS generic

v The local time offset changed because of a change 079 Internal bus failed.
to or from local daylight savings time
080 Battery clock module failed.
081 Wrong card in card location XX.
Timer (9037) or equivalent.
082 Backup data invalid.
084 Identical Unit Addresses on the Base
cards.
Detecting Module: IEATTOC
089 Warning: Power-on diagnostic failure.
090 Unable to communicate with other
IEA272I ETR SERVICE IS REQUESTED.
unit.
REASON CODE=reason-code
093 Warning: configuration mismatch on
Explanation: The External Time Reference (ETR)
CLO links.
requires service. ETR is the MVS generic name for the
IBM Sysplex Timer (9037) or equivalent. 094 Warning: ETS configuration conflict.
In the message text: 098 Port card in slot 0 failed.
reason-code 099 Port card in slot 1 failed.
A reason code explaining the error follows. For 100 Port card in slot 2 failed.
more information about the reason codes, see
Maintenance Information for the 9037 Sysplex 101 Port card in slot 3 failed.
Timer. 102 Port card in slot 4 failed.
033 CLO Links cross-cabled. 103 Port card in slot 5 failed.
034 CLO Link A wrapped. 104 Port 0 failed.
035 CLO Link B wrapped. 105 Port 1 failed.
036 CLO links jumpered. 106 Port 2 failed.
037 Non-severe fan failure detected. 107 Port 3 failed.
040 Communication lost with console. 108 Port 4 failed.
041 Communication lost with standby 109 Port 5 failed.
console.
110 Port 6 failed.
044 The external time source is out of
tracking range. 111 Port 7 failed.
045 The external time source is not 112 Port 8 failed.

responding. 113 Port 9 failed.
046 The external time source reported a 114 Port 10 failed.
synchronization change.
115 Port 11 failed.
047 The external time source is not
synchronized. 116 Port 12 failed.
065 Base card failed. 117 Port 13 failed.
066 Port card in card location 2 failed. 118 Port 14 failed.
074 Control link card failed. 122 Port 18 failed.
075 Severe fan failure detected. 123 Port 19 failed.
076 Other 9037 unit failed. 124 Port 20 failed.
077 Control link A failed. 125 Port 21 failed.
078 Control link B failed. 126 Port 22 failed.

127 Port 23 failed. Source: Timer supervision
System Action: Processing continues. Detecting Module: IEATPSDH
Operator Response: The reason code indicates that
service is required. Check the system console IEA276I ETR ATTACHMENT DAMAGE WAS
associated with this processor. If the system has DETECTED.
contacted the IBM Support Center, no further action is
Explanation: The system found that the External Time
required.
Reference (ETR) attachment was damaged. ETR is the
Otherwise, contact 9037 hardware support. Note that MVS generic name for the IBM Sysplex Timer (9037) or
the same event might occur on more than one of the equivalent.
processors in a sysplex.
System Action: The system attempts to validate the
Source: Timer supervision damaged hardware. The system continues processing.
Detecting Module: IEATEEIH, IEATESMR Source: Timer supervision
Detecting Module: IEATEADH
IEA273I TOD CLOCKS DYNAMICALLY
ADVANCED TO MAINTAIN ETR
IEA277I TIMING FACILITY DAMAGE WAS
SYNCHRONISM.
DETECTED.
Explanation: After an External Time Reference (ETR)
Explanation: The system found that the time-of-day
synchronization check, the system synchronized the
(TOD) clock or the TOD synchronization facility was
time-of-day (TOD) clocks again. ETR is the MVS
damaged.
generic name for the IBM Sysplex Timer (9037) or
equivalent. System Action: The system attempts to validate the
damaged hardware. The system continues processing.
The channel path measurement facility (CPMF) stops or
enters a restartable error state. The system restarts the Source: Timer supervision
CPMF.
Detecting Module: IEATTFDH
Resynchronization may have created a gap in
timestamps. IEA278I THE LINK FROM PORT n TO THE ETR
IS TUNED.
Explanation: All link segments from the specified port
Detecting Module: IEATESCH to the External Time Reference (ETR) are tuned. A
tuned link is one for which transmission adjustments
have been made to account for the length of the link.
IEA274W THE ONLY ONLINE TOD CLOCK HAS
FAILED. In the message text:
Explanation: The last, or only, online time-of-day n The port number.
(TOD) clock failed.
System Action: The system enters nonrestartable
wait state X'A1E'. Source: Timer supervision
Operator Response: See the operator response for Detecting Module: IEATEEIH, IEATESGR
wait state X'A1E'.
System Programmer Response: See the system IEA279I ALL CLOCK RELATED SET
programmer response for wait state X'A1E'. COMMANDS ARE IGNORED WHEN IN
ETR MODE.
Explanation: The operator entered a SET command
Detecting Module: IEATESCH, IEATESC2, while the system was running in External Time
IEAVRTOD, IEATTSCH, IEATTFDH Reference (ETR) synchronization mode. ETR is the
MVS generic name for the IBM Sysplex Timer (9037) or
equivalent.
IEA275I PRIMARY SYNCHRONIZATION
FACILITY DAMAGE WAS DETECTED. System Action: The system ignores the SET
command.
Explanation: The system found that the primary
synchronization facility was damaged. Source: Timer supervision
System Action: The system attempts to validate the Detecting Module: IEA6503D
damaged hardware. The system continues processing.

IEA280I ETR DATA CANNOT BE ACCESSED.
[PORT STATUS CANNOT BE DETERMINED.]
CPC CONTINUES IN LOCAL MODE.
Explanation: One of the following occurred: [ETR DATA COULD NOT BE OBTAINED FOR CPC
v Timer supervision could not obtain the required data PORT 0]
words from the External Time Reference (ETR).
[ETR DATA COULD NOT BE OBTAINED FOR CPC
v The data words that timer supervision obtained from
PORT 1]
the ETR are not valid.
ETR is the MVS generic name for the IBM Sysplex Or
Timer (9037) or equivalent.
hh.mm.ss ETR STATUS ETR SIMULATION MODE,
System Action: Processing continues in local
SIMETRID=nn
synchronism mode.
Operator Response: Check the system console Both messages are in response to the DISPLAY ETR
associated with this processor. If you have already command.
contacted the IBM Support Center, no further action is
required. ETR is the MVS generic name for the IBM Sysplex
Otherwise, contact 9037 hardware support. Note that Timer (9037) or equivalent.
processors in a sysplex. In the first message text:
Source: Timer supervision hh.mm.ss

The hour (00-23), minute (00-59), and second
Detecting Module: IEATPORT (00-59) that the system issued this message.
mode
IEA281I ETR SYNC CHECK THRESHOLD HAS The current synchronization mode, as follows:
BEEN EXCEEDED. CPC CONTINUES IN
LOCAL MODE. ETR The system time-of-day (TOD) clocks are
synchronized to an External Time
Explanation: The number of External Time Reference Reference (ETR).
(ETR) synchronization checks exceeded the number
allowed by the system. ETR is the MVS generic name LOCAL
for the IBM Sysplex Timer (9037) or equivalent. The operator set the system TOD clocks.
The system TOD clocks are synchronized
System Action: Processing continues in local to a local oscillator.
synchronization mode.
<==
Provide the logrec data set error records. ==>
An arrow pointing to the active ETR port.
op The operational status of the ETR port, as follows:
Detecting Module: IEATESCH
OPERATIONAL
The port is working.
IEA282I text
NONOPERATIONAL
Explanation: Where text is one of the following The port is not working.
messages:
enb
hh.mm.ss ETR STATUS SYNCHRONIZATION One of the following:
MODE=mode CPC SIDE=n ENABLED
[CPC PORT 0 [<==] active [==>] CPC PORT 1 MVS has enabled the port.
op op
enb enb DISABLED
[CPC PORT 0 [<==] active [==>] CPC PORT 1 MVS has disabled the port.
op op etrnet
enb enb The ETR network identifier, in decimal.
ETR NET ID=etrnet ETR NET ID=etrnet
ETR PORT=etrport ETR PORT=etrport etrport
ETR ID=etrid ETR ID=etrid The ETR port number, in decimal.
[THE ETR FACILITY IS NOT INSTALLED.]

etrid v Enter the DISPLAY ETR command to display
The ETR identifier, in decimal. information about the port.
THE ETR FACILITY IS NOT INSTALLED Source: Timer supervision
There is no ETR installed on the system.
Detecting Module: IEATCMD
PORT STATUS CANNOT BE DETERMINED
The system cannot communicate with the ETR.
IEA285I THE LINK FROM PORT n TO THE ETR
IS NOT TUNED.
The second message text is displayed if SIMETRID=nn
in CLOCKxx is specified. In the second message text: Explanation: One or more link segments in the path
from the specified port to the External Time Reference
hh.mm.ss
(ETR) are not tuned. An untuned link has had no
transmission adjustments made to account for its length.
(00-59) that the system issued this message.
nn The simulated sysplex timer identifier ranging from
X'00' to X'1F'. n The port number.
System Action: The system continues processing. System Action: Processing continues normally, unless
a resynchronization of the time-of-day (TOD) clock is
required. If a resynchronization is required, the system
Detecting Module: IEATDISP will switch to local mode.
IEA283I ETR PORT n IS ENABLED.
Detecting Module: IEATEEIH, IEATESMR
Explanation: An External Time Reference (ETR) port
is enabled. ETR is the MVS generic name for the IBM
IEA287I IGDDFPKG {DFSMS OFFERING|DFSMS
FEATURE} IS n
Explanation: This message is issued during IPL to
n The port number. show which DFSMS/MVS offering or feature was
specified in the IGDDFPKG parmlib member.
n The offering or feature value specified. For
Detecting Module: IEATCMD information about the offering or feature value, refer
to the OS/390 MVS Initialization and Tuning
IEA284I ETR PORT n CANNOT BE ENABLED. Reference.
Explanation: The system cannot enable an External System Action: Processing continues.
Time Reference (ETR) port for one of the following Source: DFSMS/MVS
reasons:
v The installation requested local synchronization Detecting Module: IEAVNP16, IGDSMSPK
mode, meaning that ETR ports must be disabled.
v The ETR Facility is not installed. IEA297W LSQA IS EXHAUSTED IN A
v The system cannot communicate with the ETR. NON-MEMTERMABLE ADDRESS
SPACE
Timer (9037) or equivalent. Explanation: The system was unable to obtain
storage from LSQA which was needed to process an
SVC instruction. The system loaded a wait state
because it was unable to terminate the address space
n The port number. of the program which issued the SVC.
System Action: The system continues processing. System Action: The system enters a non-restartable
wait state and issues message IEA297W.
v Wait 30 seconds. Operator Response: Provide a stand-alone dump if
requested by the system programmer. ReIPL the
v Enter the SETETR command again.
system.
If the system issues message IEA284I again, the port
cannot be enabled. System Programmer Response: The problem may
be caused by a loop which causes LSQA to be
exhausted. If the source of the problem cannot be

determined, search problem reporting data bases for a System Action: If the missing member is a NIP
fix. If no fix exists, contact IBM support center. Provide module, the system enters a disabled wait state. If not,
the stand-alone dump. processing continues.
Source: Supervisor Control Operator Response: Record the address of the
device where the I/O error occurred and contact
hardware support.
IEA298I MAXCAD VALUE, xxxxxx, NOT VALID.
DEFAULT OF 25 USED Source: System initialization (IPL/NIP)
Explanation: During system initialization, an incorrect Detecting Module: IEAVNIPM, IEAVNP13,
MAXCAD value was specified in one of two ways: IEAVNPM4, IEAVNPM3
v In the IEASYSxx parmlib member
v In the operator response to message IEA101A
IEA301I mem {NOT FOUND|IS ALIAS} IN
dsname|PARMLIB
Explanation: The nucleus initialization program (NIP)
xxxxxx The incorrect MAXCAD value
detected an error condition.
System Action: Initialization continues with the default
MAXCAD value of 25. Note: This message can also be issued for a
non-existing member of SYS1.LINKLIB; check
Operator Response: ReIPL may be done to enter a
the parmlib member for any typographical errors.
correct value, but is not required.
System Programmer Response: Respecify the In the message text:
MAXCAD value by doing one of the following:
mem NOT FOUND IN dsname
v Ask the operator to enter a correct value in response NIP could not find member mem of data set
to message IEA101A. dsname.
v Correct the value specified in the IEASYSxx member.
mem IS ALIAS IN dsname
Source: Supervisor control Member mem is an alias, but the directory of data
set dsname also contains an alias entry for this
Detecting Module: IEAVNPO9
member.
dsname
IEA299I CONDITIONAL RIM mod NOT FOUND
If the parmlib concatenation consists of only one
IN SYS1.NUCLEUS. INITIALIZATION
data set, this is the name of that data set.
CONTINUES
PARMLIB
Explanation: During nucleus initialization, the nucleus
If the parmlib concatenation consists of more than
initialization program (NIP) could not find an optional
one data set, the member was not found in any of
resource initialization module (RIM) in the
the parmlib data sets.
SYS1.NUCLEUS data set.
In the message text: This message is often accompanied by messages
IEA324I and IEA336A in this sequence:
mod The missing optional RIM
IEA301I IEASYS00 NOT FOUND IN SYS1.PARMLIB
System Action: Nucleus initialization continues. This message occurs even if the operator specified
Source: System initialization (IPL/NIP) IEASYSxx parmlib members other than IEASYS00.
IEA324I SYSP INPUT TERMINATED IN IEASYS00
Detecting Module: IEAVNIPM IEA336A RESPECIFY PARAMETERS OR PRESS
ENTER TO CANCEL
IEA300I I/O ERROR DURING BLDL FOR mem IN This combination occurs when NIP cannot find the
dsname primary IEASYSxx member, IEASYS00, while the
system is processing the operator’s response to
Explanation: An uncorrectable I/O error prevents the
message IEA101A.
nucleus initialization program (NIP) from reading a
directory entry for a member in a data set. This is System Action: If the missing member is a required
probably a hardware error. NIP module, the system enters a disabled wait state. If
not, processing continues.
If message IEA301I is accompanied by messages
mem The member name
IEA324I and IEA336A, the system resumes processing
dsname after the operator replies to message IEA336A.
The data set containing the member

Operator Response: When message IEA301I is
IEA304W SYSTEM WAIT STATE - CODE cde
followed by IEA324I and IEA336A in the sequence
DURING mod INITIALIZATION
shown above, reply to IEA336A by specifying the SYSP
system parameter so that the system can access Explanation: The nucleus initialization program (NIP)
IEASYSxx parmlib members. encountered an error and the system enters a wait
state.
System Programmer Response: If the error occurred
for the link list or LPA, determine what library the In the message text:
member is in. Determine if the library needs to be
cde The last three digits identify the wait state
added to the concatenated list. Reinitialize the system.
code. See OS/390 MVS System Codes for a
If the error occurred in SYS1.PARMLIB, add the missing description of the wait state code and for a
member to the data set. description of the order of the bits.
If the member was in the data set, search problem mod Identifies the NIP module that was in control
reporting data bases for a fix for the problem. If no fix when the system entered the wait state.
exists, contact the IBM Support Center. Note that the
System Action: The system enters a wait state.
IBM Support Center might request a stand-alone dump
if the problem has recurred. Operator Response: See the operator response for
the wait state issued.
Detecting Module: IEAVNIPM, IEAVNP13,
programmer response for the wait state issued.
IEAVNPC5, IEAVNPM4
IEA303W ABEND cde REASON rsn DURING Detecting Module: IEAVNIPM
INITIALIZATION UNDER RIM dsname
[modname NOT FOUND]
IEA305A INVALID REPLY FORMAT - RESPECIFY
Explanation: During nucleus initialization, a system
function abended. Explanation: During nucleus initialization, the last
reply entered through the console was not in correct
In the message text, format.
cde A hexadecimal abend code System Action: The system ignores the reply just
entered and waits for the reply to be respecified.
rsn The reason code from register 15 that was
specified on the REASON keyword of the Operator Response: Reenter the reply correctly.
ABEND macro. Ensure that it is not longer than 80 characters.
dsname Source: Contents supervision (CSV)
The resource initialization (RIM) data set name
under which processing was occurring. Detecting Module: IEAVNWTO
modname
The name of the module that abended. IEA306I dev,chp,I/O ERROR,cm, stat,[sens],[ser]
System Action: The system enters disabled wait state Explanation: The nucleus initialization program (NIP)
X'040'. issued an I/O request to a device on a channel path.
The I/O request included a command that resulted in an
Operator Response: See the operator response for unsuccessful I/O completion.
wait state X'040'.
programmer response for the abend code in the dev
message text. The device number
Problem Determination: See the problem chp

determination information for the abend code in the The channel path identifier
message text. cm The I/O command that resulted in an unsuccessful
For additional problem determination information, see I/O completion
wait state X'040'. stat
Source: System initialization (IPL/NIP) The channel status word (CSW) status bytes
Detecting Module: IEAVNIPM sens

The first two bytes of sense data

The sense data appears only for errors involving a an I/O error also occurred while trying to read
unit check status. the resulting sense data.
ser The volume serial number of a direct access
Note: If this situation occurs, no second line of
storage device (DASD) involved
message IEA307I is displayed.
The volume serial number appears only for DASD.
NO SENSE DATA
System Action: If the I/O request is critical to the This text appears for non-unit check errors.
system initialization process, the system issues Since the error was not a unit check, then no
message IEA304W and enters a disabled wait state. sense data exists.
Otherwise, processing continues.
Note: If this situation occurs, no second line of
If the device is a console, the system also issues
message IEA307I is displayed.
message IEA193I, which indicates the CONSOLxx
member that defines the console where the error System Action: The system continues processing.
occurred.
Operator Response: Notify the system programmer of
Operator Response: This is probably a hardware the I/O error that occurred while the system was reading
error. If the system issues message IEA304W, see the the volume label for the specified device.
operator response for that message and the associated
wait state. System Programmer Response: Contact hardware
support.
If the system does not issue message IEA304A, restart
the system and then contact hardware support. Provide Source: Input/output supervisor (IOS)
the message text. Detecting Module: IOSVVOLV
Source: Nucleus initialization program (NIP)
Detecting Module: IEAVNPM3 IEA308I MAXIMUM NUMBER OF PARMLIBS
EXCEEDED
IEA307I dev,chp, I/O ERROR READING VOLUME Explanation: More than 10 PARMLIB statements were
LABEL, cmd,stat,text. [sense-data] specified in LOADxx.
Explanation: A program issued a request to read a System Action: IPL continues.

volume label on a device. The I/O request included a System Programmer Response: Ensure that a
command that caused an unsuccessful I/O completion. maximum of 10 PARMLIB statements are specified in
In the message text: LOADxx.
dev Source: Initial program load (IPL)

The device number. Detecting Module: IPXI50PS
chp
The channel path identifier (CHPID) IEA309I PARMLIB DATA SET IGNORED: dsname
cmd volser
The I/O command that caused the error. Explanation: A data set in the PARMLIB
stat concatenation is ignored because more than 10 (the
The subchannel status word (SCSW) status bytes. maximum allowed) data sets have been specified.
text In the message text:

A variable length text string that is one of the dsname
following: The name of the data set that will not be used.
SENSE FOLLOWS volser The volume where dsname resides.
This text appears for unit check errors in which
the resulting sense data could be successfully System Action: IPL continues.
read. If this text is displayed, the sense data is System Programmer Response: Ensure that a
also displayed. maximum of 10 PARMLIB statements are specified in
sense-data LOADxx.
Shows up to 32 bytes of the resulting Source: Initial program load (IPL)
sense data in the second line.
Detecting Module: IPXI50PS
INVALID SENSE DATA
This text appears for unit check errors in which

IEA310A INVALID REPLY
Operator Response: If the device is not the device
| Explanation: During nucleus initialization, the last
you wanted to dismount, do the following:
| reply to message IEA120A, IEA213A, or IEA214A did
| not contain the required information. v ReIPL the system with the correct device in ready
status.
| System Action: The system ignores the reply. The
v If the device is not required during system
| system issues message IEA120A, IEA213A, or
initialization, enter a VARY command to establish the
| IEA214A again.
volume status at the end of system initialization.
Operator Response: Enter the reply correctly.
Detecting Module: IEAVNPM3, IEAVNP02, IEA314I CONFLICTING VOLUME ON dev
IEAVNP03, ILRASRIM
found a device with an incorrect device type while
IEA311I UNLABELED DASD ON dev. UNIT PUT attempting to mount a volume. In the message text:
OFFLINE.
dev
Explanation: The direct access storage device The device number.
(DASD) mounted on a device is not formatted correctly.
System Action: One of the following:
In the message text: 1. If the volume on the device is not permanently
dev resident, the system marks the device not ready.
The device number. The system issues message IEA315A.
2. If the volume on the device is permanently resident,
System Action: The system marks the device offline.
but the volume to be mounted is for an optional data
Operator Response: Notify the system programmer. set, the system issues message IEA317A.
System Programmer Response: Ensure that the 3. If the volume to be mounted is for a required data
volume mounted on the device was properly initialized set, and the volume on the device is permanently
by the ICKDSF program. resident, the system enters wait state X'039'.
Source: Input/output supervisor (IOS) Operator Response: See the operator response for
message IEA315A, IEA317A, or wait state code X'039'.
Detecting Module: IOSVVOLV
Source: DFSMSdfp
IEA312I dev OFFLINE Detecting Module: IEAVNPM3
Explanation: Because a direct access storage device

(DASD) was formatted incorrectly, the system placed IEA315A M devname,[NL], dsname
the device offline. In the message text: Explanation: During system initialization, the system
dev required one of the following:
The device number. v An unlabeled tape for a SYS1.DUMPnn data set
System Action: The system continues processing v The volume containing a data set to be mounted on a
without the device. device
Operator Response: Notify the system programmer. In the message text:

System Programmer Response: Ensure that the devname
system properly initialized the volume mounted on the The name of the device on which the volume
device. should be mounted.
The name of the data set in the volume to be
IEA313I DEVICE dev DISMOUNTED mounted.
Explanation: During nucleus initialization, the system System Action: The system waits for a volume to be
dismounted a device in response to message IEA212A. mounted on the specified device.
In the message text: Operator Response: Mount one of the following:

v The direct access volume containing the specified
dev data set
The device number.

v An unlabeled scratch tape 4. In logically partitioned (LPAR) mode, use the IOPD
frame option A5 and the device number to
Source: DFSMSdfp
determine if the device is supported and in which
Detecting Module: IEAVNPM3 logical partition.
5. Check if the control unit is powered and enabled to
IEA316A D dev[,ser] the interface. If the control unit interface path is
switched through a 3814, check the switching unit
Explanation: During system initialization, the system settings.
found that a volume was mounted on a device other 6. For 3380 device level selection (DLS) or device
than the device requested. level selection extended (DLSE) devices, check if
If the device is a tape unit, the volume is write-protected the device enable/disable switch is in the ENABLE
or contains a standard IBM tape label. position.
7. If you replied to message IOS120A with the ‘CONT’
command, reIPL the system.
dev The device number. 8. Verify that the devices defined in the IODF are
ser The serial number of the volume that was online.
mounted incorrectly. Source: DFSMSdfp
System Action: The system issues message Detecting Module: IEAVNPM3
IEA315A.
Operator Response: Do the following: IEA318I UNIT UNACCEPTABLE
v Demount the specified volume.
v Ensure that the proper volume is mounted on the found that the unit specified in the reply to message
specified device. IEA317A contained one of the following:
v Ensure that the volume is initialized with the proper v An unacceptable device type for the data set volume
volume serial number. to be mounted
Source: DFSMSdfp v A volume that could not be demounted
Detecting Module: IEAVNPM3 System Action: The system rejects the unit
specification. The system issues message IEA317A
again.
IEA317A SPECIFY UNIT FOR dataset ON volser
[OR CANCEL] Operator Response: See the operator response for
message IEA317A, specifying an alternate unit. Ensure
that the alternate unit:
could not find a data set on a mounted volume. In the
message text: v Is the proper device type for the volume to be
mounted
dataset The name of the data set that the nucleus
v Does not contain a required system data set
initialization program (NIP) could not find.
v Is demountable
volser The serial number of the volume where the
data set should reside. Source: DFSMSdfp
[OR CANCEL] Detecting Module: IEAVNPM3

The operator may cancel a request to mount
the volume. IEA319I dsname NOT FOUND ON volser
System Action: The system waits for the operator to Explanation: During system initialization, the system
reply. If the operator replies R 00,xxx, the system may could not find a data set on a volume. In the message
issue messages IEA318I and IEA317A. text:
Operator Response: Do the following: dsname
1. Enter the command REPLY 00,dev. The data set name.
2. Find the channel path identifier (CHPID) defined for volser The volume serial number.
the device using the I/O problem determination
(IOPD) frame option A5. System Action: If the data set is logrec,
SYS1.SVCLIB, SYS1.PARMLIB, or SYS1.LINKLIB, the
3. Check the CHPID availability for the current physical
system enters a disabled wait state. Otherwise, the
partition using the channel configuration (CHNCFA)
frame.
Operator Response: Remove the incorrect volume

and mount the correct one. If the action does not
IEA323I OPI INVALID IN mem
correct the problem, notify the system programmer.
found an incorrect OPI parameter in a IEASYSxx
v List the table of contents of the volume that should parmlib member. The OPI parameter must be specified
contain the data set. as either OPI=YES or OPI=NO.
v If the data set is not on the volume, create the data
set.
v Tell the operator to restart the system. mem The IEASYSxx parmlib member containing an
incorrect OPI parameter
Source: DFSMSdfp
System Action: The system ends the input from the
Detecting Module: IEAVNPM3 member and issues message IEA324I. The system
issues message IEA336A to prompt the operator to
IEA321I INVALID PARAMETER SYNTAX - prm - respecify the SYSP parameter.
text Operator Response: Respond to message IEA336A
Explanation: text is one of the following: by specifying the SYSP parameter again or canceling
INVALID OPI KEYWORD the use of it for this IPL. Parameters interpreted up to
IMPROPER DELIMITER the point of the error remain in effect.
UNBALANCED PARENS System Programmer Response: Make sure that the
INVALID CONTINUATION IEASYSxx parmlib member correctly specifies the SYSP
UNDEFINED KEYWORD parameter. Ensure that the SYSP list of system
parameters is specified correctly.
The specified parameter is not valid.
In the message text: Detecting Module: IEAVNP03
prm
The specified parameter. IEA324I SYSP INPUT TERMINATED IN mem
INVALID OPI KEYWORD Explanation: During system initialization, the nucleus
The OPI parameter is specified incorrectly in the initialization program (NIP) ended input from an
IEASYSxx parmlib member. It must be either IEASYSxx parmlib member because of an error.
OPI=YES or OPI=NO.
IMPROPER DELIMITER
The parameter is followed by an incorrect delimiter. mem The IEASYSxx parmlib member
Parameters must be separated by a comma or a System Action: NIP issues a message before
blank. message IEA324I to explain the error. After message
UNBALANCED PARENS IEA324I, the system then issues message IEA336A to
The parameter included a different number of right prompt the operator to respecify the parameter input
and left parentheses. that was truncated. Parameters specified before the
error remain in effect.
INVALID CONTINUATION
The parameter continued across more than two Operator Response: Notify the system programmer.
successive lines of text. See the operator response for the message preceding
IEA324I.
UNDEFINED KEYWORD
The parameter is not valid for message IEA101A System Programmer Response: See the system
under operating system/virtual storage 2 (OS/VS2). programmer response for the message preceding
IEA324I.
a reply by issuing message IEA336A, IEA324I, Source: System initialization (IPL/NIP)
IEA332A, or IEA906A. Detecting Module: IEAVNP03
the accompanying message. IEA325I IEASYSxx PARAMETER LIST
Source: Virtual storage management (VSM) Explanation: During system initialization, the operator
Detecting Module: IEAVNP08 requested a listing of the SYSP list of parameters when
responding to message IEA101A. This message is the
header for the listing of the IEASYSxx parmlib member.

xx The identifier for the IEASYS parmlib member. Operator Response: Notify the system programmer.
Obtain a stand-alone dump.
System Action: The system lists the parameters and
continues processing. System Programmer Response: Do one of the
following:
v Reduce the total number of extents in the data sets
Detecting Module: IEAVNP03 in the parmlib member.
v Reduce the number of data sets specified for
IEA326I LOCATE FAILED FOR dsname inclusion in the LNKLST.
Explanation: dsname is one of the following: To reopen the LNKLST concatenation, have the
SYS1.DUMP operator reIPL the system.
SYS1.CSSLIB
SYS1.LINKLIB Do not try to reduce the number of extents by
SYS1.LPALIB compression while the data sets are opened as part of
SYS1.DSSVM LNKLST. Data sets must not be compressed while they
SYS1.MIGLIB are in the LNKLST concatenation.
During system initialization, the nucleus initialization If the problem recurs, search problem reporting data
program (NIP) could not find a data set in the system bases for a fix for the problem. If no fix exists, contact
catalog. the IBM Support Center. Provide the stand-alone dump.
System Action: If the data set is SYS1.LINKLIB or Source: Contents supervision (CSV)
SYS1.CSSLIB, the system enters wait state X'00A'. For
Detecting Module: IEAVNPE5, CSVLLCRE
other data sets, the system provides additional
diagnostic information in message IEA208I, IEA351I,
IEA354I, or IEA355A. IEA329I RETRYABLE ERROR. RECENT
COMMANDS MAY NEED TO BE
REPEATED
Explanation: The current command to be processed
programmer response for accompanying messages or
is not valid. The system recovered from a previous
for wait state X'00A' if the missing data set name is
abend.
SYS1.LINKLIB or SYS1.CSSLIB.
System Action: The system does not process the
command and all subsequent commands in the queue.
Detecting Module: IEAVNPC5, IEAVNPE5
Operator Response: You may have to retry one or
more of the following commands:
IEA328E LNKLSTxx INPUT TRUNCATED AT v CONTROL C,A
dsname v CONTROL C,E
v CONTROL C,I
Explanation: Too many data set names were specified
v CONTROL M
for inclusion in the LNKLST concatenation.
If the problem persists, contact the system programmer.
xx The identifier for the LNKLST or PROG parmlib
member that defined the LNKLST
concatenation.
dsname
The name of the last data set in the parmlib Detecting Module: IEAVC700
member
System Action: The system did one of the following: IEA330A CONTINUE prm PARM
v Accumulated data set names for the LNKLST until its Explanation: This message permits the operator to
work area filled up. continue entering information related to a parameter.
v Concatenated as many of the specified data sets to
SYS1.LINKLIB as can be described in the data
extent block (DEB) for the LNKLST. The work area or prm The parameter name.
the DEB were filled up in processing data set
dsname. The system ignores the data set names System Action: The system prompts for the operator
after dsname. for a reply.

Operator Response: Continue entering information
IEA334A dsname(mem) HAS AN INVALID
related to the parameter.
RECORD LENGTH - SPECIFY EOB TO
Source: Communications task (COMMTASK) CONTINUE
Detecting Module: IEAVNP03 Explanation: The nucleus initialization program (NIP)

read at least one record from a parmlib member. The
member has a physical record length (block size) that is
IEA331I LINK LIBRARY CONCATENATION not a multiple of 80. The logical record length (LRECL)
SYS1.LINKLIB dsname dsname ... for parmlib members must be 80. The physical record
Explanation: The message lists the data sets that the length must be a multiple of LRECL.
system concatenated to SYS1.LINKLIB. The system In the message text:
issues this message if the list (L) keyword is specified in
the LNK system parameter. dsname
The data set containing the member
mem The member that has the incorrect physical
dsname record length
The data set name of a data set concatenated
to the SYS1.LINKLIB data set. System Action: Initialization processing waits for your
response.
Source: Contents supervision (CSV) To continue the IPL, specify EOB (press ENTER). This
Detecting Module: IEAVNP03 action requests processing of member mem, even
though it has an incorrect record length.
IEA332A SPECIFY prm System Programmer Response: Make sure that the
physical record length of records in mem is a multiple of
Explanation: The nucleus initialization program (NIP) 80.
found that a function defined by a parameter in an
IEASYSxx parmlib member was omitted. Source: System initialization (IPL/NIP)
In the message text: Detecting Module: IEAVNPM4
prm The parameter name of a required or optional

function. If OR CANCEL appears in the IEA335I dsname MODULE mod IN mem LIST IS
message text, the function is optional. text
System Action: To allow you to respond, the system Explanation: text is one of the following:
issues message IEA101A, then waits for your response.
NOT EXECUTABLE
Operator Response: Contact the system programmer. ALIAS OF ALIAS
If the function is required, reply to message IEA101A as NOT AUTHORIZED
follows: LIST IS A DUPLICATE
If, for example, prm is CON:
R 0,CON=xx The system could not process a module a for data set
R 0,CON=(xx) in a parmlib member.
R 0,CON=(xx,L)
If, for example, prm is LOGREC:
R 0,LOGREC=dsname
dsname
If the function is optional (OR CANCEL appears in the The name of the data set.
message text), press the ENTER key on the console to
bypass the parameter and continue system initialization NOT EXECUTABLE
without the optional function. The system cannot process module mod.
System Programmer Response: See the system ALIAS OF ALIAS

programmer response for message IEA101A. The directory entry for the module name mod
specifies that it is an alias. However, the
Source: System initialization (IPL/NIP) module name that it is an alias of is also an
Detecting Module: IEAVNP03 alias. This is not valid.
NOT AUTHORIZED
Module name mod is not in a library listed in
the authorized program facility (APF) list.

LIST IS A DUPLICATE
IEA338A INVALID prm PARM - RESPECIFY parm
Module mod duplicates a module name that
OR PRESS ENTER TO CANCEL
already appears in member mem.
Explanation: One of the system parameters specified
mod The name of the module. If the member is
during system initialization was incorrect.
specified as IOSDLPAL, then the module is a
device support module that should reside in In the message text:
SYS1.LINKLIB.
prm The incorrect parameter
mem The parmlib member that names module mod.
System Action: The system ignores the module name parameter and prompts the operator for a reply.
mod and continues processing. If ALIAS OF ALIAS
Operator Response: Respecify the parameter or
appears in the message text, the system has loaded the
press ENTER to cancel the use of the parameter for
module with the original alias, but the module cannot be
this IPL.
accessed using the incorrect alias name.
an installation error. Ensure that the module with the Detecting Module: IEAVNP03
incorrect alias is link edited properly.
Source: Contents supervision (CSV) IEA339A dsname HAS AN INVALID BLOCKSIZE -
PRESS ENTER TO CONTINUE
Explanation: The block size of the parmlib data set
dsname is not a multiple of 80. The logical record length
IEA336A RESPECIFY PARAMETERS OR PRESS
(LRECL) of a parmlib data set must be 80, and the
ENTER TO CANCEL
block size must be a multiple of LRECL.
Explanation: During nucleus initialization, one of the
System Action: Initialization processing waits for your
following contained an incorrect parameter:
response.
v The operator response to message IEA101A
Operator Response: Notify the system programmer of
v The system parameters defined in an active
this message. To continue the IPL, press ENTER. This
IEASYSxx parmlib member
action requests processing of the concatenated parmlib
System Action: The system accepts all parameters data set with the incorrect block size
specified before the parameter in error. The system
prompts the operator to respecify the incorrect
LRECL of the data sets in the concatenated parmlib is
parameter or cancel the use of the parameter for this
80 and that the block size is a multiple of 80.
IPL.
This message may be preceded by explanatory
messages IEA301I and IEA324I. Detecting Module: IEAVNP03
Operator Response: Do one of the following:
v Enter a reply specifying only the corrected parameter IEA340I REAL OR VIRTUAL STORAGE NOT
and subsequent parameters. AVAILABLE FOR func
v Cancel further input by pressing ENTER. In this case, Explanation: The nucleus initialization program (NIP)
the parameters accepted by the system remain in could not obtain storage for the function indicated.
effect.
Any parameter may be respecified in this response.
func The function is one of the following:
System Programmer Response: If the parameters v BLDL/BLDLF
were correct or if the problem persists, and a search of
the problem reporting data bases shows no fix, contact v FIX
the IBM Support Center. v IOSDLPAL
Source: System initialization (IPL/NIP) v LPA Device Support Modules
v MLPA
v PFT
System Action: If func is not a necessary system
function, the system will continue processing. If,
however, func is a necessary system function, the
system enters disabled wait state X'038' or X'03A'.

Functions and system actions are as follows:
IEA343D NUCLEUS OVERLAPS PLPA, RE-IPL
func System Action OR REPLY ‘GO’ FOR COLD START
PFT Wait state X'038' Explanation: The nucleus overlaps into the previous
system queue area/extended system queue area
LPA Device (SQA/ESQA) area. This causes an overlap into the area
Wait state X'03A' required by pageable link pack area (PLPA) or extended
Support PLPA (EPLPA). This might have been caused by one of
the following:
Modules
v The size of the nucleus increased.
BLDL/BLDLF v The amount of central storage increased; this
Respecification offered by prompt message increase results in an increase in the size of the
MLPA The system issues message IEA353I nucleus.
FIX The system issues message IEA353I PLPA and EPLPA must be in the same virtual storage
location as the previous IPL for warm starts to proceed.
Note: PFT is not a system parameter. Therefore, the quick or warm start cannot proceed. The
operator must reIPL or allow the IPL to change to a cold
Operator Response: Report this message to the start.
system programmer.
System Action: This message requests a response
Application Programmer Response: If message from the operator. If the operator replies GO, the system
IEA956I or message IEA968I was issued previously, issues message IEA929I (CLPA FORCED), changes the
probable hardware error. Central storage might have a IPL to a cold start, and continues paging initialization.
defective frame located at a fairly low address If Otherwise, the operator must reIPL.
message IEA956I or message IEA968I was not issued
previously, this is probably an installation error. Make Operator Response: Determine if the correct nucleus
sure that sufficient storage is available for NIP was specified at IPL. If not, specify the correct nucleus
processing. Reduce the number or the size of your and reIPL. If the correct nucleus was specified at IPL,
optional system facilities, such as the fixed link pack notify the system programmer.
area (FLPA) or the fixed BLDL list. System Programmer Response: If the problem
System Programmer Response: If the error recurs cannot be resolved, search problem reporting data
and the program is not in error, search problem bases for a fix for the problem. If no fix exists, contact
reporting data bases for a fix for the problem. If no fix the IBM Support Center.
exists, contact the IBM Support Center. Source: Auxiliary storage manager (ASM)
Source: Contents supervision (CSV) Detecting Module: ILRASRIM
IEA345A dsname NOT USED (text) - PRESS
IEA341A RESPECIFY prm PARM OR PRESS ENTER TO CONTINUE
ENTER Explanation: The system cannot use the specified
Explanation: A system parameter specified during parmlib data set.
initialization was incorrect. Previous messages might In the message text:
diagnose the specific error in the parameter
specification. dsname
The data set name.
text
prm The incorrect system parameter. A variable length text string that is one of the
System Action: The system prompts the operator for following:
a reply. OPEN FAILED
Operator Response: Enter the parameter correctly or The system cannot open data set dsname.
press ENTER. If you press ENTER, any system defaults volser NOT FOUND
for the parameter are used. The system cannot locate or cannot mount
If prm is DUMP, ensure that TA was not specified in volume volser.
the SYS1.PARMLIB dump command.
NOT CATALOGED
Source: Nucleus initialization program (NIP) The LOADxx parmlib statement for data set
Detecting Module: IEAVNP08 dsname was not cataloged in the master
catalog.

System Action: IPL processing waits for the operator System Action: The system prints the list and
to press ENTER. processing continues.
Operator Response: Notify the system programmer. Source: Contents supervision (CSV)
To continue the IPL without data set dsname, press
Detecting Module: IEAVNP05, IEAVNPC5
ENTER.
System Programmer Response: Depends on text:
IEA351I dsname REQUIRED FOR mem
OPEN FAILED
Ensure that dsname either resides on the volume
cannot find the data set dsname. The data set is
specified on the LOADxx parmlib statement or is
required for member mem in the parmlib.
cataloged in the master catalog. IPL the system
again to use the data set. In the message text:
volser NOT FOUND dsname
Ensure that the volume exists and it is mounted. The specified data set name.
IPL the system again to use the data set.
mem The specified member name.
NOT CATALOGED
Ensure that the data set dsname is cataloged on System Action: The system continues processing.
the master catalog or specify a volume for it on the Operator Response: This is probably an installation
LOADxx parmlib statement. IPL the system again to error. Report the problem to the system programmer
use the data set. and reply in the format specified for message IEA101A
Source: Nucleus initialization program (NIP) as requested by the system programmer, or cancel the
job.
Detecting Module: IEAVNPOP
IEA347A SPECIFY MASTER CATALOG reporting data bases for a fix for the problem. If no fix
PARAMETER exists, contact the IBM Support Center.
Explanation: During system initialization, the system Source: Contents supervision (CSV)
issues this message asking the operator to specify
whether the normal master catalog or an alternate Detecting Module: IEAVNP05
master catalog is to be used by the system.
System Action: The system waits for the operator to IEA352I LIST mem FOR prm INVALID text
reply. The system generates the name of the MODNAME mod
SYS1.NUCLEUS parmlib member that will be used to Explanation: text is one of the following:
find the master catalog.
Operator Response: Do one of the following: INCORRECT LIBNAME FORMAT
EXCEED MAX BLDL ENTRIES
v Reply nn: To select the alternate master catalog,
INCORRECT VOLID FIELD
SYSCATLGnn. nn is the two character suffix of
EXCEED APF TABLE STORAGE
SYSCATLG. Member SYSCATLGnn will now be used
MODNAME mod FOR dsname
to find the master catalog in SYS1.NUCLEUS.
INCORRECT LIBNAME FORMAT FOR dsname
v Press enter: To use the default member of MODULE LIST NOT CLOSED FOR dsname
SYS1.NUCLEUS, SYSCATLG to find the master INVALID KEYWORD FOUND
catalog. INVALID DELIMITER
Source: DFSMSdfp MIXED SYNTAX ENCOUNTERED
Detecting Module: IEAVNP11 The parmlib member specified for a parameter is

incorrect.
IEA350I mem MODULE LIST
Explanation: This is a header message for the library
listing requested by the operator. The modules specified mem
in the parmlib member are printed following this The name of the parmlib member.
message. prm
In the message text: The parameter.
mem The specified parmlib member name. MODNAME mod

mod identifies the name of the incorrect module
specified.

INCORRECT LIBNAME FORMAT prm The specified parameter. If prm is CLPA, a link
The parmlib list did not properly define a module pack area (LPA) cold start has failed.
source library.
mod The module that was to be loaded when the
EXCEED MAX BLDL ENTRIES error was detected.
The parmlib list contained too many module names;
System Action: If this initial program load (IPL) was
BLDL has more than X'7FFF' names.
not a cold start, the system continues processing.
INCORRECT VOLID FIELD Modules specified before mod are added to the LPA. If
The parmlib list contained volid’s that were prm is CLPA, the system is placed in wait state X'03A'.
specified in the wrong format, or possibly not
Operator Response: This is probably an installation
specified at all.
error. Report this message to the system programmer.
EXCEED APF TABLE STORAGE
System Programmer Response: Ensure that there is
The parmlib list IEAAPFxx contains entries with a
adequate storage for the prm function being attempted.
character count exceeding the maximum storage
Respond as indicated for the wait state code if it occurs.
allocated for the authorized program facility (APF)
table. If the error recurs and the program is not in error,
MODNAME mod FOR dsname
The parmlib member specified an incorrect module
Center.
name, mod for data set dsname.
INCORRECT LIBNAME FORMAT FOR dsname
The parmlib member specified an incorrect module Detecting Module: IEAVNP05, IEAVNPC5
source library for data set dsname.
MODULE LIST NOT CLOSED FOR dsname IEA354I [CLPA|MLPA|BLDL|IOSDLPAL] FAILED
The parmlib member is missing the module list - text
closing delimiter for data set dsname.
Explanation: The system link pack area (LPA) or the
INVALID KEYWORD FOUND pageable build directory entry list (BLDL) table could not
The parmlib member contains an invalid keyword. be created. text indicates the reason:
INVALID DELIMITER LPALIB UNAVAILABLE
The parmlib member contains an incorrect keyword The SYS1.LPALIB data set is not defined in the
delimiter. catalog or the data set could not be opened. The
reason for the failure is given in the previous
MIXED SYNTAX ENCOUNTERED
message.
The parmlib member specified libraries with
keyword and non-keyword syntaxes. LPALIB EMPTY
The SYS1.LPALIB data set did not contain any load
System Action: For the texts ″INCORRECT LIBNAME
modules.
FORMAT″, INCORRECT VOLID FIELD″, and ″EXCEED
APF TABLE STORAGE″, the system continues. For all STORAGE UNAVAILABLE
others, the system prompts the operator to respecify the Virtual storage is too small to contain all the
parameter or cancel. modules in SYS1.LPALIB. The number of modules
in SYS1.LPALIB must be reduced if cold start is to
be successful.
error. Respond to the prompt message and report this
message to the system programmer. I/O ERROR
An I/O error occurred when the nucleus initialization
program (NIP) attempted to read a record from the
SYS1.LPALIB directory.
reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. PGOUT ERROR
An error occurred during the processing of the
PGSER macro. The PGSER macro tried to page
Detecting Module: IEAVNPA5, IEAVNPC5, IEAVNP05 out the modified link pack area (MLPA) area,
pageable link pack area (PLPA) area, or the
pageable BLDL list.
IEA353I prm INPUT TERMINATED AT mod
NON-EXECUTABLE MODS
Explanation: The definition of the parameter failed for
Non-processible modules were found on
lack of storage as indicated by the preceding message.
SYS1.LPALIB.

wait state X'03A'. If any modules were successfully module mod into the LPA, but mod cannot be accessed
loaded into the LPA, the system issues message by the alias aliasname.
IEA353I.
error. Notify the system programmer.
IEA357I ERRORS IN ‘IEAPAKxx’ LIST
exists, contact the IBM Support Center. text - sysact
Source: Contents supervision (CSV) Explanation: text is one of the following:

v MODULE mod HAS INVALID RMODE
v DELIMITER FOLLOWING mod INVALID
v NAME FOLLOWING mod IMPROPER
IEA355A RESPECIFY prm [OR CANCEL]
v I/O ERROR FOLLOWING mod
detected an error a parameter. sysact is one of the following:
v MODULE IGNORED
v SKIPPING TO NEXT GROUP
prm The parameter name. v LIST TERMINATED
OR CANCEL
CANCEL is a reply option. During initial program load (IPL), the system detected
one or more errors while processing the link pack area
System Action: The system issues message (LPA) packing list member, IEAPAKxx, of the parmlib.
IEA101A.
Operator Response: Contact the system programmer, In the message text:
then reply in the format specified by message IEA101A.
MODULE mod HAS INVALID RMODE
If CANCEL is a reply option, you may press the enter
The system found that the residence mode
button on the console to bypass the parameter.
(RMODE) for module mod is different from the
System Programmer Response: See the system RMODE for the group containing the module. The
programmer response for message IEA101A. RMODE for a group is the RMODE of the first
module in the group.
DELIMITER FOLLOWING mod INVALID
Detecting Module: IEAVNPA1 The left parenthesis before a group of module
names is missing, or the right parenthesis after a
IEA356I ALIAS name OF MODULE mod group is missing, or a blank is not preceded by a
IGNORED left parenthesis or comma. mod is the last valid
module name before the error. mod is ***START if
Explanation: During the initial program load (IPL) of no valid module names preceded the error.
the link pack area (LPA), the entry for aliasname in a
library directory (the library is SYS1.LPALIB, NAME FOLLOWING mod IMPROPER
SYS1.LINKLIB, or SYS1.SVCLIB) specifies that it is the A module name in the list has more than eight
alias of the specified module. However, mod is not in characters. mod is the last valid module name
that library directory or is itself an alias. A message before the error. mod is ***START if no valid
accompanying message IEA356I names which library. module names preceded the error.
In the message text: mod INVALID

Module mod is not in the directory of SYS1.LPALIB,
name The specified alias name. is the name of an alias (not a module), or is
mod The specified module. specified more than once in the LPA packing list.
System Action: If a cold start is in progress and the I/O ERROR FOLLOWING mod
system is creating the pageable link pack area (PLPA) An I/O error occurred while the system was reading
this message follows message IEA301I. If the system is the list. mod is the last valid module name before
loading the modified link pack area (MLPA) or the fixed the I/O error. if no valid module names preceded
link pack area (FLPA) this message follows message the error.
IEA335I. The system ignores the entry for aliasname sysact
during the IPL of the LPA. The system may have loaded sysact is one of the following:

MODULE IGNORED v Immediate action messages (with descriptor codes 1
Module mod is ignored. The system continues and 2)
processing the list. v Non-critical eventual action messages (with descriptor
SKIPPING TO NEXT GROUP code 3)
The system scans the list from the error to the v Critical eventual action messages (with descriptor
next right parenthesis, which ends the group. code 11)
The modules in the group before the error are v Write to operator with reply messages (WTORs)
processed as the only modules in the group.
Processing then continues with the start of the System Action: The system continues to retain
next group. immediate action and eventual action messages.
LIST TERMINATED Operator Response: Enter the DISPLAY R command

The modules in the group before the error are to display information about all outstanding immediate
processed as the only modules in the group. action and eventual action messages. Delete messages
The system then ends processing of the LPA by:
packing list and continues processing as v Responding to messages requesting an action.
though it had reached the end of the LPA v Entering the CONTROL C command. See the
packing list normally. OS/390 MVS System Commands book for the syntax
of the CONTROL C command.
System Action: See sysact in the description above
for the system action. Note: When enough messages are deleted so that the
Source: Contents supervision (CSV) buffer area is less than 75% full, the system
issues message IEA361I and deletes message
Detecting Module: IEAVNPC5 IEA359E.
IEA358A LPALIB MODULE mod IS
NON-EXECUTABLE. PRESS ENTER TO Detecting Module: IEAVMQWR
CONTINUE, OR RE-IPL THE SYSTEM
Explanation: Module mod on SYS1.LPALIB (or a IEA360A SEVERE BUFFER SHORTAGE FOR
library specified in the LPALSTxx parmlib member) is RETAINED ACTION MESSAGES - 100%
marked non-executable and cannot be loaded into the FULL
system link pack area (LPA). Explanation: The action message retention facility
In the message text: (AMRF) is active, and the buffer area for the following
messages is full:
mod The specified module.
v Immediate action messages (with descriptor codes 1
System Action: The system prompts the operator for and 2)
a reply. If the reply is ENTER, the system continues v Non-critical eventual action messages (with descriptor
processing. The system does not place the code 3)
non-executable module into the LPA.
v Critical eventual action messages (with descriptor
Operator Response: Report this message to the code 11)
system programmer. Either press ENTER to have the v Write to operator with reply messages (WTORs)
IPL continue or reIPL after the system programmer has
fixed the error. Note that pressing ENTER to continue System Action: The system no longer retains
the IPL means that the specified module will not be non-critical eventual action messages. The system
placed into the LPA. issues message IEA360A if console message buffers
(WQEs) begin to back up.
System Programmer Response: Replace the
non-executable module with processible versions. When the WQE buffer shortage is no longer critical, the
system deletes message IEA405E and IEA404A and
Source: Contents supervision (CSV) issues message IEA361I. The system retains new
Detecting Module: IEAVNPC5 immediate action and critical eventual action messages
and keeps them in the common service area (CSA).
IEA359E BUFFER SHORTAGE FOR RETAINED Operator Response: Enter the DISPLAY R command
ACTION MESSAGES - 80% FULL to display the details of all outstanding immediate action
and eventual action messages. Delete messages by:
Explanation: The action message retention facility v Responding to messages requesting an action
(AMRF) is active, and 80% of the buffer area for the v Entering the CONTROL C command. See the
following messages is full: OS/390 MVS System Commands book for the syntax
of the CONTROL C command.

If a shortage still exists, you might want to deactivate
IEA363I mod NOT FOUND IN LPA
the AMRF by entering the CONTROL M,AMRF=N
command. Explanation: The nucleus initialization program (NIP)
could not find the module in the link pack area (LPA).
Detecting Module: IEAVMQWR
mod The specified module.
IEA361I BUFFER SHORTAGE RELIEVED FOR System Action: Except during special NIP processing,
RETAINED ACTION MESSAGES the system indicates which function was made
inoperative by issuing message IEA208I, and then it
Explanation: The number of retained action messages
continues processing. If the system cannot continue
was reduced so that the buffer is now less than 75%
processing without the module, the system enters wait
full. This message is preceded by message IEA359E or
state X'03B'.
both IEA359E and IEA360A, which indicated the extent
of the buffer shortage. Operator Response: This is probably an installation
error. Notify the system programmer.
The system deletes messages IEA359E and IEA360A. Application Programmer Response: Ensure that the
missing routine is in the LPA. If necessary, add the
module to the SYS1.LPALIB and have the operator run
Detecting Module: IEAVMQWR a cold start.
The module must be defined in the parmlib list
IEA362E BUFFER EXTENSION FAILED FOR referenced by the modified link pack area (MLPA) or
RETAINED ACTION MESSAGES FIX option, if either of these options is used.
Explanation: The action message retention facility System Programmer Response: If the error recurs
(AMRF) is active, the system could not obtain additional and the program is not in error, search problem
buffers, and the buffer area for the following messages reporting data bases for a fix for the problem. If no fix
is full: exists, contact the IBM Support Center.
v Immediate action messages (with descriptor codes 1 Source: Contents supervision (CSV)
and 2)
Detecting Module: IEAVNPS5, IEAVNP05, IEAVNP07
v Non-critical eventual action messages (with descriptor
code 3)
v Critical eventual action messages (with descriptor IEA364E {AMRF [RESTART]|MPF} FAILED,
code 11) INACTIVE {RETAINED MESSAGES
DELETED|MPF TABLE DELETED}.
System Action: The system retains any new
immediate action messages and critical eventual action Explanation: One of the following appears in the
messages in the common service area (CSA). The message text:
system no longer retains non-critical eventual action AMRF FAILED, INACTIVE - RETAINED MESSAGES
messages. DELETED
The system issues messages IEA405E and IEA404A if The action message retention facility (AMRF) failed
console message buffers (WQE) start to back up. The because of a system error.
system deletes message IEA362E if the buffer shortage MPF FAILED, INACTIVE - MPF TABLE DELETED
is relieved. The message processing facility (MPF) failed
Operator Response: Enter a DISPLAY R command to because of a system error. The error occurred in
display the details of all outstanding immediate action the MPF table scan routine.
and eventual action messages. If a shortage still exists, System Action: Depending on the message text, one
you may want to deactivate the AMRF by entering the of the following:
CONTROL M,AMRF=N command. If the problem
persists, contact the system programmer. AMRF FAILED, INACTIVE - RETAINED MESSAGES
DELETED
System Programmer Response: Check for a The system no longer retains action messages if
shortage of storage in the master scheduler address the facility was active before the failure occurred.
space. Messages that were retained previously are no
Source: Communications task (COMMTASK) longer available.
Detecting Module: IEAVMQWR MPF FAILED, INACTIVE - MPF TABLE DELETED

The system deletes the message table. The MPF is
inactive.

Operator Response: If the AMRF failed and you want
IEA367A MULTIPLE CONSOLE SUPPORT
to restart it, enter the CONTROL M,AMRF=Y command.
INOPERATIVE ERROR CODE = xxxx
If the MPF failed and you want to reactivate it, enter the REPLY WITH ANY CHARACTER TO
SET MPF=xx command, where xx is the last two digits CONTINUE WITHOUT MULTIPLE
of an MPFLSTxx parmlib member. CONSOLE SUPPORT
If either problem recurs, contact the system Explanation: Because of an error, the communications
programmer. task (COMMTASK) failed.
System Programmer Response: Search problem In the message text:

xxxx The reason code, which is one of the following:
8001 The system could not establish a
recovery routine.
8002 The system could not attach a needed
routine.
IEA365E COMMAND SCHEDULER RESTART
8003 The error occurred during a POST.
FAILED,
8004 The error occurred during a POST.
ABEND RECURSION
8005 The error occurred during an update
THE FOLLOWING
to the command address space table.
COMMANDS ARE INOPERATIVE:
D C D C,K D PFK D R REPLY 8006 The error occurred during an operator
D OPDATA ROUTE TRACE MCS LOGON request to activate an extended
MCS LOGOFF multiple console support (MCS)
console class.
Explanation: Command processing failed. The system
tried to restart it, but the restart also failed. 8007 The error occurred during a POST.
This message follows message IEE481I, which 8008 The error occurred when the system
identifies the system abend code of the original error. tried to issue a Supervisor Call (SVC).
System Action: The system continues other Fccc An error occurred; the system issued
processing. abend code ccc.
Operator Response: If necessary, reIPL the system to System Action: The system prompts the operator for
return the system to full processing. a reply.
System Programmer Response: See the system Operator Response: Do one of the following:
programmer response for the abend identified in v To continue processing with MCS, reIPL the system
message IEE481I. with MCS.
Source: Communications task (COMMTASK) v To request that processing continue without MCS,
reply with any character. Note that in this case, all
3270 consoles will be non-functional, but programs
that are processing that do not need to interact with a
IEA366W MULTIPLE CONSOLE SUPPORT console operator will be able to continue.
INOPERATIVE-WAIT STATE 201 - REIPL
System Programmer Response: If Fccc appears, see
Explanation: Because of a failure, multiple console the system programmer response for the abend code
support (MCS) is not working. ccc.
System Action: System initialization stops. The Source: Communications task (COMMTASK)
system writes an SVC dump and enters wait state
X'201'.
IEA368I INVALID RECORD IN memname. FIRST
wait state X'201.'.
17 BYTES ARE xxxxxxxxxxxxxxxxx
programmer response for wait state X'201.'.
found an incorrect record in the memname parmlib
Source: Communications task (COMMTASK) member. The system cannot process the keyword.
Detecting Module: IEAVN700 In the message text:
memname The parmlib member

containing an
IEA372I module EXCLUDED FROM NUCLEUS
incorrect record.
memname is one of Explanation: An EXCLUDE statement in the
the following: NUCLSTxx parmlib member specified that module
v LOADxx modname be excluded from the nucleus.
v NUCLSTxx
xxxxxxxxxxxxxxxxx The first seventeen
module The module excluded from the nucleus.
characters in the
incorrect record. System Action: System initialization continues.
System Action: The system ignores the incorrect Source: Initial program load (IPL)
record and system initialization continues.
Provide the parmlib member name, memname, and the
incorrect record. IEA376I VIODSN PARAMETER IS ’IGNORE’. NO
VIO JOURNALING
System Programmer Response: Correct the incorrect
record in parmlib member memname. Explanation: The value of the VIODSN parameter in
the IEASYSxx parmlib member used for this IPL is
If the record is correct, search problem reporting data ’IGNORE’ or null, which means that no VIO journaling
bases for a fix for the problem. If no fix exists, contact will take place.
System Action: IPL continues. The system rejects
Source: Initial program load (IPL) journaling requests for VIO data sets.
Detecting Module: IEAIPL50 Operator Response: If VIO journaling is necessary,
re-IPL at direction of system programmer, specifying a
VIO journaling data set name for the VIODSN
IEA370I MASTER CATALOG SELECTED IS
parameter.
MASTER CATALOG name
System Programmer Response: Ensure that VIO
Explanation: The system issues this message during
journaling is not required. If it is needed, specify
system initialization to display the name of the catalog
VIODSN in IEASYSxx.
selected as the master catalog. The master catalog is
from the SYSCATxx member of SYS1.NUCLEUS. The Source: Auxiliary Storage Manager (ASM)
operator specified the name of the catalog for use as
the master catalog in response to system message Detecting Module: ILRASRM2
IEA347A.
System Action: Processing continues IEA377D REPLY VIO JOURNALING DATA SET
NAME OR ’IGNORE’
Source: Nucleus initialization program (NIP)
Explanation: This message allows the operator to
respecify the VIO journaling data set name or indicate
IEA371I data-set ON DEVICE nnnn SELECTED that journaling of VIO data sets is not necessary.
FOR IPL PARAMETERS
Explanation: During system initialization, the system reply. If the operator replies with a new data set name,
selected data set dataset containing the IPL the system processes the data set.
parameters.
If the operator replies IGNORE, or gives a null reply,
In the message text: message IEA378I is displayed and the IPL continues.
The system rejects journaling requests for VIO data
data-set
sets.
The data set containing the IPL parameters.
The data set is one of the following: Operator Response: Enter one of the following:
v SYS1.PARMLIB
v SYSn.IPLPARM dsname
nnnn The device number where the IPL parameter DSN=dsname

data set was located. VIODSN=dsname
System Action: System initialization continues with To specify a VIO journaling data set name.
the IPL parameters found in data set data-set. IGNORE
Source: System initialization (IPL) null
Detecting Module: IEAIPL50 To specify that VIO journaling is not necessary.

If VIO journaling is necessary, reIPL at the direction of v In the IEASYSxx parmlib member
the system programmer, specifying the VIODSN v In the operator response to message IEA101A
parameter.
System Programmer Response: Ensure that VIO
journaling is not required. If it is needed, specify value The incorrect NSYSLX value, which is less
VIODSN in IEASYSxx. than 10 or greater than 512
Source: Auxiliary Storage Manager (ASM) number The default value for NSYSLX. This is currently
165.
Detecting Module: ILRASRM2
System Action: Initialization continues with the default
NSYSLX value of 165.
IEA378I REPLY TO IEA377D IS ’IGNORE’ OR
NULL. NO VIO JOURNALING Operator Response: In response to message
IEA101A, enter a new NSYSLX value specified by the
Explanation: The reply to the message IEA377D
system programmer. If message IEA101A does not
indicates that system initialization should continue
appear, reIPL to enter a correct value.
without VIO initialization.
System Programmer Response: Respecify the
System Action: The IPL continues. The system will
number of system linkage indexes by doing one of the
reject journaling requests for VIO data sets.
following:
Operator Response: If VIO journaling is necessary, v Ask the operator to enter a correct value in response
re-IPL at the direction of the system programmer. to message IEA101A.
System Programmer Response: Ensure that VIO v Correct the value specified in the IEASYSxx member.
journaling is not required. If it is needed, specify
Source: Supervisor control
VIODSN in IEASYSxx.
Detecting Module: IEAVNPO9
Source: Auxiliary Storage Manager (ASM)
IEA401I SDUMP NOT SCHEDULED FOR
REMOTE DUMP. INCIDENT
IEA379I VIODSN=dsname,DATA SET NOT TOKEN:intoken REASON - reason
CATALOGED - reg15
Explanation: The system was unable to write an SVC
Explanation: The data set name specified in the dump for another system in a sysplex.
VIODSN parameter in IEASYSxx could not be located in
the system catalog.
intoken The incident token for the dump. The token
The message text, reg15 is the value returned from
contains the name of the sysplex, the name of
SVC 26 in Register 15.
the system that originated the dump request,
System Action: Message IEA377D is issued. If the and the date and time of the request.
operator replies with a new data set name, the system
reason One of the following:
processes the data set. If the operator replies IGNORE,
or gives a null reply, message IEA378I is displayed and DUMP=NO WAS SET AT IPL OR INDICATED
the IPL continues. The system will reject journaling BY CHNGDUMP
requests for VIO data sets. The installation indicated that no SVC
dumps are to be written.
Operator Response: Reply to message 377D with
VIO journaling data set name or IGNORE. NO SRBS COULD BE SCHEDULED TO
START THE DUMP
System Programmer Response: If VIO journaling is
A system error occurred.
required, supply the VIO journaling data set name in the
VIODSN parameter of IEASYSxx before the next IPL. SVC DUMP ABNORMALLY TERMINATED
Source: Auxiliary Storage Manager (ASM)
A STATUS STOP SRBS CONDITION WAS
DETECTED
IEA400I NSYSLX VALUE, value, NOT VALID,
NO STORAGE AVAILABLE
DEFAULT OF number USED
The system could not acquire the storage
Explanation: During system initialization, the number needed to build the dump request; no
of system linkage indexes, NSYSLX, was incorrectly dump was written.
specified in one of two ways:

UNKNOWN
IEA404A SEVERE WTO BUFFER SHORTAGE -
100% FULL
System Action: The system continues processing but
does not write the requested SVC dump.
messages is at the limit value specified in the MLIM
This message is sent to the console on which the parameter of a CONSOLxx parmlib member.
DUMP command was entered or, if the dump was
System Action: The system puts non-privileged jobs
requested by another system in the sysplex but not by a
issuing messages in a wait state (if they did not specify
DUMP command, to console ID 0.
a busy exit return) until the number of WTOs is reduced
System Programmer Response: Determine why the below the buffer limit.
system could not write an SVC dump requested by
Operator Response: Enter the DISPLAY CONSOLES
another system in the sysplex. If the problem cannot be
command. If the system has accumulated a large
corrected, search problem reporting data bases for a fix
number of WTO messages, do one or more of the
following:
Center.
v Enter the CONTROL Q command to reroute the
Source: SVC dump messages.
Detecting Module: IEAVTSIT – Enter the CONTROL E,D command if CONTROL
Q does not reroute the messages.
IEA402A REPLY ID PROCESSING ERROR. text ATTENTION: Messages already queued to a

display area will not be deleted by a CONTROL
Explanation: Where text can be one of the following: Q. Enter CONTROL E,D to erase these messages
v XCF RETURN CODE xxxxxxxx, REASON CODE if the CONTROL Q command does not relieve the
yyyyyyyy shortage.
During WTOR or DOM processing, an unexpected v Enter the CONTROL S command to delete a
return code was received from XCF. The XCF return specified number of messages.
and reason code are displayed in hexadecimal. v Enter the CONTROL M,MLIM command to increase
v ATTEMPT TO OBTAIN STORAGE FAILED the value of the WTOR buffer limit.
During WTOR or DOM processing, it was not v Put the display console in roll mode to let a specified
possible to obtain storage necessary to complete the number of messages roll off the screen at a specified
operation. time interval.
v Respond to any messages requesting an operator
System Action: For WTOR processing, if possible, a
action.
reply ID is assigned. For DOM processing, the reply ID
is released and processing continues. System Programmer Response: Before the next
system initialization, increase the value of MLIM in the
Operator Response: Contact your systems
CONSOLxx parmlib member to increase the maximum
programmer.
number of buffers that WTO messages can use.
exists, contact the IBM Support Center. If the problem is Detecting Module: IEAVMQWR
due to unexpected return codes from XCF, supply the
XCF return and reason codes.
IEA405E WTO BUFFER SHORTAGE - 80% FULL
Source: Master scheduler
Detecting Module: IEAVM616 messages is 80% of the limit value specified in the
MLIM parameter of a CONSOLxx parmlib member.
IEA403I VALUE OF RMAX HAS BEEN System Action: Processing continues. Consoles that
CHANGED TO 99 are currently in HOLD mode and have messages
waiting are taken out of HOLD mode. The system will
Explanation: The maximum number of systems which
no longer hold messages for other systems in the
could enter this sysplex is more than 8. The value of
sysplex. If another system is experiencing a WTO buffer
RMAX was less than 99. The system has increased
shortage, this system will resume sending messages to
RMAX to 99.
the constrained system. The system issues a D C,B
Operator Response: Contact the system programmer. command and a D EMCS,ST=B,L=Z command.
System Programmer Response: Review the value of Operator Response: Enter the DISPLAY CONSOLES
RMAX in CONSOLxx, and increase if necessary. command. If the console has accumulated a large

number of WTO messages, do one or more of the
| IEA411I SLIP TRAP ID=xxxx DISABLED FOR
following:
| {MATCHLIM | PRCNTLIM}
v Enter the CONTROL Q command to reroute the
messages. | Explanation: If disabled for MACHLIM, then the SLIP
| trap with ID of xxxx matched M times, where M is equal
v Enter the CONTROL S command to delete a
| to or greater than the matchlim value specified on the
specified number of messages.
| trap. The trap is disabled.
v Enter the CONTROL M,MLIM command to increase
the value of the WTO buffer limit. | If disabled for PRCNTLIM, then the SLIP trap with ID of
| xxxx has consumed more than P percent of the CPU,
v Put the display console in roll mode to let a specified
| where P is equal to or greater than the PRCNTLIM
number of messages roll off the screen at a specified
| value specified on the trap. The trap is disabled.
time interval.
v Respond to any messages requesting an operator System Action: The trap is disabled.
action. Source: SLIP
System Programmer Response: Before the next Detecting Module: IEECB941
system initialization, increase the value of MLIM in the
CONSOLxx parmlib member to increase the maximum
number of buffers that WTO messages can use. IEA412I SLIP TRAP ID=xxxx, x SDUMPS NOT
SCHEDULED. RETURN CODE=nn
Source: Communications task (COMMTASK) REASON CODE=mm |
Detecting Module: IEAVMQWR RETURN/REASON CODES NOT
AVAILABLE
IEA406I WTO BUFFER SHORTAGE RELIEVED Explanation: The event specified for a SLIP trap
occurred. The trap requested an SVC dump. When
Explanation: The shortage of buffers for write to SLIP processing requested one or more dumps for the
operator (WTO) messages was relieved. The system trap, one of the following occurred:
issued message IEA405E and/or IEA404A to indicate
v The internal resources required to process the SVC
the shortage.
dumps are not available. The resources are currently
System Action: The system continues processing. being used for another SVC dump. This situation may
The system resumes normal message processing. occur if the SUMLIST or LIST parameter is specified
on the SLIP command. The return/reason codes may
Source: Communications task (COMMTASK) not be available.
Detecting Module: IEAVMQWR v Another dump is in progress.
– If the message contains the text RETURN
IEA407I DIRECTORY ENTRY FOR MODULE CODE=nn REASON CODE=mm, then the dump
mem INVALID IN SYS1.LPALIB in progress is not related to the dump requested
by the slip trap.
However, if the message contains the text
found an incorrect directory entry for a member of
RETURN/REASON CODES NOT AVAILABLE,
SYS1.LPALIB while attempting to build the link pack
then this slip trap has matched multiple times in
directory from SYS1.LPALIB.
quick succession. In this case, the first match
In the message text: successfully scheduled the dump. Subsequent
matches tried unsuccessfully to schedule the
mem A member of SYS1.LPALIB
dump, producing IEA412I. IEA412I can be ignored
System Action: Processing continues with the next in this case.
member. The system will resume holding messages for Note that if the time between matches is
the other system in the sysplex. If another system is sufficiently small, a trap can match multiple times
experiencing a WTO buffer shortage, this system will even if matchlim is 1.
hold its messages instead of sending them to the
v The system is set to ignore requests for SVC dumps.
constrained system.
Operator Response: Notify the system programmer. See OS/390 MVS Programming: Authorized Assembler
Services Reference LLA-SDU for details on the return
and reason codes.
cause of the incorrect directory entry, and link-edit the
member of SYS1.LPALIB again, if necessary.
xxxx The ID of the matching trap.
x The number of dumps that were not scheduled.

nn The return code from the first failing SDUMP The status of the following resources that control PER is
invocation. unknown:
mm The reason code from the first failing SDUMP v PER control registers
invocation. v PER bit in the old program status words (PSW) for
each system
For additional details on the return and reason codes, v PER bit in the PSWs that are stored in request
see the SDUMP macro in OS/390 MVS Programming: blocks (RB)
Authorized Assembler Services Reference LLA-SDU.
v PER bit in the new PSWs for SVC, external, and I/O
System Action: The system continues processing, but interruptions for each system
does not write the requested SVC dumps. v PER bit in the address space control block (ASCB)
Source: SLIP for each address space
Detecting Module: IEECB909 Thus, PER interruptions might continue to occur. They
will not be processed by SLIP but can slow system
IEA413I SLIP TRAP ID=xxxx DATA performance.
UNAVAILABLE System Action: The system writes a logrec data set
Explanation: While checking for a match for a SLIP error record. The system also does the following:
trap, SLIP processing was unable to access the data v For case 1, the system writes an SVC dump.
specified by the DATA parameter on the SLIP v For case 2, because of the state of the system, the
command. The reason is either: system does not write an SVC dump.
v The data is paged out.
v An indirect pointer to the data is paged out. Operator Response: If the system programmer asks
for an SVC dump, set a SLIP trap.
In the message text: System Programmer Response: Do the following:
ID=xxxx 1. Try to correct the status of the resources that control
The SLIP trap identifier specified on the SLIP PER by setting and then disabling a PER trap for an
command. address space that is not currently active in the
system.
SLIP counts the number of times the data is unavailable 2. If the status of the resources cannot be corrected,
to determine how often this message is issued: monitor the performance of the system to be sure it
v For a program event recording (PER) trap, this is operating within acceptable limits.
message is issued only the first time the data is 3. Search problem reporting data bases for a fix for the
unavailable. problem. If no fix exists, report the problem to the
v For a non-PER trap, this message is issued each IBM Support Center. Provide the SVC dump. If an
time the data is unavailable. SVC dump is not produced with the abend, ask the
operator to set a SLIP to obtain an SVC dump.
System Action: The system continues SLIP
processing. The trap does not match. Source: Recovery termination manager (RTM)
Operator Response: Enter the DISPLAY SLIP=xxxx Detecting Module: IEAVTGLB, IEAVTPVT
command to display the current value of the unavailable
data counter. IEA415I SLIP ERROR ATTEMPTING TO
Source: SLIP ACTIVATE/DEACTIVATE PER, DUMP
SCHEDULED
Detecting Module: IEECB909
Explanation: SLIP processing encountered an error
while attempting to activate or deactivate program event
IEA414I SLIP UNABLE TO DEACTIVATE PER recording (PER) in an address space. The
Explanation: SLIP processing could not deactivate accompanying SVC dump identifies the address space.
program event recording (PER). The reason is either: The status of PER in the address space is unknown;
1. While trying to deactivate PER in the system, SLIP consequently:
encountered an error because of a previous error. v If the error occurred while SLIP processing was
Message IEE743I precedes this message. attempting to set or enable a PER trap, the trap
2. While trying to deactivate PER when a job step task might not be monitoring this address space.
or address space was ending, SLIP encountered an v If the error occurred while SLIP processing was
error. attempting to disable or delete a PER trap, PER

interruptions might continue to occur in this address
IEA422I ABEND IN IEAVTJBN DURING
space. They will not be processed by SLIP but can
PROCESSING FOR SLIP
slow system performance.
Explanation: SLIP processing encountered an error
System Action: The system writes an SVC dump.
while determining if program event recording (PER)
System Programmer Response: Do the following: should be active for a particular address space. The
v Try to correct the status of PER in the address space accompanying SVC dump identifies the address space.
as follows: The status of PER in the address space is unknown;
– If the error occurred while SLIP processing was consequently:
attempting to set or enable a PER trap, ask the v PER might not be active in the address space in
operator to enter SLIP MOD commands to disable which it should be active.
the same trap and then enable it.
v PER might be active in an address space in which it
– If the error occurred while SLIP processing was should not be active. PER interruptions might
attempting to disable or delete a PER trap, ask continue to occur in this address space. They will not
the operator to enter SLIP SET and SLIP MOD be processed by SLIP but can slow system
commands to set and then disable a PER trap for performance.
an address space that is not currently active in the
system. System Action: The system writes a logrec data set
error record and an SVC dump.
v If the status of PER cannot be corrected, search
problem reporting data bases for a fix for the System Programmer Response: Do the following:
problem. If no fix exists, report the problem to the 1. Enter the SLIP trap again, specifying either:
IBM Support Center. Provide the SVC dump.
v ACTION=IGNORE ASID=NONE to ignore the
Source: SLIP address space on the SLIP trap.
Detecting Module: IEAVTGLB v ASID=asid to trap the address space.
2. If the problem continues, search problem reporting
IEA416W SYSTEM TRACE INITIALIZATION
report the problem to the IBM Support Center.
TERMINATED DUE TO AN ERROR.
Provide the SVC dump, the logrec data set error
Explanation: An error occurred during the creation of records, and messages.
the system trace address space or during the
Source: SLIP
initialization of the system trace function. The system
trace function returned a nonzero return code. Detecting Module: IEAVTJBN
System Action: The system enters nonrestartable
wait state X'023'. IEA423I ERROR IN IEECB915
Operator Response: Notify the system programmer. Explanation: An error occurred during SLIP
processing.
programmer response for wait state X'023'. System Action: The system ends SLIP processing.
The system writes a logrec data set error record.
Source: System Trace
The system holds the messages generated by SLIP
processing until the command processing component
IEA421E START STOPPED PROCESSORS
receives control; for example, when a SLIP trap is
Explanation: The system has recovered. deleted.
System Action: The system continues processing. System Programmer Response: Search problem
This message is not removed automatically from a reporting data bases for a fix for the problem. If no fix
display console, and must be manually removed. exists, report the problem to the IBM Support Center.
Provide the logrec data set error record and messages.
Operator Response: Restart the systems stopped
during the recovery processing. Remove this message Source: Recovery termination manager (RTM)
from the display console.
Detecting Module: IEECB915
Detecting Module: IEAVNP51, IECVIRST, IECVFCHN

IEA424I SLIP ERROR DURING PER IEA426I SLIP TRAP ID=xxxx
ACTIVATION/DEACTIVATION, MODEL ACTION=SYNCSVCD CANNOT BE
PSA NOT UPDATED PERFORMED; ACTION=SVCD DONE.
Explanation: SLIP processing was not able to page-fix Explanation: An active SLIP trap specified program
the model prefix save area (PSA). Therefore, SLIP event recording (PER) and an action of SYNCSVCD.
could not update: The PER interrupt occurred while the system was:
v The PER bit in the external program status word v Disabled
(PSW) in the model PSA v Locked
v In service request block (SRB) mode
v The PER bit in the Supervisor Call (SVC) PSW in the
model PSA
ACTION=SYNCSVCD can be performed only when the
v The PER bit in the I/O new PSW in the model PSA system is:
v Enabled
If the system on which SLIP was running is varied v Unlocked
online, the PER bits associated with that system will be v In task mode
incorrect.
Rather than taking no diagnostic action, SLIP schedules
System Action: The system issues messages about an SVC dump with ACTION=SVCD.
the problem.
System Programmer Response: Search problem In the message text:
reporting data bases for a fix for the problem. If no fix ID=xxxx
exists, report the problem to the IBM Support Center. The SLIP trap identifier specified on the SLIP
Source: SLIP command.
Detecting Module: IEAVTGLB System Action: The system schedules an SVC dump.
The interrupted unit of work regains control and the
IEA425I SLIP ERROR DURING PER
ACTIVATION, CROSS MEMORY Operator Response: Reset the SLIP trap, as
SUPPORT IS INCOMPLETE specified by the system programmer.
Explanation: SLIP processing was activating a System Programmer Response: Do one of the
program event recording (PER) trap. Because the SLIP following:
command did not specify IGNORE, the trap was to be v If the PER interrupt occurred for an incorrect event,
active immediately. SLIP processing activated PER, but ask the operator to reset the trap and specify
cross memory support was incomplete. Therefore, SLIP additional filtering keywords.
processing does not intercept any cross-memory-set- v If the interrupt was supposed to occur while the
initiated address space changes. system was disabled, locked, or in SRB mode, ask
The following occurs: the operator to reset the trap and specify
ACTION=SVCD rather than ACTION=SYNCSVCD.
v If the SLIP trap was defined with the ASID parameter
but without the MODE=HOME parameter, important Source: SLIP
data may not be trapped.
Detecting Module: IEAVTSLT
v In all other cases, the trap captures the desired
information, but SLIP processing may slow system
performance slightly. IEA430E dev, MAINTENANCE REQUIRED,
ACTION CODE = ac
Explanation: A device returned an I/O error with an
Operator Response: Notify the system programmer. action code. The device can run in degraded mode, but
System Programmer Response: Make sure the SLIP it will eventually require maintenance.
trap was specified correctly. In the message text:
Source: SLIP dev
Detecting Module: IEECB909 The device number.
ac Action code X'5' or X'B'.
Operator Response: See the book for the device type
for an explanation of the action code. Contact hardware
support, if needed.

Source: Input/output supervisor (IOS) Source: DFSMSdfp
Detecting Module: IGE0002G
IEA435I PHYSICAL DEVICE INCONSISTENT
WITH LOGICAL DEFINITION
IEA431A dev, POSSIBLE LOST DATA, ACTION
[PHY=pdevtype LOG=ldevtype] text
CODE = cc
Explanation: During VARY,ONLINE command
Explanation: A device returned an I/O error with an
processing, the device service exit determined that the
action code. The system may not have printed one or
physical device type was not compatible with the logical
more print lines.
device type defined in the I/O configuration.
If PHY=pdevtype LOG=ldevtype appears in the
dev message, there are mismatches between the hardware
The device number. configuration and the device definition in HCD.
cc Action code X'2', X'6', or X'B'. In the message text:
System Action: The system issues the failing channel pdevtype

command word (CCW) again. The physical device type
Operator Response: See the book for the device type ldevtype
for an explanation of the action code. To recover The logical device type defined in the I/O
missing output, backspace the JES writer or rerun the configuration.
job. Contact hardware support, if needed.
text Additional message text.
Additional message information is issued if
Detecting Module: IGE0002G there is a conflict in the way the tape device
has been defined through the HCD and the
physical attributes of the device as reported
IEA432I sysa IS REMOVING sysb FROM THE through initialization I/O. The reasons for this
SYSPLEX. sysa IS EXPERIENCING conflict are reported through the explanatory
STORAGE SHORTAGES. text that is appended to the message. The
Explanation: System sysb is attempting to join the reasons are:
sysplex. However, system sysa cannot obtain enough HCD DEVICE DEFINITION AT VARIANCE
storage to maintain a view of sysb that is consistent WITH RDC DATA
with other systems in the sysplex. The device is defined through HCD as one
In the message text: type of device but RDC data indicates a
different type of device.
sysa An active system in the sysplex.
System Programmer Response: Correct
sysb A system that is attempting to join the sysplex. the HCD device definitions to match the
System Action: System sysa removes the joining device type of the device physically
system from the sysplex. The joining system enters wait attached to the system.
state code X'087'. DEFINED WITH COMPACTION, BUT
Operator Response: Relieve the storage constraint FEATURE NOT PRESENT
on sysa, then reIPL sysb. The HCD definition for the device is at
variance with the actual attribute of the
Source: Communications task (COMMTASK) device with respect to compaction.
Detecting Module: IEAVG607 System Programmer Response: Correct
the HCD device definitions to match the
IEA434I DEVICE ONLINE IS NOT ALLOWED, device type of the device physically
reason attached to the system.
Explanation: During VARY ONLINE command 3590 DRIVE DETECTED BUT NOT ALL 3590
processing, the device service exit determined that the SUPPORT IS PRESENT
device is not allowed to become online for the reason Support for the 3590-E1x drives was
specified. (Example, SPARE DEVICE). shipped through PTF UW90622. If this
PTF is not installed, this message will be
System Action: The device remains offline. issued.
System Programmer Response: Check the system System Programmer Response: Install
configuration to determine if the device number is the required maintenance.
correct.

3590 IN 3490 EMULATION MODE NOT
IEA437I TAPE LIBRARY DEVICE(dev), text
ALLOWED IN ATLDS
3590 tape devices that are operating in Explanation: Initialization for an ATLDS device failed.
their 3490 emulation mode are not The device will not be brought online until the cause of
supported in the ATLDS. the failure is corrected.
System Programmer Response: Take In the message text:
the device out of that emulation mode and
dev The number of the failing ATLDS device
attach the device at the appropriate
address for its device type. text One of the following:
INITIALIZATION I/O FAILED LIBRARY INTERFACE IS OFFLINE
Initialization I/O required to successfully The hardware communication path
initialize a tape device has failed. between the tape control unit and the
library manager has not been established.
Determine the cause of the failure. Recovery Action: Contact your hardware
service representative to restore the
SENSE ID I/O INDICATES UNSUPPORTED
communication path to the library
DEVICE TYPE
manager.
Sense ID I/O was successfully issued to
the device and the resulting information RETURNED A ZERO LIBRARY-ID
indicates a device type that is not The hardware communication path
recognized by the system. between the tape control unit and the
library manager has been established, but
System Programmer Response: Correct
the library manager returned an incorrect
the HCD device definitions to match the
library-id (zeroes) to the host.
device type of the device physically
attached to the system. Recovery Action: Contact your hardware
service representative to repair the library
System Action: The device is not allowed online, and
manager.
remains offline.
INITIALIZATION FAILURE
System Programmer Response: Correct the HCD
The device was defined with HCD as a
device definitions to match the device type of the device
LIBRARY device, but the host was unable
physically attached to the system. See also text above
to obtain library information from the
for any other response needed, due to the additional
device. The channel program command
explanatory text.
that failed was Read Device
Source: DFSMSdfp Characteristics (RDC).
Recovery Action: Contact your hardware
IEA436I I/O ERROR DURING DEVICE service representative to determine the
INITIALIZATION cause of the RDC failure.
Explanation: During VARY,ONLINE command UNAVAILABLE TO LIBRARY MANAGER
processing, the device service exit received an The hardware communication path
unexpected I/O error while attempting to obtain the between the tape control unit and the
physical device characteristics. library manager has been established, but
the library manager has ’marked’ the
This message can also be seen if an older device that
device unavailable.
does not support the SENSE ID CHANNEL command is
attached to an incompatible UCB type; in other words, Recovery Action: Contact your hardware
the physical device does not match the logical device. service representative to repair the device
and restore its availability to the library
System Action: The device remains offline.
manager.
Operator Response: Use established procedures for
HCD(xxxxx-xx),DEVICE(xxxxx-xx)
reporting a hardware error. If this appears to be a
During device initialization, it was found
mismatch of logical and physical device types, notify the
that the LIBRARY-ID and LIBPORT-ID
system programmer.
specified to HCD do not match the
System Programmer Response: If the logical device LIBRARY-ID and LIBPORT-ID that were
and physical device are not compatible, correct the assigned to the hardware during
HCD device definitions. installation.
Source: DFSMSdfp Recovery Action: Correct either the

hardware or HCD. If the hardware was in

error (or was incorrectly attached to the is a different device type than those that
system), correct the hardware and then were previously defined for the same
VARY the device ONLINE. Use the string.
command DS QT,dddd,RDC to determine
Recovery Action: Correct either the
the library-ID and libport-ID assigned to
hardware or HCD. If the hardware was in
the hardware. In the following example,
error (or was incorrectly attached to the
device 2C80 is assigned library-ID BA067
system), correct the hardware and then
and libport-ID 01:
vary the device online. Use the command
DS QT,2C80,RDC
READ DEVICE CHARACTERISTICS DS QT,dddd,RDC to determine the
34905434905400EO 1FD8808004000000 00000000 00000000 library-ID and libport-ID assigned to the
0BA0607010000000 4281000000000000 00000000 00000000
hardware.
ACTIVATE IODF=XX, IS REQUIRED
The device was unavailable when the TAPE LIBRARY DEVICE aaaa (bbbbb-cc)
currently active eligible device tables DEFINED AS MTL BUT DEVICE xxxx
(EDTs) were built; the EDTs are used for (yyyy-zz) IS REAL ATL/VTS DEVICE. DEVICE
device allocation. Although the device is NOT ALLOWED ONLINE.
now available to this system, it cannot be The tape drive at address aaaa, with HCD
allocated until the EDTs are rebuilt. EDTs defined LIBRARY-ID bbbbb and
are rebuilt during IODF activation. LIBPORT-ID cc is defined as an MTL
resident drive (for example, MTL=YES was
Recovery Action: Activate the current specified with LIBRARY-ID and
IODF, then VARY the device ONLINE. LIBPORT-ID), but the RDC data indicates
that the drive resides in the ATLDS. The
TAPE LIBRARY DEVICE aaaa (bbbbb-cc) IS
device is treated as a valid ATL resident
A DUPLICATE OF DEVICE xxxx (yyyyy-xx)
drive.
AND IS BEING MARKED FOR DELETION
A device with CUU=xxxx, Recovery Action: Review the HCD
LIBRARY-ID=yyyyy, and LIBPORT-ID=zz is definition for the device.
being processed and another device with
CUU=aaaa, LIBRARY-ID= bbbbb, and TAPE LIBRARY DEVICE aaaa (bbbbb-cc)
LIBPORT-ID=cc has been found that: EMULATING 3490 NOT ALLOWED ONLINE
IN AN MTL.
v has the same hardware reported The tape drive at address aaaa, with HCD
sequence number, or defined LIBRARY-ID bbbbb and
v has the same CUU, that is, xxxx=aaaa. LIBPORT-ID=cc, is defined as an MTL
resident drive but is emulating a 3490
It is determined to be the same device and device which is not supported in an MTL.
the device with CUU=aaaa is not allowed The device is not allowed online.
online.
Recovery Action: Review the HCD
definition for the device.
This can occur in a variety of situations,
for example, when two control units are MTL DEVICE aaaa (bbbbb-cc) IS ATTACHED
physically uncabled from the library, and TO A CONTROL UNIT THAT IS DIFFERENT
when recabled, the port cables are THAN THAT FOR OTHER DEVICES
switched. ALREADY IN THE POOL.
The tape drive at address aaaa, with HCD
Recovery Action: Correct either the defined LIBRARY-ID bbbbb and
hardware or HCD. If the hardware was in LIBPORT-ID cc, is attached to a control
error (or was incorrectly attached to the unit different than that for devices already
system), correct the hardware and then in the pool. The device is not allowed
vary the device online. Use the command online.
DS QT,dddd,RDC to determine the
Recovery Action: Review the HCD
library-ID and libport-ID assigned to the
definition for the device, and other devices
hardware.
with the same LIBRARY-ID and
TAPE LIBRARY DEVICE aaaa (bbbbb-cc) IS LIBPORT-ID values. Ensure that all
A DIFFERENT DEVICE TYPE THAN devices for the same LIBRARY-ID and
DEVICES PREVIOUSLY DEFINED IN THE LIBPORT-ID values are connected to the
SAME STRING. THE DEVICE IS NOT same control unit.
ALLOWED ONLINE
TAPE LIBRARY DEVICE aaaa (bbbbb-cc)
A device with CUU=aaaa,
NOT ALLOWED ONLINE, UNABLE TO ADD
LIBRARY-ID=bbbbb, and LIBPORT-ID=cc

LIBRARY TO CONTROL BLOCK. System Action: The device is not available for use by
The tape drive at address aaaa, with HCD the system.
defined LIBRARY-ID bbbbb and
System Programmer Response: To determine the
LIBPORT-ID cc, cannot be added to the
reason that a device is unavailable, attempt to vary one
existing device pool because it is full. The
of the devices online. If the error has been corrected,
device is not allowed online.
the device will be brought online. If the error still exists,
Recovery Action: Review the HCD message IEA437I will explain the reason for the failure.
definition for the device, and other devices If the device is displayed with an asterisk, it will become
with the same LIBRARY-ID and available when the error has been corrected.
LIBPORT-ID values. Ensure that MTL
If the device is not displayed with an asterisk, perform
devices are not overgenned.
an IPL or an I/O activate after correcting the error to
INVALID PEER-TO-PEER VTS DATA make the device available to the system after the error
During initialization of a device in a has been corrected.
Peer-to-Peer VTS, the I/O operation
If an I/O activate is to be done, the device must first be
requesting Peer-to-Peer configuration data
varied online. The device does not need to remain
either failed or returned invalid information.
online.
This message is issued when an RDC
command returned data indicating that the Source: Tape Device Initialization Exit (DSE)
device is in a Peer-to-Peer VTS library.
However, the subsequent request to obtain Detecting Module: IECTDSR2
Peer-to-Peer data failed (or returned
invalid data). IEA441I UNABLE TO ESTABLISH MVS MODE
Recovery Action: Correct your hardware CONTROLS FOR DEVICE nnnn
service representative to determine the Explanation: An error was encountered during
cause of the failure. issuance of mode control CCWs for device number
System Action: The device is not available for use by nnnn. The error prevents setting the mode control page
the system. values. When these controls are not properly set, the
device cannot be brought online.
System Programmer Response: When the condition
has been corrected, attempt to VARY the device Mode control CCWs set certain attributes of the device
ONLINE. If the device was previously defined to HCD in a manner well-defined for normal MVS processing.
as a library device, with the proper library-ID and Mode control CCWs are issued by MVS when the
libport-ID, the device will come ONLINE. device:
If the device is not defined with HCD as a library device, is allocated if it is ready, or
the device will not be allowed ONLINE if an IODF comes ready, if it is already allocated
activate is required. Message ACTIVATE IODF=XX, IS System Action: The device is boxed.
REQUIRED indicates that because of previous failure,
the library-ID and libport-ID were not known when the Operator Response: Once the cause of the error has
systems EDTs were build. Now that these IDs are been determined and corrected, the device can be
known, an activate is required in order to cause the varied online. Varying the device online before the error
EDTs to be rebuilt. is corrected may cause the error to occur again.
Source: Tape Device Initialization Exit (DSE) System Programmer Response: Collect diagnostic
data such as GTF traces for I/O and any system logs
Detecting Module: IECTDSR2 that are available. Follow your installation’s procedures
for reporting this error.
IEA438I THE FOLLOWING TAPE LIBRARY Source: Asynchronous Operation Manager Attention
DEVICE ARE UNAVAILABLE: dev [dev Processing Routine for Tape Devices (AOMATTNT)
... dev [*dev]]
Explanation: During IPL, initialization failed for one or IEA442E dev REPORTS DISABLED INTERFACE
more library devices. In many cases, this message is ON nn -- FAULT CODE = cccc -- NOTIFY
normal and expected. For example, if the interface to a CE
3490 string is disabled, and the devices were defined
with HCD as library devices, those library devices will [CONTINUATION OF IEA442E
be listed in this message. SNS=sense]
Devices that are displayed with an asterisk will become Explanation: An I/O request failed because a storage
available when the error has been corrected, without an director within a 3880 Storage Control Unit is disabled.
IPL or I/O activate request being required. In the message text:

dev The address of the I/O device that reported the returned environmental data. The data has been written
disabled status of storage director. to the logrec data set.
nn The disabled storage director identifier. In the message text:
cccc The fault code that explains why the storage ss Subsystem ID (SSID)
director is disabled.
ss.p SSID storage path
sense Sense data.
xx-xx Controller device
System Action: The system records the disabled
sense Sense data.
status of storage director in a logrec data set error
record. The system retries the I/O request on the System Action: Processing continues.
specified device.
Source: DFSMSdfp
Detecting Module: IGGSNS01
v Isolate the failing control unit. Contact hardware
support to repair it.
v If only one unit remains, transfer critical applications IEA449A RESET WRITE INHIBIT SWITCH ON
to back-up. PAGING DEVICE - device-number
v Identify and recover failing tasks.
[CONTINUATION OF IEA449A
Source: DFSMSdfp SNS=sense]
Detecting Module: IECVDERP, IGGSNS01 Explanation: The 3880 Storage Control Model 11 or
21 detected a 3350 write inhibit switch in the read
position. The last digit, in hexadecimal, identifies the
IEA447E PATH chp TO DEVICE s-cc-d physical 3350, as follows:
UNAVAILABLE
Digit 3350 Device
Explanation: The system cannot reach a device
through a path. A hardware error occurred, or the data 0 or 8 0
path switch for the device is open.
1 or 9 1
2 or A 2
chp The identifier (CHPID) of the unavailable
3 or B 3
channel path.
4 or C 4
ss-cc-d The identifier of the storage director that found
the problem. 5 or D 5
System Action: The system varies the path offline. If 6 or E 6
additional paths are available, the system retries the
7 or F 7
failing channel program on another path to the device.
Operator Response: If the data path switch is open, In the message text:
close it. Otherwise, do the following:
device-number The path ID of the path that reported
v Isolate the failing control unit. Contact hardware the error.
support to repair it.
v If only one unit remains, transfer critical applications sense Sense data.
to back-up. System Action: The error recovery procedure (ERP)
v Identify and recover failing tasks. reissues the channel command words (CCWs) that
failed.
Source: DFSMSdfp
Operator Response: Set the 3350 write inhibit switch
Detecting Module: IGGSNS01 to the write position. Then reply ‘U’ to this message.
This message may be followed by another IEA449A
IEA448I 1,SENSE DATA LOGGED FOR DEVICE message after you have set the switch; reply ‘U’ to this
ss.p-xx-xx second IEA449A to continue processing.
[CONTINUATION OF IEA448I Application Programmer Response: None.

SNS=sense] Source: DFSMSdfp
2,SENSE DATA LOGGED FOR
CONTROLLER ss.p-xx-xx Detecting Module: ERPs
Explanation: The specified device or controller has

IEA451I {MICROCODE LOGICAL|SUBSYSTEM
PROCESSING} ERROR - FAULT CODE Source: DFSMSdfp
= cccc-ss.p-xx-xx
[CONTINUATION OF IEA451I
SNS=sense] IEA453I {SUBSYSTEM|NVS} STORAGE
AVAILABILITY THRESHOLD CROSSED
Explanation: An internal logic error occurred during a
-ss.p-xx-xx
subsystem storage operation on a Storage Control
device with a cache.
In the message text: SNS=sense]
cccc The fault symptom code from sense bytes 22 Explanation: The amount of subsystem storage
and 23. offline, in the 3880 Storage Control with a cache
crossed a reporting boundary making a portion of the
ss.p-xx-xx
subsystem storage unusable.
The physical identifier of the reporting storage
director. In the message text:
sense Sense data. ss.p-xx-xx
The physical identifier of the reporting storage
System Action: The system ends I/O processing for
director.
this request. If the error occurred in a Storage Control
device with a cache subsystem storage is taken offline, sense Sense data.
and future I/O requests are processed directly with the
DASD. System Action: The error recovery procedure (ERP)
reissues the channel command words (CCW) that
Operator Response: The system issues this message failed.
because of a microcode error. Follow installation
procedures to take corrective action. Operator Response: The system issues this message
because of a hardware error. The subsystem storage
Application Programmer Response: If the error remains operational, allowing service to be deferred
occurred on the Model 11 or 21, reconfigure the system until it is convenient. Follow installation procedures to
to move the paging data to another subsystem. take corrective action.
Otherwise, no action is required.
Source: DFSMSdfp
Source: DFSMSdfp
IEA452I SUBSYSTEM STORAGE EQUIPMENT Detecting Module: IGGSNS01

CHECK - FAULT CODE =
cccc-ss.p-xx-xx IEA454E SUBSYSTEM STORAGE IS UNUSABLE
- FAULT CODE = cccc-ss.p-xx-xx
SNS=sense] [CONTINUATION OF IEA454I
Explanation: An equipment check occurred during a SNS=sense]
subsystem storage operation on the 3880 Storage Explanation: Subsystem storage in a Storage Control
Control with a cache. device with a cache is unusable due to previously
In the message text: reported failures of a device or subsystem storage. The
failures are recorded in the error recording data set.
cccc The fault symptom code from sense bytes 22
and 23. In the message text:
ss.p-xx-xx cccc The fault symptom code from sense bytes 22

The physical identifier of the reporting storage and 23.
director. ss.p-xx-xx
sense Sense data. The physical identifier of the reporting storage
director.
this request. sense Sense data.
Operator Response: The system issues this message System Action: The system ends I/O processing for
because of a hardware error. Follow installation this request. If the problem occurred in a Storage
procedures to take corrective action. Control device with a cache subsystem storage is taken

offline, and future I/O requests are processed directly ss.p-xx-xx
with the DASD. The physical identifier of the reporting storage
director.
Operator Response: The system issues this message
because of a hardware error. Follow installation sense Sense data.
procedures to take corrective action.
System Action: The error recovery procedure (ERP)
Application Programmer Response: If the problem reissues the channel command words (CCW) that
occurred on the 3880 Model 11 or 21, reconfigure the failed.
system to move the paging data to another subsystem.
Otherwise, no action is required.
Application Programmer Response: Format the
Source: DFSMSdfp
paging packs attached to the paging storage director of
Detecting Module: IGGSNS01 the 3880 Model 11 or 21.
IEA455E SUBSYSTEM STORAGE MUST BE and the program is not in error, search problem
INITIALIZED - FAULT CODE = reporting data bases for a fix for the problem. If no fix
cccc-ss.p-xx-xx exists, contact the IBM Support Center.
Source: DFSMSdfp
[CONTINUATION OF IEA455E
SNS=sense] Detecting Module: IGGSNS01
Explanation: An error occurred during a subsystem
storage operation on the 3880 Storage Control Model IEA458I STORAGE DIRECTOR
11 or 21. The data in the cache may not be valid. COMMUNICATION FAILED - FAULT
CODE = cccc-ss.p-xx-xx
cccc The fault symptom code from sense bytes 22 [CONTINUATION OF IEA458I
and 23. SNS=sense]
ss.p-xx-xx Explanation: The 3880 cache control unit storage
The physical identifier of the reporting storage directors cannot communicate.
director.
sense Sense data.
cccc The fault symptom code from sense bytes 22
System Action: The system ends I/O processing for and 23.
this request.
ss.p-xx-xx
Operator Response: The system issues this message The physical identifier of the reporting storage
because of a hardware error. System IPL may be director.
required to continue operations. System IPL is required
sense Sense data.
to reinitialize the storage for this subsystem. Follow
installation procedures to take corrective action. System Action: The error recovery procedure (ERP)
reissues the channel command words (CCW) that
failed.
subsystem storage remains unusable following the
system IPL, reconfigure the system to move the paging Operator Response: Check the 3380 Enable/Disable
data to another subsystem. switches to ensure that they are enabled. If the 3380
switches are enabled, or the problem occurred on the
Source: DFSMSdfp
3880 Control Unit, this problem is probably the result of
Detecting Module: IGGSNS01 a hardware error. Follow installation procedures to take
corrective action.
IEA457I TRACK FORMAT NOT SUPPORTED Application Programmer Response: None.
FOR PAGING - ss.p-xx-xx
Source: DFSMSdfp
[CONTINUATION OF IEA457I Detecting Module: IGGSNS01
SNS=sense]
Explanation: The 3880 Storage Control Model 11 or
21 detected an incorrect track format or no-record-found
error.

IEA459I CACHING [RESET-REDEFINE BOUND
AREAS/NON-CACHING DEVICES|
REINITIATED] - ss.p-xx-xx
stand-alone dump.
[CONTINUATION OF IEA459I Source: Supervisor Control
SNS=sense]
Detecting Module: IEAVEGR
Explanation: Caching was automatically reinitialized
by the 3880 Storage Control following a storage director
IEA466I PATH(dev,chp) PERMANENT I/O
communication timeout or a subsystem storage control
ERROR {sense|FAULT CODE=cccc}
structure failure.
Explanation: The system detected a permanent error
on a single path on a device with multiple paths. The
ss.p-xx-xx system completed the request on an alternate path to
The physical identifier of the reporting storage the device.
director.
dev The device number.
sense Sense data.
chp The channel path identifier (CHPID).
System Action: The error recovery procedure (ERP)
sense The sense byte information.
reissues the channel command word (CCW) that
received the message. cccc The fault code.
Operator Response: Bound areas of cache and the System Action: The system varies the path offline.
non-caching state of the devices were reset. If any
bound areas or non-caching devices are required, they Operator Response: Do the following:
must be established. If none are required, no action v Isolate the failing control unit. Contact hardware
need be taken. support to repair it.
Application Programmer Response: None. v If only one unit remains, transfer critical applications
to back-up.
Source: DFSMSdfp v Identify and recover failing tasks.
Detecting Module: IGGSNS01 Source: DFSMSdfp
Detecting Module: IECVDER2
IEA460W SYSTEM ERROR: WAIT STATE CODE:
ccc REASON CODE: rrr [THE SYSTEM
CANNOT TERMINATE ASID hhhh] IEA467E PATH(dev,chp) type WRITE INHIBITED
sense
Explanation: The system attempted to rebuild the
work unit queues, but it could not do so successfully. Explanation: The system found a hardware write error
on a channel path. Recovery was unsuccessful on that
In the message text: path. Subsequent writes to that device or any other
ccc device on that interface could result in a loss of data.
The wait state code. In the message text:
rrr The reason code associated with the wait state dev The device number.
code.
THE SYSTEM CANNOT TERMINATE ASID hhhh
The system encountered an address space whose sense The sense byte information.
queues it could not rebuild, so it tried to terminate
type The component for which the system
the address space. The system could not terminate
established the write inhibit condition. One of
the address space, so it entered a wait state.
the following devices:
hhhh v The channel interface
The identifier of the address space that the system v The storage director
needed to terminate in order to continue v The DASD controller
processing.
System Action: The system varies the device path
System Action: The system enters a non-restartable logically offline. The system issues message IEA469E.
wait state. If additional paths are available, the system retries the
failing chain on another path to the same device.
Operator Response: Provide a stand-alone dump, if
requested by the system programmer. Operator Response: If the error persists, do the
following:

1. Enter the following: to vary the path offline, reset the fenced condition to one of the devices
assuming that the path is online but not allocated: attached to the fenced interface.
VARY PATH(dev,cc),OFFLINE, UNCOND 3. If no online paths remain to the device, do the
2. After hardware support corrects the problem, submit following:
a job to run an ICKDSF CONTROL command to v VARY FORCE the devices attached to the
reset the fenced condition to one of the devices interface offline.
attached to the fenced interface. v Cancel all jobs that are using the device.
3. If no online paths remain to the device, do the v Vary online at least one path to the device.
following:
v Vary the device online, making sure that no jobs
v VARY FORCE the devices attached to the allocate the pack.
interface offline.
v Enter an ICKDSF CONTROL WRITEALLOW
v Cancel all jobs that are using the device. command, directing it to one device attached to
v Vary online at least one path to the device. the failing interface.
v Vary the device online, making sure that no jobs v Vary online all paths that the system varied
allocate the pack. offline.
v Enter an ICKDSF CONTROL WRITEALLOW 4. If paths remain online, do the following:
command, directing it to one device attached to v Enter an ICKDSF CONTROL WRITEALLOW
the failing interface. command, directing it to one device attached to
v Vary online all paths that the system varied the failing interface.
offline. v Vary online all paths that the system varied
4. If paths remain online, do the following: offline.
v Enter an ICKDSF CONTROL WRITEALLOW Source: DFSMSdfp
command, directing it to one device attached to
the failing interface.
IEA469E {PATH (dev,chp) HAS BEEN VARIED
v Vary online all paths that the system varied
OFFLINE| PATH (dev,chp) CANNOT BE
offline.
VARIED OFFLINE}
Source: DFSMSdfp
SNS=sense]
Explanation: A hardware error occurred. Recovery for
IEA468I WRITE INHIBITED PATH (dev,chp)
the direct access storage device (DASD) determined
ENCOUNTERED
that a path should be varied offline.
[CONTINUATION OF IEA468I In the message text:
SNS=sense]
Explanation: The system tried to issue I/O to a device
through a path that was write inhibited.
sense Sense data.
System Action: If the path is online, the system
retries the failing channel command word (CCW) chain
chp The channel path identifier (CHPID). on another path to the same device.
sense Sense data. Depending on the message text, one of the following:
System Action: The system varies the path offline. If PATH (dev,cc) HAS BEEN VARIED OFFLINE
additional paths are available, the system retries the The DASD recovery varies the path offline.
failing I/O on another path to the same device.
PATH (dev,cc) CANNOT BE VARIED OFFLINE
Operator Response: If the error persists, do the The DASD recovery does not vary the path offline
following: because it is the last path to the device.
1. Enter the following: to vary the path offline, Operator Response: If PATH (dev,cc) CANNOT BE
assuming that the path is online but not allocated: VARIED OFFLINE appears in the message text, and the
VARY PATH(dev,cc),OFFLINE, UNCOND error persists, enter a VARY PATH or UNCOND
2. After hardware support corrects the problem, submit command to vary the path offline.
a job to run an ICKDSF CONTROL command to Source: DFSMSdfp

IEA473I vvvvvv FENCED FROM STORAGE PATH IEA475E vvvvvv IS SUSPENDED DUPLEX
x - device-number/ssid.p-cc-nn {PRI|SEC} FAILED|INTERVENTION
REQUIRED - ccu/ssid.p-cc-nn
SNS=sense] [CONTINUATION OF IEA475E
SNS=sense]
Explanation: A device is unavailable through a
storage path due to a hardware error. Explanation: The storage director cannot successfully
update the primary or secondary device of a duplex
pair. The system may issue this message as a result of
vvvvvv The volume that failed. improper procedures.
x The storage path fenced. In the message text:
device-number The physical device address. vvvvvv The volume that failed.
ssid The subsystem identifier. device-number The physical device address.
p The storage path. ssid The subsystem identifier.

cc The controller address. p The storage path.
nn The device number. cc The controller address.

sense Sense data. nn The device number.
System Action: The subsystem attempts to recover sense Sense data.

the operation using an alternate path.
System Action: Processing will continue in suspended
Operator Response: The system issues this message duplex mode.
because of a hardware error. Follow your installation’s
procedures for reporting this error.
Source: DFSMSdfp procedures for reporting this error. If the device
associated with this message is attached via the IBM
Detecting Module: IGGSNS01 3990 Model 3 or Model 6 Storage Control, see IBM
3990/9390 Operations and Recovery Guide for detailed
IEA474E NONVOLATILE STORAGE UNUSABLE - recovery actions.
ccu/ssid.p-xx-xx Source: DFSMSdfp
[CONTINUATION OF IEA474E Detecting Module: IGGSNS01

SNS=sense]
Explanation: The nonvolatile storage failed or could IEA476E vvvvvv ACCESS PROHIBITED -
not be initialized. RC=(reason-code) device-number/ssid.p-
cc-nn
device-number The physical device address. [CONTINUATION OF IEA476E
SNS=sense]
ssid The subsystem identifier.
Explanation: The status of the subsystem or a device
p The storage path. cannot be determined. Access is not allowed until the
sense Sense data. problem is corrected.
System Action: DASD fast write operations will In the message text:
continue without using fast write. Dual copy will continue vvvvvv The volume that failed.
with reduced recovery in the event of a cache failure.
reason-code The reason code of the failure. See
Operator Response: The system issues this message IBM 3990/9390 Storage Control
because of a hardware error. Follow your installation’s Reference, Chapter 5, “Sense Byte
procedures for reporting this error. Information” under the heading Format
Source: DFSMSdfp F Message C.
device-number The physical device address.
p The storage path.

cc The controller address. during a destage operation. The data is pinned in
cache/nonvolatile storage.
nn The device number.
sense Sense data.
vvvvvv The volume that failed.
this request. device-number The physical device address.
Operator Response: The system issues this message ssid The subsystem identifier.
because of a hardware error or configuration problem.
p The storage path.
Follow your installation’s procedures for reporting this
error. If the device associated with this message is cc The controller address.
attached via the IBM 3990 Model 3 or Model 6 Storage
Control, see IBM 3990 Operations and Recovery Guide nn The device number.
for detailed recovery actions. sense Sense data.
Source: DFSMSdfp System Action: Processing continues.
Detecting Module: IGGSNS01 Operator Response: The system issues this message
IEA477I vvvvvv PERMANENT DATA CHECK ON procedures for reporting this error. If the device
PRIMARY - RECOVERED ON associated with this message is attached via the IBM
SECONDARY device-number/ssid.p-cc-nn 3990 Model 3 or Model 6 Storage Control, see IBM
3990/9390 Operations and Recovery Guide for detailed
recovery actions.
SNS=sense] Source: DFSMSdfp
Explanation: A permanent read data check on the
primary device of a duplex pair was recovered by IEA479E vvvvvv TRACK FORMAT NOT
reading the secondary device. CORRECT FOR DESTAGE - RC=(rc)
device-number/ssid.p-cc-nn
vvvvvv The volume that failed. [CONTINUATION OF IEA479I
SNS=sense]
Explanation: An attempt to write data from cache to
DASD encounters a DASD track format incompatible
p The storage path. with the operation.
cc The controller address. In the message text:
nn The device number. vvvvvv The volume that failed.
sense Sense data. reason-code The reason code of the failure. See
IBM 3990/9390 Storage Control
Reference, Chapter 5, “Sense Byte
Operator Response: Follow your installation’s Information” under the heading Format
procedures for reporting this error. If the device F Message 7.
associated with this message is attached via the IBM
3990 Model 3 or Model 6 Storage Control, see detailed
recovery actions information in the IBM 3990/9390 ssid The subsystem identifier.
Operations and Recovery Guide.
p The storage path.
Source: DFSMSdfp
cc The controller address.
nn The device number.
sense Sense data.
IEA478E PINNED DATA FOR vvvvvv -
device-number/ssid.p-cc-nn System Action: If the destage is for a fast write, the
track is pinned in cache/nonvolatile storage. If the
[CONTINUATION OF IEA478E destage is to a duplex pair, the duplex pair is
SNS=sense] suspended.
Explanation: A permanent hardware error occurred Operator Response: Follow your installation’s
procedures for reporting this error. If the device

associated with this message is attached via the IBM twelve hexadecimal characters is the
3990 Model 3 or Model 6 Storage Control, see IBM recommended media maintenance
3990 Operations and Recovery Guide for detailed procedure number.
recovery actions.
volser The volume serial number of the
Source: DFSMSdfp failing volume. This field is only
applicable for 3390 SIMs where the
device or volume is involved in the
failure.
IEA480E yyyy, {SCU | CACHE | DASD | MEDIA },
id Two-hexadecimal character SIM ID.
{SERVICE | MODERATE | SERIOUS |
SIM ID is a subsystem-assigned
ACUTE} ALERT, MT=machine
identifier for each individual SIM. It
type/model, SER=MMPP-SSSSS,
appears in the console message as a
REFCODE= nnnn-nnnn-nnnn,
discrete field only for 3390 SIMs. For
VOLSER=volser, ID=id, CCHH=x'cccc
3990 SIMs, it is contained in the
hhhh', REPEATED [CONTINUATION OF
REFCODE as the last two digits.
IEA480E SNS=sense]
cccc hhhh MEDIA ALERTs only. Hexadecimal
Explanation: IEA480E is a Service Information
cylinder/head address of the failing
Message (SIM) console message. The specified device
track. Provided for use by automated
or storage control has detected an abnormal condition
media maintenance actions or to
that requires operator or service attention.
initiate media maintenance actions
In the message text: without the need to run EREP.
yyyy Address or number of the device or REPEATED Appears for non-MEDIA ALERTs only.
storage control that reported the error. This field is shown when the SIM is a
repeat presentation of a
SCU Storage control hardware. previously-reported SIM.
CACHE Storage control cache of nonvolatile sense Sense data.
storage.
System Action: The system logs an alert in the
DASD Storage device hardware. LOGREC data set and continues processing.
MEDIA Device data storage media. Operator Response: The system issues this message
SERVICE|MODERATE|SERIOUS|ACUTE to indicate that operator or service attention is required.
Follow your installation’s procedures for obtaining
Describes the severity of the SIM service. Consult your customer engineer, if applicable.
event being reported. ACUTE is the
most severe and SERVICE is the System Programmer Response: Run an EREP
least severe. For additional details, System Exception Report to obtain a Service
see IBM 3990 Operations and Information Message report for additional information.
Recovery Reference. Source: DFSMSdfp
machine-type/model Detecting Module: IGGSNS01
Machine type and model number (7
characters maximum).
IEA480E yyyy,{TLIB | TCU | TVIR | TAPE}, mt,
MMPP-SSSSS Where: {ACUTE | SERIOUS | MODERATE |
v MM identifies the manufacturer (01 SERVICE} ALERT, SER=mmpp-sssss,
indicates IBM). MC=mc, ES=es, ID=id, REF=
v PP identifies the manufacturing ref1-ref2-ref3, UM=um1-um2-um3,
plant. {CLEAN | CLEAN/SERVICE |
CLEANED}, REPEATED
v SSSSS is the five-digit machine
serial number. Explanation: IEA480E is a Service Information
Message (SIM) console message. The specified tape
nnnn-nnnn-nnnn-nnnn
library, tape controller, virtual tape server, or tape drive
Twelve hexadecimal characters; unit has detected an abnormal condition that requires
provides encoded information, operator or service attention.
including the FRU number to repair
the failure if a service SIM. For
MEDIA ALERTs, the last digit of these yyyy Address of unit that reported the SIM
message.

TLIB Automated tape library. software levels will only specify the ES code for
cleaning.
TCU Tape control unit.
If the specified unit is TAPE and CLEAN/SERVICE is
TVIR Virtual Tape Server (VTS).
presented (or ES=8B), then cleaning is required. Note
TAPE Tape drive. that some software levels will only specify the ES code
for cleaning.
mt Machine type of unit that caused the
SIM message. This will reflect the Repetitive occurrences of the CLEAN/SERVICE
software image of the machine type, message indicate that service beyond cleaning is
not necessarily the underlying physical required.
machine type. VTS, for example, will
If the specified unit is TAPE and CLEANED is presented
report '3490' as the machine type,
(or ES=9A), then cleaning was completed. No further
even though the underlying drive
action is required. Note that some software levels will
machine type may be 3590.
only specify the ES code for cleaning completed.
ACUTE|SERIOUS|MODERATE|SERVICE
If the specified unit is TAPE and ES has any other
Indicates the severity of the SIM value, then consult your customer engineer for detailed
message. ACUTE is the most severe recovery actions for the installed tape drive.
and SERVICE is the least severe.
If the specified unit is TLIB, then consult your customer
ser Serial number of unit referenced by engineer for detailed recovery actions for the installed
the SIM message. library.
mc Message code. Indicates source of If the specified unit is TVIR, then consult your customer
SIM. engineer for detailed recovery actions for the installed
VTS product.
es Exception/Service code.
If the specified unit is TCU, then consult your customer
id Identifier of the SIM in the control unit engineer for detailed recovery actions for the installed
internal SIM log. tape control unit.
ref1-ref2-ref3 Error reference codes. System Programmer Response: Run an EREP
um1-um2-um3 Unit modifier reference codes. Some System Exception Report to obtain a Service
software releases may not include Information Message report for additional information.
these codes. Source: DFSMSdfp
CLEAN Tape drive requires cleaning cartridge Detecting Module: IGGSNS02
to be inserted. Only returned for a
TAPE unit.
IEA481I CONTROLLER NOT OPERATIONAL
CLEAN/SERVICE WITH STORAGE PATH -
Tape drive requires cleaning cartridge device-number/ssid.p-cc-nn
to be inserted. Repeated occurrences
of CLEAN/SERVICE indicate the need
for additional service. Only returned
SNS=sense]
for a TAPE unit.
Explanation: The specified DASD controller cannot be
CLEANED Cleaning just completed for the tape
accessed through the specified storage path.
drive. Cleaning cartridge ejected. Only
returned for a TAPE unit. In the message text:
REPEATED Indicates this SIM has already been device-number The physical device address.
presented at least once prior to this
presentation.
p The storage path.
LOGREC data set and continues processing. cc The controller address.
Operator Response: The system issues this message nn The device number.
to indicate that operator or service attention is required.
Follow your installation’s procedures for obtaining sense Sense data.
service. Consult your customer engineer, if applicable. System Action: Processing continues.
If the specified unit is TAPE and CLEAN is presented Operator Response: The system issues this message
(or ES=89), then cleaning is required. Note that some because of a hardware error. Follow your installation’s
procedures for reporting this error. If the device

associated with this message is attached via the IBM command. Issue the MODIFY
3990 Model 3 or Model 6 Storage Control, see IBM LOGROUTE,NODEID=nodevalue.useridvalue command
3990/9390 Operations and Recovery Guide for detailed to correct the NODEID value.
recovery actions.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IGGSNS01 IEA484I CACHING STATUS RESET TO
DEFAULT - device-number/ssid.p-cc-nn
IEA482I ser WAITING FOR CONTROL UNIT -
dev, REASON CODE=(nn)
SNS=sense]
[CONTINUATION OF IEA482I Explanation: Retentive status of the subsystem, a fast
SNS=sense] write or dual copy has been reset.
Explanation: I/O was attempted to DASD device In the message text:
whose control unit is in an extended busy condition.
This busy condition might last for several minutes;
additional messages will describe the reason for the ssid The subsystem identifier.
busy condition.
p The storage path.
This problem may be caused by one of the following:
cc The controller address.
v The control unit could be busy destaging DASD fast
write data for the device when a SETCACHE nn The device number.
DASDFASTWRITE OFF command was issued.
sense Sense data.
v The control unit could also be busy copying data from
the primary device to the secondary device if a System Action: Processing continues.
SETCACHE SETSECONDARY command was issued Operator Response: If the device associated with this
to the device, particularly if PACE(0) parameter was message is attached via the IBM 3990 Model 3 or
specified. Model 6 Storage Control, see IBM 3990/9390
In the message text: Operations and Recovery Guide for detailed recovery
actions.
ser Volume serial number.
Source: DFSMSdfp
dev DASD device number.
nn Reason code IEA486E cuu, TVOL, {ACUTE | SERIOUS |
sense Sense data. MODERATE | SERVICE} ALERT,
VOLUME=volid, S=s, MC=mc, E=e,
System Action: The system will queue and REF=refc-med-fi, REPEATED
periodically retry the I/O to device dev until the control
unit accepts the request. Message IEA482I will be Explanation: IEA486E is a Media Information
displayed for each retry of the I/O request while the Message (MIM) console message. The specified device
busy condition exists. has detected an abnormal medium condition that
requires storage administration attention.
Source: DFSMSdfp
IEA483I LOGROUTE FAILED - DYNAMIC cuu Address of unit that reported the MIM
ALLOCATION ERROR RC=return-code message.
Explanation: A user issued the START LOGROUTE TVOL Tape Volume.

command to route a record to the workstation ACUTE|SERIOUS|MODERATE|SERVICE
NODE.USERID, but the command failed because of a
dynamic allocation error. Indicates the severity of the MIM
message. ACUTE is the most severe
In the message text: and SERVICE is the least severe.
return-code The return code. volid Volid of the tape volume referenced
System Action: No log records will be routed to the by the MIM message. If blank and the
workstation NODE.USERID. volume was not unlabeled, the volid
may still be determined from job or
Operator Response: Report this message to the system logs.
system programmer. If return-code is 046C, an incorrect
NODE was specified on the START LOGROUTE s Volid source.

mc Message code (to indicate MIM Note: The time indicated in the message is the
source). timestamp of the ERP action message, and not
necessarily the exact time of the failure. Select
e Exception code.
the CRIT(YES) option of the CESTPAIR
refc-med-fi Error reference code - Media identifier command if you require exact synchronization to
- Format identifier. the time of the failure.
REPEATED Indicates this MIM has already been volser
presented. This is the volume serial number of the PPRC
volume pair encountering the failure.
LOGREC data set and continues processing. error-reason
The error reasons are:
to indicate that storage administrator attention is v SUSPENDED, PRIMARY-DEVICE-WRITE-
required. For instructions, consult your customer FAILURE
engineer for the installed model supporting the indicated A write failure occurs during a write operation
media and format. from the application site storage control to the
primary device indicated by the volume serial
System Programmer Response: Run an EREP number. The primary volume storage control
System Exception Report to obtain a Media Information continues to keep track of changed cylinders,
Message report to obtain additional information. such that after the error is corrected, you may
Source: DFSMSdfp select the RESYNC option to reestablish the
PPRC pair.
v SUSPENDED, SECONDARY-SUBSYSTEM-
FAILURE
IEA489I INVALID SYSTEM LEVELS OF An error occurs in the recovery storage
QUALIFICATION. DEFAULT OF 1 USED subsystem that has caused the peer-to-peer
Explanation: In the SYSCATnn member of remote copy pair to be suspended at the time
SYS1.NUCLEUS, the field that defines the system indicated. The primary volume storage control
levels of qualification is incorrect. Valid values are 01, continues to keep track of changed cylinders,
02, 03, 04, F1, F2, F3, F4, or 40. (The last five values such that after the error is corrected, you can
are EBCDIC codes for decimal 1, 2, 3, 4, and blank.) select the correct reestablish method. If the error
is such that data may have been lost (for
System Action: The system continues processing, example, a physical secondary device error or
using the default of 1 as the level of qualification. the loss of NVS), after the error is corrected,
Operator Response: Issue MODIFY select the COPY option to reestablish the PPRC
CATALOG,ALIASLEVEL(n), where n is the number of pair.
levels of qualification requested by the system v SUSPENDED, COMMUNICATION-TO-
programmer. SECONDARY-FAILURE
System Programmer Response: To correct the field An error has been encountered in the
in the SYSCATnn member, ask the operator to issue a peer-to-peer remote copy communications paths,
MODIFY CATALOG,ALIASLEVEL(n) command. Provide such that the application site storage control for
a value for n to the operator. n is the number of levels the device indicated can no longer communicate
of qualification. The valid range for n is 1 through 4. with the target volume’s storage control. The
primary volume’s storage control continues to
Source: DFSMSdfp keep track of changed cylinders. When the error
is corrected, you may select the RESYNC option
to reestablish the PPRC pair.
v SUSPENDED, CRITICAL-STATE,
IEA491E volser-PPRC SUSPENDED error-reason, ALL-WRITES-FAILED
(PRI) SER=aaaa-bbbbb,CCA=xx (SEC)
A previous PPRC error has occurred on a
SER=aaaa-bbbbb,CCA=xx
volume established with the CRIT(YES)
parameter. A write I/O has occurred to the
[CONTINUATION OF IEA491E
volume indicated by the volume serial number
SNS=sense]
and it has been unit checked.
Explanation: The peer-to-peer remote copy operation v SECONDARY NOT READY,
has been suspended at the time indicated for the error
The secondary device of a PPRC pair has been
reason stated in the message.
suspended because the secondary device in the
pair is not ready. The primary volume storage

control continues to keep track of changed message has previously occurred.
cylinders. After the error is corrected, you may
select the RESYNC option to reestablish the
IEA492I SSID=subid,PARTITION=partition, text -
PPRC pair.
action
(PRI) SER=aaaa-bbbbb,CCA=xx
Explanation: The capacity manager has detected a
This is the primary PPRC volume storage control
capacity status change for a device configured in the
serial number followed by the primary volume’s
specified partition, either from normal status to abnormal
channel connection address. The reported serial
status or from abnormal status to normal status.
number can be one of the following:
v aaaa — The first four bytes of the storage In the message text:
control serial number. subid
v bbbbb — The last five bytes of the 12-byte The subsystem identifier of the subsystem to which
sequence number portion of the serial number. the device is configured.
This number can be found on the lower left-hand
portion of the storage control operator panel. partition
The partition identifier where the device is
v xx — The two-byte channel connection address. configured.
(SEC) SER=aaaa-bbbbb,CCA=xx text
This is the PPRC secondary volume’s storage One of the following:
control serial number followed by the secondary v CAPACITY USAGE IS BELOW percent%
volume’s channel connection address. The reported v CAPACITY USAGE IS ABOVE percent%
serial number can be one of the following:
v aaaa— The first four bytes of the storage control action
serial number. One of the following:
v DFHSM CALLED FOR device-number,volser
v bbbbb — The last five bytes of the 12-byte v DFHSM NOT INSTALLED
sequence number portion of the serial number. v DFHSM NOT ACTIVE
This number may be found on the lower v DFHSM CALL FAILED
left-hand portion of the storage control operator
panel. System Action: If the device capacity status becomes
v xx — The two-byte channel connection address. abnormal, the system attempts to invoke DFHSM to
migrate the data off the volume. No action is taken if the
sense device capacity status becomes normal.
Sense data.
Operator Response: If the error message persists or
System Action: Unless CRIT(YES) has been if the attempt to call DFHSM is not successful, contact
specified when the PPRC pair was established, the the IBM Support Center.
processing continues in suspended state.
Source: DFSMShsm
Based on the specific error reason, the primary volume
storage control continues to keep track of changed
cylinders, such that after the error is corrected, you may IEA493I NIP CONSOLE NOT FOUND
select the RESYNC option to reestablish the PPRC pair. Explanation: No suitable nucleus initialization program
However, depending on the nature of the error, if there (NIP) console has been found. This message is
is a possibility that data has been lost on the secondary accompanied by wait state code X'007'.
subsystem or device, the recovery action requires a full
copy after the problem has been fixed and the PPRC System Action: The system logs this message before
pair reestablished. loading non-restartable wait state X'007'.
Operator Response: The system issues this message Operator Response: Follow the operator response for
because of a hardware error. Follow your installation’s wait state X'007'.
procedures for reporting this error. System Programmer Response: Follow the system
Application Programmer Response: This is a programmer response for wait state X'007'.
hardware problem. Contact your hardware support Source: Communications task (COMMTASK)
personnel.
Detecting Module: IEAVNPCA
Note: Disaster and recovery protection is exposed until
this error is corrected and the PPRC pair is
reestablished.
Problem Determination: Note that in the case of the
“Critical State” message, the actual error causing the

approximately two minutes. Contact your hardware
IEA494I dev, volser, PPRC state, SSID=ssid,
support group if assistance is required to set the bit and
CCA=ca, optional-text
duration.
Explanation: The state of the PPRC pair has
changed. This message (with the exception of the SUSPENDING
state variation) will be broadcast to all subsystems
where the device is attached and online. Some systems
dev may receive more than one variation of the
The device number of the primary device of a SUSPENDING and/or SUSPENDED state message
PPRC pair. during a suspending event.
volser System Action: If no action is taken by the operator
The volume serial number of the primary device of or automation program , at the end of the EXTENDED
a PPRC pair. LONG BUSY period, processing will continue in
suspended duplex state
state
The new state of the PPRC pair is one of the Note: See message IEA491E for additional information
following: related to this message. Message IEA494E will be
detected and issued by only one of the systems where
SUSPENDING
the device is attached.
The control unit is in the process of suspending
the PPRC pair. This text appears only when Operator Response: This message is intended for
the device is in the extended long busy state, use by automation programs that monitor operator
and EXTENDED LONG BUSY STATE will messages. Actions may be attempted by the operator,
appear at the end of the message. but an automation program is recommended.
SUSPENDED Source: DASD device initialization/re-initialization
The PPRC pair has changed from PENDING
Detecting Module: IECCINIT
or FULL DUPLEX state to SUSPENDED state.
If the device is in the extended long busy state,
the message will have the optional text IEA495I dev, volser, DUAL COPY PAIR state,
EXTENDED LONG BUSY STATE appended at SSID=ssid, CCA=ca, optional-text
the end.
Explanation: The state of the dual copy pair has
TERMINATED changed.
The PPRC pair has terminated from the
PENDING, FULL DUPLEX, or SUSPENDED In the message text:
state. dev
PAIR PENDING The device number of the primary device of a dual
A PPRC copy operation is starting. This may copy pair.
be initial or from a previous suspended state. volser
PAIR FULL DUPLEX The volume serial number of the primary device of
A PPRC copy operation has completed and the a dual copy pair.
primary and secondary devices are state
synchronized. The new state of the dual copy pair is one of the
ssid following:
The ssid of the primary device of the PPRC pair. FULL DUPLEX
ca The two-byte channel connection address of the The copy of the primary device of the dual
primary device of the PPRC pair. copy pair to secondary is complete and the
primary to secondary devices are
optional-text synchronized.
EXTENDED LONG BUSY STATE.
TERMINATED
The dual copy pair has been terminated from
Note: The optional text is present only if the PPRC
the PENDING, FULL DUPLEX, or
control unit microcode is at the correct level and the
SUSPENDED state.
Vital Product Data bit has been set at the control unit
panel, requesting activation of extended long busy PENDING
mode. The duration of this extended long busy is also A dual copy operation is starting or restarting.
set at the control unit panel, with a default value of The primary and secondary devices are not
synchronized yet.

SUSPENDED volser
The dual copy pair has changed from the The volume serial number of the primary device of
PENDING or FULL DUPLEX state to the a mirrored pair.
FAILED or SUSPENDED state.
state
ssid The new state of the mirrored pair is one of the
The ssid of the primary of the dual copy pair. following:
ca The two-byte channel connection address of the OPERATIONAL
primary device of the dual copy pair. The copy of the primary of a mirrored pair to
secondary is complete, and the primary to
optional-text
secondary devices are synchronized.
The state of the original; one of the following:
PENDING
ORIGINAL ON PRIMARY
Mirrored operation is starting or restarting. The
The original device address is on the primary
primary and secondary devices are not yet
device address (no mapping to the primary
synchronized.
device).
FAILED
ORIGINAL NOT ON PRIMARY
The mirrored pair has been terminated from
The original device address is not the primary
the PENDING or OPERATIONAL state.
device address. The controller is mapping to
the primary device. ssid
The ssid of the primary of the mirrored pair.
Note: The optional text is present if the state of the dual
ca The two-byte channel connection address or the
copy pair is FAILED or SUSPENDED.
primary device of the mirrored pair.
Operator Response: The various formats of the
Operator Response: The various formats of the
IEA495I message will be broadcast to all systems
IEA496I message will be issued when the system
where the primary device of the dual copy pair is
detects a change of state for an online primary device
attached and online. Follow your installation’s
of a mirrored pair. Follow your installation’s procedures
procedures for reporting this error.
for reporting this error.
This message is intended to supplement message
Note: Automation programs that monitor operator
IEAD475E which will only be issued on one console of
messages may want to monitor for the occurrence of
a multiple system complex where the dual copy devices
these messages to assist with decisions concerning the
are attached to more than one of the systems.
availability of critical data.
Automation programs that monitor operator messages
may want to monitor for the occurrence of these Source: DASD device initialization/re-initialization
messages to assist with copy operations.
Find message IEA475E and refer to the text for that
message to determine the system action. If the device
IEA500A RESTART INTERRUPT DURING
associated with this message is attached via the
{jobname stepname|UNKNOWN
IBM3990 Model 3 or Model 6 Storage Control Unit, see
JOBNAME} ASID=aaaa MODE=mmmm
the IBM 3990/9390 Operations and Recovery Guide for
PSW=psw REPLY RESUME TO
detailed recovery actions.
RESUME INTERRUPTED PROGRAM
Source: DASD device initialization/re-initialization REPLY ABEND TO ABEND
INTERRUPTED PROGRAM [PREVIOUS
REPLY WAS INVALID, ENTER A VALID
REPLY]
IEA496I dev, volser, MIRRORING state,
Explanation: When the operator caused a restart
SSID=ssid, CCA=ca
interruption, the specified job was in progress. The
Explanation: The state of the mirrored pair has message asks the operator to resume the job that was
changed. in progress or end it.
dev jobname
The device number of the primary device of a The name of the job that the system was
mirrored pair. currently processing.

stepname [NO BATCH JOBS OR TIME SHARING USERS
The name of the step that the system was FOUND | RECOMMEND YOU DISPLAY ACTIVE AND
currently processing or blanks. DISPLAY QUEUES]
The system found no batch jobs or time sharing
UNKNOWN JOBNAME
users. However, there may be started tasks in the
The system could not identify the current job.
system.
ASID=aaaa
System Action: The system issues message
The address space identifier (ASID)
IEE125A. The system waits for the operator to reply to
MODE=mmmm message IEE125A. Then the system begins restart
The system was processing one of the processing.
following units of work:
Operator Response: Reply to message IEE125A.
TASK A task Depending on the message text, one of the following:
SRB A service request [WRITE-TO-OPERATOR BUFFER LIMIT EXCEEDED.
ISSUE K M,MLIM COMMAND TO RAISE LIMIT]
WAIT The system wait task Enter the CONTROL M,REF command to display
* A unit of work other than those listed the limit. Enter the CONTROL M,MLIM=nnnn
above command to raise the limit.
PSW=psw [NO BATCH JOBS OR TIME SHARING USERS

The program status word (PSW) at the time of FOUND | RECOMMEND YOU DISPLAY ACTIVE AND
the restart interruption DISPLAY QUEUES]
Enter the DISPLAY ACTIVE and/or the DISPLAY
System Action: The system prompts the operator for QUEUE command to determine if the system is
a reply. holding a job queue.
Operator Response: Reply one of the following: Source: Loadwait/Restart
RESUME Detecting Module: IEAVEREX
The job that was in progress continues at the
next sequential instruction.
IEA502A RESTART REASON COULD NOT BE
ABEND OBTAINED. REPLY WITH RESTART
The system ends the job with abend X'071'. REASON CODE:
Source: Loadwait/Restart Explanation:
Detecting Module: IEAVEREX 0 - ABEND CURRENT PROGRAM
1 - PERFORM MVS SYSTEM DIAGNOSTICS
IEA501I SYSTEM NON-DISPATCHABILITY [PREVIOUS REPLY WAS INVALID, ENTER A VALID

INDICATOR [IS OFF | WAS ON, IS NOW REPLY]
BEING RESET] [WRITE-TO-OPERATOR
BUFFER LIMIT EXCEEDED. ISSUE K Following a restart interruption, the system could not
M,MLIM COMMAND TO RAISE LIMIT] obtain the restart reason code from the service
[NO BATCH JOBS OR TIME SHARING processor.
USERS FOUND RECOMMEND YOU
DISPLAY ACTIVE AND DISPLAY System Action: The system issues message IEA501I.
QUEUES] The system waits for the operator to reply.
Explanation: The operator caused a restart Operator Response: Reply one of the following:
interruption, specifying REASON 1. This message
0 The system responds with message IEA500A,
displays the results of the diagnostics that the system
which allows you to abnormally end the current
performs in response to the restart interruption.
program.
1 The system checks and repairs critical data
SYSTEM NON-DISPATCHABILITY INDICATOR [IS areas.
OFF | WAS ON, IS NOW BEING RESET]
Source: Loadwait/Restart
If the non-dispatchability indicator is on, the system
sets it off and marks all address spaces as Detecting Module: IEAVEREX
dispatchable.
[WRITE-TO-OPERATOR BUFFER LIMIT EXCEEDED.
ISSUE K M,MLIM COMMAND TO RAISE LIMIT]
The write to operator (WTO) message buffer is full.

IEA503W MULTIPLE CPUS FAILED DURING ETR
SYNC-CHECK PROCESSING. Detecting Module: IEAVN615
Explanation: At least two processors could not
complete External Time Reference (ETR) IEA510A LNKLST PROCESSING IS
synchronization check processing. A hardware failure INOPERATIVE, HIT ENTER TO
occurred. ETR is the MVS generic name for the IBM CONTINUE WITH THE DEFAULT
Sysplex Timer (9037) or equivalent. LNKLST OR RE-IPL THE SYSTEM
System Action: The system enters nonrestartable Explanation: The nucleus initialization program (NIP)
wait state X'0A4'. detected unrecoverable errors during the initialization of
the LNKLST function. The LNKLST function cannot
operate because of the errors. In most cases, the
wait state X'0A4'.
system an accompanying diagnostic message identifies
System Programmer Response: See the system the specific type of error.
programmer response for wait state X'0A4'.
System Action: NIP does not initialize the LNKLST
Source: Timer supervision function. Initialization processing waits for your
response.
Detecting Module: IEATESCH, IEATESC2
about this message and any accompanying diagnostic
IEA504I CONSOLxx HARDCOPY DEVICE dddd
message. To continue initialization with the default
NOT ACCEPTED. OPERLOG IS
LNKLST, press ENTER. Otherwise, IPL the system
ACCEPTED. REASON=reason-code
again.
Explanation: The hardcopy console specified in the
Application Programmer Response: To correct the
CONSOLxx parmlib member is not valid. Because the
condition that caused the problem, respond to the
operations log was also specified, it will receive the
accompanying diagnostic message, then reIPL the
hardcopy message set.
system.
xx The suffix of the CONSOLxx parmlib
member.
IEA512W h.IODFxx IS NOT VALID. SUFFIX
dddd The device number of the console. RANGE IS ‘00’ THRU ‘FF’.
reason-code The reason code, as follows: Explanation: The specified input/output definition file
(IODF) suffix is not a valid hexadecimal number.
1 dddd is not a console. The
CONSOLE statement In the message text:
defining the device as a
h The high level qualifier of the IODF data set
console might be missing.
name (DSN).
2 dddd is not a valid device
xx The suffix of the IODF DSN.
number.
System Action: The system ends initialization. The
3 dddd is a display console. A
system enters nonrestartable wait state X'0B1' with
display console cannot be
reason code X'008'.
used as a hardcopy device.
System Action: The system ignores the request for a
programmer response for wait state X'0B1'.
hardcopy console and continues processing. The
system logs messages to the operations log only. Source: Input/output supervisor (IOS)
System Programmer Response: Before the next Detecting Module: IEAIPL43
system initialization, ensure the following:
v The device number is the same in both the I/O IEA513W DATASET NOT FOUND ON DEVICE
definition file (IODF) and the CONSOLE statement in dev: dsname
Explanation: The system cannot find a data set name
v The device type is the same in both the IODF and
because one of the following conditions exists:
the CONSOLE statement in the CONSOLxx parmlib
member. v The device number is incorrect
v A hardcopy device is defined as a console (not a v The wrong LOADxx suffix was entered in the load
display console) in CONSOLxx. frame parameter

In the message text: System Action: The system ends initialization. The
dev
reason code X'003'.
The device number.
dsname
The data set name. It is one of the following:
v SYS1.PARMLIB Source: Input/output supervisor (IOS)
v h.IODFxx, where h is the high level qualifier. Detecting Module: IOSIOFR
system enters nonrestartable wait state X'0B1' with IEA516W MODIFY SUBCHANNEL FAILED FOR
reason code X'001'. DEVICE NUMBER dev
Operator Response: Do one of the following: Explanation: During system initialization, the Modify
v If the data set name is SYS1.PARMLIB, correct the Subchannel (MSCH) instruction failed while the system
IPL device number or enter the correct device was trying to enable a device.
number for the parmlib member in the IPL load In the message text:
parameter.
dev
v If the data set name is h.IODFxx, enter the correct
The device number.
LOADxx suffix in the in the IPL load parameter.
If the data set name is not one of the above, notify the system enters nonrestartable wait state X'0B1' with
system programmer. reason code X'004'.
System Programmer Response: See the system System Programmer Response: See the system
programmer response for wait state X'0B1' with reason programmer response for wait state X'0B1'.
code X'001'.
Detecting Module: IOSIOFR
Detecting Module: IOSIOFR
IEA517W IODF IS NOT VALID FOR AN IPL
IEA514W MORE THAN ONE EXTENT FOR
dsname
found an incorrect I/O definition file (IODF) data set
Explanation: A data set in the LOADxx parmlib name in the LOADxx parmlib member.
member occupies more than one extent.
In the message text: system enters nonrestartable wait state X'0B1' with
reason code X'005' or X'00A'.
dsname
The data set name. System Programmer Response: See the system
system enters nonrestartable wait state X'0B1' with Source: Input/output supervisor (IOS)
reason code X'002'.
IEA518W CONFIGURATION ID xxxxxxxx NOT
Source: Input/output supervisor (IOS) FOUND IN IODF.
Detecting Module: IOSIOFR Explanation: During system initialization, the system
could not find the configuration identifier from the
LOADxx parmlib member in the I/O definition file
IEA515W DEVICE NUMBER dev NOT DEFINED
(IODF).
TO THE CHANNEL SUBSYSTEM
could not find a subchannel for the device that contains xxxxxxxx
the parmlib member. The configuration identifier.
In the message text: System Action: The system ends initialization. The
dev
reason code X'006'.
The device number.

programmer response for wait state X'0B1'. num
The number of devices.
System Action: System initialization continues. The
system does not recognize any devices of the specified
device type.
IEA519I IODF DSN = dsname
Explanation: This message identifies the I/O definition reporting data bases for a fix for the problem. If no fix
file (IODF) data set name. exists, contact the IBM Support Center.
In the message text: Source: Input/output supervisor (IOS)
dsname Detecting Module: IEAIPL71

The data set name.
System Action: System initialization continues. IEA522I UIM modname DID NOT BUILD A DFT
FOR DEVICE NUMBER dev
System Programmer Response: If the IODF data set
name is incorrect, enter the correct name in the Explanation: A unit information module (UIM) did not
LOADxx parmlib member. Then ask the operator to build a device features table (DFT) for the specified
reIPL the system. device number. The device type is not supported by the
system level.
modname
The name of the UIM.
IEA520I CONFIGURATION ID = xxxxxxxx. IODF
DEVICE NUMBER = dev dev
The device number.
Explanation: This message identifies the configuration
identifier and the I/O definition file (IODF) device System Action: System initialization continues. The
number. system does not recognize the device types defined by
the UIM.
xxxxxxxx reporting data bases for a fix for the problem. If no fix
The configuration identifier. exists, contact the IBM Support Center.
dev Source: Input/output supervisor (IOS)
The device number.
System Action: System initialization continues.
Operator Response: If the IODF device number is IEA523W NO DEVICES DEFINED
incorrect, enter the correct IODF device number in the
IPL load parameter. Then reIPL the system. If the Explanation: The system cannot recognize any of the
problem persists, contact the system programmer. devices defined in the I/O definition file (IODF). This
error occurred for one of the following reasons:
System Programmer Response: If the configuration
identifier is incorrect, enter a different configuration v The IODF does not contain any devices defined to
identifier in the LOADxx parmlib member. Then ask the the system.
operator to reIPL the system. v The unit information modules (UIM) supporting these
devices are not present.
System Action: System initialization ends. The system
Detecting Module: IEAIPL43 enters nonrestartable wait state X'0B2'.
IEA521I devtype DEVICE TYPE NOT programmer response for wait state X'0B2'.
RECOGNIZED (num DEVICES)
Explanation: The system could not find a valid unit
information module (UIM) for the specified device type.
IEA525W UIM modname SPECIFIED UNDEFINED
In the message text: DEVICE NUMBER dev
devtype Explanation: A user interaction module (UIM) asked to
The device type. use the device class extension of the unit control block
(UCB) for a device. The system did not build a UCB for

that device because of a logic error in the UIM.
IEA540I taskname TASK FAILED - RESTART
In the message text: ATTEMPT IN PROGRESS.
modname Explanation: taskname is one of the following:

The unit information module (UIM). ADDRESS SPACE TERMINATION
DUMP
dev RECORD
The device number.
System Action: System initialization ends. The system One of the permanent tasks in the recovery termination
enters nonrestartable wait state X'0B4'. manager (RTM) failed.

ADDRESS SPACE TERMINATION
The RTM address space failed.
Detecting Module: IOSIUCB
DUMP
The RTM dump task failed.
IEA526I SYSNAME SYSTEM PARAMETER
RECORD
INVALID
The RTM recording task failed.
Explanation: During system initialization, the nucleus
System Action: One of the following:
initialization program (NIP) found an incorrect
SYSNAME parameter. The incorrect SYSNAME v If the task was not attempting to restart when it failed,
parameter was specified in either an IEASYSxx or RTM issues this message. RTM attempts to restart
IEASYMxx parmlib member or by the operator in the task.
response to message IEA101A. v If the task was attempting to restart, RTM also issues
message IEA541E. RTM does not try to restart the
System Action: The system issues message IEA527A
task.
to prompt the operator for a reply.
Operator Response: Enter SYSNAME=sysname,
where sysname is a valid system name, in reply to Detecting Module: IEAVTMS1
message IEA527A.
System Programmer Response: Correct the IEA541E taskname TASK FAILED DURING
SYSNAME system parameter in the IEASYSxx or RESTART ATTEMPT.
IEASYMxx parmlib member used to IPL the system.
Explanation: taskname is one of the following:
Source: System initialization (IPL/NIP) ADDRESS SPACE TERMINATION
DUMP
Detecting Module: IEAVNPCF
RECORD
IEA527A SPECIFY REQUIRED SYSNAME One of the permanent tasks in the recovery termination
PARAMETER. SYSNAME= manager (RTM) failed. This task had failed previously
and was attempting to restart when a second error
occurred.
name in the SYSNAME parameter is incorrect or
missing.
the correct SYSNAME.
Operator Response: Enter SYSNAME=sysname,
DUMP
where sysname is one to eight characters, each of
The RTM dump task failed.
which is a alphanumeric or national character. The
name that is chosen should uniquely identify the system RECORD
that is being IPLed. The RTM recording task failed.
System Programmer Response: Add or correct the System Action: The system does not try to restart the
SYSNAME parameter in the IEASYSxx or IEASYMxx task. The task’s function will not be available until the
parmlib member used to IPL the system. system is initialized again.
Source: System initialization (IPL/NIP) Operator Response: ReIPL the system.
Detecting Module: IEAVNPCF Source: Recovery termination manager (RTM)

Detecting Module: IEAVTMSI cccc The error code. It is the same as would have
been displayed in message IEA367A.
IEA542I taskname TASK RESTART COMPLETED System Action: The system enters restartable wait
SUCCESSFULLY. state X'202'.
Explanation: taskname is one of the following: Operator Response: See the operator response for
ADDRESS SPACE TERMINATION wait state X'202'.
DUMP
RECORD
programmer response for wait state X'202'. See
message IEA367A for a description of error codes.
One of the permanent tasks in the recovery termination
manager (RTM) failed, but restarted itself. Source: Communications task (COMMTASK)
IEA546E NO FULL CAPABILITY MCS
CONSOLES, REASON=xxxx TO
DUMP RESTORE MASTER CONSOLE: PRESS
The RTM dump task failed. THE ENTER KEY ON ANY AVAILABLE
FULL CAPABILITY CONSOLE AND
RECORD PRESS THE EXTERNAL INTERRUPT
The RTM recording task failed. KEY OR ISSUE VARY CONSOLE OR
System Action: The task is now available for CONTROL V COMMAND TO RESTORE
processing. A FULL CAPABILITY CONSOLE.
Source: Recovery termination manager (RTM) Explanation: Console switch processing results in loss
of all the full capability multiple console support (MCS)
Detecting Module: IEAVTSDT, IEAVTMTC, consoles. The failing console’s undelivered (UD)
IEAVTR2S, IEAVTRET messages will be re-routed to consoles with the UD
attribute or a console with master authority. The system
IEA544I EXTERNAL INTERRUPT IGNORED. [NO will send other messages to the hard-copy log.
FULL CAPABILITY CONSOLES In the message text:
DEFINED OR] MASTER CONSOLE WAS
VARIED OFFLINE. REASON=xxxx Communications task (COMMTASK)
lost all the full capability MCS
Explanation: The system did not process an external consoles. xxxx is one of the following:
interrupt.
EXT The operator pressed the
In the message text: external interrupt key.
NO FULL CAPABILITY CONSOLES DEFINED IOER An I/O error occurred on the
No full capability consoles are defined in the failing console.
SWER A software error occurred for
MASTER CONSOLE WAS VARIED OFFLINE the failing console.
The master console was varied offline.
VMST The operator entered the
System Action: The system assigns the specified VARY MSTCONS command.
name to the console. The system continues processing.
OPER An open failure occurred for
Source: Communications task (COMMTASK) the console.
Detecting Module: IEAVMQWR CF CHP
The operator entered a
IEA545W MULTIPLE CONSOLE SUPPORT CONFIG CHP command.
INOPERATIVE MESSAGE IEA367A CQEER
COULD NOT BE DISPLAYED ERROR CQE error for a console.
CODE = cccc
SFAIL A system in the sysplex
Explanation: Multiple console support (MCS) is failed.
inoperative. The system tried to display message
IEA367A, but failed. System Action: The system continues processing.
Consoles with the UD attribute or the system console
In the message text: receive the failing console’s undelivered messages. If

there are no other consoles with the UD attribute name to the console. The system continues processing.
(including the hard-copy log), the system sends the
failing console’s UD messages to the system console.
The system sends all other messages to the hard-copy Detecting Module: IEAVN701
log.
Operator Response: Do one of the following: IEA554I CONSOLE DELAYED SVC
v If there are active consoles with the UD attribute but PROCESSING SUSPENDED. RESTART
there is no MCS console with master authority, you {PENDING | SUCCESSFUL}
may restore master console authority to a console or Explanation: The system is delaying message
do nothing. processing because of errors.
v If both the MCS console with master authority and
consoles with the UD attribute are not active, you In the message text:
may restore master console authority to a console or PENDING
activate a console with the UD attribute. If you do not The restart is pending.
do so, the system will send undeliverable action
messages, write to operator with reply messages SUCCESSFUL
(WTOR) and messages with descriptor code 12 to The restart was successful.
one of the following: System Action: The system tries to restart message
– The hard-copy log, if directed to the hard-copy log processing. If SUCCESSFUL appears in the message
– The system console text, the restart was successful.
Source: Communications task (COMMTASK) Source: Communications task (COMMTASK)
Detecting Module: IEAVSWCB, IEAVSWCR

IEA555E CONSOLE DELAYED SVC
PROCESSING ABORTED. RESTART
IEA548W NIP CONSOLE UNAVAILABLE. UNSUCCESSFUL
INITIALIZATION CANNOT PROCEED.
FAILING MESSAGE: text Explanation: The system is delaying message
processing because of errors.
Explanation: During initialization, a console was not
available. The system must issue a write to operator System Action: The system does not display
with reply (WTOR) or emergency message. branch-entered write to operator with reply (WTOR)
messages. The system storage may become filled with
In the message text: messages waiting to be issued.
text The first 8 lines of the message which could Operator Response: ReIPL the system when it is
not be delivered. convenient.
System Action: The system enters nonrestartable Source: Communications task (COMMTASK)
wait state X'A70'.
Operator Response: ReIPL when the system console IEA557A MULTIPLE REQUESTORS FOR REPLY
is available. ID 0, REPLY TO ID 0 ON sysname
System Programmer Response: See the system Explanation: An authorized program issued a write to
programmer response for wait state X'A70'. operator with reply (WTOR) message while access to a
Source: Communications task (COMMTASK) global reply identifier pool was restricted. Another
program is using reply identifier 0.
IEA549I SYSTEM CONSOLE FUNCTIONS In the message text:

AVAILABLE SYSTEM CONSOLE NAME sysname
ASSIGNED consname The name of the system on which the
Explanation: The system initialized the system authorized program is running.
console as an extended console. The console is now System Action: The program that issued the WTOR
available for message and command processing. waits until a reply identifier becomes available.
In the message text: Operator Response: Reply to the WTOR as soon as
consname possible.
The name the system assigns to the system Source: Communications task (COMMTASK)
console.
System Action: The system assigns the specified

IEAVMXIT ABENDED
IEA590I WTO USER EXIT text
Enter the CONTROL M,UEXIT=N command to
Explanation: text is one of the following: delete the erroneous IEAVMXIT routine, then enter
exit-name ABENDED the CONTROL M,UEXIT=Y command to activate
IEAVMXIT ABENDED the corrected IEAVMXIT routine.
IEAVMXIT NOT FOUND
IEAVMXIT NOT FOUND
IEAVMXIT NOT LOADED - NO STORAGE
Place the installation exit routine, IEAVMXIT, in a
AVAILABLE
system library in the LNKLST concatenation.
An error occurred during the initialization or running of a IEAVMXIT NOT LOADED - NO STORAGE
WTO installation exit routine. AVAILABLE
Increase the storage in the common service area
In the message text: (CSA) by changing the CSA specification in the
SYSP parameter. Then reenter the CONTROL M
exit-name ABENDED command to activate the installation exit.
The WTO installation exit abnormally ended. The
system marked it as nonexecutable. Source: Communications task (COMMTASK)
In the message text: Detecting Module: IEAVVINT, IEAVX600
exit-name
The name of the installation exit. IEA598I TIME ZONE = d.hh.mm.ss
IEAVMXIT ABENDED Explanation: This message displays the time zone,

The general WTO installation exit routine which is the difference between local time and
abnormally ended. The system marked it as Greenwich mean time (GMT).
nonexecutable.
IEAVMXIT NOT FOUND
d The location of the time zone in relation to
The system could not load installation exit routine
GMT, as follows:
IEAVMXIT from any system library.
E A time zone east of GMT.
IEAVMXIT NOT LOADED - NO STORAGE
AVAILABLE W A time zone west of GMT.
Storage was requested for the general WTO
hh.mm.ss
installation routine IEAVMXIT, but the storage was
The difference in hours (00-15), minutes
not available.
(00-59), and seconds (00-59) from GMT.
System Action: The system action is one of the
following:
System Programmer Response: If the time zone
exit-name ABENDED
value is unacceptable, specify a different value in the
The system abnormally ends user exit exit-name.
CLOCKxx parmlib member.
IEAVMXIT ABENDED
The system abnormally ends installation exit
IEAVMXIT. Detecting Module: IEAVNP20
IEAVMXIT NOT FOUND
The system does not process the CONTROL M IEA599I CLOCKxx LINE nnnn: text STMT
command. IGNORED. UNRECOGNIZED PARM.
IEAVMXIT NOT LOADED - NO STORAGE Explanation: A statement in a CLOCKxx parmlib
AVAILABLE member contains an incorrect parameter.
The system does not process the CONTROL M
command. In the message text:
Operator Response: Contact the system programmer. CLOCKxx

error messages as follows: nnnn The line number in the CLOCKxx parmlib
member that contains the ignored statement.
exit-name ABENDED
Enter the SET MPF=NO command to remove the text The statement that contains the incorrect
erroneous exit routine, then enter the SET MPF parameter.
command to invoke a correct WTO installation exit. System Action: The system ignores all CLOCKxx

parmlib members. The system issues message CLOCKxx
IEA906A. The parmlib member, with the suffix xx.
Operator Response: Reply to message IEA906A. If nnnn The line number in the CLOCKxx parmlib
you press the enter button on the console, the system member that contains the duplicate statement.
sets the following defaults:
text The duplicate statement.
v The system does not prompt the operator during
time-of-day (TOD) initialization. System Action: The system ignores the duplicate
statement. The system continues processing.
v The system sets the local time equal to the
Greenwich mean time (GMT). System Programmer Response: Remove the
duplicate statement from CLOCKxx
System Programmer Response: Check for
misspelled parameters in the CLOCKxx parmlib member Source: Timer supervision
from the specified keyword to the end.
Detecting Module: IEAVNP20 IEA602I ADDRESS SPACE CREATE FAILED.
text
IEA600I CLOCKxx LINE nnnn: TIMEZONE STMT Explanation: A request to create a new address
IGNORED. VALUE NOT VALID. space could not be honored because of an error or a
resource limitation.
Explanation: A TIMEZONE statement in the CLOCKxx
parmlib member contains an incorrect specification: In the message text:
v The syntax of the statement is incorrect text
v The value is outside the correct range (00.00.00 - One of the following:
15.00.00 hours).
THE GETMAIN FOR THE ASCB FAILED
Storage could not be obtained from SQA for
the new address space’s ASCB or ASSB.
CLOCKxx
MAXUSERS WOULD HAVE BEEN EXCEEDED
The maximum number of allowable address
nnnn The line number in the CLOCKxx parmlib spaces as specified in the MAXUSER
member that contains the ignored statement. parameter in the IEASYSxx parmlib member.
System Action: The system ignores all CLOCKxx ADDRESS SPACE SERVICES FAILED
parmlib members. The system issues message Address space services suffered an error
IEA906A. which prevented the address space creation.
Operator Response: Reply to message IEA906A. If A STORAGE SHORTAGE EXISTS
you press the enter button on the console, the system There is insufficient SQA, pageable storage, or
sets the following defaults: auxiliary storage available.
v The system does not prompt the operator during AN UNEXPECTED ERROR OCCURRED
time-of-day (TOD) initialization. An unexpected error occurred which prevented
v The system sets the local time equal to the the address space creation.
Greenwich mean time (GMT).
System Action: The system was unable to create the
System Programmer Response: Check for requested new address space. The system continues
misspelled parameters in the CLOCKxx parmlib processing without the new address space.
member. Ensure that the value for TIMEZONE is within
Operator Response: Notify the System Programmer.
the valid range (00:00:00 - 15:00:00).
System Programmer Response: Resolve the
resource shortage if the problem is a shortage of SQA,
Detecting Module: IEAVNP20 auxiliary storage, or MAXUSERs. For the unexpected
error cases, check the logrec data set for an error
record or retry the request.
IEA601I CLOCKxx LINE nnnn: DUPLICATE text
STMT IGNORED Source: Supervisor control
Explanation: A statement in the CLOCKxx parmlib Detecting Module: IEAVEMRQ
member is a duplicate.

IEA603I NO UCBS BUILT FOR nnnnn 4-DIGIT IEA611I {COMPLETE|PARTIAL} DUMP ON
DEVICES FOUND IN THE IODF dsname
Explanation: Initial program load (IPL) completed
text
successfully but the system has encountered nnnnn
4-digit devices. Explanation: Where text is:
DUMPID=dumpid REQUESTED BY JOB (jobname)
In the message text: FOR ASIDS(id,id,...)
[REMOTE DUMPS REQUESTED|
nnnnn The number of 4-digit devices encountered. REMOTE DUMP FOR SYSNAME: sysname]
INCIDENT TOKEN: incident-token
System Action: Processing continues. No UCBs are [SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz]
[reason-text]
built for the nnnnn 4-digit devices. [ERRORID = SEQ yyyyyy CPUzz ASIDasid
TIMEhh.mm.ss.t] [TSOID = tsoid]
Detecting Module: IEAIPL71 [ID = uuuuuuuuuu]
The system wrote a complete or partial SVC dump to

IEA607E THE DUMPSRV ADDRESS SPACE HAS an automatically allocated dump data set on a direct
FAILED AND CANNOT RESTART access storage device. In the message text:
Explanation: Errors occurred in dumping services, COMPLETE
which processes SVC dumps. The dumping services | The SVC dump contains all of the virtual storage
address space (DUMPSRV) has ended several times in | that was requested.
succession. Dumping services cannot do the following:
PARTIAL
v Give control to the post dump installation exit routine
| Not all of the virtual storage requested was
v Process a dump request | collected. However, enough storage may have
v Process a DUMPDS operator command | been dumped to allow the debugging of the
| problem to be successful. The codes in the SDRSN
SYS1.DUMPnn data sets that were added are no longer | field can be used to determine what storage was
allocated for dumps. These data sets could contain SVC | effected, or what problems were encountered while
dumps; do not delete these dump data sets. | SVC dump processing was executing.
System Action: The system continues processing with dsname

no SVC dumping capability. The dump was written to the data set named
dsname.
Operator Response: ReIPL the system to reinitialize
and restart the dumping services address space. dumpid
The 3-character dump identifier.
jobname
Detecting Module: IEAVTSDR The name of the job that requested the dump.
id The address space identifiers (ASID), in
IEA607I THE DUMPSRV ADDRESS SPACE HAS hexadecimal, for the address spaces included in
FAILED AND IS RESTARTING the dump.
Explanation: Errors occurred in dumping services, REMOTE DUMPS REQUESTED
which processes SVC dumps. The dumping services The SDUMPX macro or DUMP command that
address space (DUMPSRV) is ending. Dumping requested this dump also requested dumps on
services is running but cannot do the following: other systems in the sysplex.
v Process a dump request
REMOTE DUMP FOR SYSNAME: sysname
v Give control to the post dump installation exit routine This dump was requested by sysname, which is
v Process a DUMPDS operator command another system in the sysplex.
System Action: The system restarts the dumping INCIDENT TOKEN: incident-token
services address space. When the restart is complete, The formatted incident token for the dump.
complete dump processing is available again.
SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz
Source: Recovery termination manager (RTM) The system wrote only a partial dump.
Detecting Module: IEAVTSDR vvvvvvvv
Partial dump reason code. One of the
following:
80000000
A system request block (SRB) for the
dump could not be scheduled to the

requested address space. Either no hung address space, dump processing
current address space had the requested obtained only fixed storage for the address
ASID or the system was ending the space.
address space with that ASID.
80000000 | 40000000
40000000 While processing SVC X’33’, the system
SVC dump processing could not obtain detected an error and gave recovery
real storage manager (RSM) serialization control.
because of a hierarchy problem.
20000000
20000000 The system detected an error in the SVC
SVC dump processing could not obtain dump task and gave recovery control.
RSM serialization because of a RSM
10000000
control problem.
The SVC dump task failed.
10000000
08000000
SVC dump processing could not obtain a
The system detected an error while writing
central storage buffer from the real storage
a trace table. The system could not write
manager.
the trace table.
08000000
04000000 | 02000000
An error in scheduled SVC dump
While processing an SVC dump, the
processing caused recovery to receive
system detected an error and gave
control.
recovery control.
04000000
01000000
An error in summary dump processing
The started dump task failed.
caused recovery to receive control.
00800000
02000000
A task abnormally ended, and SVC dump
An error in summary dump processing or
processing took a partial dump. The
suspend summary dump processing
resource manager for SVC dump
caused recovery to receive control.
processing receives control.
00400000
00400000
An error caused the loss of the summary
The system detected an error in the SVC
dump.
dump writing task and gave recovery
00200000 control.
During suspend summary dump
00200000
processing, the virtual storage buffer filled
An address space involved in the dump
up.
abnormally ended, and SVC dump took a
00100000 partial dump. The resource manager for
No more summary dump data could be SVC dump processing receives control.
written because the central storage buffer
00100000
was full.
The DUMPSRV address space abnormally
00080000 ended, and SVC dump processing took a
While the system was writing a trace table, partial dump. The resource manager for
an error occurred. The trace table could SVC dump processing receives control.
not be written.
00080000
wwwwwwww While processing the dump header, the
Partial dump reason code. One of the system ran out of space to place data.
following:
00040000
00010000 During dump processing of local storage,
During dump processing of a possibly the system issued a PURGEDQ because
hung address space, the address was a hung address space was detected. This
found to be invalid. The dump data may will result in the loss of some storage
not be consistent. related to the address space.
00020000 00020000
During dump processing of a possibly During dump processing of a possibly

hung address space, dump processing 00100000
obtained only fixed storage for the address While dump processing was copying
space. global storage into a data space, an error
occurred.
00010000
During dump processing of a possibly 00080000
hung address space, the address space While dump processing was copying a
was found to be invalid. The dump data sub-range of common storage into a data
may not be consistent. space, an error occurred.
xxxxxxxx 00040000
Partial dump reason code. One of the An error occurred in the processing of data
following: spaces that were requested through the
LISTD keyword on the SDUMPX macro, or
80000000
through the DSPNAME parameter on the
While building the address range table for
DUMP command.
global storage areas, SVC dump
processing filled the table and remaining 00020000
entries could not be added. Dump processing could not add some
ranges of read/write storage to the range
40000000
table.
While building the address range table for
local storage areas, SVC dump processing 00010000
filled the table and remaining entries could SVC dump processing truncated the dump
not be added. because the maximum amount of space
was been reached.
20000000
While building the address range table, 00008000
SVC dump processing filled the table and While processing the SQA SDATA option,
remaining entries could not be added. the system filled in the range table.
10000000 00004000
While dump processing was writing to the While processing the CSA SDATA option,
dump data set, an I/O error occurred. the system filled in the range table.
Remaining entries could not be added.
08000000
The dump data set is full, but more data 00002000
needs to be dumped. While processing global subpools, the
system filled in the range table. Remaining
04000000
entries could not be added.
An error occurred while writing the
summary dump. 00001000
While processing the LSQA SDATA option,
02000000
the system filled in the range table.
An error occurred while dump processing
was obtaining trace data.
00000800
01000000
While processing the RGN SDATA option,
While dump processing was setting up the
service request block (SRB) under which
the dump was to be processed, an error
occurred. 00000400
While processing private subpools, the
00800000
system filled in the range table. Remaining
An error occurred in an exit routine.
00400000
00000200
An error occurred while writing the
While processing the SWA SDATA option,
end-of-data record to the dump data set.
00200000 Remaining entries could not be added.
Some read-only ranges of data could not
00000100
be added to the range table.
While copying global data into a data
space, dump processing was unable to
capture some ranges of global storage.

00000080 dump processing failed during suspend
An exit data space could not be created, summary dump processing, leaving the
or the data space was created but an caller suspended.
ALET could not be obtained to access the
10000000
data space.
IEAVTSDB released serialization for all
00000040 serialized structures specified in the
A summary data space could not be STRLIST because SDUMP appears to
created, or the data space was created but have failed or ended.
an ALET could not be obtained to access
08000000
the data space.
The central storage buffer containing the
00000020 summary dump was released when it was
A local data space could not be created, or determined that dump processing was
the data space was created but an ALET hung. The summary dump was lost.
could not be obtained to access the data
00800000
space.
Facility not available. Some structures will
00000010 not be dumped.
A global data space could not be created,
00400000
or the data space was created but an
The structure is not available for one of
ALET could not be obtained to access the
the following reasons:
data space.
v The system detected a structure failure
00000008 and the structure cannot be accessed
SVC dump could not create or could not v The structure is not allocated
use the data spaces that are required to
00200000
process the STRLIST request. Some data
No facility dump space is allocated or no
will not be included in the dump.
facility dump space is available because it
00000001 is being used to hold structure dump
SVC dump processing truncated the dump tables for other structure dumps
because a critical shortage of auxiliary
00100000
storage existed. See the information for
Possible error in STRLIST parameter list
message IRA201E to determine how to
for one of the following reasons:
relieve the shortage.
v The structure does not exist in the
zzzzzzzz active policy
Partial dump reason code. One of the v The structure type is not compatible
following: with the specified range options
v A lock structure was requested. SDUMP
Bits in the first byte indicate a result that
does not support lock structures
occurred because one or more of the
following conditions may exist- 00080000
a. there is a shortage of central storage b. Some or all of the STRLIST could not be
there is a shortage of auxiliary storage c. processed
the DUMPSRV address space dispatching
00040000
priority is too low
The system released structure dump
80000000 serialization before capturing all the data.
Dump processing had reset the system The system captured the rest of the data
dispatchable and dump processing failed after releasing serialization.
or ended, leaving the system set
00020000
non-dispatchable. dump was lost.
Recovery received control while
40000000 processing STRLIST
Dump processing had reset the tasks
00010000
dispatchable in one or more address
SVC dump was unable to continue
spaces involved in the SVC dump. Then
processing a structure requested in the
dump processing failed or ended, leaving
STRLIST parameter list. This may be
the tasks non-dispatchable.
because the operator deleted the structure
20000000 dump with the SETXCF FORCE
Dump processing reset the caller’s unit of command.
work, which was stopped as part of
suspend summary dump processing. Then

00008000 SOME STORAGE COULD NOT BE DUMPED
Recovery received control while building RC=rc
the SDUMP signals for other systems in Storage could not be dumped. rc can be one of
the sysplex the following:
reason-text 04 The system could not find the
One of the following: requested ASIDs.
SUMMARY DUMP INFORMATION WAS LOST 08 Not all of the data requested in a
A problem arose where processing was unable summary dump could be contained in
to complete a requested summary dump. Refer the central storage buffer or virtual
to the description of the SDRSN bits that are storage buffer.
set to determine whether the data was
truncated, or completely lost. | Note: Even though some summary
A CRITICAL AUXILIARY STORAGE SHORTAGE
| dump records may be missing,
EXISTED
| IEA611I COMPLETE DUMP
SVC dump processing truncated the dump
| will be issued when there are
because a critical shortage of auxiliary storage
| no other data truncation reason
existed. See message IRA201E to determine
| bits set. This indicates that the
how to relieve the shortage.
| dump contains all of the virtual
| storage requested. Only the
DUMP DATA SET FULL - DUMP ENDED WHILE | summary dump records are
WRITING | missing, and these are usually
{SUMDUMP|GLOBAL|LOCAL|STRLIST} | duplicated in the virtual storage
The dump data set is full, but more data needs | dumped at a slightly later time.
to be dumped. The message indicates at what
12 Either (1) the internal SVC dump
point the data set became full.
control blocks are full, so that some
I/O ERROR - NO EOF WRITTEN - DUMP ENDED data was not dumped, or (2) dump
WHILE WRITING processing received an error return
{SUMDUMP|GLOBAL|LOCAL|STRLIST} code when it tried to dump the system
An I/O error occurred while the system was trace.
writing to the dump data set. The message
16 SVC dump was not able to process all
indicates the system was dumping at the time
of the structures specified in the
of the I/O error.
STRLIST parameter list.
MAXSPACE LIMIT REACHED WHILE
20 SDUMP processing could not collect
CAPTURING DUMP
the local storage of at least one of the
Insufficient space was available to capture the
normally collected storage address
complete dump. See the MAXSPACE
spaces involved in the dump. Refer to
parameter of the CHNGDUMP SET,SDUMP
the description of the SDRSN bits that
command in OS/390 MVS System Commands.
are set for more information.
ERROR OCCURRED IN AN SDUMP EXIT
SYSTEM RESET DISPATCHABLE PRIOR TO
ERROR OCCURRED IN AN SDUMP LOCAL EXIT DUMP COMPLETION
Dump processing failed or ended with the
ERROR OCCURRED IN AN SDUMP GLOBAL
system set non-dispatchable. The system
EXIT
detected the error and reset dispatchable.
ERROR OCCURRED IN AN SDUMP EARLY
TASKS RESET DISPATCHABLE PRIOR TO
GLOBAL EXIT
DUMP COMPLETION
ERROR OCCURRED IN AN SDUMP Dump processing failed or ended with tasks set
ONE-TIME-ONLY EXIT non-dispatchable in one or more address
spaces involved in the SVC dump. The system
ERROR OCCURRED IN AN SDUMP DYNAMIC detected the error and reset the tasks
LOCAL EXIT dispatchable.
ERROR OCCURRED IN AN SDUMP DYNAMIC ENABLED CALLER RESET PRIOR TO DUMP
GLOBAL EXIT COMPLETION
Dump processing encountered an unexpected Dump processing failed or ended during
error in an SDUMP exit of the specified type. suspend summary dump processing, leaving
the caller suspended. The system detected the
error and reset the caller’s unit of work.

STRUCTURE DUMP SERIALIZATION RELEASED v Logrec error records
PRIOR TO DUMP COMPLETION v CHNGDUMP option settings
The SVC dump time disabled interruption exit v DUMPDS status
routine released dumping serialization that was v The partial SVC Dump
held for a structure requested in the STRLIST v Dump data set information
parameter list. Serialization was released
I/O ERROR - NO EOF WRITTEN - DUMP ENDED
because:
WHILE WRITING
v The routine had detected that SVC dump
{SUMDUMP|GLOBAL|LOCAL|STRLIST}
processing was not continuing normally or
Look at the logrec error records to determine the
had ended and left the structure serialized.
device problem. Contact hardware support.
v ACCESSTIME=ENFORCE was specified on
the dump request (or defaulted) and the Format the partial dump. If a previous dump was in
data requested in the STRLIST parameter the dump data set, the data set may contain a
list for a requested structure was not combination of the two dumps.
completely processed within the time limit
specified by the ACCESSTIME parameter on ERROR OCCURRED IN SDUMP
the IXLCONN macro. Obtain the logrec error record. Search the problem
reporting data bases for a fix for the problem. If no
ERROR OCCURRED IN SDUMP fix exists, notify the IBM Support Center. Provide
Dump processing encountered an unexpected the logrec error record.
error.
SOME STORAGE COULD NOT BE DUMPED RC=16
ERRORID = SEQyyyyyy CPUzz ASIDasid Refer to the description of the SDRSN bits that are
TIMEhh.mm.ss.t set. Use the IPCS Sub-Command STRDATA to
The error identifier. format the list of structures that was requested to
be dumped. The reason that the structures were
yyyyyy The sequence number
not completely processed will be displayed.
zz The central processor address
Source: SVC dump
asid The ASID for the address space
Detecting Module: IEAVTSDC
in which the error occurred
hh.mm.ss.t The time in hours (00 through
IEA630I OPERATOR opername NOW ACTIVE,
23), in minutes (00 through 59), in
SYSTEM=sysname, LU=unitname
seconds (00 through 59), and in
tenths of a second (0 through 9). Explanation: Multiple console support (MCS) activated
an operator on a Time Sharing Option Extensions
TSOID = tsoid
(TSO/E) terminal.
The dump was generated for a SLIP trap that was
set in a Time Sharing Option (TSO) session. In the message text:
tsoid The identifier of the TSO user who defined opername
the trap. The userid or console name of the TSO/E
operator.
ID = uuuuuuuuuu
The component or subsystem identifier that was sysname
supplied in the ID keyword on the SDUMP or The name of the system to which the operator
SDUMPX macro. logged on. The system name is specified on
the SYSNAME parameter in the IEASYSxx
parmlib member.
Operator Response: Notify the system programmer;
unitname
identify the dsname of the dump.
The logical unit name. This name identifies the
System Programmer Response: Take the physical location of the terminal that the TSO/E
appropriate action as indicated in the following operator used to logon to the system.
descriptions:
DUMP DATA SET FULL - DUMP ENDED WHILE
WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}
Format the partial dump.
Automatic allocation is not functioning properly. If
the problem persists, search the problem reporting
contact the IBM Support Center. Be able to provide:

v The SYSDDIR statement in the BLSCUSER parmlib
IEA631I OPERATOR opername NOW INACTIVE,
has not been processed.
SYSTEM=sysname, LU=unitname
System Action: The system disables the function to
Explanation: An operator on a Time Sharing Option
add source descriptions for SVC dumps to the sysplex
Extensions (TSO/E) terminal became inactive.
dump directory. The system deletes the outstanding
In the message text: requests to add source descriptions; no new requests
will be created.
opername
The userid or console name of the TSO/E Application Programmer Response: Check the
operator. causes listed in the explanation and correct the
problem. Then cancel the DUMPSRV address space.
sysname
When the DUMPSRV address space restarts, the add
The name of the system to which the operator
function is again enabled.
logged on. The system name is the value of
the SYSNAME parameter in the IEASYSxx Source: SVC dump
parmlib member.
Detecting Module: DSE
unitname
The logical unit name. This name identifies the
IEA652A WTO STORAGE EXHAUSTED - WTOS
physical location of the terminal that the TSO/E
WILL BE DISCARDED
operator used to logon to the system.
Explanation: Outstanding WTO messages have used
all of the available buffer space. Some WTOs will be
Source: Communications task (COMMTASK) discarded.
System Action: The system processes only WTO
IEA650I SYSPLEX DUMP DIRECTORY ENTRY messages that might be critical to relieving the buffer
NOT PROCESSED shortage, such as responses to the D C,B and D R
commands. All other WTO messages are discarded.
Explanation: Because of a failure, the system could
Discarded messages are not sent to the console, the
not automatically add a source description for an SVC
hardcopy log, the message exits, the SSI, or the joblog.
dump to the sysplex dump directory. The cause of the
failure could be that: Commands issued while WTO storage is exhausted are
v The sysplex dump directory was full. executed, but command response messages are not
v A sysplex dump directory had not been created. displayed or logged except for responses to D C,B and
v The sysplex dump directory was not specified. D R commands.
v The sysplex dump directory was continually in use.
JES3 monitors some command responses to update
v The SYSDDIR statement in the BLSCUSER parmlib
status for devices and jobs. Because these command
has not been processed.
responses are not issued JES3 is unable to process the
System Action: The source description for the dump status changes. When buffer space becomes available,
is not added to the sysplex dump directory. Other the system issues message IEA655I.
processing continues. The system will re-try the addition
Operator Response: Examine the output from the D
later.
C,B command. Based on the information displayed:
Application Programmer Response: Check the v If a console has accumulated a large number of
causes listed in the explanation and correct the messages, do one of the following:
problem.
– Use the CONTROL Q command to reroute the
Source: SVC dump messages
Detecting Module: IEAVTSST – Use the CONTROL E command to delete
messages
– Use the CONTROL S command to put the
IEA651E SYSPLEX DUMP DIRECTORY
console into roll mode and allow messages to roll
PROCESSING TERMINATED
off the screen
Explanation: Because of a failure, the system could – Use the VARY CN command to deactivate the
not automatically add a source description for an SVC console.
dump to the sysplex dump directory. This is the tenth
v If an address space has accumulated a large number
failure. The cause of the failures could be that:
of messages notify the system programmer.
v The sysplex dump directory was full.
v A sysplex dump directory had not been created. v If a large number of messages have arrived from
v The sysplex dump directory was not specified. another system then diagnose the problem on the
v The sysplex dump directory was continually in use. system sending the messages.

v If a large number of messages are waiting for sysname2
delivery to another system, then try to relieve the The name of the system that cannot sent
buffer shortage on the target system. messages to system sysname1.
System Programmer Response: If an address space System Action: System sysname2 holds messages
has accumulated a large number of messages, follow for system sysname1 until either:
the response for message IEA099A. Otherwise, follow v The WTO buffer shortage is relieved on system
the system programmer response for message sysname1
IEA404A. v WTO buffers on system sysname2 reach 80% full
Source: Communications Task (COMMTASK) Operator Response: Try to relieve the WTO buffer
shortage on system sysname1 as described in message
IEA404A.
System Programmer Response: Follow the system
IEA653I JOBNAME= jobname ASID= asid HAS
programmer response for message IEA404A to reduce
REACHED nn% OF THE WTO BUFFER
the probability of a WTO buffer shortage on system
LIMIT
sysname2.
Explanation: The job named in the message has used
Source: Communications Tack (COMMTASK)
nn% of the limit of WTO buffers as determined by the
value of MLIM in the CONSOLxx parmlib member. nn% Detecting Module: IEAVG610
is a percentage that is high enough to suggest a
possible problem.
IEA655I WTOS NO LONGER BEING
In the message text: DISCARDED - nnnnnnnn MESSAGES
WERE LOST WHILE WTO STORAGE
jobname
WAS EXHAUSTED
The name of the job that is using a large
percentage of the WTO message buffers. Explanation: The WTO storage shortage is less
severe, and messages are no longer being discarded.
asid
This message only goes to the hardcopy log.
The ASID of the named job.
nn.
the percent of the maximum number of WTO nnnnnnnn
buffers used by the specified job. The number of messages that were discarded.
(When more than 99,999,999 messages have been
discarded, nnnnnnnn contains ********.)
System Action: The system can now process some
Application Programmer Response: If your program WTOs.
is in a WTO loop, correct the program. Consider
modifying the program so that it uses the
MSGFLAG=BUSYEXIT parameter so that the system Source: Communications Task (COMMTASK),
will return control to the program when the WTO buffer
limit is reached.
System Programmer Response: Follow the response
IEA705I ERROR DURING
for message IEA099A.
{GETMAIN|FREEMAIN}, SYS CODE=
Source: Communications Tack (COMMTASK) cde-rc {jobname|aaa} stepname fb
w1w2w3w4w5w6
Detecting Module: IEAVH600
Explanation: The system found an error when
processing a GETMAIN, FREEMAIN, or STORAGE
IEA654A WTO BUFFER SHORTAGE ON SYSTEM
macro.
sysname1 IS AFFECTING MESSAGES
ON SYSTEM sysname2 In the message text:
Explanation: System sysname2 cannot send cde The abend code.
messages to system sysname1 because system
rc The reason code.
sysname1 is experiencing a WTO buffer shortage.
jobname The name of the job that was running
when the error occurred.
sysname1
aaa The return address of the calling
The name of the system that is experiencing a
routine. This field appears if the entry
WTO buffer shortage.

to GETMAIN or FREEMAIN was not Dxx 04 a b c d f g
through system linkage.
08 a b c d f
stepname The name of the step that was
running when the error occurred.
(Attention: If this message was issued
In the table:
while running under the MSTR
subsystem, this field may contain a The current address space control block
residual information and require (ASCB) address.
verification against the ASCB and
TCB information provided). b The dispatched task control block (TCB)
address.
fb The flag byte, which indicates how the
system entered GETMAIN or c The input TCB address.
FREEMAIN. fb is one of the following: d The first two bytes are the subpool identifier
00 System linkage was used. requested. The third byte contains request
The GETMAIN or FREEMAIN flags, as follows:
was entered through one of 1... .... The access list entry table (ALET)
the following: was specified on the STORAGE
v A Supervisor Call (SVC) macro.
instruction generated by
.1.. .... Storage may be backed above or
the GETMAIN or
below 16 megabytes.
FREEMAIN macro
v A Program Call (PC) ..1. .... Virtual storage may be above 16
instruction generated by a megabytes.
STORAGE macro ...1 .... Virtual storage may be below 16
80 GETMAIN or FREEMAIN megabytes.
was entered through a .... 1... Request is variable-length.
Branch instruction generated
by a GETMAIN or .... .1.. Storage should be on page boundary.
FREEMAIN macro. .... ..1. Request is unconditional.
w1w2w3w4w5w6 .... ...1 Request is a FREEMAIN or
Variable data, in hexadecimal. The STORAGE RELEASE.
data depends on the abend code and
reason code in the message text, as
The 4th byte is zero.
follows:
e The address of the parameter list supplied by
cde rc w1 w2 w3 w4 w5 w6 the caller.
1xx all a b c d f f The length of the area requested for
2xx all a b c h GETMAIN, FREEMAIN, or STORAGE.
3xx all a b c d f g g The starting address of the area to be freed.
4xx all a b c d f g h The address of the virtual storage manager

(VSM) work area.
5xx all a b c e
i The address specified on the INADDR
6xx all a b c e parameter for the GETMAIN or STORAGE
7xx all a b c h macro.
8xx 4-14 a b c d f System Action: The system abnormally ends the job
step.
18,20 a b c d f g
24,28 a b c d f i
the accompanying abend and reason codes.
9xx all a b c d f g
Axx all a b c d f g programmer response for the accompanying abend and
Bxx 4-4C a b c d reason codes.
50-54 a b c d f i Source: Virtual storage manager (VSM)

IEA710A LPALST FUNCTION INOPERATIVE - HIT IEA712I LPALST LIBRARY DATA SETS
ENTER TO CONTINUE WITH THE IGNORED
DEFAULT LPALST OR RE-IPL THE
SYSTEM (dsname) (text)
(dsname) (text)
Explanation: The system was initializing the LPALST .
.
function, but it encountered an I/O while reading from .
one of the specified LPALSTxx parmlib members. An
Explanation: The data set named dsname, which was
accompanying diagnostic message, such as IEA300I,
specified in the selected LPALSTxx members of
IEA301I, or IEA306I, describes the specific error.
SYS1.PARMLIB, could not be concatenated to
System Action: The system does not initialize the SYS1.LPALIB for the reason indicated in the message
LPALST function. Initialization processing waits for your text.
response.
dsname
about this message and the accompanying message. To
continue system initialization with the default LPALST
concatenation, press ENTER. Otherwise, reIPL the text
system. One of the following:
System Programmer Response: To correct the UNABLE TO LOCATE
condition that caused the problem, respond to the The system could not find a catalog entry for
accompanying diagnostic message, then reIPL the the data set.
system to build the LPALST concatenation.
UNABLE TO MOUNT
Source: Contents supervision (CSV) The system could not find the data set on the
volume indicated by the system catalog. This
condition will be accompanied by message
IEA317A or IEA319I.
IEA711E LPALSTxx INPUT TRUNCATED AFTER
UNABLE TO OPEN
dsname
An error occurred while opening the data set.
Explanation: Too many data set names were specified This condition will be accompanied by
for inclusion in the LPALST concatenation. LPALSTxx is message IEA211I.
the parmlib member from which the last data set name,
UNABLE TO INCLUDE
dsname, was obtained for the LPALST.
The data extent block (DEB) for the
In the message text: concatenation could not contain the number of
extents required to include the data set.
xx Identifies the parmlib member of LPALST.
dsname
The specified data set name. Operator Response: Notify the system programmer.
System Action: The system placed the data set System Programmer Response: This is probably an
names up to dsname in the LPALST concatenation. The installation error. Correct the condition that caused the
system ignores the data set names after dsname. problem.
The nucleus initialization program (NIP) issues this Source: Contents supervision (CSV)
message when the concatenation is opened. LNKLST
lookaside reissues this message to ensure that it
remains on the operator’s screen.
IEA713I LPALST LIBRARY CONCATENATION
(dsname) . . (dsname)
Explanation: This message lists the data sets,
an installation error. Reduce the number of data sets
dsname, concatenated to SYS1.LPALIB.
specified for inclusion in LPALST. To reopen the
LPALST concatenation, run a cold start initial program In the message text:
load (IPL).
dsname
Source: Contents supervision (CSV) The specified data set name.
Detecting Module: IEAVNP05 System Action: Normal processing continues.
CSVLLCRE Source: Contents supervision (CSV)

Detecting Module: IEAVNP05 bases for a fix for the problem. If no fix exists, contact
IEA716I text- member DATA SET IGNORED Source: Contents supervision (CSV)
library
Detecting Module: CSVMLPRM
text is one of the following: IEANPE5
LIBRARY NOT LOCATED
LIBRARY NOT IN APF TABLE
IEA738I MAXUSER=val1, RSVNONR=val2,
UNABLE TO MOUNT VOLUME
RSVSTRT=val3 SUM EXCEEDS
UNABLE TO OPEN LIBRARY
MAXIMUM OF 32767
Explanation: The system could not process a library
Explanation: The sum of the MAXUSER, RSVSTRT,
specified in a parmlib member.
and RSVNONR values exceeds the allowed maximum
In the message text: of 32,767. These parameters are specified in the
IEASYSxx parmlib member and are added together to
LIBRARY NOT LOCATED
compute the size of the address space vector table
The system could not locate library library
(ASVT).
specified in parmlib member member
LIBRARY NOT IN APF TABLE
Library library is not authorized by the val1 The value of MAXUSER in IEASYSxx
authorized program facility (APF)
val2 The value of RSVNONR in IEASYSxx
UNABLE TO MOUNT VOLUME
val3 The value of RSVSTRT in IEASYSxx
The system could not mount the volume where
library data set, library is located System Action: The system prompts the operator to
respecify the three parameters by issuing message
UNABLE TO OPEN LIBRARY
IEA906A three times: once each for MAXUSER,
The system could not open the library data set,
RSVNONR, and RSVSTRT.
library
Operator Response: Respond to message IEA906A
member
as the system programmer directs.
The parmlib member where the library was
specified. System Programmer Response: Do the following:
The parmlib member is one of the following: v Select a smaller value for one or all of the
v IEALPAxx parameters.
v IEAFIXxx v Ask the operator to respond to message IEA906A
with the new values for the parameters.
library The name of the library data set specified in
the parmlib member, member v Correct the parameters in the IEASYSxx member so
that this message will not be issued during every
System Action: The system continues processing the system initialization using IEASYSxx.
indicated parmlib member, but does not process library
library. Source: Supervisor control
If UNABLE TO MOUNT or UNABLE TO OPEN appear Detecting Module: IEAVNP09

in the message text, the system issues messages
IEA211I, IEA307I, IEA311I, IEA312I, IEA314I, IEA317A, IEA740W SUPERVISOR UNABLE TO RECOVER
and IEA319I explaining the error. FROM SVC D LOOP
Operator Response: If UNABLE TO MOUNT appears Explanation: While the system was processing the
in the message text, mount the appropriate volume and Supervisor Call (SVC) instruction for an ABEND macro,
reIPL the system. a program check occurred recursively.
See the operator response for accompanying System Action: The system enters wait state X'104'.
messages.
System Programmer Response: If UNABLE TO wait state X'104'.
MOUNT or UNABLE TO OPEN appear in the message
text, see the system programmer response for System Programmer Response: See the system
accompanying messages IEA211I, IEA307I, IEA311I, programmer response for wait state X'104'.
IEA312I, IEA314I, IEA317A, or IEA319I.
If the problem persists, search problem reporting data
Detecting Module: IEAVESVR

IEA763I OPTIONS FOR OPERATIONS IEA764I REQUEST TO CHANGE OPERATIONS
COMPONENT TRACE ARE NOT VALID. COMPONENT TRACE BUFFER SIZE
FAILED
Explanation: One of the following occurred:
1. The OPTIONS keyword, specified on the REPLY Explanation: The system cannot obtain storage for
command in response to a TRACE the new trace buffer size requested. One of the
CT,ON,COMP=SYSOPS command, was entered following occurred:
with incorrect options. v A TRACE CT,ON,COMP=SYSOPS command was
2. The operations component trace parmlib member entered with a new buffer size in the CTRACE
specified on a TRACE parmlib member.
CT,ON,COMP=SYSOPS,PARM=CTIOPSxx v A TRACE CT,nnnnK(or nnnnM),COMP=SYSOPS
command contains incorrect options on the command was entered.
OPTIONS keyword.
System Action: The TRACE CT command is rejected.
3. The operations component trace parmlib member The operations component trace buffer size is not
specified at IPL contains incorrect options on the changed.
OPTIONS keyword.
Operator Response: Either adjust the amount
Valid options are: specified and re-enter the TRACE CT command, or
v MESSAGES{,MSG=msgid} re-enter the command later. There might have been a
v MSGDLVRY{,MSG=msgid} temporary storage shortage.
v SYSPLEX Source: Communications Task (COMMTASK)
v WTO{,MSG=msgid}
v Combination of above options Detecting Module: IEAVH703
System Action: If the error occurred during use of the

TRACE CT command, the command is rejected. If the IEA765I CTRACE DEFINE FOR SYSOPS
error occurred during system initialization, operations FAILED, TRACING WILL BE
component trace (SYSOPS) will be initialized with the INITIALIZED {WITH DEFAULT PARMLIB
default tracing options. MEMBER | WITH NO PARMLIB
MEMBER} , RETCODE=xx,
Operator Response: Do one of the following: RSNCODE=yy
v If the options were specified on the REPLY
Explanation: Component trace initialization by the
command, re-enter the TRACE command and specify
operations component has failed for one of two reasons:
the correct options on the REPLY command.
1. A CTIOPSxx parmlib member (other than
v If the options were contained in an operations
CTIOPS00) was specified and contains errors.
CTRACE parmlib member that was specified on the
PARM= keyword of the TRACE CT command, have 2. The CTIOPS00 parmlib member was either
the system programmer correct the parmlib member. specified or used by default, and contains errors.
When the parmlib member has been corrected,
re-enter the TRACE CT command. The return and reason codes are the result of a
v If this message was issued during initialization, wait ?CTRACE DEFINE macro call and are listed in the
for the system initialization to complete and then OS/390 MVS Programming: Authorized Assembler
enter the DISPLAY TRACE,COMP=SYSOPS Services Reference ALE-DYN under ″CTRACE Return
command to display the current tracing options. If the and Reason Codes″.
desired options are not in effect, enter the TRACE System Action: If a CTIOPSxx parmlib member other
CT command to change operations tracing activity as than CTIOPS00 (the default) was specified during
needed. Notify the system programmer that the initialization, the CTIOPS00 will be used to define OPS
parmlib member that was used contains errors. CTRACE. If CTIOPS00 was specified (or selected by
System Programmer Response: If the incorrect default), OPS CTRACE will be defined using the OPS
options were listed in an operations CTRACE parmlib CTRACE defaults.
member, correct the parmlib member. Notify the System Programmer Response: Correct the currently
operator when the parmlib member has been corrected. specified CTIOPSxx parmlib member or provide a valid
Source: Communications Task (COMMTASK) CTIOPSxx parmlib member in SYS1.PARMLIB.
Detecting Module: IEAVH703 Source: Communications Task (COMMTASK)


entries with newer trace entries when the operations
IEA766I CTRACE DEFINE FOR SYSOPS
trace buffers filled up.
FAILED, TRACING WILL NOT BE
INITIALIZED, RETCODE=xx, System Action: The operations component trace
RSNCODE=yy continues. New trace entries continue to overlay older
trace entries. The action message will be deleted when
Explanation: Component trace initialization by the
the condition is resolved, if the component trace
Operations component has failed when it tried to define
abnormally terminates.
the Operations component trace without a parmlib
member. This case only occurs after CTIOPSxx failed Operator Response: This message will be deleted if a
and/or CTIOPS00 failed. valid TRACE CT command is issued with either the
WTRSTRAT parameter or with COMP=SYSOPS
The return and reason codes are the result of a
specified.
?CTRACE DEFINE macro call and are listed in the
OS/390 MVS Programming: Authorized Assembler System Programmer Response: You probably
Services Reference ALE-DYN under ″CTRACE Return started the operations component trace without first
and Reason Codes″. connecting a trace external writer. If the trace did not
capture enough data to diagnose the problem, ask the
System Action: OPS CTRACE is not initialized.
operator to reenter the TRACE CT command and do
System Programmer Response: Search the problem one (or both) of the following:
reporting data bases for a fix for the problem. If no fix v Increase the size of the operations component trace
exists, contact the IBM Support Center. (SYSOPS) trace buffers
Source: Communications Task (COMMTASK) v Start an external writer and connect operations
component trace (SYSOPS) to the external writer.
Source: Communications Task (COMMTASK)
IEA767A OPERATIONS COMPONENT TRACE Detecting Module: IEAVH704
HAS WRAPPED AN ALREADY FULL
BUFFER
IEA768I FAILURE IN CREATING DUMPSRV
Explanation: The operations component trace was ADDRESS SPACE mc, return-code,
started and the trace data was collected in operations reason-code
trace buffers. Operations overlaid some older trace
Explanation: An error occurred during the creation of
entries with newer trace entries when the operations
the dumping services address space (DUMPSRV),
trace buffers filled up.
which processes SVC dumps. Dumping services is
System Action: The operations component trace running but cannot do the following:
continues. New trace entries continue to overlay older v Give control to the post dump installation exit routine
trace entries.
v Process a dump request
System Programmer Response: You probably v Process a DUMPDS operator command
started the operations component trace without first
connecting a trace external writer. If the trace did not In the message text:
capture enough data to diagnose the problem, ask the
operator to reenter the TRACE CT command and do mc A module code, which is one of the
one (or both) of the following: following:
v Increase the size of the operations component trace 01 The system experienced an
(SYSOPS) trace buffers error while creating the
v Start an external writer and connect operations address space.
component trace (SYSOPS) to the external writer.
02 The DUMPSRV address
Source: Communications Task (COMMTASK) space experienced the error.
Detecting Module: IEAVH704 04 A request for virtual storage
for the SDUMP virtual buffer
or the summary dump
IEA767I OPERATIONS COMPONENT TRACE extended work area (SMEW)
HAS WRAPPED AN ALREADY FULL failed.
BUFFER
return-code The return code placed in register 15
Explanation: The operations component trace was by the failing module.
started and the trace data was collected in operations
trace buffers. Operations overlaid some older trace reason-code The reason code placed in register 0

by the failing module. When mc is 04, does not complete ending of the address space. The
the system does not put a value into system ignores any CANCEL or FORCE operator
register 0. command to end the address space.
System Action: The system continues processing, but In most cases, the system writes a logrec data set error
cannot process dump requests. The system writes a record. The record contains the ASCB in the variable
logrec data set error record. recording area (VRA) of the system diagnostic work
area (SDWA).
reporting data bases for a fix for the problem. If no fix System Programmer Response: Search problem
exists, report the problem to the IBM Support Center. reporting data bases for a fix for the problem. If no fix
Provide the logrec data set error record. exists, report the problem to the IBM Support Center.
Provide the logrec data set error record and messages.
Detecting Module: IEAVTSAI, IEAVTSAS
Detecting Module: IEAVTMTC
IEA774I SUBCHANNEL INITIALIZATION FAILED
FOR SUBCHANNEL nnnn, DEVICE IEA793A NO SVC DUMP DATA SETS AVAILABLE
NUMBER dev FOR DUMPID=dumpid FOR JOB
(*MASTER*). USE THE DUMPDS
Explanation: The system tried to initialize a
COMMAND OR REPLY D TO DELETE
subchannel for a device. The subchannel was not
THE CAPTURED DUMP
operational, or busy in a state that could not be cleared.
Explanation: The system has captured the data for
the dump but cannot locate an available dump data set
nnnn for the dump. An available dump data set is either a
The subchannel identifier. SYS1.DUMPnn data set with the first record containing
an end of file, or an automatically allocated data set. If
dev automatic dump data set allocation is already active,
The device number. check the syslog for a previous IEE799I message for
System Action: The system continues subchannel details about the dump data set allocation failure.
initialization with the next sequential subchannel In the message text:
number.
dumpid A 3-character dump identifier.
System Action: SVC dump processing continues to
Source: Input/output supervisor (IOS) search for an available dump data set until one of the
Detecting Module: IEAVNP02 following occurs:
v An available dump data set is found
IEA792I ADDRESS SPACE asid CANNOT BE v The operator replies D to delete the captured dump
TERMINATED - JOB [jobname] v The interval specified by the MSGTIME parameter on
the CHNGDUMP command expires
Explanation: The system was trying to end an
address space when an error occurred. Operator Response: Do one of the following:
In the message text: v Use the DUMPID on the DISPLAY DUMP command
to display the title or error information.
asid The address space identifier (ASID) of the
v Enter the DUMPDS command to clear an existing
address space that was ending.
dump data set or to add a new dump data set in
jobname order to write the dump to a data set.
The name of the job that was running in the v Reply D to the message. SDUMP will delete the
address space. The job is one of the following: captured dump.
v An initiated task
v Run a utility to clear an existing dump data set.
v A started task
v A mounted task v Add additional SMS classes (DUMPDS ADD,SMS=)
v A time sharing option (TSO) logon task or DASD volumes (DMPDS ADD,VOL=) to the
automatic allocation facility, or correct the problem
If the job name is not available, jobname does which caused the automatic dump data set allocation
not appear in the message. failure.
System Action: The system removes the address
space control block (ASCB) from the end queue and

If a utility other than DUMPDS will be used to make a vv The type of machine check:
dump data set available automatically, no response is
IPD Instruction processing damage
required. SVC dump processing periodically searches
the queue of data sets until one becomes available or SD System damage
the MSGTIME interval expires.
IV Invalid program status word (PSW) or
Source: SVC dump registers
Detecting Module: IEAVTSCD TC Time of day (TOD) clock damage
PT CPU timer damage
IEA794I SVC DUMP HAS CAPTURED:
DUMPID=dumpid REQUESTED BY JOB Clock comparator damage
(*MASTER*) DUMP TITLE=dump-title PS Primary sync damage
Explanation: The system has captured the data for AD External Time Reference (ETR)
the SVC dump. attachment damage
In the message text: SL Switch to local
dumpid A 3-character dump identifier. text
dump-title One of the following:
The title of the dump, provided by the caller or v AN UNKNOWN ERROR OCCURRED.
by the operator. The title can be up to 100 v CPU x CHECKSTOPPED.
characters long.
v CPU x REACHED ITS vv MACHINE-CHECK
System Action: The system writes the SVC dump to THRESHOLD OF SPIN-LOOP RECOVERY
the dump data set, if available, and issues message PROCESSING.
IEA611I or IEA911E. IEA611I and IEA911E indicate: v CPU x’s TOD CLOCK COULD NOT BE
v Whether the system wrote a complete or partial dump SYNCHRONIZED.
v Which dump data set contains the dump. v OF A MALFUNCTION IN THE DAT HARDWARE.
v CPU x’s CLOCK COULD NOT BE
If no dump data set is available, the dump remains SYNCHRONIZED TO THE ETR.
captured and the system issues message IEA793A. v AN UNRECOVERABLE MACHINE ERROR
IEA793A indicates: OCCURRED.
v That a dump has been captured but no dump data v PHYSICAL VARY FOR THE CPU FAILED.
set is available.
v PHYSICAL STATE OF THE CPU UNKNOWN.
v The DUMPID which may be used on the DISPLAY
DUMP command. PHYSICAL VARY FOR THE CPU FAILED
v That the operator may use the DUMPDS command The service processor was unable to take the
to clear a dump or cancel a dump. failing processor physically offline.
Source: SVC dump PHYSICAL STATE OF THE CPU UNKNOWN

The service processor request was unable to
Detecting Module: IEAVTSCC complete. The failing processor is not physically
offline.
IEA796E ACR PROCESSING HAS TAKEN CPU System Action: The system continues processing.
[AND VF] x [LOGICALLY] OFFLINE
BECAUSE text The system does not automatically remove this
message from the display console. The operator must
Explanation: Alternate CPU recovery (ACR) has manually delete the message.
successfully placed a failing processor (CPU), and
possibly the associated Vector Facility (VF), logically The system writes a logrec data set error record.
and physically offline. Operator Response: Delete the message from the
In the message text: console with the CONTROL(K) command.
x The processor that was taken offline. If PHYSICAL VARY FOR THE CPU FAILED or
PHYSICAL STATE OF THE CPU UNKNOWN appears
AND VF in the message text, take processor x physically offline
The associated VF was taken offline. with the CONFIG CPU, OFFLINE command. Contact
hardware support. Provide the logrec data set error
LOGICALLY
records.
The processor was taken logically offline.
Source: Alternate CPU recovery (ACR)

Detecting Module: IEAVTACR, IEAVTCRE reason-text
The reason why the system could not automatically
allocate a dump data set, as follows:
IEA797W {THE POINTER TO THE CURRENT FRR
STACK IS NOT VALID.| AN FRR STACK NO RESOURCES DEFINED
POINTER IS DAMAGED.} Automatic allocation of dump data sets is
active, but no allocation resources are defined.
Explanation: A recovery termination manager (RTM)
first level interruption handler (FLIH) determined that an INSUFFICIENT SPACE
interruption is an error. The FLIH issued a CALLRTM Automatic allocation of dump data sets is
macro to recover or to end the routine that caused the active and allocation resources are defined, but
error. While processing the request, RTM found there was insufficient space on any of the
uncorrectable damage to at least one functional resources to allocate a dump data set.
recovery routine (FRR) stack pointer in the recovery
DATA SET NAME NOT UNIQUE
stack vector table (PSARSVT) of the prefixed save area
An allocated data set could not be cataloged.
(PSA).
The data set has been deleted.
System Action: The system:
DYNALLOC FAILED RETURN CODE=return-code
1. Issues this message. ERROR RSN CODE=ersn INFO RSN CODE=irsn
2. Places all processors on this system in The automatic allocation of the dump data set
non-restartable X'084' wait state, with reason code failed because the dynamic allocation (SVC 99)
X'04'. failed. One or more messages preceded
IEA799I further describing the error condition.
See OS/390 MVS Programming: Authorized
wait state X'084'.
Assembler Services Guide for a description of
System Programmer Response: See the system dynamic allocation return codes, error reason
programmer response for wait state X'084'. codes, and information reason codes.
Source: Recovery termination manager (RTM) reason-text2
Additional information about the failure, as follows:
Detecting Module: IEAVTRTV
SMS RSN CODE=srsn, WILL TRY VOLUME
ALLOCATION
IEA798W UNSUCCESSFUL RECOVERY The automatic allocation failed for all storage
ATTEMPT BY RECOVERY management subsystem (SMS) classes
TERMINATION MANAGER specified using the SMS parameter of the
Explanation: The recovery termination manager DUMPDS command. See OS/390 MVS
(RTM) was trying to invoke a functional recovery routine Programming: Authorized Assembler Services
(FRR) when a double recursive abnormal end occurred. Guide for a description of dynamic allocation
SMS reason codes. SVC dump attempts to
System Action: The system enters non-restartable allocate the data set to one of the DASD
wait state X'084', with reason code X'08', X'0C', or X'10'. volumes available for automatic allocation.
Operator Response: If requested by the system SMS RSN CODE=srsn
programmer, take a stand-alone dump. The automatic allocation failed for all storage
System Programmer Response: Request the management subsystem (SMS) classes
operator to take a stand-alone dump to ensure first specified using the SMS parameter of the
failure data capture. See the system programmer DUMPDS command. See OS/390 MVS
response for wait state X'084'. If the problem is not Programming: Authorized Assembler Services
contained in a problem reporting data base, contact the Guide for a description of dynamic allocation
IBM Support Center. Provide the stand-alone dump. SMS reason codes.
Source: Recovery termination manager (RTM) VOLUME ALLOCATION FAILED

The automatic allocation failed for all volumes
available to SVC dump.
IEA799I AUTOMATIC ALLOCATION OF SVC
DUMP DATA SET FAILED System Action: SVC Dump processing will attempt to
DUMPID=dumpid REQUESTED BY JOB write the dump to a SYS1.DUMP data set. If no
(jobname) reason-text reason text2 SYS1.DUMP data set is available, message IEA793A
will be issued.
Explanation: The system has captured data for a
dump with automatic allocation active, but was unable Operator Response: Notify the system programmer.
to allocate a dump data set for the dump. System Programmer Response: Use DISPLAY
In the message text: DUMP command to display the status of automatic

allocation resources. Use the DUMPDS command to System Action: GTF ended trace formatting. The
add allocation resources or de-activate automatic system continues writing the ABEND dump. The
allocation as necessary. formatted trace output is incomplete because it does not
include the most current trace entries.
Source: SVC Dump
System Programmer Response: Proceed according
Detecting Module: IEAVTSCD
to the response documented for the error message or
completion code that occurred when GTF ended.
IEA802W DAT ERROR IN SYSTEM ADDRESS
SPACE
Explanation: A dynamic address translation (DAT)
IEA809I ERROR IN BUFFER REMAINDER OF
error occurred for a system address space. The
BUFFER IGNORED
recovery termination manager (RTM) does not end the
address space because the ASCBNOMT and Explanation: During formatting of the trace buffers in
ASCBNOMD fields of the address space control block the generalized trace facility (GTF) region, an incorrect
(ASCB) show that the MEMTERM option of the length field was discovered.
CALLRTM macro is not valid for the address space.
System Action: GTF does not format the remainder of
The address space is crucial for system operation.
the buffer.
System Action: The system enters wait state X'A00'.
System Programmer Response: Obtain the SYSOUT
Operator Response: See the operator response for output for the job. Collect all printed output and output
wait state X'A00'. data sets related to the problem. Search problem
programmer response for wait state X'A00'.
Detecting Module: IEAVTRTM
IEA810E UNCORRECTABLE I/O ERROR ON LPA

IEA806I jjj.sss HAS BEEN TERMINATED DUE TO
PAGE; CREATE LPA ON NEXT IPL
AN UNCORRECTABLE I/O ERROR ON
THE PAGE DATA SET Explanation: An uncorrectable I/O error occurred
while attempting to page in a warm start copy of a link
Explanation: Because of an I/O error, the system
pack area (LPA) page. Because the external storage for
abnormally ended a task with abend X'028'
this LPA page cannot be read, the problem will recur on
In the message text: the next IPL unless a new LPA is created.
jjj The job name. System Action: The system abnormally ends the task
which requested paging of the LPA page.
sss
The step name. Operator Response: On the next IPL, create a new
LPA through the CLPA parameter when specification of
System Action: The system issues messages to the system parameters is requested.
job log about the job.
Operator Response: Repeated occurrences of this IEA811E PAGTOTL PAGE VALUE xxx OUTSIDE
message indicate that the page data set should be VALID RANGE
reallocated and formatted at the next IPL.
Explanation: The system does not accept the
System Programmer Response: If the problem specified total number of page data sets. It must be a
recurs and if the program is not in error, search problem number from 0 to 256.
messages in the job log, the JCL for the job, and all
xxx The total number of page data sets.
problem. System Action: The system issues message IEA906A
to prompt the operator to respecify the PAGTOTL
parameter, or to press the ENTER button on the
IEA808I GTF TERMINATED DURING TRACE
console.
FORMATTING
Operator Response: Either respecify the PAGTOTL
Explanation: During formatting of the generalized
values or press the ENTER button, which specifies the
trace facility (GTF) trace buffers, GTF encountered a
default values of (5,1).
severe error.

Source: Auxiliary storage manager (ASM)
IEA820I TRANSACTION DUMP REQUESTED
Detecting Module: ILRASRIM BUT NOT TAKEN. reason
Explanation: The requested transaction dump was not
IEA812E PAGTOTL VALUES INCREASED TO taken reason is one of the following:
(ppp,sss) PARAMETER LIST ADDRESS ZERO
SYSMDUMP DUMP MODE SET TO NODUMP BY
Explanation: The PAGTOTL value was less than the CHNGDUMP COMMAND
actual number of page data sets that were specified THE DUMP WAS SUPPRESSED BY SLIP
through the PAGE parameter. Therefore, the system PARAMETER LIST ALET NOT VALID
increases the specified PAGTOTL value. PARAMETER LIST NOT ACCESSIBLE
In the message text: PARAMETER LIST VERSION NOT VALID
PARAMETER LIST LENGTH NOT VALID FOR
ppp The actual number of page data sets plus one. VERSION
System Action: The system continues processing NO DCB OR DATA SET NAME SUPPLIED
using the new PAGTOTL value. BOTH DCB AND DATA SET NAME SUPPLIED
DCB ALET NOT VALID
Source: Auxiliary storage manager (ASM) DCB NOT ACCESSIBLE
Detecting Module: ILRASRM1 DATA SET NAME ALET NOT VALID
DATA SET NAME NOT ACCESSIBLE
NO HEADER SUPPLIED
IEA813E PAGNUM IS AN OBSOLETE HEADER ALET NOT VALID
KEYWORD, PAGTOTL SHOULD BE HEADER DATA NOT ACCESSIBLE
USED HEADER LONGER THAN 100 CHARACTERS
DUMP INDEX DSNAME ALET NOT VALID
Explanation: The system no longer recognizes the
DUMP INDEX DSNAME NOT ACCESSIBLE
PAGNUM keyword. PAGTOTL should be used instead.
DUMP INDEX DSNAME NOT VALID
System Action: The system determines the actual SYMPTOM RECORD ALET NOT VALID
number of page data sets specified by the PAGE SYMPTOM RECORD DATA NOT ACCESSIBLE
parameter. Then, the system sets default PAGTOTL SYMPTOM RECORD NOT VALID
values by adding one to the actual number of page data INCIDENT TOKEN ALET NOT VALID
sets The system continues processing, using the default INCIDENT TOKEN DATA NOT ACCESSIBLE
PAGTOTL values. REMOTE AREA ALET NOT VALID
REMOTE AREA DATA NOT ACCESSIBLE
REMOTE AREA NOT VALID
Detecting Module: ILRASRIM PROBLEM DESCRIPTION AREA ALET NOT VALID
PROBLEM DESCRIPTION AREA DATA NOT
ACCESSIBLE
IEA814D DATA SET dsname DRAINING ON PROBLEM DESCRIPTION AREA NOT VALID
PREVIOUS IPL, CONTINUE DRAINING? STORAGE LIST ALET NOT VALID
REPLY ‘YES’ OR ‘NO’ STORAGE LIST NOT ACCESSIBLE
Explanation: On a warm start IPL, the system STORAGE LIST START ADDRESS GREATER
determined that a data set had been draining on the THAN END ADDRESS
previous IPL. The operator must indicate whether the SUBPOOL LIST ALET NOT VALID
data set is to remain draining or is to be returned to SUBPOOL LIST DATA NOT ACCESSIBLE
normal system use. SUBPOOL LIST NOT VALID
DATASPACE LIST ALET NOT VALID
In the message text: DATASPACE LIST DATA NOT ACCESSIBLE
dsname DATASPACE LIST NOT VALID
The name of the data set. ECB ALET NOT VALID
ECB DATA NOT ACCESSIBLE
System Action: The system waits for the operator to ECB NOT VALID
reply YES or NO. CALLER AUTHORIZATION INSUFFICIENT FOR
Operator Response: If the data set should remain in REQUESTED FUNCTIONS
draining status, reply YES and the data set remains DUMP DATA SET NAME NOT VALID
read-only. If the data set should be returned to normal DUMP DATA SET NAME TOO LONG
system use, reply NO and the data set becomes eligible DUMP DATA SET NAME SYMBOL SUBSTITUTION
for writes. FAILED
DATASPACE CREATION FAILED FOR AUTOMATIC
Source: Auxiliary storage manager (ASM) ALLOCATION

COULD NOT ACCESS DATASPACE FOR Report the problem to the system programmer.
AUTOMATIC ALLOCATION
AUTOMATIC ALLOCATION OF DUMP DATA SET
statements in the IEASVCxx parmlib member for syntax
FAILED
problems.
THE DUMP WAS SUPPRESSED BY DAE
AN I/O ERROR OCCURRED Source: Supervisor control
INTERNAL PROCESSING ERROR DETECTED,
REASON CODE=rsncode Detecting Module: IEAVNP25
In the message text: IEA822I {COMPLETE∨PARTIAL} TRANSACTION

DUMP WRITTEN [TO dsname]
rsncode
Internal processing error reason code. Will be Explanation: The system wrote a complete or partial
one of the following: transaction dump to a data set on a direct access
storage device (DASD).
01 Unable to obtain storage for
transaction dump from subpool 230 In the message text:
below the line.
COMPLETE
02 Unable to establish recovery The transaction dump was complete.
environment for IEAVTDMP.
PARTIAL
03 Unable to obtain storage for The transaction dump was not complete.
transaction dump from subpool 239
above the line. dsname
The dump was written to the dsname data set.
transaction dump from subpool 231 System Action: The system continues processing.
above the line. System Programmer Response: Open the dump
05,06,07 under IPCS to view diagnostic data.
Unable to obtain storage for Source: IEAVTDMP
transaction dump from subpool 239
above the line. Detecting Module: IEAVTDMP

transaction dump from subpool 250 IEA823I IEASVCxx: SVCnum: text
above the line. Explanation: text is one of the following:
FF IEAVTDMP’s recovery received SYNTAX ERROR AT parm
control. UNBALANCED PARENTHESIS AT parm
TYPE t SVC CANNOT GET GLOBAL SPIN LOCK
System Action: The system continues processing. TYPE 6 SVC CANNOT GET ANY LOCK
Application Programmer Response: The message CANNOT REQUEST CMS LOCK WITHOUT LOCAL
describes the reason for which the dump was not taken. LOCK
Examine and correct the condition.
An SVC number was incorrectly specified in the
Source: IEAVTDMP IEASVCxx parmlib member.
Detecting Module: IEAVTDMP
IEA821I SYNTAX ERROR IN “SVC=” xx The suffix of the IEASVCxx parmlib member
PARAMETER num The SVC number that was incorrectly specified
Explanation: Non-alphanumeric characters were text Describes the error. text is one of the following:
specified in the SVC parameter in the IEASVCxx
parmlib member. SYNTAX ERROR AT parm
Where parm is a character string in the
System Action: The system prompts the operator to SVCnum specification.
respecify the SVC parameter.
UNBALANCED PARENTHESIS AT parm
Operator Response: When the system prompts for Where parm is a keyword specification.
the new SVC parameter, do one of the following:
TYPE t SVC CANNOT GET GLOBAL SPIN
v Respecify the parameter.
LOCK
v Specify EOB (press the enter button on the console) Where t is the SVC type specification.
to proceed with the default SVC table.

TYPE 6 SVC CANNOT GET ANY LOCK Source: Supervisor control
A type 6 SVC cannot request any locks,
but it did.
CANNOT REQUEST CMS LOCK WITHOUT
IEA826I IEASVCxx: SVCnum: TYPE t ROUTINE
LOCAL LOCK
name NOT FOUND.
An SVC cannot request the cross memory
services (CMS) lock without first obtaining Explanation: The entry point address could not be
the local lock, but an SVC tried to do this. found for a module specified with user type t and SVC
number num in the IEASVCxx parmlib member. The
System Action: The system ignores the statement.
load module name is missing from the nucleus or the
System Programmer Response: Check the link pack area (LPA).
problems.
xx The suffix of the IEASVCxx parmlib member
num The SVC number specified
t The user type specified
IEA824I IEASVCxx: SVCnum: DUPLICATE parm name The module name for which the entry point
KEYWORD. address could not be found
Explanation: A keyword option appears more than System Action: The system ignores the statement.
once on a single statement in the IEASVCxx parmlib
member for an SVC number. System Programmer Response: Do one or both of
the following:
In the message text: v Check the statements in the IEASVCxx parmlib
xx The suffix of the IEASVCxx parmlib member member for syntax problems.
v Determine why the load module is missing from the
num The SVC number
nucleus or the LPA.
parm The parameter for which the keyword option
was specified more than once
Detecting Module: IEAVNP25, IEAVNPS5
IEA828I IEASVCxx: PARSE ERROR,
STATEMENT nnnn.
problems.
Explanation: The system parser encountered an error
while processing the SVCPARM specifications in a
Detecting Module: IEAVNP25 statement in the IEASVCxx parmlib member.
IEA825I IEASVCxx: STATEMENT nnnn : NO
VALID parm SPECIFICATION.
nnnn The statement number in the IEASVCxx
Explanation: A required keyword parameter is missing
parmlib member where the system parser
or unidentifiable on a statement in the IEASVCxx
encountered an error
parmlib member.
System Programmer Response: Check statement
number nnnn in the IEASVCxx parmlib member for
nnnn The statement number in the IEASVCxx syntax problems.
parmlib member with the missing or incorrect
keyword parameter
parm The keyword parameter that is missing or
incorrect
IEA829I SVC num FOR aaa NOT USABLE,
MODULE bbb NOT FOUND IN ccc.
Explanation: The system needed a module for a
program product or access method Supervisor Call
problems.
(SVC) request, but the system could not find the module

in either the nucleus (NUC) or link pack area (LPA). parm The parameter for which an incorrect value
was specified
num The program product or access method SVC
number System Programmer Response: Check the
aaa The program product or access method that
problems.
appeared to be installed
bbb The module needed for the specified SVC
request that was not found Detecting Module: IEAVNP25
ccc One of the following:
LPA for the link pack area IEA833I IEASVCxx: STATEMENT nnnn: num IS
NUC for the nucleus NOT A VALID SVCNUM.
System Action: The system does not update the SVC Explanation: An SVC number, specified on a
table entry for this SVC. The system will abnormally end SVCPARM statement in the IEASVCxx parmlib member,
any program trying to use this SVC. is outside the range for installation-provided SVC
numbers. Valid values are 200 through 255.
System Programmer Response: Check to see if the
specified product is installed, or should be. In the message text:
v If it is installed, check that it is installed correctly.
v If it is not installed but should be, install it.
nnnn The statement number on which the incorrect
SVC number was specified
Detecting Module: IEAVNPST
num The incorrect SVC number
IEA830I IEASVCxx: DUPLICATE UPDATES TO
SVCnum IGNORED. System Programmer Response: Upon completion of
the initial program load (IPL), the system will not contain
Explanation: One or more IEASVCxx parmlib
an SVC instruction for the incorrect SVCPARM
members contain two or more SVCPARM statements
statement. Before the next IPL, check the SVCPARM
for the same SVC number.
In the message text: problems.
xx The suffix of the IEASVCxx parmlib member Source: Supervisor control
num The SVC number for which there two or more Detecting Module: IEAVNP25
statements
System Action: The system uses the first correct IEA836I PAGE DATA SET dsname NOT
SVCPARM statement and ignores any duplicate ALLOCATED - ERROR CODE err
statements. INFORMATION CODE xxxx
System Programmer Response: Remove duplicate Explanation: A request to allocate a page data set
SVCPARM statements for the same SVC number from resulted in an error.
the IEASVCxx parmlib members.
dsname
Detecting Module: IEAVNP25 The name of the data set.
err The error code.
IEA832I IEASVCxx: SVCnum: pval IS NOT A
xxxx The information code.
VALID parm.
System Action: One of the following, depending on
Explanation: A parameter specified on a statement in
the message text:
an IEASVCxx parmlib member is not valid.
PAGE
If the system knows from a previous IPL that the
xx The suffix of the IEASVCxx parmlib member page data set contains VIO pages that should be
used with current IPL options, the system issues
num The SVC number for which an incorrect
message IEA930I and continues paging
parameter was specified
initialization.
pval The incorrect value specified for the parameter

All other cases In the message text:
The system issues message IEA922D to let the
yyddd
operator respecify the data set name before
The date, in years (00 through 99) and in days of
continuing paging initialization.
the year (000 through 366)
hh.mm.ss.t
System Programmer Response: Respond according The time, in hours (00 through 23), in minutes (00
to the error code and information code in the message through 59), in seconds (00 through 59), and in
text. tenths of a second (0 through 9)
Source: Auxiliary storage manager (ASM) id The processor identifier
Detecting Module: ILRASRM2 symptoms
The symptoms from the dump header record for the
original abnormal end
IEA837I DISCARD ALL PERFORMED FOR
CACHE AT dev System Action: DAE suppresses the SYSMDUMP
dump.
Explanation: The auxiliary storage manager (ASM)
issues this message when a DISCARD ALL is run for Source: Recovery termination manager (RTM)
the cache of a cached auxiliary storage subsystem.
Detecting Module: IEAVTSYS
For a cold start or a quick start, this message is strictly
informational: for the first use of the cache: ASM
IEA839I WARM START DATA IS INVALID,
initialization automatically performs a DISCARD ALL for
QUICK START MAY BE FORCED
the cache during these starts. If more than one page
data set on the direct access storage device (DASD) Explanation: The previous initialization did not
backs the cache, ASM will issue this message only for complete. During that initialization attempt, the auxiliary
the first data set detected. storage manager (ASM) reset a cached auxiliary
subsystem because of a bad cache. This reset makes
For a warm start, this message may indicate a problem:
the cache usable, but makes the warm start data in the
ASM performed the DISCARD ALL after a sense
cache incorrect. A local page data set that contains VIO
subsystem status request to the cache indicated that a
pages is associated with the cache.
DISCARD ALL was required. This DISCARD ALL makes
any warm start data in the cache incorrect. The warm System Action: The system stops the warm start and
start will not be allowed to continue if ASM determines forces a quick start.
that warm start data may have been lost.
System Programmer Response: If the error cannot
dev The device number. be resolved, search problem reporting data bases for a
System Action: The system continues operation. If
Support Center.
warm start data was lost, the system issues message
ILR003A to force a quick start. Source: Auxiliary storage manager (ASM)
Operator Response: Reply U to message ILR003A. Detecting Module: ILRASRIM
For a warm start, notify the system programmer.
System Programmer Response: For a data problem IEA841E {PLPA|COMMON|LOCAL} DATA SET
during a warm start, search problem reporting data dsname UNUSABLE DUE TO BAD
bases for a fix for the problem. If no fix exists, contact CACHE AT dev
Explanation: The page data set is on a device
Source: Auxiliary storage manager (ASM) attached to a cached auxiliary storage subsystem.
When the system tested the cache, the control unit
reported the cache cannot be used due to hardware
errors.
IEA838I SYSMDUMP SUPPRESSED AS A
DUPLICATE OF: ORIGINAL: DATE
yyddd TIME hh.mm.ss.t CPU id dsname
(symptoms) The name of the data set.
Explanation: Dump processing issues this message dev The device number.
for any SYSMDUMP ABEND dump suppressed by
dump analysis and elimination (DAE). System Action: The system does one of the following:
For a cold start: The system issues message IEA922D.

In response, the operator may choose a new data set In the message text:
name or reply IGNORE.
dsname
For a quick start: The name of the data set.
v For a PLPA or local data set, the system issues System Programmer Response: Contact hardware
message IEA922D. In response, the operator may support.
choose a new PLPA or local data set name or the
IGNORE option. Source: Auxiliary storage manager (ASM)
v For a COMMON data set, if PLPA pages did not Detecting Module: ILRASRM2
overflow to the data set on the cold start associated
with this quick start, the system issues message System Action and Operator Response: Depending
IEA922D. In response, the operator may choose a on the system action, the operator does one of the
new COMMON data set name or the IGNORE option. following:
For a COMMON data set, if PLPA pages overflowed For a cold start: The system issues message IEA922D.
to the data set, the quick start cannot continue. The In response, choose a new data set name or the
system forces a cold start, issues message IEA929I, IGNORE option.
and then issues message IEA922D. In response, the
For a quick start:
operator may choose a new COMMON data set
name or the IGNORE option. v For a PLPA or local data set, the system issues
message IEA922D. In response, choose a new PLPA
For a warm start: or local data set name or the IGNORE option.
v For a PLPA data set, the system issues message v For a COMMON data set, if the PLPA pages did not
IEA922D. In response, the operator may choose a overflow to the data set on the cold start associated
new PLPA data set name or the IGNORE option. The with this quick start, the system issues message
new PLPA data set must have been used on a IEA922D. In response, the choose a new COMMON
previous cold start; otherwise, the warm start will fail data set name or the IGNORE option.
and a cold start will be forced. For a COMMON data set, if PLPA pages overflowed
v For a COMMON data set, if PLPA pages did not to the data set, the quick start cannot continue. The
overflow to the data set on the cold start associated system forces a cold start, issues message IEA929I,
with this warm start, the system issues message and then issues message IEA922D. In response,
IEA922D. In response, the operator may choose a choose a new COMMON data set name or the
new COMMON data set name or the IGNORE option. IGNORE option.
For a COMMON data set, if PLPA pages overflowed
For a warm start:
to the data set, the warm start cannot continue. The
system forces a cold start, issues message IEA929I, v For a PLPA data set, the system issues message
and then issues message IEA922D. In response, the IEA922D. In response, choose a new PLPA data set
operator may choose a new COMMON data set name or the IGNORE option. The new PLPA data set
name or the IGNORE option. The local page data set must have been used on a previous cold start;
information is not preserved. otherwise, the warm start will fail and a cold start will
be forced.
v For a local page data set that contains VIO pages,
the warm start cannot continue. The system forces a v For a COMMON data set, if PLPA pages did not
quick start and issues message IEA930I. overflow to the data set on the cold start associated
with this warm start, the system issues message
For a local page data set that contains no VIO pages,
IEA922D. In response, choose a new COMMON data
the warm start continues. However, the data set is
set name or the IGNORE option.
not used as the local page data set for this IPL.
For a COMMON data set, if PLPA pages overflowed
System Programmer Response: Contact hardware to the data set, the warm start cannot continue. The
support. system forces a cold start, issues message IEA929I,
Source: Auxiliary storage manager (ASM) and then issues message IEA922D. In response,
choose a new COMMON data set name or the
Detecting Module: ILRASRM2 IGNORE option. The local page data set information
is not preserved.
IEA842E {PLPA|COMMON|LOCAL} DATA SET v For a local page data set that contains VIO pages,
dsname UNUSABLE DUE TO I/O the warm start cannot continue. The system forces a
ERROR quick start and issues message IEA930I.
For a local page data set that contains no VIO pages,
Explanation: During initialization of page data sets,
the warm start continues. However, the data set is
the auxiliary storage manager (ASM) could not use a
not used as the local page data set for this IPL.
data set because of an I/O error while opening it.

IEA843I MODULE mmmmmmmm NOT FOUND
Explanation: During system initialization, a resource
IEA848I INSTALLATION PREDUMP EXIT,
initialization module (RIM) cannot find a module needed
dumpexit, MODIFIED/SUPPRESSED THE
for SNAP and ABEND dumping.
DUMP REQUEST
--or--
mmmmmmmm The name of the
module not found.
NO DUMP WAS PRODUCED FOR THIS
System Action: The system cannot load the missing ABEND, DUE TO SYSTEM OR
module into central storage. Therefore, the system will INSTALLATION REQUEST
not be able to write SNAP and ABEND dumps.
Operator Response: Notify the system programmer. If --or--
requested by the system programmer, reIPL the system.
DUMP SUPPRESSED - USER NOT
System Programmer Response: Place the module AUTHORIZED BY SAF
indicated by this message into the SYS1.LPALIB data
set. Then, ask the operator to reIPL the system. --or--
DUMP SUPPRESSED - ABDUMP
Detecting Module: IEAVTABI SERIALIZATION DEADLOCK AVOIDED,
SVC DUMP TAKEN INSTEAD
IEA846I SYSTEM CONSOLE INTERFACE
UNSUCCESSFUL. RESTART OPTIONS --or--
MAY NOT BE INITIALIZED ON CPU x
(yyyy) DUMP SUPPRESSED - ABDUMP
SERIALIZATION DEADLOCK AVOIDED,
Explanation: During nucleus initialization program SVC DUMP FAILED RC=sscc
(NIP) processing, the system tried unsuccessfully to
display the restart options on the processor restart
--or--
frame. The system may have already displayed the
options.
DUMP SUPPRESSED - ABDUMP MAY
In the message text: NOT DUMP STORAGE FOR KEY 0-7
JOB jobname
x The processor.
Explanation: Depending on the message text, the
yyyy
message means:
A hexadecimal reason code explaining the error.
yyyy is one of the following: INSTALLATION PREDUMP EXIT, dumpexit,
MODIFIED/SUPPRESSED THE DUMP REQUEST
0040 Service processor error.
The dump was suppressed by the installation
03F0 Processor x is not installed. predump exit.
04F0 Processor x is not in the configuration. In the message text:
10F0 Processor x is powered off. dumpexit

The most recent exit that requested
System Action: The system continues processing. suppression.
Operator Response: Check the restart options display NO DUMP WAS PRODUCED FOR THIS ABEND, DUE
on the restart frame on processor x. If the restart TO SYSTEM OR INSTALLATION REQUEST
options are displayed, no action is necessary. You can The system or installation requested no dump for
use the options at that console. this abend.
If the restart options are not displayed, notify the system DUMP SUPPRESSED - USER NOT AUTHORIZED BY
programmer. You can restart the system from the SAF
console, but the restart parameter value defaults to The system authorization facility (SAF), resource
REASON 0. access control facility (RACF), or its equivalent,
System Programmer Response: Determine why the determined that the caller does not have authority
system was unable to signal the console. If necessary, to dump the program that was running at the time
contact hardware support. of the error.

DUMP SUPPRESSED - ABDUMP SERIALIZATION system does not suppress needed dumps. If necessary,
DEADLOCK AVOIDED, SVC DUMP TAKEN INSTEAD change the security authority so that the application
ABDUMP did not produce a dump because another programmer gets a needed dump.
task holds a critical resource. In this environment,
Source: Dumping Services
the task will never release the resource. An SVC
dump will be taken instead of the SYSUDUMP, Detecting Module: IEAVTABD
SYSMDUMP or SYSABEND dump. The dump title
will include the jobname of the abending task.
IEA849I SYSMDUMP DATA SET FULL NO DUMP
DUMP SUPPRESSED - ABDUMP SERIALIZATION TAKEN TO dsname
DEADLOCK AVOIDED, SVC DUMP FAILED RC=sscc
ABDUMP did not produce a dump because another Explanation: The system attempted to write a
task holds a critical resource. In this environment, SYSMDUMP ABEND dump to a SYS1.SYSMDPxx data
the task will never release the resource. An attempt set with a disposition of SHARE. There was no
was made to take an SVC dump, but the system end-of-file (EOF) indicator in the first record of the data
was unable to take the dump. The return code set. The absence of an EOF indicator signals that the
indicates this with a value of X'08'. The reason data set is full; therefore, the system could not write the
codes describe the specific cause. Some SYSMDUMP. The dump is lost.
applications reason codes may be: In the message text:
02 The capture phase of another SVC dump dsname
was in progress. The data set to which the dump was to be
04 The SVC dump was suppressed by a SLIP written.
NODUMP command. System Action: The system continues processing.
0B The dump was suppressed by DAE. System Programmer Response: Create a routine
that copies the SYSMDUMP from its data set to another
Refer to OS/390 MVS Programming: Authorized data set and writes an EOF indicator as the first record.
Assembler Services Reference LLA-SDU for a Because the system issues message IEA993I each time
complete description of the SDUMPX macro return it writes a SYSMDUMP, include the routine in the
reason codes. installation exit routine for the WTO macro that issues
IEA993I.
ss The SDUMPX reason code.
Detecting Module: IEAVTABD
cc The SDUMPX return code.
DUMP SUPPRESSED - ABDUMP MAY NOT DUMP IEA850I FOLLOWING WILL BE PROCESSED ser
STORAGE FOR KEY 0-7 JOB jobname ON devtyp ccc-ccc
ABDUMP did not produce a dump because the
Explanation: This message lists all VATDEF entries
storage access key for the task is authorized,
that the system encountered before the I/O error
between 0 and 7. The program that issued the
referred to in message IEA949A. The second line
ABEND may still dump data via one of the following
appears for each volume. In the message text:
methods:
v Use the SDUMP macro to obtain a dump, or ser The serial number of the volume
v Use the SNAP macro to selectively dump data devtyp The device type
areas.
ccc-ccc The characteristics requested for the volume,
as follows:
Alternately, a SLIP trap may be set to request that
an SVC dump be generated for the ABEND. Also, P/R-PUB
the installation may allow the user to receive these Permanently resident, public
dumps by permitting the user to have READ access
to the IEAABD.DMPAKEY FACILITY as described P/R-PRV
in the OS/390 SecureWay Security Server RACF Permanently resident, private
Security Administrator’s Guide. P/R-STR
System Action: The system suppresses the dump. Permanently resident, storage
Application Programmer Response: If a dump RSV-PUB

needed to diagnose a problem was suppressed, notify Reserved, public
the system programmer. RSV-PRV
System Programmer Response: Make sure that the Reserved, private

RSV-STR
IEA852A REPEAT REPLY
Reserved, storage
Explanation: This message prompts the operator for a
System Action: The system processes the entries
reply to message IEA852I.
before the I/O error. The system sets attributes as
indicated, unless subsequent entries override them. System Action: The system waits for the operator to
reply.
Operator Response: Enter the reply again correctly or
enter REPLY id,‘U’.
IEA851A REPLY DEVICE ADDRESSES OR U
reply to message IEA851I.
IEA852I dev ADDRESS INVALID - n
reply. Explanation: The reply to message IEA851A is
incorrect. The system issues message IEA852I for each
Operator Response: If any of the volumes listed in
incorrect device in the reply, then message IEA852A. In
message IEA851I are to be mounted, enter REPLY
the message text:
id,‘dev,dev,dev,...’ where each dev is a device number
for a device on which you will mount a volume. You can dev
optionally precede a device number with a slash (/). Any The device number of the device in error.
valid direct access devices can be used, including those
n The cause of the error, as follows:
that already have volumes mounted on them. Mount the
required volumes on the devices in the reply, after n Meaning
message IEA860A appears.
1 The reply specified a duplicate device
If no volumes are to be mounted, enter REPLY id,‘U’. number.
Source: Allocation/unallocation 2 The specified device number is unknown
to the system.
3 The specified device contains a
permanently resident or reserved volume.
IEA851I FOLLOWING MAY BE MOUNTED ser
ON devtype 4 The specified device is not direct access.
Explanation: During processing of the VATLSTxx 5 The reply specified a device type is not
parmlib member, the system found that all volumes in needed for mounting of the requested
the member were not mounted. volumes.
ser ON devtype appears once for each unmounted 6 The system could not check for a data
volume. In the message text: path to the offline device.
ser The serial number of a volume to be mounted. 7 No data path is available to the specified
device.
devtyp
The type of device, such as 3330, on which the 8 No operational data path is available to the
volume is to be mounted. devtyp does not specify specified device.
any special features, such as track overflow, that
may be required; the installation must select the 9 The specified device is for an exposure
device that has any required special features. within a multiple exposure device
(supported pre-MVS/ESA SP 5.2), but is
System Action: The system issues message not the base exposure.
IEA851A.
10 The reply specified a device address for a
Operator Response: See the operator response for non-demountable device that was online at
message IEA851A. IPL.
Source: Allocation/unallocation System Action: The system issues message
IEA852A.
message IEA852A.

v If no volume can be mounted (for example, there is
IEA853A REPLY CONT, END OR RESPECIFY.
an error on that device), and the device is listed in
Explanation: While reading the VATLSTxx parmlib IEA860A, reply ’NO’ to message IEA893A when all
member, referred to in message IEA949A, the system other required devices have been mounted (that is,
detected an uncorrectable I/O error. when the required devices are not listed on
IEA893A).
reply. Source: Allocation/unallocation
Operator Response: If the system can continue Detecting Module: IEAVAP00
without VATLSTxx, enter one of the following:
REPLY id,‘CONT’ IEA855I INVALID VATLSTxx ENTRY
The system will try to continue processing other
Explanation: During processing of a VATLSTxx
specified VATLST members.
parmlib member, the system found an incorrect entry.
REPLY id,‘END’
System Action: Processing continues with the
If the reply is END, no more VATLST processing
remaining VATLSTxx entries.
will be done.
System Programmer Response: Using IEBPTPCH,
REPLY id,‘xx’
print the VATLSTxx member. Using IEBUPDTE, correct
If the reply is xx, VATLSTxx will be processed
the incorrect entry. Note that the device type might be
before processing the remaining VATLST members.
valid, but it was not specified as valid during system
nn is a new VATLST member.
installation.
If necessary, reIPL the system. Source: Allocation/unallocation
Source: Allocation/unallocation Detecting Module: IEAVAP00
IEA857W UNREC {H|S} ACR ERR-x-R=nn D=dd
IEA854I ERROR READING VOLUME LABEL. Explanation: Alternate CPU recovery (ACR)
encountered an unrecoverable error while recovery was
Explanation: For processing of a VATLSTxx parmlib
in progress for another processor. ACR attempted to
member, the system could not read the volume label on
recover and was unsuccessful.
a device. The device address is specified in subsequent
messages. One of the following occurred: In the message text:
v If message IEA306I precedes this message, an I/O H ACR encountered a hardware error.
error occurred when reading the label.
S ACR encountered a software error.
v The volume does not contain a standard label.
v In the case of Mass Storage System (MSS) volume, x An error code, which is one of the following:
the volume serial number on the label does not 1 The failure occurred prior to entering
match the volume serial number requested from the post processing.
3850 MSS. This case can occur when an MSS
volume label has been clipped to a different serial 2 The failure occurred during ACR post
number. processing.
System Action: For an MSS volume, the VATDEF nn Recovery processor identifier.
entry is ignored; processing continues with the
dd Failed processor identifier.
remaining VATLSTxx entries.
System Action: The system attempts to write a logrec
For non-MSS volumes the system waits for the operator
data set error record for the failed processor.
to mount the correct volume, if all device addresses
specified in reply to IEA851A have not yet had volumes When the error is a software error, the system places all
mounted on them. If they have, the system does not processors in non-restartable wait state X'051'.
wait; a mount request for the desired volume must be
When the error is a hardware error, the system places
issued later.
all processors in non-restartable wait state X'052'.
Operator Response: For MSS volumes, no response
Operator Response: If S appears in the message
is necessary.
text, see the operator response for wait state X'051'.
For non-MSS volumes:
If H appears in the message text, see the operator
v If the wrong volume is mounted, remove it and mount response for wait state X'052'.
the correct volume.
System Programmer Response: If S appears in the

message text, see the system programmer response for If no volume can be mounted on this unit, reply ‘NO’ to
wait state X'051'. message IEA893A when all other required devices have
been mounted, that is, when the required devices are
If H appears in the message text, see the system
not listed in message IEA893A.
Detecting Module: IEAVTCR1
IEA860A dev,dev,... REPLY U WHEN ALL

IEA858E ACR COMPLETE CPU [AND VF] NOW
DEVICES ARE READY.
OFFLINE [PHYSICAL VARY FAILED]
Explanation: To complete processing of the
Explanation: A failing processor was placed logically
VATLSTxx parmlib member, the operator must mount
offline by alternate CPU recovery (ACR).
volumes. In the message text:
dev
AND VF The device number for a device needing a volume.
The associated VF was taken offline.
PHYSICAL VARY FAILED mount the volumes, then to reply.
The service processor tried unsuccessfully to
Operator Response: Mount volumes, as listed in
vary the failing processor physically offline or
message IEA851I, on these devices. When the devices
the physical vary function is not supported by
are ready, REPLY ‘U’.
the service processor.
The system writes a logrec data set error record. Detecting Module: IEAVAP00
The system does not automatically remove this
message from the display console. The operator must IEA861A VAL=xx NOT FOUND. REPLY U OR
manually delete the message. CORRECT VALUE
Operator Response: Delete the message from the Explanation: The VAL parameter in the IEASYSxx
console with the CONTROL(K) command. parmlib member specified a suffix for a VATLSTxx
parmlib member. The system could not find in
If this ACR was initiated by an earlier response to the
SYS1.PARMLIB a VATLSTxx member with that suffix. In
excessive spin-loop message IEE331A, enter the
the message text:
CONFIG command to configure CPU x back online.
VAL=xx
If PHYSICAL VARY FAILED appears in the message
The specified suffix.
text, take processor x physically offline with the
CONFIG CPU, OFFLINE command. System Action: The system waits for the operator to
reply.
Contact hardware support. Provide the logrec data set
error record. Operator Response: If an error was made in the reply
to message IEA101A, enter REPLY id,nn where nn is a
correct value.
Detecting Module: IEAVTACR
Enter REPLY id,U to ignore this VATLSTxx and continue
processing any other specified members. Use
IEA859I UNREQUESTED VOLUME. UNIT dev IEBPTPCH to list the members of SYS1.PARMLIB.
NOW UNLOADED.
Explanation: A volume was mounted on a unit
specified by the operator in response to message
IEA862I RCT INITIALIZATION FAILED
IEA851A. No entry exists in the VATLSTxx parmlib
member for the device. In the message text: Explanation: A START, MOUNT, or LOGON command
requested the creation or initialization of an address
dev
space. The region control task (RCT) could not process
The device number.
the command for one of the following reasons:
System Action: The system unloads the volume. v RCT was unable to attach the dump task.
Operator Response: Mount a volume requested in v RCT was unable to attach started task control (STC).
message IEA851A on this unit. Reply ‘U’ to message v RCT was unable to establish a recovery environment.
IEA893A when the device is ready.
System Action: The system abends the partially

created address space and writes a logrec data set incorrect parameters in the parmlib member before the
error record. The system may write an SVC dump. next IPL.
System Programmer Response: Do the following: Source: Master scheduler
v If the installation uses the System Modification Detecting Module: IEAVNP13
Program (SMP) or SMP Extended (SMP/E) to make
all changes, run SMP or SMP/E to list the current
maintenance and local modifications in the system. IEA864I GETMAIN FAILED FOR
{COMMNDxx|IEACMD00} - cmd
v If the installation makes any changes to the system
without using SMP, run the LIST service aid with a Explanation: During master scheduler initialization,
LISTIDR control statement to list all load modules the system processed a command contained in a
with maintenance changes or local modifications. Run parmlib member. The processing requested virtual
LIST against the following Libraries: storage for the system queue area (SQA). The request
SYS1.LINKLIB failed because there is not enough storage available.
SYS1.LPALIB
SYS1.SVCLIB In the message text:
Library containing the program that issued the COMMNDxx
message. The COMMNDxx parmlib member in which the
error occurred.
If the problem persists, search problem reporting data
bases for a fix for the problem. If no fix exists, contact IEACMD00
the IBM Support Center. Provide: The command was in the IEACMD00 parmlib
v The logrec data set error record member.
v The SVC dump, if available cmd
v The linkage editor output The command.
Source: Region control task (RCT) System Action: Depending on the message text, the
Detecting Module: IEAVAR00 system does the following:
IEACMD00
IEA863I dddddddddddddddd SPECIFICATION The system tries to process the COMMNDxx
INVALID IN {COMMNDxx|IEACMD00} parmlib members.
Explanation: During master scheduler initialization, COMMNDxx

the system detected one of the following errors: The system does not process any COMMNDxx
parmlib members.
v The system found a parameter other than the COM
parameter. System Programmer Response: Do the following:
v The value of a COM parameter is incorrect. 1. Make sure that sufficient SQA storage is available
for system initialization.
This is probably an error in the parameter.
2. If the problem continues, search problem reporting
dddddddddddddddd
16 characters of data from the erroneous record in
the parmlib member. Detecting Module: IEAVNP13
COMMNDxx
The COMMNDxx parmlib member in which the IEA865I SYSTEM ERROR DURING NIP
error occurred. PROCESSING OF prm PARAMETER -
IPL TERMINATED
IEACMD00
The error was found in the IEACMD00 parmlib Explanation: A system error was detected while
member. processing the parameter indicated. The error was
detected while attempting to prompt for the parameter
and could mean that processing modules have been
COM parameter and continues processing the parmlib
overlaid or some necessary data destroyed.
member.
prm The parameter indicated.
parameters in the parmlib member. Respecify any System Action: The system will enter disabled wait

state X'03D' displayed in the wait state program status device if dev is listed in message IEA860A, or if all
word (PSW). devices listed in message IEA860A have not become
ready. If the device was in the reply to message
Operator Response: Dump central storage and notify
IEA851A, the volume must have a serial number listed
the system programmer of this message. Then reIPL
in message IEA851A.
the system.
and the program is not in error, search problem Detecting Module: IEAVAP00
IEA872I INVALID IPS IN IEAIPSxx
Explanation: Processing for system resources
Detecting Module: IEAVNP05, IEAVNPC5 manager (SRM) initialization found incorrect installation
performance specification (IPS) data in the IEAIPSxx
parmlib member.
IEA866I VOLUME ser ON dev REQUIRED ON A
{devtyp|dev1} In the message text:
Explanation: During processing of a VATLSTxx IEAIPSxx
parmlib member, the system found the volume specified The parmlib member, where xx is the suffix of
in a VATDEF entry mounted on a device different from the member used.
the specified device type. In the message text:
System Action: The system ignores all IPS data in
ser The volume serial number specified in the VATDEF this member. The system writes message IEA906A to
entry. ask the operator to respecify the IPS parameter.
Diagnostic messages are written to the hardcopy log.
dev
The device number of the device on which the Operator Response: Write the hardcopy log (when it
specified volume is mounted. becomes available), correct the errors, then use the
SET IPS commands to begin using the corrected IPS.
devtype
In response to IEA906A, specify another valid IEAIPSxx
The device type specified in the VATDEF entry.
member or specify EOB (press ENTER) to continue
dev1 system initialization.
The device number of the device specified in the
System Programmer Response: Write the hardcopy
VATDEF entry.
log (when it becomes available) to see which diagnostic
System Action: If the volume is not premounted, the messages have been written. Correct the IPS
system unloads it. If the volume is premounted, the parameters in the IEAIPSxx member.
system issues message IEA947A.
If the IEAIPSxx member was correct, search problem
Operator Response: If the volume is unloaded, mount reporting data bases for a fix for the problem. If no fix
the correct volume on the device type or device exists, contact the IBM Support Center. Provide a listing
indicated. of the IEAIPSxx member.
Source: Allocation/unallocation Source: System resources manager (SRM)
Detecting Module: IEAVAP00 Detecting Module: IEAVNP10
IEA867I DUPLICATE VOLUME ser. UNIT dev IEA873I SKELETON IPS IN CONTROL - ALL
NOW UNLOADED. USERS AT SAME LEVEL
Explanation: In a VATLSTxx parmlib member, a Explanation: During system initialization, the system
VATDEF entry specified a volume serial number that found an error in the specified IEAIPSxx parmlib
duplicates the serial number of a volume already member. To continue operation, the system is using the
mounted. In the message text: skeleton installation performance specification (IPS).
The valid performance group numbers are 1 and 2. The
ser The duplicate volume serial number. system makes no distinction in the performance given to
dev problems in different performance groups.
The device number of the device on which the System Action: The system writes messages about
volume was mounted. the problem and continues processing.
System Action: The system unloaded the volume on Operator Response: Notify the system programmer.
device dev. Use the SET IPS command to specify a valid IPS that
Operator Response: Mount a different volume on the supersedes the skeleton IPS.

System Programmer Response: Correct the IEAVTSSD
IEAIPSxx parmlib member. The system writes no summary dumps.
If the IEAIPSxx member was correct, search problem IEAVTSDR
reporting data bases for a fix for the problem. If no fix The system does not process memory ends for
exists, contact the IBM Support Center. Provide a listing SVC dump recovery.
of the IEAIPSxx member.
IEAVTSSV
Source: System resources manager (SRM) The system writes no suspend summary dumps.
Detecting Module: IEAVNP10 IEAVTSXT
The system does not give control to the installation
exits for SVC dumps.
IEA874I INVALID OPT IN IEAOPTxx
ISGDSDMP
Explanation: Processing for system resources
manager (SRM) initialization found an incorrect
exits for SVC dump.
parameter value in the IEAOPTxx parmlib member.
IEAVTSEP
IEAOPTxx exits after SVC dumps.
The parmlib member, where xx is the suffix of
IARQDUMP
the member used.
The system may dump excessive amounts of virtual
System Action: The system ignores all OPT data in storage.
the member. The system writes message IEA906A to
ask the operator to respecify the OPT parameter. The module name can be for an installation-provided
post dump exit routine, if the exit name is specified in
Operator Response: In response to IEA906A, specify
IEAVTSEP and the routine is not in SYS1.LINKLIB.
another valid IEAOPTxx member or specify EOB (press
ENTER) to continue system initialization. Operator Response: Notify the system programmer of
this message. If requested by the system programmer,
System Programmer Response: Correct the OPT
reIPL the system.
parameters in the IEAOPTxx member.
System Programmer Response: Place the missing
If the IEAOPTxx member was correct, search problem
modules in the appropriate system library. Ask the
operator to reIPL the system to establish full SVC
exists, contact the IBM Support Center. Provide a listing
dumping.
of the IEAOPTxx member.
Source: System resources manager (SRM)
Detecting Module: IEAVTSDI, IEAVTDSV
IEA884I PARAMETERS INVALID FOR

IEA883I MODULE mmmmmmmm NOT FOUND
SYS1.PARMLIB MEMBER
Explanation: During system initialization, SVC dump mmmmmmmm
initialization processing cannot find a module in the link
Explanation: During system initialization, the parmlib
pack area (LPA), nucleus, or SYS1.LINKLIB system
member that specifies installation options for an ABEND
library.
dump contained incorrect parameters.
mmmmmmmm
mmmmmmmm
The name of the module that cannot be found.
The name of the parmlib member, which is one of
System Action: The system continues initialization. the following:
SVC dumping is impaired.
IEAABD00
If mmmmmmmm has the following values, system The installation options for SYSABEND dumps
action is the following: are not valid.
IGC005A IEADMP00
The installation options for SYSUDUMP dumps
IEAVTSPR are not valid.
IEAVTSDT IEADMR00
The system writes no SVC dumps. The installation options for SYSMDUMP dumps
are not valid.

System Action: One of the following: ss The second (00-59).
v If this message is followed by message IEA885I, the
parmlib member contains correct and incorrect Note: The apostrophes in the above reply are optional.
parameters. The system uses the correct options. If you include GMT in your reply, the system
converts the time and date to Greenwich mean
v If this message is not followed by message IEA885I,
time. If you omit GMT, the system assumes the
all options were incorrect. The system uses none of
values are the local time and date, converts them
the options.
to Greenwich mean time values, and sets the
Operator Response: Notify the system programmer. clock(s) with the Greenwich mean time.
System Programmer Response: Correct the parmlib Source: Timer supervision
member before the next system initialization.
Detecting Module: IEAVRTOD
Detecting Module: IEAVTABI IEA888A [GMT
DATE=yyyy.ddd,CLOCK=hh.mm.ss]
LOCAL
IEA885I VALID OPTIONS FOR SYS1.PARMLIB
DATE=yyyy.ddd,CLOCK=hh.mm.ss
MEMBER mmmmmmmm SDATA=
op,op,...,op PDATA= op,op,...,op
REPLY U, OR GMT/LOCAL TIME
Explanation: During system initialization, the parmlib
Explanation: This message displays the following:
member that specifies installation options for an ABEND
v The local time and date
dump contained incorrect parameters.
v The Greenwich mean time (GMT) and date
mmmmmmmm
The name of the parmlib member. yyyy.ddd
The year (4 digit year: 1900 - 2042) and the
op An SDATA or PDATA option.
day (001-366).
System Action: The system uses the correct dump
hh.mm.ss
options. The system ignores the incorrect options.
Operator Response: Notify the system programmer. (00-59).
System Programmer Response: Correct the parmlib System Action: The system prompts the operator for
member before the next system initialization. a reply.
Note: The system automatically issues message
Detecting Module: IEAVTABI IEA888A at IPL time if TOD=PROMPT is
included in the active CLOCKxx member of
SYS1.PARMLIB. See the OS/390 MVS
IEA886A TOD CLOCK(S) MUST BE SET
Initialization and Tuning Reference for details.
Explanation: The operator did not set the time-of-day
Operator Response: If the values shown in the text of
(TOD) clock(s).
message IEA888A are acceptable, reply ’U’. If you want
System Action: The system prompts the operator for to change the value of the time-of-day (TOD) clock,
a reply. When you enter a valid reply to message enter a new date, time, or both as follows:
IEA886A, the system issues message IEA903A. R id,‘[DATE=yyyy.ddd][,CLOCK=hh.mm.ss],GMT’
Operator Response: Use the following form of the
REPLY command to set the time of day clock. If you want to change the value of the local clock, enter
a new date, time, or both as follows:
R id,‘DATE=[yyyy.ddd[,CLOCK=hh.mm.ss][,GMT]’
R id,‘[DATE=yyyy.ddd][,CLOCK=hh.mm.ss]’
In the command text:
Note: The apostrophes in the above replies are
id The reply identifier. optional.
yyyy The year (4 digit year: 1900 - 2042).
If you specify a different TOD clock setting, the system
ddd The day (001-366). issues message IEA903A. If you omit ’GMT’, the the
hh The hour (00-23). system assumes the local date and/or time. Once you
have set the new time and/or date, the system reissues
mm The minute (00-59). message IEA888A with new values. Reply to the
message as previously described.

Notes:
IEA890I comnd FAILED- MEMORY COULD NOT
1. Resetting GMT time causes the TOD clock to be BE CREATED
reset. It also affects the local time. Respecifying
GMT time causes the local time value to be Explanation: comnd is one of the following:
recalculated using the new GMT and the system LOGON
time zone constant. MOUNT
START
2. Resetting local time does not affect GMT time or the
TOD clock. However, it will cause the system time
The system tried to create or initialize an address space
zone constant (which is initialized at IPL from the
for a command, but failed. The failure may be caused
CLOCKxx member of SYS1.PARMLIB) to be
by system overload or lack of paging space.
recalculated. The new time zone constant will
remain in effect until either local time is modified
again or the next IPL. If message IEA888A indicates In the message text:
that both GMT and local time values are incorrect, comnd
always reset the GMT values first. The command for which the system tried to create
3. The TOD clock should be set to a value based on or initialize an address space. comnd is one of the
zero being equivalent to 00 hours, 00 minutes, 00 following:
seconds on January 1, 1900 GMT. During an IPL, LOGON
the TOD clock might contain a value that, relative to MOUNT
this base, is not correct. This can happen, for START
example, when a customer engineer (CE) left the
System Action: The system deletes the partially
clock in the error state. In this case, to ensure that
created address space. The system does not process
the local time and date are correct, specify GMT
the command.
before setting the local time and date.
Operator Response: Enter the command again. If the
system issues this message again, notify the system
Detecting Module: IEAVRTOD programmer. ReIPL as requested by the system
programmer.
IEA889A REPLY U THEN DEPRESS TOD CLOCK System Programmer Response: If the system issued
SECURITY SWITCH this message while starting an initiator, the auxiliary
storage manager (ASM) may have run out of paging
Explanation: The time-of-day (TOD) clocks must be space. Ask the operator to reIPL, specifying larger or
synchronized because one of the following occurred: additional paging data sets. If these data sets are not
v A processor was varied online. available, modify ASM paging constant ASMSLOTC as
v A timing facilities damage machine check occurred. described in the system programmer response for wait
state code X'03C'. Ask the operator to reIPL with the
System Action: One of the following: existing page data sets.
v If the operator acknowledges receipt of the message
and presses the switch within 30 seconds, the
v If the operator does not press the switch within 30 IEA891I NO MAXUSER VALUE SPECIFIED,
seconds, or if the operator presses the switch and DEFAULT VALUE OF 255 USED
releases it before synchronization is complete, the Explanation: The IEASYSxx parmlib member does
system issues message IEA889A again. not specify a MAXUSER number. The system is using
Operator Response: Do the following: the default value of 255.
v Enter REPLY xx,‘U’ to acknowledge that you received System Action: The system continues processing.
this message.
v Press the security switch and hold it down for 5 to 10
seconds. Detecting Module: IEAVNP09
IEA892I MAXUSER=val1 RSVNONR=val2
Detecting Module: IEAVRTOD RSVSTRT=val3 SUM TOO LARGE FOR
AVAILABLE SQA
Explanation: The system could not obtain sufficient
storage from the system queue area (SQA) to build the
address space vector table (ASVT). One of the following
occurred:

v The sum of the MAXUSER, RSVNONR, and
IEA894I REQUESTED VOLUME ON
RSVSTRT values is too large.
UNREQUESTED UNIT. dev NOW
v The SQA is too small. UNLOADED.
In the message text: Explanation: During processing of a VATLSTxx

parmlib member, the system found a requested volume
val1 The value of MAXUSER in IEASYSxx mounted on a device that was not in the reply to
message IEA851A. In the message text:
val2 The value of RSVNONR in IEASYSxx
dev
val3 The value of RSVSTRT in IEASYSxx
The device number of a device that was not in the
System Action: The system prompts the operator to reply.
respecify the three parameters by issuing message
System Action: The system unloads the volume.
IEA906A three times: once each for MAXUSER,
RSVNONR, and RSVSTRT. Operator Response: Mount the volume on a
requested device if the attributes are to be processed.
Operator Response: Respond to message IEA906A
as the system programmer directs. Source: Allocation/unallocation
System Programmer Response: Do the following: Detecting Module: IEAVAP00
v Examine the size of the SQA.
v If a MAXUSER, RSVNONR, or RSVSTRT parameter IEA895A FORMAT ERROR. REPEAT REPLY.
value is too large, provide the operator with new
values for the parameters. Explanation: An error exists in the reply to message
IEA851A.
v Ask the operator to respond to message IEA906A
with the new values for the parameters. System Action: The system ignores the reply and
v Correct the parameters in the IEASYSxx member so waits for the operator to enter another reply.
that this message will not be issued during every Operator Response: Enter the reply again correctly,
system initialization using IEASYSxx. or reply ‘U’.
Source: Supervisor control Source: Allocation/unallocation
Detecting Module: IEAVNP09 Detecting Module: IEAVAP00
IEA893A NOT READY. REPLY U WHEN DEVICES IEA896I RECORDING FUNCTION NO LONGER
ARE READY, OR NO IF NOT ACTIVE
MOUNTING. dev,dev,...
Explanation: The recovery termination manager
Explanation: To complete processing of the (RTM) has stopped recording because of unrecoverable
VATLSTxx parmlib member, the system is waiting for errors. The system cannot do the following:
devices that are not ready. In the message text:
v Write logrec data set error records.
dev v Write to the operator for the WTO macro.
The device number of a device that is not ready.
System Action: The system does not process
System Action: The system waits for the operator to recording requests. Requesters receive a return code
ready the devices, then to respond. indicating that recording is no longer active.
Operator Response: When you have readied all of Operator Response: Notify the system programmer of
the volumes in message IEA851A that you require on this message. If requested by the system programmer,
the devices listed in message IEA860A, REPLY ‘U’ or reIPL the system.
press ENTER.
System Programmer Response: If recording is
If any devices have not been readied, message needed, ask the operator to reIPL the system.
IEA893A will be reissued, listing those devices.
Respond as above if there are more volumes to be Search problem reporting data bases for a fix for the
mounted. If no more volumes are to be mounted on the problem. If no fix exists, report the problem to the IBM
devices listed, REPLY ‘NO’. Support Center.
Source: Allocation/unallocation Source: Recovery termination manager (RTM)

REPLY U THEN DEPRESS TOD CLOCK SECURITY
IEA900I INVALID ICS IN IEAICSxx
SWITCH WHEN ENTERED TIME OCCURS, do the
Explanation: Processing for system resources following:
manager (SRM) initialization found an incorrect v Enter REPLY id,‘U’ to acknowledge that you received
parameter value in the IEAICSxx parmlib member. this message.
In the message text: v Press the security switch at the same time you
respond to message IEA888A or IEA886A.
IEAICSxx
The parmlib member, where xx is the suffix of
When the message reads REPLY U WHEN THE
the member used.
ENTERED TIME OCCURS, enter REPLY id,‘U’ at the
System Action: The system ignores all installation same time specified in message IEA888A or IEA886A.
control specification (ICS) data in this member. The
system writes message IEA906A to ask the operator to
respecify the ICS parameter. Diagnostic messages are Detecting Module: IEE6603D
written to the hardcopy log.
Operator Response: Write the hardcopy log (when it IEA907W UNABLE TO INITIALIZE PAGE AND/OR
becomes available), correct the errors, then use the SEGMENT TABLES FOR
SET ICS commands to begin using the corrected ICS. {CSA|SQA|LPA}
In response to IEA906A, specify another valid IEAICSxx
member or specify EOB (press ENTER) to continue Explanation: The system cannot initialize the system
system initialization. queue area (SQA), common service area (CSA), or link
pack area (LPA) because there is not enough central
System Programmer Response: Write the hardcopy storage available.
log (when it becomes available) to see which diagnostic
messages have been written. Correct the ICS System Action: The system enters wait state X'03D'.
parameters in the IEAICSxx member. Operator Response: Request a stand-alone dump.
If the IEAICSxx member was correct, search problem Notify the system programmer.
reporting data bases for a fix for the problem. If no fix System Programmer Response: Increase the
exists, contact the IBM Support Center. Provide a listing amount of central storage available to the system, or
of the IEAICSxx member. decrease the amount of virtual storage requested for the
Source: System resources manager (SRM) SQA, CSA or LPA.
Detecting Module: IEAVNP10 Source: Virtual storage manager (VSM)
IEA903A {REPLY U THEN DEPRESS TOD IEA908I QUICKSTART IS IN PROCESS - SQA

CLOCK SECURITY SWITCH WHEN PARM IS IGNORED - VALUES USED
ENTERED TIME OCCURS|REPLY U ARE nnnnK AND mmmmmmmK
WHEN THE ENTERED TIME OCCURS} Explanation: The requested system queue area
Explanation: The operator responded to message (SQA) size is not the same as the SQA size requested
IEA888A or IEA886A in a way that requires the at the previous system initialization. One of the following
time-of-day (TOD) clock to be set. occurred:
v A different SQA size was specified at quickstart
Message REPLY U WHEN THE ENTERED TIME
OCCURS is issued when you are running MVS under v The nucleus size increased since the previous
VM or PR/SM. system initialization
System Action: When the message reads REPLY U In the message text:
THEN DEPRESS TOD CLOCK SECURITY SWITCH nnnnK The size of the SQA for the duration
WHEN ENTERED TIME OCCURS and when the of this initial program load (IPL).
operator acknowledges receipt of the message, the
system attempts to set a TOD clock for a one-minute mmmmmmmK The size of the extended SQA for the
interval. If the operator does not press the security duration of this IPL.
switch during that interval, the system issues message System Action: The system defaults to the SQA size
IEA888A or IEA886A again. specified in message IEA908I. The system continues
When the message reads REPLY U WHEN THE processing.
ENTERED TIME OCCURS, the system starts the TOD Source: Virtual storage manager (VSM)
and continues processing.
Operator Response: When the message reads

| to allow the debugging of the
IEA909I {CSA|SQA} PARM SPECIFIED IS a,b.
| problem to be successful. The
ONLY xxxxxxxx OF VIRTUAL STORAGE
| codes in the SDRSN field can be
AVAILABLE FOR
| used to determine what storage
{CSA|SQA|ECSA|ESQA}
| was effected, or what problems
Explanation: The storage area requested for the | were encountered while SVC
system queue area (SQA) or common service area | dump processing was executing.
(CSA) is too large.
dumpid The 3–character dump identifier.
jobname The name of the job that requested
a,b The parameter that specified the amount of the dump.
virtual storage. The parameters are shown as
REMOTE DUMPS REQUESTED
they were specified in the IEASYSxx parmlib
member, where n is a decimal number of one The SDUMPX macro or DUMP
or more digits: command that requested this dump
v a can be n, nK, or nM also requested dumps on other
v b can be n, nK, or nM systems in the sysplex.
xxxxxxxx REMOTE DUMP FOR SYSNAME: sysname
The amount of virtual storage available.
The dump was requested by
System Action: The system issues message sysname, which is another system in
IEA906A. the sysplex.
Operator Response: See the operator response for INCIDENT TOKEN: incident-token
message IEA906A.
The formatted incident token for the
Source: Virtual storage manager (VSM) dump.
Detecting Module: IEAVNP08 SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz
The system wrote only a partial dump.
IEA911E {COMPLETE|PARTIAL} DUMP ON
SYS1.DUMPnn vvvvvvvv Partial dump reason code. One of the
following:
DUMPid=dumpid REQUESTED BY 80000000
JOB (jobname) A system request block (SRB) for
FOR ASIDS(id,id,...) the dump could not be scheduled
[REMOTE DUMPS REQUESTED|REMOTE to the requested address space.
DUMP FOR Either no current address space
SYSNAME:sysname] had the requested ASID or the
INCIDENT TOKEN:incident-token system was ending the address
[SDRSN = space with that ASID.
vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz]
[reason-text] 40000000
[ERRORID = SEQyyyyyy SVC dump processing could not
CPUzz ASIDasid obtain real storage manager
TIMEhh.mm.ss.f] (RSM) serialization because of a
[TSOID = tsoid] hierarchy problem.
[ID = uuuuuuuuuu] 20000000
Explanation: The system wrote a complete or partial SVC dump processing could not
SVC dump to a pre-allocated dump data set on a direct obtain RSM serialization because
access storage device (DASD) or a tape volume. of a RSM control problem.
In the message text: 10000000

SVC dump processing could not
COMPLETE The SVC dump was complete. obtain a central storage buffer
from the real storage manager.
PARTIAL The SVC dump was not complete.
08000000
| nn The dump was written to the
An error in scheduled SVC dump
| SYS1.DUMPnn data set. Not all
processing caused recovery to
| of the virtual storage requested
receive control.
| was collected. However, enough
| storage may have been dumped

04000000 04000000|02000000
An error in summary dump While processing an SVC dump,
processing caused recovery to the system detected an error and
receive control. gave recovery control.
02000000 01000000
An error in summary dump The started dump task failed.
processing or suspend summary
00800000
dump processing caused
A task abnormally ended, and
recovery to receive control.
SVC dump processing took a
00400000 partial dump. The resource
An error caused the loss of manager for SVC dump
summary dump. processing receives control.
00200000 00400000
During suspend summary dump The system detected an error in
processing, the virtual storage the SVC dump writing task and
buffer filled up. gave recovery control.
00100000 00200000
No more summary dump data An address space involved in the
could be written because the dump abnormally ended, and
central storage buffer was full. SVC dump took a partial dump.
The resource manager for SVC
0080000
dump processing receives control.
While the system was waiting for
writing a trace table, an error 00100000
occurred. The trace table could The DUMPSRV address space
not be written. abnormally ended, and SVC
dump processing took a partial
wwwwwwww Partial dump reason code. One of the
dump. The resource manager for
following.
SVC dump processing receives
00010000 control.
During dump processing of a
00080000
possibly hung address space, the
While processing the dump
address was found to be invalid.
header, the system ran out of
The dump data may not be
space to place data.
consistent.
00040000
00020000
During dump processing of local
storage, the system issued a
possibly hung address space,
PURGEDQ because a hung
dump processing obtained only
address space was detected. This
fixed storage for the address
s will result in the loss of some
space.
storage related to the address
80000000|40000000 space.
While processing SVC X’33’, the
00020000
system detected an error and
gave recovery control.
possibly hung address space,
20000000 dump processing obtained only
The system detected an error in fixed storage for the address
the SVC dump task and gave space.
recovery control.
00010000
10000000 During dump processing of a
The SVC dump task failed. possibly hung address space, the
address space was found to be
08000000 invalid. The dump data may not
The system detected an error be consistent.
while writing a trace table. The
system could not write the trace xxxxxxxx Partial dump reason code. One of the
table. following:

80000000 copying a sub-range of common
While building the address range storage into a data space, an
table for global storage areas, error occurred.
SVC dump processing filled the
00040000
table and remaining entries could
An error occurred in the
not be added.
processing of data spaces that
40000000 were requested through the
While building the address range LISTD keyword on the SDUMPX
table for local storage areas, SVC macro, or through the DSPNAME
dump processing filled the table parameter on the DUMP
and remaining entries could not command.
be added.
00020000
20000000 Dump processing could not add
While building the address range some ranges of read/write
table, SVC dump processing filled storage to the range table.
the table and remaining entries
00010000
could not be added.
SVC dump processing truncated
10000000 the dump because the maximum
While dump processing was amount of space was been
writing to the dump data set, an reached.
I/O error occurred.
00008000
08000000 While processing the SQA SDATA
The dump data set is full, but option, the system filled in the
more data needs to be dumped. range table.
04000000 00004000
An error occurred while writing While processing the CSA SDATA
the summary dump. option, the system filled in the
range table. Remaining entries
02000000
could not be added.
An error occurred while dump
processing was obtaining trace 00002000
data. While processing global subpools,
the system filled in the range
01000000
table. Remaining entries could not
While dump processing was
be added.
setting up the service request
block (SRB) under which the 00001000
dump was to be processed, an While processing the LSQA
error occurred. SDATA option, the system filled in
the range table. Remaining
00800000
An error occurred in an exit
routine. 00000800
While processing the RGN
00400000
SDATA option, the system filled in
An error occurred while writing
the end-of-data record to the
dump data set.
00000400
00200000
While processing private
Some read-only ranges of data
subpools, the system filled in the
could not be added to the range
range table. Remaining entries
table.
could not be added.
00100000
00000200
While processing the SWA
copying global storage into a data
SDATA option, the system filled in
space, an error occurred.
00080000 entries could not be added.

00000100 80000000
While copying global data into a Dump processing had reset the
data space, dump processing system dispatchable and dump
was unable to capture some processing failed or ended,
ranges of global storage. leaving the system set
non-dispatchable.
00000080
An exit data space could not be 40000000
created, or the data space was Dump processing had reset the
created but an ALET could not be tasks dispatchable in one or more
obtained to access the data address spaces involved in the
space. SVC dump. Then dump
processing failed or ended,
00000040
leaving the tasks
A summary data space could not
non-dispatchable.
be created, or the data space
was created but an ALET could 20000000
not be obtained to access the Dump processing reset the
data space. caller’s unit of work, which was
stopped as part of suspend
00000020
summary dump processing. Then
A local data space could not be
dump processing failed during
created, or the data space was
suspend summary dump
created but an ALET could not be
processing, leaving the caller
obtained to access the data
suspended.
space.
10000000
00000010
IEAVTSDB released serialization
A global data space could not be
for all serialized structures
created, or the data space was
specified in the STRLIST because
created but an ALET could not be
SDUMP appears to have failed or
obtained to access the data
ended.
space.
08000000
00000008
The central storage buffer
SVC dump could not create or
containing the summary dump
could not use the data spaces
was released when it was
that are required to process the
determined that dump processing
STRLIST request. Some data will
was hung. The summary dump
not be included in the dump.
was lost.
00000001
00800000
Facility not available. Some
the dump because a critical
structures will not be dumped.
shortage of auxiliary storage
existed. See the information for 00400000
message IRA201E to determine The structure is not available for
how to relieve the shortage. one of the following reasons:
zzzzzzzz Partial dump reason code. One of the v The system detected a
following: structure failure and the
structure cannot be accessed
Bits in the first byte indicate a
v The structure is not allocated
result that occurred because one or
more of the following conditions 00200000
may exist: No facility dump space is
v there is a shortage of central allocated or no facility dump
storage space is available because it is
being used to hold structure
v there is a shortage of auxiliary
dump tables for other structure
storage
dumps
v the DUMPSRV address space
dispatching priority is too low 00100000
Possible error in STRLIST

parameter list for one of the The dump data set is full, but
following reasons: more data needs to be dumped.
v The structure does not exist in The message indicates at what
the active policy point the data set became full.
v The structure type is not I/O ERROR - NO EOF WRITTEN -
compatible with the specified DUMP ENDED WHILE WRITING
range options {SUMDUMP|GLOBAL|LOCAL|STRLIST}
v A lock structure was requested. An I/O error occurred while the
SDUMP does not support lock system was writing to the dump
structures data set. The message indicates
the system was dumping at the
00080000 time of the I/O error.
Some or all of the STRLIST could
not be processed MAXSPACE LIMIT REACHED
WHILE CAPTURING DUMP
00040000 Insufficient space was available to
The system released structure capture the complete dump.
dump serialization before
capturing all the data. The system ERROR OCCURRED IN AN SDUMP
captured the rest of the data after EXIT
releasing serialization. ERROR OCCURRED IN AN SDUMP
00020000 LOCAL EXIT
Recovery received control while ERROR OCCURRED IN AN SDUMP
processing STRLIST GLOBAL EXIT
00010000 ERROR OCCURRED IN AN SDUMP
SVC dump was unable to EARLY GLOBAL EXIT
continue processing a structure
requested in the STRLIST ERROR OCCURRED IN AN SDUMP
parameter list. This may be ONE-TIME-ONLY EXIT
because the operator deleted the ERROR OCCURRED IN AN SDUMP
structure dump with the SETXCF DYNAMIC LOCAL EXIT
FORCE command.
ERROR OCCURRED IN AN SDUMP
00008000 DYNAMIC GLOBAL EXIT
Recovery received control while Dump processing encountered an
building the SDUMP signals for unexpected error in an SDUMP
other systems in the sysplex exit of the specified type.
reason-text One of the following: SOME STORAGE COULD NOT BE
SUMMARY DUMP INFORMATION DUMPED RC=rc
WAS LOST Storage could not be dumped. rc
A problem arose where can be one of the following:
processing was unable to 04 The system could not find the
complete a requested summary requested ASIDs.
dump. Refer to the description of
the SDRSN bits that are set to 08 Not all of the data requested
determine whether the data was in a summary dump could be
truncated, or completely lost. contained in the central
storage buffer or virtual
A CRITICAL AUXILIARY STORAGE storage buffer.
SHORTAGE EXISTED
| Note: Even though some
the dump because a critical
| summary dump
shortage of auxiliary storage
| records may be
existed. See message IRA201E
| missing, IEA911E
to determine how to relieve the
| COMPLETE DUMP
shortage.
| will be issued when
DUMP DATA SET FULL - DUMP | there are no other
ENDED WHILE WRITING | data truncation reason
{SUMDUMP|GLOBAL|LOCAL|STRLIST} | bits set. This indicates

| that the dump v The routine had detected that SVC
| contains all of the dump processing was not
| virtual storage continuing normally or had ended
| requested. Only the and left the structure serialized.
| summary dump v ACCESSTIME=ENFORCE was
| records are missing, specified on the dump request (or
| and these are usually defaulted) and the data requested
| duplicated in the in the STRLIST parameter list for a
| virtual storage requested structure was not
| dumped at a slightly completely processed within the
| later time.). time limit specified by the
12 Either (1) the internal SVC ACCESSTIME parameter on the
dump control blocks are full, IXLCONN macro.
so that some data was not ERROR OCCURRED IN SDUMP
dumped, or (2) dump Dump processing encountered an
processing received an error unexpected error.
return code when it tried to
dump the system trace. ERRORID = SEQyyyyyy CPUzz ASIDasid
TIMEhh.mm.ss.t
16 SVC dump was not able to The error identifier.
process all of the structures
specified in the STRLIST yyyyyy The sequence number
parameter list. zz The central processor
20 SDUMP processing could not address
collect the local storage of at asid The ASID for the address
least one of the normally space in which the error
collected storage address occurred
spaces involved in the dump.
Refer to the description of hh.mm.ss.t
the SDRSN bits that are set The time in hours (00
for more information. through 23), in minutes (00
through 59), in seconds (00
SYSTEM RESET DISPATCHABLE PRIOR TO DUMP through 59), and in tenths of
COMPLETION Dump processing failed or ended with a second (0 through 9).
the system set non-dispatchable. The
system detected the error and reset TSOID = tsoid The dump was generated for a SLIP
dispatchable. trap that was set in a Time Sharing
Option (TSO) session.
TASKS RESET DISPATCHABLE PRIOR TO DUMP
COMPLETION Dump processing failed or ended with tsoid The identifier of the TSO
tasks set non-dispatchable in one or user who defined the trap.
more address spaces involved in the
ID = uuuuuuuuuu
SVC dump. The system detected the
The component or subsystem
error and reset the tasks dispatchable.
identifier that was supplied in the ID
ENABLED CALLER RESET PRIOR TO DUMP keyword on the SDUMP or SDUMPX
COMPLETION Dump processing failed or ended macro.
during suspend summary dump
processing, leaving the caller
suspended. The system detected the Operator Response: To keep dump data sets
error and reset the caller’s unit of available, ask the system programmer to identify
work. SYS1.DUMPnn data sets that can be cleared. Then
enter DUMPDS commands to clear them.
STRUCTURE DUMP SERIALIZATION RELEASED
PRIOR TO DUMP COMPLETION System Programmer Response: Take the
The SVC dump time disabled appropriate action as indicated in the following
interruption exit routine released descriptions:
dumping serialization that was held for
DUMP DATA SET FULL - DUMP ENDED WHILE
a structure requested in the STRLIST
WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}
parameter list. Serialization was
Format the partial dump.
released because:

I/O ERROR - NO EOF WRITTEN - DUMP ENDED Detecting Module: IEAVTABD
WHILE WRITING
{SUMDUMP|GLOBAL|LOCAL|STRLIST}
IEA913I COMMON AREA BELOW 16M
Look at the logrec error records to determine the
EXCEEDS 8M by xxxxK
device problem. Contact hardware support.
Explanation: The size of the common area below 16
Format the partial dump. If a previous dump was in
megabytes is greater than 8 megabytes. This reduces
the dump data set, the data set may contain a
the size of the private area below 16 megabytes.
combination of the two dumps.
ERROR OCCURRED IN SDUMP
Obtain the logrec error record. Search the problem xxxxK The number of kilobytes by which the size of
reporting data bases for a fix for the problem. If no the private area below 16 megabytes is
fix exists, notify the IBM Support Center. Provide reduced.
the logrec error record.
SOME STORAGE COULD NOT BE DUMPED RC=16
Refer to the description of the SDRSN bits that are Source: Virtual storage manager (VSM)
set. Use the IPCS Sub-Command STRDATA to Detecting Module: IEAVNP08
format the list of structures that was requested to
be dumped. The reason that the structures were
not completely processed will be displayed. IEA915E SYNTAX ERROR IN IEASYSxx
CONTENTS, PROMPT FOLLOWS
Source: SVC dump
Explanation: Paging data set names are incorrect in
Detecting Module: IEAVTSDC the PAGE parameter of the IEASYSxx parmlib member.
IEA912I RECOVERY/TERMINATION DUMP
FAILED [DUE TO cde] IEASYSxx
Explanation: During recovery from an error, the
system requested an ABEND dump. The dump failed for System Action: The system issues a message to ask
one of the following reasons: the operator to respecify the PAGE parameter.
v An unopened data control block (DCB) was Operator Response: Respond to the message. Notify
referenced during validity checking. the system programmer.
v A task control block (TCB) address that is not valid System Programmer Response: Before the next IPL,
was referenced during validity checking. correct the contents of IEASYSxx according to the
v A page that was not valid was referenced during syntax for specifying paging space data set names.
validity checking.
v Storage was unavailable.
v The DCB type was not correct.
In the message text: IEA916E SYNTAX ERROR IN

{PAGE=|PAGTOTL=| NONVIO=}
DUE TO cde
SYSTEM PARAMETER, PROMPT
SYSMDUMP processing ended abnormally with a
FOLLOWS
completion code of cde.
Explanation: A system parameter contains a syntax
System Action: Except for the case where tasks are
error.
prematurely marked dispatchable, the system does not
write out the dump. System Action: The system issues message IEA906A
to prompt the operator to respecify the parameter, or to
System Programmer Response: Correct the original
press the ENTER button on the console.
failure and, if the message includes cde, the dump
failure. See the system programmer response for Operator Response: Reply to message IEA906A.
completion code cde. In the case where the tasks were Notify the system programmer.
prematurely made dispatchable, and enqueue lockout
situation was detected and allowed to clear up.
system parameter has the correct syntax.
However, the information in the dump must be carefully
validated because task processing might have changed Source: Auxiliary storage manager (ASM)
vital information in common and shared storage areas.
Detecting Module: ILRASRIM

Operator Response: Reply to message IEA922D, if
IEA918I PAGE DATA SET dsname NOT
issued. Notify the system programmer.
ACCEPTED
Explanation: The system could not use a page data
system initialization, verify that the page data set is
set because either:
cataloged in the master catalog.
v The auxiliary storage manager (ASM) is already
using the data set. Source: Auxiliary storage manager (ASM)
v This data set would exceed the limit of page data Detecting Module: ILRASRM2
sets.
IEA921I PAGE DATA SET dsname INVALID

Explanation: The catalog for a page data set does not
dsname
meet the requirements of a page data set. The device
may not be supported for paging, or the data set is not
System Action: The system continues initialization. If defined as previously known for paging.
the data set is already in use, the system issues
message IEA922D.
dsname
Operator Response: Do one of the following:
v If message IEA922D follows this message, the data
set is already in use. Respecify a data set name. System Action: If the page data set was to contain
PLPA pages, the system issues message IEA935W.
v If a page data set limit has been reached, notify the
The system ends initialization.
system programmer.
If the DUPLEX page data set is known from a previous
System Programmer Response: If this data set must
IPL and should be used under current IPL options, the
be used and some others should be omitted, respecify
system issues message IEA942I. Paging initialization
the paging data sets when restarting the system with
continues.
the CLPA or CVIO option.
If the page data set is known to paging initialization as
containing VIO pages which should be used under
Detecting Module: ILRASRIM current IPL options, the system issues message
IEA930I. Paging initialization continues.
IEA920I PAGE DATA SET dsname NOT In all other cases, the system issues message
LOCATED IEA922D.
Explanation: The system could not use a page data Operator Response: If the system issues IEA922D,
set because either: respecify the data set name. Otherwise, notify the
v The system could not locate a data set in the master system programmer.
catalog. System Programmer Response: Check catalog
v The master catalog information does not agree with information about this data set. If necessary, redefine it
expected and necessary attributes of a page data before the next system initialization.
set.
In the message text: Detecting Module: ILRASRM2
dsname
The name of the data set. IEA921I PAGE DATA SET dsname INVALID
System Action: The system continues initialization. Explanation: The catalog for a page data set does not
meet the requirements of a page data set. The device
If the data set was newly specified during this IPL, the
may not be supported for paging, or the data set is not
system issues message IEA922D to prompt the
defined as previously known for paging.
operator to respecify the data set name.
If PAGE is specified in the message text and the page
data set is known from a previous IPL as containing dsname
VIO pages that should be used under current IPL The name of the data set.
options, the system issues message IEA930I. The
System Action: If the page data set was to contain
system continues initialization.
PLPA pages, the system issues message IEA935W.
In all other cases, the system issues message The system ends initialization.
IEA922D.
If the page data set is known to paging initialization as

containing VIO pages which should be used under If the volume is to be provided (GO), initialization
current IPL options, the system issues message continues. The system issues a mount message. The
IEA930I. Paging initialization continues. data set is used.
In all other cases, the system issues message If the volume is to be ignored (IGNORE), initialization
IEA922D. continues without the data set.
Operator Response: If the system issues IEA922D, Operator Response: Either enter REPLY id,GO and
respecify the data set name. Otherwise, notify the prepare to mount the requested volume, or enter
system programmer. REPLY xx,IGNORE. Notify the system programmer of
this message if you reply IGNORE.
System Programmer Response: Check catalog
information about this data set. If necessary, redefine it System Programmer Response: Review space now
before the next system initialization. being used for paging, depending upon which type was
ignored. Ask the operator to enter the PAGEADD
command to help system performance if space was
Detecting Module: ILRASRM2 insufficient.
IEA922D REPLY ‘DSN=’ OR ‘IGNORE’
Explanation: This message allows the operator to
respecify a page data set name.
IEA924D VOLUME ser NEEDED FOR PAGE DATA
System Action: The system waits for the operator to SET WAS NOT MOUNTED; {CLPA MAY
reply. If the operator replies with a new data set name, BE FORCED|NEW PLPA DATA SET
the system processes the data set. If the operator MAY BE REQUESTED}; REPLY ‘GO’ OR
replies IGNORE, initialization either continues with the ‘IGNORE’
existing list of data sets, or the system enters wait state
Explanation: The system attempted to open a page
X'03C' if the data is:
data set on this volume, but discovered that the volume
v The PLPA page data set. was not mounted.
v The COMMON page data set.
v The only local page data set that is available to the
system. ser The volume serial number.
Operator Response: Do one of the following: CLPA MAY BE FORCED

The COMMON page data set resides on this
v Enter REPLY id,DSN= to specify the new data set
volume.
name.
v Enter REPLY id,IGNORE to continue with the data NEW PLPA DATA SET MAY BE REQUESTED
set. The PLPA page data set resides on this volume.
Notify the system programmer. reply. If the volume is to be provided (GO), paging
System Programmer Response: See the previously initialization continues. The system issues a mount
issued message. message. The data set is used.
Source: Auxiliary storage manager (ASM) In most cases, if the volume is not to be provided
(IGNORE), message IEA922D requests a new data set
Detecting Module: ILRASRM2 name.
If a quick or warm start is in progress, the PLPA page
IEA923D VOLUME ser NEEDED FOR PAGE DATA data set overflowed to the COMMON page data set.
SET WAS NOT MOUNTED; REPLY ‘GO’ The unmounted volume contains this COMMON page
OR ‘IGNORE’ data set. Initialization will force a cold start (CLPA) and
issue message IEA929I.
Explanation: The system could not open a page data
set because the volume was not mounted. The data set Operator Response: Either enter REPLY id,GO and
does not contain any pages of PLPA or VIO that would prepare to mount the requested volume, or enter
be missed with the IPL options in effect. REPLY id,IGNORE. Notify the system programmer.
In the message text: System Programmer Response: If a permanent
change is desired, update the IEASYSxx parmlib
member to reflect the new PLPA or COMMON page
System Action: The system waits for the operator to data set name. Otherwise, complete the IPL, correct the
reply. problem, and reIPL with the original data sets.

Source: Auxiliary storage manager (ASM) Detecting Module: IEAVNP1F
IEA927I PLPA AND COMMON PAGE DATA SETS
FULL FROM PREVIOUS IPL
IEA925D VOLUME ser NEEDED FOR PAGE DATA
SET WAS NOT MOUNTED; CVIO MAY Explanation: On a previous system initialization, the
BE FORCED; REPLY ‘GO’ OR ‘IGNORE’ PLPA and COMMON page data sets were filled up
during the write of the pageable link pack area (PLPA).
Explanation: When the system tried to open a page
The common storage area (CSA) and the rest of the
data set, the volume containing the data set was not
PLPA have no primary slots.
mounted. The volume contains pages of VIO data sets
that may be required for recovery of one or more VIO System Action: Initialization continues with the
data sets. DUPLEX page data set. If there is no DUPLEX page
data set, the system issues message IEA935W.
System Programmer Response: If a warm start is
necessary to clean up work in the system, ensure that
reply.
the previous DUPLEX page data set is usable, then ask
If the volume is to be provided (GO), initialization the operator to reIPL. Otherwise, redefine the PLPA and
continues. The system issues a mount message. The COMMON page data sets, then ask the operator to
page data sets on that volume are used. reIPL with the CLPA option.
If the volume is not provided (IGNORE), initialization Source: Auxiliary storage manager (ASM)
continues without page data sets on that volume. In
addition, the CVIO option will be in effect, causing all
VIO data sets from previous IPLs to be unrecoverable.
IEA928I MODULE AT LOCATION xxxxxx IN PLPA
Operator Response: Either enter REPLY id,GO and
CONTAINS HOLES
prepare to mount the requested volume, or enter
REPLY xx,IGNORE. Notify the system programmer of Explanation: One of the following occurred:
this message if the volume is not made available. 1. While building the paging information for the
System Programmer Response: Review paging pageable link pack area (PLPA) during a cold start
space because the CVIO option is in effect (CLPA IPL), the system found an incorrect external
unexpectedly. Only data sets specified on this IPL will page table entry for a PLPA module.
be used. Consider asking the operator to enter the 2. While restoring paging information for PLPA during a
PAGEADD command. warm or quick start (not a CLPA IPL), the system
found an external page table entry for a PLPA
module that contained zero, indicating that condition
Detecting Module: ILRASRM1 1 occurred during cold start.
These conditions indicate that the module in the PLPA

IEA926I INVALID SYNTAX FOR CMB KEYWORD
contains non-contiguous code or large constant areas
Explanation: The parameter string of the channel on the page referenced by the page table entry. This
measurement block (CMB) keyword in the IEASYSxx condition should not occur in a PLPA module.
parmlib member is incorrect.
System Action: The system ignores all data in the
CMB keyword. The system writes a message to ask the xxxxxx The address of the module.
operator to respecify the CMB keyword and its
System Action: Paging initialization processing marks
parameter string.
the external page table entry as incorrect. Initialization
Operator Response: Reply to the prompting message processing continues. Any address space that
with a valid CMB keyword or specify EOB (press subsequently references this PLPA page will abnormally
ENTER). end with abend code X'028'.
System Programmer Response: Verify the CMB Operator Response: Notify the system programmer.
keyword and its parameters in the IEASYSxx member. If
System Programmer Response: Use the current LPA
the parameters are correct, search problem reporting
map to identify the module containing virtual address
xxxxxx. Correct the module. Ask the operator to IPL,
specifying the CLPA system parameter.

Detecting Module: ILRQSRIT System Programmer Response: Obtain the SYSOUT
output for the job.
IEA929I CLPA FORCED Collect all printed output and output data sets related to
the problem. Search problem reporting data bases for a
Explanation: Initialization cannot continue without the
CLPA option. A cold start is forced.
Support Center.
System Action: Initialization continues as if CLPA had
been specified.
System Programmer Response: Look for the
IEA933I UNABLE TO LOAD FORMAT
messages that preceded this message.
APPENDAGE xxx. FURTHER RCDS
Source: Auxiliary storage manager (ASM) REQUIRING THIS MOD WILL BE
DUMPED IN HEX
Explanation: Generalized trace facility (GTF)
formatting module was unable to load a format
IEA930I CVIO FORCED appendage.
Explanation: Initialization cannot continue without the In the message text:
CVIO option. All VIO data set pages are cleared.
xxx The format appendage.
System Action: Initialization continues as if CVIO had
been specified. System Action: The system continues formatting GTF
buffers, dumping in hexadecimal any record that
Operator Response: Notify the system programmer. requires the format appendage for editing.
System Programmer Response: Look for the System Programmer Response: Collect all printed
messages that preceded this message. output and output data sets related to the problem.
Source: Auxiliary storage manager (ASM) Search problem reporting data bases for a fix for the
Detecting Module: ILRASRIM Center.
IEA931I ESTAE REQUEST FOR GTF TRACE
FORMATTING FUNCTION Detecting Module: IGC0F05A
UNSUCCESSFUL
Explanation: The recovery environment requested by IEA934I INVALID RETURN CODE RECEIVED
the generalized trace facility (GTF) was not established. FROM mod. FURTHER RCDS
REQUIRING THIS MOD WILL BE
System Action: The system does not format any GTF DUMPED IN HEX
buffers.
Explanation: The system detected an incorrect return
System Programmer Response: Obtain the SYSOUT code on return from a module.
output for the job.
Collect all printed output and output data sets related to
the problem. Search problem reporting data bases for a mod The name of the module.
fix for the problem. If no fix exists, contact the IBM System Action: The system continues formatting GTF
Support Center. buffers, dumping in hexadecimal any record that
Source: Generalized trace facility (GTF) requires this module for editing.
Detecting Module: IGC0F05A System Programmer Response: Collect all printed

IEA932I INSUFFICIENT STORAGE FOR GTF problem. If no fix exists, contact the IBM Support
BUFFER FORMATTING Center.
Explanation: There is insufficient system queue area Source: Generalized trace facility (GTF)
(SQA) for generalized trace facility (GTF) buffer
formatting. Detecting Module: IGC0F05A
System Action: The system does not format any GTF

buffers.

wrong level of the COMMON page data set is
IEA935W INSUFFICIENT PAGING RESOURCES,
accessed, system operation continues with a cold start
IPL TERMINATED
(CLPA IPL) forced.
Explanation: To support minimal paging, there must
be a minimum number of paging data sets with a
minimum number of system-page-sized slots in a System Programmer Response: If the system
certain distribution available. The system determined entered a wait state, correct or replace the COMMON
that these requirements are not available. page data set. Then ask the operator to reIPL with the
CLPA option.
System Action: System initialization stops. The
system enters a wait state. If the system did not enter a wait state, and a warm
start is necessary, stop the IPL. Make the correct level
COMMON page data set available. Then ask the
the wait state.
operator to reIPL.
programmer response for the wait state.
IEA938W NO STORAGE AVAILABLE, PAGING
INITIALIZATION TERMINATED
IEA936D FUTURE QUICK AND WARM STARTS
Explanation: A request for additional storage failed
OF THIS IPL WILL FAIL. RE-IPL OR
during initialization. The maximum size of the system
REPLY ‘GO’ TO CONTINUE COLD
queue area (SQA) specified has probably been
START
exceeded.
Explanation: On a system initialization with the CLPA
System Action: System initialization stops. The
option, the system needed to write quick/warm start
system enters a wait state.
data to the first records of the PLPA page data set.
However, the write failed. None of the information will Operator Response: Notify the system programmer.
be accessible to a future initialization.
System Programmer Response: Ensure that enough
System Action: The system waits for the operator to SQA is requested. If not, increase the SQA maximum
reply. size.
Operator Response: Notify the system programmer. Otherwise, the system configuration may be too small.
Enter REPLY id,GO to continue with the cold start, or
reIPL at the system programmer’s request. Possibly, an error occurred in the system. Search
System Programmer Response: When using this no fix exists, contact the IBM Support Center.
PLPA page data set again, ask the operator to perform
an IPL with the CLPA option. Source: Auxiliary storage manager (ASM)
Source: Auxiliary storage manager (ASM) Detecting Module: ILRASRM2
Detecting Module: ILRQSRIT

IEA939D QUICK AND WARM START DATA IS
INVALID, RE-IPL OR REPLY ‘GO’ FOR
IEA937I COMMON PAGE DATA SET COLD START
TIMESTAMP FAILURE
Explanation: A system initialization without the CLPA
Explanation: When this message is followed by option was attempted. Information on the PLPA paging
message IEA935W, the system could not read or write data set was inaccessible:
the time stamp record in the COMMON page data set. v The specified PLPA paging data set must be the
The time stamp is written on initializations with the same as that used on the previous successful cold
CLPA option; it is written on initializations without the start (CLPA IPL).
CLPA option if part of the PLPA was written to the
COMMON page data set. v If the same data set was being used, then the system
could not read the necessary information.
When this message is followed by message IEA929I,
the system read the time stamp in the COMMON page System Action: The system waits for the operator to
data set, but the time stamp failed to match the time reply.
stamp of the PLPA slot information. Operator Response: Either enter REPLY id,GO if a
System Action: If unable to access the COMMON cold start is desired, or reIPL with a different data set
page data set, the system enters a wait state. If the specified for PLPA paging. Notify the system
programmer.

IEA942I DUPLEXING INACTIVE, {NO DATA
correct IEASYSxx parmlib member is being used. Also,
SET|BAD TIME STAMP}
verify the previous use of the PLPA paging data set.
Explanation: A DUPLEX page data set and the CLPA
option were specified either on the current initialization
Detecting Module: ILRASRIM or on the CLPA IPL for which the current initialization is
based. While trying to use the DUPLEX page data set,
the system detected an error.
IEA940I THE FOLLOWING PAGE DATA SETS
ARE IN USE: In the message text:
NO DATA SET
PLPA ... dsname A preceding message indicates the error.
COMMON . dsname
LOCAL .. dsname BAD TIME STAMP
. If the CLPA option was specified or forced, the
. attempt to write a time stamp to the first record of
. the data set failed. If the CLPA option was not
used, the attempt to read the time stamp failed or
Explanation: This message is issued if L is specified the time stamp no longer matched that of the PLPA
on the PAGE system parameter, or if the system has slot information.
been forced to change the list of page data sets
originally specified. The list of data sets should help the System Action: Initialization continues without
operator verify which paging volumes are in use, duplexing.
especially after a warm start where data sets used on
Operator Response: To restore duplexing, perform a
the previous initialization were not specified on this
cold start (CLPA IPL) with the DUPLEX page data set
initialization.
specified. If necessary, replace or correct the DUPLEX
In the message text: page data set.
dsname Source: Auxiliary storage manager (ASM)

System Action: Initialization continues.
Source: Auxiliary storage manager (ASM) IEA943W FAILURE DURING SAVE OR REBUILD
OF PLPA
Explanation: For an initialization without the CLPA
option, the system attempted to restore paging
IEA941D VOLUME ser NEEDED FOR DUPLEX information for the PLPA data set into the page tables
DATA SET NOT MOUNTED DUPLEXING representing the PLPA. However, the page table could
MAY BE STOPPED, REPLY ‘GO’ OR not be found or PLPA slot information was incorrect.
‘IGNORE’
For a cold start (CLPA IPL), the system attempted to
Explanation: The system attempted to open a volume, save paging information found in page tables
but discovered that the volume was not mounted. If representing the PLPA. However, a page table could not
duplexing is desired for this initialization, the volume be found.
must be mounted.
System Action: The system ends initialization and
In the message text: enters wait state X'061'.
ser The volume serial number. Operator Response: Notify the system programmer.
System Action: The system waits for the operator to ReIPL with the CLPA option.
reply. If the volume is to be provided (GO), initialization System Programmer Response: See the operator
continues; the system issues a mount message and response for wait state X'061'.
uses the data set. If the volume is not provided
(IGNORE), initialization continues without duplexing. Source: Auxiliary storage manager (ASM)
Operator Response: Either enter REPLY id,GO and Detecting Module: ILRASRIM
prepare to mount the requested volume, or enter
REPLY id,IGNORE.
IEA944I QUICK OR WARM STARTS FROM THIS
Source: Auxiliary storage manager (ASM) IPL WILL HAVE RANDOM RESULTS
Detecting Module: ILRASRIM Explanation: On a quick or warm start, an attempt to
write page data set information to the PLPA page data
set has failed. The failure might have destroyed

previous information or might have just left the installation procedures to increase the central storage
information down level. Further use of the information requirements.
would, therefore, cause unpredictable results.
Source: Virtual storage manager (VSM)
System Action: Initialization continues.
Detecting Module: IGVVSCEL
Be sure that the device containing the PLPA page data
IEA947A REPLY U TO CONTINUE, OR RE IPL.
set is not in READ ONLY status.
If the present IPL status is either specified or forced
parmlib member, the system found a system volume,
CVIO, and it is desired to do an IPL without the CVIO
specified in message IEA866I, that is not mounted on
option, then stop the current IPL. If the present IPL did
the device type specified in the VATLST entry.
not specify the CVIO option, continue with the current
IPL only to clear up previous VIO-related jobs. System Action: The system waits for the operator to
reply.
ReIPL according to the system programmer’s
instructions. Operator Response: If the wrong volume was
mounted for IPL, mount the correct volume. If the
System Programmer Response: Evaluate the PLPA
correct volume is mounted, REPLY ‘U’ to continue, and
page data set, and replace or redefine, as necessary.
notify the system programmer of the VATLST entry
Then, ask the operator to reIPL with this PLPA page
error. If you reply ‘U’, the system will ignore the
data set and with the CLPA option.
attributes of the volume and they will remain public.
IEA945W UNABLE TO USE CLOCK FOR

IEA948I dev NOW UNLOADED.
TIMESTAMP
Explanation: On a system initialization with CLPA or
parmlib member, the system unloaded a volume. In the
CVIO specified or forced, the system could not obtain a
message text:
unique time stamp to mark corresponding information
and data sets. dev
The device number of the device from which the
System Action: Initialization ends. The system enters
volume was unloaded.
wait state X'061'.
System Action: The system unloads the volume.
wait state X'061'. Operator Response: See the operator response for
preceding message, either message IEA854I or
IEA866I.
IEA946W NO {VIRTUAL|REAL} STORAGE
AVAILABLE FOR SQA
IEA949I I/O ERROR READING VATLSTxx.
Explanation: During processing for a GETMAIN or a
FREEMAIN macro, the system found that no storage Explanation: During processing of a VATLSTxx
was available in the system queue area (SQA) to back parmlib member, the system detected an uncorrectable
the storage request. I/O error. If message IEA949A does not appear, then
the system had not processed any VATDEF entries
System Action: The system enters one of the
before the error occurred.
following wait states:
v X'101' for a virtual storage request System Action: The system may issue message
v X'102' for a central storage request IEA949A to prompt the operator for a reply.
Operator Response: Restart the system. If the Operator Response: If message IEA949A appears,
system displays this message frequently, contact the see the operator response for that message.
system programmer.
System Programmer Response: See installation
procedures to increase the space allowed for the SQA. Detecting Module: IEAVAP00
If the system displays this message frequently, see

Operator Response: Notify to the system
IEA949A REPLY YES FOR LIST OF ENTRIES
programmer.
THAT WILL BE PROCESSED, OR U
FOR NO LIST. System Programmer Response: Rebuild IEAAPP00
prior to the next IPL for.
reply to message IEA949I. Source: DFSMSdfp
System Action: The system waits for the operator to Detecting Module: IEAVNP16
reply.
Operator Response: REPLY ‘YES’ for a list of entries IEA959I ERROR CAUSED ACTIVE LPA TO BE
(encountered before the error occurred) that will be TRUNCATED, MODULE CONTROL MAY
processed, or ‘U’ if you do not want a list. BE LOST
Source: Allocation/unallocation Explanation: Recovery from a system error required
the active link pack area (LPA) to be truncated. This
means that modules in the LPA may no longer be
invocable and attempts to use them may cause
IEA950I MODULE mod NOT FOUND; MC abnormal ending or unpredictable results.
ROUTING INACTIVE
Explanation: A module was not found in the link pack The system writes a logrec data set error record.
area (LPA). The system will be unable to initialize the
Operator Response: Report this message to the
generalized trace facility (GTF).
system programmer. If frequent abnormal endings
In the message text: occur, reIPL may be necessary. Obtain a stand-alone
dump if the system programmer requests one.
mod The name of the module.
System Programmer Response: To use GTF, ensure exists, contact the IBM Support Center. Provide the
that the following modules are present in LPA: logrec data set error record and the stand-alone dump,
AHLSETEV if available.
AHLSETD
AHLMCER
After updating the necessary libraries with these IEA964I HARDCOPY SUSPENDED,
modules, reIPL the system to initialize GTF. REASON=xxxx, NO HARDCOPY
DEVICE AVAILABLE
Explanation: The device used to receive the
Detecting Module: IEAVNP17 hard-copy log, or scheduled to receive the hard-copy
log, is unavailable. The system cannot switch the
IEA958I EXCP APPENDAGE NAME TABLE NOT hard-copy log to the system log or to an appropriate
BUILT console because neither is available.
Explanation: During system initialization, the nucleus In the message text:

initialization program (NIP) accessed the IEAAPP00 xxxx The reason code, as follows:
parmlib member to build a table of valid modules that
may be loaded as run channel program (EXCP) ATTRES
appendages. Due to an I/O error or to a syntax error in The master console was varied offline
IEAAPP00, NIP could not complete construction of this after a failure.
table.
KV The operator entered a CONTROL V,
If installation supplied modules are being loaded as USE=FC command to relieve a no
appendages for a data control block (DCB) with consoles condition.
MACRF=(E), the modules must operate in protection
VARY The operator varied a console online
key 0-7 or be authorized under authorized program
to relieve a no consoles condition.
facility (APF).
CQUEER
System Action: If unauthorized installation-supplied
The system cannot obtain the console
appendages are loaded for a DCB with MACRF=(E),
queue element (CQE).
the system issues abend code X'913'with a return code
X'20'. HCSW The hard-copy log was switched from
the system log.

EXT The operator pressed the external
IEA967W UNSUCCESSFUL RECOVERY
interrupt key.
ATTEMPT BY SUPERVISOR CONTROL
IOER An I/O error occurred on the failing
Explanation: Supervisor control experienced a double
console.
recursive abnormal end in its super functional recovery
SWER A software error occurred for the routine (FRR). This is a probable software error.
failing console.
System Action: The system enters wait state X'01C'.
VMST The operator entered a VARY
MSTCONS command.
wait state X'01C'.
OPER An open failure occurred for the
console.
programmer response for wait state X'01C'.
CFCHP
The operator entered a CONFIG CHP
command. Detecting Module: IEAVESPR
SFAIL A system in the sysplex failed.
IEA989I SLIP TRAP ID=xxxx MATCHED. [text]
SINIT A system in the sysplex completed
initialization, causing a change in the Explanation: A SLIP command had set a SLIP trap
console configuration. which requested that a dump be suppressed. All
conditions defined by the SLIP trap were met, and the
System Action: Processing continues. The system
system has suppressed the dump. The system issues
does not save messages processed when no hard-copy
this message to hardcopy only.
log is available.
Operator Response: Issue the VARY
{devnum|SYSLOG},HARDCPY command to restart the ID=xxxx
hardcopy log. Either an actual hardcopy printer device The SLIP trap identifier specified on the SLIP
can be specified, or SYSLOG may be used if you want command.
the system log to be the hardcopy log.
text
Source: Communications task (COMMTASK) One of the following:
Detecting Module: IEAVSWCB JOBNAME=jobname,ASID=asid
The name of the job associated with the home
address space and the address space identifier
IEA966I NO SRM DEVICE SELECTION OR I/O
(ASID) of the home address space at the time
LOAD BALANCING
of the error or PER interrupt. If the job name is
Explanation: The system could not obtain central not available, but the ASID is available, the
storage to build channel measurement blocks (CMB). jobname is *UNAVAIL.
Device allocation and I/O load balancing use these
JOBNAME/ASID NOT AVAILABLE
channel measurements.
The job name and ASID of the home address
System Action: The system continues processing with space at the time of the error.
the device allocation and I/O load balancing algorithms
System Action: The system suppresses the dump
operating without I/O measurement data. The system
and continues processing.
writes messages about the problem.
Source: SLIP
Operator Response: Configure additional central
storage. Notify the system programmer. Detecting Module: IEAVTSL2
REAL, SQA, and CSA parameters are properly defined IEA990I {REAL|VIRTUAL} STORAGE NOT
in the IEASYSxx parmlib member. AVAILABLE FOR {CMB|OPTIONAL
CMB ENTRIES|CPMF INTERFACE|IOS
If the parameters are correct, search problem reporting
INTERFACE}
contact the IBM Support Center. Explanation: The system could not obtain enough
central (real) or virtual storage for the channel
measurement block (CMB) or for the channel path
Detecting Module: IEAVNP1F measurement facility (CPMF).
System Action: Depending on the message text, the
system does the following:

STORAGE NOT AVAILABLE FOR CMB ID=xxxx
The system continues processing, but the SRM The SLIP trap identifier specified on the SLIP
channel measurement facility is unavailable for command.
device selection and I/O load balancing for the
text
duration of this IPL. The system writes message
IEA966I.
JOBNAME=jobname,ASID=asid
OPTIONAL CMB ENTRIES
The name of the job associated with the home
The system writes a message to ask the operator
address space and the address space identifier
to respecify the CMB keyword.
(ASID) of the home address space at the time
{CPMF INTERFACE|IOS INTERFACE} of the error or PER interrupt. If the job name is
The system continues processing without the use of not available, but the ASID is available, the
CPMF. jobname is *UNAVAIL.
Operator Response: Check the available central JOBNAME/ASID NOT AVAILABLE
storage to see if it is properly configured. The job name and ASID of the home address
space at the time of the error or PER interrupt
are not available.
allocation of storage for the common service area (CSA)
is properly specified. If the message reads OPTIONAL System Action: The system continues processing.
CMB ENTRIES, ensure that the CMB system parameter
If the SLIP command specified ACTION=WAIT, the
is properly specified in the IEASYSxx parmlib member.
system will enter wait state X'01B'. Ordinarily, the
Source: System resources manager (SRM) system enters the wait state before issuing this
message, but, due to timing within the system, the
Detecting Module: IEAVNP1F
system may issue this message before entering the
wait.
IEA991I SRM CHANNEL DATA NO LONGER
AVAILABLE FOR I/O SERVICE
System Programmer Response: If a wait state
Explanation: One of the following occurred:
occurs, look at the data in message IEE844W.
v The channel measurement facility is not measuring
device connect time intervals (DCTI) because of a Source: SLIP
failure in a channel or processor Detecting Module: IEAVTSL2
v Storage is not available for a required system
resources manager (SRM) parameter list
IEA993I SYSMDUMP TAKEN TO dsname
System Action: SRM uses the execute channel
Explanation: The system wrote a SYSMDUMP dump
program (EXCP) counts from address space control
to the data set specified on the SYSMDUMP DD
blocks (ASCBs) to calculate I/O activity.
statement. The dump is a complete dump.
Operator Response: If the system programmer
designated an IEAIPSxx parmlib member to be used
when device connection times are not available, enter a dsname
set command for that IEAIPSxx member. Notify the The data set name.
system programmer.
reason for the lack of storage. Search problem reporting Source: Recovery termination manager (RTM)
data bases for a fix for the problem. If no fix exists, Detecting Module: IEAVTABD
Source: System resources manager (SRM) IEA995I SYMPTOM DUMP OUTPUT
Detecting Module: IEAVNP1F
text
IEA992I SLIP TRAP ID=xxxx MATCHED. [text] Explanation: Where text is:
{SYSTEM|USER} COMPLETION CODE=cde [REASON CODE=reason-code]
Explanation: A SLIP command had set a SLIP trap. TIME=hh.mm.ss SEQ=sssss CPU=cccc ASID=asid
PSW AT TIME OF ERROR xxxxxxxx xxxxxxxx ILC x INTC xx
All conditions defined by the SLIP trap were met. The { ACTIVE LOAD MODULE ADDRESS=aaaaaaaa OFFSET=nnnnnnnn |
system has performed the requested action. NO ACTIVE MODULE FOUND}
{NAME=load-module-name|NAME=UNKNOWN}
{DATA AT PSW hhhhhhhh - dddddddd dddddddd dddddddd |
In the message text: DATA AT PSW IS INACCESSIBLE BY USER |
DATA AT PSW IS UNAVAILABLE AT THIS TIME}

ADDRESS=aaaaaaaa
registers
Address of the load module, if the PSW points to
END OF SYMPTOM DUMP one of the following:
v A module running under the current task
The system issues this message, which is the symptom v A module loaded by the current task.
dump, for all abnormal ends when a SYSABEND,
SYSUDUMP, or SYSMDUMP is requested. You can use NAME=load-module-name
the information in this message to assist in problem Load module name, if the PSW points to an active
determination. load module.
NAME=UNKNOWN
If you want to suppress this message on your system, The system cannot ascertain the load module name
do one of the following: because the PSW does not point to an active load
v Use the message processing facility (MPF) module.
v Stop the system from generating symptom dumps by OFFSET=nnnnnnnn
adding the SDATA=NOSYM option to the Offset into the load module of the failing instruction,
SYSABEND, SYSUDUMP, or SYSMDUMP dump if the PSW points to an active load module.
options. You can specify the SDATA=NOSYM dump
option in the following ways: DATA AT PSW hhhhhhhh - dddddddd dddddddd
dddddddd
– Use the CHNGDUMP command from an operator
Address in the PSW minus six, followed by the
console.
contents of the three words beginning at the
– Specify NOSYM in the IEAABD00, IEADMP00, address in hhhhhhhh.
and IEADMR00 parmlib members.
registers
In the message text: The content of the general purpose registers at the
time of error. If the PSW at the time of error is in
SYSTEM COMPLETION CODE=cde AR ASC mode, the access registers will appear.
The system completion code from the ABEND For a detailed description of the registers displayed,
macro. see the following explanations.
USER COMPLETION CODE=cde
The user completion code from the ABEND macro. The registers displayed in this message include all
registers that contain something other than zero. The
REASON CODE=reason-code output varies depending on whether the system is
The reason code, if specified in the ABEND macro. running in ESA/390 or z/Architecture mode, whether the
TIME=hh.mm.ss ARs are all zero, and whether the high halves of the
The time that the dump was written in hours (00 GPRs are all zero.
through 23), in minutes (00 through 59), and in
seconds (00 through 59). Case 1: The system is running in ESA/390 mode (or
z/Architecture mode when all the high halves of the
SEQ=sssss GPRs are zero) and all ARs are zero:
Sequence number for the dump. GR 0: gggggggg 1: gggggggg
2: gggggggg 3: gggggggg
CPU=cccc 4: gggggggg 5: gggggggg
6: gggggggg 7: gggggggg
The central processor identifier. If cccc is 0000, the 8: gggggggg 9: gggggggg
system did not determine on which processor the A: gggggggg B: gggggggg
C: gggggggg D: gggggggg
abend occurred. E: gggggggg F: gggggggg
ASID=asid
The address space identifier (ASID) of the failing Case 2: The system is running in ESA/390 mode (or
task. z/Architecture mode when all the high halves of the
GPRs are zero) and not all ARs are zero:
PSW AT TIME OF ERROR xxxxxxxx xxxxxxxx AR/GR 0: aaaaaaaa/gggggggg 1: aaaaaaaa/gggggggg
The program status word (PSW) at the time of 2: aaaaaaaa/gggggggg 3: aaaaaaaa/gggggggg
4: aaaaaaaa/gggggggg 5: aaaaaaaa/gggggggg
error. 6: aaaaaaaa/gggggggg 7: aaaaaaaa/gggggggg
8: aaaaaaaa/gggggggg 9: aaaaaaaa/gggggggg
ILC x A: aaaaaaaa/gggggggg B: aaaaaaaa/gggggggg
C: aaaaaaaa/gggggggg D: aaaaaaaa/gggggggg
Instruction length code for the failing instruction. E: aaaaaaaa/gggggggg F: aaaaaaaa/gggggggg
INTC xx
Interrupt code for the failing instruction. Case 3: The system is running in z/Architecture mode,
the high halves of the GPRs are not all zero, and and
ACTIVE LOAD MODULE all ARs are zero:
GR 0: gggggggg_gggggggg 1: gggggggg_gggggggg
2: gggggggg_gggggggg 3: gggggggg_gggggggg

6: gggggggg_gggggggg 7: gggggggg_gggggggg System Programmer Response: Do the following:
A: gggggggg_gggggggg B: gggggggg_gggggggg v Look at the messages in the job log.
C: gggggggg_gggggggg D: gggggggg_gggggggg
E: gggggggg_gggggggg F: gggggggg_gggggggg v Collect all printed output and output data sets related
to the problem.
Case 4: The system is running in z/Architecture mode,
v Obtain the program listing for the job.
the high halves of the GPRs are not all zero, and the
ARs are not all zero: Source: Recovery termination manager (RTM)
AR/GR 0: aaaaaaaa/gggggggg_gggggggg 1: aaaaaaaa/gggggggg_gggggggg
2: aaaaaaaa/gggggggg_gggggggg 3: aaaaaaaa/gggggggg_gggggggg Detecting Module: IEAVAD01
4: aaaaaaaa/gggggggg_gggggggg 5: aaaaaaaa/gggggggg_gggggggg
A: aaaaaaaa/gggggggg_gggggggg B: aaaaaaaa/gggggggg_gggggggg IEA998I PARTIAL SYSMDUMP TAKEN TO
C: aaaaaaaa/gggggggg_gggggggg D: aaaaaaaa/gggggggg_gggggggg dsname
E: aaaaaaaa/gggggggg_gggggggg F: aaaaaaaa/gggggggg_gggggggg
Explanation: The system could write only a partial
SYSMDUMP ABEND dump to the data set on a direct
Detecting Module: IEAVTSYM access storage device (DASD) and defined on the
SYSMDUMP DD statement. One of the following errors
occurred:
IEA996I READ FOR JFCB/JFCBE FAILED,
STANDARD DUMP FORMAT ASSUMED v An I/O error occurred while the system was writing
the dump to the dump data set.
Explanation: While trying to determine the requested
v The dump data set was filled before the system
format of a dump, the system tried to read the job file
finished writing all dump data.
control block (JFCB) or JFCB extension (JFCBE) for the
3800 printing subsystem. The system failed to read the
control block.
dsname
System Action: The system writes the dump in the
The data set specified on the SYSMDUMP DD
standard format of 120 characters per line. The system
statement.
The system sends messages about the problem to the
job log. System Programmer Response: Do the following:
Application Programmer Response: Rerun the job. If 1. Print the SYSMDUMP data set. Enough data might
the problem recurs, notify the system programmer. have been dumped to diagnose the problem that
caused the dump.
2. Increase the size of the DASD data set specified on
v Look at the messages in the job log. the SYSMDUMP DD statement.
v Collect all printed output and output data sets related
to the problem.
v Obtain the program listing for the job. Detecting Module: IEAVTABD

IEA999W ADDRESS TRANSLATION ERROR IN
Detecting Module: IEAVTABD, IEAVAD01 MASTER MEMORY
Explanation: The system encountered recursive
IEA997I READ FOR JFCB/JFCBE FAILED, addressing translation exceptions. Possibly the segment
DUMP CANCELLED table (SGTE) or page tables (PGTE) for the master
Explanation: While trying to determine the requested scheduler address space were initialized incorrectly or
format for a SNAP or ABEND dump, the system tried to overlaid.
read a job file control block (JFCB) or JFCB extension System Action: The system places all operating
(JFCBE) for the 3800 printing subsystem. The system systems on all processors in a wait state X'014'.
failed to read the control block.
System Action: The system cancels the dump. The wait state X'014'. ReIPL the system.
system returns a return code of X'08' to the program
that tried to read the JFCB or JFCBE. System Programmer Response: See the system
The system sends messages about the problem to the
job log. Source: Supervisor control
Application Programmer Response: Rerun the job. If Detecting Module: IEAVEPC

the problem recurs, notify the system programmer.

Chapter 16. IEB Messages
IEBA01I IEBIMAGE UTILITY COMPLETE. IEBA03I NO SPACE IN DIRECTORY.
RETURN CODE = return-code
Explanation: A STOW macro has been issued but all
Explanation: The utility has completed processing. directory blocks for the data set specified by the
The return code indicates the greatest severity of error SYSUT1 DD statement have been used.
found in any of the requested operations:
System Action: The IEBIMAGE program continues
00 Successful completion, operation(s) performed processing the next control statement, but subsequent
as requested. writing to the library data set is inhibited.
04 Operation(s) performed, investigate messages Application Programmer Response: Using utility
for exceptional circumstances. programs such as IEBCOPY and IEHPROGM the data
set may be recreated, allowing for more directory
08 Operation(s) not performed. Investigate
entries.
messages.
12 Severe exception. Utility may end.
16 Catastrophic exception. Utility ended. the job log for more information. Search problem
20 SYSPRINT data set could not be opened. exists, contact the IBM Support Center. Provide the
Utility ended. JCL, the SYSOUT output, and the source input for the
24 User parameter list incorrect. Utility ended. job.
Source: DFSMSdfp
return-code The return code. IEBA04I PERMANENT I/O ERROR IN
System Action: IEBIMAGE processing is ended. [DIRECTORY] devnum, devtyp, ddname,
op, errdes, lastskad, accmeth
return code to determine the degree of successful Explanation: During writing to the specified library an
processing. If the return code is ‘08’ or greater, the I/O error occurred.
preceding messages must be investigated and resolved In the message text:
and the job rerun.
devnum
System Programmer Response: If the error recurs The device number.
reporting data bases for a fix for the problem. If no fix devtyp The device type.
exists, contact the IBM Support Center. Provide the ddname
SYSOUT output, the source input for the job, and all The DDNAME specified.
problem. op The operation.
Source: DFSMSdfp errdes A description of the error.
lastskad
IEBA02I MEMBER (mem) {ADDED|REPLACED} The last seek address.
IN DIRECTORY
accmeth
Explanation: The specified member has been placed The access method.
into the library and a directory entry added or replaced
System Action: IEBIMAGE processing is ended.
in the PDS directory.
Application Programmer Response: Rerun the job.
mem The member name.
System Action: The IEBIMAGE program continues the job log for more information.
processing the next control statement.
Source: DFSMSdfp
Source: DFSMSdfp

IEBA05I FCB SPECIFICATION BEYOND RANGE
processing the next control statement, but writing to the
OF FORM.
library data set for the current operation is inhibited.
Explanation: The keywords supplied on the FCB
Application Programmer Response: Respecify
control statement have specified channel controls
COPYMOD statements to optimize storage usage. If
beyond the last byte of the FCB image.
more than 64 segments are needed for ‘GRAPHIC’, up
System Action: The IEBIMAGE program continues to four ‘GRAFMODS’ can be created and their names
processing the next control statement, but writing to the included into this appropriate character arrangement
library data set for the current operation is inhibited. table. For FCB, SIZE keyword determines maximum
number of lines. Respecify the control cards and rerun
the job.
FCB control statement and rerun the job.
SYSOUT output, the source input for the job, and all
problem.
problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEBA08I NO MEMBER NAME SPECIFIED.

IEBA06I PARAMETERS SPECIFIED IN (LOC)
KEYWORD RESULT IN X(FF), AN Explanation: No NAME control statement or no name
UNPRINTABLE CHARACTER. was specified on the NAME or INCLUDE statement.
Explanation: During processing of a TABLE operation, System Action: The IEBIMAGE program continues
the LOC keyword contained a parameter group in the processing the next control statement, but writing to the
following specification (23, 3F, 03). The “3F” index into library data set for the current operation is inhibited.
WCGM ‘03’ is specifically reserved to represent an
unprintable character. The message does not inhibit the
missing 1- to 4-character name and rerun the job.
construction of the character arrangement table, but this
character will not be printed. System Programmer Response: If the error recurs
Application Programmer Response: If an unprintable SYSOUT output, the source input for the job, and all
character is desired, specify only the character printed output and output data sets related to the
arrangement table location, that is (LOC=23). To specify problem.
a printable character the WCGM or the CGMID
Source: DFSMSdfp
reference must be changed and the job rerun.
IEBA09I DUPLICATE MEMBER NAME FOR
(mem), MEMBER NOT ADDED.
exists, contact the IBM Support Center. Provide the Explanation: A request was made to add a member to
SYSOUT output, the source input for the job, and all the specified library whose directory currently contains
printed output and output data sets related to the the name of a member equal to that of the name of the
problem. member to be added.
IEBA07I MODULE TOO LONG OR TOO SHORT
Explanation: An INCLUDE statement referenced a processing the next control statement, but writing to the
module that is too long or too short to be valid. If an library data set for the current operation is inhibited.
FCB module is being built, the length field is too large
for the virtual storage occupied by the module, or too Application Programmer Response: Change the
small to describe a valid FCB. Maximum size for name of the member to be added or if the member
COPYMOD is 8196 bytes, and for GRAPHIC is 64 currently on the library is no longer needed, specify the
segments. For FCB, the LPI keyword specifies lines replace option (R) on the NAME control statement.
beyond that specified by the SIZE keyword.

IEBA12I CONTINUATION INVALID.
reporting data bases for a fix for the problem. If no fix Explanation: A control statement was found that is not
exists, contact the IBM Support Center. Provide the in proper format for a continuation statement. Columns
SYSOUT output, the source input for the job, and all 1 through 15 must be blank and the continuation
printed output and output data sets related to the information must start in column 16.
problem.
Source: DFSMSdfp processing the next control statement, but writing to the
IEBA10I MEMBER (mem) NOT FOUND. Application Programmer Response: Change either
the control statement that indicates continuation (it is
Explanation: While processing the utility control
non-blank in column 72), or ensure that the subsequent
statements, the name specified could not be found on
control statement is specified properly.
the library directory. If this message precedes message
IEBA42I, control card specifications are erroneous; System Programmer Response: If the error recurs
otherwise it is an attention only message. and the program is not in error, search problem
mem The member name. SYSOUT output, the source input for the job, and all
System Action: The IEBIMAGE program continues problem.
library data set for the current operation is inhibited. Source: DFSMSdfp

name specified is correct and resubmit the job if IEBA13I PREVIOUS INCLUDE STATEMENT
necessary. INVALID FOR THIS OPERATION, IT IS
IGNORED.
and the program is not in error, search problem Explanation: If an INCLUDE control statement
reporting data bases for a fix for the problem. If no fix precedes a FCB control statement or a print-only
exists, contact the IBM Support Center. Provide the request, it is incorrect and is ignored. If multiple
SYSOUT output, the source input for the job, and all INCLUDE statements are present, only the last
printed output and output data sets related to the INCLUDE statement is used.
problem.
Source: DFSMSdfp processing the next control statement.
Application Programmer Response: Remove
IEBA11I FCB NOT MULTIPLE OF 1/2 INCH. unnecessary INCLUDE statements and rerun job, if
necessary.
Explanation: The form length as described by the LPI
keyword is not a multiple of one half inch. Any lines not System Programmer Response: If the error recurs
specified by the LPI keyword default to 6 LPI, up to the and the program is not in error, search problem
length of the form (as specified by the SIZE keyword). reporting data bases for a fix for the problem. If no fix
System Action: The IEBIMAGE program continues SYSOUT output, the source input for the job, and all
processing the next control statement, but writing to the printed output and output data sets related to the
library data set for the current operation is inhibited. problem.
Application Programmer Response: Correct the LPI Source: DFSMSdfp
keyword specifications and rerun the job.
System Programmer Response: If the error recurs IEBA14I PARAMETER(S) INVALID FOR
and the program is not in error, search problem KEYWORD (keywd).
exists, contact the IBM Support Center. Provide the Explanation: Parameters for the indicated keyword
SYSOUT output, the source input for the job, and all have been incorrectly specified. There are too many
printed output and output data sets related to the characters, or too many parameters, or incorrect
problem. parameter specification. It may also mean that the
number of lines described by the LPI keyword exceeds
Source: DFSMSdfp the length of the form as described by LINES or SIZE.
Chapter 16. IEB Messages 673

keywd The specified keyword. printed output and output data sets related to the
problem.
processing the next control statement, but writing to the Source: DFSMSdfp
Application Programmer Response: Correct the IEBA17I INVALID CONTROL CARD FORMAT.
parameter specifications and resubmit the job.
Explanation: Either the control statement has an
System Programmer Response: If the error recurs incorrect label, or it is a blank card image.
printed output and output data sets related to the Application Programmer Response: Correct the
problem. control statement and resubmit the job.
IEBA15I KEYWORD (keywd) INVALID FOR THIS
OPERATION.
Explanation: The indicated keyword is not valid for printed output and output data sets related to the
the current operation. problem.
keywd The specified keyword.
IEBA18I INVALID SEQUENCE FOR INITIAL
COPY NUMBER, IN SEGMENT segnum.
library data set for the current operation is inhibited. Explanation: In an existing module that was either
built or modified by other than the IEBIMAGE utility, the
indicated segment has an initial copy member that is
control statement and resubmit the job.
lower than the previous segment.
reporting data bases for a fix for the problem. If no fix segnum
exists, contact the IBM Support Center. Provide the The segment number.
problem.
Source: DFSMSdfp
Application Programmer Response: Using the
INCLUDE with the DELSEG keyword, delete the
IEBA16I OPERATION INVALID - op appropriate segments.
Explanation: The indicated operation is incorrectly System Programmer Response: If the error recurs
specified, is not in the proper sequence, or is missing a and the program is not in error, search problem
name statement. reporting data bases for a fix for the problem. If no fix
op The operation. printed output and output data sets related to the
problem.
processing the next control statement, but writing to the Source: DFSMSdfp
Application Programmer Response: Correct the IEBA19I DATA SET NOT FOUND, DSNAME =
indicated control statement and rerun the job. dsname
System Programmer Response: If the error recurs Explanation: The indicated data set could not be
and the program is not in error, search problem found during the issuance of an OPEN macro.

dsname JCL, the SYSOUT output, the source input for the job,
The specified dsname. and all printed output and output data sets related to
the problem.
Source: DFSMSdfp
DD statement is correctly specified. Rerun the job.
IEBA22I INVALID CHARACTER IN CARD
COLUMN number
reporting data bases for a fix for the problem. If no fix Explanation: An unexpected character was
exists, contact the IBM Support Center. Provide the encountered in the indicated column.
problem. number The indicated column number.
Source: DFSMSdfp System Action: The IEBIMAGE program continues
IEBA20I FAILURE DURING OPEN FOR DD =
ddname Application Programmer Response: Correct the
control statement and resubmit the job.
Explanation: The indicated DDNAME statement was
incorrectly specified or not included in the JCL for this System Programmer Response: If the error recurs
job step. If the DDNAME=SYSIN, the LRECL of the and the program is not in error, search problem
data set is probably not 80. reporting data bases for a fix for the problem. If no fix
Application Programmer Response: Correct the DD printed output and output data sets related to the
statement error and rerun the job. For SYSIN DD, also problem.
ensure that the data set is allocated with LRECL=80.
Source: DFSMSdfp
IEBA23I DUPLICATE OR MUTUALLY
EXCLUSIVE KEYWORD (keywd) FOR
OPERATION.
printed output and output data sets related to the Explanation: The indicated keyword has been
problem. specified more than once on this control statement, or
conflicts with other keywords or with the operation.
Source: DFSMSdfp
IEBA21I INSUFFICIENT SPACE IN DATA SET - keywd The specified keyword.
dsname
Explanation: The indicated data set is full. A D37 processing the next control statement, but writing to the
ABEND which has been suppressed by the utility has library data set for the current operation is inhibited.
occurred.
In the message text: control statement and rerun the job.
dsname System Programmer Response: If the error recurs
The specified dsname. and the program is not in error, search problem
processing the next control statement, but subsequent
writing to the library data set is inhibited.
Application Programmer Response: Using utility problem.
programs such as IEBCOPY and IEHPROGM, the data
Source: DFSMSdfp
set may be recreated, allowing for more space.

IEBA24I SEGMENT NUMBER (segnum)
NONEXISTENT. System Action: The IEBIMAGE program continues
Explanation: The indicated segment number is
greater than the number of segments in the module
referenced. Application Programmer Response: Correct the
control statement and rerun the job.
segnum
The indicated segment number.
System Action: The IEBIMAGE program continues exists, contact the IBM Support Center. Provide the
processing the next control statement, but writing to the SYSOUT output, the source input for the job, and all
library data set for the current operation is inhibited. printed output and output data sets related to the
problem.
segment number specification in the DELSEG or the Source: DFSMSdfp
REF keyword and rerun the job.
System Programmer Response: Run the IEBIMAGE IEBA27I NO OPERATION DEFINED.
utility to print the applicable member. If the error recurs
Explanation: A NAME control statement has been
encountered that does not immediately follow an
operation control statement (that is, FCB, COPYMOD,
CHARSET, TABLE, or GRAPHIC).
printed output and output data sets related to the System Action: The IEBIMAGE program continues
problem. processing the next control statement, but writing to the
Source: DFSMSdfp
control statement sequence and rerun the job.
IEBA25I INSUFFICIENT KEYWORD
INFORMATION TO COMPLETE System Programmer Response: If the error recurs
OPERATION. and the program is not in error, search problem
Explanation: Necessary keywords have not been
specified, preventing the requested operation from
completing successfully.
System Action: The IEBIMAGE program continues problem.
Source: DFSMSdfp
IEBA28I INVALID DATA SEQUENCE NUMBER.
necessary keywords and rerun the job.
Explanation: The sequence number on a data card
(column 29 and 30) for a GRAPHIC or CHARSET
operation is incorrect. The sequence number must be a
2-digit decimal number, between 1 and 24 (if the device
being used is an IBM 3800 Model 1) or between 1 and
40 (if the device being used is an IBM 3800 Model 3 or
Model 6).
problem.
Source: DFSMSdfp
IEBA26I INVALID USE OF DELIMITER IN
KEYWORD (keywd).
sequence number and rerun the job.
Explanation: A comma or a parenthesis has been
encountered on a control statement which does not
have the proper relationship to other delimiters within
the indicated keyword.
In the message text: SYSOUT output, the source input for the job, and all

IEBA31I NO VALID INPUT DATA FOR
problem.
{GRAPHIC|CHARSET} ASSIGN.
Source: DFSMSdfp
Explanation: The GRAPHIC or CHARSET operation
with an ASSIGN keyword is not followed by a data card
IEBA29I MEMBER NAME OR REPLACE OPTION which has the data ‘SEQ=’ in column 25 through 28.
INVALID.
Explanation: The name specified exceeds four processing the next control statement, but writing to the
characters or the replace option (R) was incorrectly library data set for the current operation is inhibited.
specified.
Application Programmer Response: Supply
System Action: The IEBIMAGE program continues appropriate data cards and rerun the job.
Application Programmer Response: Correct the reporting data bases for a fix for the problem. If no fix
error and rerun the job. exists, contact the IBM Support Center. Provide the
System Programmer Response: If the error recurs printed output and output data sets related to the
and the program is not in error, search problem problem.
IEBA32I SIZE OF FORM IS nn.n INCHES (xxxx.xx
problem.
MM).
Source: DFSMSdfp
Explanation: The FCB form size is printed as a
number in inches and in millimeters (MM). This size was
IEBA30I {GRAPHIC|CHARSET} DATA EXCEEDS specified or defaulted with the SIZE parameter.
RANGE OF PITCH IN SEGMENT
segnum
nn.n The size of the form in inches.
Explanation: Data specified on the GRAPHIC or
CHARSET data cards requires a character be built xxxx.xx The size of the form in millimeters.
which has bits outside the allowable limits of the pitch
specified in the ASSIGN keyword. In the formatted print
of that character the erroneous bit(s) will be printed as a
dollar sign ($). Application Programmer Response: None
segnum
System Action: The IEBIMAGE program continues SYSOUT output, the source input for the job, and all
processing the next control statement, but writing to the printed output and output data sets related to the
library data set for the current operation is inhibited. problem.
System Programmer Response: If the error recurs IEBA33I SEGMENT segnum COPY copynum LINE
and the program is not in error, search problem linenum MAY CREATE A LINE
reporting data bases for a fix for the problem. If no fix OVERRUN CONDITION IF PREVIOUS
exists, contact the IBM Support Center. Provide the LINE IS PRINTED AT {6|8|10|12} LINES
SYSOUT output, the source input for the job, and all PER INCH.
Explanation: The segment with segment number
problem.
segno, in combination with all the previous segments,
Source: DFSMSdfp may cause a line overrun condition to occur when this
copy modification module is used. If the message
specifies 12 lines per inch, the segment can be printed
at 6, 8, or (for 3800-3) 10 lines per inch. If the message
specifies 10 lines per inch, the segment can be printed
at 6 or 8 lines per inch. If the message specifies 8 lines

per inch, the segment can be printed only at 6 lines per printed output and output data sets related to the
inch. problem.
segnum
The indicated segment number. IEBA35I UNBALANCED PARENTHESIS IN
KEYWORD (keywd).
copynum
The number of the copy in which the line Explanation: The number of right parentheses does
overrun condition may occur. not equal the number of left parentheses in the
indicated keyword.
linenum
The line number in that copy. In the message text:
The corresponding segment in the formatted listing is
flagged with the designation “NOTE (n)”. If “n” is 0 (for System Action: The IEBIMAGE program continues
3800-3), 2, or 3, it indicates at least one overrun processing the next control statement, but writing to the
condition for 12, 8, or 6 lines per inch respectively. If “n” library data set for the current operation is inhibited.
is 1, it indicates at least one overrun condition for 12
lines per inch (for 3800-1), or 10 lines per inch (for
3800-3).
Application Programmer Response: Respecify exists, contact the IBM Support Center. Provide the
COPYMOD statements such that each segment in SYSOUT output, the source input for the job, and all
combination with preceding segments does not create a printed output and output data sets related to the
line overrun condition when the copy modification problem.
module is used. The OPTION statement with the
Source: DFSMSdfp
OVERRUN parameter can be used to suppress this
message.
IEBA36I DUPLICATE CHANNEL SPECIFICATION
FOR PRINT LINE prtlnnum
reporting data bases for a fix for the problem. If no fix Explanation: More than one channel specification has
exists, contact the IBM Support Center. Provide the been requested for the same print line (for example,
SYSOUT output, the source input for the job, and all CH1=10, CH2=10).
problem. In the message text:
Source: DFSMSdfp prtlnnum

The print line number specified.
IEBA34I CHARACTERS SPECIFIED IN TEXT System Action: The IEBIMAGE program continues
KEYWORD RESULT IN HEXADECIMAL processing the next control statement, but writing to the
(FF). library data set for the current operation is inhibited.
Explanation: A specification in the TEXT keyword Application Programmer Response: Correct the
which results in a hexadecimal (FF) is incorrect. ‘FF’ control statement and rerun the job.
has been reserved for use within copy modification text System Programmer Response: If the error recurs
to denote a duplication factor. and the program is not in error, search problem
System Action: The IEBIMAGE program continues reporting data bases for a fix for the problem. If no fix
processing the next control statement, but writing to the exists, contact the IBM Support Center. Provide the
library data set for the current operation is inhibited. SYSOUT output, the source input for the job, and all
Application Programmer Response: Correct the problem.
Source: DFSMSdfp

correct the error, or rebuild the module using an
IEBA37I REFERENCES TO NONEXISTENT
INCLUDE control statement with the DELSEG keyword,
CGMID WITHIN TABLE.
and a GRAPHIC or CHARSET control statement with
Explanation: One or more locations in the character the ASSIGN keyword and appropriate data cards.
arrangement table reference a CGMID that has not
been defined in the trailer portion of the table.
System Action: The IEBIMAGE program continues reporting data bases for a fix for the problem. If no fix
processing the next control statement, but writing to the exists, contact the IBM Support Center. Provide the
library data set for the current operation is inhibited. SYSOUT output, the source input for the job, and all
problem.
Source: DFSMSdfp
reporting data bases for a fix for the problem. If no fix IEBA40I INCONSISTENT PITCH WITHIN
exists, contact the IBM Support Center. Provide the SEGMENT segnum
Explanation: In a graphic character modification
module that was either created or modified by other
problem.
than the IEBIMAGE utility, the indicated segment was
Source: DFSMSdfp found to have inconsistent pitch.
IEBA38I TABLE REFERENCES NO PRINTABLE
segnum
CHARACTERS.
Explanation: A character arrangement table has been
constructed or modified such that the resulting table has
all 256 locations referencing the non-printable character
(FF).
Application Programmer Response: Use SPZAP to
correct the error, or rebuild the modules using an
INCLUDE control statement with the DELSEG keyword,
and a GRAPHIC or CHARSET control statement with
Application Programmer Response: Correct the the ASSIGN keyword and the appropriate data cards.
System Programmer Response: If the error recurs and the program is not in error, search problem
and the program is not in error, search problem reporting data bases for a fix for the problem. If no fix
reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the
exists, contact the IBM Support Center. Provide the SYSOUT output, the source input for the job, and all
SYSOUT output, the source input for the job, and all printed output and output data sets related to the
printed output and output data sets related to the problem.
problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEBA41I PREVIOUSLY USED {EBCDIC|WCGM}
IEBA39I INVALID PARITY IN SEGMENT segnum ASSIGNMENT IN SEGMENT segnum
Explanation: In a graphic character modification Explanation: A segment was found to have an
module that was either created or modified by other assignment value equal to that of one previously used
than the IEBIMAGE utility, the indicated segment was in the module. This error does not prohibit completion of
found to have incorrect parity. the operation. For GRAPHIC operations all segments
are built, but only the last one will take effect should it
be loaded into the printer. For CHARSET operations
segnum only the last of the duplicated assignments is built. All
The indicated segment number. previous library character set segments are ignored.
System Action: The IEBIMAGE program continues In the message text:

segnum
Application Programmer Response: Use SPZAP to

processing the next control statement. COPY—The number of the copy at which additional
printing is to begin, plus the number of copies, cannot
Application Programmer Response: For GRAPHIC
exceed 256.
operations the unwanted duplicate segments can be
deleted by using an INCLUDE control statement with
LINE—The number of the line at which additional
the DELSEG keyword. An assignment value can be
printing is to begin, plus the number of lines, cannot
changed by using the GRAPHIC control statement with
exceed 133. The IEBIMAGE utility allows the sum to be
the REF keyword to change the EBCDIC assignment
133, which is valid for a 3800 using International
value. For CHARSET operations the INCLUDE control
Standards Organization (ISO) paper sizes. If this value
statement with the DELSEG keyword can be used to
is greater than 120 for a 3800 that uses common-use
delete any unwanted segments. An assignment value
paper sizes, the entry is never used.
can be inserted by using the CHARSET control
statement with the REF or ASSIGN keywords.
TEXT—The number of the character at which additional
System Programmer Response: If the error recurs printing is to begin, plus the number of characters,
and the program is not in error, search problem cannot exceed 205.
printed output and output data sets related to the segnum
problem. The indicated segment number.

IEBA42I MEMBER NOT ADDED TO LIBRARY,
ERROR(S) LISTED. Application Programmer Response: Correct the
Explanation: Errors previous to this statement have
prevented the utility from updating the library with the System Programmer Response: If the error recurs
module specified in the current operation. and the program is not in error, search problem
Application Programmer Response: Correct the problem.
errors and rerun the job. Source: DFSMSdfp
and the program is not in error, search problem IEBA44I SEQUENCE NUMBER INVALID OR
reporting data bases for a fix for the problem. If no fix PREVIOUSLY USED.
SYSOUT output, the source input for the job, and all Explanation: A data card sequence number of less
printed output and output data sets related to the than 1, or one that has been used previously, has been
problem. encountered.

IEBA43I IN SEGMENT segnum,
{COPY|LINE|TEXT} SPECIFICATION Application Programmer Response: Correct the data
BEYOND RANGE OF MAXIMUM card and resubmit the job.
VALUE. System Programmer Response: If the error recurs
Explanation: One of the following values has been and the program is not in error, search problem
exceeded: reporting data bases for a fix for the problem. If no fix
COPY - 256
LINE - 133
TEXT - 205 printed output and output data sets related to the
problem.
The IEBIMAGE utility does not allow number of copies, Source: DFSMSdfp
number of lines, or number of text characters per line
specifications to exceed certain values.

IEBA45I LIBRARY SPACE INCREASED TO nn IEBA47I INSUFFICIENT VIRTUAL STORAGE TO
EXTENTS. PERFORM STOW FUNCTION.
Explanation: After updating the library specified by the Explanation: A STOW SVC was issued and its
SYSUT1 DD statement, it was found that the last record function was prohibited due to lack of virtual storage.
was written on a different extent than the previous
update. The SYS1.IMAGELIB system data set can have
processing the next control statement, but subsequent
up to 16 extents.
writing to the library data set is inhibited.
Application Programmer Response: Rerun the job.
nn The number of extents. The error may be a temporary one caused by
fragmentation of virtual storage.
processing the next control statement. System Programmer Response: If the error recurs
Application Programmer Response: Programs that
have the library open while IEBIMAGE is processing
may not be able to access new or updated members
unless they close and reopen it.
System Programmer Response: If the error recurs problem.
Source: DFSMSdfp
exists, contact the IBM Support Center. Provide the IEBA48I DUPLICATE TABLE REFERENCE FOR
SYSOUT output and all printed output and output data LOCATION (loc).
sets related to the problem.
Explanation: Specification for the same location in a
Source: DFSMSdfp character arrangement table occurred more than once.
Each reference must be unique.
IEBA46I REQUEST TO UPDATE LIBRARY In the message text:
DENIED, DSNAME = dsname.
loc The indicated location.
Explanation: The OPEN macro has caused a
message to be sent to the operator requesting an
update to a library whose expiration has not been
exceeded. The operator replied M, denying the request.
dsname
The data set name.
System Action: IEBIMAGE processing continues with reporting data bases for a fix for the problem. If no fix
the next control statement but updating of the library exists, contact the IBM Support Center. Provide the
data set is inhibited. SYSOUT output, the source input for the job, and all
Application Programmer Response: Specify a
problem.
different volume and/or obtain authorization to update
the subject data set. Source: DFSMSdfp
and the program is not in error, search problem IEBA49I NO CHANNEL 1 CODE HAS BEEN
reporting data bases for a fix for the problem. If no fix SPECIFIED.
Explanation: The FCB does not contain a channel 1
code. Be careful when using this FCB, because a skip
command will cause a unit check at the printer if the
problem.
FCB does not contain the required channel code.
Source: DFSMSdfp

IEBA52I VALUE OF LINES CONTRADICTS
VALUE OF SIZE
problem. Explanation: When building an FCB module for the
3800, 3262 model 5, or 4248 printer, the specifications
Source: DFSMSdfp
for the LPI, LINES, and SIZE parameters on the FCB
statement were conflicting.
IEBA50I CLOC PARAMETER NOT SPECIFIED
FOR REFERENCED GCM SEGMENT
segnum
Explanation: When building a library character set
using the REF keyword of the CHARSET operation, no
FCB statement with complementary values for the
character location (CLOC) assignment was specified for
LINES, SIZE, and LPI parameters. See the IEBIMAGE
the graphic character module (GCM).
chapter in OS/390 DFSMSdfp Utilities for the default
In the message text: value of each parameter.
segnum System Programmer Response: If the error recurs

The indicated segment number. and the program is not in error, search problem
Application Programmer Response: Specify a problem.
WCGM location in the second parameter of the REF Source: DFSMSdfp
keyword for the CHARSET operation. All library
character set segments require a WCGM location
assignment between ‘00-3F’. IEB001I {SYSUT1|SYSUT2|SYSIN} NOT
OPENED
and the program is not in error, search problem Explanation: The SYSUT1, SYSUT2, or SYSIN data
reporting data bases for a fix for the problem. If no fix set, as indicated in the message text, could not be
exists, contact the IBM Support Center. Provide the opened. Either the DD statement defining the data set
SYSOUT output, the source input for the job, and all was not included in the input stream, or a DCB
printed output and output data sets related to the parameter for the data set was incorrect.
problem.
System Action: The job step is ended. The return
Source: DFSMSdfp code is 8.
IEBA51I LIBRARY NOT UPDATED: MODULE error. Ensure that a DD statement for SYSUT1,
CONTAINS NO DATA SYSUT2, and SYSIN is included in the input stream,
and that the parameters on the DD statements are
Explanation: The module being created contains no correct (particularly that the block size specification is a
data. This may have been caused by a DELSEG multiple of 80). Resubmit the job.
parameter on an INCLUDE statement which deleted all
the segments of the module. System Programmer Response: If the error recurs
System Action: The IEBIMAGE program continues the job log for more information. Search problem
processing the next control statement, but writing to the reporting data bases for a fix for the problem. If no fix
library data set for the current operation is inhibited. exists, contact the IBM Support Center. Provide the JCL
Application Programmer Response: Correct the and all printed output and output data sets related to
control statement and rerun the job. the problem.

reporting data bases for a fix for the problem. If no fix IEB008I INVALID NAME FIELD
SYSOUT output, the source input for the job, and all Explanation: The name field is incorrect in the EDIT
printed output and output data sets related to the statement preceding this message. Possibly, the name
problem. field consists of more than 8 characters or contains an
incorrect character.
Source: DFSMSdfp

EDIT statement. The return code is 4.
IEB011I INVALID OPERAND
Explanation: The operand is incorrect in the EDIT
error. Correct the name field on the preceding
statement preceding this message. Possibly, a
statement. Resubmit the job to process either the entire
parameter is misspelled or incompatible parameters are
input stream or the unedited portion of the input stream.
specified.
reporting data bases for a fix for the problem. If no fix Application Programmer Response: Probable user
exists, contact the IBM Support Center. Provide the JCL error. Correct the operands on the preceding control
and all printed output and output data sets related to statement. Resubmit the job to process either the entire
the problem. input stream or the unedited portion of the input stream.
IEB009I INVALID STATEMENT SYNTAX
Explanation: The EDIT statement preceding this exists, contact the IBM Support Center. Provide the JCL
message is coded incorrectly. and all printed output and output data sets related to
the problem.
EDIT statement. The return code is 4. Source: DFSMSdfp

error. Correct the preceding statement. Resubmit the job IEB014I INVALID DELIMITER
to process either the entire input stream or the unedited
Explanation: A delimiter is incorrect in the EDIT
portion of the input stream.
statement preceding this message.
reporting data bases for a fix for the problem. If no fix Application Programmer Response: Correct the
exists, contact the IBM Support Center. Provide the JCL delimiters on the preceding control statement. Resubmit
and all printed output and output data sets related to the job to process either the entire input stream or the
the problem. unedited portion of the input stream.
IEB010I INVALID OPERATION CODE
Explanation: The preceding statement is not an EDIT exists, contact the IBM Support Center. Provide the JCL
utility control statement. Possibly, EDIT is misspelled. and all printed output and output data sets related to
the problem.
EDIT statement. The return code is 4. Source: DFSMSdfp

error. Correct the operation on the preceding control IEB020I INVALID CONTINUATION CARD
statement to EDIT. Resubmit the job to process either
Explanation: The continuation does not begin at
the entire input stream or the unedited portion of the
column 16 in the statement preceding this message.
input stream.
the job log for more information. Search problem Application Programmer Response: Probable user
reporting data bases for a fix for the problem. If no fix error. Begin the continuation statement in column 16 or,
exists, contact the IBM Support Center. Provide the JCL if no continuation is desired, correct the statement that
and all printed output and output data sets related to indicated a continuation. Resubmit the job to process
the problem. either the entire input stream or the unedited portion of
the input stream.
Source: DFSMSdfp

exists, contact the IBM Support Center. Provide the JCL error. Insert the missing step into the input stream or
and all printed output and output data sets related to correct the control information on the associated EDIT
the problem. statement. Resubmit the job to process either the entire
input stream or the unedited portion of the input stream.
Source: DFSMSdfp
IEB021I INVALID CHARACTER
Explanation: A character is incorrect in the EDIT reporting data bases for a fix for the problem. If no fix
statement preceding this message. exists, contact the IBM Support Center. Provide the JCL
and all printed output and output data sets related to
System Action: Processing continues with the next the problem.
Source: DFSMSdfp
error. Correct the error in the control statement.
Resubmit the job to process either the entire input IEB024I high WAS HIGHEST SEVERITY CODE
stream or the unedited portion of the input stream.
Explanation: The return code was the highest return
System Programmer Response: If the error recurs code generated during processing of the IEBEDIT
and the program is not in error, look at the messages in program.
exists, contact the IBM Support Center. Provide the JCL high The highest return code generated.
Application Programmer Response: For other than
the problem.
successful job completion (severity code= 0), resubmit
Source: DFSMSdfp the job to process either the entire input stream or the
unedited portion of the input stream.
IEB022I JOB NAME NOT FOUND BEFORE END System Programmer Response: If the error recurs
OF FILE and the program is not in error, look at the messages in
Explanation: Either no JOB statement was found in
the input data set, or the specified job could not be
found.
System Action: The job step is ended. The return the problem.
code is 4.
Source: DFSMSdfp
error. Insert the missing JOB statement into the input
IEB027I I/O ERROR dsname, jjj, sss, ddd, devtyp,
stream or correct the control information on the
ddname, op, err, xxxx, acc
associated EDIT statement. Resubmit the job.
Explanation: A permanent input/output error occurred
while processing on the device.
the job log for more information. Search problem In the message text, the error analysis information
reporting data bases for a fix for the problem. If no fix provided by the SYNADAF data management macro
exists, contact the IBM Support Center. Provide the JCL issued by the SYNAD routine was:
dsname
the problem.
Data set name.
Source: DFSMSdfp
jjj Job name.
sss
IEB023I sss STEP COULD NOT BE FOUND
Step name.
Explanation: The step could not be found in the input
ddd
data set. Possibly, the step name was misspelled.
Device number of the device.
devtyp
sss The indicated step. Device type.
System Action: Processing continues with the next ddname
EDIT statement. The return code is 4. Data definition name.

op Operation attempted. System Programmer Response: If the error recurs
err Error description.
xxxx reporting data bases for a fix for the problem. If no fix
Last seek address or block count. exists, contact the IBM Support Center. Provide the JCL
acc the problem.
Access method.
Source: DFSMSdfp
System Action: The program is ended. The return
code is 8.
IEB033I STATEMENT NOT PROCESSED EOF
Application Programmer Response: Correct the ON SYSUT1
error condition indicated in the message text according
to the error analysis information provided by the Explanation: An end-of-file condition was encountered
SYNADAF data management macro instruction. on the SYSUT1 data set. The preceding EDIT
Resubmit the job. statement was not processed.
System Programmer Response: If the error recurs System Action: The job step is ended. The return
and the program is not in error, look at the messages in code is 4.
error. Restructure the EDIT statements if the edited
output is not as desired and resubmit the job; otherwise,
disregard the unprocessed EDIT statements.
the problem.
Source: DFSMSdfp
IEB030I {SYSUT1|SYSIN} BLKSIZE INVALID reporting data bases for a fix for the problem. If no fix
Explanation: The block size of the SYSUT1 or SYSIN and all printed output and output data sets related to
data set, as indicated in the message text, is not a the problem.
multiple of 80 bytes.
Source: DFSMSdfp
code is 8.
IEB034I STEPNAME REQUIRED WITH TYPE=
Application Programmer Response: Probable user {INCLUDE|EXCLUDE}
error. Correct the block size of the indicated data set
and resubmit the job. Explanation: No step name was specified with a
TYPE=INCLUDE or TYPE=EXCLUDE operation, as
System Programmer Response: If the error recurs indicated in the message text.
the job log for more information. Search problem System Action: Processing continues with the next
reporting data bases for a fix for the problem. If no fix EDIT statement. The return code is 4.
error. Correct the condition indicated in the message
the problem.
text. Resubmit the job to process either the entire input
Source: DFSMSdfp stream or the unedited portion of the input stream.
IEB032I SYSUT2 BLKSIZE INVALID - SYSUT1 and the program is not in error, look at the messages in
ASSUMED the job log for more information. Search problem
Explanation: The block size of the SYSUT2 data set exists, contact the IBM Support Center. Provide the JCL
is not a multiple of 80 bytes. and all printed output and output data sets related to
System Action: The SYSUT1 block size attributes are the problem.
assumed for the SYSUT2 data set. Processing Source: DFSMSdfp
continues. The return code is 4.
error. If the block size for SYSUT1 is undesirable for
SYSUT2, correct the block size for SYSUT2 and
resubmit the job; otherwise, disregard this message.

v On a different channel.
IEB100I I/O ERROR READING MEMBER
memname System Programmer Response: If the error recurs
Explanation: An I/O error was encountered while
reading the specified member. Message IEB139I, which
gives detailed information regarding the location of the
error record, is always issued previous to this message.
In the message text: the problem.
memname Source: DFSMSdfp
The specified member name.
System Action: The next COPY control statement is IEB102I MEMBER member NOT {COPIED |
sought unless a data check occupies the key or data LOADED | UNLOADED} DUE TO I/O
portion. In this case, the error is ignored and data is ERROR
copied as it came into main storage. If the copy is
Explanation: An I/O error on the SYSUT3 work file
performed, the return code is 4; if not, the return code is
has made processing of the member impossible. If
8.
******** replaces the member name in the above
Application Programmer Response: Depending on message, the error was found reading from SYSUT3.
the type of error, rerun the COPY operation with the
data set in error allocated:
v At a different physical location on the volume. member
The name of the member.
v On a different device.
v On a different channel. The severity is 8.
If the error is on an input data set, it may be necessary System Action: Processing continues with the next
to re-create the data set. member to be copied.
System Programmer Response: If the error recurs Application Programmer Response: Retry the failing
and the program is not in error, look at the messages in operation, and either:
reporting data bases for a fix for the problem. If no fix v Remove the SYSUT3 DD statement and increase the
exists, contact the IBM Support Center. Provide the JCL work area size as previously indicated in previously
and all printed output and output data sets related to message IEB1051I.
the problem. v Use a different SYSUT3 data set. Place the SYSUT3
data set on a different physical location on the
Source: DFSMSdfp volume, on a different device, or on a different
channel.
IEB101I I/O ERROR WRITING MEMBER DATA System Programmer Response: Use the IEHLIST
AT TTR=ttr [-DURING READ BACK utility to investigate the output directory and determine
CHECK] which member(s) were not copied.
Explanation: An I/O error occurred while copying Source: Data Facility Product (DFP)
member data to the output data set. The TTR of the
record in error relative to the beginning of the data set
is given. The [ ] part of the message is only given if the IEB103I MEMBERS member THRU END OF
error occurred during a read back check. DATASET ARE NOT ACCESSIBLE DUE
TO I/O ERROR
Explanation: Due to an I/O error while updating the
ttr The logical disk address. output data set’s directory, members starting from the
System Action: If the error was encountered during named member, member, through the end of the data
read back check and involved a data check in key or set (in alphameric order) have become inaccessible.
data only, the error is ignored, and the return code is 4. In the message text:
Otherwise, the next COPY control statement is sought,
and the return code is 8. member
The name of the member.
Application Programmer Response: Depending on
the type of error, rerun the COPY operation with the
The severity is 12.
data set in error allocated:
v At a different physical location on the volume. System Action: The operation is ended and the next
control statement is sought.

Application Programmer Response: Retry the failing
IEB106I UNEQUAL PARENTHESIS
operation. Use a different output data set. Place the
data set on a different physical location on the volume, Explanation: The statement just listed has an
on a different device, or on a different channel. unbalanced number of parentheses.
System Programmer Response: Verify that the The severity is 8.
output data set directory is large enough. If the error
System Action: The operation is ended and the next
problem reporting data bases for a fix for the problem. If Application Programmer Response: Correct the
no fix exists, contact the IBM Support Center. Provide control statement.
the JCL and all printed output and output data sets
related to the problem. System Programmer Response: If the error recurs
Source: Data Facility Product (DFP) the job log for more information. Search problem
IEB104I INVALID COMMAND OR KEYWORD
Explanation: A command or keyword on the control the problem.
statement just listed is misspelled or is incorrect for the
Source: Data Facility Product (DFP)
IEBCOPY program.
The severity is 8.
IEB107I INVALID CONTINUATION
Explanation: The control statement just listed is
incorrect.
(1) Parameters may have ended with a comma (which
control statement.
implies continuation), but the continuation column (72)
System Programmer Response: If the error recurs was blank.
(2) An attempt may have been made to continue a
statement from within a rename/replace specification
within nested parentheses. This is incorrect.
and all printed output and output data sets related to The severity is 8.
the problem.
Source: Data Facility Product (DFP) control statement is sought.
IEB105I PARAMETER INVALID control statement.
Explanation: A parameter on the control statement System Programmer Response: If the error recurs
just listed is too long or contains an incorrect character. and the program is not in error, look at the messages in
The severity is 8.
System Action: The operation is ended and the next exists, contact the IBM Support Center. Provide the JCL
control statement is sought. and all printed output and output data sets related to
the problem.
control statement. Source: Data Facility Product (DFP)
and the program is not in error, look at the messages in IEB108I MEMBER WITHOUT SELECT OR
the job log for more information. Search problem EXCLUDE
Explanation: A control statement containing a
MEMBER= operand has been encountered. The
operand can not be associated with a previous SELECT
the problem.
or EXCLUDE statement. The control statements are out
Source: Data Facility Product (DFP) of order or a SELECT or EXCLUDE statement is
missing.
The severity is 8.

System Action: The operation is ended and the next the job log for more information. Search problem
control statement is sought. reporting data bases for a fix for the problem. If no fix
Application Programmer Response: Place each
MEMBER= following a SELECT or EXCLUDE statement
the problem.
or MEMBER= operand.
the job log for more information. Search problem IEB111I NULL PARAMETERS
Explanation: A control statement was completely
blank, or blanks followed the equal sign immediately
after a keyword.
the problem.
No blanks are allowed inside or between any operands
on the same input record.
The severity is 8.
IEB109I NO MIXING OF SELECT AND EXCLUDE
MODES IN SAME COPY STEP System Action: The operation is ended and the next
Explanation: A SELECT statement immediately
follows an EXCLUDE statement without an INDD= Application Programmer Response: Correct the
statement between, or vice versa. control statement.
The severity is 8. System Programmer Response: If the error recurs
Application Programmer Response: Divide the exists, contact the IBM Support Center. Provide the JCL
operation into two operations. Place all SELECT and all printed output and output data sets related to
statements in one and all EXCLUDE statements in the the problem.
other.
IEB112I CANNOT RENAME/REPLACE ON
EXCLUDE
exists, contact the IBM Support Center. Provide the JCL Explanation: The control statement just listed has a
and all printed output and output data sets related to parameter embedded within parentheses, requesting a
the problem. rename or replace of this member. This is not allowed
during an exclusive copy operation.
The severity is 8.
IEB110I INVALID REPLACE SPECIFIED System Action: The operation is ended and the next
Explanation: Parentheses are missing from an INDD=
operand list or a MEMBER= operand list, or unbalanced Application Programmer Response: Correct the
parentheses have been found. control statement.
Each member_name/newname/replace triplet or Source: Data Facility Product (DFP)
DD_name/replace pair must appear in parentheses.
When the first operand of a INDD= or a MEMBER= IEB113I OUTDD OR INDD NOT SPECIFIED
operand indicates a replace or rename then the entire
operand must be enclosed in two sets of parentheses. Explanation: The commands are incomplete. An
INDD= keyword must be associated with a COPY
The severity is 8. statement that has defined the output data set (with the
OUTDD= keyword). A SELECT or EXCLUDE statement
may have been read without an INDD= preceding it.
The severity is 8.
control statement. System Action: The operation is ended and the next

IEB116I MIXING CONTROL STATEMENTS
control statement.
FROM OLD AND NEW VERSION OF
System Programmer Response: If the error recurs IEBCOPY
Explanation: Both types of statements were contained
within the same copy step, or multiple operations were
attempted using IEBCOPY control statements from a
release prior to OS Release 20.
the problem. The severity is 8.
Source: Data Facility Product (DFP) System Action: IEBCOPY ends, leaving control
statements unprocessed.
IEB114I OUTDD/LIST NOT ON COPY CARD If a complete set of valid statements (i.e. all old format
or all new format) occurred together, then the operation
Explanation: The OUTDD= or LIST= keywords were
was performed. If the statements were intermixed, no
scanned, but they were not physically or logically
operation was performed after the point where the
associated with the COPY, COPYMOD, or ALTERMOD
change in format was detected.
statement.
Application Programmer Response: Convert the old
The severity is 8.
format control statements to new format.
Application Programmer Response: Correct the the job log for more information. Search problem
control statement. reporting data bases for a fix for the problem. If no fix
System Programmer Response: If the error recurs and all printed output and output data sets related to
and the program is not in error, look at the messages in the problem.
reporting data bases for a fix for the problem. If no fix Source: Data Facility Product (DFP)
IEB117I TABLES EXCEED ALLOCATED
the problem.
STORAGE -- INCREASE WORK=
Source: Data Facility Product (DFP) VALUE IN PARM FIELD
Explanation: The number of names from {INDD} and
IEB115I END OF FILE ON SYSIN {SELECT} or {EXCLUDE} statements have grown too
large. The virtual storage available for saving the names
Explanation: The end of the control statement file was has been exceeded.
reached when more control statements were needed to
complete the current operation. Previous error may also The severity is 8.
have caused IEBCOPY to expect more statements.
The severity is 0. control statement is sought.
System Action: IEBCOPY ends because no more Application Programmer Response: Do either of the
operations remain. following:
Application Programmer Response: Correct the v Make more virtual storage available to IEBCOPY.
preceding error or supply control statements. Make more virtual storage available to IEBCOPY.
See message IEB1055I.
System Programmer Response: If the error recurs v Split the operation into multiple operations to
and the program is not in error, look at the messages in decrease the maximum number of DDNAMEs and
the job log for more information. Search problem member names in any one operation.
and all printed output and output data sets related to and the program is not in error, look at the messages in
the problem. the job log for more information. search problem
Source: Data Facility Product (DFP) exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.

perform the current operation.
IEB118I CONTROL STATEMENT ERROR
Explanation: The statement just listed has an
incorrect command, keyword, or parameter. ddname
The DDNAME.
The severity is 8.
System Action: The operation is ended and the next The severity is 8.
Application Programmer Response: Check for control statement is sought.
multiple INDD= keywords on the same statement, or
statements that mix old and new format keywords. Application Programmer Response: Correct any
errors diagnosed by accompanying messages.
the job log for more information. search problem and the program is not in error, look at the messages in
and the program listing for the job. exists, contact the IBM Support Center.
Source: Data Facility Product (DFP) Source: Data Facility Product (DFP)
IEB119I STATEMENT SEQUENCE ERROR IEB121I OPEN ERROR ON DDNAME ddname
Explanation: The error is one of the following: Explanation: The data set could not be opened.
v The first COPY statement, in a contiguous series of In the message text:
COPY statements, is either incomplete or out of
ddname
sequence.
The DDNAME.
v The first COPYMOD statement, in a contiguous
series of COPYMOD statements, is either incomplete The severity is 8.
or out of sequence.
v IEBCOPY control statements from a release prior to
OS Release 20 are not in the correct sequence.
Application Programmer Response: Correct any
The severity is 8. incorrect DD statement parameters.
System Action: The operation is ended and the next System Programmer Response: Check for
control statement is sought. accompanying IEBCOPY and IEC, IGD, IGW, and IOS
prefix messages.
If old format statements were used then IEBCOPY
ends. Source: Data Facility Product (DFP)
control statements. IEB122I DSCB COULD NOT BE OBTAINED.
OBTAIN RC=return-code REASON
CODE=reason
the job log for more information. search problem Explanation: The data set associated with the DD
reporting data bases for a fix for the problem. If no fix statement named in accompanying message IEB120I
exists, contact the IBM Support Center. Provide the JCL was not on the volume (taken from the catalog or the
and the program listing for the job. DD statement), or the volume could not be mounted.
Source: Data Facility Product (DFP) In the message text:
return-code The OBTAIN macro return code.
IEB120I ddname VALIDATION ERROR
reason The OBTAIN macro reason code.
Explanation: The data set cannot be used. The next
message(s) explain the error encountered while opening The severity is 8.
or validating the data set.
The DD statement may be missing, or the identified control statement is sought.
data set may be missing, or the data set may have DCB
attributes which are not permitted, or the data set Application Programmer Response: Verify that the
attributes may conflict among the data sets required to named volume is the correct volume, and if it is, verify

that it does contain the data set. In a system with output data sets related to the problem.
System Managed Storage (SMS) active, it is possible
that SMS will assign a data set to a different volume
than the one coded on a DD statement.
IEB124I INVALID LRECL (nnnnn)
Refer to IGD and IEF prefix messages in the JCL
message data set to verify which volume contains a Explanation: The logical record length of the data set
SMS managed data set. identified by message IEB120I is not valid. It may be
zero, or exceed the maximum allowed by the data set
block size (DCBBLKSI).
the job log for more information. Search problem One of the following may have occurred:
reporting data bases for a fix for the problem. If no fix 1. The data set has never been opened for output,
exists, contact the IBM Support Center. Provide the JCL therefore the BLKSIZE and LRECL fields in the data
and all printed output and output data sets related to set label are uninitialized.
the problem. 2. A data set intended for output is being used for
input because of incorrect control statements.
Problem Determination: The IDCAMS utility may be
3. The data set is not a PDS, but a VSAM, or
used to display the volume on which a cataloged data
SYSOUT data set, etc.
set is supposed to reside. The IEHLIST utility may be
4. RECFM has been incorrectly coded in the JCL.
used to display the names of data sets which resident
on a specific volume.
nnnnn The record length tested.
IEB123I INVALID DSORG (X'hhhh') The severity is 8.

Explanation: The data set associated with the DD System Action: The operation is ended and the next
statement named in accompanying message IEB120I control statement is sought.
does not have partitioned or physical sequential
organization. Application Programmer Response: Verify the
IEBCOPY control statements. Verify that the job which
One of the following may have occurred: created the data set was successful. Verify the
1. The data set has never been opened for output, BLKSIZE and LRECL used when allocating the data
therefore the DSORG field in the data set label is set.
uninitialized.
2. A data set intended for output is being used for System Programmer Response: The IEHLIST utility
input because of incorrect control statements. may be used to display the logical record length in the
3. The data set is not a PDS, but a VSAM, or data set label. If the error recurs and the program is not
SYSOUT data set, etc. in error, look at the messages in the job log for more
4. DSORG has been incorrectly coded in the JCL. information. Search problem reporting data bases for a
In the message text: Support Center. Provide the JCL and all printed output
and output data sets related to the problem.
hhhh The data set organization code.
The severity is 8.
IEB125I INVALID BLOCK SIZE (nnnnn)
control statement is sought. Explanation: The block size of the data set identified
by message IEB120I is not valid. It may be zero, or it
may exceed the hardware track length (unless the data
set uses the hardware track overflow feature).
created the data set was successful. Verify the DSORG
used when allocating the data set. One of the following may have occurred:
1. The data set has never been opened for output,
therefore the BLKSIZE and LRECL fields in the data
set label are uninitialized.
2. A data set intended for output is being used for
The IEHLIST utility may be used to display the DSORG input because of incorrect control statements.
in the data set label. 3. The data set is not a PDS, but a VSAM, or
SYSOUT data set, etc.
4. DSORG or RECFM has been incorrectly coded in
the JCL.
Center. Provide the JCL and all printed output and

IEB127I RECFM INCOMPATIBLE -- INPUT
nnnnn The actual block size. RECFM=iiii OUTPUT RECFM=oooo
Explanation: The record format of the input data set is
The severity is 8. incompatible with that of the output data set.
System Action: The operation is ended and the next IEBCOPY can not copy from fixed-length record format
control statement is sought. to variable-length record format or the reverse.
Application Programmer Response: Verify the In the message text:
created the data set was successful. Verify the iiii The input record format.
BLKSIZE and LRECL used when allocating the data
oooo The output record format.
set.
System Programmer Response: The IEHLIST utility The severity is 8.
may be used to display the block size in the data set
label. If the error recurs and the program is not in error,
look at the messages in the job log for more
information. Search problem reporting data bases for a Application Programmer Response: Verify the
fix for the problem. If no fix exists, contact the IBM RECFM of each data set. If they are correct, then
Support Center. Provide the JCL and all printed output IEBCOPY can not be used to copy the data set.
System Programmer Response: The IEHLIST utility
Source: Data Facility Product (DFP) may be used to display the RECFM in the data set
IEB126I ddname REFERENCES AN
UNMOVABLE DATA SET
Explanation: The input data set is flagged as Support Center. Provide the JCL and all printed output
unmovable in its DSORG. An unmovable data set can and output data sets related to the problem.
not be compressed in place or copied because it may
contain location dependent data.
IEB128I CANNOT REBLOCK TRACK
ddname OVERFLOW DATA SET
The DDNAME.
Explanation: The input and/or output data set(s) have
track overflow records. Reblocking operations can not
The severity is 8.
be done.
The severity is 8.
created the data set was successful. Verify the DSORG Application Programmer Response: Perform one of
used when allocating the data set. the following actions:
If the data set does not contain location dependent (1) Copy the data set to a new data set without track
data, then supply a DSORG override on the DD overflow.
statement and retry the operation.
(2) Reallocate the output data set so that it has a block
System Programmer Response: The IEHLIST utility size that is consistent with the input data set block size
may be used to display the DSORG in the data set (so that reblocking will not be done).
Support Center. Provide the JCL and all printed output
Source: Data Facility Product (DFP) the problem.

The severity is 8.
IEB129I CANNOT REBLOCK KEYED DATA
SETS System Action: The operation is ended and the next
Explanation: The input and/or the output data set(s)
have keyed records. Reblocking operations can not be Application Programmer Response: Make a full
done. copy to a new data set. Substitute this
The severity is 8. System Programmer Response: If the error recurs
Application Programmer Response: Reallocate the exists, contact the IBM Support Center. Provide the JCL
output data set so that it has a block size that is and all printed output and output data sets related to
consistent with the input data set block size (so that the problem.
reblocking will not be done).
IEB132I INVALID RE/DE-BLOCKING. INPUT
BLKSIZE IS inblksz, OUTPUT BLKSIZE
IS outblksz.
and all printed output and output data sets related to Explanation: The input data set block size is
the problem. incompatible with the output data set block size.
Source: Data Facility Product (DFP) For fixed length records, the size of each block must be
a multiple of the logical record length.
IEB130I KEY LENGTHS UNEQUAL. INPUT KEY For variable length records the output block size must
LENGTH IS inlen, OUTPUT KEY be equal to or greater than the input logical record
LENGTH IS outlen. length.
Explanation: The key length of the input data set and For undefined length records the output block size must
key length of the output data set are not equal. be equal to or greater than the input block size.
inlen The input key length. inblksz The input block size.
outlen The output key length. outblksz
The output block size.
The severity is 8.
The severity is 8.
control statement is sought. System Action: For RECFM=U data sets, the copy
operation continues. For all other RECFM, the copy
Application Programmer Response: Reallocate the
operation ends.
output data set so that it has the same key length as
the input data set key length. Application Programmer Response: Respecify the
output block size to allow this member to be properly
copied. Copying a larger block size to a small block size
may be used to display the key length in the data set
can create ″fat″ blocks, which cause I/O errors when
other programs try to read them. Use COPYMOD
instead of COPY to reblock load modules.
fix for the problem. If no fix exists, contact the IBM System Programmer Response: If the error recurs
Support Center. Provide the JCL and all printed output and the program is not in error, look at the messages in
and output data sets related to the problem. the job log for more information. Search problem
IEB131I CANNOT COMPRESS KEYED DATA the problem.
SET
Explanation: A compress-in-place operation was
requested, but the data set contains keyed records.
IEBCOPY does not compress keyed data sets in place.

IEB133I MINIMUM REQUESTED STORAGE
(amount) NOT AVAILABLE
Application Programmer Response: Perform one of
Explanation: IEBCOPY could not obtain a work area
the following actions:
of even minimum size.
v Make more virtual storage available to IEBCOPY.
In the message text: Make more virtual storage available to IEBCOPY.
amount The number of bytes of virtual storage that See message IEB1055I.
must be available to IEBCOPY for use as a v Divide the operation into several operations with each
work area. operation using fewer members.
The severity is 16.
System Action: IEBCOPY ends processing. the job log for more information. Search problem
Application Programmer Response: Make more exists, contact the IBM Support Center. Provide the JCL
virtual storage available to IEBCOPY. Make more virtual and the program listing for the job.
storage available to IEBCOPY. See message IEB1055I.
the job log for more information. Search problem IEB136I CANNOT ALLOCATE TWO TRACKS OF
reporting data bases for a fix for the problem. If no fix I/O BUFFERS FOR COMPRESS
Explanation: There is not enough unallocated virtual
storage available to contain 2 buffers, each the (device
Source: Data Facility Product (DFP) dependent) track size. COMPRESS operations must
have this much I/O buffer space for full track I/O and
synchronization.
IEB134I CANNOT COMPRESS WITH SELECT
OR EXCLUDE The severity is 8.
Explanation: The input and output data set are the System Action: The operation is ended and the next
same data set, which implies a compress-in-place. A control statement is sought.
SELECT or EXCLUDE statement is also present, which
is not allowed for a compress-in-place operation.
The severity is 8. v Make more virtual storage available to IEBCOPY.
System Action: The operation is ended and the next Make more virtual storage available to IEBCOPY.
control statement is sought. See message IEB1055I.
v Make a full copy to a new data set. Substitute this
Application Programmer Response: Make a full
copy to a new data set. Substitute this System Programmer Response: If the error recurs
reporting data bases for a fix for the problem. If no fix and the program listing for the job.
and all printed output and output data sets related to Source: Data Facility Product (DFP)
the problem.
Source: Data Facility Product (DFP) IEB137I CANNOT SPECIFY DUPLICATE
MEMBER NAMES FOR
SELECT/EXCLUDE/RENAME -
IEB135I MINIMUM I/O BUFFER NOT DUPLICATE IS member
ALLOCATABLE
Explanation: The member name appears more than
Explanation: IEBCOPY obtained the largest size work once in the SELECT or EXCLUDE statements for this
area available from virtual storage. It was not large operation. It may be both an old name and a new
enough to contain two minimum size I/O buffers and the name.
tables built from INDD=, SELECT, and/or EXCLUDE
statements. All names on SELECT or EXCLUDE statements in one
operation must be unique, even if the name is used
The severity is 8. once as a old name and once as a new name.

In the message text: READING PDS
member
The specified member name. WRITING PDS
The severity is 4.
READING UNLOADED PDS
System Action: The operation is not performed for the
named members. Processing continues for the
WRITING UNLOADED PDS
uniquely-named members.
Application Programmer Response: If duplicate
GET FROM CONTROL STMT FILE
names must be specified, create additional operations.
System Programmer Response: Check for duplicate
PUT TO MESSAGE FILE
renamed old names, duplicate old names that were not
renamed, duplicate new names, or a combination of
these. DURING ERASE
If the error recurs and the program is not in error, look
at the messages in the job log for more information. DURING READBACK CHECK
DURING READ
Center. Provide the JCL and the program listing for the
job.
DURING WRITE
DURING LOAD
IEB138I CANNOT PROCESS ALL
OLD/NEW-NAMES SPECIFIED
DURING UNLOAD
Explanation: The virtual storage required to hold pairs
of old and new names (of members being renamed) is
not available. synad_text
The text issued by the SYNAD macro.
The severity is 8.
the type of error, retry the operation with the data set in
error allocated:
v Make more virtual storage available to IEBCOPY.
v At a different physical location on the volume.
Make more virtual storage available to IEBCOPY.
See message IEB1055I. v On a different device.
v Divide the operation into several operations with each v On a different channel.
operation using fewer members.
If the error is on an input data set, it may be necessary
System Programmer Response: If the error recurs to re-create the data set.
If the operation is compress-in-place and the error is
NO RECORD FOUND, restore the backup and copy the
data set to a different physical location.
IEB139I I/O ERROR activity synad_text reporting data bases for a fix for the problem. If no fix
Explanation: An I/O error has occurred, the and all printed output and output data sets related to
SYNADAF macro was issued, and SYNAD text was the problem.
generated by the SYNADAF macro.
activity The activity taken, as follows:

IEB140I ddname REFERENCES A NULL INPUT IEB142I CANNOT CONTINUE TO BUILD
DATA SET CTLTAB
Explanation: The data set contains no members. Explanation: More virtual storage is required to build
the required control table to process the current
operation.
ddname
The severity is 8.
The DDNAME.
The severity is 0. control statement is sought.
System Action: The next input data set or control Application Programmer Response: Perform one of
statement is sought. the following actions:
Application Programmer Response: Check the v Make more virtual storage available to IEBCOPY.
operation which created the input data set. Make more virtual storage available to IEBCOPY.
See message IEB1055I.
System Programmer Response: If the error recurs v If the operation is not already a selective copy, then
and the program is not in error, look at the messages in obtain a list of all members in the data set using the
the job log for more information. Search problem IEHLIST utility. Divide the operation into multiple
reporting data bases for a fix for the problem. If no fix selective copy operations. Each one should copy
exists, contact the IBM Support Center. Provide the JCL approximately the same number of members.
the problem. v If the operation is already a selective copy, then
divide the operation into several operations each
Source: Data Facility Product (DFP) specifying fewer members.
IEB141I CAN NOT RE/DE-BLOCK WITH and the program is not in error, look at the messages in
NOTE-LIST/USER TTRN IN MEMBER the job log for more information. Search problem
member reporting data bases for a fix for the problem. If no fix
Explanation: The directory entry for the member
indicates the presence of a Notelist and/or User TTRNs.
IEBCOPY is reblocking or deblock members as they are Source: Data Facility Product (DFP)
copied because the input and output data set attributes
are different.
IEB143I ALL SELECTED MEMBERS {COPIED |
The reblocking will make the Notelist data incorrect so it LOADED | UNLOADED}- DID NOT USE
is not allowed. If this member is to be copied, it cannot ALL SPECIFIED INDD’S
be reblocked.
Explanation: All specified (selected) members have
In the message text: been successfully copied, and there are still data sets in
the INDD list which have not yet been examined. It was
member
not necessary to use all specified input data sets in
The specified member.
order to locate all the selected members.
The severity is 8. The severity is 0.
System Action: The operation is ended and the next System Action: The next control statement is sought.
Application Programmer Response: See messages
Application Programmer Response: Respecify the IEB154I, IEB155I, and IEB167I. Verify that each
factors which cause reblocking (the BLKSIZE, RECFM, member copied came from the expected data set.
LRECL of the two data sets), so that reblocking will not
take place. Retry the operation.
reporting data bases for a fix for the problem. If no fix and all printed output and output data sets related to
exists, contact the IBM Support Center. Provide the JCL the problem.
the problem.

done during a compress-in-place operation.
IEB144I THERE ARE nnnnn UNUSED TRACKS
IN OUTPUT DATASET REFERENCED The severity is 8.
BY ddname
Explanation: This message is issued after completing control statement is sought.
the operation to the output partitioned data set.
If an error has occurred, the number of tracks given in the following actions:
this message may be incorrect. v Avoid reblocking by specify the same DD statement
In the message text: for both INDD= and OUTDD=.
v Make a full copy to a new data set. Substitute this
nnnnnn The number of tracks available in the data set.
System Programmer Response: Check that the
ddname
same DCB parameters are specified on each DD
The DDNAME.
statement. If the error recurs and the program is not in
The severity is 0.
System Action: The next control statement is sought. fix for the problem. If no fix exists, contact the IBM
Application Programmer Response: If not enough and output data sets related to the problem.
space remains available, adding a compress-in-place
operation may make additional space available. Source: Data Facility Product (DFP)
IEB147I END OF JOB - return-code WAS
HIGHEST SEVERITY CODE
IEB145I CANNOT COMPRESS TRACK
OVERFLOW DATA SET Explanation: This message is issued after all
operations have been finished.
Explanation: IEBCOPY does not allow a
compress-in-place operation to be done if the track In the message text:
overflow bit has been set in the format 1 DSCB of the
return-code The highest return code from any
output data set. (This bit is the DCBRECTO bit in the
operation.
DS1RECFM field.)
System Action: The operation is ended and the next System Action: IEBCOPY ends. When the severity
control statement is sought. code is other than 0, message IEB151I will also be
issued.
Application Programmer Response: Make a full
copy to a new data set. Substitute this Application Programmer Response: Verify that all
operations completed as expected.
Consider not using the track overflow feature.
System Programmer Response: Consult message
IEB151I if issued.
may be used to examine the RECFM in the data set
label for track overflow. Look for an override on the DD Source: Data Facility Product (DFP)
statement. If the error recurs and the program is not in
IEB148I NO SPACE IN OUTPUT DIRECTORY
FOR DIRECTORY ENTRIES FROM
INPUT DATA SET ddname
and output data sets related to the problem. Explanation: While building an updated output
directory (to reflect members copied from the input data
set) IEBCOPY has determined that the amount of
directory space allocated to the output data set is
IEB146I CANNOT COMPRESS WITH insufficient.
RE/DE-BLOCKING
Explanation: The compress-in-place operation can not
ddname
alter the block size or record length of a data set. The
The DDNAME.
data set to be compressed is identified by two different
DD statements, and the input data set attributes are
different from the output data set attributes. The The severity is 8.
different attributes imply reblocking, which can not be System Action: If message IEB168I does not

immediately follow this message, the output data set In the message text:
directory reflects those members copied through the
ddname
immediately preceding input data sets. If this data set is
The DDNAME.
the first input data set in the operation, the output data
set is unchanged.
The severity is 4.
If the message IEB168I does follow, the output directory
is truncated. System Action: IEBCOPY attempts to write the output
directory in a structure identical to that of the input data
The operation is ended and the next control statement set directory. This concludes the current operation and
is sought. the next control statement is sought.
Application Programmer Response: Allocate a new Application Programmer Response: The data may
output data set large enough to contain all the members be recovered with this procedure: Allocate a new data
in the old output data set plus the members from the set. Perform a selective copy to move approximately
input data set(s). Retry the operation to the new output half of the members from the broken data set to the
data set. new data set. Repeat a separate selective copy
operation to move the remaining members.
may be used to display the members present in the System Programmer Response: Dump the directory
output data set. If the error recurs and the program is with SPZAP and determine its structure. Examine the
not in error, look at the messages in the job log for program that created the input data set for defects.
more information. Search problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM Source: Data Facility Product (DFP)
and output data sets related to the problem. IEB151I JOB HAS TERMINATED WITH
Source: Data Facility Product (DFP) ERROR(S)
Explanation: IEBCOPY issued a message of severity
IEB149I THERE ARE nnnnn UNUSED 4 or greater. One or more operations were not
DIRECTORY BLOCKS IN OUTPUT completed successfully.
DIRECTORY The severity is 0.
Explanation: This message is issued after completing System Action: IEBCOPY is finished operating and
the operation to the output partitioned data set identified will end.
in message IEB144I.
If an error has occurred, the number of blocks given in errors indicated by preceding error messages, and retry
this message may be incorrect. the operations not successfully completed.
In the message text: System Programmer Response: Look up the severity
nnnnn The number of whole 256 byte directory blocks code of each issued message. Many IEBCOPY suffix I
available for additional member name. messages have a severity code greater than zero. If the
error recurs and the program is not in error, look at the
The severity is 0.
System Action: The next control statement is sought. no fix exists, contact the IBM Support Center. Provide
the JCL and all printed output and output data sets
Application Programmer Response: If not enough
space remains available, a new data set with a larger
directory must be allocated and the smaller data set Source: Data Facility Product (DFP)
copied to it.
Source: Data Facility Product (DFP) IEB152I member COMPRESSED - WAS
ALREADY IN PLACE AND NOT MOVED
IEB150I **WARNING** THE OUTPUT DATASET Explanation: The member did not need to be
REF BY ddname CONTAINS TOO MANY physically moved during the compress-in-place
DIRECTORY BLOCKS PER TRACK operation.
Explanation: Because of short or damaged directory In the message text:
blocks, more blocks were encountered than were
member
expected. Errors will probably result if the is accessed
The specified member name.
by other programs. The BLDL and STOW functions are
particularly vulnerable.
The severity is 0.

IEB156I NOT A DIRECT ACCESS DATA SET
Explanation: The data set referred to by the DDNAME
in preceding message IEB120I is not on a direct access
IEB153I ALL MEMBERS COMPRESSED - ALL device. The data set is identified as a PDS or PDSE
WERE ORIGINALLY COMPRESSED which must always reside on a direct access device.
Explanation: The data set was not in need of being The severity is 8.
compressed because all member data is contiguous at
the front of the data set. No members from this data set
were physically moved.
Application Programmer Response: Check that the
The severity is 0.
data set is on a direct access volume.
Source: Data Facility Product (DFP) and the program is not in error, look at the messages in
IEB154I member HAS BEEN SUCCESSFULLY exists, contact the IBM Support Center. Provide the JCL
{COPIED | LOADED | UNLOADED | and all printed output and output data sets related to
{COPIED | LOADED | UNLOADED | the problem.
ALTERED}
Explanation: The member has been successfully
copied, loaded, or unloaded from the input data set to
the output data set, or altered in the output data set. IEB157I ddname DD STATEMENT NOT FOUND
In a compress-in-place operation, this message may be Explanation: The DDNAME DD statement was not
issued for members not actually moved (as identified in supplied either in the JCL or by dynamic allocation
message IEB152I). before IEBCOPY was invoked.
member ddname
The specified member name. The DDNAME.

System Action: Normal processing continues. System Action: The operation is ended and the next
spelling of ddname in the control statement. If it is
IEB155I member HAS BEEN SUCCESSFULLY spelled correctly then include the missing DD statement,
{COPIED | LOADED | UNLOADED | or allocate a DDNAME file before invoking IEBCOPY.
{COPIED | LOADED | UNLOADED |
ALTERED}AND IS A NEW NAME System Programmer Response: If the error recurs
Explanation: The member, which is a new name, has the job log for more information. Search problem
been successfully copied, loaded, or unloaded from the reporting data bases for a fix for the problem. If no fix
input data set to the output data set, or altered in the exists, contact the IBM Support Center. Provide the JCL
output data set. and all printed output and output data sets related to
The old name of this member can be determined by the problem.
checking the IEBCOPY control statement(s) listed at the Source: Data Facility Product (DFP)
beginning of the operation which issued this message.
In the message text: IEB158I PARM=COMPRESS NOT VALID
member Explanation: PARM=COMPRESS was specified on
The specified member name. the JCL EXEC statement, and new format control
statements are being used. New format statements do
The severity is 0. not use PARM=COMPRESS to request a compress.
System Action: Normal processing continues. System Action: Processing continues.
Source: Data Facility Product (DFP) Compress-in-place will be done only if it is requested in
a subsequent COPY statement.

IEB160I CONCATENATED DATA SETS
is informational only. It indicates that the
PARM=COMPRESS parameter from the EXEC Explanation: The DDNAME identified in message
statement is ignored. Remove this parameter from the IEB120I is a concatenation of data sets. IEBCOPY does
JCL to avoid further occurrences of this message. not process concatenated data sets.
If IEBCOPY is dynamically invoked then The severity is 8.
PARM=COMPRESS is in the parameters passed to
IEBCOPY by the caller.
Application Programmer Response: If more than
one input data set is to be used in the copy step,
IEB159I NO MEMBERS {COPIED | LOADED} provide a separate DD statement for each, and include
FROM INPUT DATA SET REFERENCED all the DDNAMEs in an INDD= utility control statement
BY DDNAME parameter.
Explanation: The input data set was not used for one System Programmer Response: If the error recurs
of the following reasons: and the program is not in error, look at the messages in
v A selective copy was specified, but none of the the job log for more information. Search problem
members to be copied were on this data set. reporting data bases for a fix for the problem. If no fix
v All of the members which should have been copied
from this input data set had names which were
the problem.
duplicates of member names on the output data set
and replace was not specified. Source: Data Facility Product (DFP)
v An I/O error (indicated by a previous message) has
precluded use of members from this input data set. IEB161I COMPRESS TO BE DONE USING INDD
v Either the input or the output data set contains NAMED ddname
duplicate or out-of-sequence members (indicated by
Explanation: A request for a compress-in-place
a previous message).
operation has been detected. This occurs when the
input and output DD statement(s) identify the same data
set and volume.
ddname
Before attempting a compress-in-place operation a
The DDNAME.
backup to the data set should be made so that it can be
recovered should the compress-in-place fail.
The severity is 0.
System Action: The next input data set will be
processed unless an error has occurred. ddname
The DDNAME.
If an I/O error has occurred, or if there are duplicate or
out-of-sequence members, actions taken are indicated
The severity is 0.
by previous message(s).
System Action: A compress-in-place operation is
Application Programmer Response: If an error
started.
occurred, correct it as indicated in the above
explanation. System Programmer Response: If compress-in-place
was not intended, check that both DD statements do not
If no error occurred, verify that the processed members
specify identical data set name and volume serials.
were found in the data sets expected to contain them.
System Programmer Response: Examine messages
message data set to verify which volume contains a
IEB154I, IEB155I, and IEB167I to verify that each
SMS managed data set.
member came from the expected data set. If the error
recurs and the program is not in error, look at the Source: Data Facility Product (DFP)
IEB162I PARM=COMPRESS IGNORED
the JCL and all printed output and output data sets Explanation: PARM=COMPRESS is specified, but the
related to the problem. input and output data sets are not the same data set, or
an unload or load operation has been requested.
System Action: PARM=COMPRESS is ignored.

IEB165I member ‘FOUND’ BUT NOT {COPIED |
is informational only. Remove the PARM=COMPRESS
LOADED | UNLOADED}DUE TO I/O
parameter from the JCL to avoid further occurrences of
ERROR READING INPUT DIRECTORY
this message. If a COMPRESS is desired, correct the
DD statements or the INDD= and OUTDD= control Explanation: The member indicated was found in the
statement parameters. current input data set directory before the I/O error
occurred. The member was not processed because
processing in the data set had not reached the data for
the member.
member
the problem.
Source: Data Facility Product (DFP) The severity is 12.
System Action: The member is not processed.
IEB163I NO MEMBER NAMES FOR PARTIAL
COPY, WILL NOT COPY Application Programmer Response: Retry the
operation. If the operation fails a second time, suspect
Explanation: The version of IEBCOPY statement from that a hardware error has occurred. The data set may
a release prior to OS Release 20 specified have to be restored. Contact your systems programmer
TYPCOPY=I, but it was not followed by any MEMBER= or hardware support personnel.
statements.
The severity is 8.
System Action: The job step is ended. IEB166I NO MEMBERS {COPIED | LOADED |
UNLOADED} TO DATA SET
Application Programmer Response: Correct and
REFERENCED BY ddname
convert the control statement to new format.
Explanation: Due to the validation error described in a
previous message, the operation did not take place. The
data set was not changed.
and the program listing for the job. ddname
The DDNAME.
The severity is 8.
IEB164I TOTAL COPY ASSUMED System Action: The next control statement is sought.
Explanation: The version of IEBCOPY statement from Application Programmer Response: Refer previously
a release prior to OS Release 20 specified issued messages for the reason.
TYPCOPY=E, but it was not followed by any MEMBER=
statements. Source: Data Facility Product (DFP)
The severity is 4.
IEB167I FOLLOWING MEMBER(S) {COPIED |
System Action: A full copy is done. LOADED} FROM INPUT DATASET
Application Programmer Response: Correct and REFERENCED BY DDNAME
convert the control statement to new format. Explanation: Following messages identify the
System Programmer Response: If the error recurs members input from the data set.
and the program is not in error, look at the messages in This message assists in tracing the data sets which
the job log for more information. Search problem were used, and which members they contributed.
exists, contact the IBM Support Center. Provide the JCL In the message text:
and the program listing for the job. ddname
Source: Data Facility Product (DFP) The DDNAME.
The severity is 0.

System Action: Messages IEB154I and IEB155I System Programmer Response: Use the IEHLIST
follow. utility to investigate the output directory and determine
which member(s) were lost. If the error recurs and the
program is not in error, look at the messages in the job
log for more information. Search problem reporting data
IEB168I **WARNING** DUE TO ERROR, bases for a fix for the problem. If no fix exists, contact
POSSIBLE LOSS OF ACCESS TO the IBM Support Center. Provide the JCL and all printed
MEMBER DATA AND/OR INCOMPLETE output and output data sets related to the problem.
DIRECTORY
Explanation: If preceded by message IEB148I, the
output directory has been truncated. Otherwise, the
IEB170I **WARNING** DUE TO SYSUT3 I/O
output directory may be incomplete.
ERROR, COMPRESS IN-PLACE NOT
The severity is 12. DONE AND COPY OPERATION
TERMINATED
control statement is sought. Explanation: An I/O error has occurred while using
the spill data set. None of the members were physically
Application Programmer Response: Depending on moved, so the data set remains as it was prior to
the type of error, retry the operation with the data set in processing.
error allocated:
v At a different physical location on the volume. The severity is 8.
v On a different channel.
If the error is on an input data set, it may be necessary Application Programmer Response: Retry the failing
to re-create the data set. operation, and either:
System Programmer Response: Dump the directory v Remove the SYSUT3 DD statement and increase the
with IEHLIST or SPZAP to determine the final status of work area size. See message IEB1051I previously
the output directory. If the error recurs and the program issued.
is not in error, look at the messages in the job log for v Use a different SYSUT3 data set. Place the SYSUT3
more information. Search problem reporting data bases data set on a different physical location on the
for a fix for the problem. If no fix exists, contact the IBM volume, on a different device, or on a different
Support Center. Provide the JCL and all printed output channel.
System Programmer Response: Use the IEHLIST
Source: Data Facility Product (DFP) utility to investigate the output directory and determine
which member(s) were not copied. If the error recurs
IEB169I **WARNING** DUE TO I/O ERROR ON the job log for more information. Search problem
SYSUT4, OUTPUT DIRECTORY MAY reporting data bases for a fix for the problem. If no fix
NOT BE COMPLETE exists, contact the IBM Support Center. Provide the JCL
Explanation: The SYSUT4 spill file holds the directory and all printed output and output data sets related to
for the output data set until the operation is complete. the problem.
Because an I/O error occurred on the SYSUT4 spill file, Source: Data Facility Product (DFP)
a portion of the output directory was lost before it could
be written to the output data set.
IEB171I **WARNING** DIRECTORY MIGHT NOT
The severity is 0. REFLECT VALID LOCATION OF
System Action: The operation is ended and the next MEMBER DATA
control statement is sought. Explanation: An I/O error during a compress-in-place
Application Programmer Response: Retry the failing operation may have affected the validity of the data set
operation, and either: directory.
v Remove the SYSUT4 DD statement and increase the The severity is 8.
work area size. See message IEB1052I previously
issued. System Action: The operation is ended and the next
v Use a different SYSUT4 data set. Place the SYSUT4
data set on a different physical location on the Application Programmer Response: The data set in
volume, on a different device, or on a different question should be checked for valid information and
channel. re-created or restored if necessary.

IEB174I **WARNING** INPUT RECORD IS A
utility to investigate the output directory. If the error
SHORT LENGTH RECORD
-DDNAME=DDNAME
[-OUTPUT TTRN=ttrn]
[-MEMBER=member]
the JCL and all printed output and output data sets Explanation: An unexpected short length record
related to the problem. (shorter than BLKSIZE) has been found on the
indicated input data set. It was copied from the member
to the output data set at the logical disk address
specified exactly as it was read from the input data set.
IEB172I ddname COULD NOT BE OPENED
This message is issued when one of the following
Explanation: The data set could not be opened. This conditions regarding a short block exists:
is normally the SYSPRINT data set. 1. For RECFM=F, the length of a physical record is not
In the message text: the same as the block size.
2. For RECFM=FB, the length of a physical record is
ddname not a multiple of the logical record length.
The DDNAME.
3. For RECFM=FBS, the length of a physical record
other than the last one is not the same as the block
The severity is 4.
size.
System Action: Normal processing continues. If this is
the SYSPRINT data set then only I/O error messages In the message text:
and an end-of-job message are issued, and they are
directed to the system console. ddname
The DDNAME.
IEHLIST utility to investigate the output data sets and member
verify the ending status of each operation performed. The specified member.
System Programmer Response: Look for a missing ttrn The logical disk address.
SYSPRINT DD statement.
The severity is 4.
System Action: The error is ignored.
IEB173I ddname -- INVALID BLOCK SIZE Application Programmer Response: If the error
cannot be ignored by the user, the input data set must
Explanation: An incorrect block size associated with be re-created.
the indicated data set DD statement was detected. This
is probably the SYSPRINT data set. System Programmer Response: If the error recurs
In the message text: the job log for more information. search problem
ddname reporting data bases for a fix for the problem. If no fix
The DDNAME. exists, contact the IBM Support Center. Provide the JCL
System Action: This data set cannot be used. If this the problem.
is the SYSPRINT data set then only I/O error messages
and an end-of-job message are issued, and they are Source: Data Facility Product (DFP)
directed to the system console.
Application Programmer Response: Use the IEB175I **WARNING** INPUT RECORD IS
IEHLIST utility to investigate the output data sets and GREATER THAN OUTPUT BLKSIZE -
verify the ending status of each operation performed. DDNAME=DDNAME
[-OUTPUT TTRN=ttrn]
System Programmer Response: Check the DD [-MEMBER=member]
statement for incorrect DCB information, such as block
size. If the error recurs and the program is not in error, Explanation: An input record on the indicated input
look at the messages in the job log for more data set whose length is greater than the output block
information. search problem reporting data bases for a size has been processed. If the record length is less
fix for the problem. If no fix exists, contact the IBM than or equal to the output device track capacity, then it
Support Center. Provide the JCL and all printed output was copied from the member to the output data set at
and output data sets related to the problem. the logical disk address specified exactly as it was read
(no truncation). Otherwise, the record is discarded.

In the message text: ddname
The DDNAME.
ddname
The DDNAME.
The severity is 8.
member
ttrn The logical disk address.
Application Programmer Response: Re-create the
member in error.
The severity is 4.
System Action: In the case of records greater than
the output track capacity, the operation ends and the
next control statement is sought. Otherwise, the error is
ignored.
Application Programmer Response: If the output and all printed output and output data sets related to
data set is to be updated or compressed, retry the the problem.
operation specifying a larger block size, by JCL, on the
output data set. If using full track blocking on input, be
sure not to use an output device with a smaller track
size than the data set block size. IEB177I member WAS SELECTED BUT NOT
FOUND IN ANY INPUT DATASET
Note: The stored load module will be executable, but it
will not be usable as input to either the program Explanation: The member was specified on a
management binder or the linkage editor. Before SELECT statement for the previous operation, but does
including it as input to either utility, copy the load not exist on any of the specified input data sets.
module to a data set with a block size greater than the
length of the largest text record. (The system’s
maximum block size, 32760 bytes, will always be large member
enough to contain any text record.) The specified member.
and the program is not in error, look at the messages in The severity is 4.
the job log for more information. search problem System Action: The member is ignored.
exists, contact the IBM Support Center. Provide the JCL Application Programmer Response: Check to see if
and all printed output and output data sets related to the member should have been found.
the problem. System Programmer Response: If the error recurs
Note: If this message is issued while processing a data and the program is not in error, look at the messages in
set that will be serviced with SMP/E, resolve the the job log for more information. search problem
condition causing the message before using SMP/E to reporting data bases for a fix for the problem. If no fix
modify the load module. The program management exists, contact the IBM Support Center. Provide the JCL
binder and editor will not use load modules named in and all printed output and output data sets related to
this message as input. the problem.
IEB176I MEMBER member IN DATASET IEB178I NOT AN IEBCOPY UNLOADED

REFERENCED BY ddname HAS MORE DATASET
THAN ONE NOTELIST POINTER Explanation: The input data set has sequential
Explanation: The directory entry for the member in organization so a LOAD operation is assumed. The data
the indicated data set has more than one Notelist (User set does not have the format of an IEBCOPY unloaded
TTRN with N not equal to zero). This is an unsupported data set so it cannot be processed by IEBCOPY.
format directory entry, and the member cannot be The severity is 8.
correctly processed.
In the message text: control statement is sought.
member Application Programmer Response: Verify that the
The specified member. data set in question was created by IEBCOPY.

IEB181I STORAGE CAN NOT BE ALLOCATED
FOR LOAD/UNLOAD PROCESSING --
INCREASE WORK= VALUE IN PARM
FIELD
the problem. Explanation: There is not enough virtual storage
available to complete the unload or load operation.
The severity is 8.
IEB179I {COPYMOD | ALTERMOD | System Action: The operation is ended and the next
COMPRESS} NOT VALID FOR control statement is sought.
LOAD/UNLOAD
Application Programmer Response: Make more
Explanation: The requested function, COPYMOD, virtual storage available to IEBCOPY. Make more virtual
ALTERMOD, or COMPRESS can not accept an storage available to IEBCOPY. See message IEB1055I.
unloaded data set as input, or can not produce an
unloaded data set as output.
The severity is 8. the job log for more information. search problem
Application Programmer Response: Verify that the the problem.
data sets in question have been specified correctly.
IEB182I UNLOAD DATA SET REFERENCED BY
ddname HAS BEEN FLAGGED AS NOT
LOADABLE
and all printed output and output data sets related to Explanation: An I/O error occurred while unloading.
the problem. The output data set is incomplete and cannot be
successfully reloaded. This message was preceded by
message IEB139I, or another error or attention
message.
IEB180I MORE THAN ONE INPUT DATA SET
SPECIFIED FOR UNLOAD OPERATION
ddname
Explanation: More than one input data set was
The DDNAME.
specified for an unload operation either in the same
INDD= group, or in an additional INDD= group.
The severity is 8.
The severity is 8.
System Action: The additional input data sets are not control statement is sought.
processed.
Application Programmer Response: If the I/O error
Application Programmer Response: If more than occurred on one of the output data sets or work files,
one data set is to be unloaded, use multiple operations retry the operation. If the error occurred on the input
(one for each data set to be unloaded) to different data set, it may have to be re-created.
output data sets.
System Programmer Response: Refer to
System Programmer Response: If the error recurs accompanying messages, starting with IEB139I. If the
and the program is not in error, look at the messages in error recurs and the program is not in error, look at the
the job log for more information. search problem messages in the job log for more information. search
reporting data bases for a fix for the problem. If no fix problem reporting data bases for a fix for the problem. If
exists, contact the IBM Support Center. Provide the JCL no fix exists, contact the IBM Support Center. Provide
and all printed output and output data sets related to the JCL and all printed output and output data sets
the problem. related to the problem.

parameters have been overridden, respecify the correct
IEB183I END OF FILE READ ON LOAD DATA
block size and key length.
SET REFERENCED BY ddname
Explanation: The data set:
may be used to display the block size and key length in
v contains directory entries without the corresponding the data set label. Look for an override on the ddname
members, or DD statement. If the error recurs and the program is not
v contains directory entries with incorrect member in error, look at the messages in the job log for more
TTRs, or information. search problem reporting data bases for a
v is a null data set. fix for the problem. If no fix exists, contact the IBM
In the message text: and output data sets related to the problem.
ddname Source: Data Facility Product (DFP)

The DDNAME.
IEB185I ddname IS NOT A LOADABLE DATA
The severity is 8. SET
System Action: The operation is ended and the next Explanation: The data set to be loaded was flagged
control statement is sought. as not loadable during a previous unload operation.
Application Programmer Response: Recreate the In the message text:
original data set and retry the operation.
ddname
System Programmer Response: If the error recurs The DDNAME.
the job log for more information. Search problem The severity is 8.
exists, contact the IBM Support Center. Provide the System Action: The operation is ended and the next
unloaded data set and the original partitioned data set. control statement is sought.
Source: Data Facility Product (DFP) Application Programmer Response: Re-create the
input data set and resubmit the job.
IEB184I MEMBER DATA RECORD READ FOR System Programmer Response: If the error recurs
MEMBER member REFERENCED BY and the program is not in error, look at the messages in
DDNAME IS LONGER THAN DATA SET the job log for more information. Search problem
BLOCK SIZE PLUS KEY LENGTH reporting data bases for a fix for the problem. If no fix
nnnnn CCHHRKDD=(mbbcchhr) exists, contact the IBM Support Center. Provide the JCL
Explanation: The DCB information given for the input the problem.
data set is incorrect because the input data set contains
a record that is too long. The record is part of the Source: Data Facility Product (DFP)
member specified and was read from the physical disk
address indicated. The actual length includes both the IEB186I INPUT AND OUTPUT DATASETS ON
key and data portions of the record. SAME TAPE VOLUME
In the message text: Explanation: Two data sets cannot be opened
member concurrently on the same tape volume because the
The specified member. tape can be positioned only within one data set at a
time.
ddname
The DDNAME. The severity is 8.
nnnnn The actual length. System Action: The operation is ended and the next
mbbcchhr
The physical disk address. Application Programmer Response: Copy the input
data set to a temporary data set on another volume,
The severity is 8. then recopy the temporary data set back to the desired
volume.
control statement is sought. System Programmer Response: If the error recurs
Application Programmer Response: If the DCB the job log for more information. Search problem

exists, contact the IBM Support Center. Provide the JCL Source: Data Facility Product (DFP)
the problem.
IEB189I DIRECTORY ENTRY member IN BLOCK
Source: Data Facility Product (DFP) READ FROM DDNAME DDNAME AT
MBBCCHHR mbbcchhr TTRN ttrn IS
OUT OF SEQUENCE OR DUPLICATE
IEB187I NOT A DIRECT ACCESS OR TAPE
DATASET Explanation: The directory of the data set contains
two entries with the same name, or the entries are not
Explanation: An input or output data set is allocated
in ascending sequence by name. The duplicate or out of
to other than a direct-access or tape device. This
place entry is for the member. The directory block is at
includes JES data sets, which are treated as unit record
the physical disk address indicated, and the logical disk
devices. Message IEB120I accompanies this message
address indicated. This is an attention message.
to identify the data set in error.
The severity is 8.
member
ddname
Application Programmer Response: Correct the DD
The DDNAME.
statement identified in message IEB120I.
mbbcchhr
The physical disk address.
the job log for more information. Search problem ttrn The logical disk address.
exists, contact the IBM Support Center. Provide the JCL The severity is 4.
the problem. System Action: Processing continues.
Source: Data Facility Product (DFP) Application Programmer Response: Delete

members from the data set so the directory entries
return to strict ascending sequence by name.
IEB188I MEMBER member IN DATASET
‘REFERENCED’ BY DDNAME HAS System Programmer Response: SPZAP may be
RECORDS GREATER THAN BLKSIZE used to dump the bad directory and to alter member
names in the directory. If the error recurs and the
Explanation: While reading the member from the data program is not in error, look at the messages in the job
set, a record longer than the data set block size was log for more information. Search problem reporting data
read. bases for a fix for the problem. If no fix exists, contact
the IBM Support Center. Provide the JCL, the SYSOUT
output for the job, the associated volume, the control
member statements for the job, and all printed output and output
The specified member. data sets related to the problem.
ddname Source: Data Facility Product (DFP)
The DDNAME.
IEB19AI MEMBER member {COPIED | LOADED}
The severity is 8.
AND {REBLOCKED | ALTERED}
Explanation: The member has been reblocked (or
altered) and copied (or unloaded) to the output data set.
Application Programmer Response: If the DCB The Relocation Dictionary (RLD) counts have been
parameters have been overridden, respecify the correct updated or were already correct.
block size and key length.
member
may be used to display the block size in the data set
The severity is 0.
fix for the problem. If no fix exists, contact the IBM System Action: Processing continues.
and output data sets related to the problem. Source: Data Facility Product (DFP)

copied to the output data set with no change in block
IEB19BI MEMBER member {COPIED | LOADED},
size or content. The link edit attributes of the member
{REBLOCKED | ALTERED}, AND IS A
make it ineligible for processing by COPYMOD.
NEW NAME
The old name of this member can be determined by
Explanation: The member is a renamed load module
checking the IEBCOPY control statements printed at the
which has been successfully copied (or loaded) and
beginning of the copy step in which this message
reblocked (or altered) to the output data set. The RLD
occurred.
counts have been updated or were already correct.
checking the IEBCOPY control statements printed at the member
beginning of the copy step in which this message The specified member.
occurred.
In the message text: The severity is 4.
member System Action: The member was copied unaltered.

The specified member. Application Programmer Response: Process the
module using the link editor.
The severity is 0.
System Programmer Response: The AMBLIST utility
System Action: Processing continues. may be used to check the link edit attributes of member.
IEB19CI MEMBER member {COPIED | LOADED}, IEB19EI MEMBER member {COPIED | LOADED},
text {NOT A LOAD
MODULE|INCOMPATIBLE OR
Explanation: COPYMOD has been specified. The
INELIGIBLE}
member is a load module which has been copied to the
output data set with no change in block size or content. Explanation: COPYMOD has been specified. The
The link edit attributes of the member make it ineligible member does not contain records in the format of or
for processing by COPYMOD. with the content required of load modules.
member member The specified
The specified member. member.
text One of the following: NOT A LOAD MODULE The member is not
v AS IS THEN ALTERED, MODULE IS a load module. A
PAGE-ALIGNED PDS may contain
both load modules
v AS IS WITHOUT REBLOCKING FORMAT
and non-load
IS SCATTER-LOAD
module members.
v AS IS WITHOUT REBLOCKING MODULE There is no error if
IS NON-EDITABLE the member is
indeed not a load
The severity is 4. module.
System Action: The member was copied unaltered.
The severity is 4.
Application Programmer Response: Process the
module using the link editor. System Action: The member was copied to the output
data set with no change in block size or content.
may be used to check the link edit attributes of member. If the member was partially copied before it was
recognized that it was not a load module, the copy was
Source: Data Facility Product (DFP) started again from the beginning of the member.
The system issues accompanying message IEB1142W
IEB19DI MEMBER member {COPIED | LOADED}, when INCOMPATIBLE OR INELIGIBLE is displayed.
FORMAT IS SCATTER-LOAD |, AND IS
A NEW NAME Application Programmer Response: Evaluate the
member to see if it was processed as expected.
member is a renamed load module which has been System Programmer Response: The AMBLIST utility

may be used to verify that the member is not a load System Programmer Response: The AMBLIST utility
module. may be used to verify that the member is not a load
module.
IEB19FI MEMBER member {COPIED | LOADED}
, {NOT A LOAD IEB19GI MEMBER member ALTERED IN PLACE
MODULE,|INCOMPATIBLE OR
Explanation: The Relocation Dictionary (RLD) counts
INELIGIBLE,} AND IS A NEW NAME
for the member have been inserted or updated.
member is a renamed member which does not contain
records in the format or with the content required of member
load modules. The specified member.
checking the IEBCOPY control statements printed at the The severity is 0.
beginning of the copy step in which this member System Action: Processing continues.
occurred.
member The specified IEB19HI MEMBER member NOT ALTERED, RLD
member. COUNT WAS CORRECT
NOT A LOAD MODULE The member is not Explanation: No change has been made to the
a load module. A member because the Relocation Dictionary (RLD)
PDS may contain counts were already correct.
both load modules
and non-load In the message text:
module members. member
There is no error if The specified member.
the member is
indeed not a load The severity is 0.
module.
INCOMPATIBLE OR INELIGIBLE COPYMOD cannot
unblock the module Source: Data Facility Product (DFP)
because the
common sections for
IEB19JI MEMBER member NOT ALTERED,
the module are not
FORMAT IS SCATTER-LOAD |
at the end of the
module where the Explanation: ALTERMOD has been specified. The
link editor usually member is a load module which was not altered. The
places them. The link edit attributes of the member make it ineligible for
system issues processing by ALTERMOD.
message IEB1142W
with more
information about member
this error. The specified member.

System Action: The member was copied to the output System Action: The member is not processed.
data set with no change in block size or content.
Application Programmer Response: Evaluate the
If the member was partially copied before it was member to see if should have been processed.
recognized that it was not a load module, the copy was
started again from the beginning of the member. System Programmer Response: The AMBLIST utility
may be used to check the link edit attributes of the
The system issues accompanying message IEB1142W member.
when INCOMPATIBLE OR INELIGIBLE is displayed.
member to see if it was processed as expected.

System Action: IEBCOPY uses the maximum value
IEB19KI MEMBER member NOT ALTERED, NOT
as the maximum block size. Processing continues.
A LOAD MODULE
Application Programmer Response: If a smaller
Explanation: ALTERMOD has been specified. The
maximum block size is required, specify or correct the
member does not contain records in the format or with
MAXBLK= parameter.
the content required of load modules.
A PDS may contain both load modules and non-load
module members. There is no error if the member is
indeed not a load module. IEB192I MINBLK DEFAULTS TO minimum
In the message text: Explanation: The MINBLK= parameter specifies a
value that is greater than the output data set block size,
member
greater than MAXBLK= parameter, less than 1 kilobyte
(1024), or not a number.
The severity is 0. In the message text:
System Action: The member is not processed. minimum
The minimum block size.
member to see if should have been processed.
The severity is 4.
System Action: IEBCOPY uses the minimum value as
may be used to verify that the member is not a load
the minimum block size. Processing continues.
module.
Application Programmer Response: If a different
minimum block size is required, specify or correct the
MINBLK= parameter.
IEB190I MAXIMUM BLOCK SIZE IS maximum,
MINIMUM BLOCK SIZE IS minimum
Explanation: The COPYMOD operation will copy or
IEB193I {MAXBLK | MINBLK}IS SPECIFIED ON
reblock load modules.
OTHER THAN A COPYMOD
In the message text: STATEMENT
maximum Explanation: A MAXBLK or MINBLK parameter is
The maximum block size that will be written. found with a statement other than COPYMOD.
minimum The severity is 8.
The minimum block size that will be written
specifically to optimize track space.
The severity is 0. Application Programmer Response: Change the
operation to COPYMOD or remove the MAXBLK=
and/or MINBLK= operands.
Application Programmer Response: If different
parameters are required, specify the MAXBLK= and/or
MINBLK= parameters.
IEB194I CANNOT ALLOCATE ENOUGH
STORAGE FOR ALTERMOD/COPYMOD
-- INCREASE WORK= VALUE IN PARM
IEB191I MAXBLK DEFAULTS TO maximum FIELD
Explanation: The MAXBLK= parameter specifies a Explanation: There is not enough unallocated virtual
value that is greater than the track size, greater than 32 storage available to reblock the records.
kilobyte-8 (32760), less than 1 kilobyte (1024), or not a
Virtual storage requirements vary with the input block
number.
size, the output block size, and the maximum number of
In the message text: RLD records that follow a block of text.
maximum The severity is 8.

The maximum block size.
The severity is 4.
Application Programmer Response: Make more

virtual storage available to IEBCOPY. Make more virtual
IEB198I RECFM ‘U’ REQUIRED WITH
storage available to IEBCOPY. See message IEB1055I.
{COPYMOD | ALTERMOD} FOR
Source: Data Facility Product (DFP) DDNAME ddname
Explanation: The data set associated with the
IEB195I RENAME/REPLACE NOT VALID WITH ddname DD statement does not have undefined format
ALTERMOD records, so it can not contain any load modules for a
COPYMOD or ALTERMOD operation.
Explanation: ALTERMOD has been specified. A
SELECT statement MEMBER= operand contains a new In the message text:
name and/or the replace indicator, which is not allowed.
ddname
ALTERMOD is an update-in-place operation does not
The DDNAME.
replace nor rename members.
System Action: The operation is ended and the next System Action: The operation is ended and the next
control statement is sought. control statement is sought.
Application Programmer Response: Remove the Application Programmer Response: Correct the
rename or replace specification from the ALTERMOD ddname DD statement.
statement.
Source: Data Facility Product (DFP) may be used to display the RECFM in the data set
label. Look for an override on the ddnameDD statement.
IEB196I INDD CANNOT EQUAL OUTDD WITH Source: Data Facility Product (DFP)
COPYMOD
Explanation: COPYMOD is not an update-in-place IEB199I DSORG ‘PO’ REQUIRED WITH
operation, so two different data sets must be used. {COPYMOD | ALTERMOD} FOR
Therefore, INDD= and OUTDD= must specify different DDNAME ddname
DDNAMEs.
Explanation: The data set associated with the
The severity is 8. ddname DD statement is not a partitioned data set, so it
can not contain any load modules for a COPYMOD or
ALTERMOD operation.
Application Programmer Response: Use a separate
COPY (not COPYMOD) operation if a compress in ddname
place is also desired. The DDNAME.
Make a full copy to a new data set. Substitute this
The severity is 8.
IEB197I INDD SPECIFIED WITH ALTERMOD
Application Programmer Response: Correct the DD
Explanation: ALTERMOD is an update-in-place statement.
operation. The OUTDD= specifies the single data set
that is updated. Specifying another data set (with
may be used to display the DSORG in the data set
INDD=) is meaningless.
label. Look for an override on the DD statement.
The severity is 8.
IEB201I INVALID CONTROL STATEMENT
Explanation: The syntax of the control statement
INDD= operand.
preceding this message is incorrect.
code is 12.
error. Correct the syntax of the preceding statement and
resubmit the job.

and all printed output and output data sets related to and all printed output and output data sets related to
the problem. the problem.
IEB202I INVALID DIRECTORY BLOCK SIZE IEB211I KEY LENGTHS ARE NOT EQUAL.
Explanation: The length of the partitioned data set Explanation: The key lengths of the SYSUT1 and
directory entry is less than 14 or greater than 256 bytes. SYSUT2 data sets are not equal.
System Action: The job step is ended. The return System Action: The program is ended. The return
code is 12. code is 12.
Application Programmer Response: Ensure that the Application Programmer Response: Probable user
specified data set is a PDS. Resubmit the job. error. Make sure that both input data sets contain keys
with the same length. Resubmit the job.
and all printed output and output data sets related to exists, contact the IBM Support Center. Provide the JCL
the problem. and all printed output and input and output data sets
Source: DFSMSdfp
Source: DFSMSdfp
IEB203I ALIAS/TRUE NAME FAILURE
IEB212I INVALID DCB PARAMETER
Explanation: A true name and an alias name were the
same for SYSUT1 and SYSUT2 data sets. Explanation: Either the record formats are not
standard, or the BLKSIZE/LRECL is omitted from either
System Action: The name that is a member in one
the input or output DD statement.
data set and an alias in the other data set is printed.
Processing continues with the comparison of user data. System Action: The program is ended. The return
The return code is 8. code is 12.
Source: DFSMSdfp Application Programmer Response: Make sure that
a valid RECFM was specified in the DCB, and that the
BLKSIZE/LRECL parameter was included in the input or
IEB205I USER DATA FIELDS UNEQUAL
output DD statement. If the data set resides on an
Explanation: The user data fields or TTRs of the unlabeled tape, make sure that a valid RECFM was
SYSUT1 and SYSUT2 data sets are not identical. included in the DCB parameter in the DD statement.
After making corrections, resubmit the job step.
System Action: The fields are listed and processing
continues. The return code is 8. System Programmer Response: If the error recurs
IEB210I TRUE NAMES MISSING FROM BOTH exists, contact the IBM Support Center. Provide the JCL
SETS and all printed output and output data sets related to
the problem.
Explanation: Not all the names in one directory have
counterpart names in the other directory. Source: DFSMSdfp

code is 12. IEB213I REPETITIOUS CARD INVALID
Application Programmer Response: Make sure that Explanation: A second COMPARE or LABELS
at least one partitioned data set has true names statement has been encountered.
associated with every member in the partitioned data System Action: The job is ended at the end of the
set. Resubmit the job.

control statement scan. The return code is 12.
IEB216I ILLEGAL CONTROL CARD SEQUENCE
Explanation: The COMPARE statement was not the
error. Remove the extra command statement and
first utility control statement, or two COMPARE
resubmit the job step.
statements were encountered.
System Action: The job is ended at the end of the
exists, contact the IBM Support Center. Provide the JCL error. Make sure that there is only one COMPARE
and all printed output and output data sets related to statement in the input stream. Resubmit the job.
the problem.
IEB214I FIXED RECORD LENGTHS UNEQUAL
Explanation: The record lengths of the SYSUT1 and and all printed output and output data sets related to
SYSUT2 data sets are not the same. the problem.
System Action: The program is ended. The return Source: DFSMSdfp

code is 12.
Application Programmer Response: Probable user IEB217I INVALID LRECL FOR V/VS RECORD
error. Make sure that the logical records in both data
Explanation: The LL field of a variable-length record
sets are of the same length, and that the LRECL
is less than 5, is greater than 32,756, or is greater than
parameter in both DCBs are correctly specified.
remaining size of the block.
Resubmit the job.
code is 12.
the job log for more information. Search problem Application Programmer Response: Make sure that
reporting data bases for a fix for the problem. If no fix the input data sets are valid. Resubmit the job.
the problem.
IEB215I RECORD FORMATS DIFFERENT
the problem. Have the input data sets available.
Explanation: The record characteristics of the
Source: DFSMSdfp
SYSUT1 and SYSUT2 data sets are not the same.
IEB218I PERMANENT INPUT ERROR - FIND
code is 12.
MACRO
Explanation: A permanent input error was found by
error. Make sure that the record characteristics of the
the FIND macro instruction during a partitioned data set
two data sets are compatible.
directory search.
code is 12.
reporting data bases for a fix for the problem. If no fix Application Programmer Response: See Problem
exists, contact the IBM Support Center. Provide the JCL Determination, below.
the problem.
the problem.

Source: DFSMSdfp
IEB225I JOB TERMINATED AFTER EXIT
Explanation: The return code from an exit routine
IEB219I INVALID BLKSIZE FOR V/VS RECORD
indicated that the job should be ended.
Explanation: The LL field of a variable-length block is
System Action: The job is ended. The return code is
less than 9 or greater than 32,760.
12 or 16, as determined by the exit routine.
Source: DFSMSdfp
code is 12.
Application Programmer Response: Make sure that
IEB226I WARNING - INVALID NAME
the input data sets are valid. Resubmit the job.
Explanation: The statement label either is longer than
eight characters or contains an incorrect character.
the job log for more information. Search problem System Action: Processing continues normally.
error. Correct the statement label. Resubmit the job.
the problem. Have the input data sets available. System Programmer Response: If the error recurs
Source: DFSMSdfp
IEB221I RECORDS ARE NOT EQUAL exists, contact the IBM Support Center. Provide the JCL
Explanation: Two corresponding records do not
the problem.
contain the same data, or the second part of the record
descriptor word is not equal (00). Source: DFSMSdfp
System Action: The records are printed and
processing continues. The return code is 8. IEB227I TEN CONSECUTIVE ERRORS
Source: DFSMSdfp Explanation: Ten successive unequal comparisons
have occurred, and an error routine was not specified.
IEB222I KEYS ARE NOT EQUAL System Action: If the input data sets are sequential,
the program is ended. The return code is 12. If the input
Explanation: Two corresponding keys do not contain
data sets are partitioned, processing continues with the
the same data.
next member. If the current member is the last member,
System Action: The records are printed and the program is ended. The return code is 8.
processing continues. The return code is 8.
Source: DFSMSdfp
Source: DFSMSdfp
IEB229I DDNAME ddname CANNOT BE
IEB223I EXTRA RECORD ON SYSUT2 OPENED
Explanation: The SYSUT2 data set contains more Explanation: The named DD statement does not
records than the SYSUT1 data set. exist.
System Action: The records are printed and In the message text:
ddname
Source: DFSMSdfp The DDNAME.
IEB224I EXTRA RECORD ON SYSUT1 code is 12.
Explanation: The SYSUT1 data set contains more Application Programmer Response: Either correct
records than the SYSUT2 data set. the DDNAME if it is misspelled in the DD statement or
the DDLIST, or insert a new DD statement with the
System Action: The records are printed and correct name.

IEB234I EXTRA USER INPUT TRAILER LABELS
the problem.
ON SYSUT2
Source: DFSMSdfp
Explanation: The SYSUT2 data set contains more
user input trailer labels than the SYSUT1 data set.
IEB230I SYSIN BLOCKSIZE ERROR
System Action: The extra labels are printed and
Explanation: The SYSIN DD statement specifies a processing continues. The return code is 8.
block size that is not a multiple of the specified logical
Source: DFSMSdfp
record length.
IEB235I SYSUT1 CONTAINS NO USER INPUT
code is 12.
HEADER LABELS
Explanation: The programmer requested the INHDR
the block size is a multiple of the specified logical
exit and/or label comparison, but there was no input
record length. Resubmit the job.
header label on the SYSUT1 data set.
System Action: Message IEB232I will be issued.
HEADER LABELS
the problem.
Source: DFSMSdfp
header label on the SYSUT2 data set.
IEB231I EXTRA USER INPUT HEADER LABELS
System Action: Message IEB231I will be issued.
ON SYSUT1
Source: DFSMSdfp
user input header labels than the SYSUT2 data set.
IEB237I BOTH INPUT DATA SETS CONTAIN NO
USER HEADER LABELS
Source: DFSMSdfp
exit and/or label comparison, but there were no input
header labels on the SYSUT1 and SYSUT2 data sets.
IEB232I EXTRA USER INPUT HEADER LABELS
System Action: Processing continues. The return
ON SYSUT2
code is 8.
Source: DFSMSdfp
user input header labels than the SYSUT1 data set.
TRAILER LABELS
Source: DFSMSdfp
Explanation: The programmer requested the INTLR
IEB233I EXTRA USER INPUT TRAILER LABELS trailer label on the SYSUT1 data set.
ON SYSUT1
System Action: Message IEB234I is also issued.
Source: DFSMSdfp
user input trailer labels than the SYSUT2 data set.
TRAILER LABELS
Source: DFSMSdfp
Explanation: The programmer requested the INTLR
trailer label on the SYSUT2 data set.
System Action: Message IEB233I is also issued.
Source: DFSMSdfp

IEB240I BOTH INPUT DATA SETS CONTAIN NO
USER TRAILER LABELS
Explanation: The programmer requested the INTLR reporting data bases for a fix for the problem. If no fix
exit and/or label comparison, but there were no input exists, contact the IBM Support Center. Provide the JCL
trailer labels on the SYSUT1 and SYSUT2 data sets. and all printed output and output data sets related to
the problem.
code is 8. Source: DFSMSdfp
Source: DFSMSdfp
IEB245I I/O ERROR WHILE READING USER
INPUT TRAILER LABEL ON SYSUT1
IEB241I INPUT HEADER LABELS ARE NOT
EQUAL Explanation: An uncorrectable input/output error
occurred while reading the user input trailer label on the
Explanation: Corresponding input header labels are
SYSUT1 data set.
not the same.
System Action: The SYSUT1 label is listed first,
code is 12.
followed by the SYSUT2 label. Processing continues.
The return code is 8. System Programmer Response: If the error recurs
Source: DFSMSdfp
IEB242I INPUT TRAILER LABELS ARE NOT exists, contact the IBM Support Center. Provide the JCL
EQUAL and all printed output and output data sets related to
the problem.
Explanation: Corresponding input trailer labels are not
the same. Source: DFSMSdfp
System Action: The SYSUT1 label is listed first,

followed by the SYSUT2 label. Processing continues. IEB246I I/O ERROR WHILE READING USER
The return code is 8. INPUT TRAILER LABEL ON SYSUT2
Source: DFSMSdfp Explanation: An uncorrectable input/output error
occurred while reading the user input trailer label on the
SYSUT2 data set.
IEB243I ERROR WHILE READING USER INPUT
HEADER LABEL ON SYSUT1 System Action: The program is ended. The return
code is 12.
Explanation: An uncorrectable input/output error
occurred while reading the user input header labels on System Programmer Response: If the error recurs
the SYSUT1 data set. and the program is not in error, look at the messages in
System Action: The program is ended. The return reporting data bases for a fix for the problem. If no fix
code is 12. exists, contact the IBM Support Center. Provide the JCL
and all printed output and output data sets related to IEB247I xxx INPUT {HEADER|TRAILER}
the problem. LABELS FROM BOTH DATA SETS ARE
COMPARED
Source: DFSMSdfp
Explanation: At the programmer’s request, the
indicated number of user input header or trailer labels
IEB244I I/O ERROR WHILE READING USER were compared.
INPUT HEADER LABEL ON SYSUT2
occurred while reading the user input header label on xxx The indicated number of user input header or
the SYSUT2 data set. trailer labels.
System Action: The program is ended. The return System Action: If the return code from the user exit
code is 12. routine is 16, message IEB225I is also issued.

Otherwise, processing continues normally.
IEB251I INCOMPATIBLE MAXIMUM LOGICAL
Source: DFSMSdfp RECORD LENGTH
Explanation: One of the input data sets contains
IEB248I xxx EXITS TO routine IS MADE FOR logical records greater than 32 kilobytes. The other one
{SYSUT1|SYSUT2} RETURN CODE does not.
FROM USER ROUTINE IS return-code
Explanation: The user label processing routine has code is 12.
been entered the indicated number of times for the
SYSUT1 or SYSUT2 data set, as indicated in the
both data sets contain records of compatible logical
message text. The routine returned a return code,
record length. Resubmit the job.
indicating that no more labels will be processed.
xxx The number of times the user label the job log for more information. Search problem
processing routine has been entered. reporting data bases for a fix for the problem. If no fix
routine The user label processing routine. and all printed output and output data sets related to
return-code The return code. the problem.
System Action: If the return code from the user Source: DFSMSdfp
routine is 16, message IEB225I is also issued.
Otherwise, processing continues normally. IEB252I KEYED DATA SETS. ONE CONTAINS
Source: DFSMSdfp SPANNED RECORD, THE OTHER ONE
DOES NOT
IEB249I NO RECORDS ARE COMPARED, Explanation: Both input data sets contain keyed
DATA=ONLY records. One data set has variable spanned records.
The other one does not.
Explanation: The programmer specified DATA=ONLY.
Therefore, only user header labels are processed. System Action: The program is ended. The return
code is 12.
code is 0. Application Programmer Response: Make sure that
the input data sets are of compatible characteristics.
Source: DFSMSdfp Resubmit the job.
IEB250I USER LABEL IS NOT SUPPORTED BY and the program is not in error, look at the messages in
PARTITIONED DATA SET the job log for more information. Search problem
Explanation: The programmer requested the INHDR reporting data bases for a fix for the problem. If no fix
or INTLR exit, but user labels are incorrect for exists, contact the IBM Support Center. Provide the JCL
partitioned data sets. and all printed output and output data sets related to
the problem.

keyword parameter in the COMPARE statement if the IEB253I RECORDS ARE COMPARED AT
data sets are indeed physical sequential. Resubmit the PHYSICAL BLOCK LEVEL
job. Explanation: Since both data sets contain keyed
System Programmer Response: If the error recurs spanned records or logical records greater than 32K
and the program is not in error, look at the messages in bytes, the comparison is made at the block level.
the job log for more information. Search problem System Action: Processing continues normally.
the problem.
Source: DFSMSdfp

IEB254I CORRESPONDING BLOCK LENGTHS IEB258I USER LABELS NOT COMPARED,
ARE NOT EQUAL UNABLE TO TAKE EXIT FOR ONE
DATA SET
Explanation: Corresponding block lengths are not the
same. Explanation: The programmer wishes to process the
input header/trailer labels as data, but the utility
System Action: The blocks are printed, and
program is unable to take the input header/trailer label
exit for one of the data sets. Probably, the SUL
Source: DFSMSdfp subparameter is missing from the SYSUT1 or SYSUT2
DD statement.
IEB255I CORRESPONDING RECORD LENGTHS System Action: The program is ended. The return
ARE NOT EQUAL code is 12.
Explanation: Corresponding lengths of variable or Application Programmer Response: Make sure that
variable spanned records are not the same. both the SYSUT1 and SYSUT2 DD statements specify
SUL in the LABEL parameter. Resubmit the job.
System Action: The records are printed and
processing continues. The return code is 8. System Programmer Response: If the error recurs
IEB256I IEBCOMPR DOES NOT COMPARE exists, contact the IBM Support Center. Provide the JCL
PARTITIONED DATA SETS WITH VS and all printed output and output data sets related to
RECFM the problem.
Explanation: The programmer requested that Source: DFSMSdfp

partitioned data sets containing variable spanned (VS)
records be compared. IEBCOMPR does not support this IEB259I INVALID KEYWORD IN OR BEFORE
function. COLUMN dd
System Action: The program is ended. The return Explanation: In the statement preceding this
code is 12. message, a keyword beginning in or before the column
Application Programmer Response: Specify is either incorrect or not applicable to the command for
TYPORG=PS in the COMPARE statement if the input which it was specified.
data sets are indeed physical sequential. Resubmit the In the message text:
job.
dd The indicated column.
and the program is not in error, look at the messages in System Action: The job is ended at the end of the
the job log for more information. Search problem control statement scan. The return code is 12.
error. Correct the error and resubmit the job.
the problem. System Programmer Response: If the error recurs
Source: DFSMSdfp
IEB257I JOB TERMINATED AFTER EXIT FOR exists, contact the IBM Support Center. Provide the JCL
USER VOLUME SWITCH LABEL and all printed output and output data sets related to
PROCESS the problem.
Explanation: The programmer requested that Source: DFSMSdfp

processing be ended after the volume switch input
header/trailer labels were examined in the labels exit
IEB260I MISSING COMMAND IN OR BEFORE
routine.
COLUMN dd
Explanation: In the statement preceding this
code is 16.
message, a command that should appear in or before
Source: DFSMSdfp the column is omitted. Possibly, the previous statement
indicated a continuation, but the continuation indicator
was not recognized, and the scan routine looked for a
command on the preceding statement.

System Action: The job is ended at the end of the reporting data bases for a fix for the problem. If no fix
control statement scan. The return code is 12. exists, contact the IBM Support Center. Provide the JCL
Application Programmer Response: Probable user the problem.
Source: DFSMSdfp
the job log for more information. Search problem IEB263I MISSING PARAMETER IN OR BEFORE
reporting data bases for a fix for the problem. If no fix COLUMN dd
message, a required parameter that should appear in or
the problem.
before the column is omitted.
Source: DFSMSdfp
IEB261I INVALID PARAMETER IN OR BEFORE
COLUMN dd System Action: The job is ended at the end of the
message, a keyword beginning in or before the column Application Programmer Response: Probable user
is incorrect: error. Correct the error and resubmit the job.
v The parameter is longer than eight characters. System Programmer Response: If the error recurs
v The parameter is incorrect for the preceding keyword. and the program is not in error, look at the messages in
v The parameter is not immediately preceded by an the job log for more information. Search problem
equals sign. reporting data bases for a fix for the problem. If no fix
v The parameter is misspelled.
System Action: The job is ended at the end of the the problem.
Source: DFSMSdfp
IEB264I FIRST CONTROL CARD IS NOT
System Programmer Response: If the error recurs COMPARE
Explanation: The COMPARE statement was not the
first utility control statement.
exists, contact the IBM Support Center. Provide the JCL System Action: The job is ended at the end of the
and all printed output and output data sets related to control statement scan. The return code is 12.
the problem.
Source: DFSMSdfp error. Correct the error and resubmit the job.
IEB262I MISSING KEYWORD IN OR BEFORE and the program is not in error, look at the messages in
COLUMN dd the job log for more information. Search problem
message, a required keyword that should appear in or
before the column is omitted, or a blank immediately
the problem.
preceded an equals sign.
Source: DFSMSdfp
IEB265I INVALID COMMAND IN OR BEFORE
System Action: The job is ended at the end of the COLUMN dd
Application Programmer Response: Probable user message, the command beginning in or before the
error. Correct the error and resubmit the job. column is either misspelled or not immediately preceded
or followed by a blank.

In the message text: xxxx
Last seek address of block count.
acc
Access method.
code is 12.
DCB information was valid. Resubmit the job.
and all printed output and output data sets related to reporting data bases for a fix for the problem. If no fix
the problem. exists, contact the IBM Support Center. Provide the JCL
Source: DFSMSdfp
the problem.
Source: DFSMSdfp
IEB266I CONTINUATION CARD BEGINS IN
WRONG COLUMN
IEB302I INVALID PARAMETER LIST
Explanation: The continuation statement preceding
this message does not begin in columns 4-16. Explanation: The parameter list supplied by the
programmer is incorrect; that is, the halfword pointed to
by the first word of the three-word parameter list
contains a negative number.
System Action: The program step is ended. The
return code is 12.
error. Make sure that the length of the parameter list
specified is not a negative number.
and all printed output and output data sets related to and the program is not in error, look at the messages in
the problem. the job log for more information. Search problem
Source: DFSMSdfp
IEB267I I/O ERROR jjj, sss, ddd, devtyp, ddname, the problem.
op, err, xxxx, acc
Source: DFSMSdfp
while processing on the device indicated.
In the message text, the error analysis information
Explanation: The syntax of the control statement
provided by the SYNADAF data management macro
preceding this message is incorrect, or a parameter
instruction issued by the SYNAD routine was:
value that is inconsistent with the data set content has
jjj Job name. been specified.
sss System Action: The program is ended. The return

Step name. code is 12.
ddd Application Programmer Response: Probable user

Device number of the device. error. Correct the error and resubmit the job.
devtyp System Programmer Response: If the error recurs

Device type. and the program is not in error, look at the messages in
ddname reporting data bases for a fix for the problem. If no fix
Data definition name. exists, contact the IBM Support Center. Provide the JCL
op Operation attempted. and all printed output and output data sets related to
the problem.

Source: DFSMSdfp v fixed records with an LRECL or BLKSIZE of zero; or
v variable records with incorrect block or record
IEB304I CONTROL STATEMENT INPUT ERROR descriptor words.
Explanation: A permanent input/output error was System Action: The program is ended. The return
detected while reading the SYSIN data set. code is 12.
System Action: The program is ended. The return Application Programmer Response: Make sure that
code is 12. the DCB values are correct for the data set being
processed.
Application Programmer Response: Retry the
operation. If the operation fails a second time with this System Programmer Response: If the error recurs
same message, then in all probability a hardware error and the program is not in error, look at the messages in
has occurred. Ensure the quality of the hardware the job log for more information. Search problem
medium on which the data set referenced by the SYSIN reporting data bases for a fix for the problem. If no fix
DD statement resides. Resubmit the job. exists, contact the IBM Support Center. Provide the JCL
System Programmer Response: If the error recurs the problem.
exists, contact the IBM Support Center. Provide the JCL IEB309I PERMANENT OUTPUT ERROR
the problem. Explanation: A permanent input/output error was
detected while writing the SYSUT2 data set.
Source: DFSMSdfp
code is 12.
IEB305I JOB TERMINATED AFTER LABEL EXIT
Explanation: A return code of 16 was returned by a the output DCB values are compatible with input DCB
LABEL exit routine, indicating that processing is ended. values, considering any record editing that was
System Action: The job is ended. The return code is requested.
16. System Programmer Response: If the error recurs
IEB306I JOB TERMINATED AFTER KEY EXIT exists, contact the IBM Support Center. Provide the JCL
Explanation: A return code of 12 or 16 was returned and all printed output and output data sets related to
by a KEY exit routine, indicating that processing is the problem.
ended. Source: DFSMSdfp
code is 12 or 16, as determined by the exit routine. IEB310I STOW ERROR IN OUTPUT DATA SET
Source: DFSMSdfp Explanation: A permanent error occurred while writing
the directory of the SYSUT2 data set. Possibly:
IEB307I JOB TERMINATED AFTER DATA EXIT v The SYSUT2 data set is not partitioned.
Explanation: A return code of 12 or 16 was returned v A member name was specified more than once in
by a DATA exit routine, indicating that processing is MEMBER statements.
ended. v A member name was specified in a MEMBER
statement, and a member of the same name already
System Action: The job is ended. The return code is exists in the partitioned data set.
12 or 16, as determined by the exit routine.
v Insufficient space was allocated for the directory.
Source: DFSMSdfp
code is 12.
IEB308I PERMANENT INPUT ERROR
Explanation: A permanent input/output error was the SYSUT2 data set is partitioned, a member name is
detected while reading the SYSUT1 data set. not specified more than once, and sufficient space is
allocated for the directory, as necessary.
For example, two situations that cause this message to
appear are: System Programmer Response: If the error recurs

and the program is not in error, look at the messages in and all printed output and output data sets related to
the job log for more information. Search problem the problem.
Source: DFSMSdfp
the problem. IEB316I DDNAME ddname CANNOT BE
OPENED
Source: DFSMSdfp
Explanation: The DDNAME indicated on the DD
statement does not exist. Perhaps a DDNAME is
IEB311I CONFLICTING DCB PARAMETERS
misspelled in an existing DD statement or ddlist.
Explanation: The DCB parameters in the SYSUT2 DD
statement are not compatible with those specified in the
SYSUT1 DD statement (that is, (1) the I/O blocksize is ddname
not a multiple of the I/O logical record length when the The DDNAME.
record format is FB, or F or (2) the I/O blocksize is not
at least 4 bytes larger than the I/O logical record length System Action: The job is ended. The return code is
when the record format is VB or V.) 12.
System Action: The job step is ended. The return Application Programmer Response: Probable user
code is 12. error. Correct the error and resubmit the job.
Application Programmer Response: Probable user System Programmer Response: If the error recurs
error. Make sure that the DCB parameters of the output and the program is not in error, look at the messages in
DD statement are compatible with the DCB parameters the job log for more information. Search problem
of the input DD statement, considering any editing that reporting data bases for a fix for the problem. If no fix
was requested. exists, contact the IBM Support Center. Provide the JCL
reporting data bases for a fix for the problem. If no fix IEB317I JOB TERMINATED, NO INPUT
exists, contact the IBM Support Center. Provide the JCL BLKSIZE/LRECL
the problem. Explanation: The BLKSIZE/LRECL parameter was
omitted from the input DD statement for SYSUT1.
Source: DFSMSdfp
code is 12.
IEB312I JOB TERMINATED AFTER ERROR EXIT
Explanation: A return code of 16 was returned by an error. Correct the error and resubmit the job.
ERROR exit routine, indicating that processing is ended.
System Action: The program is ended. The return and the program is not in error, look at the messages in
code is 16. the job log for more information. Search problem
IEB315I SPACE NOT AVAILABLE
Source: DFSMSdfp
Explanation: Insufficient virtual storage space is
available for the work area, buffers, and save areas.
IEB318I JOB TERMINATED, NO OUTPUT
System Action: The job is ended. The return code is BLKSIZE/LRECL
12.
Explanation: The BLKSIZE/LRECL parameter was
Application Programmer Response: Increase virtual omitted from the output DD statement for SYSUT2.
storage size and resubmit job.
System Programmer Response: If the error recurs code is 12.
reporting data bases for a fix for the problem. If no fix error. Correct the error and resubmit the job.

the job log for more information. Search problem System Action: The job is ended. The return code is
reporting data bases for a fix for the problem. If no fix 12.
error. Correct the data set characteristics (RECFM,
Source: DFSMSdfp BLKSIZE, LRECL) to be equal for the input and output
data sets, and do not edit if keys are desired on VS or
VBS records.
IEB319I INVALID SYSPRINT/SYSIN BLOCKSIZE
Explanation: The SYSPRINT/SYSIN DD statement
specifies a block size that is not a multiple of the
specified logical record length.
System Action: The program is ended. The return exists, contact the IBM Support Center. Provide the JCL
code is 12. and the program listing for the job.
Application Programmer Response: Probable user Source: DFSMSdfp
System Programmer Response: If the error recurs IEB322I JOB TERMINATED AFTER OPENING
and the program is not in error, look at the messages in OUTPUT DATA SET UPON USER
the job log for more information. Search problem REQUEST
Explanation: The input header user label routine
requires ending of the job after the output data set is
opened.
Source: DFSMSdfp
16.
IEB320I OUTPUT DATA SET WITH KEYS IN
Source: DFSMSdfp
VS/VBS PROCESSING
Explanation: During processing of other than “straight
IEB323I JOB TERMINATED AFTER HEADER
copy,” the programmer specified keys for a VS or VBS
LABEL PROCESSING
output data set. If a change is required in the data set
characteristics, or if editing is to be done, a key cannot Explanation: The programmer specified a LABELS
be specified. DATA=ONLY statement. Therefore, after the user
header labels are processed, the program is ended.
12. System Action: The program is ended. The return
code is 8.
error. Correct the data set characteristics (RECFM, Source: DFSMSdfp
BLKSIZE, LRECL) to be equal for the input and output
data sets, and do not edit if keys are desired on VS or
IEB324I xxx TIMES TO routine EXIT ROUTINE
VBS records.
Explanation: The user label exit routine has received
control the indicated number of times.
the job log for more information. Search problem In the message text:
exists, contact the IBM Support Center. Provide the JCL xxx The number of times the user label exit routine
and the program listing for the job. received control.
Source: DFSMSdfp routine The user label exit routine.

System Action: Processing is continued. The return
IEB321I INPUT DATA SET WITH KEYS IN code is 0.
VS/VBS PROCESSING Source: DFSMSdfp
Explanation: The input data set contained keys, and
either the input or output data set contained VS or VBS IEB325I LAST RETURN CODE WAS return-code
records. The other data set did not contain VS or VBS
records. If a change is required in the data set Explanation: The indicated return code was the last
characteristics, or if editing is to be done, a key cannot return code issued by the user routine specified in
be specified. message IEB324I.

return-code The return code. error. Make data set characteristics (RECFM, LRECL,
BLKSIZE) equal for input and output data sets. Do not
System Action: Processing is continued. The return
specify editing. Resubmit the job.
code is 0.
Source: DFSMSdfp
IEB326I {SYSUT1|SYSUT2} | reporting data bases for a fix for the problem. If no fix
{HEADER|TRAILER} LABEL GAVE I/O exists, contact the IBM Support Center. Provide the JCL
ERROR and the program listing for the job.
Explanation: A permanent input/output error occurred Source: DFSMSdfp
while reading or writing a SYSUT1 or SYSUT2 header
or trailer label, as indicated in the message text. If the
IEB329I PDS NOT ALLOWED WHEN
error occurred while reading or writing a header label,
INPUT/OUTPUT DATA SET HAS
the data set was not opened.
RECFM=VS/VBS
Explanation: The programmer specified that the
code is 12.
output data set should be partitioned, but the input
Application Programmer Response: Retry the and/or output data set has VS or VBS records which
operation. If the operation fails a second time with this are incorrect.
same message, ensure the quality of the hardware
medium on which the data set referenced by the
12.
SYSUT1 or SYSUT2 DD (see the details of the
message) resides. Resubmit the job. Application Programmer Response: Probable user
error. Remove the utility control statements which
specify the output data set as being a PDS, and
resubmit the job.
exists, contact the IBM Support Center. Provide the JCL and the program is not in error, look at the messages in
and the program listing for the job. the job log for more information. Search problem
Source: DFSMSdfp
IEB327I SPECIFIED KEY EXITS ARE NOT
Source: DFSMSdfp
TAKEN
Explanation: The programmer specified key exits on a
IEB330I TOTALING EXIT REQUESTS
job requiring processing of a VS or VBS data set with
TERMINATION
reformatting.
Explanation: A return code of 16 was returned by the
System Action: Key exits are not taken. Processing
programmer’s totaling routine, indicating that processing
continues. The return code is 4.
is ended.
Application Programmer Response: Do not specify
key exits.
code is 16.
Source: DFSMSdfp
Source: DFSMSdfp
IEB328I LRECL EXCEEDS 32K; STRAIGHT

IEB331I PROCESSING ENDS UPON REQUEST
COPY NOT SPECIFIED
OF TOTALING EXIT
Explanation: A process other than “straight copy” was
specified. However:
v The RECFM specified for the input or output DCB is ended, but normal end-of-data processing is
was VS or VBS. completed for the output data set.
v The LRECL specified for the input or output DCB, or
System Action: Processing is ended, but normal
both, was greater than 32,756.
end-of-data processing is completed for the output data
System Action: The job is ended. The return code is set. The return code is 8.
12.
Source: DFSMSdfp

v An operation other than GENERATE, EXITS,
IEB332I TOTALING EXIT DEACTIVATED UPON
MEMBER, RECORD, or LABELS was specified.
ITS OWN REQUEST
v The LABELS statement appears twice.
v There are more input labels than are specified by the
RECORD LABELS= n statement.
is continued, but no further totaling exits are taken.
System Action: Processing continues, but no further In the message text:
totaling exits are taken. The return code is 0.
dd the specified column.
Source: DFSMSdfp
12.
IEB333I RECORD LABELS=nnn STATEMENTS
ARE REQUIRED Application Programmer Response: Probable user
Explanation: The programmer has specified a
LABELS DATA= INPUT statement. Therefore, RECORD System Programmer Response: If the error recurs
LABELS= statements are also required. and the program is not in error, look at the messages in
nnn The number of record labels.
Source: DFSMSdfp
code is 12.
IEB337I INVALID KEYWORD IN COLUMN dd
error. If user labels are desired, insert a RECORD
LABELS= n statement and the associated labels Explanation: In the statement preceding this
statements in the input stream. If labels are not desired, message, a keyword beginning in the column is either
remove the LABELS DATA=INPUT statement. Resubmit misspelled, incorrect, or not applicable to the command
the job. for which it was specified.
the job log for more information. Search problem dd The specified column.
reporting data bases for a fix for the problem. If no fix System Action: The job is ended. The return code is
exists, contact the IBM Support Center. Provide the JCL 12.
IEB334I NO EDITING OR CONVERSION WILL and the program is not in error, look at the messages in
BE DONE the job log for more information. Search problem
Explanation: Both data sets contain VS or VBS reporting data bases for a fix for the problem. If no fix
records, have the same block size, and have the same exists, contact the IBM Support Center. Provide the JCL
logical record length. Therefore, no editing or and the program listing for the job.
conversion is done. Source: DFSMSdfp
code is 0. IEB338I INVALID PARAMETER IS COLUMN dd
Source: DFSMSdfp Explanation: In the statement preceding this
message, a parameter beginning in the column is
IEB336I INVALID COMMAND IN COLUMN dd incorrect:
v A member name contains more than eight characters.
message, the operation beginning in the specified v In the RECORD statement, the IDENT keyword is
column is incorrect: followed by more than three parameters.
v A GENERATE statement is not the first control v In the RECORD statement, the FIELD keyword is
statement. followed by more than four parameters.
v The GENERATE statement appears twice. v In the RECORD statement, the conversion
parameters in the FIELD keyword are not HE, PZ, or
v An operation is misspelled. ZD.

v In the RECORD statement, the LABELS keyword is In the message text:
not followed by a number from one to eight.
dd The specified column.
v In the LABELS statement, the parameters in the
DATA keyword are not ALL, ONLY, YES, NO, or System Action: The job is ended. The return code is
INPUT. 12.
v In the GENERATE statement, the parameter in the Application Programmer Response: Probable user
MAXFLDS, MAXNAME, MAXGPS or MAXLITS error. Correct the error and resubmit the job.
keyword is not within the specified limits.
dd The specified column. reporting data bases for a fix for the problem. If no fix
12.
Source: DFSMSdfp
IEB341I PARAMETER MISSING PRECEDING
COLUMN dd
the job log for more information. Search problem Explanation: In the statement preceding this
reporting data bases for a fix for the problem. If no fix message, a parameter that should appear before the
exists, contact the IBM Support Center. Provide the JCL column is omitted. That is, a keyword is not followed by
and the program listing for the job. a parameter, or the IDENT keyword in the RECORD
statement is not followed by all three parameters.
Source: DFSMSdfp
IEB339I COMMAND MISSING PRECEDING dd The specified column.
COLUMN dd
Explanation: In the statement preceding this code is 12.
message, no operation is specified before the column.
Possibly, the preceding statement is a continuation
statement, but the previous statement indicating the
continuation contained an error and, therefore, the System Programmer Response: If the error recurs
continuation was not recognized. and the program is not in error, look at the messages in
dd The specified column. exists, contact the IBM Support Center. Provide the JCL
error. Correct the error and resubmit the job. IEB342I INVALID SPACE ALLOCATION
System Programmer Response: If the error recurs Explanation: Required keywords in the GENERATE
and the program is not in error, look at the messages in statement are omitted, or their parameter values are too
the job log for more information. Search problem small. This message is also issued if a RECORD
reporting data bases for a fix for the problem. If no fix LABELS= n statement is not preceded by a LABELS
exists, contact the IBM Support Center. Provide the JCL DATA=INPUT statement.
Source: DFSMSdfp 12.
IEB340I KEYWORD MISSING PRECEDING error. Correct the error and resubmit the job.
COLUMN dd
Explanation: In the statement preceding this and the program is not in error, look at the messages in
message, a required keyword that should appear before the job log for more information. Search problem
the column is omitted. That is, the NAME keyword is not reporting data bases for a fix for the problem. If no fix
specified in the MEMBER statement, or the DATA exists, contact the IBM Support Center. Provide the JCL
keyword is not specified in the LABELS statement. and the program listing for the job.

Source: DFSMSdfp System Action: The program is ended. The return
code is 12.
IEB343I ALLOWED NO. OF CARDS EXCEEDED Application Programmer Response: Probable user
Explanation: Three or more LABELS statements were
encountered. Two LABELS statements are the System Programmer Response: If the error recurs
maximum number allowed. and the program is not in error, look at the messages in
code is 12.
Application Programmer Response: Probable user and the program listing for the job.
Source: DFSMSdfp
IEB347I DUPLICATE KEYWORD
reporting data bases for a fix for the problem. If no fix Explanation: In the EXITS statement preceding this
exists, contact the IBM Support Center. Provide the JCL message, a keyword is specified twice.
IEB344I WARNING: INVALID STATEMENT error. Correct the error and resubmit the job.
LABEL
Explanation: In the statement preceding this and the program is not in error, look at the messages in
message, the name field is greater than eight the job log for more information. Search problem
characters, or contains an incorrect character. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
Source: DFSMSdfp
IEB348I PRECEDING MEMBER REQUIRES
‘IDENT’
IEB345I CONTINUATION NOT STARTED IN 4-16
Explanation: Two MEMBER statements were
Explanation: The statement preceding this message encountered; however, there was no RECORD IDENT
does not contain any characters in columns 4-16, statement associated with the first MEMBER statement.
indicating that the statement is not a continuation.
However, the previous statement indicated that a
code is 12.
continuation statement was to follow.
code is 12.
the job log for more information. Search problem and the program listing for the job.
Source: DFSMSdfp
IEB349I INCONSISTENT PARAMETERS IN
Source: DFSMSdfp
FIELD OR IDENT
Explanation: The first two parameters on an IDENT or
IEB346I MISSING PARENTHESIS
FIELD keyword are not consistent with each other.
message, a closing parenthesis is omitted, or an error
code is 12.
was encountered in a parameter list before the closing
parenthesis. Application Programmer Response: Probable user

error. Make sure that the length indicator is accurate for Application Programmer Response: Make sure that
the parameter it is describing, and resubmit the job. the data set characteristics accurately describe the data
set which is being accessed. If they do not, correct
them, and resubmit the job.
and the program listing for the job. reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
Source: DFSMSdfp
IEB350I LITERAL LENGTH EXCEEDS 40
Explanation: In the RECORD statement preceding
| IEB352I WARNING: ONE OR MORE OF THE
this message, the literal specified in the FIELD keyword
| OUTPUT DCB PARMS COPIED FROM
is greater than 40 bytes.
| INPUT
| Explanation: When DCB parameters RECFM, LRECL,
12.
| and BLKSIZE are not available from the output data set,
Application Programmer Response: Probable user | the IEBGENER program copies these values from the
error. Correct the error and resubmit the job. | input data set. One or more of the three DCB
| parameters are copied. See the OS/390 DFSMSdfp
System Programmer Response: If the error recurs | Utilities for a more detailed table.
the job log for more information. Search problem | Application Programmer Response: If you want to
reporting data bases for a fix for the problem. If no fix | change the output RECFM, BLKSIZE, and LRECL,
exists, contact the IBM Support Center. Provide the JCL | always specify the RECFM (except for U) and the
and the program listing for the job. | BLKSIZE on the output DD statement. Also, the LRECL
| must be present on the output DD statement if editing is
Source: DFSMSdfp | required.
| Source: DFSMSdfp
IEB351I I/O ERROR jjj, sss, ddd, devtyp, ddname,
op, err, xxxx, acc
IEB353I INVALID DBCS CHARACTERS IN
Explanation: A permanent input/output error occurred RECORD
while processing on the device indicated.
Explanation: A record in the input data file contains
In the message text, the error analysis information characters that are not valid DBCS characters. Valid
provided by the SYNADAF data management macro DBCS characters are X'4040' and two bytes with values
instruction issued by the SYNAD routine was: of X'41' through X'FE'.
jjj Job name. System Action: The program continues until all input
sss records have been processed. The return code is 8.
Step name. Application Programmer Response: Probable user
ddd error. Correct the error and resubmit the job.
Device number of the device. Source: DFSMSdfp
devtyp
Device type. IEB354I INVALID SO AND SI CHARACTERS IN
ddname RECORD.
Data definition name. Explanation: A record in the input data file contains
op Operation attempted. SO and/or SI characters. SO and/or SI are in the wrong
location in the record, or they are unpaired (for every
err Error description. SO, you must have an SI).
xxxx System Action: The program continues until all input
Last seek address or block count. records have been processed. The return code is 8.
acc Application Programmer Response: Probable user
Access method. error. Correct the error and resubmit the job.
System Action: The job step is ended. The return Source: DFSMSdfp
code is 12.

IEB355I UNBRACKETED DBCS DATA.
Explanation: A record in the input data file contains
Source: DFSMSdfp
DBCS data that should be bracketed with SO and SI
characters but is not.
IEB360I RECORD IDENTIFYING DBCS DATA
System Action: The program continues until all input
NOT BRACKETED.
records have been processed. The return code is 8.
Explanation: A DBCS data string was found during
the search for the last record of a group that matches
the string entered in an IDENTG parameter, but the
Source: DFSMSdfp string in the input record is not bracketed by SO and SI
bytes. This record does not qualify as the last record of
the group.
IEB356I FIELD OUTPUT LOCATIONS OVERLAP
Explanation: The output location variables in a set of
field parameters overlap one another. This will result in
questionable results in the output. Application Programmer Response: Probable user
error. Correct the error and resubmit the job. IEB361I DBCS ERRORS IN RECORD
nnnnnnnnnn.
Source: DFSMSdfp
Explanation: If the input data has DBCS errors, this
message identifies the record number (starting with 1)
IEB357I DBCS DATA NOT AN EVEN NUMBER
of the record in error. Messages identifying the types of
OF BYTES
errors will follow this message.
Explanation: DBCS data must contain an even
number of bytes. This record contains data that is
identified as DBCS data, but has an odd number of nnnnnnnnnn
bytes. The record number indicated.
System Action: The program continues until all input System Action: The program continues until all input
records have been processed. The return code is 8. records have been processed.
Application Programmer Response: Probable user Application Programmer Response: Probable user
error. Correct the error and resubmit the job. error. Correct the error and resubmit the job.
IEB358I DBCS CV CONVERSION AND NO SO/SI IEB362I text

BYTES FOUND.
Explanation: This message displays questionable
Explanation: DBCS CV conversion works on mixed data in the input file. It may appear along with other
DBCS data. Mixed DBCS data must have at least one messages as additional information.
set of SO and SI bytes.
text The text of the message.
records have been processed.
Source: DFSMSdfp
Source: DFSMSdfp
IEB359I DBCS STRING LENGTH ERROR.
Explanation: There is a problem with the length of the
DBCS string. Most likely the last DBCS character is not
followed by an SI byte.

IEB363I DBCS LENGTH VARIABLE NOT AN IEB367I WARNING SYSUT2 MEMBER NAME
EVEN VALUE. NOT SPECIFIED FOR PDS
Explanation: The length variable contains a value that Explanation: An attempt was made to copy to a PDS
is not an even number. without specifying a member name on the SYSUT2 DD
statement.
records have been processed. The return code is 12. System Action: The program is terminated. The return
code is 12.
error. Correct the error and resubmit the job. Application Programmer Response: Specify at least
one GENERATE statement, one MEMBER statement
Source: DFSMSdfp
per output member, and RECORD statements as
required. Also, specify a member name on the SYSUT2
IEB364I UNBRACKETED IDENTG LITERAL. DD statement and resubmit the job.
Explanation: The literal in an IDENTG parameter is

not bracketed with SO and SI bytes. IEB368I SYSTEM DETERMINED BLKSIZE USED
FOR OUTPUT
System Action: The program ends. The return code is
12. Explanation: The SYSUT2 DD statement did not
specify a BLKSIZE. It need not be specified if LRECL
Application Programmer Response: Probable user and RECFM are available from the input data set or
error. Correct the error and resubmit the job. specified on the output data set. In these cases, if
Source: DFSMSdfp output BLKSIZE is not specified, the system will
determine an optimal BLKSIZE, SDB
(system-determined BLKSIZE).
IEB365I WARNING SYSUT2 USING RECFM=U.
UNBLOCKED. System Action: The system allows the job to run
through completion.
Explanation: The SYSUT2 DD statement did not
specify a record format but did specify a block size Application Programmer Response: None.
(BLKSIZE). The SYSUT1 DD statement specified Source: DFSMSdfp
RECFM=F. Because SYSUT2 did not specify RECFM,
the system supplies RECFM=U; thus, each block will
contain only one record. IEB401I PRINT/PUNCH STATEMENT NOT FIRST.
System Action: The system allows the job to run to Explanation: A PRINT or PUNCH statement is not the
completion. first utility control statement.
Application Programmer Response: On the SYSUT2 System Action: The program is ended. The return
DD statement, either specify all three parameters code is 12.
(RECFM, LRECL, and BLKSIZE) or specify none of the
parameters. If you specify none, IEBGENER copies
RECFM, LRECL, and BLKSIZE from the SYSUT1
statement. System Programmer Response: If the error recurs
Source: DFSMSdfp
IEB366I WARNING EMPTY DATA SET NOT exists, contact the IBM Support Center. Provide the JCL
COPIED TO TAPE. and all printed output and output data sets related to
the problem.
Explanation: An attempt was made to copy an
EMPTY data set to tape. The SYSUT2 data set will be Source: DFSMSdfp
OPENED and CLOSED and an EOF will be written on
the tape but no data will be transferred.
IEB402I INVALID OPERATION
System Action: The job runs to completion. The
Explanation: In the utility statement preceding this
return code is 4.
message, the operation is incorrect.
code is 12.

System Programmer Response: If the error recurs preceding statement. If multiple RECORD statements
and the program is not in error, look at the messages in are included, make sure that an IDENT parameter is
the job log for more information. Search problem contained in each statement except the last. The last
reporting data bases for a fix for the problem. If no fix statement does not require the IDENT parameter.
the problem.
IEB403I MORE THAN TWO TITLE
the problem.
STATEMENTS.
Source: DFSMSdfp
Explanation: More than two TITLE statements are
included. Two TITLE statements are the maximum
number allowed. IEB406I JOB TERMINATED AFTER USER EXIT
System Action: The program is ended. The return Explanation: The job was ended after control was
code is 12. returned from an exit routine.
Application Programmer Response: Probable user System Action: The program is ended. The return
error. Correct the error and resubmit the job. code is 12 or 16, as determined by the exit routine.
IEB407I JOB TERMINATED DUE TO I/O ERROR
exists, contact the IBM Support Center. Provide the JCL Explanation: A permanent input/output error was
and all printed output and output data sets related to encountered.
the problem.
IEB404I KEYWORD INVALID OR OMITTED error. Check the DCB parameters of the SYSUT1 or the
SYSIN data sets. Make sure that the maximum LRECL
size is specified for variable-length records. Make sure
message, a required keyword is either incorrect or
that TYPORG=PO was not specified for a physical
missing.
sequential data set. If SYSUT1 record format is V or
System Action: The program is ended. The return VS, make sure there are no records less than the
code is 12. minimum 5 bytes long. Make sure that SYSIN BLKSIZE
is a multiple of 80.
error. Correct the error and resubmit the job. System Programmer Response: If the error recurs
the problem.
the problem. Source: DFSMSdfp
Source: DFSMSdfp
IEB408I MEMBER memname CANNOT BE
FOUND
IEB405I PARAMETER INVALID OR OMITTED
Explanation: The member specified is not contained
in the SYSUT1 data set.
message, a required parameter is either incorrect,
inconsistent, or missing. In the message text:
System Action: The program is ended. The return memname
code is 12. The specified member name.
Application Programmer Response: Probable user System Action: The member is not printed or
error. Correct or include the required parameter on the punched. If there is another MEMBER statement, the

next member is read; otherwise, the program is ended. reporting data bases for a fix for the problem. If no fix
The return code is 8. exists, contact the IBM Support Center. Provide the JCL
the problem.
the member to be printed or punched is contained in the
SYSUT1 data set. Source: DFSMSdfp
and the program is not in error, look at the messages in IEB411I DDNAME ddname CANNOT BE
the job log for more information. Search problem OPENED
Explanation: The indicated DDNAME on the DD
statement does not exist. Perhaps a DDNAME is
misspelled in an existing DD statement or ddlist.
the problem.
Source: DFSMSdfp
ddname
The DDNAME.
Explanation: The construction of the control statement
code is 12.
preceding this message is incorrect.
code is 12.
error. Make sure that the construction of the preceding
statement is correct. If this is a TITLE card, make sure
there are valid parentheses with the ITEM keyword.
Source: DFSMSdfp
and all printed output and output data sets related to IEB412I INVALID INP/OUTP DCB PARAMETER
the problem.
Explanation: One or more parameters in the BLKSIZE
Source: DFSMSdfp or LRECL keywords were omitted from the
SYSUT1/SYSUT2 DD statement. The omitted
parameters were replaced by the value 1.
IEB410I INCORRECT RECORD STATEMENT
Explanation: The RECORD statement preceding this
code is 12.
message is incorrect.
the DCB contains all necessary parameters.
code is 12.
error. If an IDENT keyword is in the preceding RECORD
statement, make sure that the sum of the input-location
parameter minus one and the length parameter does
not exceed the SYSUT1 logical record length. If one or
more FIELD keywords are in the preceding RECORD
the problem.
statement, make sure that the sum of the input-location
parameter and the length parameter does not exceed Source: DFSMSdfp
the SYSUT1 logical record length. Also, make sure that
the sum of all length parameters, for fields defined in
the preceding RECORD statement, does not exceed the IEB414I parm PARAMETER IS TOO SMALL
specified output length minus one per printed line or per Explanation: The number of FIELD keywords, IDENT
punched card. keywords, literals, or name keywords in MEMBER or
System Programmer Response: If the error recurs RECORD statements is greater than the number
and the program is not in error, look at the messages in specified in parameter parm-MAXFLDs, MAXGPS,
the job log for more information. Search problem MAXLITS, MAXLINE, or MAXNAME.

parm The indicated parameter.
System Action: The program is ended. The return exists, contact the IBM Support Center. Provide the JCL
code is 12. and all printed output and output data sets related to
the problem.
error. Specify a greater value for the parameter. Source: DFSMSdfp
and the program is not in error, look at the messages in IEB418I VS/VBS NOT ALLOWED IN PDS
Explanation: The data set organization conflicts with
the record format; that is, if RECFM=VS or VBS, then
TYPORG must be PS.
the problem. System Action: The program is ended. The return
code is 12.
Source: DFSMSdfp
error. If SYSUT1 record format is VS or VBS, make
IEB415I VS/VBS DATA PROCESSED IN
sure that TYPORG=PO was not specified.
BLOCKS
Explanation: The LRECL specified for the VS or VBS
input data area exceeds 32,756 bytes.
System Action: Processing continues on a physical reporting data bases for a fix for the problem. If no fix
basis; that is, blocks, rather than logical records, are exists, contact the IBM Support Center. Provide the JCL
printed or punched. and all printed output and output data sets related to
the problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEB416I PREFORM, VS LRECL LARGER THAN

32K IEB419I USER RETURN CODE return-code
INVALID
Explanation: The LRECL specified for the VS or VBS
input data set exceeds 32,756 bytes, and PREFORM Explanation: The return code was returned by the
was specified in the PRINT or PUNCH utility control user. However, the return code is incorrect if it is other
statement. than 0, 4, or 16.
System Action: The program is ended. The return In the message text:
code is 12.
System Action: The return code is ignored.
error. Reformat the data set or delete the PREFORM
Processing continues according to prior conditions.
parameter from the PRINT or PUNCH control
statement. Application Programmer Response: Change the
return code to 0, 4, or 16.
IEB420I SYSIN IS EMPTY
and all printed output and output data sets related to Explanation: The SYSIN data set does not contain
the problem. any IEBPTPCH control statements.
Source: DFSMSdfp System Action: The program is ended. The return
code is 12.
IEB417I DATA SET EMPTY, RETURN CODE IS 4. Application Programmer Response: Probable user
Explanation: The data set to be printed or punched
contains no data. System Programmer Response: If the error recurs
System Action: The print or punch operation is
ended. The return code is 4.

and all printed output and output data sets related to error. Correct the incorrect keyword in the preceding
the problem. statement. If this is a LABELS command, make sure
that the keyword specified for the DATA= operand is
Source: DFSMSdfp
either ALL, ONLY, YES, or NO. If this is a PRINT
command, make sure that the parameter specified for
IEB421I I/O ERROR jjj, sss, ddd, devtyp, ddname, the CNTRL keyword is not greater than that specified
op, err, xxxx, acc for the MAXLINE keyword. If this is a PUNCH
command, make sure that neither the INITPG nor
Explanation: A permanent input/output error occurred MAXLINE keyword has been specified.
In the message text, the error analysis information and the program is not in error, look at the messages in
provided by the SYNADAF data management macro the job log for more information. Search problem
instruction issued by the SYNAD routine was: reporting data bases for a fix for the problem. If no fix
jjj Job name. exists, contact the IBM Support Center. Provide the JCL
sss the problem.
Step name.
Source: DFSMSdfp
ddd
Device number of the device.
IEB432I INVALID PARAMETER IN COLUMN dd
devtyp
Device type. Explanation: In the statement preceding this
message, a parameter beginning in the column
ddname indicated is either incorrect or not applicable to the
Data definition name. keyword for which it is specified.
op Operation attempted. In the message text:
err Error description. dd The column indicated.
xxxx System Action: The program is ended at the end of
Last seek address or block count. the control statement scan. The return code is 12.
acc Application Programmer Response: Probable user
Access method. error. Correct the incorrect parameter on the preceding
System Action: The program is ended. The return statement. If the NAME, INREC, or OUTREC keywords
code is 12. are specified, make sure that the parameter does not
exceed 8 characters.
error. Correct the error and resubmit the job. System Programmer Response: If the error recurs
reporting data bases for a fix for the problem. If no fix and all printed output and output data sets related to
exists, contact the IBM Support Center. Provide the JCL the problem.
the problem. Source: DFSMSdfp
Source: DFSMSdfp
IEB433I MISSING KEYWORD BEFORE COLUMN
dd
IEB431I INVALID KEYWORD IN COLUMN dd
Explanation: In the statement preceding this message, a required keyword that should appear before
message, a keyword beginning in the column indicated the column indicated is either omitted, preceded, or
is either incorrect or not applicable to the command for followed by an incorrect delimiter.
which it is specified.
dd The column indicated.
System Action: The program is ended at the end of
System Action: The program is ended at the end of the control statement scan. The return code is 12.
the control statement scan. The return code is 12.

error. Correct the error and resubmit the job. Source: DFSMSdfp
and the program is not in error, look at the messages in IEB436I INVALID COMMAND
message, a command is incorrect or incorrect because
of conditions set by commands, keywords, or
parameters on previous statements.
the problem.
System Action: The program is ended at the end of
Source: DFSMSdfp
IEB434I MISSING PARAMETER BEFORE
error. Correct the command on the preceding statement.
COLUMN dd
Make sure that previous keywords and parameters,
Explanation: In the statement preceding this such as MAXGPS or MAXNAME, do not conflict with
message, a required parameter that should appear this command or that no RECORD command precedes
before the column indicated is either omitted, preceded, the first MEMBER command.
or followed by an incorrect delimiter.
System Action: The program is ended at the end of exists, contact the IBM Support Center. Provide the JCL
the control statement scan. The return code is 12. and all printed output and output data sets related to
the problem.
error. Correct or include the required parameter on the Source: DFSMSdfp
preceding statement. If a TITLE statement precedes this
message, make sure that the literal in the ITEM
IEB437I INVALID ITEM PARAMETER
parameter does not exceed 40 characters.
Explanation: The “title” or “output-location” parameter
of the ITEM operand in a TITLE statement is incorrect.
the job log for more information. Search problem System Action: The program is ended. The return
reporting data bases for a fix for the problem. If no fix code is 12.
error. Make sure that the “title” field of the ITEM
the problem.
operand does not exceed 40 bytes, is not zero, or does
Source: DFSMSdfp not contain one apostrophe instead of two. Also, make
sure that the sum of the “title” length and the
“output-location” length does not exceed the output
IEB435I MISSING COMMAND PRECEDING
logical record length.
COLUMN dd
message, a required command that should appear
before the column indicated is omitted. If it is a
continuation statement, however, an error occurred on
the preceding statement.
System Action: The program is ended at the end of the problem.
Source: DFSMSdfp
IEB438I INVALID NAME
message, the statement name is either too long or
contains an incorrect character.
exists, contact the IBM Support Center. Provide the JCL System Action: Processing continues normally.
and all printed output and output data sets related to However, the control statement is ignored.
the problem.

error. Correct the error and resubmit the job. be specified on the PRINT or PUNCH utility control
statement.
and the program is not in error, look at the messages in System Action: The program is ended at the end of
the job log for more information. Search problem the control statement scan. The return code is 12.
error. If SYSUT1 specifies a physical sequential data
set, remove the MEMBER statement. If SYSUT1
the problem.
specifies a partitioned data set, specify TYPORG=PO
Source: DFSMSdfp on the PRINT or PUNCH statement.
IEB439I CONTINUATION NOT STARTED IN 4-16 and the program is not in error, look at the messages in
Explanation: In the continuation statement preceding
this message, data does not begin in columns 4 through
16.
System Action: The program is ended at the end of the problem.
Source: DFSMSdfp
error. Make sure that the continuation statement begins
IEB442I USER LABEL I/O ERROR CAUSED
in columns 4 through 16. If the statement is not a
TERM.
continuation, however, correct the previous statement
that indicates a continuation. Explanation: An uncorrectable I/O error occurred.
System Programmer Response: If the error recurs v A standard user label exit was present and the error
and the program is not in error, look at the messages in occurred during label processing.
the job log for more information. Search problem v A user totaling exit was present and the error
reporting data bases for a fix for the problem. If no fix occurred while the utility was placing data on the
exists, contact the IBM Support Center. Provide the JCL output data set.
the problem.
code is 12.
Source: DFSMSdfp
Application Programmer Response: If further
handling of the error is desired, the user exit should be
IEB440I MISSING PARENTHESIS expanded to examine the standard status information
and issue an appropriate message.
message, either a parenthesis is omitted, or there is an Source: DFSMSdfp
error within the parentheses.
System Action: The program is ended at the end of IEB443I INVALID CHARACTER IN ppppp nnnnnn
Explanation: An incorrect DBCS character code was
Application Programmer Response: Probable user encountered.
ppppp The position in the record.
the job log for more information. Search problem nnnnnn The record.
exists, contact the IBM Support Center. Provide the JCL System Action: The incorrect character code is
and all printed output and output data sets related to changed to a DBCS period. The system continues
the problem. processing. The return code is 8.

input data and resubmit the job.
IEB441I MEMBER INVALID: TYPORG NOT PO Source: DFSMSdfp
Explanation: The MEMBER statement preceding this

message is incorrect since physical sequential (PS)
organization was specified. That is, TYPORG=PO must

Source: DFSMSdfp
IEB444I UNPAIRED SO IN ppppp nnnnnn
Explanation: An SO character is not paired with an
IEB448I CONVERSION VARIABLE VC INVALID
SI.
Explanation: The VC conversion variable is present,
but the DBCS parameter is NO.
System Action: The system ends processing. The
nnnnnn The record. return code is 12.
System Action: The incorrect SO will be changed to Application Programmer Response: Correct the
an SBCS period. The system continues processing. The input parameters and resubmit the job.
return code is 8.
Source: DFSMSdfp
IEB449I LENGTH ERROR IN RECORD
Source: DFSMSdfp STATEMENT
Explanation: A DBCS conversion variable is present
IEB445I UNPAIRED SI IN ppppp nnnnnn on a record statement, but the length is odd.
Explanation: An SI character is not paired with an SO System Action: The system ends processing. The
character. return code is 12.
In the message text: Application Programmer Response: Correct the
input parameters and resubmit the job.
Source: DFSMSdfp
nnnnnn The record.
System Action: The incorrect SI is changed to an
IEB451I FIELD OUTPUT LOCATIONS OVERLAP
SBCS period. The system continues processing. The
return code is 8. Explanation: The output location variables in a set of
field parameters overlap one another. The resulting
output will be questionable.
System Action: The system ends the program.
Source: DFSMSdfp
overlap error. Submit the job again.
IEB446I ILLEGAL DBCS LENGTH ppppp nnnnnn
Source: DFSMSdfp
Explanation: A DBCS field has an odd length.
IEB500I END OF DISKETTE MAINTENANCE
ppppp The position in the record. UTILITY
nnnnnn The record. Explanation: Normal end-of-job indication.
System Action: The SO and SI characters are System Action: Normal system processing continues.
changed to an SBCS period. The system continues
Source: DFSMSdfp
processing. The return code is 8.
IEB501I INCOMPLETE TRACK 0 INFORMATION
Explanation: Track 0 of the output diskette could not
Source: DFSMSdfp
be formed because not enough information was
specified by the input track 0 and/or control statements.
IEB447I CONVERSION VARIABLE CV INVALID Message IEB512I will follow identifying the sectors in
error.
Explanation: The CV conversion variable is present,
but the DBCS parameter is NO. System Action: The job is ended.
System Action: The system ends processing. The Application Programmer Response: Provide the
return code is 12. necessary control statements and resubmit the job.

input parameters and resubmit the job.

Application Programmer Response: Correct the DS
IEB502D MOUNT OUTPUT DISKETTE ON ddd
Explanation: The read operation of the Diskette
Source: DFSMSdfp
Maintenance Utility has been completed. The diskette to
be used for output should now be mounted on the
device so processing may continue. IEB506I DS nn INVALID SPECIFICATION
In the message text: Explanation: The information specified by the DS
statement was incorrect for one of the following
ddd The indicated device.
reasons:
System Action: The system waits for the operator to v The data set identifier was specified incorrectly. The
respond, then continues processing. data set identifier must conform to the IBM standard
Operator Response: Mount the output diskette on for simple data set name.
device ddd, ready the device, and reply ‘U’ to continue v The creation and/or expiration date was specified and
processing. If the output diskette is unavailable, then was not of numeric yymmdd format, where
processing may be ended by replying ‘C’. 01=yy=99, 01=mm=12, and 01=dd=31.
Source: DFSMSdfp v The data set identifier specified was a duplicate of an
existing data set.
v The beginning of extent, end of extent, or end of data
IEB503D ddd UNEXPIRED FILES ON OUTPUT
do not maintain the proper relationship of TRK1
DISKETTE
Sector 1 ≤ BOE ≤ EOE ≤ TRK73 sector 26, BOE ≤
Explanation: During a COPY operation from one EOD, and EOD ≤ EOE plus 1.
diskette to another diskette, the diskette to be used for
output contains unexpired data sets. Note: Sector number must be ≥ 1 and ≤ 26.
In the message text: v The record length does not contain a value greater
than 0 and ≤ 128.
ddd The indicated unit.
v The bypass indicator was specified and was not a B.
System Action: The system waits for the operator’s v The write protect indicator was specified and was not
reply, then continues processing. a P.
Operator Response: If the data sets on the unit are to v The verify indicator was specified and was not a V or
be overridden, reply with ‘U’. If the data sets are not to C.
be overridden, but another diskette is available for use v The multivolume indicator was specified and was not
as the output diskette, mount the diskette on the unit, a C or L.
ready the unit and reply ‘R’. Otherwise the job may be
v The volume sequence number was specified and was
canceled by replying with a ‘C’.
not a two digit positive numeric value.
Source: DFSMSdfp
IEB504I ERROR SECTORS ON OUTPUT nn The DS statement.
DISKETTE
System Action: The job is ended.
Explanation: An I/O error was encountered while
attempting to write the output diskette.
incorrect information on the DS statement and re-submit
System Action: The job is ended. the job.
Application Programmer Response: Resubmit the Source: DFSMSdfp
job using an error-free diskette for output.
Source: DFSMSdfp IEB507I DS nn INVALID EXTENT
Explanation:
IEB505I INCORRECT FORMAT – DS v The beginning of extent, end of extent, or end of data
STATEMENT does not maintain the proper relationship of TRK1
Explanation: The DS statement preceding this Sector 1 ≤ BOE ≤ EOE ≤ TRK73 sector 26, BOE ≤
message does not conform to the standard format of: EOD, and EOD ≤ EOE plus 1.
bDSxx nnnnnnnn,lllll,sssss, eeeee,hhhhh,
[,[[b],[a],[w],[r] ,[v], Note: Sector number must be ≥ 1 and ≤ 26.
[dd],[ffffff],[gggggg]]. v The extent information overlaps an extent of an
already defined data set.

nn The DS statement. OPENED
System Action: The job is ended. Explanation: Required DD statement does not exist or
the OPEN macro instruction failed for the file specified
Application Programmer Response: Correct the by the DDNAME.
extent information and resubmit the job.
Source: DFSMSdfp
ddname
The DDNAME.
IEB508I SYSUT1 VOL1 SECTOR IN ERROR
Explanation: The VOL1 sector of the input diskette
could not be read and no VOL control statement was Application Programmer Response: Either correct
supplied, or the VOL1 sector of the input diskette was the DDNAME, if it is misspelled in the DD statement, or
incorrect for one or more of these reasons: insert a new DD statement with the correct name and
v The label identifier (bytes 01-03) does not contain JCL parameters and resubmit the job.
VOL. Source: DFSMSdfp
v The volume label number (byte 04) is not 1.
v The volume identifier (bytes 05-10) does not contain IEB512I FILE NUMBER xx – ERROR SECTOR
all alphabetic or numeric characters or is not
left-justified. Explanation: The header 1 sector for the file number
could not be read from the input diskette and no DS
v The label standard version (byte 80) does not
control statement was provided.
indicate the standard version by containing a ‘W’.
xx The file number.
Application Programmer Response: If the VOL1
sector is incorrect, correct it and resubmit the job. If the System Action: The job is ended.
VOL1 sector cannot be read, supply a VOL control
Application Programmer Response: Supply a DS
control statement for the file number and resubmit the
Source: DFSMSdfp job.
Source: DFSMSdfp
IEB509I INCORRECT CONTROL IDENTIFIER
Explanation: The control statement is not properly IEB513I READ ERROR – TRACK tt, SECTOR ss
identified.
Explanation: the track and the sector of the input
System Action: The job is ended. diskette could not be read. Any data transferred by the
read operation will be written on the output diskette. If
no data was transferred, a sector of blank characters
errors in the identifier parameter of the utility control
will be written to the output diskette. Processing
statements (VOL and DS) and resubmit the job.
continues with the next sector.
Source: DFSMSdfp
tt The track.
IEB510I {SYSUT1 | SYSUT2} UNIT INVALID
ss The sector.
Explanation: For SYSUT1, the device specified is not
3540. For SYSUT2, the device specified is not 3540 or System Action: Processing continues with the next
a direct-access device. If both SYSUT1 and SYSUT2 sector of the diskette.
specify 3540, the unit specified must not be the same
Source: DFSMSdfp
unit.
IEB514I EXCESS DS STATEMENTS
Explanation: More DS statements were provided than
and resubmit the job.
there were error sectors in the input diskette track 0. A
Source: DFSMSdfp DS statement should only be supplied for track 0
sectors that cannot be read.

excessive DS statements from the control data set and
IEB518D ddd –SECURE {INPUT | OUTPUT}
resubmit the job.
DISKETTE
Source: DFSMSdfp
Explanation: The diskette mounted for input or output
is a secure volume.
IEB515I CONTROL STATEMENT OUT OF
SEQUENCE
ddd The device indicated.
Explanation: The statement preceding this message
may be out of sequence for one of the following System Action: The system waits for the operator’s
reasons: reply, then continues processing.
v A VOL statement was encountered and it was not the
Operator Response: For an input diskette, if the
first control statement in the control data set.
volume is to be copied, reply ‘q’ (where ‘q’ is a
v A DS statement has a sequence number greater than
one-character volume accessibility indicator needed to
19 or less than 01.
gain access to the volume). If the volume is not to be
v A DS statement has a sequence number which is not
copied, processing may be ended by replying with a
greater than the sequence number on the preceding
blank. For an output diskette, if the volume is to be
DS statement.
used, reply ‘q’, where ‘q’ is the one-character volume
v A DS statement has a sequence number that is not
accessibility indicator needed to gain access to the
numeric.
volume. If the secure volume is not to be used and
System Action: The job is ended. another diskette is available for use as the output
diskette, mount the diskette on ddd, ready the device,
and reply ‘RETRY’. Otherwise, the job may be canceled
sequence error and resubmit the job.
by replying with a blank.
Source: DFSMSdfp
Application Programmer Response: If a secure
volume is to be used as the input or output diskette,
IEB516I SYSUT1 INCORRECT VOLUME notify the operator of the necessary volume security
qualifier when submitting the job.
Explanation: The volume identifier specified on the
VOL control statement was not the same as the input Source: DFSMSdfp
diskette.
System Action: The job is ended. IEB519I INVALID VOL SPECIFICATION
Application Programmer Response: Insure that the Explanation: The volume identifier specified on the
volume identifier specified on the VOL control statement VOL statement preceding this message did not consist
is the same as the volume identifier on the input of one to six left-justified alphameric characters.
diskette and resubmit the job.
Source: DFSMSdfp
volume identifier on the VOL statement and resubmit
IEB517D ddd – PROTECTED FILES ON OUTPUT the job.
DISKETTE
Source: DFSMSdfp
Explanation: The diskette mounted for output contains
write protected data sets.
IEB520I DDNAME I/O ERROR
Explanation: An I/O error occurred on the device
ddd The device indicated. specified by the DDNAME.
System Action: The system waits for the operator’s System Action: The job is ended.
reply, then continues processing.
Operator Response: If another diskette is available the type of error, resubmit the job allocating the file
for use as the output diskette, mount the diskette on the specified by the DDNAME to a different device or
device, ready the device, and reply ‘R’. Otherwise the volume.
job may be canceled by replying with a ‘C’.
Source: DFSMSdfp
Application Programmer Response: Supply an
output diskette which contains no write protected files.
Source: DFSMSdfp

IEB521I OUTPUT DISKETTE VOLUME IEB531I INVALID HDR1 FOR dsid ON ser, ddd
ACCESSIBILITY = s
Explanation: The HDR1 label for the dsid on the
Explanation: When forming track 0 for the output volume device was incorrect for one of the following
diskette, a secure data set with a data set security reasons:
indicator was detected. The VOL1 label as read from v The label identifier (bytes 01-03) does not contain
the input diskette or provided via the VOL control HDR.
statement did not have a volume accessibility indicator
v The label number (byte 04) does not contain ‘1’.
specified. Since a secure data set must reside on a
secure volume, the volume accessibility indicator for the v There are duplicate data set identifiers on this
output diskette was set to the indicated setting. diskette.
v The interchange level indicator does not indicate the
basic interchange architecture.
s The data set security indicator. v The beginning of extent (BOE) (bytes 29-33), end of
System Action: Processing continues and the VOL1 extent (EOE) (bytes 35-39), or end of data (EOD)
label of the output diskette will be written with a volume (bytes 75-79) does not maintain the proper
accessibility indicator of s. relationship of TRK1 Sector1 ≤ BOE ≤ EOE ≤ TRK73
Sector 26, BOE≤EOE, BOE≤EOD, and EOD≤EOE
Application Programmer Response: The volume address plus 1.
accessibility indicator will be required to access the data
on the diskette. Note: Sector number must be ≥ 1 and ≤ 26.
Source: DFSMSdfp v The extents of BOE and EOE overlap the extents of
another data set on the diskette.
IEB530I INVALID VOL1 LABEL on ddd, ser v The block length (bytes 23-27) contains a value of 0
or is greater than 128.
Explanation: An attempt was made to process a
v The volume sequence number is incorrect.
diskette with an incorrect VOL1 label. The VOL1 label
was incorrect for one or more of the following reasons: v The data set security qualifier was non-blank and the
volume accessibility indicator was blank.
v The label identifier (bytes 01-03) does not contain
VOL. v The block length on a continuation volume is different
from that of the preceding volume of a multivolume
v The volume label number (byte 04) is not 1.
diskette data set.
v The volume identifier (bytes 05-10) does not contain
v The Bypass Indicator does not contain a ‘blank’ or B,
all alphabetic or numeric characters or is not left
(input only).
justified.
v The Write Protect Indicator does not contain a ‘blank’
v The volume accessibility qualifier on a continuation
or ‘P’, (output only).
volume is different from that of the preceding volume
of a multivolume diskette data set. v A verified data set was requested, but the data set
was not verified.
v The label standard version (byte 80) does not
indicate the standard version by containing a ‘W’. v The Expiration Date is incorrect, (output only).
v The Data Set Security Qualifier on a continuation
In the message text: volume is different from that of the preceding volume
of a multivolume diskette data set.
ddd The device address.
ser The contents of the volume identifier field. In the message text:
System Action: If the error was data set related (e.g. ddd The device address.
volume accessibility qualifier on a continuation volume),
ser The volume identifier from the VOL1 label.
processing of the data set is ended and processing
continues with other data sets on the same diskette. If dsid The contents from the data set identifier field of
the error was volume related, processing on this the HDR1 label.
diskette is ended and processing continues with the
System Action: If the device is processing input data
next diskette.
sets, the request for the data set is ended. The system
Operator Response: Notify the owner of the diskette will continue processing with the next data set.
of the error condition.
If the device is processing output data sets, the diskette
Application Programmer Response: Correct the is flushed and the system will continue processing with
error(s) in the volume label and rerun the job, if the next diskette.
necessary.
Operator Response: If the device is being used for
Source: DFSMSdfp output, inform the owner of the diskette of the error. If

the device is being used for input, there is no response dsid The multivolume input data set.
necessary.
System Action: Wait for operator response and
Application Programmer Response: Correct the continue processing.
error(s) in the HDR1 label and rerun the job if
Operator Response: Provide the correct diskettes in
necessary.
the correct order, without any intervening diskettes, and
Source: DFSMSdfp enter REPLY xx, ‘R’ to retry and continue reading the
multivolume file. If unable to provide the correct
diskettes in the correct order, enter REPLY xx, ‘C’ to
IEB532A MOUNT vvvvvv ON ddd
cancel processing of the data set.
Explanation: During processing of a diskette data set,
the operator inadvertently unloaded a diskette with the
diskettes for the multivolume file are contiguous and in
VOLSER indicated and loaded another diskette on the
the correct order before submitting the job.
device.
Source: DFSMSdfp
vvvvvv The volume serial number.
IEB541D M ddd,vvvvvv
Explanation: The volume was specified as the
System Action: Wait until diskette with VOLSER is diskette volume containing the JCL data set, but the
mounted and continue processing. volume was not the first diskette mounted on the 3540
device.
Operator Response: Mount diskette with VOLSER
indicated. In the message text:
Source: DFSMSdfp ddd The device indicated.

vvvvvv The volume serial number.
IEB540D DISKETTE SEQUENCE ERROR, ddd,
System Action: Wait for operator response and
dsid
Explanation: An error was detected while attempting
Operator Response: Mount the diskette volume on
to open the input data set or while processing
the device, ready the device, and reply ‘R’ to retry. If
continuation diskettes of the multivolume input data set
unable to supply the diskette volume, reply ‘C’ to cancel
on the device. A continuation diskette is any diskette in
processing of the volume.
a multivolume file except the first one. The sequence
error is a result of one of the following conditions: Application Programmer Response: When
v The continuation volume in the drive unit does not submitting a diskette volume containing a JCL data set,
contain a HDR1 label describing the data set being be sure that the operator is informed of the correct
processed. This condition may arise because volume serial number.
diskettes with incorrect VOL1 or HDR1 labels have Source: DFSMSdfp
been flushed.
v The volume sequence number in the HDR1 label
IEB542D SECURE {VOLUME | DATA SET} ON
describing the first extent of the data set was one.
ddd,ser[,jobname] [,dsid]
The volume sequence number in the HDR1 label
describing the extent now in the drive unit is a value Explanation:
other than one greater than the previous volume v For a secure volume, the volume specified on the
sequence number. device is a secure volume and additional qualification
v The volume sequence number in the HDR1 label is required to access it. The additional qualification on
describing the first extent of the data set was input is required to allow further processing of the
non-blank and was not 1. data sets on the volume. On output the additional
v While opening a data set, a volume sequence qualification is required to allow data sets to be
number of other than blank or one was found in the created on the volume.
HDR1 label. v For a secure data set, the data set specified with a
v While opening a data set, a multivolume indicator of volume identifier on the device is a secure data set
L was found in a HDR1 label with a blank volume and additional qualification is required to access it.
sequence number.
In the message text: ddd The device indicated.
ddd The device indicated. ser The volume serial number.

jobname
IEB544E ASSOCIATED DATA SET LIMIT
The jobname.
EXCEEDED READING JOB jjj FROM
dsid The data set identifier. ddd
System Action: Wait for the operator response, and Explanation: While reading the job from the device
continue processing. indicated, the diskette reader encountered a DD * or DD
DATA statement with the DSID keyword, and the limit of
Operator Response: Specify the qualifier for volume associated data sets per job stream has already been
ser or specify the qualifier for data set dsid on volume reached, or more than 1,000 associated data set
identified by ser with a reply of: requests have been detected in the current job.
REPLY xx, ‘q’
where q is the one character qualifier that must match jjj The job name.
the volume accessibility indicator or data set security
indicator to gain access to the volume or data set. If no ddd The device indicated.
qualifier is available, reply with System Action: The diskette reader stops processing
REPLY xx, ‘b’. the JCL input stream and beings reading the required
associated data sets. When associated data set
If ‘b’ is replied or the correct qualifier is not supplied in processing is complete the diskette reader ends
three attempts, the data set will not be accessed. processing. The job stream beginning with the job is
flushed from the system and must be resubmitted.
operator of the necessary volume and data set security Operator Response: In order to have the diskette
qualifiers prior to submitting the job stream. reader process the remaining jobs in the input stream
after associated data set processing is complete, do
Source: DFSMSdfp one of the following:
v If the device is card reader, place the rest of the job
IEB543I ddname DD MISSING OR INVALID FOR stream, beginning with the job, back into input device.
DISKETTE READER Initiate another diskette reader task to process the
remaining jobs.
Explanation: The DD statement specified was missing
from the JCL supplied for running the diskette reader or v If the device is not a card reader, initiate another
was incorrect for one of the following reasons: diskette reader to the same input data set, specifying
the job as the starting point for the reader.
v The UNIT specified on the SYSDATA DD statement
was not a 3540 device. Application Programmer Response: The maximum
v The SYSUT2 DD statement did not describe a number of associated data sets per job stream can be
subsystem data set. increased, if necessary, by changing the PARM
specified on the EXEC statement for the diskette reader.
v The SYSUT3 DD statement did not describe a DASD
(or VIO) device to contain the intermediate partitioned Source: DFSMSdfp
data set.
IEB545I FOLLOWING DATA SET(S) NOT FOUND
ON ddd
ddname
Explanation: A delimiter (/*DSKT) diskette was
Specified the DD statement.
encountered on the device. The associated data sets
System Action: The diskette reader is ended. described in message IEB546I, which follows, are
required by the job stream but were not found on
Operator Response: If JCL parameters were diskettes on the device.
overridden using the START command, be sure that the
overridden values are valid. In the message text:
Application Programmer Response: The system ddd The device indicated.

programmer should be sure that any reader procedures
System Action: Messages IEB546I and IEB547A are
for use by IEBDKRDR contain required DD statements
written listing the data sets and requesting operator
that define valid devices.
response.
Source: DFSMSdfp
Source: DFSMSdfp

System Action: The system action is determined by
IEB546I DSNAME=dsname JOBNAME=jjj
the operator’s response.
[,VOLSER=volser]
Operator Response:
Explanation: The data set on the VOLSER indicated
is not available for the job on the device named in v If the data set(s) listed in message IEB546I are
message IEB545I. This message appears for each data available, the operator should load the diskettes
set that is not available. VOLSER appears only if it was containing those data sets into the hopper of the
coded on the DD statement describing the data set as device named in the message IEB545I, ready the
an associated data set. device, and reply RETRY. The reader will then
continue processing with these associated data sets.
v If the data set(s) are not available, the operator
dsname should reply GO. The diskette reader will then
The data set name. resume processing without the required associated
data sets.
jjj The jobname.
Application Programmer Response: All associated
data sets required for a given job stream should be
System Action: Message IEB547A is written available when the job stream is processed by the
requesting operator response. diskette reader.
IEB547D REPLY ‘RETRY’ OR ‘GO’ IEB548E ddd INPUT ERROR [,READING JOB jjj]
Explanation: This message follows messages IEB545I Explanation: An uncorrectable input error occurred
and IEB546I which describe associated data sets that while a diskette reader was reading the job in the JCL
appear to be missing from the diskettes containing input stream, or while a diskette reader was reading
associated data sets. An associated data set is associated data sets. The optional jobname is not
considered a missing data set in the following cases: specified if the error occurred while reading associated
v The requested data set is on a diskette that was fed data sets. If a blank jobname is specified, the error
into the 3540 stacker while reading part of a occurred on the JCL input stream before any job was
multivolume data set on the same diskette. encountered or after an erroneous job statement with no
jobname was encountered. When reading a multivolume
v The job stream contains more than one associated JCL data set from the 3540, the message will result
data set request for a data set that is the only data from conditions that prevent successful end-of-volume
set on the diskette. After the data set has been read processing.
to satisfy the first request, the diskette is placed in
the stacker and is therefore unavailable for other In the message text:
requests for the same data set.
v The data set identifier in the diskette label does not
match the data set identifier in the JCL associated jjj The job name.
data set request due to key entry errors. System Action: If the error occurred while reading the
v The requested data set was not on the diskettes JCL input stream, the diskette reader continues normal
submitted with the job. processing assuming that the jobs preceding the job
v The operator did not supply the correct volume indicated are the only jobs in the job stream. Jobs
accessibility qualifiers for the diskette containing the through the end of the job stream are ignored. If the
data set during the allowed three attempts. error occurred while reading associated data sets, the
diskette reader will be ended.
v The volume containing the requested associated data
set did not have a valid VOL1 label and therefore Operator Response: After the error-producing device
was placed in the stacker without searching for data has been corrected, start another diskette reader. If a
sets. jobname was written in this message, do one of the
v The index track on the volume containing the following:
requested associated data set could not be read and v If the device is card reader, place the rest of the job
the diskette was therefore placed in the stacker stream, beginning with the job indicated back into
without searching for data sets. input device. Initiate another diskette reader task to
process the remaining jobs.
In the first two cases, the missing data sets may be v If the device is not a card reader, initiate another
retrieved by replacing the diskettes in the 3540 hopper diskette reader to the same input data set, specifying
and indicating that the reader should again search the the job indicated as the starting point for the reader.
diskettes.

v If no jobname was written in this message, the whole Source: DFSMSdfp
job stream must be re-run.
Application Programmer Response: Insure that the IEB550E JOB NUMBER LIMIT EXCEEDED
IEFRDER and SYSDATA DD statements are valid. READING JOB jjj FROM ddd
Source: DFSMSdfp Explanation: The diskette reader can correctly handle
up to 9,999 jobs. A job statement was encountered in
the job stream that described a new job after 9,999 jobs
IEB549I ddname, DISKETTE READER OPEN
had already been encountered.
FAILED
Explanation: The diskette reader was unable to
OPEN the file because the OPEN macro instruction was jjj The job name.
unsuccessful for the specified file, or the IEFRDER file
is using a 3540 device and one of the following errors
was detected: System Action: The diskette reader stops processing
v The diskette data set specified as containing JCL the JCL input stream and begins reading the required
does not have 80 for a record length. associated data sets. When associated data set
processing is complete, the diskette reader ends
v No volume serial number was specified in the DD
processing. The job stream beginning with the job
statement.
indicated is flushed from the system and must be
v No data set name was specified in the DD statement resubmitted.
or supplied in the START command.
Operator Response: In order to have the diskette
v The data set specified in the DD statement could not
reader process the remaining jobs in the input stream
be located on the specified diskette.
after associated data set processing is complete, do
v The operator was unable to provide volume one of the following:
accessibility or data set security qualifiers for the
v If the device is a card reader, place the rest of the job
requested data set.
stream, beginning with the job indicated, back into
v The specified volume has an incorrect VOL1 label. the input device. Initiate another diskette reader task
v The HDR1 label describing the specified data set is to process the remaining jobs.
incorrect. v If the device is not a card reader, initiate another
v A permanent I/O error occurred while trying to read diskette reader to the same input data set, specifying
the label track on the specified diskette. the job indicated as the starting point for the reader.
v A delimiter (/*DSKT) was provided in the 3540 as the Application Programmer Response: The maximum
diskette containing the JCL data set. number of associated data sets per job stream can be
v A reply of ‘C’ was given to message IEB541A. increased, if necessary, by changing the PARM
v The volume serial number specified is an incorrect specified on the EXEC statement for the diskette reader.
diskette volume identifier. Source: DFSMSdfp

IEB551I DATA SET NOT AVAILABLE –
ddname CODE=ccc
The file specified by the OPEN.
Explanation: The data set specified in the DD
System Action: The diskette reader is ended. statement preceding this message was not successfully
Operator Response: Ensure that the correct volume retrieved from the associated data set stream for the
serial number and data set name were supplied in the reason indicated by the condition code.
START command and the correct diskette was provided In the message text:
in the 3540. Ensure that the correct volume accessibility
and data set security qualifiers were provided if ccc the condition code, as follows:
requested by the diskette reader. Code Explanation
Application Programmer Response: If the operator 132 The operator replied ‘GO’ after
was unable to correct the problem, the programmer messages IEB545, IEB546, and
should ensure that his run instructions were correct. If IEB547 were issued describing this
the run instructions were correct, the diskette that data set.
contains the JCL should be checked for label incorrectly
or errors. If the diskette is good, or if no diskette was 202 Requested data set was found but
involved in the error, the system programmer should operator did not successfully supply
ensure that procedures used for starting the diskette the volume accessibility qualifier.
reader correctly define the required files.

204 Requested data set was found, but Application Programmer Response: Correct the
operator did not successfully supply problem indicated by the return code and resubmit the
the data set security qualifier. job.
212 Requested data set id described by Source: DFSMSdfp
an incorrect HDR1 label. Message
IEB531I indicates possible causes.
IEB552I INVALID PARAMETERS SUPPLIED TO
216 Requested data set was found, but DISKETTE READER
permanent I/O error occurred while
Explanation: The value supplied for the PARM=
priming buffers.
keyword on the EXEC statement of the JCL or as a
224 A volume sequence error was PARM= override in the START command was not
detected while attempting to open the numeric or exceeded six characters.
data set. The operator replied ‘C’ to
System Action: The diskette reader is ended.
message IEB540D.
Operator Response: If a PARM override was supplied
228 The VOLSER specified in JCL was
in the START command, check its validity. If in error,
found, but it did not contain the
issue another START command using valid parameter
requested data set. If there were
values.
duplicate VOLIDs in an ADS stream,
the first volume encountered with a Application Programmer Response: If the error is
given identifier must contain data sets not in operator provided parameter values, correct the
specifying that VOLID or this message errors in the JCL provided to run the diskette reader.
results.
Source: DFSMSdfp
300 Requested data set was found and
opened, but an error was encountered
while reading the data set. IEB553I DISKETTE READER UNABLE TO GET
TABLE SPACE
310 Requested data set was found and
opened, but an incorrect VOL1 label Explanation: The program was unable to get space
was encountered in EOV processing for a data set name table large enough to accommodate
for a multivolume data set. Message the number of associated data sets specified on the
IEB530I indicates possible reasons PARM= keyword.
the VOL1 label was incorrect. System Action: The diskette reader is ended.
312 Requested data set was found and Operator Response: Start the program again
opened, but an incorrect HDR1 label specifying a smaller PARM= value.
was encountered in EOV processing
for a multivolume data set. Message Application Programmer Response: Change the
IEB531I indicates possible reasons JCL used to run the diskette reader so that the PARM=
the HDR1 label was incorrect. value is small enough to have space acquired.
316 Requested data set was found and Source: DFSMSdfp

opened, but a permanent I/O error
occurred while reading the data set. IEB554E ddname, DISKETTE READER I/O
320 Requested data set was found and ERROR [,PROCESSING JOB jjj ]
opened, but a delimiter diskette was Explanation: An I/O error occurred on the file
encountered while reading the data specified by either SYSUT2 or SYSUT3. The error
set. prevents further processing by the diskette reader. A
324 Requested data set was found and blank jobname indicates the error occurred before a job
opened, but during EOV processing of was encountered in the JCL stream or after an
a multivolume data set, the operator erroneous job statement with no jobname was
replied ‘C’ to message IEB540A. encountered.
408 The volume identifier specified in JCL In the message text:

was incorrect as a volume identifier ddname
for a diskette. The DD name.
System Action: Processing was discontinued for data jjj The job name.
set specified by the data set identifier. The job
requesting the data set will be run TYPRUN=SCAN in System Action: The diskette reader is ended. If some
order to pass this message back to the programmer as jobs have been passed to the subsystem, the optional
a JCL comment statement. jobname in the message will indicate at which job the

job stream processing should be resumed on a later Operator Response: Remove the remainder of the
attempt. The job named in the message may have been jobstream from the hopper and feed mechanism if a
partly passed to the internal reader before the error card reader is used to read JCL. Use a merge mode
occurred. reader to process the remainder of the jobstream
starting with the job indicated.
Operator Response: Start the diskette reader again. If
no jobname was specified, the entire job stream must Source: DFSMSdfp
be re-run. If a jobname was specified, only the jobs
starting with the specified job must be re-run.
IEB570I ddd,ser NON-SCRATCH DISKETTE
Application Programmer Response: Ensure that the FOUND
specified DD statement is satisfactory for the diskette
Explanation: The diskette that was just fed into the
reader.
stacker was not a scratch diskette (that is, it contained a
Source: DFSMSdfp write protected data set or an unexpired data set) and,
therefore, was not suitable to receive an output data
set.
IEB555E DISKETTE READER DIRECTORY
ERROR In the message text:
Explanation: The diskette reader issued a STOW or ddd The device address.
BLDL macro instruction to access the directory of the
ser The volume identifier from the VOL1 label.
SYSUT3 intermediate file. The STOW or BLDL could
not be successfully completed for one of the following System Action: Continue processing with the next
reasons: diskette.
v Not enough directory blocks were allocated for the Operator Response: Provide additional scratch
SYSUT3 file, (applicable to STOW only). diskettes, if needed, to allow the diskette writer to
v The directory access failed because of permanent I/O complete processing.
errors.
Source: DFSMSdfp
v Insufficient virtual storage was available to perform
the STOW or BLDL function.
IEB571I jjj, dsid ON VOL(S) xx [, xxx,xxx,xxx,xxx]
Explanation: A diskette writer has written the data set
Operator Response: If the number of associated data identified for the job indicated, on the diskette(s) having
sets to be processed (PARM= value) or the number of the volume serial(s) listed. If the data set spans more
directory entry blocks allocated to the SYSUT3 file were than five diskettes, the message appears after the fifth
modified via the START command, insure that the diskette has been completed, and will be issued again
values were reasonable. The number of associated data to list the next group of diskettes used.
sets should not be so large as to leave no virtual
storage for the STOW function. The number of directory In the message text:
entry blocks should be 1 + (number of ADS ÷ 20). If
jjj The job name.
these values were reasonable, the error was caused by
an I/O error in the SYSUT3 file. Correct the cause of dsid The data set identifier.
the error if possible, and start the diskette reader again
xxx The listed volume serial numbers.
to run the job stream.
System Action: Continue processing.
number of associated data sets and number of directory Operator Response: The operator may use this
entry blocks specified in the JCL. Then rerun the information to correlate the diskettes with the jobs
diskette reader. submitted.
IEB556E DSID KEYWORD ENCOUNTERED IEB572E ddd DISKETTE WRITER CLOSED,

READING JOB jjj OUTPUT ERROR
Explanation: A direct mode diskette reader detected Explanation: This message occurs when a permanent
the DSID keyword while processing the job. I/O error is encountered by the diskette writer on the
device.
jjj The job name.

System Action: The diskette writer to device ddd is jjj The job name.
ended.
Operator Response: Change the diskette and start
System Action: Wait for the operator response, and
another diskette writer. Save the diskette.
Source: DFSMSdfp
Operator Response: Specify the security parameters
for the data set with the jobname as requested by the
IEB573E DATA SET NOT WRITTEN FOR, JOB= programmer. The general form of the reply is:
jjj, CLASS=c
REPLY xx,‘YYMMDD,w,d,v’
Explanation: The diskette writer has selected a
YYMMDD is the expiration date that the data set can be
SYSOUT data set for the job indicated with output in the
purged.
class indicated that did not have a DSID specified on its
DD statement. A DSID is required for data sets being w is the write protect indicator to indicate that the data
written to a 3540 device. set is write protected. This must be a blank or ‘P’.
In the message text: d is the one character data set security indicator. To
secure a data set, both the data set security and
jjj The job name.
volume accessibility indicators must be set.
c The class.
v is the one character accessibility indicator. This
System Action: The data set is unallocated KEEP in secures the volume from unauthorized access.
the class. The data set remains on spool.
If a parameter is not to be specified, the comma should
Operator Response: Route the data set to the
be entered to denote the missing parameters. r
appropriate class for output for processing to some
xx,‘741231,,,x’ indicates the expiration date and volume
device other than a 3540.
accessibility. r xx,‘,P’ specifies write protection.
Application Programmer Response: If a data set is
to be written on a diskette, be sure to specify a DSID on All data sets get a minimum of one day date protection
the SYSOUT DD statement for that data set. and sequence number protection. When extended
security is used while processing in multi-data sets per
Source: DFSMSdfp
diskette mode, the volume accessibility indicator must
be specified for the first data set to be secured and
IEB574I IEFRDER DD STATEMENT MISSING OR cannot be specified for any other data sets on that
INVALID FOR DISKETTE WRITER diskette.
Explanation: There was no IEFRDER DD statement Application Programmer Response: Notify the
supplied in the JCL or the diskette writer was started to operator of the level of data set security required for the
a device that was not a 3540. data set with the jobname.
System Action: The diskette writer is ended. Source: DFSMSdfp
Operator Response: Specify a 3540 when the 3540
External Writer is started. IEB576I SYSIO ERROR ON dsid FOR JOB jjj
Application Programmer Response: The system Explanation: While processing the data set for the job
programmer should be sure that diskette writer indicated the diskette writer (IEBDKWTR) detected an
procedures specify a 3540 as the device for the uncorrectable I/O error reading the data set from spool.
IEFRDER DD statement.
Source: DFSMSdfp
dsid The data set identifier.
jjj The job name.
IEB575A SPECIFY SECURITY FOR
DSNAME=dsname, JOB=jjj, ON ddd System Action: The diskette writer will stop
processing the input data set and will go on to process
Explanation: A diskette writer has been started to
other input data sets.
write secure data sets on the device. The data set for
the job indicated requires the operator to specify the Application Programmer Response: Recreate the
security parameters. data set by processing the job step that produced it.
dsname
The data set name.

exists, contact the IBM Support Center. Provide the JCL the same data set identifiers, care should be taken to
and all printed output and output data sets related to insure that they are processed in one data set per
the problem. diskette mode.
IEB577E ddd DISKETTE WRITER ENDED, {OPEN IEB579I INVALID PARAMETERS SUPPLIED TO
| SUBSYSTEM | ALLOCATION} ERROR THE DISKETTE WRITER
Explanation: The diskette writer to the device Explanation: The parameters supplied for the PARM=
detected an error condition that was uncorrectable keyword on the EXEC statement of the JCL, the
based on the return codes received from one of the PARM= override in the START command, or the fourth
following: positional parameter of the START command were
v The subsystem interface. incorrect.
v The subsystem System Action: The diskette writer is ended.
v Dynamic allocation/unallocation. Operator Response: If a START command was used
v Subsystem data set. to override parameters in the JCL, check to be sure
they were valid. If they were incorrect, issue another
System Action: The diskette writer to device ddd is
START command using valid parameters. If they were
ended.
valid, notify the programmer.
Operator Response: Report this message to the
system programmer and make sure the problem
errors in the JCL provided to run the diskette writer.
determination information is available.
Source: DFSMSdfp
Application Programmer Response: For allocation
and subsystem errors, the system programmer should
examine the error message IEB581E, in the message IEB580I OPEN ERROR – DISKETTE WRITER
data set.
Explanation: The diskette writer was unable to OPEN
System Programmer Response: If the error recurs the IEFRDER file because the OPEN macro instruction
and the program is not in error, look at the messages in was unsuccessful.
System Action: The diskette writer is ended.
exists, contact the IBM Support Center. Provide the Application Programmer Response: The
SYSOUT output for the job and all printed output and programmer should insure that the JCL used for starting
output data sets related to the problem. the diskette writer is correct.
IEB578I ddd DUPLICATE DATA SET IDENTIFIER IEB581E {SUBSYSTEM INTERFACE |

dsid FOR jjj SUBSYSTEM REQUEST | DYNAMIC
ALLOC/UNALLOC} ERROR, return-code
Explanation: While processing diskette output data
sets for the job indicated in multiple data sets per Explanation: The diskette writer detected a return
diskette mode, the diskette writer to the device code from the subsystem interface, subsystem request,
encountered two data sets with the same data set or dynamic allocation and could not recover.
identifier.
System Action: The diskette writer is ended.
jjj The job name.
dsid The data set identifier. cause of the error indicated by the return code and
rerun the job.
System Action: The diskette writer will write the data
set on the next scratch diskette and continue System Programmer Response: If the error recurs
processing. and the program is not in error, look at the messages in
Operator Response: Inform the programmer that
submitted the job of this condition.
Application Programmer Response: When JCL, the SYSOUT output for the job, and all printed
submitting jobs that create diskette output data sets with output and output data sets related to the problem.

Source: DFSMSdfp acc
Access method.
IEB600I UTILITY PROGRAM IEBISAM HAS System Action: The program is ended. The return
SUCCESSFULLY COMPLETED THE code is 8.
REQUESTED OPERATION
Application Programmer Response: Make sure the
COMPLETION CODE=00
DCB information is consistent with the original indexed
Explanation: The program has successfully completed sequential data set.
the requested operation.
System Action: Program operation has completed. and the program is not in error, look at the messages in
The return code is 0. the job log for more information. Search problem
Source: DFSMSdfp
IEB601I DCB FIELD VALUES INCONSISTENT the problem.
COMPLETION CODE=08
Source: DFSMSdfp
Explanation: One or more of the following DCB
subparameters are incorrect: RECFM LRECL, BLKSIZE,
IEB603I DUPLICATE RECORD COMPLETION
RKP, and KEYLEN.
CODE=08
System Action: The program is ended. The requested
Explanation: A record key is identical to a record key
operation is not performed. The return code is 8.
previously placed in the indexed sequential data set.
Application Programmer Response: Probable user Possibly, the RKP or the KEYLEN parameter has been
error. Correct the incorrect DCB subparameters. changed. This message appears for a LOAD operation
only.
and the program is not in error, look at the messages in System Action: The program is ended.
the job log for more information. Search problem Reconstruction of the indexed sequential data set is
reporting data bases for a fix for the problem. If no fix incomplete. The return code is 8.
Application Programmer Response: UNLOAD the
original indexed sequential data set and respecify the
the problem.
LOAD operation. Also, specify the original DCB
Source: DFSMSdfp parameters in the SYSUT1 and SYSUT2 DD
statements.
IEB602I jjj, sss, ddd, devtyp, ddname, op, err, System Programmer Response: If the error recurs
xxxx, acc COMPLETION CODE=08 and the program is not in error, look at the messages in
Explanation: A permanent input/output error occurred reporting data bases for a fix for the problem. If no fix
while processing on device ddd. In the message text, exists, contact the IBM Support Center. Provide the JCL
the error analysis information provided by the and all printed output and output data sets related to
SYNADAF data management macro instruction issued the problem.
by the SYNAD routine was:
Source: DFSMSdfp
jjj Job name.
sss IEB604I NUMBER OF CHARACTERS TO BE
Step name. TRANSMITTED EXCEEDS LIMIT
ddd COMPLETION CODE=08
Device number of the device. Explanation: The number of characters in a
devtyp fixed-length record exceeds the value specified in
Device type. LRECL or in LRECL + KEYLEN (for fixed-length,
unblocked records with a relative key position of 0). This
ddname message appears for a LOAD operation only.
Data definition name.
System Action: The program is ended. The requested
op Operation attempted. operation is not performed. The return code is 8.
err Error description. Application Programmer Response: Probable user
xxxx error. Correct the LRECL subparameter and unload the
Last seek address or block count.

original indexed sequential data set. Then, respecify the and all printed output and output data sets related to
LOAD operation. the problem.
IEB608I INVALID OPTION IN THE PARM FIELD
OF THE EXECUTE CARD COMPLETION
CODE=16
the problem. Explanation: The PARM parameter of the EXEC
statement is incorrect.
Source: DFSMSdfp
code is 16.
IEB605I CLOSE REQUESTED BY USER AFTER
A USER EXIT COMPLETION CODE=04 Application Programmer Response: Probable user
Explanation: The return code returned by the user
was either 4 or 12. System Programmer Response: If the error recurs
code is 4.
Source: DFSMSdfp exists, contact the IBM Support Center. Provide the JCL
the problem.
IEB606I ILLEGAL RETURN CODE RECEIVED
FROM A USER EXIT COMPLETION Source: DFSMSdfp
CODE=12
Explanation: The return code returned by the user IEB609I INPUT SEQUENCE ERROR
was other than 0, 4, 8, or 12. COMPLETION CODE=08
System Action: The program is ended. The return Explanation: Either a record was lost, or a noise
code is 12. record was encountered when loading an indexed
sequential data set. Possibly, the RKP, KEYLEN, or
OPTCD parameter has been changed.
error. Correct the user exit routine to issue a valid return
code. System Action: The program is ended. The return
code is 8.
and the program is not in error, look at the messages in Application Programmer Response: If possible, use
the job log for more information. Search problem a backup copy of the unloaded data set. UNLOAD the
reporting data bases for a fix for the problem. If no fix original indexed sequential data set, and respecify the
exists, contact the IBM Support Center. Provide the JCL LOAD operation. Also, specify the original DCB
and all printed output and output data sets related to parameters in the SYSUT1 DD statement.
the problem. Have a listing of the exit routine available.
IEB607I SYSUT2 OR SYSUT1 DD CARD
MISSING. COMPLETION CODE=16
Explanation: No SYSUT1 or SYSUT2 DD statement the problem.
was included in the job step.
Source: DFSMSdfp
code is 16.
IEB700I DATA GENERATION HAS BEEN
Application Programmer Response: Probable user [SUCCESSFULLY] COMPLETED.
error. Correct the error and resubmit the job. COMPLETION CODE IS ccc
System Programmer Response: If the error recurs Explanation: If the code is ZERO, data generation
and the program is not in error, look at the messages in was successfully completed.
If the code is FOUR, the job step was ended at the
request of the user.

If code is EIGHT, an error occurred while processing a
IEB703I INVALID KEYWORD VALUE.
utility control statement.
DELIMITER, DESCRIPTOR OR TYPE IS
If the code is TWELVE, an error occurred while IMPROPER OR DUPLICATED. AN FD
processing an input or output data set. NAME HAS OCCURRED PREVIOUSLY.
If the code is SIXTEEN, incorrect parameters were Explanation: The keyword value pinpointed by
encountered in a data control block while opening a message IEB727I (if any) is incorrect. Possibly:
data set. v A double quote specified within a picture caused an
In the message text: incorrect length.
v A starting character of * was used when AL or AN
ccc The completion code. format was specified.
System Action: The program is ended. v A character other than 0-9 or A-F was used when a
hexadecimal digit was to be specified.
Application Programmer Response: If the code is
ZERO or FOUR, no action is necessary. v A non-numeric character was used when a decimal
number was to be specified.
If the code is EIGHT, correct the appropriate control
v A keyword was misspelled.
statements, and resubmit the job step.
v An FD statement contained a previously used name.
If the code is TWELVE, correct the error condition
v Mutually exclusive subparameters are encountered
described in message IEB729I, and resubmit the job
such as FORMAT=CO and ACTION=RO. In this
step.
case, message IEB727I will not precede this
If the code is SIXTEEN, correct the appropriate DD message.
statement, and resubmit the job step.
System Action: Syntax checking of the remainder of
System Programmer Response: If the error recurs the utility control statements in this set continues, but no
and the program is not in error, look at the messages in additional data is generated. Processing continues
the job log for more information. Search problem normally with the next DSD statement encountered. The
reporting data bases for a fix for the problem. If no fix return code is 8.
error. Since the output data set may have been only
the problem.
partially completed, run IEHPROGM to scratch the data
Source: DFSMSdfp set, if necessary. Correct the error and resubmit the job.
IEB702I OPERATION WAS NOT DSD, FD, and the program is not in error, look at the messages in
CREATE, REPEAT, OR END. CORRECT the job log for more information. Search problem
AND RERUN. reporting data bases for a fix for the problem. If no fix
Explanation: The preceding utility control statement
specified an incorrect operation; that is, the operation
the problem.
was not DSD, FD, CREATE, REPEAT, or END.
Source: DFSMSdfp
the utility control statements in this set continues, but no
additional data is generated. Processing continues IEB704I INPUT DDNAME ON CREATE OR FD
normally with the next DSD statement encountered. The CARD IS NOT SPECIFIED ON DSD
return code is 8. CARD.
Application Programmer Response: Probable user Explanation: The ddname specified on a CREATE or
error. Since the output data set may have been only FD statement was not referred to on the DSD statement
partially completed, run IEHPROGM to scratch the data beginning this set of utility control statements. The
set, if necessary. Correct the error and resubmit the job. IEBDG program was unable to open the data set.
System Programmer Response: If the error recurs System Action: Syntax checking of the remainder of
and the program is not in error, look at the messages in the utility control statements in this set continues, but no
the job log for more information. Search problem additional data is generated. Processing continues
reporting data bases for a fix for the problem. If no fix normally with the next DSD statement encountered. The
exists, contact the IBM Support Center. Provide the JCL return code is 8.
the problem.
Source: DFSMSdfp partially completed, run IEHPROGM to scratch the data
set, if necessary. Correct the error and resubmit the job.

IEB707I FD NAME ON CREATE CARD IS NOT
PREVIOUSLY DEFINED BY AN FD
CARD OR IS NOT ASSOCIATED WITH
CORRECT DCB.
the problem.
Explanation: The NAME parameter on a CREATE
Source: DFSMSdfp
statement does not specify a value previously defined
on an FD statement.
IEB705I INVALID KEYWORD, POSSIBLE
IMBEDDED COMMA.
Explanation: The keyword pinpointed by message additional data is generated. Processing continues
IEB727I is incorrect. Possibly, the keyword is misspelled normally with the next DSD statement encountered. The
or contains an embedded comma. return code is 8.
System Action: Syntax checking of the remainder of Application Programmer Response: Probable user
the utility control statements in this set continues, but no error. Since the output data set may have been only
additional data is generated. Processing continues partially completed, run IEHPROGM to scratch the data
normally with the next DSD statement encountered. The set, if necessary. Correct the error and resubmit the job.
return code is 8.
Application Programmer Response: Probable user and the program is not in error, look at the messages in
error. Since the output data set may have been only the job log for more information. Search problem
partially completed, run IEHPROGM to scratch the data reporting data bases for a fix for the problem. If no fix
set, if necessary. Correct the error and resubmit the job. exists, contact the IBM Support Center. Provide the JCL
the problem.
IEB708I PICTURE LENGTH TOO LARGE FOR
CONVERSION
the problem.
Explanation: A decimal picture was to be converted to
Source: DFSMSdfp
packed decimal or to a binary equivalent; however, the
number of digits specified in the picture exceeds 16. No
IEB706I NUMBER SPECIFIED IS LARGER THAN conversion is performed.
32,767 OR EXCEEDS MACHINE
CAPACITY.
Explanation: A length parameter on an FD statement additional data is generated. Processing continues
was specified larger than 32,767 or machine capacity normally with the next DSD statement encountered. The
during an INDEX operation. No conversion is return code is 8.
performed.
System Action: Syntax checking of the remainder of error. Since the output data set may have been only
the utility control statements in this set continues, but no partially completed, run IEHPROGM to scratch the data
additional data is generated. Processing continues set, if necessary. Correct the error and resubmit the job.
normally with the next DSD statement encountered. The
return code is 8.
Application Programmer Response: Probable user the job log for more information. Search problem
error. Since the output data set may have been only reporting data bases for a fix for the problem. If no fix
partially completed, run IEHPROGM to scratch the data exists, contact the IBM Support Center. Provide the JCL
set, if necessary. Correct the error and resubmit the job. and all printed output and output data sets related to
the problem.
the problem.

IEB709I USER EXIT ROUTINE RETURNED AN
INVALID RETURN CODE
Explanation: The return code returned from the user reporting data bases for a fix for the problem. If no fix
exit routine was other than 0, 4, 12, or 16. exists, contact the IBM Support Center. Provide the JCL
the problem.
additional data is generated. Processing continues Source: DFSMSdfp
return code is 8.
IEB712I CONTROL CARD NAME OR KEYWORD
Application Programmer Response: Probable user VALUE EXCEEDS 8 CHARACTERS
Explanation: The length of a keyword value or control
statement name is greater than 8 characters.
set, if necessary. Correct the user exit routine so that a
valid return code is returned and resubmit the job. System Action: Syntax checking of the remainder of
additional data is generated. Processing continues
Support Center. Have program listing of the associated
user exit routine available.
return code is 8.
Source: DFSMSdfp
IEB710I UNABLE TO GET ENOUGH SPACE TO partially completed, run IEHPROGM to scratch the data
PROCESS REMAINING CONTROL set, if necessary. Correct the error and resubmit the job.
CARDS
Explanation: A GETMAIN operation was unable to get and the program is not in error, look at the messages in
sufficient space to process the remaining control the job log for more information. Search problem
statements. reporting data bases for a fix for the problem. If no fix
the problem.
normally with the next DSD statement encountered. The Source: DFSMSdfp
return code is 8.
Application Programmer Response: Probable user IEB713I FLAGGED KEYWORD IS NOT
error. Since the output data set may have been only COMPATIBLE WITH A PRECEDING
partially completed, run IEHPROGM to scratch the data KEYWORD
set, if necessary. If a REGION parameter was specified,
Explanation: The keyword pinpointed by message
ensure that the specified value is sufficient to complete
IEB727I is not compatible with another keyword already
the necessary processing and resubmit the job.
specified on the same statement. (For example, the
Source: DFSMSdfp keywords PICTURE and FORMAT cannot be used
together.)
IEB711I KEYWORD VALUE NOT FOLLOWED System Action: Syntax checking of the remainder of
BY A BLANK OR COMMA the utility control statements in this set continues, but no
Explanation: The keyword value pinpointed by
message IEB727I is not followed by a blank or a
return code is 8.
comma.
return code is 8. System Programmer Response: If the error recurs
the problem.

Source: DFSMSdfp
IEB716I PICTURE STRING OR FD FIELD
OVERFLOWS OUTPUT RECORD OR
IEB714I REPEAT CARD ERROR OR REQUIRED INPUT FIELD SELECTED OVERRUNS
NUMBER OF CREATE CARDS NOT INPUT WORKAREA
PRESENT
Explanation: During construction of an output record
Explanation: One of the following error conditions by a CREATE statement, a specified picture string or
occurred: FD field extended past the end of the defined record.
v Two or more REPEAT statements refer either to the System Action: Syntax checking of the remainder of
same CREATE statement or to the same group of the utility control statements in this set continues, but no
CREATE statements. additional data is generated. Processing continues
v A CREATE keyword in a REPEAT statement specifies normally with the next DSD statement encountered. The
a number greater than the number of following return code is 8.
CREATE statements.
System Action: Syntax checking of the remainder of error. Since the output data set may have been only
the utility control statements in this set continues, but no partially completed, run IEHPROGM to scratch the data
additional data is generated. Processing continues set. Make sure that the DCB parameters are correct.
normally with the next DSD statement encountered. The Compare the LRECL parameter value with the length of
return code is 8. the defined record, and make sure the value is specified
correctly. Resubmit the job.
error. Since the output data set may have been only System Programmer Response: If the error recurs
partially completed, run IEHPROGM to scratch the data and the program is not in error, look at the messages in
set, if necessary. Correct the error and resubmit the job. the job log for more information. Search problem
the problem.
IEB717I INPUT RECORD SIZE EXCEEDS
Source: DFSMSdfp SPECIFIED OUTPUT RECORD SIZE
Explanation: The record length specified in a DD
IEB715I NAME AND/OR LENGTH OR QUANTITY statement for an output data set is not sufficient to
SPECIFICATION(S) OMITTED FROM FD contain corresponding input records.
AND/OR REPEAT CARD
Explanation: One or more of the field name, length, the utility control statements in this set continues, but no
and quantity specifications is missing from an FD and/or additional data is generated. Processing continues
REPEAT statement. normally with the next DSD statement encountered. The
return code is 8.
the utility control statements in this set continues, but no Application Programmer Response: Probable user
additional data is generated. Processing continues error. Since the output data set may have been only
normally with the next DSD statement encountered. The partially completed, run IEHPROGM to scratch the data
return code is 8. set, if necessary. Correct the error and resubmit the job.
Application Programmer Response: Probable user System Programmer Response: If the error recurs
error. Since the output data set may have been only and the program is not in error, look at the messages in
partially completed, run IEHPROGM to scratch the data the job log for more information. Search problem
set, if necessary. Correct the error and resubmit the job. reporting data bases for a fix for the problem. If no fix
the problem.
Source: DFSMSdfp

IEB718I DSD CONTROL CARD MUST BE FIRST
return code is 8.
CARD OF SET
Explanation: The DSD control statement is either out
of order or missing.
System Action: Syntax checking of the remainder of set, if necessary. Correct the error and resubmit the job.
return code is 8.
Application Programmer Response: Probable user exists, contact the IBM Support Center. Provide the JCL
error. Insert the missing DSD statement, or correct the and all printed output and output data sets related to
sequence of control statements. the problem.
IEB723I PICTURE PARAMETER IS NOT
FOLLOWED BY A BLANK OR COMMA
and all printed output and output data sets related to Explanation: The picture length subparameter or the
the problem. picture value field is not followed by a blank or comma.
Source: DFSMSdfp System Action: Syntax checking of the remainder of
IEB720I BLANK DOES NOT FOLLOW
OPERATION OR CONTROL CARD
return code is 8.
NAME
Explanation: The control statement name or operation
is not followed by a blank.
System Action: Syntax checking of the remainder of set, if necessary. Correct the error and resubmit the job.
return code is 8.
Application Programmer Response: Probable user exists, contact the IBM Support Center. Provide the JCL
error. Since the output data set may have been only and all printed output and output data sets related to
partially completed, run IEHPROGM to scratch the data the problem.
Source: DFSMSdfp
IEB724I UNABLE TO OPEN DATA SET. LOOK
FOR CONFLICTING VALUES OR
MISSING DD CARD
and all printed output and output data sets related to Explanation: An input or output data set referred to by
the problem. a DSD statement could not be opened. Possibly, the DD
statement is missing or the BLKSIZE, LRECL, or
Source: DFSMSdfp
RECFM subparameters is incorrect.
System Action: No syntax checking or data
IEB721I KEYWORD, KEYWORD VALUE OR
generation is performed for this set of utility control
DELIMITER IS MISSING OR EXTENDS
statements. Processing continues normally with the next
INTO COLUMN 72
DSD statement encountered. The return code is 8.
Explanation: A required keyword, keyword value, or
delimiter is missing or is specified in column 72.

reporting data bases for a fix for the problem. If no fix was detected in the preceding control statement.
System Action: The system action and return code
are as indicated in the error message that follows this
the problem.
message.
Source: DFSMSdfp
Application Programmer Response: Respond as
indicated in the error message that follows this
IEB725I A DUPLICATE DSD CARD HAS BEEN message.
FOUND. CHECK FOR MISSING END
Source: DFSMSdfp
CARD.
Explanation: An END statement is either out of order
IEB728I INPUT STREAM FLUSHED FROM THIS
or missing.
POINT. LRECL, BLKSIZE, OR RECFM
System Action: Syntax checking of the remainder of INCORRECT IN INPUT OR OUTPUT
the utility control statements in this set continues, but no DCB
Explanation: An input or output data set could not be
opened. Probably, the LRECL, BLKSIZE, or RECFM
return code is 8.
specification for the data set is incorrect or missing.
System Action: No syntax checking or data
generation is performed for this set of utility control
System Programmer Response: If the error recurs statements. Processing continues normally with the next
and the program is not in error, look at the messages in DSD statement encountered. The return code is 8.
and all printed output and output data sets related to System Programmer Response: If the error recurs
the problem. and the program is not in error, look at the messages in
Source: DFSMSdfp
IEB726I EXEC STATEMENT PARM PARAMETER and all printed output and output data sets related to
IS CODED INCORRECTLY the problem.
Explanation: The PARM parameter of the EXEC Source: DFSMSdfp
statement contains an incorrect character, or does not
contain a 4-digit decimal number.
IEB729I PERMANENT I/O ERROR, jjj, sss, ddd,
System Action: The line count of the message data devtyp, ddname, op, err, xxxx, acc
set is set to a default value of 58. The return code is 0.
Application Programmer Response: Probable user while processing on the device.
error. If the default value assumed is unacceptable,
In the message text, the error analysis information
correct the LINECNT subparameter on the EXEC
provided by the SYNADAF data management macro
statement.
instruction issued by the SYNAD routine was:
jjj Job name.
the job log for more information. Search problem sss
reporting data bases for a fix for the problem. If no fix Step name.
and all printed output and output data sets related to ddd
the problem. Device number of the device.
Source: DFSMSdfp devtyp

Device type.
IEB727I ERROR ddname

Data definition name.
Explanation: This message immediately follows an
error message and pinpoints the location of syntax op Operation attempted.
errors, incompatible keywords, and other control err Error description.
statement coding errors. In most cases, the “E” of
ERROR falls directly below the point at which the error

xxxx sss
Last seek address or block count. Step name.
acc ddd
Access method. Device number of the device.
System Action: The program is ended. The return devtyp
code is 12. Device type.
Application Programmer Response: Correct the ddname
error condition as indicated in the message text. Data definition name.
System Programmer Response: If the error recurs op Operation attempted.
reporting data bases for a fix for the problem. If no fix xxxx
exists, contact the IBM Support Center. Provide the JCL Track address or relative block number.
the problem. acc
Access method.
Source: DFSMSdfp
code is 12.
IEB801I {OM|NM} LRECL AND BLOCKSIZE
ASSUMED 80/80 Application Programmer Response: Correct the
error condition indicated in the message text.
Explanation: Necessary DCB parameters were
omitted from the SYSUT1 (indicated by OM or old System Programmer Response: If the error recurs
master) or SYSUT2 (indicated by NM or new master) and the program is not in error, look at the messages in
DD statement. The program assumes that the SYSUT1 the job log for more information. Search problem
or SYSUT2 data set, as applicable, contains 80-byte reporting data bases for a fix for the problem. If no fix
unblocked records. exists, contact the IBM Support Center. Provide the JCL
System Action: Processing continues. However, if the the problem.
data set does not contain 80-byte unblocked records,
additional messages will be generated during Source: DFSMSdfp
processing, and the job step will be ended. The return
code is 0. IEB803I PERMANENT INPUT ERROR - FIND
Application Programmer Response: If the record MACRO
format specifications assumed are correct, there is no Explanation: A permanent input error was detected by
response required. Otherwise, correct the applicable the FIND macro instruction while attempting to search a
parameters. partitioned data set directory.
System Programmer Response: Use IEHLIST to list System Action: The program is ended. The return
the VTOCs of the volumes on which the old master and code is 12.
new master data sets reside. If the error recurs and the
program is not in error, look at the messages in the job Application Programmer Response: Check the DD
log for more information. Search problem reporting data statement describing the SYSUT1 data set for missing
bases for a fix for the problem. If no fix exists, contact or incorrect parameters.
the IBM Support Center. Provide the JCL and all printed System Programmer Response: If the error recurs
output and output data sets related to the problem. and the program is not in error, look at the messages in
IEB802I I/O ERROR jjj, sss, ddd, devtyp, ddname, and all printed output and output data sets related to
op, err, xxxx, acc the problem.
Explanation: A permanent input/output error occurred Source: DFSMSdfp
In the message text, the error analysis information IEB804I PERMANENT INPUT ERROR - BLDL
provided by the SYNADAF data management macro MACRO
instruction issued in the SYNAD routine was:
Explanation: A permanent input/output error was
jjj Job name. detected by the BLDL macro when attempting to search
a partitioned data set directory.

IEB807I INVALID OPERATION
code is 12.
Explanation: The statement preceding this message
Application Programmer Response: Check the DD
is inconsistent with previously specified parameters.
statement describing the SYSUT1 data set for missing
Possibly:
or incorrect parameters.
v A DELETE statement is encountered during an
System Programmer Response: If the error recurs UPDATE=INPLACE operation.
v A CHANGE statement is encountered, but
PARM=NEW was specified on the EXEC statement.
exists, contact the IBM Support Center. Provide the JCL v Data statements are out of sequence. Old master
and all printed output and output data sets related to records are out of sequence and renumbering was
the problem. not requested.
v A NUMBER statement with a SEQ1 parameter is
Source: DFSMSdfp
encountered following an ADD statement.
v More than 16 alias statements have been found for
IEB805I CONTROL STATEMENT ERROR the member scheduled to be updated.
Explanation: In the utility control statement preceding System Action: If the data set is partitioned, the
this message, a name, keyword, or parameter is program continues processing with the next function
incorrect. statement. If the data set is not partitioned, the program
System Action: If the data set is partitioned, the is ended. The return code is 4.
program continues processing with the next function Application Programmer Response: Probable user
statement. If the data set is not partitioned, the program error. Correct the error and resubmit the job.
is ended. The return code is 4.
Application Programmer Response: Probable user and the program is not in error, look at the messages in
error. Correct the error and resubmit the job. the job log for more information. Search problem
the job log for more information. Search problem and all printed output and output data sets related to
reporting data bases for a fix for the problem. If no fix the problem.
the problem.
IEB808I TERMINATED THIS MEMBER.
Source: DFSMSdfp IEBUPDTE WILL TRY NEXT MEMBER
Explanation: A control statement error, a statement
IEB806I STATEMENT SEQUENCE ERROR sequence error, or an incorrect operation has ended an
Explanation: Either the utility control statements are update operation.
out of sequence, or an unnecessary statement has System Action: Processing continues with the next
been encountered. function statement. The return code is 0.
System Action: If the data set is partitioned, the Application Programmer Response: Correct the
program continues processing with the next function control statement error.
statement. If the data set is not partitioned, the program
is ended. The return code is 4. System Programmer Response: If the error recurs
Application Programmer Response: Probable user the job log for more information. Search problem
error. Correct the error and resubmit the job. reporting data bases for a fix for the problem. If no fix
the problem.
Source: DFSMSdfp

IEB810I DELETE RANGE INVALID IEB813I OUTPUT DIRECTORY FULL
Explanation: In the DELETE statement preceding this Explanation: Insufficient space was allocated for
message, the SEQ1 or SEQ2 value specified does not directory entries in the SYSUT2 data set. Therefore, the
match a sequence number in an existing logical record. member was not placed in the data set.
System Action: Processing continues with the next System Action: The program is ended. The return
function statement. The return code is 4. code is 12.
Application Programmer Response: Probable user Application Programmer Response: Re-create the
error. Correct the error and resubmit the job. SYSUT2 data set, allocating sufficient space for the
additional directory entries. Then resubmit IEBUPDTE to
include the members that were omitted.
and all printed output and output data sets related to reporting data bases for a fix for the problem. If no fix
the problem. exists, contact the IBM Support Center. Provide the JCL
Source: DFSMSdfp
Source: DFSMSdfp
IEB811I NUMBER RANGE INVALID
Explanation: In the NUMBER statement preceding
OPENED
this message, the SEQ1 value does not match a
sequence number in an existing logical record. Explanation: The data set specified on the DD
statement cannot be opened. Possibly, the LRECL or
BLKSIZE for the SYSIN volume is not equal to, or a
function to be performed. The return code is 4.
multiple of, 80.
ddname
Identifies the DD statement.
the problem.
Source: DFSMSdfp
IEB812I DIRECTORY WRITE ERROR reporting data bases for a fix for the problem. If no fix
while writing the directory of the SYSUT2 data set.
Source: DFSMSdfp
code is 12.
IEB815I CANNOT PROCESS MORE THAN ONE
PS DATA SET PER PASS
sufficient space is allocated for the directory on the
SYSUT2 DD statement. Explanation: A control statement specified the
processing of two input sequential data sets in the same
job step.
error. Ensure that there is no disagreement between the
Source: DFSMSdfp JCL and the user control statements. Resubmit the job.

the job log for more information. Search problem System Action: The program is ended normally.
Source: DFSMSdfp
IEB819I END OF JOB IEBUPDTE
Source: DFSMSdfp
Explanation: IEBUPDTE has completed processing.
IEB816I {MEMBER NAME mem System Action: The program is ended normally.
FOUND|MEMBER NAME mem FOUND
IN NM DIRECTORY. TTR IS NOW Source: DFSMSdfp
ALTERED}
Explanation: For the first format of the message, the IEB820I CANNOT PROCESS MORE THAN ONE
member name specified on an ADD statement already FUNCTION STATEMENT WHEN
exists. UPDATE=INPLACE IS SPECIFIED
For the second format of the message, the member Explanation: If a function statement specifies
name exists in the new master (NM) directory. UPDATE=INPLACE, it must be the only function
statement in the job step.
mem The member name. code is 12.
System Action: For the first format of the message, Application Programmer Response: Probable user
the program is ended. The return code is 12. error. Correct the error and resubmit the job.
For the second format of the message, an entry (TTR) System Programmer Response: If the error recurs
is altered and processing continues. The return code is and the program is not in error, look at the messages in
0. the job log for more information. Search problem
Application Programmer Response: For the first
format of the message, change the member name to be
added. For the second format of the message, no action
is necessary. Source: DFSMSdfp
and the program is not in error, look at the messages in IEB821I INVALID EXIT NAME. JOB ENDED
reporting data bases for a fix for the problem. If no fix Explanation: The name of a user exit routine specified
exists, contact the IBM Support Center. Provide the JCL on a function statement is incorrect.
and the program listing for the job. System Action: The program is ended. The return
IEB817I MEMBER NAME mem NOT FOUND IN error. Correct the error and resubmit the job.
NM DIRECTORY. STOWED WITH TTR System Programmer Response: If the error recurs
Explanation: The member name does not exist in the and the program is not in error, look at the messages in
directory of the new master (NM) data set. the job log for more information. Search problem
and the program listing for the job. Have the exit routine
listings and linkage editor output available.
System Action: An entry (TTR) is made for the
Source: DFSMSdfp
member in the directory. Processing continues. The
return code is 0.
IEB822I EXIT RETURN CODE ENDED JOB
Source: DFSMSdfp
Explanation: The return code returned by the user
was 16.
IEB818I HIGHEST CONDITION CODE WAS ccc
Explanation: The condition code indicated was the
code is 16.
highest code generated in the job step.
Application Programmer Response: If a return code
of 16 was not expected, check your exit routine, and
ccc The condition code. resubmit the job.

System Programmer Response: If the error recurs System Action: Processing continues. The return
and the program is not in error, look at the messages in code is 0.
Source: DFSMSdfp
and the program listing for the job. Have the exit routine IEB827I INVALID INPUT PARAMETER
listings available.
Explanation: Either the EXEC statement contains an
Source: DFSMSdfp incorrect PARM parameter, or an incorrect parameter
was passed to IEBUPDTE.
IEB823I {SYSUT1|SYSIN} HAS NO RECORDS System Action: The program is ended. The return
code is 12.
Explanation: The SYSUT1 or SYSIN data set, as
indicated in the message text, contains no records. Application Programmer Response: Probable user
System Action: For the SYSUT1 data set, processing
continues with the next member, if any. The return code System Programmer Response: If the error recurs
is 4. and the program is not in error, look at the messages in
For the SYSIN data set, the program is ended. The
return code is 12.
The system issues messages about the job to the job and the program listing for the job.
log.
Source: DFSMSdfp
Application Programmer Response: Insert data
statements for the SYSIN data set, or ensure that the
IEB828I PAGE NUMBER PARAMETER INVALID
proper SYSUT1 data set is specified.
Explanation: An incorrect starting page number for
If the problem recurs and if the program is not in error,
the message data set was passed to IEBUPDTE.
problem. If no fix exists, contact the IBM Support System Action: A page number of 1 is assigned to
Center. Provide the JCL for the job and the program the first page of the printout. The return code is 4.
listing for the job.
Source: DFSMSdfp error. If the default of 1 is not acceptable, correct the
starting page number.
IEB825I ALIAS IGNORED - SEQUENTIAL DATA System Programmer Response: If the error recurs
SET and the program is not in error, look at the messages in
Explanation: An ALIAS statement specified an alias
name for an output sequential data set.
System Action: The statement is ignored. The return and the program listing for the job.
code is 4.
Source: DFSMSdfp
error. Delete the ALIAS statement.
IEB829I DDNAME PARAMETER IS INVALID
Explanation: An incorrect DDNAME parameter was
passed to IEBUPDTE.
reporting data bases for a fix for the problem. If no fix System Action: The program is ended. The return
exists, contact the IBM Support Center. Provide the JCL code is 12.
IEB826I MEMBER NAME FOUND IN OM and the program is not in error, look at the messages in
DIRECTORY AS AN ALIAS - CHANGED the job log for more information. Search problem
TO TRUE NAME IN NM DIRECTORY reporting data bases for a fix for the problem. If no fix
Explanation: The member name is an alias name in
the old master (OM) directory, and is entered as a
member name in the new master (NM) directory. Source: DFSMSdfp

routine The routine specified.
IEB830I OLD AND NEW MASTER LRECL
UNEQUAL System Action: Processing continues. The return
code is 0.
Explanation: The logical record lengths of the old and
new master data sets are unequal. Source: DFSMSdfp
code is 12. IEB833I xx ENTRANCES TO routine
Application Programmer Response: Probable user Explanation: The number of entrances to user routine
error. Correct the LRECL subparameter of the DCB is indicated.
parameter on the SYSUT2 DD statement.
and the program is not in error, look at the messages in xx The number of entrances to the user routine.
the job log for more information. Search problem routine The user routine.
exists, contact the IBM Support Center. Provide the JCL System Action: Processing continues. The return
and the program listing for the job. code is 0.
IEB831I OLD AND NEW MASTER DSORGS IEB834I LAST RETURN CODE FROM routine
INCOMPATIBLE WAS return-code
Explanation: The data set organizations implied or Explanation: The return code indicated was the last
specified on the SYSUT1 and/or SYSUT2 DD return code issued by the user routine.
statements are either: In the message text:
v Inconsistent with one another.
v Inconsistent with the data set organizations implied or
specified on the utility control statements. routine The user routine.
System Action: The program is ended. The return System Action: Processing continues. The return
code is 12. code is 0.
Application Programmer Response: Probable user Source: DFSMSdfp

error. In the first case, ensure that the space allocation
specified on the SYSUT1 and/or SYSUT2 DD IEB835I {TOTALING|USER LABELS}
statements is consistent with the data set organization. SUPPORTED ONLY ON PS DATA SETS
Also, ensure that the DSORG subparameter, if included,
is correct. Explanation: The user requested totaling exits or user
label processing, as indicated in the message text, for a
In the second case, ensure that the keywords specified data set whose organization is not physical sequential.
on the utility control statements are consistent with the These functions are supported only for physical
data set organizations specified or implied on the sequential data sets.
SYSUT1 and/or SYSUT2 DD statements.
System Programmer Response: If the error recurs code is 8.
reporting data bases for a fix for the problem. If no fix error. Correct the error and resubmit the job.
IEB832I routine IS PROCESSING USER and the program listing for the job.
{INPUT|HEADER|OUTPUT|TRAILER}
LABELS Source: DFSMSdfp
Explanation: The user routine is currently processing

input or output, header or trailer labels, as indicated in
the message text.

routine The user totaling routine.
IEB836I TRAILER LABEL PROCESSING NOT
SUPPORTED FOR UPDATE=INPLACE System Action: If the return code passed to
IEBUPDTE was 0, totaling exits are discontinued, but
Explanation: The user specified user trailer label exits
with an UPDATE=INPLACE operation. User trailer label
exits are not supported for UPDATE=INPLACE If the return code was 8, the program is ended. The
operations. return code is 12.
System Action: The program is ended. The return If the return code was 16, the program is ended. The
code is 8. return code is 16.
Application Programmer Response: Probable user Application Programmer Response: If ending the
error. Correct the error and resubmit the job. totaling exit routine was not expected, check the exit
routine, and resubmit the job.
and the program listing for the job. exists, contact the IBM Support Center. Provide the JCL
Source: DFSMSdfp
listing available.
Source: DFSMSdfp
IEB837I I/O ERROR WHILE PROCESSING USER
LABEL
IEB841I INVALID RETURN CODE FROM routine,
TOTALING EXITS DISCONTINUED
occurred during user label processing. The results of
the label processing are unpredictable. Explanation: The return code passed to IEBUPDTE
by the user totaling routine during a totaling exit was not
valid. That is, the return code was not 0, 4, 8, or 16.
code is 12.
Application Programmer Response: Ensure that no
DCB parameters for the data set are incorrect or routine The user totaling routine.
missing.
System Action: Totaling exits are discontinued, but
System Programmer Response: If the error recurs processing continues. The return code is 0.
reporting data bases for a fix for the problem. If no fix error. Check the user routine to make sure that a valid
exists, contact the IBM Support Center. Provide the JCL return code was passed to the utility program. Resubmit
and the program listing for the job. the job.

IEB839I routine IS TAKING TOTALING EXITS reporting data bases for a fix for the problem. If no fix
Explanation: The user routine is taking totaling exits
prior to writing each record.
listings available.
Source: DFSMSdfp
routine The user routine.
System Action: Processing continues. The return IEB842I TOTALING EXITS NOT SUPPORTED
code is 0. FOR UPDATE=INPLACE
Source: DFSMSdfp Explanation: The user specified totaling exits with an
UPDATE=INPLACE operation. Totaling exits are not
supported for UPDATE=INPLACE operations.
IEB840I routine REQUESTED TERMINATION OF
TOTALING EXITS System Action: The program is ended. The return
code is 12.
Explanation: A return code other than 4 was passed
to IEBUPDTE by the user totaling routine. Application Programmer Response: Probable user

System Programmer Response: If the error recurs and the program listing for the job. Have the associated
and the program is not in error, look at the messages in input data set available.
Source: DFSMSdfp
and the program listing for the job. IEB846I ALIAS IGNORED FOR
UPDATE=INPLACE
Source: DFSMSdfp
Explanation: ALIAS statements for partitioned data
set members cannot be processed using the
IEB843I INVALID CORE SIZE
UPDATE=INPLACE operation.
Explanation: The virtual storage specified in the
System Action: All ALIAS statements are ignored.
TOTAL keyword either is a non-numeric character, is
Processing continues. The return code is 0.
less than 2 bytes, or is greater than 32K bytes.
code is 12.
the job log for more information. Search problem and the program listing for the job.
Source: DFSMSdfp
IEB1010I function FUNCTION REQUESTED FOR
Source: DFSMSdfp
A PDSE. Action
Explanation: An ALTERMOD or COMPRESS
IEB844I NO USER {HEADER|TRAILER} LABELS
operation is requested for a PDSE, or a COPYMOD
EXISTS ON INPUT DATA SET
operation is requested for a PDSE.
Explanation: The user specified SUL on the DD
Message inserts and meanings:
statement for the input data set, but there are no header
or trailer labels, as indicated in the message text, on the function
data set. is one of:
COPYMOD
ALTERMOD
code is 0.
COMPRESS
Source: DFSMSdfp
Action is one of:
IT IS IGNORED.
IEB845I NO USER {HEADER|TRAILER} LABELS REQUEST TREATED AS COPY.
CREATED ON OUTPUT DATA SET
The severity is 0.
Explanation: The user specified SUL on the SYSUT2
DD statement, but no header or trailer labels, as System Action: An ALTERMOD or COMPRESS
indicated in the message text, were copied from the operation is ignored. A COPYMOD operation is treated
SYSUT1 data set, and no labels were generated by a as a COPY request.
LABEL statement.
User Response: Remove the compress or
System Action: Processing continues. The return ALTERMOD operation to eliminate this message, or
code is 0. change COPYMOD to COPY since the PDSE can not
contain a load module.
Application Programmer Response: If user labels
are desired on the output data set, make sure that the Source: DFSMSdfp
SYSUT1 data set contains user labels, or supply user
labels with the LABEL statement. Resubmit the job.
IEB1010S function FUNCTION REQUESTED FOR
System Programmer Response: If the error recurs A PDSE. NO PDSE SUPPORT IN THIS
and the program is not in error, look at the messages in RELEASE.
reporting data bases for a fix for the problem. If no fix Explanation: A PDSE has been encountered on a
exists, contact the IBM Support Center. Provide the JCL system before DFP V3 R2. This is probably because
the DASD containing the PDSE is shared with a system

running a DFP or DFSMS release that does support size amount of storage available in the work area
PDSEs. when the PDSE operation started.
The severity is 8.
function
System Action: Processing is incomplete.
is one of:
COPY User Response: 1. Refer to preceding IGW messages
COPYMOD to learn what processing was completed. 2. Increase
ALTERMOD the size of the work area, or decrease the number of
COMPRESS members involved in the operation, or specify LIST=NO
LOAD to reduce the message traffic.
UNLOAD
The user response for message IEB1057I discusses
The severity is 12.
increasing the WORK area size.
System Action: Any operation involving a PDSE on a
Source: DFSMSdfp
system without PDSE support is ended.
User Response: Re-run the job on the system with
IEB1013I COPYING FROM dtype INDD=ddname
PDSE support available.
VOL=volume DSN=dsname
Source: DFSMSdfp
Explanation: This message documents the copy
source data set.
IEB1011E AVAILABLE STORAGE (avail) IS TOO
SMALL. ADD nnnnn MORE BYTES TO
WORK SIZE. dtype type of data set:
Explanation: A list of members to be copied to or from PDSE a library (DSNTYP=LIBRARY)
a PDSE was being built when all available virtual
storage in the work area was exhausted. PDS a partitioned (DSORG=PO)
Message inserts and meanings: PDSU a sequential data set containing a

PDS or PDSE in unloaded format.
avail amount of storage available in the work area
when the PDSE operation started. ddname
input DD name from the COPY statement.
nnnnn number of additional bytes required.
volume volume containing the data set.
The severity is 8. dsname
data set name.
System Action: The requested COPY operation is not
performed.
The severity is 0.
User Response: Increase the work area size, or
reduce the number of members involved in the System Action: Processing continues.
operation. Source: DFSMSdfp
The user response for message IEB1057I discusses IEB1014I TO dtype OUTDD=ddname VOL=volume
increasing the WORK area size. DSN=dsname
Source: DFSMSdfp Explanation: This message documents the destination
data set.
IEB1012E COPY OPERATION NEEDS nnnnn Message inserts and meanings:
BYTES MORE STORAGE. OUTPUT
AREA IS size BYTES. dtype type of data set:
Explanation: The amount of storage available to PDSE a library (DSNTYP=LIBRARY)

communicate with the PDSE routines is too small. PDS a partitioned (DSORG=PO)
This area is used to return member lists, and PDSU a sequential data set containing a
messages. PDS or PDSE in unloaded format.
Message inserts and meanings: ddname
nnnnn amount of the virtual storage shortage. output ddname from the COPY statement.

volume volume containing the data set. v return-code > 8 is severity 8, message IEB1017E.
dsname System Action: The next operation is sought.
data set name.
User Response: This probably represents an unusual
condition or problem. Refer to accompanying messages,
The severity is 0.
particularly those with IGW and IEB prefixes, for specific
System Action: Processing continues. information and additional guidance.
Source: DFSMSdfp System Programmer Response: Research

accompanying messages in SYSPRINT and in the job
log for more specific information.
IEB1016I RETURN CODE IS return-code
Explanation: This message records information about problem. If no fix exists, contact the IBM Support
the results of a copy operation involving a PDSE. Center.
The value of return-code is not a IEBCOPY step Please furnish the information in this message when
completion code; it is a return code from an internal requesting service along with the JCL, job log, system
routine. The IEBCOPY completion code is affected by messages, and all SYSPRINT output.
this return-code as documented in message IEB1017.
Please preserve the input and output data sets related
The severity is 0. to the problem in case it should be necessary to
System Action: Message IEB1017 follows. reproduce the problem.
User Response: This may represent either a normal Source: DFSMSdfp

condition or a problem. Refer to accompanying
messages for additional guidance. IEB1018I COMPRESSING PDS OUTDD=ddname
Source: DFSMSdfp VOL=volume DSN=dsname
Explanation: This message documents the data set
IEB1017I -- DIAGNOSTIC CODE IS X'diagcode' being compressed.
IEB1017W -- DIAGNOSTIC CODE IS X'diagcode' ddname
output DD name from the COPY statement.
IEB1017E -- DIAGNOSTIC CODE IS X'diagcode' volume volume containing the data set.
Explanation: This message accompanies messages dsname
IEB1016I or IEB1137I. Report this diagnostic code to data set name.
the IBM support center when requesting service.
The severity is 0.
Note: The historical step completion codes from
IEBCOPY cause normal attention conditions to System Action: Processing Continues.
be reported as completion code 0. Generally
Source: DFSMSdfp
speaking, completion code 4 means that a copy
operation has failed, and completion code 8
means that execution can not continue under IEB1019I SKIPPING COMPRESS OF PDSE
any circumstances. OUTDD=ddname VOL=volume
DSN=dsname
In order to reconcile the existing completion codes in
Explanation: A request to compress a PDSE was
IEBCOPY with the modern standards, the return codes
suppressed, as a PDSE never needs compressing.
from new function related to PDSEs are reduced by 4 to
create the IEBCOPY completion code. Message inserts and meanings:
ddname
DD name.
diagcode
an internal DFP diagnostic code.
dsname
The severity is based on the return code in message data set name.
IEB1016I:
v return-code < 8 is severity 0, message IEB1017I. The severity is 0.
v return-code = 8 is severity 4, message IEB1017W. System Action: Processing continues.

User Response: Consider removing the compress ddname
request from the job. DD name identifying the data set.
Source: DFSMSdfp volume volume containing the data set or blank for
VIO.
IEB1020I UPDATING PDS OUTDD=ddname dsname
VOL=volume DSN=dsname name of the data set.
Explanation: This documents the data set being
The severity is 0.
processed by an “in-place” operation such as
ALTERMOD. System Action: An indicative dump may be printed
next on SYSPRINT. Message IEB1023I will follow the
dump (if any).
ddname
Source: DFSMSdfp
output DD name for the data set.
IEB1023I activity MEMBER=member TTR= X'ttr'
dsname MBBCCHHR=mbbcchhr TAPE
data set name. BLOCK=bbbbb
Explanation: This messages follows IEB1022E to
The severity is 0.
document the current activity at the time of the I/O error.
This message identifies the location of the I/O error first
Source: DFSMSdfp reported in message IEB1021E. These fields may be
incomplete or missing depending on the details of
processing at the time of the error. When a field
IEB1021E synad_text LEN=length SENSE= contains zero, it is not valid. If both the TTR and
iobsens0-iobecbcc MBBCCHHR are not zero then both should identify the
Explanation: This message, with following message same record in the data set.
IEB1023I, contains text generated by the SYNADAF TTR= and MBBCCHHR= are valid only if the data set
function during I/O error processing. resides on direct access storage. TAPE BLOCK= is
Message inserts and meanings: valid only if the data set resides on tape.
synad_text text generated by the SYNADAF Message inserts and meanings:

macro. activity is one of:
length amount of data read or 0. COPYMOD READ
COPYMOD WRITE
iobsens0 first 2 sense bytes. READING UNLOADED PDSE
iobecbcc ECB post code. WRITING UNLOADED PDSE
GET FROM CONTROL STMT FILE
The severity is 8. PUT TO MESSAGE FILE
DURING READ
System Action: Message IEB1022I and IEB1023I DURING WRITE
follow. DURING ERASE
DURING READBACK CHECK
Source: DFSMSdfp
DURING LOAD
DURING UNLOAD
IEB1022I I/O ERROR ON dtype DDN=ddname UNEXPECTED END OF FILE
VOL= volume DSN=dsname READING OUTPUT DIRECTORY
PROCESSING HEADER RECORDS
Explanation: This messages follows IEB1021E to
SCANNING DIRECTORY
document the data set involved in the I/O error.
INPUT DIRECTORY MERGE
Message inserts and meanings: OUTPUT DIRECTORY MERGE
LOCATING MEMBER
dtype type of data set:
member
PDSE a library (DSNTYP=LIBRARY) name of the PDS or PDSE member.
PDS a partitioned (DSORG=PO) ttr 3-byte hexadecimal relative disk address.
PDSU a sequential data set containing a mbbcchhr
PDS or PDSE in unloaded format. DASD address of record.

bbbbb block number used for tape positioning. System Action: Processing continues. If the page
number is missing in the supplied parameter, the
The severity is 0. beginning page number will be 1. If the page number in
the supplied parameter is too long, the beginning page
System Action: Error processing continues. number will be some left portion of that number. If the
User Response: Refer to message IEB1021. supplied parameter is not an EBCDIC number, the
beginning page number will be an unpredictable
System Programmer Response: Refer to message numerical value.
IEB1021.
User Response: Correct the program invoking
Source: DFSMSdfp IEBCOPY to properly construct and pass the third
parameter. Refer to the OS/390 DFSMSdfp Utilities
IEB1024E SYNTAX ERROR IN PARM FIELD Appendix A for information about dynamic invocation of
OPTIONS IEBCOPY and parameters.
Explanation: There is an error in one of the following: Source: DFSMSdfp

v The parameter passed via the PARM= field on the
EXEC JCL statement IEB1027E IO LIST PARAMETER IS NOT
v The program parameter field in the TSO CALL SUPPORTED AND IS IGNORED.
command
v The first parameter in the parameter list passed by a Explanation: A program invoked IEBCOPY, supplying
program dynamically invoking IEBCOPY. a fourth parameter which is not used by IEBCOPY.
Some IBM Utility programs support user IO routines
The severity is 8. which are passed in a list as the fourth parameter.
Since IEBCOPY does not support user IO routines, it
System Action: Processing continues, ignoring does not expect more than three passed parameters.
options which could not be understood because of the
syntax error. The severity is 8.
User Response: Correct the options. System Action: Processing continues.
Source: DFSMSdfp User Response: To prevent this message from

appearing, change the program invoking IEBCOPY so
that it will not pass more than three parameters. Refer
IEB1025I DD NAME LIST PARAMETER IS IN to the OS/390 DFSMSdfp Utilities Appendix A for
ERROR AND MIGHT BE IGNORED. information about dynamic invocation of IEBCOPY and
Explanation: A program invoked IEBCOPY, supplying parameters.
a list of DD names to be substituted for those normally Source: DFSMSdfp
used by IEBCOPY. However, some or all of the supplied
names could not be recognized.
IEB1028I OPERATING IN KEY 0 SUPERVISOR
The severity is 8. STATE
System Action: Processing continues. The names
that can be correctly identified as substitutes are used; IEB1028T OPERATING IN KEY 0 SUPERVISOR
the others are ignored. STATE
User Response: Correct the program invoking Explanation: IEBCOPY has detected that it was called
IEBCOPY to properly construct and pass the second in supervisor state and protection key zero.
parameter. Refer to the OS/390 DFSMSdfp Utilities
Appendix A for information about dynamic invocation of The interface to some services changes when the
IEBCOPY and parameters. invoker is in supervisor state/key 0 and IEBCOPY is not
coded to use these different interfaces.
Source: DFSMSdfp
IEBCOPY must be invoked in problem state and
non-zero protect key.
IEB1026I PAGE NUMBER PARAMETER IS IN
ERROR AND MIGHT BE IGNORED The severity is 0.
Explanation: A program invoked IEBCOPY, supplying System Action: IEBCOPY ends.

a beginning page number for the IEBCOPY messages Application Programmer Response: Invoke
and control cards listing. The page number is either IEBCOPY as an application program.
missing, too long, or contains characters which are not
EBCDIC numbers. System Programmer Response: Check the program
properties table for programs such as SMP/E that
The severity is 8. invoke IEBCOPY under the covers.

Source: DFSMSdfp
IEB1031E VOLUME volume DD NAME ddname
DOES NOT CONTAIN DATA SET
IEB1029I INVOKED AS A TSO COMMAND dsname
PROCESSOR
Explanation: The data set is not present on the
Explanation: IEBCOPY has been entered from TSO indicated volume. Note that the volume information may
as a command processor. This message is issued come from a catalog or from JCL, and that for SMS
because IEBCOPY was not written to be a TSO data sets, volume information in the JCL may be
command processor but may function when so invoked ignored.
while not providing all the services of a command
processor (e.g. prompting for missing/incorrect
parameters, providing HELP information). volume volume serial number.
The severity is 0. ddname
DD name.
dsname
User Response: Use the TSO CALL command to
data set name.
invoke IEBCOPY. Do not enter IEBCOPY as a TSO
command or CLIST statement.
The severity is 4.
Source: DFSMSdfp
System Action: For an output data set, the COPY
group is ended. For an input data set, processing
IEB1030I DD NAME ddname REFERS TO dtype continues with the next data set in the INDD group.
DATA SET ON VOLUME volume NAMED
User Response: Correct the catalog, add VOL=SER=
dsname
to the DD statement, or create the data set on the
Explanation: This message accompanies message volume.
IEB120I which occurs when a data set can not be
System Programmer Response: The IDCAMS utility
opened. This message may appear multiple times for
may be used to display the volume on which a
each DD name involved in the operation.
cataloged data set is supposed to reside. The IEHLIST
This message is to document data set names and utility may be used to display the names of data sets
volumes when the copy operation fails before messages which reside on a specific volume.
IEB1013I etc. are issued.
Message inserts and meanings: message data set to verify which volume contains a
SMS managed data set.
ddname
DD name identifying the data set. Source: DFSMSdfp
dtype type of data set:
IEB1032E RECORD FORMAT OMITTED FOR DD
PDSE a library (DSNTYP=LIBRARY)
NAME ddname
PDS a partitioned (DSORG=PO)
Explanation: No information about the RECFM for the
PDSU a sequential data set containing a data set identified by the ddname DD statement can be
PDS or PDSE in unloaded format. found.
volume volume containing the data set or blank for Message inserts and meanings:
VIO.
ddname
dsname name of the DD statement.
name of the data set.
The severity is 4.
The severity is 0.
System Action: Processing continues. control statement is sought.
User Response: Correct the error indicated by User Response: Verify that the input data set contains
previous message IEB120I. data (i.e. has been opened for output previously and
successfully closed). The IEHLIST utility may be used to
Source: DFSMSdfp display the data set characteristics from the data set
label.
Source: DFSMSdfp

(Variable length records can be copied from an input
IEB1033E BLOCK SIZE (blksize) INCONSISTENT
data set with equal or shorter length records than the
WITH RECORD LENGTH (reclen) FOR
output data set.)
RECFM=recfm
Explanation: An incorrect combination of block size
and logical records length has been detected. in_ddname
input data set DD statement name.
in_length
blksize physical record size (JCL DD statement
logical record size of the input data set.
BLKSIZE parameter).
out_ddname
reclen logical record size (JCL DD statement LRECL
output data set DD statement name.
parameter).
out_length
recfm record format, as used with the JCL DD
logical record size of the output data set.
statement RECFM parameter.
The severity is 4.
A summary of the rules follows, based on RECFM:
System Action: For an output data set, the COPY
F LRECL must equal BLKSIZE.
group is ended. For an input data set, processing
FB LRECL multiplied by an integer must equal continues with the next data set in the INDD group.
BLKSIZE.
User Response: Correct or supply DCB parameters.
FBS LRECL multiplied by an integer must equal
BLKSIZE.
utility to print the data set label and compare the DCB
V BLKSIZE must exceed LRECL by a minimum parameter fields with the JCL. If the data set is an
of 4. output data set, also examine the DCB parameters from
the current input data set.
VB BLKSIZE must exceed LRECL by a minimum
of 4. Refer to OS/390 DFSMS: Using Data Sets for a
discussion of how all the sources are merged to
VS LRECL may exceed BLKSIZE.
determine the DCB parameters used.
VBS LRECL may exceed BLKSIZE.
Source: DFSMSdfp
When track overflow is not used (RECFM does not
contain a “T”) then the BLKSIZE must not exceed the IEB1035I job_name procstep step_name local_time
track size of a DASD device. PARM=‘parameters’ eye_catcher
Explanation: This message documents the job and
The severity is 4. step producing the IEBCOPY printed report, the local
System Action: The operation is ended and the next time IEBCOPY processed, and the parameters passed
control statement is sought. to IEBCOPY from the JCL EXEC statement PARM field.
Also included is the current maintenance level of the
User Response: Correct or supply DCB parameters. program.
System Programmer Response: Use the IEHLIST Message inserts and meanings:
utility to print the data set label and compare the DCB
parameter fields with the JCL. If the data set is an job_name
output data set, also examine the DCB parameters from JCL Job Name or Time Sharing Option (TSO)
the current input data set. User-ID.
See OS/390 DFSMS: Using Data Sets for a discussion procstep

of how all the sources are merged to determine the if present, the JCL procedure name.
effective DCB parameters. step_name
Source: DFSMSdfp JCL EXEC Step Name.
local_time
IEB1034E RECORD LENGTHS UNEQUAL local (as opposed to universal or GMT) date
BETWEEN INDD in_ddname (in_length) and time.
AND OUTDD out_ddname (out_length) parameters
Explanation: IEBCOPY can not pad or truncate logical parameters supplied when IEBCOPY was
records when reblocking. When fixed length logical invoked.
records are copied they must be the same size.

eye_catcher
IEB1038I ORIGINAL dtype (BEFORE UNLOAD)
latest APAR or PTF applied to IEBCOPY.
WAS RECFM= urecfm BLKSIZE=ublksize
LRECL= ulrecl KEYLEN=ukeylen
The severity is 0. OPTCD= uoptcd UCBTYPE=udevtype
Source: DFSMSdfp INDC= indc
Explanation: The unload data set contains header
IEB1036E TRACK OVERFLOW NOT SUPPORTED records that record the characteristics of the source
FOR DD NAME ddname PDS or PDSE which was unloaded to create the data
set being processed as input. This message informs
Explanation: The DASD device associated with DD you what they are.
name ddname does not support the Track Overflow
feature, or the data set associated with DD name Message inserts and meanings:
ddname is not a PDS. dtype type of data set:
Message inserts and meanings: PDSE a library (DSNTYP=LIBRARY)
ddname PDS a partitioned (DSORG=PO)
DD name identifying the data set.
PDSU a sequential data set containing a
The severity is 4. PDS or PDSE in unloaded format.
System Action: The operation is not preformed and urecfm record format.
the next control statement is sought. ublksize
User Response: Remove the RECFM=T from your block size.
JCL to stop requesting the track overflow feature. ulrecl logical record length.
Source: DFSMSdfp ukeylen
key length.
IEB1037I BLOCK SIZE IN THE DATA SET LABEL uoptcd option codes.
OF ddname INCREASED TO newsize
FROM oldsize udevtype
device type from UCB.
Explanation: A COPYMOD operation has been
requested to reblock a load module. The MAXBLK indc indicator byte.
parameter supplied on the COPYMOD statement (or the
default when MAXBLK is not supplied) limits the largest The severity is 0.
physical record size that COPYMOD will write. This
number is greater than the current block size in the
output data set label. User Response: Refer to this information if you need
to resolve DCB parameter conflicts with the output data
set. Appendix B of the OS/390 DFSMSdfp Utilities book
ddname has details about the header records content.
output data set DD statement name.
Source: DFSMSdfp
newsize
new block size placed in the data set label.
IEB1039W PDSU HAS DIFFERENT BLOCK SIZE
oldsize old block size before the COPYMOD operation. NOW (current) THAN WHEN IT WAS
CREATED (original). AN I/O MAY
The severity is 0. OCCUR WHILE READING IT.
System Action: IEBCOPY updates the data set label Explanation: One of the following occurred while
to contain a correct block size. IEBCOPY was reading an unload data set:
User Response: If the new block size is not v The data set produced from an unload operation has
acceptable, then provide a MAXBLK parameter on the been reblocked. There is a documented restriction
COPYMOD statement. that the data set produced from an unload operation
must not be changed. IEBCOPY may encounter an
Source: DFSMSdfp I/O error reading it. IEBCOPY records the block size
inside the unload data set so it can be compared with
the block size in the unload data set label.
v If the unload data set resides on tape and is
processed with LABEL=(,NL) or LABEL=(,BLP) and

the DCB parameters are omitted from the JCL then
IEB1045D diagnostic_text
IEBCOPY will see the BLKSIZE as zero and report it
as such in this message: IEBCOPY may still Explanation: This message contains diagnostic
encounter an I/O error while processing the tape in information for you to supply to IBM when requesting
this case. service.
Note that the block sizes refer to the unload data set
itself and not to the PDS or PDSE from which it was
created. Explanation: This message contains diagnostic
information for you to supply to IBM when requesting
Message inserts and meanings: service.
current current block size of the unload data set.

original block size IEBCOPY used to create the unload
data set. Explanation: This message contains diagnostic
The severity is 0. service.

User Response:
Explanation: This message contains diagnostic
v Do not change a data set produced from an unload
operation.
service.
v Always provide correct DCB parameters for an
unload data set using JCL or the TSO ALLOCATE or
TSO ATTRIB command operands when the data set IEB1049D diagnostic_text
label is omitted, ignored, or incorrect. Explanation: This message contains diagnostic
Source: DFSMSdfp information for you to supply to IBM when requesting
service.
IEB1051I ut3_blocks in_ddname DIRECTORY
Explanation: This message contains diagnostic ENTRIES SPILLED TO spill_ddname --
information for you to supply to IBM when requesting nnnnn BYTES MORE WORK MAY
service. IMPROVE PERFORMANCE
Explanation: Not enough virtual storage was available
IEB1041D diagnostic_text for IEBCOPY to retain in storage the directory entries
Explanation: This message contains diagnostic for all members being copied. IEBCOPY wrote them to
information for you to supply to IBM when requesting SYSUT3 and read them back one by one as individual
service. processing required the individual entries.
Performance may improve if you can give IEBCOPY
IEB1042D diagnostic_text enough virtual storage to hold all directory entries. Then
you will not need to supply a spill data set.
information for you to supply to IBM when requesting Message inserts and meanings:
service. ut3_blocks number of records written to the spill
data set.
IEB1043D diagnostic_text in_ddname input data set DD name.
Explanation: This message contains diagnostic spill_ddname spill data set DD name. (normally
information for you to supply to IBM when requesting SYSUT3).
service.
nnnnn number of additional bytes needed to
hold all directory entries in storage.
Explanation: This message contains diagnostic The severity is 0.
information for you to supply to IBM when requesting System Action: Processing continues.
service.
User Response: Make more virtual storage available
to IEBCOPY.

The user response for message IEB1057I discusses only message to inform you about what IEBCOPY was
The user response for message IEB1057I discusses doing at the time of failure.
The OS/390 DFSMSdfp Utilities book contains
in_ddname
information about calculating the amounts of virtual
input data set DD name.
storage required to hold directories, and choosing
between a large region or spill files. spill_ddname
spill data set DD name. (normally SYSUT3).
Source: DFSMSdfp
The severity is 0.
IEB1052I ut4_blocks out_ddname DIRECTORY
BLOCKS SPILLED TO spill_ddname -- System Action: IEBCOPY proceeds to open the spill
nnnnn BYTES MORE WORK MAY data set.
IMPROVE PERFORMANCE User Response: Look for message IEB1051I which
Explanation: Not enough virtual storage was available follows later after successful completion of the current
to retain the whole merged output directory in memory. operation.
The merged output directory was written to SYSUT4. If message IEB120I or other data set related messages
Performance may improve if you can give IEBCOPY follow this message then look for problems related to
enough virtual storage to hold all directory entries. Then the spill data set.
you will not need to supply a spill data set. Source: DFSMSdfp
ut4_blocks IEB1054I out_ddname DIRECTORY BLOCKS
number of records written to the spill data set. SPILLING TO spill_ddname
out_ddname Explanation: The amount of unused virtual storage in

output data set DD name. the work area has just been exhausted. IEBCOPY will
try to use a spill data set to hold what can not be
spill_ddname retained in the work area.
spill data set DD name. (normally SYSUT4).
Should the spill data set not be present or be too small
nnnnn number of additional bytes needed to keep the or another problem arise then this message may be the
output directory in storage. only message to inform you about what IEBCOPY was
doing at the time of failure.
The severity is 0.
out_ddname
User Response: Make more virtual storage available output data set DD name.
to IEBCOPY.
spill_ddname
The user response for message IEB1057I discusses spill data set DD name. (normally SYSUT4).
increasing the WORK area size. The severity is 0.
The OS/390 DFSMSdfp Utilities book contains System Action: IEBCOPY proceeds to open the spill
information about calculating the amounts of virtual data set.
storage required to hold directories, and choosing
between a large region or spill files. User Response: Look for message IEB1052I which
follows later after successful completion of the current
Source: DFSMSdfp operation.
If message IEB120I or other data set related messages
IEB1053I in_ddname DIRECTORY ENTRIES follow this message then look for problems related to
SPILLING TO spill_ddname the spill data set.
Explanation: The amount of unused virtual storage in Source: DFSMSdfp
the work area has just been exhausted. IEBCOPY will
try to use a spill data set to hold what can not be
retained in the work area.
Should the spill data set not be present or be too small
or another problem arise then this message may be the

IEB1055I THE REMAINING AMOUNT OF WORK IEB1057I VL GETMAIN REQUESTED minimum TO
AREA, avail BYTES, IS {TOO SMALL maximum BYTES. OBTAINED obtained.
TO ALLOCATE ANOTHER RELEASED freeamt.
BUFFER.|SURPLUS SPACE WHICH IS
Explanation: IEBCOPY requests virtual storage to be
NOT NEEDED.}
subdivided into work areas and buffers. The amount
Explanation: After reading and saving the directory requested and received is controlled by the WORK=
entries for the members to be copied there is still a parameter and the JCL REGION= parameter.
small amount of work area available. The extra area will
This message documents how much was requested and
go unused.
obtained. All numbers are in bytes.
This is not an error condition. This message is to help
you better manage resources by telling you about idle
storage. minimum
minimum amount of virtual storage required by
Normally the remaining work area is used for additional
IEBCOPY. Additional virtual storage is required
buffer space. However, the small amount is not enough
for larger data sets.
for a whole buffer, so the buffer space is not expanded.
maximum
value of the IEBCOPY WORK= parameter,
avail amount of virtual storage unused in the work default 1M.
area.
obtained
amount of virtual storage GETMAIN awarded
The severity is 0.
IEBCOPY.
freeamt amount of virtual storage freed immediately so
User Response: If the amount of storage used by that the region will still contain unallocated
IEBCOPY must be reduced then the size of the work virtual storage for use by system routines, etc.
area could be reduced by about avail. Or, the size of
the work area could be increased enough to hold The severity is 0.
another buffer. The amount of additional storage
required would be the difference between the buffer size
in message IEB1058I and avail. User Response: Use this message with message
IEB1056I to calculate IEBCOPY virtual storage
Source: DFSMSdfp
requirements and actual usage, so that you make the
best use of the computing resources.
IEB1056I RELEASED nnnnn ADDITIONAL BYTES.
To increase the size of the work area:
Explanation: IEBCOPY released the indicated virtual 1. If the REGION= size is large enough so that
storage. IEBCOPY is being given the full amount that it
requests for its work area, then increase the
Small quantities of virtual storage are released at
REGION= parameter and the WORK= parameter by
various processing stages so the access methods and
the same amount. This condition is true when
other operating system services will not fail from lack of
maximum equals obtained.
virtual storage. At IEBCOPY end, all remaining virtual
2. If IEBCOPY is not being given the full amount that it
storage (from the block initially acquired by IEBCOPY)
requests for its work area, then increase the
will be released.
REGION= parameter by maximum-obtained.
When the size of the work area can not be increased,
nnnnn number of bytes released.
1. Reduce the amount specified for buffers (with the
SIZE= invocation parameter) to the minimum
The severity is 0. amount (or default it). This will use the minimum
System Action: Processing continues. amount of work area virtual storage as buffers and
increase the amount of virtual storage available for
User Response: Use this message with message member names and directory entries. Doing this
IEB1055I to calculate IEBCOPY virtual storage most often results in decreased performance, even if
requirements and actual usage, so that you make the it increases the size of the WORK= area so that the
best use of the computing resources. spill file is no longer used.
Source: DFSMSdfp 2. If the current operation is a selective copy, then
divide the operation into more operations each with

a smaller number of members. This leaves more User Response: If it is necessary to reduce the
room in the WORK= area for buffers and directory amount of storage IEBCOPY uses then the work area
blocks. size may be reduced by the size of the second buffer
given in this message.
System Programmer Response: Message IEF374I
printed in the JCL message data set will tell the actual The user response for message IEB1057I discusses
region size used by a job step. The user response for message IEB1057I discusses
Source: DFSMSdfp
Source: DFSMSdfp
IEB1058I ALLOCATED 2 CONTIGUOUS
BUFFERS EACH bbbbb BYTES. WORK IEB1063W MEMBER member1 READ FROM
AREA HAS avail BYTES AVAILABLE. DDNAME ddname IS NOT AN ALIAS
BUT HAS SAME TTR AS MEMBER
Explanation: At the start of each operation IEBCOPY
member2
allocates part of the work area for buffers. The buffers
reported by this message are the minimum size Explanation: The directory of the dataset contains two
required to perform the operation, and are sufficient to entries with the same TTR and neither is an alias.
complete the operation.
member1
bbbbb size of 1 buffer. name of member to be copied
avail amount of virtual storage in the work area still member2
available for tables and saving directory name of member already copied
entries, etc.
ddname
ddname of dataset
The severity is 0.
System Action: Processing continues. The severity is 4.
User Response: This message documents how much System Action: If the current operation is a compress,
of the work area is allocated to buffer to assist you in the identified members are written as one entry (both
managing the virtual storage resource. members will have the same TTR). For all other
operations, the identified members will be written as two
Source: DFSMSdfp
separate members (each member will have a different
TTR).
IEB1059I ALLOCATED SECOND BUFFER OF
User Response: Determine proper relationship of the
bbbbb BYTES. FIRST BUFFER IS NOW
identified members and correct the directory.
fffff BYTES. WORK AREA HAS avail
BYTES AVAILABLE.
IEB1064I STANDARD DD NAMES- sysin sysprint
Explanation: The copy operation is ready to copy the
sysut1 sysut2 sysut3 sysut4
first member. Enough virtual storage remained in the
work area after building tables and saving directory Explanation: This message always precedes
entries for additional buffers to be allocated. IEB1065I. Please refer to it for an explanation of both
messages.
IEBCOPY uses two buffers, so the existing two buffers
have been merged into a single ″first″ buffer. Then a Message inserts and meanings:
new ″second″ buffer is created from the free work area.
sysin DD name for the control statement data set.
A small amount of storage may remain unused in the
sysprint
work area after this second buffer allocation. This is
DD name for the listing data set.
normal.
sysut1 DD name for the input data set.
sysut2 DD name for the output data set.
bbbbb amount of storage added to the buffer pool.
sysut3 DD name for the first spill data set.
fffff original size of the buffer pool.
sysut4 DD name for the second spill data set.
avail residual amount of storage in the work area.
The severity is 0.
The severity is 0.

User Response: Refer to message IEB1065I. The severity is 0.
Source: DFSMSdfp System Action: Processing continues.
User Response: Code the Replace option on the
IEB1065I OVERRIDING DD NAMES- sysin sysprint INDD or SELECT statement to force the member to be
sysut1 sysut2 sysut3 sysut4 copied.
Explanation: IEBCOPY has been called by a program Source: DFSMSdfp
which has given IEBCOPY a list of DD names to be
used for various files. Message IEB1064I lists the
IEB1068W JCL FOR DD ddname WILL PROCESS
default DD names. Message IEB1065I lists the DD
THE DATA SET AS SEQUENTIAL BUT
names IEBCOPY will use.
THE LABEL SAYS IT IS PARTITIONED.
Differences between the two lists indicate that the (DS1DSORG= X'label_org' JFCDSORG=
calling program provided names to override the default X'jcl_org')
names.
Explanation: There is a conflict between the JCL and
Message inserts and meanings: the data set label. The JCL supplied DSORG=PS
overrides the DSORG=PO in the label.
sysin DD name for the control statement data set.
Parameters like DSORG=PS can be added to your JCL
sysprint
even though you did not code them. SMS ACS routines,
DD name for the listing data set.
Data Classes, the JCL LIKE and DCB parameters can
sysut1 DD name for the input data set. all implicitly add to JCL.
sysut2 DD name for the output data set. Message inserts and meanings:
sysut3 DD name for the first spill data set. ddname

sysut4 DD name for the second spill data set.
label_org
The severity is 0. value of the DSORG field in the data set label.
System Action: Processing continues. jcl_org value of the DSORG field in the JCL.
Application Programmer Response: Refer to The severity is 4.

OS/390 DFSMSdfp Utilities book Appendix A for details
about dynamically invoking IEBCOPY. System Action: The existing data set will be
converted from partitioned to sequential and all
Source: DFSMSdfp members in the partitioned data set will be lost. An
unload data set will be created in its place.
IEB1066D diagnostic_text User Response: Determine where the the
Explanation: This message contains diagnostic DSORG=PS is coming from. Look at the label of data
information for you to supply to IBM when requesting sets referenced by the LIKE or DCB parameter, and use
service. ISMF to look at the definition of any Data Class
assigned to the data set.
IEB1067I member NOT disposition FROM INPUT A conflict like this can either be removed at its source or
DATA SET BECAUSE REPLACE WAS you may override the conflict by coding DSORG=PO on
NOT SPECIFIED the DD statement or in the TSO ALLOCATE or ATTRIB
command.
Explanation: The member named was not copied to
the output data set because the output data set already Source: DFSMSdfp
contains a member of the same name.
Message inserts and meanings: IEB1069E JCL FOR DD ddname WILL PROCESS
THE DATA SET AS PARTITIONED BUT
member THE LABEL SAYS IT IS SEQUENTIAL.
name of the PDS or PDSE member. EXPECT A TERMINAL I/O ERROR.
disposition (DS1DSORG= X'label_org' JFCDSORG=
is one of: X'jcl_org')
COPIED Explanation: There is a conflict between the JCL and
LOADED the data set label. The JCL supplied DSORG=PO
UNLOADED overrides the DSORG=PS in the label.
MOVED
ALTERED Parameters like DSORG=PO can be added to your JCL

even though you did not code them. SMS ACS routines, The severity is 0.
Data Classes, the JCL SPACE, LIKE and DCB
System Action: The data set is processed as an
parameters can all implicitly add to JCL.
unload (sequential) data set.
User Response: Remove the conflicting DSORG=PS
ddname parameter or the directory quantity from the SPACE
DD name identifying the data set. parameter. If DSORG=PS does not appear in the JCL
or on the TSO ALLOCATE or ATTRIB command and the
label_org
data set is partitioned then add DSORG=PO to the JCL
value of the DSORG field in the data set label.
or DSORG(PO) to the TSO command.
jcl_org value of the DSORG field in the JCL.
Source: DFSMSdfp
The severity is 8.
IEB1071E DD NAME ddname IS SUPPOSED TO
System Action: When IEBCOPY attempts to read the BE A PARTITIONED DATA SET BUT IT
directory at the start of the data set, one of three things HAS NO DIRECTORY. EXPECT A
may occur: TERMINAL I/O ERROR. (DS1LSTAR=
1. A Wrong Length Record I/O error may occur X'ttr' DS1DSORG=X'label_org'
because the first record is not 256 bytes data with JFCDSORG=X'jcl_org')
an 8 byte key, or
2. IEBCOPY may find 0 directory records which is Explanation: There is a conflict between the JCL and
interpreted as a corrupt partitioned data set, or the data set label.
3. IEBCOPY may find the directory of a deleted
The data set is assumed to be partitioned because the
partitioned data set which used to occupy the disk
JCL contains DSORG=PO or because the JCL is silent
space, which will cause extra members (possibly
and the data set label contains DSORG=PO.
corrupt) to appear in the data set.
A valid partitioned data set must contain a directory,
User Response: Determine where the DSORG=PO is
which means that the address of the last record in the
coming from. Look for directory blocks in the space
data set can not be zero. However, DS1LSTAR is zero
parameter, look at the label of data sets referenced by
which implies that a directory was never written in the
the LIKE or DCB parameter, and use ISMF to look at
data set. Thus the data set is really sequential and the
the definition of any Data Class assigned to the data
JCL incorrectly specifies DSORG=PS, or the data set is
set.
corrupt.
A conflict like this can either be removed at its source or
you may override the conflict by coding DSORG=PS on
the DD statement or in the TSO ALLOCATE or ATTRIB
Data Classes, the JCL SPACE, LIKE and DCB
command.
Source: DFSMSdfp
ddname
IEB1070W JCL FOR DD ddname REQUESTS
DIRECTORY BLOCKS WITH A
SEQUENTIAL DATA SET. (JFCDSORG= ttr address of the last record in the data set. It is
X'jcl_org' JFCBDQTY=dir_blocks) a 3-byte hexadecimal relative disk address.
Explanation: There is a conflict between parameters label_org
in the JCL. The SPACE parameter specifies directory value of the DSORG field in the data set label.
blocks, which implies that the data set is partitioned.
DSORG=PS also appears in the JCL and indicates that
the data set is sequential.
The severity is 8.
even though you did not code them. SMS ACS routines, System Action: Processing continues and the data
Data Classes, the JCL SPACE, LIKE and DCB set is assumed to be partitioned.
parameters can all implicitly add to JCL. When IEBCOPY attempts to read the directory at the
Message inserts and meanings: start of the data set, one of three things may occur:
1. A Wrong Length Record I/O error may occur
ddname DD name identifying the data set. because the first record is not 256 byte data with an
8 byte key, or
2. IEBCOPY may find 0 directory records which is
dir_blocks number of directory blocks specified in interpreted as a corrupt partitioned data set, or
the JCL.

3. IEBCOPY may find the directory of a deleted ALLOCATE or ATTRIB command to explicitly override
partitioned data set which used to occupy the disk the DSORG.
space, which will cause extra members (possibly
Source: DFSMSdfp
corrupt) to appear in the data set.
User Response: Determine where the DSORG=PO is
IEB1073W JCL FOR DD ddname REQUESTS A
coming from. Look for directory blocks in the space
NEW SEQUENTIAL DATA SET WITH
DIRECTORY BLOCKS. THE DATA SET
WAS CREATED AS PARTITIONED AND
WILL BE PROCESSED AS
set.
PARTITIONED. (DS1DSORG=
Add DSORG=PS to the DD statement or the TSO X'label_org' JFCDSORG= X'jcl_org'
ALLOCATE or ATTRIB command to explicitly override JFCBDQTY=dir_blocks)
the DSORG.
Explanation: There is a conflict in the JCL.
Source: DFSMSdfp DSORG=PS has been coded or implicitly added to the
JCL, and/or directory blocks appear in the SPACE
parameter coded in the JCL or implicitly added to the
IEB1072W JCL FOR DD ddname IMPLIES THAT
JCL.
THE DATA SET IS PARTITIONED BUT
IT IS ON MAGNETIC TAPE. The data set is being created in this job step and
PROCESSING IT AS SEQUENTIAL. DADSM has written a directory and set DSORG=PS in
(DEVTYPE= X'dev_type' JFCDSORG= the data set label.
X'jcl_org' JFCBDQTY=dir_blocks)
Explanation: There is a conflict in the JCL or between even though you did not code them. SMS ACS routines,
the JCL and the catalog entry for the data set. Data Classes, the JCL SPACE, LIKE and DCB
The unit allocated to the data set is a tape drive.
Therefore the data set must be an unload (sequential) Message inserts and meanings:
data set. However, the JCL contains DSORG=PO
ddname
and/or a SPACE parameter which specifies directory
blocks which indicates that the data set is partitioned.
label_org
Parameters like DSORG=PO can be added to your JCL
DSORG from the data set label.
Data Classes, the JCL SPACE, LIKE and DCB jcl_org DSORG from the JCL.
dir_blocks
Message inserts and meanings: quantity of directory blocks specified in the JCL
SPACE parameter.
ddname
The severity is 0.
dev_type
device type from the UCBDEVT field. System Action: The data set is processed as
partitioned.
User Response: Examine the JCL, the Data Class
dir_blocks assigned, and the label of any data set referred to by
number of directory blocks specified in the the LIKE or DCB parameter in the JCL. Remove the
JCL. source of the conflict, or code DSORG=PO in the JCL
or on the TSO ALLOCATE or ATTRIB command.
The severity is 0.
Source: DFSMSdfp
System Action: The data set is treated as an unload
data set.
IEB1074I THE UNLOAD DATASET CONTAINS
User Response: Determine where the DSORG=PO is PROGRAM OBJECTS AND OUTPUT
coming from. Look for directory blocks in the space DATASET IS PDS.
Explanation: The PDSE unloaded to create the
unload data set being read contained program objects,
but the target dataset is not a PDSE dataset.
set.
The severity is 8.
Add DSORG=PS to the DD statement or the TSO
System Action: The operation ends.

Source: DFSMSdfp This is not an error condition. This message is to help
you better manage resources by telling you about idle
virtual storage.
IEB1077I member WAS EXCLUDED BUT NOT
FOUND IN ANY INPUT DATA SET Message inserts and meanings:
Explanation: The member was coded on a EXCLUDE size ″SIZE″ parameter value from the OS PARM
statement does not exist in any input data set. field.
Message inserts and meanings: avail amount of storage remaining unused in the
work area.
member
name of PDS or PDSE member.
The severity is 0.
The severity is 0. System Action: The extra storage remains unused.
System Action: No action is taken. User Response: If the amount of virtual storage used
by IEBCOPY must be reduced then the size of the work
User Response: Check the spelling of the name and
area could be reduced by about avail.
the directory of the input library to verify that the
member does not exist. The user response for message IEB1057I discusses
Source: DFSMSdfp
Source: DFSMSdfp
IEB1078I THE BUFFER SPACE LIMIT
PARAMETER ″SIZE=size″ IS LESS IEB1080D diagnostic_text
THAN THE MINIMUM BUFFER SIZE OF
length.
Explanation: A SIZE= parameter was coded in the OS service.
PARM field. The value of this parameter is too small.
Message inserts and meanings: IEB1081D diagnostic_text
size ″SIZE″ parameter value from the OS PARM Explanation: This message contains diagnostic
field. information for you to supply to IBM when requesting
service.
length minimum value required for the parameter.
The severity is 0. IEB1082D diagnostic_text

System Action: The SIZE parameter is ignored. Explanation: This message contains diagnostic
User Response: Remove the SIZE parameter. service.
If you must specify a SIZE parameter, check the
OS/390 DFSMSdfp Utilities book for information about IEB1083D diagnostic_text
calculating the minimum value.
Source: DFSMSdfp information for you to supply to IBM when requesting
service.
IEB1079I CAN NOT ALLOCATE ANOTHER
BUFFER WITHOUT EXCEEDING THE IEB1084D diagnostic_text
″SIZE=size″ PARAMETER. WORK AREA
HAS avail BYTES AVAILABLE. Explanation: This message contains diagnostic
Explanation: The SIZE parameter was supplied, and service.
the supplied value is the total amount of virtual storage
which has been put to use as buffers.
Additional virtual storage is available in the work area
after tables are built and directory entries saved. All of Explanation: This message contains diagnostic
this extra space would normally be assigned to information for you to supply to IBM when requesting
additional buffers. service.
However, this extra space will be unused because the
buffers are already as large as the SIZE parameter
value will permit.

IEB1086D diagnostic_text IEB1096I NO MEMBERS disposition IN DATA SET
REFERENCED BY out_ddname
information for you to supply to IBM when requesting Explanation: Due to the validation error described in a
service. previous message, the ALTERMOD or COMPRESS
operation did not take place. The data set was not
changed.
information for you to supply to IBM when requesting disposition
service. is one of:
MOVED
ALTERED
out_ddname
DD name for the output data set.
service.
The severity is 8.
System Action: No members are altered or moved in
the data set.
User Response: Refer to previously issued messages
for the reason.
service.
Source: DFSMSdfp
IEB1097I FOLLOWING MEMBER(S) disposition IN
DATA SET REFERENCED BY ddname
service. Explanation: Following messages identify the
members altered or compressed.
IEB1091D diagnostic_text This message assists in tracing the data sets which
were used, and which members they contributed.
information for you to supply to IBM when requesting Message inserts and meanings:
service.
disposition
is one of:
IEB1092D diagnostic_text MOVED
ALTERED
information for you to supply to IBM when requesting ddname
service. DD name for the output data set.
IEB1093D diagnostic_text The severity is 0.
Explanation: This message contains diagnostic System Action: Messages IEB154I and IEB155I
information for you to supply to IBM when requesting follow.
service. Source: DFSMSdfp
IEB1094D diagnostic_text IEB1098I mmmmm OF ttttt MEMBERS disposition

Explanation: This message contains diagnostic Explanation: This is a summary of the number of
information for you to supply to IBM when requesting members located in the current input data set and how
service. many were actually copied, etc.
Failure to copy all members may not be an error. Not
IEB1095D diagnostic_text every members found may be eligible because
Explanation: This message contains diagnostic ″replace″ was not specified or because a member of the
information for you to supply to IBM when requesting same name was previously copied.
service. Message inserts and meanings:

mmmmm System Action: The operation is suppressed.
number of members processed.
User Response: Use COPY, not COPYMOD to
ttttt number of members found in the current input compress or unload a data set. To alter an unload
data set. (sequential) data set, reload it with COPYMOD and then
unload it.
disposition
is one of: Source: DFSMSdfp
COPIED
LOADED
UNLOADED
MOVED Explanation: This message contains diagnostic
ALTERED information for you to supply to IBM when requesting
service.
The severity is 0.
System Action: Processing continues. IEB1102D diagnostic_text
Source: DFSMSdfp Explanation: This message contains diagnostic
service.
IEB1099S *** IEBCOPY IS NOT APF AUTHORIZED
***
IEB1103I FIRST GAS BUBBLE IS position
Explanation: IEBCOPY must run from an authorized
MEMBER member AT TTR=ttr.
library to use special I/O appendages. IEBCOPY has
found that it is not authorized, and may not be able to Explanation: A compress operation is scanning a
copy from a partitioned data set. partitioned data set and has located the first space
which is unused. The TTR of this first gas bubble and
The severity is 12.
the name of the member closest to the bubble is given
System Action: IEBCOPY will try to avoid operations in the message.
requiring authorization. It will abend when it can not
A gas bubble inside a member represents space at the
avoid using a service requiring authorization. This
end of a track that is large enough to hold the first
abend will be issued by the requested service (e.g.
record from the next track.
GETMAIN, OPEN) not IEBCOPY.
A gas bubble outside a member represents member
User Response: Verify that any STEPLIB or JOBLIB
data that was deleted or updated.
does not have any unauthorized libraries in the
concatenation. position
is one of:
System Programmer Response: Verify that
BEFORE
IEBCOPY is linked AC(1) into a library in the IEAAPFxx
INSIDE
list used to IPL the system, etc.
AFTER
Source: DFSMSdfp
member
IEB1100S statement MAY NOT BE USED TO
ttr 3-byte hexadecimal relative disk address.
PERFORM A function OPERATION.
Explanation: Certain operations such as COPYMOD The severity is 0.
are restricted from performing specific operations such
System Action: Scanning stops and repacking
as a compress or unload.
members begins.
Source: DFSMSdfp
statement
is one of:
IEB1104E VARIABLE SPANNED RECORD
COPYMOD
FORMAT DATA SETS CAN NOT BE
ALTERMOD
REBLOCKED. EXECUTION
function TERMINATES.
is one of:
Explanation: IEBCOPY does not support partitioned
COMPRESS
data sets with RECFM=VS or RECFM=VBS. (Do not
UNLOAD
confuse this with a unload (sequential) data set which
always has a spanned RECFM.)
The severity is 4.

The input and output DCB parameters demand that User Response: Use this message to estimate how
logical records be reblocked or deblocked. many additional members can be copied with out
increasing the work area size. Each additional member
The severity is 4.
will increase the control table size by 10 bytes.
Source: DFSMSdfp
User Response: Use an application program that has
been coded to handle spanned records to process the
IEB1108I COPYMOD TABLE AREA IS nnnnn
data set.
BYTES LONG. WORK AREA HAS avail
Source: DFSMSdfp BYTES AVAILABLE.
Explanation: Room for COPYMOD tables and buffers
IEB1104W VARIABLE SPANNED RECORD has been reserved.
FORMAT DATA SETS CAN NOT BE
REBLOCKED. EXECUTION
CONTINUES. nnnnn amount of space reserved for COPYMOD.
Explanation: IEBCOPY does not support partitioned avail amount of the work area remaining for buffers,
data sets with RECFM=VS or RECFM=VBS. (Do not tables, and directory entries.
confuse this with a unload (sequential) data set which
always has a spanned RECFM.) The severity is 0.
The input and output DCB parameters do not demand System Action: Processing continues.
that logical records be reblocked or deblocked.
Source: DFSMSdfp
The severity is 0.
System Action: Execution continues as if the data IEB1109D diagnostic_text
sets were RECFM=U. An I/O error may occur.
User Response: Use an application program that has information for you to supply to IBM when requesting
been coded to handle spanned records to process the service.
data set.
Source: DFSMSdfp IEB1110D diagnostic_text
IEB1105I THE TARGET DATA SET IS information for you to supply to IBM when requesting
CURRENTLY EMPTY service.
Explanation: The scan of the output data set directory
discloses that there are no members in the data set. IEB1111D diagnostic_text
The severity is 0. Explanation: This message contains diagnostic
service.
Source: DFSMSdfp
IEB1106I CONTROL TABLE IS ttttt BYTES LONG.
WORK AREA HAS avail BYTES
AVAILABLE.
service.
Explanation: The table of members to be processed
has been built from the SELECT statements or from the
input data set directory (for a full copy). There are avail
bytes left to hold input data set directory entries and Explanation: This message contains diagnostic
output data set directory blocks. information for you to supply to IBM when requesting
service.
ttttt size of the control table.
avail amount of remaining free area.
The severity is 0.
service.

IEB1115D diagnostic_text IEB1125D diagnostic_text
Explanation: This message contains diagnostic Explanation: This message contains diagnostic
information for you to supply to IBM when requesting information for you to supply to IBM when requesting
service. service.

service. service.

service. service.

service. service.

service. service.
IEB1120D diagnostic_text IEB1130I A severity MESSAGE FROM PDSE

PROCESSING APPEARS ABOVE --
DIAGNOSTIC INFORMATION IS
X'diagcode'
service.
Explanation: Something from the current operation
with a PDSE deserves further attention. The diagnostic
information may help the IBM support center should you
Explanation: This message contains diagnostic request software service.
service.
severity
is one of:
WARNING
Explanation: This message contains diagnostic ERROR - an error severity appears as
information for you to supply to IBM when requesting IEB1130W.
service. SEVERE ERROR- a severe error severity
appears as IEB1130E.
TERMINATING - a terminating severity
IEB1123D diagnostic_text appears as IEB1130E.
Explanation: This message contains diagnostic diagcode
information for you to supply to IBM when requesting diagnostic information that should be supplied
service. when requesting service.
IEB1124D diagnostic_text The severity is 0.
Explanation: This message contains diagnostic System Action: Processing Continues.

User Response: Look at the IGW prefix messages
service.
preceding this message for a message of significance.

Application Programmer Response: This probably
IEB1132E VARIABLE FORMAT LOGICAL
represents an unusual condition or problem. Refer to
RECORD IS TOO LONG FOR BLOCK.
accompanying messages, particularly those with IGW
RECORD LENGTH IS length OUTPUT
and IEB prefixes, for specific information and additional
BLKSIZE IS oblksize
guidance.
Explanation: For variable format records, the longest
System Programmer Response: Please furnish the
logical record that can be written to the output data set
information in this message when requesting service. If
is 4 bytes less than the output data set block size
the error recurs and the program is not in error, look at
blocksize. A logical record in the input data set is length
the messages in the job log for more information.
byte long, which is too big to fit in an output data set
block.
Center. Provide the JCL and all printed output and Message inserts and meanings:
length length of the logical record.
Source: DFSMSdfp
blocksize
output data set block size.
IEB1131W PHYSICAL RECORD IN MEMBER
member REFERENCED BY ddname The severity is 0.
EXCEEDS INPUT DATA SET BLOCK
SIZE. RECORD LENGTH IS length, System Action: The operation is ended.
INPUT BLKSIZE IS iblksize, TTR=TTR User Response: Increase the block size of the output
CCHHRKDD=CCHHRKDD. data set.
Explanation: A fat block was found in member Source: DFSMSdfp
member. Most programs cannot read fat blocks; they
receive I/O errors when they try.
IEB1133E COPYMOD WORK AREA OVERFLOW
IEBCOPY is reblocking the input records and will copy PROCESSING MEMBER member
all of the logical records in this fat block to 1 or more
output blocks as needed. Explanation: The internal tables used by COPYMOD
are too small. This may be because the load module
This message will appear only once per member even being processed is defective.
when the member contains more than 1 fat block.
member
member name of the PDS or PDSE member.
ddname The severity is 8.
DD name of the input data set. System Action: The member is copied as if the
length length of physical record. operation were COPY instead of COPYMOD.
iblksize input data set block size. User Response: Try Link Editing the member and/or
executing it to verify that it is a valid load module.
ttr 3-byte hexadecimal relative disk address.
System Programmer Response: If the member is a
mbbcchhr valid load module then request service as the table size
DASD address of record. may be too small.
The severity is 0. Source: DFSMSdfp
System Action: Processing Continues.

User Response: Increase the block size in the label of
the input data set to meet or exceed length, or copy the Explanation: This message contains diagnostic
member to another PDS with a different block size and information for you to supply to IBM when requesting
then back again to reblock it to the current input data service.
set block size.
Source: DFSMSdfp IEB1135D diagnostic_text
service.

IEB1136D diagnostic_text IEB1139W THE OUTPUT DATA SET BLOCK SIZE
IS BEING REDUCED FROM <old> TO
<new> BYTES. ANY EXISTING
PHYSICAL RECORDS LONGER THAN
service.
<new> BYTES ARE FAT BLOCKS AND
MAY CAUSE I/O ERRORS.
Explanation: IEBCOPY may create fat blocks if the
Explanation: This message contains diagnostic data set already contains records longer than the new
information for you to supply to IBM when requesting block size. While the link editor and program fetch and
service. IEBCOPY can tolerate fat blocks, other programs may
encounter I/O errors processing them.
IEB1137E UTTR WORK AREA OVERFLOW System Action: Processing continues, possibly
PROCESSING MEMBER MMMMMMMM, creating fat block.
MISSES=NNNN
User Response: Increase the BLKSIZE and/or LRECL
Explanation: UTTR table has overflowed while of the output data set to be at least as large as the
processing module MMMMMMMM. longest record.
System Action: Processing ceases.

IEB1140W <member> IS NOT A LOAD MODULE.
User Response: Contact IBM support and provide the <reason>. EXPECTED=<expected>
value NNNN for correction. ACTUAL=<actual>
Explanation: While examining the directory entry for
IEB1137W UTTR WORK AREA OVERFLOW the load module, COPYMOD determined that the
PROCESSING MEMBER mmmmmmmm, member is not a load module for the given <reason>. It
MISSES=nnnnnnnn. will be copied without reblocking as if COPY not
Explanation: The table of user TTRs was of COPYMOD was requested. <expected> and <actual>
insufficient size to copy member mmmmmmmm. are length in bytes of the directory entry.
Message inserts and meanings: Possible <reason>s are:

v DIRECTORY ENTRY TOO SHORT (LESS THAN 33
mmmmmmmm
BYTES)
name of member.
v 0 OR 3 USER TTRS
nnnnnnnn
v USER TTR 1 IS A NOTELIST
amount of storage necessary for successful
copy. v RESERVED USER TTR 2 NOT ZERO
v SCATTER LOAD/OVERLAY WITH ONLY 1 TTR
The severity is 4. v USER TTR 2 IS ZERO
Operator Response: Rerun IEBCOPY specifying v 2 TTRS BUT NOT SCATTER LOAD/OVERLAY
PARM=’UTTRTAB=nnnnnnnn’ where nnnnnnnn is the v OVERLAY MODULE WITHOUT NOTELIST
value given in ’misses=’.
v SCATTER LOAD MODULE HAS NOTELIST
System Programmer Response: Processing v DIRECTORY ENTRY SIZE WRONG
continues.
Source: DFSMSdfp
User Response: Validate the directory entry and the
input data set. Relink or recreate the load module.
IEB1138W THE OUTPUT DATA SET BLOCK SIZE
OF <out_size> BYTES IS SMALLER System Programmer Response: Verify that all
THAN THE INPUT BLKSIZE OF maintenance has been applied to programs such as the
<in_size> BYTES. link editor and binder to correct any compatibility
problems.
Explanation: Fat blocks may be created. Increase
output BLKSIZE.
IEB1141W <member> IS NOT A LOAD MODULE.
<reason>
Explanation: COPYMOD determined that the member
currently being processed is not a load module for
<reason>. It will be copied without reblocking as if
COPY not COPYMOD was requested.

Possible <reason>s are:
IEB1143I AT LOAD MODULE RECORD
v OVERLAPPING TEXT BLOCKS <record_count>
v TEXT RECORD SIZE WRONG
Explanation: The relative record number of the last
v OVERLAY MODULE NOTE LIST SIZE load module record COPYMOD examined before
v CESD RECORD SIZE WRONG detecting the error or problem reported in message
v CONTROL RECORD SIZE WRONG IEB1141W or IEB1142W is <record_count>.
v ECORD IS NOT A CONTROL RECORD System Action: Processing continues.

v NO-TEXT MODULE CESDN RECORD SIZE
v IDR RECORD SIZE WRONG IEB1144I MEMBER TT-R AF TT-R.N TT-R.N
v SYM (TEXTRAN) RECORD SIZE WRONG TT-R.N ATTR ...
v UNIDENTIFIABLE RECORD TYPE Explanation: See message IEB1144I.
v READRLD DIAGNOSED RLD PROBLEM System Action: Processing continues.
v RAN OFF END OF ESD TABLE
System Programmer Response: Refer to the link
v GETINPUT DIAGNOSED DS SPACE PROBLEM editor or BLDL macro documentation to interpret the
v OVERLAY MODULE SEGMENT OVER/UNDER RUN hex data.
v OVERLAY MODULE SEGMENT NOT IN NOTE LIST
System Action: A COPY operation is performed for IEB1145I <de_member> <hex_data>
the member. Explanation: IEB1144I titles the printout of the load
User Response: Validate the directory entry and the module directory entry in hexadecimal by message
input data set. Relink or recreate the load module. IEB1145I. These two messages follow IEB1140I.
SYSTEM PROGRAMMER RESPONSE: Verify that all System Action: Processing continues.
maintenance has been applied to programs such as the
link editor and binder to correct any compatibility System Programmer Response: Refer to the link
problems. editor or BLDL macro documentation to interpret the
hex data.
IEB1142W module IS AN INCOMPATIBLE OR

DAMAGED LOAD MODULE AND IEB1153I An INVALID RECORD WAS READ
SHOULD BE RE-LINKED -- COMMON FROM PDSU DDN=ddname
SECTION OUT OF PLACE RECORD=nn DSN=dsname
Explanation: The COPYMOD function of the Explanation: An invalid record was detected in off
IEBCOPY utility cannot unblock a module because the loaded data set.
common sections for the module are not at the end of In the message text:
the module where the link editor usually places them.
COPYMOD cannot process the module displayed in the ddname
message text. The DDNAME of the data set.
In the message text: nn The invalid record number.
module dsname
The load module being processed by COPYMOD. The data set name.
System Action: IEBCOPY uses the COPY function System Action: The copy operation is ended.
instead of the COPYMOD function to process the Source: DFSMSdfp
displayed load module.
Detecting Module: IEBCPMOD
System Programmer Response: Relink or rebind the
load module and then retry the COPYMOD function of
the IEBCOPY utility. IEB1157W DIRECTORY ENTRY FOR MMMMMMMM
CONTAINS AN INVALID UTTR ’ttttrr’
Source: DFSMSdfp REPLACED BY VALID DATA FROM
Detecting Module: IEBCPMOD NNNNNNNN
Explanation: An invalid user TTR was detected while
processing module MMMMMMMM. The invalid data was
replaced by the corresponding user TTR from module
NNNNNNNN.

User Response: Verify that the copied module
functions correctly.
IEB1157E DIRECTORY ENTRY FOR MMMMMMMM

CONTAINS AN INVALID UTTR ’ttttrr’ -
UTTR DATA UNCHANGED
Explanation: An invalid user TTR was detected while
processing module MMMMMMMM.
System Action: Processing ceases.
User Response: Obtain a valid copy of the module in
error.
IEB1160I OUTPUT DATASET

RECFM/LRECL/BLKSIZE COPIED
FROM INPUT DATASET
Explanation: The JCL for the output dataset did not
specify one or more of the dataset attributes listed. The
values have been set from the corresponding attribute
of the input dataset.
System Action: The copy operation continues.
Source: DFSMSdfp
Detecting Module: IEBDSCPY
| IEB1161W DIRECTORY ENTRY FOR MMMMMMMM

| CONTAINS AN INVALID TTR
| Explanation: An invalid user TTR was detected while
| processing module MMMMMMMM.
| System Action: Processing continues.
| User Response: Verify that the copied module
| functions correctly.
| Source: DFSMSdfp
| Detecting Module: IEBWSU

Appendix. Notices
This information was developed for products and services offered in the USA.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that only
that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
USA
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
Mail Station P300
2455 South Road
Poughkeepsie, NY 12601-5400
USA

Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.
The licensed program described in this information and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any
equivalent agreement between us.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:
v ACF/VTAM
v AFP
v AIX
v AT
v BookManager
v C/370
v CICS
v CICS OS/2
v CICS/ESA
v CT
v DATABASE 2
v DB2
v DB2 Universal Database
v DFSMS
v DFSMS/MVS
v DFSMSdfp
v DFSMSdss
v DFSMShsm
v DFSMSrmm
v DFSORT
v eNetwork
v Enterprise System/9000
v Enterprise Systems Architecture/390
v ES/3090
v ES/9000
v ESA/390
v ESCON
v Extended Services
v GDDM
v IBM
v IBMLink
v Infoprint
v Language Environment
v Macro Assembler/2
v MQSeries
v MVS
v MVS/DFP
v MVS/ESA
v MVS/SP
v MVS/XA
v OpenEdition
v OS/2
v OS/390
v PR/SM

v Print Services Facility
v Processor Resource/Systems Manager
v PSF
v RACF
v Resource Measurement Facility
v RMF
v S/370
v S/390
v SecureWay
v SOM
v SOMobjects
v SP
v Sysplex Timer
v System/370
v VM/ESA
v VTAM
v 400
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.
TME is a trademark of Tivoli Systems, Inc.
Tivoli is a trademark of Tivoli Systems, Inc.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, and service names may be trademarks or service marks of others.
Appendix. Notices 791

Readers’ Comments — We’d Like to Hear from You
OS/390
MVS System Messages
Publication No. GC28-1786-16
Overall, how satisfied are you with the information in this book?
Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Overall satisfaction h h h h h
How satisfied are you that the information in this book is:
Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Accurate h h h h h
Complete h h h h h
Easy to find h h h h h
Easy to understand h h h h h
Well organized h h h h h
Applicable to your tasks h h h h h
Please tell us how we can improve this book:
Thank you for your responses. May we contact you? h Yes h No
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you.
Name Address
Company or Organization
Phone No.
___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
GC28-1786-16 IBMR Along Line
_ _ _ _ _ _ _Fold
_ _ _ and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
IBM Corporation
Department 55JA, Mail Station P384
2455 South Road
Poughkeepsie, NY
12601-5400
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
GC28-1786-16 Along Line
IBMR
Program Number: 5647-A01
Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.
GC28-1786-16

Manual de Erros

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Manual de Erros

Hochgeladen von

Copyright:

Verfügbare Formate

OS/390 IBM

MVS System Messages

MVS System Messages

Seventeenth Edition, December 2001

FAX (United States & Canada): 1+845+432-9405

IBMLink (United States customers only): IBMUSM10(MHVRCFS)

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Chapter 2. LANRES Messages (EWX, ACP, ASD) . . . . . . . . . . . . . . . . . . . . 13

Chapter 3. EZM Application Enabling Technology Messages. . . . . . . . . . . . . . . 149

Chapter 4. GDE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 5. GFSA Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Chapter 6. GFSC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Chapter 7. GOS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Chapter 8. GPM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Chapter 9. IAR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Chapter 10. ICP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Chapter 11. ICT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

© Copyright IBM Corp. 1988, 2001 iii

Chapter 13. IDA Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Chapter 14. IDC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Chapter 15. IEA Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

Chapter 16. IEB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

Appendix. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789

iv OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Who Should Use These MVS System Messages Books

How to Use These Books

© Copyright IBM Corp. 1988, 2001 v

Using LookAt to look up message explanations

You can use LookAt on the Internet at:

Where to Find the Most Current Message Information

vi OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Subsystem, Product, and Hardware Books

About This Book vii

viii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

Prefix Component Book Title - Order Number

OS/390 TSO/E Messages, GC28-1978

OS/390 MVS Dump Output Messages,

RMF Messages and Codes, GC28-1948

About This Book ix

OS/390 MVS Dump Output Messages,

OS/390 MVS Dump Output Messages,

OS/390 MVS Dump Output Messages,

x OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

OS/390 MVS Dump Output Messages,

OS/390 MVS Dump Output Messages,

OS/390 HCD Messages, GC28-1849

OS/390 MVS Dump Output Messages,

OS/390 MVS Dump Output Messages,

OS/390 TSO/E Messages, GC28-1885

OS/390 MVS Dump Output Messages,

OS/390 MVS Dump Output Messages,

About This Book xi

OS/390 MVS Dump Output Messages,

RMF Messages and Codes, GC28-1948

xii OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

OS/390 Application Enabling Technology:

OS/390 MVS System Messages, Vol 3

About This Book xiii

OS/390 MVS Dump Output Messages,

Input/Output Configuration Program User’s Guide

xiv OS/390 V2R10.0 MVS System Messages, Vol 3 (EWX-IEB)

OS/390 DFSMSdfp Diagnosis Reference,

About This Book xv