Problem Identification PDF

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 . . . . . . . . . . . . . . . . . . . . .
Locations . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console . . . . . . . . . . . . . . . . . . . . . . . . . .
Hard-Copy Log . . . . . . . . . . . . . . . . . . . . . . . .
System Log . . . . . . . . . . . . . . . . . . . . . . . . .
Job Log . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSOUT Data Set . . . . . . . . . . . . . . . . . . . . . .
Messages. . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Format . . . . . . . . . . . . . . . . . . . . . . .
How Messages are Explained in this Book. . . . . . . . . . . . . .
Messages Sent to MCS Consoles . . . . . . . . . . . . . . . . .
Messages Sent to Hard-Copy Log in JES2 System . . . . . . . . . .
Messages Sent to Hard-Copy Log in JES3 System . . . . . . . . . .
Messages Sent to the Job Log, to Other Data Sets, and to Display Terminals
Truncated Data in Multi-line Messages. . . . . . . . . . . . . . .
A Method for Finding Changes to MVS and TSO/E Message Texts . . . . .
Using SYS1.MSGENU to Find Message Text Changes . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1
. 1
. 1
. 1
. 2
. 2
. 2
. 2
. 2
. 5
. 6
. 7
. 8
. 10
. 11
. 11
. 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
v
v
v
OS/390
OS/390
OS/390
OS/390
JES2 Messages, GC28-1796

JES3 Messages, GC28-1804
TSO/E Messages, GC28-1978
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
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
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

Guide
GA32-0100
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
Specification
N/A
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 Users Guide and Reference
S544-3100
IBM Enterprise Systems Architecture/390 Principles of Operation
SA22-7201
Remote Copy Administrators 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 systems 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
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 installations 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

(ASB-ERB), GC28-1785
ADF
Time Sharing Option Extensions (TSO/E)

session manager
OS/390 TSO/E Users Guide, SC28-1968

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

ADRY
DFDSS

ADY
Dump analysis and elimination (DAE)

AEM
AFB
VSFORTRAN
VSFORTRAN Version 2 Language and Library

Reference, SC26-4221
AHL
Generalized trace facility (GTF)

OS/390 MVS Dump Output Messages,
GC28-1749
AMA
SPZAP service aid

AMB
LIST service aid

AMD
Stand-alone dump

AMS
Availability manager

RMF Messages and Codes, GC28-1948
ANT
Remote Copy

About This Book
ix
Prefix
Component
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

AOP
Infoprint server

API
Starting with Release 8: Infoprint Server

APS
Print services facility (PSF)
Print Services Facility Messages, S544-3675
ARC
DFSMShsm

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

ASB
Advanced Program-to-Program
Communications/MVS (APPC/MVS)

GC28-1749
ASD
LANRES

ASM
Auxiliary storage manager (ASM)

GC28-1749
ASMA
High Level Assembler for MVS & VM & VSE
HLASM Programmers Guide, SC26-4941
ASR
Symptom record (SYMREC)

GC28-1749
ATB
Advanced Program-to-Program
Communications/MVS (APPC/MVS)

GC28-1749
ATR
Resource recovery services (RRS)

GC28-1749
AVM
Availability manager

BFS
IBM LAN server for MVS

BLG
Information System, Information Management
The Information/Management Library Messages

and Codes, SC34-4459
BLM

Prefix
Component
BLS
Interactive problem control system (IPCS)

GC28-1749
BLX

BLW
Loadwait/Restart

BNH
Network Problem Determination Application

(NPDA)
NPDA Messages, SC34-2115
BPX
OS/390 UNIX System Services

GC28-1749
CBDA
Hardware configuration definition (HCD)

OS/390 HCD Messages, GC28-1849
CBR
Object access method (OAM)

CEE
Language Environment
OS/390 Language Environment Debugging

Guide and Run-Time Messages, SC28-1942
CHS
MVSSERV messages for the user and system

programmer
CMP
Compression management services

CNL
MVS message service (MMS)

GC28-1749
COF
Virtual lookaside facility (VLF)

GC28-1749
CSQ
MQSeries
MQSeries for OS/390 V2R1 Messages and

Codes, GC34-5375
CSR
Callable services requests (CSR)

GC28-1749
CSV
Contents supervision, virtual fetch, fetch

GC28-1749
CSY
OPC/A Production Control System
OPC/A Messages, SH19-6448
About This Book
xi
Prefix
Component
CSZ
OPC/A Network Event Communicator
DFH
Customer Information Control System/Virtual

Storage (CICS/VS)
CICS/ESA Messages and Codes, SC33-0672
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

GC28-1749
DQD
Cache RMF Reporter (CRR)
Cache RMF Reporter Program

Description/Operations Manual, SH20-6295
DRK
OPC/A Event Manager Subsystem
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 Users

Guide and Reference, S544-3702
DZJ
Print Management Facility
Print Management Facility Users Guide and

Reference, SH35-0059
EDC
C/C++ Run-time Library

EDG
DFSMSrmm

EQQ
OPC/ESA
OPC/ESA Messages and Codes, SH19-6719
ERB
Resource Measurement Facility (RMF)

RMF Messages and Codes, GC28-1948
ERX
EWX
LANRES

(EWX-IEB), GC28-1786
EZA
OS/390 SecureWay Communication Server IP OS/390 eNetwork Communications Server: IP

Messages Volume 1, SC31-8517
EZB

xii
Prefix
Component
EZM
Application Enabling Technology (AET)/Auto

UNIX System
OS/390 Application Enabling Technology:

Administration and Programming, GC28-1993
OS/390 Application Enabling Technology:
Customization Guide, GC28-1994
EZY

EZZ

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

Codes, SC28-1908
FOMF

Codes, SC28-1908
FOMI

Codes, SC28-1908
FOMM

Codes, SC28-1908
FOMO

Codes, SC28-1908
FOMOA

Codes, SC28-1908
FOMOG

Codes, SC28-1908
FOMOH

Codes, SC28-1908
FSUM

Codes, SC28-1908
FSUMA

Codes, SC28-1908
FSUMB

Codes, SC28-1908
FSUMF

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)

GFSA
Network File System Server

GFSC
Network File System Server Client Messages

GIM
SMP/E
OS/390 SMP/E Messages and Codes,

SC28-1738
About This Book
xiii
Prefix
Component
GQD
GQF
HASP
JES2, network job entry facility for JES2
OS/390 JES2 Messages, GC28-1796
IAR
Real storage manager (RSM)

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 Users Guide and

Reference, GC35-0033
ICN
NCP/SSP/EP
NCP/SSP/EP Messages and Codes, SC30-3169
ICP
Input/Output Configuration Program (IOCP)

Input/Output Configuration Program Users Guide
and Reference, GC28-1027
ICQA
Information Center Facility administrator

messages
ICQC
Information Center Facility user messages
ICT
Programmed Cryptographic Facility

ICU
Cryptographic Unit Support

IDA
Virtual storage access method (VSAM) control

block expansion

IDC
Access method devices

xiv
Prefix
Component
IEA
v Allocation/unallocation

v Auxiliary storage manager (ASM)

v Contents supervision
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

IEC
Data Facility Product (DFP) components

(IEC-IFD), GC28-1787
OS/390 DFSMSdfp Diagnosis Reference,
SY27-7611
IEE
v Auxiliary storage manager (ASM)

v Communications task (COMMTASK)
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
Prefix
Component
IEF
v Allocation/unallocation

v Converter/interpreter
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

IEFI
Converter/interpreter

IEH
Data Facility Product (DFP) utilities

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
IFA
System management facilities (SMF)

GC28-1749
IFB
Input/output environment recording routines:

OBR and SVC 76

IFC
IFCDIP00 service aid for the logrec data set

IFCEREP0 and IFCEREP1 service aids
Environmental Record Editing and Printing

Program (EREP) Users Guide and Reference,
GC28-1378
IFD
Online test executive program (OLTEP)

IFL
Network Control Program (NCP)
3704 and 3705 Control Program Generation and

Utilities Guide and Reference Manual,
GC30-3008
Advanced Communications Function (ACF) for

Network Control Program (NCP)
Network Control Program/System Support

Programs/Emulation Programs Messages and
Codes, SC30-3169
IFO
xvi
MVS Assembler
OS/VS - VM/370 Assembler Programmers

Guide, GC33-4021
Prefix
Component
IGD
Storage management subsystem (SMS) of Data

Facility Product (DFP)

(IGD-IZP), GC28-1788
GC28-1749
IGF
Dynamic device reconfiguration (DDR) Machine

check handler (MCH)

IGGN
Data Facility Product (DFP)

IGV
Virtual storage management (VSM)

IGW
Data Facility Product (DFP) Storage

management subsystem (SMS)

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,
IHJ
Data Facility Product (DFP) checkpoint/scheduler OS/390 MVS System Messages, Vol 5
restart
IKF
VS COBOL II
VS COBOL II Application Programming:

Debugging, SC26-4049
IKJ

GC28-1749
IKM
Programming Language/I (PL/I) syntax checker

IKT
OS/390 TSO/E Messages, GC28-1978,

SC27-0614, SC27-0470, SC23-0114
Advanced Communications Function for Virtual

Telecommunications Access Method
(ACF/VTAM)
VTAM Messages and Codes, SC31-6333
ILR
Auxiliary storage manager (ASM)

ILX
VS FORTRAN Compiler
VS FORTRAN Version 2 Programming Guide for

CMS and MVS, SC26-4222
IHV

Codes
ING

Codes, SC33-7041
ISQ

Codes, SC33-7041
About This Book
xvii
Prefix
Component
INM
Interactive Data Transmission Facility (IDTF)

TRANSMIT and RECEIVE commands
IOAC
Open Systems Adapter-Express (OSA-Express)
OSA-Express Customers Guide and Reference,

SA22-7403
IOP
Input/output configuration program (IOCP)

ES/3090 Processor Complex IOCP Users Guide
and Reference, SC38-0066
IOS
Input/output supervisor (IOS)

GC28-1749
IPD
FORTRAN syntax checker

IRA
System resources manager (SRM)

GC28-1749
IRD
ESCON Director Device Support (EDDS)

IRR
Resource Access Control Facility (RACF)
OS/390 SecureWay Security Server RACF

Messages and Codes, SC28-1918
IRX

restructured extended executor language
(REXX)
ISG
Global resource serialization

GC28-1749
ISN
Service Processor Interface

ISP
Interactive system productivity facility
ISQ

Codes
ISRB
Interactive system productivity facility
ISRL
Library management facility
IST
Advanced Communications Function for Virtual

Telecommunications Access Method
(ACF/VTAM)
Advanced Communications Function for VTAM

Messages and Codes, SC27-0614, SC27-0470,
SC23-0114
ITA
TOLTEP for Advanced Communications Function Advanced Communications Function for VTAM
Messages and Codes, SC27-0614, SC27-0470,
for Virtual Telecommunications Access Method
(ACF/VTAM)
SC23-0114
ITT
Component trace

GC28-1749
xviii
Prefix
Component
ITV
Data-in-virtual

GC28-1749
ITZ
Transaction trace

GC28-1749
IWM
Workload manager (WLM)

GC28-1749
IXC
Cross-system coupling facility (XCF)

GC28-1749
IXG
System logger (SCLOG)

IXL
Cross System Extended Services (XES)

GC28-1749
IXP

ES/9000 ES/3090 IOCP Users Guide Volume
A04, GC38-0097
IXZ
JES common coupling services (JESXCF)

GC28-1749
IYP

zSeries 900 IOCP Users Guide for IYP IOCP,
SB10-7029
IZP

ES/9000 IOCP Users Guide and ESCON CTC
Reference Volume A04, GC38-0401
SNM

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
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
xxi
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
IAR002A
IAR003W
IAR004I
IAR005E
IAR006A
IAR009I
IAR010I
IAR011I
IAR011W
IAR012W
IDC3009I
IDC3351I
IEA253I
IEA435I
IEA437I
IEA811E
IEA812E
IEA848I
IEA920I
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 installations automation
package. Ensure that your installations 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
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
GFSA344I
GFSA345I
GFSA346I
GFSA770I
GFSA777I
GFSA784I
GFSA950I
GFSA951I
GFSA952I
GFSA953I
GFSA954I
GFSA955I
GFSA956I
GFSA957I
GFSA958I
GFSA959I
GFSA960I
GFSA961I
GFSA964I
GFSA965I
GFSA966I
GFSA975A
GFSC100E
GFSC101E
GFSC102E
GFSC103E
GFSC105E
GFSC106E
GFSC107E
GFSC110E
GFSC200E
GFSC201E
GFSC202E
GFSC203E
GFSC204E
GFSC205E
GFSC206E
GFSC207E
GFSC208E
GFSC209E
GFSC307E
GFSC318E
GFSC721E
GFSC722E
GFSC723E
GFSC724E
GFSC725E
GFSC840E
GFSC841E
GFSC842E
GFSC843E
GFSC845I
GFSC846E
GFSC847E
GFSC848E
GFSC849E
Summary of Changes
xxiii
v
v
v
v
v
v
v
v
v
v
v
v
v
v
GFSC850E
GFSC854I
GFSC855E
GFSC856E
GFSC858E
GPM069I
IDC2055I
IDC3897I
IEA015A
IEA016W
IEA020W
IEA051I
IEA052I
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
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
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
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
IEA474E
IEA475E
IEA476E
IEA477I
IEA478E
IEA479I changed to IEA479E
IEA480E
IEA481I
IEA482I
IEA484I
IEA491E
IEA510A
IEA710A
IEA763I
IEA765I
IEA766I
IEA794I
IEA888A
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
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
GFSA439
GFSA440
GFSA566
GFSA786
GFSA801
GFSA802
GFSA822
GFSA823
GFSA909
GFSC210
GFSC211
GPM050I
GPM051I
GPM052I
GPM054I
GPM055I
GPM056I
GPM057I
GPM058I
GPM059I
GPM060I
GPM061I
GPM062I
GPM063I
GPM064I
GPM065I
GPM066I
GPM067I
IEA494I
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
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
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
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
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
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
GFSA991E
GFSC300E
GFSC301E
GFSC302E
GFSC303E
GFSC304E
GFSC305E
GFSC306E
GFSC309E
GFSC310I
GFSC311I
GFSC312I
GFSC313I
GFSC315E
GFSC317E
GFSC319E
GFSC500I
GFSC501I
GFSC502E
GFSC503E
GFSC504I
GFSC505E
GFSC506E
GFSC700I
GFSC701I
GFSC702I
GFSC703E
GFSC704E
GFSC705E
GFSC707E
GFSC708E
GFSC709E
GFSC710E
GFSC711E
GFSC712E
GFSC713E
GFSC714E
GFSC715E
GFSC716I
IDC01880I
IDC01881I
IDC01882I
IDC01883I
IDC01884I
IDC01885I
IDC01886I
IDC01887I
IDC01895I
IDC11468I
IDC1147I
IDC11818I
IDC31880I
IDC31881I
IDC31882I
IDC31883I
IDC31884I
xxxviii
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
IDC31885I
IDC31886I
IDC31887I
IDC31888I
IDC31890I
IDC31891I
IDC31892I
IDC31893I
IDC31894I
IDC31895I
IDC31896I
IDC31897I
IDC31898I
IDC31950I
IDC31951I
IDC31952I
IDC31953I
IDC31954I
IDC31955I
IDC31956I
IDC31957I
IDC31958I
IDC31959I
IEA308I
IEA309I
IEA345A
IEA611I
IEA651E
IEA911E
IEB1138W
IEB1139W
IEB1140W
IEB1141W
IEB1142W
IEB1143I
IEB1144I
IEB1145I
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
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
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
GFSA360I
GFSA361I
GFSA400I
GFSA403I
GFSA404I
GFSA405I
GFSA406I
GFSA407I
GFSA408I
GFSA409I
GFSA410I
GFSA411I
GFSA412I
GFSA413I
GFSA414I
GFSA415I
GFSA416I
GFSA418I
GFSA419I
GFSA420I
GFSA421I
GFSA422I
GFSA423I
GFSA424I
GFSA425I
GFSA426I
GFSA429I
GFSA430I
GFSA431I
GFSA435E
GFSA450I
GFSA451I
GFSA452I
GFSA501I
GFSA502I
GFSA557I
GFSA561I
GFSA811I
GFSA812I
GFSA813I
GFSA814I
GFSA815I
GFSA816I
GFSA817I
GFSA820I
GFSA827I
GFSA829I
GFSA832I
GFSA833I
GFSA840I
GFSA842I
GFSA843I
GFSA847I
GFSA848I
GFSA849I
GFSA850I
xlii
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
GFSA851I
GFSA852I
GFSA853I
GFSA854I
GFSA858I
GFSA859I
GFSA860I
GFSA862I
GFSA863I
GFSA871I
GFSA876I
GFSA877I
GFSA877I
GFSA881I
GFSA886I
GFSA895I
GFSA896I
GFSA897I
GFSA898I
GFSA899I
GFSA970I
GFSA971I
GFSA972I
GFSA973I
GFSA974I
GFSA976I
GFSA977I
GFSA978I
GFSA979I
GFSA997I
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
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.
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
id
id
id
id
CCCnnn text
CCCnnns text
CCCnnnns text
CCCnnnnns text
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.
Decision: The operator must choose an alternative.
Eventual action: The operator must perform action when time is available.
Information: No operator action is required. Most information messages are for a

programmer.
Severe error: Severe error messages are for a programmer.
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.
Decision: Operator must choose an alternative action.
Information: No operator action is required.
Attention: No operator action is required, but an error occurred.
For SYSPRINT messages, the type code indicates the severity:

I
Informational message.
Attention message. Task continues, but an error occurred.
Error message. The particular task might end or might continue without completing all
requests.
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.
Information
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
Severity code. Severity codes can be:

E
Error. Action is required.
Information. Action is not required.
Severe Error. Action is required.
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
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
Information
Severe
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
Information: Severity 0
Severe error: Severity 12
Terminating error: Severity 16
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
Information: Return code 0
Severe: Return code 16
Ending: Return code 12
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).
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
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.
End line or data-end line of a multiple-line message.
Label line of a multiple-line message.
First line of a multiple-line message.
Single-line message that does not require a reply.
Operator LOG command.
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.
A multi-line message that requires a reply and sent only to the hard-copy log.
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.
Command response.
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
Binary:
0 1 0 0
Routing Codes: 1 2 3 4
2
0 0 1 0
5 6 7 8
0
0 0 0 0
9 10 11 12
C
1 1 0 0
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
MLG
JES
MLG
MLG
LOG
LOG
LOG
MLG
LOG
LOG
CN3E1
CN3E1
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
MASTER
CN3E1
CN3E1
CN3E1
CN3E1
CN3E1
CN3E1
CN3E1
CN(15)
CN(15)
CN(15)
CN(101)
CN(101)
CN(101)
CN(101)
CN(101)
CN(101)
CN(101)
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
90131
1734486
1734492
1734492
1734492
1734492
1734501
1734517
1734517
1735017
1735238
1735239
1735239
1735239
1735239
1735239
1735239
1735239
1735239
1735239
1735240
1735240
1735240
1735240
1735506
1735506
1735522
1735522
1735522
1735522
1735522
1735590
1735590
1736007
1736007
1736007
1736007
1736007
1736049
1736050
1736126
1736126
1736353
1736354
1736374
1736374
1736374
1736374
1736374
1736374
SY1 R= SYSLOG
IEF196I IEF237I JES3 ALLOCATED TO SYSLOG02
SY1 R= SYSLOG
IEF196I IEF285I
+MASTER+.SYSLOG.JOB00001.D000000A.?
SYSOUT
SY1 R= SYSLOG
IEE043I A SYSTEM LOG DATA SET HAS BEEN QUEUED TO SYSOUT CLASS A
SY1 R=
0000000 SY1
90131 17 34 49.36 SYSLOG
00000000 IEE042I SYSTEM LOG
SY1 R=
DATA SET INITIALIZED
IAT7001 JOB SYSLOG (JOB00001) IS ON WRITER PRT002(002),RECORDS=1343
IAT7007 JOB SYSLOG (JOB00001) ON WRITER PRT002 (002), DSN=
IAT7007 +MASTER+.SYSLOG.JOB00001.D000000A.?, PURGED.
+E
+I O
IAT8541 NAME
ADDR LV ALT
MAIN
SWITCH
DEPTH DEPQD
IAT8542 CN3E1
(3E1) 15 CN310
SY1
050 00000
IAT8542 MASTER (3E0) 15 -------- -------- TYPE=MCS --- ----IAT8542 MCS15
(320) 15 -------- -------- TYPE=MCS --- ----IAT8542 MCS10
(321) 10 -------- -------- TYPE=MCS --- ----IAT8542 MCS05
(3DC) 05 -------- -------- TYPE=MCS --- ----IAT8542 MCS00
(3DD) 00 -------- -------- TYPE=MCS --- ----IAT8542 MCS302 (302) 15 -------- -------- TYPE=MCS --- ----IAT8542 MCS303 (303) 15 -------- -------- TYPE=MCS --- ----IAT8542 AUTOMCS (
) 15 -------- -------- TYPE=MCS --- ----IAT8542 CN310
(310) 15 CN3E1
SY1
CN3E1
050 00000
IAT8542 CN311
(311) 15 CN3E1
SY1
CN3E1
050 00000
IAT8542 DUMMY
( ) 15 NONE
NONE
032 00000
+T SY2 D R,L
SY2 R= JES3
D R,L
SY2 R=
IEE112I 17.35.50 PENDING REQUESTS 427
SY2 R=
RM=0
IM=0
CEM=1
EM=0
RU=0
IR=0
AMRF
SY2 R=
ID R/K T SYSNAME JOB ID
MESSAGE TEXT
SY2 R=
2 C SY1
*IAT6360 CHECKPOINT DATA SET <CHKPNT2>
SY2 R=
UNAVAILABLE - CHKPNT2 DD NOT DEFINED.
+T SY1 D R,L
-D R,L
SY1 R=
IEE112I 17.35.59 PENDING REQUESTS 603
SY1 R=
RM=0
IM=0
CEM=2
EM=0
RU=0
IR=0
AMRF
SY1 R=
ID R/K T SYSNAME JOB ID
MESSAGE TEXT
SY1 R=
11 C SY1
JES3
*IAT5525 272 DUPLICATE VOLUME DETECTED, CAN
SY1 R=
NOT MOVE VOLUME SPOOL1 ON SY2
+Z LOG NEXT COMMAND IS FROM A MCS-ONLY CONSOLE
IAT7150 CN(15)
NEXT COMMAND IS FROM A MCS-ONLY CONSOLE
-D T
SY1 R=
IEE136I LOCAL TIME=17.36.12 DATE=90.131 GMT TIME=21.36.12 DATE=90.131
+Z LOG NEXT COMMAND IS FROM AN EXTENDED MCS-ONLY CONSOLE
IAT7150 CN(101) NEXT COMMAND IS FROM AN EXTENDED MCS-ONLY CONSOLE
+I Q
IAT8674 JOB SYSLOG
(JOB00001) P=15 CL=A
MAIN(EXECUTING-SY1)
IAT8674 JOB VTAM220 (JOB00004) P=15 CL=A
MAIN(EXECUTING-SY1)
IAT8674 JOB TCAS
(JOB00005) P=15 CL=A
MAIN(EXECUTING-SY1)
IAT8674 JOB SYSLOG
(JOB00007) P=15 CL=A
MAIN(EXECUTING-SY2)
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.
10
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.
11
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
D - IEE162I 46
&NNN. ROLL &A. MESSAGES (DEL=R OR RD)

&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.
12
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
Severity code
E
Error. Operator action is required. LAN Server continues to function.
Information. Operator action is not required.
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
Explanation: This is a generic diagnostic message
used during LANRES software development and debug.
System Action: Command processing continues.
User Response: No additional information is given,
except for information in the message itself.
System Programmer Response: None.
Source: LANRES
EWXxx0001E A member name is not allowed when
the data set name has special
character(s).
Explanation: The user attempted to EWXDS GET or
EWXDS PUT a member of a partitioned data set where
the data set name contained special characters (*).
System Action: Command processing ends. The
system status remains the same.
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
the name. To EWXDS GET or EWXDS PUT all the
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.
EWXxx0004E Function function was unsuccessful.

Reason: reason.
Explanation: The application attempted to perform
function, function. The attempt was unsuccessful with
reason, reason.
User Response: If possible, correct the reason for the
error. Otherwise, contact your system programmer.
System Programmer Response: If the error cannot
be corrected, contact your IBM service representative.
Source: LANRES
EWXxx0005E Conflicting option(s) option(s)
specified.
Explanation: Options entered on the command line
were in conflict with other options.
User Response: Correct the conflict and reenter the
command.
Source: LANRES

Source: LANRES
EWXxx0006E Duplicate option(s) option specified.

Explanation: Duplicate options were entered on the
command line.
13

User Response: Correct the duplication and reenter
the command.
EWXxx0011S Level mismatch between Host and

Server programs.
Explanation: The host is connecting to a NetWare
server running an unsupported version of the LANRES
NLMs.
Source: LANRES

EWXxx0008E Incorrect option(s) option(s) specified.
User Response: Notify your system programmer.
Explanation: The indicated option(s) are not correct.

The error may be a misspelling, missing information,
incorrect information, incomplete information, or
improper abbreviation.
System Programmer Response: Verify that the

NetWare server is running LANRES NLMs at version
3.0 or greater.

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

necessary.

Source: LANRES
User Response: Correct the problem indicated by

error_text. Reenter the command.
EWXxx0015E Command not valid before

EWXCONN LINK login.
Explanation: You cannot enter any administration or

distribution commands until you are logged into the
NetWare server.
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
system programmer.
System Programmer Response: Provide the user
with a user ID and, optionally, a password on the server.
Source: LANRES
EWXxx0019E Insufficient parameters specified.
Explanation: Additional parameters are required for
this command.
command.
Source: LANRES
Source: LANRES
EWXxx0016E The user ID password entered is
longer than 127 characters.
Explanation: The user ID password specified was
User Response: If the spelling of the specified user ID
password is incorrect, correct it. If the specified
password is to be assigned to a user ID, choose a
password with less than 127 characters. Reenter the
command.
EWXxx0020W Cannot close the host file filename.

Error returned was: error_text
Explanation: An error occurred while trying to close
the host file, filename. The explanation for the error,
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
the file is not closed.
error_text to close the file.
Source: LANRES
Source: LANRES
EWXxx0017E Cannot open the host file filename.
Explanation: An error occurred while trying to open
the file, filename, on the host. The explanation for the
error, error_text, was returned in the message.
Source: LANRES
EWXxx0018E Cannot read the host file filename.
Explanation: An error occurred while trying to read
EWXxx0021E Permission denied by NetWare

server.
Explanation: The user has insufficient authority to
perform the operation. Depending on the task being
performed, the proper trustee rights, security
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: Obtain the appropriate authority to
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
file, then perform the operation again. It is also possible
that the operation that you are performing may be on a
directory and not a file. Determine if the filename is a
directory. You can do this by using the distribution
command to list the files and specify the same filename
15
that you entered when you received this message.

System Programmer Response: If appropriate, grant
the proper authority to the user.
Source: LANRES
EWXxx0029E Connected to the function1 function,
not the function2 function.
Explanation: You are connected to the function1
function on the NetWare server, but tried to enter a
command to the function2 function. The command
cannot complete.
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
that caused the error.
If the problem is in the disk, host-to-LAN print, or
LAN-to-host print function, reenter the command that
caused the error.
User Response: Enter the EWXCONN LINK

command to establish a new connection to the NetWare
server. Reenter the command that caused the error. If
the problem persists, notify your system programmer.
System Programmer Response: Unload the
LANRES NLMs from the NetWare server and load them
again. If the problem persists, check the NetWare
server for error messages and contact your IBM service
representative.
Source: LANRES
EWXxx0033E Cannot find host file filename.
Explanation: The host file indicated in the message
cannot be found in the search path.
User Response: Make sure the file name was spelled
correctly, If the file name is correct, make sure the file is
in your search path. Correct the problem and reenter
the command.
If the problem persists, notify your system programmer.
Source: LANRES

again. If the problem persists, contact your IBM service
representative.
EWXxx0034E Error sending data to the NetWare

server. Error returned was: error_text
Source: LANRES
EWXxx0031E Cannot write to host file filename.
Error was: error_text
Explanation: An error occurred while trying to write to
Source: LANRES
EWXxx0032S Authentication error. Connection to
the NetWare server will be dropped.
Explanation: Packets sent between the host and the
NetWare server contain signatures to verify that the
packet originated from the correct function. If this
signature does not match what is expected, then a
communications error has occurred and the connection
to the NetWare server will be dropped.
connection to the NetWare server is dropped.
16
Explanation: A communications error occurred while

sending data to the NetWare server. The type of error is
indicated by error_text.
LANRES function on the NetWare server tries to
recover from this error.
User Response: Reenter the command that caused
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.
communications method is operating correctly. Other
error messages may be displayed to help you determine
the problem. If the problem persists, contact your IBM
service representative.
Source: LANRES
EWXxx0036E Data was not successfully received
from the NetWare server.
receiving data from the NetWare server.

system programmer.
error messages may be issued to help you determine
the problem.
Source: LANRES
EWXxx0037E Error receiving data from the
NetWare server. Error returned was:
error_text
receiving data from the NetWare server. The type of
error is indicated by error_text.
system programmer.
error messages may be displayed to help you determine
the problem. If the problem persists, contact your IBM
Source: LANRES
EWXxx0042E Incorrect user name user specified.
Explanation: A user name must be between 1 and 47
characters long, and cannot contain spaces or any of
the following special characters:
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)
NetWare may also restrict the user name from

containing other special characters.
User Response: Correct the spelling of the specified
user name. Reenter the command.
Source: LANRES
EWXxx0043E Value missing for option option.
Explanation: The specified option requires that an
additional value be assigned to it.
Source: LANRES

EWXxx0041E Incorrect server name server

specified.

command.
Explanation: A server name must be between 2 and

47 characters long, and cannot contain spaces or any
of the following special characters:
/
\
:
;
,
*
?
EWXxx0046E Host and Server security passwords

do not match for the function function.
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)
NetWare may also restrict the server name from

server name. Reenter the command.
Source: LANRES
Explanation: You tried to connect to a LANRES

function on the NetWare server but the passwords you
used did not match those expected by the server
function. Please note that different servers may have
different security passwords.
User Response: Retry the server connection request
specifying the correct security passwords for the server
function.
Source: LANRES
17
EWXxx0050E Double-byte characters cannot be

specified on the command line.
Explanation: Double-type characters were specified
on the command line but these characters cannot be
processed by the command.
command.
Source: LANRES
EWXxx0063I A value for parameter was previously
specified; the new value value will be
used.
Explanation: A value was already specified for the
parameter listed; because the parameter was specified
again, the last value associated with the same
parameter will be used.
System Action: Processing continues.
User Response: If the value needed was the first
value, retype the command using the parameter only
once with the correct data.
Source: LANRES
EWXxx0067E Incorrect print server name server
specified.
Explanation: A print server name must be between 1
and 47 characters long, and cannot contain spaces or
any of the following special characters:
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)
NetWare may also restrict the print server name from

print server name. Reenter the command.
Source: LANRES

Source: LANRES
EWXxx0068E Incorrect print queue name queue

specified.
EWXxx0065E Incorrect nickname nickname

specified.
Explanation: A print queue name must be between 1

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
keywords ADMIN, DISK, DIST, HLPRT, or LHPRT.
User Response: Enter the command with a shorter or
different nickname.
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)

Source: LANRES
EWXxx0066E Incorrect component password data
set dsname specified.
Explanation: A component password data set was
specified in the command but the data set name is
incorrect.
User Response: Correct the data set name and
reenter the command.
18
NetWare may also restrict the print queue name from

print queue name. Reenter the command.
Source: LANRES
EWXxx0069E Incorrect group name group

specified.
server has been lost. The server may no longer be

running or the system administrator may have logged
you off the server.
Explanation: A group name must be between 1 and


/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)
NetWare may also restrict the group name from

group name. Reenter the command.
Source: LANRES
EWXxx0070E Incorrect volume name volume
specified.
Explanation: A volume name must be between 2 and
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)
User Response: Try to reestablish your connection to

the NetWare server. If that fails, make sure the server is
still running or ask your system administrator to verify
that you still have access to the server.
System Programmer Response: Verify that the user
still has a valid user ID on the NetWare server.
Source: LANRES
EWXxx1001E No procedures file found.
Explanation: The program could not find the
procedures file on the system.
System Action: LAN-to-host print service machine
stops.
System Programmer Response: Ensure that the
procedures file has been created and that the
necessary service machines have access to it. See
OS/390 LANRES Configuration Files and Commands
for more information. Then re-start the service machine.
Source: LANRES
EWXxx1002I LAN-to-host print function initialization
completed.
Explanation: Both the LAN-to-host NLM and service
machine have initialized and are ready to start
processing print requests.
System Action: None.
User Response: None.
Source: LANRES
NetWare may also restrict the volume name from

volume name. Reenter the command.
EWXxx1003E No valid procedure names found in

procedures file(s).
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
programs were found to be valid in the procedures
file(s).
Source: LANRES
System Action: The LAN-to-host print service

machine stops.
EWXxx0071E Your login to the NetWare server has

been lost.
Explanation: You cannot issue any more

administration or distribution commands to your target
NetWare server because your login to that NetWare

names in the procedures file(s) are correct. Verify that
the exits exist on the system and are accessible by the
LAN-to-host print service machine. Restart the
19
LAN-to-host print service machine after the corrections

have been made.
Source: LANRES
EWXxx1004I The NLM requested the service
machine be restarted.
Explanation: A condition that caused the LAN-to-host
print NLM to be restarted occurred forcing the host
service machine to restart.
machine is being restarted; the environment remains the
same and no information is lost.
EWXxx1007I Shutting down the LAN-to-host print

service machine at the users request.
Explanation: The service machine is being shutdown
as a result of a interrupt from the keyboard.
System Action: A shutdown can only occur when
there is no job currently printing; therefore the shutdown
will be normal.
Source: LANRES
EWXxx1008I LAN-to-host print servicing has ended.
System Programmer Response: Usually no

additional action is necessary, but the cause of the
restart is not known to the host service machine, for any
additional information refer to the NetWare system
console.
Explanation: The service machine has stopped

processing.
Source: LANRES
EWXxx1005I The maximum number of queues has
been reached.
Explanation: The number of queues to be serviced
exceeds the allowable number. All other queues will be
ignored.
machine operates on the queues defined.
System Programmer Response: Reduce the number
of queues this job processes; start another job to handle
any number of queues above 80.
Source: LANRES
System Action: Processing ended. The return code

will be the most severe value encountered, among the
warning messages.
System Programmer Response: Refer to the
previous messages to determine the cause of the
service machine stopping.
Source: LANRES
EWXxx1009E An unknown packet was received.
Explanation: The service machine has received a
unknown packet type. The host and NetWare server are
out of sync.
System Action: The LAN-to-host print machine will
restart.
EWXxx1006E Error on the NetWare server. Check

the NetWare server console for
messages.
Explanation: An error condition in the LAN-to-host
print NLM occurred that the host did not recognize. A
message stating the error will be displayed by the NLM
and can be found on the NetWare server console.
machine stops; the LAN-to-Host print NLM may or may
not stop, depending upon the severity.
System Programmer Response: Check the NetWare
server console and perform the instructions that the
message states. Restart the service machine after the
necessary steps have been taken.
Source: LANRES
20
Source: LANRES
EWXxx1010E The print server, server, does not
exist on the NetWare server.
Explanation: The print server entered from the
LAN-to-host print service invocation or the default of
HOSTPRT does not exist on the NetWare server being
connected to.
machine stops.
User Response: Verify that the correct print server
was specified. If correct, contact the NetWare system
programmer to have the print queue added to the file
server.
System Programmer Response: If a new print server
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.

Source: LANRES
EWXxx1011E No print queues in the Lan-to-Host
configuration file for, Server.
Explanation: There are no print queues associated
with the specified print server. Therefore, no jobs would
ever be printed.
machine stops.
User Response: Verify that the correct print server
was specified when starting the LAN-to-host print
service machine. If so, contact your NetWare system
programmer to have the desired queues associated with
the requested print server.
System Programmer Response: If the requested
print queue does not exist, it must first be created. After
the print queue exists, it must be associated with the
specified print server, by using the NetWare
PCONSOLE utility or the EWXADMIN functions in
LANRES.
Source: LANRES
EWXxx1012I The user exit, exit has unknown type.
Explanation: The user exit listed in the procedures file
cannot be processed.
System Action: The queue associated with the
particular exit will not be added to the list of queues for
host processing.
System Programmer Response: Check the
processing type of the user exit and make the
necessary changes. Valid type are EXEC, OLDEXEC,
TSO, PGM and INTERNAL.
Source: LANRES
EWXxx1013I The user exit, exit listed in the
procedures file cannot be found.
Explanation: The user exit listed in the procedures file
cannot be found in the search order.
System Action: The queue associated with the
particular exit will not be added to the list of queues for
host processing.
EWXxx1014I Could not translate print queue name,

queue.
Explanation: The queue specified associated with the
NPRINT command could not be translated correctly.
Therefore the LAN-to-host print service machine cannot
determine which user exit to call.
System Action: The print job is not printed; the
LAN-to-host print function continues to run.
System Programmer Response: If the translation
routine is incorrect there will be other similar messages.
Otherwise the name of the print queue may not be
correct in EBCDIC.
Source: LANRES
EWXxx1015I Execution of user exit associated with
queue, queue stopped.
Explanation: The user exit associated with the queue
specified stopped, because it cannot be found, not
executing correctly, or any other possibility.
machine is not stopped. The queue is removed from the
list of available queues for LANRES. The queue will no
longer be valid until the service machine is stopped and
the problem corrected.
System Programmer Response: Determine why the
user exit cannot be executed.
Source: LANRES
EWXxx1016I Job status message could not be
translated.
Explanation: The message returned from the user exit
stating the status of the print job could not be translated
from EBCDIC to ASCII correctly.
System Action: The print job status is unknown; the
System Programmer Response: If the translation
routine is in error there will be other similar messages.
Otherwise the message may not be correct in terms of
translating to ASCII.
Source: LANRES
System Programmer Response: Check the accesses

granted to the service machine and make the necessary
changes.
EWXxx1017I The user exit for queue queue is not

using the stack correctly.
Source: LANRES
Explanation: The expected amount of data is not on

the stack.
System Action: The service machine continues to
21
run. The status message may not be presented to the

client.

Source: LANRES

System Programmer Response: Change the user
exit to ensure the proper data is used and returned to
the LAN-to-host print service machine.
Source: LANRES
EWXxx1022E Did not specify a NetWare print

server after keyword QS.
Explanation: The keyword QS exists in the command
but the NetWare print server name did not follow.
System Action: Command processing ends.
EWXxx1018E Error allocating storage.

Explanation: An error was returned when allocating
storage.
System Action: The service machine continues.
System Programmer Response: Stop the service
machine, free storage, then restart the service machine.
Source: LANRES
EWXxx1019E The user exit definition for queue,
queue, is incorrect.
Explanation: The syntax of the queue line in the
procedures file is incorrect.
System Action: The service machine is not stopped,
though the queue will not be placed on the available
queue list.
System Programmer Response: Correct the line in
procedures file associated with the queue.
User Response: Reenter the command with a print

server name or do not use the QS keyword. If you do
not use the QS keyword, the default print server name
will be used.
Source: LANRES
EWXxx1023I All the fields in the print job
configuration structure may not be
translated correctly.
Explanation: The routine translating the text fields in
the print job configuration structure indicated that the
translations may not be complete. Some of the fields
may not have translated successfully.
machine is not stopped. This data is not used by the
service machine. It is passed directly to the user exits.
Though it is probable the user exit will not succeed.
Source: LANRES

translation routine is not translating correctly; keeping in
mind it may be the type of data being sent from the
NLM.
EWXxx1020E Translation of the NetWare print

server name is not possible.
Source: LANRES
Explanation: The NetWare print server name could

not be translated from EBCDIC to ASCII.
EWXxx1024I The message was longer than 57

bytes.

machine is stopped.
Explanation: The length of the message exceeded 57

bytes which is the maximum length of a message sent
to a client.

server name is not being translated and make the
necessary changes.

run.
Source: LANRES

exit such that the message length does not exceed the
maximum.
EWXxx1021I Using the default NetWare print server

name, server.
Explanation: No NetWare print server was specified
on the command line. The default is being used.
22
Source: LANRES
EWXxx1025I The queuename is being truncated to

its maximum length of length.
Explanation: The length of the queue name has been
exceeded. The queue name will be truncated to fit into
the desired length.
run.
System Programmer Response: The queue name
can be changed to a valid queue name to avoid
truncation. Truncation may result in unexpected results.
Source: LANRES
EWXxx1029E Did not specify a debug value after
keyword DEBUG.
Explanation: The keyword DEBUG exists in the
command but the value did not follow.
User Response: Re-enter the command with a value
for debug, or do not use the DEBUG keyword thus
defaulting debug to off.
Source: LANRES
Source: LANRES
EWXxx1026I The file name is being truncated to its

maximum length of length.
EWXxx1030E Cannot create the print job file, file.

Explanation: The length of the file name has been

exceeded. The file name will be truncated to fit into the
desired length.
Explanation: The file, file, cannot be created. This file

contains the print job the user exits will process. The
explanation for the error, error_text, was returned in the
message.

run.
System Action: The service machine stops.
System Programmer Response: The file name can

be changed to a valid file name to avoid truncation.
Truncation may result in unexpected results.

file cannot be opened.
Source: LANRES
Source: LANRES
EWXxx1027I The execution type is being truncated
to its maximum length of length.
Explanation: The length of the execution type has
been exceeded. The execution type will be truncated to
fit into the desired length.
run.
System Programmer Response: The execution type
may be changed to a valid type to avoid truncation.
Truncation may result in unexpected results.
Source: LANRES
EWXxx1028E Could not open procedure file procs.
Explanation: The program found the procedures file
but cannot open the file to read.
EWXxx1031E Cannot write to print job file filename.

Explanation: An error occurred while trying to write to
System Programmer Response: Correct the problem
Source: LANRES
EWXxx1032E Unable to run user exit: error_text
Explanation: An error occurred while trying to run a
user exit. The explanation for the error, error_text, was
returned in the message.
System Action: LAN-to-host print service machine

stops.


procedures file is not accessed by another process.
Source: LANRES
23
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
the EWXLHPRT.PROCS file.
System Action: The system status remains the same.
System Programmer Response: Correct the entry in
the procedures file.
Source: LANRES
EWXxx1034E LANRES connection already
established for another function.
Explanation: A connection to the NetWare server
already exists for another LANRES function. LANRES
supports only one connection at a time to the NetWare
server.
User Response: Drop the existing LANRES
connection and restart the LAN-to-Host print server.
System Action: The service machine stops.

file cannot be deleted. An exit may not have freed the
file.
Source: LANRES
EWXxx1038E The print server, server, is in use.
Explanation: The print server entered from the
LAN-to-host print service invocation or the default of
HOSTPRT is already being serviced by LANRES.
System Programmer Response: Determine where
the print server should be started from or create another
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
LANRES.
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 Programmer Response: Use the error text to

determine why the output device cannot be opened,
then correct the problem.
System Programmer Response: Review the error

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 exit name specified is not defined.
the LAN-to-host print procedures file.
Source: LANRES
EWXxx1037E Cannot delete the print job file, file.
Explanation: The file, file, cannot be deleted. This file
contains the print job the user exits will process. The
message.
24
Explanation: The named file has been processed

successfully by LANRES and has been given to the
host operating system to print.
Source: LANRES
EWXxx1102E Printing of file failed.
Explanation: LANRES processing for the named file
has failed. Examine other messages in the log to
determine the cause of the failure.
User Response: Correct any errors and resubmit print
job. If problem persists, contact system programmer.

System Programmer Response: Determine cause of
error and take corrective action.
EWXxx1107E Error writing JCL. Error was

error_text.
Source: LANRES
Explanation: An error occurred while writing JCL

needed to print data. Use the error text to determine the
cause of the failure.
EWXxx1103E Options not found for exit exitname.
Explanation: Print exit exitname expects options to be

passed in.



System Programmer Response: Change the
EWXLHPRT.PROCS file to include the necessary
options.
Source: LANRES
Source: LANRES
EWXxx1108E Unable to open JCL member member.
Error was error_text.

the member member. The member will be found in the
dataset pointed to by DD EWXLHJCL or
prefix.EWXLHPRT.JCL if the DD does not exist.
Member EWXLHJOB is the JOB statement that will be
used for all JCL members that do not start with their
own JOB statements. Use the error text to determine
the cause of the failure.
System Programmer Response: Correct the

translation type in the EWXLHPRT.PROCS file.
User Response: Have the system programmer correct

the error then resubmit the print job.
Source: LANRES

EWXxx1105E Error writing print data. Error was

error_text.
Source: LANRES
Explanation: An error occurred while writing the

processed print data. Use the error text to determine the
EWXxx1109E Unable to open job. Error was

error_text.

the job. Use the error text to determine the cause of the
failure.
EWXxx1104E Incorrect translation type type

specified.
Explanation: The translation type specified is
incorrect. Valid types are: LINE, SEND, and NONE.



the error then resubmit the print job.
Source: LANRES

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
type must be 3820 or 38PP.
EWXxx1151E Incorrect AFP structured field.
Explanation: An Incorrect structured field was found in

the input to Enhanced Print stream transformation.

the entry in the LAN-to-host print procedure file.
System Action: The print stream currently being

translated is terminated.

the LAN-to-host print procedure file.
User Response: Re-submit the print job. If it still fails,

there is probably a problem with the print stream to be
translated.
Source: LANRES
25
Source: LANRES
Source: LANRES
EWXxx1156E Unable to open file filename.
EWXxx1152E Begin Document AFP structured field
not found.
Explanation: While trying to open file filename needed

for transformation, an error occurred.
Explanation: An Begin Document AFP structured field

was not found in the first 100 bytes of information to be
translated.


translated.
Source: LANRES
EWXxx1153E Incorrect AFP structured field length.
Explanation: An AFP structured field was found with
an incorrect length.
translated.
Source: LANRES
EWXxx1154E Incorrect AFP SF identifier detected.
Explanation: An incorrect AFP structured field
identifier was found.
translated.
Source: LANRES
EWXxx1155E Dataset dataset_name is not a PDS
dataset.
Explanation: While trying to locate a file need for
transformation, a dataset was encountered that was not
properly allocated.
User Response: Re-allocate the dataset as a PDS
dataset then re-submit the print job.
26

System Programmer Response: Verify that the file
exists and re-submit the print job.
Source: LANRES
EWXxx1157W Unable to use scalable font file
filename.
Explanation: While trying to read file filename a
problem was encountered.
System Action: Transformation continues, but the
output will not use this font.
filename is in PCL Scalable font.
Source: LANRES
EWXxx1158I The maximum number of Soft fonts
soft_font_max has been reached.
Explanation: While trying to add a soft font, it was the
maximum number of soft fonts was reached. The
maximum number of soft fonts is 200.
System Action: Transformation continues.
System Programmer Response: Update the queue
profile to contain fewer soft fonts.
Source: LANRES
EWXxx1159W Font font_name font bitmap file_name
does not exist.
Explanation: The font file file_name cannot be found.
output will not use this font.
System Programmer Response: Make sure file
file_name exists.
Source: LANRES
EWXxx1160W font_type entry font_name dataset

file_name is incorrect.
Explanation: The font_type entry file file_name cannot
be found.
output will not be in this font.
System Programmer Response: Make sure file
file_name exists.
Source: LANRES
EWXxx1161E Mode entry not found in queue
profile file_name.
Explanation: No valid mode entries were found in file
file_name.
System Action: Transformation is terminated.
EWXxx1164W Incorrect class definition class in

AFPFONT entry afpfont_name in queue
profile file_name is ignored.
Explanation: An incorrect AFPFONT entry
afpfont_name was detected in queue profile file_name.
System Action: Transformation continues but this
AFPFONT entry is ignored.
AFPFONT entry afpfont_name in the queue profile
file_name.
Source: LANRES
EWXxx1165W Incorrect scale scale_type of
scale_value in queue profile file_name.
Explanation: A scale_type scale of scale_value is not
valid. Valid values are between 50 and 200.
System Programmer Response: Add a mode entry

into the queue profile file_name.
System Action: Transformation continues but scaling

is set to the default of 100. If no other scale entry was
found in queue profile file_name.
Source: LANRES
EWXxx1162W Incorrect entry_type entry in queue

profile file_name.
System Programmer Response: Correct the Scale

entry in the queue profile file_name to have both the
horizontal and vertical scales between 50 and 200.
Explanation: An incorrect entry_type was found in file

file_name.
Source: LANRES
System Action: Transformation continues but the

option specified by entry_type will not be used.
EWXxx1166W Scalfont entry class in queue profile

file_name is incorrect.
Explanation: An incorrect class was found on a

Scalfont entry in the queue profile file_name .

entry_type entry in the queue profile file_name.
Source: LANRES

scalfont is not used.
EWXxx1163W Duplicate entry_type entry in queue

profile file_name is ignored.
System Programmer Response: Check the class and

attribute specified on the Scalfont entry.
Explanation: A duplicate entry_type was found in file

file_name.
Source: LANRES
System Action: Transformation continues.
EWXxx1167W No file specified on Scalfont entry

class in queue profile file_name.

System Programmer Response: Remove the
additional entry_type entry in the queue profile
file_name.
Source: LANRES
Explanation: The file name is missing from scalfont

entry class.
scalfont is not used.
System Programmer Response: Add the file name
on the specified on the Scalfont entry.
Source: LANRES
27
EWXxx1168W Unable to open file file_name.

Explanation: The file file_name cannot be opened.
System Action: Transformation continues but this file
is not used.
System Action: Transformation is terminated.

System Programmer Response: Verify that all of the
LANRES Transformation files are accessible and
re-submit the print job. It the problem persists, contact
your IBM service representative.

file_name exists.
Source: LANRES
Source: LANRES
EWXxx1178E No free storage available.
EWXxx1169W Incorrect font header in file

file_name.
Explanation: There is no storage available for a free

storage request.
System Action: The command terminates.
Explanation: The file file_name does not have a valid

font header.
System Action: Transformation continues but this font

file is not used.
System Programmer Response: Allocate more

storage for host-to-LAN print and restart host-to-LAN
Print.

file_name is a PCL font bit map.
Source: LANRES
EWXxx1170W Incorrect Setup index setup_index in
queue profile file_name.
Source: LANRES
EWXxx1179E No User parameters specified for
user exit EWXHLTRN.
Explanation: There is no queue profile specified for
the EWXHLTRN user exit.
System Action: The command terminates.
Explanation: The Setup string index setup_index is

not between 1 and 4.

Setup string is not used.
System Programmer Response: Place the name of

the queue profile as a parameter to the EWXHLTRN
user exit.

System Programmer Response: Change the Setup
string index to be between 1 and 4.
Source: LANRES
EWXxx1171W Font entry class is incorrect.
Explanation: The class, pitch or attribute on the font
entry are incorrect.
System Action: Transformation continues but this font
entry is not used.
System Programmer Response: Enter a valid class
pitch or attribute.
Source: LANRES
EWXxx1173E Error found in Host-to-LAN print
Transformation file.
Explanation: An internal error has been detected with
one of the LANRES enhanced print stream
transformation files.
Source: LANRES
EWXxx1180E Transformation output buffer full.
Explanation: The buffer used to store transformed
data is full.
Source: LANRES
EWXxx1341E The Host to LAN print queue context
could not be set.
Explanation: The entry specified for the print queue in
the configuration dataset is probably incorrect.
System Action: The print job is not processed at the
server.
User Response: Correct the queue name and context
in the Host to LAN configuration dataset.
28
Source: LANRES
EWXxx1342E Host to LAN print storage allocation
failure.
Explanation: A storage allocation request has failed
on the server.
server.
User Response: Verify that sufficient storage is
available on the server or increase storage if necessary.
EWXxx1351E Print user exit exitname has incorrect

type type
Explanation: The type specified for the user exit
exitname in the host-to-LAN print procedures file is not
EXEC or PGM.
System Action: The user exit is ignored. The system
status remains the same.
User Response: Correct the user exit type so that it is
EXEC or PGM.
Source: LANRES
Source: LANRES
EWXxx1343E The server internal address was not
found.
Explanation: The address of the server on which the
print queue resides cannot be obtained.
server.
User Response: Verify that the selected server is
operational and that the proper volume is mounted.
Source: LANRES
EWXxx1352E No valid exit names were found in

the print exits file.
Explanation: The host-to-LAN print server reads the
print exits file and verifies that the exits are of the
proper type. No exit names were found with correct exit
types.
User Response: Correct the user exit types so that
they are EXEC or MODULE.
Source: LANRES
EWXxx1344E A file server connection could not be

established.
Explanation: An attempt to connect to the server on
which the print queue resides has failed.
server.
User Response: Verify that the server user licenses
have not been exceeded.
EWXxx1353E An error occurred on the NetWare

server.
Explanation: An error on the NetWare file server that
the host did not recognize. The error will be displayed
on the NetWare system console.
System Action: The host server stops.
User Response: Notify your NetWare system
programmer.
Source: LANRES
System Programmer Response: Check the NetWare

console for error messages and refer to the explanation
associated with the NetWare error messages.
EWXxx1345E The server connection cannot be

authenticated.
Source: LANRES
Explanation: The LANRES object does not have

access to resources on the server.
EWXxx1354E File server fileserver does not exist.

server.
User Response: Unload and reload the LANRES
object with access to server resources.
Source: LANRES
Explanation: A NetWare file server was selected for

the print request, but the file server could not be found.
System Action: The print job is canceled.
User Response: Correct the file server name in the
host-to-LAN print defaults file and restart the
host-to-LAN print server.
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.
29
Source: LANRES
User Response: Reenter the command with a

numeric timeout value in the correct range.
EWXxx1355E An error occurred while sending print

data to the NetWare server.
Explanation: An error occurred during the

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

printing on the server.
EWXxx1357E The timeout value specified, timeout,

is not numeric.
Explanation: The specified print job is waiting to be

printed.
Explanation: The timeout value used to determine

how often the host-to-LAN print server checks for
completed jobs is not numeric data. The data must be
in terms of the number of seconds to wait between
checks.

numeric timeout value.

Source: LANRES
EWXxx1362I Print job jobnumber (jobid) has been
printed.
Explanation: The specified print job was transferred
from the NetWare print queue to the printer.
Source: LANRES
System Action: The specified operation was

performed.
EWXxx1358E The timeout value specified, timeout,

is not in a range of 1 through 359999.
Explanation: The timeout value cannot exceed

359999 seconds. It must be a positive number.
Source: LANRES

30
EWXxx1363I No print jobs currently waiting to be

printed.
Explanation: There are no print jobs, for the user ID
specified, residing in the NetWare print queues.

Source: LANRES

Source: LANRES
EWXxx1377I Printer printer Host ID hostid NetWare

Queue queue NetWare Server server
ASCII NOTIFY Exit Name exitname
exittype ( exitparms
EWXxx1364I Error specifying option option, value

value used.
Explanation: The message lists the value of an entry

in the host-to-LAN print printer definition table.
Explanation: The option option in the host-to-LAN

print defaults file was not set to one of the required
values. It is set to value

User Response: Correct the value specified in the
host-to-LAN printing defaults file.

Source: LANRES
EWXxx1378I Printer printer has already been started.
Source: LANRES
Explanation: The printer printer is currently connected

to JES or VTAM and does not need to be started.
EWXxx1365I The host-to-LAN print server is ending.
System Action: The command to start the printer is

not processed.
Explanation: A stop command was entered for the

System Action: The host-to-LAN print server stops.

Source: LANRES
EWXxx1366E Error reading parameter parameter on
line line of the host-to-LAN print
definition data set dsname.
Explanation: The host-to-LAN print server detected an
error in parameter parameter on line line of the
definition data set allocated dsname.
System Action: The line is ignored.
User Response: Correct the error in the definition
data set.
Source: LANRES
EWXxx1374E Cannot create a REXX stack buffer.
The error returned was: error_text
Explanation: An error occurred while trying to create a
REXX stack buffer on the host. The explanation for the

Source: LANRES
EWXxx1379I Printer printer_name is not an active
printer.
Explanation: The command issued for printer
printer_name failed because the printer was not found
in the list of active printers.
System Action: The operator command is not
processed.
User Response: Reenter the operator command with
the correct printer name.
Source: LANRES
EWXxx1380I An unknown command subcommand
was entered.
Explanation: An operator command other than F or P
was entered.
processed.
the correct command.
31
Source: LANRES
EWXxx1381I An unknown printer subcommand
subcommand was entered.
Explanation: A printer subcommand other than, F, A,
D, or Z was entered.
processed.
the correct subcommand.
EWXxx1385E The JES START command must be

used to start a JES printer.
Explanation: A host START command was issued for
a host-to-LAN JES printer. JES local printers must be
started using the JES $S command.
processed.
User Response: Retry the operation using the JES $S
command.
Source: LANRES
Source: LANRES
EWXxx1382I An incomplete operator command was
entered.
EWXxx1387E The LANRES host-to-LAN Print

server could not connect with JES.
Explanation: The LANRES host-to-LAN print server

did not find a complete operator command statement.

received a non-zero return code from the FSIREQ
CONNECT service.

processed.
System Action: The LANRES host-to-LAN print server

ends.

the required information.
User Response: Contact your system programmer.

Source: LANRES
EWXxx1383I The printer definition on line lineno is
incomplete.
did not find a complete printer definition statement.
System Action: The printer definition is not
processed.
User Response: If one of the parameters in the
printer definition statement was incorrect, correct it.
Otherwise add the missing parameters to the printer
definition statement.
System Programmer Response: Check the FSSDEF

statements to make sure that the host-to-LAN printer
server was correctly defined to JES. If no errors are
found contact your IBM service representative.
Source: LANRES
EWXxx1388I All printer routines have not been
stopped
Explanation: JES requested that the Host-to-LAN print
server end, but there were still active printers.
System Action: The host-to-LAN print server ends.
User Response: Issue the JES commands to stop the
printers, then try to stop LANRES host-to-LAN print.
Source: LANRES
Source: LANRES
EWXxx1384I Error in parameter parameter in
command buffer.
Explanation: The LANRES/MVS host-to-LAN print
server found an error in parameter parameter in the
command buffer.
processed.
User Response: Correct the error and try the
command again.
Source: LANRES
32
EWXxx1389I The host-to-LAN print server has

ended.
received a shut-down command from JES, or ended
abnormally.
ends.
Source: LANRES
EWXxx1390E The host-to-LAN print server could

not start printer printer_name
received a start printer command from JES, but could
not start the printer routine.
System Programmer Response: Check the message
log for the host-to-LAN print server for other error
messages to determine why the ATTACH failed. If
necessary, contact your IBM service representative.
Source: LANRES
EWXxx1391I The host-to-LAN print server could not
find the specified printer printer_name
received a start printer command, but no printer
definition with the specified printer ID was found.
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.
Source: LANRES
messages to determine why the session could not be

established.
Source: LANRES
EWXxx1394E The server name server was not
found in the host-to-LAN print servers
file.
Explanation: The host-to-LAN print command could
not find the server name server in the host-to-LAN print
servers file.
System Action: The host-to-LAN print command
ends.
User Response: Add the entry for the server to the
servers file.
Source: LANRES
already exists for another LANRES function. LANRES
supports only one connection at a time to the NetWare
server.
connection and restart the host-to-LAN print server.
EWXxx1392I The host-to-LAN print server received

error error_text when requesting a
session with PLU luname
Explanation: The LANRES host-to-LAN print servers
attempt to connect to the PLU luname ended with error
error_text.
System Action: The printer is not started.
messages to determine why the session could not be
established.
Source: LANRES
EWXxx1396E Error specifying parameter parameter
of the host-to-LAN print servers file.
Explanation: The value of parameter parameter in the
host-to-LAN print servers file is incorrect.
User Response: Correct the error and retry the print
command.
Source: LANRES
Source: LANRES
EWXxx1393I The option option is no longer used. It
is ignored.
EWXxx1397E Line number number of the

host-to-LAN print servers file is
incomplete.
Explanation: The option specified is no longer used in

the current release of LANRES.
Explanation: Not enough parameters were specified

in the line of the host-to-LAN print servers file.
System Action: The printer is not started.
User Response: Correct the error in the file.

33
Source: LANRES
EWXxx1398I The file server fileserver is on the
network.
Explanation: The file server specified in this message
is currently active on the LAN. This message should
appear only once for each active file server currently on
the LAN when an EWXCONN QUERY PRINT (TYPE
SLIST function is requested.

not find module EWXHLPJS.
Explanation: An error occurred when the host-to-LAN
print server attempted to access module EWXHLPJS in
STEPLIB.
System Action: The host-to-LAN printer task ends.
System Programmer Response: Check that a
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
not create a linkage table entry.
print server attempted to create a linkage table entry.

not open STEPLIB.
print server attempted to access a module in STEPLIB.
System Programmer Response: Contact IBM

support.
System Programmer Response: Check that a

STEPLIB DD exists in the procedure used to run the
host-to-LAN print functional subsystem.
Source: LANRES
Source: LANRES

not create an entry table entry.

not create the vector table.

print server attempted to add an entry to the entry table.

print server attempted to save the address of the vector
table.

support.
Source: LANRES

support.
Source: LANRES
EWXxx1405E The host-to-LAN print server is not a

started task.
Explanation: The host-to-LAN print server determined
that it was not started by JES.
System Programmer Response: Define the
necessary JES statements to start the host-to-LAN print
server as a functional subsystem.
Source: LANRES

not connect to JES.
print server attempted to connect to JES.
User Response: Contact you system programmer.
System Programmer Response: Check that the
definition of the host-to-LAN print functional subsystem
is correct. If it is, contact IBM support.
Source: LANRES
34
EWXxx1410I The host-to-LAN print server received

error error_text when opening the ACB
for printer printer_name.

start a printer because
communications are not active.
Explanation: The host-to-LAN printer server attempted

to open an ACB for printer printer_name and received
an error.
Explanation: The host-to-LAN printer server received

a request to start a printer from JES. However,
communications with the NetWare server are not active.
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.
VTAM definition for the printer is correct.
Source: LANRES
EWXxx1411I The DELETE|MODIFY command cannot
be issued for an active printer.
an operator request to delete an entry from the printer
definition table. However, a printer with name
printer_name is currently active.
System Action: The host-to-LAN printer definition
table is not updated.
Source: LANRES

communications definition for the host-to-LAN print
server is correct. A communications definition may be
changed using the MODIFY operator command.
Communications may be restarted using the MODIFY
operator command.
Source: LANRES
establish communications with the
NetWare server.
a non-zero return code when it attempted to
communicate with the NetWare file server.
EWXxx1412I The definition for printer printer_name

was not found.
an operator request to delete an entry from the printer
definition table. However, an entry with name
printer_name does not exist.
Source: LANRES

communications definition for the host-to-LAN print
server is correct. A communications definition may be
changed using the MODIFY operator command.
Source: LANRES
EWXxx1416E The host-to-LAN print services
module EWXHLPC could not be
initialized.
a non-zero return code when it attempted to define the
services module EWXHLPPC to MVS.
System Action: The host-to-LAN printer server ends.
EWXxx1413I The definition for printer printer_name

already exists.
an operator request to add an entry to the printer
definition table. However, an entry with name
printer_name already exists.

System Programmer Response: Contact your IBM
Source: LANRES

EWXxx1417E The host-to-LAN print services

module EWXHLPC could not be found.


a non-zero return code when it attempted to LOAD the
services module EWXHLPPC.
Source: LANRES

35

host-to-LAN print services module EWXHLPPC is in the
library concatenation for the job.

server could not obtain the command
scheduler communications list.
Source: LANRES

received a non-zero return code from the EXTRACT
service.
EWXxx1418I No host-to-LAN printer definitions were

processed.

ends.
Explanation: Either the host-to-LAN printer definition

data set could not be read, or no valid printer definitions
were found in it.
User Response: Contact your system programmer

entries in the host-to-LAN printer definition data set are
correct. Printer definitions may be added dynamically
using the MODIFY operator command.
Source: LANRES
EWXxx1419E No START parameters were specified
for the host-to-LAN print server.

Source: LANRES
server could not run non-swappable.
received a non-zero return code from the SYSEVENT
DONTSWAP service.
ends.
System Programmer Response: Ensure that the PPT

entry for the host-to-LAN Print server allows the server
to become non-swappable, but does not specify that the
server is non-swappable.
Source: LANRES
Explanation: The length of the command input buffer

returned by the EXTRACT service was 0.

FSS-related statements in the JES initialization data set
are correct.
Source: LANRES
server was not started by JES.
determined that it was started by an operator command,
rather than by JES.
ends.
Do not start the host-to-LAN print server by using the
START command.

server could not find the FSI ORDER
routine EWXHLORD.
received a non-zero return code when it attempted to
LOAD module EWXHLORD.
ends.
System Programmer Response: Ensure that
EWXHLORD is in the library concatenation used by the
Source: LANRES
System Programmer Response: Add the necessary

FSSDEF statements to JES to start the host-to-LAN
Print serving FSS.

server could not establish a recovery
routine.
Source: LANRES

received a non-zero return code from the ESTAE
service.
ends.
36

System Programmer Response: If the error persists,

contact IBM service personnel.
Source: LANRES
Source: LANRES
EWXxx1425E Storage not available for LANRES
Print FSS.
could not obtain storage.
ends.
System Programmer Response: Ensure there is
enough storage available for LANRES host-to-LAN print
serving to run.
Source: LANRES
EWXxx1600E Disk image name name is more than
8 characters.
Explanation: The name for a LANRES disk image is
User Response: Specify a disk image name with no
more than 8 characters.
EWXxx1603S Error reading data from the NetWare

server: error_text.
Explanation: An attempt to read data from the
LANRES disk program that runs on the NetWare file
server was unsuccessful.
System Action: The connection to the NetWare file
server is closed and the LANRES disk server program
continues.
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
re-establish the connection to the NetWare server.
Otherwise, investigate the cause of the error and correct
it.
Source: LANRES
EWXxx1604W Error opening disk image
disk_image_name: error_text.
Explanation: An attempt to open the indicated disk
image was unsuccessful.
Source: LANRES
System Action: The initialization of the LANRES disk

server continues. The disk image which failed to open
will not be used.
EWXxx1601E Error occurred while processing

LANRES command options.
User Response: If it is desired for this disk image to

be used by this LANRES disk server program, correct
the problem and restart the LANRES disk server.
Explanation: An error was detected while processing

the LANRES command options. A previous message
describes the error condition.
EWXxx1605E No disk images specified or no disk

images successfully opened.
User Response: Correct the error and retry the

command.
Source: LANRES
EWXxx1602W Incorrect request received from the
LANRES disk driver running on the
NetWare server.
Explanation: The LANRES disk driver program that
runs on the NetWare file server sent a request that was
not recognized by this LANRES disk server program.
System Action: The LANRES disk serving function
continues.
Source: LANRES
Explanation: Either no disk images were specified

when the LANRES disk server was started or none of
the disk images specified were successfully opened.
System Action: The LANRES command ends and the
disk server is not started.
User Response: Verify that at least one disk image
was specified when the LANRES disk server was
started. If at least one was specified, then for each disk
image specified, error message EWXDSK1604W should
have been displayed to explain the reason why it could
not be opened. Correct the problem or problems and
retry.
Source: LANRES
37
EWXxx1606E Not enough free storage available.
EWXxx1610I Disk server shutting down per request.
Explanation: An attempt to obtain free storage was

unsuccessful.
Explanation: This LANRES disk server is ending in

response to a shutdown request.

System Action: The LANRES disk server ends.
User Response: Make more free storage available for

this LANRES disk server and restart it.
Source: LANRES
EWXxx1607W Disk image file_name has not been
initialized.
Explanation: The indicated disk image has not been
initialized.
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
disk server.
Source: LANRES
EWXxx1608S Error sending data to the NetWare
server: error_text.
Explanation: An attempt to send data to the LANRES
disk driver program that runs on the NetWare file server
was unsuccessful.
server is closed and the disk server program continues.
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
re-establish the connection to the NetWare server.
Otherwise, investigate the cause of the error and correct
it.
Source: LANRES

Source: LANRES
EWXxx1611I Disk server stopped at request of disk
driver program.
Explanation: The LANRES disk driver program that
runs on the NetWare file server has sent a request to
end this LANRES disk server.
Source: LANRES
EWXxx1612S System error code occurred when
attempting to start a timer.
Explanation: An attempt to start a timer was
unsuccessful.
System Action: The LANRES disk server program
ends.
User Response: Correct the error and restart this
LANRES disk server.
Source: LANRES
already exists for a LANRES function other than disk
serving. LANRES supports only one connection at a
time to the NetWare server.
EWXxx1609I Disk driver program closed the

connection.

connection and restart the LANRES disk server.
Explanation: The LANRES disk program that runs on

the NetWare file server closed the connection.
System Action: The LANRES disk server program

continues.
Source: LANRES
38
Source: LANRES
EWXxx1614E NetWare server connection
information not available.
Explanation: The LANRES disk server is unable to
re-establish a connection to the NetWare server
because no connection options were specified on the
LANRES command line and the initial server connection
was established before the EWXLDDSK command was

issued.
User Response: Specify the connection options on
the LANRES disk server command line and retry the
LANRES disk server command.
Source: LANRES
EWXxx1618I Disk Server Release release

Modification modification Service level
service_level started.
Explanation: The LANRES disk server has
successfully completed its initialization and is about to
attempt communications with the LANRES disk driver
program that runs on the NetWare file server.
System Action: The LANRES disk server continues.
EWXxx1615W Server connection signature

mismatch.
Explanation: The signature information in a request
received from the NetWare server is incorrect. This can
occur if the NetWare server was restarted after a
connection had been established.
System Action: The current NetWare server
connection will be terminated and a new connection will
be established.
System Programmer Response: Report this problem
to IBM if it continues to occur and the NetWare server is
not being restarted.
Source: LANRES

Source: LANRES
EWXxx1619S Error closing disk image
Explanation: LANRES was unable to close the
indicate disk image and commit the changes.
System Action: The LANRES disk server continues to
end.
User Response: Investigate the error indicated and
correct the error condition before restarting the LANRES
disk server. The disk image may not contain all of the
changes made by the NetWare server as a result of the
close failure.
EWXxx1616W Actual_number bytes were read from

the disk driver program when
expected_number bytes were expected.
Explanation: More or less data than expected was
read from the LANRES disk driver program that runs on
the NetWare file server.
server is closed and the disk server program continues.
contact IBM service personnel.
Source: LANRES
EWXxx1617S Unable to commit disk image
Explanation: An attempt was made to commit the
data written to the disk image but it was unsuccessful.
User Response: Restart the LANRES disk server
program and rewrite any data that may have been
written immediately preceding the error.
Source: LANRES
Source: LANRES
EWXxx1625E Incorrect value of value specified for
RETRY.
Explanation: The value indicated is not a valid
specification for the RETRY option. Valid values must
be in a range from 10 through 3,600.
User Response: Restart the LANRES disk server with
a valid value.
Source: LANRES
EWXxx1635E Error opening file filename: error_text.
Explanation: An attempt to open the indicated file was
unsuccessful.
User Response: Investigate the cause of the error,
correct it, and retry the LANRES command.
Source: LANRES
39
EWXxx1637E Error reading file filename: error_text.

Explanation: An attempt to read the indicated file was
unsuccessful.
User Response: Investigate the cause of the error,
correct it and restart the LANRES disk server.
Source: LANRES
EWXxx1638E Disk name disk_name in configuration
file filename is too long.
Explanation: The disk name field within the indicated
configuration file was longer than 8 characters.
User Response: Correct the configuration file and
restart the LANRES disk server.
Source: LANRES
EWXxx1644E No disk image definitions found in

configuration file filename.
Explanation: There were no disk image definition
records found in the indicated configuration file.
User Response: Add one or more disk image
definition records to the configuration file and restart the
LANRES disk server.
Source: LANRES
EWXxx1645S Error reading disk image
Explanation: An attempt to read data from 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.
Then stop and restart this LANRES disk server.
EWXxx1640E Missing Dataset Name field in

Source: LANRES
Explanation: The Dataset Name field in the indicated

configuration file is missing for a disk image definition
record.
EWXxx1646S Error writing disk image


Source: LANRES
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.
Then stop and restart this LANRES disk server.
EWXxx1643E Dataset name dsname in

configuration file filename is too long.
Source: LANRES
Explanation: The dataset name field of a disk image

definition record in the indicated configuration file is
EWXxx1650E DBCS characters are not allowed in

the disk image name.

Source: LANRES
Explanation: A SHIFT OUT (X'0E') or SHIFT IN

(X'0F') character was found in the disk image name.
User Response: Specify a disk image name that does
not contain DBCS characters.
Source: LANRES
40
EWXxx1651E Invalid window size size specified in

Explanation: The window size field in the indicated
configuration file is incorrect. The window size must be
a decimal number between 1 and 2048.
Source: LANRES
EWXxx2001E The error returned was error.

Explanation: There was an error returned when a
query was made to determine what function was
connected to your userid. The error is listed in the
message.
User Response: From the error returned, fix the
problem and try the command again. This may require
having to bring the connection to the server back up
again.
Source: LANRES
EWXxx1653E Duplicate disk image name

disk_name specified.
Explanation: Two or more disk images with the same
name were specified when this LANRES disk server
was started.
User Response: Remove the specification of all but
one of the disk images and restart this LANRES disk
server.
Source: LANRES
EWXxx1654E Incorrect Access Mode field
access_mode in configuration file
filename.
Explanation: The access mode field in the indicated
configuration file is incorrect. Only a single character W
or R is correct.
Source: LANRES
EWXxx1655W More than 50 disk images defined.
Explanation: There were more than 50 disk images
defined for this LANRES disk server. Only the first 50
images will be used.
System Action: The LANRES disk serving function
continues.
User Response: Start another LANRES disk server to
support the additional disk images.
Source: LANRES
EWXxx2003E Packets lost in the transmission;

command canceled.
Explanation: A read request has been sent but the
number of packets read does not agree with the number
of packets sent from the NetWare NLM server on the
NetWare server.
User Response: Reenter the command. It may be
necessary to restart the link with the NetWare server. If
the condition persists, notify your system programmer.
System Programmer Response: Check the link
between the host and the NetWare server.
Source: LANRES
EWXxx2004E DOS partition cannot be accessed by
the server.
Explanation: A request has been sent to read to or
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.
System Programmer Response: Restart the server
to load DOS back in the server.
Source: LANRES
EWXxx2005E An error occurred trying to view the
log.
Explanation: A command was issued to view the log.
The return code indicated that there was an error.
41
Source: LANRES
Source: LANRES
EWXxx2006E File filename already exists. Specify

REPLACE option.
EWXxx2010E File filename in use.
Explanation: The specified file already exists.

User Response: If you want to overwrite the contents
of the file, then reenter the command with the
REPLACE option. Otherwise, use a different file name.
Explanation: The file could not be referenced because

it is active.
User Response: Wait until the file is closed and then
Source: LANRES
Source: LANRES
EWXxx2007E File filename already exists; specify

REPLACE option.
EWXxx2011E File filename is read-only.
Explanation: The specified file already exists.

User Response: If you want to overwrite the file,
reenter the command with the REPLACE option. If you
want to keep the file, you can rename the file, using the
command to rename, or you can specify a different file
name for the new file. If you want to examine the file on
the host, you can use the distribution command to
receive the file to get a copy of it.
Source: LANRES
EWXxx2008E File filename already exists; file name
not changed.
Explanation: The distribution command to rename a
file request was unsuccessful because the new file ID
is already being used by another file.
User Response: Specify another file ID.
Source: LANRES
EWXxx2009E Directory dname already exists.
Explanation: The specified directory already exists.
User Response: You can use the distribution
command to list files to examine the existing directory.
Use the distribution command to either remove a
directory or rename the directory to give it a new
directory name.
42
Explanation: The command was unsuccessful

because it attempted to write to, copy to, rename, or
delete a read-only file.
User Response: If you want to change this file,
change the file attributes to NORMAL using the
CHANGE ATTRIBUTES distribution command and then
Source: LANRES
EWXxx2012E The filename specified for the
NetWare server, dirname, is a directory.
Explanation: A filename was entered for the NetWare
server. However, the filename that was entered is really
a directory.
User Response: Reenter the command entering a
valid NetWare filename and not a directory.
Source: LANRES
EWXxx2013E Unsuccessful creating the directory
dname.
Explanation: A distribution command to copy a file or
make a directory request was unsuccessful because it
could not create the new directory on the NetWare
server.
User Response: Check to see if a file with the same
name as the directory already exists. Use the
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

make a directory.

Source: LANRES
Source: LANRES
EWXxx2014E Error writing file filename
Explanation: An input/output error occurred when the
specified file was being written on the server. The
volume space limit may have been exceeded. It is
possible that the primary File Allocation Table or
Directory table was damaged.
User Response: Determine if the disk is full, or if you
have exceeded your volume space limit. If so, remove
files and purge the deleted files with the purge
command, or request for your volume space limit to be
increased. Reenter the command. If the error persists,
notify your server administrator.
System Programmer Response: Verify disk usage
and volume space limits. Determine if the volume is full.
It may be necessary to purge deleted files on the
volume. If the there does not appear to be a disk usage
or limit problem, and the problem persists, run the
NetWare VREPAIR NLM to correct the problems on the
volume. VREPAIR will correct many of the problems
that can occur if the primary File Allocation Table or
Directory table is damaged.
Source: LANRES
EWXxx2015E An input/output error occurred when
the specified file was being read.
Explanation: It is possible that the NetWare servers
primary File Allocation Table or Directory table was
damaged.
EWXxx2017E File filename has been changed since

LASTMOD; file attributes not changed.
Explanation: The file attributes are not changed
because the file was changed at some point after the
last modification date and time information specified on
the EWXDS ATTRIBUTES request.
User Response: Check the file using the EWXDS
LIST command and reenter the command with a
different LASTMOD date and time.
Source: LANRES
EWXxx2018E Message cannot be longer than nn
characters; message not sent.
Explanation: The distribution command to send a
message to a NetWare user has been entered with
message text that is longer than the maximum allowed.
For messages sent to all users or to a specific user ID,
the maximum is 57 characters. For messages sent to
the NetWare console, the maximum is 79 characters.
User Response: Reenter the command with a shorter
message text.
Source: LANRES

User Response: Reenter the command. It may be
necessary to reissue the EWXCONN LINK command to
reset the connection. If the condition persists, notify
your system programmer.
System Programmer Response: Run the NetWare
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
table is damaged.
Source: LANRES
EWXxx2016E File filename is empty.
EWXxx2019E User user is not logged in.

Explanation: The specified user is not logged in to the
NetWare server, so no message has been sent. This
message is applicable only when the userid option of
the command is used.
User Response: Try again later after the user is
logged in.
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.
43
EWXxx2021E File filename not found.

Explanation: The specified file was not found. The file
does not reside on the directory, the file identification
was misspelled, or incomplete identification was
provided.
User Response: Verify that the volume on which the
file resides is mounted and that the complete file
identification was spelled correctly.
Source: LANRES
EWXxx2022E Directory dname not found.
the volume information for your particular volume. If you

get message 2021, the volume does not exist. Ask your
system programmer for help. If the volume does exist,
note the number of the blocks left in the volume. If you
decide to erase some of the files, use the distribution
command to delete files.
System Programmer Response: Check that all the
volumes are correctly allocated. If the specified volume
has not been created, determine if this volume should
be added or a different volume should be used by the
user.
Source: LANRES
EWXxx2025E Paths must end with a backslash
when SUBDIR is specified.
Explanation: The specified directory was not found.

Either the directory does not reside on the volume, the
directory name was misspelled or incomplete
identification was provided to cause the appropriate
path to be searched.
Explanation: The SUBDIR option can only be used to

copy entire subdirectories and neither a source not
destination file name can be specified. The backslash (\)
at the end of both the source path and destination path
verifies that the previous characters are interpreted as
subdirectory names instead of file names.


User Response: To verify the directory exists, enter

the command to list the files. Verify that the volume on
which the directory resides is mounted.

command.

Source: LANRES
Source: LANRES
EWXxx2026E Error opening the file filename.
EWXxx2023E Cannot remove a nonempty directory.
Explanation: The distribution command to remove a
directory has been entered to remove an existing
directory and the specified directory contains files.

specified file was being opened, or the file is an
execute-only file, or the file is being used by another
user.


User Response: Enter the distribution command to list

file and examine the files in the directory. If you decide
to erase all the files in the directory, use the distribution
delete command.
User Response: Check to see if the file is an

execute-only file by using the command to list the files.
If the file is not an execute-only file, reenter the
command. If the error persists, notify your system
programmer. The file may also be in use by another
user. Be sure that there is no one else using the file.

Source: LANRES
EWXxx2024E Volume volname not found or volume
is full.
Explanation: The distribution command to copy files
was entered to copy files from one directory to another
directory and the specified target volume does not exist
or the target volume does not have any space left.
User Response: Enter the distribution command to list
44

volume. VREPAIR will correct minor problems that occur
if the primary File Allocation Table or Directory table is
damaged, which may have been the reason for the
error.
Source: LANRES
EWXxx2027I The log file was cleared on date at time.
not been removed from the server. The DOS error code
meaning can be found in the DOS reference manual.
Explanation: This is an informational message

indicating when the log was last cleared.
Source: LANRES

EWXxx2032E Incorrect distribution command name

issued.
Explanation: The user entered a command that was
not recognized by the distribution.
Source: LANRES

EWXxx2028E File(s) must be on the local server.
User Response: Verify that the distribution command

was spelled correctly. See OS/390 LANRES
Configuration Files and Commands for correct syntax.
Explanation: The distribution command that you

entered cannot be used to process files on a remote
server. You probably preceded the file name(s) with a
remote server name. The server name should not be
specified, or else it must be the local server name.
User Response: Verify that the local server, the server
that your system is physically connected to, is the
correct server.
Source: LANRES
EWXxx2029E Unable to load file filename on the
server.
Explanation: An error occurred while loading the
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
requires that other NLMs be loaded first, or the file is
not an NLM.

Source: LANRES
EWXxx2033E The UNIT parameter contains
incorrect syntax. The 5th character
must be a dash (-).
Explanation: The fifth character must be a dash (-)
when the six character format is specified.
System Action: The distribution command is not
processed.
User Response: Correct and retry the failing
command.
Source: LANRES
EWXxx2034E The UNIT parameter has incorrect
length. The length must be 4 to 6
characters.

Explanation: The UNIT parameter must contain at

least four characters and not more than six.
User Response: Verify that you are specifying the

correct NLM and that all prerequisite NLMs are already
loaded.
System Action: The distribution command is not

processed.
User Response: Correct and retry the failing

command.
Source: LANRES

Source: LANRES
EWXxx2030E command was unsuccessful. DOS

error code-nn
Explanation: An unexpected error has occurred while
working with files on the DOS partition of the server. It
is possible that DOS has been removed from the server.
User Response: Verify that the command syntax is
correct and retry the command. If the error persists,
notify your server administrator.
EWXxx2036E Error copying the file filename.

specified file was being copied. The primary File
Allocation Table or Directory table may be damaged.
User Response: Reenter the command. If the error
persists, notify your system programmer.
System Programmer Response: Verify that DOS has

45

volume. VREPAIR will correct minor problems that can
occur if the primary File Allocation Table or Directory
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

copied.
Explanation: The user entered a directory name that

was more than 254 characters in length.
Explanation: The server file contains only an

end-of-file character. This file is considered to be empty
and cannot be copied. This error will also occur when
request is made to copy from a particular record of the
file, and the file contains less than that number of
records.

Source: LANRES
User Response: Verify that the file does contain data,

and the number of records in the file. Reenter the
command with the correct values or parameters.
EWXxx2048E The two volume names vol1 and vol2

must be the same.

Source: LANRES
User Response: Correct the directory name to be less

than 254 characters.
Source: LANRES
Explanation: The attempt to rename the directory or

file was unsuccessful, because the files/directory to be
renamed must reside on the same volume.
EWXxx2040E Distribution command name ended

with a server error code of nn.

Explanation: An unexpected error occurred while

processing the command.
User Response: Enter the same volume name for

both directories or files and reenter the command.

User Response: Verify that the command syntax is

correct and reenter the command. If the error persists,
notify your system programmer of the server error code.
System Programmer Response: See the NetWare
System Messages book for the server error code.
Source: LANRES
EWXxx2041I time renaming filename1 to filename2.
Explanation: The information message is displayed
when the distribution command to rename a file with the
option to TYPE out information messages is used.
System Action: The specified operation is performed.
Source: LANRES
EWXxx2042I time copying filename1 to filename2.
Explanation: The information message is displayed
when the distribution command to copy a file with the
option to TYPE out information messages is chosen.
System Action: The specified operation is performed.
46
Source: LANRES
EWXxx2049E Directory cannot be removed.
Explanation: The attempt to remove a directory on the
NetWare server by specifying the option to remove the
directory with the delete files command was
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
flag was set on for that directory.
System Action: Files may have been removed from
the directory but the directory remains.
User Response: Check to see if any of the reasons
for the error listed above apply. Correct the situation
and use the command to remove directories to remove
the directory.
Source: LANRES
EWXxx2052E You must be logged into the local
server to run this command.
Explanation: You must be logged into the local server
to enter this command. The local server is the server
running the LANRES NLMs that you are directly
connected to by one of the LANRES communication

methods. If you enter the EWXDS QUERY ID
command, your local server is shown opposite File
Server Name and the server you are logged into is
shown opposite Logged in Server Name.
User Response: Enter the EWXCONN DROP
command to drop the current connection. Then enter
the EWXCONN LINK command and directly connect to
the server that you want the command to run on.
Source: LANRES
EWXxx2056I SERVER number = servername
Explanation: Indicates the server name of a NetWare
server that is connected to the same LAN as the current
server.
EWXxx2060I p1 p2 p3 p4/p5/p6 p7:p8:p9

Explanation: This is used for a buffer that will be
formatted and displayed.
Source: LANRES
EWXxx2061E Error_text returned on open of dataset
dataset
Explanation: The attempt to open dataset dataset on
the host, was unsuccessful. The reason for the error is
identified in the message.
User Response: The error text will identify the reason
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: This is used for a header that will be
Explanation: Indicates the number of directories found

when the distribution command to list the files in a
directory was issued.
Source: LANRES
Source: LANRES
EWXxx2058I Filename Size Attrs Create Date Time
EWXxx2063I Files found: files (bytes Bytes).

Explanation: Indicates the number of files found when

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

Source: LANRES
EWXxx2064I buffer
Explanation: Displays a buffer that has been
formatted to the user.
47
Source: LANRES
EWXxx2065I parm1 parm2 parm3 parm4 parm5
Explanation: Sets up a buffer to be formatted and
displayed to the user.
EWXxx2069E Incorrect date, date, specified.

Explanation: The date entered in not a valid date.
User Response: Choose a valid date and reenter the
command.
Source: LANRES
Source: LANRES
EWXxx2066E The directory name, dirname,
specifies a server.
Explanation: A directory name was entered that
included a server name. The server name cannot be a
part of the directory name.
User Response: You can do one of two things. Enter
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
running the command again.
Source: LANRES
EWXxx2067E Incorrect filename, filename,
specified.
Explanation: The file name entered is not a valid file
name.
User Response: Specify a correct file name.
EWXxx2070E Error_text returned on reading of file

filename.
Explanation: An attempt to read the host file,
filename, was unsuccessful. The reason for the error is
specified by error_test.
User Response: Use the information provided by
error_text to determine the cause of this error.
Source: LANRES
EWXxx2071E The connection to the server is to the
administration function.
Explanation: You are requesting to run a distribution
command, but you do not have a connection to the
distribution function.
User Response: Drop the connection from the current
function, get a connection to the distribution function,
and reenter the command.
Source: LANRES
Source: LANRES
EWXxx2072E There is no connection to the server.
EWXxx2068E Incorrect time, time, specified.
Explanation: The time entered in not a valid time.
Explanation: You issued a command for the LANRES,

but you do not have a connection to the server.


User Response: Choose a valid time and reenter the

command.
User Response: Issue the EWXCONN LINK

command to receive a connection to the NetWare
server.

Source: LANRES

Source: LANRES
48

disk function.
EWXxx2152I Logged in Server Name. . . . . . . . . .

name

Explanation: You are logged in to a user ID on this

NetWare server. This may or may not be the same as
the local server that you are connected to. The local
server is the server that is running the LANRES NLMs.

Source: LANRES
host-to-LAN Print function.
Source: LANRES

Source: LANRES
EWXxx2153I Logged in NetWare Level. . . . . . . . .
vrelease.mod
Explanation: This is the level of the NetWare server
that you are logged in to.
Source: LANRES
EWXxx2154I File Server Name . . . . . . . . . . . . name
Explanation: This is the NetWare server that you are
connected through. This is the server that is running the
LANRES NLMs.

LAN-to-host Print function.


EWXxx2155I NetWare Level. . . . . . . . . . . . . .

vrelease.mod

Explanation: This is the level of the NetWare server

that you are connected through.

Source: LANRES
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
Explanation: The command you entered were made

by this LANRES host function.

Source: LANRES

Source: LANRES
49
EWXxx2157I Host Level . . . . . . . . . . . . . . .

vversion.release.mod.sl
Explanation: This is the level of the host LANRES
program that you are using.

Source: LANRES
EWXxx2177E Error_text returned on closing dataset
dataset.
Explanation: An attempt to close dataset dataset on
specified by error_text.
Source: LANRES

EWXxx2158I NLM Function . . . . . . . . . . . . . .

function

error_text to determine the problem.
Explanation: This is the LANRES function that you

are connected to on the NetWare server.

Source: LANRES

Source: LANRES
EWXxx2159I NLM Service Level . . . . . . . . . . .
service_level
Explanation: This is the service level of the LANRES
function that you are connected to on the NetWare
server.
EWXxx2178E Error_text returned on deleting

dataset dataset.
Explanation: An attempt to delete dataset dataset on
Source: LANRES
Source: LANRES
EWXxx2179E The length of the translated string is

larger than the buffer.
EWXxx2175I None
Explanation: An attempt was made to translate a

string that was larger than the buffer.
Explanation: This is a message used in an

information message.

Source: LANRES
Source: LANRES
EWXxx2176E Error_text returned on writing to
dataset dataset.
Explanation: An attempt to write to dataset dataset on
50
EWXxx2180E There was an error renaming

filename1 to filename2.
Explanation: You requested to rename a file, but an
error occurred.
User Response: There are more informational
messages that accompany this message. Use these
additional messages to determine the problem.
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

to filename2.
Explanation: You requested to copy a file, but an

error occurred.
User Response: There are more informational
messages that accompany this message. Use these
additional messages to determine the problem.
Source: LANRES
EWXxx2182I Successfully renamed numfiles of
totfiles files.
Source: LANRES
EWXxx2185E A severe error occurred trying to
view the dsname dataset.
Explanation: An attempt was made to BROWSE the
dataset using the ISPF BROWSE function. The
application indicated a severe error occurred.
User Response: Determine if there is a problem with
the dataset listed in the error message and fix the
problem.

indicating how many files were successfully renamed.
Source: LANRES

EWXxx2186E Requested dataset, dsname, is empty.
User Response: If the two numbers in the message

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
Explanation: A request was made to view the dataset

in the message, but the dataset is empty.
Source: LANRES
EWXxx2183I Successfully copied numfiles of totfiles

files.
indicating how many files were successfully copied.
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.
Source: LANRES
EWXxx2187E The member name must be bounded

by /.
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 didnt use
the MEMBER option.
User Response: Reenter the command with the
slashes around the member name.
Source: LANRES
EWXxx2184E Distribution supports FB or VB

recfms. The dataset has a RECFM of
recfm.
Explanation: The user attempted an EWXDS GET or
EWXDS PUT. But, when the dataset was opened, it
showed a RECFM that was not FB or VB. LANRES only
supports FB or VB record formats.
EWXxx2188E An asterisk may not be a part of the

member name.
Explanation: If a member name is specified, it may
not contain an asterisk.
User Response: Reenter the command specifying a
member name without asterisks.
51

Source: LANRES
EWXxx2196E The dataset name entered cannot

have an asterisk in the fourth qualifier
or beyond.
EWXxx2189W The value for option was not valid. It

was changed to newvalue.
Explanation: An asterisk was entered in the dataset

name that went beyond the third qualifier.
Explanation: The value for the option specified was

not valid. It was changed so that processing could
continue.


User Response: Reenter the command. Do not place

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

long.
Explanation: The dataset name specified is not a

partitioned dataset. But, you specified the member
option as if it were a partitioned dataset.
Explanation: The dataset name entered is too long.

User Response: Reenter with a dataset that is the

correct length.

valid partitioned dataset name if you are using the
member option or enter a valid sequential dataset name
without the member option.
Source: LANRES
Source: LANRES
EWXxx2191E The member name, member, is too

long.
EWXxx2198E The dataset specified is not a

sequential dataset.
Explanation: The member name entered is too long.
Explanation: The dataset name specified is not a

sequential dataset, but is a partitioned dataset.

User Response: Reenter with a member that is the
correct length.
Source: LANRES

valid partitioned dataset name if you are using the
member option or enter a valid sequential dataset name
without the member option.
EWXxx2195E The value specified, value, cannot be

more than 9 digits long.
Source: LANRES
Explanation: A value for the option FROM, FOR,

OFFSET, LENGTH or LRECL was entered with a value
that was more than 9 digits long.
EWXxx2199E The option_1 option must be used

before specifying option_2.

correct value.
Explanation: In order to use the option specified, put

either ASCII or BINARY before the option shown in the
message.
User Response: Reenter the command specifying

either ASCII or BINARY.
Source: LANRES

Source: LANRES
52
EWXxx2301E Option option requires a numeric

value.
Explanation: The specified option requires a numeric
value to be specified. Either no value was found or a
non-numeric value was found.
command.
Source: LANRES
EWXxx2302E Option option requires a value.

User Response: Reenter the command. If the
problem persists, take down the link using the
EWXCONN DROP command and restart it with the
EWXCONN LINK command.
Source: LANRES
EWXxx2306E Error_text returned on read of file
filename
Explanation: The specified error was returned when
reading from the identified file.
Explanation: The specified option requires a value to

be specified. No value was found.
User Response: The cause of the error should be

identified in the error text. Correct the problem and


command.
Source: LANRES
EWXxx2303S Storage allocation error.
Explanation: The program running was unable to
allocate sufficient storage to complete the command.
Source: LANRES
EWXxx2304E Error translating string.
Explanation: While attempting to translate a string, a
translation error occurred. The string may have been a
server file name or the actual data that was being sent
to the server.
has the correct code pages selected and that the
translation tables are available.
Source: LANRES
EWXxx2305E Error_text error returned from pipe.
Explanation: The identified error was returned from
the host to server connection. The data link is probably
not available.
Source: LANRES
EWXxx2307W Error_text error returned on close of
file filename
attempting to close the identified file. The file may be
intact.
User Response: Examine the file to determine if the
content is correct. If not, the error text identifies the
cause of the error. Correct the problem and reenter the
command.
Source: LANRES
EWXxx2308E Incorrect server volume name:
volname
Explanation: The server volume name specified on
the PC file name path was incorrect or missing. The
volume name must be specified for all files.
User Response: Correct the volume name and
Source: LANRES
EWXxx2309E Incorrect server file name: filename
Explanation: The server file name specified was
incorrect or missing. A PC file name must be specified,
or the wildcard * must be used. If a wildcard is used,
then the wildcard may not be accompanied by any other
characters. For example, sys:\t*.ext is incorrect because
53
the t appears before the *. The length server path

specified must be less than the NetWare restricted
length of 254 characters.
EWXxx2313E Error_text error returned on write to

dataset dataset.

writing to the identified dataset.
User Response: Correct the file name and reenter the

command.

Source: LANRES
User Response: The cause of the error is identified in

the error text. Correct the problem and reenter the
command.
EWXxx2310E Error matching file filename_pattern Error_message
Source: LANRES
Explanation: While attempting to determine the host

files that matched the specified file name pattern the
identified error occurred.
EWXxx2314W Error_text returned on open of

dataset dataset.

User Response: User response will depend on the
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
their system programmer to obtain access.
Source: LANRES
EWXxx2311E Incorrect host dataset name dataset
Explanation: The dataset name specified was not
valid. Correct the dataset name and reenter the
command.
Explanation: An attempt to open the translation

defaults dataset was unsuccessful. The reason for the
error is identified by error_text.
User Response: The file transfer will continue using
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
EWXTRANS ddname. If the error text indicates
improper authorization, see your system programmer.
System Programmer Response: If the user was
denied access, grant them access to the dataset.
Source: LANRES
EWXxx2315I Time starting transfer of name

command.
Explanation: name is being transferred to the server

or from the server. This message is informational only.
System Action: None. Message is informational only.
Source: LANRES

EWXxx2312W An incorrect line received: dataline

Explanation: The LANRES list file command returned
an incorrect line of data. The line of data will be
ignored. It is possible that undetected I/O errors are
occurring on the disk, or that undetected
communications errors are occurring between the host
and the server. If the problem persists, contact your
support programmer.
Warning message only.
User Response: If the message persists, contact your
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
54
Source: LANRES
EWXxx2316I Time completed transfer of name
Explanation: name is being transferred to the server
or from the server. This message is informational only.
System Action: None. Message is informational only.
Source: LANRES
EWXxx2317W The entry filename in defaultname is

too long.
Explanation: The entry, filename, in the translation
defaults, defaultname, was incorrect. Names must be
shorter than the system identified maximum length.
User Response: If you are using your own file, correct
the entry. If you are using the system defaults file,
contact your system programmer.
System Programmer Response: If the problem is in
the system translation defaults, correct the identified
entry.
Source: LANRES
EWXxx2318W Extension entry extension in
defaultname exceeds 3 characters.
Explanation: The specified extension entry in the
translation defaults identified above was incorrect.
Extensions must be less than or equal to 3 characters
in length.
help in finding the cause of the error.

User Response: Determine the cause of the error,
correct, and if necessary reenter the command.
Source: LANRES
EWXxx2323E Error_text returned from read file list.
Explanation: As part of the command processing,
LANRES created a list of the datasets. While reading
from this list an error occurred. The error text describes
the error that occurred.
User Response: Determine the cause of the error
from the error text. If necessary contact your software
support personnel.
Source: LANRES

EWXxx2325W Server File extension file_extension

too long - truncated.
User Response: If you are using your own file, correct

the entry. If you are using the system defaults file,
contact your system programmer.
Explanation: The server file extension given to

LANRES was too long. The file extension is truncated to
3 characters.
System Programmer Response: If the problem is in

the system EWXTRANS default file, correct the
identified entry.
Source: LANRES
Source: LANRES
EWXxx2319W Error_text error returned on read of
dataset dataset
Explanation: This error error_text was returned when
reading from dataset dataset. The dataset opened was
not critical to the success of the command.
EWXxx2326W Server File name file_name too long truncated.

Explanation: The server file name given to LANRES
was too long. The file name is truncated to 8
characters.
User Response: The cause of the error should be

identified in the error text. Correct the problem and if
necessary, reenter the command.
Source: LANRES
Source: LANRES
EWXxx2320W Unable to create directory dirname
DOS Return code dos-return-code
Explanation: While attempting to create a directory on
the NetWare server, an unexpected error condition
occurred. File transfers will continue, but other errors
may occur. The DOS return code given is displayed to
EWXxx2328E Unable to delete dataset - filename

Reason error_text
Explanation: An error occurred while transferring the
file from the NetWare server. As a result, an attempt
was made to clean up and delete the dataset that was
created. However, the error, error_text, occurred while
trying to delete the dataset.
55
User Response: Based on the error text, determine

why the dataset could not be removed. The dataset
may contain incomplete data and should be removed.
Or, if the dataset is EWXLANDS.LISTUT1, then an
attempt was made to erase the dataset that contained
the list of server files. You need to just erase this
dataset.
Source: LANRES

Source: LANRES
EWXxx2329E Option SUBDIR must be specified
when server directory is specified.
Explanation: The NetWare file name given identified a
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
considers a path a directory when it ends with a slash
(/) or a backslash (\).
User Response: Reenter the command, specifying a
file for the server directory, or adding the SUBDIR
option.
Source: LANRES
EWXxx2332E Server File name file_name too long

Explanation: The server file name given to LANRES
was too long. When copying a file from the NetWare
server, server file name must be between 1 and 8
characters.
User Response: Reissue the command, specifying a
valid file name.
Source: LANRES
EWXxx2333E Subdirectory option not allowed to
DOS partitions.
Explanation: A command was issued that requested
copying subdirectories to or from the servers DOS
partition. Subdirectory operations are not supported for
DOS partitions.
User Response: Reissue the command without the
subdirectory option.
EWXxx2330E File filename cannot be created. No

space on device.
Source: LANRES
Explanation: The NetWare server returned and

indication that the volume is full. The file cannot be
allocated.
EWXxx2401I VOLUME NAME
User Response: This condition may only be

temporary. Retry the command at a later time. If the
problem persists, contact the system programmer.
System Programmer Response: The volume may

give a full indication because deleted files have not
been purged. Issue the PURGE command to free up
space. If this does not free sufficient space, add a new
volume segment to the volume.
Source: LANRES
Source: LANRES

EWXxx2402I BLKSIZE
EWXxx2331E Server File extension file_extension

too long
Explanation: The server file extension given to

LANRES was too long. When copying a file from the
NetWare server, the server file extension given must be
3 characters or less.
Source: LANRES

User Response: Reissue the command, specifying a
valid extension.
56
EWXxx2403I BLK USED-(%)

Source: LANRES
EWXxx2404I BLK LEFT
EWXxx2409E The file name or directory specified,

filename, is on a DOS partition.
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
names on a DOS partition.
User Response: Specify a file or directory name that
is not on a DOS partition.
Source: LANRES

EWXxx2410W EWXDS LIST does not display DOS

partition subdirectory information.
Source: LANRES
Explanation: The EWXDS LIST does not support

showing subdirectory information for a DOS partition.
The SUBDIR option is ignored.
EWXxx2405I BLK TOTAL


User Response: Either specify a file name that is not

a DOS partition or find a way to get to the DOS
partition. One way is to DOWN the server.
Source: LANRES
Source: LANRES
EWXxx2411I The two files names are identical.
EWXxx2406I VOLUME MOUNTED - STATISTICS NOT
AVAILABLE
Explanation: The two file names entered are the

same. No request was sent to the NetWare server.


User Response: Determine if the correct file names

were entered. If not, enter the command again with the
correct file names.

Source: LANRES
EWXxx2408E The file specified, fname, is a
directory.
Explanation: The filename that was specified is not a
file, but a directory.

Source: LANRES
EWXxx2412I Successfully received nnn of mmm
files.
Explanation: This message indicates how many of the
files were successfully received from the server.
User Response: Determine the correct filename to be

used for the operation to perform and retry the
operation.
Source: LANRES
Source: LANRES
57
EWXxx2413I Successfully sent nnn of mmm files.

Explanation: This message indicates how many of the
files were successfully sent to the server.
Source: LANRES
EWXxx2414E Dataset dsname not found.
Explanation: The dataset indicated in the error
message was not found. If you were doing an EWXDS
PUT, this could indicate that you specified a partitioned
dataset without a member specified versus a sequential
dataset. If you were doing an EWXDS LOG VIEW, the
log dataset does not exist. If you were doing EWXDS
GET, the PDS/E dataset needs to exist when specifying
a member.
EWXxx2452I No compression was done because

storage was not decreased for host file
filename.
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
EWXxx2453E Error_text error - compression could
not be done.
there was an error when trying to compress data.

System Programmer Response: The cause of the

error is identified in the error text. Correct the problem.
User Response: If you are trying to run an EWXDS

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
viewed. Set logging on by issuing EWXDS LOG ON.
Source: LANRES

Source: LANRES
EWXxx2450I No compression was done because no
algorithms are available.
there are no compression algorithms on the system.
EWXxx2454I No page aligned storage available for

compression dictionary.
there was an error when trying to get page aligned
storage for a compression/expansion dictionary. An
attempt will be made to compress without using a
dictionary.
Source: LANRES

EWXxx2455I No storage available to compress file.
Source: LANRES

there was an error when trying to get storage for
compressing a file.
EWXxx2451E Compressed data could not be

expanded because the needed
algorithm was not available.
Explanation: A file written to the host with the
COMPRESS option could not be retrieved because this
system did not have the needed expansion algorithm.

Source: LANRES
System Action: The PUT function stops.

System Programmer Response: Ensure that host
compression/expansion algorithms are available.
Source: LANRES
58
EWXxx2456E Storage not available to check if

should expand file filename.
Explanation: A file may have been saved on a GET
using the COMPRESS option. Storage needed to
determine if the file was compressed was unavailable.

User Response: Ensure there is sufficient virtual
storage available and reenter the command.
Source: LANRES
EWXxx2461E COMPRESS option invalid when

output is to the display device.
Explanation: The COMPRESS option was specified,
but no output dsname was specified. The output to the
display device would be unreadable.
System Action: GET processing for this file stops.
EWXxx2457E Error expanding compressed

dictionary - error_text.
Explanation: A file written to the host with the
COMPRESS option could not be retrieved because its
dictionary was compressed and could not be expanded.
User Response: Specify a dsname for a file that is to

be compressed, or do not specify the COMPRESS
option if the file is to be displayed.
Source: LANRES

EWXxx3001E User or group already exists.

causing the compression dictionary to not be able to be
expanded.
Explanation: The user or group already exists. Two

causes of this message are:
v Attempting to add an already existing user or group.
v Attempting to rename a user or group to an already
existing user or group.
Source: LANRES
EWXxx2458E Data was compressed using a later
level of code than PUT expansion code
supports.
Explanation: The level of code used when data was
compressed on the GET is newer than the level of code
available to expand the code on the PUT. The code
cannot be expanded.
newest level of the PUT code is available on the
system.
Source: LANRES
If you are using NetWare Version 4.01 or later, this

message may indicate that there is another directory
services object by the same name on the server.
Directory services does not allow objects of different
object types to use the same object name. For example,
you cannot have a user and a print queue named SAM
on the same server.
User Response: Check the spelling of the specified
user or group name. If the spelling is incorrect, correct
it. Reenter the command.
If you are using NetWare Version 4.01 or later, make
sure there is no other object by the same name on the
server.
EWXxx2459I No compression was done because

compression dictionary could not be
built - error_text.

was not used because a compression dictionary could
not be built and an alternate algorithm not requiring a
dictionary was not available.
EWXxx3002E Incorrect user or group name.
Source: LANRES
Explanation: A command was entered specifying a

user or group that could not be found. The use of
special characters could produce this message.


causing the compression dictionary to not be built. Also,
ensure that all host compression/expansion algorithms
are available.

it. Reenter the command.
Source: LANRES

Source: LANRES
59
EWXxx3003E Special characters not allowed in

user or group name.
Explanation: A user or group name cannot contain
spaces or any of the following special characters:
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)
NetWare may also restrict the user or group name from

containing other special characters. This message may
appear if no name is specified.

Source: LANRES
EWXxx3006E Command rejected: Require
Password is set to no.
Explanation: A command was entered which requires
the Require Password field on the Account
Restrictions screen of SYSCON to be set to YES.
If you are using NetWare Version 4.01 or later, the
Require Password field can be found in the Password
Restrictions screen of the NETADMIN or NWADMIN
utility.
User Response: Enter the EWXADMIN REQPASSW
command and specify the YES parameter.
Note: Not all commands produce this message when a

user or group name contains one of the above
characters. Some commands will return message
3002E Incorrect user or group name.

EWXxx3007E Command rejected: Allow User To

Change Password is set to no.
User Response: Reenter the command with a valid

name.

the Allow User To Change Password field in the
Account Restrictions screen of SYSCON to be set to
YES.

Source: LANRES
EWXxx3004E User or group does not exist.
user or group that could not be found.
it. Reenter the command with a valid name.
Source: LANRES
EWXxx3005E Volume does not exist.
volume that could not be found.
volume name. If the spelling is incorrect, correct it. If
you are unsure of the spelling, use the VOLUMES
command at the NetWare server console to view the list
of volumes mounted on the server. Reenter the
command with a valid volume name.
60
Source: LANRES

Allow User To Change Password field can be found in
the Password Restrictions screen of the NETADMIN or
NWADMIN utility.
User Response: Ask your system programmer or
someone who manages your account to change your
user IDs Allow User To Change Password field to
YES. If you want your password changed, your system
programmer or someone who manages your account
can change it for you.
System Programmer Response: Load the NetWare
SYSCON utility at a client workstation. Select Account
Restrictions on the User Information panel. Change the
Allow User to Change Password field in SYSCON to
YES. If the user IDs password needs to be changed,
you may use the SYSCON utility or enter the LANRES
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
Allow User To Change Password field in the
Password Restrictions screen.
Source: LANRES
EWXxx3008E Command rejected: Force Periodic

Password Changes is set to no.
the Force Periodic Password Changes field in the
Account Restrictions screen of SYSCON to be set to
YES.
Force Periodic Password Changes field can be found
in the Password Restrictions screen of the NETADMIN
or NWADMIN utility.
User Response: Enter the following command with
the interval parameter set to a suitable non-zero value
(SYSCON uses a default of 40):
v Enter the EWXADMIN PWEXPINT command.
Source: LANRES
EWXxx3009E Print queue or print server already
exists.
because the print queue or print server already exists.
Two causes of this message are:
v Attempting to add an already existing print queue or
print server
v Attempting to rename a print queue or print server to
an already existing print queue or print server.
If you are using NetWare Version 4.01 or later, this
message may indicate that there is another directory
services object by the same name on the server.
Directory services does not allow objects of different
object types to use the same object name. For example,
you cannot have a user and a print queue named SAM
on the same server.
print queue or print server name. If the spelling is
incorrect, correct it. Reenter the command.
If you are using NetWare Version 4.01 or later, make
sure there is no other object with the same name on the
server.

Source: LANRES
EWXxx3011E Special characters not allowed in
print queue or print server name.
Explanation: A print queue or print server name
cannot contain spaces or any of the following special
characters:
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)
NetWare may also restrict the print queue or print

server name from containing other special characters.
This message may appear if no name is specified.
print queue or print server name contains one of
the above characters. Some commands will
return message 3010E Incorrect print queue or
print server name.
User Response: Examine the specified print queue or
print queue name. If the name contains any of the
special characters, remove them. Reenter the command
with a valid print queue or print server name.
Source: LANRES
EWXxx3012E Print queue or print server does not
exist.
print queue or print server that could not be found.
Source: LANRES

EWXxx3010E Incorrect print queue or print server

name.


print queue or print server that could not be found.

Source: LANRES
61
EWXxx3013E Print queue not deleted; print jobs

still present.
Explanation: The command to delete the print queue
was unsuccessful because print jobs were still present
in the print queue.
User Response: If you want to delete the print queue
regardless of the existing job count, reenter the
command with the FORCE parameter.
Source: LANRES
EWXxx3014E Directory could not be created.
Explanation: The attempt to create a directory was
unsuccessful. The directory path for the directory being
created may not exist.
User Response: Connect to the distribution function
and enter the following command to determine the
cause of the error:
v Enter the EWXDS MKDIR command.
Source: LANRES
EWXxx3015E Specified file(s) or directory could
not be removed.
Explanation: The attempt to remove a file or files was
unsuccessful. Probable causes are:
v Subdirectories are present
v Delete inhibit flags set in the directory
and enter the following commands to determine the
cause of the error:
v Enter the EWXDS DELETE and EWXDS RMDIR
commands.
Source: LANRES
EWXxx3016E The path indicated is a directory, not
a path to a file.
Explanation: The command attempted to remove one
or more files but determined that the specified path
identified a directory only.
62
User Response: Correct the path name to specify the

desired file to remove. Reenter the command.
Source: LANRES
EWXxx3017E Directory could not be removed.
Explanation: The attempt to remove a directory was
unsuccessful. The most likely cause is that the directory
is not empty.
and enter the following command to determine the
cause of the error:
v Enter the EWXDS RMDIR command.
Source: LANRES
EWXxx3018E Command rejected: Command
chaining cannot be nested.
Explanation: If you enter a EWXADMIN BEGINCC
command to begin command chaining, you must enter a
EWXADMIN ENDCC or EWXADMIN RESTSYS
command to stop command chaining before you can
enter a second EWXADMIN BEGINCC command.
User Response: Change the command sequence.
Source: LANRES
EWXxx3019E Administration command name was
unsuccessful with internal error code
xxx nnn.
processing the administration command name. The
error code returned from the NLM is displayed. The
internal error code has two parts, the LANRES error
code xxx and the NetWare error code nnn.
User Response: Notify your system programmer of
the internal error code.
System Programmer Response: Look up the
NetWare error code nnn in the NetWare System
Messages book. The LANRES error code is only used
by IBM service.
If the NetWare error code is not sufficient to indicate the
problem, enter the following sequence of commands
and perform the indicated actions:
1. Enter EWXADMIN DEBUG ON. This places the

administration function in trace mode.
2. Run the command sequence that caused the error
again. The assumption here is that the error is
repeatable.
3. Enter EWXADMIN DISPDB. This displays the trace
information on the host terminal screen and also
writes it to a trace file. The LANRES trace file is
prefix.EWXADMIN.DEBUGMSG.
4. Enter EWXADMIN DEBUG OFF. This returns the
administration function to normal mode.
5. Examine the trace file for problem determination and
fault isolation.
Source: LANRES
chaining is not active.
EWXxx3023E Command rejected: Bindery cannot

be restored during command chaining.
Explanation: The EWXADMIN RESTBIND command
cannot be used while a EWXADMIN BEGINCC
command is in progress. If a EWXADMIN RESTBIND
command is processed, the bindery files saved during
the start of command chaining would be restored. In this
case, any bindery modifications after the EWXADMIN
BEGINCC command and prior to the EWXADMIN
RESTBIND command would be lost.
Source: LANRES
Explanation: The EWXADMIN ENDCC command

cannot be used unless a EWXADMIN BEGINCC
command is in progress.
EWXxx3024E Login script file exceeds the limit of

4000 bytes.

Explanation: The command cannot process login

script files longer than 4000 bytes.


Source: LANRES
chaining is not active.
Explanation: The EWXADMIN RESTSYS command
cannot be used unless a EWXADMIN BEGINCC
command is in progress.
Source: LANRES
EWXxx3022E Command rejected: Bindery cannot
be saved during command chaining.
Explanation: The EWXADMIN SAVEBIND command
cannot be used while a EWXADMIN BEGINCC
command is in progress. If a EWXADMIN SAVEBIND
command is processed, the bindery files saved during
the start of command chaining would be overlaid. In this
case, the EWXADMIN RESTSYS command would not
be able to restore the originally saved bindery files.
User Response: You must use the distribution

function to copy the login script file to the server. For
example, assume there is a user named BIGUSER and
a login script file on the host named
prefix.BIGLOGIN.SCRIPT is longer than 4000 bytes.
Enter the following sequence of commands to install the
file on the server:
1. While still attached to the administration function,
enter:
EWXADMIN USERINFO BIGUSER SYS
BIGUSERs internal ID is returned along with other
information. Assume the internal ID returned is
1F000037.
2. Use the EWXCONN DROP command to drop the
connection to the administration function and the
EWXCONN LINK command to connect to the
3. If this system is using DOS as an operating system,
enter:
EWXDS PUT 'prefix.BIGLOGIN.SCRIPT'
SYS:\MAIL\1F000037\LOGIN (REPLACE
If this system is using OS/2 as an operating system,

enter:
EWXDS PUT 'prefix.BIGLOGIN.SCRIPT'
SYS:\MAIL\1F000037\LOGIN.OS2 (REPLACE

Source: LANRES

Source: LANRES
63
EWXxx3027E Debug facility in use on target server.

Explanation: The debug facility is already in use by
another user on the target server. You must wait for that
user to stop use of the debug facility before you can
use it.
User Response: Wait and retry the operation.
System Programmer Response: Tell the user of the
debug facility to stop the debug facility by entering the
following command:
v Enter:
EWXADMIN DEBUG OFF
Source: LANRES
EWXxx3028E Command rejected: Debug mode is
off.
Explanation: This command requires that debug
mode be enabled.
User Response: Enable the debug facility with the
following command:
v Enter:
EWXADMIN DEBUG ON
You must have trustee rights to LANADME.DBG and
LANADMO.DBG in the SYS:\SYSTEM\directory to use
the debug function. Reenter the unsuccessful
command.
Source: LANRES
EWXxx3029E Unable to open debug file.
Explanation: The debug file could not be opened on
the server. This is usually because the user has
insufficient trustee rights or the operating system is
unable to open the file (for example, if it is out of disk
space).
System Action: Command processing ends. Debug
mode is not enabled.
System Programmer Response: If the user should
be able to use the debug facility, give the user trustee
rights to LANADME.DBG and LANADMO.DBG in
SYS:\SYSTEM\.
Source: LANRES
EWXxx3030E Unable to open bindery information

file.
Explanation: The bindery information file could not be
opened on the server. This is usually because the user
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.
System Programmer Response: If the user should
be able to enter the query bindery command, give the
user trustee rights to BINDERY.LST in SYS:\SYSTEM\.
Source: LANRES
EWXxx3031E Current password not entered or
incorrect.
Explanation: A password in the correct format must
be supplied. in the format required.
User Response: Use the keyword NULL for the
password if you are trying to assign a null password
(which means no password) to a user. Otherwise, retry
the command with a valid password.
Source: LANRES
EWXxx3032E Unable to close debug file.
Explanation: The system could not close the debug
file. This might happen if you lost trustee rights to the
file (for example, someone removed them) before you
disabled the debug facility.
System Programmer Response: Connect to the
administration function as the SUPERVISOR and enter
the following command:
v Enter:
EWXADMIN DEBUG OFF
Source: LANRES
EWXxx3033E Command rejected: New password
duplicated current or previous
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
64
password must be different from the eight previous

passwords.


User Response: Check the spelling of the user or

group name specified on the command line. If the
spelling is correct, you may have entered the command
previously. If the spelling is incorrect, correct it. Reenter
the command.
User Response: Reenter the command with a new

password.
Source: LANRES
EWXxx3034E Command rejected: SUPERVISOR or
equivalent authority required.
Explanation: The attempted operation requires that
the user be the NetWare SUPERVISOR or have
security equivalence to SUPERVISOR.
User Response: Ask a user with SUPERVISOR
authority to perform the action for you, or to assign
SUPERVISOR security equivalence to your user ID.
System Programmer Response: If required, assign
SUPERVISOR security equivalence to the user.
Source: LANRES
EWXxx3035E Command rejected: Target server
busy command chaining.
Explanation: The function you requested cannot be
performed at this time because another user has begun
command chaining operations on the target server. You
must wait until that user finishes and then retry the
command.
User Response: Wait and retry the operation.
System Programmer Response: Inform the user
performing command chaining to stop it by entering the
following command:
v Enter:
EWXADMIN ENDCC

Source: LANRES
EWXxx3037E Incorrect path specified, or trustee
rights to the path required.
path that was incorrect or nonexistent, or the proper
trustee rights are required for the path before the
command can be processed.
User Response: Verify that the correct volume name
and path were entered correctly on the command line. If
the path is correct and you need trustee rights for the
path, ask your system programmer to assign the trustee
rights to you.
System Programmer Response: Assign trustee
rights, if required, to the user for the path specified on
the command line.
Source: LANRES
EWXxx3038E Member does not exist.
Explanation: The command tried to remove an
existing user or group as a member when the user or
group is not a member.
group name specified on the command line. If the
the command.
or
Source: LANRES
EWXADMIN RESTSYS
Source: LANRES
EWXxx3036E Member already exists.
Explanation: The command was unsuccessful. Two
causes are:
v Attempting to add a user to a group when the user is
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
EWXxx3039E The password is shorter than the

minimum password length or greater
than 127 characters.
Explanation: The user IDs password must have a
length greater than or equal to the value of the
Minimum Password Length field, but not greater than
127 characters long.
65
User Response: Specify a password with a shorter or

longer length. You may use the NetWare SYSCON
utility or enter the EWXADMIN USERINFO command to view
the minimum password length for your user ID.
Source: LANRES
EWXxx3040W Current password was not required
and was not used.
Explanation: A command was entered to change a
user IDs password, and the user issuing the command
has SUPERVISOR authority or manages the specified
user ID. A SUPERVISOR or the user IDs manager
need not specify the current password when changing
the user IDs password.
System Action: The command continues.
User Response: Verify that you have changed the
correct user IDs password.
Source: LANRES
EWXxx3041W Print queue created but print server
name contains special characters.
Explanation: The command tried to create a print
queue and assign a print server to it. The print queue
was created successfully, but the command was
unsuccessful while attempting to assign a print server to
the print queue. A print server name cannot contain
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)

containing other special characters. This message may
appear if no name is specified.
print queue or print server name contains one of
the above characters.
System Action: The print queue is created but the
print server is not assigned to it.
User Response: Examine the specified print server
name. If the name contains any of the special
characters listed, remove them. Use the EWXADMIN
ASQSERV command to assign the correct print server to
the new print queue.
66

Source: LANRES
EWXxx3042W Print queue created but the print
server does not exist.
the print queue. The specified print server name could
not be found. Use the NetWare PCONSOLE utility to
verify that the print server exists.
System Action: The print queue is created but the
print server name. If the spelling is incorrect, correct it.
Use the EWXADMIN ASQSERV command to assign the
correct print server to the new print queue.
Source: LANRES
EWXxx3043W Print queue created but print server
not assigned to it.
the print queue. This error message may appear when
the server is out of memory or when the bindery is
locked.
System Action: The print queue is created, but the
User Response: Use the EWXADMIN ASQSERV command
to assign the print server to the new print queue. If the
command fails, notify your system programmer.
System Programmer Response: Use the NetWare
PCONSOLE utility to verify that the print server exists.
Assign the print server to the print queue from
PCONSOLE.
Source: LANRES
EWXxx3044E Security equivalence does not exist.
Explanation: The command tried to withdraw a
security equivalence from a user, but the user did not
possess that security equivalence.
group name entered on the command line. If the
the command with the correct information.

Source: LANRES
print queue name. If the spelling is incorrect, correct it.

Reenter the command.
EWXxx3045E Command rejected: Require

Password is set to yes. No null
passwords.
the Require Password field in the Account Restrictions
screen of SYSCON to be set to NO.
User Response: Enter the EWXADMIN REQPASSW
command and specify the YES parameter.
Source: LANRES
EWXxx3046W Print queue renamed but print server
was incorrect or does not exist.
Explanation: The command tried to rename a print
queue and inform the LAN-to-host print server of the
change. The print queue was renamed successfully, but
the specified print server name was incorrect or could
not be found. Use the NetWare PCONSOLE utility to
verify that the print server exists. A print server name
cannot contain spaces or any of the following special
characters:
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)

System Action: The print queue is renamed and the
LAN-to-host print server is not informed.
Source: LANRES
EWXxx3047E Print queue does not exist.
Explanation: The specified print queue name could
not be found.
Source: LANRES
EWXxx3048E Special characters are not allowed in
print queue name.
Explanation: A print queue name cannot contain
/
\
:
;
,
*
?
(slash)
(backslash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)
NetWare may also restrict the print queue name from

User Response: Examine the specified print queue
name. If the name contains any of the special
characters, remove them. Reenter the command.
Source: LANRES
EWXxx3049E Command rejected: Another QUERY
BINDERY command is being
processed.
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
QUERY BINDERY command can be entered by another
user.
System Action: Command processing ends. The first
EWXADMIN QUERY BINDERY command will continue to be
processed.
User Response: Wait for the first EWXADMIN QUERY
BINDERY command to be finished before reentering your
EWXADMIN QUERY BINDERY command.
Source: LANRES
EWXxx3050E Print server already assigned to print
queue.
Explanation: The print server has already been
assigned to service the print queue.
67

EWXxx3054E The NFS ID specified already exists.
User Response: Check the spelling of the print server

and print queue entered on the command line. If the
spelling is incorrect, correct it. Reenter the command.
Explanation: The attempt to add an NFS ID to the

NFSUSERS or NFSGROUP file in the SYS:\ETC\
directory was unsuccessful because the specified ID
already exists in the file.

Source: LANRES

EWXxx3051E Print server not servicing print

queue.
User Response: Be sure that the NFS ID specified is

correct. If it is, delete the NFS ID and then add it with
the new NetWare ID.
Explanation: The print server cannot be removed from

the print queue because it is not servicing the print
queue.

Source: LANRES
EWXxx3055E Unable to unlock the filename file that
is locked.
User Response: Check the spelling of the print server

and print queue entered on the command line. If the
spelling is incorrect, correct it. Reenter the command.
Explanation: The attempt to unlock the specified file

in the SYS:\ETC\ directory was unsuccessful.

Source: LANRES
EWXxx3052E Unable to open the filename file.
Explanation: The attempt to open the specified file in
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.
User Response: Determine which of the conditions
mentioned in the explanation exist. Correct the problem
Source: LANRES
EWXxx3053E Unable to create a temporary file.
Explanation: The attempt to create a temporary file in
Source: LANRES
User Response: Determine why the file is locked. It is

possible that someone is using it. Unlock the file and
Source: LANRES
EWXxx3056E The server is out of memory to lock
the filename file.
Explanation: The attempt to lock the specified file in
the SYS:\ETC\ directory was unsuccessful because the
server ran out of memory.
User Response: Make more memory available and
Source: LANRES
EWXxx3057E There was a time-out trying to lock
the filename file.
the SYS:\ETC\ directory was unsuccessful. The file is
already locked.
User Response: Determine why the file is locked. It is
possible that someone is using it. Unlock the file and
68
Source: LANRES
EWXxx3058E There was an error trying to lock the
filename file.
the SYS:\ETC\ directory was unsuccessful.
User Response: Determine why the file cannot be
locked. Correct the problem and reenter the command.
Source: LANRES
EWXxx3062E Unable to rename the temporary file

to filename.
Explanation: The attempt to rename a temporary file
in the SYS:\ETC\ directory to the specified file name
was unsuccessful.
User Response: The temporary file still exists in the
SYS:\ETC\ directory. Rename the temporary file to
NFSUSERS if the request is to work with an NFS user,
otherwise, rename the temporary file to NFSGROUP.
Source: LANRES
EWXxx3059E The NFS ID must be an integer

between 0 and (2**32-1).
Explanation: An incorrect NFS ID was specified. The
NFS ID value must be from 0 to (2**32-1).
EWXxx3063E The NFS ID did not exist in the

filename file.

Explanation: The request to delete an NFS ID from

the specified file in the SYS:\ETC\ directory was
unsuccessful because the NFS ID does not exist in the
file.
User Response: Change the NFS ID to a value from

0 to (2**32-1) and reenter the command.

User Response: Make sure the correct NFS ID was

entered.
Source: LANRES

EWXxx3060E The NetWare ID must be less than or
equal to 47 characters in length.
Source: LANRES
Explanation: The NetWare ID specified was longer

than 47 characters.
EWXxx3064E Unable to create the filename file.

User Response: Change to a correct NetWare ID and
Source: LANRES
EWXxx3061E Unable to open the filename.BKP file.
Explanation: The attempt to open the backup file in
Source: LANRES
Explanation: The attempt to create the specified file in

the SYS:\ETC\ directory was unsuccessful. The
SYS:\ETC\ directory may not exist, the user may not
have trustee rights to SYS:\ETC\, or the NetWare for
NFS product may not be installed on the server.
User Response: Make sure the SYS:\ETC\ directory
exists or that you have the trustee rights to the
SYS:\ETC\ directory. If the directory does not exist,
either create the directory or install the NetWare for
NFS product on your server.
Source: LANRES
EWXxx3065E The filename file did not exist to
delete the NFS ID.
Explanation: The attempt to delete an NFS user or
group was unsuccessful. The specified file does not
exist in the SYS:\ETC\ directory. It is possible that
NetWare for NFS may not be installed on the server.
69

User Response: There is no NFS ID to delete.
NetWare for NFS may need to be installed.
Source: LANRES
EWXxx3066E Directory cannot be removed.
Explanation: You attempted to remove a directory on
the NetWare server but the attempt failed. The failure
may be caused by:
v Not all files have been deleted from the directory
v Subdirectories exist inside that directory
v The DeleteInhibit flag was set on for that directory.
System Action: Command processing ends. Files
may have been removed from the directory but the
directory remains.
User Response: Check to see if any of the reasons
for failure listed above applies. Correct the situation and
use the EWXADMIN RMDIR command to remove the
directory.
Source: LANRES
EWXxx3067E This command is not supported on a
NetWare Version 4.01 or later server.
Explanation: Certain LANRES administration
commands cannot be entered when you are logged-in
to a NetWare Version 4.01 or later server.
The new NetWare Version 4.01 architecture does not
support the following administration commands:
v EWXADMIN BEGINCC
v EWXADMIN ENDCC
v EWXADMIN RESTBIND
v EWXADMIN RESTSYS
v EWXADMIN SAVEBIND
There are no substitutes for these unsupported
administration commands.
authority to create and configure the print queue or print

server. Ideally, you should have security equivalence to
the SUPERVISOR user ID to enter this command.
User Response: Ask the system administrator to give
you the proper authority to create the print queue or
print server, or to create the print queue or print server
for you.
System Programmer Response: If appropriate,
create the print queue or print server, or grant the
proper authority to the user. To grant the proper
authority, you may give the user security equivalence to
the SUPERVISOR user ID or to another user ID with
the authority to create print queues or print servers.
Source: LANRES
EWXxx3069E Cannot configure print queue or print
server, and cannot delete it.
Explanation: Your attempt to create a new print queue
or print server succeeded but you did not have sufficient
authority to configure the print queue or print server.
The command then tried to delete the print queue or
print server but was unable to delete it. The system
administrator must grant you the authority to configure
the print queue or print server. Ideally, you should have
security equivalence to the SUPERVISOR user ID to
enter this command.
System Action: Command processing ends. The print
queue or print server was created but not properly
configured.
User Response: Ask the system administrator to give
you the proper authority to configure the print queue or
print server, or to configure the print queue or print
server for you.
System Programmer Response: If appropriate,
configure the print queue or print server, or grant the
proper authority to the user. To grant the proper
authority, you may give the user security equivalence to
the SUPERVISOR user ID or to another user ID with
the authority to configure print queues or print servers.

Source: LANRES
User Response: Enter a supported command.
EWXxx3070E Permission denied by NetWare

server. Insufficient trustee rights.

Source: LANRES
Explanation: You do not have sufficient authority to

perform the operation. The proper file or directory
trustee rights may be required.
EWXxx3068E Insufficient rights to create and

configure print queue or print server.

Explanation: Your attempt to create a new print queue

or print server failed because you did not have sufficient
authority to create or configure the print queue or print
server. The system administrator must grant you the
User Response: Obtain the appropriate trustee rights

to perform the operation.
70
the proper trustee rights to the user.
Source: LANRES
Source: LANRES
EWXxx3071W Name has no trustee rights or you

are not authorized for them.
EWXxx3075W Lines in file filename may have been

truncated.
Explanation: You tried to query the file and directory

trustee rights assigned to a user ID or a group ID, but
the trustee rights information cannot be displayed. This
user or group has no trustee rights, or you do not have
sufficient authority over the user or group to see their
trustee rights.
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
been truncated.
System Action: The command completes and this

warning message is displayed on the screen or written
to a file.

User Response: Set up a file with the correct record
length and reenter the command.
User Response: If necessary, obtain the appropriate

authority to perform the operation.
Source: LANRES

the proper authority to the user.
EWXxx3076E Incorrect data set name dsname

specified.
Source: LANRES
Explanation: An incorrect data set name was

specified in the command.
EWXxx3072E Parameter parameter must be USER

or GROUP.

Explanation: The command syntax requires that the

indicated parameter be either the keyword USER or the
keyword GROUP.
User Response: Correct the data set name and


Source: LANRES

command.
EWXxx3077E Incorrect date value date specified.
Source: LANRES
Explanation: The date value must be in the format

defined for your system, and be a date that NetWare
accepts.
EWXxx3073E The full name entered is more than

127 characters.
The following restrictions on the year also applies. The

year must be in the range 81 to 99 (1981 to 1999) or in
the range 00 to 80 (2000 to 2080).
Explanation: The full name must be less than or

equal to 127 characters in length.


User Response: Correct the date and reenter the

command.

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
equivalent to himself and you cannot make a user not
security equivalent to himself.
Explanation: This is a message used to display

information requested by the user.

71
User Response: Verify the two user names in the

command. If the user names are incorrect, correct them
EWXxx3082E Cannot remove a non-empty

directory.
Explanation: A directory which contains files or

subdirectories cannot be deleted.
Source: LANRES
EWXxx3079E Incorrect path name path specified.
Explanation: A NetWare path name consists of a
correct volume name. a colon, and the file or directory
name within the volume. The file or directory name is
usually optional.

User Response: Delete all files and subdirectories
from the directory. Reenter the command.
Source: LANRES

EWXxx3083E File or directory already exists.
User Response: Correct the path name and reenter

the command.
Explanation: The file or directory already exists and

cannot be overwritten.

Source: LANRES
EWXxx3080E File or directory is read-only.
because it attempted to write to, copy to, rename, or
delete a read-only file or directory.
User Response: Change the file or directorys
read-only attribute and reenter the command. The file or
directorys attributes may be changed with a NetWare
utility, such as FLAG or FLAGDIR.

different file or directory name.
Source: LANRES
EWXxx3084E Incorrect directory name specified.
Explanation: The command to create a directory
failed. The volume was not mounted, the directory name
was misspelled, part of the directory path does not
exist, or incomplete identification was provided.
Source: LANRES
User Response: Reenter the command with a correct

directory name.
EWXxx3081E File or directory not found.
Explanation: The specified file or directory was not

found. The file or directory does not reside on the
volume, the volume was not mounted, the file or
directory name was misspelled, or incomplete
identification was provided.
Source: LANRES

User Response: Verify that the file or directory name
was spelled correctly, and that the volume was
mounted.
Source: LANRES
EWXxx3085E The DS option is not supported on a

NetWare Version 3.x server.
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
option is accepted only when you are logged-in to a
NetWare Version 4.01 or later server.
User Response: Change the operating system
parameter to DOS or OS2 and reenter the command.
Source: LANRES
72
EWXxx3086E Cannot find Directory Services

functions on the NetWare server.
Explanation: The command requires Directory
Services functions on the NetWare server in order to
perform its task, but these functions are not available.
There are several probable causes for this problem: 1)
you are logged-in to a NetWare Version 3.x server; 2)
you are logged-in to a NetWare Version 4.x server but
the administration NLM, EWXADMIN.NLM, is running on
a NetWare Version 3.x server; or 3) the NetWare
DSAPI.NLM is not loaded on the server. Directory
Services functions are only available when NetWares
DSAPI.NLM is loaded on the server.
Source: LANRES
EWXxx3089I You are logged on tree . . . . . . . . .
tree_name
Explanation: This is the NetWare Directory Services
tree name that you are logged in to.
Source: LANRES

EWXxx3090I Your current context . . . . . . . . . .

context_name
User Response: Make sure you are connected to and

logged-in to a NetWare Version 4.x server. If you are
running on a NetWare Version 4.x server, ask your
system programmer to load DSAPI.NLM on the server.
Explanation: This is the current context the user is

logged into the NetWare Directory Services.
System Programmer Response: Load DSAPI.NLM

on the server.
Source: LANRES
Source: LANRES
EWXxx3087E Cannot login with Directory Services.
EWXxx3091I You have logged-in under context

context as user user.
Explanation: The administration function attempted to

login with your user ID through Directory Services to
use Directory Services functions but the attempt failed.
The problem is probably caused by using the
SUPERVISOR user ID on a NetWare Version 4.x
server.
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
NWADMIN and make it security equivalent to the
ADMIN user ID.
Explanation: You are now logged-in as user user on

the NetWare server under context.
Source: LANRES
EWXxx3092E Invalid syntax. Check the syntax in
context field.
Explanation: An invalid syntax was entered - most
likely the context field is entered wrong.
Source: LANRES

EWXxx3088E EWXADMIN PROGRAM CANNOT BE

FOUND.
User Response: Check the syntax and reenter.
Explanation: You have invoked the EWXADMIN

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
found.
User Response: Make sure you have access to the
EWXADMIN program.

Source: LANRES
EWXxx3093E Object objname not found.
Explanation: The specified object was not found.
Either the object does not reside in the context
specified, the object name was misspelled or incomplete
identification was provided to cause the appropriate
path to be searched.
73

User Response: To verify the object exists, enter the
command with correct name or syntax.
but neither the user configuration file nor the system

configuration file can be found. Without these files, the
connection to the NetWare server cannot be
established. The user configuration file is:
v EWXCONFG.LINKUSER
Source: LANRES
The system configuration file is:

v EWXCONFG.LINK
EWXxx3094E Login unsuccessful: User tried to

login to NDS.

Explanation: The file server or user ID specified on

the command tried to login to NetWare Directory
Services. NetWare Directory services not installed.
User Response: Notify your system programmer if

you need access to the system configuration file or you
may create your own user configuration file. You may
also connect to the NetWare server by specifying all the
required values on the command line.

User Response: Use the proper syntax to login.

has access to the system configuration file that was
customized during installation.
Source: LANRES
Source: LANRES
EWXxx3095E Not logged in to NDS. Reenter the
command with correct syntax.
EWXxx4002E Parameter parameter not in the form

server/user or NDS format.
Explanation: The syntax used in the command is for

NetWare Directory Services. Use the non-NDS syntax
for the command.
Explanation: The indicated parameter is not correct. It

must be in the form server/user to specify the NetWare
server and user ID to login to. In case logging in to
NDS, use NDS format of the parameter.


User Response: Use the proper syntax of the

command Reenter the command.

command.
Source: LANRES
Source: LANRES
EWXxx3096E The two context names context1 and

context2 must be the same.
EWXxx4003E Login was unsuccessful (server error

code=nn).
Explanation: The attempt to rename/swap the

directory or file was unsuccessful, because the
files/directory to be renamed must reside in the same
context.

trying to login to the NetWare server.

User Response: Call your system programmer with

the server error code.
User Response: Enter the same context name for

both directories or files and reenter the command.
System Programmer Response: Look up the server

error code nn in the NetWare System Messages book.
Correct the problem which caused the server error
code.

Source: LANRES

Source: LANRES
EWXxx4001E Cannot find user or system
configuration file to establish
connection.
EWXxx4004I Logging of LANRES messages is on.
Explanation: Not all the required values were

specified on the command line. The command tried to
use the configuration files to fill in the missing values
74
Explanation: Messages from LANRES programs will

be recorded in a log file.
Source: LANRES
v EWXCOMM.INI file
v EWXxxxx.NPW file
v Specified by the PWIN and PWOUT parameters
when the NLMs were loaded
EWXxx4005I Logging of LANRES messages is off.
You may have to ask the system programmer for the

NetWare server passwords.

Explanation: Messages from LANRES programs will

not be recorded in a log file.
Source: LANRES
EWXxx4006E Command request to the host-to-LAN
print function is too long.
Explanation: The request from the EWXCONN PRINT
or EWXCONN QUERY PRINT command cannot be sent
to the host-to-LAN print server on the host. The
command that was entered is longer than the maximum
length for a valid EWXCONN PRINT or EWXCONN
QUERY PRINT command.
User Response: Check the command for misspellings
or duplicate values. Correct the error and reenter the
command.
Source: LANRES
EWXxx4007E Cannot connect to the function
function. Password exchange was
unsuccessful.
Explanation: The LANRES functions on the host and
the NetWare server perform a password exchange to
verify that both sides are authorized to connect to each
other. This password exchange was unsuccessful. The
error indicates that the PWIN password value on the
host does not match the PWOUT password value on
the NetWare server.
User Response: Make sure that you are using the
correct passwords. On the host, the passwords may be
found in one of the following places (xxxx may be
ADMIN, DISK, DIST, HLPRT, or LHPRT):
System Programmer Response: Give the user the

NetWare server passwords for the function to be
connected to.
Source: LANRES
EWXxx4009E Connection to the NetWare server
will be dropped.
Explanation: An error has occurred which caused the
connection to the NetWare server to be dropped.
Additional error messages may be displayed to help
determine the problem.
User Response: If additional error messages are
available, use them to determine the problem. Correct
the problem and reenter the command.
Source: LANRES
function on the NetWare server.
Explanation: No connection can be made to the
function function on the NetWare server. Probable
causes are:
v You specified an incorrect or unavailable connectivity
path
v You specified an incorrect server name or user name
for the administration or distribution function and a
matching line cannot be found in the configuration
files.
Other error messages may be displayed to indicate the
cause of the problem.
User Response: If other error messages were
displayed, use them to find and correct the problem. If
possible, specify all the parameters and options
required by the command so the command will not have
to use the configuration files.
v EWXxxxx.MVSPW file
v Specified by the PWIN and PWOUT options on the

EWXCONN LINK command
Source: LANRES
On the NetWare server, the passwords may be found in

one of the following places (xxxx may be ADMIN, DISK,
DIST, HLPRT, or LHPRT):
75
EWXxx4011E Cannot connect to the NetWare

server with the nickname nickname.
EWXxx4015E No matching line in configuration

data sets to establish connection.
Explanation: No connection can be made to the

NetWare server with the specified nickname. Probable
causes are:
Explanation: All the required values were not

specified on the command line. The command tried to
use the configuration data sets to fill in the missing
values but cannot find a matching line in the
configuration data sets. For the administration and
distribution functions, the command tried to match the
nickname, server name, user name, protocol, and target
values. For the disk, host-to-LAN print, and LAN-to-host
print functions, the command tried to match the
nickname, protocol, and target values. Without these
missing values, the connection to the NetWare server
cannot be established. The possible configuration data
sets are the data sets allocated to the EWXCONFG
DDname, the EWXCONFG.LINK data set, and the data
set defined by the Link_Connection_Configuration
option of the host configuration options data set.
v You specified an incorrect or unavailable connectivity

path
v You specified an incorrect server name or user name
for the administration or distribution function and a
matching line cannot be found in the configuration
files
v You specified an incorrect nickname and a matching
line cannot be found in the configuration files
Other error messages may be displayed to indicate
what the problem was.
User Response: If other error messages were
displayed, use them to find and correct the problem. If
possible, specify all the parameters and options
required by the command so the command will not have
to use the configuration files.
Source: LANRES
EWXxx4012I Connection established to the function
Explanation: You are now connected to the function
System Action: Connection made to the NetWare
server.
Source: LANRES
EWXxx4013E Cannot read login password. Error
Explanation: The user was prompted to type in a
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.
Source: LANRES
76

User Response: Notify your system programmer if
you need access to the system configuration data set.
You may create your own configuration data set. You
may also connect to the NetWare server by specifying
all the required values on the command line.
has access to the configuration data set that was
customized during installation.
Source: LANRES
EWXxx4016E Login unsuccessful: Unknown file
server or user ID.
Explanation: The file server or user ID specified on
the command was incorrect or nonexistent.
User Response: Check the spelling of the file server
name and user ID. If the spelling is incorrect, correct it.
Source: LANRES
EWXxx4017E Login unsuccessful: Access to
server denied.
Explanation: The most probable causes for getting
this message are:
v The supplied password was incorrect.
v The user account has been locked out of the server
by the NetWare Intruder Detection/Lockout feature.
v The user tried to login when they were not allowed
access to the server.
v The administrator has disabled logins by entering the

DISABLE LOGIN command at the server console.
Source: LANRES

EWXxx4022E The raddr operand must be the EVEN

address of the subchannel pair.

correct user ID and password. If the error persists, ask
your system programmer to grant you access to the
server.
Explanation: When using the CHANNEL or MMC

protocol, the radder operand on the EWXCONN LINK
command was incorrectly specified. (It must be a threeor 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
to grant the user access to the server during the
required time period. Enter the ENABLE LOGIN command
on the server console to allow users to login to the
server.
Source: LANRES

User Response: Reenter the EWXCONN LINK
command with the correct subchannel address.
Source: LANRES
EWXxx4018I You have logged-in to server server as

user user.
Explanation: You are now logged-in as user user on
the NetWare server server.
Source: LANRES
EWXxx4020E Symdestname symdestname is not a
valid symbolic destination name.
Explanation: When using the APPC protocol, the
target operand specified an incorrect symbolic
destination name. It must be an alphanumeric string of
up to 8 characters.
command.
Source: LANRES
EWXxx4021E Raddr raddr is not a valid real
subchannel address.
Explanation: When using the CHANNEL or MMC
protocol, the radder operand on the EWXCONN LINK
command was incorrectly specified. (It must be a threeor four-character hexadecimal number specifying the
even subchannel address of a read/write address pair.)
EWXxx4024E Login unsuccessful: Maximum

number of concurrent connections
exceeded.
Explanation: NetWare has placed a restriction on the
number of stations that the user may login to at one
time. The login attempt exceeded this number.
User Response: Logout of another station before
reentering the command to login to the server. You can
also ask your system programmer to raise the maximum
number of concurrent connections for your user ID.
System Programmer Response: Increase the
maximum number of concurrent connections for the
user.
Source: LANRES
EWXxx4025E Login unsuccessful: User account
has expired or been disabled.
Explanation: The users account on the server is
either expired or disabled.
User Response: Ask your system programmer to
enable your user account on the server and change
your account expiration date. Reenter the command to
login to the server.
System Programmer Response: Remove the user
IDs account disabled restriction and change his account
expiration date on the server.
Source: LANRES
User Response: Reenter the EWXCONN LINK

command with the correct subchannel address.
77
EWXxx4026E Login unsuccessful: Password has

expired.
EWXxx4033W Line number of configuration file

filename is too long.
Explanation: The user IDs password on the server

has expired.
Explanation: The line indicated in the message is too

long.

System Action: The line in error is bypassed.

change your user IDs password, if required, and
password expiration date. You may also login to the
server from a PC client and change your password
when prompted for a new one. Reenter the command to
login to the server. Supply the new password if it has
been changed.
IDs password and password expiration date on the
server, if required.
User Response: Edit the configuration file and correct

the specified line. You may have to notify the system
programmer if the incorrect line is in the system
configuration file and you do not have write access to
the system configuration file:
v EWXCONFG.LINK
System Programmer Response: Correct the system
configuration file if necessary.
Source: LANRES
Source: LANRES
EWXxx4035E Hostname hostname is not a valid

host name.
EWXxx4027E Login unsuccessful: Grace login limit

exceeded.
Explanation: When using the TCP/IP protocol, the

hostname operand was incorrectly specified. (It must be
specified as a character string of up to 63 characters.)
Explanation: The user IDs password has expired and

the login attempt exceeded the number of grace logins
permitted.


change your user IDs password and password
expiration date, if required. Reenter the command to
login to the server. Supply the new password if it has
been changed.
IDs password and password expiration date on the
server, if required.
Source: LANRES
EWXxx4032W Line number of configuration file
filename has an incorrect format.
Explanation: The line indicated in the message is in
an incorrect format. Values may be missing or specified
out of order.
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
have to notify the system programmer if the incorrect
line is in the system configuration file and you do not
have write access to the system configuration file:
v EWXCONFG.LINK
System Programmer Response: Correct the system
configuration file if necessary.
Source: LANRES
78
User Response: Correct and reenter the EWXCONN

LINK command.
Source: LANRES
EWXxx4036W Dropping previous connection
before trying new connection.
Explanation: You tried to establish a connection to a
LANRES function on the NetWare server when there is
already a connection to the NetWare server. There can
be only one LANRES connection at a time so your
previous connection will be dropped before a new
connection is attempted.
System Action: The previous connection to the
NetWare server will be dropped.
Source: LANRES
EWXxx4041E Incorrect component password
password specified.
Explanation: A component password must be
between 1 and 8 characters long, and be an
alphanumeric string (0-9, a-z, A-Z). The password is not
case sensitive.

command.

Source: LANRES

Source: LANRES
EWXxx4046I Dropping protocol connection through

server to function function.
EWXxx4043E Component password file filename

cannot be found.
Explanation: Your connection to the specified function

is being dropped.
Explanation: The component password file contains

the two component passwords required to authorize the
connection between the host and the NetWare server.
The command was unsuccessful because these
passwords were not specified with the command and a
file containing these passwords cannot be found.
System Action: The connection to the NetWare server

is dropped.

User Response: You may specify these component
passwords when you enter the command or you may
create a default component password file to hold these
passwords.
The default password file should be created as
EWXADMIN.MVSPW, EWXDISK.MVSPW,
EWXDIST.MVSPW, EWXHLPRT.MVSPW, or
EWXLHPRT.MVSPW.
Notify your system programmer if you do not know what
these component passwords are.
System Programmer Response: Find out what the
component passwords are and inform the user.
Source: LANRES

Source: LANRES
EWXxx4049E Error dropping the connection. Error
Explanation: An error occurred while trying to drop
your connection. The explanation for the error,
error_text, was returned in the message.
User Response: Correct the problem indicated:
error_text. Reenter the command. If the problem
persists, notify your system programmer.
again. If the problem persists, contact your IBM service
representative.
Source: LANRES
EWXxx4044E The PWIN and PWOUT values must

be specified as a pair.
Explanation: If the PWIN and PWOUT component
passwords are to be specified on the command line,
then they must be specified together or not at all.
EWXxx4054I protocol connection through server

established to function function.
Explanation: Your connection to the NetWare server
has been established.

command.
Source: LANRES
Source: LANRES
EWXxx4045E No connection to drop. You were not
connected to the server.

function. Error returned was: error_text
Explanation: You were not connected to a LANRES

function on the NetWare server so there was no
connection to drop.
Explanation: An error occurred while trying to connect

to the function function on the NetWare server. The
message.


User Response: None. You are no longer connected

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
79
the problem persists, notify your system programmer.

System Programmer Response: If necessary, load
additional LANRES NLMs on the server. If the problem
persists, unload the LANRES NLMs from the NetWare
server and load them again. If the problem still persists,
contact your IBM service representative.
Source: LANRES
EWXxx4060I Attempted protocol connection through
target.
User Response: Correct the component password file

Source: LANRES
EWXxx4064I Information
Explanation: This is a message used to display
information requested by the user.
Explanation: A connection was attempted through the

indicated protocol and target but the attempt failed.
System Action: Command continues with next

connection attempt.
Source: LANRES

Source: LANRES
EWXxx4061E Line number of component password
file filename is too long.
Explanation: The line indicated in the message is
longer than 128 characters. Correct lines should not
require more than 128 characters.
User Response: Edit the component password file
and correct the specified line.
Source: LANRES
EWXxx4062E Incorrect password in line number of
component password file filename.
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: Correct the component password file
EWXxx4065W Lines in file filename may have been

truncated.
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
been truncated.
User Response: Set up a file with the correct record
length and reenter the command.
Source: LANRES
EWXxx4066E The command specified in the CMD
option is too long.
Explanation: The host command string specified
between the CMD option delimiters cannot be longer
than the maximum length of 255 characters. The CMD
option must also be the last option on the command
line.
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
option value.
Source: LANRES
Source: LANRES
EWXxx4063E One or both component passwords
cannot be found in filename.
EWXxx4067E CMD command command was

unsuccessful. Resulting return code is
return-code.
Explanation: Both component passwords are required

to connect the host to a NetWare function.
Explanation: The command specified as the CMD

option value was unsuccessful.

System Action: Connection is established with the

NetWare server but the command failed.
80
User Response: Check the resulting return code

found in the message to determine why the command
was unsuccessful.
EWXxx4205E Error closing disk image

Explanation: An attempt to close the indicated disk

Source: LANRES
EWXxx4201E Error opening disk image
Explanation: An attempt to open the indicated disk

User Response: Correct the problem and retry the
failing command.
Source: LANRES

failing command.
Source: LANRES
EWXxx4206I Building compression dictionary for

disk image disk_image_name.
Explanation: LANRES is building the data
compression dictionary for the indicated disk image
dataset.
EWXxx4202E Error reading disk image

Explanation: An attempt to read the indicated disk

Source: LANRES

failing command.
Source: LANRES
EWXxx4207I Compression dictionary built for disk

image disk_image_name.
Explanation: LANRES has finished building the data
compression dictionary for the indicated disk image
dataset.
EWXxx4203E Error writing disk image

Explanation: An attempt to write the indicated disk

Source: LANRES

failing command.
EWXxx4208I Disk image statistics for dsname.

Explanation: This is the VSAM linear dataset name.
Source: LANRES

EWXxx4204E Unable to commit disk image

Explanation: An attempt to commit the indicated disk
failing command.
Source: LANRES
Source: LANRES
EWXxx4209I NetWare volume size is nwsizeK, actual
volume size is ldsizeK.
Explanation: The NetWare volume size is the size of
the volume reported to the NetWare server while the
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.
81

Source: LANRES
EWXxx4210I sizeK is being used by blocks disk
blocks, compression ratio is ratio%.
Explanation: Each NetWare disk block is 512 bytes.
When disk compression is enabled, LANRES will
compress each group of 8 disk blocks before writing the
data to the VSAM linear dataset. The compression ratio
is the ratio between the number of bytes actually written
to the VSAM dataset and the number of bytes written by
the NetWare server.
EWXxx4213E DIV request for dsname failed with

error error, reason code reason-code.
Explanation: A data-in-virtual request for the indicated
VSAM linear dataspace failed with the indicated error
and reason codes. See OS/390 MVS Programming:
Assembler Services Reference for a description of the
DIV error codes.
User Response: Correct the problem and then retry
the failing command.
Source: LANRES

Source: LANRES
EWXxx4211I usedK in use, unusedK not in use,
unallocatedK not allocated.
Explanation: Space in the VSAM linear dataset is
either in use by a NetWare disk block, allocated but not
in use, or not allocated. Initially, all space in the dataset
is unallocated. As the NetWare server writes to the disk
volume, space will be allocated to handle the changed
disk blocks. As the disk blocks change in size due to
different compression ratios, the old disk block space
will be placed in a pool of unused space to be re-used
by future space allocations. Disk fragmentation
increases as the unallocated space decreases and the
unused space increases. You should use the
EWXLDCMP and EWXLDRST commands to rebuild the
VSAM linear dataset when the unallocated space
becomes zero.
Source: LANRES
EWXxx4212E Linear dataspace dsname has not
been initialized.
Explanation: The indicated VSAM linear dataspace
has not been initialized for use with LANRES.
User Response: Use the EWXLDCRT command to
initialize the dataspace and then retry the failing
command.
Source: LANRES
EWXxx4214E DSPSERV request for dsname failed

with error error, reason code
reason-code.
Explanation: A dataspace request for the indicated
and reason codes. See OS/390 MVS Programming:
Assembler Services Reference for a description of the
DIV error codes.
User Response: Correct the problem and then retry
Source: LANRES
EWXxx4215E Data compression support is not
available.
Explanation: Data compression is not available on the
current system. The EWXLDDMP and EWXLDRST
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
ZIV data compression support to restore a dataset
created by the EWXLDDMP command on a system with
ZIV data compression support.
User Response: Use the EWXLDDMP command with
the RLE option to create the dump dataset using RLE
data compression instead of ZIV data compression.
Source: LANRES
EWXxx4216E Error opening the EWXDUMP
dataset: error_text.
Explanation: LANRES was unable to open the dump
dataset defined by the EWXDUMP DD statement.
82

failing command.
Source: LANRES
EWXxx4221E Unable to build compression

dictionary: error.
Explanation: LANRES was unable to build the
compression dictionary for the indicated reason.
EWXxx4217E Error reading from the EWXDUMP

Explanation: LANRES was unable to read from the
dump dataset defined by the EWXDUMP DD statement.
failing command.
Source: LANRES

failing command.
Source: LANRES
EWXxx4222I countK bytes written to dump dataset
for disk image dsname.
Explanation: The dump dataset was successfully
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

failing command.
Source: LANRES
EWXxx4223E The EWXDUMP dataset was not

created by the EWXLDDMP command.
Explanation: The dataset specified by the EWXDUMP
DD statement does not contain a valid LANRES disk
image dump.
EWXxx4219E Error closing the EWXDUMP dataset:

error_text.
Explanation: LANRES was unable to close the dump
dataset defined by the EWXDUMP DD statement.
User Response: Use the EWXLDDMP command to

create the dump dataset.
Source: LANRES

failing command.
EWXxx4224I Dumping disk image dsname.
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.
Explanation: The EWXDUMP dataset used by the
EWXLDDMP and EWXLDRST commands must have
RECFM=VB and LRECL=4100. The BLKSIZE can be
any value which is supported by the device.
failing command.
Source: LANRES

Source: LANRES
EWXxx4225E Disk image dsname must be sizeK in
order to restore disk image.
Explanation: The disk image dataset for the
EWXLDRST command must be the same size as the
disk image dataset which was dumped using the
EWXLDDMP command when data compression is not
being used.
83
User Response: Allocate a new disk image dataset

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.
Source: LANRES
EWXxx4227I Disk image dsname restored.
Explanation: The indicated disk image has been
restored from the EWXDUMP dataset.

User Response: Issue the EWXLDDLT command to
delete the current disk image dataset and then retry the
EWXLDCRT command.
Source: LANRES
EWXxx4253E The disk image size of size is less
than the minimum size of 2 megabytes.
Explanation: The size specified for a new LANRES

disk image was less than 2 megabytes.
User Response: Specify a disk image size of at least

2 megabytes.
Source: LANRES

EWXxx4228E Insufficient storage available to
allocate work buffers.
Source: LANRES
Explanation: LANRES was unable to allocate its

internal work buffers.
EWXxx4254E The disk image size of size is greater

than the maximum size of 4 gigabytes.
Explanation: The size specified for a new LANRES

disk image is greater than 4 gigabytes.
User Response: Increase the region size and retry

Source: LANRES

User Response: Specify a disk image size no greater
than 4 gigabytes.
EWXxx4229W Disk image page page has been

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

number_of_blocks blocks.
Explanation: The LANRES disk image has been
successfully created. There are 512 bytes per disk
image block.
System Action: The command ends successfully.
User Response: Specify a valid NetWare volume

segment size.
Source: LANRES
EWXxx4264E Unable to delete disk image

Source: LANRES
EWXxx4257E A volume must be specified when
SMS is not active.
Explanation: A volume serial must be specified on the
EWXLDCRT command in order to create a new disk
image dataset when System Managed Storage is not
active.
User Response: Specify a volume serial on the
EWXLDCRT command.
Explanation: LANRES was unable to delete the

specified disk image.
command.
Source: LANRES
EWXxx4266E The disk image size parameter is
invalid.
Source: LANRES
Explanation: An invalid disk image size was specified.

The minimum disk image size is 2 megabytes and the
maximum disk image size is 4 gigabytes.
EWXxx4258I disk_image_name has been deleted.
Explanation: The LANRES disk image has been

successfully deleted.
User Response: Specify a valid LANRES disk image

size.
System Action: The command ends successfully.
Source: LANRES

Source: LANRES
EWXxx5001S Unable to create TCP/IP socket: Error

error.
Explanation: LANRES was unable to create the

specified disk image.
Explanation: LANRES was unable to create a TCP/IP

socket. The error code is the value returned for the
TCP/IP socket() function. See the OS/390 SecureWay
Communications Server: IP Programmers Reference for
a description of the error codes.

command.
User Response: Report the problem to the system

programmer.
System Programmer Response: Report the problem

to IBM.
EWXxx4261E Unable to create disk_image_name for

number_of_blocks blocks: error_text.
Source: LANRES
Source: LANRES
85
EWXxx5002S TCP/IP socket number is too large.

Explanation: The socket number returned by the
TCP/IP socket() function is too large. LANRES supports
a maximum of 32 TCP/IP connections per LANRES
command.
programmer.
to IBM.
EWXxx5006E TCP/IP send() function failed with

error error.
Explanation: The TCP/IP send() function failed with
the indicated error code. See the OS/390 SecureWay
programmer.
Source: LANRES
Source: LANRES
EWXxx5003E TCP/IP select() function failed with

error error.
EWXxx5007E Incorrect protocol name specified.
Explanation: The TCP/IP select() function failed with

programmer.
Explanation: An incorrect or unsupported protocol

was specified.
User Response: Specify a valid communications
protocol.
Source: LANRES

Source: LANRES
EWXxx5008E Incorrect destination name specified.
Explanation: The TCP/IP connect() function failed with

Explanation: An incorrect destination name was

specified. For a channel connection, the destination is
the even subchannel address assigned to the NetWare
server. For an APPC connection, the destination is
either the symbolic destination name or the
fully-qualified partner LU name. For a TCP/IP
connection, the destination is the host name assigned
to the NetWare server.

programmer.
User Response: Specify a valid destination.
EWXxx5004E TCP/IP connect() function failed with

error error.

Source: LANRES
Source: LANRES
EWXxx5005E TCP/IP recv() function failed with
error error.
Explanation: The TCP/IP recv() function failed with
programmer.
Source: LANRES
EWXxx5009E Service distribution rejected by

server server.
Explanation: The service distribution request was
rejected by the target NetWare server because the
distribution service level is less than or equal to the
current service level installed on the server. You can
force the service to be distributed by re-issuing the
command and specifying that service level checking is
to be bypassed.
User Response: Retry the command.
Source: LANRES
86
EWXxx5010E Service distribution to destination

destination failed.
Explanation: The LANRES service distribution
controller was unable to send the current service level
to the NetWare server at the indicated destination. For
an APPC connection, the destination name is either the
symbolic destination name or the fully-qualified partner
LU name. For a TCP/IP connection, the destination
name is the server host name. For a channel
connection, the destination name is the channel device
address assigned to the server.
System Action: The current service level is not sent.
User Response: Correct the cause of the error.
Source: LANRES
EWXxx5011E The NetWare service package file has
been modified.
Explanation: The NetWare service package file has
been modified.
User Response: Verify that you are accessing the
correct NetWare service package file. If the problem
persists, report the problem to the system programmer.
more information on the channel and device status

codes.
Source: LANRES
EWXxx5014E Device address has been halted.
Explanation: One of the LANRES channel device
addresses was halted by the operating system. This can
occur if the missing interrupt handler determines that
the channel device is not responding to I/O requests or
if the NetWare NLM is unloaded after a connection has
been established.
programmer.
NetWare server is operational and has not abnormally
terminated.
Source: LANRES
EWXxx5015E Device address is offline.
Explanation: LANRES was unable to allocate one of
the channel device addresses because the device is
offline.
System Programmer Response: Re-install the

LANRES product. Contact IBM if the problem persists.
User Response: Vary the device online or use a

different pair of device addresses.
Source: LANRES

Source: LANRES
EWXxx5012E Service distribution is not enabled

for destination destination.
Explanation: The ACCEPT_SERVICE parameter in
the EWXCOMM.INI control file on the NetWare server is
set to NO.
User Response: Change the EWXCOMM.INI file to
specify ACCEPT_SERVICE=YES.
Source: LANRES
EWXxx5013E I/O error on device address: Device
status devstat, Channel status chanstat,
Sense sense.
EWXxx5016E Device address is not a supported

device type.
Explanation: The indicated device is not supported by
LANRES.
User Response: Make sure that you have specified
the correct device addresses for the channel-attached
NetWare server. Also make sure that the correct control
unit tables are specified in the channel configuration file
on the NetWare server.
Source: LANRES
Explanation: LANRES encountered an I/O error on

one of the channel device addresses.
EWXxx5017E Device address is allocated to

another job.
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
87
User Response: End the other job or use a different

pair of device addresses.

Source: LANRES

Source: LANRES
EWXxx5301S ISPF is already active.
EWXxx5018E Device address does not exist.
Explanation: The EWXISPF command must be

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.
programmer.
device address is correct and that the NetWare server
is online and operational.
Source: LANRES
EWXxx5019E Device address is not a 3088/CTCA
type device.
Explanation: The device at the specified address is
not supported by LANRES for channel attachment.
programmer.
device address is correct and that the NetWare server
is online and operational.
Source: LANRES
EWXxx5020E Device address is not operational.
Explanation: The indicated device is not operational.
Intervention required status was reported on the I/O
request.
User Response: Make sure that the NetWare server
is powered on and that the channel device driver has
been loaded.
Source: LANRES
EWXxx5300S The EWXISPF command is valid only
in the TSO environment.
Explanation: The EWXISPF command must be
invoked as a command processor under TSO.
User Response: Issue the EWXISPF command while
logged on to TSO in the foreground or when the
Terminal Monitor Program is active in the background.
88

User Response: Issue the EWXISPF command from
the TSO READY prompt.
Source: LANRES
EWXxx5302I LANRES READY
Explanation: The EWXEXEC command processor is
ready to process a new command. When running in a
TSO environment, any TSO command may be entered
as well as the TSO, PGM, and REXX special
commands. When running in a non-TSO environment,
TSO commands are not supported and only the PGM
and REXX special commands may be entered.
The TSO special command tells EWXEXEC to process
the rest of the command line as a TSO command and
not to check for special commands. This is necessary if
you want to run a TSO command named PGM or
REXX.
The PGM special command tells EWXEXEC to process
the rest of the command line as an MVS program
invocation. The first token following the PGM command
specifies the dataset name and member of the MVS
load module. The remainder of the command line will be
passed to the MVS program as the parameter string.
The dataset name prefix will be added unless the
dataset name is enclosed in quotes. If the load module
is located in a STEPLIB, JOBLIB, or link list dataset,
omit the dataset name and specify just the member
name enclosed in parentheses. If a dataset name is
specified, it will be used as a tasklib on the ATTACH
command.
The REXX special command tells EWXEXEC to
process the rest of the command line as a REXX
procedure invocation. The first token following the
REXX command specifies the dataset name and
optional member of the REXX procedure. The
remainder of the command line will be passed to the
REXX procedure as the argument string. The dataset
name prefix will be added unless the dataset name is
enclosed in quotes. If the REXX procedure is located in
a SYSEXEC dataset, omit the dataset name and
specify just the member name enclosed in parentheses.
System Action: EWXEXEC waits for a command. In
the foreground TSO environment, commands are read
from the terminal. In the background TSO environment,
commands are read from SYSTSIN. In the batch
environment, commands are read from EWXINPUT.

User Response: Enter a command.
EWXxx5307S Insufficient storage available.
Explanation: The EWXEXEC command was unable to

allocate storage for work buffers.
Source: LANRES
EWXxx5303E Unable to read from the EWXINPUT

dataset: error.
read a record from the command dataset specified by
the EWXINPUT DD statement.
User Response: Run the EWXEXEC command in a

larger region.
Source: LANRES
EWXxx5308I command
Explanation: This message is issued by the

EWXEXEC command when it is reading commands
from the EWXINPUT dataset. Each command is
displayed before it is run.
Source: LANRES
User Response: Correct the error and re-issue the

EWXEXEC command.

EWXxx5304E Unable to get command line:
PUTGET error error.
get the next command line.
User Response: Correct the error and re-issue the
EWXEXEC command. See the OS/390 TSO/E
Programming Services for a description of the PUTGET
error codes.
Source: LANRES
EWXxx5305E Command is too long.
Explanation: The command read by EWXEXEC
exceeds the maximum length of 512 characters.

Source: LANRES
EWXxx5309E APPC is not available.
Explanation: This message is issued if the APPC
functions cannot be found in the current step library, job
library, or link library. APPC is available only on
MVS/ESA 4.2 and later.
System Action: The APPC connection is not
established.
User Response: Make sure that SYS1.CSSLIB is in
the step library, job library, or link library and then retry
the failing request.
Source: LANRES
System Action: The command is not executed.

User Response: Enter a shorter command.
Source: LANRES
EWXxx5306E Premature end of data while reading
the EWXINPUT dataset.
Explanation: The EWXEXEC command reached the
end of the EWXINPUT dataset while constructing a
command to be executed.
System Action: The command is not executed.
User Response: Make sure that the last command in
the dataset does not end with a continuation character.
EWXxx5310E APPC error error occurred on

connection to server.
Explanation: An error was detected on an APPC
request. The fully-qualified partner LU name will be
included in the message if it is known at the time of the
error. Otherwise, the symbolic destination name used to
establish the connection will be included in the
message.
System Action: The connection to the NetWare server
is dropped.
User Response: Correct the cause of the error and
then retry the failing request.
Source: LANRES
Source: LANRES
89
EWXxx5402E Unable to execute command: error.
EWXxx6005E Print queue name is a required input
Explanation: LANRES was unable to execute a

system command for the indicated reason.
Explanation: Print queue name is a required input for

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.
Source: LANRES
EWXxx6001E User ID is a required input
Explanation: The NetWare user ID is a required input
for this command.
System Action: The command is not executed, and
the ISPF panel is re-displayed with the cursor placed on
the Userid input field.
User Response: Type the NetWare Userid in the field
and retry the command.
Source: LANRES
EWXxx6002E Group ID is a required input
Explanation: The NetWare Groupid is a required input
for this command.
the Groupid input field.
User Response: Type the NetWare Groupid in the
field and retry the command.
Source: LANRES
User Response: Enter the print queue name and retry

the command.
Source: LANRES
EWXxx6006E Print server name is a required input
Explanation: Print server name is a required input for
this command.
the cursor placed at the beginning of the print server
name field.
User Response: Enter the print server name and retry
the command.
Source: LANRES
EWXxx6009E A user/group ID must be specified
Explanation: A NetWare user or group ID is a
required input for this panel.
the cursor placed at the beginning of the field.
User Response: Enter the NetWare user or group ID
in the field.
Source: LANRES
EWXxx6003E Login script file name is a required

input
Explanation: The name of a host data set that
contains or will contain the NetWare login script file is a
required input for this command.
the login script file name input field.
User Response: Type the NetWare login script file
name in the field and retry the command.
Source: LANRES
EWXxx6015E A password expiration interval of 0 to

365 must be specified
Explanation: The time interval between forced
password changes must be a positive integer less than
365. Entering 0 means that the password will never
expire.
the cursor placed at the beginning of the password
expiration interval field.
User Response: Re-type the password expiration
interval with a value between 0 and 365.
Source: LANRES
90
EWXxx6016E A password length of 1 to 20 must be

specified
Explanation: The minimum password length is a
number between 1 and 20.
the cursor placed at the beginning of the password
length interval field.
User Response: Re-type the password length with a
value between 1 and 20.
Source: LANRES
Source: LANRES
EWXxx6022E Message text must be specified
Explanation: No message text was specified to be
sent as a message.
the cursor placed at the beginning of the VSAM LDS
size field.
User Response: Type the message text in the
specified field.
Source: LANRES
EWXxx6017E The name of the restricted volume

must be specified
Explanation: The name of the NetWare volume where
the restriction on user disk space will apply must be
entered.
the cursor placed at the beginning of the volume name
field.
User Response: Enter the volume name in the
volume name field.
EWXxx6025E A date in the form of MM/DD/YY must

be specified
Explanation: Either a date was not entered, or a date
was not entered in the format MM/DD/YY.
the cursor placed at the beginning of the date field.
User Response: Re-type the date in the correct
format in the specified field.
Source: LANRES
Source: LANRES
EWXxx6019E A valid TSO data set name must be
entered
Explanation: A TSO data set name is required for this
input field. A valid TSO data set name may be up to 44
characters in length and have as many as 5 levels of
qualification.
EWXxx6026E A time in the form of HH:MM:SS must

be specified
Explanation: Either a time was not entered, or a time
was not entered in the format HH:MM:SS.
the cursor placed at the beginning of the time field.

the cursor placed at the beginning of the TSO data set
name field.
User Response: Re-type the time in the correct

format in the specified field.
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

for the data set size
Explanation: The field was left blank or a valid PC

path/file name was not entered.
Explanation: The size of the VSAM Linear Data set is

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
size field.
User Response: Enter a valid PC path/file name in

the specified field.
User Response: Enter a numeric value for the size of

the VSAM LDS in the specified field.

Source: LANRES
91
EWXxx6028E A number between 0 and 200 must

be specified for grace logins
EWXxx6035E A value between 0 and 268435455

must be specified
Explanation: The number of times a user can log in

with an expired password is a number between 1 and
200. Entering 0 means that the number of grace logins
is unlimited.
Explanation: A value between 0 and 268435455 must

be specified to complete the operation.

the cursor placed at the beginning of the grace logins
field.
User Response: Enter a number between 0 and 200
in the grace logins field.
Source: LANRES

Source: LANRES
EWXxx6036I Processing Successful
Explanation: The users request has been
successfully completed.
EWXxx6029E A number between 0 and 250 must

be specified for concurrent log ins
Explanation: The number of workstations a user may
be concurrently logged into is a number between 1 and
250. Entering 0 means that the number of concurrent
logins is unlimited.
the cursor placed at the beginning of the concurrent
logins field.

Source: LANRES
EWXxx6037E Processing Unsuccessful
Explanation: The users request did not complete
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.
Source: LANRES

Source: LANRES
EWXxx6031E A valid volume name must be

specified
Explanation: A valid volume name must be specified
to complete the operation.
EWXxx6040E Password data set cannot be

specified with passwords.
Explanation: Cannot specify a password data set if

the passwords are also listed.
Source: LANRES

Source: LANRES
EWXxx6032E A valid device address must be

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

Explanation:
Source: LANRES
EWXxx6042E A value between 1 and 1000000 must

be specified for line limit.
Explanation: The maximum number of lines allowed
in the log data set is a number from 1 to 1000000.
Source: LANRES
EWXxx6043E A value between 1 and 255 must be
specified for copies.
Explanation: You may make from 1 to 255 copies.
System Programmer Response: If the problem

persists, contact your IBM service representative.
Source: LANRES
EWXxx6047I Initializing data with information from
sample data set
Explanation: The specified data set does not exist.
The table summarizing data set entries has been
initialized from the sample LANRES configuration data
set.
System Action: Entries from the sample configuration
data set are displayed.
User Response: You can add, modify, or delete
entries.
Source: LANRES

Source: LANRES
EWXxx6048E Data set name is not valid

Explanation: An invalid data set name was specified.
EWXxx6044E Command not recognized

Explanation: An invalid command was entered in the
prefix area.
System Action: The ISPF panel is redisplayed with

the cursor placed at the beginning of the data set name
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

display and modification or a D to mark an entry for
deletion.

Source: LANRES
EWXxx6045W Some exit parameter data cannot be
displayed due to field constraints
Explanation: The amount of exit parameter data for
the entry exceeds the length of the parameter fields.
This situation can occur if long parameter values are
specified because values are not wrapped across
multiple fields.
System Action: The exit parameter data is truncated.
User Response: Data may be lost if the entry is
saved.
Source: LANRES
EWXxx6049E Member specified, but data set is not
partitioned
Explanation: The data set name is conflicting because
the data set is sequential, but a member was specified.
field.
User Response: Enter a valid data set name.
Source: LANRES
EWXxx6050E Protected data set cannot be
accessed
Source: LANRES
Explanation: The specified data set is protected so it

cannot be accessed through this interface.
EWXxx6046S Error encountered displaying ISPF

panel

field.
Explanation: A severe ISPF error occurred.

System Action: LANRES will attempt to redisplay the
previous panel.
User Response: Enter a nonprotected data set name,

or get authorization for the protected data set.
User Response: Restart the ISPF session.

93
Source: LANRES
EWXxx6051E Error processing requested data set
Explanation: The specified data set name could not
be used successfully.
field.
User Response: Verify the data set name, and reenter
it.
EWXxx6055E The disk image name must consist of

alphanumeric characters
Explanation: A character other than A-Z, a-z, or 1-9
was entered in the disk image name field.
the cursor placed at the beginning of the disk image
name field.
User Response: Retype the information in the field
using only the characters A-Z, a-z, and 1-9.
Source: LANRES
Source: LANRES
EWXxx6052E Password expected from server and
reentered value do not match
Explanation: The value specified for the password
expected from the NetWare server does not match the
reentered value.
the cursor placed at the beginning of the password field.
EWXxx6056E The disk image name must start with

an alphabetic character
Explanation: A character other than A-Z or a-z was
entered as the first character of the disk image name.
the cursor placed at the beginning of the disk image
name field.
User Response: Reenter the password expected from

the server and the verification password.

using only a character in A-Z and a-z for the first
character.
Source: LANRES
Source: LANRES
EWXxx6053E Password expected by server and

reentered value do not match
EWXxx6057E When data space size is specified,

access mode must be specified
Explanation: The value specified for the password

expected by the NetWare server does not match the
reentered value.
Explanation: The access mode field was left blank,

but a value was specified for the data space size.
Because the configuration data set is composed of
tokens, if the data space size is specified, the preceding
field (access mode) must also be specified.

User Response: Reenter the password expected by
the server and the verification password.
Source: LANRES

the cursor placed at the beginning of the access mode
field.
User Response: Enter a value for the access mode,
or blank out the value in the data space size field.
EWXxx6054E The password must consist of

alphanumeric characters
Source: LANRES
Explanation: A character other than A-Z, a-z, or 1-9

was entered in the password field.
EWXxx6058E Data space size must be in the range

of 1 to 2048 megabytes or left blank

Explanation: If a data space size is specified, it must

be set to a value between 1 and 2048.

using only the characters A-Z, a-z, and 1-9.

the cursor placed at the beginning of the data space
size field.

Source: LANRES
94
User Response: Reenter the data space size with a

value between 1 and 2048 or blank out the field.
BLANK, or provide a value in the PC extension field.
Source: LANRES

Source: LANRES
EWXxx6059E Access mode must be R, W, or left

blank
Explanation: If the access mode is specified, it must
indicate Read only or Write.
EWXxx6063E Data was truncated when written to

the data set

the cursor placed at the beginning of the access mode
field.
Explanation: Data was lost when the entry was

written to the configuration data set because the data
set logical record length is smaller than the length of the
specified data.
User Response: Indicate an access mode value of

Read only or Write, or blank out the field.
System Action: A truncated version of the entry is

stored in the data set.
User Response: Increase the logical record length of

the data set and reenter the data, or use a different
interface to enter this data.
Source: LANRES
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

the cursor placed at the beginning of the translation
option field.
Explanation: The attempt to allocate the data set so

that the entry could be written to it failed. The data has
not been stored in the data set.
User Response: Indicate a translation option value of

ASCII, ASCIITAB, or BINARY.
System Action: The ISPF panel showing the

summary of entries is redisplayed.
User Response: Verify that you have write authority

for the specified data set.
Source: LANRES

EWXxx6061E If type qualifier is BLANK, PC
extension cannot be specified
Source: LANRES
Explanation: BLANK was specified as the type

qualifier, and a value was entered in the PC extension
field.
EWXxx6065E The notify when printed field must be

set to YES or NO

the cursor placed at the beginning of the PC extension
field.
User Response: Blank out the PC extension field, or
change the type qualifier value.
Source: LANRES
Explanation: Either YES or NO must be selected for

the notify when printed field.
the cursor placed at the beginning of the notify when
printed field.
User Response: Indicate YES, that the print job
owner should be notified when the data has been
printed, or NO, that the owner should not be notified.
EWXxx6062E If PC extension is not specified, type

qualifier must be BLANK
Source: LANRES
Explanation: A value was not specified for the PC

extension field, and the type qualifier was set to a value
other than BLANK.
EWXxx6066E The translate data field must be set

to YES or NO

the cursor placed at the beginning of the type qualifier
field.
User Response: Change the type qualifier value to

the translate data field.
the cursor placed at the beginning of the translate data
field.
95
User Response: Indicate YES, that the data should

be translated from EBCDIC to ASCII, or NO, that the
data should not be translated.
EWXxx6070E For internal exit type, exit name must

be EWXLHJOB or EWXLHLNP
Source: LANRES
Explanation: An exit type of INTERNAL was specified,

but the exit name field was not set to a valid
IBM-supplied exit.
EWXxx6067E The user exit type field must be set

to EXEC, INTERNAL, or PGM

the cursor placed at the beginning of the exit name
field.
Explanation: A value other than EXEC, INTERNAL, or

PGM was entered in the user exit type field.
the cursor placed at the beginning of the user exit type
field.
User Response: Reenter a value for the user exit type
field using EXEC, INTERNAL, or PGM.
Source: LANRES
EWXxx6068E For internal exit type, exit name must
be EWXHLINE, EWXHLTRN, or
EWXHSCS
Explanation: An exit type of INTERNAL was specified,
but the exit name field was not set to a valid
IBM-supplied exit.
the cursor placed at the beginning of the exit name
field.
User Response: Reenter a value for the exit name
field using EWXHLINE, EWXHLTRN, or EWXHSCS, or
change the exit type.
Source: LANRES
EWXxx6069E The exit type must be set to EXEC,
INTERNAL, OLDEXEC, PGM, or TSO
Explanation: A value other than EXEC, INTERNAL,
OLDEXEC, PGM, or TSO was entered in the exit type
field.
User Response: Reenter a value for the exit name

field using EWXLHJOB or EWXLHLNP, or change the
exit type.
Source: LANRES
EWXxx6071E The function field must be set to
DISK, HLPRT, or LHPRT
Explanation: A value indicating disk serving,
host-to-LAN print, or LAN-to-host print must be entered
in the function field.
the cursor placed at the beginning of the function field.
User Response: Select the disk serving, host-to-LAN
print, or LAN-to-host print option for the function field.
Source: LANRES
EWXxx6072E The function field must be set to
ADMIN or DIST
Explanation: A value indicating administration or
distribution must be entered in the function field.
the cursor placed at the beginning of the function field.
User Response: Select the administration or
distribution option for the function field.
Source: LANRES

the cursor placed at the beginning of the exit type field.
EWXxx6073E The protocol field must be set to

APPC, CHANNEL, or TCPIP
User Response: Reenter a value for the exit type field

using EXEC, INTERNAL, OLDEXEC, PGM, or TSO.
Explanation: A value indicating APPC, Channel, or

TCP/IP must be entered in the protocol field.

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
96
EWXxx6074E An entry already exists for the

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

Source: LANRES
Source: LANRES
EWXxx9000S No storage is available to initialize

the heap.
EWXxx9004E Unable to read message msgid from

the LANRES message repository.
Explanation: LANRES was unable to obtain its initial

storage requirements.
Explanation: LANRES was unable to display a

message due to an error while reading the message
repository.

representative.

displayed.
support programmer.
97

Source: LANRES
Source: LANRES
EWXxx9010S Connection open exchange was

unsuccessful with internal error error.
EWXxx9005S LANRES requires MVS/ESA Release

3.1.3 or later.
Explanation: The session initialization exchange with

the NetWare server was unsuccessful with the specified
internal error code.
Explanation: LANRES does not support the current

level of the host operating system.


to IBM.

Source: LANRES
EWXxx9006E Unable to write message to dsname:
error..
Explanation: LANRES was unable to write a log
message to the indicated log file.
Source: LANRES
EWXxx9011E Unable to read filename: error.
Explanation: An I/O error occurred while reading a
LANRES configuration file.
System Action: Configuration file processing ends.
System Action: The log message is not written to the

file.
User Response: Correct the problem and reenter the

command.
User Response: Correct the problem indicated by the

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
prompt the user to enter the actual password.
System Action: The configuration option is not

processed.
System Action: Wait for the user to enter the

password.
User Response: Correct the configuration options file

by specifying a valid configuration option.
User Response: Enter the password for the displayed

user ID.

Source: LANRES

Source: LANRES
EWXxx9013E option is an incorrect value for the

keyword configuration option.
EWXxx9008E Unable to read from terminal: Error

error.
Explanation: An incorrect option was specified in the

LANRES configuration options file.
Explanation: LANRES was unable to read a user

response from the terminal because the PUTGET
function failed with the indicated error. See OS/390
TSO/E Programming Services for a description of the
error codes.
System Action: The configuration option is ignored.
Source: LANRES

support programmer.
98
User Response: Correct the configuration options file

by specifying a valid configuration option.
EWXxx9014E Unable to read NetWare service file:

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

99
EWXxx9150E Dynamic allocation request for

dataset dsname failed with return code
return-code and error code error.
EWXxx9153E Unable to delete member member

from dataset dsname: STOW error error,
reason code reason-code.
Explanation: A dynamic allocation request failed for

the indicated dataset. The return code is the decimal
value returned in register 15 by SVC 99 and the error
code is the hexadecimal value returned in the error
reason field of the SVC 99 request block. See OS/390
MVS Programming: Authorized Assembler Services
Guide for a description of the error and possible
recovery actions.
Explanation: LANRES was unable to delete the

indicated partitioned dataset member due to a STOW
failure. See OS/390 DFSMS Macro Instructions for Data
Sets for a description of the error and possible recovery
actions.
System Action: The dataset is not allocated.

request.
System Action: The member is not deleted.

request.
Source: LANRES

Source: LANRES
EWXxx9151E Dynamic unallocation request for DD
ddname failed with return code
Explanation: A dynamic unallocation request failed for
the indicated DD. The return code is the decimal value
returned in register 15 by SVC 99 and the error code is
the hexadecimal value returned in the error reason field
of the SVC 99 request block. See the OS/390 MVS
Programming: Assembler Services Guide for a
description of the error and possible recovery actions.
System Action: The dataset is not freed.
EWXxx9154E Error reading dsname: error.

indicated dataset. The error text consists of the
messages returned by the SYNADAF system function.
request.
Source: LANRES
EWXxx9155E Error writing dsname: error.

request.
Explanation: An I/O error occurred while writing the

indicated dataset. The error text consists of the
messages returned by the SYNADAF system function.
Source: LANRES

request.

device ddname failed with return code
Explanation: A dynamic allocation request failed for

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

request.
Source: LANRES

Source: LANRES
100
EWXxx9157E Unable to store member member in

dataset dsname: STOW error error,
indicated partitioned dataset member due to a STOW
actions.
System Action: The member is not stored.
request.
Source: LANRES
EWXxx9161E TSO service routine IKJEFTSR ended
with return code code and reason code
reason-code.
Explanation: The IKJEFTSR service routine ended
with an unexpected return code. See OS/390 TSO/E
Programming Services for a description of the return
codes and possible recovery actions.
System Action: The TSO command is not executed.
Source: LANRES
Source: LANRES
EWXxx9158E Unable to store member member in

dataset dsname because the dataset
directory is full.
EWXxx9162E name was not found.

indicated partitioned dataset member because there is
no room available in the dataset directory.
System Action: The member is not stored.
request.
Explanation: The indicated TSO command, REXX

procedure, or host program program was not found.
System Action: The command or program is not run.
User Response: Make sure that the name is correct
and that the proper DD statements are defined.
Source: LANRES

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
when either the Terminal Monitor Program (TMP) is not
running or the CALL command was used to start the
LANRES program.
Explanation: A TSO command or program was

terminated by an attention interrupt.
System Action: The command is terminated.
Source: LANRES
System Action: The command is not processed.

Source: LANRES
EWXxx9160E name abnormally terminated:

Completion code code, Reason code
reason-code.
EWXxx9164E Unable to run program name: error.
Explanation: A TSO command, REXX procedure, or

host system program abnormally terminated. The
completion code is either a hexadecimal system
completion code (Sxxx) or a decimal user completion
code (Unnnn).
System Action: The program is not executed.
Explanation: LANRES was unable to run a host

system program.

error text.
System Action: The command is terminated.
User Response: For a system completion code, see

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.
Source: LANRES

101
EWXxx9165E Syntax error in command command

Explanation: LANRES detected a syntax error in a
system command.
System Action: The command is not run.
User Response: Specify a valid system command.
Source: LANRES
EWXxx9169E Unable to run REXX procedure:

IRXEXEC error error.
Explanation: LANRES was unable to run a REXX
procedure. See OS/390 TSO/E REXX Reference for a
System Action: The REXX procedure is not executed.
request.
EWXxx9166E Unable to locate program name:

BLDL error error, reason code
reason-code.
Explanation: LANRES was unable to locate the
indicated program due to a BLDL failure. See OS/390
DFSMS Macro Instructions for Data Sets for a
Source: LANRES
EWXxx9170E Unable to run REXX procedure name:
error.
Explanation: LANRES was unable to run a REXX
procedure.
System Action: The program is not executed.
System Action: The REXX procedure is not executed.

request.

error text.
Source: LANRES
Source: LANRES
EWXxx9167E Unable to create REXX environment:

IRXINIT error error, reason code
reason-code.
EWXxx9171S LANRES task name terminated by

attention interrupt.

REXX environment. See OS/390 TSO/E REXX
Reference for a description of the error and possible
recovery actions.
request.
Explanation: A TSO attention interrupt was received

while a LANRES task was active. A U0024 user abend
will be issued to terminate the current task.
Source: LANRES

Source: LANRES
EWXxx9168E Unable to issue REXX stack request:
IRXSTK error error.
EWXxx9172E Online help is not available.

Explanation: Online LANRES help was requested but
LANRES is not running in a foreground TSO session.
System Action: The help information is not displayed.
Explanation: LANRES was unable to issue a REXX

data stack request. See OS/390 TSO/E REXX
Reference for a description of the error and possible
recovery actions.
User Response: Online help is available only when

LANRES is invoked as a TSO command in a
foreground TSO session. Retry the help request when
logged on to TSO.
System Action: The stack operation is not performed.

request.
Source: LANRES
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
102
encountered an error while displaying the help

information.
User Response: Make sure ISPF is available and that
the proper DD statements have been defined.
Source: LANRES
EWXxx9174E Unable to display help panel name:
error.
Explanation: The requested help panel either was not
found in the ISPF panel library or an error occurred
while attempting to open the panel member.
User Response: Make sure that the LANRES ISPF
panel library dataset is allocated to the ISPPLIB DD.
Source: LANRES
EWXxx9175E IDCAMS error error detected while
listing catalog level level.
Explanation: The IDCAMS utility returned an error for
the indicated catalog level. The error is usually the last
three digits of the IDCAMS error message. For
example, a return code of 12 indicates that message
IDC3012I was issued by IDCAMS. See the
DFSMS/MVS Access Method Services for VSAM
manual for more information on IDCAMS. See the
OS/390 MVS System Messages, Vol 3 (EWX-IEB)
manual for a description of the IDC messages.
System Action: The catalog list is not created.
failing command.
Source: LANRES
EWXxx9177E Linear dataspace dsname has not

been initialized.
Explanation: The indicated VSAM linear dataspace
has not been initialized for use with LANRES.
User Response: Use the EWXLDCRT command to
initialize the dataspace and then retry the failing
command.
Source: LANRES
EWXxx9178E DSPSERV request for dsname failed
with error error, reason code
reason-code.
Explanation: A dataspace request for the indicated
and reason codes. See the OS/390 MVS Programming:
Authorized Assembler Services Reference ALE-DYN for
a description of the DIV error codes.
System Action: Disk serving is terminated for the
failing LANRES volume.
User Response: Correct the problem and restart the
disk server job.
Source: LANRES
SYSOUT failed with return code
Explanation: A dynamic allocation request failed for a
SYSOUT dataset. The return code is the decimal value
returned in register 15 by SVC 99 and the error code is
the hexadecimal value returned in the error reason field
of the SVC 99 request block. See OS/390 MVS
Programming: Assembler Services Reference for a
System Action: The dataset is not allocated.
EWXxx9176E DIV request for dsname failed with

error error, reason code reason-code.

request.
Explanation: A data-in-virtual request for the indicated

and reason codes. See the OS/390 MVS Programming:
Authorized Assembler Services Reference ALE-DYN for
a description of the DIV error codes.
System Action: Disk serving is terminated for the

failing LANRES volume.
User Response: Correct the problem and restart the
disk server job.
Source: LANRES
Source: LANRES
allocating VSAM dataset dsname.
the indicated VSAM dataset. The error code is usually
the last three digits of the IDCAMS error message. For
103

System Action: The LANRES disk image dataset is
not created.
EWXLDCRT command.
Source: LANRES
deleting VSAM dataset dsname.
the indicated VSAM dataset. The error code is usually
the last three digits of the IDCAMS error message. For
System Action: The LANRES disk image dataset is
not deleted.
EWXLDDLT command.
Source: LANRES
EWXxx9184E Internal error detected - dictionary
tree corrupted.
Explanation: LANRES detected an internal error while
building a data compression dictionary.
to IBM.
Source: LANRES
EWXxx9185E Unable to read dictionary dsname:
error.
data compression dictionary dataset.
failing command.
Source: LANRES
EWXxx9186E dsname does not contain a valid
dictionary.
Source: LANRES
Explanation: The indicated dataset does not contain a

valid data compression dictionary.
EWXxx9182I message_text
Explanation: This message is used by the EWXWTO

command to send a message to a host system operator
console. The message text is supplied by the caller of
EWXWTO.
User Response: Change the EWXDICT DD statement

to point to a valid data compression dictionary dataset
and retry the failing command.

Source: LANRES

Source: LANRES
EWXxx9183E DSPSERV request failed with error
error and reason code reason-code.
Explanation: A dataspace request failed with the
indicated error and reason codes. See the OS/390 MVS
Programming: Authorized Assembler Services
Reference ALE-DYN for a description of the DSPSERV
error codes.
failing command.
104
EWXxx9187W Disk image dsname is too small for

data compression.
Explanation: Data compression was requested but the
disk image dataset is not large enough to contain the
data compression control tables. As a general rule, the
disk image dataset should not be smaller than one half
the size of the NetWare volume segment.
System Action: Data compression is not used for the
disk image.
User Response: If the error occurred while creating a
new disk image dataset, specify either a larger image
dataset size or a smaller NetWare volume segment
size. If the error occurred while restoring a disk image
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.

Source: LANRES
EWXxx9188E Unable to enqueue dataset dsname:
Error error.
Explanation: LANRES was unable to issue an
enqueue for a sequential or partitioned dataset. The
error code is the return code from the ENQ macro.
System Action: The dataset is not opened.
programmer.
to IBM.
EWXxx9197S LANRES task name abnormally

terminated with completion code code
Explanation: A LANRES task was abnormally
terminated. The completion code is either a
hexadecimal system completion code (Sxxx) or a
decimal user completion code (Unnnn). The reason
code is always a hexadecimal value. See OS/390 MVS
System Codes for a description of the system
completion codes.
LANRES uses the following user completion codes:
0016 - The C/370 abort() function was requested.
0020 - Communication subtask abnormally
terminated.
0024 - Task terminated by attention interrupt.
Source: LANRES
System Action: The LANRES command is

terminated.
EWXxx9195S Unable to attach the communication

subsystem task: Error error.

command.
Explanation: LANRES was unable to start the

communication subsystem task. This task performs all
inter-task and inter-system communication functions as
well as message display and logging functions.
Error codes between 0 and 99 are the ATTACH
return code.
Error codes between 100 and 199 are the IDENTIFY
return code + 100.

Source: LANRES
EWXxx9198E Unable to locate C/370 save area
during exit processing.
System Action: The current task is terminated.
Explanation: The LANRES ESTAE exit was unable to

locate a C/370 save area for use during recovery
processing.

programmer.
System Action: ESTAE recovery is not attempted and

the task is terminated.

to IBM. and is not translated.

support programmer.
Source: LANRES

to IBM.
EWXxx9196S The communication subtask is not

responding to requests.
Source: LANRES
Explanation: The LANRES communication subtask is

not responding to requests. This task performs all
inter-task and inter-system communication functions as
well as message display and logging functions. This
error can occur if a read has been issued for data from
the NetWare server and the server does not respond.
EWXxx9199S The communication subtask has

abnormally terminated.
System Action: The current task is terminated with a

U0020 abend.
Explanation: The LANRES communication subtask

has terminated. This task performs all inter-task and
inter-system communication functions as well as
message display and logging functions. There should be
additional messages in the job log indicating the cause
of the failure.
User Response: Make sure that the NetWare server

is operational and that the LANRES NLM has not
terminated.
System Action: The current task is terminated with a

U0020 abend.

request.
Source: LANRES

Source: LANRES
105
EWX Server Messages
EWX Server Messages

0100I
Explanation: The progname program has been loaded

and successfully initialized.
System Action: The program is ready to process
transactions.
Source: LANRES
0101I
control block. Other messages will be issued to

help determine the problem. The session is
cleaned up.
progname initialized.
progname Service Level level initialized.
Explanation: The progname program at service level

level has been loaded and successfully initialized.
System Action: The program is ready to process
transactions.
System Action: The failing program is unloaded or

restarted.
System Programmer Response:
v For RC=1, a session will have to be made available
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
SESSIONS field in the EWXCOMM.INI file (this
requires unloading and reloading all the LANRES
NLMs).
v For RC=6, correct the problem using the other
messages. Then restart the EWXCOMM NLM.
v For RC=8, use the other messages to determine and

correct the problem. Then restart the failing program.
Source: LANRES
Source: LANRES
0107E
0102E
Communications RECEIVE command

error (RC=return-code).
Explanation: An error occurred while reading data

from the host.
System Action: The communication session ends, but
the failing program will start to listen for a connection
from the host again. Other messages from EWXCOMM
should be issued.
System Programmer Response: The problem could
be that the host ended the conversation or it could be
that the communication link had an error. Use the other
messages to determine the problem.
progname level mismatch between Host

and Server programs.
Explanation: The version, release, and modification

numbers of program progname do not match the
release and modification numbers of the corresponding
program on the host.
System Action: The server program remains loaded
waiting for the correct version of the host program to be
run.
System Programmer Response: Check the levels of
the server and host programs. Then determine which
level should be run and make the necessary changes.
Source: LANRES
Source: LANRES
0109S
0103E
Unable to start communications

(RC=return-code).
Explanation: The communications driver was unable

to start a session on behalf of an application. The
possible error return codes are:
1
Communication layer could not find an empty

control block
Communication layer failed to initialize and will

unload. Other messages will be issued
indicating the failure(s).
An error occurred after finding the session
106
A request has been received that

cannot be executed by progname.
Explanation: The server program progname has

received an incorrect command request from the host.
System Action: The request is ignored and a return
code is passed back to the host program.
System Programmer Response: Ensure the
LANRES host programs are installed at the correct
release level that matches the NetWare NLMs. Do this
by entering either the EWXADMIN QUERY ID or
EWXDS QUERY ID command. The user may need to
enter the EWXCONN LINK command to establish a new
connection to the server.
EWX Server Messages

Source: LANRES
0110I
progname has been unloaded.
Explanation: The program progname has been

unloaded by a request from the NetWare console.
System Action: The program is unloaded. Any
session being used by progname becomes available.
Source: LANRES
0111I
Host timeout on session session.
and restart it, or enter a EWXCONN DROP command

from the host user ID connected to the NLM.
Source: LANRES
0130I
Connection established with host disk

server program, session session.
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
0132E
Insufficient memory to initialize disks.
Explanation: The host program has not responded to

a request within the time specified by the disk timeout
value.
Explanation: The disk driver, EWXDISK, was unable

to allocate the storage needed to add the disks.
System Action: The program stays loaded waiting for

a connection. The EWXDISK component will deactivate
all disks associated with that line and reactivate the
disks when the connection is reestablished.
System Action: The disks are not allocated to the

NetWare server. The disk driver, EWXDISK, will
continue to service disk requests for currently allocated
disks. If this occurs during initialization, EWXDISK will
unload.

System Programmer Response: Restart the host
program related to the NLM used to reestablish a
connection.
Source: LANRES
0112S
Host did not read the correct number

of packets.
Explanation: The server application tried to send a

certain number of packets of data to the host program.
The host program was interrupted and all the packets
were not read.
System Action: The server program remains
operational. The packets received at the host program
are discarded.

System Programmer Response: Unload programs or
install more system memory on the server.
Source: LANRES
0133I
Number of disks equals zero on

session session.
Explanation: The disk driver, EWXDISK, received a

response from the host program indicating that there
are no disks.
System Action: The disk driver, EWXDISK, will
remain loaded.
System Programmer Response: Restart the disk
server with the required disks.
Source: LANRES
System Programmer Response: Other error

messages may indicate why all the packets were not
read and should be used to correct the problem.
0134E
Source: LANRES
0115E
Host program is not a progname server.
Disks are currently active; use

QUIESCE or FORCE option.
Explanation: The EWXCMD DROP DISK command

was entered while disks were still active.
System Action: The disk is not dropped.
Explanation: The program on the NetWare server

does not match the program on the host. The server is
connected to a host program that performs a different
function.
System Action: The program remains loaded, waiting

for a request from the correct program.
LOAD SYS:\EWXNLM\EWXCMD DROP DISK 20 QUIESCE
System Programmer Response: Enter the EWXCMD

DROP DISK command again with the QUIESCE or
FORCE option; for example:

System Programmer Response: Unload the NLM
107
EWX Server Messages

For more information about the EWXCMD DROP DISK
command and the QUIESCE and FORCE options, see
OS/390 LANRES Configuration Files and Commands.
Source: LANRES
0135S
Initialization failed; unable to add disk

device.
Explanation: The disk driver, EWXDISK, received an

unacceptable return code from NetWare when adding a
disk to the system.
System Action: The disk driver, EWXDISK, unloads.
System Programmer Response: Reload the disk
driver.
Source: LANRES
0136S
Initialization failed; unable to add disk

card.
Explanation: The disk driver, EWXDISK, received an

unacceptable return code from NetWare when adding a
disk to the system.
System Action: The disk driver, EWXDISK, will
unload.
volumes associated with a host server.

System Programmer Response: Do not enter a
MOUNT command on the server while the disk driver,
EWXDISK, is mounting these volumes.
Source: LANRES
0143I
Log file copied to: log-fname.
Explanation: The current log has been saved in file

log-fname.
System Programmer Response: Since the log file
has been saved, it may be desirable to clear the log file
using the Reset log file menu option.
Source: LANRES
0144I
Message Buffer dumped to:

MB-dumped.
Explanation: The wrapping buffer used to save trace

messages has been dumped to file MB-dumped.
System Programmer Response: Retry the operation.
System Programmer Response: The file may be

used to view the last trace messages saved. Tracing to
this buffer is started by selecting the Selective Trace to
Buffer option from the Trace options menu.
Source: LANRES
0137E
The subchannel specified is not active.
Explanation: The subchannel specified on the DROP

DISK command is not being used by the disk driver,
EWXDISK.
System Action: The disk driver, EWXDISK, continues
to process requests.
System Programmer Response: Enter the DROP
DISK command again specifying a subchannel that the
disk driver, EWXDISK, is using. To see which
subchannels the disk driver is using, use the EWXCMD
Query Connections command.
For more information about the EWXCMD DROP DISK
command, see OS/390 LANRES Configuration Files
and Commands.
Source: LANRES
0141I
Mounting nn volumes; please do not

issue MOUNT command until done.
Explanation: The disk driver, EWXDISK, sends this

message before mounting the volumes.
System Action: The EWXDISK program mounts the
108
Source: LANRES
0146E
Log file buffer full, lost-message-count

message(s) were lost.
Explanation: The log file buffer is used to process

messages before writing them to the log file. The buffer
overflowed before writing completed and
lost-message-count messages were unable to be
processed.
System Action: Message logging continues after the
loss.
System Programmer Response: The log buffer size
may be increased in the configuration file using the
LOG_BUFFER_SIZE keyword
Source: LANRES
0199S
An internal processing error occurred

with symptom string: symptom.
Explanation: The system detected that it was in an

invalid state.
EWX Server Messages

System Action: Unpredictable.
User Response: Record the symptom string and
notify IBM service.
Source: LANRES
0501E
Insufficient parameters specified.
Explanation: Additional parameters are required for

this command.
System Action: The program is unloaded from the
NetWare server.
System Programmer Response: Load the program
using the correct syntax. For syntax information, see
Source: LANRES
0502E
Incorrect parameter(s) parameter(s)

specified.
Explanation: Incorrect parameter(s) were entered on

the command line following the program name. They
were possibly misspelled, incorrect, incomplete, or
improperly abbreviated.
NetWare server.
Source: LANRES

NetWare server.
Source: LANRES
0505E
API NetWare API error

(RC=return-code).
Explanation: A LANRES call to the NetWare API API

returned with the error return-code.
System Action: Error recovery is initiated.
System Programmer Response: Retry the operation
that failed. If the problem persists, look up the return
code in the NetWare library.
Source: LANRES
0506E
Duplicate parameter(s) parameter(s)

specified.
Explanation: The parameter(s) listed in the message

are part of the program syntax, but the parameter(s)
have been entered more than once.
NetWare server.
Source: LANRES
0503E
Too many parameters entered.
Explanation: Extraneous parameters were entered on

the command line following the program name.
NetWare server.
Source: LANRES
0504E
The password entered is longer than

127 characters.
Explanation: The password can not be longer than

127 characters in length for a NetWare object such as a
user ID or the LANRES object.
0507E
Incorrect server name server specified.
Explanation: A server name must be between 2 and

47 characters long and cannot contain spaces or any of
the following special characters:
/
\
:
;
,
*
?
(slash)
(back slash)
(colon)
(semicolon)
(comma)
(asterisk)
(question mark)

NetWare server.
109
EWX Server Messages

0511E
Source: LANRES
0508E
Conflicting parameter(s) parameter(s)

specified.
Explanation: The parameter(s) listed in the message

can not be used with another parameter entered on the
command line.
NetWare server.
Source: LANRES
0509E
Directory name in parameter parameter

is too long.
Explanation: The directory associated with the

parameter listed in the message exceeds the allowable
length of 254 characters.
Explanation: The program that issued this message

can be loaded multiple times on the NetWare server,
but certain parameters, such as the parameter listed in
the message, can be specified only by the first copy of
this program to be loaded. The value obtained from this
parameter will be used by subsequent copies of the
program to be loaded.
System Action: The copy of the program that issued
this message is unloaded from the NetWare server.
System Programmer Response: If you want to use
the parameter listed in the message, unload all copies
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
Source: LANRES
0512E

NetWare server.
Source: LANRES
0510E
Program unloaded. Required values

were not successfully initialized.
Explanation: Multiple copies of the program listed in

the message were loaded on the NetWare server at the
same time. These copies are dependent on certain
values being initialized by the first copy of the program
to be loaded. Not all the required values were initialized
successfully. All copies of the program will be unloaded
from the server.
System Action: All copies of the program are
unloaded.
Parameter parameter can only be

specified by the first NLM that is
loaded for this function.
Parameter parameter can only be

specified by the first EWXHLPRT.NLM
or EWXDIST.NLM loaded.
Explanation: Multiple copies of the EWXHLPRT.NLM

and EWXDIST.NLM can be loaded on the NetWare
server at the same time, but certain parameters, such
as the parameter listed in the message, can only be
specified by the first copy of either EWXHLPRT.NLM or
EWXDIST.NLM to be loaded. The value obtained from
this parameter will be used by subsequent copies of
EWXHLPRT.NLM and EWXDIST.NLM to be loaded.
System Action: The copy of the program that issued
this message is unloaded from the NetWare server.
System Programmer Response: To use the
parameter listed in the message, unload all copies of
EWXHLPRT.NLM and EWXDIST.NLM from the server
and load the first program using the parameters.
Otherwise, load the program with the correct syntax. For
syntax information, see OS/390 LANRES Configuration
Files and Commands.
Source: LANRES

System Programmer Response: Verify all required
values, such as component passwords or the LANRES
object password, are available to the first copy of the
program being loaded.
0513E
Source: LANRES
Explanation: The PWIN and PWOUT parameters

designate the values for the component passwords and
must be specified as a pair.
The PWIN and PWOUT parameters

must be specified as a pair. If one
parameter is specified, the other
parameter must also be specified.

NetWare server.
110
EWX Server Messages


System Programmer Response: Correct the file

filename and load the program again. Verify comments
in the file start with *, /, or ; in the first column.
Source: LANRES
Source: LANRES
0514E
0517I
Cannot open component password file

filename. Program will be unloaded.
Explanation: The program listed in the message tried

to open the component password file but the file cannot
be found or opened.
NetWare server.
Trace option turned on for function

function.
Explanation: The TRACE parameter was specified on

the command line or in the initialization file. The
program that issued this message will now run in
TRACE mode.
System Programmer Response: Verify the

component password file exists. The location where the
file can be found can be specified by using the function
or communication driver command line or from the
communication driver initialization file. Default
component password files can be created. The default
file name should be EWXxxxxx.NPW (xxxxx should be
replaced by the function ADMIN, DIST, DISK, HLPRT, or
LHPRT) and the file should be located in the directory
the program is loaded from or in the SYS:\EWXNLM
directory.
System Programmer Response: The TRACE

parameter should be used with the help of an IBM
Source: LANRES
0515E
Line number of component password

file filename is too long. Program will be
unloaded.
Explanation: Lines in the component password file,

except comments, are limited to 128 characters in
length. Line number in filename exceeded this limit.
NetWare server.
filename and load the program again.
Source: LANRES
0516E
Incorrect password specified in line

number of component password file

between 1 and 8 characters in length, and be an
The password is not case sensitive. Line number in
filename contains a password that does not fit this
format.
NetWare server.
Source: LANRES
0518E
Authentication error. Signature

mismatch between host and server
programs. Connection will be dropped.
Explanation: Packets sent between the host and the

NetWare server contain signatures to verify the packet
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
to the host will be dropped.
System Action: Connection to the host is dropped.
The program on the NetWare server tries to recover
from this error.
User Response: The user on the host should enter a
EWXCONN LINK command to establish a new
connection with the NetWare server.
System Programmer Response: This problem may
occur if the user on the host is using subchannels for
communications and does not use the LANRES LINK
command to change the set of subchannels used for
communications. If the problem persists, contact an IBM
Source: LANRES
0519E
Error sending data to the host

(RC=return-code).

sending data to the host.
System Action: The program on the NetWare server
tries to recover from this error.
communications method is operating correctly.
111
EWX Server Messages

Source: LANRES
Source: LANRES
0520W
0523E
Error receiving data from the host

(RC=return-code).

receiving data from the host.
Cannot find or open a file which

contains the LANRES object password.
Program will be unloaded.
Explanation: The program listed in the message tried

to find the LANRES object password in a designated
LANRES object password file or in default LANRES
object password files, but these files could not be found
or opened.

communications method is operating correctly.

NetWare server.
Source: LANRES
System Action: The program on the NetWare server

tries to recover from this error.
0521E
Cannot open a connection for the

function function because there are no
available sessions.
Explanation: The SESSIONS parameter in the

communications driver command line or in the
initialization file specifies how many sessions are
available to the LANRES functions. Each of the
EWXADMIN.NLMs, EWXDIST.NLMs,
EWXHLPRT.NLMs, and EWXLHPRT.NLMs loaded on
the server take up one of the available sessions. The
EWXDISK.DSK program takes up as many available
sessions as specified by its DISK_SESSIONS
parameter. This message was issued because all the
available sessions were taken, so no new LANRES
function can be loaded or started.

LANRES object password file exists. Specify where the
file can be found by using the function or the
communications driver command line, or the
communications driver initialization file. A default
LANRES object password file can be created. The
default file name should be EWXLOBJ.PWF, and the file
should be located in the directory the program is loaded
from or in the SYS:\EWXNLM directory.
Source: LANRES
0524E
Line number of LANRES object

password file filename is too long.
Program will be unloaded.
Explanation: Lines in the LANRES object password

file, except comments, are limited to 128 characters in
length. Line number in filename exceeded this limit.
System Action: If the function is ADMIN, DIST,

HLPRT, or LHPRT, then the program is unloaded from
the NetWare server. If the function is DISK, then the
new session is not started.

NetWare server.
System Programmer Response: Add additional

sessions with the EWXCMD server command or free up
some sessions by unloading one of the LANRES
functions.

Source: LANRES
0522E
Incorrect component password

password specified.

between 1 and 8 characters in length, and be an
The password is not case sensitive.
NetWare server.
112
Source: LANRES
0525E
Password specified in line number of

LANRES object password file filename
is too long. Program will be unloaded.
Explanation: A password can not be longer than 127

characters in length for the LANRES object. Line
number in filename contains a password that exceeds
this limit.
NetWare server.
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.
v The program has recovered from an error and
restarted successfully.
Source: LANRES
0527E
Cannot allocate memory for data

encryption or decryption. Program will
restart.

Source: LANRES
0530E
Logfile is full.
Explanation: The log file has reached its maximum

size and the current message cannot be logged.
System Action: The message is not logged.
System Programmer Response: Remove the log file
or increase the maximum size for the log file in the
EWXCOMM.INI file.
Source: LANRES
Explanation: Not enough memory is available on the

NetWare server to run the data encryption program for
processing component passwords.
0531W
System Action: The connection to the host will be

dropped.
Explanation: While logging a message, the log files

size exceeded the specified threshold.

persists, free up server memory by unloading NLMs or
add additional system memory to the server.
Source: LANRES
Source: LANRES
0528S
0532E
An unauthorized connection was

attempted to the function function.
Connection to the host will be
dropped.
The size of the logfile has exceeded

the threshold.
Parameter parameter is longer than the

maximum of number characters.
Explanation: The parameter listed in the message is

too long.
Explanation: Component passwords are used to

authorize the connection between the host and the
NetWare server. These component passwords must be
the same on the host and the server for the connection
to be maintained. The server program received an
incorrect password, which means the connection is not
authorized and will be dropped.

System Action: Connection to the host is dropped.
Source: LANRES

NetWare server.

component passwords are the same on the host and on
the server.
Source: LANRES
0529E
Value missing for parameter parameter.
Explanation: The parameter parameter requires an

associated value.
NetWare server.
0533E
Incorrect value value specified for

parameter parameter.
Explanation: The value listed in the message was

specified on the command line, but it is not an
acceptable value for the parameter listed in the
message.
NetWare server.
113
EWX Server Messages


Source: LANRES
Source: LANRES
0538I
0534E
One or both passwords cannot be

found in the component password file
Explanation: Both component passwords are required

to connect the host to a NetWare function.
NetWare server.
Source: LANRES
0535S
Unable to load as EWXCOMM failed

initialization.
Explanation: EWXCOMM did not initialize. All other

LANRES NLMs will not start.
System Action: The NLM will unload.
System Programmer Response: Examine the log file
or console to determine why EWXCOMM did not
initialize. Fix the problem and then restart EWXCOMM
followed by required LANRES NLMs.
Source: LANRES
0536E
API NetWare API error (RC=return-code;

message).
Explanation: A call was made to the NetWare API

listed in the message and an error was returned. The
return code from the API and, if available, an
explanation for the error are also displayed.
Connection between NLM_name and

the host on session session_number
will be dropped.
Explanation: The program on the host has requested

that the connection to the NLM be dropped. The internal
session number is displayed.
Source: LANRES
0539E
Cannot obtain a communication buffer

to send to the host.
Explanation: The NLM asked the communication layer

for a buffer to send to the host but the communication
layer was unable to fulfill the request. Suspect
insufficient server memory for the buffer.
System Action: The connection to the host is
restarted or the NLM is unloaded.
persists, free up server memory by unloading NLMs or
add more memory to the server.
Source: LANRES
0540I
NetWare Directory Services not

installed / DS.API not loaded.
Explanation: Either Netware Directory Services is not

installed or DS.API not loaded.
System Action: Bindery Emulation will be used.
User Response: If NDS is installed, load DS.API to
use NetWare Directory Services and then reload this
NLM. Otherwise, use bindery services for this NLM.
System Programmer Response: Uses bindery
services.
Source: LANRES
Source: LANRES
0541E
0537I
NLM_name has established a

connection to the host on session
session_number.
Explanation: The NLM has established a connection

to a program on the host. The internal session number
is displayed.
114
API NetWare API error

(RC=return-code).
Explanation: A LANRES call to the NetWare API API

returned with the error return-code.
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
Source: LANRES
1201I
LAN-to-host printing has established

host communications.
System Action: The program is unloaded.

System Programmer Response: If the return code is
1, 3, or 4, report the error to an IBM service
representative. If the return code is 2, operation will
continue normally.
Explanation: A communications link has been

established between the server and the host.
Source: LANRES
System Action: The file server will wait indefinitely for

the message from the host. When the proper message
is received and processing of print jobs is to begin, this
message is displayed. Should the connection be lost
and regained, this message will be displayed.
1206I

Source: LANRES
1203S
No print queues found for the print

server.
Explanation: There were no print queues set up on

the NetWare server that could be attached to the
LAN-to-host print server.
Explanation: The NetWare print server associated

with EWXLHPRT.NLM was deleted. When this happens,
the EWXLHPRT.NLM no longer has access to the
NetWare Queue Management System and cannot
process print jobs.
System Action: The EWXLHPRT.NLM which issued
the message is unloaded.
Source: LANRES
1208E
System Action: The program is unloaded.

System Programmer Response: Use PCONSOLE or
EWXADMIN to create the necessary print queues. See
EWXADMIN ADDPRTQ in OS/390 LANRES
Configuration Files and Commands.
Source: LANRES
1204S
Print server name already in use.
Explanation: The print server specified during the

start up of print on the host, or the default name:
HOSTPRT, is already being serviced by another print
server utility such as PSERVER.NLM.
System Action: The host side of print exits, and the
NLM waits for the host to restart.
System Programmer Response: Verify that the print
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
it; check PSERVER first.
Source: LANRES
1205S
Error returned using the AddINC

function (RC=return-code).
EWXLHPRT.NLM stopped because

print server was deleted.
Print queue file read error. Print server

restarting.
Explanation: A system I/O error was detected while

trying to read a print queue file.
System Action: The program will reset and try to read
the file again.
Source: LANRES
1209E
Number of print queues exceeded 100;

excess queues discarded.
Explanation: The print server was assigned more than

100 print queues. The first 100 are queued, the others
are not queued.
System Action: Subsequent print queues after the
first 100 are discarded. Processing continues normally
for the first 100 queues.
System Programmer Response: Use EWXADMIN
DELPRTQ to delete some queues that are not needed.
This will allow the system to restart and pick up the new
queues. For details about the EWXADMIN DELPRTQ
command, see OS/390 LANRES Configuration Files
and Commands.
Source: LANRES
Explanation: While trying to call the AddINC program,

an internal error was generated.
115
EWX Server Messages

1210E
A shared print queue, printq, was

found.
Explanation: The print server detected that the named

print queue is configured in the NetWare bindery as a
shared print queue. Shared print queue are not
supported.
System Action: The shared print queue will not be
serviced by EWXLHPRT.
System Programmer Response: Use either the
EWXADMIN RMVQSERV command on the host, or the
PCONSOLE utility on the NetWare console to disassociate
the shared print queue from all but one print server.
Then restart the LAN-to-host print connection(s) which
received this error. For information on the EWXADMIN
RMVQSERV command, see see OS/390 LANRES
Configuration Files and Commands. Use PCONSOLE to
display which print queues are associated with which
print servers.
Source: LANRES
1211I
Queue queue_name not defined at the

Host.
Explanation: The queue specified in the NPRINT

command was not recognized by the Host service
machine.
System Action: Processing of jobs for other queues
continues.
User Response: Use another print queue or contact
your system programmer with the queue name to be
added to the LAN-to-host print configuration.
System Programmer Response: Add the queue
name and corresponding data into the LAN-to-host print
configuration file, EWXLHPRT PROCS.
Source: LANRES
1213I
Print job purged; empty file.
Explanation: The print job specified to print contained

no data to print.
System Action: Print job is discarded. Processing of
jobs continues.
User Response: Do not send empty jobs to be printed
at the host.
Source: LANRES
1214I
Status_of_print_job
Explanation: The status of the print job when sent to

the host is returned through the use of a message that
the customer creates/modifies within the host user exits.
The message from the host is displayed by this
message.
System Programmer Response: Create messages
that are self explanatory. The message will be truncated
after 58 characters.
Source: LANRES
1215I
Cannot attach to queue queue.

print server specified during the start of the LAN to host
print service machine cannot be attached to the
EWXLHPRT.NLM.
System Action: The queue will not be monitored by
LAN to host print.
parameters associated with the queue status by using
PCONSOLE and modify if necessary.
Source: LANRES
1212I
Print job sent to host; status unknown.
Explanation: A user exit processed the job, but no

message information was returned. The status of the
print job is unknown. The job may or may not have
printed. This message is generated at the host print
service machine, and displayed at the client terminal.
System Action: Processing of jobs continues.
user exit associated with the queue is not returning any
message information.
Source: LANRES
1216I
Could not translate print queue name,

queue.

NPRINT command could not be translated correctly.
The LAN-to-host print service machine can not
determine which user exit to call.
System Action: The print job is not printed. The
System Programmer Response: Verify the queue
name is valid in terms of translating to EBCDIC. If
queue name is correct, check the translation routine.
Source: LANRES
116
EWX Server Messages

1217I
Job status message could not be

translated.
1427E
Error writing data into the print queue

(RC=return-code).
Explanation: The message returned from the user exit

stating the status of the print job could not be translated
from EBCDIC to ASCII correctly, or the message
returned was longer than 57 bytes.
Explanation: An I/O error was detected while trying to

write the data into the NetWare print queue. This could
be caused by a hardware problem on a disk or a
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

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
translating to ASCII. If the message is correct, check the
translation routine.
Source: LANRES
1218I
Error in user exit for queue queue.
Explanation: The user exit associated with the queue

returned a nonzero return code signifying that the user
exit did not process as expected.
System Action: The print job is not printed. The
user exit is not executing properly.
Source: LANRES

persists, either the NLM should be unloaded or the host
service machine should be stopped, or both should be
done. The cause of the problem should be determined.
When the problem is found, then the NLM should be
reloaded and the host service machine restarted.
Source: LANRES
1428E
Cannot start the function function

(RC=return-code; message).
Explanation: EWXHLPRT.NLM tried to start the

function indicated in the message as a separate
process in the NetWare server but the attempt failed.
The return code and, if available, an explanation for the
error are displayed.
1219W
Print job in progress, abend possible if

unload continues.
Explanation: The command UNLOAD EWXLHPRT

was entered on the NetWare console and
EWXLHPRT.NLM is currently processing a print job.
Continuing to unload could cause the NetWare server
processing to stop, print data to be lost, or both.
System Action: A continue with the unload command
prompt will be displayed.
User Response: Discontinue the unload command.

Source: LANRES
1429E
Insufficient memory for internal print

job information.
Explanation: EWXHLPRT.NLM creates internal tables

to store information about file servers and print jobs.
This error message is displayed when the NLM cannot
obtain enough memory from the server to add to these
internal tables.
Source: LANRES
System Action: The print job is cancelled and the

connection to the host is restarted.
1426I
Host-to-LAN printing
Explanation: This is a data dictionary lookup.

User Response: None
System Programmer Response: None
Source: LANRES
System Programmer Response: The host-to-LAN

print program on the host should automatically
reconnect to the NLM and resubmit the print job. If the
problem persists, free up server memory by unloading
NLMs or add more memory to the server.
Source: LANRES
117
EWX Server Messages

1430W
Insufficient memory to save

information for querying host-to-LAN
print jobs.
Explanation: The host-to-LAN print NLM cannot save

the information necessary for the EWXCONN QUERY
PRINT command.
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: If other messages
are being displayed because of the shortage on
memory, follow the direction associated with the other
messages or increase the memory on the NetWare
server.
1433E
Explanation: EWXHLPRT.NLM expected an

initialization packet but did not receive one.
restarted.
System Programmer Response: The host-to-LAN
print program on the host should automatically
reconnect to the NLM and send another initialization
packet.
Source: LANRES
1434E
Source: LANRES
1431E
Insufficient memory for number read

buffer records.
Explanation: EWXHLPRT.NLM cannot obtain enough

memory from the server to create an internal table
which is used to receive packets from the host. The
number of records for the internal table is taken from
the BUFFERS=number option or the default value.
System Action: The NLM is unloaded.
Incorrect initialization packet received

from the host.
The host packet that was received is

too small.
Explanation: EWXHLPRT.NLM received a packet from

the host that did not contain all the required information
to be a valid packet.
restarted.
persists, contact an IBM service representative.
Source: LANRES

System Programmer Response: Load the NLM with
a smaller number in the BUFFERS=number option. If
the problem persists, free up server memory by
unloading NLMs or add more memory to the server.
Source: LANRES
1432E
Insufficient memory for number thread

group records.
Explanation: EWXHLPRT.NLM cannot obtain enough

memory from the server to create an internal table
which is used to keep track of the separate processes
started by the NLM. The number of processes is taken
from the PROCESSES=number option or the default
value.
System Action: The NLM is unloaded.
System Programmer Response: Load the NLM with
a smaller number in the PROCESSES=number option.
If the problem persists, free up server memory by
unloading NLMs or add more memory to the server.
Source: LANRES
1435E
All the thread groups have not ended.
Explanation: EWXHLPRT.NLM is waiting for all the

separate processes to end before unloading or
restarting the connection to the host, but all the
processes have not ended.
System Action: The NLM is unloaded which will force
all processes to end.
Source: LANRES
1436E
Unknown host packet type number

received.
Explanation: EWXHLPRT.NLM does not recognize the

type of the packet received from the host.
restarted.
Source: LANRES
118
EWX Server Messages

1437W
The list of file servers has been locked

the last number minutes.
Explanation: EWXHLPRT.NLM is processing a lot of

work and is slow in responding to the task that issued
this message. The list of file servers is an internal list
used by the NLM. This message may appear
occasionally on a busy file server.
System Action: The task continues to wait for the list
of file servers.
System Programmer Response: If this message
appears frequently, contact an IBM service
representative.
Source: LANRES
1438W
No receive buffer has been freed the

last minutes minutes.
Explanation: EWXHLPRT.NLM is processing a lot of

work and is slow in processing the requests from the
host. Receive buffers are used internally by the NLM to
read information from the host. This message may
appear occasionally on a busy file server.
Source: LANRES
1754E
Incorrect value value given for

DISK_SESSIONS.
Explanation: An incorrect value was given for the

DISK_SESSIONS option when loading EWXDISK.
System Action: EWXDISK will unload.
System Programmer Response: Specify a correct
value for DISK_SESSIONS. If a number is not specified,
one additional EWXDISK session will be started.
Source: LANRES
1755S
Initialization failed because of a

session that was not valid.
Explanation: A session number greater than the

allowed number of sessions was passed to the
communication layer during initialization.
dropped.
System Action: The task continues to wait for a

receive buffer.
System Programmer Response: Determine what

application is causing the problem and correct it.
Source: LANRES

BUFFERS value on the LOAD EWXHLPRT.NLM
command line. If this message still appears frequently,
contact an IBM service representative.
1756E
Source: LANRES
1751E

DISKTIMEOUT.
Explanation: An incorrect value was given for the DT=

option when loading EWXDISK.
Unable to start connection.
Explanation: A EWXCMD START DISK command has

encountered an error while starting connection to the
host for the disk driver. Other error messages
accompany this message.
System Action: No more sessions will be started.
System Programmer Response: If more sessions are
needed, determine the error from the other messages
and correct it. Enter the EWXCMD START DISK
command again.
System Programmer Response: Specify a value of 1

to 3600 for DT.
Source: LANRES
Source: LANRES
1757S
1753E

IDLETIMEOUT.
Not enough memory to begin thread

(RC=return-code).
Explanation: Not enough memory was available to

start a thread necessary for the disk driver to run.
Explanation: An incorrect value was given for the IT=

option when loading EWXDISK.
System Action: The disk driver unloads.
System Programmer Response: Using the NetWare

MODULES command, determine what other programs
have already been loaded, and unload any that are not
currently needed. Otherwise, add additional memory to
the server.

System Programmer Response: Specify a value of 1
to 3600 for IT.
119
EWX Server Messages

Source: LANRES
1758E
Not enough memory to begin thread

(RC=return-code).
Explanation: A EWXCMD START DISK command has

encountered an error. Not enough memory was
available to start a thread that accepts connections from
the host.
System Action: No additional disk sessions will be
started.
System Programmer Response: If more disk
sessions are desired, use the NetWare MODULES
command to determine what other programs have
already been loaded, and unload any that are not
the server.
1761E
Explanation: A communications error occurred during

the internal write routine. The host session may have
been stopped.
System Action: The session in which the error
occurred ends. The disk driver starts another session to
allow the host to reconnect.
System Programmer Response: Determine what is
causing the problem and correct it. The host side may
have been intentionally stopped or the communications
link could have gone down.
Source: LANRES
1762E
Source: LANRES
1759E
Unrecognized command to disk

command routine.
Explanation: The disk command routine was not able

to recognize the parameter passed by EWXCMD.
System Action: The EWXCMD command request is
discarded. Suspect memory has been overwritten.
System Programmer Response: Determine which
NLM is causing the problem.
Source: LANRES
1760E
Error in internal read routine

(RC=return-code).
Explanation: A communications error occurred during

the internal read routine. The host session may have
stopped.
System Action: The session in which the error
occurred ends. The disk driver starts another session
that accepts a connection from the host. The host can
then reconnect.
System Programmer Response: Determine what is
causing the problem and correct it. The host side may
have been intentionally stopped or a communications
link could have gone down.
Source: LANRES
Error in internal write routine

(RC=return-code).
Not enough memory to get a buffer

(RC=return-code).
Explanation: The buffer request was denied because

there is not enough memory.
System Action: The disks are deleted for this session
and become not recognized by the server. The
connection to the host is ended and the session
becomes available for the next connection from the
host.
currently needed or add additional memory to the
server. After adding more memory, restart the host
connection using the LANRES LINK command.
Source: LANRES
1763E
Error initializing disks (RC=return-code).
Explanation: An error occurred while starting a disk

image. If the return-code is -1, then the disk driver
thread could not start. If the return-code is 8, then the
SetThreadGroupId API failed. Other messages will be
displayed with this.
System Action: The disk image will not start and the
session will close.
System Programmer Response: If the return-code is
-1, the NetWare server is probably running out of
memory. Unload unnecessary NLMs or add more
memory to the server. If the return-code is 8, then follow
the directions from the other message displayed.
Source: LANRES
120
EWX Server Messages

1764E
Incompatible version of NetWare. This

program was built for execution on
NetWare Version
Intended_NetWare_version but is being
loaded on NetWare Version
Actual_NetWare_version.
Explanation: There are two LANRES programs

provided by LANRES for disk serving. One is intended
for use on NetWare Version 3 and is named
EWXDISK3.DSK and the other is intended for use on
NetWare Version 4 and is named EWXDISK4.DSK.
Both programs are shipped on the LANRES diskette
and the LANRES installation installs both into the
SYS:\EWXNLM subdirectory. The installation program
also determines what version of NetWare is running on
the NetWare file server from which the LANRES
installation program is being invoked and copies the
LANRES disk serving program that is compatible with
that version, to the SYS:\EWXNLM subdirectory as the
program named EWXDISK.DSK. Invoking the LANRES
installation program from a NetWare 3.xx file server,
three programs, EWXDISK3.DSK, EWXDISK4.DSK and
EWXDISK.DSK are installed to the SYS:\EWXNLM
subdirectory and the EWXDISK.DSK program is a copy
of the EWXDISK3.DSK program and must be loaded
only on NetWare version 3.xx file servers. Invoking the
LANRES installation program from a NetWare 4.xx file
server, three programs, EWXDISK3.DSK,
EWXDISK4.DSK and EWXDISK.DSK are installed to
the SYS:\EWXNLM subdirectory and the
EWXDISK.DSK program is a copy of the
EWXDISK4.DSK program and must be loaded only on
NetWare version 4.xx file servers. This error message
indicates that EWXDISK.DSK is being executed on a
NetWare file server that is running a different version
from that which the LANRES installation program was
invoked.
1765E
Error on BeginThread call

(ERRNO=errno).
Explanation: During the execution of LANRES disk

serving, a call was made for the EWXCOMM NLM to
begin a thread, via the NetWare BeginThread API, and
the API failed with an errno as indicated.
System Action: The program continues operation.
System Programmer Response: If the errno
displayed is 5 then this indicates that the NetWare file
server does not have enough memory. Using the
NetWare MODULES command, determine which
programs can be unloaded to free up memory.
Otherwise, add more memory to the server.
Source: LANRES
5501E
Insufficient memory available for

number_of_sessions sessions.
Explanation: EWXCOMM detected an error while

trying to reserve memory for the number_of_sessions
that were to be initialized. This number was either
specified on the load command for EWXCOMM.NLM, in
EWXCOMM.INI, or the default of 16.
System Action: The program unloads.
System Programmer Response: Determine if all of
the identified sessions are necessary, and if possible
decrease the number of sessions. Using the NetWare
have already been loaded and unload any that are not
the server.

NetWare server.
Source: LANRES
5503I

LANRES Disk Driver program is being loaded on a
version of NetWare that is supported by LANRES. See
the LANRES Licensed Program Specifications for
details on the versions supported. If the NetWare
version is supported then determine what version of
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
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
reissue the LOAD EWXDISK command.
Explanation: EWXCOMM is performing TCP/IP

initialization.
Source: LANRES
Explanation: The TCP/IP initialization failed with the

specified return value. Possible return values are:
Initializing TCP/IP.
System Action: EWXCOMM creates a socket and

binds it to the LANRES well known port number.
Source: LANRES
5504E
Could not initialize TCP/IP

(RC=return-code).
Cannot create socket
Cannot bind socket

121
EWX Server Messages

3
Error occurred starting ListenTCPThread
Cannot declare resource
Unable to locate a port number.
Error occurred starting ListenPWSCSThread
System Action: EWXCOMM attempts to initialize the

other communications options. If any of the other
communications options successfully initialize, then
EWXCOMM continues to operate. If no other
communications options are successfully initialized,
EWXCOMM exits.
System Action: EWXCOMM attempts to initialize any

communication options successfully initialize, then
EWXCOMM continues to operate. If no other
communication options are successfully initialized,
EWXCOMM exits.
System Programmer Response: Examine the

console to determine if any errors occurred in starting
TCP/IP.

console to determine if any errors occurred in starting
VM PWSCS. If the error code is 1, then EWXCOMM
was unable to be identified as the private resource
manager for the resource EWXCOMM. Verify no other
programs on this server have already identified this
resource using VM PWSCS Display/Configure.
v If TCP/IP is a necessary connectivity, unload

EWXCOMM, determine the problem, and correct it
based on the return values, and then reload
EWXCOMM.
v If the return value was 1, the server is probably
running out of buffer space. Message
EWXCOM5522E will also be displayed with more
information to help determine the problem.
Source: LANRES
v If the return value was 2, another application might

be using LANRESs well known port number, or
TCP/IP has not closed up the port. It might be
necessary to unload TCP/IP and restart it. Message
EWXCOM5523E will also be displayed with more
information to help determine the problem.
Explanation: VM PWSCS communications code

successfully initialized.
v If the return value was 3, there was not enough

memory to start a thread. Using the NetWare
MODULES command, determine what other
programs have already been loaded, and unload any
that are not currently needed. Otherwise, add
additional memory to the server. Message
EWXCOM5524E may also be displayed with this
message.
v If the return value was 4, verify that the well known

port address for LANRES has been added to the
\ETC\SERVICES file.
Source: LANRES
5505I
Initialized TCP/IP successfully.
Explanation: The TCP/IP communications code

successfully initialized.
System Action: EWXCOMM continues
communications initialization.
Source: LANRES
5509I
Initialized PWSCS successfully.

Source: LANRES
5512E
Error initializing NetWare for SAA

(RC=return-code).
Explanation: The NetWare CMLOGIN process

returned return-code, indicating a possible problem with
the NetWare for SAA side information file.
System Action: EWXCOMM attempts to initialize
EWXCOMM continues to operate. Otherwise,
EWXCOMM exits.
System Programmer Response: Verify the NetWare
for SAA side information file for EWXCOMM is correct.
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
file to increase the number of allowed sessions, or
unload the programs using the sessions.
Source: LANRES
5508E
Could not initialize PWSCS

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

specified return-code:
122
EWX Server Messages

5513I
Initialized NetWare for SAA

successfully.
Explanation: The NetWare for SAA communications

code successfully initialized.
5520E
An error occurred processing

arguments (RC=return-code).
Explanation: An error occurred while processing the

EWXCOMM command line arguments or the LANRES
initialization file (the default name is EWXCOMM.INI).
System Action: EWXCOMM unloads.
System Programmer Response: Verify the command

arguments passed to EWXCOMM are valid and the
LANRES initialization file exists and can be found.
Examine the LANRES message log or the server
console for further information as to which arguments or
initialization values were incorrect.
Source: LANRES
5516E
Error initializing channel connection

(RC=return-code).
Explanation: EWXCOMM could not initialize any of

the identified subchannels.
Source: LANRES
System Action: If any of the other communications

options successfully initialized, then EWXCOMM
continues to operate. Otherwise, EWXCOMM exits. An
return-code value of 3 indicates that no threads started
successfully.
5521I
System Programmer Response: Use the previous

error messages for information as to which subchannel
failed and take the appropriate action.
System Programmer Response: Using the other

messages displayed, determine the error and correct
the problem. Then reload EWXCOMM.
Source: LANRES
Source: LANRES
5517I
5522E
Initialized channel connection

successfully.
Explanation: The channel connections successfully

initialized.
Source: LANRES
5519E
No communication drivers loaded or

initialized successfully.
LANRES communications unloading.
Explanation: EWXCOMM is unloading because of an

error.
TCP/IP socket command failed during

initialization (ERRNO=errno).
Explanation: An error was encountered creating the

main socket. An errno of 55 indicates insufficient buffer
space.
System Action: This message may be displayed with
message EWXCOM5504E. TCP/IP connections are not
initialized, but EWXCOMM tries to initialize the other
connectivities. If any of the other connectivities
successfully initialize, EWXCOMM continues. Otherwise,
EWXCOMM unloads.
System Programmer Response: If TCP/IP

connectivity is necessary, unload EWXCOMM. Using
the NetWare MODULES command, determine which
programs can be unloaded to free memory on the
server. Otherwise, add additional memory to the server.
Then reload EWXCOMM.
Source: LANRES
Explanation: EWXCOMM was unable to initialize

communications for any of the supported
communications types.
System Programmer Response: Use the previous

error messages to determine what communications
types were unsuccessfully initialized and take the
necessary corrective action.
Source: LANRES
5523E
TCP/IP bind on port portnumber failed

during initialization (ERRNO=errno).
Explanation: The TCP/IP bind call failed during

initialization with errno:
9
Socket is already bound to another address

123
EWX Server Messages

48
Specified port is already in use (637 is the

LANRES port number).
49
Specified port is not available (637 is the

LANRES port number).

EWXCOMM unloads.

\ETC\SERVICES file on the server for a LANRES entry.
If it has not been added, add a line similar to the
following:
lanserver
Source: LANRES
5526S

System Programmer Response: If TCP/IP
connectivity is necessary, unload EWXCOMM. Check
\ETC\SERVICES to ensure no other application is using
the LANRES well known port number, 637. If another
application is using the port number, change the port
number for LANRES or the other application, and make
the corresponding changes on the host.
If LANRES is the only application using the port, then it
is possible that TCP/IP has not cleaned up the socket.
Wait five minutes and reload EWXCOMM. This will give
TCP/IP a chance to clean up the socket. If this still does
not work, unload the TCPIP.NLM and then restart
TCP/IP.
Error starting TCP thread

(ERRNO=errno).
Explanation: EWXCOMM could not start a thread,

using a BeginThread call, because the server does not
have enough memory.
EWXCOMM unloads.
MODULES command, determine which programs can
be unloaded to free up memory. Otherwise, add more
memory to the server.
Error accepting connection

(ERRNO=errno).
Explanation: The TCP/IP accept call failed because

memory has been overwritten.
System Action: The thread that listens for TCP/IP
connection from the host has stopped. No TCP/IP
sessions can be started.
System Programmer Response: If TCP/IP is a
needed connectivity, unload EWXCOMM and try to
restart it.
Source: LANRES
5527E
Source: LANRES
5524E
637/tcp
function function is not available. Load

the desired NLM.
Explanation: A host user tried to establish a

connection to a LANRES NLM and there is no function
of that type waiting for a connection. There are sessions
still available to accept more host connections, but the
desired LANRES function is not available because
either the function is not loaded or all loaded copies are
in use by another host user.
System Action: The host connection fails, issuing an
error message.
System Programmer Response: Load the requested
LANRES NLM (EWXADMIN, EWXDIST, EWXDISK,
EWXHLPRT, or EWXLHPRT) so the user can attach to
it. If the EWXDISK is already loaded, add another
session with EWXCMD START DISK 1.
Source: LANRES
Source: LANRES
5528E
5525E
Explanation: A host user tried to establish a

connection to a LANRES NLM, but there were no
sessions available to satisfy the request.
Unable to locate port number.
Explanation: The LANRES well known port number

was not found in the \ETC\SERVICES file.
EWXCOMM unloads.
124
No sessions were available to start

connection for function function.
System Action: The host connection fails, issuing an

error message.
System Programmer Response: Free up a session
by entering the LANRES DROP command from a host
EWX Server Messages

using the specified LANRES function, enter the
EWXADMIN TERM command from a user attached to
the administration function, or unload EWXADMIN,
EWXDIST, EWXDISK, EWXHLPRT, or EWXLHPRT.
Attention: By entering the UNLOAD command at the
server console, ALL the NLMs by that name will be
unloaded.
Source: LANRES
5532W
Error queuing buffer for session

session (RC=return-code).
Explanation: An error occurred queuing the buffer.

System Action: The buffer was not queued. The
session is cleaned up and stops.
Source: LANRES
5529E
Error setting TCP/IP parameters

(ERRNO=errno).
5533E
Explanation: The setsockopt API failed.

System Action: TCP/IP communications does not
start.
System Programmer Response: To use TCP/IP
communications, unload the LANRES NLMs and then
unload TCP/IP and restart it. Then reload the LANRES
NLMs.
Host dropped connection during

initialization.
Explanation: The host has stopped the connection.

System Action: EWXCOMM continues to accept more
TCP/IP connections.
Source: LANRES
Source: LANRES
5535E
5530E
Error starting TCP data thread

(ERRNO=errno).
Explanation: During a LANRES LINK, EWXCOMM

could not start a thread, using a BeginThread call,
because the server does not have enough memory.
System Action: The host and the NLM are notified of
the error and the connection stops.
MODULES command, determine which programs can
be unloaded to free up memory. Otherwise, add more
memory to the server.
Source: LANRES
5531E
TCP/IP error from a read call

(ERRNO=errno).
Explanation: An error occurred during the TCP/IP

read call.
Incorrect length sent. Cleaning up

session sessionnumber.
Explanation: During a TCP/IP read, the length sent

was greater than 4K.
System Action: The session ends with the host and is
cleaned up. The data received is discarded.
Source: LANRES
5536S
TCP/IP error on read for session

sessionnumber (ERRNO=errno).
Explanation: An error was returned on a TCP/IP read

for session sessionnumber.
System Action: The session is stopped.
System Action: EWXCOMM continues to accept more

TCP/IP connections.
System Programmer Response: The connection can

be restarted and the data move can be retried. If the
problem persists, contact an IBM service representative.
Source: LANRES

Source: LANRES
5537W
EOF received on TCP/IP read for

session sessionnumber.
Explanation: The socket was closed causing the

TCP/IP connection to receive an EOF.
System Action: The session sessionnumber is
stopped.
125
EWX Server Messages

System Programmer Response: The connection may
be restarted.
5540E
reSetThreadGroupID failed
(RC=return-code).
Source: LANRES
Explanation: The NetWare API SetThreadGroupID

failed to reset the thread group ID back to the original
ID. Memory may have been corrupted.
5538E
System Action: EWXCOMM continues. LANRES

function may terminate.
Error starting PWSCS thread

(ERRNO=errno).
Explanation: EWXCOMM could not start the thread,

from the BeginThread call, because the server does
not have enough memory.
System Action: PWSCS connections are not
EWXCOMM unloads.

System Programmer Response: If memory
corruption is suspected, contact an IBM service
representative and report the return code.
Source: LANRES
5541W

System Programmer Response: If PWSCS
connectivity is needed, unload EWXCOMM. Using the
Source: LANRES
An error occurred while closing

session session (RC=return-code).
Explanation: An error occurred when one of the

LANRES functions closed a session.
System Action: EWXCOMM continues.
Source: LANRES
5539E
Error declaring PWSCS

CPI-Communications resource
(RC=return-code).
Explanation: An error occurred declaring EWXCOMM

as a resource manager. The return-code is the return
code from the PWSCS call.
System Action: PWSCS connections are not
EWXCOMM unloads.
5542E
Error sending data (RC=return-code).
Explanation: An error occurred sending data to the

host with VM PWSCS or NetWare for SAA. The
return-code is the return code from the
CPI-Communications CMSEND call. This message
could be displayed with either EWXCOM5527 or
EWXCOM5528.
System Action: The host does not get the error, but
the conversation is closed as part of routine clean up.
System Programmer Response: If the return-code is:
System Programmer Response: Use the return code

to determine the problem.
20
17
The host application has ended abnormally.

The host has deallocated the conversation.
Correct the host problem and restart the host
application.
20
For PWSCS, use the PWSCS Display

Configure Utility to examine the Log to
determine the problem. For NetWare for SAA,
examine the NetWare for SAA console to
28
Use the PWSCS Display Configure Utility to

examine the log file. If the resource table has
overflowed, then increase the resources
permitted by modifying the value in the
PWSCS ACPI.INI file. The new value will take
effect when LANRES is restarted.
Another application has already declared this
resource. Determine which application has the
resource and remove that application.
Source: LANRES
126
Source: LANRES
EWX Server Messages

5543E
Error deallocating conversation

(RC=return-code).
Explanation: The CPI-Communications CMDEAL call

failed.

System Programmer Response: Correct the host
error, and restart the host application.
Source: LANRES
System Action: The conversation is not cleaned up.

System Programmer Response: The conversation
has already been cleaned up or the conversation
cannot be cleaned up. The next time the system is
restarted the conversation will be cleaned up.
Source: LANRES
5544E
Error receiving data (RC=return-code).
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
CPI-Communications CMRCV call.
System Action: The error is returned to the LANRES
NLM that is using this conversation. The conversation is
cleaned up. The LANRES NLM may unload or restart.
5548E
Error setting deallocation type

(RC=return-code).
Explanation: The CPI-Communications CMSDT call

has received an error.
System Action: The conversation is not cleaned up.
System Programmer Response: The system will still
be usable, but the conversation will not be cleaned up
until the next time LANRES is restarted. If the problem
Source: LANRES
5549E
Unexpected event: event
Explanation: The CPI-Communications XCWOE call

has received an unexpected event.
System Programmer Response: If the return code is:
System Action: The PWSCS connectivity thread will

end.
17
20

application.
For PWSCS, use the PWSCS Display
Configure Utility to examine the Log to
determine the problem. For NetWare for SAA,
examine the NetWare for SAA console to
System Programmer Response: Contact an service

representative.
Source: LANRES
5550E
Error wait on event failed

(RC=return-code).
Source: LANRES
Explanation: The CPI-Communications XCWOE call

has failed.
5545E
System Action: The PWSCS connectivity thread

stops.
Error accepting conversation

(RC=return-code).
Explanation: An error has occurred on the

CPI-Communications CMACCP call.
System Action: EWXCOMM keeps issuing CMACCP,
trying to accept a conversation from the host.

System Programmer Response: Contact an IBM
Source: LANRES

5551E
Source: LANRES
Explanation: The BeginThread call failed because of

lack of storage.
5546E
System Action: NetWare for SAA connections is not

EWXCOMM unloads.
Partner abnormally stopped.
Explanation: The host application has ended

abnormally.
System Action: The CPI-Communications CMRCV
call received a status indicating the host application has
abnormally stopped.
Error starting NetWare for SAA listen

thread (RC=return-code).

127
EWX Server Messages

System Programmer Response: If NetWare for SAA
connectivity is needed, unload EWXCOMM. Using the
Source: LANRES
5552E
Error declaring NetWare for SAA

CPI-Communications resource
(RC=return-code).
Explanation: An error occurred declaring EWXCOMM

as a resource manager. The return-code is the return
code from the CMSLTP call.
System Action: NetWare for SAA connections are not
connectivities. If none of the other connectivities
successfully initialize, EWXCOMM unloads; otherwise it
continues.
5557E
Error starting channel thread on

subchannel subchannel for type adapter
adapter. Thread not started
(RC=return-code).
Explanation: The thread that accepts data from the

host could not start because there was not enough
memory. The subchannel is the even subchannel for the
subchannel pair on type adapter adapter.
System Action: The session is no longer valid and
the connection is dropped and restarted.
the server.
Source: LANRES

20, examine the NetWare for SAA console for errors.
Source: LANRES
5554E
Error starting NetWare for SAA receive

thread (ERRNO=errno).
Explanation: EWXCOMM could not start the thread,

using the BeginThread call, because the server does
not have enough memory.
System Action: The host is notified and the
connection is severed. EWXCOMM continues.
5558I
No subchannels were started.
Explanation: The communications layer was unable to

start a subchannel. This could be because no
subchannels were specified in the EWXCOMM.INI file
or on the LOAD command for EWXCOMM. Otherwise,
other messages will be issued to determine the
problem.
System Action: EWXCOMM attempts to initialize
EWXCOMM continues. Otherwise, EWXCOMM unloads.
System Programmer Response: If this NetWare for

SAA connection is needed, unload EWXCOMM. Using
the NetWare MODULES command, determine what
other programs have already been loaded and unload
any that are not currently needed. If freeing memory
does not solve the problem, then add additional memory
to the server.
System Programmer Response: If subchannel

communication is necessary, use the error messages to
determine what the problem is. Verify the
EWXCOMM.INI file has the correct even subchannel
and corresponding adapter identified on the
subchannel= line. Check the adapter configuration file
(PSCA1.CFG or PSCA2.CFG) to ensure the list of ALL
the subchannels used (even and odd) for LANRES are
in the file.
Source: LANRES
Source: LANRES
5555E
5559E
Error: incorrect session number.
Explanation: The host has passed a session number

that is not valid to the server during connection
initialization.
System Action: The connection used to pass the
incorrect session number is deallocated.
Source: LANRES
128
ReadHandle could not be opened for

subchannel subchannel on type adapter
adapter (RC=return-code).
Explanation: A read subchannel could not be opened

because all the subchannel handles are currently in
use. The MMC card has a limit of 128 simultaneous
subchannels in use per adapter. The subchannel
subchannel specified is the even (read) subchannel of
the subchannel pair on type adapter adapter.
System Action: The subchannel pair specified does
not accept connections, but this does not effect the
EWX Server Messages

other pairs that initialize successfully nor the other
connectivities.
System Action: The subchannels are closed and the

session is stopped.

subchannel pairs on the adapter are not needed and
update the EWXCOMM.INI accordingly. Use EWXCMD
DELETE to remove subchannels and EWXCMD ADD to
add subchannels to be used. If more than 128
subchannels are needed, add another adapter.

contact an service representative.
Source: LANRES
5563E
Source: LANRES
5560E
WriteHandle could not be opened for

Explanation: A write subchannel could not be opened

because all the subchannel handles are currently in
use. The MMC card has a limit of 128 simultaneous
subchannels in use per adapter. The subchannel
subchannel specified is the odd (write) subchannel of
the subchannel pair on type adapter adapter.
System Action: The subchannel pair specified does
not accept connections, but this does not effect the
other pairs that initialize successfully nor the other
connectivities.
subchannel pairs on the adapter are not needed and
update the EWXCOMM.INI accordingly. Use EWXCMD
DELETE to remove subchannels and EWXCMD ADD to
add subchannels to be used. If more than 128
subchannels are needed, add another adapter.
Source: LANRES
5561E
Error return code from adapter status

for subchannel subchannel on type
adapter adapter (RC=return-code).
Explanation: An error occurred querying the status of

the type adapter card.
System Action: The subchannel is closed and made
not available for use by LANRES.
System Programmer Response: Try to reopen the
subchannel by using the EWXCMD ADD command.
Could not assign READ handle during

initialization, subchannel subchannel on
type adapter adapter (RC=return-code).
Explanation: An error occurred during initialization on

the read subchannel. Other messages may be
displayed with this message.
System Action: The subchannel pair does not
complete initialization. EWXCOMM continues initializing
other subchannels and the other communication
options. If none successfully initialize, EWXCOMM
unloads.
Source: LANRES
5564E
Could not assign WRITE handle during

Explanation: An error occurred during initialization on

the write subchannel. Other messages may occur with a
more detailed explanation of the error.
unloads.
Source: LANRES
5565E
Could not set extended mode during

Source: LANRES
Explanation: An error occurred during subchannel

initialization.
5562E

unloads.
Adapter error opening the subchannel

subchannel. Command
code=command_code (RC=return-code).
Explanation: An adapter error occurred while

initializing the subchannel pair subchannel. Status was
taken from the MMC and returned the command code.
129
EWX Server Messages

System Action: The connection for the MMC stops

and the subchannels close.
Source: LANRES
5566I
System Programmer Response: To make the

subchannels available again, use the EWXCMD ADD
command.
Host encountered an error during

initialization for subchannel subchannel
on type adapter adapter
(RC=return-code).
Source: LANRES
Explanation: The host encountered an error and

closed the subchannel connection.
5571E
System Action: EWXCOMM will clean up the

connection and then prepare to accept another
subchannel connection.
Explanation: The host has ended the channel

connection (either normally or abnormally).
System Action: EWXCOMM restarts the subchannels

and accepts another connection.
System Programmer Response: Restart the host

connection using the EWXCONN LINK command.
Source: LANRES
5567E
Adapter error reading for function

(RC=return-code).
Explanation: An error occurred on the MMC adapter.

This message is issued with other messages.
command.
Source: LANRES
5568E
Error reading initialization information

from host (RC=return-code).
Explanation: An error occurred reading initialization

information from the host on an MMC connection. This
message is displayed with message EWXCOM5569I,
which will indicate what subchannels had the error.
Error sending initialization information

to host (RC=return-code).

error occurred on the host and restart the host side
using the EWXCONN LINK command.
Source: LANRES
5572E
Adapter error sending initialization

information (RC=return-code).
Explanation: An error occurred on the MMC adapter

while sending initialization information to the host. Other
messages explaining the cause of the error in more
detail will be displayed with this message.
System Action: The connection with the host is
stopped and the subchannels are closed.
System Programmer Response: Using the other
messages, determine what caused the error and correct
it. Use the EWXCMD ADD command to reopen the
subchannels and restart the host side using the
EWXCONN LINK command.
Source: LANRES

5573E
Explanation: An error occurred sending the

initialization information to the host. The return codes
are:

command.
119
The MMC adapter did not have resources to

complete request
122
The MMC adapter did not have available

buffers to send data
130

buffers to send a command
Source: LANRES
5569I
Subchannel pair at subchannel on type

adapter adapter have not been brought
on-line.
Explanation: This message is displayed with message

EWXCOM5568E to identify the subchannels in error.
130
Error sending return code to host

(RC=return-code).
System Action: The EWXCOMM retry count has been

exhausted trying to send information to the host. The
MMC connection and the subchannels are closed.
EWX Server Messages

5577E
System Programmer Response: Use EWXCMD ADD

to make the subchannels available.
Source: LANRES
5574E
Error reading data from host for

session number session
(RC=return-code).
Explanation: An error occurred reading data using

MMC.
System Action: The session stops. If the return-code
is 12, the subchannels are closed. Otherwise, the
subchannels are reset and made ready to accept a
connection from the host.
12, then use the EWXCMD ADD command to add the
subchannels back on line. Use the EWXCONN LINK
command to restart the host.
Adapter error occurred on the read.

Command code=command_code
(RC=return-code).
Explanation: Status was taken from the MMC and

returned the command code. This message may occur
with other related messages.
session is stopped.
contact an service IBM representative to report the
command code.
Source: LANRES
5578E
Adapter error occurred on the write.

Command code=command_code
(RC=return-code).
Source: LANRES
Explanation: Status was taken from the MMC and

returned the command code. This message may occur
5575E

session is stopped.
Error waiting for data from host

(RC=return-code).
Explanation: EWXCOMM was waiting for data from

the host when an MMC adapter error occurred on the
connection.
System Action: Status is taken on the adapter to
determine the error. The subchannels are closed and
the session is stopped. This message may occur with
other messages.

contact an IBM service representative to report the
command code.
Source: LANRES
5579S

System Programmer Response: Use the other
messages to determine the error. After fixing the
problem, use EWXCMD ADD to bring the subchannels
back on-line.
Source: LANRES
5576E
Error querying adapter status

(RC=return-code).
Explanation: An error occurred while trying to obtain

status from the MMC adapter. This message may occur
session is stopped.
to add the subchannels.
Source: LANRES
SetThreadGroupID failed
(RC=return-code).
Explanation: The NetWare API SetThreadGroupID

failed to set the current thread group ID to
EWXCOMMs ID. Memory has been corrupted.
System Action: EWXCOMM continues. The LANRES
function may terminate. Unpredictable results could
occur.
System Programmer Response: DOWN the server
and restart it. If the problem persists, contact an IBM
service representative with the return code.
Source: LANRES
5580E
Adapter error sending EOF to host

(RC=return-code).
Explanation: EWXCOMM was restarting the

connection to the host by sending an EOF on the
subchannel, but an error occurred.
System Action: The connection does not restart.
Status is taken on the MMC, and the subchannels are
closed.
131
EWX Server Messages

System Programmer Response: Determine the error
from the other messages and correct it. Use EWXCMD
ADD to restart the subchannels after the problem has
been corrected.
Source: LANRES
5581E
Error restarting channel thread on

5584W
Host ended session session with

connection.
Explanation: The host stopped the session with

EWXCOMM.
System Action: The connection is broken and the
session is cleaned up. The LANRES function using this
session tries to accept another connection.
Explanation: EWXCOMM could not restart the

connection because of a channel error.
Source: LANRES
System Action: EWXCOMM made an attempt to

communicate to the host, but failed. The connection
stops and the subchannels are closed.
5586S
An error occurred on TCP/IP write for

Explanation: A TCP/IP write error occurred. Suspect

memory corruption.

to restart the subchannels.
System Action: The connection is stopped and the

session is cleaned up.
Source: LANRES
5582E

Open received bad status

(RC=return-code).
Explanation: A LANRES function (EWXADMIN,

EWXDISK, EWXDIST, EWXHLPRT, or EWXLHPRT)
tried to start a connection with the host, but failed. This
message may occur with other error messages.
System Action: No connection is made to the host
and the session is cleaned up. The LANRES functions
try to restart the connection.
Source: LANRES
5583W
Bad status was returned to read for

session session, status=status.
Explanation: This could be caused by one of the

LANRES functions dropping the connection from the
host by issuing a EWXCONN DROP or EWXCONN
LINK command. If an error occurred, other error
messages will be displayed.
System Action: The connection to the host is broken
and the session is cleaned up.
Source: LANRES
5587E
Explanation: Channel adapter encountered an error.

System Action: Status is taken from the channel
adapter. Other related messages are displayed.
System Programmer Response: Determine the
cause of the problem from the other messages.
Source: LANRES
5588E
Source: LANRES
An error occurred on channel write for

Explanation: An error occurred sending the data to

the host. The return codes are:
119
The MMC adapter did not have resources to

complete request
122

buffers to send data
130

buffers to send a command

System Programmer Response: If an error did occur,
examine the LANRES message log for other errors to
determine what happened.
Error on adapter sending data on

System Action: The EWXCOMM retry count has been

exhausted trying to send the information to the host.
The MMC connection and the subchannels are closed.
132
EWX Server Messages

to make the subchannels available.
5595W
Source: LANRES
Explanation: FreeBuf was told to deallocate a buffer

with a 0 address.
5589E
An error occurred on NetWare for SAA

write for session session
(RC=return-code).
Explanation: The CPI-Communications CMSEND call

failed.
Incorrect address for FreeBuf.
System Action: The request is denied.

System Programmer Response: If this continues and
the NetWare server runs out of memory, contact an IBM
System Action: The connection to the host is cleaned

up.
Source: LANRES
5597E

17
20

application.
Examine the NetWare for SAA console to
Source: LANRES
Error closing listening socket

(RC=return-code).
Explanation: When unloading EWXCOMM, an error

occurred closing the TCP/IP socket that accepts
incoming connections from the host during unload time.
System Programmer Response: If trouble occurs
loading EWXCOMM, unload TCPIP NLM and restart
TCP/IP.
Source: LANRES
5590E
An error occurred on PWSCS write for

5598E
Explanation: The CPI-Communications CMSEND call

failed.
System Action: The connection to the host is cleaned
up.
17
20

application.
Use the VM PWSCS Display Configure Utility
to examine the Log to determine the problem.
Source: LANRES
Error starting channel thread on

adapter. Thread not started
(RC=return-code).
Explanation: A command, like EWXCMD ADD,

encountered an error starting a channel thread to
accept connections on the subchannel because there
was not enough memory.
System Action: EWXCMD continues and unloads
when finished.
currently needed. Or, add additional memory to the
server.
Source: LANRES
5592W
Channel pair for subchannel

subchannel on type adapter adapter not
found when closing (RC=return-code).
Explanation: While closing a session, the subchannel

was not found in the control block structure.
System Action: The NLM continues to clean up the
session.
Source: LANRES
5599E
Subchannel subchannel on type adapter

adapter is not active.
Explanation: This may occur after entering the

EWXCMD DELETE command. The subchannel being
deleted is not being used by LANRES.
System Action: The subchannel is not deleted.
System Programmer Response: Verify the correct
subchannel was specified.
133
EWX Server Messages

Source: LANRES
5600E
Unable to open message repository

<name> (RC=return-code).
Explanation: EWXCOMM was unable to open the

indicated message repository.

Source: LANRES
5604E

System Programmer Response: Verify the identified
message repository is in the LANRES installation
directory. If the repository is not there, copy the
repository from the EWXNLM directory of the LANRES
installation diskette. If the repository is in the LANRES
installation directory, examine the console for other
messages that may suggest why the message
repository did not open.
Source: LANRES
5601E
Duplicate subchannel subchannel

specified.
Explanation: The same subchannel address was

specified more than once on the command line.
NetWare server.
Source: LANRES
5602E
Odd subchannel subchannel specified.
Explanation: The subchannel address specified on

the command line must be a two digit hexadecimal
number that corresponds to the even subchannel
address of a read/write address pair.
NetWare server.
Source: LANRES
The log files full directory name will

be too long.
Explanation: The directory name, which includes the

volume name, for the log file cannot be greater than
254 characters in length.
NetWare server.
Source: LANRES
5605W
Unable to begin thread to process log

files. Messages will still be recorded.
Explanation: The communications driver tried to start

a separate thread to process the log files, but failed. A
possible cause is the lack of server memory to start a
new thread.
System Action: Log files are not processed at
midnight, but messages continue to be recorded in the
current log file.
System Programmer Response: Load the
communications driver again. If the problem persists,
free up server memory by unloading NLMs or add
system memory to the server.
Source: LANRES
5606E
Cannot find or open an initialization

file. Communications driver will be
unloaded.
Explanation: The initialization file is required by the

communications driver. The communications driver
reads the file to set default values for certain program
parameters.
NetWare server.
5603E
Incorrect adapter number number

specified.

NetWare server.
System Programmer Response: Use the INIT_FILE

parameter on the command to specify the location of
the initialization file, or create a default initialization file.
The default file name should be EWXCOMM.INI and the
file should be located in the directory that the program
is loaded from or in the SYS:\EWXNLM directory.
Source: LANRES
Explanation: The adapter number must be 1 or 2.
134
EWX Server Messages

5607W
Line number of initialization file

filename is too long. Line will not be
used.
Explanation: Lines in the initialization file, except

comments, are limited to 500 characters in length.
initialization file filename.
Source: LANRES
5611W
Keyword keyword in line number of

initialization file filename has an
incorrect value. Line will not be used.
Explanation: A value was assigned to the keyword

listed in the message, but it is not an acceptable value
for the keyword.
Source: LANRES
5608W
Line number of initialization file

filename has an incorrect format. Line
will not be used.
Explanation: Lines in the initialization file must follow

a specific format. For more information about the
EWXCOMM.INI file, see OS/390 LANRES Configuration
Files and Commands.
5612W
Value missing for keyword keyword in

line number of initialization file filename.
Line will not be used.
Explanation: The specified keyword in the initialization

file requires a value be associated with it.
Source: LANRES
Source: LANRES
5613W
5609W
Duplicate keyword keyword in line

number of initialization file filename.
Previous value is replaced.
Explanation: A duplicate keyword is found in the

initialization file. Values from keywords lower in the file
will replace values from keywords higher in the file.
System Action: The previous keyword value is
replaced.
initialization file filename by deleting one of the duplicate
keywords.
Source: LANRES
5610W
Incorrect keyword keyword in line

number of initialization file filename.
Line will not be used.
Explanation: A keyword in the initialization file is not

recognized.
One or more incorrect subchannel

addresses were found in line number of
initialization file filename. The incorrect
subchannel addresses were not used.
Explanation: One or more values specified in the

SUBCHANNEL line of the initialization file were
incorrect. The incorrect values were discarded, but the
correct values will still be used. Possible causes of this
message are:
v The subchannel address was not a two digit
hexadecimal number.
v The subchannel address was not an even
subchannel address.
v The subchannel address was a duplicate of a
previous subchannel address on the same line or a
previous line.
v The adapter number was not 1 or 2.
v An extra semicolon was encountered after the last
subchannel address.
System Action: The incorrect subchannel addresses
are bypassed. Other subchannel addresses on the
same line are used.
Source: LANRES
Source: LANRES
135
EWX Server Messages

5617W
Unable to close initialization file

filename.
Explanation: An attempt to close the initialization file

failed.
System Action: The initialization file remains open.
The program continues.
System Programmer Response: Unloading the
communications driver and loading it may be required to
access the initialization file.
Source: LANRES
5618W
Unable to delete file filename.
Explanation: An attempt to delete the file listed in the

message failed. 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.
Source: LANRES
5621W
Unable to open current log file

filename.
Explanation: An attempt to archive the current log file

or record messages to it failed because the file cannot
be opened. The file may be opened or locked by
another process.
System Programmer Response: Unload and reload
the communications driver if necessary.
Source: LANRES
5622W
Unable to open archived log file

filename.
Explanation: An attempt to archive the current log file

failed because the archived log file listed in the
message cannot be opened. The file may be opened or
locked by another process.
the communications driver if necessary.
Source: LANRES
5619W
Reason for failure: error.
Explanation: This message is displayed with other

messages to explain a failure.
System Programmer Response: Use this message
to determine the cause of the error listed in the other
error message.
Source: LANRES
5620W
Out of space on volume to archive

current log file filename.
Explanation: The current log file cannot be archived

because there is no space to create the archive log file.
System Programmer Response: Free up space on
the volume by deleting old files, or add more space to
the volume.
Source: LANRES
5623W
Unable to archive current log file

filename.
Explanation: An attempt to append the current log file

to the appropriate archived log file failed.
the communications driver if necessary. Delete or
archive the current log file with a NetWare client or with
the LANRES Distribution function.
Source: LANRES
5624W
Unable to open log directory directory.
Explanation: Archived log files cannot be deleted

because the attempt to open the log directory directory
failed.
the communications driver if necessary. Delete the
archived log files with a NetWare client or with the
LANRES Distribution function.
Source: LANRES
136
EWX Server Messages

5625W
Unable to close log directory directory.
Explanation: An attempt to close the log directory

directory failed.
the communications driver.
host the subchannel is known as 25A, specify 5A as the

subchannel. The subchannel must also be in the
channel adapters configuration file (for example,
PSCA1.CFG, PSCA2.CFG, or NSCA1.CFG). See the
for more information on these files.
Source: LANRES
6254E
Source: LANRES
5626I
Log file started on server server.
Explanation: This message is recorded in the current

log file to indicate which server the log file is from.
Source: LANRES
5811I
{Add|Delete} available for subchannel

subchannel. Waiting for function.
Subchannel number missing from load

statement.
Explanation: No subchannel number was specified on

the LOAD EWXLSA command.
System Action: EWXLSA unloads.
System Programmer Response: Specify the
Subchannel=subchannel parameter on the LOAD
EWXLSA command, where subchannel is the
subchannel number. Refer to OS/390 LANRES
Configuration Files and Commands for the correct
format of the LOAD EWXLSA command.
Source: LANRES
Explanation: The requested connection is available,

and waiting for the associated function NLM to load.
6255E

User Response: Load the required NLM.
Explanation: The channel adapter type was not

specified on the LOAD EWXLSA command and is
needed.
Source: LANRES
6252E
Incorrect parameter specified.
Explanation: An incorrect parameter was specified

when loading EWXLSA.
System Programmer Response: Verify the load
command is specified correctly. Refer to OS/390
LANRES Configuration Files and Commands for the
correct format of the LOAD EWXLSA command.
Adapter type missing from load

statement.
System Programmer Response: EWXLSA cannot

determine which adapter to use. Specify the
Adapter=adapt_type parameter on the LOAD
EWXLSA command, where adapt_type is either MMC1,
MMC2, or ESCON. Refer to OS/390 LANRES
Source: LANRES
6256E
Too many parameters specified on

load statement.
Source: LANRES
Explanation: Two subchannels and one adapter type

can be specified on the load command.
6253E
Invalid subchannel specified.
Explanation: The subchannel on the LOAD EWXLSA

command was not valid.
subchannel was specified. The subchannel is the last
two digits of the host subchannel. For example, if on the

System Programmer Response: Correct the LOAD
EWXLSA command. Refer to OS/390 LANRES
Source: LANRES
137
EWX Server Messages

6257E
Subchannel number out of range.
Explanation: The subchannel number is out range for

the channel adapter. The MMC adapter cannot use
subchannel 0xFF. The ESCON adapter cannot use
0xFE and 0xFF.
System Programmer Response: Use a subchannel
other than 0xFF or 0xFE depending on the adapter
type.
Source: LANRES
6258E
Adapter type is not recognized.
Explanation: The adapter type specified on the LOAD

EWXLSA was not an accepted value. The acceptable
values are MMC1, MMC2, and ESCON.
Source: LANRES
6261E
Explanation: EWXLSA could not assign the

subchannel.
subchannel is not being used by another application. If
the subchannel is free, unload and reload the channel
adapter driver. If this does not work DOWN, then restart
the server. Then restart the channel adapter. If the
problem persists, contact an IBM service representative
and report the return code, return-code.
Source: LANRES
6262E

System Programmer Response: Correct the LOAD
EWXLSA line with the correct adapter type. Refer to
for the correct format of the LOAD EWXLSA command.
Source: LANRES
6259E
Connection to adapter_type adapter

could not be opened (RC=return-code).
Explanation: The adapter, adapter_type could not be

opened.
System Programmer Response: Verify the adapter

specified matches the one installed in the server. If the
specified adapter is in the machine, contact an IBM
service representative and report the return code,
return-code.
Source: LANRES
6260E
Could not determine which adapter to

use. Please reload using the Adapter
option.
Not enough resources available to

allocate buffer.
Explanation: EWXLSA tried to allocate a buffer, but

there was not enough resources.
System Programmer Response: The NetWare server
may be running out of memory. Unload unnecessary
NLMs or add more memory to the server.
Source: LANRES
6263E

Subchannel assign failed

(RC=return-code).
Error receiving command command on

the channel (RC=return-code).
Explanation: EWXLSA did not receive the expected

command command from VTAM,
System Programmer Response: Verify VTAM is
operational. It may be necessary to restart the VTAM list
that defines the channel adapter for LANRES. Refer to
for information on the VTAMLST. If the error persists,
contact an IBM service representative and report the
return code, return-code.
Explanation: EWXLSA could not determine which

adapter to use.
Source: LANRES
6264E

System Programmer Response: Specify the adapter
by using the Adapter parameter on the LOAD
EWXLSA command. Refer to OS/390 LANRES
138
Error sending command command on

the channel (RC=return-code).
Explanation: An error occurred sending command to

the host.
EWX Server Messages

System Programmer Response: Verify VTAM is
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
Files and Commands for information on the VTAMLST.
If the error persists, contact an IBM service
representative and report the return code, return-code.
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).

Source: LANRES
6269W
VTAM sent a stop system.
System Action: EWXLSA continues.
Explanation: EWXLSA could not set the channel

adapter to VTAM header mode.
Source: LANRES

System Programmer Response: Restart LANRES,
including unloading and reloading the channel adapter
driver. If the error persists, contact an IBM service
representative and report the return code, return-code.
Source: LANRES
6270W
Error writing data to channel

(RC=return-code).
Explanation: EWXLSA tried to send data to the host,

but failed. The primitive is skipped and processing
continues.
6266W
Error reading data from channel

(RC=return-code).
Explanation: An error occurred reading data from the

host.
System Action: EWXLSA will continue.

Source: LANRES
6271W
Error querying adapter status

(RC=return-code).

Explanation: EWXLSA could not determine what the

primitive was from VTAM. The primitive is skipped and
processing continues.
Source: LANRES

6267W
Error reading primitives from channel.
Explanation: This message is displayed with message

6266. An error occurred while reading for primitives sent
from the host.
Source: LANRES
System Action: EWXLSA will continue.
6272W

Source: LANRES
6268W
Unknown primitive received from

channel, 0xprimitive.
Explanation: EWXLSA could not determine what the

primitive was from VTAM. The primitive is skipped and
Adapter error occurred on the write

(Command code=command:
RC=return-code).
Explanation: An adapter error occurred while sending

data to the host.
System Programmer Response: If the problems
persists and diagnostics do not detect an error, contact
an IBM service representative to report the failing
command and return-code.
Source: LANRES

139
EWX Server Messages

6273W
Unknown VTAM request

command=0xcmd.
Explanation: VTAM sent an unrecognized request.

System Action: The command, cmd is not processed.
EWXLSA continues.
6278W
Invalid length received for command

0xcommand.
Explanation: The command, command, received a

negative length from VTAM.

Source: LANRES
Source: LANRES
6274W
Unknown VTAM response

command=0xcmd.
6279W
Explanation: VTAM sent an unrecognized response.

System Action: The response command, cmd, is not
processed. EWXLSA continues.
Source: LANRES
6275W
Unknown VTAM primitive: 0xcmd.
Explanation: VTAM sent an unrecognized primitive.

System Action: The command, cmd, is not
processed. EWXLSA continues.
Wrong state for command 0xcommand;

state = state.
Explanation: The state does not support execution of

the command, command.
Source: LANRES
6280E
LSL registration failed

(RC=return-code).
Explanation: EWXLSA was unable to register with the

LSL.
System Action: EWXLSA will unload.
Source: LANRES
6276W
System Programmer Response: The Return Codes

are:
Subchannel Reset received.
Explanation: EWXLSA received a subchannel reset

indicating VTAM was restarted.
-2
EWXLSA was unable to allocate a resource

tag. DOWN the server and try again.
System Action: EWXLSA resets; waiting for another

connection from VTAM.
-3
EWXLSA was unable to allocate memory.

DOWN the server and try again.
-119
The NetWare Server has run out of resources.

DOWN the server and try again.
-125
Another program has previously registered the

name EWXLSA is attempting to register.
-126
A system error has occurred. Contact an IBM


Source: LANRES
6277I
VTAM header mode not reset

(RC=return-code).
Explanation: The call to the adapter to reset the

VTAM header mode failed.
If the problem persists, contact an IBM service

representative.
System Action: EWXLSA continues to close the

channel.
Source: LANRES

Source: LANRES
140
EWX Server Messages

6281E
Error on BeginThread call

(ERRNO=errno).
Explanation: EWXLSA attempt to begin a thread, via

the NetWare BeginThread API, and the API failed with
an errno as indicated.
System Action: EWXLSA will unload.
System Programmer Response: An errno of 5
indicates that the NetWare file server does not have
enough memory. Using the NetWare MODULES
command, determine which programs can be unloaded
to free up memory. Otherwise, add more memory to the
server.
Source: LANRES
6282W
CSUNLOAD has not been done on

service profile.
Explanation: An attempt was made to unload the

EWXLSA.NLM before unloading the corresponding
service profile. This message is also issued with the
NetWare message Unload module anyway? and a
prompt.
7902E
No drop type specified.
Explanation: EWXCMD was started without a drop

type on the command line.
System Programmer Response: Enter a valid drop
type on the EWXCMD command line.
Source: LANRES
7903E
No query type specified.
Explanation: EWXCMD was started without a query

System Programmer Response: Enter a valid query
Source: LANRES
7904E
No start type specified.
System Action: EWXLSA waits for the prompt

response. A y response may cause the server to go
down or hang. A n response should keep EWXLSA
loaded. Follow the instructions in the System
Programmers Response.
Explanation: EWXCMD was started without a start

User Response: none.
System Programmer Response: Enter a valid start

System Programmer Response: Answer the prompt

with an n. Then unload the following in this order:
1. Any applications using EWXLSA.NLM (including
LANRES NLMs) for its communications
2. CPIC_SAA
3. The corresponding service profile using CSUNLOAD
4. EWXLSA
Source: LANRES

Source: LANRES
7905E
No subchannel specified.
Explanation: A subchannel was not specified on the

command line.
7901E
No command specified.
Explanation: EWXCMD was started with a blank

command line.
System Programmer Response: Enter the command

again specifying the subchannel.
Source: LANRES

System Programmer Response: Enter a valid
command on the EWXCMD command line.
Source: LANRES
7906E
Time must be between 1 and 3600

seconds.
Explanation: The optional time parameter must be

between 1 and 3600 second.
again specifying a valid time parameter.
Source: LANRES
141
EWX Server Messages

7907E
DROP DISK for subchannel subchannel

on type adapter adapter failed
(RC=return-code).
Explanation: EWXCMD received an error while trying

to drop the requested subchannel.
DROP command failed and take any necessary action.
7912E
Incorrect option on DROP Disk:

options.
Explanation: EWXCMD detected an option on the

command line that was not valid.
with valid options.
Source: LANRES
Source: LANRES
7913E
7908I
DROP DISK was successful.
Incorrect option on Query

Connections: options.
Explanation: EWXCMD successfully dropped the

requested subchannel.


with valid options.
Source: LANRES
Source: LANRES
7909I
Channel device driver is not loaded.
Explanation: EWXCMD was unable to add or delete a

subchannel because no channel device driver was
loaded.
Source: LANRES
7910E
Incorrect command command.
7914E
Incorrect option on Query Mmcstatus:

options.

with valid options.
Source: LANRES
Explanation: EWXCMD detected a command on the

7915E
Explanation: EWXCMD detected a query type on the

Incorrect query type type.
System Programmer Response: Enter a valid

command.
Source: LANRES

with a valid query type.
7911E
Incorrect drop type type.
Source: LANRES
Explanation: EWXCMD detected a drop type on the

7916E
Explanation: EWXCMD detected a start type on the


System Programmer Response: Reenter the
command with a valid drop type.
Source: LANRES
142
Incorrect start type type.

EWX Server Messages

with a valid start type.
Source: LANRES
7917E
Incorrect subchannel subchannel,

subchannel must be even.
Explanation: EWXCMD detected an odd subchannel

on the command line.
specifying an even subchannel.
Source: LANRES
7918E
EWXDISK is not loaded.
7921E
device_name device driver is not

loaded.
Explanation: EWXCMD was unable to display the

device driver version because the requested device
driver is not loaded.
Source: LANRES
7922E
Start for count sessions failed

(RC=return-code).
Explanation: EWXCMD received an error while trying

to start the requested sessions.
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
7919I
device_name Version
version.modification.
Explanation: EWXCMD displays the requested device

drivers version.
7923I
Start for count sessions was

successful.
Explanation: EWXCMD successfully started the

requested sessions.
Source: LANRES

Unexpected character <character> at
non-blank position.
Source: LANRES
7924E
7920E
Explanation: EWXCMD found an unexpected

character while parsing a subchannel list.
Missing adapter number for

subchannel subchannel.
Explanation: A comma was specified on the

command line indicating an adapter number would be
supplied, but the adapter number was not specified.
either removing the comma or specifying a valid adapter
number.
Source: LANRES

with a valid subchannel list.
Source: LANRES
7925E
Invalid adapter specified.
Explanation: An Invalid adapter was specified on the

command.
143
EWX Server Messages

command with a valid adapter number.
Source: LANRES
User Response: Enter the command with the a valid

clear option.
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
Explanation: The clear type was not valid.

command with a device driver.
User Response: Enter the command with a valid clear

type.
Source: LANRES
Incorrect clear type clear-type.
Source: LANRES
7927I
{Add|Delete} successful for subchannel

subchannel on type adapter adapter.
Explanation: The requested add or delete function

completed successfully.
Source: LANRES
7928I
LANRES service level is service_level.
Explanation: Informational message displayed when

the service level is queried. This is the service level
currently running on the NetWare server.
7932E
Not enough resources available to

allocate buffer.
Explanation: EWXCMD tried to allocate a buffer, but

there wasnt enough resources.
System Action: EWXCMD command status is not
processed.
the server.
Source: LANRES

7950I

Source: LANRES
7929I
LANRES service level service_level will

be applied.
Explanation: Informational message displayed when

the service level is queried. This is the service level that
will be applied to the NetWare server the next time
LANRES starts.
Service level service_level was

successfully received.
Explanation: EWXSRVC has successfully received a

new service level from an attached host.
Source: LANRES
7951E
Error receiving service level.
Explanation: An error occurred while receiving

service. See preceding messages to determine exact
cause of error.
Source: LANRES

7930E
No clear type specified.
Explanation: The Logfile to be cleared has not been

specified.
144
System Programmer Response: Review preceding

error messages to determine the cause of failure.
Source: LANRES
EWX Server Messages

7952I
Canceling service level service_level.
Explanation: A host attempted to send an older

service level to the NetWare server.
Source: LANRES
7953E
Incorrect sequence number.
Explanation: An incorrect sequence number was

detected while transferring data.
System Action: The data transfer stops.
7957E
Error removing file filename

(ERRNO=errno).
Explanation: An error occurred while removing the

file.
System Programmer Response: Use the errno to
determine why removing the file failed.
Source: LANRES
7958E
Error renaming file filename1 to

filename2 (ERRNO=errno).
Explanation: An error occurred while renaming the

file.
Source: LANRES
7954E
Unable to create file filename

(ERRNO=errno).

determine why renaming the file failed.
Source: LANRES
Explanation: An error occurred creating the file.

7975E

determine why creating the file failed.
Source: LANRES
7955E
Error writing to file filename

(ERRNO=errno).
Explanation: An error occurred writing to the file.
EWXSTART cannot be loaded while

LANRES is active.
Explanation: LANRES cannot be restarted while

LANRES NLMs are loaded.
User Response: Stop all LANRES NLMs before
restarting.
Source: LANRES

determine why writing to the file failed.
Source: LANRES
7976E
Error opening file filename

(ERRNO=errno).
Explanation: An error occurred while opening the file.

7956E
CRC error.
Explanation: A CRC (cyclic redundancy check) error

occurred while transferring data.

determine why opening the file failed.
Source: LANRES

Source: LANRES
7977E
Unknown error in ProcessBundle

(RC=return-code).
Explanation: An unexpected error occurred with

unpacking the LANRES service.
145
EWX Server Messages

Source: LANRES
7978E
Error opening file filename.
7982E
Error opening output file filename
Explanation: An error occurred opening file filename

while unpacking the service bundle.
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.

System Programmer Response: Determine why an
error occurred while opening the file.
Source: LANRES
7983E
Source: LANRES
7979E
Invalid header format in file filename.
Explanation: An invalid header was found in the

service bundle.
System Programmer Response: Remove the service
bundle from the NetWare server. If the problem
reoccurs, disable service distribution on the host with
the incorrect service bundle.
Explanation: An error occurred while reading the

header information from the service bundle.
System Programmer Response: Load EWXSTART
again. If the problem persists, remove the service
bundle from the NetWare server and the host.
Source: LANRES
7984E
Source: LANRES
7980I
Unpacking file filename from bundle

bundlename.
Explanation: File filename was successfully extracted.

Source: LANRES
7981E
CRC error unpacking file filename from

bundle bundlename.
Explanation: A CRC (cyclic redundancy check)

occurred while unpacking the file filename.
System Programmer Response: Remove the service
bundle from the NetWare server. If the problem
reoccurs, disable service distribution on the host with
the incorrect service bundle.
Source: LANRES
Error reading header from bundle

bundle_name (RC=return-code).
Error reading from bundle bundle_name

(RC=return-code).
Explanation: An error occurred while reading data

from the service bundle.
System Programmer Response: Loading
EWXSTART again. If the problem persists, remove the
service bundle from the NetWare server and the host.
Source: LANRES
7985E
Error writing file filename

(RC=return-code).
Explanation: An error occurred while writing to a file

extracted from the service bundle.
cause of the write error and start EWXSTART again.
Source: LANRES
7986E
Error initializing expansion routine.
Explanation: An error occurred while initializing the

service unpacking routines.
146
EWX Server Messages

System Programmer Response: If the server is
indicating a memory shortage, unload any unused
NLMs or add more memory to the server. Restart
EWXSTART.
Source: LANRES
7987E
Unable to set time for file filename

(ERRNO=errno).
Explanation: An error occurred when changing the

time stamp for the file.
determine why changing the time stamp for the file
failed.
Source: LANRES
7988E
Cannot determine language type for

file filename.
Explanation: The application was unable to determine

the installed language type. The service bundle may be
defective or the message repository is not where it is
expected or the name has been changed.
Source: LANRES
8001E
LANRES object already exists.
Explanation: The LANRES object cannot be added

because it already exists in the NetWare servers
bindery.
System Action: Execution of the command is
stopped. The system status remains the same.
System Programmer Response: The password for
the LANRES object can be changed using the
EWXLOBJ CHANGE command. The LANRES object
can be deleted using the EWXLOBJ DELETE command
and a new LANRES object can be added using the
EWXLOBJ ADD command.
Source: LANRES
8002E
LANRES object does not exist.
Explanation: The LANRES object cannot be deleted

because it cannot be located in the NetWare servers
bindery.
stopped. The system status remains the same.

NetWare server is being used.
System Programmer Response: Unload all the

LANRES NLMs. Reload the LANRES product from
diskette. If the problem persists, contact an IBM service
representative.
Source: LANRES
8003E
Source: LANRES
7989I
Service was successfully applied.
Explanation: The previously received service bundle

was processed successfully.
Source: LANRES
7990E
Error(s) occurred while applying

service.
Explanation: One or more errors occurred while

processing the previously received service bundle
successfully.
System Programmer Response: See the previous
messages to determine what errors occurred.
Required parameter, PASSWORD or

NEWPASSWORD, not specified.
Explanation: The PASSWORD or NEWPASSWORD

parameter must be specified. If neither one of these
parameters is specified, then both passwords will
default to null passwords which would be the same.
NetWare requires the new password be different from
the current password.
stopped.
Source: LANRES
8004E
Cannot login to LANRES object on

server servername. Unknown server or
LANRES object does not exist.
Explanation: The servername server cannot be found

or the LANRES object does not exist in that servers
bindery.
147
EWX Server Messages

stopped.
server is being used.
Source: LANRES
8005E
Cannot login to LANRES object on

server servername. Access denied.
8009I
Password for LANRES object on server

server has been changed.
Explanation: The password for the LANRES object in

server server has been changed.
Source: LANRES
Explanation: The servername server denied the login

attempt to the LANRES object in its bindery. The most
probable cause is an incorrect password.
8010I

stopped.
Explanation: The LANRES object has been made a

user of the print queue.
System Programmer Response: Verify the password

specified is correct.
Source: LANRES
8006E
The new password is a duplicate of the

current password.
Explanation: NetWare requires the new password be

different from the current password.
LANRES object has been made a user

of print queue queue.

Source: LANRES
8011E
Print queue queue does not exist.
Explanation: The Queue does not exist.


stopped.
User Response: Enter the command with the correct

Queue name.

Source: LANRES
Source: LANRES
8007I
LANRES object has been added.
Explanation: The LANRES object has been added to

the NetWare servers bindery.
Source: LANRES
8008I
LANRES object has been deleted.
Explanation: The LANRES object has been deleted

from the NetWare servers bindery.
Source: LANRES
148
Chapter 3. EZM Application Enabling Technology Messages

EZM077E
The specified service source is not

valid.
Explanation: The source of the service must be either

file or tape and neither was specified.
User Response: If you have the source to the
program that invoked the API, verify that the
EZMSMS20_SOURCE field is being filled in properly.
System Programmer Response: If you have the
source to the program that invoked the API, verify that
the EZMSMS20_SOURCE field is being filled in
properly.
EZM078E
An error occurred attempting to access

the specified source file.
Explanation: When the command attempted to

retrieve the service package file from the file system, an
error occurred.
User Response: Verify the correct file name was
supplied. Examine the permission bits to verify the
system has access to the file and reissue the command.
file name was supplied. Examine the permission bits to
verify the system has access to the file and reissue the
command.
EZM079E
Service source was specified as file,

but no filename was provided.
Explanation: If you have the source that invoked the

API, verify that filename is being properly placed in the
EZMSMS20_FILENAME field when
EZMSMS20_SOURCE specifies file.
User Response: Reissue the command or contact the
owner of the command.
System Programmer Response: Reissue the
command or contact the owner of the command.
EZM080E
The specified application is not known

to the system
Explanation: The command must specify the name of

the application as it is known to the system. If you are
not sure of this name, contact the owner of the
application.
User Response: Reissue the command supplying the
name of an application that is known to the system.
command supplying the name of an application that is
known to the system.
EZM081E
An error occurred accessing the

service data, reason = %d.
Explanation: While attempting to retrieve the service

information from the indicated source, an error occurred.
The problem may be a system error or a problem with
the service package itself.
System Programmer Response: Contact the supplier
of the service package.
EZM082E
The length of the application name is

not valid.
Explanation: An application name cannot exceed

eight characters in length.
User Response: Verify the application name specified
is less than eight characters. Contact the owner
provider of the application if you are not sure what
name to specify.
application name specified is less than eight characters.
Contact the owner provider of the application if you are
not sure what name to specify.
EZM083E
Unable to determine length of source

file.
Explanation: An error occurred attempting to

determine the length of the specified file.
User Response: Contact the supplier of the service
package.
System Programmer Response: Contact the supplier
of the service package.
EZM084E
The length of the source file name is

not valid.
Explanation: The length of the specified file name

exceeded the maximum allowed limit for a file name.
User Response: Reissue the command specifying a
path whose length does not exceed the maximum file
length limit.
command specifying a path whose length does not
exceed the maximum file length limit.
EZM085E
The source file path must be fully

qualified.
Explanation: The source file name must begin with a

/.
149
EZM Application Enabling Technology Messages

complete path to the file.
command specifying a complete path to the file.
EZM086E
The user or group name must not

contain the string EZM.
Explanation: Userids and group names containing the

string EZM are reserved.
User Response: Specify a different userid or group
name.
System Programmer Response: Specify a different
userid or group name.
EZM087E
The application specified is not defined

to the system.
Explanation: The application name specified on the

command is not defined to the system.
valid application name or install the application.
command specifying a valid application name or install
the application.
EZM088E
The file contains an empty segment
Explanation: The tcpactn file is divided into segments

by a special line of text. Two of these lines were found
on together. This would cause one of the file segments
to be empty which is not valid.
User Response: Either remove an extraneous file
segment line or provide contents for the empty file
segment.
System Programmer Response: Either remove an
extraneous file segment line or provide contents for the
empty file segment.
EZM089E
The file contains a line which is too

wide
Explanation: A tcpactn file may not contain lines

greater than 80 bytes long (not including the new-line
character).
User Response: Find the line which is too long and
split it into two lines or remove extraneous characters
which cause it to be too wide.
System Programmer Response: Find the line which
is too long and split it into two lines or remove
extraneous characters which cause it to be too wide.
150
EZM090E
The list operation has no parameters.
Explanation: No parameters are needed for the list

operation.
User Response: Enter the list operation without
parameters.
System Programmer Response: Enter the list
operation without parameters.
EZM091E
Parameter entered must be lower case.
Explanation: Parameters entered must be lower case.

User Response: Enter parameters in lower case.
System Programmer Response: Enter parameters in
lower case.
EZM092E
Specified command not found.
Explanation: The system was unable to cancel the

command whose SARID (System Administration
Request Identifier) was specified because it could not
find an active command with that identifier. Either the
command finished before it could be cancelled, or the
specified SARID is not valid.
User Response: Verify the command you wish to
cancel is still running and that the SARID you specified
is correct.
System Programmer Response: Verify the command
you wish to cancel is still running and that the SARID
you specified is correct.
EZM093E
This command was cancelled
Explanation: The system administration command

service, ezmcmd, was used to cancel this command.
EZM094E
The user must not connected to the

specified primary group
Explanation: Before a new primary group can be

specified, the user must be connected to the group.
User Response: Use the chuser command to connect
the user to the group, then reissue the chuser command
to make the group the primary group.
System Programmer Response: Use the chuser
command to connect the user to the group, then reissue
the chuser command to make the group the primary
group.

EZM095E
Unable to delete this userid.
EZM100I
Command processing was successful.
Explanation: This userid either does not exist or is a

system id and cannot be deleted.
Explanation: All operations for this command were

User Response: Specify the name of a user that

exists and can be deleted.
System Programmer Response: Specify the name of

a user that exists and can be deleted.
EZM096I
No information found for specified

user(s).
Explanation: No information was found for the user(s)

specified.
User Response: Specify the name of a user that
exists.
a user that exists.
EZM097I
No information found for specified

group(s).
Explanation: No information was found for the group

name(s) specified.
User Response: Specify the name of a group that
exists.
a group that exists.

EZM101E
Explanation: A structure passed by the command to

the system administration API was invalid.
User Response: Report the error and reason code to
the owner of the command issued.
System Programmer Response: Report the error and
reason code to the owner of the command issued.
EZM102E
User Response: Contact the system program to

obtain authority if required.
System Programmer Response: Determine if the
user should have authority to the command and grant it
if appropriate.
Owner userid specified is not valid.
Explanation: The userid specified as the owner of the

group is not valid.
User Response: Supply a userid which can be used
to own the group.
System Programmer Response: Supply a userid
which can be used to own the group.
EZM099I
TCP/IP Definition file contained too few

sections
Explanation: The TCP/IP definition file provided to the

tcpact command must have the correct number of
sub-sections.
User Response: Provide the command with a file
containing the correct number of sub-sections.
System Programmer Response: Provide the
command with a file containing the correct number of
sub-sections.
Insufficient authority to issue this

command.
Explanation: You do not have sufficient authorization

to perform this function.
EZM103E
EZM098E
Command error occurred, structure not

valid, reason code = nn
An internal error occurred while

processing the command, reason code
= nnn
Explanation: An internal problem prevented execution

of the command. The reason code displayed is the
primary reason code from the request management
block (EZMSARMB).
User Response: Report the problem to IBM.
EZM104E
The system administration server is

terminating.
Explanation: During processing of the command the

system administration server entered termination
processing. This could be a normal or abnormal
termination. Your command was cancelled.
User Response: Retry the command when the server
has restarted.
System Programmer Response: If the termination of
the server was unexpected, possibly determine why the
termination occurred and/or report the problem to IBM.
151

EZM105E
Command processing error, reason =

xxxx
Explanation: An problem was encountered in the

processing of the command. The reason code displayed
is the secondary reason code found in the request
specific block (EZMSARSB).
User Response: Report the problem to the owner of
the command.
EZM106E
Unable to obtain storage
Explanation: The command was unable to obtain

storage for the request management block
(EZMSARMB) or request specific block (EZMSARSB).
the command.
EZM107I
Userid not defined to the system.
Explanation: The userid specified is not defined to the

system.
User Response: Retry the command with the correct
userid.
System Programmer Response: Retry the command
with the correct userid.
EZM111A
Enter the new password
Explanation: The command is prompting you to enter

the new password for the user.
User Response: Enter the new password (1 to 8
characters long) and press enter.
System Programmer Response: Enter the new
password (1 to 8 characters long) and press enter.
Default string will be used
Explanation: No text was entered on the command,

so the default string will be used by the command.
User Response: None unless you entered text in
which case report the problem to the owner of the
command.
System Programmer Response: None unless you
entered text in which case report the problem to the
EZM108I
EZM110E
EZM112E
No userid specified
Explanation: The userid whose password is to be

changed must be specified as a parameter to the
command.
User Response: Reissue the command specifying the
userid whose password you wish to change.
command specifying the userid whose password you
wish to change.
The following text will be echoed
Explanation: This message will be followed by the

text which is being used for the function. It may be the
default string or the string entered on the command
which may be truncated if it is too long.
User Response: None unless the following text is not
what you expected in which case report the problem to
the owner of the command.
EZM113E
Too many parameters specified
Explanation: More parameters were specified than

are allowed for this command.
User Response: Reissue the command with the
correct number of parameters.
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
EZM109E
Explanation: The length of the specified userid is

incorrect. It must be 1 to 8 characters long.
An internal command error occurred.
Explanation: The front end processing for the

command encountered an internal error not related to
the system administration server.
the command.
to the owner of the command.
Userid length not valid
User Response: Reissue the command with a userid

of the correct length.
command with a userid of the correct length.
EZM115E
No new password specified
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.
152

command and respond to message EZM111A with a
valid password.
EZM116E
Password length not valid
Explanation: The password must be 1-8 characters

long.
User Response: Reissue the command and respond
to message EZM111A with a valid password.
command and respond to message EZM111A with a
valid password.
EZM117E
The specified file system name is not

valid.
Explanation: The command is unable to locate the file

system whose name was specified.
User Response: Specify a valid file system name.
System Programmer Response: Specify a valid file
system name.
EZM121E
Explanation: During the process of restoring from

tape, an error message was issued.
User Response: The restore failed. Try another
backup tape if one exists or contact the owner of the
command for more information.
System Programmer Response: The restore failed.
Try another backup tape if one exists or contact the
owner of the command for more information.
EZM122I
A warning was issued during dump

processing.
Explanation: While dumping to tape a warning

message was issued.
User Response: Consider executing the dump again
as it may not be valid.
System Programmer Response: Consider executing
the dump again as it may not be valid.
EZM123E
EZM118E
An error occurred during restore

processing.
Unable to write to write-protected tape
An error occurred during dump

processing.
Explanation: The command must write to a tape and

the mounted tape is write-protected.
Explanation: While dumping to tape an error message

was issued.
User Response: Remount the tape with the write

protect turned off or use another tape.
User Response: The dump failed. Try another tape or

contact the owner of the command for more information.
System Programmer Response: Remount the tape

with the write protect turned off or use another tape.
System Programmer Response: The dump failed.

Try another tape or contact the owner of the command
for more information.
EZM119A
Mount a tape
Explanation: A tape needs to be mounted for the

command to continue processing.
User Response: Mount a tape.
System Programmer Response: Mount a tape.
EZM124E
Error initializing tape
Explanation: While attempting to initialize the tape

prior to use an error occurred.
User Response: Try another 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

tape, a warning message was issued.
Explanation: The function value is not a valid

selection.
User Response: Examine the restored file system.

The restore may or may not have been successful.
User Response: Specify a valid function value.

restored file system. The restore may or may not have
been successful.
System Programmer Response: Specify a valid

function value.
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.
153

System Programmer Response: Specify the correct
required parameters for the command.

group name.
EZM127E
EZM133E
Required parameter missing.
Explanation: A required parameter for this command

was not supplied.
User Response: Specify the required parameter.
System Programmer Response: Specify the required
parameter.
EZM128E
Specified file system name has

incorrect length
An unknown group name was

specified.
Explanation: The group that was specified is not

defined to the system.
User Response: Specify a valid group name.
group name.
EZM134E
The owner specified is not valid.
Explanation: A file system name must be 15

characters long.
Explanation: The specified owner userid was not

valid.
User Response: Specify a valid owner userid.

system name.

owner userid.
EZM129E
EZM135E
Format of specified file system name is

not valid.
Explanation: The name specified is not in the form

required for a file system
system name.
EZM130E
The length of the specified function is

not valid.
Explanation: The specified function contains too many

or too few characters to be a valid value.
User Response: Specify a valid function value
function value
EZM131E
Keyword must be specified in lower

case
Explanation: All keywords are in lower case. The

specified value contained upper case characters.
User Response: Specify a valid keyword in lower
case.
keyword in lower case.
The specified groupname is not valid.
Explanation: A group name was specified that is not
usable.
User Response: Specify a valid group name.
154
Specified GID is not in the valid range
Explanation: The specified gid value is not in the

range of valid gids.
User Response: Specify a valid gid.
System Programmer Response: Specify a valid gid.
EZM136E
The combination of SU and id values is

not valid.
Explanation: You cannot specify SU=N (the default)

and id=0.
User 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
command.
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
command.
EZM137E
Cannot change/delete reserved system

groups
Explanation: The specified group is a reserved

system group and cannot be modified.
User Response: Specify another group to
change/delete.
System Programmer Response: Specify another
group to change/delete.

EZM138E
Duplicate parameters specified.
EZM144E
Owner parameter length is not valid.
Explanation: The same keyword was specified more

than once.
Explanation: The owner name parameter specified on

the command is too long.
User Response: Reissue the command without

specifying the same keyword more than once.
User Response: Specify a valid owner name on the

command.

command without specifying the same keyword more
than once.

owner name on the command.
EZM145E
EZM139E
Syntax Error
No value was specified for the gid

keyword
Explanation: The command was issued with invalid

syntax.
Explanation: The gid keyword was specified, but no

value was supplied
User Response: Reissue the command using the

proper syntax.

value for the gid keyword.

command using the proper syntax.

command specifying a value for the gid keyword.
EZM140E
EZM146E
Final parameter should be the group

name
Explanation: The last parameter on the command

was not the group name for the command to operate
on.
User Response: Specify the desired group name as
the final parameter.
System Programmer Response: Specify the desired
group name as the final parameter.
Explanation: The owner keyword was specified, but

no value was supplied
value for the owner keyword
command specifying a value for the owner keyword
EZM147E
EZM141E
Specified keyword is not valid.
Explanation: An unrecognized keyword was specified

on the command.
No value was specified on the owner

keyword
ALL is not a valid parameter value
Explanation: The value ALL may not be specified on

this command.
User Response: Specify only valid keywords.
User Response: Reissue the command using specific

values.
System Programmer Response: Specify only valid

keywords.

command using specific values.
EZM142E
EZM148E
The length of the specified gid is not

valid.
Explanation: The gid specified on the command is too

long.
User Response: Specify a valid gid.
Nothing to change was specified
Explanation: No parameters to change were

specified.
User Response: Specify something to change
System Programmer Response: Specify a valid gid.
System Programmer Response: Specify something

to change
EZM143E
EZM149E
Group parameter length is not valid.
No value entered for a keyword
Explanation: The group name parameter specified on

the command is too long
Explanation: A keyword was specified without an

accompanying value
User Response: Specify a valid group name on the

command.
User Response: Enter a value for the keyword

group name on the command.
System Programmer Response: Enter a value for

the keyword
155

EZM150E
The value entered after a keyword is

not valid.
Explanation: The value entered after a keyword was

invalid
User Response: Specify a valid value for the
keyword.
value for the keyword.
EZM156E
Explanation: The command was unable to delete the

user from the groups listed
User Response: Reissue the command properly
specifying the desired groups.
command properly specifying the desired groups.
EZM157E
EZM151E
A parameter length is not valid.
Explanation: The length of one of the parameters is

invalid
User Response: Specify all parameters with correct
lengths.
System Programmer Response: Specify all
parameters with correct lengths.
EZM152E
The length of the userid parameter is

not valid.
Explanation: The userid specified is too long.

User Response: Specify a userid with a valid length.
System Programmer Response: Specify a userid
with a valid length.
EZM153E
No userid was supplied
Explanation: The command requires a userid

parameter and one was not specified.
User Response: Specify a userid.
System Programmer Response: Specify a userid.
EZM154E
Unable to determine the default

primary group
Delete failed for groups: xxxxx,xxxx...
Userid entered is not valid.
Explanation: The specified userid is not valid.

User Response: Specify a valid userid.
userid.
EZM158E
Tried to add too many groups
Explanation: More groups were specified to be added

than are permitted by the command.
User Response: Reissue the command specifying
fewer groups to be added.
command specifying fewer groups to be added.
EZM159E
Tried to delete the user from too many

groups
Explanation: More groups were specified for the user

to be deleted from than are permitted by the command.
fewer groups.
command specifying fewer groups.
EZM160E
Specified uid is not valid.
Explanation: The command was unable to determine

the default group to use for the prgrp command.
Explanation: The uid specified on the command is not

valid.
User Response: Report the error to the owner of the

command.

valid uid.
System Programmer Response: Report the error to


command specifying a valid uid.
EZM155E
EZM161E
Connect failed for groups:

xxxxx,xxxx...
Explanation: The command was unable to connect

the user to the groups listed
User Response: Reissue the command properly
specifying the desired groups
command properly specifying the desired groups
156
Group name to connect to is not valid
Explanation: A group name specified for the user to

be connected to is invalid.
valid group names
command specifying valid group names

EZM162E
Group name to delete user from is not

valid.
Explanation: A group name specified for the user to

be deleted from is invalid.
valid group names
command specifying valid group names
EZM163E
Specified primary group is not valid.
Explanation: The group name specified for the new

primary group is invalid
User Response: Specify a valid primary group name.
primary group name.
EZM164E
Specified su parameter is not valid
Explanation: The value specified for the su parameter

is invalid.
User Response: Specify a valid value for the su
parameter.
System Programmer Response: Report the error to

EZM168E
An incorrect tape was mounted. Mount

the correct tape.
Explanation: The label on the tape indicates that this

tape does not contain the required information.
User Response: Mount a valid tape for this command.
System Programmer Response: Mount a valid tape
for this command.
EZM169E
The source and destination values are

required.
Explanation: The source and destination values must

be specified and at least one was not.
proper syntax.
EZM170E
Unable to obtain current userid.

value for the su parameter.
Explanation: To process the command, the current

userid must be obtained and the command was unable
to do this successfully.
EZM165E

the command.
Specified gecos parameter is not valid.
Explanation: The value specified on the gecos

parameter is not valid.

to the owner of the command.
User Response: Specify a valid value for the gecos

parameter.
EZM171E

value for the gecos parameter.
Explanation: A title must be specified for the captured

diagnostics
Missing required title
User Response: Specify a title

EZM166E
Combination of source and destination

is not valid.
System Programmer Response: Specify a title
Explanation: The selected combination of source and

destination values is invalid.
EZM172I
User Response: Specify compatible source and

destination values.
Explanation: This flavor of the command does not

require a title to be specified but one was provided. It is
ignored.
System Programmer Response: Specify compatible

source and destination values.
The specified title will not be used.

EZM167I
A warning was issued during

command processing
Explanation: During the processing of the command a

warning was issued while moving files between source
and destination.
User Response: Report the error to the owner of the
command.
EZM173E
Parameter specified is not valid.
Explanation: A parameter was specified that is not a

part of the valid syntax for the command.
proper syntax.
157

EZM174E
Source specified is not valid.
Explanation: The source parameter specifies an

invalid value.
User Response: Specify a valid value for the source
parameter.
value for the source parameter.
EZM179E
Specified destination is not valid.
Explanation: The destination value is not a valid

selection.
User Response: Specify a valid destination value.
destination value.
EZM180E
GID keyword is not valid
Explanation: The syntax of the gid keyword is invalid.

EZM175E
This command has no parameters
Explanation: The command takes no parameters,

however parameters were specified.
User Response: Reissue the command without
specifying parameters.
command without specifying parameters.
EZM176I
Returned information exceeds

available space.
Explanation: The command was unable to allocate

sufficient space to capture information about all the
users/groups requested or to contain all the TCP/IP
configuration data.
User Response: Reissue the command requesting
information about fewer users/groups or provide a larger
buffer in the EZMSARSB.
command requesting information about fewer
users/groups or provide a larger buffer in the
EZMSARSB.
EZM177E
Parameter must be uppercase
Explanation: The parameter to this command must be

in upper case.
proper syntax.
EZM178E
Too many userids/groups specified.
Explanation: The user exceeded the maximum

number of userids/groups which may be specified on
this command.
fewer userids/groups.
command specifying fewer userids/groups.
158

proper syntax.
EZM181E
The first parameter must be the gid.
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
correctly specified in the first parameter.
proper syntax.
EZM182E
Input Error
Explanation: An error occurred parsing the input to

the command.
User Response: Verify the syntax passed to the
command was valid.
System Programmer Response: Verify the syntax
passed to the command was valid.
EZM183E
Unable to open file
Explanation: The command failed attempting to open

the output file specified.
file with a valid path that you have authority to open.
command specifying a file with a valid path that you
have authority to open.
EZM184E
A specified index is not valid.
Explanation: The specified index is not valid.

valid index.
command specifying a valid index.

EZM185E
Missing index or filename
Explanation: The command syntax requires an index

and file name to be specified on the detailed form of the
command.
User Response: Reissue the command with the
proper syntax.
index of the error of interest and a file name for the

information to be written to.
User Response: Reissue the command as
appropriate if desired.
command as appropriate if desired.

command with the proper syntax.
EZM191A
EZM186E
Explanation: The command is verifying that you are

sure you wish to shutdown the system at this time.
Text is too long. It will be truncated.
Explanation: The text entered exceeds the maximum

length. It will be truncated.
User Response: Reissue the command with less text
or accept the truncated version.
command with less text or accept the truncated version.
EZM187E
Unable to write to file
Explanation: The command is unable to write to the

output file
file which can be written to.
command specifying a file which can be written to.
EZM188E
An error occurred closing the file
Confirm you wish to continue with

system shutdown (Y/N):
User Response: Respond Y to continue with

shutdown and N to not shutdown.
System Programmer Response: Respond Y to
continue with shutdown and N to not shutdown.
EZM192E
The confirmation response is not valid.
Explanation: Respond to prompt with a Y or N.

User Response: Respond to prompt with a Y or N.
System Programmer Response: Respond to prompt
with a Y or N.
EZM193I
Command processing terminated.
Explanation: The command does not continue to

process your request.
Explanation: While attempting to close the output file,

an error occurred.
User Response: Examine the contents of the output

file. If the contents are correct, ignore the error,
otherwise report the problem to the owner of the
command.
EZM194E

contents of the output file. If the contents are correct,
ignore the error, otherwise report the problem to the
EZM189I
Explanation: The command requires you to specify

which TCP/IP definition set you wish to active.
TCP/IP definition set identifier.
command specifying a TCP/IP definition set identifier.
No diagnostic information to display
Explanation: The command was unable to locate any

diagnostic information to report.
EZM190I
No TCP/IP definition identifier was

supplied.
Reissue the command with an index

and output file name for more
information.
Explanation: To receive more information about a

particular error, reissue the command specifying the
EZM195A
Are you sure you want to recycle

TCP/IP now? All users will be
terminated. Reply Y/N.
Explanation: Respond Y to terminate all users and

recycle TCP/IP using the definition set you specified.
Respond N to abort the command.
User Response: Respond Y to terminate all users
and recycle TCP/IP using the definition set you
specified. Respond N to abort the command.
System Programmer Response: Respond Y to
terminate all users and recycle TCP/IP using the
159

definition set you specified. Respond N to abort the
command.
EZM201I
EZM196E
Explanation: Automated service application requires a

re-IPL to occur
Error opening TCP/IP definition file.
Explanation: An error occurred opening the specified

TCP/IP definition file.
User Response: Verify the file exists or specify
another file.
System Programmer Response: Verify the file exists
or specify another file.
EZM197E
Error closing TCP/IP definition file.
Explanation: An error occurred closing the specified

TCP/IP definition file.
User Response: Verify the file exists or specify
another file.
System Programmer Response: Verify the file exists
or specify another file.
The service apply needs to shutdown

the system and reIPL.
System Action: Control Center process should re-IPL

the system
Operator Response: None.
Detecting Module: EZMSAWTO
EZM202I
Installing appl_name service step step

of totalstep
Explanation: This message is issued as a status

update as progress is made in applying service.
In the message text:
appl_name
Application name
step
EZM198E
Unable to determine length of TCP/IP

Definition file.
Explanation: The command was unable to determine

the length of the specified TCP/IP definition file.
User Response: Examine the definition file to ensure
it is not corrupted. Report the problem to the owner of
the command.
definition file to ensure it is not corrupted. Report the
problem to the owner of the command.
Current Step
totalstep
Total Steps
System Action: Service apply processing continues
until all steps are complete or an error occurs
EZM203I
EZM199I
No captured diagnostic information

was found
Explanation: No captured diagnostic information was

found on the system.
Control Center needs to download its

code and recycle.
Explanation:
Control Center
downloaded to
Control Center
The service includes an update to the

code. The new code needs to be
the Health Monitor platform and the
should recycle to use the new code

EZM200I
Service apply is complete or was not

needed.
Explanation: Automated service application completed

or was not necessary.

EZM220E
appl_name Service level of newlevel

cannot be installed on oldlevel
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
attempted to regress to a previous level which is not
supported via this process.
160

appl_name
Application name
newlevel
New Service Level
oldlevel
Previous Service Level
System Action: Service apply processing stops. The
system must be restored from backup tapes.
System Programmer Response: Restore the system
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.
Explanation: An error occurred during service

application processing. The system attempted to repeat
an install step which is not allowed.
appl_name
Application name

EZM223I
System restore is complete.
Explanation: Processing following restore of the

system from tape is complete.
System Action: Automation will now make the system
available for use
EZM224E
Restore system/HFS failed. Preceding

messages should detail the error.
Explanation: Job EZMHFSRS used to restore the

HFS systems files failed.
System Action: System restore processing stops.
Automation stops thus stopping the start of any
subsystems.
step
Current processing step
totalstep
Total number of steps
EZM222E
appl_name Service REXX

EZMSRVrexxid failed with a return code
of returncode. A preceding message
should detail the error.
Explanation: An exec involved in processing service

application failed.
appl_name
Application name
rexxid
Last two characters of the Rexx exec name
returncode
The return code from the exec
System Programmer Response: Look at the

SYSLOG or dataset EZM.JOBOUT.EZMHFSRS to
determine why the EZMHFSRS job failed.
EZM300I
Have automation switch NETVIEW log
Explanation: Automation needs to switch to a new

Netview log
System Action: Automation switches to a new
Netview log
EZM301I
Invalid message or fillins: text
Explanation: Automation was requested to issue an

undefined message or a valid message without the
required fillins.
System Action: The error is returned to the issuer of
the message.
161

EZM302I
Automation job was successful
Explanation: A job started by automation has

System Action: Job is terminated. Automation
continues with next step. Used when applying service.
EZM303I
Automation job failed
Explanation: A job started by automation has

completed but errors were detected.
appl_name
Application name
operation
Operation completed on the Application name
EZM307I
parameter was not specified.
Explanation: The required parameter was not left out

in the call to the EZMAPP REXX.
System Action: Job is terminated. Automation will

issue other messages indicating what actions should be
taken. Used when applying service.
parameter
Parameter name
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
be omitted.

EZM304I
Build dump summary for: text
Explanation: Automation has found that a dump

dataset does not have a summary dataset associated
with it.
System Action: Automation builds a summary report
dataset in the form dump_dataset_.Rnnn .
EZM305I
nnn Application(s) Found
Explanation: This is the first line in a multi-line

message listing all the applications installed and
activated on the system. The second line is a title line.
The third and remaining lines list the application name,
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.
EZM306I
appl_name has been operation
Explanation: The specified operation has been

performed successfully on the application.
162

EZM308I
Status not specified or is not I or A
Explanation: An application is being added to the

application list by the EZMAPP REXX. However, the
status of the application was not specified or was not I
or A.
System Action: The application is not added to the
application list.
REXX. The parameters are Operation_to_be_performed
Application_name Application_REXX Application_status.
EZM309I
Cannot do that operation to that

application.
Explanation: An operation is trying to be performed

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.
System Action: The requested operation is not done
to the application.
Operator Response: Perform the proper operation on
the application. Use Install followed by activate, then
deactivate, and lastly uninstall.

EZM310I
EZM313I
Application not found.
Explanation: An operation is trying to be performed

on an application that does not exist (has not been
installed).
System Action: The requested operation is not done
to the application.
Operator Response: Call EZMAPP REXX with the
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.
Unknown EZMAPP Operation.
Explanation: The EZMAPP REXX is being called to

perform an unknown operation.
System Action: The requested operation is not done.
Operator Response: Call EZMAPP REXX with a
proper operation: LIST, INSTALL, UNINSTALL,
ACTIVATE, DEACTIVATE, QUERY, or REXX.

EZM311I
Application name/rexx must be 8 or

less characters in length.
Explanation: Either the Application name and/or

Application_REXX parameters being specified on the
call to the EZMAPP REXX are greater than 8
characters.
name/rexx
The words Name or REXX
REXX insuring the Application_name and/or
Application_REXX are 8 or less characters in length.
EZM314I
REXX name is already being used to

support another application.
Explanation: An operation is trying to be install an

application. However, the REXX name specified on the
call to EZMAPP is already in the application list to
support another application. The REXX name must be
unique.
System Action: The requested operation is not done.
Operator Response: Call EZMAPP REXX with the
LIST operation to determine the application that is using
the REXX name. Determine if the correct REXX names
are being used. Two applications cannot use the same
REXX.

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

EZM315I
EZMKILL PARAMETERS: ? - DISPLAY

THIS HELP TEXT NETVIEW NOAUTO PREVENT AUTOMATIC RESTART OF
NETVIEW/EZMAUTO. NETVIEW AUTO RESTART NETVIEW/EZMAUTO IF IT
TERMINATES. JESCOLD - SET THE
NETVIEW VARIABLES SUCH THAT
WHEN JES2 IS STARTED AGAIN IT
WILL BE A COLD START. JESWARM SET THE NETVIEW VARIABLES SUCH
THAT WHEN JES2 IS STARTED AGAIN
IT WILL BE A WARM START. RESTHFS
- SET THE NETVIEW VARIABLES
SUCH THAT WHEN NETVIEW IS
RECYCLED OR IPL, RESTORE THE
HFS SYSTEM FILES. NORESTHFS SET THE NETVIEW VARIABLES SUCH
THAT WHEN NETVIEW IS RECYCLED
OR IPL, DO NOT RESTORE THE HFS
FILES. CLPAON - MODIFY IEASYS00
TO CLEAR LPA DURING THE NEXT
IPL. LONG IPL. CLPAOFF - MODIFY
IEASYS00 TO NOT CLEAR LPA
DURING THE NEXT IPL. SHORT IPL.
SET SUBSYS ON/OFF - TURN ON/OFF
SYSTEM AUTOMATION FOR A
SUBSYSTEM RESTART SUBSYS CHANGE STATE OF SUBSYSTEM TO
RESTART. RECYCLE SUBSYS - STOP
A SUBSYSTEM AND RESTART IT.
SUBSYS=subsys subsys subsys subsys
subsys subsys
Explanation: Describes the options available on the

EZMKILL command
subsys
Supported Subsystems
EZM316I
count Application(s) Found NUMBER

NAME REXX STATUS count appname
rexxname status
Explanation: This is the first line in a multi-line

message listing all the applications installed and
activated on the system. The second line is a title line.
The third and remaining lines list the application name,
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.
Lists the installed and active applications.
164
count
The number of applications
appname
Application name
rexxname
Application Rexx exec name
status
Application Status: (I)nstalled or (A)ctive
EZM900E
System Administration Structure

Event: module, errno, errno2, errno3
Explanation: An error was detected by the System

Administration Server
module
The detecting module
errno
Primary Error Code
errno2
Secondary Error Code
errno3
Tertiary Error Code
System Action: The request involved in the error or
all active requests may be terminated depending on the
error
Operator Response: None. The System
Administration Server should continue or automatically
recycle depending on the severity of the error
System Programmer Response: None. The System
Administration Server should continue or automatically
recycle depending on the severity of the error
EZM901I
Command Processing Successful
Explanation: A System Administration command

System Action: The successful completion is reported
to the issuer of the command by the System
Administration Structure

EZM902I
Command Processing Failed
Explanation: A System Administration command failed

System Action: The error is reported to the issuer of
the command by the System Administration Structure
EZM906I
System Administration Server Active
Explanation: The System Administration Server has

completed initialization and is available for use
EZM903E
EZM907I
Unable to Issue Requested Message:

msgid Reason Code = rsncode
Explanation: The EZMSAWTO module was invoked to

issue a message but was unable to issue the requested
message.
msgid
Requested Message Id
rsncode
Reason Code
System Action: This message is issued instead.
System Administration Server

Terminated

ended.
System Action: No further system administration
commands may be processed until the server restarts. It
will automatically restart unless the system is shutting
down.

to IBM
EZM904I
Unable to Find an EZMSARSB

expected to have an EZMSARSB control block supplied
to it but could not locate it.
EZM908W
Warning Restoring Dataset
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
of the command.
System Action: The command fails and the command

issuer is notified.
EZM909E

to the owner of the failing command.

restored, an error occurred.

EZM905I
System Administration Server

Initializing

been started
Error Restoring Dataset

the command.
System Action: Initialization continues

EZM910W

dumped, a warning was issued.
Warning Dumping Dataset

of the command.
165

v (EZMKILL RECYCLE TCPIP)
v (EZMSTOP R)
System Action: The text of the command is

processed as a command by automation
EZM911E
Error Dumping Dataset

dumped, an error occurred.

the command.
EZM916E
Explanation: An error occurred attempting to use the

RACF DELUSER command

DELUSER failed

the command.
EZM912E
Error from IEHINITT.
Explanation: An error occurred initializing a tape

the command.
EZM917E

CHUSER failed

RACF ALTUSER command

the command.
EZM913E
ADDUSER failed

RACF ADDUSER command
the command.

EZM918I
MAKESITE failed

TCP/IP MAKESITE command

the command.
EZM914E
Connect failed

RACF CONNECT command
the command.
EZM915I
text
Explanation: The text of the command is processed

as a command by automation
v (EZMSTOP Q)
166

EZM919I
ADRDSSU issued a warning
Explanation: Processing by DFSMSdss resulted in a

warning
of the command.

EZM920I
ADRDSSU failed
EZM925I
LISTGROUP failure.
Explanation: Processing by DFSMSdss resulted in an

error

RACF LISTGROUP command

the command.

the command.
EZM921E
EZM926I
LSUSER failed

RACF LISTUSER command
the command.
text
Explanation: Automation will issue the EZMAPP

command using the text of this message as parameters.
Usually issued as a WTOR, automation will respond
with the result of the command.
System Action: Automation issues the command.
EZM922I
RUN HOUSKEEPING FOR CPDIAG.

requires automation housekeeping to be run
System Action: Automation begins housekeeping
processing.
EZM923I
HOUSKEEPING TASK FINISHED.
Explanation: Automation housekeeping has

completed.
System Action: A command which is waiting for
housekeeping to complete may continue.
EZM927I
cpserve error copying from

SYS1.EZMAPP.SERVICE
Explanation: During processing of the cpserve

command, an attempt is made to copy the application
exec, the EZMSRV01 exec, and the EZMSR01 proc
from SYS1.EZMAPP.SERVICE. This message indicates
that one of these copies failed.
System Action: cpserve processing is ended. The
error is returned to the issuer of the cpserve command.
EZM928I
cpserve error restoring

SYS1.EZMAPP.SERVICE
Explanation: An error occurred processing the

showdiag command.
Explanation: During processing of the cpserve

command, an attempt is made to restore
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
service was located). This restore has encountered an
error. Probably the file is not located in the dump
dataset or the dump dataset could not be found.

the command.
System Action: cpserve processing is ended. The

error is returned to the issuer of the cpserve command.

EZM924I
SHOWDIAG failure.
167
168
Chapter 4. GDE Messages

GDE001E
DISTRIBUTED FILEMANAGER TARGET

SYSTEM INITIALIZATION FAILED. text
GDE002I
Explanation: A problem occurred during initialization

of the Distributed FileManager/MVS target function,
which was requested via a START command.
text
One of the following:
null-message-text
A system error occurred. Refer to preceding
error messages to help determine the specific
error and, if applicable, call the IBM Support
Center.
ECSA STORAGE COULD NOT BE OBTAINED. n
HEX BYTES REQUIRED
A request for ECSA storage could not be
fulfilled. n indicates the number of ECSA bytes,
in hexadecimal, required to initialize the
Distributed FileManager/MVS. Increase the
size of ECSA by at least n hexadecimal bytes
and try again.
GDEIGBS COULD NOT BE LOADED. LOAD
ABEND CODE=cccccccc REASON
CODE=reason-code ALIAS NAME=alias-name
The DFM load module GDEIGBS could not be
loaded because of an error detected by the
LOAD function while attempting to obtain the
address of the alias name CSECT. Check the
LOAD abend and reason codes and take
corrective action. If no corrective action solves
the problem, call the IBM Support Center.
(Note that an ABEND code of 99 and a reason
code of 99 is set by the Distributed
FileManager/MVS to indicate that the alias
name loaded was linkedited above 16
megabytes but is required to be linkedited
below 16 megabytes.)
System Action: The Distributed FileManager/MVS
target function is not activated, except in the case
where message GDE006E was issued with CDRA
reason code X'FFFFFFFF'. See message GDE006E for
details.
System Programmer Response: See the abend or
reason codes contained in either the message text or in
any related console messages. If no corrective action
can be taken, contact the IBM Support Center.
Source: Distributed FileManager/MVS (DFM/MVS)

CONVERSATION INITIALIZATION
FAILED FOR ASID=aaaaaaaa
USERID=uuuuuuuu
PRTNRLU=nnnnnnnnnnnnnnnnn
CONVID=cccccccc. text
Explanation: The Distributed FileManager/MVS was

attempting to initialize the DFM target transaction
program (TP) in address space aaaaaaaa in response
to an APPC ALLOCATE request issued from a DFM
source system. The DFM target TP initialization ended
abnormally.
aaaaaaaa
The address space identifier (ASID).
uuuuuuuu
The MVS user ID specified on the conversation
allocation request.
nnnnnnnnnnnnnnnnn
The name of the (partner) logical unit (LU) at which
the DFM source server requesting the conversation
allocation is located.
cccccccc
The conversation ID assigned by APPC to this
conversation.
text
null-message-text
A system error occurred. Refer to preceding
error messages to help determine the specific
error and, if applicable, call the IBM Support
Center.
PRIVATE STORAGE COULD NOT BE OBTAINED.
n HEX BYTES REQUIRED
A request for private storage could not be
fulfilled. n indicates the number of private
storage bytes, in hexadecimal, required to
initiate the conversation. Increase the region
size of the conversation address space by at
least n hexadecimal bytes and tell the DFM
source LU to try again. The region size can be
specified in the TP profile JCL or in the
TPDEFAULT REGION(xx) parameter in the
ASCHPMxx parmlib member.
ECSA STORAGE COULD NOT BE OBTAINED. n
HEX BYTES REQUIRED
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.
169
ATTACH ERROR. ATTACH RTNCD=return-code

An error was detected by the ATTACH function.
Check the ATTACH return code and correct the
problem. Then tell the DFM source LU to try
again.
APPC ERROR. VERB=vvvvvvvv
RTNCD=return-code
An error was detected by an APPC routine.
The name of the APPC verb that was being
processed is supplied along with the return
code from the APPC verb routine. Correct the
problem and tell the DFM source LU to try
again.
System Action: The conversation is ended. If a
system error occurred, an abend is issued, the error is
logged in the logrec data set, and a dump is produced
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.
System Programmer Response: Search problem
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
logrec data set and the dump, if available.
GDE003I

SYSTEM INITIALIZATION COMPLETE
Explanation: Initialization of the Distributed

FileManager/MVS target function was successful.
System Action: The Distributed FileManager/MVS is
available for use.
GDE004E

CENTRAL ADDRESS SPACE FAILED
{IN ASID=aaaaaaaa|ASID=aaaaaaaa
REASON=bbbbbbbb}
Explanation: The main Distributed FileManager/MVS

address space, named DFM, ended abnormally in the
specified address space identifier (ASID).
System Action: The Distributed FileManager/MVS
DSAS ends. The Distributed FileManager/MVS
conversation address spaces continue running. The
system logs the error in the logrec data set and
produces a dump in the SYS1.DUMPnn data set.
reason for the failure and take corrective action. Other
error messages precede this one. Refer to their
documentation for corrective action. DFM must be
restarted to restore full Distributed FileManager/MVS
target function.
GDE005I

SYSTEM {ALREADY ACTIVE|NOT
ACTIVE, START DFM}
Explanation: Either an attempt was made to start the

Distributed FileManager/MVS target system using the
START DFM command, but the target function is
already active or an attempt was made to use the
DFM/MVS, but the target function is not active and
needs to be started.
System Action: If DFM/MVS is already active, the
system ignores the START DFM command. If DFM/MVS
is not active, jobs requiring target DFM function will end
with non-zero return codes.
Operator Response: If DFM/MVS is active, none. If
DFM/MVS is not active, enter a START DFM command.
GDE006E
INVALID [VALUE FOUND FOR]

KEYWORD: kkkkkkkk DISTRIBUTED
FILEMANAGER TARGET SYSTEM NOT
STARTED
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
Character Data Representation Architecture (CDRA).
For example, RC=00010001 is used by CDRA to
indicate that the CCSID is undefined and RC=00060001
is used to indicate that the CDRA resource files needed
for data conversion cannot be located.
System Action: DFM will not be started. There is an
exception when the keyword is CCSID and the return
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
support data conversion.
System Programmer Response: Correct the DFMxx
parmlib member with a correct value for the keyword.
GDE007E
module ERROR INVOKING FUNCTION:

function return_code reason_code
Explanation: During DFM DataAgent processing the

MVS function shown failed with the indicated return and
reason codes .
However, common errors have more specific text. For
example, if the DataAgent routine cant be found in
JOBLIB, STEPLIB, or LPALIB, LOCATING MODULE
DataAgent_routine_name will be substituted for
function, return_code, and reason_code.
System Action: DFM DataAgent processing is
terminated.
Operator Response: Notify your System Programmer.
170
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
172
Chapter 5. GFSA Messages

GFSA320I
NETWORK FILE SYSTEM SERVER

INITIALIZATION FAILED: text
Explanation: text can be:

v VIRTUAL STORAGE IS UNAVAILABLE,
v MAPPING SIDE FILE NOT FOUND,
v MAPPING SIDE FILE HAS INVALID SYNTAX OR
FORMAT,
v ERROR OPENING/READING MAPPING SIDE FILE,
v SIDE FILE SPECIFIED BUT MAPPING IS
DIS-ALLOWED BY INSTALLATION,
v TASK IS NOT APF AUTHORIZED, or
v DFP LEVEL MUST BE DFSMS 1.2 OR HIGHER.
The server could not be initialized. During server
initialization, the server:
Could not obtain virtual storage,
Was not loaded from an APF-authorized library, or
Is running on a system with a release of DFP prior
to OS/390 1.2.
System Action: The Network File System ends.

Operator Response: Before starting the Network File
System, both the OS/390 UNIX System Services MVS
and the TCP/IP address spaces must have successfully
been started.
Source: DFSMSdfp and Network File System Server
GFSA322I
OPENEDITION V_REG FAILED: RV=1

RC=h_digit1, RSN=h_digit2.
Explanation: The Network File System failed to

register.
h_digit1
The return code from OpenEdition V_REG callable
service.
h_digit2
The reason code from OpenEdition V_REG callable
service.
System Action: The Network File System startup

ends.
Operator Response: Notify the system programmer.
System Programmer Response: See the OS/390

UNIX System Services File System Interface Reference
manual for addition details on the return code and
reason code from OpenEdition V_REG callable service.

v If it is a virtual storage problem, increase the region
size.
Operator Response: Contact the system programmer.
v If an APF-authorization problem, APF authorize all

libraries in the STEPLIB DD statement.
Source: OS/390 NFS Server
v If mapping side file is not found, make sure the name

specified in the attribute data set is correct and the
file exists.
GFSA323I
v If mapping side file has invalid syntax, check the part

GFSAPMAP in SYS1.NFSSAMP library for mapping
side file rules.
v If error occurs during opening of the side file, check
to make sure that the side file is not migrated and it
is readable.
v If sfmax=0 then the side file cannot be specified in
the attribute data set.
v If a back-level release of DFP, restart Network File
System Server after installing DFSMSdfp 1.2 or a
later release.
OS/390 NETWORK FILE SYSTEM LOCK

MANAGER (HDZ11TS) WILL NOT
START BECAUSE OMVS(UID(0)) IS
NOT DEFINED.
Explanation: The Network Lock Manager initialization

fails because the Network Lock Manager startup
procedure is not defined as OMVS(UID(0)).
System Action: The Network Lock Manager
terminates.
User Response: Define Network Lock Manager
startup procedure as OMVS(UID(0)).
Operator Response: None
Source: OS/390 NFS server, GFSAPRMN
Source: OS/390 NFS server

GFSA324I
GFSA321I

INITIALIZATION FAILED: OPENEDITION
MVS ADDRESS SPACE HAS NOT
BEEN STARTED.
Explanation: The Network File System was not able

to establish successful communication with the
OPENEDITION MVS address space.
OS/390 NETWORK FILE SYSTEM

STATUS MONITOR (HDZ11TS) WILL
NOT START BECAUSE OMVS(UID(0))
IS NOT DEFINED.
Explanation: The Network Status Monitor initialization

fails because the Status Monitor startup procedure is
not defined as OMVS(UID(0)).
173
System Action: The Network Status Monitor

terminates.
User Response: Define Network Status Monitor
startup procedure as OMVS(UID(0)).
Source: OS/390 NFS server, GFSASMSV
GFSA330I
SERVER SHUTDOWN COMPLETE.
Explanation: The system has ended the network file

system server and its associated subtasks.
System Action: Network File System Server ends.
GFSA325I
REQUESTED MEMORY NOT

AVAILABLE.
Explanation: An operation to allocate system memory

failed. If this condition persists, it is for one of the
following reasons:
v The value specified on the REGION parameter is too
small.
v The value specified on the BUFHIGH attribute is too
large.
System Action: The system ends the request.
Network File System Server processing continues.
Application Programmer Response: Do one or both
of the following:
v Increase the region size for the job and step or
started task.
v Decrease the value specified for the BUFHIGH
attribute of the attribute data set.
GFSA331E
RECALL FAILED FOR MIGRATED DATA

SET text.
Explanation: DFSMShsm was unable to recall a data

set because the data movement program DFSMSdss
detected, during restore, that the migrated data set had
internal errors.
text
The data set name.
System Action: The DFSMS/MVS NFS Server
Operator Response: Notify System Programmer for
recovery actions.
System Programmer Response: The data set text
had an internal error when migrated, and cannot be
recalled. Refer to DFSMShsm Message ARC0075E for
appropriate recovery actions.
Source: DFSMS/MVS NFS Server
GFSA328I
DFSMS/MVS 1.2.0 NETWORK FILE

SYSTEM IS NOT APF AUTHORIZED.
Explanation: One or more of the data sets referenced

by the STEPLIB DD statement is not authorized
program facility (APF)-authorized.
System Action: The system ends Network File
System Server startup processing.
Application Programmer Response: Authorize all
libraries in the STEPLIB DD statements.
GFSA329I
SERVER SHUTDOWN IN PROGRESS.
Explanation: The system has started server shutdown

procedures.
System Action: The system continues Network File
System Server ending processing.
Detecting Module: GFSASCAR

GFSA333I
DFSMS/MVS version NETWORK FILE

SYSTEM SERVER fmid IS NOT
STARTED BY A START COMMAND.
Explanation: The system programmer tried to start the

Network File System Server with a command other than
START.
version
The DFSMS/MVS version number, for example:
1.2.0 or VERSION 1.
fmid
The DFSMS/MVS Network File System Server
FMID started, for example: null, (HDZ11SP), or
(HDZ11SM).
System Programmer Response: Start Network File
System Server by entering the START command.
174
GFSA334I
MOUNT HANDLE DATABASE CANNOT

BE READ
Explanation: The Network File System Server has

tried to read the mount handle database but was unable
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.
System Action: System processing continues but in a
degraded mode. Some or all of the directories will not
have been remounted.
System Programmer Response: If this is the first
startup after installation of a new release, the mount
handle database will have to be cleared and the server
restarted, because the format of the mount handle
database is not recognizable by the new release.
Reboot or unmount any previously mounted directories.

System Programmer Response: The mount handle
data sets probably created with incorrect attributes.
Detecting Module: GFSAXFHD
GFSA337I
THE FILE SIZE IS TOO LARGE.

FN=text, OFFSET=h_digit1,
LEN=h_digit2.
Explanation: The Network File System client user

tried to read or write the file text beyond the 4G.
System Action: The request is stopped. An error,
NFSERR_FBIG(27), is returned to the client. Network
File System processing continues.
User Response: Check the file size used. Split into
multiple files and try again.
GFSA344I
GFSA335I
Explanation: The Network File System Lock Manager

is initialized successfully and is started.
MOUNT HANDLE DATA SET CANNOT

BE WRITTEN, EXPECTING LEN
d_digits1 REAL LEN d_digits2, VSAM
R15(DEC) d_digits3 REASON
CODE(DEC) d_digits4 LAST OP(DEC)
d_digits5.
OS/390 NETWORK FILE SYSTEM LOCK

MANAGER (fmid) STARTED
System Action: The Network File System Lock

Manager startup ends and continues processing.
Explanation: The Network File System Server has

tried to write the mount handle data sets but was unable
to do so.
Detecting Module: The Network File System Lock

Manager
System Action: System processing continues but in a

degraded mode. Any further mounts or unmounts are
likely to fail.
GFSA345I

System Programmer Response: The mount handle
data sets have probably become unusable and either
need to be cleared or restored to some previous level,
and then the server has to be restarted. Reboot or
unmount any previously mounted directories.
GFSA336E
MOUNT HANDLE DATA SET CANNOT

BE OPENED, VSAM R15(DEC) d_digits1
REASON CODE(DEC) d_digits2 LAST
OP(DEC) d_digits3.
Explanation: During resource timeout, the Network

File System had tried to open the mount handle data
set for writing but unable to do so. The failing
information in fopen the VSAM kSDS mount handle
data set is the decimal return code d_digits1, the
decimal error code or reason code d_digits2, and the
code for the last operation d_digits3.
Explanation: The network File System Status

Manager is initialized successfully.
System Action: The Network File System Status
Manager startup ends and continues processing.
Detecting Module: The Network File System Status
Monitor
GFSA346I
time_stamp.
Explanation: Displays the current time stamp. This

message is issued when the NFSLOG switches.
GFSA347I
ERROR RETURNED TO CLIENT: RC =

d_digits<string>.
Explanation: The system found an error during

processing.
d_digits
The error code returned by the system.
System Action: The Network File System stops.

User Response: None
OS/390 NETWORK FILE SYSTEM

STATUS MONITOR (fmid) STARTED
string
The meaning of the error code.
175
System Action: The system continues processing.
GFSA361I
Application Programmer Response: None

GFSA348I

SYSTEM SERVER fmid STARTED.
Explanation: The system has initialized the network

file system server and is ready to accept MODIFY
commands from the operator console.
version
The DFSMS/MVS version number, for example:
1.2.0 or VERSION 1.
fmid
The DFSMS/MVS Network File System Server
FMID started, for example: null, (HDZ11SP), or
(HDZ11SM).
NETWORK FILE SYSTEM SERVER IS

SHORT ON STORAGE.
Explanation: This message is displayed to the

operator console when a shortage of virtual storage is
detected.
System Action: Network File System Server
continues processing. The storage constraint might be
relieved when some storage is freed later.
Operator Response: If this message is displayed
repeatedly within a short period of time, stop or cancel
Network File System Server and notify the system
programmer.
System Programmer Response: Do one of both of
the following before restarting Network File System
Server:
v Increase the region size for the step or started task.
v Decrease the value specified for the BUFHIGH
attribute of the attribute data set.
Operator Response: Enter MODIFY commands.

GFSA349I
UNEXPECTED ERROR DETECTED:

string.
Explanation: The network file system server has

encountered a condition that indicates continued
processing will produce undesirable results.
string
Additional debugging information for the

programming support personnel.
System Action: Network File System Server will either

shutdown or end the request and continue processing,
depending on where the error was detected.
System Programmer Response: Contact the IBM
Support Center.
GFSA362I
REGION SIZE WILL NOT

ACCOMODATE BUFHIGH AND
LOGICAL CACHE SPECIFICATIONS.
Explanation: The specifications for the BUFHIGH and

LOGICAL CACHE keywords are not valid.
line_number
The line number on which the specifications
exist.
System Action: The startup for Network File System
Server ends.
System Programmer Response: Either increase the
region size of the job or reduce the value for BUFHIGH
and LOGICAL CACHE.
Source: Network File System Server

GFSA400I
GFSA360I
string.
Explanation: This message displays memory

management statistics.
string
The memory management statistics.
INVALID RECFM SPECIFICATION string.
Explanation: string is the invalid record format

specified in the attribute data set.
System Server processing.
Application Programmer Response: Correct the
attribute data set.

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
176
data set name might be incorrect.

GFSA405I
PARSE FAILED FOR ATTRIBUTE FIELD

- ILLEGAL KEYWORD IN LINE d_digits.
Application Programmer Response: Correct the JCL

for DDNAME NFSATTR. Run the job again.
Explanation: The keyword specified in line number

d_digits of the attribute data set is not a valid attribute
keyword.
d_digits
GFSA402I
READ FAILED FOR THE ATTRIBUTES

DATA SET.
Explanation: An error occurred while the network file

system server was processing the attributes data set.
This message follows other messages that describe the
error in greater detail. The attributes data set is defined
in the JCL for DDNAME NFSATTR.
attributes data set.
GFSA403I
PARSE FAILED IN LINE d_digits string.
Explanation: The parsing of line number d_digits in

the attribute data set failed. This message follows other
messages that describe the error in greater detail.
d_digits
The specified line number.
string
The actual line from the attribute data set that

contains the failure.

attribute data set.
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.
d_digits
attribute data set.

attribute data set.
GFSA406I
MISSING LEFT PARENTHESIS IN LINE

d_digits.
Explanation: An attribute specified on line number

d_digits of the attribute data set is missing a left
parenthesis.
d_digits
attribute data set.
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
parenthesis.
d_digits
attribute data set.
GFSA408I
PARSE FAILED ON NUMBER FIELD IN

LINE d_digits.
Explanation: An attribute with a negative number was

specified on line number d_digits of the attribute data
set.
177
d_digits


GFSA412I

attribute data set.
Explanation: The unit specified in the UNIT attribute

on line number d_digits of the attribute data set is not
valid.
INVALID UNIT SPECIFICATION IN LINE

d_digits.

GFSA409I
INVALID DSORG SPECIFICATION IN

LINE d_digits.
Explanation: The data set organization specified in

the DSORG attribute on line number d_digits of the
attribute data set is not valid or is not supported by the
network file system server.
d_digits
attribute data set.
d_digits
GFSA413I

attribute data set.
GFSA410I
INVALID MODEL SPECIFICATION IN

LINE d_digits.
Explanation: The data set specified in the MODEL

attribute on line number d_digits of the attribute data set
is not valid.
d_digits
attribute data set.
GFSA411I
INVALID VOL SPECIFICATION IN LINE

d_digits.
Explanation: The volume specified in the VOL or

VOLUME attribute on line number d_digits of the
attribute data set is not valid.
d_digits
THE ATTRIBUTE VALUE d_digits1 IS

NOT IN THE RANGE OF d_digits2 TO
d_digits3.
Explanation: The value, d_digits1, specified in one of

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.
d_digits1
The specified value.
d_digits2
The minimum specified value.
d_digits3
The maximum specified value.
Application Programmer Response: See message
GFSA403I to determine the attribute in error, then
correct the attribute data set.
GFSA414I
THE ATTRIBUTE VALUE d_digits1

EXCEEDS THE MAXIMUM VALUE OF
d_digits2.
Explanation: The value, d_digits1, specified in one of

the attributes of the attribute data set must be less than
or equal to d_digits2. Message GFSA403I follows this
message.

d_digits1

attribute data set.
d_digits2
The maximum value allowed for this attribute.
178

GFSA403I to determine the attribute in error, then
correct the attribute data set.
GFSA415I
THE ATTRIBUTE TIME OUT VALUE

d_digits1 IS LESS THAN THE MINIMUM
TIME OUT VALUE d_digits2.
Explanation: The value, d_digits1, specified in the

ATTRTIMEOUT attribute of the attribute data set must
be greater than or equal to the value d_digits2 which is
specified in the MINTIMEOUT attribute of the attribute
data set.
d_digits1
d_digits2
The minimum value allowed, as specified in the
MINTIMEOUT attribute.
attribute data set.
GFSA416I
THE READ TIME OUT VALUE d_digits1

IS LESS THAN THE MINIMUM TIME
OUT VALUE d_digits2.

READTIMEOUT attribute of the attribute data set must
be greater than or equal to the value d_digits2 which
was specified in the MINTIMEOUT attribute of the
attribute data set.
d_digits1
d_digits2
attribute data set.
GFSA417I
THE WRITE TIME OUT VALUE d_digits1

IS LESS THAN THE MINIMUM TIME
OUT VALUE d_digits2.

WRITETIMEOUT attribute of the attribute data set must
be greater than or equal to the value d_digits2 which
was specified in the MINTIMEOUT attribute of the
attribute data set.
d_digits1
d_digits2
attribute data set.
GFSA418I
THE ATTRIBUTE TIME OUT VALUE

d_digits1 IS GREATER THAN THE
MAXIMUM TIME OUT VALUE d_digits2.

ATTRTIMEOUT attribute of the attribute data set must
be less than or equal to the value d_digits2 which was
specified in the MAXTIMEOUT attribute of the attribute
data set.
d_digits1
d_digits2
The maximum value allowed, as specified in
the MAXTIMEOUT attribute.
attribute data set.
GFSA419I
THE READ TIME OUT VALUE d_digits1

IS GREATER THAN THE MAXIMUM

READTIMEOUT attribute of the attribute data set must
data set.
179
d_digits1
NOMAXTIMEOUT attribute in the attribute data set.

Correct the attribute data set.
d_digits2

GFSA422I

attribute data set.
GFSA420I
THE WRITE TIME OUT VALUE d_digits1


WRITETIMEOUT attribute of the attribute data set must
data set.
d_digits1
d_digits2
THE NOREADTIMEOUT ATTRIBUTE

WAS SPECIFIED BUT THE
MAXTIMEOUT VALUE WAS SET TO
d_digits.
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
timeout attributes. These attributes are in conflict. The
NOREADTIMEOUT and MAXTIMEOUT attributes are
specified in the attribute data set.
d_digits
Specified as the MAXTIMEOUT value, in
seconds, that the data set is to remain
allocated.
Application Programmer Response: If the
NOREADTIMEOUT attribute is desired, specify the


attribute data set.
GFSA423I

GFSA421I
THE NOATTRTIMEOUT ATTRIBUTE

d_digits.
Explanation: The NOATTRTIMEOUT attribute means

that the data set is not to be deallocated following a
LOOKUP or SHOWATTR operation. The MAXTIMEOUT
attribute specifies the maximum time out value allowed
for any of the timeout attributes. These attributes are in
conflict. The NOATTRTIMEOUT and MAXTIMEOUT
attributes are specified in the attribute data set.
d_digits
allocated.
NOATTRTIMEOUT attribute is desired, specify the
180
THE NOWRITETIMEOUT ATTRIBUTE

d_digits.
Explanation: The NOWRITETIMEOUT attribute

means that the data set is not to be deallocated
following a write operation. The MAXTIMEOUT attribute
specifies the maximum time out value allowed for any of
the timeout attributes. These attributes are in conflict.
The NOWRITETIMEOUT and MAXTIMEOUT attributes
are specified in the attribute data set.
d_digits
allocated.
NOWRITETIMEOUT attribute is desired, specify the
GFSA424I
MINIMUM TIME OUT VALUE, d_digits1,

TIME OUT VALUE, d_digits2.
Explanation: The value specified in the MINTIMEOUT

attribute of the attribute data set is greater than the
value specified in the MAXTIMEOUT attribute of the
attribute data set.
d_digits1
The value specified in the MINTIMEOUT
attribute.
d_digits2
The value specified in the MAXTIMEOUT
attribute.
attribute data set.
GFSA425I
INVALID SPECIFICATION
RECFM(string).
Explanation: One of the characters in string specified

on the RECFM attribute of the attribute data set is not
valid.
GFSA429I
INVALID DSNTYPE SPECIFICATION IN

d_digits.
Explanation: The data set name type specified in the

DSNTYPE attribute on line number d_digits of the
attribute data set is not valid.
d_digits
attribute data set.
GFSA430I
INVALID SMS_keyword SPECIFICATION

IN LINE line_number.
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
ends if the keyword was specified as a site attribute. If
the incorrect SMS keyword was specified by a client as
a mount parameter or on a command, the line number
is set to zero and an I/O error is returned to the client.

attributes data set.
string
The RECFM attribute specification.

attribute data set.
GFSA426I
INVALID RECFM(string) - MUST

SPECIFY U, F, OR V.
Explanation: One of the characters in string specified

on the RECFM attribute of the attribute data set must
define whether the records are fixed length (F), variable
length (V), or undefined format records (U).
string
The RECFM attribute specification.

attribute data set.
GFSA431I
INVALID OPTION SPECIFICATION OF

string IN LINE d_digits.
Explanation: The option specified in the string

attribute on line number d_digits of the attribute data set
is not valid.
System Programmer Response: Correct the site
attributes file, if applicable.
GFSA434I
string1(d_digits1) IS SET TO THE

DEFAULT VALUE,
string1(d_digits2,d_digits3).
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
takes on the default value for the new release.
181
GFSA435E
SUM OF d_digit1 PLUS d_digits2 MUST

BE LESS THAN OR EQUAL TO d_digits
Explanation: The sum of d_digit1 plus d_digit2 is

greater than d_digits. This is not allowed.
processing stops.
System Programmer Response: Correct the values.
GFSA436I
INVALID SIDEFILE SPECIFICATION IN

LINE d_digits
Explanation: A data set name was not specified in the

sidefile attribute.
System Action: The Network File System server
startup ends.
GFSA439I
HFS PUBLIC PATHNAME SPECIFIED

BUT HFS IS NOT ENABLED
Explanation: An HFS public pathname was specified

in the public keyword but nohfs was also specified
which disables HFS processing.
startup ends.
Operator Response: Correct the problem and make
the necessary changes in the installation table.
Source: GFSAFNPA
GFSA440I
INVALID SECURITY SPECIFICATION IN

d_digits
Explanation: The parsing of the security keyword

resulted in error for one of the following reasons.
v Missing first parameter

and make necessary changes in the attribute data set.
v Invalid first parameter specified
Source: GFSAFNPA

startup ends.
GFSA437I

necessary changes in the attributes data set.
INVALID PUBLIC SPECIFICATION IN

LINE d_digits
Explanation: The parsing of the public keyword

resulted in error for one of the following reasons:
v public keyword specification is syntactically incorrect
Source: GFSAFNPA
GFSA450I
v No public pathnames have been specified

v Pathname specified is invalid
v HFS public pathname does not match HFS prefix
startup ends
the necessary changes in the attributes dataset.
Source: GFSAFNPA
GFSA438I
EXPORT SPANNING PATHNAMES NOT

SUPPORTED
Explanation: The Export Spanning Pathnames

support for a multi-component lookup request is not
supported.
System Action: The request fails. Network File
System processing continues.
CREATED TASK (h_digits) - string1 string2.
Explanation: The network file system server is

creating the number of tasks requested in the
NFSTASKS attribute of the attribute data set. This
message is displayed for each task created.
h_digits
The task control block (TCB) address.
string1 The task name.

string2 The module name.
GFSA451I
DELETING TASK(h_digits) - string.
Explanation: The network file system server is

deleting a task. This is in response to the STOP
operand of the MODIFY command. This message is
displayed for each task deleted.
Source: GFSAFNPA
User Response: Construct a different pathname in

which the path is not spanned
h_digits
string
182
The module name.
System Action: The system continues end processing

for Network File System Server.
GFSA452I
SUBTASK TERMINATED: h_digits.
Explanation: The network file system server is ending

a task. This is in response to the STOP operand of the
MODIFY command. This message is displayed for each
task terminated.
System Action: ESTAE processing ends. The

Network File System Server address space might also
end.
Operator Response: Restart the Network File System
Server address space. Notify network users of the
failure.
Support Center. Provide a symptom string, the related
logrec data set entries, any related SVC dumps, and the
Network File System Server error trace log.

GFSA501I
h_digits
System Action: The system continues end processing
for Network File System Server.
GFSA470I
NETWORK FILE SYSTEM SERVER SVC

DUMP REQUEST FAILED.
REASON=reason_code.
Explanation: A request to take an SVC dump failed.
REQUEST HEADER ALLOCATION

FAILED.

for a request header was attempted, but was
unsuccessful.
System Action: The system ends the request. The
system continues processing for Network File System
Server.
Application Programmer Response: Increase the
size of the job and step region.
GFSA502I
reason_code
A hexadecimal value indicating the reason
MVS was unable to take the dump. See the
description of the SDUMP macro in OS/390
MVS Programming: Authorized Assembler
Services Reference LLA-SDU.

for a request header data block was attempted, but was
unsuccessful.
System Action: Abend processing continues.

Operator Response: If the dump could not be taken
due to an operational procedure and a dump is
necessary to diagnose the failure, correct the
procedure.
System Programmer Response: If the failure
appears to be due to an Network File System Server
error, contact the IBM Support Center. Provide a
symptom string and a copy of the console log.
REQUEST HEADER DATA BLOCK

ALLOCATION FAILED.

Server.
GFSA554I
REGISTER FOR PORT d_digits1

PROGRAM d_digits2 - VERSION
d_digits3 - FAILED.
Explanation: During processing of the network file

system server , the system found an unexpected error.
GFSA471I

ESTAE EXIT UNABLE TO COMPLETE
PROCESSING. ABEND=abend-code.
d_digits1
The port number.
Explanation: The Network File System Server for

DFSMS/MVS 1.1.0 ESTAE exit routine abended and is
unable to complete processing.
d_digits2
The RPC program number.
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.

183
Application Programmer Response: Contact the IBM

Support Center.
GFSA558I
GFSA555I
REGISTER FOR PORT d_digits1

PROGRAM d_digits2 - VERSION
d_digits3 - SUCCESSFUL.
Explanation: The register for the specified port was

successful.
UNABLE TO CREATE IPC QUEUE.

for an IPC queue was attempted, but was unsuccessful.
Server.
d_digits1
The port number.
d_digits2
GFSA559I
d_digits3
GFSA556I
UNREGISTER PROGRAM d_digits1

VERSION d_digits2 - FAILED.
Explanation: During processing for the network file

system server , the system found an unexpected error.
d_digits1
CANNOT CREATE UDP SERVICE.
Explanation: UDP service transport could not be

created, or you started TCP/IP before the _ initialization
was completed.
System Action: The Network File System stops.
Operator Response: Check your MVS TCP/IP setup
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
TCP/IP setup. Also check your _ BPXPRMxx parmlib
member, specifically the MAXFILEPROC,
MAXSOCKETS, INADDRANYPORT, and
INADDRANYCOUNT. The INADDRANYPORT and
INADDRANYCOUNT must be specified, but its range
cannot include 2049, in order for the server to initialize.
See OS/390 MVS Initialization and Tuning Guide for
more details.
d_digits2
GFSA561I

Support Center.
GFSA557I
UNREGISTER PROGRAM d_digits1

VERSION d_digits2 - SUCCESSFUL.
Explanation: The processing for the unregister

program was successful.
d_digits1
d_digits2
System Action: The system continues processing for
Network File System Server.
184
UNABLE TO REGISTER (PROG:

d_digits1 VERS: d_digits2, UDP).
Explanation: The specified program number and

version number failed to register with the service
dispatch routine.
d_digits1
The specified program number.
d_digits2
The specified version number.
Support Center.
GFSA564I
NETWORK SERVICE IS UNAVAILABLE.
Explanation: If the port mapper or the transmission

control protocol/internet protocol (TCP/IP) is not running,
the Network File System Server will fail to initialize.
System Action: The startup of Network File System
Server ends.
System Programmer Response: Ensure that both the
port mapper and the TCP/IP are operational.
GFSA566I
CANNOT ACCEPT NEW TCP CLIENT

CONNECTION MAXIMUM NUMBER
OF SOCKETS HAS REACHED
Explanation: When an NFS TCP client attempts to

connect to the OS/390 NFS server, the server cannot
accept the connection because the maximum number of
sockets has been reached.
System Action: The connection request fails. Network
File System processing continues.
User Response:
Operator Response: Increase the value of
MAXSOCKETS for AF_INET domain in the BPXPRMxx
parmlib member so that client TCP connections can be
accepted by the OS/390 NFS server. Please refer to
OS/390 UNIX System Services Planning manual for
more information.
Source: GFSATCPT
GFSA750I
SMF PROCESSING ACTIVE FOR USER

LOGOUT
Explanation: SMF processing is active for user logout

records. This message is displayed in response to the
status operand on the MODIFY command.
GFSA751I
SMF PROCESSING SUSPENDED FOR

USER LOGOUT
Explanation: SMF processing is suspended for user

logout records. This message is displayed in response
to the status operand on the MODIFY command, or
after receiving a non-zero return code from SMF. See
message GFSA754I for the SMF return code.
processing continues without generating any user or file
SMF records.
Operator Response: Notify the system programmer if
this message was received as a result of a non-zero
return code from SMF.
System Programmer Response: Determine what has

caused the non-zero return code from SMF. Correct the
problem, and have the operator issue a MODIFY
command specifying SMF=ON.
GFSA752I
SMF PROCESSING ACTIVE FOR FILE

TIMEOUT
Explanation: SMF processing is active for file timeout

records. This message is displayed in response to the
status operand on the MODIFY command.
GFSA753I
SMF PROCESSING SUSPENDED FOR

FILE TIMEOUT
Explanation: SMF processing is suspended for file

timeout records. This message is displayed in response
to the status operand on the MODIFY command, or
after receiving a non-zero return code from SMF. See
message GFSA754I for the SMF return code.
processing continues without generating any user or file
SMF records.
Operator Response: Notify the system programmer if
this message was received as a result of a non-zero
return code from SMF.
System Programmer Response: Determine what has
caused the non-zero return code from SMF. Correct the
problem, and have the operator enter a MODIFY
command specifying SMF=ON.
GFSA754I
UNEXPECTED RETURN CODE d_digits

RECEIVED FROM SMF WHILE
WRITING RECORD TYPE 42 SUBTYPE
[7|8].
Explanation: The Network File System Server

received a non-zero return code d_digits while
processing a file timeout (subtype 7) or user logout
(subtype 8) record.
processing continues. No more SMF records of the
same type and subtype are generated until the Network
File System Server address space is re-started, or the
SMF=ON operand of the MODIFY command is entered.
System Programmer Response: See OS/390 MVS
System Management Facilities (SMF) for information
about the return code. Correct the problem, and have
185
the operator enter a MODIFY command specifying

SMF=ON.
System Action: The request is stopped. Network File

System Programmer Response: Check the SAF

security product user profiles.
GFSA770I
OS/390 UNIX REGISTRATION

SUCCESSFUL.
Explanation: Connection with _ established.

System Action: Network File System processing
continues.
GFSA771I
UNIX System Services MVS HFS

MOUNTS SUSPENDED.
Explanation: Mount requests to HFS file systems

have been disabled. Given in response to a console
MODIFY command.
continues.
GFSA772I
UNIX System Services MVS HFS

MOUNTS RESUMED.

have been enabled. Given in response to a console
MODIFY command.
GFSA782I
Explanation: This message is in response to the

list=mounts operand of the MODIFY command and
shows that there are no OS/390 UNIX System Services
clients connected to the Network File System.
continues.
GFSA783I
GFSA776I
UNIX System Services MVS CANNOT

RESOLVE PATH NAME text.
Explanation: Failure to resolve a path name with

OS/390 UNIX System Services, when initializing from
the mount handle data sets. The HFS file system has
been removed or renamed. If the user attempts to
access a file object under this mount point, the Network
File System error response NFSERR_STALE is
returned.
text
The unresolved path name.
continues.
GFSA777I
OS/390 UNIX SERVICE REQUESTER

DOES NOT HAVE SECURITY
PRIVILEGE.
Explanation: The client user must be defined to RACF

as a user of OpenEdition MVS to access HFS file
objects.
186
NO ACTIVE HFS DATA SETS.

list=dsnames operand of the MODIFY command and
shows that there are no clients actively accessing HFS
data sets.
continues.
GFSA784I

continues.
NO ACTIVE HFS MOUNT POINTS.
text1 RPC OS/390 UNIX ERROR

VNODE_OP text2 RC: number1: text3
RSN: number2 number3.
Explanation: The Network File System has

encountered a problem on an interface call with _. The
error was encountered during processing of a text1 rpc
call. text2 is the function called when failure occurred.
number1 is the return code and text3 is the English
description of the return code. The combination of
number2 number3 represents the reason code as
returned by _. Refer to _ documentation for a full
explanation of OpenEdition MVS reason codes (for
example, OS/390 UNIX System Services Programming:
Assembler Callable Services Reference).
System Action: The Network File System continues
processing.
System Programmer Response: Refer to the _
documentation.
GFSA786I
MULTI-COMPONENT LOOKUP
REQUEST FOR PATHNAME text
CANNOT BE RESOLVED.
Explanation: The multi-component lookup request for

the path name failed. Possible reasons are:
v Symbolic links cannot be embedded in a
multi-component path name as it is not supported at
this time
v Pathname specified is either not supported or access
is not allowed
v Public path is not set up on this server.
System Action: The request fails. Network File

GFSA812I
User Response: Construct a different lookup request

with a valid path name.
GFSA801I
MOUNT FAILED: text
Explanation: The text can be:

v FILE MAPPING ENABLED BUT NO SIDE FILE
SPECIFIED,
v STORAGE LIMIT REACHED LOADING MAPPING
SIDE FILE,
v MAPPING SIDE FILE NOT FOUND,
v ERROR OPENING/READING MAPPING SIDE FILE,
v MAPPING SIDE FILE HAS INVALID SYNTAX OR
FORMAT, or
FLUSH FAILED: RC d_digits1 OFFSET

d_digits2 WAS DROPPED FOR DATA
SET string1(string2).
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
d_digits2 was discarded. This error message follows
more specific error messages.
d_digits1
The specified return code.
d_digits2
The offset at which the data was discarded.
string1 The data set that was dropped.
string2 The member of the data set.
v SIDE FILE SPECIFIED BUT MAPPING IS

DIS-ALLOWED BY INSTALLATION.
System Action: The data set is closed. The system

continues processing for Network File System Server.
User Response:
Application Programmer Response: See the

message preceding this message to determine the
correct action. The data set might be incomplete.
v Specify a side file if fileextmap is ON, or

v Fix problem with mapping side file, or
v Consult the system administrator to change sfmax
value and re-issue the MOUNT command.

GFSA813I
GFSA802E
REMOUNT FAILED PHYSICAL FILE

SYSTEM CHANGED. PATH: pathname
PREV: datasetname CURRENT:
datasetname
Explanation: During restart of the Network File

System server, rebuild of the mount point recorded in
the Mount Handle Database failed. The failure occurred
because the physical file system for the mount point
was changed by a TSO UNMOUNT since the mount
point was originally mounted.
REMOVE FAILED: RC d_digits DSN

string1(string2).
Explanation: The error was detected when trying to

remove member string2 from data set string1.
d_digits
string1 The data set.

string2 The member being removed.
System Action: Network File System server


Source: GFSAPHFS

GFSA811I
CANNOT FLUSH PARTIAL RECORDS

FOR DATA SET. string1(string2): FB
h_digits
Explanation: There was not enough memory to

allocate storage required to flush partial records to the
data set at data set close time. The partial record was
discarded.
System Action: The data set is closed. The system
size of the job and step region. The data set might be
incomplete.
GFSA814I
RENAME FAILED: RC d_digits DSN

string1 OLDMEM string2 NEWMEM
string3.

rename member string2 to string3 in data set string1.
d_digits
string1 The data set name.
187
string2 The member name of the old member.

string3 The member name of the new member.
Byte 3: DADSM rename return code.

02
Error cataloging new data set name.

Byte 1: Recatalog return code for old data set

name.
Byte 2: DADSM rename return code for old

data set name.

GFSA815I
RENAME FAILED: RC d_digits OLDDSN

string1 VOL string2 UNIT h_digits
NEWDSN string3.

rename data set string1 to string3.
d_digits
string1 The data set name of the old data set.
Byte 3: Catalog return code for new data set

name.
Catalog and DADSM rename return codes are
documented in OS/390 DFSMSdfp Storage
Administration Reference. Message IEC614I is written
for DADSM rename errors and contains further
diagnostic codes. These codes are documented in
OS/390 DFSMSdfp Diagnosis Reference.
GFSA816I
string2 The volume name.

h_digits
The unit number.
string3 The data set name of the new data set.

System Programmer Response: h_digits1 is a
composite of one or more error return codes
encountered when trying to rename the data set. The
hexadecimal digits are decoded using the list below.
Renaming a data set requires three steps:
1. Uncatalog the old data set name.
2. Rename the data set in the disk VTOC.
3. Catalog the new data set name.
Should an error occur in either of the last two steps, the
prior steps are undone to preserve the old data set
name.
Explanation: The client host name of the specified IP

address is not defined in either the TCP/IP Domain
Name Server or the TCP/IP Site Table. SeeOS/390 IBM
Communications Server: IP Migration for more
information.
d_digits
The specified IP address.
processing continues. The dotted IP address is used as
the host name.
Application Programmer Response: Insert this
clients host entry into either the TCP/IP Domain Name
Server or the TCP/IP Site Table.
GFSA817I
Find the step that failed by matching the value in byte

zero of the return code with the values under the
heading byte 0 below. Byte three contains the return
code from the first failing MVS/DFP service
(Uncatalog/catalog or DADSM rename). If subsequent
errors occur when attempting to recatalog and/or
rename the data set back to the old name, the return
codes are placed in bytes one and two.
Byte 0 Explanation/Other Bytes
00
Error uncatalog old data set name.

Byte 3: Uncatalog return code.
01
Error renaming the data set.

Byte 1: Recatalog return code for old data set
name.
HOST NAME OF IP ADDRESS (d_digits)

WAS NOT FOUND BY TCP/IP.
string1 REQUEST NOT VALID ON ALIAS

NAME string2
Explanation: A REMOVE (RM or RMDIR) or

RENAME (MV) request was attempted while using an
alias name. The true file name is required.
string1 Either REMOVE or RENAME.

string2 MVS Access Method Services alias name of a
file which also has a true name.
System Action: The request ends. An I/O error
indication is returned. Network File System Server
User Response: Provide the true name of the file on
the request.
188
GFSA818I
EXPORTS: NO VALID HOST NAMES IN

string LIST.
Explanation: None of the client host names in the

READ/WRITE or ACCESS list are defined to the
network.
16
Serializing the DASD volume. See OS/390

Services Reference LLA-SDU for the
RESERVE macro.
20
Reading the DSCB. See OS/390 DFSMSdfp

Storage Administration Reference for the
CVAFDIR macro.
24
Writing the DSCB. See OS/390 DFSMSdfp

Storage Administration Reference for the
CVAFDIR macro.
string
Either the READ/WRITE or the ACCESS list.
System Action: Network File System Server does not

export the associated directory.
System Programmer Response: Correct the host
names in the EXPORTS file or have the host names
defined to the network.


GFSA822I
GFSA820I
CATALOG ERROR OCCURRED WHILE

[RETRIEVING|UPDATING] CATALOG
INFORMATION FOR string. RETURN
CODE IS d_digits1, REASON CODE IS
cc-d_digits2.
UNABLE TO PERFORM FILE MAPPING

BECAUSE NO SIDE FILE SPECIFIED
OR LOADED
Explanation: File mapping cannot be performed

because a side file was not specified either as a default
or at the mount point.
Explanation: Catalog Management module IGG0CLcc

returned this return code, d_digits1, and reason code,
d_digits2, as the result of a catalog error or an
exception condition. string was the name of the data set
that the retrieve or update operation was performed
against.
System Action: Operation fails

Source: GFSAXFB GFSAARDR
System Programmer Response: See message

IDC3009I for specific return and reason code
information.
GFSA823I

GFSA821I
ERROR OCCURRED WHILE UPDATING

THE FORMAT 1 DSCB FOR string1 ON
string2. FUNCTION CODE IS d_digits1,
RETURN CODE IS d_digits2, REASON
CODE IS d_digits3.
Explanation: string1 is the name of the data set and

string2 is the volume serial number of the volume on
which the data set resides. The function code can be
one of the following:
2
12
De-serializing the UCB. See OS/390 MVS

Reference SET-WTO for the UCBPIN macro.
De-serializing the DASD volume. See OS/390
Services Reference ALE-DYN for the DEQ
macro.
Searching for the UCB. See OS/390 MVS
Reference SET-WTO for the UCBLOOK macro.
User Response: Specify a side file in the mount

command.
System Programmer Response: Specify a side file in
the attributes data set.
PUBLIC PATH CANNOT BE

ESTABLISHED.
Explanation: The public pathname(s) specified in the

public keyword cannot be established during server
startup. This could be because the path is not exported
or it does not exist.
startup ends.
Operator Response: Make sure the public pathname
exist and is exported if export list checking is enabled.
Correct the problem and restart the server.
Source: GFSAMCMN
GFSA827I
REQUEST h_digits CREDENTIALS

ALLOCATION FAILED.

for a credentials block was attempted, but was
unsuccessful.
h_digits
The request block address.
189

Server.
h_digits

string

GFSA829I
REQUEST h_digits INVALID

CREDENTIALS FLAVOR d_digits.
Explanation: Incorrect credentials flavor received from

client. Probable client software error. The network file
system server supports UNIX and non-authentication
styles.

The specified member name of data set name.

Server.
User Response: Correct the error and resubmit the
request.
GFSA840I
h_digits
Explanation: A dynamic file allocation error occurred.

d_digits
The incorrect credentials flavor.
Server.
Application Programmer Response: Inform the client
user that the credentials used are not valid.
GFSA832I
REQUEST h_digits INVALID

MEMBERNAME FOR string.
Explanation: The member name of a partitioned data

set (PDS) was specified as a file name by the user, but
the file name specified was incorrect or not found in the
PDS.
h_digits
string
DYNAMIC ALLOCATION FAILED WITH

RETURN CODE d_digits FOR DATA SET
string1(string2).
The specified member name.

Server.
request.
GFSA833I
REQUEST h_digits PARSE FAILED FOR

string.
Explanation: The member name of a partitioned data

set (PDS) or a data set name that was specified as a
file name by the user was incorrect, not found in the
PDS, or was an incorrect or nonexistent data set.
d_digits
The dynamic allocation return code.

string2 The member name, if any.
Server.
Application Programmer Response: This message
is preceded by either message GFSA853I or GFSA854I.
See the programmer response for the message that
precedes this message to determine the appropriate
action.
GFSA842I
string UNSUPPORTED DSORG {ISAM |

UNKNOWN}
Explanation: The data set organization of data set

string1 is not supported by the network file system
server.
string
The unsupported data set organization.

Server.
job.
GFSA843I
CREATE FAILED FOR string.
Explanation: An error occurred while the network file

system server was trying to create the specified data
set. This message follows other messages that describe
the error in greater detail.
190
string
The specified data set name.

Server.
messages preceding this message to determine the
appropriate response.
GFSA847I
IDCAMS ERROR: text.
Explanation: text is an access method services error

message.
System Messages, Vol 3 (EWX-IEB) for more
information on the access method services error
message.
GFSA848I
PDS string IS NOT EMPTY.
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)
to be empty before it is removed.
string
GFSA850I
FILE string EXISTS.
Explanation: The user attempted to rename a file to

the target name string. A file named string already
exists.
string
The file name.
System Action: The system ends the request. An

error is returned to the user. The system continues
processing for Network File System Server.
User Response: Check the filename used. Correct it
and file it again.
GFSA851I
FILE string DOES NOT EXIST.
Explanation: The user attempted to rename or

remove a file that does not exist.
string
The specified file name.

and attempt to rename or remove the file again.
The name of the PDS.

User Response: Remove all files in the directory then
resubmit the RMDIR request.
GFSA849I
NEW AND OLD FILES ARE NOT

MEMBERS OF THE SAME PDS.
Explanation: Rename is not allowed for a member of

a partitioned data set (PDS) when the target name is
not in the same PDS.
and resubmit the request.
GFSA853I
DYNAMIC ALLOCATION: INPUT

VALIDATION ROUTINE REJECTED
ALLOCATION.
Explanation: Dynamic allocation failed when issued

by the installation input validation routine. Probable
installation configuration errors.
Server.
Application Programmer Response: See the input
validation documentation for more information on the
input validation routine.
GFSA854I
DYNAMIC ALLOCATION: RC=d_digits

ERROR=h_digits1 INFO=h_digits2: string.
Explanation: Dynamic allocation processing failed.

d_digits
The return code.
h_digits1
The error reason code.
191
h_digits2
The information reason code.
string
The description of the interrupted dynamic

allocation request.

Server.
dynamic allocation documentation for more information
about these codes.
GFSA858I
OPEN FAILED RC d_digits FOR DATA

GFSA860I
WRITE FAILED RC d_digits FOR DATA

Explanation: An error occurred while trying to write

the specified data set.
d_digits
The return code.

Server.

Application Programmer Response: If this error was

not caused by an out-of-memory condition, contact the
IBM Support Center.
d_digits
The return code.
GFSA862I

Server.
IBM Support Center.
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
exist or is not mounted. If it does not exist, the entry in
the master catalog may be incorrect.
string
The user catalog name.

GFSA859I
READ FAILED RC d_digits FOR DATA


d_digits
The return code.

Server.
IBM Support Center.

GFSA863I
READDIR ON ROOT IS NOT ALLOWED.
Explanation: The user attempted to list the contents

of the master catalog.
Server.
GFSA864I
CANNOT OPEN THE EXPORTS DATA

SET.
Explanation: The server was unable to open the

exports file defined in the JCL for DDNAME EXPORTS.
The DD statement might be missing or the data set
name might be incorrect.
192

for DDNAME EXPORTS.
GFSA868I

GFSA865I
EXPORTS: UNEXPECTED OPTION

(string)SHUTDOWN SCHEDULED.
Explanation: The option information provided in string

is incorrect. This error could occur as a result of
unexpected blanks, incorrect syntax, or the use of
mutually exclusive options.
string
The specified option.
System Action: Checking of the EXPORTS file

continues, but the system will end Network File System
Server when checking is complete.
EXPORTS file and restart Network File System Server.
Explanation: The host named string has an IP

address that is not valid.
string
The host name.
d_digits
The IP address.
EXPORTS file.
GFSA869I

GFSA866I
EXPORTS: DIRECTORY string WAS

NOT EXPORTED.
Explanation: An error was encountered severe

enough to prevent the data set or index from being
exported. This message follows a more specific error
message.
string
The name of the data set or index.

EXPORTS file.
EXPORTS: HOST (string) WITH

UNKNOWN ADDRESS TYPE (d_digits)
HAS BEEN IGNORED.
EXPORTS: UNKNOWN HOST (string)

HAS BEEN IGNORED.
Explanation: The client host named string is not

string
The host name.

Network File System Server. If this undefined client host
is the only host specified for an RW or ACCESS option
in the EXPORTS file, the Network File System Server
does not export the associated directory. If there are
other defined client hosts specified for the option,
Network File System Server ignores this undefined
client host.
Application Programmer Response: Correct the host
name in the EXPORTS file or have this host name
GFSA867I
EXPORTS: string1 CANNOT BE

EXPORTED BECAUSE string2
ALREADY IS.
Explanation: The data set or index named in string1

is a parent directory or a subdirectory of the data set or
index named in string2 which is already exported.
string1 The name of the data set or index that is a

parent or subdirectory of string2.
string2 The name of the data set or index already
exported.
EXPORTS file.
GFSA871I
REQUEST h_digits HAS MISMATCHED

UID: CRED = d_digits1 ARGS =
d_digits2.
Explanation: A request was attempted with

mismatched ID numbers. The userid numbers do not
match the credential id numbers.
h_digits
A block created for the logon or logout request.
d_digits1
Represents the credential user ID number.
d_digits2
Represents the client user ID number.

193

Server.
Application Programmer Response: Inform the
Network File System Server client that the credentials
used are not valid.
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
Explanation: The physical I/O layer attempted to

check some previous operation in the data set. The
check failed.

h_digits1
The sense bytes 0 and 1 from the device.
h_digits2
The first 3 bytes of the channel status word
(CSW) from the device.
h_digits3
The last 4 bytes of the CSW from the device.
h_digits4
The access method return code.
h_digits5
The access method reason code.
Server.
System Programmer Response: A Data

Management message should have been displayed on
the console. See OS/390 MVS System Messages, Vol 2
(ASB-ERB) for more information on the Data
Management error message.
GFSA881I
FUB: h_digits1 UNABLE TO ACCESS

FILE string1 (string2) OWNED BY FUB
h_digits2.
Explanation: A user has attempted to access a data

set already locked internally by the network file system
server for writing by another user. The data set has not
been released yet.
h_digits1
The address of the file usage block (FUB).
h_digits2
The address of the file usage block which
currently has the file allocated.
System Action: The system ends the request. A not
owner error is returned to the user. The system
Application Programmer Response: None.
GFSA886I
UNABLE TO WRITE RECNO d_digits TO

string1(string2) DUE TO PREVIOUS
ERROR.
Explanation: An error was previously detected which

prevents writing to a data set.

appropriate device documentation for more information
on the sense bytes and CSW.
d_digits
The record number.

GFSA877I
R0=h_digits1 R1=h_digits2: text ACCESS

METHOD RC = h_digits3 ACCESS
METHOD RSN = h_digits4
Explanation: A SYNAD error was detected during

physical I/O operation. h_digits1 is the contents of
register 0; h_digits2 is the contents of register 1. The
text is the message returned from the SYNAD analysis
function macro. h_digits3 is the access method return
code. h_digits4 is the access method reason code.
System Action: The request is stopped. If the error
detected is a B37, D37 or E37 abend, the Network File
System restores the file size to the last known file size
before the SYNAD error. Network File System
194

Server.
Application Programmer Response: If the previous
error cannot be determined, contact the IBM Support
Center.
GFSA895I
REQUEST h_digits - FILE string NOT

ALLOCATED.
Explanation: The network file system server did not

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
set, causing Network File System Server to close the
data set.

Server.
h_digits

string
The data set name.
System Action: The system ends the request. Return

code X'131' is passed back to the user. The system
GFSA898I
EOL SEQUENCE MISMATCH FOR

DATA SET. string1(string2)
Explanation: The end-of-line terminator was not found

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

h_digits2 ASSOCIATED WITH FILE string
NOT IN USE BY CREDENTIALS
h_digits3.
Explanation: The request to close file string was

received, but the file was not opened by the user. A file
can only be closed by the same user that opened the
file.

Server.
h_digits1
h_digits2
The file block address.
string
The specified file name.
h_digits3
The credentials block address.
System Action: The system ends the request. Return
code X'132' is passed back to the user. The system
GFSA899I
BLANKSTRIP MODE: TRAILING

BLANK(S) IN RECORD d_digits IS NOT
ALLOWED. DSN = string1(string2).
Explanation: The user attempted to write data in text

mode with blank stripping enabled and blanks at the
end of the line to a data set with fixed-length records.
d_digits
The record.

Server.
GFSA897I
RECORD d_digits1 SIZE d_digits2 IS

{TOO LONG | TOO SHORT}:
{MAXIMUM | MINIMUM} = d_digits3 DSN
= string3(string4).
Explanation: The record received from the user is

either too long or too short.
d_digits1
The record number.
d_digits2
The record size.
d_digits3
The maximum or minimum length allowed.

GFSA900I
MOUNT PROCESSING ACTIVE.
Explanation: Mounts can be issued from the network.

This message is displayed in response to the STATUS
operand of the MODIFY command.

195
GFSA901I
MOUNT PROCESSING SUSPENDED.
Explanation: Mount processing has been suspended

by the FREEZE=ON operand of the MODIFY command.
This message is displayed in response to either the
FREEZE=ON or STATUS operands of the MODIFY
command.
Network File System Server. Further mount requests
from the network are ignored. Existing mounts are
unaffected.
GFSA905I
HFS MOUNT PROCESSING

SUSPENDED
Explanation: HFS mount processing has been

suspended by the freeze=onhfs operand of the MODIFY
command. This message is displayed in response to
either the freeze=onhfs or status operands of the
MODIFY command. Further HFS mount requests from
the network are ignored. Existing mounts are
unaffected.
System Action: The Network File System processing
continues.
Detecting Module: GFSACOPR
GFSA902I
MOUNT PROCESSING RESUMED.
Explanation: Mount processing has been resumed by

the FREEZE=OFF operand of the MODIFY command.
Network File System Server. Further mount requests
from the network will be honored. Existing mounts are
unaffected.
GFSA908I
HFS PROCESSING DISABLED
Explanation: HFS processing is suspended. This

message is displayed in response to the status operand
of the MODIFY command.
System Action: The Network File System processing
continues.
Detecting Module: GFSACOPR
GFSA903I
TASK h_digits1 TCB h_digits2

PROGRAM = string1 = string2.
Explanation: This message is issued in response to

the STATUS operand of the MODIFY command.
h_digits1
The task queue address.
GFSA909E
UNMOUNT COMMAND FAILED: MOUNT

POINT STILL IN USE

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
later after there is no reference to file system.
h_digits2

system continues processing for the Network File
System.
string1 The program name.
string2 The specific task name.

GFSA904I
HFS MOUNT PROCESSING ACTIVE.
Explanation: Mounts can be issued from the network.

This message is displayed in response to the status
operand of the MODIFY command.
continues.
GFSA910I
string ACTIVE = d_digits.

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
path. The number may not be accurate if a user has
crashed without unmounting the files.
string
The mounted file space.
d_digits
The number of active users mounting the files
by the specified path.
196

GFSA911I
string1(string2) ACTIVE = d_digits.
Explanation: This status message is in response to

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
path. The number may not be accurate if a user has
crashed without unmounting the files.
GFSA914I
string DEALLOCATED.
Explanation: The data set name appears in response

to a RELEASE=dsname(member) operand of the
MODIFY command after successful deallocation.
string
The data set name.


d_digits
GFSA915I
The number of active users mounting the files
by the specified path.
string NOT ALLOCATED.


to the RELEASE=dsname(member) operand of the
MODIFY command if the data set or member specified
to be released was not found.
string
GFSA912I
string.

to a LIST=DSNAMES operand of the MODIFY
command and shows a currently active data set.
string
The data set name.
The data set name.

GFSA916I
string UNMOUNTED.


to an UNMOUNT (data set or member) operand of the
MODIFY command after a successful unmount.
string
GFSA913I
string1(string2).
Explanation: The partitioned data set (PDS) member

appears in response to the LIST=DSNAMES operand of
the MODIFY command and shows a currently active
data set.

The data set name.

GFSA917I
string NOT MOUNTED.

to the UNMOUNT (data set or member) operand of the
MODIFY command if the data set or member specified
to be unmounted was not found in the current mount
list.
string
The data set name.

197
GFSA918I
string IS NOT A VALID DATA SET

NAME.
Explanation: The data set name specified on either

the RELEASE or UNMOUNT operand of the MODIFY
command is not a valid data set name.
string
The data set name.

Operator Response: Respecify the command with a
valid data set name.
GFSA922I
VERIFY: (string) IS NOT A VSAM DATA

SET.

VERIFY operand of the MODIFY command and shows
that the data set name specified is not a virtual storage
access method (VSAM) data set.
string
The data set name.

Server.
GFSA919I
string IS NOT A VALID MEMBER NAME.
Explanation: The member name specified on either

the RELEASE or UNMOUNT operand of the MODIFY
command is not a valid MVS member name.
string
The incorrect member name.

Operator Response: Respecify the command with a
valid member name.
GFSA923I
VERIFY SUCCESSFUL FOR (string).

that the verify was successful for the virtual storage
access method (VSAM) data set.
string
The data set name.

GFSA920I
NO ACTIVE MOUNT POINTS.

LIST=MOUNTS operand of the MODIFY command and
shows that there are no clients connected to the
network file system server .
GFSA924I
VERIFY FAILED WITH RC = d_digits

FOR (string).

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.

LIST=DSNAMES operand of the MODIFY command
and shows that there are no users actively accessing
data sets.
string
The data set name.

GFSA847I to determine the correct action.

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
198
or more errors were detected in the EXPORTS file; for

example, the EXPORTS file cannot be opened.
switched-to log data set is filled.

processing continues. The existing EXPORTS file will
not be changed.
System Programmer Response: Consider allocating

larger error log data sets for future Network File System
Server usage. Note that the last data buffer will be lost
when the log is switched.
System Programmer Response: Review previous

console error messages for detailed information as to
the specific error in the EXPORTS file.
GFSA931I

GFSA926I
EXPORT LIST HAS BEEN REBUILT

SUCCESSFULLY

operand of the MODIFY command, indicating that the
command has completed normally.
processing continues with the new EXPORTS file in
effect.
GFSA927I
MODIFY EXPORTS COMMAND

IGNORED - THE EXPORTS FILE IS NOT
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
done.

LOGGING IS TERMINATED.
Explanation: The Network File System Server logging

ends. This can be caused by a no space condition of
the log data set.
System Programmer Response: Allocate a larger log
data set for future Network File System Server usage.
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,
string is STDERR. Otherwise, string is the associated
DD of the active log data set.
GFSA933I
LOG DATA SET IS RE-INITIALIZED.
Explanation: The error log is re-initialized.

processing continues with the security options
unchanged.

GFSA930I
GFSA934I
LOG DATA SET IS SWITCHED FROM

string1 TO string2.
NFSLOG1 OR NFSLOG2 DD
STATEMENTS NOT DEFINED.
Explanation: A no space or an I/O error condition is

detected when writing to the log data set. Network File
System Server logging is now switched to the other log
data set.
Explanation: The NFSLOG1 or the NFSLOG2 DD

statements are not coded in the Network File System
Server start-up cataloged procedure.
System Programmer Response: Code the NFSLOG1

and NFSLOG2 DD statements and allocate the
associated log data sets.
string1 The DD associated with the switched-from log

data set.
string2 The DD associated with the switched-to log
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
199
GFSA935I
SWITCHED-TO LOG IN ERROR.

LOGGING CONTINUED ON DD:string.
Explanation: An operator entered a SWITCHLOG

command but an open error is detected in the new log
data set.
GFSA953I
PASSWORD CHANGE REQUIRED BY

HOST.
Explanation: The MVS password for the user ID

passed to the host has expired. A new password is
required. Message GFSA974I follows this message.
string
The DD associated with the original log data

set.
System Action: Network File System Server logging

continues in the original log data set.
Operator Response: Correct the non-active log data
set.
GFSA949I
COMMAND string NOT VALID.
Explanation: The operator has entered the operator

command or operand string which is not valid.
string
GFSA954I
HOST text1 RETURNED ERROR

d_digits:text2
Explanation: An error was detected during mvslogin

processing. Host text1 returned error code d_digits and
message text2 to the client.
User Response: The password or user ID might be
incorrect. Start the mvslogin command sequence again
and use the correct password or user ID.
GFSA955I
text LOGGED IN OK.
Explanation: The MVS user ID text was logged in

without any errors.
The incorrect operator command or operand.

usage: text [-pn][-g group][-a account]
hostname [mvs_username]

GFSA956I
Operator Response: Enter the operand of the

MODIFY command again with the correct syntax.
Explanation: Usage information for the text command.

GFSA950I
UNKNOWN FLAG -character
Explanation: The character character specified on the

mvslogin, mvslogout, or showattr command is not a
valid option. A usage message might follow this
message.
User Response: See OS/390 Network File System
Users Guide for a description of the valid options used
with the command.
User Response: Enter the command using the correct

syntax.
GFSA957I
Explanation: An error was detected during mvslogout

processing. Host text1 returned error code d_digits and
message text2 to the client.
User Response: Notify your MVS system
programmer.
GFSA958I
GFSA951I
text: CANT FIND NAME FOR UID

d_digits.
HOST text1 RETURNED ERROR

d_digits:text2
UID text LOGGED OUT OK.
Explanation: The MVS user ID text was logged out

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

the command again.
GFSA959I
USAGE: text HOSTNAME
Explanation: Usage information for the text command.

GFSA952I
RETYPED PASSWORD DOES NOT

MATCH
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.
200
User Response: Enter the command using the correct

syntax.
GFSA960I
text1: HOST text2 UNKNOWN.
Explanation: The host text2, specified on command

text1, is not known to the network.
User Response: Correct the host name specified and
try the command again.
GFSA961I
text1: text2
Explanation: Command text1 received an error when

trying to create a client transport handle using the
clntudp_create TCP/IP remote procedure call. text2 is
the message produced by the clnt_pcreateerror
TCP/IP procedure. This message is issued if:
v The host name is unknown
v The host is not operational
v The Network File System on the named host is not
operational
GFSA970I
REGISTERED WITH UNIX System

Services MVS.
Explanation: Connection with OS/390 UNIX System

Services established.
GFSA971I
HFS MOUNTS DISABLED.

have been disabled. Given in response to a console
MODIFY command.
User Response:
v Correct the host name specified and try the
command again,
GFSA972I
HFS MOUNTS ENABLED.
v Make sure the specified host is operational and try

the command again, or

have been enabled. Given in response to a console
MODIFY command.
v Make sure the OS/390 NFS server on the named

host is operational and try the command again.

GFSA964I
text: ERROR: CANNOT DETERMINE

SERVER.
Explanation: The text command found the mount

path, but the server name was not returned by the local
operating system service that keeps mount point
information.
User Response: Correct the mount point table and try
the command again.
GFSA965I
text1: ERROR: text2 MOUNTED FROM

SERVER text3, NO text4.
Explanation: The wrong host name was specified for

the text1 command. text2 is mounted from server text3
instead of server text4.
User Response: Specify the command again with the
correct host name.
GFSA966I
text: ERROR: UNKNOWN RETURN

FROM USAGE ROUTINE.
GFSA973I
UNIX System Services MVS IS NOT

RESPONDING.
Explanation: Registration with OS/390 UNIX System

Services has been successful but a request for an HFS
file object has failed.
System Server processing continues.
System Programmer Response: If the log is being
flooded with these messages, restart the Network File
System Server and set site attribute nohfs.
GFSA974I
INVALID UNIX System Services MVS

RELEASE LEVEL.
Explanation: The Network File System Server only

works with MVS/SP 5.1 or later.
Explanation: The usage routine used for the text

command returned an unknown error code.

processing continues. Access to conventional MVS data
sets is not impacted.
User Response: Contact your programming support

personnel.
System Programmer Response: Install MVS/SP 5.1

or later.
201
GFSA975A
RETYPE NEW MVS PASSWORD:
GFSA991E
Explanation: MVS requires the new password to be

entered twice for verification.
User Response: Enter the new MVS password again.
GFSA976I
CANNOT RESOLVE PATHNAME WITH

UNIX SYSTEM SERVICES MVS.
Explanation: A failure occurred when attempting to

resolve a pathname with UNIX System Services MVS,
when initializing from the mount handle data sets. The
HFS file system has been removed or renamed. If the
user attempts to access a file object under this mount
point, the Network File System Server error response
NFSERR_STALE is returned.
GFSA977I
SERVICE REQUESTER DOES NOT

HAVE SECURITY PRIVILEGE.
Explanation: The client user must be defined to RACF

as a user of OS/390 UNIX System Services MVS to
access HFS file objects.
System Programmer Response: Check the SAF
security product user profiles.
GFSA978I
text logged in ok. Mismatch in uid/gid:

UNIX System Services uid is digit_1,
gid is digit_2, client uid is digit_3, gid is
digit_4
Explanation: The OS/390 UNIX System Services

UID/GID does not match the client machine UID/GID.
The authentication is successful and the message is for
informational use only.
User Response: None
GFSA979I
SECURITY PRODUCT IS NOT

INSTALLED.
Explanation: OS/390 UNIX System Services has

detected that the security product is not installed. The
user receives an NFS error response NFSERR_ACCES
to the request.
System Programmer Response: Ensure the correct
release of the security product is installed.
202
MESSAGE FORMAT FROM USER EXIT

ROUTINE(S) IS INCORRECT. USER text
EXIT ROUTINE(S) HAS(HAVE) ENDED.
Explanation: The text exit routine returned an

incorrect length message.
In the message text, text is one of the following:
LOGON AND FILE SECURITY
User logon and file security exit routines.
FILE SECURITY
User file security exit routine.
System Action: The Network File System Server
processing continues without the user exit routine(s).
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.
Detecting Module: GFSASCLO
GFSASCSE
GFSA996E
INSTALLATION DEFAULT
TRANSLATION TABLE CANNOT BE
INITIALIZED.
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
Network File System Server start-up catalog
procedure, and the xlat processing attribute is
specified.
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 Translation table contained in the translation table
data set is in an incorrect format.
processing stops.
System Programmer Response: Do the following
before restarting the Network File System Server:
v Code the NFSXLAT DD statement in the Network File
System Server start-up catalog procedure correctly.
v Allocate the translation table data set defined in the
NFSXLAT DD statement.
v Make sure the translation table in the translation table
data set exists.
v Make sure the translation table specified in the
translation table data set is in the correct format.
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.
203
204

GFSC100E
RPC REQUEST (h_digit) FAILED,

RETURN VALUE -1 RETURN CODE
returncd REASON CODE rsnc (text)
Explanation: RPC request failed. (h_digit) is the

request block address. Reason code, rsnc, is the return
code returned from TCP/IP. text is the failure reason.
For the explanation of return code, returncd, refer to
OS/390 UNIX System Services Messages and Codes.
System Action: Client continues processing.
User Response: See the return code, returncd, in
OS/390 UNIX System Services Messages and Codes,
and the reason code, rsnc, in OS/390 eNetwork
Communications Server: IP Messages.
Detecting Module: OS/390 NFS client, module
GFSCCXDR
GFSC101E

REQUEST FAILED (h_digit),
OPENEDITION RETURN CODE returncd
RETURN CODE retc (text)
Explanation: Network File System server failed the

request from the client. (h_digit) is the request block
address. Return code, retc, is returned from Network
File System server. text is the failure reason for the
request. For the explanation of return code, returncd,
refer to OS/390 UNIX System Services Messages and
Codes.

GFSCCXDR
GFSC103E

REQUEST FAILED (h_digit),
OPENEDITION RETURN CODE returncd
RETURN CODE retc
Explanation: Network File System server failed the

request from the client. (h_digit) is the request block
address. Return code, retc, is returned from Network
File System server. For the explanation of return code,
returncd, is referred to in OS/390 UNIX System
Services Messages and Codes.
and the return code, retc, in the Network File System
Protocol Specification, RFC 1094.
GFSCCXDR
GFSC105E
READ FAILED, RETURN VALUE -1

RETURN CODE returncd REASON
CODE reasoncd.
Explanation: While reading a block of data from a

remote file, an error returncd was detected.
System Action: The read operation ends. OS/390

NFS client processing continues.

and the return code, retc, in the Network File System
Protocol Specification, RFC 1094.
User Response: Refer to OS/390 UNIX System

Services Messages and Codes for a description of the
return code returncd and the reason code reasoncd to
determine corrective action.

GFSCCXDR

GFSC2BIO
GFSC102E
RPC REQUEST (h_digit) FAILED,

returncd REASON CODE rsnc
Explanation: RPC request failed. (h_digit) is the

request block address. Reason code, rsnc, is the return
code returned from TCP/IP. For the explanation of
return code, returncd, is referred to in OS/390 UNIX
System Services Messages and Codes.
and the reason code, rsnc, in OS/390 eNetwork
Communications Server: IP Messages.
GFSC106E
WRITE FAILED, RETURN VALUE -1

CODE reasoncd.
Explanation: While writing a block of data to a remote

file, an error returncd was detected.
System Action: The write operation ends. OS/390
NFS client processing continues. The remote file may
not be complete.
GFSC2BIO
205
GFSC107E
FLUSH FAILED, RETURN VALUE -1

CODE reasoncd.
Explanation: While flushing cached data to a remote

file during close processing, an error returncd was
detected.
System Action: The write operation ends. OS/390
NFS client processing continues. The remote file may
not be complete.
GFSC2BIO
GFSC110E
text FAILED, RETURN VALUE -1

CODE reasoncd
Explanation: The OS/390 NFS client has detected an

error in the function, text.
System Action: The request has ended. OS/390 NFS
client processing continues.
GFSC201E
Explanation: OS/390 NFS client only supports

asynchronous mount.
System Action: The MOUNT command ended with an
error. OS/390 NFS client processing continues.
User Response: Reissue MOUNT command with the
asynchronous option.
GFSCVMNT
GFSC202E
GFSC200E
VFS_MOUNT FAILED, RETURN VALUE

-1 RETURN CODE returncd REASON
CODE reasoncd.
Explanation: The MOUNT command failed because of

error returncd.
System Action: The MOUNT command ended
abnormally. OS/390 NFS client processing continues.
determine the corrective action, and reissue MOUNT
command.
GFSCVMNT
A FILE SYSTEM WITH THE SAME

NAME IS ALREADY MOUNTED.
Explanation: Cannot mount on an existing mount

point.
error. No mount point was established. OS/390 NFS
User Response: Reissue MOUNT command with a
different mount point.
GFSCVMNT
GFSC203E
System Programmer Response: Collect the detail

trace log from client and from server if any.
Detecting Module: OS/390 NFS client, modules
GFSCVNAC, GFSCVNAT, GFSCVNDR, GFSCVNLK,
GFSCVNRM, and GFSCVNRW
NETWORK FILE SYSTEM CLIENT

DOES NOT SUPPORT SYNCHRONOUS
MOUNT REQUEST.
PARSING MOUNT OPTION FAILED,

returncd REASON CODE reasoncd
OPTION=text.
Explanation: The mount option text was incorrectly

specified.
error. No mount point is established. OS/390 NFS client
return code returncd, and refer to OS/390 Network File
System Customization and Operation for further details
of the reason code reasoncd. Correct the mount option,
and reissue MOUNT command.
GFSCVMNT
GFSC204E
VFS_UMOUNT FAILED, RETURN

VALUE -1 RETURN CODE returncd
REASON CODE reasoncd.
Explanation: The UMOUNT or UNMOUNT command

failed.
System Action: The UMOUNT or UNMOUNT
command ended with an error. The mount point may
still exist. OS/390 NFS client processing continues.
206

determine the corrective action. Correct it and reissue
UNMOUNT again.
GFSCVMNT
no fix exists, contact the IBM Support Center. Provide

all the printed output and copies of output data sets
related to the problem.
GFSCVMNT
GFSC208E
GFSC205E
VFS_STATFS FAILED, RETURN VALUE

CODE reasoncd.
Explanation: The VFS_STATFS operation failed.

While trying to get the status of a remote file system, an
error returncd was detected.
System Action: The VFS_STATFS ended with an
determine the corrective action.
GFSCVMNT
GFSC206E
VFS_SYNC FAILED, RETURN VALUE -1

CODE reasoncd.
Explanation: The VFS_SYNC operation failed. While

flushing cached data of remote files, an error returncd
was detected.
System Action: The VFS_SYNC ended with an error.
The remote files may not be complete. OS/390 NFS
determine the corrective action.
GFSCVMNT
GFSC207E
VFS_RECOVER FAILED, RETURN

REASON CODE reasoncd.
Explanation: The VFS_RECOVER operation failed.

While trying to recover from a previous abend, an error
returncd was detected.
System Action: The VFS_RECOVER ended with an
determine the corrective action. If the error occurs and
the program is not in error, look at the messages in the
client log data sets for more information. Search
problem reporting data bases for a fix for the problem. If
VFS_PFSCTL FAILED, RETURN VALUE

CODE reasoncd.
Explanation: The VFS_PFSCTL operation failed.

System Action: The VFS_PFSCTL ended with an
determine the corrective action. If the error occurs and
the program is not in error, look at the messages in the
client log data sets for more information. Search
GFSCVMNT
GFSC209E
THE IP ADDRESS OF REMOTE HOST

NAME, hostname, COULD NOT BE
RESOLVED.
Explanation: The VFS_MOUNT operation failed. The

mount processing failed when it tried to resolve the
remote host name hostname to a dotted IP address.
User Response: Correct the remote host name or use
the dotted IP address of the remote host, and reissue
the MOUNT command.
GFSCMNTD
GFSC210E
NFS SERVER <hostname> DOES NOT

SUPPORT NFS VERSION 3 PROTOCOL
WHILE VERS(3) WAS SPECIFIED

mount processing failed because the server does not
support NFS version 3 protocol, which the user
requested with the mount parameter vers(3).
System Action: The mount command ended with an
error. OS/390 NFS client processing continue.
User Response: Verify that the server actually does
not support NFS version 3 protocol. Remove vers(3)
from the mount parameter, and reissue the mount
command.
207
Source: OS/390 NFS client, module GFSCMNTD

GFSC211E
NFS SERVER <hostname> DOES NOT

SUPPORT AUTH_UNIX
AUTHENTICATION.

mount processing failed because the server does not
do UNIX authentication. (AUTH_UNIX). OS/390 does
not support other authentication such as Kerboros.
System Action: The mount command ended with an
error.
User Response: Verify that the server actually does
not support AUTH_UNIX authentication. Notify the
server system administrator.
Source: OS/390 NFS client, module GFSCMNTD
GFSC300E
MISSING LEFT PARENTHESIS IN text

KEYWORD.
Explanation: Specified keyword, text, is missing a left

parenthesis.
text
The installation or mount parameter keyword.
System Action: Network File System Client
processing stops if the error occurs in the DFSMS/MVS
NFS client installation parameter. The mount command
failed if the error is in the mount parameter.
console message and notify the MVS system
programmer.
System Programmer Response: If the error is in the
mount parameter, correct the parameter, and reissue
the mount command. If the error occurs in the
DFSMS/MVS NFS client installation parameter, correct
the parameter, stop OS/390 UNIX System Services, and
restart OS/390 UNIX System Services.

programmer.
Source: DFSMS/MVS NFS Client
Detecting Module: GFSCPARS
GFSC302E
Explanation: Specified keyword, text, is missing a

right parenthesis.
text
processing stops if the error is in the Network File
System Client installation parameter. The mount
command failed if the error is in the mount parameter.
programmer.
GFSC303E

GFSC301E
PARSE FAILED ON NUMERIC FIELD

FOR text KEYWORD.
Explanation: Specified keyword, text, contains

alphabetic data in numeric field.
text
MISSING RIGHT PARENTHESIS IN text

KEYWORD.
THE SPECIFIED VALUE d_digit1 IS NOT

IN THE RANGE OF d_digit2 TO d_digit3
FOR text KEYWORD.
Explanation: The value, d_digit1, specified in the

keyword, text, must be between the minimum value,
d_digit2, and the maximum value, d_digit3.
d_digit1
The value specified in the installation or mount
parameter.
d_digit2
The minimum allowed value.
d_digit3
The maximum allowed value.
text
208

programmer.
GFSC304E
PARSE FAILED ON ALPHABETIC

FIELD FOR text KEYWORD.
Explanation: Specified keyword, text, contains

numeric data for alphabetic field.
In the message text, text2 is the installation or mount

parameter keyword.
programmer.
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
parameter, correct the option for the keyword, text2,
stop OS/390 UNIX System Services, and restart OS/390
UNIX System Services.
GFSC306E
text
programmer.
Explanation: An incorrect option, text, has been

specified for the keyword, delim.
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
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').
cr
The cr option for the installation or mount delim

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

FOR text2 KEYWORD, VALID OPTION
IS Y OR N.
crlf
The crlf option for the installation or mount delim
delimiter followed by the EBCDIC line feed delimiter
(X'0D25').
Explanation: An incorrect option, text1 , was specified

for the keyword, text2.
In the message text, text1 is one of the following:
Y
Yes option for the installation or mount parameter

keyword.
No option for the installation or mount parameter

keyword.
INCORRECT OPTION text SPECIFIED

FOR DELIM KEYWORD, VALID OPTION
IS BINARY, NL, CR, LF, CRLF, OR
LFCR.
lfcr
The lfcr option for the installation or mount delim
followed by the EBCDIC carriage return delimiter
(X'250D').
209

programmer.
delim, and reissue the mount command. If the error
parameter, correct the option for the keyword, delim,
GFSC307E
text IS AN INCORRECT KEYWORD FOR

MOUNT PARAMETER.
Explanation: text can only be specified as an

installation parameter.
GFSC310I
Explanation: The keywords, readahead and

delaywrite, will be ignored because datacaching has
been set off.
System Action: DFSMS/MVS NFS client continues
processing.
programmer.
System Programmer Response: Check parameters
to make sure that datacaching is supposed to be off.
GFSC311I
System Action: The mount command failed.

System Programmer Response: Correct the mount
parameter keyword, text.
GFSCPARS
GFSC309E
UNKNOWN KEYWORD ENCOUNTERED

AROUND POSITION d_digit.
Explanation: The keyword specified in position,

d_digit, is not a valid keyword.
d_digit
The installation or mount parameter keyword
position.
programmer.
mount parameter, correct the keyword, and reissue the
mount command. If the error occurs in the DFSMS/MVS
NFS client installation parameter, correct the keyword,
210
READAHEAD AND DELAYWRITE

OPTIONS WILL BE IGNORED AS
DATACACHING IS OFF.
CLN_CCSID AND SRV_CCSID WILL BE

IGNORED AS XLAT OPTION IS OFF.
Explanation: The keywords, cln_ccsid and

srv_ccsid, will be ignored because xlat has been set
off.
processing.
programmer.
to make sure that xlat is supposed to be off.
GFSC312I
ACREGMIN, ACREGMAX, ACDIRMIN,

AND ACDIRMAX OPTIONS WILL BE
IGNORED AS ATTRCACHING IS OFF.
Explanation: The keywords, acregmin, acregmax,

acdirmin and acdirmax, will be ignored because
attrcaching has been set off.
processing.
programmer.
to make sure that attrcaching is supposed to be off.
GFSC313I
RETRANS OPTION WILL BE IGNORED

AS HARD OPTION IS ON.
Explanation: The keyword, retrans, will be ignored

because hard has been set on.
processing.
programmer.
to make sure that hard is supposed to be on.

GFSC318E
READ FAILED FOR NETWORK FILE

SYSTEM CLIENT MOUNT
PARAMETERS.
Explanation: An error occurred while the Network File

System Client was processing the mount parameters.
This message follows other messages, GFSC3xxE, that
describe the error in greater detail.
System Programmer Response: Correct the mount
parameter options, and reissue mount command.

GFSCPARS
GFSC315E
GFSC319E
ERROR ENCOUNTERED WHILE

PARSING MOUNT PATH, REASON
CODE reason_code.
Explanation: The specified mount path is not correct.

reason_code
Explanation: text can only be specified as a mount

parameter.
text
The incorrect installation parameter keyword.

programmer.
System Programmer Response: Refer to OS/390
UNIX System Services Messages and Codes for a
description of the reason code reason_code. Correct the
mount path, and reissue the mount command.
GFSC317E
ERROR ENCOUNTERED WHILE

PARSING HOSTNAME, REASON CODE
reason_code.
text IS AN INCORRECT KEYWORD FOR

INSTALLATION PARAMETER.

processing stops.
programmer.
System Programmer Response: Correct the Network
File System Client installation parameter, stop OS/390
UNIX System Services, and restart OS/390 UNIX
System Services.
GFSC320E
Explanation: The specified hostname is not correct.

INCORRECT OPTION text SPECIFIED

FOR DELIM KEYWORD, VALID OPTION
IS BINARY, CR, CRLF, CRNL, LF, LFCR,
OR NL.
reason_code
Explanation: An incorrect option, text, has been

specified for the keyword, delim.

programmer.
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
and treats any delimiters on input as data.

description of the reason code reason_code. Correct the
hostname, and reissue the mount command.
cr
The cr option for the installation or mount delim

delimiter (X'0D').
211
crlf
The crlf option for the installation or mount delim
delimiter followed by the EBCDIC line feed delimiter
(X'0D25').
crnl
The crnl option for the installation or mount delim
delimiter followed by the EBCDIC new line delimiter
(X'0D15').
lf
The lf option for the installation or mount delim

(X'25').
GFSC501I
CLIENT LOG DATA SET text

RE-INITIALIZED.
Explanation: The error log data set is re-initialized.

text
The associated data set name of the active
DFSMS/MVS NFS Client log data set.
Detecting Module: GFSCTLOG
lfcr
The lfcr option for the installation or mount delim
followed by the EBCDIC carriage return delimiter
(X'250D').
nl
The nl option for the installation or mount delim

parameter. Specifies the EBCDIC new line delimiter
(X'15').

programmer.
delim, and reissue the mount command. If the error
parameter, correct the option for the keyword, delim,
GFSC500I
CLIENT LOG DATA SET, text,

FLUSHED.
Explanation: The data buffer of the active client log

data set, text, was flushed to disk.
text
GFSC502E
CANNOT OPEN CLIENT LOG DATA

SET, text1, text2.
Explanation: DFSMS/MVS NFS client failed to open

client log data set.
text1
The DD associated with the client log data set
which cannot be opened.
text2
The failure reason of the C function, fopen.
processing stops.
programmer.
System Programmer Response: Fix client log data
set and reply to the OS/390 UNIX System Services
message to restart DFSMS/MVS NFS client.
GFSC503E
CLIENT LOGGING ENDED.
Explanation: DFSMS/MVS NFS client failed to

manipulate the client log data set. See previous
operator console message for the failure reason.
programmer.
set, stop DFSMS/MVS NFS client, and reply to the
OS/390 UNIX System Services message to restart
DFSMS/MVS NFS client.
212
GFSC504I
CLIENT LOG DATA SET SWITCHED TO

text.
Explanation: A no space or an I/O error condition

was detected while writing to the client log data set.
Network File System Client logging switched to the
other log data set, text.
text
GFSC505E
MISSING DD STATEMENT OR
INCORRECT DATA SET
ORGANIZATION FOR LOG DATA SET.
Explanation: The error log data set has incorrect data

set organization, or missing DD statement.
processing stops if the error occurred during
initialization time. Network File System Client processing
continues with client logging ended if the error occurred
after initialization time.
programmer.
System Programmer Response: Correct error log
data set DD statement or data set organization, stop
DFSMS/MVS NFS client, and reply to the OS/390 UNIX
System Services message to restart DFSMS/MVS NFS
client.

programmer.
set, stop DFSMS/MVS NFS client, and reply to the
OS/390 UNIX System Services message to restart
DFSMS/MVS NFS client.
GFSC700I

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
Version 1 of DFSMS/MVS.
In the message text, fmid is one of the following:
(HDZ11SE)
DFSMS/MVS Network File System Client FMID
started.
processing.
Detecting Module: GFSCMAIN
GFSC701I

SHUTDOWN IN PROGRESS.
Explanation: DFSMS/MVS NFS client shutdown

processing has started.
System Action: DFSMS/MVS NFS client shutdown


Detecting Module: GFSCTERM
GFSC506E
text1 FAILED FOR text2, text3.
Explanation: DFSMS/MVS NFS client failed to

manipulate the client log data set, text2.
GFSC702I
Explanation: DFSMS/MVS NFS client has completed

shutdown processing.
text1
The C function where the failure occurred.
text2
The associated data set name of the DFSMS/MVS
NFS Client log data set.

SHUTDOWN COMPLETE.
System Action: Network File System and its

associated subtasks have ended.
Detecting Module: GFSCTERM
text3
The reason for the C function failure.
213
GFSC703E

INITIALIZATION FAILED: NETWORK
FILE SYSTEM CLIENT IS ALREADY
STARTED.
memory is not available during the DFSMS/MVS NFS

client initialization. Do one or both of the following
before restarting the Network File System Client:
v Increase the REGION size for the client procedure.
Explanation: Only one Network File System Client

can be started on an MVS system.
v Decrease the value specified for the bufhigh attribute

of the FILESYSTYPE parameter in the BPXPRMxx
Parmlib member.
System Action: This Network File System Client

ends.

programmer.
System Programmer Response: A prior
DFSMS/MVS NFS client session has not ended.
OS/390 UNIX System Services MVS end processing
should have ended the DFSMS/MVS NFS client colony
address space. Collect installation parameters, dumps,
DFSMS/MVS NFS client log data sets, and contact IBM
programming support personnel. Use the force
command to end the DFSMS/MVS NFS client colony
address space and then restart OS/390 UNIX System
Services.
GFSC704E

INITIALIZATION FAILED: DOWN LEVEL
SECURITY PRODUCT.
Explanation: RACF MVS security product is down

level.

GFSC707E
Explanation: The DFSMS/MVS NFS client has

detected an error in the installation parameters.
System Action: The Network File System Client ends.
programmer.
System Programmer Response: Check previous
console messages prefixed with GFSC. Correct the
parameter, stop OS/390 UNIX System Services, and
GFSC708E

programmer.
System Programmer Response: Check OS/390
Network File System Customization and Operation to
determine the required RACF level.
GFSC705E

INITIALIZATION FAILED: MAIN
STORAGE IS UNAVAILABLE.
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
large or the REGION size is too small.
programmer.
System Programmer Response: The requested
214

INITIALIZATION FAILED: INCORRECT
PARAMETER IN INSTALLATION
PARAMETERS.

INITIALIZATION FAILED: CDRA IS NOT
INSTALLED OR NOT AVAILABLE
RETURN CODE retc, REASON CODE
reason_code.
Explanation: CDRA initialization request failed.

Operator Response: Record MVS operator console
message and notify the MVS system programmer.
MVS System Messages, Vol 2 (ASB-ERB) for a
description of the return code return_code and the
reason code reason_code to determine the corrective
action.
Source: OS/390 NFS client, module GFSCMAIN
GFSC709E

INITIALIZATION FAILED: NOT
STARTED IN A STANDALONE COLONY
ADDRESS SPACE.

detected an error during initialization processing.
DFSMS/MVS NFS client was started by some other
means, other than OS/390 UNIX System Services MVS

kernel.
programmer.
System Programmer Response: The DFSMS/MVS
NFS client must be initialized by OS/390 UNIX System
Services kernel.
System Services and TCP/IP connection failure.

return_code
The error return code.
Operator Response: Collect any dumps,
DFSMS/MVS NFS client log data sets, and notify the
system programmer.
System Programmer Response: Collect installation
parameters, dumps, DFSMS/MVS NFS client log data
sets, and Contact IBM programming support personnel.
GFSC710E

INITIALIZATION FAILED: ESTAE
INITIALIZATION FAILED.

detected an error during the initialization processing.
system programmer.
GFSC711E

INITIALIZATION FAILED: UNIX System
Services KERNEL SERVICE FAILED.

detected an error during the second phase of
initialization processing.
system programmer.

GFSC713E

LOGGING IS TERMINATED.

detected an error. The Client Log daemon has ended.
system programmer.
Detecting Module: GFSCSTAE
GFSC714E
NETWORK FILE SYSTEM CLIENT SVC

DUMP REQUEST FAILED, RETURN
CODE returncd REASON CODE
reason_code.
Explanation: A request to take an MVS SVC dump

failed. Refer to the description of the SDUMP macro in
Services Reference LLA-SDU, for the meaning of the
return code, return_code, and reason code,
reason_code.
return_code
The error return code.
reason_code
GFSC712E

INITIALIZATION FAILED: SOCKET
CALL GETHOSTNAME FAILED,
RETURN CODE return_code.
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
Operator Response: Collect the MVS console log,

system programmer.
215

GFSC715E

ESTAE EXIT UNABLE TO COMPLETE,
ABEND CODE d_digit.
Explanation: The DFSMS/MVS NFS client recovery

exit has detected a recursive abend.
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
the client log data sets for more information. Search

GFSC0RPC
d_digit
The last abend code encountered by a secondary
instance of the ESTAE exit routine.
GFSC722E
System Action: The ESTAE processing stops. The

DFSMS/MVS NFS client ends.
console log, DFSMS/MVS NFS client log data sets, and
notify the system programmer.
parameters, dumps, the MVS console log, DFSMS/MVS
NFS client log data sets, and Contact IBM programming
support personnel.
GFSC716I

DAEMON TASK RESTARTED.
Explanation: The DFSMS/MVS NFS client detected a

stopped asynchronous daemon task. The DFSMS/MVS
NFS client has restarted the stopped asynchronous
daemon task.
System Action: The DFSMS/MVS NFS client daemon
has restarted. DFSMS/MVS NFS client processing
continues.
A SOCKET COULD NOT BE CREATED,

returncd REASON CODE reasoncd.
Explanation: OS/390 NFS client Daemon or thread

processing failed to create a socket for network
communication.
System Action: If the error occurred in the daemon,
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
processing.
console log, OS/390 NFS client log data sets, and notify
description of the return code returncd and the reason
code reasoncd to determine the corrective action. If the
error occurs and the program is not in error, look at the
messages in the client log data sets for more
information. Search 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 related to the problem.
GFSC0RPC

GFSC723E
GFSC721E
UNABLE TO SETUP ERROR

RECOVERY (ESTAE), RETURN CODE
returncd.
Explanation: OS/390 NFS client daemon or thread

failed to setup error recovery. See OS/390 MVS
Reference ENF-IXG for information the ESTAE macro
return code, returncd.
processing.
216

ABEND @ module+offset.
Explanation: OS/390 NFS client encountered a

programming error. SVC dump was issued to capture
the diagnostic information.
System Action: OS/390 NFS client has initiated
shutdown processing.
System Programmer Response: Look at the
Detecting Module: OS/390 NFS client, modules
GFSC0RPC, GFSC1RPC, GFSC0BIO, GFSC1BIO, and

GFSC2BIO
-e
GFSC724E
GFSC841E
UNABLE TO BIND A RESERVED PORT

TO SOCKET socketnum.
Explanation: The MOUNT daemon or UMOUNT

thread failed to obtain a reserved port for socket,
socketnum, for network communication.
processing.
System Programmer Response: If the error occurs
the client log data sets for more information. Search
GFSC0RPC
GFSC725E
SOCKET, socketnum, COULD NOT BE

CLOSED, RETURN VALUE -1 RETURN
CODE returncd REASON CODE
reasoncd.
Display the list of exported directories from host

NFS server
UNKNOWN HOST text
Explanation: The user entered incorrect host address

information, text.
System Action: Command stops processing.
User Response: Correct syntax and re-issue the
command.
GFSC842E
CANNOT RESOLVE LOCAL HOST

NAME
Explanation: Local host name is not found.

User Response: Contact your system administrator to
check TCP/IP configuration.
GFSC843E
UNKNOWN FLAG -character
Explanation: An incorrect option, -character, is

specified.
command.
Explanation: While closing a socket, socketnum, an

error returncd was detected.
GFSC845I
System Action: OS/390 NFS client continues

processing.
Explanation: This is the usage for the os22mvs and

mvs2os2 commands. text is the command as entered
by the user. The valid parameters are as follows:

description of the return code returncd and the reason
code reasoncd to determine the corrective action. If the
error occurs and the program is not in error, look at the
GFSC0RPC
USAGE: text INPUT OUTOUT
input
Absolute path name of the input file to be converted
output
Absolute path name of the output file
GFSC846E
CANNOT OPEN INPUT FILE, text1:text2
Explanation: Cannot open input file, text1. text1 is the

input path name as entered by the user. text2 is the
failure information returned when attempting to open the
input file.
GFSC840I
usage: text [-a] [-d] [-e] [host]
Explanation: This is the usage for the showmount

command. text is the command as entered by the user.
The valid options are as follows:
-a
Display all mounts in the format

Hostname:Directory from host NFS server
-d
Display only directory names of all mounts from

host NFS server
User Response: Check input file, text1.

GFSC847E
CANNOT OPEN OUTPUT FILE,

text1:text2
Explanation: Cannot open output file, text1. text1 is

the output path name as entered by the user. text2 is
the failure information returned when attempting to open
the output file.
217
User Response: Check output file, text1.

GFSC848E
CANNOT READ INPUT FILE, text1: text2
Explanation: Cannot read input file, text1. text1 is the

input path name as entered by the user. text2 is the
failure information returned when attempting to read the
input file.
User Response: Check input file, text1.
GFSC849E

User Response: Check output file, text1.
INPUT PATH NAME CANNOT BE
EQUAL TO OUTPUT PATH NAME.
Explanation: Input path name cannot be equal to

output path name.
command.
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
218
MUST BE A ROOT USER TO ISSUE

character flag
Explanation: The option, character, can only be

issued with the root authority.
User Response: Contact your system administrator to
issue this command.
GFSC856E
CANNOT WRITE OUTPUT FILE, text1:

text2
Explanation: Cannot write output file, text1. text1 is

the output path name as entered by the user. text2 is
the failure information returned when attempting to write
the output file.
GFSC850E
GFSC855E

COMMAND, text, FAILED RETURN
REASON CODE reasoncd
Explanation: The command, text, failed.

return code, returncd. Refer to OS/390 Network File
System Customization and Operation for further
information on the reason code, reasoncd.
GFSC858E
DIRECTORY text NOT MOUNTED.
Explanation: The directory, text, was not mounted.

User Response: Issue nfsstat -m to view the list of
active mount points. If the mount point does not exist,
contact system administrator to mount the directory.
Chapter 7. GOS Messages

GOS000I
SOM/MVS SUBSYSTEM ssname:

PRODID=productid PRODLVL=productlvl
COMPID=compid (C) COPYRIGHT IBM
CORP. 1995, 1997 ALL RIGHTS
RESERVED. U.S. GOVERNMENT
USERS RESTRICTED RIGHTS - USE,
DUPLICATION, OR DISCLOSURE
RESTRICTED BY GSA ADP SCHEDULE
CONTRACT WITH IBM CORP.
Explanation: This is a proprietary statement

concerning the use of the SOMobjects product. The
second line of the message indicates the product id,
product level, and component id of the product.
ssname
is the name of the SOMobjects subsystem.
productid
The SOMobjects product id.
productlvl
The SOMobjects product level.
than 8 characters, begins with an invalid symbol, or

contains an imbedded blank.
ssname
System Action: SOMobjects subsystem initialization
continues. The specified command prefix value is
ignored and as a default, the subsystem name ssname
is used as the command prefix.
Operator Response: If the default command prefix is
unacceptable, enter a CANCEL command prefixed by
the ssname to cancel the SOMobjects subsystem
immediately. Then if the bad command prefix was
entered by you as a parameter on the START command
when you first started SOMobjects, re-enter the START
command to restart the SOMobjects subsystem with a
valid command prefix value.
If the bad command prefix was not specified by you on
the START command, notify your system programmer.
System Action: SOMobjects subsystem processing

continues.
System Programmer Response: If the bad command

prefix was specified as a parameter in the job procedure
that was used to start the SOMobjects subsystem,
correct the command prefix parameter in the procedure
so the next time the subsystem is started, the desired
command prefix will be used.
Source: SOM
Source: SOM
GOS006I
GOS008I
compid
The SOMobjects component id.
SOM/MVS SUBSYSTEM JOBNAME

jobname IS NOT VALID.
Explanation: The SOMobjects procedure name, which

is used as the name of the subsystem, is not a valid 1-4
character name.
SOM/MVS ssname COMMAND PREFIX

IS cmdprefix
Explanation: The command prefix that is being used

by the SOMobjects subsystem ssname is cmdprefix. All
commands entered for the subsystem should begin with
this prefix.
jobname
The name of the SOMobjects job or started
procedure.
ssname
The name of the SOMobjects subsystem.
System Action: The SOMobjects address space

ends.
cmdprefix
is a 1-8 character command prefix.

SOMobjects job name/procedure name is a valid
subsystem name (1-4 characters).
System Action: SOMobjects subsystem initialization

continues.
Source: SOM
GOS007I
SOM/MVS ssname INPUT COMMAND

PREFIX IS NOT VALID. DEFAULT
PREFIX USED.
Operator Response: Whenever you enter one of the

commands supported by the SOMobjects subsystem,
you must begin the command with the indicated
command prefix (e.g., cmdprefix STATUS).
Source: SOM
Explanation: A command prefix value that was

specified as input to the SOMobjects subsystem
ssname is not valid. The prefix value is either greater
219
GOS009I
SOM/MVS ssname INITIALIZATION

COMPLETE.
Explanation: The SOMobjects subsystem ssname has

completed its initialization.
Operator Response: If you were restarting the

SOMobjects subsystem after an error situation, ensure
that the first instance of the subsystem ends before
issuing the START command.
Source: SOM
ssname
GOS013I
System Action: The SOMobjects subsystem

continues processing. It is now ready to accept
distributed SOM requests.
Explanation: The SOMobjects subsystem ssname is

not a defined subsystem name known by the system.
Source: SOM
GOS010I
SOM/MVS ssname ENDED.
Explanation: The SOMobjects subsystem ssname has

completed shutting down.
ssname
System Action: The SOMobjects subsystem address
space ends.
ssname
System Action: The SOMobjects subsystem ends.
SOMobjects subsystem name ssname is defined as a
valid subsystem name in the IEFSSNxx SYS1.PARMLIB
member that was used to IPL the system.
Source: SOM
GOS019I
Source: SOM
GOS011I
SOM/MVS ssname INITIALIZATION

FAILED.
Explanation: The SOMobjects subsystem ssname

could not be successfully initialized. The specific
initialization error is indicated by a SOMobjects error
message or abend that was issued just prior to this
message.
ssname
SYSLOG to determine the error message or abend that
caused initialization to fail and then correct the condition
that caused the error.
Source: SOM
GOS012I
SOM/MVS ssname ALREADY ACTIVE.
Explanation: One instance of the SOMobjects

subsystem ssname already exists. Starting more than
one SOMobjects subsystem is not allowed.
ssname
System Action: The SOMobjects subsystem that
issued this message ends.
220
SOM/MVS ssname IS NOT A VALID

SUBSYSTEM.
INITIALIZATION COMPLETE FOR

SOM/MVS SERVER server_name WITH
ALIAS alias_name
Explanation: A SOMobjects server has completed

initialization. The ALIAS for this server is aliasname.
server_name
The name of the SOMobjects server, which is
specified on DSOM server utility commands. See
OS/390 SOMobjects Configuration and
Administration Guide for a descriptions of those
commands.
alias_name
The alias of the SOMobjects server.
System Action: The SOMobjects server continues
processing. It is ready to accept requests from
distributed SOM clients.
Source: SOM
GOS021I
SOM/MVS ssname SUBSYSTEM

FUNCTIONS DISABLED.
Explanation: In the process of ending either normally

or abnormally, the SOMobjects subsystem ssname
disabled the subsystem functions it normally provides
for jobs that use Distributed SOM (DSOM) services via
the SOMobjects subsystem.
ssname
Distributed SOM requests will no longer be processed.

Any usage of servers, clients, and DSOM utilities will be
affected.
Source: SOM
GOS022I
SOM/MVS ssname SUBSYSTEM

FUNCTION DISABLEMENT FAILED.

or abnormally, the SOMobjects subsystem ssname
attempted to disable the subsystem functions it normally
provides for jobs that use Distributed SOM (DSOM)
services via the SOMobjects subsystem. However, a
failure occurred that prevented the subsystem from
completely disabling all the subsystem functions it
supports.
cmdname
The name of the command that was entered.
System Action: The SOMobjects subsystem stops
Operator Response: If the keyword was misspelled,
enter the command again with the correct keyword
specified. Otherwise, if the keyword should not have
been specified, enter the command again without the
unsupported keyword.
Source: SOM
GOS025I
MVS/DSOM ssname cmdname

COMMAND ERROR -- NOT
AUTHORIZED TO ISSUE COMMAND.
Explanation: The operator/console is not authorized to

enter the command, cmdname.
ssname

Any jobs, managed by the subsystem shown in the
message text, that try to use DSOM services might
abnormally end.
Source: SOM
GOS023I
SOM/MVS SUBSYSTEM ssname

ALTERED TO USE THE PRIMARY
SUBSYSTEM.
Explanation: The SOMobjects subsystem is to be

started only under the primary subsystem. The system
issues this message if your installation specifies the
SOMobjects subsystem initialization routine,
GOSAMSSI, on the initialization statement for the
SOMobjects subsystem in the IEFSSNxx parmlib
member. The SOMobjects subsystem initialization
routine will always force the specified SOMobjects
subsystem is to be initialized under only the primary
subsystem. This message is written to hardcopy only.
ssname
System Action: System initialization continues.
Source: SOM
ssname
cmdname
The name of the command that was entered.
System Action: The SOMobjects subsystem stops
Operator Response: Contact your installations
security administrator to ensure both you and the
console are properly authorized to enter the command
that you were attempting.
Source: SOM
GOS026I
MVS/DSOM ssname STOP INITIATED.
Explanation: In response to a STOP command, the

SOMobjects subsystem ssname has initiated stop
processing.
ssname
System Action: The SOMobjects subsystem quiesces
its processing and ends processing for servers that are
in running. When all server activity ends, the
SOMobjects subsystem ends normally.
Source: SOM
GOS024I
SOM/MVS ssname cmdname COMMAND

ERROR -- SPECIFIED KEYWORD IS
NOT VALID.
Explanation: The command entered, cmdname,

specified a keyword that is not supported.
ssname
GOS027I
hh.mm.ss ssname HELP INFO

MVS/DSOM COMMAND SYNTAX: ...
STOP DAEMON ... CANCEL DAEMON
..... Not Supported
Explanation: This message is a multiline message

issued in response to the HELP command. It displays a
summary of the syntax for the commands supported by
the SOMobjects subsystem shown in the message text.
Chapter 7. GOS Messages
221
(prefix ITT) accompanying this message.
hh.mm.ss
The time in hours (00-23), minutes (00-59), and
seconds (00-59).
Source: SOM
ssname
Source: SOM
GOS031I
SOM/MVS ssname INITIALIZATION OF

DAEMON SUBTASK FAILED.
Explanation: The SOMobjects subsystem ssname

could not properly initialize the SOM subsystem
subtask. More error information may be available from
the SYSPRINT output, if available, or from the TRACE
log, if available.
ssname
SYSLOG or the jobs log or the SYSPRINT data set for
the job to determine the error message or abend that
caused initialization to fail. Analyze the TRACE log, if
one was requested. Ensure that the correct data sets
are specified for the GOSRTL1 DD. Correct the
condition that caused the error.
GOS033I
DSOM TRACE REQUEST FAILED.

OPTIONS ARE NOT ALLOWED.
Explanation: The system rejected the request to trace

the system object model (SOM). The TRACE command
specified options, but options are not allowed.
System Action: The system rejects the request to
trace SOM.
Operator Response: Enter the TRACE command
again without specifying any options.
Source: SOM
GOS041I
SOM/MVS ssname WAITING FOR

SERVERS TO END.

or abnormally, the SOMobjects subsystem ssname must
wait for distributed SOM (DSOM) servers to end before
the subsystem is ended.
ssname
System Action: The SOMobjects subsystem will wait
for the servers to end. If the servers do not end, the
SOMobjects subsystem stops waiting and finishes
ending. After that time, servers may end abnormally.
Source: SOM
Source: SOM
GOS042I
GOS032I
SYSDSOM COMPONENT TRACE

FAILED. DIAG1: nnnnnnnn xxxxxxxx
Explanation: The SYSDSOM (SOMobjects)

component tried to initialize component tracing using
default options. The system is now running without
component tracing for SYSDSOM.
nnnnnnnn
Used by IBM for problem determination.
xxxxxxxx
Used by IBM for problem determination.
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
222
SOM/MVS ssname WAITING FOR OMVS

TO START.
Explanation: In the process of initialization, the

SOMobjects subsystem ssname must wait for the
OS/390 UNIX address space to initialize before
completing subsystem initialization.
ssname
System Action: The SOMobjects subsystem waits for
the OMVS address space to initialize.
Source: SOM
Chapter 8. GPM Messages

GPM001I
PM OF OS/390 DATA SERVER ACTIVE
Explanation: The PM of OS/390 data server has been

initialized and is ready to receive connection requests
from PWS clients.
Source: Resource Measurement Facility (RMF) Performance Monitoring of OS/390 (PM of OS/390)
GPM002I
PM OF OS/390 DATA SERVER

TERMINATED
Explanation: The PM of OS/390 data server has

ended.
System Action: System processing continues.
GPM003I
PM OF OS/390 IDLE TIME EXCEEDED
Explanation: The time specified by the MAXIDLE

parameter for the PM of OS/390 data server has
elapsed without any transaction requests.
GPM006E
TCP/IP PORT NUMBER NOT

SPECIFIED
Explanation: The PM of OS/390 data server has been

started without a valid TCP/IP port parameter.
System Action: The PM of OS/390 data server ends
processing.
Operator Response: Specify a valid TCP/IP port
number with the START command of the PM of OS/390
data server.
GPM050I
GPMSERVE CANNOT FIND MEMBER

member IN PARMLIB
Explanation: The DDS host server address space
cannot find the specified PARMLIB member. It continues
processing and uses defaults parameters.
System Action: The host server continues the
initialization using default parameters.

processing.
Operator Response: Inform the system programmer.
Operator Response: Restart the PM of OS/390 data

server.
System Programmer Response: Make sure that a

valid GPMSRVxx PARMLIB member exists in the
parameter library (usually the PARMLIB concatenation).
System Programmer Response: If needed, specify a

longer period for the MAXIDLE parameter.
GPM004E
LIBRARY IS NOT IN APF TABLE
Explanation: The PM of OS/390 data server resides

in a load library without APF authorization.
processing.
System Programmer Response: Ensure that the PM
of OS/390 load library is APF authorized.
GPM005E
INVALID COMMAND FOR PM OF

OS/390
Explanation: An unsupported MODIFY command has

been entered for the PM of OS/390 data server.
GPM051I
TCP/IP IS NOT ACTIVE ON THE OS/390

HOST
Explanation: The TCP/IP component of OS/390 is not
active on the OS/390 host. The GPMSERVE address
space has detected that TCP/IP services are not
available.
System Action: The host server terminates.
TCP/IP component of OS/390 is active before the DDS
host server is started.
GPM052I
TRACE IS NOW (IN)ACTIVE
Explanation: This message is issued in response to
the MODIFY command for the GPMSERVE address
space with the TRACEON or TRACEOFF option.
223
System Action: If the trace is active, GPMSERVE will

put its trace output to DDNAME SYSOUT. If the trace is
inactive, GPMSERVE will no longer write trace output to
DDNAME SYSOUT.
GPM054I
PERMANENT ERROR IN PM OF OS/390

SERVER THREAD
Explanation: The DDS host server has detected that
an important component of the server address space
has encountered a permanent error. In this case, the
component that accepts incoming TCP/IP session
requests has abnormally terminated. The most probable
cause for this problem is, that TCP/IP is inactive or has
produced an error.
System Action: The component is restarted. After 5
unsuccessful requests. the component is deactivated.
System Programmer Response: Make sure that all
required prerequisites for the component are active and
operational (for example, TCP/IP). Make sure that the
specified port in the GPMSRVxx PARMLIB member
(SESSION_PORT option) is free and can be used by
the DDS host server.
GPM055I
SESSION WITH partner ABNORMALLY

TERMINATED
Explanation: A session with the specified partner has
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
v A symbolic host name such as
smith.boeblingen.ibm.com
v A unix path name such as /tmp/GPMServe.C00
System Action: The session is terminated
immediately.
timeout option in the GPMSRVxx PARMLIB member
(TIMEOUT option) is set properly, and that the DDS
host server is active.
GPM056I
SYNTAX ERROR IN GPMSRVNN

MEMBER. LINE: ll NEAR TEXT ttttttt
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.
224
System Action: The server is terminated immediately.

erroneous option member.
GPM057I
SPECIFIED HOSTNAME hostname

CANNOT BE RESOLVED
Explanation: The ACCEPT_DATAGRAM parameter in
the GPMSRVxx member contains a hostname, that can
not be resolved by the name server.
System Action: The indicated hostname is discarded.
GPM058I
I/O ERROR READING PARMLIB

MEMBER name
Explanation: The DDS host server address space
detected an I/O error reading the specified PARMLIB
member. It continues processing and uses default
parameters.
System Programmer Response: Make sure that a
valid GPMSRVxx PARMLIB member exists in the
parameter library (usually the PARMLIB concatenation).
GPM059I
COMMAND ccccc IS NOT VALID
Explanation: The MODIFY command that was issued
against the DDS data server is not a valid command.
System Action: The command is ignored.
User Response: Specify a valid command.
GPM060I
DDS SERVER READY FOR

COMMANDS
Explanation: The DDS server is now accepting
commands from the console.
GPM061I
OPTIONS IN EFFECT: options
Explanation: This message lists the currently active
options for the DDS server.
GPM062I
component last_status
Explanation: This message displays the status of an
active component of the DDS server. The component
may be:
RMF-REFR
The automatic data refresher
DM-SERV
The datagram server
INET-LIS
Task that listens for incoming TCP/IP

requests
CMD-HNDL
MODIFY command handler
INET-CLI
TCP/IP client
UNIX-CLI
UNIX client
HTTP-LIS
The task that listens for incoming

HTTP requests
HTTP-CLI
The HTTP session client
System Action: None

User Response: None
GPM063I
PERMANENT ERROR IN DM/390

SERVER THREAD
component that processes incoming performance
request datagrams has abnormally terminated. The
most probable cause for this problem is, that TCP/IP is
inactive or has produced an error.
specified port in the GPMSRVxx PARMLIB member
(DATAGRAM_PORT option) is free and can be used by
the DDS host server.
GPM064I
PERMANENT ERROR IN UNIX

SESSION SERVER
component that accepts incoming session requests via
UNIX domain sockets (for example, PM of OS/390
APPC clients) has abnormally terminated.
operational (mainly OS/390 UNIX System Services).
Make sure that the pathname
/tmp/gpmserve/pmos390
is free and can be used by the DDS server.
If more than one instance of the DDS host server is
started, this message will appear for all instances but
the first one, because the UNIX socket pathname
cannot be shared by different servers. In this case,
always the first server will handle incoming UNIX
session requests.
This message might be caused by using the old OS/2
version of PM of OS/390 which is not supported
anymore. Please, insure that only the Java Edition of
PM of OS/390 will be used.
GPM065I
SERVER NOT STARTED FROM AN

AUTHORIZED LIBRARY
Explanation: The DDS host server has not been
started from an APF-authorized library, but APF
authorization is necessary for the GPMDDSRV host
server module.
System Action: The host server is terminated.
library, where the GPMDDSRV module resides (usually
SYS1.SERBLINK) is APF-authorized.
GPM066I
DDS SERVER TERMINATED
Explanation: The DDS host server has terminated.
System Action: 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.
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.
226

IAR002A
REAL = xxxx IS TOO LARGE,

MAXIMUM AVAILABLE IS yyyy.
RESPECIFY OR PRESS ENTER FOR
THE DEFAULT
Explanation: The system cannot allocate the

requested V=R area because it would overlap the virtual
storage allocated for the common service area (CSA).
xxxx
The kilobytes of central (real) storage specified.
yyyy
The maximum kilobytes of central storage

allowed.
System Action: The system waits for the operator to

reply.
IAR004I
THE RSU PARAMETER WAS NOT

COMPLETELY SATISFIED
Explanation: During system initialization, the real

storage manager (RSM) found that system storage
requirements and the REAL parameter have not left
enough central storage to satisfy the reconfiguration
storage units (RSU) parameter. The REAL and RSU
parameters are in the IEASYSxx parmlib member.
System Action: The system makes available as many
storage units as possible for reconfiguration, but the
RSU parameter is not completely satisfied.
Operator Response: Enter a Display M command to
determine which storage units are available for
reconfiguration. Notify the system programmer.
Operator Response: Reenter the parameter with a

value equal to or less than yyyy or press ENTER to get
the default. The default value for the REAL parameter is
the smaller of the following two values:

parameters in IEASYSxx before the next IPL.
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
Source: Real storage manager (RSM)

Detecting Module: IARMS, IAXMS
IAR003W
AN INVALID SEGMENT TABLE ENTRY

WAS FOUND FOR THE area AREA
Explanation: During system initialization, the real

storage manager (RSM) attempted to page protect an
area. RSM found an incorrect segment table entry
(SGTE) for this area.
In the message text, area identifies the area to be page
protected and is one of the following:
PREFERRED AREA HAS EXPANDED,

RECONFIGURABILITY AND
PERFORMANCE MAY BE IMPAIRED.
CHECK RSU VALUE.
Explanation: The real storage manager (RSM)

converted one or more nonpreferred frames to preferred
frames. The system may no longer be able to
reconfigure all or part of the storage in the nonpreferred
area. If this expansion involves frames below 16
megabytes, the system can page fix these frames,
which might lead to performance problems.
System Action: The system can use the newly
designated frames as preferred storage for additional
long term resident pages.
MLPAModified link pack area

EXTENDED MLPA
READ-ONLY NUCLEUS
NUCMAPNucleus map
PLPAPageable link pack area
EXTENDED PLPA
BLDLBuild directory entry list
FLPAFixed link pack area
EXTENDED FLPA
Operator Response: Enter a Display M command to

determine the number of frames remaining in the
nonpreferred area.
System Action: The system enters wait state X'A21'.

wait state code X'A21'.
Detecting Module: IARUC, IAXUC

reconfigurable storage unit (RSU) value specified in the
IEASYSxx parmlib member is appropriate for your
installation. See OS/390 MVS Initialization and Tuning
Reference for more information about the IEASYSxx
parmlib member.

programmer response for wait state code X'A21'.
Detecting Module: IARMN, IAXMN
227
IAR006A
INVALID {VRREGN|REAL|RSU} PARM RESPECIFY OR PRESS ENTER FOR

THE DEFAULT
Explanation: The VRREGN, REAL, or RSU parameter

contains a value that is not valid.
reply.
Operator Response: Reenter the VRREGN, REAL, or
RSU parameter with a valid value.
Detecting Module: IARMU, IARMS, IARMT, IAXMU,
IAXMS, IAXMT
IAR007I
RSM COMPONENT TRACE DATA

SPACE IS NAMED SYSIARnn.
Explanation: The operator started the real storage

manager (RSM) component trace using the TRACE CT
operator command and requested that RSM use a data
space for its trace buffers.
If the TRACE command specified NODMPOFF but not
DMPREC, the system does not dump these buffers.
The operator has to request a dump.
SYSIARnn
The name and number of the data space.
System Action: The system starts the RSM
component trace. RSM uses data space SYSIARnn to
contain the trace data.
Operator Response: Use the data space name in this
message to obtain the RSM trace buffers in an SVC
dump requested by a DUMP command or in a
stand-alone dump. However, to obtain the dump when
the RSM trace is turned off or through the use of the
DMPREC option, the data space name is unnecessary.
Detecting Module: IARQC
IAR008E
RSM TRACE TERMINATED, text
Explanation: The operator attempted to start the real

storage manager (RSM) component trace using the
TRACE CT operator command. RSM did not start the
trace.
In the message text, text tells why RSM did not start the
trace, as follows:
ENVIRONMENTAL ERROR.
INSUFFICIENT STORAGE FOR TRACE BUFFERS.
INSUFFICIENT STORAGE FOR TRACE
INITIALIZATION.
INVALID PARAMETER SPECIFIED FOR BUFF=
OPTION.
228
PREVIOUS INVOCATION TERMINATION HAS NOT

COMPLETED.
THE RSM TRACE DATA SPACE COULD NOT BE
CREATED.
TOTAL SIZE OF BUFFERS EXCEEDS TRACE
DATA SPACE SIZE.
UNIDENTIFIED OPTION.
System Action: The system does not start the RSM
component trace.
Operator Response: Depending on the value of text,
do one of the following:
INVALID PARAMETER SPECIFIED FOR BUFF=
OPTION or UNIDENTIFIED OPTION
One of the options is incorrect. Correct the error.
Reenter the TRACE command.
PREVIOUS INVOCATION TERMINATION HAS NOT
COMPLETED
Wait a few minutes and reenter the TRACE
command. If the error occurs again, contact the
IBM Support Center.
System Programmer Response: Depending on the
value of text, do one of the following:
ENVIRONMENTAL ERROR or THE RSM TRACE
DATA SPACE COULD NOT BE CREATED
An unexpected error occurred during trace
initialization. Contact the IBM Support Center.
INSUFFICIENT STORAGE FOR TRACE BUFFERS
There is not enough fixed common service area
(CSA) storage for trace buffers. First, ensure that
the size specified on the BUFF option is correct. If
the BUFF option was specified correctly, then either
reduce the amount specified or increase the
amount of CSA available to the system.
INSUFFICIENT STORAGE FOR TRACE
INITIALIZATION
There is not enough system queue area (SQA)
virtual or central storage available for trace
initialization; a request failed for a relatively small
amount of SQA storage. Increase the size of SQA
virtual or central storage.
TOTAL SIZE OF BUFFERS EXCEEDS TRACE DATA
SPACE SIZE
The size of the trace buffers that reside in fixed
CSA storage is larger than the size of the trace
data space. The size of the fixed trace buffers must
be smaller than the data space size so they can be
copied to the data space. Respecify the size of the
fixed buffers and the size of the trace data space.
Detecting Module: IARQC
IAR009I
RSM COMPONENT TRACE HAS LOST

AN ENTRY BECAUSE ALL BUFFERS
WERE FULL.

manager (RSM) component trace and requested that a
trace data space be used to contain the trace data.
RSM lost some of the trace entries because it was
creating trace entries faster than it could copy them
from central storage to the trace data space.
System Action: The RSM component trace continues.
Trace entries continue to be lost until RSM finishes
copying the trace buffers to the data space. RSM then
re-uses the buffers for newer trace entries.
System Programmer Response: If the RSM trace
successfully captured enough data to diagnose the
problem, the message indicates no problem. When the
trace is turned off, examine the trace entries in the
dump. The trace data gives the number of entries lost.
If the trace did not capture enough data to diagnose the
problem, re-create the problem and ask the operator to
start the trace again and either:
v Increase the size of the central storage trace buffers,
using the BUFF option
v Decrease the need for buffers by specifying fewer
RSM trace functions and events
Detecting Module: IARQZ, IAXQZ

IAR011I
RSM COMPONENT TRACE EXTERNAL

WRITER MAY HAVE LOST ENTRIES

manager (RSM) component trace and requested that
the system write the trace entries to a trace data set
through the external writer. The system could not write
the trace entries to the data set for one of the following
reasons:
v The operator did not start the external writer before
connecting the RSM component trace to the external
writer.
v RSM reused the full trace buffer before the system
could write the trace entries out to the trace data set.
Some older trace entries have been lost.
System Action: The system continues processing the
RSM component trace.
System Programmer Response: Do one of the
following:
v If you did not start the external writer, start it before
connecting the RSM component trace to the external
writer,
v Use IPCS to examine the trace entries that the
system collected. If the trace did not collect enough
data to successfully diagnose the problem, start the
trace again and either:
Use more trace buffers.
Increase the size of the trace buffers.
IAR010I
RSM COMPONENT TRACE HAS

WRAPPED AN ALREADY FULL
BUFFER.

manager (RSM) component trace and requested that
the trace data be collected in central storage buffers.
RSM overlaid some older trace entries with newer trace
entries when the central storage buffers filled up.
System Action: The RSM component trace continues.
Newer trace entries continue to overlay older trace
entries.
System Programmer Response: This message
almost always appears when the RSM component trace
is being used without a trace data space. It usually does
not indicate a problem. When the trace is turned off,
examine the trace entries in the dump. If the trace did
not capture enough data to diagnose the problem,
re-create the problem and ask the operator to start the
trace again and either:
v Increase the size of the central storage trace buffers
v Use a trace data space

IAR011W
A PAGE WITHIN FLPA IS NOT PAGE

FIXED.

detected pageable storage within the range of the fixed
link pack area (FLPA) or the EXTENDED FLPA.
wait state X'A20'.
programmer response for wait state X'A20'.
IAR012W
A PAGE WITHIN PLPA OR MLPA HAS

NO COPY ON AUXILIARY STORAGE

detected a page within the range of the pageable link
pack area (PLPA), EXTENDED PLPA, the modified link
pack area (MLPA), or the EXTENDED MLPA that has
never been paged to auxiliary storage. Ranges of
229
system storage that are page protected must have a

copy on auxiliary storage so the system can refresh the
page if necessary.
System Action: The system enters wait state X'A2A'.
the additional storage should be configured as

expanded storage and the system re-IPLed.

wait state X'A2A'.
Detecting Module: IARMI

programmer response for wait state X'A2A'.
IAR016I

IAR013I
xxxxxxM STORAGE IS
RECONFIGURABLE
Explanation: The indicated amount of storage,

xxxxxxM, has been made reconfigurable in response to
the value specified in the RSU parameter.
Detecting Module: IARMT, IAXMT
THE SYSTEM WAS IPLED IN ESAME

MODE WITH EXPANDED STORAGE
DEFINED. THIS STORAGE WILL NOT
BE USED BY THE SYSTEM
Explanation: In z/Architecture mode, the system does

not support expanded storage. However, the storage
may be defined as central storage and made available
to the system for use.
However, the expanded storage is not used.
Operator Response: None. However, to take full
advantage of the storage available in the configuration,
the expanded storage should be configured as central
storage and the system re-IPLed.
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,
230
Chapter 10. ICP Messages

ICP050D
SHOULD jobname WRITE TO LEVEL

xxx IOCDS? REPLY YES, NO, OR
CANCEL
Explanation: A job processed the input/output

configuration program (IOCP) with a WRTCDS option
other than NO on the PARM parameter of an EXEC
statement.
message ICP050D, that this job failed to build the level

indicated input/output configuration data set (IOCDS).
Operator Response: Notify the system programmer
that the job failed.
System Programmer Response: Review the
messages on the job listing, and take the necessary
actions.
Source: Input/output configuration program (IOCP)
jobname
Detecting Module: ICPPCNTL

The jobname.
xxx
The specified level.
System Action: IOCP issues this message to request

permission from the system operator for the job to write
to the specified level input/output configuration data set
(IOCDS) in the processor controller. If two or more jobs
are allowed to update concurrently the specified level
IOCDS, the outcome could be an IOCDS that is
logically inconsistent with the input from any one job.
Using this IOCDS at power-on reset or SYSIML CLEAR
could produce undesirable results.
Operator Response: A reply of YES allows the job to
continue processing and, if no errors are encountered,
to replace the input/output configuration data in the
specified level IOCDS in the processor controller with
the input/output configuration data generated by this
job. Use the IOCDSM frame to ensure the level IOCDS
is not write-protected.
A reply of NO allows the job to continue generating
input/output configuration data in storage and to
produce reports, but does not permit the job to replace
the input/output configuration data in the level IOCDS in
the processor controller.
ICP057I
IOCP JOB jobname SUCCESSFUL.

LEVEL xxx IOCDS REPLACED.
Explanation: A job was processing the input/output

configuration program (IOCP) with the WRTCDS=
option on the PARM parameter of an EXEC statement.
jobname
The jobname.
xxx
System Action: IOCP abnormally ends the job with a

return code of 4. IOCP issues this message to inform
the system operator, who had previously granted
permission to write the IOCDS in response to message
ICP050D, that this job successfully replaced the level
indicated input/output configuration data set (IOCDS).
Operator Response: Follow the installation
procedures.
A reply of CANCEL ends the job immediately with

system completion code X'222'.
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
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
231
232
Chapter 11. ICT Messages

ICT010I
CRYPTOGRAPHY SYSTEM MASTER

KEY HAS BEEN SET
Explanation: The key generator utility program has

successfully set the host master key. If there are any
control statements requesting updates to the secondary
key-encrypting keys, these statements are processed at
this time.
Note: The security administrator must ensure that an
authorized person was running the key generator
utility program. More information about the
requester is recorded in SMF record type 82.
System Action: Key generator utility processing
continues.
Source: Programmed Cryptographic Facility (PCF)
ICT011I
CRYPTOGRAPHY KEY UPDATE

STARTED
Explanation: The key generator utility program, has

successfully updated the cryptographic key data set
(CKDS) to reflect a new, changed, or deleted secondary
key-encrypting key. This message is issued only for the
first update to the CKDS for a secondary key-encrypting
key although the job may contain several update
requests.
continues.
ICT012I
ERROR IN EXECUTING KEY

GENERATOR UTILITY
Explanation: The key generator utility program did not

complete successfully. A message identifying the nature
of the problem is routed to the data set defined by the
SYSPRINT DD statement.
System Action: Key generator utility processing ends.
Application Programmer Response: Respond to the
problem identified by the message appearing in the data
set defined by the SYSPRINT DD statement.
ICT020I
synad message from VSAM while

processing CKDS
Explanation: A physical I/O error occurred while the

key manager was attempting to read the cryptographic
key data set (CKDS).
System Programmer Response: See the explanation
of the accompanying VSAM physical I/O error message.
If the volume caused the error, use a backup copy of
the CKDS on a different volume. (If you do not want to
re-IPL the system, be ensure that the new copy of the
CKDS uses the same host master key as the old copy.)
If the device caused the error, move the volume
containing the CKDS to an alternate device. To change
the volume or device, stop the Programmed
Cryptographic Facility (via IPL or an operator STOP
command) and restart it (via an operator START
command), specifying an alternate data set name on
the START command, if required. Rerun the job.
To ensure that you have all the messages issued for
this problem, specify MSGLEVEL=(1,1) for the job.
ICT021I
VIOLATION ON RETKEY BY text text is

USER (userid) GROUP (groupid) JOB (jjj)
STEP (sss)
Explanation: An unauthorized program has issued the

RETKEY SVC requesting that a data-encrypting key
enciphered under a cross key be enciphered again
under the host master key. The RACF (Resource
Access Control Facility) user (userid) and group name
(groupid) are given if they are available. Otherwise, the
job name (jjj) and step name (sss) are supplied. The
REMKEY field in SMF record type 82 contains the label
of the cross key.
Note: The security administrator must determine if an
attempted security violation occurred. Follow the
security procedures established by your
installation.
System Action: Key manager processing ends.
Operator Response: Notify the security administrator.
ICT022I
xxx ABEND DURING [GENKEY |

RETKEY ] PROCESSING
Explanation: An error occurred during processing of

either the GENKEY or RETKEY function of the key
manager. In the message, xxx indicates the system
completion code.
233

Application Programmer Response: Notify the
system programmer.
System Programmer Response: Respond to the
problem identified by the system completion code.
To ensure that a dump is produced for this problem, run
the job again with a SYSABEND DD statement.
ICT023I
KEY label HAS INCORRECT PARITY
Explanation: The key-encrypting key identified by

label has been read from the cryptographic key data set
(CKDS) by the key manager and the key manager has
determined that the clear form of the key has bad parity.
This situation can occur if there is a problem with the
CKDS. It can also occur when the CKDS used to
initialize the host master key in storage has been
replaced by a CKDS that contains a different host
master key but storage was not reinitialized. Storage is
initialized the first time you start the Programmed
Cryptographic Facility or run the key generator utility
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: If the CKDS was
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
master key in the CKDS that was used to initialize
storage.
If the listings indicate that the host master key values
are not the same, do one of the following:
v Replace the CKDS on the system with a CKDS that
contains the same host master key as the one in
storage. To replace the data set, stop the
Programmed Cryptographic Facility and restart it with
an operator START command that specifies the name
of the CKDS that contains the correct value for the
host master key. Rerun the job that failed.
v Reinitialize storage so that the value of the host
master key in storage matches the value in the
CKDS currently on the system. To reinitialize storage,
you can re-IPL the system and restart the
Programmed Cryptographic Facility with an operator
START command that specifies the name of the
CKDS currently on the system. Or, you can
reinitialize storage with the key generator utility
program, using the CHGM function and specifying a
host master key value that matches the value on the
current CKDS. To run the key generator utility
234
program, stop the Programmed Cryptographic

Facility, run the utility when there are no
cryptographic sessions or jobs running on the
system, and restart the facility. Rerun the job that
failed.
If host master keys are identical, or if the CKDS was not
replaced, use a backup copy of the CKDS. Stop the
Programmed Cryptographic Facility and restart it
specifying the name of the backup CKDS in the START
command. Do not use the original data set again. Rerun
the job that failed.
ICT024I
UNEXPECTED VSAM ERROR CODE rc

[FDBK code]
Explanation: An error occurred when the key

manager attempted to read the cryptographic key data
set (CKDS). In the message, rc is the return code that
identifies the error. If rc identifies a logical error, then
FDBK code indicates the specific logical error that has
occurred. For an explanation of the return code and
feedback code, see the description of the VSAM macro.
Correct the problem and rerun the job.
ICT030I
CRYPTOGRAPHY INITIALIZATION
UNABLE TO LOCATE name in LPA
Explanation: The Programmed Cryptographic Facility

installation process invoked by the operator START
command or the key generator utility program was
unable to locate the routine specified by name in a
search of the active link pack area queue and the link
pack area directory.
System Action: Programmed Cryptographic Facility
initialization processing ends.
Application Programmer Response: Determine if the
GENKEY or RETKEY installation exit routine (module
ICTMGR90 or ICTMGR95) is properly link edited into
SYS1.LPALIB. If the module has been replaced since
the Programmed Cryptographic Facility was installed,
check the linkage editor output from the most recent
change. If it has not been replaced, check the output of
the install process (SMP or SYSGEN) to see that the
module was properly installed. Correct the problem and
reissue the operator START command or rerun the key
generator utility program.

ICT031I
INVALID CRYPTOGRAPHY USER SVC

NUMBER SPECIFIED

initialization process invoked by the operator START
command or the key generator utility program has
determined that the options module, ICTOPTNS,
contains a user SVC number that is not valid.
System Programmer Response: Update the
installation options module, ICTOPTNS, to reflect a valid
user SVC number in the range of 200 through 255. See
the Programmed Cryptographic Facility Program
Directory for information on how to modify the options
module. When the update is complete, reissue the
operator START command or rerun the key generator
utility program.
ICT032I
UNABLE TO OPEN ddname

unable to open the data set identified by ddname. For a
VSAM data set, this message is accompanied by a
VSAM error message that further identifies the problem.
specified ddname has been included in the JCL for the
START procedure or in the JCL for the key generator
utility program. For a VSAM data set, see the
accompanying VSAM error message for additional
information. Correct the problem and reissue the
utility program.
ICT033I
LOAD FAILED FOR CRYPTOGRAPHY

INSTALLATION OPTIONS MODULE

unable to load the installation options module,
ICTOPTNS.
Application Programmer Response: Check the
output of the install process (SMP) to verify that the
installation options module was properly installed in
SYS1.LINKLIB. Correct the problem and reissue the
utility program.
ICT034I
UNABLE TO ESTABLISH ESTAE CODE
xxx

unable to establish an ESTAE recovery environment.
The code from ESTAE processing is specified by xxx.
Operator Response: If the code is 14, reissue the
operator START command. For all other codes, contact
your system programmer. When the problem is
corrected, reissue the START command.
Application Programmer Response: If the code is
14, rerun the key generator utility program. For all other
codes, contact your system programmer. When the
problem is corrected, or rerun the utility program.
exists, contact the IBM Support Center.
ICT035I

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

Correct the problem and rerun the job. If the volume
caused the error, use a backup copy of the CKDS on a
different volume. (If you do not want to re-IPL the
system, ensure that the new copy of the CKDS uses the
same host master key as the old copy.) If the device
caused the error, move the volume containing the
CKDS to an alternate device. To change the volume or
device, stop the Programmed Cryptographic Facility, if it
is active (via IPL or an operator STOP command). Make
the required change and then reissue the START
command or rerun the key generator utility program. If
applicable, specify the alternate data set name.
ICT036I
UNEXPECTED VSAM ERROR

PROCESSING CKDS CODE rc [FDBK
code]
Explanation: An error occurred during Programmed

Cryptographic Facility initialization processing while
reading the host master key from the cryptographic key
data set (CKDS). In the message, rc is the return code
that identifies the error. If rc identifies a logical error,
then FDBK code indicates the specific logical error that
has occurred.
System Programmer Response: For an explanation
of the return code and feedback code, see the
description of the VSAM macro. Correct the problem
and reissue the operator START command or rerun the
key generator utility program.
ICT040I
CRYPTOGRAPHY FACILITY HAS BEEN

DEACTIVATED: REQUESTS FOR NEW
CRYPTOGRAPHY SESSIONS WILL BE
REJECTED
Explanation: An operator STOP command has

successfully deactivated the Programmed Cryptographic
Facility. All current sessions or jobs using the EMK or
CIPHER functions of the facility can continue
processing. All new sessions or jobs requesting the
facility (using a GENKEY or RETKEY macro instruction)
will be rejected.

ICT041I

ACTIVATED
Explanation: An operator START command has

successfully activated the Programmed Cryptographic
Facility. All functions of the facility are currently
operational.
System Action: The Programmed Cryptographic
Facility is active.
ICT042I
START CRYPTO TERMINATED
Explanation: The START command procedure ended

abnormally when attempting to start the Programmed
Cryptographic Facility. Another message that explains
the nature of the error precedes this message.
System Action: START command processing ends.
The Programmed Cryptographic Facility is not active.
problem described by the preceding message.
ICT043I
UNABLE TO OPEN SYSCKDS
Explanation: The START command procedure used to

start the Programmed Cryptographic Facility was not
able to open the cryptographic key data set (CKDS)
defined by the SYSCKDS DD statement. This message
is accompanied by a VSAM error message that further
identifies the problem.
System Programmer Response: Verify that a DD
statement has been included in the START procedure
for the CKDS with the ddname SYSCKDS. Check the
operator START command.
ICT044I
START CRYPTO UNABLE TO

ESTABLISH ESTAE CODE xxx
Explanation: The START procedure used to start the

Programmed Cryptographic Facility was unable to
establish an ESTAE recovery environment. The return
code from ESTAE processing is specified by xxx.
236

operator START command. When the problem is
corrected, reissue the START command. For all other
codes, contact your system programmer.

Application Programmer Response: Supply a new

clear key value on the control statement or remove the
KEY parameter completely to let the key generator
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.
Rerun the utility program, specifying the CHGK function
on the EXEC statement and providing the corrected
control statement as input.
ICT045I
ICT1002

START CRYPTO OR KEY GENERATOR

ALREADY IN PROGRESS
Explanation: An operator START command was

issued to start the Programmed Cryptographic Facility
but the facility has already been started, the START
command procedure is currently running, or the key
generator utility program is running.
INVALID VERB
Explanation: A verb that was specified on a control

statement for the key generator utility program was not
valid. The control statement containing the error
precedes this message.
System Action: The START command is ignored.
System Action: Processing ends for this control

statement. Processing continues for any other control
statements.
Operator Response: If a START command was

issued when the Programmed Cryptographic Facility is
already active or the START command procedure is
already running, an operator STOP command must be
issued before another START command can be
accepted. If the key generator utility program is currently
running, reissue the START command when the utility
program ends.
Application Programmer Response: Correct the verb

on the control statement. The valid verbs are LOCAL,
REMOTE, CROSS, EXTRA-LOCAL, EXTRA-REMOTE,
EXTRA-CROSS, and INSTDAT. The verb must be
preceded and followed by a blank. Rerun the key
generator utility program, specifying the CHGK function
ICT046I
ICT1003
STOP CRYPTO IN PROGRESS
Explanation: An operator STOP for the Programmed

Cryptographic Facility has been accepted. STOP
command processing waits until all outstanding requests
to access the cryptographic key data set (CKDS) are
finished before closing the CKDS and stopping the
Programmed Cryptographic Facility task. (Requests to
access the CKDS are made by the GENKEY or the
RETKEY macro instructions.) Once the STOP command
is accepted, all new sessions or jobs requesting the
Programmed Cryptographic Facility are rejected.
System Action: STOP command processing waits
until the CKDS is not being used.
ICT1001
WEAK KEY SPECIFIED
Explanation: A weak clear key value was specified on

a LOCAL, REMOTE, or CROSS control statement for
the key generator utility program. The control statement
containing the weak key precedes this message.
statements.
SYNTAX ERROR IN KEY
Explanation: The clear key value specified on a

LOCAL, REMOTE, or CROSS control statement for the
key generator utility program was not valid. The control
statement containing the error precedes this message.
statements.
Application Programmer Response: Supply a valid
clear key value on the control statement. A valid value
consists of 16 hexadecimal digits. (Valid hexadecimal
digits are 0 through 9 and A through F.) Rerun the key
ICT1004
SYNTAX ERROR IN LABEL
Explanation: A label specified on a LOCAL, REMOTE,

or CROSS control statement for the key generator utility
program was not valid. The control statement containing
the error precedes this message.
237

statements.
requested on the control statement. The sum of these

two values must not exceed 9999.

label on the control statement. A valid label consists of 1
to 8 alphameric characters. Valid alphameric characters
are A through Z and 0 through 9. Rerun the key
Rerun the key generator utility program, specifying the

CHGK function on the EXEC statement and providing
the corrected control statement.
ICT1007

ICT1005
INVALID OR REDUNDANT KEYWORD

SPECIFIED
Explanation: A keyword parameter specified on a

LOCAL, REMOTE, or CROSS control statement for the
key generator utility program was redundant or not
valid. The control statement containing the error
statements.
keyword parameter or remove the redundant keyword
parameter on the control statement. Rerun the key
control statement.
STATEMENT REJECTED BY
INSTALLATION EXIT
Explanation: A control statement was rejected by the

key generator utility program installation exit routine.
The rejected control statement precedes this message.
statements.
Application Programmer Response: Follow local
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
corrected control statement.
ICT1008
REQUIRED PARAMETER
INFORMATION MISSING
Explanation: The key generator utility program found

that the value for the SETM, CHGM, or SEED
parameter on the EXEC statement is missing.
ICT1006
INVALID VALUE SPECIFIED ON EXTRA

STATEMENT
Explanation: One of the following conditions was

encountered on an EXTRA-LOCAL, EXTRA-CROSS, or
EXTRA-REMOTE control statement for the key
generator utility program:
v The first through fourth characters of the value for
label-base were not alphameric.
v The fifth through eighth characters of the value for
label-base were not numeric.
v An incorrect number of additional keys was
requested.
The control statement containing the error precedes this
message.
statements.
alphameric portion of the label-base is incorrect, supply
a valid value on the control statement. A valid value
consists of 4 alphameric characters. Valid alphameric
characters are A through Z and 0 through 9.
Otherwise, correct the numerical portion of the
label-base and/or the number of additional keys
238
Application Programmer Response: Supply the

missing value in the PARM field of the EXEC statement
and rerun the key generator utility program.
ICT1009
DUPLICATE LABEL; KEY NOT ADDED
Explanation: A user requested the key generator

utility program to add a label and its associated
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
statements.
Application Programmer Response: Assign a unique
label to the key and rerun the key generator utility
program, specifying the CHGK function on the EXEC
statement and providing the corrected control statement.
ICT1010
LABEL NOT FOUND; NOT

PROCESSED

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
label was not defined in the CKDS. The rejected control
statement precedes this message.
statements.
correct label and rerun the key generator utility program,
specifying the CHGK function on the EXEC statement.
ICT1011
synad I/O error message from VSAM
Explanation: A physical I/O error occurred when the

key generator utility program attempted to access the
SYSCKDS or SYSNCKDS data set.
If the volume caused the error, use a backup copy of
the CKDS on a different volume. (If you do not want to
re-IPL the system, ensure that the new copy of the
CKDS uses the same host master key as the old copy.)
If the device caused the error, move the volume
containing the CKDS to an alternate device.
Rerun the key generator utility program as 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 this listing
to determine which control statements were processed
successfully. Then rerun the utility program using the
CHGK function to process the remaining control
statements.
Detecting Module: ICTMKG00, ICTMKG01
ICT1012
PROCESSING TERMINATES DUE TO

INSTALLATION EXIT REQUEST
Explanation: The key generator utility program stops

processing at the request of the installation exit routine.
If the problem occurred while the utility program was
processing a change to the host master key, the
contents of the PARM field of the EXEC statement
precede this message. If the problem occurred while the
utility program was processing a SYSIN control
statement, the control statement precedes this
message.

procedures.
ICT1013
PROCESSING ENDED DUE TO ESTAE

OR STAE RETURN CODE xxx
Explanation: The key generator utility program

attempted to use the ESTAE system service, but the
error code xxx was returned.
No control statements are processed.
14, run the key generator utility program again. For all
other codes, contact your system programmer. When
the problem is corrected, rerun the utility program.
ICT1014
SYSIN DATA SET EMPTY; NO

PROCESSING OCCURRED
Explanation: The CHGK function of the key generator

utility program was requested but no control statements
could be found.
Application Programmer Response: Add the desired
control statements to the SYSIN data set and rerun the
Detecting Module: ICTMKG01
ICT1015
UNABLE TO [OPEN | CLOSE ] ddname

[CODE rc]
Explanation: The key generator utility program was

unable to open or close the data set defined by the DD
statement identified by ddname.
If the data set is a VSAM data set (SYSCKDS or
SYSNCKDS), the VSAM return code rc is included to
help identify the error.
Application Programmer Response: If the problem
occurred while trying to open a data set, check the JCL.
Be sure the required DD statements were included, that
they have the correct ddnames, and that they define the
correct data sets. The following ddnames are valid:
SYSCKDS, SYSNCKDS, SYSIN, and SYSMKDS.
239
An open failure can also occur if the SYSCKDS or

SYSNCKDS data set was defined without the proper
parameters. See Defining Storage for the CKDS and
the MKDS in OS/VS1 and OS/VS2 MVS Programmed
Cryptographic Facility: Installation Reference Manual for
instructions on using the access method services
DEFINE CLUSTER command.
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,
(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 to process the
remaining control statements.
For information on defining and reorganizing the CKDS,

see Defining Storage for the CKDS and MKDS in
OS/VS1 and OS/VS2 MVS Programmed Cryptographic
Facility: Installation Reference Manual. The commands
needed to define, reorganize and copy the data set are
described in your VSAM catalog administration books.
Notify the security administrator.

ICT1017

unable to run because the Programmed Cryptographic
Facility was active.
CRYPTOGRAPHY STARTED; INVALID

KEY GENERATOR REQUEST

ICT1016
INSUFFICIENT SPACE ON CKDS
Explanation: The key generator utility program could

not complete a request to update the cryptographic key
data set (CKDS) because there is insufficient space on
the target data set. The target data set is defined by the
SYSNCKDS DD statement if the CHGK function was
requested.
message.
Application Programmer Response: If the SETM or
CHGM function was requested and the host system
master key was not set (the contents of the PARM field
precede this message), define a larger target data set
for the CKDS and rerun the job. Otherwise, the key
generator utility program failed while processing a
SYSIN control statement and one of the following must
be done:
v Reorganize the target CKDS to force more efficient
space utilization.
v Define a larger data set for use as the new target
CKDS and copy the contents of the original target
CKDS to the larger data set.
Then, use this listing to determine which control
statements were processed successfully and rerun the
key generator utility program using the CHGK option to
process the remaining control statements.
Application Programmer Response: When the

Programmed Cryptographic Facility is stopped and there
are no cryptographic sessions or jobs running in the
system, rerun the key generator utility program to
change the host master key. Restart the Programmed
Cryptographic Facility by entering an operator START
command.
ICT1018
KEY GENERATION NOT ALLOWED text
Explanation: In the message, text is one of the

following:
TOD CLOCK ERROR
SEED NOT SUPPLIED
An error was encountered when the key generator utility
program attempted to read the time-of-day (TOD) clock,
the TOD clock was inoperative, or a seed value was not
supplied on the EXEC statement. Processing continues;
however, no keys can be generated.
continues.
involves the TOD clock, contact your service
representative. If a seed value was not supplied, ignore
this message unless message ICT1025 also appears. If
message ICT1025 appears, see the description of
message ICT1025.
240
ICT1019

KEY HAS BEEN SET

key-encrypting keys, they are processed at this time.
continues.
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.
CURRENT MASTER KEY

NEW MASTER KEY
NEW MASTER KEY COMPLEMENT SEED
An incorrect value was specified for the SETM, CHGM,
or SEED parameter in the PARM field of the EXEC
statement for the key generator utility program.
value in the PARM field of the EXEC statement. A valid
value consists of 16 hexadecimal digits. (Valid
hexadecimal digits are 0 through 9 and A through F.)
Rerun the key generator utility program.

keyword parameter in the PARM field. The valid
keyword parameters are SETM, CHGM, CHGK, and
SEED. Rerun the key generator utility program.
ICT1021
WEAK SYSTEM MASTER KEY

SPECIFIED
Explanation: A weak value for the new host master

key was specified in the PARM field of the EXEC
host master key value and its complement in the PARM
field of the EXEC statement. 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.
ICT1022
INVALID SYNTAX FOR text
Explanation: In the message, text is one of the

following:
ICT1023
INVALID RETURN CODE FROM

INSTALLATION EXIT; PROCESSING
TERMINATES
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
message.
installation exit routine to determine if there are any
problems in the module and make any necessary
corrections. Link edit the key generator utility program
with the corrected exit routine. (See Adding
User-Written Exit Routines in OS/VS1 and OS/VS2
Reference Manual.) Rerun the key generator utility
program as follows. Rerun the entire job if the SETM or
CHGM function was requested and the host master key
was not set (the contents of the PARM field precede
this message).
241
ICT1024
REQUIRED OPERAND[S] MISSING;

STATEMENT IGNORED
Explanation: While scanning a SYSIN control

statement, the key generator utility program could not
find one or more required parameters. LOCAL,
REMOTE, and CROSS control statements require a
label. EXTRA-LOCAL, EXTRA-REMOTE, and
EXTRA-CROSS control statements require a number
and a label-base. The REASGN control statement
requires an existing label and a new label. The control
statement containing the error precedes this message.
statements.
control statement. Rerun the key generator utility
to the cryptographic key data set (CKDS). In the

message, rc is the return code that identifies the error. If
rc identifies a logical error, then FDBK code indicates
the specific logical error that has occurred.
and rerun the utility program as follows. If the SETM or
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
to process the remaining control statements.
ICT1025
ICT1027
REQUIRED INPUTS FOR KEY

GENERATION NOT AVAILABLE

attempted to generate a key for a control statement and
either a problem occurred with the time-of-day (TOD)
clock or a valid seed value was not supplied on the
EXEC statement. Message ICT1018, which identifies
the specific problem, and the control statement being
processed when the problem occurred, precede this
message.
statements.
Application Programmer Response: Respond as
follows:
v If message ICT1018 stated that there is a problem
involving the TOD clock, contact your service
representative.
v If message ICT1018 stated that a seed value was
supplied, add a seed value to the EXEC statement.
Rerun the key generator utility program specifying the
the control statement that was being processed when
the problem occurred.
SYSTEM MASTER KEY PREVIOUSLY

SET; INVALID KEY GENERATOR
REQUEST
Explanation: An attempt was made to use the SETM

function of the key generator utility program to set host
master key, but the host master key has already been
set. Any change to it must be requested using the
CHGM function of the utility program.
Application Programmer Response: If you want to
change the host master key and secondary
key-encrypting keys, rerun the key generator utility
program specifying CHGM on the EXEC statement. If
you want to change secondary key-encrypting keys
only, rerun the utility program specifying CHGK on the
EXEC statement.
ICT1028
SYSTEM MASTER KEY
Explanation: When attempting to change the host

master key, the key generator utility program
encountered an incorrect current host master key value
in the PARM field of the EXEC statement.
ICT1026

[FDBK code]

generator utility program attempted to read from or write
242

value of the current host master key in the EXEC
statement and rerun the key generator utility program.

ICT1029
INVALID PARITY IN NEW MASTER KEY
Explanation: A value specified for the new host

master key in the PARM field of the EXEC statement for
the key generator utility program was not valid.
value for the new host master key and the complement
of the value in the EXEC statement. The new key value
must contain odd parity in each byte. Rerun the key
generator utility program.
ICT1031
Explanation: While scanning the PARM field of the

EXEC statement, the key generator utility program did
not find an expected delimiter or encountered an
unexpected delimiter.
Application Programmer Response: The valid
delimiters are comma, right and left parentheses, and
blank. Correct the error and rerun the key generator
utility program.
ICT1032

ICT1030
INVALID SMF DATA LENGTH FROM

TERMINATES
Explanation: The key generator installation exit

routine returned the SMF buffer with a value greater
than 64 in the length field.
System Action: The key generator utility program
does not include the installation-defined data in the SMF
record. The program writes the SMF record to the SMF
data set and stops processing.
with the corrected exit routine. (See Adding
User-Written Exit Routines in OS/VS1 and OS/VS2
Reference Manual.) Rerun the key generator utility
requested and the host master key was not set
remaining control statements. Notify the security
administrator.
INVALID DELIMITER IN PARM FIELD
CRYPTOGRAPHY EMK FUNCTION

FAILED - CODE xx
Explanation: An error occurred during the processing

of an EMK macro instruction issued by the key
generator utility program. In the message text, xx is the
error return code from the EMK macro. The values of xx
and their explanations are as follows:
Code
Explanation
The Programmed Cryptographic Facility has

not been initialized.
The operation requested was not valid; the

macro was not EMK.
12
An ESTAE recovery environment could not be

established.
32
The address of the clear key-encrypting key or

the address of the enciphered key-encrypting
key was specified as zero.

Application Programmer Response: Contact your
programming support personnel. When the problem has
been corrected, rerun the key generator utility program
as follows. If the SETM or CHGM function was
243
ICT1033
CRYPTOGRAPHY CIPHER FUNCTION

FAILED - CODE xx

of a CIPHER macro instruction issued by the key
error return code from the macro. The values of xx and
their explanations are as follows:
Code
Explanation

not been initialized. The data could not be
enciphered or deciphered.
The operation requested was not valid; the

macro was not CIPHER.
12

established.
16
The length of the data to be enciphered or

deciphered was specified as zero or as a
negative number.
20
The BRANCH=YES parameter was specified,

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.

system programmer. When the problem has been
corrected, rerun the key generator utility program as
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
this listing to determine which control statements were
processed successfully. Then rerun the utility program
using the CHGK function to process the remaining
control statements.
ICT1034
CRYPTOGRAPHY KEY TRANSLATION

FAILED - CODE xx
Explanation: An error has occurred during key

translation processing. The translation was requested by
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:
Code
Explanation

not been initialized.
The operation requested was not valid.
244
12

established.
24
Bad parity was detected in the local, remote, or

cross key.
28
The program requesting the key translation

function is not APF-authorized or in supervisor
state or running under storage protect key 0
through 7.
32
The address of the enciphered data-encrypting

key or the address of the enciphered
key-encrypting key was specified as zero.

ICT1035
synad message for non-VSAM
Explanation: An I/O error occurred while the key

generator utility program was processing the non-VSAM
data set defined by the SYSMKDS or SYSIN DD
statement.
Application Programmer Response: For the format
and explanation of the message, see the description of
the SYNADAF macro instruction in your data
administration macro instruction book. 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 (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 to process the remaining
control statements. Notify the security administrator.
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.
245
246
Chapter 12. ICU Messages

ICU010I

KEY HAS BEEN SET

key-encrypting keys, these statements are processed at
this time.
Source: Cryptographic Unit Support Program (CUSP)

ICU013I
KEY GENERATOR UTILITY jobname

STARTED AT time
Explanation: The key generator utility job, indicated

by jobname, began running at the time shown in the
message.


requester is in SMF record type 82.

continues.

continues.
ICU011I
ICU014I
CRYPTOGRAPHY KEY UPDATE

STARTED IN KEY GENERATOR
UTILITY job name
Explanation: The key generator utility program,

identified by jobname, has successfully updated the
cryptographic key data set (CKDS) to reflect a new,
changed, or deleted secondary key-encrypting key. This
message is issued only for the first update to the CKDS
for a secondary key-encrypting key although the job
may contain several update requests.
continues.
ICU012I
ERROR IN EXECUTING KEY

GENERATOR UTILITY jobname
Explanation: The key generator utility program,

identified by jobname, did not complete successfully. A
message identifying the nature of the problem is routed
to the data set defined by the SYSPRINT DD statement.
problem identified by the message appearing in the data
set defined by the SYSPRINT DD statement.
KEY GENERATOR UTILITY jobname

ENDED AT time
Explanation: The key generator utility job, indicated

by jobname, completed processing at the time shown in
the message.
requester is in SMF record type 82.
Application Programmer Response: Respond to any
error messages that were issued.
ICU020I

processing CKDS
Explanation: A physical I/O error occurred while the

key manager was attempting to read the cryptographic
key data set (CKDS).
of the accompanying VSAM physical I/O error message
in your VSAM macro instruction book. If the volume
CKDS to an alternate device. To change the volume or
device, stop the Cryptographic Unit Support (via IPL or
an operator STOP command) and restart it (via an
operator START command), specifying an alternate data
247
set name on the START command, if required. Rerun

the job.
ICU021I
VIOLATION ON RETKEY BY text
Explanation: text is
USER (userid) GROUP (groupid)
JOB (jobname) STEP (stepname)
An unauthorized program has issued the RETKEY SVC
requesting that a data-encrypting key enciphered under
a cross key be enciphered again under the host master
key. The RACF (Resource Access Control Facility) user
(userid) and group name (groupid) are given if they are
available. Otherwise, the job name (jobname) and step
name (stepname) are supplied. The REMKEY field in
SMF record type 82 contains the label of the cross key.
Note: The security administrator must determine if an
attempted security violation occurred. Follow the
security procedures established by your
installation.

and rerun the job.
ENTRY xxxxxxxx FAILS
AUTHENTICATION TEST
ICU025I
Explanation: The key manager has determined that

the secondary key-encrypting key, stored in the
cryptographic key data set (CKDS) entry indicated by
xxxxxxxx, has been changed since it was stored in the
CKDS. The key authentication procedure, using the test
pattern in the CKDS entry, detected the problem.
System Action: Processing stops for this request.
CKDS and MKDS that are mounted are the current
versions of the data sets. Rerun the job.

ICU026I
INTERNAL CKDS LOOKUP FAILED

AND DISABLED. ERROR CODE xx yy

ICU022I
xxx ABEND DURING [GENKEY |

RETKEY ] PROCESSING
Explanation: An error occurred during processing of

either the GENKEY or RETKEY function of the key
manager. In the message, xxx indicates the system
completion code.
Explanation: A failure occurred in the cryptographic

key table (CKT). xx and yy are the return and reason
codes for the error. An error was encountered when
ICUMKM18 attempted to locate a CKDS record from the
in-core cryptographic key table (CKT).
System Action: Access to the cryptographic key data
set (CKDS) resumes.
Operator Response: Respond according to the

specific return and reason codes.

problem identified by the system completion code.
Return
Code
Reason
Code
Description
CKT address not passed by

ICUMKM14.
CKT information passed from
ICUMKM14 was not valid.
Invalid CKT record key passed
by ICUMKM14.
Invalid record buffer passed by
ICUMKM14.
No entries in CKT to retrieve.
Invalid CKT RKP passed by
ICUMKM14.
To ensure that a dump is produced for this problem, run

the job again with a SYSABEND DD statement.
ICU024I

[FDBK code]

manager attempted to read the cryptographic key data
set (CKDS). In the message, rc is the return code that
identifies the error. If rc identifies a logical error, then
FDBK code indicates the specific logical error that has
occurred.
248
16
20
24
28
32
40
12
ICU030I
36
CKT record failed modification

detection check (MDC). CKT
has become corrupted.
Recovery environment could
not be established in
ICUMKM18.
UNABLE TO LOCATE name IN LPA
Explanation: The Cryptographic Unit Support

installation process invoked by the operator START
unable to locate the routine specified by name in a
search of the active link pack area queue and the link
pack area directory.
System Action: Cryptographic Unit Support
GENKEY or RETKEY installation exit routine (module
ICUMGR90 or ICUMGR95) is properly link edited into
SYS1.LPALIB. If the module has been replaced since
the Cryptographic Unit Support was installed, check the
linkage editor output from the most recent change. If it
has not been replaced, check the output of the install
process (SMP) to see that the module was properly
installed. Correct the problem and reissue the operator
START command or rerun the key generator utility
program.

ICU033I
LOAD FAILED FOR CRYPTOGRAPHY

INSTALLATION OPTIONS MODULE

unable to load the installation options module,
ICUOPTN2.
output of the install process (SMP) to verify that the
installation options module was properly installed in
SYS1.LINKLIB. Correct the problem and reissue the
utility program.
ICU034I
UNABLE TO ESTABLISH ESTAE CODE
xxx

The code from ESTAE processing is specified by xxx.
See OS/390 MVS Programming: Assembler Services
Reference for further information.

ICU031I

operator START command. For all other codes, contact
INVALID CRYPTOGRAPHY USER SVC

NUMBER SPECIFIED

command or the key generator utility program has
determined that the options module, ICUOPTN2,
contains an user SVC number that is not valid.
System Programmer Response: Update the
installation options module, ICUOPTN2, to reflect a valid
user SVC number in the range of 200 through 255. See
the Cryptographic Unit Support Program Directory for
information on how to modify the options module. When
the update is complete, reissue the operator START
command or rerun the key generator utility program.

the problem is corrected, run the key generator utility
program again.

249
ICU041I

ACTIVATED

successfully activated the Cryptographic Unit Support.
All functions of the facility are currently operational.
System Action: The Cryptographic Unit Support is
active.
ICU042I
START jobname TERMINATED
Explanation: The START command procedure,

identified by jobname, ended abnormally when
attempting to start the Cryptographic Unit Support. One
or more messages that explain the nature of the error
precede this message.
The Cryptographic Unit Support is not active.
ICU043I
UNABLE TO OPEN SYSCKDS
Explanation: The START command procedure used to

start the Cryptographic Unit Support was not able to
open the cryptographic key data set (CKDS) defined by
the SYSCKDS DD statement. This message is
accompanied by a VSAM error message that further
identifies the problem.

System Programmer Response: The return code
from ESTAE processing is specified by xxx. See
OS/390 MVS Programming: Assembler Services
ICU045I
CRYPTOGRAPHIC UNIT SUPPORT OR

KEY GENERATOR OR PROGRAMMED
CRYPTOGRAPHIC FACILITY ALREADY
IN PROGRESS
Explanation: An operator START command was

issued to start the Cryptographic Unit Support but a
cryptographic function is already in progress. The
cryptographic function could be the Cryptographic Unit
Support, the key generator for the Cryptographic Unit
Support, the Programmed Cryptographic Facility, or the
key generator for the Programmed Cryptographic
Facility.
System Action: The START command is ignored.
Operator Response: If a START command was
issued when the Cryptographic Unit Support is already
active or the START command procedure is already
running, an operator STOP command must be issued
before another START command can be accepted. If
the key generator utility program is currently running,
reissue the START command when the utility program
ends.

ICU047I
MODIFY CRYPTOGRAPHY COMMAND

REJECTED
System Programmer Response: Verify that a DD

statement has been included in the START procedure
for the CKDS with the ddname SYSCKDS. Check the
operator START command.
Explanation: An operator MODIFY command was

issued to change the configuration of cryptographic
units, but the configuration established by the MODIFY
command does not include any cryptographic units
available to the Cryptographic Unit Support.

System Action: MODIFY command processing ends.

System processing continues with the configuration that
existed before the MODIFY command was issued.

ICU044I
START jobname UNABLE TO

Explanation: The START procedure used to start the

Cryptographic Unit Support, identified by jobname, was
operator START command. For all other codes, notify
250
Operator Response: Ensure that the cryptographic

units specified in the command are physically online.
Reissue the MODIFY command.
ICU048I
MODIFY CRYPTOGRAPHY -- NEW

DEVICE CONFIGURATION IS
device-addr
Explanation: An operator MODIFY command has

successfully changed the configuration of cryptographic
units. In the message, device-addr identifies the
cryptographic unit now available to the Cryptographic

Unit Support.
ICU050I
USER-SUPPLIED KEY AND DEVICE

device-addr KEY DO NOT MATCH
Explanation: The host master key supplied as input to

the key generator does not have the same value as the
host master key installed in the cryptographic unit
identified by device-addr.
System Action: Processing continues if another
cryptographic unit is available. Otherwise, processing
ends.
Application Programmer Response: If a
cryptographic unit was not available to continue
processing, rerun the key generator utility program.
Security Administrator Response: Ensure that the
host master key installed in the cryptographic unit and
the value supplied in the PARM field of the EXEC
statement are the same.
ICU051I
KEY USED TO CREATE DATA SET

ddname AND DEVICE device-addr KEY
DO NOT MATCH
Explanation: The host master key installed in the

cryptographic unit, identified by device-addr, is not the
same value as the host master key whose variants were
used to encipher entries on the cryptographic key data
set (CKDS), identified in the message by ddname.
System Action: If another cryptographic unit is
available, processing continues. Otherwise, processing
ends.
CKDS, defined by the specified ddname, is the current
version of the data set. If a cryptographic unit was not
available to continue processing, rerun the key
generator utility program. Notify the security
administrator.
ICU052I
DATA SETS ddname-1 AND ddname-2

NOT CREATED WITH SAME MASTER
KEY
Explanation: The entries on the cryptographic key

data set (CKDS), identified in the message by
ddname-1, were not enciphered under the host master
key variants that are stored on the master key variant
data set (MKDS), identified in the message by
ddname-2.

CKDS and MKDS that are defined on the specified DD
statements are the current versions of the data sets.
Rerun the key generator utility program. Notify the
security administrator.
ICU053I
USER-SUPPLIED KEY AND KEY USED

TO CREATE ddname DO NOT MATCH
Explanation: The value supplied to the key generator

as the old host master key (for a CHGM request) is not
the value whose variants were used to encipher the
entries on the cryptographic key data set (CKDS),
identified in the message by ddname.
CKDS that is defined on the specified DD statement is
the current version of the data set. Ensure that the
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
the security administrator.
ICU054I
KEY VERIFICATION NOT EXECUTED.

INVALID INPUT.
Explanation: The code that indicates which of the key

verification tests is to be performed was not valid. The
code did not indicate any of the defined key verification
tests.
System Action: The program that requested key
verification (either the key generator utility, START
command processing, or MODIFY command
processing) ends.
When the problem has been corrected, issue the
START or MODIFY command again.
system programmer. When the problem has been
corrected, run the key generator utility again.
ICU055I
KEY VERIFICATION TEST FAILED DUE

TO I/O ERROR
Explanation: A cryptographic unit failed the key

verification test because of an I/O error. This error can
occur following the invocation of the cryptographic unit
access routine.
251

ends. A logrec data set record is written.
Operator Response: Contact hardware support. Notify
System Programmer Response: Run OLTEP
diagnostics for the problem device.
ICU060I
INTERNAL CKDS LOAD FAILURE 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
error was encountered when ICUMKM17 attempted to
load the CUSP cryptographic key data set (CKDS) into
an in-core tabular image of the file called the
cryptographic key table (CKT).
System Action: Processing associated with creating
the cryptographic key table (CKT) ends.
Operator Response: Respond according to the
specific return and reason codes.
Return
Code
Reason
Code
Description
4
12
20
4
12
Error closing the CUSP CKDS.

Error opening the CUSP CKDS.
Unable to get storage for CKT
(in subpool 231).
Error occurred during VSAM
GET on CUSP CKDS. If the
error is a VSAM physical error,
this message is preceded by
message ICU020I. If the error
is a VSAM logical error, this
message is preceded by
message ICU024I.
Recovery environment could
not be established in
ICUMKM17.
16
28
ICU061I

TERMINATED

INITIALIZATION OF CRYPTOGRAPHY
FACILITY AND OPEN SYSCKDS
SUCCESSFUL

successfully initialized the Cryptographic Unit Support
and has opened the cryptographic key data set defined
by the SYSCKDS DD statement. Key verification must
still be performed on the cryptographic unit(s) before all
functions of the Cryptographic Unit Support are
operational.
ICU070I
INTERNAL BUFFER BAD ON DEVICE

device-addr
Explanation: The internal buffer of the cryptographic

unit identified by device-addr is not functioning properly.
System Action: If at least one other cryptographic unit
is available, processing continues. Otherwise,
processing ends.
ICU071I
Explanation: An operator STOP command has

successfully deactivated the Cryptographic Unit Support.
All current sessions and all new sessions will fail.
252
ICU062I
I/O PROCESSING FAILED ON DEVICE

device-addr
Explanation: The cryptographic unit, identified by

device-addr, was unable to process input/output data
because of a hardware error.
ends.
ICU072I
NO DEVICE PATH TO DEVICE

device-addr
Explanation: There is no physical I/O path to the

cryptographic unit identified by device-addr.
ends.
cryptographic unit is physically online and logically
online (by means of a VARY command) and that the
cryptographic units physical key is locked. Then issue a
MODIFY command to add this unit to the configuration
of cryptographic units, or issue a START command after
the Cryptographic Unit Support is stopped.


and security administrator.
System Programmer Response: Ensure that all

access to any cryptographic unit is controlled by the
Cryptographic Unit Support to benefit from the
authorization checks it performs to ensure the security
of the cryptographic unit.
ICU073I
INTERNAL LINE BUFFER TEST

UNABLE TO GETMAIN STORAGE
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

sufficient storage is available in subpool 252. Reissue
the START command or rerun the key generator utility
program.
DEVICE device-addr UNAVAILABLE OFFLINE AND IN USE BY A SYSTEM

COMPONENT

attempted to allocate the cryptographic unit identified by
device-addr, but the unit was designated as not
allocatable (UCBNALOC=ON).

ends.
ICU074I

and security administrator.
UNABLE TO DYNAMICALLY
ALLOCATE DEVICE device-addr CODE
xxxx
Explanation: Dynamic allocation failed with code xxxx

while attempting to allocate or deallocate the
cryptographic unit identified by device-addr.
ends.
System Programmer Response: Ensure that all

access to any cryptographic unit is controlled by the
Cryptographic Unit Support to benefit from the
authorization checks it performs to ensure the security
of the cryptographic unit.

Programming: Authorized Assembler Services Guide for
the explanation of the error code. Correct the problem
and reissue the START command or rerun the key
generator utility.
ICU077I
DEVICE device-addr PREVIOUSLY

ALLOCATED TO ANOTHER JOB OR
TASK

attempted to allocate the cryptographic unit identified by
device-addr, but the unit is allocated to another job or
task in the system.
ends.
ICU080I
I/O INITIALIZATION UNABLE TO

Explanation: The Cryptographic Unit Support I/O

initialization routine, invoked by the operator START
command or the key generator utility program, was
unable to establish a recovery environment. The return
code from ESTAE processing is specified by xxx. See
OS/390 MVS Programming: Assembler Services
System Action: The Cryptographic Unit Support I/O
initialization or key generator utility ends.
utility program. For all other codes, contact your system
programmer. When the problem is corrected, reissue
the START command or rerun the key generator.
Application Programmer Response: If the code is 4,
rerun the key generator utility program. For all other
codes, contact your system programmer. When the
problem is corrected, reissue the START command or
rerun the key generator.
253

ICU081I
I/O INITIALIZATION UNABLE TO

GETMAIN SP227 STORAGE
Explanation: The Cryptographic Unit Support I/O

initialization routine, invoked by the operator START
command or the key generator utility program, was
unable to obtain sufficient storage from subpool 227.
System Action: START command or key generator
utility program processing ends.

utility processing ends.
When the problem is corrected, issue the START
command again.
system programmer. When the problem is corrected,
run the key generator utility program again.
sufficient storage is available in subpool 230.
ICU085I
NO CRYPTOGRAPHIC UNITS
AVAILABLE

sufficient storage is available in subpool 227. Reissue
the START command or rerun the key generator utility
program.
Explanation: All cryptographic units failed with one of

the following errors:

v Sufficient storage to perform the internal buffer test

could not be obtained.
v The cryptographic unit could not be opened.
ICU082I
One or more messages that explain the error precede

this message.
NO 3848 CRYPTOGRAPHIC UNITS

SYSGENED INTO ELIGIBLE DEVICE
TABLE
Explanation: No entries with UNITNAME=3848 were

found in the eligible device table. An entry with
UNITNAME=3848 must exist for each cryptographic unit
defined in the configuration, and at least one such entry
must exist for successful initialization of the
Cryptographic Unit Support.
utility processing ends.
System Programmer Response: Ensure that at least
one cryptographic unit is defined during system
generation. Reissue the START command or rerun the
ICU084I
IEFAB4UV UNABLE TO GETMAIN

SP230 STORAGE
Explanation: The allocation unit verification routine

(IEFAB4UV) that is used by the I/O initialization routine,
invoked by the operator START command or the key
generator utility program, was unable to obtain sufficient
storage from subpool 230.
254
v Key verification test failed

v Internal buffer test failed

processing ends.
ICU1001
WEAK KEY SPECIFIED
Explanation: A weak clear key value was specified on

a LOCAL, LOCAL-GROUP, REMOTE, or CROSS
control statement for the key generator utility program.
The control statement containing the weak key
statements.
clear key value on the control statement or remove the
KEY parameter completely to let the key generator
utility program generate a clear key value. See OS/390
DFSMS: Using Data Sets for a description of weak key
values. Rerun the utility program, specifying the CHGK
function on the EXEC statement and providing the
corrected control statement as input.
ICU1002
INVALID VERB
Explanation: A verb specified on a control statement

for the key generator utility program was not valid. The
control statement containing the error precedes this
message.
statements.
Application Programmer Response: Correct the verb
on the control statement. The valid verbs are LOCAL,
LOCAL-GROUP, REMOTE, CROSS, EXTRA-LOCAL,
EXTRA-REMOTE, EXTRA-CROSS, REASGN, and
INSTDAT. The verb must be preceded and followed by
a blank. Rerun the key generator utility program,
specifying the CHGK function on the EXEC statement
and providing the corrected control statement as input.
ICU1005
INVALID OR REDUNDANT KEYWORD

SPECIFIED
Explanation: An incorrect or redundant keyword

parameter was specified on a LOCAL, LOCAL-GROUP,
REMOTE, CROSS, or REASGN control statement for
the key generator utility program. The control statement
containing the error precedes this message.
statements.
keyword parameter or remove the redundant keyword
parameter on the control statement. Rerun the key
control statement.
ICU1003
ICU1006
SYNTAX ERROR IN KEY
Explanation: An incorrect clear key value was

specified on a LOCAL, LOCAL-GROUP, REMOTE, or
CROSS control statement for the key generator utility
program. The control statement containing the error
statements.
clear key value on the control statement. A valid value
consists of 16 hexadecimal digits. (Valid hexadecimal
digits are 0 through 9 and A through F.) Rerun the key
ICU1004
SYNTAX ERROR IN LABEL
Explanation: An incorrect label was specified on a

LOCAL, LOCAL-GROUP, REMOTE, CROSS, or
REASGN control statement for the key generator utility
program. The control statement containing the error
statements.
label on the control statement. A valid label consists of 1
to 8 alphameric characters. Valid alphameric characters
are A through Z and 0 through 9. Rerun the key
INVALID VALUE SPECIFIED ON EXTRA

STATEMENT
Explanation: One of the following conditions was

encountered on an EXTRA-LOCAL, EXTRA-CROSS, or
EXTRA-REMOTE control statement for the key
generator utility program:
v The first through fourth characters of the value for
label-base were not alphameric.
v The fifth through eighth characters of the value for
label-base were not numeric.
v An incorrect number of additional keys was
requested.
The control statement containing the error precedes this
message.
statements.
alphameric portion of the label-base is incorrect, supply
a valid value on the control statement. A valid value
consists of 4 alphameric characters. Valid alphameric
characters are A through Z and 0 through 9.
Otherwise, correct the numerical portion of the
label-base and/or the number of additional keys
requested on the control statement. The sum of these
two values must not exceed 9999.
Rerun the key generator utility program, specifying the
the corrected control statement.

255
ICU1007
STATEMENT REJECTED BY
INSTALLATION EXIT
Explanation: A control statement was rejected by the

key generator utility program installation exit routine.
The rejected control statement precedes this message.
statements.
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
corrected control statement.
ICU1008
REQUIRED PARAMETER
INFORMATION MISSING
Explanation: The key generator utility program found

that the value for the SETM, CHGM, or SEED
parameter on the EXEC statement is missing.
missing value in the PARM field of the EXEC statement
ICU1009
DUPLICATE LABEL; KEY NOT ADDED

utility program to add a label and its associated
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
statements.
Application Programmer Response: Assign a unique
label to the key and rerun the key generator utility
ICU1010
LABEL NOT FOUND; NOT

PROCESSED

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
256
label was not defined in the CKDS. The rejected control

statement precedes this message.
statements.
correct label and rerun the key generator utility program,
specifying the CHGK function on the EXEC statement.
ICU1011
synad I/O error message from VSAM
Explanation: A physical I/O error occurred when the

key generator utility program attempted to access the
SYSCKDS or SYSNCKDS data set.
of the accompanying VSAM physical I/O error message
in your VSAM macro instruction book. If the volume
CKDS to an alternate device.
Rerun the key generator utility program as follows. If the
master key was not set (message ICU010I was not
statements.
ICU1012
PROCESSING TERMINATES DUE TO

INSTALLATION EXIT REQUEST
Explanation: The key generator utility program stops

processing at the request of the installation exit routine.
message.
procedures.
ICU1013
PROCESSING ENDED DUE TO ESTAE

OR STAE RETURN CODE xxx

attempted to use the ESTAE system service, but the
error code xxx was returned.
No control statements are processed.
the problem is corrected, run the key generator utility
program again.
ICU1014
SYSIN DATA SET EMPTY; NO

PROCESSING OCCURRED
Explanation: The CHGK function of the key generator

utility program was requested but no control statements
could be found.
Application Programmer Response: Add the desired
control statements to the SYSIN data set and rerun the
Correct the problem and rerun the key generator utility

(message ICU010I was not issued), rerun the entire job.
ICU1017

unable to run because the Cryptographic Unit Support
was active.
Application Programmer Response: When the
Cryptographic Unit Support is stopped and there are no
cryptographic sessions or jobs running in the system,
rerun the key generator utility program to change the
host master key. Restart the Cryptographic Unit Support
by entering an operator START command.
ICU1018

ICU1015
If the data set is a VSAM data set (SYSCKDS or

SYSNCKDS), the VSAM return code rc is included to
help identify the error. For the explanation of the return
code, see the description of the VSAM macro. This
message is accompanied by a VSAM error message
that further identifies the problem.
occurred while trying to open a data set, check the JCL.
Be sure the required DD statements were included, that
they have the correct ddnames, and that they define the
correct data sets. The following ddnames are valid:
SYSCKDS, SYSNCKDS, SYSIN, and SYSMKDS.
Note: An open failure can also occur if the SYSCKDS
or SYSNCKDS data set was defined without the
proper parameters on the access method
services DEFINE CLUSTER command.
KEY GENERATION NOT ALLOWED text
text is
TOD CLOCK ERROR
SEED NOT SUPPLIED
UNABLE TO [OPEN | CLOSE ] ddname

[CODE rc]

unable to open or close the data set defined by the DD
statement identified by ddname.
CRYPTOGRAPHY STARTED; INVALID

KEY GENERATOR REQUEST
Explanation: An error was encountered when the key

generator utility program attempted to read the
time-of-day (TOD) clock, the TOD clock was inoperative,
or a seed value was not supplied on the EXEC
statement. Processing continues; however, no keys can
be generated.
continues.
involves the TOD clock, contact your service
representative. If a seed value was not supplied, ignore
this message unless message ICU1025 also appears. If
message ICU1025 appears, see the description of
message ICU1025.
ICU1019

KEY HAS BEEN SET

257
key-encrypting keys, they are processed at this time.

continues.
ICU1020
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.
keyword parameter in the PARM field. The valid
keyword parameters are SETM, CHGM, CHGK, and
SEED. Rerun the key generator utility program.
ICU1021
WEAK SYSTEM MASTER KEY

SPECIFIED
Explanation: A weak value for the new host master

key was specified in the PARM field of the EXEC
host master key value and its complement in the PARM
field of the EXEC statement. See OS/390 DFSMS:
Using Data Sets for a description of weak key values.
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
was not set (the contents of the PARM field precede
this message).
ICU1024
REQUIRED OPERAND[S] MISSING;

STATEMENT IGNORED
Explanation: While scanning a SYSIN control

statement, the key generator utility program could not
find one or more required parameters. LOCAL,
LOCAL-GROUP, REMOTE, and CROSS control
statements require a label. EXTRA-LOCAL,
EXTRA-REMOTE, and EXTRA-CROSS control
statements require a number and a label-base. The
REASGN control statement requires an existing label
and a new label. The control statement containing the
error precedes this message.
statements.
control statement. Rerun the key generator utility

ICU1025
ICU1023

attempted to generate a key for a control statement and
either a problem occurred with the time-of-day (TOD)
clock or a valid seed value was not supplied on the
EXEC statement. Message ICU1018, which identifies
the specific problem, and the control statement being
processed when the problem occurred, precede this
message.
INVALID RETURN CODE FROM

TERMINATES
Explanation: A return code provided by the key

generator utility program installation exit was not valid. If
the problem occurred while the key generator utility
program was processing a change to the host master
key, the contents of the PARM field of the EXEC
statement precede this message. If the problem
occurred while the utility program was processing a
SYSIN control statement, the control statement
258
REQUIRED INPUTS FOR KEY

GENERATION NOT AVAILABLE

statements.
v If message ICU1018 stated that there is a problem
involving the TOD clock, contact your service
representative.
v If message ICU1018 stated that a seed value was
supplied, add a seed value to the EXEC statement.
Rerun the key generator utility program specifying the

the control statement that was being processed when
the problem occurred.
ICU1030
INVALID SMF DATA LENGTH FROM

TERMINATES
Explanation: The key generator installation exit

routine returned the SMF buffer with a value greater
than 64 in the length field.
System Action: The key generator utility program
does not include the installation-defined data in the SMF
record. The program writes the SMF record to the SMF
data set and stops processing.
with the corrected exit routine. See OS/390 DFSMS:
Using Data Sets Rerun the key generator utility program
remaining control statements. Notify the security
administrator.
error return code from the EMK macro. The values of xx

and their explanations are as follows:
Code
Explanation
The Cryptographic Unit Support has not been

initialized.
An incorrect operation was requested; the

macro was not EMK.
12

established or an unrecoverable I/O error
occurred.
32
The address of the clear key-encrypting key or

the address of the enciphered key-encrypting
key was specified as zero.


ICU1033

of a CIPHER macro instruction issued by the key
error return code from the macro. The values of xx and
their explanations are as follows:
ICU1031
INVALID DELIMITER IN PARM FIELD
Explanation: While scanning the PARM field of the

EXEC statement, the key generator utility program did
not find an expected delimiter or encountered an
unexpected delimiter.
Code
Explanation

initialized. The data could not be enciphered or
deciphered.
An incorrect operation was requested; the

macro was not CIPHER.
12

occurred.
16
The length of the data to be enciphered or

deciphered was specified as zero or as a
negative number, or exceeded the maximum
specified in the installation options module.
20
The BRANCH=YES parameter was specified,

but the program issuing the macro is not
running in supervisor state.

Application Programmer Response: The valid
delimiters are comma, right and left parentheses, and
blank. Correct the error and rerun the key generator
utility program.
ICU1032
CRYPTOGRAPHY EMK FUNCTION

FAILED - CODE xx

of an EMK macro instruction issued by the key
CRYPTOGRAPHY CIPHER FUNCTION

FAILED - CODE xx
259
32
The address of the clear data or the

enciphered data was specified as zero.
40
A retry of the CIPHER request was required

but could not be performed because the input
area and output area overlapped.

ICU1034
CRYPTOGRAPHY KEY TRANSLATION

FAILED - CODE xx
Explanation: An error has occurred during key

translation processing. The translation was requested by
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:

ICU1035
synad message for non-VSAM
Explanation: An I/O error occurred while the key

generator utility program was processing the non-VSAM
data set defined by the SYSMKDS or SYSIN DD
statement. The format and explanation of the message
is in the description of the SYNADAF macro in your
VSAM macro instruction book.
Application Programmer Response: See OS/390
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
master key was not set (message ICU010I was not
statements.
Code
Explanation

initialized.
The operation requested was not valid.
ICU1036
12

occurred.
24
Bad parity was detected in the local, remote, or

cross key.
28
The program requesting the key translation

function is not APF-authorized or in supervisor
state or running under storage protect key 0
through 7.
32
The address of the enciphered data-encrypting

key or the address of the enciphered
key-encrypting key was specified as zero.

260
CKDS ENTRY SUCCESSFULLY

DELETED

successfully deleted an entry from the cryptographic key
data set (CKDS). The control statement that was
processed precedes this message.
ICU1038
NO CRYPTOGRAPHIC UNITS ARE

AVAILABLE WITH A VERIFIED KEY
Explanation: The key generator has determined that

either key verification has not completed successfully for
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
cryptographic unit has been changed.
security administrator. Determine if message ICU050I,
ICU051I, ICU052I, ICU053I, ICU054I, or ICU055I was
issued; if so, refer to that message for the appropriate

response and rerun the job. If not, then the
cryptographic unit was tampered with while the key
generator was running. Ensure that the master key in
the cryptographic unit is properly installed. Then rerun
the key generator as follows. If the SETM or CHGM
function was requested and the host master key was
not set (message ICU010I 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 to
ICU1041
CONTINUATION CARD EXPECTED AND

NOT FOUND
Explanation: A LOCAL-GROUP or CROSS control

statement was expected to continue (that is, it ended
with a comma) but did not. The control statement
containing the error precedes this message.
statements.
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
providing the corrected control statement.
ICU1039
LABEL IS A RESERVED KEY WORD
Explanation: The label supplied for a cryptographic

key data set (CKDS) entry is not valid. The following
key words cannot be used for labels: LOCAL, REMOTE,
CROSS, REASGN, ADD, UPDATE, DELETE, KEY,
IKEY, KEYLOC, IKEYLOC, KEYREM, IKEYREM. The
message.
statements.
label on the control statement. Rerun the key generator
utility program, specifying the CHGK function on the
EXEC statement providing the corrected control
statement.
ICU1040
LOCAL-GROUP STATEMENT
CONTAINS TOO MANY LABELS
Explanation: The maximum number of labels that can

be specified on a LOCAL-GROUP control statement is
64. The control statement containing the error precedes
this message.
statements.
Application Programmer Response: Rerun the key
on the EXEC statement. Provide more than one
LOCAL-GROUP control statement as necessary so that
each does not specify more than 64 labels.
ICU1042
INVALID CHANGE REQUESTED
Explanation: A control statement requests a change

to an entry in the cryptographic key data set (CKDS);
however, the change conflicts with the existing entry.
For a REASGN control statement, if the new label
already exists on the CKDS, it must contain the same
type of key-encrypting key as the existing label entry.
For a LOCAL, REMOTE, or CROSS control statement,
the updated or deleted entry must have the same type
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
REMOTE control statement; and to update or delete
cross keys, use a CROSS control statement. The
message.
statements.
control statement in error. Rerun the key generator
utility program, specifying the CHGK function on the
EXEC statement and providing the corrected control
statement.
ICU1043
CKDS RECORD WITH VERIFICATION

PATTERNS NOT FOUND
Explanation: The key generator has searched the

cryptographic key data set (CKDS) and cannot locate
the records that contain the verification patterns. (These
verification patterns are derived when the CKDS is
created and are used in the key verification procedure.)
The records are expected to have labels of
X'DACBEDFCEDCCFEE1' and
X'DACBEDFCEDCCFEE2'.
261
security administrator. The CKDS is probably not

usable. If a back-up copy of the CKDS is available, use
it; otherwise, the CKDS must be recreated.
ICU1044
THE ATTACH OF TASK ICUMKG04

FAILED WITH CODE xx

generator issued the ATTACH macro instruction for
ICUMKG04. The module could not be found in
SYS1.LINKLIB. This module is invoked when the key
generator has determined that the cryptographic unit
has been tampered with. ICUMKG04 will try to locate
another cryptographic unit that is available to the
Cryptographic Unit Support.
security administrator. Ensure that the module
ICUMKG04 is properly loaded in SYS1.LINKLIB and
rerun the key generator utility.
v Define a larger data set for use as the new target

CKDS and copy the contents of the original target
CKDS to the larger data set.
Then, use this listing to determine which control
statements were processed successfully and rerun the
key generator utility program using the CHGK option to
For information on defining and reorganizing the CKDS,
see DFSMS/MVS Access Method Services for VSAM
The commands needed to define, reorganize, and copy
the data set are described in DFSMS/MVS Access
Method Services for VSAM and OS/390 DFSMS Macro
Instructions for Data Sets.
ICU1046
INVALID SYNTAX FOR {OLD MASTER

KEY | NEW MASTER KEY | SEED}
Explanation: An incorrect value for the SETM, CHGM,

or SEED parameter was found in the PARM field of the
EXEC statement for the key generator utility program.
ICU1045
INSUFFICIENT SPACE ON ddname
Explanation: The key generator utility program could

not complete a request to build or update the data set
defined in the message by ddname because there is
insufficient space on the target data set.
message.
Application Programmer Response: Notify your
system programmer.
System Programmer Response: If the SETM or
CHGM function was requested and the host system
master key was not set (the contents of the PARM field
precede this message), define a larger target data set
for the CKDS and rerun the entire job. Otherwise, the
key generator utility program failed while processing a
SYSIN control statement and one of the following must
be done.
v Reorganize the target CKDS to force more efficient
space utilization.
262

value in the PARM field of the EXEC statement. A valid
value consists of 16 hexadecimal digits. (Valid
hexadecimal digits are 0 through 9 and A through F.)
ICU1047
UNEXPECTED VSAM ERROR ON

ddname CODE rc [FDBK code]

generator utility program attempted to read from or write
to the data set identified by ddname in the message. In
the message, rc is the return code that identifies the
error. If rc identifies a logical error, then FDBK code
indicates the specific logical error that has occurred.
and rerun the utility program as follows. If the SETM or
was not set (message ICU010I 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
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
263
264
Chapter 13. IDA Messages

IDA001
INVALID POSITIONAL PARAMETER,

prm - IGNORED
Explanation: The specified positional parameter is not

valid.
prm
Indicates the specified positional parameter.
System Action: The system ignores the positional

parameter. The system expands the macro normally.
Application Programmer Response: This is probably
an error in the calling program. Correct the positional
parameter. Submit the job again.
System Programmer Response: If the error recurs
and the program is not in error, search problem
program listing, the assembly listing, and the source
input for the job.
Source: DFSMSdfp
Detecting Module: IDAMDVRP
keyword
The keyword.
System Action: The system does not expand the
macro.
an error in the calling program. Correct the erroneous
value. Submit the job again.
input associated with the job.
Source: DFSMSdfp
IDA004
keyword KEYWORD NOT VALID FOR

EXECUTE FORM - IGNORED
Explanation: The indicated keyword is not valid for

the execute form of the macro.
IDA002
keyword KEYWORD REQUIRED - NOT

SPECIFIED
Explanation: The caller omitted a required keyword.

keyword
The keyword.
macro.
an error in the calling program. Provide the required
keyword and value. Submit the job again.
input for the job.
Source: DFSMSdfp
IDA003
INVALID VALUE, value, SPECIFIED FOR

keyword KEYWORD
Explanation: The value specified for the indicated

keyword was incorrect.
keyword
The keyword.
System Action: The system ignores the keyword. The
system expands the macro normally.
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
execute form.
input associated with the job.
Source: DFSMSdfp
IDA005
Explanation: The specified sublist item is not valid or

is duplicated for the keyword.
keyword
The keyword.
value
INVALID OR DUPLICATE SUBLIST

ITEM FOR keyword KEYWORD, xxx
xxx
The name of the sublist item.
265

macro.
Source: DFSMSdfp

an error in the calling program. Correct the sublist item.
Resubmit the job.
IDA008
Explanation: The sublist items specified for the

keyword are incompatible.

input for the job.
yyy
Source: DFSMSdfp
keyword
IDA006
keyword VALUE, value, NOT VALID FOR

LIST FORM
INCOMPATIBLE SUBLIST ITEMS. xxx

AND yyy, FOR keyword KEYWORD
xxx
The specified sublist names.
The keyword.
macro.
Explanation: The specified value for the keyword is

not valid for the list form of the macro.
Application Programmer Response: Remove one of

the incompatible sublist items. Run the job again.

input for the job.
keyword
The keyword.
value

macro.
an error in the calling program. Correct the erroneous
value. Submit the job again.
input for the job.
Source: DFSMSdfp
IDA007
LOGIC ERROR IN MACRO mac
Explanation: The system detected a logic error in the

macro.
mac
The name of the macro.

macro.
Application Programmer Response: Determine
where the error occurs in the macro. Correct the error.
Run the job again.
input for the job.
266
Source: DFSMSdfp
IDA009
nnn CONTROL BLOCK KEYWORDS

SPECIFIED - ONLY ONE ALLOWED
Explanation: The caller specified more than one

control block for a TESTCB macro. This is an error.
nnn
The number of control block keywords

specified.

macro.
Application Programmer Response: Remove all but
one of the control block keywords. Run the job again.
input for the job.
Source: DFSMSdfp
IDA010
EXIT ADDRESS REQUIRED FOR

keyword KEYWORD - NOT SPECIFIED
Explanation: An exit address required for the keyword

was not specified.
keyword
The keyword.

macro.
Source: DFSMSdfp

required exit address. Run the job again.
IDA019

input for the job.
Explanation: The indicated keywords cannot be

specified together.
Source: DFSMSdfp
IDA011
keyword IS NOT A VALID xxx

KEYWORD - IGNORED
Explanation: The specified keyword is not valid for the

control block.
keyword
The keyword.
xxx
The control block.
System Action: The system ignores the incorrect

keyword. The system expands the macro normally.
Application Programmer Response: Remove the
incorrect keyword. Run the job again.
input for the job.
Source: DFSMSdfp
KEYWORDS keyword1 AND keywd2

ARE INCOMPATIBLE
keyword1
keyword2
The specified keywords.
macro.
error by specifying compatible keywords. Run the job
again.
input for the job.
Source: DFSMSdfp
Detecting Module: IDA0192V
IDA020
VTAM SUBLIST ITEM, xxx, SPECIFIED

FOR keyword KEYWORD WITHOUT
SPECIFYING AM=VTAM
Explanation: The VTAM sublist item specified for the

keyword is not valid because AM=VTAM was not
specified.
IDA018
VTAM KEYWORD, keyword, SPECIFIED

WITHOUT SPECIFYING AM=VTAM
Explanation: The specified VTAM keyword is not valid

because AM=VTAM was not specified.
keyword
The keyword.
macro.
Application Programmer Response: Either remove
the incorrect keyword or specify AM=VTAM. Run the job
again.
input for the job.
xxx
The specified sublist item.
keyword
The keyword.
macro.
Application Programmer Response: Specify
AM=VTAM. Run the job again.
input for the job.
Source: DFSMSdfp
Detecting Module: IDA0200T
267
keyword1 AND keywd2 KEYWORDS

MUST BE SPECIFIED TOGETHER BUT
ONE IS MISSING
IDA021
Explanation: The keywords specified in the message

text form a pair. One cannot be specified without the
other.
keyword1
keyword2
The keywords.
macro.
missing keyword or remove the one specified. Run the
job again.
input for the job.
Source: DFSMSdfp
keyword
The keyword.
macro.
error by specifying a non-VSAM keyword. Run the job
again.
input for the job.
Source: DFSMSdfp
www, xxx, yyy CONFLICTING

SUBPARAMETERS IN keyword
KEYWORD, www ASSUMED
IDA025
Explanation: More than one subparameter was

specified for the indicated keyword. This is an error.
www
xxx
IDA022
CONFLICTING SUBLIST ITEMS WERE

SPECIFIED FOR keyword KEYWORD
yyy
The specified subparameters.
Explanation: The keyword was specified with

conflicting sublist items.
keyword
System Action: The system expands the macro using

www as the default.
keyword
The keyword.
macro.
sublist item or items that are in conflict. Run the job
again.
input for the job.
Source: DFSMSdfp
IDA024
keyword, A VSAM KEYWORD

SPECIFIED FOR A NON-VSAM
CONTROL BLOCK
Explanation: The specified keyword is a VSAM

keyword, but it is being specified for a non-VSAM
control block.
268
The keyword.
Application Programmer Response: Specify one of

the conflicting subparameters for the keyword. Run the
job again.
input for the job.
Source: DFSMSdfp
IDA026
keyword1 CONFLICTS WITH keywd2.

keywd1 IGNORED.
Explanation: The meaning of the first keyword

specified either conflicts with or repeats the meaning of
the second keyword specified.
keyword1
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
269
270
Chapter 14. IDC Messages

IDC0001I
Explanation: The system issues this message upon

completion of any functional command. If an error has
occurred, the condition code is not 0. If an error has
occurred, it will be indicated by error messages that
precede the completion message.
cde
The highest condition code of the completed

function.
System Action: The system sets the last condition

code (LASTCC) to cde. The system sets the maximum
condition code (MAXCC) if cde is greater than the
current MAXCC value.
Source: DFSMSdfp
Detecting Module: IDCAL01, IDCBI01, IDCCC01,
IDCDE01, IDCDL01, IDCLC01, IDCLR01, IDCMP01,
IDCPM01, IDCPR01, IDCRC01, IDCRM01, IDCRP01,
IDCRS01, IDCVY01, IDCXP01
IDC0002I
IDCAMS PROCESSING COMPLETE.

MAXIMUM CONDITION CODE WAS cde
Explanation: The system issues this message at the

completion of the job. If an error occurred, the condition
code is not 0.
cde
The highest condition code of the completed

job.
System Action: The system places the highest

condition code (MAXCC) set during the step in register
15.
Source: DFSMSdfp
IDC0005I
NUMBER OF RECORDS PROCESSED

WAS nnn
Explanation: The system issues this message to

indicate the number of records processed by the job.
nnn
to the output data set. If the Access Method

Services Cryptographic Option Program
Product is installed and the ENCIPHER
parameter of the REPRO command was
used, then the number includes one or more
header records.
FUNCTION COMPLETED, HIGHEST

CONDITION CODE WAS cde
Depending on the command, nnn indicates the

following:

Source: DFSMSdfp
Detecting Module: IDCPR01
IDC0014I
LASTCC=cde
Explanation: The system issues this message when a

nonzero condition code is returned by any functional
command upon its completion. If the condition code is
greater than 0, error messages precede this message.
cde
The condition code, as follows:

4
Attention message. The system will

complete processing.
Serious error. The system completed

processing.
12
Abnormal error. The system

abnormally ends the command.
System Action: The system either completes or

abnormally ends processing depending on the condition
code.
Application Programmer Response: Determine the
cause of the error. Correct the error. Run the job again.
Source: DFSMSdfp
IDCDE01, IDCDL01, IDCLC01, IDCMP01, IDCRM01,
IDCRS05, IDCVY01, IDCXP01
IDC0018I
MAXIMUM NUMBER OF CVOL

ENTRIES EXCEEDED
Explanation: Only 1455 CVOL entries may be

referenced.
System Action: JOB COMPLETES
User Response: None
v For the catalog reload function of the

REPRO command, the number of records
read from the input data set.
v For EXPORT and all other REPRO and

PRINT commands, the number of records
written to the output data set. If input
records were selectively processed, the
number includes only those actually written
Source: IDCAMS
Detecting Module: IDCSA02
271
IDC0038I
IDC0038I COMPRESSION INTERFACE

USED, DATA TRANSFER COMPLETE.
Explanation: This message may be issued after doing

a REPRO of a compressed data set to another
compressed data set and no decompress conditions
were met.
Source: IDCAMS
Detecting Module: IDCRP01
IDC0061I
CARTRIDGE csn EJECTED
Explanation: Either a scratch cartridge or an old or

defective data cartridge was ejected from the Mass
Storage Facility.
csn
The cartridge.
System Action: The command continues processing.

Source: DFSMSdfp
IDC0063I
CARTRIDGE LABELS AND INVENTORY

RECORD RESTORED
Explanation: The system restored the cartridge labels

and Inventory data set to original status after an error
had been encountered while relabeling a Mass Storage
Volume.
Application Programmer Response: Take the
following action for the command that failed:
v If a rename operation failed for ADDV and if the
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
rename operation.
If the ADDV, MODIFYV, or STOREV commands are
run to recover from a rename failure, specify a DD
statement for the volume with deferred mounting.
The values specified for the VOLUME and
NEWSERIAL parameters depend upon how the
volume record is recorded in the Inventory data set. If
the cartridge labels have been updated, the volume
record will be identified by the new volume serial
number, as follows:
For the VOLUME parameter, specify the volume
serial number as recorded in the cartridge labels
and the volume record.
For the NEWSERIAL parameter, specify the
desired volume serial number. Note that the
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.
272
If ADDV, MODIFYV, or STOREV abnormally ends

without indicating the status of the rename operation,
run LISTMSVI to determine if the volume is flagged
for recovery purposes. If the 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 a
rename operation failed for the preceding volume and
that the serial number is recorded in the volume label
of the volume.
v If a rename operation failed for MODIFYV, recover
from a MODIFYV rename failure by:
If the volume is inactive and has no volume serial
mismatch condition, run ADDV to activate the
volume.
If the volume is inactive and has a volume serial
mismatch condition, run ADDV to activate the
volume and to complete the rename operation.
If the volume is active and has a mismatch
condition, run MODIFYV to complete or retry the
rename operation.
If the volume is active and a duplicate volume
serial number is desired, run STOREV to
complete or retry the rename operation.
the job log for more information. Search problem
exists, contact the IBM Support Center. Provide the job
control language (JCL), the SYSOUT output, and all
output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01
IDC0064I
text UPDATED IN CARTRIDGE LABELS

AND INVENTORY RECORD
Explanation: text is one of the following:

SERIAL
OWNER
SERIAL, OWNER
The volume serial number, the owner name, or both
was updated in the label of the data cartridges assigned
to the Mass Storage Volume and in the volume record
in the Inventory data set. However, the data may not yet
be updated in the software volume label.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01, IDCSR01
IDC0068I
nnn BACKUP COPIES EXIST BEYOND

MAXIMUM BACKUP
Explanation: The number of backup copies exceeds

the backup number specified through the use of the
CREATEV or MODIFYV command.
nnn
The number of backup copies that exceed the

maximum.
Operator Response: Remove the ejected cartridge or

cartridges from the cartridge access station of the Mass
Storage Facility.
Source: DFSMSdfp
IDC0085I
CARTRIDGES csn [csn] EJECTED
Explanation: The cartridges assigned to a Mass

Storage Volume were ejected from the Mass Storage
Facility.
Application Programmer Response: The excess

backup copies are scratched by:
msn
v The next COPYV command processed to create a

new backup copy. The oldest backup copies will be
scratched.
v Specify the SCRATCHV command for each backup

copy to be scratched.
Detecting Module: IDCEV01, IDCCO01, IDCSR01
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCMV01
IDC0073I
VOLUME ATTRIBUTES CHANGED TO

AGREE WITH GROUP grpname
Explanation: The attributes of a general use volume

were changed to match the attributes defined at the
group level for all general use volumes belonging to the
group. If the caller did not explicitly request the attribute
change, the attributes are changed implicitly because:
The cartridge serial numbers of the sequence

one and sequence two cartridges.
Source: DFSMSdfp
IDC0086I
text UPDATED IN VOLUME LABEL

SERIAL
OWNER
SERIAL, OWNER
The volume serial number, the owner name, or both
was changed in the volume label.
v The volume is being assigned to a different group
Source: DFSMSdfp
v A volume that does not belong to a group is being

assigned to a group
v The group level attributes were changed while a

general use volume was inactive and is now being
activated
IDC0088I

Source: DFSMSdfp
IDC0083E
csn [csn] EJECTED; VOL volser jobname sss
Explanation: One or both cartridges assigned to the

Mass Storage Volume were ejected from the Mass
Storage Facility.
CARTRIDGES csn [csn] SCRATCHED

FOR COPY yyddd
Explanation: The cartridges assigned to the copy

volume were successfully scratched. If only one
cartridge was in the Mass Storage Facility (MSF), the
single cartridge serial number identifies the sequence
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
sequence one and sequence two cartridges are listed.
csn
The cartridge serial number.
yyddd
The date on which the cartridges were

scratched.
csn
volser
The volume serial number.
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCSV01
jobname
The jobname.
sss
The stepname.

273
IDC0098I
** LOCATION OF VOLUME: location
Explanation: The location information recorded in the

Inventory data set and assigned to the Mass Storage
Volume is listed. See the preceding message for the
cartridge serial numbers of these cartridges.
grpname
The group name.
System Action: If any groups remain to be processed,
the system continues processing with the next group.
Otherwise, the system abnormally ends the command.
Source: DFSMSdfp
Detecting Module: IDCLD01, IDCSD01
location
The location in the Inventory data set.
System Action: The system abnormally ends the
command.
Application Programmer Response: Insert the
missing cartridges when the Mass Storage Volume
Control portion of the Mass Storage System
Communicator is enabled. Run the command again. If
the cartridges assigned to the volume are lost, use the
REMOVEVR command to delete the volume record
from the Inventory data set before running the
command again.
Source: DFSMSdfp
IDC0106I
NO ACTIVE GENERAL USE VOLUMES

IN GROUP grpname
Explanation: Either there are no mass storage

volumes in the indicated group or there are no base
volume records in the Inventory data set that have the
active and general-use flags on.
the system continues processing with the next group.
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCRV01, IDCSV01

IDC0107I
IDC0102I
NO ACTIVE NON-GROUPED VOLUMES

IN THE INVENTORY DATA SET
NO DATA SETS ELIGIBLE FOR

SELECTION ON VOLUME volser
Explanation: There are no non-grouped, active mass

storage volumes in the inventory data set.
Explanation: No data sets on the indicated volume

met the criteria specified on the command for either
listing or scratching.

command. The system returns a reason code from the
Mass Storage Volume Control functions.
System Action: If there are more volumes to be

processed, the system processes the next volume.
Source: DFSMSdfp
Source: DFSMSdfp
IDC0104I
IDC0112I
NO ACTIVE VOLUMES IN THE

INVENTORY DATA SET
Explanation: Either there are no base volume records

in the Inventory data set or there are no base volume
records with the active flag on in the Inventory data set.
The Mass Storage Volume Control functions returned a
reason code of either X'208' or X'223'.
dsname SCRATCHED
Explanation: The data set was successfully scratched

from the volume table of contents (VTOC).
System Action: If other data sets remain to be
scratched, the system continues processing with the
next data set. Otherwise, the system abnormally ends
the command.

command.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCSD01

IDC0105I
NO ACTIVE VOLUMES IN GROUP

grpname
Explanation: Either there are no mass storage

volumes in the group or there are no base volume
records with the active flag on in the group.
274
IDC0117I
VOL volser IN GROUP grpname NOT

PROCESSED BY SIS
Explanation: The system-initiated scratch function

scheduled for processing an entry that indicated the
volume in a group. The entry was found:
v when modifying the group status with the OFFT or
OFFP parameter
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
grpname
The group name.
System Action: The system continues processing;
however, the system does not process the volume.
Source: DFSMSdfp
Detecting Module: IDCAL01, IDCDE01, IDCMP01
IDC0181I
construct USED IS constnme
Source: DFSMSdfp
Explanation: The Storage Management Subsystem

(SMS) construct was specified in an access method
services DEFINE or IMPORT command. The construct
name was the construct actually used during processing
of the command. The values for construct and
constnme may be one of the following:
Detecting Module: IDCMV01, IDCSR01
v DATACLASS
Application Programmer Response: Use the

SCRDSET command as required to perform necessary
scratch processing for the volume. The volume is not
scheduled for system-initiated scratch processing.
v MANAGEMENTCLASS
IDC0140I
ALIASES ARE NOT EXPORTED FOR

VSAM MASTER CATALOGS
Explanation: An integrated catalog facility catalog is

being exported, but its user catalog pointer entry is in a
virtual storage access method (VSAM) master catalog.
Therefore, EXPORT will not export the aliases of this
integrated catalog facility catalog.
v STORAGECLASS.
For each specific command, the value of the construct
may differ from that of the construct name. Any
difference between the two constructs resulted from
automatic class selection processing.
System Action: The system continues processing with

the export of the integrated catalog facility catalog.
construct
The construct.
Source: DFSMSdfp
constnme
The construct name.
IDC0144I
VOLUME SERIAL FOR catname

DURING EXPORT DISCONNECT WAS
volser

Source: DFSMSdfp

indicating the volume serial number for the volume that
contains the catalog being disconnected.
Detecting Module: IDCDE01, IDCMP01
Explanation: The system issues this message for one

of the following reasons:
catname
The name of the catalog being disconnected.
volser

Source: DFSMSdfp
IDC0180I
PASSWORD SPECIFICATION FOR

entrynme MAY BE INEFFECTIVE
Explanation: During an access method services

ALTER or DEFINE operation, the system found that one
or more passwords were specified. Since the object
entry name is managed by the Storage Management
Subsystem (SMS), these passwords will be ineffective
for the protection of that object.
entrynme
The entry name.
IDC0182I
EXPIRATION DATE RESET TO yyyy.ddd
v The expiration date specified during an access

method services ALTER or DEFINE operation
exceeded the management class retention period.
The system resets the date.
v An alternate index (AIX) expiration date is being
overridden. For an SMS managed AIX, CATALOG
processing does not allow the expiration date to
exceed that of the related cluster.
System Action: The system uses the reset date
instead of the expiration date. For an AIX that does not
have a management class, the system sets the
expiration date to that of the related cluster.
Application Programmer Response: If the reset date
is incorrect, change it by doing one of the following:
v By MANAGEMENTCLASS, specify a different
management class that allows the expiration date
originally specified
275
v By FOR or TO, specify an expiration date that does

not exceed the management class retention period
Source: DFSMSdfp
Detecting Module: IDCAL01, IDCDE01
IDC0196I
dsname HAS BEEN ROLLED OFF AND

action
Explanation: Changing the maximum number of

generation data sets (GDSs) that can be associated
with a generation data group (GDG) caused one or
more of the GDSs to be rolled off. In addition to being
rolled off, the GDS data set name was:
v Recataloged as a non-VSAM data set
v Uncataloged, but still exists
v Deleted
dsname
The data set name.
action
Indicates whether the GDS was recataloged,

uncataloged or deleted.
and the calling program is not in error, search problem

SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRI01
IDC0222I
WARNING: COMMAND-END DELIMITER

APPEARS WITHIN APOSTROPHES
Explanation: The system found a semicolon, the

optional command delimiter, in an item that is enclosed
within apostrophes. A closing apostrophe may have
been omitted.
System Action: The system accepts the usage. The
system continues processing, treating the semicolon as
a valid character.
Application Programmer Response: Insert the
missing apostrophe, if one was omitted. Run the job
again.
Source: DFSMSdfp

Detecting Module: IDCAL01
Source: DFSMSdfp
IDC0204I
PRECEDING COMMAND BYPASSED

DUE TO CONDITION CODES
Explanation: The modal command structure

specification caused the command to be bypassed.
System Action: The system checks the command for
syntax errors. The system does not process the
command.
recurs and the program is not in error, search problem
Source: DFSMSdfp
IDC0206I
IMPROPERLY PLACED COMMA HAS

BEEN FOUND AND IGNORED
Explanation: The caller coded an unnecessary

comma. Omitted positional parameters may not be
denoted by consecutive commas.
System Action: The system accepts the usage and
ignores the comma.

IDC0233I
TOO MANY RIGHT PARENTHESES

FOUND. EXCESS IGNORED
Explanation: The system found too many right

parentheses at the end of a subparameter list or
following a first-level parameter.
System Action: The system ignores the excess
parameters. Scanning continues.
syntax of the parameters.
Source: DFSMSdfp
IDC0234I
WARNING: TOO FEW RIGHT

PARENTHESES FOUND AT END OF
COMMAND

extra comma.
Explanation: The system found too few right

parentheses at the end of the command to close off the
subparameter lists.
System Action: The system accepts the usage. The
276

syntax of the parameters.
Source: DFSMSdfp
Application Programmer Response: Save the key

value for use when the data set is deciphered.
Source: DFSMSdfp
Detecting Module: IDCIO01
IDC0361I
** dsname NOT LOCATED
Explanation: The virtual storage access method

(VSAM) or OS locate request for the indicated data set
was unsuccessful. A preceding message indicates the
reason for the failure.
IDC0254I
CANCEL COMMAND WAS EXECUTED
Explanation: An IDCAMS CANCEL command was

issued to end the current job step. The step will be
ended with a return code in register 15 equal to the
value of the highest condition code encountered before
the CANCEL command was run.
System Action: The system ends the job step. The
remainder of the command stream is not processed.
Application Programmer Response: The maximum
condition code is returned in register 15 and will be
printed out on the IDCAMS completion message,
IDC0002I. Perform the programmer response from
message IDC0002I.
Source: DFSMSdfp
IDC0339I
ENCIPHERED DATAKEY FOR keyname

IS keyval
Explanation: The key value field provides information

for the data encrypting key enciphered under the
secondary file key whose external label is the key
name.
keyname
The key name.
keyval
The key value.

Application Programmer Response: Save the key
value for use when the data set is deciphered.
Source: DFSMSdfp
IDC0342I
PRIVATE DATA KEY IS keyval
Explanation: The caller did not specify a private data

encrypting key. REPRO command processing provided
the data encrypting key.
dsname
The data set name.
System Action: If the SCRDSET command is being
run, this data set is not scratched. If the LISTDSET
command is being run, this data set is listed unless the
UNCATALOGED, EXPIRATIONDATE, EXPIRATION,
CREATIONDATE, or CREATION parameter is specified.
Application Programmer Response: Determine why
the data set was not located. Correct the problem if
necessary. Run the command again.
the job log for more information.
Issue the access method services LISTCAT command
to list catalog entries and information about objects
defined in the catalog.
Then 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
IDC0362I
** dsname NOT SCRATCHED
Explanation: An error occurred during a virtual

storage access method (VSAM) delete request. The
error prevented the data set from being scratched. A
preceding message explains the type of error.
dsname
The data set name.
System Action: The command continues to scratch
and uncatalog remaining eligible data sets.
error identified in the preceding message and do one of
the following:
v Run the SCRDSET command again
keyval
v Specify DELETE in the DISP parameter on the DD

statement to scratch the data set
The key value.
277
v Run the DELETE command to scratch the data set

Run the LIST service aid with the following control
statements:
v LISTOBJ: to obtain an object module listing
v LISTLOAD OUTPUT=BOTH: to obtain a formatted
listing of the load module with its module map and
cross references
If the error still exists, 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
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.
The error prevented the data set from being
uncataloged.
v An error occurred during an operating system (OS)
uncatalog request.
The error prevented the data set from being
uncataloged.
v An error occurred during the scratch of the data set.
Because the data set cannot be scratched, no
attempt was made to uncatalog the data set.
dsname
The data set name.

statement to scratch the data set.
v Run the DELETE command to scratch the data set.
v Run the IEHPROGM utility to scratch and uncatalog
the data set.
the job log for more information. Run the LIST service
aid with the following control statements:
v LISTOBJ: to obtain an object module listing
v LISTLOAD OUTPUT=BOTH: to obtain a formatted
listing of the load module with its module map and
cross references
If the error cannot be determined, search problem
JCL, the SYSOUT output, and all printed output and
Source: DFSMSdfp
IDC0394I
jobname.sss 3850 DEMOUNT FAILED,

VOL=vvvvvv,vua, RC=X'cde'
Explanation: The system was unable to demount the

virtual volume requested in the indicated step of the job.
jobname
The jobname.
sss
The specified job step.
vvvvvv The virtual volume serial address.

vua
The virtual unit address.
cde
The failed reason code.
System Action: The command continues to scratch

and uncatalog remaining eligible data sets. The system
explains the error with a preceding message.

problem indicated by the Mass Storage System (MSS)
reason codes. Then issue the UNLOAD command.

error identified in the preceding message. If the data set
was already scratched from the volume table of
contents (VTOC), do one of the following:
Source: DFSMSdfp
v Specify UNCATLG in the DISP parameter on the DD

statement to uncatalog the data set.
IDC0396I
Detecting Module: IDCSA06, IDCSA10

** dsname NOT RECATALOGED
v Run the DELETE command to uncatalog the data

set.
Explanation: The data set was not recataloged. The

system writes a preceding message that explains the
reason for the error.
v Run the IEHPROGM utility to uncatalog the data set.
If the data set was not scratched from the VTOC, do

dsname
v Run the SCRDSET command again.
The data set name.
Application Programmer Response: Examine the
278
preceding message for response.

Source: DFSMSdfp
IDC0397I
DATA SET CATALOGED IN VSAM

CATALOG THAT DOES NOT OWN
VOLUME
Explanation: The data set identified in the subsequent

message was located in a virtual storage access
method (VSAM) catalog that does not own the volume.
VSAM catalog management does not support altering
device type and volume serial number in VSAM
catalogs other than the owning catalog.

Source: DFSMSdfp
IDC0497E
CARTRIDGE EJECTED; jobname,

stepname
Explanation: The system writes an informational

message to the system operator, notifying him of the
presence of a cartridge in the cartridge access station.
Application Programmer Response: Use the access

method services LISTCAT, DELETE, and DEFINE
commands to determine the fields defined in the entry.
Delete the entry and redefine the entry with the new
device type.
jobname

the job log for more information. Issue the access
method services LISTCAT command to list catalog
entries and information about objects defined in the
catalog.
Source: DFSMSdfp
The jobname.
stepname
The job step.
Operator Response: Remove the cartridge from the
cartridge access station.
Source: DFSMSdfp
IDC098D
ACCESS REQUESTED TO text

VOL=SER=volser: REPLY Y OR N text
Explanation: Processing of REPAIRV DISPLAY or

REPAIRV COPY command requests authorization to
access a staging pack, or processing of the REPAIRV
MODIFY command requests authorization to update the
volume table of contents (VTOC) or its header
(VTOCHEADER).
IDC0398I
DATA SET RESIDES ON MORE THAN

TWENTY VOLUMES
Explanation: The data set identified in the subsequent

message resides on more than twenty volumes. It has
not already been recataloged. Recataloging is not
supported by this program if the data set resides on
more than 20 volumes. If the data set is cataloged in
the virtual storage access method (VSAM) owning
catalog, it has already been recataloged.
Application Programmer Response: Use
IEHPROGM utility or access method services DELETE
and DEFINE command to recatalog the data set if it is
cataloged and not already recataloged.
the job log for more information. Issue the access
catalog.
text
STAGING PACK VTOCHEADER VTOC.
volser
System Action: Processing of the REPAIRV

command waits for the operator to respond. If the
response is Y, the system continues processing. If the
response is N, the system abnormally ends the
command.
Operator Response: Enter Y to allow access, or enter
N to deny access.
exists, contact the IBM Support Center. Provide the JCL
and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07
279
IDC0508I
DATA ALLOCATION STATUS FOR

VOLUME volser IS return-code
Explanation: The system indicates the allocation

status for a volume containing the data component. The
code indicating the status is the virtual storage access
method (VSAM) catalog return code.
ser
return-code
The return code. A 0 indicates

success.
Detecting Module: IDCDE01

IDC0511I
SPACE ALLOCATION STATUS FOR


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
return-code

success.

IDC3009I for a complete explanation of the return code.
Source: DFSMSdfp

Detecting Module: IDCDE01, IDCMP01, IDCRM01

IDC0509I
INDEX ALLOCATION STATUS FOR


status for a volume containing the index component.
The code indicating the status is the virtual storage
access method (VSAM) catalog return code.
ser
return-code

success.

Source: DFSMSdfp
IDC0510I
CATALOG ALLOCATION STATUS FOR


status of a volume containing the virtual storage access
method (VSAM) catalog. The code indicating the status
is the VSAM catalog return code.
Source: DFSMSdfp
IDC0512I
NAME GENERATED - (x) dsname
Explanation: Data and index component names are

generated by virtual storage access method (VSAM)
catalog management, when these names have not been
specified.
Either a D or an I. It indicates which

component the data set names.
dsname
The data set name.
Source: DFSMSdfp
IDC0520I
CATALOG RECOVERY VOLUME IS ser
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
the object just defined.
ser
ser
return-code

success.
Application Programmer Response: Mount the

named volume for any future operation that modifies the
catalog entry for the object just defined.

Source: DFSMSdfp
280
Source: DFSMSdfp
IDC0526I
ALTERED ALLOCATION STATUS FOR

Explanation: The system writes this message to

indicate the allocation status of volumes being added or
removed from a virtual storage access method (VSAM)
data set. The code indicating the status is the VSAM
catalog return code.
system output indicates the reason the member name

was not renamed. The system continues processing.
problem indicated by the previous message. Run the
command again.
Source: DFSMSdfp
ser
IDC0535I
return-code
The return code. See message

IDC3009I for an explanation of the
return code.
Explanation: The indicated member has been

successfully renamed.

Source: DFSMSdfp
IDC0531I
ENTRY xxx ALTERED

indicate that the specified entry has been successfully
altered.
xxx
The altered entry.

Source: DFSMSdfp
IDC0532I
** ENTRY xxx NOT ALTERED
MEMBER mem RENAMED
mem
The indicated member.

Source: DFSMSdfp
IDC0548I
** MEMBER mem NOT DELETED

inform the operator or programmer that the member
was not deleted.
mem
The indicated member.
System Action: An associated message accompanies

this message indicating why the member was not
deleted. The system continues processing.
Source: DFSMSdfp

indicate that the entry was not altered.
Detecting Module: IDCDL01
IDC0549I
xxx

indicate the member that has been successfully deleted.
The unaltered entry.
System Action: The preceding message in the

system output indicates the reason the entry was not
altered. The system continues processing.
MEMBER mem DELETED
mem
The deleted member.

problem indicated by the previous message. Run the
command again.
Source: DFSMSdfp
Source: DFSMSdfp

IDC0550I
IDC0534I
** MEMBER mem NOT RENAMED
ENTRY (x) dsname DELETED

indicate the member name that was not renamed.
Explanation: The specified data set name entry was

deleted from the virtual storage access method (VSAM)
catalog.
mem
dsname
The member name.
The data set name.
System Action: The preceding message in the

281
The type of entry, as follows:

C--cluster
D--data
G--alternate index
I--index
R--path
V--volume
U--user catalog
M--master catalog
A--non-VSAM
B--GDG base
X--alias
System Action: The system deletes a volume entry

only when the volume no longer contains any data
spaces. The system uncatalogs, but does not delete, a
data set with indirect or extended indirect VolSer. The
ser
System Action: The volume is still owned by the

catalog in which it was originally defined.
Source: DFSMSdfp
IDC0571I
CATALOG RELOAD HAS BEEN

INVOKED
Explanation: A REPRO command has been

processed where the target data set is a catalog. This
marks the beginning of processing of a catalog reload
operation.
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCDL01, IDCMP01, IDCRM01,

IDCXP01
IDC0594I
IDC0551I
** ENTRY dsname NOT DELETED

indicate that the entry that was not deleted. An
accompanying message will indicate why the entry was
not deleted.
dsname
The data set name.
PORTABLE DATA SET CREATED

SUCCESSFULLY ON date AT hh:mm:ss
Explanation: At this point, the portable data set

contains all information necessary to re-create the
cluster being exported.
date
The date of the data set creation.
hh:mm:ss
The time of the data set creation in hours,
minutes, and seconds.
System Action: The named data set is not deleted.

cause of the error.
Source: DFSMSdfp

Detecting Module: IDCXP01

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
Center. Provide the JCL and the SYSOUT output for the
job.
Explanation: This message identifies the name of the

catalog for which CONNECT completed successfully.
Source: DFSMSdfp
dsname
Detecting Module: IDCDL01, IDCXP01

The data set name.
IDC0555I
DELETION OF SPACE OBJECT DID

NOT CAUSE ser TO BE DELETED
Explanation: When a DELETE command is processed

against the volume serial number and the FORCE
parameter is not specified, all empty data spaces are
deleted. Data spaces that still contain data set
segments are not deleted. Only when all data spaces
on a volume are deleted or when FORCE is specified,
is that volume deleted from its owning catalog.
282
Source: DFSMSdfp
Detecting Module: IDCMP01
IDC0604I
DATA SET BEING IMPORTED WAS

EXPORTED ON date AT hh:mm:ss
Explanation: This message informs the caller of the

date and time that the data set was exported.
date
The date on which the data set was exported.
hh:mm:ss
The time at which the data set was exported,
in hours, minutes, and seconds.
Source: DFSMSdfp
Detecting Module: IDCMP01, IDCRM01
IDC0634I
NUMBER OF ENTRIES CONVERTED

WAS nnn
Explanation: The number of catalog entries

successfully converted into entries in the virtual storage
access method (VSAM) or the integrated catalog facility
(ICF) catalog is indicated. All base entries and their
associations are counted. Data and index component
entries are not counted.
IDC0611I
DATA SET TO BE IMPORTED

ALREADY EXISTS - DELETE
ATTEMPTED
Explanation: A catalog define was attempted for the

data set to be imported. The command failed because
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
exported.
System Action: An attempt is made to delete the
existing entry. The message following this message in
the listing indicates whether the delete was successful.
Source: DFSMSdfp
IDC0622I
USERCATALOG catname
DISCONNECTED
Explanation: A callers catalog has been disconnected

by IMPORTRA in order to connect a new pointer to the
user catalog.
catname
The catalog name.
Source: DFSMSdfp
Detecting Module: IDCRM01
IDC0626I
IMPORTRA SUCCEEDED FOR dsname
Explanation: The data set has been successfully

imported.
dsname
The data set name.
System Action: Normal processing continues.
Source: DFSMSdfp
nnn
The number of entries converted.

Source: DFSMSdfp
Detecting Module: IDCCC01
IDC0635I
** dsname NOT CONVERTED
Explanation: During CNVTCAT processing, the

catalog entry data set was not converted.
dsname
The data set name.
System Action: An associated message contains the
information required to correct the error. The system
continues processing with the next entry.
Source: DFSMSdfp
IDC0636I
NUMBER OF ENTRIES UPDATED WAS

nnn
Explanation: The number of non-virtual storage

access method (VSAM) entries whose volume
information has been updated is indicated. Volume
information of a non-VSAM entry is updated when the
volume information of a duplicate entry being converted
from the operating system (OS) source catalog is
different from that of the existing non-VSAM entry.
nnn
The number of entries updated.

Source: DFSMSdfp
IDC0637I
** dsname NOT UPDATED
Explanation: The operating system (OS) catalog entry

specified was not converted.
dsname
The data set name.
283
System Action: An accompanying message contains

the information required to correct the error. The system
continues processing.
Source: DFSMSdfp
IDC0659I
SORT PRODUCT MESSAGE DATA SET

NOT ALLOCATED: REASON CODE IS
reason-code
Explanation: DFSORT (or an equivalent product) was

unable to allocate the DFSORT (or equivalent product)
message data set.
IDC0639I
In the message text, reason-code is:
SPHERE CONVERSION STARTED FOR

dsname
Explanation: The conversion of the specified base

sphere and its associations has started.
dsname
The data set name.
Source: DFSMSdfp
IDC0652I
dsname SUCCESSFULLY BUILT
Explanation: Building of the alternate index identified

by the data set name has been successfully completed
with no errors encountered.
04
Allocation failed
08
Insufficient virtual storage to perform allocation
System Action: BLDINDEX will process the command

using DFSORT (or an equivalent product) but no
messages will be written to the DFSORT (or equivalent
product) message data set.
Application Programmer Response: For reason
code 04, supply a DD statement for the DFSORT (or
equivalent product) message data set (see the
SORTMESSAGEDD parameter).
For reason code 08, increase the virtual storage region
size and resubmit the job.
Detecting Module: IDCBI01
IDC0665I
dsname
The data set name.
Source: DFSMSdfp
IDC0657I
REQUIRED SORT PRODUCT

FUNCTIONS UNAVAILABLE
NUMBER OF ENTRIES THAT

MISCOMPARED IN THIS CRA - nnn
Explanation: The COMPARE option was requested

and this informational message indicates the number of
entries for which a miscompare between the catalog
recovery area (CRA) and catalog occurred. The types of
entries are as follows:
v Volume
v Cluster
v Alternate index
v non-virtual storage access method (VSAM)
v user catalog entries
Explanation: DFSORT (or an equivalent product) with

the functions required for BLDINDEX was not available.
System Action: The system stops processing the

command.
System Programmer Response: Correct the error as

indicated in the preceding messages if they exist. If no
preceding messages exist, check the DFSORT (or
equivalent product) message data set for detailed
information on the cause of the failure. If
SORTMESSAGELEVEL(ALL) was specified use the call
identifier to find the set of DFSORT (or equivalent
product) messages for this call (see IDC01850I and
DFSORT message ICE200I or the appropriate message
for an equivalent product), and correct the DFSORT (or
equivalent product) error that caused the failure.
nnn
The number of entries miscompared.

whether recovery is required.
Source: DFSMSdfp
Detecting Module: IDCLR01
IDC0669I
EXPORTING FROM CRA ON VOLUME

volser
Explanation: This message indicates the current

catalog recovery area (CRA) and volume being used to
export the data sets named in the following messages.
ser
284
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC0680I
IDC0670I
DATA SET SUCCESSFULLY EXPORTED
Explanation: The data set named in message

IDC0674I was successfully retrieved and written to the
portable data set.
Source: DFSMSdfp
IDC0672I
** LOCKED ON CATALOG catname
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
first CRA processed.
catname
The catalog name.
VOLUME volser CREATED ON

CARTRIDGES csn1 csn2
Explanation: A new volume was created.

volser
csn1
csn2
The cartridge serial numbers.

Source: DFSMSdfp
Detecting Module: IDCCV01
IDC0686I
PARTIALLY CREATED VOLUME volser

SCRATCHED
Explanation: The partially created volume was

scratched during back out because an error occurred.
volser
Source: DFSMSdfp
System Action: The command ends normally.

error indicated in a preceding message. Run the
command again.
IDC0674I
** NAME IS dsname
Explanation: This second-level message gives the

data set name of the object referred to in the preceding
messages.
Source: DFSMSdfp
IDC0703I
dsname
The data set name.
System Action: See the primary message.
Application Programmer Response: See the primary
message.
** VOL volser COPIES TO CART csn1

csn2, DATE yyddd
Explanation: The volume was copied to the cartridges

on the date indicated.
volser
Source: DFSMSdfp
csn1
csn2
yyddd
The date, in year and days.
IDC0676I
PORTABLE DATA SET CREATED

SUCCESSFULLY ON date AT time
Explanation: This message indicates the portable

data set contains the necessary information to recreate
the data sets by IMPORTRA.
Source: DFSMSdfp
IDC0704I
date
Date on which data set was created.
time
Time at which data set was created.

Source: DFSMSdfp
Detecting Module: IDCCO01

** CARTRIDGES OF OLDEST BACKUP
COPY yyddd SELECTED FOR REUSE
Explanation: The COPYV command selected the

cartridges of the oldest backup copy volume indicated
by the date for reuse. The preceding message
describes the status of the new copy volume.
285
yyddd

Source: DFSMSdfp
Application Programmer Response: Run the

MODIFYV command to change the volume attributes or
the volume serial number of the active volume.
Source: DFSMSdfp
Detecting Module: IDCAV01

IDC0724I
IDC0705I
** CARTRIDGES OF AN INCOMPLETE
COPY VOLUME SELECTED FOR
REUSE
** SERIAL NUMBER OF VOLUME volser

NOT CHANGED
Explanation: The volume has been activated but the

volume serial number could not be changed. See the
preceding message for further explanation of the error.
Explanation: Due to a previous failure by the COPYV

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
Source: DFSMSdfp

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

COPY VOLUME volser2, COPY DATE
yyddd
Explanation: The designated volume was successfully

restored using either the latest backup copy or a user
designated copy created on the date indicated.
However, if the target volume serial number is different
than the copy volume, the target volume serial number
was overwritten during the copy operation and must be
restored. The target volume is currently flagged as an
incomplete copy in the Inventory data set. The
command restores the volume label and clears the
incomplete copy flag from the Inventory data set before
processing of the command ends.
volser1 The volume serial number of the restored

volume.
volser2 The volume serial number of the restoring
volume.
yyddd

Source: DFSMSdfp
IDC0725I
READWRITE ATTRIBUTE SET FOR

VOLUME volser
Explanation: The volume is assigned the readwrite

attribute as requested.
volser

Source: DFSMSdfp
IDC0731I
VOLUME volser HAS BEEN MADE

INACTIVE
Explanation: The designated volume was successfully

deactivated and made nonmountable.
Source: DFSMSdfp
volser
Detecting Module: IDCRV01
Source: DFSMSdfp
IDC0722I
VOLUME volser HAS BEEN ACTIVATED
Explanation: The inactive volume was made active

but either the volume attributes could not be updated or
the volume serial could not be changed.
volser
286
Detecting Module: IDCSR01

IDC0733I
VOLUME LABEL RESTORED TO

ORIGINAL STATUS
Explanation: The volume label is restored to its

original status because the volume cannot be
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

cartridge labels, will remain set only if the flag was
previously set from an earlier relabel failure by:
v The MODIFYV command
v The ADDV command
v The STOREV command
System Action: The command abnormally ends with
an error message.
Application Programmer Response: Take one of the
following actions for the command that failed:
v For a Rename operation failure for ADDV, run ADDV
to backout or retry the rename operation if the
volume is inactive. If the volume is active, run
MODIFYV or STOREV to either backout or retry the
rename operation.
run to recover from a rename failure, a DD statement
for the volume is required and must specify deferred
mounting.
number. For the VOLUME parameter, specify the
volume serial number as recorded in the cartridge
labels and the volume record. For the NEWSERIAL
parameter, specify the desired volume serial number.
Note that the security check for non-VSAM status
and password protected data sets is bypassed only if
the NEWSERIAL parameter specifies the same
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.
If ADDV, MODIFYV, or STOREV terminates without
indicating the status of the rename operation,
LISTMSVI can be run to determine whether the
volume is flagged for recovery purposes. If the
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
a rename operation failed for the preceding volume
and that serial number nnnnnn is recorded in the
volume label of the volume.
v For a Rename Operation failure for MODIFYV,
recover by:
Run ADDV to activate the volume if the volume is
merely inactive and has no volume serial
mismatch condition
Run ADDV to both activate the volume and
complete the rename operation if the volume is
both inactive and has a volume serial mismatch
condition
Run MODIFYV again to complete or retry the
rename operation if the volume is active but has a
mismatch condition, or 4) run STOREV to
complete or retry the rename operation if the
volume is active and if a duplicate volume serial

number is desired as a result of the rename.
For the DD statement requirements, the proper
VOLUME and NEWSERIAL parameter values, and
use of LISTMSVI, refer to the description above for
an ADDV rename failure.
v For a Rename Operation failure for STOREV, run
STOREV again or run MODIFYV to either backout or
retry the rename operation.
JCL, the SYSOUT output for the job, and all printed
output and output data sets related to the problem.
Source: DFSMSdfp
IDC0737I
FURTHER PROCESSING TERMINATED
Explanation: An error occurred which prevents any

further processing. Preceding messages indicate the
extent of the processing which has been completed.
Functions which may not be completed are:
v Updating the alternate track information in the volume
table of contents (VTOC) of the TO volume.
v If the volume is virtual storage access method
(VSAM), updating the time stamp in the VTOC of the
TO volume.
v If the FROM and TO volume serial numbers are
different, updating the serial number in the label of
the TO volume.
v Updating the owner in the label of the TO volume.
v If a recatalog option was specified or defaulted to,
recataloging the data sets.
v If the scratch option was specified or defaulted to,
scratching the data sets on FROM volume.
For conversion from a 3336 Model 1 Disk Pack to a
mass storage volume the incomplete copy flag is set
in the Inventory data set for any of the following
cases:
v The FROM and TO volume serial numbers are not
the same, and processing ended during the copy
operation.
v The FROM and TO volume serial numbers are not
the same, and processing ended before the VTOC
and volume label were updated.
v The TO volume is VSAM and processing ended
before the VSAM recataloging was completed.
287

an error message indicating the severity of the problem.
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
Mass Storage Volume using the SCRATCHV command.
Otherwise, decide whether to run the CONVERTV
command again or complete the functions not
performed by CONVERTV using other access method
services commands or utility programs. The owner in
the volume label can be updated by the MODIFYV
command for Mass Storage Volumes. Data sets can be
recataloged using access method services DELETE and
DEFINE commands or IEHPROGM utility. Data sets can
be scratched using the access method services
DELETE command or IEHPROGM utility.

Source: DFSMSdfp
Detecting Module: IDCCN01
IDC0748I
ELIGIBLE NON-VSAM DATA SETS

SUCCESSFULLY RECATALOGED
Explanation: The data sets not in the virtual storage

access method (VSAM) owning catalog have been
recataloged if there were any that needed to be
recataloged.
Source: DFSMSdfp

IDC0749I
Source: DFSMSdfp
VTOC OF FROM VOLUME SCRATCHED
Explanation: The volume table of contents (VTOC) of

the source volume was successfully scratched.
Source: DFSMSdfp

IDC0751I
IDC0743I
FROM VOLUME COPIED TO THE TO

VOLUME
Explanation: The source volume was successfully

copied to the target volume.
Source: DFSMSdfp
Explanation: The requested volume was scratched.

The cartridge IDs in the message are in reverse order
from the order in which they were scratched.
volser
DATA SETS IN VSAM CATALOG

SUCCESSFULLY RECATALOGED
Explanation: Data sets in the virtual storage access

method (VSAM) catalog owning the volume have been
successfully recataloged.
Source: DFSMSdfp
csn1
csn2
IDC0746I
CARTS csn1 csn2 SCRATCHED FOR

VOLUME volser
The cartridge serial numbers of the cartridges

that were scratched.

Source: DFSMSdfp
Detecting Module: IDCSV01
IDC0760I
RECORD FOR COPY yyddd REMOVED
Explanation: The copy record created on the date

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
storage access method (VSAM) time stamp in the
volume table of contents (VTOC). The converted
volume now has the appropriate owner and volume
serial number in the label.
288
yyddd

Source: DFSMSdfp
Detecting Module: IDCRR01
IDC0763I
RECORD FOR VOLUME volser

REMOVED
Explanation: A base volume record for the indicated

volume was removed from the Inventory data set.
volser

Source: DFSMSdfp
IDC0780I
SCRATCH CARTRIDGE csn EJECTED
Explanation: A scratch cartridge was ejected from the

Mass Storage Facility (MSF).
csn
IDC0790I
Explanation: An old or defective cartridge of a Mass

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
defective cartridge has been copied to the new
cartridge.
csn1
The cartridge serial number of the replaced

cartridge.
csn2
The cartridge serial number of the replacing

cartridge.

Source: DFSMSdfp
Detecting Module: IDCRL01
IDC0791E
Source: DFSMSdfp
Detecting Module: IDCEC01
IDC0781I
NUMBER OF SCRATCH CARTRIDGES

EJECTED IS nnn
Explanation: A number of scratch cartridges were

ejected successfully from the library.
nnn
The number of scratch cartridges ejected.

Source: DFSMSdfp
IDC783E
SCRATCH CARTRIDGE csn EJECTED;

jjj sss
Explanation: A scratch cartridge was ejected from the

Mass Storage Facility (MSF).
csn
jjj
The jobname.
sss
The job step.

Operator Response: Remove the scratched cartridge
from the Cartridge Access Station and label it as a
scratch cartridge.
Source: DFSMSdfp
CARTRIDGE csn1 REPLACED BY

CARTRIDGE csn1
REPLACED CARTRIDGE
{csn|UNIDENTIFIED} EJECTED; jjj sss
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
Facility (MSF) after being replaced with a different
cartridge. The jobname and the stepname identify the
job associated with the ejected cartridge.
If the cartridge was ejected, the replacement failed and
the system failed to read the base volume record. The
cartridge serial number could not be identified.
Messages IDC2080I and IDC2400I will follow this
message indicating that the base volume could not be
read.
csn
The cartridge serial

number.
UNIDENTIFIED
The cartridge serial

number could not be
identified.
jjj
The jobname.
sss
The job step.

Operator Response: Remove the cartridge from the
Cartridge Access Station and label it as an old or
defective cartridge.
Source: DFSMSdfp
IDC0810I
VOLUME volser BEING PROCESSED
Explanation: A new volume is being processed.

Messages follow to indicate the data sets on the volume
that are scratched.
289
Source: DFSMSdfp
ser
System Action: The system begins processing of data

sets on the volume.
IDC0814I
Source: DFSMSdfp
IDC0811I
dsname UNCATALOGED
Explanation: The data set entry was successfully

removed from the catalog.
Explanation: The number of cataloged multivolume

data sets that were not scratched is specified. The
SCRDSET command does not scratch multivolume
cataloged data sets.
nnn
dsname
The data set name.
Source: DFSMSdfp
IDC0812I
nnn DATA SETS WERE SCRATCHED

FROM VOLUME volser
Explanation: The number of data sets scratched from

the indicated volume is specified.
nnn CATALOGED MULTI-VOLUME

DATA SETS WERE NOT SCRATCHED
The number of multi-volume data sets that

were not scratched.

the next volume.
Application Programmer Response: If the data sets
must be scratched, use one of the following methods to
scratch them:
v Run the IEHPROGM utility.
v Run the DELETE command.
v Specify DELETE in the DISP parameter of the DD
statement.
Source: DFSMSdfp
nnn
The number of the data sets scratched.
ser

Source: DFSMSdfp
IDC0813I
nnn CATALOGED GDG TYPE DATA

SETS WERE NOT SCRATCHED
IDC0815I
VOLUME volser IN GROUP grpname

BEING PROCESSED
Explanation: A new volume in the indicated group is

being processed. Additional messages follow to indicate
the data sets that have been scratched, if any.
ser
grpname
The group name.
Explanation: The number of cataloged generation

data group (GDG) type data sets that were not
scratched is specified. The SCRDSET command does
not scratch cataloged data sets with names that end in
name.GnnnnVnn.
System Action: The system processes the volume.
IDC0816I
nnn
Explanation: The PURGE parameter was not

specified on a SCRDSET command and an OS system
or control volume (CVOL) catalog data set SYSCTLG
met the limiting criteria for data set scratching. Data set
SYSCTLG was not scratched.
The number of the data sets that were not

scratched.

the next volume.
Application Programmer Response: If the data sets
must be scratched, use one of the following methods to
scratch them:
v Run the IEHPROGM utility.
v Run the DELETE command.
statement.
290
Source: DFSMSdfp
SYSCTLG DATA SET NOT SCRATCHED

the next volume.
Application Programmer Response: If the SYSCTLG
data set must be scratched, use the IEHPROGM utility
or run the SCRDSET command with the PURGE
parameter.
Source: DFSMSdfp
IDC0861I

IDC0817I
ALL ACTIVE VOLUMES IN GROUP

grpname WERE EXCLUDED
Explanation: No volumes were processed in the

specified group. Each active volume that normally would
have been processed was excluded with the
EXCLUDEVOLUMES parameter.
NO TAPE DATA SETS OPEN FOR THIS

CHECKPOINT
Explanation: No type 1 DSDRs were found for this

checkid.
System Action: Normal processing continues, but the
checkpoint is not processed.
Source: DFSMSdfp
Detecting Module: IDCCK01

IDC0862I
grpname
The group name.
the system continues processing with the next group. If
no groups remain to be processed, the system
abnormally ends the command.
Source: DFSMSdfp
IDC0832I
NO text RECORDS EXIST IN THE

INVENTORY
DUPLICATE SELECTED CHECKID

xxxxxxxx
Explanation: The same checkid was selected by the

user more than once.
xxxxxxxx
The duplicated check identification.
System Action: Normal processing continues, but the
checkpoint is not processed.
Application Programmer Response: Check to see if
another checkid was intended. Run the job again.

BASE VOLUME
DUPLICATE VOLUME
NONGROUPED VOLUME
CARTRIDGE INDEX
PLACE HOLDER
GROUP SCRATCH
GROUP CATALOG
Source: DFSMSdfp
No records of the type requested exist in the inventory.
xxxxxxxx
The duplicated checkpoint entry.
Source: DFSMSdfp
Detecting Module: IDCLV01

IDC0863I
DUPLICATE CHECKPOINT ENTRY

xxxxxxxx
Explanation: A duplicate entry was found for a

user-selected checkid already.

Source: DFSMSdfp
ICBVUT02

IDC0855I
CHANGE OF prm SUCCESSFUL
Explanation: The specified TUNE command

parameter was successfully changed.
prm
The specified parameter.

Source: DFSMSdfp
Detecting Module: IDCTU01
IDC0874I
FOLLOWING NOT ALPHABETIC INSUFFICIENT WORK SPACE FOR

SORT
Explanation: Insufficient virtual storage is available for

alphabetically sorting the objects to be listed by a
LISTCRA command.
System Action: The system does not sort the objects.
The system lists the objects in the order in which they
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
291
System Action: The system ignores the dump

element.
IDC0877I

length and/or type of the specified dump element.
NUMBER OF RECORDS THAT

MISCOMPARED IN THIS CRA - nnn
Explanation: The COMPARE option found a number

of records for which a miscompare between the catalog
recovery area (CRA) and the catalog occurred.
nnn
Source: DFSMSdfp
Detecting Module: IDCDB02
IDC0923I
The number of records miscompared.

whether recovery is required.
Source: DFSMSdfp
xxx ARRAY HEADER INVALID FOR

SYMBOLIC DUMP
Explanation: The specified array header in a symbolic

dump list:
v Has an incorrect extent field. The field must be
greater than 0 and less than or equal to 99.
v Has an incorrect item count field. The field must be

greater than 0.
IDC0888I
v Is an array header within an existing array

specification.
** ENTRY CONTAINS NO DATA

RECORDS
Explanation: There are no data records in the virtual

storage access method (VSAM) data set to be exported.
See the primary message for the name of the data set.
System Action: Processing of catalog information only
for this data set is attempted. See the primary message
for processing result. If processing was successful, then
the portable data set contains the necessary information
to redefine the data set through IMPORTRA.
Source: DFSMSdfp
IDC0896I
MIGRATED ENTRY dsname DELETED
Explanation: The migration utility deleted the specified

data set.
The condition code remains unchanged.

System Action: The system ignores the array header.
Dump elements within the array specification are treated
as single, non-arrayed items.
fields of the specified array header.
Source: DFSMSdfp
IDC0924I
DUMP ROUTINE INVOKED AT mac
Explanation: The access method services dump

routine has been invoked at the specified UDUMP
macro, a dump entry point.
mac
dsname
System Action: The system provides a dump of the

IDCAMS trace tables, as well as symbolic and/or full
region dumps, if requested by the IDCAMS user.
Source: DFSMSdfp
Source: DFSMSdfp
The data set name.
IDC0922I
xxx DUMP ELEMENT INVALID FOR

SYMBOLIC DUMP
Explanation: The specified dump element in a

symbolic dump list has an incorrect type field or the
length field is incorrect for the specified type. The
condition code remains unchanged.
xxx
The specified dump element.
The macro entry point.
IDC0925I
DUMP xxx PRODUCED AT DUMP

POINT mac
Explanation: A dump was requested and produced at

the specified UDUMP macro.
xxx
The dump identifier.
mac
The macro entry point.

Source: DFSMSdfp
292

IDC0932I
STORAGE MANAGEMENT
SUBSYSTEM CALL FAILED. RETURN
CODE WAS rc
Explanation: The subsystem interface was unable to

complete successfully the call to the storage
management subsystem (SMS).
Register 15 contains a hexadecimal reason code that
explains the error:
Code
Explanation
04
SMS does not support the requested function.
16
The function was not completed because of an

error.
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.
Source: DFSMSdfp
Detecting Module: IDCVS01
IDC0974I
** LAST USE DATE NOT CHANGED

FOR DATA SET(S) ON VOLUME volser
Explanation: An attempt to set or clear the

date-last-used field for one or more data sets failed on
the indicated volume. This message is preceded by a
message that specifies the error.
volser
Source: DFSMSdfp

error specified in the previous message. Run the
command again to set or clear the date-last-used field.

IDC0934I
STORAGE MANAGEMENT
SUBSYSTEM EXISTS, BUT IS NOT
OPERATIONAL.
Explanation: The call to the storage management

subsystem (SMS) was unsuccessful because the
subsystem is not operational.
Source: DFSMSdfp
IDC0935I
STORAGE MANAGEMENT
SUBSYSTEM DOES NOT EXIST.
Explanation: The system does not recognize the

storage management subsystem (SMS) as a valid
subsystem.
Source: DFSMSdfp
System Programmer Response: Run the IEHLIST

utility:
v With LISTVTOC FORMAT: to format and show the
volume table of contents (VTOC) for the volume
associated with the problem
v With LISTVTOC DUMP: to list the VTOC for the
associated volume
v With LISTPDS: to list the directory of the partitioned
data set (PDS) associated with the problem
If the error recurs and the program is not in error,
search problem reporting data bases for a fix for the
Center. Provide the JCL, the SYSOUT output for the
job, and all printed output and output data sets related
to the problem.
Source: DFSMSdfp
IDC1002I

IDC0970I
** NUMBER OF TRACKS = nnn; CCHH

OF NEXT TRACK =X'cchh'
Explanation: The above data could not be restored in

the volume table of contents (VTOC).
nnn
The number of tracks.

Application Programmer Response: If the volume is
a virtual volume, ignore this error since alternate tracks
do not apply for virtual volumes and the problem need
RESETCAT CATALOG catname VOL

volser LEVEL timestmp
Explanation: This message indicates the catalog to be

reset and the time stamp on the volume.
catname
The catalog name.
volser
timestmp
The time stamp on the volume.
Source: DFSMSdfp
293
Detecting Module: IDCRS01
Storage Volume Control Journal data set.

IDC01011I
CRA CHOSEN FOR RESET - VOL volser

LEVEL timestmp
Explanation: This message indicates the catalog

recovery area (CRA) to be reset and the time stamp on
the volume.
volser
timestmp
The time stamp on the volume.
Source: DFSMSdfp
IDC01037I
catname HAS BEEN RESET
Explanation: This message indicates that RESETCAT

processing has been completed for the indicated
catalog.
cde

A subsequent function may fail because of the error in
the Inventory data set.
Application Programmer Response: Investigate the
reason code returned from the Mass Storage System
Communicator. Contact the system programmer. The
Inventory data set should be restored from the backup
copy of the Inventory data set and the Journal data set.
Source: DFSMSdfp
IDC1116I
catname
The catalog name.
The reason code returned from the Mass

Storage System Communicator.
ERROR UPDATING CARTRIDGE

LABEL: text

VOLUME=volser, SEQ=nnn
CSN=csn [,CSN=csn2]
Source: DFSMSdfp
IDC01049I
NON-VSAM/USERCATALOG ENTRIES
MOVED TO NEW CATALOGS CRA
Explanation: This message indicates that RESETCAT

processing has moved non-virtual storage access
method (VSAM), generation data group (GDG) base,
alias, or user catalog entries from the catalog recovery
area (CRA) on the old catalogs volume to the CRA on
the new catalogs volume.
Source: DFSMSdfp
IDC1069I
FUNCTION PERFORMED - ERROR

UPDATING INVENTORY, CODE =
X'cde'.
Explanation: If a Mass Storage Control function was

requested, the function was performed by the Mass
Storage Control. However, an error prevented the Mass
Storage Volume Control Inventory data set from being
updated. If Inventory data set updating was requested,
at least one record was updated in the Inventory. An
error prevented the rest of the records from being
updated. The request has been journaled in the Mass
294
One of the following has occurred:

v For a REPLACEC command, a Copy Cartridge order
resulted in the replacement of one of two cartridges
in the indicated volume with the sequence number.
An unrecoverable error occurred while the label of
the other cartridge was being updated to point to the
target cartridge.
v For a COPYV, CREATEV, or SCRATCHV command,
a Define Volume or Eliminate Volume order resulted
in the cartridges being listed on the scratch cartridge
list table. The cartridge or cartridges in error are
given an unusable cartridge serial number because
the label could not be updated successfully.
volser
nnn
The sequence number.
csn
csn2
System Action: The system completes processing of

the failing order. Environmental data that identifies the
failing cartridge was logged on the primary processing
unit.
Application Programmer Response: For a
REPLACEC command, if the REPLACEC command
detected the error, reissue the command to replace the
other cartridge of the volume, which is indicated by the

sequence number. If either the COPYV, CREATEV, or
SCRATCHV command detected the error, issue the
MODIFYC command with the DIRECTEJECT parameter
to move the failing cartridge or cartridges to the exit
station. Then issue the NULLIFYC SCRC CSN
command to eliminate the records for the ejected
cartridges from the Mass Storage Facility.

exists, contact the IBM Support Center. Provide all
printed output and output data sets related to the
problem.
Source: DFSMSdfp
IDC01122I
IDC01120I
INCONSISTENT field
Explanation: The fields do not match in table entries

that are otherwise matching. Two secondary messages
identify the specific field or attribute values that are
inconsistent, and the respective tables and table indices
in which the inconsistencies occur.
field
The inconsistent field.

inconsistency. Issue the DUMPMSS, LISTMSF, or
LISTMSVI command to obtain dumps of the table with
the inconsistency. If there is any doubt whether the
inconsistency is temporary or not, issue the
CHECKMSS command again.
problem.
Source: DFSMSdfp
Detecting Module: IDCCH04
Source: DFSMSdfp
SUM=nnn OF INDIVIDUAL counts FROM
table NOT EQUAL TO TOTAL VALUE
Explanation: The sum of the individual counts or

value counts obtained from the specified table does not
match the field that should contain the total of the
counts or values. A secondary message identifies the
total value, and the table and table indices to locate the
entry containing the total.
nnn
The sum of individual counts.
counts
The specified counts.
table
The specified table.

LISTMSVI command to obtain dumps of the table with
inconsistency is temporary or not, run the CHECKMSS
command again.
problem.
Source: DFSMSdfp
IDC01121I
DUPLICATE field REFERENCE FOUND
Explanation: More than one table entry references the

same field or attribute. All entries should be unique with
respect to that field or attribute. Two secondary
messages identify the specific field or attribute values
that are identical, and the tables and table indices in
which the duplicate occurs.

IDC01123I
** VALUE=value table (index)
Explanation: This secondary message identifies the

value of the field or attribute named in a primary
message: the table name containing the field or
attribute, and the table indices that identify the particular
table entry containing the field or attribute.
field
The duplicated field.
value

duplicate table entries. Issue the DUMPMSS, LISTMSF,
or LISTMSVI command to obtain dumps of the table
containing the duplicate information. If there is any
doubt whether the duplicate is temporary or not, issue
the CHECKMSS command again.
table
The table containing the field.
index
The index that identifies the table.


programmer response for the primary message.
295

problem.
Source: DFSMSdfp
IDC01124I
MATCHING field=value NOT FOUND IN

table1 TO MATCH table2 (index)
Explanation: An entry in the first table did not have a

matching entry in the second table.
field=value
Identifies the field or attribute and its

value for which a matching entry was
not found or was not valid.
table1
table2
The specified tables.
index
The table indices that locate the

unmatched entries.
IDC1142I
OBJECT NOT SUPPORTED IN

RECORDMODE, CIMODE USED
Explanation: The user has requested EXPORT

RECORDMODE for an object that must be processed
using control interval access. EXPORT RECORDMODE
cannot be used for linear data set (LDS) clusters.
System Action: The system continues processing
using EXPORT CIMODE.
Application Programmer Response: Verify the
attributes of the data set being exported.
Source: DFSMSdfp
IDC01146I
NO DISCREPANCIES FOUND, REPORT

NOT PRINTED
Explanation: No report was printed by the AUDITMSS

command with the CHECK or READLABEL parameter.
No discrepancies were found.
Source: DFSMSdfp

LISTMSVI command to obtain dumps of the tables with
inconsistency is temporary or not, run the CHECKMSS
command again.
Detecting Module: IDCAU03

problem.
Source: DFSMSdfp
IDC1147I
IT IS RECOMMENDED THAT
DIAGNOSE AND EXAMINE BE RUN
BEFORE IMPORT OF CATALOG
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.
Source: DFSMSdfp
IDC1141I
OBJECT NOT SUPPORTED IN CIMODE,

RECORDMODE USED
Explanation: The programmer requested EXPORT

CIMODE for an object that the system cannot process
using control interval access. EXPORT CIMODE can
only be used for ESDS base clusters that do not have
an alternate index.
using EXPORT RECORDMODE.
attributes of the data set the system is exporting.
Source: DFSMSdfp
296
IDC1178I
DEFINE SPACE SUBCOMMAND

IGNORED - CATALOG IS ICF FORMAT
Explanation: A DEFINE SPACE subcommand was

found to be oriented to an integrated catalog facility
(ICF) catalog. This function is incorrect in the ICF
catalog environment and thus this command is ignored.
System Action: This is an attention message. The
system writes this message with a return code of 4 to
call attention to the condition.
Source: DFSMSdfp
Source: DFSMSdfp
IDC01190I
CARTRIDGE csn IS NOW A SCRATCH

CARTRIDGE
IDC1252I
Explanation: The cartridge with the specified cartridge

serial number is now a scratch cartridge.
csn
the cartridge serial number of the scratched

cartridge.

Source: DFSMSdfp
Detecting Module: IDCNC01
IDC01215I
LAST RECORD NOT FOUND IN dsname
Explanation: While displaying or copying the

requested records, the last record specified in the
DATASETRANGE or the REPAIRRANGE parameter
was not found in the data set.
COMMAND ALLOWS NO
PARAMETERS - PARAMETERS
IGNORED
Explanation: This message indicates that for a

command defined to have no parameters, some
parameters were coded.
System Action: The system ignores the parameters
but processes the command.
problem and the control statements for the job.
Source: DFSMSdfp

IDC01360I
dsname
The data set name.
System Action: REPAIRV DISPLAY/COPY ends.
Control returns to access method services. The return
code is 0.
Source: DFSMSdfp
IDCRD06
IDC01236I
TRACK cchh WAS DEBLOCKED INTO

nnn RECORDS
Explanation: The DEBLOCK function has deblocked

the R0/R1 pair into a number of records (including R0).
cchh
Indicates the track.
nnn
The number of records the rack was deblocked

into.
System Action: REPAIRV DEBLOCK has written

deblocked records to repair work.
THE FOLLOWING ENTRIES HAD NO

ERRORS
Explanation: The entries that follow this message

passed the DIAGNOSE checks with no errors.
System Action: The system lists the entries without
errors.
Source: DFSMSdfp
IDC01371I
RECORD DISPLAY SUPPRESSED,

ALREADY DUMPED
Explanation: The record described by message

IDC21365I will not be dumped here because the record
has already been dumped. If DIAGNOSE is unable to
obtain enough storage to show which records have
been dumped, suppression of duplicates are
suspended.
Source: DFSMSdfp
Detecting Module: IDCDA03
IDC01379I
NO VVDS ENTRY FOR DSCB NAME

dscbname
Explanation: A data set control block (DSCB) with no

matching VVDS entry was found.
dscbname
The DSCB name.
current command.
297
Source: DFSMSdfp
IDC01380I
GENERATION DATA SET FOUND IN

DEFERRED ROLL IN STATE
Explanation: It is an informational message only.

Comparison of GDs is deferred and roll in state and
catalog recording continues.
IDC01381I
VVR INTERRUPT RECOGNITION FLAG

FOUND ON FOR dsname
Explanation: During system processing, DIAGNOSE

found the interrupt recognition flag (IRF) on in the
VSAM volume record (VVR) for the specified data set.
The IRF was left on when data facility data set services
(DFDSS) was moving the subject data set and had not
completed the operation.
dsname
current command.
Application Programmer Response: Because the
VVR may not correctly describe the extent of the data
set, do the following:
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.
dsname
The data set name.
the next base object.
Application Programmer Response: Another
message will give the name of the object and the
reason it could not be defined. Correct this problem.
Run the job again.
Source: DFSMSdfp
IDC01408I
DATA SPACES TO BE DELETED FOR

VOLUME volser
Explanation: During processing of a CNVTCAT

command, suballocated entries in a virtual storage
access method (VSAM) catalog have been found. The
specified volumes VSAM data spaces will be deleted to
allow conversion. Unless an error message follows this
message indicating the delete failed, the data spaces
will have been deleted.
1. Copy the data set to a new data set.
volser
2. Verify the correct number of records were copied.

3. Delete the old data set.
System Action: The system continues processing if

the delete of the volumes 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
IDC01402I
IDC1412I
SPHERE CONVERSION COMPLETED

FOR dsname
Explanation: The conversion of the specified base

sphere and its associations has completed successfully.
dsname
The data set name.
IDC01407I
SPHERE BACKED OUT OF TARGET

CATALOG FOR dsname
Explanation: The specified sphere base and any of its

associations defined in the target catalog have been
deleted from the target catalog. The reason for this
298
TRACE ALREADY IN REQUESTED

STATE
Explanation: The hardware trace is already in the

requested state. The Mass Storage System
Communicator reason code is X'7F'.
System Action: The command completes normally.
Source: DFSMSdfp
IDC01460I
Source: DFSMSdfp
THE NUMBER OF ENTRIES MERGED

WAS nnn
Explanation: The number of entries merged from the

source catalog to the target catalog is specified. This
count does not include data or index components.
nnn
The number of entries merged.
Source: DFSMSdfp
IDC01500I
{BIND | UNBIND} SUCCESSFUL FOR

(SUBSYSTEM CONTAINING) volser
Explanation: The data was successfully bound or

unbound for the device specified or unbound for the
subsystem.
System Action: The ALTER command continues

processing with a condition code of 4, altering any
parameters other than KEYS and RECORDSIZE.
Incorrect key values also prevent alteration of record
size values in the same command.
Application Programmer Response: If the default
values are not correct, run an ALTER command to
correct the values.
System Action: The system performed the I/O

operation without error.

Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCSS03
IDC1502I
IDC1544I
volser
PASSWORD SUPPRESSION IN MODEL

OBJECT
Explanation: The password information in the model

object was inaccessible because there was insufficient
password protection authorization or RACF
authorization. This is an informational or attention
message that occurs if the password or RACF
authorization provided is not high enough to locate the
passwords themselves. The passwords were not used
for the object being defined.
The passwords are not modeled.
passwords are to be modeled, delete the data set.
Before redefining, either supply the MASTERPW
password of the model object or have your user profile
modified so you have RAC-alter access to the model
object.
KEYS AND/OR RECORDSIZE VALUES

EQUAL TO PRIOR NON-DEFAULT
VALUES
Explanation: The ALTER command specified the

KEYS or maximum RECORDSIZE parameter with
values equal to those already defined.
System Action: The ALTER command continues
processing with a condition code of 4, altering any
parameters other than KEYS and RECORDSIZE.
Incorrect key values also prevent alteration of record
size values in the same command.
Application Programmer Response: If the specified
values are not correct, run an ALTER command to
correct the values.
the job log for more information Search problem
Source: DFSMSdfp
Source: DFSMSdfp
IDC1543I
NEW KEYS AND/OR RECORDSIZE

VALUES EQUAL TO PRIOR DEFAULT
VALUES.

KEYS or maximum RECORDSIZE parameter with
values equal to the default values chosen by the
DEFINE command. The DEFINE defaults are KEYS (64
0) and RECORDSIZE (4089 4089) for non-spanned
record data sets or RECORDSIZE (4086 32600) for
spanned record data sets.
IDC01551I
type CACHING STATUS: stat FOR SD

Xss DEV Xdd
Explanation: This message is routed to the systems

console by the LISTDATA command in response to a
request for status with the WTO parameter.
type
Identifies the DASD type.
stat
Status, as follows:
v ACTIVE if the subsystem is active.
299
v SUBSYSTEM ERROR if an I/O error

occurred when requesting status from the
subsystem and the model is not 3990 Model
3 or Model 6.
Operations and Recovery Guide for detailed recovery

actions.
v HOST TERMINATION if a SETCACHE

command has been previously issued to turn
off caching in the subsystem and the model
is not 3990 Model 3 or Model 6.
Detecting Module: IDCLA01
ss
The address of the subsystems caching

storage director.
dd
The channel connection address of the device

on which the I/O was done.
System Action: The system continues processing. A

full status report appears on SYSPRINT or in the
alternate data set described in the procedure used to
issue the LISTDATA command.
Source: DFSMSdfp
IDC01553I
Explanation: This 3990 Model 3 or Model 6 message

is routed to the systems console by the LISTDATA
command in response to a request for status with the
WTO parameter. This message might appear with
IDC01552I, IDC01554I, IDC01555I, and IDC01556I.
stat
v DEACTIVATED-SUBSYSTEM ERROR when

an internal subsystem error caused
nonvolatile storage termination.
Detecting Module: IDCBD0I
v DEACTIVATED-HOST/SF when an explicit

host system or support facility request
caused nonvolatile storage termination.
SUBSYSTEM CACHING STATUS:

stat-DEV Xddd
v DEACTIVATION IN PROGRESS when a

request for deactivation has been received
and the destage is in progress.

WTO parameter. This message might appear with
v DEACTIVATION FAILED when a request for

deactivation was received and the destage
failed.
stat
v ACTIVATION PENDING if the cache is being

brought online.
v DEACTIVATED-SUBSYS when an internal
subsystem error caused caching termination.
v DEACTIVATED-HOST/SF when an explicit
host system or support facility request
caused caching termination.
v DEACTIVATION PENDING when a request
for deactivation has been received and the
operation is in progress.
v DEACTIVATION FAILED when a request for
deactivation was received and the operation
failed. when the status is represented by an
undefined bit combination.
ddd
The device number on which the I/O operation

occurred.

Operator Response: If the device associated with this
message is attached via the IBM 3990 Model 3 or
Model 6 Storage Control, see IBM 3990/9390
300
v DISABLED when the nonvolatile storage is

disabled for maintenance.
Status, as follows:
v ACTIVE if the subsystem is active.
Status, as follows:
v ACTIVE if the nonvolatile storage is active.
Source: DFSMSdfp
IDC01552I
NVS STATUS: stat DEV Xddd
ddd

occurred.

actions.
Source: DFSMSdfp
IDC01554I
DASD FAST WRITE STATUS: stat DEV

ddd
Explanation: This 3990 model 3 message is routed to

the systems console by the LISTDATA command in
response to a request for status with the WTO
parameter. It may appear with IDC01552I, IDC01553I,
IDC01555I, or IDC01556I.
stat
Status, as follows:
v ACTIVE if DASD fast write is active.

v DEACTIVATION PENDING when transfer of
modified DASD fast write data to DASD
failed.
v DEACTIVATED when DASD fast write is
disabled. combination.
ddd

occurred.

actions.
Source: DFSMSdfp
IDC01556I
CACHE FAST WRITE STATUS: stat DEV

ddd
Explanation: This 3990 model 3 message is routed to

the systems console by the LISTDATA command in
response to a request for status with the WTO
parameter. It may appear with IDC01552I, IDC01553I,
IDC01554I, or IDC01555I.
stat
Status, as follows:
v ACTIVE if cache fast write is active.
v DISABLED if cache fast write is disabled.
ddd
The device address (370) on which the I/O

operation occurred.

Source: DFSMSdfp
IDC01555I
DUPLEX PAIR STATUS: stat {PRI | SEC}

DEV Xddd {pri|sec} DEV Xxx

WTO parameter when the device in the status request
is part of a duplex pair. This message might appear with
stat
Status, as follows:
v ACTIVE if the duplex pair is active.
v PENDING when the copy to establish a
duplex pair is in progress.
v SUSPENDED when the duplex pair is
suspended by a host command (for
example, SETCACHE SUSPENDPRIMARY),
or by the subsystem.
pri
Indicates that the addressed device is primary.
sec
Indicates that the addressed device is

secondary.
ddd

occurred.
xx
The channel connection address (CCA) of the

other device in the duplex pair returned in the
sense subsystem status data.

Source: DFSMSdfp
IDC01557I
ACCESS CODE FOR SCU Xscu SC

Xsc IS Xacode
Explanation: The LISTDATA command to retrieve the

remote access authorization code was successful. One
message is routed to the systems console for each
storage cluster.
scu
The box serial number.
sc
The 2 hexadecimal digit storage cluster

number.
acode
The 8 hexadecimal digit remote access code.

Source: DFSMSdfp
IDC1561I
WKSPC LACKING FOR dsname
Explanation: A larger region size is required for this

particular invocation of access method services and
LISTCAT.
dsname
The data set name.
System Action: The LISTCAT command bypasses the
indicated entry and continues processing with a
condition code of 4.
Application Programmer Response: Run the job
again in a larger region for those entries that were
bypassed.
301

Source: DFSMSdfp
Detecting Module: IDCLC02
IDC1562I
ser VOLUME SERIAL NUMBER TOO

LONG

specified entry and continues processing with a
again with the correct type or types specified.
Source: DFSMSdfp
Explanation: A volume serial number exceeds six

characters for the LISTCAT SPACE request.
IDC1566I
ser
Explanation: One of the following conditions is

present:

indicated entry and continues processing with a
again with the corrected volume serial numbers.
** xxx NOT LISTED
v An entry name specified in the LISTCAT ENTRIES

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
no entry types specified.
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
xxx
IDC1564I
chartyp IS AN UNKNOWN TYPE
Explanation: An entry returned from the catalog is a

type not supported by LISTCAT.
chartyp The unsupported type.

entry and continues processing with a condition code of
4.
Source: DFSMSdfp
The entry name.
System Action: The system bypasses the designated

entry. The system continues processing with a return
code of 4.
entry name. Return the job to list only this entry or refer
to the documentation for message IDC3009I and
respond as indicated for the specified return code and
reason code.
If the name should be in the virtual storage access
method (VSAM) volume data set (VVDS), run a PRINT
of the VVDS to verify the presence of the catalog name.
Source: DFSMSdfp
IDC1565I
xxx NOT A REQUESTED TYPE
Explanation: A desired entry was not among the types

requested.
xxx
302
The desired type.

IDC1567I
** INVALID CONTROL INTERVAL

NUMBER nnn
IDC1575I
ONLY {BACKUP|TARGET} DEFINES

{dsname|ser}
Explanation: An entry identified by a control interval

number in the virtual storage access method (VSAM)
catalog does not exist.
Explanation: This message indicates that either the

backup or target catalog does not contain the data set
or volume entry.
nnn
dsname
The incorrect control interval number.
System Action: The system bypasses the designated

entry. The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCLC01, IDCLC02
IDC1569I
EXPIRATION PARAMETER DOES NOT

APPLY TO ENTRY TYPE(S)
Explanation: The EXPIRATION option of LISTCAT

was specified with entry types that contain either no
expiration-date field or an expiration-date field that is
never initialized.
System Action: LISTCAT continues normally after the
attention message, processing the specified entry types.
The listing is not restricted by the EXPIRATION option.
All specified entry types will be listed.
Source: DFSMSdfp
IDC1574I
CATALOG ENTRY COMPARISON NO

LONGER FUNCTIONING
Explanation: This message follows the 100th

IDC1575I message. Comparison of the backup and
target catalog continues but only volume serial number
mismatches are listed.
System Action: The system continues reload
processing.
Application Programmer Response: The large
number of discrepancies detected between the target
and backup catalogs indicate that the reloaded catalog
should be used until the LISTCAT output obtained
before and after the reload has been carefully checked.
Source: DFSMSdfp
The data set name.
ser
System Action: The system continues reload

processing.
Application Programmer Response: Do one of the
following:
v If only the backup defines a data set, the physical
data for the data set probably does not exist on the
volumes indicated. Delete the catalog entry. Use the
DELETE NOERASE option, since the ERASE option
may affect other users data.
v If only the backup defines a volume, the volume is
probably no longer owned by this catalog. Delete any
data sets indicated as residing on this volume. Then
delete the volume.
v If only the target defines a virtual storage access
method (VSAM) data set, access to the data set has
been lost. Obtain and import (IMPORT command) a
backup copy of the data set (output from EXPORT).
v If only the target defines a non-VSAM data set or an
alias or generation data group (GDG), reestablish the
catalog entries with the DEFINE command.
v If only the target defines a volume, access has been
lost to the volume. It cannot be reused by VSAM until
the VSAM ownership and data space protection
attributes have been removed. Run access method
services ALTER REMOVE VOLUME.
Source: DFSMSdfp
IDC1595I
PASSWORDS SUPPRESSED FOR THE

EXPORTED DATA SET
Explanation: The password and other protection

information was inaccessible due to insufficient
password or RACF authorization. The portable version
of the data set has been created, but without the
protection attributes.
When protection information is exported, it does not
include the RACF profile, the passwords, and other
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
303
or have your user profile modified so it indicates

RACF-alter access to the data set.
unit address makes the second cache storage director

accessible.
Source: DFSMSdfp
Operator Response: Contact hardware support.
Source: DFSMSdfp
IDC1597I
THE text PARAMETER IS INVALID FOR

AN ICF CATALOG

INHIBITSOURCE
INHIBITTARGET
PERMANENT
IDC01605I
STORAGE DIRECTOR Xyy SET {ON |

OFF}, PREVIOUSLY {ON | OFF}
Explanation: The SETCACHE command to set the

storage director on or off completed successfully.
An integrated catalog facility (ICF) catalog is to be

exported and INHIBITSOURCE or INHIBITTARGET was
specified or PERMANENT was specified or defaulted.
These parameters are incorrect when exporting an ICF
catalog.
yy
Indicates the address of the storage director.
System Action: The system sets the return code to 0.

Source: DFSMSdfp

parameter. The system exports the object.
Detecting Module: IDCSC0I
Application Programmer Response: If an ICF

catalog is being exported, do not specify
INHIBITSOURCE or INHIBITTARGET and specify
TEMPORARY.
IDC1631I

Source: DFSMSdfp
IDC01600I
CACHING SET {ON | OFF} FOR

(SUBSYSTEM CONTAINING) volser.
Explanation: The I/O operation to set the cache on or

off completed successfully.
volser
System Action: the system sets the return code to 0.
DUPLICATE SYS1. DATA SET NAME

IN TARGET CATALOG
Explanation: A duplicate SYS1. data set entry was

found in the virtual storage access method (VSAM) or
integrated catalog facility (ICF) catalog while attempting
to convert an OS catalog entry.
System Action: An accompanying message identifies
the entry not converted. The system does not convert
the entry.
Application Programmer Response: If duplicates
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
command.
Source: DFSMSdfp
Source: DFSMSdfp
CVOL POINTER xxx TO VOLUME ser
NOT CONVERTED
IDC1632I
IDC01603I
Explanation: The control volume (CVOL) name was

not converted to an alias entry in the virtual storage
access method (VSAM) or integrated catalog facility
(ICF) master catalog because the CVOLEQUATES
parameter was not specified, or was specified but the
CVOL volume serial number in the CVOL pointer entry
was not the one specified in the parameter.
EQUIPMENT CHECK ON FIRST UNIT

ADDRESS, SECOND ADDRESS
ACCESSED
Explanation: An I/O operation received an equipment

check on the first unit address because the first cache
storage director could not access the second cache
storage director in the subsystem.
System Action: The system starts a second I/O
operation using the second unit address. The second
304
xxx
The CVOL pointer.
ser
System Action: The system does not convert the

entry.
DEFINE ALIAS command to create an alias entry in the
master catalog.
Source: DFSMSdfp
IDC1638I
ALIASES OF GENERATION INDEX

POINTER ENTRIES ARE NOT
CONVERTED
Explanation: An alias name of an OS catalog

generation index pointer entry (GIPE) was encountered.
Because aliases of virtual storage access method
(VSAM) or integrated catalog facility (ICF) catalog
generation data group (GDG) base entries are not
allowed, the GIPE alias name is not converted.
System Action: The system does not convert the
entry.
Application Programmer Response: After the

alternate index is built, delete the short record. Rewrite
a long enough record through a user program with the
alternate index as part of the upgrade set. The alternate
index will be upgraded to reflect this particular base
record.
Source: DFSMSdfp
IDC1645I
NONUNIQUE AIX KEY key PRIME

{KEY|RBA} IS xxx
Explanation: The alternate index being built was

defined with the UNIQUEKEY attribute. That is, the
alternate key exists on only one base cluster record.
However, multiple occurrences of the same alternate
key have been encountered. The system writes this
message for each multiple occurrence. The message
gives the alternate key first, up to a maximum of the
first ten bytes, expressed in hexadecimal.
If the base cluster is a key-sequenced data set, the
specified record is the prime key (up to a maximum of
the first ten bytes) expressed in hexadecimal.

If the base cluster is an entry-sequenced data set, the

specified record is the prime relative block address
(RBA) in decimal.
key
Indicates the nonunique key.
Source: DFSMSdfp
xxx
Indicates the prime key.
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
be reflected in the alternate index record.
IDC1644I
ALTERNATE INDEX KEY NOT IN BASE

RECORD xxx
Explanation: The base cluster record is not long

enough to contain the entire alternate key. If the base
cluster is a key-sequenced data set, the specified
record is the key of the short base cluster record (up to
a maximum of the first ten bytes) expressed in
hexadecimal.
If the base cluster is an entry-sequenced data set, the
specified record is the relative block address (RBA) of
the short base cluster record, given in decimal.
xxx
Indicates the base cluster record.
System Action: The system bypasses the base

cluster record. The record will not be reflected in the
alternate index being built. See the subsequent
message for the name of the alternate index.

UNIQUEKEY attribute was correctly specified, then the
base cluster is in error. Correct it through a calling
program
If the UNIQUEKEY attribute was incorrectly specified:
v and the alternate index was defined with the REUSE
parameter, change it to NONUNIQUEKEY using the
access method services ALTER command.
v and the alternate index was defined with the REUSE
parameter, change it to NONUNIQUEKEY using the
access method services ALTER command.
v and the alternate index was not defined with the
REUSE attribute, delete the alternate index and
redefine it with the NONUNIQUEKEY attribute.
305
Then rebuild the alternate index using the BLDINDEX

Command.
Source: DFSMSdfp
IDC1646I
nnnnn EXCESS PRIME {KEY|RBL}

VALUES FOR AIX KEY key
Explanation: The specified key is the key of an

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.
nnnnn
The number of pointers that could not fit into

the record. The name of the alternate index
being built is given in a subsequent message.
key
Indicates the key.
dsname
The data set name.
System Action: The building of the alternate index is
complete.
Application Programmer Response: Refer to the
action outlined for the individual errors.
Source: DFSMSdfp
IDC01653I
ALIASES FROM THE PORTABLE DATA

SET WERE DEFINED
Explanation: The names that follow this message are

aliases from the portable data set; they have been
defined for the integrated catalog facility catalog being
imported.
System Action: The alternate index record is created

with only those pointers that could fit.
System Action: Processing continues with the aliases

defined and listed.
Application Programmer Response: Delete the

alternate index and redefine it using the access method
services commands with a maximum record size long
enough to contain the maximum number of pointers for
any one alternate key. Then rebuild the alternate index
using the BLDINDEX command.

Source: DFSMSdfp
Source: DFSMSdfp
IDC01654I
ALIASES FROM THE PORTABLE DATA

SET WERE NOT DEFINED
Explanation: The names that follow this message are

aliases from the portable data set; they have not been
defined for the integrated catalog facility catalog being
imported.
System Action: Processing continues with the aliases
listed.
IDC1653I
dsname BUILT WITH ERRORS
Explanation: Building of the alternate index has been

completed but some non-ending errors were
encountered. Non-ending errors consist of:
v Alternate index key not contained in one or more
base cluster records.
v Multiple occurrences of one or more alternate keys
for an alternate index defined with the UNIQUEKEY
attribute.
Source: DFSMSdfp
IDC01657I
OBJECT WAS SMS-MANAGED WHEN

EXPORTED. CHANGED TO
UNMANAGED.
v One or more alternate index records too short to

contain all the prime key or RBA pointers.
Explanation: The object of an IMPORT command was

SMS managed when it was exported to the portable
data set. After processing of the IMPORT command, the
object became unmanaged.
All non-ending errors for this alternate index have been

identified in messages that precede this message.
System Action: The object is imported to unmanaged

storage.
Source: DFSMSdfp
306

IDC1661I
OUT-OF-SYNC DATA SET

SUCCESSFULLY EXPORTED (BY
FORCE)
Explanation: The portable data set contains the

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
stamps or space information. See the secondary
message for the data set name.
Source: DFSMSdfp
IDC1662I
OUT-OF-SYNC DATA SET NOT

EXPORTED

(VSAM) data set named in the message that follows is
out of synchronization and the FORCE parameter was
not specified. The out-of-synchronization is caused by a
mismatch of the space information.
System Action: The system bypasses processing of
the VSAM data set.
Application Programmer Response: If the data set,
with its possible problems, is desired, then specify the
FORCE parameter on the EXPORTRA command. Run
the job again.
Source: DFSMSdfp
IDC1663I
BYPASSED RELATION dsname
IDC1664I
ASSOCIATION ERROR, dsname
Explanation: The named catalog entry described a

generation data set having no relationship to any
OS/VS2 generation data group, or the entry describes a
non-VSAM data set containing other than an OS/VS
alias related to it.
dsname
The data set name.
System Action: The association cannot be processed.
The system continues processing of the named object.
Application Programmer Response: List the named
object after performing an IMPORTRA operation to
determine missing related objects and to redefine the
related objects.
Source: DFSMSdfp
IDC1667I
VOLUME volser1 IS OUT-OF-SYNC AND

LATER THAN VOLUME volser2
Explanation: The data-set-directory-entry time stamp

mismatches the time stamp for the virtual storage
access method (VSAM) data set named in the following
message. The volumes are out of synchronization,
although some of the data sets may still be recoverable.
ser1
ser2
The volume serial numbers that indicate the

volumes that are out of synchronization.
System Action: The system bypasses the VSAM data

set entry and associations.
Explanation: An error occurred or a catalog entry

could not be located for a path or an alternate index to
a virtual storage access method (VSAM) cluster, an
OS/VS alias for a non-VSAM object, or a non-VSAM
object associated with an OS/VS2 generation data
group.
Application Programmer Response: Get the two

volumes in synchronization. Run the job again.
IDC1678I
dsname
Source: DFSMSdfp
** DATA SET EXPORTED WITH MINOR
ERRORS
The name of the cluster, non-VSAM object, or

generation data group (GDG).
Explanation: An error occurred while processing an

associated object for an object being exported.
System Action: The system bypasses the related

object. The system continues processing of the named
object.

the associated object.
Application Programmer Response: List the named

object after performing an IMPORTRA operation to
determine missing related objects and to redefine the
related objects.
Source: DFSMSdfp

preceding message to determine the type of error and
the recovery procedure.
Source: DFSMSdfp

307
IDC1679I
** OUT-OF-SYNC DATA SET

EXPORTED WITH MINOR ERRORS

associated object for an out-of-synchronization data set.
The out-of-synchronization is caused by a mismatch
between the time stamps or space information on the
various volumes of a multi-volume data set.
size
Indicates the control interval size.
Source: DFSMSdfp
IDC01705I
CONTROL AREA SIZE IS size
Explanation: This message displays the control area

size in decimal.

the associated object.

preceding message to determine the type of error and
the recovery procedure.
Source: DFSMSdfp
Source: DFSMSdfp
size
Indicates the control area size.
IDC01706I
RBA IS rba
Explanation: This message displays a relative byte

address (RBA) in decimal.
IDC01700I
INDEXTEST BEGINS
Explanation: The INDEXTEST diagnostic procedure is

beginning to process.
System Action: The system begins processing.
rba
Indicates the relative byte address.
Source: DFSMSdfp
IDC1707I
Source: DFSMSdfp
IDC01701I
DATATEST BEGINS
Explanation: The DATATEST diagnostic procedure is

beginning to process.
System Action: The system begins processing.
Source: DFSMSdfp
** OWNER ownerid NOT UPDATED IN

INVENTORY FOR NEW COPY yyddd
Explanation: The owner data in the volume label of

the new copy volume, created on the specified date,
could not be updated in the copy volume record or in
the cartridge labels.
This condition occurred because the cartridges of an
existing copy volume were reused. See the preceding
message for further explanation of the problem.
IDC01702I
HIGH-USED RBA IS rba
Explanation: This message displays the component

high-used relative byte address (RBA) in decimal.
rba
Indicates the high-used relative byte address.
Source: DFSMSdfp
IDC01703I
HIGH-ALLOCATED RBA IS rba
Explanation: This message displays the component

high-allocated relative byte address (RBA) in decimal.
rba
Indicates the high-allocated relative byte

address.
Source: DFSMSdfp
IDC01704I
CONTROL INTERVAL SIZE IS size
Explanation: This message displays the control

interval size in decimal.
308
ownerid
Indicates the owner of the data.
yyddd

Application Programmer Response: This
discrepancy cannot be corrected. The LISTMSVI reports
will reflect different owners for the source volume and
the designated copy volume, even though the owner
data is correct in the volume labels of both volumes.
Source: DFSMSdfp
IDC01707I
CURRENT INDEX LEVEL IS level
Explanation: This message displays the level of the

index being processed when an error is detected.
level
Indicates the current index level.
Source: DFSMSdfp
IDC01708I
nnn CONTROL INTERVALS

ENCOUNTERED
Explanation: This message indicates the total number

of control intervals read.
nnn
The number of control intervals.

Source: DFSMSdfp
System Action: The system concludes processing

normally.
Source: DFSMSdfp
IDC01713I
DATA CONTROL INTERVAL DISPLAY

AT RBA rba FOLLOWS
Explanation: This message displays the relative byte

address (RBA) in decimal of the control interval. The
control interval display follows.
IDC01709I
DATATEST COMPLETE - NO ERRORS

DETECTED
Explanation: The entire data component has been

tested and no errors have been found.
normally.
Source: DFSMSdfp
rba
The relative byte address.
Source: DFSMSdfp
IDC01714I
ERROR LOCATED AT OFFSET offset
Explanation: This message follows a control interval

display and specifies the location in hexadecimal of the
item in error.
IDC01710I
DATA COMPONENT CONTAINS nnn

RECORDS
Explanation: After DATATEST concludes, this

message displays the number of records contained in
the data set.
nnn
The number of records.

normally.
Source: DFSMSdfp
offset
The offset.
Source: DFSMSdfp
IDC01716I
INDEX KEY FOLLOWS
Explanation: The key value follows this message.

Where applicable, two key values follow.
Source: DFSMSdfp
IDC01717I
DATA KEY FOLLOWS
Explanation: The key display follows this message.

IDC01711I
DATA COMPONENT CONTAINS nnn

DELETED CONTROL INTERVALS

message displays the number of unreclaimed empty
control intervals.
nnn
The number of control intervals.

normally.
Source: DFSMSdfp
IDC01712I
MAXIMUM LENGTH DATA RECORD

CONTAINS nnn BYTES

message displays the length in decimal of the longest
data record encountered.
Source: DFSMSdfp
IDC01718I
RECORD UPDATE NUMBER IS number
Explanation: This message displays the expected

update number of the spanned record segment.
number The number of the record update.

Source: DFSMSdfp
IDC01720I
INDEX CONTROL INTERVAL DISPLAY

AT RBA rba FOLLOWS
Explanation: This message displays the relative byte

address (RBA) in decimal of the control interval. The
control interval display follows.
rba
nnn
Source: DFSMSdfp
The number of bytes.
309
IDC01722I
nnn PERCENT FREE SPACE

message displays the percentage of free space in the
data set.
nnn
rba
Source: DFSMSdfp
IDC1742I
The percentage of available space.
Source: DFSMSdfp
IDC01723I
ERRORS MAY BE DUE TO

CONCURRENT ACCESS
Explanation: The catalog OPEN indicator or AMDSB

indicates that the data set may have been updated
during EXAMINE testing. Some or all of the detected
errors may not exist.
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
processing.
RECATALOG OPTION INVALID FOR

VOLUME
Explanation: The source volume is not owned by a

virtual storage access method (VSAM) catalog.
Therefore, the VSAMCATALOG option does not apply.
System Action: No recataloging is performed. The
command continues processing.
IEHPROGM utility or the access method services
DELETE and DEFINE commands to recatalog data
sets.
Source: DFSMSdfp
IDC01724I
INDEXTEST COMPLETE - NO ERRORS

DETECTED
Explanation: The entire index component has been

tested and no errors have been found.
normally.
Application Programmer Response: Run DATATEST
to validate the data component.
Source: DFSMSdfp

IDC1784I
NO SCRATCH CARTRIDGES FOUND IN

MSF
Explanation: No scratch cartridges can be ejected

from the Mass Storage Facility (MSF) because there are
no cartridges in the MSF.
a message.
Source: DFSMSdfp
IDC01725I
REFER TO DATA CONTROL INTERVAL

DISPLAY FOR RBA rba
Explanation: This message is issued in lieu of

message IDC01713I when an error is detected in a
previously-displayed data control interval. This message
displays the relative byte address (RBA) in decimal of
the data control interval.
rba
Source: DFSMSdfp
IDC01726I
REFER TO INDEX CONTROL INTERVAL

DISPLAY FOR RBA rba
Explanation: This message is issued in lieu of

message IDC01720I when an error is detected in a
previously-displayed index control interval. This
message displays the relative byte address (RBA) in
decimal of the index control interval.
310

IDC01806I
NO VOLUMES WERE SELECTED TO

BE PROCESSED
Explanation: The volumes specified in the volumes

parameter or resolved from the storage group
parameter do not exist on the system or are not
available for processing.
Application Programmer Response: Ensure that the
specified volumes exist and are on line.
Source: DFSMSdfp
IDC01811I
NUMBER OF n RECORDS PROCESSED

WAS xxxx
IDC01850I
SORT PRODUCT CALL

IDENTIFICATION NUMBER xxxx
Explanation: xxxx represents the identification number

of a call to DFSORT (or an equivalent product) by
BLDINDEX. This identification number corresponds to
the call identifier in DFSORT message ICE200I (or to
the identifier in the appropriate message for an
equivalent product).
The type of record written.
xxxx
The number of records written.
Explanation: Indicates the number of n-type records

written to the output data set.
Source: DFSMSdfp
IDC01851I
IDC1840I
TRACE AREA EMPTY - NO DATA

DUMPED
Explanation: An attempt was made to dump trace

data but the trace areas requested were null.
Application Programmer Response: Turn the trace
on before requesting a dump.
Source: DFSMSdfp
NOSORTCALL invalid parameter for

extended addressability data set.
Explanation: User must use SORTCALL parameter in

BLDINDEX command for building alternate indexes for
extended addressability data sets.
System Action: Processing for the BLDINDEX
STEP/JOB Terminated.
Application Programmer Response: Specify sortcall
parameter on the BLDINDEX command to build
alternate indexes for extended addressability data set.
System Programmer Response: IDCBI01
Source: DFSMSdfp
IDC1860I
SELECTED CHECKID, xxxxxxxx NOT

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

BE DETERMINED - ALL DATA DUMPED
Explanation: An attempt was made to dump only

current trace data, but the end of the current data was
not found. Therefore, all of the trace data was dumped.
There may be data from a previous trace period in the
output data set.
System Action: The command dumped all the data in
the requested trace area.
Application Programmer Response: Run the trace
report program and select only the data from the current
trace period for processing.
xxxxxxxx
The check identification.
System Action: The system continues processing, but
the CHECKID is not processed.
checkid spelling, and that the correct checkpoint data
set was used.
Source: DFSMSdfp
Source: DFSMSdfp
311
IDC1864I
NO CHECKPOINTS FOUND ON DATA

SET
Explanation: No CHR records were found on the

checkpoint data set.
System Action: The system abnormally ends
CHKLIST.
Application Programmer Response: Verify that the
correct checkpoint data set was used, then resubmit
job.
Source: DFSMSdfp
IDC1865I
xxxxxxxx ADDITIONAL VOLUME

SERIAL NOT FOUND IN CHKPT DATA
SET

Source: DFSMSdfp
IDC1867I
CURRENT VOLUME NOT FOUND

xxxxxxxx
Explanation: The volume sequence number exceeded

the number of volumes for the indicated ddname.
xxxxxxxx
The ddname.
Application Programmer Response: Keep all related
data sets and listings for reference.
Explanation: Probable checkpoint logic error. A type 1

or type 2 DSDR indicated the presence of a type 2
DSDR which did not exist.

for the job.
Source: DFSMSdfp
xxxxxxxx

The additional volume serial number.
System Action: Incomplete CHKLIST information is

listed. The system continues processing with the next
checkpoint entry.
data sets and listing for reference.
Source: DFSMSdfp
IDC1866I
UNEXPECTED EOF ON CHECKPOINT

DATA SET
IDC1870I
** IGNORED VSAM ERROR READING

CRA - CI nnX
Explanation: A LISTCRA function encountered an I/O

error reading a catalog recovery area (CRA) record at
the specified control interval.
nn
The control interval number in hexadecimal.
System Action: The system ignores the record. The

system continues processing as long as no more than
50 errors have been encountered while processing the
LISTCRA command. When the number of errors
reaches 50, the system ends processing.
preceding message to determine the cause of the I/O
error. Correct the problem. Run the job again.
Source: DFSMSdfp
Explanation: End-of-file occurred while processing

DSDRs.
Detecting Module: IDCLR01, IDCCK01

CHKLIST utility.
IDC1871I

data sets and listings for reference.
312
** IGNORED VSAM ERROR READING

CATALOG - CI nnX
Explanation: A LISTCRA function encountered an I/O

error reading a catalog record at the specified control
interval.
nn
The control interval number in hexadecimal.
System Action: The system ignores the record. The

system continues processing as long as no more than
50 errors have been encountered while processing the
LISTCRA command. When the number of errors
reaches 50, the system ends processing.
The following list identifies each LISTCRA procedure

and the field for which it was searching when it
encountered the error:
CATOPEN
The catalog name in the cluster

record of the catalog.
CKEYRNG
The high key value in a given catalog

recovery area (CRA) record.
CRAOPEN
Either the owning catalog name or the

volume serial number in the CRA.
CTTBLD
The entry type of the catalog CI in the

CRA record.
Detecting Module: IDCLR01, IDCLR02
GETPRT
The entry type or the entry name in

the CRA record.
IDC1875I
INTASOC
The associated entry type or entry

name fields in the CRA records.
INTSORT
The name in a given CRA record.
INTVEXT
The extension pointer in a given CRA

record.
PRTCMP
The used length field in a given CRA

record.
PRTDMP
The used length field in a given CRA

record.
PRTOJVL
The volume information of high key

value in a given CRA record.
PRTVOL
The volume time stamp information in

a given catalog or CRA record.

preceding message to determine the cause of the I/O
error. Correct the problem. Run the job again.
Source: DFSMSdfp
ERROR TRANSLATING CRA CI FROM

CATALOG CI - nnX
Explanation: An error occurred when translating an

entrys catalog control interval number, which points at a
related entry, to a catalog recovery area (CRA) control
interval before reading the entry.
nn
The catalog control interval number in

hexadecimal.
This will normally result from an incomplete entry

definition or an I/O error identified in a preceding
message.
System Action: The system bypasses the error. The
system continues processing. However, there may be
minor errors in the list.
Application Programmer Response: Restore the
volume on which the error occurred to a previous valid
condition.

system continues processing. There may be minor
errors in the list.
condition.
Source: DFSMSdfp

Source: DFSMSdfp
IDC1878I
xxxxxxxx IGNORED ERROR FROM

FIELD MANAGEMENT
Explanation: An error occurred when called by

LISTCRA.
xxxxxxxx
The LISTCRA procedure in control when the
error was detected.
IDC1880I
IGNORED I/O ERROR READING

VOLUME LABEL
Explanation: A LISTCRA command encountered an

I/O error reading the format-4 data set control block
(DSCB) in the VTOC to obtain the time stamp
information.
System Action: The system ignores the error. The
system does not print the time stamps.
313

Source: DFSMSdfp
IDC01884I
UNBOUND LOCKS DELETED FOR

dsname
Explanation: A SHCDS FRDELETEUNBOUNDLOCKS

command was executed for data set dsname. Locks
being retained for the data set have been removed.
Source: DFSMSdfp
IDC1881I
IGNORED OPEN FAILURE FOR

ALTERNATE OUTPUT DATA SET
Explanation: LISTCRA encountered an error

attempting to open the alternate output data set.
system uses the output data set.
Application Programmer Response: If the output is
desired in the alternate data set, determine the cause of
the error. Correct the error. Run the job again.
Source: DFSMSdfp
IDC01880I
RECOVERY SET FOR dsname
Explanation: A SHCDS FRSETRR command was

executed for data set dsname.
Source: DFSMSdfp
Detecting Module: IDCSH11

IDC01885I
NON-RLS UPDATE PERMITTED FOR

dsname
Explanation: The data set that has been accessed in

RLS mode is now permitted to be accessed in non-RLS
mode.
Source: DFSMSdfp
IDC01886I
NON-RLS UPDATE DENIED FOR

dsname

non-RLS mode is now denied access in non-RLS mode.
Source: DFSMSdfp

IDC01887I
IDC01881I
UNBIND SET FOR dsname
Explanation: A SHCDS FRUNBIND command was

executed for data set dsname. The locks for the data
set have been unbound or disconnected from the data
set.
Source: DFSMSdfp
IDC01882I
BIND SET FOR dsname
Explanation: A SHCDS FRBIND command was

executed for data set dsname. The locks for the data
set have been bound or connected to the data set.
Source: DFSMSdfp
IDC01883I
RECOVERY RESET FOR dsname
Explanation: A SHCDS FRRESETRR command was

executed for data set dsname.
Source: DFSMSdfp
SUBSYSTEM subsystem REMOVED
Explanation: The subsystem with connections

remaining for RLS is removed. All lock and subsystem
connectivity information is deleted.
Source: DFSMSdfp
IDC1885I
CRA RECORD COULD NOT BE READ

BY FIELD MANAGEMENT
Explanation: The Data Facility Product (DFP) called

by LISTCRA to read catalog recovery area (CRA) fields
for the miscompare list was unable to return the
requested field. This message normally results from an
I/O error identified in the preceding message.
system continues processing. There may be minor
errors in the list.
condition. Contact your programming support personnel
and make sure the job stream and system output
associated with this job is available for problem
determination. LRPM is the last access method services
diagnostic dump point before the error was detected.
314


command.
Source: DFSMSdfp


IDC1887I
ERROR REFERENCING CRA ON

VOLUME ser - REASON CODE cde
Explanation: In opening the catalog recovery area

(CRA) there was a problem indicated by the reason
code.
ser
cde
The reason code, as follows:

Code
Explanation
Time stamp for volume was not

obtained.

IDC01895I
DATA SETS SUCCESSFULLY

PROCESSED
Explanation: An SHCDS CFREPAIR or CFRESET

command was issued. The list of datasets successfully
processed is presented.
Source: DFSMSdfp
Detecting Module: IDCSH15, IDCSH16
I/O error reading the CRA record.

requires no action, but the problem causing it may
cause other messages that may require a response.
Source: DFSMSdfp
IDC1890I
Source: DFSMSdfp
RACF PROFILE COULD NOT BE

DELETED NOT ELIGIBLE
Explanation: As the result of a DELETE or EXPORT

command, a RACF indicated member was successfully
deleted. However, the RACF profile for this data set is
not eligible for deletion for one of these reasons:
v RACDEF was failed by the installation exit.
v The resource name in the profile was not previously
defined to RACF.
command.
Source: DFSMSdfp
IDC1927I
INVALID MARGINS VALUES

SPECIFIED, DEFAULT MARGINS
ASSUMED
Explanation: The left margin value specified in a

MARGINS parameter is not strictly less than the right
margin value. At least two character positions must be
provided.
System Action: The system assumes the default
margin values of 2 and 72.
MARGINS specifications.
Source: DFSMSdfp
Detecting Module: IDCPM01
IDC1968I
VSAM TIME STAMP NOT UPDATED IN

VTOC OF {FROM|TO} VOLUME volser
Explanation: An error was encountered reading or

updating the volume table of contents (VTOC) so the
virtual storage access method (VSAM) time stamp was
not updated for the volume.
IDC1891I
RACF PROFILE COULD NOT BE

DELETED NOT FOUND
Explanation: As the result of a DELETE or EXPORT

command, a RACF indicated member was successfully
deleted. However, the RACF profile for this data set
could not be found.
FROM|TO
Indicate which value encountered the error for
commands that process more than one value.
volser
System Action: The command ends normally if no
315
functions have been performed yet. If some functions

have been performed, the command continues
processing.
again if the job was not completed. If the function
completed, use the SPZAP service aid to correct the
VSAM time stamp or ignore the error.
catname
The Catalog being deleted.
Operator Response: Reply Y to delete or N to
cancel the command.
System Programmer Response: To eliminate the
issuance of the WTOR see the Modify Catalog
command in MVS/ESA SYSTEM COMMANDS or the
DFSMS/MVS MANAGING CATALOG books.
Source: DFSMSdfp
IDC1998I
Source: DFSMSdfp
vvdsname AND ITS VVRS AND NVRS

ARE ABOUT TO BE DELETED REPLY
Y TO DELETE N TO CANCEL.
Explanation: This message is an attention that a

VVDS is about to be deleted.
IDC1969I
ALTERNATE TRACK DATA NOT

RESTORED IN VTOC OF TO VOLUME
volser
Explanation: An error was encountered reading or

updating the volume table contents (VTOC) so the
alternate track information was not restored in the
VTOC of the target volume after the copy of data. A
previous message explains the error.
volser

a Mass Storage Volume, ignore this error since
alternate tracks do not apply for Mass Storage Volumes.
If the volume is a real volume, use the AMASPZAP
service aid to place the information from the subsequent
message into the VTOC.
Source: DFSMSdfp
IDC1997I
catname AND ITS DATA SETS TO BE

DELETED, REPLY Y TO DELETE N
TO CANCEL.
vvdsname
The VVDS being deleted.
Operator Response: Reply Y to delete, or N to
cancel the command.
System Programmer Response: To eliminate the
issuance of the WTOR see the Modify Catalog
command in MVS/ESA SYSTEM COMMANDS or the
DFSMS/MVS MANAGING CATALOG books.
Source: DFSMSdfp
IDC2011I
FUNCTION CANNOT BE EXECUTED.

INSUFFICIENT MAIN STORAGE.
Explanation: An access method services function has

been requested that requires more virtual storage than
was available. Reasons for this message being issued
by the utility include the attempt to get storage by:
v IDCSS01 to build the output buffer.
v IDCSS02 to add to the work area, or for storage for
the SSSCB.
v IDCSS05 to obtain pinned track or dsname areas, or
for storage for the SSSCB.
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).
System Action: The function requested was not
performed.
Explanation: This message is an attention that a

Catalog is about to be deleted.

again in a larger address space.

316

for the job.
Source: DFSMSdfp
Detecting Module: IDCLM01
IDC2054I
INVALID AUTHORIZATION TO
EXECUTE FUNCTION
Explanation: A caller without the proper RACF facility

class authorization requested a function that involves a
storage management subsystem data set.
IDC2035I
INVALID ERROR CONVERSION TABLE
Explanation: An error was detected in the information

transmitted in the Error Conversion Table, when
attempting to convert a numeric error code to a prose
message.
System Action: The conversion request is ended.
Source: DFSMSdfp
Detecting Module: IDCTP06
IDC2053I
STEP CONTAINING JOBCAT/STEPCAT

REFERENCES SMS-MANAGED DATA
SET
Explanation: A step that referenced an SMS-managed

data set contains one of the following:
v a JOBCAT DD statement
v a STEPCAT DD statement
v both a JOBCAT and a STEPCAT DD statement
System Action: The system voids the step action for
the SMS-managed data set.
Application Programmer Response: Depending on
the DD statements present in the step, take one of the
following corrective actions:
v Remove the JOBCAT DD statement if there is no
need for it.
v Remove the JOBCAT DD statement, and insert
STEPCAT DD statements only where required.
v Remove the STEPCAT DD statement if there is no
need for it.
v If a single step references one or more
SMS-managed data sets and still requires a
STEPCAT DD statement, split the step into two or
more steps such that those steps referencing any
SMS-managed data sets do not require a STEPCAT
DD statement.
v Ensure that all referenced integrated catalog facility
(ICF) catalogs are connected to the system master
catalog.
Source: DFSMSdfp
Application Programmer Response: Acquire the

proper RACF facility class authorization. Run the job
again.
Source: DFSMSdfp
IDC2055I
ERROR DURING RETRIEVAL OF

ALLOCATION MESSAGES - RETURN
CODE WAS returncode REASON CODE
WAS rsncode
Explanation: An error occurred during calls to

dynamic allocation error message processor program
(IEFDB476) to return allocation messages, with the
return code, reason code from IEFDB476.
returncode
The return code.
rsncode
The reason code.
System Action: The function terminates.

MVS Programming: Authorized Assembler Services
Guide for more explanation on the return code and
reason code from IEFDB476.
Source: DFSMSdfp
IDC2065I
** UNABLE TO CLEAR
SERIAL-MISMATCH FLAG FROM
INVENTORY RECORD
Explanation: A flag indicating a volume serial

mismatch between the cartridge labels and the volume
label for a Mass Storage Volume could not be cleared
from the Inventory data set. See the previous message
for further explanation of the problem.
System Action: The command ends with an error
message.
problem as identified in the previous message and take
the following actions for the command that failed:
v For a Rename operation failure for ADDV run ADDV
rename operation.
317

mounting.
and that serial number nnnnnn is recorded in
v For a Rename operation failure for MODIFYV,
recover from the failure by:
Running ADDV to activate the volume if the
volume is merely inactive and has no volume
serial mismatch condition
Running ADDV to both activate the volume and
condition

Source: DFSMSdfp
IDC2074I
VOLUME ser NOT ACTIVE
Explanation: The specified volume is not active and is

recorded in the Inventory data set as inactive. The
command issuing the message requires an active
volume.
ser
System Action: Processing of the command ends

with a message indicating the final condition code.
Application Programmer Response: Run the ADDV
command to activate the volume. Run the command
again. If the volume is already active but only the record
indicates that the volume is inactive, contact the space
manager. The Inventory data set may need to be
restored from the backup copy and the Journal data set.
Source: DFSMSdfp
Detecting Module: IDCLD01
Run MODIFYV again to complete or retry the

mismatch condition
IDC2075I
Run STOREV to complete or retry the rename

operation if the volume is active and if a duplicate
volume serial number is desired as a result of the
rename.
Explanation: An attempt to make the specified volume

active and mountable failed. See preceding message
for further explanation of the failure.

volser
v For a Rename operation failure for STOREV run

318
** VOLUME volser CANNOT BE

ACTIVATED


message.
command again after:
v Reentering one or both cartridges if the cartridges are
outside the Mass Storage Facility (MSF)
v Correcting the problem as indicated in the preceding
message
v Running the EJECTV command to eject the volume

and then reentering the cartridges if the cartridges
were originally entered while the Mass Storage
Volume Control (MSVC) was disabled.
IDC2078I
** COPY RECORDS FOR VOL volser

CANNOT BE RETRIEVED
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.
Source: DFSMSdfp
volser
Detecting Module: IDCAV01, IDCCV01, IDCMV01
System Action: The command ends with a message.
IDC2076I
** CART csn1 [csn2] NOT IN MSF FOR

COPY yyddd

created on the indicated date cannot be found in the
Mass Storage Facility (MSF). See preceding message
for additional information.

error as indicated in the preceding message.
Source: DFSMSdfp
csn1
csn2
The cartridge serial numbers that identify the

sequence one and sequence two cartridges
not in the MSF.
yyddd
System Action: The command ends with a message

unless additional copies are specified for processing.
condition as indicated in the preceding message. Run
the command after:
v Reentering the missing cartridges
v Selecting another copy volume
v If one of the cartridges is lost, running the
SCRATCHV command to make the remaining
cartridge assigned to the volume scratch cartridge
and to delete the record from the Inventory data set
v Running the REMOVEVR command to delete the
record for the copy volume if both cartridges are lost
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCRV01, IDCSV01
Detecting Module: IDCCO01, IDCLV01, IDCRR01,

IDCSV01
IDC2079I
** RECORD FOR GROUP grpname

CANNOT BE RETRIEVED FROM
INVENTORY
Explanation: An attempt to access the record in the

Inventory data set for the specified group failed. See the
preceding message for further explanation of the failure.
grpname
The group name.
unless additional groups are specified for processing.
error as indicated in the preceding message. Verify that
the group name is specified correctly. Run the
command again.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCV01, IDCLC01,
IDCLV01, IDCMG01, IDCMV01, IDCSD01
319
IDC2080I
** RECORD FOR VOL volser CANNOT

BE RETRIEVED FROM INVENTORY
Explanation: An attempt to access the record in the

Inventory data set for the specified volume failed. See
the preceding message for further explanation of the
failure.
that one cartridge. See the preceding message for

further explanation of the failure.
csn1
csn2

not scratched.
yyddd
volser
System Action: The system sends messages about

the job to the job log.
error as indicated in the preceding message. Before
running the command again check that the volume
serial number is specified correctly.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCN01, IDCCO01,
IDCLD01, IDCLV01, IDCMG01, IDCMV01, IDCRL01,
IDCRR01, IDCRV01, IDCSD01, IDCSR01, IDCSV01
IDC2084I
** CARTRIDGES NOT EJECTED
Explanation: The cartridges assigned to a Mass

Storage Volume could not be ejected from the Mass
Storage Facility (MSF). If only one cartridge was in the
MSF, an attempt to eject that one cartridge failed. See
failure.
error as identified in the preceding message. Run the
command again.
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCEV01, IDCSR01
IDC2087I
** CART csn1 [csn2] NOT SCRATCHED

FOR COPY yyddd

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
320

problem as indicated in the preceding message. If the
cartridges are out of the MSF, enter the cartridges into
the MSF and run the command again. If the cartridges
are lost, run the REMOVEVR command to delete the
record for the copy from the Inventory data set. Run the
command again.
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCSV01
IDC2091I
** {READONLY|READWRITE}
ATTRIBUTE NOT SET FOR VOLUME
volser
Explanation: The specified volume could not be

assigned the READONLY or READWRITE attribute.
READONLY may be required because the volume
belongs to a group which has the READONLY attribute
specified for all general-use volumes. See the preceding
volser

MODIFYV command to change the volume attribute to
READONLY or READWRITE.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCV01, IDCMV01
IDC2093I
** VOLUME ATTRIBUTES NOT

CHANGED TO AGREE WITH GROUP
grpname
Explanation: An attempt to change the attributes of a

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.
See the preceding message for additional information
on the problem.
The following are valid attributes:
v bind/nobind
v exclusive/shared
v readonly/readwrite
v dasderase/nodasderase
v pagefault/nopagefault
grpname
The group name
LISTMSVI command to list the information recorded in
the Inventory data set about the group. After
determining the volume attributes specified at the group
level, run the MODIFYV command to update the volume
attributes to agree with the group specifications.
If there are many volumes in the group whose attributes
do not agree with the group, run the MODIFYG
command to request a change of the group attributes. If
you specify the same attributes on the MODIFYG
command as are recorded already in the group record,
MODIFYG will still change the attributes of all the active
general-use volumes for the group.
Source: DFSMSdfp
IDC2095I
{FROM|TO} VOLUME volser

INCOMPLETELY RENAMED IN A PRIOR
OPERATION
Explanation: The specified column cannot be used. A

previous MODIFYV, ADDV, or STOREV command
ended before completely changing the volume serial
number of the volume. The volume serial number on the
cartridge labels and in the Inventory record does not
agree with the volume serial number in the volume
label.
FROM|TO
Designate which volume is unusable for those
commands processing both a source and
target volume having the same volume serial
numbers.
volser

reflecting the severity of the error.
problem as identified in the preceding message and
take the following actions for the command that failed:
v For a Rename operation failure for ADDV, run ADDV
rename operation.
mounting. The values specified for the VOLUME and
number.
serial number as recorded in the cartridge labels and
the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number. Note that
the 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. This allows the original volume
serial number of a VSAM volume to be restored if the
volume is left partially renamed.
If ADDV, MODIFY, or STOREV terminates without
but also highlights the preceding volume and that
serial number nnnnnn is recorded in the volume label
of the volume.
v For a Rename operation failure for MODIFYV,
recover from a MODIFYV by:
condition
Running MODIFYV again to complete or retry the
mismatch condition
321
Running STOREV to complete or retry the rename

rename
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCLD01, IDCSD01,
IDCRV01, IDCEV01, IDCMG01, IDCMV01, IDCSR01,
IDCSV01, IDCCN01, IDCCO01
IDC2096I

INCOMPLETELY COPIED IN A PRIOR
OPERATION
Explanation: The specified volume was incompletely

copied by the COPYV, RECOVERV, or CONVERTV
commands and cannot be used.
FROM|TO
number.
volser
System Action: The command terminates with a

message containing the severity code.
problem as indicated in the preceding message. Then,
take one of the following actions for the command that
failed:
v For a Copy operation failure in COPYV, run COPYV
again to complete the copy operation to the
incomplete copy volume. COPYV will reuse the
cartridges of the incomplete copy volume for the new
copy. Or run SCRATCHV to scratch the incomplete
copy volume before rerunning the COPYV command.
IF COPYV ends without indicating the status of the
copy operation, LISTMSVI can be run to determine
whether the volume is flagged for recovery purposes.
If 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 a note that a copy operation failed
for the preceding copy volume.
v For a Copy operation failure for RECOVERV, run
RECOVERV again to complete the recover operation
322
to the target volume that is flagged as an incomplete

copy volume. Otherwise, run SCRATCHV to scratch
the target volume. The incomplete copy volume may
even be used as the target volume in the
CONVERTV command. In all cases, the empty
volume table of contents (VTOC) check or security
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
specify deferred mounting. If the RECOVERV
command is run again, the DD statement is not
required for the target volume, which is flagged as an
incomplete copy, unless the volume serial number of
the target volume is different from the source volume.
If a DD statement is provided for the target volume,
deferred mounting must be specified. If a VSAM
catalog is on the volume, a DD statement for the
catalog is not required; if provided, deferred mounting
must be specified.
If RECOVERV terminates without indicating the
status of the recover operation, LISTMSVI can be run
to determine 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 information for the volume but also
highlights the volume report with a note that a copy
operation failed for the preceding volume.
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
incomplete copy volume. Otherwise, run SCRATCHV
to scratch the target volume. The incomplete copy
volume may even by used as the target volume in
the RECOVERV command. In all cases, the empty
VTOC check or the security check for password
protected data sets is bypassed.
is not required for the incompletely copied volume
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
specify deferred mounting. If a VSAM catalog is on
the volume and a DD statement is provided for the
catalog, the DD statement must also specify deferred
mounting.
If CONVERTV ends without indicating the status of
the conversion operation, LISTMSVI can be run to
determine 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
highlights the volume report with a note that a copy
operation failed for the preceding volume.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCO01, IDCLD01,

IDCSD01, IDCSR01, IDCRV01, IDCEV01, IDCMG01,
IDCMV01, IDCCN01

error. Recatalog the data set using IEHPROGM utility or
the access method services DELETE and DEFINE
commands.
IDC2097I

INCOMPLETELY CREATED IN A PRIOR
OPERATION
Explanation: The specified volume was incompletely

created by the CREATEV command and could not be
used.
FROM|TO
number.
volser

Source: DFSMSdfp
IDC2101I

reflecting the severity of the error.
Application Programmer Response: Before creating
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
statement for the partially created volume. The empty
volume table of contents (VTOC) check is bypassed.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCLD01, IDCSD01,
IDCSR01, IDCRV01, IDCMG01, IDCMV01, IDCCN01,
IDCEV01, IDCCO01
IDC2100I
CATALOG RETURN CODE FOR

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
Catalog Management. The subsequent message
identifies the data set not recataloged. During a
CONVERTV operation, if the data set was cataloged in
a VSAM user catalog on the converted volume, the data
set may have been recataloged, and this message can
be ignored.
return-code
The reason code.
CATALOG RETURN CODE FOR RECAT

REQUEST WAS return-code - REASON
CODE rsncde
Explanation: The return code from an OS/VS

recatalog request was specified. The reason code in
register 0 was specified. A subsequent message
identifies the data set not cataloged.
return-code
The return code.
rsncode
The reason code.

error and recatalog the data set using the IEHPROGM
utility or the Access Method Services DELETE and
DEFINE commands.
the job log for more information. 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, the
SYSOUT output for the job, and all printed output and
Source: DFSMSdfp
IDC2103I
VOLUME IN RECORD CHAIN CANNOT

BE RETRIEVED
Explanation: An Inventory data set error caused a

break in the group or non-grouped volume chain. The
next record in the chain either was not found, or the
record indicates that it does not belong in the chain
being processed. A reason code of X208 or X224 was
returned from the Mass Storage Volume Control
functions. The error may be caused by another
command updating the Inventory data set while this
command is running.
323

the next group if the request is for grouped volumes. If
the request is for non-grouped volumes, the system
ends processing.
command again. If there is a permanent Inventory data
set error, contact the system programmer.
Source: DFSMSdfp
IDC2110I
** REMAINING VOLUMES IN GROUP

grpname CANNOT BE PROCESSED

Explanation: An Inventory data set error occurred to

prevent processing down the volume chain for the
specified group. The problem may be temporary, or the
Inventory data set may have permanent errors. A
preceding message indicates the type of error
encountered with the Inventory data set.
Source: DFSMSdfp
grpname
The group name.
IDC2108I
** UNABLE TO PROCESS VOLUME ser
Explanation: The specified volume cannot be

processed. A preceding message indicates the reason
why the volume cannot be processed.
ser
System Action: The command continues with the next

volume to be processed. If there are no more volumes,
the command ends.
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
determination steps for the preceding message.
Source: DFSMSdfp
IDC2109I
** REMAINING VOLUMES CANNOT BE

PROCESSED
Explanation: An error occurred in the Inventory data

set that prevents any more volume records from being
read. Remaining volumes cannot be processed by the
command. A preceding message indicates the type of
error encountered with the Inventory data set.
System Action: The command ends.
Application Programmer Response: Contact the
system programmer to correct the problem with the
Inventory data set.
324

the next group. If there are no more groups, the
command ends.
preceding message to determine why processing for
this group ended. Contact the system programmer to
correct the Inventory data set if necessary. Run the
command again.
Source: DFSMSdfp
IDC2111I
** REMAINING GROUPS CANNOT BE

PROCESSED
Explanation: An error occurred in the Inventory data

set that prevented any more group records from being
read. A preceding message indicates the type of
Inventory data set error.
preceding message for the type of Inventory data set
error.
Source: DFSMSdfp

IDC2118I
** SCRATCH RECORD FOR GROUP

grpname CANNOT BE RETRIEVED
Explanation: The scratch record for the specified

group cannot be retrieved because either:
v The attempt to access a scratch record in the
inventory data set for the group failed
v The scratch record did not contain volumes
scheduled for processing by the system-initiated
scratch function.
See the preceding message for further explanation of
the failure.

Source: DFSMSdfp
IDC2160I
INVALID REFERENCE TO VOLUME

xxxxxx, OBJECT BYPASSED
Explanation: EXPORTRA has encountered a virtual

storage access method (VSAM) object that references a
volume entry that contains no reference to the object.
This may be the result of a system failure during a prior
delete operation.
grpname
xxxxxx Indicates the volume.

The group name.
System Action: The command ends with this

message unless additional groups are specified for
processing.
error specified in the preceding message. Before
running the command again, check that the group name
is specified correctly.
Source: DFSMSdfp
IDC2119I
** CATALOG RECORD FOR GROUP

grpname CANNOT BE RETRIEVED
Explanation: An attempt to access the catalog record

in the inventory data set for the specified group failed.
the failure.
grpname
The group name.
System Action: The command ends with this
message unless additional groups are specified for
processing.
error specified in the preceding message. Verify that the
group name is specified correctly. Run the command
again.
System Action: EXPORTRA bypasses the VSAM data

set and its associations.
Application Programmer Response: Copy the data
on valid volumes using the REPRO command. Delete
the data set using the DELETE command. The data set
cannot be opened for output.
Source: DFSMSdfp
IDC2360I
CATALOG ENTRY FOR DATA SET

INDICATES DIFFERENT DEVICE TYPE
Explanation: The ULOCATE function, after locating a

data set name in the catalog, determined that the data
set resides on a device type other than the catalog
indicates, or else a duplicate data set name exists.
the next data set on the volume.
Application Programmer Response: If the device
type is incorrect, uncatalog the data set and then
recatalog it with the correct device type.
System Programmer Response: Issue the access
catalog.
If the error recurs and the program is not in error, look
at the messages in the job log for more information.
325
to the problem.
Source: DFSMSdfp
Source: DFSMSdfp
IDC2364I
IDC2371I
CATALOG ENTRY TYPE FOR DATA

SET IS OTHER THAN NON-VSAM
Explanation: The ULOCATE function, after locating a

data set name in the catalog, determined that the
catalog entry type was not for a virtual storage access
method (VSAM) data set, or else a duplicate data set
name exists.
Application Programmer Response: If the data set
entry is cataloged, rerun the SCRDSET command after
restructuring the STEPCAT concatenation.
catalog.
to the problem.
Source: DFSMSdfp
UNABLE TO OBTAIN STORAGE FOR

I/O PROCESSING
Explanation: There was insufficient storage to perform

the necessary I/O processing.
region size for the job. Run the command again.
Source: DFSMSdfp
IDC2372I
OPEN ABEND EXIT {dsname|VTOC}
Explanation: The OPEN macro encountered an error

that resulted in the OPEN DCB ABEND exit being
entered. This error prevented the opening of the data
control block (DCB) and stopped further I/O processing.
The specified data set or the volume table of contents
(VTOC) was being opened.
IDC2370I
UNABLE TO READ JFCB FOR DD

ENTRY ddname RDJFCB CODE x
Explanation: The system was not able to read the job

file control block (JFCB) for the specified DD statement.
The RDJFCB macro return code was specified. This
condition generally occurs when the DD statement was
not supplied.
ddname
The data definition name.
The macro return code.

Application Programmer Response: Ensure the DD
name in the FILE parameter is correct and there is a
corresponding DD statement in the JCL statements.
326
dsname
The data set name.
write-to-programmer message issued by the OPEN
macro for the specific error code. Correct the problem.
Run the command again.
Source: DFSMSdfp
IDC2373I
INVALID PASSWORD dsname
Explanation: One of the following errors occurred:

v The operator did not supply the correct password for
the specified non-VSAM data set, for the specified
VSAM unique data or index 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.
dsname
The data set name.
System Action: The command ends normally. The
requested function cannot be performed.
Application Programmer Response: If the operator
supplied the incorrect password, do the following:
v Tell the system operator the correct password. The
operator is prompted for the password that
corresponds to:
1. The data or index component name or code word
(VSAM data sets)

write-to-programmer message issued by the CLOSE
macro for the specific error. Correct the problem. Run
the command again if the function was not performed.
Source: DFSMSdfp
IDC2375I
**I/O ERROR volser IOS RC =

return-code
Explanation: An I/O error occurred from the

command.
volser
2. The name of the DD statement for the data set

(non-VSAM data sets).
return-code
The IOS completion code, that comes

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:
v Supply a JOBCAT or STEPCAT DD statement for the
catalog or supply the master password of the VSAM
catalog on the command or via operator prompting.
Source: DFSMSdfp
IDC2374I
CLOSE ABEND EXIT {dsname|VTOC}
Explanation: The CLOSE macro encountered an error

that resulted in the CLOSE DCB ABEND exit being
entered. This error prevented the closing of the DCB
and stopped further I/O processing. The specified data
set or volume table of contents (VTOC) was being
closed.
dsname
The data set name.
Application Programmer Response: This is a

probable subsystem problem. Correct any error. Run the
command again.
Source: DFSMSdfp
IDC2376I
SECURITY VIOLATION dsname
Explanation: One of the following errors occurred:

v The system operator did not supply the correct
password for the non-VSAM data set for the virtual
storage access method (VSAM) unique data or index
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.
v The user does not have the proper RACF
authorization to the VSAM unique data or index
component or for a data or index component within
the specified VSAM data space.
dsname
The data set name.
requested function is not performed.
327

supplied the incorrect password, tell the system
operator the correct password. The operator is
prompted for the password that corresponds to the data
or index component name or code word (VSAM data
sets) or the name of the DD statement for the data set
(non-VSAM data sets). Reissue the command.
If there is no JOBCAT or STEPCAT DD statement for
the VSAM catalog, supply a JOBCAT or STEPCAT DD
statement for the catalog or supply the master password
of the VSAM catalog on the command or through the
use of operator prompting. Reissue the command.
IDC2386I
UNIT ASSIGNED TO ddname COULD

NOT BE READIED FOR MOUNTING
Explanation: The unit assigned by the DD statement

cannot be used to mount needed volumes, because a
previous volume cannot be demounted.
ddname
The data definition name.
If the protection violation occurred for a RACF-protected

VSAM component, acquire the proper RACF user
authorization to all RACF-protected VSAM components
on the volume or the VSAM catalog that owns the
volume. Reissue the command.

command again. Specify the correct volume serial on
the DD statement. If the same unit is assigned to the
DD statement and the same error occurs, run the
command again after the operator varies the unusable
unit offline.


Source: DFSMSdfp
Source: DFSMSdfp
IDC2381I
VOLUME WITH SERIAL volser

ALREADY MOUNTED IN SYSTEM
Explanation: After mounting the specified mass

storage volume the user control block (UCB) cannot be
posted because it causes a duplication of volume label
within the system.
volser
System Action: The system demounts the mass

storage volume. The command ends normally.
command again after the volume with the same serial
number is demounted.
Source: DFSMSdfp
328
IDC2387I
** VOLUME volser COULD NOT BE

MOUNTED
Explanation: The mount of the specified volume is

unsuccessful. A preceding message gives the
explanation for this error.
volser

preceding message and correct the problem. Run the
command again.
Source: DFSMSdfp
IDC2388I

DEMOUNTED
Explanation: The demount of the specified volume is

unsuccessful. A preceding message gives the
explanation for this error.
volser

preceding message and correct the problem. Run the
command again.
Source: DFSMSdfp
IDC2390I
VOLUME volser COULD NOT BE

ENQUEUED FOR EXCLUSIVE USE
return-code
The return code.
System Action: The system does not continue the

function.
return code and correct the problem. Run the command
again.
Source: DFSMSdfp
IDC2399I
CATALOG ENTRY FOR DATA SET

INDICATES DIFFERENT VOLUME
Explanation: The ULOCATE function, after locating

the data set name in the catalog, determined that the
data set resides on a different volume than the catalog
indicates, or else a duplicate data set name exists.
Explanation: The enqueue of the specified volume for

exclusive use cannot be done because the volume
serial is enqueued for shared use.
Application Programmer Response: Uncatalog the

data set, then recatalog it with the correct volume serial
number.

catalog.
volser

command again after the volume is not being used by
any other job. Specify the volume serial on the DD
statement.
Source: DFSMSdfp
IDC2391I
UNABLE TO ESTABLISH E/STAE

ENVIRONMENT - RETURN CODE
X'return-code'
Explanation: The STAE or ESTAE macro returned a

non-zero return code that prevented recovery protection
in case of an abnormal end of the command.

to the problem.
Source: DFSMSdfp
IDC2533I
MEMBER CANNOT BE SPECIFIED

WITH A GENERIC NAME
Explanation: A generic entry name was given followed

by a member name in parentheses, which is not an
allowable combination.
asterisk (*) indicating a generic entry name or remove
the member name to achieve the desired alteration.
Source: DFSMSdfp
329
System Action: The system ends processing for this

entry.
IDC2552I

dynamic allocation error messages or supply a FILE
parameter.
ENTRY TYPE IS INVALID FOR DELETE
Explanation: The caller attempted to delete an entry

type that cannot be deleted. The only types of entries
that can be deleted are as follows:
v Cluster
v User
v Catalog
v Master catalog
v Non-VSAM
v Space
v Alias
v GDG base
v Path and alternate index
System Action: The system does not delete the entry.
The rest of the entries are deleted if possible.
Application Programmer Response: If the caller
thinks the entry is one of these types, he should list that
entry with LISTCAT to check the type field.
and the entry type is listed as valid in the LISTCAT,
job.
Source: DFSMSdfp

and the SYSOUT output for the job. Obtain the ABEND
dump for the failing job step.
Source: DFSMSdfp
IDC2557I
SCRATCH NOT AVAILABLE FOR TYPE

OF OBJECT TO BE DELETED
Explanation: The SCRATCH option is incorrect for the

entry type being deleted. SCRATCH is incorrect for a
virtual storage access method (VSAM):
v Master catalog
v User catalog
v Path
v Alias
v GDG base
System Action: The system ends processing for the
entry.
Application Programmer Response: Ensure that

SCRATCH is valid for all entries specified, or do not use
the SCRATCH option.
IDC2553I
Source: DFSMSdfp
ERASE OPTION IS INVALID FOR

ENTRY TYPE
Explanation: Only virtual storage access method

(VSAM) clusters and alternate indexes can be erased.
The remaining VSAM entries, if any, are deleted.
Application Programmer Response: Submit the
request again without the ERASE parameter.
JCL, the SYSOUT output for the job.
Source: DFSMSdfp
IDC2554I
DYNAMIC ALLOCATION FAILED OR

FILE WAS NOT CODED WITH
SCRATCH
Explanation: A dynamic allocation failed. Preceding

messages (prefixed by IKJ) indicate the reason for the
failure.
330

IDC2559I
MEMBER CANNOT BE SPECIFIED

WITH A GENERIC NAME
Explanation: The generic name used is followed by a

member name enclosed in parentheses. This
combination is incorrect.
entry.
asterisk (*) which indicates a generic entry name or
remove the member name.
Source: DFSMSdfp
IDC2563I
ALLOCATION/VOLUME PARAMETER IS
INVALID FOR ENTRY TYPE(S)
Explanation: A LISTCAT command request for

allocation or volume information conflicts with the
desired entries or types of entries.
System Action: The LISTCAT command attempts
recovery to list that part of the request that does not
conflict.
again with LISTCAT parameters that are compatible
with the fields specification.
Source: DFSMSdfp
IDC2616I
PATH path WAS NOT SUCCESSFULLY

IMPORTED

IDC2620I
OBJECT TYPE NOT SUPPORTED FOR

OBJECT dsname
Explanation: A duplicate data set name was found in

the virtual storage access method (VSAM) catalog while
attempting to convert an OS catalog entry.
The portable data set format is not supported on this
system for one of the following reasons:
v The object is empty.
v The object has the NOALLOCATE attribute.
v The object has the SAM ESDS attribute.
dsname
The data set name.
System Action: An associated message identifies the
entry not converted.
Application Programmer Response: Resolve the
duplicate name.
Explanation: IMPORT was not able to define

successfully path over the object being imported. The
most likely cause is a duplicate object name already in
the catalog.

Source: DFSMSdfp
path
The path object.
System Action: The system continues processing,

attempting to define any remaining paths whose catalog
information is stored on the portable data set.
Application Programmer Response: Determine if the
paths whose defines failed already exist in the catalog.
If so, delete and redefine them.
Source: DFSMSdfp
IDC2618I
INVALID OBJECTS SUBPARAMETER

FOR PATH path
Explanation: An OBJECTS subparameter other than

NEWNAME or FILE was specified for path object.
path
The path object.
System Action: The system continues IMPORT

processing, attempting to define any remaining paths
from the portable data set.
error. Correct the OBJECTS parameter. Submit the job
again.
Source: DFSMSdfp
IDC2621I
IMPORTRA FAILED FOR obj
Explanation: The object named could not be

imported. The preceding messages will give the reason
for the failure.
obj
The specified object.

the next object on the portable data set unless one of
the following conditions exists:
v A failure occurred while attempting to alter the name
of the cluster to or from the dummy name provided in
the OUTFILE DD statement. (Message IDC3619I
precedes this message.)
v An error occurred while trying to read the portable
data set.
In both cases, the command ends.
cause of the failure by examining previous messages on
the SYSPRINT output. Correct the indicated error. Run
the job again.
Source: DFSMSdfp
331

IDC2630I
DUPLICATE DATA SET NAME IN

TARGET CATALOG
Explanation: A duplicate data set name was found in

the target catalog while attempting to convert an OS or
virtual storage access method (VSAM) catalog entry.
System Action: An associated message identifies the
entry not converted.
Application Programmer Response: Resolve the
duplicate name.
Source: DFSMSdfp
IDC2640I
dsname NOT AN AIX
Explanation: The specified data set is not an alternate

index or a path over an alternate index. The data set
name was specified in either the:
v Job control identified through the OUTFILE dname
subparameter
v OUTDATASET dsname subparameter
The OUTFILE data set must be a defined alternate
index or a path over the alternate index.
dsname
The data set name.
OUTFILE or OUTDATASET subparameter. However, the
system continues processing with any other
subparameters specified in the OUTFILE or
OUTDATASET parameter.
Application Programmer Response: Correct the data
set name in the job control identified by the OUTFILE
dname subparameter or the data set name specified in
the OUTDATASET subparameter to be a defined
alternate index or a path over an alternate index.
Submit the job again.
Source: DFSMSdfp
332
IDC2642I
dsname NOT RELATED TO BASE
Explanation: The specified data set is an alternate

index or a path over an alternate index, but the
alternate index is not related to the base cluster
identified by the INFILE or INDATASET parameter. All
alternate indexes identified by the OUTFILE or
OUTDATASET parameter of the BLDINDEX command
must have been defined as being related to the base
cluster identified by the INFILE or INDATASET
parameter. This relationship is established by the
RELATE parameter in the DEFINE ALTERNATEINDEX
command.
dsname
The data set name.
System Action: The system sends processing for this
alternate index. However, the system continues
processing for any other alternate indices identified by
the OUTFILE or OUTDATASET parameter.
Application Programmer Response: Either the
alternate index identified by the OUTFILE or
OUTDATASET parameter or the base cluster identified
by the INFILE or INDATASET parameter must be
corrected so that the proper relationship exists. If the
alternate index was defined improperly, it must be
deleted and redefined with the proper relationship
specified in the RELATE parameter. Submit the job
again.
Source: DFSMSdfp
IDC2647I
INSUFFICIENT STORAGE TO OBTAIN

BUFFERS AND WORK AREAS
Explanation: BLDINDEX encountered a failure when

attempting to obtain storage for buffers, work areas and
a minimum sort area. BLDINDEX is the amount of
storage required to build one alternate index. The name
of the alternate index is given in a subsequent
message.
alternate index. However, BLDINDEX attempts to
process any other alternate indices identified by the
OUTFILE or OUTDATASET parameter.
virtual storage region size. Submit the job again.

Source: DFSMSdfp
IDC2648I
JOB CONTROL CARDS FOR

EXTERNAL SORT MISSING OR IN
ERROR
Explanation: If this message occurs by itself, the

caller specified the EXTERNALSORT parameter, but did
not provide the proper job control for the sort work files.
If this message is preceded by IDC2649I or IDC2650I,
BLDINDEX was not able to complete an internal sort.
Proper job control for the external sort work files was
not supplied. The alternate index being built is named in
a subsequent message.
process any other alternate indices specified by the
external sort work file job control. Submit the job again.
Alternatively, provide enough virtual storage so that an
internal sort can be performed.
Source: DFSMSdfp
IDC2649I
INSUFFICIENT STORAGE TO
PERFORM INTERNAL SORT
Explanation: Although BLDINDEX was able to obtain

a minimum amount of virtual storage to start the sort, it
was less than the amount calculated to be required for
the entire sort. This is based on the number of records
in the base cluster statistic stored in the virtual storage
access method (VSAM) catalog entry for the base
cluster. Under these circumstances, BLDINDEX
attempts to prepare for an external sort. The system
writes this message only when proper job control for the
external sort work files was not supplied.
process any other alternate indexes specified via the

Source: DFSMSdfp
IDC2650I
INSUFFICIENT STORAGE TO FINISH

INTERNAL SORT
Explanation: During initialization, BLDINDEX

calculates the amount of storage required for an internal
sort. This calculation is based on the number of records
in the base cluster statistic stored in the virtual storage
access method (VSAM) catalog entry for the base
cluster.
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,
probably due to a failure during a close of the base
cluster, and the initial amount of storage obtained was
exhausted. Under these circumstances, BLDINDEX
must perform an external sort. The system issues this
message only when proper job control for the external
sort work files was not supplied.
process any other alternate indices specified by the
Application Programmer Response: Correct the sort
work file job control. Alternatively, delete the alternate
index. Use the EXPORT command to create a portable
copy of the base cluster, followed by an IMPORT
command to rebuild the base cluster. This will correct
the erroneous statistic. Then redefine the alternate
index. Submit the job again.
Source: DFSMSdfp
IDC2651I
DEFINE OF SORT WORK FILES

FAILED

external sort work file job control, or provide enough
virtual storage so that an internal sort can be performed.
Submit the job again.
Explanation: In preparing for an external sort

BLDINDEX attempts to define dynamically two sort work
files. However, the define was rejected by virtual
storage access method (VSAM) catalog management.
This message is preceded by either message IDC3007I
or IDC3009I giving the VSAM catalog return code. Refer
to the appropriate message for an explanation of the
code.


333
process any other alternate indexes specified by the

error as explained for the return code. Submit the job
again.
BLDINDEX attempts to process any other alternate

indices identified by the OUTFILE or OUTDATASET
parameter.
Application Programmer Response: Follow the
problem determination actions.


Source: DFSMSdfp
Source: DFSMSdfp
IDC2654I
dsname WAS NOT BUILT
Explanation: An error was encountered for the

alternate index. The message containing the error
dsname
The data set name.
process any other alternate indexes identified by the
Source: DFSMSdfp
IDC2655I
UNABLE TO LOCATE ATTRIBUTES OF

dsname

(VSAM) catalog locate function issued by BLDINDEX
has been unable to obtain all the necessary information
regarding the entry. This indicates a serious catalog
error since the information requested should be present
for all catalog entries, as follows:
IDC2656I
LOCATE FAILED FOR dsname

(VSAM) catalog locate function issued against the base
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
code.
The locate failure may have been against the named
object or an object associated with the named object.
dsname
The data set name specified by the
INFILE/INDATASET or
OUTFILE/OUTDATASET parameter.
System Action: If the failure is associated with the
base cluster, the system ends processing for the entire
BLDINDEX command.
If the failure is associated with an alternate index, the
system ends processing for the alternate index.
However, BLDINDEX attempts to process any other
alternate indices identified by the OUTFILE or
OUTDATASET parameter.
error as explained for the return code. Submit the job
again.
v Associated objects

v AMDSB control block for data objects
Source: DFSMSdfp
v Entry type
dsname
The data set name.
System Action: If the specified data set name is the
base cluster, the system ends BLDINDEX processing.i If
it is an alternate index or a path over an alternate index,
the system ends processing for the alternate index.
334
IDC2658I
SORT PRODUCT FAILED
Explanation: BLDINDEX has invoked DFSORT (or an

equivalent product) to sort the alternate index. An error
has occurred during this processing.

command.
System Programmer Response: Correct the error as
indicated in the preceding messages if they exist. If no
preceding messages exist, check the DFSORT (or
equivalent product) message data set for detailed
information on the cause of the failure. If
SORTMESSAGELEVEL(ALL) was specified use the call
identifier to find the set of DFSORT (or equivalent
product) messages for this call (see IDC01850I and
DFSORT message ICE200I or the appropriate message
for an equivalent product), and correct the DFSORT (or
equivalent product) error that caused the failure.
IDC2660I
INVALID ENTRY TYPE IN CATALOG,

OBJECT BYPASSED
IDC2668I
DATA SET NOT EXPORTED, VOLUME

ser REQUIRED BUT NOT SUPPLIED
Explanation: Synchronization checking was attempted

on a volume not included in the list of volumes in the
catalog recovery area (CRA) keyword.
ser
System Action: The system does not process the

virtual storage access method (VSAM) entry.
Application Programmer Response: Add the volume
serial number to the CRA keyword. Run the job again.
Source: DFSMSdfp
Explanation: The entry type field indicates the object

being exported is not one of the following:
IDC2671I
v A virtual storage access method (VSAM) cluster

v Alternate index
Explanation: This volume does not belong to the

catalog named in the following message.
v User catalog
v Non-VSAM object
ser
v OS/VS2 generation data group (GDG)

object.
Application Programmer Response: Redefine the
object in error. For the object name, see the following
second-level message.
Source: DFSMSdfp
IDC2666I
ENTRY NAME SPECIFIED CANNOT BE

FOUND IN SPECIFIED CRA
Explanation: The data set named in the ENTRIES

parameter of the EXPORTRA command cannot be
found in the catalog recovery area (CRA) specified. See
message IDC0674I for the name of that unlocated data
set.
System Action: The system ends processing of this
object. The system begins processing of the next object.
Application Programmer Response: Verify the name
and CRA of the data set to be exported using the
LISTCRA command.
WILL NOT PROCESS CRA ON VOLUME

ser, DIFFERENT CATALOG NAME
System Action: The system discontinues processing

of this volume.
with the correct catalog name.
Source: DFSMSdfp
IDC2673I
CONFLICTING JCL SPECIFICATIONS

FOR DNAME dname
Explanation: Incorrect volume information was

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
in the job control for a CRA.
dname The specified DNAME.

request.
volume information in error. Run the job again.
Source: DFSMSdfp
Source: DFSMSdfp
335
IDC2675I
DUPLICATE NAME ENCOUNTERED,

NAME ON VOLUME ser BYPASSED
System Action: The command scratches the partially

created volume and ends processing normally.

error as indicated in the preceding message. Run the
command again, requesting creation of the volumes not
created.
ser
Source: DFSMSdfp
Explanation: Duplicate names were found in the

catalog recovery areas (CRA) on two different volumes.
System Action: The system skips the name specified

in the following second-level message.
Application Programmer Response: If the copy of

the data set skipped was on a volume not to be
skipped, run the job again specifying only the desired
volume and data set.
IDC2685I
** NO ATTEMPT MADE TO CREATE

ADDITIONAL VOLUMES
Source: DFSMSdfp
Explanation: An error occurred preventing the

creation of all volumes requested. A preceding message
explains the error.
IDC2677I
** DATA SET NOT EXPORTED
Explanation: An error occurred or a catalog field could

not be located for the object being exported.
EXPORTRA command.
type of error from the preceding message, and redefine
the object.
Source: DFSMSdfp
IDC2681I
** VOLUME volser NOT CREATED
Explanation: The volume was not created for the

specified volume serial number. A preceding message
explains the error.
volser
System Action: The command does not attempt to

create any subsequent volumes and ends normally.
command again.
Source: DFSMSdfp
IDC2684I
** VOLUME volser NOT INITIALIZED
Explanation: The newly created volume was not

initialized with a volume label and an empty volume
table of contents (VTOC). A preceding message
explains the error.
volser
336


error indicated in the preceding message. Run the
command again, requesting creation of the volumes not
created.
Source: DFSMSdfp
IDC2687I
** PARTIALLY CREATED VOLUME

volser NOT SCRATCHED
Explanation: The partially created volume was not

scratched during back out because an error occurred. A
preceding message explains the error.
volser

volume record in the Inventory data set for the volume
indicates the volume was incompletely created.
error indicated in the preceding message.
Run SCRATCHV to scratch the partially created volume
before running CREATEV again to recreate the same
volume. A DD statement is not required even if the
partially created volume is active. If a DD statement is
provided, deferred mounting must be specified.
SCRATCHV bypasses the empty volume table of
contents (VTOC) check of the partially created volume.
If CREATEV ends without indicating the status of the
volume create operation, run LISTMSVI to determine
whether the volume is flagged for recovery purposes. If
the incomplete create 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 a create operation failed for the preceding volume.

csn2
The unscratched cartridges.
Source: DFSMSdfp
volser
IDC2688I

command again.
** INCOMPLETE VOLUME CREATION

FLAG NOT RESET FOR VOLUME volser
csn1
Explanation: The recovery flag for incomplete volume

creation was not turned off in the Inventory record after
new volume creation was completed for the specified
volume. A preceding message explains the error.
Source: DFSMSdfp
IDC2753I
volser
System Action: The command scratches the partially

created volume.
command again.

VOLUME volser NOT SCRATCHED,
COPIES EXIST
Explanation: The base volume was not scratched

because copies still exist.
volser
System Action: The command ended normally.


error that prevented the copies from being scratched.
Run the command again, specifying the ALL parameter.
Source: DFSMSdfp
IDC2761I
Source: DFSMSdfp

IDC2689I
INSUFFICIENT NUMBER OF
CARTRIDGES SPECIFIED ON
COMMAND
** RECORD FOR COPY yyddd NOT

REMOVED
Explanation: The volume copy record created on the

indicated date was not removed from the Inventory data
set. A preceding message explains the reason for the
error.
Explanation: The number of cartridges specified in the

CARTRIDGE parameter is insufficient to create the
number of new volumes requested.
yyddd
System Action: The command creates as many

volumes as possible before ending normally.
System Action: The command either continues

processing or ends depending on the severity of the
error encountered.

sufficient cartridges in the CARTRIDGE parameter for
all volumes to be created or do not specify any
cartridges in the CARTRIDGE parameter. Run the
command again.

command again to remove records not removed.
Source: DFSMSdfp
Source: DFSMSdfp

IDC2762I
IDC2752I
** CARTS csn1 cns2 NOT SCRATCHED

FOR volser
Explanation: The requested volume was not

scratched.
** RECORD FOR VOLUME volser NOT

REMOVED
Explanation: The volume record was not removed

from the Inventory data set. A preceding error message
explains the reason for the error.
337
volser

command to remove the volume record.
Source: DFSMSdfp
IDC2764I
CARTRIDGES STILL IN MASS

STORAGE FACILITY
Explanation: The REPLACEVOLUME keyword is

specified, but the base volume cartridges have been
reentered into the Mass Storage Facility (MSF) while
the Mass Storage Volume Control was disabled.
System Action: The system bypasses the request.
The remaining requests will be attempted.
Application Programmer Response: When the Mass
Storage Volume Control is enabled, eject the base
volume from the Mass Storage Control and reenter it.
Issue the following access method services commands:
v MSS LISTMSF for mountable volumes
v MSS LISTMSF with the CARTRIDGES parameter
v PRINT to list the contents of the mass storage
volume control inventory data set
v LISTMSVI
v LISTMSF with the ALL parameter
Source: DFSMSdfp
IDC2765I
RECORD FOR VOLUME volser NOT

REMOVED. RECORD FOR COPY
EXISTS
Explanation: A copy volume record still exists.

Therefore, the base volume record for the specified
volume cannot be removed. See a preceding message
for the error that prevented removal of all copy records.
IDC2782I
** SCRATCH CARTRIDGE csn NOT

EJECTED
Explanation: The requested scratch cartridge could

not be ejected. See the preceding message for further
explanation of the problem.
csn

problem as identified in the preceding message. Run
the command again to eject the cartridge.
Source: DFSMSdfp
IDC2800I
ATTRIBUTES COULD NOT BE

CHANGED FOR REMAINING VOLUMES
IN GROUP
Explanation: Although the group level attributes have

been successfully changed in the group record in the
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
record cannot be retrieved from the Inventory data set.
v bind/nobind,
v exclusive/shared,
volser

REMOVEVR command again with the ALL parameter.
Source: DFSMSdfp
338

problem as identified in a preceding message. To
determine the number of additional volumes in the
group that must be updated, run the LISTMSVI
command. Run the command again if a large number of
volumes remain to be updated. Otherwise, run the
MODIFYV command to change the volume attributes of
each volume if the number of remaining volumes is
small.
Source: DFSMSdfp
Detecting Module: IDCMG01

Source: DFSMSdfp
IDC2801I
** ATTRIBUTES NOT CHANGED FOR

VOLUME volser
Explanation: Although the attributes have been

changed in the group record, the attributes of the
specified volume cannot be changed. The volume may
be currently mounted, marked in the Inventory data set
for recovery purposes, or unavailable for another
reason. See the preceding message for further
v bind/nobind
v readonly/readwrite,
v exclusive/shared
problem as identified in the preceding message. Run
the MODIFYV command to change the volume
attributes of each volume that could not be updated.
Source: DFSMSdfp
Detecting Module: IDCMG01
IDC2821I
** text REPORT NOT PRODUCED

SCRATCH CARTRIDGE
MOUNTABLE VOLUME
NON-MOUNTABLE VOLUME
The indicated report was not produced due to a
previously identified error.
System Action: The command continues with the next
report.
previous error message for the cause of the failure.
Correct the error. Run the command again.
IDC2823I
** text TOTAL COULD NOT BE

CALCULATED

SCRATCH CARTRIDGE
MOUNTABLE VOLUME
NON-MOUNTABLE VOLUME
EMPTY CELL
Because of an error, the summary count information
could not be calculated. A previous message explains
the error.
System Action: The command continues processing,
but the indicated count is not listed.
error identified in the previous message. Run the
command again.
Source: DFSMSdfp
IDC2831I
** RECORD CHAIN BROKEN, REST OF

CHAIN NOT LISTED
Explanation: The record could not be found for a

volume recorded in the Inventory data set as part of a
chain of non-grouped volumes or a chain of volumes
belonging to a specific group. See the preceding
message for further explanation of the error.
command again to list volumes that could not be listed.
Source: DFSMSdfp
339
IDC2833I
** CARTRIDGE RECORD csn NOT

FOUND IN INVENTORY
Explanation: The cartridge record for the cartridge

cannot be found in the Inventory data set.
csn

Application Programmer Response: Correctly
specify the cartridge serial number. Run the job again. If
the problem is not the result of a user error, contact the
space manager.
prm
The tuning parameter.
System Action: The command ended normally. The

system does not display more parameters.
error. Run the command again.
Source: DFSMSdfp
IDC2854I
** CHANGE OF prm NOT SUCCESSFUL
Explanation: An attempt to change the specified

TUNE command parameter failed. See preceding
message for an explanation of the error.
prm
The indicated parameter.

system does not change any more tuning parameters.
Source: DFSMSdfp

error. Run the command again.
Source: DFSMSdfp
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
was possible. A preceding message explains the I/O
error.
Explanation: The catalog recovery area (CRA) on this

volume belongs to a catalog other than the one for
which COMPARE was specified.
nnn
catname
The number of records dumped.
System Action: No more data was dumped. The

command ends normally.
command again to get the remaining trace data. If the
problem continues, reallocate and recatalog the data set
which is getting I/O errors.
Source: DFSMSdfp
IDC2853I
** DISPLAY OF prm NOT SUCCESSFUL
Explanation: An attempt to retrieve the information for

the indicated tuning parameter failed. See preceding
340
The catalog name.

System Action: The system ignores the COMPARE
option. The system continues processing.
Application Programmer Response: Specify the
correct catalog in the CATALOG parameter. Run the job
again.
Source: DFSMSdfp
IDC2873I
** COMPARE OPTION IGNORED
Explanation: The catalog recovery area (CRA) on this

volume cannot be opened or belongs to a catalog other
than the one for which COMPARE was specified. If an
error occurred in open, a preceding message gives the
cause.
System Action: The system ignores the COMPARE
option of the LISTCRA command. The system continues
processing.
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
unsuccessful.

Source: DFSMSdfp
IDC2884I
IGNORED VERIFY FAILURE FOR

CATALOG

system continues processing. An incomplete listing of
the contents of the catalog recovery area may result.
Explanation: When a catalog is opened, a VERIFY

command is issued by LISTCRA to set up the proper
end-of-file condition. The VERIFY was unsuccessful.

condition.
System Action: The system ignores the command.

The system continues processing. Erroneous
miscompares or I/O errors may result.


condition.
Source: DFSMSdfp
IDC2879I
CATALOG NOT LOCKED UP FOR THIS

EXECUTION
Explanation: LISTCRA was unable to gain exclusive

control of the catalog. One or more other programs may
be updating the catalog during LISTCRA processing.
System Action: The system continues LISTCRA
processing. Some listing errors or miscompares may
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
doubted, run the job again when no other programs are
accessing the catalog.

Source: DFSMSdfp
IDC2886I
UNABLE TO REFERENCE CRA ON

VOLUME ser - REASON CODE cde
Explanation: When opening the catalog recovery area

(CRA) the system detected an error.
ser
cde
The hex reason code, as follows:

Codes Explanation
Source: DFSMSdfp
Cannot verify the CRA.
Cannot open the CRA.
I/O error on control interval No.0
I/O error on control interval No.3
Error on number of directories.
Error on directory entries.
IDC2882I
VSAM ERROR READING CRA

CONTROL RECORD
Explanation: A LISTCRA command encountered an

error reading the control record in the catalog recovery
area (CRA) to determine the size of the table necessary
for its processing.
CRA.
condition.
System Action: The system marks the CRA as bad.

No entries are placed on the portable data set.
Application Programmer Response: If the reason
code is 1, 2, 4, or 5, restore the volume on which the
error occurred to a previous valid condition.
If the reason code is 7 or 8, provide the FORCE
keyword in the EXPORTRA command to override the
synchronization problem.
341
Source: DFSMSdfp
IDC2889I
UNUSABLE DATA SET NOT

EXPORTED
Explanation: A multi-volume data set, identified in the

following message and marked unusable, was
encountered by EXPORTRA. The data set is not on one
or more of its secondary volumes. This situation is
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
valid volumes can be removed using the REPRO
command prior to deletion. The data set cannot be
opened for output.
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).
The remaining entries, if any, are deleted.
parameters specified. If RECOVERY is specified for a
GDG, the GENERATIONDATAGROUP parameter must
be specified. Run the job again.
Source: DFSMSdfp
IDC2894I
GENERIC NAME NOT ALLOWED FOR

NVR, VVR OR TRUENAME DELETE
Explanation: On a DELETE command, a name in the

generic form, a name with a qualifier of asterisk (*), was
specified along with the NVR, VVR or TRUENAME
parameter. Generic names are not allowed when
deleting NVR, VVR or TRUENAME entries. One
DELETE command is required for each NVR, VVR or
TRUENAME entry to be deleted.
IDC2892I

command.
Source: DFSMSdfp
INVALID ENTRY TYPE FOR A VSAM

VOLUME DATA SET
Explanation: A virtual storage access method (VSAM)

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.
The remaining entries, if any, are deleted.
CLUSTER parameter or run a LISTCAT against the
catalog to verify the entry type. Correct the error. Run
the job again.
Source: DFSMSdfp
IDC2893I
INVALID PARAMETER SPECIFIED FOR

THE RECOVERY OPTION
Explanation: The RECOVERY parameter has been

specified for a DELETE command and a virtual storage
access method (VSAM) volume data set (VVDS) is not
to be deleted, or the GENERATIONDATAGROUP
342

name specification. Run the job again.
Source: DFSMSdfp
IDC2895I
ALL REQUIRED VOLUMES NOT

INCLUDED IN DD STATEMENT
SPECIFIED IN FILE PARAMETER
Explanation: A FILE parameter was specified on a

DELETE command. The DD statement does not contain
all of the required volumes to delete the entry.
However, it does delete any remaining entries.
Application Programmer Response: You may
perform one of the following procedures:
v Add the missing volumes to the DD statement. Run
the job again.
v Remove the FILE parameter and allow dynamic
allocation to allocate the necessary volumes. You
may need a JOBCAT or STEPCAT to insure that the

volumes contain the correct mount status.
Source: DFSMSdfp
IDC2908I
ddname NOT FOUND IN SYSTEM
Explanation: An attempt was made to use the

specified volume. The DD statement corresponding to
the ddname could not be found.
IDC2910I
** NO VOLUME MOUNTED
Explanation: None of the volumes specified for the

data set are mounted.
System Action: The data set is not scratched.
Application Programmer Response: Mount the
proper volumes. Submit the job again.
Source: DFSMSdfp

IDC2912I
ddname
The ddname.
System Action: The volume cannot be accessed.
erroneous ddname or provide a DD statement. Submit
the job again.
** PASSWORD VERIFICATION FAILED
Explanation: The console operator did not supply the

proper password for the data set to be scratched.
Application Programmer Response: Submit the job
again, supplying the correct password when prompted.


Source: DFSMSdfp
Source: DFSMSdfp
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
second-level message explains the error.
Explanation: The PURGE option was not specified,

and the data set retention period has not expired.
dsname
ser
The data set name.


Application Programmer Response: Submit the job
again, specifying PURGE to delete the data set.
Source: DFSMSdfp

Source: DFSMSdfp
343
IDC2914I
** PERMANENT I/O ERROR ON

VOLUME ser
Explanation: The volume table of contents (VTOC)

cannot be read because of an I/O error.
ser

Application Programmer Response: Request that
the volume be restored.
Source: DFSMSdfp
IDC2917I
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
resource. RACF could not perform the user
authorization check for the resource.
resname
The resource name. resname can be either a
RACF FACILITY class or a DASD volume. In
the case of a RACF FACILITY class, resname
will be the name of the class. For a DASD
volume, resname will contain the volume serial
number.
Source: DFSMSdfp
IDC2915I
** UNABLE TO MOUNT VOLUME ser
Explanation: An appropriate unit was not available for

mounting, or JES3 will not permit the volume to be
mounted.
ser

Application Programmer Response: Ensure that a
unit is available for mounting.
Source: DFSMSdfp
NO RACF PROFILE ON resname
System Action: If a Cache-DASD command was

issued, the system continues processing. Otherwise, the
command ends.
Cache-DASD commands are as follows:
v BINDDATA
v LISTDATA
v SETCACHE
Application Programmer Response: Before running
the job again, define the resource to RACF. If the
resource is a data set, use the RACF ADDSD
command. Otherwise, use the RACF RDEFINE
command.
These commands can be run in the foreground or with
the Terminal Monitor Program in the background.
Source: DFSMSdfp
IDC2916I
** DATA SET WAS IN USE
Explanation: The data set to be scratched was in use.

Application Programmer Response: To delete the
data set, ensure that no one else is using the data set
when you run the job again.
344
IDC2918I
RACHECK FAILED FOR resname
Explanation: An unauthorized caller requested access

to a RACF protected resource. The caller does not have
the proper authorization for the specified resource.
resname
The resource name.
System Action: The system ends the command.
RACF security administrator to acquire the proper

authorization. Run the job again.
Source: DFSMSdfp
IDC2919I
INVALID URACHECK PARAMETER

LIST
Explanation: The parameter list passed to the

URACHECK macro is incorrect. The access method
services module which invoked the URACHECK macro
either set up the parameter list incorrectly or passed an
incorrect pointer to the parameter list. This is a system
error.
Source: DFSMSdfp
IDC2930I
** INVALID RACF AUTHORIZATION
Explanation: The data set to be scratched is

RACF-protected. The caller does not have the proper
RACF authorization to scratch the data set.
RACF security administrator to acquire the proper
Source: DFSMSdfp
IDC2950I
INVALID FORMAT STRUCTURE
Explanation: An element of one of the text format

structures is incorrect. If it does, it is a system error.
System Action: The system ignores the request to
print a line.
problem determination steps.
Source: DFSMSdfp
IDC2951I
OUTPUT COLUMN SPECIFIED OUT OF

RANGE
Explanation: An output column specified is outside

the print line width. This should not occur on a
checked-out access method services command.
System Action: The ignored this field and subsequent
fields.
problem determination steps.
Source: DFSMSdfp
IDC2952I
EXCESSIVE FIELD LENGTH FOR BD

OR PU CONV
Explanation: A binary to decimal or packed to

unpacked conversion length was specified as greater
than 15 characters. This should not occur in a valid
program.
System Action: The system uses the default.
Source: DFSMSdfp
345
IDC2953I
A REDO SUB-STRUCTURE IS NESTED
IDC2960I
NO PSWDFILE FOR dsname
Explanation: A redo structure cannot be defined within

the set of structures to be redone. This should not occur
in a valid program.
Explanation: A password protected data set was

found on the volume table of contents (VTOC) but no
DD statement was found with that data set name.
System Action: The current redo operation is ended.

All structures will be treated only once.

Source: DFSMSdfp
IDC2954I
STATIC TEXT ENTRY REQUESTED

NOT IN MODULE
Explanation: A static text request indicated an entry

that was not in the specified module. This should not
occur in a valid program.
System Action: The system does not honor the
request.
Source: DFSMSdfp
dsname
The data set name.
Application Programmer Response: Provide a DD
statement with the name of the data set. Specify the
name of the DD statement on the PASSWORDFILE
parameter. Run the command again.
Source: DFSMSdfp
IDC2961I
{FROM|TO} VOLUME volser CONTAINS

NON-VSAM DATA SETS
Explanation: The command requires that no

non-virtual storage access method (VSAM) data sets
can reside on the specified volume. However, a format
1 DSCB was found for a non-VSAM data set.
IDC2955I
INVALID PACKED DECIMAL FIELD
Explanation: A conversion request for packed to

unpacked found a digit that was not in the range 0 to 9.
The input data may be wrong. This occurs when an
incorrect field is being printed.
System Action: Conversion stops. Previously
converted data will be printed.
Application Programmer Response: Check the input
data.
FROM|TO
Indicate which volume contains the data set for
those commands that process more than one
command.
volser

Source: DFSMSdfp
Source: DFSMSdfp
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
346
or, if not specified on the command, in the VSAM

catalog in the STEPCAT, JOBCAT, master catalog
hierarchy.
volser

Source: DFSMSdfp
Source: DFSMSdfp
IDC2965I
IDC2963I
Explanation: An error occurred reading or updating

the volume table of contents (VTOC) so that no more
data sets could be scratched. The virtual storage
access method (VSAM) ownership flag has been set off
in the VTOC.
FORMAT 4 DSCB NOT FOUND ON

VTOC OF {FROM|TO} VOLUME
Explanation: The program positioned to the first

record in the volume table of contents (VTOC) of the
volume but it was not a Format 4 DSCB.
FROM|TO
Indicate which volume encountered the error
for the commands that process more than one
volume.
Application Programmer Response: This probably
indicates an access method services error. Possibly the
VTOC has been destroyed. Attempt to list the VTOC
using the IEHLIST utility, and reconstruct the VTOC.
Source: DFSMSdfp
IDC2964I
** SCRATCH OF DATA SETS NOT

PERFORMED
Explanation: An error occurred which prevented any

data set from being scratched. The volume is still
marked as virtual storage access method (VSAM)
volume. A preceding message indicates the specific
error.
Application Programmer Response: Run
AMASPZAP service aid program to alter the volume
table of contents (VTOC) if any VSAM data sets are on
the volume and the VSAM data sets have been
recataloged. If the volume is not a VSAM volume, use
the IEHPROGM utilitys SCRATCH VTOC statement.
ATTEMPT TO SCRATCH DATA SETS

TERMINATED
System Action: The system does not make any

further attempts to scratch a data set. The command
AMASPZAP service aid program to alter the VTOC if
the VTOC contains VSAM data sets and the data sets
have been recataloged. If the volume is not a VSAM
volume, use the IEHPROGM utilitys SCRATCH VTOC
statement.
Source: DFSMSdfp
IDC2966I
RECATALOGING OF NON-VSAM DATA

SETS NOT PERFORMED
Explanation: An error occurred which prevented any

non-virtual storage access method (VSAM) data sets
from being recataloged. A preceding message will
indicate the specific reason for the error.
system performs no further function.
IEHPROGM utility or the access method services
DELETE and DEFINE commands to recatalog the data
sets. If the error recurs and the program is not in error,
look at the messages in the job log for more
Support Center. Provide the JCL, the SYSOUT output
for the job, and all printed output and output data sets
Source: DFSMSdfp
347

IDC2967I
ATTEMPT TO RECATALOG NON-VSAM

DATA SETS TERMINATED
Explanation: An error occurred after some data sets

were recataloged. A preceding message indicates the
specific reason for the error.
System Action: The system does not recatalog any
more non-virtual storage access method (VSAM) data
sets. The command terminates normally. The system
does not perform any further function.
IDC2972I
LSPACE ERROR. LSPACE RETURN

CODE WAS return-code.
Explanation: The LSPACE macro failed to return

volume free space information for a LISTDSET space
usage report.
return-code
Application Programmer Response: List the catalog

to determine which data sets were recataloged or, if the
LIST parameter was specified, examine the SYSPRINT
listing to see which data sets were recataloged.
Recatalog the data sets not previously recataloged
using the IEHPROGM utility or the access method
services DELETE and DEFINE commands.
The return code, as follows:

Code
Explanation
An I/O error occurred while

reading the DSCBs.
The last allocation of the

volume was made under
DOS.
12
The user control block (UCB)

address is incorrect. The
UCB is not for a
direct-access device, or the
UCB-not-ready bit is on,
indicating the device is not
ready.
16
Indicates an incorrect
message area address or
system management facility
(SMF) indicator.
Source: DFSMSdfp
IDC2971I
RESERVE FOR VOLUME volser NOT

SUCCESSFUL
Explanation: The reserve with the HAVE option

returned an unsuccessful condition code.
volser
System Action: The command ends processing.

command again.
Source: DFSMSdfp
System Action: The volume is not processed. The

system processes other specified volumes.
Application Programmer Response: Determine why
the LSPACE macro failed. Message IDC2108I follows
this messages and identifies the failing volume.
Source: DFSMSdfp
IDC2973I
VTOC ON volser, VOLUME TO BE

COPIED, IS IN ERROR
Explanation: Either an error occurred when the

volume services routine attempted to redefine a
format-5 data space control block (DSCB) or the DIRF
bit is on in the format-4 DSCB. The DIRF bit is used to
detect a system failure or permanent I/O error while the
volume table of contents (VTOC) is being updated.
volser
System Action: Instead of attempting to copy only
348
allocated cylinders, the system makes a copy of all

cylinders of the volume.
VTOC is not in error. Try to list the VTOC using the
IEHLIST utility program.
Source: DFSMSdfp
IDC3003I
FUNCTION TERMINATED. CONDITION

CODE IS cde.
IDC3006I
FUNCTION TERMINATED DUE TO

BEGINNING POSITIONING ERROR
Explanation: An error occurred when positioning to a

record in a data set was attempted. The position
indicator may be beyond the limits of the data set or an
I/O error may have occurred in positioning. An I/O error
message may have been printed.
System Action: The system ends the operation.
positioning parameter value. See the I/O error message
description for the I/O error indicated ahead of this
message.
Explanation: The system writes this message when

an error condition has occurred in the processing of a
functional command. Messages printed just before this
message in the program listing indicate the error that
occurred.

Source: DFSMSdfp
cde
The condition code of the abnormally ended

function.

the next command. The system sets LASTCC to the
condition code. The system also sets MAXCC if the
condition code is greater than the current MAXCC
value.
IDC3007I
VSAM CATALOG RETURN-CODE IS

return-code
Source: DFSMSdfp
Explanation: This condition code was returned as the

result of a catalog error or exceptional condition. The
system uses this message only when a more
specifically worded message does not exist. In most
instances, a subsequent message will indicate the
action taken for the command that encountered the
condition.
Application Programmer Response: Preceding

messages indicate the appropriate programmer
response.
return-code
IDC3004I
FUNCTION TERMINATED.
INSUFFICIENT MAIN STORAGE.
Explanation: The region size was not large enough to

process a functional command.
the next command.
size of the storage allocated.
for the job.
Source: DFSMSdfp
IDCDE01, IDCED02, IDCLC01, IDCMP01, IDCPR01,
IDCRC01, IDCRM01, IDCRP01, IDCRS05, IDCVY01,
IDCXP01
The return code. It may be either a

virtual storage access method (VSAM)
return code or a control volume
(CVOL) processor return code. To
determine which, determine whether
the entry name specified in the
command was directed to a VSAM
catalog or a CVOL catalog. For a
return code to be a CVOL return
code, the entry name specified in the
command must be qualified; and the
first qualifier must be identical to an
alias entry in the master catalog. The
alias entry must be related to a
non-VSAM entry of the form
SYSCTLG.
The CVOL processor return codes follow. The VSAM

catalog return codes are listed with message IDC3009I,
where they appear together with reason codes. For
message IDC3007I, ignore the VSAM return codes:
Code
Explanation
349
Cannot allocate catalog, catalog does not exist,

or is not open.
The data set does not exist, or a CVOL

contains a CVOL pointer or generation data
group (GDG) alias, or the entry name
duplicates an existing name.
20
There is insufficient space in the CVOL data

set.
24
LOCATE operation - Permanent I/O error,

unrecoverable error, or nonzero return code
from ESTAE. The CVOL processor issues the
ESTAE.
28
Non-LOCATE operation - Permanent I/O error,

unrecoverable error, or nonzero return code
from ESTAE. The CVOL processor issues the
ESTAE.
44
All eligible entries could not be listed by the

LISTCAT function. LISTCAT can handle a
maximum of 1,456 entries.
48
Function inconsistent with CVOL processor.
56
An attempt to delete an entry failed because

the DELETE command specified SCRATCH,
but password verification failed for the
password protected data set.
84

the DELETE command specified SCRATCH
without PURGE, but the expiration date of the
data set has not been reached.
102

but the data set is defined to RACF and the
accessor is not authorized to it.
164
There is insufficient virtual storage available for

a CVOL catalog management work area.
168

but the device type of the cataloged volume
did not match the user control block (UCB)
device type.
184

but the data set is currently open and cannot
be scratched.

Application Programmer Response: Respond
according to the return code, as follows:
Code
Response
Ensure that the CVOL is mounted. Verify the

use of the STEPCAT and JOBCAT JCL or of
the ddname DD statement.
Check that the entry name is spelled correctly.

Verify the use of JOBCAT and STEPCAT
catalogs, if employed.
20
See your system programmer for assistance in

reorganizing the CVOL.
24
Have the volume restored or try mounting the

volume on a different device.
28
Have the volume restored or try mounting the

volume on a different device.
44
Change the LEVEL or ENTRIES parameter of

the LISTCAT command to limit the number of
eligible entries to 1,456.
48
Verify the use of JOBCAT and STEPCAT

catalogs, if employed, to ensure that the
catalog being acted upon is appropriate to the
action you are attempting.
56
Message IEC301A has been printed until the

maximum number of attempt is exceeded.
Provide the operator with the correct password.
Run the job again.
84
Specify the PURGE option, if desired. Run the

job again.
102
Get authorization for the data set. Run the job

again.
164
Increase the region size for the step.
168
If the data set was cataloged using an esoteric

device type, such as SYSDA, a non-standard
device type is cataloged, such as, 000B2000.
To delete the entry, use the access method
services DELETE command with NOSCRATCH
specified. Then, to scratch the data set, specify
DISP=(OLD, DELETE), or IEHPROGM to
scratch the data set.
184
Run the job again. To ensure proper

completion, specify a disposition of OLD, not
SHR.

Source: DFSMSdfp
Detecting Module: IDCAL01, IDCDE02, IDCMP01,
IDCRM01, IDCTR01
IDC3008I
FUNCTION IS NOT SUPPORTED IN

THIS ENVIRONMENT
Explanation: A request for prompting or data set

name qualifying has been received while not in a Time
Sharing Option/Extensions (TSO/E) environment.
350

Source: DFSMSdfp

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.
The list of return codes and reason codes follows:

RETURN CODE 4
Explanation: Catalog management returned this

return code and reason code as a result of a catalog
error or exceptional condition.
Explanation: The system encountered an error while

performing open/close processing for a catalog. If the
catalog is being accessed dynamically (e.g. no JOBCAT
or STEPCAT DD statement in the JCL), dynamic
allocation may have failed because the volume is
allocated exclusively. The volume may be allocated
exclusively due to one of the following:
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.
IDC3009I
VSAM CATALOG RETURN CODE IS

return-code - REASON CODE IS
IGGOCLaa - reason-code
For an explanation of the return and reason codes,

check below to:
v Find the underlined heading for the return code.
v Scan for the associated reason code.
If you are using BookManager, to quickly find the
explanation of the return and reason codes, enter the
search argument:
v Previous access method services command in the

job step needed to demount the volume and changed
the allocation of the volume to exclusive.
Reason
Code
x
IDC3009I rtn rsn

Do not specify leading zeros. For example, for message
IEC331I 004-33,XXXXXXXX,YYYYYYYY,OPN VSM ACB,ZZZZZZZZ
search for
IDC3009I 4 33
If the search takes you to a description of the reason
code x, it means the reason code you received is one
of a group of reason codes having a common
description. Most of these represent internal logic errors
and they will indicate you should contact the IBM
Support Center.
Source: Data Facility Product (DFP)
System Action: The system ends processing
associated with the error return code.
programmer response for the specific return code and
reason code. Inspect other messages concerning
DADSM or open/close to aid in solving this problem. If
necessary, contact your programming support
personnel.
Description
Explanation: An internal error has
occurred during Catalog processing.
Programmer Response: Contact the
IBM Service Center. An SVC dump may
have been produced for this error.
Explanation: An error occurred while
opening a new catalog that is being
defined, or the master catalog.
Programmer Response: Check for
open/close problem determination
messages in the job stream output.
Explanation: A request has referenced
a catalog while catalog management is
processing, or after catalog management
has processed, an access method
services DELETE command for the
specific catalog.
Programmer Response: The catalog
needed for the request has been
deleted. If needed, the catalog must be
redefined before attempting the request
again.

351
Reason
Code
8
23
25
26
27
30
31
32
Description
Explanation: An incorrect access
method control block (ACB) was
supplied to catalog management for a
catalog to be used during a catalog
request.
Programmer Response: Contact your
Explanation: While performing a
GETMAIN from the requested subpool,
the VSAM volume data set (VVDS)
manager protocol module returned an
error.
Programmer Response: Increase the
size of the CSA or run the job again
when more CSA is available.
Explanation: Unable to get CSA storage
(subpool 241).
Reason
Code
34
60
83

size of CSA or run the job when more
CSA is available.
Explanation: Unable to get storage for
scheduler workarea (subpool 252).
REGION size.
Explanation: Unable to get CSA for
catalog (subpool 241).
size of CSA or run the job when more
CSA is available.
Explanation: Unable to get in subpool
252.
REGION size.
Explanation: The VVDS manager
encountered an error processing a
VSAM volume record (VVR) request.
Explanation: The system was unable to
complete verification that the required
volume is mounted.
84
85
86
Programmer Response: Ensure that

the unit is available for mounting and
that the correct volume is mounted.
102
Description
Explanation: An attempt to open a
catalog could not find the VVR record for
the catalog.
Programmer Response: It is possible
that the catalog name is still defined in
the master catalog but does not
physically exist on the expected volume.
This is usually a result of reinitializing
the volume without doing an EXPORT
DISCONNECT of any user catalogs on
the volume.
Explanation: Unable to get storage in
subpool 252 (for EOV) or in subpool 253
(for CLOSE).
REGION size.
Explanation: The catalog has been
deleted, and CAXWA is still on the chain
until all jobs allocated to it end or logoff.
Programmer Response: Do not use the
catalog, or a new catalog with the same
name, until all jobs allocated to the old
catalog end or logoff.
Explanation: CAXWA count of active
users has reached 32767, the maximum
allowed.
Programmer Response: Do not use the
catalog until one of the current jobs
allocated to it ends or logs off.
Explanation: Unable to get CSA for the
catalog ACB or for the PCTT (subpool
241)
size of the CSA or run the job when
more CSA is available.
opening the catalog.
Programmer Response: See
associated message IEC161I and/or
IEC331I for information about the OPEN
error. The catalog might be damaged.
Run the DIAGNOSE or EXAMINE
command to analyze the catalog.
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.
352
Reason
Code
104
106
108
114
118
Description
Explanation: A necessary catalog could
not be dynamically allocated in the
catalog address space, and the catalog
parameter list indicated dynamic
allocation in the callers address space
was not allowed.
allocation problem determination
Follow the programmer response for
these messages.
was not allowed.
these messages.
was not allowed.
these messages.
Explanation: A a catalog needed for the
request could not be allocated to the
Catalog address space, and the caller
did not request it be allocated to the
callers address space.
Programmer Response: When a
catalog cannot be dynamically allocated
to the Catalog Address Space, it must
be allocated to the user address space
before the catalog request is issued.
Explanation: The catalog needed for
this request has been deleted.
Programmer Response: Redefine the
deleted catalog and reissue the request.
Reason
Code
120
122
Description
Explanation: The master catalog
connector record was not found for the
named catalog.
Programmer Response: Enter the
access method services LISTCAT
command to display the entries in the
master catalog. If the user catalog is not
listed, enter the access method services
IMPORT CONNECT command to
connect the catalog. If the user catalog
data set name is listed, ensure that the
entry is for a user catalog.
Explanation: The master catalog
connector record was not found for the
named catalog.
Programmer Response: Enter the
access method services LISTCAT
command to display the entries in the
master catalog. If the user catalog is not
listed, enter the access method services
IMPORT CONNECT command to
connect the catalog. If the user catalog
data set name is listed, ensure that the
entry is for a user catalog.
RETURN CODE 8
Explanation: The entry does not exist, if action is one
that locates the entry. The entry already exists, if action
is one which adds an entry to a catalog.
Reason
Code
0
Description
Explanation: An entry was not found on
LOCATE REQUEST.
the proper entry was specified.
Explanation: The catalog cluster record
was not found.
Programmer Response: Call your
Explanation: No record was found from
record management.
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
Code
8
12
14
16
18
20
Description
Explanation: A request to place a
record by key into a catalog resulted in a
duplicate key error from VSAM.
the entry name is spelled correctly and
that the proper catalog is being used.
Explanation: An incorrect entry type
occurred for super-locate on the entry
named. The data set was not found in a
catalog.
the proper data set name was specified
in the job control language DD
statement.
Explanation: A generation data group
(GDG) entry type for super-locate did not
find the specified entry in a catalog.
|
|
|
|
|
|
|
Reason
Code
38
|
|
|
|
|
|

statement.
Explanation: A GDG entry was found to
be deleted from a catalog.
statement.
Explanation: A GDG type of
super-locate request specified an
incorrect generation number.
statement.
Explanation: The volume entry being
removed from an catalog entry during
ALTER REMOVEVOLUMES processing
cannot be found the catalog record.
Programmer Response: Verify that the
volume serial numbers specified actually
exist in the catalog entry for the data set
being altered.
40
42
44
46
50
Description
Explanation: During an attempt to add
an entry to a catalog, either a duplicate
name or an alias that matches one or
more level of qualification of the new
name was found in the target catalog.
See section on Multi Level Alias Facility
in your Managing Catalogs manual.
Programmer Response: In the DEFINE
command, specify a name that does not
already exist in the target catalog. In the
case of a DEFINE ALIAS, make sure
there are no datasets that currently exist
with that same high-level qualifier.
Explanation: A DEFINE GDG command
was not issued prior to the DEFINE
NONVSAM command with GDG entry
name.
the GDG base is defined prior to
defining the non-VSAM with a GDG
entry name.
Explanation: The catalog record for the
requested entry could not be found.
the entry name specified on the access
method services command is in the
catalog specified.
Explanation: A request to place a
record by key into an ICF catalog
resulted in a duplicate key error from
VSAM.
the entry name is spelled correctly and
that the proper catalog is being used.
Explanation: A base record was not
found upon deletion of a cluster, AIX or
GDG in an ICF catalog.
Programmer Response: Run the
DIAGNOSE command to analyze the
catalog. The ICF catalog may have to be
restored or rebuilt.
Explanation: A record was not found
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.
354
Reason
Code
52
54
Description
Explanation: A duplicate data
component name was found.
Reason
Code
10
Programmer Response: Ensure that all

data component names are unique and
run the job again.
Explanation: A duplicate index
component name was found.
Description
Explanation: An incorrect VSAM volume
record was read from the VSAM volume
data set and was detected while
modifying the catalogs VSAM volume
record.
Programmer Response: Perform the
following steps:
1. Try accessing the catalog from
another system, if shared.
Programmer Response: Ensure that all

index component names are unique and
run the job again.
2. Run DIAGNOSE or EXAMINE from

either system.
RETURN CODE 10
3. Use catalog address space (CAS)

commands to refresh control blocks.
Explanation: An incorrect record type was found.
4. IPL will refresh control blocks if CAS

is not available.
Reason
Code
x
Description
Explanation: A record being processed
contained inconsistent or incorrect data
for the type of entry.
DIAGNOSE command to check for a
damaged catalog record. A SYS1.DUMP
may have been produced for this error.
Explanation: An incorrect record type is
found when trying to find a subrecord to
be moved.
12
14

damaged catalog record.
20
42
50
5. If the above steps show actual

damage, rebuild or restore the
catalog. Use the MODIFY
CATALOG,CLOSE command if
necessary.
Explanation: The record type for a data
set was found to be incorrect during
reset of a reusable data set.
the target of a reset is a VSAM data set.
Call your programming support
personnel.
Explanation: On a disconnect request,
the connector record was missing or
incorrect.
DIAGNOSE command to determine if
the user catalog connector record is
damaged and take the recommended
action.
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.
Explanation: A VVDS record contained
inconsistent data.
damaged VVDS record.
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
Code
x
Description
Explanation: A required component was
not found within a catalog record.
Reason
Code
4-10,98

damaged catalog record. A SYS1.DUMP
may have been produced for this error.
Description
Explanation: An ALTER for a migrated
data set was issued, but the call to
DFSMShsm failed. The reason-code
code is from DFSMShsm.
Programmer Response: Refer to
DFSMShsm message ARC0073I in
(ASB-ERB) for an explanation of the
reason code and take the appropriate
action.
RETURN CODE 14
Explanation: A required cell has not been found in a
catalog record when expected.
RETURN CODE 20
Reason
Code
x
Description
Explanation: A required cell was not
found in a catalog record during
processing.
access method services DIAGNOSE
command to check for a damaged
catalog record. A SYS1.DUMP may have
been created.
Explanation: There is insufficient space in the catalog

to perform the requested update or addition.
Reason
Code
0
RETURN CODE 18
Programmer Response: Scratch

unneeded data sets from the volume.
Delete all unnecessary entries from the
catalog. The catalog may need to be
reallocated and rebuilt if these steps do
not resolve the space shortage.
Explanation: An ALTER error occurred.
Reason
Code
0
Description
Explanation: A system request to alter
the backup-while-open (BWO) options
specified an inconsistent or unsupported
state.
Programmer Response: This is most
likely an invalid catalog parameter list.
Contact the IBM Support Center.
Explanation: An attempt to alter a data
sets storage class name or
management class name has fail
because DFSMShsm was not active.
The system found incorrect data for an
alter of a backup while the backup was
open.
Programmer Response: Verify
DFSMShsm is operational and retry the
request.
356
Description
Explanation: The catalog is full. It is
impossible to obtain another extent,
because there is no more space on the
volume in which the catalog resides, or
the maximum number of extents has
been reached.
RETURN CODE 22
Explanation: The Field Vector Table (FVT) address is
zero or an incorrect FVT field was found.
Reason
Code
x
Description
Explanation: An invalid structure was
passed as input to a catalog request.
IBM Support Center.
RETURN CODE 24
Explanation: Permanent read error of a catalog.
Reason
Code
2
Description
Explanation: An I/O error occurred while
attempting to read information from the
catalog.
Programmer Response: Messages
IEC331I, IEC332I, and IEC333I have
been printed to aid in determining the
cause of the error and where the error
occurred. If a hardware error is not
causing the problem, restore or rebuild
the catalog.
Reason
Code
4
RETURN CODE 26
Explanation: A VSAM record management error has
occurred.
Reason
Code
x
Description
Explanation: A VS record management
error occurred while processing a
catalog request.
IBM Support Center. An SVC dump will
be created for this error.
26
28
RETURN CODE 28
Explanation: Permanent I/O error in catalog.
30
Reason
Code
2
Description
Explanation: An I/O error processing
the catalog occurred while processing an
access method services command that
requires modifying the catalog.
Description
Explanation: An I/O error occurred
during catalog OPEN.
the catalog.
Explanation: One or more entries were
not deleted due to an I/O related error
during DELETE processing.
the catalog.
Explanation: An I/O error occurred while
writing the catalogs self-describing
records.
IBM Support Center.
Explanation: A close error occurred
after the writing of the catalogs
self-describing records.
IBM Support Center.
Explanation: An I/O error occurred
writing records to the catalog.
IBM Support Center.
RETURN CODE 30
the catalog.
Explanation: Automated Tape Library Data Server

(ATLDS) processing error.
Reason
Code
x
Description
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
Code
6
18
20
22
34
40
42
44
46
Description
Explanation: Attempt to define an alias
that relates to a volume category.
Programmer Response: This is an
incorrect function. Possible user error.
Explanation: The required library name
was not specified for a define library
request.
Programmer Response: Supply a
library name and rerun the job.
Explanation: Required library id was not
specified for a define library request.
library id and rerun the job.
Explanation: The library logical type
specified is incorrect for a define library
record request.
Programmer Response: Supply a valid
library logic type and rerun the job.
Explanation: Incorrect name was
specified for a define volume category
request.
Programmer Response: The volume
categorys name must begin with
SYS1.VOLCAT.V.
Explanation: Incorrect checkpoint
indicator was specified for a define
volume request.
checkpoint indicator and rerun the job.
Explanation: Incorrect volume location
was specified for a define volume
request.
Reason
Code
48
50
56
Description
Explanation: Required volume name
not specified for a define volume
request.
volume name and rerun the job.
Explanation: Incorrect date format
specified.
Programmer Response: Respecify the
date in the following format:
YYYY-MM-DD.
Explanation: Attempt to alter the
number of scratch volume message
thresholds for an incorrect media type.
58

media type and rerun the job.
Explanation: Attempt to alter the
number of scratch volumes for an
incorrect media type.
60

media type and rerun the job.
Explanation: JOBCAT/STEPCAT was
specified for a request associated with
volume or library record.
62
68

volume location and rerun the job.
Explanation: Required library name not
specified for a define volume request
with a volume location of library
specified.
Explanation: Incorrect volume use
attribute specified for a define volume
request.
70

use attribute and rerun the job.
72
Programmer Response: Remove

JOBCAT/STEPCAT and rerun the job.
Explanation: No general volume
category was found.
Programmer Response: Define
SYS1.VOLCAT.VGENERAL then rerun
the job.
Explanation: Non-volume category was
specified for a request associated with
volume or library record.
Programmer Response: Insure
SYS1.VOLCAT.VGENERAL is a volume
category for library requests. For volume
entry requests, check all catalogs with
volume category naming convention to
be volume categories.
Explanation: A duplicate entry name
was found during define library or
volume request.
Programmer Response: Remove the
duplicate entry and rerun the job.
Explanation: General volume category
had been deleted or disconnected.
Programmer Response: Redefine or
reconnect general volume category.
358
Reason
Code
98
154
Description
Explanation: Incorrect library name
specified for a define library request. The
library name cannot begin with V.
Reason
Code
2

Explanation: Attempting to delete a
library record which is not empty, or
scratch volumes is not equal to zero.
4
158
168
Programmer Response: Verify the

library record tried to delete. If the library
record is empty and the scratch volumes
count equal to zero then contact the IBM
Support Center
volume record that has not reached its
expiration date.
Programmer Response: Verify the
expiration date. ALTER command may
be used to alter the expiration date.
record without specifying the correct type
in catalog parameter list.
Programmer Response: Specify the
type and rerun the job.
12
Description
Explanation: An incorrect record type
was found in the access method
services ALTER command.
Programmer Response: Determine if
the correct name was specified in the
command or if the proper fields are
requested to be modified for the entry
type.
Explanation: A data set name was not
found on the VTOC.
the proper versions of the volume and
catalog are being processed and that the
volume is synchronized with the catalog,
or ensure that the VVR/NVR entry type
in the VVDS matches its corresponding
format 1 DSCB record type from the
VTOC.
Explanation: A super-locate request to
catalog management requires dynamic
access to a catalog.
Programmer Response: If this error
causes a job to end, ensure that the
master catalog references the proper
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
list. Such a condition indicates an internal error in
access method services (IDCAMS).
Reason
Code
x
Description
occurred.
RETURN CODE 38
Explanation: The catalog installation exit module,
replaced by an installation-supplied module,
encountered an error while processing an SVC 26
request. If the module was supplied by the data facility
hierarchical storage manager (DFHSM), the message
with this return code was preceded by one or more
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
Code
2
Description
Explanation: An error was encountered
while attempting to recall a data set with
a volume serial of MIGRAT. The catalog
entry indicated that the data set was
migrated, but DFHSM determined that
the data set was not migrated.
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.
while attempting to recall a data set with
a volume serial of MIGRAT (the catalog
migrated).
Reason
Code
12
16

log.
while attempting to delete a data set with
a volume serial of MIGRAT (the catalog
migrated).
log.
24
Description
Explanation: The catalog installation
exit module issued a locate request, and
catalog indicated that the request was
not successful.
log.
exit module was processing a JES3
converter/interpreter (C/I) request for a
data set with a volume serial of MIGRAT
(the catalog entry indicated that the data
set was migrated). The exit module
determined that DFHSM was not ready
to process the JES3 C/I request
because of one of the following:
v DFHSM was not active
v DFHSM did not have volumes defined
to which the migrated data set could
be recalled
v The storage management subsystem
was not available to determine the
storage class for a migrated
SMS-managed data set
v The recall exit was inoperable
log.
exit module was processing a JES3 (C/I)
request for a data set, and determined
that the request was from an
unauthorized user.
log.
360
Reason
Code
48
RETURN CODE 44
Description
Explanation: The referenced data set is
in an incomplete status.
Programmer Response: Recall the
data set and then issue your request
again.
Explanation: The catalog work area for returning

results of a catalog request is too small to contain all of
the requested results. If you are using the Catalog
Search Interface (CSI) you need to increase the size of
the work area you provide for the request. Other
occurences of this problem may indicate logic errors in
components or products that use catalog services.
RETURN CODE 40
Explanation: The volume list or work area is too small.
This return code would normally represent an error in
the calling program. If the user is using the Catalog
Search Interface, this return code indicates that a large
enough return workarea was not provided.
Reason
Code
0
Description
Explanation: The user provided work
area is too small.
Reason
Code
2
Programmer Response: Run the job

again with a work area length that is at
least equal to the required length.
Explanation: The format 1 work area is
too small.
again with a work area length that is at
least equal to the required length.
Explanation: The volume list is too
small to include the storage
management subsystem workarea.
RETURN CODE 42
4
6
Description
Explanation: A DADSM RENAME error
occurred on branch entry.
Explanation: A DADSM ALLOCATE
error occurred on branch entry.
Explanation: A DADSM SCRATCH error
occurred on branch entry.
Programmer Response: Check the

work area length. If it is correct, contact
the IBM Support Center. If the length is
not correct, run the job again with a valid
length.
Explanation: The callers work area is
too small.
Programmer Response: If this is a
Catalog Search Interface (CSI) request,
you need to increase the size of the
work area. Otherwise, this may be a
logic error or limitation in the component
making the request.
Explanation: An access method
services DELETE command to delete an
entire generation data group, with the
FORCE parameter, encountered a work
area too small to contain names of
entries deleted. However, the entire
GDG was successfully deleted. The
following then occurs:
1. The work area is not large enough to
return the name of the generation
data base.
Explanation: A DADSM error occurred on branch entry

to DADSM back end. The DADSM error return data
from the invoked sub-function (SFI) field is the value of
the variable sfierror in message IEC331I.
Reason
Code
2
Description
Explanation: The delete catalog work
area is too small.
2. The system does not delete the

catalog.

again with a larger work area.
Explanation: The callers work area is
too small.
Programmer Response: If this is a
Catalog Search Interface (CSI) request,
you need to increase the size of the
work area. Otherwise, this may be a
logic error or limitation in the component
making the request.
361
Reason
Code
12
Description
Explanation: The amount of data that
the system will return may overflow the
workarea.
Programmer Response: Either divide
the catalog into smaller catalogs or
convert to the ICF catalog format.
Explanation: The amount of data
returned by the system cannot be
contained in a 2-byte length field.
14
Programmer Response: None. This is

a design limitation. If you are using the
CSI (Catalog Search Interface), you
must request that fullword lengths be
used for all lengths.
Reason
Code
14
16
Reason
Code
x
18
24
Programmer Response: Do not attempt

the incorrect ALTER commands. Correct
the commands and rerun the job.
Explanation: It is not valid to attempt to
change the name of a user catalog or
alias entry through the use of the access
method services ALTER Command.
10
Description
occurred.
IBM Support Center.
Explanation: An ALTER of a non-VSAM
entry is not allowed for the fields being
modified.
the proper entry name was specified on
the access method services ALTER
command and that only fields that exist
for a non-VSAM entry are requested to
be changed.
Explanation: An ALTER of the catalog
name is not allowed.
the catalog name was not used by
mistake. Catalog names can only be
changed by DELETE and then
re-DEFINE catalog commands.
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.
362
Programmer Response: Do not open a

data set for reset processing that is
inhibited for update processing.
Explanation: A data set is not reusable.
non-empty data set for reset processing
that is not reusable.
Explanation: It is only valid to change
the attributes or ownerid fields of a GDG
base entry by the access method
services ALTER command.
RETURN CODE 48
Explanation: Incorrect catalog function.
Description
Explanation: A data set is update
inhibited.
26
28
29

change the name of a non-VSAM entry
that is a GDG base or member through
the use of the access method services
ALTER command.
delete a GDG base entry that contains
non-VSAM entries.
Programmer Response: Delete the
members of the GDG base explicitly.
Alternatively, the GDG base and its
members may be deleted with the use of
the FORCE parameter in the DELETE
command.
Explanation: RBA too large for data set.
Reason
Code
30
36
40
42
Description
Explanation: It is not valid to delete the
master catalog with the FORCE
parameter. If the user catalog is being
force-deleted, a stepcat or jobcat card
may be missing or specifies the wrong
catalog.
Programmer Response: The master
catalog cannot be deleted. To delete the
user catalog, correct the stepcat or
jobcat card. Submit the job again.
Explanation: The ALTER
REMOVEVOLUMES volume cleanup
function contains incorrect coded
parameters.
Programmer Response: Only the
master catalog name, password, and file
parameters may be coded for the ALTER
REMOVEVOLUMES function.
Explanation: An incorrect catalog
management function, ALTER of a VVDS
name, occurred.
the commands. Run the job again.
Explanation: The maximum number of
extensions was exceeded.
Reason
Code
64
70
72
74
76
78
80
54
56

catalog with a RECORDSIZE specifying
a maximum of 32400.
Explanation: An incorrect reset of a
non-reusable data set was detected.
non-empty data set for reset processing
that is not reusable.
Explanation: The data set update is
inhibited.
90
94
96
98
60

data set for reset processing that is
inhibited for update processing.
Explanation: A define no-allocate or
RECATALOG was not APF authorized.
Programmer Response: Probable user
error. Ensure that access method
services is APF authorized.
102
104
108
112
Description
Explanation: A DEFINE of a
SYS1.VVDS.Vvolser cannot request
space in records.
Programmer Response: Change
records to tracks or cylinders. Run the
DEFINE command again.
Explanation: An ALTER LOCK of the
master catalog is not allowed.
Explanation: An incorrect catalog
management function alter of a
non-VSAM data set name that is
cataloged with an indirect volser
occurred.
Explanation: An alter newname of a
tape data set is incorrect.
the commands. Run the job again.
Explanation: An alter of non-VSAM data
set that contains the extended format
cell is not allowed.
Programmer Response: None
Explanation: The conversion of SMS to
non-SMS managed cannot be done for a
data set that contains the extended
format cell.
Explanation: Define data set with
extended format information is not valid
for a non-SMS data set.
Explanation: Recataloging a temporary
VSAM data set is not allowed.
Explanation: The conversion of SMS to
non-SMS managed cannot be done for a
data set that contains attributes
extension information.
Explanation: Define data set with
attributes extension information is not
valid for a non-SMS data set.
Explanation: A define of non-extended
data set that contains compress
information is not allowed.
Explanation: The request is against an
SMS-managed data set, but the
specified data set is not SMS managed.
Explanation: The user is not authorized
to issue ALTER no VVDS update.
Explanation: The specified SMS
construct cannot be altered.
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
Code
118
120
122
124
126
128
130
132
134
136
140
142
144
146
148
Description
Explanation: A SMS storage class
construct cannot be blanks.
Explanation: The ALTER NEWNAME is
not allowed for non-VSAM data set with
an alias when the new name resolves to
a different catalog than the current one.
Explanation: The ALTER NEWNAME is
not allowed for VSAM data set when the
new name resolves to a different catalog
than the current one.
be converted to SMS managed because
not all of the volumes belong to the
same storage group.
be converted to SMS managed because
not all of its associated names in the
sphere resolve to the same catalog.
Explanation: An SMS storage class
construct cannot have a length of zero.
Explanation: Altering a non-SMS
managed VSAM data set to an SMS
managed one (or vice versa) is a
stand-alone function. No other ALTER
functions are allowed.
Explanation: Altering a non-specific
volume serial to a specific one is a
stand-alone function. No other ALTER
functions are allowed.
Explanation: The caller is not
authorized to issue ALTER non-specific
volume.
Explanation: An incorrect component
was supplied for ALTER non-specific
volume.
Explanation: An ALTER GDG limit of 0
is not allowed.
Explanation: An ALTER fails due to
unsuccessful DADSM UPDATE function.
Explanation: A Record unit of allocation
not valid for linear data sets.
Explanation: The ALTER NONVSAM
RECATALOG function and the caller
pass SMS information for conversion,
but the caller is not authorized to use
this function.
Explanation: Alter request is not valid
for stand-alone function such as alter of
backup while open (BWO) data set.
the field requested to be altered is valid
for stand-alone function.
364
Reason
Code
152
156
158
160
162
166
168
170
Description
Explanation: An attempt has been
made to define a PDSE as a member of
a GDG base. PDSEs may not be a
member of a GDG base
Programmer Response: Be sure that
the IGDSMS00 parmlib member has
DSNTYPE default of PDS.
Explanation: The alter backup while
open (BWO) request is not for valid
component or record.
the BWO alter request is for cluster,
data, non-VSAM, or GDS only.
Explanation: The alter backup while
open (BWO) indicator is incorrect for
non-SMS managed datasets
the data set is SMS-managed.
Explanation: An attempt was made to
alter a non-SMS managed non-VSAM
data set to a name in the format of a
GDS (e.g. the name ends with
GnnnnVnn).
Programmer Response: Change the
name of the new data set to be a
non-GDS format name.
alter a non-SMS managed GDS to a
non-GDS name.
Explanation: An alter volume or device
type on OAM entries is not allowed.
alter an SMS-managed non-VSAM data
set to a GDS name (e.g. the name ends
with GnnnnVnn), but there is no GDG
base associated with the new name.
name of the new data set to one that
has an existing GDG base definition.
Explanation: When defining an OAM
data set, a generation data set low level
qualifier (i.e., G0000V00) or an
increment of a GDG number (i.e., +1) is
invalid.
Programmer Response: Use a name
other than the GDS low level qualifier or
a GDG increment number. Rerun the
define request.
Reason
Code
172
174
175
176
178
184
186
188
190
192
194
196
Description
Explanation: REUSE was specified for
a non-cluster component or a
component that had an AIX Associated
with it.
Explanation: ALTER REUSE was
specified for a cluster that has an AIX
defined over it.
Explanation: A DEFINE of a striped
data set specified REUSE, which is
invalid.
Explanation: ALTER REUSE was
specified for a cluster that contains a
KEYRANGE.
Explanation: ALTER-REUSE-ON and
ALTER-REUSE-OFF are mutually
exclusive. They cannot be active at the
same time.
Programmer Response: Only one
ALTER-REUSE bit should be set at a
time.
Explanation: Attempted to ALTER the
DDM file class attribute for other than a
CLUSTER or NONVSAM entry.
Explanation: Attempted to ALTER the
pointer to the last active record for other
than CLUSTER or NONVSAM entry.
Explanation: Attempted to ALTER DFM
attributes for a non-SMS data set.
attributes for other than a CLUSTER
entry.
attributes for other than a CLUSTER or
NONVSAM entry.
Explanation: A specific request to locate
an OAM data set was made and a data
set was found, but it is not an OAM data
set. name.
name of the data set desired is an OAM
data set.
Explanation: A specific request to locate
an OAM data set was made and a data
set was found, but it is not an OAM data
set. name.
name of the data set desired is an OAM
data set.
Reason
Code
200
202
204
216
218
222
Description
Explanation: The ALTER ADDVOL
function cannot be used to cause the
number of volumes of a SMS-managed
data set to exceed the maximum of 59
volumes.
Programmer Response: The maximum
allowable volumes for a SMS-managed
data set is 59. If this error was issued
incorrectly, contact the IBM Support
Center.
Explanation: A request to recatalog a
temporary non-VSAM data set is not
valid.
Programmer Response: Correct the
request. If the error recurs, contact the
IBM Support Center.
Explanation: HSM-INCOMPLETE-ON
and HSM-INCOMPLETE-OFF are
mutually exclusive. They cannot be
active at the same time.
Programmer Response: Only one
HSM-INCOMPLETE bit should be set at
a time.
Explanation: Define of ACCOUNT
information is invalid for
nonSMS-managed data sets.
the data set is SMS- managed and then
rerun the request.
Explanation: Alter of ACCOUNT
information is invalid for
nonSMS-managed data sets.
the data set is SMS-managed and then
rerun the request.
Explanation: Extended attribute (AX)
cell and ACCOUNT information are
mutually exclusive for define or alter
request.
the AX cell and ACCOUNT information
are not both specified during define or
alter of the 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
Code
x
Description
occurred, or an error has been detected
in the structure or contents of a VVDS.
Programmer Response: Run a
DIAGNOSE and print the VVDS
associated with the problem. These
errors will usually be accompanied by
additional console messages which
contain SFI information necessary to
diagnose the problem. Contact the IBM
Support Center.
Explanation: New catalog name added.
This is a normal return code returned
during the adding of a new VVR. The
associated catalog name of the VVR
was new to the VVDS and was added to
the VVCR/VVCN record.
Explanation: VVDS Manager parameter
list had incorrect information. This
attention error code does not effect the
operation of the request.
10

IBM Support Center.
Explanation: The VVDS required for
LISTCAT could not be accessed. The
missing data in the LISTCAT output will
contain Xs. The volume might be offline,
but a mount request is not automatically
issued for a LISTCAT operation.
Programmer Response: Ignore the
return code or ensure the volume is
online and available for the LISTCAT
operation.
Explanation: A requested VVR or NVR
was not found in the VVDS specified. sfi
in message IEC331I contains characters
5 through twelve of the requested VVR
name.
the volume serial numbers provided in
VOLUMES parameters and DD
statements are correct. If all the
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.
366
Reason
Code
7
11
Description
Explanation: One or more of the 3
required VVRs for a catalog was not
found. SFI in message IEC331I contains
the first 8 characters of the catalog
name whose VVR(s) was missing.
Programmer Response: Run
DIAGNOSE command against the VVDS
and correct any problem detected.
Explanation: A DEFINE command for a
VVDS has failed because a VVDS
already exists on the volume. No SFI
data.
Programmer Response: If the existing
VVDS is to be replaced, delete it before
defining the new VVDS.
Explanation: A dynamic allocation will
require a TIOT slot, but a search finds
none available. No SFI data.
IBM Support Center.
Explanation: Bad return code from
dynamic allocation issued from
DFSMS/MVS. SFI contains the SVC 99
reason code.
the VVDS name or the volume serial
number provided is correct. If an access
method services command was being
processed, ensure that all required FILE
parameters are supplied. Ensure that the
volume will be mounted and available by
providing a DD statement for the
volume.
Explanation: The caller of the VVDS
manager passed a volume serial number
in the parameter list and a UCB address.
The UCBs volume serial does not match
the parameter list volume serial. The SFI
contains the UCB volume serial while
the parameter list volume serial is in the
second field in the SFI data.
IBM Support Center.
Reason
Code
12
14
16
17
Description
Explanation: An attempt to allocate
space on a DASD volume has failed.
SFI contains the historical return code
from DADSM allocate.
there is enough space for the VVDS
data set being defined. The data set will
require a minimum of three to four
tracks. If space was available when the
error occurred, contact the IBM Support
Center.
Explanation: A request to delete a
VVDS has failed because the VVDS still
contained VVRs. SFI contains the RBA
of the first CI that contains a VVR.
Programmer Response: If the VVDS is
to be deleted, first delete the VSAM data
sets on the volume and then run the
DELETE command again. Or, if the
VVDS is to be recovered, run the
DELETE command again with the
RECOVERY parameter.
Explanation: No storage was available
for the VVDS manager work area. There
may be no SFI data because the
working storage for the VVDS manager
could not be obtained. Otherwise, SFI
will contain the register 15 return code
from the GETMAIN request.
Reason
Code
25
26
28

IBM Support Center.
Explanation: No storage was available
for VVDS manager buffers. SFI contains
xxxxzzzz where xxxx is the amount of
storage being requested and zzzz is the
register 15 return code from the
GETMAIN request.
Programmer Response: Increase
available LSQA storage. This error can
sometimes be avoided by decreasing the
region size.
30
Description
Explanation: An OBTAIN was issued to
read the F1 DSCB for an existing VVDS
and OBTAIN returned with an error. SFI
contains the register 15 return code from
OBTAIN.
Programmer Response: A failure to
obtain a DSCB for a VVR may indicate
either a damaged VVDS or the existence
of an orphan VVR. In either case, enter
the DIAGNOSE command to check the
integrity of the VVDS. Correct any errors
found as a result of using the
DIAGNOSE command.
Explanation: An OBTAIN was issued to
read the F1 DSCB for a new VVDS and
OBTAIN returned with an error. SFI
contains the register 15 return code from
OBTAIN.
Programmer Response: A failure to
obtain a DSCB for a VVR may indicate
either a damaged VVDS or the existence
of an orphan VVR. In either case, enter
the DIAGNOSE command to check the
integrity of the VVDS. Correct any errors
found as a result of using the
DIAGNOSE command.
Explanation: A call to VSAM end of
volume to extent the VVDS has failed.
SFI contains register 15 return code
from end of volume.
Programmer Response: There is
probably insufficient space on the
volume or in the VTOC to extend the
VVDS, in which case no more VSAM
data sets can be defined on that volume
until space is made available to extend
the VVDS. If sufficient space is available
at the time this error occurs, contact the
IBM Support Center.
Explanation: While updating the VVDS,
it was found to be full and needed to
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
Code
32
38
40
82
Description
Explanation: The VVDS is full
(maximum 65536 CIs). There is no SFI
data.
Programmer Response: If a VSAM
data set was being defined, use an
alternate volume. If a VVDS was being
defined, decrease the primary space
allocation.
Explanation: A DELETE command with
the NOSCRATCH parameter has been
issued for a catalog. The VVR for the
catalog was not deleted because the
catalog has data on the volume. SFI
contains the RBA of the first CI that has
a VVR owned by the catalog.
Reason
Code
85
86
87

the correct catalog is being used and
that the VVDS is correctly specified.
Explanation: A call to scratch the F1
DSCB from a volume has failed. SFI
contains the return code from the
scratch.
Programmer Response: It is possible
that a user other than the one issuing
the delete has an outstanding ENQ on
the VVDS. If this is the case, the ENQ
should be removed.
Explanation: The system discovered,
during synchronization processing of the
VTOC and VVR extents, that the number
of extents indicated for the data set in
the VTOC is more than the number
indicated in the VVR.
88
92
84
Programmer Response: Print the

VVDS and VTOC. Contact the IBM
Support Center.
Explanation: The system discovered,
during synchronization processing of the
VTOC and VVR extents, that the number
of extents indicated for the data set in
the VVR is more than the number
indicated in the VTOC.
94
Support Center.
Description
Explanation: During synchronization
processing of the VTOC and VVR
extents, the VVDS manager was unable
to read the DSCBS.
Support Center.
Explanation: The VVR for the VVDS
number of extents field is not valid; it
has more than 123 extents in it. SFI
contains the VVRs extent number.
VVDS. Contact the IBM Support Center.
Explanation: During open processing of
a data set, the system discovered that
the extent information in the VVR does
not match the extent information in the
DSCB.
Programmer Response: Use LISTCAT
and LISTVTOC statements to determine
the mismatch. Delete the data set, then
define and reload it.
Explanation: A VVR or NVR with the
correct component name was found, but
the catalog name did not match. On a
delete request, the BCS record will be
deleted, but the VVR or NVR and the
format 1 DSCB will not be scratched.
There is no SFI data.
Programmer Response: No action is
required because this code is for
information only.
Explanation: A request to allocate
dynamically the VVDS has failed. SFI
contains the dynamic allocation error
reason code returned in the SVC 99
request block, or text stating why the
allocation routine failed.
Programmer Response: Determine why
the dynamic allocation reason code was
returned.
Explanation: A VSAM OPEN request to
open the VVDS failed. SFI contains
xxrrrrrr, where rrrrrr=register 15 from
the OPEN and xx is ACBERFLG.
the OPEN reason code was returned.
368
Reason
Code
100
Description
Explanation: A F1 DSCB with a
SYS1.VVDS.Vxxxxxx was found and it is
not a VSAM data set. A VVDS cannot be
created or opened for this volume.
Reason
Code
2
Programmer Response: Determine the

source of the non-VSAM data set and
have it renamed or removed.
RETURN CODE 52
Explanation: An OBTAIN error occurred while
attempting to access a DSCB in the VTOC.
Reason
Code
x
4
Description
Explanation: The reason codes are
either the OBTAIN return code, the
DADSM diagnostic code, or the CVAF
CVSTAT code associated with the error.
Programmer Response: See OS/390
DFSMSdfp Diagnosis Reference for an
explanation of the completion codes.
RETURN CODE 54
Explanation: Incorrect use of JOBCAT or STEPCAT.
Reason
Code
2
Description
Explanation: A JOBCAT or STEPCAT
was found in a step that referenced an
SMS data set.
Explanation: An attempt to define an
SMS data set with JOBCAT or
STEPCAT failed.
14
RETURN CODE 56
Explanation: A security verification failed.
16
28
Description
Explanation: The system attempted to
verify alter authority to the master
catalog (update authority for an ALTER
NEWNAME), but the the user did not
have the required authority.
Programmer Response: Ensure the
user has the proper authority to the
master catalog. For some types of
requests, only the proper data set
authority is required, and the master
catalog is only checked if they do not
have necessary data set authority.
Granting the authority to the data set
may eliminate this error.
Explanation: A non-system caller has
specified request special authority level
checking in the catalog parameter list.
IBM Support Center if the user written
programs are not calling catalog
management.
Explanation: The user did not have the
required access authority to the specified
entry.
user has the proper RACF authorization
for the function being requested.
Explanation: The return code from the
RACHECK REQUEST=AUTH was other
than 0, 4, or 8.
reason for the unexpected RACF return
code.
Explanation: An implicit alter of a GDG
was denied because the user did not
have the the proper authority to the
GDG base and the catalog.
user has the proper authority for the
GDG base.
authorized for the requested SMS
Management Class, SMS Storage Class,
or both.
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
Code
30
32
Description
Explanation: The caller was not
authorized to the catalog when defining
an SMS data set into the master catalog.
Explanation: The return code from the
RACHECK REQUEST=AUTH was other
than 0, 4, or 8 when attempting to verify
access to a facility class.
Reason
Code
4

reason for the unexpected RACF return
code.
occurred.
34
6
IBM Support Center.
authorized. When no profile exists for
functions that require RACF
authorization, the caller must be at least
APF authorized.
Explanation: RACF options do not
permit use or cataloging of uncataloged
non-SMS managed data sets.
Explanation: Caller is not authorized to
use the specified volume.
36
40
42
Programmer Response: Acquire

authority to the specified volume and
resubmit the job.
Explanation: Caller is not authorized to
update catalog for DEFINE ATL request
44
RETURN CODE 60
Explanation: Incorrect entry type for requested action.
Reason
Code
2
Description
Explanation: Probable system error. An
incorrect entry type for an extract
operation was detected.
the name of the entry specified in the
command is correct. Ensure that the
catalog entry is still valid, by performing
a LISTCAT run. If the reason code
indicates a system error, list the catalog
using the PRINT command with the
DUMP option. Contact the IBM Support
Center. Otherwise, correct the error. Run
the job again.
370
10
Description
(cluster or non-VSAM) was detected.
the job again.
Explanation: An incorrect cluster entry
for ALTER of data set attributes was
detected.
the job again.
Explanation: An incorrect cluster or
index entry for ALTER of buffer size was
detected.
the job again.
(CLUSTER) to ALTER the FREESPACE
or WRITECHECK parameters was
detected.
the job again.
Reason
Code
12
14
14
20
Description
(CLUSTER) to ALTER volumes was
detected.
the job again.
Explanation: Probable system error. An
incorrect catalog parameter list was
supplied in an attempt to add a volume.
the job again.
Explanation: A specific volume serial
has been specified in an ALTER
ADDVOLUMES or ALTER
REMOVEVOLUMES for an
SMS-managed data set.
Reason
Code
22
26
28

volume serial(s) to a nonspecific value
(*).
Explanation: The upgrade set
association in the base cluster data
record does not point to an upgrade set
record.
the job again.
30
Description
Explanation: The data association in the
cluster record does not point to a data
record.
the job again.
Explanation: ALTER of
EXCEPTIONEXIT was specified, but the
entry is not a data or index component.
the job again.
Explanation: ALTER of average
RECORDSIZE was specified, but the
entry is not a data or index component.
the job again.
Explanation: ALTER of expiration date
was specified but the entry is not a
cluster, alternate index, or path.
the job again.
371
Reason
Code
32
34
36
Description
Explanation: ALTER of last back-up
date was specified, but the component is
not a cluster, non VSAM, or GDS.
Explanation: ALTER of last back-up
date was specified, but the data set is
non-SMS managed and does not have a
last back-up date.
Explanation: An alias entry may only be
defined for non-VSAM or user catalog
entries.
Reason
Code
44
46
38
40
42

an incorrect DEFINE operation.
Explanation: A LOCATE or ALTER was
specified for a GDG base, and entry is
not a GDG.
Programmer Response: GDGs must
have qualified names. Ensure that all
levels of qualification are specified for
GDG. Submit the job again.
Explanation: An input base record to
catalog upgrade management is not an
alternate index, cluster or data type
entry.
48

DUMP 11 option. Contact the IBM
Support Center. Otherwise, correct the
error. Run the job again.
Explanation: An input base record to
catalog reusable processing is not a
data type entry.
52

DUMP 11 option. Contact the IBM
error. Run the job again.
372
50
54
Description
was encountered in a DELETE
operation, other than the expected alias
entry.
the proper entry name was specified and
that the catalog reflects the expected
structure. It may be necessary to rebuild
the catalog.
was encountered in a DELETE
operation, other than the expected VVR
type.
the proper entry name was specified.
Explanation: An entry type other than
the expected NVR type was encountered
in a DELETE operation.
Explanation: An incorrect entry type,
other than the expected BCS type, was
encountered in a delete operation.
the correct entry type was specified.
Explanation: ALTER of SMS constructs
was specified, but the component is not
a cluster, non-VSAM, or GDS.
Explanation: Define an Extended
Format UCAT is not allowed.
Programmer Response: Define the
UCAT as a non-Extended Format data
set.
56
Explanation: ALTER of FILEID or
CCSID is not allowed with other DFM
attributes.
Programmer Response: Ensure that no
other DFM attributes are being altered in
the same request. Run the job again.
58
Explanation: ALTER of CCSID is not
allowed for non-SMS managed data set,
or the data component of a catalog.
the entry being altered is an SMS
managed VSAM or non-VSAM data set.
Correct the error. Run the job again.
Reason
Code
60
Description
Reason
Code
74
Explanation: ALTER of DFM/NFSS

LAST SIZE CHANGE field is not
allowed for non-SMS managed data set.
Explanation: ALTER of FILEDATA is not


62
Explanation: An attempt has been
made to alter DFM attributes for a
non-SMS managed data set.
76
MODIFIED TIME field is not allowed for


64
ACCESS AUTH field is not allowed for
78
ATTR CHNG TIME field is not allowed
for non-SMS managed data set.


66
ACCESS TIME field is not allowed for
80
BINARY FILE SIZE field is not allowed


70
USERID field is not allowed for
Description
82
LOGICAL RECORD COUNT field is not


84
72
GROUPID field is not allowed for

CHARS NO PADDING field is not
allowed for non=SMS managed data set.


373
Reason
Code
86
Description
Reason
Code
96
Description
Explanation: ALTER of the RLS
recovery timestamp (GMT) is not
allowed for a data set that is not capable
of being used by RLS. Data sets that are
Linear, non-SMS managed, keyrange or
temporary are not eligible for RLS
access.

TEXT TIMESTAMP field is not allowed

the entry being altered is eligible for RLS
processing. Correct the error. Run the
job again.
88
ATTRIBUTE EXTENSION FLAGS is not
98
Explanation: ALTER of the RLS flags is

not allowed for a data set that is not
capable of being used by RLS. Data
sets that are Linear, non-SMS managed,
are keyrange or temporary are not
eligible for RLS access.

90
EXTENDSION AREA field is not allowed

job again.
100
Explanation: ALTER of the BWO flag is
not allowed for non-SMS managed data
set or a linear data set.
92
Explanation: ALTER of the RLS SMS
flag is not allowed for a data set that is
not capable of being used by RLS. Data
sets that are Linear, non-SMS managed,
keyrange or temporary are not eligible
for RLS access.
job again.

managed VSAM data set that is not
LINEAR. Correct the error. Run the job
again.
102
Explanation: ALTER of ACCOUNT
INFORMATION is specified but the entry
type is not Data, NonVSAM, or GDS.
94
Explanation: ALTER of the RLS
recovery timestamp (local) is not allowed
for a data set that is not capable of
being used by RLS. Data sets that are
Linear, non-SMS managed, keyrange or
access.
job again.
374
104

catalog is still valid by performing a
LISTCAT run. If the reason code
DUMP11 option. Contact the IBM
error and run the job again.
Explanation: Invalid entry type for alter
of extended addressability data set.
Reason
Code
106
108
110
112
Description
Explanation: ALTER of the
LOGSTREAMID parameter is not
allowed for a data set that is not capable
of being used by RLS. Data sets that are
Linear, non-SMS managed, are
keyrange or temporary are not eligible
for RLS access.
job again.
Explanation: ALTER of the LOG
parameter is not allowed for a data set
that is not capable of being used by
RLS. Data sets that are Linear, non-SMS
managed, are keyrange or temporary
are not eligible for RLS access.
job again.
Explanation: ALTER of the FRLOG
parameter is not allowed for a data set
that is not capable of being used by
RLS. Data sets that are Linear, non-SMS
managed, are keyrange or temporary
are not eligible for RLS access.
job again.
Explanation: An IDCAMS SHCDS
command with either the CFRESET or
CFRESETDS keywords was issued
against a data set not capable of being
used by RLS. Data sets that are Linear,
non-SMS managed, are keyrange or
access.
job again.
Reason
Code
x
Description
Explanation: An attempt to extend a
striped data set to a new volume
encountered an internal logic error when
locating the volume information in the
catalog to be updated.
IBM Support Center.
RETURN CODE 64
Explanation: The associated entry does not exist. This
condition indicates that a system error has occurred
such that the catalog cannot find either a data or an
index entry which is associated with a cluster or
alternate index entry.
Reason
Code
x
Description
Explanation:An internal logic error has
occurred.
IBM Support Center.
Explanation: The association of a
truename record in an ICF catalog is
incorrect.
Programmer Response: Use access
method services to define the associated
base of the truename record.
RETURN CODE 66
Explanation: Bad DADSM parameter list.
Reason
Code
x
Description
Explanation: The reason code listed is
the return code from the DADSM
function, which may have been a
RENAME or a SCRATCH request.
RETURN CODE 68
RETURN CODE 62
Explanation: An error was encountered while initializing
the extension of a data set.
Explanation: No space is available on the user volume.

Only the primary volume will be used for ICF catalogs.
375
Reason
Code
x
20,22,24
Description
Explanation: The return DADSM
Historic Return Code was other than 0,
4, 8, or 12. The reason code shown is
the DADSM return code. See OS/390
DFSMSdfp Diagnosis Reference for an
explanation of the DADSM return and
diagnostic codes.
Programmer Response: The return
code is returned by DADSM.
Explanation: An attempt to allocate an
SMS-managed data set using the Best
Fit interface was able to allocate space
on all supplied volumes, but the amount
of space allocated was not the total
amount required.
Programmer Response: The storage
group did not contain sufficient space to
allocate the data set.
RETURN CODE 70
Reason
Code
8

volume and the volume information (time
stamps) contained in the catalog are at
the same level. If the problem is due to
insufficient virtual storage, specify a
larger region parameter. Run the job
again.
RETURN CODE 74
Explanation: Cell not found.
Reason
Code
0
Explanation: Component not found.
Reason
Code
0
Description
occurred procesing a GDS record.
IBM Support Center.
RETURN CODE 72
Explanation: The user volume is not mounted. The
reason codes are from VSAM open/close/end-ofvolume, volume mount and verify routine IDA0192V.
Reason
Code
4
Description
Explanation: Unable to mount user
volumes.
proper volumes are implicitly or explicitly
allocated by the JCL.
376
Description
attempting to mount the user volume.
Examples of possible errors include
insufficient virtual storage for workareas
or a time-stamp mismatch problem.
Description
Explanation: The volume cell for a base
clusters data or index component was
not found. A DEFINE alternate index
command was being processed.
Programmer Response: Run access
method services DIAGNOSE command
for additional information. The base
cluster may have to be deleted with the
NOSCRATCH option and redefined with
the RECATALOG option.
Explanation: The relate cell was not
found in the base cluster sphere record
while a moved subrecord update was in
progress.
against the catalog and then determine
the action to be taken. Delete with the
NOSCRATCH parameter. Define with the
RECATALOG parameter.
Explanation: An association cell was
not found for a path or alias record while
a subrecord move update was in
progress.
the action to be taken. Delete with the
NOSCRATCH parameter. Define with the
Reason
Code
10
12
Description
Explanation: The SMS cell was not
found in the VVDS entry for a data set,
even though the data set is
SMS-managed.
the action to be taken. The data set may
need to be copied to a new SMS data
set and the failing data set deleted.
Explanation: The SMS cell was not
found in the BCS entry for a data set,
even though the data set is
SMS-managed.
Reason
Code
2

the action to be taken. The catalog may
be repaired by doing a DELETE
NOSCRATCH, followed by DEFINE
RECATALOG.
Explanation: No unit available for mounting or volume

not mounted.
Description
Explanation: Access method services
ALTER name change of a unique object
was specified, but no volumes containing
any part of the data set were mounted.
JCL statements cause the proper
volumes and units to be allocated. Also,
ensure that all ddnames specified match
the access method services dname
parameter when specified. Determine a
minimum unit count and have sufficient
units available for job processing.
Ensure that volumes are allocatable by
the use of dynamic allocation.

Explanation: A scan of the task I/O
table (TIOT) failed to find a needed JCL
dd statement.
you have all needed JCL DD statements
and that all JCL statements cause the
proper volumes and units to be
allocated. Also, ensure that all ddnames
specified match the access method
services dname parameter when
specified. Determine a minimum unit
count and have sufficient units available
for job processing. Ensure that volumes
are allocatable by the use of dynamic
allocation.
RETURN CODE 76
Reason
Code
0
Description
Explanation: The volume was not
mounted when expected.
10
For a non-VSAM data set, ensure the

number of volumes on the DD statement
match the number of volumes where the
data set resides.
table (TIOT) failed to find the user
specified JCL ddname statement.
377
Reason
Code
12
Description
table (TIOT) failed to find the user
specified JCL ddname statement.
Reason
Code
2
RETURN CODE 78
Explanation: Subrecord move error.
Reason
Code
x
Description
Explanation: An internal logic error
occurred while processing a subrecord.
IBM Support Center.
RETURN CODE 80
Explanation: Incorrect related object. The object
specified in the RELATE parameter of a DEFINE
command does not exist, or is improper for the type of
object being defined.
Reason
Code
x
Description
occurred.
IBM Support Center.
Explanation: The related object is
reusable.
DEFINE command so that the entry
named in the RELATE parameter is
proper for the type of object being
defined.
378
10
12
Description
Explanation: The related object is a
relative-record data set or a linear data
set.
defined.
Explanation: The related object does
not exist.
defined.
Explanation: An alternate index or path
is not allowed to be built over a catalog.
defined.
Explanation: The names of an alternate
index or path and a related object are
identical.
defined.
Explanation: There is no pointer to a
related object of an alternate index or
path.
defined.
Explanation: An alternate index is not to
be built over a base cluster, or the
related path object is not a cluster or an
alternate index.
defined.
Reason
Code
14
16
Description
Explanation: A DEFINE PATH command
specified a PATHENTRY name of a
PAGESPACE object.
Reason
Code
0

path entry name. Run the DEFINE PATH
command again.
Explanation: A DEFINE PATH command
has specified a PATHENTRY name for a
VVDS.
2
20
28
30
40

path entry name. Run the DEFINE PATH
command again.
Explanation: The related object for a
DEFINE ALTERNATEINDEX is a VVDS.
related name. Run the DEFINE AIX
command again.
Explanation: The related name
specified for a DEFINE ALIAS command
is for a record type other than
NONVSAM or USERCATALOG.

the related name is correct and that a
DEFINE ALIAS command is desired. If
the above is true refer to access method
services DIAGNOSE command to obtain
additional information.
Explanation: The version number of the
related generation data set name does
not match the version number in the
base GDG. The DEFINE ALIAS will fail.
version number in the GnnnnVnn part of
the generation data set name. Run the
DEFINE ALIAS command again.
Explanation: The related object is a
variable relative-record data set.
RETURN CODE 84
Description
Explanation: An unexpired purge date
exists. An attempt to delete an entry
failed because its expiration date has not
been reached, and the DELETE
command did not specify the PURGE
option.
PURGE option if desired. Run the
DELETE command again.
Explanation: There are conflicting date
formats. An attempt to retrieve a date in
the new format (YYYYDDD) failed
because the request used the old format
(YYDD) by passing the old format field
dictionary name DSETEXDT or
DSETCRDT. The date cannot be passed
correctly in the old format.
Programmer Response: Submit the job
again using the new format field
dictionary name DSCRDT2 (creation
date) or DSEXDT2 (expiration date).
Explanation: An unexpired new format
purge date exists. An attempt to delete
an entry failed because its expiration
date has not been reached, and the
DELETE command did not specify the
PURGE option. This expiration date is
stored in the new format (YYYYDDD)
and it is beyond the year 1999.
PURGE option if desired. Run the
DELETE command again.
RETURN CODE 86
Explanation: Recatalog error.
Reason
Code
0
Explanation: Date error.
Description
Explanation: No related PATHENTRY
name was found on the path catalog
record.
the PATHENTRY name is correct. If it is,
refer to access method services,
DIAGNOSE command, to obtain
additional information.
occurred.
IBM Support Center.
379
Reason
Code
4
Description
Explanation: Something other than a
CLUSTER or alternate index type object
specified the RECATALOG parameter.
Reason
Code
10
Programmer Response: You can only

recatalog pagespace, swapspace, or
SYS1 data sets to a different catalog
than the one specified in the VVR. If the
data set you are recataloging is one of
those types, or if you are getting this
error in response to a REPRO
MERGECAT command, contact the IBM
support center.

the object being recataloged is a cluster
or alternate index.
Explanation: Either the primary VSAM
volume record (VVR) points to another
catalog, or the primary VVR or
non-VSAM volume record (NVR) for the
object being recataloged was not found
on the first volume serial number
specified. The primary VVR or NVR
contains the data set information needed
to recatalog the object.
Possible causes of this error are:
v No VVR exists.
12
v A VVR exists, but it points to another

catalog.
v Parameters were not specified as they
were when the cluster was originally
defined. The parameters are NAME,
INDEXED, LINEAR, NONINDEXED,
NUMBERED, and VOLUMES.
14
Programmer Response:
16
If no VVR exists, then re-issue the

DEFINE command, without the
RECATALOG parameter, for the ICF
catalog.
18
20
If the VVR exists but points to a different

catalog, specify the correct catalog and
re-issue the DEFINE command with the
If the original values for parameters

NAME, INDEXED, LINEAR,
NONINDEXED, NUMBERED, and
VOLUMES were not specified, specify
the original values and re-issue the
DEFINE command with the
Explanation: The RECATALOG
parameter is incorrect on the DEFINE
command for an ICF catalog.
22
380
Description
Explanation: The catalog associated
with this data set does not match the
catalog name found in the VVR.
If your data sets is not one of those

types, print the VVR to determine which
catalog the data set should be
associated with.
Explanation: The VVR for the data set
being recataloged indicated it was for a
LINEAR data set, but the DEFINE
RECATALOG command did not specify
the LINEAR keyword.
Explanation: The DEFINE RECATALOG
command specified the LINEAR
keyword, but the VVR for the data set
did not indicate it was a LINEAR data
set.
Explanation: NVR for the object being
recataloged was not found on the
volume serial numbers specified.
Explanation: Something other than the
expected NVR was retrieved.
Explanation: A DEFINE NONVSAM
RECATALOG request was issued on a
volume that does not have the UCBSMS
indicator on.
Programmer Response: This could
result from an IDCAMS DEFINE
NONVSAM RECATALOG request or an
IDCAMS REPRO request that would
cause the DEFINE RECATALOG to be
issued. A DEFINE NONVSAM
RECATALOG request is valid only for
SMS NONVSAM data sets. Therefore,
the volume specified must have the
UCBSMS indicator set to on. Check to
see if the volume was removed from the
active configuration or if the volume was
set to non-SMS status. Correct the error
and run the job again.
Explanation: The VVR/NVR catalog
name does not match the name of the
catalog currently oriented to.
RETURN CODE 90
Explanation: Delete error.
Reason
Code
2
10
12
14
16
Description
delete the Master Catalog.
the correct catalog is specified. If so, run
the job again with a different master
catalog.
determine if the catalog is empty.
Programmer Response: Specify
FORCE, RECOVERY, or run DIAGNOSE
and recommended action.
Explanation: An incorrect DELETE
TRUENAME request was specified. The
associated base object exists.
Programmer Response: User error.
Explanation: A pagespace record was
damaged. It could not be determined if
pagespace was active.
Programmer Response: Run
DIAGNOSE and take the recommended
action.
Explanation: The generation data set
was not found in the GDG.
Programmer Response: Run LISTCAT
to determine the generation data sets in
the GDG. Run the delete job again with
the correct generation/version number.
Explanation: A required FILE parameter
was not specified on the DELETE VVR
command.
Programmer Response: Specify FILE
parameter. Run the job again.
Explanation: No DD was found to
match the supplied DD name on the
DELETE VVR request.
Programmer Response: Check FILE
parameter. Run the job again with the
correct DD name.
Explanation: DELETE VVR request for
a VVR with an associated catalog.
Reason
Code
18
20
22
24
26
30
32
34
Description
Explanation: The usercatalog parameter
is missing.
Programmer Response: Specify the file
Explanation: DELETE NVR request for
a NVR with an associated catalog.
Programmer Response: This is
probably a user error.
Explanation: No DD was found to
match the DD name on the DELETE
NVR request.
Respecify the DDname in the FILE
Explanation: The request is to delete an
SMS data set only, but the data set is
non-SMS managed.
Explanation: A required FILE parameter
was not specified on the DELETE NVR
command.
Explanation: DELETE VVR resulted in
an attempt to delete a DSCB that has an
associated VVR with a catalog name
other than the one specified. Nothing
was deleted.
Explanation: For DELETE VVR/NVR,
the VVR/NVR was not found, but a
DSCB was found. The DSCB was
deleted.
Programmer Response: This is an
informational message. No action is
required.
an attempt to delete a non-VSAM DSCB.
Nothing was deleted.
DELETE VVR cannot be used to delete
non-VSAM data sets.
381
Reason
Code
36
38
40
42
44
46
48
50
Description
an attempt to delete a DSCB whose
name resolves to an associated
keyrange VVR. Nothing was deleted.
Use DELETE CLUSTER.
Explanation: For DELETE VVR, both
the VVR and DSCB were not found.
Nothing was deleted.
Programmer Response: Informational
message. Neither the VVR nor the
DSCB were found. The object name may
be misspelled. If so, run the job again
with the correct object name specified.
Explanation: For DELETE VVR, the
DSCB was not found.
Programmer Response: Informational
message. The VVR was found, but the
associated DSCB was not found. The
VVR is deleted.
Explanation: An NVR was retrieved
during a DELETE VVR request.
Specify DELETE NVR and run the job
again.
Explanation: A VVR was retrieved
during a DELETE NVR request.
Specify DELETE VVR and run the job
again.
Explanation: DELETE VVR failed to
specify the system master catalog name
in the catalog parameter.
Rerun the failing DELETE VVR job
specifying the system master catalog
name in the catalog parameter.
Explanation: DELETE CLUSTER failed
because the data set is using RLS
resources.
Programmer Response: This data set
must be deleted on a DFSMS/MVS 1.3
or higher system to ensure the RLS
resources are freed.
Explanation: DELETE failed because
SMSVSAM Server was not available.
Programmer Response: Retry the
operation when the SMSVSAM Server is
available.
382
Reason
Code
52
Description
Explanation: The SMSVSAM Server
encountered an internal error performing
the delete operation. Diagnostic data will
be written to Logrec, and a system dump
may have been taken.
Programmer Response: Refer the
problem to IBM programming support
center.
RETURN CODE 94
Explanation: A DADSM OBTAIN request failed during a
catalog delete request.
Reason
Code
4
12
Description
Explanation: The correct volume was
not mounted for OBTAIN.
Programmer Response: Check the JCL
and file parameters, and ensure that the
required volume is mounted.
Explanation: OBTAIN did not find
requested format-1 DSCB on specified
volume.
the correct volume is mounted.
Explanation: OBTAIN encountered an
I/O error in the volumes VTOC.
Programmer Response: Check for a
possible hardware error.
Explanation: The reason code is the
OBTAIN return code.
meaning of the obtain return code.
RETURN CODE 96
Explanation: An error occurred in specifying key length,
key position, or record size for an alternate index or
spanned cluster.
Reason
Code
0
Description
Explanation: The key specified for
spanned record exceeds the control
interval size.

erroneous parameter (KEYS or
RECORDSIZE). Run the job again.
Explanation: The alternate index key
position plus the key length for the base
cluster is larger than the control interval
size minus 10 for spanned records.
Explanation: The alternate index key
position plus the key length for the base
cluster is larger than the record size.
RETURN CODE 98
Explanation: An unusual condition occurred during an
ALTER name of a unique or non-VSAM data set.
RETURN CODE 108

Explanation: An incorrect field name was found in the
field parameter list (CTGFL). The field name passed by
AMS does not exist in the catalog management
dictionary.
Reason
Code
0
RETURN CODE 102
Description
Programmer Response: The message
indicates that the callers AMS release
level or maintenance level is different
from the CATALOG level that is being
called. Ensure that IDCAMS and
CATALOG are at the same level.
RETURN CODE 110

Explanation: Unable to modify or delete RACF profile.
Reason
Code
4
Description
same as returned by the DADSM
RENAME function in the status byte of
the RENAME volume list.
meaning of the RENAME return code, as
documented in the Status Codes from
RENAME section in OS/390 DFSMSdfp
Diagnosis Reference. Correct the error.
Run the job again.
Description
DADSM SCRATCH function status code.
meaning of the SCRATCH status code.
See OS/390 DFSMSdfp Diagnosis
Reference for these status codes and
take the appropriate corrective action
before rerunning the job that failed.

Explanation: The maximum logical
record size for spanned records exceeds
the control area size.

Reason
Code
x
Reason
Code
x
Description
Explanation: The data set to which an
ALTER RENAME command is directed is
RACF indicated. However, there is no
RACF profile.
Programmer Response: Make the data
set RACF-protected or remove the
RACF indicator.
Explanation: An ALTER RENAME
command has been issued for a
RACF-protected data set. This failed
because as a result of the new name,
the data set cannot be defined to the
security subsystem.
Programmer Response: Use a new
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
4
Description
occurred.
Reason
Code
0
Programmer Response: Probable

system error. Contact the IBM Support
Center. However, if a user program is
interfacing directly with catalog
management, the FPL contains improper
data.
RETURN CODE 114

Explanation: A duplicate RACF profile exists.
12
Reason
Code
0
Description
Explanation: As a result of an IMPORT
or DEFINE command, VSAM has
attempted to establish a RACF profile for
a cluster/alternate index, data, or index
object. This failed because a profile with
the same name already exists.
Description
Explanation: As the result of a DEFINE,
IMPORT, or IMPORTRA command,
VSAM attempted to define a RACF
profile for the object. The profile could
not be established because the user
does not have sufficient authority for the
specified data set characteristics.
installation security subsystem guidelines
for defining a data set in the security
subsystem. Modify the data set
characteristics accordingly.
Explanation: As a result of a DEFINE,
IMPORT or IMPORTRA command,
VSAM attempted to define a RACF
profile for the object. RACF was
incapable of building the profile.
Programmer Response: RACF was
inactive and could not process the profile
build request. To activate RACF, contact
the system security administrator.
Programmer Response: Either:

v Enter an IMPORT or DEFINE
command for the data set with a
different cluster/alternate index, data,
or index name
v Have the owner of the profile with the
name you wish to use delete that
profile and associated data, if any.
RETURN CODE 120

Explanation: Attempt to modify the non-existent or
system field. This is a system error.
Reason
Code
0
RETURN CODE 116

2
Explanation: A catalog record has been damaged, or
contains inconsistent data.
Reason
Code
24
Description
Explanation: An incorrect association
was returned during upgrade retrieval.
Programmer Response: An IDCAMS
DIAGNOSE should be run against the
catalog and any errors identified
corrected.
384
RETURN
CODE 124
Explanation:
Incorrect
control
interval
number.
Description
IBM Support Center.
Explanation: The storage management
subsystem field in the BCS is
inconsistent with that field in the VVDS
entries.
Reason
Code
2
34
36
Description
Explanation: An incorrect relative block
address (RBA) return code was returned
from VSAM record management.
Programmer Response: This is a
system error indicating that the catalog
may need to be restored. Use of the
access method services list catalog
(LISTCAT) or DIAGNOSE commands
may help identify the incorrect entry. It
may be necessary to contact the IBM
Support Center.
Explanation: DASDCALC returns either
an incorrect physical block size or an
incorrect index into the physical block
size table.
Programmer Response: The possible
cause of this error is a CI size that is not
compatible with the physical device.
Correct the CI size and rerun the job.
Explanation: VSAM record
management has returned an invalid CI
error on an access to a catalog record.
This error generally occurs because an
invalid CIDF or RDF is detected within a
catalog CI. One possible cause is
damage as a result of a hardware
failure. An IEC331I message will be
issued and the SFI information will
contain additional information about the
VSAM error.
Programmer Response: For the ACS reason code

referenced in the appropriate SMS SUB-System
Message Manual. Refer to the Storage Management
Subsystem Reason Codes, Sub-Sections Subsystem
Interface Reason Codes and ACS Service Reason
Codes in the OS/390 DFSMSdfp Diagnosis Reference
for a complete description of the reason codes.
RETURN CODE 128
Explanation: A user-provided storage is outside the
user region. Probable system error.
Reason
Code
0
Description
Explanation: An integrity check of the
user catalog parameter list (CPL), the
FPL, or the FVT, failed.
IBM Support Center unless a
user-written program is interfacing
directly with catalog management.
Explanation: A storage validity check
failed on a user FPL or on the user work
area referenced from the CPL.
Explanation: A CPL field that references
the work area is zero.
Programmer Response: Run an access

method services DIAGNOSE command,
and EXAMINE DATATEST against the
catalog. The catalog may need to be
recovered.
RETURN CODE 130

RETURN CODE 126
Explanation: Alter new name of a GDS, non-VSAM or
cluster failed because an ACS service returns a
non-zero return code.
Reason
Code
ACS reason
code =
catalog
reason code
+ 1000
Description
Explanation: Catalog management can
only support ACS services reason codes
from 1000 to 1255. The ACS services
return and reason codes are
documented in the OS/390 DFSMSdfp
Diagnosis Reference.
Explanation: An ALTER RENAME recatalog error.
Reason
Code
4
Description
Explanation: Only the old name catalog
entry remains to be deleted, but the
VTOC still has the DSCB with the old
name.
Explanation: Only the old name catalog
entry remains to be deleted, but the
VVDS still has the NVR with the old
name.
Explanation: The DSCB has been
renamed, but no DSCB with either the
old name or the new name can be
found.
385
Reason
Code
10
12
14
16
Description
Explanation: The data set DSCB cannot
be located.
Explanation: The NVR has been
renamed, but the NVR with the new
name cannot be located.
Explanation: There should be an NVR
with the old name, but that NVR cannot
be located.
Explanation: The DSCB has been
renamed without error, but the NVR
cannot be renamed because there is
already an NVR with that name.
Reason
Code
124
126
128
130
RETURN CODE 132

Explanation: Incorrect pointer value in argument list.
Probable system error.
132
Reason
Code
x
134
0
20
48
122
386
Description
Explanation: An expected field value
was not supplied or an internal logic
error occurred. This is probably a logic
error in the caller of catalog
management.
Programmer Responsse: Contact the
IBM Support Center.
Explanation: Expected component not
found.
Explanation: There is no pointer to the
catalog work area in the catalog
parameter list, and the DEFINE function
is unable to return the names generated
for a component.
Explanation: The AMDSB information
has not been found in the VVR, or
VSAM CLOSE passed invalid AMDSB
data to update the VVR. In the latter
case, message IEC251I will be issued.
not found.
damaged catalog record. Contact the
IBM Support center if message IEC251I
was issued.
Explanation: Define master catalog or
user catalog with extended format
information or attributes extension
information is not valid.
Description
Explanation: Backout while open
specificaion not valid for non-VSAM data
set.
Explanation: Backout while open
specification not valid for ALTER of
non-SMS data set.
occurred.
IBM Support Center.
occurred.
IBM Support Center.
Explanation: Record Level Sharing
attributes not valid for non-VSAM data
set.
Explanation: Record Level Sharing
attributes not valid for non-SMS data set.
RETURN CODE 136

Explanation: Required parameters not supplied.
Probable system error.
Reason
Code
x
22
32
34
Description
occurred.
Programmer Responsse: Contact the
IBM Support Center.
Explanation: A unique data set needs a
DD statement for a rename, or the DD
statement is missing.
dname job control statement.
Explanation: An alias name was not
provided on a DEFINE command.
DEFINE command. Run the job again.
Explanation: GDG limit or attribute data
were not provided on a DEFINE
command.
DEFINE command. Run the job again.
Reason
Code
40
42
46
Description
Explanation: A required DD statement is
missing for a mountable unit. The
system is unable to mount the volume
required for DELETE NONVSAM
SCRATCH processing.
Programmer Response: Use file
parameter on DELETE and allocate a
mountable unit to the job through a DD
statement. Specify DEFER mount.
Explanation: An error occurred from
IDA0192V while attempting to mount a
volume required for DELETE NONVSAM
SCRATCH processing.
the mountable unit was allocated for
DELETE processing.
Explanation: No storage class
information was passed for an SMS
managed data set.
Reason
Code
4
RETURN CODE 138

Explanation: DADSM RENAME error.
Reason
Code
x
10
Description
Explanation: Volume status code from
DADSM.
RETURN CODE 140
20
Explanation: Inconsistent or conflicting arguments were

provided.
Reason
Code
2
Description
Explanation: The index component was
found for relative record data set or
entry-sequenced data set. This is a
system error.
Programmer Response: If the reason
code indicates a system error, contact
the IBM Support Center. Otherwise,
follow the programmer response
indicated by the reason code.
28
30
Description
Explanation: The key range is incorrect
for catalog define, or the key ranges are
not specified in ascending sequence in
the DEFINE of a VSAM key sequenced
data set.
DEFINE command.
Explanation: Key ranges were found on
both data and cluster catalog FVT. This
is a system error.
Explanation: The work area is too
small. This is a system error.
Explanation: Space parameters were
found on both cluster and data catalog
FVT. This is a system error.
Explanation: The key lengths for data
and index are not equal. This is a
system error.
Explanation: There are an unequal
number of volume serial numbers and
file sequence numbers in list entries.
input. Run the job again.
Explanation: More device type entries
exist than volume serial numbers.
387
Reason
Code
34
44
Description
Explanation: An incorrect space request
type on DEFINE was detected. This is a
system error.
Explanation: A relative-record data set
has a maximum record length that is not
equal to the average record length.
Reason
Code
74
78
80
60
62
64
66
72

Explanation: The logical record size for
an ICF catalog has been exceeded. The
DEFINE ALIAS has caused the updated
catalog record to exceed the catalogs
logical record size.
catalog record size to increase the
logical record size to a value up to the
32,400 byte maximum. Run the DEFINE
of the alias again.
Explanation: The maximum average
logical record size is less than 4086
bytes for an ICF catalog define.
maximum average logical record size.
Run the DEFINE command again.
Explanation: An incorrect group code
for field management was detected.
Programmer Response: This is a
system programming error.
Explanation: The component key length
exceeds the limit.
388

INDEX option. Run the define operation
again.
Explanation: The request to field
management was not valid.
CPL for calling field management.
Explanation: The size of the generation
data set subrecord exceeds the
maximum spanned record size of the
ICF catalog.
Programmer Response:
Do one of the following:
v Reduce the size of the generation
data set by removing unused volume
serial numbers.
82
84
90

damaged catalog record.
Explanation: Duplicate volumes exist in
the volume list of a non-keyrange data
set.
Programmer Response: For a DEFINE,
remove the duplicate volume from the
volume list and rerun the DEFINE. For
an ALTER ADDVOLUMES, a volume
being added might already exist as a
primary or candidate volume for the data
set; therefore, remove the volume from
the ADDVOLUMES list and rerun the
ALTER.
Description
Explanation: The define of a VVDS had
the INDEX option specified. A VVDS is
an entry sequenced data set.
92
94
v Define a new ICF catalog with a

larger maximum spanned record size.
The default is 32,400 bytes.
Explanation: Key ranges are not
allowed on a DEFINE of an ICF catalog.
KEYRANGES parameter. Run the
Explanation: The REUSE parameter
was specified with UNIQUE or KEY
ranges.
Programmer Response: Remove one
of the conflicting parameters. Run the
Explanation: More than one volume
serial number is specified for the
DEFINE request of a non-VSAM data
set, and one of the volume serial
numbers is ******.
Programmer Response: If the indirect
volser feature (a non-VSAM data set
defined with a volser of ******) is wanted,
remove the other volsers from the
DEFINE request.
Explanation: A format 2 work area is
incorrect for this catalog request.
again with a format 1 work area.
Explanation: DEFINE NONVSAM no
BCS for a non-SMS managed data set
cannot be requested.
Reason
Code
96
98
100
102
104
106
110
112
116
120
122
124
Description
Explanation: DEFINE NONVSAM no
NVR for a non-SMS managed data set
cannot be requested.
Explanation: The new record length will
exceed the maximum VVR or NVR size.
Explanation: The number of volumes
passed exceeds the number of UCB
addresses.
Explanation: The Volser in the UCB
does not match the volser in the volume
list.
Explanation: An incorrect number of
device types were passed for the ALTER
non-specific volume request.
Explanation: An incorrect number of
volumes were passed for the ALTER
non-specific volume request.
Explanation: A 31-bit overflow occurred
while calculating the required space
allocation with the values specified in the
RECORDS parameter.
Programmer Response: Define the
data set with a smaller space allocation
request.
Explanation: An incorrect high-allocated
RBA was found during a define of a data
component. The high-allocated RBA was
less than the high-used RBA.
Programmer Response: Reduce the
amount of space specified for the data
component of the cluster. Enter the
Explanation: A request was made to
compress a data set that is not an
Extended Format data set.
RETURN CODE 142

Explanation:DADSM OBTAIN error.
Reason
Code
x
RETURN CODE 144

Explanation: An incorrect entry name format or the
name has an initial character as a numeric.
Reason
Code
2
10

IBM Support Center.
Explanation: Compressible request is
allowed for KSDS data set only.
job to define the data set as a
non-compressible data set.
Explanation: Catalog G1000Vxx will
cause the GDG to exceed the limit of
10,999.
Programmer Response: Clean up the
GDG in error then catalog G1000Vxx.
Explanation: Invalid data set type for
extended addressability.
Description
Explanation: Return code from OBTAIN.
12
16
Description
Explanation: An incorrect first character,
non-alphabetic, was detected. The
alternate index or path name is incorrect.
entry name.
Explanation: The data and index names
are not allowed for a catalog.
Programmer Response: Avoid the use
of names at the INDEX and DATA level
of DEFINE MASTERCATALOG and
DEFINE USERCATALOG.
Explanation: A syntax error was
encountered in examining a GDG name.
name. Run the job again.
Explanation: A reserved high-level
qualifier name was specified on an ICF
define operation. CATINDEX is a
reserved high-level qualifier.
name to use a different high-level
qualifier. Run the define operation again.
Explanation: The data name specified
for an SMS VSAM data set does not
orient to the same user catalog that the
cluster did.
Explanation: The index name does not
resolve to the same catalog as the
cluster name did.
RETURN CODE 150

Explanation: Name length error for an SMS construct.
Programmer Response: Clean up the

GDG in error then catalog G1000Vxx.
389
Reason
Code
2
4
6
Description
Explanation: An incorrect storage class
name length was detected.
Explanation: An incorrect data class
name length was detected.
Explanation: An incorrect management
class name length was detected.
Reason
Code
2
1. An access method services DEFINE

or IMPORT command specifies a
device type that was not system
generated into the system, or is not
acceptable for a catalog or data set.
2. The volume serial number specified
is incorrect, or the volume serial
number is missing.
RETURN CODE 152

Explanation: A non-empty catalog cannot be deleted.
Reason
Code
0
Description
Programmer Response: If the catalog
and all of its entries are to be deleted
specify the FORCE parameter on the
access method services DELETE
CATALOG command.
Description
Explanation: One of the following has
occurred:
Programmer Response: Specify a

device type or device name that is
acceptable to the system.
Explanation: An incorrect device name
was specified on a define of a
non-VSAM entry.
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
area. This condition arises when there is insufficient
virtual storage available for catalog management.
Reason
Code
2
10
Description
Explanation: A GETMAIN failure
occurred. There is insufficient virtual
storage available.
region size available to the step.
Explanation: A GETMAIN failure
occurred. There is insufficient virtual
storage available for the catalog
communication area.
region size available to the step.
RETURN CODE 168

Explanation: Unsupported device type.
390
RETURN CODE 172

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
x
2
Description
Explanation: The return code from a
failed DADSM RENAME.
Explanation: A duplicate name was
detected on a volume during a define of
a data set.
Programmer Response: Select another
data set name, scratch the original data
set from the volume, or ensure that there
are as many volumes as key ranges for
the define of a unique key sequenced
data set (KSDS).
RETURN CODE 176

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
Code
0
Description
Programmer Response: Delete any
unneeded data sets from the volume, in
order to make additional DSCBs
available, or recreate the volume with a
larger VTOC.
Reason
Code
x
Description
Explanation: Internal logic error.
IBM Support center.
RETURN CODE 184

RETURN CODE 178
Explanation: An error occurred during ICF catalog
processing of a VSAM partial release request.
Reason
Code
2
Description
Explanation: The open-for-output
indicator was found on in the catalog
while a partial release request was being
processed. Partial release processing
cannot occur if there are other users
opened to the data set.
Explanation: The data set is currently open and cannot

be deleted or altered. This condition arises when two
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
same volume.
Reason
Code
0
10
Programmer Response: Run an

IDCAMS verify against the data set to
reset the open-for-output indicator and
re-run the partial release request.
Explanation: The data set is not an
extended format VSAM cluster. Partial
release processing is supported only for
extended format VSAM clusters.
Explanation: The data set name passed
to a VSAM partial release request was
not a VSAM cluster data component.

name being passed is the VSAM cluster
data component and re-run the partial
release request.
Explanation: A DADSM partial release
request failed.
Programmer Response: Examine the
job and system log for related messages
explaining the DADSM failure.
perform partial release processing
against a data set defined with
guaranteed space. Guaranteed space
data sets are not supported for partial
release processing.
RETURN CODE 182
Description
Explanation: A rename is not allowed
for an open data set. The backout has
been done successfully.
Explanation: The data set is currently
open to another user.
Explanation: The data or index
component (or both) is in use, and the
data set cannot be deleted.
command again. To ensure proper
completion, specify a disposition
parameter of OLD, not SHR.
Explanation: The attempted DELETE or
ALTER of a PAGESPACE, or attempted
DELETE CATALOG FORCE that
implicitly deletes a PAGESPACE, cannot
be allowed. UCB indicates the possibility
of an active PAGESPACE on the
volume.
Programmer Response: If a
PAGESPACE is to be deleted or altered,
it must not be known at IPL as an
eligible PAGESPACE, or the volume
must not be online at IPL.
Explanation: The data set is in use by
another job; this reason code usually
means that a Backup-While-Open
(BWO) dump of the data set is in
progress.
requested function again after verifying
the data set is not currently being
dumped.
Explanation: Bad DADSM UPDATE parameter list.
391
RETURN CODE 186

Explanation: Error attempting to lock a catalog or
access a locked catalog.
Reason
Code
0
Reason
Code
2
Description
Explanation: Lock verification failed.
Programmer Response: An
unauthorized caller attempted to access
a locked catalog. To access a locked
catalog, a user must have read authority
to the profile IGG.CATLOCK of class
type FACILITY. Obtain the correct
Explanation: Access was denied for one
As a volume error code: Catalog

unavailable for the remainder of
processing which establishes volumes
as candidates for future extension. This
occurs during define of VSAM data sets
only when another error is encountered
during candidate processing. This code
appears as a volume error code for the
volumes that are not processed due to
the other error code which will appear in
the access method services jobstream
output.
v RACF, or an equivalent product, was

not active
v No MVS router exit was found
Programmer Response: Either define

the profile IGG.CATLOCK, activate
RACF, or supply an MVS router exit.
authorized for DEFINE LOCK.
Programmer Response: To use the
DEFINE LOCK command, a caller must
have read authority to the profile
IGG.CATLOCK of class type FACILITY.
Obtain the correct authorization. Run the
job again.
authorized for ALTER LOCK.
Programmer Response: A caller
attempted to issue either the ALTER
LOCK command for an unlocked
catalog, or the ALTER UNLOCK
command for a locked catalog for which
the caller was unauthorized. To use the
ALTER LOCK and ALTER UNLOCK
commands, a caller must have read
authority to the profile IGG.CATLOCK of
class type FACILITY. Obtain the correct
RETURN CODE 188

Explanation: As a catalog management return code:
392
Programmer Response: If this error

causes a job to end, contact the IBM
Support Center. Otherwise, it is only a
means of communicating a condition
within the system that is not an error.
Explanation: The catalog is temporarily
unavailable.
Programmer Response: Try the
request again at a later time. If a COPY
or IMPORT operation has failed, do a
DELETE RECOVERY and import a
backup copy of the catalog.
v No profile IGG.CATLOCK of class

type FACILITY was found
Description
Explanation: A required JOBCAT or
STEPCAT is not available for processing
of a catalog request. The system ignores
the request until the catalog is available.
RETURN CODE 190

Explanation: Authorization error on a facility class
function applied to SMS data sets.
Reason
Code
0
2
4
6
8
10
12
Description
Explanation: The function
BCS only.
DIRECTED CATALOG.
NONVSAM with no BCS.
NONVSAM with no NVR.
NVR with no BCS check.
NOSCRATCH.
GDG FORCE.
was ALTER
was
was DEFINE
was DEFINE
was DELETE
was DELETE
was DELETE
Reason
Code
14
16
Description
Explanation: The function was ALTER
UNCONVERT from SMS managed
VSAM data set back to non-SMS
managed.
Explanation: The user is not authorized
to perform a ATLDS define, alter or
delete request.
Programmer Response: Insure that the
user has read access authority to
STGADMIN.IGG.LIBRARY.
Reason
Code
28
30
34
40
RETURN CODE 192

Explanation: Maximum logical record length specified
is greater than 32,761 for a non-spanned data set.
Reason
Code
0
Description
maximum logical record length or define
the data set as spanned.
RETURN CODE 194
42
44
Explanation: An error occurred during multi-level alias

(MLA) facility processing.
46
Reason
Code
8
10
14
18
20
Description
Explanation: MLA was unavailable for
the request.
Explanation: MLA detected a damaged
master catalog record. A snap dump was
taken to aid in resolution of the problem,
and MLA facility in-storage tables were
invalidated.
invalidated.
invalidated.
invalidated.
50
Description
Explanation: An error occurred during a
generic search of the alias table for the
input data set name.
Explanation: MLA was unable to obtain
sufficient memory to hold its in-storage
tables.
Explanation: MLA was unable to obtain
sufficient memory to rebuild its in-storage
tables.
Explanation: The system number of
qualification was not between 1 and 4.
The search order of the multi-level alias
facility is undefined. All requests
requiring the multi-level alias facility will
fail until the situation is rectified.
Programmer Response: Use the
MODIFY CATALOG,ALIASLEVEL
operator command to send a valid level
of qualification.
invalidated.
invalidated.
Explanation: An error occurred during a
generic search of the alias table for the
input data set name.
Explanation: The MLA tables are
incorrect. The generic request cannot be
fulfilled.
RETURN CODE 196

Explanation: The data component control interval size
specified is greater than 32,767.
Reason
Code
0
Description
control interval size of the data
component.
RETURN CODE 198

Explanation: An attempt has been made to use an
unsupported feature.
393
Reason
Code
6
RETURN CODE 204

Description
Explanation: Invalid use of JOBCAT or
STEPCAT. The catalog pointed to by the
JOBCAT/STEPCAT resides on a device
that has a UCB defined above 16MB.
RETURN CODE 200
Explanation: Key specification extends beyond end of

maximum logical record.
Reason
Code
0
Explanation: The specified or defaulted control interval

size of the index component is greater than the
maximum block size of the index device.
Description
key length, change the key position, or
increase the logical record length.
RETURN CODE 208

Reason
Code
0
Description
control interval size of the index
component or use a different device with
a larger maximum block size.
Explanation: The buffer space specified is too small.

The buffer size specified is too small to contain the
minimum number of control intervals for the type of
VSAM data set being defined or altered. An indexed
data set requires enough virtual storage for 2 data
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
error.
Reason
Code
0
4
6
Description
Explanation: An error was detected
during a call to SMS.
Programmer Response: Print the OBR
record to get the appropriate error
messages.
Explanation: An error was detected
during a call to determine whether all
volumes belong to the same storage
group.
Explanation: An incorrect definition was
passed to the SMS.
Explanation: Insufficient space was
provided for that definition to the SMS
subsystem.
alter the expiration date of an
SMS-managed data set that was defined
with a management class whose
maximum number of retention days was
specified as zero.
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.
394
Reason
Code
0
Description
buffer size specified through the
BUFFERSPACE parameter of the
DEFINE command.
buffer size specified through the
BUFFERSPACE parameter of the
ALTER command.
RETURN CODE 210

Explanation: Subsystem call error.
Reason
Code
x
Description
Explanation: Return code from
Subsystem call.
RETURN CODE 212

Explanation: Control interval size calculation
unsolvable. This condition arises should catalog
management be unable to compute an acceptable
control interval size value. This condition only occurs in
the DEFINE and IMPORT commands.
Reason
Code
0
RETURN CODE 222

Description
Explanation: The control interval and
the control area calculations are
unsolvable with specified parameters.
Programmer Response: Determine
which of the specifications may have
caused the problem.
The following are the possible
specifications:
v Buffer size
v Control interval size
Explanation: Alter new name of a GDS, non-VSAM or

cluster failed because an ACS service returns a
non-zero return code.
Reason
Code
ACS reason
code =
catalog
reason code
+ decimal
256
Description
Explanation: Adding decimal 256 to the
catalog reason code will give the correct
ASC reason code. The ACS services
return and reason codes are
documented in the OS/390 DFSMSdfp
Diagnosis Reference
v Device type
4
10
12
v Logical record size

Explanation: Specified and default
values result in only one control interval
per control area for a key-sequenced
data set.
Explanation: Using the specified or
default values, the maximum index
control interval size for the device would
be exceeded for nonunique objects.
data control interval size or decrease the
data control area size.
Explanation: Using the specified or
default values, the maximum index
control interval size for the device would
be exceeded for unique objects.
data control interval size or decrease the
data control area size.
Explanation: The buffer space is too
small for a nonunique object.
buffer size. Run the job again.
Explanation: The specified and default
value result in only one control interval
per control area for a variable
relative-record data set.
Programmer Response To ACS reason code add

decimal 256 to obtain the correct error code for
reference in the appropriate SMS SUB-System
Message Manual. Refer to the Storage Management
Subsystem Reason Codes, Sub-Sections Subsystem
Interface Reason Codes and ACS Service Reason
Codes in the OS/390 DFSMSdfp Diagnosis Reference &
for a complete description of the reason codes.
RETURN CODE 224
Explanation: A field in a catalog entry has exceeded
the maximum allowable number of repetitions. This
condition arises when one of the repeating fields within
the catalog entry is to be extended, and the extension is
not possible. For example, should more than 255
volume serials be attempted to be placed in the entry,
as might happen when an ALTER command attempts,
through the ADDVOLUMES parameter, to add more
candidate volumes to the entry.
Reason
Code
0
2
RETURN CODE 214
Explanation: Subsystem call error.
Reason
Code
x
Description
Explanation: The maximum number of
volume extent (group occurrence)
pointers have been processed.
the excessive values are being supplied.
Explanation: More than 255 volume
extent (group occurrence) pointers exist
in a record, or more than 125 alternate
indexes exist in the upgrade set.
System Action: The additional values
are not added to the entry.
Description
Explanation: Return code from
Subsystem call.

the excessive values are being supplied.
395
RETURN CODE 226
Reason
Code
13
Explanation: Test authorization macro failed. The caller

is not authorized to perform the requested function.
Reason
Code
4
26
Description
Explanation: To OPEN a catalog, the
caller must be running in key 0 - 7, must
be in supervisor state, or must be APF
authorized.
To do CLOSE or EOV processing for a
catalog the caller must be running in key
0 - 7, must be in supervisor state, or
must be APF authorized.
To process the CONVERTV function, the
caller must be APF authorized.
Scheduler type superlocate
(non-generic) is restricted. To issue
LOCATE SVC, the caller must be
running in key 0 - 7, must be in
supervisor state, or must be APF
authorized.
28
29
| 47
|
|
|
|
|
|
|
|
|
48
Programmer Response: Respond to

the particular error accordingly. If there is
no fix for the problem, contact the IBM
Support Center.
Description
ECS activation was requested for a
catalog with the NOECSHARING
attribute.
Returned on a non-ECS system when
an attempt is made to access a catalog
that is ECS-active on another system.
Catalog is temporarily in use by a
non-ECS system.
ECS-activation of a catalog is requested
but the catalog does not have
cross-system share options or is not on
a shared volume.
A Coupling Facility error has occurred.
Correct the coupling facility error (see
the IXL messages that accompany the
coupling facility error). Next, reactivate
ECS by ensuring that all systems are
connected to the ECS structure, and
then issue the F
CATALOG,ECSHR(AUTOADD)
command.
An attempt was made to add a catalog
to the Coupling Facility structure for
Enhanced Catalog Sharing use, but the
structure is full.
size of the ECS structure definition in the
CFRM policy.
RETURN CODE 228

Enhanced Catalog Sharing request. The following
reasons may be corrected by the installation. Codes not
shown indicate an internal system error.
Reason
Code
x
2
3
4
9
396
Description
An internal logic error has occurred.
IBM Support Center.
ECS workarea storage is not available.
Coupling Facility connection error. If
received with message IEC377I, fields
aaaa and bbbb contain the return and
reason codes from IXLCONN.
An ECS request was made but the
system is not ECS-active.
Coupling Facility disconnection error. If
received with messge IEC377I, fields
aaaa and bbbb contain the return and
reason codes from IXLDISC.
RETURN CODE 232

Explanation: An error was encountered while Catalog
Management was performing system management
facility (SMF) processing.
Reason
Code
x
Description
Explanation: The reason code
represents the catalog management
return code encountered while
performing SMF processing. The catalog
management return codes correspond to
the return codes listed for this message.
Programmer Response: Examine the
reason code returned. Run the job again
after performing the required corrective
measures.
RETURN CODE 238

Explanation: No user catalog entry in the master
catalog for Convert Volume processing.
Reason
Code
0
Reason
Code
16
Description
Programmer Response: Use the
access method services IMPORT
CONNECT command to put an entry for
the user catalog into the master catalog.
RETURN CODE 240

Explanation: Required DD statement not supplied.
Reason
Code
0
14
18
Description
Explanation: An ALTER of expiration
date was specified, but no DD statement
was supplied.
Explanation: The DEVTYPE function
failed during DEFINE processing.
Programmer Response: Provide the
required parameter, ensure that the DD
statement name is correctly spelled, or
that the DD statement is present for the
step. Also, ensure that the volumes can
be allocated by dynamic allocation. If
these are correct, contact the IBM
Support Center.
Explanation: An incorrect device type
was encountered during DEFINE
processing.
Support Center.
Explanation: A delete of a unique object
was specified, but no DD statement was
supplied.
22
34
Description
Explanation: A delete of a non-VSAM
object with the scratch option was
specified, but no DD statement was
supplied.
Support Center.
Explanation: A delete of a VSAM object
with the erase option was specified, but
no DD statement was supplied.
Support Center.
Explanation: There was no DDname
match found in the TIOT.
Support Center.
determine the DD statement name for a
CRA.
Support Center.

Support Center.
397
Reason
Code
36
Description
Explanation: Either a required DD
statement is missing or, if the user is
dynamically allocating the data set, the
limit to the number of data sets that can
be dynamically allocated has been
exceeded.
be allocated by dynamic allocation.
Check the DYNAMNBR parameter in the
users LOGON procedure to determine if
the limit on the number of data sets that
can be dynamically allocated was
exceeded. If these are correct, contact
the IBM Support Center.
RETURN CODE 242
Reason
Code
x
System Action: The system voids the

delete action on that data set.
the erasure was impossible. Alternatively,
run the DELETE command again with
the NOERASE option.
RETURN CODE 246

Explanation: An internal error has occurred while
processing a catalog request.
Reason
Code
x
Explanation: A physical I/O error occurred trying to

erase the data set being deleted.
Reason
Code
x
Description
Explanation: The reason codes
correspond to the VSAM OPEN error
codes. The system write message
IEC161I with this message.
Description
Explanation: An internal error has
occurred.
System Action: An SVC dump may be
produced for the error, depending on the
reason code. Processing of the catalog
request is terminated.
Description
correspond to the VSAM Record
Management error codes.

an SVC dump was created for this
failure, and contact the IBM Support
Center for assistance.

again with the NOERASE option. The
data set cannot be deleted.
RETURN CODE 250

RETURN CODE 244
Explanation: Erase action failed. This condition arises
when Catalog Management is unable to open the
VSAM data set being deleted.
Explanation: VSAM Record Management has found a

logical error during erase processing while deleting a
VSAM data set.
Reason
Code
x
Description
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.
398
RETURN CODE 254
entname
Explanation: An error was encountered during catalog

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
2
Description
Explanation: The opening of a catalog
failed during catalog reorientation.
Explanation: The allocation of a catalog
unit failed.
IDC3010I
UNABLE TO OPEN dsname
The entry name.
If no catalog was specified, ensure that the first-level

qualifier of the data set name is the name of a user
catalog or the alias of a user catalog.
Source: DFSMSdfp
Detecting Module: IDCCN01, IDCLC01, IDCMP01,
IDCSA02, and IDCXP02 processing associated with the
entry name.
Explanation: The dname specified in the command

indicated either concatenated catalogs or a different
data set.
IDC3013I
v The data set name supplied by the caller already

exists in the specified catalog.
dsname
The data set name.
System Action: The command ends with a condition
code of 12.
dname specified in the command does not identify a DD
statement that defines concatenated catalogs, unless
the desired catalog is the first in the concatenation.
Ensure that the command and the JCL specify the
same data set.
Source: DFSMSdfp
IDCCN01, IDCDE01, IDCDE02, IDCDL01, IDCLC02,
IDCMP01, IDCRC02, IDCRM01, IDCRS01, IDCRS06,
IDCSA02, IDCXP01
IDC3012I
ENTRY entname NOT FOUND
Explanation: The data set name supplied by the caller

is not in the specified catalog. If a catalog was not
specified, the entry name is the first-level qualifier of a
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
catalog management error code values.
In the Time Sharing Option/Extensions (TSO/E)
environment the second-level message is not displayed,
except by request. To request it, enter a question mark
(?) after the TSO READY message.
DUPLICATE DATA SET NAME
Explanation: One of the following conditions has

occurred:
v The data set name supplied by the caller already

exists as the first-level qualifier of a data set name in
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
or an alias name in the catalog.
See the associated second-level message for the
specific catalog management error code values.
command.
entry name is spelled correctly. Check the use of the
JOBCAT and STEPCAT catalogs, if employed. Ensure
that the data set name or the first-level qualifier of the
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
catalog.
Source: DFSMSdfp
IDC3014I
CATALOG ERROR
Explanation: An error occurred during a catalog

operation. See the associated second-level message for
the specific catalog management error code values.
399

System Action: The system ends processing
associated with the catalog error.
programmer response associated with the second-level
message.
IDC3017I
INSUFFICIENT SPACE IN CATALOG
Explanation: The catalog is full. There is no more

space on the volume in which the catalog resides, or
the maximum number of extents has been reached. See

IDC3015I
Source: DFSMSdfp
** VSAM CATALOG RETURN CODE IS

reason-code
Explanation: System interface errors. Catalog

management returned the return code and reason code
indicating either a catalog error or exceptional condition.
return-code
The return code
reason-code
The reason code, which is one of the following:
Code
Explanation
004
Non existent catalog
122
Common filter service error
186
Catalog log related error
188
Catalog temporarily unavailable
System Action: Processing associated with the error

return code is halted.
Source: DFSMSdfp
Application Programmer Response: Scratch

unneeded data sets from the volume. Delete unneeded
VSAM data sets. See your system programmer for
assistance in reorganizing the catalog.
Source: DFSMSdfp
IDC3018I
SECURITY VERIFICATION FAILED
Explanation: The number of attempts was exceeded

by the operator, or the user-specified verification routine
failed to authorize use of the data set or the callers
RACF authorization was inadequate. See the
associated second-level message for the specific
password specified, obtain the required RACF
authorization, or determine why the verification routine
did not allow access.
Source: DFSMSdfp
IDC3016I
CATALOG IS NOT AVAILABLE
Explanation: A required catalog is unavailable to

perform the specified command. See the associated
second-level message for the specific catalog
management error code values.

IDC3019I
INVALID ENTRY TYPE FOR

REQUESTED ACTION
Explanation: This condition arises if, for example, an

attempt was made to DELETE an index component of a
VSAM data set. See the associated second-level
message for the specific catalog management error
code values.

catalog specified by the command exists or determine
why it cannot be accessed.

Source: DFSMSdfp

specified action is allowed for this entry type. The entry
400
type can be validated by the LISTCAT command.
RELATE parameter is correct.
Source: DFSMSdfp
Source: DFSMSdfp
IDC3020I
IDC3023I
UNABLE TO ALLOCATE SPACE ON

USER VOLUME
UNEXPIRED PURGE DATE
Explanation: A specified volume cannot accommodate

either the initial allocation of space or a subsequent
extension. See the associated second-level message
for the specific catalog management error code values.
Explanation: An attempt to delete an entry failed

because its expiration date has not been reached. The
PURGE option was not specified. See the associated


Application Programmer Response: Scratch

unneeded data sets from the volume, or run an ALTER
command to add candidate volumes for the data set.

PURGE option. Run the command again.
Source: DFSMSdfp
Source: DFSMSdfp

IDC3024I
IDC3021I
USER VOLUME NOT MOUNTED
Explanation: An attempt to update the volume table of

contents (VTOC) on a volume failed because the
volume was not mounted. See the associated
volume is mounted.
Source: DFSMSdfp
IDC3022I
INVALID RELATED OBJECT
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
DEFINE command so that the entry named in the
VOLUME OWNED BY ANOTHER

CATALOG
Explanation: Only one catalog may own or allocate

space upon a given volume. See the associated
following:
v Specify an unowned volume. Run the command
again.
v Use the ALTER REMOVEVOLUMES command to
reset the volume ownership if a catalog does not own
the volume.
Source: DFSMSdfp
IDC3025I
INSUFFICIENT SUBALLOCATION DATA

SPACE
Explanation: A volume does not contain a data space

with sufficient room for allocation of another virtual
storage access method (VSAM) data set. See the
401

v Delete any unneeded data sets or data spaces from

the volume to make additional DSCBs available.
v Recreate the volume with a larger VTOC.

following:
v Use the DEFINE command to create additional data
space.
v Delete unneeded VSAM data sets.
v Decrease the amount of storage required by the
object being defined.
Source: DFSMSdfp
IDC3026I
DUPLICATE DATA SPACE NAME ON

VOLUME
Explanation: A DEFINE operation specifies the name

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
sequenced data set (KSDS), with the UNIQUE attribute,
which has more than one key range on the same
volume. See the associated second-level message for
the specific catalog management error code values.
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
each UNIQUE key range is on a separate volume.
Source: DFSMSdfp
IDC3027I
NO SPACE IN VTOC OR VTOC INDEX
Explanation: During the definition or extension of a

data space, an attempt was made to perform a DADSM
allocate or extend function, but either there was no
space in the volume table of contents (VTOC) for an
additional data set control block (DSCB) or there was
not enough space in the VTOC index for a new entry.
Source: DFSMSdfp
IDC3028I
DATA SET IN USE
Explanation: The data set is currently open and

cannot be deleted. This condition arises when two
different jobs are referencing the same virtual storage
access method (VSAM) data set simultaneously. See
command again. Specify disposition of OLD, not SHR.
Source: DFSMSdfp
IDC3029I
LOGICAL RECORD LENGTH EXCEEDS

32761
Explanation: The maximum logical record length

specified is greater than 32,761 for a non-spanned data
set. See the associated second-level message for the
Application Programmer Response: Reduce the
maximum logical record length or define the data set as
spanned.
Source: DFSMSdfp
IDC3030I
CONTROL INTERVAL SIZE TOO

LARGE
Explanation: The data component control interval size

specified is greater than 32,768 or the index component
control interval size is greater than the maximum block
size of the index device. See the associated

following:


402

following:
v Reduce the control interval size.
v If the error occurred due to the index components
device type, use a different device with a larger
blocksize.
IDC3033I
VOLUME RECORD NOT FOUND IN

CATALOG
Explanation: This condition arises when a function

requires a volume that is not owned by the virtual
storage access method (VSAM) catalog being used.
Source: DFSMSdfp

IDC3031I

volumes specified have been defined in the catalog
against which the request is being issued.
KEY EXTENDS BEYOND MAXIMUM

RECORD LENGTH
Explanation: The KEY specification extends beyond

the end of the maximum logical record. See the
Source: DFSMSdfp

IDC3034I

COMMAND FAILED DUE TO
DUPLICATE RACF PROFILE
v Reduce the key length
Explanation: As a result of an IMPORT, IMPORTRA

or a DEFINE command, virtual storage access method
(VSAM) catalog management has attempted to
establish a profile. This attempt failed because a profile
with the same name exists. Note that in addition to this
message, an IDC3009I message with a 114 return code
will also be issued.
v Change the key position

following:
v Increase the record length

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
(VSAM) data set being defined. See the associated
BUFFERSPACE parameter of the DEFINE command.
Source: DFSMSdfp

reason code on the accompanying IDC3009I message.
Take the recommended action for this reason code. Run
the job again.
Source: DFSMSdfp
IDC3036I
DATA SET COULD NOT BE DEFINED

TO SECURITY SUBSYSTEM
Explanation: Catalog management attempted to

define a RACF profile for the data set. The security
subsystem rejected the RACF DEFINE command
because the characteristics of the caller and the data
set make the data set not eligible for definition.
Application Programmer Response: Compare the
characteristics of the data set with the inclusion
standards of the security subsystem package as
specified in the installation security subsystem
documentation. Modify the data set characteristics. Run
the job again.
Source: DFSMSdfp
403
IDC3037I
STORAGE FOR NUMBER OF ENTRIES

EXCEEDS 16M LIMIT
Explanation: IDCAMS runs below the 16M line and is

unable to satisfy the users request due to a storage
constraint.
Application Programmer Response: The user can
modify the command to avoid this situation. For
example, when issuing a LISTCAT level, additional
qualifiers can be specified which will avoid exhausting
storage.
IDC3062I
** CARTRIDGE LABELS AND

INVENTORY RECORD NOT RESTORED
Explanation: An error was encountered while

relabeling a mass storage volume. The attempt to
restore the labels of the cartridges and Inventory data
set to their original status failed. The volume serial
mismatch may exist between the cartridge labels and
volume label for the volume. See the preceding
problem as identified in the preceding message. Take
the following actions for the command that failed:
v For a rename operation failure for ADDV, run ADDV
rename operation.
mounting. The values specified for the VOLUME and
number.
serial number as recorded in the cartridge labels and
the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number. Note that
the security check for non-virtual storage access
method (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. This
allows the original volume serial number of a VSAM
volume to be restored if the volume is left partially
renamed.
indicating the status of the rename operation, run
LISTMSVI to determine whether the volume is
flagged for recovery purposes. If the mismatch flag is
set in the volume record, LISTMSVI not only lists the
404

highlights the preceding volume and that serial
number is recorded in the volume label of the
volume.
v For a rename operation failure for MODIFYV, recover
from a MODIFYV rename by:
condition
mismatch condition
Running STOREV to complete or retry the rename
rename. For the DD statement requirements, the
proper VOLUME and NEWSERIAL parameter
values, and use of LISTMSVI, refer to the
description above for an ADDV rename failure.
Source: DFSMSdfp
IDC3066I
** UNABLE TO CLEAR INCOMPLETE COPY FLAG FROM INVENTORY

RECORD
Explanation: The incomplete-copy flag in the

Inventory record for the volume could not be cleared.
the failure.
System Action: The system ends the command with
an error message.
problem as indicated in the preceding message. Take
one of the following actions for the command that failed:
v For a copy operation failure in COPYV, run COPYV
again to complete the copy operation to the
incomplete copy volume. COPYV will reuse the
copy. Or run SCRATCHV to scratch the incomplete
copy volume before rerunning the COPYV command.
If COPYV ends without indicating the status of the
copy operation, run LISTMSVI to determine whether
the volume is flagged for recovery purposes. If the
incomplete copy flag is set in the copy volume

for the preceding copy volume.
v For a copy operation failure for RECOVERV, run
RECOVERV again to complete the recover operation
to the target volume that is flagged as an incomplete
copy volume. Otherwise, run SCRATCHV to scratch
the target volume. The incomplete copy volume may
even be used as the target volume in the
CONVERTV command. In all cases, the empty
volume table of contents (VTOC) check or security
check for password protected data sets is bypassed.
is not required for the volume and if provided, must
specify deferred mounting. If the RECOVERV
command is run again, the DD statement is not
required for the target volume, which is flagged as an
incomplete copy, unless the volume serial number of
the target volume is different from the source volume.
If a DD statement is provided for the target volume,
deferred mounting must be specified.
If a virtual storage access method (VSAM) catalog is
on the volume, a DD statement for the catalog is not
required. If one is provided, specify deferred
mounting.
If RECOVERV ends without indicating the status of
the recover operation, run LISTMSVI to determine
If the incomplete copy flag is set in the target volume
for the preceding volume.
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
incomplete copy volume. Otherwise, run SCRATCHV
to scratch the target volume. The incomplete copy
volume may even be used as the target volume in
the RECOVERV command. In all cases, the empty
VTOC check or the security check for password
protected data sets is bypassed.
is not required for the incompletely copied volume
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 specify deferred mounting. If a VSAM catalog is
on the volume and a DD statement is provided for
the catalog, the DD statement must also specify
deferred mounting.
If CONVERTV ends without indicating the status of
the conversion operation, run LISTMSVI to determine

for the preceding volume.
Source: DFSMSdfp
IDC3067I
{FROM|TO}VOLUME volser OWNED BY

A VSAM CATALOG
Explanation: A virtual storage access method (VSAM)

catalog owns the specified volume. The volume cannot
be used.
FROM|TO
Indicate which volume is unusable for those
numbers.
volser

a message.
Application Programmer Response: Before running
the command, do one of the following:
v Select a volume not cataloged in a VSAM catalog.
v Use the access method services DELETE command
to delete all VSAM data sets and data spaces on the
volume, provided the volume is active and
mountable.
v Do not specify a new serial number through the
NEWSERIAL parameter in the command statement.
System Programmer Response: Enter the access
catalog.
to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCN01, IDCCO01,
IDCRV01
If the incomplete copy flag is set in the target volume

405
IDC3070I
** text NOT UPDATED IN VOLUME

LABEL [OF TO VOLUME]

SERIAL
OWNER
SERIAL, OWNER
Either the volume serial number or owner name or both
was not updated in the volume label as requested. A
mismatch may exist between the cartridge labels and
the volume label for the mass storage volume. See the
preceding message for further explanation of the
problem.
OF TO VOLUME
Indicates which volume could not be updated
for those commands processing both a source
and target volume having the same volume
serial number.
a message reflecting the severity of the error.
Application Programmer Response: Take one of the
following actions for the command that failed:
v For a rename operation failure for ADDV, run ADDV
rename operation. 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. The
values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is
recorded in the Inventory data set. If the volume
record is identified by the new volume serial number
because the cartridge labels have been updated,
both the VOLUME and NEWSERIAL parameters
must specify the new volume serial number.
Otherwise, specify the old volume serial number with
the VOLUME parameter. Note that the 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. This
allows the original volume serial number of a VSAM
volume to be restored if the volume is left partially
renamed.
If ADDV, MODIFYV, or STOREV ends without
indicating the status of the rename operation, run
LISTMSVI to determine whether the volume is
flagged for recovery purposes. If the mismatch flag is
set in the volume record, LISTMSVI not only lists the
highlights the volume report with a note that a
406
rename operation failed for the preceding volume and

that the serial number is recorded in the volume label
of the volume.
v For a rename operation failure for MODIFYV, recover
from a MODIFYV rename by:
serial mismatch condition.
Running ADDV both to activate the volume and
condition
rename operation if the volume to complete or
retry the rename operation if the volume is active
and if a duplicate volume serial number is desired
as a result of the rename.
v For a rename operation failure for STOREV, run
retry the rename operation. For the DD statement
requirements, the proper VOLUME and NEWSERIAL
parameter values, and use of LISTMSVI, refer to the
description above for an ADDV rename failure.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCN01, IDCRV01
IDC3071I
** COPY NOT COMPLETED
Explanation: The copy operation failed. The target

volume is marked incomplete in the Inventory data set
and will be reused when the command is run again.
the failure.
an error message.
error as identified by the preceding message. To run the
command again, follow the recovery actions identified
for the recovery of space management.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCRV01
IDC3072I
VOLUME ATTRIBUTES DO NOT AGREE

WITH GROUP ATTRIBUTES
Explanation: One or more of the specified volume

attributes do not agree with the group level
specifications for all general-use volumes belonging to
the group.

Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCV01
IDC3081I
The possible attributes are as follows:
** RECORD NOT RETRIEVED FROM

INVENTORY FOR COPY yyddd, NO. nnn
v exclusive/shared
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
date. See the preceding message for a further
explanation of the error.

an error message.
yyddd
The date in year and days.
nnn
The copy sequence number.

LISTMSVI command to list the group level
specifications. Run the command again with volume
attributes specified that correspond to the group that the
volume is being assigned.

a message unless additional copies are to be
processed.
v bind/nobind

Source: DFSMSdfp
Detecting Module: IDCCN01, IDCRV01

error as indicated in the preceding message. Before
running the command again, ensure that copy date and
sequence number are specified correctly.
Source: DFSMSdfp
IDC3077I
** CART csn1 [csn2] NOT IN MSF FOR

VOL volser
Explanation: The cartridges assigned to the specified

volume cannot be found in the Mass Storage Facility
(MSF). See the preceding message for additional
information.
csn1
csn2

not in the MSF.
volser

a message.
problem as indicated in the preceding message. If the
cartridges are outside the MSF, enter the cartridges
again. Run the command again.
Detecting Module: IDCAV01, IDCRR01, IDCRV01

IDC3082I
** COPY NOT PERFORMED
Explanation: The copy operation could not be started

to the target volume. The target volume remains usable
since the original data on the volume has not been
destroyed. See the preceding message for a further
an error message.
error as identified in the preceding message. To run the
command again, follow the recovery actions for space
management.
407
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCRR01, IDCRV01
IDC3089I
A DUPLICATE VOLUME EXISTS WITH

SERIAL NO. volser
Explanation: More than one volume with the specified

volume serial number is recorded in the Inventory data
set. Duplicate volumes within the same Mass Storage
System occur when:
v The record is deleted from the Inventory data set for
an ejected volume, and before the volume is
reentered the serial number has been assigned to
another volume.
v The record for an ejected copy volume is deleted
from the Inventory data set and the copy is
reentered.
v A volume is entered in the Mass Storage Facility from
another Mass Storage System.
volser

an error message.
LISTMSVI command to obtain the sequence one and
sequence two cartridge serial numbers of the correct
volume to be processed. Run the command again
specifying either cartridge serial number with the
CARTRIDGE parameter so that the command can
select the correct volume.
Source: DFSMSdfp
Detecting Module: IDCCN01, IDCRV01
IDC3090I
VOLUME volser CANNOT BE

RELABELED: READONLY ATTRIBUTE
IS ASSIGNED
Explanation: The specified volume has the attribute

assigned which prohibits any changes to be made to
the volume.
volser

a message identifying the severity of the error.
recorded as active in the Inventory data set, use the
MODIFYV command to change the READONLY
408
attribute to READWRITE. If the volume to be relabeled

is inactive, use the ADDV command and specify the
READWRITE parameter.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCEV01
IDC3092I
FILE PARAMETER WITH DEFERRED

MOUNT REQUIRED
Explanation: The volume is recorded in the Inventory

data set as:
v Incompletely created
v Incompletely copied
v Having a volume serial number mismatch
These problems may cause dynamic allocation of the
volume to encounter an error. Therefore, this command
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
mounting to prevent allocation from mounting the
volume.
a message identifying the severity of the error.
command again with the FILE parameter specifying the
name of a JCL DD statement which allocates a unit with
deferred mounting.
Source: DFSMSdfp
IDC3094I

RENAMED; COPIES EXIST
Explanation: The volume serial number cannot be

changed on the specified volume because there are
existing copies of the volume made through the COPYV
command.
volser

an error message.
SCRATCHV command to scratch all existing copies of
the volume. Run the command again. If the copies must
be saved, run the EJECTV command with the
NORECORD option for each copy volume, or run the
REMOVEVR command if the copy is already ejected.
This deletes the copy volume record information
recorded in the Inventory data set and permits the
original volume to be renamed.
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
Detecting Module: IDCAV01, IDCMV01, IDCRV01,
IDCSR01
IDC3099I
LENGTH OF CARTRIDGE SERIAL

NUMBER csn INVALID
Explanation: A cartridge serial number cannot be less

than eleven characters in length.
csn
The cartridge serial number containing the

incorrect length.

a message unless additional cartridges have been
specified for processing.
Application Programmer Response: Specify an 11or 12-character cartridge serial number. Run the
command again. If a cartridge serial number of 11
characters is specified, the command extends the
cartridge serial number to 12 characters by inserting a
blank character in the fourth position from the left. If you
specify 12 characters, include the value in quotes
because a blank is required as the fourth character.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCO01, IDCCV01,
IDCEC01, IDCEV01, IDCLV01, IDCMC01, IDCRL01
IDC3113I
INVALID LEVEL PARAMETER
Explanation: There is an asterisk (*) in the last

position of the LEVEL parameter. This is an error.
asterisk from the last position of the LEVEL parameter.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCO01, IDCCV01,
IDCEC01, IDCEV01, IDCLV01, IDCMC01, IDCRL01
IDC3114I
VOLUME ser HAS DOWN LEVEL

SPACE
Explanation: The specified volume that belongs to a

group as a general use volume is being:
v Activated through the use of the ADDV command
v Made a general use volume in a group through the
use of the MODIFY command.
In either case, the base volume record in the Inventory
data set indicates the volume has down level space. If
the MODIFY command is being used, the following
applies:
v A JCL DD statement was not provided (or was
provided but allocated to a volume different than the
volume being modified) and the attempt by the
MODIFY command dynamically to allocate the
volume failed.
If the ADDV command is being used, the following
applies:
v A JCL DD statement was not provided specifying
deferred mount and the attempt by the ADDV
command dynamically to allocate the volume failed.
ser
System Action: The system ends the MODIFYV or

ADDV command.
Application Programmer Response: Either provide
the appropriate OS/VS JCL DD statement or allow the
MODIFYV or the ADDV command dynamically to
allocate the volume. Run the MODIFYV or ADDV
command again. If dynamic allocation is failing,
determine the reason for this failure before running the
job again.
409

v BUFNI
Source: DFSMSdfp
v REPLICATE
Detecting Module: IDCLD01
v SHAREOPTIONS
v CONTROLINTERVALSIZE
v FREESPACE
v IMBED
v NOREPLICATE
v RECORDSIZE
v STRNO
IDC3143I
THE OUTPUT DATA SET CANNOT BE

THE SAME AS THE INPUT DATA SET

command.
Explanation: The data set specified on the

Outfile/Outdataset parameter is the same one that the
system is exporting.

catalog format to be defined. Remove the incorrect
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.
Source: DFSMSdfp
IDC3145I
INVALID PORTABLE DATA SET

ORGANIZATION
Explanation: An attempt was made to export either a

virtual storage access method (VSAM) data set or a
user catalog, using a VSAM data set as the portable
data set. The portable data set can be only a sequential
access method file.
Application Programmer Response: Change the
specification of portable data set to sequential
organization.
Source: DFSMSdfp
IDC3170I
ICF CATALOG PARAMETER SPECIFIED

FOR A VSAM CATALOG
Explanation: During the define of a virtual storage

access method (VSAM) user or master catalog, a
parameter applicable only to an ICF catalog was
encountered. The parameter has been specified at the
catalog, data or index component levels. A VSAM
catalog is being defined because the VSAMCATALOG
parameter has been specified or defaulted.
The parameter is one of the following:
v BUFND
410

Source: DFSMSdfp
IDC3174I
SPECIFIED MAXIMUM RECORD SIZE

LESS THAN REQUIRED MINIMUM
Explanation: During the define of an ICF catalog, the

value specified for the data component maximum record
size was found to be less than the minimum required
value, 4086 bytes. The maximum record size value
specified for the data component will override any value
specified for the catalog component.
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
specified for the data component is at least the
minimum required value.
Source: DFSMSdfp
IDC3175I
RESTRICTED VVDS NAME SPECIFIED

FOR INVALID OBJECT TYPE
Explanation: During the define of an object, not a

NONINDEXED (ESDS) cluster, the specified name was
found to have the format of the restricted virtual storage
access method (VSAM) volume data set (VVDS) prefix,

SYS1.VVDS.V. Define processing will disallow the use
of any name having this prefix if the name is not
specified at the cluster component level of a DEFINE
CLUSTER subcommand with the NONINDEXED
parameter specified. This prefix has a special use and
should only be specified to define a VVDS.
command.
data set name specified in the NAME parameter if a
VVDS is not to be defined. If a VVDS is to be defined,
specify the NONINDEXED parameter.
JCL.
Source: DFSMSdfp
IDC3176I
VSAM VOLUME DATA SET VOLUME

SERIAL NUMBER SPECIFICATION
ERROR
Explanation: During the define of a virtual storage

access method (VSAM) volume data set (VVDS), the
volume serial number specified by volser of the VVDS
name, SYS1.VVDS.Vvolser, did not match the volume
serial number specified on the VOLUMES parameter.
Only the first volume serial number specified by
VOLUME is valid and is compared.
command.
NAME and VOLUMES specifications. Change the
parameter in error. Run the job again.
Source: DFSMSdfp
IDC3179I
INCORRECT SPECIFICATION OF
EXPIRATION DATE
Explanation: Using the TO parameter, an access

method services ALTER or DEFINE command specified
an incorrect expiration date.
System Action: The application aborts with a return
code of 12.
Application Programmer Response: Respecify the
TO parameter. The year must be a four-digit number
ranging from 1900 to 2155 or a two-digit number

ranging from 00 to 99. The day must be a three-digit
number ranging from 001 to 366. The expiration date
must not be less than the current date.
Source: DFSMSdfp
IDC3183I
UNABLE TO PROCESS SMS

CONSTRUCTS
Explanation: An access method services DEFINE or

IMPORT command specified storage management
subsystem (SMS) constructs, but during processing of
the command, SMS was not available to process any
constructs.
command.
Application Programmer Response: If the data set
must reside on managed storage, ensure that the SMS
is operational. Enter the command again.
If the data set can reside on non-SMS managed
storage, enter the command again without specifying an
SMS construct.
Source: DFSMSdfp
IDC3184I
DUPLICATE VOLUMES SPECIFIED FOR

NON-KEYRANGE DEFINITION
Explanation: A DEFINE command for a data set

specified duplicate volume serials for a non-keyrange
request.
command.
VOLUMES parameter for duplicate volume serial
names. Either code keyranges or remove the duplicate
name.
Source: DFSMSdfp
Detecting Module: IDCDE01, IDCMP01
IDC3185I
TOO MANY VOLUMES SPECIFIED
Explanation: A DEFINE command for a storage

management subsystem (SMS) managed data set
specified more than 59 volume serial numbers. 59 is the
maximum volume serials.
DEFINE command.
Application Programmer Response: Reduce the
amount of volume serial numbers in the VOLUMES
parameter to 59 or less. Submit the command again.
Source: DFSMSdfp
411
IDC3186I
INVALID VOLUME SERIAL SPECIFIED
Explanation: An attempt was made to define a

non-SMS-managed data set with a volume serial of *.
A volume serial of * is only permitted for
SMS-managed data sets.
System Action: The system fails the job.
User Response: Correct the volume serial and run the
job again.
Source: DFSMSdfp
IDC3187I
THE VOLCATALOG ENTRYNAME IS

INVALID
Explanation: The entryname specified on an IDCAMS

DEFINE USERCATALOG command is not valid for a
volume catalog. The general volume catalog must be in
the form:
xxxxxxxx.VOLCAT.VGENERAL
Where xxxxxxxx is either SYS1 or another high level
qualifier specified in the LOADxx member of
SYS1.PARMLIB. The specific volume catalog must be in
the form:
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.
command.
entryname.
Source: DFSMSdfp
IDC3190I
keywd PARAMETER INVALID WITH

ENTRY TYPE
Explanation: The specified key word is improper for

the type of object being altered. This is usually a
problem in distinguishing between cluster and
data/index component attributes.
keywd
The keyword.

proper data set name. Run the command again.
412

Source: DFSMSdfp
IDC3191I
VSAM VOLUME DATA SET NAME OR

ITS GENERIC FORM NOT ALLOWED
Explanation: During processing of an access method

services command, a name was specified and had the
restricted virtual storage access method (VSAM) volume
data set (VVDS) prefix or one of its generic forms. The
VVDS prefix, allowed for the following:
v ENTRYNAME for the ALTER command.
v NEWNAME for the ALTER command.
v INDATASET for the REPRO command.
v MODEL for the DEFINE command.
The requested operation is not allowed for a VVDS.
command.
Application Programmer Response: Do not use the
restricted data set name prefix for the data sets. If a
data set has been created with the restricted prefix, an
alternate method must be found to complete the desired
operation.
and. the SYSOUT output for the job.
Source: DFSMSdfp
IDC3192I
LIBRARYNAME MUST REMAIN

SHELF WHILE LOCATION IS
SHELF
Explanation: An attempt to alter LIBRARYNAME from

SHELF was made while LOCATION was SHELF.
LOCATION and LIBRARYNAME must be consistent.
command.
System Programmer Response: Use the IDCAMS
ALTER command to change LOCATION from SHELF to
LIBRARY when altering LIBRARYNAME.
Source: DFSMSdfp
IDC3193I
dsname IS NOT A CANDIDATE FOR

ROLLIN
Explanation: An access method services ALTER

request specified a ROLLIN operation for a non-VSAM
data set that is not in the deferred or rolled off state.
dsname
The data set name. It may be in the active
state already, or it was not originally defined to
the generation data group (GDG) base.
Application Programmer Response: Check whether
the data set name is the intended candidate for a
ROLLIN operation.
Source: DFSMSdfp
IDC3197I
Explanation: An attempt was made by an

unauthorized caller to alter either the STORAGECLASS
or MANAGEMENTCLASS name for the data set being
altered. The caller of application management
subsystem (AMS) at the time of the ALTER must be
running in an authorized program facility (APF)
authorized state.
ALTER command.
Source: DFSMSdfp
IDC3198I

IDC3194I
SMS CONSTRUCT conname SPECIFIED

FOR NON-SMS MANAGED OBJECT

command requested to change the storage
management subsystem (SMS) construct that is either
the storage or management class name. However, the
specified object is not SMS managed, so the construct
cannot be changed.
INVALID AUTHORIZATION TO ALTER

STORAGECLASS OR
MANAGEMENTCLASS
SLOT VALUE CANNOT BE SPECIFIED

FOR A MANUAL LIBRARY
Explanation: NUMBERSLOTS and

NUMBEREMPTYSLOTS are not valid parameters for a
manual library.
command.
System Programmer Response: Either remove the
NUMBERSLOTS and/or NUMBEREMPTYSLOTS
parameters or specify LOGICALTYPE(AUTOMATED) on
the IDCAMS ALTER command.
Source: DFSMSdfp
conname
The construct name.

ALTER command.
IDC3199I
Application Programmer Response: Ensure that this

request is made against only SMS managed objects.
Source: DFSMSdfp
LIBRARYNAME OF SHELF IS NOT

ALLOWED WITH A LOCATION OF
LIBRARY
Explanation: The LIBRARYNAME of SHELF can only

be specified when LOCATION is SHELF.

command.
IDC3195I
System Programmer Response: Choose a

LIBRARYNAME other than SHELF or change the
LOCATION parameter to LIBRARY.
OBJECT IS NOT SMS MANAGED

command requested that a generation data set (GDS)
be rolled in, but the GDS is not managed by the storage
management subsystem (SMS).
command.
ROLLIN specification on the ALTER command.
Source: DFSMSdfp
IDC3200I
TOO MANY POSITIONAL

PARAMETERS AFTER prm
Source: DFSMSdfp
Explanation: A parameter list has too many positional

parameters specified.
prm
The parameter list.
System Action: Processing skips to the end of the
413
command. The system resumes interpretation with the

next command.

excess parameters. Run the command again.
IDC3203I

Explanation: The specified constant does not meet

the naming restrictions on its format. This is usually a
problem in specifying data set names.
Source: DFSMSdfp
IDC3201I
CONSTANT xxx EXCEEDS LENGTH

LIMIT
Explanation: A constant is longer than the maximum

allowed by the parameter definition or by the
implementation.
xxx
The constant that exceeded the maximum

length.

next command.
ITEM xxx DOES NOT ADHERE TO

RESTRICTIONS
xxx
The constant.

next command.
Application Programmer Response: Check the data
restrictions for the parameter and correct the item. Run
the command again.
Source: DFSMSdfp
DELIMITER xxx IS NOT PROPERLY
PRECEDED BY A CONSTANT OR KEY
WORD

definition of the parameter value in question. Specify an
allowable value. Run the command again.
IDC3205I

Explanation: A delimiter has been specified where a

subparameter list or data should have appeared. The
delimiter is being used improperly. Parentheses are
likely to be improper or a positional parameter may be
missing.
Source: DFSMSdfp
xxx
IDC3202I

next command.
ABOVE TEXT BYPASSED UNTIL NEXT

COMMAND. CONDITION CODE IS 12.
Explanation: Following the occurrence of an error in

the current command, the remainder of the command is
bypassed. An error message preceding this message in
the program listing will pinpoint the error.
System Action: The system performs no further
syntax or semantic checking on the command.
related error. Run the job again.
Source: DFSMSdfp
414
The delimiter.

usage. Run the command again.
Source: DFSMSdfp
IDC3207I
REMAINDER OF COMMAND INPUT

STREAM IGNORED
Explanation: An error has occurred that prohibits

further scanning of the input stream. There are
preceding error messages to explain the error. The
condition code (MAXCC) is always set to 16 when the
remainder of the input stream is ignored.
System Action: The system ignores the remainder of
the command input stream.
Source: DFSMSdfp
IDC3208I
LEFT PARENTHESIS MISSING

FOLLOWING KEY WORD keywd
Explanation: An opening parenthesis delimiting the

subparameter list or constants associated with the
keyword does not precede the keyword.
keywd
The keyword.

next command.
requirements of the parameter. Correct the usage. Run
the command again.
Source: DFSMSdfp
IDC3209I
RIGHT PARENTHESIS MISSING AFTER

xxx
Explanation: A right parenthesis is missing which

should delimit the end of one or more constants. Too
many items might be specified.
xxx
The item before which the parenthesis is

missing.

next command.
Source: DFSMSdfp
IDC3210I
INVALID PARENTHESES FOR

SPECIFYING REPEATED
SUBPARAMETER LIST
Explanation: Parentheses for delimiting repetitions of

a repeated subparameter list are missing or unmatched.
command. The system begins interpretation with the
next command.
Source: DFSMSdfp
IDC3211I
KEY WORD keywd IS IMPROPER
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.

next command.
usage of the keyword and the parentheses.
Source: DFSMSdfp
415
IDC3212I
INVALID LEFT PARENTHESIS AFTER

prm
Explanation: A left parenthesis appears to delimit a

positional parameter. However, the positional parameter
is not a constant or list of constants, so no parentheses
are allowed.
prm
The positional parameter.

next command.
usage. Run the job again.
Source: DFSMSdfp
IDC3213I
KEY WORD keywd APPEARS TOO

OFTEN
Explanation: A keyword has been coded more than

once in the same parameter list or subparameter list.
keywd
Source: DFSMSdfp
IDC3216I
ABOVE TEXT BYPASSED UNTIL NEXT

COMMAND
Explanation: Following the occurrence of an error in

the current command, the remainder of the command is
bypassed. An error message preceding this message
will pinpoint the error. The command was being
scanned for syntax checking purposes only when the
error was found.
System Action: The system performs no further
syntax or semantic checking on the command. The
system condition code is not affected.
Source: DFSMSdfp
The keyword.

next command.
redundant keyword. Run the command again.
Source: DFSMSdfp
IDC3214I
HEX OR BINARY CONSTANT

SPECIFIED IMPROPERLY
Explanation: A hexadecimal or binary constant is not

in its proper form.
next command.
416

IDC3217I
PASSWORD IMPROPER AFTER prm
Explanation: A password is found following a data

item that does not allow a password.
prm
The data item that does not allow a password.

next command.
improper password. Run the command again.
Source: DFSMSdfp
IDC3218I
TOO MANY REPEATED

SUBPARAMETER LISTS APPEAR
Explanation: More repeated subparameter lists are

coded than are allowed.
next command.
parameter description to see how many repetitions are
allowed. Correct the usage. Run the job again.

Source: DFSMSdfp
IDC3221I
CONSTANT xxx NOT WITHIN VALUE

RANGE

Explanation: A constant is of a value not within the

range of values allowed for this parameter.
Source: DFSMSdfp
xxx

next command.
IDC3219I
VERB NAME verb UNKNOWN
Explanation: The specified verb name is not known to

the system.
verb
The verb name.

next command.
improper verb name. Run the command again.
Source: DFSMSdfp
IDC3220I
IMPROPER NUMERIC DIGIT FOUND IN

prm
Explanation: An incorrect numeric digit has been

found. A decimal number may use only 0-9, a
hexadecimal number may use only 0-9 and A-F, and a
binary number may use only digits 0 and 1.
prm
The parameter in which the incorrect digit was

found.

next command.

The constant.

Source: DFSMSdfp
IDC3223I
TOO MANY CONSTANTS IN LIST

BEGINNING AT xxx
Explanation: Too many constants have been coded in

a list.
xxx
The constant that begins the list.

next command.
parameter definition to see how many constants appear
in the list. Correct the usage. Run the job again.
Source: DFSMSdfp
417
IDC3225I
REQUIRED (SUB)PARAMETER OF prm

IS MISSING
Explanation: The system issues this message for one

v A parameter required by the command is missing.

Source: DFSMSdfp
v For Cache-DASD the specified parameter is required.
IDC3241I
prm
Explanation: A DSNAME or DDNAME does not

adhere to naming restrictions.
The required parameter.

next command.
Application Programmer Response: Add the missing
Source: DFSMSdfp
IDC3226I
INCONSISTENT PARAMETERS
INVOLVING prm
Explanation: A user issued an IDCAMS command

that has conflicting or inconsistent parameters.
INVALID prm NAME-xxx
prm
xxx
The first sixty-four characters of the name, if

more than sixty-four characters were entered.
System Action: The system prompts the caller for a

valid name. See message IDC3249I.
Application Programmer Response: Enter a valid
name.
Source: DFSMSdfp
prm
The conflicting or inconsistent parameter.
IDC3242I
prm VALUE HAS INVALID LENGTH-xxx

command; interpretation begins at the next command.
Explanation: A constant is either too long or has a

null length.

error. Issue the command again.
Source: DFSMSdfp
IDC3240I
prm VALUE OF nnn OUT OF RANGE
prm
xxx
The first sixty-three characters of the constant,

if more than sixty-three were entered.

valid constant. See message IDC3249I.
Explanation: A number is either larger or smaller than

is allowed for the specified parameter.

constant.

prm
nnn
Represents the first ten digits of the number.

valid number. See message IDC3249I.
Application Programmer Response: Enter a number
within the allowable value range.
418
Source: DFSMSdfp
IDC3243I
prm LIST TOO LONG BEGINNING AT

xxx
Explanation: A list of nonnumeric constants or

subparameter lists has too many elements.
prm
xxx
The first sixty-three characters of the constant,

if more than sixty-three characters were
entered.
System Action: The system prompts the caller to

indicate whether the excess list elements may be
ignored. See message IDC3250I.
Application Programmer Response: Enter OK to
allow the excess elements to be ignored. Any other
response ends the command.
Source: DFSMSdfp
IDC3244I
prm1 (REPLY1) AND prm2 (REPLY 2)

ARE IN CONFLICT
Explanation: Two parameters have been coded that

conflict with each other.
prm1
prm2
The conflicting parameters.

indicate which of the two parameters should be kept.
See message IDC3246I.
Application Programmer Response: Enter 1 to
keep the first parameter. Enter 2 to keep the second
parameter.
Source: DFSMSdfp
IDC3246I
ENTER REPLY NUMBER OF

PARAMETER TO BE RETAINED
Explanation: This message follows message

IDC3244I and allows the operator to specify which
parameter to retain.
System Action: The system waits for the caller to
reply.
Application Programmer Response: Enter 1 to
keep the first parameter listed in the preceding
message. Enter 2 to keep the second parameter.
Source: DFSMSdfp
IDC3247I
ENTER SUBFIELD OF KEY WORD

keywd
Explanation: A keyword parameter is missing. It is

required by the command or by some other parameter
that has been coded.
keywd
The keyword.
System Action: The system waits for the caller to

reply. Either a constant or a subparameter set is
required.
Application Programmer Response: Enter the
requested subfield data.
Source: DFSMSdfp
IDC3248I
prm LIST TOO LONG BEGINNING AT

nnn
Explanation: A list of numbers contains too many

elements.
prm
nnn
The first ten digits of the number.

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

Source: DFSMSdfp
IDC3253I
MISSING SUBFIELD OF KEY WORD

keywd
Explanation: A keyword subparameter is missing, but

the system is not able to prompt the Time Sharing
Option/Extensions (TSO/E) user for it because a
PROFILE NOPROMPT command has been issued.
IDC3249I
REENTER
Explanation: This prompting message follows

messages that identify incorrect constants: IDC3240I,
IDC3241I, and IDC3242I.
System Action: The system requests the caller to
enter a valid constant.
constant.
Source: DFSMSdfp
IDC3250I
REPLY OK TO IGNORE EXCESS AND

CONTINUE
Explanation: This prompting message follows

message IDC3243I or IDC3248I which indicate too
many elements have been coded in a list.
indicate whether the excess elements can be ignored.
Application Programmer Response: If the response
is OK or OK, OK, OK the excess elements are
ignored. Any other response causes the command to
end.
Source: DFSMSdfp
keywd
The keyword.

command.
Operator Response: The TSO/E user should reenter
the command with the proper keyword.
Source: DFSMSdfp
IDC3300I
ERROR OPENING {dsname|ddname}
Explanation: An error was detected attempting to

open the data set name. See associated message for
explanation.
dsname
The data set name.
ddname
The ddname. Appears only when the data set
name is not available.
IDC3251I
FOR SUBFIELD REPETITION nnn
Explanation: This message prefaces any other error

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.

associated message.
Source: DFSMSdfp

indicated subparameter list repetition.
Source: DFSMSdfp
IDC3301I
Explanation: An error was detected while attempting

to close the data set. See the associated message in
the program listing for an explanation.
ERROR CLOSING dsname
420
dsname
The data set name.
associated message.
Source: DFSMSdfp
Detecting Module: IDCIO02, IDCIO05
IDC3304I
** JCL STATEMENT MISSING
Explanation: The DD statement named in a FILE,

INFILE, or OUTFILE parameter cannot be found. If the
job or Time Sharing Option/Extensions (TSO/E) session
contains a delete request that causes the system to
invoke dynamic deallocation, the DD statement for the
deleted data set is not accessible for the remainder of
the job or session.
command.
Application Programmer Response: Check ddnames
for incorrect spelling or check for missing DD
statements. Correct the error. Run the job again.

to access the data set. See the associated message in
the program listing for explanation.

Source: DFSMSdfp
dsname
IDC3302I
ACTION ERROR ON dsname
The data set name.

IDC3305I

associated message.
Explanation: The processor cannot open this

non-virtual storage access method (VSAM) data set for
output. Specifically, indexed sequential access method
(ISAM) data sets may not be output data sets.

Source: DFSMSdfp
IDC3303I
** CANNOT OPEN FOR UPDATE
Explanation: Only virtual storage access method

(VSAM) data sets may be opened for update mode.
System Action: The system does not open the data
set. The system ends the command.
Application Programmer Response: Change the DD
statement to specify a VSAM data set.
Source: DFSMSdfp
Detecting Module: IDCIO01, IDCIO03, IDCRS06
** CANNOT BE OPENED FOR OUTPUT

command.
keyword value to specify either a VSAM or SAM data
set.
Source: DFSMSdfp
IDC3306I
** PS PROCESSING INVALID FOR

KEYED DATA SET
Explanation: Physical sequential access is not

possible for the data set. Indexed sequential access
method (ISAM) data sets may not be processed other
than sequentially by key.
command.
JCL statement to specify a virtual storage access
421
method (VSAM) data set, or correct the usage of the

data set.


Source: DFSMSdfp
Source: DFSMSdfp
Explanation: The specified record was not written for

one of the following reasons:

IDC3307I
** DATA SET CANNOT BE OPENED

FOR KEYED PROCESSING
Explanation: Only indexed virtual storage access

method (VSAM) and indexed sequential access method
(ISAM) data sets can be opened for keyed processing.
command.
JCL statement to specify a keyed data set or correct the
usage of the data set in the command. Run the job
again.
Source: DFSMSdfp
IDC3308I
** DUPLICATE RECORD xxx
Explanation: The output data set of a REPRO

command already contains a record with the same key
or record number.
xxx
For an indexed data set, the first five bytes of

the duplicate key, in hexadecimal format.
For a relative record data set, the relative
record number (in decimal) of the duplicate
record.
System Action: The system does not write the record.

The system continues processing with the next record,
unless this is a copy catalog and a duplicate record is
encountered or there has been a total of four errors.
The system ends in either case. For example, if a
duplicate record is encountered while REPRO is
copying a catalog, the system ends processing.
422

IDC3309I
** RECORD xxx NOT WRITTEN.

LENGTH INVALID.
v The record length was greater than the LRECL of the

output data set (logical processing).
v The record length was less than the LRECL of the
output data set and output RECFM=FIXED, or output
is a relative record data set.
v The control-interval length to be written did not equal
the control interval size for the output data set.
v The record length was less than the minimum output
LRECL allowed (input LRECL + 4) when RECFM=F
and output is to a subsystem device.
xxx
The first five bytes of the record in

hexadecimal format.

until four such errors occur, in which case no more
records are written to the data set.
output data set with the correct LRECL or control
interval size.
Source: DFSMSdfp
IDC3310I
** KEY SUPPLIED IS LONGER THAN

KEY LENGTH OF DATA SET
Explanation: The key supplied for positioning was

longer than the key length of the data set. For example,
the key specified by FROMKEY is longer than the key
length of the data set.
command.
correct key on the command. Run the job again.

Source: DFSMSdfp
IDC3311I
** TYPE OF POSITIONING NOT

SUPPORTED
Explanation: Positioning is valid only for virtual

storage access method (VSAM) and indexed sequential
access method (ISAM) data sets.
command.
JCL statement defining a VSAM or ISAM data set or
remove the positioning parameter. Run the job again.
Source: DFSMSdfp
IDC3312I
** SYSTEM UNABLE TO OPEN
Explanation: DCBOFLG was not set after an OPEN

request.
Application Programmer Response: In the
description of the OPEN macro instruction, check for an
explanation of failure to set the DCBOFLG field in a
non-virtual storage access method (VSAM) data control
block (DCB) after an OPEN request.

Source: DFSMSdfp
IDC3314I
RECORD xxx OUT OF SEQUENCE
Explanation: The key of the record to be written is

less than or equal to the key of the last record written.
xxx
The first five bytes in hexadecimal format of

the key of the record that is out of sequence.
System Action: If the output data set is a virtual

storage access method (VSAM) data set, the system
ends processing of the command after four errors. If the
output data set is a NONVSAM data set, the system
continues processing the command. During an
EXPORT, the system ends processing of the command
after the first error.
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
using skip sequential processing. Run the job again and
the output data set will be opened for skip sequential
processing (because data already exists in the data set)
and records that were out of sequence will be written.

Source: DFSMSdfp
Source: DFSMSdfp
Explanation: Access method services cannot process

a non-virtual storage access method (VSAM) data set
with a logical record length greater than 32,760 bytes.
The DCB LRECL parameter was specified with a value
greater than 32,760. This value was obtained either
from the DD statement, the format-1 data set control
block (DSCB) or the data set label (for a tape data set)
for a non-VSAM data set, or it was generated by the
EXPORT or EXPORTRA command for a portable data
set. The logical record length for the EXPORT or
EXPORTRA command is based on the maximum record
size of the VSAM data set being exported plus system
overhead. The maximum VSAM record size that can be
handled by EXPORT is:

IDC3313I
synadaf-message
Explanation: An I/O error occurred for a non-virtual

storage access method (VSAM) data set. The
SYNADAF message is written.
explanation in the SYNADAF message. Correct the
error. Submit the job again.
Detecting Module: IDCIO01, IDCIO05

IDC3315I
** RECORD SIZE GREATER THAN

32760 NOT SUPPORTED
423
v 32,752 for relative record data sets

v 32,756 for all other types of VSAM data sets
The maximum record size that can be handled by
EXPORTRA is:
v 32,748 for relative record data sets
v 32,752 for all other types of VSAM data sets
command.
following:
v Change the DD statement to specify a DCB LRECL
parameter of less than 32,760 bytes or to refer to a
non-VSAM data set whose logical record length (as
specified in its format-1 DSCB or data set label) is
less than 32,760 bytes
v Change the VSAM maximum logical record size to
conform to the restrictions given above. In order to
use the second alternative, redefine and reload the
VSAM data set.
catalog.
job.
Source: DFSMSdfp
IDC3316I
** DATA SET IS NOT VSAM CATALOG
Explanation: A request is for a virtual storage access

method (VSAM) catalog to be opened and the data set
is not a VSAM catalog.
IDC3317I
** PERMANENT I/O ERROR
Explanation: An I/O error was detected performing an

I/O operation on the data set named in the preceding
message.
command.
Application Programmer Response: Check the job
control statement to ensure that the data set was
correctly defined. If it was correctly defined, a hardware
I/O error was encountered. The data set must be
created in a new location.
Source: DFSMSdfp
IDC3318I
** INVALID DATA SET SPECIFICATION
Explanation: A STOW was issued against the data

set, but the specified data control block (DCB) is not
open or is opened incorrectly.
Source: DFSMSdfp
Detecting Module: IDCIO01, IDCIO02, IDCIO03
IDC3321I
** OPEN/CLOSE/EOV ABEND EXIT

TAKEN

catalog keyword to specify a user catalog. Run the job
again.
Explanation: The OPEN/CLOSE/EOV SVC routines

detected an error, and an ABEND message has been
written to the system output data set.

Source: DFSMSdfp

write-to-programmer (WTP) message written by the
OPEN/CLOSE routine. Correct the error. Submit the job
again.
Source: DFSMSdfp
424
Source: DFSMSdfp
IDC3322I
** DATA SET ORGANIZATION IS NOT

VSAM
Explanation: A request for an existing data set

indicated that the data set was virtual storage access
method (VSAM). The data set was in fact not VSAM.
set name or type. Run the job again.
IDC3327I
Explanation: During a REPRO operation an attempt

has been made to add a record to the output base
cluster. However, a duplicate record in the upgrade set
has been encountered when upgrading an alternate
index with the UNIQUEKEY attribute over the output
data set.
xxx

** INCORRECT BLOCKSIZE SPECIFIED
FOR IMPORTRA
Explanation: The data set cannot be opened due to

an incorrect block size in the INFILE parameter.
IMPORTRA command.
block size in the INFILE parameter to that used in the
EXPORTRA command. Run the job again.
Source: DFSMSdfp
IDC3326I
** REPLACE INVALID FOR OUTPUT

THROUGH A PATH
Explanation: The caller has specified the REPLACE

parameter in a REPRO command when the output data
set is a path. REPLACE processing is not allowed for
an output path.
If the base cluster is a key-sequenced data set,

the first five bytes of the prime key expressed
in hexadecimal.
If the base cluster is an entry-sequenced data
set, the first five bytes of the record expressed
in hexadecimal.
Source: DFSMSdfp
IDC3325I
** DUPLICATE RECORD IN UPGRADE

SET - BASE RECORD xxx
System Action: The system does not write the record

into the base cluster. The system continues processing
until four action errors occur, at which point the system
ends processing.
UNIQUEKEY attribute was correctly specified, the base
cluster record being added is in error and must be
corrected. If the UNIQUEKEY attribute was incorrectly
specified, it may be changed to NONUNIQUEKEY using
the ALTER command. Run the job again using just
those records that were in error as input.
Source: DFSMSdfp
IDC3330I
** xxx NOT FOUND

command.
Explanation: The indicated entry does not exist in the

directory.
Application Programmer Response: If the input does

not contain any records duplicating prime keys (and
alternate keys of any upgrade set alternate index having
the UNIQUEKEY attribute) in the output, the caller may
still run REPRO by simply removing the REPLACE
parameter.

xxx
The entry not found.

entry name. Run the job again.
425

If it is not empty, delete whatever is defined in it, then

delete it, and redefine it.
Source: DFSMSdfp
Enter the REPRO command again.

IDC3331I
** mem ALREADY EXISTS
Explanation: A member with the new member name

already exists in the PDS directory.
Source: DFSMSdfp
Detecting Module: IDCIO02, IDCIO03, IDCSA02
mem
The member.

Application Programmer Response: Specify a
different new name. Run the job again.
Source: DFSMSdfp
IDC3332I
** INSUFFICIENT MAIN STORAGE
Explanation: There is not sufficient main storage

allocated.
System Action: The system ends the job.
Application Programmer Response: Specify a larger
region size. Run the job again.
IDC3334I
** INVALID CI NUMBER
Explanation: The REPRO command to copy a source

catalog into a target catalog failed because there was
an incorrect control-interval number in an entry in the
source catalog.
System Action: The system does not carry out the
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
number.
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
catalog record that contains the incorrect control-interval
number and to determine what the control-interval
number should be. Contact the IBM Support Center.
Source: DFSMSdfp
Source: DFSMSdfp
IDC3335I

to use a Programmed Cryptographic Facility service to
encipher or decipher data. See the accompanying
IDC3333I
** CATALOG IS NOT EMPTY
Explanation: The REPRO command to copy a source

catalog into a target catalog failed because the target
catalog was not empty or was empty but had been
used. That is, it has entries defined in it, then deleted
from it.
System Action: The system does not carry out the
copy operation. The system ends the command.
correct target catalog has been specified. If it has, use
the LISTCAT command to determine whether the
catalog is empty. If it is empty, delete it and redefine it.
426
{ENCIPHER|DECIPHER} ERROR

problem described by the accompanying message.
Source: DFSMSdfp

IDC3336I
** text RETURN CODE IS return-code

CIPHER
EMK
GENKEY
RETKEY
The indicated Programmed Cryptographic Facility (PCF)
service returned a nonzero return code. PCF and
cryptographic unit support program (CUSP) macros will
receive identical error return codes if they run on
integrated cryptographic service facility (ICSF)/MVS or
on PCF/CUSP, with one exception. If a key is installed
in the cryptographic key data set (CKDS) with the
correct label but an incorrect key type, an attempt to
use that key by RETKEY or GENKEY will result in a
return code of 8 from PCF/CUSP, indicating that the key
was not of the correct type. ICSF will issue a return
code of 12, indicating the key could not be found.
Installations must ensure that PCF/CUSP LOCAL or
CROSS 1 keys are installed on the ICSF CKDS as
EXPORTER keys, and that REMOTE and CROSS 2
keys are installed as IMPORTER keys.
text
The text of the message.
return-code

For CIPHER/EMK:
Code
Explanation
PCF was not initialized.
12
The system encountered an

error that forced an abnormal
end.
For GENKEY/RETKEY:
Code
Explanation
PCF was not active.
The key type was incorrect.
12
The key name was not found

in the CKDS.
16
An installation exit caused

the request to fail.

Source: DFSMSdfp
IDC3337I
TARGET DATA SET IS NOT EMPTY

FOR {ENCIPHER|DECIPHER}
Explanation: The target virtual storage access method

(VSAM) entry-sequenced data set (ESDS) for the
ENCIPHER or DECIPHER operation was not empty.
statement for the target data set pointed to by the
OUTFILE parameter or the data set name specified by
the OUTDATASET parameter to specify an empty
VSAM ESDS, or, if the VSAM ESDS was defined with
the REUSE option, specify REUSE in the command.
Source: DFSMSdfp
IDC3338I
INVALID SOURCE DATA SET FOR

DECIPHER
Explanation: The source data set was not enciphered

by a REPRO ENCIPHER command, and therefore
cannot be deciphered.
statement pointed to by the INFILE parameter or the
data set name specified by the INDATASET parameter
to specify a data set that was produced by a REPRO
ENCIPHER operation.
24
An error occurred in the

installation exit routine.
28
The authorization check

failed.

32
The key has incorrect parity.
Source: DFSMSdfp
36
The system encountered an

error that forced an abnormal
end.
427
IDC3340I
SYSTEMKEYNAME text

ENCIPHERED SYSTEMDATAKEY
NOT FOUND IN SOURCE DATA SET
The caller did not specify the key name or enciphered
data encrypting key to be used to decipher the data.
REPRO command processing tried to obtain the needed
information from the header of the source data set, but
the information was not stored in the header when the
data set was enciphered by the REPRO ENCIPHER
command.

Source: DFSMSdfp
IDC3350I
synad[SYNAD]message[from VSAM]
Explanation: An I/O error occurred for a virtual

storage access method (VSAM) data set. The message
text, format, and explanation of VSAM I/O errors are
provided in OS/390 DFSMS Macro Instructions for Data
Sets.
synad
The synad data.

needed key name or enciphered data encrypting key in
the command using the SYSTEMKEYNAME or
SYSTEMDATAKEY parameter.
message
The message text.


explanation of the error. Correct the error. Submit the
job again.
Source: DFSMSdfp
IDC3341I
DECIPHER KEY IS INVALID
Explanation: One of the keys supplied by the caller to

decipher the data is not the same as the key that was
used to encipher the data. If the SYSTEMKEY
parameter was specified, then one of the following is
incorrect:
v The secondary file key name specified by the
SYSTEMKEYNAME parameter.
v The secondary file key name contained in the header.
v The enciphered data encrypting key specified by the
SYSTEMDATAKEY parameter.
v The enciphered data encrypting key contained in the
header.
If the DATAKEYVALUE parameter was specified, then
the specified value (plain text data encrypting key) is
incorrect. If the DATAKEYFILE parameter was specified,
then the first record in the data encrypting key data set
is incorrect.
System Action: If possible, the system continues

processing.

Source: DFSMSdfp
IDC3351I
** VSAM {OPEN|CLOSE|I/O} RETURN

CODE IS return-code
{RPLFDBWD=nnnnnnnn}
Explanation: An error was encountered during virtual

storage access method (VSAM) open, close, or action
request processing, as indicated in the text of the
message.
nnnnnnnn
The meaning of RPLFDBWD, the RPL
Feedback Word. For detailed information on
the RPL Feedback Word, see OS/390 DFSMS
Macro Instructions for Data Sets.
rc
For a CLOSE Error

correct key. Run the job again.
Code
Explanation
The data set indicated by the

access-method control block is
already closed.
124
A request was cancelled from a use

JRNAD Exit.

428
128
Index search horizontal chain pointer

loop encountered.
129
TCLOSE was issued against a media

managers structure.
132
An uncorrectable I/O error occurred

while VSAM was reading the job file
control block (JFCB).
136
Not enough virtual storage was

available in the programs address
space for a work area for CLOSE.
144

while VSAM was reading or writing a
catalog record.
145
An uncorrectable error occurred in the

VSAM volume data set (VVDS).
148
An unidentified error occurred while

VSAM was searching the catalog.
180
A VSAM catalog specified in the JCL

either does not exist or is not open,
and no record for the data set to be
closed was found in any other catalog.
184

while VSAM was completing
outstanding I/O requests.
236
A permanent destaging error occurred

in the Mass Storage System
(RELINQUISH). With temporary
CLOSE, destaging error or a staging
error (ACQUIRE) occurred.
246
The compression management

services (CMS) close function failed.
For an OPEN Error

0
When register 15 contains 0, no error.

When register 15 contains 8, one of
the following conditions exists:
1. VSAM is processing the
access-method control block for
some other request.
2. The access-method control block
is already open.
3. DDNAME was not specified
correctly in the access-method
control block.
4. The access-method control block
address is incorrect.

access-method control block is
already open.
76
Attention message: The interrupt

recognition flag (IRF) was detected for
a data set opened for input
processing.
88
A previous extend error has occurred

during EOV processing of the data
set.
92
Attention message: Inconsistent use

of CBUF processing. Sharing options
differ between index and data
components.
96
Attention message: an unusable data

set was opened for input.
100
Attention message: OPEN

encountered an empty alternate index
that is part of an upgrade set.
104
Attention message: the time stamp of

the volume on which a data set is
stored doesnt match the system time
stamp in the volume record in the
catalog; this indicates that extent
information in the catalog record may
not agree with the extents indicated in
the volumes VTOC.
108
Attention message: the time stamps of

a data component and an index
component do not match; this
indicates that either the data or the
index has been updated separately
from the other. Check for possible
duplicate VVRs.
110
Attention message: JRNAD exit was

not specified on the first ACB opened
for the data set. Processing continues
without journaling.
116
Attention message: the data set was

not properly closed or was not
opened. If the data set was not
properly closed, then data may be lost
if processing continues. Use the
access method services VERIFY
command to attempt to close the data
set properly. See DFSMS/MVS
Access Method Services for ICF for a
description of the VERIFY command.
In a cross-system shared DASD
environment, a return code of 116 can
have two meanings:
v The data set was not properly
closed.
v The data set is opened for output
on another processor.
Note: If you use the VERIFY
command, this message can
appear again when VERIFY
processing opens the data set.
If VERIFY processing then
successfully closes the data
set, VERIFY processing issues
condition code 0 at the end of
429
Improved control interval processing

(ICIP) was specified for an extended
format data set will also result in this
error.
its processing. In addition, an

empty cluster cannot be
verified.
118
Attention message: The data set was

not properly closed but OPENs
implicit verify was successfully
processed.
128
DD statement for this access method

control block is missing or incorrect.
132
One of the following errors occurred:

v Not enough storage was available
for work areas.
For more information on this return

code, see OS/390 DFSMSdfp
Diagnosis Reference.
164

while VSAM was reading the volume
label.
168
The data set is not available for the

type of processing specified, or an
attempt was made to open a reusable
data set with the reset option while
another user had the data set open.
176
An error occurred while VSAM was

attempting to fix a page of virtual
storage in central storage.
180
A VSAM catalog specified in JCL

either does not exist or is not open,
and no record for the data set to be
opened was found in any other
catalog.
184

while VSAM was completing an I/O
request.
188

access-method control block is not of
the type that may be specified by an
access-method control block.
190
An incorrect high-allocated RBA was

found in the catalog entry for this data
set. The catalog entry is bad and will
have to be restored.
192
An unusable data set was opened for

output.
193
The interrupt recognition flag (IRF)

was detected for a data set opened
for output processing.
194
Direct access of a compressed data

component is not allowed.
195
An attempt was made to open a

VSAM Extended Addressable data set
on a release other than DFSMS/MVS
1.30.
196
Access to data was requested through

an empty path.
200
Volume is unusable.
204
The ACB MACRF specification is GSR

and caller is not operating in
supervisor protect key 0 to 7, or the
ACB MACRF specification is CBIC
(control blocks in common) and caller
v The required volume could not be

mounted.
v An uncorrectable I/O error occurred
while VSAM was reading the job
file control block (JFCB).
v The format-1 DSCB or the catalog
cluster record is incorrect.
v The user-supplied catalog name
does not match the name on the
entry.
v The user is not authorized to open
the catalog as a catalog.
136
140
The catalog indicates this data set has

an incorrect physical record size.
144

while VSAM was reading or writing a
catalog record.
145
An uncorrectable error occurred in the

VSAM volume data set (VVDS).
148
No record for the data set to be

opened was found in the available
catalog(s), or an unidentified error
occurred while VSAM was searching
the catalog.
152
160
430
Not enough virtual-storage space is

available in the programs address
space for work areas, control blocks,
or buffers.
Security verification failed; the

password specified in the
access-method control block for a
specified level of access doesnt
match the password in the catalog for
that level of access; user is not
authorized to access this file.
The operands specified in the ACB or
GENCB macro are inconsistent with
each other or with the information in
the catalog record. This error can also
occur when the VSAM cluster being
opened is empty.
is not operating in supervisor state

with protect key 0 to 7.
205
The ACBCATX option or VSAM

Volume data set OPEN was specified
and the calling program was not
authorized.
12
You attempted to store a record out of

ascending key sequence in
skip-sequential mode; record had a
duplicate key; for skip-sequential
processing, your GET, PUT, and
POINT requests are not referencing
records in ascending sequence; or, for
skip-sequential retrieval, the key
requested is lower than the previous
key requested. For shared resources,
buffer pool is full.
16
Record not found.
20
Record already held in exclusive

control by another requester.
24
Record resides on a volume that

cannot be mounted.
28
Data set cannot be extended because

VSAM cannot allocate additional
direct-access storage space. Either
there is not enough space left to make
the secondary allocation request, you
attempted to increase the size of a
data set while processing with
SHROPT=4 and DISP=SHR, or the
index CI is not large enough to hold
the entire CA. This error could also be
due to a data set trying to extend
beyond 4GB on a system that does
not support extended addressability.
32
An RBA specified that does not give

the address of any data record in the
data set.
36
Key ranges were specified for the

data set when it was defined, but no
range was specified that includes the
record to be inserted.
40
Insufficient virtual storage in the users

address space to complete the
request.
44
Work area not large enough for the

data record (GET with OPTCD=MVE).
56
End of data set encountered (during

sequential retrieval), or the search
argument is greater than the high key
of the data set. Either no EODAD
routine is provided, or one is provided
and it returned to VSAM and the
processing program issued another
GET.
At the beginning of CI or CA split for

backup while open (BWO), an error
was detected in catalog update
processing.
64
As many requests are active as the

number specified in the STRNO
parameter of the ACB macro;
therefore, another request cannot be
activated.
You attempted to store a record with a
68
An attempt was made to use a type of
208

and caller is using a VS1 system.
212

or LSR and the data set requires
create processing.
216

or LSR and the key length of the data
set exceeds the maximum key length
specified in BLDVRP.
220

or LSR and the data sets control
interval size exceeds the size of the
largest buffer specified in BLDVRP.
224
Improved control interval processing is

specified and the data set requires
create mode processing.
228

or LSR and the VSAM shared
resource table (VSRT) does not exist
(no buffer pool is available).
232
Reset (ACB MACRF=RST) was

specified for a nonreusable data set
and the data set is not empty.
236
Indicates a stage or destage error.
240
Format-4 DSCB and catalog time

stamp verification failed during volume
mount processing for output
processing.
244
The volume containing the catalog

recovery area was not mounted and
verified for output processing.
245
The ESCON channel is required to

process an extended format data set.
246
The compression management

services (CMS) open function failed.
For a Logical I/O Error

4
duplicate key, or there is a duplicate

record for an alternate index with the
unique key option.
431
72
76
processing (output or control-interval)

that was not specified when the data
set was opened.
TRANSID was greater than 31 or

the shared resource option was
not specified.
You made a keyed request for access

to an entry-sequenced data set, or
you issued a GETIX or PUTIX to an
entry-sequenced or relative record
data set.
6. ICI processing was specified, but

a request other than a GET or a
PUT was issued.
You issued an addressed or

control-interval PUT to add to a
key-sequenced data set, or you
issued a control-interval PUT to a
relative record data set.
80
You issued an ERASE request for

access to an entry-sequenced data
set, or you issued an ERASE request
for access to an entry-sequenced data
set via a path.
84
OPTCD=LOC specified for a PUT

request or in a request parameter list
in a chain of request parameter lists.
88
You issued a sequential GET request

without having caused VSAM to be
positioned for it, or you changed from
addressed access to keyed access
without causing VSAM to be
positioned for keyed-sequential
retrieval; there was no positioning
established for sequential PUT insert
for a relative record data set, or you
attempted an incorrect switch between
forward and backward processing.
92
You issued a PUT for update or an

ERASE without a previous GET for
update or a PUTIX without a previous
GETIX.
96
An attempt was made to change the

prime key or key of reference while
making an update.
100
An attempt was made to change the

length of a record while making an
addressed update.
104
The RPL options are either incorrect

or conflicting in one of the following
ways:
1. SKP was specified and either KEY
was not specified or BWD was
specified.
2. BWD was specified for CNV
processing.
7. MRKBFR MARK=OUT or
MARK=RLS was issued, but the
RPL did not have a data buffer
associated with it.
8. The RPL specified WAITX, but the
ACB did not specify LSR or GSR.
108
The RECLEN specified was larger

than the maximum allowed, equal to
0, or smaller than the sum of the
length and the displacement of the
key field of the base cluster or related
alternate index (AIX). The RECLEN
was not equal to the slot size
specified for a relative record data set.
112
KEYLEN specified was too large or

equal to 0.
116
During initial data set loading (that is,

when records are being stored in the
data set the first time its opened),
GET, POINT, ERASE, direct PUT, and
skip-sequential PUT with
OPTCD=UPD are not allowed. During
initial data set loading, VERIFY is not
allowed except for an
entry-sequenced data set (ESDS)
defined with the RECOVERY option.
For initial loading of a relative record
data set, the request was other than a
PUT insert.
120
The request was operating under an

incorrect TCB. For example, an
end-of-volume call or a GETMAIN
would have been necessary to
complete the request, but the request
was issued from a job step other than
the one that opened the data set. The
request can be resubmitted from the
correct task if the new request
reestablishes positioning.
124
A request was cancelled for a user

JRNAD exit.
128
A loop exists in the index horizontal

pointer chain during index search
processing.
132
An attempt was made in locate mode

to retrieve a spanned record.
136
You attempted an addressed GET of

a spanned record in a key-sequenced
data set.
3. FWD and LRD were specified.

4. Neither ADR, CNV, nor KEY was
specified in the RPL.
5. WRTBFR, MRKBFR, or SCHBER
was issued was issued, but either
432
140
Inconsistent spanned record.
144
Incorrect pointer (no associated base

record) in an alternate index.
148
The maximum number of pointers in

the alternate index has been
exceeded.
152
Not enough buffers are available to

process your request (shared
resources only).
156
An addressed GET UPD request

failed because the control interval flag
was on, or an incorrect control interval
was detected during keyed
processing. In the latter case, the
control interval is incorrect for one of
the following reasons:
SVC 109 by ACQRANGE, CNVTAD,

and MNTACQ macros (return code =
36).
217
Incorrect AMBL detected by SVC 109

called by ACQRANGE, CNVTAD, and
MNTACQ macros (return code = 40).
218
Unrecognizable return code from SVC

109.
224
MRKBFR OUT was issued for a buffer

with incorrect contents.
228
Caller in cross-memory mode is not in

supervisor state or RPL of caller in
SRB or cross-memory mode does not
specify SYN processing.
229
The record length changed during

decompression processing of a
compressed data set.
232
UPAD error. ECB was not posted by

user in cross-memory mode.
236
Validity check error for

SHAREOPTIONS 3 or 4.
240
For shared resources, one of the

following is being performed:
1. A key is not greater than the

previous key.
2. A key is not in the current control
interval.
3. A spanned record RDF is present.
4. A free space pointer is incorrect.
5. The number of records does not
match a group RDF record count.
160
6. A record definition field is

incorrect.
1. An attempt is being made to

obtain a buffer in exclusive control.
7. An index CI format is incorrect.
2. A buffer is being invalidated.
One or more candidates were found

with a modified buffer marked to be
written. The buffer was left in write
status with valid contents. With this
condition, it is possible to have other
buffers invalidated or found under
exclusive control.
192
Incorrect relative record number.
196
You issued an addressed request to a

relative record data set.
200
You attempted addressed or

control-interval access through a path.
204
PUT insert requests are not allowed in

backward mode.
208
The user has issued an ENDREQ

macro instruction against an RPL that
has an outstanding WAIT against the
ECB associated with the RPL. This
can occur when an ENDREQ is
issued from a STAE or ESTAE routine
against an RPL that was started
before the ABEND. No ENDREQ
processing has been done.
212
Unable to split index; increase index

CI size.
216
Incorrect parameter list passed to
3. The buffer use chain is changing.

For more detailed feedback, reissue
the request.
244
Register 14 stack size is not large

enough.
245
A severe error was detected by the

compression management services
(CMS) during compression
processing.
246
A severe error was detected by the

compression management services
(CMS) during decompression
processing.
248
Register return offset went negative.
250
A valid dictionary token does not exist

for the compressed data set. The data
record cannot be decompressed.
252
Record mode processing is not

allowed for a linear data set.
253
VERIFY is not a valid function for a

linear data set.
254
I/O activity on the data set was not

quiesced before the data set was
closed.
433
Note: See OS/390 DFSMS Macro Instructions for Data

Sets. for additional information on the return
codes.
System Action: The action depends on the function
being processed. See the message in the program
listing following this message.
cause of the error.
Source: DFSMSdfp
Detecting Module: IDCIO01, IDCIO02, IDCIO03
IDC3380I
FILE ddname MUST SPECIFY A

DEMOUNTABLE UNIT
Explanation: The unit for the file defined by the DD

statement with the name indicated was not assigned for
exclusive control. Volumes cannot be mounted or
demounted on this unit. Either the volume allocated by
the DD statement was already mounted when the
statement was processed, or the correct parameters
were not specified on the DD statement.
ddname
The DD name.
again after demounting the volume. This causes the
device to be assigned for exclusive control while the job
or step is running.
Source: DFSMSdfp
Detecting Module: IDCIO01, IDCIO02, IDCIO03,
IDCRS06
IDC3383I
FILE ddname MUST SPECIFY A

VIRTUAL UNIT
ddname
The DD name.
UNIT parameter. Run the command again.
Source: DFSMSdfp
IDC3384I
FILE ddname SPECIFIED AN INVALID

UNIT FOR FUNCTION REQUESTED
Explanation: The direct access storage unit, specified

on the DD statement through the FILE parameter, is not
supported by this function. The unit is not a direct
access device or, if DASD, is not a 3330 or 3330V.
ddname
The DD name.
UNIT parameter. Run the command again.
Source: DFSMSdfp
IDC3385I
VOLUME ser IS PERMANENTLY

RESIDENT OR RESERVED
Explanation: The volume is marked permanently

resident or reserved in the unit control block (UCB).
Therefore, the volume cannot be demounted. The
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.
Explanation: The DD statement specified through the

FILE parameter does not specify a virtual unit but a
virtual unit is required.
ser

DD statement named in the FILE parameter specifies
434
the correct volume serial. You might have mistakenly

specified the volume serial of a permanently resident or
reserved volume. If the DD statement does have the
correct volume serial, then you cannot run the
command while that volume is permanently resident or
reserved.

parameters of the MODIFYC command for errors. If any
errors are found, correct the input. Run the command
again. If errors cannot be found, one of the following
commands can be run to help determine where the
cartridge is and what the cartridge status is.

The command is:
Source: DFSMSdfp
IDC3392I
NO UNIT AVAILABLE FOR VOLUME

volser
Explanation: The TEST enqueue indicates that the

volume is allocated to a job step, but no unit is available
for mounting the volume. All units that have open virtual
storage access method (VSAM) catalogs are
non-shareable and cannot be used.
v LISTMSF command if the cartridge is a scratch

cartridge.
v LISTMSVI command if the cartridge is part of a mass
storage volume.
v AUDITMSS command if the cartridge to be modified
was requested by using the CELL parameter.
If the cartridge still cannot be located, see Problem
Determination.
Source: DFSMSdfp
Detecting Module: IDCMC01
volser

Application Programmer Response: Either change
the disposition of your data set to share or run the job
again when a non-shareable unit is available.
Source: DFSMSdfp
IDC3435I
CARTRIDGE NOT EJECTED, EXIT

STATION FULL
Explanation: A request was made to eject a cartridge

from the cartridge access station, but the cartridge
access station was already full.
System Action: The system ends the MODIFYC
command. The cartridge remains in its original location
in the cartridge store.
Application Programmer Response: Have the
operator empty the cartridge access station and run the
command again.
Source: DFSMSdfp
IDC3436I
CARTRIDGE TO BE MODIFIED COULD

NOT BE LOCATED
Explanation: The request to modify a cartridge failed

because the cartridge could not be found.
command.
IDC3437I
ACCESSED CELL IS EMPTY OR THE

DESTINATION CELL IS FULL
Explanation: The attempt to modify a cartridge failed

because the home cell where the cartridge was
supposed to be was empty, or an attempt to reassign a
cartridge to a new location failed because the new
location is already occupied.
command.
parameters of the MODIFYC command for errors. If
errors are found, correct them and submit the command
again. If errors cannot be found, do the following:
1. Run the MODIFYC command again unchanged
because the cartridge that was requested might
have been at a data recording device when the
initial request was processed. If the same error
occurs, one of the following commands can be run
to help determine the nature of the error. If the
home cell location is not known, the commands
LISTMSF for scratch cartridges or LISTMSVI for
cartridges that are part of volumes, can be run to
determine the home cell location. The AUDITMSS
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
the MODIFYC command again.
3. If the above actions do not correct the problem, see
the Problem Determination.
435
Source: DFSMSdfp

IDC3503I
IDC3438I
ACCESSED OR DESTINATION CELL

ADDRESS IS INVALID FOR THIS MSF
Explanation: The accessed or destination cell address

is specified incorrectly. Either the Mass Storage Facility
is incorrectly identified or the cell address parameter did
not follow the rules of specification for each model of a
Mass Storage Facility.
System Action: The MODIFYC commands ends. The
return code is 12.
input parameters of the MODIFYC command. Ensure
that the parameters are consistent with the Mass
Storage System requirements for each model of a Mass
Storage Facility. Correct any errors in the input
parameters and rerun the command.
Source: DFSMSdfp
IDC3500I
A VALID VSAM DEFINE STRUCTURE

WAS NOT PROVIDED
Explanation: The object parameter list was not

specified properly. The access method services
reader/interpreter should have detected this error.
System Action: The command is ended.
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
the IBM Support Center. Provide the JCL and the
Source: DFSMSdfp
FILE SEQUENCE LIST IS

INCONSISTENT WITH VOLUME LIST
Explanation: The number of elements in the

FILESEQUENCENUMBERS parameter list is not equal
to the volumes in the VOLUMES parameter list.
error. Check the elements in both lists, and make
corrections where needed.
Source: DFSMSdfp
IDC3504I
THE RANGE LIST CANNOT BE

CONSTRUCTED
Explanation: In the construction of the RANGE LIST,

the allotted area was not sufficient.
Application Programmer Response: Possible system
error. Rerun the job with the PARM option--PARM TEST
(FULL((DEFN.1.1))); contact your system programmer.
Source: DFSMSdfp

IDC3505I
IDC3501I
MODEL ENTYPE IS NOT CONSISTENT

WITH THE OBJECT BEING DEFINED
Explanation: The object being used to model a VSAM

data set or user catalog differs from that being defined.
error. Ensure that the model object type is identical to
that being defined.
Source: DFSMSdfp
436
SPACE ALLOCATION
Explanation: The space parameters TRACKS,

CYLINDER, or RECORDS do not appear on the
appropriate object parameter list.
error. See the DEFINE command and space
specifications in DFSMS/MVS Access Method Services
for ICF
Source: DFSMSdfp
IDC3506I
A REQUIRED VOLUME OR DEVT LIST

HAS BEEN OMITTED
Explanation: The VOLUMES parameter does not

appear in the command when required.
error. A volume list must be available to DATA and
INDEX objects (the INDEX object appears only if the
data set is KSDS). The availability may be through
explicit specification of volumes, via propagation of
volumes from the Cluster parameter list or from the
model object.
Source: DFSMSdfp
IDC3514I
KEYRANGES ARE INVALID
Explanation: The KEYRANGES parameter (DEFINE

or IMPORT command) specified incorrect key values for
the low or high key values:
v The high key value is lower than the low key value in
a low-key high-key pair.
v Two or more low-key high-key pairs overlap, or are
identical.
KEYRANGES specifications.
Source: DFSMSdfp
IDCMP01
IDC3515I
AVERAGE RECORD SIZE EXCEEDS

MAXIMUM RECORD SIZE
Explanation: The first size value of the RECORDSIZE

parameter is greater than the second.
System Action: Processing for the command is

ended.
IDC3507I
Application Programmer Response: Correct either

the average or the maximum size value.
THE RECORDSIZE PARAMETER IS

REQUIRED BUT NOT SPECIFIED
Explanation: The RECORDSIZE parameter must be

specified when defining VSAM space and the allocation
unit is records.
error. Specify RECORDSIZE and resubmit the job.
Source: DFSMSdfp
IDC3516I
KEYS PARAMETER REQUIRED FOR

KEY SEQUENCED DATA SET
Explanation: The definition of a KSDS requires the

specification of the key position and length, via the
KEYS parameter.
ended.
Source: DFSMSdfp

DEFINE command.
Source: DFSMSdfp
IDC3513I
DYNAMIC ALLOCATION FAILED OR

FILE NOT CODED WHEN REQUIRED
Explanation: FILE was specified in a utility command

and the ddname was not found.
Application Programmer Response: See if the
ddname on the FILE parameter is the same as the
corresponding dd statement ddname.
Source: DFSMSdfp
IDC3517I
AVG AND MAX RECORDSIZE NOT

EQUAL FOR RELATIVE RECORD DATA
SET
Explanation: The RECORDSIZE parameter specified

average and maximum record sizes that were not equal.
Relative record data sets must have fixed-length
records.
437
Source: DFSMSdfp
IDC3522I

IDC3518I
REUSE PARAMETER INVALID WITH

UNIQUE OR KEYRANGES
Explanation: The REUSE attribute may not be

specified for a cluster or an alternate index together with
the UNIQUE or KEYRANGES parameter, either
explicitly or implicitly thru use of the MODEL parameter.
command by deleting either the REUSE or the UNIQUE
and/or KEYRANGES parameter; then rerun the job.
Source: DFSMSdfp
IDC3519I
REUSE ATTRIBUTE CONFLICT

BETWEEN DATA AND INDEX
Explanation: The REUSE attribute was not the same

for the data and index objects. Examples:
1. NOREUSE is specified at the cluster level and
REUSE is specified at the data level with nothing
specified at index level resulting in index defaulting
to NOREUSE.
2. Modeling at the cluster level and explicitly overriding
model attributes at data or index level but not both.
object ensuring that data and index REUSE attributes
are in harmony.
Source: DFSMSdfp
IDC3521I
SPANNED ATTRIBUTE INVALID FOR A

RELATIVE RECORD DATA SET
Explanation: SPANNED and NUMBERED were

specified together, either explicitly or through use of the
MODEL parameter. Records of an RRDS may not span
control intervals.
SPANNED parameter or the data set type specification.
Source: DFSMSdfp
438
SPANNED ATTRIBUTE REQUIRED FOR

RECORDSIZE GREATER THAN 32,761
Explanation: The RECORDSIZE parameter specifies

a maximum size greater than 32,761, but SPANNED is
not specified.
RECORDSIZE parameter, or specify the SPANNED
parameter.
Source: DFSMSdfp
IDC3523I
GENERATION DATA GROUP NAME

EXCEEDS 35 CHARACTERS
Explanation: The name specified for a generation

data group cannot exceed 35 characters.
Application Programmer Response: Shorten the
generation data group name and rerun the job.
Source: DFSMSdfp
IDC3524I
KEYRANGE VALUES EXCEED

KEYLENGTH OR ARE NOT IN
ASCENDING ORDER
Explanation: This message is issued by DEFINE

when the key values of the KEYRANGE parameter are
specified incorrectly. Either a key range key value was
longer than the user specified/defaulted key length or
the key range pairs were in nonascending order.
key range values on the DEFINE command. Determine
what the key length will be for the data set and insure
that all key values specified in the KEYRANGE
parameter are no longer than this length. Also, insure
that key range pairs are ordered in ascending
sequence. Then resubmit the job.
Source: DFSMSdfp
Detecting Module: IDCDE01, IDCDE02
IDC3525I
INSUFFICIENT SECURITY
AUTHORIZATION TO ALTER KEYS
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

password of the protected component is sufficient.
Source: DFSMSdfp
System Action: Processing of the command is ended.

proper level password or have your RACF profile
altered to the required level of access. Rerun the job.
Source: DFSMSdfp
IDC3530I
ENTRY AND NEWNAME PDS NAMES

MUST BE THE SAME
Explanation: An attempt was made to rename PDS

member but the entry name and the new name
referenced different partitioned data set names.
IDC3527I
ALTER WAS UNABLE TO LOCATE

ATTRIBUTES OF OBJECT TO BE
MODIFIED
Explanation: The entry to be modified could not be

found in the catalog.
Application Programmer Response: Make sure that

the same PDS name is given in both the entry name
and new name parameters.
Source: DFSMSdfp
dsname IS A RLS DATA SET WHICH IS

INCOMPATIBLE WITH THIS LEVEL OF
DFSMS

catalog entry exists and the catalog being used is
proper.
IDC3531I

Explanation: The data set specified on an IDCAMS

ALTER NEWNAME command is a RLS data set and
cannot be altered on this level of DFSMS.
Source: DFSMSdfp
dsname The data set name.

command.
IDC3528I
Application Programmer Response: Run command

on appropriate level of DFSMS.
THE OBJECT TO BE MODIFIED IS

PASSWORD SUPPRESSED
Explanation: The MASTERPW password of the entry

or the UPDATEPW or higher level catalog password
must be supplied for modifications to be allowed to the
entry.
Application Programmer Response: Verify which
password is required and provide the password.
Source: DFSMSdfp
IDC3529I
NAME CREATED FROM GENERIC

NEWNAME IS LONGER THAN 44
CHARACTERS
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
IDC3536I
INVALID USE OF * WITH THE

NEWNAME PARAMETER
Explanation: If either the ENTRYNAME or

NEWNAME parameter specifies a generic name (*),
then both must.
both the ENTRYNAME and NEWNAME parameters
specify a generic name if either do.
Source: DFSMSdfp

error and rerun the job.
439
IDC3537I
INVALID ALTERNATE INDEX

PARAMETERS SPECIFIED
Explanation: Either UPGRADE is specified but the

object being altered is not an alternate index, or
UNIQUEKEY is specified but the data object being
altered is not the data object of an alternate index.
specify the name of an alternate index, or the data
object name of an alternate index.
Source: DFSMSdfp
IDC3540I
Explanation: The new key length, key position, or

maximum record size is such as to require a larger
control interval.
System Action: The objects catalog entry is not
altered.
Application Programmer Response: Delete and
redefine the object with the proper KEYS and
RECORDSIZE parameters.
Source: DFSMSdfp
IDC3541I

IDC3538I
UNIQUEKEY/UPGRADE INVALID FOR

NON-EMPTY ALTERNATE INDEX
Explanation: The UNIQUEKEY or UPGRADE

parameter is specified, but the alternate index is
non-empty. These parameters may only be specified if
the alternate index contains no records.
Application Programmer Response: If
UNIQUEKEY/UPGRADE alternate index is truly desired,
the alternate index must be deleted and redefined with
proper attributes, then rebuilt with BLDINDEX.
Source: DFSMSdfp
IDC3539I
KEYS AND/OR RECORDSIZE

PARAMETER SPECIFIED FOR
NON-EMPTY OBJECT

KEYS or RECORDSIZE parameter, but the cluster or
alternate index contains data records.
altered.
change key position and/or record size, you must
delete, redefine, and reload the object.
Source: DFSMSdfp
440
KEYS/RECORDSIZE VALUES
CONFLICT WITH CONTROL INTERVAL
SIZE
NEW ALTERNATE INDEX KEY VALUES

CONFLICT WITH BASE CLUSTER
RECORDSIZE
Explanation: The ALTER command for an alternate

index specifies a KEYS parameter for a key whose
ending position is outside the base clusters maximum
record size. If the base cluster is spanned, the ending
key position must be in the base clusters first control
interval.
altered.
ALTER command or correct the base clusters
maximum record size or control interval size.
Source: DFSMSdfp
IDC3542I
AVG AND MAX RECORDSIZE NOT

EQUAL FOR RELATIVE RECORD DATA
SET
Explanation: The RECORDSIZE parameter specified

average and maximum record sizes that were not equal.
Relative record data sets must have fixed-length
records.
Source: DFSMSdfp
IDC3545I
KEYS AND/OR RECORDSIZE VALUES

CANNOT BE ALTERED
Explanation: The ALTER command specified new

KEYS or maximum RECORDSIZE values for an object
whose corresponding values were specified when the
object was defined, or which have been altered to

non-default values.
altered.
IDC3568I
(xxx) INVALID USE OF *
Explanation: The level name starts or ends with an *,

which is not allowed.

correctly redefine the object.
xxx
Source: DFSMSdfp

level name and rerun the job.
IDC3546I

NEW KEY VALUES CONFLICT WITH

RECORDSIZE
Explanation: The ALTER command specifies a KEYS

parameter that defines a key whose ending position is
outside the maximum recordsize.
Application Programmer Response: Specify key
length and position such that the key is entirely
contained in the base cluster record.
The indicated level name.
Source: DFSMSdfp
IDC3570I
Source: DFSMSdfp
IDC3547I
ENTRY TYPE INVALID WITH

KEYS/RECORDSIZE PARAMETER
Explanation: The entry name specified is not the data

component of a cluster or alternate index, nor is it a
cluster or alternate index, nor is it a path over a cluster
or alternate index.
System Action: The entrys catalog data is not
altered. Processing of the command is ended.
entry name and rerun the job.
Source: DFSMSdfp
IDC3558I
FORCE OPTION IS INVALID FOR

ENTRY TYPE
Explanation: The FORCE option on the DELETE

command can be used to delete only data spaces,
generation data groups, and VSAM user catalogs, but
the FORCE option was specified on a DELETE
command for some other type of entry.
System Action: The DELETE command is not run.
Processing continues.
Source: DFSMSdfp
DELIMITERS MUST NOT BE SPECIFIED

WHEN RELOADING A CATALOG
Explanation: REPRO command delimiters

(FROMKEY, TOKEY, etc.) cannot be specified for
reloading a catalog.
Application Programmer Response: Remove
delimiters from the REPRO command.
Source: DFSMSdfp
IDC3572I
TARGET CATALOG IS TOO SMALL TO

CONTAIN THE BACKUP CATALOG
Explanation: The size of the target catalog is

inadequate.
Application Programmer Response: Determine size
of the backup catalog from LISTCAT output obtained at
the time of the unload. Redefine the target catalog with
adequate space to contain the low key range of the
catalog.
Source: DFSMSdfp
441
IDC3573I
text
v VVDS Sphere Record (maybe)

NAME OF BACKUP AND TARGET CATALOG DO
NOT AGREE
VOLSER OF BACKUP AND TARGET CATALOG DO
NOT AGREE
DEVTYP OF BACKUP AND TARGET CATALOG DO
NOT AGREE
An additional record has been found.
The target catalog name, its volume serial number,

and/or the device type do not agree with the backup.


Application Programmer Response: Check whether
you are reloading from the proper backup into the
intended catalog.
Source: DFSMSdfp
IDC3576I
ALTER CATALOG NAME FOR dsname

FAILED
Explanation: During REPRO copy of a catalog entry

record, from one ICF catalog to another, an attempt was
made to update the catalog pointer in the corresponding
VVR record. This update processing for dsname failed.
dsname
The data set name.
System Action: Processing is ended.

Application Programmer Response: Use the PRINT
command to display the contents of the target catalog. If
it contains more than the expected records redefine the
catalog and rerun the job.
Source: DFSMSdfp
IDC3578I
SOURCE AND TARGET CATALOG ARE

SAME
Explanation: During an ICF catalog REPRO copy

request, it has been determined that the ICF catalog
names, identified by the INFILE/INDATASET and
OUTFILE/OUTDATASET parameters, specify the same
name. This implies a copy to itself and is not allowed.
source or target catalog specification and rerun the job.
Source: DFSMSdfp
Application Programmer Response: Resolve

problem described by preceding message(s), restore
volumes and rerun the job.
IDC3579I

Source: DFSMSdfp
IDC3577I
TARGET CATALOG IS NOT EMPTY
Explanation: During a REPRO copy of an ICF

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
442
SOURCE CATALOG LRECL IS LARGER

THAN TARGET CATALOG LRECL
Explanation: Before an ICF catalog copy operation,

the LRECL of the source catalog has been compared to
that of the target catalog. It has been determined that
the source catalog LRECL value is larger than the
target LRECL value and thus records in the source
catalog may not fit in the target catalog.
Application Programmer Response: Review the
attributes of the target catalog and redefine it with an
LRECL value equal to or greater than that of the source
catalog. Rerun the job.
Source: DFSMSdfp
IDC3580I
dsname DOES NOT SPECIFY A BASE

OBJECT
Explanation: During a REPRO ICF catalog merge

operation, catalog entry dsname was found to identify:
v An entry for an object other than
a cluster
a non-VSAM
a GDG
a user catalog
v A VVDS name
v The source catalog name
dsname
The data set name.
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
non-linear. The LRECL of the physical sequential
data set is not equal to the CISIZE of the linear data
set.
status of the input and output data sets. REPRO is
unable to satisfy your request. Set up data sets
correctly and rerun the job.
Source: DFSMSdfp

ENTRIES specification and rerun the job.
IDC3583I

prm INCOMPATIBLE WITH INFILE

DATA SET TYPE
Source: DFSMSdfp
Explanation: The specified parameter is not correctly

used with this type data set. A conflict results between
delimiters and the data set type. An example is
specifying the TOKEY parameter with an relative-record
data sets.
prm
IDC3581I
REPRO OF CATALOGS CANNOT

SPECIFY DELIMITERS
Explanation: The REPRO command does not process

beginning and ending delimiters when you are copying
catalogs.
incorrect parameters from the command and rerun job.

parameters or data set specified and rerun.

Source: DFSMSdfp
Source: DFSMSdfp
IDC3584I

IDC3582I
INPUT DATA SET ORGANIZATION

INCOMPATIBLE WITH OUTPUT DATA
SET
Explanation: When you attempt to copy information

from one data set into another, this error condition
occurs when one of the following is true:

IDCRP01
RECOVERABLE CATALOGS CANNOT
BE COPIED
Explanation: A REPRO command specified a VSAM

catalog copy operation where either the input catalog or
the output catalog or both was defined with the
RECOVERABLE attribute. Neither the source or target
catalog can be recoverable in a catalog copy operation.
Application Programmer Response: To convert a
443
unrecoverable catalog into a recoverable catalog, you

must export each VSAM data set from the
unrecoverable catalog, then import it into the newly
defined recoverable catalog. To convert a recoverable
catalog into a unrecoverable catalog or to copy a
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
IDC3585I
dsname IS INVALID FOR

{ENCIPHER|DECIPHER}
Explanation: The data set is not a valid source or

target for an ENCIPHER or DECIPHER operation. The
data is incorrect for one of the following reasons:
v ENCIPHER was specified and the source is a VSAM
catalog.
v ENCIPHER was specified and the target is not a
SAM or VSAM ESDS (entry-sequenced data set)
data set.
v DECIPHER was specified and the target is a VSAM
catalog.

statement pointed to by the OUTFILE parameter or the
data set name specified by the OUTDATASET
parameter to specify a target data set with the
appropriate record length.
Source: DFSMSdfp
IDC3587I
UNLOAD/RELOAD NOT ALLOWED

FOR CATALOG
Explanation: An ICF catalog was identified as the

source or target catalog during a REPRO request and
the other object identified was a non-VSAM data set.
This implies an ICF catalog unload or reload operation
and it is not allowed.
source and/or target specifications and rerun the job.

dsname
Source: DFSMSdfp
v DECIPHER was specified and source is not a SAM

or VSAM ESDS data set.
The data set name.

statement pointed to by the INFILE or OUTFILE
parameter or the data set name specified by the
INDATASET or OUTDATASET parameter to specify a
data set of the correct type for the operation.
Source: DFSMSdfp
IDC3586I
CANNOT ENCIPHER RRDS TO

TARGET DATA SET
Explanation: The source data set for an encipher

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.
444
IDC3588I
WRONG CATALOG TYPE FOR

MERGECAT PARAMETER
Explanation: The MERGECAT parameter has been

coded but the source and target catalogs, identified by
the INFILE/INDATASET and OUTFILE/OUTDATASET
parameters, are not both ICF catalogs.
MERGECAT parameter or correct the source and target
catalog specifications and rerun the job.
Source: DFSMSdfp
IDC3589I
VVDS NOT ALLOWED FOR REPRO
Explanation: A VVDS has been identified as the

source or target object of a REPRO command. The
data set identified by the INFILE/INDATASET or
OUTFILE/OUTDATASET parameters has the VVDS
prefix SYS1.VVDS.V.

Source: DFSMSdfp
Detecting Module: IDCRX01, IDCCC01, IDCRC02,
IDCXP01
IDC3596I

source or target specifications and rerun the job.
Source: DFSMSdfp
IDC3592I
THE ENTRY NAME IS NOT A CLUSTER,

ALTERNATE INDEX OR ICF CATALOG
Explanation: The object identified by the entry

parameter in the EXPORT command is not a cluster,
alternate index or ICF catalog. Only cluster, alternate
index or ICF catalog objects can be exported.
THE DATA SET SPECIFIED IN THE

EXPORT PARAMETER IS NOT USABLE
Explanation: The data set specified in the EXPORT

command has been marked as not usable by a
DELETE FORCE operation or by a RESETCAT
operation because of space occupancy conflicts.
Application Programmer Response: This data set
cannot be exported under current catalog conditions. If
you wish to recover the data, use the REPRO
command.
Source: DFSMSdfp
System Action: The command is ended. No export

action takes place.
IDC3598I
Application Programmer Response: If a catalog is to

be disconnected, DISCONNECT must be specified in
the command. Check to be sure your entry name is a
cluster, alternate index or ICF catalog object name.
Explanation: The object identified by the entry

parameter in the EXPORT command is a VSAM volume
Data Set which cannot be exported.
OBJECT IS A VSAM VOLUME DATA

SET WHICH CANNOT BE EXPORTED


action takes place.
Source: DFSMSdfp


IDC3593I
A REQUIRED CATALOG FIELD WAS

NOT LOCATED
Explanation: One of the following required catalog

fields could not be located by catalog management:
ENTYPE, ENTNAME, or NAMEDS.
action takes place.
Application Programmer Response: Something is
wrong with the catalog entry for this cluster. If this
happens, consult your system programmer.
Application Programmer Response: Do not attempt

to export a VSAM Volume Data Set.
Source: DFSMSdfp
IDC3599I
UNABLE TO SERIALIZE ON CATALOG

catname
Explanation: An attempt was made and has failed to

serialize the catalog, CNVTCAT or REPRO. The catalog
is to be serialized to prevent its update during
processing.
catname
The catalog name.
445
System Action: The CNVTCAT or REPRO command

is ended.
subparameters in OBJECTS parameter and rerun the

job.
Application Programmer Response: You should

restrict access to the catalog during this process and
rerun the job.
Source: DFSMSdfp

Source: DFSMSdfp
IDC3602I
IMPORT OF DATA SET FAILED AFTER

DEFINE DELETE ATTEMPTED
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,
I/O error on portability data set, for instance).

IDC3606I
PORTABILITY DATA SET IN ERROR
Explanation: The data on the portable data set is not

as was expected; specifically, the record preceding the
data records for the cluster or alternate index is
incorrect. Probable user error.
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.
If the problem reoccurs, do the problem determination
action.
Source: DFSMSdfp
For IMPORTRA, message IDC2621I follows this

message and gives the name of the failing cluster or
alternate index.
IDC3607I
System Action: For IMPORT, the command is ended.

For IMPORTRA, processing continues with the next
object on the portable data set unless an I/O error
occurred on the portable data set, in which case the
command is ended.
Explanation: The deletion that was to be attempted

was not performed. A duplicate name was found in the
catalog, and the temporary export flag was not on for
the duplicate data set or the data set was not empty.
Application Programmer Response: Consult the

message preceding this message in the program listing.
Source: DFSMSdfp
Detecting Module: IDXMP01, IDCRM01
DELETE UNSUCCESSFUL - NOT A

TEMPORARY DATA SET

name, or delete the duplicate cluster if you mean to
replace it.
Source: DFSMSdfp
IDC3605I
INVALID OBJECTS SUBPARAMETER

FOR ICF CATALOG
Explanation: The NEWNAME or KEYRANGES

parameters, has been specified as a subparameter(s) of
the OBJECTS parameter, on an IMPORT command.
The portable data set contains an ICF catalog for which
these subparameters are incorrect.

IDC3608I
CONNECT FOR dsname FAILED
System Action: IMPORT ends processing.
Explanation: This message merely identifies the name

of the user catalog which could not be connected. A
message will follow to explain the catalog return code
received when attempting to connect the user catalog.
Application Programmer Response: Remove these
446
dsname

The data set name.

message following this message in the program listing.
Source: DFSMSdfp
Application Programmer Response: Specify device

types and volumes in the command to connect a user
catalog.
Source: DFSMSdfp

IDC3612I
IDC3609I
VOLUME SPECIFICATION NEEDED

FOR dsname
Explanation: Volume information could not be found

on the portable data set or in the IMPORT command.
You are probably trying to import a portable data set
from a system using the first release of access method
services (OS/VS2 Release 2, OS/VS2 Release 1.6,
OS/VS1 Release 2, or DOS/VS Release 29).
dsname
The data set name.
Application Programmer Response: If the portable
data set was created with the EXPORT PERMANENT
option on a system using the first release of access
method services (as listed above), you must specify
volume information by using the OBJECTS parameter of
the IMPORT command. If you specify the cluster name
in the entryname subparameter of the OBJECTS
parameter, the volume information will be propagated to
the data component and, for a key-sequenced cluster, it
will be propagated to the index component. Volume
information may be specified separately for the data and
index components by repeating the OBJECTS
parameter list, which will override any cluster
specification.
Source: DFSMSdfp
IDC3610I
SPECIFICATION OF DEVICE TYPES,

VOLUMES REQUIRED FOR CONNECT
Explanation: When connecting a user catalog, the

DEVICETYPES and VOLUMES parameters, as well as
the catalog name, are required.
DELETE UNSUCCESSFUL - NOT A

CLUSTER OR AIX
Explanation: An attempt was made to delete the

duplicate entry because catalog define of the cluster or
alternate index being imported failed due to the
existence of a duplicate name in the catalog. A locate
performed on the name revealed that the entry was not
a cluster or alternate index.
NEWNAME parameter to change the name of the
cluster or alternate index you are attempting to import.
Do a LISTCAT to see what you really have; what you
are trying to import has a conflicting name in the
catalog.
Source: DFSMSdfp
IDC3613I
ERROR ENCOUNTERED OPENING

PORTABILITY DATA SET
Explanation: The portability data set could not be

opened.
Application Programmer Response: None. The
preceding message in the listing explains why the entry
data set was not opened.
the job log for more information. search problem
Source: DFSMSdfp
447
IDC3614I
INVALID NAME IN OBJECTS

PARAMETER: obj
Explanation: The name specified in the OBJECT

parameter in the IMPORT command does not match
any of the object names for the VSAM data set being
imported.
obj
The specified object.

object name.
Source: DFSMSdfp
IDC3615I
DSNAME ON THE OUTFILE JCL

STATEMENT INCORRECT
Explanation: The cluster or alternate index name of

the imported data set does not match the data set name
specified in the JCL statement identified by the
OUTFILE parameter. The data set name in the JCL
statement must be the same as the object being
imported or a path over it.
ended.
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
(d)
The maximum record size of the data set being

imported into is less than that of the data set
exported.
System Action: IMPORT processing is ended.

redefine the predefined data set with proper attributes.
Then rerun the job.
Source: DFSMSdfp
IDC3619I
ALTER RENAME FOR IMPORTRA

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
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
in a preceding message. Message IDC2621I follows this
message. It gives the real name of the failing object.
System Action: Processing of the IMPORTRA
command is ended.
reason for the failure of the ALTER, correct the problem,
and rerun the job.
Source: DFSMSdfp

IDC3624I
IDC3617I
ATTRIBUTES OF PREDEFINED ENTRY

INCOMPATIBLE WITH THOSE
EXPORTED
Explanation: The control interval size of the data set

being imported into is not equal to the size of the data
set exported. The data set being imported into is not
consistent with that one which previously exported and
now being imported. One of the following things is
wrong:
(a)
The relative key positions are not equal.
(b)
The data sets are not of the same type (KSDS,

RRDS, ESDS, and LDS).
(c)
The key lengths are not the same.
448
UNABLE TO OBTAIN OUTPUT DATA

SET NAME
Explanation: IMPORTRA was unable to obtain the

data set name from the OUTFILE JCL statement. This
is probably due to an error in the JCL statement.
statement. Ensure that it contains a data set name,
volume, unit, DISP=OLD, and the AMP=AMORG
parameter.
Source: DFSMSdfp
IDC3629I

IDC3625I
INTOEMPTY KEY WORD

{REQUIRED|NEEDED TO IMPORT INTO
AN EMPTY DATA SET}
Explanation: A duplicately named empty data set was

encountered while attempting to perform the import. The
loading of this data set with the data of the portable
data set was not allowed to occur because the user did
not specify the INTOEMPTY key word. As a security
precaution, the system does not allow imports into an
empty data set unless the INTOEMPTY key word has
been specified.
Application Programmer Response: If you own an
empty data set into which you have planned to import,
rerun the job and specify the INTOEMPTY key word. If
not, determine who owns the existing empty data set
and resolve the conflict in usage of this data set name
to insure proper protection for your data.
Source: DFSMSdfp
THE PORTABILITY DATA SET FORMAT

IS INVALID CI MODE NOT
SUPPORTED
Explanation: The portability data set format is control

interval (CI) mode which is not supported on this
operating system.
System Action: The IMPORT command is ended.
Application Programmer Response: The portability
data set must be created with record mode for it to be
supported on this system.
Source: DFSMSdfp
IDC3633I
SCANNING ERROR ON OS CATALOG

WHILE PROCESSING xxx INDEX
Explanation: An error occurred while scanning the OS

catalog. Processing was at the indicated index.
xxx
The indicated index.
System Action: Conversion is ended.

OS catalog being converted is valid by listing the OS
catalog using IEHLIST. If the catalog appears valid,
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

alternate index to the dummy name specified by the
DSN parameter on the OUTFILE DD statement. The
dummy name cannot be renamed to the real name and
the cluster or alternate index remains in the catalog with
the dummy name. The reason for the failure is given in
a preceding message. Message IDC2621I also
precedes this message. It gives the real name of the
failing cluster or alternate index.

Source: DFSMSdfp
dsname NOT A BASE CLUSTER
IDC3641I
Application Programmer Response: Delete the

cluster or alternate index using the dummy name in the
DELETE command. Correct any other error conditions
as indicated by previous messages and rerun the job.
Explanation: The data set is not a base cluster or a

path over a base cluster. The entry name was specified
in job control identified via (1) the INFILE dname
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.

Source: DFSMSdfp
dsname
The data set name.
System Action: Processing is ended for the entire
BLDINDEX command.
449
Application Programmer Response: The data set

name in the job control identified via the INFILE
subparameter or the data set name in the INDATASET
subparameter must be corrected to be that of a defined,
non-empty base cluster or a path over a base cluster.
Then resubmit the job.
Source: DFSMSdfp
IDC3683I
volser PLUS COUNT EXCEEDS

MAXIMUM VOLUME SERIAL NUMBER
Explanation: The number of volumes to be created,

added to the specified volume serial number (volser),
exceeds the maximum value of 999999.
volser
System Action: Command ends normally.

volume serial number with a lower number or request
less volumes to be created and rerun the command.
Source: DFSMSdfp
IDC3643I
dsname IS EMPTY
Explanation: The base cluster contains no records. In

order to build an alternate index, the base cluster must
contain at least one record.
dsname
The data set name.

IDC3691I
VOLUME ser LABEL NOT REBUILT
Explanation: The rewriting of the new volume label

failed. Either the volume is specified as READONLY or
an I/O error occurred when writing the label.
System Action: BLDINDEX processing is ended.
ser
Application Programmer Response: The base

cluster must be loaded via a user program (alternatively,
the access method services REPRO command may be
used) with at least one record. Then resubmit the job.
System Action: The command ends. The return code

is 12.

Application Programmer Response: Rerun the

command or take the Problem Determination actions.
Source: DFSMSdfp
Detecting Module: IDCMV01
IDC3692I
Source: DFSMSdfp
IDC3682I
FINAL CHARACTER(S) IN volser NOT

NUMERIC
VTOC HEAD ADDRESS CANNOT

EXCEED X'0012'
Explanation: The VTOC head address specified is too

large; it cannot exceed X'0012'.
is 12.
Explanation: A character in the volume serial number

is not a numeric value and cannot be incremented to
created new volume serial numbers.
Application Programmer Response: Specify a VTOC

head address not exceeding X0012 and rerun the
command.
Source: DFSMSdfp
volser
System Action: Function ends normally.

beginning volume serial number with adequate number
of numeric characters and rerun the command.
Source: DFSMSdfp
450
IDC3700I
** LATEST COPY RECORD CANNOT

BE RETRIEVED FROM INVENTORY
Explanation: An attempt to access the record for the

latest copy recorded in the Inventory data set failed.
The command checks if the latest copy is incomplete
due to a previous copy failure; the cartridges will be
reused if an incomplete copy exists. See the preceding
message for the error condition.

message.
problem as indicated in the preceding message and
rerun the command.
v Run the REMOVEVR command to delete the copy

volume record from the Inventory data set if both
cartridges are lost.
v Reenter the missing cartridges in the Mass Storage
Facility (MSF) while the Mass Storage Volume
Control (MSVC) is enabled.
Source: DFSMSdfp
IDC3706I
Source: DFSMSdfp
IDC3701I
** OLDEST BACKUP COPY RECORD

INVENTORY
Explanation: An attempt to access the record for the

oldest backup copy volume recorded in the Inventory
data set failed. The cartridges of the oldest backup copy
are to be either reused or scratched. See the preceding
message for the error condition.
System Action: This command ends with an error
message.
problem as indicated in the preceding message and
rerun the command.
Source: DFSMSdfp
IDC3702I
TARGET COPY yyddd CANNOT BE

USED
Explanation: The command selected the cartridges of

an existing copy volume created on the date indicated
for reuse but the cartridges cannot be used. The
following message explains why the designated copy
volume cannot be used.
yyddd
The date in year and days.

message.
Application Programmer Response: Before
rerunning the COPYV command, either:
** COPY TO CARTRIDGES csn1 csn2 IS

INCOMPLETE
Explanation: The copy operation to the copy volume

failed. The copy volume is marked incomplete in the
Inventory data set and will be reused by the COPYV
command when the command is run again. The
cartridges of the copy volume were selected either by
the user, by the Mass Storage Control (MSC) at
random, or by the command using an existing copy
volume. See the preceding message for further
explanation of the error.
csn1
csn2

rerunning the COPYV command correct the problem as
indicated in the preceding message.
Rerun COPYV to complete the copy operation to the
incomplete copy volume (COPYV will reuse the
copy) or run SCRATCHV to scratch the incomplete copy
volume before rerunning the COPYV command.
If COPYV ends without indicating the status of the copy
operations, LISTMSVI can be run the determine
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
a note that a copy operation failed for the preceding
copy volume.
to the problem.
Source: DFSMSdfp
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
Explanation: No existing copy volumes were eligible

for reuse for this copy request. An attempt to create a
new target volume from scratch cartridges failed. A new
copy volume was not created. See the preceding
message.
error condition as indicated in the preceding message
and rerun the command.
volser

message.
command requesting a specific nonbackup copy volume
if any exist.
Source: DFSMSdfp
IDC3712I
Source: DFSMSdfp
IDC3709I
** COPY TO CARTRIDGES csn1 csn2

NOT PERFORMED
Explanation: The Mass Storage Controller (MSC)

could not perform the copy operation to the copy
volume. The copy volume remains usable because the
original data on the volume was not destaged. See the
preceding message for further explanation of the error.
csn1
csn2

message.
error as indicated in the preceding message and rerun
the command.
Source: DFSMSdfp
** LATEST BACKUP COPY RECORD

INVENTORY
Explanation: The recovery operation requires the

latest backup copy, but the record for that copy volume
could not be retrieved from the Inventory data set. See
error.
message.
rerunning the command correct the error as indicated in
the preceding message or specify another copy to be
used in the recovery operation.
Source: DFSMSdfp
IDC3720I
NEW SERIAL NO. REQUIRED TO

ACTIVATE A COPY OR DUPLICATE
VOLUME
Explanation: A copy or duplicate volume cannot be

activated unless the volume is relabeled with a unique
volume serial number.
IDC3710I
** NO BACKUP COPY VOLUMES EXIST

FOR VOLUME volser
Explanation: The designated volume has no backup

copy. The option to restore from the latest backup
cannot be satisfied. See the preceding message for
further explanation of the problem.
452

command specifying the NEWSERIAL parameter and a
unique volume serial number that can be used to
relabel the copy or duplicate volume in order to activate
it.

Source: DFSMSdfp
IDC3721I
VOLUME volser IS ALREADY ACTIVE
command to store the volume, but do not request the

volume serial number be changed. If the volume must
be renamed, run the SCRATCHV command to scratch
all copies before requesting STOREV to rename and
store the volume.
Explanation: The designated volume is already active.
Source: DFSMSdfp
volser

Source: DFSMSdfp
IDC3732I

MADE INACTIVE
Explanation: The status of the volume could not be

changed from active to inactive. See the preceding
message for further explanation of the error.
IDC3726I
UNABLE TO REPLACE THE BASE

VOLUMES
Explanation: The REPLACEVOLUME key word

parameter is specified, but the base volume cartridges
are not reassigned or are in the Mass Storage Facility.
System Action: The request is bypassed, but an
attempt is made to fulfill the remaining requests.
Application Programmer Response: The request
can be modified and rerun. A new serial number
(NEWSERIAL) must be supplied without the
REPLACEVOLUME key word parameter. The same
request can be rerun if the base volume is first ejected
or nullified.
problem.
Source: DFSMSdfp
IDC3730I

RELABELED; COPIES EXIST
Explanation: The volume serial number of the volume

cannot be changed because copies of the volume exist.
volser

message.
volser

error as identified in the preceding message.
Rerun STOREV or run MODIFYV to either backout or
If the STOREV or MODIFYV commands are run to
recover from a rename failure, the DD statement for the
volume is required and must specify deferred mounting.
The values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is
recorded in the Inventory data set. If the cartridge labels
have been updated, the volume record will be identified
by the new volume serial number. For the VOLUME
parameter, specify the volume serial number as
recorded in the cartridge labels and the volume record.
For the NEWSERIAL parameter, specify the desired
volume serial number. Note that the 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. This allows the
original volume serial number of a VSAM volume to be
If STOREV ends without indicating the status of the
rename operation, LISTMSVI can be run to determine
the 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 a rename operation failed for the preceding volume
453
Source: DFSMSdfp
IDC3734I
** VOLUME LABEL COULD NOT BE

RESTORED TO ORIGINAL STATUS
Explanation: Following a failure to deactivate the

volume and change the volume serial number in the
cartridge labels, an attempt to restore the volume label
to its original status also failed. A volume
serial-mismatch exists between the volume label and
the cartridge labels of the cartridges assigned to the
Mass Storage Volume. A flag indicating the mismatch is
set in the Inventory data set for the volume. See the
preceding message for further explanation of the
problem.
message.
error as identified in the preceding message.
v If a Rename Operation Failed for ADDV
Run ADDV to backout or retry the rename operation
if the volume is inactive. If the volume is active, run
rename operation.
mounting.
If ADDV, MODIFYV, or STOREV ends without
v If a Rename Operation Failed for MODIFYV
To recover from a MODIFYV rename failure 1) run

ADDV to activate the volume if the volume is merely
inactive and has no volume serial mismatch
condition, or 2) run ADDV to both activate the volume
and complete the rename operation if the volume is
condition, or 3) rerun MODIFYV to complete or retry
the rename operation if the volume is active but has
a mismatch condition, or 4) run STOREV to complete
or retry the rename operation if the volume is active
and if a duplicate volume serial number is desired as
result of the rename.
v If a Rename Operation Failed for STOREV
Rerun STOREV or run MODIFYV to either backout or
Source: DFSMSdfp
IDC3736I
ddname MUST NOT BE ALLOCATED

TO SHARED OR SHARED U.P. UNITS
Explanation: CONVERTV can only use non-shareable

spindles, and cannot be a uniprocessor unit.
ddname
The DD name.
Application Programmer Response: See your
system programmer to determine if a shared spindle
was used or if the system was sysgened for
uniprocessor operations.
Source: DFSMSdfp
IDC3738I
** DATA SETS NOT RECATALOGED IN

VSAM CATALOG
Explanation: An error occurred which prevented all

the data sets in the VSAM owning catalog from being
recataloged. A preceding message explains the error.
System Action: The command ends normally. If the
454
target volume is a 3336 Model 1 Disk Pack, use Device

Support Facilities to reformat the volume to meet the
empty VTOC requirement of the CONVERTV command.
error and rerun the command.
catalog. 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
to the problem.
Source: DFSMSdfp

Source: DFSMSdfp
IDC3741I
RECATALOG OPTION INVALID FOR

VSAM VOLUME
Explanation: The source volume is owned by a VSAM

catalog and the volume and any VSAM data sets on the
volume must be recataloged. Therefore, NONE is an
incorrect option.
IDC3739I
FROM AND TO UNITS ARE THE SAME

DEVICE TYPE
Explanation: The device type specified in the UNIT

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
error message.
Application Programmer Response: Either correct
the UNIT parameter and rerun the command or if you
want to move data between two volumes of the same
type, use the IEHMOVE utility program.
Source: DFSMSdfp

VSAMCATALOG option on the RECATALOG parameter
or omit the control statement. Rerun the command.
Source: DFSMSdfp
IDC3744I
JOBCAT/STEPCAT MUST NOT BE

SPECIFIED FOR VSAM CATALOG ON
VOLUME
Explanation: A JOBCAT or STEPCAT DD statement

was used to allocate the VSAM user catalog on the
volume to be processed. If the VSAM user catalog is on
the volume being processed, the user catalog must not
be open as a result of the use of a JOBCAT or
STEPCAT DD statement.
IDC3740I
MULTIPLE VOLUME SERIAL NUMBERS

ASSOCIATED WITH FILE ddname
Explanation: CONVERTV will only convert a single

volume at a time. The specified ddname has more than
one volume associated with it.
ddname
The specified DD name.
Application Programmer Response: Specify only
one volume serial on the DD statement or supply a
FROMVOLUME statement for the volume to be
converted. Rerun the command.
Application Programmer Response: Use a standard

DD statement ddname rather than JOBCAT or
STEPCAT to allocate the VSAM user catalog, and
supply that ddname in the CATALOG parameter. Rerun
the command. In VS2 you can omit the DD statement
and only specify the name of the catalog on the
CATALOG parameter.
455
Source: DFSMSdfp
Detecting Module: IDCCN01, IDCSR01
IDC3745I
DD NAME MUST BE SPECIFIED FOR

VSAM USER CATALOG ON VOLUME
Explanation: No ddname was specified for the VSAM

CATALOG residing on the volume being processed
preventing the catalog from being opened.
is not created or modified. Control is returned to the

user with a condition code of 12.
correct combination of parameters and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCGR01, IDCMG01
IDC3820I
System Action: Command ends normally.

Application Programmer Response: Supply a DD
statement for the catalog that owns the volume. The DD
statement name cannot be JOBCAT or STEPCAT.
Specify the name of the DD statement which allocates
the catalog in the CATALOG parameter. Rerun the
command.
Source: DFSMSdfp
Detecting Module: IDCCN01, IDCSR01
** TABLES COULD NOT BE COPIED TO

WORK DATA SET
Explanation: An error code was returned from the

request to copy the MSC tables to the work data set. A
preceding message explains the reason.
System Action: The command preceding ends
normally.
preceding message to determine the exact error.
Correct the error and rerun the command.
Source: DFSMSdfp
IDC3770I
VOLUME volser ACTIVE
Explanation: The volume is active and cannot be

ejected.
volser

message.
STOREV command to both deactivate and eject the
volume.

IDC3822I
MSF NOT AVAILABLE
Explanation: The Mass Storage Facility (MSF) does

not have a staging adapter assigned to it in the Mass
Storage Control (MSC) tables and cannot be considered
to exist for system use.
Application Programmer Response: Specify a valid
MSF on the command and rerun the command.


Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: IDCEV01
Detecting Module: IDCAU01, IDCLM01
IDC3802I
IDC3835I
INVALID SIS PARAMETER
AN MSVI ERROR WAS DETECTED

WHILE PROCESSING CART (csn)
Explanation: Either an incorrect combination of

parameters was specified for the system-initiated
scratch function, or incorrect subparameters were
specified with the SIS parameter in the CREATEG or
MODIFYG command.
Explanation: A Mass Storage Volume Inventory

(MSVI) error occurred because either one or both
cartridge serial numbers of the volume record that was
being read were not properly initialized.
System Action: The request is ended and the group
456
csn

Application Programmer Response: The problem
was probably caused by a system failure during the
CREATEV command. Issue the SCRATCHV command
to scratch the incomplete mass storage volume. Rerun
the command.
JCL, the SYSOUT output for the job, all printed output
and output data sets related to the problem, and the
program listing for the job.
IDC3850I
THE NUMBER OF SECONDS IN THE

LRU CLOCK IS INVALID
Explanation: The number of seconds in the LRU clock

(LRUCLOCK parameter) is incorrect. The only valid
numbers are 128, 256, 512, 1024, 2048, 4096, 8192,
and 16384.
System Action: The command ends normally. No
tuning parameters have been changed.
LRUCLOCK parameter and rerun the command.
Source: DFSMSdfp
Source: DFSMSdfp
IDC3842I
IDC3851I
ORDER OF TRACE AREAS COULD

NOT BE DETERMINED - NO DATA
DUMPED
Explanation: An attempt was made to dump both

trace areas, but the first trace area could not be
determined. Therefore, no trace data was dumped. The
programmer will have to submit individual X and/or Y
trace dump requests.
TRACE command specifying either trace area X or
trace area Y.
Source: DFSMSdfp
LOWER VALUE MUST BE LESS THAN

HIGHER VALUE FOR ACTIVEPAGES
Explanation: On the ACTIVEPAGES parameter, the

lower number of pages is a number greater than or
equal to the higher number of pages. The lower number
must be less than the higher number.
ACTIVEPAGES parameter and rerun the command.
Source: DFSMSdfp
IDC3852I
TOTAL OF UNITS IN LRUGROUPS

MUST BE LESS THAN OR EQUAL TO
16
Explanation: When the LRU clock units for all groups

are added together they exceed the maximum (16).

IDC3844I

LRUGROUPS parameter (which specifies the number of
LRU clock units) and rerun the command.
BLOCKSIZE OF OUT DATA SET IS NOT

A MULTIPLE OF 264.
Explanation: Because trace records are 264 bytes

long, they must be blocked in multiplies of 264. That is,
the blocksize specified for the Output Data set must be
a multiple of 264.
System Action: The Trace Utility is ended.
blocksize specification in the JCL and rerun the job.
Source: DFSMSdfp
IDC3860I
GROUP PARAMETERS CANNOT BE

SPECIFIED FOR NONGROUPED
VOLUMES

Explanation: A request to set group level attributes for

a volume that does not belong to a group is incorrect.
Source: DFSMSdfp

message.
457
command after removing the conflicting parameters that

specify group attributes.
Source: DFSMSdfp
IDC3861I
VOLUME ser LABEL NOT REBUILT
Explanation: The rewriting of the new volume label

failed. Either the volume is specified as READONLY or
an I/O error occurred when writing the label.
ser

is 12.
command or take the Problem Determination actions.
Source: DFSMSdfp
IDC3885I
VOLUME ser PERMANENTLY

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

correct volume serial number was specified on the DD
statement for the FILE parameter. If the correct volume
serial was specified, you cannot run the command while
that volume is permanently resident or reserved.
Source: DFSMSdfp
IDC3862I
VTOC HEAD ADDRESS CANNOT

EXCEED X'0012'
IDC3897I
Explanation: The VTOC head address specified is too

large; it may not exceed X'0012'.
is 12.
Application Programmer Response: Specify a VTOC
head address not exceeding X0012 and rerun the
command.
Source: DFSMSdfp
IDC3883I
** ERROR COUNT EXCEEDED UPPER

LIMIT, FUNCTION TERMINATED
CONFLICT EXISTS BETWEEN

ENTRYNAME AND DD SPECIFIED ON
DATA SET NAME
Explanation: Conflict between the entryname

specified on DELETE command and data set name
specified on the file parameter referenced DD
statement.
System Action: The system processing continues.
Operator Response: Correct the data set name
specified on the file parameter referenced DD
statement, if incorrectly specified. Or, correct the
entryname in the entryname parameter on the DELETE
command, if incorrectly specified.
Explanation: A LISTCRA command encountered more

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.
Correct the problem, and rerun the job.
IDC3900I
Source: DFSMSdfp
return-code
458
PUTGET ERROR CODE IS return-code
Explanation: The PUTGET macro instruction failed.

Code
Explanation
The PUTGET service routine

did not complete. An
attention interrupt occurred

during the processing of
PUTGET, and the attention
handler turned on the
completion bit in the
communications ECB.
12
12
No prompting was allowed on

a PROMPT request. Either
the user at the terminal
requested no prompting with
the PROFILE command, or
the current source of input is
an in-storage list.
A line could not be obtained
after a MODE request. A
chain of second level
informational messages
exists, and the current stack
element is non-terminal, but
the terminal user did not
request PAUSE processing
with the PROFILE command.
The messages are therefore
not available to him.
IDC3901I
ERROR QUALIFYING dsname
Explanation: The Time Sharing Option/Extensions

(TSO/E) default service routine failed to qualify the data
set indicated.
dsname
The data set name.
System Action: The request is ended.
Application Programmer Response: An associated
message, IDC3902I directs the user in how to correct
this error.
Source: DFSMSdfp
16
The NOWAIT option was

specified for TPUT and no
line was put out or received.
IDC3902I
20
The NOWAIT option was

specified for TGET and no
line was received.
24
Incorrect parameters were

supplied to the PUTGET
service routine.
Explanation: This message contains the return code

information required to correct the error indicated in
associated message IDC3901I. The LOCATE error code
is part of VSAM Catalog Management. Refer to
message IDC3009I for the return codes as well as the
possible system and programmer responses.
28
A conditional GETMAIN was

issued by PUTGET for output
buffers and there was not
sufficient space to satisfy the
request.
32
The terminal has been

disconnected.
** DEFAULT SERVICE ROUTINE

ERROR CODE return-code, LOCATE
ERROR CODE cde
cde
The LOCATE error code.
rc
The possible system and programmer

responses for the default service routine error
conditions along with the return code, as
follows:
Code
Explanation

error based on the return code information and rerun
the job.
Return code from PUTLINE or

PUTGET was not zero.
Data set name was longer than 44

bytes.
12
An I/O error occurred while searching

the catalog, the catalog data set was
not available or the data set name
was not specified correctly.
16
The index structure of the catalog was

not consistent with the data set name.
For example, the name specified was
A.B.C, but there is a data set called
A.B, so there cannot be one called
A.B.C.

Source: DFSMSdfp
459
20
The data set name could not be found

in the catalog.
24
An attention interruption occurred

during processing of this request.
28
Incorrect parameters were specified.
32
It was necessary to prompt the user,

but the caller specified that the user
should not be interrupted.
36
Not enough qualifiers were specified

for the data set name. For example,
the name specified was A.B, but the
catalog contains an entry for A.B.C.

Application Programmer Response: The response
depends on the return codes, rc and cde. Possible
responses for return code rc follow:
Code
Response
Make sure the user is still logged on to the

system.
reason-code
The reason code returned by SMS
System Action: The system may end processing of

the IDCAMS command.
Application Programmer Response: Refer to
OS/390 DFSMSdfp Diagnosis Reference for an
explanation of the SMS reason code.
Source: DFSMSdfp
IDC3933I
ATTACH RETURN CODE WAS

return-code
Explanation: An ATTACH SVC returned the specified

code due to an error during the ATTACH operation.
return-code

command.
Correct the data set name.
Source: DFSMSdfp
12
Examine the data set name for syntax errors,

for example, embedded punctuation marks.
Check the CVOL index structures to be sure
CVOLs are properly linked. If an I/O error
occurred, it may be necessary to rebuild the
catalog.

IDC3936I
16
Respecify the data set name or recatalog the

data set.
Explanation: During DIAGNOSE processing, an error

occurred in CVAFFILT.
20
Respecify the data set name or recatalog the

data set.
return-code
The return code.
24
None.
reason-code
The reason code.
28
Check to be sure the parameter list for

IKJEHDEF was not improperly modified.

command.
32
None.
36
Respecify the data set name.
Source: DFSMSdfp

Source: DFSMSdfp
IDC3932I
STORAGE MANAGEMENT
SUBSYSTEM CALL FAILED. REASON
CODE WAS reason-code
Explanation: An IDCAMS command called a Storage

Management Subsystem (SMS) service, but the call
failed.
460
CVAFFILT ERROR RETURN CODE IS

reason-code

IDC4227I
AN ELSE COMMAND APPEARS

IMPROPERLY
Explanation: An ELSE modal command appears

without a matching IF-THEN modal command. Modal
command continuation may be incorrect.
System Action: The remainder of the command input
stream is ignored.
usage and rerun.


Source: DFSMSdfp
Source: DFSMSdfp
IDC4228I
IDC4232I
AN END COMMAND IS INVALID
Explanation: An END modal command occurs without

a matching DO modal command.
stream is ignored.
DO-END usage and rerun.
Source: DFSMSdfp
IDC4229I
IF COMMAND HAS INVALID

RELATIONAL EXPRESSION
Explanation: An IF modal command has an incorrect

relational expression.
IMPROPER OR MISSING THEN KEY

WORD
Explanation: The THEN portion of the IF modal

command is misspelled or missing. Modal command
continuation may be incorrect.
System Action: The remainder of the input stream is
ignored.
usage and rerun.
Source: DFSMSdfp
IDC4236I
INPUT STREAM END-OF-FILE FOUND

BEFORE END-OF-COMMAND

stream is ignored.
Explanation: Command input stream end-of-file has

been found while scanning a command. There may be
input records missing.

syntax and semantic requirements of the IF command.
Correct the usage and rerun.
System Action: The current command is not

processed.

Source: DFSMSdfp
IDC4230I
SET COMMAND HAS INVALID

ASSIGNMENT EXPRESSION
Explanation: A SET modal command has an incorrect

assignment expression.
stream is ignored.
syntax and semantic restrictions on the SET command.
Correct the usage and rerun.
Application Programmer Response: Add the missing

data and rerun.
Source: DFSMSdfp
IDC4237I
TOO MANY LEVELS OF IF COMMAND

NESTING
Explanation: IF modal commands have been nested

to a level that cannot be handled.
stream is ignored.
Application Programmer Response: Restructure the
modal commands to conform to the restriction of ten
levels of nesting.
461

Source: DFSMSdfp

Source: DFSMSdfp
IDC4999I
UABORT CODE return-code
Explanation: This message indicates an error, which

caused the processor to abort. The code number
indicates the nature of the error. Since the error is
usually such that no further processor code may be run
with confidence, this message appears in the output
listing by a write-to-programmer action.
return-code

Code
Explanation
24
Text processors print control

table address not set in GDT.
28
No virtual storage available

for one of the following:
v Text processors translate
table.
v Initialization of the I/O
adapter.
v Automatic (dynamic)
storage of a module.
v Text processor dynamic
storage.
See the in-virtual storage
trace tables to determine
which is the correct condition.
32
36
There was a request to

access an unopened data
set.
The processor was unable to
open SYSPRINT (or
whichever DD name is
employed to denote the
processors standard listing
output data set).
IDC11003I
CONTROL INTERVAL nnnnnn

BYPASSED IN CRA volser
Explanation: IGNORE was specified and an I/O error

was encountered. The record is ignored. This message
is preceded by IDC3351I which indicates the nature of
the error.
volser
nnnnnn The control interval number of the record in the

catalog.
Application Programmer Response: This may cause
errors to be detected in objects on the volume specified,
or objects on the volume may be totally lost without
notification. Perform a LISTCAT operation of the catalog
to determine which objects still exist after the reset
operation.
catalog.
Source: DFSMSdfp
IDC11015I
CONTROL INTERVAL nnnnnn

BYPASSED IN CATALOG
Explanation: IGNORE was specified and an I/O error

was encountered. The record is ignored. Message
IDC3351I precedes this message indicating the specific
error.
40
Incorrect U-macro argument

list found.
nnnnnn The control interval number of the record in the

catalog.
44
The processor is unable to

produce a dump.
56
The BLDL macro failed to

find a required AMS (access
method services) module.
72
An internal RESETCAT error

occurred (probable system
error).
462
Application Programmer Response: The record

noted in the catalog is inaccessible. If it contained a
corresponding reset CRA entry, the entry will be
recovered. If it contained a non-reset CRA entry, the
entry remains inaccessible. A LISTCAT may reveal
whether the error is of any consequence. nnnnnn is the
control interval number of the record in the catalog.

catalog.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11022I
entryname, type CONTAINS A

CONNECTOR TO INVALID RECORD
nnnnnn, type
Explanation: An object contains a dependency on a

record that does not exist. The base record is noted by
name and type. The dependent record which is
incorrect is noted by its expected control interval
number and record type. The reference to the incorrect
record is deleted. See either message IDC21024I,
IDC21025I or IDC21026I which follows. The message
will note the other action taken as a result of this error.
entryname
The base record noted by name.
nnnnnn
The control interval number of the

record in the catalog.
type
The entry type of the record. The

value are defined under message
IDC21045I.
IDC11029I
SPACE MAP FOR VOLUME volser

CORRECTED
Explanation: The suballocated VSAM data space has

been corrected to reflect what is on the volume. This
correction occurs if entries are deleted by RESETCAT,
or space stated as suballocated is not suballocated
(that is, the space map is incorrect on entry to
RESETCAT).
volser

is given for information only. It is a correction of some
state of error. The error may be specifically noted in a
preceding error message or not at all. In the latter case,
the situation is due to space being suballocated from
available suballocatable space; however, no entry can
be found which claims this space. No corrective action
by the programmer is required.
Source: DFSMSdfp

following message (noted in the explanation) to
determine what action was taken.
IDC11031I
Source: DFSMSdfp
IDC11023I
entryname, type, ERROR FOR

ASSOCIATION [nnnnnn,] type
Explanation: An entry is chained to a record of a type

different than anticipated, or the object noted consists of
incomplete set of records. If the control interval number
of the expected association is not given, then no
association for that object exists in the base record; an
association for that type is required for the entry name
noted. Message IDC21026I follows, noting that the entry
has been deleted.
entryname
The entry name noted.
nnnnnn
The control interval number of the

record in the catalog.
type
The entry type of the record. The

values of are defined under message
IDC21045I.

IDC21026I.
UNIQUE DATA SET entryname HAS

FEWER EXTENTS THAN THE DATA
SPACE
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
inform you that space exists which is not in use. If the
data set is extended, this space will be used. No
corrective action is taken.
entryname
The specified entry name.

Source: DFSMSdfp
IDC11033I
dsname, volser NOT DELETED
Explanation: A unique data set, on a volume not

being reset, has no corresponding DATA or INDEX
component. The component was defined on one of the
volumes being reset, but no longer exists on that
volume.
volser
463
dsname
The unique data set name.
Application Programmer Response: If the data set is
no longer valid, then SCRATCH it.
Source: DFSMSdfp
IDC11041I
dsname SPACE CORRECTED
Explanation: The extents in the space header for the

data space noted were not identical to the extents in the
corresponding Format 1 DSCB. The extents in the
space header were corrected using the extents in the
Format 1 DSCB and the Format 3 DSCB if one exists.
dsname
IDC11036I
entryname, type OUT-OF-SYNC ON

volser
The data set name.

Application Programmer Response: This may be

caused by some previous system error. This message is
given for information purposes. A later message may
indicate whether objects were marked unusable,
perhaps as a result of this condition if fewer extents
existed in the data set than the data space. Watch for
message IDC21027I or IDC21030I.
volser
Source: DFSMSdfp
entryname
The entry name indicated.
type
The type specified. The values of type

are defined under message
IDC21045I.
IDC11042I
Explanation: The data set named may have incorrect

space information. The extents occupied by the named
data set are not in conflict with any other VSAM data
set or with the system; however, a self-checking field
failed to check. The data set itself may be all right.

Application Programmer Response: List the data set
and ensure that it is correct and accessible.
Source: DFSMSdfp
dsname SPACE DELETED
Explanation: The space header for the data space

referred to a nonexistent Format 1 DSCB. The space
header for the data space was deleted.
dsname
The data set name.

IDC11040I
dsname UNKNOWN
Explanation: The VSAM Format 1 DSCB did not have

a corresponding space header in the volume record.
Hence, the catalog does not account for the space
allocated to the data set. The data set noted above was
scratched.
Application Programmer Response: This may be

caused by some previous system error. This message is
given for information purposes. A later message may
indicate whether objects were marked unusable,
perhaps as a result of this condition. Watch for
message IDC21037I or IDC21020I.
Source: DFSMSdfp
dsname

The data set name.

Application Programmer Response: If an I/O error
occurred when reading from the CRA for this volume,
this condition may arise. It may also be caused by some
previous system error. This message is given for
informational purposes. A later message may indicate
whether objects were marked unusable, perhaps as a
result of this condition. Watch for message IDC21027I
or IDC21030I.
Source: DFSMSdfp
IDC11043I
TIME STAMP FOR VOLUME RECORD

ON VOL volser WAS CORRECTED
Explanation: The time stamp for the volume record

did not match the time stamp in the VTOC. This may
have resulted from a failure in Catalog Management
after updating one and not the other. The time stamps
are synchronized.
volser

Source: DFSMSdfp
464

IDC11044I
dsname NOT SCRATCHED
Explanation: The attempt to scratch the data set for

the reason stated in preceding message IDC11040I
failed.
dsname
The data set name.
Application Programmer Response: See IDC11040I.
Source: DFSMSdfp
IDC11216I
INVALID R0/R1 STAGE ERROR

RECORD PAIR: R0 NOT FOUND
(volsercchh) IN REPAIR WORK FILE
dsname
Explanation: During deblocking, the record was not

found in the file indicated by dsname. If your installation
has D/T3350 support, ignore R0 (record 0). It is no
longer flagged with stage error information.
volsercchh
The indicated record.
dsname
The indicated data set name.
System Action: REPAIRV DEBLOCK continues

processing at the next valid state error record pair. The
return code is 4.
Application Programmer Response: Display the
repair work file records. If necessary rebuild the repair
work file using REPAIRV COPY.
Source: DFSMSdfp
dsname
System Action: REPAIRV DEBLOCK continues

processing at the next valid stage error record pair. The
return code is 4.
repair work file records. If necessary rebuild the repair
work file using REPAIRV COPY.
Source: DFSMSdfp
Detecting Module: ICRD04
IDC11218I
THE R0/R1 (volsercchh) PAIR ARE NOT

UNMODIFIED STAGE ERROR
RECORDS IN REPAIR WORK FILE
dsname
Explanation: The specified records in the repair work

file are not a R0/R1 pair created by a stage error. If
your installation had D/T3350 support, ignore R0 (record
0). It is no longer flagged with stage error information.
volsercchh
dsname
System Action: REPAIRV DEBLOCK continues with

the next valid stage error record pair. The return code is
4.
Application Programmer Response: Necessary,
display the repair work file records.
Source: DFSMSdfp

IDC11219I
IDC11217I
INVALID R0/R1 STAGE ERROR

RECORD PAIR: R1 NOT FOUND
dsname
Explanation: The record following the specified R0

stage error record is not an R1 stage error record. If
your installation had D/T3350 support, ignore R0 (record
0). It is no longer flagged with stage error information.
volsercchh
DEBLOCK FAILED FOR R0/R1

dsname
Explanation: Two consecutive errors were found while

trying to deblock the stage error record pair. An error
occurs when the length specified in the count field of a
record is wrong. This is determined by inspecting the
bytes following the specified length and not finding a
valid count field. REPAIRV DEBLOCK cannot continue
processing this record pair. If your installation had
D/T3350 support, ignore R0 (record 0). It is no longer
flagged with stage error information.
465
volsercchh
dsname
System Action: REPAIRV DEBLOCK continues with

the next valid stage error record pair. The return code is
4.
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.
Source: DFSMSdfp
IDC11250I
WARNING: NO VOLUME ATTRIBUTES

MODIFIED.
Explanation: While processing a MODIFYC

command, a cartridge label was changed to reflect it as
csn1|csn2 of a volume. However, no changes to the
volume attributes were requested in the command. If
the cartridge being modified was a scratch cartridge, the
scratch cartridge bit in the label remains on, to the
exclusion of all volume attributes. If the cartridge being
modified was not a scratch cartridge, then the volume
attributes remain unchanged and might not agree with
the mass storage control tables and the inventory data
set.
Modification of one or more volume attributes turns off
the scratch cartridge bit in the label.
System Action: The command continues normally.
error, if necessary, and rerun the command.
Source: DFSMSdfp
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
LISTCAT to verify the presence or absence of the entry
in the catalog.
If the entry is in the catalog but DIAGNOSE cannot
locate it, consult your hardware support personnel.
Source: DFSMSdfp
IDC11362I
THE FOLLOWING CATALOG

REFERENCED VOLUMES WERE NOT
ENCOUNTERED
Explanation: The catalog contains some entries for

VVDSs (volumes) that are not referred to by any of the
entries processed. The volume serial numbers of the
volumes containing the VVDSs are listed. This indicates
that certain entries in the catalog may be missing
volume information. However, under the following
circumstances, this message may indicate a normal
condition:
v If you converted or deleted all data sets on the
volume that are cataloged in the specified catalog.
v If you chose to explicitly catalog the VVDS.
System Action: DIAGNOSE considers this an
attention condition and processing continues.
Application Programmer Response: If DIAGNOSE
encountered any errors which precluded looking at any
volume cells, this message may be issued. Therefore,
first fix other errors indicated by DIAGNOSE.
If DIAGNOSE was run with any entry qualification, such
as INCLUDE or EXCLUDE, this message may be
issued. In this case, the entries which were bypassed
may refer to the listed volume.
If a data set is missing volume information, to recover
the missing volume information, use the DEFINE
command with the RECATALOG option to recatalog the
data set. Then make any candidate volumes available
to the recataloged data set by using the ALTER
command with the ADDVOLUMES parameter.
If the VVDS entry is extraneous, you can delete it using

DELETE NOSCRATCH for the specified VVDS.
IDC11361I
Source: DFSMSdfp
THE FOLLOWING
{INCLUDE|EXCLUDE} ELEMENTS
WERE NOT ENCOUNTERED
Explanation: The names which follow the messages

were expected to be in the catalog or VVDS as they
were specified in the INCLUDE or EXCLUDE list. These
names were not encountered during processing.
System Action: DIAGNOSE considered this an
attention condition and continued to process the catalog
or VVDS.
Application Programmer Response: An analysis of
466

IDC11367I
THE FOLLOWING VVDS REFERENCED

CATALOGS WERE NOT
ENCOUNTERED
Explanation: The list of catalog names which follow

are referenced by the VVDS as catalog entries but
these names were not found in any entries for scanned
VVDSs. There may be missing or damaged VVDS
entries. This may be a normal condition if all data sets
on the volumes which are cataloged in the specified

catalog have been converted or deleted, or if
DIAGNOSE was run with any entry qualification, such
as INCLUDE or EXCLUDE.
Application Programmer Response: Run
DIAGNOSE ICFCATALOG for the extraneous catalog
name. Determine whether data sets are missing from
the volume. If no data sets are missing, use the
DELETE command with the NOSCRATCH option to
remove the VVDS entry from the extraneous catalog.
If any data sets are missing from the volume, recover
the data sets in their entirety. Multivolume data sets
require that all volumes are recovered together, not just
the affected volume.
Source: DFSMSdfp
IDC11373I
THE FOLLOWING COMPARE

ELEMENTS WERE NOT
ENCOUNTERED
Explanation: The names that follow this message

were given in the comparison list but were not
encountered during processing. The entries may no
longer be in the catalog or VVDS.
attention condition and continues processing the catalog
or VVDS.
spelling carefully. If you are using DD statements to
define catalogs, ensure that a DSNAME has been
coded. If a volume serial number has been coded,
ensure that it is correct. If the command is correctly
coded, take the following steps:
v For a BCS, use LISTCAT to verify the catalog
contains an entry for the listed VVDS. Determine
whether any data sets in the catalog are missing
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
not missing, change the DIAGNOSE command to
remove the reference to the missing compare name;
there is no error.
v For a VVDS, determine whether any VVDS entries
should be referencing the named catalog.
If the entry is in the catalog but DIAGNOSE cannot
locate it, contact your service representative.
Source: DFSMSdfp
IDC11374I
THESE ADDITIONAL CATALOG

REFERENCED VOLUMES WERE
ENCOUNTERED volume-serial-numbers
Explanation: The listed volume serial numbers

volume-serial-numbers are referenced by catalog entries
but these volume serial numbers were not found as
VVDS entries. This may indicate entries are referencing
volumes for which the catalog has no record. There
should be a SYS1.VVDS.Vvolser entry for each volume
referenced by VSAM entries in the catalog, except
where the SYS1.VVDS.Vvolser is created by EOV.
Vvolser is the volume serial number of the volume.
is an attention and may signal entries which are missing
or damaged. To add an entry for the missing VVDS to
the catalog, using DEFINE RECATALOG on the VVDS.
If a VSAM data set incorrectly references the volume,
remove the reference from the data set entry with
ALTER REMOVEVOLUMES.
Source: DFSMSdfp
IDC11375I
THESE ADDITIONAL VVDS

REFERENCED CATALOGS WERE
ENCOUNTERED
Explanation: The catalog names listed are referenced

by VVDS entries but these names were not found as
catalog entries in the VVDS. The VVDS contains the
names of all referenced catalogs in the VVDS control
record (VVCR). Each entry in the VVDS contains the
name of the catalog in which the component is
cataloged. There were catalog names in VVDS entries
which were not also in the VVCR.
This message applies only for volumes and catalogs
with non-SMS-managed data sets.
System Action: Consider this an attention condition,
is an attention and may signal entries which are missing
or damaged. Either the VVCR entry for the catalog is
missing, or a VVDS record is referring to a catalog
incorrectly. Run DIAGNOSE ICFCATALOG against each
catalog listed, and compare each to the VVDS.
To add the catalog name to the VVCR, define a dummy
data set on the volume by using the DEFINE command,
and specify the catalog name needed in the CATALOG
parameter. Then delete the dummy data set by using
the DELETE command. The catalog name remains in
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
Source: DFSMSdfp
IDC11441I
ENTRY WAS INTERRUPTED DURING A

PREVIOUS PROCESS
Explanation: This ICF catalog entry was previously

interrupted before completion of a delete or
update-extend function.
System Action: LISTCAT processing continues listing
the entrys remaining information normally.
Application Programmer Response: It may be
desirable to run the access method services
DIAGNOSE command. See DFSMS/MVS Access
Method Services for ICF for details on DIAGNOSE.
NVR/VVR NOW POINTS TO TARGET

CATALOG
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
processing must be done under the target catalog.
Source: DFSMSdfp
IDC11560I
NO PINNED TRACKS EXIST FOR

VOLUME volser
Explanation: There are no pinned tracks on the

specified volume. Two requests can result in the
issuance of this message:

v a LISTDATA PINNED request for a PINNED TRACK

REPORT.
Source: DFSMSdfp
volser
IDC11462I
REQUESTED RANGE END BEYOND

END OF DATA SET
Explanation: A PRINT or REPRO command was

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.
System Action: The command continues processing
with a condition code of 4.
Application Programmer Response: None if the
default is correct. Otherwise, correct the range value
and rerun the command.
Source: DFSMSdfp
IDC11465I
DELIMITERS WERE SPECIFIED, BUT

NO RECORDS WERE PROCESSED.
Explanation: An IDCAMS REPRO was executed with

delimiters specified, however due to an error in their
specification no records were processed.
v a SETCACHE DISCARDPINNED request to

invalidate all cache fast write and DASD fast write
data for the device.
The volume serial number specified in the

LISTDATA/SETCACHE command.

Source: DFSMSdfp
IDC11563I
INCOMPLETE {COUNTS | STATUS}

FOR THIS VOLUME, SD OFFLINE
Explanation: There is no path to the other storage

director for 3880 Model 21 or 23, COUNTS and/or
STATUS REPORTS.
System Action: The report for the available storage
director is printed. The other half of the report for Model
21 COUNTS or STATUS, or Model 23 STATUS is not
printed. The Model 23 COUNTS report depicts the
performance statistics for both storage directors in the
same report; therefore the offline storage director will
have zero counts.
Source: DFSMSdfp
System Action: Job Completes condition code 4

User Response: Correct the delimiters and resubmit.
Source: IDCAMS
468
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
duplex pair was issued, and the requested devices were
not on separate storage facilities. This attention is also
issued when the devices are on separate 2-path strings
having the same string address in a DLSE mode
subsystem with intermixed 2-path and 4-path DASD

strings. Separate storage facilities are recommended to
avoid single points of failure when duplexing. The
SETCACHE commands that could cause this attention
message to be generated are:
v SETSECONDARY, if the prospective primary and
secondary devices are on the same storage facility.
v REESTABLISHDUPLEX, if the primary device and
the requested alternate device are on the same
storage facility.
to continue ending the duplex pair.

Model 6 Storage Control, see IBM 3990 Operations and
Recovery Guide. for detailed recovery actions.
Application Programmer Response: If a true copy
was required, another method for the copy will have to
be used.
Source: DFSMSdfp

System Programmer Response: See the IBM 3990
Operations and Recovery Guide. manual for additional
recovery comments for this message.
Source: DFSMSdfp
IDC11614I
AUTHORIZATION CHECKING HAS

BEEN BYPASSED. VOLSER NOT
AVAILABLE FOR THE OFFLINE
DEVICE.
Explanation: An IDCAMS command requiring volume

authorization checking was issued. That checking was
not possible because the volume serial could not be
obtained from the offline device. The DASDVOL ALTER
authorization checking for the volume is bypassed and
processing of the command continues. This message
can result from the following commands:
v SETCACHE SETSECONDARY, for the secondary
volume
v SETCACHE REESTABLISHDUPLEX, for the
alternate volume
Source: DFSMSdfp
IDC11651I
A DUPLICATE ENTRY WAS FOUND

FOR ALIAS alias
Explanation: A duplicate name was found in the

master catalog while attempting to define an entry into it
for the IMPORT of an integrated catalog facility catalog.
alias
The name of the alias.
System Action: Processing continues with the next

alias to be defined.
Application Programmer Response: None, but you
may want to verify that the alias names, existing after
the IMPORT is complete, are still valid.
Source: DFSMSdfp
IDC11656I
ALIAS KEY WORD IGNORED WITH

VSAM MASTER CATALOGS
Explanation: The system is operating under a VSAM

master catalog and the keyword ALIAS was coded.
Aliases on the portable data set for integrated catalog
facility user catalogs cataloged in a VSAM master
catalog are not defined.
System Action: Aliases that may exist on the portable

data set are ignored. Processing continues.
IDC11617I
RESETTOSIMPLEX COMMAND IN
PROCESS. HOWEVER, DASD FAST
WRITE COULD NOT BE DEACTIVATED.
COPIES MAY NOT BE IDENTICAL.
Explanation: If an active duplex pair is ended with

DASD fast write active, the resulting simplex volumes
may not be true copies. When ending a duplex pair,
IDCAMS issues a channel command to deactivate
DASD fast write to allow for destage of any DASD fast
write data. This attention message is issued when the
attempt to deactivate DASD fast write failed (probably
because DASD fast write was in pending state from
another job). If DASD fast write was on prior to issuing
the RESETTOSIMPLEX channel command, then DASD
fast write would have been reactivated for the primary of
the ended pair.
System Action: Processing continues with the attempt
Source: DFSMSdfp
IDC11659I
INSUFFICIENT WORKAREA PROVIDED

TO RETURN FULL VOLUME LIST
Explanation: A problem program issued a VOLLIST

request, but didnt provide a large enough workarea to
contain the response to that request.
Application Programmer Response: Make sure the
workarea you provide is large enough to list all volume
serial names (VOLSERs) necessary to satisfy the
VOLLIST request. In DFSMS/MVS Access Method
Services for ICF refer to the section about invoking
access method services from a problem program; that
469
section describes VOLLIST requirements.

Source: DFSMSdfp
IDC11704I
INDEX KEYS ARE NOT IN SEQUENCE
Explanation: The present key has a smaller value

than the previously tested key.
IDC11700I
System Action: The relevant control interval is

dumped, and processing continues.
HIGH-LEVEL INDEX STRUCTURE IS

NOT UNIQUE
Explanation: A single level index structure is

expected, but a horizontal pointer linking one control
interval to another is found.
System Action: The control interval is dumped, and
Application Programmer Response: See summary
messages for final analysis. Issue a VERIFY command
and reissue the EXAMINE command.
Source: DFSMSdfp
IDC11701I
STRUCTURAL PROBLEM FOUND IN

INDEX
Explanation: A single level index structure, the

sequence set, is expected, but a control interval
assigned to a higher level is found.
messages for final analysis.
Source: DFSMSdfp
IDC11702I
BASE RBA IS NOT ZERO
Explanation: A base relative byte address of zero (0)

is expected for the first sequence set control interval,
but a nonzero value is found.
Source: DFSMSdfp
IDC11703I
DUPLICATE KEYS IN INDEX
Explanation: The present and previous keys of the

current index level are identical.
Source: DFSMSdfp
470

Source: DFSMSdfp
IDC11705I
INDEX RECORD CONTAINS

DUPLICATE INDEX POINTERS
pointer-value
Explanation: An index control interval has duplicate

vertical pointers. The pointer value is displayed in HEX.
pointer-value
The value of the pointer, in hexadecimal.
Source: DFSMSdfp
IDC11706I
MISSING SEQUENCE SET ENTRIES
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
represents.
System Action: Supportive information is displayed
and processing continues.
Source: DFSMSdfp
IDC11707I
DUPLICATE INDEX POINTERS FOUND

IN SEQUENCE SET
Explanation: A sequence set control interval has

duplicate data or free control interval pointers.
System Action: The sequence set control interval is
Source: DFSMSdfp
IDC11708I
HIGH-USED INDEX RBA DOES NOT

EQUAL HIGHEST RBA FOUND
Explanation: The largest relative byte address

encountered while processing the index does not equal
the index high-used relative byte address less index
control interval size.
System Action: One or more supportive messages
display the addresses found, and processing continues.
Source: DFSMSdfp
IDC11709I
DATA HIGH-USED RBA IS GREATER

THAN HIGH-ALLOCATED RBA
Explanation: The data component high-used relative

byte address is greater than the high-allocated relative
byte address.
System Action: Supportive messages display
pertinent data, and processing continues.
IDC11712I
DATA HIGH-ALLOCATED RBA IS NOT

A MULTIPLE OF CI SIZE
Explanation: The high-allocated relative byte address

is not an integral multiple of the control interval size.
Source: DFSMSdfp
IDC11714I
UNUSED INDEX SPACE IS NOT A

MULTIPLE OF CI SIZE
Explanation: The difference between the

high-allocated and high-used relative byte address for
an extent is not an integral multiple of the control
interval size.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11715I
IDC11710I
DATA HIGH-USED RBA IS NOT A

MULTIPLE OF CI SIZE
Explanation: The data component high-used relative

byte address is not an integral multiple of the control
interval size.
INDEX HIGH-USED RBA IS NOT A

MULTIPLE OF CI SIZE
Explanation: The index component high-used relative

byte address is not an integral multiple of the control
interval size.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11716I
IDC11711I
INDEX CONTROL INTERVAL COUNT

ERROR
Explanation: The arithmetic count of all index control

intervals less all unused index control intervals does not
equal the actual number of index control intervals read.
INDEX HIGH-ALLOCATED RBA IS NOT

A MULTIPLE OF CI SIZE
Explanation: The high-allocated relative byte address

for the index component is not an integral multiple of
the control interval size.
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

data, and processing continues.
IDC11722I
DUPLICATE INDEX BASE RBA FOUND
Explanation: Two sequence set control intervals have

identical base relative byte addresses.
Source: DFSMSdfp
System Action: Supportive messages are displayed,

IDC11718I

DATA COMPONENT HIGH-USED RBA

IS NOT EQUAL TO CA SIZE
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.
Source: DFSMSdfp
IDC11719I
MISSING CI WITHIN INDEX LEVEL
Explanation: An index control interval is not

referenced in the index horizontal pointer chain. The
next higher level indicates it should exist.
Source: DFSMSdfp
IDC11723I
Explanation: A sequence set base relative byte

address is not an integral multiple of the control area
size.
Source: DFSMSdfp
IDC11724I

BASE RBA NOT ON CA BOUNDARY
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

component of AMDSB is zero.
Source: DFSMSdfp
IDC11721I
OUT OF RANGE INDEX POINTER

WITHIN SEQUENCE SET
Explanation: A data or free control interval pointer in a

sequence set control interval was found with a value
greater than the maximum allowed.
System Action: The sequence set control interval is
Source: DFSMSdfp
Source: DFSMSdfp
IDC11725I
SEQUENCE SET RBA INCONSISTENT

WITH VSAM-MAINTAINED RBA
Explanation: The first sequence set control interval

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
index component.
System Action: Supportive messages supply pertinent
data, and processing continues.
Source: DFSMSdfp
IDC11726I
CI ON CURRENT LEVEL NOT POINTED

TO BY NEXT LEVEL
Explanation: A control interval on the current index

level is not pointed to by the next higher index level.
472

Source: DFSMSdfp
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
IDC11728I
DATA FOUND IN EMPTY CI
Explanation: The free area of an empty control

interval contains data.
IDC11732I
Explanation: The free space of a data component

control interval contains residual data.
Source: DFSMSdfp
IDC11733I
UNSPANNED RECORD FOUND WHEN

SPANNED RECORD SEGMENT
EXPECTED
Explanation: The first segment of a spanned record

has been read, but the current record is not identified as
being in an intermediate or last segment.
System Action: The index and data control intervals
are dumped, and processing continues.
DATA COMPONENT KEY SEQUENCE

ERROR
Explanation: A key sequence error exists in or

between data control intervals.
System Action: The previous key and the current
data control interval are dumped, and processing
continues.
Source: DFSMSdfp
IDC11734I
Source: DFSMSdfp
IDC11730I
DATA FOUND IN FREE AREA OF DATA

CI
SEQUENCE SET AND DATA CI KEY

SEQUENCE MISMATCH
Explanation: The data key is not within the range of

keys valid for this data control interval. It must be
greater than the index key of the previous data control
interval, and less than or equal to the index key for this
data control interval.
System Action: The previous and current index keys
and the current data control interval are dumped, and
Source: DFSMSdfp
Source: DFSMSdfp
IDC11735I
IDC11731I
SPANNED RECORD UPDATE NUMBER

ERROR
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.
EMPTY CI ENCOUNTERED WHILE

PROCESSING SPANNED RECORDS
Explanation: An empty control interval was read, but

a spanned record segment was expected.
System Action: The relevant index and data control
intervals are dumped, and processing continues.
Source: DFSMSdfp
Source: DFSMSdfp
473
IDC11736I
ERROR IN RDF
Explanation: The record definition field flag byte

contains incorrect bits, or, for an index control interval,
the length field is incorrect.
Source: DFSMSdfp
IDC11737I
A RIGHT RDF IS CODED AS

CONTAINING THE NUMBER OF
RECORDS IN CI
control interval definition field or overlaps the leftmost

record definition field.
dumped, processing continues.
Source: DFSMSdfp
IDC11741I
DUPLICATE CONSECUTIVE KEYS

FOUND
Explanation: Two consecutive keys are identical.

System Action: The current control interval is
Explanation: A right record definition field is coded

with the attributes of a left record definition field.


Source: DFSMSdfp

IDC11742I
Source: DFSMSdfp
Explanation: The index contains too many sequence

set control intervals.
IDC11738I

A LEFT RDF IS CODED AS

CONTAINING THE LENGTH OF
RECORDS IN CI
Explanation: A left record definition field is coded with

the attributes of a right record definition field.
MORE SEQUENCE SET CONTROL

INTERVALS FOUND THAN EXPECTED

Source: DFSMSdfp
IDC11743I
SOFTWARE EOF FOUND IN INDEX

SEQUENCE SET CI
Source: DFSMSdfp
Explanation: An index sequence set control interval

contains a software end-of-file.
IDC11739I

SPANNED RECORD SEGMENT

SEQUENCE ERROR
Explanation: A record coded as a first segment is

found, but an intermediate or last segment is expected,
or an intermediate or last segment is found when no
first segment was read.

Source: DFSMSdfp

IDC11744I

Explanation: The last data control interval does not

contain a software end-of-file.
Source: DFSMSdfp

IDC11740I

DATA RECORDS OVERLAP FREE

SPACE OR CONTROL INFORMATION
Explanation: The length of the records in the current

control interval exceeds the length specified in the
474
SOFTWARE EOF NOT FOUND IN THE

HIGH-USED RBA CI
Source: DFSMSdfp
IDC11745I
ERROR IN CIDF
IDC11758I
SOFTWARE EOF FOUND IN INDEX CI
Explanation: An error has been found in the control

information definition field of the current control interval.
Explanation: An index control interval contains a

software end-of-file.




Source: DFSMSdfp
Source: DFSMSdfp
IDC11751I
IDC11760I
INCONSISTENCY EXISTS BETWEEN

CODING OF LEFT AND RIGHT RDF
Explanation: The control information of a left record

definition field does not agree with the control
information of a right record definition field.
Source: DFSMSdfp
IDC11755I
LENGTH OF FREE SPACE NOT EQUAL

TO VALUE IN CIDF
Explanation: The length of the free space in a data

control interval does not equal the value in the control
interval definition field.
CI SIZE INVALID
Explanation: The control interval size was not n times

512 bytes, where n is an integer one to sixteen.
System Action: The control interval size is displayed,
Source: DFSMSdfp
IDC11761I
DATA KEY POSITION OR LENGTH

ERROR
Explanation: The calculated ending position of the key

is greater than the maximum record length, the
maximum spanned record length, or the length of the
record being processed.
System Action: The control interval is dumped, if
applicable, and processing continues.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11762I
IDC11756I
SOFTWARE EOF FOUND IN FREE CI
LENGTH OF VERTICAL POINTER

INVALID
Explanation: A free data control interval contains a

Explanation: The index vertical pointer length is not 1,

2, or 3 bytes.



Source: DFSMSdfp
Source: DFSMSdfp
IDC11763I
IDC11757I
SOFTWARE EOF FOUND IN DATA CI
Explanation: A data control interval contains a

Source: DFSMSdfp
RBA OF INDEX CI GREATER THAN OR

EQUAL TO HIGH-USED RBA
Explanation: The relative byte address of an index

control interval is greater than or equal to the index
high-used relative byte address.
System Action: RBAs are displayed, and processing
continues.
475
Source: DFSMSdfp
IDC11764I
NUMBER OF CONTROL INTERVALS IN

CA NOT GREATER THAN ZERO
IDC11769I
MORE INDEX POINTERS THAN

EXPECTED
Explanation: The number of control intervals per

control area found in AMDSB is zero.
Explanation: More vertical, horizontal, or base relative

byte address pointers have been found while
processing an index level than should exist on that
level.


Source: DFSMSdfp
Source: DFSMSdfp
IDC11765I
IDC11770I
DATA HIGH-USED RBA IS NOT A

MULTIPLE OF CA SIZE
Explanation: The data high-used relative byte address

is not an integral multiple of the control area size.
Source: DFSMSdfp
IDC11766I
ERROR IN INDEX RECORD
Explanation: A field in the index header or entries

contain incorrect data.
System Action: The index control interval is dumped,
Source: DFSMSdfp
INDEX RECORD HORIZONTAL

POINTER POINTS TO ITSELF
Explanation: An index control interval contains a

horizontal pointer specifying the relative byte address of
the control interval itself.
Source: DFSMSdfp
IDC11771I
INVALID RBA GENERATED
Explanation: An incorrect relative byte address has

been generated from index component data.
Source: DFSMSdfp
IDC11767I
DATA HIGH-ALLOCATED RBA IS NOT

A MULTIPLE OF CA SIZE
Explanation: The data high-allocated relative byte

address is not an integral multiple of the control area
size.
IDC11772I
HORIZONTAL POINTER CHAIN LOOP
Explanation: A long loop has been discovered in the

horizontal pointer chain in an index level.
Source: DFSMSdfp
Source: DFSMSdfp
IDC11808I
IDC11768I
CI SPLIT IN PROGRESS
Explanation: A control interval split

in-progress-indicator was encountered.
Explanation: During data collection for the specified

data set, errors were detected.

dsname
Source: DFSMSdfp
volser
476
ERRORS WERE DETECTED FOR

dsname ON VOLUME volser ERROR
BYTE WAS Xnn
The data set name.

nn
The hexadecimal error byte.
IDC11816I

Application Programmer Response: See the field
DCDERROR in that data sets D record for the
specific failure.
Source: DFSMSdfp
IDC11812I
MESSAGE PROCESSING SUSPENDED,

ERROR LIMIT EXCEEDED
Explanation: The number of error messages printed

exceeds the number specified in the error limit
parameter.
Application Programmer Response: If all error
messages are required, increase the error limit or do
not specify the error limit parameter.
DYNAMIC ALLOCATION FAILED FOR

VOLUME volser
Explanation: Volume volser could not be dynamically

allocated by the system. Severity is 4.
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.
Application Programmer Response: If the error
recurs and the program is not in error, look at the
messages in the job log for more information. Search
the JCL, the SYSOUT output for the job, and printed
IDC11818I
type INFORMATION NOT FOUND
Explanation: This message indicates that a requested

definition was not found or unavailable.
type

The type of definition not found:
Source: DFSMSdfp
v CACHE SET NAME
v STORAGE CLASS CONSTRUCT

v MANAGEMENT CLASS CONSTRUCT
v STORAGE GROUP CONSTRUCT
v SMS VOLUME
v BASE CONFIGURATION
v AGGREGATE GROUP CONSTRUCT
IDC11813I
ERRORS WERE DETECTED FOR volser

ERROR BYTE WAS Xnn
Explanation: During volume information processing,

errors were detected for the specified volser.
volser
nn
The error byte.

Application Programmer Response: See the field
DCVERROR in that volsers V record for the specific
error.
v OPTICAL DRIVE
v OPTICAL LIBRARY
v ACS ROUTINE
Note: CACHE SET NAME in this context refers to
a VSAM RLS cache set. See OS/390
DFSMSdfp Storage Administration
Reference.
System Programmer Response: None, the message
is informational only.
Source: DFSMSdfp
Detecting Module: IDCDC03
IDC11819I
DEVICE PENDING OFFLINE - NO

RECORDS PROCESSED FOR (volser)
Explanation: The specified volume is offline and no

data can be processed for this volume.
Source: DFSMSdfp
477

the next volume.
Source: DFSMSdfp
IDC11860I
NO DBCS CHARACTERS INDICATED

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
the DBCS characters in the source data set. However,
the data set does not indicate the presence of DBCS
characters (no SO or SI characters were located).
is informational. However, you may want to recheck the
specification of the data set name to ensure that the
proper data set was processed, or specify
INSERTSHIFT values to insert SO and SI characters to
allow the detection of DBCS characters.
Source: DFSMSdfp
IDC11861I
INVALID DBCS CHARACTER IN

RECORD number AT OFFSET offset
IDC21009I
entryname, type DOES NOT EXIST ON

VOLUME volser
Explanation: A multivolume data set existed on a

volume prior to reset. The data set is not on the volume
and will be marked unusable.
volser
entryname
type
The type of record. The values are

defined under message IDC21045I.

Application Programmer Response: The data set on
valid volumes may be removed via REPRO prior to
deleting the data set. The data set cannot be opened
for output.
Source: DFSMSdfp
IDCRS03
IDC21020I
UNABLE TO ALLOCATE volser
Explanation: INSERTSHIFT or INSERTALL was

specified on an access method services (AMS) PRINT
or REPRO copy of a data set. AMS, while criteria
checking the DBCS characters in the source data set,
detected an incorrect DBCS character.
Explanation: An attempt to allocate a volume for

RESETCAT failed. See message IDC3905I.
number The record number.
Application Programmer Response: Make the

volume indicated available to RESETCAT via
CRAFILES and reissue the command.
offset
The offset indicated.
volser
Source: DFSMSdfp

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
will be replaced with DBCS periods.
Source: DFSMSdfp
IDC11902I
parameter-name SET TO DEFAULT OF

default-value
Explanation: The system accepted a default value for

the specified parameter.
command.
Source: DFSMSdfp
IDC21024I
entryname, type CONTAINS AN INVALID

ALIAS CHAIN
Explanation: The alias chain for a user catalog or

non-VSAM entry is incorrect.
entryname
type
The type of record. The values are defined

under message IDC21045I.

Application Programmer Response: The alias chain
will be corrected. A LISTCAT should be run to determine
which aliases may be lost.
478

catalog.
Source: DFSMSdfp
IDC21027I
{CRA|CATALOG} SPACE NOT VOLUME

volser NOT OWNED BY CATALOG
Explanation: The CRA extents or catalog extents

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
been recovered; however, the generation data set string
associated with this base has been altered to reflect
only those data set descriptions which can be located.
entryname
type
The type of record. The values of type

IDC21045I.

Application Programmer Response: Perform a
LISTCAT for the GDG base and determine which
entries no longer exist. Though entries do not exist,
RESETCAT has not altered/scratched the data sets. If
the resulting GDG data set string is in error, delete the
GDG and redefine it; then catalog the correct
generations by name.
volser

Application Programmer Response: The resultant
catalog is vulnerable because there are conflicting
space ownership requests between the VTOC and the
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
that they contain reasonable data. Then add ownership
to the volume, and then use import to reestablish the
data sets.
Source: DFSMSdfp
IDC21030I
entryname, type HAS INVALID SPACE

DESCRIPTION FOR volser
Explanation: The entry noted claims space on

volume. That space is not allocated to that entry.
Source: DFSMSdfp
entryname
type

IDC21045I.
volser
IDC21026I
entryname, type DELETED
Explanation: A previous message indicates an error

which resulted in this entry being deleted from the
catalog.
entryname
type

IDC21045I.

Application Programmer Response: The entry noted
was deleted. Any space that it occupied has been
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
instance, if a cluster is deleted, all paths, alternate
indexes, and the upgrade set are also deleted.
Source: DFSMSdfp

Application Programmer Response: The data set is
marked unusable and the volume description
invalidatable. LISTCAT may be run to determine the
incorrect extents. Delete the data set. Redefine it and
reload it.
catalog.
Source: DFSMSdfp
IDC21032I
type DELETED FROM entryname, type
Explanation: An object of the type specified was

defined over the entry named. However, the records
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
entryname
type

IDC21045I.

Application Programmer Response: Perform a
LISTCAT for the entryname noted, and try to determine
which entity was deleted and redefine it.
Source: DFSMSdfp
Detecting Module: IDCRS02, IDCRS03
IDC21034I
SPACE MAP ERROR FOR volser
Explanation: The space map, which indicates which

space is available for suballocation on a volume, is not
the correct length in the catalog. This may be due to a
damaged catalog or CRA. This situation is not
correctable by RESETCAT.
volser

Application Programmer Response: All data sets on
the volume noted may be EXPORTed, the volume and
all VSAM space should be deleted. Redefine the
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.
type

IDC21045I.
avol
The volume.

Application Programmer Response: If the renamed
entry was a non-VSAM entry, the associated format-1
DSCB has not been renamed. The entry may be
deleted (NOSCRATCH), the conflict resolved and the
entry redefined.
If a GDG base or GDG set has been renamed, the base
and its associated data sets should be deleted
(NOSCRATCH) and redefined after resolving the
conflict.
If a catalog connector was renamed, that catalog may
be EXPORTed (using the DISCONNECT option), the
conflict resolved, and the catalog connector entry
IMPORTed.
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
inaccessible via this new name, because the Format 1
DSCB name does not correspond to the catalog name.
The catalog entry is accessible.
Source: DFSMSdfp
IDC21046I
Source: DFSMSdfp
IDC21045I
entryname, type avol RENAMED

entryname
Explanation: An attempt was made to reset an object

that bears the same name as some other object in the
catalog. One of the objects was chosen to be renamed
as noted in the message.
The types of entries are as follows:
A -- non-VSAM
B -- GDG base
C -- cluster
D -- data
G -- alternate index
I -- index
R -- path
U -- user catalog
X -- alias
entryname
480
entryname, type ON cravol RENAMED

entryname
Explanation: An attempt was made to reset a unique

object into a catalog which contains an object of the
same name. The unique object was renamed along with
its corresponding format-1 DSCB on all volumes.
entryname
type

IDC21045I.
cravol
The catalog recovery area (CRA)

volume.

Application Programmer Response: The object
noted is accessible. If desired, the conflicting named
object in the catalog may be moved or renamed, and
this object renamed via ALTER back to its former name.
Source: DFSMSdfp
IDC21047I
entryname, type ON cravol MAY NOT BE

ACCESSED BY NAME
Explanation: An attempt was made to reset a unique

object into a catalog which contained an object of the
same name. RESETCAT attempted to rename the
unique object, but failed either because all volumes
were not available (see message IDC3906I) or the
RENAME failed.
Remaining dump requests are processed.

sector range, specifying a low sector value that is lower
than the high sector value. Resubmit the command.
Source: DFSMSdfp
Detecting Module: IDCDU01
INVALID SSID nnnn
IDC21103I
entryname
type

IDC21045I.
Explanation: The SSID value was incorrectly specified

for a Staging Adapter. SSIDs for Staging Adapters must
be of the form X'08x0', where x is in the range 0
through F.
cravol
The catalog recovery area (CRA)

volume.

Application Programmer Response: The object
noted may be accessed via the cluster name, but not
the data or index name noted. The data set may be
EXPORTed, and then IMPORTed after resolving the
name conflict in order to gain accessibility via the date
or index component name.
Source: DFSMSdfp
nnnn
The SSID value.
System Action: Requests for this SSID are bypassed.

SSID and rerun the command.
Source: DFSMSdfp
IDC21104I

IDC21100I
UNABLE TO DUMP MSC MAIN

STORAGE
UNABLE TO DUMP SA nnnn MAIN

STORAGE
Explanation: An error occurred while the main storage

of the Staging Adapter was being read. The main
storage for that Staging Adapter cannot be dumped.
There is a preceding message that indicates the MSSC
reason code associated with the error.
Explanation: An error occurred while the Mass

Storage Control main storage was being read. The
Mass Storage Control main storage cannot be dumped.
There is a preceding message that indicates the MSSC
reason code associated with the error.
nnnn
System Action: This dump request is bypassed.


Application Programmer Response: Take the action

associated with the MSSC reason code in the preceding
message.

message.
Source: DFSMSdfp
Source: DFSMSdfp
IDC21101I
IDC21105I
LOWSECTOR X'll' IS GREATER THAN

HIGHSECTOR X'hh'.

The SSID value.
UNABLE TO DUMP SA nnnn

EXTENDED STORAGE
Explanation: An error occurred while the extended

storage of the Staging Adapter was being read. The
extended storage for that Staging Adapter cannot be
dumped. There is a preceding message that indicates
the MSSC reason code associated with the error.
ll
The low sector value.
hh
The high sector value.
nnnn
Explanation: A sector range was specified incorrectly.

The low sector value was greater than the high sector
value.
The SSID value.
481
Source: DFSMSdfp

message.

IDC21143I
Source: DFSMSdfp
IDC21109I
ONE OR MORE REQUESTED

EXTENDED SECTORS ARE NOT
AVAILABLE
Explanation: One or more of the sectors requested for

a Staging Adapter extended storage dump are incorrect
in this configuration.
System Action: The incorrect sectors are bypassed,
but all valid requested sectors are dumped.
values for future dumps.
Source: DFSMSdfp
** INCOMPLETE READ REPORT

PRODUCED, ERROR AT X LOCATION
xxx
Explanation: The AUDITMSS command is unable to

read the labels of all the requested cartridges.
xxx
The X coordinate of the cell where the error

occurred.

command for the values not processed (all the cells with
X coordinate equal to or greater xxx), after corrective
action was taken as indicated in the primary message.
Source: DFSMSdfp
Detecting Module: IDCCAU03

IDC21144I
IDC21125I
SA 8x0 TABLES CANNOT BE READ:

SA IS OFFLINE OR SUU.
Explanation: While interrogating the MSC (Mass

Storage Control) main sectors 7C-7F, the staging
adapter UCB for staging adapter 8 x 0 showed that
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
unusable) is valid and online but not ready.
System Action: The request is bypassed. All
processing regarding this staging adapter is bypassed,
and the remaining requests are attempted.
Application Programmer Response: If the staging
adapter is offline, vary it online. If it is SUU, see
Problem Determination. Resolve the equipment problem
and then rerun the job.
LOW XRANGE lowx IS GREATER THAN

HIGH XRANGE highx
Explanation: The low value in the XRANGES

parameter is greater than the high value. The values
must be in the range 150 through 247, and the low
value must not be greater than the high value.
lowx
The low range.
highx
The high range.
System Action: The incorrect XRANGE is ignored,

specify the incorrect range and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCCAU03
Source: DFSMSdfp
IDC21147I
IDC21127I

check the status of all the requested cells. The X
coordinates of the range of cells that could not be
checked are indicated by n1 n2.
UNABLE TO READ STAGING ADAPTER

STORAGE
Explanation: An error occurred while the system was

reading staging adapter main storage. Staging adapter
main storage cannot be dumped. A message indicating
the MSSC (Mass Storage System Communicator)
reason code for the error appears prior to this message.
System Action: The request is bypassed, and the
remaining requests are attempted.
Application Programmer Response: Perform the
response indicated in the description of the message
that identified the MSSC reason code.
482
** INCOMPLETE AUDIT REPORT

PRODUCED, ERROR WITHIN X RANGE

command for the values not processed (all the cells
within the range n1 through n2), after corrective action
was taken as indicated in the primary message.
Source: DFSMSdfp
IDC21276I
QCB FOR VOLUME volser HAS BEEN

MARKED IN ERROR
Explanation: The QCB (queue control block) for the

active, general-use volume has been marked in error.
The volume being marked in error is valid only if the
MSC (mass storage controller) is at EC level 737573 or
later.
volser
System Action: The system ends with a message that

indicates the severity of the error.
NULLIFYC command with the NULLIFYQCBINERROR
parameter to clear the error flag in the base volume
record. You must also specify the ACTIVE and
VOLUME parameters.
Source: DFSMSdfp

IDC21364I
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
BCS, or an RBA for a VVDS. In most cases, this
message is followed by an IDC21365I message that
displays the record in error. An IDC21363I message
summarizes all entries with errors at the conclusion of
the DIAGNOSE run.
entry
The entry name. The entry name is

followed by a character which
indicates the entry type. See OS/390
DFSMS: Managing Catalogs for an
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.
offset
The offset into the record at which the

error was found.
reason-code
Detecting Module: IDCC001

IDC21363I
THE FOLLOWING ENTRIES HAD

ERRORS
Explanation: This message provides a summary of

the errors found by the DIAGNOSE FSR. Each entry
name is followed by a reason code indicating the
specific error for that entry. For example:
ERROR DETECTED BY DIAGNOSE:

{VVDS|ICFCAT} ENTRY: entry RECORD:
rec OFFSET: offset REASON:
reason-code
Code
Explanation
CELL LENGTH IS ZERO

Each record is composed of
cells, each of which has a
cell type and a cell length.
The indicated entry has a cell
length of zero, which is an
error. This error may be
caused by incorrect
positioning (caused by some
other error) or the length may
actually be zero.
SYS1.VVDS.VCATALG (D) - REASON CODE: 17

Here SYS1.VVDS.VCATALG is the entry name and 17
is the reason code. (D) is the entry type.
When the error was initially encountered, a specific
message was printed and a record dump may have
been done. The IDC21363I message provides a
summary of the entries which had errors. For VSAM
data sets, the entry name may be a cluster, component
(data or index), path or true name entry. For non-VSAM
entries, the entry name may be an entry or an alias.
System Action: DIAGNOSE ended processing of that
particular entry and moved along to another entry.
Application Programmer Response: Decide on the
seriousness of the error and correct the error if need be.
The reason codes set by DIAGNOSE are detailed below
under message IDC21364I.
CELL TYPE NOT

RECOGNIZED
Various catalog records can
only contain certain cell
types. The record being
analyzed contained a cell
type that either did not
belong in the record or was
not a legal cell type. This
error may be caused by an
incorrect length in the
preceding cell that resulted in
incorrect positioning.
Source: DFSMSdfp
483
Each record in a BCS or

VVDS has an record type.
The record named has an
invalid type for integrated
catalog facility catalogs.
4
484
12
RECORD LENGTH
INCORRECT
CATLG AND VVDS NAMES

UNEQUAL
There are four name fields in
a VVDS record. The BCS
entry and the VVDS entry do
not have precisely the same
names (length fields must
also be the same) for one of
the following four fields:
v Record name
v Subrecord name
v Component name
v Catalog name
13
VVDS AND VTOC EXTENT

SEQ. NO. UNEQUAL
VTOC sequence numbers
start at 0; VVDS record
sequence numbers start at 1.
The VVDS record number
should always be one greater
than the VTOC number. An
exception to this rule is the
VVR sequence number for
key range data sets.
14
REPEATING CELL NOT

VALID
Although certain cells such
as volume cells can occur
more than once in an entry,
most cells may not. The
indicated cell occurred more
than once, but is a type of
cell that should not.
INCOMPLETE DELETE
DETECTED
The DELETE function did not
execute to completion. This
may indicate existence of
partial record structures in
the BCS.
CELL LENGTHS SUM AND

COMPONENT LENGTH
DISAGREE
The sum of all cell lengths in
a component is not equal to
the component length, which
it should be. Either the
component length is wrong or
one of the cell lengths is
wrong.
11
CELL LENGTH TOO LARGE

A cell length was found that
is inconsistent with
component or record length.
This may describe the cell
being processed or the
preceding cell.
INCOMPLETE EXTEND
DETECTED
The EXTEND function did not
execute to completion. The
named entry was interrupted
in the middle of an
EXTEND/EOV operation.
COMPONENT LENGTH IS
ZERO
VSAM clusters and alternate
indexes, and generation data
groups, have components.
While checking one of these
types of entries, DIAGNOSE
found a component length of
zero. However, component
length should always be
greater than zero.
10
UNEXPECTED RECORD ID
ENCOUNTERED
While processing an entry, a
cell type was encountered
that signalled the beginning
of a new record. This may be
caused by an invalid length
value or a damaged entry.
The record length at the front

of the record is not the same
as the length stored by
VSAM record management.
RECORD TYPE NOT

RECOGNIZED
CATLG AND VVDS VOLFLG

UNEQUAL
VOLFLG is a field in the
VVDS record for the named
entry. This field has prime
and overflow indicators. For
the named entry, the
indicators in the BCS and
VVDS are not equal.
15
CATLG AND VVDS KEYS

UNEQUAL
BCS and VVDS records both
have high and low key fields.
The fields and their lengths

must be equal; they were
not.
16
point back to the non-VSAM

data set record.
22
VVDS AND VTOC

STARTING CCHH
UNEQUAL
VSAM clusters with

components have more than
one catalog entry. The
associated components have
truename entries. A truename
entry was not found,
although there should be
one.
The extents in the VTOC

DSCB and VVDS record
were compared. They were
not equal, although they
should be.
17
VTOC ENTRY NOT FOUND

The data set control block
(DSCB) for the named entry
could not be found in the
VTOC.
18
23
24
VVDS ENTRY NOT FOUND
20
21
25
ASSOCIATION LOOP
FAILURE
For an explanation of
association, see reason
code 20. If an association
can be found, but the
association does not point
back to the original entry, an
association loop failure
exists. For example, if a
non-VSAM data set has an
alias, the alias record should
ALLOCATE OF COMPARE
DATA SET FAILED
The BCS named in the
VVDS record could not be
allocated.
ASSOCIATION NOT FOUND

Certain types of BCS entries
may be paired with other
BCS entries. For example,
catalogs, non-VSAM data
sets, and generation data
sets are paired with their
aliases, and VSAM data sets
are paired with their paths.
This pairing of one record
with another is called an
association. Associations
between entries are
connected by name and are
indicated by an association
cell in an entry. The indicated
association name cannot be
found elsewhere in the BCS.
REQUIRED CELL MISSING,

CELL TYPE type
Depending on the component
or entry type, certain cells
are required. The cell type
indicated is required, but
missing.
CATLG ENTRY NOT FOUND

The BCS should have an
entry for the VVDS record,
but one could not be found.
TRUENAME LOOP FAILURE

The truename entry for a
cluster did not point back to
the cluster record.
There should be a VVDS

entry for this BCS entry, but
one could not be found.
19
TRUENAME NOT FOUND
26
CELL TYPE INVALID IN

CONTEXT
The indicated cell is a valid
cell type, but it is not valid for
the type of entry being
scanned.
27
ENTRY MISSING FROM

GAT CELL
Each generation data set
entry should be reflected in
the generation aging table
(GAT) cell of the generation
data group entry. An entry is
missing.
28
GAT CELL ENTRY NOT

FOUND
Each entry in a GAT cell
represents a generation data
set entry within the current
generation data group
record. No generation data
set could be found for a GAT
cell entry.
29
ENTRY MISSING FROM

REL CELL
485
Each alternate index entry is

reflected in the REL
(relation) cell of the
associated cluster record. An
alternate index entry was
found that was not reflected
in a REL cell.
30
32
34
40
41
42
36
VVDS AND VTOC EXTENT

COUNTS UNEQUAL
43
ASSOCIATION NAME CELL

NOT FOUND
A BCS entry that matches a
VVDS record was found, but
the BCS entry was missing
its required association cell.
486
CATALOG AND VVDS SMS

CONSTRUCTS UNEQUAL
The storage class or
management class names
are not the same in the
catalog and VVDS records.
The catalog and VVDS
records are displayed.
LENGTH OF NAME INVALID

The length of a name cell
should be from 1 to 45
characters long, but is not.
37
NONSYSTEM DEFAULT
CATALOG NAME IN VVDS
The catalog named in the
VVDS record for an
SMS-managed data set is
not the system default
catalog. (The default catalog
is the catalog that is chosen
for a data set when the
catalog search is not being
directed by the user.)
VVDS AND VTOC ENDING

CCHH UNEQUAL
The extent information kept

in the VTOC and VVDS
should agree, but do not.
DUPLICATE VVR/NVRS IN
VVDS
Two VVRs for a VSAM
component, or two NVRs for
a non-VSAM data set, were
found in the VVDS. Both
records are displayed.
The extent information kept

in the VTOC and VVDS
should agree, but do not.
35
COMPONENT CELL NOT

FOUND
The component cell for a
VSAM cluster could not be
found within the clusters
sphere record in the BCS.
INCOMPLETE UPDATE
DETECTED
The current entry was
undergoing a subrecord
update/move operation that
did not complete. This record
or subrecord may be
damaged.
BASE OR COMPONENT
CELL NOT FOUND
Although a truename record
was found for a component,
the associated cluster record
or component cell was not
found.
WRONG RECORD TYPE

A BCS record which matches
a VVDS record was found,
but the BCS record is not a
cluster, truename, or
non-VSAM record.
33
39
OPEN OF COMPARE DATA

SET FAILED
The BCS named in the
VVDS record could not be
opened.
CLUSTER AND EXTENSION

RECS SMS MISMATCH
A VSAM extension record
indicates that the cluster is
SMS-managed, but the
associated cluster record
indicates that the cluster is
not SMS-managed, or vice
versa.
REL CELL ENTRY NOT

FOUND
An entry in a REL (relation)
cell in a cluster record does
not represent an alternate
index entry.
31
38
45
VOLUME CELL NOT FOUND

A volume cell that matches
the volume serial number of
the VVDS was not found.
This may indicate an
orphaned VVDS record or
multiple VVDS records

pointing to the same BCS.
46
VVDS ENTRY NOT FOUND.

ALLOCATION ERROR.
An attempt to allocate the
BCS named in the VVR
failed.
47

DATA SET OPEN ERROR.
An attempt to open the BCS
named in the VVR failed.
48

GET RECORD FAILED.
An attempt to get a
VVR/NVR record that
matches the BCS record
failed.
49
1. Use DELETE NOSCRATCH to remove the sphere

or base record, if it exists.
2. Use DELETE TRUENAME to remove any remaining
association records.
3. Reintroduce the removed entries into the catalog, by
recataloging or redefining them. Introduce
generation data sets into the generation data group
in the proper order.
For VVDS records:

1. Use DELETE NOSCRATCH to remove the entries
from the BCS, if they exist.
2. Use DELETE VVR or NVR to remove the damaged
VVDS records.
3. Restore the data set from a backup copy.
For the following reason codes, recover as indicated:
Code
Action
10
You should recover the data set. Records

existing in a data set prior to the aborted
extend operation should still be accessible if
the data set is opened for input only. You can
retrieve these records by using the REPRO
command. After you retrieve the records, you
can delete or redefine the data set. Then
reinsert the records by using the REPRO
command.
11
You can finish the deletion process by

rerunning the DELETE job.
12
If the catalog names disagree, remove the

entries in the BCS by using the DELETE
command with the NOSCRATCH option. At this
point, if the VVDS record contains the desired
catalog name, you can catalog the data set
into the desired BCS by using the DEFINE
RECATALOG command; otherwise, catalog the
data set into the catalog indicated in the VVDS
record. (It will be necessary to define this
catalog if it does not exist.) Then move the
catalog record to the desired catalog by using
the REPRO MERGECAT command.

SCAN RECORD FAILED.
An attempt to get the specific
VVR/NVR within the CI that
matches the BCS record
failed.
50

GET VVDS FAILED.
An attempt to get the entire
VVDS record that matches
the BCS record failed.
51

SCAN VVDS FAILED.
An attempt to get the specific
VVR/NVR within the VVDS
that matches the BCS record
failed.
52
INVALID VOLSER FOR

MIGRATION CELL.
A Migration Cell was found in
the BCS, but the VOLSER in
the Volume Cell is not equal
to MIGRATE.
53
If the names that disagree are not catalog

names, and if the VVDS record is correct,
remove the entries from the BCS by using the
DELETE command with the NOSCRATCH
option. Then use the DEFINE RECATALOG
command to recatalog the data set.
RESERVED BITS SET IN

CATALOG ALIAS ENTRY.
If the VVR is incorrect, remove the data set by

using the EXPORT command. At this point,
you can import the data set using the IMPORT
command with the desired NEWNAMES
parameter.
The alias entry shown

contains reserved flags that
are incorrectly set.
System Action: Processing continues with another
record.
Application Programmer Response: Except for the
reason codes listed below, use the following procedures
to recover from these conditions:
25
Check for OPEN or allocation error messages

to determine the source of the problem.
31
Check for OPEN or allocation error messages

to determine the source of the problem.
For BCS Entries:
487
38
41
Delete the cluster entry with DELETE

NOSCRATCH, and recatalog it with DEFINE
RECATALOG. Then rebuild the alternate index
with DEFINE ALTERNATEINDEX and
BLDINDEX.
indicates which error; the record is the key or RBA of

the record involved in the error. The first X'44' bytes of
the Format 1 DSCB are not displayed.
Delete the data set. Then use DELETE VVR or

NVR to delete the duplicate VVDS record.
Recover the data set from a backup copy.
rec
42
Use REPRO MERGECAT to move the data

sets catalog entry to the correct catalog.
43
Use DELETE NOSCRATCH to delete the BCS

record, and DEFINE RECATALOG to recreate
the BCS record. The storage class and
management class may be changed with
ALTER if they are incorrect.
45
Delete the orphaned or extra VVDS records.
46
Determine if the BCS named in the VVR is

valid. If necessary, see OS/390 DFSMS:
Managing Catalogs for the appropriate
recovery procedures.
47
Determine if the BCS named in the VVR is

valid. If necessary, see OS/390 DFSMS:
Managing Catalogs for the appropriate
recovery procedures.
48
49
Determine whether the BCS entry or the

VVR/NVR entry is in error. See OS/390
DFSMS: Managing Catalogs for the
appropriate recovery procedures.

The record in which the error occurred.
System Action: The record is displayed and

DIAGNOSE continues.
Application Programmer Response: Use this record
display to analyze the error and determine correction
techniques.
to the problem.
Source: DFSMSdfp
IDC21372I
xxxxxxxxxxxxxx IS NOT {AN

ICFCATALOG|A VVDS}
Explanation: The DDNAME or DSN given was not the

type indicated in the DIAGNOSE command syntax. If
the data set to be scanned is an ICFCATALOG, the
compare parameter should indicate a VVDS. If input
data set is a VVDS, the compare parameter should
indicate an ICFCATALOG.
50

51

Application Programmer Response: Check for

spelling error. Check for message IDC11373I to see if
compare elements were not used during the
DIAGNOSE run. Correct the statement and resubmit the
job.
53
Delete and redefine the alias entry to correct

the problem.
Source: DFSMSdfp
xxxxxxxxxxxxxx
The indicated DD
name or data set
name.
Source: DFSMSdfp
IDC21365I
text RECORD DISPLAY: RECORD: rec
IDC21404I
dsname IS AN INVALID ASSOCIATION

FOR SPHERE TYPE
Explanation: The data set is not a valid association

for its base object.

ICFCATALOG
VVDS
VTOC
dsname
The record which follows was involved in an error

detected by DIAGNOSE. A previous error message
System Action: The base object and any of its

associations already defined will be deleted from the
488

The data set name.
target catalog and the processing will continue with the

next base object.
problem and rerun the job.
catalog. If the error recurs and the program is not in
error, look at the messages in the job log for more
Support Center. Provide the JCL, the SYSOUT output
for the job, and all printed output and output data sets
Source: DFSMSdfp
v If the operation was a CNVTCAT, restore the

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
Method Services DELETE NOSCRATCH to remove
the catalog entries for sphere dsname from the
source catalog.
v If the delete failed for the target catalog, restore the
volumes, correct the problem and rerun the job.
catalog.
Source: DFSMSdfp

IDC21411I
IDC21409I
CONVERSION FAILED FOR SPHERE

dsname
Explanation: The specified sphere base could not be

converted to the target catalog.
dsname
The data set name.
System Action: Processing is continued with the next
base object.
problem indicated in a preceding message and rerun
the job.
Source: DFSMSdfp
IDC21410I
DELETE OF SPHERE sph FROM

{TARGET|SOURCE} CATALOG FAILED
Explanation: CNVTCAT or REPRO MERGECAT has

attempted to delete a sphere from the source or target
catalog and has failed. When the sphere is not deleted
from the source catalog, the sphere exists in both
source and target catalogs. When the sphere is not
deleted from the target catalog, only a partial sphere
may exist in the target catalog and the sphere exists in
the source catalog as it did before the processing
began.
sph
The indicated sphere.
System Action: Processing of the sphere is ended

and processing continues with the conversion of the
next spheres base.
Application Programmer Response: You can
respond to one of the following conditions:
DATA SET dsname IS MARKED NOT

USABLE
Explanation: The specified data set has been marked

as not usable by a DELETE FORCE operation or by a
RESETCAT operation because of space occupancy
conflict.
dsname
The data set name.
System Action: If the sphere base and any of its
associations have been defined in the target catalog
they will be deleted from the target catalog. Then
processing is continued with the next base object.
can be recovered by using the REPRO command. Then
reissue the CNVTCAT command.
catalog.
Source: DFSMSdfp
IDC21412I
DEFINE FAILED FOR dsname
Explanation: The define failed for the specified data

set.
dsname
The data set name.
System Action: If dsname is a base object and any of
its associations have been defined in the target catalog,
dsname and its associations will be deleted from the
target catalog. The processing is continued with the
next base object. If dsname is a VSAM Volume Data
Set (VVDS), CNVTCAT processing is ended.
489

catalog volume and all volumes owned by the catalog;
correct the problem and reissue the CNVTCAT
command.
Source: DFSMSdfp
IDC21558I
THE REQUEST FOR AN ACCESS

CODE CANNOT BE COMPLETED FOR
CLUSTER X'cluster' - reason
Explanation: The LISTDATA command to retrieve the

remote access authorization code was not successful
for the reason specified. In the message text:
cluster
The 2 hexadecimal digit storage cluster

number.
reason The reason for the error, as follows:

v THE SUPPORT FACILITY IS NOT
AVAILABLE
v THE MODEM ENABLE/DISABLE SWITCH
IS NOT ENABLED
error. Ascertain why the access authorization code was
not returned from the reason specified and resubmit the
request when the access code is obtainable.
Source: DFSMSdfp
IDC21608I
PAIR IS NOT IN SUSPENDED DUPLEX

MODE, CANNOT {RESETTODUPLEX |
REESTABLISHDUPLEX}
Explanation: A SETCACHE command requiring that

the duplex pair be in suspended mode was issued and
the devices were not in suspended duplex state.
Source: DFSMSdfp
IDC21700I
MINOR ERRORS FOUND BY

INDEXTEST
Explanation: INDEXTEST discovered minor errors

during evaluation of the data set index component.
System Action: INDEXTEST concludes with a return
code of four (4).
Application Programmer Response: The discovered
errors should not affect normal processing; however, the
user may wish to verify or rebuild the data set to
eliminate the diagnostic errors.
Source: DFSMSdfp
490
IDC21701I
MAJOR ERRORS FOUND BY

INDEXTEST
Explanation: INDEXTEST found major errors during

evaluation of the data set index component.
System Action: INDEXTEST concludes with a return
code of eight (8).
should not be accessed using the index prior to further
diagnostic testing. If DATATEST processing completes
successfully, you should be able to use export and
import of the data set (via the EXPORT and IMPORT
commands) to rebuild the index.
Source: DFSMSdfp
IDC21702I
MINOR ERRORS FOUND BY DATATEST
Explanation: DATATEST found minor errors during

evaluation of the data set data component. Error
messages displayed prior to this message describe
whether the problem lies within the data repository or
the index sequence set.
System Action: DATATEST concludes with a return
code of four (4).
Application Programmer Response: Minor errors do
not generally result in loss of data. Regeneration of the
data set, using a backup copy, is advisable to eliminate
any current or future problems.
Source: DFSMSdfp
IDC21703I
MAJOR ERRORS FOUND BY

DATATEST
Explanation: DATATEST discovered one or more

major errors during evaluation of the data set data
component. Error messages displayed prior to this
message describe whether the problem lies within the
data repository or the index sequence set.
System Action: DATATEST concludes with a return
code of eight (8).
Application Programmer Response: Data validity is
in question; records may be missing, duplicated, or in
error. The data set must be reconstructed using a
backup copy.
Source: DFSMSdfp
IDC21803I
STORAGE GROUP NAME name DOES

NOT EXIST
Explanation: The specified storage group name is not

defined to the system.
name
The storage group name.

storage group.
Application Programmer Response: Verify validity of
specified storage group.
08
0C
Source: DFSMSdfp
IDC21804I
FAILURE DURING function

PROCESSING - RETURN CODE WAS
return-code, REASON CODE WAS
reason-code VOLSER WAS volser
Explanation: The return code and reason code were

returned by catalog management module ARCUTIL,
DEVINFO, or VVAS as a result of an exceptional
condition. The VOLSER line will only be output if the
failure was from the VVAS.
04
No functions to perform.
05
Incorrect combinations of
options.
Error opening DFHSM control

data set.
01
DFSMShsm MCDS
could not be opened.
02
DFSMShsm BCDS could

not be opened.
Error reading DFSMShsm control

data set.
01
More than 10 read errors

occurred accessing the
DFSMShsm MCDS.
02
More than 10 read errors

occurred accessing the
DFSMShsm BCDS.
03
User specified DUMMY

on the MCDS or BCDS
DD statement. This is
not accepted when
requesting the
corresponding
MCDS/BCDS statistics.
function
The name of the function that was

processing when the error occurred.
return-code
The return code.
reason-code
The reason code.
volser
The Volume Serial number. (Only if

VVAS failure.)

return code is ended.
A list of the return and reason codes follow for each
function affected:
Function
MIGRATION DATA COLLECTION SERVICE
14
An abnormal end occurred.

The reason code
contains the system
completion code.
Function
DEVICE INFORMATION SERVICE
Code
Reason Explanation
00
10
08
UPID not equal to

UPIDNAME.
Size of parameter list is

incorrect.
0C
UPVERS incompatible
with current version used
by ARCUTIL.
Storage for the return

area is not provided or is
not owned by the caller.
10
Storage for the volume

serial list is not owned
by the caller.
04
Incorrect parameter list.
03
The reason code

contains the contents of
register 1 received from
the SYNADAF macro.
Storage for the

parameter list is not
owned by the caller.
Reason Explanation
02
Error writing to the output data

set.
04
Code
01
10
Data control block (DCB)

address not provided.
491
14
Storage for the device

number list is not owned
by the caller.
18
Storage for the PDAREA

is not provided, is not
owned by the caller, or is
too small.
1C
Storage for the return

area is too small to
contain at least a header
and one entry.
20
A bad resume code was

passed by the caller.
24
No matches were found;

search arguments given
are too restrictive.
28
No requests specified.
2C
Incorrect parameter list

level.
30
Conflicting features
request.
34
Incorrect device number

passed.
38
Incorrect device number

passed.
3C
A release call was made

but there was no storage
to free.
04
The pointer in JESCT to

the EDT is zero.
14
18
An error return code was received

from common filter services.
1C
An abend occurred.
20
A nonzero return code was

returned from IEFEB4UV.
24
A nonzero return code was

returned from DEVTYPE.
Function
VTOC/VVDS ACCESS SERVICE
Code
Explanation
08
An error occurred while accessing

the volume table of contents
(VTOC). The reason code
contains the CVAFFILT return
code. See OS/390 DFSMSdfp
Diagnosis Reference for more
information about the CVAF
reason code.
0C
492
An error occurred while accessing

the VSAM volume data set

(VVDS). The reason code
contains the VVDS Manager
return code. See the list of reason
codes for IDC3009I, return code
50.
10
Processing error. The reason

code is the SVC number.
20
Parameter list error.
Source: DFSMSdfp
IDC21805I
ATTEMPT TO ACQUIRE INFORMATION

FAILED FOR VOLSER volser
Explanation: The specified volume was selected for

processing but extracted information was insufficient to
continue processing.
volser

volume.
user control block (UCB) for this volume is valid.
Source: DFSMSdfp
IDC21807I

PROCESSING - RETURN CODE WAS
return-code
Explanation: The return code was returned by the

named function as a result of an exceptional condition.
function
The name of the function, such as TRACK
CIRCULATION SERVICE or LSPACE service.
return-code
The return code. See OS/390 DFSMSdfp
Storage Administration Reference for the return
codes to TRACK CIRCULATION SERVICE.
return code ends.
04
Information for this data set could

not be calculated.
Source: DFSMSdfp
10
Return area provided is too small.
14
Associated with the following

reason codes:
IDC21809I
FAILURE ATTEMPTING TO WRITE

xx-TYPE RECORD FOR DATA SET
dsname ON VOLUME volser
Explanation: The record built for the specified data

set could not be written to the output data set.
xx
00
Size of parameter list is

incorrect.
04
Parameter list not owned

be the caller.
08
Incorrect device
specification.
0C
RTNAREA not specified

(address is zero).
10
RTNAREA not owned by

caller.
14
PDAREA not specified

(address is zero).
18
PDAREA not owned by

caller.
1C
PDAREA too small.
20
DCSDS table not owned

by caller.
24
No requests specified.
The type record.
dsname
The data set name.
volser

problem. Run the utility again.
Source: DFSMSdfp
18
Error encountered in call to CVAF.
1C
ABEND detected with RETRY

parameter specified.
20
Storage unavailable.
Explanation: The return code was returned with the

named function as a result of an exceptional condition.
24
DCS unable to open volume table

of contents (VTOC).
28
Error encountered in call to

device information services.
2C
Error encountered in call to

TRKCALC for a globally used
value (value is not data
set-specific).
IDC21814I

PROCESSING FOR dsname - RETURN
CODE WAS return-code
function
The name of the function.
dsname
The data set name.
return-code
The return code.

return code ends.
A list of the return and reason codes follow for each
function affected:
Function
DASD CALCULATION SERVICE
Code
Reason Explanation
Source: DFSMSdfp
IDC21815I
ARCUTIL NOT CALLED. DATA

CONTROL BLOCK ADDRESS IS
INVALID
Explanation: The address of the output data sets

data control block (DCB) cannot be passed to
ARCUTIL, which builds the records for migrated data
sets, backup versions, and capacity planning
information. The severity is 8.
System Action: Processing associated with ARCUTIL
is bypassed.
Operator Response: The output data sets I/O is
being controlled by the user. If M, B, C, or T
493
records are required, IDCAMS must open the output

data set so that the DCB can be passed to ARCUTIL.
the JCL, the SYSOUT output for the job, and printed
IDC21862I
DBCS CRITERIA ERROR IN RECORD

number AT OFFSET offset
Explanation: DBCS was specified on an access

method services (AMS) PRINT or REPRO copy of a
data set operation. AMS, while criteria checking DBCS
characters to be printed or copied, detected that
characters indicated as DBCS do not meet criteria.
offset
The offset.

catalog to be reset is not in use as a master catalog
before issuing RESETCAT.
Source: DFSMSdfp
IDC31004I
DEFINE OF WORK FILE FAILED
Explanation: DEFINE failed for the work file. Message

IDC3009I precedes this message identifying the Catalog
Management return code which will indicate the reason
for failure.
System Action: The RESETCAT command is ended.
No change has been made to the catalog or a Catalog
Recovery Area (CRA).
Application Programmer Response: Take corrective
action as noted in the IDC3009I message.
Source: DFSMSdfp
number The record number in the source data set.

System Action: Processing continues. The return
code is 8.
IDC31005I

DBCS data meet the following criteria:
Explanation: The work file was defined in the catalog

to be reset.
v The data must be bracketed by paired SO and SI

characters when in combination with SBCS data.
v The number of bytes between the SO and SI
characters must be even, since each DBCS character
requires two bytes to represent it.
Source: DFSMSdfp
IDC31000I
CATALOG NOT A RECOVERABLE

CATALOG
WORK FILE DEFINED IN THE

CATALOG TO BE RESET

No change has been made to be catalog or a Catalog
catalog other than the one being reset via the
WORKCAT parameter, or specify another catalog as the
first concatenated entry in the JOBCAT or STEPCAT
statement.
Source: DFSMSdfp
Explanation: The catalog specified for reset is not a

recoverable catalog.

IDC31006I

catalog to be reset.
Source: DFSMSdfp
IDC31001I
SYSTEM MASTER CATALOG

SPECIFIED FOR RESET
Explanation: The master catalog was specified for

reset. The master catalog cannot be reset while it is in
use as a master catalog.
494
PHYSICAL I/O ERROR - VSAM ACTION

CODE actcde
Explanation: A physical I/O error on the catalog was

encountered while extending the catalog.
actcde
The action code.

physical error and reissue RESETCAT. The VSAM
action code can be found in the OS/390 DFSMS Macro
Instructions for Data Sets . The catalog and CRA entries
have not been altered and hence are recoverable in
their current state - barring the I/O error.
Source: DFSMSdfp
IDC31007I
LOGICAL I/O ERROR - VSAM ACTION

CODE actcde
IDC31012I
MAXIMUM RELATIVE RECORD

NUMBER EXCEEDED IN WORK FILE
Explanation: A logical I/O error was encountered

while extending the catalog during RESETCAT. There
were not enough free records in the catalog being reset,
consequently RESETCAT attempted to get more.
Explanation: The work file relative record number (rrn)

limit has been exceeded. No more records can can be
written to the work file. The resultant catalog is too
large.
System Action: The operation is ended.
actcde
Application Programmer Response: Respecify

subsets of the CRA volumes specified for reset and
issue multiple RESETCAT commands. The catalog
entries have not been altered.
The action code.

logical error. The VSAM action code can be found in
OS/390 DFSMS Macro Instructions for Data Sets. If the
catalog has reached 16 extents and cannot be
extended further, a larger catalog may be defined in
which to perform the RESETCAT. The catalog and CRA
entries have not been altered.
Source: DFSMSdfp
IDC31008I
ERROR ACCESSING THE CATALOG
Explanation: RESETCAT encountered an error trying

to access the data set specified by the CATALOG
parameter. Message IDC3009I precedes this message
identifying the specific error.
error specified in the IDC3009I message and reissue
the command. If the error is not correctable, a new
catalog of the same name may be defined into which all
of the volumes owned by the failing catalog may be
reset using RESETCAT. The entries in the catalog have
not been altered.
Source: DFSMSdfp
IDC31010I
CRA DOES NOT BELONG TO

CATALOG - VOL volser
Explanation: The CRA was specified for reset, but it

belongs to a catalog other than the catalog to be reset.
volser

correct volume to be reset and reissue the command.
Source: DFSMSdfp
Source: DFSMSdfp
IDC31013I
COULD NOT MERGE ONE OR MORE

CRAS
Explanation: See preceding message which indicates

that:
v Open failed for CRA (IDC3300I)
v Close failed for CRA (IDC3301I)
v CRA does not belong to catalog to be reset
(IDC31010I)
error in the referenced message and reissue the
command. The catalog entries have not been altered.
Source: DFSMSdfp
IDC31014I
DELETE OF WORK FILE FAILED
Explanation: DELETE failed for the work file.

Message IDC3009I precedes this identifying the specific
error.
Application Programmer Response: Unless some
previous message indicates an ending error, the
RESETCAT operation has been completely performed.
The work file may be deleted using the DELETE
command after correcting the error indicated in
message IDC3009I.
Source: DFSMSdfp
IDC31016I
NO CRA SPECIFIED FOR RESET
Explanation: The CRAFILES parameter specified no

CRA with the ALL option; hence, no volume was
specified for reset.
495
correct volumes for reset and issue the command.

Source: DFSMSdfp
IDC31017I
UNABLE TO GET EXCLUSIVE USE OF

THE CATALOG
Explanation: Some other task is open to the catalog

requested to be reset. The RESET operation is unable
to reset a catalog without exclusive use.
IDC31035I
BAD VOLUME RECORDS FOR volser
Explanation: In a CRA, either the volume record for

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
mean that all data sets allocated on this volume will be
marked unusable. If NOIGNORE was specified, the
RESETCAT operation ends before updating the catalog
or CRA(s).
volser
Application Programmer Response: For the catalog

being reset, specify DISP=(OLD,KEEP) on the DD
statement, or get exclusive use. Reissue the command.
System Action: The command may end (see

Explanation).
Source: DFSMSdfp
IDC31018I
CRA UNAVAILABLE
Explanation: RESETCAT required a volume that could

not be allocated.
Application Programmer Response: A secondary
CRA volume was required during the reset of a catalog
and it was not available. If enough units are not
available, specify the volume via a DD statement and
include that DD statement in the CRAFILES parameter
on the command indicating NONE. See message
IDC21020I.
Source: DFSMSdfp
IDC31019I
CRA volser SPECIFIED FOR RESET

MORE THAN ONCE
Application Programmer Response: If IGNORE was

specified, no error exists in the catalog; accompanying
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
on this volume, FORCE DELETE the volume, and use
IMPORTRA to recover all data sets.
Source: DFSMSdfp
Detecting Module: IDCRS01, IDCRS03
IDC31038I
COULD NOT UPDATE ONE OR MORE

CRAS
Explanation: See preceding message which indicates

that:
v Open failed for CRA (IDC3300I)
v Close failed for CRA (IDC3301I)
error in the referenced message and reissue the
command. The catalog entries have been updated but
the CRA entries have not.
Explanation: The CRAVOLS parameter specified the

same volser more than once, or the CRAFILES
parameter specified the same volser more than once via
ddnames.
Source: DFSMSdfp
IDC31126I
volser
Detecting Module: IDCDA01, IDCRS01

UNABLE TO READ MSC MAIN
STORAGE
Source: DFSMSdfp
Explanation: An error occurred while the system was

reading MSC (Mass Storage Control) main storage.
MSC main storage cannot be dumped. A message
indicating the MSSC (Mass Storage System
Communicator) reason code for the error appears prior
to this message.

correct volumes for reset and reissue the command.
Application Programmer Response: Perform the

response indicated in the description of the message
that identified the MSSC reason code.
Source: DFSMSdfp
496

IDC31143I
** INCOMPLETE {CHECK|READ}
REPORT PRODUCED, ERROR AT X
LOCATION xxx

check the status of all the requested cells, or to read
the labels of all the requested cartridges.
xxx

occurred.

Application Programmer Response: Reissue the
X coordinate equal to or greater than xxx), after
corrective action was taken as indicated in the primary
message.
Source: DFSMSdfp
IDC31145I
** NO READ REPORT PRODUCED,

ERROR AT X LOCATION xxx
IDC31160I
TOSTAGINGDRIVE SSID SPECIFIED IS

NOT A VALID MSC TABLES SSID
Explanation: The SSID specified as a target for the

table copy is not a valid mass storage control table
SSID. The SSID must be X'000', X'002', X'004', or
X'006'.
System Action: Processing of this command ends.
specify the SSID used with the TOSTAGINGDRIVE
parameter, and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCST01
IDC31170I
UNABLE TO DETERMINE PRIMARY

MSC TABLES LOCATION
Explanation: The attempt to read the Mass Storage

Control main storage to determine the primary mass
storage control tables location failed. The information
necessary to build the SSID for the primary tables is not
available.

read the labels of any of the requested cartridges.

command after the problem with the Mass Storage
Control has been corrected.
Source: DFSMSdfp
xxx
Detecting Module: IDCST01

occurred.

X coordinate equal to or greater than xxx), after
corrective action was taken as indicated in the primary
message.
Source: DFSMSdfp
IDC31180I
PRIMARY TABLES CANNOT BE

COPIED TO WORK DATA SET
Explanation: The primary mass storage control tables

cannot be copied to the work data set.
work data set is allocated properly, and rerun the
command.
Source: DFSMSdfp
IDC31148I
** NOT AUDIT REPORT PRODUCED,

ERROR WITHIN X RANGE n1 n2

check the status of any of the requested cells.
n1 n2
The X coordinates of the range of cells that

could not be checked.

command for the values not processed for all the cells
within the range n1 through n2, after corrective action is
taken as indicated in the primary message.
Source: DFSMSdfp
Detecting Module: IDCCP01

IDC31181I
SECONDARY TABLES CANNOT BE

COPIED TO WORK DATA SET
Explanation: The secondary mass storage control

tables cannot be copied to the work data set.
work data set is allocated properly, and rerun the
command.
Source: DFSMSdfp
Detecting Module: IDCCP01, IDCEC01
497
IDC31201I
REPAIRRANGE PARAMETER cchhr1 GT

cchhr2 FOR dsname
Explanation: The named repair work file (repair work

file) keys in the REPAIRRANGE parameter of REPAIRV
DISPLAY were incorrectly specified.
cchhr1 The first key, which is greater than the second,

identifies a record address.
cchhr2 The second key identifies a record address.
dsname
The data set name.
System Action: REPAIRV DISPLAY ends. Control
returns to access method services. The return code is
12.
Application Programmer Response: Correct
REPAIRRANGE so that the second key is greater than
or equal to the first key and resubmit.
Source: DFSMSdfp
in error, search problem reporting data bases for a fix

for the problem. If no fix exists, contact the IBM Support
job.
Source: DFSMSdfp
IDC31203I
UNIT INDICATES A VIRTUAL DEVICE
Explanation: The unit address specified in the DD

statement referred to by INFILE indicates a virtual
device; if the STAGINGRANGE parameter was
specified, the unit specified must be real. Either the
STAGINGRANGE parameter is incorrect or you have
specified the wrong unit parameter in the JCL.
code is 12.
the unit parameter in the JCL to a real unit or change
STAGINGRANGE to DATASETRANGE, as appropriate,
and resubmit.
Source: DFSMSdfp
IDC31202I
BEGINNING KEY volsercchhr DOES

NOT EXIST FOR dsname
Explanation: The first key specified in

REPAIRRANGE of REPAIRV DISPLAY was not found in
the specified repair work file. Either the volume serial
number is incorrect, the address is incorrect, or the
repair work file is not the one containing the specified
record.
volser
cchhr
The five hexadecimal characters that identify

the record address.
IDC31204I
The repair work file.

System Action: REPAIRV DISPLAY ends. Control
12.
REPAIRRANGE to specify a valid key for the first record
to be displayed. Ensure that the repair work file dsname
is correct and that the key specified is in that work file.
Resubmit.
method services PRINT command to print the repair
work data set. If the error recurs and the program is not
STAGING PACK VOL=SER=volser NOT

FOUND IN STAGINGRANGE
Explanation: The volume serial number of the staging

pack specified in STAGINGRANGE of REPAIRV
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
by INFILE. The JCL and REPAIRV syntax must
correspond.
volser
dsname
498
System Action: REPAIRV DISPLAY/COPY ends

control returns to access method services. The return
code is 12.
correct volume serial number and correct either the job
control language or STAGINGRANGE, as appropriate,
and resubmit.
Source: DFSMSdfp
IDC31205I
INVALID STAGINGRANGE cchhr FOR

DEVICE TYPE
Explanation: The address in the STAGINGRANGE

parameter of REPAIRV DISPLAY/COPY is not valid for
the device type specified in the UNIT parameter of the
DD statement specified by the ddname parameter of
INFILE. Either a portion of STAGINGRANGE is incorrect
or the UNIT parameter is incorrect.
cchhr
Identify a record address.

code is 12.
correct device type of the staging pack and correct
either STAGINGRANGE or the UNIT parameter in the
job control language, as appropriate, and resubmit.
Ensure that the cc is a valid cylinder address and hh a
valid head (track) address for the device.
Source: DFSMSdfp
IDC31206I
AUTHORIZATION TO ACCESS TO
STAGINGPACK VOL=SER=volser
DENIED BY SYSTEM OPERATOR
Explanation: The system operator has responded N

to REPAIRVs request (IDC499D) for access to the
specified volume.
volser
System Action: REPAIRV DISPLAY/COPY/MODIFY

ends. Control returns to access method services. The
return code is 12.
Application Programmer Response: Check with the
appropriate system operations personnel for the reason
for access denial.
Source: DFSMSdfp
IDC31207I
INCORRECT STAGINGRANGE cchhr
Explanation: A count of characters specified in the

STAGINGRANGE parameter of the REPAIRV DISPLAY
or the REPAIRV COPY command showed the length of
the address to be other than 5, the DISPLAY to be
other then 3, or COPY to be other than 1 in the volume.
Anything other than 5, 3, or 1 is incorrect.
cchhr
Identify a record in the track.

code is 12.
STAGINGRANGE and resubmit.
Source: DFSMSdfp
IDC31208I
STAGINGRANGE cchhr1 GT cchhr2 FOR

STAGING PACK VOL=SER=volser
Explanation: The record address parameters in the

STAGINGRANGE parameter of the REPAIRV DISPLAY
or the REPAIRV COPY command were incorrectly
specified for the volume. The first key is greater then
the second key specified in this parameter.
cchhr1 The first key specified. It indicates a record

address.
cchhr2 The second key specified. It indicates a record
address.
volser
System Action: The REPAIRV DISPLAY or the

REPAIRV COPY command ends. Control returns to
access method services. The return code is 12.
STAGINGRANGE so that the second key (cchhr) is
greater then or equal to the first key (cchhr) and
resubmit.
Source: DFSMSdfp
499
IDC31209I
INCORRECT INDATASET PARAMETER

FORMAT4.DSCB
Explanation: The dsname in INDATASET refers to a

volumes VTOC, which is an incorrect specification for
this parameter.
code is 12.
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 volumes
VTOC, use the INFILE parameter and specify
FORMAT4.DSCB as the data set name on the DD
statement of INFILE. Otherwise, specify a valid data set
name in INDATASET; that is, one referring to a data set
cataloged in the system master catalog, a catalog
specified in a STEPCAT or JOBCAT DD statement, or a
catalog having the data sets highest level qualifier as
an alias.
Source: DFSMSdfp
IDC31210I
VOL=SER=volser IN parameter DOES

NOT MATCH THE VOLSER IN DD
STATEMENT ddname
Explanation: The volume serial number in the

parameter does not match the volume serial number
specified in VOL=SER parameter of the DD statement
referred to by INFILE. The JCL and REPAIRV syntax
must correspond.
Valid parameter values follow:
v DATASETRANGE
v INDATASETADDRESS
v OUTDATASETADDRESS
v VTOCHEADERADDRESS
v VTOCHEADER
the data set whose records are to be processed and

correct either the JCL or parameter as appropriate, and
resubmit.
Source: DFSMSdfp
IDC31211I
UNIT INDICATES A REAL DEVICE FOR

dsname
Explanation: The unit parameter specified in the DD

statement referred to by INFILE indicates a real device;
it must indicate a Mass Storage volume. Either the data
set name is incorrect or you have specified the wrong
unit parameter in the JCL.
dsname
The data set name.
System Action: REPAIRV ends. Control returns to
the unit in the job control language to a virtual unit or
change the parameters as appropriate, and resubmit.
Source: DFSMSdfp
IDC31212I
DATASETRANGE cchhr1 TO cchhr2 NOT

WITHIN EXTENTS OF dsname
Explanation: The address range specified in

DATASETRANGE is outside the extents of the specified
data set.
volser
cchhr1 The first key of the range. It indicates a record

address.
parameter
ddname
The specified DD name.
return code is 12.
correct volume serial number of the volume containing
500
cchhr2 The second key of the range. It indicates a

record address.
dsname
The data set name.
code is 12.
actual extents of the data set. Correct the

DATASETRANGE parameters of the named data set
and resubmit.
Source: DFSMSdfp
Application Programmer Response: Correct RANGE

to specify a valid key for the first record to be
deblocked. Ensure that the repair work file is the one
desired and that the key specified is in that work file.
Resubmit.
Source: DFSMSdfp
IDC31213I
(hh1) GREATER THAN hh2 FOR dsname
Explanation: The stage error record keys in the

RANGE parameter of REPAIRV DEBLOCK were
incorrectly specified for repair work file. The first key is
greater than or equal to the second key.
hh1
The first key.
hh2
The second key.
IDC31220I
HEADER RECORD EITHER NOT

FOUND OR INVALID FOR dsname
Explanation: Either no header record was found at

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.
dsname
The data set name.
dsname
The data set name.
System Action: REPAIRV DEBLOCK/MODIFY ends.
code is 12.
Application Programmer Response: Correct RANGE
or INREPAIRRANGE so that the second key (hh) is
greater then or equal to the first key (hh) and resubmit.
System Action: REPAIRV DEBLOCK ends. Control

12.
Application Programmer Response: Correct the job
control language to indicate the appropriate repair work
file or recreate the repair work file using REPAIRV
COPY and resubmit.
Source: DFSMSdfp

job.
Source: DFSMSdfp

IDC31214I
FIRST KEY (volsercchh) IN THE RANGE

NOT FOUND FOR dsname
Explanation: The first key specified in RANGE was

not found in the repair work file. Either the volume serial
number is incorrect, the address is in correct, or the
repair work file is not the one desired.
volser
cchh
The address of a record.

IDC31221I
RECORD IN INDATASETADDRESS
volsercchhr NOT FOUND FOR dsname
Explanation: The specified record is not in the

referenced input data set. That is, the address specified
is not within the extents of the specified data set or
within the first track of the VTOC (VTOCHEADER).
Either the address is incorrect or the wrong data set
was specified.
dsname
The data set name.
12.
volser
cchh
501
dsname

The data set name.
System Action: REPAIRV MODIFY ends. Control

12.
actual extents of the data set, then correct the
INDATASETADDRESS parameter and resubmit.
Source: DFSMSdfp
IDC31222I
RECORD IN INREPAIRKEY volsercchhr

NOT FOUND FOR dsname
Explanation: The record specified in INREPAIRKEY is

not in the referenced repair work file.
volser
cchh
dsname
The output data set name.
parameter
12.
actual address of the record. Correct the
OUTDATASETADDRESS or VTOCHEADER parameter
and resubmit.
Source: DFSMSdfp
volser
cchh
IDC31224I
Explanation: The record specified in OUTREPAIRKEY

is not in the referenced repair work file.
dsname
12.
repair work file records. If necessary, recreate the repair
work file using REPAIRV COPY, or correct the
INREPAIRKEY parameter, and rerun.
job.
Source: DFSMSdfp
IDC31223I
RECORD volsercchhr IN parameter NOT

FOUND FOR dsname VTOCHEADER
Explanation: The record specified in

OUTDATASETADDRESS or VTOCHEADERADDRESS
is not in the specified user data set. That is, the address
specified is not within the extents of the specified output
data set or within the first track of the VTOC
(VTOCHEADER).
502
RECORD IN OUTREPAIRKEY
volsercchhr NOT FOUND FOR dsname
volser
cchh
dsname
12.
work file using REPAIRV COPY, or correct the
OUTREPAIRKEY parameter, and resubmit.
job.
Source: DFSMSdfp
IDC31225I
RECORD volsercchhr IN parameter

DOES NOT MATCH THE FIRST
INREPAIRRANGE ADDRESS
Explanation: Both OUTDATASETADDRESS or

VTOCHEADERADDRESS and INREPAIRRANGE were
specified, indicating a full track replacement is to be
performed.
volser
cchhr
The address of a record, where r of the

VTOCHEADERADDRESS or
OUTDATASETADDRESS volume must be 0 to
indicate the beginning of the track or did not
match the first INREPAIRRANGE address.
parameter
12.
address in OUTDATASETADDRESS or
VTOCHEADERADDRESS to ensure a 0 in the record
field, and a match to the INREPAIRRANGE first
address.
Source: DFSMSdfp
IDC31226I
NOT ALL TRACKS SPECIFIED IN

INREPAIR RANGE ARE ALLOCATED
TO OUTPUT text

dsname
VTOCHEADER
INREPAIRRANGE parameter to specify only allocated

tracks and resubmit.
to the problem.
Source: DFSMSdfp
IDC31227I
RECORD ZERO FOR volsercchh WAS

NOT FOUND IN dsname
Explanation: Record zero in the stage error deblocked

track specified in the message could not be found in the
specified repair work file. Either the volume serial
number or the range in INREPAIRRANGE is incorrect.
volser
cchh
dsname
System Action: REPAIRV MODIFY ends after the
entire range. Control returns to access method services.
The return code is 12.
work file using REPAIRV COPY. Correct
INREPAIRRANGE and resubmit.
job.
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
dsname
12.
actual extents of the data set. Correct the
RECORD volsercchhr IS NOT A

DEBLOCKED STAGE ERROR RECORD
IN dsname
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
been corrected by DEBLOCK.
volser
503
cchhr

12.
dsname
System Action: REPAIRV MODIFY ends after
checking the entire range. Control returns to access
method services. The return code is 12.
INREPAIRRANGE and resubmit.
job.
Source: DFSMSdfp
The offset.

OFFSET parameter and resubmit.
to the problem.
Source: DFSMSdfp

IDC31231I
IDC31229I
DEBLOCKED TRACK cchh TOO LARGE

FOR dsname
Explanation: The modified records from the specified

repair work file will not fit within the track of the
specified data set. Either one or more records have
been lengthened or added to the original track, or you
are moving from a device with longer tracks to one with
shorter tracks.
Explanation: A record that was to replace another

record in the specified output data set or
VTOCHEADER does not fit in the output data set track.
dsname
The output data set name.

12.

replacement record will fit in the output data set track.
cchh
INPUT RECORD TOO LARGE

{dsname|VTOCHEADER}
dsname
12.
Application Programmer Response: Verify that your
input is correct and will fit within the specified track.
job.
Source: DFSMSdfp
IDC31230I
OFFSET n OUTSIDE KEY OR DATA

FIELD

job.
Source: DFSMSdfp
IDC31232I
MODIFIED RECORD TOO LARGE FOR

{dsname|VTOCHEADER}
Explanation: The input string specified in the

command causes the record being modified to exceed
the track boundaries of the specified data set or repair
work file or VTOCHEADER.
Explanation: The offset specified for the key or data

field is longer than the actual key or data field length.
dsname
504
The specified data set name or repair work file.

12.

return code is 12.

input string does not cause the modified record to
exceed its track boundary.

correct device type of the data set and correct either the
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

Source: DFSMSdfp
IDC31233I
INCORRECT parameter cchh FOR

dsname
Explanation: A count of characters specified in the

parameter of REPAIRV DISPLAY/COPY/MODIFY
showed the length of the record address to be other
than 5, or COPY to be other then 3. Anything other then
5 or 3 is incorrect.

IDC31235I
DATASETRANGE cchhr1 GT cchhr2

FOR dsname
Explanation: The parameters in the DATASETRANGE

parameter of REPAIRV DISPLAY/COPY were incorrectly
specified. The first key is greater than the second key
specified in this parameter.
parameter
cchh
cchhr1 The first key specified. It indicates the address

of a record.
cchhr2 The second key specified. It indicates the

address of a record.
dsname
return code is 12.
parameters and resubmit.
Source: DFSMSdfp
IDC31234I
INVALID PARAMETER cchhr FOR

DEVICE
Explanation: The address parameter of REPAIRV

DISPLAY/COPY/MODIFY is not valid for the device type
specified in the UNIT parameter of the DD statement
specified by the ddname parameter of INFILE. Either a
portion of the parameter is incorrect or the UNIT
parameter is incorrect.
cchhr
dsname
code is 12.
DATASETRANGE so that the second cchhr is greater
then or equal to the first cchhr and resubmit.
Source: DFSMSdfp
IDC31237I
THE SUM OF THE LENGTH

SUBPARAMETERS IS TOO
{LARGE|SMALL}
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
either larger or smaller than the actual sum of the
original records.
505

12.
Application Programmer Response: Correct the key
and data lengths specified in the LENGTH parameter
are correct: display the R0/R1 records, correct, and
rerun.
job.

Source: DFSMSdfp
IDC31240I
OUTDATASETADDRESS cchhr DOES

NOT REFER TO A RECORD IN VTOC
Explanation: The record address value in the

OUTDATASETADDRESS parameter of the MODIFY
function is not within the range of the VTOC.
Source: DFSMSdfp
cchhr
IDC31238I
UNABLE TO DEFINE dsname
Explanation: REPAIRV COPY was not able to define

the repair work file as specified in the DD statement
referred to by OUTFILE. The last message issued prior
to this one explains why the attempted definition failed.
dsname
System Action: REPAIRV COPY ends. Control
12.

returns to access method services. Return code is 12.
condition causing the failure.
Source: DFSMSdfp

IDC31241I

Explanation: The length specified in the NEWCOUNT

parameter is less than 8 bytes long.
Source: DFSMSdfp
IDC31239I
VTOCHEADERADDRESS cchhr DOES

NOT REFER TO THE FIRST TRACK OF
VTOC
Explanation: The VTOCHEADERADDRESS

parameter of the MODIFY function is not the first track
of the VTOC of the output volume.
NEWCOUNT MUST BE EIGHT BYTES

LONG

12.
NEWCOUNT parameter to be exactly 8 bytes long.
Source: DFSMSdfp
cchhr
System Action: REPAIRV MODIFY ends, control

12.
506
IDC31242I
BAD RECORD
{PRECEDING|SUBSEQUENT TO}
RECORD volsercchhr IN OUTPUT
dsname
Explanation: It is necessary to read all records in the

track to calculate if the record to be modified would fit in
the track; either a previous or subsequent record to the

one to be modified had an I/O error in the repair work
file.
volser
cchh
dsname
12.
Application Programmer Response: Rerun the job;
the error should correct itself, that is, it either goes away
or becomes a destage error.
cchh

is 12.
Application Programmer Response: Verify that you
specified the correct address in the command. The R1
record can be replaced in the repair work file or in the
original data set with the correct records from another
source by using the REPAIRV MODIFY command.
Alternatively, the R1 record can be restored by using
the REPAIRV MODIFY command.
method services PRINT command to print the repair If
the error recurs and the program is not in error, search
the JCL and the SYSOUT output for the job. work data
set.
Source: DFSMSdfp
Source: DFSMSdfp
IDC31243I
THE COUNT OF RECORD ZERO cchhr

CANNOT BE MODIFIED
Explanation: The user tried to modify the count, or

increase the length of the data field or insert a key in a
record zero address, which is not permissible.
cchhr
IDC31245I
AN UNCORRECTABLE I/O ERROR

WAS ENCOUNTERED WHILE
MODIFYING cchh OF dsname
Explanation: An I/O error was encountered while

writing to the specified data set.
cchh
dsname

12.
System Action: REPAIRV MODIFY processing ends.

code is 12.
Application Programmer Response: Ensure that you

really want to modify record zero; if you are going to
modify record zero, you are allowed only to modify the
data field without increasing its length. Resubmit.
Application Programmer Response: The results are

unpredictable. Run REPAIRV DISPLAY command to
display the track on which the error occurred to
determine how much of modify process completed. Take
appropriate action to reconstruct data.

Source: DFSMSdfp
IDC31244I
UNABLE TO DEBLOCK cchh
Explanation: The record pair (R0 or R1) that results

from the stage error could not be deblocked because
the R1 record contained a dummy data field length of
1. This condition is caused by the loss of the track
descriptor during staging.
Source: DFSMSdfp
IDC31246I
OBTAIN FAILED FOR dsname
Explanation: OBTAIN SVC failed for the specified

data set name.
dsname
System Action: REPAIRV ends. Control returns to
Application Programmer Response: If processing a
507
VSAM data set, ensure that unit and volume information

are not present on the DD statement for the specified
data set name. Correct the condition causing the failure
and resubmit.
IDC31265I
A SECURE MOUNTED VOLUME

CANNOT BE COPIED
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.
Source: DFSMSdfp

COPYV command specifying NOT MOUNTED.
Source: DFSMSdfp
IDC31247I
TRACK DOES NOT BEGIN WITH

RECORD 1
Explanation: The data portion of record pair R0,

which shows the original first record number, shows that
record number to be other than record 1.
is 12.
Application Programmer Response: Issue REPAIRV
DISPLAY to display the blocked stage error records R0
and R1. If the records appear to be valid, usable
records that you want to deblock, issue REPAIRV
MODIFY to change the R0 data portion of record 0,
mapping the original record number of record 1 to the
value 1. Then, after issuing REPAIRV DISPLAY to verify
your change, issue REPAIRV DEBLOCK to deblock
your blocked stage error records.
job.
Source: DFSMSdfp
IDC31251I
CARTRIDGE NOT EJECTED
Explanation: An unsuccessful attempt was made to

eject a cartridge with the DIRECTEJECT option of the
MODIFYC command. The location of the cartridge is not
known.
System Action: The MODIFYC command ends. The
return code is 12.
Source: DFSMSdfp
Detecting Module: IDCRD04, IDCMC01
IDC31366I
INPUT DATA SET IS NOT {AN

ICFCATALOG|A VVDS}
Explanation: The data set to be diagnosed was not

an ICF catalog or a VVDS as the type indicated in the
DIAGNOSE command syntax. If the data set to be
scanned is an ICF catalog, the syntax should be
DIAGNOSE ICFCATALOG; if the data set is a VVDS,
the syntax should be DIAGNOSE VVDS.
System Action: The DIAGNOSE processing ends.
statement and resubmit the job.
Source: DFSMSdfp
IDC31368I
CATALOG MAY NOT BE SPECIFIED

WITH ICFCATALOG
Explanation: The CATALOG parameter may not be

coded as an include or exclude subparameter for
ICFCATALOG. CATALOG qualification is only intended
for diagnosis of a VVDS.
System Action: DIAGNOSE considers this an error
condition; processing ended.
DIAGNOSE statement and rerun the job. If DIAGNOSE
is being run against an ICFCATALOG, replace the
catalog parameter with either ENTRIES or LEVEL. If not
analyzing a catalog but a VVDS, change the
ICFCATALOG parameter to VVDS.
Source: DFSMSdfp
IDC31369I
text PROCESSING TRUNCATED

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.
508
This message may also result from I/O errors, if so,

message IDC3351I, which precedes IDC31369I, may be
used to determine the cause of the I/O error. In either
case, this may be indicative of a badly damaged input
data set.
condition; processing ended.
ERRORLIMIT value is too low, set a different value and
rerun the job. ERRORLIMIT has a default value,
determine the default value (you may wish to allow
DIAGNOSE to detect more errors than the default
value) and rerun the job. If the problem is an I/O error,
the data set is too damaged for DIAGNOSE to analyze.
Consider initiating BCS or VVDS recovery procedures.
Source: DFSMSdfp
v Uplevel the BCS.

v Re-run DIAGNOSE.
Source: DFSMSdfp
IDC31377I
FIRST CATALOG ENTRY NOT FOUND
Explanation: DIAGNOSE cannot locate the first ICF

catalog entry. The self describing cluster entry for the
catalog is absent or damaged.
following actions.
v Import the BCS to restore it.
v Uplevel the BCS.
v Re-run DIAGNOSE.
Source: DFSMSdfp

IDC31400I
IDC31370I
UNABLE TO OBTAIN INFORMATION

ON {dsname|ddname}
Explanation: An attempt to extract allocation

information for the named data or dd statement has
failed. If the data set in question is the input data set,
DIAGNOSE cannot continue. If the data set in question
is a compare data set then compare processing cannot
occur.
UNABLE TO OBTAIN CATALOG NAME
Explanation: CNVTCAT did not receive either the

source or target catalog name. The source catalog is
identified via the INFILE or INDATASET parameter and
the target catalog via the OUTFILE, OUTDATASET or
CATALOG parameter.

specification of the catalog and rerun the job.
dsname
Source: DFSMSdfp
The data set name.
The DD name.
IDC31401I
ddname
condition; processing may end or continue, depending
on which data set incurred the error.
spelling of the named data set or dd statement. Correct
and then rerun the job. If the spelling is not in error,
contact your service representative.
Source: DFSMSdfp
IDC31376I
INPUT CATALOG HAS NO VVDS

ENTRIES
Explanation: The ICF catalog that the system is

currently diagnosing has no SYS1.VVDS.Vvoler entries.
This indicates BCS damage; there should be a VVDS
entry for the volume.
System Action: The system ends DIAGNOSE
processing.
UNABLE TO GET NEXT BASE OBJECT

dsname
Explanation: Catalog management could not get the

next base object and the catalog end of file has not
been reached.
dsname
The data set name.
catalog volume, and all volumes owned by the catalog,
correct the problem identified in the associated
message and rerun the job.
catalog.
Source: DFSMSdfp

following actions.
v Import the BCS to restore it.
509
IDC31403I
UNABLE TO DETERMINE CATALOG

TYPE FOR dsname
Explanation: A catalog management LOCATE failed

and the catalog type could not be determined.
and rerun the job. If correct, the master catalog must be

made a user catalog before it may be converted.
Source: DFSMSdfp

IDC31440I
dsname
The data set name.
problem identified in the associated message and rerun
the job.
catalog.
Source: DFSMSdfp
IDC31405I
INVALID COMBINATION OF CATALOGS

FOR CONVERT
Explanation: Prior to converting an OS CVOL or a

VSAM catalog it was determined that the source and
target object types constitute an incorrect conversion
combination. The source and target object types were
such that the conversion could not be allowed. The
following are valid source and target combinations:
SPACE PARAMETER IS INVALID FOR

AN ICF CATALOG
Explanation: The catalog selected by LISTCAT to be

listed was an ICF catalog. ICF catalogs do not contain
space entries. This message is issued if a single entry
type parameter of SPACE is specified or if multiple
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.
Application Programmer Response: Check if the
correct catalog has been specified to be listed. Check
either the LISTCAT CATALOG parameter or the
STEPCAT JOBCAT DD parameter. If none are
specified, then the master catalog must be an ICF
catalog.
Source
Target
Source: DFSMSdfp
OS CVOL
VSAM
OS CVOL
ICF
VSAM
ICF
System Action: Processing of this command is

ended.
source and/or target catalog specification and rerun the
job.
Source: DFSMSdfp
IDC31406I
CONVERSION OF THE SYSTEM

MASTER CATALOG NOT ALLOWED
Explanation: During catalog validation, it was found

that the source catalog specified by the user is the
system master catalog. All entries are deleted from the
source catalog during conversion and thus conversion
of the master catalog cannot be allowed.
ended.
source catalog name specification. If in error, correct
510
IDC31461I
REPRO MERGECAT FROM MASTER

CATALOG NOT ALLOWED
Explanation: During REPRO catalog validation, it was

found that the source catalog specified by the user is
the system master catalog. All objects that have been
successfully merged are deleted from the source
catalog; therefore, merging from the master catalog
cannot be allowed.
ended.
source catalog name specification. If in error, correct
and rerun the job. If correct, the master catalog must be
made a user catalog before it may be merged.
Source: DFSMSdfp

IDC31466I
THE SOURCE DATA SET CANNOT BE

A type
Explanation: The type is either CVOL or CATALOG.

DBCS was specified on an access method services
(AMS) REPRO copy of a data set. AMS, while checking
the data set type, detected that the source data set was
either a catalog or CVOL. REPRO will not copy a
catalog or CVOL if DBCS is specified.
type
The specified type.
System Action: The command is ended. The return

code is 12.
Application Programmer Response: Recheck the
specification of the data set name to ensure the proper
data set was processed. If you intend to copy a catalog
or CVOL, remove the DBCS keyword from your
command.
Source: DFSMSdfp
IDC31503I
UNABLE TO OBTAIN DEVICE

INFORMATION
Explanation: A DEVTYP (device type) macro

instruction, issued by a program, failed to obtain cchh
boundaries, probably because of a system error.
request.
Application Programmer Response: Probable
system error. Add an AMSDUMP DD statement to the
JCL, and run the program again.
Source: DFSMSdfp
Detecting Module: IDCBD01
IDC31504I
NOT ENOUGH ROOM IN THE CACHE

TO HOLD THE SPECIFIED DATA
Explanation: The LOWCCHH and HIGHCCHH

parameters specify more data to be bound than can be
contained in the available cache space of the 3880
device.
IDC31467I
MAXIMUM ERROR LIMIT REACHED
Explanation: The number of errors encountered has

reached the error limit value.
System Action: Processing terminates.
Application Programmer Response: If ERRORLIMIT
value is too low, set a different value and rerun the job.
ERRORLIMIT has a default value (you may wish to
allow REPRO to detect more errors than the default
value) and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCI001
IDC31502I
SPECIFIED cchh IS NOT IN BOUNDS

OF THE 3380
Explanation: The record address has the value of

LOWCCHH or HIGHCCHH, as specified on the
BINDDATA command. The value should be in range for
the device attached to the Model 13.
cchh
System Action: The command is not processed.

command and resubmit.
Source: DFSMSdfp
Detecting Module: IDCBD01, IDCSS04
Application Programmer Response: Issue the

LISTDATA command with the STATUS parameter to
determine how much cache space is available. If the
amount of offline space available is excessive, contact
your programming support personnel.
Change the values of the LOWCCHH and HIGHCCHH
parameters to fit the available cache space. Then issue
the BIND command again.
Source: DFSMSdfp
IDC31550I
UNABLE TO LOCATE ANY CACHING

SUBSYSTEM DEVICES ONLINE
Explanation: The user issued either a LISTDATA or

SETCACHE command, but the system could not find
any subsystem devices online for the associated UNIT
and VOLSER.
System Action: Processing is ended for this
command.
Application Programmer Response: Do the
following:
v Ensure that the correct UNIT and VOLSER are
specified.
v Make sure there are volumes online. You can use the
DEVSERV PATHS command to determine the
volume and path status.
v Rerun the command.
Source: DFSMSdfp
511
IDC31559I
ASYNCHRONOUS OPERATIONS
MANAGER RC=return-code
REASON=reason-code other
Return Code 4: Reason Codes

4
GETMAIN failure occurred within the service.

This may indicate that the region size for your
IDCAMSjo job or your region size for TSO/E
needs to be increased. IDCAMS should have
issued IDC2011I when this error code was
returned. Please refer to IDC2011I for details
on the error condition. If the GETMAIN failure
is for a system area, then a system message
indicating the failure appears on the system
console and you should follow the directions
for the system message.
Explanation: An IDCAMS channel program was

passed to the asynchronous operations manager. The
resulting return and reason codes from the
asynchronous operations manager were unexpected.
return-code
The return code from the

asynchronous operations manager.
reas
The reason code from the

asynchronous operations manager.
other
Additional information, when available,

from the asynchronous operations
manager:
0-15
16-31
xxxxxxxx
xxxxxxxx
xxxxxxxx
xxxxxxxx
xxxxxxxx
xxxxxxxx
xxxxxxxx
xxxxxxxx
12
16
v INTERNAL QUEUE ERROR

CODE=internal queue error return
code: the code returned from the
asynchronous operations manager
for return code 12, reason code 4.
v Blank when no additional
information is available.
20
ASYNCHRONOUS OPERATIONS MANAGER

ERROR
The request to the service failed with the
reason code specified below.
512
INVALID REQUEST TYPE FOR CONTROL

UNIT
Internal error.
28
SUBSYSTEM DATA AREA NOT LARGE

ENOUGH
Internal error.
32
UNABLE TO LOCATE SSSCB ENTRY

Internal error.
OPERATION FAILED
12
24
REQUEST FAILED
INVALID CCW OR DATA AREA POINTER

Internal error. IDCAMS should have issued
message IDC31602I for this condition. Please
refer to this message for further details on the
error condition.
SUCCESSFUL
The request to the service completed without
error.
UNABLE TO ESTABLISH ESTAE

IDC2391I for this error condition. Please refer
to this message for further details on the error
condition.
The Asynchronous Operations Manager return and

reason codes are:
Return Codes
UNAUTHORIZED REQUEST
IDCAMS was not authorized for this request.
Possible reasons are that IDCAMS was
invoked via a TSO/E CALL command, was not
linkedited as authorized, or does not reside in
an authorized library. Contact your systems
programmer.
Sense data will be returned when

available.
v ABEND CODE=abndcde: the
abend code returned from the
asynchronous operations manager
for return code 12, reason code 8.
INVALID PARAMETER LIST

IDC31601I or IDC31550I for this error
condition. Please refer to this message for
further details on the error.
v 32 bytes of I/O sense data in the

form:
SENSE BYTES
INSUFFICIENT STORAGE
36
REQUEST BUFFER SIZE NOT A MULTIPLE

OF 8
Internal error.
40
CONFIGURATION TABLE INDEX TOO HIGH

Internal error.
44
SSSCBUPD VALUE(S) INVALID
Internal error.
48
52
UNABLE TO OBTAIN COMPLETE SSSCB

ENTRY
Internal error.
136
SSDP POINTS AT AREA NOT OWNED BY

CALLER
DEVICE NUMBER INVALID
Internal error.
140
UCB ADDRESS OR DEVICE NUMBER

NEEDED FOR RACF CHECK
INVALID RACF LEVEL

Internal error.
76
ONLY ONE ACCESS CODE AVAILABLE

4
Internal error.
80

POINTS AT NON-DASD DEVICE
Internal error.
88
REQTYPE DRVR PARM(S) NOT ALLOWED
12
Internal error.
96
100
16
REQUEST BUFFER HAS ONLY ONE

SUB-BUFFER
INDIRECT ADDRESS LISTS NOT ALLOWED

IN DRVR CHANNEL PROGRAM
20
TIC MUST POINT AT *-8

Internal error.
112

MISSING
Internal error.
116
SSDP MISSING
Internal error.
124
NO 3990 MODEL 3 IN THE SYSTEM

Internal error.
128
INVALID REQUEST FOR REQTYPE MULTI

Internal error.
ASYNCHRONOUS OPERATION TIME OUT

The asynchronous operation is still in progress,
but the timer for IDCAMS waiting for the
operation has expired. When the asynchronous
operation completes, if it Fails or Completes
In Error an AOM000I message will be issued
to the system console. If the operation is
successful the status will be correctly reflected
in the storage control and in all attached host
systems. Generally this error will occur while
establishing or reestablishing a dual copy pair
and contention from other hosts or the host
trying to do the operation cause time to be
taken away from the 3990 copy operation to
service these other I/O operations.
Internal error.
108
ASYNCHRONOUS OPERATION FAILED

IDCAMS should issue IDC31610I message for
this error condition. Refer to that message for
details on the error.
Internal error.
104
ASYNCHRONOUS OPERATION COMPLETED

IN ERROR
IDCAMS should have issued IDC2391I for this
error condition. Please refer to that message
for details on the error.
SSDP AND SSDL NOT ALLOWED

Internal error.
ASYNCHRONOUS OPERATION PENDING

The asynchronous operation is still in progress
and IDCAMS should still be waiting for
completion.
SSDL MISSING
Internal error.
92
I/O ERROR EXECUTING CALLERS

CHANNEL PROGRAM
An I/O error occurred. IDCAMS issues
message IDC31559I when sense data is
available. Otherwise IDCAMS issues message
IDC2375I. Please refer to that message for
further information on the error condition.
INVALID EYE-CATCHER IN SERVL OR

UNABLE TO ACCESS LAST BYTE IN SERVL
Internal error.
84
AOM services caller requested an operation

against an exposure address of a multiple
exposure device, which was supported prior to
MVS/ESA SP 5.2. AOM services caller
requested an operation against an alias device
number of a parallel access volume.
Internal error.
60
INVALID EYE-CATCHER IN INPUT BUFFER
Internal error.
Internal error.
56
132
24
REQUEST LOST BY SUBSYSTEM

The storage control lost knowledge of the
asynchronous operation. Please refer to a
merged LOGREC listing for more details.
513
Running an IDCAMS LISTDATA report will give

you the current state of the subsystem and
device. After determining the current state, you
may need to rerun your IDCAMS job to
establish the new states that you desire.
28
DESTAGE-ALL DID NOT COMPLETE

SUCCESSFULLY
Message AOM001I is issued for failing
subsystem. Refer to message AOM001I for
information on the problem determination
required to isolate the devices attached to the
subsystem that have pinned data.
32
I/O ERROR EXECUTING INTERNAL

CHANNEL PROGRAM
Internal error.
36
I/O ERROR, RETRIES EXHAUSTED FOR

CALLERS CHANNEL PROGRAM
Permanent I/O error.
40
AN ATTEMPTED I/O OPERATION RESULTED

IN A CONDITION CODE 3.
Permanent I/O error.
44
AN I/O OPERATION TO A DEVICE

ENCOUNTERED AN INTERVENTION
REQUIRED CONDITION.

4
INTERNAL QUEUE ERROR

Internal error.
ABNORMAL TERMINATION
Internal error.

Application Programmer Response: If the sense
data is returned, find the returned sense data in IBM
3990 Storage Control Reference. Otherwise, refer to
IBM 3990 Operations and Recovery Guide.
Source: DFSMSdfp
IDC31561I
VTOC ACCESS ERROR RC=return-code

CVSTAT=stat ADDR=cccchhhhrr
Explanation: The LISTDATA command to print a

PINNED TRACK REPORT was issued and was
unsuccessful. The attempt to access the VTOC for the
volume failed.
return-code
The decimal return code from a

CVAFSEQ or CVAFDIR macro.
stat
The CVAF status code in decimal.
cccchhhhrr
The hexadecimal address in the

VTOC of the DSCB being read.
514

Application Programmer Response: For MVS/ESA
or MVS/XA, refer to OS/390 DFSMSdfp Storage
Administration Reference for the meanings of CVSTAT
codes. For OS/390, see OS/390 MVS System Data Set
Definition.
For logical errors, return codes 4 and 12, contact your
local IBM support personnel. For VTOC structure errors,
return code 8, and for I/O errors, return code 16, correct
the cause of the error and resubmit the job.
Source: DFSMSdfp
IDC31562I
THE parameter PARAMETER IS NOT

AVAILABLE FOR THE SPECIFIED
SUBSYSTEM OR DEVICE
Explanation: A LISTDATA or SETCACHE command

was issued. Either a parameter that is not supported on
the device specified was encountered or a hardware
error might have caused the device to be unable to
perform the requested command. This message is also
printed if:
v The device specified for a duplex pair secondary or
alternate device is not attached to a 3990 Model 3 or
Model 6.
v DIRECTOR (SD) is requested for a device not
attached to a 3880 Model 21.
v SETCACHE REINITIALIZE, SETCACHE
SUBSYSTEM OFF, SETCACHE NVS OFF, or
LISTDATA ACCESSCODE is issued to the secondary
device of a duplex pair.
v DUAL COPY OPERATION (SETSECONDARY,
SUSPENDPRIMARY, SUSPENDSECONDARY,
RESETTODUPLEX, REESTABLISHDUPLEX,
RESETTOSIMPLEX) was issued to a 2105 storage
control unit.
parameter
The parameter that is not applicable for the
specified subsystem.
For SETCACHE, unsupported parameters
include:
v CACHEFASTWRITE
v DASDFASTWRITE
v DESTAGE
v DIRECTOR
v DISCARDPINNED
v NVS
v PENDINGOFF
v REESTABLISHDUPLEX
v REINITIALIZE
v RESETTODUPLEX
v RESETTOSIMPLEX
v SETSECONDARY
v SUSPENDPRIMARY
v SUSPENDSECONDARY
v UNITNUMBER
v DEVICE
v SUBSYSTEM
For LISTDATA, unsupported parameters
include:
v DSTATUS
v PINNED
v ACCESSCODE
Application Programmer Response: Resubmit the
job, specifying the appropriate device. Check the status
of the device to verify that it can perform the requested
command.
Source: DFSMSdfp
IDC31602I
LOAD REAL ADDRESS FAILED ON I/O

OPERATION
Explanation: The Load Real Address (LRA)

assembler instruction failed during an I/O operation.
This is probably a system error.
System Action: The system could not process the
instruction.
Application Programmer Response: Add an
AMSDUMP DD statement to the JCL and run the
program again.
Source: DFSMSdfp
IDC31564I
THE SUBSYSTEM WILL NOT SUPPORT

PAGING MODE: THE CACHE MUST BE
INITIALIZED
Explanation: This message is issued when a

permanent error occurs and the subsystem can no
longer support paging. The message appears at the end
of the subsystem status report containing the status
counts at the time the error occurred.
System Action: The cache is initialized when MVS is
IPLed (if the subsystem is online), or during the first
PAGEADD command.
Application Programmer Response: IPL MVS with
the subsystem online, or set the subsystem online after
the IPL and do a PAGEADD to initialize the cache.
Source: DFSMSdfp
IDC31601I
VOLUME volser NOT ON A CACHING

SUBSYSTEM
Explanation: The FILE or VOLUME parameter

specifies a volume that is not on a caching subsystem.
volser

IDC31604I
UNITTYPE SPECIFIED IS NOT A VALID

SUBSYSTEM UNITTYPE
Explanation: The unit type specified in the unit

parameter was not valid. 3350 and 3380 are valid unit
types for LISTDATA and SETCACHE commands. 3380
is the only valid unit type for a BINDDATA command.
This message is also issued if the request is not
supported for the storage control model.
System Action: Processing is ended for this
command.
Application Programmer Response: Change the unit
type and reissue the command.
Source: DFSMSdfp
Detecting Module: IDCBD01, IDCLA01, IDCSC01
IDC31606I
UNABLE TO action -PROBABLE CAUSE

IS cause -VOLUME volser
Explanation: A SETCACHE or LISTDATA request

cannot be run because the state of the subsystem or
device is not as required.

command with the FILE or VOLUME parameter.
For a SETCACHE request, action and cause can be

replaced with the following values:

error, or the operator varied offline the device with the
specified volume.
Action Causes/Responses
Correct the DD statement associated with the FILE

parameter, or correct the volser on the VOLUME
parameter. Make sure that the required device is online.
Then issue the command again.
Source: DFSMSdfp
SET DEVICE CACHING ON

-PINNED DATA: Probable cause for the device
being in pending state is pinned data. In order
for the device to be activated for caching the
pinned data must first be discarded
(SETCACHE DISCARDPINNED).
A PINNED TRACK REPORT can be generated
(LISTDATA PINNED), and the data set with
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

data set are IEBCOPY and IEBGENER.) For
other types of pinned data, reaccess and try to
destage or discard.
SET DEVICE CACHING OFF
-DASDFASTWRITE FAILED: The DASD fast
write failed condition exists for this device. The
command is ended and results in no action
taken.
DISCARDPINNED
-DASDFASTWRITE FAILED: The DASD fast
write failed condition exists for this device. The
command is ended and results in no action
taken.
DESTAGE
-NVS FAILED: The nonvolatile storage is
failed. The command is ended and results in
no action taken.
SET SUBSYSTEM STORAGE OFF
-NVS FAILED: The nonvolatile storage is
failed. The command is ended and results in
no action taken.
SET SUBSYSTEM STORAGE ON
-PINNED DATA: Probable cause for the
subsystem being in pending state is pinned
data. To activate the subsystem storage, the
pinned data must first be discarded by a
SETCACHE DISCARDPINNED for each
volume with pinned data or a SUBSYSTEM
PENDINGOFF, which causes cache fast write
pinned data in the cache to be discarded.
(SUBSYSTEM PENDINGOFF will not work for
data pinned in the NVS.) A PINNED TRACK
REPORT can be generated (LISTDATA
PINNED), and then the data set with pinned
retriable or non-retriable tracks can be copied
to a device prior to discarding the pinned data.
(Possible utilities for copying the data set are
IEBCOPY and IEBGENER.) For other types of
pinned data, reaccess and try to destage or
discard.
-DISABLED FOR MAINTENANCE: To activate
subsystem storage, rerun the SETCACHE
command when the subsystem is no longer
disabled for maintenance (probable SR action
to enable).
SET SUBSYSTEM STORAGE PENDINGOFF
-WRONG COMMAND ISSUED: The
subsystem is not in pending state with scan
complete. The SETCACHE SUBSYSTEM OFF
would probably have resulted in the subsystem
storage being deactivated.
-NVS PINNED DATA: There is pinned data in
the NVS. A PINNED TRACK REPORT can be
generated (LISTDATA PINNED), and then the
data set with pinned retriable or non-retriable
tracks can be copied to a device prior to
516
discarding the pinned data. (Possible utilities

for copying the data set are IEBCOPY and
IEBGENER.) For other types of pinned data,
reaccess and try to destage or discard.
SET NVS ON
-PINNED DATA: Probable cause for the NVS
being in pending state is pinned data. To
activate the NVS, the pinned data for each
volume must first be discarded (SETCACHE
DISCARDPINNED). If the volume is a DASD
fast write volume and in pending state, the
data can be discarded with a SETCACHE
DASDFASTWRITE PENDINGOFF. A PINNED
TRACK REPORT can be generated
(LISTDATA PINNED), and then the data set
with pinned retriable or non-retriable tracks can
data set are IEBCOPY and IEBGENER.) For
other types of pinned data, reaccess and try to
destage or discard.
-PINNED DATA OR NVS FAILED: If the DASD
FAST WRITE volumes show pending in the
STATUS REPORT or NVS is failed (which is
caused by a malfunction or NVS being taken
offline by a SR action), a SETCACHE
DASDFASTWRITE PENDINGOFF can be
issued for the devices which are pending (have
pinned data). A PINNED TRACK REPORT can
be generated (LISTDATA PINNED), and then
the data set with pinned retriable or
non-retriable tracks can be copied to a device
prior to discarding the pinned data. (Possible
utilities for copying the data set are IEBCOPY
and IEBGENER.) For other types of pinned
data, reaccess and try to destage or discard.
-DISABLED FOR MAINTENANCE: To activate
the NVS, rerun the SETCACHE command
when the NVS is no longer disabled for
maintenance (probable SR action to enable).
SET NVS OFF
-NVS INITIALIZING: Rerun the SETCACHE
job when the NVS has finished initialization.
SET DASD FAST WRITE ON
-NVS FAILED: Probable cause is malfunction
or SR action. This message may occur after a
duplex pair has been ended (with a
RESETTOSIMPLEX parameter). If DASD fast
write is on prior to ending a duplex pair,
IDCAMS will attempt to set DASD fast write off
and then restore to active status after the end.
This is done to assure that the pairs are true
copies.
SET DASD FAST WRITE OFF
-DASDFASTWRITE FAILED: This is caused by
an incorrect device ID (DASD fast write failed)
and the device is DASD fast write active.
-INVALID DFW DATA FOR SYNC: There is

data for the device in the failed nonvolatile
storage and the data is not in cache storage.
This condition prevents the scheduling of
destage of all DASD fast write data for the
device, and the setting of indicators to prevent
further DASD fast write activity on the device.
SET DASD FAST WRITE PENDINGOFF
-WRONG COMMAND ISSUED: The
SETCACHE DASDFASTWRITE OFF command
would probably have resulted in the DASD fast
write being deactivated.
SET CACHE FAST WRITE ON
-PINNED DATA: A PINNED TRACK REPORT
can be generated (LISTDATA PINNED), and
then the data set with pinned retriable or
non-retriable tracks can be copied to a device
prior to discarding the pinned data. (Possible
utilities for copying the data set are IEBCOPY
and IEBGENER.) For other types of pinned
data, reaccess and try to destage or discard.
ESTABLISH A DUPLEX PAIR
-NVS OFFLINE: Issue a SETCACHE NVS ON
to activate NVS.
-CACHE OFFLINE: Issue a SETCACHE
SUBSYSTEM ON to activate subsystem
storage.
-PRIMARY DEVICE NOT SIMPLEX: A volser
was selected which is already being used for
dual copy operations. Reissue the command
with a non-duplex pair volser specified.
-SECONDARY DEVICE NOT SIMPLEX: A
device ID was selected which is already being
used for dual copy operations. Reissue the
command with a non-duplex pair device ID
specified.
-CACHING ACTIVE: Although IDCAMS will set
device caching off to both devices prior to
attempting to establish a duplex pair, if device
caching is inadvertently set back on (perhaps
by another host) or is in pending state this
cause is given. Note that IDCAMS restores the
device caching state of the duplex pair to the
original state of the primary device after the
establish duplex pair channel program has run.
-PRIMARY AND SECONDARY ARE SAME
DEVICE: The volser of the requested primary
and the device id of the requested secondary
are the same device.
-DEVICE RESERVED OR BUSY TO
ANOTHER PROCESSOR: An attempt to
establish a duplex pair has failed because the
target secondary device was busy when the
3990 attempted to claim the volume. A possible
reason for the target secondary to be busy is
that the device is not offline to ALL attached
hosts and there is host activity using this

volume. (Operator commands like a DEVSERV
against the target volume will cause host I/O to
the volume.) Synchronize the target secondary
device on all attached hosts and reissue the
command.
-PATH-GROUPS ARE NOT COMPATIBLE:
The 3990 command rejected the establishment
of the duplex pair with sense indicating that the
proposed secondary device for the duplex pair
has at least one path group established, and
that the primary and secondary devices do not
have the same path groups established on all
channel paths. A possible reason for this is that
some other host attached to this device had
the device ONLINE and another non-MVS host
attached to the secondary has a path group
established for the secondary. Note that this
3990 check is to help insure that the secondary
is in the proper state; that is, either no path
group exists or the path group of the
secondary is the same as that for the primary.
Insure that the target secondary device is
OFFLINE to all attached MVS hosts. If
non-MVS hosts are attached to the device
insure that the path groups for the secondary
device are resigned or equal to the primary.
REESTABLISH A DUPLEX PAIR
-PINNED DATA: The suspended duplex
primary volume has pinned data. A PINNED
data set are IEBCOPY and IEBGENER.)
Discard using DISCARDPINNED or
DASDFASTWRITE PENDINGOFF (depending
on the circumstances).
to activate NVS.
storage.
-DEVICE IS NOT A PRIMARY: The volser
specified as the primary volume is not part of a
duplex pair or is the secondary volume of a
duplex pair. Probable user error. Correct the
volser and reissue the command. volser.
-ALTERNATE DEVICE NOT SIMPLEX: A
device ID was selected which is already being
used for dual copy operations. Reissue the
command with a non-duplex pair device ID
specified.
-CACHING ACTIVE: Although IDCAMS will set
device caching off to the alternate device prior
to attempting to establish a duplex pair, if
517

volser and reissue the command.
device caching is inadvertently set back on

(perhaps by another host) or is in pending
state this cause is given.
-PRIMARY AND ALTERNATE ARE SAME
DEVICE: The volser of the requested primary
and the device ID of the requested alternate
are the same device.
-DEVICE RESERVED OR BUSY TO
ANOTHER PROCESSOR: An attempt to
establish a duplex pair has failed because the
target alternate device was busy when the
3990 attempted to claim the volume. The target
alternate could be busy because the device is
not offline to all attached hosts and there is
host activity using this volume (operator
commands like a DEVSERV against the target
volume will cause host I/O to the volume).
Synchronize the target alternate device on all
attached hosts and reissue the command.
-PATH-GROUPS ARE NOT COMPATIBLE:
The 3990 command rejected the establishment
of the duplex pair with sense indicating that the
proposed alternate device for the duplex pair
has at least one path group established and
that the primary and alternate devices do not
have the same path groups established on all
channel paths. A possible reason for this is that
some other host attached to the alternate had
the alternate ONLINE and another non-MVS
host attached to this device has a path group
established for the device. Note that this 3990
check is to help insure that the alternate is in
the proper state; that is, either no path group
exists or the path group of the alternate is the
same as that for the primary. Insure that the
target alternate device is OFFLINE to all
attached MVS hosts. If non-MVS hosts are
attached to the device insure that the path
groups for the alternate device are resigned or
equal to the primary.
ESTABLISH A DUPLEX PAIR FROM SUSPENDED
DUPLEX
-PINNED DATA: The suspended duplex
primary volume has pinned data. A PINNED
data set are IEBCOPY and IEBGENER.)
Discard using DISCARDPINNED or
DASDFASTWRITE PENDINGOFF (depending
on the circumstances).
to activate NVS.
storage.
518
TERMINATE A DUPLEX PAIR

-PINNED DATA: DASD fast write is in pending
state. A PINNED TRACK REPORT can be
generated (LISTDATA PINNED), and then the
data set with pinned retriable or non-retriable
tracks can be copied to a device prior to
discarding the pinned data. (Possible utilities
for copying the data set are IEBCOPY and
IEBGENER.) Discard using DISCARDPINNED
or DASDFASTWRITE PENDINGOFF
(depending on the circumstances).
SUSPEND A DUPLEX PAIR
-PAIR ALREADY SUSPENDED: A request to
suspend an already suspended duplex pair
results in no action being taken.
-SUSPENDPRIMARY TO DUPLEX PENDING
PAIR: A request to suspend a duplex pair with
the primary as the suspended device while
establishing a duplex pair is pending. The
SUSPENDPRIMARY command is ended with
no action taken.
For a LISTDATA request, action and cause can be
replaced with the following values:
Action Cause
READ PINNED TRACK DATA
-CACHE STORAGE IS FAILED OR
UNAVAILABLE: An attempt to read pinned
track data was unsuccessful because cache
storage was not available or pending.
volser
action
The specified action.
cause
The cause of the error.

Application Programmer Response: Resubmit when
the state changes to allow the command. Most can be
checked with LISTDATA...STATUS. In the case of a
user error, correct the volser or other erroneous

condition and reissue the command.
Source: DFSMSdfp
IDC31607I
THE SPECIFIED COMMAND REQUIRES

ALTER AUTHORIZATION. THE USER
DOES NOT HAVE SUFFICIENT ACCESS
AUTHORITY FOR devid TO BE
INCLUDED IN A DUPLEX PAIR
Explanation: A SETCACHE SETSECONDARY

command or a SETCACHE REESTABLISHDUPLEX
command was issued. The volume serial of offline
volume which is either the secondary or the alternate
volume is not equal to the volume serial of the primary
volume. The requestor does not have DASDVOL ALTER
authority for the offline volume specified.
devid
The device identification.
Source: DFSMSdfp
IDC31609I
DEVICES SELECTED TO FORM A

DUPLEX PAIR ARE NOT
COMPATIBLE-reason
Explanation: The SETCACHE command requiring

compatible devices was unsuccessful. Commands
requiring compatible devices are:
v SETSECONDARY (establish a duplex pair).
v REESTABLISHDUPLEX (reestablish a duplex pair
using an alternate device).
reason The reason for the error, as follows:

v THE DEVICES ARE NOT THE SAME
GEOMETRY AND CAPACITY
v THE DEVICES ARE NOT IN THE SAME
LOGICAL DASD SUBSYSTEM
Application Programmer Response: Select
compatible devices and rerun the command.
Source: DFSMSdfp
IDC31610I
THE REQUESTED ASYNCHRONOUS

OPERATION {COMPLETED IN ERROR |
FAILED}
Explanation: A SETCACHE command requesting an

asynchronous operation was unsuccessful. The
asynchronous operations manager returned a return
code 8, with reason code 12 (COMPLETED IN ERROR)
or reason code 16 (FAILED).
asynchronous operation completed, but during the

operation sense data was offloaded to an attached host
with the environmental data present bit set. This sense
data indicates the errors that occurred with the
asynchronous operation.
For the FAILED condition, the asynchronous operation
did not complete. This error may be accompanied by an
I/O error message on the console relating to the specific
error. There may also be environmental sense data
present that could help identify this error.
System Action: The asynchronous operation in the
storage control has completed. IDCAMS processing
continues.
Application Programmer Response: Examine a
merged LOGREC from all hosts attached to the storage
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
volume within an allocated data set. From this
information you can determine the severity of the error.
Note that there may be a collection of environmental
sense data caused by this one asynchronous operation.
Additional information can be gathered by issuing the
DEVSERV command to the device and examining
output from message IEE459I. After completing this
examination take the appropriate actions to correct the
specific data set or entire volume error. If all errors were
not in allocated space on the volume, the impact of the
error may be minimal. Once you have made these
corrections, the volume should be ready to be
completely used. Note that the asynchronous operation
need not be repeated because it did complete and the
state of the subsystem or volume should be as desired.
For the FAILED condition, examine the sense data
associated with the specific error as well as any I/O
messages that may have appeared on the system
console. Environmental sense data may also be helpful
in determining the reason for the asynchronous
operations failure. Additional information can be
gathered by issuing the DEVSERV command to the
device and examining output from message IEE459I.
After completing this examination take the appropriate
actions to correct the problem, and then attempt to
reissue the asynchronous operation using the IDCAMS
utility.
Source: DFSMSdfp
IDC31611I
WHEN CREATING A DUPLEX PAIR THE

{SECONDARY | ALTERNATE} DEVICE
MUST BE OFFLINE
Explanation: A SETCACHE request which requires

that certain volumes be offline was unsuccessful. The
following requests require the specified volume to be
offline:
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)

requires the alternate volume to be offline.
IDC31616I
REINITIALIZE FAILED device IS NOT

OFFLINE
Application Programmer Response: Vary the

secondary/alternate device offline (in ALL hosts
attached to the subsystem) and rerun the command.
Explanation: A SETCACHE REINITIALIZE request

requires that all devices attached to the subsystem be
offline. This message is issued for the first volume
found to be not offline.
Source: DFSMSdfp
device
IDC31612I
NO PATHS ARE AVAILABLE TO THE

REQUESTED SD; TO SET ON, ISSUE A
SETCACHE SUBSYSTEM ON
Explanation: This message is applicable to a 3880

Model 21. When a storage director is varied online a
SETCACHE SUBSYSTEM ON is required to set the
storage director on.
Application Programmer Response: Vary the
storage director online and issue a SETCACHE
SUBSYSTEM ON.
Source: DFSMSdfp
The device identifier (unit number) for one of

the devices attached to the subsystem.

command after all volumes have been varied offline.
Source: DFSMSdfp
IDC31617I
THE COMMAND command IS

COMPLETE FOR {THE SUBSYSTEM
CONTAINING} volser | unitaddr
Explanation: The I/O operation for the SETCACHE

command completed successfully.
IDC31615I
THE SPECIFIED DEVICE ID device WAS

NOT FOUND OR IS NOT CONNECTED
TO A CACHING CONTROLLER.
Explanation: A command requiring I/O to an offline

device was issued and could not be run. The specified
device identifier was not found or the device was
connected to a non-caching controller. Commands
which allow I/O to offline devices are:
v LISTDATA ACCESSCODE
v LISTDATA STATUS
v SETCACHE NVS OFF
v SETCACHE REINITIALIZE
v SETCACHE RESETTOSIMPLEX
v SETCACHE SUBSYSTEM OFF
v the secondary device ID in SETCACHE
SETSECONDARY
v the alternate device ID in SETCACHE
REESTABLISHDUPLEX
device
The device identifier.

command using a device identifier (unit number)
attached to a supported subsystem for which the
request is to be run.
Source: DFSMSdfp
520
command
v SUSPENDPRIMARY
v SUSPENDSECONDARY
v SETSECONDARY
v DISCARDPINNED
v REINITIALIZE
v RESETTODUPLEX
v RESETTOSIMPLEX
v REESTABLISHDUPLEX
v CACHEFASTWRITE ON
v CACHEFASTWRITE OFF
v DASDFASTWRITE ON
v DASDFASTWRITE OFF
v DASDFASTWRITE PENDINGOFF
v DESTAGE
v NVS ON
v NVS OFF
volser
unitaddr
The unit address.
System Action: The system sets the return code to 0.
Source: DFSMSdfp
IDC31652I
OBJECT NOT SUPPORTED IN CIMODE
Explanation: An attempt was made to import an

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.

Application Programmer Response: You must either
create the portable data set in record mode, or change
its attributes to an ESDS cluster with no alternate
indexes.
Source: DFSMSdfp
IDC31662I
UNAUTHORIZED CALLER REQUESTED

AN AUTHORIZED FUNCTION
Explanation: Access method services was called to

IMPORT a catalog using the problem program interface.
However, the caller was not running in an authorized
mode.
System Action: The request is ended.
IDC31655I
keywd PARAMETER INVALID WITH

ENTRY TYPE
Explanation: The specified keyword is improper for

the type of object being imported.
Application Programmer Response: Obtain APF

authorization for the caller of access method services
using the problem program interface.
Source: DFSMSdfp
keywd
The specified keyword.

proper parameters for the type of object being imported
and retry the command.
Source: DFSMSdfp
IDC31700I
VSAM OPEN ERROR
Explanation: An error during OPEN processing

prevents testing of the data set.
System Action: Processing ends.
Application Programmer Response: For more
information, see message IDC3009I, which immediately
Source: DFSMSdfp
IDC31658I
INVALID AUTHORIZATION TO BYPASS

ACS PROCESSING
Explanation: A caller supplied a pointer to the ACERO

in the AMS processor invocation argument list; that
pointer ordinarily causes the caller to bypass ACS
processing. However, the caller was not APF
authorized, and thus cannot bypass ACS processing.
command.
Application Programmer Response: Either clear the
ACERO pointer in the AMS processor invocation
argument list, or reissue the command in an
APF-authorized state.
IDC31701I
INSUFFICIENT VIRTUAL STORAGE

AVAILABLE
Explanation: Virtual storage is insufficient to continue

processing.
System Action: The data set is closed, and
processing ends.
region size and re-run.
Source: DFSMSdfp
IDC31702I
Source: DFSMSdfp
DATA SET REQUESTED IS NOT A

VSAM KSDS CLUSTER
Explanation: At open time it is found that the data set

is not a key-sequenced data set.
IDC31660I

processing ends.
INVALID CATALOG NAME ON

OUTDATASET OR OUTFILE.
Explanation: The catalog name on the out data set or

outfile does not match the catalog name in the exported
copy. This is an error.

are using the correct data set name.
Source: DFSMSdfp
System Action: The system ends command

processing.
IDC31703I

catalog name on the out data set or outfile. Run the job
again.
Explanation: The data set is in create mode and,

therefore, cannot be tested.
Source: DFSMSdfp
DATA SET REQUESTED FOUND TO BE

IN CREATE MODE

processing ends.
521
are using the correct data set name.

Source: DFSMSdfp
IDC31704I
DATA SET IS ALREADY OPEN FOR

OUTPUT OR WAS NOT CLOSED
CORRECTLY
Explanation: The data set is already OPEN for output

by a user on another system, or was not previously
closed.
processing ends.
Application Programmer Response: If the data set is
OPEN for output, it must be closed before running
EXAMINE. If it is not OPEN for output, you must run
verify (via the VERIFY command) before running
EXAMINE.
attempt to determine the cause of the problem. See

OS/390 DFSMSdfp Diagnosis Guide for information on
dump points.
Source: DFSMSdfp
IDC31708I
ERROR OBTAINING FORMAT ONE

DSCB FROM VTOC
Explanation: An error other than 'DSCB Not Found'

occurred when EXAMINE tried to obtain a Format-1
DSCB for the cluster.
dump points.
Source: DFSMSdfp
Source: DFSMSdfp
IDC31709I
IDC31705I
DATATEST NOT PERFORMED DUE TO

SEVERE INDEXTEST ERRORS
Explanation: You have requested both INDEXTEST

and DATATEST. Errors encountered during the index
test are of such severity that further testing of the data
component might not yield usable information.
processing ends.
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
NOINDEXTEST DATATEST parameters.
Source: DFSMSdfp
ERROR OBTAINING VOLUME

INFORMATION
Explanation: Volume information for the specified

entry name cannot be obtained.
attempt to determine the cause of the problem. Refer to
dump points.
Source: DFSMSdfp
IDC31710I
CI ACCESS ERROR
Explanation: An I/O error has been encountered while

attempting to read a control interval.
IDC31706I
VSAM CONTROL BLOCK ERROR
Explanation: At least one field within a VSAM control

block built by OPEN contains incorrect data.
processing ends.
dumps points.
Source: DFSMSdfp
IDC31707I
ERROR OBTAINING TSO QUALIFIER
Explanation: The Time Sharing Option/Extensions

(TSO/E) user id cannot be prefixed to the unqualified
data set name.
522

dump points.
Source: DFSMSdfp
IDC31750I
IMPROPER ENVIRONMENT FOR

COMMAND
Explanation: During processing of a command,

access method services detected that the environment
was improper for that command. Processing occurred in
either a Time Sharing Option (TSO) or TSO/Extensions
(TSO/E) release 1 environment; the command requires
a TSO/E release 2 or higher.
command.
Application Programmer Response: If TSO/E
release 2 or higher is installed, run the command in the
foreground as a TSO command.

Source: DFSMSdfp
Detecting Module: IDCTC01
IDC31751I
COMMAND ABNORMALLY
TERMINATED. TMP ABEND CODE IS
code
Explanation: The terminal monitor program (TMP)

indicated to access method services (AMS) that a
command abnormally ended.
code

Source: DFSMSdfp
IDC31810I
The abend code.

Source: DFSMSdfp
Detecting Module: IDCTC01
IDC31801I
INVALID FORMAT FOR OUTPUT DATA

SET name
Explanation: Data set had an incorrect data set

organization or an incorrect record format.
name

system programmer.
The data set name.

data set has a data set organization of physical
sequential and a record format of V or VB.
Source: DFSMSdfp
IDC31802I
LOAD OF MODULE name WAS

UNSUCCESSFUL. ABEND CODE IS xx REASON CODE IS reason-code
Explanation: An attempt was made to perform a

function without proper authority to
STGADMIN.IDC.DCOLLECT.
Application Programmer Response: Obtain proper
facility class authorization to
STGADMIN.IDC.DCOLLECT.
Source: DFSMSdfp
IDC31863I
OFFSET MISSING OR SPECIFICATION

INVALID IN OFFSET PAIR number
REASON CODE IS reason-code
Explanation: INSERTSHIFT was specified on an

access method services (AMS) PRINT or REPRO copy
of a data set operation. AMS, while checking offset
values, detected one of the following:
Code
Reason
One or more pairs have the offset missing.
The difference between the first offset and the

second offset is not an even number.
12
The first offset was specified as greater than

the second offset.
Explanation: The named module could not be loaded

into system storage.
INSUFFICIENT FACILITY CLASS

AUTHORIZATION TO PERFORM
FUNCTION
number
The offset pair in which the error was

detected.
The abend code.
reason-code
The reason code.
The reason code.

code is 12.
name
The name of the module.
xx
reason-code
System Action: Processing provided by the named

module is not performed.
523
specification of the offset pairs in the INSERTSHIFT

keyword. Make sure offset1 is not greater than offset2
in any offset pair and that the difference between
offset1 and offset2 is an even number.
Source: DFSMSdfp
IDC31864I
OFFSET PAIR number1 RANGE

OVERLAPS OFFSET PAIR number2

access method services (AMS) PRINT or REPRO copy
of a data set operation. AMS, while checking offset
values, detected that a set of offset pairs had
overlapping ranges. This would cause the data to fail
during DBCS criteria checking.

IDC31881I
UNBIND NOT SET FOR dsname
Explanation: A SHCDS FRUNBIND command failed

for data set dsname. The explanation for the command
failure follows the message.
Source: DFSMSdfp
IDC31882I
BIND NOT SET FOR dsname
Explanation: A SHCDS FRBIND command failed for

data set dsname. The explanation for the command
Source: DFSMSdfp
number1 and number2

The offset pairs with overlapping values.

code is 12.
IDC31883I

offset pair specifications in the INSERTSHIFT keyword.
You should make sure that offset pair values do not
overlap.
Explanation: A SHCDS FRRESETRR command failed

for data set dsname. The explanation for the command
Source: DFSMSdfp
Source: DFSMSdfp
IDC31883I RECOVERY NOT RESET

FOR dsname

IDC31865I
OFFSET offset IN OFFSET PAIR number

EXCEEDS MAXIMUM RECORD
LENGTH

access method services (AMS) REPRO copy of a data
set. AMS, while comparing offsets and target data sets
(maximum) record length, discovered that the offset
exceeds the maximum record length of the target data
set.
IDC31884I
UNBOUND LOCKS NOT DELETED FOR

dsname
Explanation: A SHCDS FRDELETEUNBOUNDLOCKS

command failed for data set dsname. The explanation
for the command failure follows the message.
Source: DFSMSdfp
offset
The offset.
number The offset pair.

code is 12.
offset pair specifications in the INSERTSHIFT keyword.
Make sure that an offset value does not exceed the
maximum record length of the target data set.
Source: DFSMSdfp
IDC31880I
RECOVERY NOT SET FOR dsname
Explanation: A SHCDS FRSETRR command failed for

data set dsname. The explanation for the command
Source: DFSMSdfp
524
IDC31885I
NON-RLS UPDATE NOT PERMITTED

FOR dsname

RLS mode has failed to be permitted access in
non-RLS mode. The explanation for the command
Source: DFSMSdfp
IDC31886I
NON-RLS UPDATE NOT DENIED FOR

dsname

non-RLS mode is not denied access in non-RLS mode.
Source: DFSMSdfp
IDC31887I
SUBSYSTEM subsystem NOT

REMOVED
Explanation: subsystem was not disconnected from

SMSVSAM. The messages that follow explain the
reason the subsystem was not removed.
System Programmer Response: Be sure the correct
subsystem name is specified.
Source: DFSMSdfp
IDC31888I
UNEXPECTED ERROR FROM

SMSVSAM SERVER DIAGNOSTIC
INFORMATION: RC = return-code RS =
reason-code
Explanation: The SMSVSAM address space returned

error indicated by the return-code and reason-code
values.
User Response: Contact the system programmer
regarding procedures to start the SMSVSAM address
space.
Operator Response: Contact the system programmer
space.
system programmer regarding procedures to start the
SMSVSAM address space.
DFSMSdfp Diagnosis Reference for providing
documentation for SMSVSAM problem.
Source: DFSMSdfp
Detecting Module: IDCSH01, IDCSH02, IDCSH03,
IDCSH04, IDCSH05, IDCSH06, IDCSH07, IDCSH08,
IDCSH14, IDCSH15
IDC31889I
SMSVSAM SERVER NOT AVAILABLE
Explanation: The SMSVSAM address space is not

available to handle the request.
User Response: Contact the system programmer
space.
Source: DFSMSdfp
IDCSH14, IDCSH15
IDC31890I
DATASET NOT LISTED
Explanation: The SMSVSAM address space did not

contain information related to the data set requested.
Can be issued also in response to SHCDS
sub-commands LISTDS, LISTSUBSYS, or
LISTSUBSYSDS. Data sets are not listed if they are not
currently open for RLS mode or do not have related
lock information being maintained in the SMSVSAM
address space.
Application Programmer Response: Ensure the data
set name has been specified correctly. Verify the related
catalog has connectivity to the system being used for
the SHCDS command. Contact system programmer for
SMSVSAM diagnosis instructions.
DFSMSdfp Storage Administration Reference for
requirements.
Source: DFSMSdfp
IDCSH06
IDC31891I
SUBSYSTEM NOT LISTED

contain information related to the subsystem requested.
LISTSUBSYSDS. Subsystems are not listed if they are
not currently active or do not have related lock
information being maintained in the SMSVSAM address
space.
Application Programmer Response: Ensure the
subsystem has been specified correctly. Contact system
programmer for SMSVSAM diagnosis instructions.
requirements.
Source: DFSMSdfp
Operator Response: Contact the system programmer

space.

IDCSH05, IDCSH06

system programmer regarding procedures to start the
SMSVSAM address space.
IDC31892I
System Programmer Response: Make the

SMSVSAM address space available. See the OS/390
requirements.
INSUFFICIENT USER AUTHORIZATION

FOR SHCDS COMMAND
Explanation: To use the SHCDS List subcommands,

READ authority to the FACILITY class profile
STGADMIN.IGWSHCDS.REPAIR is required. UPDATE
authority to this FACILITY class profile is required for
the FR* subcommands, the PERMITNONRLSUPDATE,
525
DENYNONRLSUPDATE, and REMOVESUBSYS

subcommands.

requirements.
For the CFREPAIR and CFRESET subcommands,

ALTER authority is required to the specified catalog.
Source: DFSMSdfp
The following additional authority is required:

v For the FR*, PERMITNONRLSUPDATE,
DENYNONRLSUPDATE subcommands, UPDATE
authority to the base cluster.
v For the REMOVESUBSYS subcommand, UPDATE
authority to the RACF SUBSYSNM class.
Application Programmer Response: Obtain the
proper authorization for the command.
System Programmer Response: Provide
authorization for using the SHCDS command.
Source: DFSMSdfp
Detecting Module: IDCSH01, IDCSH15, IDCSH16
IDC31893I
NO SUBSYSTEM INFORMATION
FOUND

contain information related to the subsystem requested.
LISTSUBSYSDS. Subsystems are not listed if they are
not currently active or do not have related lock
information being maintained in the SMSVSAM address
space.
Application Programmer Response: Ensure the
subsystem has been specified correctly. Contact system
programmer for SMSVSAM diagnosis instructions.
requirements.
IDC31895I
DATA SETS UNSUCCESSFULLY

PROCESSED
Explanation: An SHCDS CFREPAIR, CFRESET, or

CFRESETDS command was issued. For each data set
that was not processed, the following information is
presented:
v The data set name
v The reason that the data set was not processed
return and reason codes and determine if any further
action needs to be taken.
Source: DFSMSdfp
IDC31896I
INSUFFICIENT USER AUTHORIZATION

FOR CATALOG UPDATE
Explanation: The user does not have sufficient

authority to the catalog that was specified in the SHCDS
CFREPAIR, CFRESET, or CFRESETDS command.
proper authorization for the command.
System Programmer Response: Provide
authorization for using the SHCDS command.
Source: DFSMSdfp
IDC31897I
Source: DFSMSdfp
CATALOG MUST BE ICF FOR SHCDS

COMMAND

IDCSH05, IDCSH06
Explanation: An SHCDS CFREPAIR, CFRESET, or

CFRESETDS command was issued against a catalog
that is not an ICF catalog.
IDC31894I

name of an ICF catalog as the parameter of the
INDATASET option.
NO DATASET RECOVERY
INFORMATION FOUND

contain lock recovery information related to the data set
requested. Can be issued also in response to SHCDS
sub-commands LISTRECOVERY. Data sets are not
listed if they do not have retained or lost locks, do not
have non-RLS permit status, or not marked with forward
recovery required.
Application Programmer Response: Ensure the data
set or data set qualifiers have been specified correctly.
Contact system programmer for SMSVSAM diagnosis
instructions.
526
Source: DFSMSdfp
IDC31898I
SECURITY VERIFICATION FAILED FOR

DATA SET
Explanation: Requestor does not have sufficient

authorization to perform function on the specified data
set.
required authorization for the data set.
Source: DFSMSdfp
IDCSH10, IDCSH11

value and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCCR01
IDC31900I
date-field
Explanation: A date was incorrectly specified when

using the IDCAMS ALTER or CREATE commands. Date
is expected in the format YYYY-MM-DD.
date-field
The specific field in error. Possible values include:
YEAR
The year is not valid. Acceptable values

are between 0000 - 2155.
MONTH
The month is not valid. Acceptable values
are between 00 - 12.
DAY
The day is not valid. Acceptable values are

between:
Value
Corresponding Dates
01 - 28 for February (not a leap year).

01 - 29 for February (leap year).
parameter1 IS GREATER THAN

parameter2
Explanation: The value specified for an IDCAMS

CREATE or ALTER command will cause the value for
parameter1 to exceed parameter2.
parameter1
Parameter value that should be lesser than or
equal to parameter2.
parameter2
Parameter value that should be greater.
command.
appropriate parameter to ensure that the value of
parameter2 is greater than or equal to the value of
parameter1.
Source: DFSMSdfp
01 - 30 for April, June, September, and

November
01 - 31 for January, March, May, July,

August, October and December.
IDC31950I
32
Explanation: There were no locks found for the

FRBIND/FRUNBIND request for the data set.
which means never expire (date

of 1999-12-32).
HYPHEN
The required hyphen is missing from either
the fifth or the eighth position in date-field.
command.
System Programmer Response: Correct the date
and rerun the job.
Source: DFSMSdfp
IDC31901I
IDC31903I
INCORRECT VALUE FOR parameter
Explanation: An invalid value was specified for the

named parameter. See DFSMS/MVS Access Method
Services for ICF for more information about valid
values.
NO LOCKS TO BIND/UNBIND
Application Programmer Response: Be sure the

correct data set has been specified. Verify lock status
for the data set with the SHCDS LISTDS subcommand.
Source: DFSMSdfp
IDC31951I
DATA SET IS OPEN. TRY AGAIN LATER
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.
Once the data set is no longer in use execute the
command.
Source: DFSMSdfp
IDCSH10, IDCSH11, IDCSH12, IDCSH13
parameter
The named parameter.
command.
527
IDC31952I
NOT SMS-MANAGED VSAM DATA SET
Explanation: The SHCDS subcommand requires that

the object of the command be an SMS-managed VSAM
data set.
data set is specified correctly.
Source: DFSMSdfp
IDCSH10, IDCSH11
IDC31953I
IDC31957I
SUBSYSTEM NOT FOUND
Explanation: The requested subsystem was not

found.
subsystem is specified correctly. Use the SHCDS
LISTSUBSYS or LISTSUBSYSDS subcommands to
verify the subsystem status.
Source: DFSMSdfp
IDCSH05, IDCSH06, IDCSH11, IDCSH12, IDCSH13
NO UNBOUND LOCKS TO DELETE
Explanation: No unbound locks were found for the

data set.
Source: DFSMSdfp
IDC31958I
SUBSYSTEM CURRENTLY ACTIVE
Explanation: The requested subsystem was active

with the SMSVSAM address space.
subsystem is specified correctly. Use the SHCDS
LISTSUBSYS or LISTSUBSYSDS subcommands to
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

the data set.
IDC31959I

Explanation: The FR* command failed and the

diagnostic-error-data was returned. return-code and
reason-code values.
Source: DFSMSdfp
IDC31955I
DATA SET IS NOT RECOVERABLE
Explanation: The data set was not recoverable.

Redefine the data set or use the ALTER command to
add the LOG(ALL) OR LOG(UNDO) option for the data
set.
Source: DFSMSdfp
IDC31956I
DATA SET NOT FOUND
Explanation: The catalog search failed or the data set

is not active within SMSVSAM.
Source: DFSMSdfp
IDCSH11, IDCSH12, IDCSH13
528
ERROR DATA: Xdiagnostic-error-data

OS/390 DFSMSdfp Diagnosis Reference for causes of
the failure.
System Programmer Response: Refer to the OS/390
DFSMSdfp Diagnosis Reference for providing
documentation for SMSVSAM problem.
Source: DFSMSdfp
IDCSH10, IDCSH11
Chapter 15. IEA Messages

IEA000A
SWAP FROM xxx TO zzz FAILED,

RETRY (R) OR TERMINATE (T)
Explanation: The 3851 ERP (error recovery

procedure) detected that the dynamic device
reconfiguration (DDR) swap service could not swap the
primary mass storage control (MSC) to the alternate
MSC. Previous operator messages indicate the reason
for the DDR swap service failure. The operator can retry
the swap or end the swap. If the swap operation fails
consistently, a permanent I/O condition exists.
xxx
zzz
Two consecutive commas or a field containing blanks or

asterisks in the message text indicates that a field could
not be determined or is contained on the next or
previous line of the message. If the sense data to be
inserted in the sens field of the message text exceeds 6
bytes, the sens field and the optional field that follows
(dcbctfd or opxxterm or cylntrck) do not appear on the
first line. Consecutive commas appear instead. The
system then issues a second line that includes the
device number of the device, the sense data, and,
optionally, dcbctfd, opxxterm, or cylntrck. In other words,
if the sense data exceeds six bytes, the message has
this format:
The low number in the range.
IEA000I
The high number in the range.
IEA000I
System Action: The system waits for the operators

reply (see the operator response for this message).
Operator Response: Retry (R). If the error continues
to occur, end (T).
If the swap is ended, the system places both MSCs
offline. The system continues processing without the
MSCs and probably without the MSS (mass storage
system) functions.
Because two separate WTO instructions issue the two

messages shown above, it is possible that one or more
unrelated messages could appear between the first
message and the second message.
dev
Device number of the device or line address of the
telecommunication device, in hexadecimal. If the
error is a channel program check (CPC) or channel
protection check (PRC), this field will be zeros; the
error was not caused by a hardware error on the
device, but was caused by the program issuing the
I/O.
If the error continues to occur, it is probably because of

a hardware problem. The system issues message
IEA000I. Follow installation procedures to take
corrective action. Notify the system programmer.
Source: DFSMSdfp
Detecting Module: ERPs. IECIOSCN, IGE0025C
IEA000I
dev,err,cm,stat,sens,
{dcbctfd|opxxterm|cylntrck}
[ser],jjj[,hh.mm.ss]
--or--
dev,err,cm,stat - MESSAGE EXIT

UNAVAILABLE - [exitname]
Explanation: For the first format of the message, an
uncorrectable input/output error was detected by the I/O
supervisor, the basic telecommunication access method
(BTAM), or the telecommunication access method
(TCAM) routine. In systems with the graphics access
method (GAM), unit checks and conditions that require
operator intervention indicate devices that do not exist
or that were included at system generation time but not
attached to the system.
For the second format of the message, the message
writer was unable to locate the routine that builds the
device dependent portion of the above message. If the
name of the routine is available, it is included in the
message as exitname.
dev,err,cm,stat,,,[ser],jjj
[,hh.mm.ss]
dev,,,sens {,dcbctfd|,opxxterm|
,cylntrck}
err Description of the error based on status and sense

information:
DSN - data streaming is not operational.
RST - the I/O Restart routine was entered by
Alternate CPU Recovery, the Channel Check
Handler, or the Missing Interrupt Handler.
SAF - Staging Adapter failure. The Staging
Adapter controlling the DASD address specified
has lost communications with the mass storage
control.
UEX - unit exception.
MSS users should check the possible values of err
and appropriate responses in the Operator
Response part of this message description.
cm Command code, in hexadecimal, of the channel

command word (CCW) being executed when the
error occurred. If the channel command word
cannot be found, this field appears as **.
stat
Status portion, in hexadecimal, of the channel
status word (CSW).
sens
The first byte, in hexadecimal, describes a unit
529
check type error condition (for telecommunication

devices). The second byte, in hexadecimal,
contains sense information resulting from the
execution of a diagnostic write/read or read/skip
command (from TCAM) which ended with a unit
check status (2701 data adapter unit). For other
devices, these same two bytes will appear, in
hexadecimal, if a unit check condition is indicated in
the stat field. For devices that give more than two
bytes of sense information, this field will also
contain the remaining sense bytes, in hexadecimal.
For devices which give more than 6 sense bytes,
this field continues on the second line of the
message. For DASD devices, this field will contain
the 8 sense bytes for program errors or 24 sense
bytes for equipment and data checks. For the 3340,
this field will contain 24 sense bytes for seek
checks.
The message on the system console reflects the
sense-byte information from the last entry for direct
access devices; the sense-byte information located
in the logrec data set data reflects the data from
the initial error condition.
debctfd
Record count, in hexadecimal, not including label
records. This field appears only for magnetic tape
and indicates the count of the record preceding the
error record.
opxxterm
TP operation code, in hexadecimal, describing the
type of channel command word (CCW) being
executed when the error occurred. xx is not used,
but is followed by the terminal identification
characters, in hexadecimal. It may be either two
bytes or one byte, depending on the terminal type.
If it is one byte, it is left justified. If a dial line is
being used with TCAM, the last four digits of the
dial number are provided.
cylntrck
Address, in hexadecimal, of the cylinder (cyln), and
the track (trck) where the error occurred. When an
error occurs while trying to obtain this data, the last
seek address is substituted. This field appears only
for certain disk and drum direct access device
errors.
ser Serial number of the volume on which the error
occurred. This field appears only for magnetic tapes
or direct access devices.
jjj
Job name. If the error is a channel program check

(CPC) or channel protection check (PRC), this field
will indicate the program in error.
hh.mm.ss
Time that the message was received in hours,
Operator Response: For all values of err, probable
hardware error. For magnetic tape devices, proceed
with caution in unconditionally accepting the results of
530
the operation. Check that tapes being used by this job

have not been replaced or removed. Each message
should be considered as a potential attention of a
marginal condition.
For other than magnetic tape devices, note that some
abnormal error condition occurred. Depending on the
severity of the error (check status and sense
information) and depending on the installation
requirements, take the appropriate action.
Possible values of err and appropriate responses are as
follows:
v For MSS users, an attempt has been made to write
on a virtual volume that was specified READ ONLY
on the CREATEV command.
v SAF - Staging Adapter failure. Use your path chart to
determine the SSID of the Staging Adapter involved
or use 8nn for the SSID, where nn is byte 25 of the
MSS sense data in this message.
Source: DFSMSdfp
Detecting Module: ERPs
IEA000I
dev,err......hh.mm.ss
Explanation: The processors error recovery

procedures detected an error that requires either a CEM
(CE message), or an SUU (subsystem unit unusable)
message. An equipment check might occur with either
CEM or SUU. Because the system WTO routine can
print only one message, the error recovery procedure
prints the CEM or SUU message and the system WTO
routine prints the remaining message with full sense
data. The error recovery procedure continues recovery
action based on the error condition.
dev
Device number of the mass storage control.
err Description of the error. The values are as follows:

v CEM -- CE message. The Mass Storage Facility
has detected an error important to the service
representative.
v SUU -- Subsystem unit unusable. The Mass
Storage Facility has marked one of its units as
unusable because of an error condition. The
SSID of that unit is in the second half of sense
byte 1 and all of byte 2 in the accompanying
message. The system continues processing;
notify your service representative.
hh.mm.ss
Time that the message was received in hours,
System Action: The error recovery procedure will
continue the recovery action based on the error
condition.
Operator Response: Probable hardware error. Each
message should be considered as a potential attention

of a marginal condition. Depending on the installation
requirements, take appropriate action.
Source: DFSMSdfp
Source: DFSMSdfp
IEA005I

IEA000I
I/O ERR,aaa,bb,cccc,dd00, ffgghhhh
Explanation: This message is sent to the primary

operator control station when TCAM error recovery
procedures fail to correct an I/O error. This message is
in addition to the record of permanent errors that is
created on disk when such an error occurs. TCAM
inserts no line control, not even EOT, into this type of
message. If line control is required, you must see to it
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.
In the message text, the fields, in hexadecimal format,
are:
aaa
Address of the line where the error occurred.
bb The command code as specified in the failing

channel program.
cccc
The status bytes of the channel status word (CCW)
as specified in the input/output block (IOB).
dd The first sense byte as specified in the IOB.

ff
The TP op code as specified in the failing CCW in

the channel program for the last retry attempt.
gg The TP op code of the failing CCW for the first

occurrence of the error.
hhhh
For stations on switched lines, if the station is
known, hhhh is replaced by the last four dial digits,
if assigned. For stations on nonswitched lines, hhhh
is replaced by polling characters for receiving
operations and addressing characters for sending
operations. If the station is on a switched line and
TCAM cannot identify it at the time the error occurs,
hhhh is replaced by the polling characters for
stations on this line. If no polling characters are
assigned, hhhh is replaced by zeros.
System Action: See the explanation.
Operator Response: In some applications, the
generation of the IEA000I message may be faster than
the handling capacity of the primary operator control
station. When the primary operator control station is the
system console, a backlog may create a system queue
area shortage. If allowed to continue without operator
intervention, a serious shortage could result and could
cause a system wait state to be entered. To reduce
generation of these error messages, TCAMs threshold
support should be used.
DATE (AND CLOCK, IF SPECIFIED)

REJECTED. DATE MUST BE
SPECIFIED AS A 4-DIGIT YEAR
Explanation: A 2 digit year was specified.

IEA007I
STATIC SYSTEM SYMBOL VALUES:

&SYSCLONE. = sysclone-text
&SYSNAME. = sysname-text
&SYSPLEX. = sysplex-text
&symbol.-name = symbol-text
.
.
.
symbol.-name = symbol-text
Explanation: This message displays the static system
symbols and their associated substitution texts. The
system issues this message:
v In response to the DISPLAY SYMBOLS command
v During system initialization, when the operator
specifies an initialization message suppression
indicator (IMSI) that does not suppress informational
messages.
&sysclone.-text
The text associated with the &SYSCLONE. static
system symbol. The substitution text for
&SYSCLONE. is defined in the IEASYMxx parmlib
member.
&sysname.-text
The text associated with the &SYSNAME. static
system symbol. The substitution text for
&SYSNAME. is defined in the IEASYMxx or
IEASYSxx parmlib member.
&sysplex.-text
The text associated with the &SYSPLEX. static
system symbol. The substitution for &SYSPLEX. is
defined in the COUPLExx or LOADxx parmlib
member.
symbol.-name
The name of a static system symbol that your
installation defined in the IEASYMxx parmlib
member.
symbol.-text
The substitution text associated with the
installation-defined system symbolname.
The system uses the substitution texts that are
displayed in the message text.
531
System Programmer Response: Determine if the list

of system symbols and substitution texts are
appropriate. If a system symbol is not correct, change
the definition in one of the following parmlib members:
COUPLExx
IEASYMxx
IEASYSxx
LOADxx
v The operator specifies an initialization message

suppression indicator (IMSI) that does not suppress
informational messages.
Source: System initialization (IPL/NIP)
xx The suffix of the first IEASYMxx parmlib member in

the system parameter concatenation.
Detecting Module: IEAVESYM

IEA008I
SYSTEM PARMS FOLLOW FOR xx...x
Explanation: This message displays the IEASYSxx

parmlib members that contain system parameters for
this system image. The IEASYSxx members are
specified in the LOADxx and IEASYMxx parmlib
members.
xx...x
Contains the full product name, version, release,
modification level and FMID. For example, in
OS/390 Release 2, xx...x is 01.02.00 JBB6602.
This field can be changed by the installation using
the SPZAP service to change the value in the
CVTVERID field of the communication vector table
(CVT).
The system uses the system parameters specified in
the IEASYSxx members that are displayed in the
message text.
system parameters are appropriate for the system. If the
list is not correct, see the section on determining where
to specify system parameters in OS/390 MVS
Initialization and Tuning Reference for information about
how to respecify IEASYSxx members.
Detecting Module: IEAVNPC4
IEA009I
SYMBOLIC DEFINITIONS WILL BE

READ FROM:
IEASYMxx
.
.
.
IEASYMzz
Explanation: This message displays the IEASYMxx

parmlib members that define system symbols for this
system. The IEASYMxx members are specified in the
LOADxx parmlib member. The system displays this
message during system initialization if both of the
following occur:
532
v The system programmer specifies the ,L parameter

on the IEASYM statement in the LOADxx parmlib
member.
zz The suffix of the last IEASYMxx parmlib member in

the system parameter concatenation.
The system uses the system symbol definitions in the
IEASYMxx members that appear in the message text.
System Programmer Response: Determine if the list
of IEASYMxx members is correct. If the list is not
correct, change the IEASYM statement in LOADxx to
specify the correct IEASYMxx members. Then reIPL the
system.
Detecting Module: IEAVNPIL
IEA010I
SYMBOLIC DEFINITION ALTERED:

SYMBOL
ORIGINAL VALUE
NEW VALUE
= &symbol.-name
= old-text
= new-text
Explanation: This message displays a value in the

static system symbol table that was changed during
initialization. The system issues this message when the
substitution text for the &SYSPLEX.system symbol is
specified in COUPLExx but not in LOADxx.
&symbol.-name
The name of the static system symbol whose
substitution text was changed during system
initialization.
old-text
The substitution text for the symbol-name static
system symbol before the change.
new-text
The substitution text for the symbol-name static
system symbol after the change.
The system uses the new substitution text for the
system symbols displayed in the message text.
new substitution text displayed in the message text is
appropriate for the associated system symbol. If not,
see OS/390 MVS Initialization and Tuning Reference for
information about how to change system symbol
definitions in parmlib. After you change the definitions
for the system symbol, reIPL the system.
IEA012E
If &symbol.-name shown in the message text is

&SYSPLEX:
v Specify the desired substitution text for &SYSPLEX
on the SYSPLEX parameter in the LOADxx parmlib
member.
v Specify SYSPLEX(&SYSPLEX.) on the SYSPLEX
parameter in the COUPLExx parmlib member, which
ensures that &SYSPLEX. resolves to the substitution
text defined on the SYSPLEX parameter in LOADxx.
CIRCULAR SYMBOLIC DEFINITION

DETECTED
text
Explanation: Where text is:
UNRESOLVED STATIC SYMBOL DEFINITIONS FOLLOW:
IEASYMyy:&symbol-name = symbol-text
.
.
.

Detecting Module: IEAVESYM
IEA011A
RESPECIFY ENTIRE IEASYMXX

SUFFIX LIST OR U TO BYPASS
Explanation: If this message is preceded by message

IEA013E, one of the following occurred:
v The system found an error in a parameter or
parameter value in one or more IEASYMxx parmlib
members that were used during IPL.
v The system could not find an IEASYMxx member
specified in LOADxx parmlib member.
Otherwise, the system found a syntax error in the
IEASYMxx parmlib member.
The system issues this message only for statements in
IEASYMxx that apply to the processor or LPAR on
which this system is being initialized.
System Action: The system issues this message on
the nucleus initialization program (NIP) console and
waits for the operator to respond. The system discards
any processing of IEASYMxx members that occurred
before the error. The system might issue messages that
describe the error prior to issuing this message, as
described in the message explanation.
following:
v If you want to respecify the IEASYMxx members,
enter all the suffixes of the IEASYMxx members in
response to this message. (For example, if you
specified three IEASYMxx suffixes and only one was
not valid, you must respecify the two valid suffixes,
and replace or remove the suffix that was not valid.)
v Reply U to bypass IEASYMxx processing and
continue with system initialization.
IEASYMzz:&symbol-name =
symbol-text
The system found one or more static system symbol

definitions that are circular. That is, one or more system
symbol definitions contain other system symbols that
refer back to each other.
The following is an example of a circular system symbol
definition:
SYMDEF(&LNK.='&APF.(-2:2)')
SYMDEF(&APF.='&LNK.(-2:2)')
In the example above, the definition of &APF. depends
on the resolution of &LNK. . However, because the
definition of &LNK. also depends on the resolution of
&APF. , the two system symbols can never be resolved.
xx The suffix of the first IEASYMxx parmlib member in

which a circular definition appears.
yy The suffix of the last IEASYMxx parmlib member in
which a circular definition appears.
&symbol-name
The name of the installation-defined system symbol
that specifies a circular definition.
symbol-text
The unresolved substitution text.
System Action: The system enters non-restartable
wait state X'07D' with return code X'0000'.
System Programmer Response: Correct the circular
reference in the IEASYMxx parmlib member, then reIPL
the system.
Detecting Module: IEAVNPCF

Detecting Module: IEAVNPIL
IEA013E
ERROR DETECTED PROCESSING

IEASYMxx: text

001 MEMBER NOT FOUND
002 RESERVED SYMBOLIC DEFINED :
system-symbol-name
003 SYMBOL LENGTH ERROR :
system-symbol-name
533
004 SYMBOL NAME ERROR: system-symbol-name

005 MAXIMUM DEFINITIONS EXCEEDED AT
SYMBOL: system-symbol-name
006 DATA LENGTH ERROR FOR SYMBOL:
system-symbol-name
007 UNDEFINED PARAMETER DETECTED:
parameter-name
008 DATA FOR parameter-name IN ERROR:
parameter-value
required ampersand (&) at the beginning and

the period (.) at the end.
System Programmer Response: Change
symbol name specified on the SYMDEF
parameter to a name is 1-8 characters long
(excluding the ampersand and the period).
Then respond to message IEA011A.
004
The system found an error in an IEASYMxx parmlib

member.
System Programmer Response: Change

symbol name specified on the SYMDEF
parameter to a name that begins with an
ampersand followed by an alphanumeric or
national character. Then respond to message
IEA011A.
xx The suffix of the IEASYMxx parmlib member in

which the error occurred.
system-symbol-name
The name of a system symbol, defined in
IEASYMxx, that contained an error.
005
parameter-name
The name of a parameter in IEASYMxx that
contained an error.
Code
Meaning and Action
001
Meaning: The system could not find the

IEASYMxx parmlib member specified in the
LOADxx parmlib member.
006

value on the IEASYM parameter in LOADxx so
it specifies one or more valid IEASYMxx
parmlib members. Then respond to message
IEA011A.
002
003
534
Meaning: A SYMDEF parameter in an

IEASYMxx parmlib member specified a symbol
name that is too long. Symbol names must
consist of 1-8 characters, excluding the
Meaning:
v A SYMDEF parameter in an IEASYMxx
parmlib member specified a substitution text
that is too long. The substitution text is
longer than the length of the associated
system symbol name, which includes the
ampersand (&) character. For example, the
length of the value assigned to the symbol
&FRED. cannot exceed five characters.
v A SYSCLONE parameter in an IEASYMxx
parmlib member specified a substitution text
that was not 1 or 2 characters long.
system symbol definition in IEASYMxx to
specify a substitution text that does not exceed
the length of the system symbol name or
correct the SYSCLONE parameter specification
in IEASYMxx. Then respond to message
IEA011A or re-IPL.
Meaning: A SYMDEF parameter in the

IEASYMxx parmlib member specified a symbol
that is reserved for system use (for example,
&SYSNAME., which specifies the system
name).
System Programmer Response: See the
section on defining system symbols in OS/390
MVS Initialization and Tuning Reference for a
list of symbols that are reserved for system
use. Change the symbol name specified on the
SYMDEF parameter to a name that is not
reserved for system use. Then respond to
message IEA011A.
Meaning: The number of installation-defined

system symbols exceeds the maximum of 100
for this system.
System Programmer Response: Reduce the
number of installation-defined system symbols
in the IEASYMxx parmlib member so there are
no more than 100 for the system. Then
respond to message IEA011A.
parameter-value
The value of a parameter in IEASYMxx that
contained an error.
The reason code in the message text identifies the
error:
Meaning: A SYMDEF parameter in a

IEASYMxx parmlib member did not begin with
an ampersand (&) followed by an alphanumeric
or national character.
007
Meaning: A parameter is specified in a

IEASYMxx parmlib member. The undefined
parameter is displayed in the message text.
name of the parameter in IEASYMxx. Then
008
Meaning: An undefined parameter in a

IEASYMxx parmlib member specified a value.
The parameter and its value are displayed in
the message text.

parameter and the value in IEASYMxx. Then
System Action: The system will do one of the
following:
v Issue message IEA011A, which asks the operator to
respecify the suffix for IEASYMxx. The system issues
message IEA011A only for statements in IEASYMxx
that apply to the processor or LPAR on which this
system is being initialized.
v Continue with the IPL. This action is taken when the
error occurs in a statement that does not apply to this
system.
v Enter a non-restartable wait state X07D with reason
code X0004. The system enters the wait state when
the error occurs in a statement that applies to this
system and it was discovered at a point too late to
accept a new IEASYMxx.
programmer response in the list of reason codes in the
message explanation.
Detecting Module: IEAVNPIL, IEAVNPCF
IEA014W
NONRECOVERABLE ERROR IN
IEASYMxx PROCESSING
Explanation: The system found an error in an

IEASYMxx parmlib member from which it cannot
recover.
xx The suffix of the IEASYMxx parmlib member in

which the error occurred.
System Action: The system might also issue
message IEA012E or IEA013E. The system enters
non-restartable wait state X'07D' with reason code
X'0004'.
System Programmer Response: If the system issues
message IEA012E or IEA013E, see the system
programmer responses for those messages. Otherwise,
see the system programmer response for wait state
X'07D' with reason code X'0004'.
IEA015A
text
Explanation: In the message, text is:
IF THIS EVENT OCCURRED ON SOME, BUT NOT

ALL SYSPLEX MEMBERS, THE LIKELY CAUSE IS
A LINK FAILURE. TO FIX, ENSURE THAT EACH
AFFECTED SYSTEM HAS AT LEAST ONE CORRECTLY
CONNECTED AND FUNCTIONAL LINK.
IF THIS EVENT OCCURRED ON ALL SYSPLEX MEMBERS,
THEN THE LIKELY CAUSE IS A SYSPLEX TIMER FAILURE.
TO FIX, REFER TO THE MESSAGE
IEA015A DESCRIPTION IN MVS SYSTEM MESSAGES.
AFTER FIXING THE PROBLEM, REPLY RETRY FROM THE
SERVICE CONSOLE (HMC). IF THE PROBLEM WAS NOT
CORRECTED, THIS MESSAGE WILL BE REISSUED AND YOU
MAY TRY AGAIN. REPLY ABORT TO EXIT MESSAGE
LOOP. PROBABLE RESULT: 0A2-114 WAITSTATE
The system has lost all connections to its sysplex
timer(s).
System Action: The system waits for a reply to
message IEA015A.
loss of Sysplex Timer connectivity occurred, repair the
problem, and then reply to the message on each
system where it occurs.
There are two basic scenarios for which this message
may be issued. You should first determine if a subset of
the ETR synchronized MVS images have issued
IEA015A or whether ALL have issued it. If only a few
MVS images issued IEA015A, then it is likely that ETR
links have failed to those machines. Repair the failed
links and then reply with RETRY on each issuing
system. If the problem was corrected, processing will
resume. If the problem was not resolved, the message
will be reissued until the problem is fixed or until you
reply ABORT. A reply of of ABORT will result in a
0A2-114 waitstate if the MVS image is a member of a
multisystem Sysplex. If it is not, processing will resume
in local TOD clock mode.
If ALL ETR synchronized MVS images issue IEA015A,
then there has been a failure of one or both Sysplex
Timers. If one Sysplex Timer fails, the other may go into
dormant state when it can not communicate with the
failed 9037. In this case, it may be possible to recover
the dormant 9037 and then reply RETRY as
previously described. See the redbook SG24-2070-00,
S/390 Time Management and IBM 9037 Sysplex Timer
for more information on how to recognize this condition
and how to recover from it. See sections 10.12 and
10.13 in Chapter 10 for detailed information.
Source: Timer Supervision
Detecting Module: IEATSWLH
THIS SYSTEM HAS LOST ALL

CONNECTION TO THE SYSPLEX TIMER.
535
IEA016W
REQUIRED LEVEL OF DFSMS IS NOT

INSTALLED
Explanation: The current release of OS/390 requires

a particular release of DFSMS in order to IPL. OS/390
R10 requires DFSMS R10.
System Action: The system issues wait state code
X'009' reason 0.
System Programmer Response: Install the proper
release of DFSMS, and then re-IPL.
IEA020W
AN FRR STACK POINTER FOR CPU x

IS DAMAGED, THE ERROR MASK IS
abcdefghijklmnopqrst.
Explanation: MVS found found uncorrectable damage

to at least one functional recovery routine (FRR) stack
pointer.
The CPU which had the damaged stack pointer or
pointers is identified by the value for x.
The error mask tells you which FRR stack pointers were
incorrect.
v If a is 1, PSACSTK is incorrect.
v If b is 1, PSANSTK is incorrect.
v If c is 1, PSASSTK is incorrect.
v If d is 1, PSAMSTK is incorrect.
v If e is 1, PSAPSTK is incorrect.
v If f is 1, PSAESTK1 is incorrect.
v If g is 1, PSAESTK2 is incorrect.

programmer response for wait state X'084' in OS/390
MVS System Codes.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTRTV
IEA024I
ERROR IN GTF. opt TRACE OPTION

WAS DISABLED
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
record was produced when GTF encountered a program
check while attempting to create a trace record.
This message is followed by a hexadecimal dump of the
error record. Refer to messages AHL118I and AHL1201.
opt
The trace option, which is one of the following:

DSP
EXT
IO
PI
SIO
SVC
System Action: The program check for the error

record caused GTF to bypass recording further events
for the trace option. However, GTF continued to record
all events for the other trace options requested.
After issuing this message, the system writes a
hexadecimal dump of the error record. Refer to
messages AHL118I and AHL1201.
v If h is 1, PSAESTK3 is incorrect.
Note: If opt is SVC, SVC tracing will continue.
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.
v If l is 1, PSASSAV is incorrect.
v If m is 1, PSAMSAV is incorrect.
v If n is 1, PSAPSAV is incorrect.
v If o is 1, PSAESAV1 is incorrect.
Ensure that sufficient storage is available within the

GTF region for a SNAP dump (an additional 4 kilobytes
is needed for ABDUMP/SNAP processing). Ensure that
the GTFSNP cataloged procedure is used to obtain an
ABDUMP/SNAP dump.
v If q is 1, PSAESAV3 is incorrect.

Center.
v If r is 1, PSARSAV is incorrect.
Source: Generalized trace facility (GTF)
v If p is 1, PSAESAV2 is incorrect.
v If s is 1, PSATSAV is incorrect.
v If t is 1, PSAASAV is incorrect.
IEA025I
System Action: The system:
Explanation: During formatting of the trace table of

the generalized trace facility (GTF), the dump formatter
found a GTF record with an incorrect EID or FID field.
ABDUMP prints this message and follows it with a
hexadecimal dump of the error record.
1. Issues this message.

2. Places all processors on this system in
non-restartable X'084' wait state, with reason code
X'04'.
wait state X'084' in OS/390 MVS System Codes.
536
INVALID GTF RECORD FOLLOWS

System Programmer Response: Ensure that problem
programs are not altering the trace table.

Detecting Module: IGC0F05A
IEA030I
OPEN FAILED FOR DUMP DATA SET

FOR {JS|ST} DUE TO {Scde|Ucde}
Explanation: While abending a task, the system tried

to open a SYSABEND, SYSMDUMP, or SYSUDUMP
dump data set, but failed.
specified on the command. The system continues

processing.
System Programmer Response: Avoid setting
multiple traps that are likely to contend for the resource
needed for remote action processing.
Source: SLIP
Detecting Module: IEAVTSL2
IEA040W

JS A dump data set for the job step task could not be
opened.
ST A dump data set for a subtask could not be
opened.
Scde
The system was in the process of abnormally
ending a task with system completion code cde.
Ucde
The system was in the process of abnormally
ending a task with user completion code cde.
System Action: The system does not write a dump,
but abends the task. The system sends messages
about the problem to the job log.
System Programmer Response: Do the following:
1. Continue diagnosis with the original completion
code.
2. Use the messages in the job log to determine why
the system could not open the dump data set.
3. If the problem appears to be in the system, search
problem reporting data bases for a fix for the
problem. If no fix exists, report the problem to the
IBM Support Center. Provide the messages from the
job log and all problem data for the original abend.
REMOTE SLIP TRAP ID=xxxx FROM

SYSTEM ssssssss MATCHED.
ACTION=WAIT RESTART THE SYSTEM
TO CONTINUE
Explanation: A remote system found a match for a

SLIP trap. The SLIP trap requested that this system be
placed into a wait state so that the operator could
capture diagnostic data.
ID=xxxx
The SLIP trap identifier specified on the SLIP
command.
ssssssss
The system on which the trap matched.
System Action: This system is placed into a
restartable wait state.
Operator Response: Perform the actions requested
by the system programmer for this trap.
Either:
v Restart the system.
v Obtain a stand-alone dump and reIPL the system.
System Programmer Response: To capture

diagnostic data, ask the operator to obtain a
stand-alone dump. The system cannot be restarted if a
stand-alone dump is written; ask the operator to reIPL
the system.
Detecting Module: IEAVTABD
Source: SLIP
IEA039I
SLIP TRAP ID=xxxx REMOTE ACTION

WAS NOT PERFORMED.
IEA041I
SDUMP SCHEDULED FOR REMOTE

SLIP TRAP ID=xxxx FROM SYSTEM
ssssssss
Explanation: A SLIP trap requested ACTION=SVCD

or ACTION=SYNCSVCD and also requested one or
more remote actions. The system cannot activate the
action on the remote system because another SLIP trap
with ACTION=WAIT or a remote action is active in the
system.
Explanation: A remote system found a match for a

SLIP trap. The SLIP trap requested that this system
write an SVC dump. This system scheduled the SVC
dump.
ID=xxxx
command.
ID=xxxx
command.
System Action: The system performs the local SVCD

or SYNCSVCD action, but not the remote action
ssssssss
The system on which the SLIP trap matched.
537
System Action: This system schedules an SVC dump

and continues processing.
specified on the MAXSPACE parameter of the

CHNGDUMP operator command at the time
the limit was reached.
Source: SLIP
IEA042I
SDUMP NOT SCHEDULED FOR

REMOTE SLIP TRAP ID=xxxx FROM
SYSTEM ssssssss. REASON - text

ANOTHER DUMP WAS IN PROGRESS
DUMP=NO WAS SET AT IPL OR INDICATED BY
CHNGDUMP
NO SYS1.DUMP DATA SET WAS AVAILABLE
NO SRBS COULD BE SCHEDULED TO START
THE DUMP
SVC DUMP ABNORMALLY TERMINATED
A STATUS STOP SRBS CONDITION WAS
DETECTED
A remote system found a match for a SLIP trap. The
SLIP trap requested that this system write an SVC
dump. However, this system could not write the dump
for the reason indicated in the message.
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
allow other dumps to be captured until the amount of
available space is greater than the threshold value. The
threshold value is the lower of two values: 35
megabytes or ten percent of the MAXSPACE value. To
view the amount of available space, use the DISPLAY
DUMP command.
Operator Response: Do one of the following:
v If any dump is captured, but there are no available
dump data sets, use the DUMPDS command or
another utility to make dump data sets available.
v If any dump is captured but not required by the
installation, reply D to message IEA793A to delete
the dumps.
v Use the MAXSPACE parameter on the CHNGDUMP
command to increase the value of MAXSPACE,
allowing SVC dump processing to use more virtual
storage to hold captured dumps.
Source: SVC dump

ID=xxxx
command.
IEA050I
ssssssss
The system on which the SLIP trap matched.
Explanation: Duplexing of PLPA and Common is no

longer supported.
text

However, the DUPLEX keyword is ignored, and no
duplexing occurs.
The reason why the system could not write the

SVC dump.
DUPLEX IS AN OBSOLETE KEYWORD.

DUPLEXING NO LONGER
SUPPORTED.
System Action: The system processes the SLIP

command, but the system does not write the requested
SVC dump.

remote system could not write an SVC dump. If the
problem cannot be corrected, search problem reporting
notify the IBM Support Center.
Detecting Module: ILRASRIM
Source: Auxiliary Storage Manager
IEA051I
THE PAGTOTL SWAP PARAMETER IS

OBSOLETE AND IS IGNORED.
Explanation: Swap data sets are no longer supported.

The swap parameter specified for the PAGTOTL
keyword is ignored.
IEA043I

However, the swap parameter is ignored.
Source: SLIP
SVC DUMP REACHED MAXSPACE

LIMIT - MAXSPACE=xxxxxxxx MEG
Explanation: The limit that an installation placed on

the amount of storage available for SVC dump to hold
captured dumps is reached.
xxxxxxxx
The amount of storage, in megabytes,
538

IEA052I
THE SWAP KEYWORD IS OBSOLETE

AND IS IGNORED.
Explanation: Swap data sets are no longer supported.

The SWAP keyword specified in the IEASYSxx parmlib
member or on the IPL parameters is ignored.
IEA084W
ENTRY POINT entrypt NOT FOUND IN

THE NUCLEUS
Explanation: During system initialization, the system

could not find an entry point in the nucleus for one of
the following:
v A device descriptor table (DDT)
v An error recovery program (ERP)
v The unit control blocks (UCB)
v The device class queue (DCQ)
v The device characteristic table (DCT)
The system loaded one of the following:
v An incomplete nucleus

However, the SWAP keyword is ignored, and the
system will continue without dedicated swap data sets.
v An incomplete I/O configuration

IEA080D
IOS KEYWORD PARAMETER INVALID.

REPLY IOS=XX OR IOS=DEFAULT
Explanation: In response to message IEA101A or

IEA080I, the operator entered an incorrect IECIOSxx
parmlib member on the IOS=xx parameter.
respond. The system issues this message on the
nucleus initialization program (NIP) console.
Operator Response: Reply with one of the following
responses:
REPLY 0,IOS=xx, where xx is a valid member
REPLY 0,IOS=DEFAULT
REPLY 0,IOS=DEF
In the case of the last two responses, the system uses
the IBM defaults for MIH and HOTIO.
Source: Input/output supervisor (IOS)
IEA081I
ERROR - IECIOSxx RECORD nnnn I/O

ERROR

could not read a record from the IECIOSxx parmlib
member.
v Both an incomplete nucleus and an incomplete I/O

configuration
entrypt The entry point address.

System Action: The system enters nonrestartable
disabled wait state X'035'.
wait state X'035'.
programmer response for wait state X'035'.
Detecting Module: IEAIPL03
IEA086I
memname NOT FOUND IN

SYS1.NUCLEUS
Explanation: The initial program load (IPL) program

was unable to locate in SYS1.NUCLEUS a member
specified on an INCLUDE statement of NUCLSTxx. The
NUCLST statement of LOADxx did not specify that a
wait state is to be loaded if any of the INCLUDE
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:
IECIOSxx
The parmlib member, with the suffix xx.
memname
The missing member.
nnnn
System Action: The IPL proceeds.
The record name.
System Action: System initialization continues. The

system processes all previous records to establish the
missing interrupt handler (MIH) and HOTIO
environment. The system rejects the unreadable record
and all records that follow it.
System Programmer Response: Either provide the

missing member or update NUCLSTxx.
539
IEA086W
memname NOT FOUND IN

SYS1.NUCLEUS

was unable to locate a necessary member in the
SYS1.NUCLEUS data set.
memname
The missing member, as follows:
IEANUC0x
x may not be the correct identifier for the
nucleus you need.
If memname is another name, the member is either a
module list table (MLT), a nucleus module list (NML), a
nucleus device support module, or a member that was
specified on an INCLUDE statement in the NUCLSTxx
member.
disabled wait state X'055'.
Because a console is not available for messages at IPL
time, the system stores this message in the IPL WTO
buffer.

IEA088W
Explanation: Initial program load (IPL) cannot

continue because the system does not have enough
virtual storage. The DAT-on nucleus requires more
storage than is available below 16 megabytes. (DAT is
the acronym for dynamic address translation.)
wait state X'071'.
This message appears in the IPL WTO buffer.
Source: Initial program load (IPL)
IEA089W

wait state X'055'
IEA087W
ENTRY POINT entrypt APPEARS IN

mod1 AND mod2
Explanation: The system detected a duplicate entry

point name appearing in more than one module. The
entry points appear in modules being loaded into the
DAT-on nucleus. (DAT is the acronym for dynamic
address translation.)
entrypt The duplicate entry point name

mod1
mod2
The first module where the duplicate entry

point name appears.
The second module where the duplicate entry
point name appears.
This message accompanies wait state code X'025'.

wait state X'025'. Because a console is not available for
messages at IPL time, the system stores this message
in the IPL WTO buffer.
wait state code X'025'.
540
NUCLEUS REQUIRES MORE STORAGE

BELOW 16MB THAN IS AVAILABLE
memname HAS MORE THAN 1 CSECT

BUT WAS NOT LINK EDITED WITH
SCTR OPTION
Explanation: The system detected an error with a

member of the SYS1.NUCLEUS being loaded into the
dynamic address translation (DAT)-on nucleus region
during system initialization. The member contained
more than one control section (CSECT) and was not
link-edited with the scatter (SCTR) option.
memname
The member of SYS1.NUCLEUS in error.
disabled wait state X'054' with reason code X'01'.
Because a console is not available for messages at IPL
time, the system stores this message in the IPL WTO
buffer.
wait state X'054'.
IEA090W
LOAD REAL ADDRESS FAILED

DURING irimname PROCESSING
Explanation: An initial program load (IPL) resource

initialization module (IRIM) issued a Load Real Address
(LRA) instruction that failed to return a valid real
address.
contains the unresolved external reference.
irimname
The IRIM that issued the failed instruction.
If IBM supplied the module, search problem reporting

contact the IBM Support Center.

wait state X'074' with reason code X'06'. Because a
console is not available for messages at IPL time, the
system stores this message in the IPL WTO buffer.
wait state X'074'.
System Programmer Response: See the operator
response for wait state X'074'.
IEA091I
NUCLEUS x SELECTED
Explanation: The system selected module IEANUC0X

as the base nucleus module to load into the DAT-on
nucleus region. (DAT is the acronym for dynamic
address translation.) The system issues this message
so that the operator can verify the nucleus selected.
The identifier for the nucleus module,

IEANUC0x
System Action: The initial program load (IPL)

program loads IEANUC0x into the DAT-on nucleus
region.
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.

MODULE modname CONTAINS
UNRESOLVED WEAK EXTERNAL
REFERENCE refname
IEA093I

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.
modname
The nucleus module
refname
The unresolved external reference
System Action: The IPL proceeds. The unresolved
external references should not affect the success of the
IPL or subsequent processing.
System Programmer Response: This might be a
normal situation. Consult the program directory and the
PSP bucket to ensure that the reason for this message
is expected. If the message is expected, ignore it.

IEA092I
WARNING: UNRESOLVED EXTERNAL

REFERENCE symbol IN MODULE
modname

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.
IEA099A
JOBNAME= jobname ASID= asid HAS

REACHED THE WTO BUFFER LIMIT
Explanation: The number of write to operator (WTO)

buffers for an address space has reached the limit
specified in the MLIM field of the CONSOLxx parmlib
member.
following:
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
System Action: The IPL proceeds, but the success of
the IPL or subsequent processing is unpredictable.
System Programmer Response: If the module is
IEANUC0x, link edit it again to determine which CSECT
v Automate the message to slow down or cancel the

offending address space.
ATTENTION: Data may be lost if you do not use
caution when cancelling the address space.
v Modify the WTO macro so it uses the
MCSFLAG=BUSYEXIT parameter. The system stops
541
WTO processing and returns control to the program

issuing the macro when the WTO buffer limit is
reached.
Source: Communications task (COMMTASK)
Detecting Module: IEAVH600
IEA100I
ETR SERVICE INFORMATION IS

PROVIDED. REASON
CODE=reason-code
Explanation: The External Time Reference (ETR)

provided service information. ETR is the MVS generic
name for the IBM Sysplex Timer (9037) or equivalent.
REASON CODE=reason-code
A reason code explaining the information follows. For
more information about the reason codes, see
Maintenance Information for the 9037 Sysplex Timer.
These codes are informational and require no action.
System Action: The system prompts the operator for

a reply, then changes the system parameters as
specified by the operator.
Operator Response: Reply as specified by the
system programmer, for example:
REPLY 00,CLPA,SYSP=83,LNK=(04,05,PQ),SYSNAME=AQ
If the reply is longer than one line (there are 80
characters per line), you can follow the last parameter
with a comma or a blank and CONT. For details about
specifying system parameters, including how to continue
system parameters, see the description of the REPLY
command in OS/390 MVS System Commands.
System Programmer Response: Tell the operator
which responses to enter.
IEA102W
OPERATOR PROMPT NOT ALLOWED

FOR A SYSPLEX TEST DATESOURCE
LPAR
005
Unit recovered.
006
Control Link A operational.
007
Control Link B operational.
008
Communication established with console.
Explanation: In the CLOCKxx parmlib member,

OPERATOR PROMPT is specified. This is not a valid
specification when IPLing a sysplex datesource LPAR.
009
Communication established with standby

console.
System Action: The system enters a non-restartable

wait state.
038
Maintenance mode set.
039
Maintenance mode cleared.
042
The 9037 is now tracking the external time

source. This service request is provided to
indicate a prior problem has been resolved.
System Programmer Response: Modify the

CLOCKxx parmlib member for the sysplex datesource
LPAR to specify OPERATOR NOPROMPT.

Source: Timer supervision
Detecting Module: IEATEEIH
IEATESMR
IEA101A
SPECIFY SYSTEM PARAMETERS FOR

xx...x
Explanation: This message is issued during system

initialization to allow the operator to change certain
system parameters.
xx...x
Contains the full product name, version,

release, modification level and FMID. For
example, in OS/390 Release 2, xx...x is
01.02.00 JBB6602.
This field can be changed by the installation
using the SPZAP service to change the value
in the CVTVERID field of the communication
vector table (CVT).
542

Detecting Module: IEAVNP21
IEA107I
prm IGNORED
Explanation: In reply to message IEA101A, the

operator specified a value for a parameter, prm.
However, in the current IEASYSxx parmlib member,
OPI=NO is specified for that parameter. The system
therefore rejects the value specified by the operator.
System Action: The nucleus initialization program
(NIP) continues processing.
Operator Response: If requested by the system
programmer, obtain a stand-alone dump
parameter was not restricted from operator changes in
the IEASYSxx parmlib member (OPI=NO option).
If IEASYSxx is correct and if the problem persists,
Center. Provide a stand-alone dump.

IEA116A
CONTINUE SYSTEM PARAMETERS
Explanation: During nucleus initialization, the reply to

message IEA101A specified CONT as its final entry.
CONT indicates that the reply was incomplete and that
additional parameters are to be specified.
a reply.
Operator Response: Continue the reply to message
IEA101A. Begin the continuation with REPLY 00.
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
CONT. If the device is required for NIP processing, tell
the operator to reIPL the system using the appropriate
backup device.
Source: Input/Output Supervisor (IOS)
IEA121I

IEA120A
DEVICE dev VOLID NOT READ, REPLY

CONT OR WAIT
Explanation: A direct access storage device (DASD)

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
other than the initializing processor.

returned a busy condition.
IEA122I
v A hardware malfunction could be causing the device

to appear busy.
dev
The device number.
reply.
Take one of the following actions:
v Enter REPLY id, WAIT to cause the system to wait
for the device to become available. If the device is
still not available after 15 seconds, the system issues
message IOS124A to prompt the operator again.
v Enter REPLY id,CONT to purge outstanding I/O
requests and mark the device offline. Replying CONT
means that the device is no longer available; NIP
processing continues without it.
Because the device is no longer available, replying
CONT can cause later errors if the device, such as
the SYSRES device is required for NIP processing.
Thus, reply CONT only when the device is not
available because of a hardware problem that can
not be corrected and the device is not required for
NIP processing.
While it is also possible to take no action, (which the
system considers an implicit WAIT), do so only at the
direction of the system programmer. Taking no action is
an appropriate response only for a device that times out
and is not required for NIP processing.
UNABLE TO OBTAIN
CHANNEL-SUBSYSTEM INFORMATION
DUE TO A BUSY CONDITION. IPL
CONTINUES.
ERROR OBTAINING CHANNEL

SUBSYSTEM INFORMATION DUE TO
HARDWARE FAILURE. IPL
CONTINUES.

tried to issue the channel-subsystem information
command. A hardware failure occurred.
IEA123I
CONSOLE DELAYED SVC

PROCESSING RESUMED. RESTART
SUCCESSFUL
Explanation: The system previously issued message

IEA544I or IEA555E. The system restart was successful
after the problems indicated by message IEA544I or
IEA555E were resolved.
Detecting Module: IEAVM613
IEA124I
SYSTEM CONSOLE consname

QUEUING RESUMED
Explanation: After the system suspended message

queuing to a console, the system resumed message
queuing to that console.
consname
The system console name.
543

SYSTEM CONSOLE consname
QUEUING SUSPENDED, ERROR CODE
= code
IEA125I
Explanation: The system suspended message

queuing to the specified system console.
v Enter the CONTROL M,RLIM command to increase

the value of the buffer limit.
v Use the VARY CN command to remove routing codes
from the system console, or take other actions to
reduce the number of messages being sent to the
console.
v Issue VARY CN(*) , DEACTIVATE from the system
console.
consname
The system console name.
IEA127I
code
Explanation: The system could not initialize the

system console input listener exit routine.
The error code, which is one of the following:

Code
Explanation
8001
The service processor logical console

is not available for output processing.
SYSTEM CONSOLE NOT ACCEPTING

[PRIORITY] OPERATOR INPUT
8002
The message queue limit for the

system console was reached.
PRIORITY
The system is not accepting operator input
from the screen that accepts priority
commands.
8003
The system found an internal queue

error.
System Action: The system console does not process

any other commands.
System Action: Depending on the error code, one of

the following:
Code

System Action
8001
The system does not display messages that

were queued to the system console. The
system does not queue new messages to the
system console.
8002, 8003
The system displays messages that were
queued to the system console. The system
does not queue new messages to the system
console.

Detecting Module: IEAVN701
IEA128I
SYSTEM CONSOLE ONLY

SUPPORTING SYNCH OUTPUT
Explanation: The system could not define the system

console as an extended MCS console.
System Action: The system does not display
non-SYNCH messages on the system console.
IEA126I
THE SYSTEM CONSOLE QUEUE IS

80% FULL
Explanation: The buffer that holds the messages on

the system console queue is 80% full.

IEA129I
MASTER CONSOLE REQUIRED.
v Reply to outstanding messages.
Explanation: The operator must use a console with

master authority because the hardware that supports
the enhanced system console function is not installed,
or the system console is not available. Also, one of the
following conditions exists:
v Cancel any jobs that are currently issuing messages.
v CON is not specified on the system parameter.

Operator Response: If desired, do one or more of the
following:
544
v CON=NONE is specified on the system parameter, or

in the IEASYSxx parmlib member.
System Action: The system prompts the operator to
specify a console with master authority on the CON
parameter.
Operator Response: Enter the parmlib member name
that specifies a valid console with master authority on
the CON parameter. ReIPL the system.
Detecting Module: IEAVNPA1
IEA133E
THE TRACE ADDRESS SPACE HAS

TERMINATED
IEA139E
PC/AUTH SERVICES ARE

INOPERABLE
Explanation: The system gave Program

Call/authorization (PC/AUTH) recovery control.
PC/AUTH recovery was unable to successfully validate
the PC/AUTH control blocks. This can be caused by an
abend code X'053'.
System Action: The system issues an SVC dump. In
most cases, tasks running when the error occurred
continue normally, and the Program Call (PC) instruction
and other cross-memory instructions can still be used.
After the error, programs that attempt to use PC/AUTH
services are abended with system completion code
X'053' reason code X'nn98'.
Explanation: The system trace address space has

abnormally ended.
System Action: The system continues processing. No

system tracing is active. The system writes a logrec
data set error record and may write an SVC dump.
v If abend X'053' with a reason code other than X'nn98'

accompanies this message, see the system
programmer response for abend code X'053'.
Operator Response: Enter a TRACE ST command to

restart system tracing.
System Programmer Response: If the error recurs,
Center. Provide the logrec data set error record and the
SVC dump, if available.
Source: System trace
v Obtain the SVC dump for this message.
v If the message is not accompanied by abend X'053',

Center. Provide the dump.
Source: Program Call/authorization (PC/AUTH)
Detecting Module: IEAVXPCR
IEA140W
Detecting Module: IEAVETRM

IEA134I
TRACE ERROR, REISSUE TRACE

COMMAND IF STATUS NOT AS
REQUESTED
Explanation: While processing a TRACE ST

command, the system detected an error.
The system attempts to record the error in logrec data
set, write an SVC dump, and repair any problems in the
system trace structure.
Operator Response: If the status is not as requested,
enter the TRACE command again. To determine the
status, enter the TRACE STATUS command.
System Programmer Response: If the error recurs,
Center. Provide the logrec data set error record and the
SVC dump, if available.
Source: System trace
Detecting Module: IEECB925
TOTAL SIZE OF NUCLEUS,

{SQA|ESQA}, {LPA|ELPA} TOO LARGE,
NO SPACE FOR {CSA|ECSA}
Explanation: The system could not initialize the

common service area (CSA). No space is left for the
CSA because the following storage areas, in
combination, overlapped the private area:
v The nucleus
v The system queue area (SQA)
v The link pack areas (LPA)
System Action: The system enters restartable wait
state X'0E3'.
programmer response for wait state X'0E3'.
Source: Virtual storage manager (VSM)
IEA145E
MESSAGES/COMMANDS MAY HAVE

BEEN LOST, COMMANDS MAY NEED
TO BE REISSUED
Explanation: In a sysplex, commands, messages, or

both may have been lost.
System Action: The system writes an SVC dump and
545
Operator Response: If console sysplex integrity is

critical, reIPL the system that issued the message to
rejoin the sysplex. Otherwise, none.
resulted from a misspelling on the NONVIO system

parameter. If it was, correct it. Otherwise, add the data
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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Detecting Module: IEAVR601

IEA163E
IEA152I
HARDCPY SPECIFICATION INVALID
Explanation: The operator responded to message

IEA101A or IEA332A by specifying a device for a
hard-copy log. The device cannot be used for hard
copy.
System Action: The system issues message
IEA332A.
the accompanying message.
IEA153I
HARDCPY CONSOLE UNAVAILABLE
ALL PAGING RESOURCES ARE

RESTRICTED VIA NONVIO
SPECIFICATION
Explanation: All of the local paging data sets specified

on the PAGE system parameter are also specified on
the NONVIO system parameter. Therefore, the system
has no local paging data sets available for VIO. The
auxiliary storage manager (ASM) must direct VIO pages
to NONVIO data sets.
System Programmer Response: If the system needs
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
data set.
Explanation: In response to message IEA101A, the

operator specified a valid console for the HARDCOPY
field in the CONSOLxx parmlib member, but the console
is unavailable.
System Action: The system issues message IEA332A

after issuing this message.
IEA166I


VATLSTxx: NO VOLUME MATCH
FOUND FOR VOLUME volser ON
DEVICE TYPE devicetype
Explanation: During processing of the VATLSTxx

parmlib member, the system could not find a volume
that matches a generic volume serial number entry.

IEA162I
dsname CANNOT BE RECOGNIZED

FOR NONVIO RESTRICTION
Explanation: The auxiliary storage manager (ASM)

did not recognize a data set. The data set name
appeared in the list of page data sets specified on the
NONVIO system parameter, but not on the list of paging
data sets specified on the PAGE system parameter.
dsname
The name of the data set.
System Action: The system ignores the data set
name and continues processing the NONVIO system
parameter. Other system initialization continues.
System Programmer Response: Before the next
system initialization, check to see if the problem
546
Note: The system may issue this message when you

code a generic volume serial and every possible
explicit volume serial covered by this generic
volume serial in the VATLST. In this case, ignore
the message.
VATLSTxx
The parmlib member, with a suffix of

xx.
volser
devicetype
The type of device.

the next VATLST statement.
Operator Response: Verify that you have mounted
the correct volumes, and ask the programmer to check
the device type in the volume attribute statement.
Source: Allocation/unallocation
Detecting Module: IEAVAP02

IEA167I
VATLSTxx: VATDEF charstring

IGNORED. text

UNRECOGNIZED KEYWORD
VALUE NOT VALID FOR IPLUSE
VALUE NOT VALID FOR SYSUSE
The system issues this message during processing of
the VATLSTxx parmlib member. A character string on
the VATDEF statement is not a valid VATDEF keyword
or operand. In the message text:
VATLSTxx
The parmlib member, with a suffix of xx.
charstring
The character string on the VATDEF statement.
System Action: VATLST processing ignores the
incorrect character string in the VATDEF statement.
character string on the VATDEF statement.
IEA168I
VATLSTxx: {VATLST|SYSTEM}
DEFAULT USE ATTRIBUTE OF
{PUBLIC|PRIVATE|STORAGE}
{USED.|ASSUMED.}
IEA169I
VATLSTxx: DUPLICATE
{SYSUSE|IPLUSE} SPECIFICATION
IGNORED.

parmlib member, the system found more than one
SYSUSE or IPLUSE keyword. In the message text:
VATLSTxx
System Action: VATLST processing ignores any
additional SYSUSE or IPLUSE keywords specified on a
VATDEF statement.
duplicate SYSUSE or IPLUSE keyword from the
VATDEF statement.
IEA170I
VATLSTxx: DUPLICATE VATDEF

SPECIFICATION IGNORED

parmlib member, the system found a duplicate VATDEF
statement. When processing one or more parmlib
members during an IPL, the system uses the SYSUSE
and IPLUSE keyword values specified in the first
VATLSTxx member. It ignores the VATDEF statements
specified in subsequent members. In the message text:
VATLSTxx
Explanation: The system issues this message during

processing of the VATLSTxx parmlib member to indicate
the value of the IPLUSE or SYSUSE keyword: PUBLIC,
PRIVATE, or STORAGE. In the message text:
System Action: The system uses the values for

SYSUSE and IPLUSE specified on the VATDEF
statement in the first parmlib member. Processing
continues with the next record in VATLSTxx.
VATLSTxx
System Programmer Response: During IPL, the

system uses the keyword values specified on the first
parmlib member. Remove the duplicate keyword from
subsequent parmlib members before the next IPL.
USED
The installation explicitly defined the value on a

VATDEF statement.
ASSUMED
The installation did not explicitly define the
value.
System Action: VATLST processing continues with

the next member.
IEA171I
System Programmer Response: Check the value

indicated for the IPLUSE keyword. If the messages
indicate an assumed value and you want an explicit
value, specify that value on the VATDEF statement.

VATLSTxx: MISSING RIGHT
PARENTHESIS ON VATDEF
STATEMENT.

processing for the VATDEF statement in the VATLSTxx
parmlib member. The VATDEF statement contains a
keyword that is missing a right (ending) parenthesis.
The system assumes a right parenthesis following the
last operand. In the message text:
VATLSTxx
System Action: VATLST processes the VATDEF
547
statement and continues on to the next record.

System Programmer Response: Before the next IPL,
add a right parenthesis to the VATDEF statement.

ReIPL the system.
Source: Reconfiguration
IEA180I
USING IBM DEFAULT PFK

DEFINITIONS. NO PFK TABLES
REQUESTED.
IEA183W
Explanation: The CONSOLxx parmlib member did not

contain a PFKTABxx member.
System Action: The system uses IBM-supplied
defaults for the program function keys (PFKs) for all
consoles.
Operator Response: To specify PFK definitions, enter
a SET PFK=xx command. Then enter a CONTROL
N,PFK=xx command for each console.
RECONFIGURATION INITIALIZATION
FAILED TO OBTAIN SIDE
INFORMATION FROM THE SERVICE
PROCESSOR.
Explanation: During reconfiguration initialization, the

system requested side information from the service
processor. The service processor did not return side
information. This is probably a hardware error.
wait state X'020' The system writes a logrec data set
error record about the failure.
Detecting Module: IEAVC701

ReIPL the system.
IEA181I

USING IBM DEFAULT PFK

DEFINITIONS. ERROR DURING PFK
PROCESSING
Explanation: The system could not change the

definition of the program function keys (PFKs).
System Action: The system ignores the specified
PFKTABxx field and uses IBM-supplied defaults for the
PFKs for all consoles.
Operator Response: To specify PFK definitions, enter
a SET PFK=xx command. Then enter a CONTROL
N,PFK=xx command for each console. If the problem
persists, notify the system programmer.
IEA182W
FAILED TO OBTAIN CHANNEL PATH
INFORMATION FROM THE SERVICE
PROCESSOR.

system requested channel path information, but the
service processor did not return channel path
information. This is probably a hardware error.
wait state X'020' The system writes a logrec data set
IEA184W
FAILED TO OBTAIN THE LENGTH OF
THE SIDE INFORMATION BLOCK

system tried to obtain the length of the resource group
information block but failed.
wait state X'020'. The system writes a logrec data set
ReIPL the system.
Detecting Module: IEEVORGI
IEA186I
FORMAT OF THE CSCBLOC SYSTEM

PARAMETER IS NOT VALID.
Explanation: The syntax of the CSCBLOC system

initialization parameter in the IEASYSxx parmlib
member is incorrect.
System Action: The system defaults the CSCBLOC
parameter to CSCBLOC=ABOVE.
548
System Programmer Response: If necessary,

change the CSCBLOC parameter so it is in one of the
following formats:
CSCBLOC=ABOVE
CSCBLOC=BELOW
CSCBLOC=(ABOVE)
CSCBLOC=(BELOW)
Detecting Module: IEAVNPB1
IEA187I
FORMAT OF THE CON SYSTEM

PARAMETER IS NOT VALID.
Explanation: The CON parameter on the CONSOLE

statement in a CONSOLxx parmlib member is incorrect.
IEA332A.
message IEA332A.
System Programmer Response: Update the CON
system parameter in the CONSOLxx parmlib member if
necessary.

CONSOLxx
The parmlib member with a suffix of xx.
dev
The device number.
UNIT NOT SUPPORTED.
The system does not support the specified device.
NO IODEVICE STATEMENT FOR dev.
The specified console device was not defined in the
IODF.
System Action: The system ignores the specified
console.
device number and device type are specified in the
IODF and in a CONSOLE statement in the CONSOLxx
parmlib member.
IEA190I

IEA188I
CONSOLxx: NO MASTER CONSOLE

SPECIFIED.
Explanation: The CONSOLE statement in the

CONSOLxx parmlib member did not specify a console
with master authority.
CONSOLxx
The parmlib member, with the suffix

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
master authority.
system initialization, define a console with master
authority in the CONSOLxx parmlib member.
CONSOLxx: MASTER CONSOLE dev

WAS OFFLINE DURING IPL.
Explanation: The console with master authority

specified in the CONSOLxx parmlib member was offline
during initial program load (IPL). In the message text:
CONSOLxx
dev
The specified console device.
System Action: The system issues message IEA191I
and continues processing. Message IEA191I identifies
the master console.
IEA191I
CONSOLE dev (consname) text AS

MASTER CONSOLE

DEFINED
SELECTED
This message identifies the master console.

IEA189I
CONSOLxx: dev IGNORED. text

UNIT NOT SUPPORTED.
NO IODEVICE STATEMENT FOR dev.
The system does not support a specified console
device.
dev
The device number.
consname
The console name.
DEFINED
The CONSOLxx parmlib member defines the
console as the master console.
549
SELECTED
The system selected the console as the master
console. In this case, this message follows
message IEA188I, IEA189I, or IEA190I.
Operator Response: Enter a VARY command to alter
the master console if the current master console is
unacceptable.
IEA193I
CONSOLxx NOT USABLE. text

NOT USABLE. UNABLE TO SELECT MASTER.
REASON=reason-code
NOT USABLE. NO VALID CONSOLE STATEMENTS
FOUND.
NOT USABLE. I/O ERROR OCCURRED.
The system found an error while processing a

IEA192I
CONSOLxx dev ALTERNATE

DEFAULTED TO {consname|dev}.
REASON=reason-code
Explanation: The system selected an alternate

console.
dev
The device number in the CONSOLxx parmlib
member.
CONSOLxx
NOT USABLE. UNABLE TO SELECT MASTER.
REASON=reason-code
The system was unable to select a console with
master authority.
reason-code
1
consname
The default console name.
No full capability console is defined in the

CONSOLxx
No valid full capability console is defined in

the CONSOLxx parmlib member.
No online full capability console is defined

in the CONSOLxx parmlib member.
reason-code
The reason code. It is one of the following:
1
An alternate console was not specified in

the CONSOLxx parmlib member. In this
case, the system uses the master console
as the alternate console.
The alternate console is not a valid
console. The system uses the master
console as the alternate console.
The alternate console has an operating
mode that is not valid. For example, a
printer console is defined as the alternate
for a full capability console.
No alternate console is defined. The
system uses the master console.
System Action: The system uses the specified

console as the alternate console. The system continues
processing.
NOT USABLE. NO VALID CONSOLE STATEMENTS

FOUND.
No valid console statement is defined in the
NOT USABLE. I/O ERROR OCCURRED.
While the system was processing the CONSOLxx
parmlib member, an error occurred.
to ask the operator to specify a new CON system
parameter.
system initialization, specify a valid CON parameter in
IEA194I
CONSOLxx dev: HARDCOPY

DEFAULTED TO SYSLOG.
REASON=reason-code
System Programmer Response: Specify an alternate

console with a CONSOLE statement in the CONSOLxx
parmlib member, if desired.
Explanation: The hard-copy console specified in the

CONSOLxx parmlib member is not valid.
Detecting Module: IEAVG607, IEAVN613
CONSOLxx
550
dev
The device number.
reason-code
1
The console is not a specified console.

There may be no CONSOLE statement for
the console.
The console is not valid.
The console is a display device.
System Action: The system assigns the device used

for the system log as the default hard-copy log. The
system initialization, ensure that the device number and
the device type are the same in both the IODF and the
CONSOLE statement in the CONSOLxx parmlib
member. Ensure that a hard-copy device is defined as a
console in CONSOLxx.
IEA195I
CONSOLxx LINE lnnum; text

UNRECOGNIZED STATEMENT TYPE IGNORED.
keywd IGNORED FOR SUBSYSTEM CONSOLE.
CONSOLE STATEMENT IGNORED.
REASON=reason-code
99 CONSOLES DEFINED. STATEMENT IGNORED.
MISPLACED num STATEMENT IGNORED.
SYSTEM ERROR mmmm-nnnn
keyword IGNORED FOR SYSTEM CONSOLE.
The system found an error on a statement in a
CONSOLxx
lnnum
The line number in CONSOLxx containing the
statement in error.
UNRECOGNIZED STATEMENT TYPE IGNORED
The first non-blank or non-comment character string
on a statement was not a valid statement type. The
system skips data until it finds a valid statement
type.
keywd IGNORED FOR SUBSYSTEM CONSOLE.

The system ignores the keyword. The keyword is
not valid for a subsystem console.
keywd
The keyword name in CONSOLxx.
CONSOLE STATEMENT IGNORED.

REASON=reason-code
The system could not identify the DEVNUM
parameter on the CONSOLE statement. The
reason code, reason-code, is one of the following:
1
The DEVNUM keyword is not the first

keyword following the CONSOLE
statement type.
The DEVNUM keyword value was not

hexadecimal, did not fall in the range of
X'000' to X'FFF', or the value was not
SUBSYSTEM or SYSCONS.
**This reason code was deleted as of

MVS/SP 4.2**
A CONSOLE statement named a console

that was already defined as a multiple
console support (MCS) console.
99 CONSOLES DEFINED. STATEMENT IGNORED.

The system issues this message for each
CONSOLE statement it encounters beyond the 99
console definition maximum. The system ignores
consoles defined beyond the 99th console.
MISPLACED num STATEMENT IGNORED.
A CONSOLE, HARDCOPY, DEFAULT, or INIT
statement was not the first statement in the
CONSOLxx member. The system ignores the
incorrect statement.
num
The statement number in CONSOLxx.
SYSTEM ERROR mmmm-nnnn

The system received an unexpected return code
when parsing the CONSOLxx member.
mmmm-nnnn
The range of statements in the erroneous
CONSOLxx member.
keyword IGNORED FOR SYSTEM CONSOLE.
The specified keyword is not valid for a system
console. Valid keywords are NAME, ROUTCODE,
LEVEL, MONITOR, MSCOPE, CMDSYS, and UD.
System Action: If the message text is SYSTEM
ERROR mmmm-nnnn, the system stops processing the
CONSOLxx member and issues message IEA332A.
For all other errors, the system continues processing
the valid statements in the CONSOLxx parmlib member.
Operator Response: If the message text is SYSTEM
ERROR mmmm-nnnn, see the operator response for
message IEA332A. For other errors, notify the system
programmer.
If the system issued this message during the IPL of a
system into a sysplex, and no MVS consoles were
initialized on this system, the system console or other
extended MCS consoles may be activated and used for
console functions until CONSOLxx members of
SYS1.PARMLIB have been corrected.
551
System Programmer Response: Check for incorrect

statements and parameters in the CONSOLxx parmlib
member. Correct these statements or parameters. If the
error occurs again, search problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM
Support Center.
If you are running a sysplex, the IEARELCN utility may
be used to remove one or more console definitions.
This will allow systems which subsequently join the
sysplex to have a subset of consoles from their
CONSOLxx member of SYS1.PARMLIB to be defined
and available. See OS/390 MVS Planning: Operations
and OS/390 MVS Initialization and Tuning Reference for
details on the 99-console limit for CONSOLxx.
SUBSYS
UNRECOGNIZED KEYWORD keywd IGNORED.
The system could not identify a keyword on the
CONSOLE statement.
keywd
The unidentified keyword.
keywd VALUE IGNORED. REASON=reason-code

The system ignores an incorrect keyword value and
processes other valid data, except when the
keywords MSGRT and AREA are specified.
keywd
The incorrect keyword.
reason-code
The reason code, which is one of

the following:
Detecting Module: IEAVN600, IEAVN601, IEAVN602,

IEAVN611, IEAVN612, IEAVN615
The value does not

conform to the syntax of
the keyword, the value is
out of range for the
keyword, or the value is
out of range for the
consoles device type.
The FORMAT or XWTR

keyword values cannot
be specified on a
HARDCOPY statement
that does not have the
system log (SYSLOG) as
HARDCOPY.
A CONSOLE statement
defines a console with
the same name as a
console that already
exists. The keyword
specified an attribute
value that was different
from the attribute value
of the existing console.
In a sysplex, the value
does not match the
corresponding value of a
console with the same
name that is already
defined to the sysplex.
The system uses the
attribute of the existing
console. To obtain the
current console attribute
values, issue the D C
command.
The specified keyword

value differs from the
current sysplex value.
The value of RMAX

exceeds the subsystem
limit. The system sets
IEA196I
CONSOLxx stmt-type: text

UNRECOGNIZED KEYWORD keywd IGNORED.
IODEVICE STATEMENT UNIT APPLIED.
REASON=reason-code
keywd IGNORED. REASON=reason-code
INCONSISTENT keywd VALUE IGNORED.
MISSING RIGHT PARENTHESIS ASSUMED.
USE(xx) FORCED. REASON=reason-code
CONSOLE NOT ACTIVATED. REASON=reasoncode
DUPLICATE SPECIFICATION IGNORED.
DEVNUM ALREADY DEFINED. STATEMENT
IGNORED.
DUPLICATE keywd KEYWORD IGNORED.
DUPLICATE keywd VALUE IGNORED.
UNBALANCED COMMENT FOUND. DATA
IGNORED.
PREMATURE END OF FILE DETECTED.
DEL(RD) FORCED.
EXTRA keywd VALUES IGNORED.
DEFAULT: RMAX VALUE IGNORED.
REASON=reason-code
The system found an error while processing a
CONSOLE statement in a CONSOLxx parmlib member.
CONSOLxx
stmt-type
cccccccc, specifying the console name.
dev, specifying the device number.
CONSOLE
DEFAULT
HARDCOPY
INIT
552
the value of RMAX to

the subsystem maximum
limit.
6
The console group

definition as specified by
the CNGRP parameter
has been defined by
another system already
active in the sysplex.
The AREA specification

was not valid because
the total out-of-line
AREA exceeded the
screen size of the
device.
If the first system joining

the sysplex is at
MVS/ESA SP 5.1 or
higher, and the value
specified for RMAX is
less than 99, RMAX is
set to 99.
The ROUTTIME value

cannot be specified on a
single system. A value of
zero is used.
An MSCOPE or
CMDSYS keyword was
specified while the
system was running in
cross-system coupling
facility (XCF)-local mode
or as a single-system
sysplex (monoplex). The
MSCOPE or CMDSYS
keyword is only valid in a
multi-system sysplex
mode.
DEVNUM(SYSCONS)
was specified, but the
system console
hardware has not been
installed.
IODEVICE STATEMENT UNIT APPLIED.

REASON=reason-code
The UNIT parameter was specified incorrectly. The
system ignores this parameter and uses the unit
type defined in the IODF for the specified device
number.
reason-code
The reason code, which is one of the
following:
1
AUTH parameter that

was specified for a UNIT
of PRT.
The device type specified in the
keywd IGNORED. REASON=reason-code

The system rejected a parameter in the CONSOLxx
member.
keywd
The rejected keyword.
reason-code

the following:
1
The system ignores the

keywords DEL, CON,
SEG, RNUM, RTME,
AREA, PFKTAB, and
UTME. One or more of
these keywords were
specified for a UNIT of
PRT.
The system ignores the

The value of keywd is not consistent with a
previous value for that keyword.
For example, ROUTCODE(ALL,NONE) is
inconsistent because you cannot assign both all
and none of the routing codes to the same console.
The system accepts the first value (ALL in this
case).
keywd
The ignored value.

A right parenthesis is missing at the end of a
statement. The system assumes it is present.
The systems operating mode was changed to
maintain consistency with the AUTH or UNIT
keyword.
xx
The new value of the USE

parameter, which controls the
types of data sets that the system
can allocate on a tape or direct
access storage device (DASD)
volume.
reason-code

the following:
1
A statement contained
AUTH(MASTER) and
USE(MS) or USE(SD),
indicating that the
console had master
authority. Since a
console with master
authority must also have
553
full capability, the system

changes the parameter
to USE(FC).
2
An operating mode of full

capability or status
display was specified for
a printer console. The
system forces USE(MS).
CONSOLE NOT ACTIVATED. RC=reason-code.

The system did not activate the console.
reason-code

the following:
1
A console with the same

name already exists in
the sysplex and is
currently active on
another system.
The console that is

logically associated with
this name was assigned
to a system component.
A console on a system
joining the sysplex has
the same name as the
failed master console.
The joining systems
console is not activated.

The system ignored a duplicate HARDCOPY,
DEFAULT, or INIT statement.
stmt-type
The duplicate statement type.
IGNORED.
The system ignored the device number because
the same device number was specified in a
previous CONSOLE statement.
DUPLICATE keywd KEYWORD IGNORED
Keyword keywd was specified more than once on
the CONSOLE statement.
keywd
The duplicate keyword.

A keyword on the statement has a duplicate value.
The system ignores the duplicate value.
keywd
The ignored keyword.
UNBALANCED COMMENT FOUND. DATA IGNORED

The system found a slash asterisk (/*) indicating the
554
beginning of a comment, but did not find an

asterisk slash (*/) to indicate the end of the
comment before the end of the file.
PREMATURE END OF FILE DETECTED.
The end of file was reached before the system
completed parsing a statement.
DEL(RD) FORCED.
The system changed the deletion mode to action
messages retained RD from a deletion mode of
either automatic message deletion Y or manual
message deletion N.
EXTRA keywd VALUES IGNORED.
The keyword had too many values specified. The
system ignores the extra values.
keywd
The ignored keyword.
System Action: Depending on the message text, the

system does one of the following:

The system ignores an incorrect keyword value and
processes other valid data, except when the
keywords MSGRT and AREA are specified.
IODF IODEVICE STATEMENT UNIT APPLIED.
REASON=reason-code
The system ignores this parameter and uses the
unit type defined in the IODF for the specified
device number.
The system accepts the first value.
The system assumes the parenthesis is present.
The systems operating mode was changed to
maintain consistency with the AUTH or UNIT
keyword.
CONSOLE NOT ACTIVATED. RC=rc.
The system does not activate the console.
The system ignores the duplicate HARDCOPY,
DEFAULT, or INIT statement.
IGNORED.
The system ignored the device number because
the same device number was specified in a
previous CONSOLE statement.
The system ignores the duplicate value.
In all cases, the system continues processing the
statements in the CONSOLxx parmlib member.
system initialization, correct the statement(s) in the

CONSOLxx member.
4. After the system programmer corrects the member,

reIPL the system.

could not use a data set member that was to contain an
alternate version of the master scheduler JCL.
System Programmer Response: Validate that the

MSTRJCL parameter in the IEASYSxx parmlib member
specifies a MSTJCLxx parmlib member or MSTJCLxx
CSECT in linklib that exists and is correct. If the
member does not exist or is not correct, create or
correct the member. Then ask the operator to enter the
MSTRJCL system parameter again (in response to this
message). Otherwise, ask the operator to enter the
MSTRJCL parameter again (in response to this
message).
Source: Master scheduler
memberxx
The member of SYS1.LINKLIB or SYS1.PARMLIB
that the system could not use.
Detecting Module: IEAVN600, IEAVN601, IEAVN602,

IEAVN610, IEAVN611, IEAVN612, IEAVN615
IEA200I
memberxx - text
IEA208I
text
A description of the error, which is one of the
following:
MEMBER NOT FOUND
The system could not find the MSTJCLxx
parmlib member or MSTJCLxx load module in
linklib that is to contain the alternate version of
the master scheduler JCL.
I/O ERROR DURING BLDL
An input/output error occurred when the
system used the build list to find the specified
module.
I/O ERROR DURING READ
An input/output error occurred when the
system was reading the data set that was to
contain the alternate version of the master
scheduler JCL.
UNEXPECTED END OF FILE
The system found an end-of-file (EOF) before
the normal end of processing.
INTERNAL CONVERSION ERROR
An internal error occurred.
UNEXPECTED FAILURE
An internal error occurred.
respecify the MSTRJCL system parameter.
func FUNCTION INOPERATIVE

detected unrecoverable errors while initializing a
function. The function is now inoperative because of
these errors. This is probably an installation error.
func
The function. If func is LPA PACKING, the PAK
parameter was not specified, and NIP could not
read the default IEAPAK00 parmlib member.
System Action: The system continues initialization. If
NIP found an error in the PAK parameter, NIP will ask
the operator to specify it again or to cancel the request.
Otherwise, the system usually issues another message
to identify the errors.
The system issues other messages about the problem.
Operator Response: See operator responses for
accompanying messages.
System Programmer Response: See system
programmer responses for accompanying messages.
Source: The following:
v Nucleus initialization program (NIP)
v Master scheduler
v Contents supervision
Operator Response: Do the following:

OBTAIN FAILED FOR dsname DATA
SET
1. Contact the system programmer. Provide the

message number and message text.
IEA211I
2. At the request of the system programmer, do one of

the following in response to the prompt to respecify
the MSTRJCL system parameter:

could not find a data set for one of the following
reasons:
v Specify the MSTRJCL system parameter on the

console; then press ENTER.
v The operator did not mount the volume containing the

data set
v Press ENTER on the console.
v The data set control block (DSCB) was not in the

volume table of contents (VTOC)
3. If the system prompts for the MSTRJCL system

parameter again, ask the system programmer to
correct the specified member.
v A permanent I/O error occurred
555
IEA214A
dsname
v If the volume that contains the data set is not
mounted, mount it.
DUPLICATE SYSRES volname FOUND

ON DEVICE dev. VERIFY THAT
CORRECT DEVICE WAS USED FOR
IPL. DUPLICATE DEVICE WILL REMAIN
OFFLINE. REPLY CONT TO
CONTINUE IPL
v If the volume is mounted, record the device number.

Notify the system programmer.

found a direct access storage device (DASD) with
volume label the same as the SYSRES device (IPL
device).
v List the VTOC of the volume that is supposed to

contain the data set.
volname
The duplicate volume serial name.
v If the data set is not on the volume, create the data

set.
dev
Source: DFSMSdfp
Detecting Module: IEAVNPM3
IEA213A
DUPLICATE VOLUME volname FOUND

ON DEVICES dev1 AND dev2. REPLY
DEVICE NUMBER WHICH IS TO
REMAIN OFFLINE

found direct access storage devices (DASD) with the
same volume label.
volname
The name of the duplicate volume.
The device number of the device on which the

duplicate volume serial name was found.
System Action: The system suspends nucleus
initialization. When the operator replies CONT, the
system issues message IEA313I and marks as offline
the device that has the same volume serial name as the
SYSRES. Then the system continues initialization.
Operator Response: The operator should verify that
the correct device has been used to IPL the system as
specified in the system control frame. If the wrong
volume has been chosen, the operator must correct the
load device in the system control frame and reIPL. If the
correct device has been used for IPL, then the operator
should indicate that the IPL can continue.
dev1
The device number for the first device with a
duplicate volume label.
dev2
The device number for the second device with a
duplicate volume label.
Explanation: The write to operator with reply (WTOR)

message buffers are currently 80% full.
System Action: The system suspends nucleus

initialization. When the operator identifies which device
to put offline, the system issues message IEA313I and
marks that device offline. The other device will be
online. Then the system continues initialization.
IEA230E
WTOR BUFFER SHORTAGE. 80% FULL

The system puts unauthorized tasks issuing WTOR
macros in a wait state.
Operator Response: Do one or more of the following:
v Reply to outstanding WTOR messages.
Operator Response: The operator must determine

which of the two devices having the same volume label
name is correct. The operator can refer to the required
volumes list for your installation or make the
determination by some other means. When the
determination is made, reply to this message with the
device number of the device that you want to place
offline.
v Cancel any jobs that are currently issuing WTOR

messages.
When specifying the device, you can optionally precede

the device number with a slash (/).

556

the value of the WTOR buffer limit.
System Programmer Response: If the shortage
persists, increase the value of RLIM in the CONSOLxx
parmlib member.
Detecting Module: IEAVMQWR
IEA231A
SEVERE WTOR BUFFER SHORTAGE.

100% FULL
Explanation: The outstanding write to operator with

reply (WTOR) messages have filled the buffer.
System Action: The system puts tasks issuing WTOR
macros in a wait state (if they did not specify a busy exit
return) until the operator either reduces the number of
outstanding WTORs or increases the number of WTOR
buffers.
Operator Response: Enter a DISPLAY R,R command
to see the accumulated WTOR messages. Do one of
the following:
v Reply to outstanding WTOR messages.
v Cancel jobs that are currently issuing WTOR macros.
the number of WTOR buffers.
Note: The RLIM value cannot be higher than the
RMAX value (RMAX is the highest possible
reply ID). If you need to increase RLIM higher
than RMAX, consider entering the CONTROL
M,RMAX command to increase RMAX. To
determine the current values of RLIM and
RMAX, issue the K M,REF command.
IEA233I
Explanation: When the LOAD command was entered,

the initialization message suppression indicator (IMSI)
was specified as a value other than a blank, A, P, or M.
The system takes the default actions: It suppresses
informational messages and does not prompt for system
parameters.
IEA234I
System Programmer Response: If the shortage

recurs, increase the value for RLIM or RMAX in the
NO MCS CONSOLES DEFINED
Explanation: No multiple console support (MCS)

consoles are currently defined to the system.
Operator Response: Perform all operator functions on
extended MCS consoles, subsystem allocatable
consoles, or the system console.
IEA235I
The value of RMAX controls the number of

digits in all reply IDs. For example, increasing
RMAX to 100 (or higher) causes all WTORs to
have 3-digit reply IDs. This might affect
automation routines. Check with the system
programmer before increasing RMAX higher
than 99.
LOAD COMMAND IMSI VALUE OF C

NOT VALID. DEFAULTED TO BLANK
RECURSIVE ABEND IN SYSCON

DOMLIST QUEUE PROCESSING.
QUEUEING SUSPENDED. DOMS TO
SYSTEM CONSOLE MAY BE LOST.
Explanation: An error occurred when the system was

processing the system console delete operator message
(DOM) queue.
System Action: The system does not queue DOM
requests to the system console. Some held messages
may not be deleted.

IEA232I
WTOR BUFFER SHORTAGE RELIEVED
Explanation: In response to message IEA230E or

IEA231A, this message indicates that the shortage of
buffer space for write to operator with reply (WTOR)
messages was relieved.
Detecting Module: IEAVG719

IEA236I
SYSCON DOMLIST QUEUE

PROCESSING RESUMED.

The system deletes messages IEA230E and IEA231A,
if they are outstanding.
Explanation: The system resumed processing of the

system console delete operator message (DOM) queue.

557
IEA238I
SYSTEM CONSOLE [PRIORITY]

OPERATOR INPUT PROCESSING
ABENDED, PROCESSING
REESTABLISHED, LAST INPUT MAY
BE LOST
Explanation: The system deleted and reestablished

the listener exit routine. Commands that the operator
entered before the error occurred may be lost.
PRIORITY
The system is not accepting operator input
from the screen that accepts priority
commands.
IEA247I
Explanation: For system initialization, the system is

using the IEASYSxx parmlib member displayed in the
message text for system parameters.
If you are using multiple IEASYSxx parmlib members,
the system displays message IEA008I in place of this
message.
xx...x

IEA240I
OBSOLETE BLDLF OR BLDL SYSTEM

PARAMETER(S) IGNORED
Explanation: Either the operator or the IEASYSxx

parmlib member specified obsolete system parameters
BLDLF and/or BLDL.
System Action: The system ignores BLDLF or BLDL
parameters.
Operator Response: Do not specify BLDLF or BLDL
for this system.
System Programmer Response: Remove any BLDLF
and BLDL specifications from the IEASYSxx parmlib
members.
Source: Contents supervision (CSV)
IEA246I
memname ID xx SELECTED
Explanation: For system initialization, the system

selected the parmlib member memname.
memname
The parmlib member selected for initial program
load (IPL) processing. memname is one of the
following:
v LOAD
v NUCLST
xx The identifying number of the parmlib member.
558
Contains the full product name, version,

release, modification level and FMID. For
example, in OS/390 Release 2, xx...x is
01.02.00 JBB6602.
This field can be changed by the installation
using the SPZAP service to change the value
in the CVTVERID field of the communication
vector table (CVT).

Operator Response: If the system did not process the
previous command, enter the command again from the
system console.
USING IEASYSxx FOR xx...x

IEA248I
NUCLEUS MODULE modname IS

LISTED IN IEANxdd1 AND IEANxdd2
Explanation: The system detected a duplicate module

entry appearing in two nucleus module lists (NML). This
may represent an error in a non-MVS product.
modname
The duplicated module name
IEANxdd1
The first nucleus module list
IEANxdd2
The second nucleus module list
system loads module modname as part of the system
nucleus.
correct version of module modname resides in the
SYS1.NUCLEUS data set. Delete the module name
from one of the NMLs listed in the message. Do not
delete the name from both NMLs unless this module
should not be loaded as part of the system nucleus.
IEA250I
[RER | RDE ] PARAMETER NOT VALID.

DEFAULT OF NO TAKEN.
Explanation: One of the system parameters, RER or

RDE, was specified incorrectly in the IEASYSxx parmlib
member.

System Programmer Response: This is probably an
installation error. Make sure that the RER or RDE
parameter is correct.
IEA251I
{DEVSUPyy: | IGDDFPKG:} INVALID

SYNTAX. MEMBER PROCESSING
TERMINATED ON LINE nnnn
Explanation: The IGDDFPKG or the DEVSUPyy

parmlib member contains an incorrect keyword.
--or-DEVSUP MTL SHARE IS IGNORED

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
which installation default applies. The message is
informational, and requires no action or response.
In the message text of the first variation:
V3
Is ISO/ANSI Version 3
V4
Is ISO/ANSI Version 4
yy
The member number
Forced V3
ISO/ANSI Version 3 is being forced
The incorrect keyword.
Forced V4
ISO/ANSI Version 4 is being forced
keyword
System Action: IPL continues.
keyword parameter.
Source: DFSMSdfp
IEA252I
{DEVSUPyy: | IGDDFPKG:} INVALID

SYNTAX. MEMBER PROCESSING
TERMINATED ON LINE nnnn
Explanation: The DEVSUPyy or IGDDFPKG parmlib

member contains a syntax error.
yy
The number of the member being processed.
nnnn
The line number, relative to the beginning of

the member, where the error was found.

syntax.
Source: DFSMSdfp
IEA253I
DEVSUP 3480X RECORDING MODE

DEFAULT IS
[NO-COMPACTION|COMPACTION]
DEVSUP ISO/ANSI TAPE LABEL
VERSION DEFAULT IS (V3|V4|FORCED
V3|FORCED V4)
DEVSUP TAPE OUTPUT DEFAULT
BLOCK SIZE LIMIT IS
[value|valueK|valueM|valueG;]
DEVSUP COPYSDB DEFAULT is
[YES|NO|INPUT| SMALL|LARGE]
value
Is a numeric value
Note: For descriptions of forced and other DEVSUPxx

parameters displayed in this message, see
OS/390 MVS Initialization and Tuning Reference.
Message DEVSUP MTLSHARE=YES SPECIFIED is
issued when MTLSHARE=YES is specified in the active
DEVSUPxx member of PARMLIB. This message can be
issued on DFSMS 1.2, DFSMS 1.3, and DFSMS 1.4
systems.
Message DEVSUP MTL SHARE IS IGNORED is issued
when MTLSHARE=YES is specified in the active
DEVSUPxx member of PARMLIB. This message can be
issued on OS/390 DFSMS Version 2 Release 10 and
higher systems.
Source: DFSMSdfp
IEA254I
CONSOLxx: RLIM EXCEEDS RMAX,

RLIM IS SET TO RMAX
Explanation: The RLIM specified on the INIT

statement exceeds the RMAX value on the DEFAULT
statement, if specified, or the default value of RMAX.
System Action: The RLIM for the sysplex is set to the
RMAX value.
Operator Response: Report the error to the system
programmer.
Application Programmer Response: Adjust either
the RMAX or RLIM value in the CONSOLxx member to
insure that RMAX >= RLIM.
--or-DEVSUP MTLSHARE=YES SPECIFIED

559
IEA255I
CONSOLE INITIALIZATION DELAYED.

AWAITING CONSOLE PARTITION
CLEANUP OF SYSTEM sysname.
Explanation: System initialization is delayed so

another system in the sysplex can complete console
partition cleanup processing for the system specified in
the message text.
sysname
The system that is undergoing console partition
cleanup.
System Action: The system delays initialization for
five seconds while another system in the sysplex
completes console partition cleanup processing. The
system may issue message IEA256I or IEA255I again.
Operator Response: If the system issues message
IEA256I after this message, no action is necessary. If
the system issues this message again, restart or
partition from the sysplex any systems that are in a
stopped or disabled state.
sysname
The name of the system that was partitioned.
IEA259I
CLOCKxx: ENVIRONMENT NOT VALID

FOR SIMETRID
Explanation: The SIMETRID parameter was

incorrectly specified in a CLOCKxx parmlib member.
The SIMETRID parameter is only valid when the system
is running as a virtual machine (VM) or processor
resource/systems manager (PR/SM) guest.
CLOCKxx
System Action: The system ignores all CLOCKxx
parmlib members. The system issues message
IEA906A.
Operator Response: Reply to message IEA906A. If
you press the enter button in reply to message
IEA906A, the system sets the following default values:
v No operator prompting for time-of-day (TOD) clock

initialization.
IEA256I
v External Time Reference (ETR) synchronization

mode. ETR is the MVS generic name for the IBM
Sysplex Timer (9037) or equivalent.
CONSOLE INITIALIZATION RESUMED.
Explanation: The system resumed console

initialization after another system in the sysplex
completed console partition cleanup.
System Action: The system issues message IEA255I
before issuing this message. System initialization
continues.
IEA257I
CONSOLE PARTITION CLEANUP IN

PROGRESS FOR SYSTEM sysname
Explanation: Console partition cleanup is in progress,

after a system in the sysplex was partitioned.
sysname
The name of the system that was partitioned.
IEA258I
CONSOLE PARTITION CLEANUP

COMPLETE FOR SYSTEM sysname
Explanation: Console partition cleanup completed

after a system in the sysplex was partitioned.
560
v ETRDELTA value of 10 seconds.

v Time zone constant obtained from ETR (or set to 0 if
time zone cannot be obtained from ETR).
synchronization mode (ETRMODE) in the CLOCKxx
parmlib member.
If you specify ETRMODE NO, you cannot specify
ETRZONE YES.
IEA260I
THE CPC IS NOW OPERATING IN ETR

MODE.
Explanation: The central processing complex (CPC) is

now synchronized with the External Time Reference
(ETR). ETR is the MVS generic name for the IBM
System Action: Processing continues in ETR
synchronization mode.
IEA261I
NO ETR PORTS ARE USABLE. CPC

CONTINUES TO RUN IN LOCAL MODE.
Explanation: There is no operational port from the

central processing complex (CPC) to the External Time
Reference (ETR). ETR is the MVS generic name for the
IBM Sysplex Timer (9037) or equivalent.
System Action: Processing continues in local
synchronization mode. The system records the error in
the logrec data set.
Operator Response: Check the system console
associated with this processor. If you have already
contacted the IBM Support Center, no further action is
required.
Otherwise, contact 9037 hardware support. Note that
the same event might occur on more than one of the
processors in a sysplex.
IEA262I
ETR PORT n IS NOT OPERATIONAL.
Explanation: The specified External Time Reference

(ETR) port is not working. ETR is the MVS generic

The system records the error in the logrec data set.
Operator Response: Contact your
configuration/cabling personnel and have the
configuration error corrected. Provide the logrec data
set error records.
Detecting Module: IEATPORT
IEA264I
PORT n TO ETR xx WAS DISABLED

BECAUSE IT IS INCORRECTLY
CONNECTED.
Explanation: The system disabled the specified port

to an External Time Reference (ETR). ETR is the MVS
generic name for the IBM Sysplex Timer (9037) or
equivalent. The port was not connected to the same
ETR as the link from the remaining or initial port.
The port number.
xx
The ETR identifier. If a question mark appears,

there was no ETR identifier available from the
port.



set error records.
Operator Response: One of the following:
The port number.
v If an ETR is installed, check the system console

contacted the IBM Support Center, no further action
is required.
v If an ETR is not installed, ensure that the CLOCKxx
member of SYS.PARMLIB contains ETRMODE NO
and ETRZONE NO.

IEA265I
UNABLE TO SYNC TOD CLOCKS TO

ETR. CPC CONTINUES IN LOCAL
MODE.
Explanation: The central processing complex (CPC)

could not synchronize with the External Time Reference
(ETR). This occurred for one of the following reasons:
v A hardware error occurred.
v The time difference between the ETR and time-of-day

(TOD) clocks exceeded the ETRDELTA value in a
CLOCKxx parmlib member.
IEA263I
ETR is the MVS generic name for the IBM Sysplex

Timer (9037) or equivalent.
BOTH CPC PORTS ARE CONNECTED

TO THE SAME SIDE OF ETR xx.
Explanation: Both central processing complex (CPC)

ports are connected to the same side of a coupled
External Time Reference (ETR). ETR is the MVS
equivalent.
System Action: The system continues processing in

local synchronization mode. The system records the
error in the logrec data set.
Provide the logrec data set error records.
xx
Detecting Module: IEATESMR
The ETR identifier.
561
IEA266I
CLOCKxx: {ETRMODE NO AND

ETRZONE YES|OPERATOR PROMPT
AND SIMETRID} ARE MUTUALLY
EXCLUSIVE PARMS.
Explanation: Both ETRMODE NO and ETRZONE

YES, or OPERATOR PROMPT and SIMETRID, were
specified in a CLOCKxx parmlib member. The timer
synchronization mode must be External Time Reference
(ETR) (ETRMODE YES) to obtain the time zone value
from the ETR. ETR is the MVS generic name for the
CLOCKxx
IEA906A.
you press the enter button in reply to message
IEA906A, the system sets the following default values:
v No operator prompting for time-of-day (TOD)
initialization.
v ETR synchronization mode.

The port number.
System Action: The system disables the port.

required.
IEA269I
A CPC SIDE ID CHANGE FROM SIDE x

TO SIDE y HAS OCCURRED.
Explanation: The central processing complex (CPC)

switched from using the External Time Reference (ETR)
ports on one side to the ports on another side. ETR is
the MVS generic name for the IBM Sysplex Timer
(9037) or equivalent.
v ETRDELTA value of 10 seconds.
v Time zone constant obtained from ETR (or set to 0 if

time zone cannot be obtained from ETR).
x, y

synchronization mode (ETRMODE) in the CLOCKxx
parmlib member.
If you specify ETRMODE NO, you cannot specify

ETRZONE YES.
Detecting Module: IEATESMR

IEA270I

IEA267I
ETR PORT n IS NOW AVAILABLE.
Explanation: An External Time Reference (ETR) port

is now working. ETR is the MVS generic name for the
The port number.
The side identifiers.
BOTH PORTS TO THE ETR HAVE

BEEN DISABLED. CPC CONTINUES IN
LOCAL MODE.
Explanation: The system disabled both ports to an

External Time Reference (ETR). ETR is the MVS
equivalent.
System Action: Processing continues in local mode.
set error records.

IEA271I
IEA268I
ETR PORT n IS DISABLED DUE TO AN

EXCESSIVE NUMBER OF STATE
CHANGES.
Explanation: The system detected an excessive

number of availability state changes for an External
Time Reference (ETR) port. ETR is the MVS generic
562
ETR TIME OFFSET CHANGES HAVE

OCCURRED.
Explanation: The system encountered a problem with

the External Time Reference (ETR). One of the
following occurred:
v A leap second increment or decrement
v The local time offset changed because of a change

to or from local daylight savings time
079
Internal bus failed.
080
Battery clock module failed.
081
Wrong card in card location XX.
082
Backup data invalid.
084
Identical Unit Addresses on the Base

cards.
089
Warning: Power-on diagnostic failure.
090
Unable to communicate with other

unit.
093
Warning: configuration mismatch on

CLO links.
094
Warning: ETS configuration conflict.
098
Port card in slot 0 failed.
reason-code
099
A reason code explaining the error follows. For

more information about the reason codes, see
Maintenance Information for the 9037 Sysplex
Timer.
100
101
102
033
CLO Links cross-cabled.
103
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

console.
109
Port 5 failed.
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

responding.
112
Port 8 failed.
113
Port 9 failed.
046
The external time source reported a

synchronization change.
114
Port 10 failed.
047
The external time source is not

synchronized.
115
Port 11 failed.
116
Port 12 failed.

Detecting Module: IEATTOC
IEA272I
ETR SERVICE IS REQUESTED.

Explanation: The External Time Reference (ETR)

requires service. ETR is the MVS generic name for the
065
Base card failed.
117
Port 13 failed.
066
Port card in card location 2 failed.
118
Port 14 failed.
067
119
Port 15 failed.
068
120
Port 16 failed.
069
121
Port 17 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.
563
127
Port 23 failed.

Operator Response: The reason code indicates that
service is required. Check the system console
associated with this processor. If the system has
required.

Detecting Module: IEATPSDH
IEA276I
ETR ATTACHMENT DAMAGE WAS

DETECTED.
Explanation: The system found that the External Time

Reference (ETR) attachment was damaged. ETR is the
MVS generic name for the IBM Sysplex Timer (9037) or
equivalent.
System Action: The system attempts to validate the

damaged hardware. The system continues processing.
Detecting Module: IEATEEIH, IEATESMR

Detecting Module: IEATEADH
IEA273I
TOD CLOCKS DYNAMICALLY

ADVANCED TO MAINTAIN ETR
SYNCHRONISM.
Explanation: After an External Time Reference (ETR)

synchronization check, the system synchronized the
time-of-day (TOD) clocks again. ETR is the MVS
equivalent.
The channel path measurement facility (CPMF) stops or
enters a restartable error state. The system restarts the
CPMF.
Resynchronization may have created a gap in
timestamps.
Detecting Module: IEATESCH
IEA274W
THE ONLY ONLINE TOD CLOCK HAS

FAILED.
Explanation: The last, or only, online time-of-day

(TOD) clock failed.
wait state X'A1E'.
IEA277I
TIMING FACILITY DAMAGE WAS

DETECTED.
Explanation: The system found that the time-of-day

(TOD) clock or the TOD synchronization facility was
damaged.
Detecting Module: IEATTFDH
IEA278I
THE LINK FROM PORT n TO THE ETR

IS TUNED.
Explanation: All link segments from the specified port

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.
The port number.


wait state X'A1E'.
Detecting Module: IEATEEIH, IEATESGR

programmer response for wait state X'A1E'.
IEA279I

Detecting Module: IEATESCH, IEATESC2,
IEAVRTOD, IEATTSCH, IEATTFDH
IEA275I
PRIMARY SYNCHRONIZATION
FACILITY DAMAGE WAS DETECTED.
Explanation: The system found that the primary

synchronization facility was damaged.
564
ALL CLOCK RELATED SET

COMMANDS ARE IGNORED WHEN IN
ETR MODE.
Explanation: The operator entered a SET command

while the system was running in External Time
Reference (ETR) synchronization mode. ETR is the
MVS generic name for the IBM Sysplex Timer (9037) or
equivalent.
System Action: The system ignores the SET
command.
Detecting Module: IEA6503D
IEA280I
ETR DATA CANNOT BE ACCESSED.

CPC CONTINUES IN LOCAL MODE.
Explanation: One of the following occurred:

v Timer supervision could not obtain the required data
words from the External Time Reference (ETR).
v The data words that timer supervision obtained from
the ETR are not valid.
[PORT STATUS CANNOT BE DETERMINED.]

[ETR DATA COULD NOT BE OBTAINED FOR CPC
PORT 0]
[ETR DATA COULD NOT BE OBTAINED FOR CPC
PORT 1]

synchronism mode.
required.
Or
hh.mm.ss ETR STATUS

SIMETRID=nn
ETR SIMULATION MODE,
Both messages are in response to the DISPLAY ETR

command.
In the first message text:
hh.mm.ss
The hour (00-23), minute (00-59), and second
(00-59) that the system issued this message.
IEA281I
mode
The current synchronization mode, as follows:
ETR SYNC CHECK THRESHOLD HAS

BEEN EXCEEDED. CPC CONTINUES IN
LOCAL MODE.
ETR
Explanation: The number of External Time Reference

(ETR) synchronization checks exceeded the number
allowed by the system. ETR is the MVS generic name
for the IBM Sysplex Timer (9037) or equivalent.
synchronization mode.
Provide the logrec data set error records.
LOCAL
The operator set the system TOD clocks.
The system TOD clocks are synchronized
to a local oscillator.
<==
==>
An arrow pointing to the active ETR port.
op The operational status of the ETR port, as follows:
Detecting Module: IEATESCH

IEA282I
OPERATIONAL
The port is working.
text
Explanation: Where text is one of the following

messages:
hh.mm.ss ETR STATUS SYNCHRONIZATION

MODE=mode CPC SIDE=n
[CPC PORT 0 [<==] active [==>] CPC PORT 1
op
op
enb
enb
[CPC PORT 0 [<==] active [==>] CPC PORT 1
op
op
enb
enb
ETR NET ID=etrnet
ETR NET ID=etrnet
ETR PORT=etrport
ETR PORT=etrport
ETR ID=etrid
ETR ID=etrid
The system time-of-day (TOD) clocks are

synchronized to an External Time
Reference (ETR).
NONOPERATIONAL
The port is not working.
enb
ENABLED
MVS has enabled the port.
DISABLED
MVS has disabled the port.
etrnet
The ETR network identifier, in decimal.
etrport
The ETR port number, in decimal.
[THE ETR FACILITY IS NOT INSTALLED.]

565
etrid
The ETR identifier, in decimal.
THE ETR FACILITY IS NOT INSTALLED
There is no ETR installed on the system.
PORT STATUS CANNOT BE DETERMINED
The system cannot communicate with the ETR.
The second message text is displayed if SIMETRID=nn
in CLOCKxx is specified. In the second message text:
hh.mm.ss
(00-59) that the system issued this message.
nn The simulated sysplex timer identifier ranging from
X'00' to X'1F'.
Detecting Module: IEATDISP
v Enter the DISPLAY ETR command to display

information about the port.
Detecting Module: IEATCMD
THE LINK FROM PORT n TO THE ETR
IS NOT TUNED.
IEA285I
Explanation: One or more link segments in the path

from the specified port to the External Time Reference
(ETR) are not tuned. An untuned link has had no
transmission adjustments made to account for its length.
The port number.
System Action: Processing continues normally, unless

a resynchronization of the time-of-day (TOD) clock is
required. If a resynchronization is required, the system
will switch to local mode.
IEA283I
ETR PORT n IS ENABLED.
Explanation: An External Time Reference (ETR) port

is enabled. ETR is the MVS generic name for the IBM
The port number.

Detecting Module: IEATCMD
IEA284I
ETR PORT n CANNOT BE ENABLED.
Detecting Module: IEATEEIH, IEATESMR

IEA287I
IGDDFPKG {DFSMS OFFERING|DFSMS

FEATURE} IS n
Explanation: This message is issued during IPL to

show which DFSMS/MVS offering or feature was
specified in the IGDDFPKG parmlib member.
The offering or feature value specified. For

information about the offering or feature value, refer
to the OS/390 MVS Initialization and Tuning
Reference.
Explanation: The system cannot enable an External

Time Reference (ETR) port for one of the following
reasons:
v The installation requested local synchronization

mode, meaning that ETR ports must be disabled.
Detecting Module: IEAVNP16, IGDSMSPK
v The ETR Facility is not installed.
IEA297W
v The system cannot communicate with the ETR.

The port number.

v Wait 30 seconds.
v Enter the SETETR command again.
If the system issues message IEA284I again, the port
cannot be enabled.
566
Source: DFSMS/MVS
LSQA IS EXHAUSTED IN A
NON-MEMTERMABLE ADDRESS
SPACE
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
of the program which issued the SVC.
wait state and issues message IEA297W.
Operator Response: Provide a stand-alone dump if
requested by the system programmer. ReIPL the
system.
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

fix. If no fix exists, contact IBM support center. Provide
the stand-alone dump.
System Action: If the missing member is a NIP

module, the system enters a disabled wait state. If not,
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
Explanation: During system initialization, an incorrect

MAXCAD value was specified in one of two ways:
v In the IEASYSxx parmlib member
v In the operator response to message IEA101A
xxxxxx The incorrect MAXCAD value

System Action: Initialization continues with the default
MAXCAD value of 25.
Operator Response: ReIPL may be done to enter a
correct value, but is not required.
System Programmer Response: Respecify the
MAXCAD value by doing one of the following:
v Ask the operator to enter a correct value in response
to message IEA101A.
v Correct the value specified in the IEASYSxx member.
Source: Supervisor control
Detecting Module: IEAVNPO9
IEA299I
CONDITIONAL RIM mod NOT FOUND

IN SYS1.NUCLEUS. INITIALIZATION
CONTINUES
Explanation: During nucleus initialization, the nucleus

initialization program (NIP) could not find an optional
resource initialization module (RIM) in the
SYS1.NUCLEUS data set.
mod
The missing optional RIM
System Action: Nucleus initialization continues.

Detecting Module: IEAVNIPM
IEA300I
I/O ERROR DURING BLDL FOR mem IN

dsname
Explanation: An uncorrectable I/O error prevents the

nucleus initialization program (NIP) from reading a
directory entry for a member in a data set. This is
probably a hardware error.
mem
The member name
dsname

Detecting Module: IEAVNIPM, IEAVNP13,
IEAVNPM4, IEAVNPM3
IEA301I
mem {NOT FOUND|IS ALIAS} IN

dsname|PARMLIB
Explanation: The nucleus initialization program (NIP)

detected an error condition.
Note: This message can also be issued for a
non-existing member of SYS1.LINKLIB; check
the parmlib member for any typographical errors.
mem NOT FOUND IN dsname

NIP could not find member mem of data set
dsname.
mem IS ALIAS IN dsname
Member mem is an alias, but the directory of data
set dsname also contains an alias entry for this
member.
dsname
If the parmlib concatenation consists of only one
data set, this is the name of that data set.
PARMLIB
If the parmlib concatenation consists of more than
one data set, the member was not found in any of
the parmlib data sets.
This message is often accompanied by messages
IEA324I and IEA336A in this sequence:
IEA301I IEASYS00 NOT FOUND IN SYS1.PARMLIB
This message occurs even if the operator specified
IEASYSxx parmlib members other than IEASYS00.
IEA324I SYSP INPUT TERMINATED IN IEASYS00
IEA336A RESPECIFY PARAMETERS OR PRESS
ENTER TO CANCEL
This combination occurs when NIP cannot find the
primary IEASYSxx member, IEASYS00, while the
system is processing the operators response to
message IEA101A.
System Action: If the missing member is a required
NIP module, the system enters a disabled wait state. If
not, processing continues.
If message IEA301I is accompanied by messages
IEA324I and IEA336A, the system resumes processing
after the operator replies to message IEA336A.
The data set containing the member

567
Operator Response: When message IEA301I is

followed by IEA324I and IEA336A in the sequence
shown above, reply to IEA336A by specifying the SYSP
system parameter so that the system can access
IEASYSxx parmlib members.
System Programmer Response: If the error occurred
for the link list or LPA, determine what library the
member is in. Determine if the library needs to be
added to the concatenated list. Reinitialize the system.
IEA304W

encountered an error and the system enters a wait
state.
cde
The last three digits identify the wait state

code. See OS/390 MVS System Codes for a
description of the wait state code and for a
description of the order of the bits.
mod
Identifies the NIP module that was in control

when the system entered the wait state.
If the error occurred in SYS1.PARMLIB, add the missing

member to the data set.
If the member was in the data set, search problem
exists, contact the IBM Support Center. Note that the
IBM Support Center might request a stand-alone dump
if the problem has recurred.
Detecting Module: IEAVNIPM, IEAVNP13,
IEAVNPC5, IEAVNPM4
SYSTEM WAIT STATE - CODE cde

DURING mod INITIALIZATION
System Action: The system enters a wait state.

the wait state issued.
programmer response for the wait state issued.
IEA303W
ABEND cde REASON rsn DURING

INITIALIZATION UNDER RIM dsname
[modname NOT FOUND]
Explanation: During nucleus initialization, a system

function abended.
In the message text,
cde
A hexadecimal abend code
rsn
The reason code from register 15 that was

specified on the REASON keyword of the
ABEND macro.
dsname
IEA305A
INVALID REPLY FORMAT - RESPECIFY
Explanation: During nucleus initialization, the last

reply entered through the console was not in correct
format.
System Action: The system ignores the reply just
entered and waits for the reply to be respecified.
Operator Response: Reenter the reply correctly.
Ensure that it is not longer than 80 characters.
The resource initialization (RIM) data set name

under which processing was occurring.
modname
The name of the module that abended.
System Action: The system enters disabled wait state
X'040'.
wait state X'040'.
programmer response for the abend code in the
message text.
Problem Determination: See the problem
determination information for the abend code in the
message text.
For additional problem determination information, see
wait state X'040'.
568
Detecting Module: IEAVNWTO

IEA306I
dev,chp,I/O ERROR,cm, stat,[sens],[ser]

issued an I/O request to a device on a channel path.
The I/O request included a command that resulted in an
unsuccessful I/O completion.
dev
The device number
chp
The channel path identifier
cm The I/O command that resulted in an unsuccessful

I/O completion
stat
The channel status word (CSW) status bytes
sens
The first two bytes of sense data
The sense data appears only for errors involving a

unit check status.
an I/O error also occurred while trying to read

the resulting sense data.
ser The volume serial number of a direct access

storage device (DASD) involved
The volume serial number appears only for DASD.
System Action: If the I/O request is critical to the
system initialization process, the system issues
message IEA304W and enters a disabled wait state.
Otherwise, processing continues.
If the device is a console, the system also issues
message IEA193I, which indicates the CONSOLxx
member that defines the console where the error
occurred.
Operator Response: This is probably a hardware
error. If the system issues message IEA304W, see the
operator response for that message and the associated
wait state.
If the system does not issue message IEA304A, restart
the system and then contact hardware support. Provide
the message text.
Note: If this situation occurs, no second line of

message IEA307I is displayed.
NO SENSE DATA
This text appears for non-unit check errors.
Since the error was not a unit check, then no
sense data exists.
Note: If this situation occurs, no second line of
message IEA307I is displayed.
Operator Response: Notify the system programmer of
the I/O error that occurred while the system was reading
the volume label for the specified device.
System Programmer Response: Contact hardware
support.
Detecting Module: IOSVVOLV
Source: Nucleus initialization program (NIP)

IEA307I
dev,chp, I/O ERROR READING VOLUME

LABEL, cmd,stat,text. [sense-data]
Explanation: A program issued a request to read a

volume label on a device. The I/O request included a
command that caused an unsuccessful I/O completion.
IEA308I
MAXIMUM NUMBER OF PARMLIBS

EXCEEDED
Explanation: More than 10 PARMLIB statements were

specified in LOADxx.
System Programmer Response: Ensure that a

maximum of 10 PARMLIB statements are specified in
LOADxx.
dev

The device number.
Detecting Module: IPXI50PS
The channel path identifier (CHPID)
IEA309I
The I/O command that caused the error.
Explanation: A data set in the PARMLIB

concatenation is ignored because more than 10 (the
maximum allowed) data sets have been specified.
chp
cmd
stat
The subchannel status word (SCSW) status bytes.
PARMLIB DATA SET IGNORED: dsname

volser
text
A variable length text string that is one of the
following:
dsname
SENSE FOLLOWS
This text appears for unit check errors in which
the resulting sense data could be successfully
read. If this text is displayed, the sense data is
also displayed.
volser
sense-data
Shows up to 32 bytes of the resulting
sense data in the second line.
INVALID SENSE DATA
This text appears for unit check errors in which
The name of the data set that will not be used.

The volume where dsname resides.

System Programmer Response: Ensure that a
maximum of 10 PARMLIB statements are specified in
LOADxx.
Detecting Module: IPXI50PS
569
IEA310A
INVALID REPLY
|
|
|
Explanation: During nucleus initialization, the last

reply to message IEA120A, IEA213A, or IEA214A did
not contain the required information.
|
|
|
System Action: The system ignores the reply. The

system issues message IEA120A, IEA213A, or
IEA214A again.
Operator Response: Enter the reply correctly.

Operator Response: If the device is not the device
you wanted to dismount, do the following:
v ReIPL the system with the correct device in ready
status.
v If the device is not required during system
initialization, enter a VARY command to establish the
volume status at the end of system initialization.

Detecting Module: IEAVNPM3, IEAVNP02,
IEAVNP03, ILRASRIM
IEA311I
UNLABELED DASD ON dev. UNIT PUT

OFFLINE.
Explanation: The direct access storage device

(DASD) mounted on a device is not formatted correctly.
dev
The device number.
CONFLICTING VOLUME ON dev
IEA314I

found a device with an incorrect device type while
attempting to mount a volume. In the message text:
dev
The device number.
System Action: One of the following:
1. If the volume on the device is not permanently
resident, the system marks the device not ready.
The system issues message IEA315A.
2. If the volume on the device is permanently resident,

but the volume to be mounted is for an optional data
set, the system issues message IEA317A.

volume mounted on the device was properly initialized
by the ICKDSF program.
3. If the volume to be mounted is for a required data

set, and the volume on the device is permanently
resident, the system enters wait state X'039'.

message IEA315A, IEA317A, or wait state code X'039'.
System Action: The system marks the device offline.
Detecting Module: IOSVVOLV

IEA312I
dev OFFLINE
Explanation: Because a direct access storage device

(DASD) was formatted incorrectly, the system placed
the device offline. In the message text:
dev
The device number.
Source: DFSMSdfp
IEA315A
M devname,[NL], dsname

required one of the following:
v An unlabeled tape for a SYS1.DUMPnn data set

without the device.
v The volume containing a data set to be mounted on a

device

system properly initialized the volume mounted on the
device.
devname
The name of the device on which the volume
should be mounted.
Source: DFSMSdfp
dsname
IEA313I
DEVICE dev DISMOUNTED
The name of the data set in the volume to be

mounted.
Explanation: During nucleus initialization, the system

dismounted a device in response to message IEA212A.
System Action: The system waits for a volume to be

mounted on the specified device.
Operator Response: Mount one of the following:
dev
v The direct access volume containing the specified

data set
The device number.
570
v An unlabeled scratch tape

Source: DFSMSdfp
IEA316A
D dev[,ser]

found that a volume was mounted on a device other
than the device requested.
If the device is a tape unit, the volume is write-protected
or contains a standard IBM tape label.
dev
The device number.
ser
The serial number of the volume that was

mounted incorrectly.
4. In logically partitioned (LPAR) mode, use the IOPD

frame option A5 and the device number to
determine if the device is supported and in which
logical partition.
5. Check if the control unit is powered and enabled to
the interface. If the control unit interface path is
switched through a 3814, check the switching unit
settings.
6. For 3380 device level selection (DLS) or device
level selection extended (DLSE) devices, check if
the device enable/disable switch is in the ENABLE
position.
7. If you replied to message IOS120A with the CONT
command, reIPL the system.
8. Verify that the devices defined in the IODF are
online.
Source: DFSMSdfp

IEA315A.
IEA318I
v Demount the specified volume.
UNIT UNACCEPTABLE
v Ensure that the proper volume is mounted on the

specified device.

found that the unit specified in the reply to message
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

to be mounted
Source: DFSMSdfp
v A volume that could not be demounted
System Action: The system rejects the unit

specification. The system issues message IEA317A
again.
IEA317A
SPECIFY UNIT FOR dataset ON volser

[OR CANCEL]

could not find a data set on a mounted volume. In the
message text:
dataset The name of the data set that the nucleus

initialization program (NIP) could not find.
volser
The serial number of the volume where the

data set should reside.

message IEA317A, specifying an alternate unit. Ensure
that the alternate unit:
v Is the proper device type for the volume to be
mounted
v Does not contain a required system data set
v Is demountable
Source: DFSMSdfp
[OR CANCEL]
The operator may cancel a request to mount
the volume.
IEA319I

reply. If the operator replies R 00,xxx, the system may
issue messages IEA318I and IEA317A.

could not find a data set on a volume. In the message
text:
dsname
1. Enter the command REPLY 00,dev.

2. Find the channel path identifier (CHPID) defined for
the device using the I/O problem determination
(IOPD) frame option A5.
3. Check the CHPID availability for the current physical
partition using the channel configuration (CHNCFA)
frame.
dsname NOT FOUND ON volser
The data set name.
volser
System Action: If the data set is logrec,

SYS1.SVCLIB, SYS1.PARMLIB, or SYS1.LINKLIB, the
system enters a disabled wait state. Otherwise, the
Operator Response: Remove the incorrect volume
571
and mount the correct one. If the action does not

correct the problem, notify the system programmer.
v List the table of contents of the volume that should
contain the data set.
IEA323I
OPI INVALID IN mem

found an incorrect OPI parameter in a IEASYSxx
parmlib member. The OPI parameter must be specified
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
Source: DFSMSdfp
IEA321I
INVALID PARAMETER SYNTAX - prm text

INVALID OPI KEYWORD
IMPROPER DELIMITER
UNBALANCED PARENS
INVALID CONTINUATION
UNDEFINED KEYWORD
The specified parameter is not valid.
The IEASYSxx parmlib member containing an

incorrect OPI parameter
System Action: The system ends the input from the

member and issues message IEA324I. The system
issues message IEA336A to prompt the operator to
respecify the SYSP parameter.
Operator Response: Respond to message IEA336A
by specifying the SYSP parameter again or canceling
the use of it for this IPL. Parameters interpreted up to
the point of the error remain in effect.
IEASYSxx parmlib member correctly specifies the SYSP
parameter. Ensure that the SYSP list of system
parameters is specified correctly.
prm
INVALID OPI KEYWORD
The OPI parameter is specified incorrectly in the
IEASYSxx parmlib member. It must be either
OPI=YES or OPI=NO.
IMPROPER DELIMITER
The parameter is followed by an incorrect delimiter.
Parameters must be separated by a comma or a
blank.
UNBALANCED PARENS
The parameter included a different number of right
and left parentheses.
The parameter continued across more than two
successive lines of text.
UNDEFINED KEYWORD
The parameter is not valid for message IEA101A
under operating system/virtual storage 2 (OS/VS2).
a reply by issuing message IEA336A, IEA324I,
IEA332A, or IEA906A.
Source: Virtual storage management (VSM)
IEA324I
SYSP INPUT TERMINATED IN mem
Explanation: During system initialization, the nucleus

initialization program (NIP) ended input from an
IEASYSxx parmlib member because of an error.
mem
The IEASYSxx parmlib member
System Action: NIP issues a message before

message IEA324I to explain the error. After message
IEA324I, the system then issues message IEA336A to
prompt the operator to respecify the parameter input
that was truncated. Parameters specified before the
error remain in effect.
See the operator response for the message preceding
IEA324I.
programmer response for the message preceding
IEA324I.
IEA325I
IEASYSxx PARAMETER LIST
Explanation: During system initialization, the operator

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.
572
xx
The identifier for the IEASYS parmlib member.
System Action: The system lists the parameters and

LOCATE FAILED FOR dsname
IEA326I

Obtain a stand-alone dump.
following:
v Reduce the total number of extents in the data sets
in the parmlib member.
v Reduce the number of data sets specified for
inclusion in the LNKLST.
Explanation: dsname is one of the following:

SYS1.DUMP
SYS1.CSSLIB
SYS1.LINKLIB
SYS1.LPALIB
SYS1.DSSVM
SYS1.MIGLIB
To reopen the LNKLST concatenation, have the

operator reIPL the system.
During system initialization, the nucleus initialization

program (NIP) could not find a data set in the system
catalog.
If the problem recurs, search problem reporting data

the IBM Support Center. Provide the stand-alone dump.
System Action: If the data set is SYS1.LINKLIB or

SYS1.CSSLIB, the system enters wait state X'00A'. For
other data sets, the system provides additional
diagnostic information in message IEA208I, IEA351I,
IEA354I, or IEA355A.
Do not try to reduce the number of extents by

compression while the data sets are opened as part of
LNKLST. Data sets must not be compressed while they
are in the LNKLST concatenation.
Detecting Module: IEAVNPE5, CSVLLCRE

IEA329I
RETRYABLE ERROR. RECENT

COMMANDS MAY NEED TO BE
REPEATED

programmer response for accompanying messages or
for wait state X'00A' if the missing data set name is
SYS1.LINKLIB or SYS1.CSSLIB.
Explanation: The current command to be processed

is not valid. The system recovered from a previous
abend.

command and all subsequent commands in the queue.
Detecting Module: IEAVNPC5, IEAVNPE5

IEA328E
LNKLSTxx INPUT TRUNCATED AT

dsname
Explanation: Too many data set names were specified

for inclusion in the LNKLST concatenation.
xx
The identifier for the LNKLST or PROG parmlib

member that defined the LNKLST
concatenation.
Operator Response: You may have to retry one or

more of the following commands:
v CONTROL C,A
v CONTROL C,E
v CONTROL C,I
v CONTROL M
If the problem persists, contact the system programmer.
dsname
The name of the last data set in the parmlib
member

CONTINUE prm PARM
System Action: The system did one of the following:
IEA330A
v Accumulated data set names for the LNKLST until its

work area filled up.
Explanation: This message permits the operator to

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
the DEB were filled up in processing data set
dsname. The system ignores the data set names
after dsname.
prm
The parameter name.
System Action: The system prompts for the operator

for a reply.
573
Operator Response: Continue entering information

related to the parameter.
IEA334A

IEA331I
LINK LIBRARY CONCATENATION

SYS1.LINKLIB dsname dsname ...
Explanation: The message lists the data sets that the

system concatenated to SYS1.LINKLIB. The system
issues this message if the list (L) keyword is specified in
the LNK system parameter.

read at least one record from a parmlib member. The
member has a physical record length (block size) that is
not a multiple of 80. The logical record length (LRECL)
for parmlib members must be 80. The physical record
length must be a multiple of LRECL.
dsname
The data set containing the member
mem
dsname
The data set name of a data set concatenated
to the SYS1.LINKLIB data set.
IEA332A
SPECIFY prm

found that a function defined by a parameter in an
IEASYSxx parmlib member was omitted.
prm
The parameter name of a required or optional

function. If OR CANCEL appears in the
message text, the function is optional.
System Action: To allow you to respond, the system

issues message IEA101A, then waits for your response.
If the function is required, reply to message IEA101A as
follows:
If, for example, prm is CON:
R 0,CON=xx
R 0,CON=(xx)
R 0,CON=(xx,L)
If, for example, prm is LOGREC:
R 0,LOGREC=dsname
If the function is optional (OR CANCEL appears in the
message text), press the ENTER key on the console to
bypass the parameter and continue system initialization
without the optional function.
programmer response for message IEA101A.
dsname(mem) HAS AN INVALID

RECORD LENGTH - SPECIFY EOB TO
CONTINUE
The member that has the incorrect physical

record length
System Action: Initialization processing waits for your

response.
To continue the IPL, specify EOB (press ENTER). This
action requests processing of member mem, even
though it has an incorrect record length.
physical record length of records in mem is a multiple of
80.
IEA335I
dsname MODULE mod IN mem LIST IS

text

NOT EXECUTABLE
ALIAS OF ALIAS
NOT AUTHORIZED
LIST IS A DUPLICATE
The system could not process a module a for data set
in a parmlib member.
dsname
NOT EXECUTABLE
The system cannot process module mod.
ALIAS OF ALIAS
The directory entry for the module name mod
specifies that it is an alias. However, the
module name that it is an alias of is also an
alias. This is not valid.
NOT AUTHORIZED
Module name mod is not in a library listed in
the authorized program facility (APF) list.
574
LIST IS A DUPLICATE
Module mod duplicates a module name that
already appears in member mem.
mod
mem
The name of the module. If the member is

specified as IOSDLPAL, then the module is a
device support module that should reside in
SYS1.LINKLIB.
The parmlib member that names module mod.
System Action: The system ignores the module name

mod and continues processing. If ALIAS OF ALIAS
appears in the message text, the system has loaded the
module with the original alias, but the module cannot be
accessed using the incorrect alias name.
an installation error. Ensure that the module with the
incorrect alias is link edited properly.
IEA338A
Explanation: One of the system parameters specified

during system initialization was incorrect.
prm
RESPECIFY PARAMETERS OR PRESS

ENTER TO CANCEL
Explanation: During nucleus initialization, one of the

following contained an incorrect parameter:
v The operator response to message IEA101A
v The system parameters defined in an active
IEASYSxx parmlib member
System Action: The system accepts all parameters
specified before the parameter in error. The system
prompts the operator to respecify the incorrect
parameter or cancel the use of the parameter for this
IPL.
This message may be preceded by explanatory
messages IEA301I and IEA324I.
The incorrect parameter

parameter and prompts the operator for a reply.
Operator Response: Respecify the parameter or
press ENTER to cancel the use of the parameter for
this IPL.
IEA339A

IEA336A
INVALID prm PARM - RESPECIFY parm

OR PRESS ENTER TO CANCEL
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
(LRECL) of a parmlib data set must be 80, and the
block size must be a multiple of LRECL.
System Action: Initialization processing waits for your
response.
this message. To continue the IPL, press ENTER. This
action requests processing of the concatenated parmlib
data set with the incorrect block size
LRECL of the data sets in the concatenated parmlib is
80 and that the block size is a multiple of 80.

v Enter a reply specifying only the corrected parameter
and subsequent parameters.
IEA340I
v Cancel further input by pressing ENTER. In this case,

the parameters accepted by the system remain in
effect.

could not obtain storage for the function indicated.
Any parameter may be respecified in this response.

System Programmer Response: If the parameters
were correct or if the problem persists, and a search of
the problem reporting data bases shows no fix, contact
REAL OR VIRTUAL STORAGE NOT

AVAILABLE FOR func
func
The function is one of the following:

v BLDL/BLDLF
v FIX
v IOSDLPAL
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'.
575
Functions and system actions are as follows:

func
System Action
PFT
Wait state X'038'
LPA Device
Wait state X'03A'
Support
Modules
IEA343D
NUCLEUS OVERLAPS PLPA, RE-IPL

OR REPLY GO FOR COLD START
Explanation: The nucleus overlaps into the previous

system queue area/extended system queue area
(SQA/ESQA) area. This causes an overlap into the area
required by pageable link pack area (PLPA) or extended
PLPA (EPLPA). This might have been caused by one of
the following:
v The size of the nucleus increased.
BLDL/BLDLF
Respecification offered by prompt message
MLPA
The system issues message IEA353I
FIX
The system issues message IEA353I
Note: PFT is not a system parameter.

Operator Response: Report this message to the
system programmer.
Application Programmer Response: If message
IEA956I or message IEA968I was issued previously,
probable hardware error. Central storage might have a
defective frame located at a fairly low address If
message IEA956I or message IEA968I was not issued
previously, this is probably an installation error. Make
sure that sufficient storage is available for NIP
processing. Reduce the number or the size of your
optional system facilities, such as the fixed link pack
area (FLPA) or the fixed BLDL list.
v The amount of central storage increased; this

increase results in an increase in the size of the
nucleus.
PLPA and EPLPA must be in the same virtual storage
location as the previous IPL for warm starts to proceed.
Therefore, the quick or warm start cannot proceed. The
operator must reIPL or allow the IPL to change to a cold
start.
System Action: This message requests a response
from the operator. If the operator replies GO, the system
issues message IEA929I (CLPA FORCED), changes the
IPL to a cold start, and continues paging initialization.
Otherwise, the operator must reIPL.
Operator Response: Determine if the correct nucleus
was specified at IPL. If not, specify the correct nucleus
and reIPL. If the correct nucleus was specified at IPL,
notify the system programmer.
cannot be resolved, search problem reporting data

IEA345A
IEA341A
RESPECIFY prm PARM OR PRESS

ENTER
Explanation: A system parameter specified during

initialization was incorrect. Previous messages might
diagnose the specific error in the parameter
specification.
prm
The incorrect system parameter.

a reply.
Operator Response: Enter the parameter correctly or
press ENTER. If you press ENTER, any system defaults
for the parameter are used.
If prm is DUMP, ensure that TA was not specified in
the SYS1.PARMLIB dump command.
576
dsname NOT USED (text) - PRESS

ENTER TO CONTINUE
Explanation: The system cannot use the specified

parmlib data set.
dsname
The data set name.
text
A variable length text string that is one of the
following:
OPEN FAILED
The system cannot open data set dsname.
volser NOT FOUND

The system cannot locate or cannot mount
volume volser.
NOT CATALOGED
The LOADxx parmlib statement for data set
dsname was not cataloged in the master
catalog.
System Action: IPL processing waits for the operator

to press ENTER.
System Action: The system prints the list and


To continue the IPL without data set dsname, press
ENTER.
System Programmer Response: Depends on text:

OPEN FAILED
Ensure that dsname either resides on the volume
specified on the LOADxx parmlib statement or is
cataloged in the master catalog. IPL the system
again to use the data set.
volser NOT FOUND

Ensure that the volume exists and it is mounted.
IPL the system again to use the data set.
NOT CATALOGED
Ensure that the data set dsname is cataloged on
the master catalog or specify a volume for it on the
LOADxx parmlib statement. IPL the system again to
use the data set.
Detecting Module: IEAVNPOP
IEA347A
SPECIFY MASTER CATALOG

PARAMETER
Detecting Module: IEAVNP05, IEAVNPC5

IEA351I
dsname REQUIRED FOR mem

cannot find the data set dsname. The data set is
required for member mem in the parmlib.
dsname
mem

Operator Response: This is probably an installation
error. Report the problem to the system programmer
and reply in the format specified for message IEA101A
as requested by the system programmer, or cancel the
job.

issues this message asking the operator to specify
whether the normal master catalog or an alternate
master catalog is to be used by the system.

reply. The system generates the name of the
SYS1.NUCLEUS parmlib member that will be used to
find the master catalog.
IEA352I
INCORRECT LIBNAME FORMAT

EXCEED MAX BLDL ENTRIES
INCORRECT VOLID FIELD
EXCEED APF TABLE STORAGE
MODNAME mod FOR dsname
INCORRECT LIBNAME FORMAT FOR dsname
MODULE LIST NOT CLOSED FOR dsname
INVALID KEYWORD FOUND
INVALID DELIMITER
MIXED SYNTAX ENCOUNTERED
v Reply nn: To select the alternate master catalog,

SYSCATLGnn. nn is the two character suffix of
SYSCATLG. Member SYSCATLGnn will now be used
to find the master catalog in SYS1.NUCLEUS.
v Press enter: To use the default member of
SYS1.NUCLEUS, SYSCATLG to find the master
catalog.
Source: DFSMSdfp
IEA350I
mem MODULE LIST
Explanation: This is a header message for the library

listing requested by the operator. The modules specified
in the parmlib member are printed following this
message.
mem
The specified parmlib member name.

LIST mem FOR prm INVALID text
MODNAME mod
The parmlib member specified for a parameter is

incorrect.
mem
The name of the parmlib member.
prm
The parameter.
MODNAME mod
mod identifies the name of the incorrect module
specified.
577
INCORRECT LIBNAME FORMAT

The parmlib list did not properly define a module
source library.
EXCEED MAX BLDL ENTRIES
The parmlib list contained too many module names;
BLDL has more than X'7FFF' names.
INCORRECT VOLID FIELD
The parmlib list contained volids that were
specified in the wrong format, or possibly not
specified at all.
EXCEED APF TABLE STORAGE
The parmlib list IEAAPFxx contains entries with a
character count exceeding the maximum storage
allocated for the authorized program facility (APF)
table.
MODNAME mod FOR dsname
The parmlib member specified an incorrect module
name, mod for data set dsname.
INCORRECT LIBNAME FORMAT FOR dsname
The parmlib member specified an incorrect module
source library for data set dsname.
MODULE LIST NOT CLOSED FOR dsname
The parmlib member is missing the module list
closing delimiter for data set dsname.
INVALID KEYWORD FOUND
The parmlib member contains an invalid keyword.
INVALID DELIMITER
The parmlib member contains an incorrect keyword
delimiter.
MIXED SYNTAX ENCOUNTERED
The parmlib member specified libraries with
keyword and non-keyword syntaxes.
System Action: For the texts INCORRECT LIBNAME
FORMAT, INCORRECT VOLID FIELD, and EXCEED
APF TABLE STORAGE, the system continues. For all
others, the system prompts the operator to respecify the
parameter or cancel.
error. Respond to the prompt message and report this
message to the system programmer.
reporting databases for a fix for the problem. If no fix
Detecting Module: IEAVNPA5, IEAVNPC5, IEAVNP05
IEA353I
prm INPUT TERMINATED AT mod
Explanation: The definition of the parameter failed for

lack of storage as indicated by the preceding message.
578
prm
The specified parameter. If prm is CLPA, a link

pack area (LPA) cold start has failed.
mod
The module that was to be loaded when the

error was detected.
System Action: If this initial program load (IPL) was

not a cold start, the system continues processing.
Modules specified before mod are added to the LPA. If
prm is CLPA, the system is placed in wait state X'03A'.
error. Report this message to the system programmer.
System Programmer Response: Ensure that there is
adequate storage for the prm function being attempted.
Respond as indicated for the wait state code if it occurs.
Center.
IEA354I
[CLPA|MLPA|BLDL|IOSDLPAL] FAILED
- text
Explanation: The system link pack area (LPA) or the

pageable build directory entry list (BLDL) table could not
be created. text indicates the reason:
LPALIB UNAVAILABLE
The SYS1.LPALIB data set is not defined in the
catalog or the data set could not be opened. The
reason for the failure is given in the previous
message.
LPALIB EMPTY
The SYS1.LPALIB data set did not contain any load
modules.
STORAGE UNAVAILABLE
Virtual storage is too small to contain all the
modules in SYS1.LPALIB. The number of modules
in SYS1.LPALIB must be reduced if cold start is to
be successful.
I/O ERROR
An I/O error occurred when the nucleus initialization
program (NIP) attempted to read a record from the
SYS1.LPALIB directory.
PGOUT ERROR
An error occurred during the processing of the
PGSER macro. The PGSER macro tried to page
out the modified link pack area (MLPA) area,
pageable link pack area (PLPA) area, or the
pageable BLDL list.
NON-EXECUTABLE MODS
Non-processible modules were found on
SYS1.LPALIB.
wait state X'03A'. If any modules were successfully

loaded into the LPA, the system issues message
IEA353I.
error. Notify the system programmer.
IEA355A
RESPECIFY prm [OR CANCEL]

detected an error a parameter.
prm
The parameter name.
OR CANCEL
CANCEL is a reply option.
IEA101A.
Operator Response: Contact the system programmer,
then reply in the format specified by message IEA101A.
If CANCEL is a reply option, you may press the enter
button on the console to bypass the parameter.
programmer response for message IEA101A.
IEA356I
ALIAS name OF MODULE mod

IGNORED
Explanation: During the initial program load (IPL) of

the link pack area (LPA), the entry for aliasname in a
library directory (the library is SYS1.LPALIB,
SYS1.LINKLIB, or SYS1.SVCLIB) specifies that it is the
alias of the specified module. However, mod is not in
that library directory or is itself an alias. A message
accompanying message IEA356I names which library.
name
The specified alias name.
mod
The specified module.
System Action: If a cold start is in progress and the

system is creating the pageable link pack area (PLPA)
this message follows message IEA301I. If the system is
loading the modified link pack area (MLPA) or the fixed
link pack area (FLPA) this message follows message
IEA335I. The system ignores the entry for aliasname
during the IPL of the LPA. The system may have loaded
module mod into the LPA, but mod cannot be accessed

by the alias aliasname.
IEA357I
ERRORS IN IEAPAKxx LIST
text - sysact
v MODULE mod HAS INVALID RMODE
v DELIMITER FOLLOWING mod INVALID
v NAME FOLLOWING mod IMPROPER
v I/O ERROR FOLLOWING mod
sysact is one of the following:

v MODULE IGNORED
v SKIPPING TO NEXT GROUP
v LIST TERMINATED
During initial program load (IPL), the system detected
one or more errors while processing the link pack area
(LPA) packing list member, IEAPAKxx, of the parmlib.
MODULE mod HAS INVALID RMODE
The system found that the residence mode
(RMODE) for module mod is different from the
RMODE for the group containing the module. The
RMODE for a group is the RMODE of the first
module in the group.
DELIMITER FOLLOWING mod INVALID
The left parenthesis before a group of module
names is missing, or the right parenthesis after a
group is missing, or a blank is not preceded by a
left parenthesis or comma. mod is the last valid
module name before the error. mod is ***START if
no valid module names preceded the error.
NAME FOLLOWING mod IMPROPER
A module name in the list has more than eight
characters. mod is the last valid module name
before the error. mod is ***START if no valid
module names preceded the error.
mod INVALID
Module mod is not in the directory of SYS1.LPALIB,
is the name of an alias (not a module), or is
specified more than once in the LPA packing list.
I/O ERROR FOLLOWING mod
An I/O error occurred while the system was reading
the list. mod is the last valid module name before
the I/O error. if no valid module names preceded
the error.
sysact
sysact is one of the following:
579
MODULE IGNORED
Module mod is ignored. The system continues
processing the list.
SKIPPING TO NEXT GROUP
The system scans the list from the error to the
next right parenthesis, which ends the group.
The modules in the group before the error are
processed as the only modules in the group.
Processing then continues with the start of the
next group.
LIST TERMINATED
The modules in the group before the error are
processed as the only modules in the group.
The system then ends processing of the LPA
packing list and continues processing as
though it had reached the end of the LPA
packing list normally.
System Action: See sysact in the description above
for the system action.
IEA358A
LPALIB MODULE mod IS

NON-EXECUTABLE. PRESS ENTER TO
CONTINUE, OR RE-IPL THE SYSTEM
Explanation: Module mod on SYS1.LPALIB (or a

library specified in the LPALSTxx parmlib member) is
marked non-executable and cannot be loaded into the
system link pack area (LPA).
mod

a reply. If the reply is ENTER, the system continues
processing. The system does not place the
non-executable module into the LPA.
system programmer. Either press ENTER to have the
IPL continue or reIPL after the system programmer has
fixed the error. Note that pressing ENTER to continue
the IPL means that the specified module will not be
placed into the LPA.
System Programmer Response: Replace the
non-executable module with processible versions.
IEA359E
BUFFER SHORTAGE FOR RETAINED

ACTION MESSAGES - 80% FULL
Explanation: The action message retention facility

(AMRF) is active, and 80% of the buffer area for the
following messages is full:
580
v Immediate action messages (with descriptor codes 1

and 2)
v Non-critical eventual action messages (with descriptor
code 3)
v Critical eventual action messages (with descriptor
code 11)
v Write to operator with reply messages (WTORs)
System Action: The system continues to retain
immediate action and eventual action messages.
Operator Response: Enter the DISPLAY R command
to display information about all outstanding immediate
action and eventual action messages. Delete messages
by:
v Responding to messages requesting an action.
v Entering the CONTROL C command. See the
OS/390 MVS System Commands book for the syntax
of the CONTROL C command.
Note: When enough messages are deleted so that the
buffer area is less than 75% full, the system
issues message IEA361I and deletes message
IEA359E.
IEA360A
SEVERE BUFFER SHORTAGE FOR

RETAINED ACTION MESSAGES - 100%
FULL

(AMRF) is active, and the buffer area for the following
messages is full:
and 2)
code 3)
code 11)
v Write to operator with reply messages (WTORs)
System Action: The system no longer retains
non-critical eventual action messages. The system
issues message IEA360A if console message buffers
(WQEs) begin to back up.
When the WQE buffer shortage is no longer critical, the
system deletes message IEA405E and IEA404A and
issues message IEA361I. The system retains new
immediate action and critical eventual action messages
and keeps them in the common service area (CSA).
Operator Response: Enter the DISPLAY R command
to display the details of all outstanding immediate action
and eventual action messages. Delete messages by:
v Responding to messages requesting an action
v Entering the CONTROL C command. See the
OS/390 MVS System Commands book for the syntax
of the CONTROL C command.
If a shortage still exists, you might want to deactivate

the AMRF by entering the CONTROL M,AMRF=N
command.

could not find the module in the link pack area (LPA).
mod
IEA361I
BUFFER SHORTAGE RELIEVED FOR

RETAINED ACTION MESSAGES
Explanation: The number of retained action messages

was reduced so that the buffer is now less than 75%
full. This message is preceded by message IEA359E or
both IEA359E and IEA360A, which indicated the extent
of the buffer shortage.
The system deletes messages IEA359E and IEA360A.
IEA362E
BUFFER EXTENSION FAILED FOR

RETAINED ACTION MESSAGES
mod NOT FOUND IN LPA
IEA363I
System Action: Except during special NIP processing,

the system indicates which function was made
inoperative by issuing message IEA208I, and then it
continues processing. If the system cannot continue
processing without the module, the system enters wait
state X'03B'.
error. Notify the system programmer.
missing routine is in the LPA. If necessary, add the
module to the SYS1.LPALIB and have the operator run
a cold start.
The module must be defined in the parmlib list
referenced by the modified link pack area (MLPA) or
FIX option, if either of these options is used.

(AMRF) is active, the system could not obtain additional
buffers, and the buffer area for the following messages
is full:


and 2)

code 3)
Detecting Module: IEAVNPS5, IEAVNP05, IEAVNP07

code 11)
IEA364E
System Action: The system retains any new

immediate action messages and critical eventual action
messages in the common service area (CSA). The
system no longer retains non-critical eventual action
messages.
The system issues messages IEA405E and IEA404A if
console message buffers (WQE) start to back up. The
system deletes message IEA362E if the buffer shortage
is relieved.
Operator Response: Enter a DISPLAY R command to
display the details of all outstanding immediate action
and eventual action messages. If a shortage still exists,
you may want to deactivate the AMRF by entering the
CONTROL M,AMRF=N command. If the problem
persists, contact the system programmer.
System Programmer Response: Check for a
shortage of storage in the master scheduler address
space.
{AMRF [RESTART]|MPF} FAILED,

INACTIVE {RETAINED MESSAGES
DELETED|MPF TABLE DELETED}.
Explanation: One of the following appears in the

message text:
AMRF FAILED, INACTIVE - RETAINED MESSAGES
DELETED
The action message retention facility (AMRF) failed
because of a system error.
MPF FAILED, INACTIVE - MPF TABLE DELETED
The message processing facility (MPF) failed
because of a system error. The error occurred in
the MPF table scan routine.
System Action: Depending on the message text, one
of the following:
AMRF FAILED, INACTIVE - RETAINED MESSAGES
DELETED
The system no longer retains action messages if
the facility was active before the failure occurred.
Messages that were retained previously are no
longer available.
MPF FAILED, INACTIVE - MPF TABLE DELETED
The system deletes the message table. The MPF is
inactive.
581
Operator Response: If the AMRF failed and you want

to restart it, enter the CONTROL M,AMRF=Y command.
IEA367A
If the MPF failed and you want to reactivate it, enter the
SET MPF=xx command, where xx is the last two digits
of an MPFLSTxx parmlib member.
MULTIPLE CONSOLE SUPPORT

INOPERATIVE ERROR CODE = xxxx
REPLY WITH ANY CHARACTER TO
CONTINUE WITHOUT MULTIPLE
CONSOLE SUPPORT
If either problem recurs, contact the system

programmer.
Explanation: Because of an error, the communications

task (COMMTASK) failed.

xxxx

8001
The system could not establish a

recovery routine.
8002
The system could not attach a needed

routine.
8003
The error occurred during a POST.
8004
8005
The error occurred during an update

to the command address space table.
8006
The error occurred during an operator

request to activate an extended
multiple console support (MCS)
console class.
8007
This message follows message IEE481I, which

identifies the system abend code of the original error.
8008
The error occurred when the system

tried to issue a Supervisor Call (SVC).
System Action: The system continues other

processing.
Fccc
An error occurred; the system issued

abend code ccc.

IEA365E
COMMAND SCHEDULER RESTART

FAILED,
ABEND RECURSION
THE FOLLOWING
COMMANDS ARE INOPERATIVE:
D C D C,K D PFK D R REPLY
D OPDATA ROUTE TRACE MCS LOGON
MCS LOGOFF
Explanation: Command processing failed. The system

tried to restart it, but the restart also failed.
Operator Response: If necessary, reIPL the system to

return the system to full processing.

a reply.

programmer response for the abend identified in
message IEE481I.
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
console operator will be able to continue.

IEA366W

INOPERATIVE-WAIT STATE 201 - REIPL
Explanation: Because of a failure, multiple console

support (MCS) is not working.
System Action: System initialization stops. The
system writes an SVC dump and enters wait state
X'201'.
wait state X'201.'.
programmer response for wait state X'201.'.
v To continue processing with MCS, reIPL the system

with MCS.
System Programmer Response: If Fccc appears, see

the system programmer response for the abend code
ccc.
IEA368I
INVALID RECORD IN memname. FIRST

17 BYTES ARE xxxxxxxxxxxxxxxxx

found an incorrect record in the memname parmlib
member. The system cannot process the keyword.
memname
582
The parmlib member
containing an
incorrect record.
memname is one of
the following:
v LOADxx
v NUCLSTxx
xxxxxxxxxxxxxxxxx
The first seventeen

characters in the
incorrect record.

record and system initialization continues.
Provide the parmlib member name, memname, and the
incorrect record.
System Programmer Response: Correct the incorrect
record in parmlib member memname.
If the record is correct, search problem reporting data
IEA370I
MASTER CATALOG SELECTED IS

MASTER CATALOG name

system initialization to display the name of the catalog
selected as the master catalog. The master catalog is
from the SYSCATxx member of SYS1.NUCLEUS. The
operator specified the name of the catalog for use as
the master catalog in response to system message
IEA347A.
System Action: Processing continues
IEA371I
data-set ON DEVICE nnnn SELECTED

FOR IPL PARAMETERS

selected data set dataset containing the IPL
parameters.
data-set
The data set containing the IPL parameters.
The data set is one of the following:
v SYS1.PARMLIB
v SYSn.IPLPARM
nnnn
The device number where the IPL parameter

data set was located.
System Action: System initialization continues with

the IPL parameters found in data set data-set.
Source: System initialization (IPL)
IEA372I
module EXCLUDED FROM NUCLEUS
Explanation: An EXCLUDE statement in the

NUCLSTxx parmlib member specified that module
modname be excluded from the nucleus.
module The module excluded from the nucleus.

IEA376I
VIODSN PARAMETER IS IGNORE. NO

VIO JOURNALING
Explanation: The value of the VIODSN parameter in

the IEASYSxx parmlib member used for this IPL is
IGNORE or null, which means that no VIO journaling
will take place.
System Action: IPL continues. The system rejects
journaling requests for VIO data sets.
Operator Response: If VIO journaling is necessary,
re-IPL at direction of system programmer, specifying a
VIO journaling data set name for the VIODSN
parameter.
System Programmer Response: Ensure that VIO
journaling is not required. If it is needed, specify
VIODSN in IEASYSxx.
Source: Auxiliary Storage Manager (ASM)
IEA377D
REPLY VIO JOURNALING DATA SET

NAME OR IGNORE
Explanation: This message allows the operator to

respecify the VIO journaling data set name or indicate
that journaling of VIO data sets is not necessary.
reply. If the operator replies with a new data set name,
the system processes the data set.
If the operator replies IGNORE, or gives a null reply,
message IEA378I is displayed and the IPL continues.
The system rejects journaling requests for VIO data
sets.
Operator Response: Enter one of the following:
dsname
DSN=dsname
VIODSN=dsname
To specify a VIO journaling data set name.
IGNORE
null
To specify that VIO journaling is not necessary.
583
If VIO journaling is necessary, reIPL at the direction of

the system programmer, specifying the VIODSN
parameter.
VIODSN in IEASYSxx.
IEA378I
REPLY TO IEA377D IS IGNORE OR

NULL. NO VIO JOURNALING
Explanation: The reply to the message IEA377D

indicates that system initialization should continue
without VIO initialization.
v In the IEASYSxx parmlib member

v In the operator response to message IEA101A
value
The incorrect NSYSLX value, which is less

than 10 or greater than 512
number The default value for NSYSLX. This is currently

165.
System Action: Initialization continues with the default
NSYSLX value of 165.
Operator Response: In response to message
IEA101A, enter a new NSYSLX value specified by the
system programmer. If message IEA101A does not
appear, reIPL to enter a correct value.
System Action: The IPL continues. The system will

reject journaling requests for VIO data sets.
System Programmer Response: Respecify the

number of system linkage indexes by doing one of the
following:
Operator Response: If VIO journaling is necessary,

re-IPL at the direction of the system programmer.
v Ask the operator to enter a correct value in response

to message IEA101A.

VIODSN in IEASYSxx.
v Correct the value specified in the IEASYSxx member.

IEA379I
VIODSN=dsname,DATA SET NOT

CATALOGED - reg15
Explanation: The data set name specified in the

VIODSN parameter in IEASYSxx could not be located in
the system catalog.
The message text, reg15 is the value returned from
SVC 26 in Register 15.
System Action: Message IEA377D is issued. If the
operator replies with a new data set name, the system
processes the data set. If the operator replies IGNORE,
or gives a null reply, message IEA378I is displayed and
the IPL continues. The system will reject journaling
requests for VIO data sets.
Operator Response: Reply to message 377D with
VIO journaling data set name or IGNORE.
System Programmer Response: If VIO journaling is
required, supply the VIO journaling data set name in the
VIODSN parameter of IEASYSxx before the next IPL.
IEA400I
NSYSLX VALUE, value, NOT VALID,

DEFAULT OF number USED
Explanation: During system initialization, the number

of system linkage indexes, NSYSLX, was incorrectly
specified in one of two ways:
584

Detecting Module: IEAVNPO9
IEA401I
SDUMP NOT SCHEDULED FOR

REMOTE DUMP. INCIDENT
TOKEN:intoken REASON - reason
Explanation: The system was unable to write an SVC

dump for another system in a sysplex.
intoken The incident token for the dump. The token

contains the name of the sysplex, the name of
the system that originated the dump request,
and the date and time of the request.
reason One of the following:
DUMP=NO WAS SET AT IPL OR INDICATED
BY CHNGDUMP
The installation indicated that no SVC
dumps are to be written.
NO SRBS COULD BE SCHEDULED TO
START THE DUMP
A system error occurred.
SVC DUMP ABNORMALLY TERMINATED
A STATUS STOP SRBS CONDITION WAS
DETECTED
NO STORAGE AVAILABLE
The system could not acquire the storage
needed to build the dump request; no
dump was written.
UNKNOWN
System Action: The system continues processing but
does not write the requested SVC dump.
This message is sent to the console on which the
DUMP command was entered or, if the dump was
requested by another system in the sysplex but not by a
DUMP command, to console ID 0.
system could not write an SVC dump requested by
another system in the sysplex. If the problem cannot be
corrected, search problem reporting data bases for a fix
Center.
Source: SVC dump
Detecting Module: IEAVTSIT
IEA402A
REPLY ID PROCESSING ERROR. text
Explanation: Where text can be one of the following:

v XCF RETURN CODE xxxxxxxx, REASON CODE
yyyyyyyy
During WTOR or DOM processing, an unexpected
return code was received from XCF. The XCF return
and reason code are displayed in hexadecimal.
v ATTEMPT TO OBTAIN STORAGE FAILED
During WTOR or DOM processing, it was not
possible to obtain storage necessary to complete the
operation.
System Action: For WTOR processing, if possible, a
reply ID is assigned. For DOM processing, the reply ID
is released and processing continues.
Operator Response: Contact your systems
programmer.
exists, contact the IBM Support Center. If the problem is
due to unexpected return codes from XCF, supply the
XCF return and reason codes.
IEA403I
VALUE OF RMAX HAS BEEN

CHANGED TO 99
IEA404A
SEVERE WTO BUFFER SHORTAGE 100% FULL

messages is at the limit value specified in the MLIM
parameter of a CONSOLxx parmlib member.
System Action: The system puts non-privileged jobs
issuing messages in a wait state (if they did not specify
a busy exit return) until the number of WTOs is reduced
below the buffer limit.
Operator Response: Enter the DISPLAY CONSOLES
command. If the system has accumulated a large
number of WTO messages, do one or more of the
following:
v Enter the CONTROL Q command to reroute the
messages.
Enter the CONTROL E,D command if CONTROL
Q does not reroute the messages.
ATTENTION: Messages already queued to a
display area will not be deleted by a CONTROL
Q. Enter CONTROL E,D to erase these messages
if the CONTROL Q command does not relieve the
shortage.
v Enter the CONTROL S command to delete a
specified number of messages.
v Enter the CONTROL M,MLIM command to increase
the value of the WTOR buffer limit.
v Put the display console in roll mode to let a specified
number of messages roll off the screen at a specified
time interval.
v Respond to any messages requesting an operator
action.
system initialization, increase the value of MLIM in the
CONSOLxx parmlib member to increase the maximum
number of buffers that WTO messages can use.
IEA405E
WTO BUFFER SHORTAGE - 80% FULL

messages is 80% of the limit value specified in the
MLIM parameter of a CONSOLxx parmlib member.
System Action: Processing continues. Consoles that

are currently in HOLD mode and have messages
waiting are taken out of HOLD mode. The system will
no longer hold messages for other systems in the
sysplex. If another system is experiencing a WTO buffer
shortage, this system will resume sending messages to
the constrained system. The system issues a D C,B
command and a D EMCS,ST=B,L=Z command.
System Programmer Response: Review the value of

RMAX in CONSOLxx, and increase if necessary.
Operator Response: Enter the DISPLAY CONSOLES

command. If the console has accumulated a large
Explanation: The maximum number of systems which

could enter this sysplex is more than 8. The value of
RMAX was less than 99. The system has increased
RMAX to 99.
585
number of WTO messages, do one or more of the

following:
v Enter the CONTROL Q command to reroute the
messages.
v Enter the CONTROL S command to delete a
specified number of messages.
v Enter the CONTROL M,MLIM command to increase
the value of the WTO buffer limit.
v Put the display console in roll mode to let a specified
number of messages roll off the screen at a specified
time interval.
| IEA411I
|
|
|
|
|
SLIP TRAP ID=xxxx DISABLED FOR

{MATCHLIM | PRCNTLIM}
Explanation: If disabled for MACHLIM, then the SLIP

trap with ID of xxxx matched M times, where M is equal
to or greater than the matchlim value specified on the
trap. The trap is disabled.
| If disabled for PRCNTLIM, then the SLIP trap with ID of

| xxxx has consumed more than P percent of the CPU,
| where P is equal to or greater than the PRCNTLIM
| value specified on the trap. The trap is disabled.
v Respond to any messages requesting an operator

action.
System Action: The trap is disabled.

system initialization, increase the value of MLIM in the
CONSOLxx parmlib member to increase the maximum
number of buffers that WTO messages can use.
Source: SLIP
IEA412I

IEA406I
WTO BUFFER SHORTAGE RELIEVED
Explanation: The shortage of buffers for write to

operator (WTO) messages was relieved. The system
issued message IEA405E and/or IEA404A to indicate
the shortage.
SLIP TRAP ID=xxxx, x SDUMPS NOT

SCHEDULED. RETURN CODE=nn
REASON CODE=mm |
RETURN/REASON CODES NOT
AVAILABLE
Explanation: The event specified for a SLIP trap

occurred. The trap requested an SVC dump. When
SLIP processing requested one or more dumps for the
trap, one of the following occurred:
v The internal resources required to process the SVC

dumps are not available. The resources are currently
being used for another SVC dump. This situation may
occur if the SUMLIST or LIST parameter is specified
on the SLIP command. The return/reason codes may
not be available.
v Another dump is in progress.

The system resumes normal message processing.
IEA407I
If the message contains the text RETURN

CODE=nn REASON CODE=mm, then the dump
in progress is not related to the dump requested
by the slip trap.
DIRECTORY ENTRY FOR MODULE

mem INVALID IN SYS1.LPALIB

found an incorrect directory entry for a member of
SYS1.LPALIB while attempting to build the link pack
directory from SYS1.LPALIB.
However, if the message contains the text

RETURN/REASON CODES NOT AVAILABLE,
then this slip trap has matched multiple times in
quick succession. In this case, the first match
successfully scheduled the dump. Subsequent
matches tried unsuccessfully to schedule the
dump, producing IEA412I. IEA412I can be ignored
in this case.
mem
A member of SYS1.LPALIB

member. The system will resume holding messages for
the other system in the sysplex. If another system is
experiencing a WTO buffer shortage, this system will
hold its messages instead of sending them to the
constrained system.
cause of the incorrect directory entry, and link-edit the
member of SYS1.LPALIB again, if necessary.
586
Note that if the time between matches is

sufficiently small, a trap can match multiple times
even if matchlim is 1.
v The system is set to ignore requests for SVC dumps.
See OS/390 MVS Programming: Authorized Assembler
Services Reference LLA-SDU for details on the return
and reason codes.
xxxx
The ID of the matching trap.
The number of dumps that were not scheduled.
nn
The return code from the first failing SDUMP

invocation.
mm
The reason code from the first failing SDUMP

invocation.
For additional details on the return and reason codes,

see the SDUMP macro in OS/390 MVS Programming:
Authorized Assembler Services Reference LLA-SDU.
does not write the requested SVC dumps.
Source: SLIP
IEA413I
SLIP TRAP ID=xxxx DATA

UNAVAILABLE
Explanation: While checking for a match for a SLIP

trap, SLIP processing was unable to access the data
specified by the DATA parameter on the SLIP
command. The reason is either:
v The data is paged out.
v An indirect pointer to the data is paged out.
The status of the following resources that control PER is

unknown:
v PER control registers
v PER bit in the old program status words (PSW) for
each system
v PER bit in the PSWs that are stored in request
blocks (RB)
v PER bit in the new PSWs for SVC, external, and I/O
interruptions for each system
v PER bit in the address space control block (ASCB)
for each address space
Thus, PER interruptions might continue to occur. They
will not be processed by SLIP but can slow system
performance.
System Action: The system writes a logrec data set
error record. The system also does the following:
v For case 1, the system writes an SVC dump.
v For case 2, because of the state of the system, the
system does not write an SVC dump.
Operator Response: If the system programmer asks
for an SVC dump, set a SLIP trap.
ID=xxxx
1. Try to correct the status of the resources that control

PER by setting and then disabling a PER trap for an
address space that is not currently active in the
system.

command.
SLIP counts the number of times the data is unavailable
to determine how often this message is issued:
v For a program event recording (PER) trap, this
message is issued only the first time the data is
unavailable.
v For a non-PER trap, this message is issued each
time the data is unavailable.
System Action: The system continues SLIP
processing. The trap does not match.
Operator Response: Enter the DISPLAY SLIP=xxxx
command to display the current value of the unavailable
data counter.
Source: SLIP
IEA414I
SLIP UNABLE TO DEACTIVATE PER
Explanation: SLIP processing could not deactivate

program event recording (PER). The reason is either:
1. While trying to deactivate PER in the system, SLIP
encountered an error because of a previous error.
Message IEE743I precedes this message.
2. While trying to deactivate PER when a job step task
or address space was ending, SLIP encountered an
error.
2. If the status of the resources cannot be corrected,

monitor the performance of the system to be sure it
is operating within acceptable limits.
3. Search problem reporting data bases for a fix for the
IBM Support Center. Provide the SVC dump. If an
SVC dump is not produced with the abend, ask the
operator to set a SLIP to obtain an SVC dump.
Detecting Module: IEAVTGLB, IEAVTPVT
IEA415I
SLIP ERROR ATTEMPTING TO

ACTIVATE/DEACTIVATE PER, DUMP
SCHEDULED
Explanation: SLIP processing encountered an error

while attempting to activate or deactivate program event
recording (PER) in an address space. The
accompanying SVC dump identifies the address space.
The status of PER in the address space is unknown;
consequently:
v If the error occurred while SLIP processing was
attempting to set or enable a PER trap, the trap
might not be monitoring this address space.
v If the error occurred while SLIP processing was
attempting to disable or delete a PER trap, PER
587
interruptions might continue to occur in this address

space. They will not be processed by SLIP but can
slow system performance.
System Action: The system writes an SVC dump.
v Try to correct the status of PER in the address space
as follows:
If the error occurred while SLIP processing was
attempting to set or enable a PER trap, ask the
operator to enter SLIP MOD commands to disable
the same trap and then enable it.
If the error occurred while SLIP processing was
attempting to disable or delete a PER trap, ask
the operator to enter SLIP SET and SLIP MOD
commands to set and then disable a PER trap for
an address space that is not currently active in the
system.
v If the status of PER cannot be corrected, search
problem reporting data bases for a fix for the
IBM Support Center. Provide the SVC dump.
IEA422I
ABEND IN IEAVTJBN DURING

PROCESSING FOR SLIP
Explanation: SLIP processing encountered an error

while determining if program event recording (PER)
should be active for a particular address space. The
accompanying SVC dump identifies the address space.
The status of PER in the address space is unknown;
consequently:
v PER might not be active in the address space in
which it should be active.
v PER might be active in an address space in which it
should not be active. PER interruptions might
continue to occur in this address space. They will not
be processed by SLIP but can slow system
performance.
System Action: The system writes a logrec data set
error record and an SVC dump.
1. Enter the SLIP trap again, specifying either:
Source: SLIP
v ACTION=IGNORE ASID=NONE to ignore the

address space on the SLIP trap.
Detecting Module: IEAVTGLB
v ASID=asid to trap the address space.
IEA416W
SYSTEM TRACE INITIALIZATION

TERMINATED DUE TO AN ERROR.
Explanation: An error occurred during the creation of

the system trace address space or during the
initialization of the system trace function. The system
trace function returned a nonzero return code.
wait state X'023'.
Source: System Trace
IEA421E
START STOPPED PROCESSORS
Explanation: The system has recovered.

This message is not removed automatically from a
display console, and must be manually removed.
Operator Response: Restart the systems stopped
during the recovery processing. Remove this message
from the display console.
Detecting Module: IEAVNP51, IECVIRST, IECVFCHN
588
2. If the problem continues, search problem reporting

report the problem to the IBM Support Center.
Provide the SVC dump, the logrec data set error
records, and messages.
Source: SLIP
Detecting Module: IEAVTJBN
IEA423I
ERROR IN IEECB915
Explanation: An error occurred during SLIP

processing.
System Action: The system ends SLIP processing.
The system writes a logrec data set error record.
The system holds the messages generated by SLIP
processing until the command processing component
receives control; for example, when a SLIP trap is
deleted.
exists, report the problem to the IBM Support Center.
Provide the logrec data set error record and messages.
IEA424I
SLIP ERROR DURING PER

ACTIVATION/DEACTIVATION, MODEL
PSA NOT UPDATED
Explanation: SLIP processing was not able to page-fix

the model prefix save area (PSA). Therefore, SLIP
could not update:
v The PER bit in the external program status word
(PSW) in the model PSA
v The PER bit in the Supervisor Call (SVC) PSW in the
model PSA
v The PER bit in the I/O new PSW in the model PSA
If the system on which SLIP was running is varied
online, the PER bits associated with that system will be
incorrect.
System Action: The system issues messages about
the problem.
Explanation: An active SLIP trap specified program

event recording (PER) and an action of SYNCSVCD.
The PER interrupt occurred while the system was:
v Disabled
v Locked
v In service request block (SRB) mode
ACTION=SYNCSVCD can be performed only when the
system is:
v Enabled
v Unlocked
v In task mode
Rather than taking no diagnostic action, SLIP schedules
an SVC dump with ACTION=SVCD.
ID=xxxx
command.
Source: SLIP
Detecting Module: IEAVTGLB
IEA425I
SLIP ERROR DURING PER

ACTIVATION, CROSS MEMORY
SUPPORT IS INCOMPLETE
Explanation: SLIP processing was activating a

program event recording (PER) trap. Because the SLIP
command did not specify IGNORE, the trap was to be
active immediately. SLIP processing activated PER, but
cross memory support was incomplete. Therefore, SLIP
processing does not intercept any cross-memory-setinitiated address space changes.
The following occurs:
v If the SLIP trap was defined with the ASID parameter
but without the MODE=HOME parameter, important
data may not be trapped.
v In all other cases, the trap captures the desired
information, but SLIP processing may slow system
performance slightly.
System Action: The system schedules an SVC dump.

The interrupted unit of work regains control and the
Operator Response: Reset the SLIP trap, as
specified by the system programmer.
following:
v If the PER interrupt occurred for an incorrect event,
ask the operator to reset the trap and specify
additional filtering keywords.
v If the interrupt was supposed to occur while the
system was disabled, locked, or in SRB mode, ask
the operator to reset the trap and specify
ACTION=SVCD rather than ACTION=SYNCSVCD.
Source: SLIP
Detecting Module: IEAVTSLT
IEA430E

System Programmer Response: Make sure the SLIP
trap was specified correctly.
Source: SLIP
SLIP TRAP ID=xxxx

ACTION=SYNCSVCD CANNOT BE
PERFORMED; ACTION=SVCD DONE.
IEA426I
dev, MAINTENANCE REQUIRED,

ACTION CODE = ac
Explanation: A device returned an I/O error with an

action code. The device can run in degraded mode, but
it will eventually require maintenance.
dev
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.
589
Source: DFSMSdfp
Detecting Module: IGE0002G

IEA435I
IEA431A
dev, POSSIBLE LOST DATA, ACTION

CODE = cc
Explanation: A device returned an I/O error with an

action code. The system may not have printed one or
more print lines.
dev
The device number.
PHYSICAL DEVICE INCONSISTENT

WITH LOGICAL DEFINITION
[PHY=pdevtype LOG=ldevtype] text
Explanation: During VARY,ONLINE command

processing, the device service exit determined that the
physical device type was not compatible with the logical
device type defined in the I/O configuration.
If PHY=pdevtype LOG=ldevtype appears in the
message, there are mismatches between the hardware
configuration and the device definition in HCD.
cc Action code X'2', X'6', or X'B'.
System Action: The system issues the failing channel

command word (CCW) again.
pdevtype
The physical device type
Operator Response: See the book for the device type

for an explanation of the action code. To recover
missing output, backspace the JES writer or rerun the
job. Contact hardware support, if needed.
ldevtype

Detecting Module: IGE0002G
IEA432I
sysa IS REMOVING sysb FROM THE

SYSPLEX. sysa IS EXPERIENCING
STORAGE SHORTAGES.
Explanation: System sysb is attempting to join the

sysplex. However, system sysa cannot obtain enough
storage to maintain a view of sysb that is consistent
with other systems in the sysplex.
sysa
An active system in the sysplex.
sysb
A system that is attempting to join the sysplex.
System Action: System sysa removes the joining

system from the sysplex. The joining system enters wait
state code X'087'.
Operator Response: Relieve the storage constraint
on sysa, then reIPL sysb.
IEA434I
DEVICE ONLINE IS NOT ALLOWED,

reason
Explanation: During VARY ONLINE command

processing, the device service exit determined that the
device is not allowed to become online for the reason
specified. (Example, SPARE DEVICE).
System Action: The device remains offline.
System Programmer Response: Check the system
configuration to determine if the device number is
correct.
590
The logical device type defined in the I/O

configuration.
text
Additional message text.

Additional message information is issued if
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
through initialization I/O. The reasons for this
conflict are reported through the explanatory
text that is appended to the message. The
reasons are:
HCD DEVICE DEFINITION AT VARIANCE
WITH RDC DATA
The device is defined through HCD as one
type of device but RDC data indicates a
different type of device.
System Programmer Response: Correct
the HCD device definitions to match the
device type of the device physically
DEFINED WITH COMPACTION, BUT
FEATURE NOT PRESENT
The HCD definition for the device is at
variance with the actual attribute of the
device with respect to compaction.
3590 DRIVE DETECTED BUT NOT ALL 3590
SUPPORT IS PRESENT
Support for the 3590-E1x drives was
shipped through PTF UW90622. If this
PTF is not installed, this message will be
issued.
System Programmer Response: Install
the required maintenance.
3590 IN 3490 EMULATION MODE NOT

ALLOWED IN ATLDS
3590 tape devices that are operating in
their 3490 emulation mode are not
supported in the ATLDS.
System Programmer Response: Take
the device out of that emulation mode and
attach the device at the appropriate
address for its device type.
INITIALIZATION I/O FAILED
Initialization I/O required to successfully
initialize a tape device has failed.
Determine the cause of the failure.
SENSE ID I/O INDICATES UNSUPPORTED
DEVICE TYPE
Sense ID I/O was successfully issued to
the device and the resulting information
indicates a device type that is not
recognized by the system.
System Action: The device is not allowed online, and
remains offline.
System Programmer Response: Correct the HCD
device definitions to match the device type of the device
physically attached to the system. See also text above
for any other response needed, due to the additional
explanatory text.
Source: DFSMSdfp
IEA436I
I/O ERROR DURING DEVICE

INITIALIZATION
Explanation: During VARY,ONLINE command

processing, the device service exit received an
unexpected I/O error while attempting to obtain the
physical device characteristics.
This message can also be seen if an older device that
does not support the SENSE ID CHANNEL command is
attached to an incompatible UCB type; in other words,
the physical device does not match the logical device.
System Action: The device remains offline.
Operator Response: Use established procedures for
reporting a hardware error. If this appears to be a
mismatch of logical and physical device types, notify the
system programmer.
System Programmer Response: If the logical device
and physical device are not compatible, correct the
HCD device definitions.
Source: DFSMSdfp
IEA437I
TAPE LIBRARY DEVICE(dev), text
Explanation: Initialization for an ATLDS device failed.

The device will not be brought online until the cause of
the failure is corrected.
dev
The number of the failing ATLDS device
text

LIBRARY INTERFACE IS OFFLINE
The hardware communication path
between the tape control unit and the
library manager has not been established.
Recovery Action: Contact your hardware
service representative to restore the
communication path to the library
manager.
RETURNED A ZERO LIBRARY-ID
library manager has been established, but
the library manager returned an incorrect
library-id (zeroes) to the host.
service representative to repair the library
manager.
INITIALIZATION FAILURE
The device was defined with HCD as a
LIBRARY device, but the host was unable
to obtain library information from the
device. The channel program command
that failed was Read Device
Characteristics (RDC).
service representative to determine the
cause of the RDC failure.
UNAVAILABLE TO LIBRARY MANAGER
library manager has been established, but
the library manager has marked the
device unavailable.
service representative to repair the device
and restore its availability to the library
manager.
HCD(xxxxx-xx),DEVICE(xxxxx-xx)
During device initialization, it was found
that the LIBRARY-ID and LIBPORT-ID
specified to HCD do not match the
LIBRARY-ID and LIBPORT-ID that were
assigned to the hardware during
installation.
Recovery Action: Correct either the
hardware or HCD. If the hardware was in
591
error (or was incorrectly attached to the

system), correct the hardware and then
VARY the device ONLINE. Use the
command DS QT,dddd,RDC to determine
the library-ID and libport-ID assigned to
the hardware. In the following example,
device 2C80 is assigned library-ID BA067
and libport-ID 01:
DS QT,2C80,RDC
READ DEVICE CHARACTERISTICS
34905434905400EO 1FD8808004000000 00000000 00000000
0BA0607010000000 4281000000000000 00000000 00000000
ACTIVATE IODF=XX, IS REQUIRED

The device was unavailable when the
currently active eligible device tables
(EDTs) were built; the EDTs are used for
device allocation. Although the device is
now available to this system, it cannot be
allocated until the EDTs are rebuilt. EDTs
are rebuilt during IODF activation.
Recovery Action: Activate the current
IODF, then VARY the device ONLINE.
TAPE LIBRARY DEVICE aaaa (bbbbb-cc) IS
A DUPLICATE OF DEVICE xxxx (yyyyy-xx)
AND IS BEING MARKED FOR DELETION
A device with CUU=xxxx,
LIBRARY-ID=yyyyy, and LIBPORT-ID=zz is
being processed and another device with
CUU=aaaa, LIBRARY-ID= bbbbb, and
LIBPORT-ID=cc has been found that:
v has the same hardware reported
sequence number, or
v has the same CUU, that is, xxxx=aaaa.
It is determined to be the same device and
the device with CUU=aaaa is not allowed
online.
This can occur in a variety of situations,
for example, when two control units are
physically uncabled from the library, and
when recabled, the port cables are
switched.
vary the device online. Use the command
DS QT,dddd,RDC to determine the
library-ID and libport-ID assigned to the
hardware.
TAPE LIBRARY DEVICE aaaa (bbbbb-cc) IS
A DIFFERENT DEVICE TYPE THAN
DEVICES PREVIOUSLY DEFINED IN THE
SAME STRING. THE DEVICE IS NOT
ALLOWED ONLINE
A device with CUU=aaaa,
LIBRARY-ID=bbbbb, and LIBPORT-ID=cc
592
is a different device type than those that

were previously defined for the same
string.
vary the device online. Use the command
DS QT,dddd,RDC to determine the
library-ID and libport-ID assigned to the
hardware.
TAPE LIBRARY DEVICE aaaa (bbbbb-cc)
DEFINED AS MTL BUT DEVICE xxxx
(yyyy-zz) IS REAL ATL/VTS DEVICE. DEVICE
NOT ALLOWED ONLINE.
The tape drive at address aaaa, with HCD
defined LIBRARY-ID bbbbb and
LIBPORT-ID cc is defined as an MTL
resident drive (for example, MTL=YES was
specified with LIBRARY-ID and
LIBPORT-ID), but the RDC data indicates
that the drive resides in the ATLDS. The
device is treated as a valid ATL resident
drive.
Recovery Action: Review the HCD
definition for the device.
EMULATING 3490 NOT ALLOWED ONLINE
IN AN MTL.
LIBPORT-ID=cc, is defined as an MTL
resident drive but is emulating a 3490
device which is not supported in an MTL.
The device is not allowed online.
definition for the device.
MTL DEVICE aaaa (bbbbb-cc) IS ATTACHED
TO A CONTROL UNIT THAT IS DIFFERENT
THAN THAT FOR OTHER DEVICES
ALREADY IN THE POOL.
LIBPORT-ID cc, is attached to a control
unit different than that for devices already
in the pool. The device is not allowed
online.
definition for the device, and other devices
with the same LIBRARY-ID and
LIBPORT-ID values. Ensure that all
devices for the same LIBRARY-ID and
LIBPORT-ID values are connected to the
same control unit.
NOT ALLOWED ONLINE, UNABLE TO ADD
LIBRARY TO CONTROL BLOCK.

LIBPORT-ID cc, cannot be added to the
existing device pool because it is full. The
device is not allowed online.
definition for the device, and other devices
with the same LIBRARY-ID and
LIBPORT-ID values. Ensure that MTL
devices are not overgenned.
INVALID PEER-TO-PEER VTS DATA
During initialization of a device in a
Peer-to-Peer VTS, the I/O operation
requesting Peer-to-Peer configuration data
either failed or returned invalid information.
This message is issued when an RDC
command returned data indicating that the
device is in a Peer-to-Peer VTS library.
However, the subsequent request to obtain
Peer-to-Peer data failed (or returned
invalid data).
Recovery Action: Correct your hardware
service representative to determine the
System Action: The device is not available for use by
the system.
System Programmer Response: When the condition
has been corrected, attempt to VARY the device
ONLINE. If the device was previously defined to HCD
as a library device, with the proper library-ID and
libport-ID, the device will come ONLINE.
If the device is not defined with HCD as a library device,
the device will not be allowed ONLINE if an IODF
activate is required. Message ACTIVATE IODF=XX, IS
REQUIRED indicates that because of previous failure,
the library-ID and libport-ID were not known when the
systems EDTs were build. Now that these IDs are
known, an activate is required in order to cause the
EDTs to be rebuilt.
Source: Tape Device Initialization Exit (DSE)
Detecting Module: IECTDSR2
IEA438I
THE FOLLOWING TAPE LIBRARY

DEVICE ARE UNAVAILABLE: dev [dev
... dev [*dev]]
System Action: The device is not available for use by

the system.
System Programmer Response: To determine the
reason that a device is unavailable, attempt to vary one
of the devices online. If the error has been corrected,
the device will be brought online. If the error still exists,
message IEA437I will explain the reason for the failure.
If the device is displayed with an asterisk, it will become
available when the error has been corrected.
If the device is not displayed with an asterisk, perform
an IPL or an I/O activate after correcting the error to
make the device available to the system after the error
has been corrected.
If an I/O activate is to be done, the device must first be
varied online. The device does not need to remain
online.
Source: Tape Device Initialization Exit (DSE)
Detecting Module: IECTDSR2
IEA441I
UNABLE TO ESTABLISH MVS MODE

CONTROLS FOR DEVICE nnnn
Explanation: An error was encountered during

issuance of mode control CCWs for device number
nnnn. The error prevents setting the mode control page
values. When these controls are not properly set, the
device cannot be brought online.
Mode control CCWs set certain attributes of the device
in a manner well-defined for normal MVS processing.
Mode control CCWs are issued by MVS when the
device:
is allocated if it is ready, or
comes ready, if it is already allocated
System Action: The device is boxed.
Operator Response: Once the cause of the error has
been determined and corrected, the device can be
varied online. Varying the device online before the error
is corrected may cause the error to occur again.
System Programmer Response: Collect diagnostic
data such as GTF traces for I/O and any system logs
that are available. Follow your installations procedures
for reporting this error.
Source: Asynchronous Operation Manager Attention
Processing Routine for Tape Devices (AOMATTNT)
Explanation: During IPL, initialization failed for one or

more library devices. In many cases, this message is
normal and expected. For example, if the interface to a
3490 string is disabled, and the devices were defined
with HCD as library devices, those library devices will
be listed in this message.
IEA442E
Devices that are displayed with an asterisk will become

available when the error has been corrected, without an
IPL or I/O activate request being required.
Explanation: An I/O request failed because a storage

director within a 3880 Storage Control Unit is disabled.
dev REPORTS DISABLED INTERFACE

ON nn -- FAULT CODE = cccc -- NOTIFY
CE
[CONTINUATION OF IEA442E
SNS=sense]
593
dev
The address of the I/O device that reported the

disabled status of storage director.
returned environmental data. The data has been written

to the logrec data set.
nn
The disabled storage director identifier.
cccc
The fault code that explains why the storage

director is disabled.
ss
Subsystem ID (SSID)
ss.p
SSID storage path
sense
Sense data.
xx-xx
Controller device
sense
Sense data.
System Action: The system records the disabled

status of storage director in a logrec data set error
record. The system retries the I/O request on the
specified device.
v Isolate the failing control unit. Contact hardware
support to repair it.
v If only one unit remains, transfer critical applications
to back-up.

Source: DFSMSdfp
Detecting Module: IGGSNS01
IEA449A
v Identify and recover failing tasks.
[CONTINUATION OF IEA449A
SNS=sense]
Source: DFSMSdfp
Detecting Module: IECVDERP, IGGSNS01
IEA447E
PATH chp TO DEVICE s-cc-d

UNAVAILABLE
RESET WRITE INHIBIT SWITCH ON

PAGING DEVICE - device-number
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
physical 3350, as follows:
Digit
3350 Device
0 or 8
1 or 9
2 or A
3 or B
4 or C
5 or D
System Action: The system varies the path offline. If

additional paths are available, the system retries the
failing channel program on another path to the device.
6 or E
7 or F
Operator Response: If the data path switch is open,

close it. Otherwise, do the following:
Explanation: The system cannot reach a device

through a path. A hardware error occurred, or the data
path switch for the device is open.
chp
The identifier (CHPID) of the unavailable

channel path.
ss-cc-d The identifier of the storage director that found

the problem.

to back-up.
Source: DFSMSdfp
device-number
The path ID of the path that reported

the error.
sense
Sense data.
System Action: The error recovery procedure (ERP)

reissues the channel command words (CCWs) that
failed.
Operator Response: Set the 3350 write inhibit switch

to the write position. Then reply U to this message.
IEA448I
This message may be followed by another IEA449A

message after you have set the switch; reply U to this
second IEA449A to continue processing.
1,SENSE DATA LOGGED FOR DEVICE

ss.p-xx-xx
[CONTINUATION OF IEA448I
SNS=sense]
2,SENSE DATA LOGGED FOR
CONTROLLER ss.p-xx-xx
Explanation: The specified device or controller has
594

Source: DFSMSdfp
IEA451I
{MICROCODE LOGICAL|SUBSYSTEM
PROCESSING} ERROR - FAULT CODE
= cccc-ss.p-xx-xx
SNS=sense]

Source: DFSMSdfp
IEA453I
{SUBSYSTEM|NVS} STORAGE
AVAILABILITY THRESHOLD CROSSED
-ss.p-xx-xx
Explanation: An internal logic error occurred during a

subsystem storage operation on a Storage Control
device with a cache.
SNS=sense]
cccc
The fault symptom code from sense bytes 22

and 23.
ss.p-xx-xx
The physical identifier of the reporting storage
director.
sense
Sense data.
System Action: The system ends I/O processing for

this request. If the error occurred in a Storage Control
device with a cache subsystem storage is taken offline,
and future I/O requests are processed directly with the
DASD.
Operator Response: The system issues this message
because of a microcode error. Follow installation
procedures to take corrective action.
occurred on the Model 11 or 21, reconfigure the system
to move the paging data to another subsystem.
Otherwise, no action is required.
Source: DFSMSdfp
IEA452I
SUBSYSTEM STORAGE EQUIPMENT

CHECK - FAULT CODE =
cccc-ss.p-xx-xx
Explanation: The amount of subsystem storage

offline, in the 3880 Storage Control with a cache
crossed a reporting boundary making a portion of the
subsystem storage unusable.
ss.p-xx-xx
director.
sense

reissues the channel command words (CCW) that
failed.
because of a hardware error. The subsystem storage
remains operational, allowing service to be deferred
until it is convenient. Follow installation procedures to
take corrective action.
Source: DFSMSdfp
IEA454E
SNS=sense]
Explanation: An equipment check occurred during a
subsystem storage operation on the 3880 Storage
Control with a cache.
cccc

and 23.
ss.p-xx-xx
director.
sense
Sense data.
Sense data.
SUBSYSTEM STORAGE IS UNUSABLE

- FAULT CODE = cccc-ss.p-xx-xx
SNS=sense]
Explanation: Subsystem storage in a Storage Control

device with a cache is unusable due to previously
reported failures of a device or subsystem storage. The
failures are recorded in the error recording data set.
cccc

and 23.
ss.p-xx-xx
director.

this request.
sense

because of a hardware error. Follow installation

this request. If the problem occurred in a Storage
Control device with a cache subsystem storage is taken
Sense data.
595
offline, and future I/O requests are processed directly

with the DASD.
because of a hardware error. Follow installation
occurred on the 3880 Model 11 or 21, reconfigure the
system to move the paging data to another subsystem.
Otherwise, no action is required.
Source: DFSMSdfp
IEA455E
SUBSYSTEM STORAGE MUST BE

INITIALIZED - FAULT CODE =
cccc-ss.p-xx-xx
SNS=sense]
Explanation: An error occurred during a subsystem

storage operation on the 3880 Storage Control Model
11 or 21. The data in the cache may not be valid.
ss.p-xx-xx
director.
sense

failed.
Application Programmer Response: Format the
paging packs attached to the paging storage director of
the 3880 Model 11 or 21.
Source: DFSMSdfp
IEA458I
cccc

and 23.
ss.p-xx-xx
director.
sense
Sense data.

this request.
because of a hardware error. System IPL may be
required to continue operations. System IPL is required
to reinitialize the storage for this subsystem. Follow
installation procedures to take corrective action.
subsystem storage remains unusable following the
system IPL, reconfigure the system to move the paging
data to another subsystem.
Source: DFSMSdfp
IEA457I
STORAGE DIRECTOR
COMMUNICATION FAILED - FAULT
CODE = cccc-ss.p-xx-xx
SNS=sense]
Explanation: The 3880 cache control unit storage

directors cannot communicate.
cccc

and 23.
ss.p-xx-xx
director.
sense
Sense data.

failed.
Operator Response: Check the 3380 Enable/Disable
switches to ensure that they are enabled. If the 3380
switches are enabled, or the problem occurred on the
3880 Control Unit, this problem is probably the result of
a hardware error. Follow installation procedures to take
corrective action.
TRACK FORMAT NOT SUPPORTED

FOR PAGING - ss.p-xx-xx
SNS=sense]
Explanation: The 3880 Storage Control Model 11 or

21 detected an incorrect track format or no-record-found
error.
596
Sense data.
Source: DFSMSdfp
IEA459I
CACHING [RESET-REDEFINE BOUND

AREAS/NON-CACHING DEVICES|
REINITIATED] - ss.p-xx-xx
SNS=sense]
Explanation: Caching was automatically reinitialized

by the 3880 Storage Control following a storage director
communication timeout or a subsystem storage control
structure failure.
ss.p-xx-xx
director.
sense
Sense data.

reissues the channel command word (CCW) that
received the message.
Operator Response: Bound areas of cache and the
non-caching state of the devices were reset. If any
bound areas or non-caching devices are required, they
must be established. If none are required, no action
need be taken.

stand-alone dump.
Source: Supervisor Control
Detecting Module: IEAVEGR
PATH(dev,chp) PERMANENT I/O
ERROR {sense|FAULT CODE=cccc}
IEA466I
Explanation: The system detected a permanent error

on a single path on a device with multiple paths. The
system completed the request on an alternate path to
the device.
dev
The device number.
chp
The channel path identifier (CHPID).
sense
The sense byte information.
cccc
The fault code.
System Action: The system varies the path offline.


to back-up.
Source: DFSMSdfp
Source: DFSMSdfp
IEA460W
SYSTEM ERROR: WAIT STATE CODE:

ccc REASON CODE: rrr [THE SYSTEM
CANNOT TERMINATE ASID hhhh]
Explanation: The system attempted to rebuild the

work unit queues, but it could not do so successfully.
ccc
The wait state code.
rrr The reason code associated with the wait state

code.
THE SYSTEM CANNOT TERMINATE ASID hhhh
The system encountered an address space whose
queues it could not rebuild, so it tried to terminate
the address space. The system could not terminate
the address space, so it entered a wait state.
hhhh
The identifier of the address space that the system
needed to terminate in order to continue
processing.
wait state.
Operator Response: Provide a stand-alone dump, if
requested by the system programmer.
Detecting Module: IECVDER2

IEA467E
PATH(dev,chp) type WRITE INHIBITED

sense
Explanation: The system found a hardware write error

on a channel path. Recovery was unsuccessful on that
path. Subsequent writes to that device or any other
device on that interface could result in a loss of data.
dev
The device number.
chp
sense
The sense byte information.
type
The component for which the system

established the write inhibit condition. One of
the following devices:
v The channel interface
v The storage director
v The DASD controller
System Action: The system varies the device path

logically offline. The system issues message IEA469E.
If additional paths are available, the system retries the
failing chain on another path to the same device.
Operator Response: If the error persists, do the
following:
597
1. Enter the following: to vary the path offline,

assuming that the path is online but not allocated:
VARY PATH(dev,cc),OFFLINE, UNCOND
2. After hardware support corrects the problem, submit
a job to run an ICKDSF CONTROL command to
reset the fenced condition to one of the devices
attached to the fenced interface.
reset the fenced condition to one of the devices

attached to the fenced interface.
3. If no online paths remain to the device, do the
following:
v VARY FORCE the devices attached to the
interface offline.
v Cancel all jobs that are using the device.
3. If no online paths remain to the device, do the

following:
v Vary online at least one path to the device.

v Vary the device online, making sure that no jobs
allocate the pack.
v VARY FORCE the devices attached to the

interface offline.
v Vary online at least one path to the device.
v Enter an ICKDSF CONTROL WRITEALLOW

command, directing it to one device attached to
the failing interface.
v Vary the device online, making sure that no jobs

allocate the pack.
v Vary online all paths that the system varied

offline.
v Cancel all jobs that are using the device.

4. If paths remain online, do the following:


offline.

offline.
4. If paths remain online, do the following:

offline.
Source: DFSMSdfp
IEA469E
{PATH (dev,chp) HAS BEEN VARIED

OFFLINE| PATH (dev,chp) CANNOT BE
VARIED OFFLINE}
Source: DFSMSdfp
SNS=sense]

IEA468I
WRITE INHIBITED PATH (dev,chp)

ENCOUNTERED
SNS=sense]
Explanation: The system tried to issue I/O to a device

through a path that was write inhibited.
Explanation: A hardware error occurred. Recovery for

the direct access storage device (DASD) determined
that a path should be varied offline.
dev
The device number.
chp
sense
Sense data.
dev
The device number.
chp
System Action: If the path is online, the system

retries the failing channel command word (CCW) chain
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

additional paths are available, the system retries the
failing I/O on another path to the same device.
Operator Response: If the error persists, do the
following:
1. Enter the following: to vary the path offline,
assuming that the path is online but not allocated:
VARY PATH(dev,cc),OFFLINE, UNCOND
2. After hardware support corrects the problem, submit
a job to run an ICKDSF CONTROL command to
PATH (dev,cc) HAS BEEN VARIED OFFLINE

The DASD recovery varies the path offline.
PATH (dev,cc) CANNOT BE VARIED OFFLINE
The DASD recovery does not vary the path offline
because it is the last path to the device.
Operator Response: If PATH (dev,cc) CANNOT BE
VARIED OFFLINE appears in the message text, and the
error persists, enter a VARY PATH or UNCOND
command to vary the path offline.
Source: DFSMSdfp
598
IEA473I
vvvvvv FENCED FROM STORAGE PATH

x - device-number/ssid.p-cc-nn
IEA475E
SNS=sense]
Explanation: A device is unavailable through a
storage path due to a hardware error.
vvvvvv IS SUSPENDED DUPLEX

{PRI|SEC} FAILED|INTERVENTION
REQUIRED - ccu/ssid.p-cc-nn
SNS=sense]
vvvvvv
The volume that failed.
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
improper procedures.
The storage path fenced.
device-number
The physical device address.
vvvvvv
ssid
The subsystem identifier.
device-number
The storage path.
ssid
cc
The controller address.
The storage path.
nn
The device number.
cc
sense
Sense data.
nn
The device number.
sense
Sense data.
System Action: The subsystem attempts to recover

the operation using an alternate path.
because of a hardware error. Follow your installations
procedures for reporting this error.
Source: DFSMSdfp
IEA474E
NONVOLATILE STORAGE UNUSABLE ccu/ssid.p-xx-xx

SNS=sense]
Explanation: The nonvolatile storage failed or could

not be initialized.
System Action: Processing will continue in suspended

duplex mode.
procedures for reporting this error. If the device
associated with this message is attached via the IBM
3990 Model 3 or Model 6 Storage Control, see IBM
3990/9390 Operations and Recovery Guide for detailed
recovery actions.
Source: DFSMSdfp
IEA476E
device-number
ssid
The storage path.
sense
Sense data.
System Action: DASD fast write operations will

continue without using fast write. Dual copy will continue
with reduced recovery in the event of a cache failure.
vvvvvv ACCESS PROHIBITED RC=(reason-code) device-number/ssid.pcc-nn

SNS=sense]
Explanation: The status of the subsystem or a device

cannot be determined. Access is not allowed until the
problem is corrected.
vvvvvv
reason-code
The reason code of the failure. See

IBM 3990/9390 Storage Control
Reference, Chapter 5, Sense Byte
Information under the heading Format
F Message C.
device-number
ssid
The storage path.
Source: DFSMSdfp
599
cc
nn
The device number.
sense
Sense data.
during a destage operation. The data is pinned in

cache/nonvolatile storage.
vvvvvv
device-number

because of a hardware error or configuration problem.
Follow your installations procedures for reporting this
error. If the device associated with this message is
attached via the IBM 3990 Model 3 or Model 6 Storage
Control, see IBM 3990 Operations and Recovery Guide
for detailed recovery actions.
ssid
The storage path.
cc
nn
The device number.
sense
Sense data.
Source: DFSMSdfp

recovery actions.

this request.
IEA477I
vvvvvv PERMANENT DATA CHECK ON

PRIMARY - RECOVERED ON
SECONDARY device-number/ssid.p-cc-nn
SNS=sense]
Explanation: A permanent read data check on the

primary device of a duplex pair was recovered by
reading the secondary device.
Source: DFSMSdfp
IEA479E
vvvvvv TRACK FORMAT NOT

CORRECT FOR DESTAGE - RC=(rc)
device-number/ssid.p-cc-nn
vvvvvv
device-number
ssid
The storage path.
Explanation: An attempt to write data from cache to

DASD encounters a DASD track format incompatible
with the operation.
cc
nn
The device number.
vvvvvv
sense
Sense data.
reason-code
The reason code of the failure. See

IBM 3990/9390 Storage Control
Reference, Chapter 5, Sense Byte
Information under the heading Format
F Message 7.
device-number
ssid
The storage path.
cc
nn
The device number.
sense
Sense data.
SNS=sense]

Operator Response: Follow your installations
3990 Model 3 or Model 6 Storage Control, see detailed
recovery actions information in the IBM 3990/9390
Operations and Recovery Guide.
Source: DFSMSdfp
IEA478E
PINNED DATA FOR vvvvvv device-number/ssid.p-cc-nn

SNS=sense]
Explanation: A permanent hardware error occurred
600
System Action: If the destage is for a fast write, the

track is pinned in cache/nonvolatile storage. If the
destage is to a duplex pair, the duplex pair is
suspended.
Operator Response: Follow your installations

3990 Operations and Recovery Guide for detailed
recovery actions.
twelve hexadecimal characters is the

recommended media maintenance
procedure number.
volser
The volume serial number of the

failing volume. This field is only
applicable for 3390 SIMs where the
device or volume is involved in the
failure.
id
Two-hexadecimal character SIM ID.

SIM ID is a subsystem-assigned
identifier for each individual SIM. It
appears in the console message as a
discrete field only for 3390 SIMs. For
3990 SIMs, it is contained in the
REFCODE as the last two digits.
cccc hhhh
MEDIA ALERTs only. Hexadecimal

cylinder/head address of the failing
track. Provided for use by automated
media maintenance actions or to
initiate media maintenance actions
without the need to run EREP.
REPEATED
Appears for non-MEDIA ALERTs only.

This field is shown when the SIM is a
repeat presentation of a
previously-reported SIM.
Sense data.
Source: DFSMSdfp
IEA480E
yyyy, {SCU | CACHE | DASD | MEDIA },

{SERVICE | MODERATE | SERIOUS |
ACUTE} ALERT, MT=machine
type/model, SER=MMPP-SSSSS,
REFCODE= nnnn-nnnn-nnnn,
VOLSER=volser, ID=id, CCHH=x'cccc
hhhh', REPEATED [CONTINUATION OF
IEA480E SNS=sense]
Explanation: IEA480E is a Service Information

Message (SIM) console message. The specified device
or storage control has detected an abnormal condition
that requires operator or service attention.
yyyy
Address or number of the device or

storage control that reported the error.
SCU
Storage control hardware.
CACHE
Storage control cache of nonvolatile

storage.
sense
DASD
Storage device hardware.
System Action: The system logs an alert in the

LOGREC data set and continues processing.
MEDIA
Device data storage media.
SERVICE|MODERATE|SERIOUS|ACUTE
Describes the severity of the SIM
event being reported. ACUTE is the
most severe and SERVICE is the
least severe. For additional details,
see IBM 3990 Operations and
Recovery Reference.
machine-type/model
Machine type and model number (7
characters maximum).
MMPP-SSSSS
Where:

to indicate that operator or service attention is required.
Follow your installations procedures for obtaining
service. Consult your customer engineer, if applicable.
System Programmer Response: Run an EREP
System Exception Report to obtain a Service
Information Message report for additional information.
Source: DFSMSdfp
IEA480E
v MM identifies the manufacturer (01

indicates IBM).
v PP identifies the manufacturing
plant.
v SSSSS is the five-digit machine
serial number.
nnnn-nnnn-nnnn-nnnn
Twelve hexadecimal characters;
provides encoded information,
including the FRU number to repair
the failure if a service SIM. For
MEDIA ALERTs, the last digit of these
yyyy,{TLIB | TCU | TVIR | TAPE}, mt,

{ACUTE | SERIOUS | MODERATE |
SERVICE} ALERT, SER=mmpp-sssss,
MC=mc, ES=es, ID=id, REF=
ref1-ref2-ref3, UM=um1-um2-um3,
{CLEAN | CLEAN/SERVICE |
CLEANED}, REPEATED
Explanation: IEA480E is a Service Information

Message (SIM) console message. The specified tape
library, tape controller, virtual tape server, or tape drive
unit has detected an abnormal condition that requires
operator or service attention.
yyyy
Address of unit that reported the SIM

message.
601
TLIB
Automated tape library.
TCU
Tape control unit.
TVIR
Virtual Tape Server (VTS).
TAPE
Tape drive.
mt
Machine type of unit that caused the

SIM message. This will reflect the
software image of the machine type,
not necessarily the underlying physical
machine type. VTS, for example, will
report '3490' as the machine type,
even though the underlying drive
machine type may be 3590.
ACUTE|SERIOUS|MODERATE|SERVICE
Indicates the severity of the SIM
message. ACUTE is the most severe
and SERVICE is the least severe.
ser
Serial number of unit referenced by

the SIM message.
mc
Message code. Indicates source of

SIM.
es
Exception/Service code.
id
Identifier of the SIM in the control unit

internal SIM log.
ref1-ref2-ref3
Error reference codes.
um1-um2-um3
Unit modifier reference codes. Some

software releases may not include
these codes.
CLEAN
Tape drive requires cleaning cartridge

to be inserted. Only returned for a
TAPE unit.
CLEAN/SERVICE
Tape drive requires cleaning cartridge
to be inserted. Repeated occurrences
of CLEAN/SERVICE indicate the need
for additional service. Only returned
for a TAPE unit.
CLEANED
Cleaning just completed for the tape

drive. Cleaning cartridge ejected. Only
returned for a TAPE unit.
software levels will only specify the ES code for

cleaning.
If the specified unit is TAPE and CLEAN/SERVICE is
presented (or ES=8B), then cleaning is required. Note
that some software levels will only specify the ES code
for cleaning.
Repetitive occurrences of the CLEAN/SERVICE
message indicate that service beyond cleaning is
required.
If the specified unit is TAPE and CLEANED is presented
(or ES=9A), then cleaning was completed. No further
action is required. Note that some software levels will
only specify the ES code for cleaning completed.
If the specified unit is TAPE and ES has any other
value, then consult your customer engineer for detailed
recovery actions for the installed tape drive.
If the specified unit is TLIB, then consult your customer
engineer for detailed recovery actions for the installed
library.
If the specified unit is TVIR, then consult your customer
VTS product.
If the specified unit is TCU, then consult your customer
tape control unit.
System Exception Report to obtain a Service
Information Message report for additional information.
Source: DFSMSdfp
IEA481I
CONTROLLER NOT OPERATIONAL

WITH STORAGE PATH device-number/ssid.p-cc-nn
SNS=sense]
Explanation: The specified DASD controller cannot be

accessed through the specified storage path.
device-number
ssid
The storage path.
cc

to indicate that operator or service attention is required.
Follow your installations procedures for obtaining
service. Consult your customer engineer, if applicable.
nn
The device number.
sense
Sense data.
If the specified unit is TAPE and CLEAN is presented

(or ES=89), then cleaning is required. Note that some

REPEATED
Indicates this SIM has already been

presented at least once prior to this
presentation.

602

recovery actions.
command. Issue the MODIFY

LOGROUTE,NODEID=nodevalue.useridvalue command
to correct the NODEID value.
Source: DFSMSdfp
Source: DFSMSdfp
IEA484I
ser WAITING FOR CONTROL UNIT dev, REASON CODE=(nn)
IEA482I
SNS=sense]
Explanation: I/O was attempted to DASD device
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
busy condition.
This problem may be caused by one of the following:
v The control unit could be busy destaging DASD fast
write data for the device when a SETCACHE
DASDFASTWRITE OFF command was issued.
v The control unit could also be busy copying data from
the primary device to the secondary device if a
SETCACHE SETSECONDARY command was issued
to the device, particularly if PACE(0) parameter was
specified.
ser
Volume serial number.
dev
DASD device number.
nn
Reason code
sense
Sense data.
System Action: The system will queue and

periodically retry the I/O to device dev until the control
unit accepts the request. Message IEA482I will be
displayed for each retry of the I/O request while the
busy condition exists.
Source: DFSMSdfp
IEA483I
LOGROUTE FAILED - DYNAMIC

ALLOCATION ERROR RC=return-code
Explanation: A user issued the START LOGROUTE

command to route a record to the workstation
NODE.USERID, but the command failed because of a
dynamic allocation error.
SNS=sense]
Explanation: Retentive status of the subsystem, a fast
write or dual copy has been reset.
device-number
ssid
The storage path.
cc
nn
The device number.
sense
Sense data.

actions.
Source: DFSMSdfp
IEA486E
The return code.
cuu
Address of unit that reported the MIM

message.
TVOL
Tape Volume.
ACUTE|SERIOUS|MODERATE|SERVICE
Indicates the severity of the MIM
message. ACUTE is the most severe
and SERVICE is the least severe.
volid
Volid of the tape volume referenced

by the MIM message. If blank and the
volume was not unlabeled, the volid
may still be determined from job or
system logs.
Volid source.
System Action: No log records will be routed to the

workstation NODE.USERID.
system programmer. If return-code is 046C, an incorrect
NODE was specified on the START LOGROUTE
cuu, TVOL, {ACUTE | SERIOUS |

MODERATE | SERVICE} ALERT,
VOLUME=volid, S=s, MC=mc, E=e,
REF=refc-med-fi, REPEATED
Explanation: IEA486E is a Media Information

Message (MIM) console message. The specified device
has detected an abnormal medium condition that
requires storage administration attention.
return-code
CACHING STATUS RESET TO

DEFAULT - device-number/ssid.p-cc-nn
603
mc
Message code (to indicate MIM

source).
Exception code.
refc-med-fi
Error reference code - Media identifier

- Format identifier.
REPEATED
Indicates this MIM has already been

presented.

to indicate that storage administrator attention is
required. For instructions, consult your customer
engineer for the installed model supporting the indicated
media and format.
System Exception Report to obtain a Media Information
Message report to obtain additional information.
Source: DFSMSdfp
IEA489I
INVALID SYSTEM LEVELS OF

QUALIFICATION. DEFAULT OF 1 USED
Explanation: In the SYSCATnn member of

SYS1.NUCLEUS, the field that defines the system
levels of qualification is incorrect. Valid values are 01,
02, 03, 04, F1, F2, F3, F4, or 40. (The last five values
are EBCDIC codes for decimal 1, 2, 3, 4, and blank.)
System Action: The system continues processing,
using the default of 1 as the level of qualification.
Operator Response: Issue MODIFY
CATALOG,ALIASLEVEL(n), where n is the number of
levels of qualification requested by the system
programmer.
System Programmer Response: To correct the field
in the SYSCATnn member, ask the operator to issue a
MODIFY CATALOG,ALIASLEVEL(n) command. Provide
a value for n to the operator. n is the number of levels
of qualification. The valid range for n is 1 through 4.
Source: DFSMSdfp
IEA491E
volser-PPRC SUSPENDED error-reason,

(PRI) SER=aaaa-bbbbb,CCA=xx (SEC)
SER=aaaa-bbbbb,CCA=xx
SNS=sense]
Explanation: The peer-to-peer remote copy operation

has been suspended at the time indicated for the error
reason stated in the message.
604
Note: The time indicated in the message is the

timestamp of the ERP action message, and not
necessarily the exact time of the failure. Select
the CRIT(YES) option of the CESTPAIR
command if you require exact synchronization to
the time of the failure.
volser
This is the volume serial number of the PPRC
volume pair encountering the failure.
error-reason
The error reasons are:
v SUSPENDED, PRIMARY-DEVICE-WRITEFAILURE
A write failure occurs during a write operation
from the application site storage control to the
primary device indicated by the volume serial
number. The primary volume storage control
continues to keep track of changed cylinders,
such that after the error is corrected, you may
select the RESYNC option to reestablish the
PPRC pair.
v SUSPENDED, SECONDARY-SUBSYSTEMFAILURE
An error occurs in the recovery storage
subsystem that has caused the peer-to-peer
remote copy pair to be suspended at the time
indicated. The primary volume storage control
continues to keep track of changed cylinders,
such that after the error is corrected, you can
select the correct reestablish method. If the error
is such that data may have been lost (for
example, a physical secondary device error or
the loss of NVS), after the error is corrected,
select the COPY option to reestablish the PPRC
pair.
v SUSPENDED, COMMUNICATION-TOSECONDARY-FAILURE
An error has been encountered in the
peer-to-peer remote copy communications paths,
such that the application site storage control for
the device indicated can no longer communicate
with the target volumes storage control. The
primary volumes storage control continues to
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,
ALL-WRITES-FAILED
A previous PPRC error has occurred on a
volume established with the CRIT(YES)
parameter. A write I/O has occurred to the
volume indicated by the volume serial number
and it has been unit checked.
v SECONDARY NOT READY,
The secondary device of a PPRC pair has been
suspended because the secondary device in the
pair is not ready. The primary volume storage
control continues to keep track of changed

cylinders. After the error is corrected, you may
select the RESYNC option to reestablish the
PPRC pair.
(PRI) SER=aaaa-bbbbb,CCA=xx
This is the primary PPRC volume storage control
serial number followed by the primary volumes
channel connection address. The reported serial
number can be one of the following:
v aaaa The first four bytes of the storage
control serial number.
v bbbbb The last five bytes of the 12-byte
sequence number portion of the serial number.
This number can be found on the lower left-hand
portion of the storage control operator panel.
v xx The two-byte channel connection address.
(SEC) SER=aaaa-bbbbb,CCA=xx
This is the PPRC secondary volumes storage
control serial number followed by the secondary
volumes channel connection address. The reported
serial number can be one of the following:
v aaaa The first four bytes of the storage control
serial number.
v bbbbb The last five bytes of the 12-byte
sequence number portion of the serial number.
This number may be found on the lower
left-hand portion of the storage control operator
panel.
v xx The two-byte channel connection address.
sense
Sense data.
System Action: Unless CRIT(YES) has been
specified when the PPRC pair was established, the
processing continues in suspended state.
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
select the RESYNC option to reestablish the PPRC pair.
However, depending on the nature of the error, if there
is a possibility that data has been lost on the secondary
subsystem or device, the recovery action requires a full
copy after the problem has been fixed and the PPRC
pair reestablished.
Application Programmer Response: This is a
hardware problem. Contact your hardware support
personnel.
message has previously occurred.

IEA492I
SSID=subid,PARTITION=partition, text action
Explanation: The capacity manager has detected a

capacity status change for a device configured in the
specified partition, either from normal status to abnormal
status or from abnormal status to normal status.
subid
The subsystem identifier of the subsystem to which
the device is configured.
partition
The partition identifier where the device is
configured.
text
v CAPACITY USAGE IS BELOW percent%
v CAPACITY USAGE IS ABOVE percent%
action
v DFHSM CALLED FOR device-number,volser
v DFHSM NOT INSTALLED
v DFHSM NOT ACTIVE
v DFHSM CALL FAILED
System Action: If the device capacity status becomes
abnormal, the system attempts to invoke DFHSM to
migrate the data off the volume. No action is taken if the
device capacity status becomes normal.
Operator Response: If the error message persists or
if the attempt to call DFHSM is not successful, contact
Source: DFSMShsm
IEA493I
NIP CONSOLE NOT FOUND
Explanation: No suitable nucleus initialization program

(NIP) console has been found. This message is
accompanied by wait state code X'007'.
System Action: The system logs this message before
loading non-restartable wait state X'007'.
Operator Response: Follow the operator response for
wait state X'007'.
System Programmer Response: Follow the system
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
605
IEA494I
dev, volser, PPRC state, SSID=ssid,

CCA=ca, optional-text
Explanation: The state of the PPRC pair has

changed.
dev
The device number of the primary device of a
PPRC pair.
volser
The volume serial number of the primary device of
a PPRC pair.
state
The new state of the PPRC pair is one of the
following:
SUSPENDING
The control unit is in the process of suspending
the PPRC pair. This text appears only when
the device is in the extended long busy state,
and EXTENDED LONG BUSY STATE will
appear at the end of the message.
SUSPENDED
The PPRC pair has changed from PENDING
or FULL DUPLEX state to SUSPENDED state.
If the device is in the extended long busy state,
the message will have the optional text
EXTENDED LONG BUSY STATE appended at
the end.
TERMINATED
The PPRC pair has terminated from the
PENDING, FULL DUPLEX, or SUSPENDED
state.
PAIR PENDING
A PPRC copy operation is starting. This may
be initial or from a previous suspended state.
PAIR FULL DUPLEX
A PPRC copy operation has completed and the
primary and secondary devices are
synchronized.
ssid
The ssid of the primary device of the PPRC pair.
ca The two-byte channel connection address of the

primary device of the PPRC pair.
optional-text
EXTENDED LONG BUSY STATE.
Note: The optional text is present only if the PPRC
control unit microcode is at the correct level and the
Vital Product Data bit has been set at the control unit
panel, requesting activation of extended long busy
mode. The duration of this extended long busy is also
set at the control unit panel, with a default value of
606
approximately two minutes. Contact your hardware

support group if assistance is required to set the bit and
duration.
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
may receive more than one variation of the
SUSPENDING and/or SUSPENDED state message
during a suspending event.
System Action: If no action is taken by the operator
or automation program , at the end of the EXTENDED
LONG BUSY period, processing will continue in
suspended duplex state
Note: See message IEA491E for additional information
related to this message. Message IEA494E will be
detected and issued by only one of the systems where
the device is attached.
Operator Response: This message is intended for
use by automation programs that monitor operator
messages. Actions may be attempted by the operator,
but an automation program is recommended.
Source: DASD device initialization/re-initialization
Detecting Module: IECCINIT
IEA495I
dev, volser, DUAL COPY PAIR state,

SSID=ssid, CCA=ca, optional-text
Explanation: The state of the dual copy pair has

changed.
dev
The device number of the primary device of a dual
copy pair.
volser
a dual copy pair.
state
The new state of the dual copy pair is one of the
following:
FULL DUPLEX
The copy of the primary device of the dual
copy pair to secondary is complete and the
primary to secondary devices are
synchronized.
TERMINATED
The dual copy pair has been terminated from
the PENDING, FULL DUPLEX, or
SUSPENDED state.
PENDING
A dual copy operation is starting or restarting.
The primary and secondary devices are not
synchronized yet.
SUSPENDED
The dual copy pair has changed from the
PENDING or FULL DUPLEX state to the
FAILED or SUSPENDED state.
ssid
The ssid of the primary of the dual copy pair.
volser
a mirrored pair.
state
The new state of the mirrored pair is one of the
following:
ca The two-byte channel connection address of the

primary device of the dual copy pair.
OPERATIONAL
The copy of the primary of a mirrored pair to
secondary is complete, and the primary to
secondary devices are synchronized.
optional-text
The state of the original; one of the following:
PENDING
Mirrored operation is starting or restarting. The
primary and secondary devices are not yet
synchronized.
ORIGINAL ON PRIMARY
The original device address is on the primary
device address (no mapping to the primary
device).
ORIGINAL NOT ON PRIMARY
The original device address is not the primary
device address. The controller is mapping to
the primary device.
FAILED
The mirrored pair has been terminated from
the PENDING or OPERATIONAL state.
ssid
The ssid of the primary of the mirrored pair.
Note: The optional text is present if the state of the dual

copy pair is FAILED or SUSPENDED.
Operator Response: The various formats of the
IEA495I message will be broadcast to all systems
where the primary device of the dual copy pair is
attached and online. Follow your installations
This message is intended to supplement message
IEAD475E which will only be issued on one console of
a multiple system complex where the dual copy devices
are attached to more than one of the systems.
Automation programs that monitor operator messages
may want to monitor for the occurrence of these
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
associated with this message is attached via the
IBM3990 Model 3 or Model 6 Storage Control Unit, see
the IBM 3990/9390 Operations and Recovery Guide for
detailed recovery actions.
ca The two-byte channel connection address or the

primary device of the mirrored pair.
Operator Response: The various formats of the
IEA496I message will be issued when the system
detects a change of state for an online primary device
of a mirrored pair. Follow your installations procedures
for reporting this error.
Note: Automation programs that monitor operator
messages may want to monitor for the occurrence of
these messages to assist with decisions concerning the
availability of critical data.
IEA500A

IEA496I
dev, volser, MIRRORING state,

SSID=ssid, CCA=ca
RESTART INTERRUPT DURING

{jobname stepname|UNKNOWN
JOBNAME} ASID=aaaa MODE=mmmm
PSW=psw REPLY RESUME TO
RESUME INTERRUPTED PROGRAM
REPLY ABEND TO ABEND
INTERRUPTED PROGRAM [PREVIOUS
REPLY WAS INVALID, ENTER A VALID
REPLY]
Explanation: The state of the mirrored pair has

changed.
Explanation: When the operator caused a restart

interruption, the specified job was in progress. The
message asks the operator to resume the job that was
in progress or end it.
dev
jobname
The device number of the primary device of a
mirrored pair.
The name of the job that the system was

currently processing.
607
stepname
The name of the step that the system was
currently processing or blanks.
UNKNOWN JOBNAME
The system could not identify the current job.
ASID=aaaa
The address space identifier (ASID)
MODE=mmmm
The system was processing one of the
following units of work:
TASK
A task
SRB
A service request
WAIT
The system wait task
A unit of work other than those listed

above
[NO BATCH JOBS OR TIME SHARING USERS

FOUND | RECOMMEND YOU DISPLAY ACTIVE AND
DISPLAY QUEUES]
The system found no batch jobs or time sharing
users. However, there may be started tasks in the
system.
IEE125A. The system waits for the operator to reply to
message IEE125A. Then the system begins restart
processing.
Operator Response: Reply to message IEE125A.
Depending on the message text, one of the following:
[WRITE-TO-OPERATOR BUFFER LIMIT EXCEEDED.
ISSUE K M,MLIM COMMAND TO RAISE LIMIT]
Enter the CONTROL M,REF command to display
the limit. Enter the CONTROL M,MLIM=nnnn
command to raise the limit.

a reply.
[NO BATCH JOBS OR TIME SHARING USERS

FOUND | RECOMMEND YOU DISPLAY ACTIVE AND
DISPLAY QUEUES]
Enter the DISPLAY ACTIVE and/or the DISPLAY
QUEUE command to determine if the system is
holding a job queue.
Operator Response: Reply one of the following:
Source: Loadwait/Restart
RESUME
The job that was in progress continues at the
next sequential instruction.
Detecting Module: IEAVEREX
PSW=psw
The program status word (PSW) at the time of
the restart interruption
IEA502A
ABEND
The system ends the job with abend X'071'.
IEA501I
SYSTEM NON-DISPATCHABILITY
INDICATOR [IS OFF | WAS ON, IS NOW
BEING RESET] [WRITE-TO-OPERATOR
BUFFER LIMIT EXCEEDED. ISSUE K
M,MLIM COMMAND TO RAISE LIMIT]
[NO BATCH JOBS OR TIME SHARING
USERS FOUND RECOMMEND YOU
DISPLAY ACTIVE AND DISPLAY
QUEUES]
Explanation: The operator caused a restart

interruption, specifying REASON 1. This message
displays the results of the diagnostics that the system
performs in response to the restart interruption.
SYSTEM NON-DISPATCHABILITY INDICATOR [IS
OFF | WAS ON, IS NOW BEING RESET]
If the non-dispatchability indicator is on, the system
sets it off and marks all address spaces as
dispatchable.
[WRITE-TO-OPERATOR BUFFER LIMIT EXCEEDED.
ISSUE K M,MLIM COMMAND TO RAISE LIMIT]
The write to operator (WTO) message buffer is full.
608
RESTART REASON COULD NOT BE

OBTAINED. REPLY WITH RESTART
REASON CODE:
Explanation:
0 - ABEND CURRENT PROGRAM
1 - PERFORM MVS SYSTEM DIAGNOSTICS
[PREVIOUS REPLY WAS INVALID, ENTER A VALID
REPLY]
Following a restart interruption, the system could not
obtain the restart reason code from the service
processor.
System Action: The system issues message IEA501I.
The system waits for the operator to reply.
Operator Response: Reply one of the following:
0
The system responds with message IEA500A,

which allows you to abnormally end the current
program.
The system checks and repairs critical data

areas.
IEA503W
MULTIPLE CPUS FAILED DURING ETR

SYNC-CHECK PROCESSING.
Explanation: At least two processors could not

complete External Time Reference (ETR)
synchronization check processing. A hardware failure
occurred. ETR is the MVS generic name for the IBM
wait state X'0A4'.
wait state X'0A4'.
programmer response for wait state X'0A4'.
Detecting Module: IEATESCH, IEATESC2
IEA504I
CONSOLxx HARDCOPY DEVICE dddd

NOT ACCEPTED. OPERLOG IS
ACCEPTED. REASON=reason-code
Explanation: The hardcopy console specified in the

CONSOLxx parmlib member is not valid. Because the
operations log was also specified, it will receive the
hardcopy message set.

IEA510A
LNKLST PROCESSING IS
INOPERATIVE, HIT ENTER TO
CONTINUE WITH THE DEFAULT
LNKLST OR RE-IPL THE SYSTEM

detected unrecoverable errors during the initialization of
the LNKLST function. The LNKLST function cannot
operate because of the errors. In most cases, the
system an accompanying diagnostic message identifies
the specific type of error.
System Action: NIP does not initialize the LNKLST
function. Initialization processing waits for your
response.
about this message and any accompanying diagnostic
message. To continue initialization with the default
LNKLST, press ENTER. Otherwise, IPL the system
again.
Application Programmer Response: To correct the
condition that caused the problem, respond to the
accompanying diagnostic message, then reIPL the
system.
xx
The suffix of the CONSOLxx parmlib

member.
dddd
The device number of the console.
reason-code

1
dddd is not a console. The

CONSOLE statement
defining the device as a
console might be missing.
dddd is not a valid device

number.
dddd is a display console. A

display console cannot be
used as a hardcopy device.
System Action: The system ignores the request for a

hardcopy console and continues processing. The
system logs messages to the operations log only.
system initialization, ensure the following:
v The device number is the same in both the I/O
definition file (IODF) and the CONSOLE statement in
IEA512W
h.IODFxx IS NOT VALID. SUFFIX

RANGE IS 00 THRU FF.
Explanation: The specified input/output definition file

(IODF) suffix is not a valid hexadecimal number.
The high level qualifier of the IODF data set

name (DSN).
xx
The suffix of the IODF DSN.
System Action: The system ends initialization. The

system enters nonrestartable wait state X'0B1' with
reason code X'008'.
programmer response for wait state X'0B1'.
IEA513W
DATASET NOT FOUND ON DEVICE

dev: dsname
v The device type is the same in both the IODF and

the CONSOLE statement in the CONSOLxx parmlib
member.
Explanation: The system cannot find a data set name

because one of the following conditions exists:
v A hardcopy device is defined as a console (not a

display console) in CONSOLxx.
v The wrong LOADxx suffix was entered in the load

frame parameter
v The device number is incorrect
609
dev
The device number.
dsname
The data set name. It is one of the following:

reason code X'003'.
v SYS1.PARMLIB
v h.IODFxx, where h is the high level qualifier.
Detecting Module: IOSIOFR

reason code X'001'.
v If the data set name is SYS1.PARMLIB, correct the
IPL device number or enter the correct device
number for the parmlib member in the IPL load
parameter.
v If the data set name is h.IODFxx, enter the correct
LOADxx suffix in the in the IPL load parameter.
If the data set name is not one of the above, notify the
system programmer.
programmer response for wait state X'0B1' with reason
code X'001'.
IEA516W
MODIFY SUBCHANNEL FAILED FOR

DEVICE NUMBER dev
Explanation: During system initialization, the Modify

Subchannel (MSCH) instruction failed while the system
was trying to enable a device.
dev
The device number.
reason code X'004'.

IEA517W
IEA514W
MORE THAN ONE EXTENT FOR

dsname
Explanation: A data set in the LOADxx parmlib

member occupies more than one extent.
dsname
The data set name.
reason code X'002'.

found an incorrect I/O definition file (IODF) data set
name in the LOADxx parmlib member.
reason code X'005' or X'00A'.
IEA518W

IEA515W
DEVICE NUMBER dev NOT DEFINED

TO THE CHANNEL SUBSYSTEM

could not find a subchannel for the device that contains
the parmlib member.
dev
The device number.
IODF IS NOT VALID FOR AN IPL
CONFIGURATION ID xxxxxxxx NOT

FOUND IN IODF.

could not find the configuration identifier from the
LOADxx parmlib member in the I/O definition file
(IODF).
xxxxxxxx
The configuration identifier.
reason code X'006'.
610
num
The number of devices.

IEA519I
IODF DSN = dsname

system does not recognize any devices of the specified
device type.
Explanation: This message identifies the I/O definition

file (IODF) data set name.

dsname

The data set name.

System Programmer Response: If the IODF data set
name is incorrect, enter the correct name in the
LOADxx parmlib member. Then ask the operator to
reIPL the system.
IEA520I
CONFIGURATION ID = xxxxxxxx. IODF

DEVICE NUMBER = dev
Explanation: This message identifies the configuration

identifier and the I/O definition file (IODF) device
number.
IEA522I
UIM modname DID NOT BUILD A DFT

FOR DEVICE NUMBER dev
Explanation: A unit information module (UIM) did not

build a device features table (DFT) for the specified
device number. The device type is not supported by the
system level.
modname
The name of the UIM.
dev
The device number.
system does not recognize the device types defined by
the UIM.
xxxxxxxx
The configuration identifier.

dev
The device number.

Operator Response: If the IODF device number is
incorrect, enter the correct IODF device number in the
IPL load parameter. Then reIPL the system. If the
problem persists, contact the system programmer.
System Programmer Response: If the configuration
identifier is incorrect, enter a different configuration
identifier in the LOADxx parmlib member. Then ask the
operator to reIPL the system.
IEA521I
devtype DEVICE TYPE NOT

RECOGNIZED (num DEVICES)
Explanation: The system could not find a valid unit

information module (UIM) for the specified device type.
devtype
The device type.

IEA523W
NO DEVICES DEFINED
Explanation: The system cannot recognize any of the

devices defined in the I/O definition file (IODF). This
error occurred for one of the following reasons:
v The IODF does not contain any devices defined to
the system.
v The unit information modules (UIM) supporting these
devices are not present.
System Action: System initialization ends. The system
enters nonrestartable wait state X'0B2'.
IEA525W
UIM modname SPECIFIED UNDEFINED

DEVICE NUMBER dev
Explanation: A user interaction module (UIM) asked to

use the device class extension of the unit control block
(UCB) for a device. The system did not build a UCB for
611
that device because of a logic error in the UIM.
IEA540I
modname
The unit information module (UIM).
dev
The device number.
taskname TASK FAILED - RESTART

ATTEMPT IN PROGRESS.
Explanation: taskname is one of the following:

ADDRESS SPACE TERMINATION
DUMP
RECORD
System Action: System initialization ends. The system

enters nonrestartable wait state X'0B4'.
One of the permanent tasks in the recovery termination

manager (RTM) failed.


The RTM address space failed.
Detecting Module: IOSIUCB

IEA526I
SYSNAME SYSTEM PARAMETER

INVALID

initialization program (NIP) found an incorrect
SYSNAME parameter. The incorrect SYSNAME
parameter was specified in either an IEASYSxx or
IEASYMxx parmlib member or by the operator in
response to message IEA101A.
to prompt the operator for a reply.
Operator Response: Enter SYSNAME=sysname,
where sysname is a valid system name, in reply to
message IEA527A.
SYSNAME system parameter in the IEASYSxx or
IEASYMxx parmlib member used to IPL the system.
IEA527A
SPECIFY REQUIRED SYSNAME

PARAMETER. SYSNAME=

name in the SYSNAME parameter is incorrect or
missing.
the correct SYSNAME.
Operator Response: Enter SYSNAME=sysname,
where sysname is one to eight characters, each of
which is a alphanumeric or national character. The
name that is chosen should uniquely identify the system
that is being IPLed.
DUMP
The RTM dump task failed.
RECORD
The RTM recording task failed.
v If the task was not attempting to restart when it failed,
RTM issues this message. RTM attempts to restart
the task.
v If the task was attempting to restart, RTM also issues
message IEA541E. RTM does not try to restart the
task.
Detecting Module: IEAVTMS1
IEA541E
taskname TASK FAILED DURING

RESTART ATTEMPT.

DUMP
RECORD
manager (RTM) failed. This task had failed previously
and was attempting to restart when a second error
occurred.
DUMP
RECORD
System Programmer Response: Add or correct the

SYSNAME parameter in the IEASYSxx or IEASYMxx
parmlib member used to IPL the system.
System Action: The system does not try to restart the

task. The tasks function will not be available until the
system is initialized again.
Operator Response: ReIPL the system.
612
Detecting Module: IEAVTMSI

IEA542I
taskname TASK RESTART COMPLETED

SUCCESSFULLY.

DUMP
RECORD
manager (RTM) failed, but restarted itself.
DUMP
RECORD
System Action: The task is now available for
processing.
Detecting Module: IEAVTSDT, IEAVTMTC,
IEAVTR2S, IEAVTRET
IEA544I
EXTERNAL INTERRUPT IGNORED. [NO

FULL CAPABILITY CONSOLES
DEFINED OR] MASTER CONSOLE WAS
VARIED OFFLINE.
Explanation: The system did not process an external

interrupt.
NO FULL CAPABILITY CONSOLES DEFINED
No full capability consoles are defined in the
MASTER CONSOLE WAS VARIED OFFLINE
The master console was varied offline.
System Action: The system assigns the specified
name to the console. The system continues processing.
IEA545W

INOPERATIVE MESSAGE IEA367A
COULD NOT BE DISPLAYED ERROR
CODE = cccc
Explanation: Multiple console support (MCS) is

inoperative. The system tried to display message
IEA367A, but failed.
cccc
The error code. It is the same as would have

been displayed in message IEA367A.
System Action: The system enters restartable wait

state X'202'.
wait state X'202'.
programmer response for wait state X'202'. See
message IEA367A for a description of error codes.
IEA546E
NO FULL CAPABILITY MCS

CONSOLES, REASON=xxxx TO
RESTORE MASTER CONSOLE: PRESS
THE ENTER KEY ON ANY AVAILABLE
FULL CAPABILITY CONSOLE AND
PRESS THE EXTERNAL INTERRUPT
KEY OR ISSUE VARY CONSOLE OR
CONTROL V COMMAND TO RESTORE
A FULL CAPABILITY CONSOLE.
Explanation: Console switch processing results in loss

of all the full capability multiple console support (MCS)
consoles. The failing consoles undelivered (UD)
messages will be re-routed to consoles with the UD
attribute or a console with master authority. The system
will send other messages to the hard-copy log.
REASON=xxxx
Communications task (COMMTASK)

lost all the full capability MCS
consoles. xxxx is one of the following:
EXT
The operator pressed the

external interrupt key.
IOER
An I/O error occurred on the

failing console.
SWER A software error occurred for

the failing console.
VMST
The operator entered the

VARY MSTCONS command.
OPER
An open failure occurred for

the console.
CF CHP
The operator entered a
CONFIG CHP command.
CQEER
CQE error for a console.
SFAIL
A system in the sysplex

failed.

Consoles with the UD attribute or the system console
receive the failing consoles undelivered messages. If
613
there are no other consoles with the UD attribute

(including the hard-copy log), the system sends the
failing consoles UD messages to the system console.
The system sends all other messages to the hard-copy
log.
name to the console. The system continues processing.
IEA554I
v If there are active consoles with the UD attribute but

there is no MCS console with master authority, you
may restore master console authority to a console or
do nothing.
Explanation: The system is delaying message

processing because of errors.
v If both the MCS console with master authority and

consoles with the UD attribute are not active, you
may restore master console authority to a console or
activate a console with the UD attribute. If you do not
do so, the system will send undeliverable action
messages, write to operator with reply messages
(WTOR) and messages with descriptor code 12 to
The hard-copy log, if directed to the hard-copy log
The system console
Detecting Module: IEAVSWCB, IEAVSWCR
IEA548W
NIP CONSOLE UNAVAILABLE.

INITIALIZATION CANNOT PROCEED.
FAILING MESSAGE: text
Explanation: During initialization, a console was not

available. The system must issue a write to operator
with reply (WTOR) or emergency message.
text
The first 8 lines of the message which could

not be delivered.

CONSOLE DELAYED SVC
PROCESSING SUSPENDED. RESTART
{PENDING | SUCCESSFUL}

PENDING
The restart is pending.
SUCCESSFUL
The restart was successful.
System Action: The system tries to restart message
processing. If SUCCESSFUL appears in the message
text, the restart was successful.
IEA555E
CONSOLE DELAYED SVC

PROCESSING ABORTED. RESTART
UNSUCCESSFUL
Explanation: The system is delaying message

processing because of errors.
System Action: The system does not display
branch-entered write to operator with reply (WTOR)
messages. The system storage may become filled with
messages waiting to be issued.
Operator Response: ReIPL the system when it is
convenient.

wait state X'A70'.
Operator Response: ReIPL when the system console

is available.
IEA557A

Explanation: An authorized program issued a write to

operator with reply (WTOR) message while access to a
global reply identifier pool was restricted. Another
program is using reply identifier 0.

IEA549I
SYSTEM CONSOLE FUNCTIONS

AVAILABLE SYSTEM CONSOLE NAME
ASSIGNED consname
Explanation: The system initialized the system

console as an extended console. The console is now
available for message and command processing.
consname
The name the system assigns to the system
console.
System Action: The system assigns the specified
614
MULTIPLE REQUESTORS FOR REPLY

ID 0, REPLY TO ID 0 ON sysname
sysname
The name of the system on which the
authorized program is running.
System Action: The program that issued the WTOR
waits until a reply identifier becomes available.
Operator Response: Reply to the WTOR as soon as
possible.
IEA590I
WTO USER EXIT text

exit-name ABENDED
IEAVMXIT ABENDED
IEAVMXIT NOT FOUND
IEAVMXIT NOT LOADED - NO STORAGE
AVAILABLE
An error occurred during the initialization or running of a
WTO installation exit routine.
exit-name ABENDED
The WTO installation exit abnormally ended. The
system marked it as nonexecutable.
IEAVMXIT ABENDED
Enter the CONTROL M,UEXIT=N command to
delete the erroneous IEAVMXIT routine, then enter
the CONTROL M,UEXIT=Y command to activate
the corrected IEAVMXIT routine.
IEAVMXIT NOT FOUND
Place the installation exit routine, IEAVMXIT, in a
system library in the LNKLST concatenation.
AVAILABLE
Increase the storage in the common service area
(CSA) by changing the CSA specification in the
SYSP parameter. Then reenter the CONTROL M
command to activate the installation exit.
Detecting Module: IEAVVINT, IEAVX600
exit-name
The name of the installation exit.
IEA598I
IEAVMXIT ABENDED
The general WTO installation exit routine
abnormally ended. The system marked it as
nonexecutable.
IEAVMXIT NOT FOUND
The system could not load installation exit routine
IEAVMXIT from any system library.
AVAILABLE
Storage was requested for the general WTO
installation routine IEAVMXIT, but the storage was
not available.
TIME ZONE = d.hh.mm.ss
Explanation: This message displays the time zone,

which is the difference between local time and
Greenwich mean time (GMT).
The location of the time zone in relation to

GMT, as follows:
E
A time zone east of GMT.
A time zone west of GMT.
hh.mm.ss
The difference in hours (00-15), minutes
(00-59), and seconds (00-59) from GMT.
System Action: The system action is one of the

following:
exit-name ABENDED
The system abnormally ends user exit exit-name.
System Programmer Response: If the time zone

value is unacceptable, specify a different value in the
CLOCKxx parmlib member.
IEAVMXIT ABENDED
The system abnormally ends installation exit
IEAVMXIT.
IEAVMXIT NOT FOUND
The system does not process the CONTROL M
command.

IEA599I
CLOCKxx LINE nnnn: text STMT

IGNORED. UNRECOGNIZED PARM.

AVAILABLE
The system does not process the CONTROL M
command.
Explanation: A statement in a CLOCKxx parmlib

member contains an incorrect parameter.
CLOCKxx

error messages as follows:
nnnn
The line number in the CLOCKxx parmlib

member that contains the ignored statement.
text
The statement that contains the incorrect

parameter.
exit-name ABENDED
Enter the SET MPF=NO command to remove the
erroneous exit routine, then enter the SET MPF
command to invoke a correct WTO installation exit.
615

IEA906A.
CLOCKxx

you press the enter button on the console, the system
sets the following defaults:
nnnn

member that contains the duplicate statement.
text
The duplicate statement.
v The system does not prompt the operator during

time-of-day (TOD) initialization.
v The system sets the local time equal to the
System Programmer Response: Check for
misspelled parameters in the CLOCKxx parmlib member
from the specified keyword to the end.
System Action: The system ignores the duplicate

statement. The system continues processing.
duplicate statement from CLOCKxx

IEA600I
CLOCKxx LINE nnnn: TIMEZONE STMT

IGNORED. VALUE NOT VALID.
Explanation: A TIMEZONE statement in the CLOCKxx

parmlib member contains an incorrect specification:
v The syntax of the statement is incorrect
v The value is outside the correct range (00.00.00 15.00.00 hours).
CLOCKxx
nnnn

member that contains the ignored statement.
IEA602I
ADDRESS SPACE CREATE FAILED.

text
Explanation: A request to create a new address

space could not be honored because of an error or a
resource limitation.
text
THE GETMAIN FOR THE ASCB FAILED
Storage could not be obtained from SQA for
the new address spaces ASCB or ASSB.
MAXUSERS WOULD HAVE BEEN EXCEEDED
The maximum number of allowable address
spaces as specified in the MAXUSER
parameter in the IEASYSxx parmlib member.

IEA906A.
ADDRESS SPACE SERVICES FAILED

Address space services suffered an error
which prevented the address space creation.

you press the enter button on the console, the system
sets the following defaults:
A STORAGE SHORTAGE EXISTS

There is insufficient SQA, pageable storage, or
auxiliary storage available.
v The system does not prompt the operator during

time-of-day (TOD) initialization.
v The system sets the local time equal to the
misspelled parameters in the CLOCKxx parmlib
member. Ensure that the value for TIMEZONE is within
the valid range (00:00:00 - 15:00:00).
IEA601I
CLOCKxx LINE nnnn: DUPLICATE text

STMT IGNORED
Explanation: A statement in the CLOCKxx parmlib

member is a duplicate.
616
AN UNEXPECTED ERROR OCCURRED

An unexpected error occurred which prevented
the address space creation.
System Action: The system was unable to create the
requested new address space. The system continues
processing without the new address space.
Operator Response: Notify the System Programmer.
System Programmer Response: Resolve the
resource shortage if the problem is a shortage of SQA,
auxiliary storage, or MAXUSERs. For the unexpected
error cases, check the logrec data set for an error
record or retry the request.
Detecting Module: IEAVEMRQ
NO UCBS BUILT FOR nnnnn 4-DIGIT

DEVICES FOUND IN THE IODF
IEA603I
IEA611I
Explanation: Initial program load (IPL) completed

successfully but the system has encountered nnnnn
4-digit devices.
text
DUMPID=dumpid REQUESTED BY JOB (jobname)
FOR ASIDS(id,id,...)
[REMOTE DUMPS REQUESTED|
REMOTE DUMP FOR SYSNAME: sysname]
INCIDENT TOKEN: incident-token
[SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz]
[reason-text]
[ERRORID = SEQ yyyyyy CPUzz ASIDasid
TIMEhh.mm.ss.t] [TSOID = tsoid]
[ID = uuuuuuuuuu]
nnnnn
The number of 4-digit devices encountered.
System Action: Processing continues. No UCBs are

built for the nnnnn 4-digit devices.
IEA607E
v Give control to the post dump installation exit routine

v Process a dump request
v Process a DUMPDS operator command
SYS1.DUMPnn data sets that were added are no longer
allocated for dumps. These data sets could contain SVC
dumps; do not delete these dump data sets.
no SVC dumping capability.
Operator Response: ReIPL the system to reinitialize
and restart the dumping services address space.
Detecting Module: IEAVTSDR
IEA607I
The system wrote a complete or partial SVC dump to

an automatically allocated dump data set on a direct
access storage device. In the message text:
THE DUMPSRV ADDRESS SPACE HAS

FAILED AND CANNOT RESTART
Explanation: Errors occurred in dumping services,

which processes SVC dumps. The dumping services
address space (DUMPSRV) has ended several times in
succession. Dumping services cannot do the following:
THE DUMPSRV ADDRESS SPACE HAS

FAILED AND IS RESTARTING
Explanation: Errors occurred in dumping services,

which processes SVC dumps. The dumping services
address space (DUMPSRV) is ending. Dumping
services is running but cannot do the following:
System Action: The system restarts the dumping
services address space. When the restart is complete,
complete dump processing is available again.
Detecting Module: IEAVTSDR
{COMPLETE|PARTIAL} DUMP ON
dsname
|
|
COMPLETE
The SVC dump contains all of the virtual storage
that was requested.
|
|
|
|
|
|
|
PARTIAL
Not all of the virtual storage requested was
collected. However, enough storage may have
been dumped to allow the debugging of the
problem to be successful. The codes in the SDRSN
field can be used to determine what storage was
effected, or what problems were encountered while
SVC dump processing was executing.
dsname
The dump was written to the data set named
dsname.
dumpid
The 3-character dump identifier.
jobname
The name of the job that requested the dump.
id
The address space identifiers (ASID), in

hexadecimal, for the address spaces included in
the dump.
REMOTE DUMPS REQUESTED

The SDUMPX macro or DUMP command that
requested this dump also requested dumps on
other systems in the sysplex.
REMOTE DUMP FOR SYSNAME: sysname
This dump was requested by sysname, which is
another system in the sysplex.
The formatted incident token for the dump.
SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz
The system wrote only a partial dump.
vvvvvvvv
Partial dump reason code. One of the
following:
80000000
A system request block (SRB) for the
dump could not be scheduled to the
617
requested address space. Either no

current address space had the requested
ASID or the system was ending the
address space with that ASID.
40000000
SVC dump processing could not obtain
real storage manager (RSM) serialization
because of a hierarchy problem.
20000000
SVC dump processing could not obtain
RSM serialization because of a RSM
control problem.
10000000
SVC dump processing could not obtain a
central storage buffer from the real storage
manager.
08000000
An error in scheduled SVC dump
processing caused recovery to receive
control.
80000000 | 40000000
While processing SVC X33, the system
detected an error and gave recovery
control.
20000000
The system detected an error in the SVC
dump task and gave recovery control.
10000000
The SVC dump task failed.
08000000
The system detected an error while writing
a trace table. The system could not write
the trace table.
04000000 | 02000000
While processing an SVC dump, the
system detected an error and gave
recovery control.
04000000
An error in summary dump processing
caused recovery to receive control.
01000000
The started dump task failed.
02000000
An error in summary dump processing or
suspend summary dump processing
caused recovery to receive control.
00800000
A task abnormally ended, and SVC dump
processing took a partial dump. The
resource manager for SVC dump
processing receives control.
00400000
An error caused the loss of the summary
dump.
00200000
During suspend summary dump
processing, the virtual storage buffer filled
up.
00100000
No more summary dump data could be
written because the central storage buffer
was full.
00080000
While the system was writing a trace table,
an error occurred. The trace table could
not be written.
wwwwwwww
following:
618
hung address space, dump processing

obtained only fixed storage for the address
space.
00400000
The system detected an error in the SVC
dump writing task and gave recovery
control.
00200000
An address space involved in the dump
abnormally ended, and SVC dump took a
partial dump. The resource manager for
SVC dump processing receives control.
00100000
The DUMPSRV address space abnormally
ended, and SVC dump processing took a
partial dump. The resource manager for
SVC dump processing receives control.
00080000
While processing the dump header, the
system ran out of space to place data.
00010000
During dump processing of a possibly
hung address space, the address was
found to be invalid. The dump data may
not be consistent.
00040000
During dump processing of local storage,
the system issued a PURGEDQ because
a hung address space was detected. This
will result in the loss of some storage
related to the address space.
00020000
00020000
hung address space, dump processing

obtained only fixed storage for the address
space.
00010000
hung address space, the address space
was found to be invalid. The dump data
may not be consistent.
xxxxxxxx
following:
80000000
While building the address range table for
global storage areas, SVC dump
processing filled the table and remaining
entries could not be added.
40000000
While building the address range table for
local storage areas, SVC dump processing
filled the table and remaining entries could
not be added.
20000000
While building the address range table,
SVC dump processing filled the table and
remaining entries could not be added.
10000000
While dump processing was writing to the
dump data set, an I/O error occurred.
08000000
The dump data set is full, but more data
needs to be dumped.
04000000
An error occurred while writing the
summary dump.
02000000
An error occurred while dump processing
was obtaining trace data.
01000000
While dump processing was setting up the
service request block (SRB) under which
the dump was to be processed, an error
occurred.
00800000
An error occurred in an exit routine.
00400000
An error occurred while writing the
end-of-data record to the dump data set.
00200000
Some read-only ranges of data could not
be added to the range table.
00100000
While dump processing was copying
global storage into a data space, an error
occurred.
00080000
While dump processing was copying a
sub-range of common storage into a data
space, an error occurred.
00040000
An error occurred in the processing of data
spaces that were requested through the
LISTD keyword on the SDUMPX macro, or
through the DSPNAME parameter on the
DUMP command.
00020000
Dump processing could not add some
ranges of read/write storage to the range
table.
00010000
SVC dump processing truncated the dump
because the maximum amount of space
was been reached.
00008000
While processing the SQA SDATA option,
the system filled in the range table.
00004000
While processing the CSA SDATA option,
Remaining entries could not be added.
00002000
While processing global subpools, the
system filled in the range table. Remaining
00001000
While processing the LSQA SDATA option,
00000800
While processing the RGN SDATA option,
00000400
While processing private subpools, the
system filled in the range table. Remaining
00000200
While processing the SWA SDATA option,
00000100
While copying global data into a data
space, dump processing was unable to
capture some ranges of global storage.
619
00000080
An exit data space could not be created,
or the data space was created but an
ALET could not be obtained to access the
data space.
00000040
A summary data space could not be
created, or the data space was created but
an ALET could not be obtained to access
the data space.
00000020
A local data space could not be created, or
the data space was created but an ALET
could not be obtained to access the data
space.
00000010
A global data space could not be created,
or the data space was created but an
ALET could not be obtained to access the
data space.
00000008
SVC dump could not create or could not
use the data spaces that are required to
process the STRLIST request. Some data
will not be included in the dump.
00000001
because a critical shortage of auxiliary
storage existed. See the information for
message IRA201E to determine how to
relieve the shortage.
zzzzzzzz
following:
Bits in the first byte indicate a result that
occurred because one or more of the
following conditions may exista. there is a shortage of central storage b.
there is a shortage of auxiliary storage c.
the DUMPSRV address space dispatching
priority is too low
80000000
Dump processing had reset the system
dispatchable and dump processing failed
or ended, leaving the system set
non-dispatchable. dump was lost.
40000000
Dump processing had reset the tasks
dispatchable in one or more address
spaces involved in the SVC dump. Then
dump processing failed or ended, leaving
the tasks non-dispatchable.
20000000
Dump processing reset the callers unit of
work, which was stopped as part of
suspend summary dump processing. Then
620
dump processing failed during suspend

summary dump processing, leaving the
caller suspended.
10000000
IEAVTSDB released serialization for all
serialized structures specified in the
STRLIST because SDUMP appears to
have failed or ended.
08000000
The central storage buffer containing the
summary dump was released when it was
determined that dump processing was
hung. The summary dump was lost.
00800000
Facility not available. Some structures will
not be dumped.
00400000
The structure is not available for one of
the following reasons:
v The system detected a structure failure
and the structure cannot be accessed
v The structure is not allocated
00200000
No facility dump space is allocated or no
facility dump space is available because it
is being used to hold structure dump
tables for other structure dumps
00100000
Possible error in STRLIST parameter list
for one of the following reasons:
v The structure does not exist in the
active policy
v The structure type is not compatible
with the specified range options
v A lock structure was requested. SDUMP
does not support lock structures
00080000
Some or all of the STRLIST could not be
processed
00040000
The system released structure dump
serialization before capturing all the data.
The system captured the rest of the data
after releasing serialization.
00020000
Recovery received control while
processing STRLIST
00010000
SVC dump was unable to continue
processing a structure requested in the
STRLIST parameter list. This may be
because the operator deleted the structure
dump with the SETXCF FORCE
command.
00008000
Recovery received control while building
the SDUMP signals for other systems in
the sysplex
SOME STORAGE COULD NOT BE DUMPED

RC=rc
Storage could not be dumped. rc can be one of
the following:
reason-text
SUMMARY DUMP INFORMATION WAS LOST
A problem arose where processing was unable
to complete a requested summary dump. Refer
to the description of the SDRSN bits that are
set to determine whether the data was
truncated, or completely lost.
A CRITICAL AUXILIARY STORAGE SHORTAGE
EXISTED
because a critical shortage of auxiliary storage
existed. See message IRA201E to determine
how to relieve the shortage.
DUMP DATA SET FULL - DUMP ENDED WHILE
WRITING
{SUMDUMP|GLOBAL|LOCAL|STRLIST}
The dump data set is full, but more data needs
to be dumped. The message indicates at what
point the data set became full.
I/O ERROR - NO EOF WRITTEN - DUMP ENDED
WHILE WRITING
An I/O error occurred while the system was
writing to the dump data set. The message
indicates the system was dumping at the time
of the I/O error.
MAXSPACE LIMIT REACHED WHILE
CAPTURING DUMP
Insufficient space was available to capture the
complete dump. See the MAXSPACE
parameter of the CHNGDUMP SET,SDUMP
command in OS/390 MVS System Commands.
ERROR OCCURRED IN AN SDUMP EXIT
ERROR OCCURRED IN AN SDUMP LOCAL EXIT
ERROR OCCURRED IN AN SDUMP GLOBAL
EXIT
ERROR OCCURRED IN AN SDUMP EARLY
GLOBAL EXIT
ERROR OCCURRED IN AN SDUMP
ONE-TIME-ONLY EXIT
ERROR OCCURRED IN AN SDUMP DYNAMIC
LOCAL EXIT
ERROR OCCURRED IN AN SDUMP DYNAMIC
GLOBAL EXIT
Dump processing encountered an unexpected
error in an SDUMP exit of the specified type.
04
The system could not find the

requested ASIDs.
08
Not all of the data requested in a

summary dump could be contained in
the central storage buffer or virtual
storage buffer.
|
|
|
|
|
|
|
|
|
|
|
|
Note: Even though some summary

dump records may be missing,
IEA611I COMPLETE DUMP
will be issued when there are
no other data truncation reason
bits set. This indicates that the
dump contains all of the virtual
storage requested. Only the
summary dump records are
missing, and these are usually
duplicated in the virtual storage
dumped at a slightly later time.
12
Either (1) the internal SVC dump

control blocks are full, so that some
data was not dumped, or (2) dump
processing received an error return
code when it tried to dump the system
trace.
16
SVC dump was not able to process all

of the structures specified in the
STRLIST parameter list.
20
SDUMP processing could not collect

the local storage of at least one of the
normally collected storage address
spaces involved in the dump. Refer to
the description of the SDRSN bits that
are set for more information.
SYSTEM RESET DISPATCHABLE PRIOR TO

DUMP COMPLETION
Dump processing failed or ended with the
system set non-dispatchable. The system
detected the error and reset dispatchable.
TASKS RESET DISPATCHABLE PRIOR TO
DUMP COMPLETION
Dump processing failed or ended with tasks set
non-dispatchable in one or more address
spaces involved in the SVC dump. The system
detected the error and reset the tasks
dispatchable.
ENABLED CALLER RESET PRIOR TO DUMP
COMPLETION
Dump processing failed or ended during
suspend summary dump processing, leaving
the caller suspended. The system detected the
error and reset the callers unit of work.
621
STRUCTURE DUMP SERIALIZATION RELEASED

PRIOR TO DUMP COMPLETION
The SVC dump time disabled interruption exit
routine released dumping serialization that was
held for a structure requested in the STRLIST
parameter list. Serialization was released
because:
v The routine had detected that SVC dump
processing was not continuing normally or
had ended and left the structure serialized.
v ACCESSTIME=ENFORCE was specified on
the dump request (or defaulted) and the
data requested in the STRLIST parameter
list for a requested structure was not
completely processed within the time limit
specified by the ACCESSTIME parameter on
the IXLCONN macro.
ERROR OCCURRED IN SDUMP
Dump processing encountered an unexpected
error.
ERRORID = SEQyyyyyy CPUzz ASIDasid
TIMEhh.mm.ss.t
The error identifier.
yyyyyy
The sequence number
zz
The central processor address
asid
The ASID for the address space

in which the error occurred
hh.mm.ss.t
The time in hours (00 through

23), in minutes (00 through 59), in
seconds (00 through 59), and in
tenths of a second (0 through 9).
TSOID = tsoid
The dump was generated for a SLIP trap that was
set in a Time Sharing Option (TSO) session.
tsoid
The identifier of the TSO user who defined

the trap.
ID = uuuuuuuuuu
The component or subsystem identifier that was
supplied in the ID keyword on the SDUMP or
SDUMPX macro.
Operator Response: Notify the system programmer;
identify the dsname of the dump.
System Programmer Response: Take the
appropriate action as indicated in the following
descriptions:
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:
622
v
v
v
v
v
Logrec error records

CHNGDUMP option settings
DUMPDS status
The partial SVC Dump
Dump data set information

WHILE WRITING
Look at the logrec error records to determine the
device problem. Contact hardware support.
Format the partial dump. If a previous dump was in
the dump data set, the data set may contain a
combination of the two dumps.
Obtain the logrec error record. Search the problem
reporting data bases for a fix for the problem. If no
fix exists, notify the IBM Support Center. Provide
the logrec error record.
SOME STORAGE COULD NOT BE DUMPED RC=16
Refer to the description of the SDRSN bits that are
set. Use the IPCS Sub-Command STRDATA to
format the list of structures that was requested to
be dumped. The reason that the structures were
not completely processed will be displayed.
Source: SVC dump
Detecting Module: IEAVTSDC
IEA630I
OPERATOR opername NOW ACTIVE,

SYSTEM=sysname, LU=unitname
Explanation: Multiple console support (MCS) activated

an operator on a Time Sharing Option Extensions
(TSO/E) terminal.
opername
The userid or console name of the TSO/E
operator.
sysname
The name of the system to which the operator
logged on. The system name is specified on
the SYSNAME parameter in the IEASYSxx
parmlib member.
unitname
The logical unit name. This name identifies the
physical location of the terminal that the TSO/E
operator used to logon to the system.
IEA631I
OPERATOR opername NOW INACTIVE,

SYSTEM=sysname, LU=unitname
Explanation: An operator on a Time Sharing Option

Extensions (TSO/E) terminal became inactive.
opername
The userid or console name of the TSO/E
operator.
sysname
The name of the system to which the operator
logged on. The system name is the value of
the SYSNAME parameter in the IEASYSxx
parmlib member.
unitname
The logical unit name. This name identifies the
physical location of the terminal that the TSO/E
operator used to logon to the system.
IEA650I
SYSPLEX DUMP DIRECTORY ENTRY

NOT PROCESSED
Explanation: Because of a failure, the system could

not automatically add a source description for an SVC
dump to the sysplex dump directory. The cause of the
failure could be that:
v The sysplex dump directory was full.
v A sysplex dump directory had not been created.
v The sysplex dump directory was not specified.
v The sysplex dump directory was continually in use.
v The SYSDDIR statement in the BLSCUSER parmlib
has not been processed.
System Action: The source description for the dump
is not added to the sysplex dump directory. Other
processing continues. The system will re-try the addition
later.
causes listed in the explanation and correct the
problem.
Source: SVC dump
Detecting Module: IEAVTSST
IEA651E
SYSPLEX DUMP DIRECTORY

PROCESSING TERMINATED
Explanation: Because of a failure, the system could

not automatically add a source description for an SVC
dump to the sysplex dump directory. This is the tenth
failure. The cause of the failures could be that:
v The sysplex dump directory was full.
v A sysplex dump directory had not been created.
v The sysplex dump directory was not specified.
v The sysplex dump directory was continually in use.
v The SYSDDIR statement in the BLSCUSER parmlib

has not been processed.
System Action: The system disables the function to
add source descriptions for SVC dumps to the sysplex
dump directory. The system deletes the outstanding
requests to add source descriptions; no new requests
will be created.
causes listed in the explanation and correct the
problem. Then cancel the DUMPSRV address space.
When the DUMPSRV address space restarts, the add
function is again enabled.
Source: SVC dump
Detecting Module: DSE
IEA652A
WTO STORAGE EXHAUSTED - WTOS

WILL BE DISCARDED
Explanation: Outstanding WTO messages have used

all of the available buffer space. Some WTOs will be
discarded.
System Action: The system processes only WTO
messages that might be critical to relieving the buffer
shortage, such as responses to the D C,B and D R
commands. All other WTO messages are discarded.
Discarded messages are not sent to the console, the
hardcopy log, the message exits, the SSI, or the joblog.
Commands issued while WTO storage is exhausted are
executed, but command response messages are not
displayed or logged except for responses to D C,B and
D R commands.
JES3 monitors some command responses to update
status for devices and jobs. Because these command
responses are not issued JES3 is unable to process the
status changes. When buffer space becomes available,
the system issues message IEA655I.
Operator Response: Examine the output from the D
C,B command. Based on the information displayed:
v If a console has accumulated a large number of
messages, do one of the following:
Use the CONTROL Q command to reroute the
messages
Use the CONTROL E command to delete
messages
Use the CONTROL S command to put the
console into roll mode and allow messages to roll
off the screen
Use the VARY CN command to deactivate the
console.
v If an address space has accumulated a large number
of messages notify the system programmer.
v If a large number of messages have arrived from
another system then diagnose the problem on the
system sending the messages.
623
v If a large number of messages are waiting for

delivery to another system, then try to relieve the
buffer shortage on the target system.
sysname2
The name of the system that cannot sent
messages to system sysname1.
System Programmer Response: If an address space

has accumulated a large number of messages, follow
the response for message IEA099A. Otherwise, follow
the system programmer response for message
IEA404A.
System Action: System sysname2 holds messages

for system sysname1 until either:
v The WTO buffer shortage is relieved on system
sysname1
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.

IEA653I
JOBNAME= jobname ASID= asid HAS

REACHED nn% OF THE WTO BUFFER
LIMIT
Explanation: The job named in the message has used

nn% of the limit of WTO buffers as determined by the
value of MLIM in the CONSOLxx parmlib member. nn%
is a percentage that is high enough to suggest a
possible problem.
System Programmer Response: Follow the system

programmer response for message IEA404A to reduce
the probability of a WTO buffer shortage on system
sysname2.
Source: Communications Tack (COMMTASK)
IEA655I
jobname
The name of the job that is using a large
percentage of the WTO message buffers.
asid
The ASID of the named job.
WTOS NO LONGER BEING

DISCARDED - nnnnnnnn MESSAGES
WERE LOST WHILE WTO STORAGE
WAS EXHAUSTED
Explanation: The WTO storage shortage is less

severe, and messages are no longer being discarded.
This message only goes to the hardcopy log.
nn.
the percent of the maximum number of WTO
buffers used by the specified job.
Application Programmer Response: If your program
is in a WTO loop, correct the program. Consider
modifying the program so that it uses the
MSGFLAG=BUSYEXIT parameter so that the system
will return control to the program when the WTO buffer
limit is reached.
System Programmer Response: Follow the response
for message IEA099A.
nnnnnnnn
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
WTOs.
Source: Communications Task (COMMTASK),
IEA705I
Source: Communications Tack (COMMTASK)

IEA654A
WTO BUFFER SHORTAGE ON SYSTEM

sysname1 IS AFFECTING MESSAGES
ON SYSTEM sysname2
Explanation: System sysname2 cannot send

messages to system sysname1 because system
sysname1 is experiencing a WTO buffer shortage.
sysname1
The name of the system that is experiencing a
WTO buffer shortage.
624
ERROR DURING
{GETMAIN|FREEMAIN}, SYS CODE=
cde-rc {jobname|aaa} stepname fb
w1w2w3w4w5w6
Explanation: The system found an error when

processing a GETMAIN, FREEMAIN, or STORAGE
macro.
cde
The abend code.
rc
The reason code.
jobname
The name of the job that was running

when the error occurred.
aaa
The return address of the calling

routine. This field appears if the entry
to GETMAIN or FREEMAIN was not

through system linkage.
stepname
The name of the step that was

running when the error occurred.
(Attention: If this message was issued
while running under the MSTR
subsystem, this field may contain
residual information and require
verification against the ASCB and
TCB information provided).
fb
The flag byte, which indicates how the

system entered GETMAIN or
FREEMAIN. fb is one of the following:
00
Dxx
08
In the table:
a
The current address space control block

(ASCB) address.
The dispatched task control block (TCB)

address.
The input TCB address.
The first two bytes are the subpool identifier

requested. The third byte contains request
flags, as follows:
System linkage was used.

The GETMAIN or FREEMAIN
was entered through one of
the following:
v A Supervisor Call (SVC)
instruction generated by
the GETMAIN or
FREEMAIN macro
v A Program Call (PC)
instruction generated by a
STORAGE macro
80
04
GETMAIN or FREEMAIN
was entered through a
Branch instruction generated
by a GETMAIN or
FREEMAIN macro.
w1w2w3w4w5w6
Variable data, in hexadecimal. The
data depends on the abend code and
reason code in the message text, as
follows:
1... ....
The access list entry table (ALET)

was specified on the STORAGE
macro.
.1.. ....
Storage may be backed above or

below 16 megabytes.
..1. ....
Virtual storage may be above 16

megabytes.
...1 ....
Virtual storage may be below 16

megabytes.
.... 1...
Request is variable-length.
.... .1..
Storage should be on page boundary.
.... ..1.
Request is unconditional.
.... ...1
Request is a FREEMAIN or
STORAGE RELEASE.
The 4th byte is zero.

e
The address of the parameter list supplied by

the caller.
The length of the area requested for

GETMAIN, FREEMAIN, or STORAGE.
The starting address of the area to be freed.
The address of the virtual storage manager

(VSM) work area.
The address specified on the INADDR

parameter for the GETMAIN or STORAGE
macro.
cde
rc
w1
w2
w3
w4
w5
w6
1xx
all
2xx
all
3xx
all
4xx
all
5xx
all
6xx
all
7xx
all
8xx
4-14
18,20 a
24,28 a
9xx
all
Axx
all
Bxx
4-4C a

programmer response for the accompanying abend and
reason codes.
50-54 a
System Action: The system abnormally ends the job

step.
the accompanying abend and reason codes.
625
IEA710A
LPALST FUNCTION INOPERATIVE - HIT

ENTER TO CONTINUE WITH THE
DEFAULT LPALST OR RE-IPL THE
SYSTEM
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
accompanying diagnostic message, such as IEA300I,
IEA301I, or IEA306I, describes the specific error.
System Action: The system does not initialize the
LPALST function. Initialization processing waits for your
response.
about this message and the accompanying message. To
continue system initialization with the default LPALST
concatenation, press ENTER. Otherwise, reIPL the
system.
System Programmer Response: To correct the
condition that caused the problem, respond to the
accompanying diagnostic message, then reIPL the
system to build the LPALST concatenation.
LPALSTxx INPUT TRUNCATED AFTER
dsname
IEA711E
Explanation: Too many data set names were specified

for inclusion in the LPALST concatenation. LPALSTxx is
the parmlib member from which the last data set name,
dsname, was obtained for the LPALST.
xx
Identifies the parmlib member of LPALST.
IEA712I
LPALST LIBRARY DATA SETS

IGNORED
(dsname) (text)
(dsname) (text)
.
.
.
Explanation: The data set named dsname, which was

specified in the selected LPALSTxx members of
SYS1.PARMLIB, could not be concatenated to
SYS1.LPALIB for the reason indicated in the message
text.
dsname
text
UNABLE TO LOCATE
The system could not find a catalog entry for
the data set.
UNABLE TO MOUNT
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.
UNABLE TO OPEN
An error occurred while opening the data set.
This condition will be accompanied by
message IEA211I.
UNABLE TO INCLUDE
The data extent block (DEB) for the
concatenation could not contain the number of
extents required to include the data set.
dsname
System Action: The system placed the data set

names up to dsname in the LPALST concatenation. The
system ignores the data set names after dsname.
System Programmer Response: This is probably an

installation error. Correct the condition that caused the
problem.
The nucleus initialization program (NIP) issues this

message when the concatenation is opened. LNKLST
lookaside reissues this message to ensure that it
remains on the operators screen.

an installation error. Reduce the number of data sets
specified for inclusion in LPALST. To reopen the
LPALST concatenation, run a cold start initial program
load (IPL).

IEA713I
LPALST LIBRARY CONCATENATION

(dsname) . . (dsname)
Explanation: This message lists the data sets,

dsname, concatenated to SYS1.LPALIB.
dsname
CSVLLCRE
626

IEA716I
text- member DATA SET IGNORED

library
text is one of the following:

LIBRARY NOT LOCATED
LIBRARY NOT IN APF TABLE
UNABLE TO MOUNT VOLUME
UNABLE TO OPEN LIBRARY
IEANPE5
Explanation: The system could not process a library

specified in a parmlib member.
LIBRARY NOT LOCATED
The system could not locate library library
specified in parmlib member member
LIBRARY NOT IN APF TABLE
Library library is not authorized by the
authorized program facility (APF)
UNABLE TO MOUNT VOLUME
The system could not mount the volume where
library data set, library is located
UNABLE TO OPEN LIBRARY
The system could not open the library data set,
library
member
The parmlib member where the library was
specified.
The parmlib member is one of the following:
v IEALPAxx
v IEAFIXxx
library

The name of the library data set specified in

the parmlib member, member

indicated parmlib member, but does not process library
library.
If UNABLE TO MOUNT or UNABLE TO OPEN appear
in the message text, the system issues messages
IEA211I, IEA307I, IEA311I, IEA312I, IEA314I, IEA317A,
and IEA319I explaining the error.
Detecting Module: CSVMLPRM
MAXUSER=val1, RSVNONR=val2,
RSVSTRT=val3 SUM EXCEEDS
MAXIMUM OF 32767
IEA738I
Explanation: The sum of the MAXUSER, RSVSTRT,

and RSVNONR values exceeds the allowed maximum
of 32,767. These parameters are specified in the
IEASYSxx parmlib member and are added together to
compute the size of the address space vector table
(ASVT).
val1
The value of MAXUSER in IEASYSxx
val2
The value of RSVNONR in IEASYSxx
val3
The value of RSVSTRT in IEASYSxx

respecify the three parameters by issuing message
IEA906A three times: once each for MAXUSER,
RSVNONR, and RSVSTRT.
as the system programmer directs.
v Select a smaller value for one or all of the
parameters.
v Ask the operator to respond to message IEA906A
with the new values for the parameters.
v Correct the parameters in the IEASYSxx member so
that this message will not be issued during every
system initialization using IEASYSxx.
IEA740W
SUPERVISOR UNABLE TO RECOVER

FROM SVC D LOOP
Operator Response: If UNABLE TO MOUNT appears

in the message text, mount the appropriate volume and
reIPL the system.
Explanation: While the system was processing the

Supervisor Call (SVC) instruction for an ABEND macro,
a program check occurred recursively.
See the operator response for accompanying

messages.
System Action: The system enters wait state X'104'.
System Programmer Response: If UNABLE TO

MOUNT or UNABLE TO OPEN appear in the message
text, see the system programmer response for
accompanying messages IEA211I, IEA307I, IEA311I,
IEA312I, IEA314I, IEA317A, or IEA319I.
If the problem persists, search problem reporting data

wait state X'104'.
Detecting Module: IEAVESVR
627
IEA763I
OPTIONS FOR OPERATIONS

COMPONENT TRACE ARE NOT VALID.
IEA764I

1. The OPTIONS keyword, specified on the REPLY
command in response to a TRACE
CT,ON,COMP=SYSOPS command, was entered
with incorrect options.
2. The operations component trace parmlib member
specified on a TRACE
CT,ON,COMP=SYSOPS,PARM=CTIOPSxx
command contains incorrect options on the
OPTIONS keyword.
3. The operations component trace parmlib member
specified at IPL contains incorrect options on the
OPTIONS keyword.
Valid options are:
v MESSAGES{,MSG=msgid}
v MSGDLVRY{,MSG=msgid}
v SYSPLEX
v WTO{,MSG=msgid}
v Combination of above options
System Action: If the error occurred during use of the
TRACE CT command, the command is rejected. If the
error occurred during system initialization, operations
component trace (SYSOPS) will be initialized with the
default tracing options.
v If the options were specified on the REPLY
command, re-enter the TRACE command and specify
the correct options on the REPLY command.
v If the options were contained in an operations
CTRACE parmlib member that was specified on the
PARM= keyword of the TRACE CT command, have
the system programmer correct the parmlib member.
When the parmlib member has been corrected,
re-enter the TRACE CT command.
v If this message was issued during initialization, wait
for the system initialization to complete and then
enter the DISPLAY TRACE,COMP=SYSOPS
command to display the current tracing options. If the
desired options are not in effect, enter the TRACE
CT command to change operations tracing activity as
needed. Notify the system programmer that the
parmlib member that was used contains errors.
System Programmer Response: If the incorrect
options were listed in an operations CTRACE parmlib
member, correct the parmlib member. Notify the
operator when the parmlib member has been corrected.
REQUEST TO CHANGE OPERATIONS

COMPONENT TRACE BUFFER SIZE
FAILED
Explanation: The system cannot obtain storage for

the new trace buffer size requested. One of the
following occurred:
v A TRACE CT,ON,COMP=SYSOPS command was
entered with a new buffer size in the CTRACE
parmlib member.
v A TRACE CT,nnnnK(or nnnnM),COMP=SYSOPS
command was entered.
System Action: The TRACE CT command is rejected.
The operations component trace buffer size is not
changed.
Operator Response: Either adjust the amount
specified and re-enter the TRACE CT command, or
re-enter the command later. There might have been a
temporary storage shortage.
IEA765I
CTRACE DEFINE FOR SYSOPS

FAILED, TRACING WILL BE
INITIALIZED {WITH DEFAULT PARMLIB
MEMBER | WITH NO PARMLIB
MEMBER} , RETCODE=xx,
RSNCODE=yy
Explanation: Component trace initialization by the

operations component has failed for one of two reasons:
1. A CTIOPSxx parmlib member (other than
CTIOPS00) was specified and contains errors.
2. The CTIOPS00 parmlib member was either
specified or used by default, and contains errors.
The return and reason codes are the result of a
?CTRACE DEFINE macro call and are listed in the
Services Reference ALE-DYN under CTRACE Return
and Reason Codes.
System Action: If a CTIOPSxx parmlib member other
than CTIOPS00 (the default) was specified during
initialization, the CTIOPS00 will be used to define OPS
CTRACE. If CTIOPS00 was specified (or selected by
default), OPS CTRACE will be defined using the OPS
CTRACE defaults.
System Programmer Response: Correct the currently

specified CTIOPSxx parmlib member or provide a valid
CTIOPSxx parmlib member in SYS1.PARMLIB.

628
IEA766I
CTRACE DEFINE FOR SYSOPS

FAILED, TRACING WILL NOT BE
INITIALIZED, RETCODE=xx,
RSNCODE=yy
Explanation: Component trace initialization by the

Operations component has failed when it tried to define
the Operations component trace without a parmlib
member. This case only occurs after CTIOPSxx failed
and/or CTIOPS00 failed.
The return and reason codes are the result of a
?CTRACE DEFINE macro call and are listed in the
Services Reference ALE-DYN under CTRACE Return
and Reason Codes.
System Action: OPS CTRACE is not initialized.
System Programmer Response: Search the problem
entries with newer trace entries when the operations

trace buffers filled up.
System Action: The operations component trace
continues. New trace entries continue to overlay older
trace entries. The action message will be deleted when
the condition is resolved, if the component trace
abnormally terminates.
Operator Response: This message will be deleted if a
valid TRACE CT command is issued with either the
WTRSTRAT parameter or with COMP=SYSOPS
specified.
System Programmer Response: You probably
started the operations component trace without first
connecting a trace external writer. If the trace did not
capture enough data to diagnose the problem, ask the
operator to reenter the TRACE CT command and do
one (or both) of the following:
v Increase the size of the operations component trace
(SYSOPS) trace buffers
v Start an external writer and connect operations
component trace (SYSOPS) to the external writer.
IEA767A
OPERATIONS COMPONENT TRACE

HAS WRAPPED AN ALREADY FULL
BUFFER
Explanation: The operations component trace was

started and the trace data was collected in operations
trace buffers. Operations overlaid some older trace
entries with newer trace entries when the operations
trace buffers filled up.
System Action: The operations component trace
continues. New trace entries continue to overlay older
trace entries.
System Programmer Response: You probably
started the operations component trace without first
connecting a trace external writer. If the trace did not
capture enough data to diagnose the problem, ask the
operator to reenter the TRACE CT command and do
one (or both) of the following:

IEA768I
FAILURE IN CREATING DUMPSRV

ADDRESS SPACE mc, return-code,
reason-code
Explanation: An error occurred during the creation of

the dumping services address space (DUMPSRV),
which processes SVC dumps. Dumping services is
running but cannot do the following:
mc
v Increase the size of the operations component trace

(SYSOPS) trace buffers
v Start an external writer and connect operations
component trace (SYSOPS) to the external writer.
A module code, which is one of the

following:
01
The system experienced an

error while creating the
address space.
02
The DUMPSRV address

space experienced the error.
04
A request for virtual storage

for the SDUMP virtual buffer
or the summary dump
extended work area (SMEW)
failed.

IEA767I
OPERATIONS COMPONENT TRACE

HAS WRAPPED AN ALREADY FULL
BUFFER
Explanation: The operations component trace was

started and the trace data was collected in operations
trace buffers. Operations overlaid some older trace
return-code
The return code placed in register 15

by the failing module.
reason-code
The reason code placed in register 0
629
by the failing module. When mc is 04,

the system does not put a value into
register 0.
cannot process dump requests. The system writes a
logrec data set error record.
Provide the logrec data set error record.
Detecting Module: IEAVTSAI, IEAVTSAS
does not complete ending of the address space. The

system ignores any CANCEL or FORCE operator
command to end the address space.
In most cases, the system writes a logrec data set error
record. The record contains the ASCB in the variable
recording area (VRA) of the system diagnostic work
area (SDWA).
Provide the logrec data set error record and messages.
Detecting Module: IEAVTMTC
IEA774I
SUBCHANNEL INITIALIZATION FAILED

FOR SUBCHANNEL nnnn, DEVICE
NUMBER dev
Explanation: The system tried to initialize a

subchannel for a device. The subchannel was not
operational, or busy in a state that could not be cleared.
nnnn
The subchannel identifier.
dev
The device number.
System Action: The system continues subchannel
initialization with the next sequential subchannel
number.
IEA793A
NO SVC DUMP DATA SETS AVAILABLE

FOR DUMPID=dumpid FOR JOB
(*MASTER*). USE THE DUMPDS
COMMAND OR REPLY D TO DELETE
THE CAPTURED DUMP
Explanation: The system has captured the data for

the dump but cannot locate an available dump data set
for the dump. An available dump data set is either a
SYS1.DUMPnn data set with the first record containing
an end of file, or an automatically allocated data set. If
automatic dump data set allocation is already active,
check the syslog for a previous IEE799I message for
details about the dump data set allocation failure.
dumpid A 3-character dump identifier.

System Action: SVC dump processing continues to
search for an available dump data set until one of the
following occurs:
v An available dump data set is found
IEA792I
ADDRESS SPACE asid CANNOT BE

TERMINATED - JOB [jobname]
Explanation: The system was trying to end an

address space when an error occurred.
asid
The address space identifier (ASID) of the

address space that was ending.
jobname
The name of the job that was running in the
address space. The job is one of the following:
v An initiated task
v A started task
v A mounted task
v A time sharing option (TSO) logon task
If the job name is not available, jobname does
not appear in the message.
System Action: The system removes the address
space control block (ASCB) from the end queue and
630
v The operator replies D to delete the captured dump

v The interval specified by the MSGTIME parameter on
the CHNGDUMP command expires
v Use the DUMPID on the DISPLAY DUMP command
to display the title or error information.
v Enter the DUMPDS command to clear an existing
dump data set or to add a new dump data set in
order to write the dump to a data set.
v Reply D to the message. SDUMP will delete the
captured dump.
v Run a utility to clear an existing dump data set.
v Add additional SMS classes (DUMPDS ADD,SMS=)
or DASD volumes (DMPDS ADD,VOL=) to the
automatic allocation facility, or correct the problem
which caused the automatic dump data set allocation
failure.
If a utility other than DUMPDS will be used to make a

dump data set available automatically, no response is
required. SVC dump processing periodically searches
the queue of data sets until one becomes available or
the MSGTIME interval expires.
vv The type of machine check:

IPD
Instruction processing damage
SD
System damage
IV
Invalid program status word (PSW) or

registers
TC
Time of day (TOD) clock damage
PT
CPU timer damage
Source: SVC dump

Detecting Module: IEAVTSCD
IEA794I
SVC DUMP HAS CAPTURED:

DUMPID=dumpid REQUESTED BY JOB
(*MASTER*) DUMP TITLE=dump-title
Clock comparator damage

PS
Primary sync damage
Explanation: The system has captured the data for

the SVC dump.
AD
External Time Reference (ETR)

attachment damage
SL
Switch to local
dumpid A 3-character dump identifier.

dump-title
The title of the dump, provided by the caller or
by the operator. The title can be up to 100
characters long.
System Action: The system writes the SVC dump to
the dump data set, if available, and issues message
IEA611I or IEA911E. IEA611I and IEA911E indicate:
text
v AN UNKNOWN ERROR OCCURRED.
v CPU x CHECKSTOPPED.
v CPU x REACHED ITS vv MACHINE-CHECK
THRESHOLD OF SPIN-LOOP RECOVERY
PROCESSING.
v Whether the system wrote a complete or partial dump
v CPU xs TOD CLOCK COULD NOT BE

SYNCHRONIZED.
v Which dump data set contains the dump.
v OF A MALFUNCTION IN THE DAT HARDWARE.
If no dump data set is available, the dump remains

captured and the system issues message IEA793A.
IEA793A indicates:
v That a dump has been captured but no dump data
set is available.
v The DUMPID which may be used on the DISPLAY
DUMP command.
v That the operator may use the DUMPDS command
to clear a dump or cancel a dump.
v CPU xs CLOCK COULD NOT BE

SYNCHRONIZED TO THE ETR.
v AN UNRECOVERABLE MACHINE ERROR
OCCURRED.
v PHYSICAL VARY FOR THE CPU FAILED.
v PHYSICAL STATE OF THE CPU UNKNOWN.
PHYSICAL VARY FOR THE CPU FAILED
The service processor was unable to take the
failing processor physically offline.
Detecting Module: IEAVTSCC
PHYSICAL STATE OF THE CPU UNKNOWN

The service processor request was unable to
complete. The failing processor is not physically
offline.
IEA796E
Source: SVC dump
ACR PROCESSING HAS TAKEN CPU

[AND VF] x [LOGICALLY] OFFLINE
BECAUSE text
Explanation: Alternate CPU recovery (ACR) has

successfully placed a failing processor (CPU), and
possibly the associated Vector Facility (VF), logically
and physically offline.
The processor that was taken offline.
AND VF
The associated VF was taken offline.
LOGICALLY
The processor was taken logically offline.
The system does not automatically remove this

message from the display console. The operator must
manually delete the message.
Operator Response: Delete the message from the
console with the CONTROL(K) command.
If PHYSICAL VARY FOR THE CPU FAILED or
PHYSICAL STATE OF THE CPU UNKNOWN appears
in the message text, take processor x physically offline
with the CONFIG CPU, OFFLINE command. Contact
hardware support. Provide the logrec data set error
records.
Source: Alternate CPU recovery (ACR)
631
Detecting Module: IEAVTACR, IEAVTCRE

IEA797W
{THE POINTER TO THE CURRENT FRR

STACK IS NOT VALID.| AN FRR STACK
POINTER IS DAMAGED.}
Explanation: A recovery termination manager (RTM)

first level interruption handler (FLIH) determined that an
interruption is an error. The FLIH issued a CALLRTM
macro to recover or to end the routine that caused the
error. While processing the request, RTM found
uncorrectable damage to at least one functional
recovery routine (FRR) stack pointer in the recovery
stack vector table (PSARSVT) of the prefixed save area
(PSA).
System Action: The system:
1. Issues this message.
2. Places all processors on this system in
non-restartable X'084' wait state, with reason code
X'04'.
wait state X'084'.
Detecting Module: IEAVTRTV
IEA798W
UNSUCCESSFUL RECOVERY
ATTEMPT BY RECOVERY
TERMINATION MANAGER
Explanation: The recovery termination manager

(RTM) was trying to invoke a functional recovery routine
(FRR) when a double recursive abnormal end occurred.
wait state X'084', with reason code X'08', X'0C', or X'10'.
Operator Response: If requested by the system
programmer, take a stand-alone dump.
System Programmer Response: Request the
operator to take a stand-alone dump to ensure first
failure data capture. See the system programmer
response for wait state X'084'. If the problem is not
contained in a problem reporting data base, contact the
IBM Support Center. Provide the stand-alone dump.
IEA799I
AUTOMATIC ALLOCATION OF SVC

DUMP DATA SET FAILED
DUMPID=dumpid REQUESTED BY JOB
(jobname) reason-text reason text2
Explanation: The system has captured data for a

dump with automatic allocation active, but was unable
to allocate a dump data set for the dump.
632
reason-text
The reason why the system could not automatically
allocate a dump data set, as follows:
NO RESOURCES DEFINED
Automatic allocation of dump data sets is
active, but no allocation resources are defined.
INSUFFICIENT SPACE
Automatic allocation of dump data sets is
active and allocation resources are defined, but
there was insufficient space on any of the
resources to allocate a dump data set.
DATA SET NAME NOT UNIQUE
An allocated data set could not be cataloged.
The data set has been deleted.
DYNALLOC FAILED RETURN CODE=return-code
ERROR RSN CODE=ersn INFO RSN CODE=irsn
The automatic allocation of the dump data set
failed because the dynamic allocation (SVC 99)
failed. One or more messages preceded
IEA799I further describing the error condition.
See OS/390 MVS Programming: Authorized
Assembler Services Guide for a description of
dynamic allocation return codes, error reason
codes, and information reason codes.
reason-text2
Additional information about the failure, as follows:
SMS RSN CODE=srsn, WILL TRY VOLUME
ALLOCATION
The automatic allocation failed for all storage
management subsystem (SMS) classes
specified using the SMS parameter of the
DUMPDS command. See OS/390 MVS
Guide for a description of dynamic allocation
SMS reason codes. SVC dump attempts to
allocate the data set to one of the DASD
volumes available for automatic allocation.
SMS RSN CODE=srsn
The automatic allocation failed for all storage
management subsystem (SMS) classes
specified using the SMS parameter of the
DUMPDS command. See OS/390 MVS
Guide for a description of dynamic allocation
SMS reason codes.
VOLUME ALLOCATION FAILED
The automatic allocation failed for all volumes
available to SVC dump.
System Action: SVC Dump processing will attempt to
write the dump to a SYS1.DUMP data set. If no
SYS1.DUMP data set is available, message IEA793A
will be issued.
System Programmer Response: Use DISPLAY
DUMP command to display the status of automatic
allocation resources. Use the DUMPDS command to

add allocation resources or de-activate automatic
allocation as necessary.
Source: SVC Dump
Detecting Module: IEAVTSCD
IEA802W
DAT ERROR IN SYSTEM ADDRESS

SPACE
Explanation: A dynamic address translation (DAT)

error occurred for a system address space. The
recovery termination manager (RTM) does not end the
address space because the ASCBNOMT and
ASCBNOMD fields of the address space control block
(ASCB) show that the MEMTERM option of the
CALLRTM macro is not valid for the address space.
The address space is crucial for system operation.
wait state X'A00'.
Detecting Module: IEAVTRTM
IEA806I
jjj.sss HAS BEEN TERMINATED DUE TO

AN UNCORRECTABLE I/O ERROR ON
THE PAGE DATA SET
Explanation: Because of an I/O error, the system

abnormally ended a task with abend X'028'
jjj
System Action: GTF ended trace formatting. The

system continues writing the ABEND dump. The
formatted trace output is incomplete because it does not
include the most current trace entries.
System Programmer Response: Proceed according
to the response documented for the error message or
completion code that occurred when GTF ended.
IEA809I
ERROR IN BUFFER REMAINDER OF

BUFFER IGNORED
Explanation: During formatting of the trace buffers in

the generalized trace facility (GTF) region, an incorrect
length field was discovered.
System Action: GTF does not format the remainder of
the buffer.
System Programmer Response: Obtain the SYSOUT
output for the job. Collect all printed output and output
data sets related to the problem. Search problem
IEA810E
UNCORRECTABLE I/O ERROR ON LPA

PAGE; CREATE LPA ON NEXT IPL
Explanation: An uncorrectable I/O error occurred

while attempting to page in a warm start copy of a link
pack area (LPA) page. Because the external storage for
this LPA page cannot be read, the problem will recur on
the next IPL unless a new LPA is created.
The job name.
System Action: The system abnormally ends the task

which requested paging of the LPA page.
The step name.
Operator Response: On the next IPL, create a new

LPA through the CLPA parameter when specification of
system parameters is requested.
sss
System Action: The system issues messages to the
job log about the job.
Operator Response: Repeated occurrences of this
message indicate that the page data set should be
reallocated and formatted at the next IPL.
recurs and if the program is not in error, search problem
messages in the job log, the JCL for the job, and all
problem.
IEA808I
GTF TERMINATED DURING TRACE

FORMATTING
Explanation: During formatting of the generalized

trace facility (GTF) trace buffers, GTF encountered a
severe error.
IEA811E
PAGTOTL PAGE VALUE xxx OUTSIDE

VALID RANGE
Explanation: The system does not accept the

specified total number of page data sets. It must be a
number from 0 to 256.
xxx
The total number of page data sets.

to prompt the operator to respecify the PAGTOTL
parameter, or to press the ENTER button on the
console.
Operator Response: Either respecify the PAGTOTL
values or press the ENTER button, which specifies the
default values of (5,1).
633

IEA812E
PAGTOTL VALUES INCREASED TO

(ppp,sss)
Explanation: The PAGTOTL value was less than the

actual number of page data sets that were specified
through the PAGE parameter. Therefore, the system
increases the specified PAGTOTL value.
ppp
The actual number of page data sets plus one.

using the new PAGTOTL value.
IEA813E
PAGNUM IS AN OBSOLETE
KEYWORD, PAGTOTL SHOULD BE
USED
Explanation: The system no longer recognizes the

PAGNUM keyword. PAGTOTL should be used instead.
System Action: The system determines the actual
number of page data sets specified by the PAGE
parameter. Then, the system sets default PAGTOTL
values by adding one to the actual number of page data
sets The system continues processing, using the default
PAGTOTL values.
IEA814D
DATA SET dsname DRAINING ON

PREVIOUS IPL, CONTINUE DRAINING?
REPLY YES OR NO
Explanation: On a warm start IPL, the system

determined that a data set had been draining on the
previous IPL. The operator must indicate whether the
data set is to remain draining or is to be returned to
normal system use.
dsname
reply YES or NO.
Operator Response: If the data set should remain in
draining status, reply YES and the data set remains
read-only. If the data set should be returned to normal
system use, reply NO and the data set becomes eligible
for writes.
634
IEA820I
TRANSACTION DUMP REQUESTED

BUT NOT TAKEN. reason
Explanation: The requested transaction dump was not

taken reason is one of the following:
PARAMETER LIST ADDRESS ZERO
SYSMDUMP DUMP MODE SET TO NODUMP BY
CHNGDUMP COMMAND
THE DUMP WAS SUPPRESSED BY SLIP
PARAMETER LIST ALET NOT VALID
PARAMETER LIST NOT ACCESSIBLE
PARAMETER LIST VERSION NOT VALID
PARAMETER LIST LENGTH NOT VALID FOR
VERSION
NO DCB OR DATA SET NAME SUPPLIED
BOTH DCB AND DATA SET NAME SUPPLIED
DCB ALET NOT VALID
DCB NOT ACCESSIBLE
DATA SET NAME ALET NOT VALID
DATA SET NAME NOT ACCESSIBLE
NO HEADER SUPPLIED
HEADER ALET NOT VALID
HEADER DATA NOT ACCESSIBLE
HEADER LONGER THAN 100 CHARACTERS
DUMP INDEX DSNAME ALET NOT VALID
DUMP INDEX DSNAME NOT ACCESSIBLE
DUMP INDEX DSNAME NOT VALID
SYMPTOM RECORD ALET NOT VALID
SYMPTOM RECORD DATA NOT ACCESSIBLE
SYMPTOM RECORD NOT VALID
INCIDENT TOKEN ALET NOT VALID
INCIDENT TOKEN DATA NOT ACCESSIBLE
REMOTE AREA ALET NOT VALID
REMOTE AREA DATA NOT ACCESSIBLE
REMOTE AREA NOT VALID
PROBLEM DESCRIPTION AREA ALET NOT VALID
PROBLEM DESCRIPTION AREA DATA NOT
ACCESSIBLE
PROBLEM DESCRIPTION AREA NOT VALID
STORAGE LIST ALET NOT VALID
STORAGE LIST NOT ACCESSIBLE
STORAGE LIST START ADDRESS GREATER
THAN END ADDRESS
SUBPOOL LIST ALET NOT VALID
SUBPOOL LIST DATA NOT ACCESSIBLE
SUBPOOL LIST NOT VALID
DATASPACE LIST ALET NOT VALID
DATASPACE LIST DATA NOT ACCESSIBLE
DATASPACE LIST NOT VALID
ECB ALET NOT VALID
ECB DATA NOT ACCESSIBLE
ECB NOT VALID
CALLER AUTHORIZATION INSUFFICIENT FOR
REQUESTED FUNCTIONS
DUMP DATA SET NAME NOT VALID
DUMP DATA SET NAME TOO LONG
DUMP DATA SET NAME SYMBOL SUBSTITUTION
FAILED
DATASPACE CREATION FAILED FOR AUTOMATIC
ALLOCATION
COULD NOT ACCESS DATASPACE FOR

AUTOMATIC ALLOCATION
AUTOMATIC ALLOCATION OF DUMP DATA SET
FAILED
THE DUMP WAS SUPPRESSED BY DAE
AN I/O ERROR OCCURRED
INTERNAL PROCESSING ERROR DETECTED,
REASON CODE=rsncode
Report the problem to the system programmer.

statements in the IEASVCxx parmlib member for syntax
problems.
IEA822I
rsncode
Internal processing error reason code. Will be
01
Unable to obtain storage for

transaction dump from subpool 230
below the line.
02
Unable to establish recovery

environment for IEAVTDMP.
03

above the line.
04

above the line.
05,06,07
above the line.
08
FF

above the line.
IEAVTDMPs recovery received
control.

Application Programmer Response: The message
describes the reason for which the dump was not taken.
Examine and correct the condition.
Source: IEAVTDMP
Detecting Module: IEAVTDMP
IEA821I
SYNTAX ERROR IN SVC=

PARAMETER
Explanation: Non-alphanumeric characters were

specified in the SVC parameter in the IEASVCxx
parmlib member.
respecify the SVC parameter.
Operator Response: When the system prompts for
the new SVC parameter, do one of the following:
v Respecify the parameter.
v Specify EOB (press the enter button on the console)
to proceed with the default SVC table.
{COMPLETEPARTIAL} TRANSACTION
DUMP WRITTEN [TO dsname]
Explanation: The system wrote a complete or partial

transaction dump to a data set on a direct access
storage device (DASD).
COMPLETE
The transaction dump was complete.
PARTIAL
The transaction dump was not complete.
dsname
The dump was written to the dsname data set.
System Programmer Response: Open the dump
under IPCS to view diagnostic data.
Source: IEAVTDMP
Detecting Module: IEAVTDMP
IEA823I
IEASVCxx: SVCnum: text

SYNTAX ERROR AT parm
UNBALANCED PARENTHESIS AT parm
TYPE t SVC CANNOT GET GLOBAL SPIN LOCK
TYPE 6 SVC CANNOT GET ANY LOCK
CANNOT REQUEST CMS LOCK WITHOUT LOCAL
LOCK
An SVC number was incorrectly specified in the
IEASVCxx parmlib member.
xx
The suffix of the IEASVCxx parmlib member
num
The SVC number that was incorrectly specified
text
Describes the error. text is one of the following:

SYNTAX ERROR AT parm
Where parm is a character string in the
SVCnum specification.
UNBALANCED PARENTHESIS AT parm
Where parm is a keyword specification.
TYPE t SVC CANNOT GET GLOBAL SPIN
LOCK
Where t is the SVC type specification.
635
TYPE 6 SVC CANNOT GET ANY LOCK

A type 6 SVC cannot request any locks,
but it did.
CANNOT REQUEST CMS LOCK WITHOUT
LOCAL LOCK
An SVC cannot request the cross memory
services (CMS) lock without first obtaining
the local lock, but an SVC tried to do this.
System Action: The system ignores the statement.
problems.
IEA824I
IEASVCxx: SVCnum: DUPLICATE parm

KEYWORD.

IEA826I
IEASVCxx: SVCnum: TYPE t ROUTINE

name NOT FOUND.
Explanation: The entry point address could not be

found for a module specified with user type t and SVC
number num in the IEASVCxx parmlib member. The
load module name is missing from the nucleus or the
link pack area (LPA).
xx
num
The SVC number specified
The user type specified
name
The module name for which the entry point

address could not be found
Explanation: A keyword option appears more than

once on a single statement in the IEASVCxx parmlib
member for an SVC number.
v Check the statements in the IEASVCxx parmlib

member for syntax problems.
System Programmer Response: Do one or both of

the following:
xx
num
The SVC number
v Determine why the load module is missing from the

nucleus or the LPA.
parm
The parameter for which the keyword option

was specified more than once

problems.
Detecting Module: IEAVNP25, IEAVNPS5

IEA828I
IEASVCxx: PARSE ERROR,

STATEMENT nnnn.
Explanation: The system parser encountered an error

while processing the SVCPARM specifications in a
statement in the IEASVCxx parmlib member.
IEA825I
IEASVCxx: STATEMENT nnnn : NO

VALID parm SPECIFICATION.
Explanation: A required keyword parameter is missing

or unidentifiable on a statement in the IEASVCxx
parmlib member.
xx
nnnn
The statement number in the IEASVCxx

parmlib member with the missing or incorrect
keyword parameter
parm
The keyword parameter that is missing or

incorrect

problems.
636
xx
nnnn
The statement number in the IEASVCxx

parmlib member where the system parser
encountered an error

System Programmer Response: Check statement
number nnnn in the IEASVCxx parmlib member for
syntax problems.
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
(SVC) request, but the system could not find the module
in either the nucleus (NUC) or link pack area (LPA).
parm
num
The program product or access method SVC

number
aaa
The program product or access method that

appeared to be installed
bbb
The module needed for the specified SVC

request that was not found
ccc

LPA for the link pack area
NUC for the nucleus
System Action: The system does not update the SVC

table entry for this SVC. The system will abnormally end
any program trying to use this SVC.
System Programmer Response: Check to see if the
specified product is installed, or should be.
v If it is installed, check that it is installed correctly.
v If it is not installed but should be, install it.
Detecting Module: IEAVNPST
IEA830I
IEASVCxx: DUPLICATE UPDATES TO

SVCnum IGNORED.
The parameter for which an incorrect value

was specified

problems.
IEA833I
IEASVCxx: STATEMENT nnnn: num IS

NOT A VALID SVCNUM.
Explanation: An SVC number, specified on a

SVCPARM statement in the IEASVCxx parmlib member,
is outside the range for installation-provided SVC
numbers. Valid values are 200 through 255.
xx
nnnn
The statement number on which the incorrect

SVC number was specified
num
The incorrect SVC number
System Programmer Response: Upon completion of

the initial program load (IPL), the system will not contain
an SVC instruction for the incorrect SVCPARM
statement. Before the next IPL, check the SVCPARM
problems.
xx
num
The SVC number for which there two or more

statements
Explanation: One or more IEASVCxx parmlib

members contain two or more SVCPARM statements
for the same SVC number.
PAGE DATA SET dsname NOT

ALLOCATED - ERROR CODE err
INFORMATION CODE xxxx
System Action: The system uses the first correct

SVCPARM statement and ignores any duplicate
statements.
IEA836I
System Programmer Response: Remove duplicate

SVCPARM statements for the same SVC number from
the IEASVCxx parmlib members.
Explanation: A request to allocate a page data set

resulted in an error.
dsname

IEA832I
IEASVCxx: SVCnum: pval IS NOT A

VALID parm.
Explanation: A parameter specified on a statement in

an IEASVCxx parmlib member is not valid.
xx
num
The SVC number for which an incorrect

parameter was specified
pval
The incorrect value specified for the parameter
err
The error code.
xxxx
The information code.
System Action: One of the following, depending on

the message text:
PAGE
If the system knows from a previous IPL that the
page data set contains VIO pages that should be
used with current IPL options, the system issues
message IEA930I and continues paging
initialization.
637
All other cases

The system issues message IEA922D to let the
operator respecify the data set name before
continuing paging initialization.
yyddd
The date, in years (00 through 99) and in days of
the year (000 through 366)
System Programmer Response: Respond according

to the error code and information code in the message
text.
hh.mm.ss.t
The time, in hours (00 through 23), in minutes (00
through 59), in seconds (00 through 59), and in
tenths of a second (0 through 9)
id
symptoms
The symptoms from the dump header record for the
original abnormal end
IEA837I
DISCARD ALL PERFORMED FOR

CACHE AT dev
Explanation: The auxiliary storage manager (ASM)

issues this message when a DISCARD ALL is run for
the cache of a cached auxiliary storage subsystem.
For a cold start or a quick start, this message is strictly
informational: for the first use of the cache: ASM
initialization automatically performs a DISCARD ALL for
the cache during these starts. If more than one page
data set on the direct access storage device (DASD)
backs the cache, ASM will issue this message only for
the first data set detected.
For a warm start, this message may indicate a problem:
ASM performed the DISCARD ALL after a sense
subsystem status request to the cache indicated that a
DISCARD ALL was required. This DISCARD ALL makes
any warm start data in the cache incorrect. The warm
start will not be allowed to continue if ASM determines
that warm start data may have been lost.
dev
The device number.
System Action: The system continues operation. If

warm start data was lost, the system issues message
ILR003A to force a quick start.
The processor identifier
System Action: DAE suppresses the SYSMDUMP

dump.
Detecting Module: IEAVTSYS
IEA839I
WARM START DATA IS INVALID,

QUICK START MAY BE FORCED
Explanation: The previous initialization did not

complete. During that initialization attempt, the auxiliary
storage manager (ASM) reset a cached auxiliary
subsystem because of a bad cache. This reset makes
the cache usable, but makes the warm start data in the
cache incorrect. A local page data set that contains VIO
pages is associated with the cache.
System Action: The system stops the warm start and
forces a quick start.
System Programmer Response: If the error cannot
be resolved, search problem reporting data bases for a
Support Center.
Operator Response: Reply U to message ILR003A.

For a warm start, notify the system programmer.
System Programmer Response: For a data problem

during a warm start, search problem reporting data
IEA841E

IEA838I
SYSMDUMP SUPPRESSED AS A
DUPLICATE OF: ORIGINAL: DATE
yyddd TIME hh.mm.ss.t CPU id
(symptoms)
Explanation: Dump processing issues this message

for any SYSMDUMP ABEND dump suppressed by
dump analysis and elimination (DAE).
{PLPA|COMMON|LOCAL} DATA SET

dsname UNUSABLE DUE TO BAD
CACHE AT dev
Explanation: The page data set is on a device

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.
dsname
dev
The device number.
System Action: The system does one of the following:

For a cold start: The system issues message IEA922D.
638
In response, the operator may choose a new data set

name or reply IGNORE.
For a quick start:
v For a PLPA or local data set, the system issues
message IEA922D. In response, the operator may
choose a new PLPA or local data set name or the
IGNORE option.
v For a COMMON data set, if PLPA pages did not
overflow to the data set on the cold start associated
with this quick start, the system issues message
IEA922D. In response, the operator may choose a
new COMMON data set name or the IGNORE option.
For a COMMON data set, if PLPA pages overflowed
to the data set, the quick start cannot continue. The
system forces a cold start, issues message IEA929I,
and then issues message IEA922D. In response, the
operator may choose a new COMMON data set
name or the IGNORE option.
For a warm start:
v For a PLPA data set, the system issues message
new PLPA data set name or the IGNORE option. The
new PLPA data set must have been used on a
previous cold start; otherwise, the warm start will fail
and a cold start will be forced.
with this warm start, the system issues message
new COMMON data set name or the IGNORE option.
to the data set, the warm start cannot continue. The
and then issues message IEA922D. In response, the
operator may choose a new COMMON data set
name or the IGNORE option. The local page data set
information is not preserved.
v For a local page data set that contains VIO pages,
the warm start cannot continue. The system forces a
quick start and issues message IEA930I.
For a local page data set that contains no VIO pages,
the warm start continues. However, the data set is
not used as the local page data set for this IPL.
support.
IEA842E
{PLPA|COMMON|LOCAL} DATA SET

dsname UNUSABLE DUE TO I/O
ERROR
Explanation: During initialization of page data sets,

the auxiliary storage manager (ASM) could not use a
data set because of an I/O error while opening it.
dsname
support.
System Action and Operator Response: Depending
on the system action, the operator does one of the
following:
For a cold start: The system issues message IEA922D.
In response, choose a new data set name or the
IGNORE option.
For a quick start:
v For a PLPA or local data set, the system issues
message IEA922D. In response, choose a new PLPA
or local data set name or the IGNORE option.
v For a COMMON data set, if the PLPA pages did not
with this quick start, the system issues message
IEA922D. In response, the choose a new COMMON
data set name or the IGNORE option.
to the data set, the quick start cannot continue. The
and then issues message IEA922D. In response,
choose a new COMMON data set name or the
IGNORE option.
For a warm start:
v For a PLPA data set, the system issues message
IEA922D. In response, choose a new PLPA data set
name or the IGNORE option. The new PLPA data set
must have been used on a previous cold start;
otherwise, the warm start will fail and a cold start will
be forced.
with this warm start, the system issues message
IEA922D. In response, choose a new COMMON data
set name or the IGNORE option.
to the data set, the warm start cannot continue. The
and then issues message IEA922D. In response,
choose a new COMMON data set name or the
IGNORE option. The local page data set information
is not preserved.
v For a local page data set that contains VIO pages,
the warm start cannot continue. The system forces a
quick start and issues message IEA930I.
For a local page data set that contains no VIO pages,
the warm start continues. However, the data set is
not used as the local page data set for this IPL.
639
IEA843I
MODULE mmmmmmmm NOT FOUND
Explanation: During system initialization, a resource

initialization module (RIM) cannot find a module needed
for SNAP and ABEND dumping.

IEA848I
INSTALLATION PREDUMP EXIT,

dumpexit, MODIFIED/SUPPRESSED THE
DUMP REQUEST
mmmmmmmm
The name of the

module not found.
System Action: The system cannot load the missing

module into central storage. Therefore, the system will
not be able to write SNAP and ABEND dumps.
Operator Response: Notify the system programmer. If
requested by the system programmer, reIPL the system.
System Programmer Response: Place the module
indicated by this message into the SYS1.LPALIB data
set. Then, ask the operator to reIPL the system.
--or-NO DUMP WAS PRODUCED FOR THIS

ABEND, DUE TO SYSTEM OR
INSTALLATION REQUEST
--or-DUMP SUPPRESSED - USER NOT
AUTHORIZED BY SAF
--or--

Detecting Module: IEAVTABI
IEA846I
SYSTEM CONSOLE INTERFACE

UNSUCCESSFUL. RESTART OPTIONS
MAY NOT BE INITIALIZED ON CPU x
(yyyy)
Explanation: During nucleus initialization program

(NIP) processing, the system tried unsuccessfully to
display the restart options on the processor restart
frame. The system may have already displayed the
options.
The processor.
yyyy
A hexadecimal reason code explaining the error.
yyyy is one of the following:
DUMP SUPPRESSED - ABDUMP

SERIALIZATION DEADLOCK AVOIDED,
SVC DUMP TAKEN INSTEAD
--or-DUMP SUPPRESSED - ABDUMP
SERIALIZATION DEADLOCK AVOIDED,
SVC DUMP FAILED RC=sscc
--or-DUMP SUPPRESSED - ABDUMP MAY
NOT DUMP STORAGE FOR KEY 0-7
JOB jobname
Explanation: Depending on the message text, the
message means:
INSTALLATION PREDUMP EXIT, dumpexit,
MODIFIED/SUPPRESSED THE DUMP REQUEST
The dump was suppressed by the installation
predump exit.
0040
Service processor error.
03F0
Processor x is not installed.
04F0
Processor x is not in the configuration.
10F0
Processor x is powered off.
dumpexit
The most recent exit that requested
suppression.

Operator Response: Check the restart options display
on the restart frame on processor x. If the restart
options are displayed, no action is necessary. You can
use the options at that console.
NO DUMP WAS PRODUCED FOR THIS ABEND, DUE

TO SYSTEM OR INSTALLATION REQUEST
The system or installation requested no dump for
this abend.
If the restart options are not displayed, notify the system

programmer. You can restart the system from the
console, but the restart parameter value defaults to
REASON 0.
DUMP SUPPRESSED - USER NOT AUTHORIZED BY

SAF
The system authorization facility (SAF), resource
access control facility (RACF), or its equivalent,
determined that the caller does not have authority
to dump the program that was running at the time
of the error.

system was unable to signal the console. If necessary,
contact hardware support.
640
DUMP SUPPRESSED - ABDUMP SERIALIZATION

DEADLOCK AVOIDED, SVC DUMP TAKEN INSTEAD
ABDUMP did not produce a dump because another
task holds a critical resource. In this environment,
the task will never release the resource. An SVC
dump will be taken instead of the SYSUDUMP,
SYSMDUMP or SYSABEND dump. The dump title
will include the jobname of the abending task.
DUMP SUPPRESSED - ABDUMP SERIALIZATION
DEADLOCK AVOIDED, SVC DUMP FAILED RC=sscc
ABDUMP did not produce a dump because another
task holds a critical resource. In this environment,
the task will never release the resource. An attempt
was made to take an SVC dump, but the system
was unable to take the dump. The return code
indicates this with a value of X'08'. The reason
codes describe the specific cause. Some
applications reason codes may be:
02
04
0B
The capture phase of another SVC dump

was in progress.
The SVC dump was suppressed by a SLIP
NODUMP command.
The dump was suppressed by DAE.
Refer to OS/390 MVS Programming: Authorized

Assembler Services Reference LLA-SDU for a
complete description of the SDUMPX macro return
reason codes.
ss
The SDUMPX reason code.
cc
The SDUMPX return code.
DUMP SUPPRESSED - ABDUMP MAY NOT DUMP

STORAGE FOR KEY 0-7 JOB jobname
ABDUMP did not produce a dump because the
storage access key for the task is authorized,
between 0 and 7. The program that issued the
ABEND may still dump data via one of the following
methods:
system does not suppress needed dumps. If necessary,

change the security authority so that the application
programmer gets a needed dump.
Source: Dumping Services
IEA849I
SYSMDUMP DATA SET FULL NO DUMP

TAKEN TO dsname
Explanation: The system attempted to write a

SYSMDUMP ABEND dump to a SYS1.SYSMDPxx data
set with a disposition of SHARE. There was no
end-of-file (EOF) indicator in the first record of the data
set. The absence of an EOF indicator signals that the
data set is full; therefore, the system could not write the
SYSMDUMP. The dump is lost.
dsname
The data set to which the dump was to be
written.
System Programmer Response: Create a routine
that copies the SYSMDUMP from its data set to another
data set and writes an EOF indicator as the first record.
Because the system issues message IEA993I each time
it writes a SYSMDUMP, include the routine in the
installation exit routine for the WTO macro that issues
IEA993I.
IEA850I
FOLLOWING WILL BE PROCESSED ser

ON devtyp ccc-ccc
Explanation: This message lists all VATDEF entries

that the system encountered before the I/O error
referred to in message IEA949A. The second line
appears for each volume. In the message text:
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

areas.
devtyp
The device type
Alternately, a SLIP trap may be set to request that

an SVC dump be generated for the ABEND. Also,
the installation may allow the user to receive these
dumps by permitting the user to have READ access
to the IEAABD.DMPAKEY FACILITY as described
in the OS/390 SecureWay Security Server RACF
Security Administrators Guide.
System Action: The system suppresses the dump.
Application Programmer Response: If a dump
needed to diagnose a problem was suppressed, notify
ccc-ccc The characteristics requested for the volume,

as follows:
P/R-PUB
Permanently resident, public
P/R-PRV
Permanently resident, private
P/R-STR
Permanently resident, storage
RSV-PUB
Reserved, public
RSV-PRV
Reserved, private
641
RSV-STR
Reserved, storage
System Action: The system processes the entries
before the I/O error. The system sets attributes as
indicated, unless subsequent entries override them.
IEA851A
REPLY DEVICE ADDRESSES OR U
Explanation: This message prompts the operator for a

reply to message IEA851I.
reply.
Operator Response: If any of the volumes listed in
message IEA851I are to be mounted, enter REPLY
id,dev,dev,dev,... where each dev is a device number
for a device on which you will mount a volume. You can
optionally precede a device number with a slash (/). Any
valid direct access devices can be used, including those
that already have volumes mounted on them. Mount the
required volumes on the devices in the reply, after
message IEA860A appears.
IEA852A
REPEAT REPLY

reply.
Operator Response: Enter the reply again correctly or
enter REPLY id,U.
IEA852I
dev ADDRESS INVALID - n
Explanation: The reply to message IEA851A is

incorrect. The system issues message IEA852I for each
incorrect device in the reply, then message IEA852A. In
the message text:
dev
The device number of the device in error.
The cause of the error, as follows:
Meaning
The reply specified a duplicate device

number.
The specified device number is unknown

to the system.
The specified device contains a

permanently resident or reserved volume.
The specified device is not direct access.

parmlib member, the system found that all volumes in
the member were not mounted.
The reply specified a device type is not

needed for mounting of the requested
volumes.
ser ON devtype appears once for each unmounted

volume. In the message text:
The system could not check for a data

path to the offline device.
ser The serial number of a volume to be mounted.
No data path is available to the specified

device.
No operational data path is available to the

specified device.
The specified device is for an exposure

within a multiple exposure device
(supported pre-MVS/ESA SP 5.2), but is
not the base exposure.
10
The reply specified a device address for a

non-demountable device that was online at
IPL.
If no volumes are to be mounted, enter REPLY id,U.

IEA851I
FOLLOWING MAY BE MOUNTED ser

ON devtype
devtyp
The type of device, such as 3330, on which the
volume is to be mounted. devtyp does not specify
any special features, such as track overflow, that
may be required; the installation must select the
device that has any required special features.
IEA851A.
message IEA851A.

IEA852A.
message IEA852A.
642
IEA853A
REPLY CONT, END OR RESPECIFY.
Explanation: While reading the VATLSTxx parmlib

member, referred to in message IEA949A, the system
detected an uncorrectable I/O error.
reply.
v If no volume can be mounted (for example, there is

an error on that device), and the device is listed in
IEA860A, reply NO to message IEA893A when all
other required devices have been mounted (that is,
when the required devices are not listed on
IEA893A).
Operator Response: If the system can continue

without VATLSTxx, enter one of the following:
REPLY id,CONT
The system will try to continue processing other
specified VATLST members.
IEA855I
INVALID VATLSTxx ENTRY
Explanation: During processing of a VATLSTxx

parmlib member, the system found an incorrect entry.
REPLY id,END
If the reply is END, no more VATLST processing
will be done.
System Action: Processing continues with the

remaining VATLSTxx entries.
REPLY id,xx
If the reply is xx, VATLSTxx will be processed
before processing the remaining VATLST members.
nn is a new VATLST member.
System Programmer Response: Using IEBPTPCH,

print the VATLSTxx member. Using IEBUPDTE, correct
the incorrect entry. Note that the device type might be
valid, but it was not specified as valid during system
installation.
If necessary, reIPL the system.

IEA857W
IEA854I
ERROR READING VOLUME LABEL.
Explanation: For processing of a VATLSTxx parmlib

member, the system could not read the volume label on
a device. The device address is specified in subsequent
messages. One of the following occurred:
UNREC {H|S} ACR ERR-x-R=nn D=dd
Explanation: Alternate CPU recovery (ACR)

encountered an unrecoverable error while recovery was
in progress for another processor. ACR attempted to
recover and was unsuccessful.
v If message IEA306I precedes this message, an I/O

error occurred when reading the label.
ACR encountered a hardware error.
v The volume does not contain a standard label.
ACR encountered a software error.
v In the case of Mass Storage System (MSS) volume,

the volume serial number on the label does not
match the volume serial number requested from the
3850 MSS. This case can occur when an MSS
volume label has been clipped to a different serial
number.
An error code, which is one of the following:
System Action: For an MSS volume, the VATDEF

entry is ignored; processing continues with the
remaining VATLSTxx entries.
nn
Recovery processor identifier.
dd
Failed processor identifier.
For non-MSS volumes the system waits for the operator

to mount the correct volume, if all device addresses
specified in reply to IEA851A have not yet had volumes
mounted on them. If they have, the system does not
wait; a mount request for the desired volume must be
issued later.
Operator Response: For MSS volumes, no response
is necessary.
For non-MSS volumes:
v If the wrong volume is mounted, remove it and mount
the correct volume.
The failure occurred prior to entering

post processing.
The failure occurred during ACR post

processing.
System Action: The system attempts to write a logrec

data set error record for the failed processor.
When the error is a software error, the system places all
processors in non-restartable wait state X'051'.
When the error is a hardware error, the system places
all processors in non-restartable wait state X'052'.
Operator Response: If S appears in the message
text, see the operator response for wait state X'051'.
If H appears in the message text, see the operator
System Programmer Response: If S appears in the
643
message text, see the system programmer response for

wait state X'051'.
If H appears in the message text, see the system
Detecting Module: IEAVTCR1
IEA858E
ACR COMPLETE CPU [AND VF] NOW

OFFLINE [PHYSICAL VARY FAILED]
Explanation: A failing processor was placed logically

offline by alternate CPU recovery (ACR).
IEA860A
dev,dev,... REPLY U WHEN ALL

DEVICES ARE READY.
Explanation: To complete processing of the

VATLSTxx parmlib member, the operator must mount
volumes. In the message text:
dev
The device number for a device needing a volume.
AND VF
The associated VF was taken offline.
PHYSICAL VARY FAILED
The service processor tried unsuccessfully to
vary the failing processor physically offline or
the physical vary function is not supported by
the service processor.
The system does not automatically remove this
message from the display console. The operator must
manually delete the message.
Operator Response: Delete the message from the
console with the CONTROL(K) command.
If this ACR was initiated by an earlier response to the
excessive spin-loop message IEE331A, enter the
CONFIG command to configure CPU x back online.
If PHYSICAL VARY FAILED appears in the message
text, take processor x physically offline with the
CONFIG CPU, OFFLINE command.
Contact hardware support. Provide the logrec data set
error record.
Detecting Module: IEAVTACR
IEA859I
If no volume can be mounted on this unit, reply NO to

message IEA893A when all other required devices have
been mounted, that is, when the required devices are
not listed in message IEA893A.
UNREQUESTED VOLUME. UNIT dev

NOW UNLOADED.
Explanation: A volume was mounted on a unit

specified by the operator in response to message
IEA851A. No entry exists in the VATLSTxx parmlib
member for the device. In the message text:
dev
The device number.

mount the volumes, then to reply.
Operator Response: Mount volumes, as listed in
message IEA851I, on these devices. When the devices
are ready, REPLY U.
IEA861A
VAL=xx NOT FOUND. REPLY U OR

CORRECT VALUE
Explanation: The VAL parameter in the IEASYSxx

parmlib member specified a suffix for a VATLSTxx
parmlib member. The system could not find in
SYS1.PARMLIB a VATLSTxx member with that suffix. In
the message text:
VAL=xx
The specified suffix.
reply.
Operator Response: If an error was made in the reply
to message IEA101A, enter REPLY id,nn where nn is a
correct value.
Enter REPLY id,U to ignore this VATLSTxx and continue
processing any other specified members. Use
IEBPTPCH to list the members of SYS1.PARMLIB.
IEA862I
RCT INITIALIZATION FAILED
Explanation: A START, MOUNT, or LOGON command

requested the creation or initialization of an address
space. The region control task (RCT) could not process
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

message IEA851A on this unit. Reply U to message
IEA893A when the device is ready.
v RCT was unable to attach started task control (STC).
644
v RCT was unable to establish a recovery environment.

System Action: The system abends the partially
created address space and writes a logrec data set

error record. The system may write an SVC dump.
incorrect parameters in the parmlib member before the

next IPL.
v If the installation uses the System Modification

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.
v If the installation makes any changes to the system
without using SMP, run the LIST service aid with a
LISTIDR control statement to list all load modules
with maintenance changes or local modifications. Run
LIST against the following Libraries:
SYS1.LINKLIB
SYS1.LPALIB
SYS1.SVCLIB
Library containing the program that issued the
message.
If the problem persists, search problem reporting data
the IBM Support Center. Provide:
v The logrec data set error record
v The SVC dump, if available
v The linkage editor output
Source: Region control task (RCT)
Detecting Module: IEAVAR00
IEA863I
dddddddddddddddd SPECIFICATION
INVALID IN {COMMNDxx|IEACMD00}
Explanation: During master scheduler initialization,

the system detected one of the following errors:
v The system found a parameter other than the COM
parameter.
v The value of a COM parameter is incorrect.
This is probably an error in the parameter.
dddddddddddddddd
16 characters of data from the erroneous record in
the parmlib member.
COMMNDxx
The COMMNDxx parmlib member in which the
error occurred.
IEACMD00
The error was found in the IEACMD00 parmlib
member.
COM parameter and continues processing the parmlib
member.
parameters in the parmlib member. Respecify any

IEA864I
GETMAIN FAILED FOR

{COMMNDxx|IEACMD00} - cmd
Explanation: During master scheduler initialization,

the system processed a command contained in a
parmlib member. The processing requested virtual
storage for the system queue area (SQA). The request
failed because there is not enough storage available.
COMMNDxx
The COMMNDxx parmlib member in which the
error occurred.
IEACMD00
The command was in the IEACMD00 parmlib
member.
cmd
The command.
system does the following:
IEACMD00
The system tries to process the COMMNDxx
parmlib members.
COMMNDxx
The system does not process any COMMNDxx
parmlib members.
1. Make sure that sufficient SQA storage is available
for system initialization.
2. If the problem continues, search problem reporting
IEA865I
SYSTEM ERROR DURING NIP

PROCESSING OF prm PARAMETER IPL TERMINATED
Explanation: A system error was detected while

processing the parameter indicated. The error was
detected while attempting to prompt for the parameter
and could mean that processing modules have been
overlaid or some necessary data destroyed.
prm
The parameter indicated.
System Action: The system will enter disabled wait
645
state X'03D' displayed in the wait state program status

word (PSW).
Operator Response: Dump central storage and notify
the system programmer of this message. Then reIPL
the system.
IEA866I
VOLUME ser ON dev REQUIRED ON A

{devtyp|dev1}

parmlib member, the system found the volume specified
in a VATDEF entry mounted on a device different from
the specified device type. In the message text:
ser The volume serial number specified in the VATDEF

entry.
dev
specified volume is mounted.
devtype
The device type specified in the VATDEF entry.
dev1
The device number of the device specified in the
VATDEF entry.
System Action: If the volume is not premounted, the
system unloads it. If the volume is premounted, the
system issues message IEA947A.
device if dev is listed in message IEA860A, or if all

devices listed in message IEA860A have not become
ready. If the device was in the reply to message
IEA851A, the volume must have a serial number listed
in message IEA851A.
IEA872I
INVALID IPS IN IEAIPSxx
Explanation: Processing for system resources

manager (SRM) initialization found incorrect installation
performance specification (IPS) data in the IEAIPSxx
parmlib member.
IEAIPSxx
The parmlib member, where xx is the suffix of
the member used.
System Action: The system ignores all IPS data in
this member. The system writes message IEA906A to
ask the operator to respecify the IPS parameter.
Diagnostic messages are written to the hardcopy log.
Operator Response: Write the hardcopy log (when it
becomes available), correct the errors, then use the
SET IPS commands to begin using the corrected IPS.
In response to IEA906A, specify another valid IEAIPSxx
member or specify EOB (press ENTER) to continue
system initialization.
System Programmer Response: Write the hardcopy
log (when it becomes available) to see which diagnostic
messages have been written. Correct the IPS
parameters in the IEAIPSxx member.
Operator Response: If the volume is unloaded, mount

the correct volume on the device type or device
indicated.
If the IEAIPSxx member was correct, search problem

exists, contact the IBM Support Center. Provide a listing
of the IEAIPSxx member.
Source: System resources manager (SRM)
IEA867I
DUPLICATE VOLUME ser. UNIT dev

NOW UNLOADED.
Explanation: In a VATLSTxx parmlib member, a

VATDEF entry specified a volume serial number that
duplicates the serial number of a volume already
mounted. In the message text:
ser The duplicate volume serial number.

dev
IEA873I
SKELETON IPS IN CONTROL - ALL

USERS AT SAME LEVEL

found an error in the specified IEAIPSxx parmlib
member. To continue operation, the system is using the
skeleton installation performance specification (IPS).
The valid performance group numbers are 1 and 2. The
system makes no distinction in the performance given to
problems in different performance groups.

volume was mounted.
System Action: The system writes messages about

the problem and continues processing.
System Action: The system unloaded the volume on

device dev.

Use the SET IPS command to specify a valid IPS that
supersedes the skeleton IPS.
Operator Response: Mount a different volume on the
646

IEAIPSxx parmlib member.
IEAVTSSD
The system writes no summary dumps.
If the IEAIPSxx member was correct, search problem

of the IEAIPSxx member.
IEAVTSDR
The system does not process memory ends for
SVC dump recovery.

IEA874I
INVALID OPT IN IEAOPTxx

manager (SRM) initialization found an incorrect
parameter value in the IEAOPTxx parmlib member.
IEAOPTxx
the member used.
System Action: The system ignores all OPT data in
the member. The system writes message IEA906A to
ask the operator to respecify the OPT parameter.
Operator Response: In response to IEA906A, specify
another valid IEAOPTxx member or specify EOB (press
ENTER) to continue system initialization.
System Programmer Response: Correct the OPT
parameters in the IEAOPTxx member.
If the IEAOPTxx member was correct, search problem
of the IEAOPTxx member.
IEA883I
MODULE mmmmmmmm NOT FOUND
Explanation: During system initialization, SVC dump

initialization processing cannot find a module in the link
pack area (LPA), nucleus, or SYS1.LINKLIB system
library.
mmmmmmmm
The name of the module that cannot be found.
System Action: The system continues initialization.
SVC dumping is impaired.
If mmmmmmmm has the following values, system
action is the following:
IGC005A
IEAVTSPR
IEAVTSDT
The system writes no SVC dumps.
IEAVTSSV
The system writes no suspend summary dumps.
IEAVTSXT
The system does not give control to the installation
exits for SVC dumps.
ISGDSDMP
exits for SVC dump.
IEAVTSEP
exits after SVC dumps.
IARQDUMP
The system may dump excessive amounts of virtual
storage.
The module name can be for an installation-provided
post dump exit routine, if the exit name is specified in
IEAVTSEP and the routine is not in SYS1.LINKLIB.
this message. If requested by the system programmer,
reIPL the system.
System Programmer Response: Place the missing
modules in the appropriate system library. Ask the
operator to reIPL the system to establish full SVC
dumping.
Detecting Module: IEAVTSDI, IEAVTDSV
IEA884I
PARAMETERS INVALID FOR

SYS1.PARMLIB MEMBER
mmmmmmmm
Explanation: During system initialization, the parmlib

member that specifies installation options for an ABEND
dump contained incorrect parameters.
mmmmmmmm
The name of the parmlib member, which is one of
the following:
IEAABD00
The installation options for SYSABEND dumps
are not valid.
IEADMP00
The installation options for SYSUDUMP dumps
are not valid.
IEADMR00
The installation options for SYSMDUMP dumps
are not valid.
647

v If this message is followed by message IEA885I, the
parmlib member contains correct and incorrect
parameters. The system uses the correct options.
v If this message is not followed by message IEA885I,
all options were incorrect. The system uses none of
the options.
System Programmer Response: Correct the parmlib
member before the next system initialization.
ss
The second (00-59).
Note: The apostrophes in the above reply are optional.

If you include GMT in your reply, the system
converts the time and date to Greenwich mean
time. If you omit GMT, the system assumes the
values are the local time and date, converts them
to Greenwich mean time values, and sets the
clock(s) with the Greenwich mean time.
Detecting Module: IEAVRTOD

IEA885I
IEA888A
VALID OPTIONS FOR SYS1.PARMLIB

MEMBER mmmmmmmm SDATA=
op,op,...,op PDATA= op,op,...,op
Explanation: During system initialization, the parmlib

member that specifies installation options for an ABEND
dump contained incorrect parameters.
[GMT
DATE=yyyy.ddd,CLOCK=hh.mm.ss]
LOCAL
DATE=yyyy.ddd,CLOCK=hh.mm.ss
REPLY U, OR GMT/LOCAL TIME
Explanation: This message displays the following:

v The local time and date
v The Greenwich mean time (GMT) and date
mmmmmmmm
The name of the parmlib member.
op An SDATA or PDATA option.
System Action: The system uses the correct dump
options. The system ignores the incorrect options.
yyyy.ddd
The year (4 digit year: 1900 - 2042) and the
day (001-366).
hh.mm.ss
(00-59).
System Programmer Response: Correct the parmlib

member before the next system initialization.

a reply.

IEA886A
TOD CLOCK(S) MUST BE SET
Explanation: The operator did not set the time-of-day

(TOD) clock(s).
a reply. When you enter a valid reply to message
IEA886A, the system issues message IEA903A.
Operator Response: Use the following form of the
REPLY command to set the time of day clock.
R id,DATE=[yyyy.ddd[,CLOCK=hh.mm.ss][,GMT]
In the command text:
id
The reply identifier.
yyyy
The year (4 digit year: 1900 - 2042).
ddd
The day (001-366).
hh
The hour (00-23).
mm
The minute (00-59).
648
Note: The system automatically issues message

IEA888A at IPL time if TOD=PROMPT is
included in the active CLOCKxx member of
SYS1.PARMLIB. See the OS/390 MVS
Initialization and Tuning Reference for details.
Operator Response: If the values shown in the text of
message IEA888A are acceptable, reply U. If you want
to change the value of the time-of-day (TOD) clock,
enter a new date, time, or both as follows:
R id,[DATE=yyyy.ddd][,CLOCK=hh.mm.ss],GMT
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]
Note: The apostrophes in the above replies are
optional.
If you specify a different TOD clock setting, the system
issues message IEA903A. If you omit GMT, the the
system assumes the local date and/or time. Once you
have set the new time and/or date, the system reissues
message IEA888A with new values. Reply to the
message as previously described.
Notes:
IEA890I
1. Resetting GMT time causes the TOD clock to be

reset. It also affects the local time. Respecifying
GMT time causes the local time value to be
recalculated using the new GMT and the system
time zone constant.
2. Resetting local time does not affect GMT time or the
TOD clock. However, it will cause the system time
zone constant (which is initialized at IPL from the
CLOCKxx member of SYS1.PARMLIB) to be
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
that both GMT and local time values are incorrect,
always reset the GMT values first.
3. The TOD clock should be set to a value based on
zero being equivalent to 00 hours, 00 minutes, 00
seconds on January 1, 1900 GMT. During an IPL,
the TOD clock might contain a value that, relative to
this base, is not correct. This can happen, for
example, when a customer engineer (CE) left the
clock in the error state. In this case, to ensure that
the local time and date are correct, specify GMT
before setting the local time and date.
IEA889A
REPLY U THEN DEPRESS TOD CLOCK

SECURITY SWITCH
Explanation: The time-of-day (TOD) clocks must be

synchronized because one of the following occurred:
v A processor was varied online.
v A timing facilities damage machine check occurred.
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
seconds, or if the operator presses the switch and
releases it before synchronization is complete, the
system issues message IEA889A again.
v Enter REPLY xx,U to acknowledge that you received
this message.
v Press the security switch and hold it down for 5 to 10
seconds.
comnd FAILED- MEMORY COULD NOT

BE CREATED
Explanation: comnd is one of the following:

LOGON
MOUNT
START
The system tried to create or initialize an address space
for a command, but failed. The failure may be caused
by system overload or lack of paging space.
comnd
The command for which the system tried to create
or initialize an address space. comnd is one of the
following:
LOGON
MOUNT
START
System Action: The system deletes the partially
created address space. The system does not process
the command.
Operator Response: Enter the command again. If the
system issues this message again, notify the system
programmer. ReIPL as requested by the system
programmer.
System Programmer Response: If the system issued
this message while starting an initiator, the auxiliary
storage manager (ASM) may have run out of paging
space. Ask the operator to reIPL, specifying larger or
additional paging data sets. If these data sets are not
available, modify ASM paging constant ASMSLOTC as
described in the system programmer response for wait
state code X'03C'. Ask the operator to reIPL with the
existing page data sets.
IEA891I
NO MAXUSER VALUE SPECIFIED,

DEFAULT VALUE OF 255 USED
Explanation: The IEASYSxx parmlib member does

not specify a MAXUSER number. The system is using
the default value of 255.

IEA892I
MAXUSER=val1 RSVNONR=val2
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:
649
v The sum of the MAXUSER, RSVNONR, and

RSVSTRT values is too large.
IEA894I
v The SQA is too small.

val1
The value of MAXUSER in IEASYSxx
val2
The value of RSVNONR in IEASYSxx
val3
The value of RSVSTRT in IEASYSxx

respecify the three parameters by issuing message
IEA906A three times: once each for MAXUSER,
RSVNONR, and RSVSTRT.
as the system programmer directs.
REQUESTED VOLUME ON
UNREQUESTED UNIT. dev NOW
UNLOADED.

parmlib member, the system found a requested volume
mounted on a device that was not in the reply to
message IEA851A. In the message text:
dev
The device number of a device that was not in the
reply.
Operator Response: Mount the volume on a
requested device if the attributes are to be processed.
v Examine the size of the SQA.

v If a MAXUSER, RSVNONR, or RSVSTRT parameter
value is too large, provide the operator with new
values for the parameters.
v Ask the operator to respond to message IEA906A
with the new values for the parameters.
v Correct the parameters in the IEASYSxx member so
that this message will not be issued during every
system initialization using IEASYSxx.
IEA895A
FORMAT ERROR. REPEAT REPLY.
Explanation: An error exists in the reply to message

IEA851A.
System Action: The system ignores the reply and
waits for the operator to enter another reply.
Operator Response: Enter the reply again correctly,
or reply U.
IEA893A
IEA896I
NOT READY. REPLY U WHEN DEVICES

ARE READY, OR NO IF NOT
MOUNTING. dev,dev,...
Explanation: To complete processing of the

VATLSTxx parmlib member, the system is waiting for
devices that are not ready. In the message text:
dev
RECORDING FUNCTION NO LONGER

ACTIVE
Explanation: The recovery termination manager

(RTM) has stopped recording because of unrecoverable
errors. The system cannot do the following:
v Write logrec data set error records.
v Write to the operator for the WTO macro.
The device number of a device that is not ready.

ready the devices, then to respond.
System Action: The system does not process

recording requests. Requesters receive a return code
indicating that recording is no longer active.
Operator Response: When you have readied all of

the volumes in message IEA851A that you require on
the devices listed in message IEA860A, REPLY U or
press ENTER.

this message. If requested by the system programmer,
reIPL the system.
If any devices have not been readied, message

IEA893A will be reissued, listing those devices.
Respond as above if there are more volumes to be
mounted. If no more volumes are to be mounted on the
devices listed, REPLY NO.
650
System Programmer Response: If recording is

needed, ask the operator to reIPL the system.
problem. If no fix exists, report the problem to the IBM
Support Center.
IEA900I
INVALID ICS IN IEAICSxx

manager (SRM) initialization found an incorrect
parameter value in the IEAICSxx parmlib member.
IEAICSxx
the member used.
System Action: The system ignores all installation
control specification (ICS) data in this member. The
system writes message IEA906A to ask the operator to
respecify the ICS parameter. Diagnostic messages are
written to the hardcopy log.
Operator Response: Write the hardcopy log (when it
becomes available), correct the errors, then use the
SET ICS commands to begin using the corrected ICS.
In response to IEA906A, specify another valid IEAICSxx
member or specify EOB (press ENTER) to continue
system initialization.
System Programmer Response: Write the hardcopy
log (when it becomes available) to see which diagnostic
messages have been written. Correct the ICS
parameters in the IEAICSxx member.
If the IEAICSxx member was correct, search problem
of the IEAICSxx member.
REPLY U THEN DEPRESS TOD CLOCK SECURITY

SWITCH WHEN ENTERED TIME OCCURS, do the
following:
v Enter REPLY id,U to acknowledge that you received
this message.
v Press the security switch at the same time you
respond to message IEA888A or IEA886A.
When the message reads REPLY U WHEN THE
ENTERED TIME OCCURS, enter REPLY id,U at the
same time specified in message IEA888A or IEA886A.
Detecting Module: IEE6603D
IEA907W
UNABLE TO INITIALIZE PAGE AND/OR

SEGMENT TABLES FOR
{CSA|SQA|LPA}
Explanation: The system cannot initialize the system

queue area (SQA), common service area (CSA), or link
pack area (LPA) because there is not enough central
storage available.
System Action: The system enters wait state X'03D'.
Operator Response: Request a stand-alone dump.

amount of central storage available to the system, or
decrease the amount of virtual storage requested for the
SQA, CSA or LPA.
IEA903A
IEA908I
{REPLY U THEN DEPRESS TOD

CLOCK SECURITY SWITCH WHEN
ENTERED TIME OCCURS|REPLY U
WHEN THE ENTERED TIME OCCURS}
Explanation: The operator responded to message

IEA888A or IEA886A in a way that requires the
time-of-day (TOD) clock to be set.
Message REPLY U WHEN THE ENTERED TIME
OCCURS is issued when you are running MVS under
VM or PR/SM.
System Action: When the message reads REPLY U
THEN DEPRESS TOD CLOCK SECURITY SWITCH
WHEN ENTERED TIME OCCURS and when the
operator acknowledges receipt of the message, the
system attempts to set a TOD clock for a one-minute
interval. If the operator does not press the security
switch during that interval, the system issues message
IEA888A or IEA886A again.
When the message reads REPLY U WHEN THE
ENTERED TIME OCCURS, the system starts the TOD
Operator Response: When the message reads
QUICKSTART IS IN PROCESS - SQA

PARM IS IGNORED - VALUES USED
ARE nnnnK AND mmmmmmmK
Explanation: The requested system queue area

(SQA) size is not the same as the SQA size requested
at the previous system initialization. One of the following
occurred:
v A different SQA size was specified at quickstart
v The nucleus size increased since the previous
system initialization
nnnnK
The size of the SQA for the duration

of this initial program load (IPL).
mmmmmmmK
The size of the extended SQA for the

duration of this IPL.
System Action: The system defaults to the SQA size

specified in message IEA908I. The system continues
processing.
651
{CSA|SQA} PARM SPECIFIED IS a,b.

ONLY xxxxxxxx OF VIRTUAL STORAGE
AVAILABLE FOR
{CSA|SQA|ECSA|ESQA}
IEA909I
Explanation: The storage area requested for the

system queue area (SQA) or common service area
(CSA) is too large.
|
|
|
|
|
|
|
a,b
The parameter that specified the amount of

virtual storage. The parameters are shown as
they were specified in the IEASYSxx parmlib
member, where n is a decimal number of one
or more digits:
v a can be n, nK, or nM
v b can be n, nK, or nM
xxxxxxxx
to allow the debugging of the

problem to be successful. The
codes in the SDRSN field can be
used to determine what storage
was effected, or what problems
were encountered while SVC
dump processing was executing.
dumpid
The 3character dump identifier.
jobname
The name of the job that requested

the dump.
REMOTE DUMPS REQUESTED

The SDUMPX macro or DUMP
command that requested this dump
also requested dumps on other
systems in the sysplex.
REMOTE DUMP FOR SYSNAME: sysname
The amount of virtual storage available.
The dump was requested by

sysname, which is another system in
the sysplex.

IEA906A.
message IEA906A.

The formatted incident token for the
dump.

SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz

The system wrote only a partial dump.
IEA911E
{COMPLETE|PARTIAL} DUMP ON
SYS1.DUMPnn
DUMPid=dumpid REQUESTED BY
JOB (jobname)
FOR ASIDS(id,id,...)
[REMOTE DUMPS REQUESTED|REMOTE
DUMP FOR
SYSNAME:sysname]
INCIDENT TOKEN:incident-token
[SDRSN =
vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz]
[reason-text]
[ERRORID = SEQyyyyyy
CPUzz ASIDasid
TIMEhh.mm.ss.f]
[TSOID = tsoid]
[ID = uuuuuuuuuu]
Explanation: The system wrote a complete or partial

SVC dump to a pre-allocated dump data set on a direct
access storage device (DASD) or a tape volume.
COMPLETE
The SVC dump was complete.
PARTIAL
The SVC dump was not complete.
|
|
|
|
|
nn The dump was written to the

SYS1.DUMPnn data set. Not all
of the virtual storage requested
was collected. However, enough
storage may have been dumped
652
vvvvvvvv

following:
80000000
A system request block (SRB) for
the dump could not be scheduled
to the requested address space.
Either no current address space
had the requested ASID or the
system was ending the address
space with that ASID.
40000000
SVC dump processing could not
obtain real storage manager
(RSM) serialization because of a
hierarchy problem.
20000000
obtain RSM serialization because
of a RSM control problem.
10000000
obtain a central storage buffer
from the real storage manager.
08000000
An error in scheduled SVC dump
processing caused recovery to
receive control.
04000000
An error in summary dump
processing caused recovery to
receive control.
04000000|02000000
While processing an SVC dump,
the system detected an error and
gave recovery control.
02000000
An error in summary dump
processing or suspend summary
dump processing caused
recovery to receive control.
01000000
The started dump task failed.
00400000
An error caused the loss of
summary dump.
00800000
A task abnormally ended, and
SVC dump processing took a
partial dump. The resource
manager for SVC dump
processing receives control.
00200000
During suspend summary dump
processing, the virtual storage
buffer filled up.
00400000
The system detected an error in
the SVC dump writing task and
00100000
No more summary dump data
could be written because the
central storage buffer was full.
00200000
An address space involved in the
dump abnormally ended, and
SVC dump took a partial dump.
The resource manager for SVC
dump processing receives control.
0080000
While the system was waiting for
writing a trace table, an error
occurred. The trace table could
not be written.
wwwwwwww
00100000
The DUMPSRV address space
abnormally ended, and SVC
dump processing took a partial
dump. The resource manager for
SVC dump processing receives
control.

following.
00010000
During dump processing of a
possibly hung address space, the
address was found to be invalid.
The dump data may not be
consistent.
00080000
While processing the dump
header, the system ran out of
space to place data.
00040000
During dump processing of local
storage, the system issued a
PURGEDQ because a hung
address space was detected. This
s will result in the loss of some
storage related to the address
space.
00020000
possibly hung address space,
dump processing obtained only
fixed storage for the address
space.
80000000|40000000
While processing SVC X33, the
system detected an error and
00020000
possibly hung address space,
dump processing obtained only
fixed storage for the address
space.
20000000
The system detected an error in
the SVC dump task and gave
recovery control.
00010000
possibly hung address space, the
address space was found to be
invalid. The dump data may not
be consistent.
10000000
The SVC dump task failed.
08000000
The system detected an error
while writing a trace table. The
system could not write the trace
table.
xxxxxxxx

following:
653
80000000
While building the address range
table for global storage areas,
SVC dump processing filled the
table and remaining entries could
not be added.
40000000
table for local storage areas, SVC
dump processing filled the table
and remaining entries could not
be added.
20000000
table, SVC dump processing filled
the table and remaining entries
could not be added.
10000000
While dump processing was
writing to the dump data set, an
I/O error occurred.
08000000
The dump data set is full, but
more data needs to be dumped.
04000000
An error occurred while writing
the summary dump.
02000000
An error occurred while dump
processing was obtaining trace
data.
01000000
setting up the service request
block (SRB) under which the
dump was to be processed, an
error occurred.
00800000
An error occurred in an exit
routine.
00400000
An error occurred while writing
the end-of-data record to the
dump data set.
00200000
Some read-only ranges of data
could not be added to the range
table.
00100000
copying global storage into a data
space, an error occurred.
00080000
654
copying a sub-range of common

storage into a data space, an
error occurred.
00040000
An error occurred in the
processing of data spaces that
were requested through the
LISTD keyword on the SDUMPX
macro, or through the DSPNAME
parameter on the DUMP
command.
00020000
Dump processing could not add
some ranges of read/write
storage to the range table.
00010000
SVC dump processing truncated
the dump because the maximum
amount of space was been
reached.
00008000
While processing the SQA SDATA
option, the system filled in the
range table.
00004000
While processing the CSA SDATA
option, the system filled in the
range table. Remaining entries
could not be added.
00002000
While processing global subpools,
the system filled in the range
table. Remaining entries could not
be added.
00001000
While processing the LSQA
SDATA option, the system filled in
the range table. Remaining
00000800
While processing the RGN
00000400
While processing private
subpools, the system filled in the
range table. Remaining entries
could not be added.
00000200
While processing the SWA
00000100
While copying global data into a
data space, dump processing
was unable to capture some
ranges of global storage.
00000080
An exit data space could not be
created, or the data space was
created but an ALET could not be
obtained to access the data
space.
00000040
A summary data space could not
be created, or the data space
was created but an ALET could
not be obtained to access the
data space.
00000020
A local data space could not be
space.
00000010
A global data space could not be
space.
00000008
SVC dump could not create or
could not use the data spaces
that are required to process the
STRLIST request. Some data will
not be included in the dump.
00000001
the dump because a critical
shortage of auxiliary storage
existed. See the information for
message IRA201E to determine
how to relieve the shortage.
zzzzzzzz

following:
Bits in the first byte indicate a
result that occurred because one or
more of the following conditions
may exist:
v there is a shortage of central
storage
v there is a shortage of auxiliary
storage
v the DUMPSRV address space
dispatching priority is too low
80000000
Dump processing had reset the
system dispatchable and dump
processing failed or ended,
leaving the system set
non-dispatchable.
40000000
Dump processing had reset the
tasks dispatchable in one or more
address spaces involved in the
SVC dump. Then dump
processing failed or ended,
leaving the tasks
non-dispatchable.
20000000
Dump processing reset the
callers unit of work, which was
stopped as part of suspend
summary dump processing. Then
dump processing failed during
suspend summary dump
processing, leaving the caller
suspended.
10000000
IEAVTSDB released serialization
for all serialized structures
specified in the STRLIST because
SDUMP appears to have failed or
ended.
08000000
The central storage buffer
containing the summary dump
was released when it was
determined that dump processing
was hung. The summary dump
was lost.
00800000
Facility not available. Some
structures will not be dumped.
00400000
The structure is not available for
v The system detected a
structure failure and the
structure cannot be accessed
v The structure is not allocated
00200000
No facility dump space is
allocated or no facility dump
space is available because it is
being used to hold structure
dump tables for other structure
dumps
00100000
Possible error in STRLIST
655
The dump data set is full, but

more data needs to be dumped.
The message indicates at what
point the data set became full.
parameter list for one of the

following reasons:
v The structure does not exist in
the active policy
v The structure type is not
compatible with the specified
range options
v A lock structure was requested.
SDUMP does not support lock
structures
00080000
Some or all of the STRLIST could
not be processed
00040000
The system released structure
dump serialization before
capturing all the data. The system
captured the rest of the data after
releasing serialization.
00020000
processing STRLIST
00010000
SVC dump was unable to
continue processing a structure
requested in the STRLIST
parameter list. This may be
because the operator deleted the
structure dump with the SETXCF
FORCE command.
00008000
building the SDUMP signals for
other systems in the sysplex
reason-text

SUMMARY DUMP INFORMATION
WAS LOST
A problem arose where
processing was unable to
complete a requested summary
dump. Refer to the description of
the SDRSN bits that are set to
determine whether the data was
truncated, or completely lost.
A CRITICAL AUXILIARY STORAGE
SHORTAGE EXISTED
the dump because a critical
shortage of auxiliary storage
existed. See message IRA201E
to determine how to relieve the
shortage.
|
|
|
|
|
|
|
DUMP DATA SET FULL - DUMP
|
ENDED WHILE WRITING
{SUMDUMP|GLOBAL|LOCAL|STRLIST} |
656
I/O ERROR - NO EOF WRITTEN DUMP ENDED WHILE WRITING

An I/O error occurred while the
system was writing to the dump
data set. The message indicates
the system was dumping at the
time of the I/O error.
MAXSPACE LIMIT REACHED
WHILE CAPTURING DUMP
Insufficient space was available to
capture the complete dump.
EXIT
LOCAL EXIT
GLOBAL EXIT
EARLY GLOBAL EXIT
ONE-TIME-ONLY EXIT
DYNAMIC LOCAL EXIT
DYNAMIC GLOBAL EXIT
Dump processing encountered an
unexpected error in an SDUMP
exit of the specified type.
SOME STORAGE COULD NOT BE
DUMPED RC=rc
Storage could not be dumped. rc
can be one of the following:
04
The system could not find the

requested ASIDs.
08
Not all of the data requested

in a summary dump could be
contained in the central
storage buffer or virtual
storage buffer.
Note: Even though some
summary dump
records may be
missing, IEA911E
COMPLETE DUMP
will be issued when
there are no other
data truncation reason
bits set. This indicates
|
|
|
|
|
|
|
|
|
|
|
v The routine had detected that SVC

dump processing was not
continuing normally or had ended
and left the structure serialized.
that the dump

contains all of the
virtual storage
requested. Only the
summary dump
records are missing,
and these are usually
duplicated in the
virtual storage
dumped at a slightly
later time.).
12
16
20
Either (1) the internal SVC

dump control blocks are full,
so that some data was not
dumped, or (2) dump
processing received an error
return code when it tried to
dump the system trace.
SVC dump was not able to
process all of the structures
specified in the STRLIST
parameter list.
v ACCESSTIME=ENFORCE was
specified on the dump request (or
defaulted) and the data requested
in the STRLIST parameter list for a
requested structure was not
completely processed within the
time limit specified by the
ACCESSTIME parameter on the
IXLCONN macro.
Dump processing encountered an
unexpected error.
ERRORID = SEQyyyyyy CPUzz ASIDasid
TIMEhh.mm.ss.t
The error identifier.
yyyyyy The sequence number
SDUMP processing could not

collect the local storage of at
least one of the normally
collected storage address
spaces involved in the dump.
Refer to the description of
the SDRSN bits that are set
for more information.
SYSTEM RESET DISPATCHABLE PRIOR TO DUMP

COMPLETION Dump processing failed or ended with
the system set non-dispatchable. The
system detected the error and reset
dispatchable.
TASKS RESET DISPATCHABLE PRIOR TO DUMP
COMPLETION Dump processing failed or ended with
tasks set non-dispatchable in one or
more address spaces involved in the
SVC dump. The system detected the
error and reset the tasks dispatchable.
ENABLED CALLER RESET PRIOR TO DUMP
COMPLETION Dump processing failed or ended
during suspend summary dump
processing, leaving the caller
suspended. The system detected the
error and reset the callers unit of
work.
STRUCTURE DUMP SERIALIZATION RELEASED
PRIOR TO DUMP COMPLETION
The SVC dump time disabled
interruption exit routine released
dumping serialization that was held for
a structure requested in the STRLIST
parameter list. Serialization was
released because:
zz
The central processor

address
asid
The ASID for the address

space in which the error
occurred
hh.mm.ss.t
The time in hours (00
through 23), in minutes (00
through 59), in seconds (00
through 59), and in tenths of
a second (0 through 9).
TSOID = tsoid
The dump was generated for a SLIP

trap that was set in a Time Sharing
Option (TSO) session.
tsoid
The identifier of the TSO

user who defined the trap.
ID = uuuuuuuuuu
The component or subsystem
identifier that was supplied in the ID
keyword on the SDUMP or SDUMPX
macro.
Operator Response: To keep dump data sets
available, ask the system programmer to identify
SYS1.DUMPnn data sets that can be cleared. Then
enter DUMPDS commands to clear them.
System Programmer Response: Take the
appropriate action as indicated in the following
descriptions:
WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}
Format the partial dump.
657

WHILE WRITING
Look at the logrec error records to determine the
device problem. Contact hardware support.
Format the partial dump. If a previous dump was in
the dump data set, the data set may contain a
combination of the two dumps.
Obtain the logrec error record. Search the problem
reporting data bases for a fix for the problem. If no
fix exists, notify the IBM Support Center. Provide
the logrec error record.
SOME STORAGE COULD NOT BE DUMPED RC=16
Refer to the description of the SDRSN bits that are
set. Use the IPCS Sub-Command STRDATA to
format the list of structures that was requested to
be dumped. The reason that the structures were
not completely processed will be displayed.
Source: SVC dump
Detecting Module: IEAVTSDC

IEA913I
COMMON AREA BELOW 16M

EXCEEDS 8M by xxxxK
Explanation: The size of the common area below 16

megabytes is greater than 8 megabytes. This reduces
the size of the private area below 16 megabytes.
xxxxK
The number of kilobytes by which the size of

the private area below 16 megabytes is
reduced.

IEA915E
SYNTAX ERROR IN IEASYSxx

CONTENTS, PROMPT FOLLOWS
Explanation: Paging data set names are incorrect in

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

the operator to respecify the PAGE parameter.
v An unopened data control block (DCB) was

referenced during validity checking.
Operator Response: Respond to the message. Notify

v A task control block (TCB) address that is not valid

was referenced during validity checking.
v A page that was not valid was referenced during
validity checking.
v Storage was unavailable.
System Programmer Response: Before the next IPL,

correct the contents of IEASYSxx according to the
syntax for specifying paging space data set names.
v The DCB type was not correct.
IEA916E
DUE TO cde
SYSMDUMP processing ended abnormally with a
completion code of cde.
System Action: Except for the case where tasks are
prematurely marked dispatchable, the system does not
write out the dump.
System Programmer Response: Correct the original
failure and, if the message includes cde, the dump
failure. See the system programmer response for
completion code cde. In the case where the tasks were
prematurely made dispatchable, and enqueue lockout
situation was detected and allowed to clear up.
However, the information in the dump must be carefully
validated because task processing might have changed
vital information in common and shared storage areas.
658
SYNTAX ERROR IN
{PAGE=|PAGTOTL=| NONVIO=}
SYSTEM PARAMETER, PROMPT
FOLLOWS
Explanation: A system parameter contains a syntax

error.
to prompt the operator to respecify the parameter, or to
press the ENTER button on the console.
Operator Response: Reply to message IEA906A.
system parameter has the correct syntax.
IEA918I

ACCEPTED
Explanation: The system could not use a page data

set because either:
v The auxiliary storage manager (ASM) is already
using the data set.
v This data set would exceed the limit of page data
sets.
dsname
System Action: The system continues initialization. If
the data set is already in use, the system issues
message IEA922D.
v If message IEA922D follows this message, the data
set is already in use. Respecify a data set name.
v If a page data set limit has been reached, notify the
system programmer.
System Programmer Response: If this data set must
be used and some others should be omitted, respecify
the paging data sets when restarting the system with
the CLPA or CVIO option.
IEA920I

LOCATED
Explanation: The system could not use a page data

set because either:
v The system could not locate a data set in the master
catalog.
v The master catalog information does not agree with
expected and necessary attributes of a page data
set.
Operator Response: Reply to message IEA922D, if

issued. Notify the system programmer.
system initialization, verify that the page data set is
cataloged in the master catalog.
IEA921I
PAGE DATA SET dsname INVALID
Explanation: The catalog for a page data set does not

meet the requirements of a page data set. The device
may not be supported for paging, or the data set is not
defined as previously known for paging.
dsname
System Action: If the page data set was to contain
PLPA pages, the system issues message IEA935W.
The system ends initialization.
If the DUPLEX page data set is known from a previous
IPL and should be used under current IPL options, the
system issues message IEA942I. Paging initialization
continues.
If the page data set is known to paging initialization as
containing VIO pages which should be used under
current IPL options, the system issues message
IEA930I. Paging initialization continues.
In all other cases, the system issues message
IEA922D.
Operator Response: If the system issues IEA922D,
respecify the data set name. Otherwise, notify the
system programmer.
System Programmer Response: Check catalog
information about this data set. If necessary, redefine it
before the next system initialization.
dsname
System Action: The system continues initialization.
If the data set was newly specified during this IPL, the
system issues message IEA922D to prompt the
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
VIO pages that should be used under current IPL
options, the system issues message IEA930I. The
system continues initialization.
IEA922D.
IEA921I
PAGE DATA SET dsname INVALID
Explanation: The catalog for a page data set does not

meet the requirements of a page data set. The device
may not be supported for paging, or the data set is not
defined as previously known for paging.
dsname
System Action: If the page data set was to contain
PLPA pages, the system issues message IEA935W.
The system ends initialization.
If the page data set is known to paging initialization as
659
containing VIO pages which should be used under

current IPL options, the system issues message
IEA930I. Paging initialization continues.
If the volume is to be provided (GO), initialization

continues. The system issues a mount message. The
data set is used.

IEA922D.
If the volume is to be ignored (IGNORE), initialization

continues without the data set.
Operator Response: If the system issues IEA922D,

respecify the data set name. Otherwise, notify the
system programmer.
Operator Response: Either enter REPLY id,GO and

prepare to mount the requested volume, or enter
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
before the next system initialization.
System Programmer Response: Review space now

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
insufficient.
IEA922D
REPLY DSN= OR IGNORE
Explanation: This message allows the operator to

respecify a page data set name.
reply. If the operator replies with a new data set name,
the system processes the data set. If the operator
replies IGNORE, initialization either continues with the
existing list of data sets, or the system enters wait state
X'03C' if the data is:
v The PLPA page data set.
v The COMMON page data set.
v The only local page data set that is available to the
system.
v Enter REPLY id,DSN= to specify the new data set
name.
v Enter REPLY id,IGNORE to continue with the data
set.
System Programmer Response: See the previously
issued message.
IEA923D
VOLUME ser NEEDED FOR PAGE DATA

SET WAS NOT MOUNTED; REPLY GO
OR IGNORE
Explanation: The system could not open a page data

set because the volume was not mounted. The data set
does not contain any pages of PLPA or VIO that would
be missed with the IPL options in effect.
ser

reply.
660

IEA924D

SET WAS NOT MOUNTED; {CLPA MAY
BE FORCED|NEW PLPA DATA SET
MAY BE REQUESTED}; REPLY GO OR
IGNORE
Explanation: The system attempted to open a page

data set on this volume, but discovered that the volume
was not mounted.
ser
CLPA MAY BE FORCED

The COMMON page data set resides on this
volume.
NEW PLPA DATA SET MAY BE REQUESTED
The PLPA page data set resides on this volume.
reply. If the volume is to be provided (GO), paging
initialization continues. The system issues a mount
message. The data set is used.
In most cases, if the volume is not to be provided
(IGNORE), message IEA922D requests a new data set
name.
If a quick or warm start is in progress, the PLPA page
data set overflowed to the COMMON page data set.
The unmounted volume contains this COMMON page
data set. Initialization will force a cold start (CLPA) and
issue message IEA929I.
REPLY id,IGNORE. Notify the system programmer.
System Programmer Response: If a permanent
change is desired, update the IEASYSxx parmlib
member to reflect the new PLPA or COMMON page
data set name. Otherwise, complete the IPL, correct the
problem, and reIPL with the original data sets.
Detecting Module: IEAVNP1F

IEA927I
IEA925D

SET WAS NOT MOUNTED; CVIO MAY
BE FORCED; REPLY GO OR IGNORE
Explanation: When the system tried to open a page

data set, the volume containing the data set was not
mounted. The volume contains pages of VIO data sets
that may be required for recovery of one or more VIO
data sets.
ser

reply.
If the volume is to be provided (GO), initialization
continues. The system issues a mount message. The
page data sets on that volume are used.
If the volume is not provided (IGNORE), initialization
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.
REPLY xx,IGNORE. Notify the system programmer of
this message if the volume is not made available.
System Programmer Response: Review paging
space because the CVIO option is in effect
unexpectedly. Only data sets specified on this IPL will
be used. Consider asking the operator to enter the
PAGEADD command.
IEA926I
INVALID SYNTAX FOR CMB KEYWORD
Explanation: The parameter string of the channel

measurement block (CMB) keyword in the IEASYSxx
parmlib member is incorrect.
System Action: The system ignores all data in the
CMB keyword. The system writes a message to ask the
operator to respecify the CMB keyword and its
parameter string.
Operator Response: Reply to the prompting message
with a valid CMB keyword or specify EOB (press
ENTER).
System Programmer Response: Verify the CMB
keyword and its parameters in the IEASYSxx member. If
the parameters are correct, search problem reporting
PLPA AND COMMON PAGE DATA SETS

FULL FROM PREVIOUS IPL
Explanation: On a previous system initialization, the

PLPA and COMMON page data sets were filled up
during the write of the pageable link pack area (PLPA).
The common storage area (CSA) and the rest of the
PLPA have no primary slots.
System Action: Initialization continues with the
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
the previous DUPLEX page data set is usable, then ask
the operator to reIPL. Otherwise, redefine the PLPA and
COMMON page data sets, then ask the operator to
reIPL with the CLPA option.
IEA928I
MODULE AT LOCATION xxxxxx IN PLPA

CONTAINS HOLES

1. While building the paging information for the
pageable link pack area (PLPA) during a cold start
(CLPA IPL), the system found an incorrect external
page table entry for a PLPA module.
2. While restoring paging information for PLPA during a
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
1 occurred during cold start.
These conditions indicate that the module in the PLPA
contains non-contiguous code or large constant areas
on the page referenced by the page table entry. This
condition should not occur in a PLPA module.
xxxxxx The address of the module.

System Action: Paging initialization processing marks
the external page table entry as incorrect. Initialization
processing continues. Any address space that
subsequently references this PLPA page will abnormally
end with abend code X'028'.
System Programmer Response: Use the current LPA
map to identify the module containing virtual address
xxxxxx. Correct the module. Ask the operator to IPL,
specifying the CLPA system parameter.
661
Detecting Module: ILRQSRIT

output for the job.
IEA929I
Collect all printed output and output data sets related to

the problem. Search problem reporting data bases for a
Support Center.
CLPA FORCED
Explanation: Initialization cannot continue without the

CLPA option. A cold start is forced.
System Action: Initialization continues as if CLPA had
been specified.
System Programmer Response: Look for the
messages that preceded this message.

IEA933I

IEA930I
CVIO FORCED
Explanation: Initialization cannot continue without the

CVIO option. All VIO data set pages are cleared.
System Action: Initialization continues as if CVIO had
been specified.
System Programmer Response: Look for the
messages that preceded this message.
IEA931I
ESTAE REQUEST FOR GTF TRACE

FORMATTING FUNCTION
UNSUCCESSFUL
Explanation: The recovery environment requested by

the generalized trace facility (GTF) was not established.
Explanation: Generalized trace facility (GTF)

formatting module was unable to load a format
appendage.
xxx
Collect all printed output and output data sets related to

the problem. Search problem reporting data bases for a
Support Center.
IEA932I
INSUFFICIENT STORAGE FOR GTF

BUFFER FORMATTING
Explanation: There is insufficient system queue area

(SQA) for generalized trace facility (GTF) buffer
formatting.
System Action: The system does not format any GTF
buffers.
662
The format appendage.
System Action: The system continues formatting GTF

buffers, dumping in hexadecimal any record that
requires the format appendage for editing.
System Programmer Response: Collect all printed
Center.
IEA934I
System Action: The system does not format any GTF

buffers.
output for the job.
UNABLE TO LOAD FORMAT

APPENDAGE xxx. FURTHER RCDS
REQUIRING THIS MOD WILL BE
DUMPED IN HEX
INVALID RETURN CODE RECEIVED

FROM mod. FURTHER RCDS
REQUIRING THIS MOD WILL BE
DUMPED IN HEX
Explanation: The system detected an incorrect return

code on return from a module.
mod
System Action: The system continues formatting GTF

buffers, dumping in hexadecimal any record that
requires this module for editing.
System Programmer Response: Collect all printed
Center.
IEA935W
INSUFFICIENT PAGING RESOURCES,

IPL TERMINATED
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
certain distribution available. The system determined
that these requirements are not available.
system enters a wait state.
the wait state.
programmer response for the wait state.
IEA936D
FUTURE QUICK AND WARM STARTS

OF THIS IPL WILL FAIL. RE-IPL OR
REPLY GO TO CONTINUE COLD
START
Explanation: On a system initialization with the CLPA

option, the system needed to write quick/warm start
data to the first records of the PLPA page data set.
However, the write failed. None of the information will
be accessible to a future initialization.
reply.
Enter REPLY id,GO to continue with the cold start, or
reIPL at the system programmers request.
System Programmer Response: When using this
PLPA page data set again, ask the operator to perform
an IPL with the CLPA option.
Detecting Module: ILRQSRIT
IEA937I
COMMON PAGE DATA SET

TIMESTAMP FAILURE
Explanation: When this message is followed by

message IEA935W, the system could not read or write
the time stamp record in the COMMON page data set.
The time stamp is written on initializations with the
CLPA option; it is written on initializations without the
CLPA option if part of the PLPA was written to the
COMMON page data set.
When this message is followed by message IEA929I,
the system read the time stamp in the COMMON page
data set, but the time stamp failed to match the time
stamp of the PLPA slot information.
System Action: If unable to access the COMMON
page data set, the system enters a wait state. If the
wrong level of the COMMON page data set is

accessed, system operation continues with a cold start
(CLPA IPL) forced.
System Programmer Response: If the system
entered a wait state, correct or replace the COMMON
page data set. Then ask the operator to reIPL with the
CLPA option.
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
operator to reIPL.
IEA938W
NO STORAGE AVAILABLE, PAGING

INITIALIZATION TERMINATED
Explanation: A request for additional storage failed

during initialization. The maximum size of the system
queue area (SQA) specified has probably been
exceeded.
system enters a wait state.
System Programmer Response: Ensure that enough
SQA is requested. If not, increase the SQA maximum
size.
Otherwise, the system configuration may be too small.
Possibly, an error occurred in the system. Search
no fix exists, contact the IBM Support Center.
IEA939D
QUICK AND WARM START DATA IS

INVALID, RE-IPL OR REPLY GO FOR
COLD START
Explanation: A system initialization without the CLPA

option was attempted. Information on the PLPA paging
data set was inaccessible:
v The specified PLPA paging data set must be the
same as that used on the previous successful cold
start (CLPA IPL).
v If the same data set was being used, then the system
could not read the necessary information.
reply.
Operator Response: Either enter REPLY id,GO if a
cold start is desired, or reIPL with a different data set
specified for PLPA paging. Notify the system
programmer.
663

correct IEASYSxx parmlib member is being used. Also,
verify the previous use of the PLPA paging data set.
IEA940I
THE FOLLOWING PAGE DATA SETS

ARE IN USE:
PLPA ... dsname
COMMON . dsname
LOCAL .. dsname
.
.
.
Explanation: This message is issued if L is specified

on the PAGE system parameter, or if the system has
been forced to change the list of page data sets
originally specified. The list of data sets should help the
operator verify which paging volumes are in use,
especially after a warm start where data sets used on
the previous initialization were not specified on this
initialization.
IEA942I
DUPLEXING INACTIVE, {NO DATA

SET|BAD TIME STAMP}
Explanation: A DUPLEX page data set and the CLPA

option were specified either on the current initialization
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.
NO DATA SET
A preceding message indicates the error.
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
the time stamp no longer matched that of the PLPA
slot information.
System Action: Initialization continues without
duplexing.
Operator Response: To restore duplexing, perform a

cold start (CLPA IPL) with the DUPLEX page data set
specified. If necessary, replace or correct the DUPLEX
page data set.
dsname

System Action: Initialization continues.

IEA943W

IEA941D
VOLUME ser NEEDED FOR DUPLEX

DATA SET NOT MOUNTED DUPLEXING
MAY BE STOPPED, REPLY GO OR
IGNORE
Explanation: The system attempted to open a volume,

but discovered that the volume was not mounted. If
duplexing is desired for this initialization, the volume
must be mounted.
ser

reply. If the volume is to be provided (GO), initialization
continues; the system issues a mount message and
uses the data set. If the volume is not provided
(IGNORE), initialization continues without duplexing.
REPLY id,IGNORE.
664
FAILURE DURING SAVE OR REBUILD

OF PLPA
Explanation: For an initialization without the CLPA

option, the system attempted to restore paging
information for the PLPA data set into the page tables
representing the PLPA. However, the page table could
not be found or PLPA slot information was incorrect.
For a cold start (CLPA IPL), the system attempted to
save paging information found in page tables
representing the PLPA. However, a page table could not
be found.
System Action: The system ends initialization and
enters wait state X'061'.
ReIPL with the CLPA option.
System Programmer Response: See the operator
IEA944I
QUICK OR WARM STARTS FROM THIS

IPL WILL HAVE RANDOM RESULTS
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

information down level. Further use of the information
would, therefore, cause unpredictable results.
System Action: Initialization continues.
Be sure that the device containing the PLPA page data
set is not in READ ONLY status.
If the present IPL status is either specified or forced
CVIO, and it is desired to do an IPL without the CVIO
option, then stop the current IPL. If the present IPL did
not specify the CVIO option, continue with the current
IPL only to clear up previous VIO-related jobs.
ReIPL according to the system programmers
instructions.
System Programmer Response: Evaluate the PLPA
page data set, and replace or redefine, as necessary.
Then, ask the operator to reIPL with this PLPA page
data set and with the CLPA option.
IEA945W
UNABLE TO USE CLOCK FOR

TIMESTAMP
Explanation: On a system initialization with CLPA or

CVIO specified or forced, the system could not obtain a
unique time stamp to mark corresponding information
and data sets.
System Action: Initialization ends. The system enters
wait state X'061'.
wait state X'061'.
IEA946W
NO {VIRTUAL|REAL} STORAGE
AVAILABLE FOR SQA
Explanation: During processing for a GETMAIN or a

FREEMAIN macro, the system found that no storage
was available in the system queue area (SQA) to back
the storage request.
System Action: The system enters one of the
following wait states:
v X'101' for a virtual storage request
v X'102' for a central storage request
installation procedures to increase the central storage

requirements.
Detecting Module: IGVVSCEL
IEA947A
REPLY U TO CONTINUE, OR RE IPL.

parmlib member, the system found a system volume,
specified in message IEA866I, that is not mounted on
the device type specified in the VATLST entry.
reply.
Operator Response: If the wrong volume was
mounted for IPL, mount the correct volume. If the
correct volume is mounted, REPLY U to continue, and
notify the system programmer of the VATLST entry
error. If you reply U, the system will ignore the
attributes of the volume and they will remain public.
IEA948I
dev NOW UNLOADED.

parmlib member, the system unloaded a volume. In the
message text:
dev
The device number of the device from which the
volume was unloaded.
preceding message, either message IEA854I or
IEA866I.
IEA949I
I/O ERROR READING VATLSTxx.

parmlib member, the system detected an uncorrectable
I/O error. If message IEA949A does not appear, then
the system had not processed any VATDEF entries
before the error occurred.
System Action: The system may issue message
IEA949A to prompt the operator for a reply.
Operator Response: Restart the system. If the

system displays this message frequently, contact the
system programmer.
Operator Response: If message IEA949A appears,

see the operator response for that message.
System Programmer Response: See installation

procedures to increase the space allowed for the SQA.
If the system displays this message frequently, see
665
IEA949A
REPLY YES FOR LIST OF ENTRIES

THAT WILL BE PROCESSED, OR U
FOR NO LIST.

Operator Response: Notify to the system

programmer.
System Programmer Response: Rebuild IEAAPP00
prior to the next IPL for.
Source: DFSMSdfp

reply.
Operator Response: REPLY YES for a list of entries

(encountered before the error occurred) that will be
processed, or U if you do not want a list.
IEA959I
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
abnormal ending or unpredictable results.

IEA950I
MODULE mod NOT FOUND; MC

ROUTING INACTIVE
Explanation: A module was not found in the link pack

area (LPA). The system will be unable to initialize the
generalized trace facility (GTF).
mod

System Programmer Response: To use GTF, ensure
that the following modules are present in LPA:
AHLSETEV
AHLSETD
AHLMCER
After updating the necessary libraries with these
modules, reIPL the system to initialize GTF.
ERROR CAUSED ACTIVE LPA TO BE

TRUNCATED, MODULE CONTROL MAY
BE LOST

system programmer. If frequent abnormal endings
occur, reIPL may be necessary. Obtain a stand-alone
dump if the system programmer requests one.
logrec data set error record and the stand-alone dump,
if available.
IEA964I
HARDCOPY SUSPENDED,
REASON=xxxx, NO HARDCOPY
DEVICE AVAILABLE

IEA958I
EXCP APPENDAGE NAME TABLE NOT

BUILT

initialization program (NIP) accessed the IEAAPP00
parmlib member to build a table of valid modules that
may be loaded as run channel program (EXCP)
appendages. Due to an I/O error or to a syntax error in
IEAAPP00, NIP could not complete construction of this
table.
If installation supplied modules are being loaded as
appendages for a data control block (DCB) with
MACRF=(E), the modules must operate in protection
key 0-7 or be authorized under authorized program
facility (APF).
System Action: If unauthorized installation-supplied
appendages are loaded for a DCB with MACRF=(E),
the system issues abend code X'913'with a return code
X'20'.
666
Explanation: The device used to receive the

hard-copy log, or scheduled to receive the hard-copy
log, is unavailable. The system cannot switch the
hard-copy log to the system log or to an appropriate
console because neither is available.
xxxx

ATTRES
The master console was varied offline
after a failure.
KV
The operator entered a CONTROL V,

USE=FC command to relieve a no
consoles condition.
VARY
The operator varied a console online

to relieve a no consoles condition.
CQUEER
The system cannot obtain the console
queue element (CQE).
HCSW The hard-copy log was switched from
the system log.
EXT
The operator pressed the external

interrupt key.
IOER
An I/O error occurred on the failing

console.
SWER
A software error occurred for the

failing console.
VMST
The operator entered a VARY

MSTCONS command.
OPER
An open failure occurred for the

console.
CFCHP
The operator entered a CONFIG CHP
command.
SFAIL
A system in the sysplex failed.
SINIT
A system in the sysplex completed

initialization, causing a change in the
console configuration.
System Action: Processing continues. The system

does not save messages processed when no hard-copy
log is available.
Operator Response: Issue the VARY
{devnum|SYSLOG},HARDCPY command to restart the
hardcopy log. Either an actual hardcopy printer device
can be specified, or SYSLOG may be used if you want
the system log to be the hardcopy log.
IEA967W
UNSUCCESSFUL RECOVERY
ATTEMPT BY SUPERVISOR CONTROL
Explanation: Supervisor control experienced a double

recursive abnormal end in its super functional recovery
routine (FRR). This is a probable software error.
System Action: The system enters wait state X'01C'.
wait state X'01C'.
programmer response for wait state X'01C'.
Detecting Module: IEAVESPR
IEA989I
SLIP TRAP ID=xxxx MATCHED. [text]
Explanation: A SLIP command had set a SLIP trap

which requested that a dump be suppressed. All
conditions defined by the SLIP trap were met, and the
system has suppressed the dump. The system issues
this message to hardcopy only.
ID=xxxx
command.
text
Detecting Module: IEAVSWCB
JOBNAME=jobname,ASID=asid
The name of the job associated with the home
address space and the address space identifier
(ASID) of the home address space at the time
of the error or PER interrupt. If the job name is
not available, but the ASID is available, the
jobname is *UNAVAIL.
IEA966I
NO SRM DEVICE SELECTION OR I/O

LOAD BALANCING
Explanation: The system could not obtain central

storage to build channel measurement blocks (CMB).
Device allocation and I/O load balancing use these
channel measurements.
the device allocation and I/O load balancing algorithms
operating without I/O measurement data. The system
writes messages about the problem.
Operator Response: Configure additional central
storage. Notify the system programmer.
REAL, SQA, and CSA parameters are properly defined
in the IEASYSxx parmlib member.
If the parameters are correct, search problem reporting
JOBNAME/ASID NOT AVAILABLE

The job name and ASID of the home address
space at the time of the error.
System Action: The system suppresses the dump
Source: SLIP
IEA990I
{REAL|VIRTUAL} STORAGE NOT

AVAILABLE FOR {CMB|OPTIONAL
CMB ENTRIES|CPMF INTERFACE|IOS
INTERFACE}
Explanation: The system could not obtain enough

central (real) or virtual storage for the channel
measurement block (CMB) or for the channel path
measurement facility (CPMF).
system does the following:
667
STORAGE NOT AVAILABLE FOR CMB

The system continues processing, but the SRM
channel measurement facility is unavailable for
device selection and I/O load balancing for the
duration of this IPL. The system writes message
IEA966I.
OPTIONAL CMB ENTRIES
The system writes a message to ask the operator
to respecify the CMB keyword.
{CPMF INTERFACE|IOS INTERFACE}
The system continues processing without the use of
CPMF.
Operator Response: Check the available central
storage to see if it is properly configured.
allocation of storage for the common service area (CSA)
is properly specified. If the message reads OPTIONAL
CMB ENTRIES, ensure that the CMB system parameter
is properly specified in the IEASYSxx parmlib member.
IEA991I
SRM CHANNEL DATA NO LONGER

AVAILABLE FOR I/O SERVICE

v The channel measurement facility is not measuring
device connect time intervals (DCTI) because of a
failure in a channel or processor
v Storage is not available for a required system
resources manager (SRM) parameter list
System Action: SRM uses the execute channel
program (EXCP) counts from address space control
blocks (ASCBs) to calculate I/O activity.
Operator Response: If the system programmer
designated an IEAIPSxx parmlib member to be used
when device connection times are not available, enter a
set command for that IEAIPSxx member. Notify the
system programmer.
reason for the lack of storage. Search problem reporting
IEA992I
SLIP TRAP ID=xxxx MATCHED. [text]
Explanation: A SLIP command had set a SLIP trap.

All conditions defined by the SLIP trap were met. The
system has performed the requested action.
668
ID=xxxx
command.
text
JOBNAME=jobname,ASID=asid
The name of the job associated with the home
address space and the address space identifier
(ASID) of the home address space at the time
of the error or PER interrupt. If the job name is
not available, but the ASID is available, the
jobname is *UNAVAIL.
JOBNAME/ASID NOT AVAILABLE
The job name and ASID of the home address
space at the time of the error or PER interrupt
are not available.
If the SLIP command specified ACTION=WAIT, the
system will enter wait state X'01B'. Ordinarily, the
system enters the wait state before issuing this
message, but, due to timing within the system, the
system may issue this message before entering the
wait.
System Programmer Response: If a wait state
occurs, look at the data in message IEE844W.
Source: SLIP
IEA993I
SYSMDUMP TAKEN TO dsname
Explanation: The system wrote a SYSMDUMP dump

to the data set specified on the SYSMDUMP DD
statement. The dump is a complete dump.
dsname
The data set name.
IEA995I
SYMPTOM DUMP OUTPUT
text
{SYSTEM|USER} COMPLETION CODE=cde [REASON CODE=reason-code]
TIME=hh.mm.ss SEQ=sssss CPU=cccc ASID=asid
PSW AT TIME OF ERROR xxxxxxxx xxxxxxxx ILC x INTC xx
{ ACTIVE LOAD MODULE ADDRESS=aaaaaaaa OFFSET=nnnnnnnn |
NO ACTIVE MODULE FOUND}
{NAME=load-module-name|NAME=UNKNOWN}
{DATA AT PSW hhhhhhhh - dddddddd dddddddd dddddddd |
DATA AT PSW IS INACCESSIBLE BY USER |
DATA AT PSW IS UNAVAILABLE AT THIS TIME}
registers
END OF SYMPTOM DUMP
The system issues this message, which is the symptom

dump, for all abnormal ends when a SYSABEND,
SYSUDUMP, or SYSMDUMP is requested. You can use
the information in this message to assist in problem
determination.
If you want to suppress this message on your system,
do one of the following:
v Use the message processing facility (MPF)
v Stop the system from generating symptom dumps by
adding the SDATA=NOSYM option to the
SYSABEND, SYSUDUMP, or SYSMDUMP dump
options. You can specify the SDATA=NOSYM dump
option in the following ways:
Use the CHNGDUMP command from an operator
console.
Specify NOSYM in the IEAABD00, IEADMP00,
and IEADMR00 parmlib members.
SYSTEM COMPLETION CODE=cde
The system completion code from the ABEND
macro.
USER COMPLETION CODE=cde
The user completion code from the ABEND macro.
The reason code, if specified in the ABEND macro.
TIME=hh.mm.ss
The time that the dump was written in hours (00
through 23), in minutes (00 through 59), and in
seconds (00 through 59).
SEQ=sssss
Sequence number for the dump.
CPU=cccc
The central processor identifier. If cccc is 0000, the
system did not determine on which processor the
abend occurred.
ASID=asid
The address space identifier (ASID) of the failing
task.
PSW AT TIME OF ERROR xxxxxxxx xxxxxxxx
The program status word (PSW) at the time of
error.
ILC x
Instruction length code for the failing instruction.
INTC xx
Interrupt code for the failing instruction.
ACTIVE LOAD MODULE
ADDRESS=aaaaaaaa
Address of the load module, if the PSW points to
v A module running under the current task
v A module loaded by the current task.
NAME=load-module-name
Load module name, if the PSW points to an active
load module.
NAME=UNKNOWN
The system cannot ascertain the load module name
because the PSW does not point to an active load
module.
OFFSET=nnnnnnnn
Offset into the load module of the failing instruction,
if the PSW points to an active load module.
DATA AT PSW hhhhhhhh - dddddddd dddddddd
dddddddd
Address in the PSW minus six, followed by the
contents of the three words beginning at the
address in hhhhhhhh.
registers
The content of the general purpose registers at the
time of error. If the PSW at the time of error is in
AR ASC mode, the access registers will appear.
For a detailed description of the registers displayed,
see the following explanations.
The registers displayed in this message include all
registers that contain something other than zero. The
output varies depending on whether the system is
running in ESA/390 or z/Architecture mode, whether the
ARs are all zero, and whether the high halves of the
GPRs are all zero.
Case 1: The system is running in ESA/390 mode (or
z/Architecture mode when all the high halves of the
GPRs are zero) and all ARs are zero:
GR 0:
2:
4:
6:
8:
A:
C:
E:
gggggggg
gggggggg
gggggggg
gggggggg
gggggggg
gggggggg
gggggggg
gggggggg
1:
3:
5:
7:
9:
B:
D:
F:
gggggggg
gggggggg
gggggggg
gggggggg
gggggggg
gggggggg
gggggggg
gggggggg
Case 2: The system is running in ESA/390 mode (or

z/Architecture mode when all the high halves of the
GPRs are zero) and not all ARs are zero:
AR/GR 0:
2:
4:
6:
8:
A:
C:
E:
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
1:
3:
5:
7:
9:
B:
D:
F:
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
aaaaaaaa/gggggggg
Case 3: The system is running in z/Architecture mode,

the high halves of the GPRs are not all zero, and and
all ARs are zero:
GR 0: gggggggg_gggggggg 1: gggggggg_gggggggg
2: gggggggg_gggggggg 3: gggggggg_gggggggg
4: gggggggg_gggggggg 5: gggggggg_gggggggg
669
6:
8:
A:
C:
E:
gggggggg_gggggggg 7: gggggggg_gggggggg
gggggggg_gggggggg 9: gggggggg_gggggggg
gggggggg_gggggggg B: gggggggg_gggggggg
gggggggg_gggggggg D: gggggggg_gggggggg
gggggggg_gggggggg F: gggggggg_gggggggg
Case 4: The system is running in z/Architecture mode,

the high halves of the GPRs are not all zero, and the
ARs are not all zero:
AR/GR 0:
2:
4:
6:
8:
A:
C:
E:
aaaaaaaa/gggggggg_gggggggg
1:
3:
5:
7:
9:
B:
D:
F:

Detecting Module: IEAVTSYM
IEA996I
READ FOR JFCB/JFCBE FAILED,

STANDARD DUMP FORMAT ASSUMED
Explanation: While trying to determine the requested

format of a dump, the system tried to read the job file
control block (JFCB) or JFCB extension (JFCBE) for the
3800 printing subsystem. The system failed to read the
control block.
System Action: The system writes the dump in the
standard format of 120 characters per line. The system
The system sends messages about the problem to the
job log.
Application Programmer Response: Rerun the job. If
the problem recurs, notify the system programmer.

v Look at the messages in the job log.
v Collect all printed output and output data sets related
to the problem.
v Obtain the program listing for the job.
Detecting Module: IEAVAD01
IEA998I
PARTIAL SYSMDUMP TAKEN TO

dsname
Explanation: The system could write only a partial

SYSMDUMP ABEND dump to the data set on a direct
access storage device (DASD) and defined on the
SYSMDUMP DD statement. One of the following errors
occurred:
v An I/O error occurred while the system was writing
the dump to the dump data set.
v The dump data set was filled before the system
finished writing all dump data.
dsname
The data set specified on the SYSMDUMP DD
statement.
1. Print the SYSMDUMP data set. Enough data might
have been dumped to diagnose the problem that
caused the dump.
v Look at the messages in the job log.
2. Increase the size of the DASD data set specified on

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, IEAVAD01
IEA997I
READ FOR JFCB/JFCBE FAILED,

DUMP CANCELLED
Explanation: While trying to determine the requested

format for a SNAP or ABEND dump, the system tried to
read a job file control block (JFCB) or JFCB extension
(JFCBE) for the 3800 printing subsystem. The system
failed to read the control block.
System Action: The system cancels the dump. The
system returns a return code of X'08' to the program
that tried to read the JFCB or JFCBE.
The system sends messages about the problem to the
job log.
Application Programmer Response: Rerun the job. If
the problem recurs, notify the system programmer.
670
IEA999W
ADDRESS TRANSLATION ERROR IN

MASTER MEMORY
Explanation: The system encountered recursive

addressing translation exceptions. Possibly the segment
table (SGTE) or page tables (PGTE) for the master
scheduler address space were initialized incorrectly or
overlaid.
System Action: The system places all operating
systems on all processors in a wait state X'014'.
wait state X'014'. ReIPL the system.
Detecting Module: IEAVEPC
Chapter 16. IEB Messages

IEBA01I
IEBIMAGE UTILITY COMPLETE.

RETURN CODE = return-code
Explanation: The utility has completed processing.

The return code indicates the greatest severity of error
found in any of the requested operations:
00
Successful completion, operation(s) performed

as requested.
04
Operation(s) performed, investigate messages

for exceptional circumstances.
08
Operation(s) not performed. Investigate

messages.
12
Severe exception. Utility may end.
16
Catastrophic exception. Utility ended.
20
SYSPRINT data set could not be opened.

Utility ended.
24
User parameter list incorrect. Utility ended.
return-code
The return code.
IEBA03I
Explanation: A STOW macro has been issued but all

directory blocks for the data set specified by the
SYSUT1 DD statement have been used.
System Action: The IEBIMAGE program continues
processing the next control statement, but subsequent
writing to the library data set is inhibited.
Application Programmer Response: Using utility
programs such as IEBCOPY and IEHPROGM the data
set may be recreated, allowing for more directory
entries.
JCL, the SYSOUT output, and the source input for the
job.
Source: DFSMSdfp
IEBA04I
System Action: IEBIMAGE processing is ended.

return code to determine the degree of successful
processing. If the return code is 08 or greater, the
preceding messages must be investigated and resolved
and the job rerun.
SYSOUT output, the source input for the job, and all
problem.
Source: DFSMSdfp
NO SPACE IN DIRECTORY.
PERMANENT I/O ERROR IN

[DIRECTORY] devnum, devtyp, ddname,
op, errdes, lastskad, accmeth
Explanation: During writing to the specified library an

I/O error occurred.
devnum
The device number.
devtyp
The device type.
ddname
The DDNAME specified.
op
The operation.
errdes
A description of the error.
lastskad
IEBA02I
MEMBER (mem) {ADDED|REPLACED}

IN DIRECTORY
Explanation: The specified member has been placed

into the library and a directory entry added or replaced
in the PDS directory.
mem
The member name.

processing the next control statement.
The last seek address.
accmeth
The access method.
Application Programmer Response: Rerun the job.
Source: DFSMSdfp
Source: DFSMSdfp
671
IEBA05I
FCB SPECIFICATION BEYOND RANGE

OF FORM.
Explanation: The keywords supplied on the FCB

control statement have specified channel controls
beyond the last byte of the FCB image.
processing the next control statement, but writing to the
library data set for the current operation is inhibited.
FCB control statement and rerun the job.
problem.
Source: DFSMSdfp
IEBA06I
PARAMETERS SPECIFIED IN (LOC)

KEYWORD RESULT IN X(FF), AN
UNPRINTABLE CHARACTER.
Explanation: During processing of a TABLE operation,

the LOC keyword contained a parameter group in the
following specification (23, 3F, 03). The 3F index into
WCGM 03 is specifically reserved to represent an
unprintable character. The message does not inhibit the
construction of the character arrangement table, but this
character will not be printed.
Application Programmer Response: If an unprintable
character is desired, specify only the character
arrangement table location, that is (LOC=23). To specify
a printable character the WCGM or the CGMID
reference must be changed and the job rerun.
problem.
Source: DFSMSdfp

COPYMOD statements to optimize storage usage. If
more than 64 segments are needed for GRAPHIC, up
to four GRAFMODS can be created and their names
included into this appropriate character arrangement
table. For FCB, SIZE keyword determines maximum
number of lines. Respecify the control cards and rerun
the job.
problem.
Source: DFSMSdfp
IEBA08I
Explanation: No NAME control statement or no name

was specified on the NAME or INCLUDE statement.
missing 1- to 4-character name and rerun the job.
problem.
Source: DFSMSdfp
IEBA09I
MODULE TOO LONG OR TOO SHORT
Explanation: An INCLUDE statement referenced a

module that is too long or too short to be valid. If an
FCB module is being built, the length field is too large
for the virtual storage occupied by the module, or too
small to describe a valid FCB. Maximum size for
COPYMOD is 8196 bytes, and for GRAPHIC is 64
segments. For FCB, the LPI keyword specifies lines
beyond that specified by the SIZE keyword.
672
DUPLICATE MEMBER NAME FOR

(mem), MEMBER NOT ADDED.
Explanation: A request was made to add a member to

the specified library whose directory currently contains
the name of a member equal to that of the name of the
member to be added.
mem
IEBA07I
NO MEMBER NAME SPECIFIED.
The member name.

name of the member to be added or if the member
currently on the library is no longer needed, specify the
replace option (R) on the NAME control statement.

problem.
Source: DFSMSdfp
IEBA10I
MEMBER (mem) NOT FOUND.
Explanation: While processing the utility control

statements, the name specified could not be found on
the library directory. If this message precedes message
IEBA42I, control card specifications are erroneous;
otherwise it is an attention only message.
mem
The member name.

IEBA12I
CONTINUATION INVALID.
Explanation: A control statement was found that is not

in proper format for a continuation statement. Columns
1 through 15 must be blank and the continuation
information must start in column 16.
Application Programmer Response: Change either
the control statement that indicates continuation (it is
non-blank in column 72), or ensure that the subsequent
control statement is specified properly.
problem.
Source: DFSMSdfp

name specified is correct and resubmit the job if
necessary.
IEBA13I

problem.
Explanation: If an INCLUDE control statement

precedes a FCB control statement or a print-only
request, it is incorrect and is ignored. If multiple
INCLUDE statements are present, only the last
INCLUDE statement is used.
Source: DFSMSdfp
IEBA11I
FCB NOT MULTIPLE OF 1/2 INCH.
Explanation: The form length as described by the LPI

keyword is not a multiple of one half inch. Any lines not
specified by the LPI keyword default to 6 LPI, up to the
length of the form (as specified by the SIZE keyword).
PREVIOUS INCLUDE STATEMENT

INVALID FOR THIS OPERATION, IT IS
IGNORED.

Application Programmer Response: Remove
unnecessary INCLUDE statements and rerun job, if
necessary.
problem.
Application Programmer Response: Correct the LPI

keyword specifications and rerun the job.
Source: DFSMSdfp

problem.
IEBA14I
Source: DFSMSdfp
PARAMETER(S) INVALID FOR

KEYWORD (keywd).
Explanation: Parameters for the indicated keyword

have been incorrectly specified. There are too many
characters, or too many parameters, or incorrect
parameter specification. It may also mean that the
number of lines described by the LPI keyword exceeds
the length of the form as described by LINES or SIZE.
673
keywd

parameter specifications and resubmit the job.
problem.
Source: DFSMSdfp

problem.
Source: DFSMSdfp
IEBA17I
INVALID CONTROL CARD FORMAT.
Explanation: Either the control statement has an

incorrect label, or it is a blank card image.
control statement and resubmit the job.
Explanation: The indicated keyword is not valid for

the current operation.

problem.
Source: DFSMSdfp
IEBA15I
keywd
KEYWORD (keywd) INVALID FOR THIS

OPERATION.

problem.
Source: DFSMSdfp
IEBA16I
OPERATION INVALID - op
Explanation: The indicated operation is incorrectly

specified, is not in the proper sequence, or is missing a
name statement.
op
The operation.

IEBA18I
INVALID SEQUENCE FOR INITIAL

COPY NUMBER, IN SEGMENT segnum.
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
lower than the previous segment.
segnum
The segment number.
Application Programmer Response: Using the
INCLUDE with the DELSEG keyword, delete the
appropriate segments.
problem.
Source: DFSMSdfp

indicated control statement and rerun the job.
IEBA19I

Explanation: The indicated data set could not be

found during the issuance of an OPEN macro.
674
DATA SET NOT FOUND, DSNAME =

dsname
dsname
The specified dsname.
DD statement is correctly specified. Rerun the job.
problem.
Source: DFSMSdfp
IEBA20I
FAILURE DURING OPEN FOR DD =

ddname
Explanation: The indicated DDNAME statement was

incorrectly specified or not included in the JCL for this
job step. If the DDNAME=SYSIN, the LRECL of the
data set is probably not 80.
Application Programmer Response: Correct the DD
statement error and rerun the job. For SYSIN DD, also
ensure that the data set is allocated with LRECL=80.
problem.
Source: DFSMSdfp
JCL, the SYSOUT output, the source input for the job,
and all printed output and output data sets related to
the problem.
Source: DFSMSdfp
IEBA22I
INVALID CHARACTER IN CARD

COLUMN number
Explanation: An unexpected character was

encountered in the indicated column.
number The indicated column number.

problem.
Source: DFSMSdfp
IEBA23I
DUPLICATE OR MUTUALLY
EXCLUSIVE KEYWORD (keywd) FOR
OPERATION.
Explanation: The indicated keyword has been

specified more than once on this control statement, or
conflicts with other keywords or with the operation.
IEBA21I
INSUFFICIENT SPACE IN DATA SET dsname
Explanation: The indicated data set is full. A D37

ABEND which has been suppressed by the utility has
occurred.
dsname
The specified dsname.
Application Programmer Response: Using utility
programs such as IEBCOPY and IEHPROGM, the data
set may be recreated, allowing for more space.
keywd

control statement and rerun the job.
problem.
Source: DFSMSdfp

675
IEBA24I
SEGMENT NUMBER (segnum)

NONEXISTENT.
Explanation: The indicated segment number is

greater than the number of segments in the module
referenced.
segnum
The indicated segment number.
segment number specification in the DELSEG or the
REF keyword and rerun the job.
System Programmer Response: Run the IEBIMAGE
utility to print the applicable member. If the error recurs
problem.
Source: DFSMSdfp
IEBA25I
INSUFFICIENT KEYWORD
INFORMATION TO COMPLETE
OPERATION.
Explanation: Necessary keywords have not been

specified, preventing the requested operation from
completing successfully.
necessary keywords and rerun the job.
problem.
Source: DFSMSdfp
IEBA26I
INVALID USE OF DELIMITER IN

KEYWORD (keywd).
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.
676
keywd

problem.
Source: DFSMSdfp
IEBA27I
NO OPERATION DEFINED.
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).
control statement sequence and rerun the job.
problem.
Source: DFSMSdfp
IEBA28I
INVALID DATA SEQUENCE NUMBER.
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).
sequence number and rerun the job.

problem.
Source: DFSMSdfp
IEBA29I
MEMBER NAME OR REPLACE OPTION

INVALID.
Explanation: The name specified exceeds four

characters or the replace option (R) was incorrectly
specified.
problem.
Source: DFSMSdfp
IEBA30I
{GRAPHIC|CHARSET} DATA EXCEEDS

RANGE OF PITCH IN SEGMENT
segnum
Explanation: Data specified on the GRAPHIC or

CHARSET data cards requires a character be built
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 ($).
segnum
IEBA31I
NO VALID INPUT DATA FOR

{GRAPHIC|CHARSET} ASSIGN.
Explanation: The GRAPHIC or CHARSET operation

with an ASSIGN keyword is not followed by a data card
which has the data SEQ= in column 25 through 28.
Application Programmer Response: Supply
appropriate data cards and rerun the job.
problem.
Source: DFSMSdfp
IEBA32I
SIZE OF FORM IS nn.n INCHES (xxxx.xx

MM).
Explanation: The FCB form size is printed as a

number in inches and in millimeters (MM). This size was
specified or defaulted with the SIZE parameter.
nn.n
The size of the form in inches.
xxxx.xx The size of the form in millimeters.

problem.

Source: DFSMSdfp

problem.
IEBA33I
Source: DFSMSdfp
SEGMENT segnum COPY copynum LINE

linenum MAY CREATE A LINE
OVERRUN CONDITION IF PREVIOUS
LINE IS PRINTED AT {6|8|10|12} LINES
PER INCH.
Explanation: The segment with segment number

segno, in combination with all the previous segments,
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
677
per inch, the segment can be printed only at 6 lines per

inch.

problem.
Source: DFSMSdfp
segnum
copynum
The number of the copy in which the line
overrun condition may occur.
linenum
The line number in that copy.
The corresponding segment in the formatted listing is
flagged with the designation NOTE (n). If n is 0 (for
3800-3), 2, or 3, it indicates at least one overrun
condition for 12, 8, or 6 lines per inch respectively. If n
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).
COPYMOD statements such that each segment in
combination with preceding segments does not create a
line overrun condition when the copy modification
module is used. The OPTION statement with the
OVERRUN parameter can be used to suppress this
message.
problem.
IEBA35I
UNBALANCED PARENTHESIS IN
KEYWORD (keywd).
Explanation: The number of right parentheses does

not equal the number of left parentheses in the
indicated keyword.
keywd

problem.
Source: DFSMSdfp
IEBA36I
DUPLICATE CHANNEL SPECIFICATION

FOR PRINT LINE prtlnnum
Explanation: More than one channel specification has

been requested for the same print line (for example,
CH1=10, CH2=10).
Source: DFSMSdfp
prtlnnum
IEBA34I

CHARACTERS SPECIFIED IN TEXT

KEYWORD RESULT IN HEXADECIMAL
(FF).
Explanation: A specification in the TEXT keyword

which results in a hexadecimal (FF) is incorrect. FF
has been reserved for use within copy modification text
to denote a duplication factor.
678
The print line number specified.

problem.
Source: DFSMSdfp
IEBA37I
REFERENCES TO NONEXISTENT
CGMID WITHIN TABLE.
Explanation: One or more locations in the character

arrangement table reference a CGMID that has not
been defined in the trailer portion of the table.
problem.
Source: DFSMSdfp
correct the error, or rebuild the module using an

INCLUDE control statement with the DELSEG keyword,
and a GRAPHIC or CHARSET control statement with
the ASSIGN keyword and appropriate data cards.
problem.
Source: DFSMSdfp
IEBA40I
INCONSISTENT PITCH WITHIN

SEGMENT segnum
Explanation: In a graphic character modification

module that was either created or modified by other
than the IEBIMAGE utility, the indicated segment was
found to have inconsistent pitch.
IEBA38I
TABLE REFERENCES NO PRINTABLE

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).
problem.
segnum
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
the ASSIGN keyword and the appropriate data cards.
problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEBA41I
IEBA39I
INVALID PARITY IN SEGMENT segnum
Explanation: In a graphic character modification

module that was either created or modified by other
than the IEBIMAGE utility, the indicated segment was
found to have incorrect parity.
segnum
Application Programmer Response: Use SPZAP to
PREVIOUSLY USED {EBCDIC|WCGM}

ASSIGNMENT IN SEGMENT segnum
Explanation: A segment was found to have an

assignment value equal to that of one previously used
in the module. This error does not prohibit completion of
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
only the last of the duplicated assignments is built. All
previous library character set segments are ignored.
segnum
679

Application Programmer Response: For GRAPHIC
operations the unwanted duplicate segments can be
deleted by using an INCLUDE control statement with
the DELSEG keyword. An assignment value can be
changed by using the GRAPHIC control statement with
the REF keyword to change the EBCDIC assignment
value. For CHARSET operations the INCLUDE control
statement with the DELSEG keyword can be used to
delete any unwanted segments. An assignment value
can be inserted by using the CHARSET control
statement with the REF or ASSIGN keywords.
problem.
Source: DFSMSdfp
IEBA42I
MEMBER NOT ADDED TO LIBRARY,

ERROR(S) LISTED.
Explanation: Errors previous to this statement have

prevented the utility from updating the library with the
module specified in the current operation.
errors and rerun the job.
problem.
Source: DFSMSdfp
IEBA43I
IN SEGMENT segnum,
{COPY|LINE|TEXT} SPECIFICATION
BEYOND RANGE OF MAXIMUM
VALUE.
Explanation: One of the following values has been

exceeded:
COPY - 256
LINE - 133
TEXT - 205
The IEBIMAGE utility does not allow number of copies,
number of lines, or number of text characters per line
specifications to exceed certain values.
680
COPYThe number of the copy at which additional

printing is to begin, plus the number of copies, cannot
exceed 256.
LINEThe number of the line at which additional
printing is to begin, plus the number of lines, cannot
exceed 133. The IEBIMAGE utility allows the sum to be
133, which is valid for a 3800 using International
Standards Organization (ISO) paper sizes. If this value
is greater than 120 for a 3800 that uses common-use
paper sizes, the entry is never used.
TEXTThe number of the character at which additional
printing is to begin, plus the number of characters,
cannot exceed 205.
segnum
problem.
Source: DFSMSdfp
IEBA44I
SEQUENCE NUMBER INVALID OR

PREVIOUSLY USED.
Explanation: A data card sequence number of less

than 1, or one that has been used previously, has been
encountered.
card and resubmit the job.
problem.
Source: DFSMSdfp
IEBA45I
LIBRARY SPACE INCREASED TO nn

EXTENTS.
Explanation: After updating the library specified by the

SYSUT1 DD statement, it was found that the last record
was written on a different extent than the previous
update. The SYS1.IMAGELIB system data set can have
up to 16 extents.
nn
The number of extents.

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.
SYSOUT output and all printed output and output data
sets related to the problem.
IEBA47I
INSUFFICIENT VIRTUAL STORAGE TO

PERFORM STOW FUNCTION.
Explanation: A STOW SVC was issued and its

function was prohibited due to lack of virtual storage.
Application Programmer Response: Rerun the job.
The error may be a temporary one caused by
fragmentation of virtual storage.
problem.
Source: DFSMSdfp
IEBA48I
DUPLICATE TABLE REFERENCE FOR

LOCATION (loc).
Source: DFSMSdfp
Explanation: Specification for the same location in a

character arrangement table occurred more than once.
Each reference must be unique.
IEBA46I
REQUEST TO UPDATE LIBRARY

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
the next control statement but updating of the library
data set is inhibited.
different volume and/or obtain authorization to update
the subject data set.
problem.
Source: DFSMSdfp

problem.
Source: DFSMSdfp
IEBA49I
NO CHANNEL 1 CODE HAS BEEN

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
FCB does not contain the required channel code.
681

problem.
Source: DFSMSdfp
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
character location (CLOC) assignment was specified for
the graphic character module (GCM).
segnum
WCGM location in the second parameter of the REF
keyword for the CHARSET operation. All library
character set segments require a WCGM location
assignment between 00-3F.
problem.
Source: DFSMSdfp
IEBA51I
LIBRARY NOT UPDATED: MODULE

CONTAINS NO DATA
Explanation: The module being created contains no

data. This may have been caused by a DELSEG
parameter on an INCLUDE statement which deleted all
the segments of the module.
problem.
Source: DFSMSdfp
IEBA52I
VALUE OF LINES CONTRADICTS

VALUE OF SIZE
Explanation: When building an FCB module for the

3800, 3262 model 5, or 4248 printer, the specifications
for the LPI, LINES, and SIZE parameters on the FCB
statement were conflicting.
FCB statement with complementary values for the
LINES, SIZE, and LPI parameters. See the IEBIMAGE
chapter in OS/390 DFSMSdfp Utilities for the default
value of each parameter.
problem.
Source: DFSMSdfp
IEB001I
{SYSUT1|SYSUT2|SYSIN} NOT
OPENED
Explanation: The SYSUT1, SYSUT2, or SYSIN data

set, as indicated in the message text, could not be
opened. Either the DD statement defining the data set
was not included in the input stream, or a DCB
parameter for the data set was incorrect.
System Action: The job step is ended. The return
code is 8.
error. Ensure that a DD statement for SYSUT1,
SYSUT2, and SYSIN is included in the input stream,
and that the parameters on the DD statements are
correct (particularly that the block size specification is a
multiple of 80). Resubmit the job.
the problem.
Source: DFSMSdfp
IEB008I
INVALID NAME FIELD
Explanation: The name field is incorrect in the EDIT

statement preceding this message. Possibly, the name
field consists of more than 8 characters or contains an
incorrect character.
682
EDIT statement. The return code is 4.

error. Correct the name field on the preceding
statement. Resubmit the job to process either the entire
input stream or the unedited portion of the input stream.
the problem.
Source: DFSMSdfp
IEB009I
INVALID STATEMENT SYNTAX
Explanation: The EDIT statement preceding this

message is coded incorrectly.
error. Correct the preceding statement. Resubmit the job
to process either the entire input stream or the unedited
portion of the input stream.
the problem.
Source: DFSMSdfp
IEB010I
INVALID OPERATION CODE
Explanation: The preceding statement is not an EDIT

utility control statement. Possibly, EDIT is misspelled.
error. Correct the operation on the preceding control
statement to EDIT. Resubmit the job to process either
the entire input stream or the unedited portion of the
input stream.
the problem.
Source: DFSMSdfp
IEB011I
INVALID OPERAND
Explanation: The operand is incorrect in the EDIT

statement preceding this message. Possibly, a
parameter is misspelled or incompatible parameters are
specified.
error. Correct the operands on the preceding control
the problem.
Source: DFSMSdfp
IEB014I
INVALID DELIMITER
Explanation: A delimiter is incorrect in the EDIT

statement preceding this message.
delimiters on the preceding control statement. Resubmit
the job to process either the entire input stream or the
unedited portion of the input stream.
the problem.
Source: DFSMSdfp
IEB020I
INVALID CONTINUATION CARD
Explanation: The continuation does not begin at

column 16 in the statement preceding this message.
error. Begin the continuation statement in column 16 or,
if no continuation is desired, correct the statement that
indicated a continuation. Resubmit the job to process
either the entire input stream or the unedited portion of
the input stream.
683

the problem.
Source: DFSMSdfp
IEB021I
INVALID CHARACTER
Explanation: A character is incorrect in the EDIT

statement preceding this message.
error. Correct the error in the control statement.
Resubmit the job to process either the entire input
stream or the unedited portion of the input stream.
the problem.
Source: DFSMSdfp
IEB022I
JOB NAME NOT FOUND BEFORE END

OF FILE
Explanation: Either no JOB statement was found in

the input data set, or the specified job could not be
found.
code is 4.
error. Insert the missing JOB statement into the input
stream or correct the control information on the
associated EDIT statement. Resubmit the job.
the problem.
Source: DFSMSdfp
IEB023I
sss STEP COULD NOT BE FOUND
Explanation: The step could not be found in the input

data set. Possibly, the step name was misspelled.
sss
The indicated step.

684

error. Insert the missing step into the input stream or
correct the control information on the associated EDIT
the problem.
Source: DFSMSdfp
IEB024I
high WAS HIGHEST SEVERITY CODE
Explanation: The return code was the highest return

code generated during processing of the IEBEDIT
program.
high
The highest return code generated.
Application Programmer Response: For other than

successful job completion (severity code= 0), resubmit
the job to process either the entire input stream or the
unedited portion of the input stream.
the problem.
Source: DFSMSdfp
IEB027I
I/O ERROR dsname, jjj, sss, ddd, devtyp,

ddname, op, err, xxxx, acc
Explanation: A permanent input/output error occurred

while processing on the device.
In the message text, the error analysis information
provided by the SYNADAF data management macro
issued by the SYNAD routine was:
dsname
Data set name.
jjj
Job name.
sss
Step name.
ddd
Device number of the device.
devtyp
Device type.
ddname
Data definition name.
op Operation attempted.
err Error description.
xxxx
Last seek address or block count.
acc
Access method.
System Action: The program is ended. The return
code is 8.
error condition indicated in the message text according
to the error analysis information provided by the
SYNADAF data management macro instruction.
Resubmit the job.
the problem.
Source: DFSMSdfp
IEB030I
{SYSUT1|SYSIN} BLKSIZE INVALID
Explanation: The block size of the SYSUT1 or SYSIN

data set, as indicated in the message text, is not a
multiple of 80 bytes.
code is 8.
error. Correct the block size of the indicated data set
and resubmit the job.
the problem.
Source: DFSMSdfp
IEB032I
SYSUT2 BLKSIZE INVALID - SYSUT1

ASSUMED
Explanation: The block size of the SYSUT2 data set

is not a multiple of 80 bytes.
System Action: The SYSUT1 block size attributes are
assumed for the SYSUT2 data set. Processing
continues. The return code is 4.

the problem.
Source: DFSMSdfp
IEB033I
STATEMENT NOT PROCESSED EOF

ON SYSUT1
Explanation: An end-of-file condition was encountered

on the SYSUT1 data set. The preceding EDIT
statement was not processed.
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
IEB034I
STEPNAME REQUIRED WITH TYPE=

{INCLUDE|EXCLUDE}
Explanation: No step name was specified with a

TYPE=INCLUDE or TYPE=EXCLUDE operation, as
indicated in the message text.
error. Correct the condition indicated in the message
text. Resubmit the job to process either the entire input
stream or the unedited portion of the input stream.
the problem.
Source: DFSMSdfp

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.
685
IEB100I
I/O ERROR READING MEMBER

memname

reading the specified member. Message IEB139I, which
gives detailed information regarding the location of the
error record, is always issued previous to this message.
v On a different channel.
the problem.
memname
Source: DFSMSdfp
System Action: The next COPY control statement is

sought unless a data check occupies the key or data
portion. In this case, the error is ignored and data is
copied as it came into main storage. If the copy is
performed, the return code is 4; if not, the return code is
8.
IEB102I

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 member NOT {COPIED |

LOADED | UNLOADED} DUE TO I/O
ERROR
Explanation: An I/O error on the SYSUT3 work file

has made processing of the member impossible. If
******** replaces the member name in the above
message, the error was found reading from SYSUT3.
member
The name of the member.
v On a different device.
The severity is 8.
If the error is on an input data set, it may be necessary

to re-create the data set.

member to be copied.

the problem.
Application Programmer Response: Retry the failing

operation, and either:
Source: DFSMSdfp
IEB101I
I/O ERROR WRITING MEMBER DATA

AT TTR=ttr [-DURING READ BACK
CHECK]
Explanation: An I/O error occurred while copying

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
error occurred during a read back check.
v Remove the SYSUT3 DD statement and increase the

work area size as previously indicated in previously
message IEB1051I.
v Use a different SYSUT3 data set. Place the SYSUT3
data set on a different physical location on the
volume, on a different device, or on a different
channel.
System Programmer Response: Use the IEHLIST
utility to investigate the output directory and determine
which member(s) were not copied.
IEB103I
ttr
The logical disk address.
System Action: If the error was encountered during

read back check and involved a data check in key or
data only, the error is ignored, and the return code is 4.
Otherwise, the next COPY control statement is sought,
and the return code is 8.
the type of error, rerun the COPY operation with the
data set in error allocated:
686
MEMBERS member THRU END OF

DATASET ARE NOT ACCESSIBLE DUE
TO I/O ERROR
Explanation: Due to an I/O error while updating the

output data sets directory, members starting from the
named member, member, through the end of the data
set (in alphameric order) have become inaccessible.
member
The name of the member.
The severity is 12.
System Action: The operation is ended and the next
control statement is sought.

operation. Use a different output data set. Place the
data set on a different physical location on the volume,
on a different device, or on a different channel.
output data set directory is large enough. If the error
the JCL and all printed output and output data sets
IEB104I
INVALID COMMAND OR KEYWORD
Explanation: A command or keyword on the control

statement just listed is misspelled or is incorrect for the
IEBCOPY program.
The severity is 8.
control statement.
the problem.
IEB106I
UNEQUAL PARENTHESIS
Explanation: The statement just listed has an

unbalanced number of parentheses.
The severity is 8.
control statement.
the problem.
IEB107I
Explanation: The control statement just listed is

incorrect.
(1) Parameters may have ended with a comma (which
implies continuation), but the continuation column (72)
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.
The severity is 8.

IEB105I

control statement.
PARAMETER INVALID
Explanation: A parameter on the control statement

just listed is too long or contains an incorrect character.
The severity is 8.
control statement.
the problem.

the problem.
IEB108I
MEMBER WITHOUT SELECT OR

EXCLUDE
Explanation: A control statement containing a

MEMBER= operand has been encountered. The
operand can not be associated with a previous SELECT
or EXCLUDE statement. The control statements are out
of order or a SELECT or EXCLUDE statement is
missing.
The severity is 8.
687

Application Programmer Response: Place each
MEMBER= following a SELECT or EXCLUDE statement
or MEMBER= operand.
the problem.
IEB109I
NO MIXING OF SELECT AND EXCLUDE

MODES IN SAME COPY STEP
Explanation: A SELECT statement immediately

follows an EXCLUDE statement without an INDD=
statement between, or vice versa.
The severity is 8.
Application Programmer Response: Divide the
operation into two operations. Place all SELECT
statements in one and all EXCLUDE statements in the
other.
the problem.

the problem.
IEB111I
NULL PARAMETERS
Explanation: A control statement was completely

blank, or blanks followed the equal sign immediately
after a keyword.
No blanks are allowed inside or between any operands
on the same input record.
The severity is 8.
control statement.
the problem.
IEB112I
CANNOT RENAME/REPLACE ON
EXCLUDE
Explanation: The control statement just listed has a

parameter embedded within parentheses, requesting a
rename or replace of this member. This is not allowed
during an exclusive copy operation.
The severity is 8.
IEB110I
INVALID REPLACE SPECIFIED
Explanation: Parentheses are missing from an INDD=

operand list or a MEMBER= operand list, or unbalanced
parentheses have been found.

control statement.
Each member_name/newname/replace triplet or

DD_name/replace pair must appear in parentheses.
When the first operand of a INDD= or a MEMBER=

operand indicates a replace or rename then the entire
operand must be enclosed in two sets of parentheses.
IEB113I
The severity is 8.
control statement.
688
OUTDD OR INDD NOT SPECIFIED
Explanation: The commands are incomplete. An

INDD= keyword must be associated with a COPY
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.
IEB116I

the problem.
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.
MIXING CONTROL STATEMENTS

FROM OLD AND NEW VERSION OF
IEBCOPY
The severity is 8.
System Action: IEBCOPY ends, leaving control

statements unprocessed.
IEB114I
If a complete set of valid statements (i.e. all old format

or all new format) occurred together, then the operation
was performed. If the statements were intermixed, no
operation was performed after the point where the
change in format was detected.
OUTDD/LIST NOT ON COPY CARD
Explanation: The OUTDD= or LIST= keywords were

scanned, but they were not physically or logically
associated with the COPY, COPYMOD, or ALTERMOD
statement.
The severity is 8.
control statement.
the problem.
IEB115I
END OF FILE ON SYSIN
Explanation: The end of the control statement file was

reached when more control statements were needed to
complete the current operation. Previous error may also
have caused IEBCOPY to expect more statements.
Application Programmer Response: Convert the old

format control statements to new format.
the problem.
IEB117I
TABLES EXCEED ALLOCATED

STORAGE -- INCREASE WORK=
VALUE IN PARM FIELD
Explanation: The number of names from {INDD} and

{SELECT} or {EXCLUDE} statements have grown too
large. The virtual storage available for saving the names
has been exceeded.
The severity is 8.
The severity is 0.

System Action: IEBCOPY ends because no more

operations remain.
Application Programmer Response: Do either of the

following:

preceding error or supply control statements.
v Make more virtual storage available to IEBCOPY.

Make more virtual storage available to IEBCOPY.
See message IEB1055I.

the problem.
v Split the operation into multiple operations to

decrease the maximum number of DDNAMEs and
member names in any one operation.
and the program listing for the job.
689
IEB118I
CONTROL STATEMENT ERROR
Explanation: The statement just listed has an

incorrect command, keyword, or parameter.
perform the current operation.

ddname
The DDNAME.
The severity is 8.
Application Programmer Response: Check for
multiple INDD= keywords on the same statement, or
statements that mix old and new format keywords.
The severity is 8.
Application Programmer Response: Correct any
errors diagnosed by accompanying messages.


IEB119I
IEB121I
STATEMENT SEQUENCE ERROR
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

COPY statements, is either incomplete or out of
sequence.
ddname
The DDNAME.
v The first COPYMOD statement, in a contiguous

series of COPYMOD statements, is either incomplete
or out of sequence.
The severity is 8.
v IEBCOPY control statements from a release prior to

OS Release 20 are not in the correct sequence.

The severity is 8.
If old format statements were used then IEBCOPY
ends.
Application Programmer Response: Correct any

incorrect DD statement parameters.
accompanying IEBCOPY and IEC, IGD, IGW, and IOS
prefix messages.

control statements.
IEB122I

Explanation: The data set associated with the DD

statement named in accompanying message IEB120I
was not on the volume (taken from the catalog or the
DD statement), or the volume could not be mounted.
IEB120I
ddname VALIDATION ERROR
Explanation: The data set cannot be used. The next

message(s) explain the error encountered while opening
or validating the data set.
The DD statement may be missing, or the identified
data set may be missing, or the data set may have DCB
attributes which are not permitted, or the data set
attributes may conflict among the data sets required to
690
DSCB COULD NOT BE OBTAINED.

OBTAIN RC=return-code REASON
CODE=reason
return-code
The OBTAIN macro return code.
reason
The OBTAIN macro reason code.
The severity is 8.
named volume is the correct volume, and if it is, verify
that it does contain the data set. In a system with

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.
Refer to IGD and IEF prefix messages in the JCL
message data set to verify which volume contains a
SMS managed data set.
the problem.
Problem Determination: The IDCAMS utility may be
used to display the volume on which a cataloged data
set is supposed to reside. The IEHLIST utility may be
used to display the names of data sets which resident
on a specific volume.
IEB123I
INVALID DSORG (X'hhhh')
Explanation: The data set associated with the DD

statement named in accompanying message IEB120I
does not have partitioned or physical sequential
organization.
One of the following may have occurred:
1. The data set has never been opened for output,
therefore the DSORG field in the data set label is
uninitialized.
2. A data set intended for output is being used for
input because of incorrect control statements.
3. The data set is not a PDS, but a VSAM, or
SYSOUT data set, etc.
4. DSORG has been incorrectly coded in the JCL.
hhhh
The data set organization code.

IEB124I
INVALID LRECL (nnnnn)
Explanation: The logical record length of the 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).
therefore the BLKSIZE and LRECL fields in the data
set label are uninitialized.
4. RECFM has been incorrectly coded in the JCL.
nnnnn
The record length tested.
The severity is 8.
IEBCOPY control statements. Verify that the job which
created the data set was successful. Verify the
BLKSIZE and LRECL used when allocating the data
set.
System Programmer Response: The IEHLIST utility
may be used to display the logical record length 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
Support Center. Provide the JCL and all printed output
and output data sets related to the problem.
The severity is 8.
created the data set was successful. Verify the DSORG
used when allocating the data set.
The IEHLIST utility may be used to display the DSORG
in the data set label.
Center. Provide the JCL and all printed output and
IEB125I
INVALID BLOCK SIZE (nnnnn)
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).
therefore the BLKSIZE and LRECL fields in the data
set label are uninitialized.
4. DSORG or RECFM has been incorrectly coded in
the JCL.
691
nnnnn
IEB127I
The actual block size.
RECFM INCOMPATIBLE -- INPUT

RECFM=iiii OUTPUT RECFM=oooo
The severity is 8.
Explanation: The record format of the input data set is

incompatible with that of the output data set.

IEBCOPY can not copy from fixed-length record format

to variable-length record format or the reverse.

created the data set was successful. Verify the
BLKSIZE and LRECL used when allocating the data
set.

may be used to display the block size in the data set
label. If the error recurs and the program is not in error,
The severity is 8.

IEB126I
ddname REFERENCES AN
UNMOVABLE DATA SET
Explanation: The input data set is flagged as

unmovable in its DSORG. An unmovable data set can
not be compressed in place or copied because it may
contain location dependent data.
ddname
The DDNAME.
The severity is 8.
created the data set was successful. Verify the DSORG
used when allocating the data set.
If the data set does not contain location dependent
data, then supply a DSORG override on the DD
statement and retry the operation.
may be used to display the DSORG in the data set
iiii
The input record format.
oooo
The output record format.

RECFM of each data set. If they are correct, then
IEBCOPY can not be used to copy the data set.
may be used to display the RECFM in the data set
IEB128I
CANNOT REBLOCK TRACK

OVERFLOW DATA SET
Explanation: The input and/or output data set(s) have

track overflow records. Reblocking operations can not
be done.
The severity is 8.
Application Programmer Response: Perform one of
the following actions:
(1) Copy the data set to a new data set without track
overflow.
(2) Reallocate the output data set so that it has a block
size that is consistent with the input data set block size
(so that reblocking will not be done).
the problem.
692
IEB129I
CANNOT REBLOCK KEYED DATA

SETS
Explanation: The input and/or the output data set(s)

have keyed records. Reblocking operations can not be
done.
The severity is 8.
Application Programmer Response: Reallocate the
output data set so that it has a block size that is
consistent with the input data set block size (so that
reblocking will not be done).
the problem.
The severity is 8.
Application Programmer Response: Make a full
copy to a new data set. Substitute this
the problem.
IEB132I
INVALID RE/DE-BLOCKING. INPUT

BLKSIZE IS inblksz, OUTPUT BLKSIZE
IS outblksz.
Explanation: The input data set block size is

incompatible with the output data set block size.
For fixed length records, the size of each block must be

a multiple of the logical record length.
IEB130I
For variable length records the output block size must

be equal to or greater than the input logical record
length.
KEY LENGTHS UNEQUAL. INPUT KEY

LENGTH IS inlen, OUTPUT KEY
LENGTH IS outlen.
Explanation: The key length of the input data set and

key length of the output data set are not equal.
For undefined length records the output block size must

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.
Application Programmer Response: Reallocate the
output data set so that it has the same key length as
the input data set key length.
may be used to display the key length in the data set
IEB131I
CANNOT COMPRESS KEYED DATA

SET
The severity is 8.
System Action: For RECFM=U data sets, the copy
operation continues. For all other RECFM, the copy
operation ends.
output block size to allow this member to be properly
copied. Copying a larger block size to a small block size
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.
the problem.
Explanation: A compress-in-place operation was

requested, but the data set contains keyed records.
IEBCOPY does not compress keyed data sets in place.
693
IEB133I
MINIMUM REQUESTED STORAGE

(amount) NOT AVAILABLE
Explanation: IEBCOPY could not obtain a work area

of even minimum size.
amount The number of bytes of virtual storage that

must be available to IEBCOPY for use as a
work area.
The severity is 16.
System Action: IEBCOPY ends processing.
Application Programmer Response: Make more
virtual storage available to IEBCOPY. Make more virtual
storage available to IEBCOPY. See message IEB1055I.
IEB134I
CANNOT COMPRESS WITH SELECT

OR EXCLUDE

v Divide the operation into several operations with each
operation using fewer members.
IEB136I
CANNOT ALLOCATE TWO TRACKS OF

I/O BUFFERS FOR COMPRESS
Explanation: There is not enough unallocated virtual

storage available to contain 2 buffers, each the (device
dependent) track size. COMPRESS operations must
have this much I/O buffer space for full track I/O and
synchronization.
The severity is 8.
Explanation: The input and output data set are the

same data set, which implies a compress-in-place. A
SELECT or EXCLUDE statement is also present, which
is not allowed for a compress-in-place operation.

The severity is 8.


the problem.
IEB135I
MINIMUM I/O BUFFER NOT

ALLOCATABLE
Explanation: IEBCOPY obtained the largest size work

area available from virtual storage. It was not large
enough to contain two minimum size I/O buffers and the
tables built from INDD=, SELECT, and/or EXCLUDE
statements.
The severity is 8.
694

v Make a full copy to a new data set. Substitute this

IEB137I
CANNOT SPECIFY DUPLICATE

MEMBER NAMES FOR
SELECT/EXCLUDE/RENAME DUPLICATE IS member
Explanation: The member name appears more than

once in the SELECT or EXCLUDE statements for this
operation. It may be both an old name and a new
name.
All names on SELECT or EXCLUDE statements in one
operation must be unique, even if the name is used
once as a old name and once as a new name.
READING PDS
member
The severity is 4.
System Action: The operation is not performed for the
named members. Processing continues for the
uniquely-named members.
Application Programmer Response: If duplicate
names must be specified, create additional operations.
System Programmer Response: Check for duplicate
renamed old names, duplicate old names that were not
renamed, duplicate new names, or a combination of
these.
Center. Provide the JCL and the program listing for the
job.
IEB138I
CANNOT PROCESS ALL

OLD/NEW-NAMES SPECIFIED
Explanation: The virtual storage required to hold pairs

of old and new names (of members being renamed) is
not available.
The severity is 8.
v Divide the operation into several operations with each
operation using fewer members.
IEB139I
I/O ERROR activity synad_text
Explanation: An I/O error has occurred, the

SYNADAF macro was issued, and SYNAD text was
generated by the SYNADAF macro.
WRITING PDS
READING UNLOADED PDS
WRITING UNLOADED PDS
GET FROM CONTROL STMT FILE
PUT TO MESSAGE FILE
DURING ERASE
DURING READBACK CHECK
DURING READ
DURING WRITE
DURING LOAD
DURING UNLOAD
synad_text
The text issued by the SYNAD macro.
the type of error, retry the operation with the data set in
error allocated:
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.
the problem.
activity The activity taken, as follows:

695
IEB140I
ddname REFERENCES A NULL INPUT

DATA SET
Explanation: The data set contains no members.

ddname
The DDNAME.
IEB142I
CANNOT CONTINUE TO BUILD

CTLTAB
Explanation: More virtual storage is required to build

the required control table to process the current
operation.
The severity is 8.
The severity is 0.

System Action: The next input data set or control

statement is sought.


operation which created the input data set.


the problem.
IEB141I
CAN NOT RE/DE-BLOCK WITH

NOTE-LIST/USER TTRN IN MEMBER
member
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
copied because the input and output data set attributes
are different.
The reblocking will make the Notelist data incorrect so it
is not allowed. If this member is to be copied, it cannot
be reblocked.
member
The specified member.
v If the operation is not already a selective copy, then

obtain a list of all members in the data set using the
IEHLIST utility. Divide the operation into multiple
selective copy operations. Each one should copy
approximately the same number of members.
v If the operation is already a selective copy, then
divide the operation into several operations each
specifying fewer members.
IEB143I
ALL SELECTED MEMBERS {COPIED |

LOADED | UNLOADED}- DID NOT USE
ALL SPECIFIED INDDS
Explanation: All specified (selected) members have

been successfully copied, and there are still data sets in
the INDD list which have not yet been examined. It was
not necessary to use all specified input data sets in
order to locate all the selected members.
The severity is 8.
The severity is 0.

System Action: The next control statement is sought.

factors which cause reblocking (the BLKSIZE, RECFM,
LRECL of the two data sets), so that reblocking will not
take place. Retry the operation.
the problem.
696
Application Programmer Response: See messages

IEB154I, IEB155I, and IEB167I. Verify that each
member copied came from the expected data set.
the problem.
IEB144I
THERE ARE nnnnn UNUSED TRACKS

IN OUTPUT DATASET REFERENCED
BY ddname
Explanation: This message is issued after completing

the operation to the output partitioned data set.
If an error has occurred, the number of tracks given in
this message may be incorrect.
nnnnnn The number of tracks available in the data set.

ddname
The DDNAME.
The severity is 0.
Application Programmer Response: If not enough
space remains available, adding a compress-in-place
operation may make additional space available.
done during a compress-in-place operation.

The severity is 8.
v Avoid reblocking by specify the same DD statement
for both INDD= and OUTDD=.
v Make a full copy to a new data set. Substitute this
same DCB parameters are specified on each DD
statement. If the error recurs and the program is not in

END OF JOB - return-code WAS
HIGHEST SEVERITY CODE
IEB147I
IEB145I
CANNOT COMPRESS TRACK

OVERFLOW DATA SET
Explanation: IEBCOPY does not allow a

compress-in-place operation to be done if the track
overflow bit has been set in the format 1 DSCB of the
output data set. (This bit is the DCBRECTO bit in the
DS1RECFM field.)
Explanation: This message is issued after all

operations have been finished.
return-code
The highest return code from any

operation.
The severity is 8.
The severity is 0.

System Action: IEBCOPY ends. When the severity

code is other than 0, message IEB151I will also be
issued.

Consider not using the track overflow feature.
may be used to examine the RECFM in the data set
label for track overflow. Look for an override on the DD
statement. If the error recurs and the program is not in
IEB146I
CANNOT COMPRESS WITH

RE/DE-BLOCKING
Explanation: The compress-in-place operation can not

alter the block size or record length of a data set. The
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
different attributes imply reblocking, which can not be
Application Programmer Response: Verify that all

operations completed as expected.
System Programmer Response: Consult message
IEB151I if issued.
IEB148I
NO SPACE IN OUTPUT DIRECTORY

FOR DIRECTORY ENTRIES FROM
INPUT DATA SET ddname
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
insufficient.
ddname
The DDNAME.
The severity is 8.
System Action: If message IEB168I does not
697
immediately follow this message, the output data set

directory reflects those members copied through the
immediately preceding input data sets. If this data set is
the first input data set in the operation, the output data
set is unchanged.
If the message IEB168I does follow, the output directory
is truncated.
The operation is ended and the next control statement
is sought.
Application Programmer Response: Allocate a new
output data set large enough to contain all the members
in the old output data set plus the members from the
input data set(s). Retry the operation to the new output
data set.
may be used to display the members present in the
output data set. 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
ddname
The DDNAME.
The severity is 4.
System Action: IEBCOPY attempts to write the output
directory in a structure identical to that of the input data
set directory. This concludes the current operation and
the next control statement is sought.
Application Programmer Response: The data may
be recovered with this procedure: Allocate a new data
set. Perform a selective copy to move approximately
half of the members from the broken data set to the
new data set. Repeat a separate selective copy
operation to move the remaining members.
System Programmer Response: Dump the directory
with SPZAP and determine its structure. Examine the
program that created the input data set for defects.
IEB151I

IEB149I
THERE ARE nnnnn UNUSED

DIRECTORY BLOCKS IN OUTPUT
DIRECTORY
Explanation: This message is issued after completing

the operation to the output partitioned data set identified
in message IEB144I.
If an error has occurred, the number of blocks given in
this message may be incorrect.
nnnnn
The number of whole 256 byte directory blocks

available for additional member name.
The severity is 0.
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
copied to it.
JOB HAS TERMINATED WITH

ERROR(S)
Explanation: IEBCOPY issued a message of severity

4 or greater. One or more operations were not
The severity is 0.
System Action: IEBCOPY is finished operating and
will end.
errors indicated by preceding error messages, and retry
the operations not successfully completed.
System Programmer Response: Look up the severity
code of each issued message. Many IEBCOPY suffix I
messages have a severity code greater than zero. If the
error recurs and the program is not in error, look at the
member COMPRESSED - WAS

ALREADY IN PLACE AND NOT MOVED
IEB152I
IEB150I
Explanation: The member did not need to be

physically moved during the compress-in-place
operation.
**WARNING** THE OUTPUT DATASET

REF BY ddname CONTAINS TOO MANY
DIRECTORY BLOCKS PER TRACK
Explanation: Because of short or damaged directory

blocks, more blocks were encountered than were
expected. Errors will probably result if the is accessed
by other programs. The BLDL and STOW functions are
particularly vulnerable.
698
member
The severity is 0.

IEB153I
ALL MEMBERS COMPRESSED - ALL

WERE ORIGINALLY COMPRESSED
Explanation: The data set was not in need of being

compressed because all member data is contiguous at
the front of the data set. No members from this data set
were physically moved.
The severity is 0.
IEB154I
member HAS BEEN SUCCESSFULLY

{COPIED | LOADED | UNLOADED |
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.
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
device. The data set is identified as a PDS or PDSE
which must always reside on a direct access device.
The severity is 8.
Application Programmer Response: Check that the
data set is on a direct access volume.
the problem.
IEB157I
ddname DD STATEMENT NOT FOUND
In a compress-in-place operation, this message may be

issued for members not actually moved (as identified in
message IEB152I).
Explanation: The DDNAME DD statement was not

supplied either in the JCL or by dynamic allocation
before IEBCOPY was invoked.
member
ddname
The DDNAME.

The severity is 0.
The severity is 8.


IEB155I
member HAS BEEN SUCCESSFULLY

ALTERED}AND IS A NEW NAME
Explanation: The member, which is a new name, has

been successfully copied, loaded, or unloaded from the
input data set to the output data set, or altered in the
output data set.
The old name of this member can be determined by
checking the IEBCOPY control statement(s) listed at the
beginning of the operation which issued this message.

spelling of ddname in the control statement. If it is
spelled correctly then include the missing DD statement,
or allocate a DDNAME file before invoking IEBCOPY.
the problem.
IEB158I
member
Explanation: PARM=COMPRESS was specified on

the JCL EXEC statement, and new format control
statements are being used. New format statements do
not use PARM=COMPRESS to request a compress.

The severity is 0.
PARM=COMPRESS NOT VALID

Compress-in-place will be done only if it is requested in
a subsequent COPY statement.
699

is informational only. It indicates that the
PARM=COMPRESS parameter from the EXEC
statement is ignored. Remove this parameter from the
JCL to avoid further occurrences of this message.
If IEBCOPY is dynamically invoked then
PARM=COMPRESS is in the parameters passed to
IEBCOPY by the caller.
IEB159I
NO MEMBERS {COPIED | LOADED}

FROM INPUT DATA SET REFERENCED
BY DDNAME
Explanation: The input data set was not used for one
v A selective copy was specified, but none of the
members to be copied were on this data set.
v All of the members which should have been copied
from this input data set had names which were
duplicates of member names on the output data set
and replace was not specified.
v An I/O error (indicated by a previous message) has
precluded use of members from this input data set.
v Either the input or the output data set contains
duplicate or out-of-sequence members (indicated by
a previous message).
ddname
The DDNAME.
The severity is 0.
System Action: The next input data set will be
processed unless an error has occurred.
If an I/O error has occurred, or if there are duplicate or
out-of-sequence members, actions taken are indicated
by previous message(s).
Application Programmer Response: If an error
occurred, correct it as indicated in the above
explanation.
If no error occurred, verify that the processed members
were found in the data sets expected to contain them.
System Programmer Response: Examine messages
IEB154I, IEB155I, and IEB167I to verify that each
member came from the expected data set. If the error
IEB160I
CONCATENATED DATA SETS
Explanation: The DDNAME identified in message

IEB120I is a concatenation of data sets. IEBCOPY does
not process concatenated data sets.
The severity is 8.
Application Programmer Response: If more than
one input data set is to be used in the copy step,
provide a separate DD statement for each, and include
all the DDNAMEs in an INDD= utility control statement
parameter.
the problem.
IEB161I
COMPRESS TO BE DONE USING INDD

NAMED ddname
Explanation: A request for a compress-in-place

operation has been detected. This occurs when the
input and output DD statement(s) identify the same data
set and volume.
Before attempting a compress-in-place operation a
backup to the data set should be made so that it can be
recovered should the compress-in-place fail.
ddname
The DDNAME.
The severity is 0.
System Action: A compress-in-place operation is
started.
System Programmer Response: If compress-in-place
was not intended, check that both DD statements do not
specify identical data set name and volume serials.
IEB162I
PARM=COMPRESS IGNORED
Explanation: PARM=COMPRESS is specified, but the

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

is informational only. Remove the PARM=COMPRESS
parameter from the JCL to avoid further occurrences of
this message. If a COMPRESS is desired, correct the
DD statements or the INDD= and OUTDD= control
statement parameters.
the problem.
IEB165I
member FOUND BUT NOT {COPIED |

LOADED | UNLOADED}DUE TO I/O
ERROR READING INPUT DIRECTORY
Explanation: The member indicated was found in the

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 severity is 12.
System Action: The member is not processed.
IEB163I
NO MEMBER NAMES FOR PARTIAL

COPY, WILL NOT COPY
Explanation: The version of IEBCOPY statement from

a release prior to OS Release 20 specified
TYPCOPY=I, but it was not followed by any MEMBER=
statements.
Application Programmer Response: Retry the

operation. If the operation fails a second time, suspect
that a hardware error has occurred. The data set may
have to be restored. Contact your systems programmer
or hardware support personnel.
The severity is 8.
System Action: The job step is ended.
IEB166I
Application Programmer Response: Correct and

convert the control statement to new format.
NO MEMBERS {COPIED | LOADED |

UNLOADED} TO DATA SET
REFERENCED BY ddname
Explanation: Due to the validation error described in a

previous message, the operation did not take place. The
data set was not changed.
ddname
The DDNAME.

The severity is 8.
IEB164I
TOTAL COPY ASSUMED
Explanation: The version of IEBCOPY statement from

a release prior to OS Release 20 specified
TYPCOPY=E, but it was not followed by any MEMBER=
statements.
The severity is 4.

Application Programmer Response: Refer previously
issued messages for the reason.
IEB167I
System Action: A full copy is done.

Application Programmer Response: Correct and
convert the control statement to new format.
FOLLOWING MEMBER(S) {COPIED |

LOADED} FROM INPUT DATASET
REFERENCED BY DDNAME
Explanation: Following messages identify the

members input from the data set.
This message assists in tracing the data sets which
were used, and which members they contributed.
ddname
The DDNAME.
The severity is 0.
701
System Action: Messages IEB154I and IEB155I

follow.
IEB168I
**WARNING** DUE TO ERROR,

POSSIBLE LOSS OF ACCESS TO
MEMBER DATA AND/OR INCOMPLETE
DIRECTORY
Explanation: If preceded by message IEB148I, the

output directory has been truncated. Otherwise, the
output directory may be incomplete.

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
the IBM Support Center. Provide the JCL and all printed
IEB170I
The severity is 12.

the type of error, retry the operation with the data set in
error allocated:
System Programmer Response: Dump the directory
with IEHLIST or SPZAP to determine the final status of
the output directory. 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
IEB169I
**WARNING** DUE TO I/O ERROR ON

SYSUT4, OUTPUT DIRECTORY MAY
NOT BE COMPLETE
Explanation: The SYSUT4 spill file holds the directory

for the output data set until the operation is complete.
Because an I/O error occurred on the SYSUT4 spill file,
a portion of the output directory was lost before it could
be written to the output data set.
The severity is 0.
work area size. See message IEB1052I previously
issued.
channel.
702
**WARNING** DUE TO SYSUT3 I/O

ERROR, COMPRESS IN-PLACE NOT
DONE AND COPY OPERATION
TERMINATED
Explanation: An I/O error has occurred while using

the spill data set. None of the members were physically
moved, so the data set remains as it was prior to
processing.
The severity is 8.
work area size. See message IEB1051I previously
issued.
channel.
which member(s) were not copied. If the error recurs
the problem.
IEB171I
**WARNING** DIRECTORY MIGHT NOT

REFLECT VALID LOCATION OF
MEMBER DATA
Explanation: An I/O error during a compress-in-place

operation may have affected the validity of the data set
directory.
The severity is 8.
Application Programmer Response: The data set in
question should be checked for valid information and
re-created or restored if necessary.

utility to investigate the output directory. If the error
IEB172I
ddname COULD NOT BE OPENED
Explanation: The data set could not be opened. This

is normally the SYSPRINT data set.
IEB174I
**WARNING** INPUT RECORD IS A

SHORT LENGTH RECORD
-DDNAME=DDNAME
[-OUTPUT TTRN=ttrn]
[-MEMBER=member]
Explanation: An unexpected short length record

(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.
This message is issued when one of the following
conditions regarding a short block exists:
1. For RECFM=F, the length of a physical record is not

the same as the block size.
ddname
2. For RECFM=FB, the length of a physical record is

not a multiple of the logical record length.
The DDNAME.
The severity is 4.
System Action: Normal processing continues. If this is
the SYSPRINT data set then only I/O error messages
and an end-of-job message are issued, and they are
directed to the system console.
IEHLIST utility to investigate the output data sets and
verify the ending status of each operation performed.
System Programmer Response: Look for a missing
SYSPRINT DD statement.
IEB173I
ddname -- INVALID BLOCK SIZE
Explanation: An incorrect block size associated with

the indicated data set DD statement was detected. This
is probably the SYSPRINT data set.
ddname
The DDNAME.
System Action: This data set cannot be used. If this
is the SYSPRINT data set then only I/O error messages
and an end-of-job message are issued, and they are
directed to the system console.
IEHLIST utility to investigate the output data sets and
verify the ending status of each operation performed.
System Programmer Response: Check the DD
statement for incorrect DCB information, such as block
size. If the error recurs and the program is not in error,
information. search problem reporting data bases for a
3. For RECFM=FBS, the length of a physical record

other than the last one is not the same as the block
size.
ddname
The DDNAME.
member
ttrn
The severity is 4.
System Action: The error is ignored.
cannot be ignored by the user, the input data set must
be re-created.
the problem.
IEB175I
**WARNING** INPUT RECORD IS

GREATER THAN OUTPUT BLKSIZE DDNAME=DDNAME
[-OUTPUT TTRN=ttrn]
[-MEMBER=member]
Explanation: An input record on the indicated input

data set whose length is greater than the output block
size has been processed. If the record length is less
than or equal to the output device track capacity, then it
was copied from the member to the output data set at
the logical disk address specified exactly as it was read
(no truncation). Otherwise, the record is discarded.

703
ddname
The DDNAME.
ddname
The DDNAME.
member
ttrn
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
data set is to be updated or compressed, retry the
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.
Note: The stored load module will be executable, but it
will not be usable as input to either the program
management binder or the linkage editor. Before
including it as input to either utility, copy the load
module to a data set with a block size greater than the
length of the largest text record. (The systems
maximum block size, 32760 bytes, will always be large
enough to contain any text record.)
the problem.
The severity is 8.
Application Programmer Response: Re-create the
member in error.
the problem.
IEB177I
member WAS SELECTED BUT NOT

FOUND IN ANY INPUT DATASET
Explanation: The member was specified on a

SELECT statement for the previous operation, but does
not exist on any of the specified input data sets.
member
The severity is 4.
System Action: The member is ignored.
Application Programmer Response: Check to see if
the member should have been found.
Note: If this message is issued while processing a data

set that will be serviced with SMP/E, resolve the
condition causing the message before using SMP/E to
modify the load module. The program management
binder and editor will not use load modules named in
this message as input.

the problem.
IEB176I
MEMBER member IN DATASET

REFERENCED BY ddname HAS MORE
THAN ONE NOTELIST POINTER
Explanation: The directory entry for the member in

the indicated data set has more than one Notelist (User
TTRN with N not equal to zero). This is an unsupported
format directory entry, and the member cannot be
correctly processed.
member
IEB178I
NOT AN IEBCOPY UNLOADED

DATASET
Explanation: The input data set has sequential

organization so a LOAD operation is assumed. The data
set does not have the format of an IEBCOPY unloaded
data set so it cannot be processed by IEBCOPY.
The severity is 8.
data set in question was created by IEBCOPY.
704

the problem.
IEB181I
STORAGE CAN NOT BE ALLOCATED

FOR LOAD/UNLOAD PROCESSING -INCREASE WORK= VALUE IN PARM
FIELD
Explanation: There is not enough virtual storage

available to complete the unload or load operation.
The severity is 8.
IEB179I
{COPYMOD | ALTERMOD |
COMPRESS} NOT VALID FOR
LOAD/UNLOAD
Explanation: The requested function, COPYMOD,

ALTERMOD, or COMPRESS can not accept an
unloaded data set as input, or can not produce an
unloaded data set as output.
The severity is 8.
data sets in question have been specified correctly.
the problem.
IEB180I
MORE THAN ONE INPUT DATA SET

SPECIFIED FOR UNLOAD OPERATION
Explanation: More than one input data set was

specified for an unload operation either in the same
INDD= group, or in an additional INDD= group.
The severity is 8.
System Action: The additional input data sets are not
processed.
Application Programmer Response: If more than
one data set is to be unloaded, use multiple operations
(one for each data set to be unloaded) to different
output data sets.

the problem.
IEB182I
UNLOAD DATA SET REFERENCED BY

ddname HAS BEEN FLAGGED AS NOT
LOADABLE
Explanation: An I/O error occurred while unloading.

The output data set is incomplete and cannot be
successfully reloaded. This message was preceded by
message IEB139I, or another error or attention
message.
ddname
The DDNAME.
The severity is 8.
Application Programmer Response: If the I/O error
occurred on one of the output data sets or work files,
retry the operation. If the error occurred on the input
data set, it may have to be re-created.

the problem.
System Programmer Response: Refer to

accompanying messages, starting with IEB139I. If the
error recurs and the program is not in error, look at the
messages in the job log for more information. search
705
IEB183I
END OF FILE READ ON LOAD DATA

SET REFERENCED BY ddname
parameters have been overridden, respecify the correct

block size and key length.

may be used to display the block size and key length in
the data set label. Look for an override on the ddname
DD statement. 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
ddname
Explanation: The data set:

v contains directory entries without the corresponding
members, or
v contains directory entries with incorrect member
TTRs, or
v is a null data set.
The DDNAME.
IEB185I
The severity is 8.
ddname IS NOT A LOADABLE DATA

SET

Explanation: The data set to be loaded was flagged

as not loadable during a previous unload operation.
Application Programmer Response: Recreate the

original data set and retry the operation.
ddname

unloaded data set and the original partitioned data set.
The severity is 8.

input data set and resubmit the job.
IEB184I

the problem.
MEMBER DATA RECORD READ FOR

MEMBER member REFERENCED BY
DDNAME IS LONGER THAN DATA SET
BLOCK SIZE PLUS KEY LENGTH
nnnnn CCHHRKDD=(mbbcchhr)
Explanation: The DCB information given for the input

data set is incorrect because the input data set contains
a record that is too long. The record is part of the
member specified and was read from the physical disk
address indicated. The actual length includes both the
key and data portions of the record.
member
ddname
nnnnn


IEB186I
INPUT AND OUTPUT DATASETS ON

SAME TAPE VOLUME
Explanation: Two data sets cannot be opened

concurrently on the same tape volume because the
tape can be positioned only within one data set at a
time.
The DDNAME.
The severity is 8.
The actual length.

mbbcchhr
The physical disk address.
The severity is 8.
Application Programmer Response: If the DCB
706
The DDNAME.
Application Programmer Response: Copy the input

data set to a temporary data set on another volume,
then recopy the temporary data set back to the desired
volume.

the problem.

IEB189I

IEB187I
NOT A DIRECT ACCESS OR TAPE

DATASET
Explanation: An input or output data set is allocated

to other than a direct-access or tape device. This
includes JES data sets, which are treated as unit record
devices. Message IEB120I accompanies this message
to identify the data set in error.
The severity is 8.
statement identified in message IEB120I.
the problem.
IEB188I
MEMBER member IN DATASET

REFERENCED BY DDNAME HAS
RECORDS GREATER THAN BLKSIZE
Explanation: While reading the member from the data

set, a record longer than the data set block size was
read.
member
ddname
DIRECTORY ENTRY member IN BLOCK

READ FROM DDNAME DDNAME AT
MBBCCHHR mbbcchhr TTRN ttrn IS
OUT OF SEQUENCE OR DUPLICATE
Explanation: The directory of the data set contains

two entries with the same name, or the entries are not
in ascending sequence by name. The duplicate or out of
place entry is for the member. The directory block is at
the physical disk address indicated, and the logical disk
address indicated. This is an attention message.
member
ddname
The DDNAME.
mbbcchhr
The physical disk address.
ttrn
The severity is 4.
Application Programmer Response: Delete
members from the data set so the directory entries
return to strict ascending sequence by name.
System Programmer Response: SPZAP may be
used to dump the bad directory and to alter member
names in the directory. If the error recurs and the
the IBM Support Center. Provide the JCL, the SYSOUT
output for the job, the associated volume, the control
statements for the job, and all printed output and output
data sets related to the problem.
The DDNAME.
The severity is 8.
Application Programmer Response: If the DCB
parameters have been overridden, respecify the correct
block size and key length.
may be used to display the block size in the data set
IEB19AI
MEMBER member {COPIED | LOADED}

AND {REBLOCKED | ALTERED}
Explanation: The member has been reblocked (or

altered) and copied (or unloaded) to the output data set.
The Relocation Dictionary (RLD) counts have been
updated or were already correct.
member
The severity is 0.
707
IEB19BI
MEMBER member {COPIED | LOADED},

{REBLOCKED | ALTERED}, AND IS A
NEW NAME
Explanation: The member is a renamed load module

which has been successfully copied (or loaded) and
reblocked (or altered) to the output data set. The RLD
counts have been updated or were already correct.
checking the IEBCOPY control statements printed at the
beginning of the copy step in which this message
occurred.
copied to the output data set with no change in block

size or content. The link edit attributes of the member
make it ineligible for processing by COPYMOD.
beginning of the copy step in which this message
occurred.
member
The severity is 4.
member
System Action: The member was copied unaltered.

The severity is 0.
Application Programmer Response: Process the

module using the link editor.
System Programmer Response: The AMBLIST utility

may be used to check the link edit attributes of member.
IEB19CI

text
IEB19EI

{NOT A LOAD
MODULE|INCOMPATIBLE OR
INELIGIBLE}
Explanation: COPYMOD has been specified. The

member is a load module which has been copied to the
output data set with no change in block size or content.
The link edit attributes of the member make it ineligible
for processing by COPYMOD.

member does not contain records in the format of or
with the content required of load modules.
member
member
The specified
member.
NOT A LOAD MODULE
The member is not

a load module. 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.
text

v AS IS THEN ALTERED, MODULE IS
PAGE-ALIGNED
v AS IS WITHOUT REBLOCKING FORMAT
IS SCATTER-LOAD
v AS IS WITHOUT REBLOCKING MODULE
IS NON-EDITABLE
The severity is 4.
System Action: The member was copied unaltered.
Application Programmer Response: Process the
module using the link editor.
may be used to check the link edit attributes of member.
IEB19DI

FORMAT IS SCATTER-LOAD |, AND IS
A NEW NAME

member is a renamed load module which has been
708
The severity is 4.
System Action: The member was copied to the output
data set with no change in block size or content.
If the member was partially copied before it was
recognized that it was not a load module, the copy was
started again from the beginning of the member.
The system issues accompanying message IEB1142W
when INCOMPATIBLE OR INELIGIBLE is displayed.
Application Programmer Response: Evaluate the
member to see if it was processed as expected.
may be used to verify that the member is not a load

module.

module.
IEB19FI
MEMBER member {COPIED | LOADED}

, {NOT A LOAD
MODULE,|INCOMPATIBLE OR
INELIGIBLE,} AND IS A NEW NAME

member is a renamed member which does not contain
records in the format or with the content required of
load modules.
beginning of the copy step in which this member
occurred.
IEB19GI
MEMBER member ALTERED IN PLACE
Explanation: The Relocation Dictionary (RLD) counts

for the member have been inserted or updated.
member
The severity is 0.
member
The specified
member.
IEB19HI
NOT A LOAD MODULE
The member is not

a load module. 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.
Explanation: No change has been made to the

member because the Relocation Dictionary (RLD)
counts were already correct.
INCOMPATIBLE OR INELIGIBLE COPYMOD cannot

unblock the module
because the
common sections for
the module are not
at the end of the
module where the
link editor usually
places them. The
system issues
message IEB1142W
with more
information about
this error.
MEMBER member NOT ALTERED, RLD

COUNT WAS CORRECT
member
The severity is 0.
IEB19JI
MEMBER member NOT ALTERED,

FORMAT IS SCATTER-LOAD |
Explanation: ALTERMOD has been specified. The

member is a load module which was not altered. The
link edit attributes of the member make it ineligible for
processing by ALTERMOD.
member
The severity is 4.
The severity is 4.
System Action: The member was copied to the output

data set with no change in block size or content.
If the member was partially copied before it was

recognized that it was not a load module, the copy was
started again from the beginning of the member.
The system issues accompanying message IEB1142W
when INCOMPATIBLE OR INELIGIBLE is displayed.

member to see if should have been processed.
may be used to check the link edit attributes of the
member.

member to see if it was processed as expected.
709
IEB19KI
MEMBER member NOT ALTERED, NOT

A LOAD MODULE
Explanation: ALTERMOD has been specified. The

member does not contain records in the format or with
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.
member
System Action: IEBCOPY uses the maximum value

as the maximum block size. Processing continues.
Application Programmer Response: If a smaller
maximum block size is required, specify or correct the
MAXBLK= parameter.
IEB192I
MINBLK DEFAULTS TO minimum
Explanation: The MINBLK= parameter specifies a

value that is greater than the output data set block size,
greater than MAXBLK= parameter, less than 1 kilobyte
(1024), or not a number.
The severity is 0.
minimum
The minimum block size.

member to see if should have been processed.
module.
IEB190I
MAXIMUM BLOCK SIZE IS maximum,

MINIMUM BLOCK SIZE IS minimum
Explanation: The COPYMOD operation will copy or

reblock load modules.
The severity is 4.
System Action: IEBCOPY uses the minimum value as
the minimum block size. Processing continues.
Application Programmer Response: If a different
minimum block size is required, specify or correct the
MINBLK= parameter.
IEB193I
{MAXBLK | MINBLK}IS SPECIFIED ON

OTHER THAN A COPYMOD
STATEMENT
maximum
The maximum block size that will be written.
Explanation: A MAXBLK or MINBLK parameter is

found with a statement other than COPYMOD.
minimum
The minimum block size that will be written
specifically to optimize track space.
The severity is 8.
The severity is 0.

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.
IEB191I
MAXBLK DEFAULTS TO maximum
Explanation: The MAXBLK= parameter specifies a

value that is greater than the track size, greater than 32
kilobyte-8 (32760), less than 1 kilobyte (1024), or not a
number.
maximum
The maximum block size.
The severity is 4.


IEB194I
CANNOT ALLOCATE ENOUGH

STORAGE FOR ALTERMOD/COPYMOD
-- INCREASE WORK= VALUE IN PARM
FIELD
Explanation: There is not enough unallocated virtual

storage available to reblock the records.
Virtual storage requirements vary with the input block
size, the output block size, and the maximum number of
RLD records that follow a block of text.
The severity is 8.
710

IEB198I

IEB195I
RENAME/REPLACE NOT VALID WITH

ALTERMOD
Explanation: ALTERMOD has been specified. A

SELECT statement MEMBER= operand contains a new
name and/or the replace indicator, which is not allowed.
ALTERMOD is an update-in-place operation does not
replace nor rename members.
RECFM U REQUIRED WITH

{COPYMOD | ALTERMOD} FOR
DDNAME ddname
Explanation: The data set associated with the

ddname DD statement does not have undefined format
records, so it can not contain any load modules for a
COPYMOD or ALTERMOD operation.
ddname
The DDNAME.
The severity is 8.
The severity is 8.



rename or replace specification from the ALTERMOD
statement.

ddname DD statement.

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

COPYMOD
Explanation: COPYMOD is not an update-in-place

operation, so two different data sets must be used.
Therefore, INDD= and OUTDD= must specify different
DDNAMEs.
The severity is 8.
Application Programmer Response: Use a separate
COPY (not COPYMOD) operation if a compress in
place is also desired.
Make a full copy to a new data set. Substitute this
IEB197I
INDD SPECIFIED WITH ALTERMOD
Explanation: ALTERMOD is an update-in-place

operation. The OUTDD= specifies the single data set
that is updated. Specifying another data set (with
INDD=) is meaningless.
The severity is 8.
INDD= operand.
IEB199I
DSORG PO REQUIRED WITH

{COPYMOD | ALTERMOD} FOR
DDNAME ddname
Explanation: The data set associated with the

ddname DD statement is not a partitioned data set, so it
can not contain any load modules for a COPYMOD or
ALTERMOD operation.
ddname
The DDNAME.
The severity is 8.
statement.
may be used to display the DSORG in the data set
label. Look for an override on the DD statement.
IEB201I
INVALID CONTROL STATEMENT
Explanation: The syntax of the control statement

preceding this message is incorrect.
code is 12.
error. Correct the syntax of the preceding statement and
resubmit the job.
711

the problem.

the problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEB202I
IEB211I
INVALID DIRECTORY BLOCK SIZE
KEY LENGTHS ARE NOT EQUAL.
Explanation: The length of the partitioned data set

directory entry is less than 14 or greater than 256 bytes.
Explanation: The key lengths of the SYSUT1 and

SYSUT2 data sets are not equal.

code is 12.

code is 12.

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.

the problem.
Source: DFSMSdfp

and all printed output and input and output data sets
Source: DFSMSdfp
IEB203I
ALIAS/TRUE NAME FAILURE
Explanation: A true name and an alias name were the

same for SYSUT1 and SYSUT2 data sets.
System Action: The name that is a member in one
data set and an alias in the other data set is printed.
Processing continues with the comparison of user data.
Source: DFSMSdfp
IEB205I
USER DATA FIELDS UNEQUAL
Explanation: The user data fields or TTRs of the

SYSUT1 and SYSUT2 data sets are not identical.
System Action: The fields are listed and processing
Source: DFSMSdfp
IEB210I
TRUE NAMES MISSING FROM BOTH

SETS
Explanation: Not all the names in one directory have

counterpart names in the other directory.
code is 12.
at least one partitioned data set has true names
associated with every member in the partitioned data
set. Resubmit the job.
712
IEB212I
INVALID DCB PARAMETER
Explanation: Either the record formats are not

standard, or the BLKSIZE/LRECL is omitted from either
the input or output DD statement.
code is 12.
a valid RECFM was specified in the DCB, and that the
BLKSIZE/LRECL parameter was included in the input or
output DD statement. If the data set resides on an
unlabeled tape, make sure that a valid RECFM was
included in the DCB parameter in the DD statement.
After making corrections, resubmit the job step.
the problem.
Source: DFSMSdfp
IEB213I
REPETITIOUS CARD INVALID
Explanation: A second COMPARE or LABELS

statement has been encountered.
System Action: The job is ended at the end of the
control statement scan. The return code is 12.

error. Remove the extra command statement and
resubmit the job step.
the problem.
Source: DFSMSdfp
IEB214I
FIXED RECORD LENGTHS UNEQUAL
Explanation: The record lengths of the SYSUT1 and

SYSUT2 data sets are not the same.
IEB216I
ILLEGAL CONTROL CARD SEQUENCE
Explanation: The COMPARE statement was not the

first utility control statement, or two COMPARE
statements were encountered.
error. Make sure that there is only one COMPARE
statement in the input stream. Resubmit the job.
the problem.

code is 12.
Source: DFSMSdfp

error. Make sure that the logical records in both data
sets are of the same length, and that the LRECL
parameter in both DCBs are correctly specified.
Resubmit the job.
IEB217I

the problem.
Source: DFSMSdfp
IEB215I
RECORD FORMATS DIFFERENT
INVALID LRECL FOR V/VS RECORD
Explanation: The LL field of a variable-length record

is less than 5, is greater than 32,756, or is greater than
remaining size of the block.
code is 12.
the input data sets are valid. Resubmit the job.
the problem. Have the input data sets available.
Explanation: The record characteristics of the

SYSUT1 and SYSUT2 data sets are not the same.
Source: DFSMSdfp

code is 12.
IEB218I

error. Make sure that the record characteristics of the
two data sets are compatible.
the problem.
Source: DFSMSdfp
PERMANENT INPUT ERROR - FIND

MACRO
Explanation: A permanent input error was found by

the FIND macro instruction during a partitioned data set
directory search.
code is 12.
Application Programmer Response: See Problem
Determination, below.
the problem.
713
Source: DFSMSdfp
IEB219I
INVALID BLKSIZE FOR V/VS RECORD
Explanation: The LL field of a variable-length block is

less than 9 or greater than 32,760.
IEB225I
JOB TERMINATED AFTER EXIT
Explanation: The return code from an exit routine

indicated that the job should be ended.
System Action: The job is ended. The return code is
12 or 16, as determined by the exit routine.

code is 12.
Source: DFSMSdfp

the input data sets are valid. Resubmit the job.
IEB226I

the problem. Have the input data sets available.
Source: DFSMSdfp
IEB221I
RECORDS ARE NOT EQUAL
Explanation: Two corresponding records do not

contain the same data, or the second part of the record
descriptor word is not equal (00).
System Action: The records are printed and
processing continues. The return code is 8.
WARNING - INVALID NAME
Explanation: The statement label either is longer than

eight characters or contains an incorrect character.
System Action: Processing continues normally.
error. Correct the statement label. Resubmit the job.
the problem.
Source: DFSMSdfp
IEB227I
TEN CONSECUTIVE ERRORS
Source: DFSMSdfp
Explanation: Ten successive unequal comparisons

have occurred, and an error routine was not specified.
IEB222I
System Action: If the input data sets are sequential,

the program is ended. The return code is 12. If the input
data sets are partitioned, processing continues with the
next member. If the current member is the last member,
the program is ended. The return code is 8.
KEYS ARE NOT EQUAL
Explanation: Two corresponding keys do not contain

the same data.
Source: DFSMSdfp
Source: DFSMSdfp
IEB229I
IEB223I
EXTRA RECORD ON SYSUT2
DDNAME ddname CANNOT BE

OPENED
Explanation: The SYSUT2 data set contains more

records than the SYSUT1 data set.
Explanation: The named DD statement does not

exist.

Source: DFSMSdfp
IEB224I
EXTRA RECORD ON SYSUT1

records than the SYSUT2 data set.
Source: DFSMSdfp
714
ddname
The DDNAME.
code is 12.
the DDNAME if it is misspelled in the DD statement or
the DDLIST, or insert a new DD statement with the
correct name.

the problem.
Source: DFSMSdfp
IEB230I
SYSIN BLOCKSIZE ERROR
Explanation: The SYSIN DD statement specifies a

block size that is not a multiple of the specified logical
record length.
code is 12.
the block size is a multiple of the specified logical
record length. Resubmit the job.
the problem.
Source: DFSMSdfp
IEB231I
EXTRA USER INPUT HEADER LABELS

ON SYSUT1

user input header labels than the SYSUT2 data set.
System Action: The extra labels are printed and
Source: DFSMSdfp
IEB232I
EXTRA USER INPUT HEADER LABELS

ON SYSUT2
IEB234I
EXTRA USER INPUT TRAILER LABELS

ON SYSUT2

user input trailer labels than the SYSUT1 data set.
Source: DFSMSdfp
IEB235I
SYSUT1 CONTAINS NO USER INPUT

HEADER LABELS
Explanation: The programmer requested the INHDR

exit and/or label comparison, but there was no input
header label on the SYSUT1 data set.
System Action: Message IEB232I will be issued.
Source: DFSMSdfp
IEB236I

HEADER LABELS

header label on the SYSUT2 data set.
System Action: Message IEB231I will be issued.
Source: DFSMSdfp
IEB237I
BOTH INPUT DATA SETS CONTAIN NO

USER HEADER LABELS

exit and/or label comparison, but there were no input
header labels on the SYSUT1 and SYSUT2 data sets.
code is 8.

user input header labels than the SYSUT1 data set.
Source: DFSMSdfp

IEB238I
Source: DFSMSdfp
IEB233I
EXTRA USER INPUT TRAILER LABELS

ON SYSUT1

TRAILER LABELS
Explanation: The programmer requested the INTLR

trailer label on the SYSUT1 data set.
System Action: Message IEB234I is also issued.

user input trailer labels than the SYSUT2 data set.
Source: DFSMSdfp

IEB239I
Source: DFSMSdfp

TRAILER LABELS

trailer label on the SYSUT2 data set.
System Action: Message IEB233I is also issued.
Source: DFSMSdfp
715
IEB240I
BOTH INPUT DATA SETS CONTAIN NO

USER TRAILER LABELS

exit and/or label comparison, but there were no input
trailer labels on the SYSUT1 and SYSUT2 data sets.
code is 8.

the problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEB245I
IEB241I
INPUT HEADER LABELS ARE NOT

EQUAL
Explanation: Corresponding input header labels are

not the same.
System Action: The SYSUT1 label is listed first,
followed by the SYSUT2 label. Processing continues.
Source: DFSMSdfp
IEB242I
INPUT TRAILER LABELS ARE NOT

EQUAL
Explanation: Corresponding input trailer labels are not

the same.
System Action: The SYSUT1 label is listed first,
followed by the SYSUT2 label. Processing continues.
Source: DFSMSdfp
IEB243I
ERROR WHILE READING USER INPUT

HEADER LABEL ON SYSUT1
Explanation: An uncorrectable input/output error

occurred while reading the user input header labels on
the SYSUT1 data set.
code is 12.
the problem.

occurred while reading the user input trailer label on the
SYSUT1 data set.
code is 12.
the problem.
Source: DFSMSdfp
IEB246I
I/O ERROR WHILE READING USER

INPUT HEADER LABEL ON SYSUT2

INPUT TRAILER LABEL ON SYSUT2

occurred while reading the user input trailer label on the
SYSUT2 data set.
code is 12.
the problem.
Source: DFSMSdfp
IEB247I
Source: DFSMSdfp
IEB244I

INPUT TRAILER LABEL ON SYSUT1
xxx INPUT {HEADER|TRAILER}

LABELS FROM BOTH DATA SETS ARE
COMPARED
Explanation: At the programmers request, the

indicated number of user input header or trailer labels
were compared.

occurred while reading the user input header label on
the SYSUT2 data set.
xxx

code is 12.
System Action: If the return code from the user exit

routine is 16, message IEB225I is also issued.
716
The indicated number of user input header or

trailer labels.
Otherwise, processing continues normally.
IEB251I
Source: DFSMSdfp
IEB248I
xxx EXITS TO routine IS MADE FOR

{SYSUT1|SYSUT2} RETURN CODE
FROM USER ROUTINE IS return-code
Explanation: The user label processing routine has

been entered the indicated number of times for the
SYSUT1 or SYSUT2 data set, as indicated in the
message text. The routine returned a return code,
indicating that no more labels will be processed.
xxx
The number of times the user label

processing routine has been entered.
routine
The user label processing routine.
return-code
The return code.
System Action: If the return code from the user

routine is 16, message IEB225I is also issued.
Otherwise, processing continues normally.
Explanation: One of the input data sets contains

logical records greater than 32 kilobytes. The other one
does not.
code is 12.
both data sets contain records of compatible logical
record length. Resubmit the job.
the problem.
Source: DFSMSdfp
IEB252I
Source: DFSMSdfp
IEB249I
NO RECORDS ARE COMPARED,

DATA=ONLY
Explanation: The programmer specified DATA=ONLY.

Therefore, only user header labels are processed.
code is 0.
Source: DFSMSdfp
IEB250I
USER LABEL IS NOT SUPPORTED BY

PARTITIONED DATA SET

or INTLR exit, but user labels are incorrect for
partitioned data sets.
code is 12.
keyword parameter in the COMPARE statement if the
data sets are indeed physical sequential. Resubmit the
job.
the problem.
INCOMPATIBLE MAXIMUM LOGICAL

RECORD LENGTH
KEYED DATA SETS. ONE CONTAINS

SPANNED RECORD, THE OTHER ONE
DOES NOT
Explanation: Both input data sets contain keyed

records. One data set has variable spanned records.
The other one does not.
code is 12.
the input data sets are of compatible characteristics.
Resubmit the job.
the problem.
Source: DFSMSdfp
IEB253I
RECORDS ARE COMPARED AT

PHYSICAL BLOCK LEVEL
Explanation: Since both data sets contain keyed

spanned records or logical records greater than 32K
bytes, the comparison is made at the block level.
Source: DFSMSdfp
Source: DFSMSdfp
717
IEB254I
CORRESPONDING BLOCK LENGTHS

ARE NOT EQUAL
Explanation: Corresponding block lengths are not the

same.
System Action: The blocks are printed, and
Source: DFSMSdfp
IEB255I
CORRESPONDING RECORD LENGTHS

ARE NOT EQUAL
Explanation: Corresponding lengths of variable or

variable spanned records are not the same.
Source: DFSMSdfp
IEB256I
IEBCOMPR DOES NOT COMPARE

PARTITIONED DATA SETS WITH VS
RECFM
IEB258I
USER LABELS NOT COMPARED,

UNABLE TO TAKE EXIT FOR ONE
DATA SET
Explanation: The programmer wishes to process the

input header/trailer labels as data, but the utility
program is unable to take the input header/trailer label
exit for one of the data sets. Probably, the SUL
subparameter is missing from the SYSUT1 or SYSUT2
DD statement.
code is 12.
both the SYSUT1 and SYSUT2 DD statements specify
SUL in the LABEL parameter. Resubmit the job.
the problem.
Explanation: The programmer requested that

partitioned data sets containing variable spanned (VS)
records be compared. IEBCOMPR does not support this
function.
Source: DFSMSdfp

code is 12.
Explanation: In the statement preceding this

message, a keyword beginning in or before the column
is either incorrect or not applicable to the command for
which it was specified.

TYPORG=PS in the COMPARE statement if the input
data sets are indeed physical sequential. Resubmit the
job.
the problem.
Source: DFSMSdfp
IEB257I
JOB TERMINATED AFTER EXIT FOR

USER VOLUME SWITCH LABEL
PROCESS
Explanation: The programmer requested that

processing be ended after the volume switch input
header/trailer labels were examined in the labels exit
routine.
code is 16.
Source: DFSMSdfp
718
IEB259I
INVALID KEYWORD IN OR BEFORE

COLUMN dd
dd
The indicated column.

error. Correct the error and resubmit the job.
the problem.
Source: DFSMSdfp
IEB260I
MISSING COMMAND IN OR BEFORE

COLUMN dd

message, a command that should appear in or before
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.
dd

the problem.
Source: DFSMSdfp
IEB261I
INVALID PARAMETER IN OR BEFORE

COLUMN dd

message, a keyword beginning in or before the column
is incorrect:
v The parameter is longer than eight characters.
v The parameter is incorrect for the preceding keyword.
v The parameter is not immediately preceded by an
equals sign.
v The parameter is misspelled.
the problem.
Source: DFSMSdfp
IEB262I
MISSING KEYWORD IN OR BEFORE

COLUMN dd

message, a required keyword that should appear in or
before the column is omitted, or a blank immediately
preceded an equals sign.
dd


the problem.
Source: DFSMSdfp
IEB263I
MISSING PARAMETER IN OR BEFORE

COLUMN dd

message, a required parameter that should appear in or
before the column is omitted.
dd

the problem.
Source: DFSMSdfp
IEB264I
FIRST CONTROL CARD IS NOT

COMPARE
Explanation: The COMPARE statement was not the

first utility control statement.
the problem.
Source: DFSMSdfp
IEB265I
INVALID COMMAND IN OR BEFORE

COLUMN dd

message, the command beginning in or before the
column is either misspelled or not immediately preceded
or followed by a blank.
719
dd

the problem.
Source: DFSMSdfp
IEB266I
CONTINUATION CARD BEGINS IN

WRONG COLUMN
Explanation: The continuation statement preceding

this message does not begin in columns 4-16.
the problem.
Source: DFSMSdfp
IEB267I
I/O ERROR jjj, sss, ddd, devtyp, ddname,

op, err, xxxx, acc

while processing on the device indicated.
instruction issued by the SYNAD routine was:
jjj
xxxx
Last seek address of block count.
acc
Access method.
code is 12.
DCB information was valid. Resubmit the job.
the problem.
Source: DFSMSdfp
IEB302I
INVALID PARAMETER LIST
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.
the problem.
Source: DFSMSdfp
IEB303I
Job name.
Explanation: The syntax of the control statement

preceding this message is incorrect, or a parameter
value that is inconsistent with the data set content has
been specified.
Step name.

code is 12.

sss
ddd
devtyp
Device type.
ddname
720

the problem.
Source: DFSMSdfp
v fixed records with an LRECL or BLKSIZE of zero; or
IEB304I
v variable records with incorrect block or record

descriptor words.
CONTROL STATEMENT INPUT ERROR
Explanation: A permanent input/output error was

detected while reading the SYSIN data set.

code is 12.

code is 12.

the DCB values are correct for the data set being
processed.

operation. If the operation fails a second time with this
same message, then in all probability a hardware error
has occurred. Ensure the quality of the hardware
medium on which the data set referenced by the SYSIN
DD statement resides. Resubmit the job.
the problem.
Source: DFSMSdfp
IEB305I
JOB TERMINATED AFTER LABEL EXIT
Explanation: A return code of 16 was returned by a

LABEL exit routine, indicating that processing is ended.
16.
Source: DFSMSdfp
IEB306I
JOB TERMINATED AFTER KEY EXIT
Explanation: A return code of 12 or 16 was returned

by a KEY exit routine, indicating that processing is
ended.
code is 12 or 16, as determined by the exit routine.

the problem.
Source: DFSMSdfp
IEB309I
PERMANENT OUTPUT ERROR

detected while writing the SYSUT2 data set.
code is 12.
the output DCB values are compatible with input DCB
values, considering any record editing that was
requested.
the problem.
Source: DFSMSdfp
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
v The SYSUT2 data set is not partitioned.
JOB TERMINATED AFTER DATA EXIT
Explanation: A return code of 12 or 16 was returned

by a DATA exit routine, indicating that processing is
ended.
12 or 16, as determined by the exit routine.
Source: DFSMSdfp
IEB308I
PERMANENT INPUT ERROR

detected while reading the SYSUT1 data set.
For example, two situations that cause this message to
appear are:
v A member name was specified more than once in

MEMBER statements.
v A member name was specified in a MEMBER
statement, and a member of the same name already
exists in the partitioned data set.
v Insufficient space was allocated for the directory.
code is 12.
the SYSUT2 data set is partitioned, a member name is
not specified more than once, and sufficient space is
allocated for the directory, as necessary.
721

the problem.

the problem.
Source: DFSMSdfp
IEB316I
Source: DFSMSdfp
IEB311I
CONFLICTING DCB PARAMETERS
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
not a multiple of the I/O logical record length when the
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
when the record format is VB or V.)

OPENED
Explanation: The DDNAME indicated on the DD

statement does not exist. Perhaps a DDNAME is
misspelled in an existing DD statement or ddlist.
ddname
The DDNAME.
12.

code is 12.


error. Make sure that the DCB parameters of the output
DD statement are compatible with the DCB parameters
of the input DD statement, considering any editing that
was requested.


the problem.
Source: DFSMSdfp
IEB312I
JOB TERMINATED AFTER ERROR EXIT
Explanation: A return code of 16 was returned by an

ERROR exit routine, indicating that processing is ended.
code is 16.
Source: DFSMSdfp
IEB315I
SPACE NOT AVAILABLE
Explanation: Insufficient virtual storage space is

available for the work area, buffers, and save areas.
12.
Application Programmer Response: Increase virtual
storage size and resubmit job.
722
Source: DFSMSdfp
IEB317I
JOB TERMINATED, NO INPUT

BLKSIZE/LRECL
Explanation: The BLKSIZE/LRECL parameter was

omitted from the input DD statement for SYSUT1.
code is 12.
Source: DFSMSdfp
IEB318I
JOB TERMINATED, NO OUTPUT

BLKSIZE/LRECL
Explanation: The BLKSIZE/LRECL parameter was

omitted from the output DD statement for SYSUT2.
code is 12.

Source: DFSMSdfp
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.
code is 12.

12.
error. Correct the data set characteristics (RECFM,
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.

Source: DFSMSdfp

IEB322I
Source: DFSMSdfp
IEB320I
OUTPUT DATA SET WITH KEYS IN

VS/VBS PROCESSING
Explanation: During processing of other than straight

copy, the programmer specified keys for a VS or VBS
output data set. If a change is required in the data set
characteristics, or if editing is to be done, a key cannot
be specified.
12.
error. Correct the data set characteristics (RECFM,
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.
JOB TERMINATED AFTER OPENING

OUTPUT DATA SET UPON USER
REQUEST
Explanation: The input header user label routine

requires ending of the job after the output data set is
opened.
16.
Source: DFSMSdfp
IEB323I
JOB TERMINATED AFTER HEADER

LABEL PROCESSING
Explanation: The programmer specified a LABELS

DATA=ONLY statement. Therefore, after the user
header labels are processed, the program is ended.
code is 8.
Source: DFSMSdfp
IEB324I
xxx TIMES TO routine EXIT ROUTINE
Explanation: The user label exit routine has received

control the indicated number of times.
xxx
The number of times the user label exit routine

received control.
Source: DFSMSdfp
routine The user label exit routine.
IEB321I
System Action: Processing is continued. The return

code is 0.
INPUT DATA SET WITH KEYS IN

VS/VBS PROCESSING
Explanation: The input data set contained keys, and

either the input or output data set contained VS or VBS
records. The other data set did not contain VS or VBS
records. If a change is required in the data set
characteristics, or if editing is to be done, a key cannot
be specified.
Source: DFSMSdfp
IEB325I
LAST RETURN CODE WAS return-code
Explanation: The indicated return code was the last

return code issued by the user routine specified in
message IEB324I.
723
return-code
The return code.
System Action: Processing is continued. The return

code is 0.
Source: DFSMSdfp
IEB326I
{SYSUT1|SYSUT2} |
{HEADER|TRAILER} LABEL GAVE I/O
ERROR

while reading or writing a SYSUT1 or SYSUT2 header
or trailer label, as indicated in the message text. If the
error occurred while reading or writing a header label,
the data set was not opened.
code is 12.
operation. If the operation fails a second time with this
same message, ensure the quality of the hardware
medium on which the data set referenced by the
SYSUT1 or SYSUT2 DD (see the details of the
message) resides. Resubmit the job.
Source: DFSMSdfp
IEB327I
SPECIFIED KEY EXITS ARE NOT

TAKEN
Explanation: The programmer specified key exits on a

job requiring processing of a VS or VBS data set with
reformatting.
System Action: Key exits are not taken. Processing
Application Programmer Response: Do not specify
key exits.
Source: DFSMSdfp
IEB328I
LRECL EXCEEDS 32K; STRAIGHT

COPY NOT SPECIFIED
Explanation: A process other than straight copy was

specified. However:
v The RECFM specified for the input or output DCB
was VS or VBS.
v The LRECL specified for the input or output DCB, or
both, was greater than 32,756.
12.
724
error. Make data set characteristics (RECFM, LRECL,

BLKSIZE) equal for input and output data sets. Do not
specify editing. Resubmit the job.
Source: DFSMSdfp
IEB329I
PDS NOT ALLOWED WHEN

INPUT/OUTPUT DATA SET HAS
RECFM=VS/VBS
Explanation: The programmer specified that the

output data set should be partitioned, but the input
and/or output data set has VS or VBS records which
are incorrect.
12.
error. Remove the utility control statements which
specify the output data set as being a PDS, and
resubmit the job.
Source: DFSMSdfp
IEB330I
TOTALING EXIT REQUESTS

TERMINATION
Explanation: A return code of 16 was returned by the

programmers totaling routine, indicating that processing
is ended.
code is 16.
Source: DFSMSdfp
IEB331I
PROCESSING ENDS UPON REQUEST

OF TOTALING EXIT

is ended, but normal end-of-data processing is
completed for the output data set.
System Action: Processing is ended, but normal
end-of-data processing is completed for the output data
set. The return code is 8.
Source: DFSMSdfp
IEB332I
TOTALING EXIT DEACTIVATED UPON

ITS OWN REQUEST

is continued, but no further totaling exits are taken.
System Action: Processing continues, but no further
totaling exits are taken. The return code is 0.
Source: DFSMSdfp
IEB333I
RECORD LABELS=nnn STATEMENTS

ARE REQUIRED
Explanation: The programmer has specified a

LABELS DATA= INPUT statement. Therefore, RECORD
LABELS= statements are also required.
nnn
The number of record labels.

code is 12.
error. If user labels are desired, insert a RECORD
LABELS= n statement and the associated labels
statements in the input stream. If labels are not desired,
remove the LABELS DATA=INPUT statement. Resubmit
the job.
Source: DFSMSdfp
IEB334I
NO EDITING OR CONVERSION WILL

BE DONE
Explanation: Both data sets contain VS or VBS

records, have the same block size, and have the same
logical record length. Therefore, no editing or
conversion is done.
code is 0.
Source: DFSMSdfp
IEB336I
INVALID COMMAND IN COLUMN dd

message, the operation beginning in the specified
column is incorrect:
v An operation other than GENERATE, EXITS,

MEMBER, RECORD, or LABELS was specified.
v The LABELS statement appears twice.
v There are more input labels than are specified by the
RECORD LABELS= n statement.
dd
the specified column.

12.
Source: DFSMSdfp
IEB337I
INVALID KEYWORD IN COLUMN dd

message, a keyword beginning in the column is either
misspelled, incorrect, or not applicable to the command
for which it was specified.
dd
The specified column.

12.
Source: DFSMSdfp
IEB338I
INVALID PARAMETER IS COLUMN dd

message, a parameter beginning in the column is
incorrect:
v A member name contains more than eight characters.
v In the RECORD statement, the IDENT keyword is
followed by more than three parameters.
v A GENERATE statement is not the first control

statement.
v In the RECORD statement, the FIELD keyword is

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
ZD.
v An operation is misspelled.
725
v In the RECORD statement, the LABELS keyword is

not followed by a number from one to eight.
v In the LABELS statement, the parameters in the
DATA keyword are not ALL, ONLY, YES, NO, or
INPUT.
v In the GENERATE statement, the parameter in the
MAXFLDS, MAXNAME, MAXGPS or MAXLITS
keyword is not within the specified limits.
dd

12.
Source: DFSMSdfp
dd

12.
Source: DFSMSdfp
IEB341I
PARAMETER MISSING PRECEDING

COLUMN dd

message, a parameter that should appear before the
column is omitted. That is, a keyword is not followed by
a parameter, or the IDENT keyword in the RECORD
statement is not followed by all three parameters.
IEB339I
COMMAND MISSING PRECEDING

COLUMN dd

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
continuation was not recognized.
dd

code is 12.
dd

code is 12.
Source: DFSMSdfp
IEB342I
INVALID SPACE ALLOCATION
Explanation: Required keywords in the GENERATE

statement are omitted, or their parameter values are too
small. This message is also issued if a RECORD
LABELS= n statement is not preceded by a LABELS
DATA=INPUT statement.
Source: DFSMSdfp

12.
IEB340I

KEYWORD MISSING PRECEDING

COLUMN dd

message, a required keyword that should appear before
the column is omitted. That is, the NAME keyword is not
specified in the MEMBER statement, or the DATA
keyword is not specified in the LABELS statement.
726

Source: DFSMSdfp

code is 12.
IEB343I

ALLOWED NO. OF CARDS EXCEEDED
Explanation: Three or more LABELS statements were

encountered. Two LABELS statements are the
maximum number allowed.
code is 12.

Source: DFSMSdfp
IEB347I
DUPLICATE KEYWORD
Explanation: In the EXITS statement preceding this

message, a keyword is specified twice.
Source: DFSMSdfp

code is 12.
IEB344I

WARNING: INVALID STATEMENT

LABEL

message, the name field is greater than eight
characters, or contains an incorrect character.
Source: DFSMSdfp
IEB345I
CONTINUATION NOT STARTED IN 4-16
Explanation: The statement preceding this message

does not contain any characters in columns 4-16,
indicating that the statement is not a continuation.
However, the previous statement indicated that a
continuation statement was to follow.
code is 12.
Source: DFSMSdfp
IEB346I
MISSING PARENTHESIS

message, a closing parenthesis is omitted, or an error
was encountered in a parameter list before the closing
parenthesis.

Source: DFSMSdfp
IEB348I
PRECEDING MEMBER REQUIRES

IDENT
Explanation: Two MEMBER statements were

encountered; however, there was no RECORD IDENT
statement associated with the first MEMBER statement.
code is 12.
Source: DFSMSdfp
IEB349I
INCONSISTENT PARAMETERS IN
FIELD OR IDENT
Explanation: The first two parameters on an IDENT or

FIELD keyword are not consistent with each other.
code is 12.
727
error. Make sure that the length indicator is accurate for

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.


Source: DFSMSdfp
IEB350I
Explanation: In the RECORD statement preceding

this message, the literal specified in the FIELD keyword
is greater than 40 bytes.
12.
Source: DFSMSdfp
IEB351I
Source: DFSMSdfp
LITERAL LENGTH EXCEEDS 40

op, err, xxxx, acc
| IEB352I
|
|
|
|
|
|
|
|
Explanation: When DCB parameters RECFM, LRECL,

and BLKSIZE are not available from the output data set,
the IEBGENER program copies these values from the
input data set. One or more of the three DCB
parameters are copied. See the OS/390 DFSMSdfp
Utilities for a more detailed table.
|
|
|
|
|
|

change the output RECFM, BLKSIZE, and LRECL,
always specify the RECFM (except for U) and the
BLKSIZE on the output DD statement. Also, the LRECL
must be present on the output DD statement if editing is
required.
| Source: DFSMSdfp

while processing on the device indicated.
jjj
WARNING: ONE OR MORE OF THE

OUTPUT DCB PARMS COPIED FROM
INPUT
IEB353I
INVALID DBCS CHARACTERS IN

RECORD
Explanation: A record in the input data file contains

characters that are not valid DBCS characters. Valid
DBCS characters are X'4040' and two bytes with values
of X'41' through X'FE'.
Job name.
System Action: The program continues until all input

records have been processed. The return code is 8.
Step name.

Source: DFSMSdfp
sss
ddd
devtyp
Device type.
ddname
xxxx
IEB354I
INVALID SO AND SI CHARACTERS IN

RECORD.

SO and/or SI characters. SO and/or SI are in the wrong
location in the record, or they are unpaired (for every
SO, you must have an SI).

Access method.

acc
code is 12.
728
Source: DFSMSdfp
IEB355I
UNBRACKETED DBCS DATA.

DBCS data that should be bracketed with SO and SI
characters but is not.
Source: DFSMSdfp
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.
code is 8.

Source: DFSMSdfp
IEB360I
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
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.
Source: DFSMSdfp
IEB361I
Source: DFSMSdfp
IEB357I
DBCS DATA NOT AN EVEN NUMBER

OF BYTES
RECORD IDENTIFYING DBCS DATA

NOT BRACKETED.
DBCS ERRORS IN RECORD

nnnnnnnnnn.
Explanation: If the input data has DBCS errors, this

message identifies the record number (starting with 1)
of the record in error. Messages identifying the types of
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
bytes.
nnnnnnnnnn
The record number indicated.


records have been processed.


Source: DFSMSdfp
Source: DFSMSdfp
IEB358I
IEB362I
DBCS CV CONVERSION AND NO SO/SI

BYTES FOUND.
Explanation: DBCS CV conversion works on mixed

DBCS data. Mixed DBCS data must have at least one
set of SO and SI bytes.
Source: DFSMSdfp
IEB359I
DBCS STRING LENGTH ERROR.
text
Explanation: This message displays questionable

data in the input file. It may appear along with other
messages as additional information.
text
The text of the message.

records have been processed.
Source: DFSMSdfp
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.
729
IEB363I
DBCS LENGTH VARIABLE NOT AN

EVEN VALUE.
Explanation: The length variable contains a value that

is not an even number.
Source: DFSMSdfp
IEB364I
UNBRACKETED IDENTG LITERAL.
Explanation: The literal in an IDENTG parameter is

not bracketed with SO and SI bytes.
System Action: The program ends. The return code is
12.
Source: DFSMSdfp
IEB365I
WARNING SYSUT2 USING RECFM=U.

UNBLOCKED.
Explanation: The SYSUT2 DD statement did not

specify a record format but did specify a block size
(BLKSIZE). The SYSUT1 DD statement specified
RECFM=F. Because SYSUT2 did not specify RECFM,
the system supplies RECFM=U; thus, each block will
contain only one record.
IEB367I
WARNING SYSUT2 MEMBER NAME

NOT SPECIFIED FOR PDS
Explanation: An attempt was made to copy to a PDS

without specifying a member name on the SYSUT2 DD
statement.
System Action: The program is terminated. The return
code is 12.
Application Programmer Response: Specify at least
one GENERATE statement, one MEMBER statement
per output member, and RECORD statements as
required. Also, specify a member name on the SYSUT2
DD statement and resubmit the job.
IEB368I
SYSTEM DETERMINED BLKSIZE USED

FOR OUTPUT
Explanation: The SYSUT2 DD statement did not

specify a BLKSIZE. It need not be specified if LRECL
and RECFM are available from the input data set or
specified on the output data set. In these cases, if
output BLKSIZE is not specified, the system will
determine an optimal BLKSIZE, SDB
(system-determined BLKSIZE).
System Action: The system allows the job to run
through completion.
Source: DFSMSdfp
IEB401I
PRINT/PUNCH STATEMENT NOT FIRST.
System Action: The system allows the job to run to

completion.
Explanation: A PRINT or PUNCH statement is not the

first utility control statement.
Application Programmer Response: On the SYSUT2

DD statement, either specify all three parameters
(RECFM, LRECL, and BLKSIZE) or specify none of the
parameters. If you specify none, IEBGENER copies
RECFM, LRECL, and BLKSIZE from the SYSUT1
statement.

code is 12.
Source: DFSMSdfp
IEB366I
WARNING EMPTY DATA SET NOT

COPIED TO TAPE.
Explanation: An attempt was made to copy an

EMPTY data set to tape. The SYSUT2 data set will be
OPENED and CLOSED and an EOF will be written on
the tape but no data will be transferred.
System Action: The job runs to completion. The
return code is 4.

the problem.
Source: DFSMSdfp
IEB402I
INVALID OPERATION
Explanation: In the utility statement preceding this

message, the operation is incorrect.
code is 12.
730

the problem.
Source: DFSMSdfp
IEB403I
MORE THAN TWO TITLE

STATEMENTS.
Explanation: More than two TITLE statements are

included. Two TITLE statements are the maximum
number allowed.
preceding statement. If multiple RECORD statements

are included, make sure that an IDENT parameter is
contained in each statement except the last. The last
statement does not require the IDENT parameter.
the problem.
Source: DFSMSdfp
IEB406I
JOB TERMINATED AFTER USER EXIT

code is 12.
Explanation: The job was ended after control was

returned from an exit routine.


code is 12 or 16, as determined by the exit routine.

the problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEB404I
KEYWORD INVALID OR OMITTED

message, a required keyword is either incorrect or
missing.
code is 12.
the problem.
IEB407I
JOB TERMINATED DUE TO I/O ERROR

encountered.
code is 12.
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
that TYPORG=PO was not specified for a physical
sequential data set. If SYSUT1 record format is V or
VS, make sure there are no records less than the
minimum 5 bytes long. Make sure that SYSIN BLKSIZE
is a multiple of 80.
the problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEB408I
IEB405I
PARAMETER INVALID OR OMITTED

message, a required parameter is either incorrect,
inconsistent, or missing.
MEMBER memname CANNOT BE

FOUND
Explanation: The member specified is not contained

in the SYSUT1 data set.

code is 12.
memname

error. Correct or include the required parameter on the
System Action: The member is not printed or

punched. If there is another MEMBER statement, the
731
next member is read; otherwise, the program is ended.

the member to be printed or punched is contained in the
SYSUT1 data set.
the problem.
Source: DFSMSdfp

the problem.
Source: DFSMSdfp
IEB411I

OPENED
Explanation: The indicated DDNAME on the DD

statement does not exist. Perhaps a DDNAME is
misspelled in an existing DD statement or ddlist.
ddname
IEB409I
Explanation: The construction of the control statement

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.
the problem.
Source: DFSMSdfp
IEB410I
INCORRECT RECORD STATEMENT
Explanation: The RECORD statement preceding this

message is incorrect.
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
statement, make sure that the sum of the input-location
parameter and the length parameter does not exceed
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
specified output length minus one per printed line or per
punched card.
732
The DDNAME.

code is 12.
the problem.
Source: DFSMSdfp
IEB412I
INVALID INP/OUTP DCB PARAMETER
Explanation: One or more parameters in the BLKSIZE

or LRECL keywords were omitted from the
SYSUT1/SYSUT2 DD statement. The omitted
parameters were replaced by the value 1.
code is 12.
the DCB contains all necessary parameters.
the problem.
Source: DFSMSdfp
IEB414I
parm PARAMETER IS TOO SMALL
Explanation: The number of FIELD keywords, IDENT

keywords, literals, or name keywords in MEMBER or
RECORD statements is greater than the number
specified in parameter parm-MAXFLDs, MAXGPS,
MAXLITS, MAXLINE, or MAXNAME.
parm
The indicated parameter.

code is 12.
error. Specify a greater value for the parameter.
the problem.
Source: DFSMSdfp
IEB415I
VS/VBS DATA PROCESSED IN

BLOCKS
Explanation: The LRECL specified for the VS or VBS

input data area exceeds 32,756 bytes.
System Action: Processing continues on a physical
basis; that is, blocks, rather than logical records, are
printed or punched.
Source: DFSMSdfp

the problem.
Source: DFSMSdfp
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.
code is 12.
error. If SYSUT1 record format is VS or VBS, make
sure that TYPORG=PO was not specified.
the problem.
Source: DFSMSdfp
IEB416I
PREFORM, VS LRECL LARGER THAN

32K
Explanation: The LRECL specified for the VS or VBS

input data set exceeds 32,756 bytes, and PREFORM
was specified in the PRINT or PUNCH utility control
statement.
code is 12.
error. Reformat the data set or delete the PREFORM
parameter from the PRINT or PUNCH control
statement.
the problem.
IEB419I
USER RETURN CODE return-code

INVALID
Explanation: The return code was returned by the

user. However, the return code is incorrect if it is other
than 0, 4, or 16.
return-code
The return code.
System Action: The return code is ignored.

Processing continues according to prior conditions.
return code to 0, 4, or 16.
Source: DFSMSdfp
IEB420I
SYSIN IS EMPTY
Explanation: The SYSIN data set does not contain

any IEBPTPCH control statements.
Source: DFSMSdfp

code is 12.
IEB417I

DATA SET EMPTY, RETURN CODE IS 4.
Explanation: The data set to be printed or punched

contains no data.
System Action: The print or punch operation is
ended. The return code is 4.

733

the problem.
Source: DFSMSdfp
IEB421I

op, err, xxxx, acc

jjj
Job name.
sss
Step name.
error. Correct the incorrect keyword in the preceding

statement. If this is a LABELS command, make sure
that the keyword specified for the DATA= operand is
either ALL, ONLY, YES, or NO. If this is a PRINT
command, make sure that the parameter specified for
the CNTRL keyword is not greater than that specified
for the MAXLINE keyword. If this is a PUNCH
command, make sure that neither the INITPG nor
MAXLINE keyword has been specified.
the problem.
Source: DFSMSdfp
ddd
devtyp
Device type.
IEB432I
INVALID PARAMETER IN COLUMN dd
ddname

message, a parameter beginning in the column
indicated is either incorrect or not applicable to the
keyword for which it is specified.
dd
xxxx
System Action: The program is ended at the end of

the control statement scan. The return code is 12.
acc
Access method.
code is 12.
the problem.
Source: DFSMSdfp
IEB431I
INVALID KEYWORD IN COLUMN dd

message, a keyword beginning in the column indicated
is either incorrect or not applicable to the command for
which it is specified.
dd
The column indicated.

734

error. Correct the incorrect parameter on the preceding
statement. If the NAME, INREC, or OUTREC keywords
are specified, make sure that the parameter does not
exceed 8 characters.
the problem.
Source: DFSMSdfp
IEB433I
MISSING KEYWORD BEFORE COLUMN

dd

message, a required keyword that should appear before
the column indicated is either omitted, preceded, or
followed by an incorrect delimiter.
dd


the problem.
Source: DFSMSdfp
IEB434I
MISSING PARAMETER BEFORE

COLUMN dd

message, a required parameter that should appear
before the column indicated is either omitted, preceded,
or followed by an incorrect delimiter.
dd

error. Correct or include the required parameter on the
preceding statement. If a TITLE statement precedes this
message, make sure that the literal in the ITEM
parameter does not exceed 40 characters.
the problem.
Source: DFSMSdfp
IEB435I
MISSING COMMAND PRECEDING

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.
the problem.
Source: DFSMSdfp
IEB436I
INVALID COMMAND

message, a command is incorrect or incorrect because
of conditions set by commands, keywords, or
parameters on previous statements.
error. Correct the command on the preceding statement.
Make sure that previous keywords and parameters,
such as MAXGPS or MAXNAME, do not conflict with
this command or that no RECORD command precedes
the first MEMBER command.
the problem.
Source: DFSMSdfp
IEB437I
INVALID ITEM PARAMETER
Explanation: The title or output-location parameter

of the ITEM operand in a TITLE statement is incorrect.
code is 12.
error. Make sure that the title field of the ITEM
operand does not exceed 40 bytes, is not zero, or does
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
logical record length.
the problem.
Source: DFSMSdfp
IEB438I
INVALID NAME

message, the statement name is either too long or
contains an incorrect character.
However, the control statement is ignored.
735

the problem.
Source: DFSMSdfp
IEB439I
CONTINUATION NOT STARTED IN 4-16
Explanation: In the continuation statement preceding

this message, data does not begin in columns 4 through
16.
error. Make sure that the continuation statement begins
in columns 4 through 16. If the statement is not a
continuation, however, correct the previous statement
that indicates a continuation.
the problem.
Source: DFSMSdfp
IEB440I
MISSING PARENTHESIS

message, either a parenthesis is omitted, or there is an
error within the parentheses.
the problem.
be specified on the PRINT or PUNCH utility control

statement.
error. If SYSUT1 specifies a physical sequential data
set, remove the MEMBER statement. If SYSUT1
specifies a partitioned data set, specify TYPORG=PO
on the PRINT or PUNCH statement.
the problem.
Source: DFSMSdfp
IEB442I
USER LABEL I/O ERROR CAUSED

TERM.
Explanation: An uncorrectable I/O error occurred.

v A standard user label exit was present and the error
occurred during label processing.
v A user totaling exit was present and the error
occurred while the utility was placing data on the
output data set.
code is 12.
Application Programmer Response: If further
handling of the error is desired, the user exit should be
expanded to examine the standard status information
and issue an appropriate message.
Source: DFSMSdfp
IEB443I
INVALID CHARACTER IN ppppp nnnnnn
Explanation: An incorrect DBCS character code was

encountered.
ppppp
The position in the record.
nnnnnn The record.

System Action: The incorrect character code is
changed to a DBCS period. The system continues
processing. The return code is 8.
Source: DFSMSdfp

input data and resubmit the job.
IEB441I
Source: DFSMSdfp
MEMBER INVALID: TYPORG NOT PO
Explanation: The MEMBER statement preceding this

message is incorrect since physical sequential (PS)
organization was specified. That is, TYPORG=PO must
736
IEB444I
UNPAIRED SO IN ppppp nnnnnn
Source: DFSMSdfp
Explanation: An SO character is not paired with an

SI.
IEB448I
Explanation: The VC conversion variable is present,

but the DBCS parameter is NO.
ppppp
nnnnnn The record.

System Action: The incorrect SO will be changed to
an SBCS period. The system continues processing. The
return code is 8.
System Action: The system ends processing. The

return code is 12.
input parameters and resubmit the job.
Source: DFSMSdfp
IEB449I
Source: DFSMSdfp
IEB445I
UNPAIRED SI IN ppppp nnnnnn
CONVERSION VARIABLE VC INVALID
LENGTH ERROR IN RECORD

STATEMENT
Explanation: A DBCS conversion variable is present

on a record statement, but the length is odd.
Explanation: An SI character is not paired with an SO

character.

return code is 12.

ppppp
nnnnnn The record.

System Action: The incorrect SI is changed to an
SBCS period. The system continues processing. The
return code is 8.
Source: DFSMSdfp
IEB446I
ILLEGAL DBCS LENGTH ppppp nnnnnn
Explanation: A DBCS field has an odd length.

ppppp
Source: DFSMSdfp
IEB451I
FIELD OUTPUT LOCATIONS OVERLAP
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.
overlap error. Submit the job again.
Source: DFSMSdfp
IEB500I
END OF DISKETTE MAINTENANCE

UTILITY
nnnnnn The record.
Explanation: Normal end-of-job indication.
System Action: The SO and SI characters are

changed to an SBCS period. The system continues
processing. The return code is 8.
System Action: Normal system processing continues.

Source: DFSMSdfp
IEB447I
CONVERSION VARIABLE CV INVALID
Explanation: The CV conversion variable is present,

but the DBCS parameter is NO.
Source: DFSMSdfp
IEB501I
INCOMPLETE TRACK 0 INFORMATION
Explanation: Track 0 of the output diskette could not

be formed because not enough information was
specified by the input track 0 and/or control statements.
Message IEB512I will follow identifying the sectors in
error.
System Action: The job is ended.

return code is 12.
Application Programmer Response: Provide the

necessary control statements and resubmit the job.

Source: DFSMSdfp
737
IEB502D
MOUNT OUTPUT DISKETTE ON ddd
Explanation: The read operation of the Diskette

Maintenance Utility has been completed. The diskette to
be used for output should now be mounted on the
device so processing may continue.
ddd
The indicated device.

respond, then continues processing.
Operator Response: Mount the output diskette on
device ddd, ready the device, and reply U to continue
processing. If the output diskette is unavailable, then
processing may be ended by replying C.
Source: DFSMSdfp
IEB503D
ddd UNEXPIRED FILES ON OUTPUT

DISKETTE
Explanation: During a COPY operation from one

diskette to another diskette, the diskette to be used for
output contains unexpired data sets.
Application Programmer Response: Correct the DS

Source: DFSMSdfp
DS nn INVALID SPECIFICATION
IEB506I
Explanation: The information specified by the DS

statement was incorrect for one of the following
reasons:
v The data set identifier was specified incorrectly. The
data set identifier must conform to the IBM standard
for simple data set name.
v The creation and/or expiration date was specified and
was not of numeric yymmdd format, where
01=yy=99, 01=mm=12, and 01=dd=31.
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
do not maintain the proper relationship of TRK1
Sector 1 BOE EOE TRK73 sector 26, BOE
EOD, and EOD EOE plus 1.
Note: Sector number must be 1 and 26.
v The record length does not contain a value greater

than 0 and 128.
ddd
v The bypass indicator was specified and was not a B.
The indicated unit.

reply, then continues processing.
v The write protect indicator was specified and was not

a P.
Operator Response: If the data sets on the unit are to

be overridden, reply with U. If the data sets are not to
be overridden, but another diskette is available for use
as the output diskette, mount the diskette on the unit,
ready the unit and reply R. Otherwise the job may be
canceled by replying with a C.
v The verify indicator was specified and was not a V or

C.
v The multivolume indicator was specified and was not
a C or L.
v The volume sequence number was specified and was
not a two digit positive numeric value.
Source: DFSMSdfp
IEB504I
ERROR SECTORS ON OUTPUT

DISKETTE

attempting to write the output diskette.
nn
The DS statement.

incorrect information on the DS statement and re-submit
the job.

job using an error-free diskette for output.
Source: DFSMSdfp
Source: DFSMSdfp
IEB507I
DS nn INVALID EXTENT
Explanation:
IEB505I
INCORRECT FORMAT DS
STATEMENT
Explanation: The DS statement preceding this

message does not conform to the standard format of:
bDSxx nnnnnnnn,lllll,sssss, eeeee,hhhhh,
[,[[b],[a],[w],[r] ,[v],
[dd],[ffffff],[gggggg]].
738
v The beginning of extent, end of extent, or end of data

does not maintain the proper relationship of TRK1
Sector 1 BOE EOE TRK73 sector 26, BOE
EOD, and EOD EOE plus 1.
v The extent information overlaps an extent of an
already defined data set.
nn
IEB511I
The DS statement.

extent information and resubmit the job.
Source: DFSMSdfp

OPENED
Explanation: Required DD statement does not exist or

the OPEN macro instruction failed for the file specified
by the DDNAME.
ddname
IEB508I
The DDNAME.
SYSUT1 VOL1 SECTOR IN ERROR
Explanation: The VOL1 sector of the input diskette

could not be read and no VOL control statement was
supplied, or the VOL1 sector of the input diskette was
incorrect for one or more of these reasons:
v The label identifier (bytes 01-03) does not contain
VOL.

the DDNAME, if it is misspelled in the DD statement, or
insert a new DD statement with the correct name and
JCL parameters and resubmit the job.
Source: DFSMSdfp
v The volume label number (byte 04) is not 1.

v The volume identifier (bytes 05-10) does not contain
all alphabetic or numeric characters or is not
left-justified.
v The label standard version (byte 80) does not
indicate the standard version by containing a W.
Application Programmer Response: If the VOL1
sector is incorrect, correct it and resubmit the job. If the
VOL1 sector cannot be read, supply a VOL control
Source: DFSMSdfp
IEB512I
FILE NUMBER xx ERROR SECTOR
Explanation: The header 1 sector for the file number

could not be read from the input diskette and no DS
control statement was provided.
xx
The file number.

Application Programmer Response: Supply a DS
control statement for the file number and resubmit the
job.
Source: DFSMSdfp
IEB509I
INCORRECT CONTROL IDENTIFIER
Explanation: The control statement is not properly

identified.
errors in the identifier parameter of the utility control
statements (VOL and DS) and resubmit the job.
Source: DFSMSdfp
IEB510I
{SYSUT1 | SYSUT2} UNIT INVALID
Explanation: For SYSUT1, the device specified is not

3540. For SYSUT2, the device specified is not 3540 or
a direct-access device. If both SYSUT1 and SYSUT2
specify 3540, the unit specified must not be the same
unit.
and resubmit the job.
Source: DFSMSdfp
IEB513I
READ ERROR TRACK tt, SECTOR ss
Explanation: the track and the sector of the input

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
will be written to the output diskette. Processing
continues with the next sector.
tt
The track.
ss
The sector.

sector of the diskette.
Source: DFSMSdfp
IEB514I
EXCESS DS STATEMENTS
Explanation: More DS statements were provided than

there were error sectors in the input diskette track 0. A
DS statement should only be supplied for track 0
sectors that cannot be read.
739
excessive DS statements from the control data set and

resubmit the job.
Source: DFSMSdfp
IEB515I
CONTROL STATEMENT OUT OF

SEQUENCE

may be out of sequence for one of the following
reasons:
v A VOL statement was encountered and it was not the
first control statement in the control data set.
v A DS statement has a sequence number greater than
19 or less than 01.
v A DS statement has a sequence number which is not
greater than the sequence number on the preceding
DS statement.
v A DS statement has a sequence number that is not
numeric.
sequence error and resubmit the job.
Source: DFSMSdfp
IEB516I
SYSUT1 INCORRECT VOLUME
Explanation: The volume identifier specified on the

VOL control statement was not the same as the input
diskette.
IEB518D
ddd SECURE {INPUT | OUTPUT}

DISKETTE
Explanation: The diskette mounted for input or output

is a secure volume.
ddd
The device indicated.

Operator Response: For an input diskette, if the
volume is to be copied, reply q (where q is a
one-character volume accessibility indicator needed to
gain access to the volume). If the volume is not to be
copied, processing may be ended by replying with a
blank. For an output diskette, if the volume is to be
used, reply q, where q is the one-character volume
accessibility indicator needed to gain access to the
volume. If the secure volume is not to be used and
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
by replying with a blank.
Application Programmer Response: If a secure
volume is to be used as the input or output diskette,
notify the operator of the necessary volume security
qualifier when submitting the job.
Source: DFSMSdfp
IEB519I
Application Programmer Response: Insure that the

volume identifier specified on the VOL control statement
is the same as the volume identifier on the input
diskette and resubmit the job.
Explanation: The volume identifier specified on the

VOL statement preceding this message did not consist
of one to six left-justified alphameric characters.
Source: DFSMSdfp
IEB517D
ddd PROTECTED FILES ON OUTPUT

DISKETTE
Explanation: The diskette mounted for output contains

write protected data sets.
ddd

Operator Response: If another diskette is available
for use as the output diskette, mount the diskette on the
device, ready the device, and reply R. Otherwise the
job may be canceled by replying with a C.
Application Programmer Response: Supply an
output diskette which contains no write protected files.
Source: DFSMSdfp
740
INVALID VOL SPECIFICATION

volume identifier on the VOL statement and resubmit
the job.
Source: DFSMSdfp
IEB520I
DDNAME I/O ERROR
Explanation: An I/O error occurred on the device

specified by the DDNAME.
the type of error, resubmit the job allocating the file
specified by the DDNAME to a different device or
volume.
Source: DFSMSdfp
IEB521I
OUTPUT DISKETTE VOLUME

ACCESSIBILITY = s
Explanation: When forming track 0 for the output

diskette, a secure data set with a data set security
indicator was detected. The VOL1 label as read from
the input diskette or provided via the VOL control
statement did not have a volume accessibility indicator
specified. Since a secure data set must reside on a
secure volume, the volume accessibility indicator for the
output diskette was set to the indicated setting.
s
The data set security indicator.
System Action: Processing continues and the VOL1

label of the output diskette will be written with a volume
accessibility indicator of s.
Application Programmer Response: The volume
accessibility indicator will be required to access the data
on the diskette.
Source: DFSMSdfp
IEB530I
INVALID VOL1 LABEL on ddd, ser
Explanation: An attempt was made to process a

diskette with an incorrect VOL1 label. The VOL1 label
was incorrect for one or more of the following reasons:
VOL.
v The volume label number (byte 04) is not 1.
v The volume identifier (bytes 05-10) does not contain
all alphabetic or numeric characters or is not left
justified.
v The volume accessibility qualifier on a continuation
volume is different from that of the preceding volume
of a multivolume diskette data set.
v The label standard version (byte 80) does not
indicate the standard version by containing a W.
ddd
The device address.
ser
The contents of the volume identifier field.
System Action: If the error was data set related (e.g.

volume accessibility qualifier on a continuation volume),
processing of the data set is ended and processing
continues with other data sets on the same diskette. If
the error was volume related, processing on this
diskette is ended and processing continues with the
next diskette.
Operator Response: Notify the owner of the diskette
of the error condition.
error(s) in the volume label and rerun the job, if
necessary.
Source: DFSMSdfp
IEB531I
INVALID HDR1 FOR dsid ON ser, ddd
Explanation: The HDR1 label for the dsid on the

volume device was incorrect for one of the following
reasons:
HDR.
v The label number (byte 04) does not contain 1.
v There are duplicate data set identifiers on this
diskette.
v The interchange level indicator does not indicate the
basic interchange architecture.
v The beginning of extent (BOE) (bytes 29-33), end of
extent (EOE) (bytes 35-39), or end of data (EOD)
(bytes 75-79) does not maintain the proper
relationship of TRK1 Sector1 BOE EOE TRK73
Sector 26, BOEEOE, BOEEOD, and EODEOE
address plus 1.
v The extents of BOE and EOE overlap the extents of
another data set on the diskette.
v The block length (bytes 23-27) contains a value of 0
or is greater than 128.
v The volume sequence number is incorrect.
v The data set security qualifier was non-blank and the
volume accessibility indicator was blank.
v The block length on a continuation volume is different
from that of the preceding volume of a multivolume
diskette data set.
v The Bypass Indicator does not contain a blank or B,
(input only).
v The Write Protect Indicator does not contain a blank
or P, (output only).
v A verified data set was requested, but the data set
was not verified.
v The Expiration Date is incorrect, (output only).
v The Data Set Security Qualifier on a continuation
volume is different from that of the preceding volume
of a multivolume diskette data set.
ddd
The device address.
ser
The volume identifier from the VOL1 label.
dsid
The contents from the data set identifier field of

the HDR1 label.
System Action: If the device is processing input data

sets, the request for the data set is ended. The system
will continue processing with the next data set.
If the device is processing output data sets, the diskette
is flushed and the system will continue processing with
the next diskette.
Operator Response: If the device is being used for
output, inform the owner of the diskette of the error. If
741
the device is being used for input, there is no response

necessary.
error(s) in the HDR1 label and rerun the job if
necessary.
Source: DFSMSdfp
IEB532A
MOUNT vvvvvv ON ddd
Explanation: During processing of a diskette data set,

the operator inadvertently unloaded a diskette with the
VOLSER indicated and loaded another diskette on the
device.
vvvvvv The volume serial number.

ddd
System Action: Wait until diskette with VOLSER is

mounted and continue processing.
Operator Response: Mount diskette with VOLSER
indicated.
Source: DFSMSdfp
dsid
The multivolume input data set.
System Action: Wait for operator response and

Operator Response: Provide the correct diskettes in
the correct order, without any intervening diskettes, and
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
cancel processing of the data set.
diskettes for the multivolume file are contiguous and in
the correct order before submitting the job.
Source: DFSMSdfp
IEB541D
M ddd,vvvvvv
Explanation: The volume was specified as the

diskette volume containing the JCL data set, but the
volume was not the first diskette mounted on the 3540
device.
ddd
vvvvvv The volume serial number.

IEB540D
DISKETTE SEQUENCE ERROR, ddd,

dsid

to open the input data set or while processing
continuation diskettes of the multivolume input data set
on the device. A continuation diskette is any diskette in
a multivolume file except the first one. The sequence
error is a result of one of the following conditions:
v The continuation volume in the drive unit does not
contain a HDR1 label describing the data set being
processed. This condition may arise because
diskettes with incorrect VOL1 or HDR1 labels have
been flushed.
v The volume sequence number in the HDR1 label
describing the first extent of the data set was one.
The volume sequence number in the HDR1 label
describing the extent now in the drive unit is a value
other than one greater than the previous volume
sequence number.
v The volume sequence number in the HDR1 label
describing the first extent of the data set was
non-blank and was not 1.
v While opening a data set, a volume sequence
number of other than blank or one was found in the
HDR1 label.
v While opening a data set, a multivolume indicator of
L was found in a HDR1 label with a blank volume
sequence number.
System Action: Wait for operator response and

Operator Response: Mount the diskette volume on
the device, ready the device, and reply R to retry. If
unable to supply the diskette volume, reply C to cancel
processing of the volume.
Application Programmer Response: When
submitting a diskette volume containing a JCL data set,
be sure that the operator is informed of the correct
Source: DFSMSdfp
IEB542D
SECURE {VOLUME | DATA SET} ON

ddd,ser[,jobname] [,dsid]
Explanation:
v For a secure volume, the volume specified on the
device is a secure volume and additional qualification
is required to access it. The additional qualification on
input is required to allow further processing of the
data sets on the volume. On output the additional
qualification is required to allow data sets to be
created on the volume.
v For a secure data set, the data set specified with a
volume identifier on the device is a secure data set
and additional qualification is required to access it.
ddd
ddd
ser
742
jobname
The jobname.
dsid
The data set identifier.
System Action: Wait for the operator response, and

Operator Response: Specify the qualifier for volume
ser or specify the qualifier for data set dsid on volume
identified by ser with a reply of:
REPLY xx, q
where q is the one character qualifier that must match
the volume accessibility indicator or data set security
indicator to gain access to the volume or data set. If no
qualifier is available, reply with
REPLY xx, b.
If b is replied or the correct qualifier is not supplied in
three attempts, the data set will not be accessed.
operator of the necessary volume and data set security
qualifiers prior to submitting the job stream.
Source: DFSMSdfp
IEB543I
IEB544E
ddname DD MISSING OR INVALID FOR

DISKETTE READER
Explanation: The DD statement specified was missing

from the JCL supplied for running the diskette reader or
was incorrect for one of the following reasons:
v The UNIT specified on the SYSDATA DD statement
was not a 3540 device.
v The SYSUT2 DD statement did not describe a
subsystem data set.
v The SYSUT3 DD statement did not describe a DASD
(or VIO) device to contain the intermediate partitioned
data set.
ddname
Specified the DD statement.
System Action: The diskette reader is ended.
Operator Response: If JCL parameters were
overridden using the START command, be sure that the
overridden values are valid.
Application Programmer Response: The system
programmer should be sure that any reader procedures
for use by IEBDKRDR contain required DD statements
that define valid devices.
Source: DFSMSdfp
ASSOCIATED DATA SET LIMIT

EXCEEDED READING JOB jjj FROM
ddd
Explanation: While reading the job from the device

indicated, the diskette reader encountered a DD * or DD
DATA statement with the DSID keyword, and the limit of
associated data sets per job stream has already been
reached, or more than 1,000 associated data set
requests have been detected in the current job.
jjj
The job name.
ddd
System Action: The diskette reader stops processing

the JCL input stream and beings reading the required
associated data sets. When associated data set
processing is complete the diskette reader ends
processing. The job stream beginning with the job is
flushed from the system and must be resubmitted.
Operator Response: In order to have the diskette
reader process the remaining jobs in the input stream
after associated data set processing is complete, do
v If the device is card reader, place the rest of the job
stream, beginning with the job, back into input device.
Initiate another diskette reader task to process the
remaining jobs.
v If the device is not a card reader, initiate another
diskette reader to the same input data set, specifying
the job as the starting point for the reader.
number of associated data sets per job stream can be
increased, if necessary, by changing the PARM
specified on the EXEC statement for the diskette reader.
Source: DFSMSdfp
IEB545I
FOLLOWING DATA SET(S) NOT FOUND

ON ddd
Explanation: A delimiter (/*DSKT) diskette was

encountered on the device. The associated data sets
described in message IEB546I, which follows, are
required by the job stream but were not found on
diskettes on the device.
ddd
System Action: Messages IEB546I and IEB547A are

written listing the data sets and requesting operator
response.
Source: DFSMSdfp
743
DSNAME=dsname JOBNAME=jjj
[,VOLSER=volser]
IEB546I
Explanation: The data set on the VOLSER indicated

is not available for the job on the device named in
message IEB545I. This message appears for each data
set that is not available. VOLSER appears only if it was
coded on the DD statement describing the data set as
an associated data set.
dsname
The data set name.
jjj
The jobname.
volser
System Action: The system action is determined by

the operators response.
Operator Response:
v If the data set(s) listed in message IEB546I are
available, the operator should load the diskettes
containing those data sets into the hopper of the
device named in the message IEB545I, ready the
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
should reply GO. The diskette reader will then
resume processing without the required associated
data sets.
System Action: Message IEB547A is written

requesting operator response.
Application Programmer Response: All associated

data sets required for a given job stream should be
available when the job stream is processed by the
diskette reader.
Source: DFSMSdfp
Source: DFSMSdfp
IEB547D
IEB548E
REPLY RETRY OR GO
Explanation: This message follows messages IEB545I

and IEB546I which describe associated data sets that
appear to be missing from the diskettes containing
associated data sets. An associated data set is
considered a missing data set in the following cases:
v The requested data set is on a diskette that was fed
into the 3540 stacker while reading part of a
multivolume data set on the same diskette.
v The job stream contains more than one associated
data set request for a data set that is the only data
set on the diskette. After the data set has been read
to satisfy the first request, the diskette is placed in
the stacker and is therefore unavailable for other
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
data set request due to key entry errors.
v The requested data set was not on the diskettes
submitted with the job.
v The operator did not supply the correct volume
accessibility qualifiers for the diskette containing the
data set during the allowed three attempts.
v The volume containing the requested associated data
set did not have a valid VOL1 label and therefore
was placed in the stacker without searching for data
sets.
v The index track on the volume containing the
requested associated data set could not be read and
the diskette was therefore placed in the stacker
without searching for data sets.
In the first two cases, the missing data sets may be
retrieved by replacing the diskettes in the 3540 hopper
and indicating that the reader should again search the
diskettes.
744
ddd INPUT ERROR [,READING JOB jjj]
Explanation: An uncorrectable input error occurred

while a diskette reader was reading the job in the JCL
input stream, or while a diskette reader was reading
associated data sets. The optional jobname is not
specified if the error occurred while reading associated
data sets. If a blank jobname is specified, the error
occurred on the JCL input stream before any job was
encountered or after an erroneous job statement with no
jobname was encountered. When reading a multivolume
JCL data set from the 3540, the message will result
from conditions that prevent successful end-of-volume
processing.
ddd
jjj
The job name.
System Action: If the error occurred while reading the

JCL input stream, the diskette reader continues normal
processing assuming that the jobs preceding the job
indicated are the only jobs in the job stream. Jobs
through the end of the job stream are ignored. If the
error occurred while reading associated data sets, the
diskette reader will be ended.
Operator Response: After the error-producing device
has been corrected, start another diskette reader. If a
jobname was written in this message, do one of the
following:
v If the device is card reader, place the rest of the job
stream, beginning with the job indicated back into
input device. Initiate another diskette reader task to
process the remaining jobs.
the job indicated as the starting point for the reader.
v If no jobname was written in this message, the whole

job stream must be re-run.
Source: DFSMSdfp
Application Programmer Response: Insure that the

IEFRDER and SYSDATA DD statements are valid.
IEB550E
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
had already been encountered.
IEB549I
ddname, DISKETTE READER OPEN

FAILED
Explanation: The diskette reader was unable to

OPEN the file because the OPEN macro instruction was
unsuccessful for the specified file, or the IEFRDER file
is using a 3540 device and one of the following errors
was detected:
v The diskette data set specified as containing JCL
does not have 80 for a record length.
v No volume serial number was specified in the DD
statement.
v No data set name was specified in the DD statement
or supplied in the START command.
v The data set specified in the DD statement could not
be located on the specified diskette.
v The operator was unable to provide volume
accessibility or data set security qualifiers for the
requested data set.
v The specified volume has an incorrect VOL1 label.
v The HDR1 label describing the specified data set is
incorrect.
v A permanent I/O error occurred while trying to read
the label track on the specified diskette.
v A delimiter (/*DSKT) was provided in the 3540 as the
diskette containing the JCL data set.
v A reply of C was given to message IEB541A.
v The volume serial number specified is an incorrect
diskette volume identifier.
jjj
The job name.
ddd
System Action: The diskette reader stops processing

the JCL input stream and begins reading the required
associated data sets. When associated data set
processing is complete, the diskette reader ends
processing. The job stream beginning with the job
indicated is flushed from the system and must be
resubmitted.
Operator Response: In order to have the diskette
reader process the remaining jobs in the input stream
after associated data set processing is complete, do
v If the device is a card reader, place the rest of the job
stream, beginning with the job indicated, back into
the input device. Initiate another diskette reader task
to process the remaining jobs.
the job indicated as the starting point for the reader.
number of associated data sets per job stream can be
increased, if necessary, by changing the PARM
specified on the EXEC statement for the diskette reader.
Source: DFSMSdfp
IEB551I
DATA SET NOT AVAILABLE

CODE=ccc
ddname
The file specified by the OPEN.
Operator Response: Ensure that the correct volume
serial number and data set name were supplied in the
START command and the correct diskette was provided
in the 3540. Ensure that the correct volume accessibility
and data set security qualifiers were provided if
requested by the diskette reader.
was unable to correct the problem, the programmer
should ensure that his run instructions were correct. If
the run instructions were correct, the diskette that
contains the JCL should be checked for label incorrectly
or errors. If the diskette is good, or if no diskette was
involved in the error, the system programmer should
ensure that procedures used for starting the diskette
reader correctly define the required files.
JOB NUMBER LIMIT EXCEEDED

READING JOB jjj FROM ddd
Explanation: The data set specified in the DD

statement preceding this message was not successfully
retrieved from the associated data set stream for the
reason indicated by the condition code.
ccc
the condition code, as follows:

Code
Explanation
132
The operator replied GO after

messages IEB545, IEB546, and
IEB547 were issued describing this
data set.
202
Requested data set was found but

operator did not successfully supply
the volume accessibility qualifier.
745
204
Requested data set was found, but

operator did not successfully supply
the data set security qualifier.

problem indicated by the return code and resubmit the
job.
212
Requested data set id described by

an incorrect HDR1 label. Message
IEB531I indicates possible causes.
Source: DFSMSdfp
216
Requested data set was found, but

permanent I/O error occurred while
priming buffers.
224
228
300
A volume sequence error was

detected while attempting to open the
data set. The operator replied C to
message IEB540D.
The VOLSER specified in JCL was
found, but it did not contain the
requested data set. If there were
duplicate VOLIDs in an ADS stream,
the first volume encountered with a
given identifier must contain data sets
specifying that VOLID or this message
results.
Requested data set was found and
opened, but an error was encountered
while reading the data set.
INVALID PARAMETERS SUPPLIED TO

DISKETTE READER
Explanation: The value supplied for the PARM=

keyword on the EXEC statement of the JCL or as a
PARM= override in the START command was not
numeric or exceeded six characters.
Operator Response: If a PARM override was supplied
in the START command, check its validity. If in error,
issue another START command using valid parameter
values.
Application Programmer Response: If the error is
not in operator provided parameter values, correct the
errors in the JCL provided to run the diskette reader.
Source: DFSMSdfp
IEB553I
DISKETTE READER UNABLE TO GET

TABLE SPACE
310

opened, but an incorrect VOL1 label
was encountered in EOV processing
for a multivolume data set. Message
IEB530I indicates possible reasons
the VOL1 label was incorrect.
312

opened, but an incorrect HDR1 label
was encountered in EOV processing
for a multivolume data set. Message
IEB531I indicates possible reasons
the HDR1 label was incorrect.
Operator Response: Start the program again

specifying a smaller PARM= value.

opened, but a permanent I/O error
occurred while reading the data set.
Source: DFSMSdfp
316
320

opened, but a delimiter diskette was
encountered while reading the data
set.
324

opened, but during EOV processing of
a multivolume data set, the operator
replied C to message IEB540A.
408
The volume identifier specified in JCL

was incorrect as a volume identifier
for a diskette.
System Action: Processing was discontinued for data

set specified by the data set identifier. The job
requesting the data set will be run TYPRUN=SCAN in
order to pass this message back to the programmer as
a JCL comment statement.
746
IEB552I
Explanation: The program was unable to get space

for a data set name table large enough to accommodate
the number of associated data sets specified on the
PARM= keyword.

JCL used to run the diskette reader so that the PARM=
value is small enough to have space acquired.
IEB554E
ddname, DISKETTE READER I/O

ERROR [,PROCESSING JOB jjj ]
Explanation: An I/O error occurred on the file

specified by either SYSUT2 or SYSUT3. The error
prevents further processing by the diskette reader. A
blank jobname indicates the error occurred before a job
was encountered in the JCL stream or after an
erroneous job statement with no jobname was
encountered.
ddname
The DD name.
jjj
The job name.
System Action: The diskette reader is ended. If some

jobs have been passed to the subsystem, the optional
jobname in the message will indicate at which job the
job stream processing should be resumed on a later

attempt. The job named in the message may have been
partly passed to the internal reader before the error
occurred.
Operator Response: Start the diskette reader again. If
no jobname was specified, the entire job stream must
be re-run. If a jobname was specified, only the jobs
starting with the specified job must be re-run.
specified DD statement is satisfactory for the diskette
reader.
Source: DFSMSdfp
IEB555E
DISKETTE READER DIRECTORY

ERROR
Explanation: The diskette reader issued a STOW or

BLDL macro instruction to access the directory of the
SYSUT3 intermediate file. The STOW or BLDL could
not be successfully completed for one of the following
reasons:
v Not enough directory blocks were allocated for the
SYSUT3 file, (applicable to STOW only).
v The directory access failed because of permanent I/O
errors.
v Insufficient virtual storage was available to perform
the STOW or BLDL function.
Operator Response: If the number of associated data
sets to be processed (PARM= value) or the number of
directory entry blocks allocated to the SYSUT3 file were
modified via the START command, insure that the
values were reasonable. The number of associated data
sets should not be so large as to leave no virtual
storage for the STOW function. The number of directory
entry blocks should be 1 + (number of ADS 20). If
these values were reasonable, the error was caused by
an I/O error in the SYSUT3 file. Correct the cause of
the error if possible, and start the diskette reader again
to run the job stream.
number of associated data sets and number of directory
entry blocks specified in the JCL. Then rerun the
diskette reader.
Operator Response: Remove the remainder of the

jobstream from the hopper and feed mechanism if a
card reader is used to read JCL. Use a merge mode
reader to process the remainder of the jobstream
starting with the job indicated.
Source: DFSMSdfp
ddd,ser NON-SCRATCH DISKETTE

FOUND
IEB570I
Explanation: The diskette that was just fed into the

stacker was not a scratch diskette (that is, it contained a
write protected data set or an unexpired data set) and,
therefore, was not suitable to receive an output data
set.
ddd
The device address.
ser
The volume identifier from the VOL1 label.
System Action: Continue processing with the next

diskette.
Operator Response: Provide additional scratch
diskettes, if needed, to allow the diskette writer to
complete processing.
Source: DFSMSdfp
jjj, dsid ON VOL(S) xx [, xxx,xxx,xxx,xxx]
IEB571I
Explanation: A diskette writer has written the data set

identified for the job indicated, on the diskette(s) having
the volume serial(s) listed. If the data set spans more
than five diskettes, the message appears after the fifth
diskette has been completed, and will be issued again
to list the next group of diskettes used.
jjj
The job name.
dsid
xxx
The listed volume serial numbers.
System Action: Continue processing.

Operator Response: The operator may use this
information to correlate the diskettes with the jobs
submitted.
Source: DFSMSdfp
Source: DFSMSdfp
IEB556E
IEB572E
DSID KEYWORD ENCOUNTERED

READING JOB jjj
Explanation: A direct mode diskette reader detected

the DSID keyword while processing the job.
jjj
The job name.
ddd DISKETTE WRITER CLOSED,

OUTPUT ERROR
Explanation: This message occurs when a permanent

I/O error is encountered by the diskette writer on the
device.
ddd
747
System Action: The diskette writer to device ddd is

ended.
Operator Response: Change the diskette and start
another diskette writer. Save the diskette.
Source: DFSMSdfp
IEB573E
DATA SET NOT WRITTEN FOR, JOB=

jjj, CLASS=c
Explanation: The diskette writer has selected a

SYSOUT data set for the job indicated with output in the
class indicated that did not have a DSID specified on its
DD statement. A DSID is required for data sets being
written to a 3540 device.
jjj
The job name.
The class.
jjj
The job name.
ddd
System Action: Wait for the operator response, and

Operator Response: Specify the security parameters
for the data set with the jobname as requested by the
programmer. The general form of the reply is:
REPLY xx,YYMMDD,w,d,v
YYMMDD is the expiration date that the data set can be
purged.
is the write protect indicator to indicate that the data

set is write protected. This must be a blank or P.
is the one character data set security indicator. To

secure a data set, both the data set security and
volume accessibility indicators must be set.
is the one character accessibility indicator. This

secures the volume from unauthorized access.
System Action: The data set is unallocated KEEP in

the class. The data set remains on spool.
Operator Response: Route the data set to the
appropriate class for output for processing to some
device other than a 3540.
Application Programmer Response: If a data set is
to be written on a diskette, be sure to specify a DSID on
the SYSOUT DD statement for that data set.
Source: DFSMSdfp
IEB574I
IEFRDER DD STATEMENT MISSING OR

INVALID FOR DISKETTE WRITER
If a parameter is not to be specified, the comma should

be entered to denote the missing parameters. r
xx,741231,,,x indicates the expiration date and volume
accessibility. r xx,,P specifies write protection.
All data sets get a minimum of one day date protection
and sequence number protection. When extended
security is used while processing in multi-data sets per
diskette mode, the volume accessibility indicator must
be specified for the first data set to be secured and
cannot be specified for any other data sets on that
diskette.
Explanation: There was no IEFRDER DD statement

supplied in the JCL or the diskette writer was started to
a device that was not a 3540.

operator of the level of data set security required for the
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
Application Programmer Response: The system

programmer should be sure that diskette writer
procedures specify a 3540 as the device for the
IEFRDER DD statement.
Source: DFSMSdfp
IEB575A
SPECIFY SECURITY FOR

DSNAME=dsname, JOB=jjj, ON ddd
Explanation: A diskette writer has been started to

write secure data sets on the device. The data set for
the job indicated requires the operator to specify the
security parameters.
dsname
The data set name.
748
SYSIO ERROR ON dsid FOR JOB jjj
Explanation: While processing the data set for the job

indicated the diskette writer (IEBDKWTR) detected an
uncorrectable I/O error reading the data set from spool.
dsid
jjj
The job name.
System Action: The diskette writer will stop

processing the input data set and will go on to process
other input data sets.
Application Programmer Response: Recreate the
data set by processing the job step that produced it.

the problem.
the same data set identifiers, care should be taken to

insure that they are processed in one data set per
diskette mode.
Source: DFSMSdfp
Source: DFSMSdfp
IEB577E
ddd DISKETTE WRITER ENDED, {OPEN

| SUBSYSTEM | ALLOCATION} ERROR
Explanation: The diskette writer to the device

detected an error condition that was uncorrectable
based on the return codes received from one of the
following:
IEB579I
INVALID PARAMETERS SUPPLIED TO

THE DISKETTE WRITER
v The subsystem interface.
Explanation: The parameters supplied for the PARM=

keyword on the EXEC statement of the JCL, the
PARM= override in the START command, or the fourth
positional parameter of the START command were
incorrect.
v The subsystem
v Dynamic allocation/unallocation.
v Subsystem data set.
System Action: The diskette writer to device ddd is
ended.
system programmer and make sure the problem
determination information is available.
Application Programmer Response: For allocation
and subsystem errors, the system programmer should
examine the error message IEB581E, in the message
data set.
SYSOUT output for the job and all printed output and
Source: DFSMSdfp
IEB578I
ddd DUPLICATE DATA SET IDENTIFIER

dsid FOR jjj
Explanation: While processing diskette output data

sets for the job indicated in multiple data sets per
diskette mode, the diskette writer to the device
encountered two data sets with the same data set
identifier.
ddd
jjj
The job name.
dsid
System Action: The diskette writer will write the data

set on the next scratch diskette and continue
processing.
Operator Response: Inform the programmer that
submitted the job of this condition.
Application Programmer Response: When
submitting jobs that create diskette output data sets with
Operator Response: If a START command was used

to override parameters in the JCL, check to be sure
they were valid. If they were incorrect, issue another
START command using valid parameters. If they were
valid, notify the programmer.
errors in the JCL provided to run the diskette writer.
Source: DFSMSdfp
IEB580I
OPEN ERROR DISKETTE WRITER
Explanation: The diskette writer was unable to OPEN

the IEFRDER file because the OPEN macro instruction
was unsuccessful.
Application Programmer Response: The
programmer should insure that the JCL used for starting
the diskette writer is correct.
Source: DFSMSdfp
IEB581E
{SUBSYSTEM INTERFACE |
SUBSYSTEM REQUEST | DYNAMIC
ALLOC/UNALLOC} ERROR, return-code
Explanation: The diskette writer detected a return

code from the subsystem interface, subsystem request,
or dynamic allocation and could not recover.
return-code
The return code.

cause of the error indicated by the return code and
rerun the job.
749
Source: DFSMSdfp
acc
Access method.
IEB600I
UTILITY PROGRAM IEBISAM HAS

SUCCESSFULLY COMPLETED THE
REQUESTED OPERATION
COMPLETION CODE=00
Explanation: The program has successfully completed

the requested operation.
System Action: Program operation has completed.
Source: DFSMSdfp
IEB601I
DCB FIELD VALUES INCONSISTENT

COMPLETION CODE=08
Explanation: One or more of the following DCB

subparameters are incorrect: RECFM LRECL, BLKSIZE,
RKP, and KEYLEN.
System Action: The program is ended. The requested
operation is not performed. The return code is 8.
error. Correct the incorrect DCB subparameters.
the problem.
Source: DFSMSdfp
IEB602I
jjj, sss, ddd, devtyp, ddname, op, err,

xxxx, acc COMPLETION CODE=08

while processing on device ddd. In the message text,
the error analysis information provided by the
SYNADAF data management macro instruction issued
by the SYNAD routine was:
jjj
Job name.
sss
Step name.
ddd
devtyp
Device type.
ddname
xxxx
750

code is 8.
DCB information is consistent with the original indexed
sequential data set.
the problem.
Source: DFSMSdfp
IEB603I
DUPLICATE RECORD COMPLETION

CODE=08
Explanation: A record key is identical to a record key

previously placed in the indexed sequential data set.
Possibly, the RKP or the KEYLEN parameter has been
changed. This message appears for a LOAD operation
only.
System Action: The program is ended.
Reconstruction of the indexed sequential data set is
incomplete. The return code is 8.
Application Programmer Response: UNLOAD the
original indexed sequential data set and respecify the
LOAD operation. Also, specify the original DCB
parameters in the SYSUT1 and SYSUT2 DD
statements.
the problem.
Source: DFSMSdfp
IEB604I
NUMBER OF CHARACTERS TO BE
TRANSMITTED EXCEEDS LIMIT
COMPLETION CODE=08
Explanation: The number of characters in a

fixed-length record exceeds the value specified in
LRECL or in LRECL + KEYLEN (for fixed-length,
unblocked records with a relative key position of 0). This
message appears for a LOAD operation only.
System Action: The program is ended. The requested
operation is not performed. The return code is 8.
error. Correct the LRECL subparameter and unload the
original indexed sequential data set. Then, respecify the

LOAD operation.

the problem.

the problem.
Source: DFSMSdfp
Source: DFSMSdfp
IEB605I
CLOSE REQUESTED BY USER AFTER

A USER EXIT COMPLETION CODE=04
Explanation: The return code returned by the user

was either 4 or 12.
code is 4.
Source: DFSMSdfp
IEB606I
ILLEGAL RETURN CODE RECEIVED

FROM A USER EXIT COMPLETION
CODE=12
IEB608I
INVALID OPTION IN THE PARM FIELD

OF THE EXECUTE CARD COMPLETION
CODE=16
Explanation: The PARM parameter of the EXEC

statement is incorrect.
code is 16.
the problem.
Source: DFSMSdfp

was other than 0, 4, 8, or 12.
IEB609I

code is 12.
Explanation: Either a record was lost, or a noise

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.
the problem. Have a listing of the exit routine available.
Source: DFSMSdfp
IEB607I
SYSUT2 OR SYSUT1 DD CARD

MISSING. COMPLETION CODE=16
Explanation: No SYSUT1 or SYSUT2 DD statement

was included in the job step.
code is 16.
INPUT SEQUENCE ERROR

COMPLETION CODE=08

code is 8.
Application Programmer Response: If possible, use
a backup copy of the unloaded data set. UNLOAD the
original indexed sequential data set, and respecify the
LOAD operation. Also, specify the original DCB
parameters in the SYSUT1 DD statement.
the problem.
Source: DFSMSdfp
IEB700I
DATA GENERATION HAS BEEN

[SUCCESSFULLY] COMPLETED.
COMPLETION CODE IS ccc
Explanation: If the code is ZERO, data generation

was successfully completed.
If the code is FOUR, the job step was ended at the
request of the user.
751
If code is EIGHT, an error occurred while processing a

utility control statement.
IEB703I
If the code is TWELVE, an error occurred while

processing an input or output data set.
If the code is SIXTEEN, incorrect parameters were
encountered in a data control block while opening a
data set.
INVALID KEYWORD VALUE.

DELIMITER, DESCRIPTOR OR TYPE IS
IMPROPER OR DUPLICATED. AN FD
NAME HAS OCCURRED PREVIOUSLY.
Explanation: The keyword value pinpointed by

message IEB727I (if any) is incorrect. Possibly:
v A double quote specified within a picture caused an

incorrect length.
ccc
v A starting character of * was used when AL or AN

format was specified.
The completion code.
System Action: The program is ended.

ZERO or FOUR, no action is necessary.
If the code is EIGHT, correct the appropriate control
statements, and resubmit the job step.
If the code is TWELVE, correct the error condition
described in message IEB729I, and resubmit the job
step.
If the code is SIXTEEN, correct the appropriate DD
statement, and resubmit the job step.
the problem.
Source: DFSMSdfp
IEB702I
OPERATION WAS NOT DSD, FD,

CREATE, REPEAT, OR END. CORRECT
AND RERUN.
Explanation: The preceding utility control statement

specified an incorrect operation; that is, the operation
was not DSD, FD, CREATE, REPEAT, or END.
v A character other than 0-9 or A-F was used when a

hexadecimal digit was to be specified.
v A non-numeric character was used when a decimal
number was to be specified.
v A keyword was misspelled.
v An FD statement contained a previously used name.
v Mutually exclusive subparameters are encountered
such as FORMAT=CO and ACTION=RO. In this
case, message IEB727I will not precede this
message.
System Action: Syntax checking of the remainder of
the utility control statements in this set continues, but no
additional data is generated. Processing continues
normally with the next DSD statement encountered. The
return code is 8.
error. Since the output data set may have been only
partially completed, run IEHPROGM to scratch the data
set, if necessary. Correct the error and resubmit the job.
the problem.
Source: DFSMSdfp

return code is 8.
IEB704I

Explanation: The ddname specified on a CREATE or

FD statement was not referred to on the DSD statement
beginning this set of utility control statements. The
IEBDG program was unable to open the data set.

the problem.

return code is 8.
Source: DFSMSdfp
752
INPUT DDNAME ON CREATE OR FD

CARD IS NOT SPECIFIED ON DSD
CARD.


the problem.
Source: DFSMSdfp
IEB705I
INVALID KEYWORD, POSSIBLE

IMBEDDED COMMA.
Explanation: The keyword pinpointed by message

IEB727I is incorrect. Possibly, the keyword is misspelled
or contains an embedded comma.
return code is 8.
the problem.
Source: DFSMSdfp
IEB706I
NUMBER SPECIFIED IS LARGER THAN

32,767 OR EXCEEDS MACHINE
CAPACITY.
Explanation: A length parameter on an FD statement

was specified larger than 32,767 or machine capacity
during an INDEX operation. No conversion is
performed.
return code is 8.
the problem.
Source: DFSMSdfp
IEB707I
FD NAME ON CREATE CARD IS NOT

PREVIOUSLY DEFINED BY AN FD
CARD OR IS NOT ASSOCIATED WITH
CORRECT DCB.
Explanation: The NAME parameter on a CREATE

statement does not specify a value previously defined
on an FD statement.
return code is 8.
the problem.
Source: DFSMSdfp
IEB708I
PICTURE LENGTH TOO LARGE FOR

CONVERSION
Explanation: A decimal picture was to be converted to

packed decimal or to a binary equivalent; however, the
number of digits specified in the picture exceeds 16. No
conversion is performed.
return code is 8.
the problem.
Source: DFSMSdfp
753
IEB709I
USER EXIT ROUTINE RETURNED AN

INVALID RETURN CODE
Explanation: The return code returned from the user

exit routine was other than 0, 4, 12, or 16.
return code is 8.
set, if necessary. Correct the user exit routine so that a
valid return code is returned and resubmit the job.
Support Center. Have program listing of the associated
user exit routine available.
Source: DFSMSdfp
IEB710I
UNABLE TO GET ENOUGH SPACE TO

PROCESS REMAINING CONTROL
CARDS
Explanation: A GETMAIN operation was unable to get

sufficient space to process the remaining control
statements.
return code is 8.
set, if necessary. If a REGION parameter was specified,
ensure that the specified value is sufficient to complete
the necessary processing and resubmit the job.
Source: DFSMSdfp
IEB711I
KEYWORD VALUE NOT FOLLOWED

BY A BLANK OR COMMA
Explanation: The keyword value pinpointed by

message IEB727I is not followed by a blank or a
comma.
return code is 8.
754

the problem.
Source: DFSMSdfp
IEB712I
CONTROL CARD NAME OR KEYWORD

VALUE EXCEEDS 8 CHARACTERS
Explanation: The length of a keyword value or control

statement name is greater than 8 characters.
return code is 8.
the problem.
Source: DFSMSdfp
IEB713I
FLAGGED KEYWORD IS NOT

COMPATIBLE WITH A PRECEDING
KEYWORD
Explanation: The keyword pinpointed by message

IEB727I is not compatible with another keyword already
specified on the same statement. (For example, the
keywords PICTURE and FORMAT cannot be used
together.)
return code is 8.
the problem.
Source: DFSMSdfp
IEB714I
REPEAT CARD ERROR OR REQUIRED

NUMBER OF CREATE CARDS NOT
PRESENT
Explanation: One of the following error conditions

occurred:
v Two or more REPEAT statements refer either to the
same CREATE statement or to the same group of
CREATE statements.
v A CREATE keyword in a REPEAT statement specifies
a number greater than the number of following
CREATE statements.
return code is 8.
the problem.
Source: DFSMSdfp
IEB715I
NAME AND/OR LENGTH OR QUANTITY

SPECIFICATION(S) OMITTED FROM FD
AND/OR REPEAT CARD
Explanation: One or more of the field name, length,

and quantity specifications is missing from an FD and/or
REPEAT statement.
return code is 8.
the problem.
IEB716I
PICTURE STRING OR FD FIELD

OVERFLOWS OUTPUT RECORD OR
INPUT FIELD SELECTED OVERRUNS
INPUT WORKAREA
Explanation: During construction of an output record

by a CREATE statement, a specified picture string or
FD field extended past the end of the defined record.
return code is 8.
set. Make sure that the DCB parameters are correct.
Compare the LRECL parameter value with the length of
the defined record, and make sure the value is specified
correctly. Resubmit the job.
the problem.
Source: DFSMSdfp
IEB717I
INPUT RECORD SIZE EXCEEDS

SPECIFIED OUTPUT RECORD SIZE
Explanation: The record length specified in a DD

statement for an output data set is not sufficient to
contain corresponding input records.
return code is 8.
the problem.
Source: DFSMSdfp
Source: DFSMSdfp
755
IEB718I
DSD CONTROL CARD MUST BE FIRST

CARD OF SET
Explanation: The DSD control statement is either out

of order or missing.
return code is 8.
error. Insert the missing DSD statement, or correct the
sequence of control statements.

return code is 8.
the problem.

the problem.
Source: DFSMSdfp
Source: DFSMSdfp

return code is 8.
IEB720I
BLANK DOES NOT FOLLOW

OPERATION OR CONTROL CARD
NAME
Explanation: The control statement name or operation

is not followed by a blank.
return code is 8.
the problem.
Source: DFSMSdfp
IEB721I
KEYWORD, KEYWORD VALUE OR

DELIMITER IS MISSING OR EXTENDS
INTO COLUMN 72
Explanation: A required keyword, keyword value, or

delimiter is missing or is specified in column 72.
756
IEB723I
PICTURE PARAMETER IS NOT

FOLLOWED BY A BLANK OR COMMA
Explanation: The picture length subparameter or the

picture value field is not followed by a blank or comma.

the problem.
Source: DFSMSdfp
IEB724I
UNABLE TO OPEN DATA SET. LOOK

FOR CONFLICTING VALUES OR
MISSING DD CARD
Explanation: An input or output data set referred to by

a DSD statement could not be opened. Possibly, the DD
statement is missing or the BLKSIZE, LRECL, or
RECFM subparameters is incorrect.
System Action: No syntax checking or data
generation is performed for this set of utility control
statements. Processing continues normally with the next
DSD statement encountered. The return code is 8.

the problem.
Source: DFSMSdfp
IEB725I
A DUPLICATE DSD CARD HAS BEEN

FOUND. CHECK FOR MISSING END
CARD.
Explanation: An END statement is either out of order

or missing.
return code is 8.
the problem.
Source: DFSMSdfp
IEB726I
EXEC STATEMENT PARM PARAMETER

IS CODED INCORRECTLY
Explanation: The PARM parameter of the EXEC

statement contains an incorrect character, or does not
contain a 4-digit decimal number.
System Action: The line count of the message data
set is set to a default value of 58. The return code is 0.
error. If the default value assumed is unacceptable,
correct the LINECNT subparameter on the EXEC
statement.
the problem.
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
message.
Application Programmer Response: Respond as
indicated in the error message that follows this
message.
Source: DFSMSdfp
IEB728I
INPUT STREAM FLUSHED FROM THIS

POINT. LRECL, BLKSIZE, OR RECFM
INCORRECT IN INPUT OR OUTPUT
DCB
Explanation: An input or output data set could not be

opened. Probably, the LRECL, BLKSIZE, or RECFM
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
statements. Processing continues normally with the next
DSD statement encountered. The return code is 8.
the problem.
Source: DFSMSdfp
IEB729I
PERMANENT I/O ERROR, jjj, sss, ddd,

devtyp, ddname, op, err, xxxx, acc

jjj
Job name.
sss
Step name.
ddd
Source: DFSMSdfp
devtyp
Device type.
IEB727I
ddname
ERROR
Explanation: This message immediately follows an

error message and pinpoints the location of syntax
errors, incompatible keywords, and other control
statement coding errors. In most cases, the E of
ERROR falls directly below the point at which the error
757
xxxx
sss
acc
Step name.
ddd
Access method.

code is 12.
devtyp
Device type.

error condition as indicated in the message text.
ddname

the problem.
Source: DFSMSdfp
IEB801I
{OM|NM} LRECL AND BLOCKSIZE

ASSUMED 80/80
Explanation: Necessary DCB parameters were

omitted from the SYSUT1 (indicated by OM or old
master) or SYSUT2 (indicated by NM or new master)
DD statement. The program assumes that the SYSUT1
or SYSUT2 data set, as applicable, contains 80-byte
unblocked records.
System Action: Processing continues. However, if the
data set does not contain 80-byte unblocked records,
additional messages will be generated during
processing, and the job step will be ended. The return
code is 0.
Application Programmer Response: If the record
format specifications assumed are correct, there is no
response required. Otherwise, correct the applicable
parameters.
System Programmer Response: Use IEHLIST to list
the VTOCs of the volumes on which the old master and
new master data sets reside. If the error recurs and the
the IBM Support Center. Provide the JCL and all printed
Source: DFSMSdfp
IEB802I

op, err, xxxx, acc

xxxx
Track address or relative block number.
acc
Access method.
code is 12.
error condition indicated in the message text.
the problem.
Source: DFSMSdfp
IEB803I
PERMANENT INPUT ERROR - FIND

MACRO
Explanation: A permanent input error was detected by

the FIND macro instruction while attempting to search a
partitioned data set directory.
code is 12.
Application Programmer Response: Check the DD
statement describing the SYSUT1 data set for missing
or incorrect parameters.
the problem.

Source: DFSMSdfp

instruction issued in the SYNAD routine was:
IEB804I
jjj
Job name.
758
PERMANENT INPUT ERROR - BLDL

MACRO

detected by the BLDL macro when attempting to search
a partitioned data set directory.

code is 12.
Application Programmer Response: Check the DD
statement describing the SYSUT1 data set for missing
or incorrect parameters.
the problem.
IEB807I
INVALID OPERATION

is inconsistent with previously specified parameters.
Possibly:
v A DELETE statement is encountered during an
UPDATE=INPLACE operation.
v A CHANGE statement is encountered, but
PARM=NEW was specified on the EXEC statement.
v Data statements are out of sequence. Old master
records are out of sequence and renumbering was
not requested.
Source: DFSMSdfp
v A NUMBER statement with a SEQ1 parameter is

encountered following an ADD statement.
IEB805I
v More than 16 alias statements have been found for

the member scheduled to be updated.
CONTROL STATEMENT ERROR
Explanation: In the utility control statement preceding

this message, a name, keyword, or parameter is
incorrect.
System Action: If the data set is partitioned, the
program continues processing with the next function
statement. If the data set is not partitioned, the program
is ended. The return code is 4.
the problem.
Source: DFSMSdfp
IEB806I
STATEMENT SEQUENCE ERROR
Explanation: Either the utility control statements are

out of sequence, or an unnecessary statement has
been encountered.
the problem.

the problem.
Source: DFSMSdfp
IEB808I
TERMINATED THIS MEMBER.

IEBUPDTE WILL TRY NEXT MEMBER
Explanation: A control statement error, a statement

sequence error, or an incorrect operation has ended an
update operation.
function statement. The return code is 0.
control statement error.
the problem.
Source: DFSMSdfp
Source: DFSMSdfp
759
IEB810I
DELETE RANGE INVALID
IEB813I
OUTPUT DIRECTORY FULL
Explanation: In the DELETE statement preceding this

message, the SEQ1 or SEQ2 value specified does not
match a sequence number in an existing logical record.
Explanation: Insufficient space was allocated for

directory entries in the SYSUT2 data set. Therefore, the
member was not placed in the data set.

function statement. The return code is 4.

code is 12.


SYSUT2 data set, allocating sufficient space for the
additional directory entries. Then resubmit IEBUPDTE to
include the members that were omitted.

the problem.
Source: DFSMSdfp

Source: DFSMSdfp
IEB811I
NUMBER RANGE INVALID
Explanation: In the NUMBER statement preceding

this message, the SEQ1 value does not match a
sequence number in an existing logical record.
function to be performed. The return code is 4.
the problem.
Source: DFSMSdfp
IEB812I
DIRECTORY WRITE ERROR

while writing the directory of the SYSUT2 data set.
code is 12.
sufficient space is allocated for the directory on the
SYSUT2 DD statement.
Source: DFSMSdfp
IEB814I

OPENED
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
multiple of, 80.
ddname
Identifies the DD statement.
code is 12.
Source: DFSMSdfp
IEB815I
CANNOT PROCESS MORE THAN ONE

PS DATA SET PER PASS
Explanation: A control statement specified the

processing of two input sequential data sets in the same
job step.
code is 12.
error. Ensure that there is no disagreement between the
JCL and the user control statements. Resubmit the job.
760

Source: DFSMSdfp
System Action: The program is ended normally.

Source: DFSMSdfp
IEB819I
END OF JOB IEBUPDTE
Explanation: IEBUPDTE has completed processing.

IEB816I
{MEMBER NAME mem

FOUND|MEMBER NAME mem FOUND
IN NM DIRECTORY. TTR IS NOW
ALTERED}
System Action: The program is ended normally.

Source: DFSMSdfp
Explanation: For the first format of the message, the

member name specified on an ADD statement already
exists.
IEB820I
For the second format of the message, the member

name exists in the new master (NM) directory.
Explanation: If a function statement specifies

UPDATE=INPLACE, it must be the only function
statement in the job step.
mem
The member name.
CANNOT PROCESS MORE THAN ONE

FUNCTION STATEMENT WHEN
UPDATE=INPLACE IS SPECIFIED

code is 12.
System Action: For the first format of the message,

the program is ended. The return code is 12.

For the second format of the message, an entry (TTR)

is altered and processing continues. The return code is
0.

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
IEB817I
MEMBER NAME mem NOT FOUND IN

NM DIRECTORY. STOWED WITH TTR
Explanation: The member name does not exist in the

directory of the new master (NM) data set.
mem
The member name.
System Action: An entry (TTR) is made for the

member in the directory. Processing continues. The
return code is 0.
Source: DFSMSdfp
IEB818I
HIGHEST CONDITION CODE WAS ccc
Explanation: The condition code indicated was the

highest code generated in the job step.
ccc
The condition code.
Source: DFSMSdfp
IEB821I
INVALID EXIT NAME. JOB ENDED
Explanation: The name of a user exit routine specified

on a function statement is incorrect.
code is 12.
and the program listing for the job. Have the exit routine
listings and linkage editor output available.
Source: DFSMSdfp
IEB822I
EXIT RETURN CODE ENDED JOB

was 16.
code is 16.
Application Programmer Response: If a return code
of 16 was not expected, check your exit routine, and
resubmit the job.
761

listings available.
Source: DFSMSdfp
IEB823I
{SYSUT1|SYSIN} HAS NO RECORDS
Explanation: The SYSUT1 or SYSIN data set, as

indicated in the message text, contains no records.
System Action: For the SYSUT1 data set, processing
continues with the next member, if any. The return code
is 4.
For the SYSIN data set, the program is ended. The
return code is 12.
The system issues messages about the job to the job
log.
Application Programmer Response: Insert data
statements for the SYSIN data set, or ensure that the
proper SYSUT1 data set is specified.
If the problem recurs and if the program is not in error,
Center. Provide the JCL for the job and the program
listing for the job.
Source: DFSMSdfp
IEB825I
ALIAS IGNORED - SEQUENTIAL DATA

SET
Explanation: An ALIAS statement specified an alias

name for an output sequential data set.
System Action: The statement is ignored. The return
code is 4.
error. Delete the ALIAS statement.
Source: DFSMSdfp
IEB826I
MEMBER NAME FOUND IN OM

DIRECTORY AS AN ALIAS - CHANGED
TO TRUE NAME IN NM DIRECTORY
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.
762

code is 0.
Source: DFSMSdfp
IEB827I
INVALID INPUT PARAMETER
Explanation: Either the EXEC statement contains an

incorrect PARM parameter, or an incorrect parameter
was passed to IEBUPDTE.
code is 12.
Source: DFSMSdfp
IEB828I
PAGE NUMBER PARAMETER INVALID
Explanation: An incorrect starting page number for

the message data set was passed to IEBUPDTE.
System Action: A page number of 1 is assigned to
the first page of the printout. The return code is 4.
error. If the default of 1 is not acceptable, correct the
starting page number.
Source: DFSMSdfp
IEB829I
DDNAME PARAMETER IS INVALID
Explanation: An incorrect DDNAME parameter was

passed to IEBUPDTE.
code is 12.
Source: DFSMSdfp
IEB830I
OLD AND NEW MASTER LRECL

UNEQUAL
Explanation: The logical record lengths of the old and

new master data sets are unequal.
code is 12.
error. Correct the LRECL subparameter of the DCB
parameter on the SYSUT2 DD statement.
routine The routine specified.

code is 0.
Source: DFSMSdfp
xx ENTRANCES TO routine
IEB833I
Explanation: The number of entrances to user routine

is indicated.
xx
The number of entrances to the user routine.
routine The user routine.

code is 0.
Source: DFSMSdfp
Source: DFSMSdfp
IEB831I
IEB834I
OLD AND NEW MASTER DSORGS

INCOMPATIBLE
Explanation: The data set organizations implied or

specified on the SYSUT1 and/or SYSUT2 DD
statements are either:
v Inconsistent with one another.
v Inconsistent with the data set organizations implied or
specified on the utility control statements.
LAST RETURN CODE FROM routine

WAS return-code
Explanation: The return code indicated was the last

return code issued by the user routine.
return-code
The return code.
routine
The user routine.

code is 12.

code is 0.

error. In the first case, ensure that the space allocation
specified on the SYSUT1 and/or SYSUT2 DD
statements is consistent with the data set organization.
Also, ensure that the DSORG subparameter, if included,
is correct.
Source: DFSMSdfp
In the second case, ensure that the keywords specified

on the utility control statements are consistent with the
data set organizations specified or implied on the
SYSUT1 and/or SYSUT2 DD statements.
Source: DFSMSdfp
IEB832I
routine IS PROCESSING USER

{INPUT|HEADER|OUTPUT|TRAILER}
LABELS
IEB835I
{TOTALING|USER LABELS}
SUPPORTED ONLY ON PS DATA SETS
Explanation: The user requested totaling exits or user

label processing, as indicated in the message text, for a
data set whose organization is not physical sequential.
These functions are supported only for physical
sequential data sets.
code is 8.
Source: DFSMSdfp
Explanation: The user routine is currently processing

input or output, header or trailer labels, as indicated in
the message text.
763
IEB836I
TRAILER LABEL PROCESSING NOT

SUPPORTED FOR UPDATE=INPLACE
Explanation: The user specified user trailer label exits

with an UPDATE=INPLACE operation. User trailer label
exits are not supported for UPDATE=INPLACE
operations.
routine The user totaling routine.

System Action: If the return code passed to
IEBUPDTE was 0, totaling exits are discontinued, but
If the return code was 8, the program is ended. The
return code is 12.

code is 8.
If the return code was 16, the program is ended. The

return code is 16.

Application Programmer Response: If ending the

totaling exit routine was not expected, check the exit
routine, and resubmit the job.

Source: DFSMSdfp
IEB837I
I/O ERROR WHILE PROCESSING USER

LABEL

occurred during user label processing. The results of
the label processing are unpredictable.
code is 12.
Application Programmer Response: Ensure that no
DCB parameters for the data set are incorrect or
missing.
Source: DFSMSdfp
IEB839I
routine IS TAKING TOTALING EXITS
Explanation: The user routine is taking totaling exits

prior to writing each record.

listing available.
Source: DFSMSdfp
IEB841I
INVALID RETURN CODE FROM routine,

TOTALING EXITS DISCONTINUED
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.
routine The user totaling routine.

System Action: Totaling exits are discontinued, but
error. Check the user routine to make sure that a valid
return code was passed to the utility program. Resubmit
the job.
listings available.
Source: DFSMSdfp
routine The user routine.

code is 0.
IEB842I
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
Explanation: A return code other than 4 was passed

to IEBUPDTE by the user totaling routine.
764
TOTALING EXITS NOT SUPPORTED

FOR UPDATE=INPLACE

code is 12.

and the program listing for the job. Have the associated
input data set available.
Source: DFSMSdfp
IEB846I
ALIAS IGNORED FOR

UPDATE=INPLACE
Source: DFSMSdfp
IEB843I
INVALID CORE SIZE
Explanation: The virtual storage specified in the

TOTAL keyword either is a non-numeric character, is
less than 2 bytes, or is greater than 32K bytes.
code is 12.
Source: DFSMSdfp
IEB844I
NO USER {HEADER|TRAILER} LABELS

EXISTS ON INPUT DATA SET
Explanation: The user specified SUL on the DD

statement for the input data set, but there are no header
or trailer labels, as indicated in the message text, on the
data set.
Explanation: ALIAS statements for partitioned data

set members cannot be processed using the
UPDATE=INPLACE operation.
System Action: All ALIAS statements are ignored.
Processing continues. The return code is 0.
Source: DFSMSdfp
IEB1010I
Explanation: An ALTERMOD or COMPRESS

operation is requested for a PDSE, or a COPYMOD
operation is requested for a PDSE.
Message inserts and meanings:
function
is one of:
COPYMOD
ALTERMOD
COMPRESS

code is 0.
Source: DFSMSdfp
IEB845I
NO USER {HEADER|TRAILER} LABELS

CREATED ON OUTPUT DATA SET
Explanation: The user specified SUL on the SYSUT2

DD statement, but no header or trailer labels, as
indicated in the message text, were copied from the
SYSUT1 data set, and no labels were generated by a
LABEL statement.
code is 0.
Application Programmer Response: If user labels
are desired on the output data set, make sure that the
SYSUT1 data set contains user labels, or supply user
labels with the LABEL statement. Resubmit the job.
function FUNCTION REQUESTED FOR

A PDSE. Action
Action
is one of:
IT IS IGNORED.
REQUEST TREATED AS COPY.
The severity is 0.
System Action: An ALTERMOD or COMPRESS
operation is ignored. A COPYMOD operation is treated
as a COPY request.
User Response: Remove the compress or
ALTERMOD operation to eliminate this message, or
change COPYMOD to COPY since the PDSE can not
contain a load module.
Source: DFSMSdfp
IEB1010S
function FUNCTION REQUESTED FOR

A PDSE. NO PDSE SUPPORT IN THIS
RELEASE.
Explanation: A PDSE has been encountered on a

system before DFP V3 R2. This is probably because
the DASD containing the PDSE is shared with a system
765
running a DFP or DFSMS release that does support

PDSEs.
function
is one of:
COPY
COPYMOD
ALTERMOD
COMPRESS
LOAD
UNLOAD
The severity is 12.
size
amount of storage available in the work area

when the PDSE operation started.
The severity is 8.
System Action: Processing is incomplete.
User Response: 1. Refer to preceding IGW messages
to learn what processing was completed. 2. Increase
the size of the work area, or decrease the number of
members involved in the operation, or specify LIST=NO
to reduce the message traffic.
The user response for message IEB1057I discusses
increasing the WORK area size.
System Action: Any operation involving a PDSE on a

system without PDSE support is ended.
Source: DFSMSdfp
User Response: Re-run the job on the system with

PDSE support available.
IEB1013I
Source: DFSMSdfp
IEB1011E
AVAILABLE STORAGE (avail) IS TOO

SMALL. ADD nnnnn MORE BYTES TO
WORK SIZE.
COPYING FROM dtype INDD=ddname

VOL=volume DSN=dsname
Explanation: This message documents the copy

source data set.
dtype
type of data set:
Explanation: A list of members to be copied to or from

a PDSE was being built when all available virtual
storage in the work area was exhausted.
PDSE
a library (DSNTYP=LIBRARY)
PDS
a partitioned (DSORG=PO)
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.
nnnnn
number of additional bytes required.
The severity is 8.
System Action: The requested COPY operation is not
performed.
ddname
input DD name from the COPY statement.
volume volume containing the data set.

dsname
data set name.
The severity is 0.
User Response: Increase the work area size, or

reduce the number of members involved in the
operation.

IEB1014I
Source: DFSMSdfp
IEB1012E
COPY OPERATION NEEDS nnnnn

BYTES MORE STORAGE. OUTPUT
AREA IS size BYTES.
Source: DFSMSdfp
TO dtype OUTDD=ddname VOL=volume
DSN=dsname
Explanation: This message documents the destination

data set.
dtype
type of data set:
Explanation: The amount of storage available to

communicate with the PDSE routines is too small.
PDSE
PDS
This area is used to return member lists, and

messages.
PDSU

nnnnn
766
amount of the virtual storage shortage.
ddname
output ddname from the COPY statement.
v return-code > 8 is severity 8, message IEB1017E.
dsname
System Action: The next operation is sought.

data set name.
The severity is 0.
Source: DFSMSdfp
IEB1016I
RETURN CODE IS return-code
User Response: This probably represents an unusual

condition or problem. Refer to accompanying messages,
particularly those with IGW and IEB prefixes, for specific
information and additional guidance.
System Programmer Response: Research
accompanying messages in SYSPRINT and in the job
log for more specific information.
Explanation: This message records information about

the results of a copy operation involving a PDSE.

Center.
The value of return-code is not a IEBCOPY step

completion code; it is a return code from an internal
routine. The IEBCOPY completion code is affected by
this return-code as documented in message IEB1017.
Please furnish the information in this message when

requesting service along with the JCL, job log, system
messages, and all SYSPRINT output.
The severity is 0.
Please preserve the input and output data sets related

to the problem in case it should be necessary to
reproduce the problem.
System Action: Message IEB1017 follows.

User Response: This may represent either a normal
condition or a problem. Refer to accompanying
messages for additional guidance.
Source: DFSMSdfp
IEB1018I
Source: DFSMSdfp
IEB1017I -- DIAGNOSTIC CODE IS X'diagcode'
COMPRESSING PDS OUTDD=ddname

Explanation: This message documents the data set

being compressed.
IEB1017W -- DIAGNOSTIC CODE IS X'diagcode'
ddname
output DD name from the COPY statement.
IEB1017E
-- DIAGNOSTIC CODE IS X'diagcode'
Explanation: This message accompanies messages

IEB1016I or IEB1137I. Report this diagnostic code to
the IBM support center when requesting service.
Note: The historical step completion codes from
IEBCOPY cause normal attention conditions to
be reported as completion code 0. Generally
speaking, completion code 4 means that a copy
operation has failed, and completion code 8
means that execution can not continue under
any circumstances.
In order to reconcile the existing completion codes in
IEBCOPY with the modern standards, the return codes
from new function related to PDSEs are reduced by 4 to
create the IEBCOPY completion code.
diagcode
an internal DFP diagnostic code.

dsname
data set name.
The severity is 0.
System Action: Processing Continues.
Source: DFSMSdfp
IEB1019I
SKIPPING COMPRESS OF PDSE

OUTDD=ddname VOL=volume
DSN=dsname
Explanation: A request to compress a PDSE was

suppressed, as a PDSE never needs compressing.
ddname
DD name.

dsname
The severity is based on the return code in message

IEB1016I:
data set name.
v return-code < 8 is severity 0, message IEB1017I.
The severity is 0.
v return-code = 8 is severity 4, message IEB1017W.

767
User Response: Consider removing the compress

request from the job.
ddname
Source: DFSMSdfp
volume volume containing the data set or blank for

VIO.
IEB1020I
UPDATING PDS OUTDD=ddname

Explanation: This documents the data set being

processed by an in-place operation such as
ALTERMOD.
ddname
output DD name for the data set.
DD name identifying the data set.
dsname
name of the data set.
The severity is 0.
System Action: An indicative dump may be printed
next on SYSPRINT. Message IEB1023I will follow the
dump (if any).
Source: DFSMSdfp
IEB1023I
dsname
data set name.
Explanation: This messages follows IEB1022E to

document the current activity at the time of the I/O error.
The severity is 0.
Source: DFSMSdfp
IEB1021E
activity MEMBER=member TTR= X'ttr'

MBBCCHHR=mbbcchhr TAPE
BLOCK=bbbbb
synad_text LEN=length SENSE=

iobsens0-iobecbcc
Explanation: This message, with following message

IEB1023I, contains text generated by the SYNADAF
function during I/O error processing.
This message identifies the location of the I/O error first

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
contains zero, it is not valid. If both the TTR and
MBBCCHHR are not zero then both should identify the
same record in the data set.
TTR= and MBBCCHHR= are valid only if the data set

resides on direct access storage. TAPE BLOCK= is
valid only if the data set resides on tape.
synad_text
text generated by the SYNADAF

macro.
length
amount of data read or 0.
iobsens0
first 2 sense bytes.
iobecbcc
ECB post code.
The severity is 8.
System Action: Message IEB1022I and IEB1023I
follow.
Source: DFSMSdfp
IEB1022I
I/O ERROR ON dtype DDN=ddname

VOL= volume DSN=dsname
Explanation: This messages follows IEB1021E to

document the data set involved in the I/O error.
dtype
768
type of data set:
activity is one of:

COPYMOD READ
COPYMOD WRITE
READING UNLOADED PDSE
WRITING UNLOADED PDSE
GET FROM CONTROL STMT FILE
PUT TO MESSAGE FILE
DURING READ
DURING WRITE
DURING ERASE
DURING READBACK CHECK
DURING LOAD
DURING UNLOAD
UNEXPECTED END OF FILE
READING OUTPUT DIRECTORY
PROCESSING HEADER RECORDS
SCANNING DIRECTORY
INPUT DIRECTORY MERGE
OUTPUT DIRECTORY MERGE
LOCATING MEMBER
member
PDSE
PDS
ttr
PDSU

mbbcchhr
DASD address of record.
name of the PDS or PDSE member.

3-byte hexadecimal relative disk address.
bbbbb
block number used for tape positioning.
The severity is 0.
System Action: Error processing continues.
User Response: Refer to message IEB1021.
System Programmer Response: Refer to message
IEB1021.
Source: DFSMSdfp
IEB1024E
SYNTAX ERROR IN PARM FIELD

OPTIONS
Explanation: There is an error in one of the following:

v The parameter passed via the PARM= field on the
EXEC JCL statement
v The program parameter field in the TSO CALL
command
v The first parameter in the parameter list passed by a
program dynamically invoking IEBCOPY.
The severity is 8.
System Action: Processing continues, ignoring
options which could not be understood because of the
syntax error.
System Action: Processing continues. If the page

number is missing in the supplied parameter, the
beginning page number will be 1. If the page number in
the supplied parameter is too long, the beginning page
number will be some left portion of that number. If the
supplied parameter is not an EBCDIC number, the
beginning page number will be an unpredictable
numerical value.
User Response: Correct the program invoking
IEBCOPY to properly construct and pass the third
parameter. Refer to the OS/390 DFSMSdfp Utilities
Appendix A for information about dynamic invocation of
IEBCOPY and parameters.
Source: DFSMSdfp
IEB1027E
IO LIST PARAMETER IS NOT

SUPPORTED AND IS IGNORED.
Explanation: A program invoked IEBCOPY, supplying

a fourth parameter which is not used by IEBCOPY.
Some IBM Utility programs support user IO routines
which are passed in a list as the fourth parameter.
Since IEBCOPY does not support user IO routines, it
does not expect more than three passed parameters.
The severity is 8.
User Response: Correct the options.
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
to the OS/390 DFSMSdfp Utilities Appendix A for
information about dynamic invocation of IEBCOPY and
parameters.
IEB1025I
DD NAME LIST PARAMETER IS IN

ERROR AND MIGHT BE IGNORED.

a list of DD names to be substituted for those normally
used by IEBCOPY. However, some or all of the supplied
names could not be recognized.
Source: DFSMSdfp
The severity is 8.
IEB1028I OPERATING IN KEY 0 SUPERVISOR

STATE
System Action: Processing continues. The names

that can be correctly identified as substitutes are used;
the others are ignored.
IEB1028T
User Response: Correct the program invoking

IEBCOPY to properly construct and pass the second
parameter. Refer to the OS/390 DFSMSdfp Utilities
Appendix A for information about dynamic invocation of
IEBCOPY and parameters.
Source: DFSMSdfp
IEB1026I
PAGE NUMBER PARAMETER IS IN

ERROR AND MIGHT BE IGNORED

a beginning page number for the IEBCOPY messages
and control cards listing. The page number is either
missing, too long, or contains characters which are not
EBCDIC numbers.
The severity is 8.
OPERATING IN KEY 0 SUPERVISOR

STATE
Explanation: IEBCOPY has detected that it was called

in supervisor state and protection key zero.
The interface to some services changes when the
invoker is in supervisor state/key 0 and IEBCOPY is not
coded to use these different interfaces.
IEBCOPY must be invoked in problem state and
non-zero protect key.
The severity is 0.
System Action: IEBCOPY ends.
Application Programmer Response: Invoke
IEBCOPY as an application program.
System Programmer Response: Check the program
properties table for programs such as SMP/E that
invoke IEBCOPY under the covers.
769
Source: DFSMSdfp
IEB1029I
INVOKED AS A TSO COMMAND

PROCESSOR
Explanation: IEBCOPY has been entered from TSO

as a command processor. This message is issued
because IEBCOPY was not written to be a TSO
command processor but may function when so invoked
while not providing all the services of a command
processor (e.g. prompting for missing/incorrect
parameters, providing HELP information).
IEB1031E
Explanation: The data set is not present on the

indicated volume. Note that the volume information may
come from a catalog or from JCL, and that for SMS
data sets, volume information in the JCL may be
ignored.
volume volume serial number.

ddname
The severity is 0.
DD name.

User Response: Use the TSO CALL command to
invoke IEBCOPY. Do not enter IEBCOPY as a TSO
command or CLIST statement.
Source: DFSMSdfp
IEB1030I
DD NAME ddname REFERS TO dtype

DATA SET ON VOLUME volume NAMED
dsname
Explanation: This message accompanies message

IEB120I which occurs when a data set can not be
opened. This message may appear multiple times for
each DD name involved in the operation.
This message is to document data set names and
volumes when the copy operation fails before messages
IEB1013I etc. are issued.
ddname
dtype
VOLUME volume DD NAME ddname

DOES NOT CONTAIN DATA SET
dsname
dsname
data set name.
The severity is 4.
System Action: For an output data set, the COPY
group is ended. For an input data set, processing
continues with the next data set in the INDD group.
User Response: Correct the catalog, add VOL=SER=
to the DD statement, or create the data set on the
volume.
System Programmer Response: The IDCAMS utility
may be used to display the volume on which a
cataloged data set is supposed to reside. The IEHLIST
utility may be used to display the names of data sets
which reside on a specific volume.
Source: DFSMSdfp
type of data set:

PDSE
PDS
PDSU

volume volume containing the data set or blank for

VIO.
IEB1032E
RECORD FORMAT OMITTED FOR DD

NAME ddname
Explanation: No information about the RECFM for the

data set identified by the ddname DD statement can be
found.
ddname
name of the DD statement.
dsname
name of the data set.
The severity is 4.
The severity is 0.
User Response: Correct the error indicated by
previous message IEB120I.
Source: DFSMSdfp

User Response: Verify that the input data set contains
data (i.e. has been opened for output previously and
successfully closed). The IEHLIST utility may be used to
display the data set characteristics from the data set
label.
Source: DFSMSdfp
770
IEB1033E
BLOCK SIZE (blksize) INCONSISTENT

WITH RECORD LENGTH (reclen) FOR
RECFM=recfm
Explanation: An incorrect combination of block size

and logical records length has been detected.
blksize physical record size (JCL DD statement

BLKSIZE parameter).
reclen
logical record size (JCL DD statement LRECL

parameter).
recfm
record format, as used with the JCL DD

statement RECFM parameter.
A summary of the rules follows, based on RECFM:

F
LRECL must equal BLKSIZE.
FB
LRECL multiplied by an integer must equal

BLKSIZE.
FBS
LRECL multiplied by an integer must equal

BLKSIZE.
BLKSIZE must exceed LRECL by a minimum

of 4.
VB
BLKSIZE must exceed LRECL by a minimum

of 4.
VS
LRECL may exceed BLKSIZE.
VBS
LRECL may exceed BLKSIZE.
When track overflow is not used (RECFM does not

contain a T) then the BLKSIZE must not exceed the
track size of a DASD device.
The severity is 4.
User Response: Correct or supply DCB parameters.
(Variable length records can be copied from an input

data set with equal or shorter length records than the
output data set.)
in_ddname
input data set DD statement name.
in_length
logical record size of the input data set.
out_ddname
output data set DD statement name.
out_length
logical record size of the output data set.
The severity is 4.
System Action: For an output data set, the COPY
group is ended. For an input data set, processing
continues with the next data set in the INDD group.
User Response: Correct or supply DCB parameters.
utility to print the data set label and compare the DCB
parameter fields with the JCL. If the data set is an
output data set, also examine the DCB parameters from
the current input data set.
Refer to OS/390 DFSMS: Using Data Sets for a
discussion of how all the sources are merged to
determine the DCB parameters used.
Source: DFSMSdfp
IEB1035I
job_name procstep step_name local_time

PARM=parameters eye_catcher
Explanation: This message documents the job and

step producing the IEBCOPY printed report, the local
time IEBCOPY processed, and the parameters passed
to IEBCOPY from the JCL EXEC statement PARM field.
Also included is the current maintenance level of the
program.

utility to print the data set label and compare the DCB
parameter fields with the JCL. If the data set is an
output data set, also examine the DCB parameters from
the current input data set.
See OS/390 DFSMS: Using Data Sets for a discussion

of how all the sources are merged to determine the
effective DCB parameters.
procstep
Source: DFSMSdfp
IEB1034E
RECORD LENGTHS UNEQUAL

BETWEEN INDD in_ddname (in_length)
AND OUTDD out_ddname (out_length)
Explanation: IEBCOPY can not pad or truncate logical

records when reblocking. When fixed length logical
records are copied they must be the same size.
job_name
JCL Job Name or Time Sharing Option (TSO)
User-ID.
if present, the JCL procedure name.
step_name
JCL EXEC Step Name.
local_time
local (as opposed to universal or GMT) date
and time.
parameters
parameters supplied when IEBCOPY was
invoked.
771
eye_catcher
latest APAR or PTF applied to IEBCOPY.
IEB1038I
The severity is 0.
Source: DFSMSdfp
IEB1036E
TRACK OVERFLOW NOT SUPPORTED

FOR DD NAME ddname
Explanation: The DASD device associated with DD

name ddname does not support the Track Overflow
feature, or the data set associated with DD name
ddname is not a PDS.
ORIGINAL dtype (BEFORE UNLOAD)

WAS RECFM= urecfm BLKSIZE=ublksize
LRECL= ulrecl KEYLEN=ukeylen
OPTCD= uoptcd UCBTYPE=udevtype
INDC= indc
Explanation: The unload data set contains header

records that record the characteristics of the source
PDS or PDSE which was unloaded to create the data
set being processed as input. This message informs
you what they are.
dtype
type of data set:
PDSE
ddname
PDS
PDSU


The severity is 4.
System Action: The operation is not preformed and
the next control statement is sought.
urecfm record format.

ublksize
block size.
User Response: Remove the RECFM=T from your

JCL to stop requesting the track overflow feature.
ulrecl
Source: DFSMSdfp
ukeylen
logical record length.

key length.
IEB1037I
BLOCK SIZE IN THE DATA SET LABEL

OF ddname INCREASED TO newsize
FROM oldsize
Explanation: A COPYMOD operation has been

requested to reblock a load module. The MAXBLK
parameter supplied on the COPYMOD statement (or the
default when MAXBLK is not supplied) limits the largest
physical record size that COPYMOD will write. This
number is greater than the current block size in the
output data set label.
ddname
output data set DD statement name.
uoptcd option codes.

udevtype
device type from UCB.
indc
indicator byte.
The severity is 0.
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
has details about the header records content.
Source: DFSMSdfp
newsize
new block size placed in the data set label.
oldsize old block size before the COPYMOD operation.

The severity is 0.
System Action: IEBCOPY updates the data set label
to contain a correct block size.
User Response: If the new block size is not
acceptable, then provide a MAXBLK parameter on the
COPYMOD statement.
Source: DFSMSdfp
IEB1039W
PDSU HAS DIFFERENT BLOCK SIZE

NOW (current) THAN WHEN IT WAS
CREATED (original). AN I/O MAY
OCCUR WHILE READING IT.
Explanation: One of the following occurred while

IEBCOPY was reading an unload data set:
v The data set produced from an unload operation has
been reblocked. There is a documented restriction
that the data set produced from an unload operation
must not be changed. IEBCOPY may encounter an
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
772
the DCB parameters are omitted from the JCL then

IEBCOPY will see the BLKSIZE as zero and report it
as such in this message: IEBCOPY may still
encounter an I/O error while processing the tape in
this case.
Note that the block sizes refer to the unload data set
itself and not to the PDS or PDSE from which it was
created.
IEB1045D
diagnostic_text
Explanation: This message contains diagnostic

information for you to supply to IBM when requesting
service.
IEB1046D
diagnostic_text

service.
current current block size of the unload data set.

original block size IEBCOPY used to create the unload
data set.
The severity is 0.
IEB1047D
diagnostic_text

service.

User Response:
v Do not change a data set produced from an unload
operation.
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
label is omitted, ignored, or incorrect.
Source: DFSMSdfp
IEB1040D
diagnostic_text

service.
IEB1042D
diagnostic_text

service.
IEB1043D
diagnostic_text

service.
IEB1044D
diagnostic_text

service.
IEB1049D
diagnostic_text

service.
diagnostic_text

service.
IEB1041D
IEB1048D
IEB1051I
ut3_blocks in_ddname DIRECTORY

ENTRIES SPILLED TO spill_ddname -nnnnn BYTES MORE WORK MAY
IMPROVE PERFORMANCE
Explanation: Not enough virtual storage was available

for IEBCOPY to retain in storage the directory entries
for all members being copied. IEBCOPY wrote them to
SYSUT3 and read them back one by one as individual
processing required the individual entries.
Performance may improve if you can give IEBCOPY
enough virtual storage to hold all directory entries. Then
you will not need to supply a spill data set.
ut3_blocks
number of records written to the spill

data set.
in_ddname
input data set DD name.
spill_ddname
spill data set DD name. (normally

SYSUT3).
nnnnn
number of additional bytes needed to

hold all directory entries in storage.
diagnostic_text

service.
The severity is 0.
User Response: Make more virtual storage available
to IEBCOPY.
773

The OS/390 DFSMSdfp Utilities book contains
information about calculating the amounts of virtual
storage required to hold directories, and choosing
between a large region or spill files.
Source: DFSMSdfp
only message to inform you about what IEBCOPY was

doing at the time of failure.
in_ddname
input data set DD name.
spill_ddname
spill data set DD name. (normally SYSUT3).
The severity is 0.
IEB1052I
ut4_blocks out_ddname DIRECTORY

BLOCKS SPILLED TO spill_ddname -nnnnn BYTES MORE WORK MAY
IMPROVE PERFORMANCE
Explanation: Not enough virtual storage was available

to retain the whole merged output directory in memory.
The merged output directory was written to SYSUT4.
Performance may improve if you can give IEBCOPY
enough virtual storage to hold all directory entries. Then
you will not need to supply a spill data set.
System Action: IEBCOPY proceeds to open the spill

data set.
User Response: Look for message IEB1051I which
follows later after successful completion of the current
operation.
If message IEB120I or other data set related messages
follow this message then look for problems related to
the spill data set.
Source: DFSMSdfp
out_ddname DIRECTORY BLOCKS

SPILLING TO spill_ddname
ut4_blocks
number of records written to the spill data set.
IEB1054I
out_ddname
output data set DD name.
Explanation: The amount of unused virtual storage in

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.
spill_ddname
nnnnn
number of additional bytes needed to keep the

output directory in storage.
The severity is 0.
User Response: Make more virtual storage available
to IEBCOPY.
The OS/390 DFSMSdfp Utilities book contains
information about calculating the amounts of virtual
storage required to hold directories, and choosing
between a large region or spill files.
Source: DFSMSdfp
IEB1053I
in_ddname DIRECTORY ENTRIES

SPILLING TO spill_ddname
Explanation: The amount of unused virtual storage in

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
774
Should the spill data set not be present or be too small

or another problem arise then this message may be the
only message to inform you about what IEBCOPY was
doing at the time of failure.
out_ddname
output data set DD name.
spill_ddname
The severity is 0.
System Action: IEBCOPY proceeds to open the spill
data set.
User Response: Look for message IEB1052I which
follows later after successful completion of the current
operation.
If message IEB120I or other data set related messages
follow this message then look for problems related to
the spill data set.
Source: DFSMSdfp
IEB1055I
THE REMAINING AMOUNT OF WORK

AREA, avail BYTES, IS {TOO SMALL
TO ALLOCATE ANOTHER
BUFFER.|SURPLUS SPACE WHICH IS
NOT NEEDED.}
Explanation: After reading and saving the directory

entries for the members to be copied there is still a
small amount of work area available. The extra area will
go unused.
This is not an error condition. This message is to help
you better manage resources by telling you about idle
storage.
Normally the remaining work area is used for additional
buffer space. However, the small amount is not enough
for a whole buffer, so the buffer space is not expanded.
avail
amount of virtual storage unused in the work

area.
The severity is 0.
User Response: If the amount of storage used by
IEBCOPY must be reduced then the size of the work
area could be reduced by about avail. Or, the size of
the work area could be increased enough to hold
another buffer. The amount of additional storage
required would be the difference between the buffer size
in message IEB1058I and avail.
Source: DFSMSdfp
IEB1056I
RELEASED nnnnn ADDITIONAL BYTES.
Explanation: IEBCOPY released the indicated virtual

storage.
Small quantities of virtual storage are released at
various processing stages so the access methods and
other operating system services will not fail from lack of
virtual storage. At IEBCOPY end, all remaining virtual
storage (from the block initially acquired by IEBCOPY)
will be released.
IEB1057I
VL GETMAIN REQUESTED minimum TO

maximum BYTES. OBTAINED obtained.
RELEASED freeamt.
Explanation: IEBCOPY requests virtual storage to be

subdivided into work areas and buffers. The amount
requested and received is controlled by the WORK=
parameter and the JCL REGION= parameter.
This message documents how much was requested and
obtained. All numbers are in bytes.
minimum
minimum amount of virtual storage required by
IEBCOPY. Additional virtual storage is required
for larger data sets.
maximum
value of the IEBCOPY WORK= parameter,
default 1M.
obtained
amount of virtual storage GETMAIN awarded
IEBCOPY.
freeamt amount of virtual storage freed immediately so

that the region will still contain unallocated
virtual storage for use by system routines, etc.
The severity is 0.
User Response: Use this message with message
IEB1056I to calculate IEBCOPY virtual storage
requirements and actual usage, so that you make the
best use of the computing resources.
To increase the size of the work area:
1. If the REGION= size is large enough so that
IEBCOPY is being given the full amount that it
requests for its work area, then increase the
REGION= parameter and the WORK= parameter by
the same amount. This condition is true when
maximum equals obtained.
2. If IEBCOPY is not being given the full amount that it
requests for its work area, then increase the
REGION= parameter by maximum-obtained.
nnnnn
number of bytes released.
The severity is 0.
User Response: Use this message with message
IEB1055I to calculate IEBCOPY virtual storage
requirements and actual usage, so that you make the
best use of the computing resources.
Source: DFSMSdfp
When the size of the work area can not be increased,

1. Reduce the amount specified for buffers (with the
SIZE= invocation parameter) to the minimum
amount (or default it). This will use the minimum
amount of work area virtual storage as buffers and
increase the amount of virtual storage available for
member names and directory entries. Doing this
most often results in decreased performance, even if
it increases the size of the WORK= area so that the
spill file is no longer used.
2. If the current operation is a selective copy, then
divide the operation into more operations each with
775
a smaller number of members. This leaves more

room in the WORK= area for buffers and directory
blocks.
System Programmer Response: Message IEF374I
printed in the JCL message data set will tell the actual
region size used by a job step.
Source: DFSMSdfp
User Response: If it is necessary to reduce the

amount of storage IEBCOPY uses then the work area
size may be reduced by the size of the second buffer
given in this message.
Source: DFSMSdfp
IEB1058I
ALLOCATED 2 CONTIGUOUS
BUFFERS EACH bbbbb BYTES. WORK
AREA HAS avail BYTES AVAILABLE.
Explanation: At the start of each operation IEBCOPY

allocates part of the work area for buffers. The buffers
reported by this message are the minimum size
required to perform the operation, and are sufficient to
complete the operation.
bbbbb
size of 1 buffer.
avail
amount of virtual storage in the work area still

available for tables and saving directory
entries, etc.
IEB1063W
MEMBER member1 READ FROM

DDNAME ddname IS NOT AN ALIAS
BUT HAS SAME TTR AS MEMBER
member2
Explanation: The directory of the dataset contains two

entries with the same TTR and neither is an alias.
member1
name of member to be copied
member2
name of member already copied
ddname
ddname of dataset
The severity is 0.
The severity is 4.
User Response: This message documents how much

of the work area is allocated to buffer to assist you in
managing the virtual storage resource.
System Action: If the current operation is a compress,

the identified members are written as one entry (both
members will have the same TTR). For all other
operations, the identified members will be written as two
separate members (each member will have a different
TTR).
Source: DFSMSdfp
IEB1059I
ALLOCATED SECOND BUFFER OF

bbbbb BYTES. FIRST BUFFER IS NOW
fffff BYTES. WORK AREA HAS avail
BYTES AVAILABLE.
Explanation: The copy operation is ready to copy the

first member. Enough virtual storage remained in the
work area after building tables and saving directory
entries for additional buffers to be allocated.
IEBCOPY uses two buffers, so the existing two buffers
have been merged into a single first buffer. Then a
new second buffer is created from the free work area.
A small amount of storage may remain unused in the
work area after this second buffer allocation. This is
normal.
bbbbb
amount of storage added to the buffer pool.
fffff
original size of the buffer pool.
avail
residual amount of storage in the work area.
The severity is 0.
776
User Response: Determine proper relationship of the

identified members and correct the directory.
IEB1064I
STANDARD DD NAMES- sysin sysprint

sysut1 sysut2 sysut3 sysut4
Explanation: This message always precedes

IEB1065I. Please refer to it for an explanation of both
messages.
sysin
DD name for the control statement data set.
sysprint
DD name for the listing data set.
sysut1
DD name for the input data set.
sysut2
DD name for the output data set.
sysut3
DD name for the first spill data set.
sysut4
DD name for the second spill data set.
The severity is 0.
User Response: Refer to message IEB1065I.
The severity is 0.
Source: DFSMSdfp
IEB1065I
OVERRIDING DD NAMES- sysin sysprint

sysut1 sysut2 sysut3 sysut4
Explanation: IEBCOPY has been called by a program

which has given IEBCOPY a list of DD names to be
used for various files. Message IEB1064I lists the
default DD names. Message IEB1065I lists the DD
names IEBCOPY will use.
Differences between the two lists indicate that the
calling program provided names to override the default
names.
sysin
DD name for the control statement data set.
User Response: Code the Replace option on the

INDD or SELECT statement to force the member to be
copied.
Source: DFSMSdfp
IEB1068W
JCL FOR DD ddname WILL PROCESS

THE DATA SET AS SEQUENTIAL BUT
THE LABEL SAYS IT IS PARTITIONED.
(DS1DSORG= X'label_org' JFCDSORG=
X'jcl_org')
Explanation: There is a conflict between the JCL and

the data set label. The JCL supplied DSORG=PS
overrides the DSORG=PO in the label.
sysut1
DD name for the input data set.
Parameters like DSORG=PS can be added to your JCL

even though you did not code them. SMS ACS routines,
Data Classes, the JCL LIKE and DCB parameters can
all implicitly add to JCL.
sysut2
sysut3
DD name for the first spill data set.
ddname
sysut4
DD name for the second spill data set.
sysprint
DD name for the listing data set.
The severity is 0.
label_org
value of the DSORG field in the data set label.
jcl_org
Application Programmer Response: Refer to

OS/390 DFSMSdfp Utilities book Appendix A for details
about dynamically invoking IEBCOPY.
The severity is 4.
Source: DFSMSdfp
IEB1066D
diagnostic_text

service.
IEB1067I
member NOT disposition FROM INPUT

DATA SET BECAUSE REPLACE WAS
NOT SPECIFIED
Explanation: The member named was not copied to

the output data set because the output data set already
contains a member of the same name.
member
disposition
is one of:
COPIED
LOADED
UNLOADED
MOVED
ALTERED
value of the DSORG field in the JCL.
System Action: The existing data set will be

converted from partitioned to sequential and all
members in the partitioned data set will be lost. An
unload data set will be created in its place.
User Response: Determine where the the
DSORG=PS is coming from. Look at the label of data
sets referenced by the LIKE or DCB parameter, and use
ISMF to look at the definition of any Data Class
assigned to the data set.
A conflict like this can either be removed at its source or
you may override the conflict by coding DSORG=PO on
the DD statement or in the TSO ALLOCATE or ATTRIB
command.
Source: DFSMSdfp
IEB1069E
JCL FOR DD ddname WILL PROCESS

THE DATA SET AS PARTITIONED BUT
THE LABEL SAYS IT IS SEQUENTIAL.
EXPECT A TERMINAL I/O ERROR.
(DS1DSORG= X'label_org' JFCDSORG=
X'jcl_org')

the data set label. The JCL supplied DSORG=PO
overrides the DSORG=PS in the label.
Parameters like DSORG=PO can be added to your JCL
777
Data Classes, the JCL SPACE, LIKE and DCB
parameters can all implicitly add to JCL.
ddname
label_org
jcl_org
The severity is 0.
System Action: The data set is processed as an
unload (sequential) data set.
User Response: Remove the conflicting DSORG=PS
parameter or the directory quantity from the SPACE
parameter. If DSORG=PS does not appear in the JCL
or on the TSO ALLOCATE or ATTRIB command and the
data set is partitioned then add DSORG=PO to the JCL
or DSORG(PO) to the TSO command.
Source: DFSMSdfp
The severity is 8.
System Action: When IEBCOPY attempts to read the
directory at the start of the data set, one of three things
may occur:
1. A Wrong Length Record I/O error may occur
because the first record is not 256 bytes data with
an 8 byte key, or
2. IEBCOPY may find 0 directory records which is
interpreted as a corrupt partitioned data set, or
3. IEBCOPY may find the directory of a deleted
partitioned data set which used to occupy the disk
space, which will cause extra members (possibly
corrupt) to appear in the data set.
User Response: Determine where the DSORG=PO is
coming from. Look for directory blocks in the space
parameter, look at the label of data sets referenced by
the LIKE or DCB parameter, and use ISMF to look at
the definition of any Data Class assigned to the data
set.
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
command.
Source: DFSMSdfp
IEB1070W
JCL FOR DD ddname REQUESTS

DIRECTORY BLOCKS WITH A
SEQUENTIAL DATA SET. (JFCDSORG=
X'jcl_org' JFCBDQTY=dir_blocks)
Explanation: There is a conflict between parameters

in the JCL. The SPACE parameter specifies directory
blocks, which implies that the data set is partitioned.
DSORG=PS also appears in the JCL and indicates that
the data set is sequential.
ddname
jcl_org
dir_blocks
number of directory blocks specified in

the JCL.
778
IEB1071E
DD NAME ddname IS SUPPOSED TO

BE A PARTITIONED DATA SET BUT IT
HAS NO DIRECTORY. EXPECT A
TERMINAL I/O ERROR. (DS1LSTAR=
X'ttr' DS1DSORG=X'label_org'
JFCDSORG=X'jcl_org')

the data set label.
The data set is assumed to be partitioned because the
JCL contains DSORG=PO or because the JCL is silent
and the data set label contains DSORG=PO.
A valid partitioned data set must contain a directory,
which means that the address of the last record in the
data set can not be zero. However, DS1LSTAR is zero
which implies that a directory was never written in the
data set. Thus the data set is really sequential and the
JCL incorrectly specifies DSORG=PS, or the data set is
corrupt.
ddname
ttr
address of the last record in the data set. It is

a 3-byte hexadecimal relative disk address.
label_org
jcl_org
The severity is 8.
System Action: Processing continues and the data
set is assumed to be partitioned.
When IEBCOPY attempts to read the directory at the
start of the data set, one of three things may occur:
1. A Wrong Length Record I/O error may occur
because the first record is not 256 byte data with an
8 byte key, or
2. IEBCOPY may find 0 directory records which is
interpreted as a corrupt partitioned data set, or
3. IEBCOPY may find the directory of a deleted

partitioned data set which used to occupy the disk
space, which will cause extra members (possibly
corrupt) to appear in the data set.
set.
Add DSORG=PS to the DD statement or the TSO
ALLOCATE or ATTRIB command to explicitly override
the DSORG.
Source: DFSMSdfp
IEB1072W
JCL FOR DD ddname IMPLIES THAT

THE DATA SET IS PARTITIONED BUT
IT IS ON MAGNETIC TAPE.
PROCESSING IT AS SEQUENTIAL.
(DEVTYPE= X'dev_type' JFCDSORG=
X'jcl_org' JFCBDQTY=dir_blocks)
Explanation: There is a conflict in the JCL or between

the JCL and the catalog entry for the data set.
The unit allocated to the data set is a tape drive.
Therefore the data set must be an unload (sequential)
data set. However, the JCL contains DSORG=PO
and/or a SPACE parameter which specifies directory
blocks which indicates that the data set is partitioned.
Parameters like DSORG=PO can be added to your JCL
ddname
dev_type
device type from the UCBDEVT field.
jcl_org
dir_blocks
number of directory blocks specified in the
JCL.
The severity is 0.
System Action: The data set is treated as an unload
data set.
set.
Add DSORG=PS to the DD statement or the TSO
ALLOCATE or ATTRIB command to explicitly override

the DSORG.
Source: DFSMSdfp
IEB1073W
JCL FOR DD ddname REQUESTS A

NEW SEQUENTIAL DATA SET WITH
DIRECTORY BLOCKS. THE DATA SET
WAS CREATED AS PARTITIONED AND
WILL BE PROCESSED AS
PARTITIONED. (DS1DSORG=
X'label_org' JFCDSORG= X'jcl_org'
JFCBDQTY=dir_blocks)
Explanation: There is a conflict in the JCL.

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
JCL.
The data set is being created in this job step and
DADSM has written a directory and set DSORG=PS in
the data set label.
ddname
label_org
DSORG from the data set label.
jcl_org
DSORG from the JCL.
dir_blocks
quantity of directory blocks specified in the JCL
SPACE parameter.
The severity is 0.
System Action: The data set is processed as
partitioned.
User Response: Examine the JCL, the Data Class
assigned, and the label of any data set referred to by
the LIKE or DCB parameter in the JCL. Remove the
source of the conflict, or code DSORG=PO in the JCL
or on the TSO ALLOCATE or ATTRIB command.
Source: DFSMSdfp
IEB1074I
THE UNLOAD DATASET CONTAINS

PROGRAM OBJECTS AND OUTPUT
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.
The severity is 8.
System Action: The operation ends.
779
Source: DFSMSdfp
IEB1077I
member WAS EXCLUDED BUT NOT

FOUND IN ANY INPUT DATA SET
This is not an error condition. This message is to help

you better manage resources by telling you about idle
virtual storage.
Explanation: The member was coded on a EXCLUDE

statement does not exist in any input data set.
size
SIZE parameter value from the OS PARM

field.
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
area could be reduced by about avail.
User Response: Check the spelling of the name and

the directory of the input library to verify that the
member does not exist.
Source: DFSMSdfp

Source: DFSMSdfp
IEB1078I
THE BUFFER SPACE LIMIT

PARAMETER SIZE=size IS LESS
THAN THE MINIMUM BUFFER SIZE OF
length.
Explanation: A SIZE= parameter was coded in the OS

PARM field. The value of this parameter is too small.
size
SIZE parameter value from the OS PARM

field.
length
minimum value required for the parameter.
IEB1080D
diagnostic_text

service.
IEB1081D
diagnostic_text

service.
diagnostic_text
The severity is 0.
IEB1082D
System Action: The SIZE parameter is ignored.

service.
User Response: Remove the SIZE parameter.

If you must specify a SIZE parameter, check the
OS/390 DFSMSdfp Utilities book for information about
calculating the minimum value.
IEB1083D
Source: DFSMSdfp

service.
IEB1079I
CAN NOT ALLOCATE ANOTHER

BUFFER WITHOUT EXCEEDING THE
SIZE=size PARAMETER. WORK AREA
HAS avail BYTES AVAILABLE.
Explanation: The SIZE parameter was supplied, and

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
this extra space would normally be assigned to
additional buffers.
However, this extra space will be unused because the
buffers are already as large as the SIZE parameter
value will permit.
780
IEB1084D
diagnostic_text
diagnostic_text

service.
IEB1085D
diagnostic_text

service.
IEB1086D
diagnostic_text

service.
IEB1087D
diagnostic_text

service.
IEB1088D
diagnostic_text

service.
IEB1089D
diagnostic_text

service.
IEB1096I
NO MEMBERS disposition IN DATA SET

REFERENCED BY out_ddname
Explanation: Due to the validation error described in a

previous message, the ALTERMOD or COMPRESS
operation did not take place. The data set was not
changed.
disposition
is one of:
MOVED
ALTERED
out_ddname
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.
Source: DFSMSdfp
IEB1090D
diagnostic_text

service.
IEB1091D
diagnostic_text

service.
IEB1092D
diagnostic_text

service.
IEB1093D
diagnostic_text

service.
IEB1094D
diagnostic_text

service.
IEB1095D
diagnostic_text

service.
IEB1097I
FOLLOWING MEMBER(S) disposition IN

DATA SET REFERENCED BY ddname
Explanation: Following messages identify the

members altered or compressed.
This message assists in tracing the data sets which
were used, and which members they contributed.
disposition
is one of:
MOVED
ALTERED
ddname
The severity is 0.
System Action: Messages IEB154I and IEB155I
follow.
Source: DFSMSdfp
IEB1098I
mmmmm OF ttttt MEMBERS disposition
Explanation: This is a summary of the number of

members located in the current input data set and how
many were actually copied, etc.
Failure to copy all members may not be an error. Not
every members found may be eligible because
replace was not specified or because a member of the
same name was previously copied.
781
mmmmm
number of members processed.
ttttt
number of members found in the current input

data set.
disposition
is one of:
COPIED
LOADED
UNLOADED
MOVED
ALTERED
System Action: The operation is suppressed.

User Response: Use COPY, not COPYMOD to
compress or unload a data set. To alter an unload
(sequential) data set, reload it with COPYMOD and then
unload it.
Source: DFSMSdfp
IEB1101D
diagnostic_text

service.
The severity is 0.
diagnostic_text
IEB1102D
Source: DFSMSdfp

service.
IEB1099S
*** IEBCOPY IS NOT APF AUTHORIZED

***
Explanation: IEBCOPY must run from an authorized

library to use special I/O appendages. IEBCOPY has
found that it is not authorized, and may not be able to
copy from a partitioned data set.
The severity is 12.
System Action: IEBCOPY will try to avoid operations
requiring authorization. It will abend when it can not
avoid using a service requiring authorization. This
abend will be issued by the requested service (e.g.
GETMAIN, OPEN) not IEBCOPY.
User Response: Verify that any STEPLIB or JOBLIB
does not have any unauthorized libraries in the
concatenation.
IEB1103I
Explanation: A compress operation is scanning a

partitioned data set and has located the first space
which is unused. The TTR of this first gas bubble and
the name of the member closest to the bubble is given
in the message.
A gas bubble inside a member represents space at the
end of a track that is large enough to hold the first
record from the next track.
A gas bubble outside a member represents member
data that was deleted or updated.
position
is one of:
BEFORE
INSIDE
AFTER
System Programmer Response: Verify that

IEBCOPY is linked AC(1) into a library in the IEAAPFxx
list used to IPL the system, etc.
Source: DFSMSdfp
FIRST GAS BUBBLE IS position

MEMBER member AT TTR=ttr.
member
IEB1100S
statement MAY NOT BE USED TO

PERFORM A function OPERATION.
Explanation: Certain operations such as COPYMOD

are restricted from performing specific operations such
as a compress or unload.
statement
is one of:
COPYMOD
ALTERMOD
function
is one of:
COMPRESS
UNLOAD
The severity is 4.
782
ttr
The severity is 0.
System Action: Scanning stops and repacking
members begins.
Source: DFSMSdfp
IEB1104E
VARIABLE SPANNED RECORD

FORMAT DATA SETS CAN NOT BE
REBLOCKED. EXECUTION
TERMINATES.
Explanation: IEBCOPY does not support partitioned

data sets with RECFM=VS or RECFM=VBS. (Do not
confuse this with a unload (sequential) data set which
always has a spanned RECFM.)
The input and output DCB parameters demand that

logical records be reblocked or deblocked.
The severity is 4.
User Response: Use an application program that has
been coded to handle spanned records to process the
data set.
User Response: Use this message to estimate how

many additional members can be copied with out
increasing the work area size. Each additional member
will increase the control table size by 10 bytes.
Source: DFSMSdfp
IEB1108I
Source: DFSMSdfp
IEB1104W
VARIABLE SPANNED RECORD

FORMAT DATA SETS CAN NOT BE
REBLOCKED. EXECUTION
CONTINUES.
COPYMOD TABLE AREA IS nnnnn

BYTES LONG. WORK AREA HAS avail
BYTES AVAILABLE.
Explanation: Room for COPYMOD tables and buffers

has been reserved.
nnnnn
amount of space reserved for COPYMOD.
Explanation: IEBCOPY does not support partitioned

data sets with RECFM=VS or RECFM=VBS. (Do not
confuse this with a unload (sequential) data set which
always has a spanned RECFM.)
avail
amount of the work area remaining for buffers,

tables, and directory entries.
The input and output DCB parameters do not demand

that logical records be reblocked or deblocked.
The severity is 0.
Source: DFSMSdfp
The severity is 0.
System Action: Execution continues as if the data
sets were RECFM=U. An I/O error may occur.
User Response: Use an application program that has
been coded to handle spanned records to process the
data set.
IEB1109D
diagnostic_text

service.
Source: DFSMSdfp
IEB1110D
IEB1105I

service.
THE TARGET DATA SET IS

CURRENTLY EMPTY
Explanation: The scan of the output data set directory

discloses that there are no members in the data set.
The severity is 0.
IEB1111D
diagnostic_text
diagnostic_text

service.
Source: DFSMSdfp
IEB1112D
IEB1106I
CONTROL TABLE IS ttttt BYTES LONG.

WORK AREA HAS avail BYTES
AVAILABLE.
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
output data set directory blocks.
ttttt
size of the control table.
avail
amount of remaining free area.
The severity is 0.
diagnostic_text

service.
IEB1113D
diagnostic_text

service.
IEB1114D
diagnostic_text

service.

783
IEB1115D
diagnostic_text

service.
IEB1116D
diagnostic_text

service.
IEB1117D
diagnostic_text

service.
IEB1118D
diagnostic_text

service.
IEB1119D
diagnostic_text

service.
IEB1120D
diagnostic_text
IEB1125D

service.
IEB1126D
diagnostic_text

service.
diagnostic_text

service.
IEB1127D
diagnostic_text

service.
IEB1128D
diagnostic_text

service.
IEB1129D
diagnostic_text

service.
IEB1130I

service.
IEB1121D
diagnostic_text
A severity MESSAGE FROM PDSE

PROCESSING APPEARS ABOVE -DIAGNOSTIC INFORMATION IS
X'diagcode'
Explanation: Something from the current operation

with a PDSE deserves further attention. The diagnostic
information may help the IBM support center should you
request software service.
severity
IEB1122D
diagnostic_text

service.
IEB1123D
diagnostic_text

service.
IEB1124D
diagnostic_text

service.
784
is one of:
WARNING
ERROR - an error severity appears as
IEB1130W.
SEVERE ERROR- a severe error severity
appears as IEB1130E.
TERMINATING - a terminating severity
appears as IEB1130E.
diagcode
diagnostic information that should be supplied
when requesting service.
The severity is 0.
User Response: Look at the IGW prefix messages
preceding this message for a message of significance.
Application Programmer Response: This probably

represents an unusual condition or problem. Refer to
accompanying messages, particularly those with IGW
and IEB prefixes, for specific information and additional
guidance.
System Programmer Response: Please furnish the
information in this message when requesting service. If
the error recurs and the program is not in error, look at
the messages in the job log for more information.
Center. Provide the JCL and all printed output and
Source: DFSMSdfp
IEB1131W
PHYSICAL RECORD IN MEMBER

member REFERENCED BY ddname
EXCEEDS INPUT DATA SET BLOCK
SIZE. RECORD LENGTH IS length,
INPUT BLKSIZE IS iblksize, TTR=TTR
CCHHRKDD=CCHHRKDD.
Explanation: A fat block was found in member

member. Most programs cannot read fat blocks; they
receive I/O errors when they try.
IEBCOPY is reblocking the input records and will copy
all of the logical records in this fat block to 1 or more
output blocks as needed.
This message will appear only once per member even
when the member contains more than 1 fat block.
member
IEB1132E
VARIABLE FORMAT LOGICAL

RECORD IS TOO LONG FOR BLOCK.
RECORD LENGTH IS length OUTPUT
BLKSIZE IS oblksize
Explanation: For variable format records, the longest

logical record that can be written to the output data set
is 4 bytes less than the output data set block size
blocksize. A logical record in the input data set is length
byte long, which is too big to fit in an output data set
block.
length
length of the logical record.
blocksize
output data set block size.
The severity is 0.
User Response: Increase the block size of the output
data set.
Source: DFSMSdfp
IEB1133E
COPYMOD WORK AREA OVERFLOW

PROCESSING MEMBER member
Explanation: The internal tables used by COPYMOD

are too small. This may be because the load module
being processed is defective.
member

The severity is 8.
ddname
DD name of the input data set.
length
length of physical record.
iblksize input data set block size.

ttr
System Action: The member is copied as if the

operation were COPY instead of COPYMOD.
User Response: Try Link Editing the member and/or
executing it to verify that it is a valid load module.
mbbcchhr
DASD address of record.
System Programmer Response: If the member is a

valid load module then request service as the table size
may be too small.
The severity is 0.
Source: DFSMSdfp
IEB1134D
diagnostic_text
User Response: Increase the block size in the label of

the input data set to meet or exceed length, or copy the
member to another PDS with a different block size and
then back again to reblock it to the current input data
set block size.

service.
Source: DFSMSdfp
IEB1135D
diagnostic_text

service.
785
IEB1136D
diagnostic_text
IEB1139W

service.
IEB1137D
diagnostic_text
THE OUTPUT DATA SET BLOCK SIZE

IS BEING REDUCED FROM <old> TO
<new> BYTES. ANY EXISTING
PHYSICAL RECORDS LONGER THAN
<new> BYTES ARE FAT BLOCKS AND
MAY CAUSE I/O ERRORS.

service.
Explanation: IEBCOPY may create fat blocks if the

data set already contains records longer than the new
block size. While the link editor and program fetch and
IEBCOPY can tolerate fat blocks, other programs may
encounter I/O errors processing them.
IEB1137E
System Action: Processing continues, possibly

creating fat block.
UTTR WORK AREA OVERFLOW

PROCESSING MEMBER MMMMMMMM,
MISSES=NNNN
Explanation: UTTR table has overflowed while

processing module MMMMMMMM.
User Response: Increase the BLKSIZE and/or LRECL

of the output data set to be at least as large as the
longest record.
System Action: Processing ceases.

User Response: Contact IBM support and provide the
value NNNN for correction.
IEB1140W
<member> IS NOT A LOAD MODULE.

<reason>. EXPECTED=<expected>
ACTUAL=<actual>
Explanation: The table of user TTRs was of

insufficient size to copy member mmmmmmmm.
Explanation: While examining the directory entry for

the load module, COPYMOD determined that the
member is not a load module for the given <reason>. It
will be copied without reblocking as if COPY not
COPYMOD was requested. <expected> and <actual>
are length in bytes of the directory entry.
Possible <reason>s are:
IEB1137W
UTTR WORK AREA OVERFLOW

PROCESSING MEMBER mmmmmmmm,
MISSES=nnnnnnnn.
mmmmmmmm
name of member.
nnnnnnnn
amount of storage necessary for successful
copy.
v DIRECTORY ENTRY TOO SHORT (LESS THAN 33

BYTES)
v 0 OR 3 USER TTRS
v USER TTR 1 IS A NOTELIST
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

PARM=UTTRTAB=nnnnnnnn where nnnnnnnn is the
value given in misses=.
v 2 TTRS BUT NOT SCATTER LOAD/OVERLAY
System Programmer Response: Processing

continues.
v DIRECTORY ENTRY SIZE WRONG
Source: DFSMSdfp
IEB1138W
THE OUTPUT DATA SET BLOCK SIZE

OF <out_size> BYTES IS SMALLER
THAN THE INPUT BLKSIZE OF
<in_size> BYTES.
Explanation: Fat blocks may be created. Increase

output BLKSIZE.
v OVERLAY MODULE WITHOUT NOTELIST

v SCATTER LOAD MODULE HAS NOTELIST

User Response: Validate the directory entry and the
input data set. Relink or recreate the load module.
System Programmer Response: Verify that all
maintenance has been applied to programs such as the
link editor and binder to correct any compatibility
problems.
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.
786
Possible <reason>s are:

v OVERLAPPING TEXT BLOCKS
v TEXT RECORD SIZE WRONG
IEB1143I
AT LOAD MODULE RECORD

<record_count>
v CONTROL RECORD SIZE WRONG
Explanation: The relative record number of the last

load module record COPYMOD examined before
detecting the error or problem reported in message
IEB1141W or IEB1142W is <record_count>.
v ECORD IS NOT A CONTROL RECORD
v OVERLAY MODULE NOTE LIST SIZE

v CESD RECORD SIZE WRONG
v NO-TEXT MODULE CESDN RECORD SIZE

v IDR RECORD SIZE WRONG
IEB1144I
v SYM (TEXTRAN) RECORD SIZE WRONG
MEMBER TT-R AF TT-R.N TT-R.N

TT-R.N ATTR ...
v UNIDENTIFIABLE RECORD TYPE
Explanation: See message IEB1144I.
v READRLD DIAGNOSED RLD PROBLEM
v RAN OFF END OF ESD TABLE

v GETINPUT DIAGNOSED DS SPACE PROBLEM
v OVERLAY MODULE SEGMENT OVER/UNDER RUN
System Programmer Response: Refer to the link

editor or BLDL macro documentation to interpret the
hex data.
v OVERLAY MODULE SEGMENT NOT IN NOTE LIST

System Action: A COPY operation is performed for
the member.
User Response: Validate the directory entry and the
input data set. Relink or recreate the load module.
SYSTEM PROGRAMMER RESPONSE: Verify that all
maintenance has been applied to programs such as the
link editor and binder to correct any compatibility
problems.
IEB1142W
module IS AN INCOMPATIBLE OR
DAMAGED LOAD MODULE AND
SHOULD BE RE-LINKED -- COMMON
SECTION OUT OF PLACE
IEB1145I
<de_member> <hex_data>
Explanation: IEB1144I titles the printout of the load

module directory entry in hexadecimal by message
IEB1145I. These two messages follow IEB1140I.
System Programmer Response: Refer to the link
editor or BLDL macro documentation to interpret the
hex data.
IEB1153I
An INVALID RECORD WAS READ

FROM PDSU DDN=ddname
RECORD=nn DSN=dsname
Explanation: The COPYMOD function of the

IEBCOPY utility cannot unblock a module because the
common sections for the module are not at the end of
the module where the link editor usually places them.
COPYMOD cannot process the module displayed in the
message text.
Explanation: An invalid record was detected in off

loaded data set.
nn The invalid record number.
module
The load module being processed by COPYMOD.
dsname
The data set name.
System Action: IEBCOPY uses the COPY function

instead of the COPYMOD function to process the
displayed load module.
System Action: The copy operation is ended.
System Programmer Response: Relink or rebind the

load module and then retry the COPYMOD function of
the IEBCOPY utility.
Source: DFSMSdfp
Detecting Module: IEBCPMOD
ddname
The DDNAME of the data set.
Source: DFSMSdfp
Detecting Module: IEBCPMOD
IEB1157W
DIRECTORY ENTRY FOR MMMMMMMM

CONTAINS AN INVALID UTTR ttttrr
REPLACED BY VALID DATA FROM
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.
787
User Response: Verify that the copied module

functions correctly.
IEB1157E

CONTAINS AN INVALID UTTR ttttrr UTTR DATA UNCHANGED

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

|
|
User Response: Verify that the copied module

functions correctly.
Source: DFSMSdfp
Detecting Module: IEBWSU
788

CONTAINS AN INVALID TTR
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
users 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
789
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
790
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
Print Services Facility

Processor Resource/Systems Manager
PSF
RACF
Resource Measurement Facility
RMF
S/370
S/390
SecureWay
SOM
SOMobjects
SP
Sysplex Timer
System/370
VM/ESA
VTAM
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
792
Readers Comments Wed 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?
Overall satisfaction
Very Satisfied
h
Satisfied
h
Neutral
h
Dissatisfied
h
Very Dissatisfied
h
Neutral
h
h
h
h
h
h
Dissatisfied
h
h
h
h
h
h
Very Dissatisfied
h
h
h
h
h
h
How satisfied are you that the information in this book is:
Accurate
Complete
Easy to find
Easy to understand
Well organized
Applicable to your tasks
Very Satisfied
h
h
h
h
h
h
Satisfied
h
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
Company or Organization
Phone No.
Address
GC28-1786-16
IBMR
___________________________________________________________________________________________________
Readers Comments Wed Like to Hear from You
Cut or Fold
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
GC28-1786-16
Cut or Fold
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

Problem Identification PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Problem Identification PDF

Uploaded by

Copyright:

Available Formats

OS/390

MVS System Messages

MVS System Messages

Seventeenth Edition, December 2001

Chapter 2. LANRES Messages (EWX, ACP, ASD) . . . . . . . . . . . . . . . . . . . . 13

Chapter 7. GOS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Chapter 10. ICP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Copyright IBM Corp. 1988, 2001

Chapter 12. ICU Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

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

About This Book

JES2 Messages, GC28-1796

Who Should Use These MVS System Messages Books

How to Use These Books

Copyright IBM Corp. 1988, 2001

Using LookAt to look up message explanations

Where to Find the Most Current Message Information

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

Where to Find More Information

Subsystem, Product, and Hardware Books

ACF/TCAM Base Installation Guide

Asynchronous Adapter Device Driver Table

C/370 Programming Guide

CICS Family: General Information

CICS Recovery and Restart Guide

Common I/O-Device Commands

CPI Communications Reference

DATABASE 2 Application Programming Guide

DFSMS/MVS DFSMSdfp Diagnosis Reference

DB2 Application Programming Guide for TSO and Batch Users

DATABASE 2 General Information Manual

IBM DATABASE 2 Messages

IBM DATABASE 2 Version 2 Messages and Codes

IBM DATABASE 2 Version 2 Release 3 Messages and Codes

IBM Graphics Access Method/SP Messages and Codes

ES/9000: Operating Your System

About This Book

FileNet OSAR Library Unit Product Description

IBM 3290 Information Panel Description and Reference

IBM 3990/9390 Operations and Recovery Guide

IBM 3990/9390 Storage Contro Planning, Installation, and Storage Administration

IBM 3990 Storage Control Reference for Model 6

IBM 9340 Direct Access Storage Subsystems Reference

LASERDRIVE** 1200 Engineering Specification

Maintaining IBM Storage Subsystem Media

Maintenance Information for the 9037 Sysplex Timer

Maintaining IBM Storage Subsystem Media

OS/2 Programming Tools and Info V-1.3 Manage Macro Assembler/2

OS/2 WARP Control Program Programming Reference

Portable Netware System Messages

Print Services Access Facility/MVS Users Guide and Reference

IBM Enterprise Systems Architecture/390 Principles of Operation

Remote Copy Administrators Guide and Reference

SCSI Adapter Completion Code Table

RT SCSI Adapter Device Driver Table

Sysplex Timer 9037 Maintenance

VM/ESA CP Command and Utility Reference

VM/ESA General User Command Reference

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

Book Title - Order Number

OS/390 MVS System Messages, Vol 1

OS/390 MVS System Messages, Vol 2

Time Sharing Option Extensions (TSO/E)